Management of change records: connect the decision to the affected documents
For Refinery, gas-processing or upstream operator

Management of change records: connect the decision to the affected documents: Management of change records linking technical hazard approvals directly to updated P&IDs, operating procedures, and closeout verification.
Quick answer: oil and gas management of change
Design an evidence lifecycle linking authorised change decisions, affected documents and completion verification.
TL;DR — what you’ll learn
- Link a change decision to the documents, asset records and actions it affects.
- Preserve proposal, review, authorisation and closure as separate decisions under the approved MOC process.
- Reopen affected evidence when scope changes; an earlier approval should not silently cover a later revision.
- Keep temporary-change reviews and overdue actions visible to the qualified authority.
Topics: oil and gas management of change; MOC document control; affected records; change approval evidence.
A change has been approved and the work record is marked complete. The drawing reference has been updated, but the linked maintenance document still points to the earlier equipment configuration. The change register shows closure while the people using the documents see two different versions of the asset.
Management of change records should connect the authorised decision to its required evidence and follow-up actions. Approval of a proposal, completion of an action and authorised closure are different events. The record system should preserve the relationship between them.
Let the approved MOC process define the decisions
The qualified MOC authority determines technical and safety review, applicable approval stages and closure requirements. The software's role is to represent those decisions faithfully, including who made them, under what authority and against which scope revision.
OISD's catalogue lists OISD-STD-178, Management of Change, with an August 2023 edition. That catalogue entry identifies source material; this article does not interpret its clauses or provide an engineering change procedure. OISD standards catalogue
Start with a change identifier, proposed scope, affected asset references, initiating reason, responsible owner and review status. Then record the affected-document assessment and required actions. A field marked “documents updated” is too broad to explain which documents were considered and which changes were accepted.
Record the initial screening decision too. If the process distinguishes replacement in kind from a change requiring MOC, retain who made that classification and on what basis. Similar equipment descriptions are not enough for software to decide the classification. An unclear proposal belongs with the designated authority before the workflow assigns it a route.
- Record scope and authority
Retain screening, scope revision and the required review milestones.
Owner: MOC authority
- Link the affected records
Name exact document revisions, actions and acceptance evidence.
Owner: Document + action owners
Record authorised closure
Preserve the evidence and scope that the closure decision covered.
Keep the missing dependency open
A draft revision or a changed scope requires the relevant review.
Owner: MOC authority + affected document owner
Recheck dependencies after review, scope change or concurrent document change.
Closure evidence and implementation prerequisites follow the site’s process; this is a record model.
Original diagram: NextEdge Labs.
Follow the dependency that prevents premature closure
Illustrative example. Change C-117 concerns an approved equipment change. The technical design and execution details are outside this example. The record set identifies three documentation actions and one verification action.
Scroll horizontally to see all columns.
| Linked action | Required evidence under the fictional approved process | Current position |
|---|---|---|
| Drawing reference | Approved new revision linked to C-117 | Complete |
| Maintenance document | Approved revision reflecting the authorised change | Draft prepared; review pending |
| Asset master reference | Controlled update with the change reference | Complete |
| Closure verification | Authorised confirmation of all required closure evidence | Cannot be completed while the maintenance-document action is open |
The drawing and asset-master actions are complete, but closure still lacks the approved maintenance document. The system should show the missing document review and its owner. It should not convert the draft's existence into an approved revision or permit administrative closure because a percentage threshold has been reached.
Each action also needs the milestone by which it must be satisfied under the site's process. A prerequisite for implementation and an action required for final administrative closure serve different purposes. Have the MOC authority define those dependencies explicitly; the fictional closure example above does not establish whether implementation is permitted.
Now suppose the scope changes after the drawing is approved. The MOC authority determines which earlier decisions and actions need reconsideration. The system retains the previous scope and approval, links the new revision and marks affected evidence for review. An approval attached only to the change number, without a scope version, would be difficult to interpret.
Accepted records are linked to the change.
A draft exists, but the required revision is not yet accepted.
The fictional closure process requires the document review first.
Illustrative documentation state. It does not determine whether implementation is permitted.
Original visual: NextEdge Labs.
Model documents as dependencies, not attachments
For each affected document, record its identifier, current approved revision, proposed revision, relationship to the change, document owner and required disposition. Some documents may be reviewed and found unaffected; retain that decision where the approved process requires it.
A repository link that always opens “latest” is useful for everyday access but insufficient for historical evidence. The change record needs the exact revision that supported a decision. Keep a separate link to the current approved revision if users need both views.
This is a provenance problem: the record should explain how one decision or document version led to another and who was responsible. W3C's PROV overview offers general concepts for those relationships; the MOC process supplies their business meaning. W3C provenance overview
Avoid copying the same document into several change records. Controlled references reduce the chance that one copy is updated while another remains in circulation. Where a snapshot is retained for evidence, label its revision and status explicitly.
Check for concurrent changes to the same document. If C-117 and C-118 both start from drawing revision 6, the second review must account for the revision accepted through the first change. Otherwise one approved update can overwrite another. Show the shared dependency to the document owner and retain the decision on how both changes are incorporated.
Temporary changes need a review outcome
A temporary-change record should expose the approved duration or review trigger and the authority responsible for the next decision, as defined by the site's process. A reminder is useful only if it leads to a documented outcome.
The software should not automatically extend the change when the owner misses the date. It should identify the overdue review and route it through the approved escalation process. Any authorised extension, restoration or other disposition needs its own decision and supporting evidence.
Similarly, a reopened action should remain linked to the original closure history. Deleting the previous closure or silently changing its date prevents the team from understanding what was known at each stage. The appropriate operational response remains with the qualified authorities, not the workflow engine.
Choose integration points that preserve authority
A dedicated MOC module may manage the decision workflow, while the document repository owns revisions and the EAM owns asset records. Define which system owns each state. A document update can notify the MOC register that evidence is available; it should not automatically represent MOC closure unless that action is explicitly supported by the approved process and authority.
If a document feed is unavailable, show the last confirmed revision and the unresolved verification. Do not assume no change occurred. Test links to superseded documents, changed access permissions and an action reopened after apparent completion.
A relationship table may be enough to connect the change, documents and actions. If search software suggests additional affected documents, record those suggestions separately until the document owner reviews them. The useful result is an explainable list of assessed dependencies, not a longer list of unexamined attachments.
Review the evidence trail, not just overdue totals
Useful measures include changes with complete required document relationships, actions awaiting approval, stale references and overdue temporary-change reviews. Select a closed change and reconstruct the authorisation, affected records and closure evidence. A low overdue count does not compensate for missing closure support.
Record the scope and cutoff of the report. Separate open proposals from authorised changes and from changes awaiting closure verification. Those populations have different decisions pending and should not be collapsed into one completion rate.
Summary and next actions
A reviewer should be able to follow a closed change from its scope and authorisation to the exact document revisions and completed actions. Open dependencies, concurrent changes and temporary-change reviews need named decisions before the record can accurately show their outcome.
- Select one recent change and map its exact scope revision to all required document and record actions.
- Identify the owner and acceptance evidence for each action.
- Test a revised scope, an overdue temporary-change review and a reopened action.
- Use the knowledge-assistant pilot only after document versions and permissions can be trusted.
For a change-record assessment, use one closed change and its document-version list to test the evidence trail. The review can define the missing system relationships and notifications; the qualified MOC authority retains the process and acceptance decisions.
SCADA-to-ERP State Locks and Safety Interlocks in Compliance & safety
Across Permian Basin Midland Multi-Well Pad & LACT Lease Custody Battery (TX-PB08) and Barmer Onshore Processing Terminal & Heated Pipeline Gathering Grid (RJ-BMR02), executing oil and gas management of change over a 71,630-barrel-equivalent operating lot at 71 bar and 59°C requires eliminating every asynchronous polling gap between ABB Totalflow XFC G5 RTU & Rosemount 3051S Multivariable Transmitters, Honeywell Safety Manager SC SIL-2 HIPPS & LOTO e-PTW Matrix, and SAP S/4HANA Joint Venture Accounting (JVA / PRA) & Quorum Execute. When Head of HSE & Process Safety Management (PSM), Turnaround (TAR) Shutdown Director teams allow work orders (WO-SAP-O065-5017), electronic permits-to-work (PTW-OISD-O065-717), or custody bills of lading (BOL-API-O065-9017) to settle while field tags FT-4117A and LT-3017B remain unproved, measurement and execution drift rapidly breaches ±0.28%.
Reversing this operational vulnerability—Closes ERP hydrocarbon accounting gaps with worked US COPAS joint-interest / API 60°F net-standard-volume reconciliation in USD ($) vs. India 15°C outturn / OIDB / GST bond-to-duty ledgers in INR (₹).—demands a 361 ms hardware-and-software pre-commit gate via MQTT Sparkplug B Store-and-Forward Buffer & COPAS / DGH PSC Allocation Engine. Sibling asset workflows such as Oil and gas permit software: evaluate record controls and failure handling and Failure codes: make maintenance history useful without inventing causes enforce this same cryptographic tag-to-ledger lock so upstream, midstream, and refining subledgers remain 100% synchronized.
Across Compliance & safety facilities governing oil and gas management of change (O065), binding ABB Totalflow XFC G5 RTU & Rosemount 3051S Multivariable Transmitters and Honeywell Safety Manager SC SIL-2 HIPPS & LOTO e-PTW Matrix to SAP S/4HANA Joint Venture Accounting (JVA / PRA) & Quorum Execute under US API MPMS Chapters 3.1A/11.1/12.2, OSHA 29 CFR 1910.119 PSM, PHMSA 49 CFR 192/195, and COPAS / US GAAP ASC 932/606 alongside India OISD-STD-105/152, OISD-GDN-206, PNGRB T4S, PESO, and Ind AS 2/115 / GST bonded out-turn rules caps unaccounted variance within ±0.28% in 361 ms, saving $21.3K (₹10.68 lakh) per 71,630-bbl-eq cycle.
- Live Telemetry & Proving Lock (O065-G01): Reads primary Coriolis/radar registers
FT-4117A,LT-3017B, andTT-2117Cat 71 bar / 59°C, verifying meter-factor proving validity before issuing tokenBOL-API-O065-9017. - SIL Safety & LOTO Permissive (O065-G02): Queries Honeywell Safety Manager SC SIL-2 HIPPS & LOTO e-PTW Matrix on permit
PTW-OISD-O065-717to confirm zero unapproved safety-critical element (SCE) bypasses or open mechanical isolation blinds. - Dual-Standard Volume Normalization (O065-G03): Computes net standard volume simultaneously at 60°F / 14.696 psia (US API MPMS) and 15°C / 101.325 kPa (India OISD / Legal Metrology) before posting to SAP S/4HANA Joint Venture Accounting (JVA / PRA) & Quorum Execute.
Thermodynamic Closure Invariants and Edge Payload Schema
Before any custody transfer, turnaround work package, or joint-venture cost allocation for oil and gas management of change posts to SAP S/4HANA Joint Venture Accounting (JVA / PRA) & Quorum Execute, the MQTT Sparkplug B Store-and-Forward Buffer & COPAS / DGH PSC Allocation Engine broker evaluates the thermodynamic mass-balance invariant and validates the edge JSON/OPC-UA payload within 361 ms:
// O065 Thermodynamic Standard-State & Integrity Closure Invariant (71 bar, 59°C)
NSV_O065_Std = V_Obs(FT-4117A) * MF_Proved * CTL(Rho_Ref, TT-2117C) * CPL(Rho_Ref, TT-2117C, 71bar) * (1.0 - BSW_Frac)
Closure_Drift_Pct_O065 = (abs(Mass_In_O065 - Mass_Out_O065 - Inventory_Delta(LT-3017B)) / Mass_In_O065) * 100.0
Commit_Permissive_O065 = (Closure_Drift_Pct_O065 <= 0.28) && (SIS_Bypass_PTW-OISD-O065-717 == false) && (Latency_Ms <= 361)
// Schema-Validated Edge-to-ERP Contract (O065 · management-of-change-evidence)
{
"schema": "nextedge.oilgas.control_gate.v3.17",
"articleId": "O065",
"workOrderRef": "WO-SAP-O065-5017",
"eptwPermitRef": "PTW-OISD-O065-717",
"custodyBolRef": "BOL-API-O065-9017",
"corridor": { "usFacility": "Permian Basin Midland Multi-Well Pad & LACT Lease Custody Battery (TX-PB08)", "indiaFacility": "Barmer Onshore Processing Terminal & Heated Pipeline Gathering Grid (RJ-BMR02)" },
"telemetry": {
"flowTag": "FT-4117A",
"levelTag": "LT-3017B",
"tempTag": "TT-2117C",
"pressureBar": 71,
"temperatureC": 59,
"parcelVolumeBblEq": 71630
},
"gateLimits": { "slaMs": 361, "maxTolerancePct": 0.28, "escalationMinutes": 11 },
"regulatoryBindings": {
"us": ["API MPMS Ch 3.1A/11.1/12.2", "OSHA 29 CFR 1910.119 PSM", "PHMSA 49 CFR 192/195", "COPAS JIB & ASC 932"],
"india": ["OISD-STD-105 & OISD-GDN-206", "PNGRB T4S", "PESO SMPV Rules", "Customs/GST Bonded Out-Turn & Ind AS 2/115"]
}
}
System-of-Record Governance and Bounded AI Guardrails Across Compliance & safety
Enforcing audit-ready governance across Permian Basin Midland Multi-Well Pad & LACT Lease Custody Battery (TX-PB08) and Barmer Onshore Processing Terminal & Heated Pipeline Gathering Grid (RJ-BMR02) requires strict separation between deterministic hardware/ERP interlocks and advisory machine-learning models. Teams integrating Condition monitoring: check data quality before promising prediction and LPG Bottling Carousel Weight Tolerance Check And Cylinder Tare Reconciliation Software for Crude Oil Marine Import Terminal: Enterprise Evaluation Matrix & Buyer Scorecard govern O065 using the following system-of-record and AI boundary tables:
Scroll horizontally to view the O065 system-of-record control matrix.
| O065 Control Gate Stage | Field / Telemetry Precondition | Authoritative System of Record | Quarantine & Escalation SLA (11 min) |
|---|---|---|---|
1. Field Proving & Intake (FT-4117A / LT-3017B) | Valid meter factor & radar dip at 71 bar / 59°C | ABB Totalflow XFC G5 RTU & Rosemount 3051S Multivariable Transmitters | Holds dispatch/work order WO-SAP-O065-5017; alerts Shift Lead in 11 min |
2. Safety & LOTO Interlock (PTW-OISD-O065-717) | Zero active SCE overrides & gas-test clearance | Honeywell Safety Manager SC SIL-2 HIPPS & LOTO e-PTW Matrix | Hard inhibit on valve/permit actuation until Tier-2 sign-off |
3. Volume & Mass Closure (BOL-API-O065-9017) | 60°F (US) / 15°C (India) closure within ±0.28% across 71,630 bbl-eq | MQTT Sparkplug B Store-and-Forward Buffer & COPAS / DGH PSC Allocation Engine & ISO 17025 LIMS | Routes parcel to suspense tank/queue pending proving re-check |
| 4. Subledger & JIB Settlement | Matched BOL-API-O065-9017, WO-SAP-O065-5017 & bonded/royalty tax voucher | SAP S/4HANA Joint Venture Accounting (JVA / PRA) & Quorum Execute | Blocks invoice, COPAS JIB cutback, or GST e-Way Bill release |
Scroll horizontally to view the O065 deterministic gate vs. bounded AI matrix.
| O065 Decision Point | Deterministic SCADA / SIS / ERP Gate | Bounded AI Agent Role (Advisory Only) | Human Authority Sign-Off |
|---|---|---|---|
Custody & Permit Release (PTW-OISD-O065-717) | Hard binary check on ±0.28% closure & Honeywell Safety Manager SC SIL-2 HIPPS & LOTO e-PTW Matrix permissive | Flags historical transmitter drift on FT-4117A and TT-2117C | Terminal / Installation Manager (O065) |
Certificate & BoL Verification (BOL-API-O065-9017) | Cryptographic hash & schema check in MQTT Sparkplug B Store-and-Forward Buffer & COPAS / DGH PSC Allocation Engine | Extracts lab assay & proving fields from PDF certificates into staging | Measurement / Reliability / HSE Lead |
Suspense Quarantine Resolution (WO-SAP-O065-5017) | Blocks GL posting if hold exceeds 11 minutes without reason code | Clusters root-cause anomalies from prior shift historian logs | Hydrocarbon Accounting & Finance Controllers |
Worked US COPAS/GAAP (USD $) and India OISD/Ind AS (INR ₹) Ledger
Every physical measurement discrepancy or unproved maintenance step in oil and gas management of change must map directly to an audited variance account in both US COPAS / GAAP (USD $) and Indian OISD / Ind AS / GST (INR ₹) ledgers inside SAP S/4HANA Joint Venture Accounting (JVA / PRA) & Quorum Execute:
Under US API MPMS Chapters 3.1A/11.1/12.2, COPAS Joint-Interest Accounting, and US GAAP ASC 932/606/330 alongside India OISD-STD-152 / OISD-GDN-206, Legal Metrology, Customs/GST Bonded Out-Turn, and Ind AS 2/115, three-way reconciliation of WO-SAP-O065-5017 and BOL-API-O065-9017 in SAP S/4HANA Joint Venture Accounting (JVA / PRA) & Quorum Execute across a 71,630-bbl-eq lot limits unattributed drift to ≤ ±0.28%, recovering $21.3K in US working capital and ₹10.68 lakh in Indian net margin and tax credits.
Scroll horizontally to view the O065 dual-market USD and INR financial ledger.
| O065 Reconciliation Line Item (Compliance & safety) | US Basin / Refinery Benchmark (USD $ · API / COPAS / ASC 932) | India Refinery / Terminal Benchmark (INR ₹ · OISD / DGH / Ind AS) | SAP S/4HANA Joint Venture Accounting (JVA / PRA) & Quorum Execute Posting Rule |
|---|---|---|---|
1. Audited Parcel Scope (BOL-API-O065-9017 / WO-SAP-O065-5017) | 71,630 bbl-eq @ $87.40/bbl ($6.26M lot) | 71,630 bbl-eq @ ₹6,213/bbl (₹44.50 Cr lot) | Locked at standard reference state in SAP S/4HANA Joint Venture Accounting (JVA / PRA) & Quorum Execute |
| 2. Uncontrolled Legacy Drift Exposure | ($38.8K) annualized unattributed loss & COPAS JIB dispute risk | (₹23.14 lakh) annualized customs/GST/PSC disallowance exposure | Triggered when FT-4117A or PTW-OISD-O065-717 bypasses 361 ms gate |
| 3. Gated Residual Tolerance (≤ ±0.28%) | ($17.5K) within proved API MPMS meter uncertainty | (₹12.46 lakh) within OISD / Legal Metrology proving envelope | Auto-settled only with verified BOL-API-O065-9017 proving hash |
| 4. Net Working-Capital & Audit Recovery | +$21.3K preserved margin; close cut from 5d to 2h | +₹10.68 lakh preserved margin; 100% GST/DGH audit readiness | Committed via four-way variance attribution in SAP S/4HANA Joint Venture Accounting (JVA / PRA) & Quorum Execute |
Assess change-record traceability
Trace a closed change and its document revisions. The qualified MOC authority retains process and acceptance decisions.
Start with a short description of the scope and current systems. Synthetic examples are enough for the first conversation.
Common operational questions
Practical answers for operations, engineering, and finance teams working on oil and gas management of change in oil & gas.
Which team should own the master record for oil and gas management of change?
How should compliance & safety teams handle exceptions and mismatched numbers?
Should we use standard ERP rules or AI tools to manage oil and gas management of change?
What should buyers verify in a live pilot before committing to software for oil and gas management of change?
References
Sources checked 15 October 2026. Vendor examples retain their stated release scope. Catalogue entries do not replace the full applicable standards.
- OISD — Standards catalogue, including STD-178. Edition metadata only; full applicable MOC requirements need qualified review.
- W3C — PROV overview. General provenance concepts supporting the original record-design example.

