Visibility Hub provides tracking data updates in context of a specific transport by managing from and until which location and time the data is visible to all involved stakeholders.

As per this standard, vehicle tracking data - such as GPS positions or stop arrival/departure events sent from an inhouse system - are considered between the first and the last stop of a transport:

This means that tracking ends when the last stop visit was confirmed.

But sometimes, not everything goes right in tracking and not all stops can be tracked:

Problems with the GPS data submission or additional vehicles that are involved in the transport were not allocated and therefore, Visibility Hub is not able to track the last stop.

To capture these cases and to not have transports too long marked as "it's currently being tracked" while in reality, "the delivery already took place", Visibility Hub ends tracking after the latest timeslot ends and adds a buffer to it.

This buffer is shown as "tracking end time" for each transport and is dynamically calculated based on various factors like transport distance, timeslots, weekends and type of tracking data received and can vary between one and multiple working days.

The goal is to keep on tracking a transport as long as it's likely that it will still get tracking updates - for example when severe delays happen - but end tracking after that to reflect the actual execution state.

You can have a look at this article to learn more about the different transport states as well as the cancellation reasons that are applied in case of an premature tracking end.