1.5 Management of Change (MOC) Processes

The Imperative of Management of Change

Organizations are dynamic entities; they constantly adapt to new technologies, market demands, and personnel shifts. While change is necessary for growth, poorly managed change is a leading cause of catastrophic incidents in industry. The Flixborough disaster in 1974, where a temporary bypass pipe failed and caused a massive explosion, is a classic example of an ad-hoc modification bypassing engineering review. Similarly, the BP Texas City explosion highlighted the dangers of organizational changes, where staffing cuts and loss of experienced personnel contributed to the disaster.

Management of Change (MOC) is a systematic, proactive process designed to ensure that safety, health, and environmental risks are identified and controlled when modifications are made to facilities, processes, materials, or personnel. For the Safety Management Professional (SMP), establishing a rigorous MOC process is a cornerstone of system safety.

Triggers for an MOC (And What is Exempt)

An effective SMS must clearly define what constitutes a 'change' that triggers the MOC process. Just as important is defining what does not trigger the process to prevent the system from becoming bogged down.

Replacement in Kind (RIK): This is typically exempt from MOC. RIK means replacing a component with an identical one, or one that falls within the original design specifications. For example, replacing a failed 50-horsepower motor with another 50-horsepower motor of the same make and model does not require an MOC. However, replacing it with a 75-horsepower motor does.

Triggers broadly fall into three categories:

1. Physical/Operational Changes:

   • Installing new equipment, bypassing safety interlocks, or modifying existing machinery.
   • Changing process parameters (e.g., increasing temperature, pressure, or line speed).
   • Introducing a new chemical or raw material.
   • Altering facility layouts or emergency escape routes.

2. Organizational/Administrative Changes:

   • Changes in key personnel or reductions in staffing levels.
   • Modifying standard operating procedures (SOPs) or maintenance schedules.
   • Changes in shift structures affecting fatigue management.

3. Software/IT Changes:

   • Modifying Programmable Logic Controllers (PLCs) or SCADA systems.
   • Software updates that control emergency shutdown systems.

The MOC Workflow and Roles

A robust MOC process follows a structured workflow to ensure comprehensive review and authorization.

Step 1: Initiation and Description The Initiator (often an engineer or operations supervisor) submits an MOC request detailing what the change is, why it is needed, and the technical basis for the proposed modification.

Step 2: Risk Assessment and Multidisciplinary Review This is the most critical step. A cross-functional team of Reviewers (including safety, engineering, operations, and maintenance) reviews the proposal to identify potential new hazards or impacts on existing hazard controls. They ask questions like: Will this new chemical react with existing processes? Does this layout change block a fire extinguisher? Does this software update affect emergency shutdown protocols?

Step 3: Action Plan and Approval Based on the risk assessment, an action plan is developed. This plan outlines the necessary steps to implement the change safely, such as updating drawings, modifying operating procedures, and conducting employee training. The MOC is then formally approved by designated Approvers (usually plant management or engineering leads) before any physical work begins.

Step 4: Implementation and Training The physical change is executed. Concurrently, affected employees must be informed of the change and trained on new procedures or hazards before they interact with the modified system.

Step 5: Pre-Startup Safety Review (PSSR) Before the modified system is turned on or handed over to operations, a PSSR is conducted. This final check verifies that:

• Construction and equipment are in accordance with design specifications.
• Safety, operating, maintenance, and emergency procedures are in place and adequate.
• Training of affected employees has been completed.
• The MOC action plan has been fully executed.

Step 6: Closure Once the PSSR is passed and the system is operational, the MOC is formally closed out, ensuring all documentation (e.g., Process Safety Information, P&IDs) is permanently updated.

Common Pitfalls and Emergency MOCs

Despite having written procedures, organizations often struggle with MOC implementation. Common pitfalls the SMP must guard against include:

• Bypassing the Process for 'Urgent' Fixes: Operations may attempt to bypass MOC for temporary fixes or workarounds during night shifts or weekends to maintain production. To handle this, a facility must have an Emergency MOC procedure. This allows for a rapid, streamlined review by an on-call team to authorize a temporary fix, with a requirement to perform a full MOC review on the next regular business day.
• Failing to Recognize Organizational Change: While companies are usually good at assessing physical equipment changes, they frequently fail to apply MOC when cutting staff, changing shift patterns, or promoting inexperienced personnel to critical roles.
• Inadequate PSSR: Treating the PSSR as a paperwork exercise rather than a rigorous physical inspection of the newly modified system.