Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions process/folder_templates/platform/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -21,3 +21,4 @@ Platform
:hidden:

safety_analysis/platform_dfa.rst
safety_planning/index.rst
159 changes: 159 additions & 0 deletions process/folder_templates/platform/safety_planning/index.rst
Original file line number Diff line number Diff line change
@@ -0,0 +1,159 @@
..
# *******************************************************************************
# Copyright (c) 2025 Contributors to the Eclipse Foundation
#
# See the NOTICE file(s) distributed with this work for additional
# information regarding copyright ownership.
#
# This program and the accompanying materials are made available under the
# terms of the Apache License Version 2.0 which is available at
# https://www.apache.org/licenses/LICENSE-2.0
#
# SPDX-License-Identifier: Apache-2.0
# *******************************************************************************

.. _platform_safety_plan_template:

Safety Planning
###############

.. document:: Platform Safety Plan
:id: doc__platform_safety_plan
:status: draft
:safety: ASIL_B
:security: NO
:realizes: wp__platform_safety_plan
:tags: template

.. attention::
The above directive must be updated according to your Platform.

- Adjust ``status`` to be ``valid``
- Adjust ``safety``, ``security`` and ``tags`` according to your needs


:note: The Safety Management Plan shall be continuously maintained during the project. Deviations to the platform plan should be documented here.


Safety management / Platform Safety Plan
----------------------------------------

Purpose
+++++++

Description of the purpose of the Safety Management Plan.

Objectives and Scope
++++++++++++++++++++

Functional Safety Management Goals
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Description of the Functional Safety Management goals.

Functional Safety Management Scope
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Description of the Functional Safety Management scope.

Tailoring
^^^^^^^^^

Description of the tailoring of safety activities in the project.

Approach
++++++++

Safety Culture
^^^^^^^^^^^^^^

Description of the safety culture in the project.

Cybersecurity Interface
^^^^^^^^^^^^^^^^^^^^^^^

Description of the interface between functional safety and cybersecurity in the project.

Functional Safety Management Organization
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Description of the organization of the Functional Safety Management in the project.

*Project Roles*

Description of the project roles relevant for Functional Safety Management.

*Critical dependencies*

Description of critical dependencies relevant for Functional Safety Management.

*Risk*

Description of risks relevant for Functional Safety Management.

*Skills*

Description of skills relevant for Functional Safety Management.

Functional Safety Resources
^^^^^^^^^^^^^^^^^^^^^^^^^^^

Description of the resources relevant for Functional Safety Management.

Functional Safety Management Communication
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Description of the communication relevant for Functional Safety Management.

*Reporting*

Description of reporting used for Functional Safety Management.

*Escalation*

Description of escalation path used for Functional Safety Management.

Functional Safety Management Life Cycle
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Description of the functional safety management life cycle.

Functional Safety Requirements
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Description of functional safety requirements.

Functional Safety Schedule
^^^^^^^^^^^^^^^^^^^^^^^^^^
Description of the functional safety schedule.

Functional Safety Development
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Description of the functional safety development.

Functional Safety Verification
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Description of the functional safety verification.

Functional Safety Tool Management
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Description of the functional safety tool management.

Functional Safety Work Products
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Description of the functional safety work products.

Functional Safety Quality Criteria
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Description of the functional safety quality criteria.

Platform Safety Plan
++++++++++++++++++++

Functional Safety Management SW Platform Work Products
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

List of all relevant Functional Safety Management work products for the platform project.

Platform Management Plan - Documents Status Chart
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Original file line number Diff line number Diff line change
Expand Up @@ -21,8 +21,7 @@ Guidance

guideline_safety_management.rst
guideline_component_classification.rst
template_feature_safety_wp.rst
template_module_safety_plan.rst
templates_safety_plan.rst
template_component_classification.rst
template_safety_manual.rst
checklist_safety_plan.rst
Expand Down

This file was deleted.

Original file line number Diff line number Diff line change
Expand Up @@ -12,12 +12,28 @@
# SPDX-License-Identifier: Apache-2.0
# *******************************************************************************

Module Safety Plan Template
===========================
Safety Plan Templates
=====================

.. gd_temp:: Feature Safety Work Products Template
:id: gd_temp__feature_safety_wp
:status: valid
:complies: std_req__iso26262__management_6465, std_req__iso26262__management_6466, std_req__iso26262__management_6467, std_req__iso26262__management_6468, std_req__iso26262__management_6469

For the content see here: :ref:`feature_safety_wp_template`


.. gd_temp:: Module Safety Plan Template
:id: gd_temp__module_safety_plan
:status: valid
:complies: std_req__iso26262__management_5425, std_req__iso26262__management_5424, std_req__iso26262__management_6465, std_req__iso26262__management_6466, std_req__iso26262__management_6467, std_req__iso26262__management_6468, std_req__iso26262__management_6469, std_req__isopas8926__44341, std_req__isopas8926__44342, std_req__isopas8926__44611, std_req__isopas8926__4463, std_req__iso26262__management_5427, std_req__iso26262__management_6421

For the content see here: :need:`doc__module_name_safety_plan`


.. gd_temp:: Platform Safety Plan Template
:id: gd_temp__platform_safety_plan
:status: valid
:complies: std_req__iso26262__management_5425, std_req__iso26262__management_5424, std_req__iso26262__management_6465, std_req__iso26262__management_6466, std_req__iso26262__management_6467, std_req__iso26262__management_6468, std_req__iso26262__management_6469, std_req__isopas8926__44341, std_req__isopas8926__44342, std_req__isopas8926__44611, std_req__isopas8926__4463, std_req__iso26262__management_5427, std_req__iso26262__management_6421

For the content see here: :need:`doc__platform_safety_plan`
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,6 @@ Inputs
^^^^^^

#. Stakeholders for the Safety Management work products?
#. Who needs which information?
#. Which safety plans do we have?
#. Which other work products of Safety Management are important?
#. What tooling do we need?
Expand All @@ -42,22 +41,40 @@ Stakeholders

#. :need:`Safety Manager <rl__safety_manager>`

* main responsible to ensure ISO 26262 compliance in the project
* role definition in :doc:`/process_areas/safety_management/safety_management_roles`
* status reporting of safety activities
* Main responsible to ensure ISO 26262 compliance in the project
* Create/Maintain Safety Plan
* Approve Component Classification
* Approve Safety Package
* Approve Safety Audit
Copy link
Contributor

@attifunel attifunel Dec 11, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is the exact meaning here? Audit is assigned to an external entity, why Safety Manager should approve? Perhaps "plan" + "support"?

Copy link
Contributor Author

@PandaeDo PandaeDo Dec 11, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it makes sense that we will approve the external Audit. With this we can document that we agree on the Audit report. That the Safety Manager and the Process Community will support is defined in the workflow of the Safety Audit. Also relevant is, that we defined that all workflows has an approval. I hope this answered your question. If not I would invite to to "Eclipse S-CORE Safety Topics, Safety Management and Execution (Safety Manager Roles required)" every Tuesday, where we also can discuss your question with the complete community.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You need to see that in the context of the define workflows,
https://eclipse-score.github.io/process_description/main/process_areas/safety_management/safety_management_workflow.html#wf__p_fs_audit

improvement in concept description could be to include the workflows, where the Safety Manager has stakes in

* Approve Formal Reviews
* Approve Safety Manual
* Monitor/Verify Safety
* Impact Analysis of Change Request
* Status reporting of safety activities

#. :need:`Safety Engineer <rl__safety_engineer>`

* Supporting the Safety Manager
* Create/Maintain Safety Package
* Create/Maintain Safety Manual

#. :need:`Project Lead <rl__project_lead>`

* planning of development for platform projects
* Planning of development for platform projects
* Approve Safety Plan
* Approve Safety Release Notes
* Approve Impact Analysis of Change Request

#. :need:`Committer <rl__committer>`

* planning of development for module projects (as a Module Project Lead)
* performing safety related development
* Planning of development for module projects (as a Module Project Lead)
* Performing safety related development
* Create Component Classification

#. :need:`External Auditor <rl__external_auditor>`

* Performs independent safety audits and formal document reviews (e.g., safety plans, safety packages, safety analyses).
* Perform Safety Audit as independent safety audits
* Perform Formal 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.

Expand All @@ -82,6 +99,6 @@ 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 activities planning (who, when) we use a Issue Tracking System to create and manage issues, and monitor progress through a project management dashboard.

For the reporting (e.g. displaying the status of the work products) additional tooling is created.
Original file line number Diff line number Diff line change
Expand Up @@ -19,19 +19,31 @@ Getting Started
:id: doc_getstrt__safety_management_process
:status: valid

If you are elected as a :need:`Safety Manager <rl__safety_manager>` by the committers in the project:
This document describes the steps which need to be done to ensure Functional Safety according to ISO 26262 as used standard in the project.

* **Establish Planning and Reporting**
- Contact the :need:`Project Lead <rl__project_lead>` for your SEooC.
- Confirm that an Issue Tracking system is in place for planning and reporting.
Therefore guidelines :need:`gd_guidl__saf_plan_definitions`, :need:`gd_guidl__saf_man`, :need:`gd_guidl__saf_package`, :need:`gd_guidl__component_classification`
and a :need:`doc_concept__safety_management_process` are available.

* **Create Your Safety Plan**
- Follow the workflow described in :need:`wf__cr_mt_safety_plan`.
General Workflow
****************

* **Understand Your Role and Responsibilities**
- Review your role description in :need:`rl__safety_manager`.
- Familiarize yourself with the Safety Management workflows in :ref:`workflow_safety_management`.
One goal of the Safety Management Process is to ensure that the project is following the defined processes and
that the evidence of Functional Safety can be shown according to the requirements. The Safety Management process
follows an continuous approach.

* **Explore Supporting Processes**
- Read the development and supporting process descriptions in :ref:`process_description`.
- Check relevant sections of :need:`wp__platform_mgmt`.
The workflows are defined in the :ref:`workflow_safety_management` section. The following workflows shall be executed continuously:

* Create/Maintain Safety Plan
* Create/Maintain Safety Package
* Create/Maintain Safety Manual
* Monitor/Verify Safety

Additional to the continuous workflows the following workflows shall be executed according to the project needs:

* Create Component Classification
* Perform Safety Audit
* Perform Formal Reviews
* Impact Analysis of Change Request

For open issues the issue tracking system is used to track the issues and to ensure that they are resolved in time.
The issue tracking system is defined in the :need:`wp__issue_track_system`.
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,7 @@ Safety Management Workflows

| The Safety Manager in the project is NOT responsible to provide the argument for the achievement of functional safety.
| But the Safety Manager creates and maintains the safety package in the sense of a collection of safety related work products.
| The generation and the maintainance of this draft safety package shall be automtated as much as possible.
| The generation and the maintenance of this draft safety package shall be automated as much as possible.
| It does not contain the final argumentation of the safety of the product.
| As the safety package is only a collection of work products, the safety plan (template) can be used for documentation.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ Safety Management Work Products

Plan to manage and guide the execution of the safety activities of a project including dates, milestones, tasks, deliverables, responsibilities (including the Safety Manager appointment) and resources.

This platform safety plan also takes into accout the eclipse organization's rules relevant for safety development.
This platform safety plan also takes into account the eclipse organization's rules relevant for safety development.

Guidelines on how an change impact analysis shall be concluded on each item or element involved together with it's connected items or elements.

Expand Down
Loading