Prepare an MOC package.
From a P&ID revision to a complete management-of-change package with scope, impact, approval, and trace
Preparing a management of change (MOC) package is the process safety engineering process of documenting every change to a covered facility per OSHA PSM 1910.119(l) and the equivalent international regimes (UK COMAH, EU Seveso III, Canadian PSR). An MOC package carries the technical scope of the change (what tags, equipment, lines, and loops are affected), the safety and operability review (HAZOP node revisit, SIL impact, LOPA delta), the approval signatures from the affected disciplines, the training requirements for operators, and the cross-reference to the updated P&ID set. MOC discipline drives the audit trail; missing MOC documentation is the most-cited deficiency in process safety audits.
Inputs.
- +Pre-change P&ID set (baseline)
- +Post-change P&ID set (proposed)
- +Existing HAZOP study
- +Existing SIL verification calculation
- +Operating procedure for the affected node
Outputs.
- →Tag-level change list with source-page references for every revised tag
- →Updated I/O list reflecting the proposed change
- →HAZOP impact assessment with affected nodes flagged
- →SIL impact assessment with affected SIFs flagged
- →Cross-discipline approval cover sheet
- →Audit-traceable MOC package (PDF binder + Excel workbook + JSON for the MOC tool)
| Stage | Source artifact | MOC document |
|---|---|---|
| Scope identification | P&ID revision diff | Tag-level change list with source-page references |
| Process safety review | HAZOP node walk | Re-rationalized HAZOP rows for the affected node |
| SIS impact assessment | SIL verification diff | Affected SIF list with revised PFDavg |
| Approval chain | Discipline lead signatures | Multi-discipline sign-off page |
| Operator training | Operating procedure update | Training record per operator |
| Trace + closeout | Final P&ID + updated I/O list | Cross-reference table for audit |
Step by step.
- 01
Diff the pre-change and post-change P&ID
Run the revision comparison. The tag-level diff becomes the technical scope of the change.
- 02
Filter affected SIS scope
Filter the diff to SIS-classified tags. Any change touching a SIS tag triggers the SIF impact assessment.
- 03
Re-walk affected HAZOP nodes
Cross-reference the changed tags against HAZOP node boundaries. Affected nodes get a revisit; unaffected nodes carry forward.
- 04
Update SIL verification
When the SIS architecture changes (sensor element added, voting reconfigured, final element replaced), the affected SIF runs through SIL re-verification.
- 05
Assemble the discipline review
Each affected discipline lead reviews the change scope and signs the approval page. The trace from the sign-off back to the tag-level diff is preserved.
- 06
Archive in the MOC tool
Excel workbook drops into Sphera ProcessMAP, Wolters Kluwer Enablon, ABS Group ABS Nautilus, or in-house MOC tooling. JSON export preserves the audit trail.
Common questions.
What regulations drive MOC discipline?
OSHA PSM 1910.119(l) in the United States; UK COMAH and EU Seveso III in Europe; Canadian PSR; equivalent regimes in Australia (Major Hazard Facilities), Singapore (MHI), and Saudi Arabia (HSE Code). The technical requirements differ in detail but the audit-trail discipline is consistent.
Can the MOC package drive the HAZOP revisit automatically?
The package surfaces the affected HAZOP nodes by cross-referencing the changed tags against HAZOP node boundaries. The decision to re-rationalize a node and the engineering judgment about consequence severity remain with the process safety team.
Start a workspace.
Upload the source documents, run the workflow, ship the document in the column shape the next consumer expects.