Skip to main content

Hello,

I have a customer with a case to handle related to task allocation with PSO and would like to have a discussion about it.

It is an IFS Cloud - PSO integration, for scheduling service tasks involving different teams from different service organizations and DUs on a daily basis.

The teams are not fixed, but are a combination of people and vehicles.

The need for people and vehicles is entered as a demand line in the standard task, which will be linked to new requests as they are created.

We currently manage vehicles as resources (people).

The goal is to assign tasks to the same group of people that can be performed by resources and vehicles with the required skills, for the whole day. These resources leave the site together, with the same vehicle or with several vehicles, and return together at the end of the day. For this reason, it is a fixed team on the day , but not necessarily over several days.

The image shows what I would not want to occur:

  • Res 70/75/84 are  vehicles
  • Technician 1 and Technician 7, are 2 technicians who have the skills to perform both tasks.

What we see here is: Tec 01 and Tec 07 leave the warehouse on the vehicle 84(daily 50), and then move on to another task with another vehicle 27 (Doblo). 

Bear in mind that the demand for resources on a task is not constant. I may have a task that requires 5 people and one that requires 2. 

 

I’d like to have:

According to the priorities (for example) crew 1 for the day 31 October consists of:

  • Technician1
  • Technician7
  • EX678LM Daily50

I therefore expect task 292- to be unallocated or assigned to a different crew.

The customer does not want to create the crew in advance, but wants the right people to be chosen based on the tasks and skills needed by the PSO and to be locked in for the day.

 

Have you ever handled such a scenario, or something similar?

Do you have any ideas/possible solutions that could help me handle this scenario?

 

Thanks

Be the first to reply!

Reply