Water utilities
A leak at chainage 12+340 is not the same job as a leak somewhere on Pipe P-123.
Location is part of the business meaning. Segment attributes — material, diameter, lining, soil type, pressure zone, age cohort — change the maintenance decision, the crew, the isolation strategy, and the compliance record. NordEAM models all of it natively.
Why standard EAM fails water networks.
Traditional EAMs treat assets as homogeneous records. A pipe is a row. A maintenance tag is a property. But distribution mains, transmission lines, trunk mains, and rising mains don't behave that way — their risk, condition, and service impact change continuously along their length.
Standard EAM
- ✕ Asset is a homogeneous block
- ✕ Leak recorded as "somewhere on Pipe P-123"
- ✕ Work order has no precise linear location
- ✕ Condition data stored at asset level, not segment level
- ✕ Renew "the pipe" — not the high-risk section
NordEAM
- ✓ Native Linear Referencing System — route + chainage
- ✓ Work orders carry from/to measures and segment context
- ✓ Segment attributes: material, soil, pressure zone, lining, age cohort
- ✓ Dynamic segmentation — multiple views over one route
- ✓ Target the 60 metres between 12+340 and 12+400, not the pipe
A data model designed for how water networks actually work.
Three layers that keep the model maintainable as networks change — without duplicating physical records or rebuilding the GIS every time a pressure zone is reconfigured.
Base route — the ruler
A stable route ID with calibrated measures. This is the spine: all segment views, all work, all measurements reference it. Route calibration integrity is everything — drift here and location reliability collapses everywhere else.
Event tables — what varies along the route
Segmentation as events over the base route, not duplicated physical records. Physical segments (material, diameter, wall class, lining, joint type). Condition segments (grade, defect type, corrosion proxy, risk rating, RUL). Pressure zone segments (zone ID, band, transient risk, critical customers). Logical segments (planner group, contractor zone, safety classification). Environment segments (soil type, corrosivity, traffic load class).
Work and measurements — what happens
Notifications, work orders, confirmations, and measurement documents all carry from/to measures and offsets. Work history is therefore spatially consistent — the segment knows what was done to it, at what chainage, by which crew. This is what makes inspection history usable for segment-level decision-making.
Six capabilities that change how you run the network.
Built on the three-layer model — so every capability works at segment resolution, not just asset resolution.
Dynamic segmentation
One route, multiple concurrent views: hydraulic zones, condition grades, physical material cohorts, pressure regimes. Change a pressure zone boundary and the segment view updates — no one is rebuilding GIS layers or asset child records.
SCADA and IoT closed loop
SCADA/IoT tags map to SAP measuring points tied to linear location. Pressure drops, flow anomalies, and leak-noise readings trigger notifications at the correct segment. The agent creates the work order with chainage, isolates the pressure zone context, and routes to the right planner group.
Segment-level KPIs
Bursts and failures per km-year, calculated at segment level and summarised by pressure zone, material cohort, age band, and soil zone. Failure density by cohort. MTTR derived from work timestamps. RUL screening for corrosion-driven risk. The right KPIs for capital programme justification.
Treatment asset hierarchy
Pump stations, treatment works, and reservoirs managed as a full equipment hierarchy — pumps, blowers, filters, clarifiers, instrumentation. OEE-grade telemetry, failure mode analysis, and agentic work order generation. The same platform as the distribution network, with no shared data model compromise.
Capital efficiency — renew the right section
When failure and condition are tied to segments, renewal programmes become surgical. You stop renewing "the pipe" and start renewing the 60-metre high-risk section with known material, age, and corrosion proxy. CAPEX targeting improves. Emergency OPEX from repeat failures falls.
GIS as a peer system
GIS is the master for geometry, topology, and LRS calibration. NordEAM is the master for maintenance, costs, and inspection. Bi-directional sync on a controlled key set — route IDs, start/end points, and business-critical attributes. No "sync everything" complexity. No ambiguous data ownership.
The segment-centric work order lifecycle.
Every step carries precise linear location and segment context — so the maintenance record is spatially consistent and the history is usable for the next decision.
- 1
Detect
SCADA alarm, customer report, leak detection, or inspection finding — all tied to a segment at the point of capture.
- 2
Record
Notification with linear location, defect coding, and segment context (pressure zone, material, soil type, criticality class).
- 3
Triage
Agent models valve isolation strategy, identifies affected customers and pressure zones, checks for open permits and traffic management conflicts.
- 4
Plan
Work order with planner group, permits, traffic management plan, GIS map, materials list, and prior work history for the segment.
- 5
Execute
Field crew captures actual chainage/offset, replacement length, materials used, and restoration notes. Map-first mobile — no ambiguous location descriptions.
- 6
Confirm and learn
Confirmation and measurement documents include linear location. Post-repair data updates condition segmentation. Segment RUL and risk score refresh. The network gets smarter.
Bring a pressure zone and a treatment works. We'll show you both.
Walk through a burst response on the distribution network and a pump overhaul work order at the treatment plant — same session, same platform, same data model.