TagIQ · business overview
A tag register is not documentation — it is the document that gates commissioning and, on most contracts, payment. Everyone already knows theirs does not meet its own naming standard. The reason it never gets fixed is that renaming tags breaks every drawing, datasheet and maintenance reference pointing at the old names, so it is rational for the team not to touch it.
TagIQ renames the register to the standard while every old reference still resolves, fills the gaps with an engineer approving each change, and hands the result to the systems that operate the plant. One working session rather than one quarter — and nothing on either side of it is replaced. It ‘just’ gets better.
Measured live in the recorded demo against an eight-unit gas plant, not modelled — the same run the presenter script quotes. Your register will produce its own numbers.
Read the arrows, not the boxes. The systems on either side are the customer's existing investment, and they are the same after as before.
The objection is never "does it work". It is "so we are replacing something, and who owns the data now?" — followed, once that is settled, by whichever version of the question fits the situation the buyer is actually in.
| Question | Answer |
|---|---|
| Does it write back into our design system? | No. The issued package is pulled and read. Nothing goes back up that arrow. |
| So it becomes the new master? | No. It holds the register for the handover window — the interval where the data is between two owners and today belongs to nobody. |
| What happens to our tag numbers? | Renaming keeps the source identifier as an alias, so every drawing, purchase order and SAP reference that already exists still resolves. |
| Who decides what is correct? | For handover, the receiving system does. TagIQ submits per record and logs SAP's own accept-or-refuse reason. It does not grade its own homework. |
| What if the AI gets it wrong? | Every change names who proposed it and who approved it, and any run can be taken back field by field. |
| What do we have to switch off? | Nothing. Both ends keep doing what they do. The manual checking step in the middle is what changes. |
| Our plant is running — there is no project. Does this still apply? | That is the more common case. The register is read out of the system that already holds it, measured, corrected and augmented, and the richer version goes back to the same system. No handover required. |
| We have several contractors. Will they see each other's data? | No. Each package sits in its own project boundary, enforced where the data is read rather than requested politely — a query that does not name one project is refused. What crosses the boundary is the score and the named gaps, which is what the owner is entitled to and nothing more. |
| Can we try it without connecting it to anything? | Yes, and it is usually the right first step. One extract in, a read-only assessment out: how far the register is from the standard it claims to follow, and what remediation actually consists of. Nothing is configured to receive, so nothing can be written. |
| What if we have no engineering register — tags start life in a spreadsheet? | Then TagIQ can be where they start instead. Numbers are issued from the class's own convention and a project counter rather than typed, and the same rulebook that grades a contractor's package grades yours. What that replaces is the spreadsheet, not a system. |
| If you hold our register, are we locked in? | It leaves whole, in open formats — CSV, Excel, JSON, a printable register — or per record into a receiving system. Holding the data for a project is a service, not a hostage position, and you are right to ask which one it is. |
| Is this only useful at handover? | No. Handover is where the pain is sharpest and easiest to price, which is why the demo runs it. The cases above are illustrations rather than a catalogue — the same checking step is worth having anywhere a register has to be trusted by someone who did not build it. |
When presenting this, point at what stays before pointing at what is new. The boxes on the left and right are the customer's existing investment, and they are the same after as before.
The handover case above is the one the demo runs. It is not the only one, and these are not a menu — what changes between them is only where the data comes from and who it goes back to. Anywhere a register crosses a boundary, or has to be trusted by someone who did not create it, is a candidate.
No project, no handover. The register already lives in the owner's asset information system and has decayed for fifteen years. TagIQ reads it, measures it, corrects and augments what can be inferred, and delivers the richer dataset back to the same system it came from.
Three contractors deliver three packages in three house styles, each one arguing its data is fine. Each package lands as its own project, and every one is measured against the same conventions, the same required documents and the same standards audit — so the packages become comparable even though the contractors are not.
The lowest-commitment version, and often the right first conversation. A copy of the register goes in and nothing comes out except a verdict: how far it is from the standard it claims to follow, which safety-critical items carry gaps, and what the remediation actually consists of.
A modification delivers a few hundred new tags into a plant that is running. The hard part is never the new tags; it is knowing which of them are genuinely new, which restate something the register already has under a different name, and which contradict it.
The cases above all preserve something that already exists. This one is different: there is no upstream register to protect, because the tags do not exist yet. They are created in TagIQ, numbered by the project's own convention, reviewed by name, and handed to the systems that will operate the plant. What this replaces is not a system — it is the spreadsheet.
It sits inside the middle box in every shape above. What makes it usable near master data is not how clever it is — it is how little it is allowed to do without being told.
And the boundary it cannot talk its way past: the agent can only see the project it is working in. That is enforced where the data is read, not asked for in its instructions — a question about another project's register comes back refused, however it is phrased.
These are not separate products. The differences are entirely in the wiring at each end; the core concepts in the middle are the same every time.
These are not separate products. The differences above are entirely in the wiring at each end; the core concepts in the middle are the same every time, and they are what makes any of it acceptable near master data.