PNG1 125.jpg

OUR PHILOSOPHY

The one constant that underpins the myriad of activities that support and enable exploration and mining projects throughout their life, (the Mining Lifecycle) is the technical data on which all significant decisions are based. The following observations reflect our philosophy at GDD as to how that data should be managed.

Why? NOT because we are fixated on making sure everything is correct, but because if you do a job efficiently and well in the first place, you generally then only have to do it once, which makes things happen not only faster, but with a greater degree of confidence, which means it will cost less in the long run, but more importantly do more to ensure the success (and profitability) of the project!

For a more detailed explanation on our data management philosophies, please have a look at our Technical Data Management Philosophy document.

General Philosophies

1. The technical database underpins all of the significant technical decisions throughout the entire mining life cycle.

2. Collect - Manage - Analyse - Profit!

3. All significant decisions need to be based on sound, valid technical data, but particularly on the same, single version of that data.

4. Choose and use the best tools for each specific job, but make sure they are ‘singing off the same sheet of music.’

5. Invest in the ‘time, the tools, and the training’, whether in-house or externally, to COLLECT, MANAGE and ANALYSE your technical data asset in line with the value of the project that depends on them.

Data Collection

6. Enter and integrate your data directly into your primary database wherever possible, at the place and time the data is originally collected.

7. Collect, enter and instantly integrate into the database ANY additional data and information relevant to the activity at hand.

8. Get your data into your database from the start. Warts and all! Then have the database help you identify and correct the problems, at which point it will be given the big green tick and accepted as ‘good stuff’!

9. Provide tools, training and technologies that allow you use your geologists as geologists, not lithological librarians or dig-line data clerks.

Data Management

10. Provide data integrity checking functions in addition to validation, to ‘prove’ the data is still in good shape at any point in time.

11. Provide tools that make personally identified problems in the database very visible so they won’t get ignored.

12. Make your people responsible and accountable for the competent management of your technical data. The best system in the world will not effectively compensate for idiots.

Data Analysis

13. Accessing, filtering, sorting, grouping, exporting and reporting data should be intuitive and easy!

14.  Our task is to make the selection and export or sharing of data subsets easy, so other packages can do what they are good at.

Specific Technical Philosophies

15. Configure all NUMERIC columns (unless they are Key or Unique Index columns) in your databases to allow NULL values, and make tis the default value for the column.

16. Configure all CHARACTER columns in your databases to NOT allow NULL values, and make the default value for the column an ‘empty string (‘’)).

For a more detailed explanation on our data management philosophies, please have a look at our Technical Data Management Philosophy document.