Procedures are planned before any modification or retrofit. The work starts only from an authorised request under 6.2.8 that names the affected hazards, the proposed hardware and software change and the reasons. An impact analysis assesses the effect on functional safety of every safety system, including a hazard and risk analysis sized to decide how far the lifecycle phases must be repeated, the effect of other concurrent modifications, and safety during and after the work; it is documented, and authorisation depends on it. Any modification affecting functional safety returns the work to the appropriate lifecycle phase, with all later phases repeated under the standard for the SILs involved. Chronological records of all modifications and retrofits reference the request, the impact analysis, the data and results re-verified and re-validated, and every affected document.
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.