Waternet: Data Libraries
At a glance
Together with Waternet, we built a shared Object Type Library that defines exactly what asset data should look like, so contractors hand over information that is consistent, meaningful, and ready to use from day one.
Challenge
Asset data came from a large number of contractors and systems, in various formats and without a common meaning, making it difficult to exchange data between applications and organizations.
Solution
A Reference Data Library, also known as an Object Type Library, is made available as Linked Data to define asset types and the precise data contracts that need to be delivered.
Results
Consistent contractor handovers, data that carries its own meaning, and a software-independent foundation that keeps growing in value.
The challenge
When asset data loses its meaning
Waternet is responsible for the full water cycle in its region, from drinking water to wastewater treatment. Managing that infrastructure well depends on one thing above all: reliable data about every asset in the network.
But asset data is only useful when it carries meaning, and too often it does not. Data arrives without the context that explains what it actually describes, which makes it unintelligent the moment it leaves the original system. It sits locked inside single databases, disconnected and incoherent. Since each contractor and every application uses its own language, exchanging the data between organizations is both slow and unreliable.
For asset owners, this is more than an inconvenience. When the data provided by contractors cannot be trusted or reused, every subsequent decision involves greater risk and additional rework. We see this problem throughout the water industry and in other asset-related sectors, and we know it can be overcome.
Asset data that finally works the way it should
The advantages increase over time as a shared library is in place, so the value grows with continued use.
Consistent handovers
Because there is a common definition used by all contractors, the data delivered is consistent, complete, and ready for use, rather than requiring cleanup at a later stage, so handovers become easier to trust.
Meaningful Information
By connecting data to the library, every record gains context and meaning. Waternet can query across different databases without first having to transform, translate, or interface the data.
A future-proof foundation
Waternet’s data, published in open standards and linked to other libraries, is ready to be integrated into the wider data ecosystem, and its value continues to grow as more sources are linked.
Our approach
Set the standard, and invite the entire value chain to meet it
We assisted Waternet in creating a Reference Data Library, also known as an Object Type Library, and publishing it as Linked Data. Rather than addressing data quality afterward, Waternet now establishes the standard at the beginning and asks the entire value chain to base its work on it, so asset data arrives ready for use. Below is a step-by-step account of how we carried out this initiative together.
A shared enterprise dictionary
We first designed and created a model for an enterprise dictionary of asset types: a single, mutually agreed definition of what each asset is and what it means. This formed the foundation of Waternet’s Object Type Library.
Clear handover requirements
We then added the specific fields that Waternet wishes to receive to those logical definitions, so contractors now know exactly what data to provide, and Waternet knows precisely what it will get.
Linked Data and open standards
We published the library as Linked Data as part of the Semantic Web; because it uses open standards, the library does not depend on any particular application, and the data associated with it carries its own context, no matter where it goes.
Tooling, and the skills to own it
We not only supplied the necessary tooling and consultancy to set up, maintain, publish, and manage the library, but also ensured that Waternet’s own team could continue to keep it active and developing, without relying on external solutions; the solution remains in their hands.
Alexander Worp
”The thinking behind and development of (data) standards is clearly reflected throughout their advice, vision, and strategy.”
