Automotive SPICE (ASPICE) v4.1: every control, and what you already have

318 controls 198 frameworks share controls with it Global (VDA QMC; automotive OEMs and their suppliers, intacs assessment scheme) verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

If you run	Shared controls
ISO/IEC 23894:2023	5	measure it →
Annex 11 to EU GMP	4	measure it →
NIST Cybersecurity Framework 2.0	4	measure it →
NIST SP 800-171A Rev 3	4	measure it →
South Korea ISMS-P	4	measure it →
South Korea Korea Internet Self-Governance Organisation (KISO) Code of Ethics	4	measure it →
WHO Global Strategy on Digital Health 2020-2025	4	measure it →
21 CFR Part 211	3	measure it →
CISA Cross-Sector Cybersecurity Performance Goals (CPG) 2.0	3	measure it →
French Sapin II Law (Law No. 2016-1691)	3	measure it →
IAEA Nuclear Security Series	3	measure it →
ICH Q10	3	measure it →

Every control

Code	Control	Also in
`ACQ.4`	Supplier Monitoring	73
`HWE.1`	Hardware Requirements Analysis	0
`HWE.2`	Hardware Design	0
`HWE.3`	Hardware Verification	0
`HWE.4`	Hardware Qualification Verification	0
`MAN.3`	Project Management	0
`MAN.5`	Risk Management	0
`MAN.6`	Measurement	1
`MLE.1`	Machine Learning Requirements Analysis	137
`MLE.2`	Machine Learning Architecture	11
`MLE.3`	Machine Learning Training	129
`MLE.4`	Machine Learning Model Testing	0
`SEC.1`	Cybersecurity Requirements Analysis	0
`SPL.2`	Product Release	0
`SUP.1`	Quality Assurance	0
`SUP.10`	Change Request Management	0
`SUP.11`	ML Data Management Support	8
`SUP.8`	Configuration Management	31
`SUP.9`	Problem Resolution Management	0
`SWE.1`	Software Requirements Analysis	0
`SWE.2`	Software Architectural Design	0
`SWE.3`	Software Detailed Design and Unit Construction	0
`SWE.4`	Software Unit Verification	0
`SWE.5`	Software Component Verification and Integration Verification	0
`SWE.6`	Software Verification	0
`SYS.1`	Requirements Elicitation	1
`SYS.2`	System Requirements Analysis	0
`SYS.3`	System Architectural Design	0
`SYS.4`	System Integration and Integration Verification	0
`SYS.5`	System Verification	0
`VAL.1`	System Validation	0
`ACQ.4.BP1`	ACQ.4.BP1 Agree on and maintain joint activities, joint interfaces, and information to be exchanged	0
`ACQ.4.BP2`	ACQ.4.BP2 Exchange all agreed information	0
`ACQ.4.BP3`	ACQ.4.BP3 Review development work products with the supplier	0
`ACQ.4.BP4`	ACQ.4.BP4 Review progress of the supplier	0
`ACQ.4.BP5`	ACQ.4.BP5 Act to correct the deviations	0
`COMPANIONS`	The companion documents held: Automotive SPICE Guidelines 2.0, Cybersecurity PAM 2.0, Potential Analysis, PAM 3.1 and the intacs scheme	0
`CONCEPTS`	Annex C key concepts: the plug-in concept, ML engineering integration, and traceability and consistency	0
`FRAMEWORK`	The measurement framework: six capability levels, nine process attributes, the NPLF rating scale and the capability level model	0
`GP 1.1.1`	GP 1.1.1 Achieve the process outcomes Achieve the intent of the base practices	0
`GP 2.1.1`	GP 2.1.1 Identify the objectives and define a strategy for the performance of the process	0
`GP 2.1.2`	GP 2.1.2 Plan the performance of the process	0
`GP 2.1.3`	GP 2.1.3 Determine the resource needs	0
`GP 2.1.4`	GP 2.1.4 Identify and make available the resources	0
`GP 2.1.5`	GP 2.1.5 Monitor and adjust the performance of the process	0
`GP 2.1.6`	GP 2.1.6 Manage the interfaces between involved parties	0
`GP 2.2.1`	GP 2.2.1 Define the requirements for the work products	0
`GP 2.2.2`	GP 2.2.2 Define the requirements for storage and control of the work products	0
`GP 2.2.3`	GP 2.2.3 Identify, store and control the work products	0
`GP 2.2.4`	GP 2.2.4 Review and adjust work products	0
`GP 3.1.1`	GP 3.1.1 Establish and maintain the standard process	0
`GP 3.1.2`	GP 3.1.2 Determine the required competencies	0
`GP 3.1.3`	GP 3.1.3 Determine the required resources	0
`GP 3.1.4`	GP 3.1.4 Determine suitable methods to monitor the standard process	0
`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	0
`GP 3.2.2`	GP 3.2.2 Ensure the required competencies for the defined roles	0
`GP 3.2.3`	GP 3.2.3 Ensure the required resources to support the performance of the defined process	0
`GP 3.2.4`	GP 3.2.4 Monitor the performance of the defined process	0
`GP 4.1.1`	GP 4.1.1 Identify the business goals	0
`GP 4.1.2`	GP 4.1.2 Establish the process information needs	0
`GP 4.1.3`	GP 4.1.3 Identify the measurable relationships between process elements	0
`GP 4.1.4`	GP 4.1.4 Derive a process measurement approach and select the analysis techniques	0
`GP 4.1.5`	GP 4.1.5 Establish quantitative control limits	0
`GP 4.1.6`	GP 4.1.6 Collect product and process measurement results through performing the defined process	0
`GP 4.2.1`	GP 4.2.1 Identify the variations in process performance	0
`GP 4.2.2`	GP 4.2.2 Identify the causes of variation	0
`GP 4.2.3`	GP 4.2.3 Identify and implement corrective actions to address assignable causes	0
`GP 5.1.1`	GP 5.1.1 Define the process innovation objectives for the process that support the relevant business goals	0
`GP 5.1.2`	GP 5.1.2 Analyze the quantitative data of the process	0
`GP 5.1.3`	GP 5.1.3 Identify the innovation opportunities	0
`GP 5.2.1`	GP 5.2.1 Define and assess the impact of the proposed changes	0
`GP 5.2.2`	GP 5.2.2 Implement the agreed process changes	0
`GP 5.2.3`	GP 5.2.3 Evaluate the effectiveness of the process changes	0
`GROUP-ACQ`	Acquisition process group (ACQ)	0
`GROUP-HWE`	Hardware engineering process group (HWE)	0
`GROUP-MAN`	Management process group (MAN)	0
`GROUP-MLE`	Machine learning engineering process group (MLE)	0
`GROUP-PIM`	Process improvement process group (PIM)	0
`GROUP-REU`	Reuse process group (REU)	0
`GROUP-SPL`	Supply process group (SPL)	0
`GROUP-SUP`	Supporting process group (SUP)	0
`GROUP-SWE`	Software engineering process group (SWE)	0
`GROUP-SYS`	System engineering process group (SYS)	0
`GROUP-VAL`	Validation process group (VAL)	0
`HWE.1.BP1`	HWE.1.BP1 Specify the hardware requirements	0
`HWE.1.BP2`	HWE.1.BP2 Structure the hardware requirements	0
`HWE.1.BP3`	HWE.1.BP3 Analyze the hardware requirements	0
`HWE.1.BP4`	HWE.1.BP4 Analyze the impact on the operating environment	0
`HWE.1.BP5`	HWE.1.BP5 Ensure consistency and establish bidirectional traceability	0
`HWE.1.BP6`	HWE.1.BP6 Communicate the agreed hardware requirements and the impact on the operating environment	0
`HWE.2.BP1`	HWE.2.BP1 Specify the hardware architecture	0
`HWE.2.BP2`	HWE.2.BP2 Specify the hardware detailed design	0
`HWE.2.BP3`	HWE.2.BP3 Specify the dynamic aspects of the hardware architecture and the hardware detailed design	0
`HWE.2.BP4`	HWE.2.BP4 Analyze the hardware architecture and the hardware detailed design	0
`HWE.2.BP5`	HWE.2.BP5 Ensure consistency and establish bidirectional traceability	0
`HWE.2.BP6`	HWE.2.BP6 Communicate the agreed hardware architecture and hardware detailed design	0
`HWE.3.BP1`	HWE.3.BP1 Specify verification measures for the verification against the hardware design	0
`HWE.3.BP2`	HWE.3.BP2 Ensure the use of compliant samples	0
`HWE.3.BP3`	HWE.3.BP3 Select verification measures	0
`HWE.3.BP4`	HWE.3.BP4 Verify against the hardware design	0
`HWE.3.BP5`	HWE.3.BP5 Ensure consistency and establish bidirectional traceability	0
`HWE.3.BP6`	HWE.3.BP6 Summarize and communicate the results	0
`HWE.4.BP1`	HWE.4.BP1 Specify verification measures for the verification against the hardware requirements	0
`HWE.4.BP2`	HWE.4.BP2 Ensure the use of compliant samples	0
`HWE.4.BP3`	HWE.4.BP3 Select verification measures	0
`HWE.4.BP4`	HWE.4.BP4 Verify the compliant hardware samples	0
`HWE.4.BP5`	HWE.4.BP5 Ensure consistency and establish bidirectional traceability	0
`HWE.4.BP6`	HWE.4.BP6 Summarize and communicate the results	0
`INFO-ITEMS`	Annex B: the information item characteristics behind the output information items	0
`LEVELS`	Capability levels 1 to 5 and their process attributes	0
`MAN.3.BP1`	MAN.3.BP1 Define the scope of work	0
`MAN.3.BP10`	MAN.3.BP10 Review and report the progress of the project	0
`MAN.3.BP2`	MAN.3.BP2 Define the project lifecycle	0
`MAN.3.BP3`	MAN.3.BP3 Evaluate the feasibility of the project	0
`MAN.3.BP4`	MAN.3.BP4 Define and monitor the work packages	0
`MAN.3.BP5`	MAN.3.BP5 Define and monitor the project estimates and resources	0
`MAN.3.BP6`	MAN.3.BP6 Define and monitor the required skills, knowledge, and experience	0
`MAN.3.BP7`	MAN.3.BP7 Define and monitor the project interfaces and agreed commitments	0
`MAN.3.BP8`	MAN.3.BP8 Define and monitor the project schedule	0
`MAN.3.BP9`	MAN.3.BP9 Ensure consistency	0
`MAN.5.BP1`	MAN.5.BP1 Identify sources of risks	0
`MAN.5.BP2`	MAN.5.BP2 Identify the potential undesirable events	0
`MAN.5.BP3`	MAN.5.BP3 Determine the risks	0
`MAN.5.BP4`	MAN.5.BP4 Define risk treatment options	0
`MAN.5.BP5`	MAN.5.BP5 Define and perform risk treatment activities	0
`MAN.5.BP6`	MAN.5.BP6 Monitor the risks	0
`MAN.5.BP7`	MAN.5.BP7 Take corrective action	0
`MAN.6.BP1`	MAN.6.BP1 Identify the information needs	0
`MAN.6.BP2`	MAN.6.BP2 Specify metrics	0
`MAN.6.BP3`	MAN.6.BP3 Collect and store the metrics	0
`MAN.6.BP4`	MAN.6.BP4 Analyze the collected metrics	0
`MAN.6.BP5`	MAN.6.BP5 Communicate the analysis results	0
`MAN.6.BP6`	MAN.6.BP6 Use metrics for decision-making	0
`MLE.1.BP1`	MLE.1.BP1 Specify the ML requirements	0
`MLE.1.BP2`	MLE.1.BP2 Structure the ML requirements	0
`MLE.1.BP3`	MLE.1.BP3 Analyze the ML requirements	0
`MLE.1.BP4`	MLE.1.BP4 Analyze the impact on the ML operating environment	0
`MLE.1.BP5`	MLE.1.BP5 Ensure consistency and establish bidirectional traceability	0
`MLE.1.BP6`	MLE.1.BP6 Communicate the agreed ML requirements and the impact on the operating environment	0
`MLE.2.BP1`	MLE.2.BP1 Develop the ML architecture	0
`MLE.2.BP2`	MLE.2.BP2 Determine the hyperparameter ranges and the initial values	0
`MLE.2.BP3`	MLE.2.BP3 Analyze the ML architectural elements	0
`MLE.2.BP4`	MLE.2.BP4 Define the interfaces of the ML architectural elements	0
`MLE.2.BP5`	MLE.2.BP5 Ensure consistency and establish bidirectional traceability	0
`MLE.2.BP6`	MLE.2.BP6 Communicate the agreed ML architecture	0
`MLE.3.BP1`	MLE.3.BP1 Specify the ML training and validation approach	0
`MLE.3.BP2`	MLE.3.BP2 Create the ML training and validation data set	0
`MLE.3.BP3`	MLE.3.BP3 Create and optimize the ML model	0
`MLE.3.BP4`	MLE.3.BP4 Ensure consistency and establish bidirectional traceability	0
`MLE.3.BP5`	MLE.3.BP5 Summarize and communicate the agreed trained ML model	0
`MLE.4.BP1`	MLE.4.BP1 Specify an ML test approach	0
`MLE.4.BP2`	MLE.4.BP2 Create the ML test data set	0
`MLE.4.BP3`	MLE.4.BP3 Test the trained ML model	0
`MLE.4.BP4`	MLE.4.BP4 Derive the deployed ML model	0
`MLE.4.BP5`	MLE.4.BP5 Test the deployed ML model	0
`MLE.4.BP6`	MLE.4.BP6 Ensure consistency and establish bidirectional traceability	0
`MLE.4.BP7`	MLE.4.BP7 Summarize and communicate the results	0
`MODEL`	Automotive SPICE PAM/PRM 4.1: what it is, its history, the 4.0 to 4.1 delta, and what is held	0
`PA-PA1.1`	PA 1.1 Process performance process attribute (capability level 1, Performed)	0
`PA-PA2.1`	PA 2.1 Process performance management process attribute (capability level 2, Managed)	0
`PA-PA2.2`	PA 2.2 Work product management process attribute (capability level 2, Managed)	0
`PA-PA3.1`	PA 3.1 Process definition process attribute (capability level 3, Established)	0
`PA-PA3.2`	PA 3.2 Process deployment process attribute (capability level 3, Established)	0
`PA-PA4.1`	PA 4.1 Quantitative analysis process attribute (capability level 4, Predictable)	0
`PA-PA4.2`	PA 4.2 Quantitative control process attribute (capability level 4, Predictable)	0
`PA-PA5.1`	PA 5.1 Process innovation process attribute (capability level 5, Innovating)	0
`PA-PA5.2`	PA 5.2 Process innovation implementation process attribute (capability level 5, Innovating)	0
`PIM.3.BP1`	PIM.3.BP1 Establish a commitment	0
`PIM.3.BP2`	PIM.3.BP2 Identify improvement measures	0
`PIM.3.BP3`	PIM.3.BP3 Establish process improvement goals	0
`PIM.3.BP4`	PIM.3.BP4 Prioritize the improvements	0
`PIM.3.BP5`	PIM.3.BP5 Define process improvement measures	0
`PIM.3.BP6`	PIM.3.BP6 Implement the process improvement measures	0
`PIM.3.BP7`	PIM.3.BP7 Confirm the process improvements	0
`PIM.3.BP8`	PIM.3.BP8 Communicate the results of the improvements	0
`PROC-ACQ.4`	ACQ.4 Supplier Monitoring	0
`PROC-HWE.1`	HWE.1 Hardware Requirements Analysis	0
`PROC-HWE.2`	HWE.2 Hardware Design	0
`PROC-HWE.3`	HWE.3 Verification against Hardware Design	0
`PROC-HWE.4`	HWE.4 Verification against Hardware Requirements	0
`PROC-MAN.3`	MAN.3 Project Management	0
`PROC-MAN.5`	MAN.5 Risk Management	0
`PROC-MAN.6`	MAN.6 Measurement	0
`PROC-MLE.1`	MLE.1 Machine Learning Requirements Analysis	0
`PROC-MLE.2`	MLE.2 Machine Learning Architecture	0
`PROC-MLE.3`	MLE.3 Machine Learning Training	0
`PROC-MLE.4`	MLE.4 Machine Learning Model Testing	0
`PROC-PIM.3`	PIM.3 Process Improvement	0
`PROC-REU.2`	REU.2 Reuse of Products	0
`PROC-SPL.2`	SPL.2 Product Release	0
`PROC-SUP.1`	SUP.1 Quality Assurance	0
`PROC-SUP.10`	SUP.10 Change Request Management	0
`PROC-SUP.11`	SUP.11 Machine Learning Data Management	0
`PROC-SUP.8`	SUP.8 Configuration Management	0
`PROC-SUP.9`	SUP.9 Problem Resolution Management	0
`PROC-SWE.1`	SWE.1 Software Requirements Analysis	0
`PROC-SWE.2`	SWE.2 Software Architectural Design	0
`PROC-SWE.3`	SWE.3 Software Detailed Design and Unit Construction	0
`PROC-SWE.4`	SWE.4 Software Unit Verification	0
`PROC-SWE.5`	SWE.5 Software Component Verification and Integration Verification	0
`PROC-SWE.6`	SWE.6 Software Verification	0
`PROC-SYS.1`	SYS.1 Requirements Elicitation	0
`PROC-SYS.2`	SYS.2 System Requirements Analysis	0
`PROC-SYS.3`	SYS.3 System Architectural Design	0
`PROC-SYS.4`	SYS.4 System Integration and Integration Verification	0
`PROC-SYS.5`	SYS.5 System Verification	0
`PROC-VAL.1`	VAL.1 Validation	0
`REU.2.BP1`	REU.2.BP1 Select products for reuse	0
`REU.2.BP2`	REU.2.BP2 Analyze the reuse capability of the products	0
`REU.2.BP3`	REU.2.BP3 Define the limitations for reuse	0
`REU.2.BP4`	REU.2.BP4 Ensure the qualification of the products for reuse	0
`REU.2.BP5`	REU.2.BP5 Provide the products for reuse	0
`REU.2.BP6`	REU.2.BP6 Communicate information about the effectiveness of the reuse activities	0
`SPL.2.BP1`	SPL.2.BP1 Define and agree the functional content of the releases	0
`SPL.2.BP2`	SPL.2.BP2 Define the release package	0
`SPL.2.BP3`	SPL.2.BP3 Ensure a unique identification of each release	0
`SPL.2.BP4`	SPL.2.BP4 Build the release from items under configuration control	0
`SPL.2.BP5`	SPL.2.BP5 Ensure the release approval before the delivery	0
`SPL.2.BP6`	SPL.2.BP6 Provide a release note	0
`SPL.2.BP7`	SPL.2.BP7 Communicate the type, service level and duration of support for each release	0
`SPL.2.BP8`	SPL.2.BP8 Deliver the release package to the intended customer	0
`SUP.1.BP1`	SUP.1.BP1 Ensure independence of quality assurance	0
`SUP.1.BP2`	SUP.1.BP2 Define the criteria for quality assurance	0
`SUP.1.BP3`	SUP.1.BP3 Assure quality of the work products	0
`SUP.1.BP4`	SUP.1.BP4 Assure quality of the process activities	0
`SUP.1.BP5`	SUP.1.BP5 Summarize and communicate quality assurance activities and results	0
`SUP.1.BP6`	SUP.1.BP6 Ensure the resolution of non-conformances	0
`SUP.1.BP7`	SUP.1.BP7 Escalate non-conformances	0
`SUP.10.BP1`	SUP.10.BP1 Identify and record the change requests	0
`SUP.10.BP2`	SUP.10.BP2 Analyze and assess the change requests	0
`SUP.10.BP3`	SUP.10.BP3 Approve the change requests before implementation	0
`SUP.10.BP4`	SUP.10.BP4 Establish bidirectional traceability	0
`SUP.10.BP5`	SUP.10.BP5 Confirm the implementation of the change requests	0
`SUP.10.BP6`	SUP.10.BP6 Track the change requests to closure	0
`SUP.11.BP1`	SUP.11.BP1 Establish an ML data management system	0
`SUP.11.BP2`	SUP.11.BP2 Develop an ML data quality approach	0
`SUP.11.BP3`	SUP.11.BP3 Collect the ML data	0
`SUP.11.BP4`	SUP.11.BP4 Process the ML data	0
`SUP.11.BP5`	SUP.11.BP5 Assure the quality of the ML data	0
`SUP.11.BP6`	SUP.11.BP6 Communicate the agreed processed ML data	0
`SUP.8.BP1`	SUP.8.BP1 Identify the configuration items	0
`SUP.8.BP2`	SUP.8.BP2 Define the configuration item properties	0
`SUP.8.BP3`	SUP.8.BP3 Establish the configuration management	0
`SUP.8.BP4`	SUP.8.BP4 Control the modifications	0
`SUP.8.BP5`	SUP.8.BP5 Establish baselines	0
`SUP.8.BP6`	SUP.8.BP6 Summarize and communicate the configuration status	0
`SUP.8.BP7`	SUP.8.BP7 Ensure completeness and consistency	0
`SUP.8.BP8`	SUP.8.BP8 Verify the availability of backup and recovery mechanisms	0
`SUP.9.BP1`	SUP.9.BP1 Identify and record the problems	0
`SUP.9.BP2`	SUP.9.BP2 Determine the causes and the impacts of the problems	0
`SUP.9.BP3`	SUP.9.BP3 Authorize urgent resolution actions	0
`SUP.9.BP4`	SUP.9.BP4 Raise alert notifications	0
`SUP.9.BP5`	SUP.9.BP5 Initiate problem resolution	0
`SUP.9.BP6`	SUP.9.BP6 Track the problems to closure	0
`SUP.9.BP7`	SUP.9.BP7 Report the status of problem resolution activities	0
`SWE.1.BP1`	SWE.1.BP1 Specify the software requirements	0
`SWE.1.BP2`	SWE.1.BP2 Structure the software requirements	0
`SWE.1.BP3`	SWE.1.BP3 Analyze the software requirements	0
`SWE.1.BP4`	SWE.1.BP4 Analyze the impact on the operating environment	0
`SWE.1.BP5`	SWE.1.BP5 Ensure consistency and establish bidirectional traceability	0
`SWE.1.BP6`	SWE.1.BP6 Communicate the agreed software requirements and the impact on the operating environment	0
`SWE.2.BP1`	SWE.2.BP1 Specify the static aspects of the software architecture	0
`SWE.2.BP2`	SWE.2.BP2 Specify the dynamic aspects of the software architecture	0
`SWE.2.BP3`	SWE.2.BP3 Analyze the software architecture	0
`SWE.2.BP4`	SWE.2.BP4 Ensure consistency and establish bidirectional traceability	0
`SWE.2.BP5`	SWE.2.BP5 Communicate the agreed software architecture	0
`SWE.3.BP1`	SWE.3.BP1 Specify the static aspects of the detailed design	0
`SWE.3.BP2`	SWE.3.BP2 Specify the dynamic aspects of the detailed design	0
`SWE.3.BP3`	SWE.3.BP3 Develop the software units	0
`SWE.3.BP4`	SWE.3.BP4 Ensure consistency and establish bidirectional traceability	0
`SWE.3.BP5`	SWE.3.BP5 Communicate the agreed software detailed design and the developed software units	0
`SWE.4.BP1`	SWE.4.BP1 Specify software unit verification measures	0
`SWE.4.BP2`	SWE.4.BP2 Select software unit verification measures	0
`SWE.4.BP3`	SWE.4.BP3 Verify the software units	0
`SWE.4.BP4`	SWE.4.BP4 Ensure consistency and establish bidirectional traceability	0
`SWE.4.BP5`	SWE.4.BP5 Summarize and communicate the results	0
`SWE.5.BP1`	SWE.5.BP1 Specify software integration verification measures	0
`SWE.5.BP2`	SWE.5.BP2 Specify verification measures for verifying the software component behavior	0
`SWE.5.BP3`	SWE.5.BP3 Select verification measures	0
`SWE.5.BP4`	SWE.5.BP4 Integrate the software elements and perform the integration verification	0
`SWE.5.BP5`	SWE.5.BP5 Perform the software component verification	0
`SWE.5.BP6`	SWE.5.BP6 Ensure consistency and establish bidirectional traceability	0
`SWE.5.BP7`	SWE.5.BP7 Summarize and communicate the results	0
`SWE.6.BP1`	SWE.6.BP1 Specify verification measures for the software verification	0
`SWE.6.BP2`	SWE.6.BP2 Select verification measures	0
`SWE.6.BP3`	SWE.6.BP3 Verify the integrated software	0
`SWE.6.BP4`	SWE.6.BP4 Ensure consistency and establish bidirectional traceability	0
`SWE.6.BP5`	SWE.6.BP5 Summarize and communicate the results	0
`SYS.1.BP1`	SYS.1.BP1 Identify stakeholders and obtain their expectations and requests	0
`SYS.1.BP2`	SYS.1.BP2 Agree on the requirements	0
`SYS.1.BP3`	SYS.1.BP3 Analyze the stakeholder requirements changes	0
`SYS.1.BP4`	SYS.1.BP4 Communicate the requirements’ status	0
`SYS.2.BP1`	SYS.2.BP1 Specify the system requirements	0
`SYS.2.BP2`	SYS.2.BP2 Structure the system requirements	0
`SYS.2.BP3`	SYS.2.BP3 Analyze the system requirements	0
`SYS.2.BP4`	SYS.2.BP4 Analyze the impact on the system context	0
`SYS.2.BP5`	SYS.2.BP5 Ensure consistency and establish bidirectional traceability	0
`SYS.2.BP6`	SYS.2.BP6 Communicate the agreed system requirements and the impact on the system context	0
`SYS.3.BP1`	SYS.3.BP1 Specify the static aspects of the system architecture	0
`SYS.3.BP2`	SYS.3.BP2 Specify the dynamic aspects of the system architecture	0
`SYS.3.BP3`	SYS.3.BP3 Analyze the system architecture	0
`SYS.3.BP4`	SYS.3.BP4 Ensure consistency and establish bidirectional traceability	0
`SYS.3.BP5`	SYS.3.BP5 Communicate the agreed system architecture	0
`SYS.4.BP1`	SYS.4.BP1 Specify verification measures for the system integration	0
`SYS.4.BP2`	SYS.4.BP2 Select verification measures	0
`SYS.4.BP3`	SYS.4.BP3 Integrate the system elements and perform the integration verification	0
`SYS.4.BP4`	SYS.4.BP4 Ensure consistency and establish bidirectional traceability	0
`SYS.4.BP5`	SYS.4.BP5 Summarize and communicate the results	0
`SYS.5.BP1`	SYS.5.BP1 Specify verification measures for the system verification	0
`SYS.5.BP2`	SYS.5.BP2 Select verification measures	0
`SYS.5.BP3`	SYS.5.BP3 Perform the verification of the integrated system	0
`SYS.5.BP4`	SYS.5.BP4 Ensure consistency and establish bidirectional traceability	0
`SYS.5.BP5`	SYS.5.BP5 Summarize and communicate the results	0
`VAL.1.BP1`	VAL.1.BP1 Specify validation measures for the product validation	0
`VAL.1.BP2`	VAL.1.BP2 Select validation measures	0
`VAL.1.BP3`	VAL.1.BP3 Perform the validation and evaluate the results	0
`VAL.1.BP4`	VAL.1.BP4 Ensure consistency and establish bidirectional traceability	0
`VAL.1.BP5`	VAL.1.BP5 Summarize and communicate the results	0

Tell me when Automotive SPICE (ASPICE) v4.1 files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What an auditor will ask you to produce

The artefacts named on the failure modes this framework speaks to.

Annual BIPA audit report
Findings register with owners
Management review minutes
Corrective action closure evidence
Internal audit charter and plan
External audit reports

How programmes fail on this

Failure modes named by this framework and others. Each opens the full record.

Findings not tracked to closure named by 3 frameworks

What this page is

A control-level reference for Automotive SPICE (ASPICE) v4.1, drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition