Define What the Switchgear Must Exchange

Network integration starts with the information operators and other systems need from new switchgear. A project may require status and alarm visibility, metering data, remote commands, or some combination; each function affects the controls design and the information exchanged. Identify the intended users and systems, such as a supervisory control platform, building controls, or an owner’s monitoring network, without assuming that any interface is included by default.

Document which functions are required, which are for monitoring only, and whether any remote control is intended. Confirm who has authority to request and approve commands, how alarms should be presented, and what happens when communications are unavailable. These early decisions help distinguish switchgear functions from network integration scope and give the design team a usable basis for selecting interfaces.

Select Protocols Around the Existing System

Protocol selection should follow the receiving system’s documented requirements and the proposed switchgear controls and metering devices. Confirm supported protocols, versions, media, and interface methods with the responsible controls and equipment teams. A protocol name alone is not enough: devices can differ in supported data objects, addressing, command behavior, diagnostics, and implementation details. Verify compatibility at the required functional level before finalizing the specification.

Also establish whether data will be exchanged directly or through a gateway, and identify who supplies, configures, and maintains that gateway. Resolve serial versus Ethernet connections, connection ownership, addressing conventions, and any required network segmentation with the project’s IT or operational technology stakeholders. Do not assume that a device supports a requested protocol, cybersecurity feature, or third-party integration until its specific design and documentation have been reviewed.

Build a Point List That Can Be Tested

A point list turns general integration goals into specific, reviewable requirements. For every required indication, alarm, measurement, or command, record the source device, point name, meaning, units where applicable, expected behavior, and destination system. Include useful context such as normal state conventions, alarm priority, update expectations, and whether a value is measured, calculated, or derived. Identify points that are optional or reserved rather than leaving their status ambiguous.

Review the list with the switchgear controls designer, metering stakeholders, and controls integrator before procurement is complete. Confirm naming, scaling, data types, read or write access, and how alarms and communications failures will be represented. If remote commands are required, define permitted command types and the project’s authorization and interlock expectations. Final point counts and capabilities must be verified against the selected equipment configuration; do not infer them from a generic product description.

Coordinate Topology and Physical Interfaces

The network topology describes how switchgear devices connect to one another and to the receiving system. Show devices, switches, gateways, network boundaries, connection paths, and the demarcation point between equipment and owner networks. Confirm port and media requirements, cable responsibility, device locations, addressing, and whether the design calls for a direct connection or an intermediate interface. These details affect enclosure planning, controls wiring, procurement scope, and coordination with the site network design.

Topology choices also establish operational dependencies. Determine which devices need network access, what functions remain locally available if communications fail, and who manages configuration and changes. Cybersecurity and remote-access requirements should be reviewed by the owner’s authorized stakeholders; avoid treating a protocol or network connection as proof of security. Physical and logical interfaces, including any equipment supplied by others, should be assigned explicitly so gaps do not emerge late in the project.

Assign Documents, Testing, and Ownership

Integration requires coordinated documents, not just a protocol selection. Identify who prepares and approves the point list, network diagrams, interface schedules, addressing information, device configuration records, and operating descriptions. Confirm which documents are needed at submittal, before testing, and for turnover. For new switchgear, the equipment supplier’s documented scope should be distinguished from the controls integrator’s configuration and the owner’s network responsibilities.

Agree on a test plan that checks the specified points and interfaces using the project’s approved procedures. Define participants, test environment, acceptance criteria, and how discrepancies will be recorded and resolved. Verify communications, point mapping, units, alarms, and authorized commands as applicable; testing must not imply unsafe work on energized equipment. Qualified electrical and controls professionals should review the design and testing approach, with applicable standards and authority requirements determined for the project.

Prepare the Integration Package for Procurement

Before requesting a proposal for new switchgear, provide the current one-line and equipment specifications alongside the intended protocol, point list, topology, and interface boundaries. Include the receiving-system requirements, owner or integrator contacts by role, preferred naming conventions, and any approved network constraints. Mark unresolved items clearly and identify who will decide them and by when. This lets the manufacturer assess the requested controls and metering configuration rather than price an assumed interface.

During review, compare each proposal’s documented scope against the required points, protocol details, hardware interfaces, and deliverables. Ask which selections remain project-dependent, what information is needed to complete them, and when interface documents must be approved to support the project schedule. Confirm that any UL 891 requirement applies to the proposed switchboard assembly, where relevant; it does not establish network capability. Final technical selections require specification review by qualified professionals and applicable project authorities.

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.

ItemWhat to confirm
Protocol and versionConfirm the receiving system’s required protocol, version, interface method, and verified compatibility with proposed devices.
Point listDefine required indications, alarms, measurements, commands, naming, units, data types, and access expectations.
Network topologyDocument devices, gateways, network boundaries, connection paths, demarcation points, and communications-failure behavior.
Scope ownershipAssign responsibility for equipment interfaces, gateway supply, configuration, network provisioning, and ongoing changes.
Documents and testingAgree on required drawings and records, test participants, test conditions, and project-specific acceptance criteria.