Application of Industrial Routers, Industrial Gateways, and Industrial Switches in the Mining Industry
Updated: Oct 12
Conceptual illustration only. The IP67 label is not a product rating or certification.
Background and operational requirements
A mine may need to carry equipment telemetry, environmental measurements, maintenance access, and operational communications across shafts, tunnels, processing areas, and remote offices. These flows should not be put into one undifferentiated “industrial network.” The roles of a router, gateway, and switch are different, and a safe design begins with the location and consequence of each traffic path.
Underground geometry, moving equipment, power, dust, moisture, and potentially hazardous atmospheres make site validation essential.
Equipment described as “industrial” is not automatically suitable for every zone or approved for a mine's safety system.
Device roles and interfaces
An industrial switch joins Ethernet devices within a local network. Its ports, fiber options, VLANs, redundancy protocol, power supply, and environmental rating need to match the installed segment. An industrial router forwards traffic between networks, perhaps over a wired or cellular WAN. VPN, firewall, dual WAN, and remote management are model-specific options, not universal features. A protocol gateway performs a documented conversion or data-collection role between a particular field interface and an application. IP routing alone does not turn a PLC register into a cloud message.
The field controller remains responsible for local machine and safety logic. A loss of the WAN or enterprise service must not silently change an approved safety response. Define the local mode with the mine's controls and safety owners.
Router
A router connects the mine network to another network or WAN when the exact model and configured path support it. Confirm the uplink, routes, permitted destinations, failover behavior and supported access controls against the device documentation and site design.
Protocol gateway
A gateway may collect or convert data across specified field and application interfaces. Confirm protocol versions, data mapping, timestamps, error handling and disconnect behavior. Routing alone does not provide protocol conversion.
Industrial switch
A switch joins local Ethernet devices. Confirm required ports, media, segmentation, power delivery and redundancy features on the exact model. Test the installed segment under its intended traffic.
Mining application scenarios
List each sensor, controller, camera, vehicle interface, and operator terminal with its physical zone and application owner. Then draw the intended path to the control room or other destination. Specify direction, protocol, update rate, permitted commands, timing, power, and behavior on link loss. Separate safety-relevant instrumentation from routine monitoring and business reporting; assess each against the mine's governing design and regulations.
Equipment and environmental telemetry: identify each sensor, owner, update need, destination and response to missing or stale values.
PLC/SCADA integration: document the exact field interface and data mapping; keep control ownership explicit.
Mobile drills and vehicles: survey the radio path with intended endpoints, movement and operating conditions.
Video and operator traffic: define viewing and retention needs and whether traffic shares a path with control.
Emergency communications: record endpoints, local fallback and mine-approved behavior; do not infer safety-system approval from network connectivity.
Maintenance and energy planning: scope remote access and meter data by owner, destination, retention and permitted action.
Workflow / endpoints | Path and device roles to verify | Operating boundary | Acceptance evidence |
|---|---|---|---|
Equipment and environmental telemetry | Sensor to its documented interface; gateway only if conversion is required; routed path to the approved application. | The sensor value and alarm meaning remain defined by the mine application owner. | Check identity, units, completeness, timestamps and behavior for missing or stale data. |
PLC/SCADA integration | Controller or PLC through the documented interface and mapping to the receiving application. | Keep local control and safety logic with the approved controller. | Compare mapped values and any permitted commands with the source and approved point list. |
Mobile equipment and video/operator traffic | Mobile endpoint through surveyed radio access and the site backbone to its intended application. | Coverage and handover depend on the installed design and operating route. | Test intended endpoints and traffic while moving through representative routes and failure conditions. |
Emergency, maintenance and energy data | Mine-approved communications path; controlled maintenance entry; meters to the assigned monitoring application. | Do not bypass local fallback or grant broad access from business systems. | Verify allowed destinations, operator indications, access logs, missing-data handling and recovery. |
Site constraints and their consequences
Underground radio coverage is a system of access points, antennas, repeaters, cabling, and site geometry. A cellular router at one cabinet does not provide tunnel-wide coverage. Survey the planned positions and representative operating conditions. Fiber or another fixed backbone may be appropriate for stationary segments; radio may serve mobile endpoints when coverage and handover have been validated.
Before installing equipment in a classified or potentially explosive area, confirm the applicable area classification and each exact device's certificate, marking, installation conditions, and enclosure requirements with the site authority. IECEx provides the conformity-assessment framework and certificate information [1]. A broad product-family statement is not enough.
Record dust, moisture, vibration, interference, temperature, corrosive exposure, available power and cable routes at the intended positions. Compare these observations with the exact device installation documentation. For a classified or potentially explosive area, confirm the zone and each device’s certificate, marking and installation conditions with the mine authority [1].
Constraint | Design input / owner | Commissioning check | Evidence to retain |
|---|---|---|---|
Tunnel geometry and moving endpoints | Survey points, antennas, cables, expected routes and endpoint locations. | Check coverage and handover along representative operating routes. | Survey records, tested positions and observed application behavior. |
Dust, moisture, vibration and temperature | Record actual conditions at each installation position and compare with exact model limits. | Inspect the installed enclosure, connectors, mounting and cable entries against documentation. | Model documentation, installation record and site inspection. |
Classified or potentially explosive area | Mine authority supplies zone classification and applicable installation conditions. | Match the exact certificate and marking to the location and installation method. | Certificate, marking, installation conditions and authority acceptance [1]. |
Legacy interfaces and data mapping | Controls owner defines source protocol, version, point list, scaling and receiving application. | Test representative values, units, timestamps, errors and any permitted command. | Approved interface map, test record and application owner sign-off. |
WAN, local segment or power loss | Controls and operations owners define what must remain local and expected operator indication. | Interrupt representative links and restore them; verify local behavior, buffering and recovery. | Approved failure criteria, event record and recovery result. |
OT security and remote access | Mine security owner defines identities, destinations, approval, logging and change process. | Test allowed and denied paths, account revocation, logging and incident procedures. | Access rules, test record and change approval [2]. |
Design responses and acceptance tests
Segment the network so a maintenance laptop or analytics service cannot automatically reach control endpoints. Give remote users named identities, limited destinations, logging, and a managed approval process. NIST SP 800-82 emphasizes adapting security controls to OT reliability, performance, and safety requirements [2]. Keep the minesite's own incident and change procedures authoritative.
At commissioning, test actual values, alarms, and approved commands end to end. Interrupt the WAN and a representative local segment. Confirm what data is buffered, what operators see, what functions remain local, and how the system recovers. A network link light or VPN status alone cannot establish application continuity. For cellular site checks, use the industrial 5G/LTE router validation checklist alongside the mine's own requirements.
The acceptance record should show the requirement, the test performed and who accepted the result.
Evaluate benefits against a measured baseline
Mine photographs and videos can show the setting, but they do not establish numerical benefits, a named deployment or hazardous-area approval for the selected equipment. Obtain site measurements and the exact certification record.
Choose the outcomes the mine expects before installation, then record a baseline using the same definitions, configuration, workload and observation period planned for the follow-up. Compare measured results after commissioning. Keep measured changes separate from assumed savings: connectivity by itself does not establish lower downtime, higher output or improved safety.
Device comparison and selection evidence
This matrix compares responsibilities and the evidence to check; it does not assign universal specifications to a device category. Fill the evidence column from the exact model documentation and the mine’s acceptance criteria.
Dimension | Router | Protocol gateway | Industrial switch |
|---|---|---|---|
Primary role | Routes traffic between networks when configured for that path. | Collects or converts data across documented field and application interfaces. | Connects Ethernet endpoints within a local network. |
Interfaces | Confirm wired or cellular uplinks and supported interfaces on the exact model. | Confirm the exact serial, Ethernet or other field interface required. | Confirm copper, fiber or other required port media on the exact model. |
Protocol and data handling | Verify supported network protocols and route configuration. | Verify protocol version, point mapping, scaling and application format. | Verify Ethernet and management features required for the segment. |
Function boundary | IP routing does not by itself translate a field value or data model. | Conversion is limited to documented interfaces and tested mappings. | Layer-3 routing is available only where the exact model documents it. |
Redundancy and recovery | Test route monitoring, configured failover and recovery. | Check buffering, error handling and recovery across source or application loss. | Test the installed redundant path or topology as configured. |
Security functions | Confirm supported VPN, firewall and access controls and their configuration. | Confirm identity, update and access controls for the gateway and its data. | Confirm supported management, segmentation and port controls. |
Environmental limits | Match exact model limits and installation rules to the site observations. | Match exact model limits and installation rules to the site observations. | Match exact model limits and installation rules to the site observations. |
Hazardous-area use | Check exact certificate, marking and installation conditions with the mine authority. | Check exact certificate, marking and installation conditions with the mine authority. | Check exact certificate, marking and installation conditions with the mine authority. |
Power and mounting | Verify supply, mounting, antenna placement and cable route. | Verify supply, isolation, mounting and field wiring. | Verify supply, mounting, fiber/copper layout and any required PoE. |
Acceptance evidence | Test permitted routed traffic, loss behavior and recovery end to end. | Test source-to-target data identity, completeness, timing and error behavior. | Test the installed segment, configured features and recovery under expected traffic. |
Illustrative deployment patterns
The following four patterns abstract the historic examples into design discussion. They are not verified customer deployments, product endorsements or performance results.
Underground backbone with legacy-system integration
A fixed underground backbone connects local switching segments. Add a gateway only for documented legacy interfaces and point mappings. Verify the chosen redundancy method and application path on the installed configuration.
Mobile machinery on a surveyed radio path
For drilling rigs and other mobile machinery, as a design example, assess private 5G, Wi-Fi, LTE or another wireless or mobile path for the planned vehicle routes. These are illustrative options only; they do not describe a Wavetel customer or product deployment and make no performance claim. Test the intended endpoints, handover, application traffic and link-loss behavior along representative routes.
Segmented underground monitoring
In a wireless mobile-network design, sensor and vehicle traffic reaches a monitoring application through a defined local segment and routed path. Separate destinations by function, keep local control responsibility explicit and test alarms and remote access.
Remote environmental sensing
An LPWAN such as LoRaWAN may be evaluated for suitable low-rate telemetry, with a gateway to the selected backhaul. Low-rate sensors at a remote location report through a suitable local interface and selected backhaul. Verify data identity, timing, power, missing readings, maintenance access and recovery for the actual installation.
Treat each architecture as a hypothesis until its route and failure behavior are proven at the site.
Future options and staged recommendations
Base expansion on requirements that have changed: endpoints, traffic, software support, security and recovery. Evaluate a candidate interface or technology with compatibility checks, a controlled pilot and owner-approved acceptance criteria before extending the design. Do not assume a future network generation or feature will be suitable without those checks.
FAQ
Does one 5G router cover an underground mine?
No such coverage follows from a router specification. The radio design needs an underground survey, suitable infrastructure, and tests with the intended mobile devices and traffic.
Are all industrial routers approved for explosive atmospheres?
No. Approval depends on the exact device certification, zone classification, installation method, and jurisdiction. Confirm all of these with the mine's authority before selecting equipment.
Can a router replace a protocol gateway?
Only if the chosen device has the required documented conversion function and passes tests with the exact field protocol, data mapping, and receiving application. Routing alone cannot do the conversion.
Which result should be measured first?
Measure whether the intended application receives complete, timely, correctly identified data under normal and failure conditions. Coverage and throughput matter because they support that outcome, not as stand-alone proof.
Does a protocol gateway replace a PLC or approved mine safety system?
No. A gateway may collect or convert data where its documented interfaces and mapping fit, but local control and approved safety logic remain with the responsible systems. Confirm that boundary with the mine’s controls and safety owners.
What must keep working and what should be tested when the WAN fails?
Define the functions that must remain local and the alarms or records operators need. Interrupt the WAN and a representative local segment; verify local control, operator indications, buffering and recovery against the mine’s approved criteria.
