Search

Now that major assembly of the International Space Station (ISS) is complete, NASA's focus has turned to using this high fidelity in-space research testbed to not only advance fundamental science research, but also demonstrate and mature technologies and develop operational concepts that will enable future human exploration missions beyond low Earth orbit. The ISS as a Testbed for Analog Research (ISTAR) project was established to reduce risks for manned missions to exploration destinations by utilizing ISS as a high fidelity micro-g laboratory to demonstrate technologies, operations concepts, and techniques associated with crew autonomous operations. One of these focus areas is the development and execution of ISS Testbed for Analog Research (ISTAR) autonomous flight crew procedures intended to increase crew autonomy that will be required for long duration human exploration missions. Due to increasing communications delays and reduced logistics resupply, autonomous procedures are expected to help reduce crew reliance on the ground flight control team, increase crew performance, and enable the crew to become more subject-matter experts on both the exploration space vehicle systems and the scientific investigation operations that will be conducted on a long duration human space exploration mission. These tests make use of previous or ongoing projects tested in ground analogs such as Research and Technology Studies (RATS) and NASA Extreme Environment Mission Operations (NEEMO). Since the latter half of 2012, selected non-critical ISS systems crew procedures have been used to develop techniques for building ISTAR autonomous procedures, and ISS flight crews have successfully executed them without flight controller involvement. Although the main focus has been preparing for exploration, the ISS has been a beneficiary of this synergistic effort and is considering modifying additional standard ISS procedures that may increase crew efficiency, reduce operational costs, and raise the amount of crew time available for scientific research. The next phase of autonomous procedure development is expected to include payload science and human research investigations. Additionally, ISS International Partners have expressed interest in participating in this effort. The recently approved one-year crew expedition starting in 2015, consisting of one Russian and one U.S. Operating Segment (USOS) crewmember, will be used not only for long duration human research investigations but also for the testing of exploration operations concepts, including crew autonomy.

Final assembly of the International Space Station (ISS) was completed in 2011. As articulated in the 2011 NASA Strategic Plan, the Agency's first goal is to extend and sustain human activities across the solar system. Thus, the emerging NASA vision is to launch a bold and ambitious new space initiative to enable human space exploration beyond low-Earth orbit to Lagrange points, the moon, near-Earth asteroids (NEAs), and Mars and its environs. To accomplish this vision, it is necessary to develop and validate innovative exploration technologies and operational concepts. With the extended life of the ISS to 2020 and possibly 2028, NASA has a mandate to maximize the potential of the Nation's newest National Laboratory. Exploration and ISS teams within NASA's Human Exploration and Operations Mission Directorate (HEOMD) have initiated a cooperative effort: the ISS Testbed for Analog Research (ISTAR), a high-fidelity operational analog that complements existing NASA terrestrial laboratory and field testing. To maximize use of the ISS platform to evaluate new exploration technologies, capabilities, and operational concepts to better comprehend and mitigate human spaceflight risks, ISTAR seeks out and encourages investigations dubbed "exploration detailed test objectives" (xDTOs). These xDTOs, building blocks of ISTAR missions, develop and optimize the operations concepts and the use of new technologies that should reduce risks and challenges facing astronauts on long exploration spaceflight voyages. In this paper, we describe (1) the rationale behind ISTAR, (2) a five-year strategic plan, (3) the approach for mission formulation, development, integration, and execution, (4) concepts for near-term missions that implement a phased approach for using ISS as an exploration testbed, and (5) the planned Mars mission simulation using the ISS. This paper will also document several challenges ISTAR must address to execute its missions.

In 2004, the Vision for Space Exploration (VSE) was announced by the United States President's Administration in an effort to explore space and to extend a human presence across our solar system. Subsequently, the National Aeronautics and Space Administration (NASA) established the Exploration Systems Mission Directorate (ESMD) to develop a constellation of new capabilities, supporting technologies, and foundational research that allows for the sustained and affordable exploration of space. Then, ESMD specified the primary mission for the Constellation Program to carry out a series of human expeditions, ranging from Low Earth Orbit (LEO) to the surface of Moon, Mars, and beyond for the purposes of conducting human exploration of space. Thus, the Constellation Program was established at the Lyndon B. Johnson Space Center (JSC) to manage the development of the flight and ground infrastructure and systems that can enable continued and extended human access to space. Constellation Program's "Design Objectives" call for an early attention to the program's life cycle costs management through the Program's Need, Goals, and Objectives (NGO) document, which provides the vision, scope, and key areas of focus for the Program. One general policy of the Constellation Program, found in the Constellation Architecture Requirements Document (CARD), states: "A sustainable program hinges on how effectively total life cycle costs are managed. Developmental costs are a key consideration, but total life cycle costs related to the production, processing, and operation of the entire architecture must be accounted for in design decisions sufficiently to ensure future resources are available for ever more ambitious missions into the solar system...It is the intent of the Constellation Program to aggressively manage this aspect of the program using the design policies and simplicity." To respond to the Program's strong desire to manage the program life cycle costs, special efforts were established to identify operability requirements to influence flight vehicle and ground infrastructure design in order to impact the life cycle operations costs, and stretch goal requirements were introduced to the Program. This paper will describe how these stretch goal requirements were identified, developed, refined, matured, approved, and infused into the CARD. The paper will also document several challenges encountered when infusing the stretch goal requirements into the Constellation Program.

When there is spacecraft collaboration between several industry partners, there is an inherent difference in integration and test (I&T) methodologies, which creates a challenge for verifying flight systems during the development phase. To converge the differing I&T methodologies, considerations were required for multiple project areas such as Flight System Testbed (FST), Assembly, Test, and Launch Operations (ATLO), and Spacecraft Simulator environments. This paper details the challenges and approaches of the JPL's effort in engineering a solution to testing the flight system with the Mission Operations Ground System while maintaining the comparability with testing methods of the industry partners.

(MRO) on August 12, 2005. It carries six science instruments and three engineering payloads. Because MRO will produce an unprecedented number of science products, it will transmit a much higher data volume via high data rate than any other deep space mission to date. Keeping track of MRO products as well as relay products would be a daunting, expensive task without a well-planned data-product tracking strategy. To respond to this challenge, the MRO project developed the End-to- End Data Accountability System by utilizing existing information available from both ground and flight elements. Therefore, a capability to perform first-order problem diagnosis is essential in order for MRO to answer the questions, where is my data? and when will my data be available? This paper details the approaches taken, design and implementation of the tools, procedures and teams that track data products from the time they are predicted until they arrive in the hands of the end users.

A method for providing uniform transparent access to disparate distributed information systems was demonstrated. A prototype testing interface was developed to access documentation and information using publicly available hypermedia tools. The prototype gives testers a uniform, platform-independent user interface to on-line documentation, user manuals, and mission-specific test and operations data. Mosaic was the common user interface, and HTML (Hypertext Markup Language) provided hypertext capability.

A method for providing uniform transparent access to disparate distributed information systems was demonstrated. A prototype testing interface was developed to access documentation and information using publicly available hypermedia tools. The prototype gives testers a uniform, platform-independent user interface to on-line documentation, user manuals, and mission-specific test and operations data. Mosaic was the common user interface, and HTML (Hypertext Markup Language) provided hypertext capability.

SNMAT is rule-based expert-system computer program designed to assist personnel in monitoring status of computer network and identifying defective computers, workstations, and other components of network. Also assists in training network operators. Network for SNMAT located at Space Flight Operations Center (SFOC) at NASA's Jet Propulsion Laboratory. Intended to serve as data-reduction system providing windows, menus, and graphs, enabling users to focus on relevant information. SNMAT expected to be adaptable to other computer networks; for example in management of repair, maintenance, and security, or in administration of planning systems, billing systems, or archives.