CONTACT US

AUTOMOTIVE · ISO 26262 · ASPICE · AUTOSAR

Automotive systems engineering for ASPICE, ISO 26262 and AUTOSAR programs

SodiusWillert deploys, extends and supports IBM Engineering Lifecycle Management for OEMs and suppliers. Trace requirements to tests across ASPICE process areas, generate ISO 26262 evidence from live engineering data, and build AUTOSAR components in IBM Rhapsody.

Traceability and Standards Regulations in the Automotive Industry
ISO 26262 · ASPICE Evidence from live lifecycle data

Trusted by regulated industry leaders

  • continental-customers-sodiuswillert (1)
  • marquardt-customers-sodiuswillert
  • daimler-customers-sodiuswillert (1)
  • motional ad-customers-sodiuswillert
  • denso-customers-sodiuswillert

YOUR CHALLENGES

Automotive programs are assessed on evidence, not intent

Software now defines the vehicle. Every requirement, model, test and change must stay linked across teams, tools and companies, and be ready for an assessor at any point in the program.

Traceability that holds up in an ASPICE assessment.

Assessors check bidirectional traceability and consistency from stakeholder requirements to software tests. Missing or outdated links drop a process to a lower capability level and put the supplier rating at risk.

Functional safety and cybersecurity evidence.

ISO 26262 expects safety requirements traced through decomposition, ASIL allocation and verification. ISO/SAE 21434 adds cybersecurity goals and requirements. Evidence assembled in spreadsheets before an audit goes stale the next day. Image: safety goal decomposed into requirements, design and tests.

Requirements exchange between OEMs and suppliers.

Specifications cross company boundaries in ReqIF, each side runs its own tools, and every change round trip creates suspect links, review cycles and contractual risk. Image: OEM and supplier toolchains exchanging ReqIF packages.

AUTOSAR architectures across platforms and variants.

Classic and Adaptive platforms coexist in the same vehicle, ARXML must stay consistent with design models, and the same components ship in dozens of variants. Image: one model feeding Classic and Adaptive ECUs and variants.

STANDARDS

Our solutions are built around the standards your programs are assessed against

Each standard sets specific demands on your toolchain. We configure IBM ELM and our own tools to produce the work products and trace links assessors ask for.

OUR SERVICES

How do you prove traceability across a multi-tool, multi-company automotive toolchain?

We work on the building blocks that make traceability assessable: the IBM ELM lifecycle, links between the tools you keep, OEM–supplier exchange, AUTOSAR models, reviews and team adoption.

IBM ELM

Build one traceable engineering lifecycle

We license, deploy and configure IBM ELM so requirements, models, tests and change share one data set across DOORS Next, Rhapsody, Engineering Workflow Management and Engineering Test Management. Information model, link types, attributes and reports are defined around the ASPICE and ISO 26262 work products your OEM assesses. Global Configuration Management carries the same structure across platforms and variants.

What we observe

In many supplier organizations, each discipline runs its own tool and its own link conventions. Traceability exists inside each tool but breaks at every hand-off, which is exactly where assessors look.

OSLC

Link the tools you keep, without copying data

Connect links Jira, PTC Windchill and Confluence to IBM ELM artifacts. Developers stay in Jira, change notices stay in Windchill, and each work item carries a live link to the requirement it implements or verifies.What we observe: Sync-based integrations duplicate artifacts and drift after the first change. Teams end up reconciling copies before every assessment instead of trusting the links. [VALIDATE with SME]

What we observe

Sync-based integrations duplicate artifacts and drift after the first change. Teams end up reconciling copies before every assessment instead of trusting the links.

Supplier exchange

Keep traceability across the OEM–supplier boundary

We set up ReqIF round trips between OEM and supplier requirements tools, and ReqXChanger brings incoming specifications into Rhapsody or Enterprise Architect. Changed requirements raise suspect links, and trace relationships go back to the source tool.

What we observe

Each specification release arrives as a document or ReqIF package re-imported by hand. Links from the previous release are lost, and impact analysis restarts from zero.

AUTOSAR

Model components with traceability to requirements

With the AUTOSAR extension we developed for IBM Rhapsody, teams import and export ARXML, model Classic and Adaptive components, and generate code with RXF for AUTOSAR Classic, each element linked to the requirements it implements.

What we observe

AUTOSAR configuration and design models often live in separate tools. ARXML becomes the reference, and the link between architecture and system requirements is rebuilt by hand for each release.

Reviews

Produce assessment evidence as you review

SECollab runs structured reviews of requirements and models across tools, and records comments, decisions and approvals against the reviewed baseline. The review trail is ready for joint reviews and change control.

What we observe

Reviews still happen in exported Word and Excel files and email threads. The decision exists, but the proof that it was made on the current baseline does not.

Adoption

Make traceability part of daily engineering

Training, workshops and safety-critical development support help teams apply ASPICE and ISO 26262 traceability rules in their daily work, not only in the weeks before an assessment.

What we observe

Toolchains configured without an adoption plan degrade fast: links are skipped under deadline pressure, and gaps reappear before the next assessment.

IBM ELM for AUTOMOTIVE

One engineering lifecycle for requirements, models, tests and change

IBM Engineering Lifecycle Management connects DOORS Next, Rhapsody, Engineering Workflow Management and Engineering Test Management in one traceable data set.

Bidirectional traceability by default.

Link stakeholder, system and software requirements to architecture, code, tests and results, and show coverage at any level for an assessor.

Variants and reuse.

Global Configuration Management versions requirements, models and tests together, so platforms and variants reuse components instead of copies.

Impact analysis on every change.

Suspect links and change sets show which requirements, models and tests a change affects before it reaches integration.

Requirements quality from the start.

IBM Engineering Requirements Quality Assistant uses IBM Watson® Natural Language Processing (NLP) to detect potential ambiguities and generates real-time scores to assess the quality of requirements.

Assessment-ready reporting.

Dashboards and document generation produce traceability views and work products from current data, not from spreadsheets assembled before an audit.

AI IN AUTOMOTIVE ENGINEERING

Governed AI for safety-relevant engineering

AI agents can draft, analyze and summarize engineering data in seconds. In an ISO 26262 or ASPICE program, each output still needs a reviewer, a baseline and a trace link. IBM Engineering AI Hub brings agents into IBM ELM under those rules, and SodiusWillert deploys and governs it in your environment.

Change impact analysis

For a change request, agents find related requirements, impacted model elements, work items and tests, and prepare an impact summary for engineering review.

Requirements quality.

Agents score requirements in DOORS Next against writing rules and propose rewrites before formal review, when fixes cost least.

Test coverage gaps.

Agents flag requirements with missing or weak test coverage, so gaps surface before the assessment rather than during it.

Work item drafting and summaries.

Agents draft work items and summarize defects and change history in Engineering Workflow Management, so engineers spend less time reconstructing context.

Engineers stay accountable.

Agents work inside ELM access controls, and changes they propose go through change sets that engineers review and approve. AI assists analysis; it does not replace the verification and validation evidence ISO 26262 requires.

Your data stays under your control.

On premises, in your cloud or air-gapped, with a choice of language models including IBM watsonx.ai and Amazon Bedrock.

Explore Engineering AI Hub →

FREQUENTLY ASKED QUESTIONS

Automotive systems engineering: your questions answered

Do we need AUTOSAR training to develop AUTOSAR components in IBM Rhapsody?

No in-depth AUTOSAR specification knowledge is required. The AUTOSAR extension for IBM Rhapsody, developed by SodiusWillert, handles ARXML import and export, and RXF for AUTOSAR Classic generates code for software components. Some AUTOSAR knowledge still helps teams get started faster.

Can we exchange requirements with an OEM or supplier that uses a different tool?

Yes. ReqIF is the standard format for requirements exchange between OEMs and suppliers. IBM DOORS and DOORS Next exchange ReqIF natively, and ReqXChanger brings ReqIF requirements into Rhapsody or Enterprise Architect models with traceability back to the source.

Does IBM ELM make our organization ASPICE compliant?

No tool makes an organization ASPICE compliant: ASPICE assesses processes and is tool-agnostic. IBM ELM supports the assessment by keeping bidirectional traceability and consistency between work products and by generating the evidence assessors review.

How does IBM ELM support ISO 26262 traceability?

IBM ELM links safety goals, safety requirements, architecture elements and verification results across DOORS Next, Rhapsody and Engineering Test Management. Suspect links flag every affected item when a requirement changes, and reports show coverage per ASIL.

Talk to an automotive systems engineering expert

Tell us about your program. Contact our team to discuss with an automotive specialist who will map your toolchain, assessment targets and next steps with you. We reply within one business day.