Confirm by examination and objective evidence that the system with its SRACs complies with the RAMS requirements and confirm or update the safety case; per 6.7.3 and depending on the safety integrity, review and update the hazard log for residual hazards, review the safety plan's continued applicability, and update the safety case to justify compliance with the system safety requirements; consider the need to demonstrate safety before any probationary operation; establish and implement a process for acquiring and evaluating operational and maintenance data as input to improvement; evaluate the adequacy of any phase 8 impact analysis; derive and collect all SRACs for operation, maintenance and decommissioning. The validation report identifies the system, documents, tools, equipment with calibration data and simulation models used, confirms the validation plan was met with deviations recorded and justified, evaluates requirements tracing, corrective-action handling under change management, test and analysis coverage of the requirements, the validator's own tests, the qualification against the technology standards, and concludes whether the system fulfils its safety requirements for its intended use. Deliverables: the RAM and safety validation reports, the hazard log as updated, safety plan, safety case and SRACs, the operational data process.
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.