Water districts, irrigation systems and process plants share a problem: the things you need to watch are spread across dozens of sites, many of them unmanned, and the people responsible can't be at all of them. Pump stations, wells, lift stations, tanks, remote skids — they need to be visible from a control room, a truck and a phone, at the same time. Ignition Perspective is built for exactly this. Here's how we put it together.
Why Perspective for remote
Perspective is a true web client — it renders in a browser and as a native mobile app, with responsive layouts that adapt from a control-room monitor down to a phone. An on-call operator opens the same screens at 2 a.m. on their phone that the room sees on the wall, no Citrix, no VPN gymnastics, no separate "mobile version" to maintain. For distributed infrastructure that's the whole game.
Architecture for distributed sites
The pattern we use most: a central Ignition gateway as the system of record and the place humans log in, with data arriving from the field one of two ways. For sites with reliable IP, the central gateway polls the site PLCs/RTUs directly over OPC UA. For truly remote or bandwidth-constrained sites, an Edge gateway at the site buffers data locally (store-and-forward, so nothing is lost when the link drops) and publishes upstream. Either way, the operator-facing application lives in one place.
MQTT / Sparkplug for the field
Over cellular and radio, polling is expensive and brittle. MQTT with the Sparkplug B specification flips it to report-by-exception: the edge device publishes only when a value changes, with automatic birth/death certificates so the central system always knows whether a site is alive. For a fleet of pump stations on cellular modems, this slashes data usage and makes "is that site online?" an unambiguous, instant answer instead of a guess.
Connectivity and the real world
Remote sites are messy: cellular dead zones, licensed radio paths, solar-and-battery power that browns out, RTUs that reboot. The design has to assume the link will drop. Store-and-forward at the edge, sensible poll/publish rates, watchdog tags on every site's comms, and a clear "last good data at HH:MM" indicator on screen keep operators honest about what they're actually seeing versus what's stale.
Security
Putting infrastructure on the web raises the stakes, and Perspective is built for it: TLS everywhere, identity providers / SSO for login, and role-based security so a field tech, an operator and a manager see and control different things. For utilities, that role model also maps onto who's allowed to issue a remote start/stop versus who can only watch.
Alarming and callout
Remote monitoring without good alarming is just a screen nobody's looking at. Prioritized alarms, mobile push notifications to the on-call phone, and an escalation path (operator → supervisor → on-call) turn the system into something that reaches out when a tank is low or a pump faults at night — instead of waiting to be discovered. This is the same alarm-and-callout pattern we build into plant SCADA, just pointed at distributed assets.
Building the screens
Three views cover most needs: a system overview (often a map) showing every site's status at a glance; a site detail view with the local process, setpoints and controls; and trends for levels, flows and pressures over time. Dense site tables — every station with signal strength, battery, last poll and comms state — are exactly where a capable data grid earns its keep over the stock table; that's why we built Perspective DataGrid Pro.
Built for the Central Valley
This is home turf for us. California's Central Valley runs on distributed water and ag infrastructure — irrigation districts, groundwater wells, conveyance canals, pump stations — and we build remote-monitoring systems for exactly that, on-site from Merced and across the Valley, plus remote support nationwide. To scope a remote-monitoring project, get in touch or see our Ignition development services.