Mission Operations Directorate - Success Legacy of the Space Shuttle Program
Total Page:16
File Type:pdf, Size:1020Kb
https://ntrs.nasa.gov/search.jsp?R=20100030556 2019-08-30T11:10:21+00:00Z View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by NASA Technical Reports Server Mission Operations Directorate - Success Legacy of the Space Shuttle Program Jim Azbell Deputy Division Chief, Space Transportation Vehicle Division, Mission Operations Directorate NASA Lyndon B. Johnson Space Center, Houston, Texas 77058 In support of the Space Shuttle Program, as well as NASA’s other human space flight programs, the Mission Operations Directorate (MOD) at the Johnson Space Center has become the world leader in human spaceflight operations. From the earliest programs - Mercury, Gemini, Apollo - through Skylab, Shuttle, ISS, and our Exploration initiatives, MOD and its predecessors have pioneered ops concepts and emphasized a history of mission leadership which has added value, maximized mission success, and built on continual improvement of the capabilities to become more efficient and effective. MOD’s focus on building and contributing value with diverse teams has been key to their successes both with the US space industry and the broader international community. Since their beginning, MOD has consistently demonstrated their ability to evolve and respond to an ever changing environment, effectively prepare for the expected and successfully respond to the unexpected, and develop leaders, expertise, and a culture that has led to mission and Program success. MOD Background To better understand the evolution and successes of MOD during the Shuttle program, one must first understand the MOD’s current roles and responsibilities. MOD’s responsibilities traditionally fall into four categories: flight design and planning, crew and flight controller training, real-time flight execution, and facility operations. MOD is typically described as a “Plan-Train-Fly” organization with facilities support and utilization encompassing all of those aspects. Operational preparation consists of two types of planning and training: Generic and Flight Specific. Generic planning and training includes the development of nominal vehicle operating procedures, generic contingency procedures, and flight rules (e.g. generic operational procedures which are the same for every flight). It also includes development of basic flight systems knowledge, MCC tools usage, Flight Control Team processes and procedures, and generic training simulations leading to basic certification (e.g. generic flight control skills). Flight specific planning and training includes mission specific plans and procedures development, mission specific consumables analysis and planning, flight specific technique and payload training, and joint flight control team and crew mission simulations. A further explanation of MOD’s major functions and examples of efficiencies in these areas are covered in the following text. Plan The “Plan” part of MOD’s description includes mission concept definition, mission requirements integration, flight planning and mission timeline development, flight rules development, procedure development, international partner integration, flight design, and pre-mission analysis. As mentioned above, the planning aspects are divided into generic and flight specific functions. MOD has developed and is responsible for the generic operations knowledge baseline for all missions - an “operator’s manual” for human spaceflight systems. Over the course of the Shuttle Program, MOD has refined the generic operational aspects for the Shuttle missions, which has led to similar operational baselines for the ISS Program, as well as considerations for future human spaceflight programs. MOD has developed and NASA - Contractor Chief Engineers Council Montreal, Canada August 2010 Page 1 refined baseline operation procedures for both the vehicle and the MCC, including operating procedures for individual systems, and integrated activation and deactivation procedures. MOD has also capitalized on generic flight techniques and flight rules development. MOD has effectively been able to baseline the “best practices” and design generic operational techniques for complex tasks such as rendezvous, landing, and contingency responses. Through the development of their generic Flight Rules, MOD has been able to document critical decision paths for contingency scenarios, vehicle systems operating limits violations, redundancy management, and mission abort criteria. For the Shuttle Program, the Flight Director office (within MOD) chairs Flight Techniques Panels for both Orbit and Ascent/Entry operations. These panels have successfully served as the forums to discuss and implement changes as a result of vehicle issues, mission experiences, and lessons learned. Developing generic flight techniques and generic flight rules have been a critical mechanism for capturing lessons learned and enabling MOD to apply these experiences to not only the Shuttle program but to ISS and future programs as well. For flight specific planning, MOD is responsible for the development of all the flight-unique timelines, as well as the procedures and rules required by the specifics of a given mission. This includes the mission (crew) timelines, which details the mission related activity for each crew person for every minute of the crew day throughout the mission. This also includes the mission specific crew procedures (i.e. payload ops, ISS assembly, EVA procedures) and the flight specific Flight Rules. MOD is also responsible for the consumables planning and the mission specific flight design and trajectories. In addition, MOD is also responsible for producing flight specific “recon” products for the vehicle flight software load. Flight specific data loads, and command and telemetry loads are required by the design and architecture of the Shuttle flight systems. This “recon” process collects vehicle specific performance data, mission specific trajectory, and command/telemetry data definitions. MOD has continued to take advantage of their operational expertise, available tools and technology, and the generic operational baselines to make development of the flight specific products more efficient over the course of the Shuttle program. Like the use of generic operational baselines, common missions (e.g. ISS docked mission) and similar to previously flown missions (e.g. Hubble Space Telescope repair mission) have also made the development of flight specific products less demanding. Train Training is a little more straight forward and includes all of the activities involved with the crew and flight controller training, including lesson and curriculum design and development. Like the planning processes described above, MOD supports training for both generic and flight specific efforts. Training includes generic skill development for both crew and flight controllers, as well as the flight specific training required for each mission. Generic training is targeted for the new and less experienced flight controllers as well as the new astronaut candidates. Astronauts must complete generic crew training before becoming eligible for a flight assignment. Generic flight controller training culminates in a formal certification for a specific console position. Generic training (for both flight controllers and crew) consists of general spacecraft knowledge, overview of vehicle systems and operations, detailed systems knowledge base, failure signature recognition and response, procedure and flight rule familiarity, use of MCC tools and processes, and “soft skills” (situational awareness, communication, prioritization, etc.). MOD provides training through the development and delivery of lessons and training materials, including formal instruction and oversight during training and simulation activities. For flight specific training, the assigned crews and mission flight controllers receive additional training to become knowledgeable and proficient in the elements and objectives for that particular mission. Crews are exposed to detailed training for the onboard systems, tools, timeline activities, and mission specific tasks such as rendezvous and docking, payload deploy/retrieval, EVA, and Remote Manipulator Systems (RMS) operations. The assigned crew and the flight control team participate in slight specific integrated NASA - Contractor Chief Engineers Council Montreal, Canada August 2010 Page 2 simulations, with the crew in the simulator and the flight control team in the mission control center. These simulations consist of flight-like data flow, communications, and mission scenarios. These simulations function as a rehearsal of the mission timeline, including time-critical and highly integrated and choreographed events. These simulations also serve for the purposes of validating for the mission timeline and as opportunities to improve the teamwork and proficiency for the crew and ground control teams. Other centers (i.e. MSFC) and International Partners can also be ties into these flight specific simulations. Integration of the International Partners into these simulations, as well as mission decisions and execution, has been as challenge that the ISS Program has continued to wrestle with throughout their program. Until recently, Flight Control and Training within MOD had been separated into different and various Divisions. Understanding that the skill base and systems knowledge for Instructors and the Flight Controllers were similar, MOD looked for ways to manage this seemingly redundant expertise in a more efficient manner. In