New white paper: Software defines premium — the 7 Pillars


02 · Autodefence

Autodefence — proof that holds for decades.

Diagnostics, traceability and software lifecycle management for defence platforms with decades-long service lives. In defence service since 2012, on programmes for Saab, FMV and BAE Systems Bofors.

X-ray view of a defence vehicle with an RBS 70 launcher, electronic control units highlighted in orange
Air-defence carrier, x-ray view — every control unit traceable
A camouflaged Oshkosh vehicle carrying a mast-mounted RBS 70 NG launcher and sight, parked by a lake
The same platform, in the field. Every control node on a vehicle like this runs its own software and holds its own configuration — and all of it has to be read, updated and verified for as long as the platform stays in service.Foto: Linus Svensson, Saab AB · Copyright Saab AB

The problem

A 35-year asset, a 5-year tool chain.

Defence platforms serve for thirty to forty years. The silicon, operating systems and test tools they were delivered with turn over every few years. A platform that cannot be diagnosed cannot be confidently returned to service — and if the only route to its ECUs runs through a single vendor's proprietary tool, readiness depends on that vendor's commercial decisions.

What we do

Traceability under the hardest requirements.

  1. 01

    System safety, hazard tracking and SBOM traceability

    Every requirement, hazard and software component tracked from specification to verified function — the evidence chain that defence certification and audits demand.

  2. 02

    Diag Studio and ALM/PLM audit support

    Off-board diagnostics for defence platforms, plus the application-lifecycle backbone that keeps decades of configuration history auditable.

  3. 03

    Sustainment across the full platform lifecycle

    Defence platforms serve for 30–40 years. We stay through upgrades, re-certifications and generation shifts — the long-term partner the platform's lifespan requires.

    Licence form, source-code escrow and maintenance — the continuity terms

Standards

Standards we work to.

  1. 01

    H SystSäk 2022

    The supplier's activities and deliverables the handbook names — SSPP, SAR, SCA — and a delivery model shaped around them rather than bolted on at the end.

  2. 02

    ISO 26262 → MIL-STD-882E

    What automotive functional-safety evidence carries over to a defence programme, and what has to be learned: mishap scope and formal risk acceptance.

  3. 03

    UN R155 / R156 and ISO/SAE 21434

    The diagnostic channel as a regulated attack surface, and the secured update path — the automotive frame that defence programmes are converging on.

  4. 04

    Tool-independent by design

    UDS (ISO 14229), ODX (ISO 22901) and DoIP (ISO 13400) as the reason the diagnostic capability outlives any one vendor's tool.

Products in this area

Built on our own software.

Delivery proof

Cases in this area.

More cases in this area

  1. BAE Systems BoforsFrom vehicle bus to fleet readinessHow BAE Systems Bofors turned the Archer howitzer's operational data into a fleet-management capability — with Diadrom.
  2. FMVOne interface for an entire military fleetHow FMV unified vehicle diagnostics across a mixed fleet — with Diadrom.

In defence service since 2012

Engaged early in the development of Saab's RBS 70 NG — and still managing the product across its lifecycle.

Member of SOFF — Swedish security & defence industry

Discuss a defence programme