Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents

...

Option

Description

Example

Adding Stockpiles manually

To add and remove stockpiles manually use the green plus and red minus buttons located in the top toolbar.

The names in the Stockpile Name column must follow this convention:

  1. Haul Infinity: "Stockpiles/MyStockpileName".

  2. Tactical Scheduler: "MyStockpileName".

Adding Stockpiles from Haul Infinity

You can add all or missing stockpiles from Haul Infinity. For this, use the Add Missing Items button located in the top toolbar.

Note

Note, that this tool will only find items with a name that begins with “Stockpiles/”.

...

Create a new Mutex Group (example, “StockpileBlend”) and assign the relevant parcels to the created Known Mining Parcel.

Infonote

Note that assigned Subset Names must match your existing and Known Mining Parcel names.

...

Project Mode

Constrain on Trucks 

Optimise Products

Finger Pile Type

Projects in Constrain on Trucks mode may choose to load First In First Out (FIFO) or Last In First Out (LIFO) logic.

In Tactical Scheduler, FIFO and LIFO refer to the reclaim sequence of the piles within the stockpile fingers. 

Note

Projects in Optimise Products mode must always use Weight Averaged piles.

Otherwise, you’ll get an error message preventing you from proceeding further through the setup without a correction.

“In stockpile <(HG1_ROM)>, you must set the stockpile to weight average because the model is set to optimize products.”

To fix, either select “WeightAveraged” finger pile type, or change the project mode to the “Constrain on trucks”, if required to use FIFO or LIFO stockpiling logic.

Example

Image RemovedImage Added

Finger Pile Size

...

Description

Example

  • Specify the size of each pile within the parcel finger.

  • A pile cannot be reclaimed until it reaches this size (unless you tick the box in Finish Pile at Period End column).

  • A pile can be reclaimed over multiple periods. 

The example on the right shows a setup for a stockpile which has fingers for all parcels. Each parcel finger is comprised of piles with a capacity equivalent to the value defined under the Finger Pile Size column. Pile number 3 in both the MG finger and the HG2 finger has not yet reached the 20,000t threshold, and therefore can't be reclaimed. If "LIFO" was selected in the Finger Pile Type column, this would cause there to be no reclaiming of HG2 or MG material.  

Image RemovedImage Added

The same logic applies if a Mutex Subset is chosen as the Parcel Finger Type. In the example, there is one finger comprising of material type “SP BLEND”. Within that finger, there are multiple piles, each having a capacity equivalent to the value defined under the Finger Pile Size column. If a pile has not met the threshold, it cannot be reclaimed.

Image RemovedImage Added

Through FIFO and LIFO, it is possible to force a stockpile which comprises of a single material type to be fully built before it can be reclaimed. This can be achieved by setting the Finger Pile Size to the capacity of the stockpile. 

...

Explanation

Example

If we consider that setup of ROM_2 which has the Finish Pile at Period End option enabledit can be observed that material is reclaimed off the stockpile before a 40,000t pile has been constructed. When using this option, the quantity reclaimed cannot exceed the closing balance of the previous period. This is why in period 3, only 3,631 tonnes of material is fed to the crusher despite there being 18,605 tonnes at the end of the period. 

Image RemovedImage RemovedImage AddedImage Added

Manual Reclaim

...

Reason

Remedy

Names of Subset parcels are not mapped correctly and don’t match names of existing parcels

Review parcels naming and mapping in the Known Mining Parcels setup step and Reserves tab > Data panel > Mutex Parcel Groups.

Mapped names must fully match names specified in the Known Mining Parcels.

Mismatching names, example “Blend” instead of “SP_Blend”, will result in an error, since “Blend” doesn’t exist as a parcel name to map other parcels into.

Tip

Tip

Despite the fact that all parcels in the imported data are detected automatically, you can specify all existing in your project parcels in the Known Mining Parcels step. It will help to avoid remapping parcels each time after updating reserves naming.

(lightbulb) If you are working with unembedded Rapid Reserver and have numerous parcels, to make sure that existing parcels names are correct, you can export Mining Database to CSV and remove duplicates for the Parcel column. It will leave you with a list of existing parcels to copy and paste in Known Mining Parcels step.

...

Раздел документации на русском языке 🇷🇺