Harsh Sites, Mixed Protocols
A metals or mining operation rarely runs one protocol end to end. Haul trucks and mobile fleet equipment report over one set of protocols, fixed crushers and conveyors over another, and processing plant systems - often decades old - over whatever the original integrator specified. OPC UA sits next to Modbus sits next to DNP3, each with its own addressing scheme, update cadence, and notion of data quality.
No common structure connects a haul truck's telemetry to a crusher's status to a plant control system's setpoints. Each is legible on its own; none of them are comparable to each other without someone manually reconciling formats first - and that reconciliation does not scale past a handful of assets.
Constrained Links Change the Math
Pits and remote sites are rarely on the same network as a modern manufacturing plant. Wireless links strain across open-pit distances; some sites depend on satellite connectivity that was never designed for continuous high-volume telemetry. The equipment that generates the most data - haul trucks and mobile fleet assets moving across a pit - is frequently the equipment with the least reliable connection back to anywhere.
This changes what "reliable" has to mean at the edge. A data plane that assumes continuous connectivity will lose data silently on exactly the assets that matter most. Local buffering has to persist readings before acknowledgment, so an intermittent wireless or satellite link translates into replayed data on reconnection - not a gap in the record.
Edge Normalization and Volume Reduction
Fleet and process sensors generate a large volume of readings, and most of them represent no meaningful change in equipment state. Feeding all of it to central analytics over a constrained site link wastes bandwidth on noise and buries the readings that actually matter.
Report-by-exception with configurable deadband thresholds filters insignificant changes before data ever leaves the site. CEL expressions compute derived values and aggregates at the edge - so a crusher's throughput trend, for example, can be derived locally rather than reconstructed later from raw sensor streams. What crosses the constrained link is signal, not volume.
Fleet-Wide Consistency
Comparing a haul truck's cycle time against a crusher's throughput, or one shift's performance against another's, only works if every asset speaks the same structure. Mixed-protocol ingestion at the edge normalizes OPC UA, Modbus, and DNP3 sources - mobile and fixed alike - into one ISA-95-aligned namespace at the point of acquisition, regardless of vendor or equipment type.
Once every asset publishes into the same namespace, fleet-wide queries stop requiring per-protocol, per-vendor translation logic. A dashboard built to compare crusher performance across a site works the same way whether the underlying equipment reports over OPC UA or DNP3, because the protocol difference was resolved at the edge, not in the query.
What Changes
When first-mile structure is applied at pit and plant alike:
- Mobile fleet equipment and fixed plant systems publish into one consistent namespace, not isolated silos
- Constrained wireless and satellite links carry filtered, meaningful signal instead of raw volume
- Intermittent connectivity at remote sites produces buffered, replayed data - not silent gaps
- Fleet-wide analytics compare equipment, shifts, and sites without a reconciliation step first
Metals and mining operations do not get to choose harsh conditions or protocol diversity - both come with the terrain. What they can choose is whether the data plane resolves that diversity at the edge, once, or leaves every downstream system to solve it independently.