Industries / Groundwater Conservation Districts
Districts run on water-level records. NightOwl adds continuous, telemetered data from the wells that are hardest to reach — so the trend is visible between field runs, not six months after it started.
Groundwater conservation district monitoring is the scheduled or continuous measurement of groundwater conditions across a district's monitoring well network — primarily depth to water, plus production, water quality, and site conditions where the program calls for it. The record supports permitting decisions, drought triggers, aquifer trend analysis, and the district's obligation to manage toward its adopted desired future conditions.
Districts have historically built that record with manual measurements — steel tape or electric line, usually during the cool months when pumping is minimal and levels sit closest to static. Telemetry does not replace that record. It fills the gaps between visits: a pressure transducer and datalogger in the well, a cellular or satellite link at the surface, and a dashboard where a manager can read the hydrograph without driving the county.
Industry context
Almost everything a district does defensibly traces back to measured water levels.
Texas districts operate under Chapter 36 of the Texas Water Code. Each district adopts a management plan, submits it to the Texas Water Development Board for approval, and re-adopts it at least once every five years. Districts within a groundwater management area jointly adopt desired future conditions for their shared aquifers, and the TWDB then issues the modeled available groundwater figures used to guide permitting. Demonstrating whether an aquifer is tracking toward those conditions is a measurement problem before it is ever a policy problem.
Reviewing a new or amended production permit is far easier to defend when the district can show the local hydrograph rather than a regional average — particularly when the applicant, the neighbours, or an attorney is in the room.
Many districts tie drought stages to specific indicators. The Barton Springs–Edwards Aquifer Conservation District sets its stages from springflow at Barton Springs and groundwater levels at the Lovelady monitor well: either indicator can move the district deeper into drought, and both must recover before it exits.
When a landowner reports a well going dry, the nearby monitor record is the difference between an explanation and a shrug — and between an interference investigation that goes somewhere and one that stalls.
Water levels get presented at board meetings, published in annual reports, and submitted to the TWDB, where they join a statewide network alongside USGS and municipal data.
The TWDB describes an "ideal" water-level monitoring network as roughly one well per 25 to one well per 125 square miles for each major and minor aquifer, depending on pumpage. Statewide, the TWDB measures close to 2,000 wells a year, and cooperators — around fifty groundwater conservation districts, plus USGS and municipalities — contribute at least 8,000 additional measurements annually.
Most districts are working toward that density with staff who also process permits, run the office, and answer the phone. That gap between the target network and the available field hours is the practical case for telemetry.
Source: Texas Water Development Board, Water Level Program.Measurement
The configuration follows the monitoring objective. A dedicated observation well and an active irrigation well are not the same instrument problem.
Referenced to a fixed measuring point and reported as depth below that point or as water-level elevation. Continuous logging exposes recovery behaviour and seasonal amplitude that a single annual reading cannot.
Required wherever a non-vented (absolute) transducer is used, so the atmospheric component can be removed. It is data, not overhead — barometric response also tells you something about confinement.
Runtime, start counts, instantaneous and totalized flow. Useful where permit holders report production, and essential for telling whether a level change is aquifer behaviour or a pump that ran all night.
Line pressure at equipped sites, and wellhead pressure where a well is artesian and the potentiometric surface sits above land surface.
Where the program justifies it. Conductivity and temperature are the common continuous parameters; most other analyses remain lab work on a sampling cycle.
Battery voltage, signal strength, last-report time. Without it, a dead site looks exactly like a flat hydrograph — which is the most expensive failure mode in remote monitoring.
Comparison
Manual measurement is the backbone of the long-term record, and it is not going away.
It is traceable, it is what the historical dataset is built from, and it remains the reference a logger gets checked against. What it cannot do is tell you what happened on the days nobody was standing at the well.
| Manual measurement (steel tape / e-line) | Continuous monitoring with telemetry | |
|---|---|---|
| Typical frequency | Annual to quarterly; some sites monthly | Logging at a fixed interval; uploads scheduled or on exception |
| Best at | Long-term trend, cross-checking loggers, sites with no power or coverage | Short-term response, recovery behaviour, drought triggers, early detection |
| Field effort | Every measurement is a site visit | Visits become maintenance and verification, not data collection |
| Failure mode | A missed season is a gap in the record | A dead sensor or dead link is a gap — unless site health is monitored |
| Cost profile | Staff time and vehicle miles, ongoing | Equipment and connectivity up front and recurring; less travel |
| What it proves | Where the aquifer was | Where the aquifer is going, and how fast |
Scroll the table horizontally to compare.
Most working district programs run both: a broad manual network measured on the cool-season schedule, and continuous instruments at the sites where timing matters — index wells, drought triggers, wells near a large permitted user, and wells in an area under review.
Workflow
Sensor to datalogger to network to dashboard to decision. Every link in that chain has a failure mode worth understanding before you buy.
A submersible pressure transducer hangs below the lowest expected water level on a support cable and reads the water column above it. Vented sensors compensate for atmospheric pressure through a vent tube in the cable; non-vented (absolute) sensors need a barometric reference to correct against. Both are used in district programs — the choice depends on depth, cable length, well construction, and how the data will be post-processed.
A datalogger records at a fixed interval and holds readings locally. Local storage is what protects the record when the network is down, which in rural monitoring locations is not a rare event.
The site uploads over whatever it can reach: LTE-M or NB-IoT for low-power remote sites, standard LTE where coverage and power are good, satellite where nothing terrestrial reaches. The TWDB's own recorder network relays over the GOES satellite system, while a number of district-run programs use cellular. Uploads are usually scheduled, with exception reports when a threshold is crossed.
Readings land in one dashboard: current level, hydrograph history, site status, and the rest of the network on the same screen — accessible to staff, consultants, and board members at the permission level you set.
Alarms fire on thresholds: a level below a drought trigger, a pump that will not stop, a site that has stopped reporting. Data exports as CSV or moves through an API into the district's own reporting, GIS, or SCADA.
Practical limits
Remote monitoring is a field-installation discipline, not a purchase. Districts that get clean multi-year records have usually decided these things deliberately.
Solar and battery are standard at observation wells with no service. Panel sizing, winter sun angle, and reporting frequency are one decision, not three — every extra upload per day is a line in that budget. Battery-only sites trade frequency for years of unattended life.
Rural monitoring wells sit exactly where cellular coverage is thinnest. Verify signal at the actual site before committing to a technology, plan the antenna, and confirm the device logs through outages and backfills when the link returns.
Sensor range should match the deepest water level the site will ever see. Oversized ranges cost accuracy; undersized ranges lose the record during a drought — precisely when the record matters most.
Field verification against a manual measurement on a defined schedule is what keeps a continuous record defensible, and what lets you correct a drifting sensor rather than discover it three years later in a trend analysis.
Casing diameter, obstructions, whether the pump is in the way, landowner access agreements, and physical security of the enclosure. Most stalled deployments stall here — not at the electronics.
Flagging bad readings, handling gaps, keeping the archive. Continuous monitoring produces far more data. That is the point, and it is also the work.
Any vendor who tells you none of this matters is selling you a gap in your record.
The NightOwl approach
NightOwl builds remote monitoring and control hardware for water wells, tanks, and pumping systems, with a cloud dashboard, configurable alarms, automated reporting, and multi-site access.
Districts typically have two distinct site types, and they need different hardware: unpowered observation and index wells out in the district, and equipped, powered sites where there is a pump worth watching. Groundwater conservation districts are a named application for the NightOwl Ultra platform.
Observation & index wells
A cellular IoT data logger and sensor hub built for sites with no power and no infrastructure — the profile of most district monitoring wells.
Powered wells & pump sites
For district-owned wells, permitted production sites, and pump houses with 120 VAC service — where monitoring and control both matter.
Simple monitoring-only sites
Up to three Modbus sensors on 12 V DC, one-minute collection with 15-minute uploads, monitoring only with no relay outputs. A sensible fit where a site already has low-voltage power and a short sensor list.
Flex specificationsDistrict storage tanks
A standalone battery-powered radar tank level monitor for liquid storage tanks — non-invasive mounting, long deployment life, hazardous-area certified. Worth being explicit: this is a tank instrument, not a groundwater level instrument. It belongs on district or system storage, not at an observation well.
TLM specificationsFor water-level sensing specifically, see the water level in the well sensor, along with flow, pressure and power monitoring.
| Hawk | Ultra | Flex | TLM | |
|---|---|---|---|---|
| Built for | Remote observation and index wells | Powered district wells and pump sites | Simple powered monitoring sites | Storage tanks |
| Power | Battery, lithium, or 6–28 V DC; solar compatible | 120 VAC | 12 V DC | Internal battery |
| Connectivity | LTE-M / NB-IoT, NTN-ready | 4G LTE (VZ / AT&T / T-Mobile) | Cellular | Cat-M1 / NB1 |
| Sensor interfaces | Card-dependent: 4–20 mA, 0–30 V, digital/pulse, RS-485, RS-232, SDI-12, I²C | 2 analog, 4 digital/pulse, 8-port Modbus RTU | Up to 3 Modbus sensors | Integrated radar |
| Remote control | — | 2 relay outputs | — | — |
| Environment | IP68, −30 °C to +60 °C | NEMA 4X, UL listed, −40 °F to 185 °F | Weatherproof enclosure | IP68 |
| Offline behaviour | Store-and-forward, onboard task logic | Scheduled and exception-based reporting | Scheduled uploads | Scheduled reporting |
Scroll the table horizontally to compare all four systems.
Districts commonly run more than one: Hawk across the remote monitoring network, Ultra wherever there is power, a pump, and something worth controlling.
Data & reporting
Monitoring data is only useful once it reaches the people making decisions, in a form they can put in front of a board.
All monitored sites on a single view, with multi-user access and role-based permissions so staff, consultants and board members each see the appropriate level of detail.
Cloud-stored history for trend review, seasonal comparison and drought-stage discussion, without rebuilding a spreadsheet every time the question comes up.
Alerts by SMS, email and dashboard: a level crossing a trigger, a rate of change that does not look natural, or a site that has gone quiet.
Scheduled reports for board packets and recurring internal review, generated on the platform rather than assembled by hand the week before the meeting.
CSV export and REST API, with MQTT for SCADA where a district or its wholesale provider already runs one. Exports support district annual reporting and state data submission workflows.
TLS-encrypted transport, hardware-based device authentication, role-based access controls, and over-the-air firmware updates across the deployed fleet.
Applications
Not every well needs telemetry. These are the sites where districts tend to instrument first.
Sites tied to rule-based stages need current numbers on a defined cadence — and a stage change should be defensible on the day the board declares it, not after the next field run.
The sites that cost half a day per measurement are the ones telemetry pays for first. Locked gates, river crossings, and pasture roads after rain all count.
Continuous data around a significant producer shows drawdown and recovery behaviour, rather than an annual snapshot that may have been taken mid-pumping.
Denser records at representative wells strengthen the evidence a district brings to joint planning and management plan reporting.
A continuous record from before and during the complaint period is far more useful than a measurement taken after someone calls the office.
Where a district or an associated system operates wells, tanks and pumps, the same platform covers runtime, flow, pressure, power, and remote control.
Evaluation
A short list worth taking into any vendor conversation, including this one.
There is no single number, and any vendor offering one before seeing your sites is guessing. Cost is driven by how many wells you instrument, which sensors each site needs, how often you want data, what power and connectivity exist at each wellhead, installation effort, and whether you need control outputs or monitoring only. Recurring costs — cellular connectivity, platform access, support — usually matter more to a district budget than the hardware line.
The workable approach is phased: instrument the wells where better timing would change a decision, run them through a full seasonal cycle, then expand with real numbers in hand.
NightOwl works through a network of well drillers, pump companies and water service professionals who install and support the equipment in the field. Districts that already work with a local driller or a hydrogeologic consultant can bring them in — installation quality is what determines record quality, and the people who know your wells are usually the right people at the wellhead. Service companies interested in offering monitoring can partner with NightOwl.
Common questions
It is the scheduled or continuous measurement of groundwater conditions across a district's well network — chiefly depth to water, plus production and site data where relevant. The record supports permitting, drought rules, aquifer trend analysis, and reporting against adopted desired future conditions.
Because water-level data is the evidence behind district decisions. Levels indicate whether an aquifer is tracking toward the desired future conditions adopted through joint planning, they drive rule-based drought stages, they inform permit review, and they feed board reporting and state datasets.
It depends on the site's role. Long-term trend wells are commonly measured annually during the cooler months, when pumping is minimal and levels sit closest to static — that convention is behind most historical records. Sites tied to drought triggers or active investigations warrant far more frequent data, which is where continuous logging and telemetry fit.
Yes. A pressure transducer and datalogger in the well record levels at a set interval, and a cellular or satellite link delivers them to a dashboard. State and district programs have run telemetered recorder wells for years — the TWDB relays its recorder network over the GOES satellite system, and a number of district programs use cellular networks.
No, and it should not be sold that way. Manual measurement remains the reference a logger is verified against and the continuity of the long-term record. Telemetry adds resolution between visits and removes trips made purely to read a number.
Reliability is a function of installation, sensor selection, power, coverage and maintenance — not brand claims. Sites that log locally through outages, report their own health, and get verified against a manual measurement on a schedule produce records a district can defend. Sites that do none of those things eventually produce gaps.
On properly specified equipment, logging continues to local storage and the backlog uploads when the link returns. NightOwl Hawk uses store-and-forward flash storage for exactly this, and can run scheduled tasks and threshold logic onboard without cellular coverage.
Yes. NightOwl sites report to a shared cloud dashboard with multi-site views, multi-user access, and role-based permissions, so field staff, management, consultants and board members can each be given an appropriate level of access.
Existing wells are commonly used, including cooperating landowners' wells — that is how most state and district networks were built in the first place. What matters is suitability: known construction, accessible casing, a documented measuring point, and an access agreement. Pumping wells can be instrumented, but the readings have to be interpreted with pump status in mind.
It can support them. Districts set drought stages by rule, using indicators defined in their own drought contingency plans — commonly water levels at designated index wells, springflow, streamflow, or drought indices. Continuous monitoring at those indicator sites gives the board current numbers when a stage decision is on the agenda.
Yes, at equipped sites. NightOwl Ultra monitors pump runtime and start counts, instantaneous and totalized flow, line pressure, power and motor conditions, with drawdown analysis and fault detection, plus relay outputs for remote control.
Yes, and it is the sensible way to do it. Start with the sites where better timing would actually change a decision, run them through a season, then expand on the same platform.
Yes. CSV export and a REST API are available, with MQTT for SCADA integration where one is already in place.
Getting started
You do not need to instrument the whole network to find out whether continuous data changes how the district operates. Pick the two or three wells where a measurement six months late is a measurement that arrived too late — the drought trigger, the well behind a locked gate, the one nearest the largest permit — and start there.
