Management of Change In Practice
How oil & gas, chemical, nuclear, and utilities operators use VisiumKMS to manage change, close actions, and satisfy OSHA PSM requirements—without shadow systems or spreadsheets
Why Regulators Care About Management of Change
Management of change is not a best practice. For operators subject to OSHA PSM, it is a mandatory program element — and one of the most frequently cited gaps in enforcement actions.
The requirement goes beyond having an MOC procedure on paper. Regulators expect documented evidence that every change was reviewed, approved, and closed before implementation — and that pre-startup safety reviews were completed before startup. When those records don’t exist, or when field teams have been running parallel systems that bypass the formal process, the exposure is significant.
VisiumKMS MOC is designed to close that gap: a configurable system that frontline teams actually use, generating the audit trail that compliance requires.
OSHA PSM (29 CFR 1910.119)
Element (l) of the PSM standard requires a written MOC procedure covering the technical basis for each change, impacts on safety and health, modifications to operating procedures, necessary time period for the change, and authorization requirements. Pre-startup safety review (PSSR) must be completed before startup of modified processes. VisiumKMS MOC is designed to satisfy these requirements out of the box.
EPA RMP (40 CFR Part 68)
Parallel management of change requirements apply to covered facilities under the Risk Management Program. Documentation of the change review process, employee notification, and PSSR completion are required. Repeat deficiencies in MOC programs are a common RMP enforcement trigger.
API RP-750 / API RP-75
API recommended practices for MOC in petroleum and petrochemical facilities define change categorization requirements, cross-functional review expectations, and records retention obligations. VisiumKMS supports configurable change categories and workflow routing by change type.
CCPS Guidelines for Process Safety Management
Center for Chemical Process Safety guidelines define MOC as a core PSM program element, with explicit requirements for change hazard review, pre-startup verification, and documentation of closure. The CCPS framework is widely used as the reference standard for PSM program design in chemical and refining operations.
How It’s Used: Five Scenarios
VisiumKMS Resolution Tracker receives actions automatically from four source workflows. Each has its own compliance requirements, timelines, and closure documentation demands.
1 — Replacing a legacy MOC system that field teams stopped using
The most common reason organizations come to VisiumKMS for MOC is not that they have no system — it’s that the system they have isn’t being used. Aging or inflexible platforms get worked around. Field teams build parallel processes in email and shared drives. A corporate audit surfaces the gap.
VisiumKMS is configured at the site level, not the corporate level. Each facility or business unit sets up its own MOC workflow — the review stages, approval chains, change categories, and PSSR checklists — without IT involvement and without affecting other sites. The result is a system field teams actually use, because it reflects their process.
Corporate leadership gets consolidated visibility across all sites through Risk Intelligence dashboards and a reporting API — without requiring every site to operate identically.
Compliance connection
OSHA PSM § 1910.119(l) requires a written MOC procedure and documented review for each change. Shadow systems and undocumented workarounds are a direct enforcement exposure.
2 — Managing MOC across a global, multi-site operation
Organizations operating across multiple geographies face a specific challenge: the need for local workflow flexibility alongside enterprise-level reporting. A single rigid system imposed from corporate typically fails at the field level. A collection of disconnected local systems produces no useful enterprise data. VisiumKMS handles this through a combination of site-level configurability and a shared reporting layer. Workflows, languages, change categories, and approval chains are configured by business unit. Reporting — MOC volumes, overdue items, PSSR completion rates, items by status — aggregates across all sites in a single view. One global Oil & Gas operator deploying VisiumKMS across the Americas, Asia Pacific, and Middle East and Europe saw MOC volume increase significantly after implementation — not because more changes were happening, but because field teams were using the system instead of avoiding it. |
Compliance connection
Multi-site operators subject to OSHA PSM must demonstrate that MOC procedures are implemented consistently across covered facilities. Enterprise reporting provides the evidence.
3 — Pre-Startup Safety Review (PSSR) enforcement
PSSR is the final gate before a changed process goes live. It confirms that construction and equipment are in accordance with design specifications, that safety, operating, maintenance, and emergency procedures are in place, that training has been completed, and that any new hazards have been addressed.
In practice, PSSR often fails not because teams skip it intentionally, but because there is no hard gate in the system preventing startup before it’s done. Checklists get completed after the fact. Items get marked closed before they are.
VisiumKMS PSSR checklists are embedded directly in the MOC workflow. The system prevents closure — and therefore change implementation — until all checklist items are signed off by the required parties. This is a process control, not an administrative one.
Compliance connection
OSHA PSM § 1910.119(i) requires PSSR completion before startup of new or modified processes. VisiumKMS enforces this as a system gate, not a procedural expectation.
4 — MOC action tracking through to closure
Every MOC generates actions: equipment inspections, procedure updates, training completions, P&ID revisions, temporary change expirations. In most organizations, these actions leave the MOC system the moment the change is approved and land in someone’s email inbox or a spreadsheet. In VisiumKMS, MOC-generated actions route directly into Resolution Tracker. Each action has a named owner, a target date, automated reminders, and an escalation path if it goes overdue. The MOC record stays linked to every action generated from it — so a post-incident investigation can immediately see what actions were assigned, what closed, and what didn’t. |
Compliance connection
OSHA PSM requires that MOC-related actions — procedure updates, training, equipment modifications — be completed and documented. Automated routing and tracking provides the evidence.
5 — Temporary and emergency change management
Temporary changes are among the highest-risk MOC categories. They are initiated quickly, often under operational pressure, and frequently outlast their authorized duration. Temporary changes that become permanent without going through full MOC review are a recognized process safety risk pattern. VisiumKMS supports configurable temporary change workflows with defined expiration dates and automated notification when a temporary change is approaching its authorized end date. If the change needs to be extended or made permanent, the system initiates the appropriate review process. If it doesn’t, it triggers the return-to-original-condition verification. |
Compliance connection
OSHA PSM explicitly addresses temporary changes, requiring the same MOC rigor as permanent changes. Expired temporary changes that have not been properly closed or extended are a common PSM citation.
Three Areas Where VisiumKMS MOC Pays for Itself
Compliance Risk Reduction
MOC deficiencies are one of the most cited elements in OSHA PSM audits and enforcement actions. The exposure is not just a citation — it is the demonstrated causal chain between an inadequate change management program and a serious incident. Operators using VisiumKMS MOC have used the platform to satisfy the terms of regulatory consent decrees, with compliance reporting generated directly from the system.
Field Adoption
The highest-cost MOC failure mode is a system nobody uses. When field teams find the system too rigid, they build workarounds. Those workarounds create the compliance exposure. VisiumKMS is designed to be configured by the people who use it — site administrators, not IT. When the system reflects the actual process, adoption follows.
Audit Readiness
When a regulator or corporate auditor asks for documentation of a change made 18 months ago — who reviewed it, who approved it, what PSSR items were completed, what actions were generated and closed — the answer is a report, not a records search. Every MOC in VisiumKMS carries a complete, timestamped audit trail from initiation to closure.
Go Deeper
Case Studies
See how industrial operators use VisiumKMS across E&P, Oil & Gas, and process safety-regulated operations.
View Case Studies →
Management of Change Software
See the full MOC module — configurable workflows, PSSR checklists, automated notifications, and audit-ready records.
See the MOC Module →
Management of Change Software Resolution & Action Tracking
MOC is the largest single source of corrective actions in most PSM programs. See how VisiumKMS Resolution Tracker handles end-to-end action closure.
See Reoslution Tracker →
See It in Your Environment
Book a discovery call with a process safety software specialist. We’ll show you how Resolution Tracker maps to your specific workflows, change categories, and PSSR requirements.
Book a Discovery Call →