Service Quality Improvement: An AI-Powered Roadmap
Ago 3, 2026 in Guia: Como fazer
Drive service quality improvement with a practical roadmap covering KPIs, AI automation, change management, and measurement for lasting results.
Não é membro? Registe-se agora
Kelwin em Jun 19, 2020
Meter tampering is a common threat to the business side of utility services and a public security threat, incurring uncontrolled tweaks that may increase the risk of accidents. So, fraud detection is core for any utility service company.
The presence of users that manipulate the network typically translates to an increased service price for the compliant users, since for sustainability of the services, remaining users absorb the additional load costs in addition to the inspection procedure costs associated with identifying such frauds.
This post showcases one of our previous AI projects on detecting meter tampering in water services. However, it can be used interchangeably in other types of services such as electricity, gas, and TV. The challenge we faced was identifying users with a high probability of meter tampering.
Marcar uma reunião com Kelwin Fernandes
Quer discutir esta ideia mais a fundo?
The first issue we faced was how reliable our labels were. While we had the outcomes from previous inspections (legal or fraud), inspections with a legal outcome may result -in some cases- from bribes. So, while you can trust positive fraud labels, negative cases are a mixture of actual legal cases and corruption itself. Another source of error on the legal observations are difficult-to-detect tampering, for example, in cases where the fraud was not directly on the meter but on bypassing the system at a different hidden point of the network.
We can model this learning task with multiple paradigms.
Finally, This problem tends to be extremely unbalanced. Take a look at one of our previous papers on how to reformulate class imbalance as ranking tasks (aqui) which can be combined with any of the solutions mentioned above.

We trained our models combining three categories of data: contractual, consumption, and context data.
We included information about the:
While some features such as the ZIP code and the income capacity of the house may be correlated with fraud, we should take this with a grain of salt since we may be increasing bias and unfairness in the decision making (check this book).
Meter tampering often is associated with dramatic drops of consumption. Thus, we extracted features from aggregated consumption over time. Since consumption is seasonal and changes from house to house, it is essential to consider relative values instead of absolute ones. For example, you should observe the percentual change in usage between months instead of the absolute difference. We also normalized these features with respect to the global trend between any two months to compensate for seasonality.
Other fraud correlated patterns we found were consumption with low inter-month variability (i.e., the standard deviation of the consumption being too small) and “capped” expenditure (i.e., over the last year, the maximum value is repeated multiple times).
Context data proved to be the most important one. Meter tampering is like a virus and spreads among neighbors, especially among neighbors with the same model/brand of meter. Therefore, we extracted information such as the density of (recent) fraud within K meters (for multiple values of K) with and without stratification per meter model. Please pay attention to our emphasis on density and not a number. In this project, relativizing features to the local context of the individual and the region was critical to learn efficiently. If you don’t know how dense an area is (pretty common in countries with scarce open data), consider internal assets such as the number of contracts you have in the region and the density of your internal assets (e.g., pipes) as a proxy for density.
When time and space are part of our learning system, we must pay attention to the way we split our data for performance estimation. Random splits will tend to “leak” information in training, giving overestimations of the model performance. In this case, we suggest splitting both temporally and geographically, as illustrated in the following graph.
Other variables to consider for splitting train and test might be the inspection rounds, inspection team, among others. The right split and its granularity (e.g., splitting between months/years, city/district/region) depend on business requirements and the way we intend to deploy our models.
Predictions by themselves are not useful. We need to combine them with a decision process considering a KPI. In this case, we could use the additional information for fraud detection to build cost-effective inspection schedules and routes, finding the right trade-off between the expected benefit obtained from inspecting a house versus the cost of such inspection. We will cover this topic on a different blog post.
Learn how to create valuable AI solutions from predictions to actions.Course, Templates
Data Ignite
We discussed here how to detect fraud detection of water meter. However, the utility industry is a vast field for the application of AI, from determining regions with a high potential value of prospect acquisition, churn prediction, anomaly detection in the network, among others. If you want to explore any of these ideas, just message us!
Gosta desta história?
Ofertas especiais, últimas notícias e conteúdo de qualidade na sua caixa de entrada.
Ago 3, 2026 in Guia: Como fazer
Drive service quality improvement with a practical roadmap covering KPIs, AI automation, change management, and measurement for lasting results.
Jul 27, 2026 in Guia: Como fazer
Follow a step-by-step Generative AI Implementation roadmap to align resources, integrate models, and secure strong ROI in your enterprise projects.
Jul 20, 2026 in Guia: Explicação
Master data quality management techniques. Learn to profile, cleanse, & validate data for better decisions & AI readiness.
| Bolacha | Duração | Descrição |
|---|---|---|
| cookielawinfo-checkbox-analiticas | 11 meses | Este cookie é definido pelo plugin de Consentimento de Cookies do RGPD. O cookie é usado para armazenar o consentimento do utilizador para os cookies na categoria "Análise". |
| --- O seu texto é uma etiqueta ou nome de campo, provavelmente de um sistema de gestão de cookies ou de um formulário web, e não uma frase completa que necessite de tradução contextual. No entanto, se o objectivo for manter a clareza e a funcionalidade para um utilizador de língua portuguesa, sugiro a seguinte tradução e explicação: **"Checkbox Funcional"** **Explicação:** * **Checkbox:** Refere-se ao elemento gráfico de marcação (uma caixa que pode ser seleccionada ou desmarcada). * **Funcional:** Indica que esta caixa de seleção está relacionada com funcionalidades essenciais do website, como o login, a gestão do carrinho de compras ou outras características que tornam o site utilizável. Se esta etiqueta pertencer a um contexto onde se refere especificamente a cookies, a tradução poderia ser ajustada para ter mais clareza: **"Aceitação de Cookies Funcionais"** ou **"Cookies Essenciais (Funcionais)"** Esta última opção é comum em avisos de cookies para indicar que estes são estritamente necessários para o funcionamento do site. --- | 11 meses | O cookie é definido pelo consentimento de cookies GDPR para registar o consentimento do utilizador para os cookies na categoria "Funcional". |
| cookielawinfo-checkbox-necessary | 11 meses | Este cookie é definido pelo plugin GDPR Cookie Consent. O cookie é usado para armazenar o consentimento do utilizador para os cookies na categoria "Necessário". |
| cookielawinfo-checkbox-outros | 11 meses | Este cookie é definido pelo plugin GDPR Cookie Consent. O cookie é usado para armazenar o consentimento do utilizador para os cookies na categoria "Outros". |
| checkbox-performance-cookielawinfo | 11 meses | Este cookie é definido pelo plugin GDPR Cookie Consent. O cookie é usado para armazenar o consentimento do utilizador para os cookies na categoria "Desempenho". |
| política_de_cookies_visualizada | 11 meses | O cookie é definido pelo plugin GDPR Cookie Consent e é utilizado para armazenar se o utilizador consentiu ou não com a utilização de cookies. Não armazena quaisquer dados pessoais. |