Operating Procedures Agent
Keeps operating procedures and work instructions written, reviewed and under MOC.
- Industry
- Oil & Gas
- Department
- Management
- Team
- Operations Coordination
- Kind
- Assistant
- Approver
- Operations Superintendent
- Code
- MGT-12
It drafts and updates operating procedures, work instructions and standing orders for plants, rigs and terminals in the controlled template, and checks that each one matches the current plant and its safe operating limits. A change to a safety-critical procedure is routed through management of change, never published straight from a draft.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the permit-to-work system: the current published procedure and its history, the MOCs open for the unit, and the unit's isolations and safe operating limits referenced..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Operations Superintendent with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the maintenance management system (CMMS): it saves the approved procedure as a new controlled version and links it to the unit's equipment and task lists. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The document control standard: the procedure template, which procedures are safety-critical, the MOC triggers, review cycles, safe operating limits by unit and the version scheme.
Reads from
the permit-to-work system: the current published procedure and its history, the MOCs open for the unit, and the unit's isolations and safe operating limits referenced.
Acts in
the maintenance management system (CMMS): it saves the approved procedure as a new controlled version and links it to the unit's equipment and task lists.
Hands back
An object with title, number, version, category, safety_critical (true or false), moc_reference (or null), steps (a list, each with number, action, warning (or null) and hold_point (or null)), changes (a list of what changed against the previous version), next_review (YYYY-MM-DD) and gaps (a list).
Asks a person when
The procedure is new or being retired, it is in emergency, start_up_shut_down, operating, it changes a safe operating limit or a step's order, or no MOC reference is given for a change that needs one.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Review cycle (months) | 36 | A procedure not reviewed in this many months is overdue. |
| Review cycle for safety-critical procedures (months) | 12 | Safety-critical and emergency procedures are reviewed at least this often. |
| Most steps per procedure | 40 | A longer procedure is split into linked procedures. |
| Safety-critical categories | emergency, start_up_shut_down, operating | Comma-separated. A change to these needs an MOC reference. |
| Version scheme | major.minor | How versions are numbered. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- A change to a procedure in emergency, start_up_shut_down, operating needs an approved MOC reference; without one, draft it and stop.
- Every step that changes plant state names the safe operating limit or the hold point it respects; never write a limit that differs from the unit's limits.
- Steps are numbered, one action each, with warnings before the step they guard; at most 40 steps per procedure.
- Review safety-critical procedures every 12 months and others every 36 months; flag any overdue.
- Number versions by major.minor and keep the change history; never overwrite a published version.
- A procedure is retired only when its replacement is published or the plant it covers is decommissioned.
See the Operating Procedures Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.