...
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. |
Notes and Recommendations
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 bar to flag/unflag the selection, or use Parcel Subsets preconfigured in the Reserves tab.
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.
...
Note that each nested rule must contain ALL destinations for the nominated sources. You cannot spread the destinations across multiple rules, since only one rule is evaluated at a time.
Tips
Rules can be copied by holding down the <CTRL> key and dragging on the clipboard icon.
Rules can be archived and shared via the save/import icons in the top right of the form.
Notes on the Constrain on Trucks and Optimise Product modes
...
Finding Destination
The Agent selects the highest ranked block and checks for available Destinations. If a block fails, it is removed from that Agent's ranked block list (another Agent may still try to mine it though).
Once Agent found the Destination Rule for available Destinations, it checks Constraints for available movement.
For more details see TS. Agents and TS. Schedule Logic Overview pages.
Navigation
Creating rule
Press the blue plus icon located in the toolbar to add a new rule.
Give the new rule a meaningful name.
Configure the rule as per the table definitions above.
Place rule into the relevant folder.
Tools
Rules can be imported and exported from projects using the floppy disk and folder buttons located in the toolbar.
Collapse or expand all folders using Expand/Collapse icon.
Use Search and Replace tool to find and replace items. Select items from the lists and read the tips provided.
Copying rule
Hold down the <CTRL> key.
Click and drag on the clipboard icon of that rule.
Drag and hold the cursor over another folder or icon where the new rule will sit. A blue arrow shows where the rule will be inserted.
Release the mouse to drop the new rule.
