Guest blog: Software-defined vehicles are here

Future vehicles will have fewer that fifty ECUs and a high-speed Ethernet backbone

Jack Weast from Intel believes an open architecture offers flexibility and choice

I grew up in a car family. And when I say car family, I mean a CAR family. The running joke was we had to have more individual cars than years my parents were married. And they’ve kept that streak alive for nearly fifty years.

We’ve had Alfas (lots of Alfas), Corvettes, Chryslers, Fiats, a Renault (Le Car!), BMWs, MGs and MBGs, Cadillacs, Chevys, Maseratis, Ferraris, Jeeps, a Dodge Ram van and truck, Hondas, and so many more I can’t even remember.

But times are changing. My folks will inevitably slow their roll in vehicle acquisition as they get beyond a safe driving age. And we are unavoidably at the end of an era in the automotive industry.

The automotive industry is facing a perfect storm of unprecedented change: the transition to electric, the advent of pervasive connectivity, the evolution of cloud-to-edge architectures, and a market disruption with the addition of the most new car makers now than in over fifty years.

As Andy Grove said, “only the paranoid survive”, and now is the time to be ultra paranoid. We are facing a true iPhone moment in the automotive industry. Those who embrace change and shed legacy mindsets while advancing their processes to reflect the pace of change in the IT industry will survive.

For my entire lifetime, and even that of my parents, the modern car really hasn’t changed much. Sure, engines have gotten more powerful and more efficient. Cars are safer in crashes. Lights are now all LEDs. But, for the most part, the foundational architecture of the modern vehicle hasn’t changed since my dad started driving in the early 1960s.

A pattern that started then and has continued until today has led to modern vehicles that contain over a mile (1.6km) of copper cabling to connect over 100 individual electronic control units (ECUs), each of which delivers a single feature or function of the vehicle. Seat heaters? New ECU. Aircon? New ECU. Electric windows? New ECU. Every function in the modern vehicle that has been added piecemeal, one by one, has led to a vehicle architecture that today, in the 21st century, is technically and economically unsustainable.

In the IT industry, we long ago moved away from embedded single-function devices and migrated to modern, high-performance computing systems where multiple functions and workloads run on a single, centralised system because of the amazing possibilities of software. There are significant cost and performance efficiency benefits. And since modern software-defined high-performance systems were introduced in the IT industry more than twenty years ago, IT and other industries who have embraced them have never looked back.

So, change is hard and only the paranoid survive. What should an automaker do? How should they know the right partner to help them with this transition?

You can’t just pay lip service to a software-defined architecture and then keep your customers locked into proprietary architectures and APIs. That’s not how it worked in the IT industry and that won’t work in automotive. Software-defined inherently means open architectures and open APIs that allow for re-use and interoperability across silicon vendors and from car to cloud.

 

Jack Weast, an Intel Fellow, is vice president and general manager of Intel Automotive

 

www.intel.com

Recommend to Colleagues: