Segmented architecture: let spacecraft share the work

CONAE’s segmented-architecture concept distributes functions across cooperating small spacecraft. One segment might carry an instrument, another storage or processing, and another a communications resource. Each still needs the support systems required to operate as a spacecraft. The aim is to make a mission adaptable by adding or replacing capabilities. This is a different design from simply launching two independent satellites that happen to observe the same planet.

The planned SARE family includes optical and microwave Earth-observation branches. CONAE’s November 2023 roadmap also describes the Patagonia multipurpose platform concept and ALOFT as a technology demonstration for formation flight. Those names identify related parts of a development effort, not three interchangeable names for one flown spacecraft. The dates in that roadmap remain historical forecasts in this lesson; no successful SARE or ALOFT launch is inferred from the passage of time.

Imagine an original three-segment mission. One satellite takes an image, a second stores a backup, and a third downlinks the result. The system needs compatible message formats, adequate links and an agreed schedule. If the image has an identifier and a timestamp, the receiver can distinguish a new observation from a repeat transmission. A shared memory is useful only when the other segments can reach it and interpret what it contains.

Suppose the instrument generates twelve data units per minute while its link carries ten. The queue grows by two units each minute, or twenty units over ten minutes if those rates stay constant. Adding a larger memory delays overflow but does not remove the long-term mismatch. Possible design changes include shorter observing periods, a faster link or justified compression. These invented rates illustrate a system budget; they are not SARE specifications or claims about the actual payload designs.

Follow the distributed data path

Two storage units can protect against one failed unit, but not necessarily against a shared software error that writes the same corrupted file to both. A useful design review follows the whole data path and asks where failures can affect several segments at once. Redundancy — open definition is therefore a relationship between a failure and a protective arrangement, rather than a simple count of duplicate boxes. Configuration records and test cases make that relationship assessable.

The DICE-1 and DICE-2 photograph provides a separate example of two small spacecraft prepared together. It does not depict SARE or demonstrate shared onboard resources. For a classroom design, sketch arrows between the sensor, storage and radio in the fictional system; then remove one arrow and explain which service stops. This exercise makes the promise and cost of distributed design visible: functions can be separated, but their interfaces become central to whether the overall mission works.