The company SaSaTrans GmbH offers various services in the field of Functional Safety Automotive:</p>
ISO26262, Part 2:
Chapter 6:
Creation of the safety plan
Carrying out safety assessments
ISO26262, Part 3:
Chapter 5:
Creating the item definition
Chapter 7:
Managing the Hazard Analysis and Risk Assessment
Chapter 8:
Creating the Functional Safety Concept
Analysis of the functions and representation of the FuSi relevant sub-functions
If possible: Representation of the functions in a reliability block diagram (RBD) for the initial breakdown of the ASIL and the fault tolerance time (FTTI)
Develop the functional safety requirements from the results of the hazard analysis and risk assessment (H&R)
Derive the test requirements for verification and validation
Checking the tests and their results
Contributing the safety aspects to the FMEA team
ISO26262, Part 4:
Chapter 6:
Creating the technical safety requirement specification
Analyzing the system and depicting the paths of action in a reliability block diagram (RBD) to break down the ASIL, the fault tolerance times (FTTI) and the failure rate (PMHF)
Developing the technical safety requirements from the functional concept
Deriving the test requirements for verification
Checking the tests and their results
Creating the safety analysis report
Creating a fault tree analysis (FTA)
Communication with the supplier via:
Request for Quotation (RFQ) and
Development Interface Agreement (DIA) (Interfaces within distributed developments, ISO26262, Part 8, Chapter 5)
Checking the supplied documents (e.g. FMEDA) and clarifying the content
Chapter 10:
Preparation of the Functional Safety Assessment Report
ISO26262, Part 5:
General:
Determine the status of whether:
the team can develop safe hardware according to ISO26262, Part 5
the hardware development process complies with ISO26262, Part 5
Chapter 6:
Creating a Hardware Safety Requirements Specification
Support for the creation of a hardware-software interface specification
Chapter 7:
Creating a Hardware Safety Analysis Report
Chapter 8:
Creating the FMEDA in a team
ISO26262, Part 6:
General:
Determine the status of whether:
the team can develop safe software according to ISO26262, Part 6
the software development process complies with ISO26262, Part 6
Chapter 6:
Creating a Software Safety Requirements Specification
Support in the creation of a hardware-software interface specification
ISO26262, Part 7:
Chapter 5:
Creating the safety-related content for the production plan
Assessment report for the ability to produce a safety product
Chapter 6:
Creating the safety-related content for maintenance
Creating the safety-related content for decommissioning
ISO26262, Part 8:
Part 8 sets requirements for the necessary work techniques. These must be adhered to by the project. Of course, they also apply to the Safety Manager.
ISO26262, Part 9:
Chapter 5: Decomposition
Decomposition enables safe systems to be created at an affordable cost. In order to create an ISO26262-compliant architecture, the rules of Chapter 5 must be observed.
Chapter 6: Criteria for Coexistence of elements
Necessary proof for the interaction of the individual configuration elements.
Chapter 7: Analysis of dependent failures
An architecture with decomposed parts must prove whether a failure could affect the decomposed elements in such a way that this failure also affects the security target. If this is the case, further measures must be initiated.
Chapter 8: Safety Analyses
