2-5 Overall Safety Management

From OpenMBD
Revision as of 08:05, 2 October 2017 by Roel (talk | contribs)
Jump to: navigation, search


Back to Home

AllLogos.png

Introduction Being ISO26262 compliant is not compulsory whatsoever. The main goal however is to provide a solid ground which can be used to provide proof that a reasonable amount of effort has been put into creating a functionally safe product. The safety activities should be managed to ensure the correctness and completeness of the safety case and to provide overview which is useful while implementing ISO26262 into the development process.

It is assumed that it is not possible for the average SME's to acquire 100% ISO26262 compliance within a reasonable amount of time as this requires too much money, time and effort. Nevertheless the processes described in ISO26262 do add value because they can significantly reduce the amount of design errors and create awareness of the risks and hazards introduced by the item and it's design. This information is crucial in creating a functionally safe product. For this reason it is advised to look at the implementation of ISO26262 as an ongoing process, rather than a step. Part 2 of ISO26262, Safety Management, is a critical part in the success factor of the introduction of ISO26262 in your company.



Requirements to the Overall Safety Management:

  • Safety Culture (Link to indicators)
  • Competence Management
  • Quality Management (according to preferably the ISO/TS 16949, or ISO9001)
  • Project independent tailoring of the safety lifecycle
  • Functional Safety as a company objective
  • Company-specific policies and processes
  • Resource management
  • Continuous Improvement Process
  • Escalation process for FS
  • Authority of safety managers, responsible parties


Work products are:

  • Organization-specific rules and processes for functional safety, resulting from ISO26262-2 Chapter 5.4.3 and 5.4.5
  • Evidence of competence, resulting from ISO26262-2 Chapter 6.4.3.4
  • Evidence of quality management, resulting from ISO26262-2 Chapter 5.4.4


Next Chapter (2-5)