borehole manual

8/13/2019 Borehole Manual

1/26

Century Systems Technologies Inc.

BoreHole ManagerVersion 2

Century SystemsTechnologies Inc.www.centurysystems.net

[email protected]

1


2/26

Century Systems Technologies Inc...............................................................................................1

Introduction.......................................................................................................................................3

2.1. Intro.......................................................................................................................................................3

2.2. What Is BHMS?.....................................................................................................................................3

......................................................................................................................................................................3

2.3. Features................................................................................................................................................3

......................................................................................................................................................................3

2.4. License..................................................................................................................................................4

......................................................................................................................................................................4

3. Installation and Overview.............................................................................................................6

3.1. Installing BHMS....................................................................................................................................

......................................................................................................................................................................

3.2. Starting BHMS......................................................................................................................................!

......................................................................................................................................................................!

3.3. System "e#uirements.........................................................................................................................!

......................................................................................................................................................................!

4. Getting Started...............................................................................................................................8

4.1. $%er%ie&...............................................................................................................................................'

4.2. Chec( In................................................................................................................................................'

4.3. Chec( $ut.............................................................................................................................................)

4.4. Co*y In................................................................................................................................................1+

4.,. Co*y $ut.............................................................................................................................................11

4.. Status..................................................................................................................................................12

. !dvanced O"tions.......................................................................................................................14

,.1. -nloc( Central B..............................................................................................................................14

,.2. Who /m I.............................................................................................................................................14

,.3. 0ri Con%ersion.................................................................................................................................14

,.4. *ort..................................................................................................................................................1,

,.,. "eresh Lists......................................................................................................................................1

,.. "e*orts................................................................................................................................................1!

,.!. /ministrator /ccess........................................................................................................................1'

,.'. System /ministration......................................................................................................................1'5.8.1. User............................................................................................................................................................ . 185.8.2. User to Profile.......................................................................................................................................... .... 195.8.3. Business Units......................................................................................................................................... .... 195.8.4. User Business Units..................................................................................................................................... 20

2


3/26

6. #e$erence.....................................................................................................................................%1

.1. Chec( out 5rocess.............................................................................................................................21

.2. Chec( in 5rocess...............................................................................................................................23

.3. 6i*s an 6ric(s...................................................................................................................................24

.4. $nline Su**ort...................................................................................................................................24

....................................................................................................................................................................24

Introduction

2.1. Intro

Welcome to the Borehole Manager, the secure data repository for geological data. WithBorehole Manager you maintain data integrity while many users are accessing yourdata.

This guide is a reference that describes the benefits and functionality of BoreholeManager. It provides instructions, tips, and examples to help you accomplish eachtask.

sers should be familiar with geological exploration and be comfortable using MicrosoftWindows.

2.2.What Is BHMS

Borehole Manager is an application that controls multi!user access to a centraldatabase of geological information. It is a companion tool to "#$ogger, the primarydata collection application for borehole information. Borehole Manager provides"#$ogger and laboratory data to the entire organi%ation. &xport routines areincluded so users can work with their data in other formats such as 'emcom,"atamine and Mapinfo or connect to them directly with ("B) *(pen "atabase)onnectivity+.

2.!."eatures

Here#s $hat BHMS can do for you%

$inking to the "#$ogger database, Borehole Manager can provide data across thecorporation to many users

3


4/26

-ccess to the data is strictly controlled. If you check out a borehole, you mustcheck in that borehole later.

Transcription errors are virtually eliminated because data is electronically copied. #old all of your local, regional and corporate geological data rovide one source for all geological data with access to reporting tools from drill

reports to Mine Modelling.

2.&.'icense

C()T*+, S,ST(MS T(CH)-'-I(S I)C. S-"TW/+( /+((M()TI" ,-* 0- )-T /+(( WITH TH(S( T(+MS /)0 C-)0ITI-)S 0- )-T

I)ST/'' TH( S-"TW/+(.

1. *S(/ou *an entity or a person+ may use the accompanying software product *the

01oftware0+, in the 2uantity purchased, sub3ect to the terms of this agreement. Inaddition you may make one *4+ archival copy of the 1oftware.

/ou must ac2uire one copy of the 1oftware for each computer on which the 1oftwarewill be installed5 you may not install the 1oftware on a network.

pgrades and Trade!upsIf the 1oftware is an upgrade or a trade!up, you are authori%ed to use the 1oftware only

if you are an authori%ed user of a 2ualifying product as determined by )entury1ystems Technologies Inc. and provided you *i+ either delete the 2ualifying productor install the new product on the same computer or network as the 2ualifying productand *ii+ do not transfer the 2ualifying product to any other person.

2. +(ST+ICTI-)S

&xcept as expressly authori%ed by this -greement, you may not alter, merge, modify oradapt the 1oftware in any way including reverse engineering, disassembling ordecompiling. /ou may not loan, rent, lease or license the 1oftware or any copy.#owever, you may transfer the 1oftware on a permanent basis provided you transferthe 1oftware, this 1oftware agreement and all documentation and media and you donot retain any copies. -ny transfer of the 1oftware must include the most recentupdate and all prior versions. If the 1oftware is demonstration and evaluation *"6&+software, you may not transfer the 1oftware for commercial purposes.

!. I)T(''(CT*/' +-(+T, +IHTS-ll intellectual property rights in the 1oftware and user documentation are owned by

)entury 1ystems Technologies Inc. or its suppliers and are protected by nited1tates and )anadian intellectual property laws *including patent, trademark and

copyright laws+, other applicable intellectual property laws, and international treatyprovisions.

)entury 1ystems Technologies Inc. retains all rights not expressly granted.

&. 'IMIT(0 W/++/)T,7or ninety *89+ days from your date of purchase, )entury 1ystems Technologies Inc.

warrants that the 1oftware will substantially conform to the applicable userdocumentation.

)entury 1ystems Technologies Inc. will, at its option, refund the amount you paid forthe 1oftware or provide you with corrected items at no charge provided that the

4


5/26

defective item*s+ is returned to )entury 1ystems Technologies Inc. within ninety *89+days from the date of purchase. -ny misuse or unauthori%ed modification of the1oftware will void this limited warranty.

&xcept as specifically provided herein, )entury 1ystems Technologies Inc. makes nowarranty, representation, promise or guarantee, either express or implied, statutoryor otherwise, with respect to the 1oftware, user documentation or related technicalsupport, including their 2uality, performance, merchantability or fitness for aparticular purpose.

The warranty and remedies set forth herein are exclusive and in lieu of all others, oralor written, express or implied. :o )entury 1ystems Technologies Inc. dealer,distributor, agent or employee is authori%ed to make any modification or addition tothis warranty. This warranty gives you specific legal rights, and you may also haveother rights, which vary, from country to country and within the states of the nited1tates of -merica.

3. 'IMIT/TI-) -" 'I/BI'IT,Because software is inherently complex and may not be completely free of errors, it is

your responsibility to verify your work and to make backup copies, and )entury1ystems Technologies Inc. will not be responsible for your failure to do so. In noevent will )entury 1ystems Technologies Inc. be liable for indirect, special,

incidental, tort, economic, cover or conse2uential damages arising out of the use ofor inability to use )entury 1ystems Technologies Inc. products or services,including, without limitation, damages or costs relating to the loss of profits,business, goodwill, data or computer programs, even if advised of the possibility ofsuch damages. In no case shall )entury 1ystems Technologies Inc. be liable formoney damages that exceed the amount paid by you for the 1oftware out of whichsuch claim arose. The foregoing limitations shall not apply to claims relating todeath or personal in3ury, which arise out of products deemed to be consumer goodsunder applicable law. 1ome states, provinces or countries do not allow theexclusion or limitation of implied warranties or limitation of liability for incidental orconse2uential damages, so the above exclusion or limitation may not apply to you.

4. *.S. -V(+)M()T +(ST+ICT(0 +IHTS

The 1oftware and;or user documentation is provided with >?!?94C *c+*4+*ii+ *Aune 48+, asapplicable. )ontractor;Manufacturer is )entury 1ystems Technologies Inc.

In the event the 'overnment seeks to obtain the 1oftware pursuant to standardcommercial practice, this software agreement, instead of the noted regulatoryclauses, shall control the terms of the 'overnmentDs license.

5. More Information1hould you have any 2uestions concerning this -greement or )entury 1ystems

Technologies Inc.D software use policies, write to Inside 1ales, )entury 1ystemsTechnologies Inc., EE :ewgate -venue, 1udbury, (ntario, C- =A8, call 4!?9=!

=E9!C@@9, fax 4!?9=!=E9!CEE>.

5


6/26

!. Installation and -6er6ie$

!.1. Installing BHMS

B#M1 is installed on a Windows8=;8 or :T computer from a )"!


7/26

!.2.Starting BHMS

To run BHMS%

"ouble click the icon on the Windows desktop

*or+

)lick rograms, 'eology Tools, B#M1.

TI% (nce the B#M1 is open. )reate a new map or open an existing map to beginworking.

!.!.System +e8uirements

Item Minimum +ecommended(perating 1ystem Microsoft Windows 8=, 8, or :T :TMemory C> Mb E@ Mbrocessor @E ! 499 mh% > @99"isk 1pace >= Mb =9

7


8/26

&. etting Started

&.1.-6er6ie$

The B#M1 *Borehole Management 1ystem+ primary task is to centrali%e collected data.

B#M1 will copy data to and from a central database and set the hole properties toeither copy,checked in or checked out.

&.2.Chec7 In

The check in module copies new and updated drill hole data from the "#$ogger intothe central database. The list on the left displays the current drill holes on the localdatabase along with their pro3ect number, status, start date, end date, who enteredthe hole, -%imuth, "ip, :orthing, &asting and &levation values. The textbox locatedunderneath this list is a status box that will inform the user of current check inactivity. /ou can print the status log at any time the window is open by clicking theprint icon. The window on the left lists all the holes currently flagged for check in tothe )entral "atabase *)heck In $ist+.

To flag a hole for check in, select itDs row in the local drill hole list and click the left arrowbutton *H+. To move all holes for check in, click the double left arrow button *HH+. Ifa mistake was made and the user wishes to remove one or more holes from the)heck In $ist, use the right arrow buttons. To begin the check!in process, click thefollowing check in button.

8


9/26

The status of the check!in process will now be displayed in the status window. This willinform the user of any errors that may occur.

In order for a hole to be successfully checked in, the following criteria must be metF

The holeDs pro3ect number must exist on the )entral "atabase. If the hole has sample numbers assigned to it, the sample

numbers must not already exist on the )entral database *belonging toanother hole+.

If the hole already exists on the )entral "atabase, it must be)hecked (ut.

The hole must be checked in by the user who checked it out.

1ee The )heck In rocess "iagram.

&.!.Chec7 -ut

The check out module allows the user to obtain drill hole data from the )entraldatabase and store itDs information on the local "#$ogger database. This enablesthe user to make changes and updates to the drill hole.

The table on the right shows the user the holes that are currently available to bechecked out from the )entral "atabase. Below this table, there is a status window

which indicates the progress of the current check out. The user may print this statuslog at any time by clicking the rint icon. The table on theleft identifies the holesfrom the )entral "atabase that are currently flagged to be )hecked (ut *)heck (ut$ist+. To add holes to the )heck (ut $ist, select the hole from the left table and clickon the left arrow button *H+, to )heck (ut all holes from the left click the double leftarrow button *HH+. To begin the )heck (ut rocess of the holes listed in the )heck(ut $ist, click on the following )heck (ut button.

9


10/26

The current activity of the check out process will be displayed in the status windowalong with any errors that may have occurred.

In order to successfully check out a hole, the following criteria must be metF

The hole must currently be )hecked In on the )entral "atabase The hole must not already exist on the local "#$ogger database. 1ample numbers that belong to the hole on )entral must not

already exist on the local "#$ogger database. If the business unit of the original creator does not allow for data

sharing, the user checking out the hole must be the original creator.

1ee The )heck (ut rocess "iagram.

&.&.Co9y In

The copy in process can be described as a backup of existing drill holes on the local"#$ogger database. -n example would be if a user wishes to have the dayDs workbacked up on the )entral "atabase in case something happens to their machineand the data becomes unavailable.

The table on the right indicates the holes in the "#$ogger database that are availableto be copied into the )entral. nderneath this table is a status window where the

progress of the )opy In process will be displayed. (n the left is the list of holesflagged to be copied into the )entral "atabase *)opy In $ist+.

To flag a hole to be copied in, select the holeDs row in the "#$ogger table and press theleft arrow key *H+. The hole number will now appear in the left window. To copy all

10


11/26

holes to the left window, use the double left arrow button *HH+. 1imilarly, if an errorwas made and the user no longer wants to copy in a hole located on the )opy In list,use the right arrow buttons to take them off. To begin the )opy In process, click thefollowing )opy In button.

If the hole being copied in exists in the )entral "atabase, it must be checked out to besuccessfully copied in. If the hole being copied in does not exist on the )entraldatabase, a copy of the hole will be created and stored on the )entral database forother users to view.

&.3.Co9y -ut

The )opy (ut process allows the user to view existing drill holes with their "#$oggerdatabase. It can be thought of as checking a book out from a library. -fter checkingout a hole, the user may make changes to it, but the changes cannot be reflected onthe )entral "atabase *cannot check in a copied out hole+. -lso, if the hole is copiedout, it will still be available to other users to copy out or check out.

(n the )opy (ut window, the table on the right identifies the holes on the )entral"atabase that are available to be copied out by the user. nderneath this table is astatus window where the status of the copy out procedure will be displayed. (n theleft, there is a list of holes currently flagged to be copied out *)opy (ut $ist+.

To add a hole to the flagged list, select itDs row in the right table and click the left arrowbutton *H+. The hole number will now appear in the )opy (ut list *on the left+. If theuser wants to copy out all existing holes, use the double left arrow button *HH+. Totake holes off of the )opy (ut list *on the left+, select the hole and click the rightarrow button *+, to remove all holes from the copy out list, click the double rightarrow button *+. To begin the )opy (ut procedure, click the following )opy (utbutton.

11


12/26

7or a hole to be successfully copied out, it must not already exist in the local "#$oggerdatabase.

&.4.Status

The status window allows you to view a list of holes from either the )entral


13/26

)urrent (wner This identifies who has checked out a hole.The name is taken from the sers login id, re2uiredwhen starting Borehole Manager. This defaults to0system0 when the hole is checked in.

1tatus &ither checked in or checked out. )heckedin holes can be freely used by any user and checked

out holes are currently being edited by a user.

To 6ie$ the Status%4. )lick -ction, 1tatus

*or+

)lick the button on the toolbar.

13


14/26

3. /d6anced -9tions

3.1.*nloc7 Central 0B

/ou must have administrative access to use this option.

This allows -dministrators to restore a locked databses.

3.2.Who /m I

This will display the user login name.

3.!.rid Con6ersion

$ocation information may be collected using a variety of grids. To compare drill holes inan organi%ation, it may be necessary to convert location information to a commongrid. 7or example, it may be re2uired to produce a map using TMDs.

To change the current grid settings on the Central data:ase chooseCalculate Common ridunder the -9tionsmenu and select the desired'rid through a drop down list. - list of grid conversion formulae is availableby selecting rid Con6ersionthrough the /ctionsmenu5 here formulasmay be added, modified, deleted or viewed. When the 'rid 1ettings arechanged, Borehole Manager will recalculate all drill hole coordinates in the)entral "atabase and convert it to a point within the new 'rid selected usingthe appropriate grid conversion formula.

To edit an e;isting rid Con6ersion "ormulaaccess the available ridCon6ersions through the /ctionsmenu and double click on the formula tobe modified. - pop!up window will appear allowing the user to makechanges.

To create a ne$ rid Con6ersion "ormula, access the rid Con6ersionsthrough the /ctionsmenu and click on the 0:ew0 button on the toolbar.This will bring up a pop!up window similar to the one shown when editing aformula where the user will enter the data relevant to the new formula. This

14


15/26

means specifying from which grid the conversion is from and specifying thegrid that it will be converted to *these fields are available as drop down lists+.The unit of measure of both grids will also be chosen from drop down lists.The :orthing, &asting, &levation and "elta -%imuth is also collected via textboxes for both grids involved in the conversion.

3.&.(;9ort

&xport drill hole information to use with )amp, 'emcom or "atamine. This processcopies the drill hole information into a format recogni%ed by the software to import.To e;9ort drill hole information close all other windows within Borehole Managerand select &xport from the -ctions menu. This will give the user the option ofselecting which type of &xport to perform. (nce the type of export is selected, awindow will be displayed where the user has to define the &xport directory *thedirectory of the export database+. The user will then define whether the holes being

exported are located in the local "#$ogger database or the )entral "atabase*through the use of the radio buttons on the top right hand corner of the window+.The window on the right displays a table of drill holes available for export. Thewindow below this table will act as a progress log that will display the activity of theexport process as well as any errors that may occur. The window on the leftdisplays the holes that are flagged to be exported *&xport $ist+. To add holes to the&xport $ist, select the hole in the right window and click the left arrow button *H+.The hole will now show up in the &xport $ist. To export all holes in the right window,click the double left arrow button *HH+. If the user wishes to remove holes from the&xport list, select the hole in the list and click the right arrow button *+. 1imilarly ifthe user wishes to empty the &xport list, use the double right arrow button *+.When finished selecting the holes for export, click the begin button on the toolbar.The progress will be displayed in the staus window on the lower left corner of the

window. The user may save or print this log if desired by clicking the appropriateicon next to the status window.

15


16/26

3.3.+efresh 'ists

se this feature to transfer the latest lists ; reference tables from the central database*"#)entral+ to your local database *"#$ogger+. Geeping your lists current is criticalwhen sharing drill hole records.

While your lists are refreshing, you can watch the status through the . (n the -ctions menu, click


17/26

3.4.+e9orts


18/26

3.5./dministrator /ccess

/dministrator /ccessis where the user may make changes to a drill holeDs creator,current owner and present status *)hecked!in or )hecked!(ut+ on the localdatabase. This is useful when 2uick changes are needed before checking!in theholes. &ach editable field is provided with a drop down list *)reator, (wner, 1tatus+.

3.


19/26


20/26

3.


21/26

4. +eference

4.1.Chec7 out rocess

21


22/26

22


23/26

4.2.Chec7 in rocess

23


24/26

4.!.Ti9s and Tric7s

#ole may only be deleted from "hlogger.


25/26

Web 1ite

)entury 1ystems Technologies Inc.EE :ewgate -ve.1udbury(:C- =A8

honeF *?9=+ =E9!C@@97axF *?9=+ =E9!CEE>

25


26/26

33D ine Pl!nning "oft#!re $ 3

BBorehole !n!ger $ 3

%%D&'( $ 6

D

Dis) "*!ce $ 7

++el* $ 24

,,icense $ 4

ine!**er Icon $ 7

borehole manual

Documents