Loop Diagrams vs P&IDs. When to Use Which.
The practical difference between a P&ID and a loop diagram, what each document is authoritative for, and why mixing them up causes rework during commissioning.
A process engineer needs to know what the plant does. A commissioning technician needs to know where every wire goes. Those two needs produce two different documents, each authoritative for different questions. Mixing up which one to check, or trying to make one document do both jobs, is a classic cause of commissioning-stage rework.
The P&ID
The Piping and Instrumentation Diagram sits at plant or unit scale. It shows.
- Process equipment. Pumps, vessels, tanks, exchangers, reactors, compressors
- Piping. Lines with size, spec, service, from, to
- Instruments. Every bubble with its ISA 5.1 tag
- Utilities and tie-ins
- Control loops at a high level. Transmitter, controller, valve
- SIS vs BPCS separation where relevant
- Off-page connectors for flows that cross drawing boundaries
Governed by ISA 5.1 for instrument symbology and a project-specific legend for the rest.
**What a P&ID is authoritative for. ** what exists in the plant. If an instrument is on the P&ID, it should exist, or be designed to exist. If it is not, it should not.
**What a P&ID is not authoritative for. ** how anything is wired. The bubble for FIT-101 does not tell you which terminal block it lands on, which cable pair carries its signal, or which PLC card and channel it reads. That detail lives in the loop diagram.
The loop diagram
The loop diagram sits at signal-path scale. It shows one control loop from field device to control system, fully annotated.
- Field device. Transmitter tag, manufacturer, model, calibration range
- Field wiring. Cable tag, pair number, gauge, routing
- Terminal boxes and junction boxes. Terminal number at each transition
- Power supply and barrier routing, for intrinsically safe installations
- Cabinet termination. Marshalling panel position, PLC rack, slot, channel
- Control system tag. The PLC program tag matched to the field instrument
- HMI or SCADA tag reference
Governed by ISA 5.4. Each sheet shows one loop, or one closely related set of loops sharing cabling.
**What a loop diagram is authoritative for. ** the wired path. During commissioning, when a loop check does not pass, the loop diagram is the document opened first. It carries every termination, every cable tag, every barrier, every marshalling strip.
**What a loop diagram is not authoritative for. ** process intent. It does not show what the loop controls at the process level, only that it exists and how it is wired.
Deep comparison. Scope and audience
| Dimension | P&ID | Loop diagram |
|---|---|---|
| Governing standard | ISA 5.1 | ISA 5.4 |
| Scale | Plant or unit | Single loop or signal path |
| Primary audience | Process engineers, safety engineers, project managers | Commissioning technicians, maintenance engineers, electrical designers |
| Shows process equipment | Yes | Rarely, instrument connection only |
| Shows instrument tags | Yes | Yes |
| Shows signal class | Yes, from tag letters | Yes, confirmed by card type |
| Shows terminal numbers | No | Yes, at every transition |
| Shows cable tags | No | Yes |
| Shows junction box detail | No | Yes, with terminal strip layout |
| Shows PLC rack, slot, channel | No | Yes |
| Shows calibration range | Sometimes | Yes |
| Shows barrier or isolator type | No | Yes |
| Shows SIS classification | Yes | Yes |
| Used during HAZOP | Yes | No |
| Used during loop check | Rarely | Yes, the primary document |
| Revised when process changes | Yes | Sometimes |
| Revised when hardware changes | Rarely | Yes |
How a single P&ID loop maps to one loop diagram
Consider a simple temperature control loop on a distillation column.
- P&ID shows. TT-312, temperature transmitter, TIC-312, temperature controller, in DCS, TV-312, temperature control valve
- That is one line on the P&ID, representing the process intent. Measure temperature at this point, compute a control output, throttle this valve.
The ISA-20-style loop diagram for this same loop shows.
- TT-312. Rosemount 3144P, 4-20mA, -50 to plus 250 degC range, located at elevation 12.5m on column C-301
- Cable tag 312-TC-001. 2-conductor, shielded, 16AWG, from TT-312 to JB-312, junction box
- JB-312. Terminal 7 plus, 8-, drawing ref JB-312-01
- Cable tag 312-TC-002. Multi-conductor, shielded, from JB-312 to marshalling cabinet MC-1
- MC-1. Terminal strip TS-12, terminals 24 plus, 25-
- PLC card. Rack 2, slot 4, channel 6, tag TT_312_AI in program
- TV-312. Fisher 667-25 with Keystone actuator, 4-20mA positioner, with position feedback TVFB_312 to rack 2, slot 5, channel 2
One line on the P&ID becomes one sheet, sometimes two on the loop diagram. The mapping is one-to-one for simple loops, one-to-many for complex loops with redundant transmitters or valve position feedback.
Terminal numbering conventions
Loop diagrams carry terminal numbers at every signal transition point. The conventions are project-specific, but the common patterns are.
Junction boxes. Terminals numbered sequentially from 1, with positive and negative, or signal and return on adjacent terminal numbers. Terminal 7 and 8 for the first instrument, 9 and 10 for the second, and so on.
Marshalling cabinets. Terminal strips labeled by cabinet identifier and strip number, MC-1 TS-12. Terminals within the strip numbered from the top. Analog inputs typically land on adjacent odd, even pairs.
PLC I/O cards. Each card has a defined channel count, typically 8 or 16 channels. The channel assignment determines the program tag address and the hardware label on the card faceplate. The loop diagram shows all three. Rack, slot, channel.
On a project where the loop diagrams and the cable schedule have been produced separately, verify that terminal numbers match at every handoff point. A common error is the cable schedule showing terminal 7, 8 at JB-312 and the loop diagram showing terminal 9, 10. The loop check finds the mismatch, but it is slower to debug from the plant than from the desk.
When commissioning needs the loop diagram vs the P&ID
During commissioning, the two documents serve different phases of the loop check.
| Commissioning task | Document to use |
|---|---|
| Scope planning. How many loops need checking. | P&ID instrument count |
| Sequence planning. Which loops are in the same cable run. | Loop diagram or cable schedule |
| Trace a cable path from field to cabinet | Loop diagram |
| Identify which PLC channel a signal should appear on | Loop diagram |
| Confirm signal class for card type verification | Both |
| Apply a calibration signal at correct mA range | Loop diagram, instrument data section |
| Confirm alarm limits against process design | P&ID notes or instrument data sheet |
| Verify SIS loop separation | Both. P&ID for SIS designation, loop diagram for physical separation confirmation |
| Sign off a completed loop | Loop-check form derived from both |
The practical rule. The P&ID tells you what to check. The loop diagram tells you how to check it.
Generating one from the other
The P&ID-to-loop-diagram direction is partially automatable. The tag, signal class, connected equipment, and line reference all transfer directly from a structured P&ID instrument extraction. Hardware selection, manufacturer, model, cable type, barrier requires engineering input. Terminal numbering requires a cable schedule or marshalling layout.
In practice, the workflow for producing loop diagrams from a P&ID extraction is.
- Extract instrument list from P&ID. Tag, signal class, description, connected equipment.
- Engineer assigns hardware, manufacturer, model, calibration range for each tag.
- Electrical designer assigns cable tags, routing, and terminal numbers.
- Loop diagram is drawn from the combined data.
The loop-diagram-to-P&ID direction rarely occurs. P&IDs are issued first in the design sequence. However, on brownfield projects where loop diagrams survive but P&IDs are missing or outdated, loop diagrams are a valid source for reconstructing an instrument index. Every loop diagram carries the instrument tag, signal class, from the card type, and PLC assignment.
Where they overlap and where they diverge
| Question | P&ID | Loop diagram |
|---|---|---|
| What instruments exist on this unit. | Yes | No |
| What signal class is this instrument. | Yes, from ISA tag | Yes, confirmed by card type |
| What line is this instrument on. | Yes | Only if relevant to wiring routing |
| What PLC card and channel does this land on. | No | Yes |
| What cable tag carries this signal. | No | Yes |
| What equipment does this instrument monitor. | Yes | Sometimes |
| Is this an SIS loop. | Yes | Yes |
| What is the calibration range. | Sometimes | Yes |
Rework patterns to watch for
Treating the P&ID as wiring documentation. Engineers sometimes try to mark terminal strip numbers on a P&ID bubble. Do not. P&IDs get revised for process reasons. Wiring annotations end up out of sync.
Treating the loop diagram as process documentation. A loop diagram does not show that PSV-201 protects vessel V-200. If you remove PSV-201 from the design because "the loop diagram shows it goes to a terminal block," you have just removed a safety valve from a vessel. The P&ID is the process authority.
Assuming the I/O list comes from one source. Tag, signal class, description, equipment, and line come from the P&ID. PLC channel, cable, termination come from the loop diagram or cable schedule. A complete I/O list usually joins both.
Revision lag. P&IDs typically revise one or two steps ahead of loop diagrams. During an active design phase, a P&ID might add FIT-305 to the drawing. The loop diagram for FIT-305 may not exist yet. If you pull the I/O list from the P&ID and try to cross-check it against loop diagrams, you will have gaps. That is normal and reflects the phase offset.
What you can automate, what you cannot
The structured data on a P&ID, instrument tags, signal class, equipment, line number, connected loop is well-defined enough to extract automatically. Every bubble has a consistent pattern. Every line has a consistent tag format. Cross-references are explicit.
The structured data on a loop diagram is less standardized. Terminal numbers, barrier placements, and cable routing are captured in project-specific conventions that vary by firm and by site. Manual review of loop diagrams during commissioning is still the norm. For the step of pulling structured tag data out of P&IDs and turning it into an I/O list, the P&ID digitization guide covers the full workflow.
Related
- P&ID to I/O list. The P&ID side of the I/O list
- Instrument index vs I/O list vs line list
- PLC tag naming conventions. What happens to the ISA tag in the PLC
- Estimating PLC I/O count
- ISA 5.1 letter codes
- Commissioning lifecycle
FAQ
Can the I/O list be derived from the P&ID alone.
Tag, signal class, description, connected equipment, line number, and process variable all come from the P&ID. PLC rack, slot, channel assignments and cable numbers come from the loop diagrams or a separate cable schedule. A complete I/O list usually spans both sources.
When should loop diagrams be issued.
Typically at issued-for-construction, IFC. The P&ID is usually issued earlier, issued-for-design or issued-for-bid. Loop diagrams depend on selected hardware, so they lag by one engineering phase.
On a brownfield project with no surviving loop diagrams, how do I get cable and terminal data.
You have three options in order of reliability. Trace cables physically in the field and document terminations. Read terminal labels from marshalling cabinet photos. Or pull channel assignments from the PLC program's I/O tag table and reconstruct backwards. All three are slower than reading a loop diagram, which is why preserving as-built loop diagrams is worth the filing effort.
Is there a standard template for loop diagrams.
ISA 5.4 defines the required elements but not the exact layout. Most EPC firms have a house standard template. For projects without a house standard, ISA TR20.00.01 provides worked examples. The key requirement is that every signal transition point shows a terminal or connector reference traceable back to the field device and forward to the control system.
Can I generate loop diagram data from a P&ID extraction.
Partially. An extracted instrument list gives you tag, signal class, calibration range, if shown on the P&ID, and connected equipment. That is enough to set up the loop diagram shell. Hardware selection, cable routing, terminal assignments, and PLC channel numbers require engineering and design work that cannot be derived from the P&ID alone.