Concept Description

Safety Management Concept		status: valid
relates to: wf__cr_mt_safety_plan, wf__cr_comp_class, wf__cr_mt_safety_package, wf__p_fs_audit, wf__p_formal_rv, wf__cr_mt_safety_manual, wf__mr_vy_safety, wf__impact_analysis_change_request
doc_concept__safety_management_process		Concept Definition

In this section a concept for the Safety Management will be discussed. Inputs for this concepts are mainly the requirements of ISO26262 “Part 2: Management of functional safety”.

Key concept

The Safety Management Plan establishes a comprehensive strategy for managing all identified safety activities throughout the entire project life cycle. It ensures that these activities are executed in a systematic, effective, and repeatable manner, providing clear guidance on responsibilities, processes, and control measures. This approach supports risk mitigation, regulatory compliance, and continuous improvement, enabling the project team to maintain safety standards consistently from initiation to completion.

Inputs

1. Stakeholders for the Safety Management work products?

2. Who needs which information?

3. Which safety plans do we have?

4. Which other work products of Safety Management are important?

5. What tooling do we need?

Stakeholders

1. Safety Manager (rl__safety_manager)

   • main responsible to ensure ISO 26262 compliance in the project

   • role definition in Roles

   • status reporting of safety activities

2. Project Lead (rl__project_lead)

   • planning of development for platform projects

3. Committer (rl__committer)

   • planning of development for module projects (as a Module Project Lead)

   • performing safety related development

4. External Auditor (rl__external_auditor)

   • Performs independent safety audits and formal document reviews (e.g., safety plans, safety packages, safety analyses).

   • Verifies compliance with defined safety processes and standards.

   • Reports audit results and decides on pass/fail status.

Safety Plans

The SW platform project defines two levels of planning: platform and module. There will be one safety plan on platform level and several safety plans on module level (one for each module). This safety planning follows how development teams and repositories are organized in the project. Each of these safety plans “creates” one SEooC. The Platform Safety Plan (wp__platform_safety_plan) exists only once and is part of the Platform Management Plan (wp__platform_mgmt).

Safety Management Work Products

Apart from the safety plans the main work products of Safety Management are:

• Safety Manual (wp__platform_safety_manual) - the safety manual defines the requirements for safe usage or integration of the SW platform (or its individual modules)

• Formal Document Review Reports (wp__fdr_reports) - on safety plan, safety package and safety analyses, according to ISO 26262 requirements

• Safety Package (wp__platform_safety_package) - the safety package contains the released work products planned in the safety plan, it does not contain the safety argumentation. By this the project ensures it does not take over liability for the SW platform (or its individual modules). But it enables the user to integrate the SW platform (or its individual modules) in their safety case.

Safety Management Tooling

For the safety planning and safety manual a “Docs-as-Code” approach is used and within that approach Id will be used for referencing.

For the activities planning (who, when) we use a Issue Tracking System to create and manage issues, and monitor progress through a project managemnet dashboard.

For the reporting (e.g. displaying the status of the work products) additional tooling is created.