Skip to main content

Hi Experts,

Is there a way we can move a Commited activity scheduled in PSO? 

I created Task 1267 as shown below and its commited to an enginner. Then Created an urgent task here 1269 with high base value that the same enginner must do then set a dependacy as well so that this urgent Task should be executed first to the same engineer.

 

But in PSO I can below message in the explanation and PSO here not moving this Commited task 1267 so that it can schedule 1269!

Is there a way we can force PSO move this first activity?

 

Thanks,

KM

Hi ​@KAMANUK 

Based on my understanding you cannot force the PSO DSE service to automatically move a committed activity (like your activity 1267) to make room for a new, more urgent task. The "committed" status signifies that a promise has been made to a customer and/or the technician has been dispatched. To maintain schedule stability and honor that promise, the DSE is explicitly designed not to automatically reshuffle committed work, regardless of the value of a new, incoming activity. When your urgent task (1269) arrives, the DSE sees the dependency and the high value. It tries to schedule it before activity 1267 . However, it cannot move 1267 because it is committed. If there is no available time slot before activity 1267, the DSE's only option is to leave the new, urgent task 1269 unallocated.

To get PSO to move the first activity (1267), a manual or external intervention is required. You must first "un-commit" the activity to give control back to the DSE. For example you can either.

  1. Manual Reschedule in the Workbench (Dispatcher Action):

    • A dispatcher can manually drag and drop the committed activity 1267 to a later time in the Gantt chart. This action effectively changes its fixed position, creating the space needed for the DSE to then automatically schedule the urgent task 1269 in the newly opened slot. assuming ‘AllowAllocatedbeforeCommited’ parameter should be enabled

  2. Change the Status via External Application:

    • Your external application (e.g., FSM or IFS Cloud) must send a CHANGE input to PSO that updates the status of activity 1267 back to a non-committed state status_id=0 (Schedulable). Once the activity is no longer committed, the DSE will regain full control. It will see the high-value urgent task (1269) with its dependency, and may correctly schedule it first, and then find the next best optimal time to schedule the now-flexible activity 1267.

Terms & ConditionsCookie settingsAccessibility statement