How about adding a resource demand with a resource group (i.e., the maintenance team) and send it to MWO as a pool task? They can then pick the task from the pool task list in MWO.  Even works without a resource group, but you probably want to assign the team at least.

thank you, I will try that

Hi ​@Alexander Heinze 

Do you know a way to assign work to multiple resources considering below conditions.

• It is kind of ad-hoc assignments. Think the back office need to assign a work to technicians who are closed to a certain work. So one technician accept the work and complete. Since it is ad-hoc work, there is no formed resource group before.
• Back office can make multiple assignments but then the assignment will not be disappeared as in pool task once one technician accepts. Other technician do not know whether someone accepted the work or not. Once one technician accept the work it should be disappeared or others should know that someone has accepted. Then they can cancel the assignment.

if you know anything please share.

Thanks.

#1 how do you define “close to a work”? You can have resources that belong to more than one group, so you could put all of them (or by region) into a dummy group and assign to that group as pool task.

#2 Did you look at “Pool” vs. “Pool - Keep” (IFS Cloud - MWO Service demystified (24R2) | IFS Community)?

I know about “Pool” vs. “Pool - Keep” options. The issue is that there is no specific group for selected technicians.  The thing is there may be few instances of this kind of requirements per day. 

The “Dummy Group” you suggested means temporary resource group?

My question is: If you don’t have a grouping of technicians, how should the system know who to assign it to or who should have access?

That is the issue I'm trying to address. A customer has a different app in which he can select multiple resources  and assign for all. Once one resource accept the work, it is disappeared.