Technical Report for the Maricunga Gold Mine - Kinross Gold

More documents

Recommendations

Info

Kinross Gold CorporationMaricunga Mine Technical ReportThe QA/QC Database Manager has certified that the database as transferred to KinrossTechnical Services on CD-R media is free of gross errors and omissions and is suitable forestimating resource and reserve estimates.14.4 Data Entry, Storage, Management and SecurityThe QA/QC Database Manager was responsible for updating and managing the ProjectDatabase (PDB). Only the QA/QC Database Manger could access, update or otherwisemodify the PDB. Regular backups were made to CD-R disks over the duration of theprogram. The final PDB was transferred to Kinross Technical Services to be used inresource modeling.14.4.1 Data EntryCollar CoordinatesThe mine survey department entered collar coordinates, drill azimuth and inclination intospreadsheets that were provided to the QA/QC Database Manager. The QA/QC DatabaseManager checked the spreadsheet data against original survey field notes prior to importingthe data into the PDB. Cross sections and drill hole composite plans were plotted usingGemcom software and were inspected by the Senior Geologist for collar and directionalerrors. Final hole depths were verified against the drill log hole depth.Downhole Survey DataComprobe provided the downhole survey data in spreadsheet format to CMM’s OfficeManager who checked the data for obvious errors. Once satisfied that the downhole surveydata was correct, the Office Manager provided the spreadsheet files to the QA/QC DatabaseManager for import into the PDB.Lithology, Alteration, Mineralization and OxidationThe Office Manager and Data Entry Clerks entered data from the field lithology logs intospreadsheets, one for each hole. A double-blind entry system was not used in recording thisdata. A 100% manual check of this data was performed at the end of the drill program.56
Kinross Gold CorporationMaricunga Mine Technical ReportAssay DataAssay results were received as digital files, identified by work order number and holenumber. The assay files included individual sample numbers allowing the samples to bematched to the sample intervals. The digital files were imported into spreadsheet files thatwere verified back to the original assay files prior to being imported into the PDB.QA/QC DataThe Senior Geologist matched assays to sample numbers on the original log and extractedthe QA/QC data from the sample stream into an excel spreadsheet which was used tomonitor QA/QC data independently from the sample stream. The QA/QC data was sortedinto worksheets for blanks, standards and duplicates. The entire file was cross-checkedbetween the Project Manager’s copy and the Senior Geologist’s copy. Once satisfied thatthe data was free of error it was sent via email to Dr. Smee for final analysis.14.4.2 Data StorageThe PDB was established and maintained using Gemcom modeling software. The PDB wasbacked up on CD-R media on a regular basis for the duration of the field program. Once thePDB was fully updated with all the results collected during the 2002-2003 programs, the datawas copied and forwarded to Kinross Technical Services in CD-R format. This database isreferred to as the Final Database (FDB).In addition to the digital files, all available hard copy data was organized and inventoried ona per hole basis. This information was copied in triplicate with one copy forwarded to KinrossTechnical Services, one copy forwarded to Bema and a final copy stored at the MaricungaMine. Original hard copy data was packaged and stored at the CMM office in Copiapó.14.4.3 Data Management and SecurityOnly the QA/QC Database Manager had the necessary file access permissions to updatethe PDB. Only Kinross’ Manager of Technical Services could access and modify the FDB.57
Page 1 and 2:
Technical Reportfor theMaricunga Go
Page 4 and 5:
Kinross Gold CorporationMaricunga M
Page 6 and 7: Kinross Gold CorporationMaricunga M
Page 106 and 107:
Page 108 and 109:
Page 110:
show all

Technical Report for the Maricunga Gold Mine - Kinross Gold

Create successful ePaper yourself

Delete template?

Save as template?