Engineering topics
Publications and source records attributed to Reagan, Marc.
This presentation examines how problem solving was done on the NEEMO 22 Mission and whether human autonomy teaming would be able to assist in the type of troubleshooting that was conducted by Mission Control.
NEEMO is the NASA Extreme Environment Mission Operations, a cooperative project between NASA and the National Oceanic and Atmospheric Administration (NOAA). NEEMO was created and is managed by the Mission Operations Directorate at the Johnson Space Center in Houston, Texas. On the NOAA side, the National Undersea Research Center (NURC) in Key Largo, FL, with the help of the University of North Carolina at Wilmington, manages and operates the Aquarius Program. NEEMO was developed by astronaut training specialists to utilize an undersea research habitat as a multi-objective mission analog for long-duration space flight. Each mission was designed to expose astronauts to extreme environments for training purposes and to research crew behavior, habitability, and space analog life sciences. All of this was done much in the model of a space mission utilizing specific crew procedures, mission rules and timelines. Objectives of the missions were very diverse and contained many of the typical space mission type activities such as EV As (also known as extra vehicular activities), in-habitat science and research, and educational, public outreach, and media events. Five missions, dubbed NEEMO 1-5, were conducted between October 2001 and July 2003, the longest of which (NEEMO 5) lasted 14 days.
The highest level of training for ISS flight is Joint Multi-Segment Training (JMST) simulations. These simulations allow two or more partners to conduct multi-segment training for their respective Mission Control Centers (MCC), include actual crew members, and usually include training facilities in each of the participating International Partner (IP) locations. It is the dress rehearsal for those events that exercise the interface between different IP modules and/or the decision making process between the different MCCs involved. This presentation will describe the challenge of successfully implementing JMST. It will start with a brief overview of who is involved, where they are located, and when JMSTs are required. Finally, it will illustrate many of the complications involved in just running a JMST between MCC-M and MCC-H. The viewer will leave with a much better appreciation for the complexities involved in successfully conducting a JMST of this nature, as well as an idea of how the picture will change as the other partners and payloads become involved.