Skip to main content

Hi everyone, 

 

We have a client with a FSM-PSO solution, and one of the requirements is to manage crews that are created and planned by them.

 

We are aware that in FSM, more specifically in the task record, it is possible to use the field “Crew Size” to identify how many elements are needed to close the task.

 

Does anyone know how to handle these requirements within FSM-PSO? We understand that there some limitations regarding integrations between FSM-PSO and we would like to know if anyone has some tips to handle this requirement following IFS best practices. 

 

Thanks in advance, 

Joana Machado

Hi Joana, 

Crew size will indicate the number of resources needed to perform that task. As an example, if crew size is 2 then 2 resources are needed. FSM will have only one task record but it will create 2 tasks to PSO with a co-requisite link (they will be named as C_@taskID_01, C_@taskID_02). 

At allocation stage, or if you are doing the fixes/commits from PSO side, you will not face any issue. But if you are fixing the task or dispatching it from FSM side, there will be some issues due to limitations in current integration (simply due to the fact that we have only one task in FSM but 2 in PSO). But this can overcome through a business rule. 

Another workaround is using multiple task records with predecessor links which will not cause any issues, but don’t know how much it is valid in your context.

Regards,

Sajith

 

Hi Sajith,

 

Our requirement is in some how share the skills between the persons from the crew. The crew concept here is a group of technicians that work together on the same van to share skills between them. 

Using the crew size in FSM, that will consider the technicians desegregated in PSO. 

 

Do you know how to configure for PSO consider the technicians as only one sharing their skills?

 

 

Thank you,

Best Regards,

Andreia Leitão

Reply


Terms & ConditionsCookie settings