This article explains the context of the "Allocated license plate is not an integrated vehicle" warning, why it’s shown, whether it's a problem from a tracking point of view and what you can potentially do about it.
Context
Visibility Hub supports two ways of vehicle/license plate allocation:
License plates, which are received from telematics connections and represented as vehicle entities in the system and
License plates, which are received as a metadata on top of visibility data provided for a transport.
To learn more details about that, see here.
Why is this warning shown?
The license plate allocation itself can be done
a) directly in the Visibility Hub application or
b) via any other supported/connected application or interface.
In case of a), the warning can’t be triggered as only vehicles available in Visibility Hub’s vehicle pool can be allocated.
In case of b), if the intent of the license plate allocation was to find a matching vehicle in Visibility Hub's vehicle pool (see scenario 1 above), but it wasn't found, this warning is shown.
Is it a problem for tracking?
It depends:
It is not a problem as long as data is sent for this vehicle (see scenario 2 above) in time (latest at the start time of the transport, which is usually the start of the timeslot of the first stop).
It is a problem if still no data is received after the start time of the transport.
What can be done about it?
First, get in touch with the party who's responsible for providing the visibility data for the transport. Next, try to figure out in which way this party is providing the license plate allocations (see Context section above) to Visibility Hub.
If it's (1), then the missing vehicle needs to be made available for Visibility Hub, which usually means to get in touch with the telematics provider.
If it's (2), try to evaluate why no visibility data was provided for this transport.