Module 3 Coaching. VESP will use ISO26262 V-model to tailor the client's coaching and certification process based on ISO2626 consulting and coaching model.
Coaching and certification process
The following figure shows the overall architecture of the ISO 26262 standard. The ISO 26262 standard is based on the V-model and serves as a reference process model for different stages of product development.
According to the ISO26262 certification standard, VESP Technology will provide tailor-made guidance to the client for the overall certification process. A total of eight steps will lead the customer to step by step towards the ISO2626 functional safety standard.
Vehicle electrical safety management and life cycle processes
Vehicle electrical safety development management and life cycle process description
Safety item definition
Define item characteristics, intended functions and their interactions, operating modes, vehicle status… and so on.
Hazard analysis and risk assessment
Identification and classification of hazardous event scenarios and risk assessments, and the appropriate ASIL level and safety goals.
Functional safety concept development
System safety concepts are designed to achieve safety goal, such as diagnostics or redundant measures implementation to avoid or migrate the hazardous conditions to a safe state.
Technical safety concepts and system design
Develop the technical concepts in order to deploy the technical safe concepts and system architecture as the basis for further software and hardware development, including implementing safety requirements accordingly.
Qualitative safety analysis
Apply the deductive and inductive safety analysis processes to verify that the design can meet system or hardware safety goal, including FMEA, FTA, safety mechanisms, DFA and so on.
Quantitative safety analysis
Calculate the hardware architecture metrics (SPFM / LFM) and safety violation due to random hardware failure evaluation (PMHF / EEC), and verify the failure rate and diagnostic coverage fault injection to achieve the safety goal
Quantitative verification and certification
Review, analyze, and test to confirm that all safety requirements have been properly implemented in the developing system or software/hardware and that all assumptions of use (SEooC) made in the safety concepts are valid.
Safety case collation
The functional safety architecture with consistent, complete, and persuasive arguments are evaluated through functional safety assessments to prove that a system or software/hardware meets all of its safety goals and appropriate regulations.