The short answer
Control Schematics
A control schematic shows every control circuit in a panel as rungs between two power rails, numbered by line, with each device drawn as its symbol in the de-energized state and every contact cross-referenced to the coil that operates it. It shows how the circuit works, not where the wires run; the wiring diagram does that. Schematics are read line by line from the power source to the load, and their cross-reference numbers are what let a technician follow a circuit across pages when the panel is dead and the pump is not running.
Key points
- A schematic shows function; a wiring diagram shows connections. A panel needs both.
- Line numbers on the left, a device per rung, contacts cross-referenced to their coils by line number.
- Every device is drawn de-energized, with no power applied and no process acting on it.
- Wire numbers on the schematic match the wire labels in the panel.
- The schematic is the document a technician reads at 2 a.m. It is drawn for that reader.
What a schematic shows
A control schematic is a functional drawing. It takes the control circuits of a panel, the 120 V AC or 24 V DC circuits that operate the starters, the relays, the pilot lights, and the controller inputs and outputs, and lays each out as a rung between a left rail and a right rail, in the order that makes the circuit easiest to understand. A pump start circuit is drawn as a line: control power, the HOA switch, the overload contact, the seal-leak relay contact, the controller output relay contact, and the starter coil. Reading the line from left to right is reading the conditions under which the coil energizes.
It does not show where the components sit in the panel or how the wires are routed, and it is not supposed to. That is the wiring diagram, which is drawn from the schematic and shows the terminals and the physical connections. A panel package contains both, and they agree with each other because one is derived from the other.
Conventions
- Line numbers
- Every rung has a number at the left margin, usually incrementing by one per line with the page number as a prefix: 101, 102, 103 on page 1. Line numbers are the addressing system of the whole drawing set.
- Rails
- Control power on the left rail, neutral or common on the right, with the source of that control power shown on the first page: the control transformer or the power supply and its protection.
- Device symbols
- Contacts, coils, switches, pilot lights, overloads, and terminals drawn to the standard the site uses, commonly NEMA or IEC, and never mixed. Devices are drawn de-energized: contacts in their shelf state, switches with no hand on them, floats hanging in air.
- Device tags
- Every device has a tag beside it: CR1, M1, OL1, HOA-1, LSH-101. The same tag is on the wiring diagram, the panel layout, and the device label.
- Cross-references
- Beside every coil, the line numbers of every contact it operates, with a bar over the number for a normally closed contact. Beside every contact, the line number of its coil. This is what lets the reader follow a relay across pages.
- Wire numbers
- Every wire between two devices has a number, usually derived from the line number where it originates, and the number is on the wire label in the panel. A technician reading wire 104A on the drawing finds wire 104A on the terminal.
- Terminal symbols
- Where a wire leaves the panel to a field device, a terminal symbol with the terminal strip and number, and the field device drawn beyond it with a note that it is field wiring.
- Notes and legend
- A legend page with the symbols, the abbreviations, and the wire numbering convention, and notes on the pages for anything the symbols do not say.
Organizing the pages
A well-organized schematic set reads in a logical order. Power distribution first: the incoming service, the disconnect, the branch protection, the control transformer, the DC supply. Then the control circuits by equipment: pump 1 control, pump 2 control, the alternator and level logic if it is in relays, the alarm circuits. Then the controller: power, inputs by module, outputs by module, each channel on its own line with the field device and the terminal. Then communications and miscellaneous. A reader looking for why pump 2 will not start goes to the pump 2 pages and follows the circuit; a reader looking for what is on input 3 of module 2 goes to the input pages.
| Belongs on the schematic | Belongs on the wiring diagram | Belongs elsewhere |
|---|---|---|
| Every control circuit, as a rung | Terminal strip layouts with every terminal | Panel layout: where the components sit |
| Device tags and cross-references | Wire-by-wire connection lists | Bill of materials: what the components are |
| Wire numbers | Cable entries and field wiring terminations | I/O list: the signal chain to the controller |
| Controller I/O channels with their field devices | Module terminal assignments | Loop drawings: instrument loops in detail |
| Power distribution and protection | Grounding and bonding connections | Nameplate schedule |
Reading a schematic under pressure
- 1
Find the load
The coil, the light, or the controller input that is not doing what it should. Its line number is the starting point.
- 2
Read the rung from the load back to the rail
Every contact and switch in series is a condition. With a meter, measure from the right rail to each point moving left; where the voltage appears is the last closed device, and the device to its right is the open one.
- 3
Follow the cross-references
An open relay contact sends you to the line of its coil, which has its own rung and its own conditions. Follow it. A relay whose coil circuit is open explains the contact.
- 4
Check the field
Where the rung passes through a terminal to a field device, the device and its wiring are the next suspect: a float, an HOA, a seal-leak probe.
- 5
Mark what you found
A schematic that has been through a real fault has notes on it that the next reader needs. Return the markup to the master.
Keeping it current
Panel schematics are the drawings most often wrong in the field, because panel changes happen at the panel and the drawing is in an office. A red-line copy in the panel pocket, marked at the time of every change, returned to the master on a schedule, is the practice that keeps them usable. A drawing that has not been red-lined in five years at a panel that has been modified is worse than no drawing, because it is trusted.
Frequently asked questions
- Do we need schematics if the logic is in the PLC?
- Yes. The controller replaces relay logic; it does not replace the control circuits that feed the controller inputs, drive its outputs through relays and starters, and keep the HOA, the overloads, and the safety devices working when the controller is not. Those circuits are on the schematic, and so is every controller channel.
- What is the difference between a schematic and an elementary diagram?
- None in this context. Elementary diagram is the older term for the same ladder-style functional drawing, still used in some specifications and by some utilities.
- Should the PLC program logic be shown on the schematic?
- No. The schematic shows the hardware circuit up to the controller channel and a note on what the channel does. The logic lives in the program and its documentation. Drawing a ladder rung from the program on the schematic invites the two to disagree.
- Who is the schematic drawn for?
- The person at the panel with a meter and a problem. Every decision about layout, numbering, and cross-references serves that reader. If a convention makes the drawing prettier and harder to trace, the reader loses.
Related topics
- How to Read a P&IDWhat 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.
- I/O ListsThe 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.
- Component LayoutArranging a panel so it is safe to work in, cool enough to run, quiet enough for its signals, and possible to modify: power and control separation, heat, wireways, terminals, and the working space rules.
- Hand-Off-Auto SelectorsWhat each position of an HOA selector does, how it is wired into the starter circuit, which protections must survive Hand, what the controller should see, and the mistakes that let a pump run with nobody watching.
- Pump Will Not StartA pump that is called and does nothing. The order to check: permissives and mode, control power, the starter or drive, the motor circuit, and the pump itself, with the measurements that settle each one in minutes.
- UL 508A Industrial Control PanelsWhat the listing actually covers, what has to appear on the label, and the requirements that most often cause a panel to fail inspection.
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.