An identifier tells you what you are looking at.
A ContextTAG tells you what it is part of, what it does, where it is and what feeds it. Every line comes from data you already have.
What existing data already knows.
Every line answers one question. Read them top to bottom.
Full name is a key: every item can be looked up, and the QR takes your phone straight to the digital record.
Data fields on ContextTAG are configurable.
−UCA01What the tag says
A technician stands in front of a switchboard in a large installation. The tag says this much. The questions are these:
A conventional tag answers the first question. A ContextTAG answers the rest.
The information already existed. ContextTAG made it visible.
Every line on the plate is something your data already knows. Follow any of them.
Nothing on this plate was typed in. The header strip says what the object belongs to, LOC where it sits, SUPPLY FROM what feeds it. Where the data has no answer, the plate shows nothing, so a gap on the plate is a gap in the data.
The object already has a name. That name is the key.
What it belongs to, where it sits, what it is connected to. Facts you already maintain.
The questions this tag should answer. Chosen per job.
One ink on white, fixed geometry. Made for the wall, not the screen.
The QR takes your phone to the record behind the tag.
A cable marker asks where from and where to. A switchboard asks what feeds it. Another industry asks other questions.
An operator in front of a vessel. The tag says which line and which process step it belongs to, which room it is in, and where the batch record lives.
A machine on the floor. The tag says which production line and process it serves, what sits upstream and downstream, and where the documentation is.
A component in a tunnel, a plant, a network. The tag says which technical system it is part of, where it is, what it is connected to and which systems relate to it.
Anything with an identity and a context can become navigable.
A solvent mixing vessel and its agitator motor. Process knows the vessel. Electrical knows the motor.
Two tags. Two disciplines. One piece of equipment. ContextTAG makes the relationship visible.
The zone comes from the room, the motor from the vessel. Same equipment. Same data. More context. Nameplates, Ex marking and status labels stay where they are.
Scan it. The full name on the foot line is the key to the digital record, and from there everything connected to the object is one step away.
Every line answers a question a person asks in the field. No codes you need a manual for.
What it belongs to, what it does, where it sits, what feeds it. The object in its surroundings, not alone.
Nothing on the tag is typed in. Every line is an answer your data already holds, and a gap on the tag is a gap in the data.
Data fields on ContextTAG are configurable. A cable asks other questions than a switchboard.
The QR takes your phone to the record. From there, everything connected to the object is one step away.
The full name on the foot line is unique. It is the key, on the wall and in the data.
These are the ones we would expect a critical customer to ask.
Because a mobile device introduces a third-party system outside the plant owner’s control, and therefore an additional operational risk. Devices may also be prohibited in classified, controlled or confidential areas. ContextTAG keeps essential information physically available. QR is optional, for deeper context.
ContextTAG cannot determine physical truth, but it can expose missing, conflicting or inconsistent data before they become operational problems. Finding discrepancies during design is far better than discovering them in operation.
From engineering data already created during design. ContextTAG does not require another manually maintained database. It structures and exposes information and relationships that already exist.
A design change identifies the ContextTAGs affected. They are regenerated and replaced as part of change management, helping prevent documentation and the physical plant from drifting apart.
Because essential context should be immediately available at the asset, without a device, network, login or external system. In daily operation, reading is also faster than repeatedly scanning and navigating.
By defining a small set of useful and sufficiently stable relationships for each object type and use case. A motor asks different questions than a vessel or a switchboard. The objective is relevant context, not more information.
No. ContextTAG is designed to use existing identifiers, models and engineering sources. It adds a contextual layer without replacing the systems that created the data.
The model defines which relationships should exist and which combinations make sense. Missing, conflicting or structurally inconsistent information can therefore be flagged before a ContextTAG is approved.
ContextTAG creates potential value throughout the lifecycle: detecting data problems during design, verifying information during handover, and reducing searching and avoidable errors during operation. The earlier it is introduced, the stronger the potential business case.
Not just better signs. ContextTAG turns existing engineering data and relationships into usable context at the physical asset. The tag is where the hidden value in your data becomes visible.
A question we have not answered? Ask it.
ContextTAG is an OntoTeq concept. OntoTeq reveals the structures, relationships and patterns already present in your data. ContextTAG applies that thinking to one of the simplest pieces of information you have: an identifier.
Start with one tag and the data you already have. We’ll show you what it already knows.