EPA RMP and OSHA PSM do not share one mechanical-integrity scope
EPA’s Risk Management Program and OSHA’s Process Safety Management standard address chemical-accident prevention under different authorities, scopes, and records. A shared equipment list or CMMS plan cannot decide which program applies or merge their accountable duties.
Editorial figure by Maintenance Operations Ledger. Source context: EPA Risk Management Program.
Establish each program’s applicability separately
EPA identifies RMP as a Clean Air Act section 112(r) program for chemical-accident prevention at facilities using extremely hazardous substances and says covered facilities develop a Risk Management Plan. OSHA identifies PSM as an occupational safety and health standard for preventing or minimizing catastrophic releases from covered processes. Those starting points concern different statutory authorities, regulated populations, applicability tests, implementing bodies, and required records even where the same facility or equipment may be relevant to both.
A maintenance system should not decide scope from the words chemical plant, covered asset, or mechanical integrity. The controlled record needs the legal entity, facility, process, chemical, quantity and threshold basis, activity, exclusion analysis, program level where relevant, jurisdiction, source version, reviewer, decision date, and trigger for reassessment. Shared master data can support both reviews while retaining which authority and accountable owner made each decision.
Map OSHA mechanical-integrity duties to exact equipment
OSHA paragraph 1910.119(j) applies its mechanical-integrity provisions to listed process equipment: pressure vessels and storage tanks; piping and piping components; relief and vent systems; emergency shutdown systems; controls including monitoring devices, sensors, alarms, and interlocks; and pumps. The standard calls for written procedures, training for employees performing maintenance, inspections and tests, documented results, correction of deficiencies outside acceptable limits, and quality-assurance checks within the covered process.
That structure requires more than recurring work orders. Each record should identify the covered process and equipment, unique asset, governing process-safety information, inspection or test method, engineering-practice basis, frequency basis, prior operating experience, person performing the work, date, result, acceptable limit, deficiency disposition, and link to safe return or continued operation. A completed or closed status does not prove that the required inspection occurred or that equipment was within acceptable limits.
Keep RMP planning and submission records in their own chain
EPA’s public program page says regulated facilities revise and resubmit RMPs every five years and provides separate program guidance, submission, public-information, inspection, and General Duty Clause resources. The Risk Management Plan is not the same record as an OSHA inspection result, maintenance procedure, work order, or compliance-audit finding. Systems can link those artifacts without treating one submission as proof that every accident-prevention or maintenance duty was performed effectively.
A useful crosswalk distinguishes the EPA and OSHA requirement, scope owner, facility and process population, source record, review cycle, submission or retention rule, exception, and evidence repository. It should expose equipment or processes appearing in one population but not the other and explain why. Copying one equipment hierarchy into both programs without a governed scope decision can create false completeness and hide obligations, exclusions, or record differences.
Preserve current rule status and unresolved site facts
EPA’s RMP page, last updated August 3, 2026, notes a February 24 proposed rule whose comment period closed May 11. A proposal is not a final revision. Teams should retain the currently controlling program record, the proposal and its status, any later final action, effective and compliance dates, and the assessed impact on their facilities rather than updating CMMS fields from a headline or anticipated change.
Maintenance Operations Ledger treats EPA and OSHA pages as official sources for their respective programs. They do not establish whether a reader’s facility or process is covered, which chemicals and thresholds apply, whether an exclusion is available, what an acceptable equipment limit is, whether a maintenance action is safe, or whether either program has been satisfied. Those questions require current controlling authority, complete site facts, and qualified legal, process-safety, engineering, operations, and maintenance judgment.
Enterprise buyer test
Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.
A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.
What we will watch next
Maintenance Operations Ledger will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.