What is a

And why should we care?!

Simply put, CDX is a new framework and language for project teams to decide their workflow and exchange requirements collaboratively.

Common Data Exchange

Common Data Exchange (CDX) is a framework and terminology used by AEC professionals & project Owner / Operators to document project data interoperability requirements. CDX is not another data standard. Rather, the CDX approach looks to associate industry specific data standards with open-source exchanges, from file-based export and import of Portable Document Format (PDF) & Industry Foundation Classification (IFC), to direct-connected Extensible Markup Language (XML) and Application Programming Interface (API).


CDX puts the decision power back into the hands of the individuals who create, manage, and share data, while actively nudging project stakeholders towards a more refined subset of choices in lieu of untamed freedom and continued digital chaos.

CDX Template.websitedpng.png


The CDX playbook is intended to be used as a standards communication template. Unlike traditional standards that are carbon copied from one project to the next, a CDX playbook is uniquely specific to a project. However, the back-end of the digital worksheet will allow project teams to “reverse engineer” how a previous project developed their tools and data requirements, while also providing a fully vetted standard for projects that may be starting from a clean slate.


Playbook Steps Icons_Players.png

Stakeholders & Personas

Playbook Steps Icons_SharedPain.png

Systems & Documents

Playbook Steps Icons_Map It.png

Points of Exchange

Playbook Steps Icons_Savings.png

Risk & Opportunity

Playbook Steps Icons_New Standard.png

Shared Objective


Step 1 - WHO

Stakeholders & Personas

There are many different project stakeholders across the informational supply-chain of a project — from the project owners and investors, the project managers, and the design professionals, to the contractors and subcontractors, and eventually to facility management and operations. 

Regardless of the name given to each project stakeholder identified below, the key is to identify when each "player" is responsible for producing, sharing, accessing, reviewing, or approving a given piece of data as it flows across the project delivery supply-chain. Despite the theory that all project data lives in a Common Data Environment (CDE), the reality is that most project data is duplicated many times over between our disparate project delivery stakeholders.


Step 2 - WHAT

Systems & Documents

Currently, there are four active CDX initiatives in the pipeline. CDX-001 Report of Findings & Standards Recommendation is to be released in September 2019. Select the workflow or data handover challenge below for more information. 


In Support of XBRL-US


In Partnership with USIBD


Step 3 - WHEN

Points of Exchange

In order to motivate players to change old habits, we must visualize the waste that exists in the current state. Only then, can we begin to align different perspectives around the shared vision of an ideas state solution. 


Step 4 - WHERE

Risk & Opportunity

Insert NEW Content Here


Step 5 - WHY

Shared Objective

No longer is an RFI or submittal workflow considered anyone's Intellectual Property (IP).  The CDX Playbook provides a common language for project teams to communicate the workflow standards that led them to collaborate more effectively. Future CDX Playbooks should serve as a baseline template that project managers use to define project workflow and data standards.