ARTUS FOR AUTOMOTIVE

Move automotive changes forward. Keep the evidence connected.

Connect change requests to affected requirements, systems, code and verification evidence across OEM and supplier workflows.

Book an automotive walkthrough

Explore the change workflow

Built around Automotive SPICE change-management and traceability workflows

Photographic vehicle cutaway exposing automotive electronic systems and internal assemblies

Changed requirement

Affected ECU

Verification evidence

From change request to reviewable evidence.

Follow the impact across engineering work products and bring the supporting evidence into review.

ILLUSTRATIVE EXAMPLE / An OEM requests revised regenerative-braking handover under cold-battery conditions.

SUP.10 · Change request management

CR-208 · Cold-battery regenerative-braking handover

OEM request · Revision 03 · Source: OEM change request CR-208

REQ-BRK-042 · Maintain the agreed braking demand during regenerative-to-friction handover under cold-battery conditions.

Source baseline: OEM-REQ-B12 · Proposed calibration: C08

Illustrative example · Requirement wording and acceptance criteria require OEM review.

SUP.10 · Change request management

CR-208 · Cold-battery regenerative-braking handover

OEM request · Revision 03 · Source: OEM change request CR-208

REQ-BRK-042 · Maintain the agreed braking demand during regenerative-to-friction handover under cold-battery conditions.

Source baseline: OEM-REQ-B12 · Proposed calibration: C08

Illustrative example · Requirement wording and acceptance criteria require OEM review.

SYS / SWE · Traceability and verification

Follow the affected engineering path

SYS-BRK-042 · System requirement · Brake-demand continuity

IF-BRK-017 · Brake-control interface · Available regenerative torque

BrakeBlendController · Software implementation · Handover logic

Three illustrative linked work products. Engineers validate the impact and applicability.

SUP.8 · Configuration management

HIL-BRK-219 · Cold-battery handover

Result: Passed · Evidence: HIL report BRK-219-R2

Tested configuration: EV Standard · SW 3.14 · Calibration C07

Proposed change: EV Standard · SW 3.14 · Calibration C08

A passed result is associated with C07. Coverage of C08 is not established by this record.

SUP.10 · Change request management

A reviewable decision, not an automatic approval

OEM requirements owner · Confirm acceptance criteria · Open

Tier 1 software owner · Confirm delivery baseline · Open

Verification lead · Confirm C08 coverage · Open

Decision record DR-208 · Pending review · Closure remains with authorised programme reviewers.

View process alignment

A passing test may cover yesterday’s configuration.

Cold battery

Brake-control ECU

HIL evidence

EV Standard · Programme EV-S · SW 3.14

Proposed calibration

C08

Tested calibration

C07

Evidence gap identified

Illustrative records. Shared ECU hardware does not establish identical variant applicability.

Connect the tools your programme already runs on.

Bring requirements, implementation, interfaces and test evidence into the same change context.

EXPLORE YOUR TOOLCHAIN / Connection options confirmed during scoping.

Requirement revisions & acceptance criteria

IBM DOORS Next

Candidate toolchain example

Unconfirmed

Siemens Polarion

Candidate toolchain example

Unconfirmed

PTC Codebeamer

Candidate toolchain example

Unconfirmed

ARTUS / CR-208 CHANGE REVIEW

Requirement revisions & acceptance criteria · Linked change context · Review evidence

Connection options confirmed during scoping. Examples are not an available-integrations catalogue.

Requirement revisions & acceptance criteria

IBM DOORS Next

Candidate toolchain example

Unconfirmed

Siemens Polarion

Candidate toolchain example

Unconfirmed

PTC Codebeamer

Candidate toolchain example

Unconfirmed

ARTUS / CR-208 CHANGE REVIEW

Requirement revisions & acceptance criteria · Linked change context · Review evidence

Connection options confirmed during scoping. Examples are not an available-integrations catalogue.

Commits, issues & change requests

GitHub

Candidate toolchain example

Unconfirmed

GitLab

Candidate toolchain example

Unconfirmed

Azure DevOps

Candidate toolchain example

Unconfirmed

Jira

Candidate toolchain example

Unconfirmed

ARTUS / CR-208 CHANGE REVIEW

Commits, issues & change requests · Linked change context · Review evidence

Connection options confirmed during scoping. Examples are not an available-integrations catalogue.

Models, ARXML & DBC artefacts

MATLAB / Simulink

Candidate toolchain example

Unconfirmed

AUTOSAR ARXML

Format / artefact — not a software connector

Unconfirmed

CAN DBC

Format / artefact — not a software connector

Unconfirmed

ARTUS / CR-208 CHANGE REVIEW

Models, ARXML & DBC artefacts · Linked change context · Review evidence

Connection options confirmed during scoping. Examples are not an available-integrations catalogue.

Results & configuration manifests

Vector CANoe

Candidate toolchain example

Unconfirmed

dSPACE

Candidate toolchain example

Unconfirmed

HIL / SIL test reports

Format / artefact — not a software connector

Unconfirmed

ARTUS / CR-208 CHANGE REVIEW

Results & configuration manifests · Linked change context · Review evidence

Connection options confirmed during scoping. Examples are not an available-integrations catalogue.

One change. Clear responsibilities across the programme.

Earlier scope clarity and fewer late surprises help teams protect delivery commitments.

SELECTED CHANGE / CR-208 · Cold-battery regenerative-braking handover

OEM

Requirement & acceptance criteria

Requirements owner · Confirm scope

Tier 1

Implementation & delivery baseline

Software owner · Confirm delivery

Verification team

Test scope & supporting results

Verification lead · Confirm coverage

Illustrative responsibility assignments. Programme owners confirm actual review and approval authority.

Clarify change scope

Surface evidence gaps

Coordinate release decisions

Start with one subsystem. Bring one real change.

Scope an evaluation around your requirements, configurations, implementation and verification evidence.

01 · Choose the change

02 · Connect the relevant sources

03 · Review the impact together

Discuss an automotive evaluation

Every change has consequences. Know them first.

Get Started

Learn More

Every change has consequences. Know them first.

Get Started

Learn More

Every change has consequences. Know them first.

Get Started

Learn More