Re:Orbital edge computing: nano satellite constellations as ...
by portillo on Monday October 12, 2020 @04:39PM
(#24759188)
I agree, this was the real reason why the project failed. Moreover, it was not clear at all that fractionation would bring any lifecycle costs savings, neither that any of the alleged extra flexibility (and maneuverability, resiliency, maintenability, and other -ilities) would result in any added value for the missions.
Fractionation is very hard,it introduces a lot of complexity in the design and interfaces, and it requires lots of coordination between multiple vendors. Project Ara by Google (a modular cellphone similar to Phoneblocks) also vouched for this idea of fractionation (and in fact was also led by Paul Ermenko) and was also cancelled.
The main problem came from the 4th F in F6, fractionated. The goal was to create a heterogenous network of satellites, built by a whole litany of manufacturers without even a common bus. That ended up being a solution in search of a problem. It made integration way more complex, which was exacerbated by the number of independent participants. The project spent a lot of time working on shared SDKs that would work across the constellation. In practice, there weren't really enough benefits over homogeneous constellations to make all the extra effort worthwhile. Instead of having 5 satellites with cameras beam their images to another satellite that determines which images are cloudy, it's easier to just have each satellite running identical code so it can figure out for itself which images are cloudy. On top of that, a homogenous network has advantages wrt survivability, manufacturing costs, maintenance, etc