Common Data Environment (CDE) is not about the software only. I have seen lots of discussions about the best platform and how to choose it. However, the essential part of implementing a CDE is designing the workflow.
Every project has its specific structure. As an information manager, you should create a process map that specifies the actual flow of the information and the approval gates and enhance the accessibility, traceability, and credibility of the information in your CDE.
Firstly, you should define the various states of the information. These states are usually; Work in Progress, shared, published, and archived. However, these states may differ based on the actual project's information workflow.
Secondly, define the required metadata of the files used to classify them; disciplines, assets, projects, authors, etc.
Next, you have to set up the revision numbering system and add metadata. The revision number should express the document type, whether it's contractual or not. It should also differentiate between the work in progress revisions and the shared revisions.
Finally, it would help if you defined the status codes that will reflect the file's suitability; for review, coordination, information, etc.
Now you are ready to select the Common Data Environment that can fulfil your workflow and gives you the flexibility to create, assign, filter, and control the metadata.
The below photo shows the CDE file states as seen in ISO 19650-1. For further information, I recommend reading ISO 19650-1 & ISO 19650-2.
#iso19650 #cde #software #aconex #bim360 #acc #aec #projectwise #bim
2 Comments
