what we protect · what we prevent.
- +Non-revenue water reduced · billing-grade LoRaWAN meters detect leaks and bypass
- +Pumps always operational · predictive maintenance 2-4 weeks ahead · no neighborhood outage
- +CFE GDMTH surcharge avoided · sub-metering + PF analysis · capacitor bank justified
- +CONAGUA and CFE audits backed · continuous report · auditable data
- +Remote operation · no house-by-house walking · staff focused on real interventions
- ✕30-50% of produced water unbilled · permanent loss for the operator
- ✕Pumps in failure · neighborhood without water for hours or days · expensive emergency repair
- ✕Permanent CFE surcharge from low PF in plants · invisible on each bill
- ✕CONAGUA fines for out-of-spec treated water discharge · no data to defend
- ✕Vandalism or theft in pump rooms and substations · no watched perimeter
eight use cases · four critical areas.
for the OOMAPAS commercial director.
Commercial Director + Billing Manager. Two cases · 30-50% of produced water unbilled, expensive house-by-house manual readings with errors. LoRaWAN-native meters address both.
for the technical director.
Technical Director + Network Operator. Two cases · pressure drop in specific sector (large-leak signal), tank empties overnight without warning. Point-to-point network coverage.
for the maintenance lead.
Maintenance Lead + Operations Director. Two cases · critical pump with silent degradation, treatment plant with process leak. Predictive maintenance and continuous coverage.
for the operator CFO.
CFO + Energy Director. Two cases · low power factor in pump plants, contracted demand exceeded in peak hours. CFE GDMTH sub-metering with data.
three compliances · one platform covers all three.
For multi-municipal operators (state-level or inter-municipal system), cross-operator dashboard with non-revenue water and operational-efficiency ranking per municipality.
from sensor to report · every five minutes · without human intervention
Five steps. They run in parallel across all your sites, all the time. When something crosses a threshold, the flow completes in under five minutes — alert delivered, response logged, inspector-ready evidence captured.
measure
Sensors measure temperature, humidity, current, door-open, leak and other magnitudes every five minutes — no operator required.
detect
The system compares each reading against the threshold configured per recipe · per site · per equipment. Threshold crossing triggers the flow.
alert
The alert routes to the right person via WhatsApp, email or push · per role and schedule configured.
respond
The operator acts from the dashboard or mobile app. The corrective action goes into an immutable log with timestamp + signature.
audit
Everything becomes part of the audit package · time series, critical events, corrective actions, NOM report ready in two clicks.
Five steps · no manual operators · no paperwork · no gaps.
five phases · per network sector.
per-sector survey
2-5 daysTechnical visit + inventory of users, tanks, wells, pumps, plants · critical pressure-point identification · per-sector deployment plan.
physical installation
1-3 weeks per sectorbilling-grade LoRaWAN meter meters at users + pressure sensors at critical points + level in tanks/wells + CT on pumps + main-panel meter at plants · sector-coverage gateways · no service interruption.
configuration + integration
1-2 weeksMeter configuration · integration with existing billing system via Custom Integration · WhatsApp alerts per role · per-sector dashboards.
team training
2 daysCommercial Director + Technical Director + Maintenance Lead + CFO + Network Operator · each role trains on their alert and report flow.
30 days of support + first billing cycle
30 daysAstreaIoT specialist available · first granular billing cycle issued · first production-vs-billing reconciliation · per-sector baseline adjustment.
For large operators (>50K users), per-sector deployment with weekly waves · first sector time-to-billing in 30-45 days.
common questions · before the quote.
are billing-grade LoRaWAN meter meters billing-grade certified?
Yes · 23 SKUs DN15-DN200 with billing-grade accuracy (Class B/R per ISO 4064) and 10-15 year battery. Compatible with Mexican regulatory frameworks for OOMAPAS and municipal water operators.
does it integrate with the existing OOMAPAS billing system?
Yes · via Custom Integration. Compatible with SAP IS-U, Oracle Utilities, specialized Mexican systems (Anubis, Sislux, ELOK), or proprietary systems. Meter data arrives directly at the billing module.
can LoRaWAN be substituted with cellular if no coverage?
Yes · gateways can use cellular backhaul (4G/5G cellular) when no Ethernet. For remote zones (mountain wells), solar gateway with cellular backhaul is standard.
what about existing SCADA if we have one?
AstreaIoT complements SCADA · does not replace it. SCADA keeps active control of valves and switching · AstreaIoT adds mass metering, uncovered-room monitoring, and billing platform. Integration via Modbus or Custom Integration.
how is residential user privacy respected?
Only aggregated per-tap consumption is measured · zero personal information in the sensor. Complies with LFPDPPP. Billing data goes directly to the operator's billing system, not to AstreaIoT cloud.
what if a neighborhood has a massive nighttime leak?
Automatic detection by meter correlation · if all sector meters show zero consumption but pressure drops, leak is upstream. Immediate alert to network operator with affected-sector location.
does the pressure sensor work on hydrants with variable flow?
Yes · industrial pipe pressure sensor designed for flow and pressure variations. Compatible with existing hydrant installation via standard adapter · no pipe cutting.