top of page
arnoldkwong7

Mercedes-Benz OS Strategy Continued 3

Timing of the development process MMA and MB.OS will share are also under the control of a management attitude. Mercedes has announced:


” We are the full architects of the stack. That doesn’t mean we need to program every line of code. It doesn’t make technological sense, and it doesn’t make economic sense…” [Kallenius, 2023]


Kallenius has also described a ‘typical’ infotainment update via configuration control management and engineering processes requiring nine months to conduct. Use features of MMA/MB.OS architecture and implementation, an expectation is for an immediate OTA download for a change.


The migration for business processes as complex as vehicle infotainment, ADAS, and platform operations from today’s extremely limited version to the needs of future Mercedes businesses – from concept to long-tail revenue – will require significant management time and immersion.


Technology (controlled and delivered by enterprise partners) and process decisions will drive needed levels of investment. Independent of the investment level will be achieving the process results desired. The scale required for this investment can be seen at Tesla, Argo, and Cariad. The expensive race to produce ADAS software, vehicle sensors, and energy management at economic price points, and the accompanying eco-systems where a single vehicle is an extension of a network.


The next post in the series will explore the concept that money can’t buy everything when it comes to advancing a next-generation vehicle OS strategy.


You’ll find that and other interesting articles at www.ekalore.com/alien-invaders

Comments


bottom of page