Laserfiche WebLink
�7- <br />Table 2 -1: Drill Holes Selected for Checking Original Data against the Database <br />Drill Hole ID <br />Hard Copy <br />in Cabinet <br />Comments <br />10 -14 -S2 <br />26 <br />No quality data in file. Thickness data only <br />11 -14 -S9 <br />213 <br />Original coal quality available. Not in DB — in mined out area of pit <br />88 -16 -08 <br />2C <br />Original coal quality available <br />UL -95 -04 <br />3A <br />Original coal quality available <br />UL -95 -04 <br />3A <br />Original coal quality available <br />WP -00 -04 <br />313 <br />Original coal quality available <br />WP- 00 -04A <br />3B <br />Rotary hole <br />DH -110 <br />3C <br />No coal quality data in file <br />DH -155 <br />3C <br />No coal quality data in file <br />DF -56 <br />1A <br />In close proximity to C -04 -24 <br />C -04 -20 <br />4C <br />Original coal quality available. E -log and drillers log depths <br />inconsistent <br />C -04 -24 <br />4C <br />Original coal quality available. E -log and drillers log depths <br />inconsistent <br />C -04 -30 <br />4C <br />Rotary hole <br />C -04 -36 <br />4C <br />Original coal quality available. I seam mis- labelled. E -log and drillers <br />log depths inconsistent <br />In the recent C -04 series TS noted a number of inconsistencies between the original <br />'from ply on the laboratory sheets when compared to the database print out. CCC <br />explained that the 'from _to' data were adjusted in the database to match the depths in the <br />downhole e� -logs. CCC felt that the e -logs gave a more precise depth than the driller's log. <br />TS was concerned to note that discrepancies increased from ±1 ft near to surface to ±6 ft at <br />the bottom of some deeper holes. CCC will need to document the reasons for these <br />discrepancies. <br />3 ACCESS DATABASE - OVERVIEW <br />Database integrity (both in terms of data validity and data reliability) is essential at any <br />operation. With large databases it is usual to have one person appointed as a Database <br />Manager who has overall responsibility for maintaining and updating the database(s). <br />Generally, other users are only allowed database read access. <br />RIO <br />TINTO <br />BR3273: FINAL Version: 1 2 T c:d `-„i«5 <br />