Mine Instrumentation Telemetry: An RFQ Responsibility Matrix

Use the working record

Download the editable worksheet. Record the actual evidence and responsible reviewer against each relevant row. The empty results are inputs for your project, not completed tests. Add the equipment identity, operating period and reference method before assigning an outcome. Retain unsuccessful checks and the evidence from any repeat after correction.

Name the decision and responsible discipline

Identify the actual system being monitored and the decision its record supports. Tailings instruments may serve an engineer's interpretation and trigger-action process. Ventilation observations serve the mine's responsible ventilation and operating teams. The RFQ should name the relevant authority and approved design basis for each included system.

List the physical assets and existing instruments. Record the approved point identity, position, quantity and reference. A generic request for remote monitoring leaves important questions unresolved, including what the instrument measures and who determines whether its reading is suitable for the intended decision.

Separate instrument supply from data integration

Identify who selects and supplies the instrument, who installs it and who verifies the underlying measurement. The integrator then needs the actual output, interface documentation and configuration needed to acquire that reading correctly. These responsibilities can sit with different parties and should remain explicit in the commercial scope.

Record any existing logger or controller between the instrument and the proposed platform. Its scaling, timestamp and quality behaviour may affect the delivered record. Acceptance should trace the value through each relevant layer instead of comparing only the final dashboard with an undocumented expectation.

Specify the data contract point by point

For every channel, define identity, quantity, unit, range, acquisition interval and quality states. Include the reference or datum where it is necessary for interpretation. Record whether the value is raw, compensated or calculated, and identify the configuration or formula version that applies.

Distinguish unavailable, suspect, out-of-range and deliberately isolated observations. The responsible engineer should approve how those states appear in the review and response process. A missing value should not silently become zero or a carried-forward apparently current observation.

Define trigger ownership separately from notification

The authorised engineering owner sets the relevant interpretation and trigger basis. The telemetry scope records the accepted rule, source, effective version and intended recipients. A configuration change should retain its approval and history rather than simply replace a threshold in the application.

Notification delivery, acknowledgement, technical assessment and operational action are separate functions. The RFQ should identify who owns each stage and what evidence is retained. A message reaching a phone does not establish that the required engineering review or site response occurred.

Test the failures relevant to the supplied architecture

Identify power, local acquisition, radio, backhaul and application dependencies. Define what remains recorded during each relevant interruption and how stale information is displayed. Recovery should preserve original acquisition time and the quality needed to interpret the historical sequence.

Use an approved test or simulation method. Certain live instruments or operating functions may require a controlled exercise instead of deliberate interruption. Label simulated evidence and verify restoration. The mine's responsible authority determines the safe method and the conditions under which the result can be accepted.

Include field access and maintenance in the quotation

The mine defines contractor permissions, work windows, isolation and location-specific requirements. Include the appropriate local specialists and the practical route for subsequent instrument checks. A feasible initial connection does not establish that a remote point can be maintained under normal operations.

Identify spares, configuration records and replacement procedures. The quotation should distinguish equipment, installation, specialist work, communication and recurring support. Use current supply information for the actual part and route rather than a generic delivery promise.

Preserve responsibility when records cross systems

A source logger, integration platform and engineering review tool may each create timestamps or calculated values. Retain their relationship and the authoritative source for each field. Test an export through the receiving workflow so the responsible reviewer can interpret it independently of the live dashboard.

Agree user access, change permissions and retention. The person who maintains a communication subscription need not have authority to alter an engineering trigger. The role model should reflect the mine's actual governance and preserve an audit of configuration changes.

Accept each discipline with its own evidence pack

Build a schedule containing expected result, reference, test method, witness and observed outcome for every relevant function. Keep failed checks and corrective work. A common platform test can verify transport and access, while instrument-specific interpretation and response require the appropriate separate sign-off.

The final handover should identify accepted points, remaining dependencies and the owner of every open item. This makes the RFQ comparable across suppliers and gives the mine a clear basis for later changes without allowing a shared telemetry layer to obscure discipline-specific engineering responsibility.

Connect the decision to the project

Use Mining optimization, Tailings dam monitoring, Mining to place this task within the wider installation. Bring a recent operating record and identify the decision that the proposed measurement should support. A focused discussion should establish the first boundary, the responsible site participants and the evidence needed before expanding the scope.

Agree who maintains the point register and who can change interpretation rules. Preserve the previous version when a device, product, reporting period or responsibility changes. During handover, demonstrate an export that another authorised person can reconcile without relying on the dashboard operator to explain missing fields.

Discuss the scope with addanode using the actual site information, available interfaces and proposed acceptance record.

Sources and method

NIST SP 800-82 Revision 3 provides architecture and dependency background. The matrix is a project procurement method; instrument design, engineering interpretation and operational thresholds remain with the mine’s appointed responsible authorities.

Frequently asked questions