HAZOPs, investigations, and audits that start prepared.
An audit means weeks of assembling evidence that should already agree, and the most common finding is an action item nobody closed. Raven's agents keep the evidence connected in the asset information model: MOCs checked against the drawings they should have reached, recommendations tracked to closure, safeguards linked to their basis and test records. Anything unresolved reaches your engineers as a flagged exception.
Investigations that start from evidence.
Incident systems hold the reports; assembling what actually happened is still manual. Raven's agents pull the alarms, permits, work orders, and prior occurrences around a failure into one timeline, so the investigation starts from evidence. Conclusions stay with your team. Reporting, investigation, and CAPA tracking themselves are Raven Incident, a standalone product for HSE teams.
discharge temperature rising on K-401
trip on TAH-4012
permit active on the adjacent line
similar trip, same machine, seal failure
Every recommendation tracked to closure.
The most common audit finding there is: a recommendation nobody closed. Raven's agents read the registers from studies, PHAs, and investigations, link the closure evidence behind each item, and surface the open ones with owners before the audit finds them.
| Recommendation | From | Status |
|---|---|---|
| Remote isolation on P-101A | HAZOP 2023 | closed · evidence linked |
| Revalidate V-201 relief sizing | audit 2024 | open · 14 months |
| Update SOP-118 after reroute | MOC-2231 | no closure evidence |
| Guard on E-210 platform | near-miss | closed |
Every inspection interval, due date, and deficiency, visible.
Mechanical integrity is the most-cited PSM element in audits, and its evidence sits across the EAM, the inspection reports, and the datasheets. Raven's agents build the register: every item with its interval, last and next date, acceptance criteria, and deficiency status. Overdue items, deficiencies without a disposition, and relief valves sitting in no maintenance plan are flagged.
| Item | Next due | Status |
|---|---|---|
| E-210 · vessel internal | 2027-03 | on schedule |
| PSV-201 · relief test | 2026-01 | overdue · 7 months |
| V-201 · shell UT | 2026-11 | deficiency · no disposition |
| PSV-108 · relief | — | in no maintenance plan |
| Line 1103-2 · circuit | 2028-02 | on schedule |
HAZOPs that start prepared.
PHA software tracks the studies; assembling each node's file is still manual. Raven's agents pull the node's drawings, safeguards, operating limits, prior incidents, and open changes into a pre-read, so the workshop spends its time on the hazards, not the paperwork.
| Item | State |
|---|---|
| P&IDs + interlock C&E | attached |
| Operating limits & safeguards | listed |
| Prior incidents on this node | 2 linked |
| Open changes on the node | MOC-2231 still open |
MOC and PSSR closeout, checked against every document the change should have reached.
MOC software routes the approvals; checking that each change actually reached the documents is still manual. Raven's agents check every MOC against the P&IDs, procedures, and records it should have updated, and verify the PSSR checklist before the unit comes back.
| Item | Status |
|---|---|
| MOC-2231 · closed out | verified |
| P&ID 1103 · Rev 7 issued | verified |
| SOP-118 · revision | outstanding |
| TMP-114 · temporary change | past its end date |
The safeguard register, built from the drawings.
Audit and barrier management programmes need one register of the safeguards; building it from the drawings is the manual part. Raven's agents read the relief valves, interlocks, and trips off the P&IDs and cause-and-effect matrices, link each one's sizing basis and test record, and flag the gaps before the audit asks.
| Safeguard | Basis | Test record |
|---|---|---|
| PSV-201 · relief | sizing linked | test 2025 |
| FIC-1102 · interlock | C&E · sheet 4 | in register |
| TAH-4012 · high trip | on the drawing | no test record |
Audit readiness, on the same model.
Inspection due dates watched
The mechanical integrity register's next-due dates tracked as they age; overdue items flagged without waiting for the audit.
Deficiencies to disposition
Failed acceptance criteria without a disposition, and deficiencies without closure evidence, surfaced per item.
MOC propagation checks
Every change checked against the P&IDs, datasheets, procedures, and records it should have reached.
Procedure certification dates
SOP revision and annual-certification dates watched; operating limits and consequence-of-deviation present.
PHA revalidation clock
Each unit's study age against the five-year revalidation clock, with its recommendation register beside it.
Relief design basis per item
A sizing basis present for every pressure-containing item, from the datasheets and the flare study.
PSI currency after each change
P&IDs, datasheets, and studies re-checked for currency when a change closes.
Findings kept as one register
Every finding kept with its source, criterion, owner, and closure evidence.
Temporary changes watched
Temporary changes flagged when they pass their end date, not found at the audit.
How a job starts here.
Most process-safety teams start with one unit and one element. Send the MOC register, the recommendation registers, and the drawings; Raven runs the checks and returns the findings: changes that never reached their documents, recommendations without closure evidence, safeguards without a test record. The same checks are what a regulator visit, an insurer's risk-engineering survey, or a post-incident review asks for.
Your auditor still audits, and your engineers still decide. They start from evidence that is already assembled and cited, not from a document hunt.
What to send: One closed MOC package and the P&IDs, procedures, and datasheets it should have reached.
See Raven on your plant
A demo walks you through the jobs on this page, on your own records. Or send one closed MOC with its drawings: we show you whether the change reached every document it should have.
