Overflow Prevention
SmartCover & sewage level for WASD — read the existing fleet, then stop the spill.
Prevent sanitary sewer overflows.
A level reading is not the objective. Stopping the spill is. Every view here is ordered by how close a site is to surcharging, what is driving it, and which crew is already moving — because an SSO is measured in gallons to surface water and consent-decree exposure, not in feet of water.
This program year
Kept out of surface water
Consent-decree exposure
Lead time before surcharge
How we get there
Prevention needs coverage, and coverage already exists — it just isn't correlated yet.
Via free REST API
API is free, unlimited users
Velocity, FOG, gas, motor current
Already exists — faster pilot
The Argument for WASD
Three points, in the order they should be told.
SmartCover publishes an open, free REST API — HTTPS, JSON, Bearer JWT, unlimited users. IoT-LogIQ pulls their level series into the same namespace as our velocity, motor current, vibration, conductivity, gas, energy and weather. DERM's investment stops being a threat and becomes an input.
- "IoT-LogIQ can ingest SmartCover" is a checkable engineering statement, not a claim
- Makes their 346 units more valuable, not obsolete
- "Your program did the screening; here's the layer that turns it into gallons and causes"
- Pilot is cheaper and faster — site selection and 3 years of baseline already exist
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, no cost, and three years of baseline history arrives with 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.