SystemEngineering Data, Tags & Documents

Asset Tag Management

Asset tag management for plant equipment tags, comparing each tag across five records, explaining why they differ, and loading a fix only after a check and a dry run.

See the demo Book a demo

Follow one control valve from passport to load ↓

The problem

A master tag register where five records describe one valve differently

One control valve lives on a drawing, a datasheet, an instrument index, the maintenance system and an inspection record. Each was right when someone typed it. A rerate updates the drawing and stops there, and the maintenance system keeps the startup value for years.

Nothing in daily work shows the gap until it does work. An inspection works out minimum wall from the old pressure, a relief valve on a drawing has no test plan because it has no record, and a work order goes out for a pump that was taken out long ago.

Built forAsset data ownersInstrument engineersReliability engineersMaintenance systems administratorsInternal auditors

The Problem Today

One plant tag lives in drawings, datasheets and the maintenance system, and they disagree, so nobody trusts it.

50,000: maintainable items on a typical offshore installation published
9,432: hours to settle the sample plant's tags by hand, 45 minutes each our estimate

Five records, read by eye

Drawings
Datasheets
Maintenance
Inspection

One tag, two namesFailure history splits across old and new names
Old values do real workWall limits set from a pressure before a rerate

The Solution

All five sources matchedEach equipment, instrument and line tag tied across each record
Disagreements explainedEach value cited, why it differs, and which one looks right
Missing and ghosts caughtReal tags with no record, and records with nothing behind them
Checked, then loadedAn engineer picks, someone else checks, a dry run comes before the load

Built-in controls

Nobody checks the value they picked
Only the administrator loads, after a check
A dry run comes before every load

What You Get

Maintenance and inspection plan from values that match the approved design, with the reason on record.

One tag, one checked recordEach value with its source and the person who picked it
Ghosts and missing tags foundEach with evidence and a proposed fix
Loads you can reverseA file to undo each load is kept

One valve, five records

Asset tag management on 420-PV-1138, a valve with three design pressures

A gas plant with 64,218 tags across nine units. In the dehydration unit, a pressure control valve carries three different design pressures in three records.

demoThe gas plant, its tags, its records and its people are sample data.

01Morning
64,218 tags; 51,642 agree in each source that holds them
Asset data owner
The plant is drawn as its units, gas in on the left and sales gas out on the right, each showing its count of tags that agree and those waiting on a person. The tree beside it lists equipment, instruments and lines. A tag is reached from the plant and its unit, so people find it the way they talk about it.
02Morning
Unit 420 has 1,532 tags to settle, and one cause explains many
Asset data owner
The dehydration unit's main tags are drawn on their process line, each colored by whether its records agree. The agents' summary for the unit lists conflicts, missing and ghost tags and names that break the standard, and points out that one approved rerate explains 147 of them.
03Morning
The passport shows 1,300, 1,480 and 1,150 psig for one valve
Asset data owner
A tag passport lines the five sources up attribute by attribute. On the drawing, an approved rerate gives 1,300 psig; on the datasheet, 1,480; in the maintenance system, 1,150 from startup. Below them sits what is at stake: a thickness survey works out minimum wall from the maintenance system value.
04Morning
The datasheet's 1,480 psig is the valve body rating, typed in the wrong box
Asset data owner
Each value opens to its page. On the datasheet, 1,480 psig sits in the design pressure box, and the cause explainer reads it as the valve body's Class 600 rating at 100 °F rather than a design value. It proposes 1,300 psig, 91% sure, and says that only the instrument engineer picks.
0509:14
He picks 1,300 psig and writes his reason; nothing is prefilled
Instrument engineer
The pick dialog lists the three values with their sources, then asks for a reason and a note for the checker in his own words. He ties it to the approved change and the drawing note. Two simpler items on the same tag, a serial and a fail position, settle with it if he ticks the box.
0609:16
A change request goes to the data owner, and he cannot check it
Instrument engineer
The passport now shows his pick and the reason, with each affected row marked in check. CR-20418 carries the sources it relied on. The screen tells him plainly that he proposed this, so someone else must check it.
0709:18
Checked, and still nothing in the maintenance system has changed
Asset data owner
With the pick, his reason and the five sources on her screen, the data owner checks the change. It joins the next load. The maintenance system changes only after a dry run and the administrator's approval, so a checked value is still a proposal until then.
0809:20
The dry run shows 175 clean and 3 held, before anything is written
Maintenance systems administrator
Batch LB-0931 holds 178 records: value changes, new records, retired ghost records and this valve. The dry run tries each against the maintenance system and holds three: two locked by open work orders, one by an inspection in progress. Nothing has been written yet.
0909:22
Loaded: 175 records, 3 held, a receipt and a file to reverse it
Maintenance systems administrator
She approves the load. The batch reads 175 loaded, 3 held, with receipt R-88240, and a file to reverse the load is kept for 90 days. The datasheet still says 1,480 psig, so the valve counts as settled with a document revision open until the corrected datasheet arrives.

Three design pressures for 420-PV-1138, and where each came from

Each value is cited to its page; the reason it differs is the cause explainer's reading, checked by people.

Source	Value	Why it says so
Drawing, Rev 7, Note 4	1,300 psig	Follows the approved rerate
Datasheet, Rev B	1,480 psig	Body rating for Class 600, typed in the design pressure box
Maintenance system	1,150 psig	Loaded at startup and never updated after the rerate

demoSample data, from the working solution. A thickness survey that works out minimum wall from 1,150 psig can pass metal that 1,300 psig would not.

Around the register

Ghosts, missing tags and causes across the master tag register

The screens the data owner, the reliability engineer and the field technician work through after one valve is settled.

Data quality by plant unit: share of tags that agree, weeks of settling, and which record was most often out of step — **Data quality**Each unit's share of tags that agree, twelve weeks of settling, and which source was out of step. Most fixes land in the maintenance system.

Ghost assets in the maintenance system and missing tags, each with evidence from drawings and the field, and a proposed fix — **Missing and ghost tags**Missing tags are real equipment with no maintenance record, so no work gets planned on them. Ghosts are records whose equipment is gone. Each has evidence and a proposed fix.

Tag conflicts grouped by cause, with the rule the agents propose and example tags for each cause — **Conflicts by cause**Disagreements grouped by why they happened, such as a change that never reached the maintenance system, so a person settles a cause instead of cell by cell.

Field walks by plant area to check suspected ghost and missing tags, with stops and the question asked at each — **Field walks**Doubtful tags grouped into walks by plant area so nobody crosses the plant twice. Only the technician answers what is actually there.

Audit trail of tag decisions: the agents' reads, the engineer's pick, the check, the dry run and the load — **Audit trail**Every read, proposal, pick, check and load, by people and agents, in order. Nothing on it can be altered, and the auditor sees the whole of it.

Overnight agent run over plant records, with what each agent read and found, its confidence, and who it handed to — **The overnight run**What each agent read, found, how sure it was and who it handed to, including the drawing sheets too faint to read that went to a person.

demoSample data, from the working solution.

Who matches the records

Seven agents tie each tag across its records, and none of them loads a value

They find, compare and explain. People pick and load.

Tag finder

Finds each tag on drawings, datasheets and records, with its spot on the page.

Never creates a tag in any system

Source matcher

Ties one tag across five sources, including misspelled and old names.

Never merges two names without showing both

Value comparer

Compares each value, converts units, and marks agree, disagree or missing.

Never picks a winner

Cause explainer

Traces why values differ, proposes one, and says how sure it is.

Never decides
Says no clear cause rather than guess

Naming checker

Tests each name against the customer's own standard.

Never renames a tag with an open work order

Missing and ghost checker

Looks both ways and proposes create, rename, retire or a field check.

Never retires a record

Change writer

Writes the change request and load file with evidence.

Cannot write into any plant system

What a tag decision needs from people

The agents prepare it. These steps belong to named roles.

The engineer picks the valueNothing is prefilled. A value that goes against an approved change cannot pass a check without a new change record.

Someone else checks itThe person who picked a value cannot check it.

The administrator approves the loadOnly after a dry run shows what would fail, with a file kept to reverse it.

Only the field says a tag is goneA record is called a ghost only with a change record or a field check behind it.

Questions plant data owners bring to asset tag management

What is asset tag management here?

Here, asset tag management means plant equipment tags, not IT labels. Each equipment, instrument and line tag is compared across drawings, datasheets, the instrument index, the maintenance system and inspection records, each value cited to its page and each difference explained.

How does it handle P&ID to CMMS reconciliation?

It reads the drawings and the maintenance system for each tag, compares the values, and proposes a fix with the cause. An engineer picks, a second person checks, and the administrator loads after a dry run.

What are ghost and missing tags?

Missing tags are real equipment on a drawing or in the field with no maintenance record, so nobody plans work on them. Ghosts are maintenance records with nothing behind them. Both come with evidence and a proposed fix.

Does it rename tags to our numbering standard?

It tests each name against the standard you load and proposes renames. A rename keeps the work history, and a tag with an open work order is not renamed.

Can a load be undone?

Yes. Each load keeps a file to reverse it, and a reversal has its own check.

Is this engineering tag management for new projects too?

It works on an operating plant's records. New tags from projects are checked against the same five sources before they reach the maintenance system.

Engineering Data, Tags & Documents

Choose one process unit
and send us its tags.

We will build a passport for each tag and show where the records part ways.

Book a demo Browse solutions

Asset Tag Management

A master tag register where five records describe one valve differently

The Problem Today

The Solution

What You Get

Asset tag management on 420-PV-1138, a valve with three design pressures

64,218 tags; 51,642 agree in each source that holds them

Unit 420 has 1,532 tags to settle, and one cause explains many

The passport shows 1,300, 1,480 and 1,150 psig for one valve

The datasheet's 1,480 psig is the valve body rating, typed in the wrong box

He picks 1,300 psig and writes his reason; nothing is prefilled

A change request goes to the data owner, and he cannot check it

Checked, and still nothing in the maintenance system has changed

The dry run shows 175 clean and 3 held, before anything is written

Loaded: 175 records, 3 held, a receipt and a file to reverse it