Automotive SPICE (ASPICE) v4.1 - Process Assessment Model
Automotive SPICE is the VDA Quality Management Center's process reference and assessment model for automotive system, software, hardware and machine learning engineering, built on the ISO/IEC 33020 measurement framework and assessed by intacs certified assessors. Version 4.1 (released 24 August 2026) revises 4.0 (2023) by removing MLE.2 BP5 with editorial changes. The graph models the 195 base practices of the 32 processes across 11 process groups and the 34 generic practices of the nine process attributes that carry capability levels 1 to 5.
Automotive SPICE (ASPICE) v4.1 - Process Assessment Model is a compliance framework from Global (VDA QMC; automotive OEMs and their suppliers, intacs assessment scheme) with 12 domains and 229 controls that map to 196 other frameworks. The largest domains are Capability levels and process attributes (PA 1.1 to PA 5.2) – Automotive SPICE (ASPICE) v4.1 - Process Assessment Model (34 controls), Supporting process group (SUP) – Automotive SPICE (ASPICE) v4.1 - Process Assessment Model (34 controls), Software engineering process group (SWE) – Automotive SPICE (ASPICE) v4.1 - Process Assessment Model (33 controls). Every control below carries what it requires and what an assessor expects to see.
Framework summaries on this platform are AI-assisted interpretations for educational and compliance planning purposes. They do not reproduce or replace the official standards. Refer to the authoritative source for the definitive text. Framework names and trademarks belong to their respective organisations.
Framework Domains (12)
Acquisition process group (ACQ) – Automotive SPICE (ASPICE) v4.1 - Process Assessment Model
| Code | Title |
|---|---|
| automotive-spice-aspice-v4-1-process-assessment-model::ACQ.4.BP1 | ACQ.4.BP1 Agree on and maintain joint activities, joint interfaces, and information to be exchanged |
| automotive-spice-aspice-v4-1-process-assessment-model::ACQ.4.BP2 | ACQ.4.BP2 Exchange all agreed information |
| automotive-spice-aspice-v4-1-process-assessment-model::ACQ.4.BP3 | ACQ.4.BP3 Review development work products with the supplier |
| automotive-spice-aspice-v4-1-process-assessment-model::ACQ.4.BP4 | ACQ.4.BP4 Review progress of the supplier |
| automotive-spice-aspice-v4-1-process-assessment-model::ACQ.4.BP5 | ACQ.4.BP5 Act to correct the deviations |
Capability levels and process attributes (PA 1.1 to PA 5.2) – Automotive SPICE (ASPICE) v4.1 - Process Assessment Model
| Code | Title |
|---|---|
| automotive-spice-aspice-v4-1-process-assessment-model::GP 1.1.1 | GP 1.1.1 Achieve the process outcomes Achieve the intent of the base practices |
| automotive-spice-aspice-v4-1-process-assessment-model::GP 2.1.1 | GP 2.1.1 Identify the objectives and define a strategy for the performance of the process |
| automotive-spice-aspice-v4-1-process-assessment-model::GP 2.1.2 | GP 2.1.2 Plan the performance of the process |
| automotive-spice-aspice-v4-1-process-assessment-model::GP 2.1.3 | GP 2.1.3 Determine the resource needs |
| automotive-spice-aspice-v4-1-process-assessment-model::GP 2.1.4 | GP 2.1.4 Identify and make available the resources |
| automotive-spice-aspice-v4-1-process-assessment-model::GP 2.1.5 | GP 2.1.5 Monitor and adjust the performance of the process |
| automotive-spice-aspice-v4-1-process-assessment-model::GP 2.1.6 | GP 2.1.6 Manage the interfaces between involved parties |
| automotive-spice-aspice-v4-1-process-assessment-model::GP 2.2.1 | GP 2.2.1 Define the requirements for the work products |
| automotive-spice-aspice-v4-1-process-assessment-model::GP 2.2.2 | GP 2.2.2 Define the requirements for storage and control of the work products |
| automotive-spice-aspice-v4-1-process-assessment-model::GP 2.2.3 | GP 2.2.3 Identify, store and control the work products |
| automotive-spice-aspice-v4-1-process-assessment-model::GP 2.2.4 | GP 2.2.4 Review and adjust work products |
| automotive-spice-aspice-v4-1-process-assessment-model::GP 3.1.1 | GP 3.1.1 Establish and maintain the standard process |
| automotive-spice-aspice-v4-1-process-assessment-model::GP 3.1.2 | GP 3.1.2 Determine the required competencies |
| automotive-spice-aspice-v4-1-process-assessment-model::GP 3.1.3 | GP 3.1.3 Determine the required resources |
| automotive-spice-aspice-v4-1-process-assessment-model::GP 3.1.4 | GP 3.1.4 Determine suitable methods to monitor the standard process |
| automotive-spice-aspice-v4-1-process-assessment-model::GP 3.2.1 | GP 3.2.1 Deploy a defined process that satisfies the context specific requirements of the use of the standard process |
| automotive-spice-aspice-v4-1-process-assessment-model::GP 3.2.2 | GP 3.2.2 Ensure the required competencies for the defined roles |
| automotive-spice-aspice-v4-1-process-assessment-model::GP 3.2.3 | GP 3.2.3 Ensure the required resources to support the performance of the defined process |
| automotive-spice-aspice-v4-1-process-assessment-model::GP 3.2.4 | GP 3.2.4 Monitor the performance of the defined process |
| automotive-spice-aspice-v4-1-process-assessment-model::GP 4.1.1 | GP 4.1.1 Identify the business goals |
| automotive-spice-aspice-v4-1-process-assessment-model::GP 4.1.2 | GP 4.1.2 Establish the process information needs |
| automotive-spice-aspice-v4-1-process-assessment-model::GP 4.1.3 | GP 4.1.3 Identify the measurable relationships between process elements |
| automotive-spice-aspice-v4-1-process-assessment-model::GP 4.1.4 | GP 4.1.4 Derive a process measurement approach and select the analysis techniques |
| automotive-spice-aspice-v4-1-process-assessment-model::GP 4.1.5 | GP 4.1.5 Establish quantitative control limits |
| automotive-spice-aspice-v4-1-process-assessment-model::GP 4.1.6 | GP 4.1.6 Collect product and process measurement results through performing the defined process |
| automotive-spice-aspice-v4-1-process-assessment-model::GP 4.2.1 | GP 4.2.1 Identify the variations in process performance |
| automotive-spice-aspice-v4-1-process-assessment-model::GP 4.2.2 | GP 4.2.2 Identify the causes of variation |
| automotive-spice-aspice-v4-1-process-assessment-model::GP 4.2.3 | GP 4.2.3 Identify and implement corrective actions to address assignable causes |
| automotive-spice-aspice-v4-1-process-assessment-model::GP 5.1.1 | GP 5.1.1 Define the process innovation objectives for the process that support the relevant business goals |
| automotive-spice-aspice-v4-1-process-assessment-model::GP 5.1.2 | GP 5.1.2 Analyze the quantitative data of the process |
| automotive-spice-aspice-v4-1-process-assessment-model::GP 5.1.3 | GP 5.1.3 Identify the innovation opportunities |
| automotive-spice-aspice-v4-1-process-assessment-model::GP 5.2.1 | GP 5.2.1 Define and assess the impact of the proposed changes |
| automotive-spice-aspice-v4-1-process-assessment-model::GP 5.2.2 | GP 5.2.2 Implement the agreed process changes |
| automotive-spice-aspice-v4-1-process-assessment-model::GP 5.2.3 | GP 5.2.3 Evaluate the effectiveness of the process changes |
Hardware engineering process group (HWE) – Automotive SPICE (ASPICE) v4.1 - Process Assessment Model
| Code | Title |
|---|---|
| automotive-spice-aspice-v4-1-process-assessment-model::HWE.1.BP1 | HWE.1.BP1 Specify the hardware requirements |
| automotive-spice-aspice-v4-1-process-assessment-model::HWE.1.BP2 | HWE.1.BP2 Structure the hardware requirements |
| automotive-spice-aspice-v4-1-process-assessment-model::HWE.1.BP3 | HWE.1.BP3 Analyze the hardware requirements |
| automotive-spice-aspice-v4-1-process-assessment-model::HWE.1.BP4 | HWE.1.BP4 Analyze the impact on the operating environment |
| automotive-spice-aspice-v4-1-process-assessment-model::HWE.1.BP5 | HWE.1.BP5 Ensure consistency and establish bidirectional traceability |
| automotive-spice-aspice-v4-1-process-assessment-model::HWE.1.BP6 | HWE.1.BP6 Communicate the agreed hardware requirements and the impact on the operating environment |
| automotive-spice-aspice-v4-1-process-assessment-model::HWE.2.BP1 | HWE.2.BP1 Specify the hardware architecture |
| automotive-spice-aspice-v4-1-process-assessment-model::HWE.2.BP2 | HWE.2.BP2 Specify the hardware detailed design |
| automotive-spice-aspice-v4-1-process-assessment-model::HWE.2.BP3 | HWE.2.BP3 Specify the dynamic aspects of the hardware architecture and the hardware detailed design |
| automotive-spice-aspice-v4-1-process-assessment-model::HWE.2.BP4 | HWE.2.BP4 Analyze the hardware architecture and the hardware detailed design |
| automotive-spice-aspice-v4-1-process-assessment-model::HWE.2.BP5 | HWE.2.BP5 Ensure consistency and establish bidirectional traceability |
| automotive-spice-aspice-v4-1-process-assessment-model::HWE.2.BP6 | HWE.2.BP6 Communicate the agreed hardware architecture and hardware detailed design |
| automotive-spice-aspice-v4-1-process-assessment-model::HWE.3.BP1 | HWE.3.BP1 Specify verification measures for the verification against the hardware design |
| automotive-spice-aspice-v4-1-process-assessment-model::HWE.3.BP2 | HWE.3.BP2 Ensure the use of compliant samples |
| automotive-spice-aspice-v4-1-process-assessment-model::HWE.3.BP3 | HWE.3.BP3 Select verification measures |
| automotive-spice-aspice-v4-1-process-assessment-model::HWE.3.BP4 | HWE.3.BP4 Verify against the hardware design |
| automotive-spice-aspice-v4-1-process-assessment-model::HWE.3.BP5 | HWE.3.BP5 Ensure consistency and establish bidirectional traceability |
| automotive-spice-aspice-v4-1-process-assessment-model::HWE.3.BP6 | HWE.3.BP6 Summarize and communicate the results |
| automotive-spice-aspice-v4-1-process-assessment-model::HWE.4.BP1 | HWE.4.BP1 Specify verification measures for the verification against the hardware requirements |
| automotive-spice-aspice-v4-1-process-assessment-model::HWE.4.BP2 | HWE.4.BP2 Ensure the use of compliant samples |
| automotive-spice-aspice-v4-1-process-assessment-model::HWE.4.BP3 | HWE.4.BP3 Select verification measures |
| automotive-spice-aspice-v4-1-process-assessment-model::HWE.4.BP4 | HWE.4.BP4 Verify the compliant hardware samples |
| automotive-spice-aspice-v4-1-process-assessment-model::HWE.4.BP5 | HWE.4.BP5 Ensure consistency and establish bidirectional traceability |
| automotive-spice-aspice-v4-1-process-assessment-model::HWE.4.BP6 | HWE.4.BP6 Summarize and communicate the results |
Machine learning engineering process group (MLE) – Automotive SPICE (ASPICE) v4.1 - Process Assessment Model
Management process group (MAN) – Automotive SPICE (ASPICE) v4.1 - Process Assessment Model
Process improvement process group (PIM) – Automotive SPICE (ASPICE) v4.1 - Process Assessment Model
| Code | Title |
|---|---|
| automotive-spice-aspice-v4-1-process-assessment-model::PIM.3.BP1 | PIM.3.BP1 Establish a commitment |
| automotive-spice-aspice-v4-1-process-assessment-model::PIM.3.BP2 | PIM.3.BP2 Identify improvement measures |
| automotive-spice-aspice-v4-1-process-assessment-model::PIM.3.BP3 | PIM.3.BP3 Establish process improvement goals |
| automotive-spice-aspice-v4-1-process-assessment-model::PIM.3.BP4 | PIM.3.BP4 Prioritize the improvements |
| automotive-spice-aspice-v4-1-process-assessment-model::PIM.3.BP5 | PIM.3.BP5 Define process improvement measures |
| automotive-spice-aspice-v4-1-process-assessment-model::PIM.3.BP6 | PIM.3.BP6 Implement the process improvement measures |
| automotive-spice-aspice-v4-1-process-assessment-model::PIM.3.BP7 | PIM.3.BP7 Confirm the process improvements |
| automotive-spice-aspice-v4-1-process-assessment-model::PIM.3.BP8 | PIM.3.BP8 Communicate the results of the improvements |
Reuse process group (REU) – Automotive SPICE (ASPICE) v4.1 - Process Assessment Model
| Code | Title |
|---|---|
| automotive-spice-aspice-v4-1-process-assessment-model::REU.2.BP1 | REU.2.BP1 Select products for reuse |
| automotive-spice-aspice-v4-1-process-assessment-model::REU.2.BP2 | REU.2.BP2 Analyze the reuse capability of the products |
| automotive-spice-aspice-v4-1-process-assessment-model::REU.2.BP3 | REU.2.BP3 Define the limitations for reuse |
| automotive-spice-aspice-v4-1-process-assessment-model::REU.2.BP4 | REU.2.BP4 Ensure the qualification of the products for reuse |
| automotive-spice-aspice-v4-1-process-assessment-model::REU.2.BP5 | REU.2.BP5 Provide the products for reuse |
| automotive-spice-aspice-v4-1-process-assessment-model::REU.2.BP6 | REU.2.BP6 Communicate information about the effectiveness of the reuse activities |
Software engineering process group (SWE) – Automotive SPICE (ASPICE) v4.1 - Process Assessment Model
| Code | Title |
|---|---|
| automotive-spice-aspice-v4-1-process-assessment-model::SWE.1.BP1 | SWE.1.BP1 Specify the software requirements |
| automotive-spice-aspice-v4-1-process-assessment-model::SWE.1.BP2 | SWE.1.BP2 Structure the software requirements |
| automotive-spice-aspice-v4-1-process-assessment-model::SWE.1.BP3 | SWE.1.BP3 Analyze the software requirements |
| automotive-spice-aspice-v4-1-process-assessment-model::SWE.1.BP4 | SWE.1.BP4 Analyze the impact on the operating environment |
| automotive-spice-aspice-v4-1-process-assessment-model::SWE.1.BP5 | SWE.1.BP5 Ensure consistency and establish bidirectional traceability |
| automotive-spice-aspice-v4-1-process-assessment-model::SWE.1.BP6 | SWE.1.BP6 Communicate the agreed software requirements and the impact on the operating environment |
| automotive-spice-aspice-v4-1-process-assessment-model::SWE.2.BP1 | SWE.2.BP1 Specify the static aspects of the software architecture |
| automotive-spice-aspice-v4-1-process-assessment-model::SWE.2.BP2 | SWE.2.BP2 Specify the dynamic aspects of the software architecture |
| automotive-spice-aspice-v4-1-process-assessment-model::SWE.2.BP3 | SWE.2.BP3 Analyze the software architecture |
| automotive-spice-aspice-v4-1-process-assessment-model::SWE.2.BP4 | SWE.2.BP4 Ensure consistency and establish bidirectional traceability |
| automotive-spice-aspice-v4-1-process-assessment-model::SWE.2.BP5 | SWE.2.BP5 Communicate the agreed software architecture |
| automotive-spice-aspice-v4-1-process-assessment-model::SWE.3.BP1 | SWE.3.BP1 Specify the static aspects of the detailed design |
| automotive-spice-aspice-v4-1-process-assessment-model::SWE.3.BP2 | SWE.3.BP2 Specify the dynamic aspects of the detailed design |
| automotive-spice-aspice-v4-1-process-assessment-model::SWE.3.BP3 | SWE.3.BP3 Develop the software units |
| automotive-spice-aspice-v4-1-process-assessment-model::SWE.3.BP4 | SWE.3.BP4 Ensure consistency and establish bidirectional traceability |
| automotive-spice-aspice-v4-1-process-assessment-model::SWE.3.BP5 | SWE.3.BP5 Communicate the agreed software detailed design and the developed software units |
| automotive-spice-aspice-v4-1-process-assessment-model::SWE.4.BP1 | SWE.4.BP1 Specify software unit verification measures |
| automotive-spice-aspice-v4-1-process-assessment-model::SWE.4.BP2 | SWE.4.BP2 Select software unit verification measures |
| automotive-spice-aspice-v4-1-process-assessment-model::SWE.4.BP3 | SWE.4.BP3 Verify the software units |
| automotive-spice-aspice-v4-1-process-assessment-model::SWE.4.BP4 | SWE.4.BP4 Ensure consistency and establish bidirectional traceability |
| automotive-spice-aspice-v4-1-process-assessment-model::SWE.4.BP5 | SWE.4.BP5 Summarize and communicate the results |
| automotive-spice-aspice-v4-1-process-assessment-model::SWE.5.BP1 | SWE.5.BP1 Specify software integration verification measures |
| automotive-spice-aspice-v4-1-process-assessment-model::SWE.5.BP2 | SWE.5.BP2 Specify verification measures for verifying the software component behavior |
| automotive-spice-aspice-v4-1-process-assessment-model::SWE.5.BP3 | SWE.5.BP3 Select verification measures |
| automotive-spice-aspice-v4-1-process-assessment-model::SWE.5.BP4 | SWE.5.BP4 Integrate the software elements and perform the integration verification |
| automotive-spice-aspice-v4-1-process-assessment-model::SWE.5.BP5 | SWE.5.BP5 Perform the software component verification |
| automotive-spice-aspice-v4-1-process-assessment-model::SWE.5.BP6 | SWE.5.BP6 Ensure consistency and establish bidirectional traceability |
| automotive-spice-aspice-v4-1-process-assessment-model::SWE.5.BP7 | SWE.5.BP7 Summarize and communicate the results |
| automotive-spice-aspice-v4-1-process-assessment-model::SWE.6.BP1 | SWE.6.BP1 Specify verification measures for the software verification |
| automotive-spice-aspice-v4-1-process-assessment-model::SWE.6.BP2 | SWE.6.BP2 Select verification measures |
| automotive-spice-aspice-v4-1-process-assessment-model::SWE.6.BP3 | SWE.6.BP3 Verify the integrated software |
| automotive-spice-aspice-v4-1-process-assessment-model::SWE.6.BP4 | SWE.6.BP4 Ensure consistency and establish bidirectional traceability |
| automotive-spice-aspice-v4-1-process-assessment-model::SWE.6.BP5 | SWE.6.BP5 Summarize and communicate the results |
Supply process group (SPL) – Automotive SPICE (ASPICE) v4.1 - Process Assessment Model
| Code | Title |
|---|---|
| automotive-spice-aspice-v4-1-process-assessment-model::SPL.2.BP1 | SPL.2.BP1 Define and agree the functional content of the releases |
| automotive-spice-aspice-v4-1-process-assessment-model::SPL.2.BP2 | SPL.2.BP2 Define the release package |
| automotive-spice-aspice-v4-1-process-assessment-model::SPL.2.BP3 | SPL.2.BP3 Ensure a unique identification of each release |
| automotive-spice-aspice-v4-1-process-assessment-model::SPL.2.BP4 | SPL.2.BP4 Build the release from items under configuration control |
| automotive-spice-aspice-v4-1-process-assessment-model::SPL.2.BP5 | SPL.2.BP5 Ensure the release approval before the delivery |
| automotive-spice-aspice-v4-1-process-assessment-model::SPL.2.BP6 | SPL.2.BP6 Provide a release note |
| automotive-spice-aspice-v4-1-process-assessment-model::SPL.2.BP7 | SPL.2.BP7 Communicate the type, service level and duration of support for each release |
| automotive-spice-aspice-v4-1-process-assessment-model::SPL.2.BP8 | SPL.2.BP8 Deliver the release package to the intended customer |
Supporting process group (SUP) – Automotive SPICE (ASPICE) v4.1 - Process Assessment Model
System engineering process group (SYS) – Automotive SPICE (ASPICE) v4.1 - Process Assessment Model
| Code | Title |
|---|---|
| automotive-spice-aspice-v4-1-process-assessment-model::SYS.1.BP1 | SYS.1.BP1 Identify stakeholders and obtain their expectations and requests |
| automotive-spice-aspice-v4-1-process-assessment-model::SYS.1.BP2 | SYS.1.BP2 Agree on the requirements |
| automotive-spice-aspice-v4-1-process-assessment-model::SYS.1.BP3 | SYS.1.BP3 Analyze the stakeholder requirements changes |
| automotive-spice-aspice-v4-1-process-assessment-model::SYS.1.BP4 | SYS.1.BP4 Communicate the requirements’ status |
| automotive-spice-aspice-v4-1-process-assessment-model::SYS.2.BP1 | SYS.2.BP1 Specify the system requirements |
| automotive-spice-aspice-v4-1-process-assessment-model::SYS.2.BP2 | SYS.2.BP2 Structure the system requirements |
| automotive-spice-aspice-v4-1-process-assessment-model::SYS.2.BP3 | SYS.2.BP3 Analyze the system requirements |
| automotive-spice-aspice-v4-1-process-assessment-model::SYS.2.BP4 | SYS.2.BP4 Analyze the impact on the system context |
| automotive-spice-aspice-v4-1-process-assessment-model::SYS.2.BP5 | SYS.2.BP5 Ensure consistency and establish bidirectional traceability |
| automotive-spice-aspice-v4-1-process-assessment-model::SYS.2.BP6 | SYS.2.BP6 Communicate the agreed system requirements and the impact on the system context |
| automotive-spice-aspice-v4-1-process-assessment-model::SYS.3.BP1 | SYS.3.BP1 Specify the static aspects of the system architecture |
| automotive-spice-aspice-v4-1-process-assessment-model::SYS.3.BP2 | SYS.3.BP2 Specify the dynamic aspects of the system architecture |
| automotive-spice-aspice-v4-1-process-assessment-model::SYS.3.BP3 | SYS.3.BP3 Analyze the system architecture |
| automotive-spice-aspice-v4-1-process-assessment-model::SYS.3.BP4 | SYS.3.BP4 Ensure consistency and establish bidirectional traceability |
| automotive-spice-aspice-v4-1-process-assessment-model::SYS.3.BP5 | SYS.3.BP5 Communicate the agreed system architecture |
| automotive-spice-aspice-v4-1-process-assessment-model::SYS.4.BP1 | SYS.4.BP1 Specify verification measures for the system integration |
| automotive-spice-aspice-v4-1-process-assessment-model::SYS.4.BP2 | SYS.4.BP2 Select verification measures |
| automotive-spice-aspice-v4-1-process-assessment-model::SYS.4.BP3 | SYS.4.BP3 Integrate the system elements and perform the integration verification |
| automotive-spice-aspice-v4-1-process-assessment-model::SYS.4.BP4 | SYS.4.BP4 Ensure consistency and establish bidirectional traceability |
| automotive-spice-aspice-v4-1-process-assessment-model::SYS.4.BP5 | SYS.4.BP5 Summarize and communicate the results |
| automotive-spice-aspice-v4-1-process-assessment-model::SYS.5.BP1 | SYS.5.BP1 Specify verification measures for the system verification |
| automotive-spice-aspice-v4-1-process-assessment-model::SYS.5.BP2 | SYS.5.BP2 Select verification measures |
| automotive-spice-aspice-v4-1-process-assessment-model::SYS.5.BP3 | SYS.5.BP3 Perform the verification of the integrated system |
| automotive-spice-aspice-v4-1-process-assessment-model::SYS.5.BP4 | SYS.5.BP4 Ensure consistency and establish bidirectional traceability |
| automotive-spice-aspice-v4-1-process-assessment-model::SYS.5.BP5 | SYS.5.BP5 Summarize and communicate the results |
Validation process group (VAL) – Automotive SPICE (ASPICE) v4.1 - Process Assessment Model
| Code | Title |
|---|---|
| automotive-spice-aspice-v4-1-process-assessment-model::VAL.1.BP1 | VAL.1.BP1 Specify validation measures for the product validation |
| automotive-spice-aspice-v4-1-process-assessment-model::VAL.1.BP2 | VAL.1.BP2 Select validation measures |
| automotive-spice-aspice-v4-1-process-assessment-model::VAL.1.BP3 | VAL.1.BP3 Perform the validation and evaluate the results |
| automotive-spice-aspice-v4-1-process-assessment-model::VAL.1.BP4 | VAL.1.BP4 Ensure consistency and establish bidirectional traceability |
| automotive-spice-aspice-v4-1-process-assessment-model::VAL.1.BP5 | VAL.1.BP5 Summarize and communicate the results |
Your Compliance Coverage
If you comply with Automotive SPICE (ASPICE) v4.1 - Process Assessment Model, you already cover:
ISO/IEC 23894:2023
2%
5 controls mapped
Compare →WHO Global Strategy on Digital Health 2020-2025
2%
4 controls mapped
Compare →NIST SP 800-171A Rev 3 - Assessing CUI Security Requirements
2%
4 controls mapped
Compare →+ 193 more: Annex 11 to EU GMP - Computerised Systems (2%), South Korea ISMS-P (2%)
See all 196 mapped frameworks ↓Maps to 196 other frameworks
Coverage is not the same as your position
This page shows what Automotive SPICE (ASPICE) v4.1 - Process Assessment Model overlaps with in general. Where your organisation actually stands, against the standard you are going for and the certifications you already hold, is a different question. Same graph and the same recorded refutations, scoped to you rather than to a pair.
The Compliance Position Diagnostic, $5,000 fixed, ten business daysWhat is Automotive SPICE (ASPICE) v4.1 - Process Assessment Model and who does it apply to?
Automotive SPICE (ASPICE) v4.1 - Process Assessment Model is a compliance framework from Global (VDA QMC; automotive OEMs and their suppliers, intacs assessment scheme) with 12 domains and 229 controls. Automotive SPICE is the VDA Quality Management Center's process reference and assessment model for automotive system, software, hardware and machine learning engineering, built on the ISO/IEC 33020 measurement framework and assessed by intacs certified assessors. Version 4.1 (released 24 August 2026) revises 4.0 (2023) by removing MLE.2 BP5 with editorial changes. The graph models the 195 base practices of the 32 processes across 11 process groups and the 34 generic practices of the nine process attributes that carry capability levels 1 to 5. It is used by organisations to establish and maintain compliance with industry standards and regulatory requirements.
What does Automotive SPICE (ASPICE) v4.1 - Process Assessment Model actually require?
Automotive SPICE (ASPICE) v4.1 - Process Assessment Model has 229 controls organised across 12 domains. The largest domains are Capability levels and process attributes (PA 1.1 to PA 5.2) – Automotive SPICE (ASPICE) v4.1 - Process Assessment Model (34 controls), Supporting process group (SUP) – Automotive SPICE (ASPICE) v4.1 - Process Assessment Model (34 controls), Software engineering process group (SWE) – Automotive SPICE (ASPICE) v4.1 - Process Assessment Model (33 controls). Each control defines specific requirements that organisations must implement to achieve compliance.
If I already comply with another framework, how much of Automotive SPICE (ASPICE) v4.1 - Process Assessment Model do I already cover?
Automotive SPICE (ASPICE) v4.1 - Process Assessment Model maps to 196 other compliance frameworks. The top mapping partners are ISO/IEC 23894:2023 (2% coverage), WHO Global Strategy on Digital Health 2020-2025 (2% coverage), NIST SP 800-171A Rev 3 - Assessing CUI Security Requirements (2% coverage). Use our comparison tool to explore control-level mappings between frameworks.
How do I implement Automotive SPICE (ASPICE) v4.1 - Process Assessment Model?
Start your Automotive SPICE (ASPICE) v4.1 - Process Assessment Model compliance journey by running a self-assessment on our platform to identify your current compliance posture. Our AI advisory can answer specific questions about Automotive SPICE (ASPICE) v4.1 - Process Assessment Model requirements, and cross-framework mapping helps you leverage existing controls from other frameworks you may already comply with. Create a free account to access all 229 controls and track your progress.
Start Your Compliance Journey
Create a free account to run self-assessments, get AI advisory, and track your compliance progress across 704 frameworks.
Get Started Free →Free forever — no credit card required