Process safety (PSM)

The PSM module keeps a fourteen-element compliance register for each covered process — a highly hazardous chemical at or above its threshold quantity — per OSHA 29 CFR 1910.119. Each process shows a rolling compliance percentage and a count of open gaps.

Register a covered process

Go to Process safety and fill in the row at the top: site, process name, chemical (autocompleted from your SDS library), and location.
Click Register process. A card appears listing all fourteen PSM elements with their 1910.119 paragraph references.

Assess each element

Set each element's status from the dropdown (compliant, gap, and so on). Rows marked as a gap turn red; compliant rows turn green, and the card header updates the compliance percentage and gap count as you go.
Use the notes field on each row for evidence or gap notes — edits save when you leave the field.
Every status or notes save stamps the element's reviewed date, shown under the notes. That date drives the recurrence escalations below, so assess an element when you actually review it.

Close the gaps

For any element flagged as a gap, click CAPA to raise a corrective action tied to that element and process. Once one exists, its badge replaces the button so you can jump straight to it — see CAPA.
Export register CSV downloads the fourteen-element register — one row per element per covered process — from api/psm/register.csv.

Management of change is program-backed (1910.119(l))

The Management of Change element isn't just a status you set — it reflects the real change activity governing the process, read live from the MOC module:

Under the element's notes you'll see the program summary: how many change requests are open, how many are implemented but not yet closed out, and how many temporary changes are past their expiry (which flags the element's row red — an overdue temporary change is a live (l) gap).
View changes opens the MOC register filtered to this process; + New change starts a change request already linked to this covered process (and its site).
A change raised this way carries the covered-process name through the MOC register, the MOC log CSV, and the overdue-temporary escalation — so a lingering temporary change names the process it belongs to.

A process with no linked changes yet simply shows "No change requests linked to this process yet" — assess the element and start changes from here to build the program record.

Deactivate a process

When a process is dismantled or falls below its threshold quantity, click Deactivate on the card header. The record and its element history stay visible, but the process drops out of the review escalations below.

What happens automatically

Three elements carry hard regulatory recurrences, measured from each element's last reviewed date:

Process hazard analysis — revalidation every 5 years (1910.119(e)(6)).
Compliance audits — every 3 years (1910.119(o)).
Operating procedures — certification annually (1910.119(f)(3)).

When a recurrence lapses on an active process, the escalation sweep raises an overdue notification to the Safety Team naming the element, the process, and when the recurrence lapsed.

An element you've assessed as a gap also escalates on its own — "PSM element gap: (element) — (process)" — a live gap in a covered process shouldn't sit as a silent dashboard count. When the same element is already being escalated for an overdue recurrence review, the gap is deduped against it so the Safety Team isn't notified twice for one element. An element that has never been assessed still doesn't escalate — it already shows as an open item on the register.

Management of change — management-of-change is a core PSM element
Incidents — incident investigation element of PSM
Hot work permits — hot-work permitting within covered processes
Lockout/tagout (LOTO) — energy-control procedures for process equipment
Root cause analysis — root-cause analysis for PSM incident findings