MQTT + Private LoRa for Upstream & Midstream

Midstream and upstream operators are under pressure to reduce downtime, cut truck rolls, and get cleaner, faster data from the field. The combination of private LoRaWAN for ultra-low-power sensing and MQTT for lightweight, reliable data movement gives you a modern, secure, and scalable telemetry stack—without ripping out existing SCADA.

Clover IQ integrates all layers: certified field sensors and edge devices, private LoRa gateways and network servers, an MQTT broker (with optional Sparkplug B), and adapters into your historians, SCADA/HMI, MES, and cloud analytics.

Why MQTT + LoRa makes sense for O&G

• Battery-first sensing: LoRaWAN sensors run for years on AA/ER batteries; perfect for well pads, tank batteries, and long pipeline stretches.
• Private and resilient: Keep traffic in your network (plant/field LAN, private LTE/5G, microwave backhaul). No dependency on public LPWANs.
• SCADA-friendly: MQTT is lightweight, firewall-friendly, and well-supported across Ignition, AVEVA, PI/AVEVA Data Hub, and modern data platforms.
• Event-driven: Publish only when values change or alarms hit; reduce chatter and cellular backhaul costs.
• Vendor-neutral: Open standards (MQTT 3.1.1/5.0, LoRaWAN, Sparkplug B) avoid lock-in.

Typical upstream & midstream use cases

Upstream (well sites, tank batteries, saltwater disposal):

• Wellhead pressure/temperature, choke position, flow, sand detection
• Tank level (guided wave radar, pressure-based), thief hatch and gate monitoring
• H₂S, VOC, methane leak detection
• Power monitoring for VFDs and artificial lift skids

Midstream (gathering, transmission, terminals, compressor stations):

• Line pressure, differential pressure, pig passage, valve position
• Cathodic protection (CP) rectifier telemetry
• Acoustic and pressure-based leak indication
• Station health: vibration, bearing temperature, vibration FFT snapshots

How Clover IQ delivers the stack

Field devices & gateways

• Pre-vetted LoRaWAN Class A/C sensors for pressure, temp, level, vibration, gas, discrete I/O
• Industrial LoRaWAN gateways (hazard-rated options) with dual SIM or multi-WAN backhaul
• Edge compute container (Node-RED/Telegraf/edge apps) for on-site transformation & store-and-forward

Network & cybersecurity

• Private LoRaWAN with redundant LNS (on-prem VM/K8s or customer cloud)
• Encrypted backhaul (IPSec/DMVPN/SD-WAN), device identity & cert lifecycle
• Role-based access, topic-level ACLs, QoS policies, and audit trails

MQTT broker integration

• Broker options: enterprise-grade (e.g., HiveMQ/EMQX) or open-source (Mosquitto) with clustering
• Sparkplug B enablement for auto-discovery and state management
• Bridging to on-prem and cloud brokers, with throttling and offline replay

Systems integration

• SCADA/HMI: Ignition, AVEVA Edge/System Platform, Wonderware
• Historians: PI/AVEVA, Canary, OSIsoft interfaces
• Data platforms: Azure IoT, AWS IoT Core, Kafka → Snowflake/Databricks/Delta Lake

MQTT design recommendations for OT

Topic namespace: Use a consistent, human-legible pattern: `org/<company>/site/<site-id>/area/<area-id>/asset/<asset-id>/sensor/<tag>`

QoS & session strategy:

• Telemetry: QoS 1 (at-least-once) for measurements; QoS 2 where mandatory (custody transfer)
• Alarms/Events: QoS 1 with retained=true for last-known state topics
• Commands (downlink): QoS 1/2 with application-level acks and timeouts

Security:

• TLS 1.2+ everywhere, mutual TLS for gateways and applications
• Per-device X.509, short-lived client certs, CRL/OCSP
• Broker-side ACLs by client and topic prefix; no wildcards for writes

Example: well pad retrofit (upstream)

Goal: Add production telemetry and thief-hatch monitoring without running new conduit.

1. Install LoRa pressure and temperature sensors on tubing/casing; magnet/reed switch on thief hatch. 2. Mount two LoRa gateways on the separator skid with directional antennas; backhaul via private LTE. 3. LNS decodes payloads → publishes via MQTT Sparkplug B into on-prem broker cluster. 4. Ignition subscribes for HMI screens and alarms; historian writes min/avg/max. 5. Cloud bridge forwards a subset (production & emissions) to analytics each hour. 6. Battery-life dashboard alerts on low-battery months in advance.

Outcomes: Single-truck installation, <1s alarm delivery over MQTT, no SCADA port sprawl, and clean separation between OT and analytics consumers.

Getting started

1. Discovery: asset list, points, alarm philosophy, data consumers 2. Pilot scope: 10–50 points across 2–3 sites, success criteria, and security guardrails 3. Design: RF survey, BoM, topic & payload schema, integration plan 4. Deploy: stage, commission, validate, hand-off with runbook 5. Operate: monitor, optimize reporting intervals, trend battery health, expand by area

Ready to modernize field telemetry without a rip-and-replace? Clover IQ can deliver the devices, the private LoRa network, the MQTT core, and the integrations that make the data useful on day one.