1. Administering Oracle Fusion Field Service
  2. Add a Resource Type for Mobile Worker in Oracle Fusion Field Service

Add a Resource Type for Mobile Worker in Oracle Fusion Field Service

A Mobile Worker is a resource that performs work, has work skills and work zones associated, and has a related user (actual person performing work or group of people). A Mobile Worker requires a user, can work, is shown with a Tech icon, and doesn't include the Organization unit option. Assume that you want to assign activities to a mobile worker. You must first create the Mobile Worker resource type and then assign the Field Resource role.

Important: This information only applies to Oracle Fusion Field Service environments. You can verify whether you've Oracle Field Service or Oracle Fusion Field Service, by signing in and checking on the About page.
Note: Some features are available only during the initial configuration. This varies based on the options selected during the configuration. Features that aren't available for editing after the initial configuration will be greyed out.

To add a resource type for the Field Resource role:

  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 Resource Types task. The Resource Types page displays all the resource types you’ve created so far.
  2. Click the plus icon. The Add Resource Type drawer opens.
  3. Complete these fields on the General Info tab:

    • Enabled: Move the slider to enable the resource type. The resource type is disabled by default, you must enable it to create resources of this type.

    • Name: Enter a name for the resource type. All supported languages are listed.

    • Label: Enter a unique identifier for the resource type. This identifier is mapped to the REST API.

    • Associated Resource Role: Select a predefined resource role and custom role that defines the resource type further. The predefined roles are created through the Manage Resource Roles task in Setup and Maintenance, example, Field Service Contract Worker.
  4. Select the required features from this list:

    • Team member: Select the Team member checkbox to identify whether the resource type participates in teamwork activities. If deselected, then you can't add the Mobile Worker resource type as an assistant to a team.

    • Team leader: Select the Team leader checkbox to identify whether the resource type is a primary team holder of an activity. An activity that requires a team is always assigned to the team holder whereas the assisting teamwork activities are assigned to the assistants during the teamwork.

    • Inventory sharing: Select whether the resource type shares inventory with other team members after an activity is started. For example, if the team holder’s inventory has 5 items and the assistant’s inventory has 3 items, then when the activity is started, there are 8 items available for use at the job site.
    • Geolocation sharing: Select the checkbox to define whether a resource (team holder or assistant) shares the geolocation in a teamwork assignment. Although, the application uses the GPS device of each resource to predict the location of the resource, these situations can occur:
      • Application is unable to obtain coordinates, as the resource’s device isn’t working.
      • Application is unable to find the location of the resource due to some reasons.

        In the above situations, the application uses an algorithm to predict the location of the resource using the coordinates of other resources in the team. Therefore, you can view the location of each team resource in the map view.

    • Skill sharing: Select this to enable the resource to share work skills with the team holder. Sharing is defined on the work skill level according to the Sharing of the skill in the teamwork parameter configured in the Add work skill dialog box.
    • Capacity planning eligible: Select this to have resources of this type contribute to the quota and capacity management functions. This implies that the corresponding resources are tracked by these functions.
      When enabled:
      • The resource type is considered while calculating available quotas for scheduling future activities.
      • Activities assigned to resources of this type count against the overall quota used for planning and capacity.
      When disabled:
      • Resources of this type are excluded from quota management calculations.
      • Scheduling and capacity planning don't take these resources into account.

      For example, assume that each resource (Mobile Worker 1, Mobile Worker 2, and Mobile Worker 3 configured as a Field Resource) has a capacity of 480 minutes per day and the Capacity planning eligible checkbox is selected for each resource. Therefore, the Max Available field in the bucket has the overall workflow capacity of 1440 minutes. Now, if a new resource type, Mobile Worker 4 is added and if the Capacity planning eligible checkbox is selected, then the overall workflow capacity of the bucket changes to 1920 minutes.

      If the Capacity planning eligible option is selected during the creation of a field resource, you can't remove (deselect) this option when editing the resource later. However, if this option wasn't selected during creation, you can enable it when editing the field resource.

    • Routing: Select the checkbox if you want routing to assign activities to a resource. If selected, the Settings tab is displayed where you can provide the details of the cost such as overtime and travel time.
    • Late start warning: Select the checkbox to trigger a notification when the resource’s route isn't activated on time. For example, consider the resources, Mobile Worker 1 and Mobile Worker 2 configured as field resources. If the Late start warning checkbox is selected for Mobile Worker 1 and not selected for Mobile Worker 2, then the notification messages are created only for Mobile Worker 1.
  5. Complete these fields on the Costs tab:
    • Working hours cost: Select how the working hours cost is calculated based on activity durations. Select from the Low, Normal, High, Highest options. The routing algorithm factors working time cost differences between resource types for assignments.
    • Overtime Cost: Select the cost of the resource working overtime. Overtime refers to the minutes worked beyond the end of the resource’s working hours for the day. Specify cost increases either as X minutes after the end of the shift or the time beyond the X minutes threshold.
    • Travel Time Cost: Specify the resource’s travel cost. Refers to the estimated time and the cost required for travelling between activities. Select one of these options:
      • Travel unpaid, for example, contractors
      • Travel partially paid, for example, gas reimbursement
      • Vehicle provided--recommended default choice for in-house employees
      • Unusually expensive travel, for example, difficult driving conditions
  6. Complete these fields on the Travel Allowance tab:
    • Start of Day: Select this to enable routing to consider travel time from the beginning of the resource’s working time for the day and to the resource’s first activity. The application estimates the actual travel time to the location of the first activity, when a resource’s Start location is defined. Note that when a route includes activities that require travel and activities that don't need travel, the travel between activities is split into two (or more) pieces by inserting nontravel activities between. If there's any idle time before an activity, it's considered as travel time for the next activity. Select one of these options:
      • Travel time to the first activity isn't included: When selected, travel time to the first activity will be calculated before the Working Time Start value. If an activity has a Service Window of 8:00 am-10:00 am, the activity will have an ETA of 8:00 am and the resource must leave their start location to arrive by 8:00 am.
      • Travel time to the first activity is included: When selected, travel time will be calculated to the first activity. If a resource has 30 minutes of travel and the activity has a service window of 8:00 am-10:00 am the activity’s ETA will be 08:30 am.
      • Partially allocate travel time: When selected, a part of the travel time can occur before the start of the shift. If the value is set to 30 minutes and the resource needs 45 minutes of travel, the first 30 minutes will occur before the start of the shift and the ETA activity’s ETA will be 08:15 am.
    • End of Day: Select this to enable routing to consider travel time to a known end location. Select one of these options:
      • Travel time from the last activity isn’t included: When selected, travel time to the final location will be calculated after the Working Time End value. If a resource’s shift ends at 6:00 pm with no overtime allowed, routing can assign activities that can end at 6:00 pm.
      • Travel time from the last activity is included: When selected, travel time to the final location will be calculated. If a resource’s shift ends at 6:00 pm with no overtime allowed, routing can't assign activities that can end at 6:00 pm.
      • Partially allocate travel time: When selected, a part of the travel time will occur after the shift ends. Suppose that the resource’s shift ends at 6:00 pm with no overtime allowed. When the value is set to 30 minutes and the resource needs 45 minutes of travel to the end location, the latest an activity can end would be 5:45pm.
  7. Complete these fields on the Statistics Parameters tab:
    • Use learned duration at the resource level: Select this to use the resource’s personal profile for duration calculations. If not selected, the application uses only company estimates. For more information, see How is activity duration calculated?
    • Use this data to enhance company-wide estimates: Select this to change the company-wide estimations based on the data reported by the resource. If not selected, the company-wide estimations aren't changed. This applies to both activity durations and travel estimations. Don't select this checkbox if you don't want the durations reported by the resource to affect company level estimations.
    • Specify the number of initial working days to exclude from statistical estimations: Specify the number of days for which the data reported by the resource doesn't affect the company-wide estimations. The date is considered from the time the user accesses the application. Default value is 5 days. For example, if you enter 15 days, then the data reported by the resource for activity and travel durations are ignored for the first 15 days and will not be considered while calculating the company-wide estimates. This field is enabled only if the Use this data to enhance company-wide estimates field is selected.
  8. On the Translations tab, add the resource type in all the languages configured in your organization.
  9. Click Add.
    The mobile worker resource type displays on the Resource Types page. If you click Edit and change a feature setting of a resource type, the application automatically applies the changes to the resource type.