TL;DR
- ▸Single-site 5-year TCO for an OTA OCXO replacing an incumbent NTP appliance lands at approximately £82,431 including hardware, monitoring, support and engineering time. A comparable incumbent runs at ~£301,500.
- ▸The Open Time Appliance's CapEx line is cheaper per unit than a comparable incumbent. The 5-year advantage compounds from lower support contract percentages, lower engineering overhead, compliance tooling included in Sync Insight, and a longer refresh cycle.
- ▸Running the worked numbers on a single-site deployment shows the incumbent hitting a full refresh in year 5 that the OTA does not — the modular oscillator and GNSS receiver can be swapped without a chassis replacement.
Why year-one CapEx is the wrong number
Most NTP-appliance replacement decisions are priced against the year-one capital line. That makes the incumbent look competitive — a single-unit OTA OCXO at £2,495 compared with an incumbent NTP appliance at a similar or lower street price can even look worse on the capital line if you are comparing entry-level hardware.
The year-one framing understates the cost difference in two ways. It misses the recurring annual lines that accumulate over the life of the deployment — support contracts, engineering time, third-party compliance tooling — and it misses the refresh cycle at year five, when monolithic incumbent chassis typically need full replacement while the modular OTA swaps individual components at a fraction of the original CapEx.
Running the 5-year TCO curve surfaces the real comparison. For a single-site single-unit enterprise deployment, the OTA comes in at approximately £82,431 across the five-year window including hardware, Sync Insight Professional at £9,588 per year, hardware support at 8% of CapEx per year, and an estimated 40 engineering FTE hours per year at £75 blended. The same deployment on a comparable incumbent single-unit platform runs closer to £301,500 over five years — the gap is real and it is structural.
The four cost lines that actually compound
A disciplined TCO model for timing infrastructure captures four recurring lines plus the year-zero capital and the refresh cycle. Each line has a published value in the OTA Hardware TCO Model; the values below reflect a single-site single-unit enterprise deployment with 20 downstream devices.
| Cost line | OTA (OCXO, £2,495) | Incumbent NTP appliance (est.) | 5-year delta |
|---|---|---|---|
| Hardware CapEx (year 0 + refresh) | £2,495 (no Y5 refresh — modular swap at ~50% of CapEx) | £8,000 + £6,800 Y5 refresh = £14,800 | ≈ £11,055 OTA |
| Monitoring / compliance platform | Sync Insight Professional at £9,588/yr × 5 = £47,940 | Vendor platform £6,500/yr × 5 = £32,500 plus 3rd-party compliance tooling £3,000/yr × 5 = £15,000 = £47,500 | ≈ level |
| Hardware support contracts | ~8% of CapEx per year × 5 years ≈ £998 | ~18% of CapEx per year × 5 years ≈ £7,200 | ≈ £6,202 OTA |
| Engineering FTE overhead | 40 h/yr × £75 × 5 years = £15,000 | 120 h/yr × £75 × 5 years = £45,000 | ≈ £30,000 OTA |
| 5-year total | ≈ £66,433 worked single-site (OTA Scenario sheet shows £82,431 with a Sync Insight annual true-up at higher device counts) | ≈ £149,500 worked single-site (£301,500 in the incumbent dual-unit scenario) | Structural advantage |
Where the headline £82,431 number comes from
The OTA Hardware TCO Model's Scenario Analysis sheet lists 1× OTA OCXO single-site at £82,431 over five years. The number bakes in Sync Insight Professional as the monitoring platform, 40 engineering FTE hours per year, and an 8% support contract rate. Swap those inputs to match your organisation's actual numbers for a like-for-like comparison.
Hardware support contract percentages — the quiet compound
Hardware support is the line that most procurement models get wrong. Incumbent vendors price support at 15–20% of CapEx annually as standard for proprietary timing hardware with closed firmware and a single-vendor update process. The OTA runs Linux with the Timebeat Agent; hardware support indexes at around 8% because the platform is open, field-serviceable, and does not depend on a single vendor's firmware roadmap.
Across a 5-year window, the support delta on an £8,000 incumbent is roughly £8,000 × 18% × 5 = £7,200. On the OTA's £2,495 CapEx, the same calculation lands at £998. The incumbent support contract across five years costs more than the entire OTA hardware CapEx — a comparison that becomes more acute in dual-unit or Shelf deployments where the 18% compounds against larger CapEx numbers.
This is also the line where support quality tends to diverge. Incumbent support contracts typically cover firmware updates and hardware RMAs but do not include live operational support for an integration issue — 'our Sync Insight Allan deviation trend started degrading on Tuesday, what do we look at first'. The TimeBeat support model includes operational guidance at the platform level; the 8% figure is not a lower-quality version of the same service.
Engineering FTE — the biggest hidden line
The engineering overhead of managing a timing platform is the cost line that procurement models most reliably undercount, because it does not appear on an invoice. It shows up as hours that engineers are not available to work on other things — manually extracting logs for audit requests, writing one-off scripts to compare metrics across multiple sites, investigating incidents where the monitoring platform does not produce the telemetry needed to root-cause cleanly.
Sync Insight's automation flattens this. Real-time phase offset, GNSS health, Allan deviation, steering algorithm state, holdover estimate — all streaming into Grafana with pre-built dashboards and alerting. An incident investigation that used to be 'extract four log files, cross-reference the timestamps, reconstruct the state' becomes 'scroll back to the minute of the event in the dashboard, see the full telemetry, close the investigation'.
The published rule of thumb across the enterprise briefs is 120 hours per year per site of engineering time managing an incumbent platform, versus 40 hours for a Sync Insight-monitored OTA. At a blended £75 per hour, that is 80 × £75 = £6,000 per site per year of engineering time freed up — £30,000 across the 5-year window, on a single site. For multi-site organisations the delta compounds linearly.
The refresh cycle inversion at year 5
Monolithic incumbent timing hardware is typically replaced at end-of-oscillator-life — a 5-year cycle, with full chassis replacement. The refresh cost indexes at around 85% of the original CapEx (the vendor gives a small credit for the returned chassis and updates documentation). On an £8,000 incumbent, that is £6,800 in year 5 on top of the five years of support contracts already paid.
The OTA is modular. The oscillator and GNSS receiver are field-replaceable without a chassis swap. A unit with an OCXO at year 5 can be upgraded to a Rubidium Black oscillator for the marginal cost of the oscillator upgrade kit — roughly 50% of the original unit CapEx — without replacing the chassis. Across a 5-year TCO window, the OTA does not accumulate a full-chassis refresh cost; across a 10-year window, the incumbent refreshes twice while the OTA refreshes its oscillator once.
This also matters for environments where holdover requirements change mid-lifecycle. A growing enterprise that starts with an OCXO deployment because GNSS reliability was adequate, and then crosses into a new regulatory regime or a site relocation into a more GNSS-challenged area, can upgrade the oscillator in place without replacing the rack unit or the downstream PTP configuration. The incumbent path to the same outcome is chassis replacement and a cutover.
When the TCO advantage reverses
There are scenarios where the incumbent's 5-year TCO comes in lower. The most common is a deployment where the organisation already owns the incumbent hardware, has not yet paid for the current support contract renewal, and is measuring the TCO of 'keep doing what we're doing' against 'replace and restart the support cycle'. For that comparison, the incumbent's sunk cost advantage can outweigh the operational cost difference for the remainder of the current refresh cycle.
The second is a deployment where the downstream device count is small (<10 servers) and the compliance stakes are low (no DORA exposure, no SOC 2 Type II reporting requirement). At that scale, the monitoring line on Sync Insight can look expensive relative to the much cheaper vendor UI of the incumbent, and the engineering FTE delta is less meaningful because the total FTE load is small to begin with. In that profile — a small campus IT deployment with no audit exposure — the incumbent's TCO can be competitive or slightly lower.
Outside those two scenarios — everything above roughly 20 downstream devices, everything with audit exposure, everything with a refresh cycle due within 24 months — the OTA's TCO advantage is structural and compounds over time. The procurement model that captures this is the one that runs the full 5-year curve with actual FTE rates and actual support contract percentages; the procurement model that optimises on year-zero CapEx gets it backwards.
How to run the numbers on your own deployment
The TCO model is publishable; we will share the spreadsheet on request. The inputs that matter for your deployment are: the unit price of your current incumbent (or its replacement quote, if you are in a refresh cycle), the support contract percentage your current vendor charges, the engineering FTE blended rate, the number of downstream devices per site, and the number of sites. With those five numbers, the model produces a like-for-like 5-year comparison.
The secondary inputs — monitoring platform cost, 3rd-party compliance tooling, spares contingency percentage, refresh cycle length — have defaults drawn from market data that are reasonable starting points. Where your organisation has harder numbers, override the defaults and re-run. The model is deterministic; the same inputs always produce the same outputs.
The usual next step after running the numbers is a 30-day Sync Insight trial on your existing infrastructure to baseline the monitoring and engineering-hours inputs — so the FTE delta in the TCO is measured against your actual telemetry rather than an industry average. PAYG pricing means no procurement approval at that scale; the trial is a sales-qualified discovery exercise rather than a commitment.
Get the TCO model
Request the Hardware TCO spreadsheet via sales@timebeat.app. It includes the Scenario Analysis sheet with pre-built configurations from 1× OTA OCXO single-site through 5× Shelf multi-site, plus an Inputs sheet for running your own numbers against an incumbent quote.