Fuse multiple time sources into one clock you can trust through any outage.
Multi-source
Fusion engine
Outlier
Detection
Seamless
Source failover
BIPM-style
Ensemble
If your entire timing strategy depends on a single GNSS antenna, you are one jamming event away from having no time. Clock Ensemble is TimeBeat’s answer to that: a multi-source fusion engine that combines GNSS, White Rabbit, upstream PTP, internal oscillators and any other reference you have — weights them by quality, detects outliers, and gives you one fused clock that’s more accurate and more resilient than any of its inputs alone. When GNSS drops, Clock Ensemble rides on the other sources. When an oscillator drifts, it falls out of the weighting. You get a clock that survives the thing your competitors haven’t planned for.
What it does
Combine GNSS, White Rabbit, upstream PTP, internal OCXO / Rubidium oscillators and any other reference you have. Clock Ensemble treats them as a weighted ensemble, not a failover chain.
Each source is continuously evaluated for noise, stability and drift. Higher-quality sources get more weight — the same principle BIPM uses to produce UTC itself.
Sources showing anomalies (spoofing, jamming, oscillator aging) are detected statistically and automatically dropped from the weighting — no manual intervention.
When a source drops out, the ensemble reweights without discontinuity. No phase jump, no step, no downstream impact — just a smoother clock.
Tune the algorithm per-site: aggressive re-weighting for volatile environments, stable averaging for metrology labs. Defaults that work for most deployments.
Know exactly how stable your ensemble is over every timescale — seconds, minutes, hours, days. The stability metric that actually matters for timing.
How it works
Step 1
Every reachable time reference on the host — GNSS, upstream PTP, White Rabbit, OCXO, Rubidium — registers with the ensemble engine.
Step 2
Each source is scored on noise, stability, and agreement with the ensemble. Scores update in real time.
Step 3
The ensemble computes a weighted-mean clock, rejects statistical outliers, and exports the fused reference to PTP, NTP, PPS or 10 MHz outputs.
Where it lives
01
When GPS is jammed or spoofed, the ensemble keeps serving clean time from White Rabbit, upstream PTP and local oscillators — seamlessly.
02
Combine multiple oscillators into a BIPM-style ensemble for better long-term stability than any single reference can provide.
03
Fuse remote PTP sources from multiple sites into one ensemble, providing network-wide holdover through any single-site failure.
04
As an OCXO or Rubidium ages, its weight drops out gradually — no surprise holdover failure, no manual recalibration.
Hardware pairs
The capabilities of Clock Ensemble pair naturally with these products. Deploy together for the fullest experience.
Standards & compatibility
Also in the platform
Book a demo
Thirty minutes with a TimeBeat engineer. We’ll show you live dashboards, answer your architectural questions, and map the platform to the problem you’re actually trying to solve.
Further reading
Pillar guide
What a grandmaster actually does, how to choose one, and the three things that separate a grandmaster you can trust from one that quietly drifts.
Cluster
Choosing the right oscillator class — the drift numbers that matter and the deployment scenarios where each is correct.
Interactive tool
Model the regulatory and operational cost of a GNSS disruption for your industry and oscillator class.
Library
Guides, blogs and case studies for teams evaluating or deploying this solution.
How the Timebeat Agent fuses GNSS, upstream PTP feeds, PPS inputs and oscillator discipline into a single weighted clock output — the same BIPM-style ensemble approach used to produce UTC itself, applied at the site level.
Why a single-grandmaster deployment is a DORA Article 11 problem, what A/B/C redundancy looks like in a single rack unit, and how the Open Time Appliance Shelf turns three independent Rubidium Black+ grandmasters — with independent GNSS antennas — into the default finance-venue topology for 2026 and beyond.
An engineering decision framework for picking oscillator tier on an Open Time Appliance. Drift maths that matter, real-world holdover scenarios, and where each tier is the right economic answer — not just the best spec sheet.
What a PTP grandmaster clock actually does, how to choose one, and what separates a grandmaster you can trust from one that quietly drifts. Written by TimeBeat's engineering team for network architects deploying IEEE 1588 in production.
A practical, vendor-neutral checklist for selecting a PTP grandmaster clock — what to specify, what to ignore, and the questions that separate a deployment that works from one that quietly fails.
Choosing between OCXO, double-OCXO and rubidium holdover oscillators in a PTP grandmaster — the drift numbers that matter, the deployment scenarios where each is correct, and the trade-offs nobody talks about.
