PSO committing jobs on the day - rule parameter

​@Alexander Heinze , I hope you are doing well. Could you please give us a hand with this question when you have a minute? Basically we would like to setup the committed rule so that only looks at the workload of resources in the current day. We think the rule is looking ahead withing the schedule window. So, we want the constraint of maximum amount of jobs = 5 to be applied only to the current day workload in the schedule. Please see committed rule setup in screenshot below. Many thanks

Hello.

I see the Send External Commits Mode is set to Manual in the Screenshot. The default value is NONE for this field. Was a test conducted where the Send External Commits Mode is set to NONE to see if it results in the desired outcome?

Hi ​@MIGDNA 

To build on what Werner mentioned earlier, here’s a brief overview the 2 rule parameters in question here, 

1. SendExternalCommitsMode

This parameter determines when the Suggested_Dispatch records are created. There are three possible modes:

• NONE: The default behavior. Suggested_Dispatch records are created based on the rules above.

• ALL: Every time an activity is committed or uncommitted, the Schedule Dispatch Service will create a Suggested_Dispatch record, provided the service did not originally suggest the dispatch.

• MANUAL: Only activities manually committed or uncommitted via the Scheduling Workbench will trigger the creation of a Suggested_Dispatch record. Manual commits are identified by Activity_Status.source = 1. Dispatches suggested by the Schedule Dispatch Service itself will have Suggested_Dispatch.source = 2. For external commits made via the Scheduling Workbench, Activity_Status.source will remain 1.

Note: The Schedule Dispatch Service will only look for activities with a "committed" status or lower. Activities set directly to "traveling" on the Scheduling Workbench will not generate a Suggested_Dispatch record.

2. Rule Window Start and Rule Window End

• Rule Window Start: Suggestions will only be made if the current schedule time has passed this specified start time. Setting this value to null indicates that there are no restrictions on when the suggestion window can begin.

• Rule Window End: Suggestions will only be made if the current schedule time is before this specified end time. Setting this value to null indicates that there are no restrictions on when the suggestion window can end.

Essentially, this is used to define a specific time window during the day when commit suggestions should be triggered by the DSP service. However, it does not limit commit suggestions to the current day— it simply means the rule will only be triggered within the defined time frame. If you want to remove any time restrictions, you can set both the Rule Start and Rule End Windows to null in the commit rule.

Hi ​@WernerC & ​@Sachitra_W 

Thank you for your comments. We have tested the Send External Commits Mode, and the manipulation of the Rule Window Start and Rule Window End does not help with the requirement.

The requirement is to have the Maximum Committed Activities parameter counting activities only during the current day. Unfortunately, we have learnt that this parameter is attached to the resource object, so it simple counts the Activities in status Committed or higher linked to a resource, in the past or in the future.