The safety manager shall be responsible for planning and coordinating the functional safety activities the organization participates in, for maintaining the safety plan and for monitoring progress against it; responsibilities for performing safety activities shall be assigned and communicated per 5.4.2.7 and 5.4.4; the safety plan shall be referenced in or included distinguishably within the project plan and shall specify the planning of activities and processes including the application of the project-independent safety activities of clause 5, the tailored activities per 6.4.5, the activities required by parts 3 to 6, the supporting processes of part 8 including the development interface agreement with other parties, the integration and verification activities of parts 3 to 6 and part 8 clause 9 and the safety validation of part 4 clause 8, the schedule of the confirmation reviews, the functional safety audit and the functional safety assessment per 6.4.9 to 6.4.12, the analyses of dependent failures per parts 3 to 6 and part 9, the proven in use argument and the confidence in software tools where applicable; each planned activity shall state its objective, dependencies, responsible persons, resources, start, end and duration, and the work products it produces; where an item, its environment or an element is modified the reference lifecycle shall be tailored to the impact analysis, the affected work products identified and reworked, and gaps in safety documentation closed; the safety plan shall be updated progressively at least at the start of each phase, its work products kept current to production release, and in distributed developments both customer and supplier shall plan their own safety activities.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.