For integrators and consultants

A deliverable for the plants you already serve: every tag mapped and described, on paper, in Norwegian or English, without touching the SCADA you built. What it reads, and how to start.

175 of 212

tags named on two real Danish sites, a wastewater plant and an office building, none of them wrong. The rest were refused, each with a reason.

4,000 of 4,000

generated exports, mixing the layouts, separators, encodings, clocks and time zones real files have, read right or refused with a reason.

For integrators and consultants.

You already know the plant, its people and its control system. This gives you a deliverable you can put in front of them: every tag mapped and described, on paper, without touching the SCADA you built.

A utility rarely buys "contextualisation". It buys a SCADA upgrade, a service agreement or a report, from someone it already trusts. That is usually you. So this is built to be used by you, on your customers' exports, as part of work you already do.

What you can deliver

A mapping report of the plant's operating data, in Norwegian or English, printed or as a PDF: every tag with its quantity, unit and machine and the evidence for each; the tags that could not be placed, each with the reason; the readings whose data went wrong this week; and what needs a person on site. It covers step 3 (map) and step 5 (describe) of Norsk Vann's seven steps to digital maturity (report 300/2026) for the data in the exports, and it is a basis for the inventory of systems a waterworks must now have under digitalsikkerhetsforskriften. It does not make anyone compliant, and it says so on the page.

What it never touches

Nothing is installed on a PLC, a SCADA server or a historian, and no connection is made to them, unless you turn on the optional OPC UA reader, which reads and writes nothing. It reads export files you or the operators already make (CSV or Excel, in the plant's own language and clock) on one machine, and it sends nothing anywhere. It does not replace the control system or compete with it: it reads what the control system writes.

What it reads

Wide exports and one row per reading; Norwegian, Danish and English headers; decimal commas and thousands separators; local time with summer time, moved to UTC only where the data shows the change; Windows-1252, UTF-16 and Excel; a file per sensor or several stations in one file. Each of these is a test that runs on every change, written after real exports published by utilities in Denmark, the United Kingdom, Germany and Spain. We have not yet read an export from a Norwegian waterworks, and we would rather say so than pretend.

How to start

Write to [email protected]. You get one zip that runs on Windows with nothing installed, and the security pack for your customer's IT and OT security. Terms for using it on your own customers' plants are agreed in writing, before you start, and nothing about a plant is shared without its owner's yes.

Sources and data

The results on this page are read from results files built from the data below, not typed by hand. Who made each data set, and its licence, is on the sources page.

Back to the front page

Start with one export.

We sit with you and run it on a machine you control, so nothing leaves the site. You keep the mapping report: every tag with its quantity, unit and machine and the evidence for each, what could not be told and why, and the data that went wrong this week, in Norwegian or English.

Write to [email protected]. If you would rather send us an anonymised export, we sign your data processing agreement first.

Read next