Standards Interrelationship Map - Standards & Compliance

IEC 61508 as Root Standard

IEC 61508 Domain Adaptations

  IEC 61508 (1998/2010) — Generic E/E/PE Functional Safety
  SIL 1 → SIL 4 (Safety Integrity Levels)
  ├── ISO 26262 (2011/2018)      Automotive road vehicles    ASIL A→D
  ├── ISO 25119               Agricultural machinery       AgPL a→e
  ├── IEC 62061               Industrial machinery safety  SIL 1→3
  ├── EN 50128 / EN 50129     Railway systems              SIL 0→4
  └── ISO 13849               Machinery safety (control)   PL a→e

  Key concepts inherited from IEC 61508 by all domain adaptations:
  • Safety Integrity Level concept (SIL / ASIL / PL / AgPL)
  • Systematic capability / hardware failure probability
  • V-cycle development lifecycle
  • Functional safety assessment by independent party
  • Safety Case and safety argument

ISO 26262 ↔ ISO/SAE 21434 Intersection

Conflict Type	Example	Resolution Approach
Security adds latency → safety deadline miss	AES-128 encryption on CAN PDU adds 50 µs → misses 500 µs ASIL C deadline	Profile-based encryption; hardware crypto offload; waiver in safety case
Safety mechanism weakens security	Unauthenticated watchdog reset exposes ECU to forced-reset attack	Document in joint TARA+HARA; add reset authentication or rate-limiting
Secure boot delays safety startup	Hash verification adds 150 ms → airbag ECU violates < 100 ms startup spec	Deferred attestation: safety-first boot, runtime security check after init
Key update disrupts availability	PKI certificate rotation takes ECU offline 30 s → ASIL B function unavailable	Stage key rotation during non-safety-critical operating modes

💡 ISO/SAE 21434 Annex H — Safety-Security Interaction

ISO/SAE 21434 Annex H (informative) provides specific guidance for identifying and resolving conflicts between safety and security requirements. The recommended approach is a joint workshop where the functional safety team brings the HARA and the cybersecurity team brings the TARA, and both teams review overlapping threat/hazard scenarios together. The output is a co-engineering record that documents each conflict, the chosen resolution, and the residual risk accepted by both teams.

AUTOSAR ↔ ISO 26262 Relationship

AUTOSAR Module	ISO 26262 Relevance	Required Integrator Action
E2E Library	Provides end-to-end protection for safety-critical PDUs; qualifiable for ASIL D	Configure E2E profile (P01/P04/P07) per signal ASIL; verify counter window
WdgM (Watchdog Manager)	Supervises software execution; detects stuck tasks; triggers safe state	Map all ASIL-relevant SW runnables to WdgM supervision entities
DEM (Diagnostic Event Manager)	Stores and reports safety-relevant faults; supports ASIL B monitoring	Assign safety-relevant DEM events to correct FDC and severity
MCAL (Micro Ctrl Abstraction)	Hardware drivers; ASIL-rated for supported MCUs (Infineon AURIX, NXP MPC57xx)	Verify MCAL version's safety manual; implement Assumed Safety Measures (ASMs)
FiM (Function Inhibition Manager)	Inhibits safety-relevant functions when monitored faults active	Configure FiM permission IDs per ASIL function vs. DEM event map

IATF 16949 ↔ ASPICE Relationship

Framework	Scope	Gate Requirement	Assessment Body
IATF 16949	Quality Management System (QMS) — processes, procedures, customer satisfaction	Certification before production start; annual surveillance audit	IATF-accredited certification body (TÜV, Bureau Veritas, SGS)
ASPICE	Software engineering process capability — requirements, design, test, CM	Supplier qualification assessment (typically Level 2 minimum)	VDA QMC-qualified ASPICE assessor
Relationship	IATF 16949 Section 8.3.4 requires software development capability assessed per ASPICE	IATF certification implicitly requires ASPICE compliance for automotive software	Both required simultaneously for safety software suppliers

Summary

The automotive standards ecosystem forms a hierarchy rooted in IEC 61508, with domain-specific adaptations (ISO 26262), complementary cybersecurity (ISO/SAE 21434), process capability (ASPICE), and quality management (IATF 16949) layers. Understanding the intersections — particularly the safety/security conflict resolution requirement and the AUTOSAR ASM obligations — prevents costly rework when conflicts are discovered late in the V-cycle.

🔬 Deep Dive — Core Concepts Expanded

This section builds on the foundational concepts covered above with additional technical depth, edge cases, and configuration nuances that separate competent engineers from experts. When working on production ECU projects, the details covered here are the ones most commonly responsible for integration delays and late-phase defects.

Key principles to reinforce:

Configuration over coding: In AUTOSAR and automotive middleware environments, correctness is largely determined by ARXML configuration, not application code. A correctly implemented algorithm can produce wrong results due to a single misconfigured parameter.
Traceability as a first-class concern: Every configuration decision should be traceable to a requirement, safety goal, or architecture decision. Undocumented configuration choices are a common source of regression defects when ECUs are updated.
Cross-module dependencies: In tightly integrated automotive software stacks, changing one module's configuration often requires corresponding updates in dependent modules. Always perform a dependency impact analysis before submitting configuration changes.

🏭 How This Topic Appears in Production Projects

Project integration phase: The concepts covered in this lesson are most commonly encountered during ECU integration testing — when multiple software components from different teams are combined for the first time. Issues that were invisible in unit tests frequently surface at this stage.
Supplier/OEM interface: This is a topic that frequently appears in technical discussions between Tier-1 ECU suppliers and OEM system integrators. Engineers who can speak fluently about these details earn credibility and are often brought into critical design review meetings.
Automotive tool ecosystem: Vector CANoe/CANalyzer, dSPACE tools, and ETAS INCA are the standard tools used to validate and measure the correct behaviour of the systems described in this lesson. Familiarity with these tools alongside the conceptual knowledge dramatically accelerates debugging in real projects.

⚠️ Common Mistakes and How to Avoid Them

Assuming default configuration is correct: Automotive software tools ship with default configurations that are designed to compile and link, not to meet project-specific requirements. Every configuration parameter needs to be consciously set. 'It compiled' is not the same as 'it is correctly configured'.
Skipping documentation of configuration rationale: In a 3-year ECU project with team turnover, undocumented configuration choices become tribal knowledge that disappears when engineers leave. Document why a parameter is set to a specific value, not just what it is set to.
Testing only the happy path: Automotive ECUs must behave correctly under fault conditions, voltage variations, and communication errors. Always test the error handling paths as rigorously as the nominal operation. Many production escapes originate in untested error branches.
Version mismatches between teams: In a multi-team project, the BSW team, SWC team, and system integration team may use different versions of the same ARXML file. Version management of all ARXML files in a shared repository is mandatory, not optional.

📊 Industry Note

Engineers who master both the theoretical concepts and the practical toolchain skills covered in this course are among the most sought-after professionals in the automotive software industry. The combination of AUTOSAR standards knowledge, safety engineering understanding, and hands-on configuration experience commands premium salaries at OEMs and Tier-1 suppliers globally.