The Connected Car in the Intersection
In the last blog post, (Staying Safe and Staying Connected – A Mutually Exclusive Conundrum?) we discussed the need to do a better job of integrating our connected lives into the car, making interactions more natural and less distracting. In this post, we will discuss the broader connected car ecosystem.
The connected car sits at the intersection of
The consumer, who demands the connected experience with services and applications that are both compelling and useful.
The government, which is responsible for road safety, traffic management, etc.
The vehicle manufacturers who want to create a great driving experience and generate customer loyalty while at the same time controlling the costs of development and support.
Various third parties who provide auto-related services. These include insurers (PAYD), fleet management, rental agencies, valet services, etc.
Of course, each of the above has their own viewpoint and criteria for what makes a great IVI platform. What's exciting is to see and enable a shared vision and objective -- to operate in the intersection. For instance a consumer wants post-sales support and service to be easy and convenient. The car OEM and the dealer want to provide good service to enhance customer loyalty.
Let's start by looking at the criteria a great IVI platform will be evaluated on from each of the viewpoints
- The consumer will evaluate an IVI system based on what it does for them and how easy it is to use. Does it enable the right usage models such as navigation, media, hands-free communications, information and diagnostics, driver assists, etc.? Is it intuitive and responsive? Are the right services and applications present, and can more services and applications be added, and can the system be kept up-to-date?
The government is mostly interested in safety as it relates to IVI systems. There are a few different aspects to vehicle safety and IVI systems. Most of the current government focus and vehicle safety laws related to in-vehicle infotainment and communication focus on the issue of driver distraction. But a growing area of interest is defining a common set of protocols for vehicle communication (V2X, or Vehicle to Vehicle and Vehicle to Infrastructure). V2X standards and protocols don't yet exist, but are actively being worked on by a variety of industry participants. V2X will enable such safety enhancements as a car signaling when it is in a hard braking situation so that cars behind it will be able to adjust, or notification of a disabled car before an approaching driver would be able to see it, or letting a driver know how long the next traffic light will stay green. Just like our current roads, we'll be looking for our governments to enable the infrastructure required. And common protocols and open standards that allow collaboration will be required to bring these capabilities to market.
Vehicle manufacturers want to attract customers by providing a compelling experience in the car, and they also want to keep a positive relationship with buyers after the sale. But they are also concerned about liability and cost. Vehicle manufacturers are increasingly looking for solutions to build from starting with a higher level of integration and capability already present so that they can speed time to market and focus development efforts directly on their differentiated experience. These solutions must be well supported by their developer and supplier ecosystems. Another feature that car manufacturcers will be looking for in the next generation of IVI platforms is the ability of that platform to be upgraded and extended so that it can stay relevant. And, vehicle manufacturers are increasingly looking to the open source community to help provide solutions that meet these needs. A few industry groups have formed to help define the specifications and requirements for these systems including; GENIVI, AGL (Automotive Grade Linux) and the recently announced Open Automotive Alliance.
Third parties are interested in getting access to information from the car that can enhance their services. These third parties are also looking for systems that implement open standards and common protocols so that data acquisition and management can be leveraged across multiple vehicle brands and types. Just like ODB II (On Board Diagnostics) provides a unified way to access information directly within the car, a unified protocol is required to access information when that car is connected to the cloud. Examples of these types of third party service providers include insurance companies that can provide Pay-As-You-Drive insurance, extended warranty service providers, valet parking services, etc.
In the next blog post we'll start looking more specifically at Tizen IVI and some of the components, protocols, standards and APIs that are being developed (in the W3C and other industry groups) to meet the above needs.
Also, as cars become more and more connected and able to communicate with each other, we have to address the overall security of the IVI system. It needs to be resistant to hacking which might turn the car into a projectile or broadcast false information to other vehicles. Look for a future blog entry specific to V2X, what usages are enabled by vehicles that can communicate, and the security risks that will need to be mitigated, or comment below with your thoughts.
See you on the road...
Tizen IVI Product Marketing