| Aspect | FTA | FMEA |
|---|---|---|
| Direction | Top-down: start with top-level failure event | Bottom-up: start with component failure modes |
| Purpose | Identify all combinations of events that cause safety violation | Identify effects of each component failure |
| Outputs | Minimal cut sets; quantitative failure probability | RPN; diagnostic coverage; FMEA worksheet |
| Best for | Understanding failure combinations; verifying hardware metrics | Comprehensive failure mode enumeration; DC assessment |
| ISO 26262 ref | Part 9 Clause 8 | Part 9 Clause 5 |
Fault Tree Analysis: Top-Down Safety Analysis
FTA Logic Gates
FTA Gate Symbols and Semantics
AND gate: all input events must occur simultaneously for output to occur ├── Symbol: flat-bottomed gate ├── Probability: P(output) = P(A) × P(B) (if independent) └── Example: sensor failure AND diagnostic failure → undetected fault OR gate: any single input event causes output to occur ├── Symbol: curved-bottomed gate ├── Probability: P(output) ≈ P(A) + P(B) (if P << 1) └── Example: power failure OR communication failure → sensor unavailable Inhibit gate: output occurs only when input AND condition both true ├── Symbol: AND gate with condition input └── Example: random fault AND diagnostic inactive period → undetected Basic event (leaf): independent failure at component level ├── Symbol: circle └── Has a quantitative failure rate (FIT value) Undeveloped event: not further analysed (bounded assumption) ├── Symbol: diamond └── Used when event is bounded by assumption (e.g., external EMC event) Transfer gate: references to sub-tree defined elsewhere ├── Symbol: triangle └── Used for large trees to manage complexity
Fault Tree: AEB Unintended Activation
Textfta_aeb.txt
Top Event: Unintended AEB activation (HE-01)
[OR gate]
├── Channel A failure AND Monitor failure [AND gate]
│ ├── Channel A: Sensor fusion error (radar + camera both wrong same direction)
│ │ [OR gate]
│ │ ├── Radar object false positive [Basic: 1e-7 /h]
│ │ └── Camera object false positive [Basic: 2e-7 /h]
│ └── Safety Monitor fails to detect Channel A error [AND gate]
│ ├── Monitor software fault [Basic: 5e-8 /h]
│ └── Monitor hardware fault (MCU failure) [Basic: 1e-8 /h]
│
├── Spurious brake actuator command (from brake ECU side) [Basic: 1e-9 /h]
│
└── Software fault in AEB decision logic [Basic: (systematic; must be addressed by process)]
Minimal Cut Sets (MCS):
MCS-1: {Radar false positive, Camera false positive} — both sensors wrong simultaneously
MCS-2: {Channel A error, Monitor software fault, Monitor HW fault}
MCS-3: {Spurious brake actuator command}
Quantification of MCS-2:
P(Channel A error) = 1e-7 + 2e-7 = 3e-7/h
P(Monitor SW fault) = 5e-8/h
P(Monitor HW fault) = 1e-8/h
P(MCS-2) = 3e-7 × 5e-8 × 1e-8 = 1.5e-22/h
→ Negligible (well below ASIL-D target < 1e-8/h for single fault)Quantitative FTA: PMHF Contribution
| MCS | Events | Rate (FIT) | Contribution to PMHF | ASIL-D Limit |
|---|---|---|---|---|
| MCS-1 | Radar + Camera simultaneous false positive | 3e-7/h × 2e-7/h = 6e-14/h (AND gate) | < 1e-14 per hour | 1e-8/h |
| MCS-2 | Channel A + Monitor SW + Monitor HW | 1.5e-22/h | Negligible | 1e-8/h |
| MCS-3 | Brake actuator spurious command | 1e-9/h | Significant — needs mitigation | 1e-8/h |
Summary
FTA and FMEA are complementary: FTA identifies the dangerous combinations (minimal cut sets) that can cause the top-level failure event, while FMEA identifies every way individual components can fail and their effects. For ASIL-D systems, both must be performed. The minimal cut sets drive the design of safety mechanisms: MCS-3 (spurious brake actuator command) has a 1e-9/h rate that directly contributes to the PMHF target — it must either be mitigated by a safety mechanism (reducing its effective contribution) or shown to be acceptable by argument. Quantitative FTA gives the probability of the top event, which feeds directly into the PMHF calculation required by ISO 26262 Part 5.
🔬 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.