How to choose a common data environment for an EPC project

Every EPC project produces tens of thousands of controlled documents: drawings, datasheets, calculations, vendor documents and the correspondence around them. The common data environment that holds them becomes the record of who issued what, when, and on what basis. When a dispute arrives, it is the CDE's audit trail that answers the question.

First decide whose environment it is

The biggest decision is not which product but who hosts it. In an owner-hosted CDE, the operator controls access, retention and the final record, and every contractor works inside it. In a contractor-hosted CDE, the EPC runs its own environment and transmits to the owner. Many large projects use both: engineering work in progress in the contractor's system, and formal issue and review in the owner's. Neutral, multi-organisation platforms such as Oracle Aconex were built for the first model, where each party keeps ownership of its own records; engineering document systems such as Bentley ProjectWise are strongest at managing design work in progress inside an engineering organisation.

Map the information states

ISO 19650 describes a common data environment in which information moves through work-in-progress, shared, published and archived states, with checks at each gate. Even if your contract does not cite ISO 19650, writing your own workflow in those terms quickly shows where a product's defaults fit and where you will need configuration.

The workflows that decide the choice

• Supplier documents: hundreds of vendors submitting thousands of documents against purchase orders, with review codes and resubmissions.
• Review and approval: discipline reviews, owner comments and the status codes your contract defines.
• Transmittals and correspondence: formal issue with an audit trail that both parties accept.
• Numbering and metadata: document numbering rules and the metadata the operator needs at handover.
• Models alongside documents: whether 3D models and drawings need to be reviewed in the same place.

What to test before signing

Run a realistic pilot: a supplier package, a design review with owner comments and a formal transmittal. Measure how much configuration it took and how many clicks it takes a document controller to do routine work. Ask for an export of the full audit trail and check that it is usable without the vendor's software. And price the whole life of the project, including archive access after completion.

Where the catalogue products fit

• Oracle Aconex: multi-organisation, owner-trusted record for very large projects.
• Bentley ProjectWise: engineering work in progress across large design teams.
• Forma Data Management: Autodesk's CDE, natural for Autodesk-centred teams.
• Idox FusionLive: engineering document control and supplier collaboration on energy capital projects.
• Asite and Thinkproject: cloud CDEs with strong building, infrastructure and European references.

Plan handover from the first day. Metadata captured as documents are issued costs a fraction of what it costs to reconstruct for the operator at the end, and the operator will ask.

Sources

1. ISO 19650-1:2018 - Information management using building information modelling, Part 1: Concepts and principlesISO · accessed 23 October 2026
2. Oracle AconexOracle · accessed 22 October 2026
3. ProjectWiseBentley Systems · accessed 22 October 2026