As-Designed vs. As-Built: How EPCs Verify Industrial Construction Against 3D Models
An industrial facility can be constructed according to an approved engineering design and still differ from the original 3D model in hundreds of small ways.
A pipe may be rerouted around an obstruction. A vendor skid may arrive with different nozzle positions. Structural steel may be installed within tolerance but not exactly where the model expected it. Cable trays, instruments and access platforms then have to be coordinated around those field conditions.
For EPC contractors, the challenge is keeping design intent and physical construction aligned.
Modern as-built verification combines 3D laser scanning, LiDAR, point clouds, engineering models and deviation analysis to compare the physical facility with what was designed—before commissioning and final handover.
As-designed describes what was intended to be built. As-built describes what was actually constructed. As-built verification compares the two.
What is the difference between as-designed and as-built?
| Term | Meaning |
|---|---|
| As-designed | Approved engineering intent represented in CAD/BIM models and drawings |
| As-planned | Planned construction sequence and execution state |
| As-constructed | Contractor records, redlines and field documentation |
| As-built | Verified representation of the physical facility |
| As-is | Current physical condition of an operating or brownfield asset |
This distinction matters because a contractor's redlined drawing does not automatically prove that the digital model matches physical reality.
Consider an LNG facility where a process pipe is designed at a specific elevation. During construction, the route is shifted to avoid an unexpected structural obstruction. The field change may be approved, but if the central 3D model is not updated, downstream engineering and operations teams can continue working from outdated geometry.
That can affect piping, cable trays, maintenance clearances, commissioning and future modifications.
Why do as-designed and as-built conditions differ?
Construction deviations are not necessarily evidence of poor workmanship. They can result from normal EPC execution realities:
- Construction tolerances: Steel, concrete, piping and equipment are installed within specified tolerances.
- Vendor changes: Replacement pumps, compressors or packaged skids can have different dimensions, nozzle locations or anchor patterns.
- Field routing: Piping, cable trays and instrumentation may be rerouted around actual site conditions.
- Engineering changes: RFIs, field change notices and approved modifications can alter the installation.
- Brownfield conditions: Existing plants may contain undocumented modifications that differ from legacy drawings.
The problem occurs when these differences are not measured, approved and incorporated into the authoritative project record.
Suggested Reads: Virtual Ergonomics and Maintenance Clearance: Validate Operator Access Before Fabrication
How does 3D as-built verification work?
A typical industrial construction verification workflow follows five stages:
3D engineering model → reality capture → point-cloud registration → model comparison → engineering review
1. Capture physical reality
Terrestrial laser scanners, LiDAR, mobile mapping and other reality-capture technologies measure the constructed facility.
The result is a point cloud containing millions of spatial measurements representing physical surfaces.
NIST research on 3D imaging and measurement emphasizes that measurement accuracy depends on the characteristics of the measurement system and the conditions under which data is captured and processed. For EPC projects, scan accuracy should therefore be evaluated against the project's required accuracy and verification methodology.
2. Register the point cloud
Multiple scans are combined into a common coordinate system so the entire facility can be analyzed consistently.
For industrial EPC projects, survey control and coordinate-system discipline are essential because the scan must align reliably with the engineering model.
3. Compare the scan with the 3D model
The registered point cloud is aligned with the approved engineering model.
Engineers can then investigate differences between:
Designed geometry ↔ measured physical geometry
4. Analyze deviations
Software can calculate spatial differences between measured points and corresponding model surfaces.
A simplified distance calculation is:
The system calculates the 3D distance between the measured scan position and the corresponding model position across the X, Y, and Z coordinates.
Where applicable, those acceptance criteria should also reflect the governing engineering codes and project specifications. A detected difference is not automatically a defect; it may be an approved field change, a model error, a survey issue, or a genuine construction deviation.
5. Resolve and update
Significant discrepancies can be connected to RFIs, NCRs or engineering change workflows. Once approved, the relevant project records and models can be updated.
This creates a controlled chain:
Field condition → measured data → deviation → engineering decision → approved change → verified record
What does as-built verification check?
3D model verification is especially valuable in dense industrial environments.
- Piping and pipe racks: Teams can investigate routing, elevations, supports, tie-ins and clearances.
- Equipment: Verification can confirm the installed location and orientation of pumps, compressors, vessels, heat exchangers, turbines and packaged skids.
- Structural steel: Point-cloud comparison can identify differences in columns, beams, platforms and pipe-rack structures.
- Electrical and instrumentation: Teams can review cable trays, supports, equipment access and spatial relationships with piping and structures.
- Maintenance and access: A component can be installed correctly yet still create an operational problem. 3D reviews can help determine whether valves, equipment and maintenance areas remain accessible.
What role does XR play?
Extended Reality does not replace laser scanning.
Laser scanning captures physical reality. Model-comparison software analyzes deviations. XR helps engineering, construction and operations teams understand those results at human scale.
For example, an EPC team can review a verified plant model in VR to examine:
- Valve accessibility;
- Equipment maintenance envelopes;
- Pipe-rack congestion;
- Operator pathways;
- Installation sequences;
- Constructability issues.
This can make spatial problems easier to communicate than reviewing complex 3D geometry on a conventional screen.
Example: detecting a piping deviation before commissioning
Consider a U.S. Gulf Coast petrochemical project.
A process line is designed to connect a vessel to a downstream heat exchanger. During construction, the pipe is rerouted around a structural member. The physical installation works, but the engineering model still shows the original route.
A scan-based verification workflow can:
- Capture the installed piping.
- Register the point cloud.
- Compare it with the engineering model.
- Identify the routing deviation.
- Determine whether it meets the approved tolerance.
- Link the condition to the relevant RFI or field change.
- Update the authoritative record where required.
The objective is not simply to find a moved pipe. It is to ensure that the digital record and physical facility agree before responsibility transitions to operations.
Suggested Reads: The As-Built vs. As-Designed Reality: Leveraging Augmented Reality for Construction QA/QC
Where is as-built verification most valuable?
The approach is particularly relevant to:
- Oil Refinery: complex piping, equipment, dense multidisciplinary process units and structural systems.
- LNG: tightly coordinated process equipment, piping and utilities.
- Petrochemical: high levels of piping and spatial coordination.
- Power Generation: turbines, HRSGs, generators, ductwork and electrical systems.
- Brownfield projects: existing conditions that may differ from legacy drawings.
Brownfield work is especially important because what exists physically can be more reliable than what old documentation says should exist.
As-built drawings vs. as-built 3D models
An as-built drawing provides a documented 2D representation of the installed facility. An as-built 3D model provides spatial relationships between equipment, structures and systems.
Neither automatically replaces the other.
A strong digital handover can combine:
Verified 3D geometry + drawings + survey data + asset information + inspection and commissioning records
ISO 19650 emphasizes defining information requirements and managing project information throughout the asset lifecycle. buildingSMART's openBIM approach similarly promotes interoperable information exchange so project data can move between systems and stakeholders. The exact digital-handover deliverables should therefore be defined by the owner's information requirements and project specifications.
5 best practices for EPC teams
1. Define verification requirements early
Establish scanning scope, coordinate systems, tolerances, milestones, responsibilities and deliverable formats in the Project Execution Plan.
2. Scan at meaningful milestones
Capture critical areas after foundations, structural erection, major equipment installation, piping installation and before systems become inaccessible.
3. Maintain coordinate-system discipline
Reliable survey control and registration are essential for aligning point clouds with engineering models.
4. Connect deviations to change management
Construction Industry Institute (CII) research emphasizes disciplined project controls and structured processes for managing construction performance. A detected discrepancy should therefore flow into the appropriate RFI, NCR or engineering-change process rather than becoming an isolated scan report.
5. Define the digital handover
Specify whether the owner requires verified models, drawings, asset attributes, survey data or digital-twin information. Do not automatically equate an as-built model with LOD 500; the required model content should follow the project's information requirements.
Frequently Asked Questions
What is as-built verification?
As-built verification is the process of comparing the physical condition of a constructed facility with its approved engineering design to identify, evaluate and document deviations.
How do EPC contractors verify construction against a 3D model?
They capture the physical site using laser scanning or other reality-capture methods, register the resulting point cloud, align it with the engineering model and analyze differences against project-defined tolerances.
What is an as-built point cloud?
An as-built point cloud is spatial measurement data captured from the constructed environment. It can support dimensional verification, documentation and comparison with engineering models.
Can as-built verification be used for brownfield projects?
Yes. Reality capture can establish a current spatial baseline before new engineering or construction begins, reducing dependence on potentially outdated drawings.
Does XR replace 3D laser scanning?
No. Scanning measures reality; model-comparison tools analyze reality against design; XR for CAD provides an immersive way to review the resulting information.
Conclusion
Industrial EPC projects will inevitably encounter conditions that differ from the original engineering model. The objective is not to eliminate every deviation—it is to identify meaningful differences, determine whether they are acceptable, document approved changes and ensure the final digital record reflects physical reality.
A modern as-built verification workflow connects:
What was designed → what was constructed → what was verified → what was handed over.
For EPC leaders across the U.S. oil & gas, LNG, refining, petrochemical and power sectors, that connection can provide a stronger foundation for QA/QC, commissioning, digital handover and future brownfield work.
