General definitions from Transpoco's system
Here you can find some concepts / definitions from your SynX product.
Index:
From the Core System:
1) Device updates
Send updates every 500m distance moved
OR after 60 seconds with ignition on
OR if direction change of more than 35 degrees
Device updates every 1 hour with ignition off
Devices goes into sleep mode after 4200 seconds (1.1hours)
In sleep mode GPS and GSM turns off.
Device will wake up every hour while ignition is off and try to send update.
Note 1: We can custom how often the tracker updates eg. 30s.
Note 2: The deep sleep mode turns off the modem and gps about 10 minutes after the ignition goes off. The modem and gps wake up every 1 hour and try to send data.
2) The Heatmap
The heatmap displays in different colours the places where fleet vehicles were driven most part of the day. The system considers since midnight of the current day.
3) Data storage capability without data connection
About 10000 updates approx 80hours of driving without data connection.
4) Driver ID settings
Driver id with buzzer is enabled
Driver deregistration (logout) time is 3 mins
Buzzer will beep for 3mins if no login
5) Unit Down: indicates that the tracker in the vehicle has stopped functioning and has not sent an update for over 7 days.
Yellow Pin on the Map: indicates that the tracker in the vehicle has stopped functioning and has not sent an update for over 12 hours.
Note: Check if the vehicle does not have a dead battery or a master switch engaged. If not, please reach out to support for help.
6) Private Mode
When the vehicle is in private mode and the engine is turned OFF, the vehicle remains in private mode. Once the engine is turned ON, the driver will have a few seconds to remain in private mode if he uses the related fob during the beeping time. Otherwise, the vehicle will be back to business mode automatically.
7) Tracker events considered for Journeys, Alerts, etc
We only consider tracker events with the number of satellites >=5. If the satellites are lower than 5, we disconsider that event.
8) The 3/4G technology
The Eco4 unit is eligible but not the FMT100 is GSM based technology.
From the Alerts Section:
1) Speeding in Zone
For this alert you need to specify exact the speed limit you want to target (eg 30km/h or 50km/h or 80km/h etc) and add an alert for this limit.
Eg speeding in zone = 30 and speed above road limit >3
In this example, you will just get alerts if the vehicle is over 33km/h in a 30 zone.
2) Day parameter in the Alerts section
The system considers each day of the week as a sequential number like 1, 2, 3...with Saturday being number 6 for instance. When we set an alert to less than Saturday, it means less than 6 so the system will ignore Saturday and Sunday on these alerts.
From the Driving Style Module:
1) Rapid Acceleration
Ruptela devices: Events are set to trigger if the next event is above 6m/s/s (increase of 21.6km/h in 1 second)
Teltonika devices: Events are set to trigger if the next event is above 2.8m/s/s (increase of 10 km/h in 1 second)
Harsh Braking
Ruptela devices: Events are set to trigger if the next event is below 6m/s/s (decrease of 21.6km/h in 1 second)
Teltonika devices: Events are set to trigger if the next event is above 2.8m/s/s (decrease of 10km/h in 1 second)
Harsh Cornering
Ruptela devices: Events are set to trigger if the next event is above 6m/s/s (increase of 21.6km/h in 1 second) when cornering
Teltonika devices: Events are set to trigger if the next event is above 2.8m/s/s (increase of 10km/h in 1 second)
2) Road speed records and GPS accuracy
To check the speed limits we validate the GPS speed received from the tracker against OpenStreetMaps and Here maps.
We also manually check about 1000 speed alerts against Google Maps Street View per quarter. This is from where the 99% accuracy comes.
Our trackers GNSS accuracy depends on radio signals from three satellite networks (GPS ,Glonass,Galileo).
GNSS doesn't work indoors and the GNSS antenna needs to be placed facing the sky to receive a good signal.
We filter out any low accuracy data based on the number of satellites seen or limited section of the sky viewed (HDOP)
US government GPS accuracy data
here
Difference between Driving Style % Speeding Events and Alerts set for speed above road limit:
1.
2.
3.
From the Fuel Module:
1) Carbon Footprint (Kg)
The total is calculated by multiplying the total number of:
refill petrol litres by 2.3kg
refill diesel litres by 2.7kg
refill CNG kilos by 2.4kg
refill Electricity kWh by 0.2958kg
2) Fuel Transactions reprocessed by stations created/edited
When creating/editing a station in the system, all transactions within a period of 3 months will be reprocessed.
3) Formula used to calculate the fuel consumption (l/100km or mpg)
((fuel quantity / distance between refills) * 100, unit)
From the Walkaround Module:
1) WA alert threshold
Speeding above 30km/h
2) Services created from the Walkaround Module as per defect reported by the driver
When we manually create a service from the walkaround module as an action of a defect reported, the system set it as due by default on the day of its creation. It means the schedule is set for today's date which is the date of its creation.
3) Completion x Received Time of the Checklists Done
Completion time of the checklist - is the time of the last checklist question answered.
Received time of the checklist - is the time when Transpoco's server receives the checklist done.
We record these different times as the Driver App can be used in an offline mode which means the driver can complete the checklist without submitting it or can click to submit it but there is no internet connexion to send the checklist at the time. In this case, the app will hold until having proper connexion to send it.
From the Cameras Module:
1) Alarms set with Video Evidences
Driver Smoking, Fatigue Driving and Driver Making Calls.
2) Speed and Location on Cameras
If we have GPS signal on the camera we should get speed and location from it.
Asset Tracker:
1) TAT100 (from Teltonika)
It's set for 1 pin a day. We can't change this at the moment.
