search
ACQ.4
Supplier Monitoring
# PROCESS PURPOSE The purpose is to track and assess the performance of an external contract-based supplier company against agreed commitments. # PROCESS OUTCOMES
- O1 Joint activities, as agreed between the customer and the supplier, are performed.
- O2 All information, agreed upon for exchange, is communicated regularly between the customer and the supplier.
- O3 Performance of the supplier is monitored against the agreements.
- O4 Changes to the agreement, if needed, are negotiated between the customer and the supplier and documented in the agreement.
BP1
Agree on and maintain joint activities, joint interfaces, and information to be exchanged. (
O1, O2, O4 )

Linked Knowledge Nuggets:
arrow_forward "Establishing supplier interface"
arrow_forward "Establishing supplier interface"
BP2
Exchange all agreed information. (
O1, O2, O3 )
BP3
Review development work products with the supplier. (
O1, O3, O4 )
BP4
Review progress of the supplier. (
O1, O3, O4 )
intacs® Certified Automotive SPICE® Hardware Engineering
Sponsored
This official intacs® certified extension training introduces the hardware engineering processes in Automotive SPICE® PAM.
Click for more details!
BP5
Act to correct deviations. (
O3, O4 )
15-51
Analysis results (
O3 )
Used by these processes:
- ACQ.4 Supplier Monitoring
- HWE.1 Hardware Requirements Analysis
- HWE.2 Hardware Design
- MAN.5 Risk Management
- MAN.6 Measurement
- MLE.1 Machine Learning Requirements Analysis
- MLE.2 Machine Learning Architecture
- PIM.3 Process Improvement
- SWE.1 Software Requirements Analysis
- SWE.2 Software Architectural Design
- SYS.1 Requirements Elicitation
- SYS.2 System Requirements Analysis
- SYS.3 System Architectural Design
13-16
Change request (
O4 )
Used by these processes:
- ACQ.4 Supplier Monitoring
- MAN.3 Project Management
- PIM.3 Process Improvement
- SUP.10 Change Request Management
02-01
Commitment/agreement (
O1, O2, O3, O4 )
Used by these processes:
- ACQ.4 Supplier Monitoring
- PIM.3 Process Improvement
13-52
Communication evidence (
O1, O2, O3 )
Used by these processes:
- ACQ.4 Supplier Monitoring
- HWE.1 Hardware Requirements Analysis
- HWE.2 Hardware Design
- HWE.3 Verification against Hardware Design
- HWE.4 Verification against Hardware Requirements
- MAN.3 Project Management
- MLE.1 Machine Learning Requirements Analysis
- MLE.2 Machine Learning Architecture
- MLE.3 Machine Learning Training
- MLE.4 Machine Learning Model Testing
- PIM.3 Process Improvement
- REU.2 Management of Products for Reuse
- SUP.1 Quality Assurance
- SUP.11 Machine Learning Data Management
- SWE.1 Software Requirements Analysis
- SWE.2 Software Architectural Design
- SWE.3 Software Detailed Design and Unit Construction
- SWE.4 Software Unit Verification
- SWE.5 Software Component Verification and Integration Verification
- SWE.6 Software Verification
- SYS.1 Requirements Elicitation
- SYS.2 System Requirements Analysis
- SYS.3 System Architectural Design
- SYS.4 System Integration and Integration Verification
- SYS.5 System Verification
- VAL.1 Validation
- PA2.1 Performance Management
14-02
Corrective action (
O4 )
Used by these processes:
- ACQ.4 Supplier Monitoring
- MAN.3 Project Management
- MAN.5 Risk Management
- SUP.1 Quality Assurance
13-09
Meeting support evidence (
O1, O2 )
Used by these processes:
- ACQ.4 Supplier Monitoring
13-14
Progress status (
O2, O3 )
Used by these processes:
- ACQ.4 Supplier Monitoring
- PA2.1 Performance Management
13-19
Review evidence (
O2 )
Used by these processes:
- ACQ.4 Supplier Monitoring
- SUP.1 Quality Assurance
- PA2.2 Work Product Management