Navigating the Complexities of Implementing a Common Data Environment

Navigating the Complexities of Implementing a Common Data Environment

In the ever-evolving landscape of project management and data handling, the implementation of a Common Data Environment (CDE) is a topic of paramount importance. Recently, we had the opportunity to engage with a large client organisation, delving deep into the practicalities and challenges of procuring a CDE.

The client initially considered mandating a single CDE across all project teams. However, our experience suggests a more nuanced approach is often required. Both design teams and general contractors tend to favour systems that allow them to manage risk effectively and maintain control over their workflow. This preference often leads to the use of closed systems, which can be at odds with the idea of a client-mandated, unified CDE.

A key point of discussion was the realisation that a mandated CDE might not streamline processes as anticipated. For instance, general contractors prefer reviewing and managing information like Requests for Information (RFIs) and submittals within their systems before sharing it with clients or design teams. This control is crucial for maintaining quality and minimising risk but can lead to a lack of real-time visibility for the client.

Moreover, the diverse range of existing tools in the industry, such as Autodesk for design teams and Procore for site management, poses another challenge. Teams are often reluctant to move away from these familiar tools due to the costs and time associated with training and onboarding. This reality necessitates a reconsideration of the one-size-fits-all approach to CDE implementation.

We advised the client to approach software vendors with caution. The industry's findings contradict the notion that one CDE can meet all project needs, a claim often made by vendors. Our client appreciated this insight, recognising the value of independent, informed advice.

Concluding our session, the client decided to review their CDE implementation strategy with other project delivery teams. This approach marks a shift towards a more collaborative and practical exploration of CDEs, considering the unique needs and challenges of each stakeholder involved.

In summary, the successful implementation of a CDE requires a careful balance between standardisation and flexibility. It demands an understanding of the varied needs of different teams and a critical evaluation of vendor claims. As we continue to navigate these complexities, our commitment remains to provide our clients with the insights and guidance necessary for informed decision-making in this crucial domain.