Setting up a preschedule |
|
|
|
Setting up a preschedule |
|
|
Setting up a preschedule |
|
|
|
Setting up a preschedule |
|
|
Mining blocks, or portions of mining blocks, which have been mined prior to the commencement of a schedule, can be accounted for in one of two ways:
| • | Mined Out Quantities - the mined out quantities list contains records that are to be removed from all scenarios in the current project. These records would normally be those mining blocks that have been mined, or partially mined, since the database was created. There is only one mined out quantities list. |
| • | Preschedule Table - a preschedule table contains records that are to be removed from a particular scenario. These records would normally be those mining blocks that are expected to be mined between now and the start of the schedule. You can set up many different preschedule tables. Each scenario may have one preschedule table attached to it, however a preschedule table may be used for more than one scenario. |
When you calculate a schedule, the preschedule record percentages are subtracted after the mined out quantities.
|
The Mined Out Quantities and the Preschedule percentages are not cumulative. |
If 50% of a record is listed in the mined out quantities and 70% of that same record is listed in the preschedule table, then the percentage mined for this record will be the greater of the two values, namely 70%.
In the above example, if you tried to mine only 40% of that record in the preschedule, you would get an error message to say that the mined percentage must be greater than or equal to the mined percentage in the mined out quantities.
