TECHNICAL GUIDES / MANUFACTURER DIRECT
Meter data integration starts with a clear agreement about what each meter measures, how readings travel, and who may use the resulting data. For a new switchgear project, these decisions can affect meter selection, control wiring, communications hardware, and coordination with a building or utility system. Switchgear Builder Virginia can provide custom-built equipment with meter features considered as project requirements; available functions, interfaces, and ratings must be verified for the quoted design. Define the data need before specifying the meter, then confirm compatibility with the intended receiving system.
Define the Measurements
List the values the project actually needs before selecting meter features. Energy readings may be required as accumulated kilowatt-hours, while demand may mean present demand, a rolling interval, or a maximum retained over a billing period. Those are not interchangeable. Specify whether the system needs real and reactive power, voltage, current, power factor, frequency, or per-phase values, and whether readings are needed for each feeder, a main, or both. Identify the expected units, sign convention, circuit names, and whether values must be displayed locally, exported, or both. A concise point list helps prevent a meter from being specified by a broad label such as “power monitoring” that leaves key functions unclear. Confirm which points are available from the selected meter and which require compatible sensing, wiring, configuration, or additional equipment. Treat every feature as subject to project verification.
Choose the Data Path
Name the receiving system and its communication requirements before choosing a protocol. A meter may offer one or more wired or network interfaces, but a shared protocol name alone does not establish that the meter and receiver will exchange every required value. Confirm supported protocol options, physical connection, addressing, data map, register format, scaling, and any required gateway or network configuration. Also decide whether the meter reports to a building management system, an energy platform, a supervisory system, or more than one destination. Each path can introduce different configuration and cybersecurity responsibilities. For a switchboard package, document where communication wiring terminates and which party supplies, configures, and tests equipment outside the switchboard. Do not assume an existing network, gateway, or software license is included. Verify the selected meter’s documented capabilities and the receiving system’s compatibility during design review and quotation.
Set Time Requirements
Timestamp expectations should match how the data will be used. A dashboard that shows current readings may have different needs from billing review, interval comparisons, or event analysis. Specify the required interval, the acceptable time basis, and whether readings must carry a timestamp at the meter or receive one in the monitoring platform. Clarify how the system handles daylight-saving changes, time-zone display, clock synchronization, and a loss of communications. These details matter when teams compare meter records with reports from other systems; mismatched clocks can make otherwise valid readings difficult to reconcile. Ask whether the selected meter stores interval history and event records, how much data it can retain, and what happens when communications are interrupted. Storage duration and clock functions vary by device and configuration, so they should be checked against the project requirement rather than assumed from the word “meter.”
Assign Data Ownership
Decide who owns the data, who can access it, and who maintains the connection after handover. The owner may require direct access to readings, while an integrator or service provider may configure the receiving platform. Record responsibility for meter setup, point naming, network addressing, credential management, data mapping, and ongoing software or gateway support. Clarify whether data is stored locally, in an owner-managed system, or through a separate hosted service; do not presume a meter package includes cloud storage or a monitoring subscription. Establish who may change settings and how configuration records will be delivered to the owner. For systems connected to an operational network, have the responsible parties review access and cybersecurity requirements through their approved process. These ownership decisions are separate from the electrical design, but they influence communications choices and commissioning scope. Put them in the project documents so that access and support do not remain ambiguous at turnover.
Verify Before Release
Before equipment release, compare the meter schedule and integration point list against the quoted configuration. Confirm the selected meter, sensing arrangement, required options, interface, protocol, and any gateway or communications components; then verify the receiver can interpret the specified values and data formats. Assign responsibility for supplying external network connections, configuring the receiving system, and performing any end-to-end checks. If testing is required, define its scope, participants, prerequisites, and acceptance records in the project documents rather than assuming a particular test is included. Review the switchboard drawings for meter locations, circuit identification, and communication termination details, and resolve conflicts before approval. Switchgear Builder Virginia manufactures new custom equipment in the United States using all-American components and ships nationwide; schedules and design details are subject to quotation and verification. For applicable low-voltage switchboard assemblies, UL 891 requirements may apply; confirm applicability and the specified configuration for the project.
