Compliance Planning & Tailoring - Standards & Compliance

Compliance Scoping: Which Standards Apply?

Pythoncompliance_scope_selector.py

#!/usr/bin/env python3
# Compliance scope selector: determine applicable standards per component

def determine_compliance_scope(component: dict) -> list:
    scope = []

    # IATF 16949: always required for automotive parts
    scope.append({"standard": "IATF 16949", "reason": "All automotive ECU suppliers"})

    # ISO 26262: required if any ASIL assignment
    if component.get("max_asil") and component["max_asil"] != "QM":
        scope.append({
            "standard": f"ISO 26262 Part 6 ({component['max_asil']})",
            "reason": f"ASIL {component['max_asil']} function: {component.get('asil_function', 'unspecified')}"
        })

    # ISO/SAE 21434: required if cybersecurity-relevant
    if component.get("has_external_interface") or component.get("stores_sensitive_data"):
        scope.append({"standard": "ISO/SAE 21434", "reason": "Cybersecurity-relevant interface or data"})

    # UNECE R155: required if OEM sells in EU and component is in CSMS scope
    if component.get("vehicle_market_eu") and component.get("in_csms_scope"):
        scope.append({"standard": "UNECE R155 (via OEM CSMS)", "reason": "EU market + cybersecurity scope"})

    # ISO 21448: required if ADAS/automated driving
    if component.get("is_adas"):
        scope.append({"standard": "ISO 21448 (SOTIF)", "reason": "ADAS function with ODD definition required"})

    # ASPICE: OEM-specified minimum level
    scope.append({
        "standard": f"ASPICE Level {component.get('aspice_min', 2)}",
        "reason": "OEM supplier qualification requirement"
    })

    return scope

# Example: ADAS Gateway ECU
component = {
    "name": "ADAS Gateway ECU",
    "max_asil": "C",
    "asil_function": "Brake-by-wire arbitration",
    "has_external_interface": True,
    "stores_sensitive_data": False,
    "vehicle_market_eu": True,
    "in_csms_scope": True,
    "is_adas": True,
    "aspice_min": 3,
}

print(f"Compliance scope for: {component['name']}")
for item in determine_compliance_scope(component):
    print(f"  • {item['standard']}: {item['reason']}")

ISO 26262 Tailoring Process

Tailoring Example	Clause	ASIL	Justification Required?
Omit MC/DC coverage	Part 6 Table 10	ASIL B	Yes — MC/DC required for C/D; optional for B with justification
Use ASIL B coding guidelines for ASIL A code	Part 6 Table 1	ASIL A	Yes — using stricter requirement; document as conservative tailoring
Skip FTA for ASIL B SW	Part 6 Table 9	ASIL B	Yes — FTA recommended not required for B; but recommended means assessor will ask why not done
Use operational experience instead of qualification for TCL2 tool	Part 8.11	All	Yes — operational experience must be documented with success metrics

⚠️ Tailoring Must Be Pre-Agreed with Safety Manager

Tailoring a requirement out of scope is a Major FSA finding if it was done unilaterally without Safety Manager approval and documentation in the Safety Plan. The ISO 26262 tailoring process requires: (1) identify the requirement to be tailored; (2) document the justification; (3) Safety Manager approves and documents in Safety Plan; (4) FSA assessor reviews during assessment. Missing any step makes the tailoring invalid.

SEooC: Safety Element out of Context

SEooC Development and Integration Flow

  Tier 2 Supplier (SEooC Developer)
  ├── Cannot access vehicle-level HARA (OEM confidential)
  ├── Defines Assumed Safety Goals (ASGs) based on typical use case
  │   e.g., "Assumed: torque signal is ASIL B"
  ├── Derives Safety Requirements from ASGs
  ├── Develops component to those requirements
  ├── Creates SEooC Safety Case with explicit assumption list
  └── Delivers component + SEooC Safety Case + Assumed Safety Goals

  Tier 1 / OEM Integrator
  ├── Receives SEooC Safety Case from Tier 2
  ├── Compares ASGs against actual vehicle HARA Safety Goals
  ├── Integration check: do actual Safety Goals cover all ASGs?
  │   YES → integration complete; reference SEooC Safety Case in system Safety Case
  │   NO  → assumption gap! → must resolve before using component in ASIL context
  └── Documents integration evidence in system-level Safety Case

Risk-Based Resource Allocation

ASIL Level	Safety Activity Effort	Key Evidence	Typical Review Depth
ASIL D	Maximum — all evidence required; independent assessor mandatory	Full MC/DC, FMEA, FTA, FSA at I3 independence	100% code review; formal inspections
ASIL C	High — most evidence required; MC/DC and FTA required	MC/DC coverage, FMEA, partial FTA	100% code review; structured walkthrough
ASIL B	Moderate — branch coverage; FMEA required	Branch coverage, DFMEA	Structured walkthrough; peer review
ASIL A	Base — statement coverage; FMEA recommended	Statement coverage, recommended FMEA	Peer review; checklist-based
QM	Quality Management only — ISO 26262 does not apply	IATF 16949 + DFMEA	Standard code review per quality process

Summary

Compliance scoping is the first compliance activity on any project — getting it wrong either wastes resources on unnecessary compliance work or creates a gap that blocks SOP. The SEooC pattern is critical for Tier 2 suppliers who develop components without access to the OEM HARA: explicit assumption documentation and a formal integration check at Tier 1 prevents the most common integration-phase compliance failure. Tailoring must always be pre-agreed and documented — an undocumented tailoring discovered during FSA is automatically a Major finding.

🔬 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.