Connect approved context
Use relevant artifacts, relationships, standards, regulatory requirements, organisational guidelines and approved decisions.
ASPICE automation software
Automate Automotive SPICE engineering with governed AI.
KlugSpice uses governed, specialist AI agents to assist engineering teams across Automotive SPICE process areas.
Governed workflow
From approved engineering context to controlled outcomes
Each workflow is configured with approved inputs, expected outcomes, responsible engineering roles and review conditions.
Prepare an outcome
A specialist agent prepares a work-product proposal, quality finding, trace relationship, impact analysis or readiness observation.
Review the evidence
The responsible engineer evaluates sources, assumptions, findings, relationships and technical rationale.
Approve the decision
An authorized engineer accepts, revises, rejects or escalates the proposal.
Synchronize outcomes
Where supported and configured, approved outcomes return with provenance and review history preserved.
Engineering authority remains human. KlugSpice prepares and analyses reviewable outcomes; authorized engineers decide what is accepted, approved and released.
Engineering activities
Which Automotive SPICE activities can KlugSpice support?
KlugSpice assists teams across Automotive SPICE process areas by preparing work products, analysing engineering relationships, identifying potential gaps and maintaining reviewable evidence.
Requirements engineering
Prepare requirement candidates and analyse ambiguity, inconsistency, duplication, completeness, feasibility, verifiability and missing parameters.
Architecture and design
Prepare system and software architecture proposals, allocations, interfaces, design elements and supporting rationale.
Verification and validation
Prepare verification criteria, test scenarios, test specifications, procedures and coverage observations.
Bidirectional traceability
Analyse relationships, propose missing links and maintain reviewable traceability across engineering work products.
Impact and change analysis
Identify affected requirements, architecture, interfaces, components, tests, evidence, baselines and responsible roles.
Assessment readiness
Surface potential process-area gaps, missing evidence, incomplete reviews, traceability weaknesses and baseline issues.
Engineering authority
Which decisions remain with engineers and assessors?
KlugSpice prepares information, analyses engineering context and proposes reviewable outcomes. It does not replace the roles responsible for engineering decisions, quality assurance, process governance or assessment.
- Technical correctness and work-product completeness
- Acceptance of requirements and design decisions
- Approval of traceability relationships
- Acceptance of verification criteria and results
- Configuration, baseline and release approval
Integration ecosystem
How does KlugSpice integrate with existing engineering tools?
KlugSpice can be integrated with the requirements, ALM, PLM, test, code and delivery systems already used by an organisation. It does not require those systems to be replaced. Integration scope depends on the customer toolchain, available interfaces, permissions, required artifact types and the workflow being implemented.
Polarion
Requirements, lifecycle, review, test and verification context.
IBM DOORS Next
Requirements, artifact relationships and lifecycle context.
Codebeamer
Requirements, ALM, review and engineering workflow context.
Jira
Planning, issues, defects, changes and workflow information.
Azure DevOps
Work items, code, builds, tests and delivery information.
Teamcenter
Product lifecycle, configuration and controlled engineering context.
Product and company names identify potential integration targets. Their inclusion does not imply a commercial partnership, endorsement or certified connector unless explicitly stated.
Process coverage
Where can KlugSpice contribute across Automotive SPICE?
The exact contribution depends on the organisation’s defined processes, performed engineering work, project scope and configured KlugSpice workflows.
| Process context | Potential KlugSpice contribution |
|---|---|
| Requirements-related processes | Requirement candidates, quality findings, stakeholder, system and software context, derivation and allocation relationships, reviews and lifecycle traceability. |
| Architecture and design processes | Architecture and design proposals, functional and technical allocations, interface information, design rationale and review evidence. |
| Verification and validation processes | Verification criteria, test scenarios and specifications, coverage analysis, requirement-to-test relationships, findings and result evidence. |
| Supporting processes | Quality findings, review status, configuration and baseline context, change requests, impact analysis, defect relationships and evidence preparation. |
| Management and organisational processes | Project decision context, responsibility and review information, readiness reporting, organisational guidelines, templates and reusable engineering knowledge. |
Scope note: This mapping identifies where KlugSpice may contribute to engineering activities and objective evidence. It does not demonstrate complete process coverage, achievement of process outcomes or an Automotive SPICE capability-level rating.
Approved context
What project context does KlugSpice use?
KlugSpice uses the approved engineering, process and compliance context relevant to the configured workflow.
Project artifacts
Requirements, architecture, interfaces, design information, test specifications, results, defects, change requests and supporting documents.
Artifact relationships
Upstream and downstream traceability, allocations, dependencies, verification relationships and existing lifecycle links.
Standards and regulatory requirements
Applicable Automotive SPICE material, safety and cybersecurity standards, regulatory requirements and customer-specific obligations.
Organisational guidelines
Internal processes, templates, quality criteria, naming conventions, review procedures, definition-of-done criteria and approval rules.
Project decisions and baselines
Approved decisions, assumptions, versions, releases, configuration status, baselines and previous review outcomes.
Workflow controls
Expected outcome, responsible engineering roles, review conditions, approval authority and synchronization rules.
Engineering outcomes
What Automotive SPICE outcomes does KlugSpice prepare?
KlugSpice prepares reviewable engineering work products, analyses lifecycle relationships and maintains the information required to evaluate coverage, consistency, change impact and assessment readiness.
Engineering work-product proposals
Requirements, architecture descriptions, interfaces, verification criteria, test specifications and other configured work products.
Requirements quality findings
Potential ambiguity, inconsistency, duplication, incompleteness, unverifiable language, missing parameters and conflicts.
Bidirectional traceability
Proposed and reviewed relationships across stakeholder requirements, system requirements, architecture, software requirements, design and verification.
Coverage and gap analysis
Work products without sufficient upstream or downstream relationships and verification items with unclear coverage.
Impact and change analysis
Affected requirements, architecture, interfaces, components, tests, evidence, baselines and responsible roles.
Verification consistency
Analysis of verification criteria and whether planned or completed verification work provides the intended coverage.
Review and baseline status
Outstanding findings, review completion, approval state, artifact versions, configuration status and baseline readiness.
Objective-evidence preparation
Connections between performed engineering activities, approved work products, traceability, reviews, decisions and configuration status.
Assessment-readiness findings
Potential process-area gaps, missing evidence, incomplete reviews, traceability weaknesses and baseline blockers.
Decision and provenance history
Source artifacts, versions, assumptions, analysis results, reviewer identity, approval decisions and rationale.
Platform role
Does KlugSpice replace an ALM platform?
No. KlugSpice coordinates governed engineering execution across existing requirements, ALM, PLM, test, code and delivery systems. These systems continue to hold authoritative project information.
For supported workflows where synchronization is enabled, approved outcomes can be returned to the appropriate controlled system.
Assessment boundary
Does KlugSpice certify Automotive SPICE compliance?
No. KlugSpice supports engineering execution and assessment preparation by connecting work products, traceability, reviews, baselines, decisions and objective evidence.
A qualified assessor remains responsible for determining process-attribute ratings and the resulting capability level.
Purpose-built execution
How is KlugSpice different from a general-purpose AI assistant?
A general-purpose AI assistant can generate text from a prompt. KlugSpice is designed to support governed engineering execution using approved project context, configured workflows, specialist agents, lifecycle relationships and defined review authority.
The objective is not to generate more content. It is to prepare engineering outcomes that can be reviewed, understood, traced and controlled within established processes.
- Approved engineering context
- Process-specific tasks
- Artifact identity and versions
- Bidirectional traceability
- Impact and change analysis
- Named engineering responsibility
- Review and approval status
- Evidence and provenance
- Controlled synchronization
- Customer-defined deployment
Questions teams ask
Frequently asked questions
Clear answers for engineering, quality, security and programme leaders.
Can KlugSpice assist across all Automotive SPICE process areas?
KlugSpice can assist activities and evidence preparation across Automotive SPICE process areas. Exact workflow coverage depends on the organisation’s processes, project scope, available context and configured capabilities.
Can KlugSpice automatically approve engineering work products?
No. KlugSpice prepares and analyses engineering outcomes. Authorized engineers remain responsible for review, acceptance, approval and release.
Can KlugSpice maintain bidirectional traceability?
KlugSpice can analyse lifecycle relationships, identify potential gaps and propose trace links. Proposed relationships remain subject to engineering review and approval.
Can KlugSpice perform change-impact analysis?
KlugSpice can identify related requirements, architecture, interfaces, components, tests, evidence, baselines and responsible roles that may be affected by a proposed change.
Does KlugSpice replace Polarion, DOORS Next or Codebeamer?
No. KlugSpice can be integrated with existing engineering systems while those systems remain authoritative. Available integration scope depends on the customer environment and implemented interfaces.
Can KlugSpice determine an Automotive SPICE capability level?
No. KlugSpice can assist with evidence analysis and readiness observations. A qualified assessor determines process-attribute ratings and capability levels.
Start with controlled scope
Evaluate KlugSpice on one controlled Automotive SPICE workflow.
Select a defined workflow, connect the relevant approved context and evaluate quality, effort, traceability, change-impact visibility and control.