Study guide
14.2 Management of Change (MOC) Procedures & Software Modification Controls
ISA CAP Certified Automation Professional Exam
Track your progress as you read
Finished sections get a check mark.
1 Introduction
About the ISA CAP Exam (2024 Content Outline)
2 Chapter 1: Feasibility Study — Scoping & Justification
1.1 Business Needs, Scope Definition & Operational Strategies 1.2 Automation Opportunity Assessment & Technology Screening 1.3 Benefit-to-Cost Analysis, Payback & Financial Metrics (NPV, ROI, IRR)
3 Chapter 2: Feasibility Study — Technical Analysis & Risk
2.1 Technical Feasibility Studies & Automation Architecture Alternatives 2.2 Preliminary Risk Assessment, Process Safety & Environmental Constraints 2.3 Preliminary Project Cost Estimating, Scheduling & Resource Requirements
4 Chapter 3: Definition — Requirements & Specifications
3.1 User Requirements Specification (URS) & Stakeholder Analysis 3.2 Functional Requirements Specification (FRS) & Functional Safety Requirements 3.3 Process & Control Strategy Determination (Continuous, Discrete, Batch & Hybrid) 3.4 Automation Boundaries, High-Level System Architecture & Scope Definition
5 Chapter 4: Definition — Safety, Cybersecurity & Cost Baseline
4.1 Regulatory Compliance & Safety Criteria (OSHA PSM, EPA RMP, 21 CFR Part 11) 4.2 Preliminary Security Architecture & Industrial Cyber Threat Assessment (ISA/IEC 62443) 4.3 Baseline Cost Estimating, Financial Justification & Project Viability Analysis
6 Chapter 5: System Design — Control Architecture, Field Devices & Motion
5.1 Control System Architecture Selection: PLC, DCS, SCADA & Hybrid Systems 5.2 Process Instrumentation, Sensor Selection & Analytical Measurement 5.3 Final Control Elements: Control Valves, Actuators & Variable Frequency Drives (VFDs) 5.4 Hazardous Location Classification, Electrical Safety & Enclosures (NEC, NFPA, ATEX/IECEx) 5.5 Discrete Devices, Motor Control, Motion Control & Mechatronics
7 Chapter 6: System Design — Safety Systems & Cybersecurity
6.1 Safety Instrumented Systems (SIS) & Safety Lifecycle (ISA-84 / IEC 61511 / IEC 61508) 6.2 SIL Determination, Verification & Layer of Protection Analysis (LOPA) 6.3 Industrial Cybersecurity by Design: Zones, Conduits & Security Levels (ISA/IEC 62443) 6.4 Hardware/Software Specifications, Procurement & Detailed Engineering Packages
8 Chapter 7: System Design — Networks, Continuous Control & Standards
7.1 Industrial Fieldbuses & Digital Communications (HART, Fieldbus, Profibus, Modbus) 7.2 Industrial Ethernet & Open Protocols (EtherNet/IP, PROFINET, OPC UA, MQTT) 7.3 Continuous Control Strategies: Feedback, Feedforward, Cascade, Ratio & Advanced PID 7.4 Batch Control Architecture, Recipes & Procedural Standards (ISA-88 / S88)
9 Chapter 8: System Design — HMI, Alarms, Enterprise Integration & Data
8.1 Human-Machine Interface (HMI) & High-Performance Graphics Design (ISA-101) 8.2 Alarm Management Lifecycle, Rationalization & Performance (ISA-18.2) 8.3 Enterprise Integration & Manufacturing Operations Management (ISA-95 / S95) 8.4 Data Flow Analysis, Historians, Relational Databases & Reporting
10 Chapter 9: Development — Software Logic & Programming
9.1 IEC 61131-3 Programming Languages: LD, FBD, ST, SFC and Legacy IL 9.2 Discrete Control Logic, Sequencing, State Machines & Interlock Implementation 9.3 Safety Logic Development, Burner Management & Interlock Verification 9.4 Software Configuration Management, Version Control & Change Tracking
11 Chapter 10: Development — Simulation, Tuning & FAT
10.1 Loop Tuning Methodologies & Dynamic Process Response (Ziegler-Nichols, Cohen-Coon, Lambda) 10.2 Simulation, Emulation & Hardware-in-the-Loop (HIL) Verification 10.3 Factory Acceptance Testing (FAT): Planning, Test Protocols, Execution & Punch Lists 10.4 Software Quality Assurance, Code Review & Validation Documentation
12 Chapter 11: Deployment — Installation, Wiring & Pre-Commissioning
11.1 Field Installation Oversight, Wiring Practices, Grounding & Shielding 11.2 Pre-Commissioning Checkout: Cold Loop Checks, Hot Loop Checks & Calibration 11.3 Site Safety Protocols, Lockout/Tagout (LOTO) & Permitting during Deployment 11.4 Installation Punch List Management & Defect Resolution
13 Chapter 12: Deployment — Commissioning, SAT & Turnover
12.1 Site Acceptance Testing (SAT): Execution, Environmental Validation & Variance Management 12.2 Commissioning & Startup Sequencing (Cold/Hot Commissioning & Fluid Runs) 12.3 Cutover Strategies, Legacy System Migration & Contingency Fallback 12.4 System Turnover, Operator/Maintenance Training Delivery & As-Built Documentation
14 Chapter 13: Operation & Maintenance — Diagnostics, Reliability & Training
13.1 Maintenance Strategies: Reactive, Preventive, Predictive & Reliability-Centered (RCM) 13.2 Troubleshooting Methodologies & Root Cause Failure Analysis (RCFA) 13.3 Calibration Management, Proof Testing & SIS Periodic Validation (IEC 61511) 13.4 Spare Parts Strategy, Critical Spares Analysis & Obsolescence Management 13.5 Asset Performance Management (APM) & Overall Equipment Effectiveness (OEE) Tracking 13.6 Training Needs Analysis, Training Delivery & Competency for Automated Systems
15 Chapter 14: Operation & Maintenance — Optimization, MOC, Security & Decommissioning
14.1 Loop Auditing, Process Variability Analysis & Control Optimization 14.2 Management of Change (MOC) Procedures & Software Modification Controls 14.3 Backup, Disaster Recovery & Disaster Recovery Testing for Industrial Systems 14.4 Operational Cybersecurity: Patch Management, Vulnerability Monitoring & Incident Response 14.5 Decommissioning Planning, Asset Retirement & Environmental Disposition
14.2 Management of Change (MOC) Procedures & Software Modification Controls
Key Takeaways Explain This Topic AI
OSHA 29 CFR 1910.119(l) mandates formal Management of Change (MOC) procedures for all modifications to process chemicals, technology, equipment, and facilities, explicitly excluding true 'Replacements in Kind' (RIK).
In automation systems, an RIK requires an exact match in form, fit, functional behavior, safety rating, and certified firmware revision; installing an updated model revision, altered range, or modified logic rung constitutes a formal change.
The automation MOC lifecycle enforces a rigorous 7-step progression: Request, Technical & Safety Evaluation (PHA/HAZOP/SIL), Multi-Disciplinary Approval, Sandbox Simulation Testing, Field Implementation, Pre-Startup Safety Review (PSSR), and As-Built Documentation Closeout.
Emergency MOC (eMOC) protocols allow expedited verbal or single-point authorization to avert imminent safety or environmental hazards, but mandate strict operational time boundaries and complete retroactive technical reviews within defined organizational windows.
Software modification controls require technical safeguards including role-based access permissions, physical controller key-switch interlocks (RUN mode), cryptographic checksum verification, and auditable electronic change logs.
Last updated: October 2026
Management of Change (MOC) Procedures & Software Modification Controls
Industrial automation systems are dynamic environments. Over the multi-decade lifespan of a chemical plant, refinery, or manufacturing facility, control engineers routinely modify PLC logic rungs, reconfigure alarm trip points, adjust PID tuning constants, replace obsolete field instruments, and update workstation operating systems. If executed in an ad-hoc, undocumented manner, seemingly innocuous modifications can defeat critical safety interlocks, introduce latent software bugs, cause catastrophic environmental releases, or lead to fatal industrial explosions.
Formal Management of Change (MOC) governance is both an engineering discipline and a legal requirement under OSHA 29 CFR 1910.119(l) (Process Safety Management of Highly Hazardous Chemicals), and it is also required by ANSI/ISA-84.00.01 / IEC 61511 (Functional Safety: Safety Instrumented Systems for the Process Industry Sector).
Regulatory Foundation & Scope of Automation MOC
Under OSHA 1910.119(l)(1), the employer must establish and implement written procedures to manage changes (except for "replacements in kind") to process chemicals, technology, equipment, and procedures, as well as changes to facilities that affect a covered process. OSHA 1910.119(l) STATUTORY CRITERIA FOR ANY CHANGE:
- 1. The technical basis for the proposed change
- 2. Impact of change on safety and health
- 3. Modifications to operating procedures
- 4. Necessary time period for the change (temporary vs. permanent)
- 5. Authorization requirements for the proposed change
- Replacement in Kind (RIK) vs. Change
The most critical regulatory distinction an automation professional must navigate is between a Replacement in Kind (RIK) and a Change .
Replacement in Kind (RIK): An exchange of equipment or software that satisfies the design specifications of the existing item in every operational and technical dimension. An RIK does not alter the process chemistry, operating envelope, electrical safety rating, mechanical strength, or control behavior.
Change: Any modification that departs from original design specifications, alters control philosophy, changes operating boundaries, or introduces new hardware/software behavior.
Automation Maintenance Activity Classification Technical Rationale
Replacing a failed 4–20 mA pressure transmitter with an identical make, model, materials of construction, and factory calibrated span (e.g., 0 − 100 psig 0-100\text{ psig} 0 − 100 psig ) Replacement in Kind (RIK) Identical form, fit, function, materials, and measurement scaling. Standard work order applies.
Replacing an obsolete pressure transmitter with the manufacturer's "next generation" smart transmitter model CHANGE (MOC Required) New model may have different damping constants, internal diagnostic response times, HART revisions, or firmware behavior.
Changing a temperature transmitter calibrated span from 0 − 200 ∘ C 0-200^\circ\text{C} 0 − 20 0 ∘ C to 0 − 300 ∘ C 0-300^\circ\text{C} 0 − 30 0 ∘ C on an existing sensor CHANGE (MOC Required) Changes analog input scaling in the DCS, modifying the engineering units, alarm trip calculations, and rate-of-change sensitivities.
Adjusting an alarm setpoint within documented, pre-approved Safe Operating Limits (SOL) defined in the Alarm Philosophy Administrative Procedure If pre-rationalized per ISA-18.2, documented operator adjustments within allowable bounds do not require formal MOC.
Adjusting a Safety Instrumented Function (SIF) trip setpoint or modifying an interlock timer preset CHANGE (MOC Required) Directly impacts the Safety Integrity Level (SIL) verification calculations and Layer of Protection Analysis (LOPA).
Flashing a minor firmware patch to a PLC Ethernet communication coprocessor CHANGE (MOC Required) Firmware updates can alter network stack behavior, protocol timing, or port vulnerabilities.
Caution
Never classify an automation component swap as a Replacement in Kind simply because the device fits onto the same DIN rail or conduit connection. If the firmware revision, wetted diaphragm metallurgy, response time, or device description (DD/EDDL) differs from the approved engineering specification, it is legally a Change and requires formal MOC processing.
The 7-Step Automation MOC Procedure
To ensure that modifications are thoroughly evaluated, tested, and documented, the engineering organization must execute a structured 7-step MOC lifecycle. +-------------------------------------------------------------------------+
- | THE 7-STEP AUTOMATION MOC LIFECYCLE |
- | |
- | [ STEP 1: INITIATION & SCOPE DEFINITION ] |
- | - Document technical justification, draft proposed logic/hardware |
- | | |
- | v |
- | [ STEP 2: TECHNICAL & SAFETY EVALUATION ] |
- | - PHA revalidation (HAZOP/What-If), SIL verification impact, LOPA |
- | | |
- | v |
- | [ STEP 3: MULTI-DISCIPLINARY APPROVAL ] |
- | - Sign-offs: Process, Safety, Operations, Automation, Maintenance |
- | | |
- | v |
- | [ STEP 4: PRE-IMPLEMENTATION TESTING & SIMULATION ] |
- | - Sandbox compilation, peer code review, emulation, rollback plan |
- | | |
- | v |
- | [ STEP 5: FIELD IMPLEMENTATION & VERIFICATION ] |
- | - Scheduled change window, controller download, online loop stroke |
- | | |
- | v |
- | [ STEP 6: PRE-STARTUP SAFETY REVIEW (PSSR) ] |
- | - Field inspection, operator training sign-off, safety interlock check|
- | | |
- | v |
- | [ STEP 7: DOCUMENTATION CLOSEOUT & AS-BUILT UPDATES ] |
- | - Update P&IDs, loop sheets, C&E matrices, baseline software vault |
- +-------------------------------------------------------------------------+
- Step 1: Initiation and Scope Definition
The initiator submits an electronic MOC request documenting:
Problem statement and engineering justification.
Classification: Permanent, Temporary (with mandatory expiration date), or Emergency.
Detailed description of proposed change (e.g., "Modify distillation column overhead reflux ratio calculation from volumetric to mass basis").
Proposed implementation schedule and rollback/contingency plan.
Step 2: Technical Review & Safety Evaluation
A multidisciplinary review panel examines the proposed change. For automation changes, this step must evaluate:
Process Hazard Analysis (PHA) Impact: Does the change introduce new operational hazards? Does it require revalidating a HAZOP node?
Functional Safety & SIL Verification: If an interlock, SIS sensor, logic solver, or final element is modified, does the change compromise the target Safety Integrity Level (SIL)? Proof test intervals and Mean Time to Fail Spurious ( M T T F spurious MTTF_{\text{spurious}} MTT F spurious ) must be recalculated.
Alarm Rationalization: Does the change impact alarm priorities, flooding potential, or operator response times per ISA-18.2 ?
Human Factors: Does the change alter HMI faceplate navigation, color coding, or operational display dynamics per ISA-101 ?
Step 3: Multi-Disciplinary Approval
Before a single wire is moved or a line of code downloaded, formal digital signatures are mandatory from all designated stakeholders: Process Engineering, Operations Superintendent, Process Safety Manager, Maintenance Lead, and Lead Automation Engineer.
Step 4: Pre-Implementation Testing & Off-Line Simulation
Application software must never be compiled and debugged directly on a live industrial controller during manufacturing operations. The automation engineer must test modifications in an offline engineering environment:
Sandbox Emulation: Load modified logic into a software simulator (e.g., FactoryTalk Logix Echo, PLCSIM Advanced, or DCS Virtual Controller).
Regression Testing: Verify that modifying a specific function block or permissive rung does not alter the execution timing, memory allocation, or cause unintended side effects in adjacent control routines.
Rollback Preparation: Create a full binary upload and cryptographic checksum of the running controller immediately prior to making changes, establishing a verified baseline for emergency rollback.
Step 5: Implementation & Field Verification
The change is executed within an authorized maintenance window. The engineer downloads the tested code, verifies communication diagnostics, and performs dynamic functional testing (e.g., injecting test signals or stroking valves under administrative bypass).
Step 6: Pre-Startup Safety Review (PSSR)
Under OSHA 1910.119(l) and 1910.119(i), a formal Pre-Startup Safety Review (PSSR) must be physically executed before introducing hazardous chemicals or re-energizing the process unit. The PSSR committee physically verifies that:
Construction and equipment installation match design specifications.
Safety, operating, maintenance, and emergency procedures have been updated.
Training of each affected operating and maintenance technician has been completed and documented.
All PHA/MOC recommendations have been fully resolved or implemented.
Step 7: Documentation Closeout & As-Built Updates
The MOC cannot be closed until all plant documentation is formally updated to "As-Built" status:
Piping and Instrumentation Diagrams (P&IDs).
Instrument Loop Sheets and Cable Schedules.
Cause and Effect (C&E) Matrices and Logic Narrative Descriptions.
Alarm Master Database and Instrument Index.
Master software repository archive updated with new version tag and cryptographic hash.
Emergency MOC (eMOC) Protocols
During live plant operations, severe unexpected equipment failures or process emergencies can arise that demand immediate control adjustments to prevent an environmental disaster, equipment destruction, or personnel injury (e.g., severe pipeline leak, compressor surge oscillation threatening impeller failure).
Under such extreme circumstances, executing a standard multi-week MOC procedure is impossible. Plants must maintain a strictly defined Emergency MOC (eMOC) protocol. EMERGENCY MOC EXECUTION PROTOCOL:
- 1. Unplanned Emergency Event Threatening Immediate Harm
- |
- v
- 2. Dual Authorization: Operations Superintendent + Lead Safety/Control Engineer
- (Verbal or expedited digital sign-off)
- |
- v
- 3. Implement Minimum Necessary Interim Modification
- |
- v
- 4. Log in Central eMOC Register & Establish Strict Time-to-Live (e.g., <= 48 Hours)
- |
- v
- 5. Retroactive Full MOC & HAZOP Review (within the site-defined window)
- Rules Governing Emergency MOCs
Strictly Limited Authorization: Only senior designated personnel (e.g., Plant Operations Manager and Lead Process Safety Engineer) hold authority under the site procedure to approve an eMOC.
Minimum Scope: The modification must represent the minimum intervention required to secure the safe state of the plant.
Mandatory Expiration Window: An eMOC carries an automatic operational expiration timer (set by site procedure—for example, 24 to 48 hours 24\text{ to }48\text{ hours} 24 to 48 hours ). If a permanent solution is not approved within this window, the affected equipment must be safely brought down.
Mandatory Retroactive MOC: The full technical review, hazard revalidation, PSSR, and as-built documentation lifecycle must be executed retroactively within the window set by site procedure (for example, a few business days). Under no circumstances does an eMOC become a permanent installation without completing the standard 7-step process.
Software Modification Controls & Change Governance
Modern industrial control systems are software-driven platforms. Protecting the integrity of controller firmware, configuration databases, and application code requires rigorous technical and procedural security controls matching ISA/IEC 62443 requirements. CONTROLLER ACCESS & SECURITY GOVERNANCE LAYERS:
- +-------------------------------------------------------------------------+
- | PHYSICAL HARDWARE LAYER: Key-Switch in RUN Mode |
- | - Inhibits unauthorized remote online logic edits or firmware downloads |
- +-------------------------------------------------------------------------+
- ^
- |
- +-------------------------------------------------------------------------+
- | NETWORK / IAM LAYER: Role-Based Access Control (RBAC) |
- | - Active Directory authentication, MFA, engineering privilege tiers |
- +-------------------------------------------------------------------------+
- ^
- |
- +-------------------------------------------------------------------------+
- | APPLICATION LAYER: Audit Trail & Version Vault |
- | - Electronic signatures, revision control, cryptographic checksums |
- +-------------------------------------------------------------------------+
- 1. Physical Controller Key-Switch Controls
Many PLCs (for example, Rockwell ControlLogix) have a physical three-position key switch on the processor; others, such as the Siemens S7-1500, use a RUN/STOP mode switch with access protection set in software:
RUN: The controller executes application code. All remote programming capabilities, online logic edits, and memory downloads are physically locked out by the hardware backplane.
PROGRAM (PROG): The controller halts logic execution, and outputs go to their configured program-mode states (often off). Full program downloads and memory clearing are permitted.
REMOTE (REM): The processor allows software packages across the industrial network to toggle between Run and Program modes, initiate online logic changes, and force I/O bits.
Important
Best engineering practice and cybersecurity standards dictate that during normal commercial production, all PLC processor key-switches must be set to RUN , with the physical key removed and secured in a locked key-box controlled by the operations shift supervisor. Leaving controllers in REMOTE exposes the facility to unvetted software downloads, inadvertent edits, or network-borne malware exploitation.
2. Role-Based Access Control (RBAC) & Electronic Signatures
Engineering workstations must enforce granular role-based permissions integrated with centralized enterprise directory services (e.g., LDAP / Active Directory). Technicians must authenticate using unique individual credentials; generic shared "engineer" or "admin" accounts are strictly prohibited.
Read-Only / Monitoring Tier: Operators and maintenance technicians can view ladder rungs, diagnostics, and online values, but cannot edit code, force I/O, or change tuning parameters.
Tuning Tier: Authorized control specialists can adjust pre-rationalized PID constants and filter settings, subject to automated audit logging.
Engineering Tier: Lead automation engineers can modify application logic rungs and configuration databases, requiring an authorized MOC number and two-factor authentication.
Electronic Signatures and Two-Person Review: Many regulated sites require logic downloads to be signed by the author and an independent verifier, with both signatures captured in the audit trail.
3. Version Control & Cryptographic Checksum Auditing
Application logic must be managed through automated version control vaults (e.g., Versiondog, Rockwell FactoryTalk AssetCentre, Git-based OT platforms):
Scheduled Difference Sweeps: The system executes automated nightly compare routines, comparing the offline certified master program in the vault against the actual binary running in each field controller.
Cryptographic Checksum Tracking: Modern safety controllers (SIL 2 / SIL 3 logic solvers) compute a 32-bit or 64-bit Safety Logic Checksum (CRC) over all certified safety code and parameters. If an engineer changes even a single contact or timer value in the field, the runtime checksum immediately diverges from the certified engineering dossier, generating an unacknowledged alarm on the central engineering console.
Realistic Industrial Scenario: The Bypassed Reactor Interlock Failure
During an intensive production run at a specialty chemical resin facility, operators encounter frequent nuisance trips on high-pressure interlock PSH-3012 regulating an exothermic batch reactor. The nuisance trips are caused by pressure spikes during raw material injection.
The Unauthorized Modification
A night-shift maintenance technician, intending to prevent another production interruption, connects an engineering laptop to the PLC network. The processor key-switch was left in REMOTE . Without submitting an MOC or notifying process engineering, the technician inserts a 10-second on-delay timer ( TON ) directly ahead of the safety shutdown coil in the PLC ladder logic, reasoning that filtering out the short pressure spikes will keep the reactor running.
The Catastrophic Consequence
Two days later, the reactor cooling water supply pump trips unexpectedly. The exothermic polymerization reaction enters a thermal runaway. Reactor pressure spikes rapidly. However, because the on-delay timer artificially delays the emergency depressurization valve opening, reactor pressure exceeds the vessel maximum allowable working pressure (MAWP). The vessel rupture disc blows, venting toxic volatile hydrocarbons directly to the flare header, which overpressures and causes an environmental release and automatic plant shutdown.
Regulatory and Forensic Audit
An OSHA investigation reveals that the off-delay timer modification lacked an MOC, had no Process Hazard Analysis, bypassed engineering approval, and omitted operator training.
The facility was cited for willful violations of OSHA 29 CFR 1910.119(l) and fined hundreds of thousands of dollars.
Remediation: The plant locked all processor key-switches into RUN , deployed an automated version control system with daily checksum mismatch alarms, and established mandatory multidisciplinary MOC review gates for any timer, setpoint, or logic adjustment.
Common Exam Traps
Treating Software Modifications as Exempt from MOC: A classic exam trap posits that "because no physical steel, piping, or instruments were touched, software logic tweaks do not require an MOC." This is completely false. Logic rungs, alarm priorities, timer presets, and scaling constants directly govern physical process dynamics; software changes legally require full MOC processing under OSHA PSM.
Confusing Replacement in Kind (RIK) with Functional Equivalents: An exam question might describe replacing a discontinued safety relay with a newer model that has identical screw terminal footprints but faster electronic switching. Candidates often choose RIK. This is incorrect. If the part number, internal electronics, or diagnostic behaviors differ, it is a Change requiring technical verification.
Believing Pre-Startup Safety Reviews (PSSR) Only Apply to Mechanical Projects: Candidates frequently assume PSSRs are only for pipe welding or vessel installation. OSHA 1910.119(i) requires a PSSR for a modified facility when the modification is significant enough to require a change in process safety information, and many sites apply a PSSR to every safety-related automation change before startup.