Sehr interessanter Artikel über den ersten MVP für die neue Softwarearchitektur von CARIAD. Lesenswert!
CARIAD’s new MVP (Minimum Viable Product) represents the very first real-life, functional network of our E3 2.0 architecture. Running across several evaluation boards, with VW.OS. and a connection to VW.AC, it’s a true representation of the capabilities of our software platform and allows for the development of vehicle functions.
Developers at CARIAD have been working on the foundations for the E³ 2.0 program over the last one and a half years, and on the MVP itself since May. Earlier this year, we consolidated various different vehicle functions across the Volkswagen Group brands and identified the key use cases that we wanted to test. After conducting a number of POCs (proofs of concept), the project became a consolidated effort and took the form of the physical MVP, comprised of various evaluation boards and ECUs (electronic control units) from the target architecture. The MVP also features a selection of sensors and actors.
The development of the MVP involved all domains across CARIAD and the entire Solution Train 2.0 – with colleagues not only from all across Germany, but also in Seattle and India. The project was developed iteratively with an agile development procedure and methodology, and new increments every three months. The recent finalization of the MVP then took place over the past couple of weeks with a team on site at the IN Campus in Ingolstadt, as well as colleagues working remotely. During this time, the team carried out final debugs of the whole network and tested the last parts of functions, focusing on every part and integrated use case.
Use case: Climate control
In developing the climate control use case, the goal was to have a realistic, customer-facing feature. Though seemingly simple from a customer point of view, it actually makes use of virtually every part of the hardware topology, as well as VW.OS and VW.AC. With remote functionality, it shows how the temperature in the vehicle can be controlled from wherever you are – whether that’s right next to the car or 100 kilometers away.
The use case begins with the Volkswagen WeConnect ID smartphone app, where the user can adjust the temperature in the vehicle (or, in this case, on the MVP). The signal is then sent from the SIM card in the phone to the cloud, where the information about the chosen temperature is processed. The processed signal returns from the cloud and, through the antenna, reaches the first ECU on the board. From there, the signal travels through the event chain, through various ECUs in the E³ 2.0 architecture and to the sensors and actuator layer. At this point, the rotation speed of the fan increases and a control panel with a display shows the new temperature, confirming that the temperature has in fact increased.
Use case: OTA
Another of the first features to be included on the first release of the 2.0 platform is OTA. With the MVP setup, we have one platform for over-the-air updates, and capabilities can be updated right from the start. CARIAD developers can push software to our backend platform and deploy any release they would like to the platform. In developing the OTA use case for the MVP, our developers were able to analyze and learn from our performance from earlier platforms, including the over-the-air update functionality currently available on software platform 1.1 in the Volkswagen ID.3 and ID.4.
The MVP and new vehicle platform allow us to deploy smaller, more incremental updates more often. Not only can we update individual applications, but also the whole VW.OS stack underneath it. Over-the-air updates are key to driving the Volkswagen Group’s vision and strategy to becoming a software-driven mobility provider. In this way, CARIAD will be able to bring updates to vehicles that are not only more frequent, but also more robust and more reliable.