JobsEnergy · Chemicals
Management of change
Revision deltas plus everything connected to the change, so MOC reviews start from evidence instead of a search through the drawings.
- Works with
- Process and operations engineers, MOC coordinators
- Starts from
- The proposed markup and the current P&IDs
- Delivers
- A change package: what changes, what it touches, what needs updating
01
Summary
Every MOC asks the same questions: what exactly is changing, what else does it touch, and which documents have to be updated afterwards. Answering them means tracing lines across sheets, finding the instruments and relief devices involved, and checking procedures and registers. It is slow, and whatever gets missed becomes a gap in the process safety information.
Operon compares the proposed change with the current, verified drawings, lists every added, removed and modified item, and follows the connections: the lines, instruments, relief devices and equipment linked to the change, and the documents that reference them. The review starts from a complete picture, and the close-out has a checklist.
02
Inputs and outputs
What goes in
- The proposed markup or revised drawings
- Current P&IDs for the affected units
- Relief device, equipment and instrument registers
- Procedures and documents that reference the affected tags
What comes out
- A structured diff of the change
- Connected items: lines, instruments, relief devices and equipment
- Documents that need updating, listed by tag
- A close-out checklist linked to the MOC
03
How it runs
Step
Operon
Your team
01
Diff the proposal
Operon
Compares the markup with the current drawings, item by item.
Your team
Submits the change as usual.
02
Follow the connections
Operon
Traces every line and device connected to the changed items, across sheets.
Your team
Reviews the impact list in the MOC meeting.
03
List the updates
Operon
Lists the drawings, registers and procedures that reference the affected tags.
Your team
Assigns an owner to each update.
04
Close out
Operon
Checks that each update was made before the MOC closes.
Your team
Approves the close-out.
04
What changes
Today
With Operon
Impact review
Today
Built from memory and a drawing search
With Operon
Starts from the full list of connected items
Document updates
Today
Missed ones found at the next audit
With Operon
Listed, assigned and checked at close-out
The record
Today
Scattered across emails
With Operon
Linked to the MOC
05
Checks built in
Engineers decide
Operon lists what a change touches. Risk judgments stay in the MOC review.
Against verified drawings
Deltas are computed against drawings your team has verified.
06
Getting started
Send a closed MOC with its markup and the P&IDs it changed. We produce the change package for it, so your team can compare it with what the review actually covered.
First results within a week. Live in three weeks.
- One closed MOC and its markup
- The P&IDs before the change
- The documents updated at close-out
Related jobs
Further reading
Start with the work that costs you the most.
Tell us where your team loses the most hours. Three weeks later, an AI employee built for your company is doing that work.