Developing Responsive and Agile Space Systems - Space-Library

Creating An Agile,
All-Space Architecture
Aerospace is working with the
Operationally Responsive Space
Office and other defense organizations
to develop a comprehensive space
architecture that will meet
urgent warfighter needs.
Thomas Adang and James Gee
For the past 40 years, the U.S. space architecture has been
focused on what is now referred to as “big space.” Most
space systems provide exquisite capability, but it takes 5–8
years to build and deploy each. The “small space” systems that were
developed and deployed more quickly were typically experimental
or research satellites, providing little to no operational capability.
Today, however, the increasingly complex role of space systems in all
aspects of peacekeeping and warfighting has created highly varied
needs for timeliness, persistence, data volume, and command and
control—and with combatant commanders requesting more regionally
focused space systems, small space is seen as an important
part of a broader space picture.
Defense planners have been increasingly vocal about the state of
U.S. space architecture, aware of the need for change. They are not
suggesting that the existing space architecture should be replaced;
rather, they argue for an evolutionary move toward a balanced
architecture that includes big and small space systems. Medium
and large systems would provide the foundational capability, while
small and less complex systems would provide additional capability
in high-demand areas and niche capability for special operations
and irregular needs. In short, the vision is for an agile “all space”
architecture that can accommodate rapid changes and deliver a full
spectrum of capabilities to the end user.
The Aerospace Corporation has supported big space for its entire
existence, and has contributed to many of the trailblazing achievements
in the small space arena. Drawing on this experience and
expertise, Aerospace is now providing technical leadership to the
development of an agile all-space architecture, working with all of
the DOD entities focused on this goal.
Building the Architecture
The pursuit of more agility in U.S. space architecture is not new.
In 2003, Air Force Space Command conducted an analysis of
alternatives to determine the cost-effectiveness of operationally
responsive launch and payload systems. The goal was to provide
transformational capabilities synchronized to warfighter needs. The
initial architecture was focused on incremental, spiral acquisition of
reusable first-stage boosters, expendable upper stages, and responsive
payloads. In 2005, the DOD Office of Force Transformation
defined operationally responsive space (ORS) as a new business
model, whereby space capabilities are designed for the operational
commanders who drive the demand, which in turn defines the
cost, risk, and mission-criticality. This model would require cheaper,
smaller satellites with single-mission payloads and far shorter life
spans. It was not designed to replace the larger space program, but
to complement it. The smaller, less expensive satellites would serve
as a testbed for larger space programs by providing a clear channel
for science and technology investments. They would also provide a
future ability to reconstitute larger space capabilities.
This effort led to the establishment of the tactical satellite (Tac-
Sat) program, with TacSats developed by the Air Force Research
Laboratory and Naval Research Laboratory. TacSats were envi-
6 • Crosslink Summer 2009