| Fault Class | Definition | Contribution to | Example |
|---|---|---|---|
| Single-point fault (SPF) | Element fault with no redundancy; directly causes safety violation | SPFM (numerator and denominator) | Torque sensor total failure with no second channel |
| Residual fault (MPF-R) | Fault that safety mechanism fails to detect (the 1-DC portion) | SPFM (numerator as residual) | 1% of torque sensor faults not caught by range check |
| Latent fault (MPF-L) | Fault in redundant channel; not immediately detectable; hazardous only with second fault | LFM (numerator and denominator) | Dead secondary sensor channel not detected by periodic test |
| Safe fault | Fault that does not contribute to safety violation | Not counted in SPFM/LFM | Sensor failure causing EPS to turn off (safe state) |
| No effect fault | Fault with no safety-relevant effect | Not counted | Internal diagnostic LED failure |
Fault Classification for Metrics
FIT Rate Data Sources
| Source | Database | Data Type | Typical Use |
|---|---|---|---|
| IEC TR 62380 | IEC standard | Generic component FIT rates | First-pass estimates; widely accepted |
| MIL-HDBK-217F | US military handbook | Component FIT rates (temperature-derated) | Historical; less used in automotive now |
| SN 29500 | Siemens standard | Component FIT rates | Common in European automotive suppliers |
| Manufacturer FMEDA | Component supplier | Device-specific FIT + failure mode distribution | Best accuracy; required for ASIL-D component claims |
| Field data | Own field return analysis | Actual in-service failure rate | Strongest evidence; available after production |
Step-by-Step SPFM Calculation
Pythonspfm_worksheet.py
#!/usr/bin/env python3
# SPFM/LFM calculation worksheet (ISO 26262 Part 5 Annex C)
# Hardware element data: (name, FIT_total, failure_mode_distribution, DC, fault_class)
# fault_class: 'SPF', 'MPF_R' (residual), 'MPF_L' (latent), 'SF' (safe), 'NE' (no effect)
hw_elements = [
# Torque sensor (ASIL-D; dual-channel)
{"name": "Torque Ch-A stuck-at", "FIT": 25, "class": "SPF", "DC": 0.97},
{"name": "Torque Ch-A drift", "FIT": 15, "class": "MPF_R", "DC": 0.90},
{"name": "Torque Ch-B stuck-at", "FIT": 25, "class": "MPF_L", "DC": 0.95},
{"name": "Torque Ch-B drift", "FIT": 15, "class": "MPF_L", "DC": 0.80},
{"name": "Torque sensor power", "FIT": 20, "class": "SPF", "DC": 0.97},
{"name": "ADC Ch-A conversion", "FIT": 10, "class": "SPF", "DC": 0.95},
{"name": "ADC Ch-B conversion", "FIT": 10, "class": "MPF_L", "DC": 0.90},
{"name": "MCU lockstep CPU", "FIT": 15, "class": "SPF", "DC": 0.99},
{"name": "MCU flash ECC-SEC", "FIT": 5, "class": "SF", "DC": 1.00},
{"name": "MCU flash ECC-DED", "FIT": 2, "class": "SPF", "DC": 1.00},
{"name": "CAN transceiver", "FIT": 8, "class": "SPF", "DC": 0.90},
{"name": "Supply voltage monitor", "FIT": 30, "class": "SPF", "DC": 0.97},
{"name": "Window watchdog circuit", "FIT": 12, "class": "MPF_L", "DC": 0.70},
]
spf_total = spf_covered = 0
mpf_r_total = mpf_r_covered = 0
mpf_l_total = mpf_l_covered = 0
for e in hw_elements:
covered = e["FIT"] * e["DC"]
residual = e["FIT"] - covered
if e["class"] == "SPF":
spf_total += e["FIT"]; spf_covered += covered
elif e["class"] == "MPF_R":
mpf_r_total += e["FIT"]; mpf_r_covered += covered
elif e["class"] == "MPF_L":
mpf_l_total += e["FIT"]; mpf_l_covered += covered
print(f" {e['name']:35s} {e['FIT']:4.0f} FIT DC={e['DC']*100:4.1f}% "
f"residual={residual:.2f} FIT [{e['class']}]")
spf_denominator = spf_total + mpf_r_total
spf_residual = (spf_total - spf_covered) + (mpf_r_total - mpf_r_covered)
SPFM = 1 - spf_residual / spf_denominator if spf_denominator else 1
mpf_l_residual = mpf_l_total - mpf_l_covered
LFM = 1 - mpf_l_residual / mpf_l_total if mpf_l_total else 1
PMHF_FIT = spf_residual + mpf_l_residual # simplified
print(f"\n{'='*60}")
print(f"SPFM = {SPFM*100:.1f}% target ASIL-D: ≥ 99.0% {'✓ PASS' if SPFM >= 0.99 else '✗ FAIL'}")
print(f"LFM = {LFM*100:.1f}% target ASIL-D: ≥ 90.0% {'✓ PASS' if LFM >= 0.90 else '✗ FAIL'}")
print(f"PMHF = {PMHF_FIT:.2f} FIT target ASIL-D: < 10 FIT {'✓ PASS' if PMHF_FIT < 10 else '✗ FAIL'}")Summary
The SPFM/LFM calculation is the quantitative evidence that hardware architecture meets ISO 26262 targets. The most common reason for failing SPFM: insufficient DC for single-point faults in critical sensor paths. The fix: either increase DC (better diagnostics) or introduce redundancy (converting SPF to MPF). The most common reason for failing LFM: insufficient periodic testing of latent faults in safety mechanisms (watchdogs, monitors). A watchdog circuit with no periodic self-test has its failure contributing 100% to the latent fault pool. Structuring the FIT data correctly (SPF vs MPF-R vs MPF-L vs safe fault) is critical — miscategorising a safe fault as an SPF inflates the residual SPF rate and fails SPFM unnecessarily.
🔬 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.