Cyril debunks the reality of a MarketPlace model for the Telematics sector. Highlighting a few important trends Looking at the key requirements for an open application platform to take shape and illustrating what Mobile Devices is able to do today to foster the concept of a telematics marketplace

1. Let’s All build a MarketPlace !

2. QUICK OVERVIEW Part 1: Opening suggestions Part 2: Fundamentals of a telematics OS and MarketPlace Part 3: How to build a telematics MarketPlace Part 4: Reality check

4. Complex ecosystem

5. No interoperability

6. Firmware basedASP TSP Map Network SIM Brands OEM Integrators Live Content Reporting Resellers

7. 4 MARKET AND SERVICES ARE MATURING SLOWLY Source: Licht Associates

9. MRM business case made

10. Demand is more complex

11. Multiple applications

12. New actors types

13. New devices

14. New verticals

15. Regional requirements

16. New applications merging the MRM and consumer marketsLarge screens overselling small ones OBD widely required Live traffic, speed limit alertsnow competitive advantagesin dispatch

17. 6 THE BATTLE IS ON FEATURE SET INTEGRATION, SPEED AND QoS, NOT JUST COST $ UI $ Features $ Speed $ QoS “Hardware agnostic” solutions don’t exist!

18. 7 WE ARE STILL LIVING IN THE PRE- iOS ERA Do you recognise this pattern? Service provision model breaks/ changes Volume growth Services multiply Complexity emerges Value understood Brand education push Hardware cost fall OS model

19. 8 WITH TELEMATICS, THE LACK OF OSIS FELT THROUGHOUT THE VALUE CHAIN OEM LEASING FLEET DRIVER Trafficspeedcam… Each Driver has different needs Task Management… ?? No visibility on the Fleet’s need Assets Management … ?? No visibility on the Leasing app ?? Diagnostics Safety… OEM specific priorities

21. Complexity not well supported in firmware environment

22. Calculation and data manipulation cannot be scaled on the embedded side

25. Multitasking between every services installed

26. In-car usage / adapted UI

27. Integration of each application with the navigation engine

28. Adaptation/ localization…

30. No carrier support/ low ARPUHow many apps are running here?

33. Drivers

34. SDK

35. Flexibility of Linux

36. License free

37. Compatibility with numerous VMCORE & eCall Black Box Black Box Smart screen Dongle PND PND 2 BUT MORE THAN THAT…

38. 14 Navigation AN OPEN TELEMATICS OSNEEDS TO INCLUDE A NAVIGATION ENGINE Rendering Routing GUI Embedded DB Announcement manager Remote diagnostic DriverProfiling Text toSpeech Push Messaging Navigation Tracking ScreenShareengine OBD Library Dynamic Navigation Engine Power management Optimisedwirelessprotocols Low level interface: GPS, GPRS accelero, battery,CAN, OBD… Memory management The Nav engine interact also with all the other embedded applications BUT MORE THAN THAT…

40. Multi applications

41. Performance

42. Reliable

43. Hardware agnostics

44. Built from the ground up with telematics in mindCORE

45. 16 MOBILE DEVICES PROVIDES AN OPEN OPERATING SYSTEM FOR THE TELEMATICS INDUSTRY We offer Telematics Service Providers the simplicity enjoyed by Consumer Electronics players PC & SmartPhones Telematics Today Telematics with Morpheus3

47. C++ control Vs. Java’s flexibility

48. Configuration tool : Ready Mix Pancake

49. The OS approach is not an alternative, it opens up more choices:

50. Advanced config tool to tune only the events

51. Ability to use a 3rd party developer

52. Brand or distribute an already-integrated app

53. Create your own solution from starch!

55. 19 MARKETPLACE MODEL: THE BEST WAY FORWARD FOR TELEMATICS - Screen based apps must be native: the service comes to the driver to maximize relevance and limit distraction - Screen based solutions are becoming pervasive and crossing over the consumer/ MRM words

56. QUICK OVERVIEW Part 1: Opening suggestions Part 2: Fundamentals of a Telematics OS and MarketPlace Part 3: How to build a telematics MarketPlace Part 4: Reality check

57. 21 THE PILLARS OF A TELEMATICS MARKETPLACE Developers have access to a full SDK to build applications on the devices and change its settings All devices run on the same Operating System: Morpheus3 OS Smart communication protocols handle all the services at once while restraining the bandwidth used

58. 22 BASIC FUNCTIONS Live Content & Maps Providers Resellers TSPWhiteLabel MarketPlace Customer specific solution Vertical specific application providers TSP Backend software providers Integrators TSP

60. Control the device through API Libraries

61. Control the communication gateway side through REST APIs

62. Control data plan’s cost through optimised Wireless Telematics Protocol

63. No joint ownership or shared IP between the MarketPlace and the TSP=> REDUCED TIME TO MARKET

65. All size fleets now looking for more integrated and comprehensive solutions

66. MRM companies often don’t have the infrastructure, R&D resources and sales processes to provide for evolving solutionSource: Licht Associates

68. Install a basic set of services

69. ASP build specific solutions on open SDK

70. White label solutions available to upgrade the basic service set

71. Already installed devices can be updated OTAResellers TSP TSP Integrators TSP

73. Live Traffic

74. Track and Trace

75. Hours of Service

76. Messaging

77. Task management

78. Signature recognition

80. Real-time speed camera alert

81. Local search (Yellow Pages)

82. Real-time parking place availability

83. Real-time fuel price

85. Shipped first with 5 services

86. Weather application pushed OTA to all devices in June

89. How many apps do we need in a car?

90. Regulations around the world

91. Who is actually developing

92. Who publishes on the marketplace today?

93. A business case for 3rd party developers?

94. Who is calling the shot on service sets

96. 33 Services available in the MarketPlace tomorrow

98. Build an Open Telematics OS (instructions above)

99. Train the TSP with your SDK

100. Build OS based black boxes for less than $100

101. Build screens that run unlimited number of apps for less than $400