01
An engineer can work on three jobs and spend the week in three clients’ common data environments, or CDEs. When a job closes, the firm needs a record of what it issued. Years later, the owner needs to open the model and see what it was approved for. Infrastructure Client Group on project CDEs
02
Say the firm sends an IFC to the owner. If the two CDEs handle revisions and status differently, someone may have to enter that information again and match the file to its approval. That work comes back when the owner moves the records to another system. UK BIM Framework guidance on transferring metadata
03
The engineering firm keeps its working models in a system it controls and shares the versions it’s responsible for issuing. The owner keeps the approved model and its release record in its own system. Both teams can consult the records they’re entitled to keep after the project account closes.
04
The firm can keep review in its existing CDE. A connector could send an issued model and its approval record over OCI. The owner can load quantities from that model into its lake or warehouse and issue a table back through the same exchange, with a link to the model it came from. OCI Distribution Specification
05
In the pilot, an author can submit a draft. Both the CDE and the registry API must block an unauthorized release. Have the designated people authorize and accept the model, then issue a second revision. The owner should still be able to verify the first approval.
06
Start with the two systems the teams already use. Once the release has crossed, disconnect the source. Ask the owner to open the exact model and show who approved it and for what use. Then try the same exchange with a compatible replacement on one side.