ISO 26262 Functional Safety
FuSi (Functional Safety/Funktionale Sicherheit) is a cross-functional guideline covering all products in the vehicle. The safety goals are oriented according to the vehicle functionalities and are based on the Hazard Analysis and Risk Assessment (HARA).
According to the different subsystems in the vehicle, the overall ASIL-Level is to be defined, and the FuSi concept is to be designed and implemented.
The FuSi Development Phases occur in parallel with the system and software development, thus overlapping with the same milestones on QM deliverables. Nonetheless, this scope presents its own goals and work products as defined by the ISO26262 and documented in the DIA (Development Interface Agreement).
L4B´s Expertise
As part of our services, we support our customers with requirements analysis and definition of the FuSi concept and goals. L4B may also focus on creating the FuSi Concept according to the OEM and Tier1’s previously defined requirements and goals.
If requested by the customer, the company also may represent and take full responsibility for the FuSi certification process, making sure that the applicable systems and vehicle products are fully compliant with the ISO26262 regulation.
Our main goal is to assist our customers and ensure that the achieved functionalities are not harmful to the vehicle’s passengers and drivers.
In general, the safety development plan is divided into two parts:
- Concept phase (with the assessment)
- Development phase (with the assessment)
As the responsible Tier1, we ensure that the Concept Phase is addressed on the system level, where all domains (SW – HW – MEC) are evaluated. The finalization of the Concept Phase is a prerequisite for the beginning of the Development Phase.
The amount of work products based on the ASIL criteria related to the Concept Phase and Development Phase are enumerated in the ISO 26262 and high-lightened in the DIA documentation.
Development Phase
Following the safety guidelines from ISO 26262-part 6, we adopt various best-fit approaches for the OEM’s project requirements. These can be easily referenced according to the stages in the Development Phase’s V-Model.
In the Software Safety Requirements Specification, L4B-Automotive’s Requirements Experts ensure that the specification is fully compliant with the safety process. Additionally, our experts ensure that those are followed throughout the development lifecycle System and Software Design, Guidelines for Implementation and Design.
L4B is able to deploy a variety of verification methodologies. The verification team has input into the project scope and requirements, such as code-walkthroughs, inspections, formal verification, and Static Code Analysis.
Safety qualified testers undertake the requirements-based testing. This may be performed in multiple ways, which includes Error-guessing, Interface test-cases, fault injection tests, resource usage tests – thus ensuring the necessary structural and functional coverage.
Safety in the automotive industry represents the lifeguard that makes sure all systems work together in the vehicle to keep driver and passengers safe, under certain and common damage circumstances (e.g., impact at 50Km/h).
This approach ensures that all relevant risks are mapped, assessed, and mitigated during the vehicle product development. Therefore, any issues can be directly corrected, thus reducing costs and delays throughout the product development lifecycle.