Define Location for Scheduling

Explanation

This activity is used to define scheduling information for a location.

Location Types are not mandatory when creating a Location. When the location has a location type defined the location will inherit the information registered for that the location type. If information is entered on the location specifically then this information will take precedence over the information from the location type.
It is also possible to group locations by defining a locality for the location. For more information refer to the activity Define Location Type and Define Locality.

In this activity it is also possible to define the regions that the location is associated with. If the location is not in a Region then there are no region restrictions for this location. If a location is linked to multiple regions then the resource must also be linked to all specified regions, either directly or via a parent region (or have a value for out of region multiplier which is not 0) in order to be allocated to a work task at this location. For more information refer to the activity Define Region.

It is possible to define the availability of a location. If no availability has been defined for the location the location will always be available. The availability for a location will be defined by connecting a work time calendar to the location. It is also possible to define exceptions to the availability of the location by registering an availability exception in the exceptions page.

It is also possible to define the resource preferences for a location. It is possible to define that one or several scheduling resources are either excluded, required, preferred or non-preferred when carrying out work at the location.

If a scheduling resource is:

• Excluded from the location, then this scheduling resource will not be allocated to work tasks at this location.
• Required for this location, then only this scheduling resource will be considered when work tasks at this location are to be allocated.
• Preferred, then this scheduling resource will is likely to be allocated to work tasks at this location.
• Non-preferred, then this scheduling resource will is less likely to be allocated to work tasks at this location.

Prerequisites

• The region which should be registered for the location must be entered and saved as region in location basic data.
• One or several work time calendars must be entered and saved in application base setup.
• The resource for which a location preference is to be defined for must first be set up as scheduling resource in scheduling basic data.

System Effects

• Location can be associated with one or several regions.
• A work time calendar can be used to define the availability of a particular location.
• Availability exceptions may be defined that takes precedence over the location availability.
• Resource preference can be defined against a location.

Pages

Location
Location Addresses

Activity Diagrams

BDR For Dispatch Console
BDR for PSO Integration
Enter Locations