One measurement point, a whole life cycle, no dashboard.

A thermal power plant came to boTec with a refreshingly modest request: not a new system – a single place where a technician can finally see everything about one measurement point. It sounds small. It’s one of the most common, and most underestimated, problems in the process industry.

01 – the request

Notable for what it didn’t ask for

Most modernisation conversations start with a system to buy or replace. This one started with the opposite. The plant’s maintenance team was clear: the existing systems stay. SAP remains the system of record for maintenance and assets. The dedicated calibration-management system keeps owning calibration data. The document archives keep the drawings and manuals. Nothing gets ripped out.

What they wanted was smaller to describe and much harder to deliver: one central place where a technician can see everything known about a single measurement point, as its complete history over time, without logging into five systems and pulling a binder off a shelf.

Every instrument and asset in the plant already carries a unique identifier – a KKS tag. The identity of the thing was never in question. What was missing was a single, assembled view under that identity. The tag exists everywhere. The story it should tell lives nowhere in one place.

02 – the daily reality

The scavenger hunt in front of every asset

Picture a technician at a pressure transmitter that’s behaving oddly. To understand it, they need its maintenance history, its last calibration and valid measurement range, its datasheet and wiring diagram, its manufacturer manual, and its functional-safety test record. Each of those is available. Each lives in a different system.

None of these systems is wrong, and none should be replaced, they each do their job well. But each one holds a single chapter of the asset’s life, and no system holds the book. So the complete picture gets reassembled from scratch at every task, out of habit and memory. The people who are fastest at it are the ones who worked the plant for twenty years.

Every system holds one chapter of the asset’s life. None of them holds the book.

03 – the part that’s genuinely hard

The life cycle runs across systems and across time

A single screen pulling today’s values from five systems would already help. But the real requirement goes deeper: the complete life cycle of a measurement point – installed, calibrated, tested, modified, replaced. Management of change, from cradle to grave.

That’s hard because a measurement point is not static. Its range gets reset, the device behind the tag gets swapped, an inspection interval changes, the tag itself may be reassigned. To read the history correctly, you have to know what was true at each moment in time, a calibration certificate from three years ago has to be read against the device that was installed then, not the one hanging there now. Most systems store the current state, not the state over time. Reconstructing an accurate life cycle means tracing changing records across several systems, each with its own notion of when things changed.

04 – the problem in one image

A patient with no single medical record

The problem in one image
The GP has the check-ups. The hospital has the surgeries. The pharmacy has the prescriptions. A specialist has the scans. Every record is accurate and no doctor can see the whole history in one place. So each new treatment begins by piecing the story together from fragments, and the most reliable single source is often the patient’s own memory. A measurement point in a plant is that patient. And the technician who has been there longest is the memory.

That last part is the quiet risk. When the most complete record of an asset lives in someone’s head, every retirement is an unplanned data loss and in a control-and-instrumentation team, those retirements are already on the calendar.

The most complete record of the asset lives in the head of the technician who’s closest to retirement.

05 – the way out

Not another system. A view on top of the ones you have.

Because the problem lives between systems, the answer isn’t a bigger system, it’s a thin layer above them that gives every tag one continuous story. Concretely, it does five things:

• Assemble one view per measurement point. Each source system is modelled once; the layer links their data under the shared KKS identity, so everything known about a tag appears in one place – pulled live from the source, never copied.
• Make the life cycle readable across time. Time becomes its own dimension. The layer records what changed and when, so a tag’s history reads correctly even as devices, ranges and assignments evolve.
• Leave every system exactly where it is. SAP stays the master for maintenance, the calibration system stays the master for calibration; the layer complements and connects – it never competes, and nothing is migrated. This was the plant’s explicit condition, and it’s the right one.
• Give the floor an interface built for the floor. A simple, task-oriented view on tablet, phone or terminal – the technician sees the asset, not the systems behind it. The experience is decoupled from the systems of record.
• Start with a core scope, grow by need. Begin with a clearly bounded set of measurement points and the handful of systems that matter most; then extend, automated reports, QR- or barcode-driven document access, as each step proves its value.

Nothing below the layer changes. The technician simply gains one place to look.

06 – the lesson travels

Information is organised by system. Work happens by asset.

Beyond power generation, this is one of the most widespread patterns in the process industry, in chemicals, pharma, utilities, water. Skilled people maintain physical assets over decades, but the information about those assets is filed by system while the work is done one asset at a time. The mismatch stays invisible until you follow a technician for a shift.

The warning signs in your own operation: your technicians keep the real history of an asset in their heads or private spreadsheets; understanding one component means opening three systems and a document archive; no system can show you what was true about an asset at a past date; and the person who knows how it all fits together is close to retirement.

The fix isn’t another system on the pile. It’s a thin layer that gives every asset one continuous story, assembled from the systems you already trust and leaving them exactly as they are. That layer is exactly what the boTec DataBridge is built to be.