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

Both Cairo and Espoo witnessed revolutions on Friday, Feb. 11^th. Mobs in the streets of Cairo saw the 30-year reign of Hosni Mubarak come to an end and Espoo saw global handset market leader Nokia embrace the smartphone platform of rival Microsoft. While Egyptians have been left to sort out what their nearly bloodless military coup hath wrought, the open source community surrounding Nokia’s now cast-off platform is assessing the long-term prospects for MeeGo and the Qt developer framework.

The implications for the automotive OS world are yet unclear.

Nokia says the first device using MeeGo is still in the works and will arrive later in 2011. Absent from any public statements at the announcement of the partnership with Microsoft was the statement of a plan for supporting MeeGo as the open source OS choice of the automotive GenIVI Alliance.

By the end of the day, crowds in Tahrir Square in Cairo were setting off fireworks and celebrating deep into the night as Mubarak made his way to the resort of Sharm el-Sheikh. Meanwhile, executives involved in the Qt developer community suggested, by Friday evening, that there was no change in their plans as a result of the Nokia-Microsft announcement. Intel made a belated statement of support for MeeGo:

“Our strategy has always been to provide choice when it comes to operating systems. MeeGo is one of those choices. We support a port of choice strategy that includes Windows, Android, and MeeGo. This is not changing.

“MeeGo is not just a phone OS, it supports multiple devices. It is already shipping and we’re seeing early momentum across multiple segments today, including automotive systems, netbooks, tablets, and set-top boxes.”

Operating system momentum in the automotive industry is slow to build and slow to dissipate. By now, MeeGo and GenIVI indeed have momentum. But there is no doubt that the Nokia announcement was NOT good news for either MeeGo or GenIVI. Both MeeGo and Mubarak were clearly “thrown under the bus.” (Perhaps it is more accurate to say Symbian was thrown under the bus, but MeeGo was clearly de-emphasized.)

In the short-term, the Nokia-Microsoft announcement is a minor blip on the automotive OS radar screen. Longer term, industry executives will watch closely to see the impact on developer support. If Stephen Elop learned nothing else from his time with Microsoft CEO Steve Ballmer (http://bit.ly/qiASt) it is the power of developers.

Qt and MeeGo both have already attracted legions of enthusiastic developers. Elop’s handling of the announcement reflected a cultural disconnect between an executive coming from outside the open source world taking the helm at a company steeped in the rich broth of open source solutions including Symbian, MeeGo and Qt.

While there is no doubt that the open source community failed to deliver the competitive edge Nokia needed, the company might take better care that it is not throwing out the baby with the bathwater. Nokia must decide whether it can support both the open source community and Microsoft’s Windows Mobile 7.

It is worth noting that no one in the industry is questioning Google's commitment to Android.

Conclusion:

Strategy Analytics expects a strong statement of support from Nokia for Qt and MeeGo at this week’s Mobile World Congress. A late statement of commitment and support is better than no statement at all. The legions of developers around the world that are bringing energy to those platforms – which are NOT in flames, to use Elop’s analogy – would benefit from a strong endorsement equivalent to the one given by Nokia to former rival Microsoft.

GenIVI will likely forge ahead with or without MeeGo over the long haul. As an open source platform, GenIVI has the flexibility to shift to a new distribution of Linux if necessary. The ship has already sailed and there is no turning back. It’s just not clear that Nokia is on board. And the company is certainly not at the helm.

Additional insight:

http://tinyurl.com/4m3rm73 - Nokia Tosses the Car Keys to Microsoft - Insight - Automotive Multimedia and Communications Service

GM’s Chevy Volt is the best thing to happen to electric vehicles since the Prius hybrid. In fact, it would be even bigger than the Prius if more than 10,000 were being made next year. The car represents revolutionary technology. It makes electric vehicles palatable to the mass consumer – at least conceptually if not based on the $41,000 price tag. The electric vehicle business was in desperate need of a car like the Volt that could take the worry out of driving electric. By adding the internal combustion engine (ICE) to drive the electric motors when the vehicle’s on-board battery is exhausted the Volt offers an acceptable range for any kind of driving requirement.

The car also features cutting edge componentry with a low-weight, low-energy stereo system from Bose, an OnStar telematics system (with five years of free service) with an iPhone app, and a multiple-screen vehicle diagnostic experience. The car looks and feels and drives like the future. But the simplicity of the Volt concept belies the complexity of the electric vehicle business and therein lies some long-term concern for the viability of any alternative fuel vehicles. A big contributor to the complexity of the EV picture has been the Regulatory Authorities.

My kingdom for a PZEV

The regulatory authorities are well-meaning bureaucrats who are trying to stimulate demand with financial incentives for specific types of cars while providing guidance to the auto maker community regarding which kinds of vehicles will be acceptable to meet fleet emission standards. These efforts have produced an alphabet soup of vehicle categories and a maze of definitions that have been further confounded by the automotive press. From the regulatory authorities we were originally given (see Strategy Analytics reports referenced below for detailed definitions and history):

·        TLEV – Transitional Low Emission Vehicle

·        LEV – Low Emission Vehicle

·        ULEV – Ultra-Low Emission Vehicle

·        SULEV – Super-Ultra Low Emission Vehicle

·        ZEV – Zero Emission Vehicle

These categories would be humorous in and of themselves but they have already been superseded by:

·        ILEV – Inherently Low-Emission Vehicle

·        PZEV – Partial Zero Emission Vehicle

·        AT-PZEV – Advanced Technology Partial Zero Emission Vehicle

·        NLEV – National Low Emission Vehicle

Again, it is tempting to chuckle, but these categories have very real and very specific definitions that can mean the difference between a $7,500 vehicle incentive and a combined $12,500 vehicle incentive. The Volt is a case in point. Because the car was introduced with an 8-year/100,000 warranty on the battery instead of a 10-year/150,000-mile warranty it did not qualify as an AT-PZEV according to the California Air Resources Board (CARB) requirements and missed out on the additional $5,000 incentive in California for which the Nissan Leaf does qualify. (This was in spite of the fact that GM reportedly tested and validated the car for the 10-year warranty and expects to boost the warranty for the current Volt or on a new version of the car by 2012.)

EVs not EZ

To make matters worse, the automotive press and industry trade associations have their own roster of EV categories – presumably reflecting their assessment of consumer perceptions. The Electric Drive Trade Association lists the following categories:

·        HEV - Hybrid Electric Vehicles

·        BEV - Battery Electric Vehicles

·        EREV - Extended Range Electric Vehicles

·        Plug-in Hybrid Vehicles

·        Fuel Cell Electric Vehicles

The Volt is sui generis! It is the only EREV, according to the EDTA. This is something that bothers industry types. This would be a minor point if it were the end of the conversation regarding the definition and categorization of the Volt, but it is not. According to some sources the Volt operates as a “plug-in series hybrid” or as a “power-split or series-parallel hybrid” depending on speed or driving mode. By the way, in California, the Volt is considered a ULEV and not a SULEV based on emissions testing.

When is a Volt not a Volt?

Few cars in the history of the automotive industry have been subjected to as much scrutiny as the Chevy Volt – suggesting some strange American instinct toward eating its own young. The Chevy Volt is unquestionably the nastiest, most clever move the automotive industry has pulled in decades. It just seems to frustrate the heck out of regulators and journalists and analysts. GM pulled a fast one out of its hat – one just wishes the company had plans to pull more than 10,000 out of its hat this year. (One might argue that Subaru of America has been a good deal more clever than GM. The company has sold a combined total of hundreds of thousands of PZEV designated Foresters, Legacies and Outbacks that are “sometimes even cleaner than some hybrid or alternative fuel vehicles,” according to the company.)

“I’ll ask my manager.”

Which is where the Chevy dealers come into this story. Having recently attended a Chevy Volt launch event I visited my local Chevrolet dealer. There was a single Volt on the showroom floor, as promised by the Website. (There are four or five Chevy Volt dealers in the area. Not all Chevrolet dealers qualified to sell Volts.) The car in the showroom had a “Do not touch” sign on it with a message that the car was already sold. Of course, that meant that the car was also locked so that the dealer was not able to give test drives, could not demonstrate the clever on-board and OnStar systems, and could not allow a customer the experience of simply sitting in the car. A salesperson indicated that he did not know when they would get any more vehicles and he was not sure what other dealers in the area had any Volts. I returned home and entered my name on the dealer’s waiting list and was called almost immediately. The salesperson on the phone said four cars were due to be shipped in January and one, a white one, was not spoken for. To reserve this incoming Volt, the salesperson said, I would have to put $5,000 down. I asked about the widely reported $350 lease on the car – an attractive option considering the limited life of the battery. The salesperson said there was no lease available and then he suddenly added that to get the Volt that was coming in January I would have to pay $5,000 over MSRP. There is little that will kill enthusiasm for a new car faster than a dealer charging $5,000 over MSRP. It wasn’t bad enough that I could not drive the car, could not sit in it, could not see it do its sexy technology stuff right there in the showroom.

Whether you want a ULEV, an EREV or a serial-parallel hybrid, you will still need to be prepared to do battle with a dealer who will use your enthusiasm against you. Who knew changing the automotive industry would be so difficult. (For the record, GM and Chevrolet representatives say they have specifically asked dealers NOT to charge above MSRP for the cars and there definitely IS a $350 lease offer on the Volt.)

Further insights: http://bit.ly/gtyxic - EV/HEV Technologies Supply & Fitment Database - Kevin Mak - Automotive Electronics Service http://bit.ly/devMOq - Hybrid Technologies Legislation/Support - Kevin Mak - Automotive Electronics Service http://bit.ly/eC7kFy - Impact of Volt, Leaf Transcends Modest Sales Expectations - Roger C. Lanctot - Insight – Automotive Multimedia & Communications Service

As recognition in the industry grows regarding the importance of crowd-sourced traffic information, the race to build or acquire the biggest crowd has taken hold. Weighing in for the struggle ahead are RIM, Google, Nokia, Telenav, TomTom, TCS/NIM, Inrix, Waze, Telmap and just about any other organization with access to the GPS feeds associated with connected mobile devices. Crowd-sourced data is not simply passive GPS data feeds. By crowd-sourced information this analyst is referring to ACTIVE information inputs from traffic observers feeding live reports of incidents and traffic jams. This is the new frontier in traffic information and traffic information providers are still building the tools to capture and integrate these inputs. (The Holy Grail will be a connected traffic solution with in-dash display showing crowd-sourced updates of hyper-local traffic conditions - certainly within the realm of the possible with existing technology.) Navteq is the latest player to join the fray with its acquisition of Trapster, the speed camera location company built upon nine million downloads of its application for reporting speed camera locations. Reportedly battled over by five other bidders, Trapster has attracted a substantial following potentially putting it ahead of TCS/NIM, with about five million probes, but behind Telenav, with more than 17 million. Of course, the challenge for any vendor of crowd-sourced information is the need to get users to turn on and actively use the application. If people are not actively navigating or otherwise sharing their location information – a power-hungry proposition – then the network is, in reality, only a fraction of the total user population. Nevertheless, crowd-sourced information is the next frontier and it has a role in everything from POI information and evaluations, to social networking and, now, traffic. The information is so important to obtain, that companies such as Waze have created elaborate games and reward systems for participants, and tools are usually put in place for identifying trusted data sources and flagging unreliable ones. The key to the success of any traffic system or service, though, is scalability. While crowd-sourced models are interesting – tantalizing even – the question the service provider eventually must face is whether or not they can be scaled. Waze has demonstrated its ability to scale across multiple geographies, although this has spread the current population of three million participants too thin to be reliably useful in all locations. Inrix has enabled crowd-sourced inputs for the U.S., which are being shared with Dept. of Transportation traffic centers, but has yet to extend the platform globally. TomTom’s Live Services application for its connected PNDs currently boasts hundreds of thousands of users, but the solution is built on a standardized and scalable platform that the company is extending – slowly but surely – to the U.S. and Asia from its European base. The GPS-based crowd-sourced data from TomTom PND and embedded PND users will enhance the company’s already cutting edge HD Traffic solution. As it seeks to stake its own claim in the crowd-sourced traffic data sweepstakes, Nokia Navteq will need to define a global traffic service solution, applicable in all geographic markets and capable of leveraging Nokia Navteq’s unique strengths and customer relationships. Just as Inrix, for example, has been able to launch 18 standardized traffic products deployable across any geography, Nokia Navteq needs to build out its traffic portfolio as part of its own effort to set as high a standard in traffic data as it has established in mapping. The race is on.* *Editor's note: OnStar and Apple are notable for their absence from the current roster of crowd-sourced traffic competitors. Nothing appears to be standing in the path of either organization entering the crowd-sourced traffic game. OnStar could no-doubt use the value enhancement to its existing traffic services. Apple, along with the major wireless carriers, has left this value proposition to third parties for now. Stay tuned. http://bit.ly/dLWMJK - Time for Nokia to Take Over Traffic Strategy - Lanctot – Automotive Multimedia & Communications Service

SAIC brought its InkaNet embedded telematics system into the market earlier this year at the Beijing Auto Show under the Roewe brand. The system is now available in dealer showrooms and it is opening eyes to the possibilities around innovative telematics solutions in China and elsewhere. The ability to deliver location-aware advertising is one capability worth a closer look especially for its potential to subsidize telematics services. The InkaNet system was created with the assistance of Pateo. The founder of Pateo is also the founder of Energy Source, which is an advertising agent established in 2001. The functionality of the system, described in literature distributed in Roewe dealerships, includes a wide-range of location-relevant applications and services. While the system does not explicitly state this objective or capability, the description of the system suggests it may well be the first automotive system (in China) able to deliver location-relevant advertisements. If so, it is not unlike the service deployed in New York City cabs by Creative Mobile Technologies. Fitted for rearseat viewing by taxi passengers, the Creative Mobile Technologies solution is able to use GPS data to determine when and where ads are shown in the rearseat. The system also enables credit card payments and CMT has started to release data regarding the kinds of information passengers have requested from the system by day of the week, such as news, weather, sports, business, Zagat or People Magazine. New York’s taxi commissioner commented in a recent NYTimes article that in lieu of demanding advertising revenue, the city hoped that the additional income for vendors might encourage them to lower the fees they charge to cab owners, which could in turn reduce the pressure to increase fares. The only current player in the telematics eco-system offering the prospect of sponsored content or services is Pioneer Electronics with its Platform for Aggregation of Internet Services (PAIS). Pioneer has made clear that this social networking oriented system, enabled through a smartphone connection or an embedded module is built around a revenue sharing model unmatched in the industry. As Google and Bing bring their browser battle to the automotive segment, the opportunity for sponsored search or other subsidized content in the car is on the table. (Will Baidu offer sponsored search for connected cars in China?) And ClearChannel’s iHeartRadio Internet radio service deal with Toyota Motor Sales could include some advertising or promotional element. It is worth noting that one of the most successful connected services delivered to cars – as measured from a profitability standpoint, is Sirius XM. Sirius and XM bought their way into dashboards which eventually led to positive cashflow. Maybe it’s time for more content and service providers to pay up. InkaNet is showing the way. NOTE: The InkaNet system is not without its shortcomings. For further details: http://tinyurl.com/2b5vbvx - Enter, the Dragon: China Getting Its Moment on the Telematics Stage - Lanctot - Insight – Automotive Multimedia & Communications Service http://bit.ly/gWT4QX - Automotive Electronic Design Heads East - Kevin Mak - Automotive Electronics Service

Bing’s map portal, relaunched last week, could be a Google killer with its array of map apps and its integration of Trafficland traffic camera images. The new platform stands out from the dominant Internet map solutions and sets a new standard for content access and management. The new portal also points the way to future multi-screen telematics system deployment. Fittingly, the new Bing maps portal is a bit of a beta experience. Several of the apps appear to be either incomplete or only dedicated to a particular region of North America or a particular country outside of North America. The Silverlight plug-in failed for this user and some apps periodically failed to function, but a patient user will find an impressive map-based canvas and an enticing palette of compelling apps to manipulate. The array of available apps are suitable to managing social networking activities as well as travel or day planning or just noodling around with local demographic information, upcoming events or shopping. Please register or log-in to read the complete report http://www.strategyanalytics.com/default.aspx?mod=reportabstractviewer&a0=5900

Nuance’s Automotive Summit, which took place in Detroit last week, highlighted the leadership position Nuance and one of its most prominent customers, Ford Motor Company, now command in the area of automotive interfaces. While battles may continue to be fought over voice, touch, haptic, and other in-vehicle interfaces, these two companies are positioned at the vortex of the debate leading the charge to develop and deliver safe vehicle interfaces and redefining the automotive branding process. The assumption of this leadership mantle occurs at a time when car makers and their suppliers have been running for cover under heavy fire from regulatory powers in Washington, DC. And the Feds have taken on the added support of lobbying groups and some research organizations. The Federal government’s regulatory arm has stepped into the roadway seeking – like a speed-gun wielding traffic officer – to impede the industry’s headlong advance toward connectivity and smartphone integration in cars. Car makers and the supplier community, by and large, have taken one of two courses. Most have remained silent on the issue of the day – driver distraction – hoping it will either go away or that some white knight, such as the Alliance for Automobile Manufacturers or some other group will calm the waters for them. Others, such as General Motors’ OnStar division, Volkswagen, and QNX have chosen to hit the accelerator. In recent weeks, OnStar has announced its plans to enable Facebook connectivity in the car. Volkswagen and QNX have posted YouTube videos showing early executions of terminal mode smartphone connectivity. These videos show all forms of smartphone images displayed in-dash with no context – ie. no discrimination between what will and won’t be accessible when the vehicle is in motion. In contrast, Ford has been reaching out to regulatory authorities on multiple fronts. The very same week OnStar was announcing Facebook connectivity, Ford representatives – together with Nuance executives – were meeting on Capitol Hill in Washington with legislators explaining the state of the art in voice-based in-vehicle interfaces. Prior to this outreach effort, which is ongoing for both legislators and regulators within the Department of Transportation’s National Highway Traffic Safety Administration, Ford also responded to complaints from the DOT’s now-famous director, Ray LaHood, and altered some of its advertising imaging and messaging. This was LaHood’s first missile fired across the bow of Ford’s Sync interface. The advertising messages are critical. Both Ford and OnStar are running some of the most highly visible television ad campaigns in the U.S. showing off their in-vehicle systems – at a time when both firms are fighting their way out of the steep sales decline of 2009. It is absolutely essential that both companies communicate effectively with so much unwanted attention being focused on these systems and with important sales and market share on the line. OnStar bears the added burden of embedded telematics industry leadership. No other auto maker has taken the embedded telematics approach as far as OnStar which now, after 15 years, has nearly six million subscribers. But with diminished vehicle sales and a virtually unchanged renewal rate, OnStar is facing a potential erosion of its subscriber base. In spite of all it has done to offer compelling solutions to consumers, the company now feels pressure to do more to boost its subscription renewal rates. The company is also swimming against a strong demographic current as GM’s historical customer base has aged. The company is clearly looking to OnStar to not only maintain its previous status as a profitable division by maintaining and adding to its existing subscriber base, but also as a potential source of demographic stimulus to reach out to younger car buyers. GM is not alone in reaching out to younger buyers. Almost every car maker is in a perennial campaign to tap into the next generation of car buyers. And with smartphone purchasing demographics corresponding with this target market, the smartphone connectivity proposition has become essential. (GM and OnStar are somewhat limited by the current vehicle offering which lacks for a robust line-up of small cars targeted toward a younger demographic.) The advertising targets can hardly be missed in the existing television spots which show young people interacting with OnStar systems to obtain location or vehicle information. (A minor pet peeve of this analyst is that it seems that not all these young people, even when they are in the front seat, are seatbelted in the ads – but company executives insist they are all safely secured.) The OnStar television campaign dovetails nicely with GM’s parallel social networking marketing initiatives on Facebook, Twitter and other Web-based communication channels. The smartphone application for controlling vehicle functions and accessing vehicle data on the Chevrolet Volt is another manifestation of these efforts. What is lost in this campaign, though, is the rock solid safety and security message that brought OnStar to this industry leadership position in the first place. Ford has also been youth-oriented in its embrace of connectivity technology. Ford’s ads emphasize the safe use of technology in cars using voice interfacing technology. Watching these ads as a participant in the industry is mesmerizing given the degree of focus on the human machine interface in the car. (While this analyst would prefer the driver not touch the display while the vehicle is in motion, Ford has made clear its adherence to AAM guidelines and the limitations of this functionality in a moving vehicle.) What OnStar and Ford both realize is the need to reach out to younger car buyers. The key motivator here is the need to provide for smartphone connectivity, both for safety and functionality. Younger smartphone, and car, buyers are primary targets for location-aware applications ranging from traffic and navigation to social networking, according to Strategy Analytics research. The drive to connect smartphones is behind the enthusiasm for Nokia’s Terminal Mode initiative along with Apple’s iPod Out, Delphi’s D-Connect, Ford’s AppLink and similar solutions. But only Ford has stepped to the forefront with a vision and implementation of a walled garden-type approach to application deployment. There is a recognition in the industry of the appeal of both smartphone connectivity and application deployment. Ford talks about the beamed in, brought in and built-in strategies for delivering content, applications and services, but the underlying philosophy is control. The power of the Ford solution lies in five value propositions: Distraction mitigation: The voice-based interface minimizes eyes-off-the road time. Demographic targeting: The smartphone interface appeals to social networking young people. Future proofing: The Microsoft-based platform allows for application development and deployment thereby enhancing the value of the solution over the life of the vehicle. Subscription anxiety: The connectivity solution allows the consumer to defer the subscription decision and places the burden of data transport on the consumer’s existing wireless subscription. Branded HMI statement: Ford IS Sync. Ford IS MyFord Touch. The interface has become the brand. A new era in the automotive industry has arrived. At last week’s Automotive Summit, Nuance emphasized all of these points. Whether the solution being shown was the company’s touchpad character recognition, hybrid on-board/off-board speech recognition, enhanced echo cancellation/noise reduction, or focused search all were targeted at reducing distraction while providing a branding pallet for car makers and their suppliers. Presenters at the event, including Nuance executives and partners, pointed to research demonstrating the efficacy of voice and touch interfaces for specific types of tasks. Presenters raised questions regarding interfaces such as BMW’s i-Drive and touch screens generally, favoring voice and console-mounted touchpads (ie. the Audi A8). The consensus opinion appeared to be that touchscreens will survive, thanks in part to Ford’s success in proving the value of the solution. On the other hand, i-Drive-like interfaces will likely continue to come under fire as what one executive described as a “linear keyboard.” Now more than ever, though, rigorous research is being applied to weigh critical HMI decisions and eyes off the road time is more than ever a deciding factor. Conclusions: The next step in the process of realizing the potential of smartphone integration is enabling application downloads. Several solutions have been proposed including: Direct handset display: Nokia Terminal Mode approach. Walled garden: Ford application deployment approach. Application validation: Delphi et. al. provide application validation. Single application: Handset application controlling access to all apps. App store validation: Apple, Blackberry et. al. provide application validation. Carrier validation: See above. What is likely to emerge is a hybrid of on-board/off-board application control shared between the vehicle and the mobile device within the context of an OEM’s walled garden. When available, server resources will assist with application functionality such as search or streaming data or content. But regardless of the source of data or service, the entire solution on-board and off-board will be encompassed by the OEM’s walled garden. The vehicle and data security associated with OEM control will increasingly be non-negotiable. Challenges to this ecosystem are already emerging as application developer candidates for the Ford platform are expressing frustration with the process of putting the Ford software developer kit to work. Ford is seen as slow to respond to developer needs, a problem that is not expected to be resolved soon. OEMs will never be able to move at developer speeds especially where vehicle safety, security and integrity are at stake. So, new voice-based interfaces and Bluetooth wireless connections have enabled a new branding proposition in the industry coinciding with growing demand for safe mobile phone connections, a youth-oriented demographic outreach (particularly in compact car segments), and the need to future proof cars to keep up with consumer electronics market advances. More than ever cars are defined by their human machine connections. Ford and Nuance have much for which to be thankful and many of those thanks ought to be directed to Ray LaHood in the Department of Transportation. Much as most industry executives are want to complain and criticize the DOT for its single-minded anti-distracted driving campaign (when drunk drivers are actually responsible for more damage), the effort has focused consumers on their risky behaviors, opened the door to creative solutions, and stimulated demand following the industry’s worst ever downturn. Additional insight: http://bit.ly/c0OLhT - Consumer Implications for Smartphone-Vehicle Connectivity  - Chris Schreiner - Automotive Consumer Insights http://tinyurl.com/34hidb5 - Smartphone Market Evolution and the Automotive Opportunity Implications - Mark Fitzgerald - Automotive Multimedia and Communications Service http://tinyurl.com/2qx88eo - Automotive Connectivity: Beyond Bluetooth Solutions - Mark Fitzgerald - Automotive Multimedia and Communications Service 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

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

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

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