The appointing party identifies and records foreseeable trigger events: points in the operational phase at which new or revised information about an asset will be created or required. Several may happen at once, similar assets may share trigger events yet call for different responses, and some (severe weather, geological events) have nothing to do with the assets themselves. Annex A.3 lists examples ranging from a decision to start managing an existing asset's information, performance evaluation, inspection, planned or reactive maintenance and minor or major works, through new, replaced or end-of-life assets and emergency response, to changes in value, regulation, regulator demands, organizational requirements, owner, operator or maintainer.
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.