The appointing party should know which information about its assets or projects it needs in order to meet its objectives, be able to communicate those requirements to the people whose work they specify or inform, and say why it wants each deliverable: an asset register; supporting compliance and regulatory duties; managing risk; and answering business questions (capacity and use, security and surveillance, renovation, predicted and actual impacts such as carbon, energy, waste and water, operation, maintenance and repair, replacement and recycling, decommissioning and disposal). Appointed parties may add requirements and pass some on. Requirements for the delivery phase are stated by project stage, and those for the operational phase by foreseeable trigger events.
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.