Tagsight for mechanical engineers
The vendor datasheet binder lands at 240 pages: pumps, exchangers, vessels, blowers, agitators. Each datasheet is a different vendor's form, each carries a different field order, and the master equipment list is the document that needs to reconcile them into one row per tag with the right metadata in the right column.
What you do today.
- Open each vendor datasheet PDF and transcribe tag, service, duty, materials, vendor model into the master equipment list
- Cross-walk rotating-equipment tags against the P&ID set to confirm scope and tag numbering
- Maintain a parallel spreadsheet of heat-exchanger thermal-rating sheets, often in a separate file from the master register
- Reconcile the binder against the P&ID set every revision cycle when scope adds or drops equipment
What changes with Tagsight.
- Upload the vendor datasheet binder, get a master equipment list with one row per tag and vendor data placed in the right columns
- Cross-reference the binder against the P&ID equipment scope; surface tags on the P&ID with no datasheet and datasheets with no P&ID parent
- Pull the heat-exchanger thermal data, the API 610 pump curves, and the API 617 compressor performance map metadata onto the same equipment row
- Maintain the per-tag datasheet linkage so the next person opening the equipment list can jump to the source datasheet PDF
- Export the equipment list in the column shape commissioning, maintenance, or the asset register expects
Where it fits in your week.
Bid-stage equipment scope reconciliation
RFQ arrives with a P&ID set, a vendor binder, and a 12-row 'preliminary equipment list'. Run the binder and the P&IDs through extraction, surface where the three documents disagree, fix the count before the bid number locks.
API 610 / 617 / 660 datasheet pull
Rotating equipment review needs every API-form datasheet rolled into a comparison table. Pull the binder through extraction, surface duty, NPSH, materials, and seal-system metadata per tag, hand the comparison to the rotating-equipment specialist.
Asset-register handover
End-of-job equipment list ships to the owner's maintenance system. Extract once, export in the column shape the maintenance system imports, skip the transcription step that usually owns the last week of the job.
FAQ.
Does this handle vendor-specific datasheet form layouts (Flowserve, John Crane, Sulzer)?
Yes. Vendor-specific datasheet forms read as drawn. The extractor maps every detected field into the canonical equipment-list column schema; vendor-specific notation is preserved in the source-form column so the original is still there if the canonical mapping is ambiguous.
Can it produce a comparison table across multiple vendors bidding the same equipment?
Yes. Run each vendor's datasheet binder as a separate workspace, then export a side-by-side comparison on key duty fields. The comparison surfaces where vendors interpreted the duty spec differently, which is usually the part that matters.