Pre-scheduling for Evolution

A new option in Maptek Vulcan 10 delivers an easy to use, auditable and repeatable workflow to prepare blocks for scheduling in Maptek Evolution.

Maptek Evolution uses a single block model to generate dynamic strategic to life of mine production schedules. It handles holistic scheduling across multiple pits, sites with automatic waste haulage route allocation and waste landform optimisation.

An intuitive new approach eliminates multiple processes for creating scheduling blocks and produces consistent validated tonnage and grade calculations. Possibilities for making mistakes are minimised.

The base information for Evolution is either a Vulcan block model containing the mining stages flagged in each block or a .csv file. The stages are represented in the mine design as solids or surfaces.

The smart Vulcan 10 interface recognises the input data and turns on/off relevant parameters for data types. Saving the temporary block model variables with the proportion of each stage makes it easy to check the flagging process.

Flagging blocks by majority volume ensures a close match of ore tonnage against the solids. Users can select a break-even cut-off grade; for more complex scenarios this can be adjusted later in Evolution using any of the attributes in the block model.

One important feature of the new interface is the ability to perform some calculations on the fly. For instance, entering the variable cost at this stage is useful for the scheduling step in Evolution.

Users can calculate the incremental mining cost by inputting figures including reference bench, or choose an existing script for Vulcan to run the calculation.

A user-defined tab allows unique measurements and mining costs to be entered for each bench.

Importantly, the reporting option allows users to check tonnage and grade calculations for each pushback and by lithology, providing confidence in the data moving into the scheduling step.

Viewing the Vulcan block model dynamically verifies that blocks included in more than one pushback have been automatically assigned to the correct stage. This process is made even easier by writing a macro aided by the new integrated tshell editor. Using BTOEVO, an external program, plus the specification file runs the process in the tshell environment.

The block model is opened in Evolution simply by browsing to the file in an explorer window or reading a .csv file.

Users can perform some transformations on the fly. For example, if not all blocks are required for scheduling, those lacking a stage value can be filtered out. Variables that will not be used in scheduling can also be filtered.

Evolution reads the input block model, applies the filter and creates blocks in the Evolution block model.

Vulcan allows display of multiple values at the same time, and in Vulcan 10 a vast number of blocks can be viewed at once.

The Workbench Property Editor allows users to interrogate different values and filter dynamically.

Running Evolution and Vulcan side by side in the Workbench allows drag and drop of a Vulcan triangulation (surface or solid), such as topography, into Evolution to see the blocks or stages in context.

Testing multiple customer datasets has verified the accuracy of calculations.

Users now have a streamlined repeatable process for adding stage information block by block. They can execute useful calculations on the fly, replacing the multiple steps and scripts previously required. Consistency between solids and blocks is maintained.