Add a Work SKill in Oracle Fusion Field Service

Work skills are client-specific sets of skills or competencies, required by resources to perform their assigned activities. You must add work skills before you can assign them to resources.

1. In Fusion Setup and Maintenance, go to Navigator > My Enterprise > Offering Setup. Select the Field Service offering. In the Scheduling and Dispatch functional area, select the Work Skills task. The Work Skills page displays all the work skills you've created so far.
2. Click the plus icon.
   The Add Work Skill drawer opens.
3. Complete these fields:
   • Enabled: Move the slider to enable the work skill. The work skill is disabled by default, you must enable it to assign it to resources.
   • Label: Enter a unique identifier for the work skill. This identifier is mapped to the REST API.
   • Name: Enter a name for the work skill. All supported languages are listed.
   • Sharing of the skill in teamwork: Select from the drop-down list:
     • Maximal: Team gets the maximal work skill level of all the team members (default).
     • Minimal: Team gets the minimal work skill level of all the team members.
     • No Sharing: This work skill, if assigned to a team member, it doesn't affect skills of the team.
     • Summary: Team gets the total sum of work skill levels of all the team members. The work skill sharing parameters will define if a specific activity can be assigned to a team-holder, but not higher than 100.

     Quota and capacity calculations don’t use effective work skills (sharing work skills in teamwork); they only use the work skills that match the activities.

4. Click Add. The work skill is added.
5. To edit a work skill, click Edit on the Work Skills page.
   The Edit Work Skill: [Work skill name] drawer opens, which is similar to the Add Work Skill drawer.
6. To delete a work skill, click the delete icon on the Work Skills page.
   You can't delete a work skill that's currently assigned to at least one resource. You can set the enabled or disabled status at any time. Disabled work skills aren't deleted from the application, however, they're unavailable for selection.

   Example of Sharing Work Skill

   A team gets the total sum of work skill levels of all the team members. The work skill sharing parameters define whether a specific activity can be assigned to a team-holder, but not higher than 100. In this example let's see how sharing influences work skill allocation in the group. If a resource is assigned a group of work skills (G) and some work skills explicitly (WS), and there's an intersection of skills, then the explicitly assigned work skills prevail. A resource that isn't assigned any work skills is considered to obtain all the work skills with 100 qualification. Consider the work skill levels for a team as given this table.

   Work Skill	Team Holder	Team Member 1	Team Member 2
   WS0 - Maximal WS1 - Maximal WS2 – No Sharing WS3 - Minimal WS4 – Summary	WS0 (100) WS3 (100) G: [WS3 (10), WS4(10)]	G: [WS0 (1),WS1 (1),WS2 (1) , WS3 (1), WS4 (1)]	WS4(10) G: [WS0(20), WS2(20)] G: [WS0(30), WS2(30)]

   Based on this example, the fffective work skills of the team-holder:

   • WS0(100) - Maximal (100, 1, 30)
   • WS1(1) - Maximal (0, 1, 0)
   • WS2(0) – No Sharing (0, 1, 30), team-holder doesn't have this skill
   • WS3(0) - Minimal (100, 1, 0)
   • WS4(21) – Summary (10, 1, 10)