The appointing party establishes, or follows suitable existing, processes that keep the AIM maintained for an appropriate period, covering: allocating tasks for producing, maintaining, retaining, transmitting, accessing, assuring and archiving information; transferring maintenance duties or AIM ownership on a change of owner or appointing party; deciding what the information contains and means and which formats and media carry it for representing, keeping, sending and retrieving it; version control, integrity checks, verification against the AIR and updating; improving quality in support of organizational objectives; archiving or disposing of obsolete, unreliable or unwanted information; archiving the AIM in whole or part at decommissioning or end of life; meeting ISO 19650-5 security requirements; safe storage from which information can readily be retrieved, protected by preventive upkeep from physical or technological decay and from obsolescence; and keeping the agreed alignment between the AIM and the physical asset. The period can follow ownership, occupancy, operating or asset management agreements and strategic, contractual, statutory, safety, environmental, social or fiscal constraints; alignment can be stated as the allowed time lag between a change to the asset and its reflection in the AIM.
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.