Every change and every permit, checked against the drawings.
MOC software routes the approvals and the permit system moves the forms, but the checking behind them is still manual: an engineer walking the drawings to map what a change touches, a sample of permits audited because nobody can read them all. Raven's agents read the drawings and records themselves: every change mapped before the review, every permit checked, every design question answered with the page it came from.
Everything a change touches, mapped before the review.
MOC software routes the change for approval; the impact assessment behind it is still an engineer walking the drawings. Raven's agents follow the change across the P&IDs and list every line, instrument, procedure, and datasheet it touches, with prior changes on the same system beside them. The review starts complete.
| Touched | Found in | Note |
|---|---|---|
| FIC-1102 · control loop | P&ID 1103 | on the new routing |
| Interlock I-12 · trips P-101A | C&E · sheet 4 | in the worksheet |
| SOP-118 · normal lineup | procedure | cites the old routing |
| PSV-201 · relief sizing | DS-0412 | basis affected |
| MOC-1984 · 2023 · same header | MOC register | prior change linked |
Every permit checked, not just a sample.
Control-of-work systems raise and route the permits; checking each one against the drawings is still manual, so audits sample. Raven's agents check every permit: the isolation list against the P&ID, the draft against your permit standard, the overlaps against other permits active in the same area.
| Permit | Check | Finding |
|---|---|---|
| PTW-3321 · hot work | isolations | blind at N2 tie-in not on the list |
| PTW-3324 · line break | SIMOPS | overlaps PTW-3321 · Rack 4 |
| PTW-3318 · vessel entry | isolations · gas test | complete |
| PTW-3299 · closed | reinstatement | de-isolation verified |
What's bypassed right now, and who approved it?
Shift logbooks and bypass registers record what happened; finding it again is the manual part. Raven's agents keep every procedure, log entry, and bypass record linked to the equipment on the drawing, and draft procedure updates from your own documents, each step cited to the SOP, P&ID, or manual it came from.
| Bypass | Record | Status |
|---|---|---|
| BP-118 · interlock I-12 | log · 12 May | open · past review date |
| BP-121 · TAH-4012 override | approval linked | review due 04 Sep |
| BP-097 · analyser A-204 | reinstated | closed |
The case file assembled while the unit is still running wrong.
When a loop hunts or a machine trips, the diagnosis starts with a document hunt: the design basis, what changed recently, whether it has happened before. Raven's agents assemble that case file while the deviation is live: design values and operating limits, past occurrences and how they closed, the changes made on the loop recently.
| Context | Record |
|---|---|
| Design range · 40–220 m³/h | DS-0311 · p.2 |
| Same behavior · Mar 2024 | WO-8841 · positioner replaced |
| Upstream reroute · 2 weeks ago | recent change · MOC-2231 |
| Operating limit · min 45 m³/h | operating manual §4 |
Design values with the page they came from.
Half the questions that reach technical services are answered in a document somebody has to find: a design pressure, a trip setting, a spec clause. Raven's agents search the datasheets, design manuals, and specs and return the value with its page, so the answer takes minutes and can be checked.
| Item | Value | Page |
|---|---|---|
| Design pressure | 12.1 barg | DS-0207 · p.2 |
| Hydrotest | 18.2 barg | DS-0207 · p.3 |
| Relief line change · 2023 | see MOC-1984 |
Shift operations and technical services, on the same model.
Permit history per equipment
Every permit raised on an equipment attached to it, one click from the drawing.
Shift handover context
What changed on shift: permits, bypasses, and log entries per unit, assembled for the handover.
Bypasses watched
Open bypasses and overrides flagged as they pass their review date, not found at handover.
Procedures that stay current
SOPs re-checked when a change closes; steps citing a superseded drawing flagged.
Cause and effect, one click away
What trips what, read from the C&E matrices and linked to each loop on the drawing.
Resolved cases kept
Every troubleshooting case file kept with its fix, findable the next time the symptom appears.
How a job starts here.
Most operations teams start with one unit and one week of permits. Send the closed permits with the unit's P&IDs; Raven checks every one and returns the findings: isolations missing from the list, overlapping work in the same area, reinstatements never verified.
Raven checks and flags. Your shift in-charge still authorizes every permit, and your engineers still decide what changes.
What to send: One week of closed permits from one unit, plus that unit's P&IDs.
See Raven on your plant
A demo walks you through the jobs on this page, on your own drawings and permits. Or send one week's closed permits with the unit's P&IDs: we check every one and show you what a full audit would have found.
