Isolated process summaries
A list of practices does not explain how work moves between roles, repositories and lifecycle decisions.
Technical guides
Connect process expectations to performed engineering work
These guides explain Automotive SPICE and related engineering topics through the artifacts, relationships, reviews and evidence that teams manage across a product lifecycle.
Explore this topic
Go deeper into technical guides
Continue with focused guidance for each capability, workflow or engineering context in this section.
Technical guideAutomotive SPICE 4.0 engineering guideUnderstand how process expectations connect to performed system and software engineering, support processes, evidence and human responsibility.Explore Technical guideAutomotive SPICE SYS process guideConnect stakeholder needs, system requirements, architecture, integration and qualification evidence across SYS.1 through SYS.5.Explore Technical guideAutomotive SPICE SWE process guideMaintain intent and verification continuity from software requirements through architecture, detailed design, implementation, integration and qualification.Explore Technical guideAutomotive SPICE capability levels guideDistinguish process outcomes and base practices from capability attributes, evidence and assessor judgment.Explore Technical guideAutomotive SPICE vs ISO 26262Understand the relationship between process capability and functional-safety lifecycle obligations without treating either framework as a substitute for the other.Explore Technical guideMachine-learning engineering under Automotive SPICEExplore how data, model, evaluation and change evidence can be connected to established engineering responsibility and lifecycle control.Explore
Why it matters
Process knowledge becomes useful when it changes execution
Teams need to connect framework language to authoritative inputs, expected outcomes, review responsibilities and maintained evidence.
Work products without context
Documents alone do not establish completeness, consistency, traceability or performed review.
Automation overreach
AI assistance must remain separate from assessor judgment, safety acceptance and accountable release decisions.
How to use the guides
Move from concept to programme-specific questions
Use each guide to understand the topic, inspect lifecycle relationships and define what must be verified in your own environment.
Clarify the scope
Identify the process purpose, terminology and boundary with adjacent engineering and support activities.
Map the lifecycle
Relate inputs and outcomes to artifacts, baselines, trace relationships and responsible roles.
Examine evidence
Ask what demonstrates that work was performed, reviewed, corrected and maintained through change.
Apply qualified judgment
Tailor the guidance to applicable standards, customer obligations and the programme assessment strategy.
The applicable source remains authoritative. Guidance supports understanding; licensed standards, agreed processes and qualified decisions govern the programme.
Execution outcomes
A practical reading path
Start broad, then move into the process or relationship most relevant to the current engineering problem.
Automotive SPICE 4.0
Build a foundation in process outcomes, performed engineering and connected evidence.
SYS and SWE processes
Follow intent from stakeholder needs through system and software realization and qualification.
Capability levels
Separate process performance from the attributes and evidence used to evaluate capability.
Safety and machine learning
Examine interfaces with ISO 26262 and the additional controls needed for data- and model-based development.
Control and evidence
Every guide links concepts to engineering evidence
The material focuses on performed work, relationships, review and change rather than treating a template or generated document as proof of process achievement.
Process purpose and expected outcomes
Authoritative inputs and work products
Upstream and downstream relationships
Review and approval responsibility
Change and configuration implications
Limits of automation and interpretation
Connected platform
Continue exploring KlugSpice
Move between the platform, engineering solution, industry and standard views without losing the engineering thread.
Questions teams ask
Frequently asked questions
Clear answers for engineering, quality, security and programme leaders.
Do these guides reproduce the Automotive SPICE standard?
No. They provide original explanatory guidance and do not replace the official process assessment model or other licensed material.
Can a guide determine process capability?
No. Capability assessment requires appropriate evidence and qualified assessor judgment in the relevant organizational and project context.
How should teams use AI with process guidance?
Use AI for bounded preparation and analysis with approved context, visible sources and human review. Do not delegate capability, safety or release decisions to the model.
Start with controlled scope
Apply the guidance to one real work package.
Choose a process relationship or evidence bottleneck that your engineers can evaluate against current practice.