TS. Destination Logic

Open

Destination Logic example overview

Destination Rules Filters

Each rule lists the destinations for transactions that match its filter criteria:

Filter	Description	Note

Filter	Description	Note
Name	Give each rule a unique name, and group in folders.	Avoid using commas in the Destination Rule name, because when exporting future reports to CSV, the commas result in misalignment of the columns.
Use Rule	If the rule is available to be used, leave the box checked. Uncheck the box to turn to disable the 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. Rules are created for the optimiser to know a Destination where Material can go. Waste Rules are order dependent and 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. Example: When items are set on the same row the decision will get made by a travel time. When setting one row after the other, destinations become order-dependent and the specified hierarchy takes place, meaning that Destination2 will only be reached if Destination1 is unavailable (example, reached capacity), and material will be sent to the Destination3 only after Destinations1 and 2 are full or inaccessible. In the example below, waste will firstly be sent to the Dump1, if Dump1 is full or unavailable it will be sent to the Dump2 or Dump3 whichever is closer or faster to get to, the DumpOverflow will be filled only when Dump1, Dump2 and Dump3 are no longer available to take the waste. Open
Destination Options	Constrain the rule to particular destinations. Agents evaluate which destination in the list is available.

Notes and Recommendations

1. It there is no Destination Logic rule that covers a transaction, that Source to Destination movement won’t be able to take place.

2. 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.

   1. Create an overarching folder for the Expit movements for each pit,

   2. Create a folder for the Stockpiles reclaim to each destination.

3. When specifying applicable source parcels, use the Space bar to flag/unflag the selection, or use Parcel Subsets preconfigured in the Reserves tab.

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. 

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

1. Press the blue plus icon located in the toolbar to add a new rule.

2. Give the new rule a meaningful name.

3. Configure the rule as per the table definitions above.

4. 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

1. Hold down the <CTRL> key.

2. Click and drag on the clipboard icon of that rule.

3. 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.

4. Release the mouse to drop the new rule.