botminds.aiRequest a demo
WorkflowEngineering Data, Tags & Documents

Engineering Tag Data Extraction

Tag data extraction that fills each equipment class template from the site's pages, cites every value and tests it against the others before the maintenance system sees it.

See the demoBook a demo
Follow one pump from 25 hp to 125 hp ↓
The problem

A clean reading of a stamped scan still loads a wrong motor size

A maintenance system needs each tag with its class and the values that class requires: flow, head, frame size, trim, set pressure. Those values sit across drawings, datasheets, vendor manuals and nameplates, and P&IDs rarely carry the specifications, so each tag means several documents.

Analysts key them class by class in a spreadsheet, and a second person spot-checks a sample by eye. A misread that looks clean passes. Gaps hide in long lists, so nobody sees that a whole group of motors has no frame size, and the error surfaces years later as the wrong spare.

Built forAsset data analystsMaintenance engineersRotating equipment engineersData stewardsInternal auditors

The Problem Today

Tag values sit across thousands of pages, and a clean reading of a bad scan still loads a wrong number.

4,600
hours to key 277,224 values, at one minute each our estimate
Each
covered process must keep its equipment data, by rule published

Keyed by hand today

  • Drawings
  • Datasheets
  • Manuals
  • Nameplates
  • Misreads look rightA spot check cannot see a digit hidden under a stamp
  • Gaps have no shapeA list hides that one motor group has no frame sizes

The Solution

  1. Read to the templateEach class's required values read from drawings, sheets, manuals and photos
  2. One square per tagA site-wide picture shows gaps by class as a shape, not a count
  3. Tested against each otherFlow, head and gravity must fit the motor; frame must fit power and speed
  4. One cause, many sheetsA stamp in one scan run is offered for a look, sheet by sheet

Built-in controls

  • A second person checks each decided value
  • Agents never write to the maintenance system
  • Classes sign only on an opened sample

What You Get

The maintenance system starts with values you can trace to a page, and people spend their time on the tags that need a judgment.

  • A signed load fileEach changed value names its reason, maker and checker
  • A field list for the restOnly what the equipment itself can show
  • Printed values keptA converted unit keeps the number on the page beside it
One site, one pump

Tag data extraction on an offshore field, and the pump sheet a stamp misread

An offshore field's maintenance system needs 38,470 tags filled to their class templates. The worst sheet is a crude transfer pump's, stamped as built by document control decades ago and scanned years later.

demoField, tags, people and numbers here are all sample data.

  1. 01First look

    38,470 tags as squares, and 31,866 of them ready before a person looks

    Asset data analyst

    Each square is one tag, grouped by class in five columns: instruments, valves, electrical, rotating, static. Bright means every required value is read and cited; dark means a gap. The panel beside it splits the 6,604 that need a person into 5,326 with gaps, 610 that do not add up and 668 hard to read, and names her first job.

  2. 02First look

    Switch the lens to frame size, and the low-voltage motors go dark

    Asset data analyst

    A lens shows one value at a time. On frame size, one block turns dark: 460 low-voltage motors with no frame. A count in a spreadsheet would hide that they are one group with one cause. As a shape, it reads at once as a missing kind of document, and the shape points to where the fix lives.

  3. 03First look

    Frame size is stamped on the nameplate, and the photos do not show it

    Asset data analyst

    Opening the class shows its template of 12 required values with fill bars. Frame size is the one with 460 missing. The note says why: the frame is stamped on the motor's nameplate, the photos on file do not show it, and the datasheets leave the box blank. That is a job for a field list, never for a typical value.

  4. 04The queue

    610 tags read cleanly and still fail a test against their own values

    Agents, for the analyst

    The queue lists every tag whose values disagree with each other, with the rule, the sum and a clock. Pump power must fit the motor, frame must fit power and speed, gravity must fit the fluid. P-4107B sits at the top, two days late: the pump needs 105.9 hp and the motor reads 25 hp.

  5. 05The pump

    Read 96.2% sure, and still wrong: the first digit is under the stamp

    Asset data analyst

    The tag page puts the math beside the sheet. 1,200 gpm at 310 ft and gravity 0.84, at 74.5% efficiency, needs 105.9 hp; the motor reads 25. Two more values back it up: a 444TS frame and 142 A fit a far bigger motor. A typical-size check alone would pass, because 25 hp and 125 hp are both standard.

  6. 06The pump

    Look closer, clean up the scan, and a faint 1 sits under AS BUILT

    Asset data analyst

    She zooms into the power cell and cleans up the scan view; the source file stays unchanged. The document control stamp sits squarely over the first digit, and a faint 1 shows in front of 25. The reading agent was right about what it could see, which is why a person has to look at the page itself.

  7. 07The pump

    She types 125 with her reason, and every test turns green as she types

    Asset data analyst

    The value box takes 125 and the reason, reading error covered by a stamp. The math re-runs at once: power fits the motor, the amps look right, the frame fits, and five more tests pass with the proposed value. Nothing changes in the register yet. Her decision goes to a checker, and she cannot check it herself.

  8. 08The scan run

    One stamp, 18 pump sheets, and one that passes the power check at 50 hp

    Asset data analyst

    The same stamp sits in the same place on one vendor's sheets in that scan run. The run lists all 18 with power as read, the math and the frame. Four fail the power check. P-5108A passes it at 50 hp on a 48.6 hp duty, yet its 445TS frame and its amps do not fit. No bulk correction: 0 of 17 are looked at, and each waits for a person.

  9. 09The check

    Agreed, and 125 hp reaches the first load with both names on its row

    Maintenance engineer, then the data steward

    The checker opens her decision, sees the math and the scan, and agrees. The class was already signed on an opened sample, so the agreed value joins it. In the load file, a search for the pump shows it in Load 1: motor rated power 125 hp, decided by the analyst, checked by the engineer. The dry run comes next.

Five of 18 sheets in one scan run lost a digit under the same stamp

The run's pump sheets where the stamp landed on a three-digit power. Four fail the power check; the fifth fails only on frame and amps.

SheetPower as readPower checkFrame check
P-4107B25 hpNeeds 106 hp444TS is not 25 hp
P-4109A50 hpNeeds 133 hp445TS is not 50 hp
P-4112A25 hpNeeds 109 hp444TS is not 25 hp
P-5103A25 hpNeeds 94 hp444TS is not 25 hp
P-5108A50 hpFits445TS is not 50 hp

demoSample data, from the working solution.

After the pump's value is agreed, the site's 38,470 tags in three piles

How the load file screen splits the site once the checker agrees.

Loaded in the first file, under a class signature12,870
Ready, waiting for their class to be signed18,997
Held for a person6,603
Tags with a class template38,470

demoSample data, from the working solution.

Around the register

Where the gaps should be, the bad scan runs and the master tag list sign-off

What the data steward, the checkers and the auditor open between decisions.

Gaps, by group5,326 tags with 5,836 missing values, grouped by what is missing and where it should be: end connections in the piping class book, frames on nameplates.
Scan runs with one causeSix of 514 scan runs share a problem: a stamp, a cut margin, faded faxes, pen marks, crooked feeds and bleed-through. One cause explains many flags.
Nameplate photos back64 photos of motors with no frame size came back on a field list. Each will be matched to its tag, read, tested, and doubts sent to the analyst.
Units kept as printedMetric values converted to the template's unit with the printed number kept beside them. PN pressure classes are never converted: 250 valves wait for a person.
Sign-off by class23 of 41 classes signed, 4 waiting for a checker. A signature covers the tags ready when given; a held tag joins once two people agree its value.
Audit trailThe pump's morning in order: the agent's flag, the scan cleaned, the decision with its reason, the offer to look at 17 sheets, and the checker's agreement.

demoSample data, from the working solution.

The agents

Eight agents read and test the pages, and none writes to the register

They sort, read, convert and test. People decide, check and sign.

Page sorter

Sorts pages by kind, notes the scan run and holds what it cannot open.

  • Never changes a source file
Tag finder

Finds tags, including old spellings, and matches them to the tag list.

  • Never creates or renames a tag
Attribute reader

Reads each required value with its unit, place and confidence.

  • Never infers a value that is not printed
  • Never takes a value from another tag
Unit converter

Converts to the template's unit and keeps the printed value.

  • Never converts PN to Class
Math checker

Tests values against each other with the class rules and shows the sum.

  • Never changes a value
  • Never marks a tag ready when a rule fails
Scan batch detective

Finds a shared cause in one scan run and offers its sheets.

  • Never corrects in bulk
Gap finder

Finds what is missing, names where it should be and drafts field lists.

  • Leaves a gap open rather than use a typical value
Load file builder

Builds rows from signed classes and runs the dry run.

  • Has no write access to the maintenance system

A changed motor size, a missing frame, a signed class: people decide those

The agents read and test. These calls sit with named people.

Which value is rightThe analyst decides with a reason from the page, and a different person checks before the value changes.
What fills a gapA missing value closes with a document, a field photo or a signed not available, each with its reason.
When a class is signedA checker opens each sampled tag first. A rejection names a value and a reason, and the sample widens.
What the load file carriesThe data steward prepares the load and a second person agrees, after a clean dry run against the template.
A disagreement on rotating equipmentIt goes to the rotating equipment engineer, who can uphold or overturn it, with the record kept.

What asset data teams ask about tag data extraction

What is tag data extraction?

Tag data extraction reads equipment and instrument tags and their attributes off drawings, datasheets, vendor manuals and nameplate photos into class templates for a maintenance system. Here each value cites its place on a page and is tested against the tag's other values before it can load.

Does it build a master tag list?

It works from the tag list the program sets, matches tags on the pages to it, including old spellings, and fills each tag's class template. It never creates or renames a tag; a tag no longer installed goes to a retire list.

Which equipment attributes does it read?

The ones each class template requires: flow, head, frame size, trim, set pressure, materials, ranges and the rest. The data steward owns the templates, and a change to one takes a second signature.

How can a value be wrong if it was read correctly?

A scan can show a clean number that is not the real one, as when a stamp covers a leading digit. The math checker tests values against each other, such as pump power against the motor, so a clean misread fails a rule and goes to a person with the sum shown.

Does every value get a math check?

No. The rules cover the values they can test, on most classes. Values outside any rule are read and cited, not tested, and the screens say which.

What happens to values in metric or other units?

They are converted to the template's unit, and the printed value is kept beside the converted one. Some ratings, such as PN pressure classes, are never converted and wait for a person.

Is functional location data part of the load?

The load carries tagged equipment and instruments with a class template. Locations, lines and items with no data template stay outside this work.

Engineering Data, Tags & Documents

More for tags, registers and equipment data

All 11 solutions →
Engineering Records Classification and Deduplication

The signed copy crowned, and every look-alike explained.

1-min demoP&ID Digitization

Plain questions for engineers, and every line followed from sheet to sheet.

1-min demoEquipment Datasheet Extraction

Only the lines that matter kept, each one marked meets, differs or missing.

1-min demo

Send us one class
and the pages behind it.

Low-voltage motors work well: we’ll read them to your template and show which values fail the math.

Book a demoBrowse solutions