Short answer. A MOP (method of procedure) is a step-by-step plan for one specific task on critical data center equipment. It lists the scope, risks, roles, steps, checks and a back-out plan, and it is approved before work starts. SOPs cover routine tasks; EOPs cover emergencies.
Definition. A MOP is a written, step-by-step plan for one specific task on critical equipment, reviewed and approved before work starts.
MOP, SOP and EOP compared
| MOP | SOP | EOP | |
|---|---|---|---|
| Used for | One specific planned task or change on critical equipment | Routine tasks done the same way every time | Failures and abnormal events |
| Example | Planned maintenance on a UPS module | Daily rounds; a standard equipment check | Loss of utility power; a UPS fault |
| When it is written | For each task, before the work | Once, then reviewed on a schedule | In advance, then drilled and reviewed |
| Approval | Before each use | When created or changed | When created or changed |
What a good MOP contains
- Scope and equipment. What will be done, on which equipment, named exactly as labeled in the field.
- Risk assessment. What could go wrong, what load is at risk, and the controls, including the electrical safety requirements under NFPA 70E-2024.
- Prerequisites. Conditions that must be true before step 1: approvals, notifications, redundancy available, parts and tools on hand.
- Roles and contacts. Who performs, who verifies, who approves, and who to call.
- Step-by-step actions with expected results. One action per step, and the state or reading expected after it.
- Hold points. Steps where work stops until a named person checks and signs off.
- Back-out (rollback) steps. How to return to a safe, stable state if a result is not as expected.
- Communications. Who is told before, during and after the work.
- Approvals. Names, roles and dates.
- Records. Readings, photos, sign-offs and time stamps kept with the MOP.
Approval workflow and version control
A MOP is only useful if the crew runs the approved version. Keep one controlled copy, record who changed what and why, and require review and approval before a new version is released. Retire old versions so they cannot be printed or opened by mistake. Field feedback (an unclear step, a wrong label) should go back to the author and become a new, approved version, not a handwritten note on one copy. See also how to digitize a procedure without losing version control.
What an EOP should include
- The event it covers and how staff recognize it.
- The first actions, in order, kept short enough to follow under stress.
- Who is in charge, who is notified, and how.
- Safety limits: what staff must not do, and when to stop and call for help.
- Steps to make people and equipment safe and to restore service.
- Where the EOP is kept, so it can be found in seconds, and how often it is drilled and reviewed.
Emergency procedures support, and do not replace, your site emergency action plan and calling 911.
ATS transfer tests and other common MOPs
An automatic transfer switch (ATS) moves load from one source to another, for example from the utility to a generator. Transfer tests are a common MOP subject. Write them from the manufacturer’s instructions and your site’s power design, with named hold points before and after each transfer, the readings to record, and a back-out plan.
Running MOPs in the field, including offline
Electrical rooms and new buildings often have no signal. A digital MOP should be stored on the device before work, record every step with no connection, and upload when the device reconnects. Show one step at a time, in order, and require a reading, photo or sign-off at critical steps.
Choosing MOP software
When comparing tools, check offline use, fixed step order, proof at critical steps, hold points and sign-off, version control and approval, and the review tools HQ gets. Our guide to choosing a field procedure system has a full checklist.
Where ICARUS Ops fits
The ICARUS Ops Error Elimination System (EES) runs MOPs, SOPs and EOPs as step-by-step digital procedures on Android and iOS. HQ writes and approves them in the ICARUS Ops web portal with version control. Technicians run them offline, one step at a time, with time stamps, photo proof and QA sign-off gates at hold points. See data center operations.
See a sample ICARUS Ops EES procedure
See a sample ICARUS Ops EES procedure
Demos are for teams actively evaluating software for deployment.
Frequently asked questions
What is a MOP in a data center?
A MOP (method of procedure) is a written, step-by-step plan for one specific task on critical data center equipment, such as maintenance or a change to the power system. It lists the scope, risks, roles, steps, checks and a back-out plan, and it is approved before work starts.
What is the difference between a MOP, an SOP and an EOP?
A MOP covers one specific, planned task and is approved before the work. An SOP covers a routine task done the same way every time, such as daily rounds. An EOP tells staff what to do when something fails, such as a loss of utility power.
What is a back-out plan?
A back-out (rollback) plan is the set of steps that returns the equipment to its last known safe and stable state if a MOP step gives an unexpected result or the work has to stop. It is written and approved with the MOP, not improvised during the work.
Who should approve a MOP?
Approval rules are set by each organization. Commonly, the MOP author, the facility or operations lead, and the people responsible for safety and for any affected customers review it before it is released. Only the approved version should reach the field.