Define What Operators Need to Know

Remote indication and alarms extend switchgear status beyond the equipment lineup, helping operators distinguish a condition requiring attention from routine operation. Begin by identifying who will receive each signal and what decision they must make: investigate a trip, respond to an abnormal measurement, or confirm that a device changed state. The equipment design should follow those operational needs rather than a generic list of available points.

For new switchgear, create a point schedule that names each condition, its normal and alarm state, priority, and intended destination. Separate alarms that require prompt action from status indications used for monitoring or records. Confirm whether signals are needed continuously, only during selected operating modes, or after a defined event. Qualified electrical and controls professionals should review the proposed points against the system design and operating procedures.

Select Alarm Conditions and Sources

Potential indications may include protective-device operation, abnormal measured values, equipment status, or a control-system fault, but the points depend on the selected devices and project configuration. Do not assume every condition is sensed or available as an output. For each requested alarm, identify its source, the device or measurement that establishes it, and whether the signal represents a commanded state, an actual state, or a calculated threshold.

Set alarm thresholds, delays, latching behavior, reset method, and priority with the responsible controls and protection teams. Consider normal operating variation and the consequences of nuisance alarms or missed events. Document which values are measured locally, which are transmitted, and whether alarm processing occurs in switchgear controls or a separate supervisory system. Device selection, ratings, and applicable standards must be verified for the specific assembly and application; no single capability should be presumed.

Specify Contacts and Signal Interfaces

A dry contact, powered output, network point, or other interface may be appropriate depending on the equipment and receiving system. Confirm the receiving input requirements, including signal type, electrical characteristics, isolation, wiring method, and any required supervision. Check whether contacts need to be normally open or normally closed, and define the state represented by loss of control power or a broken circuit. These choices affect both the equipment design and how the receiving system interprets a fault.

Identify ownership at each interface: which party supplies field wiring, terminal blocks, interposing devices, control power, and network configuration. Agree on terminal naming, point identifiers, wire references, and available space for conductors during design review. If communications are proposed, confirm protocol, addressing, data mapping, cybersecurity requirements, and responsibility for configuration with the controls integrator. Do not assume a particular protocol, contact capacity, or communications feature until it is confirmed for the selected equipment and project.

Choose Destinations and Alarm Handling

List each destination explicitly, such as a building automation system, plant control system, remote annunciator, or operator workstation, only where that destination is part of the project. For every point, record whether it is a local indication, a remote alarm, an event record, or more than one of these. Confirm who receives notifications, how alarms are acknowledged, and whether an alarm remains active until the condition clears or requires a separate reset.

Define behavior during loss of communications, loss of control power, or a receiving-system outage. The project team should determine whether local indication remains necessary and how operators learn that remote reporting is unavailable. Establish priorities and naming conventions that fit the destination's alarm management practices, and avoid duplicating routine status as urgent alarms. These decisions should be coordinated across the switchgear specification, controls narrative, point list, and operating documentation so that the same condition is described consistently.

Coordinate Drawings, Documents, and Verification

Controls, metering, and documents should be developed together. Useful inputs include one-line and control diagrams, device schedules, metering requirements, operating sequences, interface specifications, and the receiving system's point list. Review the alarm schedule against the proposed equipment and identify points that require added devices, wiring, or engineering. Resolve naming, terminal references, signal states, and responsibility boundaries before drawings are released for production.

Plan verification around the agreed point list and interfaces. Where included in the project scope, checks can confirm that each documented input changes the intended indication, reaches the correct destination, and displays the approved text and priority. Define who witnesses or records checks and what test access or simulated inputs are permitted. Testing arrangements must be coordinated with qualified personnel and site procedures; they do not replace review of protective settings or authorization by relevant authorities.

Prepare a Clear Procurement Package

When requesting new switchgear with remote indication and alarms, provide the point schedule, destination list, interface requirements, alarm priorities, desired operating behavior, and relevant control and metering documents. Include known receiving-system constraints and identify unresolved decisions rather than leaving them implicit. Ask for the proposed points and interfaces to be reviewed against the selected equipment, with exceptions or assumptions clearly identified before approval.

For Austin and Central Texas projects, coordinate submittal reviews, delivery planning, and receiving-system integration around the site schedule; nationwide shipment is also available. The manufacturer builds in the USA using all-American components and can develop custom assemblies to specification. Lead time depends on the project, so confirm it after requirements are reviewed. Before release, have qualified electrical and controls professionals check ratings, design details, applicable standards, documentation, and authority requirements for the particular application.

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
Alarm point scheduleConfirm each condition, source, normal state, alarm state, priority, delay, latch, and reset behavior.
Contact and signal interfaceSpecify signal type, electrical characteristics, isolation, terminal references, and receiving-input requirements.
Destinations and ownershipName each receiving system and define wiring, control power, configuration, acknowledgement, and notification responsibilities.
Communications requirementsWhere used, confirm protocol, data mapping, addressing, cybersecurity criteria, and integration responsibility.
Drawings and verificationCoordinate point lists, control diagrams, operating sequences, test scope, records, and responsible reviewers.