ISA-5.1 loop diagrams: what the standard asks for
By Saad, practising automation engineer · Updated 2026-09-25
A practical reading of ISA-5.1 identification and typical loop-sheet content — tags, function letters, and the path from field to I/O — without treating generated drawings as a certified deliverable.
What ISA-5.1 is (and is not)
ISA-5.1 is the instrumentation identification standard most plants still use for tags: a measured variable letter (P, T, F, L) plus a function (T transmitter, V valve, S switch) and a loop number. It is not a drawing-format standard and it is not a SIL/IEC 61511 certificate.
SchematicForge uses those tags as the loop key. Generated sheets are drafting aids for review; engineer approval is still required.
What a loop sheet usually shows
A typical issued loop diagram shows one tag from field device through junction box and marshalling to the controller channel, with cable IDs, terminals, and I/O type on the path.
Multi-signal loops (a control valve with AO plus DI limits) stay one tag with several signals — the same model SchematicForge uses when two IO-list rows share a tag.
From spreadsheet to sheet
If the IO list already carries tag, signal type, and destinations, the drawing can be generated instead of traced in CAD. Edit the Loop Register and regenerate only the loops that changed.
Use the free IO-list checker to see whether your vendor file already has a tag column the importer can read.
Frequently asked questions
Does SchematicForge certify ISA-5.1 compliance?
No. Output is a drafting aid. Tag letters and loop numbers follow the identification you supply; review against your project standard remains the engineer's job.
Where do function letters come from?
From the instrument tag and signal type on the IO list. The generator does not invent a new tagging scheme.