Water & Wastewater
Water and wastewater utilities run lift stations and remote monitoring points that field staff may visit once a week, if that-so the telemetry stream is the only operational presence at the site, and the record it produces is what operators and auditors trust after the fact. On lean municipal budgets, KŌJŌ Stack captures overflow and spill alarm events at the moment they happen, keeps that record gap-free and defensible for discharge and permit reporting, and buffers durably so an unmanned site never goes silent without anyone knowing. When no one is there to see it, the data has to be the eyes.
Architecture Highlights
The Record Is the Only Witness
The Problem
Unmanned Sites Have No Other Eyes
Lift stations and remote monitoring points are visited by field staff on a schedule measured in days or weeks, not hours. Between visits, the telemetry stream is the only indication of what the asset is doing-if a sensor stops reporting, no one notices until the next scheduled visit, or until something has already gone wrong.
A Data Gap Is a Reporting Problem, Not Just a Monitoring Gap
Discharge and permit reporting depends on a complete, defensible record of what happened and when. A missing reading is not just a blind spot for operators-it is a hole in the record a utility must be able to stand behind when asked to account for what occurred at a site.
Overflow and Spill Alarms Must Be Captured, Not Missed
Overflow and spill events are exactly the moments when a marginal cellular or radio link is most likely to be under stress-and exactly the moments a lean-staffed utility cannot afford to lose the alarm. An event that never reaches the control center might as well not have happened.
What Fails in Traditional Architectures
Without structured, prepared data at the first mile, downstream systems inherit every inconsistency, gap, and limitation of the raw source data.
A Silent Site Looks Identical to a Quiet One
Without durable local buffering, a dropped link between an unmanned lift station and the control center produces the same signature as a period with nothing happening: no data. Field staff have no way to tell a communications gap from an uneventful day until the next scheduled visit.
The Record Can't Be Defended
When readings are missing or arrive out of order, a utility responding to a discharge or permit inquiry cannot produce a complete account of what happened at a site. What should be a straightforward record pull becomes a reconstruction effort with gaps that can't be explained.
A Missed Overflow Alarm Is Indistinguishable from One That Didn't Happen
If an overflow or spill event occurs during a connectivity outage and there is no local buffering, the event never reaches the control center at all. Operators cannot respond to, or later document, an incident they were never told about.
How KŌJŌ Stack Helps
Continuous Capture at Sites No One Is Watching
Each lift station and remote monitoring point is polled directly over DNP3 or Modbus and reports continuously, so the record exists independent of when field staff are physically on-site-the telemetry stream stands in for a human presence between visits.
Gap-Free, Defensible Records for Discharge and Permit Reporting
Durable local buffering persists every reading before acknowledgment. If a link drops, data accumulates on-site and replays in order with original timestamps once connectivity returns, so the record a utility produces for discharge and permit reporting has no unexplained gaps.
Overflow and Spill Events Captured at the Moment They Occur
Alarm and state-change events are captured and buffered locally at the point of origin, so an overflow or spill condition is recorded even if the link to the control center is down at that exact moment-and delivered in the order it happened as soon as connectivity is restored.
One Structure Across a Dispersed, Lean-Staffed Fleet
Every site-regardless of type or location-publishes to the same ISA-95 compliant namespace, so a small operations team can monitor and report across dozens of unmanned assets from one consistent structure instead of reconciling formats site by site.
Why This Requires First-Mile Data Structuring
Water and wastewater utilities run largely unmanned infrastructure: lift stations and remote monitoring points that field staff may visit on a weekly or biweekly rotation, connected by cellular, licensed radio, or occasionally satellite links that were never sized for continuous high-volume telemetry. Between visits, the DNP3 or Modbus data stream from each RTU is the only account of what happened at the site-there is no operator present to notice a problem in real time. That makes two properties non-negotiable: the record cannot have unexplained gaps, because discharge and permit reporting depends on it being complete and defensible, and alarm-class events-an overflow, a spill, a pump failure-cannot be lost to the exact connectivity interruption they are most likely to coincide with. KŌJŌ Stack addresses both by running acquisition and durable buffering at the site itself: readings and events are captured and normalized at the point of origin, persisted locally before acknowledgment, and replayed in order once a dropped link reconnects-so a lean operations team covering many unmanned sites can trust the record between visits, not just during them.
Expected Outcomes
Durable buffering and ordered replay close the gaps a dropped link would otherwise leave in the record
Alarm events are recorded at the edge and delivered in order, even through a connectivity interruption
One namespace across every unmanned site, sized for a lean operations team
Own the First Mile
Owning the first mile ensures water & wastewater data is consistent, contextualized, and usable across the enterprise.