Skip to content
AXXA

Sector 02

Automotive

Vehicles have become distributed computers on wheels. We engineer the software that has to work across all of them.

01Introduction

Overview

Automotive software is defined by scale, regulation and long-term responsibility: many variants, many suppliers, and a vehicle that must remain safe and secure for its entire service life.

We contribute senior engineering to the parts of the vehicle where embedded software, communication and integration meet, and we produce the evidence that safety and cybersecurity processes require.

Schematic of a zonal vehicle architecture: a central compute unit connected over an automotive Ethernet backbone to zone controllers, which connect to ECUs over CAN; a telematics unit links the vehicle to cloud services for over-the-air updates.AUT · SCHEMATICFRONTHPCCENTRALZONE 1ZONE 2ZONE 3ZONE 4CANETHTCUCLOUD · OTA

02Engineering challenges

What makes this sector difficult.

  1. 01

    Architectures in transition

    The move from dozens of ECUs to zonal and central compute changes where software runs, how it communicates and who owns which interface.

  2. 02

    Safety and cybersecurity by regulation

    Functional safety and cybersecurity are type-approval matters. Every architectural and process decision has to produce evidence for both.

  3. 03

    Mixed criticality on shared hardware

    Safety-relevant functions, infotainment and connectivity share compute platforms. Isolation and timing guarantees must be designed, not assumed.

  4. 04

    Updating vehicles in the field

    Over-the-air updates must be secure, robust against interruption and traceable across a fleet of software variants.

03Typical systems

The systems we work on.

  • Telematics and connectivity units
  • Infotainment and digital cockpit platforms on Embedded Linux
  • Zonal and central compute architectures
  • ECU software and gateways (CAN, CAN FD, Automotive Ethernet)
  • Over-the-air update chains
  • ADAS prototypes, test vehicles and test benches

04How we contribute

Capabilities applied to this sector.

05Regulatory context

Standards and regulation that shape the work.

Listed as the regulatory context engineering work in this sector must respect. They are not certifications held.

ISO 26262
Functional safety for road vehicles.
ISO/SAE 21434
Cybersecurity engineering for road vehicles.
UNECE R155 / R156
Cybersecurity management and software update management systems, required for type approval.
Automotive SPICE
Process assessment model widely used by vehicle manufacturers to evaluate suppliers.
Cyber Resilience Act (EU) 2024/2847
Excludes vehicle products covered by type approval, but can apply to aftermarket devices, chargers and tooling.

Contact

Engineering challenges in automotive?

Describe the system and its constraints. We will tell you honestly whether and how we can help.

Start a conversation