Management of Change (MOC) — Engineering Guide
Shared by TSIMEREZIVO Team · 4 Oct 2026 · 35 views
#
Management of Change (MOC)
The Management of Change (MOC) process ensures that any modification to PLC logic,
alarm setpoints, interlocks, or control strategies is formally reviewed, approved, and
documented before implementation. TSIMEREZIVO provides a built-in MOC workflow that integrates
directly with the Code Vault, Tag Manager, and Audit Log.
15 min
## Why MOC Matters
> **Industry Accidents Caused by Uncontrolled Change** —
Many major industrial accidents (Bhopal, Texas City, Deepwater Horizon) had in common:
modifications to safety systems, setpoints, or control logic that bypassed formal review.
OSHA Process Safety Management (PSM) regulation 1910.119 mandates MOC for covered processes.
Even outside PSM-regulated facilities, good engineering practice requires that all changes
be reviewed by a competent engineer before implementation.
## MOC Lifecycle
| step | desc |
|---|---|
| 1. Request | Originator creates MOC |
| 2. Review | Technical peer review |
| 3. Approve | Engineer/Admin approves |
| 4. Implement | Change is made & tested |
| 5. Verify | SAT or simulation test |
| 6. Close | MOC closed, vault updated |
))}
## Creating an MOC Request
### Step 1 — Navigate to MOC
From the sidebar click **MOC** (Management of Change module).
Click **+ New MOC Request**.
### Step 2 — Complete the MOC Form
Fill in all required fields:
```text
MOC Number: Auto-assigned (MOC-2026-052)
Title: Add VSD speed limit for PP-101 (max 80% at night)
Type: Temporary / Permanent / Emergency
Plant: Midlands Refinery — Block B
Equipment: PP-101 (Cooling Water Pump, Block B)
Description:
Current State: PP-101 runs at 100% VSD speed during off-peak hours
Proposed Change: Limit VSD speed command to max 80% between 22:00 and 06:00
to reduce noise at adjacent residential area
Reason: Community noise complaint, EPA requirement
Affected Tags: PP101_SPEED_SP, PP101_MAX_SPEED_LIM
Affected Logic: MAIN.LD Rung 0045 (speed limiting rung)
Affected Screens: PP-101 Motor Faceplate (speed setpoint range)
Risk Assessment:
Could the change affect production? YES — reduced pump throughput 22–06
Could the change affect safety? NO — lower speed only, no safety impact
Could the change affect quality? YES — review with process engineer first
Does it affect a safety function? NO
Does it require loop test? YES
Pre-Implementation Requirements:
[ ] Process engineer to review flow balance at 80% speed
[ ] Night shift manager notification
[ ] Test in LogicForge Simulator
Planned Implementation Date: 2026-05-10 06:00 (after night shift)
Estimated Downtime: None (bumpless transfer)
Reversal Plan: Delete speed limit rung, restore to 100% max SP
```
### Step 3 — Attach Supporting Documents
Attach relevant files to the MOC:
- Revised P&ID redline showing the change
- Simulation results from LogicForge (screenshot or export)
- Email approval from process engineer
- Site noise survey report (for regulatory evidence)
### Step 4 — Submit for Review
Click **Submit MOC**.
The system sends a notification to all Engineers and Admins on the plant.
Status changes to ● UNDER REVIEW.
## Reviewing an MOC (Engineer)
### Step 1 — Open the MOC
Go to **MOC → Pending Review**. Open the MOC.
Review the description, affected tags, risk assessment, and supporting documents.
### Step 2 — Add Review Comments
Add technical review comments in the Review Comments field. Flag any concerns.
Multiple reviewers can add comments. All comments are timestamped and attributed.
### Step 3 — Approve or Reject
Click **Approve** or **Reject**.
An approval reason or rejection reason is required. If approved, status changes to
● APPROVED — AWAITING IMPLEMENTATION.
Rejected MOCs are returned to the originator for revision.
## Implementing the Change
### Step 1 — Make the Technical Changes
Implement the approved change:
- Edit the LogicForge program (Rung 0045 — speed limit)
- Update alarm setpoints in the Tag Manager if needed
- Update SCADA faceplate if display ranges changed
### Step 2 — Link to MOC Record
In the Vault upload, reference the MOC number in the "Reason for Change" field.
In LogicForge, add a rung comment:
```text
{`(* MOC-2026-052: Speed limit rung — max 80% between 22:00 and 06:00
Approved by: J. Smith (Engineer) on 2026-05-09
Implemented by: A. Patel on 2026-05-10 *)
IF time_of_day >= T#22:00:00 AND time_of_day ● IMPLEMENTED — PENDING VERIFICATION.
### Step 4 — Verify and Close
After the change is in service and verified (loop test, one shift of monitoring):
Click **Close MOC**.
Add a verification note: e.g. *"Speed limiting confirmed active 22:00–06:00. No production impact observed. Noise complaint resolved."*
MOC status: ● CLOSED. Cannot be reopened.
### Related Guides
| href | label | desc |
|---|---|---|
| /dashboard/docs/vault-versioning | Code Vault | Version control for all program changes |
| /dashboard/docs/sat-commissioning | Site Commissioning | SAT checklist for verifying implemented changes |
| /dashboard/docs/rbac-roles | User Roles | Who can approve and implement MOC requests |