Destination Logic

Destination Logic describes the resting place of material at the end of the period.

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 the final resting place of material if that block is picked.


Destination Logic example overview

Destination Rules Filters

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

Notes & Recommendations

Finding Destination

Navigation

 

Name

Description

Note

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.

  • Untick the check box to disable the rule.

Code Filters

Description

Note

May differentiate destinations by some custom logic.

Custom logic to differentiate destinations. For more details and a fully worked example, see: Code Filters.

Period Filters

Description

Note

May differentiate pre- and post- plant commissioning.

 

Agent Filters

Description

Note

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.

The StockpileReclaimer as an Agent does not have a capacity. The rate of material movement is based on the Fleet assigned to the Reclaimer in the Steps Logic.

Destination Logic (Top)

Source and Parcel Filters

Description

Note

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:

  1. When items are set on the same row the decision will get made by a travel time.

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

  1. waste will firstly be sent to the Dump1,

  2. if Dump1 is full or unavailable it will be sent to the Dump2 or Dump3 whichever is closer or faster to get to,

  3. the DumpOverflow will be filled only when Dump1, Dump2 and Dump3 are no longer available to take the waste.

Destination Options

Constrain the rule to particular destinations. Agents evaluate which destination in the list is available.

If you need to prioritise direct feed to the Crusher over the Stockpiles reclaim in the Trucks Constraint mode, in the Destination rules, you should have two lines for the destination where the Crusher is priority 1 and Stockpile(s) are priority number 2.

If you put them on the same line, then the optimization engine will send it to the destination which is closer or faster to get to.

If you are using Product Optimisation mode, you can only keep Crusher Feed rules on the same line, and if the stockpiles are actually a closer haul (which is usually the case) then ensure that you have a cash flow on the Crusher to incentivise the direct tip especially if the Crusher is not receiving enough material in a period (you should put a cash flow on the Crusher in any case).

Chargers

Description

Note

If a model includes electric trucks, a column to limit routes to use specific chargers is available.

This logic is used to prevent trucks from driving a long distance across the mine site to charge.

If all chargers are set to constrain by kWh and the schedule requires more kWh than are available, chargers will be used over capacity to honor the schedule rather than constraining tonnages.

Charger Capacity is consumed based on the order of the chargers selected in the list. Once charger capacity is consumed, trucks will continue to run and charging will ‘overflow’ to the closest charger in the list.

Destination Logic (Top)

Notes & 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. Use Setup > Reserve Database > Parcel Subsets to specify applicable source parcels .

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.

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 the Agent has found the Destination Rule for available Destinations, it checks Constraints for available movement.

For more details see: Agents and Schedule Logic Overview

Destination Logic (Top)

Navigation

Creating a rule

  1. Click theblue 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.


Destination Logic Step tools

Copying a 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.


Copying LG rule

Destination Logic (Top)