Hi everyone,

We’re encountering a persistent issue with how Private Activities (PAs) are handled in PSO, and we’d appreciate any insights or suggestions.

Use Case:
Like most, we use Private Activities to indicate when a technician is unavailable. Up until the day of the appointment, everything looks fine—tasks are scheduled around the PA within their respective SLA windows.

The Problem:
On the day of service, when PSO assigns work early in the morning, it appears to ignore the SLA windows. Instead, it schedules all tasks to begin after the Private Activity ends, leaving the earlier part of the day empty—even if the tasks were originally meant to occur before the PA.

I believe we see the same issue with fixed assignments as well under certain scenarios.

Example Scenario:

• A technician has jobs from 8:00 AM to 1:00 PM (let say 4 one hour tasks), and a PA from 2:00 PM to 4:00 PM with his work day ending at 5pm
• Instead of correctly scheduling the tasks before 2:00 PM, PSO stacks them all after 4:00 PM, even pushing them past the technician’s workday.

Additional Complication:
This issue is worse for technicians who are drip-fed tasks. When tasks are pushed past the PA, it creates white space earlier in the day. The optimizer then fills that space with new work from other resources, only to later shift those tasks again—creating a huge mess.

Has anyone else experienced this behavior? Any workarounds or configuration tips would be greatly appreciated.