Thank you for taking your time to dive into this!
Do I understand correctly that ‘priority’ on a service is more a ‘suggestion’ than a ‘requirement’?
I do not understand your remark: ’ we need to elaborate how to enforce that prio 1 jobs must be assigned’. Are you suggesting there is way to enforce a ‘hard assign’ or that you need to alter the algorithm to force a ‘hard assign’?
Let me just explain how we would like to implement route optimization. Shipment requests are gathered from customers and at data-entry a delivery date is assigned (soft) usually 14 days in advance. At the end of the day all future delivery dates are presented to Route Optimization. Shipments which had not yet been assigned but do fit in a route are given a ‘hard deliverydate’. The customer gets a message confirming the deliverydate.
As long as the deliverydate is still more than two businessdays in the future we really do not care which vehicle on which route is assigned the shipment. As long as it stays on the previously ‘hardened’ deliverydate seeing that optimization has previously suggested the shipment ‘fits’.
In the next days more shipments can be added to the same delivery date. And Route optimization should check if the shipments stil ‘fit’ even with the new shipments added.
If a (new) shipment does not fit we message the planner a different deliverydate has to be assigned to the shipment. In that case the customer does not get a message confirming the deliverydate.
We have seen that adding a single shipment to an existing delivery date can ‘mix up’ the previous routes; shipments are reassigned to other vehicles and vehicles get new routes. Thats fine We just need to know if the shipments will fit.
In essence, what we are looking for is a ‘hard’ assign. Even if this means the routes are not optimal, given the shipments.
Thinking about this I think we are looking for new objective. ‘Do the new shipments (with a low priority) still fit on the given day, given already assigned shipments (with a high priority)’.