One register for the whole network.
Water and sewer, georeferenced, whole-life — the system of record the models run on and risk scores against.
HydroDSS keeps your network as a single system of record, not a drawer of files. Water and sewer assets live in one georeferenced PostGIS register, carrying lifecycle and valuation, a full records-and-inspection history, and parameters auto-populated from a cited spec catalog. Condition feeds straight back into the hydraulics. It's the spine the models run on, the inspections attach to, and the risk layer scores against — one register, not three tools.
The register your models and your risk both read from.
One register, shared by every part of the platform — the engine reads it to run, the risk layer scores against it, and the GIS draws it. No re-keying the network into a second tool.
Water and sewer, in one register.
A single, type-discriminated PostGIS register holds the whole network — mains, pumps, valves, junctions, manholes, conduits — water and sewer in one place, not a separate inventory per domain. Georeferenced, so every asset sits in true coordinates on a shared map.
Parameters filled, not hand-keyed.
The register draws on the cited spec catalog: give it a material and a size — “DN225 PVC” — and it resolves diameter, wall, strength class, cross-section shape, and roughness defaults, each traceable to a source. Modellers stop hand-keying the numbers a standard already fixes.
In the cloud, on the map, versioned.
The register is the system of record — multi-tenant with row-level tenancy, versioned, and shared. Your network is a live view your whole team can open in the browser, not a file emailed between desktops.
More than a geometry on a map.
Each asset is a full lifecycle record: what it is, what it's worth, what's happened to it, and what the platform has computed about it. Curated columns for what risk and planning query on; a flexible tail for the class-specific rest.
The asset, whole-life.
Beyond geometry: lifecycle status, expected and remaining useful life, install and replacement cost, valuation and depreciation — the ISO 55000 / IIMM fields capital planning needs, on every asset.
Everything that happened to it.
A timeline of incidents, inspections, maintenance, photos, and documents per asset — the operational history, attached to the asset on the map, not buried in a separate work-order system.
Condition, risk, and life, in place.
Condition grade, risk band, and remaining life are written back onto each asset by the inspection and risk runs — so the register sorts and the map colours without a join. The source of truth stays the run; the asset carries the answer.
It surfaces as an asset detail view — attributes, condition timeline, risk breakdown, deterioration, records, and the asset's role in the model — opened from the map, with spec-catalog autofill on the editable fields.
Inspections with the rigor the standards expect.
Condition isn't a free-text note. Coded inspection — to the established sewer-coding standards (NASSCO PACP / MACP; WRc MSCC / EN 13508) — turns a CCTV survey into graded, located defects, rolled up to a structural and O&M condition rating per segment. Standards-agnostic by design, via a code catalog rather than hard-wired codes.
Graded and located
Each observation carries its code, severity grade (1–5), distance, and clock position — the table-stakes inspection model.
Structural & O&M
Observations roll up to structural, O&M, and quick ratings per segment — the grade that drives deterioration and risk.
Video, scrubbed to the defect
The inspection video links to each coded defect's distance — and AI auto-grading is the longer-term aim.
A defect isn't just a maintenance ticket.
Per-asset condition does two things at once. It raises a conduit's likelihood-of-failure for the risk layer, and it degrades the hydraulics: deposits and corrosion push roughness up and effective diameter down. The same condition reading feeds both renewal planning and a more honest model.
Capture condition
Per-asset condition on the register — material, age, defects, increasingly coded from inspection video.
Adjust the hydraulics
Condition maps to roughness and effective-diameter changes, so the model reflects the pipe as it is, not as built.
Raise the risk
The same reading lifts likelihood-of-failure, which the risk layer combines with criticality to reprioritise renewals.
The register sits at the centre.
Fills the parameters
Cited geometry, class, and roughness defaults auto-populate each asset from its material and size.
The engine →Runs on the register
EPANET and SWMM runs build straight from the register's GeoJSON — the model is a view of the assets.
Asset risk →Scores against it
Likelihood and criticality are computed per asset, then rolled into a defensible renewals plan.
Where it stands: the register and its GIS, the records timeline, lifecycle and valuation attributes, the asset detail view, spec-catalog autofill, coded PACP inspection condition-grading, and the condition→hydraulics loop are all built and running on dev; CCTV video review and AI auto-grading are on the roadmap. HydroDSS is in private build ahead of a 2026 launch — everything here is coming soon, not yet generally available.