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.
No migration cliff.
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.
How the transition runs.
- 01Parallel routingTeams typically start by routing the document side through Tagsight while the AVEVA environment continues to host diagram authoring.
- 02Retire the modelWhen the team is ready to retire the model entirely, every extracted document is already in standard formats.
- 03Legacy backfillLegacy drawings outside the model run through the same pipeline.
Read directly from the drawing.
The drawing itself: PDF, scan, or image. No engineering database and no per-seat license required to read it.
ISA 5.1, KKS, IEC 81346, NORSOK, JIS, GOST, or any in-house code, no configuration step.
Drawing-only input.
Upload two PDFs, run Revision Comparison, export an Excel Change Report with added / removed / modified instruments.
PDFs from any AVEVA version, scans of any vintage, all supported as inputs.
- TIA Portal XML, Studio 5000 L5X, PLCCreator CSV, DEXPI XML, Excel, CSV, JSON. All available on every project.
- Supported the same way. Scanned, photographed, or vector PDF, all supported.
Two workflows, six decisions.
Where the AVEVA workflow concentrates engineering effort, and where the Tagsight workflow concentrates it instead.
| Topic | 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. 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. |
Common questions
Does Tagsight require access to the source engineering database?
How does this fit during a system transition?
What tag conventions are supported?
Can we still produce DEXPI?
How are control loops represented?
What about scanned drawings that never made it into the model?
Move off AVEVA P&ID Diagrams.
Read PDFs and scans directly. Produce the I/O list, equipment list, and line list without a shared engineering database in the middle.