Power distribution, with purpose.
A sequence-of-events recorder (SER) helps engineers reconstruct the order and timing of electrical changes, such as breaker status transitions, protective-relay pickups, and alarms. Its usefulness depends less on the recorder alone than on selecting the right inputs, defining time synchronization, and documenting how signals reach it. For a new switchboard or switchgear design, resolve those details before the control scheme is frozen; retrofitting missed points or incompatible instrument-transformer circuits can be costly.
Start with the event questions
Define what an operator or investigator must be able to establish after an abnormal event. If the question is whether a feeder breaker opened before a bus undervoltage alarm, both signals must be captured with a common time basis and meaningful point names. A trip command, relay target, breaker auxiliary contact, and final breaker position are different events; recording only one may not show whether protection operated, the mechanism responded, or an indication failed.
Build the point list from the one-line diagram, protection and control narrative, operating procedures, and the owner’s investigation needs. Identify each input’s source, normal state, transition of interest, and destination. Include critical interlocks or transfer signals where their order affects interpretation. Avoid filling the recorder with every available contact without a purpose: excessive points can complicate commissioning, naming, review, and storage without answering the key questions.
Choose inputs and transformer interfaces deliberately
SER points are commonly binary status or alarm inputs, while analog quantities may come from a separate meter, relay, or recorder function. Confirm the proposed device’s supported input types, isolation, wetting voltage, threshold, channel count, scan or event-resolution behavior, and contact compatibility. A dry auxiliary contact, a powered control signal, and a relay output are not interchangeable. The control designer should check contact ratings and circuit supervision so the recording interface does not burden or defeat the original control function.
CTs and VTs are relevant when the design also requires current or voltage waveforms, disturbance records, or analog measurements; they are not automatically required for a binary SER. Establish whether the recorder receives secondary signals directly or through protective relays or meters, then coordinate ratios, secondary values, burden, polarity, grounding, fusing, and isolation with those devices. CT selection and circuit design require particular care because an open-circuited energized CT secondary can create a hazardous voltage. A qualified professional must determine the suitable arrangement and safe work practices.

Set timing, accuracy, and data ownership
A timestamp is only useful if its resolution and clock alignment suit the investigation. Specify the needed event time resolution, time source, synchronization protocol or hardwired signal, loss-of-sync indication, and expected behavior during a communications or power interruption. A recorder’s stated resolution does not by itself establish end-to-end timing accuracy: input filtering, contact bounce, relay output delay, network paths, and clock error can affect when an event is registered. Ask the manufacturer for applicable device data and have the engineer assess the complete chain.
Define who owns the event files and how they can be retrieved, retained, and interpreted. Specify native and export formats, point-name conventions, time-zone and daylight-saving handling, retention expectations, access permissions, and whether settings or event records are subject to the owner’s cybersecurity controls. Confirm whether data resides in the recorder, a supervisory system, or both, and who is responsible for backups. Do not assume that a communications connection means the purchaser has usable, portable records.
Use source documents to make a worked decision
The design review should draw on the one-line, AC and DC schematics, elementary diagrams, protection settings basis, equipment control-voltage requirements, relay and recorder manuals, existing point lists, and owner data-retention or network standards. Confirm which signals are available as contacts and which exist only as internal relay records. Record document revisions and identify unresolved interfaces; a vendor drawing set may not reveal owner-specific event priorities unless those are supplied.
For a hypothetical 480 V distribution lineup, suppose the owner needs to determine whether a main breaker opened before a bus undervoltage alarm and whether a feeder trip followed. The team could specify SER points for the main breaker’s open and closed auxiliary contacts, the undervoltage alarm, and the feeder trip indication, then require a common synchronized time base and named, polarity-defined inputs. If voltage magnitude and waveform behavior are also needed, the team would separately evaluate relay disturbance records or suitable voltage measurement inputs. This example is not a customer project or a final design; the actual point selection and performance criteria require engineering review.
Compare architectures and preserve evidence
A dedicated SER can centralize event capture and provide a consistent point list, but it adds device, wiring, configuration, and maintenance interfaces. Using protective-relay event records may reduce separate hardware and can capture relay-specific logic, yet coverage and time alignment can vary by relay model and settings. A supervisory control system may offer convenient history, but polling intervals, communications interruptions, and timestamping behavior can make it unsuitable for resolving closely spaced changes. Compare demonstrated event capture and retrieval needs, not just device counts.
Require records that let reviewers verify what was built and configured. The submittal and closeout package should identify the recorder model and applicable data, point schedule, input circuit drawings, CT/VT interface details where used, time-synchronization architecture, communications and data format, settings responsibility, and approved revisions. Commissioning documentation should show which points were functionally checked and how timestamp alignment and data retrieval were verified, without treating a successful display test as proof of every protection function.
Define the quote scope and the limits
For a quote on new equipment, provide the one-line and control schematics, system nominal voltage and applicable equipment ratings, desired event points, control power, required CT/VT interfaces, time-source and network requirements, data ownership rules, and preferred recorder or relay information if specified. State whether the scope includes devices, wiring, programming, drawings, testing documentation, or only the assembly. A manufacturer can review the proposed build and available components; ratings, short-circuit duty, component availability, applicable standards, and any U.S.-origin requirement must be confirmed for the specific order. UL 891 applies to low-voltage switchboards where applicable, not to medium-voltage switchgear generally.
The design conclusion remains limited until qualified professionals verify the actual signal sources, device capabilities, coordination, timing performance, code interpretation, and owner requirements. Final settings, work practices, and acceptance criteria belong to the responsible engineering and operations teams. For projects in Dallas–Fort Worth or elsewhere, a clear, revision-controlled specification helps the equipment manufacturer evaluate interfaces and pursue a shorter lead time as a goal, without implying a guaranteed schedule or that the manufacturer performs installation.
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 |
|---|---|
| Event points | Source contact or signal, normal state, and transition of interest |
| Time alignment | Required resolution, synchronization source, and loss-of-sync behavior |
| Measurement interface | Whether CT/VT signals are needed and how secondary circuits are coordinated |
| Data and records | Ownership, export format, retention, point names, and verification documents |
