EUVIMEDEUVIMED entdecken
Crossref

Why Large Spacecraft Swarms Will Be Maintained Primarily by Design, Not Solely by Control

Chenglong Xu

Aerospace Engineering Communications · 25.06.2026 · 1 (2) · 87-92

DOI: 10.62762/aec.2026.392649 ↗

Kurz gefasst

Fachartikel in der Zeitschrift Aerospace Engineering Communications, online erschienen am 25.06.2026. Verfasst von Chenglong Xu.

AbstractBibliografische AngabenZitierenVerwandte Studien

Abstract (Originalsprache)

As orbital swarms grow toward populations of tens to hundreds, long-term maintenance changes character. We argue that it is distinct from reconfiguration or trajectory planning, defined by two requirements: it is perpetual, and it must be low-frequency, because every active maneuver arc is stolen from the payload's working time. Against these requirements the three dominant paradigms: centralized planning, distributed reactive control, and configuration design-then-maintain, fail in qualitatively different ways. Two of these failures are structural, properties of how the problem is posed; only the third is fixable. We therefore contend that scalable swarm maintenance will be achieved primarily by design rather than by control alone, provided the design phase is reformulated to treat deployment cost and extensibility as first-class objectives. We close on the resulting open question: how to lift safety from a pairwise to a collective property so that its cost stops growing with the number of pairs.

Zitieren

APA

Xu, C. (2026). Why Large Spacecraft Swarms Will Be Maintained Primarily by Design, Not Solely by Control. Aerospace Engineering Communications, 1(2), 87-92. https://doi.org/10.62762/aec.2026.392649

Vancouver

Xu C. Why Large Spacecraft Swarms Will Be Maintained Primarily by Design, Not Solely by Control. Aerospace Engineering Communications. 2026;1(2):87-92. doi:10.62762/aec.2026.392649

BibTeX
@article{Xu2026,
  author = {Xu, Chenglong},
  title = {Why Large Spacecraft Swarms Will Be Maintained Primarily by Design, Not Solely by Control},
  journal = {Aerospace Engineering Communications},
  year = {2026},
  volume = {1},
  number = {2},
  pages = {87--92},
  doi = {10.62762/aec.2026.392649}
}
Kostenlos starten →