Reconcile across a multi-document engineering bundle.
From a P&ID + datasheet + cable + loop + JB schedule bundle to a single reconciled tag graph
Cross-document reconciliation is the engineering process of joining every tag across a multi-document engineering bundle (P&ID set, instrument index, datasheet binder, cable schedule, loop diagrams, JB schedule) and surfacing the agreements, disagreements, orphans, and phantoms. A tag that appears on the P&ID with no datasheet is an orphan; a datasheet that references a tag not on any P&ID is a phantom; a cable terminating at a tag that doesn't exist is a phantom reference; a JB terminal labeled for a tag that's actually elsewhere is a mistermination. Cross-document reconciliation surfaces every one of these inconsistencies before they become field issues.
Inputs.
- +P&ID set
- +Instrument index (extracted or supplied)
- +Datasheet binder
- +Cable schedule
- +Loop diagrams
- +JB schedule
Outputs.
- →Tag-level reconciliation report with one row per project tag and per-source columns
- →Orphan instrument list (tags on P&ID with no datasheet)
- →Phantom datasheet list (datasheets with no P&ID parent)
- →Phantom cable termination list (cables to nonexistent tags)
- →JB mistermination list
- →Range, loop number, and signal class disagreement reports
- →Export targets: Excel workbook (multi-sheet by inconsistency class), JSON for the engineering audit tool
| Class | Detection | Engineering decision required |
|---|---|---|
| Orphan instrument | On P&ID, no datasheet | Procurement gap or extraction error |
| Phantom datasheet | Datasheet, no P&ID parent | Scope drift or vendor over-supply |
| Phantom cable termination | Cable to nonexistent tag | Mistermination or wiring scope gap |
| JB mistermination | Terminal labeled wrong tag | Field rework before energization |
| Range disagreement | Datasheet vs. instrument index | Engineering decision on as-built range |
| Loop number mismatch | Loop diagram vs. I/O list | Loop renumbering or revision-merge gap |
| Signal class mismatch | P&ID vs. loop diagram | Re-classify per single source |
Step by step.
- 01
Upload the bundle
Drop the P&ID set, datasheet binder, cable schedule, loop diagrams, and JB schedule into a single workspace. Each document extracts in parallel.
- 02
Join on tag
Every tag across the six document classes becomes a node in the tag graph. Per-source columns show where each tag appears.
- 03
Surface orphans and phantoms
Tags present in some sources but missing from others flag automatically. The orphan list and phantom list ship as separate workbook sheets for review.
- 04
Detect attribute disagreements
Range, loop number, signal class, and service description compared across sources. Disagreement rows ship for engineering decision.
- 05
Walk the field-issue list
Cable phantoms and JB misterminations route to the I&C engineer; range disagreements to the responsible discipline; phantom datasheets to procurement.
- 06
Ship the audit report
Excel workbook + JSON. The reconciliation report becomes the engineering audit record, scope-locking the package before commissioning starts.
Common questions.
How is this different from comparing two P&ID revisions?
Revision comparison runs between two states of the same document class. Cross-document reconciliation runs across distinct document classes (P&ID, datasheet binder, cable, loop, JB) within the same revision. Both are useful; cross-document reconciliation catches the issues that survive a clean revision diff.
Can I run this on a partial bundle (some documents missing)?
Yes. Partial bundles produce partial reports - the reconciliation flags the missing source columns so the engineering review knows which document classes were unavailable. As the bundle completes, the reconciliation re-runs.
Does this catch field issues before SAT?
Yes. Cable phantoms and JB misterminations are the dominant SAT failure modes; detecting them at the bundle-reconciliation stage (before site work begins) prevents the field cycle.
Start a workspace.
Upload the source documents, run the workflow, ship the document in the column shape the next consumer expects.