Century Systems Technologies Inc.

BoreHole Manager
Version 2

Century Systems
Technologies Inc. www.centurysystems.net info@centurysystems.net

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. 0ri1 Con%ersion.................................................................................................................................14 ,.4. 23*ort..................................................................................................................................................1, ,.,. "e4resh Lists......................................................................................................................................1 ,. . "e*orts................................................................................................................................................1! ,.!. /1ministrator /ccess........................................................................................................................1' ,.'. System /1ministration......................................................................................................................1'
5.8.1. User............................................................................................................................................................. 18 5.8.2. User to Profile.............................................................................................................................................. 19 5.8.3. Business Units............................................................................................................................................. 19 5.8.4. User Business Units..................................................................................................................................... 20

6. #e$erence.....................................................................................................................................%1
.1. Chec( out 5rocess.............................................................................................................................21 .2. Chec( in 5rocess...............................................................................................................................23 .3. 6i*s an1 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. With Borehole Manager you maintain data integrity while many users are accessing your data. This guide is a reference that describes the benefits and functionality of Borehole Manager. It provides instructions, tips, and examples to help you accomplish each task. sers should be familiar with geological exploration and be comfortable using Microsoft Windows.

2.2. What Is BHMS

Borehole Manager is an application that controls multi!user access to a central database of geological information. It is a companion tool to "#$ogger, the primary data collection application for borehole information. Borehole Manager provides "#$ogger and laboratory data to the entire organi%ation. &xport routines are included 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 corporation to many users the

, -ccess to the data is strictly controlled. If you check out a borehole, you must check 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()T I" ,-* 0- )-T /.+(( WITH TH(S( T(+MS /)0 C-)0ITI-)S1 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. In addition you may make one *4+ archival copy of the 1oftware. /ou must ac2uire one copy of the 1oftware for each computer on which the 1oftware will be installed5 you may not install the 1oftware on a network. pgrades and Trade!ups If 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 )entury 1ystems Technologies Inc. and provided you *i+ either delete the 2ualifying product or install the new product on the same computer or network as the 2ualifying product and *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 or adapt the 1oftware in any way including reverse engineering, disassembling or decompiling. /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 transfer the 1oftware, this 1oftware agreement and all documentation and media and you do not retain any copies. -ny transfer of the 1oftware must include the most recent update 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*/' 2+-2(+T, +I.HTS -ll intellectual property rights in the 1oftware and user documentation are owned by )entury 1ystems Technologies Inc. or its suppliers and are protected by nited 1tates and )anadian intellectual property laws *including patent, trademark and copyright laws+, other applicable intellectual property laws, and international treaty provisions. )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 user documentation. )entury 1ystems Technologies Inc. will, at its option, refund the amount you paid for the 1oftware or provide you with corrected items at no charge provided that the

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 the 1oftware will void this limited warranty. &xcept as specifically provided herein, )entury 1ystems Technologies Inc. makes no warranty, representation, promise or guarantee, either express or implied, statutory or otherwise, with respect to the 1oftware, user documentation or related technical support, including their 2uality, performance, merchantability or fitness for a particular purpose. The warranty and remedies set forth herein are exclusive and in lieu of all others, oral or written, express or implied. :o )entury 1ystems Technologies Inc. dealer, distributor, agent or employee is authori%ed to make any modification or addition to this warranty. This warranty gives you specific legal rights, and you may also have other rights, which vary, from country to country and within the states of the nited 1tates 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 )entury 1ystems Technologies Inc. will not be responsible for your failure to do so. In no event will )entury 1ystems Technologies Inc. be liable for indirect, special, incidental, tort, economic, cover or conse2uential damages arising out of the use of or 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 of such damages. In no case shall )entury 1ystems Technologies Inc. be liable for money damages that exceed the amount paid by you for the 1oftware out of which such claim arose. The foregoing limitations shall not apply to claims relating to death or personal in3ury, which arise out of products deemed to be consumer goods under applicable law. 1ome states, provinces or countries do not allow the exclusion or limitation of implied warranties or limitation of liability for incidental or conse2uential damages, so the above exclusion or limitation may not apply to you. 4. *.S. .-V(+)M()T +(ST+ICT(0 +I.HTS The 1oftware and;or user documentation is provided with <&1T<I)T&" -:" $IMIT&" <I'#T1. se, duplication or disclosure by the 'overnment is sub3ect to restrictions as set forth in 7-< =>.>>?!4@ *Aune 48B?+ -lternate III *g+*C+ *Aune 48B?+, 7-< =>.>>?!48 *Aune 48B?+, or "7-<1 =>.>>?!?94C *c+*4+*ii+ *Aune 48BB+, as applicable. )ontractor;Manufacturer is )entury 1ystems Technologies Inc. In the event the 'overnment seeks to obtain the 1oftware pursuant to standard commercial practice, this software agreement, instead of the noted regulatory clauses, shall control the terms of the 'overnmentDs license. 5. More Information 1hould you have any 2uestions concerning this -greement or )entury 1ystems Technologies Inc.D software use policies, write to Inside 1ales, )entury 1ystems Technologies Inc., BEE :ewgate -venue, 1udbury, (ntario, .C- =A8, call 4!?9=! =E9!C@@9, fax 4!?9=!=E9!CEE>.

!. Installation and -6er6ie$

!.1. Installing BHMS
B#M1 is installed on a Windows8=;8B or :T computer from a )"!<(M. The computer must have access to a )"!<(M drive during installation. Install BHMS from a C0% TI.F )entury 1ystem )"Ds support autorun. 4. Insert the B#M1 )"!<(M in the available )"<(M drive.

>. C. @. =.

)lick and choose <un from the 1tart menu Type &F.exe *1ubstitute your )"!<(M drive letter for &F+ )lick the (G button. Install 1hield will prepare your computer for installation. 7ollow the instructions on your screen.

This will load the software and place B#M1 on your start menu, and place a B#M1 icon on your Windows desktop. -lso, an ("B) entry will be created for B#M1 by the install routine. Install BHMS from a )et$or7 Share% TipF -sk an administrator about share privileges 4. >. C. @. =. E. Insert the B#M1 )"!<(M in the available )"<(M drive. In My )omputer, click the )" drive you want to share. (n the 7ile menu, click .roperties. )lick the 1haring tab, and then click 1hared -s. To add a comment about the share, type the text in )omment. To set a ser $imit other than Maximum -llowed, click -llow, and specify a number of sers. ?. To set share permissions, click .ermissions. B. 7rom the client computer access the shared )" from :etwork :eighborhood 8. "ouble click 1etup.exe

!.2. Starting BHMS

To run BHMS% "ouble click the *or+ )lick icon on the Windows desktop

.rograms, 'eology Tools, B#M1.

TI2% (nce the B#M1 is open. )reate a new map or open an existing map to begin working.

!.!. System +e8uirements

Item
(perating 1ystem Memory .rocessor "isk 1pace

Minimum

+ecommended

Microsoft Windows 8=, 8B, or :T :T C> Mb E@ Mb @BE ! 499 mh% .> @99 >= Mb =9

&. .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 to either copy,checked in or checked out.

&.2. Chec7 In
The check in module copies new and updated drill hole data from the "#$ogger into the central database. The list on the left displays the current drill holes on the local database along with their pro3ect number, status, start date, end date, who entered the hole, -%imuth, "ip, :orthing, &asting and &levation values. The textbox located underneath this list is a status box that will inform the user of current check in activity. /ou can print the status log at any time the window is open by clicking the print icon. The window on the left lists all the holes currently flagged for check in to the )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 arrow button *H+. To move all holes for check in, click the double left arrow button *HH+. If a 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 the following check in button.

The status of the check!in process will now be displayed in the status window. This will inform 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 to another 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 )entral database and store itDs information on the local "#$ogger database. This enables the 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 be checked 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 status log at any time by clicking the .rint icon. The table on theleft identifies the holes from 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 click on the left arrow button *H+, to )heck (ut all holes from the left click the double left arrow button *HH+. To begin the )heck (ut .rocess of the holes listed in the )heck (ut $ist, click on the following )heck (ut button.

The current activity of the check out process will be displayed in the status window along 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 work backed up on the )entral "atabase in case something happens to their machine and the data becomes unavailable. The table on the right indicates the holes in the "#$ogger database that are available to 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 holes flagged 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 the left arrow key *H+. The hole number will now appear in the left window. To copy all

10

holes to the left window, use the double left arrow button *HH+. 1imilarly, if an error was 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 the following )opy In button. If the hole being copied in exists in the )entral "atabase, it must be checked out to be successfully copied in. If the hole being copied in does not exist on the )entral database, a copy of the hole will be created and stored on the )entral database for other users to view.

&.3. Co9y -ut

The )opy (ut process allows the user to view existing drill holes with their "#$ogger database. It can be thought of as checking a book out from a library. -fter checking out a hole, the user may make changes to it, but the changes cannot be reflected on the )entral "atabase *cannot check in a copied out hole+. -lso, if the hole is copied out, 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 a status window where the status of the copy out procedure will be displayed. (n the left, 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 arrow button *H+. The hole number will now appear in the )opy (ut list *on the left+. If the user wants to copy out all existing holes, use the double left arrow button *HH+. To take holes off of the )opy (ut list *on the left+, select the hole and click the right arrow button *I+, to remove all holes from the copy out list, click the double right arrow button *II+. To begin the )opy (ut procedure, click the following )opy (ut button.

11

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

&.4. Status
The status window allows you to view a list of holes from either the )entral <epository *"#)entral+ or your $ocal "atabase *"#$ogger+. "rill holes listed for the $ocal "atabase represent those holes that either have been 0)hecked (ut0 from the )entral <epository or holes that are new and were created on the $ocal "atabase through the "#$ogger. "rill holes listed on the )entral <epository are those holes that have been checked in by all users of the system.

Item 0escri9tion
)entral <epository *"#)entral+ typically located on the database. $ocal database *"#$ogger+ a client computer .ro3ect :umber #ole :umber 1tart "ate &nd "ate $ogged by record. (riginal )reator The name of the creator is taken from the sers login id when the borehole record was created. This identifier is never changed once a hole has been created. The $ocal database is a remote database located on that is typically a data collection device. The pro3ect that boreholes belong to. Borehole number. 1tart date as stored on the borehole record. &nd date as stored on the borehole record. :ame of logger as stored on the borehole The )entral <epository is the central database server and treated by many users as the 0master0

12

)urrent (wner

This identifies who has checked out a hole. The name is taken from the sers login id, re2uired when starting Borehole Manager. This defaults to 0system0 when the hole is checked in. &ither checked in or checked out. )hecked in holes can be freely used by any user and checked out holes are currently being edited by a user.

1tatus

To 6ie$ the Status% 4.

)lick -ction, 1tatus *or+ )lick the button on the toolbar.

13

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 in an organi%ation, it may be necessary to convert location information to a common grid. 7or example, it may be re2uired to produce a map using TMDs.

To change the current grid settings on the Central data:ase1 choose Calculate Common .rid under the -9tions menu and select the desired 'rid through a drop down list. - list of grid conversion formulae is available by selecting .rid Con6ersion through the /ctions menu5 here formulas may be added, modified, deleted or viewed. When the 'rid 1ettings are changed, Borehole Manager will recalculate all drill hole coordinates in the )entral "atabase and convert it to a point within the new 'rid selected using the appropriate grid conversion formula. To edit an e;isting .rid Con6ersion "ormula1 access the available .rid Con6ersions through the /ctions menu and double click on the formula to be modified. - pop!up window will appear allowing the user to make changes. To create a ne$ .rid Con6ersion "ormula, access the .rid Con6ersions through the /ctions menu 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 a formula where the user will enter the data relevant to the new formula. This
14

means specifying from which grid the conversion is from and specifying the grid 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 text boxes for both grids involved in the conversion.

3.&. (;9ort
&xport drill hole information to use with )amp, 'emcom or "atamine. This process copies the drill hole information into a format recogni%ed by the software to import. To e;9ort drill hole information1 close all other windows within Borehole Manager and select &xport from the -ctions menu. This will give the user the option of selecting which type of &xport to perform. (nce the type of export is selected, a window will be displayed where the user has to define the &xport directory *the directory 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. The window below this table will act as a progress log that will display the activity of the export process as well as any errors that may occur. The window on the left displays 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 *I+. 1imilarly if the user wishes to empty the &xport list, use the double right arrow button *II+. 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 appropriate icon next to the status window.

15

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 critical when sharing drill hole records. While your lists are refreshing, you can watch the status through the <efresh $ocal $ists window. To refresh local lists% 4. Be sure the check in and check out windows are closed. >. (n the -ctions menu, click <efresh lists... *or+ C. click (n the -ctions menu, click Begin *or+ click

16

3.4. +e9orts

<eports allow the user to view and save a number of custom created reports. To gain access to the reports window, click the <eports icon on the toolbar. This will bring up a window where there is drop down list in the upper right hand corner. The user is able to select the report they wish to view through the use of this drop down list. The option of running the report on the $ocal "#$ogger "atabase or the )entral database is selected through the use of radio buttons on the upper left hand corner of the window. (nce selected, the report will be displayed in the window and the user has the option of searching, sorting, printing or saving the report by clicking on the appropriate icon on the toolbar. If the user chooses to save the report, a window will be displayed where the user can enter the location and the name of the file that will hold the report data *in a text with headers format+. These reports are available in both the Borehole Manager and the "#$ogger applications.

17

3.5. /dministrator /ccess

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

3.<. System /dministration

3.<.1.*ser
The systems administration user dialog box is used to maintain login information.

&nter all information possible

18

3.<.2.*ser to 2rofile
-ssign each user one or more profiles. .rofiles are predefined by the Buisness -dministration Manager. &ach profile controls what menu option, window and button will be shown to the assigned user.

3.<.!.Business *nits
Business units maintain security and hole information management nits are used to maintain copy and check in;out functions

19

3.<.&.*ser Business *nits

In this dialog box you can assign business units to login names

20

4. +eference
4.1. Chec7 out 2rocess

21

22

4.2. Chec7 in 2rocess

23

4.!. Ti9s and Tric7s

#ole may only be deleted from "hlogger. <ight )lick on the toolbars to customi%e them. The status of the #ole is marked in red on the collars tabe of "#$ogger .rofiles are created with the )entury 1ystems Business -dministrator

4.&. -nline Su99ort

)entury 1ystems Technologies Inc. has made every effort to make "#$ogger intuitive5 however, if there is something you are unable to figure out, please consult the help material. The printed user guide and on!line help provide the starting point for help information. The on!line help contains all the information from the serDs 'uide. .lease ensure that the serDs 'uide and on!line help do not provide the answer you need before reaching out for further help. This will always be your fastest solution. 1upport plans may vary. 1upport options include those described in the following sections. )ontact )entury 1ystems directly if you have any Training, data conversion or custom programming re2uirements. The information stored within the "#$ogger database can be easily exported to a number of plotting programs *'emcom, .rolog;Tralog, "ataMine, 1urpac, etc.+ for further analysis. -lso, 1J$ reports can be generated directly from "#$ogger data. )entury 1ystems is committed to improving the functionality of "#$ogger with new features in future software releases. -lso, )entury 1ystems offers custom reporting. If you would like to re2uest a new feature or discuss custom solutions, please contact )entury 1ystems. 1upportKcenturysystems.net InfoKcenturysystems.net 1alesKcenturysystems.net

24

Web 1ite )entury 1ystems Technologies Inc. BEE :ewgate -ve. 1udbury (: .C- =A8 .honeF 7axF *?9=+ =E9!C@@9 *?9=+ =E9!CEE>

25

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

Dis) "*!ce $ 7

+
+el* $ 24

B
Borehole !n!ger $ 3

,
,icense $ 4 ine !**er Icon $ 7

%
%D&'( $ 6

26