Telematics and Drilling Data on a Used Rig: What Actually Transfers?

1. Understand the four layers of connectivity

A functioning system normally requires onboard sensors and controllers, a gateway or communication device, portal or local-server software, and an authorised account or subscription. Failure at any layer can make reports unavailable. Sandvik describes cloud and on-premises offerings, while Epiroc Certiq documentation for selected FlexiROC models illustrates metrics such as fuel, drill metres, utilisation and litres per metre.

A visible antenna proves only that an antenna is present. It does not prove that sensors are calibrated, the gateway is registered, the subscription is active or the portal accepts data from the serial number. The inspection should therefore assign a verified, failed or not-tested status to each layer rather than giving the whole system one label.

• Sensors and machine controllers
• Gateway, modem, SIM or mine network
• Portal, licence and authorised user

2. Request a digital configuration record

Tie the record to the machine serial number. It should show controller, display, sensor and gateway part numbers; software and firmware versions; installed package and subscription level; last successful upload; report types; export formats; drill-plan and MWD capability; onboard storage; and fault or update history. Ask exactly which MWD parameters are measured rather than accepting the phrase MWD capable.

Take screenshots of the version, option, storage and connection pages during the same inspection. Compare them with authorised-service records and the physical gateway label. If a component was replaced, request evidence that it was configured for this machine and that its data continuity or calibration was checked afterward.

• Hardware and software identity
• Current subscription and expiry
• Available data, reports and export formats

3. Define ownership and privacy before transfer

Historical reports may contain production, personnel or location information belonging to the previous owner. Agree which machine-health records may be shared, which site data must be removed, how the serial number leaves the seller's fleet and who controls future access. Never transfer an informal shared password; use the OEM or authorised provider's account-reassignment process.

• Separate machine history from confidential site data
• Document deletion, retention and handover
• Create buyer-controlled credentials

4. Prove the full data path live

During inspection, show the serial number on the display and record the communication timestamp. Create a new operating event, confirm it reaches the portal or local server, and export a sample utilisation report. Where supported, upload a small drill plan, perform a controlled hole or simulation, and retrieve the as-drilled or MWD result. Record latency, signal conditions and every communication fault.

Use a unique test name and timestamp so the new record cannot be confused with historical data. Open the exported file and check that identifiers, units and values are plausible. Where no signal is available, test local buffering and later upload if the system is designed for that workflow; otherwise record the path as unverified.

• New event from machine to report
• Plan upload and result download where fitted
• Unedited evidence of timestamps and alarms

5. Check destination and integration compatibility

Confirm cellular bands, SIM ownership, roaming, Wi-Fi or mine-network requirements, GNSS correction, radio permissions, cloud availability, cybersecurity policy and third-party fleet integration. Some operations require data to remain on site; others use cloud subscriptions. Ask what new hardware, licence or commissioning is needed when the rig leaves the seller's network and country.

Ask the buyer's IT and operations teams to review the proposal before shipment. They should define permitted network connections, user roles, data retention, backups and incident contacts. A technically functional modem may still be unacceptable under the mine's security policy or unable to exchange data with its maintenance and planning systems.

• Network and regional compatibility
• Cloud versus on-premises policy
• API, export and third-party integration

6. Use telemetry as supporting evidence

Fuel-per-metre, utilisation and alarm history can strengthen due diligence, but they do not replace inspection. Data gaps may reflect lost communications, hours may use different definitions, and easier geology may produce better metrics. Combine telemetry with maintenance records, oil analysis, fault-code review, component checks and a loaded drilling test before drawing a condition conclusion.

Compare trends, not isolated best values. A gradual change may justify a closer inspection, but it is not a diagnosis by itself. Ask whether sensors were calibrated, firmware changed, operating modes reclassified or the machine moved to different geology during the period. Document alternative explanations before assigning repair cost.

• Compare definitions and time ranges
• Investigate gaps instead of guessing
• Cross-check digital and physical evidence

7. Handover scope and evidence limits

The contract should list telemetry hardware, licences, account assistance, exports, configuration backups, drill-plan software, integration, training and commissioning. OEM sources describe capabilities that vary by model, year, hardware, market and subscription. They do not prove that a unit advertised here includes telemetry, MWD, transferable access or a particular data history.

• Write included digital assets into the sale
• Mark unavailable access as unverified
• Obtain OEM or specialist support for critical transfers