Three weeks after the dramatic announcement from Nokia of its partnership with Microsoft and a shift to Windows Phone 7 as the preferred OS platform for its mobile phone business, kinder gentler thoughts in the marketplace regarding the prospects for the partnership are beginning to prevail. Having regrouped to put its own spin on recent events the head of Nokia’s automotive team recently pointed out the advantages of the Microsoft partnership in support of Terminal Mode and ongoing activity within the Qt developer community in support of both MeeGo and Symbian.

 

While it is true MeeGo has been significantly de-emphasized and Symbian will be phased out – after 150M more Symbian phones are shipped – Nokia Navteq remains an active player in the automotive marketplace focusing on opportunities for mobile phone connectivity and navigation. Post-partnership the combined organizations, while separate, represent a force to be reckoned with. The powerful search platform of Bing along with Navteq’s maps and Ovi’s marketplace represent a triple threat in a market where mobile advertising and mobile commerce are rapidly emerging around the world in cars and on devices.

 

The challenges facing the Microsoft-Nokia Navteq partnership are significant. The Windows Phone 7 platform is just four months into a slow start in the market and Microsoft has not defined a clear synergistic connection between Windows Phone 7 and Windows Embedded for Automotive 7. Microsoft can point to several successful mobile phone connectivity partnerships in the automotive market – such as Fiat, Kia and Ford – but most of these are built around different versions of Windows Auto or Windows CE.

 

Microsoft can also point to head unit partnerships with Mitsubishi Electric, Clarion and Alpine in support of Mercedes and Nissan. In fact, Alpine and Clarion have already endorsed and adopted terminal mode for enabling smart phone connectivity to access maps, music and for enabling map-based safety applications. While no one in the industry expects Apple to endorse and deploy terminal mode connectivity, makers of Android-based handsets and RIM may find it prudent to make terminal mode technology available.

 

Helping to make terminal mode connectivity more attractive, Nokia Navteq is stepping up its Ovi Marketplace game adding search now powered by Bing along with Navteq’s mapping, graphics, turn-by-turn navigation, geo-coding and reverse geo-coding to facilitate local commerce opportunities around the world. Created in conjunction with the CE4A industry consortium, terminal mode has been demonstrated by Volkswagen engineers – reflecting the company’s strong ties to German car makers. Nokia is looking to build on its Japan market inroads with a (now cancelled) Terminal Mode Summit in Tokyo late in March where the official Terminal Mode trademark will be launched (http://www.terminalmode.org/en/Events/registration) along with release 1.1 and a future release roadmap.

 

Almost lost in the Microsoft Nokia Navteq announcement was the impact on the Qt developer community and the de-emphasis of MeeGo. Qt and MeeGo continue to go hand and hand in the open source developer world and MeeGo continues to boast support from Intel and the now-fairly-large GenIVI Alliance (which will be gathering in Dublin in May). As car makers look to deploy application stores to support embedded solutions expect the GenIVI Alliance to strongly advocate for MeeGo as the ideal OS platform choice.

 

MeeGo stacks up as a strong alternative to Android or iOS for in-vehicle app stores. While Windows Embedded for Automotive and QNX are candidates, MeeGo’s candidacy is made stronger for being a cross-carmaker open development platform. And Qt is something of a wild card for MeeGo as a source of developer support.

 

Support for MeeGo has been years in the making. The Microsoft-Nokia announcement was not greeted warmly by Intel executives and received with some dismay by GenIVI members. Intel eventually announced its intentions to forge ahead undaunted in multiple device markets – including automotive. A week after the announcement, the MeeGo element of the announcement has been relegated to a sidelight with no impact on MeeGo’s or GenIVI’s longterm objectives.

 

In the end, Microsoft and Nokia Navteq are in position to have a significant influence over automotive infotainment systems, mobile device integration and in vehicle content/service/application delivery and mobile commerce. Now it is up to the two organizations to prove out the on-paper value proposition in the marketplace.

 

Additional Insight:

 

http://bit.ly/dLXz1v - Terminal Mode at Forefront of Connectivity, Competition Closing in - Insight - Roger C. Lanctot - Automotive Multimedia & Communications Service

Next week American Honda Motors will introduce its 2011 Odyssey at the Los Angeles Auto Show. The car comes equipped with what the company calls FM Traffic. This seemingly innocuous announcement marks a shift in the industry with wide ranging implications for both automotive radio and on-board traffic information.

Auto makers are confronting major decisions regarding content delivery to the car and the configuration of the center stack. The battle lines for content delivery divide over the question of embedding a telecommunications module or connecting the driver’s smartphone. Smartphone connectivity shifts the data plan burden onto the driver, while embedding allows wider latitude for vehicle data collection by the OEM.

The radio is the beating heart of the center stack and here a struggle is unfolding between and among traditional AM/FM technology, HD Radio, satellite radio and Internet radio. The battlelines are drawn over content delivery, personalization, localization, monetization and flexibility. Honda’s FM Traffic is based on RDS-TMC, a free (to the consumer) traffic data service delivered over the FM sideband. RDS-TMC represents the state of the art in North America for delivering accurate and timely information on traffic conditions. The Honda solution is unique in that it is supplied by the Broadcast Traffic Consortium (BTC), a nationwide group of broadcasters allied with Navteq.

The industry will have to wait until next week to see how Honda has implemented incident and flow messages, but it is likely that Honda and its supplier, Alpine, have added value to the traffic reporting proposition (http://automobiles.honda.com/traffic/). Alpine will also be bringing the BTC RDS-TMC solution to its aftermarket products. Honda is only the second North American OEM to deploy RDS-TMC from BTC, following Mercedes-Benz. More are expected.

The dominant RDS-TMC supplier in North America is Clear Channel, which is partnered with Inrix. The Clear Channel solution is offered by BMW, Volvo, Mazda and a few other OEMs. Honda’s decision is significant given that the company also offers Sirius XM’s NavTraffic service, which requires a monthly subscription. But Honda’s choice reflects several hard truths for the industry:

Truth #1 – The value of traffic data is declining. Once valued at $1/user/month, traffic data has declined in value to 25 cents/user/month or less at the supplier level. For the consumer, traffic information is perceived as free – especially since so much of it is readily available over radio and television broadcast sources as well as from Depts. of Transportation via the Internet. RDS-TMC traffic information is also free (to the consumer) and, therefore, fits this model and mindset.

Truth #2 – RDS-TMC traffic data is better than good enough. Anyone who has used RDS-TMC-equipped navigation systems in a heavy traffic corridor can attest to its accuracy and reliability. Satellite radio traffic information, by comparison, is not competitive – based on this analyst’s experiences. (Some European RDS-TMC data, Germany in particular, is the exception to this.)

Truth #3 – Traffic information services continue to evolve and improve and service providers must evolve along with them. While HD Radio deployment of TPEG traffic data services will be the next step, it will be followed quickly by solutions based on smartphone integration and, ultimately, embedded traffic data platforms that provide for Internet connectivity. All of this is bad news for Sirius XM. The company is already wrestling two alligators – a transition of existing Sirius users to XM service by 2016 (see http://bit.ly/bIWHJ6) and the introduction of Satellite Radio 2.0 in Q4 2011 (see http://bit.ly/bqiU7F).

While managing these two processes, the company is also justifying its existence on a quarterly basis before its investors as a public company.   Traffic data services are key to Sirius XM because they represent the most successful telematics service the company has been able to deliver. Unfortunately, because of the capacity limitations (traffic data for all cities must be delivered down a single connection leading to data being left out due to capacity limitations or delayed due to the carousel-like data transmission) and one-way nature of the satellite pipe, Sirius XM traffic is poor.  

In fact, Sirius XM traffic, based as it is on Navteq’s Traffic.com, has given Navteq’s data service a bad reputation – through no fault of Navteq’s. (This is not to be confused with the city-by-city audio traffic broadcasts provided by Metro Traffic.) Honda’s selection of BTC RDS-TMC is a shot in the arm for Navteq’s traffic team which is looking to bounce back from its reliance on Sirius XM.  The subscriber volume for satellite traffic has been poor as a result of the poor data. Some OEMs do not even offer satellite traffic for their satellite radio systems. This points to a wider problem for satellite radio. The company has yet to find a successful model for branching out beyond talk and music.  

Both Sirius TV (Chrysler) and TravelLink (Ford) are seen in the industry as failed services due to low subscriber volumes. Of course, the business models were also flawed. Sirius TV only offered three channels of rearseat entertainment, a fatal limitation, and most of the TravelLink services – for parking or inexpensive gas – are available on smartphone apps.  Now Sirius XM is setting the stage for Satellite Radio 2.0. In a report to LibertyMedia shareholders last month, CEO Mel Karmazin tipped his hand a bit by referencing the possibility of transmitting local movie times and/or red-light camera info to drivers via satellite radio. He also mentioned enhanced time-shifting technology, presumably from storing or buffering some satellite content.  Other reports regarding Satellite Radio 2.0 suggest more sophisticated search functions for finding particular artists or songs that may be playing at any given time across the voluminous satellite radio dial. Some industry sources say SR 2.0 is expected to have 25% more capacity. It’s not clear whether any of these SR 2.0 possibilities are true, possible or even compelling to future subscribers. 

But Karmazin has a compelling story for investors. He told them last month that OEM penetration of satellite radio as a percentage of new cars was 60% and that the number of satellite radio factory-enabled vehicles in operation in North America was approximately 30M and on a path to hit 80M by 2015. For this reason, the company is continuing to promote certified preowned vehicle programs for satellite radio re-activation – which is seen as a key to future growth.  Karmazin further notes that Sirius XM has some of the lowest subscriber churn in the media landscape (1.8%), has one of the largest subscriber bases (19.5M, second only to Comcast), and now captures 15% of overall radio revenue ($2.8B) vs. $15B for terrestrial radio, and ~$1B for Internet radio/music services. He also notes that satellite radio’s subscriber revenue is $2.8B vs. ~$300M for Internet radio which translates to per subscriber revenue (annual 2009 est.) of $136 vs. $1.25/user for Internet radio and $10-$20/listener for terrestrial radio. 

Conclusions  It’s worth noting that Karmazin made no reference to either HD Radio or to Sirius XM’s stated transition to XM by 2016. While the present looks promising for Sirius XM in the form of rising vehicle sales and the launch of new certified pre-owned vehicle programs, the long-term outlook is less rosy.  The wider deployment of competing and free traffic services should put the last nail in the coffin of Sirius XM’s telematics ambitions. Embedded telematics services and smartphone connectivity, combined with FM- and HD Radio-based solutions, will obviate the need for any Sirius XM data services.  A new front end to Sirius XM’s audio content will provide a short-term lift in allowing for easier access to specific types of music. And premium sports and personality content remain a demand wild card and, combined with nationwide reception, preserve the satellite value proposition.   But car makers are still not likely to integrate satellite radio into the core of their center stack platforms, meaning satellite radio will remain an add-on, particularly given ongoing system upgrades. In a matter of years, cars will be shifting to Internet connected solutions allowing for personalization and location awareness, two propositions with which satellite radio cannot compete. Additional insights: http://bit.ly/dniNxa - Navigation Heuristic Evaluation: Telmap5 – Schreiner – Automotive Consumer Insights http://bit.ly/95NCoW - Automotive DMB Digital Radio: Marketing Strategies an Increasing Priority – Blight – Automotive Multimedia and Communications Service http://bit.ly/dtRE5C - Automotive Telematics Services: Shifts in Pricing and Monetization Expected – Canali – Automotive Multimedia and Communications Service http://bit.ly/bwdwcW - Connected Vehicle and Vehicle Device Connectivity System Database by Feature, Region, and Price 2010 – Canali – Automotive Multimedia and Communications Service http://bit.ly/d0aLhq - Connected Vehicle Telematics: Car Maker Profiles – Canali – Aumotive Multimedia and Communications Service http://bit.ly/deumcd -# Traffic Data Quality Will Determine #Telematics Winners - Lanctot - blog - Strategy Analytics

Microsoft intends to clear the air at Convergence in Detroit this week with the launch of Windows Embedded Automotive 7.0, the merged automotive operating system that takes the place of MS Auto and Windows Automotive – in all their versions. An earlier version of the OS, Windows Embedded Automotive, will be featured in the information hub in Nissan’s Leaf electric vehicle, according to Microsoft, and will be joined in the spotlight by Silverlight for Windows Embedded, Microsoft’s alternative to Flash. Also highlighted at Convergence by Microsoft will be Fiat’s plans to bring the Fiat 500 to the U.S. along with its Blue&Me 2.0 (not it's official name) interface with support for the iPod. Ford and Kia will likely be making announcements related to their Microsoft implementations and Microsoft noted its participation in 12 different device platforms over the next 12 months from a number of different car makers reflecting the company’s continuing commitment to the automotive business. The announcements and enhanced presence at Convergence concludes multiple reorganizations at Microsoft which saw the departures of senior executives on the automotive team and a consolidation of all embedded activities under a Server and Tools group. Existing OEM and Tier One partners with Microsoft solutions include Ford, Fiat, Chrysler, Kia, Mercedes, Honda, Nissan, Alpine, Mitsubishi, and Clarion. Microsoft will use Convergence to demonstrate various Silverlight development tools for handling prototyping and to accelerate testing within the development and approval process while allowing OEMs to create executable specifications for suppliers. Tools will also be shown for a thread priority-based tuning system that allows for handling and logging errors during development. Microsoft will also highlight advances in its Tellme embedded speech product, currently being deployed by Kia in the Uvo. The new recognizer can handle eight languages with speaker independence while providing for the tuning of recognition for individual users. Also new for the embedded Tellme is an SMS reply function capable of performing fuzzy logic matches to a set of predetermined responses. Separate from the Convergence activities, Microsoft is pursuing automotive opportunities for its Bing search engine as well as for Tellme as a server-based voice recognizer. Both the Ford and Fiat Microsoft solutions provide for application downloads and updates, though Microsoft has not created its own automotive app store model. The Nissan Leaf information hub is the most significant of the announcements at Convergence. The hub will handle navigation, charging, radio and HVAC functionality in the car. The hub implementation suggests the potential for a wider Microsoft engagement with both Nissan and Clarion. As Nissan moves closer to realizing its connected vehicle vision outside of Japan, the company can be expected to move beyond its current reliance on VxWorks. Conclusion: Microsoft remains a credible alternative to QNX and the various versions of Linux distributions in the automotive industry. The MeeGo operating system created from the merged elements of Nokia’s Maemo and Intel’s Moblin platforms and adopted by the Genivi Alliance is not expected to be available in even a beta version until April 2011. Some Genivi members say an automotive version of the OS may be out before the end of the year. Google and its Android operating system continue to flirt with the automotive industry – playing hard to get. Google is interested in the automotive industry for the emerging search-related opportunities and for the potential to sell traffic and cloud-based location-aware applications, but the company still refuses to certify or support Android for embedded use. In spite of Android’s orphaned status in automotive, Continental and Parrot continue to carry the flag, secure in the knowledge that Android can still claim the largest and fastest growing developer community – key to unlocking app store opportunities. Microsoft’s step by step, implementation by implementation, customer-focused approach has left some customers and potential customers scratching their heads about the company’s long-term commitment to automotive. The headquarters reorganizations continue to raise questions, and yet Microsoft forges on, enhancing and refining its solutions and adding to its portfolio. Just the past year has seen Silverlight and Bing added to the mix along with Tellme. After years of wavering it appears that Microsoft has finally taken its vows and accepted its automotive market responsibilities. By now, the company has learned that the automotive contest is not always won by the swiftest, but by the supplier with the most staying power – and it looks like MS is in for the long haul. Further insight: Smartphone Market Evolution and the Automotive Opportunity Implications – Mark Fitzgerald – Automotive Multimedia and Communications Service - http://tinyurl.com/34hldb5 Automotive Connectivity: Beyond Bluetooth Solutions – Mark Fitzgerald – Automotive Multimedia and Communications Service - http://tinyurl.com/2gx88eo

The latest salvo from the Genivi Alliance – a SWOT analysis of competing automotive operating systems – appears to cloud rather than clarify the existing automotive OS market environment. The future prospects for current and emerging players are described with little supporting evidence or insight. The report also concludes – from OEM and supplier interviews – that the Alliance’s assumptions regarding cost savings are valid without providing a detailed financial analysis of where cost savings may be achieved – ie. head count, lines of code, etc. Not surprisingly, the self-serving report concludes that Genivi will rule the market in the long term with deployments beginning in the 2013-2015 timeframe (http://tinyurl.com/29aly2t). The report initially sets out to provide a thumbnail view of current OS market leaders Microsoft, QNX, MicroItron, Linux and Android. Going without mention are Mentor Graphics, Ubuntu, OpenSynergy, Meego or even VxWorks (currently used by Peugeot-Citroen, Nissan and Volkswagen). Also missing entirely are Genivi members MontaVista and Wind River. Ostensibly, the goal of the report is to benchmark and/or handicap these various infotainment software architectures and their influence on in-vehicle infotainment systems; and to validate the cost savings claimed for Genivi’s code-sharing/recycling model. Missing is a detailed description of the actual software architectures themselves – ie. what makes one “better” than another. What is available in the report summary seems misleading such as a reference to Microsoft Auto booting slowly, which is also a shortcoming of Android, but which is also easily overcome. Also missing is a discussion of current market forces, strategic supplier relationships, recent mergers and acquisitions or potential mergers or acquisitions. The absence of these latter aspects means that Intel’s acquisition of Wind River goes without mention as does the merger of Intel’s Moblin platform with Nokia’s Maemo OS to create Meego – rumored to have been selected by Genivi as its infotainment platform of choice. (Press and Nokia reports have quoted senior Genivi representatives stating that Meego has been chosen for this purpose - http://tinyurl.com/2d46xls. No affirmation of this selection has come from any Genivi member other than BMW.) MontaVista’s acquisition by Cavium Networks and QNX’s purchase by RIM gets no attention in the report. Neither does TomTom’s decision to adopt the Webkit OS, a platform found in other segments of the mobile market such as Palm’s Web OS. (The report fails to note Bosch’s adoption of Linux or Visteon’s embrace of Genivi, Microsoft, QNX AND Ubuntu – hedging its bets.) These oversights are more significant than they seem as they suggest a lack of awareness of the symbiosis between mobile device operating systems and automotive hardware and software architectures. Additionally, the report repeatedly refers to “risk-averse” Japanese OEMs and tier one’s being hesitant to adopt open, Linux-based platforms – including anything from Genivi to Android.  This assertion is patently absurd given Clarion’s longstanding support of Linux. The report also paints a grim picture of QNX’s market outlook, suggesting the company’s app support is “difficult to configure” and that the company can be expected to withdraw from the IVI market entirely within a short period of time. This will no doubt be news to executives at QNX’s Ottawa headquarters where headcount committed to automotive projects is on the rise as are design wins. And the acquisition of QNX by RIM opens doors to automotive-related IP (ie. traffic apps) while adding access to a massive and growing installed base (ie. probes). Unlike all of the alternatives currently in the market, QNX currently offers a range of flexible, scalable solutions future proofed to support Adobe Flash, HTML5, Flash Air and Flash 10.1 and all mobile OS's. QNX is customer friendly with support unmatched by Linux-based competitors or Microsoft. By way of contrast, OEMs implementing Microsoft are finding they must enlist the aid of third-party developers (bSquare, Elektrobit, etc.) to customize Microsoft Auto to their requirements. Microsoft has left application development entirely to its customers and their partners. It is worth noting as well that QNX’s flexibility is an advantage vis-à-vis Microsoft. Where QNX supports nearly every potential application or implementation known to automotive engineers without favor, Microsoft is likely to push its Bing search engine, Silverlight graphics and other in-house offerings. The report notes that the next generation Microsoft IVI platform, Motegi (Windows Automotive Embedded 7), will launch with Japanese OEMs, though it provides no time frame. Microsoft indeed has at least two partners in Japan – Alpine and Mitsubishi – which suggests that either Honda or Mercedes may be implementing Motegi. The report neglects to mention QNX’s recent gains in Japan, including Panasonic and Denso, showing a deeper penetration of QNX into Toyota. In fact, QNX has benefitted handsomely and rapidly from its separation from Harman – immediately attracting attention from potential Japanese and Chinese customers. Where QNX is weakest is in developer support. This is precisely where Android shines. The report summary correctly identifies existing developers working on automotive Linux implementations – ie. Parrot, Continental and Roewe – and identifies the inclination of many designers in the industry to connect with Android but to keep it out of the central stack. The report also notes Google’s disinclination to support or endorse Android for automotive implementations, but leaves the door open to an embedded future for Android. (GM is thought to be considering an open platform such as Meego or Android for a future OnStar or infotainment launch.) But this points up a fundamental gap in the report, which is the wider context of the OS debate. Android and Genivi do not line up directly with QNX, Microsoft or Linux (pick your distribution). Genivi has always been positioned as a code sharing platform for infotainment systems - as such it has never been presented as a replacement for Microsoft or QNX. Android, similarly, is being pursued as an alternative for ultra-low-cost (entry level) platforms - typically those emanating from India and China - as well as a means for implementing revenue sharing models based on mobile applications in the car. The new Genivi report marks the first time the Alliance's platform is proposed as a replacement for QNX or Microsoft or any other OS, indicating a change in strategy for the group. This is where the group may be overreaching. Presenting Genivi as a one-for-one substitute for existing real-time operating system solutions is a different proposition from offering a code-sharing/recycling platform intended to reduce development costs. Obtaining industry buy-in to this vision will take 5-10 years, by which time the market may well have moved on to the next big thing. And as an industry coalition-driven solution, Genivi arrives untested in the marketplace. The report further attempts to validate Genivi’s vision for cost-reduced platform development, saying interviewees estimated IVI deployment cost savings of up to 50%. At the same time, though, the report acknowledges that initial implementations may cost even more than incumbent solutions. Justifying or validating proposed Genivi cost savings will continue to be a tall order for the Alliance. Conclusions: The Genivi Alliance’s IVI software architecture report provides valuable insights but is rife with glaring omissions, unsupported conclusions and errant assumptions. The report oversimplifies the automotive OS ecosystem and competitive environment and underestimates the influence of some incumbent players, such as QNX, and the emerging role of content and service aggregators including TeleNav, Inrix, Airbiquity, WirelessCar, TCS, ITIS Holdings, Navteq and Hughes Telematics. A few of these content and service providers were interviewed for the report. But not a single telecommunications carrier or handset maker – outside of Nokia - was interviewed. Even more obvious than these omissions, however, was the exclusion of both Audi and the e.solutions joint venture with Elektrobit - the single most prominent, influential and competing IVI platform in the industry. The oversight is obvious and unfortunate. The forces that are determining the future of the automotive IVI experience are almost entirely developing outside of the car, so a wider base of interviewees should have been considered. The single greatest weakness of the Genivi Alliance is its inward focus on the automotive industry as opposed to an outreach to the wider world of mobile devices and consumer electronics. It is possible for Genivi to “win” in the long run and “challenge” (in the report’s own words) Microsoft, but the Microsoft embedded solution will always have the advantage of developer support from across a broader range of industries and the design priorities that those other user communities will contribute. Genivi’s narrower focus is at once its greatest strength but, in the end, its Achilles heel. <!--[if !supportLineBreakNewLine]--> <!--[endif]--> Further insight: Smartphone Market Evolution and the Automotive Opportunity Implications – Mark Fitzgerald – Automotive Multimedia and Communications Service - http://tinyurl.com/34hldb5 Automotive Connectivity: Beyond Bluetooth Solutions – Mark Fitzgerald – Automotive Multimedia and Communications Service - http://tinyurl.com/2gx88eo

It’s difficult to comprehend the schizophrenia of the automotive industry unless you’ve been living with it for longer than you can remember. One minute OEMs are embracing suppliers, the next they are beating them into the earth, forcing down their margins. The latest manifestation of this schizophrenia (some may call it give and take) is the contest over infotainment operating system dominance. Which automotive OS is best? Which is gaining? Which is losing? Does anyone care? The questions are all serious ones and they reflect the struggles at tier one suppliers to determine which operating systems to support. The issue was highlighted, yet again, at the annual Fachkongress Elektronik in Ludwigsburg last week. At the event, Audi voiced its support for QNX, Microsoft restated its devotion to the automotive industry as part of its wider embedded software initiative, and BMW announced its first Genivi implementation for a MY2013 vehicle program. But might these commitments shrivel in time as so many others before them have? What’s new in the current debate is the increased assertiveness of OEMs. OEMs are no longer content to take whatever a tier one supplier may deliver. In addition, there is a perception that the operating system represents a potential point of cost reduction. OEMs are taking charge in a variety of ways including specifying the operating system in the RFQ, creating a coalition for sharing and re-using code as in the case of Genivi, or getting into the system integration business itself as in the case of Audi’s e.solutions venture with Elektrobit. This new assertiveness on the part of OEMs has placed tier one suppliers in a bind. For many of these organizations, software and, by extension, the operating system, has represented the special sauce that the tier one brings to the RFQ proposition. From a tier one supplier’s perspective, the OEMs are seeking to strain that special sauce, which translates roughly as added value or cost, draining it of its value and ultimately diminishing the justification for an expensive solution. OEMs are hiring software engineers and programmers the way they used to hire line workers and tier one suppliers are feeling the pressure. The usual schizophrenia enters the picture when tier one’s try to make sense of what OEMs say they want. OEMs say they want open source software – as in the case of the Genivi Alliance built around Linux – yet they say, generally, that Android (also based on Linux) is too open. They say they prefer closed software systems – as in the case of Microsoft or QNX – but not too closed. It is a clever supplier, indeed, that can make sense of these conflicting messages. But with five-year development cycles in mind, hard decisions must be made. The fundamental criteria for evaluating operating systems break down to: Developer support Cost Flexibility Security Stability Cross Platform Functionality Long-Term Viability Independence All of the available operating system platforms have their merits and are competitive on each of these criteria with some notable exceptions. But it is worth considering the relative merits of each of the most popular platforms. Android is considered by many OEMs and suppliers to be “too open” – by which is meant vulnerable to attack. Android is supported most notably by Continental and Parrot and, indirectly, by a rapidly growing developer community and a growing range of hot selling handsets, Android is an OS to be reckoned with regardless of the qualms regarding its openness. And the widening use of an abstraction layer of code in automotive systems has rendered moot most security concerns. Our sources at Strategy Analytics say RFQs requiring Android have already been awarded. There is a broader battle surrounding Android in that the technology is being extended to a wide range of consumer electronics categories including televisions, netbooks and tablet PCs. Google’s promotion of Android into other domains places the Linux-based OS in direct confrontation with Microsoft and Apple which also have designs on the consumer electronics OS market. The fact that Android is being leveraged to facilitate connectivity to the wider device eco-system makes it an attractive choice for auto makers. Even GM/OnStar is considering Android for its next generation platform. Nevertheless, industry resistance persists. When it comes to automotive operating systems, though, Strategy Analytics recommends a dispassionate consideration of the relevant criteria and all signals suggest Android is a legitimate contender for future automotive platforms. Genivi is a Linux-based, industry-coalition driven OS intended to reduce development costs for OEMs by re-using and sharing software code. Genivi inspires both respect and anger in the industry. But, again, Strategy Analytics recommends a dispassionate evaluation. Genivi inspires respect because it has been promulgated by Intel and BMW, which have attracted a broad coalition of OEMs, tier ones and second and third tier suppliers. It inspires anger because coalition members of lesser status feel their influence is diminished. Most industry participants feel they must “participate” in the Genivi coalition so as not to miss out on any business opportunities with the leaders of the coalition: Intel, BMW and GM. At the same time, skepticism abounds regarding the length of time required for Genivi to impact the industry, the motives of the founders, and the internal decision-making processes of the organization. The impact of Genivi can probably best be compared to the influence of Autosar or JasPar. These initiatives unfolded over many years with the true nature of their impact only recently becoming clear. A typical benchmark to put Genivi into perspective, is the 10 years it took for Nokia’s “terminal mode” technology to reach the market as a commercial standard. As for the motives of the Genivi founders, it is simply to share and re-use code with the intention of reducing the cost of development. Leading Genivi participants expend a great deal of energy emphasizing the limited amount of software code that will be impacted by this sharing, but second- and third-tier players in the organization remain suspicious. BMW’s announcement at the Ludwigsburg event of te first vehicle implementation of Genivi for model year 2013 was momentous for the organization and the industry. But industry sources say the entry nav version of the platform in question – BMW’s NBT, for Next Big Thing – is being built around an nVidia processor. NVidia is not a participant in Genivi. Even in its first implementation, Genivi is raising questions about the solidarity of its coalition. (The premium NBT package will be QNX-based on an Intel platform.) Linux, in all its forms, appears to be the most popular operating system in the industry. Linux benefits from not having the support of any large organization with an industry shaping agenda. As an open source platform it is perfectly malleable and well-suited to a rapidly changing marketplace and technology eco-system. Linux is open and yet not perceived as representing a security risk and it is showing up in a growing range of systems and devices both within and outside the automotive industry. As in the case of Android, developer support is strong, and some tier ones previously working in older platforms, have begun shifting to Linux, as the safe choice. Robert Bosch and Clarion/Hitachi are just two of many suppliers that have turned to Linux even as they weigh other options. Visteon has been showing Ubuntu implementations during and since the Consumer Electronics Show in January. Microsoft, meanwhile, has one of the hottest hands at the OS table. The company routinely points to its two-million unit success with Ford Sync and its one-million unit (and counting) achievement with Fiat’s Blue&Me, with similar expectations for the soon-to-be-launched Kia Uvo platform. But Microsoft still struggles with a legacy of suspicion in the automotive industry. Car makers and OEMs frequently express their concern that the automotive industry is an afterthought for Microsoft. Microsoft has fostered this thought process by shuffling executives into and out of the automotive group. At the Ludwigsburg event the newest head of the Embedded Software group, Kevin Dallas, had his debut making a forceful statement for the Microsoft platform. In spite of any concerns about Microsoft's devotion, suppliers Alpine and Mitsubishi in Japan and Continental and Magneti Marelli in Europe have profitably embraced the platform. Microsoft can rightfully claim perhaps the widest developer support in the software industry. The company’s Bing search initiative is making impressive gains and its developer tools are widely supported. Microsoft even has its own alternative to Flash, called Silverlight, which is expected to see automotive implementations in the near future. Where Microsoft is weak, at least at the moment, is in the mobile market. Where Android has been able to counter Apple’s growing influence in mobile phone operating systems, Microsoft is struggling. Microsoft’s influence on the automotive market would no doubt be greater at this time if the company could point to a stronger position in the handset market. For now, Microsoft will be content to support individual OEM customers. Building on its success at Ford and Fiat and anticipated gains at Kia, it is likely that Microsoft will have a new OEM partner to announce within the next year. Chrysler and Mercedes are the most obvious but not the only candidates for a future announcement. QNX is in the strongest position it has ever been in in the automotive OS market. Harman’s design wins over the past five years have created a monumental backlog of premium infotainment implementations that will keep the company busy for the foreseeable future. At the Ludwigsburg event, QNX gained the endorsement of Audi as a critical element in its strategic plans. The company can also lay claim to the support of Panasonic and Denso, reflecting strong relationships with Chrysler and Toyota. QNX is perceived by many in the industry as being vulnerable for its lack of developer support and its lack of influence beyond the automotive market. But these perceptions may be subject to revision following the company’s acquisition by RIM. RIM creates instant credibility for QNX in the mobile market and QNX for RIM in the automotive market. In its current form, QNX is challenged by the need to keep pace with new drivers for mobile devices arriving on the market on a weekly basis. Microsoft and Android have the luxury of actually providing the drivers to many of these devices. QNX will gain from its RIM relationship, but the challenge will be to expand the capabilities of its operating system without increasing its system requirements. It is clear, though, that QNX has already gained a significant boost from its separation from Harman, making it easier for competing tier ones to adopt the platform. Conclusion The ongoing automotive operating system debate is complex and not easily resolved. Even aging platforms such as Micro-Itron or VxWorks (Nissan, PSA, Volkswagen) continue to persist and most vehicle infotainment systems and devices use multiple operating systems. In fact, the typical car might have a dozen or more operating systems processing information. The automotive business is not a zero sum game. Even at the Ludwigsburg event last week, new OS players Mentor Graphics and OpenSynergy were on hand taking in the latest industry developments even as they are laying the groundwork to make their own impact. Strategy Analytics can only recommend that industry executives make their OS decisions dispassionately and avoid prejudice and suspicion. There is plenty of business to go around and a win by one OS is not a defeat for another. Additional insight: Global OE Automotive Multimedia and Communications Systems Forecast 2009-2017 - Joanne Blight - http://tinyurl.com/24n9nz5 Global Automotive OE Audio/Visual (A/V) Systems Forecast 2009-2017 - Joanne Blight - http://tinyurl.com/2g897ax

Nokia, BMW and Daimler highlighted mobile phone integration in their Geneva Motor Show announcements this month. But each company took a different path with its own merits and shortcomings. The most flexible solution was shown by Daimler, but the BMW and Nokia solutions will influence future integration decisions.

 

The solutions – two iPhone-based and one Nokia specific - reflect the three fundamental paths to integration. Nokia’s terminal mode emphasizes leveraging the vehicle human machine interface via a bi-directional data exchange that transfers the device display into the vehicle head unit; hands control of the device over to the vehicle HMI; and makes use of vehicle CAN data for contextual feedback to the driver.

 

The BMW Mini iPhone integration puts iPhone applications, most notably Internet radio from RadioTimes, behind a large-screen embedded interface. Availability of this new connected solution is unclear, although the implication is that additional functions will ultimately be enabled and the vehicle HMI – in particular, a multidirectional, finger-sized toggle – will allow the driver to interact with phone-based applications without touching the phone.

 

The Daimler solution, offered for its Smart cars, is the closest to market – due this summer with a $400 price tag – and represents the most elaborate offering. It is also a third path to integration, providing a dash mounted iPhone holder with a suite of automotive applications – the first such suite developed by an OEM. Daimler has even gone so far as to customize the on-device interface with larger fonts and buttons.

 

Among the big differences between the Daimler integration solution and the competing offerings is that the driver mainly makes use of the on-device interface. Included in the application suite in the Smart iPhone application are hands-free calling, access to the on-device music library and Internet radio, Bing Internet search, a car finder function, and navigation with a “smart touch” feature. The cradle acts as a control unit, charger and microphone with stereo integration for muting during calls.

 

An additional enhancement due later in the year is a Smart drive kit camera, for fitting on the windscreen. The device will be able to transmit pictures of the area in front of the car to the smart drive kit via Wi-Fi and will thereby provide traffic sign recognition functionality including speed limits – a feature offered on a handful of portable navigation devices.

 

The smart drive app for the iPhone can be downloaded from the App Store at a one-off price of €9.99 for the basic version. The navigation upgrade with up-to-date maps costs €49.99 per year. Daimler says its researchers are currently putting the final touches to the smart drive kit camera functions.

 

The Daimler solution for its Smart car line-up is particularly appropriate since Smart cars in Europe are quite often sold without a head unit. In this case, the customer’s iPhone indeed becomes the vehicle’s on-board car radio, hands-free phone, navigation and driver assist system.

 

In contrast, the BMW Mini offering requires an embedded solution which will limit its scalability and upgradability, although the display real estate is substantial and the use of the vehicle’s HMI elements is preferable. The Daimler unit requires the driver to use the iPhone screen as the main interface. All three of these solutions will benefit from voice interfaces.

 

Like the BMW solution, Nokia’s Terminal Mode is intended to hand off HMI responsibility for smartphone functionality to the car. While the solution is promising, and Nokia is working with partners including Alpine, Magneti Marelli and Harman Becker, it is proprietary. As a proprietary solution, Nokia will face challenges to achieve market adoption despite working closely with the Consumer Electronics for Automotive (CE4A) coalition of German car makers.

 

Concept vehicles using the Nokia technology were shown at Geneva by Fiat and Valmet Automotive. In fact, the solution shown by Fiat, mounting a Nokia phone on a dash board as a navigation device connected to the Blue&Me system was significant given Fiat’s existing relationship with TomTom for a Blue&Me integrated PND.

 

Nokia’s terminal mode is promising, especially given its anticipated ability to obtain CANbus data for integration with different applications, but as a proprietary solution it is likely to be geographically challenged (ie. Eurocentric). A good example of an equally elegant solution with limited distribution is Novero’s proprietary Bluetooth interface developed for Ford. This solution is at risk of being marginalized once Ford finally decides to bring Sync to Europe.

 

Nokia has the right idea in pushing hard at smartphone integration, but the company would do well to enable standards-based technologies already deployed rather than seeking proprietary solutions. Even in the best of scenarios, the deployment of a proprietary Bluetooth profile on handsets and in cars is a years-long proposition. Daimler’s solution arrives in a matter of months with upgrades and enhancements to come before the end of the year, no doubt. Mini won’t be far behind.