Safe planning

Managing the data generated by large construction projects is a gigantic task. Teams therefore need centralized data access and visibility to retrieve information at the right time. A Common Data Environment (CDE) is an invaluable tool to streamline the complexity of large construction and infrastructure projects and improve the sustainability of these assets throughout their lifecycle.

7 Best Practices

1. the right access at the right time: A shared data environment allows project stakeholders to start collaborating sooner, but releasing project data too early or too late can lead to confusion. The ideal CDE solution should allow users to be divided into groups so there is control over who has access to what and when they can view it. For example, one group can be set up for owners, another for architects, and another for tradespeople. BIM managers can then define what data each group can view and when, and add or remove it as the project progresses.

2. support the need for individual CDEs.: It may sound counterintuitive, but in some situations there are good reasons for maintaining separate CDEs. Subcontractors that need to perform intensive design, estimating, and cost analysis work may want to maintain their own CDEs to protect their cost data and streamline the amount of information they provide to the general contractor or owner. In this case, they import the released design model into their own CDE, perform their analyses, and send their detailed models back to the general contractor. This approach reduces the amount of data generated on a larger project, while allowing the subcontractor to centralize data management and sharing between internal teams.

3. Mapping your data: A good CDE preserves the quality of the data, regardless of the program used to create the original model and the systems used by the various team members to revise it. Viewers of the CDE model should not remove the data from the original. Instead, they should translate it so that it can always be viewed in a format that is faithful to the original. To do this, the fields must be aligned between systems, a process known as data mapping.

As a by-product of data mapping, users gain a better understanding of the information collected. Data mapping forces project stakeholders to think about what information really needs to be extracted from the various files and what attributes should be assigned within the CDE.

4. automate workflows using APIs: A CDE that supports application programming interfaces (APIs) makes it possible to connect to any number of systems - from ERP systems to document management tools. With this connectivity, automations can be set up to improve efficiency and data accuracy. Using a tool such as Trimble Connect, for example, planners can automate workflows with the ERP and CDE to trigger payments to surveyors once they have completed their task list in the CDE. API connectors also allow technology investments to scale.

5. Only collect data that is really needed: After design and construction, project data can be used by owners to more efficiently operate and maintain the buildings they create, and by designers and contractors during retrofits, remodels, and upgrades. However, this data is only valuable if it is easily accessible and relevant. To avoid data overload, users should configure their CDE to capture only the data that is necessary for the project and useful to the teams involved.

For example, you can create your own property sets consisting of the inputs used to create your model. Within these property sets, you can create fields or properties that can be assigned specific attributes. If the new field requires a numeric input, these can be set as parameters and even the minimum or maximum value can be limited.

6. open standards for sharing: To truly benefit from centralized data, you need a CDE that treats all data the same, regardless of which program or tool it comes from. Otherwise, planners run the risk associated with manual data entry and poor data integrity. A CDE that supports open standards for data sharing makes it possible to facilitate workflows with any design tool without losing or corrupting data. And that's what makes a truly software-independent project possible. Open standards allow each organization to use the technology that best suits its needs and budget, and still collaborate fully without the need for workarounds.

7. working with a single continuous model: Version control can be a problem when each stakeholder works with their own model. With an object-oriented CDE, information can be exchanged directly between the model and the own internal design tools via APIs.

With everyone involved working on a single end-to-end model, rather than uploading new files every time a change is made, version control is no longer a problem. As an added bonus, the learning curve for adoption is even shorter than most other CDEs because users make updates with the tools they are currently using. This improved model interactivity also supports Level 3 BIM maturity.

Equipping for the success of a robust data environment

Some CDEs offer more features than others, allowing you to create a single source of truth about each project and get greater value from your data. If the CDE is only for data storage and offers little else, you may be missing out on all the benefits that a single source of truth can provide, such as increased productivity, efficiency and sustainability, and reduced risk. When all stakeholders have access to the right data at the right time, new automated processes can be introduced to increase productivity; data transparency can be increased to reduce risk. In addition, stakeholders can provide the right data at the right time to make better and faster decisions, gain meaningful insights, and increase efficiency throughout the project lifecycle (red./sgr).

Source: Trimble