Choosing the right Meinberg platform for critical infrastructure
LANTIME, microSync and IMS solve different timing problems. The right choice depends on the protocols, accuracy, resilience, interfaces and lifecycle your operation requires.
Time becomes infrastructure when every system depends on it
Accurate time supports far more than clocks. It aligns broadcast video and audio, timestamps financial transactions, coordinates power systems and gives defence platforms a common operational reference. When that reference becomes inaccurate or unavailable, the resulting fault can affect every connected system.
Meinberg has focused on synchronisation since 1979. Its portfolio spans dedicated NTP servers, compact PTP grandmasters and modular platforms that combine PTP, NTP, GNSS and legacy timing signals. That range provides flexibility, but it also makes the selection process an engineering decision rather than a simple model comparison.
Three Meinberg platforms, three distinct roles
The platforms overlap in capability, but each starts from a different operational requirement.
LANTIME
LANTIME appliances synchronise systems that use NTP or SNTP. Stable internal oscillators can bridge a temporary loss of the external reference.
- Rackmount and application-specific configurations
- Multiple reference inputs and legacy signal options
- Models for conventional networks through to high request volumes
Best fit: dependable NTP distribution where PTP is not required.
microSync
microSync provides IEEE 1588 PTP grandmaster capability and high-performance NTP in space-efficient DIN rail, half-rack and full-rack formats.
- GNSS support across GPS, GLONASS, Galileo and BeiDou
- Broadcast profiles including SMPTE ST 2059-2 and AES67
- Legacy timing inputs and outputs for mixed environments
Best fit: broadcast, AV, substations and edge sites needing compact PTP.
IMS
IMS combines a universal synchronisation core with application-specific input and output cards. Modules support field upgrades, hot plugging and hot swapping.
- Optional redundant clock modules and power supplies
- PTP, NTP, GNSS and legacy broadcast signals in one chassis
- High-density client and interface configurations
Best fit: long-life infrastructure with complex I/O, redundancy or future expansion.
| Selection factor | LANTIME | microSync | IMS |
|---|---|---|---|
| Primary purpose | NTP and SNTP distribution | Compact PTP grandmaster with NTP | Modular, multi-signal synchronisation |
| PTP support | No on the dedicated LANTIME NTP platform | Yes | Yes, with application-specific cards and profiles |
| Physical format | Primarily rackmount appliances | DIN rail, half-rack and full-rack options | Multiple modular chassis sizes |
| Expansion | Configured for the required NTP role | Model-specific interfaces and options | Field-replaceable input, output and clock modules |
| Typical environments | Enterprise, data centre and general infrastructure NTP | Broadcast, Pro AV, OB, industrial and substation systems | Finance, energy, defence, broadcast and national infrastructure |
Resilience depends on the whole timing chain
A grandmaster can only protect the operation when the reference, oscillator, network path and monitoring strategy have been designed together.
Reference and holdover
Meinberg systems can accept GNSS and other references, with oscillator options selected for the required holdover performance. The oscillator maintains a usable timebase when GNSS or another external reference disappears.
- Specify the acceptable timing drift during reference loss
- Match TCXO, OCXO or higher stability options to the holdover window
- Plan the antenna path, cable distance, gain and lightning protection
Network and system redundancy
Redundant grandmasters and paths protect against a single device or network failure. Meinberg PTP Auto Mode can link two grandmasters so clients continue following the same valid source when GNSS loss and a network fault occur together.
- Separate timing paths and network failure domains
- Use redundant power where availability requires it
- Validate failover behaviour before the system enters service
Application-specific timing architectures
The same clock does not suit every industry. Profiles, client counts, interfaces and failure consequences change the design.
Broadcast and media over IP
PTP aligns video, audio and control across SMPTE ST 2110 environments. microSync suits compact studios and OB systems, while IMS supports redundant grandmasters, PTP and legacy black burst, tri-level sync or audio references in larger facilities.
Energy and substations
PTP, PRP and legacy signal conversion can support staged migration from IRIG-based infrastructure. Redundant references and network paths help preserve event timing and protection-system coordination.
Finance and data centres
High client capacity, hardware timestamping and network segregation support traceable time across trading, transaction and infrastructure systems. Modular IMS configurations can consolidate dense PTP and NTP requirements.
Defence and secure infrastructure
Multiple references, strong holdover and isolated timing interfaces support systems that cannot assume continuous GNSS availability. The architecture should also integrate monitoring, event records and controlled management access.
Security and management belong in the specification
Meinberg systems allow unused physical interfaces and management protocols to be disabled. Role-based privileges and central authentication can support controlled access through RADIUS, TACACS+ or LDAP. PTP interfaces can also remain segregated from the management processor.
These controls matter because timing devices sit at the centre of many operational networks. Security configuration, firmware management and alarm handling should form part of commissioning, rather than follow after installation.
Operational tools
- PTP Track Hound captures, visualises and analyses PTP traffic for commissioning and fault finding.
- Net Sync Monitor provides logging and alarms through SNMP traps, syslog or email on supported IMS systems.
- mbgNMS supports device discovery, configuration backup, monitoring, alarm rules and fleet firmware deployment.
A practical specification checklist
Answering these questions early makes platform and oscillator selection much clearer.
- Which systems require NTP, PTP or legacy timing signals?
- Which PTP profiles must operate, and can more than one profile share the platform?
- How many clients and requests must the system support?
- What accuracy must remain during GNSS or reference loss?
- Which antenna location, cable distance and distribution constraints apply?
- Does the operation require dual clocks, dual power or network redundancy?
- Which monitoring, authentication and audit systems need integration?
- Which interfaces or capabilities may need to be added during the asset lifecycle?
Not sure which Meinberg platform fits?
Bring iTkey the required protocols, interfaces, client capacity, holdover target and operating environment. We will define the timing architecture, identify the right platform and plan how it integrates with the wider network.
Technical source: Meinberg Timing & Synchronisation Solutions presentation supplied by iTkey, July 2026. Final system capability depends on the selected chassis, modules, oscillator, firmware and licensed features.
Ready to Discuss Your Requirements?
Our technical experts are ready to help you design and implement the perfect timing solution for your critical infrastructure needs.
- Precision EngineeringOur timing solutions deliver nanosecond-level accuracy for the most demanding applications.
- Security FirstMilitary-grade security features and compliance with classified network requirements.
- Expert SupportTechnical support from timing specialists with defence and infrastructure experience.
- Custom SolutionsTailored timing architectures designed for your specific operational requirements.
Open the published page to view and test the live form.
