Find orphan instruments.
Surface every instrument tag that appears on a P&ID but has no per-instrument datasheet
An orphan instrument is a tag that appears on a P&ID but has no corresponding per-instrument datasheet in the project datasheet binder. Orphan instruments are the most common engineering scope gap on brownfield retrofits and late-stage greenfield projects: a tag added in a P&ID revision was never carried through to procurement, or the datasheet exists for a vendor model that differs from the as-installed instrument, or a vendor-supplied skid drawing tags an instrument that the EPC scope misses. Surfacing the orphan list early prevents the most common SAT punch class.
Inputs.
- +P&ID set (extracted instrument index)
- +Datasheet binder
- +Vendor skid drawings (if applicable)
Outputs.
- →Orphan instrument list with per-row root cause column for engineering review
- →Cross-reference table for renaming-during-revision cases
- →Procurement gap report for tags missing from procurement scope
- →As-installed update list for tags substituted by the contractor
| Pattern | Typical cause | Engineering decision |
|---|---|---|
| Tag added in revision, no datasheet | Revision merge gap | Add to procurement scope |
| Datasheet exists, different vendor | As-installed substitution | Update datasheet to as-installed |
| Tag on vendor skid, missed by EPC | Scope boundary drift | Update master register from skid drawing |
| Tag exists, datasheet under different tag | Renaming during revision | Cross-reference table to legacy tag |
| Tag never installed | Cancelled scope, P&ID not updated | Remove from P&ID set |
Step by step.
- 01
Extract the P&ID instrument scope
Upload the P&ID set. The extracted instrument index becomes the master tag list (the universe of what should exist).
- 02
Extract the datasheet binder
Upload the datasheet binder. Each per-instrument datasheet maps to its tag.
- 03
Surface the orphans
Tags on the P&ID with no datasheet match. The orphan list ships as a dedicated workbook sheet with the source P&ID page reference per row.
- 04
Classify root cause
Each orphan reviewed for revision-gap vs. as-installed-substitution vs. scope-boundary-drift vs. renaming-during-revision vs. cancelled-scope. The root-cause column drives the engineering action.
- 05
Drive the action list
Procurement gaps route to procurement; as-installed substitutions route to the responsible discipline for datasheet update; cancelled scope routes to drafting for P&ID revision.
Common questions.
Why are orphan instruments such a common SAT punch class?
Field commissioning walks the loop sensor through final element. An orphan instrument has no datasheet to verify range, calibration, or vendor model against; the commissioning electrician cannot sign off until the datasheet exists. The orphan list surfaced at the engineering-audit stage prevents the field cycle.
Can this surface phantom datasheets too?
Yes - phantom datasheets are the inverse case (datasheet with no P&ID parent). The reconciliation surfaces both directions. Phantoms typically indicate scope drift (vendor over-supply) or stale datasheets carried forward from a prior project revision.
Start a workspace.
Upload the source documents, run the workflow, ship the document in the column shape the next consumer expects.