Integrate the automotive software stack to improve connected vehicles

Bypass roadblocks in the evolving automotive OS landscape

Technology continues to propel the automotive industry forward. We only need to look around us to notice that the cars on our roads are increasingly hybrid or electric. They will also be predominantly connected: by 2030, connected vehicles are predicted to account for 95 percent of new-vehicle sales globally.

Consumers want connected vehicles and their extensive features, and it is easy to understand why. Just as the smartphone transformed how we use our mobile devices, software-defined vehicles will have the same impact; they will forever change the driving experience via personalization, convenience, and autonomy.

Car manufacturers are working to meet this growing demand, but the transition from a mechanical-native to a software-native frameworks is a potential roadblock – one many OEMs will have to bypass before they can effectively create the vehicles consumers want today and in the years ahead.

While building cars with modern software has enabled useful features like GPS navigation and voice assistants, it has also created silos in the architecture. Navigation, security, and user-interface systems all have their own software building blocks and layers, which together create a stack like that of any tech product.

The operating system (OS) is the foundational layer, where the automotive software and computing platform lies. This is the system that communicates with the cloud, infrastructure, and external devices to perform essential functions underlying the vehicle. Integration here is vital to ensure the platform runs reliably and smoothly. Otherwise, critical safety systems, like ABS and collision avoidance, may lack speed and precision, putting the driver at serious risk. And this is just one example of what could go wrong.

OEMs are recognizing the importance of investing significantly in this area. However, the automotive OS landscape itself is quickly evolving. Determining the best approach among so many options is a serious challenge.

OEMs are recognizing the importance of investing significantly in this area. However, the automotive OS landscape itself is quickly evolving. Determining the best approach among so many options is a serious challenge.

QNX and Android systems are mainstays among many automakers that have opted for a track record of reliability. Many OEMs have gravitated towards Android and its open-source architecture for its philosophy of transparency and collaboration. It also facilitates full customization and flexibility – just like on smartphones – allowing OEMs to not be beholden to any company and maintain control over the system.

Some players are even joining forces to differentiate their offerings from the rest. For example, BlackBerry and Amazon Web Services have partnered to develop BlackBerry IVY, an AI platform for automotive built for improving the in-vehicle experience while preserving security and safety. IVY was designed with a specific focus on accelerating the journey to the software-defined vehicle.

All this shows the changing dynamic in the industry around car operating systems as it moves towards its software-defined vehicle future. Capgemini is fully plugged in to this transformation. Our combined engineering, cloud, and telecommunications capabilities mean we are positioned to help automotive companies take the right approach for integrating the entire automotive software stack, starting with the OS.

I would be happy to hear from you about the moves your company has been making. Let’s discuss the evolving car OS ecosystem and its role in shaping the connected vehicles of the future.