The appointing party identifies OIR already in place, or sets up, documents and maintains OIR (Figure 2) that support what its organization does and how it runs its asset management system. OIR may originate with the appointing party or with its stakeholders (for instance the owner, where the appointing party operates the asset), and may include or build on existing requirements. Annex A.2 lists activities that generate OIR (asset accounting, planning and budgeting, capital investment, regulatory interfaces, maintenance and condition monitoring, emergencies, risk, safety, health and environment, and others) and gives example OIR such as life cycle cost comparisons, warranty expiry dates, service levels and asset replacement values.
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.