Home Learning Paths ECU Lab Assessments Interview Preparation Arena Pricing Log In Sign Up

FMEA at the Architecture Level

Architecture FMEA vs Component FMEA

Architecture-level FMEA (sometimes called System FMEA or DFMEA for hardware) analyses the failure modes of architectural elements -- ECUs, buses, interfaces, power domains -- and their effects at the vehicle level. It is distinct from component-level FMEA (which analyses individual circuit components) and software FMEA.

Key outputs for the architecture:

  • Identification of single-point failures (one element failure causes system hazard): must be ASIL-D or eliminated
  • Identification of latent failures (silent failure that accumulates until second failure causes hazard): requires diagnostic coverage
  • Validation that safety measures (redundancy, monitoring, E2E) actually cover the failure modes identified

Architecture FMEA Table

Pythonarch_fmea.py
"""Architecture-level FMEA for zone vehicle EEA."""
from dataclasses import dataclass
from typing import List

@dataclass
class FMEAEntry:
    fmea_id:         str
    element:         str   # which architecture element
    failure_mode:    str   # how it can fail
    local_effect:    str   # effect on this element
    system_effect:   str   # effect at vehicle level
    severity:        int   # S1-S3
    occurrence:      int   # O1-O10
    detection:       int   # D1-D10 (1=easily detected)
    safety_measure:  str   # what prevents/mitigates
    status:          str   # open/closed/accepted

    def rpn(self) -> int:
        return self.severity * self.occurrence * self.detection

ARCH_FMEA: List[FMEAEntry] = [
    FMEAEntry(
        fmea_id="FMEA-001",
        element="Chassis CAN bus",
        failure_mode="Bus-off: permanent CAN bus error",
        local_effect="All CAN nodes on chassis bus lose communication",
        system_effect="ABS/EPS lose wheel speed signals; degraded braking/steering",
        severity=3, occurrence=3, detection=2,  # RPN=18
        safety_measure="Bus-off recovery; wheel speed backup via wheel pulse counter",
        status="closed"
    ),
    FMEAEntry(
        fmea_id="FMEA-002",
        element="Zone ECU Front-L power supply",
        failure_mode="12V supply undervoltage (< 9V)",
        local_effect="Zone ECU Front-L resets",
        system_effect="Window, door, mirror controls lost; left front camera lost",
        severity=1, occurrence=4, detection=1,  # RPN=4
        safety_measure="Power supervisor IC; UDS DTC logged; driver warning",
        status="closed"
    ),
]

high_rpn = [f for f in ARCH_FMEA if f.rpn() > 100]
print(f"High RPN items (>100): {len(high_rpn)}")
for f in sorted(ARCH_FMEA, key=lambda x: -x.rpn()):
    print(f"  [{f.fmea_id}] RPN={f.rpn()} | {f.element}: {f.failure_mode[:40]}")

Summary

Architecture-level FMEA is the analysis that validates architecture decisions rather than just documenting them. If the FMEA reveals that a single ECU failure causes an ASIL-D hazard (single-point failure), the architecture must be changed to add redundancy or decomposition -- the FMEA finding is a design requirement, not just a risk to be accepted. The RPN (Risk Priority Number) is a prioritisation tool, not an acceptance criterion: an RPN of 1000 in automotive can still be acceptable if the severity is S1 (minor injury), while an RPN of 10 with S3 (fatal) is not acceptable. The severity dimension overrides RPN for architecture decisions.

🔬 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

  1. 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'.
  2. 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.
  3. 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.
  4. 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.

← PreviousSecurity Zones and Trust BoundariesNext →Hands-On: Safety Architecture Design