Management of Change (MOC) in Manufacturing: A Practical Guide

Management of change (MOC) is the formal process for reviewing, approving, and documenting any modification to equipment, process conditions, materials, or procedures before it is implemented, so hazards introduced by the change are identified and controlled in advance rather than discovered in operation. MOC is a required element of process safety management regimes (OSHA PSM in the US, Seveso requirements in the EU), and a healthy discipline for any plant, regulated or not.

What triggers an MOC

• Equipment changes: new machines, modified guarding, changed interlocks, different pump or valve specifications.
• Process changes: new setpoints outside proven ranges, altered sequences, changed cleaning regimes.
• Material changes: a new raw material, lubricant, or chemical, or a new supplier grade of an existing one.
• Procedural and organizational changes: revised operating procedures, staffing or responsibility shifts on safety-critical tasks.
• Temporary changes: bypasses, rented equipment, trial runs. These need an expiry date and a forced review.

The only modifications exempt are true replacements in kind: identical part, identical specification, identical function. Anything else is a change.

The MOC workflow

1. Request: the initiator describes the change, its purpose, and the affected equipment and documents.
2. Risk review: a competent team assesses hazards introduced or altered by the change, scaled to its risk.
3. Approval: defined authorities approve or reject, with conditions where needed.
4. Implementation: the change is executed, drawings and procedures are updated, and affected staff are trained.
5. Pre-startup safety review (PSSR): a final check that everything the approval required is actually in place.
6. Closure: the MOC record is completed, and temporary changes are either made permanent through a new review or removed.

Worked example: scoring a change

A team wants to switch a hydraulic unit from mineral oil to a cheaper alternative fluid. A simple 5x5 risk screen scores the change: likelihood of seal incompatibility is rated 3 of 5 (supplier data is ambiguous), severity is rated 4 of 5 (a pressurized leak near a hot surface), giving 12 of 25, which the site matrix classifies as medium-high and routes to a full review instead of a fast-track signature. The review orders a seal compatibility test and a HAZOP-style pass on the affected system, which surfaces one guideword deviation (more temperature: the new fluid's lower flash point) and adds a temperature alarm before approval. Cost of the review: a few engineering hours. Cost of finding the flash point issue in operation: potentially a fire.

MOC methods and companions

The risk review inside an MOC borrows standard tools: FMEA for equipment-level failure modes, HAZOP for process deviations, and job safety analysis for task-level risk. Execution-side companions matter too: high-risk implementation work usually runs under a permit to work with lockout/tagout, and systemic failures found later should flow into CAPA.

Where MOC fails in practice

• Change creep: many small unreviewed tweaks that add up to a different process.
• Temporary forever: bypasses and trial settings that never get closed out.
• Paper updates lagging reality: the plant changes, the P&IDs and procedures do not.
• All changes treated equally: when a lubricant swap needs the same paperwork as a reactor modification, people route around the system.
• No connection to maintenance records: changes implemented through work orders that the MOC file never references.

The data trail: assets and work orders

Auditors and incident investigators ask the same question: what exactly changed on this equipment, and when? That answer should come from records, not memory. Keeping every modification tied to its asset in a CMMS, with the work orders that implemented it, gives MOC a reliable backbone, and dedicated MOC software can layer the approval workflow on top. Fabrico contributes the equipment truth: complete asset histories plus real-time production monitoring, so teams can also see how performance actually shifted after a change went live.

Frequently Asked Questions

What is a replacement in kind?

A replacement that matches the original in specification, material, and function, such as fitting the same OEM part number. It does not require MOC. A "similar" part with different ratings, materials, or a different manufacturer is a change and needs review.

Is MOC only for chemical plants?

No. The legal mandate is strongest in process industries, but the failure mode it prevents (an unreviewed change interacting with the system in an unexpected way) exists in every factory. Discrete manufacturers apply lighter-weight MOC to equipment, tooling, and material changes.

How is MOC different from engineering change management?

Engineering change management (ECM or ECO processes) controls product design changes. MOC controls changes to the plant, process, and procedures with a safety and risk focus. Many changes touch both systems, so mature sites cross-reference them.

Keep a complete, auditable equipment history behind every change. Book a Fabrico demo.