packaging materials and trash; and the ability to design, build, or repair
systems with common, modular components. To enable the journey to Mars,
NASA will invest in reusable systems with common components that are
modular and extensible to multiple missions to reduce unique developments
and the need for spares. Complex tradeoffs between resupply and use of insitu resources must be first addressed before we achieve Earth Independence.
NASA will use missions in the Proving Ground to validate new operational
approaches and learn how to balance logistics sent from Earth with the
potential benefits and challenges of using local resources.
The second challenge is recognition that achieving Earth Independence
will take decades and can be impacted by multiple uncertain events. NASA’s
strategy must be flexible and resilient to changes in the priorities of future
administrations, the emergence of breakthrough technologies, discovery
of new scientific knowledge, fluctuations in funding, and new partnership
opportunities. Due to these uncertainties, we must make decisions with
incomplete knowledge to ensure continued momentum. However, we
can plan for these changes proactively and design for uncertainty to be
better positioned when change occurs. We do this by designing a resilient
architecture that focuses on critical capabilities across a range of potential
missions, investing in technologies that provide large returns, and maximizing
flexibility and adaptability through commonality, modularity, and reusability.
The journey to Mars is only possible through multi-use, evolvable space
infrastructure that minimizes unique developments and associated cost. We
also ensure each mission leaves something behind to reduce the cost, risk, or
schedule for the next mission.
Features of a Resilient Pioneering Approach
Logistics
Modularity
Commonality
Extensibility
Affordability
Design to minimize the number of systems, use them multiple
times, refresh instead of replace them, and maintain with local
resources to enable self-sufficient missions.
Standardize for flexibility, simple interfaces to enhance complex
subsystems and components.
Develop systems that serve multiple purposes across the
campaign at many destinations.
Develop initial hardware with paths for enhanced applications.
Optimize system development across a campaign, not a mission
to minimize development costs.
12