TIBA: connect spacecraft design to a complete service

Tiba 1 launched on an Ariane 5 in November 2019. The TIBA-1 project combined an Airbus spacecraft platform with a communications payload built by Thales Alenia Space. Airbus’s manufacturing account describes Ka-band roles for secure and broadband communications. These responsibilities separate the equipment that keeps the spacecraft functioning from the equipment that performs its communications mission.

The platform supplies services such as power, thermal control, pointing and propulsion. The payload processes or relays mission signals. Neither works as a useful national service in isolation: ground gateways, user terminals, network operations and suitable procedures must connect the space segment to actual users. A capability described in a procurement or manufacturing release is therefore the start of a service explanation, not the complete answer.

Imagine a simplified network path with a satellite allocation of 100 megabits per second, a gateway connection capable of 80 and a remote terminal capable of 20. If all these limits apply to the same single transfer, its upper bound is twenty megabits per second. The lowest relevant capacity constrains the path. Adding the three numbers would not describe a rate that the user can achieve.

This is an invented bottleneck — open definition exercise, not a specification for TIBA-1. Real networks share capacity, introduce protocol overhead and experience changing conditions. An advertised spacecraft capability is not automatically the sustained rate at a particular terminal. A useful service test measures the complete path under stated conditions and reports how many users and flows are sharing it.

A path is limited by its bottleneck

Secure communications also depend on more than a satellite’s existence. Authorized equipment, access controls and operational procedures must work together. The phrase secure payload does not by itself establish every property of an end-to-end service. Similarly, a planned fifteen-year design life expresses an engineering target; it does not guarantee uninterrupted service to every customer throughout that period.

ESA’s launch account establishes delivery of TIBA-1 and its co-passenger into the planned launch orbits. Positioning, commissioning and user acceptance are subsequent questions. The important lesson is to connect each claim to the part of the system that can support it. Hardware specifications, launch events and measured user performance are all valuable, but they answer different questions about the same communications program.