CDX Scenarios
A common data exchange (CDX) scenario supports the graphical documentation of current pain points and the desired future state of a specific information transaction between two or more project stakeholders. Following the framework of CDX, impacted stakeholders will gather to discuss the document of record (DOR) in question by inviting the individual personas that utilize applications to generate, regulate, store, or share the DOR at different points of exchange (PoE). At a given PoE, the persona is either sharing data internally with their stakeholder’s system of record (SOR), or externally with another stakeholder’s SOR. Applying this shared language and approach to integration standards will unlock new industry benchmarks that focus on the leading indicators of project performance.
Key Terms to Know For a comprehensive overview of CDX terms and relationships, please review pages 13-19 of the most recent RFI Report.
-
A document of record (DOR) is the project-level form, report, or certificate that evolves through multiple stages and is exchanged between multiple stakeholders.
-
A stakeholder is the business or government entity that is responsible for originating, providing, aggregating, controlling, or consuming the project DOR.
-
A system of record (SOR) is the physical or virtual location where a project's information and DOR are retained.
-
An application is a tool or system that is used to enact and control changes to an SOR or DOR. Applications exist in one of three form analog, digital, and interoperable.
-
An analog SOR application is a physical information storage device that lacks any capacity for digital storage (i.e., - Filing Cabinet, Drawing Rack)
-
A digital SOR application is an electronic information storage device that can retain digital DOR and information, but lacks a direct connection with other SOR (i.e., -Personal Computer, Local Network Hard Drive)
-
An integrated SOR application is a cloud-connected information storage device with a defined data structure and documented API exchange capabilities.
-
A persona is the individual employed by a project stakeholder to perform one or more activities within the CDX scenario.
-
An exchange activity is the recorded transaction of project information between two or more stakeholders. Similar to applications, exchanges can be analog (handwritten/typed), digital (spreadsheet, access database), or interoperable (cloud/API connected). Information sent or released
to an external stakeholder is represented by a male plug. Information received, submitted, or retrieved as part of the exchange is represented by a female plug.
Learning to speak CDX, like any other language, does not happen overnight. You have to start with the basics.
Building the 'Scene'
A completed CDX scenario should communicate the following pieces of information:
HOW is the data produced, exchanged, and retained?
-
Analog (physical, human-readable)
WHEN is the data reviewed or qualified?
-
Pre-validation (conditional)
-
Post-verification (cognitive)
WHO is impacted in the scenario?
-
Stakeholders
-
Personas
WHERE is the data being exchanged?
-
Authoring Application
-
Exchange Application
-
System of Record
WHAT information is being exchanged?
-
Document of Record
-
Transmittal Record
HOW is the data produced, exchanged, and retained?
-
Analog (physical, human-readable)
-
Digital (semi-structured, malleable, offline)
-
Integrated (structured, interoperable, real-time)
Step 1
Pick a Shared Pain
While a CDX kickoff could map out multiple documents and exchanges, each scenario begins and ends with a core DOR that is producing the #SharedPains.
Some examples include:
-
RFIs
-
Submittal reviews
-
Progress reports
-
Digital twin verifications
How to Develop a CDX Scenario
A CDX should be tailored to the specific project and stakeholders involved.
Each stakeholders’ standard applications and preferences will shape how the
CDX-validated scenario is defined. To develop a CDX scenario, follow these steps:
Step 1
Pick a Shared Pain
Step 2
Identify WHO
is impacted
Step 3
Map it out!
Step 4
Score the Savings
Step 5
Set the
new Standard
CDX Scorecard & Certification Levels
This certification process exists to promote transparency and accountability between construction tech and construction stakeholders by introducing and upholding actionable definitions built upon market adoption, stakeholder acceptance, verifiable ROI, and demonstrable process improvements.
Certification Criteria
Level | Achievement Threshold | Submission Requirements |
|---|---|---|
CDX-Listed | Demonstrate active CDX interoperability between two or more stakeholder systems. Must provide documentation of accumulated adoption on five or more customers. | Submit list of project use cases with reference contact information. Review/Approve CDX scenario documentation. |
CDX-Validated | A CDX-Listed integration with over 1,000 annual transactions that submits an anonymized report of CDX usage and project accumulation over time. | Interview testimonials from representatives of the different stakeholders involved. |
CDX-Verified | Demonstration of CDX interoperability adoption that also assures compliance with broader reporting standard or collaboration protocol (i.e. - ISO 19650, CMMC). | Note - this level of certification is not yet feasible in the North American Construction Market. A shift in government policy or business paradigm is first required. |
CDX-Listed Scenario Documentation
The following is an example of the CDX-Listed Workflow Scenario Documentation required for certification. This example is the documentation created for the Newforma Connect by Ryvit on Procore App Market.
![[CDX-Listed]_Newforma_Connect_by_Ryvit_on_Procore_App_Mkt.jpg](https://static.wixstatic.com/media/8493e3_6e7801c14acc45b0a48026c9888e39e9~mv2.jpg/v1/fill/w_770,h_577,al_c,q_85,usm_0.66_1.00_0.01,enc_avif,quality_auto/%5BCDX-Listed%5D_Newforma_Connect_by_Ryvit_on_Procore_App_Mkt.jpg)