My Network app is available on all the OEM Plans and on the Fleet Plans Expand and Evolve.
You need to be an Admin or Fleet admin to see the overview in My Network app. You can read more about user roles here
Reading the Overview tab
My Network Overview displays important Key Performance Indicators (KPIs) that help you monitor various device statuses and settings. The KPIs are organized in cards in three different categories:
Device Connectivity & Data
Device Power
Device Configuration
To find the overview go to My Network app and select Overview.
Each card has configurable thresholds, warning limits, and device type coverage. Read more about the individual cards further down this article.
Note: A device needs to be installed and activated in order to be included as a KPI.
Understanding the Health Score
In the top right corner of the overview page you find the fleet wide health score. Each telematics device has a device health metric that is calculated based on factors considered critical for the device’s health and ability to deliver data. The device health can be either High, Medium, or Low. A high score means the device is fully functioning and that it reports data consistently.
A device will change health status from, for example, high to medium if at least one condition changes, such as “No data”, for more than 14 days.
Note: The Health Scores cannot be configured and they operate independently from any configurations made on a specific card. See how to configure a card here
See how the Health Score is assigned to a telematics device
| Low | Medium | High | Applicable devices |
No data | > 30d | > 14d | Default | All device types |
No location | - | > 30d | Default | All device types |
External power | - | < 5.85V (4.5V + 30% buffer) | Default | Only TU200/300/400/500/600 |
Battery level | < 3.5V | < 3.78V | Default | Only TU200/300/400/500/600 and Spot |
Battery level (Spot 2) | < 2.8V | < 3V | Default | Spot 2 |
No CAN data | - | When all conditions are true:
| Default | Only TU devices with a CAN profile |
Operating hours issues |
|
|
| Only relevant for devices reporting operating hours |
Reading the different cards
Device Connectivity & Data
No Data
Monitors the number of devices that have not transmitted any data for a certain amount of days. The threshold is configurable
No Location
Monitors the number of devices that have not transmitted a GPS Fix for a certain amount of days. The threshold is configurable
No CAN Data
Monitors the number of devices that have a CAN profile and have been operating after having the CAN profile assigned, but have not yet sent any CAN data.
Operating Hours Issues
Monitors the number of devices that have one or more issues with reporting machine operating hours, divided into the following metrics:
Hours fluctuating
This filter detects if the last received operating hours value from the device is lower than the previously recorded value - the operating hours decreased. Both CAN operating hours and input hours are included.
To filter out false positives, additional conditions are applied:
Number of data fluctuations needs to be greater than 1
Difference between previous operating hours value and next value needs to be greater than 30 minutes
Analysis period is 5 days.
Hours from CAN modified
This filter detects if the operating hours offset value has changed from default 0 to anything that is not 0 and CAN hours are detected.
A check is performed if operating hours was received from CAN message within 5 days. If not, devices are not included in the filter.
Hours from CAN not provided
This filter detects if operating hours are not being recorded from CAN, while the below conditions are met:
Device has CAN support
Device has assigned CAN filter which has operating hours included
It is checked if the CAN operating hours data is older than 7 days from last engine status update.
Reporting 0 hours per day
Device has operating hours value set to 0. In addition, device needs to be active.
Both CAN operating hours and input hours are included.
Analysis period is 5 days.
Reporting 24 hours per day
Device reporting more than 23.5 hours per day. To calculate this value all deltas between next operating hours values are summed together.
Analysis period is 5 days.
Device Power
No External Power
Monitors the number of devices where the latest message received from the device indicated that the external power was zero.
No Battery Power
Monitors the number of devices where the latest message indicated that the device internal battery level was too low. If battery level is 3685 mV or below, it counts as being “too low”.
The threshold is configurable.
Device Configuration
Firmware Updates
Only for OEM customers.
Monitors the number of devices that have a firmware lower than 63.00. Only considers device models TU500, TU501 and TU600.
No Encryption
Only for OEM customers.
Monitors the number of devices communicating with the IRIS gateway where no encryption has been negotiated. Devices are transmitting data unencrypted. This KPI is ignoring devices on the Zitcom gateway, since encryption is not supported on that platform.
Bluetooth Disabled
Monitors the number of devices where Bluetooth scanning is disabled. Only considers devices with Bluetooth support.
💡 Tip:
Need more help? Get support from the Trackunit Community
Find answers and get help from Trackunit Tech Support and Community Experts