Levels & Overflow Risk
Existing level sites and IoT-LogIQ signals, read together. Complements the basin I&I attribution pilot.
Levels and overflow risk, read alongside the I&I pilot.
The pilot's headline is basin I&I attribution, complementary to the SmartCover program WASD already runs. This view reads existing level sites next to IoT-LogIQ velocity, pump current, FOG and gas, ordered by headroom to surcharge and the correlated cause — so a rising level arrives with a reason and a crew.
Example scenario, not a result
Example scenario, not a result
Example scenario, not a result
Lead time before surcharge
How we get there
Prevention needs coverage, and coverage already exists — it just isn't correlated yet.
Fleet size unverified · not yet ingested
Vendor API, per published terms
Velocity, FOG, gas, motor current
If historical export is available
Why read the existing fleet
Integration position, architecture and the value of correlated signals.
SmartCover publishes a documented REST API — HTTPS, JSON, Bearer JWT. IoT-LogIQ pulls those level series into the same namespace as velocity, motor current, vibration, conductivity, gas, energy and weather. The existing level program becomes an input to the layer.
- API is publicly documented by the vendor (see Data & Integrations)
- Existing level sites gain correlated causes, not a replacement
- Screening readings are translated into gallons, causes and work orders
- Existing site selection and historical baseline shorten the pilot
SmartCover is their hardware, their satellite, their portal. You cannot put a vibration sensor in it, or a conductivity probe, or a motor CT clamp, or a FOG fluorescence probe. LoRaWAN is an open standard — any conforming sensor from any vendor joins the same network.
- Closed vertical stack versus open horizontal layer
- Protocol-agnostic ingestion: 500+ integrations plus Modbus, MQTT and REST
- Any conforming sensor from any vendor joins the same network
- The question stops being "which sensor vendor"
Our H₂S isn't a better measurement. It's H₂S sitting in the same namespace as pump current, wet-well drawdown, FOG discharge events, sludge blanket and weather. In their portal, H₂S is H₂S. In ours, a spike correlates to a specific cause.
- Correlate a spike to a FOG slug, a station running septic, or a drawdown pattern
- Same sensor, different epistemic value
- Not basin-scoped — same platform runs plant gas arrays and worker safety
- Also covers energy and rotating equipment
Pull level timeseries from the documented endpoint into IoT-LogIQ. No hardware to install; historical baseline can be retrieved where the account allows it.
Correlate their level data against velocity, pump current, wet-well drawdown, FOG discharge and weather — converting screening alerts into gallons, causes and work orders for the WASD team.