Two diagram types answer different questions
Elementary and wiring diagrams serve related but distinct purposes in new switchgear documentation. An elementary, or functional, schematic shows how a control or metering circuit is intended to operate: which devices interact, what conditions enable an action, and how signals or contacts affect the sequence. A wiring diagram translates that design into physical connection information, identifying conductors, terminals, and device points to be connected. The schematic helps reviewers assess function; the wiring drawing helps installers and panel builders trace connections. Neither drawing should be treated as a substitute for the other. Agreeing on the purpose and detail of each deliverable early reduces ambiguity during design review, assembly, and field integration.
Define the functions before selecting detail
Start by identifying what the switchgear control and metering documents must communicate. Inputs may include operating sequences, control power assumptions, instrument and meter requirements, device contact data, alarms, interlocks, and any required remote indications or commands. Confirm which functions belong in the equipment and which are provided by external systems. The elementary schematic should make those boundaries and operating relationships understandable without implying an unverified capability. Determine whether the project needs overview-level logic, device-by-device control circuits, or both. The appropriate detail depends on the application, equipment design, and review needs; it is not determined by a generic diagram package. Qualified electrical professionals should review the requirements and applicable project criteria.
Specify terminal and interface information
Wiring diagrams need a clear connection convention. Confirm terminal designations, device identifiers, conductor identification expectations, and how external connections will be shown. Identify interfaces to field devices, other switchgear sections, control panels, metering systems, and building or supervisory controls, as applicable. For each interface, clarify the signal or circuit purpose, source and destination, and responsibility for defining the connection. Also establish how spare or reserved points should be represented, if required, rather than assuming their inclusion. These decisions help keep drawings aligned with the actual assembly and reduce uncertainty at connection points. Connection details, ratings, and compatible devices must be verified against the project design and selected equipment.
Choose metering and control representations
Metering requirements influence both functional and connection drawings. Specify the measurements, indications, alarms, and communications interfaces the project calls for, then identify the instruments or devices and their intended relationships. Confirm the required signal types and interfaces with the responsible system designers; do not infer compatibility from a drawing symbol alone. Control design choices may include local versus remote operation, permissive conditions, status feedback, and how interlocks are represented. The elementary diagram should explain these relationships, while wiring documentation should show the associated connections at the level required for review and construction. Instrument transformer arrangements, protective functions, and other design details require project-specific verification and should not be assumed from a general diagram description.
Coordinate review, revisions, and verification
Before documentation is finalized, coordinate the schematics and wiring drawings with the equipment specification, device information, interface schedules, and control narratives. Reviewers should check that identifiers and references agree across documents and that external connection responsibilities are unambiguous. Resolve comments through controlled revisions so changes to a function also prompt review of affected terminal information. Establish what drawing status is needed for procurement, approval, assembly, and final record documentation. Any inspection or testing expectations should be defined for the specific project and equipment; drawings alone do not establish test scope or prove system performance. Applicable standards and verification methods depend on the design and must be confirmed by qualified professionals and relevant authorities.
Prepare a useful documentation request
For a new switchgear quotation or design review, provide the one-line diagram, equipment specifications, control narrative, metering schedule, interface list, and known external connection requirements where available. Mark open decisions, such as which party supplies remote signals or defines field terminal conventions, instead of allowing assumptions to enter the drawings. Ask which elementary and wiring diagram deliverables are proposed, what level of detail they contain, and how revisions and review comments will be handled. Custom assemblies can be developed to project specifications, with the document scope coordinated to the selected design. For projects in Austin or elsewhere in Central Texas, identify review milestones and shipping coordination needs early; the manufacturer builds in the USA and can ship nationwide, while timing is project-dependent.
Project specification checklist
Use this checklist to organize the details for a project-specific review. Final ratings, applicable standards and equipment selections depend on the approved design.
| Item | What to confirm |
|---|---|
| Functional scope | Confirm required operating sequences, interlocks, indications, alarms, and control boundaries. |
| Metering requirements | Define measurements, devices, signal interfaces, and communications needs for the project. |
| Terminal conventions | Agree on identifiers, conductor references, external connection points, and reserved-point treatment. |
| Interface responsibility | Document signal source and destination and clarify which party defines each connection. |
| Document lifecycle | Set deliverable detail, review milestones, revision control, and any required record-document status. |