Skip to content
QuantyDocs
Open Quanty

Telematics in the TMS

Positions on a map are only the start. In the TMS, telematics ticks off route stops by itself, gives each order its expected arrival and its real kilometres, builds the road cards, raises an issue when a truck stands too long, finds border crossings, moves the odometer forward and, with Inelo GBOX, shows how much driving time a driver has left.

Before you start

  • A telematics connection (see Connecting telematics).
  • The TMS vehicles must be linked to the vehicles your telematics reports (below). Positions sent through Your own system (API) link the vehicle by themselves.
  • Linking and importing vehicles needs the Fleet module for a member limited to some TMS modules.

In Vehicles and sets, the page menu has:

  • Link with telematics: pairs your TMS vehicles that have no telematics yet with the reported vehicles, by plate (compared in capitals, without spaces and dashes). The result, Fleet linked with telematics, says "Matched by plate: 3 linked now, 5 were linked before." and lists Vehicles with no telematics match and Telematics vehicles not in the fleet, with Add these 4 to the fleet.
  • Import from telematics: adds every reported vehicle that is not in the fleet yet, with its plate, type (a tractor when the provider does not say) and odometer. It skips "plate already in the fleet" and "no plate in telematics", and says "4 vehicles added to the fleet and linked with telematics." or "Nothing new to add: every telematics vehicle is already in the fleet."
Linking the fleet with telematics.
The result Fleet linked with telematics: Matched by plate with how many were linked now and before, the vehicles with no telematics match and the telematics vehicles not in the fleet

In People, Link to telematics pairs the people with the drivers your telematics reports, by driver card first and then by full name, only when the pair is certain.

Without telematics, the vehicles list says "No telematics yet." and "Connect GBOX, Webfleet, Samsara, Frotcom or Eurowag to see live positions, kilometres and border crossings." with Connect telematics.

Stops and delays from GPS

  • Route stops from GPS (on by default): when your own truck comes within the Arrival radius (500 m) of a loading or unloading place, the stop becomes arrived and, when it leaves, done; the order moves to in progress and delivered by itself.
  • Long stop: a truck on an order standing still (under 3 km/h) twice as long as A stop counts from (15 minutes by default), away from a planned place, raises an issue.
  • Delays: an expected arrival after the unloading window shows the order under Late in Tracking and in Issues.

These are set in Automatic actions.

ETA

Each order on the road gets an expected arrival in Tracking:

  • ETA from the truck's own computer ("from the truck" on the vehicle board): when the truck's own computer reports one (today Inelo GBOX, while it works on an errand), its position is younger than 15 minutes, the ETA is not more than 10 minutes in the past, and the order is the tractor's first own-fleet order in progress.
  • Otherwise ETA estimated by Quanty from the last position.

Kilometres, road cards and border crossings

  • An order's kilometres come from GPS once the truck has driven it ("from GPS so far" while it is on the road; "No GPS trail for this order yet." before). After delivery they are read again for 12 hours.
  • Road cards: "GPS km, orders, fuel and border crossings of the vehicle in one period." "The card builds itself from GPS, orders and fuel cards." See Road cards and the VAT mileage log.
  • Border crossings come from the position history and feed the Border crossings, Driver month and Vehicle month reports (see TMS reports).

The vehicle board and the odometer

  • Tracking, Vehicles shows every tractor with its position ("12 min ago", amber after 2 hours, "No position" without one) and, from GBOX, "3 h 20 min of driving left" with "read 25 min ago". See Tracking.
  • The TMS vehicle's odometer moves forward with every new reading, never back. Readings of 0 or above 5 000 000 km are ignored.
  • Samsara also sends vehicle readings (such as fuel, AdBlue, battery, engine hours and fault codes) for the vehicle's health card.

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:

  1. For a driver linked to a person in People, Quanty keeps one row per driver and day, under the provider's name. Readings of drivers who are not linked are not kept.
  2. The person's Working time tab shows Now (Until the break, Driving left today, Driving left this week, Daily rest in, Weekly rest in, Extensions to 10 h left, Reduced daily rests left, "Read from telematics (Inelo GBOX) at 10:42", An old reading after 6 hours) and The last 28 days.
  3. "Driving time comes from the remaining times telematics reports: an estimate, not the tachograph record." "Working-time days are kept for 12 months, then deleted."
The Working time tab of a person.
A person's Working time tab: Now with the times left, the last 28 days, and Tachograph files with Upload DDD files

TMS settings, Connections, Drivers and routes has the switch Keep drivers' working times: "The remaining driving and rest times your telematics sends are kept on the vehicle (personal data of the driver). Off: only the daily summary is kept." It is off by default and only admins change it ("Only organization admins change this."). Switching it off removes the kept times from the vehicles at once. The daily rows on the person and the driving time on the vehicle board stay. See TMS people, trips and working time.

Tachograph files (DDD) are uploaded on the person's and vehicle's cards; Quanty keeps them with their deadlines and does not read their contents.

Working times are personal data

The driving and rest times of a driver are that person's personal data. Keep the switch off unless you need the times on the vehicle.