Digitalization in EPC: BIM, ISO 19650 and What You Get at Handover

The most valuable thing digitalization delivers on an EPC project is not construction efficiency. It is the data you own when the contractor leaves.

That outcome is decided before award, in a document most owners do not write. The Exchange Information Requirements specify what model, in what format, at what level of detail, is delivered at handover. Without it, an owner receives whatever the contractor happened to produce.

The framework governing this is ISO 19650, the international standard for information management using building information modelling. Its 2026 revision makes the point explicit: the distinction between delivery phase and operational phase has been removed, and the handover data drop disappears in favor of information that flows continuously.

For an industrial operator, that changes the question from how the project is built to what the asset register looks like on day one of operation.

This guide covers what digitalization actually does at each EPC phase, the standards that govern it, and what to specify so the model becomes an operating asset rather than a folder of files.

What Are EPC Project Services?

• EPC Project Services are the turnkey delivery of large-scale industrial and infrastructure assets, covering Engineering, Procurement and Construction under a single contract.
• The scope runs from concept and engineering design through sourcing materials and equipment to construction and handover. The owner holds one contract rather than many, and the contractor carries the integration risk between the three.
• Traditionally, EPC projects involved long timelines, fragmented workflows and cost overruns, with information held in documents that did not connect to each other.

What digitalization changes structurally

• It replaces documents with a model and a data environment. Drawings become views of a model rather than the record itself, and the model carries non-graphical data that documents never could.
• That shift is what allows clash detection before construction, quantity extraction for procurement, and an asset register at handover. All three are consequences of the same change.

How Digitalization Is Reshaping EPC Project Services

Digitalization in EPC rests on one framework and three phase-specific applications, and the framework is what makes the applications work together.

Building information modelling, under ISO 19650-1:2018 clause 3.3.14, is the use of a shared digital representation of a built asset to facilitate design, construction and operation processes, to form a reliable basis for decisions.

The phrase that matters is “reliable basis for decisions.” A model nobody verifies is not that, and an unverified as-built model is worse than none because it is trusted.

What follows covers the three major phases, and the standards and deliverables attached to each.

Engineering Phase: Smarter Designs Through Digital Tools

• The design phase determines what the owner eventually receives, because the information requirements set here govern every deliverable afterwards.
• ISO 19650 is the international standard for information management using building information modelling, published in parts.

The four information requirements, and who writes them

• Organizational Information Requirements, or OIR, define what the owner’s organization needs to manage its portfolio.
• Asset Information Requirements, or AIR, define what information is needed to manage this specific asset across its life. The owner writes these.
• Project Information Requirements, or PIR, define what the owner needs from the project itself.
• Exchange Information Requirements, or EIR, translate those into what the appointed party must deliver, when, and in what format.
• Establishing the common data environment and setting the exchange information requirements are the appointing party’s obligations before appointment, not the contractor’s after it.

If the EIR was never written

• The contractor delivers to its own standard, which is optimized for building the asset rather than for operating it. The owner discovers this at handover, when the leverage has gone.
• Write the AIR and the EIR before tender. They become contractual deliverables, and their absence is the single most common reason handover data is unusable.

The BIM Execution Plan

• The BIM Execution Plan, or BEP, is the contractor’s response to the EIR, setting out how information will be produced and delivered. A pre-appointment BEP outlines the approach during tender; a post-appointment BEP confirms delivery.
• Beneath it sit the Master Information Delivery Plan and the Task Information Delivery Plans, which schedule who produces what and when.
• Some public procurement frameworks require the BEP as a contractual deliverable within 30 days of award. Where yours does not, set the deadline yourself.

What the model does during design

Clash detection identifies physical conflicts between disciplines before construction, which is where the model repays its cost fastest. Federating the structural, mechanical, electrical and piping models exposes conflicts that two-dimensional coordination misses.

Procurement Phase: Precision and Cost Control

Procurement benefits from digitalization through quantity extraction and supplier integration, and both depend on data quality rather than on software.

Quantity take-off pulls material quantities directly from the model, replacing manual measurement from drawings. Its accuracy is governed by the model’s level of detail, which means quantities taken from a concept-stage model are indicative rather than contractual.

Artificial intelligence helps predict material demands based on project progression and historical usage, part of a wider shift toward technology-driven, predictive procurement across EPC supply chains.

Smart procurement platforms integrate with suppliers and can trigger orders against defined thresholds, and digital procurement systems allow real-time monitoring of commitment against budget.

What this requires first

• A consistent material classification and a material master that identifies the same item the same way across the model, the purchase order and the delivery. Without that, model quantities and procurement records do not reconcile.
• That data condition, rather than platform selection, is what determines whether procurement digitalization works.

Construction Phase: Real-Time Control and Safety

• Construction digitalization turns progress reporting from a claimed percentage into a measured quantity.
• 4D scheduling links model elements to programme activities, so progress is visible as what has physically been built rather than as a figure on an invoice. 5D adds cost, linking elements to the cost plan.
• Connected sensors and IoT devices on plant and equipment report utilization and condition. Drones conduct site survey and progress capture, producing point clouds that can be compared against the model. Augmented reality overlays design information on the physical site, letting workers verify position before installation.
• Wearable devices and site access systems improve safety by tracking personnel location and identifying exposure to hazard zones.

Why progress measurement matters most

• A contractor’s progress claim is a statement. A model-linked measurement is evidence, and the gap between the two is the earliest reliable warning of schedule slip.
• That single capability justifies more of the digital investment than any other construction-phase application.

Key Benefits of Digitalization in EPC Project Services

Digitalization delivers value in five areas, and the largest one arrives after the project is finished.

Reducing Costs

• Cost reduction in EPC digitalization comes primarily from avoided rework, and rework avoided is cheapest when the clash is found in the model rather than in the field.
• A conflict between a pipe run and a cable tray costs a model revision during design. The same conflict found during installation costs a site instruction, a re-fabrication and a delay to everything downstream of it.
• Digital planning, predictive analytics and procurement automation contribute, and so does accurate quantity extraction, which reduces both over-ordering and shortfall.

Where the saving does not come from

It does not come from the software, and it does not come from having a model. It comes from using the model to make decisions earlier, which requires the decisions to be scheduled around the model’s maturity rather than around the drawing issue dates.

Improved Collaboration

• The collaboration mechanism in EPC is the common data environment, and it is a governed system rather than a shared folder.
• A common data environment, or CDE, is the agreed single source of information for a project or asset, with defined workflow states controlling what is in progress, shared, published and archived.
• Information containers move through those states under approval, which means a recipient always knows whether what they are looking at is a work in progress or an approved issue. That distinction is what a shared drive cannot provide.
• Model federation combines discipline models into a coordinated whole without merging them, so each task team retains authorship of its own content while the federated model exposes the interfaces between them.

Setting up the CDE

• The appointing party establishes or approves the CDE, defines naming conventions and information container states, and confirms them in the EIR before appointment.
• Doing it afterwards means migrating information that has already been produced to a different convention, which is expensive and lossy.

Increased Speed to Market

Digitalization compresses schedule mainly by removing waiting time between disciplines, not by making individual tasks faster.

In a document-based workflow, a discipline waits for another discipline’s drawing issue. In a CDE-based workflow, work-in-progress information is visible as it develops, so downstream work starts earlier at a known level of confidence.

Clash detection before construction removes site stoppages that would otherwise interrupt the programme, and model-linked progress measurement surfaces slippage earlier, when recovery is still cheap.

Higher Quality and Compliance

• Quality in a digital EPC deliverable is defined by level of detail, and it is specified rather than assumed.
• Level of Development, or LOD, defines the precision of geometry and the reliability of data in a model element at each stage. Level of Information, or LOI, covers the non-graphical data attached to it.

A 2026 industry outlook reports that 72 percent of infrastructure owners now mandate LOD 500 for project handover, to ensure operational data integrity for facility management.

The terminology is changing

ISO 7817-1 defines Level of Information Need, which replaces the ambiguous LOD term. LOD was interpreted differently across countries and organizations for years, and the new term requires the client to specify the geometry and information required for each specific purpose rather than selecting a numbered level.

Specify by purpose. “LOD 500” means less than “sufficient to populate the maintenance management system with asset tag, manufacturer, model, serial number and maintenance requirement.”

Verifying the as-built model

• An as-built model that has not been field-verified records the design intent, not the installation. The verification step is the one most frequently omitted and the one that determines whether the model is usable.
• Require verification as a condition of handover acceptance, and spot-check it against the physical asset before releasing the associated payment.

Insurance and audit

Insurers and lenders assess the completeness of handover documentation when underwriting an operating asset. A verified asset information model is stronger evidence than a drawing set, and an unverified one creates exposure if it is relied upon and proves wrong.

Sustainability and Efficiency

• The model carries the data that sustainability reporting requires, which turns a reporting exercise into a data extraction.
• Material quantities extracted from the model support embodied carbon calculation. Equipment data in the asset information model supports energy performance tracking against design intent once the asset is operating.
• Resource efficiency during construction follows from the same accuracy that reduces cost: ordering what is needed reduces waste, and avoiding rework avoids the material and transport that rework consumes.

The honest limitation

A model does not make an asset efficient. It makes the data available to find out whether it is, which is a prerequisite rather than an outcome.

The Role of Digital Twin Technology

• A digital twin in EPC is what the project information model becomes after handover, and the transition has a name and a standard.
• The Project Information Model, or PIM, is the model produced during design and construction. The Asset Information Model, or AIM, is what the owner operates with. ISO 19650-3 governs the transition and the operational phase that follows.
• The AIM is the operating asset register. It holds equipment identity, location, specification, maintenance requirement and the documentation attached to each item.
• Teams use that model for monitoring system performance, predictive maintenance scheduling, lifecycle cost analysis, and operator training using real-world simulations.

Where the commercial value actually lands

In operations, not in construction. An owner who receives a verified AIM starts operating with a populated maintenance management system. An owner who receives PDFs spends the first year of operation rebuilding the asset register by walking the plant.

That rebuild is the hidden cost of an unspecified handover, and it is incurred at exactly the point when the operating team has least capacity.

What makes an AIM useful rather than impressive

• Asset tagging consistent with the maintenance management system. Equipment data complete for the items that matter rather than for everything. And a verification record proving it reflects what was installed.
• A visually complete model with inconsistent tagging cannot populate a CMMS, which means it looks finished and delivers nothing.

Artificial Intelligence in EPC

• Artificial intelligence in EPC is applied to scheduling, risk prediction and document analysis, and its accuracy is capped by the project data available to train it.
• Current applications include predicting schedule slip from progress and historical patterns, identifying design conflicts by comparing against completed projects, optimizing logistics sequencing, and extracting obligations from contract documents.

What AI requires first

• Structured project data across multiple completed projects, with consistent coding of activities, costs and outcomes. Most owners and contractors hold project records that differ in structure from one project to the next, which means there is nothing consistent to learn from.
• An organization deploying AI on project data it has not standardized produces confident analysis of inconsistent inputs.

What AI does not do here

• It does not replace the engineering judgement in a clash resolution or the commercial judgement in a change order assessment. It narrows where to look.
• Treat it as a prioritization layer over a well-structured dataset, not as a decision layer over an unstructured one.

Overcoming Challenges in Digital Adoption

Three obstacles recur in EPC digital adoption, and only one of them is technical.

High Initial Investment

• Digital tools at enterprise level carry licence, implementation and training cost, and the return is realized across the asset life rather than within the project.
• The investment is recouped primarily through avoided rework during construction and through the avoided cost of rebuilding an asset register during the first year of operation. The second is larger and is almost never included in the business case.

How to frame the case

• Scope the investment against the specific deliverable it produces. A CDE and an EIR cost a fraction of a full digital transformation programme and deliver most of the handover value.
• Starting with the information requirements rather than with the software is both cheaper and more likely to succeed.

Change Management

• Employees accustomed to traditional workflows may resist new digital systems. Successful adoption requires training programmes, change champions and ongoing support throughout the project lifecycle.
• The resistance is usually rational. A workflow that is slower for the person doing it and faster for someone downstream will be resisted unless the benefit is visible to both.

Staffing

Information management under ISO 19650 is a defined role, not an addition to an engineering job. The appointing party needs someone who owns the EIR, the CDE configuration and the acceptance of delivered information.

Where that role is unstaffed, the requirements are written once and never enforced.

Data Integration

Integrating digital tools with legacy systems is the technical obstacle, and open formats are the mechanism that makes it tractable.

Industry Foundation Classes, or IFC, is the open, software-neutral format for exchanging model data between different authoring tools. It is what prevents an owner being locked into whichever platform the contractor chose.

COBie, Construction Operation Building Information Exchange, is a structured data format for transferring asset data from the model into a facility or maintenance management system at handover. It is the bridge between the model and the CMMS.

ISO 19650-4 specifies the processes for information exchange, including the technical requirements for file formats and information containers.

What to specify

Require delivery in IFC alongside any native format, and require COBie or an equivalent structured export mapped to your maintenance management system’s fields.

Specifying only the native format means the data is only usable for as long as you hold that licence.

If the contractor uses different software

That is normal and it is what IFC exists for. The requirement is not that everyone uses the same tool; it is that everyone can export to a common format that validates.

Require a test exchange early in the project rather than discovering the export is incomplete at handover.

Outside the United States

ISO 19650 applies internationally and is the basis of national frameworks in the UK and elsewhere. In the United States, NBIMS-US and COBie requirements may apply, particularly on federal contracts. Confirm which framework governs before writing the EIR.

Real-World Success: How Prismecs Leads Digital EPC Services

Prismecs delivers EPC and owner’s engineering on industrial energy projects, and the digital question we help owners answer is what to require rather than which platform to buy.

Delivered project scope includes eight TM2500 dual-fuel units totaling 260 MW at Birr, Switzerland, online in six months with a new 220 kV interconnection and engineered noise controls on a compact site; four TM2500 units totaling 110 MW at Duqm, Oman, kept grid-ready with resident O&M crews, CMMS and parts support; an LM2500XPRESS plant at Miaoli, Taiwan delivered in ten months; and an LM6000 fleet decommissioned in Norway, transported and recommissioned at a new site.

The Duqm arrangement is the relevant reference for this subject. Resident crews operating against a maintained CMMS with parts support is the operating state a good handover produces, and the state a poor one prevents.

How to evaluate a contractor’s information capability

Ask for a redacted BIM Execution Plan from a comparable project. Ask which CDE they use and who administers it. Ask for a sample IFC export and try to open it. Ask what their last project’s handover data looked like and whether the client’s maintenance system was populated from it.

One scope boundary worth stating. Prismecs delivers engineering, procurement, construction management, commissioning and operations. BIM authoring, digital twin software implementation, AI platform deployment and enterprise systems integration are software disciplines with separate providers. Our role is specifying what the owner requires and verifying what is delivered against it.

The Future of EPC Project Services Is Digital

The 2026 revision of ISO 19650 removes the distinction between delivery phase and operational phase, which changes what an owner must specify and when.

The focus of the standard is now explicitly the whole life of the asset, with the delivery and operational phase distinction removed. Three consequences follow for owners.

Information requirements must cover the entire lifecycle, so the AIR, PIR and EIR are written once against operational need rather than separately for project and operations.

The data drop disappears. Information flows continuously rather than being handed over in a single event at practical completion, which removes the moment where everything either works or does not.

Facility managers are engaged from the concept phase rather than at handover, because they are the people who know what the asset information model needs to contain.

What to do now

Write the AIR before the next project starts, with the operating team in the room. Everything else in the information chain derives from it.

By sector

• Power generation projects produce asset registers dominated by rotating equipment with defined maintenance intervals, which makes equipment data completeness the priority.
• Petrochemical and process projects carry mechanical integrity obligations under inspection codes, so the model must support the inspection programme rather than only the maintenance programme. 
• Data centre projects change fastest, with equipment replaced on cycles shorter than the building, which makes the model’s ability to be updated more important than its initial completeness.
• Metals and mining projects are distributed across large sites with harsh conditions, where locating an asset reliably is itself a significant benefit.

At the Bottom Line

Digitalization in EPC is governed by ISO 19650, delivered through a common data environment, and judged by what the owner can operate with afterwards.

The Exchange Information Requirements decide that outcome and are written before award. The Asset Information Model is the deliverable that matters, verified as-built, exchanged in IFC, and mapped into the maintenance management system through COBie or an equivalent.

Clash detection, 4D progress measurement and quantity extraction all repay their cost during construction. The larger return arrives when the operating team starts work with a populated asset register rather than a filing cabinet.

Ready to Start Your Digital EPC Journey?

Prismecs provides EPC delivery, owner’s engineering, commissioning and operations for industrial energy projects, including specification and verification of handover information requirements.

Capability spans EPC services for project delivery, owner’s engineering for independent technical representation and information requirement review, I&C services for installation, commissioning and controls, O&M services for the operating phase, technology and consulting for assessment and options analysis, and supply chain solutions for procurement and expediting. Delivered work is on the projects page.

Apply this article’s criteria to any proposal, including ours. Ask who writes the Exchange Information Requirements and when. Ask what level of information needed is specified for handover and against what purpose. Ask for a sample IFC export and open it. Ask how the as-built model is verified before acceptance.

To discuss EPC delivery, owner’s engineering or handover information requirements, send your project scope and capacity, contract form if selected, current project stage and your maintenance management system to sales@prismecs.com or call +1 (888) 774-7632.

Frequently Asked Questions

What is BIM in an EPC context?

Under ISO 19650-1:2018 clause 3.3.14, building information modelling is the use of a shared digital representation of a built asset to facilitate design, construction and operation processes, to form a reliable basis for decisions. In EPC it is the engineering deliverable, the clash detection mechanism, the quantity source for procurement, and the basis of the asset register handed over at completion.

What is ISO 19650 and what are its parts?

The international standard for information management using building information modelling. Part 1 covers concepts and principles including the common data environment. Part 2 covers the delivery phase during design and construction. Part 3 covers the operational phase and the transition from project to asset information model. Part 4 covers information exchange. Part 5 covers security. Part 6 covers health and safety information.

What are Exchange Information Requirements and who writes them?

The EIR specifies what information the appointed party must deliver, when, and in what format. The appointing party, meaning the owner, writes it before appointment, derived from the Asset Information Requirements that define what is needed to operate the asset. Without an EIR, the contractor delivers to its own standard, which is optimized for building the asset rather than for operating it.

What is a common data environment?

The agreed single source of information for a project or asset, with defined workflow states controlling what is in progress, shared, published and archived. Information containers move through those states under approval, so a recipient always knows whether what they are viewing is a work in progress or an approved issue. The appointing party establishes or approves it before appointment.

What is the difference between a PIM and an AIM?

The Project Information Model is produced during design and construction. The Asset Information Model is what the owner operates with afterwards, holding equipment identity, location, specification, maintenance requirement and attached documentation. ISO 19650-3 governs the transition and the operational phase. The AIM is effectively the operating asset register, which is where the commercial value of the whole exercise lands.

What LOD should be specified at handover?

LOD 500, as-built and field-verified, is the handover standard, and a 2026 industry outlook reports 72 percent of infrastructure owners now mandating it to ensure operational data integrity. LOD 300 applies at detailed design and coordination, LOD 350 at issue for construction, and LOD 400 at construction with fabrication detail. Specify by operational purpose rather than by number alone.

What is the difference between LOD and LOI?

LOD is Level of Development, covering geometric precision and the reliability of the element. LOI is Level of Information, covering the non-graphical data attached to it. Geometry alone does not satisfy an asset owner, because the operating value is in the data: asset tag, manufacturer, model, serial number and maintenance requirement. Both must be specified separately.

What is replacing LOD in ISO 19650?

ISO 7817-1 defines Level of Information Need, which replaces the ambiguous LOD term. LOD was interpreted differently across countries and organizations for years, meaning Level of Detail, Level of Definition or Level of Development depending on context. The new approach requires the client to specify the geometry and information required for each specific purpose rather than selecting a numbered level.

What are IFC and COBie and why do they matter?

IFC, Industry Foundation Classes, is the open software-neutral format for exchanging model data between different authoring tools, preventing lock-in to whichever platform the contractor chose. COBie, Construction Operation Building Information Exchange, is a structured data format for transferring asset data from the model into a facility or maintenance management system at handover. Require both alongside any native format.

What changed in ISO 19650 in 2026?

The revision removes the distinction between delivery phase and operational phase, focusing the standard explicitly on the whole life of the asset. Information requirements must cover the entire lifecycle rather than stopping at handover. The data drop disappears, with information flowing continuously instead of transferring in a single event. Facility managers are engaged from the concept phase rather than at handover.

Why does handover data matter more than construction efficiency?

Because an owner who receives a verified asset information model starts operating with a populated maintenance management system, while an owner who receives PDFs spends the first year of operation rebuilding the asset register by walking the plant. That rebuild is the hidden cost of an unspecified handover, incurred exactly when the operating team has least capacity.

How do you verify an as-built model?

By field verification against the physical installation, which is the step most frequently omitted. An as-built model that has not been verified records design intent rather than what was installed, and an unverified model is worse than none because it is trusted. Require verification as a condition of handover acceptance and spot-check it before releasing the associated payment.

What does AI actually do in EPC projects?

It predicts schedule slip from progress and historical patterns, identifies design conflicts by comparison with completed projects, optimizes logistics sequencing, and extracts obligations from contract documents. Its accuracy is capped by data quality, and it requires structured project records with consistent coding across multiple completed projects. It narrows where to look rather than replacing engineering or commercial judgement.

How do I evaluate a contractor’s information management capability?

Ask for a redacted BIM Execution Plan from a comparable project. Ask which common data environment they use and who administers it. Ask for a sample IFC export and try to open it. Ask what their last project’s handover data looked like and whether the client’s maintenance system was populated from it. Those four questions reveal more than any capability statement.

Tags: BIM ISO 19650 EPC Digitalization Asset Information Model Handover