Engineering Library
Reference material for the documents a control system is designed, built, and handed over with.
Written guides in this section
Full references, procedures, and diagnostic guides published under Engineering Library.
How to Read a P&ID
What a piping and instrumentation diagram shows, how ISA-5.1 tag bubbles and line types encode the control system, and how to trace a loop across sheets.
8 min readUpdated Sep 5, 2026
Control Schematics
The ladder-style drawing of every control circuit in a panel: how a schematic is organized by line number, the conventions for contacts, coils, and cross-references, what belongs on a schematic and what belongs on a wiring diagram, and reading one under pressure.
9 min readUpdated Sep 5, 2026
Wiring Diagrams
The drawing that says where every wire goes: panel wiring and interconnection diagrams, and the conventions of wire numbers, conductor colors, terminal numbers, and cable numbers that make them readable. What belongs here versus on the schematic.
9 min readUpdated Sep 5, 2026
Network Drawings
The two drawings every control network needs: a logical drawing of zones, subnets, VLANs, firewalls, and conduits, and a physical drawing of switches, ports, cables, fiber, radios, and sites. What each shows and why they are sensitive.
9 min readUpdated Sep 5, 2026
Panel Layouts
The drawing of what goes where inside a control panel: enclosure, back plate with every component to scale and keyed to the bill of material, wireways, terminals, door devices, and entries. The conventions, the required spacings, and the checks.
9 min readUpdated Sep 5, 2026
I/O Lists
The document that ties the field to the controller: what every I/O list column means, how tags, terminals, and module channels are assigned, spare capacity rules, how the list drives the drawings and the program, and how to keep it true after commissioning.
9 min readUpdated Sep 5, 2026
Browse Engineering Library
Drawings
The drawing set a control system is built from.
5 topics
Lists & Schedules
The tabular deliverables that keep a project consistent.
5 topics
Control Documentation
Describing intended behavior before anyone writes code.
4 topics
Checklists
Repeatable checks for design, test, and turnover.
7 topics
Standards
The standards bodies whose documents govern this work.
8 topics
Full contents
Direct contact
Have a controls question?
Reach Eric Sullivan directly about anything on this site, a controls or automation topic, or one of his personal projects.
References to manufacturers, products, model numbers, software platforms, technical specifications, companies, standards organizations, or other organizations are provided for informational purposes and do not imply sponsorship, endorsement, authorization, or affiliation unless expressly stated. Manufacturer specifications must be independently verified against current manufacturer documentation.