Repository navigation
Automotive SPICE process capability
Standards tour · stop 18 of 20 · ← UL 4600 · Machinery Regulation →
Six capability levels as a staircase, each built on the one below; each level adds process attributes, rated not, partly, largely or fully achieved. Generated by tour_figures.py; it explains the standard's idea and claims nothing about the arm.
In one sentence. Automotive SPICE is a model for rating how capable a project's processes are, from performed to innovating; the record uses it to rate its own processes because machinery has no such model.
Automotive SPICE, version 4.0, a process assessment model from the automotive industry. It defines processes (management, system, software, hardware, machine learning, support and others) and rates each on six capability levels.
- CL0 Incomplete: the process does not achieve its purpose.
- CL1 Performed: its outcomes are achieved.
- CL2 Managed: it is planned and monitored, and its work products are controlled.
- CL3 Established: a defined standard process is used.
- CL4 Predictable: it is measured and controlled in numbers.
- CL5 Innovating: it is improved continuously.
Each level adds process attributes, each rated N, P, L or F: not, partly, largely or fully achieved.
The concept-phase package found the basic quality records missing: design reviews, nonconformance, corrective action (GAP-32). A capability model makes the gap measurable and gives each process a target.
| What the record takes | Where |
|---|---|
| A self-assessment baseline per process, with a target per gate: CL2 for management, support, system and software, CL1 for hardware and machine learning | Process capability baseline, WP-M-12 |
| The ASPICE column of the work product register | WP-M-00 |
An assessment: the baseline is a self-assessment, not one by a qualified assessor.
- Capability level (CL): 0 to 5.
- Process attribute (PA): a measurable property of a process at a given level.
- N, P, L, F: not, partly, largely, fully achieved.
No standard is held by the project, so every clause number on this page is to be checked against a licensed copy. The lead decided to buy them only when an assessor is engaged (DQ-011). The record uses the model's process and capability definitions as a whole.
Standards tour · stop 18 of 20 · ← UL 4600 · Machinery Regulation →
Mirrored from wiki/ on main at 832f97b, 2026-11-01. Pages are reviewed by pull request; the wiki is not edited in place. This wiki explains and links; safety claims and evidence live in the assurance record.
reBot-DevArm assurance wiki
- Home
- Processes
- Process maps
- Standards at a glance
- How we use each standard
- Standards tour
- Roadmap and status
- How the repository is organized
- How decisions are made
- Glossary
- Reading the safety case
- Hazard scenes
- For the assessor
- Reference arm
- Contributor guide
- Reporting a safety concern
- Session log
- FAQ
The standards tour
- Start here
- ISO 12100
- ISO 10218-1 and -2
- ISO 13849-1 and -2
- IEC 62061
- IEC 61508
- EN 60204-1
- ISO 13850
- ISO 13854
- ISO 13857
- ISO 13855
- ISO/TS 15066
- IEC 60812
- IEC 61025
- ISO 21448
- IEC 62443
- ISO/IEC TR 5469
- UL 4600
- Automotive SPICE
- Machinery Regulation
- AI Act
Repository