Developing a corss-project support system during mission operations: Deep Space 1 extended mission flight control

NASA Technical Reports Server (NTRS)

Scarffe, V. A.

2002-01-01

NASA is focusing on small, low-cost spacecraft for both planetary and earth science missions. Deep Space 1 (DS1) was the first mission to be launched by the NMP. The New Millennium Project (NMP) is designed to develop and test new technology that can be used on future science missions with lower cost and risk. The NMP is finding ways to reduce cost not only in development, but also in operations. DS 1 was approved for an extended mission, but the budget was not large, so the project began looking into part time team members shared with other projects. DS1 launched on October 24, 1998, in it's primary mission it successfully tested twelve new technologies. The extended mission started September 18, 1999 and ran through the encounter with Comet Borrelly on September 22,2001. The Flight Control Team (FCT) was one team that needed to use part time or multi mission people. Circumstances led to a situation where for the few months before the Borrelly encounter in September of 2001 DSl had no certified full time Flight Control Engineers also known as Aces. This paper examines how DS 1 utilized cross-project support including the communication between different projects, and the how the tools used by the Flight Control Engineer fit into cross-project support.

Autonomous Mission Operations Roadmap

NASA Technical Reports Server (NTRS)

Frank, Jeremy David

2014-01-01

As light time delays increase, the number of such situations in which crew autonomy is the best way to conduct the mission is expected to increase. However, there are significant open questions regarding which functions to allocate to ground and crew as the time delays increase. In situations where the ideal solution is to allocate responsibility to the crew and the vehicle, a second question arises: should the activity be the responsibility of the crew or an automated vehicle function? More specifically, we must answer the following questions: What aspects of mission operation responsibilities (Plan, Train, Fly) should be allocated to ground based or vehicle based planning, monitoring, and control in the presence of significant light-time delay between the vehicle and the Earth?How should the allocated ground based planning, monitoring, and control be distributed across the flight control team and ground system automation? How should the allocated vehicle based planning, monitoring, and control be distributed between the flight crew and onboard system automation?When during the mission should responsibility shift from flight control team to crew or from crew to vehicle, and what should the process of shifting responsibility be as the mission progresses? NASA is developing a roadmap of capabilities for Autonomous Mission Operations for human spaceflight. This presentation will describe the current state of development of this roadmap, with specific attention to in-space inspection tasks that crews might perform with minimum assistance from the ground.

IRIS Mission Operations Director's Colloquium

NASA Technical Reports Server (NTRS)

Carvalho, Robert; Mazmanian, Edward A.

2014-01-01

Pursuing the Mysteries of the Sun: The Interface Region Imaging Spectrograph (IRIS) Mission. Flight controllers from the IRIS mission will present their individual experiences on IRIS from development through the first year of flight. This will begin with a discussion of the unique nature of IRISs mission and science, and how it fits into NASA's fleet of solar observatories. Next will be a discussion of the critical roles Ames contributed in the mission including spacecraft and flight software development, ground system development, and training for launch. This will be followed by experiences from launch, early operations, ongoing operations, and unusual operations experiences. The presentation will close with IRIS science imagery and questions.

Rosetta mission operations for landing

NASA Astrophysics Data System (ADS)

Accomazzo, Andrea; Lodiot, Sylvain; Companys, Vicente

2016-08-01

The International Rosetta Mission of the European Space Agency (ESA) was launched on 2nd March 2004 on its 10 year journey to comet Churyumov-Gerasimenko and has reached it early August 2014. The main mission objectives were to perform close observations of the comet nucleus throughout its orbit around the Sun and deliver the lander Philae to its surface. This paper describers the activities at mission operations level that allowed the landing of Philae. The landing preparation phase was mainly characterised by the definition of the landing selection process, to which several parties contributed, and by the definition of the strategy for comet characterisation, the orbital strategy for lander delivery, and the definition and validation of the operations timeline. The definition of the landing site selection process involved almost all components of the mission team; Rosetta has been the first, and so far only mission, that could not rely on data collected by previous missions for the landing site selection. This forced the teams to include an intensive observation campaign as a mandatory part of the process; several science teams actively contributed to this campaign thus making results from science observations part of the mandatory operational products. The time allocated to the comet characterisation phase was in the order of a few weeks and all the processes, tools, and interfaces required an extensive planning an validation. Being the descent of Philae purely ballistic, the main driver for the orbital strategy was the capability to accurately control the position and velocity of Rosetta at Philae's separation. The resulting operations timeline had to merge this need of frequent orbit determination and control with the complexity of the ground segment and the inherent risk of problems when doing critical activities in short times. This paper describes the contribution of the Mission Control Centre (MOC) at the European Space Operations Centre (ESOC) to this

Shuttle remote manipulator system mission preparation and operations

NASA Technical Reports Server (NTRS)

Smith, Ernest E., Jr.

1989-01-01

The preflight planning, analysis, procedures development, and operations support for the Space Transportation System payload deployment and retrieval missions utilizing the Shuttle Remote Manipulator System are summarized. Analysis of the normal operational loads and failure induced loads and motion are factored into all procedures. Both the astronaut flight crews and the Mission Control Center flight control teams receive considerable training for standard and mission specific operations. The real time flight control team activities are described.

APOLLO XIII CREW - MISSION OPERATIONS CONTROL ROOM (MOCR) - APOLLO XII - LUNAR EXTRAVEHICULAR ACTIVITY (EVA) - MSC

NASA Image and Video Library

1969-11-21

S69-59525 (19 Nov. 1969) --- Overall view of activity in the Mission Operations Control Room (MOCR) in the Mission Control Center (MCC), Building 30, during the Apollo 12 lunar landing mission. When this picture was made the first Apollo 12 extravehicular activity (EVA) was being televised from the surface of the moon. Photo credit: NASA

Mission control team structure and operational lessons learned from the 2009 and 2010 NASA desert RATS simulated lunar exploration field tests

NASA Astrophysics Data System (ADS)

Bell, Ernest R.; Badillo, Victor; Coan, David; Johnson, Kieth; Ney, Zane; Rosenbaum, Megan; Smart, Tifanie; Stone, Jeffry; Stueber, Ronald; Welsh, Daren; Guirgis, Peggy; Looper, Chris; McDaniel, Randall

2013-10-01

The NASA Desert Research and Technology Studies (Desert RATS) is an annual field test of advanced concepts, prototype hardware, and potential modes of operation to be used on human planetary surface space exploration missions. For the 2009 and 2010 NASA Desert RATS field tests, various engineering concepts and operational exercises were incorporated into mission timelines with the focus of the majority of daily operations being on simulated lunar geological field operations and executed in a manner similar to current Space Shuttle and International Space Station missions. The field test for 2009 involved a two week lunar exploration simulation utilizing a two-man rover. The 2010 Desert RATS field test took this two week simulation further by incorporating a second two-man rover working in tandem with the 2009 rover, as well as including docked operations with a Pressurized Excursion Module (PEM). Personnel for the field test included the crew, a mission management team, engineering teams, a science team, and the mission operations team. The mission operations team served as the core of the Desert RATS mission control team and included certified NASA Mission Operations Directorate (MOD) flight controllers, former flight controllers, and astronaut personnel. The backgrounds of the flight controllers were in the areas of Extravehicular Activity (EVA), onboard mechanical systems and maintenance, robotics, timeline planning (OpsPlan), and spacecraft communicator (Capcom). With the simulated EVA operations, mechanized operations (the rover), and expectations of replanning, these flight control disciplines were especially well suited for the execution of the 2009 and 2010 Desert RATS field tests. The inclusion of an operations team has provided the added benefit of giving NASA mission operations flight control personnel the opportunity to begin examining operational mission control techniques, team compositions, and mission scenarios. This also gave the mission operations

MISSION CONTROL CENTER (MCC) - CELEBRATION - CONCLUSION - APOLLO 11 MISSION - MSC

NASA Image and Video Library

1969-07-25

S69-40023 (24 July 1969) --- Overall view of the Mission Operations Control Room (MOCR) in the Mission Control Center (MCC), Building 30, Manned Spacecraft Center (MSC), showing the flight controllers celebrating the successful conclusion of the Apollo 11 lunar landing mission.

(abstract) Mission Operations and Control Assurance: Flight Operations Quality Improvements

NASA Technical Reports Server (NTRS)

Welz, Linda L.; Bruno, Kristin J.; Kazz, Sheri L.; Witkowski, Mona M.

1993-01-01

Mission Operations and Command Assurance (MO&CA), a recent addition to flight operations teams at JPL. provides a system level function to instill quality in mission operations. MO&CA's primary goal at JPL is to help improve the operational reliability for projects during flight. MO&CA tasks include early detection and correction of process design and procedural deficiencies within projects. Early detection and correction are essential during development of operational procedures and training of operational teams. MO&CA's effort focuses directly on reducing the probability of radiating incorrect commands to a spacecraft. Over the last seven years at JPL, MO&CA has become a valuable asset to JPL flight projects. JPL flight projects have benefited significantly from MO&CA's efforts to contain risk and prevent rather than rework errors. MO&CA's ability to provide direct transfer of knowledge allows new projects to benefit directly from previous and ongoing experience. Since MO&CA, like Total Quality Management (TQM), focuses on continuous improvement of processes and elimination of rework, we recommend that this effort be continued on NASA flight projects.

Low Cost Mission Operations Workshop. [Space Missions

NASA Technical Reports Server (NTRS)

1994-01-01

The presentations given at the Low Cost (Space) Mission Operations (LCMO) Workshop are outlined. The LCMO concepts are covered in four introductory sections: Definition of Mission Operations (OPS); Mission Operations (MOS) Elements; The Operations Concept; and Mission Operations for Two Classes of Missions (operationally simple and complex). Individual presentations cover the following topics: Science Data Processing and Analysis; Mis sion Design, Planning, and Sequencing; Data Transport and Delivery, and Mission Coordination and Engineering Analysis. A list of panelists who participated in the conference is included along with a listing of the contact persons for obtaining more information concerning LCMO at JPL. The presentation of this document is in outline and graphic form.

Activities at the JSC Payload Operations Control Center During Spacelab Mission

NASA Technical Reports Server (NTRS)

1984-01-01

During a Spacelab flight, the hub of activity was the Payload Operations Control Center (POCC) at the Johnson Space Flight Center (JSC) in Houston, Texas. The POCC became home to the management and science teams who worked around the clock to guide and support the mission. All Spacelab principal investigators and their teams of scientists and engineers set up work areas in the POCC. Through the use of computers, they could send commands to their instruments and receive and analyze experiment data. Instantaneous video and audio communications made it possible for scientists on the ground to follow the progress of their research almost as if they were in space with the crew. This real-time interaction between investigators on the ground and the crew in space was probably the most exciting of Spacelab's many capabilities. As principal investigators talked to the payload specialists during the mission, they consulted on experiment operations, made decisions, and shared in the thrill of gaining new knowledge. In December 1990, a newly-established POCC at the Marshall Space Flight Center (MSFC) opened its door for the operations of the Spacelab payloads and experiments, while JSC monitored the Shuttle flight operations. MSFC had managing responsibilities for the Spacelab missions.

Architectures for mission control at the Jet Propulsion Laboratory

NASA Technical Reports Server (NTRS)

Davidson, Reger A.; Murphy, Susan C.

1992-01-01

JPL is currently converting to an innovative control center data system which is a distributed, open architecture for telemetry delivery and which is enabling advancement towards improved automation and operability, as well as new technology, in mission operations at JPL. The scope of mission control within mission operations is examined. The concepts of a mission control center and how operability can affect the design of a control center data system are discussed. Examples of JPL's mission control architecture, data system development, and prototype efforts at the JPL Operations Engineering Laboratory are provided. Strategies for the future of mission control architectures are outlined.

Spitzer observatory operations: increasing efficiency in mission operations

NASA Astrophysics Data System (ADS)

Scott, Charles P.; Kahr, Bolinda E.; Sarrel, Marc A.

2006-06-01

This paper explores the how's and why's of the Spitzer Mission Operations System's (MOS) success, efficiency, and affordability in comparison to other observatory-class missions. MOS exploits today's flight, ground, and operations capabilities, embraces automation, and balances both risk and cost. With operational efficiency as the primary goal, MOS maintains a strong control process by translating lessons learned into efficiency improvements, thereby enabling the MOS processes, teams, and procedures to rapidly evolve from concept (through thorough validation) into in-flight implementation. Operational teaming, planning, and execution are designed to enable re-use. Mission changes, unforeseen events, and continuous improvement have often times forced us to learn to fly anew. Collaborative spacecraft operations and remote science and instrument teams have become well integrated, and worked together to improve and optimize each human, machine, and software-system element. Adaptation to tighter spacecraft margins has facilitated continuous operational improvements via automated and autonomous software coupled with improved human analysis. Based upon what we now know and what we need to improve, adapt, or fix, the projected mission lifetime continues to grow - as does the opportunity for numerous scientific discoveries.

A Virtual Mission Operations Center: Collaborative Environment

NASA Technical Reports Server (NTRS)

Medina, Barbara; Bussman, Marie; Obenschain, Arthur F. (Technical Monitor)

2002-01-01

The Virtual Mission Operations Center - Collaborative Environment (VMOC-CE) intent is to have a central access point for all the resources used in a collaborative mission operations environment to assist mission operators in communicating on-site and off-site in the investigation and resolution of anomalies. It is a framework that as a minimum incorporates online chat, realtime file sharing and remote application sharing components in one central location. The use of a collaborative environment in mission operations opens up the possibilities for a central framework for other project members to access and interact with mission operations staff remotely. The goal of the Virtual Mission Operations Center (VMOC) Project is to identify, develop, and infuse technology to enable mission control by on-call personnel in geographically dispersed locations. In order to achieve this goal, the following capabilities are needed: Autonomous mission control systems Automated systems to contact on-call personnel Synthesis and presentation of mission control status and history information Desktop tools for data and situation analysis Secure mechanism for remote collaboration commanding Collaborative environment for remote cooperative work The VMOC-CE is a collaborative environment that facilitates remote cooperative work. It is an application instance of the Virtual System Design Environment (VSDE), developed by NASA Goddard Space Flight Center's (GSFC) Systems Engineering Services & Advanced Concepts (SESAC) Branch. The VSDE is a web-based portal that includes a knowledge repository and collaborative environment to serve science and engineering teams in product development. It is a "one stop shop" for product design, providing users real-time access to product development data, engineering and management tools, and relevant design specifications and resources through the Internet. The initial focus of the VSDE has been to serve teams working in the early portion of the system

View of Mission Control Center celebrating conclusion of Apollo 11 mission

NASA Image and Video Library

1969-07-25

S69-40022 (24 July 1969) --- Overall view of the Mission Operations Control Room (MOCR) in the Mission Control Center (MCC), Building 30, Manned Spacecraft Center (MSC), showing the flight controllers celebrating the successful conclusion of the Apollo 11 lunar landing mission.

Activities During Spacelab-J Mission at Payload Operations and Control Center

NASA Technical Reports Server (NTRS)

1992-01-01

The group of Japanese researchers of the Spacelab-J (SL-J) were thumbs-up in the Payload Operations Control Center (POCC) at the Marshall Space Flight Center after the successful launch of Space Shuttle Orbiter Endeavour that carried their experiments. The SL-J was a joint mission of NASA and the National Space Development Agency of Japan (NASDA) utilizing a marned Spacelab module. The mission conducted microgravity investigations in materials and life sciences. Materials science investigations covered such fields as biotechnology, electronic materials, fluid dynamics and transport phenomena, glasses and ceramics, metals and alloys, and acceleration measurements. Life sciences included experiments on human health, cell separation and biology, developmental biology, animal and human physiology and behavior, space radiation, and biological rhythms. Test subjects included the crew, Japanese koi fish (carp), cultured animal and plant cells, chicken embryos, fruit flies, fungi and plant seeds, frogs, and frog eggs. The POCC was the air/ground communications channel between the astronauts and ground control teams during the Spacelab missions. The Spacelab science operations were a cooperative effort between the science astronaut crew in orbit and their colleagues in the POCC. Spacelab-J was launched aboard the Space Shuttle Orbiter Endeavour on September 12, 1992.

Mission operations management

NASA Technical Reports Server (NTRS)

Rocco, David A.

1994-01-01

Redefining the approach and philosophy that operations management uses to define, develop, and implement space missions will be a central element in achieving high efficiency mission operations for the future. The goal of a cost effective space operations program cannot be realized if the attitudes and methodologies we currently employ to plan, develop, and manage space missions do not change. A management philosophy that is in synch with the environment in terms of budget, technology, and science objectives must be developed. Changing our basic perception of mission operations will require a shift in the way we view the mission. This requires a transition from current practices of viewing the mission as a unique end product, to a 'mission development concept' built on the visualization of the end-to-end mission. To achieve this change we must define realistic mission success criteria and develop pragmatic approaches to achieve our goals. Custom mission development for all but the largest and most unique programs is not practical in the current budget environment, and we simply do not have the resources to implement all of our planned science programs. We need to shift our management focus to allow us the opportunity make use of methodologies and approaches which are based on common building blocks that can be utilized in the space, ground, and mission unique segments of all missions.

View of Mission Control during Apollo 9 earth orbital mission

NASA Image and Video Library

1969-03-03

S69-26301 (March 1969) --- Overall view of the Mission Operations Control Room in the Mission Control Center, Building 30, during the Apollo 9 Earth-orbital mission. When this photograph was taken a live television transmission was being received from Apollo 9 as it orbited Earth.

Integrated payload and mission planning, phase 3. Volume 3: Ground real-time mission operations

NASA Technical Reports Server (NTRS)

White, W. J.

1977-01-01

The payloads tentatively planned to fly on the first two Spacelab missions were analyzed to examine the cost relationships of providing mission operations support from onboard vs the ground-based Payload Operations Control Center (POCC). The quantitative results indicate that use of a POCC, with data processing capability, to support real-time mission operations is the most cost effective case.

Advancing Autonomous Operations Technologies for NASA Missions

NASA Technical Reports Server (NTRS)

Cruzen, Craig; Thompson, Jerry Todd

2013-01-01

This paper discusses the importance of implementing advanced autonomous technologies supporting operations of future NASA missions. The ability for crewed, uncrewed and even ground support systems to be capable of mission support without external interaction or control has become essential as space exploration moves further out into the solar system. The push to develop and utilize autonomous technologies for NASA mission operations stems in part from the need to reduce operations cost while improving and increasing capability and safety. This paper will provide examples of autonomous technologies currently in use at NASA and will identify opportunities to advance existing autonomous technologies that will enhance mission success by reducing operations cost, ameliorating inefficiencies, and mitigating catastrophic anomalies.

The Virtual Mission Operations Center

NASA Technical Reports Server (NTRS)

Moore, Mike; Fox, Jeffrey

1994-01-01

Spacecraft management is becoming more human intensive as spacecraft become more complex and as operations costs are growing accordingly. Several automation approaches have been proposed to lower these costs. However, most of these approaches are not flexible enough in the operations processes and levels of automation that they support. This paper presents a concept called the Virtual Mission Operations Center (VMOC) that provides highly flexible support for dynamic spacecraft management processes and automation. In a VMOC, operations personnel can be shared among missions, the operations team can change personnel and their locations, and automation can be added and removed as appropriate. The VMOC employs a form of on-demand supervisory control called management by exception to free operators from having to actively monitor their system. The VMOC extends management by exception, however, so that distributed, dynamic teams can work together. The VMOC uses work-group computing concepts and groupware tools to provide a team infrastructure, and it employs user agents to allow operators to define and control system automation.

Modeling Real-Time Coordination of Distributed Expertise and Event Response in NASA Mission Control Center Operations

NASA Astrophysics Data System (ADS)

Onken, Jeffrey

This dissertation introduces a multidisciplinary framework for the enabling of future research and analysis of alternatives for control centers for real-time operations of safety-critical systems. The multidisciplinary framework integrates functional and computational models that describe the dynamics in fundamental concepts of previously disparate engineering and psychology research disciplines, such as group performance and processes, supervisory control, situation awareness, events and delays, and expertise. The application in this dissertation is the real-time operations within the NASA Mission Control Center in Houston, TX. This dissertation operationalizes the framework into a model and simulation, which simulates the functional and computational models in the framework according to user-configured scenarios for a NASA human-spaceflight mission. The model and simulation generates data according to the effectiveness of the mission-control team in supporting the completion of mission objectives and detecting, isolating, and recovering from anomalies. Accompanying the multidisciplinary framework is a proof of concept, which demonstrates the feasibility of such a framework. The proof of concept demonstrates that variability occurs where expected based on the models. The proof of concept also demonstrates that the data generated from the model and simulation is useful for analyzing and comparing MCC configuration alternatives because an investigator can give a diverse set of scenarios to the simulation and the output compared in detail to inform decisions about the effect of MCC configurations on mission operations performance.

Evolution of Training in NASA's Mission Operations Directorate

NASA Technical Reports Server (NTRS)

Hutt, Jason

2012-01-01

NASA s Mission Operations Directorate provides all the mission planning, training, and operations support for NASA's human spaceflight missions including the International Space Station (ISS) and its fleet of supporting vehicles. MOD also develops and maintains the facilities necessary to conduct training and operations for those missions including the Mission Control Center, Space Station Training Facility, Space Vehicle Mockup Facility, and Neutral Buoyancy Laboratory. MOD's overarching approach to human spaceflight training is to "train like you fly." This approach means not only trying to replicate the operational environment in training but also to approach training with the same mindset as real operations. When in training, this means using the same approach for executing operations, responding to off-nominal situations, and conducting yourself in the operations environment in the same manner as you would for the real vehicle.

SPOT satellite family: Past, present, and future of the operations in the mission and control center

NASA Technical Reports Server (NTRS)

Philippe, Pacholczyk

1993-01-01

SPOT sun-synchronous remote sensing satellites are operated by CNES since February 1986. Today, the SPOT mission and control center (CCM) operates SPOT1, SPOT2, and is ready to operate SPOT3. During these seven years, the way to operate changed and the CCM, initially designed for the control of one satellite, has been modified and upgraded to support these new operating modes. All these events have shown the performances and the limits of the system. A new generation of satellite (SPOT4) will continue the remote sensing mission during the second half of the 90's. Its design takes into account the experience of the first generation and supports several improvements. A new generation of control center (CMP) has been developed and improves the efficiency, quality, and reliability of the operations. The CMP is designed for operating two satellites at the same time during launching, in-orbit testing, and operating phases. It supports several automatic procedures and improves data retrieval and reporting.

Flight Operations . [Zero Knowledge to Mission Complete

NASA Technical Reports Server (NTRS)

Forest, Greg; Apyan, Alex; Hillin, Andrew

2016-01-01

Outline the process that takes new hires with zero knowledge all the way to the point of completing missions in Flight Operations. Audience members should be able to outline the attributes of a flight controller and instructor, outline the training flow for flight controllers and instructors, and identify how the flight controller and instructor attributes are necessary to ensure operational excellence in mission prep and execution. Identify how the simulation environment is used to develop crisis management, communication, teamwork, and leadership skills for SGT employees beyond what can be provided by classroom training.

Mission Control Center at conclusion of Apollo 15 lunar landing mission

NASA Image and Video Library

1971-08-07

An overall view of activity in the Mission Operations Control Room in the Mission Control Center at the conclusion of the Apollo 15 lunar landing mission. The television monitor in the right background shows the welcome ceremonies aboard the prime recovery ship, U.S.S. Okinawa, in the mid-Pacific Ocean.

The Right Stuff: A Look Back at Three Decades of Flight Controller Training for Space Shuttle Mission Operations

NASA Technical Reports Server (NTRS)

Dittemore, Gary D.; Bertels, Christie

2010-01-01

This paper will summarize the thirty-year history of Space Shuttle operations from the perspective of training in NASA Johnson Space Center's Mission Control Center. It will focus on training and development of flight controllers and instructors, and how training practices have evolved over the years as flight experience was gained, new technologies developed, and programmatic needs changed. Operations of human spaceflight systems is extremely complex, therefore the training and certification of operations personnel is a critical piece of ensuring mission success. Mission Control Center (MCC-H), at the Lyndon B. Johnson Space Center, in Houston, Texas manages mission operations for the Space Shuttle Program, including the training and certification of the astronauts and flight control teams. This paper will give an overview of a flight control team s makeup and responsibilities during a flight, and details on how those teams are trained and certified. The training methodology for developing flight controllers has evolved significantly over the last thirty years, while the core goals and competencies have remained the same. In addition, the facilities and tools used in the control center have evolved. These changes have been driven by many factors including lessons learned, technology, shuttle accidents, shifts in risk posture, and generational differences. Flight controllers will share their experiences in training and operating the Space Shuttle throughout the Program s history. A primary method used for training Space Shuttle flight control teams is by running mission simulations of the orbit, ascent, and entry phases, to truly "train like you fly." The audience will learn what it is like to perform a simulation as a shuttle flight controller. Finally, we will reflect on the lessons learned in training for the shuttle program, and how those could be applied to future human spaceflight endeavors.

Web Design for Space Operations: An Overview of the Challenges and New Technologies Used in Developing and Operating Web-Based Applications in Real-Time Operational Support Onboard the International Space Station, in Astronaut Mission Planning and Mission Control Operations

NASA Technical Reports Server (NTRS)

Khan, Ahmed

2010-01-01

The International Space Station (ISS) Operations Planning Team, Mission Control Centre and Mission Automation Support Network (MAS) have all evolved over the years to use commercial web-based technologies to create a configurable electronic infrastructure to manage the complex network of real-time planning, crew scheduling, resource and activity management as well as onboard document and procedure management required to co-ordinate ISS assembly, daily operations and mission support. While these Web technologies are classified as non-critical in nature, their use is part of an essential backbone of daily operations on the ISS and allows the crew to operate the ISS as a functioning science laboratory. The rapid evolution of the internet from 1998 (when ISS assembly began) to today, along with the nature of continuous manned operations in space, have presented a unique challenge in terms of software engineering and system development. In addition, the use of a wide array of competing internet technologies (including commercial technologies such as .NET and JAVA ) and the special requirements of having to support this network, both nationally among various control centres for International Partners (IPs), as well as onboard the station itself, have created special challenges for the MCC Web Tools Development Team, software engineers and flight controllers, who implement and maintain this system. This paper presents an overview of some of these operational challenges, and the evolving nature of the solutions and the future use of COTS based rich internet technologies in manned space flight operations. In particular this paper will focus on the use of Microsoft.s .NET API to develop Web-Based Operational tools, the use of XML based service oriented architectures (SOA) that needed to be customized to support Mission operations, the maintenance of a Microsoft IIS web server onboard the ISS, The OpsLan, functional-oriented Web Design with AJAX

The Final Count Down: A Review of Three Decades of Flight Controller Training Methods for Space Shuttle Mission Operations

NASA Technical Reports Server (NTRS)

Dittermore, Gary; Bertels, Christie

2011-01-01

Operations of human spaceflight systems is extremely complex; therefore, the training and certification of operations personnel is a critical piece of ensuring mission success. Mission Control Center (MCC-H), at the Lyndon B. Johnson Space Center in Houston, Texas, manages mission operations for the Space Shuttle Program, including the training and certification of the astronauts and flight control teams. An overview of a flight control team s makeup and responsibilities during a flight, and details on how those teams are trained and certified, reveals that while the training methodology for developing flight controllers has evolved significantly over the last thirty years the core goals and competencies have remained the same. In addition, the facilities and tools used in the control center have evolved. Changes in methodology and tools have been driven by many factors, including lessons learned, technology, shuttle accidents, shifts in risk posture, and generational differences. Flight controllers share their experiences in training and operating the space shuttle. The primary training method throughout the program has been mission simulations of the orbit, ascent, and entry phases, to truly train like you fly. A review of lessons learned from flight controller training suggests how they could be applied to future human spaceflight endeavors, including missions to the moon or to Mars. The lessons learned from operating the space shuttle for over thirty years will help the space industry build the next human transport space vehicle.

Calculation of Operations Efficiency Factors for Mars Surface Missions

NASA Technical Reports Server (NTRS)

Laubach, Sharon

2014-01-01

The duration of a mission--and subsequently, the minimum spacecraft lifetime--is a key component in designing the capabilities of a spacecraft during mission formulation. However, determining the duration is not simply a function of how long it will take the spacecraft to execute the activities needed to achieve mission objectives. Instead, the effects of the interaction between the spacecraft and ground operators must also be taken into account. This paper describes a method, using "operations efficiency factors", to account for these effects for Mars surface missions. Typically, this level of analysis has not been performed until much later in the mission development cycle, and has not been able to influence mission or spacecraft design. Further, the notion of moving to sustainable operations during Prime Mission--and the effect that change would have on operations productivity and mission objective choices--has not been encountered until the most recent rover missions (MSL, the (now-cancelled) joint NASA-ESA 2018 Mars rover, and the proposed rover for Mars 2020). Since MSL had a single control center and sun-synchronous relay assets (like MER), estimates of productivity derived from MER prime and extended missions were used. However, Mars 2018's anticipated complexity (there would have been control centers in California and Italy, and a non-sun-synchronous relay asset) required the development of an explicit model of operations efficiency that could handle these complexities. In the case of the proposed Mars 2018 mission, the model was employed to assess the mission return of competing operations concepts, and as an input to component lifetime requirements. In this paper we provide examples of how to calculate the operations efficiency factor for a given operational configuration, and how to apply the factors to surface mission scenarios. This model can be applied to future missions to enable early effective trades between operations design, science mission

Integrated Human-Robotic Missions to the Moon and Mars: Mission Operations Design Implications

NASA Technical Reports Server (NTRS)

Mishkin, Andrew; Lee, Young; Korth, David; LeBlanc, Troy

2007-01-01

For most of the history of space exploration, human and robotic programs have been independent, and have responded to distinct requirements. The NASA Vision for Space Exploration calls for the return of humans to the Moon, and the eventual human exploration of Mars; the complexity of this range of missions will require an unprecedented use of automation and robotics in support of human crews. The challenges of human Mars missions, including roundtrip communications time delays of 6 to 40 minutes, interplanetary transit times of many months, and the need to manage lifecycle costs, will require the evolution of a new mission operations paradigm far less dependent on real-time monitoring and response by an Earthbound operations team. Robotic systems and automation will augment human capability, increase human safety by providing means to perform many tasks without requiring immediate human presence, and enable the transfer of traditional mission control tasks from the ground to crews. Developing and validating the new paradigm and its associated infrastructure may place requirements on operations design for nearer-term lunar missions. The authors, representing both the human and robotic mission operations communities, assess human lunar and Mars mission challenges, and consider how human-robot operations may be integrated to enable efficient joint operations, with the eventual emergence of a unified exploration operations culture.

Integrated Human-Robotic Missions to the Moon and Mars: Mission Operations Design Implications

NASA Technical Reports Server (NTRS)

Korth, David; LeBlanc, Troy; Mishkin, Andrew; Lee, Young

2006-01-01

For most of the history of space exploration, human and robotic programs have been independent, and have responded to distinct requirements. The NASA Vision for Space Exploration calls for the return of humans to the Moon, and the eventual human exploration of Mars; the complexity of this range of missions will require an unprecedented use of automation and robotics in support of human crews. The challenges of human Mars missions, including roundtrip communications time delays of 6 to 40 minutes, interplanetary transit times of many months, and the need to manage lifecycle costs, will require the evolution of a new mission operations paradigm far less dependent on real-time monitoring and response by an Earthbound operations team. Robotic systems and automation will augment human capability, increase human safety by providing means to perform many tasks without requiring immediate human presence, and enable the transfer of traditional mission control tasks from the ground to crews. Developing and validating the new paradigm and its associated infrastructure may place requirements on operations design for nearer-term lunar missions. The authors, representing both the human and robotic mission operations communities, assess human lunar and Mars mission challenges, and consider how human-robot operations may be integrated to enable efficient joint operations, with the eventual emergence of a unified exploration operations culture.

Toward lowering the cost of mission operations

NASA Technical Reports Server (NTRS)

Wall, S. D.; Ledbetter, K. W.

1993-01-01

The mission operations system is one of the more significant drivers of the cost of the mission operations and data analysis segment of missions. In large or long-lived projects, the MOS can also be a driver in total mission cost. Larger numbers of missions, together with an increasingly cost-conscious environment, dictate that future missions must more strictly control costs as they perform to their requirements. It is therefore prudent to examine the conduct of past missions for ways to conserve resources. In this paper we review inputs made to past projects' 'lessons-learned' activities, in which personnel from past projects (among other things) identified major cost drivers of MOS's and considered how economies were or might have been realized in both design and performance of their MOS. Common themes among four such reviews are summarized in an attempt to provide suggestions for cost reduction in future missions.

Mission Control Center (MCC) - Apollo 8

NASA Image and Video Library

1968-12-25

S68-56007 (23 Dec. 1968) --- Overall view of the Mission Operations Control Room in the Mission Control Center, Building 30, on the third day of the Apollo 8 lunar orbit mission. Seen on the television monitor is a picture of Earth which was telecast from the Apollo 8 spacecraft 176,000 miles away.

Systems Engineering Challenges for GSFC Space Science Mission Operations

NASA Technical Reports Server (NTRS)

Thienel, Julie; Harman, Richard R.

2017-01-01

The NASA Goddard Space Flight Center Space Science Mission Operations (SSMO) project currently manages19 missions for the NASA Science Mission Directorate, within the Planetary, Astrophysics, and Heliophysics Divisions. The mission lifespans range from just a few months to more than20 years. The WIND spacecraft, the oldest SSMO mission, was launched in 1994. SSMO spacecraft reside in low earth, geosynchronous,highly elliptical, libration point, lunar, heliocentric,and Martian orbits. SSMO spacecraft range in size from 125kg (Aeronomy of Ice in the Mesosphere (AIM)) to over 4000kg (Fermi Gamma-Ray Space Telescope (Fermi)). The attitude modes include both spin and three-axis stabilized, with varying requirements on pointing accuracy. The spacecraft are operated from control centers at Goddard and off-site control centers;the Lunar Reconnaissance Orbiter (LRO), the Solar Dynamics Observatory (SDO) and Magnetospheric MultiScale (MMS)mission were built at Goddard. The Advanced Composition Explorer (ACE) and Wind are operated out of a multi-mission operations center, which will also host several SSMO-managed cubesats in 2017. This paper focuses on the systems engineeringchallenges for such a large and varied fleet of spacecraft.

Cost Analysis in a Multi-Mission Operations Environment

NASA Technical Reports Server (NTRS)

Felton, Larry; Newhouse, Marilyn; Bornas, Nick; Botts, Dennis; Ijames, Gayleen; Montgomery, Patty; Roth, Karl

2014-01-01

Spacecraft control centers have evolved from dedicated, single-mission or single mission-type support to multi-mission, service-oriented support for operating a variety of mission types. At the same time, available money for projects is shrinking and competition for new missions is increasing. These factors drive the need for an accurate and flexible model to support estimating service costs for new or extended missions; the cost model in turn drives the need for an accurate and efficient approach to service cost analysis. The National Aeronautics and Space Administration (NASA) Huntsville Operations Support Center (HOSC) at Marshall Space Flight Center (MSFC) provides operations services to a variety of customers around the world. HOSC customers range from launch vehicle test flights; to International Space Station (ISS) payloads; to small, short duration missions; and has included long duration flagship missions. The HOSC recently completed a detailed analysis of service costs as part of the development of a complete service cost model. The cost analysis process required the team to address a number of issues. One of the primary issues involves the difficulty of reverse engineering individual mission costs in a highly efficient multi-mission environment, along with a related issue of the value of detailed metrics or data to the cost model versus the cost of obtaining accurate data. Another concern is the difficulty of balancing costs between missions of different types and size and extrapolating costs to different mission types. The cost analysis also had to address issues relating to providing shared, cloud-like services in a government environment, and then assigning an uncertainty or risk factor to cost estimates that are based on current technology, but will be executed using future technology. Finally the cost analysis needed to consider how to validate the resulting cost models taking into account the non-homogeneous nature of the available cost data and

View of Mission Control Center celebrating conclusion of Apollo 11 mission

NASA Technical Reports Server (NTRS)

1969-01-01

Overall view of the Mission Operations Control Room in the Mission Control Center, bldg 30, Manned Spacecraft Center (MSC), at the conclusion of the Apollo 11 lunar landing mission. The television monitor shows President Richard M. Nixon greeting the Apollo 11 astronauts aboard the U.S.S. Hornet in the Pacific recovery area (40301); NASA and MSC Officials join the flight controllers in celebrating the conclusion of the Apollo 11 mission. From left foreground Dr. Maxime A. Faget, MSC Director of Engineering and Development; George S. Trimble, MSC Deputy Director; Dr. Christopher C. Kraft Jr., MSC Director fo Flight Operations; Julian Scheer (in back), Assistant Adminstrator, Offic of Public Affairs, NASA HQ.; George M. Low, Manager, Apollo Spacecraft Program, MSC; Dr. Robert R. Gilruth, MSC Director; and Charles W. Mathews, Deputy Associate Administrator, Office of Manned Space Flight, NASA HQ (40302).

Mission Control Center (MCC) - Celebration - Conclusion - Apollo XI Mission - MSC

NASA Image and Video Library

1969-07-24

S69-40301 (24 July 1969) --- Overall view of the Mission Operations Control Room (MOCR) in the Mission Control Center (MCC), Building 30, Manned Spacecraft Center (MSC), at the conclusion of the Apollo 11 lunar landing mission. The television monitor shows President Richard M. Nixon greeting the Apollo 11 astronauts aboard the USS Hornet in the Pacific recovery area. Astronauts Neil A. Armstrong, Michael Collins, and Edwin E. Aldrin Jr. are inside the Mobile Quarantine Facility (MQF).

Advancing Autonomous Operations Technologies for NASA Missions

NASA Technical Reports Server (NTRS)

Cruzen, Craig; Thompson, Jerry T.

2013-01-01

This paper discusses the importance of implementing advanced autonomous technologies supporting operations of future NASA missions. The ability for crewed, uncrewed and even ground support systems to be capable of mission support without external interaction or control has become essential as space exploration moves further out into the solar system. The push to develop and utilize autonomous technologies for NASA mission operations stems in part from the need to reduce cost while improving and increasing capability and safety. This paper will provide examples of autonomous technologies currently in use at NASA and will identify opportunities to advance existing autonomous technologies that will enhance mission success by reducing cost, ameliorating inefficiencies, and mitigating catastrophic anomalies

Reusablility in ESOC mission control systems developments - the SMART-1 mission case

NASA Astrophysics Data System (ADS)

Pignède, Max; Davies, Kevin

2002-07-01

The European Space Operations Centre (ESOC) have a long experience in spacecraft mission control systems developments and use a large number of existing elements for the build up of control systems for new missions. The integration of such elements in a new system covers not only the direct re-use of infrastructure software but also the re-use of concepts and work methodology. Applying reusability is a major asset in ESOC's strategy, especially for low cost space missions. This paper describes re-use of existing elements in the ESOC production of the SMART-1 mission control system (S1MCS) and explores the following areas: The most significant (and major cost-saving contributors) re-used elements are the Spacecraft Control and Operations System (SCOS-2000) and the Network Control and TM/TC Router System (NCTRS) infrastructure systems. These systems are designed precisely for allowing all general mission parameters to be configured easily without any change in the software (in particular the NCTRS configuration for SMART-1 was time and cost effective). Further, large parts of the ESOC ROSETTA and INTEGRAL software systems (also SCOS-2000 based) were directly re-used, such as the on-board command schedule maintenance and modelling subsystem (OBQ), the time correlator (TCO) and the external file transfer subsystem (FTS). The INTEGRAL spacecraft database maintenance system (both the editors and configuration control mechanism) and its export facilities into the S1MCS runtime system are directly reused. A special kind of re-use concerns the ENVISAT approach to both the telemetry (TM) and telecommanding (TC) context saving in the redundant server system in order to enable smooth support of operations in case of prime server failure. In this case no software or tools can be re-used because the S1MCS is based on a much more modern technology than the ENVISAT mission control system as well as on largely differing workstations architectures but the ENVISAT validated

Lessons Learned from Engineering a Multi-Mission Satellite Operations Center

NASA Technical Reports Server (NTRS)

Madden, Maureen; Cary, Everett, Jr.; Esposito, Timothy; Parker, Jeffrey; Bradley, David

2006-01-01

NASA's Small Explorers (SMEX) satellites have surpassed their designed science-lifetimes and their flight operations teams are now facing the challenge of continuing operations with reduced funding. At present, these missions are being reengineered into a fleet-oriented ground system at Goddard Space Flight Center (GSFC). When completed, this ground system will provide command and control of four SMEX missions and will demonstrate fleet automation and control concepts. As a path-finder for future mission consolidation efforts, this ground system will also demonstrate new ground-based technologies that show promise of supporting longer mission lifecycles and simplifying component integration. One of the core technologies being demonstrated in the SMEiX Mission Operations Center is the GSFC Mission Services Evolution Center (GMSEC) architecture. The GMSEC architecture uses commercial Message Oriented Middleware with a common messaging standard to realize a higher level of component interoperability, allowing for interchangeable components in ground systems. Moreover, automation technologies utilizing the GMSEC architecture are being evaluated and implemented to provide extended lights-out operations. This mode of operation will provide routine monitoring and control of the heterogeneous spacecraft fleet. The operational concepts being developed will reduce the need for staffed contacts and is seen as a necessity for fleet management. This paper will describe the experiences of the integration team throughout the reengineering effort of the SMEX ground system. Additionally, lessons learned will be presented based on the team s experiences with integrating multiple missions into a fleet-based automated ground system.

Lessons Learned from Engineering a Multi-Mission Satellite Operations Center

NASA Technical Reports Server (NTRS)

Madden, Maureen; Cary, Everett, Jr.; Esposito, Timothy; Parker, Jeffrey; Bradley, David

2006-01-01

NASA's Small Explorers (SMEX) satellites have surpassed their designed science-lifetimes and their flight operations teams are now facing the challenge of continuing operations with reduced funding. At present, these missions are being re-engineered into a fleet-oriented ground system at Goddard Space Flight Center (GSFC). When completed, this ground system will provide command and control of four SMEX missions and will demonstrate fleet automation and control concepts. As a path-finder for future mission consolidation efforts, this ground system will also demonstrate new ground-based technologies that show promise of supporting longer mission lifecycles and simplifying component integration. One of the core technologies being demonstrated in the SMEX Mission Operations Center is the GSFC Mission Services Evolution Center (GMSEC) architecture. The GMSEC architecture uses commercial Message Oriented Middleware with a common messaging standard to realize a higher level of component interoperability, allowing for interchangeable components in ground systems. Moreover, automation technologies utilizing the GMSEC architecture are being evaluated and implemented to provide extended lights-out operations. This mode of operation will provide routine monitoring and control of the heterogeneous spacecraft fleet. The operational concepts being developed will reduce the need for staffed contacts and is seen as a necessity for fleet management. This paper will describe the experiences of the integration team throughout the re-enginering effort of the SMEX ground system. Additionally, lessons learned will be presented based on the team's experiences with integrating multiple missions into a fleet-automated ground system.

Cost Analysis In A Multi-Mission Operations Environment

NASA Technical Reports Server (NTRS)

Newhouse, M.; Felton, L.; Bornas, N.; Botts, D.; Roth, K.; Ijames, G.; Montgomery, P.

2014-01-01

Spacecraft control centers have evolved from dedicated, single-mission or single missiontype support to multi-mission, service-oriented support for operating a variety of mission types. At the same time, available money for projects is shrinking and competition for new missions is increasing. These factors drive the need for an accurate and flexible model to support estimating service costs for new or extended missions; the cost model in turn drives the need for an accurate and efficient approach to service cost analysis. The National Aeronautics and Space Administration (NASA) Huntsville Operations Support Center (HOSC) at Marshall Space Flight Center (MSFC) provides operations services to a variety of customers around the world. HOSC customers range from launch vehicle test flights; to International Space Station (ISS) payloads; to small, short duration missions; and has included long duration flagship missions. The HOSC recently completed a detailed analysis of service costs as part of the development of a complete service cost model. The cost analysis process required the team to address a number of issues. One of the primary issues involves the difficulty of reverse engineering individual mission costs in a highly efficient multimission environment, along with a related issue of the value of detailed metrics or data to the cost model versus the cost of obtaining accurate data. Another concern is the difficulty of balancing costs between missions of different types and size and extrapolating costs to different mission types. The cost analysis also had to address issues relating to providing shared, cloud-like services in a government environment, and then assigning an uncertainty or risk factor to cost estimates that are based on current technology, but will be executed using future technology. Finally the cost analysis needed to consider how to validate the resulting cost models taking into account the non-homogeneous nature of the available cost data and the

Artificial intelligence in a mission operations and satellite test environment

NASA Technical Reports Server (NTRS)

Busse, Carl

1988-01-01

A Generic Mission Operations System using Expert System technology to demonstrate the potential of Artificial Intelligence (AI) automated monitor and control functions in a Mission Operations and Satellite Test environment will be developed at the National Aeronautics and Space Administration (NASA) Jet Propulsion Laboratory (JPL). Expert system techniques in a real time operation environment are being studied and applied to science and engineering data processing. Advanced decommutation schemes and intelligent display technology will be examined to develop imaginative improvements in rapid interpretation and distribution of information. The Generic Payload Operations Control Center (GPOCC) will demonstrate improved data handling accuracy, flexibility, and responsiveness in a complex mission environment. The ultimate goal is to automate repetitious mission operations, instrument, and satellite test functions by the applications of expert system technology and artificial intelligence resources and to enhance the level of man-machine sophistication.

The Right Stuff: A Look Back at Three Decades of Flight Controller Training for Space Shuttle Mission Operations

NASA Technical Reports Server (NTRS)

Dittemore, Gary D.

2011-01-01

Operations of human spaceflight systems is extremely complex, therefore the training and certification of operations personnel is a critical piece of ensuring mission success. Mission Control Center (MCC-H), at the Lyndon B. Johnson Space Center, in Houston, Texas manages mission operations for the Space Shuttle Program, including the training and certification of the astronauts and flight control teams. This paper will give an overview of a flight control team s makeup and responsibilities during a flight, and details on how those teams are trained and certified. The training methodology for developing flight controllers has evolved significantly over the last thirty years, while the core goals and competencies have remained the same. In addition, the facilities and tools used in the control center have evolved. These changes have been driven by many factors including lessons learned, technology, shuttle accidents, shifts in risk posture, and generational differences. Flight controllers will share their experiences in training and operating the Space Shuttle throughout the Program s history. A primary method used for training Space Shuttle flight control teams is by running mission simulations of the orbit, ascent, and entry phases, to truly "train like you fly." The reader will learn what it is like to perform a simulation as a shuttle flight controller. Finally, the paper will reflect on the lessons learned in training for the shuttle program, and how those could be applied to future human spaceflight endeavors. These endeavors could range from going to the moon or to Mars. The lessons learned from operating the space shuttle for over thirty years will help the space industry build the next human transport space vehicle and inspire the next generation of space explorers.

New Mission Control Center Briefing

NASA Technical Reports Server (NTRS)

1995-01-01

Live footage shows panelists, Chief Center Systems Division John Muratore, and Acting Chief, Control Center Systems Division, Linda Uljon, giving an overview of the new Mission Control Center. Muratore and Uljon talk about the changes and modernization of the new Center. The panelists mention all the new capabilities of the new Center. They emphasize the Distributed real time command and control environment, the reduction in operation costs, and even the change from coaxial cables to fiber optic cables. Uljon also tells us that the new Control Center will experience its first mission after the launch of STS-70 and its first complete mission (both launching and landing) during STS-71.

Apollo 13 - Mission Control Console

NASA Image and Video Library

1970-04-15

S70-35096 (16 April 1970) --- As the problem-plagued Apollo 13 crewmen entered their final 24 hours in space, several persons important to the mission remained attentive at consoles in the Mission Operations Control Room of the Mission Control Center at Manned Spacecraft Center. Among those monitoring communications and serving in supervisory capacities were these four officials from National Aeronautics and Space Administration Headquarters, Washington, D.C.: (from left) Thomas H. McMullen, Office of Manned Space Flight, who served as Shift 1 mission director; Dale Myers, associate administrator, Manned Space Flight; Chester M. Lee of the Apollo Program Directorate, OMSF, Apollo 13 mission director; and Dr. Rocco A. Petrone, Apollo program director, OMSF.

Operational training for the mission operations at the Brazilian National Institute for Space Research (INPE)

NASA Technical Reports Server (NTRS)

Rozenfeld, Pawel

1993-01-01

This paper describes the selection and training process of satellite controllers and data network operators performed at INPE's Satellite Tracking and Control Center in order to prepare them for the mission operations of the INPE's first (SCD1) satellite. An overview of the ground control system and SCD1 architecture and mission is given. Different training phases are described, taking into account that the applicants had no previous knowledge of space operations requiring, therefore, a training which started from the basics.

Low Cost Missions Operations on NASA Deep Space Missions

NASA Astrophysics Data System (ADS)

Barnes, R. J.; Kusnierkiewicz, D. J.; Bowman, A.; Harvey, R.; Ossing, D.; Eichstedt, J.

2014-12-01

The ability to lower mission operations costs on any long duration mission depends on a number of factors; the opportunities for science, the flight trajectory, and the cruise phase environment, among others. Many deep space missions employ long cruises to their final destination with minimal science activities along the way; others may perform science observations on a near-continuous basis. This paper discusses approaches employed by two NASA missions implemented by the Johns Hopkins University Applied Physics Laboratory (JHU/APL) to minimize mission operations costs without compromising mission success: the New Horizons mission to Pluto, and the Solar Terrestrial Relations Observatories (STEREO). The New Horizons spacecraft launched in January 2006 for an encounter with the Pluto system.The spacecraft trajectory required no deterministic on-board delta-V, and so the mission ops team then settled in for the rest of its 9.5-year cruise. The spacecraft has spent much of its cruise phase in a "hibernation" mode, which has enabled the spacecraft to be maintained with a small operations team, and minimized the contact time required from the NASA Deep Space Network. The STEREO mission is comprised of two three-axis stabilized sun-staring spacecraft in heliocentric orbit at a distance of 1 AU from the sun. The spacecraft were launched in October 2006. The STEREO instruments operate in a "decoupled" mode from the spacecraft, and from each other. Since STEREO operations are largely routine, unattended ground station contact operations were implemented early in the mission. Commands flow from the MOC to be uplinked, and the data recorded on-board is downlinked and relayed back to the MOC. Tools run in the MOC to assess the health and performance of ground system components. Alerts are generated and personnel are notified of any problems. Spacecraft telemetry is similarly monitored and alarmed, thus ensuring safe, reliable, low cost operations.

Designing Mission Operations for the Gravity Recovery and Interior Laboratory Mission

NASA Technical Reports Server (NTRS)

Havens, Glen G.; Beerer, Joseph G.

2012-01-01

NASA's Gravity Recovery and Interior Laboratory (GRAIL) mission, to understand the internal structure and thermal evolution of the Moon, offered unique challenges to mission operations. From launch through end of mission, the twin GRAIL orbiters had to be operated in parallel. The journey to the Moon and into the low science orbit involved numerous maneuvers, planned on tight timelines, to ultimately place the orbiters into the required formation-flying configuration necessary. The baseline GRAIL mission is short, only 9 months in duration, but progressed quickly through seven very unique mission phases. Compressed into this short mission timeline, operations activities and maneuvers for both orbiters had to be planned and coordinated carefully. To prepare for these challenges, development of the GRAIL Mission Operations System began in 2008. Based on high heritage multi-mission operations developed by NASA's Jet Propulsion Laboratory and Lockheed Martin, the GRAIL mission operations system was adapted to meet the unique challenges posed by the GRAIL mission design. This paper describes GRAIL's system engineering development process for defining GRAIL's operations scenarios and generating requirements, tracing the evolution from operations concept through final design, implementation, and validation.

Mission Operations with an Autonomous Agent

NASA Technical Reports Server (NTRS)

Pell, Barney; Sawyer, Scott R.; Muscettola, Nicola; Smith, Benjamin; Bernard, Douglas E.

1998-01-01

The Remote Agent (RA) is an Artificial Intelligence (AI) system which automates some of the tasks normally reserved for human mission operators and performs these tasks autonomously on-board the spacecraft. These tasks include activity generation, sequencing, spacecraft analysis, and failure recovery. The RA will be demonstrated as a flight experiment on Deep Space One (DSI), the first deep space mission of the NASA's New Millennium Program (NMP). As we moved from prototyping into actual flight code development and teamed with ground operators, we made several major extensions to the RA architecture to address the broader operational context in which PA would be used. These extensions support ground operators and the RA sharing a long-range mission profile with facilities for asynchronous ground updates; support ground operators monitoring and commanding the spacecraft at multiple levels of detail simultaneously; and enable ground operators to provide additional knowledge to the RA, such as parameter updates, model updates, and diagnostic information, without interfering with the activities of the RA or leaving the system in an inconsistent state. The resulting architecture supports incremental autonomy, in which a basic agent can be delivered early and then used in an increasingly autonomous manner over the lifetime of the mission. It also supports variable autonomy, as it enables ground operators to benefit from autonomy when L'@ey want it, but does not inhibit them from obtaining a detailed understanding and exercising tighter control when necessary. These issues are critical to the successful development and operation of autonomous spacecraft.

Pointing control for the International Comet Mission

NASA Technical Reports Server (NTRS)

Leblanc, D. R.; Schumacher, L. L.

1980-01-01

The design of the pointing control system for the proposed International Comet Mission, intended to fly by Comet Halley and rendezvous with Comet Tempel-2 is presented. Following a review of mission objectives and the spacecraft configuration, design constraints on the pointing control system controlling the two-axis gimballed scan platform supporting the science instruments are discussed in relation to the scientific requirements of the mission. The primary design options considered for the pointing control system design for the baseline spacecraft are summarized, and the design selected, which employs a target-referenced, inertially stabilized control system, is described in detail. The four basic modes of operation of the pointing control subsystem (target acquisition, inertial hold, target track and slew) are discussed as they relate to operations at Halley and Tempel-2. It is pointed that the pointing control system design represents a significant advance in the state of the art of pointing controls for planetary missions.

Discovery Planetary Mission Operations Concepts

NASA Technical Reports Server (NTRS)

Coffin, R.

1994-01-01

The NASA Discovery Program of small planetary missions will provide opportunities to continue scientific exploration of the solar system in today's cost-constrained environment. Using a multidisciplinary team, JPL has developed plans to provide mission operations within the financial parameters established by the Discovery Program. This paper describes experiences and methods that show promise of allowing the Discovery Missions to operate within the program cost constraints while maintaining low mission risk, high data quality, and reponsive operations.

Leadership Challenges in ISS Operations: Lessons Learned from Junior and Senior Mission Control Personnel

NASA Technical Reports Server (NTRS)

Clement, James L.; Ritsher, Jennifer Boyd; Saylor, Stephanie A.; Kanas, Nick

2006-01-01

The International Space Station (ISS) is operated by a multi-national, multi-organizational team that is dispersed across multiple locations, time zones, and work schedules. At NASA, both junior and senior mission control personnel have had to find ways to address the leadership challenges inherent in such work, but neither have had systematic training in how to do so. The goals of this study were to examine the major leadership challenges faced by ISS mission control personnel and to highlight the approaches that they have found most effective to surmount them. We pay particular attention to the approaches successfully employed by the senior personnel and to the training needs identified by the junior personnel. We also evaluate the extent to which responses are consistent across the junior and senior samples. Further, we compare the issues identified by our interview survey to those identified by a standardized questionnaire survey of mission control personnel and a contrasting group of space station crewmembers. We studied a sample of 14 senior ISS flight controllers and a contrasting sample of 12 more junior ISS controllers. Data were collected using a semi-structured qualitative interview and content analyzed using an iterative process with multiple coders and consensus meetings to resolve discrepancies. To further explore the meaning of the interview findings, we also conducted new analyses of data from a previous questionnaire study of 13 American astronauts, 17 Russian cosmonauts, and 150 U.S. and 36 Russian mission control personnel supporting the ISS or Mir space stations. The interview data showed that the survey respondents had substantial consensus on several leadership challenges and on key strategies for dealing with them, and they offered a wide range of specific tactics for implementing these strategies. Interview data from the junior respondents will be presented for the first time at the meeting. The questionnaire data showed that the US mission

Flight Controllers in Mission Control Center during splashdown of Apollo 14

NASA Image and Video Library

1971-02-09

S71-18400 (9 Feb. 1971) --- Flight controllers in the Mission Operations Control Room (MOCR) of the Mission Control Center (MCC) view a colorful display which signals the successful splashdown and recovery of the crew of the Apollo 14 lunar landing mission. The MOCR's large screen at right shows a television shot aboard the USS New Orleans, Apollo 14 prime recovery ship.

Controlling Infrastructure Costs: Right-Sizing the Mission Control Facility

NASA Technical Reports Server (NTRS)

Martin, Keith; Sen-Roy, Michael; Heiman, Jennifer

2009-01-01

Johnson Space Center's Mission Control Center is a space vehicle, space program agnostic facility. The current operational design is essentially identical to the original facility architecture that was developed and deployed in the mid-90's. In an effort to streamline the support costs of the mission critical facility, the Mission Operations Division (MOD) of Johnson Space Center (JSC) has sponsored an exploratory project to evaluate and inject current state-of-the-practice Information Technology (IT) tools, processes and technology into legacy operations. The general push in the IT industry has been trending towards a data-centric computer infrastructure for the past several years. Organizations facing challenges with facility operations costs are turning to creative solutions combining hardware consolidation, virtualization and remote access to meet and exceed performance, security, and availability requirements. The Operations Technology Facility (OTF) organization at the Johnson Space Center has been chartered to build and evaluate a parallel Mission Control infrastructure, replacing the existing, thick-client distributed computing model and network architecture with a data center model utilizing virtualization to provide the MCC Infrastructure as a Service. The OTF will design a replacement architecture for the Mission Control Facility, leveraging hardware consolidation through the use of blade servers, increasing utilization rates for compute platforms through virtualization while expanding connectivity options through the deployment of secure remote access. The architecture demonstrates the maturity of the technologies generally available in industry today and the ability to successfully abstract the tightly coupled relationship between thick-client software and legacy hardware into a hardware agnostic "Infrastructure as a Service" capability that can scale to meet future requirements of new space programs and spacecraft. This paper discusses the benefits

STS-3 MISSION OPERATIONS CONTROL ROOM (MOCR) - JSC

NASA Image and Video Library

1982-03-26

Mission Control Activities during the STS-3 Mission, Day-4 with: Maj. Gen. James A. Abrahamson, Associate Administrator of the Space Transportation System (STS), NASA Hdqs., conversing with Dr. Kraft; Glynn S. Lunney, Manager, Space Shuttle Program Office, JSC, Aaron Cohen, Manager, Space Shuttle Orbiter Project Office; and, J. E. Conner, Ford Aerospace Engineer at the Instrumentation and Communications Officer (INCO) Console position. 1. Glynn S. Lunney 2. Major General James A. Abrahamson 3. Aaron Cohen 4. J. E. Conner 5. Dr. Christopher Kraft JSC, Houston, TX

Mariner Mars 1971 project. Volume 3: Mission operations system implementation and standard mission flight operations

NASA Technical Reports Server (NTRS)

1973-01-01

The Mariner Mars 1971 mission which was another step in the continuing program of planetary exploration in search of evidence of exobiological activity, information on the origin and evolution of the solar system, and basic science data related to the study of planetary physics, geology, planetology, and cosmology is reported. The mission plan was designed for two spacecraft, each performing a separate but complementary mission. However, a single mission plan was actually used for Mariner 9 because of failure of the launch vehicle for the first spacecraft. The implementation is described, of the Mission Operations System, including organization, training, and data processing development and operations, and Mariner 9 spacecraft cruise and orbital operations through completion of the standard mission from launch to solar occultation in April 1972 are discussed.

Operations Concepts for Deep-Space Missions: Challenges and Opportunities

NASA Technical Reports Server (NTRS)

McCann, Robert S.

2010-01-01

Historically, manned spacecraft missions have relied heavily on real-time communication links between crewmembers and ground control for generating crew activity schedules and working time-critical off-nominal situations. On crewed missions beyond the Earth-Moon system, speed-of-light limitations will render this ground-centered concept of operations obsolete. A new, more distributed concept of operations will have to be developed in which the crew takes on more responsibility for real-time anomaly diagnosis and resolution, activity planning and replanning, and flight operations. I will discuss the innovative information technologies, human-machine interfaces, and simulation capabilities that must be developed in order to develop, test, and validate deep-space mission operations

Lunar Surface Mission Operations Scenario and Considerations

NASA Technical Reports Server (NTRS)

Arnold, Larissa S.; Torney, Susan E.; Rask, John Doug; Bleisath, Scott A.

2006-01-01

Planetary surface operations have been studied since the last visit of humans to the Moon, including conducting analog missions. Mission Operations lessons from these activities are summarized. Characteristics of forecasted surface operations are compared to current human mission operations approaches. Considerations for future designs of mission operations are assessed.

Mission Control Center (MCC) - Apollo 15 Launch - MSC

NASA Image and Video Library

1971-07-26

S71-41357 (26 July 1971) --- An overall, wide-angle lens view of activity in the Mission Operations Control Room in the Mission Control Center minutes after the launch of the Apollo 15 lunar landing mission. Ground elapsed time was 45 minutes and 42 seconds when this photograph was taken.

Mission management aircraft operations manual

NASA Technical Reports Server (NTRS)

1992-01-01

This manual prescribes the NASA mission management aircraft program and provides policies and criteria for the safe and economical operation, maintenance, and inspection of NASA mission management aircraft. The operation of NASA mission management aircraft is based on the concept that safety has the highest priority. Operations involving unwarranted risks will not be tolerated. NASA mission management aircraft will be designated by the Associate Administrator for Management Systems and Facilities. NASA mission management aircraft are public aircraft as defined by the Federal Aviation Act of 1958. Maintenance standards, as a minimum, will meet those required for retention of Federal Aviation Administration (FAA) airworthiness certification. Federal Aviation Regulation Part 91, Subparts A and B, will apply except when requirements of this manual are more restrictive.

MSFC Skylab contamination control systems mission evaluation

NASA Technical Reports Server (NTRS)

1974-01-01

Cluster external contamination control evaluation was made throughout the Skylab Mission. This evaluation indicated that contamination control measures instigated during the design, development, and operational phases of this program were adequate to reduce the general contamination environment external to the Cluster below the threshold senstivity levels for experiments and affected subsystems. Launch and orbit contamination control features included eliminating certain vents, rerouting vents for minimum contamination impact, establishing filters, incorporating materials with minimum outgassing characteristics and developing operational constraints and mission rules to minimize contamination effects. Prior to the launch of Skylab, contamination control math models were developed which were used to predict Cluster surface deposition and background brightness levels throughout the mission. The report summarizes the Skylab system and experiment contamination control evaluation. The Cluster systems and experiments evaluated include Induced Atmosphere, Corollary and ATM Experiments, Thermal Control Surfaces, Solar Array Systems, Windows and Star Tracker.

New Human-Computer Interface Concepts for Mission Operations

NASA Technical Reports Server (NTRS)

Fox, Jeffrey A.; Hoxie, Mary Sue; Gillen, Dave; Parkinson, Christopher; Breed, Julie; Nickens, Stephanie; Baitinger, Mick

2000-01-01

The current climate of budget cuts has forced the space mission operations community to reconsider how it does business. Gone are the days of building one-of-kind control centers with teams of controllers working in shifts 24 hours per day, 7 days per week. Increasingly, automation is used to significantly reduce staffing needs. In some cases, missions are moving towards lights-out operations where the ground system is run semi-autonomously. On-call operators are brought in only to resolve anomalies. Some operations concepts also call for smaller operations teams to manage an entire family of spacecraft. In the not too distant future, a skeleton crew of full-time general knowledge operators will oversee the operations of large constellations of small spacecraft, while geographically distributed specialists will be assigned to emergency response teams based on their expertise. As the operations paradigms change, so too must the tools to support the mission operations team's tasks. Tools need to be built not only to automate routine tasks, but also to communicate varying types of information to the part-time, generalist, or on-call operators and specialists more effectively. Thus, the proper design of a system's user-system interface (USI) becomes even more importance than before. Also, because the users will be accessing these systems from various locations (e.g., control center, home, on the road) via different devices with varying display capabilities (e.g., workstations, home PCs, PDAS, pagers) over connections with various bandwidths (e.g., dial-up 56k, wireless 9.6k), the same software must have different USIs to support the different types of users, their equipment, and their environments. In other words, the software must now adapt to the needs of the users! This paper will focus on the needs and the challenges of designing USIs for mission operations. After providing a general discussion of these challenges, the paper will focus on the current efforts of

Medical System Concept of Operations for Mars Exploration Missions

NASA Technical Reports Server (NTRS)

Urbina, Michelle; Rubin, D.; Hailey, M.; Reyes, D.; Antonsen, Eric

2017-01-01

Future exploration missions will be the first time humanity travels beyond Low Earth Orbit (LEO) since the Apollo program, taking us to cis-lunar space, interplanetary space, and Mars. These long-duration missions will cover vast distances, severely constraining opportunities for emergency evacuation to Earth and cargo resupply opportunities. Communication delays and blackouts between the crew and Mission Control will eliminate reliable, real-time telemedicine consultations. As a result, compared to current LEO operations onboard the International Space Station, exploration mission medical care requires an integrated medical system that provides additional in-situ capabilities and a significant increase in crew autonomy. The Medical System Concept of Operations for Mars Exploration Missions illustrates how a future NASA Mars program could ensure appropriate medical care for the crew of this highly autonomous mission. This Concept of Operations document, when complete, will document all mission phases through a series of mission use case scenarios that illustrate required medical capabilities, enabling the NASA Human Research Program (HRP) Exploration Medical Capability (ExMC) Element to plan, design, and prototype an integrated medical system to support human exploration to Mars.

Lean Mission Operations Systems Design - Using Agile and Lean Development Principles for Mission Operations Design and Development

NASA Technical Reports Server (NTRS)

Trimble, Jay Phillip

2014-01-01

The Resource Prospector Mission seeks to rove the lunar surface with an in-situ resource utilization payload in search of volatiles at a polar region. The mission operations system (MOS) will need to perform the short-duration mission while taking advantage of the near real time control that the short one-way light time to the Moon provides. To maximize our use of limited resources for the design and development of the MOS we are utilizing agile and lean methods derived from our previous experience with applying these methods to software. By using methods such as "say it then sim it" we will spend less time in meetings and more time focused on the one outcome that counts - the effective utilization of our assets on the Moon to meet mission objectives.

Mars Polar Lander Mission Distributed Operations

NASA Technical Reports Server (NTRS)

Norris, J.; Backes, P.; Slostad, J.; Bonitz, R.; Tharp, G.; Tso, K.

2000-01-01

The Mars Polar Lander (MPL) mission is the first planetary mission to use Internet-based distributed ground operations where scientists and engineers collaborate in daily mission operations from multiple geographically distributed locations via the Internet.

Front view of bldg 30 which houses mission control

NASA Image and Video Library

1984-08-30

41D-3072 (30 Aug 1984) --- A 41-D shift change is taking place in the Johnson Space Center's Building 30. In its twenty years of operation, the mission control center has been the scene of many such changes. The windowless wing at left houses three floors, including rooms supporting flight control rooms 1 & 2 (formerly called mission operations control rooms 1 & 2).

Infusion of innovative technologies for mission operations

NASA Astrophysics Data System (ADS)

Donati, Alessandro

2010-11-01

The Advanced Mission Concepts and Technologies Office (Mission Technologies Office, MTO for short) at the European Space Operations Centre (ESOC) of ESA is entrusted with research and development of innovative mission operations concepts systems and provides operations support to special projects. Visions of future missions and requests for improvements from currently flying missions are the two major sources of inspiration to conceptualize innovative or improved mission operations processes. They include monitoring and diagnostics, planning and scheduling, resource management and optimization. The newly identified operations concepts are then proved by means of prototypes, built with embedded, enabling technology and deployed as shadow applications in mission operations for an extended validation phase. The technology so far exploited includes informatics, artificial intelligence and operational research branches. Recent outstanding results include artificial intelligence planning and scheduling applications for Mars Express, advanced integrated space weather monitoring system for the Integral space telescope and a suite of growing client applications for MUST (Mission Utilities Support Tools). The research, development and validation activities at the Mission technologies office are performed together with a network of research institutes across Europe. The objective is narrowing the gap between enabling and innovative technology and space mission operations. The paper first addresses samples of technology infusion cases with their lessons learnt. The second part is focused on the process and the methodology used at the Mission technologies office to fulfill its objectives.

View of Mission Control Center during the Apollo 13 liftoff

NASA Technical Reports Server (NTRS)

1970-01-01

Sigurd A. Sjoberg, Director of Flight Operations at Manned Spacecraft Center (MSC), views the Apollo 13 liftoff from a console in the MSC Mission Control Center, bldg 30. Apollo 13 lifted off at 1:13 p.m., April 11, 1970 (34627); Astronaut Thomas F. Mattingly II, who was scheduled as a prime crewman for the Apollo 13 mission but was replaced in the final hours when it was discovered he had been exposed to measles, watches the liftoff phase of the mission. He is seated at a console in the Mission Control Center's Mission Operations Control Room. Scientist-Astronaut Joseph P. Kerwin, a spacecraft communicator for the mission, looks on at right (34628).

The Final Count Down: A Review of Three Decades of Flight Controller Training Methods for Space Shuttle Mission Operations

NASA Technical Reports Server (NTRS)

Dittemore, Gary D.; Bertels, Christie

2011-01-01

Operations of human spaceflight systems is extremely complex, therefore the training and certification of operations personnel is a critical piece of ensuring mission success. Mission Control Center (MCC-H), at the Lyndon B. Johnson Space Center, in Houston, Texas manages mission operations for the Space Shuttle Program, including the training and certification of the astronauts and flight control teams. As the space shuttle program ends in 2011, a review of how training for STS-1 was conducted compared to STS-134 will show multiple changes in training of shuttle flight controller over a thirty year period. This paper will additionally give an overview of a flight control team s makeup and responsibilities during a flight, and details on how those teams have been trained certified over the life span of the space shuttle. The training methods for developing flight controllers have evolved significantly over the last thirty years, while the core goals and competencies have remained the same. In addition, the facilities and tools used in the control center have evolved. These changes have been driven by many factors including lessons learned, technology, shuttle accidents, shifts in risk posture, and generational differences. A primary method used for training Space Shuttle flight control teams is by running mission simulations of the orbit, ascent, and entry phases, to truly "train like you fly." The reader will learn what it is like to perform a simulation as a shuttle flight controller. Finally, the paper will reflect on the lessons learned in training for the shuttle program, and how those could be applied to future human spaceflight endeavors.

Verification and Implementation of Operations Safety Controls for Flight Missions

NASA Technical Reports Server (NTRS)

Jones, Cheryl L.; Smalls, James R.; Carrier, Alicia S.

2010-01-01

Approximately eleven years ago, the International Space Station launched the first module from Russia, the Functional Cargo Block (FGB). Safety and Mission Assurance (S&MA) Operations (Ops) Engineers played an integral part in that endeavor by executing strict flight product verification as well as continued staffing of S&MA's console in the Mission Evaluation Room (MER) for that flight mission. How were these engineers able to conduct such a complicated task? They conducted it based on product verification that consisted of ensuring that safety requirements were adequately contained in all flight products that affected crew safety. S&MA Ops engineers apply both systems engineering and project management principles in order to gain a appropriate level of technical knowledge necessary to perform thorough reviews which cover the subsystem(s) affected. They also ensured that mission priorities were carried out with a great detail and success.

NASA Extreme Environment Mission Operations: Science Operations Development for Human Exploration

NASA Technical Reports Server (NTRS)

Bell, Mary S.

2014-01-01

The purpose of NASA Extreme Environment Mission Operations (NEEMO) mission 16 in 2012 was to evaluate and compare the performance of a defined series of representative near-Earth asteroid (NEA) extravehicular activity (EVA) tasks under different conditions and combinations of work systems, constraints, and assumptions considered for future human NEA exploration missions. NEEMO 16 followed NASA's 2011 Desert Research and Technology Studies (D-RATS), the primary focus of which was understanding the implications of communication latency, crew size, and work system combinations with respect to scientific data quality, data management, crew workload, and crew/mission control interactions. The 1-g environment precluded meaningful evaluation of NEA EVA translation, worksite stabilization, sampling, or instrument deployment techniques. Thus, NEEMO missions were designed to provide an opportunity to perform a preliminary evaluation of these important factors for each of the conditions being considered. NEEMO 15 also took place in 2011 and provided a first look at many of the factors, but the mission was cut short due to a hurricane threat before all objectives were completed. ARES Directorate (KX) personnel consulted with JSC engineers to ensure that high-fidelity planetary science protocols were incorporated into NEEMO mission architectures. ARES has been collaborating with NEEMO mission planners since NEEMO 9 in 2006, successively building upon previous developments to refine science operations concepts within engineering constraints; it is expected to continue the collaboration as NASA's human exploration mission plans evolve.

Hitchhiker mission operations: Past, present, and future

NASA Technical Reports Server (NTRS)

Anderson, Kathryn

1995-01-01

What is mission operations? Mission operations is an iterative process aimed at achieving the greatest possible mission success with the resources available. The process involves understanding of the science objectives, investigation of which system capabilities can best meet these objectives, integration of the objectives and resources into a cohesive mission operations plan, evaluation of the plan through simulations, and implementation of the plan in real-time. In this paper, the authors present a comprehensive description of what the Hitchhiker mission operations approach is and why it is crucial to mission success. The authors describe the significance of operational considerations from the beginning and throughout the experiment ground and flight systems development. The authors also address the necessity of training and simulations. Finally, the authors cite several examples illustrating the benefits of understanding and utilizing the mission operations process.

Current Level of Mission Control Automation at NASA/Goddard Space Flight Center

NASA Technical Reports Server (NTRS)

Maks, Lori; Breed, Julie; Rackley, Michael; Powers, Edward I. (Technical Monitor)

2001-01-01

NASA is particularly concerned with reducing mission operations costs through increased automation. This paper examines the operations procedures within NASA Mission Control Centers in order to uncover the level of automation that currently exists within them. Based on an assessment of mission operations procedures within three representative control centers, this paper recommends specific areas where there is potential for mission cost reduction through increased automation.

Mission Operations Planning and Scheduling System (MOPSS)

NASA Technical Reports Server (NTRS)

Wood, Terri; Hempel, Paul

2011-01-01

MOPSS is a generic framework that can be configured on the fly to support a wide range of planning and scheduling applications. It is currently used to support seven missions at Goddard Space Flight Center (GSFC) in roles that include science planning, mission planning, and real-time control. Prior to MOPSS, each spacecraft project built its own planning and scheduling capability to plan satellite activities and communications and to create the commands to be uplinked to the spacecraft. This approach required creating a data repository for storing planning and scheduling information, building user interfaces to display data, generating needed scheduling algorithms, and implementing customized external interfaces. Complex scheduling problems that involved reacting to multiple variable situations were analyzed manually. Operators then used the results to add commands to the schedule. Each architecture was unique to specific satellite requirements. MOPSS is an expert system that automates mission operations and frees the flight operations team to concentrate on critical activities. It is easily reconfigured by the flight operations team as the mission evolves. The heart of the system is a custom object-oriented data layer mapped onto an Oracle relational database. The combination of these two technologies allows a user or system engineer to capture any type of scheduling or planning data in the system's generic data storage via a GUI.

An operations concept methodology to achieve low-cost mission operations

NASA Technical Reports Server (NTRS)

Ledbetter, Kenneth W.; Wall, Stephen D.

1993-01-01

Historically, the Mission Operations System (MOS) for a space mission has been designed last because it is needed last. This has usually meant that the ground system must adjust to the flight vehicle design, sometimes at a significant cost. As newer missions have increasingly longer flight operations lifetimes, the MOS becomes proportionally more difficult and more resource-consuming. We can no longer afford to design the MOS last. The MOS concept may well drive the spacecraft, instrument, and mission designs, as well as the ground system. A method to help avoid these difficulties, responding to the changing nature of mission operations is presented. Proper development and use of an Operations Concept document results in a combined flight and ground system design yielding enhanced operability and producing increased flexibility for less cost.

Inflight - Apollo XI (Mission Control Center [MCC]) - MSC

NASA Image and Video Library

1969-07-24

S69-40302 (24 July 1969) --- A group of NASA and Manned Spacecraft Center (MSC) officials join in with the flight controllers in the Mission Operations Control Room (MOCR) in the Mission Control Center (MCC), Building 30, in celebrating the successful conclusion of the Apollo 11 lunar landing mission. From left foreground are Dr. Maxime A. Faget, MSC Director of Engineering and Development; George S. Trimble, MSC Deputy Director; Dr. Christopher C. Kraft Jr., MSC Director of Flight Operations; Julian Scheer (in back), Assistant Administrator, Office of Public Affairs, NASA Headquarters; George M. Low, Manager, Apollo Spacecraft Program, MSC; Dr. Robert R. Gilruth, MSC Director; and Charles W. Mathews, Deputy Associate Administrator, Office of Manned Space Flight, NASA Headquarters.

An Architecture to Promote the Commercialization of Space Mission Command and Control

NASA Technical Reports Server (NTRS)

Jones, Michael K.

1996-01-01

This paper describes a command and control architecture that encompasses space mission operations centers, ground terminals, and spacecraft. This architecture is intended to promote the growth of a lucrative space mission operations command and control market through a set of open standards used by both gevernment and profit-making space mission operators.

Timeline-Based Mission Operations Architecture: An Overview

NASA Technical Reports Server (NTRS)

Chung, Seung H.; Bindschadler, Duane L.

2012-01-01

Some of the challenges in developing a mission operations system and operating a mission can be traced back to the challenge of integrating a mission operations system from its many components and to the challenge of maintaining consistent and accountable information throughout the operations processes. An important contributing factor to both of these challenges is the file-centric nature of today's systems. In this paper, we provide an overview of these challenges and argue the need to move toward an information-centric mission operations system. We propose an information representation called Timeline as an approach to enable such a move, and we provide an overview of a Timeline-based Mission Operations System architecture.

An agent-oriented approach to automated mission operations

NASA Technical Reports Server (NTRS)

Truszkowski, Walt; Odubiyi, Jide

1994-01-01

As we plan for the next generation of Mission Operations Control Center (MOCC) systems, there are many opportunities for the increased utilization of innovative knowledge-based technologies. The innovative technology discussed is an advanced use of agent-oriented approaches to the automation of mission operations. The paper presents an overview of this technology and discusses applied operational scenarios currently being investigated and prototyped. A major focus of the current work is the development of a simple user mechanism that would empower operations staff members to create, in real time, software agents to assist them in common, labor intensive operations tasks. These operational tasks would include: handling routine data and information management functions; amplifying the capabilities of a spacecraft analyst/operator to rapidly identify, analyze, and correct spacecraft anomalies by correlating complex data/information sets and filtering error messages; improving routine monitoring and trend analysis by detecting common failure signatures; and serving as a sentinel for spacecraft changes during critical maneuvers enhancing the system's capabilities to support nonroutine operational conditions with minimum additional staff. An agent-based testbed is under development. This testbed will allow us to: (1) more clearly understand the intricacies of applying agent-based technology in support of the advanced automation of mission operations and (2) access the full set of benefits that can be realized by the proper application of agent-oriented technology in a mission operations environment. The testbed under development addresses some of the data management and report generation functions for the Explorer Platform (EP)/Extreme UltraViolet Explorer (EUVE) Flight Operations Team (FOT). We present an overview of agent-oriented technology and a detailed report on the operation's concept for the testbed.

Mission Control Technologies: A New Way of Designing and Evolving Mission Systems

NASA Technical Reports Server (NTRS)

Trimble, Jay; Walton, Joan; Saddler, Harry

2006-01-01

Current mission operations systems are built as a collection of monolithic software applications. Each application serves the needs of a specific user base associated with a discipline or functional role. Built to accomplish specific tasks, each application embodies specialized functional knowledge and has its own data storage, data models, programmatic interfaces, user interfaces, and customized business logic. In effect, each application creates its own walled-off environment. While individual applications are sometimes reused across multiple missions, it is expensive and time consuming to maintain these systems, and both costly and risky to upgrade them in the light of new requirements or modify them for new purposes. It is even more expensive to achieve new integrated activities across a set of monolithic applications. These problems impact the lifecycle cost (especially design, development, testing, training, maintenance, and integration) of each new mission operations system. They also inhibit system innovation and evolution. This in turn hinders NASA's ability to adopt new operations paradigms, including increasingly automated space systems, such as autonomous rovers, autonomous onboard crew systems, and integrated control of human and robotic missions. Hence, in order to achieve NASA's vision affordably and reliably, we need to consider and mature new ways to build mission control systems that overcome the problems inherent in systems of monolithic applications. The keys to the solution are modularity and interoperability. Modularity will increase extensibility (evolution), reusability, and maintainability. Interoperability will enable composition of larger systems out of smaller parts, and enable the construction of new integrated activities that tie together, at a deep level, the capabilities of many of the components. Modularity and interoperability together contribute to flexibility. The Mission Control Technologies (MCT) Project, a collaboration of

SCOSII OL: A dedicated language for mission operations

NASA Technical Reports Server (NTRS)

Baldi, Andrea; Elgaard, Dennis; Lynenskjold, Steen; Pecchioli, Mauro

1994-01-01

The Spacecraft Control and Operations System 2 (SCOSII) is the new generation of Mission Control Systems (MCS) to be used at ESOC. The system is generic because it offers a collection of standard functions configured through a database upon which a dedicated MCS is established for a given mission. An integral component of SCOSII is the support of a dedicated Operations Language (OL). The spacecraft operation engineers edit, test, validate, and install OL scripts as part of the configuration of the system with, e.g., expressions for computing derived parameters and procedures for performing flight operations, all without involvement of software support engineers. A layered approach has been adopted for the implementation centered around the explicit representation of a data model. The data model is object-oriented defining the structure of the objects in terms of attributes (data) and services (functions) which can be accessed by the OL. SCOSII supports the creation of a mission model. System elements as, e.g., a gyro are explicit, as are the attributes which described them and the services they provide. The data model driven approach makes it possible to take immediate advantage of this higher-level of abstraction, without requiring expansion of the language. This article describes the background and context leading to the OL, concepts, language facilities, implementation, status and conclusions found so far.

Prototype Interoperability Document between NASA-JSC and DLR-GSOC Describing the CCSDS SM and C Mission Operations Prototype

NASA Technical Reports Server (NTRS)

Lucord, Steve A.; Gully, Sylvain

2009-01-01

The purpose of the PROTOTYPE INTEROPERABILITY DOCUMENT is to document the design and interfaces for the service providers and consumers of a Mission Operations prototype between JSC-OTF and DLR-GSOC. The primary goal is to test the interoperability sections of the CCSDS Spacecraft Monitor & Control (SM&C) Mission Operations (MO) specifications between both control centers. An additional goal is to provide feedback to the Spacecraft Monitor and Control (SM&C) working group through the Review Item Disposition (RID) process. This Prototype is considered a proof of concept and should increase the knowledge base of the CCSDS SM&C Mission Operations standards. No operational capabilities will be provided. The CCSDS Mission Operations (MO) initiative was previously called Spacecraft Monitor and Control (SM&C). The specifications have been renamed to better reflect the scope and overall objectives. The working group retains the name Spacecraft Monitor and Control working group and is under the Mission Operations and Information Services Area (MOIMS) of CCSDS. This document will refer to the specifications as SM&C Mission Operations, Mission Operations or just MO.

INFLIGHT (MISSION CONTROL CENTER) - STS-2 - JSC

NASA Image and Video Library

1981-11-13

S81-39494 (12 Nov. 1981) --- An overall view of activity in the mission operations control room (MOCR) in Houston?s Mission Control Center (MCC) as viewed from the second front row of consoles during the STS-2 mission. The remote manipulator system (RMS) console is in the immediate foreground. Note TV transmission on the Eidophor screen at front of MOCR and shuttle orbiter marker on tracking map at left indicating the vehicle?s location over the Hawaiian Islands. The downlink was through the Hawaii tracking station. Photo credit: NASA

Concurrent engineering: Spacecraft and mission operations system design

NASA Technical Reports Server (NTRS)

Landshof, J. A.; Harvey, R. J.; Marshall, M. H.

1994-01-01

Despite our awareness of the mission design process, spacecraft historically have been designed and developed by one team and then turned over as a system to the Mission Operations organization to operate on-orbit. By applying concurrent engineering techniques and envisioning operability as an essential characteristic of spacecraft design, tradeoffs can be made in the overall mission design to minimize mission lifetime cost. Lessons learned from previous spacecraft missions will be described, as well as the implementation of concurrent mission operations and spacecraft engineering for the Near Earth Asteroid Rendezvous (NEAR) program.

Mars mission science operations facilities design

NASA Technical Reports Server (NTRS)

Norris, Jeffrey S.; Wales, Roxana; Powell, Mark W.; Backes, Paul G.; Steinke, Robert C.

2002-01-01

A variety of designs for Mars rover and lander science operations centers are discussed in this paper, beginning with a brief description of the Pathfinder science operations facility and its strengths and limitations. Particular attention is then paid to lessons learned in the design and use of operations facilities for a series of mission-like field tests of the FIDO prototype Mars rover. These lessons are then applied to a proposed science operations facilities design for the 2003 Mars Exploration Rover (MER) mission. Issues discussed include equipment selection, facilities layout, collaborative interfaces, scalability, and dual-purpose environments. The paper concludes with a discussion of advanced concepts for future mission operations centers, including collaborative immersive interfaces and distributed operations. This paper's intended audience includes operations facility and situation room designers and the users of these environments.

Clifford Charlesworth seated at his console in Mission Control Room

NASA Image and Video Library

1968-12-21

S68-55742 (21 Dec. 1968) --- Clifford E. Charlesworth, Apollo 8 "Green Team" flight director, is seated at his console in the Mission Operations Control Room in the Mission Control Center, Building 30, during the launch of the Apollo 8 (Spacecraft 103/Saturn 503) manned lunar orbit space mission.

Ensemble: an Architecture for Mission-Operations Software

NASA Technical Reports Server (NTRS)

Norris, Jeffrey; Powell, Mark; Fox, Jason; Rabe, Kenneth; Shu, IHsiang; McCurdy, Michael; Vera, Alonso

2008-01-01

Ensemble is the name of an open architecture for, and a methodology for the development of, spacecraft mission operations software. Ensemble is also potentially applicable to the development of non-spacecraft mission-operations- type software. Ensemble capitalizes on the strengths of the open-source Eclipse software and its architecture to address several issues that have arisen repeatedly in the development of mission-operations software: Heretofore, mission-operations application programs have been developed in disparate programming environments and integrated during the final stages of development of missions. The programs have been poorly integrated, and it has been costly to develop, test, and deploy them. Users of each program have been forced to interact with several different graphical user interfaces (GUIs). Also, the strategy typically used in integrating the programs has yielded serial chains of operational software tools of such a nature that during use of a given tool, it has not been possible to gain access to the capabilities afforded by other tools. In contrast, the Ensemble approach offers a low-risk path towards tighter integration of mission-operations software tools.

Lessons Learned on Operating and Preparing Operations for a Technology Mission from the Perspective of the Earth Observing-1 Mission

NASA Technical Reports Server (NTRS)

Mandl, Dan; Howard, Joseph

2000-01-01

The New Millennium Program's first Earth-observing mission (EO-1) is a technology validation mission. It is managed by the NASA Goddard Space Flight Center in Greenbelt, Maryland and is scheduled for launch in the summer of 2000. The purpose of this mission is to flight-validate revolutionary technologies that will contribute to the reduction of cost and increase of capabilities for future land imaging missions. In the EO-1 mission, there are five instrument, five spacecraft, and three supporting technologies to flight-validate during a year of operations. EO-1 operations and the accompanying ground system were intended to be simple in order to maintain low operational costs. For purposes of formulating operations, it was initially modeled as a small science mission. However, it quickly evolved into a more complex mission due to the difficulties in effectively integrating all of the validation plans of the individual technologies. As a consequence, more operational support was required to confidently complete the on-orbit validation of the new technologies. This paper will outline the issues and lessons learned applicable to future technology validation missions. Examples of some of these include the following: (1) operational complexity encountered in integrating all of the validation plans into a coherent operational plan, (2) initial desire to run single shift operations subsequently growing to 6 "around-the-clock" operations, (3) managing changes in the technologies that ultimately affected operations, (4) necessity for better team communications within the project to offset the effects of change on the Ground System Developers, Operations Engineers, Integration and Test Engineers, S/C Subsystem Engineers, and Scientists, and (5) the need for a more experienced Flight Operations Team to achieve the necessary operational flexibility. The discussion will conclude by providing several cost comparisons for developing operations from previous missions to EO-1 and

Cost efficient operations for Discovery class missions

NASA Technical Reports Server (NTRS)

Cameron, G. E.; Landshof, J. A.; Whitworth, G. W.

1994-01-01

The Near Earth Asteroid Rendezvous (NEAR) program at The Johns Hopkins University Applied Physics Laboratory is scheduled to launch the first spacecraft in NASA's Discovery program. The Discovery program is to promote low cost spacecraft design, development, and mission operations for planetary space missions. The authors describe the NEAR mission and discuss the design and development of the NEAR Mission Operations System and the NEAR Ground System with an emphasis on those aspects of the design that are conducive to low-cost operations.

View of Mission Control during lunar surface Apollo 11 EVA

NASA Image and Video Library

1969-07-20

Overall view of the Mission Operations Control Room in the Mission Control Center, bldg 30, during the lunar surface extravehicular activity (EVA) of Apollo 11 Astronauts Neil A. Armstrong and Edwin E. Aldrin Jr.

MISSION CONTROL CENTER (MCC) - APOLLO-SOYUZ TEST PROJECT (ASTP) - JSC

NASA Image and Video Library

1975-07-17

S75-28682 (17 July 1975) --- An overall view of the Mission Operations Control Room in the Mission Control Center during the joint U.S.-USSR Apollo-Soyuz Test Project docking mission in Earth orbit. The large television monitor shows a view of the Soyuz spacecraft as seen from the Apollo spacecraft during rendezvous and docking maneuvers. Eugene F. Kranz, JSC Deputy Director of Flight Operations, is standing in the foreground. M.P. Frank, the American senior ASTP flight director, is partially obscured on the right.

Re-Engineering the Mission Operations System (MOS) for the Prime and Extended Mission

NASA Technical Reports Server (NTRS)

Hunt, Joseph C., Jr.; Cheng, Leo Y.

2012-01-01

One of the most challenging tasks in a space science mission is designing the Mission Operations System (MOS). Whereas the focus of the project is getting the spacecraft built and tested for launch, the mission operations engineers must build a system to carry out the science objectives. The completed MOS design is then formally assessed in the many reviews. Once a mission has completed the reviews, the Mission Operation System (MOS) design has been validated to the Functional Requirements and is ready for operations. The design was built based on heritage processes, new technology, and lessons learned from past experience. Furthermore, our operational concepts must be properly mapped to the mission design and science objectives. However, during the course of implementing the science objective in the operations phase after launch, the MOS experiences an evolutional change to adapt for actual performance characteristics. This drives the re-engineering of the MOS, because the MOS includes the flight and ground segments. Using the Spitzer mission as an example we demonstrate how the MOS design evolved for both the prime and extended mission to enhance the overall efficiency for science return. In our re-engineering process, we ensured that no requirements were violated or mission objectives compromised. In most cases, optimized performance across the MOS, including gains in science return as well as savings in the budget profile was achieved. Finally, we suggest a need to better categorize the Operations Phase (Phase E) in the NASA Life-Cycle Phases of Formulation and Implementation

Navigation Operations for the Magnetospheric Multiscale Mission

NASA Technical Reports Server (NTRS)

Long, Anne; Farahmand, Mitra; Carpenter, Russell

2015-01-01

The Magnetospheric Multiscale (MMS) mission employs four identical spinning spacecraft flying in highly elliptical Earth orbits. These spacecraft will fly in a series of tetrahedral formations with separations of less than 10 km. MMS navigation operations use onboard navigation to satisfy the mission definitive orbit and time determination requirements and in addition to minimize operations cost and complexity. The onboard navigation subsystem consists of the Navigator GPS receiver with Goddard Enhanced Onboard Navigation System (GEONS) software, and an Ultra-Stable Oscillator. The four MMS spacecraft are operated from a single Mission Operations Center, which includes a Flight Dynamics Operations Area (FDOA) that supports MMS navigation operations, as well as maneuver planning, conjunction assessment and attitude ground operations. The System Manager component of the FDOA automates routine operations processes. The GEONS Ground Support System component of the FDOA provides the tools needed to support MMS navigation operations. This paper provides an overview of the MMS mission and associated navigation requirements and constraints and discusses MMS navigation operations and the associated MMS ground system components built to support navigation-related operations.

Calculation of Operations Efficiency Factors for Mars Surface Missions

NASA Technical Reports Server (NTRS)

Layback, Sharon L.

2014-01-01

For planning of Mars surface missions, to be operated on a sol-by-sol basis by a team on Earth (where a "sol" is a Martian day), activities are described in terms of "sol types" that are strung together to build a surface mission scenario. Some sol types require ground decisions based on a previous sol's results to feed into the activity planning ("ground in the loop"), while others do not. Due to the differences in duration between Earth days and Mars sols, for a given Mars local solar time, the corresponding Earth time "walks" relative to the corresponding times on the prior sol/day. In particular, even if a communication window has a fixed Mars local solar time, the Earth time for that window will be approximately 40 minutes later each succeeding day. Further complexity is added for non-Mars synchronous communication relay assets, and when there are multiple control centers in different Earth time zones. The solution is the development of "ops efficiency factors" that reflect the efficiency of a given operations configuration (how many and location of control centers, types of communication windows, synchronous or non-synchronous nature of relay assets, sol types, more-or-less sustainable operations schedule choices) against a theoretical "optimal" operations configuration for the mission being studied. These factors are then incorporated into scenario models in order to determine the surface duration (and therefore minimum spacecraft surface lifetime) required to fulfill scenario objectives. The resulting model is used to perform "what-if" analyses for variations in scenario objectives. The ops efficiency factor is the ratio of the figure of merit for a given operations factor to the figure of merit for the theoretical optimal configuration. The current implementation is a pair of models in Excel. The first represents a ground operations schedule for 500 sols in each operations configuration for the mission being studied (500 sols was chosen as being a long

MISSION CONTROL CENTER (MCC) - APOLLO 16 - MSC

NASA Image and Video Library

1972-05-08

S72-37010 (20 April 1972) --- NASA officials gather around a console in the Mission Operations Control Room (MOCR) in the Mission Control Center (MCC) prior to the making of a decision whether to land Apollo 16 on the moon or to abort the landing. Seated, left to right, are Dr. Christopher C. Kraft Jr., Director of the Manned Spacecraft Center (MSC), and Brig. Gen. James A. McDivitt (USAF), Manager, Apollo Spacecraft Program Office, MSC; and standing, left to right, are Dr. Rocco A. Petrone, Apollo Program Director, Office Manned Space Flight (OMSF), NASA HQ.; Capt. John K. Holcomb (U.S. Navy, Ret.), Director of Apollo Operations, OMSF; Sigurd A. Sjoberg, Deputy Director, MSC; Capt. Chester M. Lee (U.S. Navy, Ret.), Apollo Mission Director, OMSF; Dale D. Myers, NASA Associate Administrator for Manned Space Flight; and Dr. George M. Low, NASA Deputy Administrator. Photo credit: NASA

Views of the mission control center during STS-9

NASA Technical Reports Server (NTRS)

1983-01-01

The two backup payload specialists for Drs. Byron K. Lichtenberg and Ulf Merbold huddle in the mission control center during day three activity aboard Spacelab. Seated at the Console is Dr. Michael Lampton. Leaning over Lampton's shoulder is Dutch scientist Wubbo Ockels. The two are surrounded by a few of the flight controllers in the payload operations control center (POCC) portion of JSC's mission control center.

Mission Performance of the GLAS Thermal Control System - 7 Years In Orbit

NASA Technical Reports Server (NTRS)

Grob, Eric W.

2010-01-01

ICESat (Ice, Cloud and land Elevation Satellite) was launched in 2003 carrying a single science instrument - the Geoscience Laser Altimeter System (GLAS). Its primary mission was to measure polar ice thickness. The GLAS thermal control architecture utilized propylene Loop Heat Pipe (LHP) technology to provide selectable and stable temperature control for the lasers and other electronics over a widely varying mission thermal environment. To minimize expected degradation of the radiators, Optical Solar Reflectors (OSRs) were used for both LHP radiators to minimize degradation caused by UV exposure in the various spacecraft attitudes necessary throughout the mission. Developed as a Class C mission, with selective redundancy, the thermal architecture was single st ring, except for temperature sensors used for heater control during normal operations. Although originally planned for continuous laser operations over the nominal three year science mission, laser anomalies limited operations to discrete measurement campaigns repeated throughout the year. For trending of the science data, these periods were selected to occur at approximately the same time each year, which resulted in operations during similar attitudes and beta angles. Despite the laser life issues, the LHPs have operated nearly continuously over this time, being non-operational for only brief periods. Using mission telemetry, this paper looks at the performance of the thermal subsystem during these periods and provides an assessment of radiator degradation over the mission lifetime.

Mission Operations of EO-1 with Onboard Autonomy

NASA Technical Reports Server (NTRS)

Tran, Daniel Q.

2006-01-01

Space mission operations are extremely labor and knowledge-intensive and are driven by the ground and flight systems. Inclusion of an autonomy capability can have dramatic effects on mission operations. We describe the prior, labor and knowledge intensive mission operations flow for the Earth Observing-1 (EO-1) spacecraft as well as the new autonomous operations as part of the Autonomous Sciencecraft Experiment.

View of Mission Control Center during the Apollo 13 liftoff

NASA Image and Video Library

1970-04-11

S70-34628 (11 April 1970) --- Astronaut Thomas K. (Ken) Mattingly II, who was scheduled as a prime crew member for the Apollo 13 lunar landing mission but was replaced in the final hours when it was discovered he had been exposed to measles, watches the liftoff phase of the mission. He is seated at a console in the Mission Control Center’s (MCC) Mission Operations Control Room (MOCR). Scientist-astronaut Joseph P. Kerwin, a spacecraft communicator for the mission, looks on at right.

NASDA's view of ground control in mission operations

NASA Technical Reports Server (NTRS)

Tateno, Satoshi

1993-01-01

This paper presents an overview of the present status and future plans of the National Space Development Agency of Japan 's (NASDA's) ground segment and related space missions. The described ground segment consists of the tracking and data acquisition (T&DA) system and the Earth Observation Center (EOC) system. In addition to these systems, the current plan of the Engineering Support Center (ESC) for the Japanese Experiment Module (JEM) attached to Space Station Freedom is introduced. Then, NASDA's fundamental point of view on the future trend of operations and technologies in the coming new space era is discussed. Within the discussion, the increasing importance of international cooperation is also mentioned.

View of Mission Control Center during Apollo 13 splashdown

NASA Image and Video Library

1970-04-17

S70-35471 (17 April 1970) --- Two flight controllers man consoles in the Missions Operations Control Room (MOCR) of the Mission Control Center (MCC) at the Manned Spacecraft Center (MSC), Houston, Texas, just before splashdown occurred in the south Pacific Ocean. Though the MOCR does not appear to be crowded in this photo, there was a very large crowd of persons on hand for the splashdown and recovery operations coverage. Most of the group crowded around in the rear of the room. Apollo 13 splashdown occurred at 12:07:44 p.m. (CST), April 17, 1970.

Achieving Operability via the Mission System Paradigm

NASA Technical Reports Server (NTRS)

Hammer, Fred J.; Kahr, Joseph R.

2006-01-01

In the past, flight and ground systems have been developed largely-independently, with the flight system taking the lead, and dominating the development process. Operability issues have been addressed poorly in planning, requirements, design, I&T, and system-contracting activities. In many cases, as documented in lessons-learned, this has resulted in significant avoidable increases in cost and risk. With complex missions and systems, operability is being recognized as an important end-to-end design issue. Never-the-less, lessons-learned and operability concepts remain, in many cases, poorly understood and sporadically applied. A key to effective application of operability concepts is adopting a 'mission system' paradigm. In this paradigm, flight and ground systems are treated, from an engineering and management perspective, as inter-related elements of a larger mission system. The mission system consists of flight hardware, flight software, telecom services, ground data system, testbeds, flight teams, science teams, flight operations processes, procedures, and facilities. The system is designed in functional layers, which span flight and ground. It is designed in response to project-level requirements, mission design and an operations concept, and is developed incrementally, with early and frequent integration of flight and ground components.

Activities in the Mission Control Center during STS 41-C

NASA Image and Video Library

1984-04-13

41C-03229 (13 April 1984) --- An overall view of activity in the Mission Operations Control Room (MOCR) of the Johnson Space Center (JSC) Mission Control Center (MCC) during post-landing activity at the Challenger's landing site at Edwards Air Force Base in California.

Enabling Autonomous Space Mission Operations with Artificial Intelligence

NASA Technical Reports Server (NTRS)

Frank, Jeremy

2017-01-01

For over 50 years, NASA's crewed missions have been confined to the Earth-Moon system, where speed-of-light communications delays between crew and ground are practically nonexistent. This ground-centered mode of operations, with a large, ground-based support team, is not sustainable for NASAs future human exploration missions to Mars. Future astronauts will need smarter tools employing Artificial Intelligence (AI) techniques make decisions without inefficient communication back and forth with ground-based mission control. In this talk we will describe several demonstrations of astronaut decision support tools using AI techniques as a foundation. These demonstrations show that astronauts tasks ranging from living and working to piloting can benefit from AI technology development.

Constellation Program Mission Operations Project Office Status and Support Philosophy

NASA Technical Reports Server (NTRS)

Smith, Ernest; Webb, Dennis

2007-01-01

The Constellation Program Mission Operations Project Office (CxP MOP) at Johnson Space Center in Houston Texas is preparing to support the CxP mission operations objectives for the CEV/Orion flights, the Lunar Lander, and and Lunar surface operations. Initially the CEV will provide access to the International Space Station, then progress to the Lunar missions. Initial CEV mission operations support will be conceptually similar to the Apollo missions, and we have set a challenge to support the CEV mission with 50% of the mission operations support currently required for Shuttle missions. Therefore, we are assessing more efficient way to organize the support and new technologies which will enhance our operations support. This paper will address the status of our preparation for these CxP missions, our philosophical approach to CxP operations support, and some of the technologies we are assessing to streamline our mission operations infrastructure.

Mission operations and command assurance: Flight operations quality improvements

NASA Technical Reports Server (NTRS)

Welz, Linda L.; Bruno, Kristin J.; Kazz, Sheri L.; Potts, Sherrill S.; Witkowski, Mona M.

1994-01-01

Mission Operations and Command Assurance (MO&CA) is a Total Quality Management (TQM) task on JPL projects to instill quality in flight mission operations. From a system engineering view, MO&CA facilitates communication and problem-solving among flight teams and provides continuous solving among flight teams and provides continuous process improvement to reduce risk in mission operations by addressing human factors. The MO&CA task has evolved from participating as a member of the spacecraft team, to an independent team reporting directly to flight project management and providing system level assurance. JPL flight projects have benefited significantly from MO&CA's effort to contain risk and prevent rather than rework errors. MO&CA's ability to provide direct transfer of knowledge allows new projects to benefit from previous and ongoing flight experience.

Advanced automation in space shuttle mission control

NASA Technical Reports Server (NTRS)

Heindel, Troy A.; Rasmussen, Arthur N.; Mcfarland, Robert Z.

1991-01-01

The Real Time Data System (RTDS) Project was undertaken in 1987 to introduce new concepts and technologies for advanced automation into the Mission Control Center environment at NASA's Johnson Space Center. The project's emphasis is on producing advanced near-operational prototype systems that are developed using a rapid, interactive method and are used by flight controllers during actual Shuttle missions. In most cases the prototype applications have been of such quality and utility that they have been converted to production status. A key ingredient has been an integrated team of software engineers and flight controllers working together to quickly evolve the demonstration systems.

Mission Control Center (MCC): Apollo XV - MSC

NASA Image and Video Library

1971-08-02

S71-41759 (2 Aug. 1971) --- A partial view of activity in the Mission Operations Control Room in the Mission Control Center during the liftoff of the Apollo 15 Lunar Module "Falcon" ascent stage from the lunar surface. An RCA color television camera mounted on the Lunar Roving Vehicle made it possible for people on Earth to watch the LM's spectacular launch from the moon. The LM liftoff was at 171:37 ground elapsed time. The LRV was parked about 300 feet east of the LM. The TV camera was remotely controlled from a console in the MOCR. Seated in the right foreground is astronaut Edgar D. Mitchell, a spacecraft communicator. Mitchell was lunar module pilot of the Apollo 14 lunar landing mission. Note liftoff on the television monitor in the center background.

XMM-Newton mission operations - ready for its third decade

NASA Astrophysics Data System (ADS)

Kirsch, M.; Finn, T.; Godard, T.; v. Krusenstiern, N.; Pfeil, N.; Salt, D.; Toma, L.; Webert, D.; Weissmann, U.

2017-10-01

The XMM-Newton X-ray space observatory is approaching its third decade of operations. The spacecraft and payload are operating without major degradation and scientific demand is continuously very high. With the change to a new way of using the Attitude and Orbit control System in 2013 the fuel consumption was reduced by a factor of two, additionally this has reduced stress on the reaction wheels. The challenge for the next decade is now to ensure that the saved fuel is available for continuous usage. We will describe the process of the so called 'fuel migration and replenishment' activities needed to keep the spacecraft operational potentially up to 2029+. We provide as well an overall health status of the mission, the evolution of the ground segment and concepts on streamlining mission operations with continued high safety requirements using automation tools.

Earth orbital operations supporting manned interplanetary missions

NASA Astrophysics Data System (ADS)

Sherwood, Brent; Buddington, Patricia A.; Whittaker, William L.

The orbital operations required to accumulate, assemble, test, verify, maintain, and launch complex manned space systems on interplanetary missions from earth orbit are as vital as the flight hardware itself. Vast numbers of orbital crew are neither necessary nor desirable for accomplishing the required tasks. A suite of robotic techniques under human supervisory control, relying on sensors, software and manipulators either currently emergent or already applied in terrestrial settings, can make the job tractable. The mission vehicle becomes largely self-assembling, using its own rigid aerobrake as a work platform. The Space Station, having been used as a laboratory testbed and to house an assembly crew of four, is not dominated by the process. A feasible development schedule, if begun soon, could emplace orbital support technologies for exploration missions in time for a 2004 first interplanetary launch.

Earth orbital operations supporting manned interplanetary missions

NASA Technical Reports Server (NTRS)

Sherwood, Brent; Buddington, Patricia A.; Whittaker, William L.

1989-01-01

The orbital operations required to accumulate, assemble, test, verify, maintain, and launch complex manned space systems on interplanetary missions from earth orbit are as vital as the flight hardware itself. Vast numbers of orbital crew are neither necessary nor desirable for accomplishing the required tasks. A suite of robotic techniques under human supervisory control, relying on sensors, software and manipulators either currently emergent or already applied in terrestrial settings, can make the job tractable. The mission vehicle becomes largely self-assembling, using its own rigid aerobrake as a work platform. The Space Station, having been used as a laboratory testbed and to house an assembly crew of four, is not dominated by the process. A feasible development schedule, if begun soon, could emplace orbital support technologies for exploration missions in time for a 2004 first interplanetary launch.

Improving the Operations of the Earth Observing One Mission via Automated Mission Planning

NASA Technical Reports Server (NTRS)

Chien, Steve A.; Tran, Daniel; Rabideau, Gregg; Schaffer, Steve; Mandl, Daniel; Frye, Stuart

2010-01-01

We describe the modeling and reasoning about operations constraints in an automated mission planning system for an earth observing satellite - EO-1. We first discuss the large number of elements that can be naturally represented in an expressive planning and scheduling framework. We then describe a number of constraints that challenge the current state of the art in automated planning systems and discuss how we modeled these constraints as well as discuss tradeoffs in representation versus efficiency. Finally we describe the challenges in efficiently generating operations plans for this mission. These discussions involve lessons learned from an operations model that has been in use since Fall 2004 (called R4) as well as a newer more accurate operations model operational since June 2009 (called R5). We present analysis of the R5 software documenting a significant (greater than 50%) increase in the number of weekly observations scheduled by the EO-1 mission. We also show that the R5 mission planning system produces schedules within 15% of an upper bound on optimal schedules. This operational enhancement has created value of millions of dollars US over the projected remaining lifetime of the EO-1 mission.

SpaceOps 1992: Proceedings of the Second International Symposium on Ground Data Systems for Space Mission Operations

NASA Technical Reports Server (NTRS)

1993-01-01

The Second International Symposium featured 135 oral presentations in these 12 categories: Future Missions and Operations; System-Level Architectures; Mission-Specific Systems; Mission and Science Planning and Sequencing; Mission Control; Operations Automation and Emerging Technologies; Data Acquisition; Navigation; Operations Support Services; Engineering Data Analysis of Space Vehicle and Ground Systems; Telemetry Processing, Mission Data Management, and Data Archiving; and Operations Management. Topics focused on improvements in the productivity, effectiveness, efficiency, and quality of mission operations, ground systems, and data acquisition. Also emphasized were accomplishments in management of human factors; use of information systems to improve data retrieval, reporting, and archiving; design and implementation of logistics support for mission operations; and the use of telescience and teleoperations.

STS-3 FLIGHT DAY 1 ACTIVITIES - MISSION OPERATIONS CONTROL ROOM (MOCR) - JSC

NASA Image and Video Library

1982-03-22

MOCR during Flight Day 1 of the STS-3 Mission. View: Thomas L. Moser, of the Structures and Mechanics Division, briefing Flight Director Eugene Kranz, Flight Operations, and Dr. Kraft, JSC Director. JSC, HOUSTON, TX

IUS/TUG orbital operations and mission support study. Volume 3: Space tug operations

NASA Technical Reports Server (NTRS)

1975-01-01

A study was conducted to develop space tug operational concepts and baseline operations plan, and to provide cost estimates for space tug operations. Background data and study results are presented along with a transition phase analysis (the transition from interim upper state to tug operations). A summary is given of the tug operational and interface requirements with emphasis on the on-orbit checkout requirements, external interface operational requirements, safety requirements, and system operational interface requirements. Other topics discussed include reference missions baselined for the tug and details for the mission functional flows and timelines derived for the tug mission, tug subsystems, tug on-orbit operations prior to the tug first burn, spacecraft deployment and retrieval by the tug, operations centers, mission planning, potential problem areas, and cost data.

INFLIGHT (MISSION CONTROL CENTER [MCC]) - STS-1 - ELLINGTON AFB (EAFB), TX

NASA Image and Video Library

1981-04-13

S81-32876 (13 April 1981) --- Brig. Gen. William T. Twinting studies the monitor at the Department of Defense (DOD) console in the mission operations control room (MOCR) at the Johnson Space Center?s Mission Control Center (MCC). He is deputy DOD manager for Space Shuttle Support Operations. Gen. Twinting and the other flight controllers seen in the background listen as astronaut John W. Young, STS-1 commander, describes the scenery of a downlink TV transmission. Photo credit: NASA

Hypermedia and intelligent tutoring applications in a mission operations environment

NASA Technical Reports Server (NTRS)

Ames, Troy; Baker, Clifford

1990-01-01

Hypermedia, hypertext and Intelligent Tutoring System (ITS) applications to support all phases of mission operations are investigated. The application of hypermedia and ITS technology to improve system performance and safety in supervisory control is described - with an emphasis on modeling operator's intentions in the form of goals, plans, tasks, and actions. Review of hypermedia and ITS technology is presented as may be applied to the tutoring of command and control languages. Hypertext based ITS is developed to train flight operation teams and System Test and Operation Language (STOL). Specific hypermedia and ITS application areas are highlighted, including: computer aided instruction of flight operation teams (STOL ITS) and control center software development tools (CHIMES and STOL Certification Tool).

MISSION CONTROL CENTER (MCC) - MSC - during Apollo 16

NASA Image and Video Library

1972-05-08

S72-37009 (20 April 1972) --- NASA officials gather around a console in the Mission Operations Control Room (MOCR) in the Mission Control Center (MCC) prior to the making of a decision whether to land Apollo 16 on the moon or to abort the landing. Seated, left to right, are Dr. Christopher C. Kraft Jr., Director of the Manned Spacecraft Center (MSC), and Brig. Gen. James A. McDivitt (USAF), Manager, Apollo Spacecraft Program Office, MSC; and standing, left to right, are Dr. Rocco A. Petrone, Apollo Program Director, Office Manned Space Flight (OMSF), NASA HQ.; Capt. John K. Holcomb (U.S. Navy, Ret.), Director of Apollo Operations, OMSF; Sigurd A. Sjoberg, Deputy Director, MSC; Capt. Chester M. Lee (U.S. Navy, Ret.), Apollo Mission Director, OMSF; Dale D. Myers, NASA Associate Administrator for Manned Space Flight; and Dr. George M. Low, NASA Deputy Administrator. Photo credit: NASA

Autonomous Mission Operations for Sensor Webs

NASA Astrophysics Data System (ADS)

Underbrink, A.; Witt, K.; Stanley, J.; Mandl, D.

2008-12-01

We present interim results of a 2005 ROSES AIST project entitled, "Using Intelligent Agents to Form a Sensor Web for Autonomous Mission Operations", or SWAMO. The goal of the SWAMO project is to shift the control of spacecraft missions from a ground-based, centrally controlled architecture to a collaborative, distributed set of intelligent agents. The network of intelligent agents intends to reduce management requirements by utilizing model-based system prediction and autonomic model/agent collaboration. SWAMO agents are distributed throughout the Sensor Web environment, which may include multiple spacecraft, aircraft, ground systems, and ocean systems, as well as manned operations centers. The agents monitor and manage sensor platforms, Earth sensing systems, and Earth sensing models and processes. The SWAMO agents form a Sensor Web of agents via peer-to-peer coordination. Some of the intelligent agents are mobile and able to traverse between on-orbit and ground-based systems. Other agents in the network are responsible for encapsulating system models to perform prediction of future behavior of the modeled subsystems and components to which they are assigned. The software agents use semantic web technologies to enable improved information sharing among the operational entities of the Sensor Web. The semantics include ontological conceptualizations of the Sensor Web environment, plus conceptualizations of the SWAMO agents themselves. By conceptualizations of the agents, we mean knowledge of their state, operational capabilities, current operational capacities, Web Service search and discovery results, agent collaboration rules, etc. The need for ontological conceptualizations over the agents is to enable autonomous and autonomic operations of the Sensor Web. The SWAMO ontology enables automated decision making and responses to the dynamic Sensor Web environment and to end user science requests. The current ontology is compatible with Open Geospatial Consortium (OGC

STS-35 Mission Manager Actions Room at the Marshall Space Flight Center Spacelab Payload Operations

NASA Technical Reports Server (NTRS)

1990-01-01

The primary objective of the STS-35 mission was round the clock observation of the celestial sphere in ultraviolet and X-Ray astronomy with the Astro-1 observatory which consisted of four telescopes: the Hopkins Ultraviolet Telescope (HUT); the Wisconsin Ultraviolet Photo-Polarimeter Experiment (WUPPE); the Ultraviolet Imaging Telescope (UIT); and the Broad Band X-Ray Telescope (BBXRT). The Huntsville Operations Support Center (HOSC) Spacelab Payload Operations Control Center (SL POCC) at the Marshall Space Flight Center (MSFC) was the air/ground communication channel used between the astronauts and ground control teams during the Spacelab missions. Teams of controllers and researchers directed on-orbit science operations, sent commands to the spacecraft, received data from experiments aboard the Space Shuttle, adjusted mission schedules to take advantage of unexpected science opportunities or unexpected results, and worked with crew members to resolve problems with their experiments. Due to loss of data used for pointing and operating the ultraviolet telescopes, MSFC ground teams were forced to aim the telescopes with fine tuning by the flight crew. This photo captures the activities at the Mission Manager Actions Room during the mission.

Designing an Alternate Mission Operations Control Room

NASA Technical Reports Server (NTRS)

Montgomery, Patty; Reeves, A. Scott

2014-01-01

The Huntsville Operations Support Center (HOSC) is a multi-project facility that is responsible for 24x7 real-time International Space Station (ISS) payload operations management, integration, and control and has the capability to support small satellite projects and will provide real-time support for SLS launches. The HOSC is a service-oriented/ highly available operations center for ISS payloads-directly supporting science teams across the world responsible for the payloads. The HOSC is required to endure an annual 2-day power outage event for facility preventive maintenance and safety inspection of the core electro-mechanical systems. While complete system shut-downs are against the grain of a highly available sub-system, the entire facility must be powered down for a weekend for environmental and safety purposes. The consequence of this ground system outage is far reaching: any science performed on ISS during this outage weekend is lost. Engineering efforts were focused to maximize the ISS investment by engineering a suitable solution capable of continuing HOSC services while supporting safety requirements. The HOSC Power Outage Contingency (HPOC) System is a physically diversified compliment of systems capable of providing identified real-time services for the duration of a planned power outage condition from an alternate control room. HPOC was designed to maintain ISS payload operations for approximately three continuous days during planned HOSC power outages and support a local Payload Operations Team, International Partners, as well as remote users from the alternate control room located in another building.

View of Mission Control Center during Apollo 13 splashdown

NASA Technical Reports Server (NTRS)

1970-01-01

Dr. Thomas O. Paine (center), NASA Administrator, and other NASA Officials joined others in applauding the successful splashdown of the Apollo 13 crewmen. Others among the large crowd in the Mission Operations Control Room of the Mission Control Center, Manned Spacecraft Center (MSC) at the time of recovery were U.S. Air Force Lt. Gen. Samuel C. Phillips (extreme left), who formerly served as Apollo program Director, Office of Manned Space Flight, NASA Headquarters; Dr. Charles A. Berry (third from left), Director, Medical Research and Operations Directorate, MSC; and Dr. George M. Low, Associate NASA Administrator.

Mission Control Center (MCC) View - Apollo 13 Splashdown - MSC

NASA Image and Video Library

1970-04-17

S70-35145 (17 April 1970) --- Overall view of Mission Operations Control Room in Mission Control Center at the Manned Spacecraft Center (MSC) during the ceremonies aboard the USS Iwo Jima, prime recovery ship for the Apollo 13 mission. Dr. Donald K. Slayton (in black shirt, left of center), director of Flight Crew Operations at MSC, and Chester M. Lee of the Apollo Program Directorate, Office of Manned Space Flight, NASA Headquarters, shake hands, while Dr. Rocco A. Petrone, Apollo program director, Office of Manned Space Flight, NASA Headquarters (standing, near Lee), watches the large screen showing astronaut James A. Lovell Jr., Apollo 13 commander, during the onboard ceremonies. In the foreground, Glynn S. Lunney (extreme left) and Eugene F. Kranz (smoking a cigar), two Apollo 13 flight directors, view the activity from their consoles.

View of Mission Control Center during Apollo 13 splashdown

NASA Technical Reports Server (NTRS)

1970-01-01

Overall view of Mission Operations Control Room in Mission Control Center at the Manned Spacecraft Center (MSC) during the ceremonies aboard the U.S.S. Iwo Jima, prime recovery ship for the Apollo 13 mission. Dr. Donald K. Slayton (in black shirt, left of center), Director of Flight Crew Operations at MSC, and Chester M. Lee of the Apollo Program Directorate, Office of Manned Space Flight, NASA Headquarters, shake hands, while Dr. Rocco A. Petrone, Apollo Program Director, Office of Manned Space Flight, NASA Headquarters (standing, near Lee), watches the large screen showing Astronaut James A. Lovell Jr., Apollo 13 commander, during the on-board ceremonies. In the foreground, Glynn S. Lunney (extreme left) and Eugene F. Kranz (smoking a cigar), two Apollo 13 Flight Directors, view the activity from their consoles.

SSS-A attitude control prelaunch analysis and operations plan

NASA Technical Reports Server (NTRS)

Werking, R. D.; Beck, J.; Gardner, D.; Moyer, P.; Plett, M.

1971-01-01

A description of the attitude control support being supplied by the Mission and Data Operations Directorate is presented. Descriptions of the computer programs being used to support the mission for attitude determination, prediction, control, and definitive attitude processing are included. In addition, descriptions of the operating procedures which will be used to accomplish mission objectives are provided.

Space Mission Operations Concept

NASA Technical Reports Server (NTRS)

Squibb, Gael F.

1996-01-01

This paper will discuss the concept of developing a space mission operations concept; the benefits of starting this system engineering task early; the neccessary inputs to the process; and the products that are generated.

MISSION CONTROL CENTER (MCC) VIEW - CONCLUSION APOLLO 11 CELEBRATION - MSC

NASA Image and Video Library

1969-07-24

S69-40024 (24 July 1969) --- NASA and Manned Spacecraft Center (MSC) officials join in with the flight controllers, in the Mission Operations Control Room (MOCR) in the Mission Control Center (MCC), in celebrating the successful conclusion of the Apollo 11 lunar landing mission. Identifiable in the picture, starting in foreground, are Dr. Robert R. Gilruth, MSC Director; George M. Low, Manager, Apollo Spacecraft Program, MSC; Dr. Christopher C. Kraft Jr., MSC Director of Flight Operation; U.S. Air Force Lt. Gen. Samuel C. Phillips (with glasses, looking downward), Apollo Program Director, Office of Manned Space Flight, NASA Headquarters; and Dr. George E. Mueller (with glasses, looking toward left), Associate Administrator, Office of Manned Space Flight, NASA Headquarters. Former astronaut John H. Glenn Jr. is standing behind Mr. Low.

Integrated mission management operations

NASA Technical Reports Server (NTRS)

1971-01-01

Operations required to launch a modular space station and to provides sustaining ground operations for support of that orbiting station throughout its 10 year mission are studied. A baseline, incrementally manned program and attendent experiment program options are derived. In addition, features of the program that significantly effect initial development and early operating costs are identified, and their impact on the program is assessed. A preliminary design of the approved modular space station configuration is formulated.

Tropical Rainfall Measurement Mission (TRMM) Operation Summary

NASA Technical Reports Server (NTRS)

Nio, Tomomi; Saito, Susumu; Stocker, Erich; Pawloski, James H.; Murayama, Yoshifumi; Ohata, Takeshi

2015-01-01

The Tropical Rainfall Measurement Mission (TRMM) is a joint U.S. and Japan mission to observe tropical rainfall, which was launched by H-II No. 6 from Tanegashima in Japan at 6:27 JST on November 28, 1997. After the two-month commissioning of TRMM satellite and instruments, the original nominal mission lifetime was three years. In fact, the operations has continued for approximately 17.5 years. This paper provides a summary of the long term operations of TRMM.

Operating and Managing a Backup Control Center

NASA Technical Reports Server (NTRS)

Marsh, Angela L.; Pirani, Joseph L.; Bornas, Nicholas

2010-01-01

Due to the criticality of continuous mission operations, some control centers must plan for alternate locations in the event an emergency shuts down the primary control center. Johnson Space Center (JSC) in Houston, Texas is the Mission Control Center (MCC) for the International Space Station (ISS). Due to Houston s proximity to the Gulf of Mexico, JSC is prone to threats from hurricanes which could cause flooding, wind damage, and electrical outages to the buildings supporting the MCC. Marshall Space Flight Center (MSFC) has the capability to be the Backup Control Center for the ISS if the situation is needed. While the MSFC Huntsville Operations Support Center (HOSC) does house the BCC, the prime customer and operator of the ISS is still the JSC flight operations team. To satisfy the customer and maintain continuous mission operations, the BCC has critical infrastructure that hosts ISS ground systems and flight operations equipment that mirrors the prime mission control facility. However, a complete duplicate of Mission Control Center in another remote location is very expensive to recreate. The HOSC has infrastructure and services that MCC utilized for its backup control center to reduce the costs of a somewhat redundant service. While labor talents are equivalent, experiences are not. Certain operations are maintained in a redundant mode, while others are simply maintained as single string with adequate sparing levels of equipment. Personnel at the BCC facility must be trained and certified to an adequate level on primary MCC systems. Negotiations with the customer were done to match requirements with existing capabilities, and to prioritize resources for appropriate level of service. Because some of these systems are shared, an activation of the backup control center will cause a suspension of scheduled HOSC activities that may share resources needed by the BCC. For example, the MCC is monitoring a hurricane in the Gulf of Mexico. As the threat to MCC

MISSION CONTROL CENTER (MCC) - APOLLO-SOYUZ TEST PROJECT (ASTP) - JSC

NASA Image and Video Library

1975-07-17

S75-28683 (17 July 1975) --- An overall view of the Mission Operations Control Room in the Mission Control Center during the joint U.S.-USSR Apollo-Soyuz Test Project docking mission in Earth orbit. M.P. Frank, the American senior ASTP flight director, is seated at his console in the right foreground. He is watching the large television monitor which shows a view of the Soyuz spacecraft as seen from the Apollo spacecraft during rendezvous and docking maneuvers.

Reinventing User Applications for Mission Control

NASA Technical Reports Server (NTRS)

Trimble, Jay Phillip; Crocker, Alan R.

2010-01-01

In 2006, NASA Ames Research Center's (ARC) Intelligent Systems Division, and NASA Johnson Space Centers (JSC) Mission Operations Directorate (MOD) began a collaboration to move user applications for JSC's mission control center to a new software architecture, intended to replace the existing user applications being used for the Space Shuttle and the International Space Station. It must also carry NASA/JSC mission operations forward to the future, meeting the needs for NASA's exploration programs beyond low Earth orbit. Key requirements for the new architecture, called Mission Control Technologies (MCT) are that end users must be able to compose and build their own software displays without the need for programming, or direct support and approval from a platform services organization. Developers must be able to build MCT components using industry standard languages and tools. Each component of MCT must be interoperable with other components, regardless of what organization develops them. For platform service providers and MOD management, MCT must be cost effective, maintainable and evolvable. MCT software is built from components that are presented to users as composable user objects. A user object is an entity that represents a domain object such as a telemetry point, a command, a timeline, an activity, or a step in a procedure. User objects may be composed and reused, for example a telemetry point may be used in a traditional monitoring display, and that same telemetry user object may be composed into a procedure step. In either display, that same telemetry point may be shown in different views, such as a plot, an alpha numeric, or a meta-data view and those views may be changed live and in place. MCT presents users with a single unified user environment that contains all the objects required to perform applicable flight controller tasks, thus users do not have to use multiple applications, the traditional boundaries that exist between multiple heterogeneous

Mission Operations and Navigation Toolkit Environment

NASA Technical Reports Server (NTRS)

Sunseri, Richard F.; Wu, Hsi-Cheng; Hanna, Robert A.; Mossey, Michael P.; Duncan, Courtney B.; Evans, Scott E.; Evans, James R.; Drain, Theodore R.; Guevara, Michelle M.; Martin Mur, Tomas J.;

VIew of Mission Control on first day of ASTP docking in Earth orbit

NASA Technical Reports Server (NTRS)

1975-01-01

An overall view of the Mission Operations Control Room in the Mission Control Center on the first day of the Apollo Soyuz Test Project (ASTP) docking in Earth orbit mission. The American ASTP flight controllers at JSC were monitoring the progress of the Soviet ASTP launch when this photograph was taken. The television monitor shows Cosmonaut Yuri V. Romanenko at his spacecraft communicator's console in the ASTP mission control center in the Soviet Union.

Mission Control, 1964

NASA Image and Video Library

2016-10-27

This archival image was released as part of a gallery comparing JPL's past and present, commemorating the 80th anniversary of NASA's Jet Propulsion Laboratory on Oct. 31, 2016. When spacecraft in deep space "phone home," they do it through NASA's Deep Space Network. Engineers in this room at NASA's Jet Propulsion Laboratory -- known as Mission Control -- monitor the flow of data. This image was taken in May 1964, when the building this nerve center is in, the Space Flight Operations Facility (Building 230), was dedicated at JPL. http://photojournal.jpl.nasa.gov/catalog/PIA21120

Mission Operations of Earth Observing-1 with Onboard Autonomy

NASA Technical Reports Server (NTRS)

Rabideau, Gregg; Tran, Daniel Q.; Chien, Steve; Cichy, Benjamin; Sherwood, Rob; Mandl, Dan; Frye, Stuart; Shulman, Seth; Szwaczkowski, Joseph; Boyer, Darrell;

Designing an Alternate Mission Operations Control Room

NASA Technical Reports Server (NTRS)

Montgomery, Patty; Reeves, A. Scott

2014-01-01

The Huntsville Operations Support Center (HOSC) is a multi-project facility that is responsible for 24x7 real-time International Space Station (ISS) payload operations management, integration, and control and has the capability to support small satellite projects and will provide real-time support for SLS launches. The HOSC is a serviceoriented/ highly available operations center for ISS payloads-directly supporting science teams across the world responsible for the payloads. The HOSC is required to endure an annual 2-day power outage event for facility preventive maintenance and safety inspection of the core electro-mechanical systems. While complete system shut-downs are against the grain of a highly available sub-system, the entire facility must be powered down for a weekend for environmental and safety purposes. The consequence of this ground system outage is far reaching: any science performed on ISS during this outage weekend is lost. Engineering efforts were focused to maximize the ISS investment by engineering a suitable solution capable of continuing HOSC services while supporting safety requirements. The HOSC Power Outage Contingency (HPOC) System is a physically diversified compliment of systems capable of providing identified real-time services for the duration of a planned power outage condition from an alternate control room. HPOC was designed to maintain ISS payload operations for approximately three continuous days during planned HOSC power outages and support a local Payload Operations Team, International Partners, as well as remote users from the alternate control room located in another building. This paper presents the HPOC architecture and lessons learned during testing and the planned maiden operational commissioning. Additionally, this paper documents the necessity of an HPOC capability given the unplanned HOSC Facility power outage on April 27th, 2011, as a result of the tornado outbreak that damaged the electrical grid to such a degree that

Modeling and Simulation for Mission Operations Work System Design

NASA Technical Reports Server (NTRS)

Sierhuis, Maarten; Clancey, William J.; Seah, Chin; Trimble, Jay P.; Sims, Michael H.

2003-01-01

Work System analysis and design is complex and non-deterministic. In this paper we describe Brahms, a multiagent modeling and simulation environment for designing complex interactions in human-machine systems. Brahms was originally conceived as a business process design tool that simulates work practices, including social systems of work. We describe our modeling and simulation method for mission operations work systems design, based on a research case study in which we used Brahms to design mission operations for a proposed discovery mission to the Moon. We then describe the results of an actual method application project-the Brahms Mars Exploration Rover. Space mission operations are similar to operations of traditional organizations; we show that the application of Brahms for space mission operations design is relevant and transferable to other types of business processes in organizations.

Avoiding Human Error in Mission Operations: Cassini Flight Experience

NASA Technical Reports Server (NTRS)

Burk, Thomas A.

2012-01-01

Operating spacecraft is a never-ending challenge and the risk of human error is ever- present. Many missions have been significantly affected by human error on the part of ground controllers. The Cassini mission at Saturn has not been immune to human error, but Cassini operations engineers use tools and follow processes that find and correct most human errors before they reach the spacecraft. What is needed are skilled engineers with good technical knowledge, good interpersonal communications, quality ground software, regular peer reviews, up-to-date procedures, as well as careful attention to detail and the discipline to test and verify all commands that will be sent to the spacecraft. Two areas of special concern are changes to flight software and response to in-flight anomalies. The Cassini team has a lot of practical experience in all these areas and they have found that well-trained engineers with good tools who follow clear procedures can catch most errors before they get into command sequences to be sent to the spacecraft. Finally, having a robust and fault-tolerant spacecraft that allows ground controllers excellent visibility of its condition is the most important way to ensure human error does not compromise the mission.

IUS/TUG orbital operations and mission support study. Volume 4: Project planning data

NASA Technical Reports Server (NTRS)

1975-01-01

Planning data are presented for the development phases of interim upper stage (IUS) and tug systems. Major project planning requirements, major event schedules, milestones, system development and operations process networks, and relevant support research and technology requirements are included. Topics discussed include: IUS flight software; tug flight software; IUS/tug ground control center facilities, personnel, data systems, software, and equipment; IUS mission events; tug mission events; tug/spacecraft rendezvous and docking; tug/orbiter operations interface, and IUS/orbiter operations interface.

Managing the Implementation of Mission Operations Automation

NASA Technical Reports Server (NTRS)

Sodano, R.; Crouse, P.; Odendahl, S.; Fatig, M.; McMahon, K.; Lakin, J.

2006-01-01

Reducing the cost of mission operations has necessitated a high level of automation both on spacecraft and ground systems. While automation on spacecraft is implemented during the design phase, ground system automation tends to be implemented during the prime mission operations phase. Experience has shown that this tendency for late automation development can be hindered by several factors: additional hardware and software resources may need to be procured; software must be developed and tested on a non-interference basis with primary operations with limited manpower; and established procedures may not be suited for automation requiring substantial rework. In this paper we will review the experience of successfully automating mission operations for seven on-orbit missions: the Compton Gamma Ray Observatory (CGRO), the Rossi X-Ray Timing Explorer (RXTE), the Advanced Composition Explorer (ACE), the Far Ultraviolet Spectroscopic Explorer (FUSE), Interplanetary Physics Laboratory (WIND), Polar Plasma Laboratory (POLAR), and the Imager for Magnetopause-to-Aurora Global Exploration (IMAGE). We will provide lessons learned in areas such as: spacecraft recorder management, procedure development, lights out commanding from the ground system vs. stored command loads, spacecraft contingency response time, and ground station interfaces. Implementing automation strategies during the mission concept and spacecraft integration and test phase as the most efficient method will be discussed.

MISSION CONTROL CENTER (MCC) - APOLLO-SOYUZ TEST PROJECT (ASTP)

NASA Image and Video Library

1975-07-15

S75-28519 (15 July 1975) --- An overall view of the Mission Operations Control Room in the Mission Control Center, Building 30, Johnson Space Center, on the first day of the Apollo-Soyuz Test Project docking mission in Earth orbit. This photograph was taken shortly before the American ASTP launch from the Kennedy Space Center. The television monitor in the center background shows the ASTP Apollo-Saturn 1B space vehicle on Pad B at KSC?s Launch Complex 39. The American ASTP liftoff followed the Soviet ASTP launch of the Soyuz space vehicle from Baikonur, Kazakhstan by seven and one-half hours.

Spacecraft attitude control for a solar electric geosynchronous transfer mission

NASA Technical Reports Server (NTRS)

Leroy, B. E.; Regetz, J. D., Jr.

1975-01-01

A study of the Attitude Control System (ACS) is made for a solar electric propulsion geosynchronous transfer mission. The basic mission considered is spacecraft injection into a low altitude, inclined orbit followed by low thrust orbit changing to achieve geosynchronous orbit. Because of the extended thrusting time, the mission performance is a strong function of the attitude control system. Two attitude control system design options for an example mission evolve from consideration of the spacecraft configuration, the environmental disturbances, and the probable ACS modes of operation. The impact of these design options on other spacecraft subsystems is discussed. The factors which must be considered in determining the ACS actuation and sensing subsystems are discussed. The effects of the actuation and sensing subsystems on the mission performance are also considered.

Remote Operations Control Center (ROCC)

NASA Technical Reports Server (NTRS)

1997-01-01

Undergraduate students Kristina Wines and Dena Renzo at Rensselaer Poloytech Institute (RPI) in Troy, NY, monitor the progress of the Isothermal Dendritic Growth Experiment (IDGE) during the U.S. Microgravity Payload-4 (USMP-4) mission (STS-87), Nov. 19 - Dec.5, 1997). Remote Operations Control Center (ROCC) like this one will become more common during operations with the International Space Station. The Isothermal Dendritic Growth Experiment (IDGE), flown on three Space Shuttle missions, is yielding new insights into virtually all industrially relevant metal and alloy forming operations. Photo credit: Rensselaer Polytechnic Institute (RPI)

Operations concepts for Mars missions with multiple mobile spacecraft

NASA Technical Reports Server (NTRS)

Dias, William C.

1993-01-01

Missions are being proposed which involve landing a varying number (anywhere from one to 24) of small mobile spacecraft on Mars. Mission proposals include sample returns, in situ geochemistry and geology, and instrument deployment functions. This paper discusses changes needed in traditional space operations methods for support of rover operations. Relevant differences include more frequent commanding, higher risk acceptance, streamlined procedures, and reliance on additional spacecraft autonomy, advanced fault protection, and prenegotiated decisions. New methods are especially important for missions with several Mars rovers operating concurrently against time limits. This paper also discusses likely mission design limits imposed by operations constraints .

OTF CCSDS Mission Operations Prototype Parameter Service. Phase I: Exit Presentation

NASA Technical Reports Server (NTRS)

Reynolds, Walter F.; Lucord, Steven A.; Stevens, John E.

2009-01-01

This slide presentation reviews the prototype of phase 1 of the parameter service design of the CCSDS mission operations. The project goals are to: (1) Demonstrate the use of Mission Operations standards to implement the Parameter Service (2) Demonstrate interoperability between Houston MCC and a CCSDS Mission Operations compliant mission operations center (3) Utilize Mission Operations Common Architecture. THe parameter service design, interfaces, and structures are described.

STS-114 Mission Support - Flight Controllers on Launch Day

NASA Image and Video Library

2005-07-26

Documentation of flight controllers in the White Flight Control Room (WFCR) on STS-114 Launch Day, July 26, 2005. View of Phil Engelauf and Flight Director Paul Hill standing at the Mission Operations Directorate (MOD) console.

Mission operations systems for planetary exploration

NASA Technical Reports Server (NTRS)

Mclaughlin, William I.; Wolff, Donna M.

1988-01-01

The purpose of the paper is twofold: (1) to present an overview of the processes comprising planetary mission operations as conducted at the Jet Propulsion Laboratory, and (2) to present a project-specific and historical context within which this evolving process functions. In order to accomplish these objectives, the generic uplink and downlink functions are described along with their specialization to current flight projects. Also, new multimission capabilities are outlined, including prototyping of advanced-capability software for subsequent incorporation into more automated future operations. Finally, a specific historical ground is provided by listing some major operations software plus a genealogy of planetary missions beginning with Mariner 2 in 1962.

View of Mission Control Center during the Apollo 13 emergency return

NASA Image and Video Library

1970-04-16

S70-35368 (16 April 1970) --- Overall view showing some of the feverish activity in the Mission Operations Control Room (MOCR) of the Mission Control Center (MCC) during the final 24 hours of the problem-plagued Apollo 13 mission. Here, flight controllers and several NASA/MSC officials confer at the flight director's console. When this picture was made, the Apollo 13 lunar landing had already been canceled, and the Apollo 13 crewmembers were in trans-Earth trajectory attempting to bring their crippled spacecraft back home.

Earth observation mission operation of COMS during in-orbit test

NASA Astrophysics Data System (ADS)

Cho, Young-Min

2011-11-01

Communication Ocean Meteorological Satellite (COMS) for the hybrid mission of meteorological observation, ocean monitoring, and telecommunication service was launched onto Geostationary Earth Orbit on June 27, 2010 and it is currently under normal operation service after the In-Orbit Test (IOT) phase. The COMS is located on 128.2° East of the geostationary orbit. In order to perform the three missions, the COMS has 3 separate payloads, the meteorological imager (MI), the Geostationary Ocean Color Imager (GOCI), and the Ka-band antenna. Each payload is dedicated to one of the three missions, respectively. The MI and GOCI perform the Earth observation mission of meteorological observation and ocean monitoring, respectively. During the IOT phase the functionality and the performance of many aspects of the COMS satellite and ground station have been checked through the Earth observation mission operation for the observation of the meteorological phenomenon over several areas of the Earth and the monitoring of marine environments around the Korean peninsula. The Earth observation mission operation of COMS during the IOT phase is introduced in terms of mission operation characteristics, mission planning, and mission operation results for the missions of meteorological observation and ocean monitoring, respectively.

Using Natural Language to Enable Mission Managers to Control Multiple Heterogeneous UAVs

NASA Technical Reports Server (NTRS)

Trujillo, Anna C.; Puig-Navarro, Javier; Mehdi, S. Bilal; Mcquarry, A. Kyle

2016-01-01

The availability of highly capable, yet relatively cheap, unmanned aerial vehicles (UAVs) is opening up new areas of use for hobbyists and for commercial activities. This research is developing methods beyond classical control-stick pilot inputs, to allow operators to manage complex missions without in-depth vehicle expertise. These missions may entail several heterogeneous UAVs flying coordinated patterns or flying multiple trajectories deconflicted in time or space to predefined locations. This paper describes the functionality and preliminary usability measures of an interface that allows an operator to define a mission using speech inputs. With a defined and simple vocabulary, operators can input the vast majority of mission parameters using simple, intuitive voice commands. Although the operator interface is simple, it is based upon autonomous algorithms that allow the mission to proceed with minimal input from the operator. This paper also describes these underlying algorithms that allow an operator to manage several UAVs.

SKYLAB III - POSTLAUNCH (MISSION CONTROL CENTER [MCC]) - JSC

NASA Image and Video Library

1973-08-06

S73-31964 (5 August 1973) --- This group of flight controllers discuss today's approaching extravehicular activity (EVA) to be performed by the Skylab 3 crewmen. They are, left to right, scientist-astronaut Story Musgrave, a Skylab 3 spacecraft communicator; Robert Kain and Scott Millican, both of the Crew Procedures Division, EVA Procedures Section; William C. Schneider, Skylab Program Director, NASA Headquarters; and Milton Windler, flight director. Windler points to the model of the Skylab space station cluster to indicate the location of the ATM's film magazines. The group stands near consoles in the Mission Operations Control Room (MOCR) of the JSC Mission Control Center (MCC). Photo credit: NASA

Formation Control for the MAXIM Mission

NASA Technical Reports Server (NTRS)

Luquette, Richard J.; Leitner, Jesse; Gendreau, Keith; Sanner, Robert M.

2004-01-01

Over the next twenty years, a wave of change is occurring in the space-based scientific remote sensing community. While the fundamental limits in the spatial and angular resolution achievable in spacecraft have been reached, based on today s technology, an expansive new technology base has appeared over the past decade in the area of Distributed Space Systems (DSS). A key subset of the DSS technology area is that which covers precision formation flying of space vehicles. Through precision formation flying, the baselines, previously defined by the largest monolithic structure which could fit in the largest launch vehicle fairing, are now virtually unlimited. Several missions including the Micro-Arcsecond X-ray Imaging Mission (MAXIM), and the Stellar Imager will drive the formation flying challenges to achieve unprecedented baselines for high resolution, extended-scene, interferometry in the ultraviolet and X-ray regimes. This paper focuses on establishing the feasibility for the formation control of the MAXIM mission. MAXIM formation flying requirements are on the order of microns, while Stellar Imager mission requirements are on the order of nanometers. This paper specifically addresses: (1) high-level science requirements for these missions and how they evolve into engineering requirements; and (2) the development of linearized equations of relative motion for a formation operating in an n-body gravitational field. Linearized equations of motion provide the ground work for linear formation control designs.

CRRES Prelaunch Mission Operation Report

NASA Technical Reports Server (NTRS)

1990-01-01

The overall NASA Combined Release and Radiation Effects Satellite (CRRES) program consists of a series of chemical releases from the PEGSAT spacecraft, the CRRES spacecraft and sounding rockets. The first chemical releases were made from the PEGSAT spacecraft in April, 1990 over northern Canada. In addition to the releases planned from the CRRES spacecraft there are releases from sounding rockets planned from the Kwajalein rocket range in July and August, 1990 and from Puerto Rico in June and July, 1991. It shows the major milestones in the overall CRRES program. This Mission Operations Report only describes the NASA mission objectives of the CRRES/Geosynchronous Transfer Orbit (GTO) mission.

View of activity in Mission Control Center during Apollo 15 EVA

NASA Image and Video Library

1971-07-30

S71-41836 (2 Aug. 1971) --- Scientist-astronaut Joseph P. Allen, left, directs the attention of astronaut Richard F. Gordon Jr., to an occurrence out of view at right in the Mission Control Center's (MCC) Mission Operations Control Room (MOCR), while Dr. Donald K. (Deke) Slayton, on right with back to camera, views activity of Apollo 15 on a large screen at the front of the MOCR. Astronauts David R. Scott and James B. Irwin are seen on the screen performing tasks of the mission's third extravehicular activity (EVA), on Aug. 2, 1971. Dr. Slayton is director of Flight Crew Operations, NASA-MSC; Gordon is Apollo 15 backup commander; and Dr. Allen is an Apollo 15 spacecraft communicator.

A new systems engineering approach to streamlined science and mission operations for the Far Ultraviolet Spectroscopic Explorer (FUSE)

NASA Technical Reports Server (NTRS)

Butler, Madeline J.; Sonneborn, George; Perkins, Dorothy C.

1994-01-01

The Mission Operations and Data Systems Directorate (MO&DSD, Code 500), the Space Sciences Directorate (Code 600), and the Flight Projects Directorate (Code 400) have developed a new approach to combine the science and mission operations for the FUSE mission. FUSE, the last of the Delta-class Explorer missions, will obtain high resolution far ultraviolet spectra (910 - 1220 A) of stellar and extragalactic sources to study the evolution of galaxies and conditions in the early universe. FUSE will be launched in 2000 into a 24-hour highly eccentric orbit. Science operations will be conducted in real time for 16-18 hours per day, in a manner similar to the operations performed today for the International Ultraviolet Explorer. In a radical departure from previous missions, the operations concept combines spacecraft and science operations and data processing functions in a single facility to be housed in the Laboratory for Astronomy and Solar Physics (Code 680). A small missions operations team will provide the spacecraft control, telescope operations and data handling functions in a facility designated as the Science and Mission Operations Center (SMOC). This approach will utilize the Transportable Payload Operations Control Center (TPOCC) architecture for both spacecraft and instrument commanding. Other concepts of integrated operations being developed by the Code 500 Renaissance Project will also be employed for the FUSE SMOC. The primary objective of this approach is to reduce development and mission operations costs. The operations concept, integration of mission and science operations, and extensive use of existing hardware and software tools will decrease both development and operations costs extensively. This paper describes the FUSE operations concept, discusses the systems engineering approach used for its development, and the software, hardware and management tools that will make its implementation feasible.

Expert systems and advanced automation for space missions operations

NASA Technical Reports Server (NTRS)

Durrani, Sajjad H.; Perkins, Dorothy C.; Carlton, P. Douglas

1990-01-01

Increased complexity of space missions during the 1980s led to the introduction of expert systems and advanced automation techniques in mission operations. This paper describes several technologies in operational use or under development at the National Aeronautics and Space Administration's Goddard Space Flight Center. Several expert systems are described that diagnose faults, analyze spacecraft operations and onboard subsystem performance (in conjunction with neural networks), and perform data quality and data accounting functions. The design of customized user interfaces is discussed, with examples of their application to space missions. Displays, which allow mission operators to see the spacecraft position, orientation, and configuration under a variety of operating conditions, are described. Automated systems for scheduling are discussed, and a testbed that allows tests and demonstrations of the associated architectures, interface protocols, and operations concepts is described. Lessons learned are summarized.

Implementation and Test of the Automatic Flight Dynamics Operations for Geostationary Satellite Mission

NASA Astrophysics Data System (ADS)

Park, Sangwook; Lee, Young-Ran; Hwang, Yoola; Javier Santiago Noguero Galilea

2009-12-01

This paper describes the Flight Dynamics Automation (FDA) system for COMS Flight Dynamics System (FDS) and its test result in terms of the performance of the automation jobs. FDA controls the flight dynamics functions such as orbit determination, orbit prediction, event prediction, and fuel accounting. The designed FDA is independent from the specific characteristics which are defined by spacecraft manufacturer or specific satellite missions. Therefore, FDA could easily links its autonomous job control functions to any satellite mission control system with some interface modification. By adding autonomous system along with flight dynamics system, it decreases the operator’s tedious and repeated jobs but increase the usability and reliability of the system. Therefore, FDA is used to improve the completeness of whole mission control system’s quality. The FDA is applied to the real flight dynamics system of a geostationary satellite, COMS and the experimental test is performed. The experimental result shows the stability and reliability of the mission control operations through the automatic job control.

View of Mission Control Center during the Apollo 13 oxygen cell failure

NASA Technical Reports Server (NTRS)

1970-01-01

Several persons important to the Apollo 13 mission, at consoles in the Mission Operations Control Room of the Mission Control Center (MCC). Seated at consoles, from left to right, are Astronaut Donald K. Slayton, Director of Flight Crew Operations; Astronaut Jack R. Lousma, Shift 3 spacecraft communicator; and Astronaut John W. Young, commander of the Apollo 13 back-up crew. Standing, left to right, are Astronaut Tom K. Mattingly, who was replaced as Apollo 13 command module pilot after it was learned he may come down with measles, and Astronaut Vance D. Brand, Shift 2 spacecraft communicator. Several hours earlier crew members of the Apollo 13 mission reported to MCC that trouble had developed with an oxygen cell in their spacecraft.

LANDSAT-D Mission Operations Review (MOR)

NASA Technical Reports Server (NTRS)

1982-01-01

The integrated LANDSAT-D systems operation plan is presented and discussed with respect to functional elements, personnel, and procedures. Specifically, a review of the LANDSAT-D program, mission requirements and management, and flight operations is given.

Making adaptable systems work for mission operations: A case study

NASA Technical Reports Server (NTRS)

Holder, Barbara E.; Levesque, Michael E.

1993-01-01

The Advanced Multimission Operations System (AMMOS) at NASA's Jet Propulsion Laboratory is based on a highly adaptable multimission ground data system (MGDS) for mission operations. The goal for MGDS is to support current flight project science and engineering personnel and to meet the demands of future missions while reducing associated operations and software development costs. MGDS has become a powerful and flexible mission operations system by using a network of heterogeneous workstations, emerging open system standards, and selecting an adaptable tools-based architecture. Challenges in developing adaptable systems for mission operations and the benefits of this approach are described.

AE-C attitude determination and control prelaunch analysis and operations plan

NASA Technical Reports Server (NTRS)

Werking, R. D.; Headrick, R. D.; Manders, C. F.; Woolley, R. D.

1973-01-01

A description of attitude control support being supplied by the Mission and Data Operations Directorate is presented. Included are descriptions of the computer programs being used to support the missions for attitude determination, prediction, and control. In addition, descriptions of the operating procedures which will be used to accomplish mission objectives are provided.

The MSG Central Facility - A Mission Control System for Windows NT

NASA Astrophysics Data System (ADS)

Thompson, R.

The MSG Central Facility, being developed by Science Systems for EUMETSAT1, represents the first of a new generation of satellite mission control systems, based on the Windows NT operating system. The system makes use of a range of new technologies to provide an integrated environment for the planning, scheduling, control and monitoring of the entire Meteosat Second Generation mission. It supports packetised TM/TC and uses Science System's Space UNiT product to provide automated operations support at both Schedule (Timeline) and Procedure levels. Flexible access to historical data is provided through an operations archive based on ORACLE Enterprise Server, hosted on a large RAID array and off-line tape jukebox. Event driven real-time data distribution is based on the CORBA standard. Operations preparation and configuration control tools form a fully integrated element of the system.

SCOSII: ESA's new generation of mission control systems: The user's perspective

NASA Technical Reports Server (NTRS)

Kaufeler, P.; Pecchioli, M.; Shurmer, I.

1994-01-01

In 1974 ESOC decided to develop a reusable Mission Control System infrastructure for ESA's missions operated under its responsibility. This triggered a long and successful product development line, which started with the Multi Mission Support System (MSSS) which entered in service in 1977 and is still being used today by the MARECS and ECS missions; it was followed in 1989 by a second generation of systems known as SCOS-I, which was/is used by the Hipparcos, ERS-1 and EURECA missions and will continue to support all future ESCO controlled missions until approximately 1995. In the meantime the increasing complexity of future missions together with the emergence of new hardware and software technologies have led ESOC to go for the development of a third generation of control systems, SCOSII, which will support their future missions up to at least the middle of the next decade. The objective of the paper is to present the characteristics of the SCOSII system from the perspective of the mission control team; i.e. it will concentrate on the improvements and advances in the performance, functionality and work efficiency of the system.

STS-26 long duration simulation in JSC Mission Control Center (MCC) Bldg 30

NASA Technical Reports Server (NTRS)

1988-01-01

STS-26 long duration simulation is conducted in JSC Mission Control Center (MCC) Bldg 30 Flight Control Room (FCR). Director of Mission Operations Directorate (MOD) Eugene F. Kranz (left) and Chief of the Flight Directors Office Tommy W. Holloway monitor activity during the simulation. The two are at their normal stations on the rear row of consoles. The integrated simulation involves MCC flight controllers communicating with crewmembers stationed in the fixed based (FB) shuttle mission simulator (SMS) located in JSC Mission Simulation and Training Facility Bldg 5.

Voice loops as coordination aids in space shuttle mission control.

PubMed

Patterson, E S; Watts-Perotti, J; Woods, D D

1999-01-01

Voice loops, an auditory groupware technology, are essential coordination support tools for experienced practitioners in domains such as air traffic management, aircraft carrier operations and space shuttle mission control. They support synchronous communication on multiple channels among groups of people who are spatially distributed. In this paper, we suggest reasons for why the voice loop system is a successful medium for supporting coordination in space shuttle mission control based on over 130 hours of direct observation. Voice loops allow practitioners to listen in on relevant communications without disrupting their own activities or the activities of others. In addition, the voice loop system is structured around the mission control organization, and therefore directly supports the demands of the domain. By understanding how voice loops meet the particular demands of the mission control environment, insight can be gained for the design of groupware tools to support cooperative activity in other event-driven domains.

Voice loops as coordination aids in space shuttle mission control

NASA Technical Reports Server (NTRS)

Patterson, E. S.; Watts-Perotti, J.; Woods, D. D.

1999-01-01

Voice loops, an auditory groupware technology, are essential coordination support tools for experienced practitioners in domains such as air traffic management, aircraft carrier operations and space shuttle mission control. They support synchronous communication on multiple channels among groups of people who are spatially distributed. In this paper, we suggest reasons for why the voice loop system is a successful medium for supporting coordination in space shuttle mission control based on over 130 hours of direct observation. Voice loops allow practitioners to listen in on relevant communications without disrupting their own activities or the activities of others. In addition, the voice loop system is structured around the mission control organization, and therefore directly supports the demands of the domain. By understanding how voice loops meet the particular demands of the mission control environment, insight can be gained for the design of groupware tools to support cooperative activity in other event-driven domains.

NASA's OCA Mirroring System: An Application of Multiagent Systems in Mission Control

NASA Technical Reports Server (NTRS)

Sierhuis, Maarten; Clancey, William J.; vanHoof, Ron J. J.; Seah, Chin H.; Scott, Michael S.; Nado, Robert A.; Blumenberg, Susan F.; Shafto, Michael G.; Anderson, Brian L.; Bruins, Anthony C.;

Inflight - STS-11/41B (MISSION CONTROL CENTER [MCC]) - JSC

NASA Image and Video Library

1984-02-08

S84-26503 (7 Feb 1984) --- This wide angle, overall view of activity in the mission operations control room in the Johnson Space Center?s mission control center, was photographed during the first even non-tethered extravehicular activity (EVA) in space. The large MOCR monitor and those at individual consoles feed to ground controllers the spectacular scene of Astronaut Bruce McCandless II ?suspended? I space above the blue and white Earth. The scene was photographed at 7:30 a.m. (CST), February 7, 1984.

Computer support for cooperative tasks in Mission Operations Centers

NASA Technical Reports Server (NTRS)

Fox, Jeffrey; Moore, Mike

1994-01-01

Traditionally, spacecraft management has been performed by fixed teams of operators in Mission Operations Centers. The team cooperatively: (1) ensures that payload(s) on spacecraft perform their work; and (2) maintains the health and safety of the spacecraft through commanding and monitoring the spacecraft's subsystems. In the future, the task demands will increase and overload the operators. This paper describes the traditional spacecraft management environment and describes a new concept in which groupware will be used to create a Virtual Mission Operations Center. Groupware tools will be used to better utilize available resources through increased automation and dynamic sharing of personnel among missions.

Dr. Gilruth and Dr. Kraft - Mission Control Center (MCC) - Apollo V Launch - MSC

NASA Image and Video Library

1968-01-22

S68-18733 (22 Jan. 1968) --- Dr. Robert R. Gilruth (right), MSC Director, sits with Dr. Christopher C. Kraft Jr., MSC director of flight operations, at his flight operations director console in the Mission Control Center, Building 30, during the Apollo 5 (LM-1/Saturn 204) unmanned space mission.

VIew of Mission Control on first day of ASTP docking in Earth orbit

NASA Image and Video Library

1975-07-15

S75-28483 (15 July 1975) --- An overall view of the Mission Operations Control Room in the Mission Control Center on the first day of the Apollo-Soyuz Test Project docking mission in Earth orbit. The American ASTP flight controllers at NASA's Johnson Space Center were monitoring the progress of the Soviet ASTP launch when this photograph was taken. The television monitor shows cosmonaut Yuri V. Romanenko at his spacecraft communicator?s console in the ASTP mission control center in the Soviet Union. The American ASTP liftoff followed the Soviet ASTP launch by seven and one-half hours.

Management of information for mission operations using automated keyword referencing

NASA Technical Reports Server (NTRS)

Davidson, Roger A.; Curran, Patrick S.

1993-01-01

Although millions of dollars have helped to improve the operability and technology of ground data systems for mission operations, almost all mission documentation remains bound in printed volumes. This form of documentation is difficult and timeconsuming to use, may be out-of-date, and is usually not cross-referenced with other related volumes of mission documentation. A more effective, automated method of mission information access is needed. A new method of information management for mission operations using automated keyword referencing is proposed. We expound on the justification for and the objectives of this concept. The results of a prototype tool for mission information access that uses a hypertextlike user interface and existing mission documentation are shared. Finally, the future directions and benefits of our proposed work are described.

Mission Control Center (MCC) - Apollo 13 - Fourth (4th) Television Signal - MSC

NASA Image and Video Library

1970-04-13

S70-35139 (13 April 1970) --- Overall view of the Mission Operations Control Room (MOCR) in the Mission Control Center (MCC) at Manned Spacecraft Center (MSC), during the fourth television transmission from the Apollo 13 mission in space. Eugene F. Kranz (foreground, back to camera), one of four Apollo 13 flight directors, views the large screen at front of MOCR, astronaut Fred W. Haise Jr., lunar module pilot, is seen on the screen. The fourth TV transmission from the Apollo 13 mission was on the evening of April 13, 1970.

Overall view of Mission Control Center during Apollo 14

NASA Image and Video Library

1971-01-31

S71-16879 (31 Jan. 1971) --- Overall view of activity in the Mission Operations Control Room in the Mission Control Center during the Apollo 14 transposition and docking maneuvers. The Apollo 14 Lunar Module, still attached to the Saturn IVB stage, can be seen on the large television monitor. Due to difficulty with the docking mechanism six attempts were made before a successful "hard dock" of the Command Module with the Lunar Module was accomplished. Aboard the Command Module were astronauts Alan B. Shepard Jr., Stuart A. Roosa, and Edgar D. Mitchell.

EURECA mission control experience and messages for the future

NASA Technical Reports Server (NTRS)

Huebner, H.; Ferri, P.; Wimmer, W.

1994-01-01

EURECA is a retrievable space platform which can perform multi-disciplinary scientific and technological experiments in a Low Earth Orbit for a typical mission duration of six to twelve months. It is deployed and retrieved by the NASA Space Shuttle and is designed to support up to five flights. The first mission started at the end of July 1992 and was successfully completed with the retrieval in June 1993. The operations concept and the ground segment for the first EURECA mission are briefly introduced. The experiences in the preparation and the conduction of the mission from the flight control team point of view are described.

IMP-J attitude control prelaunch analysis and operations plan

NASA Technical Reports Server (NTRS)

Hooper, H. L.; Mckendrew, J. B.; Repass, G. D.

1973-01-01

A description of the attitude control support being supplied for the Explorer 50 mission is given. Included in the document are descriptions of the computer programs being used to support attitude determination, prediction, and control for the mission and descriptions of the operating procedures that will be used to accomplish mission objectives.

Spaceport operations for deep space missions

NASA Technical Reports Server (NTRS)

Holt, Alan C.

1990-01-01

Space Station Freedom is designed with the capability to cost-effectively evolve into a transportation node which can support manned lunar and Mars missions. To extend a permanent human presence to the outer planets (moon outposts) and to nearby star systems, additional orbiting space infrastructure and great advances in propulsion system and other technologies will be required. To identify primary operations and management requirements for these deep space missions, an interstellar design concept was developed and analyzed. The assembly, test, servicing, logistics resupply, and increment management techniques anticipated for lunar and Mars missions appear to provide a pattern which can be extended in an analogous manner to deep space missions. A long range, space infrastructure development plan (encompassing deep space missions) coupled with energetic, breakthrough level propulsion research should be initiated now to assist in making the best budget and schedule decisions.

Autonomous Satellite Operations Via Secure Virtual Mission Operations Center

NASA Technical Reports Server (NTRS)

Miller, Eric; Paulsen, Phillip E.; Pasciuto, Michael

2011-01-01

The science community is interested in improving their ability to respond to rapidly evolving, transient phenomena via autonomous rapid reconfiguration, which derives from the ability to assemble separate but collaborating sensors and data forecasting systems to meet a broad range of research and application needs. Current satellite systems typically require human intervention to respond to triggers from dissimilar sensor systems. Additionally, satellite ground services often need to be coordinated days or weeks in advance. Finally, the boundaries between the various sensor systems that make up such a Sensor Web are defined by such things as link delay and connectivity, data and error rate asymmetry, data reliability, quality of service provisions, and trust, complicating autonomous operations. Over the past ten years, researchers from the NASA Glenn Research Center (GRC), General Dynamics, Surrey Satellite Technology Limited (SSTL), Cisco, Universal Space Networks (USN), the U.S. Geological Survey (USGS), the Naval Research Laboratory, the DoD Operationally Responsive Space (ORS) Office, and others have worked collaboratively to develop a virtual mission operations capability. Called VMOC (Virtual Mission Operations Center), this new capability allows cross-system queuing of dissimilar mission unique systems through the use of a common security scheme and published application programming interfaces (APIs). Collaborative VMOC demonstrations over the last several years have supported the standardization of spacecraft to ground interfaces needed to reduce costs, maximize space effects to the user, and allow the generation of new tactics, techniques and procedures that lead to responsive space employment.

Personnel - Gemini-Titan (GT)-10 - Mission Control Center (MCC) - MSC

NASA Image and Video Library

1966-07-18

S66-43377 (18 July 1966) --- Standing at the flight director's console, viewing the Gemini-10 flight display in the Mission Control Center, are (left to right) William C. Schneider, Mission Director; Glynn Lunney, Prime Flight Director; Christopher C. Kraft Jr., MSC Director of Flight Operations; and Charles W. Mathews, Manager, Gemini Program Office. Photo credit: NASA

Sleep and cognitive function of crewmembers and mission controllers working 24-h shifts during a simulated 105-day spaceflight mission

NASA Astrophysics Data System (ADS)

Barger, Laura K.; Wright, Kenneth P.; Burke, Tina M.; Chinoy, Evan D.; Ronda, Joseph M.; Lockley, Steven W.; Czeisler, Charles A.

2014-01-01

The success of long-duration space missions depends on the ability of crewmembers and mission support specialists to be alert and maintain high levels of cognitive function while operating complex, technical equipment. We examined sleep, nocturnal melatonin levels and cognitive function of crewmembers and the sleep and cognitive function of mission controllers who participated in a high-fidelity 105-day simulated spaceflight mission at the Institute of Biomedical Problems (Moscow). Crewmembers were required to perform daily mission duties and work one 24-h extended duration work shift every sixth day. Mission controllers nominally worked 24-h extended duration shifts. Supplemental lighting was provided to crewmembers and mission controllers. Participants' sleep was estimated by wrist-actigraphy recordings. Overall, results show that crewmembers and mission controllers obtained inadequate sleep and exhibited impaired cognitive function, despite countermeasure use, while working extended duration shifts. Crewmembers averaged 7.04±0.92 h (mean±SD) and 6.94±1.08 h (mean±SD) in the two workdays prior to the extended duration shifts, 1.88±0.40 h (mean±SD) during the 24-h work shift, and then slept 10.18±0.96 h (mean±SD) the day after the night shift. Although supplemental light was provided, crewmembers' average nocturnal melatonin levels remained elevated during extended 24-h work shifts. Naps and caffeine use were reported by crewmembers during ˜86% and 45% of extended night work shifts, respectively. Even with reported use of wake-promoting countermeasures, significant impairments in cognitive function were observed. Mission controllers slept 5.63±0.95 h (mean±SD) the night prior to their extended duration work shift. On an average, 89% of night shifts included naps with mission controllers sleeping an average of 3.4±1.0 h (mean±SD) during the 24-h extended duration work shift. Mission controllers also showed impaired cognitive function during extended

Guidance system operations plan for manned CM earth orbital missions using program SKYLARK 1. Section 4: Operational modes

NASA Technical Reports Server (NTRS)

Dunbar, J. C.

1972-01-01

The operational modes for the guidance system operations plan for Program SKYLARK 1 are presented. The procedures control the guidance and navigation system interfaces with the flight crew and the mission control center. The guidance operational concept is designed to comprise a set of manually initiated programs and functions which may be arranged by the flight crew to implement a large class of flight plans. This concept will permit both a late flight plan definition and a capability for real time flight plan changes.

View of Mission Control Center during the Apollo 13 oxygen cell failure

NASA Image and Video Library

1970-04-14

S70-34902 (14 April 1970) --- Several persons important to the Apollo 13 mission, at consoles in the Mission Operations Control Room (MOCR) of the Mission Control Center (MCC). Seated at consoles, from left to right, are astronauts Donald K. Slayton, director of flight crew operations; astronaut Jack R. Lousma, Shift 3 spacecraft communicator; and astronaut John W. Young, commander of the Apollo 13 backup crew. Standing, left to right, are astronaut Tom K. Mattingly II, who was replaced as Apollo 13 command module pilot after it was learned he may come down with measles, and astronaut Vance D. Brand, Shift 2 spacecraft communicator. Several hours earlier, in the late evening hours of April 13, crew members of the Apollo 13 mission reported to MCC that trouble had developed with an oxygen cell on their spacecraft.

Early Mission Maneuver Operations for the Deep Space Climate Observatory Sun-Earth L1 Libration Point Mission

NASA Technical Reports Server (NTRS)

Roberts, Craig; Case, Sara; Reagoso, John; Webster, Cassandra

2015-01-01

The Deep Space Climate Observatory mission launched on February 11, 2015, and inserted onto a transfer trajectory toward a Lissajous orbit around the Sun-Earth L1 libration point. This paper presents an overview of the baseline transfer orbit and early mission maneuver operations leading up to the start of nominal science orbit operations. In particular, the analysis and performance of the spacecraft insertion, mid-course correction maneuvers, and the deep-space Lissajous orbit insertion maneuvers are discussed, com-paring the baseline orbit with actual mission results and highlighting mission and operations constraints..

Operational effectiveness of a Multiple Aquila Control System (MACS)

NASA Technical Reports Server (NTRS)

Brown, R. W.; Flynn, J. D.; Frey, M. R.

1983-01-01

The operational effectiveness of a multiple aquila control system (MACS) was examined under a variety of remotely piloted vehicle (RPV) mission configurations. The set of assumptions and inputs used to form the rules under which a computerized simulation of MACS was run is given. The characteristics that are to govern MACS operations include: the battlefield environment that generates the requests for RPV missions, operating time-lines of the RPV-peculiar equipment, maintenance requirements, and vulnerability to enemy fire. The number of RPV missions and the number of operation days are discussed. Command, control, and communication data rates are estimated by determining how many messages are passed and what information is necessary in them to support ground coordination between MACS sections.

Mission Analysis, Operations, and Navigation Toolkit Environment (Monte) Version 040

NASA Technical Reports Server (NTRS)

Sunseri, Richard F.; Wu, Hsi-Cheng; Evans, Scott E.; Evans, James R.; Drain, Theodore R.; Guevara, Michelle M.

2012-01-01

Monte is a software set designed for use in mission design and spacecraft navigation operations. The system can process measurement data, design optimal trajectories and maneuvers, and do orbit determination, all in one application. For the first time, a single software set can be used for mission design and navigation operations. This eliminates problems due to different models and fidelities used in legacy mission design and navigation software. The unique features of Monte 040 include a blowdown thruster model for GRAIL (Gravity Recovery and Interior Laboratory) with associated pressure models, as well as an updated, optimalsearch capability (COSMIC) that facilitated mission design for ARTEMIS. Existing legacy software lacked the capabilities necessary for these two missions. There is also a mean orbital element propagator and an osculating to mean element converter that allows long-term orbital stability analysis for the first time in compiled code. The optimized trajectory search tool COSMIC allows users to place constraints and controls on their searches without any restrictions. Constraints may be user-defined and depend on trajectory information either forward or backwards in time. In addition, a long-term orbit stability analysis tool (morbiter) existed previously as a set of scripts on top of Monte. Monte is becoming the primary tool for navigation operations, a core competency at JPL. The mission design capabilities in Monte are becoming mature enough for use in project proposals as well as post-phase A mission design. Monte has three distinct advantages over existing software. First, it is being developed in a modern paradigm: object- oriented C++ and Python. Second, the software has been developed as a toolkit, which allows users to customize their own applications and allows the development team to implement requirements quickly, efficiently, and with minimal bugs. Finally, the software is managed in accordance with the CMMI (Capability Maturity Model

View - Mission Control Center (MCC) - Lunar Surface - Apollo XI Extravehicular Activity (EVA) - MSC

NASA Image and Video Library

1969-07-20

S69-39815 (20 July 1969) --- Interior view of the Mission Operations Control Room (MOCR) in the Mission Control Center (MCC) during the Apollo 11 lunar extravehicular activity (EVA). The television monitor shows astronauts Neil A. Armstrong and Edwin E. Aldrin Jr. on the surface of the moon.

AOCS operations preparation for the BepiColombo mission to mercury

NASA Astrophysics Data System (ADS)

Steiger, C.; Altay, A.; Montagnon, E.; Companys, V.

2018-06-01

The 2018 ESA/JAXA BepiColombo mission to Mercury features a complex modular design, with two scientific Mercury orbiters and a cruise module. The spacecraft (S/C) and mission design lead to a number of challenges for the attitude and orbit control system (AOCS), including electric propulsion usage during cruise to Mercury, AOCS capability to deal with several S/C configurations, and strict attitude constraints owing to the harsh thermal environment. This paper presents the activities for AOCS operations preparation by ESA/ESOC, covering the current preparation status as well as an outlook on upcoming activities before launch.

Cultural Challenges Faced by American Mission Control Personnel Working with International Partners

NASA Technical Reports Server (NTRS)

Clement, J. L.; Ritsher, J. B.

2006-01-01

Operating the International Space Station (ISS) involves an indefinite, continuous series of long-duration international missions, and this requires an unprecedented degree of cooperation across multiple sites, organizations, and nations. Both junior and senior mission control personnel have had to find ways to address the cultural challenges inherent in such work, but neither have had systematic training in how to do so. The goals of this study were to identify and evaluate the major cultural challenges faced by ISS mission control personnel and to highlight the approaches that they have found most effective to surmount these challenges. We pay particular attention to the approaches successfully employed by the senior personnel and the training needs identified by the junior personnel. We also evaluate the extent to which the identified approaches and needs are consistent across the two samples. METHODS: Participants included a sample of 14 senior ISS flight controllers and a contrasting sample of 12 more junior controllers. All participants were mission operations specialists chosen on the basis of having worked extensively with international partners. Data were collected using a semi-structured qualitative interview and content analyzed using an iterative process with multiple coders and consensus meetings to resolve discrepancies. RESULTS: The senior respondents had substantial consensus on several cultural challenges and on key strategies for dealing with them, and they offered a wide range of specific tactics for implementing these strategies. Data from the junior respondents will be presented for the first time at the meeting. DISCUSSION: Although specific to American ISS personnel, our results are consistent with recent management, cultural, and aerospace research on other populations. We aim to use our results to improve training for current and future mission control personnel working in international or multicultural mission operations teams.

Mars Pathfinder mission operations concepts

NASA Technical Reports Server (NTRS)

Sturms, Francis M., Jr.; Dias, William C.; Nakata, Albert Y.; Tai, Wallace S.

1994-01-01

The Mars Pathfinder Project plans a December 1996 launch of a single spacecraft. After jettisoning a cruise stage, an entry body containing a lander and microrover will directly enter the Mars atmosphere and parachute to a hard landing near the sub-solar latitude of 15 degrees North in July 1997. Primary surface operations last for 30 days. Cost estimates for Pathfinder ground systems development and operations are not only lower in absolute dollars, but also are a lower percentage of total project costs than in past planetary missions. Operations teams will be smaller and fewer than typical flight projects. Operations scenarios have been developed early in the project and are being used to guide operations implementation and flight system design. Recovery of key engineering data from entry, descent, and landing is a top mission priority. These data will be recorded for playback after landing. Real-time tracking of a modified carrier signal through this phase can provide important insight into the spacecraft performance during entry, descent, and landing in the event recorded data is never recovered. Surface scenarios are dominated by microrover activity and lander imaging during 7 hours of the Mars day from 0700 to 1400 local solar time. Efficient uplink and downlink processes have been designed to command the lander and microrover each Mars day.

Robotic assembly and maintenance of future space stations based on the ISS mission operations experience

NASA Astrophysics Data System (ADS)

Rembala, Richard; Ower, Cameron

2009-10-01

MDA has provided 25 years of real-time engineering support to Shuttle (Canadarm) and ISS (Canadarm2) robotic operations beginning with the second shuttle flight STS-2 in 1981. In this capacity, our engineering support teams have become familiar with the evolution of mission planning and flight support practices for robotic assembly and support operations at mission control. This paper presents observations on existing practices and ideas to achieve reduced operational overhead to present programs. It also identifies areas where robotic assembly and maintenance of future space stations and space-based facilities could be accomplished more effectively and efficiently. Specifically, our experience shows that past and current space Shuttle and ISS assembly and maintenance operations have used the approach of extensive preflight mission planning and training to prepare the flight crews for the entire mission. This has been driven by the overall communication latency between the earth and remote location of the space station/vehicle as well as the lack of consistent robotic and interface standards. While the early Shuttle and ISS architectures included robotics, their eventual benefits on the overall assembly and maintenance operations could have been greater through incorporating them as a major design driver from the beginning of the system design. Lessons learned from the ISS highlight the potential benefits of real-time health monitoring systems, consistent standards for robotic interfaces and procedures and automated script-driven ground control in future space station assembly and logistics architectures. In addition, advances in computer vision systems and remote operation, supervised autonomous command and control systems offer the potential to adjust the balance between assembly and maintenance tasks performed using extra vehicular activity (EVA), extra vehicular robotics (EVR) and EVR controlled from the ground, offloading the EVA astronaut and even the robotic

Lessons Learned from Optical Payload for Lasercomm Science (OPALS) Mission Operations

NASA Technical Reports Server (NTRS)

Sindiy, Oleg V.; Abrahamson, Matthew J.; Biswas, Abhijit; Wright, Malcolm W.; Padams, Jordan H.; Konyha, Alexander L.

2015-01-01

This paper provides an overview of Optical Payload for Lasercomm Science (OPALS) activities and lessons learned during mission operations. Activities described cover the periods of commissioning, prime, and extended mission operations, during which primary and secondary mission objectives were achieved for demonstrating space-to-ground optical communications. Lessons learned cover Mission Operations System topics in areas of: architecture verification and validation, staffing, mission support area, workstations, workstation tools, interfaces with support services, supporting ground stations, team training, procedures, flight software upgrades, post-processing tools, and public outreach.

Immersive Environments for Mission Operations: Beyond Mars Pathfinder

NASA Technical Reports Server (NTRS)

Wright, J.; Hartman, F.; Cooper, B.

1998-01-01

Immersive environments are just beginning to be used to support mission operations at the Jet Propulsion Laboratory. This technology contributed to the Mars Pathfinder Mission in planning sorties for the Sojourner rover.

Design Reference Missions (DRM): Integrated ODM 'Air-Taxi' Mission Features

NASA Technical Reports Server (NTRS)

Kloesel, Kurt; Starr, Ginn; Saltzman, John A.

2017-01-01

Design Reference Missions (DRM): Integrated ODM Air-Taxi Mission Features, Hybrid Electric Integrated System Testbed (HEIST) flight control. Structural Health, Energy Storage, Electric Components, Loss of Control, Degraded Systems, System Health, Real-Time IO Operator Geo-Fencing, Regional Noise Abatement and Trusted Autonomy Inter-operability.

Analyzing human errors in flight mission operations

NASA Technical Reports Server (NTRS)

Bruno, Kristin J.; Welz, Linda L.; Barnes, G. Michael; Sherif, Josef

1993-01-01

A long-term program is in progress at JPL to reduce cost and risk of flight mission operations through a defect prevention/error management program. The main thrust of this program is to create an environment in which the performance of the total system, both the human operator and the computer system, is optimized. To this end, 1580 Incident Surprise Anomaly reports (ISA's) from 1977-1991 were analyzed from the Voyager and Magellan projects. A Pareto analysis revealed that 38 percent of the errors were classified as human errors. A preliminary cluster analysis based on the Magellan human errors (204 ISA's) is presented here. The resulting clusters described the underlying relationships among the ISA's. Initial models of human error in flight mission operations are presented. Next, the Voyager ISA's will be scored and included in the analysis. Eventually, these relationships will be used to derive a theoretically motivated and empirically validated model of human error in flight mission operations. Ultimately, this analysis will be used to make continuous process improvements continuous process improvements to end-user applications and training requirements. This Total Quality Management approach will enable the management and prevention of errors in the future.

Beyond Mission Command: Maneuver Warfare for Cyber Command and Control

DTIC Science & Technology

2015-05-18

operation in an A2AD environment. 15. SUBJECT TERMS command and control; maneuver warfare; cyberspace; cyberspace operations; cyber warfare , mission...Some Principles of Cyber Warfare (NWC 2160) (U.S. Naval War College, Joint Military Operations Department, Newport, RI: U.S. Naval War College...research/ innovationleadership.pdf. Crowell, Richard M. Some Principles of Cyber Warfare (NWC 2160). U.S. Naval War College, Joint Military Operations

Mission Control Center (MCC) View - Apollo 13 Oxygen Cell Failure - MSC

NASA Image and Video Library

1970-04-15

S70-35014 (15 April 1970) --- A group of flight controllers gathers around the console of Glenn S. Lunney (seated, nearest camera), Shift 4 flight director, in the Mission Operations Control Room (MOCR) of Mission Control Center (MCC), located in Building 30 at the Manned Spacecraft Center (MSC). Their attention is drawn to a weather map of the proposed landing site in the South Pacific Ocean. Among those looking on is Dr. Christopher C. Kraft, deputy director, MSC, standing in black suit, on right. When this photograph was taken, the Apollo 13 lunar landing mission had been canceled, and the problem-plagued Apollo 13 crew members were in trans-Earth trajectory attempting to bring their crippled spacecraft back home.

The flyby of Rosetta at asteroid Šteins - mission and science operations

NASA Astrophysics Data System (ADS)

Accomazzo, Andrea; Wirth, Kristin R.; Lodiot, Sylvain; Küppers, Michael; Schwehm, Gerhard

2010-07-01

The international Rosetta mission, a cornerstone mission of the european space agency scientific Programme, was launched on 2nd March 2004 on its 10 years journey towards a rendezvous with comet Churyumov-Gerasimenko ( Gardini et al., 1999). During its interplanetary flight towards its target Rosetta crosses the asteroid belt twice with the opportunity to observe at close quarters two asteroids: (2867)-Šteins in 2008 and (21)-Lutetia in 2010. The spacecraft design was such that these opportunities could be fully exploited to deliver valuable data to the scientific community. The mission trajectory was controlled such that Rosetta would fly next to asteroid Šteins on the 5th of September 2008 with a relative speed of 8.6 km/s at a minimum distance of 800 km. Mission operations have been carefully planned to achieve the best possible flyby scenario and scientific outcome. The flyby scenario, the optical navigation campaign, and the planning of the scientific observations had to be adapted by the Mission and the Science Operations Centres to the demanding requirements expressed by the scientific community. The flyby was conducted as planned with a large number of successful observations.

Terra Mission Operations: Launch to the Present (and Beyond)

NASA Technical Reports Server (NTRS)

Kelly, Angelita; Moyer, Eric; Mantziaras, Dimitrios; Case, Warren

2014-01-01

The Terra satellite, flagship of NASA's long-term Earth Observing System (EOS) Program, continues to provide useful earth science observations well past its 5-year design lifetime. This paper describes the evolution of Terra operations, including challenges and successes and the steps taken to preserve science requirements and prolong spacecraft life. Working cooperatively with the Terra science and instrument teams, including NASA's international partners, the mission operations team has successfully kept the Terra operating continuously, resolving challenges and adjusting operations as needed. Terra retains all of its observing capabilities (except Short Wave Infrared) despite its age. The paper also describes concepts for future operations. This paper will review the Terra spacecraft mission successes and unique spacecraft component designs that provided significant benefits extending mission life and science. In addition, it discusses special activities as well as anomalies and corresponding recovery efforts. Lastly, it discusses future plans for continued operations.

Satellite Mission Operations Best Practices

NASA Technical Reports Server (NTRS)

Galal, Ken; Hogan, Roger P. (Technical Monitor)

2001-01-01

The effort of compiling a collection of Best Practices for use in Space Mission Operations was initiated within a subcommittee of the American Institute of Aeronautics and Astronautics (AIAA) Space Operations and Support Technical Committee (SOSTC). The idea was to eventually post a collection of Best Practices on a website so as to make them available to the general Space Operations community. The effort of searching for available Best Practices began in the fall of 1999. As the search progressed, it became apparent that there were not many Best Practices developed that were available to the general community. Therefore, the subcommittee decided to use the SOSTC Annual Workshop on Reducing Space Mission Costs as a forum for developing Best Practices for our purpose of sharing them with a larger audience. A dedicated track at the April 2000 workshop was designed to stimulate discussions on developing such Best Practices and forming working groups made up of experienced people from various organizations to perform the development. These groups were solicited to help outside the workshop to bring this effort to fruition. Since that time, biweekly teleconferences have been held to discuss the development of the Best Practices and their posting.

Middleware Evaluation and Benchmarking for Use in Mission Operations Centers

NASA Technical Reports Server (NTRS)

Antonucci, Rob; Waktola, Waka

2005-01-01

Middleware technologies have been promoted as timesaving, cost-cutting alternatives to the point-to-point communication used in traditional mission operations systems. However, missions have been slow to adopt the new technology. The lack of existing middleware-based missions has given rise to uncertainty about middleware's ability to perform in an operational setting. Most mission architects are also unfamiliar with the technology and do not know the benefits and detriments to architectural choices - or even what choices are available. We will present the findings of a study that evaluated several middleware options specifically for use in a mission operations system. We will address some common misconceptions regarding the applicability of middleware-based architectures, and we will identify the design decisions and tradeoffs that must be made when choosing a middleware solution. The Middleware Comparison and Benchmark Study was conducted at NASA Goddard Space Flight Center to comprehensively evaluate candidate middleware products, compare and contrast the performance of middleware solutions with the traditional point- to-point socket approach, and assess data delivery and reliability strategies. The study focused on requirements of the Global Precipitation Measurement (GPM) mission, validating the potential use of middleware in the GPM mission ground system. The study was jointly funded by GPM and the Goddard Mission Services Evolution Center (GMSEC), a virtual organization for providing mission enabling solutions and promoting the use of appropriate new technologies for mission support. The study was broken into two phases. To perform the generic middleware benchmarking and performance analysis, a network was created with data producers and consumers passing data between themselves. The benchmark monitored the delay, throughput, and reliability of the data as the characteristics were changed. Measurements were taken under a variety of topologies, data demands

Personnel discussing Gemini 11 space flight in Mission Control

NASA Image and Video Library

1966-09-12

S66-52157 (12 Sept. 1966) --- Discussing the Gemini-11 spaceflight in the Mission Control Center are: (left to right) Christopher C. Kraft Jr., (wearing glasses), Director of Flight Operations; Charles W. Mathews (holding phone), Manager, Gemini Program Office; Dr. Donald K. Slayton (center, checked coat), Director of Flight Crew Operations; astronaut William A. Anders, and astronaut John W. Young. Photo credit: NASA

MOS 2.0: Modeling the Next Revolutionary Mission Operations System

NASA Technical Reports Server (NTRS)

Delp, Christopher L.; Bindschadler, Duane; Wollaeger, Ryan; Carrion, Carlos; McCullar, Michelle; Jackson, Maddalena; Sarrel, Marc; Anderson, Louise; Lam, Doris

2011-01-01

Designed and implemented in the 1980's, the Advanced Multi-Mission Operations System (AMMOS) was a breakthrough for deep-space NASA missions, enabling significant reductions in the cost and risk of implementing ground systems. By designing a framework for use across multiple missions and adaptability to specific mission needs, AMMOS developers created a set of applications that have operated dozens of deep-space robotic missions over the past 30 years. We seek to leverage advances in technology and practice of architecting and systems engineering, using model-based approaches to update the AMMOS. We therefore revisit fundamental aspects of the AMMOS, resulting in a major update to the Mission Operations System (MOS): MOS 2.0. This update will ensure that the MOS can support an increasing range of mission types, (such as orbiters, landers, rovers, penetrators and balloons), and that the operations systems for deep-space robotic missions can reap the benefits of an iterative multi-mission framework.12 This paper reports on the first phase of this major update. Here we describe the methods and formal semantics used to address MOS 2.0 architecture and some early results. Early benefits of this approach include improved stakeholder input and buy-in, the ability to articulate and focus effort on key, system-wide principles, and efficiency gains obtained by use of well-architected design patterns and the use of models to improve the quality of documentation and decrease the effort required to produce and maintain it. We find that such methods facilitate reasoning, simulation, analysis on the system design in terms of design impacts, generation of products (e.g., project-review and software-delivery products), and use of formal process descriptions to enable goal-based operations. This initial phase yields a forward-looking and principled MOS 2.0 architectural vision, which considers both the mission-specific context and long-term system sustainability.

Interoperability for Space Mission Monitor and Control: Applying Technologies from Manufacturing Automation and Process Control Industries

NASA Technical Reports Server (NTRS)

Jones, Michael K.

1998-01-01

Various issues associated with interoperability for space mission monitor and control are presented in viewgraph form. Specific topics include: 1) Space Project Mission Operations Control Architecture (SuperMOCA) goals and methods for achieving them; 2) Specifics on the architecture: open standards ad layering, enhancing interoperability, and promoting commercialization; 3) An advertisement; 4) Status of the task - government/industry cooperation and architecture and technology demonstrations; and 5) Key features of messaging services and virtual devices.

Personnel in Mission Control examine replica of spider habitat from Skylab 3

NASA Technical Reports Server (NTRS)

1973-01-01

Flight Director Neil B. Hutchinson, left, and Astronaut Bruce McCandless II hold up a glass enclosure - home for the spider Arachne, which is the same species as the two spiders carried on the Skylab 3 mission. The real spider is the one barely visible at the upper right corner of the square; the larger one is a projected image on the rear-screen-projected map in the front of the Mission Operations Control Room (MOCR) of the Mission Control Center (MCC). McCandless served as backup pilot for the first manned Skylab mission and was a spacecraft-communicater (CAPCOM) for the second crew.

Efficient mission control for the 48-satellite Globalstar Constellation

NASA Technical Reports Server (NTRS)

Smith, Dan

1994-01-01

The Globalstar system is being developed by Globalstar, Limited Partnership and will utilize 48 satellites in low earth orbit (See Figure 1) to create a world-wide mobile communications system consistent with Vice President Gore's vision of a Global Information Infrastructure. As a large long term commercial system developed by a newly formed organization, Globalstar provides an excellent opportunity to explore innovative solutions for highly efficient satellite command and control. Design and operational concepts being developed are unencumbered by existing physical and organizational infrastructures. This program really is 'starting with a clean sheet of paper'. Globalstar operations challenges can appear enormous. Clearly, assigning even a single person around the clock to monitor and control each satellite is excessive for Globalstar (it would require a staff of 200! . Even with only a single contact per orbit per satellite, data acquisitions will start or stop every 45 seconds! Although essentially identical, over time the satellites will develop their own 'personalities'and will re quire different data calibrations and levels of support. This paper discusses the Globalstar system and challenges and presents engineering concepts, system design decisions, and operations concepts which address the combined needs and concerns of satellite, ground system, and operations teams. Lessons from past missions have been applied, organizational barriers broken, partnerships formed across the mission segments, and new operations concepts developed for satellite constellation management. Control center requirements were then developed from the operations concepts.

Study 2.6 operations analysis mission characterization

NASA Technical Reports Server (NTRS)

Wolfe, R. R.

1973-01-01

An analysis of the current operations concepts of NASA and DoD is presented to determine if alternatives exist which may improve the utilization of resources. The final product is intended to show how sensitive these ground rules and design approaches are relative to the total cost of doing business. The results are comparative in nature, and assess one concept against another as opposed to establishing an absolute cost value for program requirements. An assessment of the mission characteristics is explained to clarify the intent, scope, and direction of this effort to improve the understanding of what is to be accomplished. The characterization of missions is oriented toward grouping missions which may offer potential economic benefits by reducing overall program costs. Program costs include design, development, testing, and engineering, recurring unit costs for logistic vehicles, payload costs. and direct operating costs.

View of Mission Control Center during the Apollo 13 oxygen cell failure

NASA Image and Video Library

1970-04-14

S70-34904 (14 April 1970) --- Astronaut Alan B. Shepard Jr., prime crew commander of the Apollo 14 mission, monitors communications between the Apollo 13 spacecraft and Mission Control Center. He is seated at a console in the Mission Operations Control Room of the MCC, Manned Spacecraft Center. The main concern of the moment was action taken by the three Apollo 13 crewmen - astronauts James A. Lovell Jr., John L. Swigert Jr. and Fred W. Haise Jr. - to make corrections inside the spacecraft following discovery of an oxygen cell failure several hours earlier.

Balancing Science Objectives and Operational Constraints: A Mission Planner's Challenge

NASA Technical Reports Server (NTRS)

Weldy, Michelle

1996-01-01

The Air Force minute sensor technology integration (MSTI-3) satellite's primary mission is to characterize Earth's atmospheric background clutter. MSTI-3 will use three cameras for data collection, a mid-wave infrared imager, a short wave infrared imager, and a visible imaging spectrometer. Mission science objectives call for the collection of over 2 million images within the one year mission life. In addition, operational constraints limit camera usage to four operations of twenty minutes per day, with no more than 10,000 data and calibrating images collected per day. To balance the operational constraints and science objectives, the mission planning team has designed a planning process to e event schedules and sensor operation timelines. Each set of constraints, including spacecraft performance capabilities, the camera filters, the geographical regions, and the spacecraft-Sun-Earth geometries of interest, and remote tracking station deconflictions has been accounted for in this methodology. To aid in this process, the mission planning team is building a series of tools from commercial off-the-shelf software. These include the mission manifest which builds a daily schedule of events, and the MSTI Scene Simulator which helps build geometrically correct scans. These tools provide an efficient, responsive, and highly flexible architecture that maximizes data collection while minimizing mission planning time.

Space Mission Operations Ground Systems Integration Customer Service

NASA Technical Reports Server (NTRS)

Roth, Karl

2014-01-01

The facility, which is now the Huntsville Operations Support Center (HOSC) at Marshall Space Flight Center in Huntsville, AL, has provided continuous space mission and related services for the space industry since 1961, from Mercury Redstone through the International Space Station (ISS). Throughout the long history of the facility and mission support teams, the HOSC has developed a stellar customer support and service process. In this era, of cost cutting, and providing more capability and results with fewer resources, space missions are looking for the most efficient way to accomplish their objectives. One of the first services provided by the facility was fax transmission of documents to, then, Cape Canaveral in Florida. The headline in the Marshall Star, the newspaper for the newly formed Marshall Space Flight Center, read "Exact copies of Documents sent to Cape in 4 minutes." The customer was Dr. Wernher von Braun. Currently at the HOSC we are supporting, or have recently supported, missions ranging from simple ISS payloads requiring little more than "bentpipe" telemetry access, to a low cost free-flyer Fast, Affordable, Science and Technology Satellite (FASTSAT), to a full service ISS payload Alpha Magnetic Spectrometer 2 (AMS2) supporting 24/7 operations at three operations centers around the world with an investment of over 2 billion dollars. The HOSC has more need and desire than ever to provide fast and efficient customer service to support these missions. Here we will outline how our customer-centric service approach reduces the cost of providing services, makes it faster and easier than ever for new customers to get started with HOSC services, and show what the future holds for our space mission operations customers. We will discuss our philosophy concerning our responsibility and accessibility to a mission customer as well as how we deal with the following issues: initial contact with a customer, reducing customer cost, changing regulations and security

Data Management Coordinators Monitor STS-78 Mission at the Huntsville Operations Support Center

NASA Technical Reports Server (NTRS)

1996-01-01

Launched on June 20, 1996, the STS-78 mission's primary payload was the Life and Microgravity Spacelab (LMS), which was managed by the Marshall Space Flight Center (MSFC). During the 17 day space flight, the crew conducted a diverse slate of experiments divided into a mix of life science and microgravity investigations. In a manner very similar to future International Space Station operations, LMS researchers from the United States and their European counterparts shared resources such as crew time and equipment. Five space agencies (NASA/USA, European Space Agency/Europe (ESA), French Space Agency/France, Canadian Space Agency /Canada, and Italian Space Agency/Italy) along with research scientists from 10 countries worked together on the design, development and construction of the LMS. This photo represents Data Management Coordinators monitoring the progress of the mission at the Huntsville Operations Support Center (HOSC) Spacelab Payload Operations Control Center (SL POCC) at MSFC. Pictured are assistant mission scientist Dr. Dalle Kornfeld, Rick McConnel, and Ann Bathew.

Solar-A Prelaunch Mission Operation Report (MOR)

NASA Technical Reports Server (NTRS)

1991-01-01

The Solar-A mission is a Japanese-led program with the participation of the United States and the United Kingdom. The Japanese Institute of Space and Astronautical Science (ISAS) is providing the Solar-A spacecraft, two of the four science instruments, the launch vehicle and launch support, and the principal ground station with Operational Control Center. NASA is providing a science instrument, the Soft X-ray Telescope (SXT)and tracking support using the Deep Space Network (DSN) ground stations. The United Kingdom s Science and Engineering Research Council (SERC) provides the Bragg Crystal Spectrometer. The Solar-A mission will study solar flares using a cluster of instruments on a satellite in a 600 km altitude, 31 degree inclination circular orbit. The emphasis of the mission is on imaging and spectroscopy of hard and soft X-rays. The principal instruments are a pair of X-ray imaging instruments, one for the hard X-ray range and one for the soft X-ray range. The Hard X-Ray Telescope (HXT), provided by ISAS, operates in the energy range of 10-100 keV and uses an array of modulation collimators to record Fourier transform images of the non-thermal and hot plasmas that are formed during the early phases of a flare. These images are thought to be intimately associated with the sites of primary energy release. The Soft X-Ray Telescope (SXT), jointly provided by NASA and ISAS, operates in the wavelength range of 3-50 Angstroms and uses a grazing incidence mirror to form direct images of the lower temperature (but still very hot) plasmas that form as the solar atmosphere responds to the injection of energy. The SXT instrument is a joint development effort between the Lockheed Palo Alto Research Laboratory and the National Astronomical Observatory of Japan. The U.S. effort also involves Stanford University, the University of California at Berkeley and the University of Hawaii, who provide support in the areas of theory, data analysis and interpretation, and ground

Automation of Hubble Space Telescope Mission Operations

NASA Technical Reports Server (NTRS)

Burley, Richard; Goulet, Gregory; Slater, Mark; Huey, William; Bassford, Lynn; Dunham, Larry

2012-01-01

On June 13, 2011, after more than 21 years, 115 thousand orbits, and nearly 1 million exposures taken, the operation of the Hubble Space Telescope successfully transitioned from 24x7x365 staffing to 815 staffing. This required the automation of routine mission operations including telemetry and forward link acquisition, data dumping and solid-state recorder management, stored command loading, and health and safety monitoring of both the observatory and the HST Ground System. These changes were driven by budget reductions, and required ground system and onboard spacecraft enhancements across the entire operations spectrum, from planning and scheduling systems to payload flight software. Changes in personnel and staffing were required in order to adapt to the new roles and responsibilities required in the new automated operations era. This paper will provide a high level overview of the obstacles to automating nominal HST mission operations, both technical and cultural, and how those obstacles were overcome.

A Data-Based Console Logger for Mission Operations Team Coordination

NASA Technical Reports Server (NTRS)

Thronesbery, Carroll; Malin, Jane T.; Jenks, Kenneth; Overland, David; Oliver, Patrick; Zhang, Jiajie; Gong, Yang; Zhang, Tao

2005-01-01

Concepts and prototypes1,2 are discussed for a data-based console logger (D-Logger) to meet new challenges for coordination among flight controllers arising from new exploration mission concepts. The challenges include communication delays, increased crew autonomy, multiple concurrent missions, reduced-size flight support teams that include multidisciplinary flight controllers during quiescent periods, and migrating some flight support activities to flight controller offices. A spiral development approach has been adopted, making simple, but useful functions available early and adding more extensive support later. Evaluations have guided the development of the D-Logger from the beginning and continue to provide valuable user influence about upcoming requirements. D-Logger is part of a suite of tools designed to support future operations personnel and crew. While these tools can be used independently, when used together, they provide yet another level of support by interacting with one another. Recommendations are offered for the development of similar projects.

NASA OFFICIALS - MISSION OPERATIONS CONROL ROOM (MOCR) - MONITORING PROBLEMS - SKYLAB (SL)-3 COMMAND MODULE (CM) - JSC

NASA Image and Video Library

1973-08-02

S73-31875 (2 Aug. 1973) --- After learning of a problem in the Command/Service Module which was used to transport the Skylab 3 crew to the orbiting Skylab space station cluster, NASA officials held various meetings to discuss the problem. Here, four men monitor the current status of the problem in the Mission Operations Control Room (MOCR) of the Mission Control Center (MCC) at the Johnson Space Center (JSC). From the left are Gary E. Coen, Guidance and Navigation System flight controller; Howard W. Tindall Jr., Director of Flight Operations at JSC; Dr. Christopher C. Kraft Jr., JSC Director; and Sigurd A. Sjoberg, JSC Deputy Director. Photo credit: NASA

Mars geoscience/climatology orbiter low cost mission operations

NASA Technical Reports Server (NTRS)

Erickson, K. D.

1984-01-01

It will not be possible to support the multiple planetary missions of the magnitude and order of previous missions on the basis of foreseeable NASA funding. It is, therefore, necessary to seek innovative means for accomplishing the goals of planetary exploration with modestly allocated resources. In this connection, a Core Program set of planetary exploration missions has been recommended. Attention is given to a Mission Operations design overview which is based on the Mars Geoscience/Climatology Orbiter Phase-A study performed during spring of 1983.

View of Mission Control Center (MCC) - Lunar Surface - Apollo XI - Extravehicular Activity (EVA) - MSC

NASA Image and Video Library

1969-07-20

S69-39817 (20 July 1969) --- Interior view of the Mission Operations Control Room (MOCR) in the Mission Control Center (MCC), Building 30, during the Apollo 11 lunar extravehicular activity (EVA). The television monitor shows astronauts Neil A. Armstrong and Edwin E. Aldrin Jr. on the surface of the moon.

Mission operations and command assurance: Instilling quality into flight operations

NASA Technical Reports Server (NTRS)

Welz, Linda L.; Witkowski, Mona M.; Bruno, Kristin J.; Potts, Sherrill S.

1993-01-01

Mission Operations and Command Assurance (MO&CA) is a Total Quality Management (TQM) task on JPL projects to instill quality in flight mission operations. From a system engineering view, MO&CA facilitates communication and problem-solving among flight teams and provides continuous process improvement to reduce the probability of radiating incorrect commands to a spacecraft. The MO&CA task has evolved from participating as a member of the spacecraft team to an independent team reporting directly to flight project management and providing system level assurance. JPL flight projects have benefited significantly from MO&CA's effort to contain risk and prevent rather than rework errors. MO&CA's ability to provide direct transfer of knowledge allows new projects to benefit from previous and ongoing flight experience.

Orbital Express Mission Operations Planning and Resource Management using ASPEN

NASA Technical Reports Server (NTRS)

Chouinard, Caroline; Knight, Russell; Jones, Grailing; Tran, Daniel

2008-01-01

As satellite equipment and mission operations become more costly, the drive to keep working equipment running with less man-power rises.Demonstrating the feasibility of autonomous satellite servicing was the main goal behind the Orbital Express (OE) mission. Planning the satellite mission operations for OE required the ability to create a plan which could be executed autonomously over variable conditions. The Automated-Scheduling and Planning Environment (ASPEN)tool, developed at the Jet Propulsion Laboratory, was used to create the schedule of events in each daily plan for the two satellites of the OE mission. This paper presents an introduction to the ASPEN tool, the constraints of the OE domain, the variable conditions that were presented within the mission, and the solution to operations that ASPEN provided. ASPEN has been used in several other domains, including research rovers, Deep Space Network scheduling research, and in flight operations for the ASE project's EO1 satellite. Related work is discussed, as are the future of ASPEN and the future of autonomous satellite servicing.

Advances in Distributed Operations and Mission Activity Planning for Mars Surface Exploration

NASA Technical Reports Server (NTRS)

Fox, Jason M.; Norris, Jeffrey S.; Powell, Mark W.; Rabe, Kenneth J.; Shams, Khawaja

2006-01-01

A centralized mission activity planning system for any long-term mission, such as the Mars Exploration Rover Mission (MER), is completely infeasible due to budget and geographic constraints. A distributed operations system is key to addressing these constraints; therefore, future system and software engineers must focus on the problem of how to provide a secure, reliable, and distributed mission activity planning system. We will explain how Maestro, the next generation mission activity planning system, with its heavy emphasis on portability and distributed operations has been able to meet these design challenges. MER has been an excellent proving ground for Maestro's new approach to distributed operations. The backend that has been developed for Maestro could benefit many future missions by reducing the cost of centralized operations system architecture.

2016 Mission Operations Working Group: Earth Observing-1 (EO-1)

NASA Technical Reports Server (NTRS)

Frye, Stuart

2016-01-01

EO-1 Mission Status for the Constellation Mission Operations Working Group to discuss the EO-1 flight systems, mission enhancements, debris avoidance maneuver, orbital information, 5-year outlook, and new ground stations.

A New Architecture for Visualization: Open Mission Control Technologies

NASA Technical Reports Server (NTRS)

Trimble, Jay

2017-01-01

Open Mission Control Technologies (MCT) is a new architecture for visualisation of mission data. Driven by requirements for new mission capabilities, including distributed mission operations, access to data anywhere, customization by users, synthesis of multiple data sources, and flexibility for multi-mission adaptation, Open MCT provides users with an integrated customizable environment. Developed at NASAs Ames Research Center (ARC), in collaboration with NASAs Advanced Multimission Operations System (AMMOS) and NASAs Jet Propulsion Laboratory (JPL), Open MCT is getting its first mission use on the Jason 3 Mission, and is also available in the testbed for the Mars 2020 Rover and for development use for NASAs Resource Prospector Lunar Rover. The open source nature of the project provides for use outside of space missions, including open source contributions from a community of users. The defining features of Open MCT for mission users are data integration, end user composition and multiple views. Data integration provides access to mission data across domains in one place, making data such as activities, timelines, telemetry, imagery, event timers and procedures available in one place, without application switching. End user composition provides users with layouts, which act as a canvas to assemble visualisations. Multiple views provide the capability to view the same data in different ways, with live switching of data views in place. Open MCT is browser based, and works on the desktop as well as tablets and phones, providing access to data anywhere. An early use case for mobile data access took place on the Resource Prospector (RP) Mission Distributed Operations Test, in which rover engineers in the field were able to view telemetry on their phones. We envision this capability providing decision support to on console operators from off duty personnel. The plug-in architecture also allows for adaptation for different mission capabilities. Different data types and

Carrington-L5: The UK/US Space Weather Operational Mission.

NASA Astrophysics Data System (ADS)

Bisi, M. M.; Trichas, M.

2015-12-01

Airbus Defence and Space (UK) have carried out a study for an operational L5 space weather mission, in collaboration with RAL, the UK Met Office, UCL and Imperial College London. The study looked at the user requirements for an operational mission, a model instrument payload, and a mission/spacecraft concept. A particular focus is cost effectiveness and timelineness of the data, suitable for operational forecasting needs. The study focussed on a mission at L5 assuming that a US mission to L1 will already occur, on the basis that L5 offers the greatest benefit for SWE predictions. The baseline payload has been selected to address all MOSWOC/SWPC priorities using UK/US instruments, consisting of: a heliospheric imager, coronagraph, EUV imager, magnetograph, magnetometer, solar wind analyser and radiation monitor. The platform is based on extensive re-use from Airbus' past missions to minimize the cost and a Falcon-9 launcher has been selected on the same basis. A schedule analysis shows that the earliest launch could occur in 2020, assuming Phase A KO in 2015. The study team have selected the name "Carrington" for the mission, reflecting the UK's proud history in this domain.

Psychological Support Operations and the ISS One-Year Mission

NASA Technical Reports Server (NTRS)

Beven, G.; Vander Ark, S. T.; Holland, A. W.

2016-01-01

Since NASA began human presence on the International Space Station (ISS) in November 1998, crews have spent two to seven months onboard. In March 2015 NASA and Russia embarked on a new era of ISS utilization, with two of their crewmembers conducting a one-year mission onboard ISS. The mission has been useful for both research and mission operations to better understand the human, technological, mission management and staffing challenges that may be faced on missions beyond Low Earth Orbit. The work completed during the first 42 ISS missions provided the basis for the pre-flight, in-flight and post-flight work completed by NASA's Space Medicine Operations Division, while our Russian colleagues provided valuable insights from their long-duration mission experiences with missions lasting 10-14 months, which predated the ISS era. Space Medicine's Behavioral Health and Performance Group (BHP) provided pre-flight training, evaluation, and preparation as well as in-flight psychological support for the NASA crewmember. While the BHP team collaboratively planned for this mission with the help of all ISS international partners within the Human Behavior and Performance Working Group to leverage their collective expertise, the US and Russian BHP personnel were responsible for their respective crewmembers. The presentation will summarize the lessons and experience gained within the areas identified by this Working Group as being of primary importance for a one-year mission.

Payload Operations Control Center (POCC). [spacelab flight operations

NASA Technical Reports Server (NTRS)

Shipman, D. L.; Noneman, S. R.; Terry, E. S.

1981-01-01

The Spacelab payload operations control center (POCC) timeline analysis program which is used to provide POCC activity and resource information as a function of mission time is described. This program is fully automated and interactive, and is equipped with tutorial displays. The tutorial displays are sufficiently detailed for use by a program analyst having no computer experience. The POCC timeline analysis program is designed to operate on the VAX/VMS version V2.1 computer system.

The BRITE Constellation Nanosatellite Mission: Testing, Commissioning, and Operations

NASA Astrophysics Data System (ADS)

Pablo, H.; Whittaker, G. N.; Popowicz, A.; Mochnacki, S. M.; Kuschnig, R.; Grant, C. C.; Moffat, A. F. J.; Rucinski, S. M.; Matthews, J. M.; Schwarzenberg-Czerny, A.; Handler, G.; Weiss, W. W.; Baade, D.; Wade, G. A.; Zocłońska, E.; Ramiaramanantsoa, T.; Unterberger, M.; Zwintz, K.; Pigulski, A.; Rowe, J.; Koudelka, O.; Orleański, P.; Pamyatnykh, A.; Neiner, C.; Wawrzaszek, R.; Marciniszyn, G.; Romano, P.; Woźniak, G.; Zawistowski, T.; Zee, R. E.

2016-12-01

BRIght Target Explorer (BRITE) Constellation, the first nanosatellite mission applied to astrophysical research, is a collaboration among Austria, Canada and Poland. The fleet of satellites (6 launched; 5 functioning) performs precise optical photometry of the brightest stars in the night sky. A pioneering mission like BRITE—with optics and instruments restricted to small volume, mass and power in several nanosatellites, whose measurements must be coordinated in orbit—poses many unique challenges. We discuss the technical issues, including problems encountered during on-orbit commissioning (especially higher-than-expected sensitivity of the CCDs to particle radiation). We describe in detail how the BRITE team has mitigated these problems, and provide a complete overview of mission operations. This paper serves as a template for how to effectively plan, build and operate future low-cost niche-driven space astronomy missions. Based on data collected by the BRITE Constellation satellite mission, designed, built, launched, operated and supported by the Austrian Research Promotion Agency (FFG), the University of Vienna, the Technical University of Graz, the Canadian Space Agency (CSA), the University of Toronto Institute for Aerospace Studies (UTIAS), the Foundation for Polish Science & Technology (FNiTP MNiSW), and National Science Centre (NCN).

Cassini Attitude Control Flight Software: from Development to In-Flight Operation

NASA Technical Reports Server (NTRS)

Brown, Jay

2008-01-01

The Cassini Attitude and Articulation Control Subsystem (AACS) Flight Software (FSW) has achieved its intended design goals by successfully guiding and controlling the Cassini-Huygens planetary mission to Saturn and its moons. This paper describes an overview of AACS FSW details from early design, development, implementation, and test to its fruition of operating and maintaining spacecraft control over an eleven year prime mission. Starting from phases of FSW development, topics expand to FSW development methodology, achievements utilizing in-flight autonomy, and summarize lessons learned during flight operations which can be useful to FSW in current and future spacecraft missions.

Interactive experimenters' planning procedures and mission control

NASA Technical Reports Server (NTRS)

Desjardins, R. L.

1973-01-01

The computerized mission control and planning system routinely generates a 24-hour schedule in one hour of operator time by including time dimensions into experimental planning procedures. Planning is validated interactively as it is being generated segment by segment in the frame of specific event times. The planner simply points a light pen at the time mark of interest on the time line for entering specific event times into the schedule.

Orbital Express mission operations planning and resource management using ASPEN

NASA Astrophysics Data System (ADS)

Chouinard, Caroline; Knight, Russell; Jones, Grailing; Tran, Daniel

2008-04-01

As satellite equipment and mission operations become more costly, the drive to keep working equipment running with less labor-power rises. Demonstrating the feasibility of autonomous satellite servicing was the main goal behind the Orbital Express (OE) mission. Like a tow-truck delivering gas to a car on the road, the "servicing" satellite of OE had to find the "client" from several kilometers away, connect directly to the client, and transfer fluid (or a battery) autonomously, while on earth-orbit. The mission met 100% of its success criteria, and proved that autonomous satellite servicing is now a reality for space operations. Planning the satellite mission operations for OE required the ability to create a plan which could be executed autonomously over variable conditions. As the constraints for execution could change weekly, daily, and even hourly, the tools used create the mission execution plans needed to be flexible and adaptable to many different kinds of changes. At the same time, the hard constraints of the plans needed to be maintained and satisfied. The Automated Scheduling and Planning Environment (ASPEN) tool, developed at the Jet Propulsion Laboratory, was used to create the schedule of events in each daily plan for the two satellites of the OE mission. This paper presents an introduction to the ASPEN tool, an overview of the constraints of the OE domain, the variable conditions that were presented within the mission, and the solution to operations that ASPEN provided. ASPEN has been used in several other domains, including research rovers, Deep Space Network scheduling research, and in flight operations for the NASA's Earth Observing One mission's EO1 satellite. Related work is discussed, as are the future of ASPEN and the future of autonomous satellite servicing.

Activity in the Mission Control Center during Apollo 14

NASA Image and Video Library

1971-02-04

S71-17610 (4 Feb. 1971) --- Partial view of activity in the Mission Operations Control Room in the Mission Control Center at the time the Apollo 14 S-IVB stage impacted on the lunar surface. The flight director's console is in the foreground. Eugene F. Kranz, chief of the MSC Flight Control Division, is in the right foreground. Seated at the console is Glynn S. Lunney, head of the Flight Director Office, Flight Control Division. Facing the camera is Gerald D. Griffin, flight director of the Third (Gold) Team. A seismic reading from the impact can be seen in the center background. The S-IVB impacted on the lunar surface at 1:40:54 a.m. (CST), Feb. 4, 1971, about 90 nautical miles south-southwest of the Apollo 12 passive seismometer. The energy release was comparable to 11 tons of TNT.

Mission Control Center (MCC) View - Apollo 13 Oxygen Cell Failure - MSC

NASA Image and Video Library

1970-04-15

S70-35012 (15 April 1970) --- Two phases of busy activity during critical moments of the Apollo 13 mission are reflected in this view in the Mission Control Center, Building 30, Manned Spacecraft Center. In the foreground, Henry Simmons (left) of Newsweek magazine and John E. Riley, public information specialist, Public Affairs Office, MSC, man their positions in the Press Room. At extreme left of photo, Gerald D. Griffin, Shift 2 flight director, talks on telephone in Mission Operations Control Room. When this photograph was taken, the Apollo 13 lunar landing had been canceled, and the problem-plagued Apollo 13 crewmen were in trans-Earth trajectory attempting to bring their crippled spacecraft back home.

A new environment for multiple spacecraft power subsystem mission operations

NASA Technical Reports Server (NTRS)

Bahrami, K. A.

1990-01-01

The engineering analysis subsystem environment (EASE) is being developed to enable fewer controllers to monitor and control power and other spacecraft engineering subsystems. The EASE prototype has been developed to support simultaneous real-time monitoring of several spacecraft engineering subsystems. It is being designed to assist with offline analysis of telemetry data to determine trends, and to help formulate uplink commands to the spacecraft. An early version of the EASE prototype has been installed in the JPL Space Flight Operations Facility for online testing. The EASE prototype is installed in the Galileo Mission Support Area. The underlying concept, development, and testing of the EASE prototype and how it will aid in the ground operations of spacecraft power subsystems are discussed.

Real-time science operations to support a lunar polar volatiles rover mission

NASA Astrophysics Data System (ADS)

Heldmann, Jennifer L.; Colaprete, Anthony; Elphic, Richard C.; Mattes, Greg; Ennico, Kimberly; Fritzler, Erin; Marinova, Margarita M.; McMurray, Robert; Morse, Stephanie; Roush, Ted L.; Stoker, Carol R.

2015-05-01

Future human exploration of the Moon will likely rely on in situ resource utilization (ISRU) to enable long duration lunar missions. Prior to utilizing ISRU on the Moon, the natural resources (in this case lunar volatiles) must be identified and characterized, and ISRU demonstrated on the lunar surface. To enable future uses of ISRU, NASA and the CSA are developing a lunar rover payload that can (1) locate near subsurface volatiles, (2) excavate and analyze samples of the volatile-bearing regolith, and (3) demonstrate the form, extractability and usefulness of the materials. Such investigations are important both for ISRU purposes and for understanding the scientific nature of these intriguing lunar volatile deposits. Temperature models and orbital data suggest near surface volatile concentrations may exist at briefly lit lunar polar locations outside persistently shadowed regions. A lunar rover could be remotely operated at some of these locations for the ∼ 2-14 days of expected sunlight at relatively low cost. Due to the limited operational time available, both science and rover operations decisions must be made in real time, requiring immediate situational awareness, data analysis, and decision support tools. Given these constraints, such a mission requires a new concept of operations. In this paper we outline the results and lessons learned from an analog field campaign in July 2012 which tested operations for a lunar polar rover concept. A rover was operated in the analog environment of Hawaii by an off-site Flight Control Center, a rover navigation center in Canada, a Science Backroom at NASA Ames Research Center in California, and support teams at NASA Johnson Space Center in Texas and NASA Kennedy Space Center in Florida. We find that this type of mission requires highly efficient, real time, remotely operated rover operations to enable low cost, scientifically relevant exploration of the distribution and nature of lunar polar volatiles. The field

Real-Time Science Operations to Support a Lunar Polar Volatiles Rover Mission

NASA Technical Reports Server (NTRS)

Heldmann, Jennifer L.; Colaprete, Anthony; Elphic, Richard C.; Mattes, Greg; Ennico, Kimberly; Fritzler, Erin; Marinova, Margarita M.; McMurray, Robert; Morse, Stephanie; Roush, Ted L.;

Mission management - Lessons learned from early Spacelab missions

NASA Technical Reports Server (NTRS)

Craft, H. G., Jr.

1980-01-01

The concept and the responsibilities of a mission manager approach are reviewed, and some of the associated problems in implementing Spacelab mission are discussed. Consideration is given to program control, science management, integrated payload mission planning, and integration requirements. Payload specialist training, payload and launch site integration, payload flight/mission operations, and postmission activities are outlined.

Operational Experience with Long Duration Wildfire Mapping: UAS Missions Over the Western United States

NASA Technical Reports Server (NTRS)

Hall, Philip; Cobleigh, Brent; Buoni, Greg; Howell, Kathleen

2008-01-01

The National Aeronautics and Space Administration, United States Forest Service, and National Interagency Fire Center have developed a partnership to develop and demonstrate technology to improve airborne wildfire imaging and data dissemination. In the summer of 2007, a multi-spectral infrared scanner was integrated into NASA's Ikhana Unmanned Aircraft System (UAS) (a General Atomics Predator-B) and launched on four long duration wildfire mapping demonstration missions covering eight western states. Extensive safety analysis, contingency planning, and mission coordination were key to securing an FAA certificate of authorization (COA) to operate in the national airspace. Infrared images were autonomously geo-rectified, transmitted to the ground station by satellite communications, and networked to fire incident commanders within 15 minutes of acquisition. Close coordination with air traffic control ensured a safe operation, and allowed real-time redirection around inclement weather and other minor changes to the flight plan. All objectives of the mission demonstrations were achieved. In late October, wind-driven wildfires erupted in five southern California counties. State and national emergency operations agencies requested Ikhana to help assess and manage the wildfires. Four additional missions were launched over a 5-day period, with near realtime images delivered to multiple emergency operations centers and fire incident commands managing 10 fires.

Wide angle view of Mission Control Center during Apollo 14 transmission

NASA Image and Video Library

1971-01-31

S71-17122 (31 Jan. 1971) --- A wide angle overall view of the Mission Operations Control Room (MOCR) in the Mission Control Center at the Manned spacecraft Center. This view was photographed during the first color television transmission from the Apollo 14 Command Module. Projected on the large screen at the right front of the MOCR is a view of the Apollo 14 Lunar Module, still attached to the Saturn IVB stage. The Command and Service Modules were approaching the LM/S-IVB during transposition and docking maneuvers.

Development and Execution of End-of-Mission Operations Case Study of the UARS and ERBS End-of-Mission Plans

NASA Technical Reports Server (NTRS)

Hughes, John; Marius, Julio L.; Montoro, Manuel; Patel, Mehul; Bludworth, David

2006-01-01

This Paper is a case study of the development and execution of the End-of-Mission plans for the Earth Radiation Budget Satellite (ERBS) and the Upper Atmosphere Research Satellite (UARS). The goals of the End-of-Mission Plans are to minimize the time the spacecraft remains on orbit and to minimize the risk of creating orbital debris. Both of these Missions predate the NASA Management Instructions (NMI) that directs missions to provide for safe mission termination. Each spacecrafts had their own unique challenges, which required assessing End-of-Mission requirements versus spacecraft limitations. Ultimately the End-of- Mission operations were about risk mitigation. This paper will describe the operational challenges and the lessons learned executing these End-of-Mission Plans

A distributed computing approach to mission operations support. [for spacecraft

NASA Technical Reports Server (NTRS)

Larsen, R. L.

1975-01-01

Computing mission operation support includes orbit determination, attitude processing, maneuver computation, resource scheduling, etc. The large-scale third-generation distributed computer network discussed is capable of fulfilling these dynamic requirements. It is shown that distribution of resources and control leads to increased reliability, and exhibits potential for incremental growth. Through functional specialization, a distributed system may be tuned to very specific operational requirements. Fundamental to the approach is the notion of process-to-process communication, which is effected through a high-bandwidth communications network. Both resource-sharing and load-sharing may be realized in the system.

Agent-Supported Mission Operations Teamwork

NASA Technical Reports Server (NTRS)

Malin, Jane T.

2003-01-01

This slide presentation reviews the development of software agents to support of mission operations teamwork. The goals of the work was to make automation by agents easy to use, supervise and direct, manage information and communication to decrease distraction, interruptions, workload and errors, reduce mission impact of off-nominal situations and increase morale and decrease turnover. The accomplishments or the project are: 1. Collaborative agents - mixed initiative and creation of instructions for mediating agent 2. Methods for prototyping, evaluating and evolving socio-technical systems 3. Technology infusion: teamwork tools in mISSIons 4. Demonstrations in simulation testbed An example of the use of agent is given, the use of an agent to monitor a N2 tank leak. An incomplete instruction to the agent is handled with mediating assistants, or Intelligent Briefing and Response Assistant (IBRA). The IBRA Engine also watches data stream for triggers and executes Act-Whenever actions. There is also a Briefing and Response Instruction (BRI) which is easy for a discipline specialist to create through a BRI editor.

The Operations Security Concept for Future ESA Earth Observation Missions

NASA Astrophysics Data System (ADS)

Fischer, D.; Bargellini, P.; Merri, M.

2008-08-01

Next-generation European earth observation missions will play a critical role in public safety and security infrastructures. This makes it necessary for ESA to protect the communication infrastructure of these missions in order to guarantee their service availability. In this paper, we discuss the development process for a generic earth observation security concept. This concept has been developed as part of a GMES Flight Operation Segment security study with the objective to analyse and select a number of high level security requirements for the missions. Further, we studied the impact of an implementation for these requirements on the operational infrastructure of current earth observation missions.

View of Mission Control on first day of ASTP docking in Earth orbit

NASA Technical Reports Server (NTRS)

1975-01-01

An overall view of the Mission Operations Control Room in the Mission Control Center, bldg 30, JSC, on the first day of the Apollo Soyuz Test Project (ASTP) docking in Earth orbit. This photograph was taken shortly before the American ASTP launch from the Kennedy Space Center. The television monitor in the center background shows the ASTP Apollo-Saturn 1B space vehicle on Pad B at KSC's Launch Complex 39.

A Mission Concept for FUSE Operations in GFY09 and Beyond

NASA Astrophysics Data System (ADS)

Moos, H. W.; Sonneborn, G.; Blair, W. P.; Kruk, J. W.; FUSE Science Operations Team

2007-05-01

We are developing a new mission concept for the Far Ultraviolet Spectroscopic Explorer (FUSE) that would significantly reduce operating costs but would continue the availability of this unique resource into GFY09 and beyond. Launched in 1999, the FUSE satellite obtains R=20,000 spectra of astronomical sources in the far-ultraviolet (912 - 1187 A) wavelength range. The FUSE scientific instrument remains healthy and the satellite has made a remarkable recovery from attitude control problems in late 2004. We expect FUSE to remain a viable scientific tool for the foreseeable future. Current plans for FUSE operations extend through GFY2008 (Sept. 30, 2008). Key elements of this new mission concept include a) continued automation and streamlining of operations to reduce costs, and b) an emphasis on a small number of unique, high priority science programs, particularly those requiring integration times on key targets that are significantly longer than has been possible in the mission design to date. A prime example of the latter would be 100 - 400 ks integrations on selected quasars to provide much improved diagnostic power to study the intergalactic medium. Synergy with the scientific objectives of the Cosmic Origins Spectrograph (COS) program on HST, and the complementary nature of FUSE and COS data on the same sightlines, is but one major motivation for this operations model. In addition to programs emphasizing very long integrations, opportunities for other high priority targets would exist. We will describe some of the ongoing development toward such an operations model as well as the scientific drivers discussed to date. Community input on these and other science drivers for extended FUSE operations is encouraged. FUSE is operated for NASA by Johns Hopkins University under NASA contract NAS5-32985.

Intelligent resources for satellite ground control operations

NASA Technical Reports Server (NTRS)

Jones, Patricia M.

1994-01-01

This paper describes a cooperative approach to the design of intelligent automation and describes the Mission Operations Cooperative Assistant for NASA Goddard flight operations. The cooperative problem solving approach is being explored currently in the context of providing support for human operator teams and also in the definition of future advanced automation in ground control systems.

Guidance, Navigation, and Control Technology Assessment for Future Planetary Science Missions

NASA Technical Reports Server (NTRS)

Beauchamp, Pat; Cutts, James; Quadrelli, Marco B.; Wood, Lincoln J.; Riedel, Joseph E.; McHenry, Mike; Aung, MiMi; Cangahuala, Laureano A.; Volpe, Rich

2013-01-01

Future planetary explorations envisioned by the National Research Council's (NRC's) report titled Vision and Voyages for Planetary Science in the Decade 2013-2022, developed for NASA Science Mission Directorate (SMD) Planetary Science Division (PSD), seek to reach targets of broad scientific interest across the solar system. This goal requires new capabilities such as innovative interplanetary trajectories, precision landing, operation in close proximity to targets, precision pointing, multiple collaborating spacecraft, multiple target tours, and advanced robotic surface exploration. Advancements in Guidance, Navigation, and Control (GN&C) and Mission Design in the areas of software, algorithm development and sensors will be necessary to accomplish these future missions. This paper summarizes the key GN&C and mission design capabilities and technologies needed for future missions pursuing SMD PSD's scientific goals.

Payload operations management of a planned European SL-Mission employing establishments of ESA and national agencies

NASA Technical Reports Server (NTRS)

Joensson, Rolf; Mueller, Karl L.

1994-01-01

Spacelab (SL)-missions with Payload Operations (P/L OPS) from Europe involve numerous space agencies, various ground infrastructure systems and national user organizations. An effective management structure must bring together different entities, facilities and people, but at the same time keep interfaces, costs and schedule under strict control. This paper outlines the management concept for P/L OPS of a planned European SL-mission. The proposal draws on the relevant experience in Europe, which was acquired via the ESA/NASA mission SL-1, by the execution of two German SL-missions and by the involvement in, or the support of, several NASA-missions.

A mission operations architecture for the 21st century

NASA Technical Reports Server (NTRS)

Tai, W.; Sweetnam, D.

1996-01-01

An operations architecture is proposed for low cost missions beyond the year 2000. The architecture consists of three elements: a service based architecture; a demand access automata; and distributed science hubs. The service based architecture is based on a set of standard multimission services that are defined, packaged and formalized by the deep space network and the advanced multi-mission operations system. The demand access automata is a suite of technologies which reduces the need to be in contact with the spacecraft, and thus reduces operating costs. The beacon signaling, the virtual emergency room, and the high efficiency tracking automata technologies are described. The distributed science hubs provide information system capabilities to the small science oriented flight teams: individual access to all traditional mission functions and services; multimedia intra-team communications, and automated direct transparent communications between the scientists and the instrument.

The Spacecraft Emergency Response System (SERS) for Autonomous Mission Operations

NASA Technical Reports Server (NTRS)

Breed, Julia; Chu, Kai-Dee; Baker, Paul; Starr, Cynthia; Fox, Jeffrey; Baitinger, Mick

1998-01-01

Today, most mission operations are geared toward lowering cost through unmanned operations. 7-day/24-hour operations are reduced to either 5-day/8-hour operations or become totally autonomous, especially for deep-space missions. Proper and effective notification during a spacecraft emergency could mean success or failure for an entire mission. The Spacecraft Emergency Response System (SERS) is a tool designed for autonomous mission operations. The SERS automatically contacts on-call personnel as needed when crises occur, either on-board the spacecraft or within the automated ground systems. Plus, the SERS provides a group-ware solution to facilitate the work of the person(s) contacted. The SERS is independent of the spacecraft's automated ground system. It receives and catalogues reports for various ground system components in near real-time. Then, based on easily configurable parameters, the SERS determines whom, if anyone, should be alerted. Alerts may be issued via Sky-Tel 2-way pager, Telehony, or e-mail. The alerted personnel can then review and respond to the spacecraft anomalies through the Netscape Internet Web Browser, or directly review and respond from the Sky-Tel 2-way pager.

Deep Space Habitat Concept of Operations for Transit Mission Phases

NASA Technical Reports Server (NTRS)

Hoffman, Stephen J.

2011-01-01

The National Aeronautics and Space Administration (NASA) has begun evaluating various mission and system components of possible implementations of what the U.S. Human Spaceflight Plans Committee (also known as the Augustine Committee) has named the flexible path (Anon., 2009). As human spaceflight missions expand further into deep space, the duration of these missions increases to the point where a dedicated crew habitat element appears necessary. There are several destinations included in this flexible path a near Earth asteroid (NEA) mission, a Phobos/Deimos (Ph/D) mission, and a Mars surface exploration mission that all include at least a portion of the total mission in which the crew spends significant periods of time (measured in months) in the deep space environment and are thus candidates for a dedicated habitat element. As one facet of a number of studies being conducted by the Human Spaceflight Architecture Team (HAT) a workshop was conducted to consider how best to define and quantify habitable volume for these future deep space missions. One conclusion reached during this workshop was the need for a description of the scope and scale of these missions and the intended uses of a habitat element. A group was set up to prepare a concept of operations document to address this need. This document describes a concept of operations for a habitat element used for these deep space missions. Although it may eventually be determined that there is significant overlap with this concept of operations and that of a habitat destined for use on planetary surfaces, such as the Moon and Mars, no such presumption is made in this document.

Mission operations of the handicapped FORMOSAT-2

NASA Astrophysics Data System (ADS)

Lin, Shin-Fa; Chern, Jeng-Shing; Wu, An-Ming

2014-10-01

Since its launch on 20 May 2004, FORMOSAT-2 (FS2, Formosa satellite ♯2) has been operated on orbit for more than 9 years. It carries two payloads: the remote sensing instrument (RSI) for Earth observations and the imager of sprites and upper atmospheric lightning instrument (ISUAL) for the purpose of scientific observations. The RSI is operating at daytime while ISUAL is active at night-time. To meet both mission objectives simultaneously, the satellite operations planning has been more complicated. In order to maximize the usage of the on-board resources, the satellite attitude maneuver activities and power charge/discharge cycles have been scheduled cautiously in every detail. Under such fully engaged operations scenario and with a design life of 5 years, it is inevitable that the satellite encountered many anomalies, either permanent or temporary. In particular, one attitude gyro (totally four) and one reaction wheel (totally four) have been failed. This paper presents the major anomalies and resolutions in the past years. Many iterations and trade-offs have been made to minimize the effect on mission operations of the handicapped FORMOSAT-2. It still can provide about 80% of the designed functions and capabilities.

The Hubble Space Telescope servicing missions: Past, present, and future operational challenges

NASA Technical Reports Server (NTRS)

Ochs, William R.; Barbehenn, George M.; Crabb, William G.

1996-01-01

The Hubble Space Telescope was designed to be serviced by the Space Shuttle to upgrade systems, replace failed components and boost the telescope into higher orbits. There exists many operational challenges that must be addressed in preparation for the execution of a servicing mission, including technical and managerial issues. The operational challenges faced by the Hubble operations and ground system project for the support of the first servicing mission and future servicing missions, are considered. The emphasis is on those areas that helped ensure the success of the mission, including training, testing and contingency planning.

SimSup's Loop: A Control Theory Approach to Spacecraft Operator Training

NASA Technical Reports Server (NTRS)

Owens, Brandon Dewain; Crocker, Alan R.

2015-01-01

Immersive simulation is a staple of training for many complex system operators, including astronauts and ground operators of spacecraft. However, while much has been written about simulators, simulation facilities, and operator certification programs, the topic of how one develops simulation scenarios to train a spacecraft operator is relatively understated in the literature. In this paper, an approach is presented for using control theory as the basis for developing the immersive simulation scenarios for a spacecraft operator training program. The operator is effectively modeled as a high level controller of lower level hardware and software control loops that affect a select set of system state variables. Simulation scenarios are derived from a STAMP-based hazard analysis of the operator's high and low level control loops. The immersive simulation aspect of the overall training program is characterized by selecting a set of scenarios that expose the operator to the various inadequate control actions that stem from control flaws and inadequate control executions in the different sections of the typical control loop. Results from the application of this approach to the Lunar Atmosphere and Dust Environment Explorer (LADEE) mission are provided through an analysis of the simulation scenarios used for operator training and the actual anomalies that occurred during the mission. The simulation scenarios and inflight anomalies are mapped to specific control flaws and inadequate control executions in the different sections of the typical control loop to illustrate the characteristics of anomalies arising from the different sections of the typical control loop (and why it is important for operators to have exposure to these characteristics). Additionally, similarities between the simulation scenarios and inflight anomalies are highlighted to make the case that the simulation scenarios prepared the operators for the mission.

Dust Storm Impacts on Human Mars Mission Equipment and Operations

NASA Technical Reports Server (NTRS)

Rucker, M. A.

2017-01-01

Although it is tempting to use dust impacts on Apollo lunar exploration mission equipment and operations as an analog for human Mars exploration, there are a number of important differences to consider. Apollo missions were about a week long; a human Mars mission will start at least two years before crew depart from Earth, when cargo is pre-deployed, and crewed mission duration may be over 800 days. Each Apollo mission landed at a different site; although no decisions have been made, NASA is investigating multiple human missions to a single Mars landing site, building up capability over time and lowering costs by re-using surface infrastructure. Apollo missions used two, single-use spacecraft; a human Mars mission may require as many as six craft for different phases of the mission, most of which would be re-used by subsequent crews. Apollo crews never ventured more than a few kilometers from their lander; Mars crews may take "camping trips" a hundred kilo-meters or more from their landing site, utilizing pressurized rovers to explore far from their base. Apollo mission designers weren't constrained by human for-ward contamination of the Moon; if we plan to search for evidence of life on Mars we'll have to be more careful. These differences all impact how we will mitigate and manage dust on our human Mars mission equipment and operations.

Views of the mission control center during STS-9

NASA Technical Reports Server (NTRS)

1983-01-01

Busy moment in the customer management room (CMR) of JSC's mission control center during Spacelab 1 day 2. Three personnel from the European Space Agency (ESA) huddle around a console along with Ralph Hoodless (seated at left), of the George C. Marshall Space Flight Center. Others pictured are Lars Tedeman and Hildegard Binck (standing); and Frank Longhurst (seated right). Tedeman is with ESA's quality control division and Longhurst is Spacelab operations manager.

Implementing Distributed Operations: A Comparison of Two Deep Space Missions

NASA Technical Reports Server (NTRS)

Mishkin, Andrew; Larsen, Barbara

2006-01-01

Two very different deep space exploration missions--Mars Exploration Rover and Cassini--have made use of distributed operations for their science teams. In the case of MER, the distributed operations capability was implemented only after the prime mission was completed, as the rovers continued to operate well in excess of their expected mission lifetimes; Cassini, designed for a mission of more than ten years, had planned for distributed operations from its inception. The rapid command turnaround timeline of MER, as well as many of the operations features implemented to support it, have proven to be conducive to distributed operations. These features include: a single science team leader during the tactical operations timeline, highly integrated science and engineering teams, processes and file structures designed to permit multiple team members to work in parallel to deliver sequencing products, web-based spacecraft status and planning reports for team-wide access, and near-elimination of paper products from the operations process. Additionally, MER has benefited from the initial co-location of its entire operations team, and from having a single Principal Investigator, while Cassini operations have had to reconcile multiple science teams distributed from before launch. Cassini has faced greater challenges in implementing effective distributed operations. Because extensive early planning is required to capture science opportunities on its tour and because sequence development takes significantly longer than sequence execution, multiple teams are contributing to multiple sequences concurrently. The complexity of integrating inputs from multiple teams is exacerbated by spacecraft operability issues and resource contention among the teams, each of which has their own Principal Investigator. Finally, much of the technology that MER has exploited to facilitate distributed operations was not available when the Cassini ground system was designed, although later adoption

Radio astronomy Explorer-B in-flight mission control system development effort

NASA Technical Reports Server (NTRS)

Lutsky, D. A.; Bjorkman, W. S.; Uphoff, C.

1973-01-01

A description is given of the development for the Mission Analysis Evaluation and Space Trajectory Operations (MAESTRO) program to be used for the in-flight decision making process during the translunar and lunar orbit adjustment phases of the flight of the Radio Astronomy Explorer-B. THe program serves two functions: performance and evaluation of preflight mission analysis, and in-flight support for the midcourse and lunar insertion command decisions that must be made by the flight director. The topics discussed include: analysis of program and midcourse guidance capabilities; methods for on-line control; printed displays of the MAESTRO program; and in-flight operational logistics and testing.

View of Mission Control Center during the Apollo 13 oxygen cell failure

NASA Technical Reports Server (NTRS)

1970-01-01

Mrs. Mary Haise receives an explanation of the revised flight plan of the Apollo 13 mission from Astronaut Gerald P. Carr in the Viewing Room of Mission Control Center, bldg 30, Manned Spacecraft Center (MSC). Her husband, Astronaut Fred W. Haise Jr., was joining the fellow crew members in making corrections in their spacecraft following discovery of an oxygen cell failure several hours earlier (34900); Dr. Charles A. Berry, Director of Medical Research and Operations Directorate at MSC, converses with Mrs. Marilyn Lovell in the Viewing Room of Mission Control Center. Mrs. Lovell's husband, Astronaut James A. Lovell Jr., was busily making corrections inside the spacecraft following discovery of an oxygen cell failure several hours earlier (34901).

hwhap_Ep11_Mission Control

NASA Image and Video Library

2017-09-22

and fifty thousand views. Famous. >> That's a lot. I try not to think about that, really. >> [laughs] But it was so fun. It was like, I mean we title it Everything. I mean it wasn't really everything, but it was, it was like fast paced information. You got to know more about Mission Control than I guess people would normally kind of find out. And we got to be on the floor. It's kind of different though, that they didn't have the titles up there, you know. We we're mission that Flight Director, GC. Those kinds of things. >> Yeah, remind me again. We'll make improvements for next time, right. >> For the next one. Okay, so welcome to the podcast. For this one we don't have to be as wrapped in fire, so that's good. >> Okay. >> We can kind of take our time. But today we are here to talk about Mission Control, and I feel like you're the perfect person to do this, because you are a Flight Director. You're in that, you're in Mission Control making all the decisions. And I guess that's sort of what a Flight Controller does. Or, sorry. A Flight Director does, right. You're kind of the, the main person in that room. >> That's right, yes. >> Okay. >> The Flight Director is the lead of the flight control team. So, they're kind of the final decision maker and real-time spacecraft operations. >> Cool. And you do that how often, in general? >> I spend a lot of time on console. I'm one of the newer Flight Directors. >> Okay. >> So probably spend a little more time on console than some of the more experienced guys that have a lot more assignments. >> I see. >> But I would say over the past year I probably pulled about a hundred shifts. >> Whoa. >> So, one shift is about eight to nine hours long. Eight hours with a one-hour hand over period. And, we do that every few weeks. We're on console for a string of anywhere from one to seven shifts I would say. >> Okay. And there three shifts in a day, right? It's just how, because you have that hand over period so nine, nine, nine. You guys can

Integrated Attitude Control Strategy for the Asteroid Redirect Mission

NASA Technical Reports Server (NTRS)

Lopez, Pedro, Jr.; Price, Hoppy; San Martin, Miguel

2014-01-01

A deep-space mission has been proposed to redirect an asteroid to a distant retrograde orbit around the moon using a robotic vehicle, the Asteroid Redirect Vehicle (ARV). In this orbit, astronauts will rendezvous with the ARV using the Orion spacecraft. The integrated attitude control concept that Orion will use for approach and docking and for mated operations will be described. Details of the ARV's attitude control system and its associated constraints for redirecting the asteroid to the distant retrograde orbit around the moon will be provided. Once Orion is docked to the ARV, an overall description of the mated stack attitude during all phases of the mission will be presented using a coordinate system that was developed for this mission. Next, the thermal and power constraints of both the ARV and Orion will be discussed as well as how they are used to define the optimal integrated stack attitude. Lastly, the lighting and communications constraints necessary for the crew's extravehicular activity planned to retrieve samples from the asteroid will be examined. Similarly, the joint attitude control strategy that employs both the Orion and the ARV attitude control assets prior, during, and after each extravehicular activity will also be thoroughly discussed.

Operations mission planner beyond the baseline

NASA Technical Reports Server (NTRS)

Biefeld, Eric; Cooper, Lynne

1991-01-01

The scheduling of Space Station Freedom must satisfy four major requirements. It must ensure efficient housekeeping operations, maximize the collection of science, respond to changes in tasking and available resources, and accommodate the above changes in a manner that minimizes disruption of the ongoing operations of the station. While meeting these requirements the scheduler must cope with the complexity, scope, and flexibility of SSF operations. This requires the scheduler to deal with an astronomical number of possible schedules. The Operations Mission Planner (OMP) is centered around minimally disruptive replanning and the use of heuristics limit search in scheduling. OMP has already shown several artificial intelligence based scheduling techniques such as Interleaved Iterative Refinement and Bottleneck Identification using Process Chronologies.

Evaluation of dual multi-mission space exploration vehicle operations during simulated planetary surface exploration

NASA Astrophysics Data System (ADS)

Abercromby, Andrew F. J.; Gernhardt, Michael L.; Jadwick, Jennifer

2013-10-01

IntroductionA pair of small pressurized rovers (multi-mission space exploration vehicles, or MMSEVs) is at the center of the Global Point-of-Departure architecture for future human lunar exploration. Simultaneous operation of multiple crewed surface assets should maximize productive crew time, minimize overhead, and preserve contingency return paths. MethodsA 14-day mission simulation was conducted in the Arizona desert as part of NASA's 2010 Desert Research and Technology Studies (DRATS) field test. The simulation involved two MMSEV earth-gravity prototypes performing geological exploration under varied operational modes affecting both the extent to which the MMSEVs must maintain real-time communications with the mission control center (Continuous [CC] versus Twice-a-Day [2/D]) and their proximity to each other (Lead-and-Follow [L&F] versus Divide-and-Conquer [D&C]). As part of a minimalist lunar architecture, no communication relay satellites were assumed. Two-person crews (an astronaut and a field geologist) operated each MMSEV, day and night, throughout the entire 14-day mission, only leaving via the suit ports to perform simulated extravehicular activities. Metrics and qualitative observations enabled evaluation of the extent to which the operating modes affected productivity and scientific data quality (SDQ). Results and discussionSDQ was greater during CC mode than during 2/D mode; metrics showed a marginal increase while qualitative assessments suggested a practically significant difference. For the communications architecture evaluated, significantly more crew time (14% per day) was required to maintain communications during D&C than during L&F (5%) or 2/D (2%), increasing the time required to complete all traverse objectives. Situational awareness of the other vehicle's location, activities, and contingency return constraints were qualitatively enhanced during L&F and 2/D modes due to line-of-sight and direct MMSEV-to-MMSEV communication. Future testing

The OSIRIS-Rex Asteroid Sample Return: Mission Operations Design

NASA Technical Reports Server (NTRS)

Gal-Edd, Jonathan; Cheuvront, Allan

2014-01-01

The OSIRIS-REx mission employs a methodical, phased approach to ensure success in meeting the missions science requirements. OSIRIS-REx launches in September 2016, with a backup launch period occurring one year later. Sampling occurs in 2019. The departure burn from Bennu occurs in March 2021. On September 24, 2023, the SRC lands at the Utah Test and Training Range (UTTR). Stardust heritage procedures are followed to transport the SRC to Johnson Space Center, where the samples are removed and delivered to the OSIRIS-REx curation facility. After a six-month preliminary examination period the mission will produce a catalog of the returned sample, allowing the worldwide community to request samples for detailed analysis.Traveling and returning a sample from an Asteroid that has not been explored before requires unique operations consideration. The Design Reference Mission (DRM) ties together space craft, instrument and operations scenarios. The project implemented lessons learned from other small body missions: APLNEAR, JPLDAWN and ESARosetta. The key lesson learned was expected the unexpected and implement planning tools early in the lifecycle. In preparation to PDR, the project changed the asteroid arrival date, to arrive one year earlier and provided additional time margin. STK is used for Mission Design and STKScheduler for instrument coverage analysis.

Crewmember and mission control personnel interactions during International Space Station missions.

PubMed

Kanas, Nick A; Salnitskiy, Vyacheslav P; Boyd, Jennifer E; Gushin, Vadim I; Weiss, Daniel S; Saylor, Stephanie A; Kozerenko, Olga P; Marmar, Charles R

2007-06-01

Reports from astronauts and cosmonauts, studies from space analogue environments on Earth, and our previous research on the Mir Space Station have identified a number of psychosocial issues that can lead to problems during long-duration space missions. Three of these issues (time effects, displacement, leader role) were studied during a series of long-duration missions to the International Space Station (ISS). As in our previous Mir study, mood and group climate questions from the Profile of Mood States or POMS, the Group Environment Scale or GES, and the Work Environment Scale or WES were completed weekly by 17 ISS crewmembers (15 men, 2 women) in space and 128 American and Russian personnel in mission control. The results did not support the presence of decrements in mood and group cohesion during the 2nd half of the missions or in any specific quarter. The results did support the predicted displacement of negative feelings to outside supervisors in both crew and mission control subjects on all six questionnaire subscales tested. Crewmembers related cohesion in their group to the support role of their commander. For mission control personnel, greater cohesion was linked to the support role as well as to the task role of their leader. The findings from our previous study on the Mir Space Station were essentially replicated on board the ISS. The findings suggest a number of countermeasures for future on-orbit missions, some of which may not be relevant for expeditionary missions (e.g., to Mars).

Tracking and data system support for the Viking 1975 mission to Mars. Volume 3: Planetary operations

NASA Technical Reports Server (NTRS)

Mudgway, D. J.

1977-01-01

The support provided by the Deep Space Network to the 1975 Viking Mission from the first landing on Mars July 1976 to the end of the Prime Mission on November 15, 1976 is described and evaluated. Tracking and data acquisition support required the continuous operation of a worldwide network of tracking stations with 64-meter and 26-meter diameter antennas, together with a global communications system for the transfer of commands, telemetry, and radio metric data between the stations and the Network Operations Control Center in Pasadena, California. Performance of the deep-space communications links between Earth and Mars, and innovative new management techniques for operations and data handling are included.

View of activity in Mission Control Center during Apollo 15 EVA

NASA Image and Video Library

1971-08-02

S71-41852 (2 Aug. 1971) --- Gerald D. Griffin, foreground, stands near his console in the Mission Operations Control Room (MOCR) during Apollo 15's third extravehicular activity (EVA) on the lunar surface. Griffin is Gold Team (Shift 1) flight director for the Apollo 15 mission. Astronauts David R. Scott and James B. Irwin can be seen on the large screen at the front of the MOCR as they participate in sample-gathering on the lunar surface.

The University of Colorado OSO-8 spectrometer experiment. IV - Mission operations

NASA Technical Reports Server (NTRS)

Hansen, E. R.; Bruner, E. C., Jr.

1979-01-01

The remote operation of two high-resolution ultraviolet spectrometers on the OSO-8 satellite is discussed. Mission operations enabled scientific observers to plan observations based on current solar data, interact with the observing program using real- or near real-time data and commands, evaluate quick-look instrument data, and analyze the observations for publication. During routine operations, experiments were planned a day prior to their execution, and the data from these experiments received a day later. When a shorter turnaround was required, a real-time mode was available. Here, the real-time data and command links into the remote control center were used to evaluate experiment operation and make satellite pointing or instrument configuration changes with a 1-90 minute turnaround.

Spacelab Mission Implementation Cost Assessment (SMICA)

NASA Technical Reports Server (NTRS)

Guynes, B. V.

1984-01-01

A total savings of approximately 20 percent is attainable if: (1) mission management and ground processing schedules are compressed; (2) the equipping, staffing, and operating of the Payload Operations Control Center is revised, and (3) methods of working with experiment developers are changed. The development of a new mission implementation technique, which includes mission definition, experiment development, and mission integration/operations, is examined. The Payload Operations Control Center is to relocate and utilize new computer equipment to produce cost savings. Methods of reducing costs by minimizing the Spacelab and payload processing time during pre- and post-mission operation at KSC are analyzed. The changes required to reduce costs in the analytical integration process are studied. The influence of time, requirements accountability, and risk on costs is discussed. Recommendation for cost reductions developed by the Spacelab Mission Implementation Cost Assessment study are listed.

Ground Support Network for Operational Radio Occultation Missions

NASA Astrophysics Data System (ADS)

Zandbergen, R.; Enderle, W.; Marquardt, C.; Wollenweber, F.

2012-04-01

The EUMETSAT/ESA Metop/EPS GRAS radio occultation mission stands out for its operational nature. From the beginning, EUMETSAT has decided to rely on an operational system for provision of the auxiliary GPS products that are needed in the occultation processing. This system is the GRAS Ground Support Network (GSN), operated in the Navigation Facility of ESOC in Darmstadt, which was first presented at EGU in 2008. The GRAS GSN is driven primarily by timeliness, availability and accuracy requirements. The performance of the GSN, measured on a monthly basis, has not only consistently met these requirements since the start of its operations, but has also been improved through several system enhancements. Currently, an additional service is being delivered on an experimental basis, consisting of a near-real time Navigation Bit Stream product, which will allow the processing of open-loop data, further increasing the scientific return of the GRAS instrument, or any other radio occultation mission using this data. This paper will present the GRAS GSN in its current configuration, and demonstrate its excellent performance in terms of accuracy, availability and timeliness. The application of the bit stream data will be shown. Some future evolution perspectives of the GRAS GSN will also be addressed. It will be demonstrated that the GRAS GSN has the potential of serving also other present and future radio occultation missions.

Flight controller alertness and performance during spaceflight shiftwork operations.

PubMed

Kelly, S M; Rosekind, M R; Dinges, D F; Miller, D L; Gillen, K A; Gregory, K B; Aguilar, R D; Smith, R M

1998-09-01

Decreased alertness and performance associated with fatigue, sleep loss, and circadian disruption are issues faced by a diverse range of shiftwork operations personnel. During Space Transportation System (STS) operations, Mission Operations Directorate (MOD) personnel provide 24-hr. coverage of critical tasks. A joint NASA Johnson Space Center and NASA Ames Research Center project was undertaken to examine these issues in flight controllers during MOD shiftwork operations. An initial operational test of procedures and measures was conducted during the STS-53 mission in December 1992. The study measures included a Background Questionnaire, a subjective daily logbook completed on a 24-hour basis (to report sleep patterns, work periods, etc.), and an 8 minute performance and mood test battery administered at the beginning, middle, and end of each shift period. Seventeen flight controllers representing the 3 Orbit shifts participated. The initial results clearly support the need for further data collection during other STS missions to document baseline levels of alertness and performance during MOD shiftwork operations. Countermeasure strategies specific to the MOD environment are being developed to minimize the adverse effects of fatigue, sleep loss, and circadian disruption engendered by shiftwork operations. These issues are especially pertinent for the night shift operations and the acute phase advance required for the transition of day shift personnel into the night for shuttle launch. Implementation and evaluation of the countermeasure strategies to maximize alertness and performance is planned. As STS missions extend to further EDO (extended duration orbiters), and timelines and planning for 24-hour Space Station operations continue, alertness and performance issues related to sleep and circadian disruption will remain highly relevant in the MOD environment.

Using full-mission simulation for human factors research in air transport operations

NASA Technical Reports Server (NTRS)

Orlady, Harry W.; Hennessy, Robert W.; Obermayer, Richard; Vreuls, Donald; Murphy, Miles R.

1988-01-01

This study examined state-of-the-art mission oriented simulation and its use in human factors research. Guidelines were developed for doing full-mission human factors research on crew member behavior during simulated air transport operations. The existing literature was reviewed. However, interviews with experienced investigators provided the most useful information. The fundamental scientific and practical issues of behavioral research in a simulation environment are discussed. Guidelines are presented for planning, scenario development, and the execution of behavioral research using full-mission simulation in the context of air transport flight operations . Research is recommended to enhance the validity and productivity of full-mission research by: (1) validating the need for high-fidelity simulation of all major elements in the operational environment, (2) improving methods for conducting full-mission research, and (3) examining part-task research on specific problems through the use of vehicles which contain higher levels of abstraction (and lower fidelity) of the operational environment.

Shuttle Radar Topography Mission (SRTM) Flight System Design and Operations Overview

NASA Technical Reports Server (NTRS)

Shen, Yuhsyen; Shaffer, Scott J.; Jordan, Rolando L.

2000-01-01

This paper provides an overview of the Shuttle Radar Topography Mission (SRTM), with emphasis on flight system implementation and mission operations from systems engineering perspective. Successfully flown in February, 2000, the SRTM's primary payload consists of several subsystems to form the first spaceborne dual-frequency (C-band and X-band) fixed baseline interferometric synthetic aperture radar (InSAR) system, with the mission objective to acquire data sets over 80% of Earth's landmass for height reconstruction. The paper provides system architecture, unique design features, engineering budgets, design verification, in-flight checkout and data acquisition of the SRTM payload, in particular for the C-band system. Mission operation and post-mission data processing activities are also presented. The complexity of the SRTM as a system, the ambitious mission objective, the demanding requirements and the high interdependency between multi-disciplined subsystems posed many challenges. The engineering experience and the insight thus gained have important implications for future spaceborne interferometric SAR mission design and implementation.

Technical Challenges and Opportunities of Centralizing Space Science Mission Operations (SSMO) at NASA Goddard Space Flight Center

NASA Technical Reports Server (NTRS)

Ido, Haisam; Burns, Rich

2015-01-01

The NASA Goddard Space Science Mission Operations project (SSMO) is performing a technical cost-benefit analysis for centralizing and consolidating operations of a diverse set of missions into a unified and integrated technical infrastructure. The presentation will focus on the notion of normalizing spacecraft operations processes, workflows, and tools. It will also show the processes of creating a standardized open architecture, creating common security models and implementations, interfaces, services, automations, notifications, alerts, logging, publish, subscribe and middleware capabilities. The presentation will also discuss how to leverage traditional capabilities, along with virtualization, cloud computing services, control groups and containers, and possibly Big Data concepts.

Operational Processing of Ground Validation Data for the Tropical Rainfall Measuring Mission

NASA Technical Reports Server (NTRS)

Kulie, Mark S.; Robinson, Mike; Marks, David A.; Ferrier, Brad S.; Rosenfeld, Danny; Wolff, David B.

1999-01-01

The Tropical Rainfall Measuring Mission (TRMM) satellite was successfully launched in November 1997. A primary goal of TRMM is to sample tropical rainfall using the first active spaceborne precipitation radar. To validate TRMM satellite observations, a comprehensive Ground Validation (GV) Program has been implemented for this mission. A key component of GV is the analysis and quality control of meteorological ground-based radar data from four primary sites: Melbourne, FL; Houston, TX; Darwin, Australia; and Kwajalein Atoll, RMI. As part of the TRMM GV effort, the Joint Center for Earth Systems Technology (JCET) at the University of Maryland, Baltimore County, has been tasked with developing and implementing an operational system to quality control (QC), archive, and provide data for subsequent rainfall product generation from the four primary GV sites. This paper provides an overview of the JCET operational environment. A description of the QC algorithm and performance, in addition to the data flow procedure between JCET and the TRNM science and Data Information System (TSDIS), are presented. The impact of quality-controlled data on higher level rainfall and reflectivity products will also be addressed, Finally, a brief description of JCET's expanded role into producing reference rainfall products will be discussed.

Formation Control for the Maxim Mission.

NASA Technical Reports Server (NTRS)

Luquette, Richard J.; Leitner, Jesse; Gendreau, Keith; Sanner, Robert M.

2004-01-01

Over the next twenty years, a wave of change is occurring in the spacebased scientific remote sensing community. While the fundamental limits in the spatial and angular resolution achievable in spacecraft have been reached, based on today's technology, an expansive new technology base has appeared over the past decade in the area of Distributed Space Systems (DSS). A key subset of the DSS technology area is that which covers precision formation flying of space vehicles. Through precision formation flying, the baselines, previously defined by the largest monolithic structure which could fit in the largest launch vehicle fairing, are now virtually unlimited. Several missions including the Micro-Arcsecond X-ray Imaging Mission (MAXIM), and the Stellar Imager will drive the formation flying challenges to achieve unprecedented baselines for high resolution, extended-scene, interferometry in the ultraviolet and X-ray regimes. This paper focuses on establishing the feasibility for the formation control of the MAXIM mission. The Stellar Imager mission requirements are on the same order of those for MAXIM. This paper specifically addresses: (1) high-level science requirements for these missions and how they evolve into engineering requirements; (2) the formation control architecture devised for such missions; (3) the design of the formation control laws to maintain very high precision relative positions; and (4) the levels of fuel usage required in the duration of these missions. Specific preliminary results are presented for two spacecraft within the MAXIM mission.

Geostationary Operational Environmental Satellite (GOES)-8 mission flight experience

NASA Technical Reports Server (NTRS)

Noonan, C. H.; Mcintosh, R. J.; Rowe, J. N.; Defazio, R. L.; Galal, K. F.

1995-01-01

The Geostationary Operational Environmental Satellite (GOES)-8 spacecraft was launched on April 13, 1994, at 06:04:02 coordinated universal time (UTC), with separation from the Atlas-Centaur launch vehicle occurring at 06:33:05 UTC. The launch was followed by a series of complex, intense operations to maneuver the spacecraft into its geosynchronous mission orbit. The Flight Dynamics Facility (FDF) of the Goddard Space Flight Center (GSFC) Flight Dynamics Division (FDD) was responsible for GOES-8 attitude, orbit maneuver, orbit determination, and station acquisition support during the ascent phase. This paper summarizes the efforts of the FDF support teams and highlights some of the unique challenges the launch team faced during critical GOES-8 mission support. FDF operations experience discussed includes: (1) The abort of apogee maneuver firing-1 (AMF-1), cancellation of AMF-3, and the subsequent replans of the maneuver profile; (2) The unexpectedly large temperature dependence of the digital integrating rate assembly (DIRA) and its effect on GOES-8 attitude targeting in support of perigee raising maneuvers; (3) The significant effect of attitude control thrusting on GOES-8 orbit determination solutions; (4) Adjustment of the trim tab to minimize torque due to solar radiation pressure; and (5) Postlaunch analysis performed to estimate the GOES-8 separation attitude. The paper also discusses some key FDF GOES-8 lessons learned to be considered for the GOES-J launch which is currently scheduled for May 19, 1995.

NASA's Spitzer Space Telescope's Operational Mission Experience

NASA Technical Reports Server (NTRS)

Wilson, Robert K.; Scott, Charles P.

2006-01-01

New Generation of Detector Arrays(100 to 10,000 Gain in Capability over Previous Infrared Space Missions). IRAC: 256 x 256 pixel arrays operating at 3.6 microns, 4.5 microns, 5.8 microns, 8.0 microns. MIPS: Photometer with 3 sets of arrays operating at 24 microns, 70 microns and 160 microns. 128 x 128; 32 x 32 and 2 x 20 arrays. Spectrometer with 50-100 micron capabilities. IRS: 4 Array (128x128 pixel) Spectrograph, 4 -40 microns. Warm Launch Architecture: All other Infrared Missions launched with both the telescope and scientific instrument payload within the cryostat or Dewar. Passive cooling used to cool outer shell to approx.40 K. Cryogenic Boil-off then cools telescope to required 5.5K. Earth Trailing Heliocentric Orbit: Increased observing efficiency, simplification of observation planning, removes earth as heat source.

Galileo mission planning for Low Gain Antenna based operations

NASA Technical Reports Server (NTRS)

Gershman, R.; Buxbaum, K. L.; Ludwinski, J. M.; Paczkowski, B. G.

1994-01-01

The Galileo mission operations concept is undergoing substantial redesign, necessitated by the deployment failure of the High Gain Antenna, while the spacecraft is on its way to Jupiter. The new design applies state-of-the-art technology and processes to increase the telemetry rate available through the Low Gain Antenna and to increase the information density of the telemetry. This paper describes the mission planning process being developed as part of this redesign. Principal topics include a brief description of the new mission concept and anticipated science return (these have been covered more extensively in earlier papers), identification of key drivers on the mission planning process, a description of the process and its implementation schedule, a discussion of the application of automated mission planning tool to the process, and a status report on mission planning work to date. Galileo enhancements include extensive reprogramming of on-board computers and substantial hard ware and software upgrades for the Deep Space Network (DSN). The principal mode of operation will be onboard recording of science data followed by extended playback periods. A variety of techniques will be used to compress and edit the data both before recording and during playback. A highly-compressed real-time science data stream will also be important. The telemetry rate will be increased using advanced coding techniques and advanced receivers. Galileo mission planning for orbital operations now involves partitioning of several scarce resources. Particularly difficult are division of the telemetry among the many users (eleven instruments, radio science, engineering monitoring, and navigation) and allocation of space on the tape recorder at each of the ten satellite encounters. The planning process is complicated by uncertainty in forecast performance of the DSN modifications and the non-deterministic nature of the new data compression schemes. Key mission planning steps include

Galileo mission planning for Low Gain Antenna based operations

NASA Astrophysics Data System (ADS)

Gershman, R.; Buxbaum, K. L.; Ludwinski, J. M.; Paczkowski, B. G.

1994-11-01

The Galileo mission operations concept is undergoing substantial redesign, necessitated by the deployment failure of the High Gain Antenna, while the spacecraft is on its way to Jupiter. The new design applies state-of-the-art technology and processes to increase the telemetry rate available through the Low Gain Antenna and to increase the information density of the telemetry. This paper describes the mission planning process being developed as part of this redesign. Principal topics include a brief description of the new mission concept and anticipated science return (these have been covered more extensively in earlier papers), identification of key drivers on the mission planning process, a description of the process and its implementation schedule, a discussion of the application of automated mission planning tool to the process, and a status report on mission planning work to date. Galileo enhancements include extensive reprogramming of on-board computers and substantial hard ware and software upgrades for the Deep Space Network (DSN). The principal mode of operation will be onboard recording of science data followed by extended playback periods. A variety of techniques will be used to compress and edit the data both before recording and during playback. A highly-compressed real-time science data stream will also be important. The telemetry rate will be increased using advanced coding techniques and advanced receivers. Galileo mission planning for orbital operations now involves partitioning of several scarce resources. Particularly difficult are division of the telemetry among the many users (eleven instruments, radio science, engineering monitoring, and navigation) and allocation of space on the tape recorder at each of the ten satellite encounters. The planning process is complicated by uncertainty in forecast performance of the DSN modifications and the non-deterministic nature of the new data compression schemes. Key mission planning steps include

Field Experiments using Telepresence and Virtual Reality to Control Remote Vehicles: Application to Mars Rover Missions

NASA Technical Reports Server (NTRS)

Stoker, Carol

1994-01-01

This paper will describe a series of field experiments to develop and demonstrate file use of Telepresence and Virtual Reality systems for controlling rover vehicles on planetary surfaces. In 1993, NASA Ames deployed a Telepresence-Controlled Remotely Operated underwater Vehicle (TROV) into an ice-covered sea environment in Antarctica. The goal of the mission was to perform scientific exploration of an unknown environment using a remote vehicle with telepresence and virtual reality as a user interface. The vehicle was operated both locally, from above a dive hole in the ice through which it was launched, and remotely over a satellite communications link from a control room at NASA's Ames Research center, for over two months. Remote control used a bidirectional Internet link to the vehicle control computer. The operator viewed live stereo video from the TROV along with a computer-gene rated graphic representation of the underwater terrain showing file vehicle state and other related information. Tile actual vehicle could be driven either from within the virtual environment or through a telepresence interface. In March 1994, a second field experiment was performed in which [lie remote control system developed for the Antarctic TROV mission was used to control the Russian Marsokhod Rover, an advanced planetary surface rover intended for launch in 1998. Marsokhod consists of a 6-wheel chassis and is capable of traversing several kilometers of terrain each day, The rover can be controlled remotely, but is also capable of performing autonomous traverses. The rover was outfitted with a manipulator arm capable of deploying a small instrument, collecting soil samples, etc. The Marsokhod rover was deployed at Amboy Crater in the Mojave desert, a Mars analog site, and controlled remotely from Los Angeles. in two operating modes: (1) a Mars rover mission simulation with long time delay and (2) a Lunar rover mission simulation with live action video. A team of planetary

Apollo experience report: Guidance and control systems. Mission control programmer for unmanned missions AS-202, Apollo 4, and Apollo 6

NASA Technical Reports Server (NTRS)

Holloway, G. F.

1975-01-01

An unmanned test flight program required to evaluate the command module heat shield and the structural integrity of the command and service module/Saturn launch vehicle is described. The mission control programer was developed to provide the unmanned interface between the guidance and navigation computer and the other spacecraft systems for mission event sequencing and real-time ground control during missions AS-202, Apollo 4, and Apollo 6. The development of this unmanned programer is traced from the initial concept through the flight test phase. Detailed discussions of hardware development problems are given with the resulting solutions. The mission control programer functioned correctly without any flight anomalies for all missions. The Apollo 4 mission control programer was reused for the Apollo 6 flight, thus being one of the first subsystems to be reflown on an Apollo space flight.

Expert diagnostics system as a part of analysis software for power mission operations

NASA Technical Reports Server (NTRS)

Harris, Jennifer A.; Bahrami, Khosrow A.

1993-01-01

The operation of interplanetary spacecraft at JPL has become an increasingly complex activity. This complexity is due to advanced spacecraft designs and ambitious mission objectives which lead to operations requirements that are more demanding than those of any previous mission. For this reason, several productivity enhancement measures are underway at JPL within mission operations, particularly in the spacecraft analysis area. These measures aimed at spacecraft analysis include: the development of a multi-mission, multi-subsystem operations environment; the introduction of automated tools into this environment; and the development of an expert diagnostics system. This paper discusses an effort to integrate the above mentioned productivity enhancement measures. A prototype was developed that integrates an expert diagnostics system into a multi-mission, multi-subsystem operations environment using the Galileo Power / Pyro Subsystem as a testbed. This prototype will be discussed in addition to background information associated with it.

Third International Symposium on Space Mission Operations and Ground Data Systems, part 1

NASA Technical Reports Server (NTRS)

Rash, James L. (Editor)

1994-01-01

Under the theme of 'Opportunities in Ground Data Systems for High Efficiency Operations of Space Missions,' the SpaceOps '94 symposium included presentations of more than 150 technical papers spanning five topic areas: Mission Management, Operations, Data Management, System Development, and Systems Engineering. The papers focus on improvements in the efficiency, effectiveness, productivity, and quality of data acquisition, ground systems, and mission operations. New technology, techniques, methods, and human systems are discussed. Accomplishments are also reported in the application of information systems to improve data retrieval, reporting, and archiving; the management of human factors; the use of telescience and teleoperations; and the design and implementation of logistics support for mission operations.

Coordination of Mars Express and Beagle2 Mission Operations

NASA Astrophysics Data System (ADS)

Trautner, R.; Chicarro, A.; Martin, P.

The Mars Express orbiter carrying the British Beagle 2 lander will arrive at Mars late 2003. The evaluation of science data from both the MEX orbiter and the lander will benefit from coordinated measurements obtained by the instrument sets on each space- craft. Furthermore, data obtained during the early mission of one spacecraft should be taken into account for the science operations planning of the other spacecraft in order to optimize the scientific return. Based on the capabilities and goals of the scientific instruments on both platforms, possible areas of cooperation are proposed. The flex- ibility required in mission operations planning for both the orbiter and the lander are assessed, and the expected benefits of coordinated operations are explained.

Transportable Payload Operations Control Center reusable software: Building blocks for quality ground data systems

NASA Technical Reports Server (NTRS)

Mahmot, Ron; Koslosky, John T.; Beach, Edward; Schwarz, Barbara

1994-01-01

The Mission Operations Division (MOD) at Goddard Space Flight Center builds Mission Operations Centers which are used by Flight Operations Teams to monitor and control satellites. Reducing system life cycle costs through software reuse has always been a priority of the MOD. The MOD's Transportable Payload Operations Control Center development team established an extensive library of 14 subsystems with over 100,000 delivered source instructions of reusable, generic software components. Nine TPOCC-based control centers to date support 11 satellites and achieved an average software reuse level of more than 75 percent. This paper shares experiences of how the TPOCC building blocks were developed and how building block developer's, mission development teams, and users are all part of the process.

Multi-Agent Modeling and Simulation Approach for Design and Analysis of MER Mission Operations

NASA Technical Reports Server (NTRS)

Seah, Chin; Sierhuis, Maarten; Clancey, William J.

2005-01-01

A space mission operations system is a complex network of human organizations, information and deep-space network systems and spacecraft hardware. As in other organizations, one of the problems in mission operations is managing the relationship of the mission information systems related to how people actually work (practices). Brahms, a multi-agent modeling and simulation tool, was used to model and simulate NASA's Mars Exploration Rover (MER) mission work practice. The objective was to investigate the value of work practice modeling for mission operations design. From spring 2002 until winter 2003, a Brahms modeler participated in mission systems design sessions and operations testing for the MER mission held at Jet Propulsion Laboratory (JPL). He observed how designers interacted with the Brahms tool. This paper discussed mission system designers' reactions to the simulation output during model validation and the presentation of generated work procedures. This project spurred JPL's interest in the Brahms model, but it was never included as part of the formal mission design process. We discuss why this occurred. Subsequently, we used the MER model to develop a future mission operations concept. Team members were reluctant to use the MER model, even though it appeared to be highly relevant to their effort. We describe some of the tool issues we encountered.

Orbital operations study. Volume 1: Mission analysis

NASA Technical Reports Server (NTRS)

Steinwachs, W. L.

1972-01-01

The final report of the orbital operations study and a summary of the 25 elements in the study inventory are presented. Fourteen interfacing activities are defined. Eleven mission models encompassing all potential interfacing element pairs and interfacing activities are included.

Shift changes, updates, and the on-call architecture in space shuttle mission control.

PubMed

Patterson, E S; Woods, D D

2001-01-01

In domains such as nuclear power, industrial process control, and space shuttle mission control, there is increased interest in reducing personnel during nominal operations. An essential element in maintaining safe operations in high risk environments with this 'on-call' organizational architecture is to understand how to bring called-in practitioners up to speed quickly during escalating situations. Targeted field observations were conducted to investigate what it means to update a supervisory controller on the status of a continuous, anomaly-driven process in a complex, distributed environment. Sixteen shift changes, or handovers, at the NASA Johnson Space Center were observed during the STS-76 Space Shuttle mission. The findings from this observational study highlight the importance of prior knowledge in the updates and demonstrate how missing updates can leave flight controllers vulnerable to being unprepared. Implications for mitigating risk in the transition to 'on-call' architectures are discussed.

Shift changes, updates, and the on-call architecture in space shuttle mission control

NASA Technical Reports Server (NTRS)

Patterson, E. S.; Woods, D. D.

2001-01-01

In domains such as nuclear power, industrial process control, and space shuttle mission control, there is increased interest in reducing personnel during nominal operations. An essential element in maintaining safe operations in high risk environments with this 'on-call' organizational architecture is to understand how to bring called-in practitioners up to speed quickly during escalating situations. Targeted field observations were conducted to investigate what it means to update a supervisory controller on the status of a continuous, anomaly-driven process in a complex, distributed environment. Sixteen shift changes, or handovers, at the NASA Johnson Space Center were observed during the STS-76 Space Shuttle mission. The findings from this observational study highlight the importance of prior knowledge in the updates and demonstrate how missing updates can leave flight controllers vulnerable to being unprepared. Implications for mitigating risk in the transition to 'on-call' architectures are discussed.

View of Mission Control Center during the Apollo 13 liftoff

NASA Image and Video Library

1970-04-11

S70-34627 (11 April 1970) --- Sigurd A. Sjoberg, director of flight operations, at the Manned Spacecraft Center (MSC), views the Apollo 13 liftoff from a console in the MSC Mission Control Center (MCC), Building 30. Apollo 13 lifted off at 1:13 p.m. (CST) April 11, 1970. Photo credit: NASA

Command and Control of Joint Air Operations through Mission Command

DTIC Science & Technology

2016-06-01

and outlines the C2 architecture systems, processes, and philosophy of com- mand required to enable mission command effectively. Mission Command...General Dempsey highlights the fact that “trust is the moral sinew that binds the distributed Joint Force 2020 together” and observes that “unless...con- fident about how their subordinates will make decisions and adapt to the dynamic battlespace environment. Processes, Systems, and Philosophy of

Programmer's manual for the Mission Analysis Evaluation and Space Trajectory Operations program (MAESTRO)

NASA Technical Reports Server (NTRS)

Lutzky, D.; Bjorkman, W. S.

1973-01-01

The Mission Analysis Evaluation and Space Trajectory Operations program known as MAESTRO is described. MAESTRO is an all FORTRAN, block style, computer program designed to perform various mission control tasks. This manual is a guide to MAESTRO, providing individuals the capability of modifying the program to suit their needs. Descriptions are presented of each of the subroutines descriptions consist of input/output description, theory, subroutine description, and a flow chart where applicable. The programmer's manual also contains a detailed description of the common blocks, a subroutine cross reference map, and a general description of the program structure.

Wind Prelaunch Mission Operations Report (MOR)

NASA Technical Reports Server (NTRS)

1994-01-01

The National Aeronautics and Space Administration (NASA) Wind mission is the first mission of the Global Geospace Science (GGS) initiative. The Wind laboratory will study the properties of particles and waves in the region between the Earth and the Sun. Using the Moon s gravity to save fuel, dual lunar swing-by orbits enable the spacecraft to sample regions close to and far from the Earth. During the three year mission, Wind will pass through the bow shock of Earth's magnetosphere to begin a thorough investigation of the solar wind. Mission objectives require spacecraft measurements in two orbits: lunar swing- by ellipses out to distances of 250 Earth radii (RE) and a small orbit around the Lagrangian point L-l that remains between the Earth and the Sun. Wind will be placed into an initial orbit for approximately 2 years. It will then be maneuvered into a transition orbit and ultimately into a halo orbit at the Earth-Sun L-l point where it will operate for the remainder of its lifetime. The Wind satellite development was managed by NASA's Goddard Space Flight Center with the Martin Marietta Corporation, Astro-Space Division serving as the prime contractor. Overall programmatic direction was provided by NASA Headquarters, Office of Space Science. The spacecraft will be launched under a launch service contract with the McDonnell Douglas Corporation on a Delta II Expendable Launch Vehicle (ELV) within a November l-l4, 1994 launch window. The Wind spacecraft carries six U.S. instruments, one French instrument, and the first Russian instrument ever to fly on an American satellite. The Wind and Polar missions are the two components of the GGS Program. Wind is also the second mission of the International Solar Terrestrial Physics (ISTP) Program. The first ISTP mission, Geotail, is a joint project of the Institute of Space and Astronautical Science of Japan and NASA which launched in 1992. The Wind mission is planned to overlap Geotail by six months and Polar by one year

MAIUS-1- Vehicle, Subsystems Design and Mission Operations

NASA Astrophysics Data System (ADS)

Stamminger, A.; Ettl, J.; Grosse, J.; Horschgen-Eggers, M.; Jung, W.; Kallenbach, A.; Raith, G.; Saedtler, W.; Seidel, S. T.; Turner, J.; Wittkamp, M.

2015-09-01

In November 2015, the DLR Mobile Rocket Base will launch the MAIUS-1 rocket vehicle at Esrange, Northern Sweden. The MAIUS-A experiment is a pathfinder atom optics experiment. The scientific objective of the mission is the first creation of a BoseEinstein Condensate in space and performing atom interferometry on a sounding rocket [3]. MAIUS-1 comprises a two-stage unguided solid propellant VSB-30 rocket motor system. The vehicle consists of a Brazilian 53 1 motor as 1 st stage, a 530 motor as 2nd stage, a conical motor adapter, a despin module, a payload adapter, the MAIUS-A experiment consisting of five experiment modules, an attitude control system module, a newly developed conical service system, and a two-staged recovery system including a nosecone. In contrast to usual payloads on VSB-30 rockets, the payload has a diameter of 500 mm due to constraints of the scientific experiment. Because of this change in design, a blunted nosecone is necessary to guarantee the required static stability during the ascent phase of the flight. This paper will give an overview on the subsystems which have been built at DLR MORABA, especially the newly developed service system. Further, it will contain a description of the MAIUS-1 vehicle, the mission and the unique requirements on operations and attitude control, which is additionally required to achieve a required attitude with respect to the nadir vector. Additionally to a usual microgravity environment, the MAIUS-l payload requires attitude control to achieve a required attitude with respect to the nadir vector.

Proximity Operations for the Robotic Boulder Capture Option for the Asteroid Redirect Mission

NASA Technical Reports Server (NTRS)

Reeves, David M.; Naasz, Bo J.; Wright, Cinnamon A.; Pini, Alex J.

2014-01-01

In September of 2013, the Asteroid Robotic Redirect Mission (ARRM) Option B team was formed to expand on NASA's previous work on the robotic boulder capture option. While the original Option A concept focuses on capturing an entire smaller Near-Earth Asteroid (NEA) using an inflatable bag capture mechanism, this design seeks to land on a larger NEA and retrieve a boulder off of its surface. The Option B team has developed a detailed and feasible mission concept that preserves many aspects of Option A's vehicle design while employing a fundamentally different technique for returning a significant quantity of asteroidal material to the Earth-Moon system. As part of this effort, a point of departure proximity operations concept was developed complete with a detailed timeline, as well as DeltaV and propellant allocations. Special attention was paid to the development of the approach strategy, terminal descent to the surface, controlled ascent with the captured boulder, and control during the Enhanced Gravity Tractor planetary defense demonstration. The concept of retrieving a boulder from the surface of an asteroid and demonstrating the Enhanced Gravity Tractor planetary defense technique is found to be feasible and within the proposed capabilities of the Asteroid Redirect Vehicle (ARV). While this point of departure concept initially focuses on a mission to Itokawa, the proximity operations design is also shown to be extensible to wide range of asteroids.

OPALS: Mission System Operations Architecture for an Optical Communications Demonstration on the ISS

NASA Technical Reports Server (NTRS)

Abrahamson, Matthew J.; Sindiy, Oleg V.; Oaida, Bogdan V.; Fregoso, Santos; Bowles-Martinez, Jessica N.; Kokorowski, Michael; Wilkerson, Marcus W.; Konyha, Alexander L.

2014-01-01

In spring 2014, the Optical PAyload for Lasercomm Science (OPALS) will launch to the International Space Station (ISS) to demonstrate space-to-ground optical communications. During a 90-day baseline mission, OPALS will downlink high quality, short duration videos to the Optical Communications Telescope Laboratory (OCTL) in Wrightwood, California. To achieve mission success, interfaces to the ISS payload operations infrastructure are established. For OPALS, the interfaces facilitate activity planning, hazardous laser operations, commanding, and telemetry transmission. In addition, internal processes such as pointing prediction and data processing satisfy the technical requirements of the mission. The OPALS operations team participates in Operational Readiness Tests (ORTs) with external partners to exercise coordination processes and train for the overall mission. The tests have provided valuable insight into operational considerations on the ISS.

MOS 2.0: The Next Generation in Mission Operations Systems

NASA Technical Reports Server (NTRS)

Bindschadler, Duane L.; Boyles, Carole A.; Carrion, Carlos; Delp, Chris L.

2010-01-01

A Mission Operations System (MOS) or Ground System constitutes that portion of an overall space mission Enterprise that resides here on Earth. Over the past two decades, technological innovations in computing and software technologies have allowed an MOS to support ever more complex missions while consuming a decreasing fraction of Project development budgets. Despite (or perhaps, because of) such successes, it is routine to hear concerns about the cost of MOS development. At the same time, demand continues for Ground Systems which will plan more spacecraft activities with fewer commanding errors, provide scientists and engineers with more autonomous functionality, process and manage larger and more complex data more quickly, all while requiring fewer people to develop, deploy, operate and maintain them. One successful approach to such concerns over this period is a multimission approach, based on the reuse of portions (most often software) developed and used in previous missions. The Advanced Multi-Mission Operations System (AMMOS), developed for deep-space science missions, is one successful example of such an approach. Like many computing-intensive systems, it has grown up in a near-organic fashion from a relatively simple set of tools into a complexly interrelated set of capabilities. Such systems, like a city lacking any concept of urban planning, can and will grow in ways that are neither efficient nor particularly easy to sustain. To meet the growing demands and unyielding constraints placed on ground systems, a new approach is necessary. Under the aegis of a multi-year effort to revitalize the AMMOS's multimission operations capabilities, we are utilizing modern practices in systems architecting and model-based engineering to create the next step in Ground Systems: MOS 2.0. In this paper we outline our work (ongoing and planned) to architect and design a multimission MOS 2.0, describe our goals and measureable objectives, and discuss some of the benefits

Smart Cruise Control: UAV sensor operator intent estimation and its application

NASA Astrophysics Data System (ADS)

Cheng, Hui; Butler, Darren; Kumar, Rakesh

2006-05-01

Due to their long endurance, superior mobility and the low risk posed to the pilot and sensor operator, UAVs have become the preferred platform for persistent ISR missions. However, currently most UAV based ISR missions are conducted through manual operation. Event the simplest tasks, such as vehicle tracking, route reconnaissance and site monitoring, need the sensor operator's undivided attention and constant adjustment of the sensor control. The lack of autonomous behaviour greatly limits of the effectiveness and the capability of UAV-based ISR, especially the use of a large number of UAVs simultaneously. Although fully autonomous UAV based ISR system is desirable, it is still a distant dream due to the complexity and diversity of combat and ISR missions. In this paper, we propose a Smart Cruise Control system that can learn UAV sensor operator's intent and use it to complete tasks automatically, such as route reconnaissance and site monitoring. Using an operator attention model, the proposed system can estimate the operator's intent from how they control the sensor (e.g. camera) and the content of the imagery that is acquired. Therefore, for example, from initially manually controlling the UAV sensor to follow a road, the system can learn not only the preferred operation, "tracking", but also the road appearance, "what to track" in real-time. Then, the learnt models of both road and the desired operation can be used to complete the task automatically. We have demonstrated the Smart Cruise Control system using real UAV videos where roads need to be tracked and buildings need to be monitored.

Mission operations for unmanned nuclear electric propulsion outer planet exploration with a thermionic reactor spacecraft.

NASA Technical Reports Server (NTRS)

Spera, R. J.; Prickett, W. Z.; Garate, J. A.; Firth, W. L.

1971-01-01

Mission operations are presented for comet rendezvous and outer planet exploration NEP spacecraft employing in-core thermionic reactors for electric power generation. The selected reference missions are the Comet Halley rendezvous and a Jupiter orbiter at 5.9 planet radii, the orbit of the moon Io. The characteristics of the baseline multi-mission NEP spacecraft are presented and its performance in other outer planet missions, such as Saturn and Uranus orbiters and a Neptune flyby, are discussed. Candidate mission operations are defined from spacecraft assembly to mission completion. Pre-launch operations are identified. Shuttle launch and subsequent injection to earth escape by the Centaur D-1T are discussed, as well as power plant startup and the heliocentric mission phases. The sequence and type of operations are basically identical for all missions investigated.

Lessons learned - MO&DA at JPL. [Mission Operations and Data Analysis cost reduction of planetary exploration

NASA Technical Reports Server (NTRS)

Handley, Thomas H., Jr.

1993-01-01

The issues of how to avoid future surprise growth in Mission Operations and Data Analysis (MO&DA) costs and how to minimize total MO&DA costs for planetary missions are discussed within the context of JPL mission operations support. It is argued that there is no simple, single solution: the entire Project life-cycle must be addressed. It is concluded that cost models that can predict both MO&DA cost as well as Ground System development costs are needed. The first year MO&DA budget plotted against the total of ground and flight systems developments is shown. In order to better recognize changes and control costs in general, a modified funding line item breakdown is recommended to distinguish between development costs (prelaunch and postlaunch) and MO&DA costs.

Mission Operations Planning with Preferences: An Empirical Study

NASA Technical Reports Server (NTRS)

Bresina, John L.; Khatib, Lina; McGann, Conor

2006-01-01

This paper presents an empirical study of some nonexhaustive approaches to optimizing preferences within the context of constraint-based, mixed-initiative planning for mission operations. This work is motivated by the experience of deploying and operating the MAPGEN (Mixed-initiative Activity Plan GENerator) system for the Mars Exploration Rover Mission. Responsiveness to the user is one of the important requirements for MAPGEN, hence, the additional computation time needed to optimize preferences must be kept within reasonabble bounds. This was the primary motivation for studying non-exhaustive optimization approaches. The specific goals of rhe empirical study are to assess the impact on solution quality of two greedy heuristics used in MAPGEN and to assess the improvement gained by applying a linear programming optimization technique to the final solution.

STS payloads mission control study continuation phase A-1. Volume 2-C, task 3: Identification of joint activities and estimation of resources in preparation for joint flight operations

NASA Technical Reports Server (NTRS)

1976-01-01

Payload mission control concepts are developed for real time flight operations of STS. Flight planning, training, simulations, and other flight preparations are included. Payload activities for the preflight phase, activity sequences and organizational allocations, and traffic and experience factors to establish composite man-loading for joint STS payload activities are identified for flight operations from 1980 to 1985.

Spitzer Mission Operation System Planning for IRAC Warm-Instrument Characterization

NASA Technical Reports Server (NTRS)

Hunt, Joseph C., Jr.; Sarrel, Marc A.; Mahoney, William A.

2010-01-01

This paper will describe how the Spitzer Mission Operations System planned and executed the characterization phase between Spitzer's cryogenic mission and its warm mission. To the largest extend possible, the execution of this phase was done with existing processing and procedures. The modifications that were made were in response to the differences of the characterization phase compared to normal phases before and after. The primary two categories of difference are: unknown date of execution due to uncertainty of knowledge of the date of helium depletion, and the short cycle time for data analysis and re-planning during execution. In addition, all of the planning and design had to be done in parallel with normal operations, and we had to transition smoothly back to normal operations following the transition. This paper will also describe the re-planning we had to do following an anomaly discovered in the first days after helium depletion.

The Mission Operations System for Wide-field Infrared Survey Explorer (WISE)

NASA Technical Reports Server (NTRS)

Heinrichsen, Ingolf H.

2006-01-01

The goal of the Wide-field Infrared Survey Explorer (WISE) mission is to perform a highly sensitive all-sky survey in 4 wavebands from 3 to 25(mu)m. Launched on a Delta II rocket into a 500km Sun-synchronous orbit in June 2009, during its 7 months of operations, WISE will acquire about 50GBytes of raw science data every day, which will be down-linked via the TDRSS relay satellite system and processed into an astronomical catalogue and image atlas. The WISE mission operations system is being implemented in collaboration between UCLA, JPL and IPAC (Caltech). In this paper we describe the challenges to manage a high data rate, cryogenic, low earth-orbit mission; maintaining safe on-orbit operations, fast anomaly recoveries (mandated by the desire to provide complete sky coverage in a limited lifetime), production and dissemination of high quality science products, given the constraints imposed by funding profiles for small space missions.

Alternative Approaches to Mission Control Automation at NASA's Goddard Space Flight Center

NASA Technical Reports Server (NTRS)

Rackley, Michael; Cooter, Miranda; Davis, George; Mackey, Jennifer

2001-01-01

To meet its objective of reducing operations costs without incurring a corresponding increase in risk, NASA is seeking new methods to automate mission operations. This paper examines the state of the art in automating ground operations for space missions. A summary of available technologies and methods for automating mission operations is provided. Responses from interviews with several space mission FOTs (Flight Operations Teams) to assess the degree and success of those technologies and methods implemented are presented. Mission operators that were interviewed approached automation using different tools and methods resulting in varying degrees of success - from nearly completely automated to nearly completely manual. Two key criteria for successful automation are the active participation of the FOT in the planning, designing, testing, and implementation of the system and the relative degree of complexity of the mission.

Smart Structures for Vibration Control on Long-Term Space Exploration and Habitation Missions

NASA Technical Reports Server (NTRS)

Gattis, Christy B.; Shepard, W. Steve, Jr.

2004-01-01

The current vision for space exploration focuses on human missions to the Moon, Mars, and beyond. To support these goals, it is certain that new vehicles and intermediate bases will be developed, whether that means simply re-direction of the ISS as a "mission research facility" or construction of a lunar base. Since these facilities are expected to be constructed from inherently light-weight materials, this work examines some of the potential sources of vibration and noise as well as means for controlling these vibrations. Many of the operating components within these facilities, such as pumps, fans, and motors, will produce vibrations during operation. These vibrations become structure in which they are housed. Resonances can impact acoustic noise levels and noise quality within the environment, possibly affecting crew health and productivity. For long-term missions in particular, it is expected that crew members will spend significant portions of their time restrained in the structure, such as in seats. As a result, the general health and well-being of the crew can be improved by limiting the harmful effects of human exposure to long-term audible and tactile vibration input. Besides the human factor, this work also examines some operational considerations in which vibrations play an important role. Vibrations can impact the environment for science and in-situ manufacturing research within these vehicles. Since a benign vibratory environment is beneficial for most types of science experiments, there is a need for various forms of vibration control. Because the operational characteristics of a vehicle can change during a long-term mission, it is further expected that the characteristics of many of the vibratory excitations will change with time. Consequently, the form of vibration control needed to improve overall habitability and usefulness of the vehicle or element for exploration missions will rely to some degree on the vibration control system's ability to

Third International Symposium on Space Mission Operations and Ground Data Systems, part 2

NASA Technical Reports Server (NTRS)

Rash, James L. (Editor)

1994-01-01

Under the theme of 'Opportunities in Ground Data Systems for High Efficiency Operations of Space Missions,' the SpaceOps '94 symposium included presentations of more than 150 technical papers spanning five topic areas: Mission Management, Operations, Data Management, System Development, and Systems Engineering. The symposium papers focus on improvements in the efficiency, effectiveness, and quality of data acquisition, ground systems, and mission operations. New technology, methods, and human systems are discussed. Accomplishments are also reported in the application of information systems to improve data retrieval, reporting, and archiving; the management of human factors; the use of telescience and teleoperations; and the design and implementation of logistics support for mission operations. This volume covers expert systems, systems development tools and approaches, and systems engineering issues.

A Multifaceted Approach to Modernizing NASA's Advanced Multi-Mission Operations System (AMMOS) System Architecture

NASA Technical Reports Server (NTRS)

Estefan, Jeff A.; Giovannoni, Brian J.

2014-01-01

The Advanced Multi-Mission Operations Systems (AMMOS) is NASA's premier space mission operations product line offering for use in deep-space robotic and astrophysics missions. The general approach to AMMOS modernization over the course of its 29-year history exemplifies a continual, evolutionary approach with periods of sponsor investment peaks and valleys in between. Today, the Multimission Ground Systems and Services (MGSS) office-the program office that manages the AMMOS for NASA-actively pursues modernization initiatives and continues to evolve the AMMOS by incorporating enhanced capabilities and newer technologies into its end-user tool and service offerings. Despite the myriad of modernization investments that have been made over the evolutionary course of the AMMOS, pain points remain. These pain points, based on interviews with numerous flight project mission operations personnel, can be classified principally into two major categories: 1) information-related issues, and 2) process-related issues. By information-related issues, we mean pain points associated with the management and flow of MOS data across the various system interfaces. By process-related issues, we mean pain points associated with the MOS activities performed by mission operators (i.e., humans) and supporting software infrastructure used in support of those activities. In this paper, three foundational concepts-Timeline, Closed Loop Control, and Separation of Concerns-collectively form the basis for expressing a set of core architectural tenets that provides a multifaceted approach to AMMOS system architecture modernization intended to address the information- and process-related issues. Each of these architectural tenets will be further explored in this paper. Ultimately, we envision the application of these core tenets resulting in a unified vision of a future-state architecture for the AMMOS-one that is intended to result in a highly adaptable, highly efficient, and highly cost

The Evolvable Advanced Multi-Mission Operations System (AMMOS): Making Systems Interoperable

NASA Technical Reports Server (NTRS)

Ko, Adans Y.; Maldague, Pierre F.; Bui, Tung; Lam, Doris T.; McKinney, John C.

2010-01-01

The Advanced Multi-Mission Operations System (AMMOS) provides a common Mission Operation System (MOS) infrastructure to NASA deep space missions. The evolution of AMMOS has been driven by two factors: increasingly challenging requirements from space missions, and the emergence of new IT technology. The work described in this paper focuses on three key tasks related to IT technology requirements: first, to eliminate duplicate functionality; second, to promote the use of loosely coupled application programming interfaces, text based file interfaces, web-based frameworks and integrated Graphical User Interfaces (GUI) to connect users, data, and core functionality; and third, to build, develop, and deploy AMMOS services that are reusable, agile, adaptive to project MOS configurations, and responsive to industrially endorsed information technology standards.

Grand Challenge Problems in Real-Time Mission Control Systems for NASA's 21st Century Missions

NASA Technical Reports Server (NTRS)

Pfarr, Barbara B.; Donohue, John T.; Hughes, Peter M.

1999-01-01

Space missions of the 21st Century will be characterized by constellations of distributed spacecraft, miniaturized sensors and satellites, increased levels of automation, intelligent onboard processing, and mission autonomy. Programmatically, these missions will be noted for dramatically decreased budgets and mission development lifecycles. Current progress towards flexible, scaleable, low-cost, reusable mission control systems must accelerate given the current mission deployment schedule, and new technology will need to be infused to achieve desired levels of autonomy and processing capability. This paper will discuss current and future missions being managed at NASA's Goddard Space Flight Center in Greenbelt, MD. It will describe the current state of mission control systems and the problems they need to overcome to support the missions of the 21st Century.

Management of Operational Support Requirements for Manned Flight Missions

NASA Technical Reports Server (NTRS)

1991-01-01

This Instruction establishes responsibilities for managing the system whereby operational support requirements are levied for support of manned flight missions including associated payloads. This management system will ensure that support requirements are properly requested and responses are properly obtained to meet operational objectives.

PC-403: Pioneer Venus multiprobe spacecraft mission operational characteristics document, volume 2

NASA Technical Reports Server (NTRS)

Barker, F. C.

1978-01-01

The data handling subsystem, command subsystem, communications subsystem, power subsystem, and mission operations of the Pioneer Venus multiprobe are presented. The multiprobe spacecraft performance in normal operating modes that correspond to the performance of specific functions at the time of specific events in the mission is described.

SPOT4 Operational Control Center (CMP)

NASA Technical Reports Server (NTRS)

Zaouche, G.

1993-01-01

CNES(F) is responsible for the development of a new generation of Operational Control Center (CMP) which will operate the new heliosynchronous remote sensing satellite (SPOT4). This Operational Control Center takes large benefit from the experience of the first generation of control center and from the recent advances in computer technology and standards. The CMP is designed for operating two satellites all the same time with a reduced pool of controllers. The architecture of this CMP is simple, robust, and flexible, since it is based on powerful distributed workstations interconnected through an Ethernet LAN. The application software uses modern and formal software engineering methods, in order to improve quality and reliability, and facilitate maintenance. This software is table driven so it can be easily adapted to other operational needs. Operation tasks are automated to the maximum extent, so that it could be possible to operate the CMP automatically with very limited human interference for supervision and decision making. This paper provides an overview of the SPOTS mission and associated ground segment. It also details the CMP, its functions, and its software and hardware architecture.

Preliminary Report on Mission Design and Operations for Critical Events

NASA Technical Reports Server (NTRS)

Hayden, Sandra C.; Tumer, Irem

2005-01-01

Mission-critical events are defined in the Jet Propulsion Laboratory s Flight Project Practices as those sequences of events which must succeed in order to attain mission goals. These are dependent on the particular operational concept and design reference mission, and are especially important when committing to irreversible events. Critical events include main engine cutoff (MECO) after launch; engine cutoff or parachute deployment on entry, descent, and landing (EDL); orbital insertion; separation of payload from vehicle or separation of booster segments; maintenance of pointing accuracy for power and communication; and deployment of solar arrays and communication antennas. The purpose of this paper is to report on the current practices in handling mission-critical events in design and operations at major NASA spaceflight centers. The scope of this report includes NASA Johnson Space Center (JSC), NASA Goddard Space Flight Center (GSFC), and NASA Jet Propulsion Laboratory (JPL), with staff at each center consulted on their current practices, processes, and procedures.

Mission Operations Directorate - Success Legacy of the Space Shuttle Program

NASA Technical Reports Server (NTRS)

Azbell, Jim

2010-01-01

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.

Mission Operations Directorate - Success Legacy of the Space Shuttle Program

NASA Technical Reports Server (NTRS)

Azbell, James A.

2011-01-01

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.

Carrington-L5: The UK/US Operational Space Weather Monitoring Mission

NASA Astrophysics Data System (ADS)

Trichas, Markos; Gibbs, Mark; Harrison, Richard; Green, Lucie; Eastwood, Jonathan; Bentley, Bob; Bisi, Mario; Bogdanova, Yulia; Davies, Jackie; D'Arrigo, Paolo; Eyles, Chris; Fazakerley, Andrew; Hapgood, Mike; Jackson, David; Kataria, Dhiren; Monchieri, Emanuele; Windred, Phil

2015-06-01

Airbus Defence and Space (UK) has carried out a study to investigate the possibilities for an operational space weather mission, in collaboration with the Met Office, RAL, MSSL and Imperial College London. The study looked at the user requirements for an operational mission, a model instrument payload, and a mission/spacecraft concept. A particular focus is cost effectiveness and timelineness of the data, suitable for 24/7 operational forecasting needs. We have focussed on a mission at L5 assuming that a mission to L1 will already occur, on the basis that L5 (Earth trailing) offers the greatest benefit for the earliest possible warning on hazardous SWE events and the most accurate SWE predictions. The baseline payload has been selected to cover all UK Met Office/NOAA's users priorities for L5 using instruments with extensive UK/US heritage, consisting of: heliospheric imager, coronograph, magnetograph, magnetometer, solar wind analyser and radiation monitor. The platform and subsystems are based on extensive re-use from past Airbus Defence and Space spacecraft to minimize the development cost and a Falcon-9 launcher has been selected on the same basis. A schedule analysis shows that the earliest launch could be achieved by 2020, assuming Phase A kick-off in 2015-2016. The study team have selected the name "Carrington" for the mission, reflecting the UK's proud history in this domain.

IMP mission

NASA Technical Reports Server (NTRS)

1972-01-01

The program requirements and operations requirements for the IMP mission are presented. The satellite configuration is described and the missions are analyzed. The support equipment, logistics, range facilities, and responsibilities of the launching organizations are defined. The systems for telemetry, communications, satellite tracking, and satellite control are identified.

The Mission Operations Planning Assistant

NASA Technical Reports Server (NTRS)

Schuetzle, James G.

1987-01-01

The Mission Operations Planning Assistant (MOPA) is a knowledge-based system developed to support the planning and scheduling of instrument activities on the Upper Atmospheric Research Satellite (UARS). The MOPA system represents and maintains instrument plans at two levels of abstraction in order to keep plans comprehensible to both UARS Principal Investigators and Command Management personnel. The hierarchical representation of plans also allows MOPA to automatically create detailed instrument activity plans from which spacecraft command loads may be generated. The MOPA system was developed on a Symbolics 3640 computer using the ZetaLisp and ART languages. MOPA's features include a textual and graphical interface for plan inspection and modification, recognition of instrument operational constraint violations during the planning process, and consistency maintenance between the different planning levels. This paper describes the current MOPA system.

The mission operations planning assistant

NASA Technical Reports Server (NTRS)

Schuetzle, James G.

1987-01-01

The Mission Operations Planning Assistant (MOPA) is a knowledge-based system developed to support the planning and scheduling of instrument activities on the Upper Atmospheric Research Satellite (UARS). The MOPA system represents and maintains instrument plans at two levels of abstraction in order to keep plans comprehensible to both UARS Prinicpal Investigators and Command Management personnel. The hierarchical representation of plans also allows MOPA to automatically create detailed instrument activity plans from which spacecraft command loads may be generated. The MOPA system was developed on a Symbolics 3640 computer using the ZETALISP and ART languages. MOPA's features include a textual and graphical interface for plan inspection and modification, recognition of instrument operational constraint violations during the planning process, and consistency maintenance between the different planning levels. This paper describes the current MOPA system.

Casualty Risk Assessment Controlled Re-Entry of EPS - Ariane 5ES - ATV Mission

NASA Astrophysics Data System (ADS)

Arnal, M.-H.; Laine, N.; Aussilhou, C.

2012-01-01

To fulfil its mission of compliance check to the French Space Operations Act, CNES has developed ELECTRA© tool in order to estimate casualty risk induced by a space activity (like rocket launch, controlled or un-controlled re-entry on Earth of a space object). This article describes the application of such a tool for the EPS controlled re-entry during the second Ariane 5E/S flight (Johannes Kepler mission has been launched in February 2011). EPS is the Ariane 5E/S upper composite which is de-orbited from a 260 km circular orbit after its main mission (release of the Automated Transfer Vehicle - ATV). After a brief description of the launcher, the ATV-mission and a description of all the failure cases taken into account in the mission design (which leads to "back-up scenarios" into the flight software program), the article will describe the steps which lead to the casualty risk assessment (in case of failure) with ELECTRA©. In particular, the presence on board of two propulsive means of de-orbiting (main engine of EPS, and 4 ACS longitudinal nozzles in case of main engine failure or exhaustion) leads to a low remaining casualty risk.

The MAP Autonomous Mission Control System

NASA Technical Reports Server (NTRS)

Breed, Juile; Coyle, Steven; Blahut, Kevin; Dent, Carolyn; Shendock, Robert; Rowe, Roger

2000-01-01

The Microwave Anisotropy Probe (MAP) mission is the second mission in NASA's Office of Space Science low-cost, Medium-class Explorers (MIDEX) program. The Explorers Program is designed to accomplish frequent, low cost, high quality space science investigations utilizing innovative, streamlined, efficient management, design and operations approaches. The MAP spacecraft will produce an accurate full-sky map of the cosmic microwave background temperature fluctuations with high sensitivity and angular resolution. The MAP spacecraft is planned for launch in early 2001, and will be staffed by only single-shift operations. During the rest of the time the spacecraft must be operated autonomously, with personnel available only on an on-call basis. Four (4) innovations will work cooperatively to enable a significant reduction in operations costs for the MAP spacecraft. First, the use of a common ground system for Spacecraft Integration and Test (I&T) as well as Operations. Second, the use of Finite State Modeling for intelligent autonomy. Third, the integration of a graphical planning engine to drive the autonomous systems without an intermediate manual step. And fourth, the ability for distributed operations via Web and pager access.

STS-105 coverage of Mission Control Center employees in the WFCR & BFCR

NASA Image and Video Library

2003-03-25

JSC2001-E-25131 (16 August 2001) --- ISS flight director Mark Ferring (seated), assembly checkout officer (ACO) Jim Ruhnke and astronaut Stephanie D. Wilson, ISS spacecraft communicator (CAPCOM), discuss the progress of the extravehicular activities at their consoles in the station flight control room (BFCR) in Houston’s Mission Control Center (MCC). Operations support officer (OSO) Ted Kenny is in the background participating in the discussion over the voice loops. At the time this photo was taken, mission specialists Daniel T. Barry and Patrick G. Forrester were performing the first of two scheduled space walks during Discovery’s voyage to the International Space Station (ISS).

Space Ops 2002: Bringing Space Operations into the 21st Century. Track 3: Operations, Mission Planning and Control. 2nd Generation Reusable Launch Vehicle-Concepts for Flight Operations

NASA Technical Reports Server (NTRS)

Hagopian, Jeff

2002-01-01

performed by crew and ground controllers. This experience has also identified the need for new approaches to staffing and training for both crew and ground controllers. This paper provides a brief overview of the mission capabilities provided by the 2nd Gen RLV, a description of NASA's approach to developing the 2nd Gen RLV, a discussion of operations concepts, and a list of challenges to implementing those concepts.

Reconfigurable Software for Mission Operations

NASA Technical Reports Server (NTRS)

Trimble, Jay

2014-01-01

We developed software that provides flexibility to mission organizations through modularity and composability. Modularity enables removal and addition of functionality through the installation of plug-ins. Composability enables users to assemble software from pre-built reusable objects, thus reducing or eliminating the walls associated with traditional application architectures and enabling unique combinations of functionality. We have used composable objects to reduce display build time, create workflows, and build scenarios to test concepts for lunar roving operations. The software is open source, and may be downloaded from https:github.comnasamct.

Lewis Wooten, manager of the Mission Operations Laboratory

NASA Image and Video Library

2015-07-20

LEWIS WOOTEN MANAGES THE MISSION OPERATIONS LABORATORY. MORE THAN 1600 INVESTIGATIONS AND STUDENT EXPERIMENTS FOR OVER 80 COUNTRIES HAVE BEEN COMPLETED WITH THE HELP OF WOOTEN'S TEAM AT NASA'S MARSHALL SPACE FLIGHT CENTER IN HUNTSVILLE, ALABAMA.

Mission operations update for the restructured Earth Observing System (EOS) mission

NASA Technical Reports Server (NTRS)

Kelly, Angelita Castro; Chang, Edward S.

1993-01-01

The National Aeronautics and Space Administration's (NASA) Earth Observing System (EOS) will provide a comprehensive long term set of observations of the Earth to the Earth science research community. The data will aid in determining global changes caused both naturally and through human interaction. Understanding man's impact on the global environment will allow sound policy decisions to be made to protect our future. EOS is a major component of the Mission to Planet Earth program, which is NASA's contribution to the U.S. Global Change Research Program. EOS consists of numerous instruments on multiple spacecraft and a distributed ground system. The EOS Data and Information System (EOSDIS) is the major ground system developed to support EOS. The EOSDIS will provide EOS spacecraft command and control, data processing, product generation, and data archival and distribution services for EOS spacecraft. Data from EOS instruments on other Earth science missions (e.g., Tropical Rainfall Measuring Mission (TRMM)) will also be processed, distributed, and archived in EOSDIS. The U.S. and various International Partners (IP) (e.g., the European Space Agency (ESA), the Ministry of International Trade and Industry (MITI) of Japan, and the Canadian Space Agency (CSA)) participate in and contribute to the international EOS program. The EOSDIS will also archive processed data from other designated NASA Earth science missions (e.g., UARS) that are under the broad umbrella of Mission to Planet Earth.

Open Source Next Generation Visualization Software for Interplanetary Missions

NASA Technical Reports Server (NTRS)

Trimble, Jay; Rinker, George

2016-01-01

Mission control is evolving quickly, driven by the requirements of new missions, and enabled by modern computing capabilities. Distributed operations, access to data anywhere, data visualization for spacecraft analysis that spans multiple data sources, flexible reconfiguration to support multiple missions, and operator use cases, are driving the need for new capabilities. NASA's Advanced Multi-Mission Operations System (AMMOS), Ames Research Center (ARC) and the Jet Propulsion Laboratory (JPL) are collaborating to build a new generation of mission operations software for visualization, to enable mission control anywhere, on the desktop, tablet and phone. The software is built on an open source platform that is open for contributions (http://nasa.github.io/openmct).

NASA Mission Operations Directorate Preparations for the COTS Visiting Vehicles

NASA Technical Reports Server (NTRS)

Shull, Sarah A.; Peek, Kenneth E.

2011-01-01

With the retirement of the Space Shuttle looming, a series of new spacecraft is under development to assist in providing for the growing logistical needs of the International Space Station (ISS). Two of these vehicles are being built under a NASA initiative known as the Commercial Orbital Transportation Services (COTS) program. These visiting vehicles ; Space X s Dragon and Orbital Science Corporation s Cygnus , are to be domestically produced in the United States and designed to add to the capabilities of the Russian Progress and Soyuz workhorses, the European Automated Transfer Vehicle (ATV) and the Japanese H-2 Transfer Vehicle (HTV). Most of what is known about the COTS program has focused on the work of Orbital and SpaceX in designing, building, and testing their respective launch and cargo vehicles. However, there is also a team within the Mission Operations Directorate (MOD) at NASA s Johnson Space Center working with their operational counterparts in these companies to provide operational safety oversight and mission assurance via the development of operational scenarios and products needed for these missions. Ensuring that the operational aspect is addressed for the initial demonstration flights of these vehicles is the topic of this paper. Integrating Dragon and Cygnus into the ISS operational environment has posed a unique challenge to NASA and their partner companies. This is due in part to the short time span of the COTS program, as measured from initial contract award until first launch, as well as other factors that will be explored in the text. Operational scenarios and products developed for each COTS vehicle will be discussed based on the following categories: timelines, on-orbit checkout, ground documentation, crew procedures, software updates and training materials. Also addressed is an outline of the commonalities associated with the operations for each vehicle. It is the intent of the authors to provide their audience with a better

View of Mission Control Center during the Apollo 13 emergency return

NASA Image and Video Library

1970-04-16

S70-35369 (16 April 1970) --- Discussion in the Mission Operations Control Room (MOCR) dealing with the Apollo 13 crewmen during their final day in space. From left to right are Glynn S. Lunney, Shift 4 flight director; Gerald D. Griffin, Shift 2 flight director; astronaut James A. McDivitt, manager, Apollo Spacecraft Program, MSC; Dr. Donald K. Slayton, director of Flight Crew Operations, MSC; and Dr. Willard R. Hawkins, M.D., Shift 1 flight surgeon.

Candidate Mission from Planet Earth control and data delivery system architecture

NASA Technical Reports Server (NTRS)

Shapiro, Phillip; Weinstein, Frank C.; Hei, Donald J., Jr.; Todd, Jacqueline

1992-01-01

Using a structured, experienced-based approach, Goddard Space Flight Center (GSFC) has assessed the generic functional requirements for a lunar mission control and data delivery (CDD) system. This analysis was based on lunar mission requirements outlined in GSFC-developed user traffic models. The CDD system will facilitate data transportation among user elements, element operations, and user teams by providing functions such as data management, fault isolation, fault correction, and link acquisition. The CDD system for the lunar missions must not only satisfy lunar requirements but also facilitate and provide early development of data system technologies for Mars. Reuse and evolution of existing data systems can help to maximize system reliability and minimize cost. This paper presents a set of existing and currently planned NASA data systems that provide the basic functionality. Reuse of such systems can have an impact on mission design and significantly reduce CDD and other system development costs.

A real-time navigation monitoring expert system for the Space Shuttle Mission Control Center

NASA Technical Reports Server (NTRS)

Wang, Lui; Fletcher, Malise

1993-01-01

The ONAV (Onboard Navigation) Expert System has been developed as a real time console assistant for use by ONAV flight controllers in the Mission Control Center at the Johnson Space Center. This expert knowledge based system is used to monitor the Space Shuttle onboard navigation system, detect faults, and advise flight operations personnel. This application is the first knowledge-based system to use both telemetry and trajectory data from the Mission Operations Computer (MOC). To arrive at this stage, from a prototype to real world application, the ONAV project has had to deal with not only AI issues but operating environment issues. The AI issues included the maturity of AI languages and the debugging tools, verification, and availability, stability and size of the expert pool. The environmental issues included real time data acquisition, hardware suitability, and how to achieve acceptance by users and management.

The OSIRIS-REx Asteroid Sample Return Mission Operations Design

NASA Technical Reports Server (NTRS)

Gal-Edd, Jonathan S.; Cheuvront, Allan

2015-01-01

OSIRIS-REx is an acronym that captures the scientific objectives: Origins, Spectral Interpretation, Resource Identification, and Security-Regolith Explorer. OSIRIS-REx will thoroughly characterize near-Earth asteroid Bennu (Previously known as 1019551999 RQ36). The OSIRIS-REx Asteroid Sample Return Mission delivers its science using five instruments and radio science along with the Touch-And-Go Sample Acquisition Mechanism (TAGSAM). All of the instruments and data analysis techniques have direct heritage from flown planetary missions. The OSIRIS-REx mission employs a methodical, phased approach to ensure success in meeting the mission's science requirements. OSIRIS-REx launches in September 2016, with a backup launch period occurring one year later. Sampling occurs in 2019. The departure burn from Bennu occurs in March 2021. On September 24, 2023, the Sample Return Capsule (SRC) lands at the Utah Test and Training Range (UTTR). Stardust heritage procedures are followed to transport the SRC to Johnson Space Center, where the samples are removed and delivered to the OSIRIS-REx curation facility. After a six-month preliminary examination period the mission will produce a catalog of the returned sample, allowing the worldwide community to request samples for detailed analysis. Traveling and returning a sample from an Asteroid that has not been explored before requires unique operations consideration. The Design Reference Mission (DRM) ties together spacecraft, instrument and operations scenarios. Asteroid Touch and Go (TAG) has various options varying from ground only to fully automated (natural feature tracking). Spacecraft constraints such as thermo and high gain antenna pointing impact the timeline. The mission is sensitive to navigation errors, so a late command update has been implemented. The project implemented lessons learned from other "small body" missions. The key lesson learned was 'expect the unexpected' and implement planning tools early in the lifecycle

Deep Space Habitat Concept of Operations for Extended Duration Transit Missions

NASA Technical Reports Server (NTRS)

Hoffman, Stephen J.; Toups, Larry

2012-01-01

NASA's Capability-Driven Framework (CDF) describes an approach for progressively extending human exploration missions farther into the Solar System for longer periods of time as allowed by developments in technology and spacecraft systems. Within this framework design reference missions (DRMs) targeted for several specific destinations are being used to assess different combinations of vehicles, operations, and advanced technologies to help understand which combination will best support expanded human exploration both efficiently and sustainably. Several of the identified destinations have been found to require missions with a round trip duration exceeding one year. These mission durations exceed the capabilities of current human-rated spacecraft if resupply from Earth is not possible. This makes the design of an efficient and reliable Deep Space Habitat (DSH) critical for reaching these destinations. The paper will describe the current understanding of DSH capabilities and functions that must be exhibited by any future habitat design for these missions. This description of the DSH is presented in the form of a concept of operation, which focuses on the functions that any DSH must provide, as opposed to a specific DSH design concept. Development of a concept of operations, based on DRM features, provides a common basis for assessing the viability of design concepts incorporating differing configurations and technologies. A study team with representation from several NASA Centers and relevant engineering and scientific disciplines collaborated to develop this DSH concept of operations for the transit phases of these missions. The transit phase of a mission is defined as the time after leaving Earth but before arrival at the destination and the time after leaving the destination but before arriving back at Earth. These transit phases were found to have many common features across all of the destinations being assessed for the CDF and thus arguing for a common concept

Design Considerations for Spacecraft Operations During Uncrewed Dormant Phases of Human Exploration Missions

NASA Technical Reports Server (NTRS)

Williams-Byrd, Julie; Antol, Jeff; Jefferies, Sharon; Goodliff, Kandyce; Williams, Phillip; Ambrose, Rob; Sylvester, Andre; Anderson, Molly; Dinsmore, Craig; Hoffman, Stephen;

Constraint and Flight Rule Management for Space Mission Operations

NASA Technical Reports Server (NTRS)

Barreiro, J.; Chachere, J.; Frank, J.; Bertels, C.; Crocker, A.

2010-01-01

The exploration of space is one of the most fascinating domains to study from a human factors perspective. Like other complex work domains such as aviation (Pritchett and Kim, 2008), air traffic management (Durso and Manning, 2008), health care (Morrow, North, and Wickens, 2006), homeland security (Cooke and Winner, 2008), and vehicle control (Lee, 2006), space exploration is a large-scale sociotechnical work domain characterized by complexity, dynamism, uncertainty, and risk in real-time operational contexts (Perrow, 1999; Woods et al, 1994). Nearly the entire gamut of human factors issues - for example, human-automation interaction (Sheridan and Parasuraman, 2006), telerobotics, display and control design (Smith, Bennett, and Stone, 2006), usability, anthropometry (Chaffin, 2008), biomechanics (Marras and Radwin, 2006), safety engineering, emergency operations, maintenance human factors, situation awareness (Tenney and Pew, 2006), crew resource management (Salas et al., 2006), methods for cognitive work analysis (Bisantz and Roth, 2008) and the like -- are applicable to astronauts, mission control, operational medicine, Space Shuttle manufacturing and assembly operations, and space suit designers as they are in other work domains (e.g., Bloomberg, 2003; Bos et al, 2006; Brooks and Ince, 1992; Casler and Cook, 1999; Jones, 1994; McCurdy et al, 2006; Neerincx et aI., 2006; Olofinboba and Dorneich, 2005; Patterson, Watts-Perotti and Woods, 1999; Patterson and Woods, 2001; Seagull et ai, 2007; Sierhuis, Clancey and Sims, 2002). The human exploration of space also has unique challenges of particular interest to human factors research and practice. This chapter provides an overview of those issues and reports on some of the latest research results as well as the latest challenges still facing the field.

Mission control activity during STS-61 EVA

NASA Image and Video Library

1993-12-07

Flight controller Susan P. Rainwater observes as two astronauts work through a lengthy period of extravehicular activity (EVA) in the cargo bay of the Earth-looking Space Shuttle Endeavour. Rainwater's EVA console was one of Mission Control's busiest during this eleven-day Hubble Space Telescope (HST) servicing mission in Earth orbit.

Mission Design and Concept of Operations of a 6U CubeSat Mission for Proximity Operations and RSO Imaging

DTIC Science & Technology

2013-05-29

Design and Concept of Operations of a 6U Cube Sat Mission for NIA Proximity Oper111ions and RSO Imaging 5b. GRANT NUMBER NIA 5c. PROGRAM ELEMENT...NUMBER NIA 6. AUTHOR(S) 5d. PROJECT NUMBER B. Udrea, M. Nayak, M. Ryle, N. Martini, S. Gillespie, T. Grande, S. Caicedo, S. NIA Wilette, A. Baba...K. , Harri s, J. DiGregorio, S. Salzburger, P. Patel , A. Huang 5e. TASK NUMBER NIA 5f. WORK UNIT NUMBER NIA T. PERFORMING ORGANIZATION NAME(S

Mission operations concepts for Earth Observing System (EOS)

NASA Technical Reports Server (NTRS)

Kelly, Angelita C.; Taylor, Thomas D.; Hawkins, Frederick J.

1991-01-01

Mission operation concepts are described which are being used to evaluate and influence space and ground system designs and architectures with the goal of achieving successful, efficient, and cost-effective Earth Observing System (EOS) operations. Emphasis is given to the general characteristics and concepts developed for the EOS Space Measurement System, which uses a new series of polar-orbiting observatories. Data rates are given for various instruments. Some of the operations concepts which require a total system view are also examined, including command operations, data processing, data accountability, data archival, prelaunch testing and readiness, launch, performance monitoring and assessment, contingency operations, flight software maintenance, and security.