MQTT in action: Connecting distributed industrial operations


Industrial operations rarely exist in one place. Assets can be spread across hundreds of miles, located at remote sites with limited connectivity, or even moving across the ocean.

That creates a fundamental data challenge: how do you reliably move operational data where it needs to go without overwhelming the network or creating increasingly complex point-to-point connections?

MQTT’s lightweight publish/subscribe architecture and report-by-exception approach make it particularly well suited for distributed industrial environments. Instead of every application connecting directly to every data source, MQTT allows data producers and consumers to communicate through a central MQTT server, or broker.

Here are four examples of how industrial organizations are using MQTT and Sparkplug to connect distributed operations.

Connecting more than 200 remote solar farms

For a solar technology company operating more than 200 geographically distributed solar farms, efficiently moving large volumes of operational data was a significant challenge.

The company was managing more than two million tags across its operations, with some individual sites generating more than 10,000 tag changes per second. Its existing infrastructure struggled to keep up with the volume of data being transmitted.

Using Ignition and Cirrus Link MQTT Modules, the company transitioned to a publish/subscribe architecture using MQTT and Sparkplug. Rather than continuously polling remote sites, data could be published when values changed.

The new architecture improved network throughput by more than 80% while giving the organization a scalable way to connect its growing portfolio of solar sites.

Read the Solar Tech Company case study

Building a smart field across 114 facilities

NGL Energy Partners faced a different version of the distributed-data challenge.

Its saltwater disposal operations included facilities spread across large geographic areas, where connectivity and bandwidth could be limited. NGL needed a SCADA architecture capable of connecting these remote assets while giving operators centralized access to operational information.

The resulting smart field connected:

  • 114 water treatment and disposal facilities, 
  • 178 pipeline tie-ins 
  • and 31 boosters, 
  • representing approximately 1.25 million tags.

MQTT became a critical part of the architecture, allowing data from remote sites to be published efficiently to centralized systems rather than relying on traditional polling-based communications.

Read the NGL Energy Partners case study

Scaling visibility across rapidly growing midstream operations

Rapid growth presented another challenge for WaterBridge Resources, a midstream water management company serving oil and gas operations.

As the company expanded, its existing SCADA and control infrastructure became increasingly difficult to scale. WaterBridge needed greater visibility across its operations and an architecture that could grow along with the business.

Working with Vertech, WaterBridge modernized its infrastructure using Ignition and MQTT. Cirrus Link MQTT technology, including redundant Chariot MQTT servers, provided the foundation for moving data between distributed operations and centralized systems.

The result was a more flexible architecture designed to accommodate continued growth while giving operators greater visibility into operations.

Read the WaterBridge Resources case study

Connecting vessels over limited satellite bandwidth

Distributed operations don’t always stay in one place.

A multinational energy company needed to modernize control and monitoring systems across its fleet of vessels. Each vessel contained multiple siloed systems responsible for functions including navigation, cargo management, vibration monitoring and engine monitoring.

Making that data available beyond the vessel presented another challenge: communications depended on VSAT satellite connections, where bandwidth was limited and expensive.

Using Ignition with Cirrus Link MQTT and Sparkplug Modules, the company created an architecture that consolidated OT data onboard and published relevant changes upstream. Instead of continuously transmitting unchanged values, MQTT’s report-by-exception approach reduced unnecessary communications.

The architecture made vessel data available for cloud analytics and use cases including predictive maintenance, operational improvements and fuel savings without requiring every system to communicate independently over the satellite connection.

Read the Vessel Control Systems case study

A more scalable approach to distributed industrial data

A solar farm, saltwater disposal facility and vessel at sea may have very different operating requirements, but their data architectures face many of the same challenges.

Remote connectivity can be limited. Bandwidth can be expensive. Operations can expand across dozens or hundreds of locations. And as more systems need access to OT data, maintaining individual point-to-point connections becomes increasingly difficult.

MQTT changes that architecture by decoupling data producers from data consumers. Combined with Sparkplug, it provides a standardized way to represent industrial data, report changes and maintain state across distributed systems.

The result is an infrastructure designed not just to connect one remote site, but to scale as industrial operations grow.

Want to see more examples of MQTT in the real world? Explore our collection of industrial case studies.

Explore Cirrus Link case studies