Industries / Industrial equipment and services / Industrial services / Turnaround management
Startup
Startup brings the unit back from cold, empty and open to full running, after a check that the work is finished, blinds are out and the people not needed have left.
4
Milestones achieved, from 1992 to 2010.
0
To watch for: announced, not yet confirmed outside.
1
Open deliverables. Nobody has shipped them.
The road
AchievedWatch forOpen
Achieved
1992
The review before startup
OSHA's 1992 process safety standard requires a pre-startup safety review (PSSR) before hazardous chemicals are let into a new process, or into a modified one when the change alters its process safety information. The review confirms that construction matches the design, procedures are in place, hazards were analysed and workers trained. A restart after a like-for-like turnaround is not covered, so plants that review those restarts do so by their own policy.
Credit
OSHA
2005
Restart with known faults
BP's Texas City refinery restarted its isomerization unit on 23 March 2005 after a month-long turnaround. BP's own policy called for a PSSR after every turnaround, but none was done. The tower's level transmitter and sight glass had been reported broken, and supervisors put off the repair because the schedule had too little time. The tower overfilled, and explosions and fires killed 15 people and injured 180.
LessonA repair cut to save turnaround time can come back as a startup hazard.
Credit
CSB investigation, report March 2007
2008
A new control system untested
On 28 August 2008 the methomyl unit at Bayer CropScience in Institute, West Virginia, was restarting after a long outage in which its control system was replaced and a vessel renewed. A runaway reaction burst a 4,500-gallon vessel, two workers died, and more than 40,000 residents were told to shelter in place. The CSB found that Bayer did not apply its pre-startup review to the control system project, equipment was not tested and calibrated, and operators used an unapproved procedure without the new system's steps.
LessonA startup after a turnaround that changed the controls is a first startup.
Credit
CSB investigation, report January 2011
2010
Too many people at a restart
On 2 April 2010 seven Tesoro workers were near heat exchangers being put back in service after cleaning at its Anacortes, Washington, refinery when a neighbouring exchanger, cracked by high-temperature hydrogen attack, ruptured and killed all seven. Leaks and small fires were so common at this restart that extra operators came to stand by with steam lances. The CSB judged the restart to be hazardous non-routine work.
LessonLeaks that happen at every startup are a warning, not a routine, and only the people a startup needs should be near it.
Credit
CSB investigation, report May 2014
Open
01
Check the procedure against changes
A tool that reads a unit's startup procedure and the list of changes made during the turnaround (new instruments, replaced valves, control system edits, deferred repairs) and flags every step the changes affect, for an engineer to review.
The briefCredit · unclaimed
Open 01 · the brief
Check the procedure against changes
The first to publish is credited on this line, and the deliverable moves from Open to Achieved.
What to build
A tool that reads a unit's startup procedure and the list of changes made during the turnaround (new instruments, replaced valves, control system edits, deferred repairs) and flags every step the changes affect, for an engineer to review.
Why it is still open
At Bayer the operators restarted with a procedure that lacked the new control system's steps, and at Texas City a deferred repair was not tied to the restart. The CSB's digest of startup accidents calls for procedures detailed enough to avoid misaligned valves. A search found commercial software that links review checklists to change records, but no tested tool that reads a procedure against the changes.
Built with what exists
An AI model that reads long documents (see the Note "Seven more flagged"); public example procedures and the sequences in CSB reports; Python to score results.
First step
Write one test pair from the Bayer report: the startup steps it describes and the control system changes, with three planted mismatches.
Done looks like
30 test pairs of procedure and change list, each with planted mismatches set by two process engineers who do not see the tool's output. The share of mismatches caught and the number of false flags are published.