Instiq
Chapter 6 · IoT, functional safety & low power·v1.0.0·Updated 7/10/2026·~17 min

What's changed: Initial version

6.3Functional safety and reliability

Key points

Covers IEC61508, the general functional-safety standard for electrical/electronic/programmable-electronic systems, and its automotive counterpart ISO26262, the safety levels SIL and ASIL they define, FMEA/FTA for systematically identifying failure effects, fail-safe (defaulting to a safe state on failure) versus fail-soft (degrading gracefully while continuing to operate), redundancy and majority voting to cover single failures, and PID control for tracking a target value.

In embedded systems where a failure can directly lead to loss of life or a serious accident—medical devices, automobiles, industrial control—it is essential not only to "build it so it does not break" but to design in, from the outset, functional safety: specifying how the system should behave safely when it does fail. A systems architect must be able to judge the safety level (SIL/ASIL) appropriate to the target system's hazard, and choose a fail behavior and redundancy configuration to match.

6.3.1Functional safety standards and SIL/ASIL

  • IEC61508 is the general functional-safety standard for electrical/electronic/programmable-electronic (E/E/PE) systems. It is a parent standard applied across industrial equipment in general, from which sector-specific standards for rail, process industries, automotive, and others are derived. ISO26262 is a functional-safety standard for the automotive sector, derived from IEC61508, applied to in-vehicle electronic control systems such as brakes and steering.
  • SIL (Safety Integrity Level) is the safety level defined by IEC61508, with four grades, SIL1 through SIL4 (higher numbers demand greater safety). ASIL (Automotive Safety Integrity Level) is the automotive safety level defined by ISO26262, with four grades, ASIL A through D (D being the strictest), plus QM (Quality Management), which indicates no safety requirement applies. The higher the hazard of a function (e.g., brake control), the higher the SIL/ASIL required, and the more rigorous the required hardware/software verification becomes.

Continue reading — free sign-up

You're reading the free preview. Sign up free to read this section in full, plus every chapter (including 4+) and all questions.