Space systems: a radar satellite, its ground station and the constellation it flies with. The loop, step by step: 1. A constellation, a station and the ground below. 2. Sensor, link, edge and console stand ready. 3. A satellite rises toward the station. 4. Sensors check that the response worked. 5. The station locks the beam and starts the pass. 6. Each reading is stamped with time and place. 7. Telemetry and payload data come down. 8. Relays carry the packets without reading them. 9. The edge verifies every signature first. 10. Mission control checks health and plans the next pass. 11. Only a confirmed result leaves the edge. 12. The next task is queued for upload. 13. The alert arrives with its evidence attached. 14. The satellite sets and the station parks. 15. Sensors check that the response worked. 16. Record, proof and action are archived together. 17. Everything settles back to idle.

01 / 17

A constellation, a station and the ground below

Nexus Observatory

Space and satellite systems

From orbit to the ground, on one protocol.

Spacecraft buses and payload classes, constellations sized to revisit and coverage, non-terrestrial networks and 3GPP direct-to-device, tasking and downlink, and space safety from tracking to conjunction awareness. Every pass, product and link carries its provenance into the grid.

Plan with usReference architectureThe open protocol

At a glance

From orbit to the ground, on one protocol

Space and satellite systems covers spacecraft buses and payload classes, constellations sized to revisit and coverage, non-terrestrial networks and direct-to-device, tasking and downlink, and space safety. Every pass, product and link carries its provenance into the same grid as the ground stations.

Tatizo

Orbit and ground, on different records

Satellite data and ground observations usually live in separate systems with separate clocks and licences. Combining them takes manual work, and the provenance is lost along the way. Analysts end up comparing images and readings without knowing whether their clocks, places or terms agree.

Key facts

Viwango: CCSDS · STAC

Components

LEO broadband user terminal (generic flat-panel class) on a ballasted pivot mount, with cable and router
Automatic weather station (AWS) to WMO siting practice
Geodetic GNSS station on a deep-drilled braced monument (generic class, no brand)
“AI tower in a box”
PTP grandmaster clock with GNSS antenna
Data hall row pair with cold-aisle containment
Operations console with a video wall

Interfaces

Radio: Satellite (LEO/GEO) · Ethernet · PoE

Where it works

Request, schedule, receive, process

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 deployment Talk to sales See Constellations and orbits See Licensing and spectrum

Tatizo
Orbit and ground, on different records
Satellite data and ground observations usually live in separate systems with separate clocks and licences. Combining them takes manual work, and the provenance is lost along the way. Analysts end up comparing images and readings without knowing whether their clocks, places or terms agree.
What it does
From orbit to the ground, on one protocol
Space and satellite systems covers spacecraft buses and payload classes, constellations sized to revisit and coverage, non-terrestrial networks and direct-to-device, tasking and downlink, and space safety. Every pass, product and link carries its provenance into the same grid as the ground stations.
Spacecraft and payloads
Buses and payload classes
Optical, radar and RF payloads ride on buses chosen for the mission. The small spacecraft shown is a base unit; constellations repeat it to buy revisit and coverage. Payloads are chosen against the measurement the mission needs, and integrated with the evidence they will produce.
See Spacecraft and payloads
The 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
Passes and records on one clock
Ground stations and spacecraft share a traceable time base, so every pass, image and link record lines up with the ground observations they are compared against. Clock offsets and orbit determination quality are carried with each record, so a comparison knows its limits.
Jinsi inavyofanya kazi
Request, schedule, receive, process
A tasking request is scheduled against passes and ground stations; the spacecraft acquires, downlinks and the ground segment processes the data into products, one chain with one record. Every request can be traced from the first order to the delivered product, with its licence and its acquisition record.
Viwango
CCSDS · STAC

See Tasking and downlink
NTN and direct-to-device
From orbit to the handset
3GPP non-terrestrial networks extend coverage from orbit to terminals and, increasingly, to ordinary devices, so remote sites stay connected when terrestrial links fail. Terminals fail over between orbit and ground automatically, and every switch is recorded with the reason. Each switch is recorded, so service levels can be checked.
See NTN and direct-to-device
Space safety
Tracking, telemetry and command
Spacecraft are tracked, commanded over authenticated links and screened for conjunctions. Every command and manoeuvre is recorded with who authorised it. Conjunction warnings are acted on according to a written procedure, and the decision is kept with the mission record.
See Space safety
Licensing and spectrum
Filings and earth-station rules
Spacecraft filings, frequency coordination and earth-station licences are prepared country by country and kept with the mission record. Filings are tracked to their deadlines, and every licence condition is checked against how the mission actually operates. Licence conditions are kept with the mission record and checked against operations.
See Licensing and spectrum
Operations
Passes, health and deliveries, watched
Operations watch pass schedules, spacecraft health and product delivery in the same console as the ground fleet. Missed passes and late products raise alerts with their cause, so recovery starts at once and the record shows what was done. Every alert carries its cause.
Constellations
Sized to revisit and coverage
Orbits and the number of spacecraft follow from how often and where the mission must look. Adding spacecraft adds revisit; adding ground stations adds contact time. The constellation plan states the revisit and coverage it buys, so a mission is designed against a need, not a catalogue.
See Constellations and orbits
What you get
Missions, tasking and backhaul
Orbit and pass methods, the payload class catalogue and ground-station interfaces on the protocol are open. Mission and payload integration, tasking and downlink services and non-terrestrial backhaul for remote sites are contracted. Pricing follows the mission and the services chosen, from a single tasking order to an operated constellation.
Talk to sales
Next step
Tell us the mission
Tell us what you need to see or connect, where and how often. We propose the orbit, the payload or the service, and the ground segment. The proposal states the revisit, the coverage, the latency to the ground and the evidence each product will carry.
Plan a deployment Talk to sales

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 presentations