DeltaV IO lists: columns SchematicForge actually reads

What we need from the sheet

A DeltaV I/O export is usable if it has an instrument tag and a signal type (AI, AO, DI, DO, or named types such as XV). Controller, card, and channel columns fill the I/O allocation appendix and the loop sheet; they are not required to parse.

SchematicForge does not emit DeltaV function-block diagrams or plant-standard Dynamos. Output is loop diagrams, registers, and schedules from the same IO-list rows.

Typical columns to keep

Keep tag, description, I/O type, controller or node, card or module, and channel. Rename headers if they are long; the importer fuzzy-matches and you can correct the mapping before generate.

One signal per row. Two rows with the same tag become one loop with two signals — the usual case for a valve with AO plus limit switches.

What to check in the free preview

Upload the vendor file on the homepage with no account. Confirm the tag column, loop count, and signal count. Cover sheets are skipped when an IO worksheet is present.

Free download after signup is a watermarked PDF of the first 15 field-wired loops. A pack issues the full set as clean PDF and native DXF.

Typical DeltaV header synonyms

Instrument Tag / Device Tag / Tag Name map to Tag. I/O Type / Signal / Channel Type map to Signal Type. Controller, Node, or DST land on Controller Node. Card, Module, or CIOC land on Card Type / Slot. Channel or Point land on Channel.

Keep one signal per row. A control valve with AO plus two DI limits is three rows, one tag. SchematicForge does not read a DeltaV .fhx or export a DeltaV project.

Frequently asked questions