Reconcile an as-built P&ID.
From the IFC drawing set to the as-built drawing set, surfacing every revised tag, loop, and equipment item
Reconciling an as-built P&ID is the engineering process of comparing the issued-for-construction (IFC) drawing set to the as-built drawing set produced after construction is complete, surfacing every tag added, dropped, moved, or revised over the construction phase. The reconciliation produces a change report scoped to the affected disciplines (I&C, mechanical, electrical, piping), feeds the MOC documentation, updates the master I/O list and equipment list to the as-built state, and produces the closeout package the owner receives.
Inputs.
- +IFC drawing set
- +As-built drawing set
- +Master I/O list (legacy baseline)
- +Master equipment list (legacy baseline)
Outputs.
- →Change report scoped per discipline (I&C / mechanical / electrical / piping)
- →Updated master I/O list reflecting as-built state
- →Updated master equipment list reflecting as-built state
- →MOC documentation per change
- →Owner closeout package: as-built drawing set + as-built documents + change report
| Change type | Detection | Downstream impact |
|---|---|---|
| Tag added on drawing | New row in extraction | Added to I/O list + cable schedule |
| Tag dropped from drawing | Missing from extraction | Removed from I/O list + JB schedule |
| Tag renamed | Loop-context match | Cross-reference table to legacy tag |
| Equipment service change | Service column diff | Datasheet revision triggered |
| Loop number reassignment | Loop-consistency pass | Loop folder index rebuild |
| Pipe-class break moved | Line list diff | Stress reanalysis flag |
Step by step.
- 01
Establish the IFC baseline
Extract the IFC drawing set as a baseline workspace. The IFC I/O list, equipment list, and line list become the comparison anchor.
- 02
Extract the as-built
Upload the as-built drawing set as a revision workspace. Page-by-page extraction produces the as-built document set.
- 03
Run the revision diff
Side-by-side comparison surfaces every added, dropped, moved, and revised tag with a per-row source reference. Drift between the IFC and the as-built becomes data.
- 04
Generate per-discipline change report
Filter the diff by discipline so I&C / mechanical / electrical / piping each receive a slice. Owner-facing change report rolls the slices up.
- 05
Update master registers
Approve the as-built delta to update the master I/O list, equipment list, and line list to the as-built state. The legacy baseline archives.
- 06
Ship the closeout package
Bundle the as-built drawing set, the as-built documents, and the change report into the owner handover package.
Common questions.
Does this work when the IFC and as-built sets carry different drawing numbering?
Yes. Drawing number drift between IFC and as-built is common when sheets are renumbered, split, or merged during construction. The reconciliation matches by loop number and equipment tag rather than by drawing number, so renumbering does not break the diff.
What if the as-built is a mix of CAD-exported and scanned redline pages?
Mixed-format drawing sets are routine on retrofits. Scanned redline pages and CAD-exported pages process side by side; lower-confidence rows from scans flag for review before the diff completes.
Can the change report drive the MOC documentation directly?
Yes. Each tagged change carries a source-page reference, the IFC value, and the as-built value. The MOC package presents the same data with the engineering reason for the change filled by the responsible discipline owner.
Start a workspace.
Upload the source documents, run the workflow, ship the document in the column shape the next consumer expects.