Translate instrument tags between engineering standards on a multi-region project.

International EPC projects routinely produce documents in two or three engineering standards at once. ISA 5.1 in the basis of design, DIN or KKS in the owner manual, NORSOK on the topsides scope. Reconciling them across the as-built register is one of the most thankless jobs on the project.

Start a workspace See pricing

Workflow.

01
Identify the source and target standards
The standards translator works between any two supported standards with a published letter-code mapping. Pick the source dialect, the way the drawing reads and the target dialect, the way the document should ship.
02
Translate tag-by-tag or apply at workspace level
For a single tag, the standards translator returns a candidate target tag plus per-component translations, letter code, signal class, equipment family and a structurally-different note when the standards do not share an identifier shape. For a workspace, the translation runs across every extracted tag in one pass.
03
Export with both dialects
The export Excel ships with the original tag in the source dialect, the translated tag in the target dialect, and a translation-note column that flags every tag where the two dialects disagree on signal class or function.

What you get.

Per-tag translation between any two supported standards
Workspace-wide translation pass with bilingual or trilingual export
Translation note per tag identifying structural differences between the two dialects
Letter-code reference table for the source and target standards alongside the export

FAQ.

01Which standards are supported.
ISA 5.1, DIN 19227, IEC 81346, KKS, NORSOK I-001 and I-005, JIS Z 8204, KS A 0610, GB, T 50001, GOST 21.404, IEC 60617, operator standards, Aramco SAES, ADNOC AGES, Equinor TR, Shell DEP, BP RP, Petrobras N, and vertical-specific standards, datacenter telecom, building automation Brick, Haystack, semiconductor SEMI, pharma ISPE GAMP. The full list lives at, standards.
02What if my project uses an in-house standard not in the supported list.
Published standards translate directly. For in-house dialects, the export preserves the original tags alongside whichever published target dialect you select, so the in-house convention stays intact and a translation-note column flags the components that have no published equivalent.

Related

IndustryLNG IndustryPetrochemicals ConvertP&ID to instrument index

Translate instrument tags between engineering standards on a multi-region project.

Workflow.

Identify the source and target standards

The standards translator works between any two supported standards with a published letter-code mapping. Pick the source dialect, the way the drawing reads and the target dialect, the way the document should ship.

Translate tag-by-tag or apply at workspace level

For a single tag, the standards translator returns a candidate target tag plus per-component translations, letter code, signal class, equipment family and a structurally-different note when the standards do not share an identifier shape. For a workspace, the translation runs across every extracted tag in one pass.

Export with both dialects

The export Excel ships with the original tag in the source dialect, the translated tag in the target dialect, and a translation-note column that flags every tag where the two dialects disagree on signal class or function.

FAQ.

01Which standards are supported.

ISA 5.1, DIN 19227, IEC 81346, KKS, NORSOK I-001 and I-005, JIS Z 8204, KS A 0610, GB, T 50001, GOST 21.404, IEC 60617, operator standards, Aramco SAES, ADNOC AGES, Equinor TR, Shell DEP, BP RP, Petrobras N, and vertical-specific standards, datacenter telecom, building automation Brick, Haystack, semiconductor SEMI, pharma ISPE GAMP. The full list lives at, standards.

02What if my project uses an in-house standard not in the supported list.

Published standards translate directly. For in-house dialects, the export preserves the original tags alongside whichever published target dialect you select, so the in-house convention stays intact and a translation-note column flags the components that have no published equivalent.