The battle is on to capture the most and the most accurate traffic incident data on a global scale. Several strategies are being deployed to collect this information including traditional journalistic traffic reporting and a growing variety of technology-based solutions including GPS-based probe solutions or GPS Floating Vehicle Data (GFVD) from smartphone and connected PND makers and carriers to cellular network-based probes (CFVD), video cameras, mobile phone camera probes and crowdsourcing. GPS-based probe data networks are particularly popular with companies ranging from TomTom and Nokia to Inrix, Google and RIM. The significance of the emergence of probe data is the fact that any organization with connected devices, applications or vehicles on the road is a candidate for delivering probe data. The industry is facing a proliferation of probe data sources encompassing everyone from Waze, Skobbler and Navigon to OnStar, TeleNav and TeleCommunications Systems. The CFVD crowd includes TomTom, AirSage, iTIS Holdings, Cellint, Intellione, TrafficCast and a few others. The inaccuracy of probe data, GPS or otherwise, is stimulating interest in license plate scanners, tolling networks and Bluetooth roadside scanners from companies such as Bluetoad. In fact, TrafficCast has already deployed or received approval to deploy Bluetoad scanners in 20 states. The Bluetoad technology with its range of up to 200 feet picks up signals from passing Bluetooth devices which have become nearly ubiquitous in mobile devices. The beauty of Bluetooth scanners is that they can precisely identify both the roadway and speed, making them ideally suited to creating flow data. The downside, of course, as with all sensor-based sources, is the high cost of deployment – usually borne largely by local DOTs who gain access to the data – and the not infrequent failures to which they are prone. Of course, all of these solutions are only really able to act as proxies for identifying incidents as they can only identify the results and not the causes of backups. That is where cameras and observers and journalistic data from companies such as Clear Channel, Westwood One and Navteq’s Traffic.com come into the picture. Two years ago this analyst was a strong believer in the power that video could bring to the traffic data reporting and interpretation game. When I met the team at TrafficLand I came to believe that I had found the ultimate solution for the driving public: show people what the traffic disturbance is rather than tell them. TrafficLand had – and has – a near monopoly on DOT traffic camera installations, but its real value add is managing those images on the back end. TrafficLand not only captures most of the data but it also serves it up to handheld devices and Websites and, soon, to automotive head units. Alas, a lot can change in two years. Cameras do play an important role in traffic reporting and interpretation, but the cameras that are likely to make a difference are not the ones mounted along highways. Front-facing mobile phone cameras are the new frontier waiting for a clever entrepreneur. More than one industry executive has talked to me about the potential power of a network of camera probes transmitting real-time traffic camera information from the road. The user interface is a potential issue as is the required bandwidth, but what is a market changing proposition without a few challenges? There is more than one way to make such a network come to pass, these executives suggest, including everything from a dedicated dashboard camera to a smartphone-mounted device to a forward-facing camera on a PND or even the use of existing on-board cameras. Solutions already exist. Navigon has shown augmented reality navigation solutions using forward-facing cameras and Imaginyze has a lane-departure warning app based on a similar device. There is even a company, Apollo Video Technology, with an iPhone app to allow transit officials to view live video feeds from buses, trains, police cars and transit vehicles. Even the execs working on the Next Generation 911 solution for the U.S. are looking for ways to integrate video and text reporting of incident information from smartphones or other devices. It shouldn't be too long before a crowd-sourced traffic solution is introduced for smartphones that allows for the automatic uploading of photos and video stills from a dashboard perspective of traffic conditions under predetermined circumstances. To make such a crowd-sourced solution effective requires a sufficiently large and connected network of users and an automated application. In fact, it is almost shocking that neither TomTom nor Nokia have taken the leap into crowd-sourced traffic video feeds. Or is it? While I was a big fan of integrating traffic video feeds into navigation solutions two years ago, with today's emphasis on mitigating distracted driving the idea has lost significant traction. In fact, U.S. Transportation Secretary Ray LaHood is on a personal jihad to ban even voice calls while driving. Video is important and can be powerful, but the time is not right and the concepts currently in the oven - including Visteon's TrafficLand app - need more time to reach maturity. What is available today, however, is crowd-sourced traffic data from Inrix via its iPhone app (and soon on Android). The app-based Inrix system is the most complete solution, designed around one-touch incident reporting along with the ability to validate the entries of nearby drivers as well as to share the resulting data with local departments of transportation. Aha Mobile has been combining its own crowd sourced inputs with Inrix flow and Clear Channel incident data since late 2009. In fact, Inrix's approach stands as a model for future crowd-sourced traffic solutions with its tools for ranking participants and identifying "trusted sources" and the integration with local traffic authorities. Since June, 47 of 50 state DOTs in the U.S. have adopted Inrix's agency model for sharing this user-generated data, which the DOTs are able to view on the large screens in their traffic operations centers and then check by dispatching their own responders. Inrix says it is processing these crowd-sourced traffic feeds in real time thereby revolutionizing traffic reporting. In this way, Inrix is distancing itself from the existing competition through the integration of an entirely new source of data and a closed loop approach. The challenge for Inrix, though, is the limited size of its probe network, based on users of the downloadable iPhone app.  To have an impact Inrix, mainly seen as a white box supplier to the industry, will need a little help from its industry friends. Crowd-sourced traffic information has become the new standard and Inrix is setting the bar. Waze may claim to have the largest user population worldwide, but the company has chosen not to integrate other corroborating traffic information sources. Fusion of multiple types of data sources is a critical foundation for using crowd-sourced data, along with building  validation processes. Inrix has the largest North American population of users and has recently rolled out its apps in Europe. It is collaborating with ClearChannel in North America and other incident providers internationally for journalistic data. Crowd-sourcing of traffic data is nothing new. Crowd-sourcing by mobile phone users has been around for decades. It is only recently, though, that smartphone apps have enabled the automation of the process and, now, with Inrix's system, the integration of crowd-sourced data into local DOT traffic feeds - although Inrix traffic app users get the data right away, including inputs from nearby drivers. What is curious is that Inrix, while not the first to market with crowd-sourced traffic, is the first to take it to a level where it is integrated with official traffic feeds. While the crowd inputs are validated or rejected by other users on the network, the local DOT is also involved in the validation process. The open line of communication with local DOTs also means that real time street closings and openings can be transmitted along with incident validation. Inrix is not alone. TeleNav has a crowd-sourcing function for its app and TrafficTalk has been testing a crowd-sourced offering. Harman's Aha Mobile and competing mobile platforms will no doubt seek to bring their own offerings to market as well. Looking at the Inrix model, one has to wonder why TomTom, OnStar, ATX, Google, Nokia, RIM, TCS or TeleNav haven't moved in the same direction. OnStar has its good Samaritan function for reporting accidents, but there is no provision for instantly integrating an OnStar user-reported accident on the in-vehicle navigation/traffic display  - let alone sharing it with public authorities in real-time. The same is true for ATX. Conclusion: The automotive environment is ripe for crowd-sourced applications, which already include the reporting of speed traps (Trapster). The world of thumbs up/thumbs down, check-ins and trusted providers of reviews/data is rapidly proliferating on mobile devices and migrating into embedded automotive solutions. It is fitting that traffic information lead this migration since this form of data is of the highest relevance to drivers and rapidly changing. The power of crowd-sourcing of traffic data has the dual effect of creating a new source of incident data along with its own validation process. One of the greatest challenges to creating reliable traffic information systems is validating journalistic data inputs. The crowd is able to view live traffic data, create new data and validate that data. The next step is to open the taps to other data types from parking and gas pricing to weather and event information. Eventually, crowd-sourced video will work its way into the mix as well - and probably sooner than anyone expects. 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

TomTom’s marketing machine was in overdrive last week with announcements of a new OEM relationship (Mazda) and advances with existing partners (Toyota, Renault), enhancements to its (European) market-leading traffic solution (HD Traffic) and a traffic manifesto. But undoing all that positive spin was the note that the company still wants to charge about $50/year for its Live Services. It looks like TomTom didn’t get the latest email about automotive value propositions. As connectivity comes to more vehicles, drivers (and passengers) will get more of their content and services from the “cloud.” What this means is that car makers will increasingly have in place systems for sending, receiving, processing and managing all types of vehicle data – the “back end.” (This is not unlike what is happening at your average NASCAR or Formula One event every weekend – without the parking space availability and Internet radio.) The value of this data is manifest to the car makers for better understanding the performance of their vehicles on the road as well as better understanding how consumers use and abuse their cars. The implications for cost avoidance, warranty and recall management are in the millions of dollars of savings. There is no immediate or obvious benefit to the driver. For this reason, this kind of vehicle connectivity ought to be free. (On the other hand, OnStar and others have demonstrated that people will pay for safety and security.) As more drivers shift to smartphones (with mandatory data plans) with access to a wide range of content and services, they will be less likely to pay for any service from the car (or PND) maker that is available for free (or for which they are already paying) via their mobile phone. So how is the industry (and TomTom) going to monetize all this connectivity? Enter the back end value proposition. Auto makers and Tier Ones have gotten the message and recognize that driver and passenger eyeballs and “click-throughs” have value. A driver asking for directions to a restaurant or movie has economic value. A system that knows the location of the driver has value. Beyond this, a system that is able to provide a broader “cloud” perspective of all location-related activity – including everything from prosaic traffic information to “heat” maps of gatherings of people, weather, etc. – has other value-add implications for drivers, passengers and roadway systems and public transportation overall. But in the short-term, vehicle related information for diagnostics, safety and entertainment take priority. Continental, Harman, Visteon, Delphi and Pioneer clearly understand this. All of these companies have introduced systems or platforms that seek to leverage vehicle location information for commercial opportunities. Even Best Buy’s connected PND delivered sponsored links in its Google Search. Unfortunately, Tier Ones face an uphill struggle in trying to get a piece of this action. The telematics eco-system consists mainly of a telematics service provider (ie. ATX), a carrier (ie. Sprint or Verizon) and a system integrator (ie. TCS). Each of these operators is interested in the other’s business – with the possible exception of the call center. (No one wants the call center hot potato – too much cost.) While the call center tends to be shunned, the data back end tends to be either misunderstood or underestimated. But the back end system is rapidly becoming the backbone of the system altering the competitive landscape. The power and influence of back end systems is visible to the consumer in the growing variety of free content and services via smartphones. Google probably has the largest back end system currently influencing developments in the automotive market. With its free navigation, traffic and search and an open source operating system, Google has rattled the industry mightily over the past two years. Carriers, meanwhile, are trying to fight there way in – not content to be simply white label suppliers of bandwidth. Among the carriers sniffing around the telematics back end opportunity are Verizon, Sprint, T-Mobile, Telenor, Orange, AT&T Mobility, Vodafone and Ericsson. All of these companies recognize that their servers are as valuable as their networks. Some of these companies fancy themselves Tier One players. At least three handset makers have the potential to rise to the Google challenge: Nokia, Apple and RIM. Like Google, Nokia is offering free navigation while also seeding the market with open source development tools (Qt), operating system softare (MeeGo) and smartphone connectivity technology (Terminal Mode). But Nokia remains ambivalent about the automotive opportunity. MeeGo is not ready for market and Ovi has not been designed for automotive opportunities. RIM brings a unique value proposition combining its smartphone system experience with its newly acquired QNX automotive expertise. RIM represents the most immediate threat to Google’s potential dominance in the automotive market because of its potential to deploy navigation and traffic applications (based on handset probe data) and its ability to monitor, manage and mine its network data traffic. Apple’s strength lies in its secure systems for managing commerce for downloading applications and enabling the purchase of content. For these reasons, Apple and RIM both have the scope and scale to add value to automotive opportunities. The massive giveaway of content and services by both Google and Nokia is a setup for capturing click-through traffic and back end processing opportunities for creating metrics and analytic output. Google already has the analytic tools in place, unlike Nokia. The current landscape for back end services is highly fragmented and includes companies such as TeleNav, Airbiquity, Hitachi, TeleCommunications Systems, Hughes Telematics, WirelessCar, Oracle and IBM, along with the previously mentioned wireless carriers, RIM and Apple. (Strangely, Microsoft seems to have disqualified itself – having disbanded its automotive business unit. The original vision defined by Microsoft at multiple industry events included integrating more and more Microsoft solutions such as Bing, Tellme, and Silverlight into automotive platforms, but the complete vision – including back end services – never materialized. The one exception to this no-show for Microsoft are the company's ongoing efforts to capitalize on the Bing search engine.) The value proposition of back end service providers revolves around secure management and processing of vehicle and driver data for applications ranging from vehicle performance and safety to content and infotainment and, ultimately, commerce opportunities. Neither OEMs nor Tier Ones are equipped to manage this opportunity and traditional telematics providers lack the scale. The lack of scale is one reason Airbiquity has partnered with Hitachi to service Nissan’s connectivity needs around the world. It is likely that companies such as Hughes and TeleNav will seek partnerships with larger integrators such as IBM or Oracle for the same reason. Nokia, like RIM, already has the scope and scale and like Apple already has the commerce platform (Ovi) but, unlike Apple, has done little beyond the introduction of terminal mode to optimize its offerings for automotive. TomTom is another player in need of a partner to provide the scope and scale necessary to compete in the connected space. The larger organizations that are able to monetize the connectivity proposition will force out smaller players dependent on subscription revenue. If TomTom can enhance its navigation and infotainment platform to include safety and security telematics, it will greatly improve its value proposition and the likelihood of building a devoted subscriber base. Conclusion Google and RIM are best positioned to leverage the back end data processing opportunity presented by the automotive industry. Google faces trepidation among potential OEM customers who are suspicious of the company’s motives and objectives. Google’s failure to validate its Android OS for automotive applications is another stumbling block. Nokia has discrete elements of a solution in place but so far lacks the commitment and execution to challenge either Google or RIM. Apple is a wild card player in a market that remains fragmented with the door open to new entrants. Microsoft's Bing search engine is another contender gaining traction, but, in the end, Microsoft is more of an arms supplier to the contesting parties. Winners in the battle for the back end will be those companies able to bring security and state-of-the-art analytics and commerce management to the automotive industry. Google knows analytics. RIM knows security and network management. It remains to be seen whether Nokia or some dark horse will step forward to challenge these two dominant players, but the race is on. Additional Insight: http://bit.ly/c0OLhT - Consumer Implications for Smartphone-Vehicle Connectivity  - Chris Schreiner - Automotive Consumer Insights http://bit.ly/c1nvTq - Consumer Interest High for Connected Safety and Security Services - Chris Schreiner - Automotive Consumer Insights http://bit.ly/aGJHDj - Smartphone Market Evolution and the Automotive Opportunity Implications -Fitzgerald - Automotive Multimedia & Communications

Mid-week thunderstorms in Detroit appeared to be Mother Nature’s comment on momentous industry events, but it was Harman International that stole OnStar’s thunder with its announced acquisition of Aha Mobile. While OnStar celebrated its 15^th anniversary by announcing plans to offer voice-enabled access to text messages and Facebook, Harman’s Aha Mobile acquisition introduces the prospect of the first cloud-based telematics solution. The timing of the two announcements was extraordinary in juxtaposing two very different visions of the future of telematics. It showed OnStar still struggling to create a solution capable of stimulating organic consumer demand, while Harman is showing the way toward a platform capable of responding to and moving with changing consumer requirements. The Harman announcement also defined a third path – different than both the dominant OnStar embedded and Ford Sync connected solutions. It is a path likely to rapidly attract adherents and converts – especially given Harman’s command of the high-end infotainment market. The greatest challenge facing the telematics industry is the inability to get consumers to pay for additional subscription services. This shortcoming is manifest in the free months and years of service that are offered to prospective telematics subscribers and the corresponding retention rates of, at most, 50%. The free service is a lie, of course, since the system cost is already baked into the price of the vehicle. But the proposition is described to the customer as a giveaway, which has multiple negative connotations. As a giveaway, the telematics service is immediately perceived as either not having any value OR as something the customer will not normally request and be willing to pay for. This is a very shaky foundation for any industry. In fact, giving away anything is usually the first step toward that product or service being discontinued – with the possible exception of navigation. A good example of this phenomenon is satellite radio vs. Internet radio. Satellite radio continues to be subsidized by the service provider with a free subscription period for the consumer. The high cost of the service and hardware is masked by the supplier’s subsidies, but the cost remains and it is because of this cost that satellite radio is increasingly a consumer-selectable option or is no longer offered on a growing proportion of cars. In contrast, the millions of users of Internet radio services have demonstrated that they will go out of their way and pay handsomely for the privilege of accessing this service. Car makers and carriers could not kill consumer demand for Internet radio even if they wanted to. The fact that satellite radio is subsidized and offered “free” to the consumer is a long-term predictor of failure. The automotive telematics industry faces this same prospect every day. Rare is the Mercedes, BMW, GM or Toyota customer that crosses the dealer threshold requesting telematics services. In fact, dealers are hesitant to mention these services because of the occasional customer that might want the system removed from the car! (Don’t believe everything you read about OnStar’s claimed influence over GM vehicle purchases. Those messages are coming from OnStar, not GM.) It is in this context that OnStar announced the prospective capability for drivers using the Gen 9 system to receive audio Facebook updates and to receive and send text messages. The group also announced what it described as a platform offering the “potential for open development.” The focus on Facebook showed OnStar reaching out for an application that will offer users daily relevance – something missing from run of the mill safety and security applications. But this laser focus on a single application misses the greater goal of enabling GM customers to safely access any application they may desire. OnStar scores big points for identifying the most popular application within its target demographic, but what it misses is the ethos of that customer base which is freedom and personalization. This is where Harman scores with its Aha Mobile acquisition. While OnStar is testing and recruiting university students to cook up creative application concepts, Aha Mobile has already created a cloud-based location aware platform purpose-built for automotive environments, that is voice-enabled, traffic-data enhanced and ready for integration into automotive solutions. More important, the Aha Mobile strategy is to rapidly deploy application programming interfaces to enable the latest applications regardless of what they may be. In other words, it isn’t all about Facebook. Aha Mobile’s success is built on a portfolio of content and applications delivered in a manner suitable and responsive to the user. There are other Aha Mobile-like platforms, such as Aloqa, representing the latest wave of cloud-based aggregation solutions. But Harman’s acquisition, coming on the heels of 18 months worth of divestitures of divisions, facilities and personnel, reflects its importance in the context of a telematics market seeking that elusive objective: organic consumer demand. It will be interesting to see which Harman client is able to push to the front of the line to deploy the Aha Mobile solution: BMW, Mercedes, Chrysler, Toyota, PSA, Volkswagen, Audi or Hyundai. Might OnStar be interested in deploying Aha Mobile? What about Ford? With the acquisition of this tiny start-up Harman may breathe life into a telematics industry in desperate need of a marketing lift. Additional insights: http://bit.ly/bUoJKc - Consumer Implications for Smartphone-Vehicle Connectivity - Chris Schreiner - Automotive Consumer Insights http://bit.ly/c0OLhT - Consumer Interest High for Connected Safety and Security Services - Chris Schreiner - Automotive Consumer Insights http://bit.ly/aLtrF7 - Google, Nokia and New Entrant Positioning in Automotive Infotainment - Lanctot - Automotive Multimedia & Communications http://bit.ly/d0aLhq - Connected Vehicle Telematics: Car Maker Profiles - John Canali - Automotive Multimedia & Communications Service

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

Delphi used the SAE 2010 World Congress event in Detroit this week to unveil D-Connect, its answer to Nokia’s terminal mode smartphone connectivity solution. D-Connect addresses an array of in-vehicle connectivity challenges – including automotive-oriented application stores - while defining a radical new vision of center stack architecture. The system architecture is described as being built around an Intel or ARM processor with a Linux kernel, common Linux packages, Genivi, ported device applications and, finally, an HMI layer. Availability of D-Connect is likely dependent on OEM adoption. For the U.S. market, its significance is its representation of Delphi’s vision of universal smartphone connectivity and arrives as the company emerges from Chapter 11. The D-Connect vision simultaneously provides center stack connectivity for any smartphone – reproducing the on-device display in its entirety on a large touchscreen display mounted in portrait mode – with separate interfaces for when the vehicle is static or in motion. When the vehicle is not moving, the display allows access to all the apps displayed on the device and allows the device to be manipulated and the apps to be accessed directly from the large display via touch or voice interface. The system was shown with a physical connection, though Delphi says the system will support Bluetooth, USB or Wi-Fi connectivity. The D-Connect vision includes Delphi’s announced intention to provide app store support. Delphi says it will certify applications to determine which will be accessible when the vehicle is in motion. When in motion, the separate HMI display will appear with large on-screen icons including “Voice Search,” “Navigation,” “View Maps,” and “Contacts.” The system appears to be positioned as an alternative to Nokia’s terminal mode, shown most recently at CeBit and at the Geneva Motor Show. Nokia’s solution similarly provides for vehicle HMI control of smartphone functions and is being developed by Nokia in conjunction with Tier Ones such as Harman, Magneti Marelli and Continental along with some OEMs. Both the Delphi and Nokia solutions are still in concept mode. The significance of the Delphi solution is magnified by its proposed use of a large portrait display in the center stack, its ability to be operating system and connectivity agnostic, its in-motion interface with app certification and its use of the Genivi operating system in conjunction with separate Linux packages. The use of Genivi and Linux is unique and represents the first demonstration of a complete solution based on the newly proposed automotive operating system. It also allows Delphi to define a new path to the much discussed in-car application store. As far as the app store is concerned, Delphi sees application downloads working strictly via the device and functioning through device connectivity – not through a direct download into the car. Delphi uses the Genivi operating system and other Linux-based applications, to interface to downloaded apps, but prefers to keep the applications themselves outside the center stack software environment. Delphi’s approach contrasts with Continental’s AutolinQ system, which brings Android into the center stack. D-Connect will connect with Android phones and applications but does not bring that code on-board.  To further build the D-Connect brand, Delphi has also chosen to name the actual phone application D-Connect.

The battle to dominate automotive connectivity has finally been taken on by Research in Motion (RIM) with the announced acquisition of Harman International's QNX Software Systems, a real-time operating system supplier focused on the automotive market. RIM had appeared to be sitting on the sidelines in recent months as fellow handset maker, Nokia, announced its terminal mode strategy and Apple grabbed multiple headlines for innovative in-vehicle connections from marketing partners. The acquisition of QNX gives RIM instant credibility as a leading automotive connectivity player and promises a spirited battle for automotive market share. The acquisition was announced this morning. The announcement says the two companies have reached an agreement for RIM to acquire QNX. The deal is subject to regulatory approval and is anticipated to close within 35-45 days. This strategic move is expected to further strengthen QNX's penetration in the automotive market and foster innovation for markets served by all parties. The move solves marketing challenges for both organizations. QNX's software is used in instrument clusters, head units and automotive Bluetooth solutions. The company had found tremendous success as part of Harman, which in recent years has come to dominate the luxury and near luxury segments of the automotive market. QNX is best known for its high-end infotainment software solutions used by Mercedes-Benz, Porsche, BMW, PSA, Hyundai and Chrysler, among other OEMs. As part of Harman, though, QNX's ability to break out into larger volume market segments was somewhat limited, and Microsoft had been winning most of the highest profile (and higher volume) automotive connectivity platforms including Fiat's Blue&Me, Ford's Sync and Kia's Uvo. At the same time, Apple was increasingly emerging as the automotive connectivity device supplier of choice for consumers and, by extension, OEMs as both the iPod and iPhone helped establish the iTunes App Store model as a compelling content, application and service delivery platform for the automotive market. It is true that some OEMs, such as Mercedes with its mbrace smartphone app, made allowances for Blackberry connectivity along with Apple's iPhone. But a growing number of OEMs, such as BMW, have been going out of their way to provide proprietary Apple connectors to enable the use of in-vehicle interfaces to access smartphone content. With few exceptions, Blackberry has been receiving no such support from OEMs and its devices remain enterprise-focused and ill-suited to automotive infotainment uses. While QNX's partnership with Alcatel-Lucent promises to target the complete spectrum of in-vehicle connectivity, a partnership with RIM opens up wider market opportunities for both QNX and RIM. The timing of the deal is ideal given that several OEMs participating in volume segments of the market have yet to launch branded, high-profile connectivity solutions. There is still time for a RIM-QNX collaboration capable of helping RIM vault into contention with both Nokia and Apple for automotive connectivity leadership. RIM also brings its unique global managed network added value to the proposition promising enhanced capabilities for in-vehicle applications that other handset suppliers are unable to match. It also presents a potential challenge to telematics service providers such as WirelessCar, Airbiquity and Telecommunications Systems. The importance of the in-vehicle connection has become increasingly important as consumers seek to use their smartphones in a growing variety of settings ranging from the home to the office and the car. QNX's existing position in the automotive market will instantly bring credibility to RIM's initiatives. It also introduces an entirely new value paradigm combining the virtues of device connectivity with the advantages of the managed network. The move is also a positive for Harman as it frees up the company to work with a wider range of software providers. Harman cannot afford to ignore the Genivi Alliance operating system, favored by its largest customer BMW. But Harman may also find it expedient to bid on Android- or Microsoft-based projects. Harman gains greater flexibility by decoupling itself from QNX. Of course, in reality the two companies will be virtually joined at the hip for the foreseeable future with a wide range of programs already underway and in the pipeline expected to extend for more than five years into the future. RIM, though, is likely the bigget winner. The company has been confronted with pressure to extend its operating system software to other industries such as netbooks, consumer electronics devices and, yes, automotive applications. The acquisition of QNX is an excellent door opener to these potential avenues of growth. QNX is in a similarly advantageous position to profit from wider market opportunities. Of course, while the move gives RIM a strong hand in contending for automotive connectivity opportunities it is likely that the merged company will continue to collaborate with Apple. QNX has a long history of supporting Apple in the automotive market including the most recent announcement of enhanced support for Apple iPods in the QNX Aviage Multimedia Suite.

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.

While Nuance reported broad-based Q1 revenue growth across all of its divisions, growth within the mobile segment hit 12.5% YOY accounting for nearly half of total company revenue and surpassing company expectations for the segment. Nuance told analysts on its earnings call it had expected healthcare to lead revenue growth for the company. Recent wins in the mobile segment show Nuance technology moving into a wider range of applications enabling new features and functions on devices and in cars. Among higher profile wins were Ford's announcement that the next generation of Ford Sync will feature significant voice enhancements from Nuance that power the MyFord Touch driver connect technology. The next generation of Ford Sync takes advantage of Nuance’s natural language understanding to recognize more than 10,000 first level commands and provide customers with cloud-based connectivity for up-to-the-minute information and entertainment content, the company stated in its prepared Q1 earnings report comments. In addition, Nuance says TomTom recently selected Nuance text-to-speech for its navigation applications for the iPhone. Nuance recently announced that its Nuance VSuite mobile speech software is now shipping on Dell’s Mini3 Android smartphone line-up in China and Brazil. During Q1 2010, mobile royalties grew, reflecting increased unit shipments as well as increased penetration of Nuance technology on device, Nuance reported. During Q1 2010, Nuance introduced Dragon Dictation and Dragon Search for the iPhone. In addition to driving visibility, the success of Nuance’s Dragon iPhone apps has generated interest from carriers and mobile providers to deliver applications for other mobile platforms, languages and vertical markets. During Q1 2010, Nuance launched its voicemail-to-text offering at AT&T, and announced the acquisition of SpinVox, which positions Nuance to accelerate growth and expand its solutions internationally in the voicemail-to-text market, according to the company. Voicemail-to-text, in particular, was cited as a critical application to impact future company growth. Key customers and design wins in Q1 2010 included Amazon, BMW, Daimler, Harman Becker, Harley Davidson, Huawei, Hyundai, LGE, Mahindra & Mahindra, Medion, Motorola, Nokia, Samsung, Sharp, Sony Ericsson, T-Mobile, TomTom, and Toyota.