Systems and records
Utility document revision tasks: drawings revised after the work order
By SourceX Editorial · Reviewed by Noah Loul ·
10 sections
Short answer
Record a drawing revised after its work order as two dated facts: the revision the work order cited at issue, and each later revision with its approval date, change description and affected sheets. Link them with a supersedes relation, then record whether the change touches the open work's scope, the next step qualified staff took, and who decided. Utility document revision tasks test whether a model notices that gap and routes it correctly.
Document stack
Utility document revision
Key takeaways
- Keep the revision a work order cited at issue time and store every later revision as its own dated, linked record.
- A case answers four questions: cited revision, newer approved revision, impact on scope, and the documented next step.
- Impact labels separate informational changes from in-scope changes and safety boundaries such as relief devices or isolation points.
- Revisions created from field redlines after the work are a different task and must not be labeled as stale-drawing gaps.
- Labels record what qualified staff decided; the benchmark never becomes operating guidance.
How do you represent a drawing revised after the work order was issued?
Freeze the revision the work order cited at issue and store every later revision as its own dated record, linked back with a supersedes relation. Never overwrite the work order's reference with the current revision: the gap between the two is the thing a model must learn to see, and a record that silently updates it destroys the evidence.
Standards already treat revisions as first-class records. ASME Y14.35 defines practices for revising engineering drawings and associated documents and establishes methods for identifying and recording revisions, so the revision letter or number, the revision history entry and the affected sheets are the natural keys. For linking, the W3C provenance ontology defines wasRevisionOf as a kind of derivation in which the newer entity is a revised version of an original, which maps cleanly onto drawing revision C being revised into revision D.
The resulting case answers four questions in order: which revision did the work order rely on, was a newer revision approved before the work was done, does the change touch what the crew was asked to do, and what did the qualified person decide. A benchmark built from such cases measures revision awareness and impact judgment, not drawing reading.
Why a stale revision on a work order is a safety and records problem
A crew working from a superseded drawing can install the wrong part, isolate the wrong point or leave records that no longer match the asset. In regulated facilities the dated link between drawings, changes and field work is also something operators are required to maintain, which is why these records are worth capturing carefully.
Two U.S. regimes show the pattern. OSHA's process safety management standard lists piping and instrument diagrams among required process safety information, requires written procedures to manage changes to equipment and procedures other than replacements in kind, and says that when a change alters process safety information, that information must be updated. Its nonmandatory Appendix C adds that P&IDs are to be completed, with operating procedures in place and staff trained, before startup.
For gas pipelines, PHMSA's rule on procedural manuals requires procedures for making construction records, maps and operating history available to appropriate operating personnel, and its maximum allowable operating pressure reconfirmation rule turns on whether records are traceable, verifiable and complete. These rules apply to specific facilities and are cited here only to show why dates and links matter; whether they apply to your assets is a question for your compliance team.
Where the evidence for one revision case lives
A single case usually spans four or five systems, and the join keys between them are the hardest part. Inventory them before designing anything, and note which ones keep history rather than only the current state.
| Record | Where it is usually kept | Fields to extract | Why the case needs it |
|---|---|---|---|
| Work order | Enterprise asset management or CMMS | Order id, asset id, issue date, scope text, attached or referenced document ids and revisions, status history | Shows what the crew was told and which drawing they were told to use |
| Drawing revisions | Engineering document management system | Document number, sheet, revision, approval date, revision description, affected zones or tags | Shows what changed and when it became the approved version |
| Change request | Management of change or engineering change system | Change id, reason, technical basis, approval chain, closure date | Explains why the drawing changed and whether the change was complete |
| Field records | Mobile work app, permits and isolation records | Execution date, crew, redlines, isolation points used, completion notes | Shows which revision was actually followed |
| Asset master | EAM or GIS | Asset id, location, equipment class, parent and child assets | Lets the case decide whether a revision touches the asset in scope |
The revision awareness and impact benchmark specification
The specification below defines one case. Field names are suggestions; the rules column is what makes the case usable as is. Example values are illustrative.
- Task 1, detection: given the work order and revision events, was a newer approved revision in force at execution?
- Task 2, localization: which sheets, zones or tags changed?
- Task 3, impact: does the change intersect the work scope, and is it a safety boundary?
- Task 4, routing: which documented next step applies and which role decides?
| Field group | Fields | Rule | Illustrative value |
|---|---|---|---|
| Case identity | case_id, utility_type, asset_class, spec_version | One case per work order and drawing pair; spec version recorded | RA-0042, gas distribution, regulator station, v1.0 |
| Work order as issued | wo_id, issued_at, scope_text, cited_doc_id, cited_revision | Copied from the order's history at issue time, never from its current state | WO-118, day 0, replace relief valve, P&ID 2-410, rev C |
| Revision events | revision, approved_at, effective_at, description, sheets, tags_changed, supersedes | Every revision after cited_revision up to execution, in order | Rev D, day 6, relief valve relocated, sheet 2, tag PSV-3 |
| Linked change | change_id, reason, status_at_execution, closed_at | Status as of the execution date, not today | MOC-77, open on day 9 |
| Execution | executed_at, revision_used, redlines, isolation_plan_id | From field records; unknown is allowed but must be stated | Day 9, rev C, no redline, ISO-5 |
| Impact label | impact_class: none, informational, in_scope, safety_boundary | Assigned by a qualified reviewer against the work scope | safety_boundary |
| Next step label | documented_action, decided_by_role, decided_at | The action actually taken and approved, not an ideal one | Hold and re-issue, engineering supervisor, day 8 |
| Evidence pointers | doc_ids and field paths that justify each label | Every label must cite at least one record | Rev D description; WO-118 scope_text |
Which revision date, asset fact or safety boundary decides what the crew may do next?
The label for the next step depends on three dated facts: whether the newer revision was approved before execution, whether its change touches assets in the work scope, and whether the linked change was complete. The table shows a typical mapping; your own procedures decide the actual one, and the benchmark records what qualified staff did, not what a model would prefer.
| Condition at execution | Typical documented next step | Who decides | Label |
|---|---|---|---|
| No revision after the cited one | Proceed as issued | Crew lead under normal procedure | none |
| Newer revision changes title block or notes only | Proceed and note the current revision on the order | Planner or crew lead | informational |
| Newer revision changes an asset or tag in scope | Hold, re-plan and re-issue the order against the new revision | Planner with engineering | in_scope |
| Newer revision changes isolation points, relief devices or protective settings | Stop; re-issue the isolation plan and procedure before work | Qualified engineering or operations authority | safety_boundary |
| Revision approved but its change is still open | Do not treat the drawing as as-built; follow the change owner's instruction | Change owner | in_scope or safety_boundary by content |
| Revision approved after execution | No gap for this order; check whether field redlines fed the revision | Document control | none, with a later-revision note |
How should revision awareness be scored?
Score each task separately, because a model that always says a drawing is stale will look strong on detection and useless on impact. Report detection precision and recall over cases with and without a gap, impact-class agreement with the reviewer, next-step agreement, and whether the cited evidence actually supports the answer.
Weight errors by consequence. Proceeding on a safety_boundary case is a severe error; holding on an informational case is a cost but not a hazard. Publish the weighting with the benchmark and report the raw confusion counts so users can apply their own. Keep a held-out set of assets and years so the model cannot learn one station's drawing numbering.
Balance the case mix deliberately. In most archives the large majority of work orders have no later revision at all, so a benchmark sampled at random would be almost entirely easy negatives. Sample gap cases and no-gap cases separately, state the ratio you chose, and include near misses such as revisions approved one day after execution, which test whether a model reads dates rather than revision letters.
Finally, record the evidence a model was given. A case scored with the full revision history attached measures something different from one where the model must ask for or retrieve it, and both are useful: the first tests judgment, the second tests whether an agent knows to check document control before acting on a work order.
Worked case (illustrative): a relief valve job and a revision that arrived late
This case is invented to show the method; no real utility, asset or record is described. A planner issues a work order on day 0 to replace a relief valve at a regulator station and cites P&ID sheet 2 at revision C. On day 6 engineering approves revision D, which relocates that relief valve downstream as part of an open change for a capacity upgrade. The crew is scheduled for day 9.
On day 8 the engineering supervisor sees the conflict, holds the order and re-issues it on day 11 against revision D with a new isolation plan. In the case record, the work order keeps revision C as cited, revision D appears as a revision event with approval on day 6, the linked change is open at the original execution date, the impact label is safety_boundary because a relief device moved, and the next-step label is hold and re-issue, decided by the engineering supervisor.
A model given the case without labels should flag the gap, name sheet 2 and tag PSV-3, classify the impact as a safety boundary and route the decision to engineering. A model that suggests swapping the valve in its old position, because that is what the order says, fails the case.
The exception: revisions that follow the work instead of preceding it
Not every later revision is a gap. When a crew finds the field different from the drawing, marks up a redline and document control issues a new revision to match, the revision comes after the work because of the work. Labeling that as a stale-drawing case teaches a model the wrong lesson.
Separate these cases by checking whether the revision description or change record cites the work order or its redline. Keep them as their own task type, field-to-drawing feedback, which is valuable in its own right: it shows how as-built records are corrected. Also watch for revisions approved but given a later effective date, where the approval date alone would create a false gap.
Where the benchmark has to stop: safety, confidentiality and specialist review
Limit the dataset to administrative and document evidence. It should never become operating guidance, and no label should read as an instruction to field staff. Have an energy operations expert confirm the impact and next-step mappings, a safety reviewer check that safety_boundary cases are labeled conservatively, and counsel review whether drawings of critical facilities, contractor-owned drawings or security-sensitive layouts may leave the company at all.
Remove names, phone numbers and crew identifiers, and generalize exact locations where a drawing could reveal security-sensitive details. If a case cannot be made safe to share without losing the revision evidence, leave it out. Remember that holding the drawings is not the same as having the right to license them; engineering contracts and client agreements may say who owns them.
Licensing revision histories from a utility or energy operator
Linked histories of work orders, drawing revisions and change records are uncommon outside the operators who keep them. An operator that wants to license selected histories can work with SourceX on sourcing, rights review, contracting, preparation and delivery, and drawing archives too large to move easily stay on the company's own storage or ship on encrypted drives rather than being hosted by SourceX.
The opening step is an assessment of the company that asks for no drawings or records, and an approved scope and a signature come before any delivery.
Frequently asked questions
What is a utility document revision task?
It is an evaluation or training task in which a model receives a work order, the drawing revision it cited and any later revisions, and must decide whether the work relied on an out-of-date drawing, what changed and what should happen next. The answer is graded against what qualified staff actually decided.
Why should a work order record the drawing revision it was issued against?
Without the cited revision, nobody can later tell whether the crew used the right drawing or whether a change arrived after planning. Recording it at issue time, and never overwriting it, preserves the evidence needed for audits, investigations and revision-awareness cases.
What is the difference between a field redline and a new drawing revision?
A redline is a markup made in the field to show where the installed condition differs from the drawing. A new revision is an approved change to the drawing itself, usually issued by document control, and it may incorporate redlines after review.
Can a model decide whether work proceeds after a drawing revision?
No. The benchmark measures whether a model notices the gap, judges its impact and routes it to the right role. Decisions to proceed, hold or stop stay with qualified staff under the operator's procedures.
Which records make a drawing revision case usable for AI evaluation?
The work order history at issue time, every later revision with its approval date and description, the linked change record and its status, field execution records and the asset master entry. Missing dates or join keys usually make a case unusable.
Sources
- ASME Y14.35 defines practices for revising drawings and associated documents and establishes methods for identifying and recording revisions. Source
- The W3C PROV ontology defines wasRevisionOf as a derivation in which the resulting entity is a revised version of an original. Source
- OSHA's process safety management standard lists piping and instrument diagrams as process safety information, requires written management-of-change procedures except for replacements in kind, and requires process safety information to be updated when a change alters it. Source
- OSHA's nonmandatory Appendix C says P&IDs are to be completed, with operating procedures in place and staff trained, before startup. Source
- 49 CFR 192.605 requires gas pipeline operators' manuals to include procedures for making construction records, maps and operating history available to appropriate operating personnel. Source
- 49 CFR 192.624 requires MAOP reconfirmation for certain onshore steel transmission segments whose records are not traceable, verifiable and complete. Source
See if your company qualifies
A short company assessment. No data uploads are needed.