Why ETAS for the Software-defined Vehicle

Share This Article

ETAS for Software Defined Vehicle SDV

We’ve shared our updated logo and brand architecture, thoughts on the software-defined vehicle and a commitment to help realize the future software-defined vehicle. But how does it all fit together?

Let’s take a quick look back at last year. Robert Bosch, the parent company of ETAS, consolidated the development of its universal vehicle software within ETAS. This activity merged the knowledge and experience of approximately 2,300 associates under the ETAS brand to develop and sell basic vehicle software, middleware, cloud services and development tools.

As a result, ETAS became positioned as a leading provider of application-independent software for vehicles and the cloud. This strengthened position in software development enables us to address market demands for the software-defined vehicle – one of the biggest transformations in the automotive industry’s history.

We do this by delivering a comprehensive end-to-end software-defined vehicle portfolio, comprising the required in-vehicle software stack, holistic cybersecurity and cloud-based operations services. All this enables fast and data-driven development, efficient deployment and management, as well as safe and secure operation of vehicle software at scale.

Our central platform of application-independent software for vehicles and the cloud will allow for quicker and more efficient development of software with partners. The industry – OEMs, suppliers and consumers – expect fast progress, so consolidating the complexity of software development into a single source will enable the speed, scale and security to achieve aggressive development timelines.  Without the middleman, ETAS allows for direct deployment and efficiently scaled systems.

These systems need to be safe and secure. As vehicles become increasingly more automated and connected, the risk of cyberattacks grows. That’s why our systems benefit from seamless, holistic cybersecurity solutions (previously provided under the ESCRYPT brand) built specifically for vehicles.

Those are the ETAS pieces to the software-defined vehicle puzzle. But what about the software-defined vehicle itself – what pieces does it bring to the puzzle?