Power distribution, with purpose.
Event records are useful only when their timestamps let operators reconstruct what happened across relays, meters, control systems, and breakers. A time-synchronization design therefore needs more than a protocol name: it must identify the authoritative clock, show how time reaches each device, and state what the system does when that source or path fails. For a new distribution assembly, define those decisions alongside the protection and control requirements, then verify actual device capabilities before specifying settings.
Start with the event record you need
First establish which records must be compared and how closely their timestamps need to align. A breaker trip, protective-relay target, meter disturbance record, and supervisory-control alarm may be created by different devices with different clock resolution and timestamp behavior. Ask whether the purpose is sequence-of-events reconstruction, fault analysis, routine trending, or a combination. Those uses can call for different accuracy, retention, and time-quality requirements; a display showing the correct local time does not by itself prove that event timestamps are sufficiently aligned.
Gather the proposed device schedule, relay and meter models, control-system architecture, event-record formats, expected time zone, daylight-saving policy, and any required accuracy or traceability criteria. Determine whether timestamps are generated at the device, at a gateway, or when data is received. That distinction matters when communications are delayed or interrupted. In a Dallas–Fort Worth facility or a remotely monitored installation, the same design questions apply: define the records and operational use rather than assuming geographic location determines the right clock architecture.
Choose an authoritative source and define its states
The specification should name the intended source of time and its relationship to any upstream reference, such as a site master clock or a network time service. Record whether the source is expected to be synchronized, in holdover, unsynchronized, or unavailable, and how its time-quality state is conveyed. A source can continue producing timestamps after losing its reference, but those timestamps may drift. The design should distinguish a valid-looking time value from a time value whose synchronization status is known.
Compare source options against the installation’s communications and resilience needs. A dedicated clock with a suitable antenna path may offer independence from a facility data network, while a network-based source may fit an established, managed infrastructure. Neither is automatically preferable: review coverage, security controls, redundancy, maintenance responsibility, and behavior during loss of the upstream reference. Specify how a source change is authorized and logged, and avoid silent switching between clocks whose time offsets or quality states are unknown.

Specify interfaces and hardwired status logic
List every receiving device and the interface it can actually use. Depending on the selected equipment, synchronization may use a network protocol, a serial interface, or a hardwired pulse or contact arrangement. Confirm protocol support, configuration limits, port availability, wiring requirements, and whether a device reports synchronization quality. A gateway may translate or distribute time, but it can also add another point of failure or obscure the original source state if the design does not preserve status information.
Hardwired logic can provide a clear alarm or inhibit signal for a source failure, but its meaning must be unambiguous. Define normal and abnormal contact states, loss-of-power behavior, supervision where required, and the destination of each indication. Decide whether loss of synchronization raises an alarm only, marks subsequent records as degraded, or invokes another approved response. Do not assume a dry contact is a time signal, or that a device’s communication interface carries a trustworthy quality indication; verify both in the applicable manufacturer documentation and project design.
Work through a hypothetical loss-of-source decision
Consider a hypothetical lineup with protective relays that record trip events and a control-system gateway that collects alarms. The project requires comparison of relay events with gateway alarms, and the selected source normally distributes time over the site network. During an outage of that network, relay clocks may continue on local holdover while the gateway stops receiving updates. The design team must decide whether the relays retain timestamps with a degraded-quality indication, whether the gateway records its own synchronization loss, and how operators can identify the interval affected.
One option is to keep local clocks running and flag records as unsynchronized; this preserves chronology but leaves increasing uncertainty about absolute alignment. Another is to suppress or mark timestamps after a defined loss interval, which may avoid false precision but reduce immediate diagnostic value. A redundant source can improve continuity, yet only if switching rules, source agreement, and status reporting are verified. The hypothetical decision is to retain records, alarm on loss, and expose quality status, subject to device capability and engineering review—not to claim that any particular relay implements that behavior.
Compare tradeoffs and document the design
Evaluate options by end-to-end performance, not merely by the clock’s stated accuracy. The relevant path includes the reference, distribution network or wiring, gateways, receiving-device clocks, event timestamp resolution, and record export. Network synchronization can simplify distribution but depends on configuration and network behavior. Dedicated wiring may be easier to isolate but adds conductors, terminals, and supervision needs. Redundancy can increase availability while creating new risks if two sources disagree or failover is not visible to operators.
Show the source, distribution paths, interfaces, and receiving devices on control schematics or network drawings, and identify associated terminals, cables, ports, and alarms. Preserve the selected time zone and daylight-saving convention, device configuration references, source-quality definitions, failover logic, and commissioning evidence in project records. Commissioning should verify the intended indication and record behavior under approved test conditions; qualified professionals must determine safe work practices, final settings, and applicable code interpretation.
Supply project inputs and keep the conclusion bounded
For a quote on a new custom-built assembly, provide the one-line diagram, equipment scope, device schedule, control schematics or network requirements, preferred time source and interfaces, event-record objectives, alarm points, and any documented accuracy or availability criteria. Identify required components, preferred American components where applicable, enclosure and shipping constraints, and the project schedule. The manufacturer can assess the proposed assembly scope and work toward a shorter lead time, but component availability and timing must be confirmed for the specific order.
A time-synchronization concept is not proof that every relay, meter, gateway, or external network will meet the project’s needs. Confirm model-specific capabilities, ratings, communications compatibility, short-circuit requirements for the assembly, applicable standards, and any U.S.-origin requirements before release. UL 891 may apply to a low-voltage switchboard assembly when appropriate, but it does not establish time accuracy and is not a general designation for medium-voltage gear. Final conclusions require review of the actual equipment, system architecture, and governing project requirements.
Specifications & planning
Review the details that matter for your application. Final specifications and availability should be confirmed for your project.
| Evaluation factor | What to establish |
|---|---|
| Time source | Authority, upstream reference, quality states, and loss indication |
| Receiving devices | Supported interface, timestamp resolution, and quality reporting |
| Failure behavior | Holdover, alarm or record marking, and approved fallback response |
| Design evidence | Drawings, configuration references, and commissioning records |
