Automated water system reporting helps operators summarize pump activity, water levels, flow, alarms, usage patterns, and overall system performance without building every report manually. NightOwl Monitoring includes automated monthly reporting to support operational review, maintenance planning, and more informed water-management decisions.
Water systems generate a continuous stream of information. Pumps start and stop, tank levels rise and fall, wells respond to withdrawal, flow changes with demand, and alarms record abnormal operating conditions. Reviewing each measurement separately may help with immediate troubleshooting, but it does not always show how the system performed across an entire month.
A monthly report organizes those separate readings into a useful operational record. It can show whether pump runtime increased, whether a tank repeatedly approached a low level, how much water moved through the system, and which alarms occurred most often.
Automation makes this process more consistent. Instead of manually exporting files, copying readings, and calculating totals, an automated system can collect selected data and present it in a standardized report. Operators still need to review and interpret the results, but less time is spent assembling the information.
Why Water Operators Need Reports
Real-time dashboards answer an immediate question:
What is happening in the system right now?
Monthly reports answer a different question:
How has the system been performing over time?
Both views are necessary. A dashboard can show that a pump is currently running, while a monthly report can reveal that its total runtime has increased for three consecutive months. A tank may appear normal during an inspection, but historical reporting may show that it repeatedly reached a low level during peak-use periods.
EPA’s Effective Utility Management framework encourages water utilities to use performance measures, report results, and follow up on improvement efforts. It also provides examples of operational measures that are commonly evaluated over monthly reporting periods. [1]
Converting Raw Data Into Operational Context
Raw sensor readings can be difficult to interpret when they are viewed one at a time.
A report can organize them into patterns such as:
- Total monthly pump runtime
- Average runtime per pumping cycle
- Number of pump starts
- Minimum and maximum water levels
- Average tank storage level
- Total water produced or consumed
- Peak flow periods
- Number and duration of alarms
- Power interruptions
- Communication outages
- Comparison with a previous month
These summaries help operators move beyond isolated readings and understand whether system behavior is stable, improving, or gradually becoming less efficient.
Preserving an Operating Record
Monthly reports create a record that can be reviewed later.
This is useful when an operator needs to determine:
- When pump runtime began increasing
- How often a tank reached a critical level
- Whether a leak caused unusual usage
- How long an alarm remained active
- Whether a repair improved performance
- How current demand compares with a previous season
- Which asset requires the most attention
Historical operating data is an important part of effective asset management. EPA guidance recommends keeping operational records for pumping facilities, including operating hours and pressure information, and using maintenance records to support preventive maintenance programs. [2]
Improving Communication
Water systems are often managed by more than one person. Operators, maintenance technicians, managers, owners, engineers, and service contractors may all need different levels of information.
A structured monthly report can give each group a common reference point.
For example:
- An operator may focus on alarms and abnormal operating periods.
- A maintenance technician may review runtime, starts, current, and vibration.
- A manager may focus on system reliability, usage, and recurring problems.
- A well professional may review pumping activity and water-level recovery.
- A property or farm owner may need a high-level summary of water availability.
Consistent reports reduce dependence on memory, informal messages, and manually assembled spreadsheets.
Supporting Performance Measurement
Effective reporting should not simply list data. It should help the organization measure performance against useful targets.
Possible targets include:
- Maximum acceptable pump starts per period
- Expected tank-level range
- Normal daily water consumption
- Target pump runtime
- Maximum allowable alarm duration
- Expected well recovery
- Flow and pressure operating ranges
- Equipment availability
- Communication uptime
EPA’s Effective Utility Management guidance identifies measurement and periodic reporting as important parts of continuous operational improvement. Some utilities report key performance indicators to management every month so developing issues can be reviewed consistently. [3]
What Monthly Reports Should Include
The contents of an automated report should reflect the system’s design, operational goals, and available sensors.
| Report Data | Value |
| Pump runtime | Maintenance planning |
| Water levels | Supply visibility |
| Flow totals | Usage tracking |
| Alarms | Problem history |
Pump Runtime and Start Count
Pump runtime shows how long the pump operated during the reporting period. Start count shows how often it turned on.
Both measurements are needed because the same total runtime can result from very different operating patterns.
For example:
- One long operating cycle may reflect sustained demand.
- Numerous short cycles may indicate a pressure-tank, control, or leakage problem.
- Increased runtime with stable water use may indicate lower pump output.
- No runtime during an expected schedule may indicate a power, control, or equipment failure.
A useful monthly pump summary may include:
- Total operating hours
- Average runtime per day
- Average runtime per start
- Total number of starts
- Longest individual cycle
- Days with unusually high runtime
- Comparison with the previous month
- Related pump alarms
Operating hours can also support maintenance scheduling. Some inspections, lubrication tasks, and component replacements are based partly on runtime rather than calendar age alone.
Well-Water Levels
Well-level reporting helps operators understand source-water availability and the well’s response to pumping.
Useful values may include:
- Highest recorded level
- Lowest recorded level
- Average water level
- Pumping water level
- Recovery after pumping
- Number of low-level alarms
- Time spent below a selected threshold
- Comparison with earlier months or seasons
Short-term changes may be caused by pumping schedules, rainfall, drought, or nearby withdrawal. Long-term records are particularly valuable for understanding groundwater availability and identifying trends that may not be visible from occasional manual measurements. USGS emphasizes that systematic water-level records are important for evaluating aquifer response, water availability, and the effects of withdrawal over time. [4]
A monthly report should not assume that every decline indicates permanent well failure. Operators should consider seasonal conditions, demand, pumping duration, recharge, and sensor accuracy.
Tank and Storage Levels
Tank-level data shows whether storage remained within the intended operating range.
A monthly summary may include:
- Average tank level
- Minimum and maximum level
- Number of low-level events
- Number of high-level events
- Duration below or above selected thresholds
- Typical daily refill pattern
- Time required to refill
- Unexpected overnight decline
- Relationship between level and pump activity
Repeated low-level events may suggest:
- Demand exceeding supply
- Reduced well production
- Insufficient pump output
- A pump or valve problem
- Poor control settings
- A leak
- Inadequate storage capacity
Repeated high-level events may suggest failed shutdown logic, level-sensor problems, an open valve, or overflow risk.
Flow Rates and Total Usage
Flow reporting should distinguish between instantaneous flow and totalized volume.
Instant flow shows how quickly water was moving at a particular time. Total flow shows how much water passed through the system during the month.
A report may summarize:
- Total monthly water production
- Total water usage
- Average daily flow
- Highest recorded flow
- Minimum operating flow
- Water use by site or zone
- Unscheduled flow
- Continuous low flow
- Comparison with earlier periods
Flow totals help operators identify changing consumption patterns. They can also be compared with pump runtime to evaluate how much water the pump delivers per operating hour.
For example, if pump runtime increases while total delivered volume remains stable, the system may be becoming less efficient. Possible causes include pump wear, reduced well yield, pipe restrictions, lower voltage, or inaccurate instrumentation.
Alarm History
An alarm summary provides more value than a simple count.
Useful alarm information includes:
- Alarm type
- Asset affected
- Date and time
- Priority
- Duration
- Number of occurrences
- Acknowledgement status
- Return-to-normal time
- Associated measurements
- Notes about corrective action
Reports should highlight recurring alarms rather than allowing them to disappear in a long event list.
Examples include:
- Repeated low tank-level alarms
- High pump-start counts
- Long runtime events
- Abnormal flow alarms
- Power interruptions
- High vibration
- Communication failures
- Low well-water levels
- Pressure outside the normal range
An alarm that occurs repeatedly may be more important than a single high-priority event that was quickly corrected.
Electrical and Equipment Data
Where electrical monitoring is available, a monthly report may also include:
- Voltage
- Amperage
- Phase imbalance
- Energy consumption
- Motor temperature
- Vibration
- Power-loss events
- Reset history
An unexplained change in energy use or electrical behavior can be an early sign of equipment failure, obstruction, mechanical wear, or changing operating conditions. EPA energy-management guidance recommends monitoring performance and periodically reviewing results so utilities can identify both energy and operational improvements. [5]
Data Availability and Sensor Status
A report should also show whether the underlying information is complete.
Useful quality indicators include:
- Percentage of expected readings received
- Communication downtime
- Sensor offline periods
- Missing data
- Calibration or maintenance periods
- Readings outside the sensor’s range
- Time synchronization problems
A report can look complete while still being misleading if a sensor was offline for several days. Operators should know when totals are based on incomplete records.
Turning Data Into Useful Monthly Indicators
Automated reporting becomes more valuable when it calculates meaningful relationships rather than presenting only individual readings.
Runtime per Unit of Water
Comparing pump runtime with total flow can help evaluate pumping performance.
A gradual increase in runtime required to deliver the same volume may indicate:
- Declining pump efficiency
- Falling well production
- Increased head pressure
- Pipe restrictions
- Valve problems
- Changes in equipment settings
The comparison should be made under reasonably similar operating conditions.
Starts per Day
Average daily starts can help identify changes in pump cycling.
A rising start count may be linked to:
- Pressure-tank problems
- Small leaks
- Unstable controls
- Reduced storage
- Changing demand
- Incorrect pressure settings
Manufacturers’ requirements should be used when determining acceptable cycling frequency.
Water-Level Recovery
For a well system, the report can compare the water level at the end of pumping with the level after a defined recovery period.
Slower recovery over time may justify further evaluation, especially when combined with longer runtime or declining flow.
Tank Inflow and Outflow Balance
Where both inflow and outflow are measured, the report can compare the two values with the change in tank storage.
A significant unexplained difference may indicate:
- A leak
- An unmetered outlet
- Meter error
- Incorrect tank-volume calculations
- Missing data
- Sensor problems
Alarm Frequency and Duration
Alarm counts alone do not show operational impact.
A better report may distinguish among:
- A single alarm lasting five hours
- Ten alarms lasting several seconds
- Repeated alarms at the same time each day
- An alarm that remained unacknowledged
- An alarm that returned after a reset
These patterns help teams prioritize corrective action.
How Reports Help Prevent Failures
A monthly report does not physically prevent a pump, valve, sensor, or well from failing. Its value lies in revealing changes early enough for operators to investigate and act.
Identifying Gradual Performance Decline
Many failures develop gradually.
A pump may still operate while:
- Runtime increases
- Flow decreases
- Electrical current changes
- Vibration rises
- Tank refill time becomes longer
- Low-level alarms become more frequent
These changes may be difficult to notice in daily operations. A monthly comparison can make the trend visible.
Detecting Short Cycling
Short cycling may not produce an immediate pump failure, but repeated starts can increase wear on motors, relays, pressure switches, and other components.
A report that combines total starts, average runtime per cycle, pressure behavior, and alarm history can help identify the pattern before damage becomes severe.
Finding Developing Water-Supply Problems
Reports can help show whether a system is becoming less capable of meeting demand.
Warning patterns may include:
- Declining well levels
- Slower recovery
- Longer pump runtime
- Reduced flow
- Increasing low-tank alarms
- Greater dependence on backup supply
One abnormal month may reflect weather or unusual use. A repeated trend deserves closer review.
Revealing Leaks and Abnormal Usage
A slow leak may not trigger a dramatic alarm.
However, monthly reporting may reveal:
- Higher total usage
- Overnight flow
- Increased pump runtime
- More frequent starts
- Lower average tank levels
- Water use outside normal schedules
Comparing several measurements makes it easier to distinguish normal demand from possible water loss.
Evaluating Maintenance Results
Reports can also show whether maintenance solved the original problem.
After a pump repair, tank adjustment, valve replacement, or leak repair, operators can compare:
- Runtime before and after the work
- Starts per day
- Flow per operating hour
- Energy use
- Alarm frequency
- Tank refill time
If the measurements do not improve, further investigation may be needed.
Prioritizing Limited Resources
Small and remote systems often have limited staff and maintenance budgets.
Monthly reports can help prioritize:
- Which pump should be inspected first
- Which site has the most alarms
- Which tank repeatedly reaches a critical level
- Which sensor has frequent communication loss
- Which well shows declining performance
- Which asset is consuming more energy
This supports condition-informed maintenance instead of treating every asset as if it has the same risk.
Limits of Automated Reporting
Automation improves consistency, but it does not eliminate the need for operator judgment.
Reports Depend on Data Quality
Incorrectly calibrated sensors, poor meter installation, missing communications, or incorrect configuration can produce misleading results.
Automated totals should be checked against:
- Manual readings
- Equipment counters
- Utility bills
- Laboratory results where relevant
- Field observations
- Maintenance records
Monthly Reports Are Not Always Regulatory Reports
Operational reports should not automatically be treated as substitutes for reports required by regulators, permits, contracts, or public-health agencies.
Regulatory submissions may require specific:
- Sampling methods
- Certified laboratory results
- Forms
- Calculations
- Signatures
- Reporting periods
- Record-retention practices
Automated operational reports can support those processes, but operators must still follow applicable requirements.
Summary Data Can Hide Short Events
A monthly average may appear normal even if the system experienced a serious five-minute event.
Reports should therefore include:
- Extremes
- Alarm events
- Duration outside limits
- Daily trends
- Significant anomalies
Averages should not be the only measurements reviewed.
Reports Still Require Follow-Up
A report is useful only when someone reviews it and assigns action.
A practical monthly review should identify:
- What changed?
- Is the change expected?
- What risks does it create?
- What additional information is needed?
- Who will investigate it?
- When will the action be completed?
- Did the corrective action improve performance?
NightOwl Monitoring Reporting Features
The monitoring platform lists automated monthly reporting alongside alarms, alarm-history logs, and real-time monitoring of wells, storage tanks, pump activity, power, flow, pressure, vibration, water quality, and environmental conditions. [6]
This allows a report to combine measurements that would otherwise need to be gathered from separate sources.
Depending on the installed equipment and configuration, monthly review may include:
- Pump start count and runtime
- Well-water levels
- Storage-tank levels
- Instant and total flow
- Voltage and amperage
- Motor vibration
- Alarm history
- Water-quality parameters
- Pump-house temperature and humidity
The main value is consolidation. Operators can review asset behavior and abnormal events in one recurring operational summary instead of manually building the same report each month.
The report should still be treated as a decision-support tool. Field inspections, sensor verification, electrical testing, well evaluation, and professional maintenance remain necessary when the data indicates a problem.
FAQs
What is automated water system reporting?
Automated water system reporting is the scheduled collection and summarization of monitoring data such as pump runtime, water levels, flow, alarms, power, and equipment conditions.
Why are monthly reports useful for water operators?
They help operators identify gradual trends, compare current performance with earlier periods, document recurring alarms, plan maintenance, and communicate system conditions to managers or service teams.
What data should a monthly water-system report include?
A useful report may include pump runtime, pump starts, well and tank levels, flow totals, pressure, power data, alarm history, communication status, and comparisons with previous periods.
Can monthly reporting identify a failing pump?
It can reveal patterns associated with developing pump problems, including longer runtime, lower flow, rising vibration, abnormal current, repeated overloads, or slower tank refill. A field inspection is needed to confirm the cause.
How can reports help detect water leaks?
Leaks may appear as higher flow totals, continuous overnight use, longer pump runtime, more frequent starts, unexplained tank-level decline, or repeated abnormal-flow alarms.
Should a report include only monthly averages?
No. It should also show minimums, maximums, totals, alarm events, duration outside limits, and significant short-term abnormalities that an average might hide.
Can automated reports replace operator inspections?
No. They help operators prioritize inspections and understand system history, but they cannot physically inspect equipment, verify every sensor, or repair a fault.
Can an automated report replace regulatory reporting?
Not automatically. Regulatory reports may require specific sampling, certified results, forms, approvals, and reporting procedures.
How should operators use an automated report?
They should review changes, identify abnormal patterns, assign follow-up actions, document maintenance, and compare later reports to determine whether the action improved system performance.
How long should reports be retained?
Retention should reflect operational, maintenance, contractual, insurance, and regulatory needs. Keeping enough history to compare seasons and equipment performance is often valuable.
Conclusion
Automated water system reporting turns continuous monitoring data into a recurring operational summary that is easier to review, share, and use.
Pump runtime supports maintenance planning. Well and tank levels provide supply visibility. Flow totals document production and consumption. Alarm records preserve the history of abnormal events. Electrical and equipment measurements add context about pump condition and system reliability.
The greatest value comes from comparing these measurements rather than reviewing them separately. Longer runtime combined with lower flow may indicate declining performance. Repeated low tank levels combined with reduced well recovery may reveal a supply limitation. Rising water use combined with overnight flow may point toward leakage.
Automated monthly reports do not replace qualified operators, inspections, sensor maintenance, or regulatory procedures. They give those activities better direction by showing what changed, when it changed, and which assets require attention.