Flexible Preference Factors

When flexible service order attributes are used to help match resources to requests, they are called Flexible Preference factors. Values for Flexible Preference factors can be specified on the Service Order - Additional General Information page of the resource request. They also appear on the Resource Profile - Preferences page so resources can further define their assignment preferences.

Flexible Preference factors measure the fit of resources to resource requests based on user-defined preferences for attributes that can be selected on a resource request. Flexible Preference factors measure how well the assignment matches the preferences of the resource regarding a specific, user-defined attribute. An example of a flexible resource preference factor is attire. Creating an Attire preference factor gives you the ability to track the dress code of each assignment, capture the attire preferences of each resource, and consider how compatible the two are when performing Resource Matching. You define Flexible Preference factors during implementation in the Flexible Attributes Setup component.

The resource request can have one or more values for each flexible attribute associated with the factor. Resources indicate their preference for each attribute value. Flexible Preference factors are calculated in the same way as Competency Interest factors.

Flexible Preference factor fit scores range from 0 to 100. The score is:

  • 100 for resources who consider the attribute value Very desirable that is specified on the resource request.

  • 0 for resources who have an interest level of Very undesirable for the attribute value that is specified on the resource request.

  • 0 for resources if the attribute values that are specified on the resource request do not exist on the resource profile.

  • 0 for resources if the attribute values that are specified on the resource request exist on their resource profiles, but the resources did not specify an interest for this competency.

    If resources don't specify an interest for an attribute value on their resource profile, Resource Matching uses a default value of 0 to calculate the fit for the attribute on this resource request.