ISO 19650 Metadata Compliance Across Multiple CDEs: What the Tools Actually Support

ISO 19650 compliance requires consistent metadata across every CDE your project uses. Most integration tools only support their own vendor's schemas. Here is what actually works.

ISO 19650 has become the standard framework for information management on infrastructure projects across the United Kingdom, Australia, Europe, and an increasing number of jurisdictions globally. It defines how information should be named, structured, versioned, and exchanged across the lifecycle of a built asset.

What it does not solve is the practical problem of enforcing that standard across multiple CDE platforms simultaneously. That is a technology problem, and the tools available to solve it vary significantly in how well they actually handle it.

What ISO 19650 Requires of Your CDE Environment

At its core, ISO 19650 requires that documents and models carry consistent, structured metadata: project codes, originator codes, volume and level identifiers, document type codes, roles, classifications, and status codes. This metadata needs to be preserved across every platform the project uses, in every direction data moves.

When documents are exchanged manually between platforms, metadata is frequently lost, corrupted, or reformatted incorrectly. A document transmitted correctly in Aconex may arrive in ProjectWise with missing fields or values that do not map to the receiving platform's schema. On a project that processes thousands of documents per month, even a small error rate compounds into a significant quality and compliance problem.

Why Most Integration Tools Cannot Solve This

General-purpose integration tools like Workato and Zapier have no AECO domain logic. They can move a file from one platform to another, but they have no understanding of ISO 19650 metadata schemas, no ability to validate field values against a project's naming convention, and no logic to handle the differences between how ACC, ProjectWise, Aconex, and Procore each structure their metadata.

Vendor-specific tools like Bentley BECS and IMAGINiT Clarity handle ISO 19650 metadata within their own platform ecosystems. BECS handles Bentley schemas. Clarity handles Autodesk schemas. Neither can translate metadata between platforms from different vendors.

Custom development can implement ISO 19650 validation logic, but this needs to be built, tested, and maintained as part of the integration. Every time the project's naming convention changes, or a new platform is added, the validation logic needs to be updated by the development team.

What Full ISO 19650 Support Across Multiple CDEs Requires

Genuine ISO 19650 compliance across a multi-vendor CDE environment requires three things.

First, a metadata mapping engine that understands how each platform stores metadata and can translate between schemas when documents move between platforms.

Second, validation logic that checks metadata values against the project's ISO 19650 information requirements and flags or blocks transfers where metadata does not comply.

Third, audit logging that records every sync event with sufficient detail to demonstrate compliance in a quality audit or handover scenario.

How CDE Sync Handles This

CDE Sync includes a dynamic metadata mapping engine that transforms metadata between all supported platforms. When a document moves from Bentley ProjectWise to Oracle Aconex, the metadata is not simply copied. It is translated from Bentley's schema to Aconex's schema, with ISO 19650 field validation applied at the point of transfer.

Version control and transmittal compliance logic are built in, not configured by the customer. Audit logging captures full sync history including every file transferred, every metadata transformation applied, and every error encountered. This log is retained for compliance and handover purposes.

CDE Sync's ISO 19650 capability was developed in partnership with buildingSMART Australasia, where Utopia Digital holds a board position, and is being actively researched through an academic industry partnership with the University of Technology Sydney.

The Practical Implication

On a project where ISO 19650 compliance is a contractual requirement and the supply chain uses more than one CDE platform, the integration layer is not a secondary concern. It is a primary one. A tool that can move files but cannot enforce metadata compliance is not a solution to the problem. It is a different version of the same problem.

CDE Sync was built to close that gap.