As future missions travel to distance destinations such as Mars or asteroids, communication between the spacecraft and Earth will be delayed. This leads to the need for more independent spacecraft crews. The AMO Mission Operations (AMO) project demonstrates advanced software to help astronauts operate a component of ISS with less assistance from Earth.Principal Investigator(s)
NASA Ames Research Center, Moffett Field, CA, United States
Johnson Space Center, Houston, TX, United States
National Aeronautics and Space Administration (NASA)Sponsoring Organization
Human Exploration and Operations Mission Directorate (HEOMD)Research Benefits
Space ExplorationISS Expedition Duration:
September 2013 - September 2014Expeditions Assigned
37/38,39/40Previous ISS Missions
As future missions travel to distance destinations such as Mars or asteroids, communication between the spacecraft and Earth will be delayed. This leads to the need for more independent spacecraft crews. The Autonomous Mission Operations (AMO) project demonstrates advanced software to help astronauts operate their spacecraft with less assistance from Earth.
o Keeping track of what TOCA maintenance and sample analysis are required when
o Analyzing TOCA performance
o Determining if the level of organic carbons within the water is in or out of current trends.
o Hardware failure determination and recovery planning
One of the major goals of this study is to show that these additional tasks and hardware knowledge can be transferred onboard without increasing preflight training. Our hypothesis is that the software can augment crew knowledge and provide failure recognition capabilities. We will also test that the operational references embedded in the software are intuitive and easy to navigate in the event of an off nominal situation.
The AMO experiment is designed to integrate with established ground analyses and planning cycles to reduce risk to crew and equipment. For TOCA, all generated data used in analysis review will remain available to the ground analysis team, in addition to being used as inputs for the AMO software package onboard. Further, planning inputs provided by the Crew based on AMO software recommendations will be sent to the Operations Planning team in time for ground review prior to short term plan uplink.
Information PendingEarth Applications
Repeated from the IDRD Requirements above:
Each week there needs to be a 5 minute crew activity (AMO-TOCA PLAN) the day before the Weekly Planning Conference (WPC) for the crew to make their TOCA activity schedule recommendations to the ground. Since the ground knows what activities are already in the long term plan the ground has the “correct answer.” If the software was unable to provide the correct answer through the crew the ground can provide corrections required during the WPC.
After each of the following nominal TOCA activities there needs to be a 5-minute crew activity (AMO-TOCA-ANALYSIS) for to review the data analysis. At the end of this activity the crew will report if TOCA performance was nominal or off-nominal (and how) and if the TOC trend was in or out of trend. The time required to actually perform the TOCA activity is not charged to the experiment, only the 5-minute additional data review preceding.
There will be three 15-minute activities (AMO-SURVEY) spaced during the increment for the crew to provide feedback regarding the software.
|ActivityActivity||Duration||Execution Notes||Ops Notes|
|AMO-TOCA PLAN||00:05||Use AMO software to provide the ground with TOCA plan recommendations||Autonomous Mission Operations (AMO) TOCA Activity planning.|
|AMO-TOCA ANALYSIS||00:05||Use AMO Software to inform MCC-H if TOCA performance was nominal and if the TOC levels are within current ISS trends. If off-nominal performance or TOC levels is suspected provide MCC-H with a next step recommendation. (Voice or crew note)||Autonomous Mission Operations (AMO) Total Organic Carbon Analyzer (TOCA) Analysis|
|AMO-TOCA CAL||00:05||Use AMO Software to inform MCC-H if TOCA performance was nominal during the preceding calibration or calibration check activity. If off-nominal performance is suspected provide MCC-H with a next step recommendation. (Voice or crew note)||Autonomous Mission Operations (AMO) Total Organic Carbon Analyzer (TOCA) Analysis|
|AMO-SURVEY||00:15||TBS||Autonomous Mission Operations (AMO) crew survey.|
Lastly near the end of the increment there will be a planned off-nominal scenario consisting of the crew attempting a sample bag analysis for an under-filled bag. This entire analysis activity should be charged to the experiment because it will be above and beyond what is required for ISS maintenance. Once the analysis fails early, TOCA will need to be re-primed and that time will also be charged to the experiment. The AMO team will work with the increment Ops Planning team to get these activities into the timeline correctly. One of the three, 15-minute survey activities should be planned shortly after this planned scenario to aid with data collection.
Once the AMO experiment begins it is highly desired to schedule all TOCA-related activities for the crew members involved with the AMO experiment. Thus after crew handover is complete all TOCA activities should be schedule for the 37S USOS crew (Mastracchio and Wakata) and not for the 36S crew (Hopkins).
If a long term plan is uplinked to the crew for any reason beyond the time period the crew has provided TOCA activity recommendations it is highly desired that all TOCA related activities be shown as blank placeholders to not provide the answer to the crew.
The AMO experiment has also requested 30 minutes of crew time to allow the crew to work through any off-nominal unplanned TOCA-related faults with the AMO software as the timeline permits.
Using the expected number of TOCA runs during the increment this equates to 6.5 hours of minimal crew time and 0.6 hours of additiona crew time (7.1 hours noimnal total).
AMO will also be working with OCA to schedule automated daily uplink of the current schedule to the AMO software and daily downlink of software log files. These activities do not require crew time.Operational Protocols