Tests each step against closed changes, the drawing and the equipment list.
- Never says a procedure is right
- Never places a hold
Operating procedure management software that walks each procedure on the unit drawing, finds the steps a closed change left behind, and backs the yearly signature with what the superintendent opened.
Follow one restart procedure from 23:40 to 09:27 ↓A change closes with an action to update procedures, and the update list names the one the engineer remembered. Three more startup and shift procedures still tell the crew to open the old valve. The crews work around the wrong line, stop mentioning it, and after a while stop trusting the book.
At year end the superintendent signs that hundreds of procedures are current and accurate. Nobody can read them all, so the signature rests on a list. Paper copies in the field shelters stay on the revision before last.
Built forProcedure ownersUnit superintendentsShift operatorsProcess safety engineersProcess safety auditors
A closed change can leave an old valve in a procedure, and the yearly signature certifies it as current anyway.
Compared by hand today
Built-in controls
The yearly signature says what was read, what was only tested and what is not current.
An outage cut a corroded dead leg and its hand valve out of the reformer stabilizer's pump recycle. The change closed, and the restart procedure still names the old valve. Here is how it gets fixed, on the working screens of the unit.
demoThe refinery, its units, tags and people, and every count on these screens are sample data.
Each night the agents test every procedure. For the stabilizer restart they read the 34 steps and 50 tag mentions, look each tag up on the current drawing and in the maintenance system, and read the closed changes on that drawing. 49 tags are found. HV-2218 is not. The shift log reader adds that 5 restarts in 14 months each name HV-2231.
She presses walk it, and each valve, pump and line the steps name lights up on the drawing in step order. At step 17 it stops: the procedure says open HV-2218, which shows as a dashed ghost where the book thinks it is, while the logged valve shows amber. Four sources sit under the drawing, each with its page.
One click opens the log line behind the count. An operator on C Crew wrote at a restart that the procedure says HV-2218, that they used HV-2231 and opened HV-2226 first, as they all do, and that the shift supervisor was told. The agents quote the logs; a log is evidence of practice, and proves nothing about whether the practice is right.
The agents' draft swaps one valve name for the other and stops there. That fails the check: on the current drawing the recycle now leaves past HV-2226, so with HV-2226 shut until step 19 the pump starts with no recycle path. The agents say plainly they cannot tell whether moving the tap changes the order. That call is hers.
She rewrites steps 18 and 19 in her words: open HV-2226 slowly before the pump with the reflux line kept shut, then start the pump from the field and confirm at least 160 gpm. Her text is marked not compared, a person must read this. Only the tags are looked up; the meaning goes to two people in her exact words.
He cannot agree until he has opened the whole procedure, the closed change and the drawing, and each opening is recorded. Then he answers the question the agents could not: does moving the recycle tap change the step order? Yes, and this edit answers it: step 18 opens HV-2226 before the pump. A no would block Agree.
The superintendent opens the same three records. The sign button stays off, and the line under it says what is still to open: the engineer's answer. His name goes on exactly what he read, so a review he has not opened does not count. A hold he placed on this procedure stays in place until the revision is live.
He opens the answer and signs. Rev 7 goes live with steps 17 to 19 in the new order, edited by the owner and signed by the superintendent. The count at the top falls to 647. The paper copy tracker puts 3 copies on the collect list, and the crews have a new revision to read.
For the annual SOP certification on Unit 22, 37 procedures wait to be opened in full: every changed one and every startup, shutdown and emergency procedure, plus a sample of 13 routine ones from a recorded draw nobody who signs chose. 238 are tested by agents and not read by a person, and 46 differ. The certificate says all four.
The unit as the certificate opened, before Rev 7 went live. The superintendent signs only what he read; the rest is listed by what happened to it.
| Procedures on Unit 22 | Count | What the certificate says |
|---|---|---|
| Differ from the plant record | 47 | Not certified; each sits with its owner on a due date |
| Changed this year | 12 | Read in full |
| Startup, shutdown and emergency, unchanged | 12 | Read in full, and kept out of any sample |
| Routine, sampled from a recorded draw | 13 | Read in full; one failure draws 5 more, a second stops the certificate |
| Routine, not drawn | 238 | Tested by the agents; no person read them |
| Total | 322 | Each procedure on exactly one line |
demoSample data, from the working solution. Even when all 13 read clean, about 21% of the routine set could still be wrong at 95% confidence, and the screen says so.
The rest of what owners, operators and auditors see, after Rev 7 went live.
demoSample data, from the working solution.
Each has its own job and its own stop.
Tests each step against closed changes, the drawing and the equipment list.
Quotes the log lines behind each procedure.
Drafts the smallest edit the sources support, or says it cannot.
Lists what changed, the exceptions, each startup, shutdown and emergency procedure, and the routine sample.
Compares numbered copies with current revisions.
Answers record questions and sends any plant question to the superintendent and process safety.
Keeps the trail and builds the exports.
What the agents find is a finding. These calls need a person who opened the record.
Read only, each cited with its page or line.
Operating procedure management keeps written operating procedures matched to the plant as it is today. Here agents test each step against closed changes, the current drawing, the equipment list and the shift logs, and draft an edit for the owner. People edit, review and sign, and the yearly certificate says what was read.
The superintendent reads every changed procedure and every startup, shutdown and emergency procedure in full, and a routine sample from a draw he did not choose. The certificate counts only recorded openings, lists every procedure not read and every one that differs, and a second person countersigns.
The agents read each closed change and look for every procedure that names what it altered, including the ones its update list left off. A procedure the change never reached becomes a difference, assigned to its owner with a due date.
No. They draft the smallest edit the sources support, or say they cannot. The owner edits, process safety reviews safety steps, and the superintendent signs before a revision goes live.
No, and it does not pretend to. It looks up the tags in typed text and refuses a removed or unknown valve. The meaning is marked not compared, and two people must open the record and read the exact words.
The logs are quoted as evidence of practice, and that is all. A different practice can be right, or a change nobody managed, so it goes to the owner, and on a safety step to process safety and the superintendent.
Which steps are held, who placed each hold and who to call, the paper copies to collect, new revisions to read, and a place to report what the crew really does, in their own words.
Tables tied to their surveys and read as an outsider would, before they go public.
1-min demoTailings Dam SafetyFindings pinned to their place on the dike, and the ones that keep coming back raised by name.
1-min demoMine Closure Security FilingThe security sum tested before filing, with each input tied to its page.
1-min demoWe will walk your procedures on your own drawings and show you where the book and the plant disagree.