Skip to main content

Good day

 

We started using PSO to schedule tasks yesterday. Everything was working correctly with tasks committing according to the commit rules, and newer tasks coming in and sitting the queue with “Allocated” status. A day later, and a lot of tasks that were allocated became unallocated, even though their SLA is still active, with plenty of room on the schedule to commit these tasks. The Current Allocation Value also changed to zero, where it should not be zero, but have an allocation value in accordance with the SLA. Please see the screenshot below:

Previously Allocated task now Unallocated while SLA is still active

Any help with this issue would be appreciated, or any ideas for where to start investigating.

The current allocation value would always be showing as 0 if the task is unallocated, which it is in this case if I’m understand it correctly.

What does PSO say is the reason for these tasks being unallocated? Could you check what is being given as the reason in the exception panel?

Thanks for the reply.

 

The reason it gives is : Reason: The current plan does not schedule this activity. This does not make sense as there is ample space in the schedule to schedule the task:

 

The tasks also come through as allocated, and is then changed to unallocated shortly after.

Problem with tasks changing status from Allocated to Unallocated even with Resource availability and active SLA’s, has been resolved.

A PSO parameter was changed; the HTM is an older version that needs to be upgraded. This was causing intermittent glitches until it was the parameter was changed to Straight line.

 

PSO Parameter was changed - TravelCalculationOption change from HierarchicalTravelMatrix to StraightLine

 

Reply


Terms & ConditionsCookie settings