Or in other words, if it is possible to consider the current day (working or non working) before allocation of a task to a future shift date.

Hi @ERCJAGATH 

When an engineer is non-working does it still have a shift for that day which has been blocked by an unavailability? Or is there no shift at all. Alos would you be able to provide your current commit rules so I can see how you have things configured.

This may be possible to solve by configuring commit rules at a shift level for days when the resource is not working, superseding the resource’s commit rules.

Any questions let me know,

Thanks,

Kai

Hai @kai.parker 

As I mentioned earlier, engineer is non working(no shift) for today. He has working shift for tomorrow. When the dispatch is configured for next 2 days obviously PSO dispatches the task for tomorrows allocated date and time. But the issue is FT is non working for today and he is getting alerts saying task has been dispatched for tomorrow’s date. As per the working policy, the the task needs to be attended immediately once it is dispatched. Since FT is non working for today, then he cannot take that task immediately and task is left un-attended. So it is an additional work to dispatcher to re-assign the task to another working shift FT.

So is there any way we can restrict the dispatch, based on the current day non working condition of the engineer even though the actual allocated and dispatched date is for tomorrow’s working shift?

Please find my answers:
When an engineer is non-working does it still have a shift for that day which has been blocked by an unavailability?

Ans: Non working means no shift and it is for current day but he has shift and working day for tomorrow. no unavailability.