Does Tagsight require access to the source engineering database?

No. The input is the drawing (PDF, scan, or image). The system does not connect to or depend on a project database. Drawings can come from a current modeling environment, an archived export, or a scan of a printed copy.

How does this fit during a system transition?

A common pattern is to use Tagsight for the document side (I/O list, equipment list, line list, MOC change reports) while the project model continues for diagram authoring. Teams that retire the model later still have all extracted data in standard formats.

What tag conventions are supported?

ISA 5.1, KKS, IEC 81346, NORSOK, JIS, GOST, and in-house conventions are all read directly from the drawing. The tool does not require the convention to be configured in advance; it reads what is on the page.

Can we still produce DEXPI?

Yes. DEXPI XML is one of the standard exports. The reviewed extraction generates DEXPI 1.3 output for downstream interchange.

How are control loops represented?

Loop numbers are inferred from the tag set per drawing and surfaced in the I/O list. Instruments are grouped by loop, equipment, and line, so loop-level checks are available in the review interface and in the Excel export.

What about scanned drawings that never made it into the model?

They are supported the same way. Scanned PDFs and image inputs are supported.

Moving off AVEVA P&ID Diagrams into structured tag data.

Read PDFs and scans directly. Produce the I/O list, equipment list, and line list without a shared engineering database in the middle.

SourcePDF · scan · image · vector PDFCutoverParallel-run, no lock-in

Start a workspace See the comparison

Two workflows, six decisions.

Where the AVEVA workflow concentrates engineering effort, and where the Tagsight workflow concentrates it instead.

AVEVA P&ID Diagrams

Tagsight

Source format

Engineering database tied to AVEVA P&ID Diagrams; license-bound access to the diagram authoring environment.

The drawing itself: PDF, scan, or image. No engineering database and no per-seat license required to read it.

Tag convention

Configured in the project database; new conventions or in-house codes require schema edits.

Read directly from the drawing. ISA 5.1, KKS, IEC 81346, NORSOK, JIS, GOST, or any in-house code, no configuration step.

Revisions

Managed through versioned project models and the authoring tool; change reports generated from the model database.

Upload two PDFs, run Revision Comparison, export an Excel Change Report with added / removed / modified instruments.

Version compatibility

Backward and forward compatibility tied to AVEVA release versions and project-database schema.

Drawing-only input. PDFs from any AVEVA version, scans of any vintage, all supported as inputs.

Export formats

Vendor-native schemas plus selected interchange formats; export configuration maintained per project.

TIA Portal XML, Studio 5000 L5X, PLCCreator CSV, DEXPI XML, Excel, CSV, JSON, annotated PDF. All available on every project.

Legacy drawings

Often live outside the model entirely; bringing them in requires re-authoring time.

Supported the same way. Scanned, photographed, or vector PDF, all supported.

Teams typically start by routing the document side through Tagsight while the AVEVA environment continues to host diagram authoring. The I/O list, equipment list, line list, and Change Reports come out of Tagsight; the diagrams themselves stay where they are. The two workflows run in parallel as long as the team wants.

When the team is ready to retire the model entirely, every extracted document is already in standard formats (Excel, TIA Portal XML, Studio 5000 L5X, PLCCreator CSV, DEXPI XML). There is no migration cliff: no engineering database to export, no per-seat license to extend through a long transition.

Legacy drawings outside the model run through the same pipeline. Scans from the EDMS produce the same documents as the vector PDF exports.

Moving off AVEVA P&ID Diagrams into structured tag data.

Read PDFs and scans directly. Produce the I/O list, equipment list, and line list without a shared engineering database in the middle.

SourcePDF · scan · image · vector PDFCutoverParallel-run, no lock-in

Start a workspace See the comparison

Two workflows, six decisions.

Where the AVEVA workflow concentrates engineering effort, and where the Tagsight workflow concentrates it instead.

AVEVA P&ID Diagrams

Tagsight

Source format

Engineering database tied to AVEVA P&ID Diagrams; license-bound access to the diagram authoring environment.

The drawing itself: PDF, scan, or image. No engineering database and no per-seat license required to read it.

Tag convention

Configured in the project database; new conventions or in-house codes require schema edits.

Read directly from the drawing. ISA 5.1, KKS, IEC 81346, NORSOK, JIS, GOST, or any in-house code, no configuration step.

Revisions

Managed through versioned project models and the authoring tool; change reports generated from the model database.

Upload two PDFs, run Revision Comparison, export an Excel Change Report with added / removed / modified instruments.

Version compatibility

Backward and forward compatibility tied to AVEVA release versions and project-database schema.

Drawing-only input. PDFs from any AVEVA version, scans of any vintage, all supported as inputs.

Export formats

Vendor-native schemas plus selected interchange formats; export configuration maintained per project.

TIA Portal XML, Studio 5000 L5X, PLCCreator CSV, DEXPI XML, Excel, CSV, JSON, annotated PDF. All available on every project.

Legacy drawings

Often live outside the model entirely; bringing them in requires re-authoring time.

Supported the same way. Scanned, photographed, or vector PDF, all supported.

Legacy drawings outside the model run through the same pipeline. Scans from the EDMS produce the same documents as the vector PDF exports.

Moving off AVEVA P&ID Diagrams into structured tag data.

Two workflows, six decisions.

Tell us about your project

Moving off AVEVA P&ID Diagrams into structured tag data.

Two workflows, six decisions.

Tell us about your project