Dispatch Configuration
The Dispatch Configuration screen is used to apply dispatch weightings. You can, for example, define a DispatchConfiguration token for each particular truck model type on site. In other words, different dispatch weightings can be applied to different models of truck.
For example, a token ModelA defines the weightings for ModelA trucks. To apply this to Mobile, you would then have a different MobileUnitConfiguration token for each model. The DispatchProfile attribute of the MobileUnitConfiguration group is the link between the DispatchConfiguration and how Mobile is implemented on each model type.
You will find more details of how the DispatchConfiguration is defined in the information on Applying Dispatch Weightings.
| Attribute | Data Type | Description |
|---|---|---|
| Dispatch Enabled | 0, 1 or 2 |
0 Recommendation mode. The dispatch system will present its decision on the Dispatch Decision pane. The decision can be accepted or rejected. If 0 and:
1 = Enabled. If Dispatch is enabled in reference data, all allocations are calculated automatically directly through Dispatch without operator intervention and applied to the Data Acquisition screen and mobile devices. |
| Same Loader Weighting | 0 to 1 | This weighting defines how important it is that a truck remain with its assigned loader. |
| Minimise Time to Load Weighting | N | Generally, set to 1. It is important that minimum load times are achieved for optimal equipment usage. |
| Adhere to Plan Weighting | 0 to 1 | This weighting defines the importance of adhering to the tasks defined in the shift plan. |
| Loader Priority Weighting | 0 to 1 | A weighting of less than 1 will lessen the need to comply with the current loader priority setting. |
| Local Dispatch Enabled | 0 to 1 |
Settings of either:
|