Workshop: Portability Across telematics service providers

1. Workshop: Portability Across telematics service providers

2. Agenda • 15 mins • NMFTA HVCS: Who we are & What we do • TSP Portability: The Motivation • Open Discussion: Portability Use Cases • Prepared slides on use cases from OTAPI work • Meant to provoke discussion • Feel free to stop me and initiate group discussions

3. About Me • Sr. Cybersecurity Research Engineer at NMFTA for the HVCS • Previously: Reverse Engineer, Security Threat and Risk Analyst, Secure Operating Systems Designer and Embedded Systems Designer. • Now: Technical resource contributing across the various things the HVCS program is doing – a mix of the above. • I can break things ... • But I enjoy fixing things (for now).

4. About NMFTA • Industry non-profit representing about 500 companies operating in interstate, intrastate, and foreign commerce in both US and Canada • Our members operate close to 200,000 trucks on the road, representing over $100 billion in freight revenue • National Motor Freight Classification (NMFC) • Standard Carrier Alpha Code (SCAC) • Standard Point Location Code (SPLC) • Other activities to the benefit of the transportation industry

5. I am not here to sell you anything We don’t sell, buy or promote any products in this space and are self funded

6. HVCS Program “Bringing together private industry, government, trade associations, and academia to work on the transportation cyber security problem on a shortened time table”

7. NMFTA HVCS Activities • Conduct research • Raise awareness • Write bulletins and papers • Sponsoring industry research • Student research programs • Scholarship program • Other industry activities

8. Portability: The Motivation • Each telematics service provider has their own proprietary APIs and carriers must integrate their services into their business-critical operations • Payroll • Fleet Maintenance • Safety and Compliance • TSPs can go out of business, some already have • MF carriers need to do multiple TSP integrations to get resiliency

10. Portability Use Cases • State of Health Check • Backup ERODS generation • Data Export (no Data Import for now) • Driver Route Start/Stop/Update & Geographic Details Update • Driver Messaging • Compliance and Safety Monitoring • In-field Maintenance and Repair • Estimating Received Data Quality • Monitoring Vehicle Status • Monitoring Fleet Battery Status Extracted from real-world carriers

11. The Context of These Use Cases • At the outset of the work to produce the Open Telematics API • carriers were interviewed for their use cases • And during the collaboration • carriers offered more use cases • Each use case represents a concrete instance of how a carrier makes use of the APIs and data provided to them by the TSPs • OR something they presently can’t do efficiently and know that they need (e.g. state of health)

12. State of Health Check Users of telematics that is highly integrated into their operations need assurances of the state of health of the Provider's services. State of health query responses are either an 'all-clear' response indicating that the provider is not aware of any issues with its services at the moment of query or some details describing the contributing factors that have led to less than optimal operation. • State of Health Check • Backup ERODS generation • Data Export (no Data Import for now) • Driver Route Start/Stop/Update & Geographic Details Update • Driver Messaging • Compliance and Safety Monitoring • In-field Maintenance and Repair • Estimating Received Data Quality • Monitoring Vehicle Status • Monitoring Fleet Battery Status

13. Backup ERODS generation Carriers use telematics systems to maintain Record of Duty Status (RODS) compliance. Since the TSP will already supply compliant records to authorities directly, the carrier may only want to produce their own RODS in the event that compliant records need to be produced when a TSP is no longer available. i.e. as a backup process only. • State of Health Check • Backup ERODS generation • Data Export (no Data Import for now) • Driver Route Start/Stop/Update & Geographic Details Update • Driver Messaging • Compliance and Safety Monitoring • In-field Maintenance and Repair • Estimating Received Data Quality • Monitoring Vehicle Status • Monitoring Fleet Battery Status

14. Data Export (no Data Import for now) Carriers want to export all data from a TSP on a daily basis. These data exports could be used by carriers to complete mandatory processes during times of TSP outage or to restore data. • State of Health Check • Backup ERODS generation • Data Export (no Data Import for now) • Driver Route Start/Stop/Update & Geographic Details Update • Driver Messaging • Compliance and Safety Monitoring • In-field Maintenance and Repair • Estimating Received Data Quality • Monitoring Vehicle Status • Monitoring Fleet Battery Status

15. Driver Route Start/Stop/Update & Geographic Details Update1 of 2 Carriers need to understand the availability of their drivers -- within the current regulatory context of those drivers -- so that the carrier can ensure regulatory compliance and, more importantly, driver safety. They calculated driver’s availability by retrieving availability factors and optionally applicable breaks and waivers for a given time period. They also update the TSP on drivers duty status in cases where they are on-duty in a facility but not in the cab of a vehicle so that the TSP has a comprehensive view of availability. Carriers update their driver's destination and route during their trip. This allows them to react to changing weather conditions, accommodate the regulatory requirements on driving hours, optimizing follow-up activities after a trip, etc. They update the current route and/or destination. They also update the geographic details of stops on the route (e.g. correct entrances, temporary obstacles for loading docks etc.) • State of Health Check • Backup ERODS generation • Data Export (no Data Import for now) • Driver Route Start/Stop/Update & Geographic Details Update • Driver Messaging • Compliance and Safety Monitoring • In-field Maintenance and Repair • Estimating Received Data Quality • Monitoring Vehicle Status • Monitoring Fleet Battery Status

16. Driver Route Start/Stop/Update & Geographic Details Update2 of 2 Carriers plan destinations and routes for their drivers and inform the drivers of the plan via the in-cab components of a telematics system. They check for flagged vehicle events and conditionally create routes for the vehicle. Carriers receive notifications when drivers have completed their trip. They follow a fleet-wide feed of driver log events (ELD/ERODS) • State of Health Check • Backup ERODS generation • Data Export (no Data Import for now) • Driver Route Start/Stop/Update & Geographic Details Update • Driver Messaging • Compliance and Safety Monitoring • In-field Maintenance and Repair • Estimating Received Data Quality • Monitoring Vehicle Status • Monitoring Fleet Battery Status

17. Driver Messaging Carriers use telematics systems to message their drivers in a specific geographic area for various reasons, not the least of which is to notify the drivers of dangerous weather conditions in their area. by messaging all vehicles in a geographic area. Carriers also message their drivers by sending messages directly to a vehicle. Carriers need to enable their drivers to 'call-back' to the dispatch in a timely and safe manner. To do this they often rely on two-way messaging provided by the TSP. The drivers can create and send messages to dispatch at the carrier by using an interface on their in-cab displays. • State of Health Check • Backup ERODS generation • Data Export (no Data Import for now) • Driver Route Start/Stop/Update & Geographic Details Update • Driver Messaging • Compliance and Safety Monitoring • In-field Maintenance and Repair • Estimating Received Data Quality • Monitoring Vehicle Status • Monitoring Fleet Battery Status

18. Compliance and Safety Monitoring Carriers use telematics systems to monitor their fleets for accidents. They follow a fleet wide feed of Log Events (ELD/ERODS) events. Carriers use telematics systems to monitor compliance and safety for their operations. They process driver performance summaries for a given time period; and in cases where it is warranted, they modify driver user accounts using TSP portal account maintenance APIs • State of Health Check • Backup ERODS generation • Data Export (no Data Import for now) • Driver Route Start/Stop/Update & Geographic Details Update • Driver Messaging • Compliance and Safety Monitoring • In-field Maintenance and Repair • Estimating Received Data Quality • Monitoring Vehicle Status • Monitoring Fleet Battery Status

19. In-field Maintenance and Repair Carriers use telematics systems to preemptively perform (and react to) maintenance needs of their fleets. They follow a fleet wide feed of vehicle fault code events; and in cases where it is warranted, they dispatch in-field assistance via third-party services APIs. • State of Health Check • Backup ERODS generation • Data Export (no Data Import for now) • Driver Route Start/Stop/Update & Geographic Details Update • Driver Messaging • Compliance and Safety Monitoring • In-field Maintenance and Repair • Estimating Received Data Quality • Monitoring Vehicle Status • Monitoring Fleet Battery Status

20. Estimating Received Data Quality Carriers need to estimate certain data quality properties of their service for a given time period. To gain these estimates they post-process either the complete or vehicle only records. For example, estimates of received data latency can be obtained by processing downloads from either of the above and summarizing the difference between the created timestamps and server timestamps. • State of Health Check • Backup ERODS generation • Data Export (no Data Import for now) • Driver Route Start/Stop/Update & Geographic Details Update • Driver Messaging • Compliance and Safety Monitoring • In-field Maintenance and Repair • Estimating Received Data Quality • Monitoring Vehicle Status • Monitoring Fleet Battery Status

21. Monitoring Vehicle Status Carriers use telematics fleet Location Time History for multiple 'fleet dynamics modeling' use cases such as: Fuel Purchase Prediction, Fuel Consumption Performance Tracking, and Fleet Maintenance Planning. They process a fleet location time history over a specific period. Carriers use telematics systems for multiple, custom, business intelligence purposes where the overall health of their fleet is considered and fed into their own proprietary models They either process the state of the fleet for a given time period or follow a feed of fleet wide vehicle info. Carriers need access to raw J1939 vehicle frames for various custom fleet management tasks. To process the raw frames in 'real-time' they follow a feed of whitelisted J1939 frames. • State of Health Check • Backup ERODS generation • Data Export (no Data Import for now) • Driver Route Start/Stop/Update & Geographic Details Update • Driver Messaging • Compliance and Safety Monitoring • In-field Maintenance and Repair • Estimating Received Data Quality • Monitoring Vehicle Status • Monitoring Fleet Battery Status

22. Monitoring Fleet Battery Status Carriers need to monitor the battery voltage of their fleet of vehicles. To monitor these battery voltages in ‘real time’ they follow a feed of fleet-wide status events containing battery voltage. • State of Health Check • Backup ERODS generation • Data Export (no Data Import for now) • Driver Route Start/Stop/Update & Geographic Details Update • Driver Messaging • Compliance and Safety Monitoring • In-field Maintenance and Repair • Estimating Received Data Quality • Monitoring Vehicle Status • Monitoring Fleet Battery Status

23. We make most things public on:nmfta.org/pages/hvcs and github.com/nmfta-repo • Subscribe here for notices and alerts:hvcslistservice.nmfta.org Thank You! Ben Gardiner ben.gardiner@nmfta.org (no, I don’t know why this needs to be clickable in a presentation either) www.nmfta.org