Versions Compared

Key

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

Overview

...

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

...

Info

Note that assigned Subset Names must match your project materials 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

...

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

...