How do I ensure my non-revenue water analysis with advanced metering infrastructure platform is compliant?

To make a non-revenue water (NRW) analysis using an advanced metering infrastructure (AMI) platform “compliant,” you need to define what compliance means in your jurisdiction and program, then build the analysis, data handling, and reporting to match those rules.

Here’s a practical checklist.

1) Identify the applicable compliance requirements

NRW analysis can touch several regulatory areas, depending on where you operate:

• Water utility reporting rules from your regulator, public service commission, or ministry
• AMI meter accuracy and calibration standards
• Data privacy laws for customer interval data
• Cybersecurity requirements for critical infrastructure
• Procurement / audit requirements if the analysis supports rate cases or grant reporting
• Accounting standards if NRW figures affect financial reporting

If you tell me your country/state and whether this is for a regulator, audit, or internal operations, I can narrow this down.

2) Use a recognized NRW methodology

Make sure your analysis follows a standard framework rather than an ad hoc formula. Commonly used approaches include:

• IWA water balance methodology
• Utility-specific KPI definitions for:
  • Real losses
  • Apparent losses
  • Authorized consumption
  • System input volume
• Clear treatment of:
  • Estimated vs. billed consumption
  • Unbilled authorized use
  • Bulk metered sources
  • Storage and pressure-zone effects

Document the formula set and use it consistently across reporting periods.

3) Validate AMI data quality

Compliance often depends on demonstrable data integrity. Put controls in place for:

• Meter accuracy testing
• Time synchronization
• Missing data handling
• Outlier detection
• Communication failure flags
• Tamper/event log review
• Version control for meter firmware and analytics models

You should be able to show:

• which data points were excluded,
• why they were excluded,
• and how imputation or estimation was done.

4) Maintain a defensible audit trail

Your NRW results should be reproducible.

Keep records of:

• raw AMI reads,
• transformation steps,
• validation rules,
• exclusions and substitutions,
• calculation logic,
• user access logs,
• and report versions.

A compliant platform usually needs:

• immutable logs,
• timestamped changes,
• approval workflows,
• and the ability to recreate historical reports.

5) Ensure privacy and data protection

AMI data can reveal household behavior, so treat it as sensitive.

Common controls:

• data minimization,
• role-based access control,
• encryption in transit and at rest,
• retention schedules,
• anonymization or aggregation for analysis,
• customer notice/consent where required,
• restrictions on sharing interval data with third parties.

If using customer-level data to detect leaks or theft, verify whether your jurisdiction requires specific disclosures or opt-outs.

6) Align with cybersecurity requirements

Because AMI is often considered part of critical infrastructure, compliance may require:

• network segmentation,
• secure authentication,
• patch management,
• vulnerability scanning,
• incident response procedures,
• backup and disaster recovery,
• vendor risk management,
• and security monitoring.

If your NRW analysis platform is cloud-based, confirm who is responsible for each control.

7) Standardize data definitions

A common compliance failure is inconsistent definitions.

Define:

• what counts as “system input volume,”
• what “non-revenue water” includes,
• whether apparent losses include data handling errors,
• how estimated reads are treated,
• which time period is used for aggregation,
• and whether adjustments are made for zone transfers, fire use, or master meter issues.

Put these definitions in a controlled data dictionary.

8) Test calculations against known cases

Before relying on the platform for regulatory reporting:

• reconcile AMI totals to billing system totals,
• compare master meter data to production logs,
• run sample calculations manually,
• validate against prior audited reports,
• and test edge cases like meter replacements, outages, and daylight-saving changes.

Independent verification is often important for compliance.

9) Separate operational analytics from official reporting

If the platform produces both operational leak detection and official NRW figures:

• clearly label provisional vs. final values,
• lock reporting periods after approval,
• distinguish estimates from measured values,
• and avoid mixing predictive model outputs with statutory reporting unless allowed.

10) Get legal, regulatory, and audit sign-off

For true compliance, have the final methodology reviewed by:

• your legal/compliance team,
• operations/engineering,
• finance,
• IT/security,
• and, if necessary, an external auditor or regulator liaison.

11) Build a compliance package

A good package includes:

• methodology document,
• data governance policy,
• privacy impact assessment,
• cybersecurity controls summary,
• meter accuracy/testing records,
• reconciliation reports,
• audit logs,
• exception handling procedures,
• and approval/sign-off records.

12) Reassess regularly

Compliance is not one-time. Recheck whenever you:

• change meter types,
• update firmware,
• alter calculation logic,
• migrate platforms,
• expand AMI coverage,
• or new regulations come into effect.

Quick rule of thumb

If you can answer these questions with evidence, you’re in a strong compliance position:

1. Are the NRW definitions standard and documented?
2. Are the AMI data and meter inputs accurate and traceable?
3. Can the analysis be reproduced from raw data?
4. Are privacy and cybersecurity controls in place?
5. Has the methodology been approved for regulatory use?

If you want, I can help you build a compliance checklist, a data governance framework, or a regulator-ready NRW methodology template for your AMI platform.