Positioning, navigation and timing: GNSS monuments across a valley tied to one reference clock. The loop, step by step: 1. Three reference stations and one grandmaster. 2. The chain from source to console stands ready. 3. Each station tracks the same satellites. 4. Each reading is stamped with time and place. 5. Corrections and time travel to the grandmaster. 6. The relay forwards sealed packets untouched. 7. The edge verifies every signature first. 8. The grandmaster disciplines its oscillator. 9. Only a confirmed result leaves the edge. 10. The clock room distributes time to the site. 11. The alert arrives with its evidence attached. 12. One station loses its sky view. 13. The other two carry the reference. 14. Instruments confirm the response took effect. 15. The whole chain is archived for audit. 16. Everything settles back to idle.
01 / 16
Three reference stations and one grandmaster
Nexus Observatory
/
Positioning, navigation and timingGNSS reference stations tied to the geodetic frame, PTP and SyncE time distribution engineered to the budget, grandmasters and holdover that ride through outages, and resilient PNT that finds jamming and spoofing before a timestamp goes wrong.
Plan with usReference architectureThe open protocolAt a glance
Where and when, with the error bound
Positioning, navigation and timing delivers GNSS reference stations tied to the geodetic frame, PTP and SyncE time distribution engineered to the budget, grandmasters with holdover, and resilient PNT that detects jamming and spoofing. Every position and every timestamp comes with the error bound it was produced with, so the user knows how far to trust it.
مسئله
A wrong timestamp is a wrong answer
Positions drive autonomous trucks; timestamps order every event in a network. When a receiver is jammed or spoofed, both can be wrong while looking perfectly normal. Integrity has to be designed and measured, because a degraded signal rarely announces itself to the systems that depend on it.
Key facts
- قالبها
- RINEX · RTCM · NTRIP
- Profiles
- IEEE 1588 PTP · ITU-T G.8275.1 · SyncE
Components
- Geodetic GNSS station on a deep-drilled braced monument (generic class, no brand)
- Robotic total station in a monitoring shelter
- Slope stability radar on a trailer
- Haul truck with onboard network and autonomy kit
- Private LTE mast on a solar skid
- “AI tower in a box”
- PTP grandmaster clock with GNSS antenna
- Data hall row pair with cold-aisle containment
Interfaces
- Time and position
- GNSS 1PPS
Where it works
- Stations tied to the geodetic frame
In the story below
- The system, part by part
- Assembly
- Installation
- Deployment
- Connections
- Operation
- Failure and recovery
- Scale and federation
- What you get
Scenes · 18
Next steps
Plan a deploymentTalk to salesSee Interference detectionSee Resilient PNTمسئله
A wrong timestamp is a wrong answer
Positions drive autonomous trucks; timestamps order every event in a network. When a receiver is jammed or spoofed, both can be wrong while looking perfectly normal. Integrity has to be designed and measured, because a degraded signal rarely announces itself to the systems that depend on it.
What it does
Where and when, with the error bound
Positioning, navigation and timing delivers GNSS reference stations tied to the geodetic frame, PTP and SyncE time distribution engineered to the budget, grandmasters with holdover, and resilient PNT that detects jamming and spoofing. Every position and every timestamp comes with the error bound it was produced with, so the user knows how far to trust it.
Reference networks
Stations tied to the geodetic frame
Continuously operating reference stations on stable monuments provide corrections and positions in the national frame, so every survey and every machine agrees on where things are. Station metadata follows published rules, so another network can use the corrections and check the frame.
- قالبها
- RINEX · RTCM · NTRIP
Holdover
Clocks that keep time when the sky goes dark
Grandmasters carry stable oscillators that hold time when satellite signals are lost. Holdover performance is part of the design, and the record shows when a clock is running on it. When the sky returns, the clocks are re-steered and the holdover period is recorded with the data it affected.
See Grandmasters and holdoverThe system
One station, part by part
Before anything is installed, the station is laid out as its parts: instrument, logger and edge compute, secure element, GNSS timing, radio, power, enclosure, wiring, earthing, mast and foundation.
Assembly
Built and tested before it ships
Each part is fitted to the pole and the enclosure, wired through surge protection to one earth, powered and bench-tested until it signs its first reading.
Installation
Installed on site
The crew arrives with the tested kit: foundation, mast raised and guyed, instruments mounted, cables run in conduit, the enclosure fitted out and the site commissioned.
Deployment
Site after site, one design
The same station goes in at every site on the plan, each commissioned against the same checklist, until the field is covered.
Wiring
Signal, power and time, wired
Inside one site the instrument’s signal pair runs to the logger, solar charges the battery that feeds the load, GNSS time reaches the clock and the logger hands its records to the radio.
Connections
Backhaul, time and power
The relay carries every site to the edge over a point-to-point link, the grandmaster’s time reaches every clock, and each site keeps its power through the night.
Time distribution
PTP, SyncE and NTP, engineered to the budget
Time is distributed from grandmasters over PTP and SyncE where precision matters and NTP where it does not. Each hop is engineered against a timing budget and measured after installation. Every hop is measured after installation and monitored afterwards, so drift is found before it breaks a budget.
- Profiles
- IEEE 1588 PTP · ITU-T G.8275.1 · SyncE
Resilient PNT
Several sources, one trusted solution
Satellite, terrestrial and inertial sources are cross-checked; a source that disagrees is set aside before it corrupts the solution, and the integrity of the result is reported with it. The solution states which sources it used, so a user can see why it should be believed.
See Resilient PNTOperations
Integrity, watched around the clock
Operations watch station health, clock offsets and interference events, and warn users before the error bound is exceeded. A degraded service is announced to users before it fails them, with the evidence and the expected time to restore. Users see the same integrity data as we do.
Interference
Jamming and spoofing found, located, logged
Monitoring stations watch the GNSS bands for interference, locate the source and log the event, so operators can act and regulators can be shown the evidence. Events are kept with their location, time and duration, so patterns can be reported and acted on.
See Interference detectionتازهها
Receivers and clocks updated by plan
Receiver firmware, clock configuration and integrity rules are updated in rings, with each ring checked against the timing budget before the next one starts. A change that degrades time or position is rolled back automatically, and the affected period is marked in the record.
How it scales
From one site to a national frame
Reference stations, grandmasters and monitors are added as coverage grows, all reporting into one network with one integrity record. Coverage and redundancy are planned so that the loss of one station or one clock never takes the service down with it.
What you get
Integrity as a service
The timing budget method and reference station metadata rules are open. Timing and positioning integrity, reference network design and operation, and holdover engineering are contracted. Integrity reports are delivered on record, so the service level can be checked by the user as well as by us.
Talk to salesNext step
Check your timing budget
Tell us what depends on time or position at your site. We measure, design and write the budget down. The result is a timing and positioning budget written down, measured on site and monitored from then on; the same budget then guides every expansion.
Plan a deploymentTalk to sales
More presentations
See it from every side.
Each opens as a full-screen presentation: deeper pages on the same subject, explainers, stories, guided tours of the places, network scenes and the observatories that came before.
All presentationsIn depth
Use case Highway corridor coverage and safety sensingUse case Wildfire camera and fire-weather nodeUse case Avalanche detection siteUse case Community cellular and sensingExplainers
Explainer · Communities and rural Communities and ruralCommunity cellular coverage on real terrain, fixed-wireless Fresnel clearance, corridors, a remote microgrid sized from its load and interim public-safety broadband.Explainer · Environment and climate Environment and climate — SectorsMethane fencelines, acoustic biodiversity grids, flux towers, river sondes and smoke networks: an interactive explainer with the method behind every number.Stories
Story · Timing and PNT Time as infrastructureA 5G cell must hold its phase within 3 µs of its neighbours, ±1.5 µs of a common reference; a synchrophasor’s one per cent vector error leaves room for only…Story · 6G and sensing Networks that senseThe framework for 6G names integrated sensing and communication as one of its usage scenarios: the same radio that carries data also measures range,…Story · Mountains and avalanche terrain Snowpack, slope and signalAvalanche forecasting reasons about the likelihood and size of avalanches on given terrain. The observations behind it come from a few stations in hard…Places and networks
Guided tour · Guided 3D tour Orbit viewGround tracks of a sun-synchronous imager and three shells of a broadband constellation, computed from their orbits over a rotating Earth.Guided tour · Guided 3D tour Arctic stationA self-powered station on the ice: a microgrid, a low-orbit satellite terminal, a weather station, a GNSS monument and an edge node that holds data through the polar night.Guided tour · Guided 3D tour Coastal portCoastal radar and AIS watch the approach, a met-ocean buoy reports the sea state, and crane-side edge compute closes the control loop on a private network.Network scene · NTN · Satellite Satellite direct to device in a mountain valleyWhere the valley cell cannot reach, phones on the pass road connect straight to a low-orbit satellite, which relays through its feeder link to a gateway.Network scene · Private 5G · Port Private 5G at a container portSmall cells on the yard lighting masts and a sector site on the operations building serve remote-controlled cranes and trucks among steel container stacks.Heritage observatories
Heritage observatory · United States · 1885 Blue Hill Meteorological ObservatoryAbbott Lawrence Rotch built a weather observatory on a hill south of Boston at his own expense and began observations on 1 February 1885.Heritage observatory · United Kingdom · 1883 Ben Nevis ObservatoryFor twenty-one years, from 1883 to 1904, observers climbed Britain’s highest mountain to read thermometers every hour, day and night, in all weathers.Interactive tools
Interactive tool · Plan a site Field Deployment StudioTerrain, devices, coverage, viewshed, power and the best spot for a station, then a deployment request with the plan attached.01 · What this platform covers
Positioning, navigation and timing, area by area.
Choose an area for its systems, standards, the industries it serves and how we deliver it.
01GNSS reference networks
Continuously operating stations, tied to the geodetic frame.02Time distribution
PTP, SyncE and NTP, engineered to the budget.03Grandmasters and holdover
Reference clocks that keep time when the sky goes dark.04Resilient PNT
Several sources, cross-checked, one trusted solution.05Interference detection
Jamming and spoofing found, located and logged.02 · Built on the open protocol
One protocol under every platform.
Marked: the functions this platform leans on hardest. The protocol itself is open, so what you build here runs anywhere the protocol runs.
01 JOIN
02 ADMIT
03 DESCRIBE
04 TIME
05 OBSERVE
06 QUALIFY
07 FEDERATE
08 ORCHESTRATE
03 · Open and enterprise
Open by default. Enterprise by contract.
The open layer lives on the main site, free to use and build on. Enterprise services are delivered under contract by Nexus Observatory Inc.
Open, on the main site
- Timing budget method
- Reference station metadata rules
Enterprise, on this site
- Timing and positioning integrity
- Reference network design and operation
- Holdover engineering
04 · Industries served
The industries that build on positioning, navigation and timing.
Each industry has its own site: its use cases, its community and the enterprise path, with this platform among the systems behind it.
صنعت Public safetyWarning time, gained at the sensor.صنعت Civil resilienceInfrastructure that reports before it fails.صنعت اقیانوسهاFrom the coastline to the open ocean.صنعت انرژیThe grid edge, observed.صنعت TelecomTowers that compute, sense and connect.صنعت TransportCorridors that report their own conditions.05 · Every platform
Every platform, one architecture.
One platform for each technical area of our work, on the same protocol, the same data and the same design.
Protocol & GridSoftwareHardware & powerSensors & instrumentsConnectivityEdge compute & AIEarth observation & GeoAIField servicesData & licensingSpace and satellite systemsPositioning, navigation and timingSecurity and trustDigital twins and simulationDesign and integrationTest and qualificationOperations centreTraining and enablementFrontier labsBring us the site.
We bring the survey, the design and the crew. Nexus Observatory Inc. The form names who receives your details.
Talk to usCreate account