Mincom-MineScape

Reserves

2 Overview
The culmination of model preparation and construction and mine design is the calculation of volumes, qualities and any other attributes for a set of mining blocks. This section explores the components of the reserves subsystem, with commentary where required to advise on the most common values for most day-to-day operations. 2.1 2.2 Terminology Interval---a conformable schema unit. In most cases, a coal seam---bounded by a top and bottom surface. Quality name---the names defined as the quality definition specifications. Quality code---the quality resource or waste identifier specified as part of a quality definition. Resources---the ore/mineral being mined. In most cases, the coal Sample table---Reserve output tables prior to accumulation Sample---one row of a sample table representing a triangular prism within the block being reserved. Surface---any type of surface, grid, table, stratmodel and expression. Preparation

Surfaces/Intervals All surfaces and intervals required as limiting, categorisation or reporting surfaces must be created prior to reserving. Stratmodel surfaces and intervals are generated automatically from the schema provided. Quality Quality is any attribute to be associated with an interval, and accumulated using a weight averaging technique. A list of quality codes must be defined, a model assigning interpolators entered, and any defaults (global or by interval) specified. Quality, is always calculated from surfaces residing in the surface database. The quality default is used if the quality surface is defined or returns a missing value, or if the thickness of composited intervals does not account for total thickness of the interval.
Note: Ensure that the quality model is set as required before evaluating quality.

PTMI-2004

Mincom-MinScape 2.3 Reserves Sample

Reserves

Menu: RESERVES>SAMPLE All reserving is based on the concept of a sample. A sample is defined as a triangular prism. The polygonal sides always comprise vertical columns through the reserve block. The top and bottom 3D traingles lie on the top and bottom bounding surfaces of the reserve block respectively. One sample is always defined by one row in the table file, prior to any accumulation. Reserves sample is generated from blocks that are defined as: Solids. 3D blocks usually generated from Batter blocks. Identified by name. Polygons. 2D polygons, poly3Ds or batter blocks. Identified by name (POLY3D/Batterblock in the Blocks database) or design file and number (element ID). Wireframes. A set of enclosing 3D triangles. Identified by a design file and search layers. Triangles. Two sets of triangles defining top and bottom limits and area to be volumed or a set of thickness triangles. Identified by design file and search layers. Mining Reserves

2.4

Menu: RESERVES>MINING RESERVES Mining reserves embellishes and modifies the input sample table to create a new sample table with columns for loss volume, dilution volume, raw recoverable mass, run-of-time (ROM) mass and product mass. If required, qualities can be adjusted to ROM or product basis. 2.5 Reserves Accumulate

Menu: RESERVES>ACUMMULATE Once the samples have been embellished and subdivided to generate the reserve values required, they may be accumulated to the lowest level of control breaking by combining all table rows with matching block name, polygon name, subset name, and reserve interval column values. This step must be performed before reports can be produced. 2.6 Reserves Reformat

Menu: RESERVES>REFORMAT The reserve sample tables may be reformatted into a variety of other formats for further processing:
PTMI-2004 2

Mincom-MineScape

Reserves

2.7

Block Interval Reserve Minestar Reserve Reporting

Menu: RESERVES>REPORT A set of default reports have been provided for the common reporting requirements. They are limited to one sub classification within each block. This subclassification can be comprised of more than one identification column in the reserves table. 1. Summary---generate a summary reserves report 2. Interval---generate an interval reserves report. 3. Burden---generate a burden reserves report. 4. Mining---generate a mining reserves report. 5. Ratio--- generate a vertical interval ratio reserves report. 6. Quality---- generate a quality reserves report. 7. User---defined--- generate a user-defined reserves report. Accumulated Reserves sample tables are reported directly.

PTMI-2004

Mincom-MinScape

Reserves

3 Reserves from Solid

Menu: RESERVES-SAMPLE-SOLIDS Solids can be used to generate samples to a table file. These samples are prisms with triangular top and bottom faces which can be accumulated to calculate volumes. Samples may also be generated graphically to a design file.

Schema Panel Name. The name of the stratigraphic schema as dened in the specification. Model type. The stratigraphic model typeeither TABLE or GRID. Quality Model. The name of quality model specification.

Input Solids Panel The input solids can be listed in a ASCII data file and/or may be entered by name. Output Panel Table file. The Table file must contain a valid name. The table file does not have to exist; if it does, it is deleted first. The table file stores the corner coordinates of the samples, the top and bottom surface names and the values of any optional columns. Solid column. A solid column name should be specified to hold the name of the solid.
PTMI-2004 4

Mincom-MineScape

Reserves

Block area. An area may be calculated for the solid and stored in the table file. The area may be defined as that of the Top face, the Bottom face or a face lying on a nominated surface. When a solid is generated using an offset operation there are 2 faces lying on the surface corresponding to the offset operation. These 2 faces can be distinguished using the SURFACETOP and SURFACEBOTTOM options. The SURFACETOP option identifies the face representing the top of part of the solid. The SURFACEBOTTOM option identifies the face representing the bottom of the adjacent part of the solid. Surface. Surface used to define the area.

Setup/Controls Panel Optional Sample Column. A number of optional columns may be included in the sample table. These columns may be added for more information. It is recommended that Volume, Area and Mass are included.
Note: The inclusion of optional columns increases the size of the table file and the amount of processing required.

Volume. The sample total volume column. Plan area. The plan (horizontal) area. Top area. The slope area of the top of the sample. Bottom area. The slope area of the bottom of the sample. Top slope. The slope as a percentage gradient of the top of the sample. Bottom slope. The slope as a percentage gradient of the bottom of the sample. Top azimuth. The direction of slope (bearing) for the top of the sample. Bottom azimuth. The direction of slope (bearing) for the bottom of sample. Mass. Mass column. Parting. In-interval parting. True thickness. True thickness is the thickness perpendicular to the dip of the interval. Vert. Thickness. True vertical thickness is the thickness from the top to the bottom of the interval in the sample. Block area. Area of the solid face.

Sample Type and Sample Density. Samples can be generated using an AREA option or a POINT option. With the AREA option, the value for the sampling density is the area per sample, hence the smaller the number, the more samples generated. The units used for the area are stored in the project's environment. With the POINT option, the value for the sampling density represents the number of samples per block, hence the larger the number, the more samples generated.

PTMI-2004

Mincom-MinScape

Reserves

Note: When using area per sample, ensure that it is defined in the current area unit. It is critical that a suitable sample density is selected. Too few samples produces unreliable, inaccurate results, while too many samples increase execution time unnecessarily. It is best to experiment with some indicate blocks to find a density where variation in reserves volumes as a function of the number of samples becomes small.

Accumulated. There is an option to perform accumulation by this module by setting the Accumulate flag to Yes. Once the samples have been embellished and subdivided to generate the reserve values required, they may be accumulated to the lowest level of control breaking by combining all table rows with matching block name, polygon name, subset name, and reserve interval column values. This step must be performed before reports can be produced.

Note: No further intersections or evaluations can be superimposed onto the sample table if the table is accumulated. This option should only be used if a quick one step process is intended. In most cases, this flag should be set to No. The accumulate menu option can be used when all sample generation steps are complete.

Use Centeroid. Samples can be generated with either horizontal or sloping top and bottom faces when evaluating surfaces. In most cases, horizontal faces are sufficient, particularly when the sample density is adequate to represent the data and the surfaces being evaluated have small dips (low angle slopes). For this option, the Use Centroid flag should be set to Yes. Samples are generated with the top and bottom faces on the same elevation as their centroids. This provides a quick and efficient method of processing. The Non-Centroid option, which ensures calculations are always performed at each corner of the sample prisms, increases the amount of processing and hence be much slower. This option should be used when design file output is important so that samples are generated with a smooth appearance at surfaces.

Note: When evaluating batters on solids (not a surface), each corner of the prism is evaluated over this part of the solid regardless of the centroid option used.

Design file output. If samples are to be drawn into a design file, the sample tops and bottoms are drawn as polygons. Layer. Layer name for sample graphical output. Append? Yes will append the graphics to existing layer, No will overwrite the existing layer. Display definition. The attributes of these polygons will be according to the display definitions named int_<interval name> if the samples represent a reserve interval roof or floor. The default display definition is used for all other samples.

PTMI-2004

Mincom-MineScape

Reserves

Interval Tab-Divider Reserve Interval Column. Interval column name must be specified to hold interval name. Topography surface. The Surface representing topography must be identified. The name entered field must be a valid surface. This surface is used as the upper surface for overburden when using reserve intervals. Burden column. column name must be specified to hold burden value. Reserves interval. If samples are to be intersected with reserve intervals, a list of intervals should be supplied along with a selection expression for each. If the reserve intervals are not associated with a schema, they must be listed in their correct stratigraphic order, that is downhole order. For each reserve interval, there is a sample produced which is flagged RESOURCE in the burden column. There is always another sample produced which is for the burden. It is is interburden, the burden column stores the name of the above-lying reserve interval. If it is overburden, it has the name of the topographical surface, OVERBURDEN (if no topographical surface is specified) or the top surface of the original sample (if it is below the topographical surface). If there is any part of the sample which is below the lower-most reserve interval it is placed in a sample which q has the burden column flagged as UNDERBURDEN and the reserve interval column stores the name of the above-lying reserve interval. Selection expression. The selection expression may be left blank (meaning True, hence all samples) or up to 80 characters of MXL entered. The file option can be used for larger expressions.

PTMI-2004

Mincom-MinScape

Reserves

Geology Tab-Divider Geological Surfaces/Intervals. A list of geological surfaces and intervals may be evaluated for each sample. The surfaces have their elevation stored while intervals have their floor elevation, thickness and parting stored. Elevations and thicknesses are evaluated at the samples' centroids. An option exists in this module to include qualities in the output sample table.

PTMI-2004

Mincom-MineScape

Reserves

Surfaceset Tab-Divider Surface Set. Surface sets can be defined by supplying a name, upper surface, lower surface and a selection expression. A subset column name also must be defined and the output table stores the name of the surface subset for each sample. The new samples generated exclude volumes outside of the specified surface subset limiting surfaces. However if a limiting surface, upper or lower, is 'missing' then no volume will be excluded by this limit. Subset name. A 16 character maximum which define the subset name. Upper and Lower surface. The upper and lower surfaces can be any Minescape surface, including surfaces defined in the specified schema. Selection expression. The selection expression may be left blank (meaning True, hence all samples) or up to 80 characters of MXL entered. The file option can be used for larger expressions.

Benches Tab-Divider Benches can be defined by supplying a bench definition name and selecting one or more benches from this bench definition. A bench column name also must be defined and the output table stores the bench name for each sample. The new samples generated only include samples within the specified benches.

PTMI-2004

Mincom-MinScape

Reserves

Qualities Tab-Divider Qualities require a set of Specs be set up. Each quality entered must have a quality definition Spec defined. For each quality in the model, there is another Spec which defines default values. These values are used when a quality surface cannot be found or the surface cannot be evaluated at a location. Table columns for each quality per interval are included in the output table. Compositing is performed over each of the samples for each reserve interval and the values are written to columns named after the quality, i.e. <quality>. Ensure that the quality model has been set before entering quality names. Washability Panel Before running reserves with washability, the user should be familiar with the format of Minescape washability tables. This is described in detail in the How to use Minescape Quality manual. In summary, all data within a washability table must have the same structure i.e. the same number and type of size fractions, the same number of RD fractions and same number and type of qualities. The data is stored in a special Minescape table with a suffix of .wsh. All washability functions only recognise this type of table. The input to wasability reserving is a list of intervals and the associated washability rables. Include washability. Yes/No.

PTMI-2004

10

Mincom-MineScape

Reserves

Reserve intervals. A list of intervals for which washability is to be calculated. These must be a subset of the main reserving interval list. Input wash table files. For each reserving interval, all of the washability data must be in same input table (and therefore of the same format). The input tables can contain more than one interval (if the data is the same format). Output wash table files. Each reserving interval can be written to a different table, or can be written to the same table if the washability table is of the same format. Search radius. Typically only a small proportion of the drill holes have washability data. The modelling search radius may therefore be insufficient for washability data and a larger value may need to be provided. If the value is missing, the modelling seaarch radius is used. Calculate Mining Reserve

3.1

Menu: RESERVES-MINING RESERVES Mining reserves embellishes and modifies the input sample table to create a new sample table with columns for loss volume, dilution volume, raw recoverable mass, run-of-time (ROM) mass and product mass. If required, qualities can be adjusted to ROM or product basis.

Models Panel Name. The name of the stratigraphic schema as dened in the specification.
PTMI-2004 11

Mincom-MinScape Model type. The stratigraphic model typeeither TABLE or GRID. Quality Model. The name of quality model specification.

Reserves

Input Panel Table file. The name of the input reserves sample table---may be any sample table that has not been accumulated that includes values for sample mass, sample volume and true vertical thickness. Ouput Panel Table file. The table output file can be of the same name as the input table (hence updating the existing sample table) or a new output table name. Any existing table is overwritten. Loss and Dilution Panel Res. Intervals. A list of intervals which to be calculated in Mining Reserves. Loss dan Dilution. Loss can be entered as a thickness or percentage so it must be flagged accordingly for each reserve intervals loss default. Similarly, Dilution may be given as a thickness or a percentage: the percentage may be added (a percentage of the in situ mass to add) or total (a percentage of the ROM mass). If a dilution surface name is supplied, the dilution value is evaluated from this surface. If a value cannot be resolved from a dilution surface, the interval default is used.

Controls Panel Quality Basis to Output. If the basis field for the output qualities is Insitu or is the same as the input basis, the values for the qualities are not recalculated. If the required, quality basis is ROM or Product and the input basis is Insitu, the qualities are corrected to the basis required ROM moisture value dan Type. Target ROM moisture value and type of value Addpercent or Totalpercent. Product moisture value dan Type. Target Product moisture value and type of value Addpercent or Totalpercent. Accumulating Reserve

3.2

Menu: RESERVES>ACUMMULATE Once the samples have been embellished and subdivided to generate the reserve values required, they may be accumulated to the lowest level of control breaking by combining all table rows with matching block name, polygon name, subset name, and reserve interval column values. This step must be performed before reports can be produced.

PTMI-2004

12

Mincom-MineScape

Reserves

3.3

Reserve Reformat

The reserve sample tables may be reformatted into a variety of other formats for further processing: Block Interval Reserve Minestar

3.3.1 Reformat Block

Menu: RESERVES>REFORMAT>BLOCK These screens are used to select which reserve sample table fields are to be reformatted into a Minestar block record format.

PTMI-2004

13

Mincom-MinScape

Reserves

Schema Panel Name. The name of the stratigraphic schema as dened in the specification. Model type. The stratigraphic model typeeither TABLE or GRID.

Input Panel Reserve table. The name of the input reserves sample table. May be any sample table that has been accumulated. Selection expression. Selection expression may be used to limit the accumulated samples reported.

Output Panel Table file. The block record table name. Any existing table is overwritten. Naming Components Panel A list of identifiers to be used in the process of constructing names. The names constructed for each record are stored in nomenclature columns of the output table. Identifiers are used to construct the names to be stored in the nomenclature columns. Where this identifier is repeated, this component of the name is appended to existing components for that particular name. The following is an example of the use of component identifier, type and value to construct output names:

PTMI-2004

14

Mincom-MineScape
Identifier RES_BLOCK RES_BLOCK RES_SUBSET Type CONSTANT BLOCKNAME SUBSET P 23456789 123 Value

Reserves

Reporting, Slopes and Other Tab-Divider These screens are used to select which reserve sample table fields are to be reformatted into a Minestar block record format. 3.4 Reserve Reporting

Menu: RESERVES>REPORT A set of default reports have been provided for the common reporting requirements. They are limited to one sub classification within each block. This sub classification can be comprised of more than one identification column in the reserves table. 1. Summary---generate a summary reserves report 2. Interval---generate an interval reserves report. 3. Burden---generate a burden reserves report. 4. Mining---generate a mining reserves report. 5. Ratio--- generate a vertical interval ratio reserves report. 6. Quality---- generate a quality reserves report. 7. User---defined--- generate a user-defined reserves report. Bellow is example of Summary report option.

PTMI-2004

15

Mincom-MinScape

Reserves

Input Panel Table file. The name of the input reserves sample table---may be any sample table that has been accumulated. Reformatted tables cannot be used. Selection expression. Selection expression may be used to limit the accumulated samples reported.

Output Panel Report file. The output report file names, and header description. Any existing report file is overwritten.. Report description. A description up to maximum 32 characters.

Naming Components Panel This is only required if surface sets, polygon classification etc. have been used. Leave blank for simple block by block reserves. The names constructed for each record are stored in nomenclature columns of the output table. Identifiers are used to construct the names to be stored in the nomenclature columns. Where this identifier is repeated, this component of the name is appended to existing components for that particular name. The following is an example of the use of component identifier, type and value to construct output names:
Identifier RES_BLOCK RES_BLOCK RES_SUBSET Type CONSTANT BLOCKNAME SUBSET P 23456789 123 Value

PTMI-2004

16