Supplier Compliance Management - Standards & Compliance

OEM-Supplier Compliance Model

OEM-Supplier Compliance Flow

  OEM specifies requirements (PPDS/SOR):
  ├── ASIL level per function
  ├── ISO/SAE 21434 security requirements
  ├── ASPICE minimum Level 2 SWE processes
  ├── IATF 16949 certification required
  └── Special requirements: AUTOSAR conformance, SecOC, OTA support

  Supplier responds with Compliance Assessment Report (CAR) before nomination:
  ├── ASPICE self-assessment (Level achieved per SWE process)
  ├── Date of last 3rd-party ASPICE assessment
  ├── ISO 26262 status (Safety Plan in place? FSA experience?)
  ├── ISO/SAE 21434 capability (TARA performed before?)
  ├── Known deviations requiring OEM waiver
  └── Tool qualification status for TCL3 tools

  OEM evaluates CAR → nominates or declines supplier
  Non-negotiable gate: ASPICE < Level 2 SWE.4 = not nominated

Supplier Monitoring During Development

Pythonsupplier_monitoring_dashboard.py

#!/usr/bin/env python3
# OEM supplier monitoring dashboard — track multiple Tier 1 suppliers
from datetime import date

suppliers = [
    {
        "name": "Tier1_Supplier_A",
        "component": "EPS ECU SW",
        "aspice_level": 2,
        "aspice_last_assessed": "2025-09-15",
        "safety_plan_status": "Approved",
        "hara_gate_date": "2025-11-01",
        "hara_gate_status": "Complete",
        "ppap_target": "2026-09-01",
        "open_safety_issues": 3,
        "overdue_crs": 0,
    },
    {
        "name": "Tier1_Supplier_B",
        "component": "ADAS Camera SW",
        "aspice_level": 1,  # BELOW THRESHOLD
        "aspice_last_assessed": "2024-03-10",
        "safety_plan_status": "In Review",
        "hara_gate_date": "2025-10-01",
        "hara_gate_status": "DELAYED",  # RED
        "ppap_target": "2026-09-01",
        "open_safety_issues": 7,  # HIGH
        "overdue_crs": 2,
    },
]

print("Supplier Compliance Dashboard:")
for s in suppliers:
    aspice_ok = s["aspice_level"] >= 2
    issues_ok = s["open_safety_issues"] < 5
    hara_ok = s["hara_gate_status"] not in ["DELAYED", "BLOCKED"]
    overall = "GREEN" if all([aspice_ok, issues_ok, hara_ok]) else "RED"
    print(f"  {s['name']} ({s['component']}): {overall}")
    if not aspice_ok:
        print(f"    RED: ASPICE Level {s['aspice_level']} < 2 — escalation required")
    if not issues_ok:
        print(f"    RED: {s['open_safety_issues']} open safety issues")
    if not hara_ok:
        print(f"    RED: HARA gate {s['hara_gate_status']}")

SOP Gate Compliance Deliverables

Deliverable	Standard	Responsibility	Blocking?
Safety Case + FSA Report	ISO 26262 Part 2	Supplier + Independent Assessor	Yes — SOP hold without signed Safety Case
Cybersecurity Assurance Report	ISO/SAE 21434 Clause 10	Supplier Cybersecurity Team	Yes — R155 requires per-vehicle-model CSMS evidence
PPAP Level 3 Package	IATF 16949	Supplier Quality Team	Yes — OEM quality team approves PPAP before SOP
ASPICE Assessment Report	VDA ASPICE PAM 3.1	3rd-party qualified assessor	Yes — Level 2+ required; Level 1 = SOP hold
Type Approval Documentation Support	UNECE R155/R156	OEM (supplier provides evidence inputs)	Yes — type approval authority approval before SOP

Supplier Escalation Process

Pythonsupplier_escalation_tracker.py

#!/usr/bin/env python3
# Supplier non-conformance escalation tracker (8D-based)
from datetime import date, timedelta

non_conformances = [
    {
        "id": "NC-2026-007",
        "supplier": "Tier1_Supplier_B",
        "description": "ASPICE SWE.4 unit verification Level 1 (target: Level 2); traceability missing",
        "date_raised": "2026-02-01",
        "8d_due":  "2026-02-15",  # 14 days
        "8d_status": "Submitted",
        "rca_root_cause": "No systematic unit test planning; tests written ad-hoc with no requirement link",
        "corrective_action": "Implement TESSY-Polarion traceability; train test engineers by 2026-04-01",
        "action_due": "2026-04-01",
        "oem_approved_closure": False,
    },
]

print("Supplier Non-Conformance Tracker:")
for nc in non_conformances:
    overdue_8d = date.today() > date.fromisoformat(nc["8d_due"]) and nc["8d_status"] == "Not submitted"
    print(f"  [{nc['id']}] {nc['supplier']}: {nc['description'][:60]}")
    print(f"    8D Due: {nc['8d_due']} — Status: {nc['8d_status']}")
    print(f"    RCA: {nc['rca_root_cause'][:80]}")
    print(f"    Action: {nc['corrective_action'][:80]}")
    print(f"    Closure: {'Approved' if nc['oem_approved_closure'] else 'Pending OEM review'}")
    if overdue_8d: print("    ⚠️ 8D OVERDUE — Escalate to management")
    print()

Summary

OEM-supplier compliance management is a continuous relationship, not a point-in-time audit. The CAR before nomination sets baseline expectations; the 6–12 month monitoring cadence detects drift before it becomes SOP-blocking; the SOP gate checklist provides the final hard gate with clear blocking criteria. Supplier escalation via 8D ensures that non-conformances get root-cause analysis rather than just superficial fixes — the 8D's D7 (prevention) step is what prevents recurrence and improves the supplier's ASPICE capability over time.

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