Skip to main content

Hello,  we’re in the middle of our deployment of PSO for our business which has two distinct operations: one is basically a logistics business: delivering water to customers with lead times of several days.  The other is a more conventional “service” business with technicians installing, servicing and repairing machines.  However, even with the service business we generally work to 5+ days SLAs and so there is very little work of a truly dynamic nature.  We’re finding that the continuous optimisation of PSO a bit difficult to work with - the concept is clear - that it’s continually trying to beat its previous schedule.  But if we’d rather run it in a “batch optimise” mode - effectively load the latest day’s work and press the “schedule” button is this possible?  This may be a preferential model for our go-live and gradually move up to the continual optimisation.

 

For info, we’re running Apps 9 (soon to upgrade to Apps 10) with PSO using the standard IFS interface 

It sounds like you would want to use the static or reactive process types (defined on the Input_Reference in your data).

There’s more information about the different process types in the Datasets section in the Scheduling Concepts - Introduction guide.

Thanks,

Sam


Thanks Sam, that’s very helpful and has got us thinking already


Reply