TECHNICAL GUIDES / MANUFACTURER DIRECT
An alarm and status point list translates operating needs into signals a control system can display, record, or act on. For a new switchgear package, agreeing on the list early helps coordinate switchboard design, protective relays, metering, communications, and the receiving control system. Switchgear Builder Virginia can build custom equipment for projects nationwide; point availability, component selection, protocols, and schedules must be confirmed during quoting and engineering. Treat the list as a project document, not a universal standard: define each point’s meaning, source, destination, and acceptance method with the responsible project teams.
Start With Operations
Organize points around the decisions operators need to make, rather than copying a generic alarm template. For each power source, identify the conditions that matter, such as source available, source connected, or source abnormal, and clarify whether each is an alarm, a status indication, or both. For each breaker, specify the required open and closed indications and whether a separate trip indication is needed. Those signals are not interchangeable: a trip reports an event or condition, while open describes position. Include the intended display, historian, or supervisory system and the party responsible for interpreting the point. Ask operations, controls, protection, and commissioning representatives to review the draft together. Their agreement can expose missing information before wiring and interface details become difficult to change. Confirm all device capabilities against the selected equipment and project documents.
Define Every Point
Give every entry a unique tag and a plain-language description that says what the signal means. Record its equipment source, destination, normal state, alarm priority if applicable, and any delay or latching behavior the project requires. State whether the point is a discrete indication, an analog value, or a calculated condition; do not leave the receiving controls team to infer the distinction. For contacts, specify whether the interface requires normally open or normally closed behavior, and define the state represented when the monitored device is healthy. Also document how loss of control power, a broken wire, or an unavailable device should appear, where the selected design supports that distinction. These details influence relay configuration, terminal allocation, and control wiring. Confirm signal polarity and fail-state conventions with the controls designer before the list becomes an approved design input.
Choose the Interface
Separate hardwired points from data communicated over a network, then identify the required interface for each group. A hardwired contact can provide a direct discrete indication, but adds terminals, conductors, and point-to-point wiring that must be coordinated. A communications link can carry multiple values through one connection, yet depends on compatible devices, agreed data mapping, and network integration. List the protocol only when the project team has selected and verified it; protocol names alone do not establish interoperability. Specify who supplies and configures gateways, network switches, addressing, and supervisory-system drivers, if those items are in scope. Identify which values must remain available if communications fail and whether a hardwired backup is required. The equipment manufacturer should confirm the selected relays and meters support the requested points and interfaces. Final selections, ratings, and responsibilities belong in the approved submittal and project documents.
Cover Protection Signals
Coordinate protective-relay points with the protection study, relay settings, and approved control narrative. Typical items to evaluate include relay alarm, trip output, protective element operation, lockout status, and relay self-supervision; the project may need only a subset. Name each protection function in terms the operator can understand, while retaining the relay’s exact element or event identifier in the technical record. Clarify whether a relay event is a momentary pulse, a maintained contact, or a network-reported value, and define any reset or acknowledgment expectations. Do not treat a broad “relay alarm” as a substitute for a specific trip or device-failure indication when those distinctions matter to response. The protection engineer should approve the requested points and confirm that their implementation does not alter approved protection behavior. Availability and contact behavior depend on the selected relay and its configured scheme.
Set Acceptance Criteria
Define acceptance before testing begins: identify who checks each point, what equipment or simulator establishes its state, where the indication must appear, and what evidence closes the test. A useful criterion names the expected change—for example, a designated breaker-position input changes the corresponding control-system indication—without prescribing unsafe field operations. Include alarm text, priority, time stamping, event recording, and communication-loss behavior when required by the project. Record exceptions, unresolved mappings, and approved revisions in the point list so the field team does not rely on informal markups. Review the final list against drawings, relay schedules, terminal plans, and control-system databases. For a new custom switchboard, Switchgear Builder Virginia can coordinate documented point requirements with the quoted assembly scope. Specific points, component capabilities, inspections, tests, and acceptance responsibilities remain subject to project documents and verification; agree on them before release for manufacture.
