Power distribution, with purpose.
A communications gateway connects switchgear controls and meters to a supervisory system, but the device alone does not define a working interface. Protocol compatibility, point meaning, network responsibility, time synchronization and commissioning boundaries all need to be settled before equipment is built. For a new switchgear order, documenting these decisions early helps avoid late drawing changes and field disputes.
Define the data path before selecting a gateway
Start with the systems that must exchange information: switchgear-mounted meters, protective relays, breaker controls or other devices on one side, and the owner’s SCADA, building management or monitoring system on the other. Identify each device model and intended role, then record the required protocol on each interface. A device may support several protocols, but that does not establish that every requested function, data object or command is available through each one. Confirm the relevant firmware, license requirements and protocol options for the specific order.
Choose whether the gateway translates between protocols, aggregates data, or performs both functions. Translation can simplify an upstream connection, but it may constrain how vendor-specific alarms, event records or control functions are represented. The quote package should identify the proposed gateway make and model, protocol direction, port types, and any required switches or accessories, subject to engineering review. If the upstream system specification is not final, state that explicitly rather than treating a provisional interface as a confirmed design.
Set network ownership and interface boundaries
A network diagram should show which party supplies and configures the gateway, Ethernet switches, fiber or copper links, addressing, VLANs, firewall rules and upstream connection. Clarify whether the gateway network is dedicated to switchgear or joins an owner-managed network. That choice affects port counts, segregation, access permissions and the information the switchgear manufacturer needs to complete its portion of the design. Do not assume that a physical Ethernet port means an approved connection to the facility network.
Assign responsibility for IP addresses, credentials, certificates, remote access and final network approval. A manufacturer may build equipment to an agreed interface, while the owner or its integrator retains responsibility for enterprise network policy and connection authorization. Make the boundary visible on the network drawing and scope matrix. For projects in Dallas–Fort Worth or elsewhere, shipping equipment nationwide does not establish responsibility for on-site network configuration or commissioning; those tasks must be explicitly assigned and validated for the project.

Make the points list operationally precise
A usable points list describes more than tag names. For every requested value, identify its source device, register or object where available, description, data type, units, scaling, normal state, update behavior and destination tag. Distinguish status and measurement points from alarms, event records and control commands. Include the intended meaning of breaker position, trip indication and alarm states, since different devices can encode similar labels differently. Mark unavailable or tentative points instead of silently omitting them.
Decide whether the gateway will expose read-only monitoring or permit commands. Remote open or close control can require additional interlocks, permissions, operating procedures and owner approvals; it should never be inferred from a request for status monitoring. A reviewed points list becomes a key design record for programming, graphics and acceptance testing. Changes after approval can affect gateway configuration, drawings and field integration, so identify who may authorize revisions and how updated versions will be distributed.
Plan time synchronization and event interpretation
Sequence-of-events data is useful only when device clocks are aligned closely enough for the intended analysis. Specify the time source and distribution method, such as an owner-provided network time service or another project-approved source, and identify which devices must synchronize directly and which rely on the gateway. Confirm that the selected devices and protocol interfaces support the required time behavior. Recording time zone, daylight-saving treatment and timestamp format prevents confusion when gateway logs, relay events and supervisory displays are compared.
Define the required timestamp resolution and acceptable synchronization performance with the system designer or owner; do not presume that a gateway improves the accuracy of source-device timestamps. The design record should state how loss of the time source is indicated and what happens after a device or gateway restart. If event chronology is part of an acceptance test, agree on a test method and responsible party before shipment. Those requirements can influence device selection, network planning and the division between factory verification and field validation.
Review cybersecurity without blurring responsibility
Request the owner’s applicable cybersecurity requirements before gateway selection and configuration. Relevant decisions may include network segmentation, disabled unused services, unique credentials, account roles, approved remote-access methods, firmware handling and logging. A gateway that bridges different protocol environments can become a consequential boundary, so its permitted traffic and management access should be documented. Security settings must be coordinated with required communications functions; disabling a service without checking its purpose can prevent intended monitoring or maintenance.
The manufacturer can review supplied requirements and document the agreed equipment configuration, but that does not by itself certify the site network or establish a cybersecurity accreditation. Identify who approves deviations, provides credentials, performs vulnerability assessment and authorizes connection to the operational network. For a quote, supply the relevant security specification and network rules early enough for compatibility review. Any unverified configuration or service should remain a planned scope item pending technical confirmation rather than being represented as an established capability.
Separate factory configuration from field integration
Factory scope may be defined around hardware mounting, internal wiring, device communications setup, gateway programming and production records, but each item requires confirmation for the specific order. Field scope may include network connection, addressing changes, integration with the owner’s supervisory system, graphics, end-to-end testing and operational acceptance. State where each task occurs, who supplies test credentials or software, and what information must be available before work begins. Do not assume shipment includes installation or field commissioning.
Useful deliverables can include an approved network diagram, device schedule, points list, interface or register map, gateway configuration record and marked-up test results, as applicable to the agreed scope. To request a quote, provide switchgear requirements, device schedules, protocol and network specifications, points list, cybersecurity rules, time-sync needs and a clear factory-versus-field responsibility matrix. New custom switchgear assemblies and American components may be considered as project requirements permit; ratings, component availability, standards, US-origin requirements and any UL 891 applicability must be confirmed for the actual order. A shorter lead time may be a goal, not a guarantee.
Specifications & planning
Review the details that matter for your application. Final specifications and availability should be confirmed for your project.
| Evaluation factor | Decision to document |
|---|---|
| Protocol path | Device protocols, direction of translation and required functions |
| Network ownership | Equipment, addressing, segmentation and connection responsibilities |
| Points and time | Point definitions, timestamp expectations and time-source responsibility |
| Scope boundary | Factory configuration, field integration, test records and acceptance owner |
