The Connected Car is Here


Published on

Consumers in today's programmable world are deriving value from connected experiences that extend beyond their smartphones, tablets, and PCs. Come learn about GM OnStar's journey through 17 years of connectivity: how they are opening up to developers and creating a thriving digital ecosystem through APIs, apps, and data.

Published in: Technology, Business
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

The Connected Car is Here

  1. 1. The Connected Car is Here Nick Pudar
  2. 2. A Long Journey to APIs • GM has been pursuing connected vehicle solutions for many years • An API strategy is a significant pivot for an entirely new journey • A quick recap of our journey…
  3. 3. 1966 – Driver Aid, Information & Routing • • • • Audio traffic alerts Visual road sign minder Route navigation Coded voice communications via radio links • Required embedded magnets in roadways
  4. 4. 1987 – Mobile Communication Network • Focus on passenger communications to others outside the vehicle • Explore Vehicle-To-Infrastructure opportunities for safer travel • Required construction of private nationwide microwave tower network
  5. 5. 1994 – Project Beacon • Create innovative new business built on connectivity • Leverage strength of unique corporate assets • Successful demonstration of real value of opportunity • Governance structure too complex
  6. 6. 1996 – OnStar Corporation • Peace of Mind services – Safety & Security – Diagnostics – Navigation • Deep vehicle integration • Live Advisors • Leverages existing cellular network for communications • Leverages existing satellite network for geolocation
  7. 7. 2010: Leveraging APIs for our own Applications • In 2010 we applied our APIs to provide industry leading information access and control for our Volt customers • We have extended these features for all of our vehicles with the RemoteLink app
  8. 8. Today’s Reality: API Services • Remote APIs provide both One-Way and Two-Way vehicle interface • All API calls go through our secure back-office infrastructure • All vehicle connectivity is through OnStar’s proprietary channels
  9. 9. We Started a Developer Program This Year • SDK/Emulator for In-Vehicle apps • Remote APIs for cloud-based access • Actively engaging with developer community – Hackathons – Sponsored contests
  10. 10. Smartgrid Example • Utilities can use APIs to provide intelligent Demand Response solutions • Presence of renewable energy in grid can signal participating EVs to start charging • First instance of consumers having a real demand signal for renewable energy • See this example at the display booth
  11. 11. Urban Mobility Solutions Will Get Better Integration
  12. 12. Where next? (illustrative example) • Who is familiar with IFTTT?
  13. 13. IFTTT Connects Events and Activities through APIs
  14. 14. OnStar essentially has been doing this internally
  15. 15. More is possible
  16. 16. MUCH MORE: Intent Engines Become Accessible
  17. 17. Programmable personalization
  18. 18. Understanding Stakeholders Matters • A successful API implementation must consider total system needs and implications • Easy to address a single stakeholder • Harder to address two stakeholders’ needs • Difficult to develop a systemic solution
  19. 19. Stakeholders Needs
  20. 20. Thank you