Vellox Group Ideas Portal
Currently, an asset availability/location snapshot is created when a trip is assigned using the "Search Closest" function. However, there are several other workflows and assignment windows within the system where vehicles can be assigned without generating the same snapshot.
It would be beneficial if an asset availability/location snapshot were automatically created whenever an asset is assigned to a trip, regardless of the assignment method used. Capturing this information consistently across all assignment workflows would provide a more complete record of resource availability and support retrospective review of assignment decisions.
Thank you for this idea! We wanted to follow up with some context.
We've previously made an enhancement so that an asset availability/location snapshot is recorded not only when "Search Closest" is used, but also at ticket creation and at asset launch; the goal being to ensure a snapshot is available for review even when Search Closest wasn't the method used to find or select the asset.
If you're still seeing cases where an assignment doesn't produce a snapshot, we'd like to dig into that further. Could you let us know which specific assignment method(s) or window(s) you're using when this happens (e.g., drag-and-drop, Time View, a specific assignment dialog)? That will help us confirm whether there's a genuine gap remaining versus something already covered, and if there is a gap, we can scope it properly.
Thanks again for flagging this — it helps us make sure resource availability records stay complete and reliable for retrospective review.