What “setting up data services” means
A sensor reading or camera event is useless if it cannot leave the site, or if it arrives without knowing which device, which hop, and which clock produced it. Setting up field data services means choosing links for range, power, and coverage — then binding them into one accountable path to the office. That path sits beside plant control; it does not replace safety systems. See field measurement requirements and LDUX and SCADA. For how we engage on requirements and scope, see the Discovery process.
Near-field & local pairing
Short-range links are how crews install, commission, and operate when there is no wide-area coverage — or when you deliberately keep traffic off the public internet.
- Bluetooth / BLE — pairing, configuration, and local readouts for meters, gateways, and handhelds; store-and-forward when the WAN is down.
- NFC — tap-to-identify assets, load credentials or job context, and reduce mis-tagged equipment without typing serials in the mud.
- Wi‑Fi — high-bandwidth local LAN for cameras, tablets, and edge PCs at the pad, yard, or facility closet; still needs auth, segmenting, and offline policy.
LPWAN & long-range radio
Low-power wide-area links carry small, infrequent payloads across sites where power and cell coverage are scarce:
- LoRa — point-to-point or private radio hops for sensors and relays when you control the spectrum plan and gateways.
- LoRaWAN — standardized device join, uplink/downlink, and network-server roles so many endpoints share a managed LPWAN without reinventing addressing.
- Requirements commonly include device EUI / join identity, duty-cycle and payload size budgets, confirmed vs. unconfirmed delivery, and a clear map of which gateway heard which uplink.
Beacons, cameras & edge sight
Not every “sensor” is a transducer. Industry setups often chain presence and vision into the same data service:
- Beacons — BLE or other presence tags that place a person, vehicle, or tool in a zone; events must carry site, zone, and time with the same identity rules as meters.
- Cameras — higher bandwidth (usually Wi‑Fi, wired Ethernet, or cellular uplink); need retention policy, who may view, and linkage from clip or metadata to the asset or alarm that triggered capture.
- Edge boxes should normalize “beacon seen” and “camera event” into the same vocabulary as pressure or level samples so the office does not maintain two unrelated systems.
Cellular & satellite backhaul
When the site must reach the cloud or a regional hub, wide-area paths carry aggregated or urgent traffic:
| Path | Typical role in field data services |
|---|---|
| Cellular (LTE / 5G / LTE-M / NB-IoT) | Primary or failover WAN for gateways, cameras, and store-and-forward queues; IoT profiles for battery endpoints. |
| Satellite | Blind spots and remote pads where terrestrial radio fails; expect higher latency, strict payload discipline, and explicit offline buffering. |
| Multi-path / failover | Prefer local mesh or LPWAN first, then cellular, then satellite — with duplicate detection so the same reading is not billed or counted twice. |
Verifiable mesh & Reticulum-class networks
Mesh and delay-tolerant networks matter when no single carrier owns the hop: pads share relays, crews carry nodes, or links form only when radios are in range. Industry-grade setups treat verifiability as a requirement, not an afterthought:
- Mesh / ad-hoc relays — multi-hop delivery with known node identities, hop limits, and store-and-forward so intermittent contact still converges.
- Reticulum and similar stacks — cryptographic destination addressing, encrypted transport, and announce/path discovery suited to contested or infrastructure-light environments; plan for key custody, destination naming, and interface bridging (radio, serial, IP tunnels).
- Verifiable delivery — signed or hashed payloads, sender and destination identity, and an audit of which path accepted the message — so a reading remains attributable after it crossed several untrusted or intermittent hops.
Common setup requirements (any link)
Regardless of radio or carrier, accountable data services share a setup checklist:
| Concern | What must be defined |
|---|---|
| Identity | Stable device, gateway, and site IDs that survive radio swap or SIM change. |
| Time | Clock sync policy; how offline samples record lag when they finally sync. |
| Ordering & duplicates | Store-and-forward queues, idempotent event IDs, and last-heard health. |
| Security | Join keys / credentials, rotation, least-privilege APIs, and segmented local Wi‑Fi. |
| Interchange | MQTT, Modbus, HTTPS APIs, or mesh destinations normalized into one office vocabulary. |
| Proof | Optional signed releases of configs and summaries; proofs may start in local private storage and later harden to device-bound stubs. |
Industry need: pick the hop that fits power and coverage — Bluetooth, NFC, Wi‑Fi, LoRa / LoRaWAN, cellular, satellite, or mesh — but keep one identity model so every packet still answers who · what · where · when · how measured after the path changes.
How we help
We help you map sites to the right mix of near-field, LPWAN, backhaul, and verifiable mesh; define gateway and event contracts; and bridge clean traffic into operator-facing views — measurement- and SCADA-adjacent, never claiming plant actuation. Engagements typically start with the Discovery process.