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/”.

...

Generate a new Mutex Parcel Group to be used in conjunction with the stockpiles by going to the Reserves tab > Data panel. When there press the gear icon to open Configure Parcel Subsets wizard.

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

Info

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

...

Tip

The "Unassigned" value in Subset Name column for each parcel needs to be paired to a "Known Parcel". For parcels which will be part of the Stockpile blend, this "Known Parcel" will be the one created in the previous step. Parcels which are not part of the Stockpile blend can simply be mapped to there own parcel name. 

Step 3. Selecting Mutex Group as Parcel Finger

Select the created mutex group from the dropdown list in the Parcel Fingers column.

...

Important Note

When creating Mutex Parcel Groups make sure that names of parcels in the Subset Name column match exactly names of Known Mining Parcels, otherwise you’ll get an error message that will prevent you from proceeding further with the setup. More details see in the Error Message section below.

Finger Pile Types

In the Finger Pile Types column, choose whether to build and reclaim stockpiles in discrete fingers.

...

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

...

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

...

Error message
Anchor
error
error

If names of parcels in the created Mutex Subset don’t match with the names of known mining parcels, you’ll get an error message, preventing you from proceeding further in the setup.

“One of the stockpiles uses mutex parcel subset <(StockpileBlend)>, which cannot be used because the following parcels are not mapped to parcel names which already exist in the model: <SP_blend-Blend, w-Waste, bg-Blend, lg-Blend, minw-Waste, hghs-Blend, hgha-Blend, hg-Blend>”.

...

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.

Image Added

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.

...

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

...