Description
Most common data environments (CDEs) are set up for the delivery team. They solve coordination during design and construction, then get handed to the owner who lives in them for decades. The folder structures and workflows that suited the project rarely fit how a facilities team works. This session will be a practical guide for owners. We'll cover what to specify before a project starts, the contract language that protects your access to the data, where standard handovers break down, and how to organize information so it stays useful over the life of the asset. You'll leave with a checklist you can apply to your next project, whether you're standing up a CDE for the first time or trying to fix one you inherited.
Key Learnings
- Learn about the CDE requirements an owner should set before a project begins.
- Learn how to draft the procurement and contract language that secures ongoing access to project data and models beyond the delivery team.
- Learn about points where a standard project-to-operations handover breaks down, and discover what to ask for to prevent data loss.
- Learn how to organize handed-over information so a facilities team can find and use it across the full life of the asset.