Maintenance User Cannot Be Set As a Resource in Resource Allocation

HI @KevinLach ,

Please add screenshots of the resource details and the resource allocation error so that we can better understand the problem.

Thanks,

Nethmini

Our maintenance manger is trying to allocation a user as a resource on an active work order, but cannot. Here are screen shots of the user (TSHEPARD) setup. As far as I can tell, the user is set up similarly to other users that can be allocated. The one part I haven’t been able to check from the IFS help is the “Scheduling Basic Data” page but I cannot find it in IFS.

 

Thank You

 

 

In the allocation screen, do you see a “Apply Constraints” option? Can you try and untick that? If that solves it, check that capacity has been generated for the resource.

Hi @KevinLach ,

Looking at the screenshots I don’t see any issue here . Ideally you should be able to drag and drop the allocated time slot to the resource as below. One thing I noted was you have not defined planned start and finish on the work task, but it does not affect the allocation process.

Scheduling Basic Data page is belonged to component SCH360. Here in the above example the resource 100 is not defined as a resource here, so I’m curious why you are looking for this window. Do you get any error message during allocation? if so please mention the error .

Thanks & Best Regards,

Nethmini 

Hello Anmise, I apologize that I’m probably not explaining the problem well. For other maintenance person resources, their name can be dragged from the top part of the screen to the bottom part to place them in schedule. In the case of TSHEPARD, the user cannot be dragged to the bottom part of the screen to place him in the schedule.

Hi Nethmini,

I performed the steps you suggested in the previous post. The user is reporting that on some work orders, he can allocate TSHEPARD to the work order. It seems that there is more than one problem happening here. I am going to stop working on this for now as we have IFS success working with the maintenance team soon and this subject will be addressed then. Thanks for your help.