We have a client with Cloud, using Cloud, PSO, and MWO and wants technicians to have visibility on mobile of all work allocated for the day. As emergency jobs arise, these should auto‑schedule immediately, removing the lowest‑priority allocated work from the technician’s schedule if it is already full. Emergencies must always be scheduled as the next job and must never be removed once allocated. At the end of the day, any remaining work should automatically unschedule and return to the pool for future allocation.
The challenge is that providing technician schedule visibility on mobile typically requires an all‑day commit rule, which prevents emergencies from auto‑allocating and displacing lower‑priority work. Alternatively, not using a commit rule and assigning work in Cloud can provide MWO visibility, but introduces the risk that PSO optimization may change the technician’s schedule, reducing schedule stability.
This creates a conflict between technician schedule stability, emergency job prioritization, and PSO‑driven optimization across the integrated platforms.
