The aim of this project is to develop common naming conventions for the different types of mining technology across different equipment types and across different tasks and then use that language to prioritize where our efforts should be.
This project will determine and provide a common taxonomy (categorization, generic framework) and definitions for mining production capabilities (operating functions, processes) and application and control systems that support the production capabilities, primarily focusing on surface mining. It is intended to be forward-looking.
This categorization is intended to be a first step to establish a common understanding, which can be used to support and drive further conversations within GMG in a targeted way, identifying common system integration areas and issues, where further collaborative efforts are needed, and identifying what issues are industry-wide versus what should be left up to the individual operator and OEM relationships. Having this common language and reference that will help operators, suppliers, and other parties communicate about their needs within determined boundaries.
This project will be led by the Data and Interoperability Working Group.
BACKGROUND
Common language was also one of the top challenges identified throughout the 2022 Mine Operator Roundtables and Working Group Workshops, particularly within the context of integrating data from multiple sources and sensors and vendors (read the report). This discussion occurred in some form in all of the Mine Operator Roundtables and many of the workshops that were focused on other topics such as asset management, mineral processing, sustainability, and underground and surface mining, emphasizing that this is a key challenge across all aspects of mine production.
OBJECTIVE
The objective is to agree on common language and how things fit together, and based on that, vote on different priorities for where we need to have data sharing, open data, or interoperability.
SCOPE
Note: At the time of proposing the project, there is still a need to agree on the foundational language and terminology within the context of this project (e.g., capability, activity, function application, system, product). It is expected to be a key discussion in project planning and definition after this project is launched.
MINING SCOPE
In Scope
Out of Scope
CONTENT AND VISION
In Scope
Out of Scope
DELIVERABLES
The expected output is clear documentation of a common taxonomy and definitions. Because this project is time-sensitive, and this type of work has a risk of becoming a long-term, more theoretical exercise at the expense of practical usefulness, it is proposed that it will be produced in stages with multiple checkpoints to confirm its usefulness. Further, because it is forward-looking in its nature, it is expected that there will be a need to revise and produce different versions in steps. Between each step, the scope and process should be revisited.
Depending on the initial outputs, the project could be a series of less formal outputs (i.e., following an approval process like white papers) that are ultimately compiled into a more formal peer-reviewed guideline with a short revision cycle.