Operation and maintenance procedures specify the routine actions that keep the as-designed functional safety, including scheduled replacement of limited-life parts such as fans and batteries; the actions and constraints during installation, start-up, operation, testing, disturbances, faults and shutdown that prevent unsafe states or reduce consequences; the records of system failure and demand rates and of audits and tests; maintenance after faults, covering diagnosis and repair, revalidation, reporting, and revalidation when original items are obsolete or replaced by new versions; how maintenance performance, failures and their analysis are reported; and the tools for maintenance and revalidation and how they are kept. The procedures are improved continually from audit and test results; routine maintenance is set by a systematic method (such as fault tree review or FMEA) finding unrevealed failures in every safety-related element from sensor to final element; the procedures are assessed for impact on the EUC; and Table B.4 techniques are applied to keep faults out of operation and maintenance.
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.