- Administering Oracle Fusion Field Service
- Add a Resource Type for Vehicle in Oracle Fusion Field Service
Add a Resource Type for Vehicle in Oracle Fusion Field Service
You must add a resource type for warehouse, so that you can create a warehouse resource and store equipment and parts in it.
- 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.
-
Click the plus icon.
The Add Resource Type drawer opens.
-
Complete these fields:
- 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.
- Role: Select Vehicle.
- Working time includes first travel to activity: Select this if the working time for the vehicle includes the travel time to the first activity.
- Working time includes travel to the final location, if defined: Select this if the working time for the vehicle includes the travel time from the last activity to the final location.
- Inventory sharing: Select this if the vehicle shares inventory with other team members after an activity is started.
- Geolocation sharing: Select this if the vehicle shares the geolocation in a teamwork assignment.
-
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.
- 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:
-
Click Add.
The Vehicle resource type displays on the Resource Types page.