Beyond the buzz: Why automakers are betting on software‑defined vehicles

Insights

• SDVs turn the car from a fixed product to a continuously evolving platform.
• Original equipment manufacturers (OEMs) are rethinking how vehicles are designed, validated, and monetized.
• Rising software complexity is pushing OEMs to consolidate compute and standardize architectures to control cost and risk.
• Differentiation is shifting from hardware performance to experience orchestration.
• Long‑term advantage will favor OEMs that own the platform, talent, and release discipline.

For more than a century, automotive advantage was built on mechanical engineering: powertrains, materials, manufacturing quality, and supply-chain. That still matters, but software and electronics now play an equally important role. OEMs are reorganizing the vehicle into a continuously updateable computing platform with a different life cycle model.

What’s driving the shift towards SDVs?

An SDV is best understood as an architectural and operating model shift. Hardware and software are deliberately decoupled, allowing a common platform to be reused across multiple vehicle models. Instead of treating software as a fixed component tied to individual electronic control units (ECUs), automakers are moving toward centralized compute, standardized platforms, and continuous software delivery supported by over‑the‑air (OTA) updates.

Complexity and cost pressures

Modern vehicles integrate advanced driver assistance systems (ADAS), electrified powertrains, infotainment, connectivity, and stringent safety features. Each addition increases software and electronic complexity. Many vehicles now contain tens of millions of lines of code sourced from dozens of suppliers.

This adds cost and integration risk. OEMs often deal with duplicated functionality, inconsistent update mechanisms, and extended validation cycles across supplier systems.

To regain control, OEMs are adopting zonal or centralized electrical and electronic (E/E) architectures, consolidating the IT resources needed into fewer high-performance controllers, and standardizing platforms that can be deployed across the vehicle portfolio. The objective is to reduce integration overhead, accelerate validation, and limit the cost escalation associated with bespoke vehicle program.

New, recurring revenue streams

SDVs also create post-sale digital revenue. Features can be activated after purchase through subscriptions, feature-on-demand models, or service bundles. Connected vehicles generate vast data that can be analyzed for usage-based insurance offerings and predictive maintenance.

Faster and safer OTA updates

OTA updates allow automakers to fix bugs, improve on-road safety, and add features without costly physical recalls. However, updates must be rigorously validated and securely deployed. Over time, this improves vehicles’ reliability and extends the useable life of vehicles by keeping systems current with regulatory, safety, and performance requirements.

Stronger customer relationships

In an SDV world, differentiation increasingly sits in the experience layer: how the vehicle adapts to driver preferences, integrates with digital ecosystems, and evolves over time. Features such as hill assist, traction control, and personalized driver profiles are now refined through software rather than hardware changes.

Challenges in delivering SDVs

Moving from mechanical-centered system to software-driven systems is complex. While SDVs promise faster innovation, feature upgrades over time, and new digital business models, delivering these benefits at scale introduces significant structural and regulatory challenges. As OTA delivery becomes standard, OEMs must manage rising software complexity, safety-critical validation, cybersecurity, and compliance obligations across the vehicle life cycle.

Cybersecurity risks

Greater connectivity expands the attack surface for malicious actors. Potential targets include vehicle control systems, personal data, cloud back ends, and the OTA delivery pipeline. Key risks include remote hijacking of ECUs or high-performance controllers, mobile application breaches that leak credentials or enable unauthorized access, insecure OTA updates that introduce supply-chain compromise, ransomware attacks on vehicles or backend systems, and sensor spoofing that degrades ADAS/automated-driving perception. Any successful attack can compromise safety, privacy, and brand trust.

To address this, the United Nations Economic Commission for Europe (UNECE) through UNECE R155 requires OEMs to implement a certified cybersecurity management system across development, production, and post‑production. This includes threat modeling, vulnerability management, incident response processes, and continuous monitoring throughout the vehicle life cycle.

Data privacy and ownership concerns

SDVs generate continuous streams of data related to vehicle performance, location, usage patterns, and driver behavior. Managing this data responsibly raises concerns about governance, storage, consent, and ethical use.

For automakers, the primary challenge is balancing data-driven services with regulatory compliance and customer trust. This requires transparent consent models, region-specific controls aligned with privacy regulations, and clear separation between operational, diagnostic, and commercial data use cases.

Software upgrade complexity

Modern vehicles contain millions of lines of code across multiple systems. Unlike phones or consumer devices, vehicles must remain operational under all conditions. Software updates cannot interrupt critical functions, and rollback mechanisms must be available if faults are detected after deployment.

UNECE R156 mandates a software update management system with traceability, auditability, and secure update pipelines. OEMs must prove that updates are validated, deployed in controlled stages, monitored in the field, and reversible if issues arise. Managing this across millions of vehicles with varying configurations is a nontrivial operational task.

Organizational readiness

OEMs need employees skilled in both software development and traditional vehicle engineering to achieve their software-defined product goals. Many OEMs are restructuring teams and are looking for software engineers, AI specialists, and cybersecurity professionals — roles traditionally associated with the tech industry rather than the mechanical automotive manufacturing.

High development cost

Developing SDV platforms requires substantial investment in compute architectures, validation infrastructure, digital tooling, compliance framework, and safety-critical OTA updates. Many OEMs can’t justify these costs independently, leading to partnerships that combine expertise and share investment. Examples include Mercedes-Benz–NVIDIA partnership on centralized vehicle compute, the GM–Red Hat collaboration on a safety-certified in-vehicle Linux base for GM’s Ultifi software platform, and the BMW–Qualcomm–AWS partnership on a cloud-enabled ADAS stack.

Revenue model friction

Customers could resist paying subscriptions for features previously included as standard. In addition, fragmented legacy architecture makes it difficult for some OEMs to deploy full vehicle OTA rollout, as not all control units can be updated or are securely addressable. This slows deployment and increases operational complexity.

Operating‑model priorities for automakers

Design the platform, not just features

OEMs must define reusable software stacks and E/E architectures. This includes setting clear boundaries between OEM-owned software and partner-provided components to maintain long-term control over system evolution.

Treat OTA as a regulated product capability

OTA delivery should be treated as a governed product function, not an afterthought. This requires release management, audit trails, rollback strategies, fleet monitoring, and secure update processes that meet UNECE R156.

Focus on safe software updates

Competitive advantage will not come from pushing more updates, but from sharing the right updates safely. Validation discipline, staged deployment, and postdeployment observability are critical to maintaining trust and safety at scale.

Build a governed engineering workbench

Move beyond linear development models toward closed-loop engineering, with deep agentic AI foundation, where learning from real-world vehicle behavior continuously improves requirements, design decisions, and software releases.

Rather than using AI only for point productivity, an integrated workbench can apply AI across the lifecycle: requirements interpretation, design decomposition, test generation, validation planning, defect triage, and release confidence.

For safety-critical automotive software, the priority is governed speed: faster iteration with nonnegotiable controls for safety, compliance, traceability, and clear human accountability.

Partner selectively while keeping architectural control

Partnerships accelerate delivery, but OEMs must retain ownership of the core platform and customer experience. Long‑term differentiation lies in architectural authority, not tool selection.

How are leading automakers adopting SDVs?

SDVs are transitioning from concept to large‑scale deployment. They are continuously interacting with surrounding ecosystems such as personal devices. OEMs and technology partners are actively building toward a future with resilient vehicle connectivity and centralized compute architectures. Global automobile leaders are showing how it is done.

Mercedes‑Benz’s MB.OS illustrates the push toward a unified operating system spanning infotainment, automated driving, body and comfort, and driving and charging. Rather than treating software as a fixed ECU‑level component, Mercedes is building a chip‑to‑cloud platform and an internal software pipeline designed for rapid, repeatable release cycles that can produce a full‑vehicle software package within a week, and is integrating software downloads into manufacturing workflows.

Xiaomi’s Human × Car × Home strategy positions the SDV as an extension of Xiaomi’s consumer electronics ecosystem. The vehicle is framed as part of a single connected lifestyle where phones, home appliances, and car exchange status and controls through one platform, turning the cabin into a familiar digital environment for Xiaomi users.

BMW’s Neue Klasse program bundles vehicle functions into a small number of high‑performance central compute units, supported by a zonal wiring architecture that reduces cables and weight, while decoupling hardware/software to enable ongoing OTA upgrades. The company’s Heart of Joy is a central high‑performance control unit for driving dynamics, designed for rapid orchestration of drivetrain and chassis functions.

An example of an applied SDV operating-model

IBI has recently helped a Europe-based EV manufacturer modernize the infotainment and platform engineering life cycle. The engagement focused on establishing a standardized DevOps and CI/CD foundation aligned with SDV principles, enabling software teams to move away from program-specific delivery toward a reusable, platform-centric model. This included integrating source control, build automation, testing, artifact management, and observability into a single governed pipeline.

Rather than accelerating release volume alone, the initiative emphasized validation rigor, traceability, and repeatability, which are key requirements for safety‑critical automotive software and UNECE‑compliant OTA delivery. The resulting setup supported staged releases, improved defect detection earlier in the life cycle, and better visibility across software versions deployed in the field.

For the client, the impact was about operating discipline: faster iteration without compromising safety, greater consistency across vehicle programs, and a foundation that can scale as software volume and configurational complexity increase. This illustrates how SDV benefits are realized through sustained changes in how vehicle software is engineered, validated, and maintained over time.

Toward a smarter and responsive future

The SDV transition is an industrial response to rising complexity, regulatory updates, and margin pressure. Vehicles are becoming software platforms, but competitive advantage will favor OEMs that can operate them effectively.

Success depends on platform reuse, compliant OTA pipelines, robust cybersecurity, and measurable real‑world outcomes. Software is becoming the primary lever for feature rollout, quality improvement, and differentiation, while reducing duplication across vehicle programs.

For automakers, the challenge now is executing the software model at scale.