Equipment loses its connection to dispatch
Telemetry and vehicle positions arrive late or disappear at particular mine levels.
Operational network for open-pit mining
We design data networks for mobile equipment, telemetry, dispatch, and remote units across a changing mine layout. We account for mine levels, active working areas, terrain, power supply, and backbone links. Where needed, a field pilot validates key assumptions. Acceptance uses agreed field and route tests.
Backbone → radio layer → mobile client → remote unit → test route
A mining network carries data between mobile equipment, remote units, and application systems. Its architecture accounts for current and planned mine levels, unit relocation, available power, and alternative backbone technologies. Fleet management and dispatch systems remain separate applications; this solution covers data infrastructure.
Signs that a solution is needed
Telemetry and vehicle positions arrive late or disappear at particular mine levels.
As the mine layout changes, existing unit locations no longer cover operating routes.
It is not possible to quickly bring fiber-optic communication lines to the observation point, sensor or post.
The problem is visible only after the complaint, and there is no up-to-date coverage map or network event log.
Conditions of the site
Terrain blocks line of sight and creates local coverage gaps.
Nodes have to be moved or added as the site develops.
Equipment, enclosures, antennas, and mounts are selected to suit operating conditions.
Solar modules, batteries and power consumption are calculated for remote points.
Masts and installation points are selected according to the terrain profile, visibility zones and access for maintenance.
The antenna and terminal on the machine should work at vibration, turns and different orientations of the equipment.
Scenarios
Transfer tasks, status and coordinates between the machines and the control system.
Collection of equipment parameters and production events from remote nodes.
Video transport from fixed and temporary locations with sufficient bandwidth.
Access work applications and data on service routes.
Communication with posts, pumping stations, warehouses and other dispersed points.
Architecture
Fiber-optic links, PtP/PtMP wireless links, or other backhaul between the core and remote areas.
Base stations, mesh nodes, sector or directional antennas.
On-board terminal and antenna system on dump truck, excavator or service machine.
Dispatching, telemetry, video and other technological systems.
Monitoring, logging, redundancy and up-to-date coverage map.
Choice of technology
| Mechanism | What it does | What we check |
|---|---|---|
| Industrial Wi‑Fi network, including mesh topology | Provides mobile access and a flexible RF layer where client devices, terrain, and the frequency plan are suitable. | Terrain, vehicle speed, hop count, client compatibility, capacity, and frequency planning. |
| PtP / PtMP | Creates fixed wireless backbone links to remote areas. | Line of sight, path profile, bandwidth, and redundancy. |
| Private LTE network | It can be used as a mobile radio layer in a large area with an available frequency resource and compatible terminals. | Spectrum and regulatory conditions, devices, latency, integration, operations, and project economics. |
| Fiber-optic links | Provides a predictable support line where laying is possible and justified. | Route, line protection, construction dates and future work changes. |
Stages of the project
Collect current and planned mine levels, routes, units, equipment, and system requirements.
Check the terrain, visibility, RF environment, mast sites and power options.
Model coverage, backbone links, relocatable units, and onboard equipment.
Check critical areas and movement of real equipment before scaling.
We mount support and field nodes, configure transport and monitoring.
Perform route tests and define how coverage maps will be kept current.
Results of the project
Acceptance
| Criterion | How to check | Where we document |
|---|---|---|
| Coverage | Drive agreed routes and mine levels to verify coverage. | Map of actual coverage and log of coordinates. |
| Telemetry | Data transfer from onboard equipment to the application system. | Loss, delay and continuity of the session. |
| Backbone | Load test of fixed and wireless transport channels. | Bandwidth, latency, availability, and failover results. |
| Change of topology | Check the agreed failure or transfer of a field node. | Documented connectivity recovery and operational procedure. |
Operation
The state of the base, mesh and onboard units is controlled centrally.
Coverage is recalculated and checked after significant changes in geography.
Critical components, configurations and replacement procedures are fixed in the regulations.
The placement of nodes provides access, safety of work and diagnostics.
The schedule is defined after reviewing project inputs and, where necessary, surveying the site. Design, delivery, installation, commissioning, and acceptance are planned separately.
Cost depends on location, areas to be covered, the client device mix, cabling and backbone condition, equipment, work, and integrations. We document the estimate after defining the project scope.
Response targets, support arrangements, monitoring, spare equipment, and restoration procedures are agreed separately according to the criticality of operations.
Questions and answers
In some scenarios, Wi‑Fi may be a suitable radio layer, but there is no universal replacement for LTE. The choice depends on the area and terrain, speed and routes of equipment, application requirements, available frequency resource, onboard devices and operational model. Wi‑Fi, private LTE network, wireless bridges and fiber-optic communication lines can be combined on one site if the applicability of each element is confirmed by calculation and field checks.
Mesh describes the topology and data paths between nodes rather than a universal alternative to Wi‑Fi. Conventional access points usually connect to an existing backbone; mesh can use radio links between nodes. Suitability depends on equipment, wireless hop count, required capacity, routing, and behavior when nodes fail, move, or are added.
Project inputs include the current and planned layout, vehicle routes, possible unit relocation or expansion sites, and available backbone options. We define how diagrams, configurations, and RF models will be updated. Significant movement of active working areas triggers field checks of critical areas and routes. Results inform the next agreed infrastructure change.
We first establish power demand, operating schedule, climate, and maintenance access for the remote unit. Generation, batteries, cabling, protection, and required autonomy are then calculated. Solar or other independent power is not selected automatically: its suitability must be validated through energy calculations, placement conditions, and a maintenance plan for that location.
No. This solution covers data transmission infrastructure rather than fleet management software development or implementation. Dispatch, telemetry, and other applications define latency, packet loss, availability, and mobility requirements. The network project records these requirements and verifies data transfer through agreed tests; application functionality remains outside this offering.
Tests use the target onboard terminal, antenna, mounting location, and an agreed route covering representative site conditions. Coordinates, network metrics, connection events, and application behavior are recorded under the approved test program. Operating speeds, conditions, and acceptance criteria are agreed in advance so that results apply to the tested configuration.
A field pilot is considered when calculations leave material uncertainties, such as complex terrain, new onboard clients, uncertain line of sight, independent power, or combined technologies. Before the pilot, we document the assumptions, configuration, route, and acceptance criteria to be tested. A pilot informs design or rollout decisions; it does not replace detailed documentation, surveys, or final network acceptance.
Provide site coordinates and boundaries, current and planned mine level maps, equipment routes and speeds, and fixed and mobile unit lists. Include application connectivity requirements, existing backbone, spectrum conditions, power supply, masts, onboard terminals, and antennas. Note seasonal, access, and installation restrictions affecting surveys and pilots.
The next step
Send site coordinates, current and planned mine levels, and the equipment and systems needing connectivity. We will propose a survey approach and pilot.
Material prepared by Connectum technical team · updated: August 2026