От водоподготовки до работы с абонентами: как данные водоканала превращаются в решения — сначала аналитика, модели только там, где они полезны.
Не каждому вопросу нужен ИИ. У каждого примера указан метод, на котором он построен.
Аналитикаправила, расчёты, показатели, тренды
Прогнозстатистические прогнозы и оценки риска
С участием моделимодель для определённой контролируемой задачи например тональность, классификация, рекомендации
150+ сводок ежемесячно. Ниже два реальных примера.
Реальные сводки, обезличенные.
Две сводки, которые бригады водоканала получили из платформы: перерисованы с исходными цифрами и переведены. Имена, логотипы и ссылки удалены.
AnalyticsReal dataWhat happened with customer requests this week?Weekly digest · requests · nature · teams
AnalyticsReal dataIs the maintenance plan being delivered?Monthly report · work orders · equipment in service · interventions
Реальные дашборды, обезличенные данные.
Рассчитаны по данным двух операторов — водоканала и оператора городских служб, — сведённым по месяцам и категориям. Без имён, адресов и лицевых счетов.
AnalyticsReal dataWhat do water customers contact the utility about?Water utility · 2,122 customer requests · Apr 2025 – Sep 2026
Model-assistedReal dataWhat is the tone of customer complaints?Water utility · 1,861 analysed descriptions · Apr 2025 – Sep 2026
Model-assistedReal dataWhat should maintenance investigate first?Repeated corrective events detected across the treated-water pump group.
Model-assistedSample dataWhich category does each free-text request belong to?Customer requests in free text · by proposed category
Model-assistedSample dataWhat should the team do next on each request?Recommended next actions · agent decision
Сначала аналитика. Модели — когда полезны.
Большинство сценариев опирается на правила, показатели и статистический анализ. Когда модель даёт выигрыш, её вызывают для определённой задачи и по тем же правилам Sparkoper.
The 406 billing requests by nature, from April 2025 to September 2026. Billing without consumption alone accounts for more than half.
AnalyticsReal dataWater utility · 1,461 requests with a usable account · Apr 2025 – Sep 2026
Which issues bring customers back?
20%of requests with a usable account are repeat contacts for the same issue category
Water shortage24%
Payments21%
Billing17%
Cut-offs & reconnections10%
Bursts & leaks0%
Share of requests whose customer account raised the same issue category more than once over the period, by category. Only requests with a usable account number are counted. A repeat contact does not prove an issue was left unresolved: it shows where first-contact resolution and proactive follow-up deserve a closer look.
Corrective requests per asset, December 2025 to September 2026. 42 assets generated at least one corrective record; the 16 that came back more than once account for 51 of the 77 records. They are the first candidates for root-cause analysis.
AnalyticsReal dataUrban services operator · 1,136 requests · since 2023
What do residents ask for?
31%on the environment
Environment31%
Services22%
Infrastructure11%
Urban planning10%
Security9%
Communication6%
Other10%
Requests by category since January 2023. Smaller categories are grouped under Other.
AnalyticsReal dataUrban services operator · status by year of creation
Do requests get closed?
97%of requests closed
ClosedIn progressNot startedCancelled
2023–202487%
202597%
202697%
Current status of requests by year of creation. 2023 and 2024, with only 15 requests, are grouped. 2026 runs to 12 September, so recent requests are still in progress.
PredictiveReal dataUrban services operator · monthly requests and projection
How many requests to expect in the coming months?
≈ 107requests expected per month
Monthly requestsProjection80% range
108
Nov2025
186
Dec
108
Jan2026
83
Feb
66
Mar
63
Apr
46
May
72
Jun
111
Jul
138
Aug
Sep
≈ 107
Oct
Nov
Monthly requests since November 2025. Projection: the average of the last three complete months; the band covers 80% of past month-to-month deviations. A deliberately simple statistical method, not a model.
≈ 9corrective requests expected in the next 30 days
5–13likely range (80%)
Corrective requests per monthProjection80% range
8
Jan2026
8
Feb
11
Mar
11
Apr
9
May
12
Jun
11
Jul
3
Aug
≈ 9
Next30 days
Real, anonymised data. Corrective requests per month, January to August 2026. Projection: a Poisson count model on the average daily rate from 1 January to 12 September 2026 (77 requests in 255 days), with an 80% predictive range. Rather than predicting individual failures from too few variables, it sizes the corrective workload to plan for.
Which pumps are most likely to fail in the next 30 days?
3pumps to inspect first
P-14 · Raw water86
P-03 · Booster78
P-09 · Treated water71
P-21 · Booster54
P-06 · Raw water42
P-11 · Wash water31
P-17 · Treated water22
P-02 · Booster12
Invented figures. The score combines running hours, vibration and temperature trends, and failure history. Above 70, the pump is inspected before its next planned maintenance.
PredictiveSample dataDistribution network · probability of at least one leak, by sector
Where are leaks most likely this month?
2sectors above 40%
Sector 762%
Sector 348%
Sector 1235%
Sector 527%
Sector 918%
Sector 111%
Sector 47%
Sector 104%
Invented figures. The probability combines pipe age and material, pressure variations, night flow and repair history. The top sectors are the first candidates for acoustic leak detection.
PredictiveSample dataTreatment plant · average daily demand, thousand m³
Will demand exceed production capacity in the coming months?
95%of capacity by November
Average daily demandProjection80% rangeProduction capacity
78
Sep2025
80
Oct
83
Nov
85
Dec
88
Jan2026
90
Feb
92
Mar
95
Apr
97
May
100
Jun
102
Jul
105
Aug
Sep
Oct
≈ 114
Nov
Invented figures. Average daily demand per month, in thousand m³, projected three months ahead with an 80% range. The top of the range crosses capacity in November: time to plan storage and pressure management.
Real, anonymised data. The structured category says Billing, but 85 of the 406 comments also describe a service interruption: billing during a period without supply, bills without consumption, a prolonged lack of water. Across the whole dataset, 132 requests reveal a water-supply issue that is not visible in their primary category, about 13% of requests outside Water shortage. Only counts are published; no comment is shown.
Real, anonymised data. A model rated the tone of 1,861 customer request descriptions, from April 2025 to September 2026: negative, neutral or positive. Only the shares are published. A complaint is negative by nature; this share is the baseline to track over time.
Model-assistedReal dataRepeated corrective events detected across the treated-water pump group.
What should maintenance investigate first?
11hydraulic-mechanical events across 3 pumps
Calculated facts
3 pumps · 11 events · same failure family
↓
Suggested investigation
Review shared hydraulic-mechanical conditions across the three pumps
Recommendation for maintenance review — not an automated decision.
Treated-water pump A3
Treated-water pump B4
Treated-water pump C4
Other equipment in the system1
Real, anonymised data, December 2025 to September 2026. After removing three exact duplicates (same date, asset and type), the treated-water tank system has 12 distinct corrective events; 11 concern three pumps of the same family, all hydraulic-mechanical. Analytics compute these facts; a model can then draft a recommendation from them, such as the one above. It does not detect the figures and does not decide in the engineer's place.
Model-assistedSample dataCustomer requests in free text · by proposed category
Which category does each free-text request belong to?
85%classified automatically
Classified automaticallyChecked by an agent
Billing453
Water shortage405
Leaks & bursts224
Meters128
Other85
Invented figures. A model proposes a category for each request written in free text. Below a confidence threshold, an agent checks the proposal before the request is routed.
Model-assistedSample dataRecommended next actions · agent decision
What should the team do next on each request?
77%accepted as proposed
Accepted as proposedEdited by the agentRejected
Send a field team81%13%
Call the customer back74%18%
Correct the bill63%27%
Merge with an open request88%
Invented figures. For each request, a model recommends the next action. Nothing happens until an agent accepts, edits or rejects it, and every call to the model is logged.