Sewer data according to the standard Exchange with consultancies and contractors Validated before it is used

Custom GWSW integration development

Appfront builds integrations with the GWSW, the Urban Water Data Dictionary (Gegevenswoordenboek Stedelijk Water) of the RIONED Foundation. It is the open standard that municipalities, water boards, consultancies and contractors use to exchange sewer and urban water data unambiguously. We connect your sewer management or project system to the standard, so that surveys, inspections and management data flow back and forth without translation work, validated before they are used.

What is a GWSW integration?

The Urban Water Data Dictionary, the GWSW, is the open standard for the unambiguous exchange and publication of data in urban water management. It describes objects such as pipes, manholes and pumping stations, and their characteristics, as an ontology. The RIONED Foundation maintains it together with the sector and provides tools for validating datasets. Data that follows the GWSW can also be found via PDOK.

In practice, a municipality receives data from an engineering consultancy, a contractor or an inspection company, each in its own format or in a version of the standard that doesn't quite fit. The data is converted by hand and entered into the management system. An error in a survey is only noticed when someone starts calculating with it. And data the municipality shares itself reaches a consultancy in a form that has to be translated all over again.

We build custom because parties differ: which management system you have, who you exchange data with, and which version of the standard those parties use. The standard is maintained by the RIONED Foundation; we make sure your systems work with it, even as the standard evolves.

According to the standard

Sewer and urban water data in and out of your system, according to the GWSW.

Exchange without translating

Surveys, inspections and management data between municipality, consultancy and contractor.

Validated first

Datasets checked against the standard before they are imported or shared.

How we build your GWSW integration

We start with your data: which asset management system you use, which parties you exchange data with, which data, and where most of the translation work lies. Parties often use different versions. We map this out so the integration can exchange data with everyone and a new version can be supported later. We test with real datasets from your partners, because that is where the differences that don't exist in theory turn up.

1
Mapping your data

Your systems, partners, data and versions.

2
Building the translation

Your data to and from the GWSW.

3
Validating and exchanging

Validation, and exchange with partners.

4
Go-live and maintenance

Go-live, monitoring, and maintenance when new versions arrive.

What a GWSW integration actually does

The components below feature in almost every GWSW integration. Which ones you need depends on your role.

Translating

Your data to the GWSW and back.

Validating

Datasets checked against the standard.

As-built surveys

From contractors in your system.

Inspections

Results against the right asset.

Share

Data to consultancies and via PDOK.

Log

Every exchange logged.

Who we build a GWSW integration for

The integration is intended for anyone who exchanges data on sewerage and urban water.

Municipalities

Sewer management. Importing data is the core.

Water boards

Pumping stations and treatment. Exchange matters most.

Engineering firms

Data for design. Translation is what's needed.

Software suppliers

Asset management or inspection software. The standard is the core.

Technology and integrations

This page is about integrations with the GWSW. For sewerage, see our page on sewer software, for open geodata our page on a PDOK integration, and for concepts such as linked data our page on a SKOS integration. You can read about our approach on building software.

GWSW Stichting RIONED Ontology Pipes, manholes and pumping stations Dataset validation As-built surveys and revisions Sewer inspections PDOK Versions of the standard Integration with sewer management

Why Appfront for your GWSW integration?

Data that is translated anew with every exchange loses something each time. That is what we build on: data that follows the standard, exchange without translation, and validation first.

No translation work

Everyone uses the same standard.

Reliable

Errors spotted before they matter.

Reusable

Data for management and design.

Security and privacy in a GWSW integration

The integration works with data on underground infrastructure, some of which is confidential. Access is set up per role, and every exchange is logged.

The integration runs in a European data centre or in your own environment, with encrypted storage and daily backups.

Frequently asked questions about a GWSW integration

Questions that asset managers and firms ask before they get started.

The Gegevenswoordenboek Stedelijk Water (Urban Water Data Dictionary): the open standard for exchanging data unambiguously in urban water management, such as data on pipes, manholes and pumping stations. It is maintained by Stichting RIONED together with the sector. Municipalities, water boards, consultancies and contractors use it to speak the same language about their data.

It means that objects, attributes and the relationships between them are described unambiguously, so that systems understand them in the same way. Data that follows the GWSW can therefore also be used as linked data. A manhole or pipe then means the same thing in every system, with the same attributes.

The integration checks data against the standard before it is imported or shared, and Stichting RIONED also offers its own tools for this. Deviations go back to whoever can fix them, with the reason. That way only data that is correct ends up in your system.

The version that you and your partners use. Not everyone switches at the same time, so an integration sometimes has to handle several versions. We map this out in the first step. When a new version is released, the integration shows what changes for your data.

Yes, if your asset management system has an interface or import function. A survey in line with the GWSW is validated and then submitted to the asset management system, so it does not have to be entered again. Deviations go back to the contractor, with the reason, before the survey is accepted.

Since version 5.0, the Dutch CAD Standard (NLCS) has included an integration with the GWSW. As a result, objects in drawings line up better with the data in asset management, and a sewer pipe from a design drawing does not have to be described again.

For municipalities and water boards that receive a lot of data from partners, for engineering firms and contractors who supply data, and for suppliers of asset management and inspection software who want to support the standard.

Sewer data without the translation work?

Tell us which asset management system you use, which parties you exchange data with and where translation currently takes place. We will show you what the integration looks like.

Edit content