Modernising Legacy Clock Systems with NTP, Indian Standard Time and NAVIC-Based Time Synchronisation

Executive Summary

Bihar Communications Pvt. Ltd. has developed and installed a modern time-synchronisation solution for the legacy clock infrastructure at the Parliament of India. The system is designed to bring a long-running legacy clock network into a modern, automatically synchronised timing environment while preserving the existing downstream clock infrastructure.

The installation combines network-based time synchronisation with an Indian Standard Time (IST) reference architecture and a NAVIC-based timing source. The solution can obtain authoritative time, validate incoming timing information, maintain local time during temporary communication interruptions, and distribute the resulting time to legacy clocks through the existing clock-distribution interface.

A key part of the engineering challenge was not simply obtaining accurate time, but understanding and reliably decoding the proprietary/legacy timing signal already travelling through the installed system. The project therefore required detailed analysis of the legacy communication behaviour, signal framing, timing characteristics and failure modes before a compatible modern controller could be developed.

The Challenge: Modern Time for a Legacy Infrastructure

Large institutional clock networks can remain in service for many years. Their displays, cabling and distribution arrangements may continue to function even when the electronics that originally generated, formatted or synchronised the time become obsolete.

The Parliament installation presented this type of engineering challenge. The objective was not merely to put a new clock on a network. The objective was to create a dependable modern time-reference and control layer that could communicate with an established legacy clock network.

This required the engineering team to work with an existing system whose timing and communication behaviour had to be understood from the signal itself rather than from a contemporary open interface specification.

Decoding the Legacy Signal

One of the most technically demanding stages of the project was decoding the signal travelling through the legacy clock system.

The engineering team had to determine how the existing system represented time, how information was framed, how frequently timing information was transmitted, how the receiving clocks interpreted the signal, and how the system behaved during missing or malformed data.

Unlike a new network design where the protocol, packet structure and interfaces can be specified from the beginning, a legacy installation requires reverse engineering and controlled validation. The work involved observing the signal, identifying repeatable patterns, correlating those patterns with known time values, and progressively developing a compatible interpretation.

This was particularly important because an apparently valid electrical signal is not necessarily a valid time message. A modern controller therefore has to distinguish between usable time information, incomplete data and corrupted or unexpected information before allowing a new time value to propagate through the clock network.

The resulting engineering approach focused on compatibility and reliability rather than replacing the complete installed clock network.

Architecture of the New Time-Synchronisation Layer

The solution places a modern time-synchronisation controller between the external time references and the legacy clock distribution network. At a functional level, the architecture can be represented as:

The controller is responsible for acquiring time, validating it, converting and maintaining it in Indian Standard Time, and delivering an appropriate time signal to the installed legacy clock infrastructure.

Network Time Synchronisation

The network path uses standard NTP-based time synchronisation. The project firmware implements an NTP client, handles binary NTP responses and converts the received UTC time to Indian Standard Time.

The supplied project documentation specifies that the system synchronises from India's national time reference through samay.nic.in and performs UTC-to-IST conversion before displaying and distributing the time. It also documents handling of extended responses and buffer clearing to avoid stale data affecting subsequent synchronisation attempts.

The system does not blindly accept every received packet. The firmware validates characteristics of the NTP response, including server-response mode, valid stratum and consistency of the receive and transmit timestamps before accepting the time.

NAVIC / GNSS-Based IST Reference

In addition to network synchronisation, the deployed architecture uses an IST-based NAVIC timing source as an independent reference for providing Indian Standard Time.

The role of the NAVIC/GNSS timing layer is to provide a local, satellite-derived reference that can be used where an independent timing source is required. This is particularly relevant to critical installations where maintaining a reliable time reference should not depend solely on a single network path.

The NAVIC timing source and the NTP synchronisation path can therefore be viewed as complementary parts of the overall timing architecture: network time provides convenient automatic synchronisation, while GNSS/NAVIC provides an independent external timing reference.

Resilience and Continuity

The controller has been designed for practical operation rather than assuming that network connectivity will always be available.

The system can use a primary network time source, move to an alternate time path when the primary source is unavailable, and continue maintaining time locally. The legacy clock network continues to receive time from the controller rather than having to understand the details of the upstream timing source.

This separation of functions is important in a legacy environment. It allows the downstream clock infrastructure to remain stable even when the upstream source changes.

Validation Before Time Is Accepted

Reliable time distribution requires more than receiving a timestamp. The controller therefore performs validation before updating the local clock.

The implemented firmware checks the NTP response mode, verifies the reported stratum, checks the receive and transmit timestamps against an acceptable range, and verifies that the two timestamps are mutually consistent. Only after these checks pass is the received time converted to IST and written to the local timekeeping system.

This approach reduces the possibility that corrupted serial data, incomplete packets or unexpected responses could cause an invalid time value to propagate to the installed clock network.

Preserving Existing Infrastructure

A central design objective was to modernise the time-reference layer without unnecessarily replacing the complete legacy clock installation.

Where the existing displays, wiring and downstream distribution infrastructure remain serviceable, the new controller provides a bridge between that legacy infrastructure and modern time sources. This approach can be valuable for large installations because it can reduce the scope of physical replacement while allowing the timing architecture to be upgraded.

What the System Can Do

The installed architecture is designed to:

• Automatically obtain time from a network time reference.
• Use an IST-based NAVIC/GNSS timing source as an independent reference.
• Convert and maintain the time in Indian Standard Time.
• Validate received timing information before accepting it.
• Maintain local time when an upstream source is temporarily unavailable.
• Detect loss of the primary synchronisation path and use an alternate path where configured.
• Provide synchronisation status to the operator.
• Interface with the existing legacy clock-distribution system.
• Continue distributing time to downstream clocks without requiring each legacy clock to become network-enabled.
• Provide a foundation for future monitoring and time-server upgrades.

Engineering Significance

The Parliament installation demonstrates an important engineering pathway for long-lived infrastructure: modernise the timing intelligence while preserving usable legacy assets.

The difficult part of such a project is often not the individual electronic components. It is understanding the behaviour of an installed system whose communication method was designed many years earlier, decoding its signals reliably, and building a modern interface that behaves correctly under normal operation as well as during missing, delayed or corrupted data.

By combining legacy-signal analysis, embedded control, network time synchronisation and an Indian satellite-based timing reference, Bihar Communications has created a practical bridge between an established clock infrastructure and modern time-synchronisation technology.

About Bihar Communications Pvt. Ltd.

Bihar Communications Pvt. Ltd. is an Indian manufacturer and OEM associated with master-slave clocks, analogue and digital clocks, GPS and network time displays, NTP time servers and time-synchronisation systems. Company documentation identifies its ORNATE range as including master-slave clocks, GPS clocks, network time displays and associated synchronisation systems.

The company has undertaken time-reference and network-time-display projects for institutional and industrial environments and continues to develop embedded and network-based time-synchronisation systems for legacy and modern installations.

Technical Note

This publication intentionally describes the system at a functional and architectural level. Detailed component selections, circuit schematics, bill of materials, firmware source code, communication pin assignments, proprietary decoding details and other implementation-level information are not disclosed.

The purpose of this article is to describe the engineering problem, the capabilities of the installed solution and the significance of modernising a legacy time-distribution system.

View Our Products →   Discuss a Similar Project →   Also: WSM at the Cabinet Secretariat →