In the previous article, AI in Process Safety: Why the Real Breakthrough Isn’t Intelligence—It’s Access, we established a critical shift in how artificial intelligence is applied in Process Safety Management (PSM): the value is not in smarter tools, but in embedding AI within the systems where work is executed. This article moves from concept to operation.
Rather than describing what AI could do, we will examine what Jodi actually does inside a real Management of Change (MOC) lifecycle when operating within FACILEX®.
From Procedure to Execution
Most organizations have a defined MOC procedure aligned with OSHA 29 CFR 1910.119 and CCPS Risk-Based Process Safety. The challenge is not the absence of procedure—it is consistent execution across:
- Scoping completeness
- Impact analysis quality
- Action tracking discipline
- PSI alignment and updates
- Timely closeout
These gaps are rarely due to lack of knowledge. They are due to limited time, fragmented information, and the manual effort required to connect all relevant data. This is where Jodi operates.
The MOC Lifecycle in FACILEX®
Within FACILEX®, MOC is not a form—it is a structured lifecycle:
- Initiation
- Scoping
- Change Design
- Impact Analysis
- Approval
- Implementation
- Pre-Startup Safety Review (PSSR)
- Closeout
Jodi participates across this lifecycle as an embedded execution assistant, operating within the same governed environment as the engineer.
Phase 1: Initiation
At initiation, the goal is to define the change clearly and determine whether it requires formal MOC.
What Jodi Does:
- Reviews the change description for completeness
- Compares against historical MOCs to identify similar change types
- Flags indicators that suggest escalation (e.g., safety-critical systems, operating envelope changes)
- Assists in distinguishing between Replacement in Kind (RIK) and valid MOC-triggering changes
Outcome:
A more consistent and defensible decision to initiate an MOC, supported by real facility history.
Phase 2: Scoping
Scoping is where many MOCs fail. Missing scope leads directly to missed hazards.
What Jodi Does:
- Retrieves similar historical MOCs and highlights relevant scope elements
- Cross-references applicable scoping checklists within FACILEX®
- Identifies missing disciplines (e.g., mechanical, instrumentation, process)
- Flags required reviews based on change type and affected systems
Outcome:
A more complete scope definition, reducing the likelihood of downstream rework or missed risks.
Phase 3: Change Design
This phase defines how the change will actually be implemented.
What Jodi Does:
- Organizes supporting documentation within the MOC workspace (calculations, drawings, vendor data)
- Links relevant PSI documents already managed in FACILEX®
- Highlights potential inconsistencies between proposed design and existing PSI
- Assists in structuring technical notes and design intent
Outcome:
A well-documented, traceable design basis aligned with existing facility knowledge.
Phase 4: Impact Analysis
Impact analysis is the core of MOC—this is where risk is evaluated.
What Jodi Does:
- Cross-references affected equipment, safeguards, and operating conditions
- Identifies related hazards based on historical incidents and PHAs
- Assists in drafting consequence scenarios and affected safeguards
- Highlights where additional analysis (e.g., PHA update) may be required
Outcome:
More rigorous and consistent identification of risk impacts using actual facility data—not generic assumptions.
Phase 5: Approval
Approvals ensure that the right stakeholders validate the change before execution.
What Jodi Does:
- Verifies that required reviews are complete
- Confirms that all prerequisite actions and documentation are in place
- Highlights outstanding issues or inconsistencies
- Supports routing through the defined approval structure in FACILEX®
Outcome:
Approvals are based on complete, validated information—not partial submissions.
Phase 6: Implementation
Implementation is where the approved change is executed in the field.
What Jodi Does:
- Tracks open actions and assigned responsibilities
- Monitors completion status against defined requirements
- Flags overdue or at-risk tasks
- Maintains alignment between field execution and documented change scope
Outcome:
Improved execution discipline and reduced risk of incomplete implementation.
Phase 7: Pre-Startup Safety Review (PSSR)
PSSR ensures the system is safe to operate before startup.
What Jodi Does:
- Verifies that all required PSSR checklist items are addressed
- Confirms that PSI updates have been completed
- Cross-checks that safeguards and procedures are in place
- Identifies gaps that would prevent safe startup
Outcome:
A more reliable and defensible readiness verification before introducing process hazards.
Phase 8: Closeout
Closeout is often delayed or incomplete, leaving residual risk and audit exposure.
What Jodi Does:
- Verifies that all actions are completed and documented
- Confirms that PSI has been updated and linked appropriately
- Ensures audit trail completeness within FACILEX®
- Flags any outstanding items preventing formal closure
Outcome:
Timely and complete closure, with a fully auditable record of the change.
What Has Changed—and What Has Not
It is important to be precise about Jodi’s role.
What Has Not Changed:
- The engineer remains accountable
- The MOC procedure remains intact
- Governance and approvals remain enforced
- All actions occur within FACILEX®
What Has Changed:
- The effort required to connect information is reduced
- The consistency of execution is improved
- The likelihood of missed scope or incomplete analysis is reduced
- The speed of progressing through the lifecycle is increased
Jodi does not replace the engineer. She extends the engineer’s ability to execute the process correctly and consistently.
From Manual Coordination to Assisted Execution
Traditional MOC execution relies heavily on manual coordination:
- Searching for prior changes
- Locating relevant PSI
- Ensuring checklist completeness
- Tracking actions across stakeholders
When Jodi operates within FACILEX®, these activities become integrated into the workflow of the system itself.
The result is not automation of decisions—it is structured support for execution.
Why This Matters
MOC breakdowns rarely occur because organizations lack procedures. They occur because execution is inconsistent under real-world constraints.
By embedding Jodi within FACILEX®, organizations can:
- Improve the quality of hazard identification
- Reduce cycle time without sacrificing rigor
- Strengthen audit readiness
- Maintain alignment between change, PSI, and operational reality
This is a practical step forward in how PSM programs are executed—not a theoretical enhancement.
Looking Ahead
This article focused on MOC as a foundational PSM process.
In the next post, we will examine how this capability is made possible, looking at how AI is connected to systems like FACILEX® in a controlled, governed manner, and how organizations maintain full control over their data and intellectual property while enabling this new level of capability.
About PSM.ai
Gateway Consulting Group has launched PSM.ai, a vendor-neutral knowledge library dedicated to the study of Artificial Intelligence in Process Safety Management. The site curates research papers, industry articles, case studies, and emerging practices from across the process industries, helping safety professionals stay informed as AI technologies begin to influence hazard identification, risk assessment, operational learning, knowledge management, and Process Safety Information governance. As the field evolves, PSM.ai will continue expanding its coverage across all aspects of Risk-Based Process Safety.
