Attributes are used to determine different properties or characteristics of an object and can be beneficial for grouping and finding data with specific characteristics. There are three attribute types that can be used in Resource Management. Attribute type Resource, Shift and Scheduling determine on what object they can be used. There are system defined attributes that comes with the installation as well as the possibility to create user-defined ones. Attributes and connected attribute values are created in Resource Attribute Manager. Attribute type Resource and Sheduling
There are System define scheduling attributes allowed to use in the Shift template or directly at the Shift level. If the user defines these attributes in the Shift template or shift level, it’s getting priority over the values define in the Scheduling resource page for that particular shift or date range. For example, the user defines Cost per KM as 10 in Scheduling Resource page for the selected resource. Then In the Shift level define that parameter as 8 only for the selected two days. When sending data to DSE it uses 8 as the Cost per KM for the defined two days and applies 10 for other days. All other Scheduling related parameters are working similar way. Parameters like Address Start, Address End, Snap Time, and Overtime use for Dispatch Console when visualizing relevant values in the same way according to priority.
There is a System define Resource attribute for resource regions allowed to use in resource Attributes.This parameter can use to define region availability for resources that use both the dynamic scheduling engine and the Dispatch console. If the user defines these attributes on the Resource Attributes page, it’s getting priority over the regions to define in the Scheduling resource region page. For example, if the user defines Region With a validity period, within that date range regions defined in the Resource Attribute page get priority over regions defined in the Scheduling Resource Region page for the selected resource, When sending data to DSE and visualizing regions in Dispatch Console, it uses same priority order.