Setting up Capability Data

This document explains how you set up the data required to allocate capabilities.

Outcome

Capability basic data is defined to be used in the Repair process. The data is used to match Work Orders requiring particular roles or set of skills with employees that satisfy the requirements.

The following M3 tables are affected:

  • CCAOBJ
  • CCATYP
  • CCAOBC
  • CCADEF
  • CCALVL
  • CCACAP
  • CRODEF
  • CROEMP
Note: It is also possible to carry out skills allocation at the work request stage. Since this process is very similar to the allocation at the work order stage that information is not duplicated in this document.

Before you start

  • Work centers must be defined in 'Work Center. Open' (PDS010)
  • Facilities must be defined in 'Facility. Open' (CRS008)
  • Work order types must be defined in 'Work Order. Type' (MOS120)
  • Employees must be defined in 'Person. Open' (CRS530)
  • Employees should have capacity generated in 'Employee. Connect Calendar' (CRS510)
  • Capability Categories must be defined such as Item, Item Group, Equipments etc.

Follow These Steps

  1. Set up resource types

    Resource types must be defined in 'Resource Type. Open' (CBS700). Press F14 to create predefined resource types to be used, for example employees.

  2. Create capability levels

    Proceed to 'Capability Levels. Open' (CBS006) to create the capability levels. The level of knowledge and skill can be defined from 01-99 where 01 is the highest level.

  3. Create capability types

    In 'Capability Type. Open' (CBS005) the capability types are created. A Capability category is connected to the type. The categories are defined as a Skill, Item Type, Item Group, Service, or as a Role.

    In order to be able to connect an employee to a capability type, either the categories Skill or Role must be defined. (It is possible to define either one or both.) The capability type 1 is defined as Skill and capability type 30 is defined as Role. In addition, an expiry method can be defined based on a date, number of running hours, or times used etc.

    The capability type for geographical allocation should be set up without using capability history and expiry method. The capability category should be set to 1-Skill/Capability. When a request for geographical allocation is made, this operation element will be populated with this capability type and part of the address in the task element ID.

    The capability type for automatic allocation should be set up without using capability history and expiry method. The capability category should be set to 1-Skill/Capability. A capability record in 'Capability. Open' (CBS004) should also be created, see Create capability definitions.

  4. Create capability definitions

    Proceed to 'Capability. Open' (CBS004) to create the definition of each capability and skill, for example, welding, turning, fitting, etc.

    For automatic allocation, the capability type, for example AUT, should be created. When a request for automatic allocation is made, the operation element will be populated with this capability type and set capability. Different capability requirements can be set for different types of automatic allocation. The required capability should be matched to the employee capability defined in 'Capability per Resource. Open' (CBS002), see Connect roles to employees.

  5. Create role definitions

    Proceed to 'Role Definition. Open' (CBS010) to create role definitions as another method of defining capability.

    For example, for a job that requires turning and fitting skills, specify that a mechanic role is needed (since a mechanic would normally have both skills).

  6. Connect roles to employees

    Proceed to 'Capability per Resource. Open' (CBS002) to link Capability or Role to an employee. Define the validity dates as well.

  7. Define capability settings

    Capability settings must be defined in 'Settings. Employee Allocation' (CBS020).These settings are defined for each maintenance order type in 'Work Order Type. Open' (MOS120).

    The settings define the following:

    • How and when allocation will be carried out (manually, automatically, at Request or Work order),
    • Should geography be considered
    • How should skills allocation hierarchy operate (i.e. in what order should employees be presented to the user when deciding which employee to allocate to a certain job).
    • Should Load and Capacity be considered when allocating employees or not.