SEooC ISO 26262 | What is Safety Element Out of Context in Automotive Functional Safety?

SEooC ISO 26262 | What is Safety Element Out of Context in Automotive Functional Safety?

• 1.
  Embitel Technologies Internationalpresence: Safety Element Out of Context: SEooC in Automotive Functional Safety
• 2.
  Embitel Technologies Internationalpresence: What if this infotainment system is ASIL C compliant? The camera will now also come under the purview of ISO 26262 standard. However, not as a regular E/E item, but as a safety element out of context (SEooC). Did we get you puzzled? Let’s bring in some clarity! The software or hardware components that are developed without considering the context of their application in a particular vehicle; meaning components that are developed without any idea of where they will be fitted, fall under the purview of SEooC. Another way to define SEooC is, “E/E systems that are not developed based on the specific requirements provided by the OEM, suppliers or technology vendors, but are developed rather on assumptions”.
• 3.
  Embitel Technologies Internationalpresence:
• 4.
  Embitel Technologies Internationalpresence: SEooC in the Context of Automotive Industry In the context of automotive industry, the most common hardware SEooC is the microcontroller. Mostly, microcontroller platform designs provide the building blocks, based on which a specific system (that caters to a particular business use-case) is developed. Hence, these building blocks (microcontroller platform and the various pins/ports) are not developed based on the requirements provided by any stakeholder in the automotive industry. Talking of a software SEooC, the classic example is an RTOS (Real time operating system). An RTOS is equipped with a scheduler, that is designed to meet the real-time requirements of an embedded system
• 5.
  Embitel Technologies Internationalpresence: General Assumptions Made for SEooC Development include: • The area of application and the intended function of the component • An overview of the technical architecture of the system • Functional and Technical Safety Requirement • Automotive Safety and Integrity Level (ASIL) value assigned to the system SEooC Development as per the ISO 26262 Standard
• 6.
  Embitel Technologies Internationalpresence: • Assumptions made by the Developer The system interfaces with other automotive ECUs via CAN BUS, in order to get the required vehicle info It is designed for a front-wheel driven automotive The system activates automatically as well as on driver’s request- Functional requirement The system deactivates if requested by the driver- Functional Requirement • ISO 26262 Related Assumptions about: Item Definition to assume the components which with the system will interact Safety Goals and ASIL Value Functional Safety Requirements (FSR) and Technical Safety Requirement (TSR) • Safety Goals and ASIL Assumption: System does not get activated at high-speed. System does not get deactivated unless the driver requests for it The system will fetch information from external sources about the vehicle speed and the driver’s request (ASIL C or ASIL D) Understanding SEooC With Example
• 7.
  Embitel Technologies Internationalpresence: Contact us today for SEooC! Mail us at [email protected]