Note: The visibility index applies only to road transport. For intermodal transport involving rail and/or ferry segments, the index may not be accurate.
The Visibility Index is a single score measuring how effectively a transport was tracked in real-time. This score ranges from 0 to 100%, where 0 indicates severe problems that prevented real-time visibility, while 100 means all tracking functioned perfectly. The score is calculated after the transport tracking ends.
This index consists of several components (see below), each representing a potential issue.
The component with the biggest issue is highlighted as the main visibility issue, guiding you on which issue to address first.
Disclaimer: Use the Visibility Index with caution, as multiple factors can affect tracking accuracy. The severity of tracking issues doesn't always directly correlate with the Visibility Index score. A low score may not be problematic depending on your specific Visibility goals and context.
If you have any questions, please contact support.
Visibility Index Components
The following components contribute to the overall index calculation.
However, in certain scenarios, the total index score will always be 0%:
Missing stop visits where no stop has been visited
⚠️ Missing stop visits
Definition: The ratio of unvisited to visited stops.
Example: If 1 out of 2 stops are visited for a transport, then this issue component is 50%.
How to improve:
Stop sequence → Verify that the transport-level stop sequence is correct by aligning transport plans with actual execution. Check for frequent "Stops visited in different sequence" warnings.
Data reception → Check if GPS data or events were received for the stops. If not, identify the data provider and examine the transmission process.
⚠️ Vehicle/tracking data received too late
Definition: Vehicle allocation was received too late to provide real-time visibility for the entire transport duration. This component's score is calculated by comparing the allocation time to the transport's start time and total tour duration.
Example: If vehicle allocation happens 3 hours into a 10-hour transport, the component score would be 30% (we cannot provide real-time visibility for the first 3 hours, which is 30% of the total transport duration).
How to improve: Provide the vehicle allocation as early as possible, ideally before the vehicle approaches the first stop of a transport.
⚠️ GPS data received too late
Definition: The GPS data was received too late, preventing us from providing real-time visibility throughout the entire transport timeframe. This component's score is calculated based on the allocation time in relation to the transport's start time and the total tour duration.
Example: If GPS data is received 3 hours into a 10-hour transport, the component score would be 30% (as we cannot provide real-time visibility for the first 3 hours, which represents 30% of the total transport duration).
How to improve: Provide the GPS data as early as possible, ideally before the vehicle approaches the first stop of a transport.
⚠️ GPS data received infrequently
Definition: GPS data is received too infrequently to maintain optimal tracking. We require at minimum 1 GPS ping per 10 kilometers (6.2 miles). Lower frequency creates what we call a "GPS jump." As jumps increase, the component score decreases.
Example: For a 200-kilometer (125-mile) transport with GPS jumps spanning 40 kilometers (25 miles), the component score calculates to 1-(40/200) = 80%.
How to improve: Depending on your GPS data source:
If using a GPS provider with Visibility: Contact your provider to investigate causes of inconsistent or infrequent data transmission.
If sending GPS data directly from your in-house system: Collaborate with your IT department to enhance the data stream.
⚠️ Early stop visit
Definition: The first stop was visited significantly before the defined timeslot. Tracking occurred retrospectively, not in real-time.
Example: A transport's first stop has a defined timeslot of 11:00–12:00. However, the vehicle arrived at the stop way earlier (up to multiple days), and tracking only began afterward.
How to improve: Ensure the first transport stop has an accurate timeslot that closely reflects reality.