The appointing party establishes, or reviews and adapts, the AIM to hold everything the AIR specify for the assets from 5.1.3, as a federated model that can include content from different information providers; it weighs the suitability of existing information systems, the ability to integrate or link PIM information at any point in a project, legal requirements on storing information (especially personal information), the ability to keep information used for analysis and reporting apart from information being updated by delivery teams, and the need for a security-minded design and operation drawing on ISO 19650-5. The AIM can span new and existing systems if they are linked and governed through the CDE workflow; no storage technology is prescribed.
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.