Software-defined vehicles: From building blocks to platform


This guest blog was written by CSEP collaborators Jonathan Smith, Professor Siddartha Khastgir, and Halima El Badaoui (WMG, University of Warwick), the authors of “The roadmap towards a Software Defined Vehicle UK centric platform: A systems thinking approach” report.

* * *

Building the software-defined vehicle might not be the hardest part. Building the platform that harmonises value to all stakeholders might be.

Technologies are advancing quickly: high-performance computing, software platforms, over-the-air updates, battery intelligence, connectivity, and increasingly data-driven services. But turning those capabilities into safe, scalable, and commercially valuable products depends on something broader: manufacturers, suppliers, infrastructure providers, insurers, regulators, and users being able to work together as part of one connected system.

That is the central message of our report. The UK already has many of the capabilities needed to compete in software-defined vehicles, but capturing their full value will depend on how effectively those capabilities are coordinated, integrated, and governed across the vehicle lifecycle.

An Ecosystem, Not Simply A Technology

There is still no shared operational understanding of what constitutes an SDV. The term is frequently used to describe individual technologies, but an SDV is better understood as a system that evolves throughout the vehicle lifecycle – from design and development through deployment, maintenance, software updates, and end-of-life management.

We therefore establish our own definition of an SDV, drawing on established definitions from the industrial literature such as the Eclipse Foundation, Advanced Propulsion Centre, IBM, Siemens and ARM to be:

A vehicle that’s engineering and operations are centralised through software across both safety critical and none-safety critical attributes: the software first vehicle

That wider view changes the question from ‘which technology do we need?’ to ‘what needs to work together, who is responsible, and what must be monitored as the system changes?’. It also exposes the dependencies that determine whether technical capability can be converted into reliable services and commercial value.

Why The UK Has A Credible Opportunity

The report finds that the UK already has many of the capabilities needed to compete in this emerging market, including strengths in artificial intelligence, cybersecurity, cloud computing, telecommunications, digital health, advanced engineering, and insurance. The challenge is not simply to create more capability, but to meaningfully connect what already exists driven by realistic two-way incentives and value chain construction.

National advantage rarely comes from technical excellence alone. It depends on coordinated investment, effective knowledge transfer and an environment in which technologies can be integrated, commercialised, and scaled. The report therefore proposes a UK-centric SDV platform: a shared foundation through which manufacturers, suppliers, technology companies, insurers, regulators, and researchers can develop and test interoperable services.

From Systems Thinking To Practical Action

Using a systems-thinking approach, the report maps the stakeholders, interactions, assumptions, and feedback loops that shape an SDV across both its development and operational phases. Case studies covering battery health and charging, secure software updates and insurance pricing demonstrate how value depends on coordination across organisational boundaries.

For example, effective battery services require more than battery hardware. They depend on reliable data, analytics, charging infrastructure, software, maintenance providers, and agreed responsibilities across the supply chain. Secure updates similarly require coordinated authentication, testing, rollback, and incident-response processes. Usage-based insurance depends on trustworthy access to standardised vehicle data and transparent customer consent.

These examples show why assurance cannot be treated as a one-off approval exercise. It must continue throughout the vehicle lifecycle, supported by monitoring, incident reporting, operational feedback, and regularly updated evidence.

Priorities For The Road Ahead

The report identifies several immediate priorities, illustrated in Table 1:

Priority What this means in practice
1. Shared requirements Create a common requirements register covering functionality, safety, cybersecurity, data governance, interoperability and commercial arrangements.
2. Open interfaces and common data models Build the platform around standardised, open interfaces and reusable data models so services can integrate without unnecessary duplication.
3. Continuous lifecycle assurance Establish continuous assurance, monitoring and incident-response processes rather than relying on one-off approval.
4. Trusted third-party onboarding Introduce a robust certification and onboarding process for third-party services that need to interact with the vehicle or platform.
5. Public trust by design Give users transparency and control over how their data is collected, shared and used.

Table 1: Platform requirements established from systems thinking.

From Report To Implementation

The SDV opportunity is not only about producing more software-enabled vehicles. It is about building the trusted ecosystem, shared infrastructure and collaborative business models needed to support them. If the UK can connect its existing strengths through a coordinated platform, it can reduce duplication, accelerate innovation, and create new products and services for a global market.

The next step is therefore not another isolated technology programme. It is to turn this systems-level view into a compelling business case and a practical programme of implementation that industry and policymakers can act on.