AGL Component Library By Precision AGL Academy

Time Synchronization / NTP Module

A dedicated precision timekeeping device that provides accurate, synchronized time to all AGL system components — including the ALCMS server, PLCs, workstations, and network equipment. The Time Synchronization / NTP Module ensures consistent timestamps across all system events, alarms, and data logs, enabling precise sequence-of-events (SOE) analysis, forensic investigation, and coordinated system responses.

Time Synchronization / NTP Module

Image disclaimer: For identification and illustration only. It may show a product by another manufacturer and may not depict the exact item described; it is not a statement of any product’s quality, approval or performance. Third-party image and trademark rights belong to their owners. See full notice.

Overview

What Is It?

A Time Synchronization / NTP Module — also referred to as a network time server, NTP server, or GPS time server — is a dedicated device that distributes highly accurate, synchronized time to all network-connected devices in an AGL system. It acts as the authoritative time source for the ALCMS, PLCs, workstations, communication gateways, and any other equipment that requires accurate timekeeping for event logging, alarm correlation, and coordinated control.

Key characteristics of the Time Synchronization / NTP Module include:

  • High-Precision Time Source: Typically synchronizes to an external reference such as GPS, GNSS (GLONASS, Galileo, BeiDou), or a high-accuracy internal oscillator (rubidium or OCXO) for autonomous operation during signal loss.
  • Network Time Protocol (NTP) Server: Provides NTP (and optionally PTP — Precision Time Protocol) services to all network clients, ensuring time accuracy typically within 1–10 ms over the network.
  • Multiple Output Formats: Supports various time distribution formats including NTP, PTP (IEEE 1588), SNTP, and hardware pulse-per-second (PPS) outputs for high-precision applications.
  • Redundant Time Sources: Supports multiple GPS/GNSS inputs, external NTP peers, and internal holdover oscillators to ensure continuous time availability even in the event of a primary reference loss.
  • Holdover Accuracy: Maintains accurate time for extended periods (hours to days) when the external reference is lost, using a high-stability oscillator (TCXO, OCXO, or rubidium).
  • Web-Based Management: Provides an intuitive web interface for configuration, status monitoring, and diagnostics, including time source status, client statistics, and alarm logging.
  • Secure Operation: Supports authentication (NTS — Network Time Security) and access control to prevent unauthorized time manipulation, protecting against cyber threats and ensuring time integrity.

In airfield lighting systems, the Time Synchronization / NTP Module is essential for correlating events across the entire AGL infrastructure. When a fault occurs (e.g., a CCR failure, lamp outage, or communication loss), the precise timestamps from all devices enable operators and maintenance teams to reconstruct the sequence of events accurately, identify root causes, and take corrective action efficiently.

Purpose

Purpose & Function

The time synchronisation module's purpose is to extend a single accurate time reference out to every device on the network, so that the value of precise timing isn't limited to whichever equipment happens to have its own GPS antenna. A CCR controller, a PLC, an operator workstation, and a network switch all need to agree on the same time down to a few milliseconds if their combined logs are ever going to be read as one coherent story rather than several separately-plausible ones. The redundancy and holdover capability matter for a specific reason: if the network's shared time reference were to silently drift during a brief GPS outage, every downstream device would drift with it without any obvious warning, quietly undermining the very event correlation the whole system depends on — so the module's job is keeping that shared, trustworthy "now" available continuously, not just most of the time.

Application

Where Is It Used?

The Time Synchronization / NTP Module is deployed in all AGL systems where accurate, synchronized time is critical for operations, maintenance, and safety. Key applications include:

  • ALCMS Server Time Synchronization: Providing the authoritative time source for the ALCMS server, ensuring that all alarms, events, and operator actions are timestamped consistently.
  • PLC and Remote I/O Synchronization: Synchronizing PLCs and remote I/O units to ensure that control actions and status changes are logged with accurate timestamps, enabling precise sequence-of-events (SOE) recording.
  • Workstation and Operator Console Time: Ensuring that all operator workstations and control panels display the same, correct time, improving situational awareness and audit traceability.
  • CCR Communication Interfaces: Synchronizing CCR communication interfaces to accurately timestamp status changes and alarms from Constant Current Regulators.
  • Network Equipment Synchronization: Providing time to Ethernet switches, communication gateways, and fiber converters for accurate network event logging and troubleshooting.
  • SCADA Integration: Providing synchronized time to SCADA systems that interface with the AGL system, ensuring that data from multiple sources is time-aligned.
  • Sequence-of-Events (SOE) Logging: Enabling precise timestamping of SOE data, which is critical for fault analysis, post-incident investigation, and compliance reporting.
  • Approach Lighting Sequencers: Synchronizing sequenced flashing lights and approach lighting systems to ensure precise timing and coordinated operation.
  • RWSL (Runway Status Light) Systems: Providing accurate time for RWSL control logic, ensuring that light state changes occur at precisely the right moments during aircraft movements.
Placement

Installation & Location

The module is rack-mounted in the main equipment room alongside the ALCMS server and core network switches, positioned so its network connection reaches the core switch or router with the shortest possible hop count to the devices it serves. Its GPS or GNSS antenna is a separate component, mounted outdoors with a clear view of the sky — typically on the equipment shelter roof or a nearby mast — and connected back to the module by a dedicated coaxial or fibre antenna cable run in its own conduit, kept short enough to avoid excessive signal loss and separated from AGL power cabling to limit interference. Where a second GNSS input or external NTP peer is used for redundancy, that reference is fed from a physically independent antenna or network path so that a single antenna fault, cable cut, or lightning strike cannot take down both time sources at once. The module's own power feed is typically drawn from the same UPS-protected circuit as the ALCMS server, so a mains interruption does not itself introduce a gap in the time reference the rest of the system depends on.

Function

How Does It Work?

The Time Synchronization / NTP Module operates as a precision time source and distribution hub, ensuring that all AGL system components are synchronized to a common time reference. Key functional aspects include:

  • External Time Reference Reception: The module receives accurate time from an external reference, typically a GPS or GNSS receiver. The GPS/GNSS signal provides Coordinated Universal Time (UTC) with sub-microsecond accuracy. The module decodes the time, date, and position data from the satellite signals.
  • Internal Oscillator and Holdover: The module uses a high-stability oscillator (TCXO, OCXO, or rubidium) to maintain accurate time when the external reference is lost. The oscillator is disciplined (slewed) to the external reference during normal operation, ensuring that the holdover accuracy remains within specification (e.g., better than 1 µs per hour).
  • Time Processing and Distribution: The module processes the time reference and makes it available to network clients via NTP (Network Time Protocol) and/or PTP (Precision Time Protocol). It responds to client requests with the current time, adjusting for network latency using sophisticated algorithms.
  • Hardware Time Stamping: Advanced modules include hardware timestamping capabilities (e.g., on the Ethernet PHY) to achieve sub-microsecond accuracy for PTP and NTP with hardware-assisted synchronization.
  • Pulse-Per-Second (PPS) Output: The module provides a hardware pulse-per-second (PPS) output, which can be used by devices that require a precise second-edge synchronization (e.g., PLCs, RTUs, and data acquisition systems).
  • Time Zone and Daylight Saving Management: The module applies the configured time zone and daylight saving rules, distributing the local time to clients as required. It also provides UTC time for applications that require a standardized reference.
  • Client Monitoring and Authentication: The module logs all NTP/PTP client requests, allowing administrators to monitor which devices are synchronized and at what accuracy. It supports authentication mechanisms (NTS, MD5, or symmetric keys) to prevent unauthorized time manipulation.
  • Redundancy and Failover: In critical installations, multiple time servers are deployed in a primary/backup configuration. The module supports peer-to-peer synchronization with other NTP servers, ensuring that a single point of failure does not compromise time accuracy.

The module is typically rack-mounted (19" 1U) and powered from a 120/230 VAC supply with redundant power inputs for high availability. It includes a front-panel display for status indication (time source, synchronization status, alarms) and may include a GPS antenna input (with surge protection) for outdoor antenna installation.

Visual Overview

One Clock, Every Device & Control Logic

GPS / GNSS Receiver

UTC from satellites, sub-µs accuracy

Internal Oscillator

OCXO/rubidium — disciplined during lock, holds over on loss

Time Processing & Distribution

Serves NTP, PTP & SNTP; applies time zone / DST rules

ALCMS Server

Alarm & event timestamps

PLCs & Remote I/O

Sequence-of-events logging

CCR Interfaces

Status change timestamps

Network Equipment

Switches & gateways

...plus workstations, SCADA, approach light sequencers & RWSL control logic
A hardware PPS output gives devices needing second-edge precision (PLCs, RTUs) a signal separate from the NTP/PTP feed.
NTS authentication and access control prevent unauthorised clients from manipulating the distributed time.
Construction

Physical Construction

The module is built as a rack-mount (typically 1U) or DIN-rail chassis housing the timing electronics, an internal oscillator (often an oven-controlled crystal for holdover stability), and a GPS/GNSS receiver board connected to an external roof- or mast-mounted antenna via a dedicated coaxial feed with surge protection at the entry point. Network connectivity is brought out through standard RJ45 or fibre ports on the rear panel alongside the antenna connector and a power inlet, with the unit designed to sit in the same equipment room or cabinet as the ALCMS servers and PLCs it serves rather than in an outdoor enclosure. A front-panel display or status LEDs indicate GPS lock and synchronisation state, and internal battery backup for the real-time clock maintains reasonable timekeeping accuracy through short power interruptions or antenna signal loss.

Specification

Technical Parameters

ParameterTypical Value
Time SourceGPS / GNSS (GLONASS, Galileo, BeiDou) — multi-constellation receiver
Antenna Input50 Ω, SMA or TNC connector, with 5 VDC antenna power, surge protected
Network Interface1–2 x 10/100/1000BASE‑T (RJ‑45) — optional fiber SFP
Protocol SupportNTP (RFC 5905), SNTP (RFC 4330), PTP (IEEE 1588), Daytime (RFC 867), Time (RFC 868)
NTP Accuracy (LAN)±1–10 ms (typical), ±100 µs (with hardware timestamping)
PTP Accuracy (LAN)±100 ns (with hardware timestamping)
Holdover Accuracy±1 µs per hour (OCXO), ±1 ms per day (TCXO), ±1 µs per day (rubidium)
PPS Output1 x BNC (pulse-per-second, TTL level)
Time DisplayFront-panel OLED or LCD display (time, date, source status, alarms)
Number of NTP Clients SupportedUp to 10,000+ (depending on model and network load)
AuthenticationNTS (Network Time Security), MD5/SHA symmetric keys, access control lists (ACL)
Management InterfaceWeb GUI (HTTPS), SSH, SNMP (v2c/v3), syslog
RedundancyDual power inputs (hot‑swappable), redundant GPS/GNSS receivers (optional), NTP peer sync
Power Supply120/230 VAC ±10%, 50/60 Hz (dual redundant, hot‑swappable)
Power Consumption15‑40 W (depending on model and options)
Operating Temperature-10°C to +55°C (industrial grade), -40°C to +70°C (ruggedized option)
Storage Temperature-40°C to +85°C
Protection ClassIP20 (indoor rack‑mount), IP54 (with optional enclosure)
Mounting19" rack‑mount (1U or 2U), or DIN rail (compact models)
Dimensions (1U)482.6mm × 44.5mm × 300mm (W × H × D)
CertificationsCE, FCC, UL, IEC 61000‑6‑2 (EMC immunity), NIST (time source traceability)
Power Supply

Electrical Requirements

RequirementTypical Value
Circuit TypeEquipment-room/control-room low-power supply, independent of the airfield series lighting circuit
Supply Voltage120/230V AC ±10%, 50/60 Hz, dual redundant hot-swappable inputs
Antenna Power5V DC supplied over the antenna cable, surge protected at the module input
Backup SupplyDual power inputs allow feed from separate UPS-backed circuits for redundancy
Cable TypeScreened antenna coax and network cabling, routed separately from AC power wiring
Earthing/GroundingChassis and antenna cable shield bonded to the equipment-room earth
Fault ProtectionSurge protection on antenna and network inputs; loss-of-source and power-input-failure reported via SNMP/alarm output
Compliance

Applicable Standards

RFC 5905

Network Time Protocol (NTP) — core specification for time synchronization over IP networks

IEEE 1588

Precision Time Protocol (PTP) — high-precision time synchronization for industrial networks

IEC 61850

Communication networks for power utility automation — includes time synchronization requirements

FAA AC 150/5345‑56

Specification for AGL control and monitoring equipment (time synchronization requirements)

Prerequisites

Installation Requirements

Rack Mounting in Equipment Room
Civil

Rack-mount the module in the main equipment room alongside the ALCMS server and core network switches, positioned for the shortest possible hop count to the devices it serves.

Antenna Siting with Clear Sky View
Civil

Mount the GPS/GNSS antenna outdoors with a clear view of the sky — typically on the equipment shelter roof or a nearby mast — where it will not be shadowed by structures or vegetation.

Antenna Cable Routing
Electrical

Run the coaxial or fibre antenna cable in its own conduit, kept as short as practical to avoid excessive signal loss and separated from AGL power cabling to limit interference.

Redundant Reference Independence
Electrical

Where a second GNSS input or external NTP peer provides redundancy, feed it from a physically independent antenna or network path so a single antenna fault, cable cut, or lightning strike cannot take down both time sources at once.

Network Connection to Core Switch
Electrical

Connect the module's network interface to the core switch or router serving the ALCMS and dependent devices.

UPS-Protected Power Feed
Electrical

Draw the module's power feed from the same UPS-protected circuit as the ALCMS server, so a mains interruption does not itself introduce a gap in the time reference.

Lightning Protection Check
Mechanical

Confirm the antenna cable run includes appropriate surge/lightning protection at the building entry point, given its outdoor, elevated antenna position.

Pre-Commissioning Sign-off
Documentation

Record rack position, antenna location and cable route, network connection, and power feed as-built before the installation is closed out.

Verification

Testing & Commissioning

Time Source & Accuracy Verification
Energisation

Confirm the module synchronises to its reference time source (GPS, upstream NTP/PTP server) and holds accuracy within the specified tolerance.

Network Connectivity Test
Energisation

Verify the module's network interface reaches all client devices on the AGL monitoring network and responds to time requests.

Failover & Holdover Test
Energisation

Disconnect the primary time reference and confirm the module correctly enters holdover mode and reports the resulting alarm.

Insulation Resistance Test
Pre-Energisation

Megger-test power and network wiring to the module before energisation, confirming insulation resistance clears the acceptable minimum.

Client Synchronisation Check
Final Acceptance

Confirm downstream CCR monitors, panels, and logging systems show correctly synchronised timestamps after commissioning.

Documentation & As-Built Sign-off
Final Acceptance

Record accuracy, failover, and client synchronisation results in the commissioning dossier for handover.

Upkeep

Inspection & Maintenance

GPS/GNSS Antenna & Feedline Check
Annual

Inspect the antenna, feedline, and surge protector for corrosion or moisture ingress, since a degraded feed forces the module into holdover.

Time Accuracy Verification
Semi-annual

Confirm NTP/PTP output accuracy against a traceable reference to catch oscillator drift before it affects downstream event timestamps.

Holdover Performance Test
Annual

Simulate a GNSS signal loss to confirm the internal oscillator holds accuracy within spec for the expected outage duration.

Redundant Power & GNSS Receiver Test
Semi-annual

Remove each hot-swappable power input in turn, and where fitted, confirm the redundant GNSS receiver takes over cleanly.

Authentication & Access Review
Annual

Verify NTS or symmetric-key authentication and access control lists remain correctly configured to prevent time-source spoofing.

NTP Client Load Review
Quarterly

Check active client count and query load against the rated capacity so the module doesn't degrade in accuracy under peak demand.

Firmware & Log Review
Semi-annual

Check for validated firmware updates and review syslog and SNMP alarms for recurring synchronisation errors.

Display & Alarm Function Test
Quarterly

Confirm the front-panel display shows correct time, date, and source status, and that alarms trigger correctly on a simulated source failure.

Field Notes

Common Field Issues

GPS/GNSS Signal Loss

GPS signal loss can occur due to antenna obstruction, cable degradation, or atmospheric conditions. When the primary time reference is lost, the module enters holdover mode. Ensure the antenna has a clear view of the sky, use high-quality low-loss coaxial cable, and verify the module's holdover accuracy meets the application's requirements. Consider using redundant GPS/GNSS receivers or a secondary time source (e.g., a cellular network time source).

Network Congestion and NTP Latency

Heavy network traffic can introduce latency and jitter, affecting NTP accuracy. Use dedicated VLANs for time synchronization traffic, prioritize NTP packets using QoS, and ensure that the network infrastructure supports hardware timestamping (e.g., PTP) for high-precision applications. Monitor NTP client offsets and adjust poll intervals to optimize performance.

Time Zone and Daylight Saving Misconfiguration

Incorrect time zone or daylight saving settings can cause timestamps to be off by an hour or more. This can affect event correlation and compliance logging. Always verify the time zone and daylight saving rules during commissioning. Use UTC for internal logging and apply the local time zone only for user display.

Antenna Cable Degradation

GPS antenna cables exposed to weather can degrade over time, leading to signal attenuation and loss of synchronization. Use high-quality, low-loss cable (e.g., LMR-400 or equivalent) with proper weatherproofing. Periodically check the cable for damage and replace it if the signal strength drops below the specified threshold.

Security Vulnerabilities (NTP Amplification)

NTP servers can be used in DDoS amplification attacks if not properly secured. Restrict NTP access to authorized clients using access control lists (ACLs). Enable NTS (Network Time Security) or symmetric key authentication to prevent unauthorized time manipulation. Regularly update the firmware to patch known vulnerabilities.

Holdover Time Exhaustion

If the module operates in holdover mode for an extended period (e.g., days or weeks), the time error may accumulate and exceed the acceptable tolerance. Monitor the holdover duration and accuracy, and consider installing a secondary time source (e.g., a second GPS receiver or a cellular time service) to provide redundancy.

Software Version Incompatibility

Mixing NTP/PTP clients with different software versions or operating systems can cause interoperability issues. Ensure all clients are using a compatible NTP implementation (e.g., ntpd, chrony, or Windows Time Service) and that the firmware version on the NTP module is up to date. Test the system in a staging environment before deployment.

PTP Unicast Negotiation Failures

In PTP unicast mode, the time server may not respond to client requests if the negotiation fails. Verify that both the server and client are configured with the correct unicast negotiation parameters. Use the default multicast mode for simpler deployments and switch to unicast only when required.

Field Notes

Troubleshooting Guide

Module in Extended Holdover Mode
Likely Cause
GPS/GNSS signal loss from antenna obstruction, cable degradation, or atmospheric conditions has cut off the primary time reference.
Diagnostic Steps
Check antenna sky view and cable condition; review signal strength logs and holdover duration against the module's specified accuracy.
Corrective Action
Clear the antenna's view or repair/replace degraded cable, and confirm the module re-acquires lock; add a secondary time source if holdover risk is significant.
Client Time Offsets Growing or Jittery
Likely Cause
Network congestion is introducing latency and jitter into NTP traffic, degrading synchronisation accuracy.
Diagnostic Steps
Monitor NTP client offsets and round-trip delay; check for competing traffic on the same network path.
Corrective Action
Move time-sync traffic to a dedicated VLAN, apply QoS prioritisation to NTP/PTP packets, and re-verify client offsets improve.
Logged Events Off by an Hour or More
Likely Cause
Incorrect time zone or daylight saving configuration on the module or a downstream client.
Diagnostic Steps
Verify the module's time zone and DST settings against the site's actual location and current rules.
Corrective Action
Correct the configuration, standardise internal logging on UTC, and apply local time zone conversion only at the display/reporting layer.
Repeated Signal Attenuation from the GPS Antenna
Likely Cause
Weather-exposed antenna cable has degraded over time, attenuating the GPS signal.
Diagnostic Steps
Measure received signal strength against the specified threshold; inspect the cable run for visible weathering or damage.
Corrective Action
Replace with low-loss, properly weatherproofed cable (e.g. LMR-400 or equivalent), and re-verify signal strength.
Unexpected Load or Suspicious Traffic on the NTP Service
Likely Cause
The module's NTP service is open to unauthorised clients, risking use in amplification attacks.
Diagnostic Steps
Review current NTP access configuration and recent traffic logs for anomalous request patterns.
Corrective Action
Restrict NTP access with ACLs to authorised clients, enable NTS or symmetric key authentication, and update firmware to the latest patched version.
PTP Clients Fail to Synchronise in Unicast Mode
Likely Cause
Unicast negotiation parameters are mismatched between the server and client.
Diagnostic Steps
Compare unicast negotiation configuration on both the server and affected clients.
Corrective Action
Correct the mismatched parameters, or fall back to multicast mode for simpler deployments where unicast is not specifically required.
Reliability

Failure Modes & Root Causes

GPS Antenna Signal Loss
High Severity
Root Cause
Cable degradation, connector corrosion, or physical obstruction (new construction, foliage growth) blocking the antenna's view of the sky.
Effect
Module enters extended holdover mode, running on its internal oscillator alone, which can drift further as holdover time increases.
Detection Method
Signal strength/satellite count monitoring at the module, and inspection of the antenna cable and connector during maintenance.
Internal Oscillator Drift
Medium Severity
Root Cause
Ageing of the internal oscillator crystal, or extended holdover periods that exceed the oscillator's rated free-run accuracy.
Effect
Client time offsets grow or become jittery across the network, degrading the accuracy of timestamped events.
Detection Method
Offset trend monitoring on client devices, and correlation with any recent extended holdover event in the module's log.
Time Zone / Leap Second Misconfiguration
Medium Severity
Root Cause
An incorrect time zone or daylight-saving setting, or a leap-second table that has not been updated to the current release.
Effect
Logged events are off by an hour or more, complicating incident investigation and cross-system correlation.
Detection Method
Configuration audit against the site's actual time zone and leap-second table, verified after any firmware update.
Antenna Cable Signal Attenuation
Medium Severity
Root Cause
A degraded or excessively long antenna cable run, water ingress at a connector, or a marginal signal amplifier.
Effect
Repeated signal attenuation from the GPS antenna, increasing the frequency and duration of holdover events.
Detection Method
Signal level measurement at the module input, and inspection/replacement of the antenna cable and connectors.
Unauthorised Access / Suspicious Network Traffic
High Severity
Root Cause
Weak or default credentials, an unpatched vulnerability, or the module exposed on a network segment without adequate isolation.
Effect
Unexpected load or suspicious traffic on the NTP service, potentially compromising the integrity of the time reference distributed to clients.
Detection Method
Review of access logs and network traffic patterns for anomalies, and periodic firmware/security patch verification.
PTP Unicast Negotiation Failure
Low Severity
Root Cause
A misconfigured unicast negotiation parameter, or a firewall/network change blocking the negotiation handshake between module and clients.
Effect
PTP clients fail to synchronise in unicast mode, even though the module itself remains locked to its reference.
Detection Method
PTP negotiation log review on the module, and a controlled unicast session test against a known-good client.
Precautions

Safety & Operational Notes

Circuit Isolation Before Internal Work
Electrical Safety

De-energise and lock out the module's power feed before opening its enclosure or disconnecting internal wiring, and verify zero energy before handling connections.

GPS/GNSS Antenna Work at Height
Personnel Safety

Use appropriate fall protection when accessing a roof- or mast-mounted GPS/GNSS antenna, and confirm the antenna feed is disconnected from the module before disturbing antenna connections.

Confirm Standalone Holdover Before Isolating
Operational

Before taking the module out of service, confirm downstream systems can tolerate a loss of the authoritative time source, or that a standby time source is available, since alarm correlation and event logging across the ALCMS depend on synchronized time.

Verify Time Distribution After Maintenance
Compliance

After maintenance, confirm the module is correctly distributing time to the ALCMS, PLCs, and other connected equipment before closing out the work, not just that the module itself has re-acquired its reference source.

PPE & Grounding
Personnel Safety

Use appropriate PPE and confirm the module chassis and antenna cabling are bonded/grounded and surge-protected per the electrical design before reconnecting.

ESD Precautions
Personnel Safety

Use anti-static handling precautions when removing or inserting cards or modules within the unit, since its internal oscillator and timing electronics can be damaged by electrostatic discharge.

FOD Control at the Enclosure
Operational

Keep tools and fasteners accounted for at all times when the unit or its antenna mount is open, and secure or remove any loose material before closing it.

Restore to Compliant State
Compliance

Do not leave the module reporting an unsynchronised or degraded reference source after maintenance; confirm it has re-acquired a valid time source before closing out the work.

Field Insight

Engineering & Expert Notes

A Degraded GNSS Signal Can Look Like a Healthy Lock
Electrical

A module can report a GPS/GNSS lock while actually tracking a marginal number of satellites or a poor-geometry fix, producing time output that's technically synchronised but with reduced accuracy; check satellite count and fix quality, not just lock status, when investigating a suspected timing discrepancy.

Holdover Accuracy Degrades With the Module's Internal Oscillator Age
Compliance

An oscillator's holdover performance during a lost reference signal degrades gradually as the oscillator ages, even though the module may have passed its holdover spec when new; factor oscillator age into how much holdover time you can actually rely on for a given unit.

Antenna Feed Surge Protection Is Separate From Power Surge Protection
Electrical

A module can have adequate surge protection on its power input while its GNSS antenna feed, exposed at a roof or mast location, remains vulnerable to induced surges from nearby lightning activity; verify both paths are protected independently.

One Module's Fault Can Desynchronise Alarm Correlation Across the Whole ALCMS
Design

Because downstream systems rely on this module as their authoritative time source, a subtle drift here doesn't just affect the module's own logs; it can misorder or misalign alarm and event timestamps across every connected system, making incident review confusing well after the module itself is fixed.

ESD Precautions Matter More on Timing Cards Than General Logic Cards
Handling

The precision oscillator circuitry on a timing module can be more sensitive to electrostatic discharge damage than typical digital logic, with damage sometimes manifesting only as gradually worsening timing accuracy rather than outright failure; treat ESD handling as non-negotiable even for a "quick" card swap.

Verify Time Distribution End-to-End, Not Just at the Source
Troubleshooting

Confirming the module itself has reacquired a valid reference doesn't confirm every downstream PLC and ALCMS component is actually receiving and applying the corrected time; check timestamps at a sample of downstream devices before closing out the work.

Quick Answers

Frequently Asked Questions

Short answers about time synchronisation / NTP modules in AGL systems: what they do, accuracy, holdover, antenna siting, standards, maintenance and common faults.

Q1What is a time synchronisation / NTP module?

It is a dedicated network time server, also called an NTP server or GPS time server, that distributes accurate, synchronised time to network-connected devices in an AGL system. It is the authoritative time source for the ALCMS, PLCs, workstations, communication gateways and other equipment that needs accurate timekeeping.

Q2Why does an AGL system need synchronised time?

A CCR controller, PLC, operator workstation and network switch must agree on the time to within a few milliseconds if their logs are to be read as one coherent story. Consistent timestamps allow event logging, alarm correlation, sequence-of-events recording and coordinated control.

Q3How does the module get its time?

It receives UTC from a GPS or GNSS receiver (GLONASS, Galileo, BeiDou), which provides sub-microsecond accuracy, then serves that time to the network. A multi-constellation receiver is typical.

Q4What happens if the GPS signal is lost?

The module enters holdover mode and keeps time with its internal oscillator. Typical holdover accuracy is about ±1 µs per hour for an OCXO, ±1 ms per day for a TCXO and ±1 µs per day for rubidium. Extended holdover usually points to an obstructed antenna, degraded cable or atmospheric conditions.

Q5How accurate is NTP compared with PTP?

Typical LAN accuracy is ±1–10 ms for NTP, or about ±100 µs with hardware timestamping. PTP (IEEE 1588) reaches about ±100 ns with hardware timestamping.

Q6Which protocols does the module support?

NTP (RFC 5905), SNTP (RFC 4330), PTP (IEEE 1588), and the Daytime (RFC 867) and Time (RFC 868) protocols. It supports 10,000+ NTP clients depending on model and network load, with a 1 PPS BNC output.

Q7Where should the module and its antenna be installed?

The module is rack-mounted in the main equipment room next to the ALCMS server and core switches, with a short network path to the devices it serves. The GPS/GNSS antenna is mounted outdoors with a clear view of the sky, typically on the shelter roof or a nearby mast, and connected by dedicated coax.

Q8How is the module protected against spoofing?

It supports NTS (Network Time Security), MD5/SHA symmetric keys and access control lists. Authentication and access settings should be reviewed regularly so time-source spoofing is prevented.

Q9Which standards apply to time synchronisation modules?

The main references are RFC 5905 (NTP), IEEE 1588 (PTP), IEC 61850 (communication networks for power utility automation, including time synchronisation) and FAA AC 150/5345-56 (AGL control and monitoring equipment). Always verify the current edition and your approved requirements.

Q10How often should the module be maintained?

Typical intervals are quarterly for NTP client load review, semi-annual for time accuracy verification and redundant power and GNSS receiver tests, and annual for antenna and feedline checks, holdover performance tests and authentication and access review. Your approved maintenance programme takes precedence.

Q11Why are my client time offsets growing or jittery?

Network congestion is usually adding latency and jitter to NTP traffic. Monitor client offsets and round-trip delay, then move time-sync traffic to a dedicated VLAN and apply QoS prioritisation to NTP and PTP packets.

Explore Further

Related Components

Go Further

Go Beyond the Component. Understand the Complete AGL System.

You have explored the component. Now understand how it works within the complete Airfield Ground Lighting system.

Learn AGL from fundamentals to design, installation, testing, photometry, commissioning, maintenance and troubleshooting through structured technical training at Precision AGL Academy.

Build practical knowledge. Understand the circuit. Read the standards. Troubleshoot with confidence.

Your next step in AGL starts here.

The Learning Pathway
Learn Understand Design Test Maintain Document Apply Certify

Need expert guidance on Time Synchronization / NTP Module selection, deployment, or integration for your AGL network?

Precision AGL Academy provides advice on time source selection, network design, redundancy planning, and best practices for accurate, reliable time synchronization.