In a failure the dispatcher gets a list of valves, not a paper map
Valve isolation shows which valves to close and who will lose water. The K-GESUT export goes to the authority with completeness validation. Knowledge of the network stops living in a few people's heads.
Three problems we solve
Three situations in which the cost of a paper map becomes visible.
Two people in the company know the network
Paper maps, files on drives and the memory of the two longest-serving employees. When they are away, the network stops making sense. GIS merges it into one source that every department uses, from one screen.
Valves are picked from memory
During a leak the dispatcher spreads out a map and rings colleagues, and the water keeps running the whole time. GIS gives the list of valves to close and the customers who will lose water within seconds.
Data filed with the authority by hand
Filing data in K-GESUT format takes several days of tedious work in which errors and a rejection from the authority come easily. GIS generates the export automatically and checks completeness before anything is sent.
Who GIS is for
Dispatchers and maintenance teams
People responding to failures - needing a network map with valve isolation analysis: which valves to close and which customers will lose water.
Surveying and GIS departments
People maintaining records and reporting to the authorities - needing compliance with K-GESUT, the Polish coordinate systems and the national mapping agency's base maps.
Management and capital planning
People responsible for refurbishment, modernisation and the multi-year budget - needing reports on asset age and condition and a reconstructable network history.
What GIS can do
Six areas in one system - Map, Inventory, Analyses, Protection zones, Editing, Reports.
Why GIS
What sets GIS apart from paper maps and foreign systems.
Emergency response analyses
Valve isolation with a ready list of valves to close and customers cut off is the function dispatchers ask for most - a plan in seconds instead of picking valves by hand from a paper map.
Native compliance with Polish law
K-GESUT, the PL-1992 and PL-2000 coordinate systems and the national base maps (orthophoto, BDOT10k, land register, utility register) are built in. Foreign systems need costly adaptation; here the data speaks the authorities' language from the start.
History and an immutable audit trail
You can reconstruct the state of the network at any point in time and account for every change. Versioning instead of deletion and a tamper-resistant log - important for audits and for critical infrastructure cybersecurity.
One platform, on-premise
GIS is part of the HydroNexis ecosystem (WMS, Control, FSM) from a single supplier. An on-premise deployment on the customer's server gives full control over critical infrastructure data.
What it looks like in practice
Screens from the GIS module deployed at a water and sewer network operator.
Network map with layers
The entire water and sewer network over a base map, with a thematic layer panel (water mains, hydrants, valves, protection zones, failures), asset search and PL-1992 coordinate readout. A daily window onto the network for every department.
Network analyses
Topological tools for dispatchers and engineers: valve isolation (which valves to close), upstream and downstream flow tracing, and supply zone. The map becomes a decision-making tool during a failure.
Integrations
GIS is the platform's geographic core - it exchanges data with the national spatial resource and with the other HydroNexis modules.
The surveying authority (K-GESUT)
Generation of network data in K-GESUT format with completeness validation before submission. A statutory obligation met without manual, error-prone work.
Official base maps (Geoportal)
Orthophotomap, BDOT10k topography, the land register and the utility register as a backdrop for the network - working on current, reliable reference data without having to obtain it by hand.
GIS software (WFS / QGIS)
Publishing network data externally over WFS - working with surveyors and designers in QGIS without manual exports.
WMS (intake operations)
Linking map data with the operational data of intakes, wells and treatment stations from the WMS module - a fuller picture of water production assets.
Data import (SHP/GeoJSON/GML)
Loading the network from Shapefile, GeoJSON and GML files - easy migration of existing data and ongoing updates.
Single sign-on (SSO)
Shared, secure sign-in across the platform - one login for several modules, with access restricted to the corporate network or VPN.
Three things we hear before a GIS decision
Answers without waiting for a sales conversation.
"Our network data is incomplete"
It almost always is. We do the import from SHP, GeoJSON and GML together with a topology check, so it is immediately clear where connections are missing. We run the analyses on whichever part of the network is complete.
"We already have QGIS and a surveyor"
The two are not mutually exclusive. GIS publishes data over WFS, so the surveyor carries on working in QGIS. The difference is for the dispatcher, who needs a shutdown analysis in seconds, not a file to open.
"Network data cannot leave the company"
GIS can be deployed on-premise on your own server, with access restricted to the corporate network and VPN. For critical infrastructure operators this is usually the only acceptable option.
Frequently asked questions
What does a GIS implementation look like?
How does valve isolation analysis work?
Which standards and formats does GIS support?
What about data security and collaborative work?
Can we migrate our existing network data into GIS?
Can GIS be deployed on our own servers (on-premise)?
Materials and contact at hand
The code opens the page directly on your phone. You will find the same set at our trade fair stand.
We start from what you already have on disk
In the conversation we look at your network files and say plainly how much of it is ready for analysis straight away and what needs filling in.