KlugSpice is an AI-native engineering execution platform for automotive programmes operating under Automotive SPICE, ISO 26262, ISO/SAE 21434 and applicable regulatory obligations.
Automotive compliance cannot be achieved by installing a tool or generating a collection of documents. It depends on performed engineering work, competent decisions, controlled work products, maintained relationships, independent evaluation and evidence that remains consistent as the product changes.
Automotive programmes frequently operate under several connected frameworks. They address different engineering and regulatory concerns and must not be treated as interchangeable.
Process assessment model
Evaluates the capability of development processes. KlugSpice can assist teams in preparing and connecting work products, reviews, traceability, baselines and objective evidence relevant to Automotive SPICE processes.
Functional-safety standard
Defines a functional-safety lifecycle for road vehicles. KlugSpice can use approved safety information as governed context and connect relevant requirements, architecture, verification, change-impact information and evidence.
Cybersecurity standard
Defines a cybersecurity-engineering lifecycle for road vehicles. KlugSpice can use approved cybersecurity information as governed context and connect requirements, engineering artifacts, verification, changes and evidence.
Type-approval regulation
Establishes vehicle-cybersecurity and CSMS requirements for type approval. KlugSpice can support related evidence relationships in configured workflows; it does not determine whether a CSMS or vehicle type satisfies UN R155.
Type-approval regulation
Establishes software-update and SUMS requirements. KlugSpice can support traceability, change impact, configuration context, verification evidence and approval history; it does not certify a SUMS.
Customer-defined execution
Approved customer processes, templates, quality criteria, terminology and review rules can be included in the governed context for configured workflows.
Scope: Availability and depth of support depend on the configured KlugSpice workflow, customer process, approved standards context, project information and implemented integrations.
KlugSpice applies governed AI to defined engineering tasks instead of treating compliance as a standalone document-generation exercise.
Use authorized artifacts, requirements, guidelines, decisions, templates and relationships.
Prepare a defined engineering proposal, finding, relationship, impact analysis or readiness observation.
Make relevant inputs, assumptions, relationships, findings and rationale available for review.
An authorized engineer accepts, revises, rejects or escalates the proposal.
Where supported, approved outcomes return through the configured repository workflow.
KlugSpice connects compliance context to performed engineering work across the development lifecycle.
Prepare and analyse requirements using approved stakeholder, system, software, safety, cybersecurity, regulatory and organisational context.
Prepare architecture and design proposals, allocations, interfaces and rationale for technical review.
Prepare verification criteria, test scenarios, specifications and coverage observations from approved context.
Analyse lifecycle relationships, propose missing links and identify orphaned artifacts or incomplete verification coverage.
Identify requirements, architecture, interfaces, components, tests, evidence, baselines and roles potentially affected by change.
Connect performed work with work products, reviews, decisions, traceability, versions and configuration status.
Automotive SPICE, functional safety and cybersecurity often depend on related product information. However, they have different objectives, work products, competent roles and acceptance criteria.
KlugSpice helps teams maintain explicit relationships between these domains without merging their responsibilities.
Performed practices, work products, reviews and objective evidence.
Approved safety analyses, requirements, constraints and assurance evidence.
Approved risk-analysis outputs, requirements, controls and supporting evidence.
Visible relationships with distinct artifact ownership and approval conditions.
A single product change can affect process evidence, system and software engineering, functional safety, cybersecurity and verification.
KlugSpice uses approved engineering, process and compliance information relevant to a configured workflow.
Requirements, architecture, interfaces, design, verification specifications, results, defects and change requests.
Derivation, allocation, dependency, implementation and verification relationships.
Applicable standards, regulatory requirements and customer-specific obligations.
Approved requirements, risk-analysis outputs, assumptions, constraints and engineering decisions.
Internal processes, templates, terminology, quality criteria, reviews and approval rules.
Approved decisions, baselines, expected outcomes, permitted actions, reviewers and synchronization rules.
KlugSpice prepares reviewable engineering outcomes and supporting information needed to evaluate consistency, relationships, impact and readiness.
Requirements, architecture descriptions, interfaces, verification criteria, test specifications and configured engineering artifacts.
Potential ambiguity, inconsistency, duplication, missing information, weak verification criteria and conflicts with project rules.
Reviewable upstream and downstream relationships between relevant engineering work products.
Missing, incomplete, orphaned or inconsistent relationships across the lifecycle.
Potential effects across artifacts, interfaces, tests, evidence, configurations, baselines and responsible roles.
Missing evidence, incomplete reviews, traceability weaknesses and unresolved configuration issues.
Potential gaps between requirements, verification criteria, planned verification and available results.
Relevant sources, versions, assumptions, analyses, reviewer identity and approval rationale according to the workflow.
KlugSpice can be integrated with requirements, ALM, PLM, test, code and delivery systems used by the customer. Existing systems can remain authoritative for approved engineering information. Integration scope depends on the customer toolchain, available APIs, permissions, required artifact types, security requirements and implemented workflow.
Potential targets include Polarion, IBM DOORS Next and Codebeamer.
Potential targets include Jira and Azure DevOps.
Potential targets include Teamcenter and relevant code, build and test environments.
References to named products identify potential integration targets. They do not imply a commercial partnership, endorsement or certified connector unless explicitly stated.
No. It provides a governed framework for preparing, connecting, reviewing and maintaining engineering work and evidence. Compliance depends on applicable requirements, performed work, competent roles and the relevant approval procedure.
KlugSpice is best described as software for compliance-ready automotive engineering. It supports compliance-related workflows but is not a certification tool, approval authority or substitute for a compliant engineering organisation.
KlugSpice can use approved HARA and TARA outputs as governed context and connect related safety and cybersecurity requirements with architecture, verification, change and evidence workflows. Exact functionality depends on the configured implementation.
General-purpose AI can draft content from a prompt. Compliance-ready engineering requires approved context, artifact identity, lifecycle relationships, named responsibility and controlled decisions.
KlugSpice is designed to prepare engineering outcomes that can be reviewed, understood, traced and controlled within established processes.
Clear answers for engineering, quality, security and programme leaders.
It helps teams apply standards, regulations and organisational processes to performed engineering work and supports the preparation, connection, review and maintenance of work products, traceability, decisions and evidence.
No. KlugSpice supports compliance-oriented engineering workflows but does not guarantee compliance, certification, assessment results or type approval.
No. KlugSpice can support preparation and connection of relevant engineering work and evidence. Certification and acceptance remain with the appropriate accountable and independent authorities.
No. It can support engineering execution, traceability and evidence preparation. Process capability is evaluated through an appropriate assessment based on performed work and objective evidence.
KlugSpice can support configured workflows relevant to cybersecurity, software updates, traceability, change control and approval history. It does not certify a CSMS or SUMS and does not grant vehicle type approval.
KlugSpice can use approved HARA and TARA outputs as governed engineering context and connect related safety and cybersecurity requirements with architecture, verification, change and evidence workflows. Exact functionality depends on the configured workflow and implementation.
No. KlugSpice can be integrated with existing systems while those systems remain authoritative. Availability depends on the customer environment and implemented connector scope.
Yes. It can identify requirements, architecture elements, interfaces, verification assets, evidence, configurations and responsible roles potentially affected by a proposed change.
Deployment can be configured according to customer infrastructure, security, identity, model and data-boundary requirements. The applicable architecture must be agreed for the specific implementation.
Select requirements quality, traceability, change-impact analysis or evidence readiness and evaluate the improvement in effort, consistency, visibility and control.
