Skip to main content
Question

Skill Level Flexibility in Resource Allocation – IFS/PSO

  • April 23, 2025
  • 1 reply
  • 11 views

SDN
Sidekick (Partner)
Forum|alt.badge.img+6
  • Sidekick (Partner)
  • 17 replies

From my understanding, the current behavior in IFS does not allow the automatic assignment of resources whose skill level is lower than the one defined in the task template.

Example Scenario:

Available resources:

  • 5 excavator operators with level 5

  • 3 excavator operators with level 4

Planned activities:

  • 6 tasks requiring level 5

  • 2 tasks requiring level 4

In this case, one of the level 5 tasks remains unassigned, even though there are 3 level 4 operators available who could potentially carry it out. The point of view of my customer is to reduce unassigned tasks due to competence constraints, while improving the flexibility and efficiency of the planning performed by the PSO. 

Questions:
Is there a way in IFS (or PSO) to configure a parameter that defines how many skill levels below the required one a resource can be and still be considered eligible for assignment?

  • Default: 0 (no tolerance – current behavior)

  • Configurable: For example, setting the parameter to 1 would allow assigning level 4 resources to tasks that require level 5.

Ideally, this behavior should act as a preference rather than a strict constraint, in order to give the system more flexibility during automatic scheduling.

Is it possible to implement or configure an automatic assignment logic that follows these criteria?

  1. Prioritize assigning resources that meet the required skill level

  2. If such resources are insufficient, allow the assignment of resources with a skill gap within the configured limit

Thanks for your support.

Stefania

1 reply

Alexander Heinze
Superhero (Employee)
Forum|alt.badge.img+23

Hi Stefania, skills and skill levels are hard constraints in PSO, hence I don’t think any customization or configuration is possible. It is however a kind of contradiction - the customer very granularly defines 5 skill levels but then allows a lower level to also get assigned? Why do you then need a level 5 at all? That’s also the reason why I don’t think R&D would consider this if you posted an idea.

What you could do however is play with the resource skill in-use cost and in-use multiplier values. Example: Make level 4 the required level and apply a cost to resources with level 4 so that preferably the level 5 resources get assigned. Or apply the cost to level 5 resources to “normally” protect them from level 4 jobs - depends on your customer’s preference.

Another idea would be to have a resource type preference, but that would only make sense if skill levels are common to certain resource types like an L5 tech vs. a L4 tech.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings