# Research Note — 2026-06-02 (NIPSCO gas meter info / AMI correction)

> **Status: Confirmed-context update — not a protocol change by itself**

## Confirmed facts
- NIPSCO says that during its AMI rollout it found an issue with a very limited number of existing gas meters, affecting less than 1% of natural gas customers. The company says the issue was not caused by AMI itself. [^1]
- NIPSCO says affected customers are being notified directly by mail and email, that overbilled customers will receive credits, and that the company expects all impacted meters to be corrected by the end of 2026. [^1]
- NIPSCO also says the root cause was mismatched meter components identified when meter photos were reviewed during AMI installation. [^1]

## Practical interpretation
- Treat this as utility-ops and billing-integrity context, not as EMF signal.
- If a field stop or route note mentions meter correction, overbilling, or AMI-related meter review, log it separately from `source_state`, `construction_context`, and the measurement itself.
- This is useful as a QA/QC and route-context note, but it does not justify changing the exposure model.

## Hypotheses
- A dedicated note for AMI-linked meter correction should reduce confusion between billing anomalies and exposure observations.
- If future field work overlaps customer notifications or meter corrections, keeping that context separate should make later comparisons cleaner.

## Sources
- [^1]: https://www.nipsco.com/campaigns/meter-info