The Complete Guide to Automotive SPICE
Process reference model, capability levels, and assessment methodology - from the fundamentals to sustainable process improvement in series development.
What is Automotive SPICE?
Automotive SPICE (Software Process Improvement and Capability dEtermination) is a process reference and assessment model developed specifically for software development in the automotive industry. It is based on ISO/IEC 15504 (SPICE) and was adapted by the HIS consortium (Herstellerinitiative Software) of German OEMs for use in series development. The current version is Automotive SPICE 3.1, published in 2017 by the VDA Automotive SPICE working group. The model is today the de facto standard for suppliers with software content in embedded systems.
The model distinguishes between the Process Reference Model (PRM), which describes which processes must be present, and the Process Assessment Model (PAM), which describes how their maturity is evaluated. For tier-1 and tier-2 suppliers with software content in safety-critical systems, an Automotive SPICE assessment is today a de facto prerequisite for OEM projects. The HIS scope defines 15 processes that OEMs typically evaluate in supplier assessments.
HIS Scope: the relevant process selection for suppliers
The HIS Scope covers 15 processes: SYS.1-SYS.5 (System Engineering), SWE.1-SWE.6 (Software Engineering), MAN.3 (Project Management), SUP.1 (Quality Assurance), SUP.8 (Configuration Management), SUP.9 (Problem Resolution Management), SUP.10 (Change Request Management), and ACQ.4 (Supplier Monitoring). Capability Level 2 in all HIS Scope processes is the minimum requirement of most OEMs.
Why Automotive SPICE is essential for suppliers
Assessments are not a bureaucratic compliance exercise. Mature processes per Automotive SPICE reduce project risk, shorten development cycles, and secure supplier capability.
OEM prerequisite for project access
Without demonstrated Automotive SPICE maturity (typically CL2 in the HIS Scope), suppliers are not qualified in many projects. The assessment result is an integral part of supplier approval and is evaluated across projects.
Reduced project escalations
Mature requirements management and test processes (SWE.1, SWE.6) prevent late requirement changes and costly rework. Suppliers at CL3 demonstrably show significantly fewer field issues than those at CL1.
Traceability from requirement to test
SWE.1 through SWE.6 enforce complete traceability: from stakeholder requirement through software architecture to qualification test. This is simultaneously a prerequisite for ISO 26262 ASIL B/C/D projects.
Structured project management
MAN.3 requires project plans with measurable milestones, resource planning at activity level, and a risk register. This creates transparency for the OEM and reduces schedule overruns through early risk detection.
Configuration management as the traceability foundation
SUP.8 ensures that software versions, tools, and documents are versioned and reproducible. Without this process at at least CL2, reliable tracing of field issues back to defined software versions is not possible.
Continuous process improvement
Automotive SPICE is not a one-time certification goal but an improvement framework. Organizations that regularly assess internally and externally systematically improve their capability level and build a sustainable quality advantage.
Process reference model, PAM, and capability levels in detail
The PRM structures all processes into three groups: Primary Life Cycle Processes (Acquisition, Supply, Engineering), Supporting Life Cycle Processes (Quality Assurance, Configuration Management, Problem Resolution, Change Request), and Organizational Life Cycle Processes (Management, Process Improvement, Reuse). Each process is defined by its purpose and outcomes. The PAM adds measurable Base Practices (BP) and Work Products (WP) to each outcome, which serve as evidence in the assessment. Generic Practices (GP) and Generic Resources (GR) describe what is additionally expected at each capability level.
The six capability levels build on each other: CL0 (Incomplete) - process not or only partially implemented. CL1 (Performed) - base practices are executed, process outcomes are achieved, but without systematic management. CL2 (Managed) - additionally: planning, monitoring, control of work, plus verification and configuration management of work products (GP 2.1-2.4). CL3 (Established) - additionally: defined standard process, tailoring guidelines, process description, and use of a process infrastructure (GP 3.1-3.2). CL4 (Predictable) - process performance is quantitatively measured and controlled. CL5 (Innovating) - continuous process innovation based on quantitative analysis. For most OEM projects, CL2 is mandatory; safety-critical systems increasingly require CL3 in engineering processes.
Implementing Automotive SPICE - step by step
A realistic roadmap from gap analysis to a successful assessment - designed for tier-1/2 suppliers with 50 to 500 developers.
Gap analysis against the HIS Scope
Internal assessment of all 15 HIS Scope processes: which base practices exist? Which work products are present and sufficient? The result is a prioritized gap matrix showing where CL1 is not yet achieved and which processes have the greatest distance to the target capability level.
Set target capability level per process
Capture OEM requirements for current and planned projects. Typical target: CL2 for all 15 HIS processes short-term, CL3 for SWE.1, SWE.2, SWE.4, SWE.6, and MAN.3 medium-term. The target level must be set per process - blanket statements without process reference are worthless in an assessment.
Build process definitions and work products
Create process descriptions, templates, and checklists for each HIS process. Work products must conform to a defined format and be stored in a revision-safe way. Special attention goes to the traceability matrix between SWE.1 (software requirements), SWE.2 (architecture), SWE.3 (detailed design), and SWE.6 (qualification test).
Pilot project and internal trial assessments
Pilot processes in a running development project. Internal assessors (intacs-trained practitioners or experienced senior developers) conduct gap assessments and document findings as improvement items. Findings are tracked as projects - with owners, deadlines, and effectiveness evidence.
Build competence for all roles
Automotive SPICE is not a pure QA topic: developers must understand what Unit Test Specification (SWE.4) requires as a work product; testers what a Software Integration Test Report (SWE.5) must deliver; project managers what artefacts MAN.3 requires at CL2. Role-specific training is more efficient than generic SPICE introductions.
External assessment and improvement action plan
An intacs-certified assessor conducts the formal assessment. Every weakness and non-conformance is documented as a finding. The resulting Improvement Action Plan (IAP) is the central management document: findings prioritized by severity, with actions, owners, and target dates. The IAP is checked for implementation at the next assessment.
Typical challenges - and how to solve them
Automotive SPICE implementations rarely fail because of QA knowledge. They fail due to insufficient project applicability of processes and missing tool support.
Processes exist on paper but not in lived project practice
Process definitions without lived practice are worthless - and experienced assessors detect this in minutes of interviewing. The only valid preparation: pilot projects with real documentation, real reviews, and real test results as evidence. Mobile2b makes it possible to maintain audit checklists for each HIS process and document proof of execution with a complete timestamp trail.
Traceability between requirements, design, and tests cannot be established
SWE.1 through SWE.6 require a complete traceability chain as a work product. Without dedicated tool support (Polarion, IBM DOORS, Jama Connect), this is not manageable with more than a few hundred requirements. The traceability matrix must be available for inspection in the assessment at any time - an Excel sheet is evaluated as insufficient from CL2 onward.
MAN.3 fails due to insufficient project plan detail
CL2 in MAN.3 requires more than a milestone plan: resource planning at activity level, a risk register with quantified assessment and countermeasures, regular documented plan-actual comparisons, and defined escalation paths. Generic Practice GP 2.2 (Work Product Management) checks whether the project plan itself is maintained and versioned as a work product.
Assessment preparation ties up too many resources at short notice
Assessment preparation as a sprint before the date creates duplicate work and delivers no sustainable process improvements. Processes must be anchored in daily development work. Digital audit tools enable continuous internal compliance checks per project, so the effort for the formal assessment shrinks to the unavoidable minimum.
Managing Automotive SPICE digitally with Mobile2b
Assessment preparation is not a one-time project but continuous process monitoring. Mobile2b creates the infrastructure to make Automotive SPICE compliance measurable and demonstrable.
HIS Scope checklists for internal assessments
Predefined audit checklists for all 15 HIS Scope processes with direct reference to base practices and generic practices per Automotive SPICE 3.1. Internal trial assessments are conducted in a structured way, findings immediately classified and created as improvement items.
Finding and improvement item tracking
Every weakness and non-conformance from internal or external assessments is captured as an improvement item: process reference, capability level impact, owner, actions, due date, and effectiveness evidence. The Improvement Action Plan is complete and current at all times.
Cross-project capability reporting
Capability level status across all running projects at a glance. Which processes are stable at CL2? Where do multiple projects show the same weaknesses in the same base practices? This is the data foundation for targeted organization-wide improvement initiatives.
Audit trail for external assessors
All internal audit results, findings, action evidence, and improvement histories are stored in a revision-safe way and exportable for external assessors at the click of a button. This accelerates external assessments and demonstrates proactive process management.
Frequently asked questions about Automotive SPICE
Ready for your next Automotive SPICE assessment?
Mobile2b supports your internal assessment preparation with structured HIS Scope checklists, complete finding documentation, and cross-project capability reporting.
Book a Demo