Post on 25-Jun-2015
description
transcript
A World of Connected FleetsM2M meets the API Economy
Toralf Richter
@ToralfRichter :: tomtom.com/telematics2
Part 1The API Economy
16 Sept 2014
@ToralfRichter :: tomtom.com/telematics3
Platforms at Large :: Software Is Eating the World …
Digitally Transform or Perish
SaaS and Platforms
APIs Are the Teeth
Digital Transformation, Software as a Service, and the API Economy
16 Sept 2014
@ToralfRichter :: tomtom.com/telematics4
The API Economy :: It’s Like Sailing Good Hope
Openness & Best-of-Breed
Creativity & Reuse
New Paradigms, Some Already Visible Progress, and Lot’s of Adventures Ahead
16 Sept 2014
@ToralfRichter :: tomtom.com/telematics5
High-Level View :: The Magnitude of the Transformation
Taxis vs. Uber
Machine breakers did not stop industrialization either
Fierce Reactions Betray That Some Changes May Be Quite Fundamental
16 Sept 2014
@ToralfRichter :: tomtom.com/telematics6
Part 2Platform Strategy and API Portfolio for a World of Connected
Fleets
16 Sept 2014
@ToralfRichter :: tomtom.com/telematics7
Connecting Fleets :: The WEBFLEET® PlatformFleet Management for Operational and Non-Operational Fleets
• in-vehicle hardware
• 2 data centers, in-house engineering
• 15+ major mobile carriers
• sales: 25+ countries, active: 60+
• top 3 of fleet telematics (ABI)
• the .connect product family of APIs and developer toolkits
• developer program (DCPP) & 3rd party portfolio (AppCenter)
Details
> 30,000
customersunits online
> 400,000
> 1.5 million
hours driven
> 65 million
km driven
> 11.5 millionliter fuel
> 500 million
positions
A Business Day in WEBFLEET (July 2014)
16 Sept 2014
@ToralfRichter :: tomtom.com/telematics8
WEBFLEET.connect :: The Fleet Management APIThe Starting Point - Connecting Fleets with Custom Systems and Partner Applications
• Base Product: WEBFLEET® SaaS
• Introduced: 2004
• Monetization: Indirect
• Type: Web API (ReSTish and SOAP protocol flavors)
• Productized: yes
• Circulation: Public (documentation, examples) with Access Control (API key and credentials required)
• Eco-System: mid-size (between LSUD and SSKD)
• Audience: business integration, mobile app and web developers (external and internal)
• Use Cases: Route Optimization, ERP and SCM, job dispatch / workflow; TomTom Telematics Mobile Apps; special purpose FMS web appsAnd many more …
16 Sept 2014
@ToralfRichter :: tomtom.com/telematics9
LINK.connect :: Taking the Platform into the VehicleEnabling End-to-End Integration Between Back-Office and Vehicles
• Base Product: TomTom LINK black box
• Productized: yes
• Eco-System: small to mid-size
• Circulation: Public (documentation, examples), In-vehicle Bluetooth® interface has access control (pairing PIN, device identification)
• Use Cases: in-vehicle sensors (temperature, tire pressure, light, movement, …), inputs ( barcode / RFID, driver ID), outputs (printers), equipment control (salt dispensers, …)
• Monetization: direct & indirect
• Type: Bluetooth interface (SPP)
• Audience: IHVs, SIs, solution providers
16 Sept 2014
@ToralfRichter :: tomtom.com/telematics10
WEBFLEET®
TomTom LINK100
OBD.connect :: 3rd Parties Create the End ProductA Platform Approach to Entering the Non-Operational Fleet Market
OBD.connect SDK
End Product
Customer Specific App
Recorded Data
RT Data & Status
Configuration & SW Updates
Recorded Data
Configuration & SW Updates
Platform
API
Specialized API
Customer or 3rd
Party Services
Pla
tfo
rm
AP
I
• Base Product: LINK 100• Monetization: indirect• Type: SDK (Smartphone)• Audience: mobile developers• Introduced: 2014• Productized: yes• Circulation: semi-public • Eco-System: small (emerging)
16 Sept 2014
@ToralfRichter :: tomtom.com/telematics11
PRO.connect :: Customizable Driver Terminals
• Android-based open device platform concept, restricted to TomTom Telematics application distribution (made for business, not for play)
• the SDK combines TomTom Telematics fleet management functionality and general TomTom navigation and map access
• Scenarios are standalone apps (on-device and using) and applications that combine on-device functionality with WEBFLEET or 3rd party APIs
• Use cases: Daily Vehicle Checks / Duty of Care (UK), barcode, digital signature capture
Deploy and Run Custom Fleet Management Apps with the New PRO8 Series
• Base Product: PRO 8 series
• Introduced: 2014 (just ending beta)
• Monetization: indirect and direct
• Type: SDK (Android based)
• Audience: mobile developers
• Productized: yes
• Exposure: public
• Eco-System: small (emerging)
• Circulation: public (with identification)
16 Sept 2014
Questions?
Toralf Richter
Senior Manager Engineering
tomtom.com/telematics
toralf.richter@tomtom.com
@ToralfRichter
http://www.linkedin.com/in/toralfrichter dutchopenhackathon.com