Define Request Work Task Preference

Explanation

This activity is used to view and register resource preferences on request work tasks. When a job is carried out, resources can be registered as preferred resources in the request work tasks. Further, preferred resources can be registered for the object or the location. Preferences registered on the object or the location will be inherited to the request work task when registering a request work task. When inheriting preferences from an object to a request work task, only the resources that are defined to be used in service will be inherited to the request work task. In addition to that, a list of values is filtered based on the same settings. Finally, once the request work task is scheduled, prioritization will be given to the preferred set of resources over others.

When registering preferences directly on the request work task, entering a Resource ID and Preference is mandatory. The Preference can be 0, 1, or any value between 0 and 1. Entering a preference of 1 indicates no other resources to be considered for the job, and a value of 0 restricts using such resources on the job. A value between 0 and 1, such as 0.5, works in a sliding scale of preference. The fields Preference Source and Source ID display the source type and identity of the source of the preference. 

Preferences Logic

Preferences for Request Tasks can be manually added. Preferences from connected Functional or Serial Objects are inherited and displayed. Location Preferences always reflect the final Task Location. Additionally, preferences from any connected Standard Task are also included for Request Work Tasks.

Prerequisites

System Effects

As a result of this activity resource preferences gets registered against the request work task.