| 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:
|  | ||
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.
|  |
...
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 project materials 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.
...
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. |
Otherwise, you’ll get an error message preventing you from proceeding further through the setup without a correction.
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 |  |   |
Finger Pile Size
...
Example | Some projects can have multiple ROM stockpiles. You may need to report total tonnes on "ROM" or “LT” for example. |
|---|---|
Setting | Create Mutex Subset to be used for reporting and assign Subset Name for each of the stockpiles.  |
Usage in Reporting | Now in the Schedule > Reporting tab you can filter by this mutex subset. MutexStockpile.Reporting = "ROM", which had been set to include all ROM stockpiles.  |
Error message
| Anchor | ||||
|---|---|---|---|---|
|
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.  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. | ||
| 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.
|
...
Раздел документации на русском языке 🇷🇺
...