Safety Management Workflows

Create/Maintain Safety Plan		status: valid
contains: gd_guidl__saf_plan_definitions, gd_temp__feature_safety_wp, gd_temp__module_safety_plan has: doc_concept__safety_management_process, doc_getstrt__safety_management_process needs input: wp__platform_mgmt, wp__issue_track_system, wp__sw_component_class, wp__tailoring outputs: wp__module_safety_plan, wp__platform_safety_plan responsible: rl__safety_manager approved by: rl__project_lead satisfied by: gd_req__safety_doc_status, gd_req__safety_wp_status
The Safety Manager is responsible for the planning and coordination of the safety activities for the platform. The Safety Manager creates and maintains the safety plan. For this a template exists to guide the creator of the safety plan.
wf__cr_mt_safety_plan		Workflow

Create Component Classification		status: valid
contains: gd_guidl__component_classification, gd_temp__component_classification has: doc_concept__safety_management_process, doc_getstrt__safety_management_process needs input: wp__platform_mgmt, wp__issue_track_system outputs: wp__sw_component_class responsible: rl__committer approved by: rl__safety_manager satisfied by: gd_req__safety_doc_status, gd_req__safety_wp_status
The Safety Manager shall approve the OSS component classification performed by an expert on this component.
wf__cr_comp_class		Workflow

Create/Maintain Safety Package		status: valid
contains: gd_guidl__saf_package, gd_temp__feature_safety_wp, gd_temp__module_safety_plan has: doc_concept__safety_management_process, doc_getstrt__safety_management_process needs input: wp__module_safety_plan, wp__platform_safety_plan, wp__issue_track_system outputs: wp__module_safety_package, wp__platform_safety_package responsible: rl__safety_engineer approved by: rl__safety_manager
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. 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.
wf__cr_mt_safety_package		Workflow

Perform Safety Audit		status: valid
contains: gd_guidl__saf_plan_definitions has: doc_concept__safety_management_process, doc_getstrt__safety_management_process needs input: wp__module_safety_plan, wp__platform_safety_plan, wp__module_safety_package, wp__platform_safety_package outputs: wp__audit_report responsible: rl__external_auditor approved by: rl__safety_manager
The external auditor is responsible to perform a safety audit. The Safety Manager and the process community shall support the external auditor during this. The Project Manager and and the Safety Manager shall approve the audit report.
wf__p_fs_audit		Workflow

Perform Formal Reviews		status: valid
contains: gd_guidl__saf_plan_definitions, gd_chklst__safety_plan, gd_chklst__safety_package has: doc_concept__safety_management_process, doc_getstrt__safety_management_process needs input: wp__module_safety_plan, wp__platform_safety_plan, wp__module_safety_package, wp__platform_safety_package outputs: wp__fdr_reports responsible: rl__external_auditor approved by: rl__safety_manager
The external auditor is responsible to perform the formal reviews on safety plan, safety package and safety analysis. The Safety Manager shall support the external auditor during the reviews. The Project Manager and and the Safety Manager shall approve the formal reviews. Therefore a checklists exist to guide the creator of the relevant safety documents.
wf__p_formal_rv		Workflow

Create/Maintain Safety Manual		status: valid
contains: gd_guidl__saf_man, gd_temp__safety_manual has: doc_concept__safety_management_process, doc_getstrt__safety_management_process needs input: wp__requirements_feat_aou, wp__requirements_feat, wp__feature_arch, wp__feature_fmea, wp__feature_dfa, wp__requirements_comp_aou, wp__requirements_comp, wp__component_arch, wp__sw_component_fmea, wp__sw_component_dfa outputs: wp__platform_safety_manual, wp__module_safety_manual responsible: rl__safety_engineer approved by: rl__safety_manager satisfied by: gd_req__safety_doc_status, gd_req__safety_wp_status
The Safety Engineer collects the necessary input for the safety manuals on platform and module level and documents it. The safety manager makes sure all items are in valid state for a release of the safety manual. Also for the safety manual a template exists as a guidance.
wf__cr_mt_safety_manual		Workflow

Monitor/Verify Safety		status: valid
contains: gd_guidl__saf_plan_definitions has: doc_concept__safety_management_process, doc_getstrt__safety_management_process needs input: wp__module_safety_plan, wp__platform_safety_plan, wp__module_safety_package, wp__platform_safety_package, wp__audit_report, wp__fdr_reports outputs: wp__issue_track_system, wp__module_sw_release_note, wp__platform_sw_release_note responsible: rl__safety_manager approved by: rl__project_lead
The Safety Manager is responsible for the monitoring of the safety activities against the safety plan. The Safety Manager is responsible to verify, that the preconditions for the release, which are part of the release notes, are fulfilled. The Safety Manager is responsible to verify the correctness, completeness and consistency of the release notes.
wf__mr_vy_safety		Workflow

Impact Analysis of Change Request		status: valid
contains: gd_temp__change_component_request, gd_temp__change_decision_record, gd_temp__change_impact_analysis has: doc_concept__safety_management_process needs input: wp__platform_mgmt, wp__issue_track_system, wp__sw_component_class, wp__tailoring outputs: wp__issue_track_system responsible: rl__safety_manager approved by: rl__project_lead
In accordance with ISO 26262-2:2018 section 5.2.2.3 d/e (Impact Analysis), the project implements a dedicated workflow for analyzing change requests. The Safety Manager is responsible for ensuring that each change request is analyzed for its impact on safety, as required by ISO 26262-2:2018. Impact analysis is performed at the element level (e.g., module or component) rather than the item (system) level, reflecting the modular architecture of the platform. This tailoring is documented in the safety plan and justified by the project structure and scope. The analysis includes: - Reviewing the change request and its context - Assessing the impact on affected elements, safety requirements, and work products - Documenting the rationale for decisions regarding acceptance, implementation, or rejection of the change The outcome is a change impact analysis report and a documented decision, which are reviewed and approved as part of the Safety Management process.
wf__impact_analysis_change_request		Workflow