Skip to main content

I am looking for best practices (if possible with reference) regarding IFS Applications field service work order planning and resource allocation. It seems there are 3 options:

  • Standard work order gantt and resource allocation: very limited functionality, user unfriendly, slow;
  • Maintenance Planning Board: complex, meant for maintenance not for field service; error prone (connection loss);
  • PSO: complex, requires mature organisation, only applicable for short cycled work orders.

Any help on this topic is highly appreciated!

If you are looking for partner solutions, Novacura has developed many different scheduling Portals for our customers. A portal can be made up of many Portlets which can listen to each other so the data on the screen is dynamic. The UI is intuitive and uses drag and drop capabilities. Novacura’s low-code platform allows changes to be made my by the customer with little to no coding.

Below is an example of our Scheduler Portlet which allows users to drag and drop work orders (or work tasks) in time and view them against the map.

 

We can add configured buttons to execute custom business logic such as auto-planning work orders.

 

Furthermore, the Kanban Portlet can be used to assign resources. In the example below, you can assigned a work order (or work task) to a department, but we have similar use cases of assigned a resource to a work task.

 

All of this is highly configurable to our customers needs and pulls and pushes data directly from IFS.

Reply


Terms & ConditionsCookie settings