The Holy Grail for Collaboration: A Connected Common Data Environment

A report from Dodge, Data & Analytics found that manual processes in cross-platform workflows negatively impact the success of delivering construction projects. Double data entry incurs an average 73% productivity loss, 70% slowed info workflows and 62% frequency of data entry errors [1].

Automating these workflows between platforms reduces these inefficiencies towards zero.

Where is manual input required in a CDE?

On any given digitally enabled construction project, the CDE is distributed between different software platforms typically used by different teams, or in different project phases. The variance in platforms used on a project comes as a result of differing needs: some are more suited to certain domain-specific requirements than others, and/or teams may already be trained to use specific software, and/or they may be locked into it commercially.

“There is a potential misconception that the CDE is more about technology and less about workflows. In fact, it is fundamental that workflows are developed first and solutions are selected to facilitate the workflow.”[2]

Teams are continuously collaborating via workflows that traverse different platforms, and using more than one creates digital thresholds between them that need to be overcome. In the context of a CDE, digital thresholds create risks and inefficiencies in the construction project due to the manual information exchange required to execute workflows across them. This ultimately fragments the collaborative experience and impacts productivity.

More complex workflows bring with them more risks, especially when humans manually carry out information exchange processes within them. Some workflows between teams require that documents are transferred between platforms. A requirement to exchange documents across platforms spawns document control tasks, which are manual processes and not always trivial.

How do manual tasks create problems?

Submittals can be large (for example, drawings from the design to client team at the end of the detailed design phase), and metadata needs to be accurately interpreted from the source software platform and inputted to the target software platform. This takes time and an understanding of the platforms involved.

Figure 1

Each software platform speaks its own unique language, defining documents, metadata and functionalities differently. To ease information exchange, it is highly recommended to adopt ISO 19650 to ensure compliance with an agreed international standard across all platforms being used. 

Regardless of the use of standards, when manual processes are required, important metadata is inevitably lost as it cannot be easily transferred with the documents, or at all. Timestamps and key dates, user interactions, review information, issue comments, document system IDs etc. are important pieces of information that are required to achieve continuity in document history.

There are issues not only with the outcome of manual processes, but from the manual transfer tasks themselves. Documents downloaded to a local machine and uploaded to another software platform often result in unpredictable behaviours which interrupt, halt or restart the transfer process, in turn losing or corrupting information, creating risks for the project and often resulting in delays. Some issues reported with manual transfer tasks include:

  • Unpredictable network performance: The maximum download and upload speed of the local computers network can be slow and variable, depending on location and restrictions from the ISP.

  • Prevents the computer from being used for other tasks:  While uploading/downloading, sometimes the platform being used cannot be used for other functions.

  • Technical failures: Any dropped connection could cause the download/upload to fail and it would need to be restarted. Technical failures can include:

    • Internet issues: Internet network unavailability and router issues.

    • Computer configuration issues: Local machine going to sleep, restarting or performing updates unexpectedly.

    • Task disruption: Accidental clicks into other parts of the platform, closing the browser window, or the platform going down

    • Network changes: Connecting/disconnecting VPN

Additionally, documents that exist outside of the CDE as a result of the manual process introduce security risks. Confidential information residing on local machines can be recovered even after deletion and should a computer be removed from the office, these files are immediately at risk of getting into the wrong hands.

What is a seamlessly connected CDE?

Considering all of these factors, the key to realising the envisioned "holy grail" CDE is to establish seamless connections. By leveraging automation technologies to connect the various platforms, distributed teams can collaborate effectively through workflows within the CDE and maintain information integrity in a secure manner. This reduces the risks associated with manual processes, eventually resulting in no risk & no inefficiencies. 

A seamlessly connected CDE generates trust amongst teams and can improve the project productivity drastically in the following ways:

  1. Information is rich and easier to find in the software being used;

  2. Standardised workflows are automated and consistent. For example, S4 status drawings could automatically be shared with the client team for approval, and/or once approved, A-status drawings are automatically published; 

  3. Document history is traceable and trustworthy, which compliments delivery of the Golden Thread of Information[3];

  4. Correspondence from various sources can be issued and saved in project records

BIMLauncher provides out-of-the-box configurable connections for the industry leading platforms that are used as a part of any typical CDE[4]. Our technology helps construction projects realise the potential value of the distributed CDE for themselves, allowing teams to work within their platform of choice, and accelerates the efficiency of collaboration between teams working on these projects. 

We are proud to share our progress and discuss this topic at the BIM Coordinator Summit for the second year in a row and we look forward to a productive and connected future.


References

  1. Dodge, Data & Analytics. (2023) Connecting Owners and Contractors. How Technology Drives Connected Construction. Available at: https://learn.assetlifecycle.trimble.com/e-books/connecting-owners-and-contractors-how-technology-drives-connected-construction 

  2. The UK BIM Framework. (2020) Information management according to BS EN ISO 19650 Guidance Part C, Facilitating the common data environment (workflow and technical solutions) [online], Edition 1. Available at: https://ukbimframework.org/wp-content/uploads/2020/09/Guidance-Part-C_Facilitating-the-common-data-environment-workflow-and-technical-solutions_Edition-1.pdf

  3. NBS. (2020) What is the Golden Thread? [online]. Available at: https://www.thenbs.com/knowledge/what-is-the-golden-thread

  4. www.bimlauncher.com

Images
Figure 1: Dodge, Data & Analytics. (2023) Connecting Owners and Contractors. How Technology Drives Connected Construction, page 5. Available at: https://learn.assetlifecycle.trimble.com/e-books/connecting-owners-and-contractors-how-technology-drives-connected-construction