I/O list to DEXPI.

Convert a Tagsight I/O list into a DEXPI 1.3 XML payload. Every instrument, every loop, every equipment item is emitted as an ISO 15926-aligned entity ready for handover to a downstream digital-thread or asset-information system.

Upload a drawing Pricing

What the DEXPI export carries.

DEXPI (Data Exchange in the Process Industry) is an open ISO 15926-aligned format for exchanging process-engineering data between authoring tools and operations / digital-thread systems. Tagsight emits DEXPI 1.3.

From I/O list to digital thread.

01UploadI/O list
02BuildAsset hierarchy
03EmitDEXPI XML
04Hand offTo downstream system

How the columns map.

Every I/O list column has a DEXPI entity destination. Auto-mapped fields carry signal-class codes directly; derived fields build structural relationships such as loop membership and equipment attachment.

I/O list column	Target field	Notes
Tag	Instrument.tagName string	auto Carried verbatim.
Service description	Instrument.serviceDescription string	preserved Free-text service description.
Loop	ControlLoop.id integer	derived Each unique loop number generates a ControlLoop entity with the constituent instruments referenced.
Signal class	Instrument.signalClass enum	auto AI/AO/DI/DO carried as ISA 5.1 signal-class codes.
Sub-class	Instrument.functionalClass enum	auto BPCS or SIS.
Range / units	Instrument.measurementRange structured	preserved Range emitted as a Quantity with low, high, and unit subfields.
Set point / Trip	ControlLoop.setPoint / Instrument.tripValue number	optional Carried when specified.
Linked equipment	Instrument.attachedTo reference	auto Equipment reference from the same DEXPI payload.
Notes / revisions	Instrument.notes string	preserved Free-text annotation.

Other targets.

DEXPI.xmlISO 15926-aligned payload for asset-information systems TIA Portal.xmlGlobalDB block and PLC tag-table CSV for S7-1200 and S7-1500 Studio 5000.L5XLogix5000 controller tag file for ControlLogix and CompactLogix PLCCreator.csvDevice IO List CSV for PLCCreator project scaffolding Excel.xlsxI/O list, equipment list, and line list on linked sheets

Common questions

What is DEXPI?

What entities are included in the export?

Instruments, equipment, lines, control loops, and asset-hierarchy nodes. Connections between them are emitted as DEXPI relationships.

Is the schema strict or lenient?

Strict. The export validates against the DEXPI 1.3 XSD before download. Validation errors are surfaced in the workspace so the I/O list can be corrected before export.

Can the DEXPI payload be re-imported into Tagsight?

Yes. Uploading a DEXPI XML reconstructs the I/O list, equipment list, and line list as if extracted from the source drawings.

Which downstream systems consume DEXPI?

Hexagon SDx, AVEVA Asset Information Management, Bentley OpenPlant ModelServer, and several Owner-Operator information-management systems. Most modern asset-data platforms can ingest DEXPI 1.3.

Are revisions tracked in the DEXPI payload?

Each entity carries a revision attribute matching the I/O list row revision. Diffing two DEXPI payloads is the way Tagsight supports the Revision Comparison workflow for asset-information systems.

Bring it into your project.

Upload an I/O list or a P&ID set, review the rows, export a DEXPI 1.3 XML payload ready for handover to your asset-information system.

Upload a drawing See pricing