Coverage maps for the three major cell providers can be accessed below under related links.

	Coverage map for T-Mobile
	Coverage map for AT&T
	Coverage map for Verizon
	Compare 4 Carriers Approximate Cellular carrier comparison (data may be different)

Yes and yes. The standard GO device receives signals from the GPS satellites to determine the lat/long, speed and altitude of a receiver (antenna in the GO device, phone, Garmin, OnStar, etc)on the earth with about 3 meters, generally less. The GPS data is then transmitted from the vehicle to a cellular communication network or an optional satellite communication network. Most customers use the cellular network modem because it is far less expensive than communicating on a satellite communication network. There are various cellular networks to choose from based on the data coverage in the area of asset operation.

When an asset needs to be tracked in very remote areas some or all of the time, and it is a high value asset, customers add a satellite modem to the standard GO system. This provides limited information in very remote areas such as oil fields. The detailed information is uploaded when the asset returns within range of the correct cellular network. This method is used to control costs because transmitting all data provided by the GO system would be cost prohibitive on a satellite communication network.

The vehicle is moving from the speed zone before it communicates with the server where the posted road speed is checked. The device must connect a second time for the alert to be triggered on the device in the vehicle. At 70 mph the vehicle may be several miles further before the driver is alerted. Adding the ProPlus service provides much faster results. This increases the communication rate with the server so the violation is recognized and sent back to the vehicle much more quickly than the standard rate used for Pro service. Communication in ProPlus takes place about every 20 seconds compared to every few minutes in Pro mode.

Differential Global Positioning System (DGPS) is an enhancement to Global Positioning System that uses a network of fixed, ground-based reference stations to broadcast the difference between the positions indicated by the satellite systems and the known fixed positions. These stations broadcast the difference between the measured satellite pseudoranges and actual (internally computed) pseudoranges, and receiver stations may correct their pseudoranges by the same amount. The correction signal is typically broadcast over UHF radio modem.

The term can refer both to the generalized technique as well as specific implementations using it. It is often used to refer specifically to systems that re-broadcast the corrections from ground-based transmitters of shorter range. For instance, the United States Coast Guard runs one such system in the US and Canada on the longwave radio frequencies between 285 kHz and 325 kHz. These frequencies are commonly used for marine radio, and are broadcast near major waterways and harbors.

Post-processing is used in Differential GPS to obtain precise positions of unknown points by relating them to known points such as survey markers.

The GPS measurements are usually stored in computer memory in the GPS receivers, and are subsequently transferred to a computer running the GPS post-processing software. The software computes baselines using simultaneous measurement data from two or more GPS receivers.

The baselines represent a three-dimensional line drawn between the two points occupied by each pair of GPS antennas. The post-processed measurements allow more precise positioning, because most GPS errors affect each receiver nearly equally, and therefore can be cancelled out in the calculations.

Differential GPS measurements can also be computed in real-time by some GPS receivers if they receive a correction signal using a separate radio receiver, for example in Real Time Kinematic (RTK) surveying or navigation.

The default data plan is 500 MB per device, per month. You can exceed this without knowing which will result in overage fees if you chose not to get a data cap protection plan. We highly recommend a data cap protection plan to avoid overages. There are several options which your account manager can review with you. It is very important to understand data conumption and to educate your employees so they do not consume needed data or create high overage fees. 

Three Types of Data Protection

• Overall cap. This simply limits the monthly use to the plan you selected (500 MB default). You can use all this data in 1 day or over the data plan cycle. 
• 50 MB per day (recommended). This limit your account to 50 MB of data usage per day. If you used 50 MB per day, you would be able to use the system for 10 days per data plan cycle. 50 MB x 10 days = 500 MB. The 500 MB overall cap is automatically included.
• 17 MB per day. This limit your account to 17 MB of data usage per day. If you used 17 MB per day, you would be able to use the system for 31 days per data plan cycle. 17 MB x 31 days = 500 MB. The 500 MB overall cap is automatically included.
• Data does not rollover to the next day or next month
  • If you have a special situation such as an accident, just contact Fleetistics support and the limits can be lifted until you communicate to reinstate them. It is best to make the request to remove and reinstate using a support case from your MyFleetistics account online. This documents the date, time and user for each request which protects you from overages due to miscommunication. You can even tell us when to reinstate it when you request to have it removed.
    
    Example: "Remove the daily data cap on camera Abc1234 for the next 24 hours." This would not remove the 500 MB data cap protection if this option was elected at the time of order or added prior to overages being incurred. 

The data plan cycle begins on the 17th of each month and billing is done on a calendar month. 

Larger data plans are available if needed. Talk to your account manager to learn more.

Overage Fees

Overage fees (OF) are on a per megabyte basis because that is how the cellular carriers calculate overages. It is very easy to run up your data consumption, especially when getting started. If you need more data during installation and training, just let us know. We'll remove the cap for the timeframe you identify and then reinstate it. During this time, data overages are possible so educate your team. Most overages result from employees viewing live streaming who do not understand the data cost model. 

CrewChief Data Plan Overview

It is important to know how the data plan works. Efficiently using data enables customers to realize low monthly service fees with the CrewChief system. Customers are responsible for managing the data plan, and paying overage fees, if applicable. It is also important when employee turnover takes place, the new system administrator is trained on how data works. There is no data pooling between dashcams and data does not rollover if not used.

The default data plan is 500 MB per device, per month but you can purchase larger plans if needed. 500 MB is generally enough for emergencies and limited spot checking. Your employees can exceed this without knowing which will result in overage fees if you chose not to enable daily data caps. We highly recommend enabling this feature. 

It is very important to understand data conumption and to educate your employees so they do not consume needed data or create high overage fees. Do not "hangout" watching videos.

Datacap Protection

• This optional service limits the monthly use to the plan selected. You can use the data plan in 1 sitting or over the billing cycle.

Data Allocation

Data allocation is a sub-service of the data cap protection optional service. After selecting the data protection, you will then choose how you want to allocate data during a data plan cycle. 

Running Out of Data? 

Customers can control the amount of data available in a day through the CMSv6 application. 

• 50 MB per day This limits your account to 50 MB of data usage per day. If you used 50 MB per day, you would be able to use the system for 10 days per data plan cycle. 50 MB x 10 days = 500 MB. The 500 MB overall cap is automatically included.
• ~17 MB per day. This limit your account to 17 MB of data usage per day. If you used 17 MB per day, you would be able to use the system for 31 days per data plan cycle. 17 MB x 31 days = 500 MB. The 500 MB overall cap is automatically included.
  
  • If you have a special situation, such as an accident, customers can remove the daily limit and reinstate it later.
    
    Example: "Remove the daily data cap on camera Abc1234 for the next 24 hours." This would not remove the 500 MB data cap protection if this option was elected at the time of order or added prior to overages being incurred. 

The data plan cycle begins on the 17th of each month and billing is done on a calendar month. 

Larger data plans are available if needed. Talk to your account manager to learn more.

Overage Fees

Overage fees (OF) are on a per megabyte basis because that is how the cellular carriers calculate overages. It is very easy to run up your data consumption, especially when getting started. If you need more data during installation and training, just let us know. We'll remove the cap for the timeframe you identify and then reinstate it. During this time, data overages are possible so educate your team. Most overages result from employees viewing live streaming who do not understand the data cost model. 

Yes. In Geotab, navigate to the Vehicles>(select vehicle)>More Details>Driver Feedback. Adjust the settings as needed.

YouTube Videos

How to Install Geotab's GO9 Device

How to Install Geotab's 16-pin T-harness

Geotab 9-pin Heavy Duty T-harness

Field Guide

Geotab Technical Guide

Install Checker

Submit form to confirm installation is correct.

You can create a custom parameter that sets a minimum volume of 1 and up to a maximum of 6.

You can apply the parameter listed below:

<Parameter Description='GoTalk min Volume level=6 (0 to 6)' Offset='175' Bytes='6' IsEnabled='true'/>

You can adjust the volume by varying between 1 and 6 in the Bytes='6' field. 

In this case it is set to 6.

Steps to Configure

• In MyGeotab>Vehicle select the vehicle. 
• Click More Details in the top menu.
• Select the Custom Parameters menu
• Add the parameter listed above and select Add New Parameter

There are many resouces to assist you with troubleshooting a GPS device. The linked content provides tips and resources beyond the Quick Test listed below. Always open a support case in MyFleetistics to log the date and time, register the issue, document the details and keep up to date on the resolution process. 

• Training Portal 
• Submit form to confirm installation is correct.

Quick Test

Open a support case in your MyFleetistics.com account and detail the testing steps completed prior to contacting support. This will make the process move much quicker. Opening a support case time date stamps all communication to hold everyone accountable for  the timely response to next steps.

1. Unplug the device for 1 minute and plug it back in. This will reboot the device. Like computers, this sometimes clears an issue. If it is a 3-wire unit, remove all power for for 1 minute.

2. Put the GPS device into another vehicle/assest that is tracking properly (be sure you have permission to see the other vehicle in the application group). Ensure you are in a known cellular data coverage area with line of site to the sky for best performance.

If the device tracks correctly in the second vehicle, the issue is likely the OBD/ECM or a wiring issue. Check each component and replace the faulty component. The GPS device and harness can be installed in another vehicle for testing both together. If they work, have the OBD checked by the OEM. 

If the device does not track in the second vehicle, there are two possible issus; a faulty GPS device or no cellular network connection. If other vehicles are transmitting in real-time in the same area, it is likely a faulty GPS device. Remember that most GPS devices will store data when they cannot connect to the cellular network and transmit when they reconnect. Understanding if a device is logging data or transmitting in real-time is important to determining if the device is faulty or there is no cellular coverage. You can always drive it home or around for a day or two to expose it to multiple coverage areas to be sure it is a faulty device and not a coverage issue.

When confirmed by support, a replacement device will be provided based on the warranty associated with the device. This process will be handled through the support case so both parties are seeing the same communication and are accountable for their part in the process. Support will review the case and take appropriate action. No waiting on hold or playing phone tag.

Opening a Support Case - Create the case and we'll get back to you!

Open a case from the Device Status Table seen below. When you open a case from this view, the device serial # and other information is inserted for you. Include the troubleshooting steps you took and the support team will investigate the issue and respond. You will get an email when an update is made to the case.

1. Navigate to Analytics& Reports>Device Status. [this process includes the device info for you.]

2. Check the system device status and create a case.

3. Open a case for any issue (technical, training, billing, etc) using this icon.

4. Filter the data in the table by clicking on the circle.

Open Support Case Here

Related Links

Related FAQs

Creating a Support Case Steps on creating a case in Fleetistics

Use the links below to locate the OBD port in a vehicle.

	CarMD – North America Only
	Innova DLC Locator - North America only
	The Diagnostic Box - North America & Europe
	Outils OBD Facile - North America & Europe
	Progressive

GoTalk adds a speaker to the Geotab GPS tracking platform to give the driver more specific feedback. Customers create the message to be read to the driver using the Geotab web interface. Let’s just say you can be as creative and colorful as you like. Installing the GoTalk speaker is very similar to connecting any other IOX device to the GPS device. Click here to download the full GoTalk installation guide.

There are a few key things to remember.

1. Make connections in the sequence outlined in the installation guide.
2. Connection GoTalk to the IOX port first.
3. Connect the OBD harness to the Geotab GPS device.
4. Turn the vehicle on.
5. The unit will be in test mode. Cycle the ignition a few times to disable it.

Note: Each time the GPS device loses power it will be in test mode when reconnected. Cycle the ignition a few times to turn it off or it will beep while driving giving you feedback on everything it does. Test mode is used for troubleshooting and very helpful when something is not working correctly.

You may want to create a rule that is triggered upon powering the GPS device so you can confirm the installation is correct. After installation, you can remove the rule. Read more

	Installation Instructions GPS and GoTalk installation instructions
	GoTalk Install Guide Download guide with instructions by Fleetistics
	GoTalk Technical Specifications & Guide Download guide with tech specs and instructions by Geotab

When connecting an auxiliary line to a circuit using the Geotab auxiliary cable, you can read the default value or invert the value. Ensure auxillary X, is used the exact same way throughout your fleet. If you are tracking a salt spreader being active with a default state value, it must be the same for all vehicles in your account. Geotab does not have a way to decipher differences between vehicles or auxillary state values.

To understand this better; on a light switch you have the on and off positions. Similarily, an auxiliary circuit provides a value of  0 or 1 based on the state of the circuit.. Lets say that 0 registers when "off" and 1 registers when "on". When the auxiliary is inverted, the values are inverted, 0 will represent "on" and 1 will represent "off". So the values are inverted in order to detect or monitor the opposite state. To get a more detailed explanation on how the auxiliaries algorithms work, please click on the link below.

Potential Scenarios:

1. You want to monitor the activation of emergency lights on an ambulance. The normal state of the circuit is powered off, so you want to see data when the lights are on.

2. A generator runs all the time to pump water from a basement in a skyscraper. The normal state of the pump drive is on, so you want to see data if the pump shut off. By inverting the aux input you can change how the data is reported.

Configuring AUX Inputs IOX-AUX self learning process & manual configuration

Heavy Duty Vehicles (J1939 and J1708)

Most heavy duty vehicles will have a round 9-ppin deutsch connector, depending on the age of the vehicle it may have a 6 pin. There are two potential protocols, J1939 and J1708. Below you will find the pin-out information for each along with their respective harness.

The new firmware release enables GO4v3, GO5 and GO6 devices with a 9-pin HD harness to support both J1708 and J1939 protocols simultaneously. In previous versions of firmware, a device installed in a vehicle with dual J1708 and J1939 protocols was limited to logging fault data from the J1939 bus only. The new firmware allows devices installed in vehicles with dual J1708/J1939 protocols to log J1708 faults also.

T-Mobile can roam into Canada but AT&T cannot. Customers based in the US which go into Canada must have T-Mobile devices and service  If the customer is based in Canada and roams into the US, Rogers is the correct option. Devices cannot be switched or upgraded so customers must get the correct device to start or purchase new devices.

Geotab's input / output expander, or IOX allows for simultaneous connections and communication between multiple devices and installed GO devices. This connection port allows for expanding the capabilities of the GO system by adding Garmin navigation devices, Iridium satellite modems, and Near Field Communications Driver ID solutions. This interface provides an open architecture for future expansion.

A common concern with plug-and-play type device is tampering. The plug-and-play device is super convenient to install but this means it can be easily removed just as easily. Serial numbered zip ties and extension cables provide two additional layers of protection but nothing if tamperproof.  For over 18 years Fleetistics has been answering questions about tampering and for 18+ years Fleetistics has said 'If a driver wants to tamper with a device, they will. The question is what are you willing to do about it to set an example?' Prior to plug-and-play devices all devices were hard-wired and they were tampered with at the same rate. Having strong HR policies in place are the best defense and deterrent.

Although there are several layers of deterrents for the plug-and-play devices ultimately there is a need to know if a device does not report correct and registers a power event. The Watchdog Report provides this data. Exceptions can also be created to notify users via email.

Devices are programmed to 'wake' from suspend mode when the ignition is off in order to register with the GO server. This handshake is pre-scheduled and if the device does not handshake an exception is recorded. The handshake takes place at various intervals depending on how long the ignition has been off. This process helps reduce the strain on vehicle batteries over extended periods. The battery voltage is reported with each heartbeat and can be monitored to prevent dead batteries. Vehicles not being used for over 30 days should have the device removed to prevent continuing batter drain. Please note this does not eliminate the service fee and add to your return on investment so use the devices as much as possible.

Heartbeat Scheduled After Ignition Off

Heartbeats are every 30 minutes after ignition off for the first 48 hours. Then every 23 hours until the next ignition on.

Geotab has been working on a DICKEY-john monitoring solution for many months and are now happy to announce the availability of this product as a “pre-release” product. The IOX-DJ unit connects up to the DICKEY-john Control Point Control System to provide distances, time, and amount of granular and liquid materials being spread during winter storm events. The data is captured through the IOX and transmitted up to MyGeotab where exceptions can be created and quantities spread determined.

About DICKEY-john

DICKEY-john’s customers range from individual farmers to original equipment manufacturers (OEMs). Amongst other markets, DICKEY-john provides systems for snow equipment vehicles which Geotab has focused on. Control Points®'s resourceful three-channel system gives you the power to control granular and liquid material application rates, spinner speed, and spread width.     

What are the features and benefits of DICKEY-john monitoring?

• View on a map which roads have been salted or sanded or had other material applied
• View areas on a map where blasting occurred
• Track distance, quantity, and time spent sanding, salting blasting or applying other DICKEY-john materials
• Compare application rates to ensure some drivers are not over or under applying material

Voltage parameters to utilize the Geoatb IOX-AUX to monitor electrical circuits turning on and off. Auxiliaries need to be utilized the same way throughout the entire fleet. Aux 1 must measure the same on every truck so exceptions and reports function correctly. How the auxiliary is measured can be inverted in the Geotab application. This means that instead of measure the "on" time, it is possible to measure the "off" time by inverting the setting.

Minimum = 3.3v

Maximum = 24v

Types of Odometer Data

Actual Odometer (AO)

AO is the value taken from the vehicle and is the value displayed on the dashboard. AO is calculated using a worm gear on the transmission. This gear can wear over time as can the other parts on the vehicle that impact the number of revolutions the gear makes. Tires are the biggest contributing factor to inaccurate odometer information . When a car or truck is made the tires are a specific size with 100% tread. If the tire size is changed or 50% of the tread is worn off, the diameter of the tire changes which changes the number of revolutions per mile made by the gear measuring and reporting the odometer value.

Virtual Odometer (VO)

VO is mileage calculated by the Geotab GPS device. The Geotab device measures the distance between GPS data points. The more data poins, the more accurate the calculation. When a vehicle does not report odometer data as part of the engine diagnostic codes, it uses VO to determine mileage. Customers on the HOS, Pro or ProPlus plan will receive engine diagnostics data which includes AO if avalailable from most fleet vehicles. Customers on the Base plan will not get AO data but will get VO data on the Trips report but will not be able to run an odometer report which is based on AO. Because VO is not impacted by things like tire size, VO is often more accurate than AO.

It is important to enter the starting odometer value when using VO. This is enter under Vehicles>(selecte vehicle)>Odometer.

Indicates Virtual Odometer in Geotab Vehicle Editor

Related Links
	Geotab Article
	Variations in Odometer Readings
	10 tips: Nab odometer roll-back scammers

Phone numbers cannot be added to a device. They are data only devices and do not support voice. Adding voice or increasing data consumption would be a different solution.

Overview

Tampering has been around since the introduction of GPS tracking when the only option was a 3-wire installation. Today, OBD devices are available and we find tampering to be about as frequent as we did 10 years ago. Tampering is best addressed before it happens by implementing a good policy and explaining the policy and why the investment is being made. To read more about how introducing GPS tracking to staff visit our website - click here. One thing to note about an HR policy is that a policy should not be implemented that will not be enforced.

The process of identifying tampering is an investigation. There are several factors and data to review before making a tampering accusation. If termination is considered, it is recommended that a support case be opened through the Help Center and the device, date(s) and times are identified, as well as the cause of the issue. The data will be reviewed and an analysis provided. Ultimately the call is yours. Erring on the side of the employee promotes good intentions and reduces complaints.  

Review the Installation

Proper installation is key to deterring, preventing and identifying tampering. Many videos are available on Fleetistics.TV covering installation. The goal of a proper installation is to place the device in a location that is not easy to get to. Once the location is identified, serial number zip ties and an install bracket help to secure all connections in a way that a driver will have difficult time getting around. These steps prevent disconnecting the device from the vehicle. Look for stretched zip ties, devices relocated,or screws loose in the dash, etc.  

When a Geotab device is unplugged it cannot report. There is no internal battery to keep it reporting. Although some devices have backup batteries it is considered a "last gasp" feature and offers little value. Devices with large backup batteries do continue to report when unplugged but they are not part of the Geotab product line. When a device is unplugged the system obviously stops reporting. This provides the device removal location because the Geotab device provides such high resolution tracking.  

Check the Data

 When the device is plugged back in (powered up) the data will indicate a power loss as seen below. This detailed data is not something you want to look at daily; it is raw data and can create confusion. Go To MyGeotab>Activity>InVehicle Accidents and Log Data. In the top left seach for "power" to get these two fault statements

1. Record Value: Reason for the record: Telematics device fault: all power removed - device restartedRecord Type: EngineFaultRecord
2. Record Value: 0 Reason for the record: Device power change (1=powered)Record Type: EngineStatusRecord.

Alerts can be created for a power loss. Again, it won't tell you when a device is unpowered but it will flag it when it receives power again. This exception is also displayed on the map and in an alerts report.

Check the odometer. If the device stops reporting or indicates a power loss, note the odometer. When the device starts to report again compare the odometer values to see if the odometer increased. Increases indicate driving while the device was not powered or the GPS signal was somehow blocked.

The map is also a good place to look. If the device shows it goes offline at one location and appears at another AND you have a power or GPS signal loss in the detailed data, there was an issue.

When a Geotab device is not being driven it transmits a heartbeat every 4 hours. By creating a Watchdog report on your dashboard or as an email attachment, you can quickly see which devices skip their heartbeat update.

The Device Status table in your MyFleetistics account is a location to see devices not reporting for multiple days from your MyFleetistics.com home page. You also do a health check from this table as well as open a support case without calling the help desk.

For the most up-to-date version of this document, please visit: goo.gl/fLCGgd.

The ruggedized telematics device is designed to withstand exposure to weather elements and environmental particulates. It can be installed outside of a vehicle’s cabin. Harnesses are available for specialty installations or for keeping the diagnostic port exposed if desired.

Read important related safety information and limitations of use following these installation instructions. Read and follow all instructions and warnings to prevent serious injury and/or vehicle damage.

Professional Installation Required — Installation of the rugged telematics device requires the installer to have sufficient technical knowledge and expertise for mobile device installation and integration into modern vehicles, i.e. Authorized Installer certification or equivalent.

Installing Your Telematics Device

Preparing For Installation

Before installing your device, please document your device serial number. You will need this information at a later time to verify your installation.

1. Verify that we support your vehicle by carefully reading the device release notes at goo.gl/fZURff or from the vehicle specific installation notes at goo.gl/MCIXt0. If you have any questions or concerns, please consult your Authorized Reseller.
2. Ensure no dash warning lights are on in the vehicle while it is running, and that all other functions, such as headlamps and flashers, are working prior to installing the device.

WARNING! Do not attempt to install, re-configure, or remove any product from a vehicle while the vehicle is in motion or otherwise in operation. All installation, configuration or removal must be done only in stationary vehicles that are securely parked. Attempting to service devices while the vehicle is in motion could result in malfunctions or accidents, leading to death or serious personal injury.

Installation in Four Steps

1. Locate the vehicle’s engine diagnostic port typically found in the driver’s area at or below knee level.

   Align the OBD connector on the HRN-RS12S2 (sold separately) with the vehicle diagnostic port and push in place.

   Note: Heavy-duty vehicles use a different connector system. Contact your Authorized Reseller for heavy-duty connector applications or for extension harnesses should it be necessary to place your device away from the engine diagnostic port.

2. Connect the 12-pin male connector on the device to the 12-pin female connector on the HRN-RS12S2 as shown and click into place. Ensure that all connections are secure. All three lights on the device will flash briefly.

3. If you are also installing an IOX, connect the 6-pin female connector on the device to the 6-pin male connector on the HRN-RX06S4 and click into place.

   Connect the female mini-USB connector on the other side of the HRN-RX06S4 to the male mini-USB connector on your IOX. Ensure that the two USB connectors are secured with a zip tie.

   With the vehicle parked outdoors to locate satellites and vent exhaust fumes, start the vehicle and allow it to run for approximately 3 minutes.

4. During this time period you will notice the Red LED will power on and light up on the face of the device. Shortly afterwards the Green and Blue LEDs will light up when the device connects to the cellular and GPS networks. This initial startup may take several minutes to complete.

   Once all three LEDs have lit up, select a location to attach your device. Drill 5/32 inch pilot holes first then secure the device into place using the supplied Hex Washer-head screws. Ensure that you install your device in a location where the wires will not interfere with the safe operation of the vehicle.

The 6-pin weatherproof female connector of the telematics device comes covered with a sealing cap for waterproofing and dustproofing. Remove the cap only if you plan on using an IOX (requires HRN-RX06S4 adapter cable). Otherwise, keep the cap in place with the arrow facing towards the lock clip located at the top of the 6-pin female connector as shown. Attaching the sealing cap in any other orientation will not guarantee a waterproof and dustproof seal.

WARNING! All in-vehicle devices and related cabling must be securely fastened and kept clear of all vehicle controls, including gas, brake and clutch pedals. This requires the use of a cable tie when securing the device or any extension harness to the OBD connector, securing both sides of the harness. If you do not use a cable tie, vibration in the vehicle can lead to a loose connection which could indirectly cause the vehicle’s engine computer to fail, loss of vehicle control and cause serious injury. Inspect devices and cabling regularly to ensure all devices and cabling continue to be securely attached.

WARNING! If at any point after an in-vehicle device is installed a warning lights up on the vehicle dash or the vehicle stalls or has a marked drop in performance, shut off the engine, remove the device, and contact your reseller. Continuing to operate a vehicle with these symptoms can cause loss of vehicle control and serious injury.

Verify Your Installation

To check the status of the device you have installed, navigate to installmygps.com. On the web page, fill in your name, the company, and the device serial number, which was recorded earlier. Once complete, click Log Install.

Light Duty OBD2 Vehicles

Most light duty vehicles have what is called an ALDL connector and the typical location is on the driver's side. The ALDL connector has 16 pins and looks like:

With respect to GPS modules, they are merely receivers operating at two low power radio signals (L1 – Civilian and L2-Military). The civilian frequency is 1575.42 MHz in the UHF band. I am not aware of any documentation/literature where a GPS module’s radiated emissions has been shown to cause interference. This is a signal we are all being hit with every day just like music radio signals. GPS units simply receive the broadcasted signal. 

In addition to using FCC compliant RADIO and GPS modules, the Marcus Radio Modules have passed FCC Part 15 Class A (Commercial/Industrial/Vehicle) or Class B (Residential/In-home) specifications. Part B is recommended for any consumer product in close proximity to a user’s unintentional emission sensitive areas (head/chest) and include cell phones, calculators, radios, computers, mp3 players, etc…  

• Coleman GPRS – FCC Part 15 Class A
• MRM Tuna – FCC Part 15 Class A
• MRM Wahoo I/II – FCC Part 15 Class B
• FCC Grant Attached  

Our devices also undergo PTCRB (GSM/UMTS Standards Body) certification for the purposes of isolating any unintentional emissions that might interfere with carrier frequencies, towers, communication, etc… These tests are based on our recommended product configuration including antenna placement and proximity to the radio module.  

The FDA and the Health Industry Manufacturer’s Association  (HIMA) specifically recommends a separation of six inches between any handheld wireless radio and a pacemaker. In fact, you will find this caution in Garmin manuals for handhelds with radio receivers/transmitters.  Given the prevalence of GPS and mobile phones, it is expect that modern pacemakers are accordingly shielded (see below).  

The American Heart Association states:

• “Modern pacemakers have built-in features to protect them from most types of interference produced by other electrical devices you might encounter in your daily routine.”
• “Cellphones available in the United States (less than 3 watts) don't seem to damage pulse generators or affect how the pacemaker works. “  

The AMA also publishes a list of devices that may interfere with pacemakers. Currently, no GPS handheld or vehicle mounted devices are listed.

Differential Global Positioning System (DGPS) is an enhancement to Global Positioning System that uses a network of fixed, ground-based reference stations to broadcast the difference between the positions indicated by the satellite systems and the known fixed positions. These stations broadcast the difference between the measured satellite pseudoranges and actual (internally computed) pseudoranges, and receiver stations may correct their pseudoranges by the same amount. The correction signal is typically broadcast over UHF radio modem.

The term can refer both to the generalized technique as well as specific implementations using it. It is often used to refer specifically to systems that re-broadcast the corrections from ground-based transmitters of shorter range. For instance, the United States Coast Guard runs one such system in the US and Canada on the longwave radio frequencies between 285 kHz and 325 kHz. These frequencies are commonly used for marine radio, and are broadcast near major waterways and harbors.

Post-processing is used in Differential GPS to obtain precise positions of unknown points by relating them to known points such as survey markers.

The GPS measurements are usually stored in computer memory in the GPS receivers, and are subsequently transferred to a computer running the GPS post-processing software. The software computes baselines using simultaneous measurement data from two or more GPS receivers.

The baselines represent a three-dimensional line drawn between the two points occupied by each pair of GPS antennas. The post-processed measurements allow more precise positioning, because most GPS errors affect each receiver nearly equally, and therefore can be cancelled out in the calculations.

Differential GPS measurements can also be computed in real-time by some GPS receivers if they receive a correction signal using a separate radio receiver, for example in Real Time Kinematic (RTK) surveying or navigation.

Divide the accelerometer value by 9.8 to get g-force.

The firmware for all live devices is managed by Geotab. The most current release firmware is pushed over the air to the devices on a regular basis.  You can go HERE to view what the current released firmware versions are. If you are experiencing issues with your device you should verify that it is running the latest version and if it is not let your reseller know so that the device can be set to update.

Once the device has been set to update, use the following procedure to update the firmware:

1. Ignition on cycle - make sure that the green LED turns on as this indicates that it has connected to the cellular network.
2. Ignition OFF
3. Wait 7-10 minutes for modem to disconnect and dowbload firmware, make sure that you leave the device plugged and ignition is OFF during this time.
4. Ignition ON and drive away

In the US, the Moss Magnuson Warranty Act of 1975 specifically prohibits manufacturers from voiding the warranty due to aftermarket additions to the vehicle. Furthermore, Geotab has spent considerable time ensuring that our products cannot cause harm to the vehicle.

The GO Device Issue Detection Report provides insight into the device related issues present in your vehicle fleet. It includes a breakdown of the devices experiencing performance issues, as well as how these issues can be addressed in order to restore normal device functionality. The Issue Detection Report is an extremely useful tool that contributes to strong telematics device uptime in your fleet. This report applies to GO Series devices only.

	Device Issue Detection Learn more
	Device Issue Detection Download report

No, the devices will go into sleep mode when the vehicle is turned off and will only draw about 5 mA of current. A typical car battery has a capacity of 50 Ah, which means it will take over a year before the device can come close to depleting the battery.

How to archive a vehicle/asset

Category:  Removing a device from the system by archiving it, to preserve the data from the device. This is useful if the data is ever needed after the device has been removed. 

Purpose: This article will go over how to remove a vehicle/asset by archiving it which will keep all of the data the device has reported for at least the last year.  

Procedure:  From the left-hand side menu in Geotab click on Vehicles & Asset(1),  Choose the vehicle/asset you would like to remove, and click remove from the top of the Asset edit page(2), When the Remove device window appears, click Archive Assets(3).

Additional Note:  If you are still having issues trying to archive a vehicle, please open a support case for further assistance. The link below contains instructions on how to create a support case. https://www.fleetistics.com/support-cases-made-easy/.

How to check vehicle faults 

Category:  Engine & Maintenance 

Purpose:  This article will go over how to check any faults for a device/vehicle. This is useful as it can provide further insight on what issues a device could be having, it also shows if the device has been removed from the vehicle. 

Procedure:  From the left-hand side menu click on the Engine & Maintenance(1), Engine and Device(2), Faults(3), Fill in the options by using the filter button at the top(4) according to the device, date period, and fault you are looking for. You could also fill out a date range and vehicle and let the system pull up all faults that took place for that vehicle during the time period selected. 

Additional Note: If you are still having issues when trying to find a vehicle fault, please open a support case for further assistance. The link below contains instructions on how to create a support case. https://www.fleetistics.com/support-cases-made-easy/.

Please check this Knowledge Base article.

https://kb2.myfleetistics.com/index.php?action=faq&cat=29&id=40&artlang=en

Submit form to confirm installation is correct.

The quickest thing you can do for an initial test is to swap the GPS unit not working one from a known working vehicle. If the GPS units continue to exhibit the same performance in the new vehicle, there is a high chance there is an issue with the GPS device. If it works in a second vehicle, the issue is likely with the vehicle. Sometimes, new or unique vehicle models, have a conflict with the vehicles computer. If you think this is the case, open a support ticket and share your detailed findings. 

Resources

• Geotab GO9 Support Document
• How to Install Geotab's GO9 Device
• How to Install Geotab's 16-pin T-harness
• Geotab 9-pin Heavy Duty T-harness
• Geotab Technical Guide

Install Checker

Submit form to confirm basic installation is correct.

It is important to perform this and other troubleshooting steps. Returning a device found to be working will result in a $50 bench testing and postage fee.

GO Device Light Definitions

On initial power-up, all three LEDs on the GO device will flash once in unison indicating that the device is receiving power. If none of the LEDs flash, this is an indicator that the device is not powered on.

After the initial flash, the Green LED will briefly turn solid indicating that the modem is connected to our servers. The Blue LED will also briefly turn solid indicating that the GPS is working. Both LEDs will eventually shut down if ignition is turned off.

Once ignition is turned on, the following are common light sequences indicating an issue:

• No lights
• Red only
• Red and Blue only (most common)
• Red and Green only

Fully seat the device to the harness.

Device Status Table

Use the device status table to monitor devices. Frequently Asked Questions - Device Status Table (myfleetistics.com)

Additional Resources

• GPS Installation Easy Instructions For Geotab OBD Devices (fleetistics.com)
• Support And Training - 24/7 Access To Help Resources For GPS (fleetistics.com)
• Device Checker
• Fleetistics.TV - YouTube
• Submit form to confirm basic installation is correct.

This article is designed to assist drivers to get started using the Geotab Drive mobile app for ELD and FMCSA compliance.  You can register for our online driver training webinar here and you can follow the steps below to get started quicker. Fleetistics customers can attend as many webinar training sessions as needed.

Special Note: Drivers must log off the Drive app, not just log out for the day. This is a common mistake that leads to many administrative issues. When a driver logs off the Drive app, the app prompts the driver to make selections that ensure compliance and smooth backend administration.

STEP 1 Download the Geotab Drive app 

Click the image to access the downloads.

Workflow

Step 2 - Logging In For The First Time

The most frequent support call we receive is from drivers who cannot log in, usually the first time.  Your ELD Account Administrator will create your credentials as described below and provide them to you.

To log in for the first time you will need:

1. Your user name (email is recommended but not required)

2. Database name for first login only (get this from your MyGeotab system administrator)

3. Password – set by your administrator

Step 3 - Once Logged In

1. Select your vehicle
2. Add or remove assets such as trailers and shipments
3. Accept or reject unassigned logs
4. Verify unverified logs
5. Inspect the vehicle – you will be placed on duty as soon as you begin the inspection

Once the inspection is completed, you will land on the dashboard screen shown below.

You are automatically moved from On Duty status to Driving status when you drive.  The screen will change to show your countdown timer showing the remaining drive time available to you.

Any movement of the vehicle while you are the assigned driver will generate driving logs assigned to you. It is very important to log out of the app at the end of your workday.  Logging out disassociates the vehicle and causes driving events to remain unassigned.

Step 4 - Get to Know Your HOS Dashboard, Tools, and Help Content

Your HOS dashboard allows you to easily access your HOS and DVIR screens, read and respond to messages if that feature is enabled, change into inspection mode, and use the add-ins your Administrator has installed.  There is also a navigation menu at the bottom of the screen.

If you are using an iPad, your dashboard will look something like the view below. On a smartphone, the icons will be arranged vertically and you may have to scroll to see them all.

If you do not see the ELD Info button on your dashboard, please contact your Administrator and ask them to add it.

It is recommended that all drivers register for and attend our online training webinar for a full overview of the app.  Use this link to register now.

Recordings of our live training are available below.

ELD Video Driver Training Part 1 (15 min) 

ELD Video Driver Training Part 2 (15 min) 

ELD Video Driver Training Full version (30 minutes)

Spanish ELD Video Driver Training (39 minutes) 

Geotab ELD Driver Content

1. Diagnostic Events and Malfunctions (Must be printed or available as electronic files and kept in the cab as per the law).
2. ELD Manual  (Must be printed or available as electronic files and kept in the cab as per the law.)
3. Data Transfer Description (Must be printed or available as electronic files and kept in the cab as per the law.)
4. A supply of blank driver’s records of duty status (RODS) graph-grids sufficient to record the driver’s duty status and other related information for a minimum of 8 days (Must be kept in the cab as per the law)
5. Driver’s Guide to HOS (Recommended)
6. DVIR Workflow (Recommended)

Installing the ELD Info app provides you with links to required documents so you will always have the latest version. If you do not have the ELD Info button on your dashboard, ask your Administrator to install it.

Yes. This can be updated in the database directly, or the Import DVIR List tool allows you to copy and paste a list from Excel into the Geotab system. Each line must be formatted in the form "part|defect|severity" in order for a successful import. Once uploaded, navigate to Administration > System > System Settings. From the General tab, scroll down to "Default Vehicle Defects List". Select your new list and click Save when complete.

This depends on the security clearance for drivers in MyGeotab. A driver can be given permission, or restricted, to add trailers to the database. 

If there is a fixed list of trailers, do not enable drivers to add trailers. Drivers will add the same trailer many times instead of search the list. This leads to significant  administrative issues. 

If drivers are using unique trailers consistently, train them to search the list before entering another trailer. You should have a process to idenfity duplicate trailer names, even if they are actually different trailers. Trailers from different companies may use the same trailer name which will be indistinguishable during an audit. 

No. Under the mandate, all driving time must be accounted for. However, logs can be assigned to an unknown driver, annotated, or ignored.  

If logs are not verified within 14 days, the carrier will have to print the logs and obtain a physical signature from the driver. They will not be compliant until the driver verifies their logs.

No. A motor carrier must either explain why the time is unassigned or assign the time to the appropriate driver.

The app automatically switches to ON when the vehicle stops moving for 5 minutes. If the driver manually changes to ON, a duplicate log is created.

No, but it does count toward ON-Duty time.

There is a purging feature that can be defined by the user on how far you want to go back and the purging frequency currently in beta.

The FMCSA requires that six months of driver logs and three months of DVIR data must be available for audit.

To access this feature in MyGeotab, follow these steps:
1. Navigate to Administration > System > System Settings
2. Select the Purge tab a. Note: if you do not see this tab, be sure that the Feature Preview setting is turned on in your user profile.
3. Switch "Routinely purge older data" to ON and adjust settings.

No. The driver will only be able to view vehicles within their assigned group.

Through their user profile in MyGeotab.

Engine and location data are collected and stored on the GO device. Once the vehicle returns to coverage, this data is sent to MyGeotab, then back to the Drive App. If you are out of cellular coverage often, you may want to connect the driver's tablet or smartphone directly to the GO device using IOX-USB to update without the need for a cellular connection. The cable connects to the devices charging cable and also provides power to charge the tablet or phone.

You can search this Knowledge Base for ELD or click the links below to external resources.

General Information about the ELD Rule | FMCSA (dot.gov)

Ruleset Matrix

3. Who must comply with the electronic logging device (ELD) rule?

A3. The ELD applies to most motor carriers and drivers who are currently required to maintain records of duty status (RODS) per Part 395, 49 CFR 395.8(a). The rule applies to commercial buses as well as trucks, and to Canada- and Mexico-domiciled drivers.

The ELD rule allows limited exceptions to the ELD mandate, including:

• Drivers who operate under the short-haul exceptions may continue using timecards; they are not required to keep RODS and will not be required to use ELDs.
• Drivers who use paper RODS for not more than 8 days out of every 30-day period.
• Drivers who conduct drive-away-tow-away operations, in which the vehicle being driven is the commodity being delivered.
• Drivers of vehicles manufactured before 2000.

No. Personal Conveyance is considered OFF-Duty time.

E-mail and web services

No. However, the log should be annotated for compliance.

Paper logs can be used for 8 days. If the vehicle is in use for longer than 8 days, an ELD is required.

When the vehicle travels over 5 mph, the system will create an automatic Drive log. This can happen if a driver moves his vehicle while off duty or in sleeper berth status, and will interrupt the consecutive hours of rest required. If the driver was still logged into the app it will assign that driving to him/her and place them on duty. If logged out, when the driver logs in it will be presented as unassigned and prompt the driver to accept or reject the log. If the driver accepts this log, it will retroactively change their status. 

Frequently Asked Questions (FAQs) - ELD Rule

ELD FAQ Categories

• General Information about the ELD Rule

• HOS Rules - Definitions and Interpretations

• ELD Exemptions

• Voluntary Usage and Compliance Phases

• Supporting Documents

• Editing and Annotations

• Harassment

• ELD Functions

• ELD Data Transfer

• ELD Malfunctions and Data Diagnostic Events

• ELD Accounts

• ELD Registration and Certification

• Differences between AOBRDs and ELDs

• Differences between AOBRDs and Logging Software Programs

• ELD Technical Specifications

• ELD Manufacturer Compliance

• Automatic On-Board Recording Device (AOBRD)

• HOS Ruleset Matrix

General Information about the ELD Rule

Per FMSCA requirements, drivers are required to have the ELD manual in their possession. It can be in paper or electronic form.

Geotab can help you meet compliance, optimize your fleet, increase productivity and much more. Through this webinar learn how to optimize your fleet to prepare for the enforcement of the ELD mandate.

Getting Started with HOS Admin Geotab can help you meet compliance, optimize your fleet, increase productivity and much more.

ELD Benefits

• ELDs make it easier, simpler, and quicker to keep driver logs.
• ELDs limit mistakes and reduce form and manner errors.
• ELDs provide information to drivers and motor carriers so that drivers can better manage fatigue and schedule issues.
• ELDs correctly record location and accurate information to easily track duty status.
• ELDs are a good management tool and back office asset to improve productivity and enhance compliance.
• With ELDs, there is less paperwork, and driver logs are orderly, clear, and accurate.

What Do I Need to Know?

The ELD Rule applies to most motor carriers and drivers who are currently required to maintain records of duty status (RODS). The rule applies to commercial buses as well as trucks. Canada- and Mexico-domiciled drivers are included, unless they qualify for one of the exceptions to the ELD rule.

ELD Rule Exceptions

The following are not required to use ELDs (but carriers may choose to use ELDs even if they are not required):

• Drivers who use paper logs no more than 8 days during any 30-day period.
• Driveaway-towaway drivers (were the vehicle driven is the commodity) or the vehicle being transported is a motor home or a recreation vehicle trailer (at least one set of wheels of the vehicle being transported must be on the surface while being transported)
• Drivers of vehicles manufactured before model year 2000.

What Do I Need to Do?

Carriers must evaluate and select ELDs, and ensure they are installed and drivers and administrative staff are trained to use them by the deadline that applies (December 16, 2019 for carriers using AOBRDs or December 18, 2017) for those using paper logs or logging software.

Drivers must understand and be able to use ELDs by the required deadline, including how to annotate and edit RODS, certify RODS, and collect required supporting documents. You will also need to know how to display and transfer data to safety officials when requested.

Under “more details” in the Geotab>Vehicles>device name>Vehicle Edit>More Details>Device Editor>Detailed Device Info.

It appears much harder to find than it is. Basically get to where you can edit a devices details and click More Details in the top menu on the right.

In the device editor change these settings.

1. "Turn GPS receiver off: must NOT be set on “immediately” but to "10 Minutes after the ignition is turned off".

2. Set "Periodically wake GPS" should be turned "on".

Once the steps are taken the device will automatically change status after 5 minutes of no movement.

Types of Odometer Data

Actual Odometer (AO)

AO is the value taken from the vehicle and is the value displayed on the dashboard. AO is calculated using a worm gear on the transmission. This gear can wear over time as can the other parts on the vehicle that impact the number of revolutions the gear makes. Tires are the biggest contributing factor to inaccurate odometer information . When a car or truck is made the tires are a specific size with 100% tread. If the tire size is changed or 50% of the tread is worn off, the diameter of the tire changes which changes the number of revolutions per mile made by the gear measuring and reporting the odometer value.

Virtual Odometer (VO)

VO is mileage calculated by the Geotab GPS device. The Geotab device measures the distance between GPS data points. The more data poins, the more accurate the calculation. When a vehicle does not report odometer data as part of the engine diagnostic codes, it uses VO to determine mileage. Customers on the HOS, Pro or ProPlus plan will receive engine diagnostics data which includes AO if avalailable from most fleet vehicles. Customers on the Base plan will not get AO data but will get VO data on the Trips report but will not be able to run an odometer report which is based on AO. Because VO is not impacted by things like tire size, VO is often more accurate than AO.

It is important to enter the starting odometer value when using VO. This is enter under Vehicles>(selecte vehicle)>Odometer.

Indicates Virtual Odometer in Geotab Vehicle Editor

Related Links
	Geotab Article
	Variations in Odometer Readings
	10 tips: Nab odometer roll-back scammers

Geotab Drive HOS Certificate
PDF download of full certificate letter

System Requirements
Android
• Android 4.4 or higher
• 7-inch screen preferred
• Capacitive touch screen preferred
• Built-in cellular modem (3G or LTE) with data connection
• Built-in GPS
• Certified by Google, with access to the Google Play Store preferred
iOS
• iOS 6.0 or higher
• 7-inch screen preferred
• Capacitive touch screen preferred
• Built-in cellular modem (3G or LTE) with data connection
• Built-in GPS
• Certified by Apple, with access to the App Store preferred

Email: ELD@dot.gov

Phone: 800-832-5660

Website: General Information about the ELD Rule | FMCSA (dot.gov)

Click the link to review detailed information on the various rulesets as reported by Geotab.

https://docs.google.com/document/d/10g2IAP8WjYQveYb-BEOEeEuElE2EOtBH4L13fRyeeTI/edit

Geotab accelerometers measure distance over time (gravitational force) in meters per second squared in three dimensions. We use sharp changes in accelerometer data to infer vehicle events such as harsh cornering. This data can be found by going to Engine & Maintenance > Engine and Device... > Options > Acceleration side to side under Diagnostics A harsh cornering rule can be set to trigger on different thresholds. Any number can be used for a custom rule, but we offer three general options in the stock rule: Passenger Car, Truck/Cube Van, and Heavy-Duty. The actual calculation uses floating point precision (approximately 7 decimal digits), where 1G = 9.8m/s2 and 1m/s2 = 0.101972G. Ex: 43 m/s2 is 4.384796 G. 43 m/s / 9.8 m/s = 4.38 G. Additional information is available at Geotab Blog

Many vehicles are coming with a GPS system pre-installed by the OEM. These instructions are specfic to Ford vehicles. Most commercial fleet vehicles manufactured after June of 2019 have a GPS receiver installed. All 2020 and newer vehicles have a GPS receiver installed. Geotab has integrated with Ford, GM, Volvo, Freightline, JohnDeere and others to provide a unified platform for viewing all vehicle activity.

There are notable differences between the GPS data Ford provides and what Geotab provides through their GO GPS device. Be sure to understand the differences before making your decision. You can always switch to the Geotab GO device if you find you need features not available in the OEM solution. Geotab devices can be easily moved between vehicles and between vehicle manufacturers and assets.

Service Feature Comparison (Geotab Pro vs Ford Pro. No Geotab Base mode at this time)

Geotab vs Ford OEM Service Features

Activating Ford OEM Service

1. Navigate to www.fleet.ford.com
2. Create an account and Fleet Identification Number (FIN) if you do not have one. It is only available for commercial fleet operators. Keep the FIN for future use. Speak with Ford if you have issues in the Ford portal.
3. Select Orders>Telematics Modem Activation
4. Select "Geotab" from the Telematics Provider drop list.
5. Check the box next to the vehicles you want to activate.
6. Click "Send to provider for activation"
7. Download the list to Excel and email to your Fleetistics account manager so Fleetistics can add the service to your acccount.
8. Fleetistics will prepare an order form for the monthly service and additional items as applicable. Monthly service billing is done by Fleetistics direct to the customer.
9. Complete the order on https://www.fleetistics.com/login/
10. Fleetistics sets up the account and provide access to Geotab and other partners and services.

Related Links

Ford portal login

MyFleetistics Portal

Detailed Ford OEM service instructions

Compare Geotab vs Ford service

For password reset issues we want to check the following before attempting to resolve the issue.

Is the user created in MyFleetistics and Geotab?

Has the user ever logged into the system before, if so, does the user login through MyFleetistics or Geotab? How to resolve password issues if the user is Created in MyFleetistics and Geotab.

Use this link to generate a password reset email. https://my4.myfleetistics.com/forgot-password

If the client tried this and did not receive the email, we get a copy of these emails. Forward the copy to the client, then have them set the new password.

Ensure both passwords match in MyFleetistics and Geotab. How to reset a password for users who are in MyFleetistics and Geotab. Please see below:

Step 1. Click on the Forgot Password option.

Step 2. Type in your email and then hit the green Reset password button.  

How to reset the password for users that are only in Geotab.

Step 1. Log in to the database that has the user having password issues. Use the support email to ensure you have permission to see all users in the account.

Step 2. After logging in, click on the Administration tab<User’s tab.

Step 3. Once in the User window, click on the specific user, then click the blue Reset password button

Step 4. From here you will enter the new password, then click the grey save button on the top right-hand side.    

For users in MyFleetistics, if you see the following date this means the user never set his password when the welcome email was sent. The welcome email will need to be sent again.    

How to send a welcome email for first password set up.  

Step 1. Click on the blue square with the unlocked lock icon in it.    

Step 2. In the Reset and Flush window, click the green Welcome & Flush button.  

If you are still having issues, please contact support at 1(800)481-1319.

Browser Related Issues

If clients are having a hard time logging in or accessing the system due to browser issues. Do the following:  

1. Ensure the client is using a supported browser. Internet Explorer is not support, Firefox is recommended. The system will also support Microsoft Edge, Google Chrome, and Safari.
2. If the client is using a supported browser, then have them clear the cache. This is done differently for every browser.

Clearing the browser cache in Google Chrome.

1. Hit the 3 vertical buttons on the top right-hand side of the browser.

2. From the drop-down menu, click on Settings

3. From settings scroll all the way down and click advanced.

4. From the advanced drop-down menu, navigate to Privacy and Security and you will see the clear browsing data.

Clearing the browsing history in Firefox:

1.       Click on the gear icon that is located at the top right-hand side of the browser.

2. From the gear icon, click on Privacy and Security on the left-hand side menu with the lock icon next to it

3. From the Privacy and Security window click on the clear data button.

If you are still having issues, please contact support at 1(800)481-1319.

The Geotab Marketplace offers three free mobile apps from the Play Store or iTunes. Search the app stores for the apps below.

You will need to enter your database name, user ID and password. Contact your account administrator for details if you are unsure. Fleetistics cannot provide this information without permission from your account administrator. Note: what you see will be limited by the groups you are assigned to in MyGeotab.

To view realtime data on an iPhone or Android users need to have the Geotab Drive App. The app is free and can be downloaded from the app store. To access the system they will need a username and password. Your System Administrator will need to request user credentials for the level of access required from your Account Manager or our Support Team.

For more information on Geotab mobile apps go to:

https://kb2.myfleetistics.com/admin/?action=editentry&id=32&lang=en

1 = unbuckled and vehicle is moving, 0 = buckled and moving, -1 = no seatbelt data during the times the vehicle was not moving.

The data may be easier to understand when viewed in a graph.

If an error is found on the Geotab map for posted road speed, a correction can be submitted. The correction will be immediately added to the OpenStreetMap map and then to Google about 60 days later.  

1. Click on Map
2. Type in the street name in the search field.
3. Click on the street and click "Updated posted Road speed" 
4. Type in the road speed and hit Apply change.  

Extendable Services is a secured data sharing technology that allows users to collaborate with trusted business partners by extending their telematics data to other Fleet Management Application users. For example, users can extend safety and performance-driven data to insurance providers to save on coverage or extend engine diagnostic data with maintenance providers to save on repairs. 

Extendable Services starts with a transaction between two Fleet Management Application users; a user from a primary database who makes a request to extend telematics services to a user from a target database, who accepts or rejects the request based on the needs of their business.  Extendable Services can only be shared with your Geotab GO devices at this time. Shared Rate Plans are available on Base, Regulatory, Pro, and ProPlus. 

Owner and target databases do not have to be on the same Rate Plan to use Extendable Services. Only data associated with the Rate Plan can be extended. Billing begins as soon as a request is accepted. 

Driver names, group names, and zone names are private and not displayed in the extended service.  Rate Plans can only be changed by terminating, then re-extending the service on the target database. Only Fleetistics can terminate an extended service on a target database.

Related Topics:
How do I initiate an Extended Service Request?
How do I cancel an Extended Service Request?
How do I accept an Extended Services request?
How do I reject an Extended Services request?
How do I remove a device from Extended Services?
How do I terminate Extended Services?

Telematics services can only be extended between active databases in the Fleet Management Application. To view extended telematics data, users must have an account in the Fleet Management Application. To view the extended services, users must have the View device share clearance. To accept/reject requests for extended services, users must have the Administer device share clearance.  By default, Administrators have the Administer device share and View device share clearances.

Related Topics:
How do I initiate an Extended Service Request?
How do I cancel an Extended Service Request?
How do I accept an Extended Services request?
How do I reject an Extended Services request?
How do I remove a device from Extended Services?
How do I terminate Extended Services?

These steps are performed by the requestor from the primary database. To extend telematics services to a target database, do the following. Remember, you must have the SecurityEditDeviceShare to extend your telematics services to another database. If you do not have this security clearance, and would like to extend services, please contact your Administrator. 

1. From the Fleet Management Application navigation menu, click Vehicles. 

2. Select a vehicle from the list, or search by name or device serial number. 

3. Alternatively, use the Select individual option from the dropdown menu to select multiple vehicles, then click the Edit selected devices button. 

4. On the Vehicle Edit page, click the Extended Services tab. If you selected multiple vehicles, do the same from the Vehicle Edit Multiple Devices page.

5. Under the Extended Services tab, click the Add another service button.  

6. Enter the name of the target database under Database. The Rate Plan associated with the device is selected by default. If necessary, select another Plan from the dropdown menu.  

7. If desired, repeat step 4 to add more databases.

8. When you are finished adding services, click the Save button on the top menu, or the checkbox under Action to send your request to the target database.

9. After saving, a notification displays at the top of the page confirming the request was successfully sent to the target database. The notification remains on the page until it is dismissed by clicking the X symbol.

10. The Service Status under the Extended services tab changes from New to Pending. The service remains on the page until it is dismissed by clicking the X symbol. 

11. The recipient of the target database can choose to accept or reject the request. If the request is accepted, the Service Status changes from Pending to Active, and billing associated with the selected Rate Plan, begins. If the service is rejected, the Service Status changes from Pending to Rejected, and no billing begins. 

Related Topics:
How do I cancel an Extended Service Request?
How do I accept an Extended Services request?
How do I reject an Extended Services request?
How do I remove a device from Extended Services?
How do I terminate Extended Services?

Extended Services requests can only be cancelled while in the Pending status. If the request was already accepted by the recipient from target database, refer to Removing an Extendable Service.

1. To cancel a Pending request, return to the Vehicle Edit page and click the X symbol associated with the request under Actions. 

2. You are asked to confirm cancellation of the request. Review the message and click the Cancel sharing button to proceed, or Continue to continue sharing. 

3. If you clicked Cancel sharing, the Service Status changes from Pending to Cancelled.

✱ NOTE: The target database does not receive a notification that the primary database cancelled the request.

Related Topics:
How do I initiate an Extended Service Request?
How do I accept an Extended Services request?
How do I reject an Extended Services request?
How do I remove a device from Extended Services?
How do I terminate Extended Services?

These steps are performed by the recipient from the target database. To accept or reject an extended services request from a primary database, do the following. Only incoming services in the Pending status can be accepted or rejected. To accept a request:

1. From the Fleet Management Application navigation menu, click Vehicles. 

2. A notification displays at the top of the page from the primary database requesting to extend telematics services to your target database. The notification remains on the page until it is dismissed by clicking the X symbol.

✱ NOTE: The request is only visible to recipients with the View device share clearance, and can only be accepted or rejected with the Administer device share clearance. If multiple requests are made, multiple notifications display. 

3. Click the View Data button on the notification to view details of the primary database, then enter a name for the service in the Description/Name: field. When finished, click Accept. ✱ NOTE: If multiple vehicles are shared, they are listed in separate Description/Name: fields.

4. Another notification displays at the top of the page confirming the request was accepted. 

5. Select the new vehicle from the list, and under the Extended services tab on the Vehicle Edit page, the Service Status changes from Pending to Active. ✱ NOTE: At any time, click the Show Help button to display additional information about the feature.

✱ NOTE: At any time, click the Show Help button to display additional information about the feature.

Related Topics:
How do I initiate an Extended Service Request?
How do I cancel an Extended Service Request?
How do I reject an Extended Services request?
How do I remove a device from Extended Services?
How do I terminate Extended Services?

These steps are performed by the recipient from the target database. To accept or reject an extended services request from a primary database, do the following. Only incoming services in the Pending status can be accepted or rejected. To accept a request:

1. From the Fleet Management Application navigation menu, click Vehicles. 

2. A notification displays at the top of the page from the primary database requesting to extend telematics services to your target database. The notification remains on the page until it is dismissed by clicking the X symbol.

✱ NOTE: The request is only visible to recipients with the View device share clearance, and can only be accepted or rejected with the Administer device share clearance. If multiple requests are made, multiple notifications display. 

3. Click the View Data button to view details of the primary database, then enter a name for the service in the Description/Name: field. When finished, click Reject.

4. The Service Status under the Extended services tab in the owner changes from Pending to Rejected.

✱ NOTE: The primary database does not receive a notification that the target database rejected the request.

5. In the event the target database receives a request to extend services that were already accepted, the request is automatically rejected, and a notification displays at the top of the target database.

Related Topics:
How do I initiate an Extended Service Request?
How do I cancel an Extended Service Request?
How do I accept an Extended Services request?
How do I remove a device from Extended Services?
How do I terminate Extended Services?

! IMPORTANT: You can remove a device from the target database after accepting a request from an primary database to extend services. However, removing a device does not remove billing for the subscription. To deactivate billing, service must be terminated. To terminate an extended service, please contact Fleetistics. 

1. To remove a device from a target database, return to the Vehicle Edit page, and under the Device tab, click the Remove button. 

2 Review the messages in the Remove device dialog, and when finished, click the Delete button. 

Related Topics:
How do I initiate an Extended Service Request?
How do I cancel an Extended Service Request?
How do I accept an Extended Services request?
How do I reject an Extended Services request?
How do I terminate Extended Services?

 Only Fleetistics can terminate Extendable Services. Email Support@Fleetistics.com or call us at 877-467-0326 to make a termination request. If you simply remove the devices from Extendable Services the billing for the plan will continue.

Related Topics:
How do I initiate an Extended Service Request?
How do I cancel an Extended Service Request?
How do I accept an Extended Services request?
How do I reject an Extended Services request?
How do I remove a device from Extended Services?

Yes and yes. The standard GO device receives signals from the GPS satellites to determine the lat/long, speed and altitude of a receiver (antenna in the GO device, phone, Garmin, OnStar, etc)on the earth with about 3 meters, generally less. The GPS data is then transmitted from the vehicle to a cellular communication network or an optional satellite communication network. Most customers use the cellular network modem because it is far less expensive than communicating on a satellite communication network. There are various cellular networks to choose from based on the data coverage in the area of asset operation.

When an asset needs to be tracked in very remote areas some or all of the time, and it is a high value asset, customers add a satellite modem to the standard GO system. This provides limited information in very remote areas such as oil fields. The detailed information is uploaded when the asset returns within range of the correct cellular network. This method is used to control costs because transmitting all data provided by the GO system would be cost prohibitive on a satellite communication network.

The vehicle is moving from the speed zone before it communicates with the server where the posted road speed is checked. The device must connect a second time for the alert to be triggered on the device in the vehicle. At 70 mph the vehicle may be several miles further before the driver is alerted. Adding the ProPlus service provides much faster results. This increases the communication rate with the server so the violation is recognized and sent back to the vehicle much more quickly than the standard rate used for Pro service. Communication in ProPlus takes place about every 20 seconds compared to every few minutes in Pro mode.

To view realtime data on an iPhone or Android users need to have the Geotab Drive App. The app is free and can be downloaded from the app store. To access the system they will need a username and password. Your System Administrator will need to request user credentials for the level of access required from your Account Manager or our Support Team.

Common Fault Descriptions

GPS Quality Poor: Check the location of the device installation to see whether there are any heavy metal components or third party electronics in the immediate vicinity. Reposition the device to a better location with clearer view of the sky, using an extension harness. Depending on the device, the GPS antenna may be on the top or bottom of the unit. Don't place the antenna against a metal object such as the dash frame.  

GPS Module Not Responding: If a hard power reset of the device does not clear this fault and restore reliable GPS latching information, then there is likely a hardware level failure and the device will need to be replaced. Install the device in a vehicle that has been tracking reliably. If the device does not report, you have confirmed there is a device level issue.  

Vehicle Battery Has Low Voltage: Review the voltage output from the battery and consider servicing the battery if this fault is prevalent for any given vehicle. Could result in eventual power loss to the device.  

All Power Removed - Device Restarted: Can be a result of low battery voltage causing the device to undergoe a brown out or potentially the install is insecure install and the device does not have a consistent connection to the vehicle's battery source.  

Telematics Device Has Been Unplugged: The device was either manually unplugged (tampered with) or the installation has come undone. Check the install integrity to make sure nothing has been changed. Use serial numbered zip ties to avoid this issue.  

Accelerometer Disabled Due To Excessive Data: Check to make sure that the device is securely installed and fastened to a solid vehicle component which will not vibrate or otherwise result in device movement. Ask your account manager about mounting brackets.  

Accident Limit For Acceleration Exceeded: The device has recorded too many consecutive accident level events. The action from the previous point above should be taken. The device may not be mounted firmly to the vehicle chassy, the drive may be hitting it on entering the vehicle (consider a Y-harness to put the device in the dash) or the rule for driving conditions may be too sensative.  

Excessive Engine Records Are Being Created: The device is logging too much engine data and the engine data logging feature is now disabled. Perform a hard power reset on the device to renable engine data logging but also follow up internally, or with your authorized Geotab reseller, in order to find out which engine diagnostics were being logged excessively. Engine data will continue to be automatically deactivated until the issue is resolved.  

Flash Memory Failure: The internal device flash memory has succumb to a hardware failure. The device needs to be replaced. Contact Fleetistics support at 877.467.0326  

* For any other faults which may appear within your fleet, please follow up with your management team and/or your authorized Geotab reseller in order to determine if they can have a negative impact.

How you change a device name depends on the GPS system you are using. Some functions are limited to users with the admin or supervisor access rights in MyGeotab so be sure to check your rights with your account administrator.

To change Geotab device names launch MyGeotab and navigate to Vehicles. Select your vehicle and change the Description field. Don't forget to checkout the Driver feedback menu to coach your drivers to be safer drivers.

Changes in the MyFleetistics device editor section will not change the device names in MyGeotab. This integration has not been completed so copy and paste the name if you want the two to match.

When connecting an auxiliary line to a circuit using the Geotab auxiliary cable, you can read the default value or invert the value. Ensure auxillary X, is used the exact same way throughout your fleet. If you are tracking a salt spreader being active with a default state value, it must be the same for all vehicles in your account. Geotab does not have a way to decipher differences between vehicles or auxillary state values.

To understand this better; on a light switch you have the on and off positions. Similarily, an auxiliary circuit provides a value of  0 or 1 based on the state of the circuit.. Lets say that 0 registers when "off" and 1 registers when "on". When the auxiliary is inverted, the values are inverted, 0 will represent "on" and 1 will represent "off". So the values are inverted in order to detect or monitor the opposite state. To get a more detailed explanation on how the auxiliaries algorithms work, please click on the link below.

Potential Scenarios:

1. You want to monitor the activation of emergency lights on an ambulance. The normal state of the circuit is powered off, so you want to see data when the lights are on.

2. A generator runs all the time to pump water from a basement in a skyscraper. The normal state of the pump drive is on, so you want to see data if the pump shut off. By inverting the aux input you can change how the data is reported.

Configuring AUX Inputs IOX-AUX self learning process & manual configuration

Yes. Reminders can be based on mileage, engine hours, or a future date. To create a reminder:

1. Click Engine & Maintenance in the left menu.
2. Click the Reminders option and a fly-out menu is displayed.
3. Select Reminder Rules from the fly-out menu.
4. Click the Add button located near the top of the window.
5. Enter a name for the reminder in the Description field.
6. Select a type for the reminder from the menu provided. Types are used to organize reminders.
7. Click the No button in the area labeled Creae reminder based on time.
8. Click the Mileage button located in the area labeled Ceate reminder based on usage.
9. Enter the number of miles between procedures for this reminder in the field labeled Mi.
10. Click the Save button located near the top of the window.

Managing Vehicle Maintenance with Geotab Creating and managing vehicle maintenance reminder reports

Terminology:

Open: Reads as neither a negative nor a positive, and has an infinite resistance.
Negative: Reads as ground, and has a zero resistance to ground.
Positive: Reads as 12 volts.

Specifications Sheet

A negative triggered circuit typically:

Rests at Open and switches to Negative

or

Rests at Positive and switches to Negative

A positive triggered circuit typically:

Rests at Open and switches to Positive

or

Rests at Negative and switches to Positive

Factory Settings

All eight auxiliary inputs come factory set as Negative triggers.

Here is how it works: When the auxiliary is Open or Positive then it will appear as OFF (or 0) within MyGeotab while when the auxiliary is Negative (grounded, 0V ) then it will appear as ON (or 1) within MyGeotab.

Inverting Auxiliary Logic within MyGeotab

Any of the eight auxiliaries can be inverted in MyGeotab by the end user by going to the vehicle properties, clicking on More Details and then selecting the Auxilairy Tab. Once on that tab you just have to click on the auxiliaries that you wish to Invert. What inverting will do is whenever it receives Aux OFF (0) from the device it will save it as Aux ON (1) and vice-versa.

Geotab Configurable

 Any of the the first 4 auxilairy inputs can be changed to be Positive inputs by Geotab support using a custom code. When this code is applied the auxiliary will appear as ON (1) when it is Positive and OFF(0) when it is Open or Negative.

https://geotab.github.io/sdk/

A common concern with plug-and-play type device is tampering. The plug-and-play device is super convenient to install but this means it can be easily removed just as easily. Serial numbered zip ties and extension cables provide two additional layers of protection but nothing if tamperproof.  For over 18 years Fleetistics has been answering questions about tampering and for 18+ years Fleetistics has said 'If a driver wants to tamper with a device, they will. The question is what are you willing to do about it to set an example?' Prior to plug-and-play devices all devices were hard-wired and they were tampered with at the same rate. Having strong HR policies in place are the best defense and deterrent.

Although there are several layers of deterrents for the plug-and-play devices ultimately there is a need to know if a device does not report correct and registers a power event. The Watchdog Report provides this data. Exceptions can also be created to notify users via email.

Devices are programmed to 'wake' from suspend mode when the ignition is off in order to register with the GO server. This handshake is pre-scheduled and if the device does not handshake an exception is recorded. The handshake takes place at various intervals depending on how long the ignition has been off. This process helps reduce the strain on vehicle batteries over extended periods. The battery voltage is reported with each heartbeat and can be monitored to prevent dead batteries. Vehicles not being used for over 30 days should have the device removed to prevent continuing batter drain. Please note this does not eliminate the service fee and add to your return on investment so use the devices as much as possible.

Heartbeat Scheduled After Ignition Off

Heartbeats are every 30 minutes after ignition off for the first 48 hours. Then every 23 hours until the next ignition on.

As Geotab continues to innovate, many modern features of the web are integrated into our products. In order use all the advanced functionality on MyGeotab, a modern browser is required.

The latest version Microsoft Edge ·        
The latest version of Google Chrome ·        
The latest version of Mozilla Firefox ·        
Apple Safari
Note: Some functionality requires the use of Windows(R) ClickOnce. If you are using a web browser other than Internet Explorer, a browser extension may be necessary. MyGeotab will show you how to install the extension suited for your browser after your first log in.

System requirements

• Windows Vista, 7, 8 or later
• Mac OS X 10.5 or later
• .NET 2.0 (already installed with Vista)
• 40 GB hard disk that has 15GB space free
• 1 GB of RAM
• Additional hard disk space might be required for data storage
• iOS (iPhone, iPad and iPod Touch) 5.0 or later
• Android 3.0 or later (Android 2.1 or later when using Firefox for Android)
• Touch screen displays are supported

Note: Due to the volume of data presented on Geotab as a result of maps and reports, we also recommend you have access to a high speed internet connection.

Driver feedback

Making it easy for your drivers to immediately improve their on-road driving behavior, the in-vehicle audible alerts notify drivers of unsafe or potentially risky driving events. Once the driver has corrected their actions, for example by reducing their speed or fastening their seat belt, the interactive in-vehicle alert will cease to notify them. This helps your organization develop a fleet-wide safety program that works without intervention.   Your fleet managers can review this information with real time reporting and be notified when events occur through by email and text messages. Reports)

When viewing the current location of your vehicle(s), you can optionally display informational layers on top of the map. Select View, then from the list select Show/Hide Zones to display any custom zones you have created which are currently in view. Repeat these steps to hide zones.

Note: Zones are used to denote areas of interest such as customer areas, workplaces or people’s homes and can be used in exception reporting. Zones.

To change the shape of a zone, find the zone on the map or search for it in the zones list. Selecting a zone on the map and the menu below will be shown. Select Change zone shape to modify the boundary by moving or removing individual points. To add a new point to the boundary, select along the zone boundary. Remove an existing point by dragging it off the map. When finished, select Save changes, or Cancel return to the previous screen.

Note: Changing zone properties will affect future data. You can reprocess data to affect data from the past.

Zones can be removed from the database by selecting a zone and then clicking Remove. Once the zone is removed, your reports which previously displayed the zone name will instead show the address if available and you will no longer be able to see the zone on the map. Making changes to or removing multiple zones at a time is made easy by using the checkbox at the top right hand corner to select multiple zones.

You can use a spreadsheet application to prepare a list of zones which can be imported to your account. This saves time when you have a large number of zones to be created. When addresses for your zones are available use the following format to create a spreadsheet in Excel:

Overview

Effectively dispatching your drivers is easy when you use Geotab to do your route optimization. You can reduce fuel consumption, mileage, CO2 emissions and increase your organization’s operational efficiency. As a fleet manager, you know how important it is to make accurate and fast deliveries while maintaining high customer satisfaction levels.

Creating a route

Routes created by connecting a sequence of zones together to create a path. The route can optionally start and end at the same location and can be defined in any order you wish. You can optionally allow Geotab to optimize the order in which a driver should visit each zone so that fuel consumption is kept to a minimum. Navigate to Zones & Messages from the left hand side options menu. Select Routes from the sub-menu, your existing routes will be displayed.

Click Add Route from the top menu to create a new route.

Assign a departure point for the route by selecting a zone on the map. Continue to select additional zones which the driver must visit along their route. After all zones have been added, select Save route from the top menu. Note: The order in which zones are added to the route is not important as the route can be optimized after all zones are added to ensure that the least distance is traveled.

Take a moment to customize your route by adding a description and optional comment. For example, describe the customer’s which will be visited or the main roads that should be driven. Select the Optimize button to ensure that the shortest route will be chosen. This will greatly help you save time and fuel for long routes.

When finished, select Save from the top menu.

Route plans

When you have a route created, a route plan can then be created allowing you to examine how a driven route compares defined route. The route plan consists of your route, timeframe for completion and a specific driver. When used in combination with one another, the route plan comparison is a powerful way to highlight where and when a driver unexpectedly spent time or has made unplanned stops. Navigate to an existing route that has been created or follow the previous steps to create a new route. Select Create plan from the top menu to create a route plan.

Comparing actual trips with planned routes

This process requires the use of the Software Development Kit (SDK) to import the routes in to your account. The routes must be formatted as a CSV file with the details of the route name, stop locations, the estimated time to drive to each location and the estimated time to be spent at each stop. Note: Geotab offers SDK samples to assist you with this process. Your stop locations must be entered as unique zones in your Geotab account. After the route has been completed, a report can be generated using the Planned vs. Actual Route Report to highlight stops made out of order, missed stops, travel time and extra time spent in zones along the route.

Plan vs. actual route report

In addition to the visual, map-based report, you can run a text based report of your route plans which can be downloaded to your computer.

Understanding where and when issues arise with fleet is made simple by establishing exception rules. When a vehicle event occurs which breaks a rule, an exception is recorded which can then optionally notify one or more people, alert the responsible driver in their vehicle, or simply log the event in your account. Fleet managers can at any time run reports and review the history of exceptions to understand the trending behaviors of their fleet.

Geotab offers a robust suite of built in exceptions separated into easy to understand categories. In addition to these, you can create an unlimited number of custom rules which combine different various conditions to suit your needs.

The types of built in exceptions available are available in three categories:

1. Safety:
   Changes to driver behavior which increases accident risk such as harsh braking, seat belt use, speed violations, accident detection and more.
2. Productivity:
   Driver measurements related to time spent performing specific actions such as excessive idling, late arrivals, early departures and more.
3. Fleet:
   Responsive vehicle monitoring Engine issues, battery drain, tracking device tamper detection and more.

Auxiliary rules allow you to manage connected external input devices and sensors to the Geotab GO Device through a familiar rule based approach. These rules integrate seamlessly with the live map and are displayed in real time.

Note: Auxiliary Rules were formerly known as Auxiliary Groups.

As an example, assume your Geotab GO Device has auxiliary 1 connected to your driver side door and is activated whenever it is opened. In MyGeotab, you would now configure an auxiliary rule named “Door Open” in the place of “Aux1” for the corresponding vehicle.

Exception rules are managed by selecting Rules & Groups from the left hand side menu, then by selecting Rules. Use the buttons shown below to open detailed explanations of each exceptions and select the pen button to begin making changes.

You can manage who is notified when exceptions occur by selecting the envelope button from the top menu.

Safety exceptions

Geotab enables fleet wide safety and driver improvement through instant notifications of in-vehicle behaviors. All exceptions can be configured to interactively alert the responsible driver at the time of exception by using an audible alarm built in to your Geotab GO Device. This feedback allows early detection and response to driver activity which greatly increases the road safety of your drivers and others on the road with them.

Productivity exceptions

Geotab is consistently raising the bar when it comes to driver productivity tracking. You can be notifications of exceptions such as late arrival, early departure, idling, unauthorized home or customer stops, excessive office time, long lunch and even long stops during work hours. Listed below are all the built in productivity related exceptions which Geotab offers.

Fleet exceptions

Thousands of vehicles equipped with Geotab technology have realized significant cost savings benefits. Geotab offers the most extensive metrics available to help you reduce fuel consumption. We help you be proactive in keeping your fuel costs down by managing driver behaviors such as excessive speeding, idling and detecting engine issues as before they become costly problems.

Grouping Auxiliaries

Generally we want to keep Auxiliary Groups in a separate Group tree from that of location, vehicle category, etc. For this reason we will group all auxiliaries in their own branch under Entire Organization. If you already have a parent group for Auxiliaries skip to step 4 Navigate to Rules & Groups from the left hand side menu, then select Groups from the sub-menu Click the “+” button connected to the Entire Organization group Name the group “Auxiliaries” and click save Next we will create our auxiliary group, click the Auxiliary branch Click the “+” button under Auxiliaries group Name the group as required, for this example we will use “Salt Truck”, click save

Auxiliary Rules

Navigate to Rules & Groups from the left hand side menu, then select Rules from the sub-menu. Select Add from the top menu to begin creating a new auxiliary rule Give your auxiliary rule a meaningful name and description such as “Salter” Select the Groups “Salt Truck” group Click the Conditions tab to specify how the rule will behave Select the connected auxiliary port from the More menu Select True for the value from the opened Condition Value Selection then click Add to associate the new rule with this auxiliary input Add any additional conditions you would require such as the ignition being on, minimum duration or vehicle speed Create the new rule by selecting Save Note: Your new rule applies to future data. If you would like to apply the auxiliary rule to historic information, you must first reprocess your historical data.

Apply Auxiliary Rule to Vehicles

Navigate to Vehicles from the left hand side menu. Select one or more vehicles from the list to add the aux rule to Select the “Groups” tab Select the “Salt Truck” group from the “Groups” control Save the vehicle(s)

User Access

Because Aux Rules are grouped, you may need to give users access to report on Aux rules. Note that given a user access to an Aux group in their “Data Scope” may result in them getting access to vehicles you do not want them to see. For this reason you can give a user access to the aux group in their reporting scope. This will give them access to see the exception on the map and report on these exceptions. If the users in question have Entire Organization data scope, skip this step. Navigate to Users from the left hand side menu Select the user(s) you want to see aux rule exceptions Under “Additionally allow reporting by these groups:” select the aux group you would like the user to report against. For example the “Salt Truck” group we set up in the above steps Save the user(s)

Auxiliary rule reports

After an auxiliary rule has been broken by a vehicle or driver, it will be available in your exception reports. Select Rules & Groups from the left hand side menu, then select Exceptions from the sub-menu. Select which Device, Driver or Group to report on and select the appropriate time and date range from the Filter. Select the Options button, the Select Exception Rules window is now displayed. From the Select All Rules drop down menu, select Select Particular Rules. Select the auxiliary rules to report on and close the Select Exception Rules window. Select Apply to run your report using the filter you created Note: To view a summarized version which includes duration totals and the total number of incidents select the Summarized button from the top menu.

After an auxiliary rule has been broken by a vehicle or driver, it will be available in your exception reports.

1. Select Rules & Groups from the left hand side menu, then select Exceptions from the sub-menu.
2. Select which Device, Driver or Group to report on and select the appropriate time and date range from the Filter.
3. Select the Options button, the Select Exception Rules window is now displayed.
4. From the Select All Rules drop down menu, select Select Particular Rules.
5. Select the auxiliary rules to report on and close the Select Exception Rules window.
6. Select Apply to run your report using the filter you created

Note: To view a summarized version which includes duration totals and the total number of incidents select the Summarized button from the top menu.

When auxiliary rules are broken you can have automatic notifications sent out to inform fleet managers. A notification can be displayed in the following ways: ·        

Email to one or more people

An alert displayed on Geotab

The driver can be alerted by an audible in vehicle alarm. Third-party systems can use additional means such as SMS

Email templates

The information included in the email notifications is fully customizable using simple to use templates.

Examples of customizing the notifications sent out are: ·        

• Compact version for mobile devices to conserve data usage on mobile data plans
• Include a contact phone number for emergency situations
• Offer a web link to a map containing directions to a service station when engine failure is detected

Note: there may be a minor delay between when data is sent from the vehicle to when the server sends a notification depending on the type of notification and exception being handled.

Advanced notifications

You can further customize the conditions which need to be met to send a notification by using the advanced editor. You can combine multiple conditions together to specify exact business cases such as:

• Dangerous driving detected from engine measurements
• Seat belt use when in motion
• Arrival and departure of zones outside normal working hours

Compare your driver’s speed with the posted road speed for local city driving, or within specific zones such as schools or other low speed residential areas. Easily watch changes in style depending on the environmental conditions.

Compare your driver’s speed with the posted road speed for local city driving, or within specific zones such as schools or other low speed residential areas. Easily watch changes in style depending on the environmental conditions.

The speed profile is accessed from the Trips History for a vehicle. Open the Map by clicking the option in the left menu. Click Trips History button above the map. Select the desired vehicle and trip day. Click the ... button located on the extreme right of the window and select Speed Profile from the menu.

Customers who use the hosted version of Geotab have access to real world posted road speeds. This allows street level accurate notifications to be sent when driver’s exceed local speed limits. Posted speed limit data comes from two sources: NAVTEQ Maps Open Street Maps (OSM) Note: Posted road speed is only available to customers who use the hosted version of Geotab and is supported in the U.S. and Canada. Posted road speeds can change frequently and may contain inaccuracies. You can update the posted road speed of any road by clicking on a road from the live map. A menu will appear, select Update posted road speed to change the value. Geotab shares the changes you make to posted road speeds with all customers. That way, everyone benefits from each others changes. On a monthly basis, Geotab will send the latest posted road speeds to OpenStreetMaps, where they will make them available to everyone else on the Internet. Note: Due to the possible inaccuracies caused by road construction or other hazards. We recommend that posted speed limits be used as part of a larger safety strategy. For the latest coverage maps from the above data sources see http://goo.gl/W0xxj7.

Vehicle acceleration

Geotab offers the ability to set exception rules for excessive driving behaviors such as harsh acceleration, harsh braking and harsh cornering. Depending on the type of vehicle the rule is applied to, use the table below as a guideline for the average g-force exertions typical to that vehicle. In most cases, the default values found in Geotab are suitable, but are highly customizable. 

Geotab has incorporated the latest in RFID technologies - Near Field Communications (NFC) - to deliver driver identification for personnel that switch between vehicles. Driver ID allows fleet managers to have a full view into their driver activities regardless of the vehicle they are currently driving. This allows running reports, rules and exceptions by driver or vehicle. Driver ID can be combined vehicle immobilization wherein a valid Driver ID keyfob must be touched to the reader before the vehicle will start.

Understanding drivers

When using Geotab, a Driver is special type of user account that is configured by your administrator. A driver can be issued a physical driver key (NFC or GO key) which is then used to identify that specific driver when in a vehicle.

Driver keys

When a driver enters a vehicle, they use their Driver ID keyfob to associate their user account with that vehicle. When using NFC, this process is performed by tapping the Driver ID keyfob on your equipped vehicle’s driver identification reader.

• NFC: Driver identification is done by tapping their key (or tag) to the Geotab NFC IOX reader. Each key has a visible unique serial number which is associated with a user account.
• GO key: Legacy driver identification which is inserted to the reader. GO keys are designed for Geotab GO2 and GO4 devices and do not have a visible serial number.

Using driver identification

When a driver enters a vehicle equipped with a driver identification system they should first use their driver key to identify themselves before starting the engine. If they do not first identify themselves, an audible sound will remind them that identification is required.

The identified driver will then be associated with that vehicle for the duration of a single trip, or until another driver identifies themselves.

If a driver attempts to use their driver key before it is assigned to their user account an exception will be generated letting you know that an unassigned key has been used to identify a driver in a vehicle.

Note: Your account must first have the driver identification feature enabled.

In order to preserve the quality of service when using Geotab there are a number of limitations applied to the number of emails which can be sent at a time, and the size of each individual message.

• Attachments cannot not exceed 10 MB
• The total data usage of emails per hour cannot exceed 500 MB
• The total number of emails sent in an hour per rule cannot exceed 500

Note: If an email limit is exceeded, any further emails will be disabled for 60 minutes.

Your Geotab GO Device is designed to collect and respond to status information in your vehicle. The port which it is installed in is traditionally used for on-board diagnostics from the vehicle’s manufacturer.

Your Geotab GO Device responds to changes in your vehicle to the following areas:

• Engine RPM
• Battery voltage
• Engine warning light on (MIL)
• Seatbelt usage
• Odometer
• Engine hours (PTO)
• Emission faults
• Vehicle identification number (VIN)

Please be aware that due to differences in vehicle manufacturers, the actual engine information available in your vehicles may vary. Geotab is consistently expanding the number of supported vehicles and features and regularly distributes firmware updates as necessary.

Note: If when installing your Geotab GO Device you experience issues such as power loss, the vehicle stalls or engine lights are displayed you may have an incompatible vehicle. Please remove the Geotab GO Device and contact your authorized Geotab reseller.

Understanding your vehicle

Authorized Geotab resellers have access to a proprietary tool which is used to automatically discover the available engine information for your vehicle. This is done by providing Geotab your vehicle identification number which is usually located on your dashboard.

In order to determine whether a vehicle is driving, stationary or turned off, the system uses patented technology to examine vehicle battery voltage, movement by use of accelerometer, GPS location and available engine status information. This allows the system to be used in vehicles that do not include an engine bus, in new electric or hybrid vehicles, commercial vans and large trucks.  

The basis of keeping track of driver safety are the safety exception rules. System components to configure include:

• Setup exceptions for dangerous driving

• speeding against posted speed limits
• harsh brake
• dangerous lane changes/ aggressive driving
• after hours use
• driving with no seatbelt

• Limiting backing up (and ensuring backing first)
• Seatbelts are used much less than expected by monitoring compliance can go from 80% to 99.8% (large fleet case study)
• Notify the driver by buzzing in the vehicle
• Driver safety scorecard
• Who to email / alert in case of accident -setup a procedure when accident happens.

• Auto retrieve
• Reconstruction from data

• Detect distracted driving – big issue

There are several different methods that the GO device uses to calculate the fuel used from a vehicle and the method that is used depends on the vehicle type and the type of data that the device is able to maintain from it. The methods are listed below:

1. Instantaneous Fuel Used - This method is the most accurate method and is obtained directly from the engine's computer. It is commonly found on all GM vehicles with CAN and on some newer CAN based OBD2 vehicles (from 2012).

 2. Total/Idle Fuel Used - This method is similar to the first method, except it is slightly less accurate than it. This method is almost always available on vehicles with the J1708 and J1939 protocols. 

3.  Mass Airflow with known fuel type - This method calculates the fuel used by obtaining the mass airflow data from the engine and inputting it into an algorithm. This method of calculating the fuel used is less accurate but it available on almost all vehicles.

4.  Mass Airflow with unknown fuel type - If the GO device is unable to obtain the fuel type data from the vehicle, it  will automatically default to GAS. Therefore, this method can be the least accurate because using a different fuel type alters the mass airflow to fuel used conversion slightly in the algorithm.

Frequency of logs and fuel economy

The fuel calculation methods above are used to calculate trip fuel used and idle fuel used. Trip fuel used is saved after every ignition off event if fuel data is obtained from the vehicle. Idle fuel used is logged and accumulates when the road speed of the vehicle is zero. Once the total fuel used is known, the fuel economy is calculated by dividing the total fuel used by the distance traveled from GPS data.

What is Accident Data?

Once a collision occurs the accelerometer within the GO device will detect an accident event and record second by second data of the accident and re-transmit this data for interpretation. This includes Latitude, Longitude, speed, accelerometer as well as various other information that are essential to reconstructing the accident event.

How do I interpret Accident Data?

There are various tools available within MyGeotab that can be utilized to interpret the raw data from the device. For the purposes of this document the below information are accident reconstructions of two real accidents that occurred.

Reconstruction of Accident Data

Case 1: GO7 

Map View

The first step to reconstructing accident data is to view the accident on trips history. This can be done by clicking on Map>Trips History. Choosing the date and the time of when the accident occurred will show that trip on the map. One of the first things to note is that the initial few seconds after the ignition event is usually inaccurate since the device will still be attempting to find the GPS latch. In the image below this vehicle was hit from the side as it was trying to pull into the main road. The map alone should not be the only tool used in the reconstruction as it does not show enough information.

This shows the individual logs as they are reported by the device before they are interpreted on the map. The important thing here is to look for the accident level detection and to match that time on the map to get a better understanding of when the accident occurred. This can be done by clicking Drivers and Activity> View Accident and Log Data. Choosing the appropriate vehicle and the data range will show each log for that time period.

Accelerometer Graph 

This is a great tool that can be used to determine the direction the vehicle was hit from and the force exerted in each direction due to the collision. This can be done by going to Engine & Maintenance > Engine Data. From here choosing the correct vehicle and time will show all the engine data that came in for that device. Make sure to change the view to Status View. From here highlight one of the accelerometer side to side or forward and back (depending on the collision direction) and click More > View on Graph.

RPM Graph

The RPM graph is important in determining if the driver had his foot on the accelerator of the vehicle. This can be used to determine if the driver was on the move or slowing down. Keep in mind that depending on the type of vehicle the engine will rev at a certain amount even at idle. A good way to interpret this is to look at the engine RPM value at ignition start. In the image below this Mazda 3 Sedan had an RPM of about 1500 at Ignition start which went down to about 1000. This vehicle will therefore idle at 1000-1500 RPM.Since the highest RPM point is just below 2000 which is very gentle acceleration.

Geotab accelerometers measure distance over time (gravitational force) in meters per second squared in three dimensions. We use sharp changes in accelerometer data to infer vehicle events such as harsh cornering. This data can be found by going to Engine & Maintenance > Engine and Device... > Options > Acceleration side to side under Diagnostics A harsh cornering rule can be set to trigger on different thresholds. Any number can be used for a custom rule, but we offer three general options in the stock rule: Passenger Car, Truck/Cube Van, and Heavy-Duty. The actual calculation uses floating point precision (approximately 7 decimal digits), where 1G = 9.8m/s2 and 1m/s2 = 0.101972G. Ex: 43 m/s2 is 4.384796 G. 43 m/s / 9.8 m/s = 4.38 G

Geotab Blog

Yes. In Geotab, navigate to the Vehicles>(select vehicle)>More Details>Driver Feedback. Adjust the settings as needed.

Geotab accelerometers measure distance over time (gravitational force) in meters per second squared in three dimensions. We use sharp changes in accelerometer data to infer vehicle events such as harsh cornering. This data can be found by going to Engine & Maintenance > Engine and Device... > Options > Acceleration side to side under Diagnostics A harsh cornering rule can be set to trigger on different thresholds. Any number can be used for a custom rule, but we offer three general options in the stock rule: Passenger Car, Truck/Cube Van, and Heavy-Duty. The actual calculation uses floating point precision (approximately 7 decimal digits), where 1G = 9.8m/s2 and 1m/s2 = 0.101972G. Ex: 43 m/s2 is 4.384796 G. 43 m/s / 9.8 m/s = 4.38 G

Geotab Blog

If you are seeing a blank or white screen when trying to open a GPS platform from the MyFleetistics menu, the X-Frame policy is causing an issue. To correct this add the appropriate browser extension. If you are unable to install the certified browser add-in, contact your IT department. An exception may need to be added for myfleetistics.com and mygeotab.com.

This is a fix Firefox and Chrome.

Firefox https://addons.mozilla.org/en-US/firefox/addon/ignore-x-frame-options-header/

Chrome https://chrome.google.com/webstore/detail/ignore-x-frame-headers/gleekbfjekiniecknbkamfmkohkpodhe?hl=en-US

Edge No issue detected

Safari Not tested - Not supported

	Firefox X-Frame Add-in Resolves page will not load from MyFleetistics.
	Chrome X-Frame Add-In Resolves page will not load from MyFleetistics.

Device Status: [Device ID from GPS System]

How you change a device name depends on the GPS system you are using. Some functions are limited to users with the admin or supervisor access rights in MyGeotab so be sure to check your rights with your account administrator.

To change Geotab device names launch MyGeotab and navigate to Vehicles. Select your vehicle and change the Description field. Don't forget to checkout the Driver feedback menu to coach your drivers to be safer drivers.

Changes in the MyFleetistics device editor section will not change the device names in MyGeotab. This integration has not been completed so copy and paste the name if you want the two to match.

Click the link below to watch a video to give you an overview of GPS tracking, telematics and engine diagnostics information.

Video Presentation 34:11 PowerPoint presentation on GPS tracking, telematics and diagnostics

Types of Odometer Data

Actual Odometer (AO)

AO is the value taken from the vehicle and is the value displayed on the dashboard. AO is calculated using a worm gear on the transmission. This gear can wear over time as can the other parts on the vehicle that impact the number of revolutions the gear makes. Tires are the biggest contributing factor to inaccurate odometer information . When a car or truck is made the tires are a specific size with 100% tread. If the tire size is changed or 50% of the tread is worn off, the diameter of the tire changes which changes the number of revolutions per mile made by the gear measuring and reporting the odometer value.

Virtual Odometer (VO)

VO is mileage calculated by the Geotab GPS device. The Geotab device measures the distance between GPS data points. The more data poins, the more accurate the calculation. When a vehicle does not report odometer data as part of the engine diagnostic codes, it uses VO to determine mileage. Customers on the HOS, Pro or ProPlus plan will receive engine diagnostics data which includes AO if avalailable from most fleet vehicles. Customers on the Base plan will not get AO data but will get VO data on the Trips report but will not be able to run an odometer report which is based on AO. Because VO is not impacted by things like tire size, VO is often more accurate than AO.

It is important to enter the starting odometer value when using VO. This is enter under Vehicles>(selecte vehicle)>Odometer.

Indicates Virtual Odometer in Geotab Vehicle Editor

Related Links
	Geotab Article
	Variations in Odometer Readings
	10 tips: Nab odometer roll-back scammers

If you are experiencing "bad" GPS data or inaccurate GPS data, there are a variety of potential reasons. Generally changing the location or position of the GPS device or moving the vehicle to an open area will resolve the issue.

Things to check

1. GPS device is in a location where it cannot "see" or receive enough signals from the GPS satellites to accurately determine position. By relating the device to an area with less metal or other obstacles, you may start to have better reception.
2. The GPS device has a semi-directional GPS antenna. Rotating the GPS device may improve reception. The letter on the device does not reflect the direction of the antenna.
3. Environmental conditions can degrade a GPS signal. Pine trees, tall buildings, metal sheds and garages are common obstructions. Move the vehicle if overhead obstructions may be causing the issue.
4. Proper installation is another factor. Ensuring the GPS device is getting the proper amount of electricity all the time is important. Do not wire to data wires which fluctuate and can damage the vehicle.

Related Links
	External Reference to Bad GPS Data

To change your time zone in Geotab, first log into MyFleetistics. Open the Geotab window by clicking "Telematics & Dashcams" then "Geotab". On the left side of the menu, click MyGeotab-> Administration-> Users. Once you see a list of users, select yours and click the UI Settings tab-> Time zone (make your change here)-> then click Save. Once you have done this, your reports will show up with the correct time zone you have chosen.

MyFleetistics Password is Not Working

• Select Reset Password on the login screen. (www.fleetistics.com/login)
• Ensure your password meets requirements for complexity.
• If can log into MyFleetistics but not Geotab or Fleetistics LITE, you can change your password from your profile. Click on your name in the top left corner. Select Reset Password and follow the steps. (Hint - Selecting Forgot Password is much easier)

Geotab and Fleetistics LITE Password is Not Working

• Both systems use the same password as MyFleetistics. The MyFleetistisc password is passed to the GPS platform but the GPS platform cannot pass back any changes for security. Therefore, only change your password in your MyFleetistics profile (click your name in the top left) or choose Forgo Password on the Fleetistics login page. (www.fleetistics.com/login)
• Ensure your password meets requirements for complexity. This may have been set by your Geotab account administrator under Administration>Services
  

Fleetistics ONE Passowrd is Not Working

• Submit a support ticket to have it reset
• Before logging in press Ctrl + F5 on your keyboad and delete your cookies

Reset Email Not Received

• If you do not receive the password reset email, check your email spam and junk folders and have your IT department white list fleetistics.com and myfleetistics.com.

"I'm trying to find out where I can create custom fields so my uploads can match and associate Order IDs to the trucks carrying them.
Please let me know if this is supported. Thank you."

When exporting reports to Excel to view or edit, you can customize the data that is included in the Excel report but you cannot merge or add external data to the Excel doc and upload it back into MyGeotab.
Contact your account manager to discuss custom data solutions or a possible marketplace partner service.

The IFTA report can provide mileage driven throughout the month. It can also provide daily mileage by choosing a date from the Custom option available from the date options area of the Options window. To run the IFTA report:

1. Click Activity in the left menu.
2. Click the IFTA Report option and the report window opens with the Options window displayed.
3. Specify the date range to inclide by making clicking a button in the Date Period area of the window.
4. Specify if the report is to include historic vehicle by clicking the yes/no buttons to the right of the option label.
5. Specify the vehicles to include by making a selection from the Vehicles menu.
6. Once all selections are made, click the Apply Changes button and the report is displayed.

1. Click the gear on the top right of the screen or click the link below to access the group settings template.
2. Click Tools and Settings.
3. Click Import Group Settings.
4. Click File Template "Download"
5. Enter Data into the required fields
6. After data has been entered click choose file.
7. Select the file location and click OK.

1. The Audit Log is accessed by clicking System in the left menu, then clicking Audit Log.
2. Select the audit type to locate. Examples include delete message, view messages, send message.

3. Once the returns are displayed, select Advanced from the View menu and the formated report is displayed. To view the report in Excel, click the Excel icon located near the top of the window.

To view vehicles on a map, select the vehicles to display from the menu located on the left side above the map. An option is provide to display all vehicles. The menu is interactive so vehicles can be selected and de-selected.

Click the link to download a .pdf which you can print and reference as you go through the setup process.

1. It is very important that you register for training inside MyFleetistics>Help Center>Live Training.
2. Completing the Fleetistics Academy online self-paced training will also improve your understanding and ROI. This should be completed by all department, branch and service managers to ensure everyone knows what is available to them from the data
3. Fleetistics.tv has a lot of videos to help you understand the installation process, troubleshooting and using the system. Your account manager is available should you have any issues or questions.

Please contact your account manager if you have any issues or concerns. Thank you for your business.

Getting Started
PDF to print and reference

Data security by Geotab
Read more

Geotab Security
Information and Documents

The Geotab map refreshes every 20 seconds.

The Lite map refreshes on demand.

There are 3 aspects to a GPS system providing data on a map.
1. GPS device log rate.
2. GPS device transmit rate from the vehicle to the network.
3. Map refresh rate.

German Greek English Spanish French Hungarian Italian Lao Dutch Polish Portuguese Romanian Russian Slovak Serbian Turkish

Zones are a key feature that can help your business in several ways. The more zones you use the easier it is to read and understand the data.

1. When you create a zone, the zone name replaces the address in reports. This enables you to understand the report more quickly because you will recognize "Tom's Home" or "ABC Transport" quickly compared to seeing the address. This reduces the time needed to go through the data and improves your ability to make decisions on the data.

2. Zones can be used with rules and alerts. Rules can be created that alert when a vehicle enters, exits, stops in, or stops outside of a zone. This can help with notifying you or customers based on vehicles being in the area or being in areas they should not be.

3. Customer zones enable you to track time spent at a customer location. This data can be used for confirming the quality of service, time spent with a customer is to long or to short, verify hours billed and confirm on-time service.

4. Zones can be color coded by type. Home zones may be blue where customer zones may be red. This allows for rapid understanding of a drivers activity just by glancing at a map.

5. Zones can be set to expire in X days. This keeps your map and reports clutter free when you will not be returning to a location.

6. Dispatching uses zones to build the route. You can send a single zone or multiple zones to the driver as a route.

Watchdog Report by Minute Keeping track of telematics device health is an important task that’s often overlooked. Manage device uptime with the Watchdog Report. Devices are tested throughout the day to ensure they are communicating via the cellular network and accurately recording trips made by fleet drivers and their vehicles. This version of the Watchdog Report allows you to monitor communication status minute by minute as compared to the default report. See which devices have been offline for 5-30 mins, 30-60 mins, and 60+ mins. The email setting makes it possible to have this fleet management report sent direct to your inbox when device communication is delayed longer than 5 minutes. Save the report to your desktop, customize and upload to your Geotab account.

Active tracking is hyper logging and display of vehicle position information for GO Series devices only. Active Tracking is made possible with increased data logging frequency and animation in MyGeotab. The animation feature displays estimates of the real-time location of the vehicle onto the live map. Viewers are able to watch a simulated icon of the vehicle as it is moving. This new feature provides dispatchers and fleet managers with a very accurate depiction of where a vehicle enabled with this technology is at any given time.

View more
Active Tracking Explation

The Dynamic Vehicle Maintenance Reminder Report helps fleet managers stay informed on vehicle maintenance. This report is distributed via email when the date due, distance due, or hours due in a reminder rule are within the values specified on the Summary sheet. Criteria is entered in cells B5 - B7 of the Summary sheet. Note, the population of at least one cell is required for email distribution to occur. This report applies to GO Series devices only.

GO Maintenance Reminders Learn more

The general process is to save the Excel file to your desktop, edit the file, save again and then upload to your Geotab account. There are few points that merit mentioning; 1. The group structure should support distribution goals; 2. Multiple reports can't be combined. 3. Do not edit or change the data on the hidden Data tab; 4. Use .xls or .xlsx files; 5. Use a naming convention to organize your reports, i.e., Fleetistics_DeviceStatus_Mgmt GO Series only.

Video on Customizing Reports
Click to watch

How to archive a vehicle/asset

Devices can be removed from the system but still maintain the data collected by the device from the vehicle. This is useful for retrieiving data if needed after the device has been removed. 

Purpose: This article provide instructions for removing a vehicle/asset by archiving, instead of deleting/removing. This procedure keeps all of the data reported by the devicefor at least the last year.  

Procedure: 

1. Click Vehicles & Assets (1) in the left menu. 
2. Select the vehicle/asset to remove.
3. Click Remove at the top of the page (2).
4. In the Remove Device window appears, click Archive Assets (3).

Additional Note: If you encounter any issues, please open a support case. The link below contains instructions on creating a support case. https://www.fleetistics.com/support-cases-made-easy/.

How to view vehicle faults 

Purpose:  This article outlines the procedure for viewing reported engine faults for a vehicle. Monitoring engine faults can provide insight into potential vehicle issues that can take a vehicle out of serivce. Also any unauthorized device removal is reported through engine faults. 

Procedure:  

1. In the left menu click Engine & Maintenance (1) > Engine and Device(2) > Faults(3),
2. Select desired options filters (4)
3. Select vehicle/device, date period, and fault to locate or leave blank for all faults.
4. Specify the date range.

Additional Note: If you encounter issues, please open a support case for assistance. The link below will contain instructions on how to create a support case. https://www.fleetistics.com/support-cases-made-easy/. 

Drivewyze Fleet Management 

Category:  Drivewyze

Purpose: This article will go over the basics of how to synchronize your fleet with Drivewyze and edit any information on the Drivewyze tab.

Procedure: From the left-hand side menu in Geotab click on the Drivewyze tab(1), From this interface, you will be able to access the vehicle, driver, and fleet details. You will also be able to manage the Drivewyze subscription levels and edit any incorrect/missing information. The vehicles and drivers tabs show you a table of the fleet information that has been synced. Select the edit icon(blue pencil)  to view driver details or view and modify vehicle details(2). 

Additional Note: If you are having any issues, please open a support case for further assistance. The link b

Geotab offers an option to replace a current device with another. This feature maintains all existing data such as trip histories, exceptions, engine data, ELD/Hour of Service data, and DVIR reports. If the instructions to not match your user interface, click the link below for legacy instructions.

To replace a device, a user must have the clearance "Administer devices" (delete/unplug/replace)

Administer devices enabled.
1. Click the Vehicles & Assets option in the left menu (figure 1).
2. Select the vehicle by clicking the vehicle name in the list.
3. Scroll to the center of the Asset tab and find the Replace with new device button (figure 2).
4. Click the Replace with new device button located under the device serial number field (figure 3). Once the button is clicked a new window is displayed.
5. Enter the serial number for the NEW device in the Serial Number field (figure 4).
6. Finally, click the OK button near the top of the window and the change is complete.

Select the instructions that match your user interface.  
Download Instructions 
Legacy Version Instructions

Use the links below to locate the OBD port in a vehicle.

	CarMD – North America Only
	Innova DLC Locator - North America only
	The Diagnostic Box - North America & Europe
	Outils OBD Facile - North America & Europe
	Progressive

Heavy Duty Vehicles (J1939 and J1708)

Most heavy duty vehicles will have a round 9-ppin deutsch connector, depending on the age of the vehicle it may have a 6 pin. There are two potential protocols, J1939 and J1708. Below you will find the pin-out information for each along with their respective harness.

The new firmware release enables GO4v3, GO5 and GO6 devices with a 9-pin HD harness to support both J1708 and J1939 protocols simultaneously. In previous versions of firmware, a device installed in a vehicle with dual J1708 and J1939 protocols was limited to logging fault data from the J1939 bus only. The new firmware allows devices installed in vehicles with dual J1708/J1939 protocols to log J1708 faults also.

T-Mobile can roam into Canada but AT&T cannot. Customers based in the US which go into Canada must have T-Mobile devices and service  If the customer is based in Canada and roams into the US, Rogers is the correct option. Devices cannot be switched or upgraded so customers must get the correct device to start or purchase new devices.

Phone numbers cannot be added to a device. They are data only devices and do not support voice. Adding voice or increasing data consumption would be a different solution.

There are several possible explanations.

1. The vehicle may have been parked outside of cellular coverage. When the vehicle re-enters cell coverage, it will update the trip data.
2. The device could be malfunctioning.
3. The device may have been unplugged at the last reported location.

Quick Troubleshooting.

1. The first thing to check is that the device has lights on the front when the vehicle is running. This is a very basic function check. If in down, power cycle the device by unplugging and plugging back into to restart the device.
2. Put the device in another vehicle with a know working OBD port and take it for a test drive. If it updates, there is an issue with the vehicle, not the device.

Contact support to open a support case and get help resolving the issue.

The quickest and easiest test is to put the GPS device into another vehicle that is tracking properly. If it tracks correctly in the second vehicle, the issue is most likely the OBD port or ECM on the original vehicle. If it does not track on the second vehicle, it is most likely the GPS device. Contact support with the device information and the test date and time for verification if it reported correctly in the second vehicle. When confirmed, a replacement device will be provided based on the warranty associated with the device.

Light Duty OBD2 Vehicles

Most light duty vehicles have what is called an ALDL connector and the typical location is on the driver's side. The ALDL connector has 16 pins and looks like:

With respect to GPS modules, they are merely receivers operating at two low power radio signals (L1 – Civilian and L2-Military). The civilian frequency is 1575.42 MHz in the UHF band. I am not aware of any documentation/literature where a GPS module’s radiated emissions has been shown to cause interference. This is a signal we are all being hit with every day just like music radio signals. GPS units simply receive the broadcasted signal. 

In addition to using FCC compliant RADIO and GPS modules, the Marcus Radio Modules have passed FCC Part 15 Class A (Commercial/Industrial/Vehicle) or Class B (Residential/In-home) specifications. Part B is recommended for any consumer product in close proximity to a user’s unintentional emission sensitive areas (head/chest) and include cell phones, calculators, radios, computers, mp3 players, etc…  

• Coleman GPRS – FCC Part 15 Class A
• MRM Tuna – FCC Part 15 Class A
• MRM Wahoo I/II – FCC Part 15 Class B
• FCC Grant Attached  

Our devices also undergo PTCRB (GSM/UMTS Standards Body) certification for the purposes of isolating any unintentional emissions that might interfere with carrier frequencies, towers, communication, etc… These tests are based on our recommended product configuration including antenna placement and proximity to the radio module.  

The FDA and the Health Industry Manufacturer’s Association  (HIMA) specifically recommends a separation of six inches between any handheld wireless radio and a pacemaker. In fact, you will find this caution in Garmin manuals for handhelds with radio receivers/transmitters.  Given the prevalence of GPS and mobile phones, it is expect that modern pacemakers are accordingly shielded (see below).  

The American Heart Association states:

• “Modern pacemakers have built-in features to protect them from most types of interference produced by other electrical devices you might encounter in your daily routine.”
• “Cellphones available in the United States (less than 3 watts) don't seem to damage pulse generators or affect how the pacemaker works. “  

The AMA also publishes a list of devices that may interfere with pacemakers. Currently, no GPS handheld or vehicle mounted devices are listed.

Differential Global Positioning System (DGPS) is an enhancement to Global Positioning System that uses a network of fixed, ground-based reference stations to broadcast the difference between the positions indicated by the satellite systems and the known fixed positions. These stations broadcast the difference between the measured satellite pseudoranges and actual (internally computed) pseudoranges, and receiver stations may correct their pseudoranges by the same amount. The correction signal is typically broadcast over UHF radio modem.

The term can refer both to the generalized technique as well as specific implementations using it. It is often used to refer specifically to systems that re-broadcast the corrections from ground-based transmitters of shorter range. For instance, the United States Coast Guard runs one such system in the US and Canada on the longwave radio frequencies between 285 kHz and 325 kHz. These frequencies are commonly used for marine radio, and are broadcast near major waterways and harbors.

Post-processing is used in Differential GPS to obtain precise positions of unknown points by relating them to known points such as survey markers.

The GPS measurements are usually stored in computer memory in the GPS receivers, and are subsequently transferred to a computer running the GPS post-processing software. The software computes baselines using simultaneous measurement data from two or more GPS receivers.

The baselines represent a three-dimensional line drawn between the two points occupied by each pair of GPS antennas. The post-processed measurements allow more precise positioning, because most GPS errors affect each receiver nearly equally, and therefore can be cancelled out in the calculations.

Differential GPS measurements can also be computed in real-time by some GPS receivers if they receive a correction signal using a separate radio receiver, for example in Real Time Kinematic (RTK) surveying or navigation.

To download the installation instructions for the FleetisticsONE XT2150 please click the link under the Related Links.

Installation Instructions for XT2150, XT2160, XT2169
This link allows for downloading a PDF of the installation instructions.

The devices on the Lite platform update at various rates ranging from 1 minute to several hours depending on the device application. Vehicle devices update every 1 minute where battery powered assets update every few hours to conserve battery life. The vehicle profile also logs information based on changes in speed and direction to provide more accurate track data. This same method for a bulldozer would create data that would be difficult to view and read in reports.

In the US, the Moss Magnuson Warranty Act of 1975 specifically prohibits manufacturers from voiding the warranty due to aftermarket additions to the vehicle. Furthermore, Geotab has spent considerable time ensuring that our products cannot cause harm to the vehicle.

FleetisticsONE offers several configurations dependant on the targeted application, the device, and the device model. A typical vehicle tracking device updates once per minute or more frequently in urban environments. Devices utilized for equipment or asset tracking are programmed differently and generally update less frequently. Ask your account manager for more details on your specific devices. FleetisticsONE devices include: AT, XT, MT, and VI devices. GO Series devices from Geotab are not included.

No, the devices will go into sleep mode when the vehicle is turned off and will only draw about 5 mA of current. A typical car battery has a capacity of 50 Ah, which means it will take over a year before the device can come close to depleting the battery.

Browser Related Issues

If clients are having a hard time logging in or accessing the system due to browser issues. Do the following:  

1. Ensure the client is using a supported browser. Internet Explorer is not support, Firefox is recommended. The system will also support Microsoft Edge, Google Chrome, and Safari.
2. If the client is using a supported browser, then have them clear the cache. This is done differently for every browser.

Clearing the browser cache in Google Chrome.

1. Hit the 3 vertical buttons on the top right-hand side of the browser.

2. From the drop-down menu, click on Settings

3. From settings scroll all the way down and click advanced.

4. From the advanced drop-down menu, navigate to Privacy and Security and you will see the clear browsing data.

Clearing the browsing history in Firefox:

1.       Click on the gear icon that is located at the top right-hand side of the browser.

2. From the gear icon, click on Privacy and Security on the left-hand side menu with the lock icon next to it

3. From the Privacy and Security window click on the clear data button.

If you are still having issues, please contact support at 1(800)481-1319.

There are several ways to share data depending on the GPS platform and data to be shared. Common sharing methods include:

1. Schedule reports to be emailed on a regular basis; daily, weekly or monthly.
2. Give employees access to the portal but with limited access rights.
3. Create a sharing link which shows the vehicles location on a map but does not share other information

Contact Fleetistics training for assistance in setting up your sytem.

The vehicle is moving from the speed zone before it communicates with the server where the posted road speed is checked. The device must connect a second time for the alert to be triggered on the device in the vehicle. At 70 mph the vehicle may be several miles further before the driver is alerted. Adding the ProPlus service provides much faster results. This increases the communication rate with the server so the violation is recognized and sent back to the vehicle much more quickly than the standard rate used for Pro service. Communication in ProPlus takes place about every 20 seconds compared to every few minutes in Pro mode.

If you are seeing a blank or white screen when trying to open a GPS platform from the MyFleetistics menu, the X-Frame policy is causing an issue. To correct this add the appropriate browser extension. If you are unable to install the certified browser add-in, contact your IT department. An exception may need to be added for myfleetistics.com and mygeotab.com.

This is a fix Firefox and Chrome.

Firefox https://addons.mozilla.org/en-US/firefox/addon/ignore-x-frame-options-header/

Chrome https://chrome.google.com/webstore/detail/ignore-x-frame-headers/gleekbfjekiniecknbkamfmkohkpodhe?hl=en-US

Edge No issue detected

Safari Not tested - Not supported

	Firefox X-Frame Add-in Resolves page will not load from MyFleetistics.
	Chrome X-Frame Add-In Resolves page will not load from MyFleetistics.

Click the link below to watch a video to give you an overview of GPS tracking, telematics and engine diagnostics information.

Video Presentation 34:11 PowerPoint presentation on GPS tracking, telematics and diagnostics

If you are experiencing "bad" GPS data or inaccurate GPS data, there are a variety of potential reasons. Generally changing the location or position of the GPS device or moving the vehicle to an open area will resolve the issue.

Things to check

1. GPS device is in a location where it cannot "see" or receive enough signals from the GPS satellites to accurately determine position. By relating the device to an area with less metal or other obstacles, you may start to have better reception.
2. The GPS device has a semi-directional GPS antenna. Rotating the GPS device may improve reception. The letter on the device does not reflect the direction of the antenna.
3. Environmental conditions can degrade a GPS signal. Pine trees, tall buildings, metal sheds and garages are common obstructions. Move the vehicle if overhead obstructions may be causing the issue.
4. Proper installation is another factor. Ensuring the GPS device is getting the proper amount of electricity all the time is important. Do not wire to data wires which fluctuate and can damage the vehicle.

Related Links
	External Reference to Bad GPS Data

MyFleetistics Password is Not Working

• Select Reset Password on the login screen. (www.fleetistics.com/login)
• Ensure your password meets requirements for complexity.
• If can log into MyFleetistics but not Geotab or Fleetistics LITE, you can change your password from your profile. Click on your name in the top left corner. Select Reset Password and follow the steps. (Hint - Selecting Forgot Password is much easier)

Geotab and Fleetistics LITE Password is Not Working

• Both systems use the same password as MyFleetistics. The MyFleetistisc password is passed to the GPS platform but the GPS platform cannot pass back any changes for security. Therefore, only change your password in your MyFleetistics profile (click your name in the top left) or choose Forgo Password on the Fleetistics login page. (www.fleetistics.com/login)
• Ensure your password meets requirements for complexity. This may have been set by your Geotab account administrator under Administration>Services
  

Fleetistics ONE Passowrd is Not Working

• Submit a support ticket to have it reset
• Before logging in press Ctrl + F5 on your keyboad and delete your cookies

Reset Email Not Received

• If you do not receive the password reset email, check your email spam and junk folders and have your IT department white list fleetistics.com and myfleetistics.com.

There are several possible explanations.

1. The vehicle may have been parked outside of cellular coverage. When the vehicle re-enters cell coverage, it will update the trip data.
2. The device could be malfunctioning.
3. The device may have been unplugged at the last reported location.

Quick Troubleshooting.

1. The first thing to check is that the device has lights on the front when the vehicle is running. This is a very basic function check. If in down, power cycle the device by unplugging and plugging back into to restart the device.
2. Put the device in another vehicle with a know working OBD port and take it for a test drive. If it updates, there is an issue with the vehicle, not the device.

Contact support to open a support case and get help resolving the issue.

1. Click the gear on the top right of the screen or click the link below to access the group settings template.
2. Click Tools and Settings.
3. Click Import POI from Excel.
4. Click Group Settings import Excel file template: Download
5. Enter Data into the required fields
6. After data has been entered click choose file.
7. Select the file location and click OK.

Geofences are a key feature that can help your business in several ways. The more geofences you use the easier it is to read and understand the data.

1. When you create a geofences , the geofences name replaces the address in reports. This enables you to understand the report more quickly because you will recognize "Tom's Home" or "ABC Transport" quickly compared to seeing the address. This reduces the time needed to go through the data and improves your ability to make decisions on the data.

2. Geofences can be used with rules and alerts. Rules can be created that alert when a vehicle enters, exits, stops in, or stops outside of a geofences. This can help with notifying you or customers based on vehicles being in the area or being in areas they should not be.

3. Customer geofences enable you to track time spent at a customer location. This data can be used for confirming the quality of service, time spent with a customer is to long or to short, verify hours billed and confirm on-time service.

4. Geofences can be color coded by type. Home geofences may be blue where customer geofences may be red. This allows for rapid understanding of a drivers activity just by glancing at a map.

5. Geofences can be set to expire in X days. This keeps your map and reports clutter free when you will not be returning to a location.

6. Dispatching uses geofences to build the route. You can send a single geofences or multiple geofences to the driver as a route.

FleetisticsONE offers several configurations dependant on the targeted application, the device, and the device model. A typical vehicle tracking device updates once per minute or more frequently in urban environments. Devices utilized for equipment or asset tracking are programmed differently and generally update less frequently. Ask your account manager for more details on your specific devices. FleetisticsONE devices include: AT, XT, MT, and VI devices. GO Series devices from Geotab are not included.

Use the links below to locate the OBD port in a vehicle.

	CarMD – North America Only
	Innova DLC Locator - North America only
	The Diagnostic Box - North America & Europe
	Outils OBD Facile - North America & Europe
	Progressive

Heavy Duty Vehicles (J1939 and J1708)

Most heavy duty vehicles will have a round 9-ppin deutsch connector, depending on the age of the vehicle it may have a 6 pin. There are two potential protocols, J1939 and J1708. Below you will find the pin-out information for each along with their respective harness.

The new firmware release enables GO4v3, GO5 and GO6 devices with a 9-pin HD harness to support both J1708 and J1939 protocols simultaneously. In previous versions of firmware, a device installed in a vehicle with dual J1708 and J1939 protocols was limited to logging fault data from the J1939 bus only. The new firmware allows devices installed in vehicles with dual J1708/J1939 protocols to log J1708 faults also.

T-Mobile can roam into Canada but AT&T cannot. Customers based in the US which go into Canada must have T-Mobile devices and service  If the customer is based in Canada and roams into the US, Rogers is the correct option. Devices cannot be switched or upgraded so customers must get the correct device to start or purchase new devices.

Phone numbers cannot be added to a device. They are data only devices and do not support voice. Adding voice or increasing data consumption would be a different solution.

There are several possible explanations.

1. The vehicle may have been parked outside of cellular coverage. When the vehicle re-enters cell coverage, it will update the trip data.
2. The device could be malfunctioning.
3. The device may have been unplugged at the last reported location.

Quick Troubleshooting.

1. The first thing to check is that the device has lights on the front when the vehicle is running. This is a very basic function check. If in down, power cycle the device by unplugging and plugging back into to restart the device.
2. Put the device in another vehicle with a know working OBD port and take it for a test drive. If it updates, there is an issue with the vehicle, not the device.

Contact support to open a support case and get help resolving the issue.

The quickest and easiest test is to put the GPS device into another vehicle that is tracking properly. If it tracks correctly in the second vehicle, the issue is most likely the OBD port or ECM on the original vehicle. If it does not track on the second vehicle, it is most likely the GPS device. Contact support with the device information and the test date and time for verification if it reported correctly in the second vehicle. When confirmed, a replacement device will be provided based on the warranty associated with the device.

Light Duty OBD2 Vehicles

Most light duty vehicles have what is called an ALDL connector and the typical location is on the driver's side. The ALDL connector has 16 pins and looks like:

With respect to GPS modules, they are merely receivers operating at two low power radio signals (L1 – Civilian and L2-Military). The civilian frequency is 1575.42 MHz in the UHF band. I am not aware of any documentation/literature where a GPS module’s radiated emissions has been shown to cause interference. This is a signal we are all being hit with every day just like music radio signals. GPS units simply receive the broadcasted signal. 

In addition to using FCC compliant RADIO and GPS modules, the Marcus Radio Modules have passed FCC Part 15 Class A (Commercial/Industrial/Vehicle) or Class B (Residential/In-home) specifications. Part B is recommended for any consumer product in close proximity to a user’s unintentional emission sensitive areas (head/chest) and include cell phones, calculators, radios, computers, mp3 players, etc…  

• Coleman GPRS – FCC Part 15 Class A
• MRM Tuna – FCC Part 15 Class A
• MRM Wahoo I/II – FCC Part 15 Class B
• FCC Grant Attached  

Our devices also undergo PTCRB (GSM/UMTS Standards Body) certification for the purposes of isolating any unintentional emissions that might interfere with carrier frequencies, towers, communication, etc… These tests are based on our recommended product configuration including antenna placement and proximity to the radio module.  

The FDA and the Health Industry Manufacturer’s Association  (HIMA) specifically recommends a separation of six inches between any handheld wireless radio and a pacemaker. In fact, you will find this caution in Garmin manuals for handhelds with radio receivers/transmitters.  Given the prevalence of GPS and mobile phones, it is expect that modern pacemakers are accordingly shielded (see below).  

The American Heart Association states:

• “Modern pacemakers have built-in features to protect them from most types of interference produced by other electrical devices you might encounter in your daily routine.”
• “Cellphones available in the United States (less than 3 watts) don't seem to damage pulse generators or affect how the pacemaker works. “  

The AMA also publishes a list of devices that may interfere with pacemakers. Currently, no GPS handheld or vehicle mounted devices are listed.

Differential Global Positioning System (DGPS) is an enhancement to Global Positioning System that uses a network of fixed, ground-based reference stations to broadcast the difference between the positions indicated by the satellite systems and the known fixed positions. These stations broadcast the difference between the measured satellite pseudoranges and actual (internally computed) pseudoranges, and receiver stations may correct their pseudoranges by the same amount. The correction signal is typically broadcast over UHF radio modem.

The term can refer both to the generalized technique as well as specific implementations using it. It is often used to refer specifically to systems that re-broadcast the corrections from ground-based transmitters of shorter range. For instance, the United States Coast Guard runs one such system in the US and Canada on the longwave radio frequencies between 285 kHz and 325 kHz. These frequencies are commonly used for marine radio, and are broadcast near major waterways and harbors.

Post-processing is used in Differential GPS to obtain precise positions of unknown points by relating them to known points such as survey markers.

The GPS measurements are usually stored in computer memory in the GPS receivers, and are subsequently transferred to a computer running the GPS post-processing software. The software computes baselines using simultaneous measurement data from two or more GPS receivers.

The baselines represent a three-dimensional line drawn between the two points occupied by each pair of GPS antennas. The post-processed measurements allow more precise positioning, because most GPS errors affect each receiver nearly equally, and therefore can be cancelled out in the calculations.

Differential GPS measurements can also be computed in real-time by some GPS receivers if they receive a correction signal using a separate radio receiver, for example in Real Time Kinematic (RTK) surveying or navigation.

Click the link to download a .pdf which you can print and reference as you go through the setup process.

1. It is very important that you register for training inside MyFleetistics>Help Center>Live Training.
2. Completing the Fleetistics Academy online self-paced training will also improve your understanding and ROI. This should be completed by all department, branch and service managers to ensure everyone knows what is available to them from the data
3. Fleetistics.tv has a lot of videos to help you understand the installation process, troubleshooting and using the system. Your account manager is available should you have any issues or questions.

Click here to download the Getting Started Guide

To download the installation instructions for the FleetisticsONE XT2150 please click the link under the Related Links.

Installation Instructions for XT2150, XT2160, XT2169
This link allows for downloading a PDF of the installation instructions.

The devices on the Lite platform update at various rates ranging from 1 minute to several hours depending on the device application. Vehicle devices update every 1 minute where battery powered assets update every few hours to conserve battery life. The vehicle profile also logs information based on changes in speed and direction to provide more accurate track data. This same method for a bulldozer would create data that would be difficult to view and read in reports.

In the US, the Moss Magnuson Warranty Act of 1975 specifically prohibits manufacturers from voiding the warranty due to aftermarket additions to the vehicle. Furthermore, Geotab has spent considerable time ensuring that our products cannot cause harm to the vehicle.

No, the devices will go into sleep mode when the vehicle is turned off and will only draw about 5 mA of current. A typical car battery has a capacity of 50 Ah, which means it will take over a year before the device can come close to depleting the battery.

Browser Related Issues

If clients are having a hard time logging in or accessing the system due to browser issues. Do the following:  

1. Ensure the client is using a supported browser. Internet Explorer is not support, Firefox is recommended. The system will also support Microsoft Edge, Google Chrome, and Safari.
2. If the client is using a supported browser, then have them clear the cache. This is done differently for every browser.

Clearing the browser cache in Google Chrome.

1. Hit the 3 vertical buttons on the top right-hand side of the browser.

2. From the drop-down menu, click on Settings

3. From settings scroll all the way down and click advanced.

4. From the advanced drop-down menu, navigate to Privacy and Security and you will see the clear browsing data.

Clearing the browsing history in Firefox:

1.       Click on the gear icon that is located at the top right-hand side of the browser.

2. From the gear icon, click on Privacy and Security on the left-hand side menu with the lock icon next to it

3. From the Privacy and Security window click on the clear data button.

If you are still having issues, please contact support at 1(800)481-1319.

There are several ways to share data depending on the GPS platform and data to be shared. Common sharing methods include:

1. Schedule reports to be emailed on a regular basis; daily, weekly or monthly.
2. Give employees access to the portal but with limited access rights.
3. Create a sharing link which shows the vehicles location on a map but does not share other information

Contact Fleetistics training for assistance in setting up your sytem.

This document explains how the API for the Fleetistics LITE platform is structured for developers. This will enable the data to be used outside the MyFleetistics environment. A small fee may apply.

View online document

Click the link to download a .pdf which you can print and reference as you go through the setup process.

1. It is very important that you register for training inside MyFleetistics>Help Center>Live Training.
2. Completing the Fleetistics Academy online self-paced training will also improve your understanding and ROI. This should be completed by all department, branch and service managers to ensure everyone knows what is available to them from the data
3. Fleetistics.tv has a lot of videos to help you understand the installation process, troubleshooting and using the system. Your account manager is available should you have any issues or questions.

Getting Started with Lite PDF to print and use while getting started

Please contact your account manager if you have any issues or concerns. Thank you for your business.

If you are seeing a blank or white screen when trying to open a GPS platform from the MyFleetistics menu, the X-Frame policy is causing an issue. To correct this add the appropriate browser extension. If you are unable to install the certified browser add-in, contact your IT department. An exception may need to be added for myfleetistics.com and mygeotab.com.

This is a fix Firefox and Chrome.

Firefox https://addons.mozilla.org/en-US/firefox/addon/ignore-x-frame-options-header/

Chrome https://chrome.google.com/webstore/detail/ignore-x-frame-headers/gleekbfjekiniecknbkamfmkohkpodhe?hl=en-US

Edge No issue detected

Safari Not tested - Not supported

	Firefox X-Frame Add-in Resolves page will not load from MyFleetistics.
	Chrome X-Frame Add-In Resolves page will not load from MyFleetistics.

Click the link below to watch a video to give you an overview of GPS tracking, telematics and engine diagnostics information.

Video Presentation 34:11 PowerPoint presentation on GPS tracking, telematics and diagnostics

If you are experiencing "bad" GPS data or inaccurate GPS data, there are a variety of potential reasons. Generally changing the location or position of the GPS device or moving the vehicle to an open area will resolve the issue.

Things to check

1. GPS device is in a location where it cannot "see" or receive enough signals from the GPS satellites to accurately determine position. By relating the device to an area with less metal or other obstacles, you may start to have better reception.
2. The GPS device has a semi-directional GPS antenna. Rotating the GPS device may improve reception. The letter on the device does not reflect the direction of the antenna.
3. Environmental conditions can degrade a GPS signal. Pine trees, tall buildings, metal sheds and garages are common obstructions. Move the vehicle if overhead obstructions may be causing the issue.
4. Proper installation is another factor. Ensuring the GPS device is getting the proper amount of electricity all the time is important. Do not wire to data wires which fluctuate and can damage the vehicle.

Related Links
	External Reference to Bad GPS Data

MyFleetistics Password is Not Working

• Select Reset Password on the login screen. (www.fleetistics.com/login)
• Ensure your password meets requirements for complexity.
• If can log into MyFleetistics but not Geotab or Fleetistics LITE, you can change your password from your profile. Click on your name in the top left corner. Select Reset Password and follow the steps. (Hint - Selecting Forgot Password is much easier)

Geotab and Fleetistics LITE Password is Not Working

• Both systems use the same password as MyFleetistics. The MyFleetistisc password is passed to the GPS platform but the GPS platform cannot pass back any changes for security. Therefore, only change your password in your MyFleetistics profile (click your name in the top left) or choose Forgo Password on the Fleetistics login page. (www.fleetistics.com/login)
• Ensure your password meets requirements for complexity. This may have been set by your Geotab account administrator under Administration>Services
  

Fleetistics ONE Passowrd is Not Working

• Submit a support ticket to have it reset
• Before logging in press Ctrl + F5 on your keyboad and delete your cookies

Reset Email Not Received

• If you do not receive the password reset email, check your email spam and junk folders and have your IT department white list fleetistics.com and myfleetistics.com.

There are several possible explanations.

1. The vehicle may have been parked outside of cellular coverage. When the vehicle re-enters cell coverage, it will update the trip data.
2. The device could be malfunctioning.
3. The device may have been unplugged at the last reported location.

Quick Troubleshooting.

1. The first thing to check is that the device has lights on the front when the vehicle is running. This is a very basic function check. If in down, power cycle the device by unplugging and plugging back into to restart the device.
2. Put the device in another vehicle with a know working OBD port and take it for a test drive. If it updates, there is an issue with the vehicle, not the device.

Contact support to open a support case and get help resolving the issue.

Click the link to download a .pdf which you can print and reference as you go through the setup process.

1. It is very important that you register for training inside MyFleetistics>Help Center>Live Training.
2. Completing the Fleetistics Academy online self-paced training will also improve your understanding and ROI. This should be completed by all department, branch and service managers to ensure everyone knows what is available to them from the data
3. Fleetistics.tv has a lot of videos to help you understand the installation process, troubleshooting and using the system. Your account manager is available should you have any issues or questions.

Click here to download the Getting Started Guide

Geofences are a key feature that can help your business in several ways. The more geofences you use the easier it is to read and understand the data.

1. When you create a geofences , the geofences name replaces the address in reports. This enables you to understand the report more quickly because you will recognize "Tom's Home" or "ABC Transport" quickly compared to seeing the address. This reduces the time needed to go through the data and improves your ability to make decisions on the data.

2. Geofences can be used with rules and alerts. Rules can be created that alert when a vehicle enters, exits, stops in, or stops outside of a geofences. This can help with notifying you or customers based on vehicles being in the area or being in areas they should not be.

3. Customer geofences enable you to track time spent at a customer location. This data can be used for confirming the quality of service, time spent with a customer is to long or to short, verify hours billed and confirm on-time service.

4. Geofences can be color coded by type. Home geofences may be blue where customer geofences may be red. This allows for rapid understanding of a drivers activity just by glancing at a map.

5. Geofences can be set to expire in X days. This keeps your map and reports clutter free when you will not be returning to a location.

6. Dispatching uses geofences to build the route. You can send a single geofences or multiple geofences to the driver as a route.

Zones can be imported but not by customers. Zones provided to Fleetistics in a specific Excel spreadsheet format can be imported for customers for a fee. Contact your account manager for more information.

Phone numbers cannot be added to a device. They are data only devices and do not support voice. Adding voice or increasing data consumption would be a different solution.

There are several possible explanations.

1. The vehicle may have been parked outside of cellular coverage. When the vehicle re-enters cell coverage, it will update the trip data.
2. The device could be malfunctioning.
3. The device may have been unplugged at the last reported location.

Quick Troubleshooting.

1. The first thing to check is that the device has lights on the front when the vehicle is running. This is a very basic function check. If in down, power cycle the device by unplugging and plugging back into to restart the device.
2. Put the device in another vehicle with a know working OBD port and take it for a test drive. If it updates, there is an issue with the vehicle, not the device.

Contact support to open a support case and get help resolving the issue.

With respect to GPS modules, they are merely receivers operating at two low power radio signals (L1 – Civilian and L2-Military). The civilian frequency is 1575.42 MHz in the UHF band. I am not aware of any documentation/literature where a GPS module’s radiated emissions has been shown to cause interference. This is a signal we are all being hit with every day just like music radio signals. GPS units simply receive the broadcasted signal. 

In addition to using FCC compliant RADIO and GPS modules, the Marcus Radio Modules have passed FCC Part 15 Class A (Commercial/Industrial/Vehicle) or Class B (Residential/In-home) specifications. Part B is recommended for any consumer product in close proximity to a user’s unintentional emission sensitive areas (head/chest) and include cell phones, calculators, radios, computers, mp3 players, etc…  

• Coleman GPRS – FCC Part 15 Class A
• MRM Tuna – FCC Part 15 Class A
• MRM Wahoo I/II – FCC Part 15 Class B
• FCC Grant Attached  

Our devices also undergo PTCRB (GSM/UMTS Standards Body) certification for the purposes of isolating any unintentional emissions that might interfere with carrier frequencies, towers, communication, etc… These tests are based on our recommended product configuration including antenna placement and proximity to the radio module.  

The FDA and the Health Industry Manufacturer’s Association  (HIMA) specifically recommends a separation of six inches between any handheld wireless radio and a pacemaker. In fact, you will find this caution in Garmin manuals for handhelds with radio receivers/transmitters.  Given the prevalence of GPS and mobile phones, it is expect that modern pacemakers are accordingly shielded (see below).  

The American Heart Association states:

• “Modern pacemakers have built-in features to protect them from most types of interference produced by other electrical devices you might encounter in your daily routine.”
• “Cellphones available in the United States (less than 3 watts) don't seem to damage pulse generators or affect how the pacemaker works. “  

The AMA also publishes a list of devices that may interfere with pacemakers. Currently, no GPS handheld or vehicle mounted devices are listed.

Solar powered and designed for tough environments, this industrial IoT asset tracking device is intrinsically safe and maintenance free for tracking, monitoring and data collection. 

SmartOne Solar's integrated solar panel and battery capabilities deliver up to 10 years of life with little to no maintenance required. This asset GPS tracking device easily mounts to any fixed or mobile asset for intelligent tracking, monitoring. SmartOne Solar has unparalleled safety/device certifications such as ATEX, IECEx and North America, IP68/69K, HERO certifications, and others to meet the needs of every application.

Wide range of reporting capabilities Including;
   -   GPS Location reporting in 4 modes
   -   Geofencing with configurable range setting
   -   Stationary or in-motion reporting
   -   Reduced messaging & theft recovery modes
   -   Receives and transmits data from external sensors
   -   12 different reporting times
   -   Interval or 24-hour operation mode
   -   Alternate reporting schedules
   -   Low battery message
   -   Motion Sensor/Vibration parameter and scheduling
   -   Contact closure parameters
   -   Diagnostic messages
   -   Include Speed and Heading data in reported motion messages

Accessing Data

To view the GPS data and various messages, log into your MyFleetistics account. Click here. On the left, under the Telematics & Dashcam menu, select Fleetistics CORE. You can view the location of each message, administrative messages such as battery power and GPS satellites, and the location of each message on the map. This device is not like a vehicle tracking system. It is low resolution due to the per message cost. 

Programming

Devices must be returned to Fleetistics to be programmed. It is important to clearly communicate your tracking goals so Fleetistics and properly program the device or advise what the device can do if it does not match your goals exactly. It is highly recommended that customers purchase one device to test the configuration before ordering more in order to dial in the configuration before deploying multiple devices. 

Turn Device On/Off

The unit is turned on/off using a magnetic switch found in the black rubber piece. Remove the black rubber piece to turn the unit on. Keep this in a safe place. Any properly sized magnet with sufficient pull can be used if the original magnet is lost. Replace the rubber piece to turn the unit off. If shipping the unit via postal or courier service, it is imporant to turn the unit off using the rubber piece so the unit is not active while in transit. The on/off can also be used to establish a starting location with certain types of configurations. 

Messages

Satellite communication handled is manage by messages, not by megabytes like a cellular communication device. Each message either counts toward a message plan (ex 100 msg per month) or a fee is charged per message above the plan allotment. Improper mounting and programming can lead to more messages being used than intended. 

Installation Mounting Guidance

For optimum performance, mount the unit on a flat surface with a clear view of the sky. It is not designed to be mounted vertically. Although you may get some communication, updates will be less consistent and solar recharging will be reduced. 

• Screws with rubber washers (preferred)
• Magnets (purchase online)
• Rivots
• Metal zip ties

• Test the solar GPS device before deploying to the field
• Document the vehicle and the solar GPS unit so you can label them correctly in the GPS software online
• Power the device on by pressing the black button seen in the image. Listen for the click.
• If you ship the device the power must be off. Press the power button listening for the click.
• View the lights to ensure proper function.
• When testing the device should be outside with a clear view of the sky and in a good cell area for the network used.
• Do not pressure wash the units from less than 3′.
• Look at your GPS account online daily or weekly to spot issues quickly.

Approximate Coverage Area

The unit uses satellite communication, not cellular. Satellite communication provides coverage in many areas not available using cellular towers. Due to differences in frequency, satellite communication is much more sensitive to interferene from overhead obstacles compared to cellular communications. A cell phone will work in your home becuase the frequency and range enables the signals to pass through many obstacles. With a satellite phone, you must be outside with a clear view of the sky. In fleet tracking, this means limited overhead obstacles such as trees and buildings. 

Specifications

DIMENSIONS
3.25 IN (H) X 7 IN (W) X 1.125 IN (D)
8.26 CM (H) X 17.78 CM (W) X 2.86 CM (D)

WEIGHT 
13.5 oz/385 g
With optional mounting bracket 40.57 oz. (1150 g) 

OPERATING TEMPERATURE* 
-40° C to +65° C (-40° F to 149° F)
NOTE: The unit is certified intrinsically safe for hazardous environments over the temperature range of -40° C to +65° C (-40° F to 149° F).

INPUT VOLTAGE
10 TO 48 VDC
NOTE: Device is not intrinsically safe when any cable is connected.

BATTERY TYPE
Built-in rechargeable NiMH batteries (non-replaceable) 

CERTIFICATIONS & STANDARDS

• FCC, ISED, CE, AUS/NZ, ANATEL, INMETRO CERTIFICATE – LMP 19.0127 X, JQA(JAPAN), IFT, ARECOM, ENACOM, KCC, NCC, ASEP AND ICASA
• ATEX/IECEx  II 1 G,Ex ia IIC T4 Ga For international Zone 0 applications, HERO
• North America cETLus:
     - Class I, Division 1, Groups A-D, T4
     - Class I, Zone 0, AEx ia IIC T4 Ga
• WEEE Compliant
• GMPCS-MoU
• IP68/69K
• MIL-STD-810G for:
• Immersion
• Impact resistance
• Salt Fog
• Acidic Atmosphere
• Humidity
• Vibration

If you are seeing a blank or white screen when trying to open a GPS platform from the MyFleetistics menu, the X-Frame policy is causing an issue. To correct this add the appropriate browser extension. If you are unable to install the certified browser add-in, contact your IT department. An exception may need to be added for myfleetistics.com and mygeotab.com.

This is a fix Firefox and Chrome.

Firefox https://addons.mozilla.org/en-US/firefox/addon/ignore-x-frame-options-header/

Chrome https://chrome.google.com/webstore/detail/ignore-x-frame-headers/gleekbfjekiniecknbkamfmkohkpodhe?hl=en-US

Edge No issue detected

Safari Not tested - Not supported

	Firefox X-Frame Add-in Resolves page will not load from MyFleetistics.
	Chrome X-Frame Add-In Resolves page will not load from MyFleetistics.

Click the link below to watch a video to give you an overview of GPS tracking, telematics and engine diagnostics information.

Video Presentation 34:11 PowerPoint presentation on GPS tracking, telematics and diagnostics

If you are experiencing "bad" GPS data or inaccurate GPS data, there are a variety of potential reasons. Generally changing the location or position of the GPS device or moving the vehicle to an open area will resolve the issue.

Things to check

1. GPS device is in a location where it cannot "see" or receive enough signals from the GPS satellites to accurately determine position. By relating the device to an area with less metal or other obstacles, you may start to have better reception.
2. The GPS device has a semi-directional GPS antenna. Rotating the GPS device may improve reception. The letter on the device does not reflect the direction of the antenna.
3. Environmental conditions can degrade a GPS signal. Pine trees, tall buildings, metal sheds and garages are common obstructions. Move the vehicle if overhead obstructions may be causing the issue.
4. Proper installation is another factor. Ensuring the GPS device is getting the proper amount of electricity all the time is important. Do not wire to data wires which fluctuate and can damage the vehicle.

Related Links
	External Reference to Bad GPS Data

MyFleetistics Password is Not Working

• Select Reset Password on the login screen. (www.fleetistics.com/login)
• Ensure your password meets requirements for complexity.
• If can log into MyFleetistics but not Geotab or Fleetistics LITE, you can change your password from your profile. Click on your name in the top left corner. Select Reset Password and follow the steps. (Hint - Selecting Forgot Password is much easier)

Geotab and Fleetistics LITE Password is Not Working

• Both systems use the same password as MyFleetistics. The MyFleetistisc password is passed to the GPS platform but the GPS platform cannot pass back any changes for security. Therefore, only change your password in your MyFleetistics profile (click your name in the top left) or choose Forgo Password on the Fleetistics login page. (www.fleetistics.com/login)
• Ensure your password meets requirements for complexity. This may have been set by your Geotab account administrator under Administration>Services
  

Fleetistics ONE Passowrd is Not Working

• Submit a support ticket to have it reset
• Before logging in press Ctrl + F5 on your keyboad and delete your cookies

Reset Email Not Received

• If you do not receive the password reset email, check your email spam and junk folders and have your IT department white list fleetistics.com and myfleetistics.com.

There are several possible explanations.

1. The vehicle may have been parked outside of cellular coverage. When the vehicle re-enters cell coverage, it will update the trip data.
2. The device could be malfunctioning.
3. The device may have been unplugged at the last reported location.

Quick Troubleshooting.

1. The first thing to check is that the device has lights on the front when the vehicle is running. This is a very basic function check. If in down, power cycle the device by unplugging and plugging back into to restart the device.
2. Put the device in another vehicle with a know working OBD port and take it for a test drive. If it updates, there is an issue with the vehicle, not the device.

Contact support to open a support case and get help resolving the issue.

The Fleetistics mobile app is a fleet toolbox of various features and services. The app can be used by an individual or connected to a MyFleetistics account. Every customer has an App License key generated with the account is created in MyFleetistics. This code is put into the mobile app under the profile menu so the users app data can be correctly associated with a MyFleetistics account. The final step in connecting the app to the MyFleetistics is to go into Acccount>Services Administration and enable the service you want to use. You can enable one or all the services in the app depending on what is important.

Learn More Here

Mobile App Modules and Services

• Priority Events (similar to an SOS feature) - This is not connected to 911. The SOS button will send an email to the email entered by the user. If the service is enabled in MyFleetistics the SOS alert will appear on the MyFleetView map.
• Asset Link and Driver ID
• Accident Form and Report
• Routine event reporting
• Waypoints
• Weather radar
• Time and Attendance - track work, breaks and personal time and mileage as well as add pushpins for waypoinst or checkins. Used for people driving personal vehicles, foot patrols or a time card. If the services is enabled in MyFleetistics, timecard reports will be available to document the data collected in the app. When a user is on personal time, the mileage and time is calculated but the users GPS track is hidden from the employer. The personal mileage and time can be used for tax mileage deductions.
• Future Modules Planned - Installation tracker, AVIR, electronic forms, and more.

Critical Weather Layer Definitions

Weather Definitions    

Current Driver Weather    

Fog (current weather): Visibility restriction affecting the sight-distance of a driver.   

Heavy Fog (current weather): Urgent visibility restriction reducing visibility on the order of car lengths.    

Light Rain:  Rain that causes no visibility restriction, but makes the road slippery.     

Moderate Rain: Rain that causes some visibility restrictions.    

Heavy Rain (current weather): Rapid rate of rain that is capable of quickly covering the roadway.  Hydroplane possibilities increased.   

Snow: Light to Moderate snow that may cause isolated travel problems.               

Heavy Snow (current weather): Rapid rate of snowfall that quickly accumulates and reduces visibility. Travel problems likely in these areas.    

Ice:  Freezing rain, sleet, or mixed wintry precipitation, capable of producing isolated travel problems.    

Heavy Ice (current weather): Rapid rate of freezing rain, sleet, or mixed wintry precipitation, capable of quickly producing widespread travel problems and damage to trees and power lines.   

Road Conditions    

Snow (road condition): Snow in an amount covering (or just partially covering) secondary and less-travelled roads.   

Heavy Snow (road condition): Snow in an amount covering major roadways and interstates   

Patch Ice (road condition): Patchy ice, with bridges likely to experience issues and isolated patches of black ice.   

Ice (road condition):  Ice covered roads resulting in significant travel impacts.    

Flooded:  Ponding on roads in areas and possible flash flooding.    

Wet: Wet or damp roads, no ponding expected.   

Threats/Hazards   

Dangerous Wind:  Crosswinds are exceeding 35mph, the critical threshold for high profile vehicles.    

Hail: Based on Data’s patented storm tracking, highlights areas where Severe Hail is possible over the next fifteen minutes.    

Twisting Wind: Based on Data’s patented storm tracking, highlights areas where Tornados are possible over the next fifteen minutes. 

• Go to Accounts > Devices
• Locate the device and click Edit
• Make sure visibility is not set to hidden

The MyFleetView map refreshes after 10 seconds on first load and every 60 seconds after.

The Lite map refreshes on demand.

There are 3 aspects to a GPS system providing data on a map.
1. GPS device log rate.
2. GPS device transmit rate from the vehicle to the network.
3. Map refresh rate.

MyFleetView (MFV) is a value added service provided by Fleetistics that provides customers one-click access to the last reported location of their fleet. This link can be shared with customers and employees or iframed into a website. To setup one-click access from your phone email the MFV link under the Acconut>Services menu. Click the link in the email on your phone. Save the page to your phone desktop as a shortcut. No logging in or selecting a fleet from a list. You can also save this link to your browser on your computer for instant access.

Use the links below to see how MyFleetView works.

MyFleetView Pro - This is an option paid service which is being provided today for free. MyFleetView Pro offers you the ability to create custom links and control the vehicles included, and days and times active. Contact your account manager for more information.

	Using MyFleetView Administering MyFleetView Standard and Pro
	Adding MyFleetView to Phone Adding a phone or tablet desktop shortcut for 1-click access.
	MyFleetView

Fleetistics offers the Priority Notification Services (PNS) to increase the speed, reliability and method of notification for key data from various GPS platforms. It is intended for the highest priority situations that need to be outside the "noise" of the standard GPS platform user. PNS notifications are the type that require immediate attention. Notifications are only available when the the GPS device provides the corresponding data. The PNS is not intended for life saving situations. To discontinue the service simply turn it off in MyFleetistics>Account>Services Administration.  You can cancel the service at anytime at the beginning of the next billing period.

The PNS is also for fleets where multiple people need to know if an event takes place. If the fleet manager is normally responsible for fleet issues but the fleet manager is on vacation, out of cellular coverage or traveling, the PNS provides seamless alert communication without editing various alerts in the GPS platform(s). Potential people/positions to be notified include: fleet managers, risk and safety managers, legal and fleet maintenance supervisors.

The PNS will contact the users listed using up to 3 different alert based on the methods selected; email, SMS and digital voice. The system will step through each method selected and terminate upon a response from a recipient.

It is recommended that users listed test the system periodically, save the phone number from the PNS as a contact on cell phones so it shows on caller ID, give the PNS contact a unique ring tone and priority status. This helps ensure off-hour notifications are "put through" and not silenced by other phone settings.

This service has been moved to the Priority Notification Service - Click Here

The Fleetistics DriveTRAX® program was developed to fill in the gaps where GPS tracking could no provide insight. Activiies such as distracted driving, littering or sleeping in a company vehicle cannot be detected by a GPS tracker. The DriveTRAX® program is a very cost effective way to add another layer of oversight to your fleet. Essentially, every citizen becomes your eyes and ears in the field. If you are using a Fleetistics vehicle GPS tracking system, the data from the GPS tracker is used to help validate the complaint so all parties can be confident the report is accurate.

An example of these behaviors include distracted driving. Fleetistics takes this two steps farther by providing 5 minutes of drive time data and a map link of the time period prior the incident report. This enables employers to verify the location of the vehicle at the time of the incident. Managers can also listen to a recording of the caller's message and view the dashboard to determine how many, and what type of, incidents are being reported.

The DriveTRAX® report summarizes, in table format, the data collected from all reported incidents in your fleet. It is very similar to the data sent via email when the incident is reported.The DriveTRAX® decal must be associated with the vehicle in MyFleetistics for the system to associate the reports with the vehicle. If you do not have GPS tracking with Fleetistics, your data can be

Incidents:
Accident, speeding, distracted driving, wreckless driving, rude driver behavior, possible impaired driver, vehicle at a suspicious location, illegal parking or stopping, not listed

Date and Time:
Captured when the report is made. Reported in user time set in MyFleetitics user profile.

Map:
If the vehicle has a GPS vehicle tracking device, you can view the vehicles track data for a 5 minute period prior to the reported incident. If the vehicle was not moving for more than 5 minutes, the vehicle will appear without track data. If there is not a Fleetistics GPS tracker in the vehicle, the link will not display any data. The track data confirms the vehicle was at the reported incident location.

Voicemail:
If the caller left a voicemail you can listen to the caller explain the situation. The voicemail is very telling and adds credibility to the report. A voicemail can be up to 30 seconds long. If a voicemail was not left, the link will be dead.

Status:
The status is set by you. Use the status to view the incidents and track which have been investigated and which are considered resolved by your organization.

Step 2. Associate Decal with Vehicle

Viewing DriveTRAX Data

1. Click the Details icon in the left column.

2. Change the status of the report from the Details window

DriveTRAX Explanation
How the DriveTRAX program works.

Monday - Friday, 8:30 am to 5:30 pm, EST. Emergencies, such as accidents, will be responded to after hours. Please review the content in the Help Center in your MyFleetistics account, Fleetistics.TV or this FAQ manager for more possible solutions during off hours.

A vehicle not reporting on the map or a user not able to login will be handled the next business day. We cannot remotely make a device report and we have a password reset function to automate resolving login issues.

Intrinsic safety (IS) is a protection technique for safe operation of electrical equipment in hazardous areas by limiting the energy available for ignition. In signal and control circuits that can operate with low currents and voltages, the intrinsic safety approach simplifies circuits and reduces installation cost over other protection methods. Areas with dangerous concentrations of flammable gases or dust are found in applications such as petrochemical refineries and mines. As a discipline, it is an application of inherent safety in instrumentation. High-power circuits such as electric motors or lighting cannot use intrinsic safety methods for protection.

Intrinsic Safety Learn more

In the US, the Moss Magnuson Warranty Act of 1975 specifically prohibits manufacturers from voiding the warranty due to aftermarket additions to the vehicle. Furthermore, Geotab has spent considerable time ensuring that our products cannot cause harm to the vehicle.

No, the devices will go into sleep mode when the vehicle is turned off and will only draw about 5 mA of current. A typical car battery has a capacity of 50 Ah, which means it will take over a year before the device can come close to depleting the battery.

Data Processing Service (IoT) API  

The Fleetistics DPS-API provides unified access to the information reported by any device registered in your account. Devices of all manufacturers, type, configuration and device data provider are supported. For all device types, the system provides a list of registered devices.

Information provided includes:

• A list of each device’s current state, manufacturer/type/configuration, current location, speed, battery status, last update date.
• A list of raw device parameter values for specific devices by date/time. The list of parameters is unified and independent from device types. However, each device type or configuration can send its own set of parameters.
• A list of raw device messages for specific devices by any date/time period. Messages contain only updated device parameters and location. Messages always provide a unified type reliant on the device message type. If device sends events such as start/stop motion or ignition on/off, the message will contain a unified event type. Messages can be empty if no change in parameter value or status.

Required skills: The ability to form and send an HTTP request with header and handling for JSON responses.

To get started: In MyFleetistics, go to Account > Services > Administer Services. Enable the Data Processing Service (IoT) API option. Then open Service Settings by clicking the icon to obtain an API Key. The Service Settings page contains an API Explorer hat includes a list of all requests and the ability to test each request on your real data, then copy the request URL.

Request details:

1. To get data send an HTTP Get request with parameters that include a query string and data will be returned as JSON response.
   
   Request must include header "Authorization” with value "Bearer " + APIToken.Z
   
   You can copy "Authorization” header on from the Data Processing Service (IoT) settings by clicking the
   Copy Auth Header button.
   
   
2. Requests can be concurrent.
   
   
3. Max number of concurrent requests and max number of requests per hour are limited by the service level selected. If requests exceed the limit - HTTP code 429 Too Many Requests is returned.
   
   
4. The maximum number of returned messages by single request (GetDeviceMessagesBy*/GetMessagesBy*) is limited by 1000 messages. If a request returns more than 1000 messages - only first 1000 messages are returned and the flag "isLimited" is true. Returned messages are ordered by Message.Id so you can build new request starting from the last returned Message.Id
   
   
5. The base API url is: https://my4.myfleetistics.com/api/dps/
6. A call always returns a JSON object containing the fields "result" and "payload". The response result=0 indicates success. The response result !=0 indicates an error. An error returns the field "message" with details.
   
   
7. Payloads can be a JSON object or array depending on the request  

Examples of calls for use with GPS devices:

1. Show devices on map or show list of devices statuses:
   
   - Request the list of devices once (/GetDevices) – to show device name and type. ·       
   - Periodically request the list of device statuses (/GetDeviceCurrentStatuses)
   
   Device current status contains latest device location, speed and bearing to show position on a map. It also includes LastCommunicationDate, IsBatteryOk, IsIgnitionOn, IsInMotion for device state.
   
   
2. Show device state for a date/time
   
   · Request the list of devices (/GetDevices) – to show the device selector
   · Ask user for DateTime
   · Request a list of parameters (/GetParameterTypes) - to display parameter names.
   · Request initial device state (device parameters values) on “DateTime” (/GetDeviceStateUpToDate)
   
   Showing device location and all parameter values can be accomplished with DateTime
   
   
3. Show device activity:
   
   · Request device list (/GetDevices) – to show the device selector.
   · Ask user for fromDate and toDate.
   · Request list of parameters (/GetParameterTypes)- to show parameter names.
   · Request list of event types (/GetEventTypes)- to show eventTypes names.
   · Request initial device state (device parameters values) using “fromDate” (/GetDeviceStateUpToDate)
   
   All device parameters values at the beginning by entering user period.
   
   - To request device messages for period fromDate to toDate (/GetDeviceMessagesByDate). If the quantity of messages is      more than 1000, the response will include isLimited = true. In this case – send again (/GetDeviceMessagesByDate)with the same period fromDate to toDate adding parameter fromMessageId as maxMessageId+1 from latest response to build afull list of messages.
   
   Device messages contain only device parameters location changed by this message. Also some devices send events like start/stop motion or ignition on/off – in this case the message will contain the event. Some messages can be empty if nothing changed. Empty messages should be ignored and show only non-empty messages. This allows the user to see device activity during the period.
   
   
4. Show device messages
   
   · Request list of devices (/GetDevices) – to show the device selector.
   · Ask user for fromDate and toDate.
   · Request the list of parameters (/GetParameterTypes)- to show name of parameters.
   · Request the list of message types (/GetMessageTypes) - to show name of messageTypes
   · Request the list of event types (/GetEventTypes)- to show name of eventTypes
   · Request device messages for period fromDate to toDate (/GetDeviceMessagesByDate).
   
   If the quantity of messages is more than 1000, the response will include isLimited = true. In this case – send (/GetDeviceMessagesByDate) again with the same period fromDate to toDate including the additional parameter fromMessageId as maxMessageId+1 from the latest response to return the full list of messages.
   
   When the list of messages is called, the message type can be a periodical update message or system message. If message has event – the event name is included. Empty messages can be shown or ignored. Some empty messages can be system or contain only an event.
   
   If full device state for each message is needed, load (/GetDeviceStateUpToDate) at the beginning of period, then check that messages are sorted by messageId in the list. In series replace the values in full device state with the same parameters. Location is provided in device state for each message.  
   
   
5. Datafeed service for continuously syncing all data to an internal database.
   
   ·        Request the list of devices once, parameters, message types, event types (/GetDevices, /GetParameterTypes, /GetMessageTypes, /GetEventTypes) to save them into your database.
   ·        Periodically, for example, once a day, request the lists again to check using “LatestUpdateDate” to determine is an entity changed, updadted, or add it to your database.
   ·        Request the initial device state (device parameters values)once for the start date of a datafeed (/GetDevicesStateUpToDate)request to save to a database. This request return states of all devices. The datafeed process can be restarted anytime from the same or a different date
   ·        Request all device messages once for all devices for a DataFeed start date without specifying a to date (/GetMessagesByDate). If the quantity of messages is more than 1000, the response will include isLimited = true. In this case send (/GetMessagesByDate)again with the same fromDate but include parameters fromMessageId as maxMessageId+1 from latest response. This builds the full list of messages. When all messages are returned, save the latest maxMessageId to a database.
   ·        To periodically calculate period how frequently devices are reporting, how frequently data is to be updated, and what are the requests limitations on your account, request new messages using (/GetMessagesById) with latest messageId saved to a database.If the quantity of messages is more than 1000 use the same procedure as the initial load but with (/GetMessagesById). Once all messages are received, save the latest messageId to a database.  
   
   To implement a datafeed of device messages, request a list of available devices again.
   
   Then, periodically sync the list of devices with returns with usage device.Id as unique ID.
   
   Device messages can be requested per device or for all devices. Message.Id can be used as serial.
   
   It is integer incrementing messages unique key that is never changed.
   
   Message.DCSDate is UTC time when server received message from device.
   
   It never returns lower number than those already received.
   
   Message.Date is generated by device. If a device sends delayed messages from its cache, you can receive an older date than those already delivered.
   
   
6. Base API url is: “https://my4.myfleetistics.com/dcsapi/”
   
   
7. A JSON object with fields "result" and "payload" are always returned. Result=0 indicates success, result !=0 indicates an error. In case off error a "message" with details is returned. Payload can be a JSON object or array depending on the request.
   
   
8. Device messages contains two dates:
   
   -   Date - is the DateTime of message sent by device.
   
   -   ServerDate - is the date the server received the message.
   
   -   Both dates are in UTC. Device messages can be stored in device memory and sent at a later time.  

DeviceCurrentStatus contains deviceID - to show device name or type, use the result of /GetDevices request.

GetDeviceCurrentStatuses does not return current status for a device that has never reported.

GetDeviceCurrentStatuses returns one current status per device.

GetDeviceCurrentStatuses always returns a list of all current statuses. It does not depend on reported device since your previous

GetDeviceCurrentStatuses request or no.    

API Requests:

1. To return a list of Parameter, Message, or Event types use (GetParameterTypes, GetMessageTypes, GetEventTypes). Example: https://my4.myfleetistics.com/dcsapi/GetParameterTypes returns:
"Id" - integer, ID of Parameter, Message, Event, used in the rest of requests
"Name" - string, name of Parameter, Message, Event
"LatestUpdateDate" - integer, Unix time, UTC/GMT, time of latest entity parameter update
Parameters, Message types, Event types include device manufacturer, type, configuration independence.

Sample:

{               

"result":0,

"payload":{ “messageTypes”: [      

                        {                                            

"Id":4,                                             

"Name":"Update",                                             

"LatestUpdateDate":1564156521                              

},{                                             

"Id":17,                                             

"Name":"System",                                             

"LatestUpdateDate":1566797645                              

}               

]

}

}   

2. List of devices, /GetDevices returns:

"Id" - integer, ID of device will be used in the rest of requests
"TypeName" - string, name of device type
"SerialNumber" - string, unique ID of device, depending on the device type, this can be the device IMEI, ESN, UID, Serial number.
"Name" - string, name of device in MyFleetistics
"ActivatedDate", integer, Unix time, (number of seconds that have elapsed since January 1, 1970 (midnight UTC/GMT)), UTC/GMT. The time the device started reporting for into this account
"DeactivatedDate" - integer, Unix time, UTC/GMT, time when the device stopped reporting for into this account, optional, can be null for active device
"LatestUpdateDate" - integer, Unix time, UTC/GMT, time of latest device parameter update
"LatestDeviceMessageDate" - integer, Unix time, UTC/GMT, time of latest device message, optional, is null for non-reporting device

Example:

{               

"result":0,               

"payload":{

“devices”: [  

{                                             

"Id":4,                                             

"TypeName":"FLT-TLP",                                             

"SerialNumber":"866425035335092",                                             

"Name":"TopFly 0x26 Test",                                             

"ActivatedDate":504921600,                                             

"DeactivatedDate":1429825293,                                             

"LatestUpdateDate":1564156521,

"LatestDeviceMessageDate ":1564156521                              

},{                                             

"Id":17,                                             

"TypeName":"FLT-TLP",                                             

"SerialNumber":"866425039637030",                                             

"Name":"test DCS export",                                             

"ActivatedDate":1566297674,                                             

"LatestUpdateDate":1566797645,

"LatestDeviceMessageDate ":1564156521                              

}              

]

}

}

3. List of devices current statuses, /GetDevicesCurrentStatus this request returns statuses of reporting devices Device type independent response. LastCommunicationDate, IsBatteryOk, IsIgnitionOn, IsInMotion "LastCommunicationDate" - integer, Unix time, UTC/GMT, time of latest device message of any type - position message, alert, heartbeat or system message "IsBatteryOk" - boolean, multi-sourced battery OK status, obtained from different parameters returned by different types of devices. Includes internal/external/backup battery state. "IsIgnitionOn" - boolean, current state of ignition if device supports it. Absent if device does not send ignition state "IgnitionChangeDate" - integer, Unix time, UTC/GMT, time when ignition state last changed "IsInMotion" - boolean, multi-sourced status obtained from non-zero speed and in motion state returned by some devices "InMotionChangeDate" - integer, Unix time, UTC/GMT, time when motion state last changed "PositionDate" - integer, Unix time, UTC/GMT, time when latest valid position was received from device "Latitude", "Longitude" - double, latest valid GPS position "Bearing" - float, in degrees, latest vehicle direction received from device "Speed" - float, in km/h, latest device speed received from device. If the device sends both OBD and GPS speed - OBD speed will be used   Sample: {                "result":0,                "payload": { “devicesCurrentStatus“: [                               {                                              "DeviceId":4,                                              "LastCommunicationDate":1564156487,                                              "IsBatteryOk":true,                                              "IsIgnitionOn":true,                                              "IgnitionChangeDate":1564145612,                                              "IsInMotion":false,                                              "InMotionChangeDate":1563403548,                                              "PositionDate":1564145926,                                              "Latitude":28.187429428100586,                                              "Longitude":-82.374893188476562,                                              "Bearing":291,                                              "Speed":0.0                               },{                                              "DeviceId":17,                                              "LastCommunicationDate":1566320213,                                              "IsIgnitionOn":false,                                              "IgnitionChangeDate":1566320213,                                              "IsInMotion":false,                                              "InMotionChangeDate":1566320213,                                              "PositionDate":1566320213,                                              "Latitude":28.19282,                                              "Longitude":-82.37767,                                              "Bearing":143,                                              "Speed":0.0                               }                ] } }  

4. Device messages Can be used for a single device - /GetDeviceMessagesByDate, /GetDeviceMessagesByServerDate, /GetDeviceMessagesById with required parameter- deviceId or for all devices - /GetMessagesByDate, /GetMessagesByServerDate, /GetMessagesById   Device message contain two dates: -   Date - is the DateTime of message sent by device -   ServerDate date time - is the date the server received the message. Both dates are UTC. A message can be stored in a devices memory and sent later when the device has a network connection. So message.ServerDate can be later than message.Date /GetDeviceMessagesByDate, /GetMessagesByDate have optional parameter - fromDate, toDate - integer, Unix time, UTC/GMT, message Date /GetDeviceMessagesByServerDate, /GetMessagesByServerDate have optional parameter - fromServerDate, toServerDate - integer, Unix time, UTC/GMT, message ServerDate /GetDeviceMessagesByDate, /GetDeviceMessagesByServerDate, /GetMessagesByDate, /GetMessagesByServerDate have optional parameter – fromMessageId – integer, min messageId to get next pack of messages if a previous request response was limited due to quantity of messages /GetDeviceMessagesById, /GetMessagesById have optional parameter - fromId, toId - integer, message Id   The set of returned parameters depends on device type/configuration. Parameter value, type and formatting are device independent. "Id" - integer, unique ID of message. "DeviceId" - integer , unique ID of device "Date" - integer, Unix time, UTC/GMT, device generated date/time of message "ServerDate" - integer, Unix time, UTC/GMT, date/time when server received message "MessageTypeId", integer, unique ID of message type. Can be decoded to name of message type by the list returned by /GetMessageTypes "EventTypeId", integer, unique ID of event type. Can be decoded to name of event type by the list returned by /GetEventTypes An optional parameter is sent when a device sends an event like ignition on, vibration, accident, OBD errors: "Parameters" – returns a list of parameters changed by message. Can be omitted if message does not change any parameters                Parameter structure: "TypeId", integer, unique ID of parameter type. Can be decoded to name of parameter type and unit by the list returned by /GetParameterTypes                               "Value" - string representation of value "Position" - GPS position if position changed. Can be omitted if message does not change the position                Position structure:                               - "Latitude", "Longitude" - double, GPS position                               - "Altitude" - float, altitude, m "Quality" - integer, can be GPSFine = 1, GPSFair = 2, GPSPoor = 3, LBS = 4, Interpolated = 5, GPSBad = 13 Sample: {                "result":0,                "payload":{                               messages: [                                              {                                                             "Id": 12,                                                             "DeviceId":11,                                                             "Date":1561100731,                                                             "ServerDate":1561115135,                                                             "MessageTypeId":1,                                                             "EventTypeId": 1              ,                                                             "Parameters":[                                                                            {                                                                                           "TypeId": 1,                                                                                           "Value":93.0                                                                            },{                                                                                           "TypeId":2,                                                                                           "Value":0                                                                            },{                                                                                           "TypeId":3,                                                                                           "Value":4153344.0                                                                            },{                                                                                           "TypeId":4,                                                                                           "Value":1                                                                            }                                                             ],                                                             "Position":{                                                                                           "Latitude":29.026450994783758,                                                                                           "Longitude":-98.360950751417988,                                                                                           "Altitude":0.0,                                                                                           "Quality":0                                                             }                                              }                               ],                               maxMessageId: 12,                               isLimited: false                } }

5. Device state to a date Can be requested for single device - /GetDeviceStateUpToDate with required parameter- deviceId or for all devices using /GetDevicesStateUpToDate both requests have required parameter - upToDate - integer, Unix time, UTC/GMT – message Date. Device state is built for latest message Date < upToDate Single device request has payload with single status object and all devices requested will have array of status objects. Status object will have: “DeviceId” – integer – Id of Device "MaxMessageId" - integer, max messageId with Date < upToDate "Parameters" – this section has the same structure as message parameters but contains all possible device parameters "Position" - has the same structure as message Position. Parameters and Position sections can be omitted if device did not send position or parameters up to upToDate Samples: For single device                {                               "result":0,                               "payload":{                                              “state”: {                                                             "DeviceId": 23, "MaxMessageId": 23,                                                             "Parameters":[                                                                            {                                                                                           "TypeId": 1,                                                                                           "Value":93.0                                                                            },{                                                                                           "TypeId":2,                                                                                           "Value":0                                                                            },{                                                                                           "TypeId":3,                                                                                           "Value":4153344.0                                                                            },{                                                                                           "TypeId":4,                                                                                           "Value":1                                                                            }                                                             ],                                                             "Position":{                                                                                           "Latitude":29.026450994783758,                                                                                           "Longitude":-98.360950751417988,                                                                                           "Altitude":0.0,                                                                                           "Quality":0                                                             }                                              }                               }                } For all devices {                               "result":0,                               "payload": {                                              “states”: [                                                             {                                                             "DeviceId": 23, "MaxMessageId": 23,                                                             "Parameters":[                                                                            {                                                                                           "TypeId": 1,                                                                                           "Value": 93.0                                                                            },{                                                                                           "TypeId": 2,                                                                                           "Value": 0                                                                            },{                                                                                           "TypeId":3,                                                                                           "Value": 4153344.0                                                                            },{                                                                                           "TypeId":4,                                                                                           "Value":1                                                                            }                                                             ],                                                             "Position":{                                                                                           "Latitude":29.026450994783758,                                                                                           "Longitude":-98.360950751417988,                                                                                           "Altitude":0.0,                                                                                           "Quality":0                                                             }                                                             }, {                                                             "DeviceId": 24, "MaxMessageId": 26,                                                             "Parameters":[                                                                            {                                                                                           "TypeId": 1,                                                                                           "Value": 93.0                                                                            },{                                                                                           "TypeId": 2,                                                                                           "Value": 0                                                                            },{                                                                                           "TypeId":3,                                                                                           "Value": 4153344.0                                                                            },{                                                                                           "TypeId":4,                                                                                           "Value":1                                                                            }                                                             ],                                                             "Position":{                                                                                           "Latitude":29.026450994783758,                                                                                           "Longitude":-98.360950751417988,                                                                                           "Altitude":0.0,                                                                                           "Quality":0                                                             }                                                             }                                              ]                               }                }                                             

6.      Refresh token API token expires after 1 year. Before a token expires – new tokens can be generated for next 1 year period by request /RefreshToken Old token will not valid Sample                {                               "result":0,                               "payload": {                                              “newToken”: “zzxxcc…” } }

The Fleetistics API service takes data from various GPS devices and normalizes it. The normalized data is then shared via API. This can be done for GPS devices sold and serviced by Fleetistics as well as any IoT devices from other providers. There are several advantages to this approach.

• Data from multiple GPS/IoT platforms can be assembled into one user interface. This is especially helpful when transitioning from one GPS platform to another. It can also provide a cost advantage by getting a lower rate for specific applications while maintaining the primary system.
• As devices and protocols are added, the API from Fleetistics will change less often. Normally the API is specific to a protocol and there can be multiple protocols with one manufacturer. Fleetistics will learn the protocol, do the integration and normalize the data so it is available through the APIs.
• A customer that only has a need for the data does not have to buy a GPS platform to get the data. Fleetistics can decode data directly from an IoT device, process it and delivery it to a customer which is only interesetd in the data which they will put in their database. Decoding and processing data requires a lot expertise and infrastructure many companies are not prepared to fund or develop due to cost and skills needed. For example a rail company may track their rail cars using an existing platform but wants to add GPS tracking to the platform. They need GPS data but they do not need an interface. Fleetistics can process and deliver the data for a fraction of the cost of bundling the GPS data with a platform or UI. Fleetistics can also provide a data plan to go with GPS units if needed.

The Fleetistics DPS-API provides unified access to the information reported by any device registered in your account. Devices of all manufacturers, type, configuration and device data provider are supported.

For all device types, the system provides a list of registered devices.

Information provided includes:

• A list of each device’s current state, manufacturer/type/configuration, current location, speed, battery status, last update date.
• A list of raw device parameter values for specific devices by date/time. The list of parameters is unified and independent from device types. However, each device type or configuration can send its own set of parameters.
• A list of raw device messages for specific devices by any date/time period. Messages contain only updated device parameters and location. Messages always provide a unified type reliant on the device message type. If device sends events such as start/stop motion or ignition on/off, the message will contain a unified event type. Messages can be empty if no change in parameter value or status.

Required skills: The ability to form and send an HTTP request with header and handling for JSON responses.

To get started: In MyFleetistics, go to Account > Services > Administer Services. Enable the Data Processing Service (IoT) API option. Then open Service Settings by clicking the icon to obtain an API Key. The Service Settings page contains an API Explorer hat includes a list of all requests and the ability to test each request on your real data, then copy the request URL.

Request details:

• To get data send an HTTP Get request with parameters that include a query string and data will be returned as JSON response.

Request must include header "Authorization” with value "Bearer " + APIToken.

You can copy "Authorization” header on from the Data Processing Service (IoT) settings by clicking the Copy Auth Header button.

• Requests can be concurrent.
• Max number of concurrent requests and max number of requests per hour are limited by the service level selected.

If requests exceed the limit - HTTP code 429 Too Many Requests is returned.

• The maximum number of returned messages by single request (GetDeviceMessagesBy*/GetMessagesBy*) is limited by 1000 messages.

If a request returns more than 1000 messages - only first 1000 messages are returned and the flag "isLimited" is true.

Returned messages are ordered by Message.Id so you can build new request starting from the last returned Message.Id

• The base API url is: https://my4.myfleetistics.com/api/dps/
• A call always returns a JSON object containing the fields "result" and "payload". The response result=0 indicates success. The response result !=0 indicates an error. An error returns the field "message" with details.
• Payloads can be a JSON object or array depending on the request

Examples of calls for use with GPS devices:

• Show devices on map or show list of devices statuses:
  • Request the list of devices once (/GetDevices) – to show device name and type.
  • Periodically request the list of device statuses (/GetDeviceCurrentStatuses)

Device current status contains latest device location, speed and bearing to show position on a map.
It also includes LastCommunicationDate, IsBatteryOk, IsIgnitionOn, IsInMotion for device state.

• Show device state for a date/time
  • Request the list of devices (/GetDevices) – to show the device selector
  • Ask user for DateTime
  • Request a list of parameters (/GetParameterTypes)- to display parameter names.
  • Request initial device state (device parameters values) on “DateTime” (/GetDeviceStateUpToDate)

Showing device location and all parameter values can be accomplished with DateTime

• Show device activity:
  • Request device list (/GetDevices) – to show the device selector.
  • Ask user for fromDate and toDate.
  • Request list of parameters (/GetParameterTypes)- to show parameter names.
  • Request list of event types (/GetEventTypes)- to show eventTypes names.
  • Request initial device state (device parameters values) using “fromDate” (/GetDeviceStateUpToDate)

All device parameters values at the beginning by entering user period.

• To request device messages for period fromDate to toDate (/GetDeviceMessagesByDate). If the quantity of messages is more than 1000, the response will include isLimited = true. In this case – send again (/GetDeviceMessagesByDate)with the same period fromDate to toDate adding parameter fromMessageId as maxMessageId+1 from latest response to build afull list of messages.

Device messages contain only device parameters location changed by this message. Also some devices send events like start/stop motion or ignition on/off – in this case the message will contain the event. Some messages can be empty if nothing changed. Empty messages should be ignored and show only non-empty messages. This allows the user to see device activity during the period.

• Show device messages
  • Request list of devices (/GetDevices) – to show the device selector.
  • Ask user for fromDate and toDate.
  • Request the list of parameters (/GetParameterTypes)- to show name of parameters.
  • Request the list of message types (/GetMessageTypes) - to show name of messageTypes
  • Request the list of event types (/GetEventTypes)- to show name of eventTypes
  • Request device messages for period fromDate to toDate (/GetDeviceMessagesByDate).
    If the quantity of messages is more than 1000, the response will include isLimited = true. In this case – send (/GetDeviceMessagesByDate) again with the same period fromDate to toDate including the additional parameter fromMessageId as maxMessageId+1 from the latest response to return the full list of messages.

When the list of messages is called, the message type can be a periodical update message or system message. If message has event – the event name is included. Empty messages can be shown or ignored. Some empty messages can be system or contain only an event.

If full device state for each message is needed, load (/GetDeviceStateUpToDate) at the beginning of period, then check that messages are sorted by messageId in the list. In series replace the values in full device state with the same parameters. Location is provided in device state for each message.

• Datafeed service for continuously syncing all data to an internal database.
  • Request the list of devices once, parameters, message types, event types (/GetDevices, /GetParameterTypes, /GetMessageTypes, /GetEventTypes) to save them into your database.
  • Periodically, for example, once a day, request the lists again to check using “LatestUpdateDate” to determine is an entity changed, updadted, or add it to your database.
  • Request the initial device state (device parameters values)once for the start date of a datafeed (/GetDevicesStateUpToDate)request to save to a database. This request return states of all devices. The datafeed process can be restarted anytime from the same or a different date
  • Request all device messages once for all devices for a DataFeed start date without specifying a to date (/GetMessagesByDate). If the quantity of messages is more than 1000, the response will include isLimited = true. In this case send (/GetMessagesByDate)again with the same fromDate but include parameters fromMessageId as maxMessageId+1 from latest response. This builds the full list of messages. When all messages are returned, save the latest maxMessageId to a database.
  • To periodically calculate period how frequently devices are reporting, how frequently data is to be updated, and what are the requests limitations on your account,
    request new messages using (/GetMessagesById) with latest messageId saved to a database.If the quantity of messages is more than 1000 use the same procedure as the initial load but with (/GetMessagesById). Once all messages are received, save the latest messageId to a database.

To implement a datafeed of device messages, request a list of available devices again.

Then, periodically sync the list of devices with returns with usage device.Id as unique ID.

Device messages can be requested per device or for all devices. Message.Id can be used as serial.

It is integer incrementing messages unique key that is never changed.

Message.DCSDate is UTC time when server received message from device.

It never returns lower number than those already received.

Message.Date is generated by device. If a device sends delayed messages from its cache, you can receive an older date than those already delivered.

• Base API url is: “https://my4.myfleetistics.com/dcsapi/”
  
  
• A JSON object with fields "result" and "payload" are always returned. Result=0 indicates success, result !=0 indicates an error. In case off error a "message" with details is returned.

Payload can be a JSON object or array depending on the request.

• Device messages contains two dates:
  • Date - is the DateTime of message sent by device.
  • ServerDate - is the date the server received the message.
  • Both dates are in UTC. Device messages can be stored in device memory and sent at a later time.

DeviceCurrentStatus contains deviceID - to show device name or type, use the result of /GetDevices request.

GetDeviceCurrentStatuses does not return current status for a device that has never reported.

GetDeviceCurrentStatuses returns one current status per device.

GetDeviceCurrentStatuses always returns a list of all current statuses. It does not depend on reported device since your previous GetDeviceCurrentStatuses request or no.

API Requests:

1. To return a list of Parameter, Message, or Event types use (GetParameterTypes, GetMessageTypes, GetEventTypes). Example: https://my4.myfleetistics.com/dcsapi/GetParameterTypes returns:

"Id" - integer, ID of Parameter, Message, Event, used in the rest of requests

"Name" - string, name of Parameter, Message, Event

"LatestUpdateDate" - integer, Unix time, UTC/GMT, time of latest entity parameter update

Parameters, Message types, Event types include device manufacturer, type, configuration independence.

Sample:

{
               "result":0,
               "payload":{
“messageTypes”: [
                              {
                                             "Id":4,
                                             "Name":"Update",
                                             "LatestUpdateDate":1564156521
                              },{
                                             "Id":17,
                                             "Name":"System",
                                             "LatestUpdateDate":1566797645
                              }
               ]
}
}

2. List of devices, /GetDevices returns:

"Id" - integer, ID of device will be used in the rest of requests

"TypeName" - string, name of device type

"SerialNumber" - string, unique ID of device, depending on the device type, this can be the device IMEI, ESN, UID, Serial number.

"Name" - string, name of device in MyFleetistics

"ActivatedDate", integer, Unix time, (number of seconds that have elapsed since January 1, 1970 (midnight UTC/GMT)), UTC/GMT. The time the device started reporting for into this account

"DeactivatedDate" - integer, Unix time, UTC/GMT, time when the device stopped reporting for into this account, optional, can be null for active device

"LatestUpdateDate" - integer, Unix time, UTC/GMT, time of latest device parameter update

"LatestDeviceMessageDate" - integer, Unix time, UTC/GMT, time of latest device message, optional, is null for non-reporting device

Example:

{
               "result":0,
               "payload":{
“devices”: [
                              {
                                             "Id":4,
                                             "TypeName":"FLT-TLP",
                                             "SerialNumber":"866425035335092",
                                             "Name":"TopFly 0x26 Test",
                                             "ActivatedDate":504921600,
                                             "DeactivatedDate":1429825293,
                                             "LatestUpdateDate":1564156521,
"LatestDeviceMessageDate ":1564156521
                              },{
                                             "Id":17,
                                             "TypeName":"FLT-TLP",
                                             "SerialNumber":"866425039637030",
                                             "Name":"test DCS export",
                                             "ActivatedDate":1566297674,
                                             "LatestUpdateDate":1566797645,
"LatestDeviceMessageDate ":1564156521
                              }
               ]
}
}

3. List of devices current statuses, /GetDevicesCurrentStatus this request returns statuses of reporting devices

Device type independent response.

LastCommunicationDate, IsBatteryOk, IsIgnitionOn, IsInMotion

"LastCommunicationDate" - integer, Unix time, UTC/GMT, time of latest device message of any type - position message, alert, heartbeat or system message

"IsBatteryOk" - boolean, multi-sourced battery OK status, obtained from different parameters returned by different types of devices. Includes internal/external/backup battery state.

"IsIgnitionOn" - boolean, current state of ignition if device supports it. Absent if device does not send ignition state

"IgnitionChangeDate" - integer, Unix time, UTC/GMT, time when ignition state last changed

"IsInMotion" - boolean, multi-sourced status obtained from non-zero speed and in motion state returned by some devices

"InMotionChangeDate" - integer, Unix time, UTC/GMT, time when motion state last changed

"PositionDate" - integer, Unix time, UTC/GMT, time when latest valid position was received from device

"Latitude", "Longitude" - double, latest valid GPS position

"Bearing" - float, in degrees, latest vehicle direction received from device

"Speed" - float, in km/h, latest device speed received from device. If the device sends both OBD and GPS speed - OBD speed will be used

Sample:

{
               "result":0,
               "payload": {
“devicesCurrentStatus“: [
                              {
                                             "DeviceId":4,
                                             "LastCommunicationDate":1564156487,
                                             "IsBatteryOk":true,
                                             "IsIgnitionOn":true,
                                             "IgnitionChangeDate":1564145612,
                                             "IsInMotion":false,
                                             "InMotionChangeDate":1563403548,
                                             "PositionDate":1564145926,
                                             "Latitude":28.187429428100586,
                                             "Longitude":-82.374893188476562,
                                             "Bearing":291,
                                             "Speed":0.0
                              },{
                                             "DeviceId":17,
                                             "LastCommunicationDate":1566320213,
                                             "IsIgnitionOn":false,
                                             "IgnitionChangeDate":1566320213,
                                             "IsInMotion":false,
                                             "InMotionChangeDate":1566320213,
                                             "PositionDate":1566320213,
                                             "Latitude":28.19282,
                                             "Longitude":-82.37767,
                                             "Bearing":143,
                                             "Speed":0.0
                              }
               ]
}
}

4. Device messages

Can be used for a single device - /GetDeviceMessagesByDate, /GetDeviceMessagesByServerDate, /GetDeviceMessagesById with required parameter- deviceId

or for all devices - /GetMessagesByDate, /GetMessagesByServerDate, /GetMessagesById

Device message contain two dates:

- Date - is the DateTime of message sent by device

- ServerDate date time - is the date the server received the message.

Both dates are UTC. A message can be stored in a devices memory and sent later when the device has a network connection. So message.ServerDate can be later than message.Date

/GetDeviceMessagesByDate, /GetMessagesByDate have optional parameter - fromDate, toDate - integer, Unix time, UTC/GMT, message Date

/GetDeviceMessagesByServerDate, /GetMessagesByServerDate have optional parameter - fromServerDate, toServerDate - integer, Unix time, UTC/GMT, message ServerDate

/GetDeviceMessagesByDate, /GetDeviceMessagesByServerDate, /GetMessagesByDate, /GetMessagesByServerDate have optional parameter – fromMessageId – integer, min messageId to get next pack of messages if a previous request response was limited due to quantity of messages

/GetDeviceMessagesById, /GetMessagesById have optional parameter - fromId, toId - integer, message Id

The set of returned parameters depends on device type/configuration.

Parameter value, type and formatting are device independent.

"Id" - integer, unique ID of message.

"DeviceId" - integer , unique ID of device

"Date" - integer, Unix time, UTC/GMT, device generated date/time of message

"ServerDate" - integer, Unix time, UTC/GMT, date/time when server received message

"MessageTypeId", integer, unique ID of message type. Can be decoded to name of message type by the list returned by /GetMessageTypes

"EventTypeId", integer, unique ID of event type. Can be decoded to name of event type by the list returned by /GetEventTypes

An optional parameter is sent when a device sends an event like ignition on, vibration, accident, OBD errors:

"Parameters" – returns a list of parameters changed by message. Can be omitted if message does not change any parameters

Parameter structure:

"TypeId", integer, unique ID of parameter type. Can be decoded to name of parameter type and unit by the list returned by /GetParameterTypes

"Value" - string representation of value

"Position" - GPS position if position changed. Can be omitted if message does not change the position

Position structure:

- "Latitude", "Longitude" - double, GPS position

- "Altitude" - float, altitude, m

"Quality" - integer, can be GPSFine = 1, GPSFair = 2, GPSPoor = 3, LBS = 4, Interpolated = 5, GPSBad = 13

Sample:

{
               "result":0,
               "payload":{
                              messages: [
                                             {
                                                            "Id": 12,
                                                            "DeviceId":11,
                                                            "Date":1561100731,
                                                            "ServerDate":1561115135,
                                                            "MessageTypeId":1,
                                                            "EventTypeId": 1              ,
                                                            "Parameters":[
                                                                           {
                                                                                          "TypeId": 1,
                                                                                          "Value":93.0
                                                                           },{
                                                                                          "TypeId":2,
                                                                                          "Value":0
                                                                           },{
                                                                                          "TypeId":3,
                                                                                          "Value":4153344.0
                                                                           },{
                                                                                          "TypeId":4,
                                                                                          "Value":1
                                                                           }
                                                            ],
                                                            "Position":{
                                                                                          "Latitude":29.026450994783758,
                                                                                          "Longitude":-98.360950751417988,
                                                                                          "Altitude":0.0,
                                                                                          "Quality":0
                                                            }
                                             }
                              ],
                              maxMessageId: 12,
                              isLimited: false
               }
}

5. Device state to a date

Can be requested for single device - /GetDeviceStateUpToDate with required parameter- deviceId

or for all devices using /GetDevicesStateUpToDate both requests have required parameter - upToDate - integer, Unix time, UTC/GMT – message Date. Device state is built for latest message Date < upToDate

Single device request has payload with single status object and all devices requested will have array of status objects.

Status object will have:

“DeviceId” – integer – Id of Device

"MaxMessageId" - integer, max messageId with Date < upToDate

"Parameters" – this section has the same structure as message parameters but contains all possible device parameters

"Position" - has the same structure as message Position.

Parameters and Position sections can be omitted if device did not send position or parameters up to upToDate

Samples:

For single device

               {
                              "result":0,
                              "payload":{
                                             “state”: {
                                                            "DeviceId": 23,
"MaxMessageId": 23,
                                                            "Parameters":[
                                                                           {
                                                                                          "TypeId": 1,
                                                                                          "Value":93.0
                                                                           },{
                                                                                          "TypeId":2,
                                                                                          "Value":0
                                                                           },{
                                                                                          "TypeId":3,
                                                                                          "Value":4153344.0
                                                                           },{
                                                                                          "TypeId":4,
                                                                                          "Value":1
                                                                           }
                                                            ],
                                                            "Position":{
                                                                                          "Latitude":29.026450994783758,
                                                                                          "Longitude":-98.360950751417988,
                                                                                          "Altitude":0.0,
                                                                                          "Quality":0
                                                            }
                                             }
                              }
               }

For all devices:

{
                              "result":0,
                              "payload": {
                                             “states”: [
                                                            {
                                                            "DeviceId": 23,
"MaxMessageId": 23,
                                                            "Parameters":[
                                                                           {
                                                                                          "TypeId": 1,
                                                                                          "Value": 93.0
                                                                           },{
                                                                                          "TypeId": 2,
                                                                                          "Value": 0
                                                                           },{
                                                                                          "TypeId":3,
                                                                                          "Value": 4153344.0
                                                                           },{
                                                                                          "TypeId":4,
                                                                                          "Value":1
                                                                           }
                                                            ],
                                                            "Position":{
                                                                                          "Latitude":29.026450994783758,
                                                                                          "Longitude":-98.360950751417988,
                                                                                          "Altitude":0.0,
                                                                                          "Quality":0
                                                            }
                                                            },
{
                                                            "DeviceId": 24,
"MaxMessageId": 26,
                                                            "Parameters":[
                                                                           {
                                                                                          "TypeId": 1,
                                                                                          "Value": 93.0
                                                                           },{
                                                                                          "TypeId": 2,
                                                                                          "Value": 0
                                                                           },{
                                                                                          "TypeId":3,
                                                                                          "Value": 4153344.0
                                                                           },{
                                                                                          "TypeId":4,
                                                                                          "Value":1
                                                                           }
                                                            ],
                                                            "Position":{
                                                                                          "Latitude":29.026450994783758,
                                                                                          "Longitude":-98.360950751417988,
                                                                                          "Altitude":0.0,
                                                                                          "Quality":0
                                                            }
                                                            }
                                             ]
                              }
               }

6.      Refresh token API token expires after 1 year. Before a token expires – new tokens can be generated for next 1 year period by request /RefreshToken Old token will not valid

Sample

               {
                              "result":0,
                              "payload": {
                                             “newToken”: “zzxxcc…”
}
}

Rosco Data Use It is important to monitor the data use from the Rosco Vision dash cam system. Incorrect settings or excessive use can lead to significant overage fees. Customers are responsible for monitoring their accounts and making adjustments to settings or use. Contact Fleetistics if assistance is needed before overage fees are incurred.

To check data usage of a Rosco Camera:

1. Log into Geotab: Log into MyFleetistics. Select GPS Systems (figure 1), then from the drop-down menu, select Geotab (figure 2).

2. Click the RoscoLive (figure 1) tab in Geotab’s left menu, then select Data Usage (figure 2) from the menu. This provides data usage for all Rosco cameras and includes an option for viewing specific groups or date ranges.

3. Select Camera Events from the menu. This tab is used to track data dealing with events. For example, speeding is a big reason cameras go over, to avoid this ensure to check the set up on the speeding rules in the account and consider bringing the speeding threshold up or talking to drivers about speeding habits.

Here is a recent example, of speeding event’s taking place in the same vehicle (#115) from 5:28:45 AM – 05:36:53 AM on the same day, this vehicle has already used 49.49 MB which is almost 10% of the available data for the month just over an 8-minute span because of multiple speeding events. If there is still any confusion contact support 1 (800) 481-1319 to schedule one on one training.

Install the DV-Pro 5 software on your PC (no Mac) and view the files from the Dual Vision in-cab video system.

Note: The camera must be powered off before removing the SD card or the SD card may be corrupted which can result in a loss of the files and programming on the SD card. Hold the power button until the LED screen turns off.

If you are unsure about proper installation techniques, contact a professional. It is more cost effective to have the installation done right the first time. Be sure to give your installer this link for reference. Failure to follow the instructions will lead to issues. Instructions herein are not all inclusive and installation best practices should be followed by a qualified installer or mechanic using the attached documents.

Special Mounting Notes:

• For the windshield glue to work correctly, the glass must be between 50 and 100 deg F or 10-38 C.
• Do not use glass cleaner. Only the provided cleaning pad and 1 per vehicle. 70% isopropyl alcohol will also work. Commercial glass cleaners contain surfactants & denatured alcohol which can reduce the effectiveness of the adhesive.
• Let the primer cure for 30-60 minutes depending on the temperature (longer for colder conditions).
• Press and hold the mount to the glass for 30-60 seconds.
• No other mounting technique works long-term as determined by testing done by 3M Corp. 3M automotive tape will not work long-term. 

Tips:

1. Installation is not complete until you view a live connection and download and view a 3 second video clip from your online account. 
2. SD card & Camera Head Removal - It is very important that you properly power off the camera before removing the SD card or mounting the camera head (**ignition must be off**). Failing to do so may corrupt the SD card or camera firmware, potentially causing a loss of all data.
   1. DV4 - To remove the SD card, with the ignition off, power the unit down per the unit instructions and then remove the SD card. The ignition may be off but the camera can still have power so be sure to follow this procedure. To remove the camera head, be sure the ignition is off.
3. The camera off delay has an auto shut down in case the battery level drops.
4. The larger DV4 cellular antenna mounts with the larger side to the glass.
5. Use a poke and wrap or solder connections. Crimp connectors and fuse taps are not recommended.
6. Zip tie all wire connections going into the unit, especially around the USB connections.
7. Avoid the airbag system.
8. Upgrade to a larger SD card for more recording time. The more cameras on a vehicle, audio recording, etc., divides the storage space among these files. A factory supplied/approved SD card is required due to extreme conditions encountered.
9. If the camera does not transmit data after confirming power and ignition and check connections. Contact support.

Replacing a Windshield

1. Order and maintain adhesive kits so they are readily avalable when a windshield is replaced.
2. Carefully remove the mount from the glass. 
3. Remove the old mounting pad and primer from the mount.
4. Follow mounting instructions as if a new installation.
5. DV6 customers can use the web portal live view to confirm the camera perspective. 
   1. For a new installation, use the Rosco installation mobile app.

Harnesses

1. DV673 for hardwire
2. DV665 for OBDII
3. DV672 for Jbus

References

• DV6 Installer app - Click here for Android and iOS
• DV6 - Getting Started

YouTube

• DV6 - https://youtu.be/KGOOwmpB02E?si=mk_1i3agDT0XKgkS
• DV4 - https://youtu.be/WcIRZeqEhIc?si=Qb-k153JyKL8eJgt 

Documents (email support@fleetistics.com if links fail)

• DV6 Quick Start and Install Guide v9.23.pdf
• DV4 Mounting Instructions.pdf
• DV4 Installation v9.23.pdf

Backup and Additional Cameras

• Single External Camera - (example backup camera) - A DV609 converter box is required
• For 2+ external cameras, a STSS1200 mulitplexer (splitter) is required in addition to the DV609

Understanding how camera settings impact your video quality and monthly cost will ensure you find a balance between the two. In general, the default settings have been found to be the best for the average customer. Changing these can increase your cost exponentially so be careful. In-cab video (ICV) is all about data transfer cost. The smaller the video files and the fewer you transmit, the less chance there is for expensive overage fees. These variables also determine how much data can be stored on the SD card in a looping memory. If you normally get 300 hours of recordings, you would only get 150 if you double the size of the data files.

File Sizes

There are 3 primary variables that impact the data volume used from the monthly data plan. Testing should be done on 1 camera before making changes to all to avoid expensive overage fees.   Framerate per second (fps) - The number of images that are captured per second. 7 fps is about what the eye can see. Moving this to 14 fps will double the data being transmitted and consume more of your data plan. Resolution - The quality of the images captured can make a big difference in the file size. This impacts the data transmitted as well. A standard resolution image is often good enough and produces a file of 2 megs. Going to HD might make the same file 8 megs or 400% more data. Exception settings - Video exceptions should be for the most important exceptions only. Exceptions such as accident detection or movement after hours should produce video clips. Creating video exceptions for speeding events could create an excessive amount of exception videos that have no real value after the first one. Each video deducts from your data bucket so choose wisely. If you opted for the live streaming service, leave some data available to stream a few times per month without going over your data plan.  

Live Video

Live video is an option for some camera systems. This enables a user online to "see" through the camera and view in the cab or outside the vehicle. This can be handy in specific applications but it consumes a lot of data. Live streaming should be limited to special situations or spot checking. Live streaming cannot be run continuously due to the cost so most cameras timeout after 60 seconds. You can then enable it over and over if needed.    

SD Cards

The cameras contain an SD card to store video continuously. The number of hours that can be recorded depends on the above variables as well as the size of the SD card itself. 64 gig cards hold a lot of data. If you use a slow or smaller SD card you can run into issues. If an event is not captured as an exception video clip, the SD card can be inserted into a computer and the looping video reviewed to find a particular date and time.   Default settings are on the device on delivery. Changing these settings requires special technical knowledge. Changes WILL impact monthly service fees. Do not change camera settings.

The Dual-Vision includes IR for the interior facing camera. The outside view is dependent on ambient light

Rosco Vision System Installation Information Rosco Camera System Installation Instructions

How to pair a GO device with Rosco Camera 

Purpose: This article outlines the process pairing a GO device with a new Rosco Camera. 

Procedure:  

1. Click RoscoLive in the left menu (1).
2. Click Camera Admin in the menu (2).
3. Click the red link icon under Paired Go Device (3).
4. Select the vehicle the camera is to be paired with (4). 

Additional Notes: If you encounter issues, please create a support case for assistance. The link below contains instructions on how to create a support case. https://www.fleetistics.com/support=cases-made-easy/. 

1. Press the circle “Menu” button.

2. Press the + button to switch the view on the in-cab monitor from “Mirrored” to “Normal” or the option that shows the image in the correct orientation.

Transferring Geotab service to a different reseller for any reason can be a disheartening experience. With over 21 years as a Geotab reseller, Fleetistics is the world’s longest-standing Geotab reseller. We know Geotab like no other reseller. More importantly, we know fleet customers and how to help them get the most out of the Geotab platform.

Additionally, the customizations Fleetistics has done go beyond the Geotab platform. Fleetistics’ team includes some of the most tenured team members of all Geotab resellers. With such great experience, our team will help you transition and achieve the user experience needed to drive your ROI while providing a superior level of customer service that is only found in a boutique business like Fleetistics.

**Important**

It is very important to address the relationship with your current reseller when transferring the Geotab service. Losing a customer is an emotional process for everyone. If you have a service agreement in place with Fleetistics or another reseller, you must settle that, or have a plan to settle it, prior to transfer.

Your current reseller is NOT required to sign the transfer document. If you owe the reseller money, address it and move forward.  Fleetistics only works with customers in good standing in a win-win relationship. If someone will bad debt another reseller, they will do it to us.

Do not sign another agreement with any Geotab reseller prior to having an exit strategy or fulfilling the agreement with your current Geotab reseller. 

Fleetistics Guarantee

Fleetistics offers a variety of service agreements ranging from monthly to longer-terms. The longer the term, the lower the price. Simple business. Since you are taking a leap of faith to join the Fleetistics family when transferringGeotab service, all transfer agreements will come with a 60 day no cancellation penalty period. If you do not like our service, pay for the service used and equipment purchased (if any), and there will be no ETF.

Transferring Service to Fleetistics

Option 1 – Most Popular

• Keep your devices (no install, vehicle downtime, or wages)
• Keep your data, account, and configuration
• Transfer your account billing, support, and administration to Fleetistics
• Current reseller and Fleetistics must sign the Geotab Transfer Billing form
• Pay $40 transfer fee, per vehicle to Geotab, billed to you by Fleetistics

Option 2 – Start Over Plan

• Scrap your devices and purchase new ones from Fleetistics with a 10-year limited lifetime warranty
• Leave your data behind but download into Excel reports prior to cancellation
• Start a new account with Fleetistics with the guidance of our experienced team
• Schedule follow up training to maximize your ROI
• Explore new products and services as your business grows

Either process for transferring Geotab service requires completing an order with Fleetistics. Each order provides access to our Terms of Sale, warranty, and online Business Management Portal (invoices, support tickets, dashboards, fuel card integration, etc.)

Transferring Service to Another Geotab Reseller

• All requests must be initiated by creating a support case. (Learn how here). This documents the time, date and user to protect you and Fleetistics.
• Do not sign a new agreement until the agreement with Fleetistics is fulfilled. Transfer and early termination fees (ETFs) may apply.
• Pay any outstanding fees due to Fleetistics.
• Provide a Request to Transfer Billing form. Provided by the new reseller to Fleetistics.
• Fleetistics will sign the form when all terms of the current agreement are fulfilled.
• Pay Geotab transfer fee. 

Alternative To Transferring Service

To avoid transfer fees, the general hassle and risk of transferring to another reseller you do not know, you can enable a third party to access your data using the free Geotab API. This often provides the desired integration without the unwanted fees.

Geotab offers an option to replace a current device with another. This feature maintains all existing data 
such a trip histories, exceptions, engine data, ELD/Hour of Service data, and DVIR reports.

To replacing a device
To replace a device, a user must have the clearance Administer devices (delete/unplug/replace) or

Administer devices enabled.
1. Click the Vehicles & Assets option in the left menu (figure 1).
2. Select the vehicle by clicking the vehicle name in the list.
3. Scroll to the center of the Asset tab and find the Replace with new device button (figure 2).
4. Click the Replace with new device button located under the device serial number field (figure 3). Once the button is clicked a new window is displayed.
5. Enter the serial number for the NEW device in the Serial Number field (figure 4).
6. Finally, click the OK button at near the top of the window and the change is complete.

Download Instructions

Figure 1

Figure 2

Visit the below related link to purchase support hours for downloader troubleshooting. Once the support hours are purchase, contact Fleetistics support at 877-467-0326 option 2. Fleetistics support will confirm the order and will begin to troubleshoot the RF passive System. Note: A remote session to the computer that has the checkmate services running may be required to perform the troubleshooting.

1.  Period to be included in the report
   
   • Today - Midnight to approximately the present time
   • Previous 24 hours - Previous conscutive 24 hours from the current time
   • Previous 3 days - Previous 3 consecutive days, excluding today, starting at 12:01 the first day
   • Previous 7 days - Previous 7 consecutive days, excluding today, starting at 12:01 the first day
   • Previous 21 days - Previous 21 consecutive days, excluding today, starting at 12:01 the first day
   • This week - Current calendar week from Monday to current day
   • This month - Current calendar month
   • Last week - Last Monday - Sunday
   • Last month - Last calendar month
   • Custom - User defined date range
2.  Period comparison options
3.  Refresh the data after selection
4.  Changes the data displayed in the chart at the top
5.  Number of devices to display in the chart at the top
6.  Select the columns to be displayed in the table below
7.  Opens the options window below the chart
8.  Search the table by device name
9.  Sort the table by the data in the column
10.  Odometer as reported by the vehicle computer at the end of the time period selected. Not all devices or vehicles provide this.
11.  Distance traveled during the selected time period. This is based on the vehicle odometer if available. If not, GPS distance is used which will vary in accuracy based on many factors.
12.  Gallons of fuel used during the selected time period as reported by the vehicle.
13.  Fuel economy as reported by the vehicle. This is not available from all OBD devices, 3-wire installs or asset trackers.
14.  Idle time over 300 seconds (>5 minutes)
15.  Idle time under 300 seconds (<5 minutes)
16.  Engine hours (run + idle) as reported by the vehicle.

The Fleetistics mobile app is a fleet toolbox of various features and services. The app can be used by an individual or connected to a MyFleetistics account. Every customer has an App License key generated with the account is created in MyFleetistics. This code is put into the mobile app under the profile menu so the users app data can be correctly associated with a MyFleetistics account. The final step in connecting the app to the MyFleetistics is to go into Acccount>Services Administration and enable the service you want to use. You can enable one or all the services in the app depending on what is important.

Mobile App Modules and Services

• Time and Attendance - track work, breaks and personal time and mileage as well as add pushpins for waypoinst or checkins. Used for people driving personal vehicles, foot patrols or a time card. If the services is enabled in MyFleetistics, timecard reports will be available to document the data collected in the app. When a user is on personal time, the mileage and time is calculated but the users GPS track is hidden from the employer. The personal mileage and time can be used for tax mileage deductions.
• SOS - This is not connected to 911. The SOS button will send an email to the email entered by the user. If the service is enabled in MyFleetistics the SOS alert will appear on the MyFleetView map.
• Future Modules Planned - Installation tracker, DVIR, electronic forms and more.

Active Directory Service

Fleetistics offers customers the ability to share secure user rights management (URM) access information between existing systems and the MyFleetistics portal providing a single sign on experience. This Active Directory integration also provides immediate user access and denial based on centrally managed Active Directory changes completed as part of routine processes with your organization. This provides additional security and a significant reduction in user maintenance time for the telematics platform program manager.

If your organization has Azure AD or ADFS but does not have the IT skills to complete the setup, www.IGTech365.com can assist you for a set project free. IGTech365 can also provide managed IT services, backups, employee help desk and other IT networking and administration services. 866.365.7798

If your organization utilizes a different URM services and would like to discuss an integration project contact your account manager. (OAuth, OpenID, SAML, LDAP, LenAuth, HTTP Basic, etc)

Submit any corrections or suggestions to contact@fleetistics.com  

Azure AD Setup

1. Enable the appropriate Active Directory service in MyFleetistics>Account>Services>Services Admin
   1. Sign into your Azure portal.
   2. Choose the Directory by selecting your account in the top right corner of the page, followed by selecting the Switch Directory navigation and then selecting the appropriate Directory.
   3. In the Azure portal, search for and select Azure Active Directory.
   4. In the Azure Active Directory left menu, select App Registrations, and then select New registration.
   5. Follow the prompts and create a new application: - Name: My Fleetistics - Supported account types: "Accounts in this organizational directory only" or "Accounts in any organizational directory" (if you have several directories) - Platform configuration (Optional): "Client Application (Web, iOS, Android, Desktop+Devices)" then click "Register"
   6. On the next page click "+ Add platform". If you accidentally close the next page after register - select the "My Fleetistics" application and click "Add a Redirect URI" select "Web application" - "Web" - Redirect URIs: "https://my4.myfleetistics.com/complete-azure-ad-login" - Logout URL: leave empty - Implicit grant: check "ID tokens" checkbox then click "Configure"
   7. On the application page select "Token configuration (preview)" at the left menu click "+ Add optional claim" and select "ID" as the Token type. Check: - email - family_name - given_name - nickname then click "Add" click "+ Add groups claim", check "Security groups" at "Select group types to include in Access, ID, and SAML tokens.", open "ID" section in "Customize token properties by type" and choose "Group ID" then click "Add"
   8. If you plan to grant the MyFleetistics application with the rights to read User Info to in order to provide the Users' phones On application page select "Certificates & secrets" at the left menu click "+ New client secret", fill the "Description" with any descriptive text like "user info access". Copy the secret value so you can assign it on the service settings page later - On application page select "API permissions" at the left menu click "+ Add a Permission", choose "Microsoft Graph" and "Application permission" then check "User.Read.All" and click "Add permissions". You can revoke this grant any time or disable reading User Info on service settings page.  
2. Enable "Azure AD Single Sign On" on Company Services Admin page, then open settings of this service and assign: - Directory ID - Directory (tenant) ID from Azure AD My Fleetistics Application page - Application ID - Application (client) ID from Azure AD My Fleetistics Application page - Application Client secret - Generated Client secret Azure AD User of your Company will be only allowed to login to My Fleetistics if was assigned to application role or group. If you want that any Azure AD User of your Company will be allowed to login to My Fleetistics - you should select "Default Permission Role" that will be used for user without assigned role or group Unique login URL is a link to special login page that should be used by users of your company - https://www.fleetistics.com/login/?azureAdCompanyID=[your companyID] Debug login URL link will show Azure AD token payload without the actual login to be able to check what is sent by Azure AD to My Fleetistics
3. If you plan to use Application Roles to manage MyFleetistics User Roles
   1. Declare roles for My Fleetistics application select "Manifest" at the left menu of My Fleetistics application page and replace node "appRoles" with list from file: app_roles.txt then click "Save"
   2. You can assign roles to users/groups as described in documentation (https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-add-app-roles-in-azure-ad-apps#assign-users-and-groups-to-roles)  
4. If you plan to user Azure AD Groups to manage My Fleetistics User Roles
   1. Create new groups: FLT-Administrator, FLT-Supervisor, FLT-DefaultUser, FLT-Dispatcher, FLT-DriveAppUser, FLT-ViewOnly, FLT-Nothing, FLT-Inactive or use your own groups
   2. Map Azure AD groups (by group Object ID) to My Fleetistics User role on the "Azure AD Single Sign On" settings page If User have more than one group assigned - will be used the first matched group in the order you created the groups mapping   5. Both - Application Roles and Azure AD Groups can be used together at the same time: - if User has assigned Application Role - it will be used - if no Application Role - Azure AD Groups will be used - if no Roles or Groups - Default Permission Role will be used - if no Default Permission Role was assigned - user won't be allowed to login.  

ADFS Setup

1. On your server open AD FS Administration and open Add Relying Party Trust Wizard by clicking “Add Relying Party Trust…” at the Action menu:
   1. “Select Data Source” - Choose “Enter data about the relying party manually”
   2. “Specify Display Name” - Enter a display name for the relying party. This name won’t be shown to user and is for Admin only
   3. “Choose profile” - Choose “AD FS Profile”
   4. “Configure Certificate” - Skip this step
   5. “Configure URL” - Skip this step
   6. “Configure Identifiers” – add Relying Party Trust Identifier that lately will be assigned on "Active Directory - ADFS User Authentication & SSO Service" admin page
   7. “Configure Multi-factor Authentication Now?” – choose “I do not want to configure multi-factor ….”
   8. “Choose Issuance Authorization Rules” – choose “Permit all users to access this relying party”
   9. “Ready to Add Trust” – skip this step
   10. Finish

Add:  

3. To assign MyFleetistics permission roles to your users you can create special groups: FLT-Administrator, FLT-Supervisor, FLT-DefaultUser, FLT-Dispatcher, FLT-DriveAppUser, FLT-ViewOnly, FLT-Nothing, FLT-Inactive or use your own groups. After this you have 2 options:

3.1.    You can map AD Groups to MyFleetistics permission roles in the MF Admin page To do so you should select Relying Party Trust and click “Edit Claim Rules…”,

Select rule name “UserInfo” and click “Edit Rule…

Add:

It will send the list of all User group SIDs to MyFleetistics on the "Active Directory - ADFS User Authentication & SSO Service" admin page map each used group to MyFleetistics permission roles by assigning Group SID and selecting permission role from the list

3.2.    You can map AD Groups to MyFleetistics permission roles in the AD FS Management. To do so you should select Relying Party Trust and click “Edit Claim Rules…”, For each group click “Add Rule…”, choose “Send Group Membership as Claims” in “Claim rule template”, assign “Claim rule name” that will be used just to name the rule, select AD Group in “User’s group”, assign “Outgoing Claim Type” as “flt-role” and “Outgoing claim value” as one of MyFleetistics permission roles Supervisor, Default, Dispatcher, Driver, ViewOnly, Nothing, Inactive

This way allows you to not send all User group SIDs to MyFleetistics but requires to assign claim type and value manually for each mapped group.  

1. Go to: https://www.fleetistics.com/login/ Enter your credentials and login.

2. On the left side menu click on FLT Control Panel. Click on FLT Account Admin.

3. In the search bar enter the name of the account, (1) and then click on the name (2) to open the administrative options for that account.

4. Choose the Users option which is the third option down.

5. On the right-hand side of the page click on Create User.

6. Enter the user information, ensuring the fields with asterisk's are filled out.

7. Under the Account section, make sure that the Status field is set to Active, and the Account Type is set to Customer.     For customers these settings should always be chosen and should not be changed.

8. For Geotab users scroll down to the bottom right hand corner and click on Save.

NOTE: For Geotab users nothing else needs to be done. Do not make any changes in the Geotab section and leave the password field blank. If this is not done it may cause login issues.

9. Once saved, look for the user you just added and choose the desired permissions.

The Device Status Table (DST) look at all GPS devices integrated into the MyFleetistics portal (Geotab, Fleetistics ONE, Fleetistics LITE, etc). The table is designed to help you see the status of your devices at a glance and easily submit a support ticket if a device is not reporting correctly.

There may be a difference between what the DTS reports and other GPS platforms. The DTS includes devices that are in your account that may not have been installed. Where Geotab does not include devices that have not reported at least one time.

Issue:

If you are unable to login into your MyFleetistics account from the Fleetistics.com website, follow these steps. If you are unable to login to your MyGeotab account click here. Only change your password in MyFleetistics, never in MyGeotab.

Routine Fix:

1. Ensure your GPS program manager has submitted your name, email and security level to Fleetistics and the profile is active.  If it is not, it can be submitted by opening a support ticket from the Help Center>Support>Cases menu or by having the GPS program manager email support@fleetistics.com.  We must have the request from your GPS program manager for security. All other requests will be declined.  The support case will be updated in this location for your convenience.
2. Ensure you are using a supported web browser and clear the browswer cache (history) to delete any "memorized" information for this URL. Click the link to view browser details. http://www.fleetistics.com/browser-help.php
3. Add Fleetistics.com, myfleetistics.com and mygeotab.com as exceptions to browswer your popup blocker.
4. Follow the Forgot Password steps by going to www.fleetistics.com. In the top right corner of MyFleetistics click on Customer Login. On the login popup window select Forgot Password and follow the steps. If you do not receive the password reset email in a few minutes check your junk mail and ask your IT person to white list fleetistics.com, myfleetistics.com and mygeotab.com.

If these steps fail please submit a case through MyFleetistics>Help Center>Support>Cases. Our support team will review all settings and contact you to help resolve the issue. By submitting a case in this manner you will avoid benig on hold or leaving a voicemail and it allows us to review the situation and get back to you with a resolution.

Issue:

If you are able to login to your MyFleetistics account but not able to launch or access your Geotab account, your passwords are out of sync. In order to provide single sign on from MyFleetistics to MyGeotab the passwords must match. *Never change your password in Geotab*, just in MyFleetistics. Your MyFleetistics password will be automatically sync and over write your Geotab password so they match. This will not work going from Geotab to MyFleetistics.

Fix:

1. Click F5 in your browser or take other steps to delete your browser cache may be needed.For more tips click this link. https://fleetistics.com/browser-help.php
2. In MyFleetistics, click the down arrow by your name in the top right corner, select Your Profile. Click the green tile that says Password and change your password. You can re-enter your current MyFleetistics password or enter a new one. Whatever you enter will be used going forward.
3. Also check your browser for a pop-up blocker.

If you still have issues contact Fleetistics through the Help Center>Support>Cases menus on MyFleetistics.

Monday - Friday, 7:00 am to 6:00 pm, EST. Emergencies, such as accidents, will be responded to after hours. Please review the content in the Help Center in your MyFleetistics account, Fleetistics.TV or this FAQ manager for more possible solutions during off hours.

A vehicle not reporting on the map or a user not able to login will be handled the next business day. We cannot remotely make a device report and we have a password reset function to automate resolving login issues.

If you are seeing a blank or white screen when trying to open a GPS platform from the MyFleetistics menu, the X-Frame policy is causing an issue. To correct this add the appropriate browser extension. If you are unable to install the certified browser add-in, contact your IT department. An exception may need to be added for myfleetistics.com and mygeotab.com.

This is a fix Firefox and Chrome.

Firefox https://addons.mozilla.org/en-US/firefox/addon/ignore-x-frame-options-header/

Chrome https://chrome.google.com/webstore/detail/ignore-x-frame-headers/gleekbfjekiniecknbkamfmkohkpodhe?hl=en-US

Edge No issue detected

Safari Not tested - Not supported

	Firefox X-Frame Add-in Resolves page will not load from MyFleetistics.
	Chrome X-Frame Add-In Resolves page will not load from MyFleetistics.

The Fleetistics DPS-API provides unified access to the information reported by any device registered in your account. Devices of all manufacturers, type, configuration and device data provider are supported.

For all device types, the system provides a list of registered devices.

Information provided includes:

• A list of each device’s current state, manufacturer/type/configuration, current location, speed, battery status, last update date.
• A list of raw device parameter values for specific devices by date/time. The list of parameters is unified and independent from device types. However, each device type or configuration can send its own set of parameters.
• A list of raw device messages for specific devices by any date/time period. Messages contain only updated device parameters and location. Messages always provide a unified type reliant on the device message type. If device sends events such as start/stop motion or ignition on/off, the message will contain a unified event type. Messages can be empty if no change in parameter value or status.

Required skills: The ability to form and send an HTTP request with header and handling for JSON responses.

To get started: In MyFleetistics, go to Account > Services > Administer Services. Enable the Data Processing Service (IoT) API option. Then open Service Settings by clicking the icon to obtain an API Key. The Service Settings page contains an API Explorer hat includes a list of all requests and the ability to test each request on your real data, then copy the request URL.

Request details:

• To get data send an HTTP Get request with parameters that include a query string and data will be returned as JSON response.

Request must include header "Authorization” with value "Bearer " + APIToken.

You can copy "Authorization” header on from the Data Processing Service (IoT) settings by clicking the Copy Auth Header button.

• Requests can be concurrent.
• Max number of concurrent requests and max number of requests per hour are limited by the service level selected.

If requests exceed the limit - HTTP code 429 Too Many Requests is returned.

• The maximum number of returned messages by single request (GetDeviceMessagesBy*/GetMessagesBy*) is limited by 1000 messages.

If a request returns more than 1000 messages - only first 1000 messages are returned and the flag "isLimited" is true.

Returned messages are ordered by Message.Id so you can build new request starting from the last returned Message.Id

• The base API url is: https://my4.myfleetistics.com/api/dps/
• A call always returns a JSON object containing the fields "result" and "payload". The response result=0 indicates success. The response result !=0 indicates an error. An error returns the field "message" with details.
• Payloads can be a JSON object or array depending on the request

Examples of calls for use with GPS devices:

• Show devices on map or show list of devices statuses:
  • Request the list of devices once (/GetDevices) – to show device name and type.
  • Periodically request the list of device statuses (/GetDeviceCurrentStatuses)

Device current status contains latest device location, speed and bearing to show position on a map.
It also includes LastCommunicationDate, IsBatteryOk, IsIgnitionOn, IsInMotion for device state.

• Show device state for a date/time
  • Request the list of devices (/GetDevices) – to show the device selector
  • Ask user for DateTime
  • Request a list of parameters (/GetParameterTypes)- to display parameter names.
  • Request initial device state (device parameters values) on “DateTime” (/GetDeviceStateUpToDate)

Showing device location and all parameter values can be accomplished with DateTime

• Show device activity:
  • Request device list (/GetDevices) – to show the device selector.
  • Ask user for fromDate and toDate.
  • Request list of parameters (/GetParameterTypes)- to show parameter names.
  • Request list of event types (/GetEventTypes)- to show eventTypes names.
  • Request initial device state (device parameters values) using “fromDate” (/GetDeviceStateUpToDate)

All device parameters values at the beginning by entering user period.

• To request device messages for period fromDate to toDate (/GetDeviceMessagesByDate). If the quantity of messages is more than 1000, the response will include isLimited = true. In this case – send again (/GetDeviceMessagesByDate)with the same period fromDate to toDate adding parameter fromMessageId as maxMessageId+1 from latest response to build afull list of messages.

Device messages contain only device parameters location changed by this message. Also some devices send events like start/stop motion or ignition on/off – in this case the message will contain the event. Some messages can be empty if nothing changed. Empty messages should be ignored and show only non-empty messages. This allows the user to see device activity during the period.

• Show device messages
  • Request list of devices (/GetDevices) – to show the device selector.
  • Ask user for fromDate and toDate.
  • Request the list of parameters (/GetParameterTypes)- to show name of parameters.
  • Request the list of message types (/GetMessageTypes) - to show name of messageTypes
  • Request the list of event types (/GetEventTypes)- to show name of eventTypes
  • Request device messages for period fromDate to toDate (/GetDeviceMessagesByDate).
    If the quantity of messages is more than 1000, the response will include isLimited = true. In this case – send (/GetDeviceMessagesByDate) again with the same period fromDate to toDate including the additional parameter fromMessageId as maxMessageId+1 from the latest response to return the full list of messages.

When the list of messages is called, the message type can be a periodical update message or system message. If message has event – the event name is included. Empty messages can be shown or ignored. Some empty messages can be system or contain only an event.

If full device state for each message is needed, load (/GetDeviceStateUpToDate) at the beginning of period, then check that messages are sorted by messageId in the list. In series replace the values in full device state with the same parameters. Location is provided in device state for each message.

• Datafeed service for continuously syncing all data to an internal database.
  • Request the list of devices once, parameters, message types, event types (/GetDevices, /GetParameterTypes, /GetMessageTypes, /GetEventTypes) to save them into your database.
  • Periodically, for example, once a day, request the lists again to check using “LatestUpdateDate” to determine is an entity changed, updadted, or add it to your database.
  • Request the initial device state (device parameters values)once for the start date of a datafeed (/GetDevicesStateUpToDate)request to save to a database. This request return states of all devices. The datafeed process can be restarted anytime from the same or a different date
  • Request all device messages once for all devices for a DataFeed start date without specifying a to date (/GetMessagesByDate). If the quantity of messages is more than 1000, the response will include isLimited = true. In this case send (/GetMessagesByDate)again with the same fromDate but include parameters fromMessageId as maxMessageId+1 from latest response. This builds the full list of messages. When all messages are returned, save the latest maxMessageId to a database.
  • To periodically calculate period how frequently devices are reporting, how frequently data is to be updated, and what are the requests limitations on your account,
    request new messages using (/GetMessagesById) with latest messageId saved to a database.If the quantity of messages is more than 1000 use the same procedure as the initial load but with (/GetMessagesById). Once all messages are received, save the latest messageId to a database.

To implement a datafeed of device messages, request a list of available devices again.

Then, periodically sync the list of devices with returns with usage device.Id as unique ID.

Device messages can be requested per device or for all devices. Message.Id can be used as serial.

It is integer incrementing messages unique key that is never changed.

Message.DCSDate is UTC time when server received message from device.

It never returns lower number than those already received.

Message.Date is generated by device. If a device sends delayed messages from its cache, you can receive an older date than those already delivered.

• Base API url is: “https://my4.myfleetistics.com/dcsapi/”
  
  
• A JSON object with fields "result" and "payload" are always returned. Result=0 indicates success, result !=0 indicates an error. In case off error a "message" with details is returned.

Payload can be a JSON object or array depending on the request.

• Device messages contains two dates:
  • Date - is the DateTime of message sent by device.
  • ServerDate - is the date the server received the message.
  • Both dates are in UTC. Device messages can be stored in device memory and sent at a later time.

DeviceCurrentStatus contains deviceID - to show device name or type, use the result of /GetDevices request.

GetDeviceCurrentStatuses does not return current status for a device that has never reported.

GetDeviceCurrentStatuses returns one current status per device.

GetDeviceCurrentStatuses always returns a list of all current statuses. It does not depend on reported device since your previous GetDeviceCurrentStatuses request or no.

API Requests:

1. To return a list of Parameter, Message, or Event types use (GetParameterTypes, GetMessageTypes, GetEventTypes). Example: https://my4.myfleetistics.com/dcsapi/GetParameterTypes returns:

"Id" - integer, ID of Parameter, Message, Event, used in the rest of requests

"Name" - string, name of Parameter, Message, Event

"LatestUpdateDate" - integer, Unix time, UTC/GMT, time of latest entity parameter update

Parameters, Message types, Event types include device manufacturer, type, configuration independence.

Sample:

{
               "result":0,
               "payload":{
“messageTypes”: [
                              {
                                             "Id":4,
                                             "Name":"Update",
                                             "LatestUpdateDate":1564156521
                              },{
                                             "Id":17,
                                             "Name":"System",
                                             "LatestUpdateDate":1566797645
                              }
               ]
}
}

2. List of devices, /GetDevices returns:

"Id" - integer, ID of device will be used in the rest of requests

"TypeName" - string, name of device type

"SerialNumber" - string, unique ID of device, depending on the device type, this can be the device IMEI, ESN, UID, Serial number.

"Name" - string, name of device in MyFleetistics

"ActivatedDate", integer, Unix time, (number of seconds that have elapsed since January 1, 1970 (midnight UTC/GMT)), UTC/GMT. The time the device started reporting for into this account

"DeactivatedDate" - integer, Unix time, UTC/GMT, time when the device stopped reporting for into this account, optional, can be null for active device

"LatestUpdateDate" - integer, Unix time, UTC/GMT, time of latest device parameter update

"LatestDeviceMessageDate" - integer, Unix time, UTC/GMT, time of latest device message, optional, is null for non-reporting device

Example:

{
               "result":0,
               "payload":{
“devices”: [
                              {
                                             "Id":4,
                                             "TypeName":"FLT-TLP",
                                             "SerialNumber":"866425035335092",
                                             "Name":"TopFly 0x26 Test",
                                             "ActivatedDate":504921600,
                                             "DeactivatedDate":1429825293,
                                             "LatestUpdateDate":1564156521,
"LatestDeviceMessageDate ":1564156521
                              },{
                                             "Id":17,
                                             "TypeName":"FLT-TLP",
                                             "SerialNumber":"866425039637030",
                                             "Name":"test DCS export",
                                             "ActivatedDate":1566297674,
                                             "LatestUpdateDate":1566797645,
"LatestDeviceMessageDate ":1564156521
                              }
               ]
}
}

3. List of devices current statuses, /GetDevicesCurrentStatus this request returns statuses of reporting devices

Device type independent response.

LastCommunicationDate, IsBatteryOk, IsIgnitionOn, IsInMotion

"LastCommunicationDate" - integer, Unix time, UTC/GMT, time of latest device message of any type - position message, alert, heartbeat or system message

"IsBatteryOk" - boolean, multi-sourced battery OK status, obtained from different parameters returned by different types of devices. Includes internal/external/backup battery state.

"IsIgnitionOn" - boolean, current state of ignition if device supports it. Absent if device does not send ignition state

"IgnitionChangeDate" - integer, Unix time, UTC/GMT, time when ignition state last changed

"IsInMotion" - boolean, multi-sourced status obtained from non-zero speed and in motion state returned by some devices

"InMotionChangeDate" - integer, Unix time, UTC/GMT, time when motion state last changed

"PositionDate" - integer, Unix time, UTC/GMT, time when latest valid position was received from device

"Latitude", "Longitude" - double, latest valid GPS position

"Bearing" - float, in degrees, latest vehicle direction received from device

"Speed" - float, in km/h, latest device speed received from device. If the device sends both OBD and GPS speed - OBD speed will be used

Sample:

{
               "result":0,
               "payload": {
“devicesCurrentStatus“: [
                              {
                                             "DeviceId":4,
                                             "LastCommunicationDate":1564156487,
                                             "IsBatteryOk":true,
                                             "IsIgnitionOn":true,
                                             "IgnitionChangeDate":1564145612,
                                             "IsInMotion":false,
                                             "InMotionChangeDate":1563403548,
                                             "PositionDate":1564145926,
                                             "Latitude":28.187429428100586,
                                             "Longitude":-82.374893188476562,
                                             "Bearing":291,
                                             "Speed":0.0
                              },{
                                             "DeviceId":17,
                                             "LastCommunicationDate":1566320213,
                                             "IsIgnitionOn":false,
                                             "IgnitionChangeDate":1566320213,
                                             "IsInMotion":false,
                                             "InMotionChangeDate":1566320213,
                                             "PositionDate":1566320213,
                                             "Latitude":28.19282,
                                             "Longitude":-82.37767,
                                             "Bearing":143,
                                             "Speed":0.0
                              }
               ]
}
}

4. Device messages

Can be used for a single device - /GetDeviceMessagesByDate, /GetDeviceMessagesByServerDate, /GetDeviceMessagesById with required parameter- deviceId

or for all devices - /GetMessagesByDate, /GetMessagesByServerDate, /GetMessagesById

Device message contain two dates:

- Date - is the DateTime of message sent by device

- ServerDate date time - is the date the server received the message.

Both dates are UTC. A message can be stored in a devices memory and sent later when the device has a network connection. So message.ServerDate can be later than message.Date

/GetDeviceMessagesByDate, /GetMessagesByDate have optional parameter - fromDate, toDate - integer, Unix time, UTC/GMT, message Date

/GetDeviceMessagesByServerDate, /GetMessagesByServerDate have optional parameter - fromServerDate, toServerDate - integer, Unix time, UTC/GMT, message ServerDate

/GetDeviceMessagesByDate, /GetDeviceMessagesByServerDate, /GetMessagesByDate, /GetMessagesByServerDate have optional parameter – fromMessageId – integer, min messageId to get next pack of messages if a previous request response was limited due to quantity of messages

/GetDeviceMessagesById, /GetMessagesById have optional parameter - fromId, toId - integer, message Id

The set of returned parameters depends on device type/configuration.

Parameter value, type and formatting are device independent.

"Id" - integer, unique ID of message.

"DeviceId" - integer , unique ID of device

"Date" - integer, Unix time, UTC/GMT, device generated date/time of message

"ServerDate" - integer, Unix time, UTC/GMT, date/time when server received message

"MessageTypeId", integer, unique ID of message type. Can be decoded to name of message type by the list returned by /GetMessageTypes

"EventTypeId", integer, unique ID of event type. Can be decoded to name of event type by the list returned by /GetEventTypes

An optional parameter is sent when a device sends an event like ignition on, vibration, accident, OBD errors:

"Parameters" – returns a list of parameters changed by message. Can be omitted if message does not change any parameters

Parameter structure:

"TypeId", integer, unique ID of parameter type. Can be decoded to name of parameter type and unit by the list returned by /GetParameterTypes

"Value" - string representation of value

"Position" - GPS position if position changed. Can be omitted if message does not change the position

Position structure:

- "Latitude", "Longitude" - double, GPS position

- "Altitude" - float, altitude, m

"Quality" - integer, can be GPSFine = 1, GPSFair = 2, GPSPoor = 3, LBS = 4, Interpolated = 5, GPSBad = 13

Sample:

{
               "result":0,
               "payload":{
                              messages: [
                                             {
                                                            "Id": 12,
                                                            "DeviceId":11,
                                                            "Date":1561100731,
                                                            "ServerDate":1561115135,
                                                            "MessageTypeId":1,
                                                            "EventTypeId": 1              ,
                                                            "Parameters":[
                                                                           {
                                                                                          "TypeId": 1,
                                                                                          "Value":93.0
                                                                           },{
                                                                                          "TypeId":2,
                                                                                          "Value":0
                                                                           },{
                                                                                          "TypeId":3,
                                                                                          "Value":4153344.0
                                                                           },{
                                                                                          "TypeId":4,
                                                                                          "Value":1
                                                                           }
                                                            ],
                                                            "Position":{
                                                                                          "Latitude":29.026450994783758,
                                                                                          "Longitude":-98.360950751417988,
                                                                                          "Altitude":0.0,
                                                                                          "Quality":0
                                                            }
                                             }
                              ],
                              maxMessageId: 12,
                              isLimited: false
               }
}

5. Device state to a date

Can be requested for single device - /GetDeviceStateUpToDate with required parameter- deviceId

or for all devices using /GetDevicesStateUpToDate both requests have required parameter - upToDate - integer, Unix time, UTC/GMT – message Date. Device state is built for latest message Date < upToDate

Single device request has payload with single status object and all devices requested will have array of status objects.

Status object will have:

“DeviceId” – integer – Id of Device

"MaxMessageId" - integer, max messageId with Date < upToDate

"Parameters" – this section has the same structure as message parameters but contains all possible device parameters

"Position" - has the same structure as message Position.

Parameters and Position sections can be omitted if device did not send position or parameters up to upToDate

Samples:

For single device

               {
                              "result":0,
                              "payload":{
                                             “state”: {
                                                            "DeviceId": 23,
"MaxMessageId": 23,
                                                            "Parameters":[
                                                                           {
                                                                                          "TypeId": 1,
                                                                                          "Value":93.0
                                                                           },{
                                                                                          "TypeId":2,
                                                                                          "Value":0
                                                                           },{
                                                                                          "TypeId":3,
                                                                                          "Value":4153344.0
                                                                           },{
                                                                                          "TypeId":4,
                                                                                          "Value":1
                                                                           }
                                                            ],
                                                            "Position":{
                                                                                          "Latitude":29.026450994783758,
                                                                                          "Longitude":-98.360950751417988,
                                                                                          "Altitude":0.0,
                                                                                          "Quality":0
                                                            }
                                             }
                              }
               }

For all devices:

{
                              "result":0,
                              "payload": {
                                             “states”: [
                                                            {
                                                            "DeviceId": 23,
"MaxMessageId": 23,
                                                            "Parameters":[
                                                                           {
                                                                                          "TypeId": 1,
                                                                                          "Value": 93.0
                                                                           },{
                                                                                          "TypeId": 2,
                                                                                          "Value": 0
                                                                           },{
                                                                                          "TypeId":3,
                                                                                          "Value": 4153344.0
                                                                           },{
                                                                                          "TypeId":4,
                                                                                          "Value":1
                                                                           }
                                                            ],
                                                            "Position":{
                                                                                          "Latitude":29.026450994783758,
                                                                                          "Longitude":-98.360950751417988,
                                                                                          "Altitude":0.0,
                                                                                          "Quality":0
                                                            }
                                                            },
{
                                                            "DeviceId": 24,
"MaxMessageId": 26,
                                                            "Parameters":[
                                                                           {
                                                                                          "TypeId": 1,
                                                                                          "Value": 93.0
                                                                           },{
                                                                                          "TypeId": 2,
                                                                                          "Value": 0
                                                                           },{
                                                                                          "TypeId":3,
                                                                                          "Value": 4153344.0
                                                                           },{
                                                                                          "TypeId":4,
                                                                                          "Value":1
                                                                           }
                                                            ],
                                                            "Position":{
                                                                                          "Latitude":29.026450994783758,
                                                                                          "Longitude":-98.360950751417988,
                                                                                          "Altitude":0.0,
                                                                                          "Quality":0
                                                            }
                                                            }
                                             ]
                              }
               }

6.      Refresh token API token expires after 1 year. Before a token expires – new tokens can be generated for next 1 year period by request /RefreshToken Old token will not valid

Sample

               {
                              "result":0,
                              "payload": {
                                             “newToken”: “zzxxcc…”
}
}

• Go to: https://www.fleetistics.com/login/ Enter your credentials and login.      

• On the left side menu click on FLT Control Panel. Click on FLT Account Admin.      

• In the search bar enter the name of the account, (1) and then click on the name (2) to open the administrative options for that account.

• Choose the Users option which is the third option down.       On the right-hand side of the page click on Create User.       Enter the user information, ensuring the fields with asterisk's are filled out.       Under the Account section, make sure that the Status field is set to Active, and the Account Type is set to Customer.       For customers these settings should always be chosen and should not be changed.       For Geotab users scroll down to the bottom right hand corner and click on Save. NOTE: For Geotab users nothing else needs to be done. Do not make any changes in the Geotab section and leave the password field blank. If this is not done it may cause login issues.         Once saved, look for the user you just added and choose the desired permissions.      

The Fleetistics API service takes data from various GPS devices and normalizes it. The normalized data is then shared via API. This can be done for GPS devices sold and serviced by Fleetistics as well as any IoT devices from other providers. There are several advantages to this approach.

• Data from multiple GPS/IoT platforms can be assembled into one user interface. This is especially helpful when transitioning from one GPS platform to another. It can also provide a cost advantage by getting a lower rate for specific applications while maintaining the primary system.
• As devices and protocols are added, the API from Fleetistics will change less often. Normally the API is specific to a protocol and there can be multiple protocols with one manufacturer. Fleetistics will learn the protocol, do the integration and normalize the data so it is available through the APIs.
• A customer that only has a need for the data does not have to buy a GPS platform to get the data. Fleetistics can decode data directly from an IoT device, process it and delivery it to a customer which is only interesetd in the data which they will put in their database. Decoding and processing data requires a lot expertise and infrastructure many companies are not prepared to fund or develop due to cost and skills needed. For example a rail company may track their rail cars using an existing platform but wants to add GPS tracking to the platform. They need GPS data but they do not need an interface. Fleetistics can process and deliver the data for a fraction of the cost of bundling the GPS data with a platform or UI. Fleetistics can also provide a data plan to go with GPS units if needed.

There are many ways to create a support case. It is highly recommended that you create a support case for all important issues and even for less important issues. By creating a support case, the Fleetistics support team will be able to research the issue and get back to you instead of having to spend time on the phone, playing phone tag or exchanging emails. Support cases are updated in MyFleetistics>Account>Cases and each party is notified when an update is made. There is no need to call for a status update as it will be shared in the case notes. If you just want to talk something through, feel free to give us a call. Cases can be created for anything from a GPS device issue, billing question or feedback on the platform. Check out the list of topics covered by our custom developed support platform.

1. Quick Case - Click on the cross in the top right corner of any window. Item #3.

2. When reviewing cases you can create a new case by clicking the button. #2. Create a case for each device serial number as they are handling individually by support.

3. From the Device Status table, click the case icon on the right.
 

Quick Case & Case Administration View

Device Status Table (Analytics>Device Status)

Account>Cases

1. Click the circle to filter list below.

2. Click to create a case with specific device information included

Support Case Options

Open a case from any window. #1

View the status of your devices. #2

Groups in MyFleetistics are independent of the various GPS systems available. This offers customers the flexibility of controlling security in MyFleetistics differently than what is done inside one or more GPS systems a customer may be utilizing. Groups in MyFleetistics are much quicker to set and do not impact how information is accessed or distributed in the GPS system.

Click the link below to watch a video to give you an overview of GPS tracking, telematics and engine diagnostics information.

Video Presentation 34:11 PowerPoint presentation on GPS tracking, telematics and diagnostics

MyFleetistics Password is Not Working

• Select Reset Password on the login screen. (www.fleetistics.com/login)
• Ensure your password meets requirements for complexity.
• If can log into MyFleetistics but not Geotab or Fleetistics LITE, you can change your password from your profile. Click on your name in the top left corner. Select Reset Password and follow the steps. (Hint - Selecting Forgot Password is much easier)

Geotab and Fleetistics LITE Password is Not Working

• Both systems use the same password as MyFleetistics. The MyFleetistisc password is passed to the GPS platform but the GPS platform cannot pass back any changes for security. Therefore, only change your password in your MyFleetistics profile (click your name in the top left) or choose Forgo Password on the Fleetistics login page. (www.fleetistics.com/login)
• Ensure your password meets requirements for complexity. This may have been set by your Geotab account administrator under Administration>Services
  

Fleetistics ONE Passowrd is Not Working

• Submit a support ticket to have it reset
• Before logging in press Ctrl + F5 on your keyboad and delete your cookies

Reset Email Not Received

• If you do not receive the password reset email, check your email spam and junk folders and have your IT department white list fleetistics.com and myfleetistics.com.

If you are unable to login into your MyFleetistics account from the Fleetistics.com website, follow these steps. Only change your password in MyFleetistics, never in the GPS system.

Routine Fix:

1. Ensure your GPS program manager has submitted your name, email and security level to Fleetistics and the profile is active.  If it is not, it can be submitted by opening a support ticket from the Help Center>Support>Cases menu or by having the GPS program manager email support@fleetistics.com.  We must have the request from your GPS program manager for security. All other requests will be declined.  The support case will be updated in this location for your convenience.
2. Ensure you are using a supported web browser and clear the browswer cache (history) to delete any "memorized" information for this URL. Click the link to view browser details. http://www.fleetistics.com/browser-help.php
3. Add Fleetistics.com, myfleetistics.com and mygeotab.com as exceptions to browswer your popup blocker.
4. Follow the Forgot Password steps by going to www.fleetistics.com. In the top right corner of MyFleetistics click on Customer Login. On the login popup window select Forgot Password and follow the steps. If you do not receive the password reset email in a few minutes check your junk mail and ask your IT person to white list fleetistics.com, myfleetistics.com and mygeotab.com.

If these steps fail please submit a case through MyFleetistics>Help Center>Support>Cases. Our support team will review all settings and contact you to help resolve the issue. By submitting a case in this manner you will avoid benig on hold or leaving a voicemail and it allows us to review the situation and get back to you with a resolution.

 How to access the Forgot Password function.

How to add a new user in MyFleetistics (customers)

Purpose: This article provides instructions for adding a new user to MyFleetistics.

Procedure: 

1. Log in to MyFleetistics.
2. Click the Accounts option(1).
3. In the Account menu, click the Users option(2)
4. In the User window click, the Create A User in the upper right corner(3).
5. In the New User window, enter a username, first name, and last name in the fields provided. The username should be a valid email address. A valid email address ensures the welcome email containing the link to set a password is received. Only complete the fields specific to your GPS system. For example, listed systems include Geotab, Fleetistics Lite, Fleetistics One. Only fields associated with your system should be completed.
   

Additional Note: Please do not hesitate to open a support case is assistance is needed. The link below contains instructions for creating a support case. https://www.fleetistics.com/support-cases-made-easy/. 

All account and device changes must be submitted using a MyFleetistics.com support case. This process documents the date, time, user, and request. It protects you and Fleetistics from any misunderstandings. 

Click here  to Login To MyFleetistics Portal For System & Account Access

Video Instructions

https://youtu.be/uydQkUhbTSg

Toggle the service on or off on the left side. Billing will start automatically after the trial period expires at the rate listed. You can end these services at any time, without penalty, at the start of the following month. Refunds are not issued for partial months service.

The Fleetistics Fuel Card is accepted at 90% of retail fuel locations throughout the U.S. Plus, additional acceptance at over 45,000 service merchants nationwide. For a full list of participating locations, visit www.wexinc.com/accepting-locations.

Insert card, driver is prompted to input driver ID number specific to each card & odometer reading. Accurate ODO is important to getting accurate reports.

Fleetistics is able to connect fuel and vehicle data when a fuel card is used for a single vehicle as identified in your MyFleetistics account. If a card is moved from vehicle to vehicle the data will not be accurate.

To associate the fuel card to a vehicle navigate to MyFleetistics>Account>Devices and click the edit icon on the right.

Customers may choose their own 4-digit Driver ID number, or WEX can randomly assign the Driver ID. Assigning each driver a unique identification number ensures accurate reporting of driver purchasing behavior and a higher level of control.

Contact WEX customer service directly for questions about your account.

The Fleetistics Fuel Card offers an online portal for its customers to easily manage their accounts online. Once enrolled online, you can login any time to:

• Add or delete cards and drivers
• Access transactions as they post to your account
• Set limits online across fuel, service and merchandise for enforcement of purchasing policies
• Receive an email when a transaction falls outside your purchase guidelines

Customer Service representatives are also available 24/7 to help answer your questions.

The authorized WEX fleet contact can order replacement cards by logging on at www.wextools.com. The fleet manager may also call WEX Customer Service to report lost or stolen cards.

The customer is responsible for all fuel card changes and account management issues. Customer service is provided directly by WEX and Fleetistics has no access to a customer WEX account. The authorized fleet contact can add or delete cards by logging into www.wextools.com. The fleet manager can also call Customer Service at 800-761-7181 to terminate or add a driver/ vehicle.

For new fleets and overnight mail requests, card orders received before 3:30pm Eastern Time will ship same day. All cards ordered for regular shipping will ship next day.

To create a new WEX account you must use the Fleetistics WEX account application. http://fleetistics.com/fuel/ in order for us to be able to connect your fuel data to your GPS data. *The WEX account setup process is generally very slow. Please allow for several weeks for this process to be completed by WEX customer service.

A $40 application fee is added to the first invoice, after which the cost is $2.00 per month, per vehicle and a small transaction percentage.

Contact your account manager. There is not price advantage getting an account directly from WEX. If you do not get your account through Fleetistics you will not receive convenient reports and views in your MyFleetistics account.

To apply today, fill out the Fleetistics Fuel Card Application or for more information on the program, call 855.671.5013855.671.5013

WEX will generally handle all customer service. Fleetistics uses the data received from WEX to create new helpful reports and dashboards.

Customer Service:1-888-387-5665

Fax: 888-387-5665

Fax Application: 813-991-7765

Pay by Phone: 800-395-0809

Drivewyze Fleet Management 

Category:  Drivewyze

Purpose: This article will go over the basics of how to synchronize your fleet with Drivewyze and edit any information on the Drivewyze tab.

Procedure: From the left-hand side menu in Geotab click on the Drivewyze tab(1), From this interface, you will be able to access the vehicle, driver, and fleet details. You will also be able to manage the Drivewyze subscription levels and edit any incorrect/missing information. The vehicles and drivers tabs show you a table of the fleet information that has been synced. Select the edit icon(blue pencil)  to view driver details or view and modify vehicle details(2). 

Additional Note: If you are having any issues, please open a support case for further assistance. The link b

Drivewyze Fleet Management 

Purpose: This article outlines the process to synchronize your fleet with Drivewyze and make any necessary edits.

Procedure: 

1. Click Drivewyze in the left menu(1).
2. From this window, vehicles, drivers, and fleet details can be edited. Options associated with Drivewyze subscription levels are also available.
3. Click the Vehicles and Drivers tabs for additional options.
4. Click the edit icon (blue pencil) to access driver and vehicle options (2). 

Additional Note: If you encounter any issues, please open a support case for further assistance. The link below contains instructions on how to create a support case. https://www.fleetistics.com/support-cases-made-easy/.  

Each mobile user must be added through the web portal before they can log into the mobile app. You will receive an email with the mobile phone number and pin number created in the web portal. After installing the mobile app, enter this information and you will be connected to your account. vice.

For Android:

1. Click the Play Store icon on your device
2. Click the search icon and type “doForms”
3. Click “Install”
4. Open the doForms app
5. Select “Connect to Existing Account”
6. Select “Mobile Number/PIN ”
7. Enter the Mobile Number/PIN provided above

For iOS:

1. Click the App Store icon on your device
2. Click the search icon and type “doForms”
3. Click “Install” (the cloud icon)
4. Open the doForms app
5. Select “Connect to Existing Account”
6. Select “Mobile Number/PIN ”
7. Enter the Mobile Number/PIN provided above

Please contact your doForms group administrator if you have any questions