Use Case Automotive · Munich BMW Tier-1 Cluster · ASPICE + EU AI Act

ASPICE + ISO 26262 + EU AI Act in one Decision Chain - for BMW Tier-1 suppliers with group works council reality

BMW Tier-1 supplier chain with ASPICE Level 2-3 + IATF 16949 + EU AI Act Annex III. Ramp-up decisions for model launches in 6-12 months lead time. Konzern-BR-experienced. UK ASPICE assessor parallel via intacs.

Workshop at Grindelberg All 7 use cases ←

Chapter 1 - Three Standards in Parallel

ASPICE Level 2-3 + ISO 26262 + EU AI Act - in one Decision Chain per engineering decision.

A BMW Tier-1 supplier with a plant in Greater Munich (Bosch Munich, Continental Regensburg, ZF Bayern, Webasto Stockdorf, Brose Würzburg) carries three standards in parallel per engineering decision: ASPICE Level 2-3 (Automotive SPICE per ISO/IEC 33002 for engineering process quality), ISO 26262 (Functional Safety, ASIL classification A to D for road vehicles), IATF 16949 (Automotive QMS, annual surveillance + 3-year re-certification).

Plus across the board: EU AI Act Annex III Point 4 for HR-IT systems (candidate selection, promotion, termination) at Tier-1 with > 250 employees - high-risk obligations from 2 August 2026 under current law, provisionally postponed to 2 December 2027 under the Digital Omnibus of 7 May 2026 (formal adoption still pending, as of June 2026), while the fine regime is already active since August 2026 (up to EUR 35M or 7% of group turnover). Plus BMW-specific: BMW Group Standard 90020 (Functional Safety BMW interpretation), BMW QPA (Quality Process Audit), BMW Software Excellence Cluster membership. UK parallel: UK automotive suppliers face the same ASPICE assessor standard via intacs; ICO is additionally relevant for HR-IT systems under UK GDPR Art. 22.

Operational reality at BMW ramp-up: 12-24 months lead time for model launch (BMW iX, i7, NEUE KLASSE). Tier-1 must ramp 200-400 engineers in 6-12 months lead time. Recruiting pipeline runs in parallel with ASPICE audit preparation + IATF surveillance + group works council consultation per § 99 BetrVG. Decision-Layer split typically: 35% RULES (IG Metall Bayern tariff logic, Tier-1 skill match tables, ASPICE audit compliance checks), 15% AI AUTONOMOUS (CV pre-triage, skill-profile mapping, BMW-GS conformity scoring), 50% HUMAN (promotion + selection + termination per EU AI Act Annex III + § 87 BetrVG co-determination).

Audit trail per HR/engineering decision: ASPICE process ID (e.g. aspice_sup8_v3.2 Configuration Management), ISO 26262 ASIL level (B+), BMW-GS-90020 conformity score, group works council consultation status, EU AI Act logging per Art. 12. At an IATF audit + ASPICE assessment + BMW supplier audit: 1-click export per audit format. With April 2026 BayLDA fine risk, every HR AI decision must have GDPR Art. 22 + Annex III logging.

Chapter 2 - Decision Record for a Tier-1 Recruiting Decision

How a BMW ramp-up recruiting decision runs in the Decision-Layer.

Anonymised decision record for a Tier-1 recruiting decision at a Munich BMW software supplier. 12-month lead time for BMW NEUE KLASSE launch. 240 ASPICE engineers to ramp. Incoming application Senior Software Engineer (ASPICE Level 3 + ISO 26262 ASIL B experience).

REC-BMW-NK-2026-05-17-09:42:17

Application Senior SW Engineer · BMW NEUE KLASSE software team · received 17.05.2026 09:42 · ASPICE L3 + ISO 26262 ASIL-B + 8 years professional experience

Result Recommended for 1st interview · Works council consultation mandatory activated
  1. 01 REGEL

    Eligibility check

    Application via internal ATS. Mandatory fields completed (CV, ASPICE certificates, ISO 26262 training records). Job requirement BMW NEUE KLASSE Software Battery Management System. Rule elig_bmw_nk_v2.3.

    ✓ Eligible
  2. 02 REGEL

    ASPICE level verification

    ASPICE Level 3 certificate (intacs assessor standard) verified against the INTACS database. Valid until 04/2028. Certificate number linked in ATS. Rule aspice_intacs_v1.4.

    ✓ ASPICE L3 verified
  3. 03 REGEL

    ISO 26262 ASIL experience match

    ASIL B experience documented in application records (Battery Management System at previous supplier). BMW NEUE KLASSE requirement is ASIL B. Match is deterministic. Rule iso26262_match_v2.1.

    ✓ ASIL-B match
  4. 04 KI

    Skill-profile mapping (model <code>tier1-skill-classifier-v2.4</code>)

    Input: CV full text, skill tags from previous applications, ASPICE process experience. Output: skill-match score 0.91 against the BMW NEUE KLASSE requirements catalogue. Sentiment analysis of self-assessment positive.

    Confidence 0.91 · threshold 0.85

    ✓ Strong profile match
  5. 05 REGEL

    BMW-GS-90020 Functional Safety conformity

    Training records show BMW-specific Functional Safety extension (BMW GS 90020 Module A + B). On supplier switch to us: re-certification not necessary (mutual recognition within BMW supplier cluster). Rule bmw_gs_90020_v3.1.

    ✓ BMW-GS conform
  6. 06 REGEL

    Anti-discrimination pre-check (GDPR Art. 22)

    Statistical parity against previous-year recruiting quota (gender, age, severe disability, nationality). Candidate (37 years, female, German) within tolerance corridor. Rule agg_3_v3.2 (based on AGG - German Equality Act; UK equivalent: Equality Act 2010 Sec. 13-15).

    ✓ Parity within corridor
  7. 07 MENSCH

    Recruiter sign-off + interview recommendation

    Mandatory stop per EU AI Act Annex III. Recruiter Ms S. (Senior Talent Acquisition, BMW supplier experience) receives a structured dataset with skill-match score, ASPICE/ISO 26262 verification, BMW-GS conformity, bias pre-check. She decides on the interview invitation. Documented with timestamp + reasoning.

    ✓ Interview invitation confirmed
  8. 08 REGEL

    Works council consultation activation (BetrVG § 99)

    Senior SW Engineer hire into the BMW NEUE KLASSE team (40+ engineers) triggers § 99 BetrVG (personnel measure for group-relevant position). Works council template auto-generated with decision-record excerpt, skill-match score, BMW requirements reference. KBR chair (IG Metall Bayern, 19 years in office) receives notification. Rule betrvg_99_v1.7.

    ▲ Works council consultation in progress
  9. 09 REGEL

    EU AI Act logging + ASPICE audit-trail persist

    EU AI Act Art. 12 logging: model version (tier1-skill-classifier-v2.4), input hash, confidence score, human override (Ms S.), risk score, works council consultation status. ASPICE SUP.8 Configuration Management audit trail. BMW QPA audit-trail view. 1-click export for three audit formats. Rule aiact_aspice_qpa_v1.4.

    ✓ Audit trail persisted

Chapter 3 - Workshop at the Tier-1 or at Munich Urban Colab

Engineering head office Hallerstraße 8 Hamburg. Workshop in Munich on-site.

Engineering counterpart sits in Hamburg, Hallerstraße 8 - 6-hour ICE route or direct flight to Munich. Discovery and stakeholder workshops happen on-site - typically 2-3 day blocks at the Tier-1 group in Schwabing / Allach / Maxvorstadt or at Munich Urban Colab (Freddie-Mercury-Straße 5, Kreativquartier, joint venture UnternehmerTUM + City of Munich). Separate rooms for works-council sessions + auditor briefings + ASPICE pre-assessment.

Munich BMW Tier-1 workshop pattern: Day 1 = stakeholder mapping (Engineering + Quality + HR + Compliance + Konzernbetriebsrat with IG Metall expert). Day 2 = Decision-Layer demo with Tier-1-specific use cases (recruiting, defect classification, engineering decision support, supplier evaluation). Day 3 = ASPICE/ISO 26262 audit-trail integration + BMW QPA preparation + mock IATF surveillance session. Workshop under EUR 10,000. Group procurement friendly.

Integration with Tier-1 existing IT: Decision-Layer integrates with ATS systems (Workday, SAP SuccessFactors, Personio, Cornerstone OnDemand), engineering tooling (Polarion, Jira, Azure DevOps), ASPICE assessment tools (intacs tools, Kugler Maag audit tool), BMW-specific Tier-1 portals (BMW Group Supplier Portal, BMW Standards Repository). REST/GraphQL/SOAP adapters depending on Tier-1 system. Source code of the adapters is handed over with the repository to the Tier-1 - no vendor lock-in of the interfaces.

After the workshop: 3-4 weeks build phase with productive pilot. One use case live (typically HR recruiting or engineering defect classification). Source code at the Tier-1, Decision-Layer UI for internal audit trails. After 12-18 months the Tier-1 engineering team operates the Decision-Layer without us - including ASPICE audit preparation + BMW QPA compliance + EU AI Act logging. For UK-headquartered groups with German Tier-1 plants: workshop in English with remote bridge to UK head office.

Related use cases

Frequently asked questions

Which automotive compliance standards does the Decision-Layer cover?
The three core automotive standards plus the AI layer. ASPICE (Automotive SPICE Level 2-3 per ISO/IEC 33002) covers engineering process quality, ISO 26262 covers functional safety (ASIL A-D), and IATF 16949 is the automotive QMS. On top sits EU AI Act Annex III Point 4 for HR-IT systems at Tier-1 suppliers, with GDPR Art. 22 for automated personnel decisions, and BMW-specific standards (BMW Software Excellence Cluster, iX/i7/NEUE KLASSE). One architecture serves the IATF audit, ASPICE assessment and BMW supplier audit. UK automotive suppliers face the same ASPICE assessor standard via intacs, with the ICO relevant for HR-IT under UK GDPR Art. 22.
What does BMW ramp-up decision mean in practice?
BMW typically announces a model launch 12-24 months before start-of-production. Tier-1 suppliers (Bosch, Continental, ZF Friedrichshafen, Webasto, Brose) must have ramped 200-400 engineers in a 6-12 month lead-time window. HR decisions in this window: recruiting (200+ positions in parallel), internal transfers (with group works council consultation per § 99 BetrVG - German Works Constitution Act; UK equivalent: ICE Regulations + works council consultation), supplier-switch evaluation, ASPICE audit preparation. Decision-Layer split: 35% RULES (IG Metall tariff logic, Tier-1 skill match, ASPICE audit compliance), 15% AI AUTONOMOUS (CV pre-triage, skill-profile mapping), 50% HUMAN (promotion + selection per EU AI Act Annex III + § 87 BetrVG).
How is the ASPICE audit requirement covered in a Tier-1 supplier with Decision-Layer?
ASPICE Level 3 (Established Process) requires documented process performance indicators + audit trail per engineering decision. For AI-supported engineering decision support (e.g. defect classification, software test prioritisation): audit trail must show model version, input hash, confidence score. If AI is involved in functional-safety-relevant decisions (ASIL B+): ISO 26262 Part 8 (Supporting Processes) requires a qualified software tool. The Decision-Layer is classified as Tool Confidence Level 2-3. BMW supplier audit captures this in the BMW Quality Process Audit (QPA). UK clients selling into BMW: intacs assessor recognition is mutual, no double certification needed.
How does the group works council co-determination work in the Munich automotive context?
Munich automotive group works councils (Konzernbetriebsräte, KBR - at BMW and Munich Tier-1 plants such as MAN Allach) are among the most experienced in Germany. When AI is introduced, § 87 (1) No. 6 BetrVG applies (mandatory co-determination on technical systems for behaviour/performance monitoring), and the § 80 (3) BetrVG expert right for AI is consistently exercised, usually with IG-Metall Bayern experts. A negotiation prerequisite is a group works agreement (Konzernbetriebsvereinbarung) with measurable escalation thresholds, audit-trail UI access for experts and a technically enforced human-in-the-loop. The Munich Urban Colab workshop runs a separate works-council session with a template-BV demonstration. The UK equivalent is works-council consultation under ICE Regulations plus the ACAS Code on AI.
Which BMW supplier compliance requirements are specific?
BMW Group Standards (BMW-GS) for software suppliers: BMW Software Excellence Cluster membership, BMW Group Standard 90020 (Functional Safety BMW-specific interpretation of ISO 26262), BMW Quality Process Audit (QPA), BMW Engineering Process Assessment (EPA). For AI components in BMW-relevant software (Autonomous Driving, Battery Management, Charging Decision): audit trail must be accessible in BMW audit format, language versions DE+EN as standard. Source-code handover to BMW is mandatory for strategic components - the Decision-Layer architecture supports this through the repository-handover pattern (source code stays with the client, no vendor lock-in).

Schedule workshop at Grindelberg

3-day discovery: Day 1 process analysis, Day 2 Decision-Layer mapping, Day 3 use-case prioritisation. Concrete deliverable.

Schedule meeting

Discovery workshop below EUR 10,000. Pilot fixed price discussed after the workshop.

← Back to overview: AI Agents Hamburg (7 use cases)