Automotive SPICE (ASPICE) Consulting & Process Assessment
Automotive SPICE (ASPICE) is a process capability assessment model, based on ISO/IEC 15504, used across the automotive industry to evaluate and improve the maturity of engineering development processes. Defined by the VDA QMC Process Assessment Model (PAM), currently at version 4.0, it is widely required by OEMs as a supplier qualification criterion. PRAETORIO helps automotive suppliers assess, improve, and prepare for Automotive SPICE assessments across their systems and software engineering processes.
Automotive SPICE assesses how consistently and capably a process is performed: it is a process maturity model, not a product safety or security standard, and needs to be understood and applied as such.
What Automotive SPICE Covers
Automotive SPICE defines process assessment across engineering and supporting process groups:
- System engineering processes: requirements elicitation, system architectural design, and system-level integration and verification.
- Software engineering processes: software requirements analysis, architectural and detailed design, unit verification, and software integration and testing.
- Supporting processes: quality assurance, configuration management, problem resolution, and change request management.
- Process capability levels: each assessed process is rated on a capability scale, from incompletely performed (Level 0) through performed, managed, established, predictable, and optimizing (Level 5), based on defined process attributes.
- Assessment scope (VDA Scope): a defined subset of processes commonly required by German OEMs as part of supplier qualification, distinct from the full PAM process reference model.
Why Automotive SPICE Matters
OEM supplier qualification routinely requires it. Many automotive OEMs, particularly in the DACH region, require Automotive SPICE capability level ratings as a condition of program award or continued supplier status.
It is a process model, not a product standard. Automotive SPICE assesses whether development processes are performed capably and consistently; it does not itself verify product-level functional safety or cybersecurity properties: those require ISO 26262 and ISO/SAE 21434 respectively, assessed separately.
The model is between versions. PAM v4.0 is the current released version, with a v4.1 preview already in circulation as of 2026: organizations building or refreshing their process framework should track the revision’s progress rather than assuming v4.0 is final indefinitely.
Process maturity and product compliance are complementary, not interchangeable. Automotive SPICE capability can support confidence in the rigor behind a functional safety or cybersecurity case, but it does not substitute for the dedicated activities those standards require.
Assessment readiness takes real lead time. Achieving a target capability level requires processes to actually operate at that level over multiple project cycles with objective evidence: it cannot be manufactured shortly before an assessment.
Our Approach
PRAETORIO supports Automotive SPICE programs across gap analysis, improvement, and assessment preparation:
- Scope definition: determine the relevant process scope (e.g. VDA Scope) and target capability levels based on customer or program requirements.
- Gap assessment: evaluate current process performance against the applicable Automotive SPICE PAM process attributes.
- Process definition and improvement: define or refine process documentation, work products, and practices to close identified gaps.
- Pilot project support: support a pilot project applying improved processes to generate objective evidence of capability.
- Internal assessment (self-assessment): conduct an internal assessment to validate readiness ahead of a formal assessment.
- Formal assessment support: support engagement with an accredited assessor for a formal Automotive SPICE assessment.
- Continuous improvement: support ongoing process maintenance and improvement following assessment.
Deliverables
- Process scope and target capability level definition
- Gap assessment report against applicable Automotive SPICE PAM requirements
- Process definition and work product templates
- Pilot project evidence and lessons learned
- Internal assessment (self-assessment) results
- Formal assessment readiness support and documentation
How PRAETORIO Can Support Your Team
- Gap assessment, evaluating current engineering processes against Automotive SPICE PAM requirements for a defined scope.
- Process definition and documentation, establishing or improving process descriptions, templates, and work products to close identified gaps.
- Pilot project support, applying improved processes on a real project to generate assessment-ready evidence.
- Internal assessment support, conducting a self-assessment to validate readiness before engaging a formal assessor.
- Formal assessment preparation, organizing documentation and evidence ahead of an accredited Automotive SPICE assessment.
- Coordination with functional safety and cybersecurity programs, aligning process improvement work with ISO 26262 and ISO/SAE 21434 activities running in parallel.
Typical Use Cases
- A supplier needing to reach a target Automotive SPICE capability level as a condition of an OEM program award.
- An organization needing a gap assessment ahead of a customer-mandated formal assessment.
- A team whose development processes are informally followed but not documented or evidenced to the level Automotive SPICE requires.
- A supplier preparing a pilot project to generate objective evidence of improved process capability.
- An organization needing to coordinate Automotive SPICE process improvement with parallel ISO 26262 or ISO/SAE 21434 compliance work.
- A company needing process engineering capacity to augment an internal quality or process improvement team.
Why PRAETORIO
- Practical engineering background across systems, software, and automotive product development, so process improvement recommendations reflect how engineering work actually happens, not abstract process theory.
- More than 15 years of experience in automotive engineering, working within and alongside process-assessed development environments.
- Cross-domain perspective connecting Automotive SPICE process maturity to functional safety and cybersecurity engagements, supporting coordinated rather than siloed improvement efforts.
- Engineering-oriented delivery: process improvements are validated through real project evidence, not delivered as documentation templates alone.
Related Services
- Functional Safety Consulting: functional safety work that Automotive SPICE process maturity can support
- ISO 26262 Consulting: the product-level safety standard distinct from but complementary to Automotive SPICE
- Systems Engineering: systems engineering processes within the Automotive SPICE scope
- Embedded Software Development: software engineering processes assessed under Automotive SPICE
- Embedded Systems Engineering: system engineering processes assessed under Automotive SPICE
- Cybersecurity Engineering: cybersecurity engineering processes often coordinated alongside Automotive SPICE improvement
FAQ
What is Automotive SPICE?
Automotive SPICE (ASPICE) is a process capability assessment model, based on ISO/IEC 15504, used to evaluate the maturity of systems and software engineering processes at automotive suppliers, defined by the VDA QMC Process Assessment Model (PAM).
What is the current version of the Automotive SPICE PAM?
Automotive SPICE PAM v4.0 is the current released version. A v4.1 preview has been circulated by VDA QMC as of 2026 but had not been finalized as of this writing: organizations should confirm the latest released version directly with VDA QMC before starting a new assessment cycle.
What are Automotive SPICE capability levels?
Capability levels range from Level 0 (incompletely performed) through Level 1 (performed), Level 2 (managed), Level 3 (established), Level 4 (predictable), and Level 5 (optimizing), based on defined process attributes evaluated during assessment.
Does Automotive SPICE certification mean a product is functionally safe or secure?
No. Automotive SPICE assesses process capability, not product-level safety or security properties. Functional safety requires ISO 26262 compliance and cybersecurity requires ISO/SAE 21434 compliance, assessed through their own dedicated activities.
What is the VDA Scope?
The VDA Scope is a defined subset of Automotive SPICE processes, commonly required by German OEMs as part of supplier qualification, narrower than the full PAM process reference model.
How long does it take to reach a target Automotive SPICE capability level?
It depends on the current process maturity and target level, but reaching a target level typically requires multiple project cycles operating at that level to generate sufficient objective evidence: it is not achievable through documentation alone shortly before an assessment.
Can PRAETORIO support process improvement without owning the full assessment engagement?
Yes. Many engagements involve gap assessment, process definition, or pilot project support for a defined scope, with the formal assessment itself conducted by an independent accredited assessor as required by the Automotive SPICE assessment model.
Need to Assess, Improve, or Prepare for an Automotive SPICE Assessment?
PRAETORIO can support your team from gap assessment through process improvement and formal assessment readiness. Contact us to discuss your Automotive SPICE requirements.
Contact Us