Compliance

Process Safety Management: The OSHA Standard That Runs Gas Plants and NGL Sites

Process safety management (PSM) is OSHA's most demanding rule for facilities that handle dangerous chemicals, and the standard that governs gas plants and NGL sites. Issued in 1992 under 29 CFR 1910.119 after the Bhopal disaster and the 1989 Phillips explosion in Pasadena, Texas, it forces a facility to know its hazards, write down how the process runs, and prove workers and contractors can run it safely.

What PSM covers

PSM applies to a process, defined as any activity involving a highly hazardous chemical, including its use, storage, manufacturing, handling, or movement on site. A facility is covered either by having a process involving one of the roughly 130 chemicals listed in Appendix A at or above its threshold quantity, or by having a process with a flammable liquid or gas in quantities of 10,000 pounds or more. That second trigger pulls most of the midstream in: a gas plant, an NGL fractionation train, or a storage terminal can hold that much propane or condensate in a single vessel or an interconnected group, which the standard counts as one process.

Retail facilities, oil and gas well drilling and servicing operations, and normally unoccupied remote facilities are excluded, but those carve-outs cover less ground than people assume. A well site with a heater treater and stock tanks is usually outside PSM; the gas plant a few miles down the line is not.

The 14 program elements

The standard is built as a set of program elements, and OSHA treats every one as a requirement: employee participation; process safety information; process hazard analysis (PHA); operating procedures; training; contractors; pre-startup safety review; mechanical integrity; hot work permits; management of change (MOC); incident investigation; emergency planning and response; compliance audits; and trade secrets.

Process safety information is the written record of the chemicals, technology, and equipment, including the design basis for vessels and relief systems. The PHA is the structured study of what can go wrong, using methods like HAZOP or what-if, with findings tracked as action items. Operating procedures must cover startup, normal operation, shutdown, and emergency conditions. Every employee in the process must be trained in the procedures for their job before working alone, with refresher training at least every three years.

Mechanical integrity turns maintenance into compliance: written procedures for pressure vessels, piping, relief systems, and emergency shutdown systems, with inspection and testing on a schedule. MOC is the gatekeeper: any change to process chemicals, technology, equipment, or procedures gets a written hazard review before it is made. Hot work on or near a covered process requires a permit before the first spark. Incident investigations begin within 48 hours of any incident that could have caused a release, and findings become action items with owners and deadlines. Emergency planning covers the site emergency action plan plus procedures for small releases, tied to the emergency action and fire prevention plans rule. Audits run at least every three years. Trade secrets cannot be used to withhold information employees need to work safely.

Where oilfield operations fit

The trigger questions for an oil and gas facility are simple: what is in the process, how much of it, and could a release travel between vessels? Gas processing and NGL handling usually answer yes. A plant receiving raw wellhead gas runs separators, amine and glycol units, and compression at flammable gas inventories that cross 10,000 pounds many times over; fractionation and storage stack the same way. Refineries have operated under PSM for decades; midstream operators now live in the same enforcement world.

Service companies get pulled in as contractors, which is where the standard touches most oilfield workers. The host employer must evaluate a contractor's safety performance, tell the contractor about the fire, explosion, and toxicity hazards on site, and require and verify that contractor employees have been trained. The contractor must train its own employees in the procedures relevant to the job, document that training, and report hazards found during the work. A service crew doing turnaround or tank cleaning at a gas plant carries real obligations: training records that match the job, written procedures, and the same respect for the host's permits as the host's own crews. Well drilling and servicing are outside PSM, but that exemption does not travel: the moment the same company steps onto a covered plant site, the standard applies. H2S is the one hazard that follows crews from the wellhead to the plant; see the H2S contingency planning guide.

Keeping the program alive

PSM programs fail in the years between audits, not at the audit. The three habits that keep a program real are revalidation, MOC discipline, and contractor training. PHAs must be updated and revalidated at least every five years, and sooner if a change or incident calls the old study into question. MOC is the element that, if skipped, quietly walks a facility past its own assumptions: a different catalyst, a larger pump, a bypass line added for the season, each is a change to a covered process needing written review before it is made. Permit to work systems are the daily control on the same idea.

Contractor training is where most oilfield gaps show up. Paper verification only holds up if the contractor's records match the people on site and the host's hazard information reaches the crew doing the work. Lockout and tagout on process equipment is a common audit finding, because the lockout/tagout program must line up with the unit's isolation points and the host's procedures.

What an audit looks like

Compliance audits run at least every three years, led by at least one person who understands the process, with a written report, a written response, and the two most recent reports kept on file. In practice the auditor walks the unit, picks elements, and asks for records: the PHA and its action items, training files that match the people on site, MOC records that line up with the equipment in the field, mechanical integrity records that match the equipment tags, and incident investigations closed with follow-up action items. Sites that come through clean are the ones where the permit, the procedure, and the field are the same thing; see the hot work and welding permits guide.

Keep the program where the work runs. Management of change requests, permit approvals, training records, and audit findings live in software like OpsFlo, which tracks tickets, dispatch, approvals, timesheets, and documents, so the version in the field is the version on record.

Sources and further reading

Want this applied to your field operation?

OpsFlo turns tickets, dispatch and approvals into one clean billing flow.

Book a working session