Process Safety, MOC, Contractors, and Fleet Safety

Technical programs must control interfaces and change

Process safety, management of change, contractor safety, and fleet safety all deal with systems where one decision can create risk far beyond a single task. A valve-material change can ruin chemical compatibility; a temporary contractor can bypass site procedures; a route change can expose drivers to fatigue and weather; a software update can alter alarms or interlocks. ASP questions frequently target these interfaces.

Process Safety Management (PSM), OSHA 29 CFR 1910.119, prevents catastrophic releases, fires, and explosions. It applies to processes containing a listed highly hazardous chemical at or above its threshold quantity, or 10,000 lb or more of a flammable liquid or gas. PSM has 14 required elements; know them as a system:

1. Employee participation
2. Process safety information (PSI)
3. Process hazard analysis (PHA)
4. Operating procedures
5. Training
6. Contractors
7. Pre-startup safety review (PSSR)
8. Mechanical integrity
9. Hot work permits
10. Management of change (MOC)
11. Incident investigation
12. Emergency planning and response
13. Compliance audits
14. Trade secrets

The PHA must be revalidated at least every five years, and incident investigations begin promptly (OSHA expects within 48 hours).

Management of change (MOC) is the formal review of any proposed change before implementation. A replacement-in-kind (identical spec) is generally exempt, but anything else - new chemical, different concentration, new pump or control logic, procedure revision, staffing change, software update, or temporary operation - must go through MOC.

A strong MOC defines the change, technical basis, hazards, affected documents, training needs, approvals, and a pre-startup safety review before the process restarts - not after a near miss proves the review was needed.

Contractor safety is far more than a badge. Host and contractor must exchange hazard information both ways: the host shares process hazards, emergency signals, LOTO expectations, and permit rules; the contractor shares its methods, chemicals, and equipment hazards. Under PSM the host must inform contractors of fire/explosion hazards and evaluate their safety performance during selection. Contractors are experts in their trade but unfamiliar with site process hazards.

Fleet safety deserves emphasis because motor vehicle crashes are a leading cause of work-related death in the United States. A fleet program controls driver qualification, vehicle inspection and maintenance, seat-belt use, route planning, backing (a frequent damage source), fatigue, distraction, impairment, weather, and load securement. Use leading indicators (completed inspections, coaching, telematics alerts) alongside lagging indicators (crashes, damage). Worked example: frequent backing damage with no injuries is a leading signal; redesign routes and spotter rules now rather than waiting for a serious crash.

PHA methods, EPA RMP, and emerging technology

The process hazard analysis uses recognized methods the exam may name: What-If, What-If/Checklist, HAZOP (Hazard and Operability study) using guide words such as "more," "less," and "no" applied to process parameters, Failure Mode and Effects Analysis (FMEA), fault tree analysis (top-down), and event tree analysis (forward from an initiating event). HAZOP suits complex continuous processes; FMEA suits equipment-by-equipment review. The PHA team must include someone with operating experience on the process.

PSM has a regulatory companion: the EPA Risk Management Program (RMP) under Clean Air Act Section 112(r) addresses the same kinds of highly hazardous chemicals but focuses on offsite consequences to the public and environment, requiring an offsite consequence analysis and a five-year accident history. PSM protects workers inside the fence; RMP protects the community outside it. A facility can be subject to both, and the two programs share data such as the PHA and incident history to avoid duplication.

The pre-startup safety review (PSSR) deserves emphasis because it is the gate between change and operation. Before introducing a highly hazardous chemical to a new or modified process, the PSSR confirms that construction matches design, safety and operating procedures are in place, training is complete, and for modified facilities the MOC requirements have been met and recommendations resolved. Skipping the PSSR is how a well-intentioned change reaches the field with an unreviewed hazard, which is exactly the failure mode ASP scenarios test.

Emerging technologies still require hazard analysis. Sensors, drones, wearables, robotics, automation, and analytics can reduce exposure but introduce reliability, false-alarm, battery, human-machine-interface, cybersecurity, and overreliance issues - and they themselves are changes that should pass through MOC. The ASP mindset is to evaluate the new risk and integrate the tool into the management system rather than assume technology is inherently safer.

Use this integration checklist:

• Identify whether the activity is a change, a contractor interface, or a high-consequence process hazard.
• Run the PHA (choosing What-If, HAZOP, or FMEA), MOC, or contractor evaluation before work or startup.
• Update procedures, drawings, training, permits, and emergency plans.
• Coordinate roles and two-way communication between parties.
• Conduct a pre-startup safety review before release to operation.
• Monitor performance and close corrective actions.