This activity is used to connect a Resource to a Location Region. This allows to connect scheduling resources to one or more regions either with an availability or an availability pattern. The regions are defined in the Location Basic Data/Location Region. If the user does not define an availability (valid from/to), the scheduling window-start and end dates are sent by default as the availability for that scheduling resource in that region. Further, if a region has been defined as an attribute for the same resource, the region attribute will take precedence within that period.
Example:
Scheduling Resource Region:
| BRIAN | Colombo-North | 01/01/2024 | 31/12/2024 |
Resource Attribute - BRIAN:
| REGION | Kandy | 01/08/2024 | 31/08/2024 |
Then the regions for the resource BRIAN will be segmented as follows when sending them over to the DSE and Dispatch Console:
| Colombo-North | 01/01/2024 | 31/07/2024 |
| Kandy | 01/08/2024 | 31/08/2024 |
| Colombo-North | 01/09/2024 | 31/12/2024 |
The incentive for a resource to work in a region can be set from the "Within Region Multiplier" value on a region-by-region basis. Leaving the within region multiplier empty results in the default value 1 being used as default, which has no effect for the region multiplier. The value "2" multiplies the incentive for the resource to work in the region with "2". The value "0" means the Scheduling Engine will not schedule work for the resource in that region.
As a result of this activity, the scheduling resources of a company that are to be scheduled will be connected to regions with a region multiplier value and can be used when Scheduling.