Asset management and project delivery should both use a CDE solution and workflow that supports the production and delivery processes of ISO 19650-2. When a project ends, containers needed for asset management pass into the AIM, and the rest are kept read-only, for use in disputes and lessons learned, for as long as the EIR specify. The current revision of every container sits in one of three states (work in progress, shared or published), with an archive state serving as record and audit trail; moving between states requires approval and authorisation. Every container carries metadata, including a revision code (following an agreed standard such as IEC 82045-1) together with a status code showing what it may be used for, set by the author and changed through approval. A CDE may combine database and transmittal functions and be spread across several systems. The producer of a container remains responsible for it, sharing containers lowers coordination cost, and a complete audit trail is available.
This control maps to 1 controls across 1 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.
The graph holds this control, the 1 it maps to, and the evidence behind each claim, over MCP and REST.