Request a Quote

Ratings & specifications

Switchgear Communications Protocols

Specify switchgear communications by starting with the owner’s monitoring objectives, then aligning device protocols, network architecture, cybersecurity controls, and the data required at each interface.

01 / BUILT WITH PURPOSE SWITCHGEAR BUILDERS OHIO

Enclosed electrical switchboard with meters and breakers
REPRESENTATIVE
EQUIPMENT
01
Made in USAAmerican manufacturing
02
UL 891 assembliesFor applicable low-voltage switchboards
03
Short lead timesTiming quoted per project

Start With the Monitoring Objective

A communications schedule should begin with what operators need to see or do, not with a preferred protocol name. Identify whether the system will display breaker status, alarms, metering, protective relay events, or equipment diagnostics, and determine which functions are monitoring-only versus permitted remote control.

Clarify where each point must appear: local display, building management system, plant SCADA, historian, or utility interface. The owner’s controls engineer should define required point names, units, update expectations, alarm priorities, and retention needs. These details shape device selection and avoid paying for data no system can use.

Match Protocols Across Every Interface

Switchgear may contain meters, trip units, protective relays, and gateway devices with different native protocols. Common options include Modbus RTU or TCP, DNP3, and IEC 61850, but availability and supported functions vary by device and configuration. Confirm the exact protocol, transport, register or data model, and firmware requirements.

A gateway can translate between systems, but translation may not preserve every event, timestamp, control command, or diagnostic value. Obtain the owner’s approved protocol list and interface specifications, then identify which device is the data source and which system is the client. Confirm whether protocol licensing or configuration files are required.

Choose a Topology That Fits the Site

Topology affects wiring, troubleshooting, latency, and failure exposure. Serial daisy chains can reduce cable runs but require attention to device addressing, termination, cable limits, and the consequences of an open connection. Ethernet designs may use switches, redundant paths, or separate networks; these choices depend on the facility’s standards and criticality.

Show the proposed network boundary and connection point on project documents. Confirm switchgear communication ports, fiber or copper media, port speeds, VLAN or subnet expectations, and who supplies network switches and patching. The responsible network engineer should review routing, redundancy, and access to plant systems before the equipment interface is finalized.

Set Cybersecurity Boundaries Before Design

Cybersecurity requirements should define access, not merely request a secure network. Ask whether remote access is prohibited, owner-managed, or allowed through an approved jump host or VPN. Confirm account roles, authentication rules, password handling, logging, time synchronization, and the process for disabling access during commissioning or after service.

Document which communications are read-only and whether any remote commands are permitted. Separate protection and control functions from supervisory monitoring as the design requires; a network connection should not be assumed to replace local protective operation. Owner cybersecurity staff should approve ports, protocols, device hardening expectations, and update responsibilities.

Define Points, Alarms, and Data Quality

A useful point list identifies each value, source device, destination, scaling, units, normal state, and alarm treatment. Distinguish breaker position from trip indication, and distinguish measured current from a calculated demand value. Specify whether event records need sequence-of-events timestamps and what time source devices will use.

Agree on naming conventions and point delivery format before fabrication documents are released. Identify required alarm deadbands, quality flags, and behavior when a device or network link is unavailable. These decisions help the controls contractor map data accurately and let the owner test that screens and alarms represent switchgear conditions correctly.

Coordinate Equipment and Network Responsibilities

A communications scope crosses equipment, controls, and IT work. Establish who provides internal device wiring, gateways, network switches, fiber converters, external cables, software configuration, and final connections. For a new switchboard or switchgear lineup, confirm the intended communication devices and available mounting or wiring provisions against the project design.

Responsibility gaps often surface at the lineup boundary: a device may be installed while its address plan, network drop, or system mapping remains undefined. Request a responsibility matrix showing supplier, electrical contractor, controls integrator, and owner tasks. Also confirm submittal review milestones and the documents needed for integration.

Plan Commissioning and Acceptance Checks

Commissioning should verify more than link lights. Define checks for device addressing, protocol communications, point mapping, scaling, breaker status, alarms, timestamps, and recovery after a communication interruption. Where remote control is authorized, establish a controlled test procedure and clear limits approved by the responsible engineer and owner.

Specify who provides test equipment, network access, system simulators, and the operator available to witness end-to-end checks. Acceptance criteria should reflect the project’s actual monitoring scope rather than assume every point is available in every device. Record final settings, addresses, firmware, and as-built network connections for operations staff.

Prepare a Complete Communications RFQ

For a communications-focused quotation, provide the one-line diagram, equipment type and voltage class, device schedule if available, monitoring-system standards, preferred protocols, point list, and network diagram. Include cybersecurity requirements, interface locations, redundancy expectations, environmental constraints, and the intended division of supply and installation work.

Identify whether the project calls for a UL 891 switchboard, UL 1558 low-voltage switchgear, or medium-voltage equipment; communications requirements do not make these equipment categories interchangeable. A U.S. manufacturer can custom-fabricate new equipment with American components and coordinate nationwide shipping. Have the responsible engineer, utility, and AHJ review applicable interfaces and design requirements.

PROJECT PARAMETERS

Details make
the difference.

Every project is different. Use these points as a starting place for a conversation about your requirements.

Discuss your specifications
SPECIFICATION OVERVIEW01 — 06
Project specification overview
Equipment & scopeDefined by project requirements
Voltage classConfirm for the application
Current ratingConfirm for the application
Applicable standardsUL 891 for applicable low-voltage switchboards; other standards per specification
ManufacturingMade in USA with American components
Lead timeQuoted per project

Final configuration, ratings, standards, and timing are confirmed with your quote.

LET'S GET TO WORK

Tell us what
you’re building.

Share the essentials and start a conversation about equipment for your project.

Prefer to talk?(951) 403-5738

Email our team at saleselectricalbuyers@gmail.com.

SWITCHGEAR BUILDERS OHIO
BUILT FOR THE WORK AHEAD

PROJECT INQUIRY

Request a quote

This form opens your email application where supported. Review and send your request to saleselectricalbuyers@gmail.com from your email app; nothing is submitted directly through this website.

* Required fields