...
Once an Agent picks a block from the ranked blocks list, it needs to put it somewhere as per the Destination Logic, where for each scheduling period we are telling the software final resting place of material if that block is picked.
...
...
Destination
...
Rules
...
All destination inputs on the same row will have the same priority and material will be sent to the Destination with the Shortest Cycle Time that is available (in the Constrain on Trucks mode).
For Destinations on multiple rows, the higher rows have priority. When all the available Destinations on a row are exhausted, the optimiser will cascade to the next row to find a next available Destination.
Availability will be judged by Capacity, open haul route (Dynamic Haulage rules) and Constraints operating on that Destination.
...
All Crusher Feed Destinations can only be listed on one row, the Product Specifications rules (Cash Flows, Grade Targets and Blend targets) will determine, which of the Destinations the Material will be sent to. That is, the material could go to the Crusher or the ROM at the end of the Period.
Destination Rules Filters
Each rule lists the destinations for transactions that match its filter criteria:
Filter | Description | Note | |||
|---|---|---|---|---|---|
Name | Give each rule a unique name, and group in folders. |
| |||
Use Rule |
| ||||
Code Filters | May differentiate destinations by some custom logic. | Requires scripting. More details see here. | |||
Period Filters | May differentiate pre- and post- plant commissioning. | ||||
Agent Filters | May differentiate autonomous and crewed tipheads. | StockpileReclaimer is a default Agent created by the software to reclaim from Stockpiles to feed the Crusher. It doesn’t work in a pit and should be unticked from the list of Expit Agents, and used for Stockpiles Rehandle only. | |||
Source and Parcel Filters | May differentiate ore and waste sources by pit. Agents evaluate whether the record source/parcel being mined is included in the list. | Ensure every Material from every Source has a Destination.
Example:
In the example below,
 | |||
Destination Options | Constrain the rule to particular destinations. Agents evaluate which destination in the list is available. |
...
It there is no Destination Logic rule that covers a transaction, that Source to Destination movement won’t be able to take place.
To make it easier to manage the material flows and troubleshoot in case of scheduling errors, it is recommended to use folders for each group of movements with sensible names to follow the Destination Logic Rules.
Create an overarching folder for the Expit movements for each pit,
Create a folder for the Stockpiles reclaim to each destination.
When specifying applicable source parcels, use the space Space bar to flag/unflag the selection, or use Parcel Subsets preconfigured in the Reserved Reserves tab.
...
4.
When an Agent generates a new schedule transaction, it reads through the Destination Logic list from top to bottom , and applies the first rule that satisfies all filters. This means that if two rules have overlapping conditions, only the first rule will ever execute for that set of conditions.
Overlapping Rules
Advanced users may occasionally create "nested" destination rules. This means a list of two or three rules with successively broader conditions, so that if the first condition is missed, then the second condition is evaluated, and so on.
...