How to Read Functional, Circuit, Wiring and Terminal Diagrams in MV Switchgear

No single switchgear drawing tells the whole truth. A functional diagram explains intent, a circuit diagram explains electrical logic, a wiring/interconnection diagram explains physical conductors, and a terminal diagram explains where work is performed. Safe troubleshooting means moving deliberately between these views while keeping device state, source and return path consistent.

This guide teaches a repeatable reading method for MV breaker trip/close, CT/VT, alarms, interlocks and external interfaces. It also shows how to detect contradictions before they become FAT or field failures.

Executive rules

Start with document status, revision, applicable panel/serial and drawing legend—not the first wire line.
Identify reference-designation, symbol, contact-state, wire and terminal conventions before tracing.
Define the equipment/energy condition represented by “normal” contacts.
Trace both supply and return; an output contact alone is not a complete circuit.
Follow object IDs across views; do not assume nearby graphical symbols are physically near.
Distinguish functional dependency from physical connection.
For every cross-reference, confirm destination sheet/grid and reciprocal reference.
Trace safety-critical CT secondary and breaker trip paths end-to-end, including test links and removable positions.
Compare drawing logic with IED/PLC/IEC 61850 configuration when software or GOOSE participates.
Record contradictions as controlled technical queries; never “interpret” a field wire into compliance.

1. Standards and conventions

Reference	Use
IEC 61082-1:2014	Presentation rules for electrotechnical diagrams, drawings and tables
IEC 81346-1:2022	System structuring and unambiguous object/reference designations
IEC 60617:2026 DB	Current IEC graphical-symbol database for diagrams
IEC 81355-1:2024	Classification/designation of information containers
IEC 61850-6:2009+A1:2018+A2:2024	SCL configuration description for communication/IED system relations
IEC 60255-27:2023	Protection-equipment product safety; not a functional logic standard

Project conventions may supplement the standards. The drawing set must state deviations and symbol variants. A familiar ANSI symbol or contact notation must not be silently mixed with IEC presentation rules.

2. Four diagram types—and the question each answers

View	Main question	Usually omits
Functional/block diagram	What functions depend on or exchange information with what?	Wire/terminal detail and exact component implementation
Circuit/elementary schematic	How does current/signal flow and logic operate?	Physical route, panel location and cable construction
Wiring/interconnection diagram	Which device pin/terminal connects by which conductor/cable?	Full functional logic and internal device algorithms
Terminal diagram/plan	What lands where, with which link/test/disconnect hardware?	Complete upstream/downstream logic

Use all four. A terminal plan can prove that X1:12 connects to cable core 14, but only the circuit/functional documents reveal whether that core is trip, supervision or a shared return and how it should behave.

3. Pre-read document control

document ID/title, project/lineup/bay and sheet count;
revision and purpose/status: review, manufacture, FAT, construction or as-built;
effective product serial/range and approved change notices;
legend, abbreviations, symbol library and wire/contact convention;
cross-reference grid/page scheme;
source drawings/configuration files and precedence;
language/unit/date and author/checker/approval;
outstanding mark-ups or superseded notices.

Stop if the field panel and drawing baseline cannot be matched. Troubleshooting against a “similar” bay can energise the wrong trip coil, open a CT or bypass an interlock.

4. Decode reference designations

A reference designation identifies the same object across views. The project may show functional, product and location aspects. Before tracing, select several labelled devices in the panel and verify their tags on schematic, terminal plan, BOM and layout. Record:

bay/functional unit and function;
physical product, e.g., relay, breaker coil, contact or MCB;
location/compartment/door/terminal box;
terminal/pin and plug/connector side;
external-system owner for cross-boundary signals.

Do not infer a device type from its tag letter alone unless the project’s IEC 81346 application rules say so. Persistent identity matters more than mnemonic convenience.

5. Understand contact state

breaker mechanically open or closed;
truck service, test/disconnected or removed;
earth switch open/closed;
coil energised/de-energised;
mechanism charged/discharged;
relay in healthy/powered state or shelf/unpowered state;
process normal, alarm or fail-safe condition.

“Normally open” often means the contact is drawn with its operating device unactuated, not necessarily the power system’s normal operating state. Breaker 52a follows closed position; 52b follows open position under common conventions, but confirm the project/manufacturer convention and timing.

6. Read a functional diagram

Identify the initiating condition or operator command.
List permissives, blocks, mode selections and dependencies.
Find timers, latches, voting, first-out and reset rules.
Identify outputs and all destinations, including remote devices.
Check fail state when power, communication or input quality is lost.
Map each block to the implementing IED/relay/hardwired circuit.
Find the requirement and test case for each path.

Functional arrows may mean information or dependency, not a copper wire. If the path is IEC 61850 GOOSE or internal IED logic, the detailed truth lives in controlled settings/SCL/logic files and must be cross-referenced.

7. Read a circuit diagram: source to return

Mark supply source, polarity/phase and protection/isolation device.
Follow every series permissive/contact/terminal.
Identify parallel paths and diode/resistor/suppressor effects.
Locate the load: trip/close coil, relay input, lamp or auxiliary relay.
Trace the return to the correct supply pole/neutral.
Check supervision branches and leakage currents.
Review the circuit in every required breaker/selector/supply state.

Highlight current flow in different colours for normal, command and failure states. A parallel indication lamp or trip-circuit supervision resistor can pass small current that does not operate a coil but changes measurements and false-pickup risk.

8. Follow cross-references correctly

device coil/function location and every associated contact location;
off-page conductor continuation with same potential/wire ID;
external drawing/document/terminal boundary;
cable/core to terminal/wiring schedule;
reciprocal reference back to origin;
reference to logic/settings/SCL for virtual connections;
change cloud/revision affecting only one side.

A missing reciprocal reference is a review defect. Never assume a same-number wire across panels is electrically common unless the wire-numbering convention explicitly defines global scope.

9. Read wiring/interconnection diagrams

from/to object and exact terminal/pin/connector;
wire number, size, colour, type and ferrule;
cable ID, core/pair/quad, shield and spare cores;
internal versus external/supplier boundary;
segregation/routing class and EMC earth point;
removable plug side and test/disconnect link;
wire-end count and terminal capacity;
jumper/bridge and whether factory or site installed.

Wiring diagrams can be point-to-point or layout-oriented. A graphical route is not necessarily the physical duct route unless the document says so. Use the cable/routing schedule for installation constraints.

10. Read a terminal diagram

block/strip and terminal sequence with panel side versus field side;
feed-through, disconnect, fused, knife, test or CT-shortening terminal type;
fixed/removable bridges and normal/test position;
wire/cable core at each side and destination;
earth/shield terminals and insulated sections;
spare terminals/cores and reserved future function;
separation of different voltage/current/EMC classes;
safe physical access and warning labels.

For CTs, confirm shorting occurs before the measuring/protection circuit opens. For VTs, confirm test isolation prevents secondary backfeed and that neutral/earth links are correct. The terminal hardware’s internal bridging is part of the circuit.

11. Worked trace: breaker trip command

Functional view: protection element operates, subject to enabled logic, then asserts Trip 1 and lockout/event outputs.
Logic/settings: identify protection stage, timer, matrix bit and physical/GOOSE output assignment.
Circuit: DC positive through trip MCB/fuse, relay output, interlocks/52 contacts as designed, test terminals and trip coil.
Return: trip coil to correct DC negative, with trip-circuit supervision branches noted.
Wiring: IED output pins to terminal block, cable/core to breaker plug and coil terminals.
Terminal plan: normal link positions, isolation/test access and external boundary.
Test: inject element, verify logic/output/current/coil/breaker/event/SCADA and repeat failure states.

Confirm that the trip relay contact can interrupt the DC inductive load or that an interposing device/suppression is correctly applied. Verify both trip coils independently where provided.

12. Worked trace: breaker close command

command source/local–remote selector and authority;
synchronism/dead-bus permissive where applicable;
breaker open, truck/service/test, earth switch, spring charged and lockout permissives;
anti-pumping circuit and close pulse duration;
DC source/protection, close coil and return;
52a/52b and mechanism contacts that interrupt/reset current;
position indication and failure-to-close alarm/time;
remote/GOOSE path supervision and cybersecurity enable.

13. CT circuit reading checklist

primary location, P1/P2 orientation and protection zone;
core, ratio/tap, class and polarity S1/S2 convention;
secondary earth exactly once at defined location;
series path through test switch/shorting links/terminals/relay/meters;
unused cores/taps treatment;
CBCT cable/screen-earth routing direction;
burden/lead resistance and wire size;
test sequence that never opens an energised secondary.

14. VT circuit reading checklist

primary phase/neutral connection and fuse/disconnect;
secondary winding, ratio, polarity and neutral earth;
secondary fuses/MCBs, selectivity and burden distribution;
metering/protection segregation and core/winding sharing;
broken-delta/residual connection and damping resistor;
withdrawable VT primary/secondary position contacts;
test plug/injection boundary and backfeed prevention;
voltage-selection/transfer logic and loss-of-voltage alarm.

15. IEC 61850 and virtual wiring

logical node/data object and semantics/quality;
publisher dataset, GOOSE control block and destination subscriber;
MAC/VLAN/priority, network/redundancy path and supervision;
logical input binding to IED logic and physical output;
SCL SCD/CID baseline and file/checksum actually loaded;
time synchronisation for events and sampled values;
fail state on stale/bad/communication loss;
test/simulation mode and blocking/indication.

A dashed arrow labelled GOOSE is not enough. Trace the SCL and IED logic to prove that the correct data object, quality handling and output matrix implement the functional intent.

16. Consistency and error detection

Symptom	Likely issue
Terminal exists only on one document	Model/view divergence or missing wiring
Contact cross-reference has no coil	Orphan/incorrect device tag
Wire changes number without terminal	Unshown boundary or drafting error
Same signal with opposite normal state	Semantic/contact convention conflict
CT earth shown at two locations	Potential circulating/measurement error
GOOSE in drawing but absent in SCL	Virtual connection not configured
Field cable has more cores than schedule	Wrong revision/cable or undocumented spare
Test passes only with link moved	Normal/test state or circuit design defect

17. Safe field-verification workflow

Match approved as-built configuration to panel/bay/serial.
Perform risk assessment, isolation, prove-dead and stored-energy control.
Identify circuit energy sources including DC, AC, CT, VT and remote backfeed.
Use approved test links and rated instruments; do not lift wires casually.
Verify tag/terminal/wire physically and cross-check both ends.
Test one controlled function/state at a time with operations coordination.
Restore every link/fuse/selector/test mode and independently verify normal state.
Record results/mark-ups and process them into controlled as-built sources.

18. Review checklist

correct approved baseline and complete index;
legend/reference/symbol/contact conventions understood;
functional–circuit–wiring–terminal object IDs consistent;
source/protection/load/return traced for each function;
cross-references reciprocal and resolvable;
all states/failure modes analysed;
CT/VT/trip/close safety features explicit;
software/SCL/relay configuration consistent;
requirements and FAT/SAT tests linked;
contradictions closed by approved revision.

19. Reading indication and alarm circuits

Do not assume an illuminated “closed” lamp is an independent proof of primary contact position. Trace its source contact—52a, mechanism auxiliary, IED logic or SCADA echo—plus lamp-test and shared return. A red/green lamp scheme can show both on or both off during transition, contact failure or DC loss.

distinguish physical position, commanded state and process current/voltage confirmation;
identify de-energise-to-alarm versus energise-to-alarm and DC-loss behaviour;
trace annunciator latching, first-out, acknowledge and reset;
check alarm contacts for normal/failed device state and communication quality;
verify lamp-test paths do not backfeed coils or relay inputs;
map local wording to SCADA signal ID, polarity and event time stamp.

References

Safety note: Drawing interpretation does not authorise live work. CT/VT/trip circuits contain hazardous energy and can operate primary equipment. Use approved switching, isolation, proving-dead, shorting/backfeed controls and qualified personnel.