Telematics (GPS)

Telematics brings your trucks' GPS into Quanty. An admin connects your telematics account once, and Quanty reads every vehicle's position, plate and driver on a schedule: you see the vehicles live on the fleet map, a Vehicles table can keep itself current, and the TMS uses the same data to tick off route stops, give orders their expected arrival and real kilometres, build road cards and find border crossings. Quanty only reads from your provider; it never writes to it.

Before you start

• Telematics is part of the TMS add-on. Without it, the Telematics card in Integrations says "Part of the TMS add-on. Contact Quanty to switch it on."
• Only organization admins connect or change telematics accounts. Who sees the vehicles is explained in Who can see positions.
• You need the API access details from your telematics provider, or a system of your own that can send positions.

How it works

1. Connect. In Integrations, Telematics (GPS), an admin picks the provider, enters its access details, chooses where the positions go (a table or the map only) and how often Quanty asks (every 5 to 60 minutes). Quanty tests the access details before it saves anything. See Connecting telematics.
2. Read. On every sync Quanty asks the provider for the vehicles, stores the last position of each and a route point when it moved, and updates the table.
3. Show. The fleet map refreshes every 30 seconds; a vehicle's detail draws its route of the last 6 hours to 3 days. See Positions and the fleet map.
4. Use. The TMS links its vehicles to the reported ones and uses the positions for stops, ETAs, kilometres, road cards, long stops, border crossings and the odometer. See Telematics in the TMS.

Providers

Cartrack and Geotab are Planned; Tell us you need this asks Quanty for them. An organization can have up to 10 connections.

Who can see positions

There is no separate telematics permission. A vehicle's position follows the access to where the connection writes it:

• With a destination table: whoever can read that table sees its vehicles, exactly like any other row. Others see "Some vehicles are not shown: positions follow the access to the table they are written to."
• With no destination table (map only): only organization admins see the vehicles on the fleet map.

A company car assigned to a person makes its location history that person's location history (see Assign a company car to a person).

Drivers and working times

A provider that sends the driving and rest times of the driver whose card is in the tachograph (today Inelo GBOX) feeds the TMS. For a driver linked to a person in People, Quanty keeps one row per driver and day, shown on the person's Working time tab (see Cabotage, return to base and tachograph files), for 12 months. These times are an estimate, not the tachograph record. The vehicle board in Tracking shows the driving time left.

TMS settings, Connections, Drivers and routes has the switch Keep drivers' working times (off by default; admins change it): with it on, the remaining driving and rest times are also kept on the vehicle. These are the driver's personal data. See Drivers and working times.

What a connection keeps

• Position history is kept for 90 days, then deleted; the syncs of a connection for 30 days.
• The token or password is stored encrypted, used only to read your vehicles, and cannot be shown again, not even to admins.

Related pages

• Connecting telematics: providers, the wizard and the connection row.
• Your own system (API): sending positions from your own system.
• Positions and the fleet map: the map, routes, the Vehicles table and who sees what.
• Telematics in the TMS: linking the fleet, ETAs, kilometres and working times.
• Tracking and the vehicle board: orders on the road with their ETA, and every tractor live.
• Fleet map and Map view: maps of any table.
• Integrations: the hub the Telematics card sits in.