Minesight® Interactive Planner (Msip) Setup and Capabilities

MineSight® Interactive Planner (MSIP) Setup and Capabilities
MineSight® Interactive Planner (MSIP)

Setup and Capabilities
Contents:
1. MineSight® Interactive Planner (MSIP) Introduction
2. New Additions in MSIP (since 3.60-02)
3. MSIP
4. IP Reserve Reporting Scripts
5. Additional Utilities
6. Integrating MSIP with MineSight® Schedule Optimizer (MSSO) and
MineSight® Activity Planner (MSAP)
1.0 MSIP Introduction
MSIP is a short- and medium-range mine planning tool intended to help the planning engineers in
designing and producing various mine plans. Depending upon the complexity and the variability of the
project, this task can be repetitive and in this regard, the flexibility, the interactive nature, and the ease
of use of MSIP is noteworthy.
Cuts can be created and reserves computed for a mine model or for a MineSight® drillhole/
composite file using the Interactive Planner Object (IPO). The parameters (Area and Material
sets, which control the reporting logic and cutoff binning methodology), the cut geometry, and the
reserves for an individual plan are stored in an Attributed Geometry Data Model (AGDM) which is an
ODBC compliant Microsoft® SQL Server/Microsoft® Access database. This database can be accessed
by various scripts, queries, or any third party external software in order to compute and report the
reserves. Mintec, Inc. recommends the use of Microsoft® SQL Server database as it allows the use of
stored procedures within the database, is much faster, and has less chances of being corrupted. Also,
other MineSight® planning and scheduling programs such as MSSO, MSAP, and MineSight® Haulage
(MSHaulage) require the use of Microsoft® SQL Server.
2.0 New Additions in MSIP (since 3.60-02)
Some of the new enhancements in MSIP are noted below:
2.1 In the multiple ore percent setup, under the Material Sets tab, an option to check the default
waste has been added (Figure 1).
Global
Mining
Software
Solutions
Since
1970
Figure 1
Page 1
2.2 A DATEVAL field has been added in AGDM Template allowing the use of dates as custom
attributes for cuts.
2.3 The IP Tool shows the path for the Model View that’s been selected in Area tab. In Figure 2, the
Model View is located in the folder _msresources\seminar08\cuidw.
Figure 2
2.4 Both IP scripts ip-label.py and ip-accum.py include swell factor options for waste,
tonnage, and volume. To activate the options, open the .py versions of the script in a Python® editor
(or notepad) and modify the flag (REP_SWELL=1). A flag value of 2 (REP_SWELL=1) will apply a
swell factor to the materials listed in the REP_SWELL_MATS. Ip-label.py stores the labels in a
geometry object in Edit mode or prompts the user for a new geometry object. (Figure 3 and 4)
Global
Mining
Software
Solutions
Figure 3 Since
1970
Page 2
Figures 4a and 4b
2.5 The batchReserves module allows scripts to access reserves outside the IP tool. These are usually
executed from the command prompt. Section 5 of the paper will cover the details.
2.6 Solids can now be used as 3D cuts against GSM models in IP. This is one of the major additions
in MSIP (v4.0) as it allows user to use solids as 3D cuts against both GSM and 3DBM projects. The
solids can be selected by navigating to File | Geometry to Cut in IP Cut Design dialog and selecting
the solid from the viewer (Figure 5). Solid cuts can be used for underground setups. However, solid
cuts can not be used in MSSO for scheduling as of the release of this paper.
Figure 5
2.7 Cut Generation tool includes new addition to assign attribute values with element attributes on
Geometry to Cut or Import Multiple. This option allows the user to attribute multiple cuts in one
step from the Naming tab in the Cut Generation tool (Engineering Tools | Cut Generation
Global tool) (Figure 6). These multiple cuts created using the Cut Generation tool can be imported into
Mining MSIP from the File | Import Multiple option in the MSIP Cut Design dialog.
Software
Solutions
Since
1970
Page 3
Figures 6a and 6b
2.8 Archive cuts script (dump and load cuts)—Mintec has developed two scripts for archiving the cuts
from an AGDM and recovering the same data back to AGDM. DumpCutsForArchive.py is
used to export cuts from an AGDM to an ASCII file. After archiving the cuts, the user can delete the
cuts from the AGDM either through a Geometry View object or directly from an IPO. These scripts
need a custom text attribute named Status with two validation values, Active and Archive.
The status is changed to Archive after the cuts are transferred to ASCII file. The archived cuts can
later be imported into the current IPO using the LoadCutsFromArchive.py script. Please refer
to the January 2008 newsletter article for further details.
3.0 MSIP Setups
The basic steps to setup MSIP include:
a. Create the cuts using the Cut Generation tool or Autoslicer in MineSight® 3D (MS3D).
b. Connect the appropriate database to MineSight®.
c. Create a new IPO. Check appropriate options corresponding to the model.
d. Set up the Area tab. Area in MSIP refers to a model. Different pits in the same model can also
be assigned to different areas.
e. Setup the Materials tab. Materials in MSIP refer to the breakdown of the materials which are
to to reported.
f. Click on Design Cuts. In the ensuing panel, the cuts are imported from geometries or Global
digitized. Custom attributes can be added for the cuts and scripts run on the selected cut and/ Mining
or all the cuts using the Scripts tab. Software
The creation of cuts and connecting to attributed databases have been covered in previous newsletter Solutions
articles and seminar workshops in substantial detail. This paper will discuss the rest of the steps. Since
3.1 Interactive Planner Set Creation 1970
An IPO can be created by right-clicking on a folder in the Data Manager and selecting New |
Interactive Planner Object. The three common options to create an IP set include (Figure 7):
a. Create new – Create a new IP set by giving it a unique name.
b. Clone existing - Create a new IP set by making a copy of an existing IP set. The user has the
option to make copy of the entire IP set including the data within the set or just create a copy
of the settings in the IP set (by selecting Settings Only) or by selectively choosing parts of the
IP set by clicking on Filter Geometry and selecting the geometries to be imported.
Page 4
c. Connect to existing – Allows the user to connect to an existing IP set. The user has the
option to connect to a portion of the IPO set by using Filter Geometry option.
Figure 7
Other options include:
d. Exposed Geometry – If checked, polygonal cuts are stored as XYZ points in the AGDM
database which can be accessed using third party software. If not checked, the cuts are stored
in a binary field, generally inaccessible to the user. Users should keep in mind that storing the
cuts in binary format usually leads to faster access while sacrificing portability to other non-
MineSight® applications.
e. Drillholes – This option is used for exploration models where the block models haven’t been
created. This allows the use of drillhole views (both drillholes and composites) to estimate
reserves. It uses polygonal approximation to estimate reserves.
f. Multi Ore Percent – This option is used when the block model has more than one ore percent
item within the block. It is normally used for complex ore and coal deposits.
h. Partials Mapping – This option is only active when the Multiple Ore Percent option is
checked. This allows for priority or selective mining by storing the block partials in an item
initialized with a minimum of 0 and maximum of 100. The stored partials value in the item
keeps track of the mined out amount in the block by progressively reducing the amount of
mined out area from 100%.
i. Min(Topo/Part) – This option is usually checked when the IP cuts follow the topography
contours. It uses the minimum value of TOPO and the partial for computing reserves as
opposed to the default option which uses the product of both.
j. Ore Clipped – Specifies how ore percentages are applied to mining blocks. Checking this
option will apply the Ore Percent value to the entire block. Not checking this option will result
in the product of Topo item and Ore Percent being used.
k. Treat Missing Grades as Zero – When checked, blocks that have a missing grade value
will be reported as having a grade of zero, thus reducing the average grade of the cut. When
unchecked, blocks that contain a grade value of missing (-1) are not used in the weighted grade
Global average calculation for the cut.
Mining 3.2 MSIP setup in 3D Block Model
Software There can be various MSIP setups depending on the presence of ZONE and/or ORE% items in the
Solutions block model. A brief review of the same is given below. For detailed explanation including the calculation
Since methodology, please refer to the MSIP 2007 seminar workshop paper. The paper can be downloaded
1970 from http://www.mintec.com/seminars/.
The ZONE and ORE% items are specified in the Area tab (Figure 8). It references the model for
which the reserves are calculated. A model and at least one grade item must be selected to define an
area. All other options in this tab are optional. Even though most of the time a single area definition is
sufficient, it is however, possible to define a multiple area corresponding to different models (from the
File | New option). Similarly, the Material Set tab (Figure9) contains the reserve bin logic and the
material definition. Multiple material sets can be associated to a single area to define varying reserve
logic. Each cut should have an associated area and material set defined.
Page 5
Figure 8
Global
Mining
Software
Solutions
Since
1970
Figure 9
Page 6
3.2.1 Single Ore Percent Model

The 3D block model with a single type of material is considered a single ore percent model. The
different possible configurations include:
a. No Zone and No Ore%
b. Zone and No Ore%
c. Ore% and No Zone
d. Zone and Ore%
a. No Zone Item and No Ore% Item
The simplest configuration is an IP set up with no zone item and no ore percent item (Figures 8, 9).
The output from this combination is a report of the average grade and tonnage for the material within
a digitized cut.
b. Zone Item and No Ore Percent Item
This is the second possible MSIP setup in a single ore percent model (Figure 10). The output from this
configuration is very handy and has an advantage over previous setups in getting reports for various
classes of material types within a cut boundary. This setup utilizes the codes of the zone item to bin
material within a cut.
Global
Figure 10
Mining
Software c. Ore Percent Item and No Zone Item
Solutions This MSIP configuration (Figure 11) facilitates the distinction between ore and waste values in the
Since block. In this scenario, the grade item represents only the ore material within a block based on which
the total weighted grade for the whole block gets calculated.
1970
Page 7
Figure 11
d. Ore Percent Item and Zone Item.
The last configuration of the single ore percent is IP setup with ore percent item and zone item (Figure
12). The advantages of this configuration over the others is that the user can differentiate between not
only ore and waste within a block but also ore materials.
Global
Mining
Software
Solutions
Since
1970
Figure 12
Page 8
3.2.2 Multiple Ore Percent Model

A project with multiple ore types in a single mining block is modeled using a multiple ore percent
model (Figure 13). In this particular example, there are two ore types and one waste type: Ore1, Ore2,
and Waste. Accordingly, each should have a percent item, a zone item, and the corresponding grade item.
(In this case: Ore percent items are Ore1%, Ore2%; zone items: Ore1, Ore 2; and the grade items are:
CUID1, CUID2, MOID1, and MOID2; similarly Waste and Waste% are the waste zone and waste
percent items.)
This section will cover the basic configurations of the multiple ore percent IP setups i.e., multiple
ore percent with no priority mining, with priority mining, and modeling a non-linear (such as an MIK
model) block model.
Figure 13
a) No Priority Mining
This basic IP setup (Figure 14) won’t account for the mining priority. In other words, tonnage for
each block will be reported without taking into account any preferential mining of the materials. The
blocks should be coded properly with the desired zone type, percent, and grade values. Specific gravity
Global values may or may not differ.
Mining
Software
Solutions
Since
1970
Figure 14
Page 9
Figure 15
b. Priority Mining
MSIP can be set up for priority mining (Figure 16) configuration by checking the multiple ore percent
and partials mapping checkboxes in the IP Set Creation dialog. This allows for situations of selective
mining where Ore2 needs to be mined before mining Ore1. As mentioned in the earlier sections, a
partials item should exist in the block model for proper material balancing (Figure 17).
Figure 16
Figure 16
Global
Mining
Software
Solutions
Figure 17a Since
1970
Figure 17b
Page 10
c. Non Liner Models

This final multiple ore percent IP configuration is a non liner model (Figure 18) where a project
consists of a complex data set requiring the application of non-linear geostatistical techniques such
as Multiple Indicator Kriging (MIK) or Uniform Conditioning (UC). In order to simplify such data
sets, the block grade needs to be defined as a block grade distribution represented as percentages above
particular grade cutoffs instead of as fixed grades. In other words, this data needs to be converted into
separate bins.
Figure 18a
Global
Mining
Software
Figure 18b
Solutions
Since 3.3 MSIP setup in Gridded Seam Models
1970 MSIP setup for 3D block model and GSM models are essentially the same with one significant
difference in the Area tab—3DBMs usually have TOPO% specified as the volume reduction item while
for GSM models, the thickness item and the seam top and seam bottom items are specified (Figure 19).
These items are used to calculate the interburden between seams, particularly for the cut which includes
material from multiple seams. Additionally, if a thickness item is defined, any GSM setup can be used
against a vertical or rotated GSM.
Page 11
3.3.1 GSM Single Ore Percent

As previously mentioned for 3D block models, there are four setups for a single ore percent GSM model:
a. No Zone and No Ore%
b. Zone and No Ore% -
c. Ore% and No Zone
d. Zone and Ore%
a. No zone Item and No Ore Percent
In this GSM IP setup (Figure 19) with a single ore percent, the user can get total tonnage and
weighted grade as an output with the reserves being treated as a single material based on the grade
cutoffs.
Figure 19a
Figure 19b
b. Zone item and no ore percent item

If the user wants to classify reserves into different materials, then an IP setup with zone item and no
ore percent item (Figure 20) needs to be used. The zone item represents the level or bench number
within each block. The number of the seams included within each cut depends on the defined 3D
range through the Edit Range.
Global
Mining
Software
Solutions
Since
1970
Figure 20a
Page 12
Figure 20b
There is also an option to report interburden material in seam by seam order. An IP setup with
multiple types of wastes associated with each seam in the Material tab as shown in the image below
(Figure 21).
Figure 21
c. Ore Percent Item and No Zone Item

In an IP set up with ore percent item and no zone item (Figure 22), the ore% item is calculated as
the ratio of the ore thickness to the total thickness within the seam. If more than one seam is covered
within the cut, then interburden materials is added to the waste. The waste tonnage is calculated using
the density value assigned in the Materials tab for the default material, while ore tonnage is based
on the density assigned to the block. This IP setup enables total ore and waste report for all levels or
Global benches within specified cut.
Mining
Software
Solutions
Since
1970
Figure 22a
Page 13
Figure 22b
d. Ore Percent Item and Zone Item

If the user wants to calculate a ratio of the ore thickness to the total thickness both within seam and
reporting by level, then an IP setup with ore percent item and zone item should be used (Figure 23).
Figure 23a
Figure 23b
Similarly, if the user wants to report the waste for each seam individually, then the setup in the Global
Material tab needs to be modified accordingly as it was shown in previous configuration. Mining
3.3.2 GSM Multiple Ore Percent Software
A GSM project with multiple ore percent uses a similar methodology as a 3DBM. GSMs are useful Solutions
when handling inclined benches, and using multiple-ore percent in combination with a GSM gives a very Since
precise modeling approach. 1970
Projects with multiple ore percent items consist of more than one ore type and possibly multiple waste
types. MSIP will read and report the multiple ore and waste tonnages for different types of material
coded to various model items.
a) No Priority Mining
An IP setup for GSM multiple ore percent with no priority mining configuration (Figure 24) reports
the tonnages for the various zones within an IP cut without preference to mining order. The blocks
need to be coded with the zone types and the associated percent items have to be assigned accordingly.
Priority mining option for GSM project is not yet implemented.
Page 14
Figure 24a
Figure 24b
3.4 MSIP for Gridded Surface File (GSF File13)

MSIP can use GSF in a similar way as GSM. A thickness item is required to calculate the mining cut
volume. Reserves classification will need zone and ore% items as well. A practical use can be a surface
which represents bench bottom and total thickness calculated from the topography.
An IP setup for single ore percent with ore percent item and no zone item produces a report where
reserves will be summarized as a single material based on the grade cutoffs (Figure 25). This setup will
estimate average weighted grade for both ore and waste combined together.
Global
Mining
Software
Solutions
Since
1970
Figure 25a
Page 15
Figure 25b
4.0 IP Reserve Reporting Scripts

MSIP includes a lot of built-in reserve reporting scripts which are usually present in the C:\
WINEXE\scripts\reserve folder. Since MSIP allows Python® scripting, user-defined scripts can
also be used for reserve reporting or the supplied scripts may be modified to allow customization.
Pre-requisites
In order to run the scripts in MSIP, Python® (version 2.2.3) and MineSight® Grail (MSGrail) should
be installed. MSGrail is a set of Python® modules for MineSight® data access. Both of them are installed
during the standard MineSight® installation (in winexe\grail).
To make sure the Python®/MSGrail installation is correct and operational, run the Automated Tests
in MineSight® by going to File | Scripts | Automated Tests. If the tests are successful, it displays the
current MSGrail version and location in the computer. One more important requirement is that the
environment variables for the Python® and MSGrail should be set up and point to the correct location.
The required variables are:
PYTHONHOME – set to the location of the Python® installation (the default folder name is
python22, e.g., c:\python22)
PYTHONPATH – set to the location of the MSGrail folder – (i.e., if your installation is C:\Grail,
the value would be C:\)
The environment variables can be accessed from the (Control Panel |System | Advanced |
Environment Variables).
Running an IP-script
Some of the commonly used scripts include ip-accum.py, ip-summary.py, ip-
flatreport.py, ip-allflatreport.py, ip-period.py, ip-report.py and the batch
versions of the same. There may also be present the xxx.pyc versions (compiled) of the same scripts
which are created upon the first run of the xxx.py scripts. One can run either the xxx.py or xxx.
pyc scripts. The only difference being that one can open the uncompiled version of the scripts (with .py
extension) in any Python® editor to configure it.
Global
These scripts can be executed from the Scripts tab in the IP Cut Design dialog (Figure 26). Scripts Mining
can be run in both the Accumulation Scripts portion of the tab as well as Additional Scripts portion
Software
of the tab. Scripts run from Accumulation Script need to have a cut open in the Cut Design tab. It
gives the reserves for that cut as well as the accumulated reserves for all the cuts. Solutions
Since
1970
Page 16
Figure 26
Ip-accum.py (or .pyc) is a useful script to generate the reserves for a single cut (whichever is
open in the Design tab) as well as the cumulative reserves for all the cuts in a given period and in the
plan (Figure 27). The waste material row is populated depending upon what type of IP setup is being
used. Figure 27 shows a typical report obtained with a multiple ore% model, however, if it was a single
ore% model, the waste row would have been empty. This is because in a single ore% model, all the
material is reported under a unique zone item and in such a case the report doesn’t differentiate between
totals for Ore and Waste.
One can customize some of the reporting options available in this script (such as the reporting units,
cutoff, etc.) by opening it in a Python® editor (idle, pythonwin) or Notepad (Figure 27).
Global
Mining
Software
Solutions
Since
1970
Page 17
Figure 27
IP-summary.py (or .pyc) is another useful script to summarize the reserves based on the
individual cuts, period total, mining area total, and cumulative total. It also has several configuration
options to alter the reporting. One such being the ability to report in CSV form. However, it does not
support cutoffs.
Global
Mining
Figure 28 Software
IP-report.py, IP-flatreport.py, IP-allflatreport.py, and IP-period.py are Solutions
other useful scripts to report the reserves. One can check the report format of these scripts by executing Since
them from the scripts tab. IP-label.py script is yet another particularly useful script if one is 1970
interested in generating the labels as a geometry object.
4.3 Batch IP Scripts
The batch versions of the above mentioned scripts are also available in the same directory. The batch
scripts allow accessing the reserves engine and IP cuts from outside the IP tool. In other words, it means
that one need not have to be connected to MSIP to get the reserves. These scripts only utilize the live
connection to a database/AGDM to generate the reserve reports. However, the DSN (or DSN/user/pswd)
for the AGDM and the IP-set plan name MUST be specified for this script to run.
Page 18
The DSN name is basically the ODBC connection name (Figure 29) for the AGDM while the IP set
plan name can be found by looking at the top right hand corner of the IP tool (Figure 29). It can also
be found out by looking at the GEOMOBJECT table of the AGDM. In this example, the DSN name is
MSIP Seminar SQL and the IP set plan name is multiple.
Figure 29
There are two ways to run the batch version of the scripts:
1. Hardcode the names below in the global variables DSN_STRING = “ MSIP Seminar
SQL “ and PLAN_NAME = “multiple” of the script and execute it using the run icon
in the editor (Figure 30).
Figure 30
2. Execute the script from command line with arguments by putting in the DSN name and IP
set plan name as command line arguments. If no arguments are provided at the command
line, the global values hardcoded into the script are used. In the figure below (Figure 31), MSIP
Seminar SQL is the DSN name while multiple is the IP set plan name.
Figure 31
5.0 Additional Utilities

In this section we will discuss some of the very handy features of the AGDM databases that can be
useful in MSIP.
5.1 Visualizing the cuts in MS3D
Global The cuts for each period can be visualized in MS3D using the Geometry View object. Geometry
Mining Views are live links into AGDM databases. Let’s say that we want to see the cuts that have a Status of 1.
We will proceed as below.
Software
Solutions a. Right click on any folder in the MS3D Data Manager and select New | Geometry View
Object. In the ensuing panel, give it a name.
Since
1970 b. Highlight the object to include and select All Geometry as the constraint (Figure 32).
c. Now make an attribute constraint. Click on the dropdown menu to select an attribute. For our
exampl, we select Status of the cuts with a value of 1.
d. Fill in the adjoining panels asshown below and click OK.
e. The Geometry View Object will now show the cuts with Status=1.
Page 19
Figure 32
Figure 33 below, shows the various cuts in Period1. The colors have been given per their mining
sequence within the period (another custom attribute).
Figure 33
In order to create a geometry object of the cuts, the Geometry View Object should be first
highlighted and then exported in survey (ASCII) form (Export | Survey (ASCII) file). It then has to be
imported in the same format (Import | Survey (ASCII) file).
Adding Custom Attributes in MSIP
Custom attributes are user-defined attributes which can be added to cuts. Custom attributing is used
for MSSO and MSAP scheduling using MSIP cuts, as well as in various other operations. To create
custom attributes:
a. Go to the Attributes tab and select Create/Edit (Figure 33).
b. In the ensuing panel as shown below, type in the attribute name in the Attr Name: box.
c. Select the type of attribute and give a default value for the same. A table of the required Global
attributes and their default value follows the figure. Mining
d. Click on Add/Change to add the attribute to the list. Software
e. After all the attributes are created, click OK to exit the panel. Solutions
Since
f. Now, in the Attributes tab panel, click Add.
1970
g. In the ensuing pop up panel, select all the attributes and click Add (Figure 34).
Page 20
Figure 34
Figure 33
Integrating MSIP with MSSO and MSAP
The cuts generated in MineSight® along with the reserves can be used for both operations-destination
based scheduling as well as equipment based scheduling using MSSO and MSAP. The figure below
(Figure 35) gives an overview of the complete workflow. It should be noted that the use of MSSO is not
mandated for the use of MSAP. MSAP can import the cuts directly from MSIP and schedule them.
Global
Mining
Software
Solutions
Since
1970
Figure 35
Page 21
The general workflow consists of designing cuts and calculating reserves using MSIP. These cuts
can be directly imported with their attributes into MSAP for scheduling. However, in practice, mines
typically have a very large number of designed cuts (sometimes over 1,000). These cuts can certainly be
imported into MSAP, but scheduling them graphically can be a daunting challenge. An imminent new
MineSight® tool, MSSO can be used to automatically schedule the cuts. MSSO can import MSIP cuts
from AGDM database and schedule them into a series of linear programming problems based on targets,
precedence and product quality, and quantity requirements. The output of MSSO is the optimum
mining sequence of cuts within each period. These cuts can then be imported into MSAP by filtering on
the period and mining sequence attributes and then scheduled.
The requirements in the database for importing it into MSSO and MSIP have been adequately covered
in several other papers which can be downloaded from http://www.mintec.com/seminars/.
Global
Mining
Software
Solutions
Since
1970
Page 22

Minesight® Interactive Planner (Msip) Setup and Capabilities

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Minesight® Interactive Planner (Msip) Setup and Capabilities

Transféré par

Droits d'auteur :

Formats disponibles

MineSight® Interactive Planner (MSIP) Setup and Capabilities

MineSight® Interactive Planner (MSIP)

3.2.1 Single Ore Percent Model

3.2.2 Multiple Ore Percent Model

c. Non Liner Models

3.3.1 GSM Single Ore Percent

b. Zone item and no ore percent item

c. Ore Percent Item and No Zone Item

d. Ore Percent Item and Zone Item

3.4 MSIP for Gridded Surface File (GSF File13)

4.0 IP Reserve Reporting Scripts

5.0 Additional Utilities

Vous aimerez peut-être aussi