The commercial vehicle (CV) industry is quietly undergoing a deep transformation. As OEMs shift from multiple electronic control units to centralised electrical and electronic (E/E) architectures, the role of software–and the middleware that connects it all–is rapidly growing. Unlike passenger cars, the CV sector moves at a different pace.
Speaking to MOTORINDIA, Mr. Christoph Herzig, Managing Director and Chief Commercial Officer of Elektrobit Automotive GmbH, explained that CV platforms operate on longer lifecycles and lower volumes, which means development takes time but allows for monetisation over many years. “Uptime guarantees and lifecycle management are already built into the CV business model,” he said, adding that this makes the segment naturally suited for software-defined vehicles (SDVs).
Yet progress is not linear. Many ambitious SDV projects in the CV world have faced delays or restarts as companies balance investment with long-term viability. One striking example is Volvo Trucks and Daimler Trucks joining forces in Sweden to develop a shared SDV platform–two rivals uniting to manage costs and accelerate innovation, he pointed out.
Mr. Herzig noted that while CV makers are embracing collaboration, passenger vehicle OEMs still largely pursue isolated approaches. “Eventually,” he said, “stronger standardisation will be essential for making the SDV vision a sustainable reality.”
Middleware: The Unseen Nerve Centre
Middleware is often called the hidden backbone of modern vehicle architecture. It must work across all segments, guided purely by performance, safety, and security–not by function. As multiple domains converge on a single high-performance computer (HPC), middleware ensures seamless communication and system behaviour.
“Today’s vehicles still carry “Frankenstein” architectures–mixing old and new systems without a unified middleware. For true SDVs, this layer must be standardised to expose deeper system functions consistently, regardless of network or vehicle type,” Mr. Herzig said.
When it comes to split-second operations like braking or ADAS, performance cannot falter. Instead of relying on costly redundant hardware, software must dynamically balance workloads to maintain real-time response and safety. This is achieved by managing latency and guaranteeing execution at the chip level.
Mr. Herzig explained that this is where specialised software vendors make the difference–offering certified functional safety that open-source solutions alone can’t guarantee. While open-source fosters collaboration and strengthens cybersecurity, functional safety demands accountability. “You can’t get safety for free. It requires a commitment–and that’s what truly defines trusted automotive software,” he noted.
Balancing Innovation, Safety, and Speed
Joining the conversation, Mr. Sai Sridhar, Managing Director of Elektrobit India, said, for modern vehicles, innovation can’t come at the cost of safety or cybersecurity. Meeting strict standards such as ISO 26262 and UNECE WP.29 demands both speed and precision. He explained that innovation must be built right from hardware–software pairing. By carefully architecting software across real-time microcontrollers and high-performance chips, OEMs can host both safety-critical ADAS and infotainment functions on the same platform–securely and efficiently. The goal, he said, is not to limit innovation but to channel it smartly so that upgrades and patches meet all safety and security norms.
Mr. Herzig pitched in stating that this shift is also reshaping the supply chain. Traditional Tier-1s now face new competition from full-stack system providers like Mobileye, which powers Level-4 robotaxis for Volkswagen’s commercial fleet in Germany. For higher-level autonomy, commercial operators–not OEMs–are taking the lead, as they can better manage maintenance, liability, and lifecycle needs.
To handle diverse software needs, Elektrobit enables dual update streams–frequent OTA updates for infotainment and tightly controlled updates for safety-critical systems like ADAS or braking. “You don’t update a brake every week. You refine how it feels, not how it stops,” Mr. Herzig noted. This multi-domain, software-defined approach allows OEMs to innovate faster while maintaining safety and reliability across every level of automation.
Making Machines Speak the same Language
With hundreds of sensors, ECUs, and software layers in today’s vehicles, smooth communication is a challenge. The answer, said Mr. Herzig, lies in “semantic APIs” – standardised interfaces that let all systems, from ADAS to infotainment, talk to each other seamlessly. By defining a single semantic API across functions, OEMs can enable secure, cross-vehicle communication and make features like 360° cameras or facial recognition work across multiple applications. But this only works if designed end-to-end, without shortcuts or incompatible updates that break the chain.
As systems grow complex, testing must evolve too. Mr. Herzig stressed that quality must be built early in the software lifecycle–testing alone can’t catch every issue. Automated checks, semantic code validation, and architecture-aware testing are now essential to prevent costly late-stage errors.
Mr. Sridhar added that “shift-left” testing is changing the game. Through virtualisation, developers can now simulate real-time scenarios–like braking–on laptops even before the hardware is ready. This approach saves time, cuts costs, and ensures safety is validated early, keeping innovation both fast and reliable.
Shaping the Software Backbone of Future Vehicles
What was once hidden inside vehicles is now driving the entire automotive transformation. Mr. Herzig explained that software–once limited to individual ECUs–is becoming the foundation for a unified, long-term vehicle experience. “It’s no longer about one control unit doing one job. Now, software defines how functions move across the entire architecture,” he said.
Elektrobit’s opportunity lies in this flexibility. Its middleware and operating systems allow automakers to decide where and how each function runs–across zonal controllers, gateways, or high-performance computers. This enables platforms to evolve across generations, supporting everything from affordable EVs to luxury SUVs, all built on the same digital foundation.
The convergence of traditional CAN/LIN networks with high-speed Ethernet is making this seamless communication possible. Elektrobit’s solutions bridge these worlds, letting OEMs reuse components, upgrade functions, and future-proof their platforms. In Mr. Herzig’s words, “It’s not about the constraints of today–it’s about building a platform that keeps evolving.”
AI: The Next Enabler in Middleware development
Mr. Herzig believes AI is set to play a powerful, though focused, role in the evolution of automotive middleware. Its real strength lies in testing, validation, and code quality–helping engineers understand how a small software change might ripple through an entire vehicle system. AI can map complex architectures, identify critical control points, and predict potential issues faster than traditional methods.
However, he cautioned that AI isn’t ready to create industry standards or design complete architectures on its own. “Today’s models connect what already exists. The truly creative and consistent management of system architecture will still rest with humans–at least for now,” he concluded.