Automotive operating systems |
Automotive via CNN Money and C | Net to the same news from the Daily Yomiuri detailing the formation of a consortium of Japanese companies and institutions (Toyota, Nissan, Honda, Toshiba, Denso and the Ministry of Industry, Commerce and Energy, among others) In order to develop an operating system for use in automotive. The system is currently called JasPar, and the objective would be to have a functional prototype in 2009.
Following a little more news, I find that 70% of the market for automotive operating systems is in the hands of OSEK / VDX, A German-French consortium formed by the union of the developments of OSEK ("Offene Systeme und deren Schnittstellen für die Elektronik im Kraftfahrzeug", originally composed of BMW, Bosch, DaimlerChrysler, Opel, Siemens, VW and the University of Karlsruhe as coordinator; And VDX ("Vehicle Distributed eXecutive"), coming from the French automotive industry, specifically PSA and Renault.
It is estimated that electronic components and software already account for around 20% of the cost of an average car, a percentage that reaches 50% in hybrid cars. In the eighties, the number of electronic systems installed in the average car remained stable around five, while at present it is about thirty in average, with some luxury models that exceed one hundred. Such demand is provoking the interest not only of the aforementioned consortiums from the industry but also of technology companies such as IBM or Microsoft.
The evolution of this type of operating system could have enormous consequences for the establishment of communication standards that would largely avoid the escalation of such costs through joint research, as well as a strong impact on the aftermarket service market. At present, brands jealously protect their electronics for competitive and security reasons, which entails enormous difficulties for the workshops and for the development of compatible parts and products, but in certain parts of the industry it is beginning to advocate the convenience of Towards open-type developments.
0 comentarios: