Set up the common data environment
Stand up the common data environment, load the information containers with the right status, and aim coordination at the shared area.
How it works, step by step
3 steps across the platform - what you do at each one, and why it matters.
Define the status states
CDEIn the CDE, define the status states, work in progress, shared, published and archived, and lay out the folder structure.
Why: If everyone reads and writes to their own copies, someone builds from a superseded drawing. The states tell you what is safe to use and what is still a draft.
Load the containers
Project FilesIn Project Files, load the information containers, models, drawings and documents, and set each one to its status.
Why: A container with no status is a trap, nobody knows if it is checked or just parked. Correct status is what lets the next person trust the file.
Federate the models
CoordinationIn Coordination, point the model federations at the shared area so everyone coordinates against the same set.
Why: Clash checking against private working models finds clashes that are already fixed and misses the ones that are not. The shared area is the single source everyone federates from.