Automotive & Mobility

Engineering Requirements Copilot

Designed for Systems engineer

Keep automotive systems requirements traceable and testable by linking each requirement to design decisions, verification cases, and applicable regulations, with engineering review before a baseline is frozen.

Contract AUT-02 · primary aggregate RequirementBaseline · mode loading

Decision brief

Freeze the baseline: evidence ready for review

This brief starts with the decision, evidence, and accountable owner. The guided workflow then shows how the recommendation was produced.

Decision signals

The evidence and control points that shape this recommendation.

Decision owner

Chief engineer and systems authority

The named role remains accountable for the consequential decision.

Governed evidence

5 record types

Structured records and cited text ground the recommendation.

Workflow

5 controlled stages

Each transition records its input, output, status, and audit context.

Human controls

1 approval gate

Approval gates prevent the copilot from making consequential decisions.

Business problem

Ahead of a design freeze the copilot shows that 14 ASIL-C braking requirements have no passing verification case, links three of them to a superseded design decision on pedal feel, surfaces a newly effective UN regulation clause for the European market with no allocated requirement, and the chief engineer withholds the freeze until the gaps are closed..

Decision to make

Keep automotive systems requirements traceable and testable by linking each requirement to design decisions, verification cases, and applicable regulations, with engineering review before a baseline is frozen.

Outcome to show

Frozen baseline released to development partners gives Chief engineer and systems authority the evidence needed to begin the final governed business outcome, with the decision trail retained for review.

  1. 1Author or import the requirement
  2. 2Check quality, ambiguity, and duplication
  3. 3Link regulations and design decisions
  4. 4Assess verification coverage
  5. 5Freeze the baseline

Step 1 of 5

Ready: Start with the business question, then use the single button above.

The output appears here immediately. More technical evidence remains available below.

System logic, GenAI, and human accountability

The demonstration keeps deterministic controls, AI assistance, and approval separate.

System logic

Source systems enforce identity, workflow order, policy filters, and record updates.

GenAI contribution

Retrieval and generation assemble relevant evidence into a cited recommendation or draft.

Human accountability

Chief engineer and systems authority verifies material claims and approves the consequential action.

Workflow stages

Run the stages in order before using the Copilot. Every stage explains what happens, why it matters, the evidence it uses, and the complete API request and response.

Seeded record
Loading
Document type
Loading
Container
Loading
Partition key
Loading
Current stage
Loading

API demonstration guidance

Run a stage to see its explanation, evidence, full request, and full response.

Grounded chat

Ask a question and receive an answer grounded in retrieved RequirementBaseline evidence.

Answer and evidence

Select a starter question or enter your own.

Evidence

Domain implementation workspace

Loaded live from /api/config, /api/domain/model, and /api/domain/sample.

Domain objective
Keep automotive systems requirements traceable and testable by linking each requirement to design decisions, verification cases, and applicable regulations, with engineering review before a baseline is frozen.
Primary aggregate
RequirementBaseline
Primary container
requirementBaselines
Hierarchical key
/tenantId + /vehicleProgramId
Schema version
1

Sample scenario

Ahead of a design freeze the copilot shows that 14 ASIL-C braking requirements have no passing verification case, links three of them to a superseded design decision on pedal feel, surfaces a newly effective UN regulation clause for the European market with no allocated requirement, and the chief engineer withholds the freeze until the gaps are closed.

Physical Cosmos DB containers

Every container provisioned for this accelerator with its hierarchical partition key.
Container Role Hierarchical partition key Document types
requirementBaselines Primary /tenantId + /vehicleProgramId RequirementBaseline, SystemRequirement, DesignDecisionRecord, VerificationCase
homologationRegulationLibrary Reference /tenantId + /marketCode RegulatoryRequirementClause

Document types

Contract document types, their owning container, and their identifier pattern.
Type Container Partition key Identifier pattern Embedding fields
RequirementBaseline requirementBaselines /tenantId + /vehicleProgramId baseline::{vehicleProgramId}::{baselineLabel} None
SystemRequirement requirementBaselines /tenantId + /vehicleProgramId requirement::{vehicleProgramId}::{requirementId} requirementVector
DesignDecisionRecord requirementBaselines /tenantId + /vehicleProgramId decision::{vehicleProgramId}::{decisionId} rationaleVector
VerificationCase requirementBaselines /tenantId + /vehicleProgramId verification::{vehicleProgramId}::{caseId} None
RegulatoryRequirementClause homologationRegulationLibrary /tenantId + /marketCode regulation::{marketCode}::{regulationId}::{clauseRef} clauseVector

Query patterns