Solved

Sending Tasks to a Pool with two or more Resource Groups

  • 3 November 2022
  • 4 replies
  • 74 views

Badge +2

Hi all,

I need help to clarify the Pool concepts because we have a new scenario.

The scenario consists of planning and sending a Work Task with Demands to two Resource Groups where only one will accept and execute the Work Task. In this case when one Mobile User accepts the Work Task, a Work Assignment is created and the Work Task is removed from all other Mobile Users in the Resource Group. The other Demand should be cancelled in Transferred Tasks/Work Assignments.

This scenario happens because of the unavailability of resources and because the Work Task can be performed by any of the related groups and not by others. The Customer expects that the unaccepted Demand will also be dropped from the Pool when the Work Task is accepted by any Mobile User.

The same scenario can happen with Tasks sent to Pool-Keep.

What is your recommendation for this scenario?
 

icon

Best answer by skullk 4 November 2022, 05:11

View original

4 replies

Userlevel 5
Badge +10

Hi,

Today, there is no functionality to drop an unattended resource demand from the pool just because attended on another resource demand. It could be that two types of resources are actually needed to complete the job so unattended one remains.

Can’t the customer create a common RG including all relevant resources and add it as the resource demand on the task instead of adding two demand lines? Then it will reach out to all relevant resources and once someone accepted it, it will be removed from the pool. 

Thanks

Sampath

Userlevel 5
Badge +13

Hi All,

A common Resource Group will be a good Idea, but a custom event can also be a solution.

So teh event will be accepting a Resource Demand and creation of a Work Assignment, teh Action will be that all other Resource lines will be removed. 

Be sure in what cases this is required, because it still can happen that the two types of resources are actually needed.

Hopefully you will get a good solution,

Robert

Badge +2

Hi Sampath,

Thank you for your answer. The Customer has well defined Resource Groups and creating a common group is not feasible for their process.

Best regards,

Badge +2

Hi Robert,

Thank you for your answer. Since there are situations where two or more Resource Groups are needed for execution, you would need a criterion that can distinguish the scenarios.

At first the Costumer will work on identifying the resources available for the execution.

Best Regards,

Reply