Herald Resources User Manual

Herald Resources
Handbook
Micromine
Herald Resources GBIS Handbook
Table of Contents
Introduction ....................................................................................................... 3
User Activities & User Profiles ............................................................................... 4
Data Views ...................................................................................................... 5
Queries........................................................................................................... 9
Data Exports ................................................................................................. 10
Coordinate Transformation Process ................................................................... 10
Data Entry & Validation Mechanism ................................................................... 12
Sample Tracker.............................................................................................. 21
Author: Jaisakthi Rayapen Commercial in Confidence Page 2 of 36

Revision: Date: 7/01/2011
AUSTRALIA • CANADA • CHINA • INDIA • INDONESIA • KAZAKHSTAN • MONGOLIA • RUSSIA • SOUTH AFRICA • TURKEY •
UNITED KINGDOM • UKRAINE • U.S.A.
INTRODUCTION
Herald Resources have implemented GBIS as part of their geological data management
solution.
This handbook gives instructions on the usage of the features in GBIS. It is aimed at
Administrative users as well as Geologists and Technicians.
Assistance with general GBIS activities can be found in the GBIS help files and standard
GBIS user training manuals and are NOT included here.
These include activities such as:
• Creating custom Imports and Exports

• Importing LAS files
• Using Custom Site Lists
• Using Plan View for data navigation
• Correlation Diagrams
• Downhole Coordinates Interpolation
• Desurvey Process
If you require assistance with these tasks please refer to the GBIS help files.

USER ACTIVITIES & USER PROFILES
Herald Resources has a setup of 2 main GBIS User Profiles. Due to the flexible nature of
the product, this may change over time. Initially these profiles are:
• Administrator
This GBIS user profile contains all the various configured views and queries
which allows data insertion, data update and delete. It has been setup
accordingly for the use of the Senior Geologist. It also contains the
capabilities of performing sample despatches and receipts.
• Data Entry
This user profile contains all the data entry functionality into the temporary
tables and also data views that allows the junior geologists to view data in the
production tables with restrictions on the update and insert and deleting
capabilities. It also contains the capability of performing sample despatches.

Data Views
There are various configured data views throughout both the user profiles. Listed below
are the specific data views which are of highest importance to the current setup at PT
Dairi Prima Minerals and a description of its purpose and function.
Admin: Projects
To view and maintain projects by accessing the GB_PROJECT table. This data view
provides access to the production table for the purpose of adding any new projects.
Admin : Standard Code Tables
To view and manage the standard lookup tables: GB_LKP_CODE and

GB_LKP_CATEGORY . This data view is used when there is a need to add a new lookup
category as well as to add a new code to an existing lookup.
Admin : Geodetic Metadata
To view and manage the coordinate system metadata by accessing the

GB_SYS_CS_DATUM table. This would be a view to access the geodetic metadata table
into order to add or create a new datum to be reference by the coordinate system.
Admin : Coordinate System
To view the coordinate system definitions by accessing the GB_COORD_SYSTEM table.

This data view could be used if there happens to be a new coordinate system which is
required to be added into the database.
Admin: Validation Rules Entry
To view and maintain all built in database validations by accessing the

GB_VALIDATION_RULES table. This data view is used to create a reference validation
towards the look up tables. At this particular point of the implementation setup,
this data view is not required to be utilized.
Geo: Site & Survey Data

To view and maintain site and surveys for drillholes and other site types by accessing
the tables, GB_SITE and GB_SITE_SURVEY. This data view connects directly to the
production table and has the capability to add, insert and delete data directly.
Geo: Downhole Survey Data
To View and maintain downhole survey related information by accessing the table,
GB_DOWNHOLE_SURVEY table. This data view connects directly to the production table
and has the capability to add insert and delete data directly.
Geo: Lithology Data
To View and manage Lithology Data by accessing the GB_LITHOLOGY table. This data
view connects directly to the production table and has the capability to add insert and
delete data directly.
Geo: Surface Details
To View and manage Surface Data by accessing the GB_SURFACE_DETAILS table. This
data view connects directly to the production table and has the capability to add insert
and delete data directly
Geo: Geotechnical Data
To View and manage Geotechnical Data by accessing the GB_GEOTECHNICAL table. This
data view connects directly to the production table and has the capability to add insert
and delete data directly
Geo: Structure Data
To View and manage Structural Data by accessing the GB_STRUCTURE table. This data
view connects directly to the production table and has the capability to add insert and
delete data directly

Geo: Sample (ROUTINES)
To view and maintain captured routine sampling details by accessing the table
GB_SAMPLE
Geo: Sample (STANDARDS)
To view and maintain captured standard sampling details by accessing the table
GB_SAMPLE_QAQC table
Geo: Analytical Results
To View analytical results by accessing the tables, GB_SAMPLE, ST_DESPATCH_SAMPLE

and ST_RESULT through the set up of various queries.
Geo: View All Data
To View all the data described above in one single data view. This data views also allows
data updating, inserting and deleting.
ST : General Lookups
To maintain the general Sample Tracker metadata lookup information and to add or
update details such as lab digest and Determination data.
General Metadata Data View
To maintain Sample Tracker metadata information by accessing the ST_XS_ELEMENT

table. This data view is used to manage information such generic methods, population of
lab standards, laboratories, and adding of field preparation information.
Laboratory Specific Metadata Data View
To maintain metadata for individual laboratories by accessing the tables, ST_MD_LAB,

ST_MD_LAB_LOCATION, ST_MD_LAB_METHOD and ST_MD_LAB_COMBO. This data view
is used to associate specific elements and sample preparation information to a particular
lab method.

SIF Format Layouts Data View
To view and maintain the SIF Format Layouts by accessing the ST_XS_FORMAT and
ST_ACCESS_FORMAT_LAYOUT tables. This data view can be used to add a new sif file
format as well as amending any current setup.
ST : Despatch Data View
To view and monitor despatch details by accessing the tables, ST_DESPATCH and
ST_DESPATCH_SAMPLE
ST : Receipt Data View
To view and monitor Receipt details by accessing the tables, ST_DESPATCH,

ST_DESPATCH_SAMPLE and ST_RESULT.
ST: Sample Results Summary
To view Routine and Check assay results in a pivoted format by accessing the tables,
ST_DESPATCH, ST_DESPATCH_SAMPLE and ST_RESULT.
To view Standard assay results in a pivoted format by accessing the tables,

ST_DESPATCH, ST_DESPATCH_STANDARD and ST_RESULT_STANDARD.

Queries
ST: Delete all receipts and results for a despatch
This query is used to delete all receipts and results of a particular despatch. This query
is useful when there is a need to test the sample receipting process. In other words you
could remove the results set for a receipted sif file if the loading was incorrectly done or
if you were just testing.
ST: Delete entire despatch
This query is used to delete all receipts and results and also the despatch information of
a particular despatch. This query is useful when there is a need to test the sample
despatching and receipting process. In other words you could remove the despatched
sample data and also the results set for a receipted sif file. This is useful when you are
testing the entire sample tracking procedure of despatching and receipting.
ST: Update Assay Result Views
This query is used to update the Pivoted results view in the database backend to
accommodate any new combination of elements, methods and units that has been
receipted into the system. It is vital to execute this query from time to time to ensure
that the pivoted query contains the list of all combinations of elements, methods and
unit.

Data Exports
At this stage, below is the most relevant Export configuration included in the setup.
This basically exports a series of views which has been configured in the sql server
database backend based on a prospect of interest.
There are 7 main exports which basically retrieves Collar, Lithology, Mineralisation,
Downhole survey, Structural, geotechnical and assay data for use in MICROMINE.
The data is exported to the location where the user profile is stored, specifically into the
sub folder: \Exports\MICROMINE folder.
Coordinate Transformation Process
Listed below are the current Coordinate Transformation process which has been set up
for Herald Resources. The coordinate transformation process is located under the
drillholes utilities.

To Run the coordinate Transformation process, simply right click the specific
configuration and select ‘open’. You will first be prompted to select a particular prospect.
Upon selecting the specific prospect, you will see the process execute. A series of
messages will appear indicating the number of records processed and the CSV output
file location. In this setup, the output has been configured to be written to the
\Exports\LOCAL_GRID folder where the GBIS user profile is located.

Data Entry & Validation Mechanism
The data entry & validation process would be the key structured process flow which has
been established in the user profiles. This process has been setup with data views along
with a series or configured queries which performs data validation, promotes data into
the production table and clears the transferred data in the temporary tables.
General Data Entry Process Flow
1. Use either one of the following 2. Run the following validation query
data entry view to enter data once the data has been entered into
into the temporary tables: the temporary tables:
Data Entry – Drillholes 2. Validate Imported Data in

Data Entry - Surface BUFFER
4. Run the validation query 3. View and rectify the validation

again to ensure that all the errors using the following data view:
errors has been validated and
rectified 3. View & Rectify TEMP Tables
Validation Results
5. Run the following query to 6. Run the following query to delete

promote the desired site id’s into the transferred data from the
the production table: temporary tables:
4. Accept validated temp 5. Delete Transferred Data from

Data and promote to Temp Tables
Production Table

Described below are the elaborate steps involved in the Data Entry process.
1. Data Entry – Drillholes
This is the data view used to enter data for all drillholes. There are various tabs to
enter drillhole related data into the respective temporary tables. The type of data
includes, site survey(collar survey), downhole survey, Lithology, Geotechnical,
Structure, related routine sample data and also standard related data.
The data view for all child records pertaining to a particular site or collar has been
setup to copy down the site_id (hole_id) of the row the cursor is currently on.
In the screenshot below, you will notice that a new row has been created by clicking
the ‘+’ sign and that the project & site_id values has been copied down based on
the parent record. Some fields have also been defaulted and the values can be
changed if required to.

The data entry process for the drillholes can then be continued through to all the various
tabs.
1. Data Entry – Surface
The Data Entry for the surface data works the same way as for the drillhole data
entry, however, it contains only the tabs required for surface related data.

2. Validate Imported Data in BUFFER (Query)
The ‘validate imported Data in Buffer’ query is basically the next process to execute
once the data entry into the temp tables has been completed.
This query has nested sub queries as indicated in the screenshot below which
performs various different validations beginning with the process of clearing any
previously populated errors in the validation table.
To run the query as a group, right click and select open.

3. View & Rectify TEMP Tables Validation Results
Once the query has been executed, you would need to then open the Data view,
‘3. View & Rectify TEMP Tables Validation Results’
The view would basically produce a list of all the validation errors.
In this Data view, you will notice the list of the various errors on the top portion of
the data view. The section in the middle connects to the various different temporary
table where there may be errors on. Associate the table name with the relevant tab
and search for the row with the error that needs to be rectified.

Once all the errors has been rectified, run the ‘validate imported Data in Buffer’
query again just to ensure that all the errors has been fixed.
4. Accept validated temp Data and promote to Production Table
When all the errors have been fixed, you can then choose to insert the data from the
temporary table into the actual production table by executing the query,
‘4. Accept validated temp Data and promote to Production Table’. Do note that there are
nested queries in this set up and you may choose to just promote a specific data of
interest. However, bare in mind that the corresponding Site data needs to be available in
the GB_SITE table first before importing specific data such as Lithology, Geotechnical
and etc..

If you run the query set as a group, you will first be prompted with the following window
allowing you to select a specific query
Upon clicking on ‘OK’, you will then be prompted with the substitution parameter window
where you could select the list of Sites on interest.

5. Delete Transferred Data from Temp Tables
Once the relevant sites has been transferred into the production table, you can then
delete them from the temporary table by executing the query, ‘5. Delete Transferred
Data from Temp Tables’. This query works the same way and will delete record that you
have selected if they are already in the production table.

With the deletion process, the data entry, validation and data promotion process is
complete.

Sample Tracker
As Herald Resources records all their routine and standards samples before they get
despatched to their nominated laboratory, the GB_SAMPLE and GB_SAMPLE_QAQC table
will be populated. Thus, a customized query has been created to cater for these 2
sample types. This query is also flexible as it is configured with a prompt that allows
entry of a range of sample numbers.
Sample Despatch
The sample tracker process begins with the sample despatching process. This can be
located under the utilities node on the GBIS Tree.
Execute the despatch by double clicking the ‘Intertek Despatch’ with Custom Query’
configuration.
Note: In order for this sample tracker example to work, the Site_id, ‘SOP297D’
has to be first promoted into the production tables.

You will first see the screen below, where you specify the despatch_id
Next, select the relevant field preparation methods followed by the lab preparations

Click on next and select the analyses to be performed.

Click on next and you will now be able to enter the first and last sample interval
numbers.
The samples will then get loaded into the sample despatch windows as follows:

Click ‘next’ followed by ‘finish’ and select ‘Yes’ on the pop up message to load the
sample despatches into the database.
At this stage you can elect to generate a despatch report. Click “Yes” and save the HTML
file to an appropriate folder. A hard copy of this report could be stored along with the
paper despatch.

Sample Receipt
There are basically 2 receipts process which has been created under the Receipts node
in the GBIS tree.
The following pages describe the format layout of both the csv and sif lab files which has
been setup for this database.

Csv format layout
The header portion

should be removed and
both the cells must just
contain the lab job
number value and the
despatch number
The original sample

number of ‘A006097 ‘
was replaced with
‘A06097’. The
additional ‘0’ and a
leading space after the
sample number was
removed

.SIF format layout
The original sample

number of ‘A006097 ‘
was replaced with
‘A06097’. The
additional ‘0’ and a
leading space after the
sample number was
removed

This receipt example is based on the file SOP0902_090292-updated.SIF, which can be

found in the example data under the subfolder \Files\Lab SIF Files.
Double click ‘the Intertek sif Receipt’ configuration under ‘Receipts’ on the GBIS Tree.
The first screen allows you to select the file format type as well as the actual .sif file.

The next page allows you to verity the file format. The purpose of this page is to verify
that the SIF file is being decoded properly.

In the 3rd page, you will see the list of the combo details. The item with the status,
‘unresolved’ in red indicates that the sample metadata which was initially populated does
not match the receipts details for this file. In this example, it indicates that the Detection
limit does not match.
To resolve this, right click and select modify or confirm combo details or simply press
F12.

Change the detection limit to 1 in order to match the sample tracker metadata and click
‘OK’
You will now notice that the error has been resolved.

Click on next to proceed with the next screen. Here, you will notice a series of
unresolved results retrieved from the lab file. The actual routine sample details relates
correctly to the despatched sample and the unresolved items relates to lab standards
and lab checks.

Select the first item, ‘Blank01_090292’ and right click to ‘Identify as lab standard’.
Select the type of standard which this item belong to. In this example, ‘Demo Standard’
was selected. Similarly, identify all other blanks and standards.
You will notice that ‘Ch:A006103’ iterates to be a check result of A06103. You can
resolve this by identifying it as a lab check with the right click options.

Once all the results has been resolved, click next to proceed to the following screen.

In this screen, click on the next button once again and then click finish to write the
results to the database.
With that, the sample receipting process is now complete.


Herald Resources User Manual

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Herald Resources User Manual

Uploaded by

Copyright:

Available Formats

Herald Resources

Author: Jaisakthi Rayapen Commercial in Confidence Page 2 of 36

These include activities such as:

• Creating custom Imports and Exports

Author: Jaisakthi Rayapen Commercial in Confidence Page 3 of 36

USER ACTIVITIES & USER PROFILES

Author: Jaisakthi Rayapen Commercial in Confidence Page 4 of 36

Admin : Standard Code Tables

To view and manage the standard lookup tables: GB_LKP_CODE and

Admin : Geodetic Metadata

To view and manage the coordinate system metadata by accessing the

Admin : Coordinate System

To view the coordinate system definitions by accessing the GB_COORD_SYSTEM table.

Admin: Validation Rules Entry

To view and maintain all built in database validations by accessing the

Geo: Site & Survey Data

Author: Jaisakthi Rayapen Commercial in Confidence Page 5 of 36

Geo: Downhole Survey Data

Geo: Lithology Data

Geo: Surface Details

Geo: Geotechnical Data

Geo: Structure Data

Author: Jaisakthi Rayapen Commercial in Confidence Page 6 of 36

Geo: Sample (ROUTINES)

Geo: Sample (STANDARDS)

Geo: Analytical Results

To View analytical results by accessing the tables, GB_SAMPLE, ST_DESPATCH_SAMPLE

Geo: View All Data

General Metadata Data View

To maintain Sample Tracker metadata information by accessing the ST_XS_ELEMENT

Laboratory Specific Metadata Data View

To maintain metadata for individual laboratories by accessing the tables, ST_MD_LAB,

Author: Jaisakthi Rayapen Commercial in Confidence Page 7 of 36

SIF Format Layouts Data View

ST : Despatch Data View

ST : Receipt Data View

To view and monitor Receipt details by accessing the tables, ST_DESPATCH,

ST: Sample Results Summary

To view Standard assay results in a pivoted format by accessing the tables,

Author: Jaisakthi Rayapen Commercial in Confidence Page 8 of 36

ST: Delete all receipts and results for a despatch

ST: Delete entire despatch

ST: Update Assay Result Views

Author: Jaisakthi Rayapen Commercial in Confidence Page 9 of 36

Coordinate Transformation Process

Author: Jaisakthi Rayapen Commercial in Confidence Page 10 of 36

Author: Jaisakthi Rayapen Commercial in Confidence Page 11 of 36

Data Entry & Validation Mechanism

General Data Entry Process Flow

Data Entry – Drillholes 2. Validate Imported Data in

4. Run the validation query 3. View and rectify the validation

5. Run the following query to 6. Run the following query to delete

4. Accept validated temp 5. Delete Transferred Data from

Author: Jaisakthi Rayapen Commercial in Confidence Page 12 of 36

1. Data Entry – Drillholes

Author: Jaisakthi Rayapen Commercial in Confidence Page 13 of 36

1. Data Entry – Surface

Author: Jaisakthi Rayapen Commercial in Confidence Page 14 of 36

2. Validate Imported Data in BUFFER (Query)

To run the query as a group, right click and select open.

Author: Jaisakthi Rayapen Commercial in Confidence Page 15 of 36

3. View & Rectify TEMP Tables Validation Results