1. OVERVIEW The Value of Engine Diagnostics Faults, Status, Voltage Email Notifications Reports: Idling/Time/Risk/Routing GO4 Device Setup Stanmex, Inc. Authorized Dealer for Geotab, Inc.

2. ◦ There is more involved than whether or not the ignition is on: ◦ How is the asset being driven  Identify harsh braking  Over revving the engine ◦ Fault Codes involving the fuel system can cause your asset to run too ‘rich’ drastically reducing the fuel efficiency of your vehicles.  Fixing a serious maintenance problem, such as a faulty oxygen sensor, can improve your mileage by as much as 40 percent. * according to http:// www.fueleconomy.gov/feg/maintain.shtml

3.  1996 vehicle manufacturers installed a diagnostic port into all vehicle to allow mechanics to plug a computer into the vehicle and ‘read’ what was occurring in the engine  There have been many evolutions to the basic protocols for light and heavy duty vehicles  2008 Introduces CAN- ‘Central Area Network’ All computer communication in the vehicle is processed on the CAN

4. CAN bus All of the vehicles systems communicate through the CAN bus By accessing the data on the CAN multiple vehicle systems can be monitored individually or in correlation to each other

5. GEO- ‘GAS’ All light duty vehicles including diesel powered cars and trucks including Ford F550 and lower all fit in this category. Supports OBDII/CAN protocol Mandatory in 2008 and newer vehicles Vehicles older than 2008 with OBDII protocols will offer limited data using an add on module (early 09) GEO –’Diesel’ All heavy diesel Vehicles Class 8 and up vehicles Supports J1939 protocol Older Diesel trucks offer a smaller data set using the J1708 protocol

6.  Active Fault Codes- these are faults that have occurred often enough for the Check Engine light to be triggered ◦ These are consistent and recurring indicating that a problem is developing

7.  Checkmate breaks the data from the engine down into three views: ◦ Summary Data-summarizes the fault activity ◦ Fault Data-details all of the faults the engine detects ◦ Status Data- Based on the firmware records information about what is going on in the vehicle

8.  The top vehicle has 76 fault Active codes  Indicates consistent and repetitive problem  The vehicle on the bottom is showing a random non- repeating fault

9.  A Fleet Manager notices a consistent fault  He calls the driver; the driver says the vehicle is not running right  The vehicle is diverted to the repair shop  This vehicle is less than two months old

10.  Is firmware driven ◦ Firmware defines what and how often engine data will be recorded ◦ Standard firmware records common engine values  Geotab builds the hardware and writes the software allowing for custom solutions when needed ◦ Development of custom firmware is additional  Engine Based Exception rules are used to identify issues of individual fleets

11.  Odometer from the vehicle  VIN (Vehicle Identification Number)  Heartbeat- Go Voltage monitoring  Fuel Level at each ignition on event  Engine Coolant Temp at each ignition off event  Active Fault Codes – Check engine light on

13. ◦ Economics  Reduce Spares -knowing that vehicles are always in running order allows fleets to reduce or eliminate spares  Longer Serviceable Life -properly maintained vehicles maintain a longer serviceable life reducing turnover expense  Less Expensive Repairs -problems are caught earlier reducing the damage and the cost of repair

14.  Every hour the vehicle is parked the voltage is sampled and recorded  Every sixth hour data is transmitted to the database

15.  Viewed in graph you see the battery fail

16.  Program the system to tell you before the battery fails

18.  Vehicle alerts mechanic that it needs service 2282 broke “battery voltage between 0 - 10 volts 2:19 AM 10/14/2008

19. REPORTS/FEATURES

20. HEARTBEAT – OVERNIGHT VOLTAGE READING DEVICE HEALTH MANAGEMENT

21. SENSOR ACTIVITY – Door Switch Stops A 1-hour door open event is highlighted

22. SENSOR ACTIVITY A green star displays the door opening. The numbers in boxes tell the sequence of stops.

23. IDLING A trip and activity summary report shows completed trips and highlights excessive idling – known ‘zoned’ stops are shown in green.

24. IDLING The idling location is displayed on the map by a single mouse click “View in Map”

25. IDLING Satellite map views often help put even greater perspective on where and perhaps why idling took place – for example sometimes service techs idle the engine for repairs and so it’s useful to see where and who was driving

26. SAFE DRIVING PROFILE The basic trip data can be profiled to identify speed. In addition, the 100 minutes of 1-second accident data can help reconstruct accident scenes

27. TIME CARD By using a Driver ID Key to clock in, a time card can summarize activity

28. ALERT Exceptions are processed as they are received by the software. An exception can be associated by work times, zone entry/exit, or a sensor trigger. Once the exception is processed – it can be 1) emailed, 2) windows pop-up and 3) reported

29. SAFETY If customer is hoping to alter driver behavior, consider the use of the buzzer that can sound an alert to a driver if, for example their seatbelt is not fastened when driving greater than X mph. It is one thing to record, display and report data, to effect behavior change, you need to interact with the driver in the moment. Risk Management Period: 10/8/2008 12:00:00 AM to 10/8/2008 11:59:59 PM Group Speed > 70 Speed >= 80 Speed >= 90 Ave. Speed Stops < 10 Mins Stops > 10 Mins Stops > 20 Mins Stops > 30 Mins Stops > 40 Mins Stops > 50 Mins Idling > 5 Mins Idling Time After Hours Trips Tampe r Signs Harsh Braking Total Miles Total Stops Driver 123400019.151000121:18:36000287

30. Zone your Fuel Stops – Alert stop time Example from a recent customer database – consider monitoring any off-site fueling activity as it may happen – check fuel purchase vs average consumption over time.

31. Monitor visits off-site A Congregation is when 2 or more of your vehicles are parked at the same off-site location.

32. Route Planning Checkmate 5.3.1 now includes basic route planning where you can generate a route by clicking on customer zones within Checkmate.

33. SETTING UP GO4 IN CHECKMATE GPS, Engine Diagnostics (CANBUS, OBDII, J1708), 8 sensor inputs, driver buzzer alert, GPS antenna, wireless antenna, Driver ID Wireless Options (CDMA, GSM, Wi-Fi, 900Mhz) Serial Connections: RS-232 Fully Software Supported – OTA updates/Gateway/SDK

34. Data Flow

41. GEOTAB HOLDS REGULAR WEBINARS ON HOW TO MAXIMIZE THE BENEFIT OF YOUR GEOTAB INVESTMENT CONTACT SUPPORT AT rick@stanmex.com to join our next webinar or organize a specific training meeting Stanmex, Inc. Authorized Dealer for Geotab, Inc.