...
Destination Logic describes the resting place of material at the end of the period.
...
Rules are created for the optimiser to know a Destination where Material can go.
Waste Rules are listed in priority
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. | ||
Source /Destination and Parcel Filters | May differentiate ore and waste sources by pit. Agents evaluate whether the record source/destinations by pit.parcel being mined is included in the list. | Ensure every Material from every Source has a Destination. | ||
Destination Options | Constrain the rule to particular destinations. Agents evaluate which destination in the list is available. |
| Info |
|---|
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.
...
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 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.
...