At the end of last year, we hosted two webinars for a select group of mining industry experts relating to the ubiquitous data management problems experienced by mines globally. The first webinar identified the typical problems experienced by Mineral Resource Management (MRM) departments relating to data quality and the management of data, the second proposed a solution to these problems.
In December 2016, the Datum360 team nominated Daisy Chain as our local chosen charity for 2017. The charity provides a haven for children and their families who are affected by autism. The charity is also close to our head office, they have an impressive site in Norton, Stockton on Tees, in the form of a 5.5-acre farm with a variety of activities and facilities for children with autism (along with their families and carers) to enjoy in a safe environment.
Last week I spent two days in Amersfoort with 53 members of CFIHOS. The Capital Facilities Information Handover Specification project conference was an energetic and knowledgeable forum. The commitment to build a pragmatic Reference Data Library or Class Library to support handover was apparent. The event was held at ISVW.
ISVW is a school for philosophers, and although the school was a great venue, I could not help thinking that CFIHOS has largely passed the philosophical phase and the flavour of this meeting was implementation.
Our next live webinar is about using digital technology to reduce risk and cost for operating assets. In 30 minutes, we will demonstrate how Datum360's methodology and technology can help you to understand the compliance and completeness of your Engineering Information and ultimately support better decision making for your assets.
A line in the Dire Straits’ classic Telegraph Road goes something like “Then came the lawyers and then came the rules”. Is the sequence significant? Cause/effect? Do we need lawyers to manage the rules, or do we need rules to manage the lawyers?
When personal computing began it took a while for the concept of a “database” to be developed, but as soon as it was, it was very closely followed by the concept of GIGO. The sequence (cause and effect) also being particularly significant. GIGO of course, refers to that particularly database centric phrase, Garbage In, Garbage Out. So, do we have garbage because we have databases, or do we simply have databases so that we can manage the garbage? The real question is: do we really have to have the garbage?