Safety Management#

Concept#

Safety Management Concept
status: valid
security:
safety:
status: valid
relates to: wf__cr_mt_safety_plan, wf__cr_comp_class, wf__cr_mt_safety_case, wf__p_fs_audit, wf__p_confirm_rv, wf__cr_mt_safety_manual, wf__mr_vy_safety
doc_concept__safety_management
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”

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. Technical Lead (rl__technical_lead)

    • planning of development for module and for platform projects

    • status reporting of safety activities

  2. Safety Manager (rl__safety_manager)

    • he is the main responsible for the safety management work products (as in Work products). See also his role definition in Roles.

  3. External Auditor (rl__external_auditor)

    • understand activities planning, processes definition and execution

  4. “Distributor” (external role)

    • use the platform in a safe way

    • integrate the platform in his product (distribution) and safety case

    • plan this integration (also in time)

    • qualify the SW platform as part of his product

Safety Plans#

This 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 is how we organize our development teams and repositories. Each of these safety plan “creates” one SEooC. The Platform Safety Plan exists only once and is part of the Platform Management Plan of S-CORE.

Safety Management Work Products#

Apart from the safety plans the main work products of safety management are (see also the link to workflows below):

  • 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)

  • Confirmation Reviews (wp__cmr_reports) - on safety plan, safety case and safety analyses, according to ISO 26262 requirements

  • Draft Safety Case (wp__platform_safety_case) - the safety case compiled is draft as it does not contain the safety argumentation. By this the S-CORE project ensures it does not take over liability for the SW platform (or its individual modules). But it enables the distributor to integrate the SW platform (or its individual modules) in his safety case.

Safety Management Tooling#

For the safety planning and safety manual, sphinx-needs will be used for referencing.

For the activities planning (who, when) we use github issues and monitor these in github projects.

For the reporting (e.g. displaying the status of the work products) additional tooling is created (see Safety Management Process Requirements)

Getting started#

Safety Management Get Started
status: valid
security:
safety:
status: valid
doc_getstrt__safety_management
Getting Startet

In case you are appointed as a Safety Manager (rl__safety_manager) by the Project Lead (rl__project_lead) in the S-CORE project:

  • Contact the Technical Lead for your SEooC to establish planning and reporting (the TL should already have established a Github project for planning)

  • Create your safety plan according to WF__cr_mt_safety_plan

  • Make familiar with your role description and the other workflows of safety management (see below)

  • Make familiar with the development and supporting process descriptions in Process plus the relevant sections of the Platform Management Plan

Workflows#

Guidance#