BAE Systems wins a Space Systems Command contract for compact radio terminals that span LEO to GEO

The compact design is aimed at integrators whose spacecraft have no spare room for another communications box. Interesting Engineering reported that the design could help accommodate communications hardware on spacecraft with limited room for additional equipment ^[5].

What such an integrator can buy today is smaller than the pitch. BAE plans to adapt an existing, space-qualified software-defined radio ^[3], and the heritage it cites sits one layer away from that radio. The company says its RAD750 single-board computer has powered more than 100 satellites ^[9]. Its RAD5545 board consolidates processing that previously took several cards ^[10]. Both are computers, not the radio being adapted. The report does not include a flight count for the radio or a delivery schedule.

Joe Dziezynski, who directs BAE's Space Systems product line, said the program rests on decades of work building hardware for demanding missions ^[11]. He also pointed to established manufacturing capacity as a way to accelerate deployment and expand production ^[12].

In our view a program office planning around these terminals should carry them as a specification until BAE's demonstration is done. The tradeoff is room: a placeholder holds volume on exactly the kind of spacecraft the report describes as having limited room for additional equipment ^[5].

To test any terminal pitch the same way, sort each claim on two axes: whether it is a measured result or a requirement, and whether a test in the contract covers it. Plan on a measured result with a test behind it. When the result comes from a different product, ask what transfers. A requirement with a test waits for the test. Do not plan on a requirement with no test behind it.

On the report's evidence, the LEO-to-GEO range ^[4] and the jamming tolerance ^[6] are requirements waiting on the demonstration ^[13]. The RAD750 record ^[9] is a measured result from a different product.