Object-oriented technologies in a multi-mission data system

NASA Technical Reports Server (NTRS)

Murphy, Susan C.; Miller, Kevin J.; Louie, John J.

1993-01-01

The Operations Engineering Laboratory (OEL) at JPL is developing new technologies that can provide more efficient and productive ways of doing business in flight operations. Over the past three years, we have worked closely with the Multi-Mission Control Team to develop automation tools, providing technology transfer into operations and resulting in substantial cost savings and error reduction. The OEL development philosophy is characterized by object-oriented design, extensive reusability of code, and an iterative development model with active participation of the end users. Through our work, the benefits of object-oriented design became apparent for use in mission control data systems. Object-oriented technologies and how they can be used in a mission control center to improve efficiency and productivity are explained. The current research and development efforts in the JPL Operations Engineering Laboratory are also discussed to architect and prototype a new paradigm for mission control operations based on object-oriented concepts.

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.

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.

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.

The Earth Science Afternoon Constellation: Preparing for Autonomous but Coordinated Operations

NASA Technical Reports Server (NTRS)

Case, Warren; Kelly, Angelita C.; Work, Kevin; Guit, William

2005-01-01

This paper describes how the challenges of coordinating the autonomous operations of geographically dispersed mission control centers for several small and large satellites are being overcome. The Earth Science Afternoon Constellation, also referred to as the "A-Train", is an international grouping of five NASA satellites (two major NASA EOS missions and three NASA/Earth System Science Pathfinder missions) and one French satellite orbiting in close proximity. This grouping of satellites provides scientists with the opportunity to perform coincident observations using data from two or more instruments on various satellites with measurements taken at approximately the same time. Three of the six missions are currently on-orbit, with the two missions expected to join the constellation later this year and one mission in 2007. The operational challenges are daunting for several reasons. There are several Mission Control Centers (widely separated on two continents), operating autonomously under tight budget constraints. All of the Mission Control Centers have reasons to be concerned about safety while flying in close proximity to other satellites, but most Centers did not have the resources or the desire to address this concern alone - the interfaces are too numerous and anticipated operations too costly. Clearly, an efficient approach was needed. This paper describes the steps taken to make this Earth science constellation a reality. Agreements were forged to allow the Mission Control Centers to maintain their autonomy, while ensuring their satellite's safety. Each member mission in the constellation operates independently in accordance with its own mission requirements, but the member missions have agreed to coordinate their operations, i.e., orbital positions and control to ensure the safety of the entire constellation. A centralized system was developed at NASA Goddard Space Flight Center to collect, analyze, and distribute ephemeris data used by each of the mission teams to determine the positions of the satellites in the constellation. The system issues warnings regarding possible dangerous configurations, eliminating the need for redundant capabilities at each Mission Control Center. On-orbit contingency situations were identified and analyzed; agreements were reached in advance of contingency operations to ensure that coordination between the Mission Control Centers can be handled expeditiously and fairly. In this manner, recovery from anomalous situations can be more quickly realized, thereby increasing the science return and reducing costs. The process used to develop these contingency procedures and the systems used to facilitate the contingency resolution are described as well.

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.

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.

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).

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.

An Open Specification for Space Project Mission Operations Control Architectures

NASA Technical Reports Server (NTRS)

Hooke, A.; Heuser, W. R.

1995-01-01

An 'open specification' for Space Project Mission Operations Control Architectures is under development in the Spacecraft Control Working Group of the American Institute for Aeronautics and Astro- nautics. This architecture identifies 5 basic elements incorporated in the design of similar operations systems: Data, System Management, Control Interface, Decision Support Engine, & Space Messaging Service.

Development of a Space Station Operations Management System

NASA Technical Reports Server (NTRS)

Brandli, A. E.; Mccandless, W. T.

1988-01-01

To enhance the productivity of operations aboard the Space Station, a means must be provided to augment, and frequently to supplant, human effort in support of mission operations and management, both on the ground and onboard. The Operations Management System (OMS), under development at the Johnson Space Center, is one such means. OMS comprises the tools and procedures to facilitate automation of station monitoring, control, and mission planning tasks. OMS mechanizes, and hence rationalizes, execution of tasks traditionally performed by mission planners, the mission control center team, onboard System Management software, and the flight crew.

Development of a Space Station Operations Management System

NASA Astrophysics Data System (ADS)

Brandli, A. E.; McCandless, W. T.

To enhance the productivity of operations aboard the Space Station, a means must be provided to augment, and frequently to supplant, human effort in support of mission operations and management, both on the ground and onboard. The Operations Management System (OMS), under development at the Johnson Space Center, is one such means. OMS comprises the tools and procedures to facilitate automation of station monitoring, control, and mission planning tasks. OMS mechanizes, and hence rationalizes, execution of tasks traditionally performed by mission planners, the mission control center team, onboard System Management software, and the flight crew.

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.

Apollo Soyuz mission planning and operations

NASA Technical Reports Server (NTRS)

Frank, M. P., III

1976-01-01

The paper describes the Apollo Soyuz project from the points of view of working group organization, mission plan definition, joint operations concept, and mission preparation. The concept for joint operations considered contingency situations as well as nominal operations. Preparations for the joint flight included cooperative tracking tests and combined training of the flight crews and mission control personnel.

Mission Manager Area of the Spacelab Payload Operations Control Center (SL POCC)

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. Pictured is Jack Jones in the Mission Manager Area.

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.

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).

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.

Crew-Centered Operations: What HAL 9000 Should Have Been

NASA Technical Reports Server (NTRS)

Korsmeyer, David J.; Clancy, Daniel J.; Crawford, James M.; Drummond, Mark E.

2005-01-01

To date, manned space flight has maintained the locus of control for the mission on the ground. Mission control performs tasks such as activity planning, system health management, resource allocation, and astronaut health monitoring. Future exploration missions require the locus of control to shift to on-board due light speed constraints and potential loss of communication. The lunar campaign must begin to utilize a shared control approach to validate and understand the limitations of the technology allowing astronauts to oversee and direct aspects of operation that require timely decision making. Crew-centered Operations require a system-level approach that integrates multiple technologies together to allow a crew-prime concept of operations. This paper will provide an overview of the driving mission requirements, highlighting the limitations of existing approaches to mission operations and identifying the critical technologies necessary to enable a crew-centered mode of operations. The paper will focus on the requirements, trade spaces, and concepts for fulfillment of this capability. The paper will provide a broad overview of relevant technologies including: Activity Planning and Scheduling; System Monitoring; Repair and Recovery; Crew Work Practices.

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.

Flight Operations reunion for the Apollo 11 20th anniversary of the first manned lunar landing

NASA Technical Reports Server (NTRS)

1989-01-01

The following major areas are presented: (1) the Apollo years; (2) official flight control manning list for Apollo 11; (3) original mission control emblem; (4) foundations of flight control; (5) Apollo-11 20th anniversary program and events; (6) Apollo 11 mission operations team certificate; (7) Apollo 11 mission summary (timeline); and (8) Apollo flight control team photographs and biographies.

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.

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.

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.

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.

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.

Shared mission operations concept

NASA Technical Reports Server (NTRS)

Spradlin, Gary L.; Rudd, Richard P.; Linick, Susan H.

1994-01-01

Historically, new JPL flight projects have developed a Mission Operations System (MOS) as unique as their spacecraft, and have utilized a mission-dedicated staff to monitor and control the spacecraft through the MOS. NASA budgetary pressures to reduce mission operations costs have led to the development and reliance on multimission ground system capabilities. The use of these multimission capabilities has not eliminated an ongoing requirement for a nucleus of personnel familiar with a given spacecraft and its mission to perform mission-dedicated operations. The high cost of skilled personnel required to support projects with diverse mission objectives has the potential for significant reduction through shared mission operations among mission-compatible projects. Shared mission operations are feasible if: (1) the missions do not conflict with one another in terms of peak activity periods, (2) a unique MOS is not required, and (3) there is sufficient similarity in the mission profiles so that greatly different skills would not be required to support each mission. This paper will further develop this shared mission operations concept. We will illustrate how a Discovery-class mission would enter a 'partner' relationship with the Voyager Project, and can minimize MOS development and operations costs by early and careful consideration of mission operations requirements.

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.

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.

Verification and Implementation of Operations Safety Controls for Flight Missions

NASA Technical Reports Server (NTRS)

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

2010-01-01

There are several engineering disciplines, such as reliability, supportability, quality assurance, human factors, risk management, safety, etc. Safety is an extremely important engineering specialty within NASA, and the consequence involving a loss of crew is considered a catastrophic event. Safety is not difficult to achieve when properly integrated at the beginning of each space systems project/start of mission planning. The key is to ensure proper handling of safety verification throughout each flight/mission phase. Today, Safety and Mission Assurance (S&MA) operations engineers continue to conduct these flight product reviews across all open flight products. As such, these reviews help ensure that each mission is accomplished with safety requirements along with controls heavily embedded in applicable flight products. Most importantly, the S&MA operations engineers are required to look for important design and operations controls so that safety is strictly adhered to as well as reflected in the final flight product.

Operator Informational Needs for Multiple Autonomous Small Vehicles

NASA Technical Reports Server (NTRS)

Trujillo, Anna C.; Fan, Henry; Cross, Charles D.; Hempley, Lucas E.; Cichella, Venanzio; Puig-Navarro, Javier; Mehdi, Syed Bilal

2015-01-01

With the anticipated explosion of small unmanned aerial vehicles, it is highly likely that operators will be controlling fleets of autonomous vehicles. To fulfill the promise of autonomy, vehicle operators will not be concerned with manual control of the vehicle; instead, they will deal with the overall mission. Furthermore, the one operator to many vehicles is becoming a constant meme with various industries including package delivery, search and rescue, and utility companies. In order for an operator to concurrently control several vehicles, his station must look and behave very differently than the current ground control station instantiations. Furthermore, the vehicle will have to be much more autonomous, especially during non-normal operations, in order to accommodate the knowledge deficit or the information overload of the operator in charge of several vehicles. The expected usage increase of small drones requires presenting the operational information generated by a fleet of heterogeneous autonomous agents to an operator. NASA Langley Research Center's Autonomy Incubator has brought together researchers in various disciplines including controls, trajectory planning, systems engineering, and human factors to develop an integrated system to study autonomy issues. The initial human factors effort is focusing on mission displays that would give an operator the overall status of all autonomous agents involved in the current mission. This paper will discuss the specifics of the mission displays for operators controlling several vehicles.

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.

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 planning, and spacecraft design.

Operator procedure verification with a rapidly reconfigurable simulator

NASA Technical Reports Server (NTRS)

Iwasaki, Yumi; Engelmore, Robert; Fehr, Gary; Fikes, Richard

1994-01-01

Generating and testing procedures for controlling spacecraft subsystems composed of electro-mechanical and computationally realized elements has become a very difficult task. Before a spacecraft can be flown, mission controllers must envision a great variety of situations the flight crew may encounter during a mission and carefully construct procedures for operating the spacecraft in each possible situation. If, despite extensive pre-compilation of control procedures, an unforeseen situation arises during a mission, the mission controller must generate a new procedure for the flight crew in a limited amount of time. In such situations, the mission controller cannot systematically consider and test alternative procedures against models of the system being controlled, because the available simulator is too large and complex to reconfigure, run, and analyze quickly. A rapidly reconfigurable simulation environment that can execute a control procedure and show its effects on system behavior would greatly facilitate generation and testing of control procedures both before and during a mission. The How Things Work project at Stanford University has developed a system called DME (Device Modeling Environment) for modeling and simulating the behavior of electromechanical devices. DME was designed to facilitate model formulation and behavior simulation of device behavior including both continuous and discrete phenomena. We are currently extending DME for use in testing operator procedures, and we have built a knowledge base for modeling the Reaction Control System (RCS) of the space shuttle as a testbed. We believe that DME can facilitate design of operator procedures by providing mission controllers with a simulation environment that meets all these requirements.

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.

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.

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.

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.

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.

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.

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.

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

National Space Transportation System Reference. Volume 2: Operations

NASA Technical Reports Server (NTRS)

1988-01-01

An overview of the Space Transportation System is presented in which aspects of the program operations are discussed. The various mission preparation and prelaunch operations are described including astronaut selection and training, Space Shuttle processing, Space Shuttle integration and rollout, Complex 39 launch pad facilities, and Space Shuttle cargo processing. Also, launch and flight operations and space tracking and data acquisition are described along with the mission control and payload operations control center. In addition, landing, postlanding, and solid rocket booster retrieval operations are summarized. Space Shuttle program management is described and Space Shuttle mission summaries and chronologies are presented. A glossary of acronyms and abbreviations are provided.

Multi-team dynamics and distributed expertise in imission operations.

PubMed

Caldwell, Barrett S

2005-06-01

The evolution of space exploration has brought an increased awareness of the social and socio-technical issues associated with team performance and task coordination, both for the onboard astronauts and in mission control. Spaceflight operations create a unique environment in which to address classic group dynamics topics including communication, group process, knowledge development and sharing, and time-critical task performance. Mission operations in the early years of the 21st century have developed into a set of complex, multi-team task settings incorporating multiple mission control teams and flight crews interacting in novel ways. These more complex operational settings help highlight the emergence of a new paradigm of distributed supervisory coordination, and the need to consider multiple dimensions of expertise being supported and exchanged among team members. The creation of new mission profiles with very long-duration time scales (months, rather than days) for the International Space Station, as well as planned exploration missions to the Moon and Mars, emphasize fundamental distinctions from the 40 yr from Mercury to the Space Shuttle. Issues in distributed expertise and information flow in mission control settings from two related perspectives are described. A general conceptual view of knowledge sharing and task synchronization is presented within the context of the mission control environment. This conceptual presentation is supplemented by analysis of quasi-experimental data collected from actual flight controllers at NASA-Johnson Space Center, Houston, TX.

Attitude Determination and Control System Design for a 6U Cube Sat for Proximity Operations and Rendezvous

DTIC Science & Technology

2014-08-04

Resident Space Object Proximity Analysis and IMAging) mission is carried out by a 6U Cube Sat class satellite equipped with a warm gas propulsion system... mission . The ARAPAIMA (Application for Resident Space Object Proximity Analysis and IMAging) mission is carried out by a 6 U CubeSat class satellite...attitude determination and control subsystem (ADCS) (or a proximity operation and imaging satellite mission . The ARAP AI MA (Application for

CCSDS Spacecraft Monitor and Control Service Framework

NASA Technical Reports Server (NTRS)

Merri, Mario; Schmidt, Michael; Ercolani, Alessandro; Dankiewicz, Ivan; Cooper, Sam; Thompson, Roger; Symonds, Martin; Oyake, Amalaye; Vaughs, Ashton; Shames, Peter

2004-01-01

This CCSDS paper presents a reference architecture and service framework for spacecraft monitoring and control. It has been prepared by the Spacecraft Monitoring and Control working group of the CCSDS Mission Operations and Information Management Systems (MOIMS) area. In this context, Spacecraft Monitoring and Control (SM&C) refers to end-to-end services between on- board or remote applications and ground-based functions responsible for mission operations. The scope of SM&C includes: 1) Operational Concept: definition of an operational concept that covers a set of standard operations activities related to the monitoring and control of both ground and space segments. 2) Core Set of Services: definition of an extensible set of services to support the operational concept together with its information model and behaviours. This includes (non exhaustively) ground systems such as Automatic Command and Control, Data Archiving and Retrieval, Flight Dynamics, Mission Planning and Performance Evaluation. 3) Application-layer information: definition of the standard information set to be exchanged for SM&C purposes.

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.

Efficiency Management in Spaceflight Systems

NASA Technical Reports Server (NTRS)

Murphy, Karen

2016-01-01

Efficiency in spaceflight is often approached as “faster, better, cheaper – pick two”. The high levels of performance and reliability required for each mission suggest that planners can only control for two of the three. True efficiency comes by optimizing a system across all three parameters. The functional processes of spaceflight become technical requirements on three operational groups during mission planning: payload, vehicle, and launch operations. Given the interrelationships among the functions performed by the operational groups, optimizing function resources from one operational group to the others affects the efficiency of those groups and therefore the mission overall. This paper helps outline this framework and creates a context in which to understand the effects of resource trades on the overall system, improving the efficiency of the operational groups and the mission as a whole. This allows insight into and optimization of the controlling factors earlier in the mission planning stage.

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.

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 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.

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.

Low-Cost Mission Operations

NASA Technical Reports Server (NTRS)

Squibb, G. F.; Heftman, K.

1996-01-01

This paper discusses the transition between traditional planetary missions (requiring constant operational control and limited in size only by booster capability) and the cheaper missions of the New Millennium spacecraft, which will be smaller and will have a great deal of autonomy.

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.

Space Students Visit MSFC During STS-35 Astro-1 Mission

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. This photo is of Space classroom students in the Discovery Optics Lab at MSFC during STS-35, ASTRO-1 mission payload operations.

A Simulation Base Investigation of High Latency Space Systems Operations

NASA Technical Reports Server (NTRS)

Li, Zu Qun; Crues, Edwin Z.; Bielski, Paul; Moore, Michael

2017-01-01

NASA's human space program has developed considerable experience with near Earth space operations. Although NASA has experience with deep space robotic missions, NASA has little substantive experience with human deep space operations. Even in the Apollo program, the missions lasted only a few weeks and the communication latencies were on the order of seconds. Human missions beyond the relatively close confines of the Earth-Moon system will involve missions with durations measured in months and communications latencies measured in minutes. To minimize crew risk and to maximize mission success, NASA needs to develop a better understanding of the implications of these types of mission durations and communication latencies on vehicle design, mission design and flight controller interaction with the crew. To begin to address these needs, NASA performed a study using a physics-based subsystem simulation to investigate the interactions between spacecraft crew and a ground-based mission control center for vehicle subsystem operations across long communication delays. The simulation, built with a subsystem modeling tool developed at NASA's Johnson Space Center, models the life support system of a Mars transit vehicle. The simulation contains models of the cabin atmosphere and pressure control system, electrical power system, drinking and waste water systems, internal and external thermal control systems, and crew metabolic functions. The simulation has three interfaces: 1) a real-time crew interface that can be use to monitor and control the vehicle subsystems; 2) a mission control center interface with data transport delays up to 15 minutes each way; 3) a real-time simulation test conductor interface that can be use to insert subsystem malfunctions and observe the interactions between the crew, ground, and simulated vehicle. The study was conducted at the 21st NASA Extreme Environment Mission Operations (NEEMO) mission between July 18th and Aug 3rd of year 2016. The NEEMO mission provides ideal conditions for this study with crew in the loop, an active control center, and real-time flow of high latency communications and data. NEEMO crew and ground support will work through procedures including activation of the transit vehicle power system, opening the hatch between the transit vehicle and a Mars ascent vehicle, transferring simulated crewmembers between vehicles, overcoming subsystem malfunctions, sending simulated crewmember on extra-vehicular activities, and other housekeeping activities. This study is enhancing the understanding of high latency operations and the advantages and disadvantages of different communication methods. It is also providing results that will help improve the design of simulation interfaces and inform the design of Mars transit vehicles.

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/product lifecycle - concept development, proposal preparation, and formulation. The VMOC-CE expands the application of the VSDE into the operations portion of the system lifecycle. It will enable meaningful and real-time collaboration regardless of the geographical distribution of project team members. Team members will be able to interact in satellite operations, specifically for resolving anomalies, through access to a desktop computer and the Internet. Mission Operations Management will be able to participate and monitor up to the minute status of anomalies or other mission operations issues. In this paper we present the VMOC-CE project, system capabilities, and technologies.

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

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.

An intelligent automated command and control system for spacecraft mission operations

NASA Technical Reports Server (NTRS)

Stoffel, A. William

1994-01-01

The Intelligent Command and Control (ICC) System research project is intended to provide the technology base necessary for producing an intelligent automated command and control (C&C) system capable of performing all the ground control C&C functions currently performed by Mission Operations Center (MOC) project Flight Operations Team (FOT). The ICC research accomplishments to date, details of the ICC, and the planned outcome of the ICC research, mentioned above, are discussed in detail.

NASA Goddard Space Flight Center

NASA Technical Reports Server (NTRS)

Carter, David; Wetzel, Scott

2000-01-01

The NASA SLR Operational Center is responsible for: 1) NASA SLR network control, sustaining engineering, and logistics; 2) ILRS mission operations; and 3) ILRS and NASA SLR data operations. NASA SLR network control and sustaining engineering tasks include technical support, daily system performance monitoring, system scheduling, operator training, station status reporting, system relocation, logistics and support of the ILRS Networks and Engineering Working Group. These activities ensure the NASA SLR systems are meeting ILRS and NASA mission support requirements. ILRS mission operations tasks include mission planning, mission analysis, mission coordination, development of mission support plans, and support of the ILRS Missions Working Group. These activities ensure than new mission and campaign requirements are coordinated with the ILRS. Global Normal Points (NP) data, NASA SLR FullRate (FR) data, and satellite predictions are managed as part of data operations. Part of this operation includes supporting the ILRS Data Formats and Procedures Working Group. Global NP data operations consist of receipt, format and data integrity verification, archiving and merging. This activity culminates in the daily electronic transmission of NP files to the CDDIS. Currently of all these functions are automated. However, to ensure the timely and accurate flow of data, regular monitoring and maintenance of the operational software systems, computer systems and computer networking are performed. Tracking statistics between the stations and the data centers are compared periodically to eliminate lost data. Future activities in this area include sub-daily (i.e., hourly) NP data management, more stringent data integrity tests, and automatic station notification of format and data integrity issues.

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.

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 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.

Around Marshall

NASA Image and Video Library

1990-12-07

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. This photo is of Space classroom students in the Discovery Optics Lab at MSFC during STS-35, ASTRO-1 mission payload operations.

Around Marshall

NASA Image and Video Library

1990-12-02

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 activity at the Operations Control Facility during the mission as Dr. Urban and Paul Whitehouse give a “thumbs up”.

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 approach to the design of operations systems

NASA Technical Reports Server (NTRS)

Chafin, Roy L.; Curran, Patrick S.

1993-01-01

The MultiMission Control Team (MMCT) consists of mission controllers which provides Real-Time operations support for the Mars Observer project. The Real-Time Operations task is to insure the integrity of the ground data system, to insure that the configuration is correct to support the mission, and to monitor the spacecraft for the Spacecraft Team. Operations systems are typically developed by adapting operations systems from previous projects. Problems tend to be solved empirically when they are either anticipated or observed in testing. This development method has worked in the past when time was available for extensive Ops testing. In the present NASA budget environment, a more cost conscious design approach has become necessary. Cost is a concern because operations is an ongoing, continuous activity. Reducing costs entails reducing staff. Reducing staffing levels potentially increases the risk of mission failure. Therefore, keeping track of the risk level is necessary.

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).

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.

Lunar and Mars Exploration: The Autonomy Factor

NASA Technical Reports Server (NTRS)

Rando, Cynthia M.; Schuh, Susan V.

2008-01-01

Long duration space flight crews have relied heavily on almost constant communication with ground control mission support. Ground control teams provide vehicle status and system monitoring, while offering near real time support for specific tasks, emergencies, and ensuring crew health and well being. With extended exploration goals to lunar and Mars outposts, real time communication with ground control teams and the ground s ability to conduct mission monitoring will be very limited compared to the resources provided to current International Space Station (ISS) crews. An operational shift toward more autonomy and a heavier reliance on the crew to monitor their vehicle and operations will be required for these future missions. NASA s future exploration endeavors and the subsequent increased autonomy will require a shift in crew skill composition, i.e. engineer, doctor, mission specialist etc. and lead to new training challenges and mission scenarios. Specifically, operational and design changes will be necessary in many areas including: Habitat Infrastructure and Support Systems, Crew Composition, Training, Procedures and Mission Planning. This paper will specifically address how to apply ISS lessons learned to further use ISS as a test bed to address decreased amounts of ground support to achieve full autonomous operations for lunar and Mars missions. Understanding these lessons learned and applying them to current operations will help to address the future impacts of increased crew autonomy for the lunar and Mars outposts and pave the way for success in increasingly longer mission durations.

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.

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 capabilities to support hot-standby system reconfiguration and machines and data resynchronisation following failures for all mission phases make them a good candidate for re-use by newer missions. Common methods and tools for requirements production, test plan production and problem tracking which are used by most of the other ESOC missions development teams in their daily work are also re-used without any changes. Finally conclusions are drawn about reusability in perspective with the latest state of the S1MCS and about benefits to other SCOS-2000 based "client" missions. Lessons learned for ESOC space missions (whether for mission control systems currently under development or up-and-coming space missions) and also related considerations for the wider space community are made, reflecting ESOC skills and expertise in mission operations and control.

Mission Operations Control Room Activities during STS-2 mission

NASA Technical Reports Server (NTRS)

1981-01-01

Mission Operations Control Room (MOCR) activities during STS-2 mission. President Ronald Reagan and Dr. Christopher C. Kraft, Jr., look toward the orbiter spotter on the projection plotter at the front of the MOCR. Also present are Astronaut Daniel C. Brandenstein, seated left, and NASA Administrator James M. Beggs standing left of center. In the foreground, Dr. Hans Mark, Deputy NASA Administrator, briefs Michael Deaver, Special Assistant to President Reagan (39504); President Reagan speaks to the STS-2 crew during the second day of their mission. On hand in MOCR were NASA Administrator James M. Beggs and Deputy Administrator Hans Mark (standing behind the president but mostly out of frame) and Dr. Kraft on the right. Eugene F. Kranz, Deputy Director of Flight Operations can be seen in the background seated at the Flight Operations Directorate (FOD) console. Also present is Astronaut Daniel C. Brandenstein, seated left, who turned the communications over to Mr. Reagan (39505).

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.

Promoting Crew Autonomy: Current Advances and Novel Techniques

NASA Technical Reports Server (NTRS)

Harris, Samantha

2017-01-01

Since the dawn of the era of human space flight, mission control centers around the world have played an integral role in guiding space travelers toward mission success. In the International Space Station (ISS) program, astronauts and cosmonauts have the benefit of near constant access to the expertise and resources within mission control, as well as lifeboat capability to quickly return to Earth if something were to go wrong. As we move into an era of longer duration missions to more remote locations, rapid and ready access to mission control on earth will no longer be feasible. To prepare for such missions, long duration crews must be prepared to operate more autonomously, and the mission control paradigm that has been successfully employed for decades must be re-examined. The team at NASA's Payload Operations and Integration Center (POIC) in Huntsville, Alabama is playing an integral role in the development of concepts for a more autonomous long duration crew of the future via research on the ISS.

HUT Data Inspected at Marshall Space Flight Center During the STS-35 Mission

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 activity of viewing HUT data in the Mission Manager Actions Room during the mission.

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.

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.

A Simulation Based Investigation of High Latency Space Systems Operations

NASA Technical Reports Server (NTRS)

Li, Zu Qun; Moore, Michael; Bielski, Paul; Crues, Edwin Z.

2017-01-01

This study was the first in a series of planned tests to use physics-based subsystem simulations to investigate the interactions between a spacecraft's crew and a ground-based mission control center for vehicle subsystem operations across long communication delays. The simulation models the life support system of a deep space habitat. It contains models of an environmental control and life support system, an electrical power system, an active thermal control systems, and crew metabolic functions. The simulation has three interfaces: 1) a real-time crew interface that can be use to monitor and control the subsystems; 2) a mission control center interface with data transport delays up to 15 minute each way; and 3) a real-time simulation test conductor interface used to insert subsystem malfunctions and observe the interactions between the crew, ground, and simulated vehicle. The study was conducted at the 21st NASA Extreme Environment Mission Operations (NEEMO) mission. The NEEMO crew and ground support team performed a number of relevant deep space mission scenarios that included both nominal activities and activities with system malfunctions. While this initial test sequence was focused on test infrastructure and procedures development, the data collected in the study already indicate that long communication delays have notable impacts on the operation of deep space systems. For future human missions beyond cis-lunar, NASA will need to design systems and support tools to meet these challenges. These will be used to train the crew to handle critical malfunctions on their own, to predict malfunctions and assist with vehicle operations. Subsequent more detailed and involved studies will be conducted to continue advancing NASA's understanding of space systems operations across long communications delays.

A Simulation Based Investigation of High Latency Space Systems Operations

NASA Technical Reports Server (NTRS)

Li, Zu Qun; Crues, Edwin Z.; Bielski, Paul; Moore, Michael

2017-01-01

This study was the first in a series of planned tests to use physics-based subsystem simulations to investigate the interactions between a spacecraft's crew and a ground-based mission control center for vehicle subsystem operations across long communication delays. The simulation models the life support system of a deep space habitat. It contains models of an environmental control and life support system, an electrical power system, an active thermal control system, and crew metabolic functions. The simulation has three interfaces: 1) a real-time crew interface that can be use to monitor and control the subsystems; 2) a mission control center interface with data transport delays up to 15 minute each way; and 3) a real-time simulation test conductor interface used to insert subsystem malfunctions and observe the interactions between the crew, ground, and simulated vehicle. The study was conducted at the 21st NASA Extreme Environment Mission Operations (NEEMO) mission. The NEEMO crew and ground support team performed a number of relevant deep space mission scenarios that included both nominal activities and activities with system malfunctions. While this initial test sequence was focused on test infrastructure and procedures development, the data collected in the study already indicate that long communication delays have notable impacts on the operation of deep space systems. For future human missions beyond cis-lunar, NASA will need to design systems and support tools to meet these challenges. These will be used to train the crew to handle critical malfunctions on their own, to predict malfunctions, and to assist with vehicle operations. Subsequent more detailed and involved studies will be conducted to continue advancing NASA's understanding of space systems operations across long communications delays.

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.

Debris/Ice/TPS Assessment and Integrated Photographic Analysis of Shuttle Mission STS-109

NASA Technical Reports Server (NTRS)

Oliu, Armando

2005-01-01

The Debris Team has developed and implemented measures to control damage from debris in the Shuttle operational environment and to make the control measures a part of routine launch flows. These measures include engineering surveillance during vehicle processing and closeout operations, facility and flight hardware inspections before and after launch, and photographic analysis of mission events. Photographic analyses of mission imagery from launch, on-orbit, and landing provide significant data in verifying proper operation of systems and evaluating anomalies. In addition to the Kennedy Space Center Photo/Video Analysis, reports from Johnson Space Center and Marshall Space Flight Center are also included in this document to provide an integrated assessment of the mission.

Debris/Ice/TPS Assessment and Integrated Photographic Analysis of Shuttle Mission STS-110

NASA Technical Reports Server (NTRS)

Oliu, Armando

2005-01-01

The Debris Team has developed and implemented measures to control damage from debris in the Shuttle operational environment and to make the control measures a part of routine launch flows. These measures include engineering surveillance during vehicle processing and closeout operations, facility and flight hardware inspections before and after launch, and photographic analysis of mission events. Photographic analyses of mission imagery from launch, on-orbit, and landing provide significant data in verifying proper operation of systems and evaluating anomalies. In addition to the Kennedy Space Center Photo/Video Analysis, reports from Johnson Space Center and Marshall Space Flight Center are also included in this document to provide an integrated assessment of the mission.

Debris/Ice/TPS Assessment and Integrated Photographic Analysis of Shuttle Mission STS-105

NASA Technical Reports Server (NTRS)

Oliu, Armando

2005-01-01

The Debris Team has developed and implemented measures to control damage from debris in the Shuttle operational environment and to make the control measures a part of routine launch flows. These measures include engineering surveillance during vehicle processing and closeout operations, facility and flight hardware inspections before and after launch, and photographic analysis of mission events. Photographic analyses of mission imagery from launch, on-orbit, and landing provide significant data in verifying proper operation of systems and evaluating anomalies. In addition to the Kennedy Space Center Photo/Video Analysis, reports from Johnson Space Center and Marshall Space Flight Center are also included in this document to provide an integrated assessment of the mission.

Debris/Ice/TPS Assessment and Integrated Photographic Analysis of Shuttle Mission STS-104

NASA Technical Reports Server (NTRS)

Oliu, Armando

2005-01-01

The Debris Team has developed and implemented measures to control damage from debris in the Shuttle operational environment and to make the control measures a part of routine launch flows. These measures include engineering surveillance during vehicle processing and closeout operations, facility and flight hardware inspections before and after launch, and photographic analysis of mission events. Photographic analyses of mission imagery from launch, on-orbit, and landing provide significant data in verifying proper operation of systems and evaluating anomalies. In addition to the Kennedy Space Center Photo/Video Analysis, reports from Johnson Space Center and Marshall Space Flight Center are also included in this document to provide an integrated assessment of the mission.

Debris/Ice/TPS Assessment and Integrated Photographic Analysis of Shuttle Mission STS-108

NASA Technical Reports Server (NTRS)

Oliu, Armando

2005-01-01

The Debris Team has developed and implemented measures to control damage from debris in the Shuttle operational environment and to make the control measures a part of routine launch flows. These measures include engineering surveillance during vehicle processing and closeout operations, facility and flight hardware inspections before and after launch, and photographic analysis of mission events. Photographic analyses of mission imagery from launch, on-orbit, and landing provide significant data in verifying proper operation of systems and evaluating anomalies. In addition to the Kennedy Space Center Photo/Video Analysis, reports from Johnson Space Center and Marshall Space Flight Center are also included in this document to provide an integrated assessment of the mission.

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.;

Around Marshall

NASA Image and Video Library

1990-12-02

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 activity of viewing HUT data in the Mission Manager Actions Room during the mission.

Around Marshall

NASA Image and Video Library

1990-12-02

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.

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.

51g-s-219

NASA Image and Video Library

2011-04-25

51G-S-219 (June 1985) --- Public Affairs Office (PAO) commentator Janet K. Ross is pictured at her console in the Mission Operations Control Room (MOCR) in the Mission Control Center at NASA's Johnson Space Center during the STS-51G mission. Photo credit: NASA

51g-s-213

NASA Image and Video Library

2011-04-25

51G-S-213 (June 1985) --- Public Affairs Office (PAO) commentator Janet K. Ross is pictured at her console in the Mission Operations Control Room (MOCR) in the Mission Control Center at NASA's Johnson Space Center during the STS-51G mission. Photo credit: NASA

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.

Around Marshall

NASA Image and Video Library

1990-12-04

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 activity of WUPPE (Wisconsin Ultraviolet Photo-Polarimeter Experiment) data review at the Science Operations Area during the mission. This image shows mission activities at the Broad Band X-Ray Telescope (BBXRT) Work Station in the Science Operations Area (SOA).

Display formats manual

NASA Technical Reports Server (NTRS)

Runnels, R. L.

1973-01-01

The standards and procedures for the generation of operational display formats to be used in the Mission Control Center (MCC) display control system are presented. The required effort, forms, and fundamentals for the design, specifications, and production of display formats are identified. The principles of display design and system constraints controlling the creation of optimum operational displays for mission control are explained. The basic two types of MCC display systems for presenting information are described.

NASA/MOD Operations Impacts from Shuttle Program

NASA Technical Reports Server (NTRS)

Fitzpatrick, Michael; Mattes, Gregory; Grabois, Michael; Griffith, Holly

2011-01-01

Operations plays a pivotal role in the success of any human spaceflight program. This paper will highlight some of the core tenets of spaceflight operations from a systems perspective and use several examples from the Space Shuttle Program to highlight where the success and safety of a mission can hinge upon the preparedness and competency of the operations team. Further, awareness of the types of operations scenarios and impacts that can arise during human crewed space missions can help inform design and mission planning decisions long before a vehicle gets into orbit. A strong operations team is crucial to the development of future programs; capturing the lessons learned from the successes and failures of a past program will allow for safer, more efficient, and better designed programs in the future. No matter how well a vehicle is designed and constructed, there are always unexpected events or failures that occur during space flight missions. Preparation, training, real-time execution, and troubleshooting are skills and values of the Mission Operations Directorate (MOD) flight controller; these operational standards have proven invaluable to the Space Shuttle Program. Understanding and mastery of these same skills will be required of any operations team as technology advances and new vehicles are developed. This paper will focus on individual Space Shuttle mission case studies where specific operational skills, techniques, and preparedness allowed for mission safety and success. It will detail the events leading up to the scenario or failure, how the operations team identified and dealt with the failure and its downstream impacts. The various options for real-time troubleshooting will be discussed along with the operations team final recommendation, execution, and outcome. Finally, the lessons learned will be summarized along with an explanation of how these lessons were used to improve the operational preparedness of future flight control teams.

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

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).

The Advanced Technology Operations System: ATOS

NASA Technical Reports Server (NTRS)

Kaufeler, J.-F.; Laue, H. A.; Poulter, K.; Smith, H.

1993-01-01

Mission control systems supporting new space missions face ever-increasing requirements in terms of functionality, performance, reliability and efficiency. Modern data processing technology is providing the means to meet these requirements in new systems under development. During the past few years the European Space Operations Centre (ESOC) of the European Space Agency (ESA) has carried out a number of projects to demonstrate the feasibility of using advanced software technology, in particular, knowledge based systems, to support mission operations. A number of advances must be achieved before these techniques can be moved towards operational use in future missions, namely, integration of the applications into a single system framework and generalization of the applications so that they are mission independent. In order to achieve this goal, ESA initiated the Advanced Technology Operations System (ATOS) program, which will develop the infrastructure to support advanced software technology in mission operations, and provide applications modules to initially support: Mission Preparation, Mission Planning, Computer Assisted Operations, and Advanced Training. The first phase of the ATOS program is tasked with the goal of designing and prototyping the necessary system infrastructure to support the rest of the program. The major components of the ATOS architecture is presented. This architecture relies on the concept of a Mission Information Base (MIB) as the repository for all information and knowledge which will be used by the advanced application modules in future mission control systems. The MIB is being designed to exploit the latest in database and knowledge representation technology in an open and distributed system. In conclusion the technological and implementation challenges expected to be encountered, as well as the future plans and time scale of the project, are presented.

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.

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 increases, HOSC must begin a phased activation of the BCC, while working resource conflicts with normal HOSC activities. In a long duration outage to the MCC, this could cause serious impacts to the BCC host facility s primary mission support activities. This management of a BCC is worked based on customer expectations and negotiations done before emergencies occur. I.

Mars Science Laboratory Cruise Propulsion Maneuvering Operations

NASA Technical Reports Server (NTRS)

Baker, Raymond S.; Mizukami, Masahi; Barber, Todd J.

2013-01-01

Mars Science Laboratory "Curiosity" is NASA's most recent mission to Mars, launched in November 2011, and landed in August 2012. It is a subcompact car-sized nuclear powered rover designed for a long duration mission, with an extensive suite of science instruments. Entry, descent and landing used a unique "skycrane" concept. This report describes the propulsive maneuvering operations during cruise from Earth to Mars, to control attitudes and to target the vehicle for entry. The propulsion subsystem, mission operations, and flight performance are discussed. All trajectory control maneuvers were well within accuracy requirements, and all turns and spin corrections were nominal.

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 and difficulties that a migration to cloud-based computing philosophies has uncovered when compared to the legacy Mission Control Center architecture. The team consists of system and software engineers with extensive experience with the MCC infrastructure and software currently used to support the International Space Station (ISS) and Space Shuttle program (SSP).

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.

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.

Spacelab

NASA Image and Video Library

1990-12-02

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. Pictured onboard the shuttle is astronaut Robert Parker using a Manual Pointing Controller (MPC) for the ASTRO-1 mission Instrument Pointing System (IPS).

Timeliner: Automating Procedures on the ISS

NASA Technical Reports Server (NTRS)

Brown, Robert; Braunstein, E.; Brunet, Rick; Grace, R.; Vu, T.; Zimpfer, Doug; Dwyer, William K.; Robinson, Emily

2002-01-01

Timeliner has been developed as a tool to automate procedural tasks. These tasks may be sequential tasks that would typically be performed by a human operator, or precisely ordered sequencing tasks that allow autonomous execution of a control process. The Timeliner system includes elements for compiling and executing sequences that are defined in the Timeliner language. The Timeliner language was specifically designed to allow easy definition of scripts that provide sequencing and control of complex systems. The execution environment provides real-time monitoring and control based on the commands and conditions defined in the Timeliner language. The Timeliner sequence control may be preprogrammed, compiled from Timeliner "scripts," or it may consist of real-time, interactive inputs from system operators. In general, the Timeliner system lowers the workload for mission or process control operations. In a mission environment, scripts can be used to automate spacecraft operations including autonomous or interactive vehicle control, performance of preflight and post-flight subsystem checkouts, or handling of failure detection and recovery. Timeliner may also be used for mission payload operations, such as stepping through pre-defined procedures of a scientific experiment.

Mission Operations Control Room Activities during STS-2 mission

NASA Technical Reports Server (NTRS)

1981-01-01

Mission Operations Control Room (MOCR) activities during STS-2 mission. President Ronald Reagan is briefed by Dr. Christopher C. Kraft, Jr., JSC Director, who points toward the orbiter spotter on the projection plotter at the front of the MOCR (39499); President Reagan joking with STS-2 astronauts during space to ground conversation (39500); Mission Specialist/Astronaut Sally K. Ride communicates with the STS-2 crew from the spacecraft communicator console (39501); Charles R. Lewis, bronze team Flight Director, monitors activity from the STS-2 crew. He is seated at the flight director console in MOCR (39502); Eugene F. Kranz, Deputy Director of Flight Operations at JSC answers a question during a press conference on Nov. 13, 1981. He is flanked by Glynn S. Lunney, Manager, Space Shuttle Program Office, JSC; and Dr. Christopher C. Kraft, Jr., Director of JSC (39503).

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.

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.

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.

Managing Risk in Safety Critical Operations - Lessons Learned from Space Operations

NASA Technical Reports Server (NTRS)

Gonzalez, Steven A.

2002-01-01

The Mission Control Center (MCC) at Johnson Space Center (JSC) has a rich legacy of supporting Human Space Flight operations throughout the Apollo, Shuttle and International Space Station eras. Through the evolution of ground operations and the Mission Control Center facility, NASA has gained a wealth of experience of what it takes to manage the risk in Safety Critical Operations, especially when human life is at risk. The focus of the presentation will be on the processes (training, operational rigor, team dynamics) that enable the JSC/MCC team to be so successful. The presentation will also share the evolution of the Mission Control Center architecture and how the evolution was introduced while managing the risk to the programs supported by the team. The details of the MCC architecture (e.g., the specific software, hardware or tools used in the facility) will not be shared at the conference since it would not give any additional insight as to how risk is managed in Space Operations.

Around Marshall

NASA Image and Video Library

1990-12-12

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 activity of WUPPE data review at the Science Operations Area during the mission.

Around Marshall

NASA Image and Video Library

1990-12-02

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 activity of BBKRT data review in the Science Operations Area during the mission.

Debris/ice/TPS assessment and integrated photographic analysis for Shuttle Mission STS-45

NASA Technical Reports Server (NTRS)

Katnik, Gregory N.; Higginbotham, Scott A.; Davis, J. Bradley

1992-01-01

The Debris Team has developed and implemented measures to control damage from debris in the Shuttle operational environment and to make the control measures a part of routine launch flows. These measures include engineering surveillance during vehicle processing and closeout operations, facility and flight hardware inspections before and after launch, and photographic analysis of mission events. Photographic analyses of mission imagery from launch, on-orbit, and landing provide significant data in verifying proper operation of systems and evaluating anomalies. In addition to the Kennedy Space Center (KSC) Photo/Video Analysis, reports from Johnson Space Center, Marshall Space Flight Center, and Rockwell International-Downey are also included to provide an integrated assessment of each Shuttle mission.

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 the decreasing flight rate. This paper presents the issues encountered during the HOSC cost analysis process, and the associated lessons learned. These lessons can be used when planning for a new multi-mission operations center or in the transformation from a dedicated control center to multi-center operations, as an aid in defining processes that support future cost analysis and estimation. The lessons can also be used by mature service-oriented, multi-mission control centers to streamline or refine their cost analysis process.

Incorporation of quality updates for JPSS CGS Products

NASA Astrophysics Data System (ADS)

Cochran, S.; Grant, K. D.; Ibrahim, W.; Brueske, K. F.; Smit, P.

2016-12-01

NOAA's next-generation environmental satellite, the Joint Polar Satellite System (JPSS) replaces the current Polar-orbiting Operational Environmental Satellites (POES). JPSS satellites carry sensors which collect meteorological, oceanographic, climatological, and solar-geophysical observations of the earth, atmosphere, and space. The first JPSS satellite was launched in 2011 and is currently NOAA's primary operational polar satellite. The JPSS ground system is the Common Ground System (CGS), and provides command, control, and communications (C3) and data processing (DP). A multi-mission system, CGS provides combinations of C3/DP for numerous NASA, NOAA, DoD, and international missions. In preparation for the next JPSS satellite, CGS improved its multi-mission capabilities to enhance mission operations for larger constellations of earth observing satellites with the added benefit of streamlining mission operations for other NOAA missions. This paper will discuss both the theoretical basis and the actual practices used to date to identify, test and incorporate algorithm updates into the CGS processing baseline. To provide a basis for this support, Raytheon developed a theoretical analysis framework, and the application of derived engineering processes, for the maintenance of consistency and integrity of remote sensing operational algorithm outputs. The framework is an abstraction of the operationalization of the science-grade algorithm (Sci2Ops) process used throughout the JPSS program. By combining software and systems engineering controls, manufacturing disciplines to detect and reduce defects, and a standard process to control analysis, an environment to maintain operational algorithm maturity is achieved. Results of the use of this approach to implement algorithm changes into operations will also be detailed.

Methods and Tools for Product Quality Maintenance in JPSS CGS

NASA Astrophysics Data System (ADS)

Cochran, S.; Smit, P.; Grant, K. D.; Jamilkowski, M. L.

2015-12-01

NOAA's next-generation environmental satellite, the Joint Polar Satellite System (JPSS) replaces the current Polar-orbiting Operational Environmental Satellites (POES). JPSS satellites carry sensors which collect meteorological, oceanographic, climatological, and solar-geophysical observations of the earth, atmosphere, and space. The first JPSS satellite was launched in 2011 and is currently NOAA's primary operational polar satellite. The JPSS ground system is the Common Ground System (CGS), and provides command, control, and communications (C3) and data processing (DP). A multi-mission system, CGS provides combinations of C3/DP for numerous NASA, NOAA, DoD, and international missions. In preparation for the next JPSS satellite, CGS improved its multi-mission capabilities to enhance mission operations for larger constellations of earth observing satellites with the added benefit of streamlining mission operations for other NOAA missions. This paper will discuss both the theoretical basis and the actual practices used to date to identify, test and incorporate algorithm updates into the CGS processing baseline. To provide a basis for this support, Raytheon developed a theoretical analysis framework, and the application of derived engineering processes, for the maintenance of consistency and integrity of remote sensing operational algorithm outputs. The framework is an abstraction of the operationalization of the science-grade algorithm (Sci2Ops) process used throughout the JPSS program. By combining software and systems engineering controls, manufacturing disciplines to detect and reduce defects, and a standard process to control analysis, an environment to maintain operational algorithm maturity is achieved. Results of the use of this approach to implement algorithm changes into operations will also be detailed.

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.

Using New Technologies in Support of Future Space Missions

NASA Technical Reports Server (NTRS)

Hooke, Adrian J.; Welch, David C.

1997-01-01

This paper forms a perspective of how new technologies such as onboard autonomy and internet-like protocols will change the look and feel of operations. It analyzes the concept of a lights-out mission operations control center and it's role in future mission support and it describes likely scenarios for evolving from current concepts.

The IXV Ground Segment design, implementation and operations

NASA Astrophysics Data System (ADS)

Martucci di Scarfizzi, Giovanni; Bellomo, Alessandro; Musso, Ivano; Bussi, Diego; Rabaioli, Massimo; Santoro, Gianfranco; Billig, Gerhard; Gallego Sanz, José María

2016-07-01

The Intermediate eXperimental Vehicle (IXV) is an ESA re-entry demonstrator that performed, on the 11th February of 2015, a successful re-entry demonstration mission. The project objectives were the design, development, manufacturing and on ground and in flight verification of an autonomous European lifting and aerodynamically controlled re-entry system. For the IXV mission a dedicated Ground Segment was provided. The main subsystems of the IXV Ground Segment were: IXV Mission Control Center (MCC), from where monitoring of the vehicle was performed, as well as support during pre-launch and recovery phases; IXV Ground Stations, used to cover IXV mission by receiving spacecraft telemetry and forwarding it toward the MCC; the IXV Communication Network, deployed to support the operations of the IXV mission by interconnecting all remote sites with MCC, supporting data, voice and video exchange. This paper describes the concept, architecture, development, implementation and operations of the ESA Intermediate Experimental Vehicle (IXV) Ground Segment and outlines the main operations and lessons learned during the preparation and successful execution of the IXV Mission.

Around Marshall

NASA Image and Video Library

1990-12-03

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. Pictured is Jack Jones in the Mission Manager Area.

Payload/orbiter contamination control requirement study: Preliminary contamination mission support plan. [a management analysis of project planning of spacecraft sterilization

NASA Technical Reports Server (NTRS)

Bareiss, L. E.; Hooper, V. W.; Ress, E. B.

1976-01-01

Progress is reported on the mission support plan and those support activities envisioned to be applicable and necessary during premission and postmission phases of the Spacelab program. The purpose, role, and requirements of the contamination control operations for the first two missions of the Spacelab equipped Space Transportation System are discussed. The organization of the contamination control operation and its relationship to and interfaces with other mission support functions is also discussed. Some specific areas of contamination to be investigated are treated. They are: (1) windows and viewports, (2) experiment equipment, (3) thermal control surfaces, (4) the contaminant induced atmosphere (as differentiated from the normal ambient atmosphere at the orbit altitude), and (5) optical navigation instruments.

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.

A life sciences Spacelab mission simulation

NASA Technical Reports Server (NTRS)

Mason, J. A.; Musgrave, F. S.; Morrison, D. R.

1977-01-01

The paper describes the purposes of a seven-day simulated life-sciences mission conducted in a Spacelab simulator. A major objective was the evaluation of in-orbit Spacelab operations and those mission control support functions which will be required from the Payload Operations Center. Tested equipment and procedures included experiment racks, common operational research equipment, commercial off-the-shelf equipment, experiment hardware interfaces with Spacelab, experiment data handling concepts, and Spacelab trash management.

The deep space network

NASA Technical Reports Server (NTRS)

1975-01-01

The objectives, functions, and organization of the Deep Space Network are summarized along with deep space station, ground communication, and network operations control capabilities. Mission support of ongoing planetary/interplanetary flight projects is discussed with emphasis on Viking orbiter radio frequency compatibility tests, the Pioneer Venus orbiter mission, and Helios-1 mission status and operations. Progress is also reported in tracking and data acquisition research and technology, network engineering, hardware and software implementation, and operations.

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.

Replicas of Snoopy and Charlie Brown decorate top of console in MCC

NASA Technical Reports Server (NTRS)

1969-01-01

Replicas of Snoopy and Charlie Brown, the two characters from Charles Schulz's syndicated comic strip 'Peanuts', decorate the top of a console in the Mission Operations Control Room in the Mission Control Center, bldg 30, on the first day of the Apollo 10 lunar orbit mission. During the Apollo 10 lunar orbit operations the Lunar Module will be called Snoopy when it is separated from the Command/Service Modules. The code words for the Command Module will be Charlie Brown.

INFLIGHT - APOLLO X - MSC

NASA Image and Video Library

1969-05-19

S69-34038 (18 May 1969) --- View of activity at the flight director's console in the Mission Operations Control Room in the Mission Control Center, Building 30, on the first day of the Apollo 10 lunar orbit mission. Seated are Gerald D. Griffin (foreground) and Glynn S. Lunney, Shift 1 (Black Team) flight directors. Milton L. Windler, standing behind them, is the flight director of Shift 2 (Maroon Team). In the center background, standing, is Dr. Christopher C. Kraft Jr., MSC Director of Flight Operations.

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.

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.

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 mission phase and the lessons learned that can be derived from this experience.

Documentary views of Flight Director and Controller activity during STS-2

NASA Image and Video Library

1981-11-12

S81-39431 (12 Nov. 1981) --- Eugene F. Kranz, left, and Dr. Christopher C. Kraft Jr. monitor data displayed on the FOD console in the mission operations control room (MOCR) in the Johnson Space Center?s mission control center following the successful launch of the Columbia, and the beginning of NASA?s second space shuttle mission. Dr. Kraft is director of the Johnson Space Center and Kranz is deputy director of the flight operations directorate (FOD) at JSC. Houston time for the launch was approximately 9:10 a.m., Nov 12, 1981. Photo credit: NASA

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.

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).

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.

The SAX Italian scientific satellite. The on-board implemented automation as a support to the ground control capability

NASA Technical Reports Server (NTRS)

Martelli, Andrea

1994-01-01

This paper presents the capabilities implemented in the SAX system for an efficient operations management during its in-flight mission. SAX is an Italian scientific satellite for x-ray astronomy whose major mission objectives impose quite tight constraints on the implementation of both the space and ground segment. The most relevant mission characteristics require an operative lifetime of two years, performing scientific observations both in contact and in noncontact periods, with a low equatorial orbit supported by one ground station, so that only a few minutes of communications are available each orbit. This operational scenario determines the need to have a satellite capable of performing the scheduled mission automatically and reacting autonomously to contingency situations. The implementation approach of the on-board operations management, through which the necessary automation and autonomy are achieved, follows a hierarchical structure. This has been achieved adopting a distributed avionic architecture. Nine different on-board computers, in fact, constitute the on-board data management system. Each of them performs the local control and monitors its own functions while the system level control is performed at a higher level by the data handling applications software. The SAX on-board architecture provides the ground operators with different options of intervention by three classes of telecommands. The management of the scientific operations will be scheduled by the operation control center via dedicated operating plans. The SAX satellite flight mode is presently being integrated at Alenia Spazio premises in Turin for a launch scheduled for the end of 1995. Once in orbit, the SAX satellite will be subject to intensive check-out activities in order to verify the required mission performances. An overview of the envisaged procedure and of the necessary on-ground activities is therefore depicted as well.

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.

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.

Transforming Our SMEX Organization by Way of Innovation, Standardization, and Automation

NASA Technical Reports Server (NTRS)

Madden, Maureen; Crouse, Pat; Carry, Everett; Esposito, timothy; Parker, Jeffrey; Bradley, David

2006-01-01

NASA's Small Explorer (SMEX) Flight Operations Team (FOT) is currently tackling the challenge of supporting ground operations for several satellites that have surpassed their designed lifetime and have a dwindling budget. At Goddard Space Flight Center (GSFC), these missions are presently being reengineered into a fleet-oriented ground system. When complete, this ground system will provide command and control of four SMEX missions, and will demonstrate fleet automation and control concepts as a pathfinder for additional mission integrations. A goal of this reengineering effort is to demonstrate new ground-system technologies that show promise of supporting longer mission lifecycles and simplifying component integration. In pursuit of this goal, the SMEX organization has had to examine standardization, innovation, and automation. A core technology being demonstrated in this effort is the GSFC Mission Services Evolution Center (GMSEC) architecture. The GMSEC architecture focuses on providing standard interfaces for ground system applications to promote application interoperability. Building around commercial Message Oriented Middleware and providing a common messaging standard allows GMSEC to provide the capabilities necessary to support integration of new software components into existing missions and increase the level of interaction within the system. For SMS, GMSEC has become the technology platform to transform flight operations with the innovation and automation necessary to reduce operational costs. The automation technologies supported in SMEX are built upon capabilities provided by the GMSEC architecture that allows the FOT to further reduce the involvement of the console, operator. Initially, SMEX is automating only routine operations, such as safety and health monitoring, basic commanding, and system recovery. The operational concepts being developed here will reduce the need for staffed passes and are a necessity for future fleet management. As this project continues to evolve, additional innovations beyond GMSEC and automation have, and will continue to be developed. The team developed techniques for migrating ground systems of existing on-orbit assets. The tools necessary to monitor and control software failures were integrated and tailored for operational environments. All this was done with a focus of extending fleet operations to mission beyond SMU. The result of this work is the foundation for a broader fleet-capable ground system that will include several missions supported by the Space Science Mission Operations Project.

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.

ATV Engineering Support Team Safety Console Preparation for the Johannes Kepler Mission

NASA Astrophysics Data System (ADS)

Chase, R.; Oliefka, L.

2010-09-01

This paper describes the improvements to be implemented in the Safety console position of the Engineering Support Team(EST) at the Automated Transfer Vehicle(ATV) Control Centre(ATV-CC) for the upcoming ATV Johannes Kepler mission. The ATV missions to the International Space Station are monitored and controlled from the ATV-CC in Toulouse, France. The commanding of ATV is performed by the Vehicle Engineering Team(VET) in the main control room under authority of the Flight Director. The EST performs a monitoring function in a room beside the main control room. One of the EST positions is the Safety console, which is staffed by safety engineers from ESA and the industrial prime contractor, Astrium. The function of the Safety console is to check whether the hazard controls are available throughout the mission as required by the Hazard Reports approved by the ISS Safety Review Panel. Safety console preparation activities were limited prior to the first ATV mission due to schedule constraints, and the safety engineers involved have been working to improve the readiness for ATV 2. The following steps have been taken or are in process, and will be described in this paper: • review of the implementation of Operations Control Agreement Documents(OCADs) that record the way operational hazard controls are performed to meet the needs of the Hazard Reports(typically in Flight Rules and Crew Procedures), • crosscheck of operational control needs and implementations with respect to ATV's first flight observations and post flight evaluations, with a view to identifying additional, obsolete or revised operational hazard controls, • participation in the Flight Rule review and update process carried out between missions, • participation in the assessment of anomalies observed during the first ATV mission, to ensure that any impacts are addressed in the ATV 2 safety documentation, • preparation of a Safety console handbook to provide lists of important safety aspects to be monitored at various stages of the mission, including links to relevant Hazard Reports, Flight Rules, and supporting documentation, • participation to training courses conducted in the frame of the ATV Training Academy(ATAC), and provision of courses related to safety for the other members of the VET and EST, • participation to simulations conducted at ATV-CC, including off-nominal cases. The result of these activities will be an improved level of readiness for the ATV 2 mission.

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.

Training augmentation device for the Air Force satellite Control Network

NASA Technical Reports Server (NTRS)

Shoates, Keith B.

1993-01-01

From the 1960's and into the early 1980's satellite operations and control were conducted by Air Force Systems Command (AFSC), now Air Force Materiel Command (AFMC), out of the Satellite Control Facility at Onizuka AFB, CA. AFSC was responsible for acquiring satellite command and control systems and conducting routine satellite operations. The daily operations, consisting of satellite health and status contacts and station keeping activities, were performed for AFSC by a Mission Control Team (MCT) staffed by civilian contractors who were responsible for providing their own technically 'qualified' personnel as satellite operators. An MCT consists of five positions: mission planner, ground controller, planner analyst, orbit analyst, and ranger controller. Most of the training consisted of On-the-Job-Training (OJT) with junior personnel apprenticed to senior personnel until they could demonstrate job proficiency. With most of the satellite operators having 15 to 25 years of experience, there was minimal risk to the mission. In the mid 1980's Air Force Space Command (AFSPACOM) assumed operational responsibility for a newly established control node at Falcon AFB (FAFB) in CO. The satellites and ground system program offices (SPO's) are organized under AFSC's Space and Missiles Systems Center (SMC) to function as a systems engineering and acquisition agency for AFSPACECOM. The collection of the satellite control nodes, ground tracking stations, computer processing equipment, and connecting communications links is referred to as the Air Force Satellite Control Network (AFSCN).

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

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 decreasing flight rate. This paper presents the issues encountered during the HOSC cost analysis process, and the associated lessons learned. These lessons can be used when planning for a new multi-mission operations center or in the transformation from a dedicated control center to multi-center operations, as an aid in defining processes that support future cost analysis and estimation. The lessons can also be used by mature serviceoriented, multi-mission control centers to streamline or refine their cost analysis process.

NASA/ESA CV-990 Spacelab Simulation (ASSESS 2)

NASA Technical Reports Server (NTRS)

1977-01-01

Cost effective techniques for addressing management and operational activities on Spacelab were identified and analyzed during a ten day NASA-ESA cooperative mission with payload and flight responsibilities handled by the organization assigned for early Spacelabs. Topics discussed include: (1) management concepts and interface relationships; (2) experiment selection; (3) hardware development; (4) payload integration and checkout; (5) selection and training of mission specialists and payload specialists; (6) mission control center/payload operations control center interactions with ground and flight problems; (7) real time interaction during flight between principal investigators and the mission specialist/payload specialist flight crew; and (8) retrieval of scientific data and its analysis.

Precision pointing of the international ultraviolet explorer /IUE/ scientific instrument using a gyroscopic and stellar reference

NASA Technical Reports Server (NTRS)

Moore, J. V.

1976-01-01

The Attitude Control System for the IUE spacecraft is described. The basic mission objectives are stated and a sequential discussion of the mission is presented. Desired accuracy for each mission phase is noted and where applicable the onboard control mechanization is shown. Sensors and actuator systems utilized by the control algorithms are described. Finally, onboard software is discussed to a level necessary to understand the prime mission mode operation.

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

Apollo guidance, navigation and control: Guidance system operations plan for manned CM earth orbital and lunar missions using Program COLOSSUS 3. Section 3: Digital autopilots (revision 14)

NASA Technical Reports Server (NTRS)

1972-01-01

Digital autopilots for the manned command module earth orbital and lunar missions using program COLOSSUS 3 are discussed. Subjects presented are: (1) reaction control system digital autopilot, (2) thrust vector control autopilot, (3) entry autopilot and mission control programs, (4) takeover of Saturn steering, and (5) coasting flight attitude maneuver routine.

Space tug thermal control

NASA Technical Reports Server (NTRS)

Ward, T. L.

1975-01-01

The future development of full capability Space Tug will impose strict requirements upon the thermal design. While requiring a reliable and reusable design, Space Tug must be capable of steady-state and transient thermal operation during any given mission for mission durations of up to seven days and potentially longer periods of time. Maximum flexibility and adaptability of Space Tug to the mission model requires that the vehicle operate within attitude constraints throughout any specific mission. These requirements were translated into a preliminary design study for a geostationary deploy and retrieve mission definition for Space Tug to determine the thermal control design requirements. Results of the study are discussed with emphasis given to some of the unique avenues pursued during the study, as well as the recommended thermal design configuration.

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.

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.

Ground Data System Risk Mitigation Techniques for Faster, Better, Cheaper Missions

NASA Technical Reports Server (NTRS)

Catena, John J.; Saylor, Rick; Casasanta, Ralph; Weikel, Craig; Powers, Edward I. (Technical Monitor)

2000-01-01

With the advent of faster, cheaper, and better missions, NASA Projects acknowledged that a higher level of risk was inherent and accepted with this approach. It was incumbent however upon each component of the Project whether spacecraft, payload, launch vehicle, or ground data system to ensure that the mission would nevertheless be an unqualified success. The Small Explorer (SMEX) program's ground data system (GDS) team developed risk mitigation techniques to achieve these goals starting in 1989. These techniques have evolved through the SMEX series of missions and are practiced today under the Triana program. These techniques are: (1) Mission Team Organization--empowerment of a closeknit ground data system team comprising system engineering, software engineering, testing, and flight operations personnel; (2) Common Spacecraft Test and Operational Control System--utilization of the pre-launch spacecraft integration system as the post-launch ground data system on-orbit command and control system; (3) Utilization of operations personnel in pre-launch testing--making the flight operations team an integrated member of the spacecraft testing activities at the beginning of the spacecraft fabrication phase; (4) Consolidated Test Team--combined system, mission readiness and operations testing to optimize test opportunities with the ground system and spacecraft; and (5). Reuse of Spacecraft, Systems and People--reuse of people, software and on-orbit spacecraft throughout the SMEX mission series. The SMEX ground system development approach for faster, cheaper, better missions has been very successful. This paper will discuss these risk management techniques in the areas of ground data system design, implementation, test, and operational readiness.

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.

Cognitive engineering models in space systems

NASA Technical Reports Server (NTRS)

Mitchell, Christine M.

1992-01-01

NASA space systems, including mission operations on the ground and in space, are complex, dynamic, predominantly automated systems in which the human operator is a supervisory controller. The human operator monitors and fine-tunes computer-based control systems and is responsible for ensuring safe and efficient system operation. In such systems, the potential consequences of human mistakes and errors may be very large, and low probability of such events is likely. Thus, models of cognitive functions in complex systems are needed to describe human performance and form the theoretical basis of operator workstation design, including displays, controls, and decision support aids. The operator function model represents normative operator behavior-expected operator activities given current system state. The extension of the theoretical structure of the operator function model and its application to NASA Johnson mission operations and space station applications is discussed.

Voice Over Internet Protocol (VoIP) in a Control Center Environment

NASA Technical Reports Server (NTRS)

Pirani, Joseph; Calvelage, Steven

2010-01-01

The technology of transmitting voice over data networks has been available for over 10 years. Mass market VoIP services for consumers to make and receive standard telephone calls over broadband Internet networks have grown in the last 5 years. While operational costs are less with VoIP implementations as opposed to time division multiplexing (TDM) based voice switches, is it still advantageous to convert a mission control center s voice system to this newer technology? Marshall Space Flight Center (MSFC) Huntsville Operations Support Center (HOSC) has converted its mission voice services to a commercial product that utilizes VoIP technology. Results from this testing, design, and installation have shown unique considerations that must be addressed before user operations. There are many factors to consider for a control center voice design. Technology advantages and disadvantages were investigated as they refer to cost. There were integration concerns which could lead to complex failure scenarios but simpler integration for the mission infrastructure. MSFC HOSC will benefit from this voice conversion with less product replacement cost, less operations cost and a more integrated mission services environment.

Around Marshall

NASA Image and Video Library

1990-12-04

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 a press briefing at MSFC during STS-35, ASTRO-1 Mission.

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 operator on-orbit of some of the more routine tasks. Overall these proposed approaches when used effectively offer the potential to drive down operations overhead and allow more efficient and productive robotic operations.

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)

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.

APOLLO X - DUKE, MICHAEL B., DR. - MSC

NASA Image and Video Library

1969-05-19

S69-34040 (18 May 1969) --- Partial view of activity in the Mission Operations Control Room in the Mission Control Center, Building 30, on the first day of the Apollo 10 lunar orbit mission. The television monitor shows a picture of Earth made during the second telecast from the Apollo 10's color TV camera.

POST-LAUNCH - APOLLO XVI - MSC

NASA Image and Video Library

1972-04-19

S72-35460 (18 April 1972) --- Dr. J.F. Zieglschmid, M.D., Missions Operations Control Room (MOCR) White Team Surgeon, is seated in the Medical Support Room (MSR) in the Mission Control Center (MCC). He monitors crew biomedical data being received from the Apollo 16 spacecraft on the third day of the lunar landing mission.

Autonomous Mission Operations

NASA Technical Reports Server (NTRS)

Frank, Jeremy; Spirkovska, Lilijana; McCann, Rob; Wang, Lui; Pohlkamp, Kara; Morin, Lee

2012-01-01

NASA's Advanced Exploration Systems Autonomous Mission Operations (AMO) project conducted an empirical investigation of the impact of time-delay on todays mission operations, and of the effect of processes and mission support tools designed to mitigate time-delay related impacts. Mission operation scenarios were designed for NASA's Deep Space Habitat (DSH), an analog spacecraft habitat, covering a range of activities including nominal objectives, DSH system failures, and crew medical emergencies. The scenarios were simulated at time-delay values representative of Lunar (1.2-5 sec), Near Earth Object (NEO) (50 sec) and Mars (300 sec) missions. Each combination of operational scenario and time-delay was tested in a Baseline configuration, designed to reflect present-day operations of the International Space Station, and a Mitigation configuration in which a variety of software tools, information displays, and crew-ground communications protocols were employed to assist both crews and Flight Control Team (FCT) members with the long-delay conditions. Preliminary findings indicate: 1) Workload of both crew members and FCT members generally increased along with increasing time delay. 2) Advanced procedure execution viewers, caution and warning tools, and communications protocols such as text messaging decreased the workload of both flight controllers and crew, and decreased the difficulty of coordinating activities. 3) Whereas crew workload ratings increased between 50 sec and 300 sec of time-delay in the Baseline configuration, workload ratings decreased (or remained flat) in the Mitigation configuration.

Replicas of Snoopy and Charlie Brown decorate top of console in MCC

NASA Image and Video Library

1969-05-18

S69-34314 (18 May 1969) --- Replicas of Snoopy and Charlie Brown, the two characters from Charles Schulz's syndicated comic strip, "Peanuts," decorate the top of a console in the Mission Operations Control Room in the Mission Control Center, Building 30, on the first day of the Apollo 10 lunar orbit mission. During lunar orbit operations, the Lunar Module will be called ?Snoopy? when it is separated from the Command and Service Modules. The code words for the Command Module will be ?Charlie Brown?.

The AMADEE-15 Mars simulation

NASA Astrophysics Data System (ADS)

Groemer, Gernot; Losiak, Anna; Soucek, Alexander; Plank, Clemens; Zanardini, Laura; Sejkora, Nina; Sams, Sebastian

2016-12-01

We report on the AMADEE-15 mission, a 12-day Mars analog field test at the Kaunertal Glacier in Austria. Eleven experiments were conducted by a field crew at the test site under simulated martian surface exploration conditions and coordinated by a Mission Support Center in Innsbruck, Austria. The experiments' research fields encompassed geology, human factors, astrobiology, robotics, tele-science, exploration, and operations research. A Remote Science Support team analyzed field data in near real time, providing planning input for a flight control team to manage a complex system of field assets in a realistic work flow, including: two advanced space suit simulators; and four robotic and aerial vehicles. Field operations were supported by a dedicated flight planning group, an external control center tele-operating the PULI-rover, and a medical team. A 10-min satellite communication delay and other limitations pertinent to human planetary surface activities were introduced. This paper provides an overview of the geological context and environmental conditions of the test site and the mission architecture, with a focus on the mission's communication infrastructure. We report on the operational workflows and the experiments conducted, as well as a novel approach of measuring mission success through the introduction of general analog mission transferrable performance indicators.

Weathering the Storm - GOCE Flight Operations in 2010

NASA Astrophysics Data System (ADS)

Steiger, C.; Da Costa, A.; Floberghagen, R.; Fehringer, M.; Emanuelli, P. P.

2011-07-01

ESA's Gravity Field and Steady-State Ocean Circulation Explorer (GOCE) was successfully launched on 17th March 2009. The mission is controlled by ESA's European Space Operations Centre (ESOC) in Darmstadt, Germany. Following completion of commissioning, routine operations started in September 2009, keeping the S/C in drag-free mode at an altitude of 259.6 km. Operations are driven by the unique aspects of the mission, in particular the very low altitude and the high complexity of GOCE's drag- free control system. Following a general introduction, the main focus is put on the special events of 2010, when science operations were interrupted for several months due to problems with the main platform computer. These anomalies presented a major challenge, requiring to operate the spacecraft "in the blind" with no status information available, and extensive modifications of the on-board software to recover the mission.

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.

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.

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.

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.

AMO EXPRESS: A Command and Control Experiment for Crew Autonomy Onboard the International Space Station

NASA Technical Reports Server (NTRS)

Cornelius, Randy; Frank, Jeremy; Garner, Larry; Haddock, Angie; Stetson, Howard; Wang, Lui

2015-01-01

The Autonomous Mission Operations project is investigating crew autonomy capabilities and tools for deep space missions. Team members at Ames Research Center, Johnson Space Center and Marshall Space Flight Center are using their experience with ISS Payload operations and TIMELINER to: move earth based command and control assets to on-board for crew access; safely merge core and payload command procedures; give the crew single action intelligent operations; and investigate crew interface requirements.

Influence of a new generation of operations support systems on current spacecraft operations philosophy: The users feedback

NASA Technical Reports Server (NTRS)

Darroy, Jean Michel

1993-01-01

Current trends in the spacecraft mission operations area (spacecraft & mission complexity, project duration, required flexibility are requiring a breakthrough for what concerns philosophy, organization, and support tools. A major evolution is related to space operations 'informationalization', i.e adding to existing operations support & data processing systems a new generation of tools based on advanced information technologies (object-oriented programming, artificial intelligence, data bases, hypertext) that automate, at least partially, operations tasks that used be performed manually (mission & project planning/scheduling, operations procedures elaboration & execution, data analysis & failure diagnosis). All the major facets of this 'informationalization' are addressed at MATRA MARCONI SPACE, operational applications were fielded and generic products are becoming available. These various applications have generated a significant feedback from the users (at ESA, CNES, ARIANESPACE, MATRA MARCONI SPACE), which is now allowing us to precisely measure how the deployment of this new generation of tools, that we called OPSWARE, can 'reengineer' current spacecraft mission operations philosophy, how it can make space operations faster, better, and cheaper. This paper can be considered as an update of the keynote address 'Knowledge-Based Systems for Spacecraft Control' presented during the first 'Ground Data Systems for Spacecraft Control' conference in Darmstadt, June 1990, with a special emphasis on these last two years users feedback.

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.

Prox-1 Automated Proximity Operations

DTIC Science & Technology

2016-01-13

K.J., and Veto, M., "Automated Trajectory Control for On-Orbit Inspection in the Prox-1 Mission," Journal of Spacecraft and Rockets , in review...the operability of all commands needed for the minimum mission. A Simulated Communications Test was performed that demonstrated long-range uplink...Guidance, Navigation and Control subsystem 6 DOF simulation , and delivered for flight coding. Validation of the system’s capability to meet full

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

jsc2010e046805

NASA Image and Video Library

2010-04-05

JSC2010-E-046805 (5 April 2010) --- John McCullough, chief of the Flight Director Office; and Janet Kavandi, deputy director, Flight Crew Operations, watch television screens at the Mission Operations Directorate (MOD) console in the space shuttle flight control room in the Mission Control Center at NASA's Johnson Space Center during launch a few hundred miles away in Florida, site of space shuttle Discovery's STS-131 liftoff.

MOCR activity during Day 4 of STS-3 mission

NASA Technical Reports Server (NTRS)

1982-01-01

Major General J.A. Abrahamson, right, talks to JSC Director Christopher C. Kraft, Jr., (seated left) and Space Shuttle Program Manager Glynn S. Lunney on the back row of consoles in the mission operations control room (MOCR) in the Johnson Space Center mission control center. The reflection behind the men is a window for the MOCR viewing room (28772,28775); Abrahamson, second right, talks to JSC's Aaron Cohen, right, as Kraft (seated left) and Lunney listen in mission control (28773); Flight controller J.E. Connor monitors a television transmission from the Space Shuttle Columbia during day 4 of the STS-3 mission. Conner is seated at his INCO console (28774).

Representing operations procedures using temporal dependency networks

NASA Technical Reports Server (NTRS)

Fayyad, Kristina E.; Cooper, Lynne P.

1993-01-01

DSN Link Monitor & Control (LMC) operations consist primarily of executing procedures to configure, calibrate, test, and operate a communications link between an interplanetary spacecraft and its mission control center. Currently the LMC operators are responsible for integrating procedures into an end-to-end series of steps. The research presented in this paper is investigating new ways of specifying operations procedures that incorporate the insight of operations, engineering, and science personnel to improve mission operations. The paper describes the rationale for using Temporal Dependency Networks (TDN's) to represent the procedures, a description of how the data is acquired, and the knowledge engineering effort required to represent operations procedures. Results of operational tests of this concept, as implemented in the LMC Operator Assistant Prototype (LMCOA), are also presented.

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.

2014 Summer Series - Robert Carvalho - Pursuing the Mysteries of the Sun: The IRIS Mission

NASA Image and Video Library

2014-06-19

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 IRIS's 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.

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

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

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.

Centralized mission planning and scheduling system for the Landsat Data Continuity Mission

USGS Publications Warehouse

Kavelaars, Alicia; Barnoy, Assaf M.; Gregory, Shawna; Garcia, Gonzalo; Talon, Cesar; Greer, Gregory; Williams, Jason; Dulski, Vicki

2014-01-01

Satellites in Low Earth Orbit provide missions with closer range for studying aspects such as geography and topography, but often require efficient utilization of space and ground assets. Optimizing schedules for these satellites amounts to a complex planning puzzle since it requires operators to face issues such as discontinuous ground contacts, limited onboard memory storage, constrained downlink margin, and shared ground antenna resources. To solve this issue for the Landsat Data Continuity Mission (LDCM, Landsat 8), all the scheduling exchanges for science data request, ground/space station contact, and spacecraft maintenance and control will be coordinated through a centralized Mission Planning and Scheduling (MPS) engine, based upon GMV’s scheduling system flexplan9 . The synchronization between all operational functions must be strictly maintained to ensure efficient mission utilization of ground and spacecraft activities while working within the bounds of the space and ground resources, such as Solid State Recorder (SSR) and available antennas. This paper outlines the functionalities that the centralized planning and scheduling system has in its operational control and management of the Landsat 8 spacecraft.

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.

Becoming Earth Independent: Human-Automation-Robotics Integration Challenges for Future Space Exploration

NASA Technical Reports Server (NTRS)

Marquez, Jessica J.

2016-01-01

Future exploration missions will require NASA to integrate more automation and robotics in order to accomplish mission objectives. This presentation will describe on the future challenges facing the human operator (astronaut, ground controllers) as we increase the amount of automation and robotics in spaceflight operations. It will describe how future exploration missions will have to adapt and evolve in order to deal with more complex missions and communication latencies. This presentation will outline future human-automation-robotic integration challenges.

Tailoring NIST Security Controls for the Ground System: Selection and Implementation -- Recommendations for Information System Owners

NASA Technical Reports Server (NTRS)

Takamura, Eduardo; Mangum, Kevin

2016-01-01

The National Aeronautics and Space Administration (NASA) invests millions of dollars in spacecraft and ground system development, and in mission operations in the pursuit of scientific knowledge of the universe. In recent years, NASA sent a probe to Mars to study the Red Planet's upper atmosphere, obtained high resolution images of Pluto, and it is currently preparing to find new exoplanets, rendezvous with an asteroid, and bring a sample of the asteroid back to Earth for analysis. The success of these missions is enabled by mission assurance. In turn, mission assurance is backed by information assurance. The information systems supporting NASA missions must be reliable as well as secure. NASA - like every other U.S. Federal Government agency - is required to manage the security of its information systems according to federal mandates, the most prominent being the Federal Information Security Management Act (FISMA) of 2002 and the legislative updates that followed it. Like the management of enterprise information technology (IT), federal information security management takes a "one-size fits all" approach for protecting IT systems. While this approach works for most organizations, it does not effectively translate into security of highly specialized systems such as those supporting NASA missions. These systems include command and control (C&C) systems, spacecraft and instrument simulators, and other elements comprising the ground segment. They must be carefully configured, monitored and maintained, sometimes for several years past the missions' initially planned life expectancy, to ensure the ground system is protected and remains operational without any compromise of its confidentiality, integrity and availability. Enterprise policies, processes, procedures and products, if not effectively tailored to meet mission requirements, may not offer the needed security for protecting the information system, and they may even become disruptive to mission operations. Certain protective measures for the general enterprise may not be as efficient within the ground segment. This is what the authors have concluded through observations and analysis of patterns identified from the various security assessments performed on NASA missions such as MAVEN, OSIRIS-REx, New Horizons and TESS, to name a few. The security audits confirmed that the framework for managing information system security developed by the National Institute of Standards and Technology (NIST) for the federal government, and adopted by NASA, is indeed effective. However, the selection of the technical, operational and management security controls offered by the NIST model - and how they are implemented - does not always fit the nature and the environment where the ground system operates in even though there is no apparent impact on mission success. The authors observed that unfit controls, that is, controls that are not necessarily applicable or sufficiently effective in protecting the mission systems, are often selected to facilitate compliance with security requirements and organizational expectations even if the selected controls offer minimum or non-existent protection. This paper identifies some of the standard security controls that can in fact protect the ground system, and which of them offer little or no benefit at all. It offers multiple scenarios from real security audits in which the controls are not effective without, of course, disclosing any sensitive information about the missions assessed. In addition to selection and implementation of controls, the paper also discusses potential impact of recent legislation such as the Federal Information Security Modernization Act (FISMA) of 2014 - aimed at the enterprise - on the ground system, and offers other recommendations to Information System Owners (ISOs).

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 geologists participated in the mission simulation. The scientific goal of the science mission was to determine what could be learned about the geologic context of the site using the capabilities of imaging and mobility provided by the Marsokhod system in these two modes of operation. I will discuss the lessons learned from these experiments in terms of the strategy for performing Mars surface exploration using rovers. This research is supported by the Solar System Exploration Exobiology, Geology, and Advanced Technology programs.

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.

Development and human factors analysis of an augmented reality interface for multi-robot tele-operation and control

NASA Astrophysics Data System (ADS)

Lee, Sam; Lucas, Nathan P.; Ellis, R. Darin; Pandya, Abhilash

2012-06-01

This paper presents a seamlessly controlled human multi-robot system comprised of ground and aerial robots of semiautonomous nature for source localization tasks. The system combines augmented reality interfaces capabilities with human supervisor's ability to control multiple robots. The role of this human multi-robot interface is to allow an operator to control groups of heterogeneous robots in real time in a collaborative manner. It used advanced path planning algorithms to ensure obstacles are avoided and that the operators are free for higher-level tasks. Each robot knows the environment and obstacles and can automatically generate a collision-free path to any user-selected target. It displayed sensor information from each individual robot directly on the robot in the video view. In addition, a sensor data fused AR view is displayed which helped the users pin point source information or help the operator with the goals of the mission. The paper studies a preliminary Human Factors evaluation of this system in which several interface conditions are tested for source detection tasks. Results show that the novel Augmented Reality multi-robot control (Point-and-Go and Path Planning) reduced mission completion times compared to the traditional joystick control for target detection missions. Usability tests and operator workload analysis are also investigated.

Applying lessons learned to enhance human performance and reduce human error for ISS operations

DOE Office of Scientific and Technical Information (OSTI.GOV)

Nelson, W.R.

1999-01-01

A major component of reliability, safety, and mission success for space missions is ensuring that the humans involved (flight crew, ground crew, mission control, etc.) perform their tasks and functions as required. This includes compliance with training and procedures during normal conditions, and successful compensation when malfunctions or unexpected conditions occur. A very significant issue that affects human performance in space flight is human error. Human errors can invalidate carefully designed equipment and procedures. If certain errors combine with equipment failures or design flaws, mission failure or loss of life can occur. The control of human error during operation ofmore » the International Space Station (ISS) will be critical to the overall success of the program. As experience from Mir operations has shown, human performance plays a vital role in the success or failure of long duration space missions. The Department of Energy{close_quote}s Idaho National Engineering and Environmental Laboratory (INEEL) is developing a systematic approach to enhance human performance and reduce human errors for ISS operations. This approach is based on the systematic identification and evaluation of lessons learned from past space missions such as Mir to enhance the design and operation of ISS. This paper will describe previous INEEL research on human error sponsored by NASA and how it can be applied to enhance human reliability for ISS. {copyright} {ital 1999 American Institute of Physics.}« less

Applying lessons learned to enhance human performance and reduce human error for ISS operations

DOE Office of Scientific and Technical Information (OSTI.GOV)

Nelson, W.R.

1998-09-01

A major component of reliability, safety, and mission success for space missions is ensuring that the humans involved (flight crew, ground crew, mission control, etc.) perform their tasks and functions as required. This includes compliance with training and procedures during normal conditions, and successful compensation when malfunctions or unexpected conditions occur. A very significant issue that affects human performance in space flight is human error. Human errors can invalidate carefully designed equipment and procedures. If certain errors combine with equipment failures or design flaws, mission failure or loss of life can occur. The control of human error during operation ofmore » the International Space Station (ISS) will be critical to the overall success of the program. As experience from Mir operations has shown, human performance plays a vital role in the success or failure of long duration space missions. The Department of Energy`s Idaho National Engineering and Environmental Laboratory (INEEL) is developed a systematic approach to enhance human performance and reduce human errors for ISS operations. This approach is based on the systematic identification and evaluation of lessons learned from past space missions such as Mir to enhance the design and operation of ISS. This paper describes previous INEEL research on human error sponsored by NASA and how it can be applied to enhance human reliability for ISS.« less

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.

CCSDS Spacecraft Monitor and Control Mission Operations Interoperability Prototype

NASA Technical Reports Server (NTRS)

Lucord, Steve; Martinez, Lindolfo

2009-01-01

We are entering a new era in space exploration. Reduced operating budgets require innovative solutions to leverage existing systems to implement the capabilities of future missions. Custom solutions to fulfill mission objectives are no longer viable. Can NASA adopt international standards to reduce costs and increase interoperability with other space agencies? Can legacy systems be leveraged in a service oriented architecture (SOA) to further reduce operations costs? The Operations Technology Facility (OTF) at the Johnson Space Center (JSC) is collaborating with Deutsches Zentrum fur Luft- und Raumfahrt (DLR) to answer these very questions. The Mission Operations and Information Management Services Area (MOIMS) Spacecraft Monitor and Control (SM&C) Working Group within the Consultative Committee for Space Data Systems (CCSDS) is developing the Mission Operations standards to address this problem space. The set of proposed standards presents a service oriented architecture to increase the level of interoperability among space agencies. The OTF and DLR are developing independent implementations of the standards as part of an interoperability prototype. This prototype will address three key components: validation of the SM&C Mission Operations protocol, exploration of the Object Management Group (OMG) Data Distribution Service (DDS), and the incorporation of legacy systems in a SOA. The OTF will implement the service providers described in the SM&C Mission Operation standards to create a portal for interaction with a spacecraft simulator. DLR will implement the service consumers to perform the monitor and control of the spacecraft. The specifications insulate the applications from the underlying transport layer. We will gain experience with a DDS transport layer as we delegate responsibility to the middleware and explore transport bridges to connect disparate middleware products. A SOA facilitates the reuse of software components. The prototype will leverage the capabilities of existing legacy systems. Various custom applications and middleware solutions will be combined into one system providing the illusion of a set of homogenous services. This paper will document our journey as we implement the interoperability prototype. The team consists of software engineers with experience on the current command, telemetry and messaging systems that support the International Space Station (ISS) and Space Shuttle programs. Emphasis will be on the objectives, results and potential cost saving benefits.

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.

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

Systems engineering considerations for operational support systems

NASA Technical Reports Server (NTRS)

Aller, Robert O.

1993-01-01

Operations support as considered here is the infrastructure of people, procedures, facilities and systems that provide NASA with the capability to conduct space missions. This infrastructure involves most of the Centers but is concentrated principally at the Johnson Space Center, the Kennedy Space Center, the Goddard Space Flight Center, and the Jet Propulsion Laboratory. It includes mission training and planning, launch and recovery, mission control, tracking, communications, data retrieval and data processing.

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.

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.

NASA Office of Aeronautics and Space Technology Summer Workshop. Volume 3: Navigation, guidance and control panel

NASA Technical Reports Server (NTRS)

1975-01-01

User technology requirements are identified in relation to needed technology advancement for future space missions in the areas of navigation, guidance, and control. Emphasis is placed on: reduction of mission support cost by 50% through autonomous operation, a ten-fold increase in mission output through improved pointing and control, and a hundred-fold increase in human productivity in space through large-scale teleoperator applications.

A Flexible Evolvable Architecture for Constellation Mission Systems User Applications

NASA Technical Reports Server (NTRS)

Trimble, Jay P.; Crocker, Alan R.

2008-01-01

While simulating a complex set of repair tasks to be performed by EVA crewmembers on an upcoming mission, flight controllers and astronauts determine that the repair will take much longer than originally anticipated. All equipment in the vicinity of the worksite must be powered off to maintain a safe environment for the astronauts. Because heater power will be unavailable, several critical components will now be at risk of freezing and permanent damage. If an impending thermal violation is detected, Mission Control will have very limited time to react. Therefore, flight controllers must not only modify their procedures to account for these risks, they must also incorporate into their displays outputs from thermal models, alternate temperature measurements, new alarm limits, and emergency power-on commands to enable the detection and response to freezing conditions. Current software for mission control systems makes scenarios like this difficult to address. Given the time frame for modifying software, operations teams are left with labor-intensive operational workarounds as their only options. NASA Ames Research Center (ARC) and NASA Johnson Space Center (JSC) are collaborating on the development of a flexible software system for mission operations that will enable greater user flexibility than has been available to date. Using composable software, end users in the scenario described above could recompose procedures and command and control displays to allow flight controllers to monitor temperature measurements, identify time-critical conditions, and execute the procedures required to respond to these conditions before flight hardware is permanently damaged.

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.

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.

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.

Delegation control of multiple unmanned systems

NASA Astrophysics Data System (ADS)

Flaherty, Susan R.; Shively, Robert J.

2010-04-01

Maturing technologies and complex payloads coupled with a future objective to reduce the logistics burden of current unmanned aerial systems (UAS) operations require a change to the 2-crew employment paradigm. Increased automation and operator supervisory control of unmanned systems have been advocated to meet the objective of reducing the crew requirements, while managing future technologies. Specifically, a delegation control employment strategy has resulted in reduced workload and higher situation awareness for single operators controlling multiple unmanned systems in empirical studies1,2. Delegation control is characterized by the ability for an operator to call a single "play" that initiates prescribed default actions for each vehicle and associated sensor related to a common mission goal. Based upon the effectiveness of delegation control in simulation, the U.S. Army Aeroflightdynamics Directorate (AFDD) developed a Delegation Control (DelCon) operator interface with voice recognition implementation for play selection, real-time play modification, and play status with automation transparency to enable single operator control of multiple unmanned systems in flight. AFDD successfully demonstrated delegation control in a Troops-in-Contact mission scenario at Ft. Ord in 2009. This summary showcases the effort as a beneficial advance in single operator control of multiple UAS.

Around Marshall

NASA Image and Video Library

1990-12-03

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 is an overview of the MSFC Payload Control Room (PCR).

Operation Eclipse; Appreciation and Outline Plan

DTIC Science & Technology

1945-04-25

the boundaries of GERMANY . " . • g« Engineering tools, equipment, plant and stores0 specially, adapted for military purposes. Bridging material of...Control Council ( Germany ) Control Commission for Germany ’ (British Element) Supreme Hq AEF Mission (Denmark) Supreme Headquarters, Allied...Mission (Norway) U.S. Group Control Council (Austria) Control Commission for Germany (Air Division) War Office, MO 1 (SP) • ’ Control Commission for

Mission planning for autonomous systems

NASA Technical Reports Server (NTRS)

Pearson, G.

1987-01-01

Planning is a necessary task for intelligent, adaptive systems operating independently of human controllers. A mission planning system that performs task planning by decomposing a high-level mission objective into subtasks and synthesizing a plan for those tasks at varying levels of abstraction is discussed. Researchers use a blackboard architecture to partition the search space and direct the focus of attention of the planner. Using advanced planning techniques, they can control plan synthesis for the complex planning tasks involved in mission planning.

Mission operations technology

NASA Astrophysics Data System (ADS)

Varsi, Giulio

In the last decade, the operation of a spacecraft after launch has emerged as a major component of the total cost of the mission. This trend is sustained by the increasing complexity, flexibility, and data gathering capability of the space assets and by their greater reliability and consequent longevity. The trend can, however, be moderated by the progressive transfer of selected functions from the ground to the spacecraft and by application, on the ground, of new technology. Advances in ground operations derive from the introduction in the mission operations environment of advanced microprocessor-based workstations in the class of a few million instructions per second and from the selective application of artificial intelligence technology. In the last few years a number of these applications have been developed, tested in operational settings and successfully demonstrated to users. Some are now being integrated in mission operations facilities. An analysis of mission operations indicates that the key areas are: concurrent control of multiple missions; automated/interactive production of command sequences of high integrity at low cost; automated monitoring of spacecraft health and automated aides for fault diagnosis; automated allocation of resources; automated processing of science data; and high-fidelity, high-speed spacecraft simulation. Examples of major advances in selected areas are described.

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.

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.

JSC officials in MCC Bldg 30 monitor STS-26 Discovery, OV-103, activity

NASA Image and Video Library

1988-10-03

JSC officials, laughing, listen to crewmembers' commentary onboard Discovery, Orbiter Vehicle (OV) 103, during STS-26. In the Flight Control Room (FCR) of JSC's Mission Control Center (MCC) Bldg 30 and seated at the Mission Operations Directorate (MOD) console, MOD Director Eugene F. Kranz (foreground), wearing red, white and blue vest, smiles along with JSC Director Aaron Cohen and Flight Crew Operations Deputy Director Henry W. Hartsfield, Jr. (far right).

JSC Officials in MCC Bldg 30 monitor STS-26 Discovery, OV-103, activity

NASA Technical Reports Server (NTRS)

1988-01-01

JSC Officials, laughing, listen to crewmembers' commentary onboard Discovery, Orbiter Vehicle (OV) 103, during STS-26. In the Flight Control Room (FCR) of JSC's Mission Control Center (MCC) Bldg 30 and seated at the Mission Operations Directorate (MOD) console, MOD Director Eugene F. Kranz (foreground), wearing red, white and blue vest, smiles along with JSC Director Aaron Cohen and Flight Crew Operations Deputy Director Henry W. Hartsfield, Jr. (far right).

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.

Around Marshall

NASA Image and Video Library

1990-12-03

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. Pictured is the TV OPS area of the SL POCC.

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.

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

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

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.

Swarm satellite mission scheduling & planning using Hybrid Dynamic Mutation Genetic Algorithm

NASA Astrophysics Data System (ADS)

Zheng, Zixuan; Guo, Jian; Gill, Eberhard

2017-08-01

Space missions have traditionally been controlled by operators from a mission control center. Given the increasing number of satellites for some space missions, generating a command list for multiple satellites can be time-consuming and inefficient. Developing multi-satellite, onboard mission scheduling & planning techniques is, therefore, a key research field for future space mission operations. In this paper, an improved Genetic Algorithm (GA) using a new mutation strategy is proposed as a mission scheduling algorithm. This new mutation strategy, called Hybrid Dynamic Mutation (HDM), combines the advantages of both dynamic mutation strategy and adaptive mutation strategy, overcoming weaknesses such as early convergence and long computing time, which helps standard GA to be more efficient and accurate in dealing with complex missions. HDM-GA shows excellent performance in solving both unconstrained and constrained test functions. The experiments of using HDM-GA to simulate a multi-satellite, mission scheduling problem demonstrates that both the computation time and success rate mission requirements can be met. The results of a comparative test between HDM-GA and three other mutation strategies also show that HDM has outstanding performance in terms of speed and reliability.

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.

Optimization of Maneuver Execution for Landsat-7 Routine Operations

NASA Technical Reports Server (NTRS)

Cox, E. Lucien, Jr.; Bauer, Frank H. (Technical Monitor)

2000-01-01

Multiple mission constraints were satisfied during a lengthy, strategic ascent phase. Once routine operations begin, the ongoing concern of maintaining mission requirements becomes an immediate priority. The Landsat-7 mission has tight longitude control box and Earth imaging that requires sub-satellite descending nodal equator crossing times to occur in a narrow 30minute range fifteen (15) times daily. Operationally, spacecraft maneuvers must'be executed properly to maintain mission requirements. The paper will discuss the importance of optimizing the altitude raising and plane change maneuvers, amidst known constraints, to satisfy requirements throughout mission lifetime. Emphasis will be placed not only on maneuver size and frequency but also on changes in orbital elements that impact maneuver execution decisions. Any associated trade-off arising from operations contingencies will be discussed as well. Results of actual altitude and plane change maneuvers are presented to clarify actions taken.

s95-16439

NASA Image and Video Library

2014-08-14

S95-16439 (13-22 July 1995) --- An overall view from the rear shows activity in the new Mission Control Center (MCC), opened for operation and dedicated during the STS-70 mission. The new MCC, developed at a cost of about 50 million, replaces the main-frame based, NASA-unique design of the old Mission Control with a standard workstation-based, local area network system commonly in use today.

The First Spacelab Mission

NASA Technical Reports Server (NTRS)

Craft, H.

1984-01-01

The role of the mission manager in coordinating the payload with the space transportation system is studied. The establishment of the investigators working group to assist in achieving the mission objectives is examined. Analysis of the scientific requirements to assure compatibility with available resources, and analysis of the payload in order to define orbital flight requirements are described. The training of payload specialists, launch site integration, and defining the requirements for the operation of the integrated payload and the payload operations control center are functions of the mission manager. The experiences gained from the management of the Spacelab One Mission, which can be implemented in future missions, are discussed. Examples of material processing, earth observations, and life sciences advances from the First Spacelab Mission are presented.

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.

Space Station crew workload - Station operations and customer accommodations

NASA Technical Reports Server (NTRS)

Shinkle, G. L.

1985-01-01

The features of the Space Station which permit crew members to utilize work time for payload operations are discussed. The user orientation, modular design, nonstressful flight regime, in space construction, on board control, automation and robotics, and maintenance and servicing of the Space Station are examined. The proposed crew size, skills, and functions as station operator and mission specialists are described. Mission objectives and crew functions, which include performing material processing, life science and astronomy experiments, satellite and payload equipment servicing, systems monitoring and control, maintenance and repair, Orbital Maneuvering Vehicle and Mobile Remote Manipulator System operations, on board planning, housekeeping, and health maintenance and recreation, are studied.

Automatic control in planetary exploration in the 1980s. [onboard spacecraft

NASA Technical Reports Server (NTRS)

Moore, J. W.

1973-01-01

Based on an examination of the planetary missions in the 1980s and their related objectives, a broad assessment of the automatic control capabilities required for these missions is presented. The ten outer-planet, terrestrial-planet, and small-body missions considered involve various operations encompassing a complex series of modes including cruise, maneuver, and powered flight control. In addition to routine navigation and attitude control, onboard control is required to point scientific instruments and antennas with respect to the vehicle and to maneuver the spacecraft in time-constrained or hazardous environments. These 1980 missions aimed at exploring new areas of the solar system will be more demanding. New design philosophies and increased performance capabilities will be required to meet the constraints imposed by science requirements and mission-cost effectiveness.

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.

MONTE: the next generation of mission design and navigation software

NASA Astrophysics Data System (ADS)

Evans, Scott; Taber, William; Drain, Theodore; Smith, Jonathon; Wu, Hsi-Cheng; Guevara, Michelle; Sunseri, Richard; Evans, James

2018-03-01

The Mission analysis, Operations and Navigation Toolkit Environment (MONTE) (Sunseri et al. in NASA Tech Briefs 36(9), 2012) is an astrodynamic toolkit produced by the Mission Design and Navigation Software Group at the Jet Propulsion Laboratory. It provides a single integrated environment for all phases of deep space and Earth orbiting missions. Capabilities include: trajectory optimization and analysis, operational orbit determination, flight path control, and 2D/3D visualization. MONTE is presented to the user as an importable Python language module. This allows a simple but powerful user interface via CLUI or script. In addition, the Python interface allows MONTE to be used seamlessly with other canonical scientific programming tools such as SciPy, NumPy, and Matplotlib. MONTE is the prime operational orbit determination software for all JPL navigated missions.

Customizing the JPL Multimission Ground Data System: Lessons learned

NASA Technical Reports Server (NTRS)

Murphy, Susan C.; Louie, John J.; Guerrero, Ana Maria; Hurley, Daniel; Flora-Adams, Dana

1994-01-01

The Multimission Ground Data System (MGDS) at NASA's Jet Propulsion Laboratory has brought improvements and new technologies to mission operations. It was designed as a generic data system to meet the needs of multiple missions and avoid re-inventing capabilities for each new mission and thus reduce costs. It is based on adaptable tools that can be customized to support different missions and operations scenarios. The MGDS is based on a distributed client/server architecture, with powerful Unix workstations, incorporating standards and open system architectures. The distributed architecture allows remote operations and user science data exchange, while also providing capabilities for centralized ground system monitor and control. The MGDS has proved its capabilities in supporting multiple large-class missions simultaneously, including the Voyager, Galileo, Magellan, Ulysses, and Mars Observer missions. The Operations Engineering Lab (OEL) at JPL has been leading Customer Adaptation Training (CAT) teams for adapting and customizing MGDS for the various operations and engineering teams. These CAT teams have typically consisted of only a few engineers who are familiar with operations and with the MGDS software and architecture. Our experience has provided a unique opportunity to work directly with the spacecraft and instrument operations teams and understand their requirements and how the MGDS can be adapted and customized to minimize their operations costs. As part of this work, we have developed workstation configurations, automation tools, and integrated user interfaces at minimal cost that have significantly improved productivity. We have also proved that these customized data systems are most successful if they are focused on the people and the tasks they perform and if they are based upon user confidence in the development team resulting from daily interactions. This paper will describe lessons learned in adapting JPL's MGDS to fly the Voyager, Galileo, and Mars Observer missions. We will explain how powerful, existing ground data systems can be adapted and packaged in a cost effective way for operations of small and large planetary missions. We will also describe how the MGDS was adapted to support operations within the Galileo Spacecraft Testbed. The Galileo testbed provided a unique opportunity to adapt MGDS to support command and control operations for a small autonomous operations team of a handful of engineers flying the Galileo Spacecraft flight system model.

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 duration work shifts. These findings indicate that extended duration work shifts present a significant challenge to crewmembers and mission support specialists during long-duration space mission operations. Future research is needed to evaluate the efficacy of alternative work schedules and the development and implementation of more effective countermeasures will be required to maintain high levels of performance.

Interactive Exploration Robots: Human-Robotic Collaboration and Interactions

NASA Technical Reports Server (NTRS)

Fong, Terry

2017-01-01

For decades, NASA has employed different operational approaches for human and robotic missions. Human spaceflight missions to the Moon and in low Earth orbit have relied upon near-continuous communication with minimal time delays. During these missions, astronauts and mission control communicate interactively to perform tasks and resolve problems in real-time. In contrast, deep-space robotic missions are designed for operations in the presence of significant communication delay - from tens of minutes to hours. Consequently, robotic missions typically employ meticulously scripted and validated command sequences that are intermittently uplinked to the robot for independent execution over long periods. Over the next few years, however, we will see increasing use of robots that blend these two operational approaches. These interactive exploration robots will be remotely operated by humans on Earth or from a spacecraft. These robots will be used to support astronauts on the International Space Station (ISS), to conduct new missions to the Moon, and potentially to enable remote exploration of planetary surfaces in real-time. In this talk, I will discuss the technical challenges associated with building and operating robots in this manner, along with lessons learned from research conducted with the ISS and in the field.

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.

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.

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.

Remote mission specialist - A study in real-time, adaptive planning

NASA Technical Reports Server (NTRS)

Rokey, Mark J.

1990-01-01

A high-level planning architecture for robotic operations is presented. The remote mission specialist integrates high-level directives with low-level primitives executable by a run-time controller for command of autonomous servicing activities. The planner has been designed to address such issues as adaptive plan generation, real-time performance, and operator intervention.

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 creatin(y an effective USI for one specific suite of tools, SERS (The Spacecraft Emergency Response System), which has been built to enable lights-out operations. SERS is a Web-based collaborative environment that enables secure distributed fault management.

NASA Space Technology Draft Roadmap Area 13: Ground and Launch Systems Processing

NASA Technical Reports Server (NTRS)

Clements, Greg

2011-01-01

This slide presentation reviews the technology development roadmap for the area of ground and launch systems processing. The scope of this technology area includes: (1) Assembly, integration, and processing of the launch vehicle, spacecraft, and payload hardware (2) Supply chain management (3) Transportation of hardware to the launch site (4) Transportation to and operations at the launch pad (5) Launch processing infrastructure and its ability to support future operations (6) Range, personnel, and facility safety capabilities (7) Launch and landing weather (8) Environmental impact mitigations for ground and launch operations (9) Launch control center operations and infrastructure (10) Mission integration and planning (11) Mission training for both ground and flight crew personnel (12) Mission control center operations and infrastructure (13) Telemetry and command processing and archiving (14) Recovery operations for flight crews, flight hardware, and returned samples. This technology roadmap also identifies ground, launch and mission technologies that will: (1) Dramatically transform future space operations, with significant improvement in life-cycle costs (2) Improve the quality of life on earth, while exploring in co-existence with the environment (3) Increase reliability and mission availability using low/zero maintenance materials and systems, comprehensive capabilities to ascertain and forecast system health/configuration, data integration, and the use of advanced/expert software systems (4) Enhance methods to assess safety and mission risk posture, which would allow for timely and better decision making. Several key technologies are identified, with a couple of slides devoted to one of these technologies (i.e., corrosion detection and prevention). Development of these technologies can enhance life on earth and have a major impact on how we can access space, eventually making routine commercial space access and improve building and manufacturing, and weather forecasting for example for the effect of these process improvements on our daily lives.

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.

Mars, the Moon, and the Ends of the Earth: Autonomy for Small Reactor Power Systems

DOE Office of Scientific and Technical Information (OSTI.GOV)

Wood, Richard Thomas

2008-01-01

In recent years, the National Aeronautics and Space Administration (NASA) has been considering deep space missions that utilize a small-reactor power system (SRPS) to provide energy for propulsion and spacecraft power. Additionally, application of SRPS modules as a planetary power source is being investigated to enable a continuous human presence for nonpolar lunar sites and on Mars. A SRPS can supply high-sustained power for space and surface applications that is both reliable and mass efficient. The use of small nuclear reactors for deep space or planetary missions presents some unique challenges regarding the operations and control of the power system.more » Current-generation terrestrial nuclear reactors employ varying degrees of human control and decision-making for operations and benefit from periodic human interaction for maintenance. In contrast, the control system of a SRPS employed for deep space missions must be able to accommodate unattended operations due to communications delays and periods of planetary occlusion while adapting to evolving or degraded conditions with no opportunity for repair or refurbishment. While surface power systems for planetary outposts face less extreme delays and periods of isolation and may benefit from limited maintenance capabilities, considerations such as human safety, resource limitations and usage priorities, and economics favor minimizing direct, continuous human interaction with the SRPS for online, dedicated power system management. Thus, a SRPS control system for space or planetary missions must provide capabilities for operational autonomy. For terrestrial reactors, large-scale power plants remain the preferred near-term option for nuclear power generation. However, the desire to reduce reliance on carbon-emitting power sources in developing countries may lead to increased consideration of SRPS modules for local power generation in remote regions that are characterized by emerging, less established infrastructures. Additionally, many Generation IV (Gen IV) reactor concepts have goals for optimizing investment recovery and economic efficiency that promote significant reductions in plant operations and maintenance staff over current-generation nuclear power plants. To accomplish these Gen IV goals and also address the SRPS remote-siting challenges, higher levels of automation, fault tolerance, and advanced diagnostic capabilities are needed to provide nearly autonomous operations with anticipatory maintenance. Essentially, the SRPS control system for several anticipated terrestrial applications can benefit from the kind of operational autonomy that is necessary for deep space and planetary SRPS-enabled missions. Investigation of the state of the technology for autonomous control confirmed that control systems with varying levels of autonomy have been employed in robotic, transportation, spacecraft, and manufacturing applications. As an example, NASA has pursued autonomy for spacecraft and surface exploration vehicles (e.g., rovers) to reduce mission costs, increase efficiency for communications between ground control and the vehicle, and enable independent operation of the vehicle during times of communications blackout. However, autonomous control has not been implemented for an operating terrestrial nuclear power plant nor has there been any experience beyond automating simple control loops for space reactors. Current automated control technologies for nuclear power plants are reasonably mature, and fully automated control of normal SRPS operations is clearly feasible. However, the space-based and remote terrestrial applications of SRPS modules require autonomous capabilities that can accommodate nonoptimum operations when degradation, failure, and other off-normal events challenge the performance of the reactor while immediate human intervention is not possible. The independent action provided by autonomous control, which is distinct from the more limited self action of automated control, can satisfy these conditions. Key characteristics that distinguish autonomous control include: (1) intelligence to confirm system performance and detect degraded or failed conditions, (2) optimization to minimize stress on SRPS components and efficiently react to operational events without compromising system integrity, (3) robustness to accommodate uncertainties and changing conditions, and (4) flexibility and adaptability to accommodate failures through reconfiguration among available control system elements or adjustment of control system strategies, algorithms, or parameters.« less

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.

Brown at RMS controls on the aft flight deck

NASA Image and Video Library

1998-11-24

STS095-366-031 (29 Oct-7 Nov 1998) --- Astronaut Curtis L. Brown, Jr., mission commander, operates controls on the aft flight deck of the Space Shuttle Discovery. Brown was joined by four other NASA astronauts and two payload specialists for the nine-day mission.

Integrated Systems Health Management for Space Exploration

NASA Technical Reports Server (NTRS)

Uckun, Serdar

2005-01-01

Integrated Systems Health Management (ISHM) is a system engineering discipline that addresses the design, development, operation, and lifecycle management of components, subsystems, vehicles, and other operational systems with the purpose of maintaining nominal system behavior and function and assuring mission safety and effectiveness under off-nominal conditions. NASA missions are often conducted in extreme, unfamiliar environments of space, using unique experimental spacecraft. In these environments, off-nominal conditions can develop with the potential to rapidly escalate into mission- or life-threatening situations. Further, the high visibility of NASA missions means they are always characterized by extraordinary attention to safety. ISHM is a critical element of risk mitigation, mission safety, and mission assurance for exploration. ISHM enables: In-space maintenance and repair; a) Autonomous (and automated) launch abort and crew escape capability; b) Efficient testing and checkout of ground and flight systems; c) Monitoring and trending of ground and flight system operations and performance; d) Enhanced situational awareness and control for ground personnel and crew; e) Vehicle autonomy (self-sufficiency) in responding to off-nominal conditions during long-duration and distant exploration missions; f) In-space maintenance and repair; and g) Efficient ground processing of reusable systems. ISHM concepts and technologies may be applied to any complex engineered system such as transportation systems, orbital or planetary habitats, observatories, command and control systems, life support systems, safety-critical software, and even the health of flight crews. As an overarching design and operational principle implemented at the system-of-systems level, ISHM holds substantial promise in terms of affordability, safety, reliability, and effectiveness of space exploration missions.

Cassini End of Mission

NASA Image and Video Library

2017-09-14

Spacecraft operations team manager for the Cassini mission at Saturn, Julie Webster, watches monitors in mission control of the Space Flight Operations Center as the Cassini spacecraft begins downlink data through NASA's Deep Space Network, Thursday, Sept. 14, 2017 at NASA's Jet Propulsion Laboratory in Pasadena, California. Since its arrival in 2004, the Cassini-Huygens mission has been a discovery machine, revolutionizing our knowledge of the Saturn system and captivating us with data and images never before obtained with such detail and clarity. On Sept. 15, 2017, operators will deliberately plunge the spacecraft into Saturn, as Cassini gathered science until the end. The “plunge” ensures Saturn’s moons will remain pristine for future exploration. During Cassini’s final days, mission team members from all around the world gathered at NASA’s Jet Propulsion Laboratory, Pasadena, California, to celebrate the achievements of this historic mission. Photo Credit: (NASA/Joel Kowsky)

Engineering and simulation of life sciences Spacelab experiments

NASA Technical Reports Server (NTRS)

Johnston, R. S.; Bush, W. H. Jr; Rummel, J. A.; Alexander, W. C.

1979-01-01

The third in a series of Spacelab Mission Development tests was conducted at the Johnson (correction of Johnston) Space Center as a part of the development of Life Sciences experiments for the Space Shuttle era. The latest test was a joint effort of the Ames Research and Johnson Space Centers and utilized animals and men for study. The basic objective of this test was to evaluate the operational concepts planned for the Space Shuttle life science payloads program. A three-man crew (Mission Specialist and two Payload Specialists) conducted 26 experiments and 12 operational tests, which were selected for this 7-day mission simulation. The crew lived on board a simulated Orbiter/Spacelab mockup 24 hr a day. The Orbiter section contained the mid deck crew quarters area, complete with sleeping, galley and waste management provisions. The Spacelab was identical in geometry to the European Space Agency Spacelab design, complete with removable rack sections and stowage provisions. Communications between the crewmen and support personnel were configured and controlled as currently planned for operational shuttle flights. For this test a Science Operations Remote Center was manned at the Ames Research Center and was managed by simulated Mission Control and Payload Operation Control Centers at the Johnson Space Center. This paper presents the test objectives, description of the facilities and test program, and the results of this test.

Rendezvous and Proximity Operations of the Space Shuttle

NASA Technical Reports Server (NTRS)

Goodman, John L.

2005-01-01

Space Shuttle rendezvous missions present unique challenges that were not fully recognized when the Shuttle was designed. Rendezvous targets could be passive (i.e., no lights or transponders), and not designed to facilitate Shuttle rendezvous, proximity operations, and retrieval. Shuttle reaction control system jet plume impingement on target spacecraft presented induced dynamics, structural loading, and contamination concerns. These issues, along with limited reaction control system propellant in the Shuttle nose, drove a change from the legacy Gemini/Apollo coelliptic profile to a stable orbit profile, and the development of new proximity operations techniques. Multiple scientific and on-orbit servicing missions, and crew exchange, assembly and replenishment flights to Mir and to the International Space Station drove further profile and piloting technique changes. These changes included new proximity operations, relative navigation sensors, and new computer generated piloting cues. However, the Shuttle's baseline rendezvous navigation system has not required modification to place the Shuttle at the proximity operations initiation point for all rendezvous missions flown.

Ground based simulation of life sciences Spacelab experiments

NASA Technical Reports Server (NTRS)

Rummel, J. A.; Alexander, W. C.; Bush, W. H.; Johnston, R. S.

1978-01-01

The third in a series of Spacelab Mission Development tests was a joint effort of the Ames Research and Johnson Space Centers to evaluate planned operational concepts of the Space Shuttle life sciences program. A three-man crew conducted 26 experiments and 12 operational tests, utilizing both human and animal subjects. The crew lived aboard an Orbiter/Spacelab mockup for the seven-day simulation. The Spacelab was identical in geometry to the European Space Agency design, complete with removable rack sections and stowage provisions. Communications were controlled as currently planned for operational Shuttle flights. A Science Operations Remote Center at the Ames Research Center was managed by simulated Mission Control and Payload Operation Control Centers at the Johnson Space Center. This paper presents the test objectives, describes the facilities and test program, and outlines the results of this test.

An Architecture to Enable Autonomous Control of Spacecraft

NASA Technical Reports Server (NTRS)

May, Ryan D.; Dever, Timothy P.; Soeder, James F.; George, Patrick J.; Morris, Paul H.; Colombano, Silvano P.; Frank, Jeremy D.; Schwabacher, Mark A.; Wang, Liu; LawLer, Dennis

2014-01-01

Autonomy is required for manned spacecraft missions distant enough that light-time communication delays make ground-based mission control infeasible. Presently, ground controllers develop a complete schedule of power modes for all spacecraft components based on a large number of factors. The proposed architecture is an early attempt to formalize and automate this process using on-vehicle computation resources. In order to demonstrate this architecture, an autonomous electrical power system controller and vehicle Mission Manager are constructed. These two components are designed to work together in order to plan upcoming load use as well as respond to unanticipated deviations from the plan. The communication protocol was developed using "paper" simulations prior to formally encoding the messages and developing software to implement the required functionality. These software routines exchange data via TCP/IP sockets with the Mission Manager operating at NASA Ames Research Center and the autonomous power controller running at NASA Glenn Research Center. The interconnected systems are tested and shown to be effective at planning the operation of a simulated quasi-steady state spacecraft power system and responding to unexpected disturbances.

Development of a cooperative operational rendezvous plan for Eureca and other maneuvering Shuttle payloads

NASA Technical Reports Server (NTRS)

Gavin, R. T.

1987-01-01

This paper discusses the development of a new class of US Space Shuttle rendezvous missions which involve a maneuvering target vehicle. The objective of the analysis was to develop an operational plan to take advantage of the target spacecraft's maneuvering ability by making it responsible for a portion of the maneuvers necessary to achieve rendezvous. This work resulted in the development of a region in space relative to the Shuttle, called the control box, into which the target vehicle maneuvers. Furthermore, a mission operations plan was developed to implement the control box technique.

JSC MCC Bldg 30 personnel monitor STS-26 post landing activities

NASA Image and Video Library

1988-10-03

JSC Mission Control Center (MCC) Bldg 30 flight control room (FCR) personnel monitor STS-26 post landing activities and ceremonies at Edwards Air Force Base (EAFB) via their monitors. Displayed on front screens are approach and landing diagrams, data, the space shuttle program insignia, the STS-26 mission insignia, the Mission Operations Directorate insignia, and the STS-26 crew standing in front of Discovery, Orbiter Vehicle (OV) 103.

Planning and Estimation of Operations Support Requirements

NASA Technical Reports Server (NTRS)

Newhouse, Marilyn E.; Barley, Bryan; Bacskay, Allen; Clardy, Dennon

2010-01-01

Life Cycle Cost (LCC) estimates during the proposal and early design phases, as well as project replans during the development phase, are heavily focused on hardware development schedules and costs. Operations (phase E) costs are typically small compared to the spacecraft development and test costs. This, combined with the long lead time for realizing operations costs, can lead to de-emphasizing estimation of operations support requirements during proposal, early design, and replan cost exercises. The Discovery and New Frontiers (D&NF) programs comprise small, cost-capped missions supporting scientific exploration of the solar system. Any LCC growth can directly impact the programs' ability to fund new missions, and even moderate yearly underestimates of the operations costs can present significant LCC impacts for deep space missions with long operational durations. The National Aeronautics and Space Administration (NASA) D&NF Program Office at Marshall Space Flight Center (MSFC) recently studied cost overruns and schedule delays for 5 missions. The goal was to identify the underlying causes for the overruns and delays, and to develop practical mitigations to assist the D&NF projects in identifying potential risks and controlling the associated impacts to proposed mission costs and schedules. The study found that 4 out of the 5 missions studied had significant overruns at or after launch due to underestimation of the complexity and supporting requirements for operations activities; the fifth mission had not launched at the time of the mission. The drivers behind these overruns include overly optimistic assumptions regarding the savings resulting from the use of heritage technology, late development of operations requirements, inadequate planning for sustaining engineering and the special requirements of long duration missions (e.g., knowledge retention and hardware/software refresh), and delayed completion of ground system development work. This paper updates the D&NF LCC study, looking at the operations (phase E) cost drivers in more detail and extending the study to include 2 additional missions and identifies areas for increased emphasis by project management in order to improve the fidelity of operations estimates.

Multi-User Space Link Extension (SLE) System

NASA Technical Reports Server (NTRS)

Perkins, Toby

2013-01-01

The Multi-User Space (MUS) Link Extension system, a software and data system, provides Space Link Extension (SLE) users with three space data transfer services in timely, complete, and offline modes as applicable according to standards defined by the Consultative Committee for Space Data Systems (CCSDS). MUS radically reduces the schedule, cost, and risk of implementing a new SLE user system, minimizes operating costs with a lights-out approach to SLE, and is designed to require no sustaining engineering expense during its lifetime unless changes in the CCSDS SLE standards, combined with new provider implementations, force changes. No software modification to MUS needs to be made to support a new mission. Any systems engineer with Linux experience can begin testing SLE user service instances with MUS starting from a personal computer (PC) within five days. For flight operators, MUS provides a familiar-looking Web page for entering SLE configuration data received from SLE. Operators can also use the Web page to back up a space mission's entire set of up to approximately 500 SLE service instances in less than five seconds, or to restore or transfer from another system the same amount of data from a MUS backup file in about the same amount of time. Missions operate each MUS SLE service instance independently by sending it MUS directives, which are legible, plain ASCII strings. MUS directives are usually (but not necessarily) sent through a TCP-IP (Transmission Control Protocol Internet Protocol) socket from a MOC (Mission Operations Center) or POCC (Payload Operations Control Center) system, under scripted control, during "lights-out" spacecraft operation. MUS permits the flight operations team to configure independently each of its data interfaces; not only commands and telemetry, but also MUS status messages to the MOC. Interfaces can use single- or multiple-client TCP/IP server sockets, TCP/IP client sockets, temporary disk files, the system log, or standard in, standard out, or standard error as applicable. By defining MUS templates in ASCII, the flight operations team can include any MUS system variable in telemetry or command headers or footers, and/or in status messages. Data fields can be arranged within messages in different sequences, according to the mission s needs. The only constraints imposed are on the format of MUS directive strings, and some bare minimum logical requirements that must be met in order for MUS to read the mission control center's spacecraft command inputs. The MUS system imposes no limits or constraints on the numbers and combinations of missions and SLE service instances that it will support simultaneously. At any time, flight operators may add, change, delete, bind, connect, or disconnect.

Smarter Software For Enhanced Vehicle Health Monitoring and Inter-Planetary Exploration

NASA Technical Reports Server (NTRS)

Larson, William E.; Goodrich, Charles H.; Steinrock, Todd (Technical Monitor)

2001-01-01

The existing philosophy for space mission control was born in the early days of the space program when technology did not exist to put significant control responsibility onboard the spacecraft. NASA relied on a team of ground control experts to troubleshoot systems when problems occurred. As computing capability improved, more responsibility was handed over to the systems software. However, there is still a large contingent of both launch and flight controllers supporting each mission. New technology can update this philosophy to increase mission assurance and reduce the cost of inter-planetary exploration. The advent of model-based diagnosis and intelligent planning software enables spacecraft to handle most routine problems automatically and allocate resources in a flexible way to realize mission objectives. The manifests for recent missions include multiple subsystems and complex experiments. Spacecraft must operate at longer distances from earth where communications delays make earthbound command and control impractical. NASA's Ames Research Center (ARC) has demonstrated the utility of onboard diagnosis and planning with the Remote Agent experiment in 1999. KSC has pioneered model-based diagnosis and demonstrated its utility for ground support operations. KSC and ARC are cooperating in research to improve the state of the art of this technology. This paper highlights model-based reasoning applications for Moon and Mars missions including in-situ resource utilization and enhanced vehicle health monitoring.

Cost-Effective Telemetry and Command Ground Systems Automation Strategy for the Soil Moisture Active Passive (SMAP) Mission

NASA Technical Reports Server (NTRS)

Choi, Josh; Sanders, Antonio

2012-01-01

Soil Moisture Active Passive (SMAP) is an Earth-orbiting, remote-sensing NASA mission slated for launch in 2014. The ground data system (GDS) being developed for SMAP is composed of many heterogeneous subsystems, ranging from those that support planning and sequencing to those used for real-time operations, and even further to those that enable science data exchange. A full end-to-end automation of the GDS may result in cost savings during mission operations, but it would require a significant upfront investment to develop such a comprehensive automation. As demonstrated by the Jason-1 and Wide-field Infrared Survey Explorer (WISE) missions, a measure of "lights-out" automation for routine, orbital pass, ground operations can still reduce mission costs through smaller staffing of operators and limiting their working hours. The challenge, then, for the SMAP GDS engineering team, is to formulate an automated operations strategy--and corresponding system architecture -- to minimize operator intervention during routine operations, while balancing the development costs associated with the scope and complexity of automation. This paper discusses the automated operations approach being developed for the SMAP GDS. The focus is on automating the activities involved in routine passes, which limits the scope to real-time operations. A key subsystem of the SMAP GDS -- NASA's AMMOS Mission Data Processing and Control System (AMPCS) -- provides a set of capabilities that enable such automation. Also discussed are the lights-out pass automations of the Jason-1 and WISE missions and how they informed the automation strategy for SMAP. The paper aims to provide insights into what is necessary in automating the GDS operations for Earth satellite missions.

Cost-Effective Telemetry and Command Ground Systems Automation Strategy for the Soil Moisture Active Passive (SMAP) Mission

NASA Technical Reports Server (NTRS)

Choi, Joshua S.; Sanders, Antonio L.

2012-01-01

Soil Moisture Active Passive (SMAP) is an Earth-orbiting, remote-sensing NASA mission slated for launch in 2014.[double dagger] The ground data system (GDS) being developed for SMAP is composed of many heterogeneous subsystems, ranging from those that support planning and sequencing to those used for real-time operations, and even further to those that enable science data exchange. A full end-to-end automation of the GDS may result in cost savings during mission operations, but it would require a significant upfront investment to develop such comprehensive automation. As demonstrated by the Jason-1 and Wide-field Infrared Survey Explorer (WISE) missions, a measure of "lights-out" automation for routine, orbital pass ground operations can still reduce mission cost through smaller staffing of operators and limited work hours. The challenge, then, for the SMAP GDS engineering team is to formulate an automated operations strategy--and corresponding system architecture--to minimize operator intervention during operations, while balancing the development cost associated with the scope and complexity of automation. This paper discusses the automated operations approach being developed for the SMAP GDS. The focus is on automating the activities involved in routine passes, which limits the scope to real-time operations. A key subsystem of the SMAP GDS--NASA's AMMOS Mission Data Processing and Control System (AMPCS)--provides a set of capabilities that enable such automation. Also discussed are the lights-out pass automations of the Jason-1 and WISE missions and how they informed the automation strategy for SMAP. The paper aims to provide insights into what is necessary in automating the GDS operations for Earth satellite missions.

VISITOR - SULTAN - JSC

NASA Image and Video Library

1985-04-04

S85-29711 (April 1985) --- Ronald C. Epps, right of the training division in the mission operations directorate, briefs the Saudi Arabian payload specialist, Sultan Salman Abdelazize Al-Saud, and his backup, Abdulmohsen Hamad Al-Bassam, in the flight control room (FCR) of the mission control center (MCC). Erlinda Stevenson is also pictured.

Virtualization - A Key Cost Saver in NASA Multi-Mission Ground System Architecture

NASA Technical Reports Server (NTRS)

Swenson, Paul; Kreisler, Stephen; Sager, Jennifer A.; Smith, Dan

2014-01-01

With science team budgets being slashed, and a lack of adequate facilities for science payload teams to operate their instruments, there is a strong need for innovative new ground systems that are able to provide necessary levels of capability processing power, system availability and redundancy while maintaining a small footprint in terms of physical space, power utilization and cooling.The ground system architecture being presented is based off of heritage from several other projects currently in development or operations at Goddard, but was designed and built specifically to meet the needs of the Science and Planetary Operations Control Center (SPOCC) as a low-cost payload command, control, planning and analysis operations center. However, this SPOCC architecture was designed to be generic enough to be re-used partially or in whole by other labs and missions (since its inception that has already happened in several cases!)The SPOCC architecture leverages a highly available VMware-based virtualization cluster with shared SAS Direct-Attached Storage (DAS) to provide an extremely high-performing, low-power-utilization and small-footprint compute environment that provides Virtual Machine resources shared among the various tenant missions in the SPOCC. The storage is also expandable, allowing future missions to chain up to 7 additional 2U chassis of storage at an extremely competitive cost if they require additional archive or virtual machine storage space.The software architecture provides a fully-redundant GMSEC-based message bus architecture based on the ActiveMQ middleware to track all health and safety status within the SPOCC ground system. All virtual machines utilize the GMSEC system agents to report system host health over the GMSEC bus, and spacecraft payload health is monitored using the Hammers Integrated Test and Operations System (ITOS) Galaxy Telemetry and Command (TC) system, which performs near-real-time limit checking and data processing on the downlinked data stream and injects messages into the GMSEC bus that are monitored to automatically page the on-call operator or Systems Administrator (SA) when an off-nominal condition is detected. This architecture, like the LTSP thin clients, are shared across all tenant missions.Other required IT security controls are implemented at the ground system level, including physical access controls, logical system-level authentication authorization management, auditing and reporting, network management and a NIST 800-53 FISMA-Moderate IT Security plan Risk Assessment Contingency Plan, helping multiple missions share the cost of compliance with agency-mandated directives.The SPOCC architecture provides science payload control centers and backup mission operations centers with a cost-effective, standardized approach to virtualizing and monitoring resources that were traditionally multiple racks full of physical machines. The increased agility in deploying new virtual systems and thin client workstations can provide significant savings in personnel costs for maintaining the ground system. The cost savings in procurement, power, rack footprint and cooling as well as the shared multi-mission design greatly reduces upfront cost for missions moving into the facility. Overall, the authors hope that this architecture will become a model for how future NASA operations centers are constructed!

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.

The Traverse Planning Process for the Drats 2010 Analog Field Simulations

NASA Technical Reports Server (NTRS)

Horz, Friedrich; Gruener, John; Lofgren, Gary; Skinner, James A., Jr.; Graf, Jodi; Seibert, Marc

2011-01-01

Traverse planning concentrates on optimizing the science return within the overall objectives of planetary surface missions or their analog field simulations. Such simulations were conducted in the San Francisco Volcanic Field, northern Arizona, from Aug. 26 to Sept 17, 2010 and involved some 200 individuals in the field, with some 40 geoscientists composing the science team. The purpose of these Desert Research and Technology Studies (DRATS) is to exercise and evaluate developmental hardware, software and operational concepts in a mission-like, fully-integrated, setting under the direction of an onsite Mobile Mission Control Center(MMCC). DRATS 2010 focused on the simultaneous operation of 2 rovers, a historic first. Each vehicle was manned by an astronaut-commander and an experienced field geologist. Having 2 rovers and crews in the field mandated substantially more complex science and mission control operations compared to the single rover DRATS tests of 2008 and 2009, or the Apollo lunar missions. For instance, the science support function was distributed over 2 "back rooms", one for each rover, with both "tactical" teams operating independently and simultaneously during the actual traverses. Synthesis and integration of the daily findings and forward planning for the next day(s) was accomplished overnight by yet another "strategic" science team.

Mission Level Autonomy for USSV

NASA Technical Reports Server (NTRS)

Huntsberger, Terry; Stirb, Robert C.; Brizzolara, Robert

2011-01-01

On-water demonstration of a wide range of mission-proven, advanced technologies at TRL 5+ that provide a total integrated, modular approach to effectively address the majority of the key needs for full mission-level autonomous, cross-platform control of USV s. Wide baseline stereo system mounted on the ONR USSV was shown to be an effective sensing modality for tracking of dynamic contacts as a first step to automated retrieval operations. CASPER onboard planner/replanner successfully demonstrated realtime, on-water resource-based analysis for mission-level goal achievement and on-the-fly opportunistic replanning. Full mixed mode autonomy was demonstrated on-water with a seamless transition between operator over-ride and return to current mission plan. Autonomous cooperative operations for fixed asset protection and High Value Unit escort using 2 USVs (AMN1 & 14m RHIB) were demonstrated during Trident Warrior 2010 in JUN 2010

Pumped Fluid Loop Heat Rejection and Recovery Systems for Thermal Control of the Mars Science Laboratory

NASA Technical Reports Server (NTRS)

Bhandari, Pradeep; Birur, Gajanana; Prina, Mauro; Ramirez, Brenda; Paris, Anthony; Novak, Keith; Pauken, Michael

2006-01-01

This viewgraph presentation reviews the heat rejection and heat recovery system for thermal control of the Mars Science Laboratory (MSL). The MSL mission will use mechanically pumped fluid loop based architecture for thermal control of the spacecraft and rover. The architecture is designed to harness waste heat from an Multi Mission Radioisotope Thermo-electric Generator (MMRTG) during Mars surface operations for thermal control during cold conditions and also reject heat during the cruise aspect of the mission. There are several test that are being conducted that will insure the safety of this concept. This architecture can be used during any future interplanetary missions utilizing radioisotope power systems for power generation.

Team Modelling: Survey of Experimental Platforms (Modelisation d’equipes : Examen de plate-formes experimentales)

DTIC Science & Technology

2006-09-01

Control Force Agility Shared Situational Awareness Attentional Demand Interoperability Network Based Operations Effect Based Operations Speed of...Command Self Synchronization Reach Back Reach Forward Information Superiority Increased Mission Effectiveness Humansystems® Team Modelling...communication effectiveness and Distributed Mission Training (DMT) effectiveness . The NASA Ames Centre - Distributed Research Facilities platform could

A Challenging Trio in Space 'Routine' Operations of the Swarm Satellite Constellation

NASA Astrophysics Data System (ADS)

Diekmann, Frank-Jurgen; Clerigo, Ignacio; Albini, Giuseppe; Maleville, Laurent; Neto, Alessandro; Patterson, David; Nino, Ana Piris; Sieg, Detlef

2016-08-01

Swarm is the first ESA Earth Observation Mission with three satellites flying in a semi-controlled constellation. The trio is operated from ESA's satellite control centre ESOC in Darmstadt, Germany. The Swarm Flight Operations Segment consists of the typical elements of a satellite control system at ESOC, but had to be carefully tailored for this innovative mission. The main challenge was the multi-satellite system of Swarm, which necessitated the development of a Mission Control System with a multi-domain functionality, both in hardware and software and covering real-time and backup domains. This was driven by the need for extreme flexibility for constellation operations and parallel activities.The three months of commissioning in 2014 were characterized by a very tight and dynamically changing schedule of activities. All operational issues could be solved during that time, including the challenging orbit acquisition phase to achieve the final constellation.Although the formal spacecraft commissioning phase was concluded in spring 2014, the investigations for some payload instruments continue even today. The Electrical Field Instruments are for instance still being tested in order to characterize and improve science data quality. Various test phases also became necessary for the Accelerometers on the Swarm satellites. In order to improve the performance of the GPS Receivers for better scientific exploitation and to minimize the failures due to loss of synchronization, a number of parameter changes were commanded via on-board patches.Finally, to minimize the impact on operations, a new strategy had to be implemented to handle single/multi bit errors in the on-board mass Memories, defining when to ignore and when to restore the memory via a re-initialisation.The poster presentation summarizes the Swarm specific ground segment elements of the FOS and explains some of the extended payload commissioning operations, turning Swarm into a most demanding and challenging mission for the Flight Control Team at ESOC.

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.

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.

Mars Observer screen display design for a multimission environment

NASA Technical Reports Server (NTRS)

Chafin, Roy L.

1993-01-01

The Multi Mission Control Team (MMCT) is responsible for support to real time operations of the Mars Observer Mission. The team has the responsibility for monitoring the ground data system for the integrity of the telemetry and command data links. It also supports the Mars Observers Spacecraft Team in monitoring spacecraft events. The Data Monitor and Display subsystem (DMD) workstation provides the data interface with the ground data system. DMD workstation displays were developed to support the Mission Controllers in accomplishing their assigned tasks for supporting the Mars Observer mission. The display design concepts that were used in the Mar Observer MMCT displays to minimize the cognitive demands on the controllers and enhance the MMCT operations were presented. The Data Monitor and Display subsystem (DMD) is the controllers window into the spacecraft and the ground data system. The DMD is a workstation that provides a variety of formatted data displays to the controller. The displays present both spacecraft telemetry data and ground system monitor data. Some displays are preplanned and developed prior to the operations in which they are used. These are called fixed displays and are quite versatile in format and content. Other displays and plots can be created in real time. These displays have limited formats but flexibility in content. These are called list or message displays. They can be rapidly generated by the controller as needed. The MMCT display repertoire provides a mix of displays appropriate to the needs of the MMCT controllers.

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.

PRIMA Platform capability for satellite missions in LEO and MEO (SAR, Optical, GNSS, TLC, etc.)

NASA Astrophysics Data System (ADS)

Logue, T.; L'Abbate, M.

2016-12-01

PRIMA (Piattaforma Riconfigurabile Italiana Multi Applicativa) is a multi-mission 3-axis stabilized Platform developed by Thales Alenia Space Italia under ASI contract.PRIMA is designed to operate for a wide variety of applications from LEO, MEO up to GEO and for different classes of satellites Platform Family. It has an extensive heritage in flight heritage (LEO and MEO Satellites already fully operational) in which it has successfully demonstrated the flexibility of use, low management costs and the ability to adapt to changing operational conditions.The flexibility and modularity of PRIMA provides unique capability to satisfy different Payload design and mission requirements, thanks to the utilization of recurrent adaptable modules (Service Module-SVM, Propulsion Module-PPM, Payload Module-PLM) to obtain mission dependent configuration. PRIMA product line development is continuously progressing, and is based on state of art technology, modular architecture and an Integrated Avionics. The aim is to maintain and extent multi-mission capabilities to operate in different environments (LEO to GEO) with different payloads (SAR, Optical, GNSS, TLC, etc.). The design is compatible with a wide range of European and US equipment suppliers, thus maximising cooperation opportunity. Evolution activities are mainly focused on the following areas: Structure: to enable Spacecraft configurations for multiple launch; Thermal Control: to guarantee thermal limits for new missions, more demanding in terms of environment and payload; Electrical: to cope with higher power demand (e.g. electrical propulsion, wide range of payloads, etc.) considering orbital environment (e.g. lighting condition); Avionics : AOCS solutions optimized on mission (LEO observation driven by agility and pointing, agility not a driver for GEO). Use of sensors and actuators tailored for specific mission and related environments. Optimised Propulsion control. Data Handling, SW and FDIR mission customization, ensuring robust storage and downlink capability, long lasting autonomy and flexible operations in all mission phases, nominal and non-nominal conditions. This paper starting from PRIMA flight achievements will then outline PRIMA family multi-purpose features addressed to meet multi mission requirements.

Interactive mission planning for a Space Shuttle flight experiment - A case history

NASA Technical Reports Server (NTRS)

Harris, H. M.

1986-01-01

Scientific experiments which use the Space Shuttle as a platform require the development of new operations techniques for the command and control of the instrument. Principal among these is the ability to simulate the complex maneuvers of the orbiter's path realistically. Computer generated graphics provide a window into the actual and predicted performance of the instrument and allow sophisticated control of the instrument under varying conditions. In October of 1984 the Shuttle carried a synthetic aperture radar built by JPL for the purpose of recording images of the earth surface. The mission deviated from planned operation in almost every conceivable way and provided an exacting test bed for concepts of interactive mission planning.

Renewing solar science: The solar maximum repair mission

NASA Technical Reports Server (NTRS)

Neal, V.

1985-01-01

The purpose of the Solar Maximum Repair Mission is to restore the operational capacity of the satellite by replacing the attitude control system module and servicing two of the scientific instruments on board. The mission will demonstrate the satellite servicing capacity of the Space Shuttle for the first time.

Staffing the ISS Control Centers: Lessons Learned from Long-Duration Human Space Flight

NASA Technical Reports Server (NTRS)

Olsen, Carrie D.; Horvath, Timothy J.; Davis, Sally P.

2006-01-01

The International Space Station (ISS) has been in operation with a permanent human presence in space for over five years, and plans for continued operations stretch ten years into the future. Ground control and support operations are, likewise, a 15-year enterprise. This long-term, 24-hour per day, 7 day per week support has presented numerous challenges in the areas of ground crew training, initial and continued certification, and console staffing. The Mission Control Center in Houston, Texas and the Payload Operations Center in Huntsville, Alabama have both tackled these challenges, with similar, yet distinct, approaches. This paper describes the evolution of the staffing and training policies of both control centers in a chronological progression. The relative merits and shortcomings of the various policies employed are discussed and a summary of "lessons learned" is presented. Finally, recommendations are made as best practices for future long-term space missions.

Deployer Performance Results for the TSS-1 Mission

NASA Technical Reports Server (NTRS)

Marshall, Leland S.; Geiger, Ronald V.

1995-01-01

Performance of the Tethered Satellite System (TSS) Deployer during the STS-46 mission (July and August 1992) is analyzed in terms of hardware operation at the component and system level. Although only a limited deployment of the satellite was achieved (256 meters vs 20 kilometers planned), the mission served to verify the basic capability of the Deployer to release, control and retrieve a tethered satellite. - Deployer operational flexibility that was demonstrated during the flight is also addressed. Martin Marietta was the prime contractor for the development of the Deployer, under management of the NASA George C. Marshall Space Flight Center (MSFC). The satellite was provided by Alenia, Torino, Italy under contract to the Agencia Spaziale Italiana (ASI). Proper operation of the avionics components and the majority of mechanisms was observed during the flight. System operations driven by control laws for the deployment and retrieval of the satellite were also successful for the limited deployment distance. Anomalies included separation problems for one of the two umbilical connectors between the Deployer and satellite, tether jamming (at initial Satellite fly-away and at a deployment distance of 224 meters), and a mechanical interference which prevented tether deployment beyond 256 meters. The Deployer was used in several off-nominal conditions to respond to these anomalies, which ultimately enabled a successful satellite retrieval and preservation of hardware integrity for a future re-flight. The paper begins with an introduction defining the significance of the TSS-1 mission. The body of the paper is divided into four major sections: (1) Description of Deployer System and Components, (2) Deployer Components/Systems Demonstrating Successful Operation, (3) Hardware Anomalies and Operational Responses, and (4) Design Modifications for the TSS-1R Re-flight Mission. Conclusions from the TSS-1 mission, including lessons learned are presented at the end of the manuscript.

Training and Tactical Operationally Responsive Space Operations

NASA Astrophysics Data System (ADS)

Sorensen, B.; Strunce, R., Jr.

Current space assets managed by traditional space system control resources provide communication, navigation, intelligence, surveillance, and reconnaissance (ISR) capabilities using satellites that are designed for long life and high reliability. The next generation Operationally Responsive Space (ORS) systems are aimed at providing operational space capabilities which will provide flexibility and responsiveness to the tactical battlefield commander. These capabilities do not exist today. The ORS communication, navigation, and ISR satellites are being designed to replace or supplement existing systems in order to enhance the current space force. These systems are expected to rapidly meet near term space needs of the tactical forces. The ORS concept includes new tactical satellites specifically designed to support contingency operations such as increased communication bandwidth and ISR imagery over the theater for a limited period to support air, ground, and naval force mission. The Concept of Operations (CONOPS) that exists today specifies that in addition to operational control of the satellite, the tasking and scheduling of the ORS tactical satellite for mission data collection in support of the tactical warfighter will be accomplished within the Virtual Mission Operations Center (VMOC). This is very similar to what is currently being accomplished in a fixed Mission Operations Center on existing traditional ISR satellites. The VMOC is merely a distributed environment and the CONOPS remain virtually the same. As a result, there is a significant drawback to the current ORS CONOPS that does not account for the full potential of the ORS paradigm for supporting tactical forces. Although the CONOPS approach may be appropriate for experimental Tactical Satellites (TacSat), it ignores the issues associated with the In-Theater Commander's need to own and operate his dedicated TacSat for most effective warfighting as well as the Warfighter specific CONOPS. What is needed to realize the full potential of the ORS approach to the support of in-theater tactical forces is the development of satellite tasking, interface, and data retrieval capabilities and mission operations approaches from a warfighter centered perspective, and the development of realistic training and simulation capabilities that will allow development, demonstration, and assessment of ORS tactical CONOPS. A system for Training and Tactical ORS Operations (TATOO) is currently being developed. This system will support development and evaluation of ORS specific CONOPS approaches, and training and evaluation of those CONOPS implementations through dedicated training capabilities, facilities, and exercises. TATOO will support the operational side of ORS and will merge with the revolutionary ORS spacecraft development and deployment processes to make the ORS paradigm a reality. TATOO's primary objective is to support the In-Theater Commander and Warfighter by developing, training, and assessing ORS mission CONOPS for In-Theater tasking, scheduling, interface, and data retrieval for TacSats owned by In-Theater Commanders. TATOO provides a laboratory/classroom environment for the development, test and evaluation of ORS Tactical Mission CONOPS for In-Theater ORS operations. The TATOO laboratory will also be used to develop, evaluate, and document ORS Mission CONOPS for tactical ISR and other ORS missions. Within this framework, the laboratory/classroom can be used to develop the necessary training materials and procedures, as well as conduct training exercises that emphasize the training of In-Theater personal with regard to: Tactical Ground Station Mission Operations; Tactical Operations for Mission Tasking and Scheduling; Tactical Mission Data Retrieval; and, Support for Warfighter Operations.

Continuous Improvements to East Coast Abort Landings for Space Shuttle Aborts

NASA Technical Reports Server (NTRS)

Butler, Kevin D.

2003-01-01

Improvement initiatives in the areas of guidance, flight control, and mission operations provide increased capability for successful East Coast Abort Landings (ECAL). Automating manual crew procedures in the Space Shuttle's onboard guidance allows faster and more precise commanding of flight control parameters needed for successful ECALs. Automation also provides additional capability in areas not possible with manual control. Operational changes in the mission concept allow for the addition of new landing sites and different ascent trajectories that increase the regions of a successful landing. The larger regions of ECAL capability increase the safety of the crew and Orbiter.

Monitor and Control of the Deep-Space network via Secure Web

NASA Technical Reports Server (NTRS)

Lamarra, N.

1997-01-01

(view graph) NASA lead center for robotic space exploration. Operating division of Caltech/Jet Propulsion Laboratory. Current missions, Voyagers, Galileo, Pathfinder, Global Surveyor. Upcoming missions, Cassini, Mars and New Millennium.

The ISECG* Global Exploration Roadmap as Context for Robotic and Human Exploration Operations

NASA Technical Reports Server (NTRS)

Lupisella, Mark

2015-01-01

The International Space Exploration Coordination Group (ISECG) Global Exploration Roadmap (GER) provides a broad international context for understanding how robotic missions and robotic assets can enable future human exploration of multiple destinations. This presentation will provide a brief high-level review of the GER with a focus on key robotic missions and robotic assets that can provide enabling technology advancements and that also raise interesting operational challenges in both the near-term and long-term. The GER presently features a variety of robotic missions and robotic assets that can provide important technology advancements as well as operational challenges and improvements, in areas ranging from: (a) leveraging the International Space Station, (b) planetary science robotic missions to potential human destinations, (c) micro-g body proximity operations (e.g. asteroids), (d) autonomous operations, (e) high and low-latency telerobotics, (f) human assisted sample return, and (g) contamination control. This presentation will highlight operational and technology challenges in these areas that have feed forward implications for human exploration.

Laser Threat Analysis System (LTAS)

NASA Astrophysics Data System (ADS)

Pfaltz, John M.; Richardson, Christina E.; Ruiz, Abel; Barsalou, Norman; Thomas, Robert J.

2002-11-01

LTAS is a totally integrated modeling and simulation environment designed for the purpose of ascertaining the susceptibility of Air Force pilots and air crews to optical radiation threats. Using LTAS, mission planners can assess the operational impact of optically directed energy weapons and countermeasures. Through various scenarios, threat analysts are able to determine the capability of laser threats and their impact on operational missions including the air crew's ability to complete their mission effectively. Additionally, LTAS allows the risk of laser use on training ranges and the requirement for laser protection to be evaluated. LTAS gives mission planners and threat analysts complete control of the threat environment including threat parameter control and placement, terrain mapping (line-of-site), atmospheric conditions, and laser eye protection (LEP) selection. This report summarizes the design of the final version of LTAS, and the modeling methodologies implemented to accomplish analysis.

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.

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.

Mental Workload and Performance Experiment (MWPE) Team in the Spacelab Payload Operations Control

NASA Technical Reports Server (NTRS)

1992-01-01

The primary payload for Space Shuttle Mission STS-42, launched January 22, 1992, was the International Microgravity Laboratory-1 (IML-1), a pressurized manned Spacelab module. The goal of IML-1 was to explore in depth the complex effects of weightlessness of living organisms and materials processing. Around-the-clock research was performed on the human nervous system's adaptation to low gravity and effects of microgravity on other life forms such as shrimp eggs, lentil seedlings, fruit fly eggs, and bacteria. Materials processing experiments were also conducted, including crystal growth from a variety of substances such as enzymes, mercury iodide, and a virus. 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. Featured is the Mental Workload and Performance Experiment (MWPE) team in the SL POCC) during STS-42, IML-1 mission.

Mental Workload and Performance Experiment (MWPE) Team in the Spacelab Payload Operations Control

NASA Technical Reports Server (NTRS)

1992-01-01

The primary payload for Space Shuttle Mission STS-42, launched January 22, 1992, was the International Microgravity Laboratory-1 (IML-1), a pressurized manned Spacelab module. The goal of IML-1 was to explore in depth the complex effects of weightlessness of living organisms and materials processing. Around-the-clock research was performed on the human nervous system's adaptation to low gravity and effects of microgravity on other life forms such as shrimp eggs, lentil seedlings, fruit fly eggs, and bacteria. Materials processing experiments were also conducted, including crystal growth from a variety of substances such as enzymes, mercury iodide, and a virus. 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. Featured activities are of the Mental Workload and Performance Experiment (MWPE) team in the SL POCC during the IML-1 mission.

Gravity Plant Physiology Facility (GPPF) Team in the Spacelab Payload Operations Control Center (SL

NASA Technical Reports Server (NTRS)

1992-01-01

The primary payload for Space Shuttle Mission STS-42, launched January 22, 1992, was the International Microgravity Laboratory-1 (IML-1), a pressurized manned Spacelab module. The goal of IML-1 was to explore in depth the complex effects of weightlessness of living organisms and materials processing. Around-the-clock research was performed on the human nervous system's adaptation to low gravity and effects of microgravity on other life forms such as shrimp eggs, lentil seedlings, fruit fly eggs, and bacteria. Materials processing experiments were also conducted, including crystal growth from a variety of substances such as enzymes, mercury iodide, and a virus. 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. Featured is the Gravity Plant Physiology Facility (GPPF) team in the SL POCC during the IML-1 mission.

Critical Point Facility (CPE) Group in the Spacelab Payload Operations Control Center (SL POCC)

NASA Technical Reports Server (NTRS)

1992-01-01

The primary payload for Space Shuttle Mission STS-42, launched January 22, 1992, was the International Microgravity Laboratory-1 (IML-1), a pressurized manned Spacelab module. The goal of IML-1 was to explore in depth the complex effects of weightlessness of living organisms and materials processing. Around-the-clock research was performed on the human nervous system's adaptation to low gravity and effects of microgravity on other life forms such as shrimp eggs, lentil seedlings, fruit fly eggs, and bacteria. Materials processing experiments were also conducted, including crystal growth from a variety of substances such as enzymes, mercury iodide, and a virus. 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. Featured is the Critical Point Facility (CPE) group in the SL POCC during STS-42, IML-1 mission.

Crystal Growth Team in the Spacelab Payload Operations Control Center (SL POCC) During the STS-42

NASA Technical Reports Server (NTRS)

1992-01-01

The primary payload for Space Shuttle Mission STS-42, launched January 22, 1992, was the International Microgravity Laboratory-1 (IML-1), a pressurized manned Spacelab module. The goal of IML-1 was to explore in depth the complex effects of weightlessness of living organisms and materials processing. Around-the-clock research was performed on the human nervous system's adaptation to low gravity and effects of microgravity on other life forms such as shrimp eggs, lentil seedlings, fruit fly eggs, and bacteria. Materials processing experiments were also conducted, including crystal growth from a variety of substances such as enzymes, mercury iodide, and a virus. 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. Featured is the Crystal Growth team in the SL POCC during STS-42, IML-1 mission.

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 multiple NASA Centers, led by NASA Ames Research Center, is building a framework to enable software to be assembled from flexible collections of components and services.

Proceedings of the 20th International Symposium on Space Flight Dynamics

NASA Technical Reports Server (NTRS)

Woodard, Mark (Editor); Stengle, Tom (Editor)

2007-01-01

Topics include: Measuring Image Navigation and Registration Performance at the 3-Sigma Level Using Platinum Quality Landmarks; Flight Dynamics Performances of the MetOp A Satellite during the First Months of Operations; Visual Navigation - SARE Mission; Determining a Method of Enabling and Disabling the Integral Torque in the SDO Science and Inertial Mode Controllers; Guaranteeing Pointing Performance of the SDO Sun-Pointing Controllers in Light of Nonlinear Effects; SDO Delta H Mode Design and Analysis; Observing Mode Attitude Controller for the Lunar Reconnaissance Orbiter; Broken-Plane Maneuver Applications for Earth to Mars Trajectories; ExoMars Mission Analysis and Design - Launch, Cruise and Arrival Analyses; Mars Reconnaissance Orbiter Aerobraking Daily Operations and Collision Avoidance; Mars Reconnaissance Orbiter Interplanetary Cruise Navigation; Motion Parameters Determination of the SC and Phobos in the Project Phobos-Grunt; GRAS NRT Precise Orbit Determination: Operational Experience; Orbit Determination of LEO Satellites for a Single Pass through a Radar: Comparison of Methods; Orbit Determination System for Low Earth Orbit Satellites; Precise Orbit Determination for ALOS; Anti-Collision Function Design and Performances of the CNES Formation Flying Experiment on the PRISMA Mission; CNES Approaching Guidance Experiment within FFIORD; Maneuver Recovery Analysis for the Magnetospheric Multiscale Mission; SIMBOL-X: A Formation Flying Mission on HEO for Exploring the Universe; Spaceborne Autonomous and Ground Based Relative Orbit Control for the TerraSAR-X/TanDEM-X Formation; First In-Orbit Experience of TerraSAR-X Flight Dynamics Operations; Automated Target Planning for FUSE Using the SOVA Algorithm; Space Technology 5 Post-Launch Ground Attitude Estimation Experience; Standardizing Navigation Data: A Status Update; and A Study into the Method of Precise Orbit Determination of a HEO Orbiter by GPS and Accelerometer.

Fault tolerant and lifetime control architecture for autonomous vehicles

NASA Astrophysics Data System (ADS)

Bogdanov, Alexander; Chen, Yi-Liang; Sundareswaran, Venkataraman; Altshuler, Thomas

2008-04-01

Increased vehicle autonomy, survivability and utility can provide an unprecedented impact on mission success and are one of the most desirable improvements for modern autonomous vehicles. We propose a general architecture of intelligent resource allocation, reconfigurable control and system restructuring for autonomous vehicles. The architecture is based on fault-tolerant control and lifetime prediction principles, and it provides improved vehicle survivability, extended service intervals, greater operational autonomy through lower rate of time-critical mission failures and lesser dependence on supplies and maintenance. The architecture enables mission distribution, adaptation and execution constrained on vehicle and payload faults and desirable lifetime. The proposed architecture will allow managing missions more efficiently by weighing vehicle capabilities versus mission objectives and replacing the vehicle only when it is necessary.

2007 Ikhana Western States and Southern California Emergency UAS Fire Missions

NASA Technical Reports Server (NTRS)

Cobleigh, Brent

2008-01-01

Four demonstration and four emergency fire imaging missions completed: a) Thermal infrared imagery delivered in near real-time (5 to 15 minutes) to: 1) SoCal Emergency: FEMA, NIFC, NorthCom, California EOC; 2) Demo Flights: NIFC, Individual Fire Incident Commands. Imagery used for tactical and strategic decision making. Air Traffic Control gave excellent support. Mission plans flown in reverse. Real time requests for revisits of active fires. Added new fire during mission. Moved fire loiter points as fires moved. Real-time reroute around thunderstorm activity. Pre & Post flight telecons with FAA were held to review mission and discuss operational improvements. No issues with air traffic control during the 8 fire missions flown.

A Mars Rover Mission Simulation on Kilauea Volcano

NASA Technical Reports Server (NTRS)

Stoker, Carol; Cuzzi, Jeffery N. (Technical Monitor)

1995-01-01

A field experiment to simulate a rover mission on Mars was performed using the Russian Marsokhod rover deployed on Kilauea Volcano HI in February, 1995. A Russian Marsokhod rover chassis was equipped with American avionics equipment, stereo cameras on a pan and tilt platform, a digital high resolution body-mounted camera, and a manipulator arm on which was mounted a camera with a close-up lens. The six wheeled rover is 2 meters long and has a mass of 120 kg. The imaging system was designed to simulate that used on the planned "Mars Together" mission. The rover was deployed on Kilauea Volcano HI and operated from NASA Ames by a team of planetary geologists and exobiologists. Two modes of mission operations were simulated for three days each: (1) long time delay, low data bandwidth (simulating a Mars mission), and (2) live video, wide-bandwidth data (allowing active control simulating a Lunar rover mission or a Mars rover mission controlled from on or near the Martian surface). Simulated descent images (aerial photographs) were used to plan traverses to address a detailed set of science questions. The actual route taken was determined by the science team and the traverse path was frequently changed in response to the data acquired and to unforeseen operational issues. Traverses were thereby optimized to efficiently answer scientific questions. During the Mars simulation, the rover traversed a distance of 800 m. Based on the time delay between Earth and Mars, we estimate that the same operation would have taken 30 days to perform on Mars. This paper will describe the mission simulation and make recommendations about incorporating rovers into the Mars surveyor program.

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.

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

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.

Screening studies of advanced control concepts for airbreathing engines

NASA Technical Reports Server (NTRS)

Ouzts, Peter J.; Lorenzo, Carl F.; Merrill, Walter C.

1993-01-01

The application of advanced control concepts to airbreathing engines may yield significant improvements in aircraft/engine performance and operability. Accordingly, the NASA Lewis Research Center has conducted screening studies of advanced control concepts for airbreathing engines to determine their potential impact on turbine engine performance and operability. The purpose of the studies was to identify concepts which offered high potential yet may incur high research and development risk. A target suite of proposed concepts was formulated by NASA and industry. These concepts were evaluated in a two phase study to quantify each concept's impact on desired engine characteristics. To aid in the evaluation, three target aircraft/engine combinations were considered: a military high performance fighter mission, a high speed civil transport mission, and a civil tiltrotor mission. Each of the advanced control concepts considered in the study were defined and described. The concept's potential impact on engine performance was determined. Relevant figures of merit on which to evaluate the concepts were also determined. Finally, the concepts were ranked with respect to the target aircraft/engine missions.

Lessons Learned for Planning and Estimating Operations Support Requirements

NASA Technical Reports Server (NTRS)

Newhouse, Marilyn

2011-01-01

Operations (phase E) costs are typically small compared to the spacecraft development and test costs. This, combined with the long lead time for realizing operations costs, can lead projects to focus on hardware development schedules and costs, de-emphasizing estimation of operations support requirements during proposal, early design, and replan cost exercises. The Discovery and New Frontiers (D&NF) programs comprise small, cost-capped missions supporting scientific exploration of the solar system. Even moderate yearly underestimates of the operations costs can present significant LCC impacts for deep space missions with long operational durations, and any LCC growth can directly impact the programs ability to fund new missions. The D&NF Program Office at Marshall Space Flight Center recently studied cost overruns for 7 D&NF missions related to phase C/D development of operational capabilities and phase E mission operations. The goal was to identify the underlying causes for the overruns and develop practical mitigations to assist the D&NF projects in identifying potential operations risks and controlling the associated impacts to operations development and execution costs. The study found that the drivers behind these overruns include overly optimistic assumptions regarding the savings resulting from the use of heritage technology, late development of operations requirements, inadequate planning for sustaining engineering and the special requirements of long duration missions (e.g., knowledge retention and hardware/software refresh), and delayed completion of ground system development work. This presentation summarizes the study and the results, providing a set of lessons NASA can use to improve early estimation and validation of operations costs.

ISS Solar Array Management

NASA Technical Reports Server (NTRS)

Williams, James P.; Martin, Keith D.; Thomas, Justin R.; Caro, Samuel

2010-01-01

The International Space Station (ISS) Solar Array Management (SAM) software toolset provides the capabilities necessary to operate a spacecraft with complex solar array constraints. It monitors spacecraft telemetry and provides interpretations of solar array constraint data in an intuitive manner. The toolset provides extensive situational awareness to ensure mission success by analyzing power generation needs, array motion constraints, and structural loading situations. The software suite consists of several components including samCS (constraint set selector), samShadyTimers (array shadowing timers), samWin (visualization GUI), samLock (array motion constraint computation), and samJet (attitude control system configuration selector). It provides high availability and uptime for extended and continuous mission support. It is able to support two-degrees-of-freedom (DOF) array positioning and supports up to ten simultaneous constraints with intuitive 1D and 2D decision support visualizations of constraint data. Display synchronization is enabled across a networked control center and multiple methods for constraint data interpolation are supported. Use of this software toolset increases flight safety, reduces mission support effort, optimizes solar array operation for achieving mission goals, and has run for weeks at a time without issues. The SAM toolset is currently used in ISS real-time mission operations.

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.

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.

Battery Control Boards for Li-Ion Batteries on Mars Exploration Rovers

NASA Technical Reports Server (NTRS)

Ewell, R.; Ratnakumar, B. V.; Smart, M.; Chin, K. B.; Whitcanack, L.; Narayanan, S. R.; Surampudi, S.

2006-01-01

Rechargeable Lithium-ion batteries have been operating successfully on both Spirit and Opportunity rovers for the last two years, which includes six months of Assembly Launch and Test Operations (ATLO), seven months of cruise and about eleven months of surface operations. The Battery Control Boards designed and fabricated in-house would protect cells against overcharge and over-discharge and provide cell balance. Their performance has thus far been quite satisfactory. The ground data o the mission simulation battery project little capacity loss of less than 3% during cruise and 180 sols. Batteries are poised to extend the mission beyond six months, if not a couple of years.

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.

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.

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.

Space Operations

DTIC Science & Technology

2009-01-06

enabling precise blue force tracking (BFT), enhancing joint force situational awareness, maneuverability, and command and control (C2... spacecraft , transmits the status of those systems to the control segment on the ground, and receives and processes instructions from the control segment...missions include the tracking , telemetry, and control operations of: (1) Ultrahigh frequency (UHF) follow-on satellite system and fleet

Moon and Mars Analog Mission Activities for Mauna Kea 2012

NASA Technical Reports Server (NTRS)

Graham, Lee D.; Morris, Richard V.; Graff, Trevor G.; Yingst, R. Aileen; tenKate, I. L.; Glavin, Daniel P.; Hedlund, Magnus; Malespin, Charles A.; Mumm, Erik

2012-01-01

Rover-based 2012 Moon and Mars Analog Mission Activities (MMAMA) scientific investigations were recently completed at Mauna Kea, Hawaii. Scientific investigations, scientific input, and science operations constraints were tested in the context of an existing project and protocols for the field activities designed to help NASA achieve the Vision for Space Exploration. Initial science operations were planned based on a model similar to the operations control of the Mars Exploration Rovers (MER). However, evolution of the operations process occurred as the analog mission progressed. We report here on the preliminary sensor data results, an applicable methodology for developing an optimum science input based on productive engineering and science trades discussions and the science operations approach for an investigation into the valley on the upper slopes of Mauna Kea identified as "Apollo Valley".

Spacelab Operations Support Room Space Engineering Support Team in the SL POCC During the IML-1

NASA Technical Reports Server (NTRS)

1992-01-01

The primary payload for Space Shuttle Mission STS-42, launched January 22, 1992, was the International Microgravity Laboratory-1 (IML-1), a pressurized manned Spacelab module. The goal of IML-1 was to explore in depth the complex effects of weightlessness of living organisms and materials processing. Around-the-clock research was performed on the human nervous system's adaptation to low gravity and effects of microgravity on other life forms such as shrimp eggs, lentil seedlings, fruit fly eggs, and bacteria. Materials processing experiments were also conducted, including crystal growth from a variety of substances such as enzymes, mercury iodide, and a virus. 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. Featured is the Spacelab Operations Support Room Space Engineering Support team in the SL POCC during STS-42, IML-1 mission.

BEARS: a multi-mission anomaly response system

NASA Astrophysics Data System (ADS)

Roberts, Bryce A.

2009-05-01

The Mission Operations Group at UC Berkeley's Space Sciences Laboratory operates a highly automated ground station and presently a fleet of seven satellites, each with its own associated command and control console. However, the requirement for prompt anomaly detection and resolution is shared commonly between the ground segment and all spacecraft. The efficient, low-cost operation and "lights-out" staffing of the Mission Operations Group requires that controllers and engineers be notified of spacecraft and ground system problems around the clock. The Berkeley Emergency Anomaly and Response System (BEARS) is an in-house developed web- and paging-based software system that meets this need. BEARS was developed as a replacement for an existing emergency reporting software system that was too closedsource, platform-specific, expensive, and antiquated to expand or maintain. To avoid these limitations, the new system design leverages cross-platform, open-source software products such as MySQL, PHP, and Qt. Anomaly notifications and responses make use of the two-way paging capabilities of modern smart phones.

Real time data acquisition for expert systems in Unix workstations at Space Shuttle Mission Control

NASA Technical Reports Server (NTRS)

Muratore, John F.; Heindel, Troy A.; Murphy, Terri B.; Rasmussen, Arthur N.; Gnabasik, Mark; Mcfarland, Robert Z.; Bailey, Samuel A.

1990-01-01

A distributed system of proprietary engineering-class workstations is incorporated into NASA's Space Shuttle Mission-Control Center to increase the automation of mission control. The Real-Time Data System (RTDS) allows the operator to utilize expert knowledge in the display program for system modeling and evaluation. RTDS applications are reviewed including: (1) telemetry-animated communications schematics; (2) workstation displays of systems such as the Space Shuttle remote manipulator; and (3) a workstation emulation of shuttle flight instrumentation. The hard and soft real-time constraints are described including computer data acquisition, and the support techniques for the real-time expert systems include major frame buffers for logging and distribution as well as noise filtering. The incorporation of the workstations allows smaller programming teams to implement real-time telemetry systems that can improve operations and flight testing.

System Design and Performance of the Two-Gyro Science Mode For the Hubble Space Telescope

NASA Technical Reports Server (NTRS)

Prior, Michael; Dunham, Larry

2005-01-01

For fifteen years, the science mission of the Hubble Space Telescope (HST) required using at least three of the six on-board rate gyros for attitude control. Failed gyros were eventually replaced through Space Shuttle Servicing Missions. The tragic loss of the Space Shuttle Columbia has resulted in the cancellation of all planned Shuttle based missions to HST. While a robotic servicing mission is currently being planned instead, controlling with alternate sensors to replace failed gyros can extend the HST science gathering until a servicing mission can be performed, and also extend science at HST's end of life. Additionally, sufficient performance may allow a permanent transition to operations with less than 3 gyros (by intentionally turning off working gyros saving them for later use) allowing for an even greater science mission extension. To meet this need, a Two Gyro Science (TGS) mode has been designed and implemented using magnetometers (Magnetic Sensing System - MSS), Fixed Head Star Trackers (FHSTs), and Fine Guidance Sensors (FGSs) to control vehicle rate about the missing gyro input axis. The development of the TGS capability is the largest re-design of HST operations undertaken, since it affects several major spacecraft subsystems, the most heavily being the Pointing Control System (PCS) and Flight Software (FSW). Additionally, and equally important, are the extensive modifications and enhancements of the Planning and Scheduling system which must now be capable of scheduling science observations while taking into account several new constraints imposed by the TGS operational modes (such as FHST availability and magnetic field geometry) that will impact science gathering efficiency and target availability. This paper discusses the systems engineering design, development, and performance of the TGS mode, now in its final stages of completion.

System Design and Performance of the Two-Gyro Science Mode For the Hubble Space Telescope

NASA Technical Reports Server (NTRS)

Prior, Michael; Dunham, Larry

2005-01-01

For fifteen years, the science mission of the Hubble Space Telescope (HST) required using at least three of the six on-board rate gyros for attitude control. Failed gyros were eventually replaced through Space Shuttle Servicing Missions. The tragic loss of the Space Shuttle Columbia has resulted in the cancellation of all planned Shuttle based missions to HST. While a robotic servicing mission is currently being planned instead, controlling with alternate sensors to replace failed gyros can extend the HST science gathering until a servicing mission can be performed, and also extend science at HST s end of life. Additionally, sufficient performance may allow a permanent transition to operations with less than 3 gyros (by intentionally turning off working gyros saving them for later use) allowing for an even greater science mission extension. To meet this need, a Two Gyro Science (TGS) mode has been designed and implemented using magnetometers (Magnetic Sensing System - MSS), Fixed Head Star Trackers (FHSTs), and Fine Guidance Sensors (FGSs) to control vehicle rate about the missing gyro input axis. The development of the TGS capability is the largest re-design of HST operations undertaken, since it affects several major spacecraft subsystems, the most heavily being the Pointing Control System (PCS) and Flight Software (FSW). Additionally, and equally important, are the extensive modifications and enhancements of the Planning and Scheduling system which must now be capable of scheduling science observations while taking into account several new constraints imposed by the TGS operational modes (such as FHST availability and magnetic field geometry) that will impact science gathering efficiency and target availability. This paper discusses the systems engineering design, development, and performance of the TGS mode, now in its final stages of completion.

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.

BMDS/SSA Integrated Sensing Demonstration (BISD)

NASA Astrophysics Data System (ADS)

Turner, T.; Springford, K.; Grimaldi, L.

2011-09-01

This demonstration is intended to provide a near-term prototype, leave-behind capability for integrating Ballistic Missile Defense System (BMDS) ground sensors for use in the Space Situational Awareness (SSA) mission. Closed-loop tasking and cueing capability will be implemented, and a demonstration of net-centric space data dissemination using the BMDS sensors will be undertaken using various SSA mission threads. The demonstration is designed to highlight the implications of modifying software and/or hardware at the BMDS command and control node so that cost, risk, and schedule for an operational implementation can be fully understood. Additionally, this demonstration is intended to assess the impacts to both mission areas as a multi-mission, non-traditional sensor capability is integrated into the SSA mission. A successful demonstration will have many leave-behind capabilities and first-of-its-kind achievements to include: a) an extensible SSA operational prototype configuration for BMDS X-Band radars such as AN/TPY-2 and Sea-Based X-Band (SBX) b) a prototype SSA tasking and cueing capability between the Joint Functional Component Command for Space (JFCC Space) Joint Space Operations Center (JSpOC) and the Command, Control, Battle Management, and Communications (C2BMC) Experimental Laboratory (X-Lab), extensible to the Combatant Commands (COCOMS), and out to BMDS sensors c) a capability for a twoway, net-centric, interface for JSpOC space operations, to include translation from net-centric communications to legacy systems and d) processing of BMDS X-Band Radar tracks in the Space Defense Operations Center (SPADOC).

Around Marshall

NASA Image and Video Library

1992-01-28

The primary payload for Space Shuttle Mission STS-42, launched January 22, 1992, was the International Microgravity Laboratory-1 (IML-1), a pressurized manned Spacelab module. The goal of IML-1 was to explore in depth the complex effects of weightlessness of living organisms and materials processing. Around-the-clock research was performed on the human nervous system's adaptation to low gravity and effects of microgravity on other life forms such as shrimp eggs, lentil seedlings, fruit fly eggs, and bacteria. Materials processing experiments were also conducted, including crystal growth from a variety of substances such as enzymes, mercury iodide, and a virus. 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. Featured is the Spacelab Operations Support Room Space Engineering Support team in the SL POCC during STS-42, IML-1 mission.

Autonomous Control of Space Reactor Systems

DOE Office of Scientific and Technical Information (OSTI.GOV)

Belle R. Upadhyaya; K. Zhao; S.R.P. Perillo

2007-11-30

Autonomous and semi-autonomous control is a key element of space reactor design in order to meet the mission requirements of safety, reliability, survivability, and life expectancy. Interrestrial nuclear power plants, human operators are avilable to perform intelligent control functions that are necessary for both normal and abnormal operational conditions.

Advanced controls for airbreathing engines, volume 3: Allison gas turbine

NASA Technical Reports Server (NTRS)

Bough, R. M.

1993-01-01

The application of advanced control concepts to airbreathing engines may yield significant improvements in aircraft/engine performance and operability. Screening studies of advanced control concepts for airbreathing engines were conducted by three major domestic aircraft engine manufacturers to determine the potential impact of concepts on turbine engine performance and operability. The purpose of the studies was to identify concepts which offered high potential yet may incur high research and development risk. A target suite of proposed advanced control concepts was formulated and evaluated in a two-phase study to quantify each concept's impact on desired engine characteristics. To aid in the evaluation specific aircraft/engine combinations were considered: a Military High Performance Fighter mission, a High Speed Civil Transport mission, and a Civil Tiltrotor mission. Each of the advanced control concepts considered in the study are defined and described. The concept potential impact on engine performance was determined. Relevant figures of merit on which to evaluate the concepts are determined. Finally, the concepts are ranked with respect to the target aircraft/engine missions. A final report describing the screening studies was prepared by each engine manufacturer. Volume 3 of these reports describes the studies performed by the Allison Gas Turbine Division.

Advanced control for airbreathing engines, volume 1: Pratt and Whitney

NASA Technical Reports Server (NTRS)

Ralph, J. A.

1993-01-01

The application of advanced control concepts to air breathing engines may yield significant improvements in aircraft/engine performance and operability. Screening studies of advanced control concepts for air breathing engines were conducted by three major domestic aircraft engine manufacturers to determine the potential impact of concepts on turbine engine performance and operability. The purpose of the studies was to identify concepts which offered high potential yet may incur high research and development risk. A target suite of proposed advanced control concepts was formulated and evaluated in a two phase study to quantify each concept's impact on desired engine characteristics. To aid in the evaluation specific aircraft/engine combinations were considered: a Military High Performance Fighter mission, a High Speed Civil Transport mission, and a Civil Tiltrotor mission. Each of the advanced control concepts considered in the study are defined and described. The concept potential impact on engine performance was determined. Relevant figures of merit on which to evaluate the concepts are determined. Finally, the concepts are ranked with respect to the target aircraft/engine missions. A final report describing the screening studies was prepared by each engine manufacturer. Volume 1 of these reports describes the studies performed by Pratt & Whitney.

Advanced control for airbreathing engines, volume 2: General Electric aircraft engines

NASA Technical Reports Server (NTRS)

Bansal, Indar

1993-01-01

The application of advanced control concepts to air breathing engines may yield significant improvements in aircraft/engine performance and operability. Screening studies of advanced control concepts for air breathing engines were conducted by three major domestic aircraft engine manufacturers to determine the potential impact of concepts on turbine engine performance and operability. The purpose of the studies was to identify concepts which offered high potential yet may incur high research and development risk. A target suite of proposed advanced control concepts was formulated and evaluated in a two phase study to quantify each concept's impact on desired engine characteristics. To aid in the evaluation specific aircraft/engine combinations were considered: a Military High Performance Fighter mission, a High Speed Civil Transport mission, and a Civil Tiltrotor mission. Each of the advanced control concepts considered in the study are defined and described. The concept potential impact on engine performance was determined. Relevant figures of merit on which to evaluate the concepts are determined. Finally, the concepts are ranked with respect to the target aircraft/engine missions. A final report describing the screening studies was prepared by each engine manufacturer. Volume 2 of these reports describes the studies performed by GE Aircraft Engines.

Advanced Autonomous Systems for Space Operations

NASA Astrophysics Data System (ADS)

Gross, A. R.; Smith, B. D.; Muscettola, N.; Barrett, A.; Mjolssness, E.; Clancy, D. J.

2002-01-01

New missions of exploration and space operations will require unprecedented levels of autonomy to successfully accomplish their objectives. Inherently high levels of complexity, cost, and communication distances will preclude the degree of human involvement common to current and previous space flight missions. With exponentially increasing capabilities of computer hardware and software, including networks and communication systems, a new balance of work is being developed between humans and machines. This new balance holds the promise of not only meeting the greatly increased space exploration requirements, but simultaneously dramatically reducing the design, development, test, and operating costs. New information technologies, which take advantage of knowledge-based software, model-based reasoning, and high performance computer systems, will enable the development of a new generation of design and development tools, schedulers, and vehicle and system health management capabilities. Such tools will provide a degree of machine intelligence and associated autonomy that has previously been unavailable. These capabilities are critical to the future of advanced space operations, since the science and operational requirements specified by such missions, as well as the budgetary constraints will limit the current practice of monitoring and controlling missions by a standing army of ground-based controllers. System autonomy capabilities have made great strides in recent years, for both ground and space flight applications. Autonomous systems have flown on advanced spacecraft, providing new levels of spacecraft capability and mission safety. Such on-board systems operate by utilizing model-based reasoning that provides the capability to work from high-level mission goals, while deriving the detailed system commands internally, rather than having to have such commands transmitted from Earth. This enables missions of such complexity and communication` distances as are not otherwise possible, as well as many more efficient and low cost applications. In addition, utilizing component and system modeling and reasoning capabilities, autonomous systems will play an increasing role in ground operations for space missions, where they will both reduce the human workload as well as provide greater levels of monitoring and system safety. This paper will focus specifically on new and innovative software for remote, autonomous, space systems flight operations. Topics to be presented will include a brief description of key autonomous control concepts, the Remote Agent program that commanded the Deep Space 1 spacecraft to new levels of system autonomy, recent advances in distributed autonomous system capabilities, and concepts for autonomous vehicle health management systems. A brief description of teaming spacecraft and rovers for complex exploration missions will also be provided. New on-board software for autonomous science data acquisition for planetary exploration will be described, as well as advanced systems for safe planetary landings. A new multi-agent architecture that addresses some of the challenges of autonomous systems will be presented. Autonomous operation of ground systems will also be considered, including software for autonomous in-situ propellant production and management, and closed- loop ecological life support systems (CELSS). Finally, plans and directions for the future will be discussed.

Programmable Thermostat Module Upgrade for the Multipurpose Logistics Module

NASA Technical Reports Server (NTRS)

Clark, D. W.; Glasgow, S. d.; Reagan, S. E.; Presson, K. H.; Howard, D. E.; Smith, D. A.

2007-01-01

The STS-121/ULF 1.1 mission was the maiden flight of the programmable thermostat module (PTM) system used to control the 28 V shell heaters on the multi-purpose logistics module (MPLM). These PTMs, in conjunction with a data recorder module (DRM), provide continuous closed loop temperature control and data recording of MPLM on-orbit heater operations. This Technical Memorandum discusses the hardware design, development, test, and verification (DDT&V) activities performed at the Marshall Space Flight Center as well as the operational implementation and mission performance.

Programmable Thermostat Module Upgrade for the Multi-Purpose Logistics Module

NASA Technical Reports Server (NTRS)

Clark, Dallas; Glasgow, Shaun; Reagan, Shawn; Presson, Keith; Howard, David; Smith, Dennis

2007-01-01

The STS-121/ULF1.1 mission was the maiden flight of the Programmable Thermostat Module (PTM) system used to control the 28 V shell heaters on the Multi-Purpose Logistics Module (MPLM). These PTMs, in conjunction with a Data Recorder Module (DRM), provide continuous closed loop temperature control and data recording of MPLM on-orbit heater operations. This paper will discuss the hardware design, development, test and verification (DDT&V) activities performed at the Marshall Space Flight Center (MSFC) as well as the operational implementation and mission performance.

Apollo Soyuz Test Project Weights and Mass Properties Operational Management System

NASA Technical Reports Server (NTRS)

Collins, M. A., Jr.; Hischke, E. R.

1975-01-01

The Apollo Soyuz Test Project (ASTP) Weights and Mass Properties Operational Management System was established to assure a timely and authoritative method of acquiring, controlling, generating, and disseminating an official set of vehicle weights and mass properties data. This paper provides an overview of the system and its interaction with the various aspects of vehicle and component design, mission planning, hardware and software simulations and verification, and real-time mission support activities. The effect of vehicle configuration, design maturity, and consumables updates is discussed in the context of weight control.

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.

RICIS Symposium 1992: Mission and Safety Critical Systems Research and Applications

NASA Technical Reports Server (NTRS)

1992-01-01

This conference deals with computer systems which control systems whose failure to operate correctly could produce the loss of life and or property, mission and safety critical systems. Topics covered are: the work of standards groups, computer systems design and architecture, software reliability, process control systems, knowledge based expert systems, and computer and telecommunication protocols.

International Space Station Mechanisms and Maintenance Flight Control Documentation and Training Development

NASA Technical Reports Server (NTRS)

Daugherty, Colin C.

2010-01-01

International Space Station (ISS) crew and flight controller training documentation is used to aid in training operations. The Generic Simulations References SharePoint (Gen Sim) site is a database used as an aid during flight simulations. The Gen Sim site is used to make individual mission segment timelines, data, and flight information easily accessible to instructors. The Waste and Hygiene Compartment (WHC) training schematic includes simple and complex fluid schematics, as well as overall hardware locations. It is used as a teaching aid during WHC lessons for both ISS crew and flight controllers. ISS flight control documentation is used to support all aspects of ISS mission operations. The Quick Look Database and Consolidated Tool Page are imagery-based references used in real-time to help the Operations Support Officer (OSO) find data faster and improve discussions with the Flight Director and Capsule Communicator (CAPCOM). A Quick Look page was created for the Permanent Multipurpose Module (PMM) by locating photos of the module interior, labeling specific hardware, and organizing them in schematic form to match the layout of the PMM interior. A Tool Page was created for the Maintenance Work Area (MWA) by gathering images, detailed drawings, safety information, procedures, certifications, demonstration videos, and general facts of each MWA component and displaying them in an easily accessible and consistent format. Participation in ISS mechanisms and maintenance lessons, mission simulation On-the-Job Training (OJT), and real-time flight OJT was used as an opportunity to train for day-to-day operations as an OSO, as well as learn how to effectively respond to failures and emergencies during mission simulations and real-time flight operations.

Dynamic Control System Mode Performance of the Space Technology-7 Disturbance Reduction System

NASA Technical Reports Server (NTRS)

O'Donnell, James R., Jr.; Hsu, Oscar; Maghami, Peiman

2017-01-01

The Space Technology-7 (ST-7) Disturbance Reduction System (DRS) is an experiment package aboard the European Space Agency (ESA) LISA Pathfinder spacecraft, launched on December 3, 2015. DRS consists of three primary components: Colloidal MicroNewton Thrusters (CMNTs), an Integrated Avionics Unit (IAU), and flight-software implementing the Command and Data Handling (C&DH) and Dynamic Control System (DCS) algorithms. The CMNTs were designed to provide thrust from 5 to 30 micro Newton, with thrust controllability and resolution of 0.1 micro Newton and thrust noise of 0.1 micro Newton/(square root of (Hz)) in the measurement band from 1-30 mHz. The IAU hosts the C&DH and DCS flight software, as well as interfaces with both the CMNT electronics and the LISA Pathfinder spacecraft. When in control, the DCS uses star tracker attitude data and capacitive or optically-measured position and attitude information from LISA Pathfinder and the LISA Technology Package (LTP) to control the attitude and position of the spacecraft and the two test masses inside the LTP. After completion of the nominal ESA LISA Pathfinder mission, the DRS experiment was commissioned followed by its nominal mission. DRS operations extended over the next five months, interspersed with station keeping, anomaly resolution, and periods where control was handed back to LISA Pathfinder for them to conduct further experiments. The primary DRS mission ended on December 6, 2016, with the experiment meeting all of its Level 1 requirements. The DCS, developed at the NASA Goddard Space Flight Center, consists of five spacecraft control modes and six test mass control modes, combined into six 'DRS Mission Modes'. Attitude Control and Zero-G were primarily used to control the spacecraft during initial handover and during many of the CMNT characterization experiments. The other Mission Modes, Drag Free Low Force, 18-DOF Transitional, and 18-DOF, were used to provide drag-free control of the spacecraft about the test masses. This paper will discuss the performance of these DCS spacecraft and test mass control modes. Flight data will be shown from each mode throughout the mission, both from nominal operations and during various flight experiments. The DCS team also made some changes to controller, filter, and limit parameters during operations; the motivation and results of these changes will be shown and discussed.

Reusable Autonomy

NASA Technical Reports Server (NTRS)

Truszkowski, Walt; Obenschain, Arthur F. (Technical Monitor)

2002-01-01

Currently, spacecraft ground systems have a well defined and somewhat standard architecture and operations concept. Based on domain analysis studies of various control centers conducted over the years it is clear that ground systems have core capabilities and functionality that are common across all ground systems. This observation alone supports the realization of reuse. Additionally, spacecraft ground systems are increasing in their ability to do things autonomously. They are being engineered using advanced expert systems technology to provide automated support for operators. A clearer understanding of the possible roles of agent technology is advancing the prospects of greater autonomy for these systems. Many of their functional and management tasks are or could be supported by applied agent technology, the dynamics of the ground system's infrastructure could be monitored by agents, there are intelligent agent-based approaches to user-interfaces, etc. The premise of this paper is that the concepts associated with software reuse, applicable in consideration of classically-engineered ground systems, can be updated to address their application in highly agent-based realizations of future ground systems. As a somewhat simplified example consider the following situation, involving human agents in a ground system context. Let Group A of controllers be working on Mission X. They are responsible for the command, control and health and safety of the Mission X spacecraft. Let us suppose that mission X successfully completes it mission and is turned off. Group A could be dispersed or perhaps move to another Mission Y. In this case there would be reuse of the human agents from Mission X to Mission Y. The Group A agents perform their well-understood functions in a somewhat but related context. There will be a learning or familiarization process that the group A agents go through to make the new context, determined by the new Mission Y, understood. This simplified scenario highlights some of the major issues that need to be addressed when considering the situation where Group A is composed of software-based agents (not their human counterparts) and they migrate from one mission support system to another. This paper will address: - definition of an agent architecture appropriate to support reuse; - identification of non-mission-specific agent capabilities required; - appropriate knowledge representation schemes for mission-specific knowledge; - agent interface with mission-specific knowledge (a type of Learning); development of a fully-operational group of cooperative software agents for ground system support; architecture and operation of a repository of reusable agents that could be the source of intelligent components for realizing an autonomous (or nearly autonomous) agent-based ground system, and an agent-based approach to repository management and operation (an intelligent interface for human use of the repository in a ground-system development activity).

Assessing possible exposures of ground troops to Agent Orange during the Vietnam War: the use of contemporary military records.

PubMed

Young, Alvin L; Cecil, Paul F; Guilmartin, John F

2004-01-01

Potential exposure of ground troops in Vietnam to Agent Orange and 2,3,7,8-tetrachlorodibenzo-p-dioxin (TCDD) remains controversial despite the passage of 30 years since the Vietnam War. Because of uncertainty over the serum dioxin levels in ground troops at the end of their service in Vietnam, attempts have been made to develop a methodology for characterizing exposure of ground troops in Vietnam to Agent Orange and other herbicides based upon historical reconstruction from military records. Historical information is often useful in evaluating and modeling exposure, but such information should be reasonably accurate, complete, and reliable. This paper reviews the procedures and supporting historical information related to the spraying of herbicides in Vietnam. The historical information is classified into two categories: procedural information and operational information. Procedural information covered the process and procedures followed in spraying herbicides from US Air Force fixed wing aircraft (Operation RANCH HAND) in Vietnam, and included approval procedures for spray missions, the criteria required to conduct a mission, the control exercised by the Forward Air Controller and the Tactical Air Control Center and the characteristics of the equipment used to apply the herbicides. Operational information includes data from the RANCH HAND Daily Air Activities Reports, which included geographic locations of specific spray missions, the amount of herbicide sprayed by a specific mission, reports of battle damage to spray aircraft, reports of fighter aircraft support for aerial spray missions, and any comments, such as reasons for canceling a mission. Historical information demonstrates that herbicide spray missions were carefully planned and that spraying only occurred when friendly forces were not located in the target area. RANCH HAND spray missions were either not approved or cancelled if approved when there were friendly forces in the area designated for spraying. Stringent criteria had to be met before spray missions could be approved. The operational information shows that spray missions for both defoliation and crop destruction were conducted in an extremely hostile environment. Heavy 'fighter suppression' with antipersonnel ordnance was used to minimize the impact of hostile ground fire on RANCH HAND aircraft. Procedures were in place that prohibited movement of troops into sprayed areas immediately after a mission due to the possible presence of unexploded ordnance delivered by fighter aircraft supporting RANCH HAND missions. The optimal nature of the spray equipment and application procedures minimized the possibility of significant spray drift. Conclusions. Few friendly troops were sprayed by fixed wing aircraft during Operation RANCH HAND, which delivered 95% of all defoliants used in Vietnam. Similarly, few troops were sprayed during helicopter or surface-based spray operations, which constituted the remaining 5% of defoliants. Detailed policies and procedures for approval and execution of spray missions ensured that friendly forces were not located in the areas targeted for spraying. Fighter aircraft assigned to accompany each spray mission frequently suppressed much of the hostile fire with bombs and other ordnance. Confirmed clearance of the target area was necessary to avoid friendly casualties. Historical records establish that these policies and procedures were strictly followed. Exposure of troops whether from direct spraying or movement through areas recently sprayed was very unlikely. The wartime military records of troop positions and herbicide operations are valuable for some purposes, but have specific limitations in exposure reconstruction. The completeness and accuracy of the geographic data (maps used by RANCH HAND and military ground units) were dependent upon the inherent precision of the map, the accuracy with which it depicted surface features, and the completeness and accuracy of the information on which it is based. Navigation by the crew using visual orientation and reference to the map was the only means that aircrew on spray missions had for establishing their locations. A Forward Air Controller independent of Operation RANCH HAND was present at the location of each spray target immediately before and during spraying operations to verify the target location and ensure that friendly forces were clear of the target area. Anecdotal reports of direct spraying of troops in Vietnam likely reflect the RANCH HAND missions spraying insecticide for mosquito control at regular intervals from March 1967 through February 1972. Outlook. The distribution and levels of serum dioxin in RANCH HAND veterans and the US Army Chemical Corps Vietnam veterans (the unit responsible for helicopter and ground-based spray operations) are distinguishable from typical levels in the population decades after the Vietnam conflict. An exposure model similar to that proposed in the 2003 report of the Institute of Medicine's Committee on 'Characterizing Exposure of Veterans to Agent Orange and Other Herbicides Used in Vietnam' was tested in 1988 by the Centers for Disease Control and Prevention and found to be a poor predictor of absorbed dose of TCDD. Military records during the Vietnam War lack the precision to determine that troops were directly sprayed with herbicides during Operation RANCH HAND, especially given the procedures in place to ensure clearance of friendly forces from the target area and the lack of elevated serum levels of TCDD in ground troops judged to have operated in heavily sprayed areas.

Telemetry distribution and processing for the second German Spacelab Mission D-2

NASA Technical Reports Server (NTRS)

Rabenau, E.; Kruse, W.

1994-01-01

For the second German Spacelab Mission D-2 all activities related to operating, monitoring and controlling the experiments on board the Spacelab were conducted from the German Space Operations Control Center (GSOC) operated by the Deutsche Forschungsanstalt fur Luft- und Raumfahrt (DLR) in Oberpfaffenhofen, Germany. The operational requirements imposed new concepts on the transfer of data between Germany and the NASA centers and the processing of data at the GSOC itself. Highlights were the upgrade of the Spacelab Data Processing Facility (SLDPF) to real time data processing, the introduction of packet telemetry and the development of the high-rate data handling front end, data processing and display systems at GSOC. For the first time, a robot on board the Spacelab was to be controlled from the ground in a closed loop environment. A dedicated forward channel was implemented to transfer the robot manipulation commands originating from the robotics experiment ground station to the Spacelab via the Orbiter's text and graphics system interface. The capability to perform telescience from an external user center was implemented. All interfaces proved successful during the course of the D-2 mission and are described in detail in this paper.

Cassini End of Mission

NASA Image and Video Library

2017-09-15

Spacecraft operations team manager for the Cassini mission at Saturn, Julie Webster, rips up the final contingency plan for the Cassini mission, Friday, Sept. 15, 2017 in mission control at NASA's Jet Propulsion Laboratory in Pasadena, California. Since its arrival in 2004, the Cassini-Huygens mission has been a discovery machine, revolutionizing our knowledge of the Saturn system and captivating us with data and images never before obtained with such detail and clarity. On Sept. 15, 2017, operators deliberately plunged the spacecraft into Saturn, as Cassini gathered science until the end. Loss of contact with the Cassini spacecraft occurred at 7:55 a.m. EDT (4:55 a.m. PDT). The “plunge” ensures Saturn’s moons will remain pristine for future exploration. During Cassini’s final days, mission team members from all around the world gathered at NASA’s Jet Propulsion Laboratory, Pasadena, California, to celebrate the achievements of this historic mission. Photo Credit: (NASA/Joel Kowsky)

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.

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

Inflight - Apollo X - MSC

NASA Image and Video Library

1969-05-18

S69-34039 (18 May 1969) --- Overall view of activity in the Mission Operations Control Room in the Mission Control Center, Building 30, on the first day of the Apollo 10 lunar orbit mission. This picture was taken following CSM/LM-S-IVB separation, and prior to LM extraction from the S-IVB. The telecast from the Apollo 10's color TV camera shows the LM still attached to the S-IVB. The CSM is making the docking approach to the LM/S-IVB.

STS-33 MS Carter operates translation hand control (THC) on aft flight deck

NASA Technical Reports Server (NTRS)

1989-01-01

STS-33 Mission Specialist (MS) Manley L. Carter, Jr operates translation hand control (THC) at the aft flight deck onorbit station while peering out overhead window W7. Carter's communications kit assembly headset microphone extends across his face.

Non-Traditional Displays for Mission Monitoring

NASA Technical Reports Server (NTRS)

Trujillo, Anna C.; Schutte, Paul C.

1999-01-01

Advances in automation capability and reliability have changed the role of humans from operating and controlling processes to simply monitoring them for anomalies. However, humans are traditionally bad monitors of highly reliable systems over time. Thus, the human is assigned a task for which he is ill equipped. We believe that this has led to the dominance of human error in process control activities such as operating transportation systems (aircraft and trains), monitoring patient health in the medical industry, and controlling plant operations. Research has shown, though, that an automated monitor can assist humans in recognizing and dealing with failures. One possible solution to this predicament is to use a polar-star display that will show deviations from normal states based on parameters that are most indicative of mission health.

Proceedings of the Defense Nuclear Agency Conference on Arms Control and Verification Technology (ACT) Held in Williamsburg, Virginia on 1-4 June 1992

DTIC Science & Technology

1993-12-01

operational schedules and overall mission costs. Several team members should be qualified to operate each item of equipment so the mission can proceed...establishing verified data exchange, scheduled on-site inspections of declared facilities and operation of a perimeter to portal monitoring system; (3...listed in Schedule 1, 2A, and 2B shall be subject to international monitoring. Each State Party also has the right to request an on-site challenge

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

The Orion GN and C Data-Driven Flight Software Architecture for Automated Sequencing and Fault Recovery

NASA Technical Reports Server (NTRS)

King, Ellis; Hart, Jeremy; Odegard, Ryan

2010-01-01

The Orion Crew Exploration Vehicle (CET) is being designed to include significantly more automation capability than either the Space Shuttle or the International Space Station (ISS). In particular, the vehicle flight software has requirements to accommodate increasingly automated missions throughout all phases of flight. A data-driven flight software architecture will provide an evolvable automation capability to sequence through Guidance, Navigation & Control (GN&C) flight software modes and configurations while maintaining the required flexibility and human control over the automation. This flexibility is a key aspect needed to address the maturation of operational concepts, to permit ground and crew operators to gain trust in the system and mitigate unpredictability in human spaceflight. To allow for mission flexibility and reconfrgurability, a data driven approach is being taken to load the mission event plan as well cis the flight software artifacts associated with the GN&C subsystem. A database of GN&C level sequencing data is presented which manages and tracks the mission specific and algorithm parameters to provide a capability to schedule GN&C events within mission segments. The flight software data schema for performing automated mission sequencing is presented with a concept of operations for interactions with ground and onboard crew members. A prototype architecture for fault identification, isolation and recovery interactions with the automation software is presented and discussed as a forward work item.

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.

An operations and command systems for the extreme ultraviolet explorer

NASA Technical Reports Server (NTRS)

Muscettola, Nicola; Korsmeyer, David J.; Olson, Eric C.; Wong, Gary

1994-01-01

About 40% of the budget of a scientific spacecraft mission is usually consumed by Mission Operations & Data Analysis (MO&DA) with MO driving these costs. In the current practice, MO is separated from spacecraft design and comes in focus relatively late in the mission life cycle. As a result, spacecraft may be designed that are very difficult to operate. NASA centers have extensive MO expertise but often lessons learned in one mission are not exploited for other parallel or future missions. A significant reduction of MO costs is essential to ensure a continuing and growing access to space for the scientific community. We are addressing some of these issues with a highly automated payload operations and command system for an existing mission, the Extreme Ultraviolet Explorer (EUVE). EUVE is currently operated jointly by the Goddard Space Flight Center (GSFC), responsible for spacecraft operations, and the Center for Extreme Ultraviolet Astrophysics (CEA) of the University of California, Berkeley, which controls the telescopes and scientific instruments aboard the satellite. The new automated system is being developed by a team including personnel from the NASA Ames Research Center (ARC), the Jet Propulsion Laboratory (JPL) and the Center for EUV Astrophysics (CEA). An important goal of the project is to provide AI-based technology that can be easily operated by nonspecialists in AI. Another important goal is the reusability of the techniques for other missions. Models of the EUVE spacecraft need to be built both for planning/scheduling and for monitoring. In both cases, our modeling tools allow the assembly of a spacecraft model from separate sub-models of the various spacecraft subsystems. These sub-models are reusable; therefore, building mission operations systems for another small satellite mission will require choosing pre-existing modules, reparametrizing them with respect to the actual satellite telemetry information, and reassembling them in a new model. We briefly describe the EUVE mission and indicate why it is particularly suitable for the task. Then we briefly outline our current work in mission planning/scheduling and spacecraft and instrument health monitoring.

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.

JPL Contamination Control Engineering

NASA Technical Reports Server (NTRS)

Blakkolb, Brian

2013-01-01

JPL has extensive expertise fielding contamination sensitive missions-in house and with our NASA/industry/academic partners.t Development and implementation of performance-driven cleanliness requirements for a wide range missions and payloads - UV-Vis-IR: GALEX, Dawn, Juno, WFPC-II, AIRS, TES, et al - Propulsion, thermal control, robotic sample acquisition systems. Contamination control engineering across the mission life cycle: - System and payload requirements derivation, analysis, and contamination control implementation plans - Hardware Design, Risk trades, Requirements V-V - Assembly, Integration & Test planning and implementation - Launch site operations and launch vehicle/payload integration - Flight ops center dot Personnel on staff have expertise with space materials development and flight experiments. JPL has capabilities and expertise to successfully address contamination issues presented by space and habitable environments. JPL has extensive experience fielding and managing contamination sensitive missions. Excellent working relationship with the aerospace contamination control engineering community/.

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.

A review of Spacelab mission management approach

NASA Technical Reports Server (NTRS)

Craft, H. G., Jr.

1979-01-01

The Spacelab development program is a joint undertaking of the NASA and ESA. The paper addresses the initial concept of Spacelab payload mission management, the lessons learned, and modifications made as a result of the actual implementation of Spacelab Mission 1. The discussion covers mission management responsibilities, program control, science management, payload definition and interfaces, integrated payload mission planning, integration requirements, payload specialist training, payload and launch site integration, payload flight/mission operations, and postmission activities. After 3.5 years the outlined overall mission manager approach has proven to be most successful. The approach does allow the mission manager to maintain the lowest overall mission cost.

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.

Statistical porcess control in Deep Space Network operation

NASA Technical Reports Server (NTRS)

Hodder, J. A.

2002-01-01

This report describes how the Deep Space Mission System (DSMS) Operations Program Office at the Jet Propulsion Laboratory's (EL) uses Statistical Process Control (SPC) to monitor performance and evaluate initiatives for improving processes on the National Aeronautics and Space Administration's (NASA) Deep Space Network (DSN).

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.

Air Breathing Propulsion Controls and Diagnostics Research at NASA Glenn Under NASA Aeronautics Research Mission Programs

NASA Technical Reports Server (NTRS)

Garg, Sanjay

2015-01-01

The Intelligent Control and Autonomy Branch (ICA) at NASA (National Aeronautics and Space Administration) Glenn Research Center (GRC) in Cleveland, Ohio, is leading and participating in various projects in partnership with other organizations within GRC and across NASA, the U.S. aerospace industry, and academia to develop advanced controls and health management technologies that will help meet the goals of the NASA Aeronautics Research Mission Directorate (ARMD) Programs. These efforts are primarily under the various projects under the Advanced Air Vehicles Program (AAVP), Airspace Operations and Safety Program (AOSP) and Transformative Aeronautics Concepts Program (TAC). The ICA Branch is focused on advancing the state-of-the-art of aero-engine control and diagnostics technologies to help improve aviation safety, increase efficiency, and enable operation with reduced emissions. This paper describes the various ICA research efforts under the NASA Aeronautics Research Mission Programs with a summary of motivation, background, technical approach, and recent accomplishments for each of the research tasks.

Three MSC officials hold discussion in Mission Control room during Gemini 11

NASA Image and Video Library

1966-09-12

S66-52754 (12 Sept. 1966) --- Three key Manned Spacecraft Center (MSC) officials hold discussion in the Mission Control room during Gemini-11 activity. Left to right, are Donald K. Slayton, MSC Director of Flight Crew Operations; astronaut Alan B. Shepard Jr., Chief, MSC Astronaut Office; and George M. Low, MSC Deputy Director. Photo credit: NASA

Cassini NASA Social

NASA Image and Video Library

2017-09-14

Cassini NASA Social attendees speak with members of the Cassini mission team in the Charles Elachi Mission Control Center in the Space Flight Operation Center, Thursday, Sept. 14, 2017 at NASA's Jet Propulsion Laboratory in Pasadena, California. Since its arrival in 2004, the Cassini-Huygens mission has been a discovery machine, revolutionizing our knowledge of the Saturn system and captivating us with data and images never before obtained with such detail and clarity. On Sept. 15, 2017, operators will deliberately plunge the spacecraft into Saturn, as Cassini gathered science until the end. The “plunge” ensures Saturn’s moons will remain pristine for future exploration. During Cassini’s final days, mission team members from all around the world gathered at NASA’s Jet Propulsion Laboratory, Pasadena, California, to celebrate the achievements of this historic mission. Photo Credit: (NASA/Joel Kowsky)

Enabling Advanced Automation in Spacecraft Operations with the Spacecraft Emergency Response System

NASA Technical Reports Server (NTRS)

Breed, Julie; Fox, Jeffrey A.; Powers, Edward I. (Technical Monitor)

2001-01-01

True autonomy is the Holy Grail of spacecraft mission operations. The goal of launching a satellite and letting it manage itself throughout its useful life is a worthy one. With true autonomy, the cost of mission operations would be reduced to a negligible amount. Under full autonomy, any problems (no matter the severity or type) that may arise with the spacecraft would be handled without any human intervention via some combination of smart sensors, on-board intelligence, and/or smart automated ground system. Until the day that complete autonomy is practical and affordable to deploy, incremental steps of deploying ever-increasing levels of automation (computerization of once manual tasks) on the ground and on the spacecraft are gradually decreasing the cost of mission operations. For example, NASA's Goddard Space Flight Center (NASA-GSFC) has been flying spacecraft with low cost operations for several years. NASA-GSFC's SMEX (Small Explorer) and MIDEX (Middle Explorer) missions have effectively deployed significant amounts of automation to enable the missions to fly predominately in 'light-out' mode. Under light-out operations the ground system is run without human intervention. Various tools perform many of the tasks previously performed by the human operators. One of the major issues in reducing human staff in favor of automation is the perceived increased in risk of losing data, or even losing a spacecraft, because of anomalous conditions that may occur when there is no one in the control center. When things go wrong, missions deploying advanced automation need to be sure that anomalous conditions are detected and that key personal are notified in a timely manner so that on-call team members can react to those conditions. To ensure the health and safety of its lights-out missions, NASA-GSFC's Advanced Automation and Autonomy branch (Code 588) developed the Spacecraft Emergency Response System (SERS). The SERS is a Web-based collaborative environment that enables secure distributed fault and resource management. The SERS incorporates the use of intelligent agents, threaded discussions, workflow, database connectivity, and links to a variety of communications devices (e.g., two-way paging, PDA's, and Internet phones) via commercial gateways. When the SERS detects a problem, it notifies on-call team members, who then can remotely take any necessary actions to resolve the anomalies.The SERS goes well beyond a simple '911' system that sends out an error code to everyone with a pager. Instead, SERS' software agents send detailed data (i.e., notifications) to the most appropriate team members based on the type and severity of the anomaly and the skills of the on-call team members. The SERS also allows the team members to respond to the notifications from their wireless devices. This unique capability ensures rapid response since the team members no longer have to go to a PC or the control center for every anomalous event. Most importantly, the SERS enables safe experimentation with various techniques for increasing levels of automation, leading to robust autonomy. For the MIDEX missions at NASA GSFC, the SERS is used to provide 'human-in-the-loop' automation. During lights-out operations, as greater control is given to the MIDEX automated systems, the SERS can be configured to page remote personnel and keep them informed regarding actions taking place in the control center. Remote off-duty operators can even be given the option of enabling or inhibiting a specific automated response in near real time via their two-way pagers. The SERS facilitates insertion of new technology to increase automation, while maintaining the safety and security of mission resources. This paper will focus on SERS' overall functionality and how SERS has been designed to handle the monitoring and emergency response for missions with varying levels of automation. The paper will also convey some of the key lessons learned from SERS' deployment across of variety of missions, highlighting this incremental approach to achieving 'robust autonomy'.

The MARS2013 Mars analog mission.

PubMed

Groemer, Gernot; Soucek, Alexander; Frischauf, Norbert; Stumptner, Willibald; Ragonig, Christoph; Sams, Sebastian; Bartenstein, Thomas; Häuplik-Meusburger, Sandra; Petrova, Polina; Evetts, Simon; Sivenesan, Chan; Bothe, Claudia; Boyd, Andrea; Dinkelaker, Aline; Dissertori, Markus; Fasching, David; Fischer, Monika; Föger, Daniel; Foresta, Luca; Fritsch, Lukas; Fuchs, Harald; Gautsch, Christoph; Gerard, Stephan; Goetzloff, Linda; Gołebiowska, Izabella; Gorur, Paavan; Groemer, Gerhard; Groll, Petra; Haider, Christian; Haider, Olivia; Hauth, Eva; Hauth, Stefan; Hettrich, Sebastian; Jais, Wolfgang; Jones, Natalie; Taj-Eddine, Kamal; Karl, Alexander; Kauerhoff, Tilo; Khan, Muhammad Shadab; Kjeldsen, Andreas; Klauck, Jan; Losiak, Anna; Luger, Markus; Luger, Thomas; Luger, Ulrich; McArthur, Jane; Moser, Linda; Neuner, Julia; Orgel, Csilla; Ori, Gian Gabriele; Paternesi, Roberta; Peschier, Jarno; Pfeil, Isabella; Prock, Silvia; Radinger, Josef; Ramirez, Barbara; Ramo, Wissam; Rampey, Mike; Sams, Arnold; Sams, Elisabeth; Sandu, Oana; Sans, Alejandra; Sansone, Petra; Scheer, Daniela; Schildhammer, Daniel; Scornet, Quentin; Sejkora, Nina; Stadler, Andrea; Stummer, Florian; Taraba, Michael; Tlustos, Reinhard; Toferer, Ernst; Turetschek, Thomas; Winter, Egon; Zanella-Kux, Katja

2014-05-01

We report on the MARS2013 mission, a 4-week Mars analog field test in the northern Sahara. Nineteen experiments were conducted by a field crew in Morocco under simulated martian surface exploration conditions, supervised by a Mission Support Center in Innsbruck, Austria. A Remote Science Support team analyzed field data in near real time, providing planning input for the management of a complex system of field assets; two advanced space suit simulators, four robotic vehicles, an emergency shelter, and a stationary sensor platform in a realistic work flow were coordinated by a Flight Control Team. A dedicated flight planning group, external control centers for rover tele-operations, and a biomedical monitoring team supported the field operations. A 10 min satellite communication delay and other limitations pertinent to human planetary surface activities were introduced. The fields of research for the experiments were geology, human factors, astrobiology, robotics, tele-science, exploration, and operations research. This paper provides an overview of the geological context and environmental conditions of the test site and the mission architecture, in particular the communication infrastructure emulating the signal travel time between Earth and Mars. We report on the operational work flows and the experiments conducted, including a deployable shelter prototype for multiple-day extravehicular activities and contingency situations.

Radioastron flight operations

NASA Technical Reports Server (NTRS)

Altunin, V. I.; Sukhanov, K. G.; Altunin, K. R.

1993-01-01

Radioastron is a space-based very-long-baseline interferometry (VLBI) mission to be operational in the mid-90's. The spacecraft and space radio telescope (SRT) will be designed, manufactured, and launched by the Russians. The United States is constructing a DSN subnet to be used in conjunction with a Russian subnet for Radioastron SRT science data acquisition, phase link, and spacecraft and science payload health monitoring. Command and control will be performed from a Russian tracking facility. In addition to the flight element, the network of ground radio telescopes which will be performing co-observations with the space telescope are essential to the mission. Observatories in 39 locations around the world are expected to participate in the mission. Some aspects of the mission that have helped shaped the flight operations concept are: separate radio channels will be provided for spacecraft operations and for phase link and science data acquisition; 80-90 percent of the spacecraft operational time will be spent in an autonomous mode; and, mission scheduling must take into account not only spacecraft and science payload constraints, but tracking station and ground observatory availability as well. This paper will describe the flight operations system design for translating the Radioastron science program into spacecraft executed events. Planning for in-orbit checkout and contingency response will also be discussed.

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).

Momentum Management for the NASA Near Earth Asteroid Scout Solar Sail Mission

NASA Technical Reports Server (NTRS)

Heaton, Andrew; Diedrich, Benjamin L.; Orphee, Juan; Stiltner, Brandon; Becker, Christopher

2017-01-01

The Momentum Management (MM) system is described for the NASA Near Earth Asteroid Scout (NEA Scout) cubesat solar sail mission. Unlike many solar sail mission proposals that used solar torque as the primary or only attitude control system, NEA Scout uses small reaction wheels (RW) and a reaction control system (RCS) with cold gas thrusters, as described in the abstract "Solar Sail Attitude Control System for Near Earth Asteroid Scout Cubesat Mission." The reaction wheels allow fine pointing and higher rates with low mass actuators to meet the science, communication, and trajectory guidance requirements. The MM system keeps the speed of the wheels within their operating margins using a combination of solar torque and the RCS.

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 adapt. To address these needs, this work also examines the development and use of smart materials to tune the dynamic characteristics of the structure in a passive sense. One prime example is the use of an adaptive electrical shunt connected to a piezoelectric patch in order to provide tuned passive vibration damping. The work also examines the use of active vibration control, such as by applying power to that same piezoelectric patch. The overall goal is to examine the use of smart structures that can react to the environment thereby improving the overall living, working, and learning environment for these long-term missions.

Development of a Novel, Two-Processor Architecture for a Small UAV Autopilot System,

DTIC Science & Technology

2006-07-26

is, and the control laws the user implements to control it. The flight control system board will contain the processor selected for this system...Unit (IMU). The IMU contains solid-state gyros and accelerometers and uses these to determine the attitude of the UAV within the three dimensions of...multiple-UAV swarming for combat support operations. The mission processor board will contain the processor selected to execute the mission

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.

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.

Validation of Mission Plans Through Simulation

NASA Astrophysics Data System (ADS)

St-Pierre, J.; Melanson, P.; Brunet, C.; Crabtree, D.

2002-01-01

The purpose of a spacecraft mission planning system is to automatically generate safe and optimized mission plans for a single spacecraft, or more functioning in unison. The system verifies user input syntax, conformance to commanding constraints, absence of duty cycle violations, timing conflicts, state conflicts, etc. Present day constraint-based systems with state-based predictive models use verification rules derived from expert knowledge. A familiar solution found in Mission Operations Centers, is to complement the planning system with a high fidelity spacecraft simulator. Often a dedicated workstation, the simulator is frequently used for operator training and procedure validation, and may be interfaced to actual control stations with command and telemetry links. While there are distinct advantages to having a planning system offer realistic operator training using the actual flight control console, physical verification of data transfer across layers and procedure validation, experience has revealed some drawbacks and inefficiencies in ground segment operations: With these considerations, two simulation-based mission plan validation projects are under way at the Canadian Space Agency (CSA): RVMP and ViSION. The tools proposed in these projects will automatically run scenarios and provide execution reports to operations planning personnel, prior to actual command upload. This can provide an important safeguard for system or human errors that can only be detected with high fidelity, interdependent spacecraft models running concurrently. The core element common to these projects is a spacecraft simulator, built with off-the- shelf components such as CAE's Real-Time Object-Based Simulation Environment (ROSE) technology, MathWork's MATLAB/Simulink, and Analytical Graphics' Satellite Tool Kit (STK). To complement these tools, additional components were developed, such as an emulated Spacecraft Test and Operations Language (STOL) interpreter and CCSDS TM/TC encoders and decoders. This paper discusses the use of simulation in the context of space mission planning, describes the projects under way and proposes additional venues of investigation and development.

Issues of geologically-focused situational awareness in robotic planetary missions: Lessons from an analogue mission at Mistastin Lake impact structure, Labrador, Canada

NASA Astrophysics Data System (ADS)

Antonenko, I.; Osinski, G. R.; Battler, M.; Beauchamp, M.; Cupelli, L.; Chanou, A.; Francis, R.; Mader, M. M.; Marion, C.; McCullough, E.; Pickersgill, A. E.; Preston, L. J.; Shankar, B.; Unrau, T.; Veillette, D.

2013-07-01

Remote robotic data provides different information than that obtained from immersion in the field. This significantly affects the geological situational awareness experienced by members of a mission control science team. In order to optimize science return from planetary robotic missions, these limitations must be understood and their effects mitigated to fully leverage the field experience of scientists at mission control.Results from a 13-day analogue deployment at the Mistastin Lake impact structure in Labrador, Canada suggest that scale, relief, geological detail, and time are intertwined issues that impact the mission control science team's effectiveness in interpreting the geology of an area. These issues are evaluated and several mitigation options are suggested. Scale was found to be difficult to interpret without the reference of known objects, even when numerical scale data were available. For this reason, embedding intuitive scale-indicating features into image data is recommended. Since relief is not conveyed in 2D images, both 3D data and observations from multiple angles are required. Furthermore, the 3D data must be observed in animation or as anaglyphs, since without such assistance much of the relief information in 3D data is not communicated. Geological detail may also be missed due to the time required to collect, analyze, and request data.We also suggest that these issues can be addressed, in part, by an improved understanding of the operational time costs and benefits of scientific data collection. Robotic activities operate on inherently slow time-scales. This fact needs to be embraced and accommodated. Instead of focusing too quickly on the details of a target of interest, thereby potentially minimizing science return, time should be allocated at first to more broad data collection at that target, including preliminary surveys, multiple observations from various vantage points, and progressively smaller scale of focus. This operational model more closely follows techniques employed by field geologists and is fundamental to the geologic interpretation of an area. Even so, an operational time cost/benefit analyses should be carefully considered in each situation, to determine when such comprehensive data collection would maximize the science return.Finally, it should be recognized that analogue deployments cannot faithfully model the time scales of robotic planetary missions. Analogue missions are limited by the difficulty and expense of fieldwork. Thus, analogue deployments should focus on smaller aspects of robotic missions and test components in a modular way (e.g., dropping communications constraints, limiting mission scope, focusing on a specific problem, spreading the mission over several field seasons, etc.).

Conceptual Inquiry of the Space Shuttle and International Space Station GNC Flight Controllers

NASA Technical Reports Server (NTRS)

Kranzusch, Kara

2007-01-01

The concept of Mission Control was envisioned by Christopher Columbus Kraft in the 1960's. Instructed to figure out how to operate human space flight safely, Kraft envisioned a room of sub-system experts troubleshooting problems and supporting nominal flight activities under the guidance of one Flight Director who is responsible for the success of the mission. To facilitate clear communication, MCC communicates with the crew through a Capsule Communicator (CAPCOM) who is an astronaut themselves. Gemini 4 was the first mission to be supported by such a MCC and successfully completed the first American EVA. The MCC seen on television is called the Flight Control Room (FCR, pronounced ficker) or otherwise known as the front room. While this room is the most visible aspect, it is a very small component of the entire control center. The Shuttle FCR is known as the White FCR (WFCR) and Station's as FCR-1. (FCR-1 was actually the first FCR built at JSC which was used through the Gemini, Apollo and Shuttle programs until the WFCR was completed in 1992. Afterwards FCR-1 was refurbished first for the Life Sciences Center and then for the ISS in 2006.) Along with supporting the Flight Director, each FCR operator is also the supervisor for usually two or three support personnel in a back room called the Multi-Purpose Support Room (MPSR, pronounced mipser). MPSR operators are more deeply focused on their specific subsystems and have the responsible to analyze patterns, and diagnose and assess consequences of faults. The White MPSR (WMPSR) operators are always present for Shuttle operations; however, ISS FCR controllers only have support from their Blue MPSR (BMPSR) while the Shuttle is docked and during critical operations. Since ISS operates 24-7, the FCR team reduces to a much smaller Gemini team of 4-5 operators for night and weekend shifts when the crew is off-duty. The FCR is also supported by the Mission Evaluation Room (MER) which is a collection of contractor engineers who provide analysis and long-term troubleshooting support. Each MER operator is an expert in a very small portion of a sub-system and each FCR console usually interfaces with several MER positions.

SKYLAB III - POSTLAUNCH (JOKE)

NASA Image and Video Library

1973-09-25

S73-34456 (September 1973) --- 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. Photo credit: NASA

An Analog Rover Exploration Mission for Education and Outreach

NASA Astrophysics Data System (ADS)

Moores, John; Campbell, Charissa L.; Smith, Christina L.; Cooper, Brittney A.

2017-10-01

This abstract describes an analog rover exploration mission designed as an outreach program for high school and undergraduate students. This program is used to teach them about basic mission control operations, how to manage a rover as if it were on another planetary body, and employing the rover remotely to complete mission objectives. One iteration of this program has been completed and another is underway. In both trials, participants were shown the different operation processes involved in a real-life mission. Modifications were made to these processes to decrease complexity and better simulate a mission control environment in a short time period (three 20-minute-long mission “days”). In the first run of the program, participants selected a landing site, what instruments would be on the rover - subject to cost, size, and weight limitations - and were randomly assigned one of six different mission operations roles, each with specific responsibilities. For example, a Science Planner/Integrator (SPI) would plan science activities whilst a Rover Engineer (RE) would keep on top of rover constraints. Planning consisted of a series of four meetings to develop and verify the current plan, pre-plan the next day's activities and uplink the activities to the “rover” (a human colleague). Participants were required to attend certain meetings depending upon their assigned role. To conclude the mission, students viewed the site to understand any differences between remote viewing and reality in relation to the rover. Another mission is currently in progress with revisions from the earlier run to improve the experience. This includes broader roles and meetings and pre-selecting the landing site and rover. The new roles are: Mission Lead, Rover Engineer and Science Planner. The SPI role was previously popular so most of the students were placed in this category. The meetings were reduced to three but extended in length. We are also planning to integrate this program into the Ontario Science Center (OSC) to educate and fascinate people of all ages.

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.

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.

75 FR 51243 - Trade Mission to the Port of Veracruz

Federal Register 2010, 2011, 2012, 2013, 2014

2010-08-19

... collection and management, hazardous materials handling, maritime inspection, operations control, designing... control systems; --Pneumatic delivery systems; --Software for inventory tracking; --Used mobile railcar...

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.

Air Force construction automation/robotics

NASA Technical Reports Server (NTRS)

Nease, A. D.; Alexander, E. F.

1993-01-01

The Air Force has several missions which generate unique requirements that are being met through the development of construction robotic technology. One especially important mission will be the conduct of Department of Defense (DOD) space activities. Space operations and other missions place construction/repair equipment operators in dangerous environments and potentially harmful situations. Additionally, force reductions require that human resources be leveraged to the maximum extent possible, and more stringent construction repair requirements push for increased automation. To solve these problems, the U.S. Air Force is undertaking a research and development effort at Tyndall AFB, FL, to develop robotic construction/repair equipment. This development effort involves the following technologies: teleoperation, telerobotics, construction operations (excavation, grading, leveling, tool change), robotic vehicle communications, vehicle navigation, mission/vehicle task control architecture, and associated computing environment. The ultimate goal is the fielding of a robotic repair capability operating at the level of supervised autonomy. This paper will discuss current and planned efforts in space construction/repair, explosive ordnance disposal, hazardous waste cleanup, and fire fighting.

Cassini End of Mission

NASA Image and Video Library

2017-09-14

A jar of peanuts is seen sitting on a console in mission control of the Space Flight Operations Center as the Cassini mission team await the final downlink of the spacecraft's data recorder, Thursday, Sept. 14, 2017 at NASA's Jet Propulsion Laboratory in Pasadena, California. Since its arrival in 2004, the Cassini-Huygens mission has been a discovery machine, revolutionizing our knowledge of the Saturn system and captivating us with data and images never before obtained with such detail and clarity. On Sept. 15, 2017, operators will deliberately plunge the spacecraft into Saturn, as Cassini gathered science until the end. The “plunge” ensures Saturn’s moons will remain pristine for future exploration. During Cassini’s final days, mission team members from all around the world gathered at NASA’s Jet Propulsion Laboratory, Pasadena, California, to celebrate the achievements of this historic mission. Photo Credit: (NASA/Joel Kowsky)

Cassini End of Mission

NASA Image and Video Library

2017-09-15

Spacecraft operations team manager for the Cassini mission at Saturn, Julie Webster is seen in mission control as the Cassini spacecraft makes its final plunge into Saturn, Friday, Sept. 15, 2017 at NASA's Jet Propulsion Laboratory in Pasadena, California. Since its arrival in 2004, the Cassini-Huygens mission has been a discovery machine, revolutionizing our knowledge of the Saturn system and captivating us with data and images never before obtained with such detail and clarity. On Sept. 15, 2017, operators deliberately plunged the spacecraft into Saturn, as Cassini gathered science until the end. Loss of contact with the Cassini spacecraft occurred at 7:55 a.m. EDT (4:55 a.m. PDT). The “plunge” ensures Saturn’s moons will remain pristine for future exploration. During Cassini’s final days, mission team members from all around the world gathered at NASA’s Jet Propulsion Laboratory, Pasadena, California, to celebrate the achievements of this historic mission. Photo Credit: (NASA/Joel Kowsky)

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.

2. NORTH SIDE OF THE CONTROL STATION OPERATIONS BUILDING SHOWING ...

Library of Congress Historic Buildings Survey, Historic Engineering Record, Historic Landscapes Survey

2. NORTH SIDE OF THE CONTROL STATION OPERATIONS BUILDING SHOWING MISSION REVIVAL FACADE. A TELECOMMUNICATIONS BUILDING CONSTRUCTED IN THE 1980s IS ADJACENT AT PHOTO-CENTER, AND COTTAGE 111 (PRESENTLY USED AS THE HYDROGRAPHER'S OFFICE) IS VISIBLE AT PHOTORIGHT. VIEW TO SOUTH. - Bishop Creek Hydroelectric System, Control Station, Bishop Creek, Bishop, Inyo County, CA

In-Flight Operation of the Dawn Ion Propulsion System - The First Nine Months

NASA Technical Reports Server (NTRS)

Garner, Charles E.; Brophy, John R.; Mikes, Steven C.; Raymond, Marc D.

2008-01-01

The Dawn mission, part of NASA's Discovery Program, has as its goal the scientific exploration of the two most massive main-belt asteroids, Vesta and Ceres. The Dawn spacecraft was launched from Cape Canaveral Air Force Station on September 27, 2007 on a Delta-II 7925H-9.5 (Delta-II Heavy) rocket that placed the 1218 kg spacecraft into an Earth-escape trajectory. On-board the spacecraft is an ion propulsion system (IPS) which will provide most of the delta-V needed for heliocentric transfer to Vesta, orbit capture at Vesta, transfer to Vesta science orbits, departure and escape from Vesta, heliocentric transfer to Ceres, orbit capture at Ceres, and transfer to Ceres science orbits. The Dawn ion engine design is based on the design validated on NASA's Deep Space 1 mission. However, because of the very substantial (11 km/s) delta-V requirements for this mission Dawn requires two engines to complete its mission objectives. The power processor units (PPU), digital control and interface units (DCIU) slice boards and the xenon control assembly (XCA) are also based on the DS1 design. The DCIUs and thrust gimbal assemblies (TGA) were developed at the Jet Propulsion Laboratory. The spacecraft was provided by Orbital Sciences Corporation, Sterling, Virginia, and the mission is managed by and operated from the Jet Propulsion Laboratory. Dawn partnered with Germany, Italy and Los Alamos National Laboratory for the science instruments. The mission is led by the principal investigator, Dr. Christopher Russell, from the University of California, Los Angeles. The first 80 days after launch were dedicated to the initial checkout of the spacecraft prior to the initiation of long-term thrusting for the heliocentric transfer to Vesta. The IPS hardware, consisting of three ion thrusters and TGAs, two PPUs and DCIUs, xenon feed system, and spacecraft control software, was investigated extensively. Thrust measurements, roll torque measurements, pointing capabilities, control characteristics, and thermal behavior of the spacecraft and IPS were carefully evaluated. The Dawn IPS fully met all its initial checkout performance objectives. Deterministic thrusting for cruise began on December 17, 2007. Over the subsequent approximately 330 days the IPS will be operated virtually continuously at full power thrusting (approximately 91 mN) leading to a Mars flyby in February 2009. The encounter with Mars provides a gravity assist for a plane change and is the only source of post-launch delta-V apart from the IPS. Following the Mars gravity assist IPS will be operated for approximately one year at full power and for 1.3 years at throttled power levels leading to rendezvous with Vesta in August of 2011. Following nine months of orbital operations with IPS providing the propulsion needed for orbit capture, science orbit transfer and orbit maintenance and Vesta escape, Dawn will transit to Ceres with an expected arrival date of February 2015. As of June 16, 2008 the ion thrusters on Dawn have operated for close to 3,846 hours and have delivered nearly 1 km/s of delta-V to the spacecraft. Dawn IPS operation has been almost flawless during the initial checkout and six months of cruise. This paper provides an overview of Dawn's mission objectives, mission and system design, and the results of the post-launch Dawn IPS mission operations through June 2008

s95-16445

NASA Image and Video Library

2014-08-07

S95-16445 (13-22 July 1995) --- A wide angle view from the rear shows activity in the new Mission Control Center (MCC), opened for operation and dedicated during the STS-70 mission. The Space Shuttle Discovery was just passing over Florida at the time this photo was taken (note mercator map and TV scene on screens). The new MCC, developed at a cost of about 50 million, replaces the main-frame based, NASA-unique design of the old Mission Control with a standard workstation-based, local area network system commonly in use today.

Astronaut Bruce McCandless shows mockup of occulting disc for Skylab exp.

NASA Image and Video Library

1973-11-23

S73-37251 (23 November 1973) --- Astronaut Bruce McCandless II, left, shows off a mock-up of the occulting disc for the T025 Coronagraph Contamination Measurement Engineering and Technology Experiment to be used by the crewmen of the third manned Skylab mission (Skylab 4), now into their eighth day in Earth orbit. On the right is flight director Neil B. Hutchinson. The men are in the Mission Operations Control Room (MOCR) of the Mission Control Center (MCC) at Johnson Space Center. Photo credit: NASA

Advanced High Temperature Structural Seals

NASA Astrophysics Data System (ADS)

Newquist, Charles W.; Verzemnieks, Juris; Keller, Peter C.; Rorabaugh, Michael; Shorey, Mark

2002-10-01

This program addresses the development of high temperature structural seals for control surfaces for a new generation of small reusable launch vehicles. Successful development will contribute significantly to the mission goal of reducing launch cost for small, 200 to 300 pound payloads. Development of high temperature seals is mission enabling. For instance, ineffective control surface seals can result in high temperature (3100 F) flows in the elevon area exceeding structural material limits. Longer sealing life will allow use for many missions before replacement, contributing to the reduction of hardware, operation and launch costs.

Advanced High Temperature Structural Seals

NASA Technical Reports Server (NTRS)

Newquist, Charles W.; Verzemnieks, Juris; Keller, Peter C.; Rorabaugh, Michael; Shorey, Mark

2002-01-01

This program addresses the development of high temperature structural seals for control surfaces for a new generation of small reusable launch vehicles. Successful development will contribute significantly to the mission goal of reducing launch cost for small, 200 to 300 pound payloads. Development of high temperature seals is mission enabling. For instance, ineffective control surface seals can result in high temperature (3100 F) flows in the elevon area exceeding structural material limits. Longer sealing life will allow use for many missions before replacement, contributing to the reduction of hardware, operation and launch costs.

STS-33 MS Carter operates translation hand control (THC) on aft flight deck

NASA Image and Video Library

1989-11-27

STS033-93-011 (27 Nov 1989) --- Astronaut Manley L. Carter, Jr., STS-33 mission specialist, operates translation hand control (THC) at the aft flight deck on orbit station while peering out overhead window W7. Carter's communications kit assembly headset microphone extends across his face.

Autonomous Systems, Robotics, and Computing Systems Capability Roadmap: NRC Dialogue

NASA Technical Reports Server (NTRS)

Zornetzer, Steve; Gage, Douglas

2005-01-01

Contents include the following: Introduction. Process, Mission Drivers, Deliverables, and Interfaces. Autonomy. Crew-Centered and Remote Operations. Integrated Systems Health Management. Autonomous Vehicle Control. Autonomous Process Control. Robotics. Robotics for Solar System Exploration. Robotics for Lunar and Planetary Habitation. Robotics for In-Space Operations. Computing Systems. Conclusion.

Behavioral Health and Performance at NASA JSC: Recent Successes and Future Plan for BHP Research and Operations

NASA Technical Reports Server (NTRS)

Leveton, L. B.; VanderArk, S. T.

2014-01-01

The Behavioral Health and Performance discipline at NASA Johnson Space Center is organized into two distinct Divisions (Biomedical Research and Environmental Science Division and Space and Clinical Operations Division) but is integrated and interrelated in its day-to-day work. Ongoing operations supporting NASA's spaceflight goals benefit from the research portfolios that address risks to mission success. Similarly, these research portfolios are informed by operations to ensure investigations stay relevant given the dynamic environment of spaceflight. There are many success stories that can be presented where initial work begun as a BHP Research project, and funded through the Human Research Program, was fully implemented in operations or addressed an operational need. Examples include improving effectiveness of the debriefings used within Mission Control by the Mission Operations Directorate and countermeasures for fatigue management. There is also ongoing collaboration with research and operations for developing selection methods for future generation astronauts, and to enhance and inform the current family support function. The objective of this panel is to provide examples of recent success stories, describe areas where close collaboration is benefitting ongoing research and operations, and summarize how this will come together as NASA plans for the one year ISS mission - a unique opportunity for both BHP operations and research to learn more about preparing and supporting crewmembers for extended missions in space. The proposed panel will be comprised of six presentations, each describing a unique aspect of research or operations and the benefits to current and future spaceflight.

KSC-LOC-63-5674

NASA Image and Video Library

1963-06-04

CAPE CANAVERAL, Fla. - Between 1962 and 1963, the Mission Control Center was modified to handle the additional complexities of the Gemini Program. In 1962, Pan American World Airways Inc. was contracted to design an addition to the facility, which wrapped around the east, north, and most of the west and south sides. The Mercury Mission Control Center in Florida played a key role in the United States' early spaceflight program. Located at Cape Canaveral Air Force Station, the original part of the building was constructed between 1956 and 1958, with additions in 1959 and 1963. The facility officially was transferred to NASA on Dec. 26, 1963, and served as mission control during all the Project Mercury missions, as well as the first three flights of the Gemini Program, when it was renamed Mission Control Center. With its operational days behind, on June 1, 1967, the Mission Control Center became a stop on the public tour of NASA facilities until the mid-90s. In 1999, much of the equipment and furnishings from the Flight Control Area were moved to the Kennedy Space Center Visitor Complex where they became part of the exhibit there. The building was demolished in spring 2010. Photo credit: NASA

KSC-LOC-63-1971

NASA Image and Video Library

1963-02-13

CAPE CANAVERAL, Fla. - Between 1962 and 1963, the Mission Control Center was modified to handle the additional complexities of the Gemini Program. In 1962, Pan American World Airways Inc. was contracted to design an addition to the facility, which wrapped around the east, north, and most of the west and south sides. The Mercury Mission Control Center in Florida played a key role in the United States' early spaceflight program. Located at Cape Canaveral Air Force Station, the original part of the building was constructed between 1956 and 1958, with additions in 1959 and 1963. The facility officially was transferred to NASA on Dec. 26, 1963, and served as mission control during all the Project Mercury missions, as well as the first three flights of the Gemini Program, when it was renamed Mission Control Center. With its operational days behind, on June 1, 1967, the Mission Control Center became a stop on the public tour of NASA facilities until the mid-90s. In 1999, much of the equipment and furnishings from the Flight Control Area were moved to the Kennedy Space Center Visitor Complex where they became part of the exhibit there. The building was demolished in spring 2010. Photo credit: NASA

KSC-LOC-63-1017

NASA Image and Video Library

1963-02-13

CAPE CANAVERAL, Fla. - Between 1962 and 1963, the Mission Control Center was modified to handle the additional complexities of the Gemini Program. In 1962, Pan American World Airways Inc. was contracted to design an addition to the facility, which wrapped around the east, north, and most of the west and south sides. The Mercury Mission Control Center in Florida played a key role in the United States' early spaceflight program. Located at Cape Canaveral Air Force Station, the original part of the building was constructed between 1956 and 1958, with additions in 1959 and 1963. The facility officially was transferred to NASA on Dec. 26, 1963, and served as mission control during all the Project Mercury missions, as well as the first three flights of the Gemini Program, when it was renamed Mission Control Center. With its operational days behind, on June 1, 1967, the Mission Control Center became a stop on the public tour of NASA facilities until the mid-90s. In 1999, much of the equipment and furnishings from the Flight Control Area were moved to the Kennedy Space Center Visitor Complex where they became part of the exhibit there. The building was demolished in spring 2010. Photo credit: NASA

KSC-LOC-63-5635

NASA Image and Video Library

1963-03-01

CAPE CANAVERAL, Fla. - Between 1962 and 1963, the Mission Control Center was modified to handle the additional complexities of the Gemini Program. In 1962, Pan American World Airways Inc. was contracted to design an addition to the facility, which wrapped around the east, north, and most of the west and south sides. The Mercury Mission Control Center in Florida played a key role in the United States' early spaceflight program. Located at Cape Canaveral Air Force Station, the original part of the building was constructed between 1956 and 1958, with additions in 1959 and 1963. The facility officially was transferred to NASA on Dec. 26, 1963, and served as mission control during all the Project Mercury missions, as well as the first three flights of the Gemini Program, when it was renamed Mission Control Center. With its operational days behind, on June 1, 1967, the Mission Control Center became a stop on the public tour of NASA facilities until the mid-90s. In 1999, much of the equipment and furnishings from the Flight Control Area were moved to the Kennedy Space Center Visitor Complex where they became part of the exhibit there. The building was demolished in spring 2010. Photo credit: NASA

Small satellite multi mission C2 for maximum effect

USGS Publications Warehouse

Miller, E.; Medina, O.; Lane, C.R.; Kirkham, A.; Ivancic, W.; Jones, B.; Risty, R.

2006-01-01

This paper discusses US Air Force, US Army, US Navy, and NASA demonstrations based around the Virtual Mission Operations Center (VMOC) and its application in fielding a Multi Mission Satellite Operations Center (MMSOC) designed to integrate small satellites into the inherently tiered system environment of operations. The intent is to begin standardizing the spacecraft to ground interfaces needed to reduce costs, maximize space effects to the user, and allow the generation of Tactics, Techniques and Procedures (TTPs) that lead to Responsive Space employment. Combining the US Air Force/Army focus of theater command and control of payloads with the US Navy's user collaboration and FORCEnet consistent approach lays the groundwork for the fundamental change needed to maximize responsive space effects.

Analog Testing of Operations Concepts for Mitigation of Communication Latency During Human Space Exploration

NASA Technical Reports Server (NTRS)

Chappell, Steven P.; Abercromby, Andrew F.; Miller, Matthew J.; Halcon, Christopher; Gernhardt, Michael L.

2016-01-01

OBJECTIVES: NASA Extreme Environment Mission Operations (NEEMO) is an underwater spaceflight analog that allows a true mission-like operational environment and uses buoyancy effects and added weight to simulate different gravity levels. Three missions were undertaken from 2014-2015, NEEMO's 18-20. All missions were performed at the Aquarius undersea research habitat. During each mission, the effects of varying operations concepts and tasks type and complexity on representative communication latencies associated with Mars missions were studied. METHODS: 12 subjects (4 per mission) were weighed out to simulate near-zero or partial gravity extravehicular activity (EVA) and evaluated different operations concepts for integration and management of a simulated Earth-based science backroom team (SBT) to provide input and direction during exploration activities. Exploration traverses were planned in advance based on precursor data collected. Subjects completed science-related tasks including presampling surveys, geologic-based sampling, and marine-based sampling as a portion of their tasks on saturation dives up to 4 hours in duration that were to simulate extravehicular activity (EVA) on Mars or the moons of Mars. One-way communication latencies, 5 and 10 minutes between space and mission control, were simulated throughout the missions. Objective data included task completion times, total EVA times, crew idle time, translation time, SBT assimilation time (defined as time available for SBT to discuss data/imagery after it has been collected, in addition to the time taken to watch imagery streaming over latency). Subjective data included acceptability, simulation quality, capability assessment ratings, and comments. RESULTS: Precursor data can be used effectively to plan and execute exploration traverse EVAs (plans included detailed location of science sites, high-fidelity imagery of the sites, and directions to landmarks of interest within a site). Operations concepts that allow for presampling surveys enable efficient traverse execution and meaningful Mission Control Center (MCC) interaction across long communication latencies and can be done with minimal crew idle time. Imagery and information from the EVA crew that is transmitted real-time to the intravehicular (IV) crewmember(s) can be used to verify that exploration traverse plans are being executed correctly. That same data can be effectively used by MCC (across comm latency) to provide further instructions to the crew from a SBT on sampling priorities, additional tasks, and changes to the plan. Text / data capabilities are preferred over voice capabilities between MCC and IV when executing exploration traverse plans over communication latency. Autonomous crew planning tools can be effective at modifying existing plans if the objectives and constraints are clearly defined.

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.

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.

Man-vehicle systems research facility: Design and operating characteristics

NASA Technical Reports Server (NTRS)

1983-01-01

The Man-Vehicle Systems Research Facility (MVSRF) provides the capability of simulating aircraft (two with full crews), en route and terminal air traffic control and aircrew interactions, and advanced cockpit (1995) display representative of future generations of aircraft, all within the full mission context. The characteristics of this facility derive from research, addressing critical human factors issues that pertain to: (1) information requirements for the utilization and integration of advanced electronic display systems, (2) the interaction and distribution of responsibilities between aircrews and ground controllers, and (3) the automation of aircrew functions. This research has emphasized the need for high fidelity in simulations and for the capability to conduct full mission simulations of relevant aircraft operations. This report briefly describes the MVSRF design and operating characteristics.

Autonomic Management of Space Missions. Chapter 12

NASA Technical Reports Server (NTRS)

Hinchey, Michael G.; Rash, James L.; Truszkowski, Walt; Rouff, Christopher A.; Sterritt, Roy

2006-01-01

With NASA s renewed commitment to outer space exploration, greater emphasis is being placed on both human and robotic exploration. Even when humans are involved in the exploration, human tending of assets becomes cost-prohibitive or in many cases is simply not feasible. In addition, certain exploration missions will require spacecraft that will be capable of venturing where humans cannot be sent. Early space missions were operated manually from ground control centers with little or no automated operations. In the mid-l980s, the high costs of satellite operations prompted NASA, and others, to begin automating as many functions as possible. In our context, a system is autonomous if it can achieve its goals without human intervention. A number of more-or-less automated ground systems exist today, but work continues with the goal being to reduce operations costs to even lower levels. Cost reductions can be achieved in a number of areas. Ground control and spacecraft operations are two such areas where greater autonomy can reduce costs. As a consequence, autonomy is increasingly seen as a critical approach for robotic missions and for some aspects of manned missions. Although autonomy will be critical for the success of future missions (and indeed will enable certain kinds of science data gathering approaches), missions imbued with autonomy must also exhibit autonomic properties. Exploitation of autonomy alone, without emphasis on autonomic properties, will leave spacecraft vulnerable to the dangerous environments in which they must operate. Without autonomic properties, a spacecraft may be unable to recognize negative environmental effects on its components and subsystems, or may be unable to take any action to ameliorate the effects. The spacecraft, though operating autonomously, may then sustain a degradation of performance of components or subsystems, and consequently may have a reduced potential for achieving mission objectives. In extreme cases, lack of autonomic properties could leave the spacecraft unable to recover from faults. Ensuring that exploration spacecraft have autonomic properties will increase the survivability and therefore the likelihood of success of these missions. In fact, over time, as mission requirements increased demands on spacecraft capabilities and longevity, designers have gradually built more autonomicity into spacecraft. For example, a spacecraft in low-earth orbit may experience an out-of-bounds perturbation of its attitude (orientation) due to increased drag caused by increased atmospheric density at its altitude as a result of a sufficiently large solar flare. If the spacecraft was designed to recognize the excessive attitude perturbation, it could decide to protect itself by going into a safe-hold mode where its internal configuration and operation are altered to conserve power and its coarse attitude is adjusted to point its solar panels toward the Sun to maximize power generation. This is an example of a simple type of autonomic behavior that has actually occurred. Future mission concepts will be increasingly dependent on space system survivability enabled by more advanced types of autonomic behaviors

Overview of the Altair Lunar Lander Thermal Control System Design

NASA Technical Reports Server (NTRS)

Stephan, Ryan A.

2010-01-01

NASA's Constellation Program has been developed to successfully return humans to the Lunar surface by 2020. The Constellation Program includes several different project offices including Altair, which is the next generation Lunar Lander. The planned Altair missions are very different than the Lunar missions accomplished during the Apollo era. These differences have resulted in a significantly different thermal control system architecture. The current paper will summarize the Altair mission architecture and the various operational phases. In addition, the derived thermal requirements will be presented. The paper will conclude with a brief description of the thermal control system designed to meet these unique and challenging thermal requirements.

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).

Use of Semi-Autonomous Tools for ISS Commanding and Monitoring

NASA Technical Reports Server (NTRS)

Brzezinski, Amy S.

2014-01-01

As the International Space Station (ISS) has moved into a utilization phase, operations have shifted to become more ground-based with fewer mission control personnel monitoring and commanding multiple ISS systems. This shift to fewer people monitoring more systems has prompted use of semi-autonomous console tools in the ISS Mission Control Center (MCC) to help flight controllers command and monitor the ISS. These console tools perform routine operational procedures while keeping the human operator "in the loop" to monitor and intervene when off-nominal events arise. Two such tools, the Pre-positioned Load (PPL) Loader and Automatic Operators Recorder Manager (AutoORM), are used by the ISS Communications RF Onboard Networks Utilization Specialist (CRONUS) flight control position. CRONUS is responsible for simultaneously commanding and monitoring the ISS Command & Data Handling (C&DH) and Communications and Tracking (C&T) systems. PPL Loader is used to uplink small pieces of frequently changed software data tables, called PPLs, to ISS computers to support different ISS operations. In order to uplink a PPL, a data load command must be built that contains multiple user-input fields. Next, a multiple step commanding and verification procedure must be performed to enable an onboard computer for software uplink, uplink the PPL, verify the PPL has incorporated correctly, and disable the computer for software uplink. PPL Loader provides different levels of automation in both building and uplinking these commands. In its manual mode, PPL Loader automatically builds the PPL data load commands but allows the flight controller to verify and save the commands for future uplink. In its auto mode, PPL Loader automatically builds the PPL data load commands for flight controller verification, but automatically performs the PPL uplink procedure by sending commands and performing verification checks while notifying CRONUS of procedure step completion. If an off-nominal condition occurs during procedure execution, PPL Loader notifies CRONUS through popup messages, allowing CRONUS to examine the situation and choose an option of how PPL loader should proceed with the procedure. The use of PPL Loader to perform frequent, routine PPL uplinks offloads CRONUS to better monitor two ISS systems. It also reduces procedure performance time and decreases risk of command errors. AutoORM identifies ISS communication outage periods and builds commands to lock, playback, and unlock ISS Operations Recorder files. Operation Recorder files are circular buffer files of continually recorded ISS telemetry data. Sections of these files can be locked from further writing, be played back to capture telemetry data that occurred during an ISS loss of signal (LOS) period, and then be unlocked for future recording use. Downlinked Operation Recorder files are used by mission support teams for data analysis, especially if failures occur during LOS. The commands to lock, playback, and unlock Operations Recorder files are encompassed in three different operational procedures and contain multiple user-input fields. AutoORM provides different levels of automation for building and uplinking the commands to lock, playback, and unlock Operations Recorder files. In its automatic mode, AutoORM automatically detects ISS LOS periods, then generates and uplinks the commands to lock, playback, and unlock Operations Recorder files when MCC regains signal with ISS. AutoORM also features semi-autonomous and manual modes which integrate CRONUS more into the command verification and uplink process. AutoORMs ability to automatically detect ISS LOS periods and build the necessary commands to preserve, playback, and release recorded telemetry data greatly offloads CRONUS to perform more high-level cognitive tasks, such as mission planning and anomaly troubleshooting. Additionally, since Operations Recorder commands contain numerical time input fields which are tedious for a human to manually build, AutoORM's ability to automatically build commands reduces operational command errors. PPL Loader and AutoORM demonstrate principles of semi-autonomous operational tools that will benefit future space mission operations. Both tools employ different levels of automation to perform simple and routine procedures, thereby offloading human operators to perform higher-level cognitive tasks. Because both tools provide procedure execution status and highlight off-nominal indications, the flight controller is able to intervene during procedure execution if needed. Semi-autonomous tools and systems that can perform routine procedures, yet keep human operators informed of execution, will be essential in future long-duration missions where the onboard crew will be solely responsible for spacecraft monitoring and control.

Vapor Crystal Growth System (VCGS) Team in the SL POCC During the STS-42 IML-1 Mission

NASA Technical Reports Server (NTRS)

1992-01-01

The primary payload for Space Shuttle Mission STS-42, launched January 22, 1992, was the International Microgravity Laboratory-1 (IML-1), a pressurized manned Spacelab module. The goal of IML-1 was to explore in depth the complex effects of weightlessness of living organisms and materials processing. Around-the-clock research was performed on the human nervous system's adaptation to low gravity and effects of microgravity on other life forms such as shrimp eggs, lentil seedlings, fruit fly eggs, and bacteria. Materials processing experiments were also conducted, including crystal growth from a variety of substances such as enzymes, mercury iodide, and a virus. 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. Featured is the Vapor Crystal Growth System (VCGS) team in SL POCC), during STS-42, IML-1 mission.

A Multi-mission Event-Driven Component-Based System for Support of Flight Software Development, ATLO, and Operations first used by the Mars Science Laboratory (MSL) Project

NASA Technical Reports Server (NTRS)

Dehghani, Navid; Tankenson, Michael

2006-01-01

This viewgraph presentation reviews the architectural description of the Mission Data Processing and Control System (MPCS). MPCS is an event-driven, multi-mission ground data processing components providing uplink, downlink, and data management capabilities which will support the Mars Science Laboratory (MSL) project as its first target mission. MPCS is designed with these factors (1) Enabling plug and play architecture (2) MPCS has strong inheritance from GDS components that have been developed for other Flight Projects (MER, MRO, DAWN, MSAP), and are currently being used in operations and ATLO, and (3) MPCS components are Java-based, platform independent, and are designed to consume and produce XML-formatted data

Tethered Satellite System (TSS) core equipment

NASA Technical Reports Server (NTRS)

Bonifazi, C.

1986-01-01

To date, three Tethered Satellite System (TSS) missions of the Italian provided scientific satellite orbiting in the ionosphere connected to U.S. Space Shuttle is foreseen. The first mission will use an electrically conductive tether of 20 km deployed upward from the orbiter flying at 300 km altitude. This mission will allow investigation of the TSS electrodynamic interaction with the ionosphere due to the high voltage induced across the two terminators of the system during its motion throughout the geomagnetic field. The second mission will use a dielectric tether of 100 km deployed downward from the Orbiter flying at 230 km altitude. Tethered-vehicle access to altitude as low as 120 to 150 km from the Orbiter would permit direct long term observation of phenomena in the lower thermosphere and determination of other dynamical physical processes. The third mission would use the same configuration of the first electrodynamic mission with the complete Core Equipment. Study of power generation by tethered systems would be possible by operating the Core Equipment in the inverted current mode. This mode of operation would allow ion current collection upon the TSS satellite by controlling its potential with respect to the ambient ionospheric plasma. The main requirements of the Core Equipment configuration to date foreseen for the first TSS electrodynamic mission is described. Besides the Core Equipment purposes, its hardware and operational sub-modes of operation are described.

Cassini End of Mission

NASA Image and Video Library

2017-09-14

Cassini program manager at JPL, Earl Maize, watches monitors in mission control of the Space Flight Operations Center as the Cassini spacecraft begins downlink data through NASA's Deep Space Network, Thursday, Sept. 14, 2017 at NASA's Jet Propulsion Laboratory in Pasadena, California. Since its arrival in 2004, the Cassini-Huygens mission has been a discovery machine, revolutionizing our knowledge of the Saturn system and captivating us with data and images never before obtained with such detail and clarity. On Sept. 15, 2017, operators will deliberately plunge the spacecraft into Saturn, as Cassini gathered science until the end. The “plunge” ensures Saturn’s moons will remain pristine for future exploration. During Cassini’s final days, mission team members from all around the world gathered at NASA’s Jet Propulsion Laboratory, Pasadena, California, to celebrate the achievements of this historic mission. Photo Credit: (NASA/Joel Kowsky)

Autonomous Spacecraft Communication Interface for Load Planning

NASA Technical Reports Server (NTRS)

Dever, Timothy P.; May, Ryan D.; Morris, Paul H.

2014-01-01

Ground-based controllers can remain in continuous communication with spacecraft in low Earth orbit (LEO) with near-instantaneous communication speeds. This permits near real-time control of all of the core spacecraft systems by ground personnel. However, as NASA missions move beyond LEO, light-time communication delay issues, such as time lag and low bandwidth, will prohibit this type of operation. As missions become more distant, autonomous control of manned spacecraft will be required. The focus of this paper is the power subsystem. For present missions, controllers on the ground develop a complete schedule of power usage for all spacecraft components. This paper presents work currently underway at NASA to develop an architecture for an autonomous spacecraft, and focuses on the development of communication between the Mission Manager and the Autonomous Power Controller. These two systems must work together in order to plan future load use and respond to unanticipated plan deviations. Using a nominal spacecraft architecture and prototype versions of these two key components, a number of simulations are run under a variety of operational conditions, enabling development of content and format of the messages necessary to achieve the desired goals. The goals include negotiation of a load schedule that meets the global requirements (contained in the Mission Manager) and local power system requirements (contained in the Autonomous Power Controller), and communication of off-plan disturbances that arise while executing a negotiated plan. The message content is developed in two steps: first, a set of rapid-prototyping "paper" simulations are preformed; then the resultant optimized messages are codified for computer communication for use in automated testing.

Automated support for system's engineering and operations - The development of new paradigms

NASA Technical Reports Server (NTRS)

Truszkowski, Walt; Hall, Gardiner A.; Jaworski, Allan; Zoch, David

1992-01-01

Technological developments in spacecraft ground operations are reviewed. The technological, operations-oriented, managerial, and economic factors driving the evolution of the Mission Operations Control Center (MOCC), and its predecessor the Operational Control Center are examined. The functional components of the various MOCC subsystems are outlined. A brief overview is given of the concepts behind the The Knowledge-Based Software Engineering Environment, the Generic Spacecraft Analysis Assistant, and the Knowledge From Pictures tool.

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.

How To Cover NASA's Chandra X-ray Observatory

NASA Astrophysics Data System (ADS)

1999-07-01

NASA's newest space telescope, the Chandra X-ray Observatory, is scheduled for launch not earlier than July 20, 1999, aboard Space Shuttle mission STS-93. The world's most powerful X-ray observatory, Chandra will join the Hubble Space Telescope and NASA's other great observatories in an unprecedented study of our universe. With its capability to "see" an otherwise invisible but violent, vibrant and ever-changing universe, Chandra will provide insights into the universe's structure and evolution. The following information is designed to assist news media representatives cover launch and activation of the Chandra X-ray Observatory. Covering from the Chandra Control Center NASA will establish a news center at the Chandra X-ray Observatory Operations Control Center in Cambridge, Mass., during the critical period of launch and early activation. The news center will be open from approximately two days prior to launch until the observatory is established in its operating orbit approximately 11 days after launch. The telephone numbers for the news center are: (617) 496-4454 (617) 496-4462 (617) 496-4484 The news center will be staffed around the clock during the Shuttle mission by media relations officers knowledgeable about the Chandra mission and its status. Media covering from the news center will be provided work space and have opportunities for face-to-face interviews with Chandra management, control team members and Chandra scientists. They will be able to participate in daily Chandra status briefings and have access to a special control room viewing area. Additionally, media covering from Cambridge will receive periodic status reports on Chandra and the STS-93 mission, and will be able to participate in interactive televised briefings on the STS-93 mission originating from other NASA centers. While advance accreditation is not required, media interested in covering Chandra from the Operations Control Center should contact Dave Drachlis by telephone at (256) 544-0031 in advance of the mission to make arrangements for special support, such as telephone service, and uplink or remote truck parking. Covering from the Kennedy Space Center The Kennedy Space Center, Fla., news center is primarily responsible for disseminating information about the Shuttle countdown and launch. However, media relations officers knowledgeable about Chandra will be present at the Kennedy news center through launch. Additionally, some members of the Chandra management and science team will be at the Kennedy Space Center and available for interviews through launch. Media interested in covering the Chandra launch from the Kennedy Space Center should contact its Public Affairs Office at (407) 867-2468. Prior accreditation is required. Covering from the Johnson Space Center The Johnson Space Center, Houston, Texas, news center has responsibility for disseminating information about STS-93 flight operations. Media interested in covering the mission from the Johnson Space Center should contact its Public Affairs Office at (281) 483-5111. Prior accreditation is required. Status Reports During the STS-93 Space Shuttle mission to launch Chandra, NASA will issue twice-daily status reports from the Chandra Operations Control Center in Cambridge, Mass. Following the Shuttle mission, through Chandra's on-orbit checkout period, reports will be issued weekly. These reports are available via the Internet at: http://chandra.msfc.nasa.gov Press Briefings During the Space Shuttle mission to launch the observatory, NASA will conduct daily press briefings on the status of the observatory. These briefings will be conducted at the Chandra Operations Control Center in Cambridge, Mass. Media briefings will be broadcast on NASA Television (see below). Media without access to NASA Television may monitor the briefings by calling (256) 544-5300 and asking to be connected to the NASA Television audio feed. A briefing schedule will be released before launch and updated as appropriate during the mission. NASA Television The launch and early activation of the Chandra X-ray Observatory will be carried live on NASA Television, available through the GE2 satellite system, which is located on Transponder 9C, at 85 degrees west longitude, frequency 3880.0 MHz, audio 6.8 MHz. Around-the-clock, up-to-the minute commentary, television and daily briefings on Chandra's status will originate from the Chandra Operations Control Center in Cambridge, Mass., during Shuttle Mission STS-93. Internet Information Up-to-date, comprehensive information on the Chandra X-ray Observatory is available to news media on the Internet at: http://chandra.harvard.edu The latest status reports, news releases, photos, fact sheets and background archives, as well as links to other Chandra-related sites, are available at this address. Live Shots - Television Back-hauls Television station news departments may conduct live, or live-to-tape interviews via the NASA satellite with Chandra program managers, scientists and control team members prior to, during, and following the launch of Chandra. For additional information or to arrange interviews, broadcasters may contact Dave Drachlis at (256) 544-0031. Interviews Members of the Chandra development, operations, and science teams are available to the news media for interviews upon request. NASA TV on the web

Enviromnental Control and Life Support Systems for Mars Missions - Issues and Concerns for Planetary Protection

NASA Technical Reports Server (NTRS)

Barta, Daniel J.; Anderson, Molly S.; Lange, Kevin

2015-01-01

Planetary protection represents an additional set of requirements that generally have not been considered by developers of technologies for Environmental Control and Life Support Systems (ECLSS). Planetary protection guidelines will affect the kind of operations, processes, and functions that can take place during future human planetary exploration missions. Ultimately, there will be an effect on mission costs, including the mission trade space when planetary protection requirements begin to drive vehicle deisgn in a concrete way. Planetary protection requirements need to be considered early in technology development and mission programs in order to estimate these impacts and push back on requirements or find efficient ways to perform necessary functions. It is expected that planetary protection will be a significant factor during technology selection and system architecture design for future missions.

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 control sample reported a level of support from their management that compared favorably to national norms. American mission control personnel and Russian crewmembers reported higher supervisor support than American crewmembers and Russian mission control personnel. We will present the specific issues underlying these findings and compare and contrast the results from the two datasets. Although specific to space station personnel, our results are consistent with recent management, cultural, and aerospace research. We aim to use our results to improve training for current and future mission control personnel.

MOCR activity during Day 6 of STS-3 mission

NASA Technical Reports Server (NTRS)

1982-01-01

Andrew A. Fullerton, the six-year-old son of STS-3 pilot C. Gordon Fullerton, watches a television monitor in the mission control center's viewing room (28802); Mrs. Marie J. Fullerton in the mission control center's viewing room. Other members of the STS-3 pilot's family are seated on each side of Mrs. Fullerton. His sister, Jeanne Dockham, is at left foreground; son Andrew A., at right foreground. Mr. and Mrs. E. G. Buettner, Mrs. Fullerton's parents, are seated at center, and beyond them is Mrs. Charles R. Fullerton, the astronaut's mother (28803); Mary Ann Austin seated at the remote manipulator sytem (RMS) console in the mission operations control room (MOCR) shares the scene with a representation of a 1/15-scale model of the Canadian-built remote manipulator system arm (28804).

Saturn Apollo Program

NASA Image and Video Library

1969-06-24

The Apollo 11 mission, the first manned lunar mission, launched from the Kennedy Space Center, Florida via the Marshall Space Flight Center (MSFC) developed Saturn V launch vehicle on July 16, 1969 and safely returned to Earth on July 24, 1969. Aboard he space craft were astronauts Neil A. Armstrong, commander; Michael Collins, Command Module (CM) pilot; and Edwin E. Aldrin Jr., Lunar Module (LM) pilot. The CM, piloted by Michael Collins remained in a parking orbit around the Moon while the LM, named “Eagle’’, carrying astronauts Neil Armstrong and Edwin Aldrin, landed on the Moon. During 2½ hours of surface exploration, the crew collected 47 pounds of lunar surface material for analysis back on Earth. Splashdown occurred in the Pacific Ocean on July 24, 1969. This overall view of the Mission Operations Control Room in the Mission Control Center at the NASA Manned Spacecraft Center (MSC) in Houston Texas shows the jubilation of the celebration of mission success. Mission controllers wave their American flags just after Apollo 11 had been recovered from the Pacific Ocean.

Tug fleet and ground operations schedules and controls. Volume 2: part 1

NASA Technical Reports Server (NTRS)

1975-01-01

This Tug Fleet and Ground Operations Schedules and Controls Study addresses both ground operational data and technical requirements that span the Tug planning phase and operations phase. A similar study covering mission operations (by others) provides the complimentary flight operations details. The two studies provide the planning data requirements, resource allocation, and control milestones for supporting the requirements of the STS program. This Tug Fleet and Ground Operations Schedules and Controls Study incorporates the basic ground operations requirements and concepts provided by previous studies with the interrelationships of the planning, IUS transition, and Tug fleet operations phases. The interrelationships of these phases were studied as a system to optimize overall program benefits and minimize operational risk factors.

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.

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.

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 enough time to capture variations in relay asset interactions, Earth/Mars time phasing, and seasonal variations in holidays). This model is used to estimate the ops efficiency factor for each operations configuration. The second model in a separate Excel spreadsheet is a scenario model, which uses the sol types to rack up the total number of "scenario sols" for that scenario (in other words, the ideal number of sols it would take to perform the scenario objectives). Then, the number of sols requiring ground in the loop is calculated based on the soil types contained in the given scenario. Next, the scenario contains a description of what sequence of operations configurations is used, for how many days each, and this is used with the corresponding ops efficiency factors for each configuration to calculate the "ops duration" corresponding to that scenario. Finally, a margin is applied to determine the minimum surface lifetime required for that scenario. Typically, this level of analysis has not been performed until much later in the mission, and has not been able to influence mission design. Further, the notion of moving to sustainable operations during Prime Mission - and the effect that that move would have on surface mission productivity and mission objective choices - has not been encountered until the most recent rover missions (MSL and Mars 2018).

Autonomous and Autonomic Systems: A Paradigm for Future Space Exploration Missions

NASA Technical Reports Server (NTRS)

Truszkowski, Walter F.; Hinchey, Michael G.; Rash, James L.; Rouff, Christopher A.

2004-01-01

NASA increasingly will rely on autonomous systems concepts, not only in the mission control centers on the ground, but also on spacecraft and on rovers and other assets on extraterrestrial bodies. Automomy enables not only reduced operations costs, But also adaptable goal-driven functionality of mission systems. Space missions lacking autonomy will be unable to achieve the full range of advanced mission objectives, given that human control under dynamic environmental conditions will not be feasible due, in part, to the unavoidably high signal propagation latency and constrained data rates of mission communications links. While autonomy cost-effectively supports accomplishment of mission goals, autonomicity supports survivability of remote mission assets, especially when human tending is not feasible. Autonomic system properties (which ensure self-configuring, self-optimizing self-healing, and self-protecting behavior) conceptually may enable space missions of a higher order into any previously flown. Analysis of two NASA agent-based systems previously prototyped, and of a proposed future mission involving numerous cooperating spacecraft, illustrates how autonomous and autonomic system concepts may be brought to bear on future space missions.

AMO EXPRESS: A Command and Control Experiment for Crew Autonomy

NASA Technical Reports Server (NTRS)

Stetson, Howard K.; Frank, Jeremy; Cornelius, Randy; Haddock, Angie; Wang, Lui; Garner, Larry

2015-01-01

NASA is investigating a range of future human spaceflight missions, including both Mars-distance and Near Earth Object (NEO) targets. Of significant importance for these missions is the balance between crew autonomy and vehicle automation. As distance from Earth results in increasing communication delays, future crews need both the capability and authority to independently make decisions. However, small crews cannot take on all functions performed by ground today, and so vehicles must be more automated to reduce the crew workload for such missions. NASA's Advanced Exploration Systems Program funded Autonomous Mission Operations (AMO) project conducted an autonomous command and control demonstration of intelligent procedures to automatically initialize a rack onboard the International Space Station (ISS) with power and thermal interfaces, and involving core and payload command and telemetry processing, without support from ground controllers. This autonomous operations capability is enabling in scenarios such as a crew medical emergency, and representative of other spacecraft autonomy challenges. The experiment was conducted using the Expedite the Processing of Experiments for Space Station (EXPRESS) rack 7, which was located in the Port 2 location within the U.S Laboratory onboard the International Space Station (ISS). Activation and deactivation of this facility is time consuming and operationally intensive, requiring coordination of three flight control positions, 47 nominal steps, 57 commands, 276 telemetry checks, and coordination of multiple ISS systems (both core and payload). The autonomous operations concept includes a reduction of the amount of data a crew operator is required to verify during activation or de-activation, as well as integration of procedure execution status and relevant data in a single integrated display. During execution, the auto-procedures provide a step-by-step messaging paradigm and a high level status upon termination. This messaging and high level status is the only data generated for operator display. To enhance situational awareness of the operator, the Web-based Procedure Display (WebPD) provides a novel approach to the issues of procedure display and execution tracking. For this demonstration, the procedure was initiated and monitored from the ground. As the Timeliner sequences executed, their high level execution status was transmitted to ground, for WebPD consumption.

The SILEX experiment system operations

NASA Technical Reports Server (NTRS)

Demelenne, B.

1994-01-01

The European Space Agency is going to conduct an inter orbit link experiment which will connect a low Earth orbiting satellite and a Geostationary satellite via optical terminals. This experiment has been called SILEX (Semiconductor Inter satellite Link EXperiment). Two payloads will be built. One called PASTEL (PASsager de TELecommunication) will be embarked on the French Earth observation satellite SPOT4. The future European experimental data relay satellite ARTEMIS (Advanced Relay and TEchnology MISsion) will carry the OPALE terminal (Optical PAyload Experiment). The principal characteristic of the mission is a 50 Megabits flow of data transmitted via the optical satellite link. The relay satellite will route the data via its feeder link thus permitting a real time reception in the European region of images taken by the observation satellite. The PASTEL terminal has been designed to cover up to 9 communication sessions per day with an average of 5. The number of daily contact opportunities with the low earth orbiting satellite will be increased and the duration will be much longer than the traditional passes over a ground station. The terminals have an autonomy of 24 hours with respect to ground control. Each terminal will contain its own orbit model and that of its counter terminal for orbit prediction and for precise computation of pointing direction. Due to the very narrow field of view of the communication laser beam, the orbit propagation calculation needs to be done with a very high accuracy. The European Space Agency is responsible for the operation of both terminals. A PASTEL Mission Control System (PMCS) is being developed to control the PASTEL terminal on board SPOT4. The PMCS will interface with the SPOT4 Control Centre for the execution of the PASTEL operations. The PMCS will also interface with the ARTEMIS Mission Control System for the planning and the coordination of the operation. It is the first time that laser technology will be used to support inter-satellite links in Europe. Due to the complexity and experimental character of this new optical technology, the SILEX experiment control facilities will be designed to allow as much operational flexibility as possible.

Varying Levels of Automation on UAS Operator Responses to Traffic Resolution Advisories in Civil Airspace

NASA Technical Reports Server (NTRS)

Kenny, Caitlin; Fern, Lisa

2012-01-01

Continuing demand for the use of Unmanned Aircraft Systems (UAS) has put increasing pressure on operations in civil airspace. The need to fly UAS in the National Airspace System (NAS) in order to perform missions vital to national security and defense, emergency management, and science is increasing at a rapid pace. In order to ensure safe operations in the NAS, operators of unmanned aircraft, like those of manned aircraft, may be required to maintain separation assurance and avoid loss of separation with other aircraft while performing their mission tasks. This experiment investigated the effects of varying levels of automation on UAS operator performance and workload while responding to conflict resolution instructions provided by the Tactical Collision Avoidance System II (TCAS II) during a UAS mission in high-density airspace. The purpose of this study was not to investigate the safety of using TCAS II on UAS, but rather to examine the effect of automation on the ability of operators to respond to traffic collision alerts. Six licensed pilots were recruited to act as UAS operators for this study. Operators were instructed to follow a specified mission flight path, while maintaining radio contact with Air Traffic Control and responding to TCAS II resolution advisories. Operators flew four, 45 minute, experimental missions with four different levels of automation: Manual, Knobs, Management by Exception, and Fully Automated. All missions included TCAS II Resolution Advisories (RAs) that required operator attention and rerouting. Operator compliance and reaction time to RAs was measured, and post-run NASA-TLX ratings were collected to measure workload. Results showed significantly higher compliance rates, faster responses to TCAS II alerts, as well as less preemptive operator actions when higher levels of automation are implemented. Physical and Temporal ratings of workload were significantly higher in the Manual condition than in the Management by Exception and Fully Automated conditions.

SOLON: An autonomous vehicle mission planner

NASA Technical Reports Server (NTRS)

Dudziak, M. J.

1987-01-01

The State-Operator Logic Machine (SOLON) Planner provides an architecture for effective real-time planning and replanning for an autonomous vehicle. The highlights of the system, which distinguish it from other AI-based planners that have been designed previously, are its hybrid application of state-driven control architecture and the use of both schematic representations and logic programming for the management of its knowledge base. SOLON is designed to provide multiple levels of planning for a single autonomous vehicle which is supplied with a skeletal, partially-specified mission plan at the outset of the vehicle's operations. This mission plan consists of a set of objectives, each of which will be decomposable by the planner into tasks. These tasks are themselves comparatively complex sets of actions which are executable by a conventional real-time control system which does not perform planning but which is capable of making adjustments or modifications to the provided tasks according to constraints and tolerances provided by the Planner. The current implementation of the SOLON is in the form of a real-time simulation of the Planner module of an Intelligent Vehicle Controller (IVC) on-board an autonomous underwater vehicle (AUV). The simulation is embedded within a larger simulator environment known as ICDS (Intelligent Controller Development System) operating on a Symbolics 3645/75 computer.

NEEMO 18-20: Analog Testing for Mitigation of Communication Latency During Human Space Exploration

NASA Technical Reports Server (NTRS)

Chappell, Steven P.; Beaton, Kara H.; Miller, Matthew J.; Graff, Trevor G.; Abercromby, Andrew F. J.; Gernhardt, Michael L.; Halcon, Christopher

2016-01-01

NASA Extreme Environment Mission Operations (NEEMO) is an underwater spaceflight analog that allows a true mission-like operational environment and uses buoyancy effects and added weight to simulate different gravity levels. Three missions were undertaken from 2014-2015, NEEMO's 18-20. All missions were performed at the Aquarius undersea research habitat. During each mission, the effects of communication latencies on operations concepts, timelines, and tasks were studied. METHODS: Twelve subjects (4 per mission) were weighed out to simulate near-zero or partial gravity extravehicular activity (EVA) and evaluated different operations concepts for integration and management of a simulated Earth-based science team (ST) to provide input and direction during exploration activities. Exploration traverses were preplanned based on precursor data. Subjects completed science-related tasks including pre-sampling surveys, geologic-based sampling, and marine-based sampling as a portion of their tasks on saturation dives up to 4 hours in duration that were designed to simulate extravehicular activity (EVA) on Mars or the moons of Mars. One-way communication latencies, 5 and 10 minutes between space and mission control, were simulated throughout the missions. Objective data included task completion times, total EVA times, crew idle time, translation time, ST assimilation time (defined as time available for ST to discuss data/imagery after data acquisition). Subjective data included acceptability, simulation quality, capability assessment ratings, and comments. RESULTS: Precursor data can be used effectively to plan and execute exploration traverse EVAs (plans included detailed location of science sites, high-fidelity imagery of the sites, and directions to landmarks of interest within a site). Operations concepts that allow for pre-sampling surveys enable efficient traverse execution and meaningful Mission Control Center (MCC) interaction across communication latencies and can be done with minimal crew idle time. Imagery and contextual information from the EVA crew that is transmitted real-time to the intravehicular (IV) crewmember(s) can be used to verify that exploration traverse plans are being executed correctly. That same data can be effectively used by MCC (across comm latency) to provide meaningful feedback and instruction to the crew regarding sampling priorities, additional tasks, and changes to the EVA timeline. Text / data capabilities are preferred over voice capabilities between MCC and IV when executing exploration traverse plans over communication latency.

BLDG. 30 - APOLLO-SOYUZ TEST PROJECT (ASTP) SIMS - FLIGHT DIRECTION - JSC

NASA Image and Video Library

1975-03-20

S75-23638 (20 March 1975) --- An overall view of the Mission Operations Control Room in the Mission Control Center during joint ASTP simulation activity at NASA's Johnson Space Center. The simulations are part of the preparations for the U.S.-USSR Apollo-Soyuz Test Project docking mission in Earth orbit scheduled for July 1975. M.P. Frank (seated, right) is the senior American flight director for the mission. Sigurd A. Sjoberg (in center, checked jacket), JSC Deputy Director, watches some of the console activity. George W.S. Abbey, Technical Assistant to the JSC Director, is standing next to Sjoberg. The television monitor in the background shows Soviet Soyuz crew activity from the Soviet Union.

Skylab Saturn 1B flight manual

NASA Technical Reports Server (NTRS)

1972-01-01

A Saturn 1B Flight Manual provides launch vehicle systems descriptions and predicted performance data for the Skylab missions. Vehicle SL-2 (SA-206) is the baseline for this manual; but, as a result of the great similarity, the material is representative of SL-3 and SL-4 launch vehicles, also. The Flight Manual is not a control document but is intended primarily as an aid to astronauts who are training for Skylab missions. In order to provide a comprehensive reference for that purpose, the manual also contains descriptions of the ground support interfaces, prelaunch operations, and emergency procedures. Mission variables and constraints are summarized, and mission control monitoring and data flow during launch preparation and flight are discussed.

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.

Operational Alignment in Predator Training Research

DTIC Science & Technology

2014-04-21

to the SO and, down the road, the Mission Intelligence Coordinator ( MIC ). 2. X-Plane 9 is COTS software and serves as the aeronautical simulation...uses to communicate with ground forces, command and control (C2) elements, and the Mission Intelligence Coordinator ( MIC ), among others. 10. LNCS...because key events can be scripted and initiated as appropriate, while distractor events like a villager walking around a market can be controlled by

Space Weather Forecasting at the Joint Space Operations Center (JSpOC)

NASA Astrophysics Data System (ADS)

Nava, O.

2012-12-01

The Joint Space Operations Center (JSpOC) at Vandenberg Air Force Base is the command and control focal point for the operational employment of worldwide joint space forces. The JSpOC focuses on planning and executing US Strategic Command's Joint Functional Component Command for Space (JFCC SPACE) mission. Through the JSpOC, the Weather Specialty Team (WST) monitors space and terrestrial weather effects, plans and assesses weather impacts on military operations, and provides reach-back support for deployed theater solar and terrestrial needs. This presentation will detail how space weather affects the JSpOC mission set and how the scientific community can enhance the WST's capabilities and effectiveness.

Case Studies in Crewed Spacecraft Environmental Control and Life Support System Process Compatibility and Cabin Environmental Impact

NASA Technical Reports Server (NTRS)

Perry, J. L.

2017-01-01

Contamination of a crewed spacecraft's cabin environment leading to environmental control and life support system (ECLSS) functional capability and operational margin degradation or loss can have an adverse effect on NASA's space exploration mission figures of merit-safety, mission success, effectiveness, and affordability. The role of evaluating the ECLSS's compatibility and cabin environmental impact as a key component of pass trace contaminant control is presented and the technical approach is described in the context of implementing NASA's safety and mission success objectives. Assessment examples are presented for a variety of chemicals used in vehicle systems and experiment hardware for the International Space Station program. The ECLSS compatibility and cabin environmental impact assessment approach, which can be applied to any crewed spacecraft development and operational effort, can provide guidance to crewed spacecraft system and payload developers relative to design criteria assigned ECLSS compatibility and cabin environmental impact ratings can be used by payload and system developers as criteria for ensuring adequate physical and operational containment. In additional to serving as an aid for guiding containment design, the assessments can guide flight rule and procedure development toward protecting the ECLSS as well as approaches for contamination event remediation.

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.

Astronaut Susan Helms uses laser instrument during SPARTAN 201 operations

NASA Image and Video Library

1994-09-16

STS064-33-003 (9-20 Sept. 1994) --- Astronaut Susan J. Helms, STS-64 mission specialist, uses a laser instrument during operations with the Shuttle Pointed Autonomous Research Tool for Astronomy 201 (SPARTAN 201). Helms, who spent many mission hours at the controls of the Remote Manipulator System (RMS), joined five other NASA astronauts for almost 11 days in Earth orbit aboard the space shuttle Discovery. Photo credit: NASA or National Aeronautics and Space Administration

(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.

Intelligent Launch and Range Operations Virtual Test Bed (ILRO-VTB)

NASA Technical Reports Server (NTRS)

Bardina, Jorge; Rajkumar, T.

2003-01-01

Intelligent Launch and Range Operations Virtual Test Bed (ILRO-VTB) is a real-time web-based command and control, communication, and intelligent simulation environment of ground-vehicle, launch and range operation activities. ILRO-VTB consists of a variety of simulation models combined with commercial and indigenous software developments (NASA Ames). It creates a hybrid software/hardware environment suitable for testing various integrated control system components of launch and range. The dynamic interactions of the integrated simulated control systems are not well understood. Insight into such systems can only be achieved through simulation/emulation. For that reason, NASA has established a VTB where we can learn the actual control and dynamics of designs for future space programs, including testing and performance evaluation. The current implementation of the VTB simulates the operations of a sub-orbital vehicle of mission, control, ground-vehicle engineering, launch and range operations. The present development of the test bed simulates the operations of Space Shuttle Vehicle (SSV) at NASA Kennedy Space Center. The test bed supports a wide variety of shuttle missions with ancillary modeling capabilities like weather forecasting, lightning tracker, toxic gas dispersion model, debris dispersion model, telemetry, trajectory modeling, ground operations, payload models and etc. To achieve the simulations, all models are linked using Common Object Request Broker Architecture (CORBA). The test bed provides opportunities for government, universities, researchers and industries to do a real time of shuttle launch in cyber space.

Intelligent launch and range operations virtual testbed (ILRO-VTB)

NASA Astrophysics Data System (ADS)

Bardina, Jorge; Rajkumar, Thirumalainambi

2003-09-01

Intelligent Launch and Range Operations Virtual Test Bed (ILRO-VTB) is a real-time web-based command and control, communication, and intelligent simulation environment of ground-vehicle, launch and range operation activities. ILRO-VTB consists of a variety of simulation models combined with commercial and indigenous software developments (NASA Ames). It creates a hybrid software/hardware environment suitable for testing various integrated control system components of launch and range. The dynamic interactions of the integrated simulated control systems are not well understood. Insight into such systems can only be achieved through simulation/emulation. For that reason, NASA has established a VTB where we can learn the actual control and dynamics of designs for future space programs, including testing and performance evaluation. The current implementation of the VTB simulates the operations of a sub-orbital vehicle of mission, control, ground-vehicle engineering, launch and range operations. The present development of the test bed simulates the operations of Space Shuttle Vehicle (SSV) at NASA Kennedy Space Center. The test bed supports a wide variety of shuttle missions with ancillary modeling capabilities like weather forecasting, lightning tracker, toxic gas dispersion model, debris dispersion model, telemetry, trajectory modeling, ground operations, payload models and etc. To achieve the simulations, all models are linked using Common Object Request Broker Architecture (CORBA). The test bed provides opportunities for government, universities, researchers and industries to do a real time of shuttle launch in cyber space.

Contrast in low-cost operational concepts for orbiting satellites

NASA Astrophysics Data System (ADS)

Walyus, Keith D.; Reis, James; Bradley, Arthur J.

2002-12-01

Older spacecraft missions, especially those in low Earth orbit with telemetry intensive requirements, required round-the-clock control center staffing. The state of technology relied on control center personnel to continually examine data, make decisions, resolve anomalies, and file reports. Hubble Space Telescope (HST) is a prime example of this description. Technological advancements in hardware and software over the last decade have yielded increases in productivity and operational efficiency, which result in lower cost. The re-engineering effort of HST, which has recently concluded, utilized emerging technology to reduce cost and increase productivity. New missions, of which NASA's Transition Region and Coronal Explorer Satellite (TRACE) is an example, have benefited from recent technological advancements and are more cost-effective than when HST was first launched. During its launch (1998) and early orbit phase, the TRACE Flight Operations Team (FOT) employed continually staffed operations. Yet once the mission entered its nominal phase, the FOT reduced their staffing to standard weekday business hours. Operations were still conducted at night and during the weekends, but these operations occurred autonomously without compromising their high standards for data collections. For the HST, which launched in 1990, reduced cost operations will employ a different operational concept, when the spacecraft enters its low-cost phase after its final servicing mission in 2004. Primarily due to the spacecraft"s design, the HST Project has determined that single-shift operations will introduce unacceptable risks for the amount of dollars saved. More importantly, significant cost-savings can still be achieved by changing the operational concept for the FOT, while still maintaining round-the-clock staffing. It"s important to note that the low-cost solutions obtained for one satellite may not be applicable for other satellites. This paper will contrast the differences between low-cost operational concepts for a satellite launched in 1998 versus a satellite launched in 1990.

NASA Flight Planning Branch Space Shuttle Lessons Learned

NASA Technical Reports Server (NTRS)

Clevenger, Jennifer D.; Bristol, Douglas J.; Whitney, Gregory R.; Blanton, Mark R.; Reynolds, F. Fisher, III

2011-01-01

Planning products and procedures that allowed the mission Flight Control Teams and the Astronaut crews to plan, train and fly every Space Shuttle mission were developed by the Flight Planning Branch at the NASA Johnson Space Center in Houston, Texas. As the Space Shuttle Program came to a close, lessons learned were collected from each phase of the successful execution of these Space Shuttle missions. Specific examples of how roles and responsibilities of console positions that develop the crew and vehicle attitude timelines have been analyzed and will be discussed. Additionally, the relationships and procedural hurdles experienced through international collaboration have molded operations. These facets will be explored and related to current and future operations with the International Space Station and future vehicles. Along with these important aspects, the evolution of technology and continual improvement of data transfer tools between the Space Shuttle and ground team has also defined specific lessons used in improving the control team s effectiveness. Methodologies to communicate and transmit messages, images, and files from the Mission Control Center to the Orbiter evolved over several years. These lessons were vital in shaping the effectiveness of safe and successful mission planning and have been applied to current mission planning work in addition to being incorporated into future space flight planning. The critical lessons from all aspects of previous plan, train, and fly phases of Space Shuttle flight missions are not only documented in this paper, but are also discussed regarding how they pertain to changes in process and consideration for future space flight planning.

Flight Planning Branch Space Shuttle Lessons Learned

NASA Technical Reports Server (NTRS)

Price, Jennifer B.; Scott, Tracy A.; Hyde, Crystal M.

2011-01-01

Planning products and procedures that allow the mission flight control teams and the astronaut crews to plan, train and fly every Space Shuttle mission have been developed by the Flight Planning Branch at the NASA Johnson Space Center. As the Space Shuttle Program ends, lessons learned have been collected from each phase of the successful execution of these Shuttle missions. Specific examples of how roles and responsibilities of console positions that develop the crew and vehicle attitude timelines will be discussed, as well as techniques and methods used to solve complex spacecraft and instrument orientation problems. Additionally, the relationships and procedural hurdles experienced through international collaboration have molded operations. These facets will be explored and related to current and future operations with the International Space Station and future vehicles. Along with these important aspects, the evolution of technology and continual improvement of data transfer tools between the shuttle and ground team has also defined specific lessons used in the improving the control teams effectiveness. Methodologies to communicate and transmit messages, images, and files from Mission Control to the Orbiter evolved over several years. These lessons have been vital in shaping the effectiveness of safe and successful mission planning that have been applied to current mission planning work in addition to being incorporated into future space flight planning. The critical lessons from all aspects of previous plan, train, and fly phases of shuttle flight missions are not only documented in this paper, but are also discussed as how they pertain to changes in process and consideration for future space flight planning.

Logistics and operations implications of manual control of spacecraft docking maneuvers

NASA Technical Reports Server (NTRS)

Brody, Adam R.; Ellis, Stephen R.

1991-01-01

The implications of logistics and operations on the manual control of spacecraft docking are discussed. The results of simulation studies to investigate fuel and time cost tradeoffs are reviewed and discussed. Comparisons of acceleration control and pulse control are presented to evaluate the effects of astronauts being instructed to use pulse mode for fuel conservation. The applications of the findings to moon and Mars missions are addressed.

Rosetta following a living comet

NASA Astrophysics Data System (ADS)

Accomazzo, Andrea; Ferri, Paolo; Lodiot, Sylvain; Pellon-Bailon, Jose-Luis; Hubault, Armelle; Porta, Roberto; Urbanek, Jakub; Kay, Ritchie; Eiblmaier, Matthias; Francisco, Tiago

2016-09-01

The International Rosetta Mission was launched on 2nd March 2004 on its 10 year journey to rendezvous with comet 67P Churyumov-Gerasimenko. Rosetta performed comet orbit insertion on the 6th of August 2014, after which it characterised the nucleus and orbited it at altitudes as low as a few kilometres. In November 2014 Rosetta delivered the lander Philae to perform the first soft landing ever on the surface of a comet. The critical landing operations have been conducted with remarkable accuracy and will constitute one of the most important achievements in the history of spaceflight. After this critical operation, Rosetta began the escort phase of the comet in its journey in the Solar System heading to the perihelion, reached in August 2015. Throughout this period, the comet environment kept changing with increasing gas and dust emissions. A first phase of bound orbits was followed by a sequence of complex flyby segments which allowed the scientific instruments to perform in depth investigation of the comet environment and nucleus. The unpredictable nature of the comet activity forced the mission control team to implement unplanned changes to the flight plan prepared for this mission phase and to plan the whole mission in a more dynamic way than originally conceived. This paper describes the details of the landing operations and of the main comet escort phase. It also includes the mission status as achieved after perihelion and the findings about the evolution of the comet and its environment from a mission operations point of view. The lessons learned from this unique and complex operations phase and the plans for the next mission phases, which include a mission extension into 2016, are also described.

STS payloads mission control study continuation phase A-1. Volume 2-B: Task 2. Evaluation and refinement of implementation guidelines for the selected STS payload operator concept

NASA Technical Reports Server (NTRS)

1976-01-01

The functions of Payload Operations Control Centers (POCC) at JSC, GSFC, JPL, and non-NASA locations are analyzed to establish guidelines for standardization, and facilitate the development of a fully integrated NASA-wide system of ground facilities for all classes of payloads. Operational interfaces between the space transportation system operator and the payload operator elements are defined. The advantages and disadvantages of standardization are discussed.

Low-Power Operation and Plasma Characterization of a Qualification Model SPT-140 Hall Thruster for NASA Science Missions

NASA Technical Reports Server (NTRS)

Garner, Charles E.; Jorns, Benjamin A.; van Derventer, Steven; Hofer, Richard R.; Rickard, Ryan; Liang, Raymond; Delgado, Jorge

2015-01-01

Hall thruster systems based on commercial product lines can potentially lead to lower cost electric propulsion (EP) systems for deep space science missions. A 4.5-kW SPT-140 Hall thruster presently under qualification testing by SSL leverages the substantial heritage of the SPT-100 being flown on Russian and US commercial satellites. The Jet Propulsion Laboratory is exploring the use of commercial EP systems, including the SPT-140, for deep space science missions, and initiated a program to evaluate the SPT-140 in the areas of low power operation and thruster operating life. A qualification model SPT-140 designated QM002 was evaluated for operation and plasma properties along channel centerline, from 4.5 kW to 0.8 kW. Additional testing was performed on a development model SPT-140 designated DM4 to evaluate operation with a Moog proportional flow control valve (PFCV). The PFCV was commanded by an SSL engineering model PPU-140 Power Processing Unit (PPU). Performance measurements on QM002 at 0.8 kW discharge power were 50 mN of thrust at a total specific impulse of 1250 s, a total thruster efficiency of 0.38, and discharge current oscillations of under 3% of the mean current. Steady-state operation at 0.8 kW was demonstrated during a 27 h firing. The SPT-140 DM4 was operated in closed-loop control of the discharge current with the PFCV and PPU over discharge power levels of 0.8-4.5 kW. QM002 and DM4 test data indicate that the SPT-140 design is a viable candidate for NASA missions requiring power throttling down to low thruster input power.

Discussions on attitude determination and control system for micro/nano/pico-satellites considering survivability based on Hodoyoshi-3 and 4 experiences

NASA Astrophysics Data System (ADS)

Nakasuka, Shinichi; Miyata, Kikuko; Tsuruda, Yoshihiro; Aoyanagi, Yoshihide; Matsumoto, Takeshi

2018-04-01

The recent advancement of micro/nano/pico-satellites technologies encourages many universities to develop three axis stabilized satellites. As three axis stabilization is high level technology requiring the proper functioning of various sensors, actuators and control software, many early satellites failed in their initial operation phase because of shortage of solar power generation or inability to realize the initial step of missions because of unexpected attitude control system performance. These results come from failure to design the satellite attitude determination and control system (ADCS) appropriately and not considering "satellite survivability." ADCS should be designed such that even if some sensors or actuators cannot work as expected, the satellite can survive and carry out some of its missions, even if not full. This paper discusses how to realize ADCS while taking satellite survivability into account, based on our experiences of design and in-orbit operations of Hodoyoshi-3 and 4 satellites launched in 2014, which suffered from various component anomalies but could complete their missions.

OMV man/system simulation integration: A preliminary analysis and recommendation

NASA Technical Reports Server (NTRS)

Rogers, Jon G.

1988-01-01

The Orbital Maneuvering Vehicle (OMV) presents a series of challenges to the human operator. Some are unique to the OMV system itself, and are largely due to remote control versus control from the cockpit. Other challenges are not necessarily unique to the OMV, but are characteristic of many man-machine space flight systems. All of these challenges affect the operator's ability to perform his portion of the mission, and could lead to human error which might jeopardize the vehicle, mission, or both. It is imperative to make every effort to design the control and displays to facilitate the operator's task. The experimental program should address the perceptual, mediational, and motor dimensions of operator performance. With this in mind, a literature review with relevant design considerations was initiated, and a comprehensive outline of control/display parameters were developed. Out of this, a series of questions not answered in the literature was derived which can be converted into experimental protocols for the simulation program. A major task of the aircraft pilot as well as the OMV operator is prediction. Certain display principles have proved to enhance the pilot's ability to predict. A brief examination of some of these principles in relationship to OMV may be useful.

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

Mission simulation as an approach to develop requirements for automation in Advanced Life Support Systems

NASA Technical Reports Server (NTRS)

Erickson, J. D.; Eckelkamp, R. E.; Barta, D. J.; Dragg, J.; Henninger, D. L. (Principal Investigator)

1996-01-01

This paper examines mission simulation as an approach to develop requirements for automation and robotics for Advanced Life Support Systems (ALSS). The focus is on requirements and applications for command and control, control and monitoring, situation assessment and response, diagnosis and recovery, adaptive planning and scheduling, and other automation applications in addition to mechanized equipment and robotics applications to reduce the excessive human labor requirements to operate and maintain an ALSS. Based on principles of systems engineering, an approach is proposed to assess requirements for automation and robotics using mission simulation tools. First, the story of a simulated mission is defined in terms of processes with attendant types of resources needed, including options for use of automation and robotic systems. Next, systems dynamics models are used in simulation to reveal the implications for selected resource allocation schemes in terms of resources required to complete operational tasks. The simulations not only help establish ALSS design criteria, but also may offer guidance to ALSS research efforts by identifying gaps in knowledge about procedures and/or biophysical processes. Simulations of a planned one-year mission with 4 crewmembers in a Human Rated Test Facility are presented as an approach to evaluation of mission feasibility and definition of automation and robotics requirements.

Increasing Intelligence, Surveillance, and Reconnaissance (ISR) Operational Agility through Mission Command

DTIC Science & Technology

2016-06-10

Counterinsurgency COM Collections Operations Management CONOP Concept of Operations CRM Collections Requirements Management DOD Department of...collection requirements management ( CRM ) and collection operations management (COM). CRM is the authoritative development and control of collection...management ( CRM ) and collections operations management (COM) (see figure 6). In general, CRM advocates and prioritizes customer requirements while

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.

Rendezvous and Proximity Operations of the Space Shuttle

NASA Technical Reports Server (NTRS)

Goodman, John L.

2005-01-01

Space Shuttle rendezous missions presented unique challenges that were not fully recognized when the Shuttle was designed. Rendezvous targets could be passive (i.e., no lights or transponders), and not designed to facilitate Shuttle rendezvous, proximity operations and retrieval. Shuttle reaction control system jet plume impingement on target spacecraft presented induced dynamics, structural loading and contamination concerns. These issues, along with limited forward reaction control system propellant, drove a change from the Gemimi/Apollo coelliptic profile heritage to a stable orbit profile, and the development of new proximity operations techniques. Multiple scientific and on-orbit servicing missions and crew exchange, assembly and replinishment flights to Mir and to the International Space Station drove further profile and piloting technique changes, including new relative navigation sensors and new computer generated piloting cues.

Stationkeeping of the First Earth-Moon Libration Orbiters: The ARTEMIS Mission

NASA Technical Reports Server (NTRS)

Folta, David; Woodard, Mark; Cosgrove, D.

2011-01-01

Libration point orbits near collinear locations are inherently unstable and must be controlled. For Acceleration Reconnection and Turbulence and Electrodynamics of the Moon's Interaction with the Sun (ARTEMIS) Earth-Moon Lissajous orbit operations, stationkeeping is challenging because of short time scales, large orbital eccentricity of the secondary, and solar gravitational and radiation pressure perturbations. ARTEMIS is the first NASA mission continuously controlled at both Earth-Moon L1 and L2 locations and uses a balance of optimization, spacecraft implementation and constraints, and multi-body dynamics. Stationkeeping results are compared to pre-mission research including mode directions.

SKYLAB (SL) - ORBITAL WORKSHOP (OWS) - JSC

NASA Image and Video Library

1973-05-29

S73-26849 (25 May 1973) --- Four flight directors for the Skylab 1 and 2 mission are grouped around the flight director's console in the Mission Operations Control Room in the Mission Control Center at Johnson Space Center during the Skylab 2 Command/Service Module (CSM) "fly around" inspection of the Skylab 1 space station cluster. They are, going counterclockwise from center foreground, Donald R. Puddy (white shirt), Milton Windler, Philip C. Shaffer and M.P. Frank. A view of the Skylab 1 Orbital Workshop seen from the Skylab 2 CSM is visible on the television monitor in the background. Photo credit: NASA

S70-34903

NASA Image and Video Library

1970-04-14

S70-34903 (14 April 1970) --- Dr. Thomas O. Paine, Administrator, National Aeronautics and Space Administration (NASA), talks on the telephone to President Richard M. Nixon. Dr. Paine is seated at his console in the Mission Operations Control Room (MOCR) at the Mission Control Center (MCC), Manned Spacecraft Center (MSC). Also pictured are Dr. Rocco Petrone, Apollo program director, Office Manned Spaceflight, NASA Headquarters (facing camera); and Chester M. Lee, Apollo mission director, Office of Manned Spaceflight, NASA Headquarters (HQ). Dr. Paine and the President were discussing the revised Apollo 13 flight plan following discovery of an oxygen cell failure in the Apollo 13 spacecraft several hours earlier.

A Multi-mission Event-Driven Component-Based System for Support of Flight Software Development, ATLO, and Operations first used by the Mars Science Laboratory (MSL) Project

NASA Technical Reports Server (NTRS)

Dehghani, Navid; Tankenson, Michael

2006-01-01

This paper details an architectural description of the Mission Data Processing and Control System (MPCS), an event-driven, multi-mission ground data processing components providing uplink, downlink, and data management capabilities which will support the Mars Science Laboratory (MSL) project as its first target mission. MPCS is developed based on a set of small reusable components, implemented in Java, each designed with a specific function and well-defined interfaces. An industry standard messaging bus is used to transfer information among system components. Components generate standard messages which are used to capture system information, as well as triggers to support the event-driven architecture of the system. Event-driven systems are highly desirable for processing high-rate telemetry (science and engineering) data, and for supporting automation for many mission operations processes.

Apollo 15 Mission Report

NASA Technical Reports Server (NTRS)

1971-01-01

A detailed discussion is presented of the Apollo 15 mission, which conducted exploration of the moon over longer periods, greater ranges, and with more instruments of scientific data acquisition than previous missions. The topics include trajectory, lunar surface science, inflight science and photography, command and service module performance, lunar module performance, lunar surface operational equipment, pilot's report, biomedical evaluation, mission support performance, assessment of mission objectives, launch phase summary, anomaly summary, and vehicle and equipment descriptions. The capability of transporting larger payloads and extending time on the moon were demonstrated. The ground-controlled TV camera allowed greater real-time participation by earth-bound personnel. The crew operated more as scientists and relied more on ground support team for systems monitoring. The modified pressure garment and portable life support system provided better mobility and extended EVA time. The lunar roving vehicle and the lunar communications relay unit were also demonstrated.

Cassini End of Mission

NASA Image and Video Library

2017-09-14

Cassini program manager at JPL, Earl Maize, is seen in mission control of the Space Flight Operations Center as the Cassini team wait for the spacecraft to establish a connection with NASA's Deep Space Network to begin the final playback of its data recorder, Thursday, Sept. 14, 2017 at NASA's Jet Propulsion Laboratory in Pasadena, California. Since its arrival in 2004, the Cassini-Huygens mission has been a discovery machine, revolutionizing our knowledge of the Saturn system and captivating us with data and images never before obtained with such detail and clarity. On Sept. 15, 2017, operators will deliberately plunge the spacecraft into Saturn, as Cassini gathered science until the end. The “plunge” ensures Saturn’s moons will remain pristine for future exploration. During Cassini’s final days, mission team members from all around the world gathered at NASA’s Jet Propulsion Laboratory, Pasadena, California, to celebrate the achievements of this historic mission. Photo Credit: (NASA/Joel Kowsky)

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.

Report on the Stanford/KACST/AMES UVLED small satellite mission to demonstrate charge management of an electrically isolated proof mass for drag-free operation

NASA Astrophysics Data System (ADS)

Saraf, Shailendhar

A spacecraft demonstration of ultra-violet (UV) LEDs and UV LED charge management based on research done at Stanford University is being developed jointly by the King Abdulaziz City for Science and Technology (KACST) Saudi Arabia and NASA Ames Research Center, with an expected launch date of June 2014. This paper will report on the payload design and testing, mission preparation, satellite launch and payload bring -up in space. Mission lifetime is expected to be at least one month, during which time the ability for the UV LEDs to mitigate actual space-based charging and the effects of radiation on the UV LED device performance will be studied. Precise control over the potential of an electrically isolated proof mass is necessary for the operation of devices such as a Gravitational Reference Sensor (GRS) and satellite missions such as LISA. The mission will demonstrate that AlGaN UV LEDs operating at 255 nm are an effective low-cost, low-power and compact substitute for Mercury vapor lamps used in previous missions. The goal of the mission is to increase the UV LED device to TRL-9 and the charge management system to TRL-7.

[Potentiality of building-up the medical operations system for long-duration space missions by noncontact physiological functions recording during sleep time].

PubMed

Baevskiĭ, R M; Bogomolov, V V; Funtova, I I; Slepchenkova, I N; Chernikova, A G

2009-01-01

Methods of investigating the physiological functions in space crews on extended missions during night sleep are of much fundamental and practical substance. The design of experiment "Sonocard" utilizes the method of seismocardiography. Purpose of the experiment is to validate the procedures of noncontact in-sleep physiological data recoding which are potent to enhance the space crew medical operations system. The experiment was performed systematically by ISS Russian crew members starting from mission-16. The experimental procedure is easy and does not cause discomfort to human subjects. Results of the initial experimental sessions demonstrated that, as on Earth, sleep in microgravity is crucial for the recovery of body functional reserves and that the innovative technology is instrumental in studying the recovery processes as well as person unique patterns of adaptation to extended space mission. It also allows conclusions about sleep quality, mechanisms of recreation, and body functionality. These data may enrich substantially the information used by medical operators of the space missions control centers.

ARM Spacecraft Illustration

NASA Image and Video Library

2016-09-20

This graphic depicts the Asteroid Redirect Vehicle conducting a flyby of its target asteroid. During these flybys, the Asteroid Redirect Mission (ARM) would come within 0.6 miles (1 kilometer), generating imagery with resolution of up to 0.4 of an inch (1 centimeter) per pixel. The robotic segment of ARM will demonstrate advanced, high-power, high-throughput solar electric propulsion; advanced autonomous precision proximity operations at a low-gravity planetary body; and controlled touchdown and liftoff with a multi-ton mass. The crew segment of the mission will include spacewalk activities for sample selection, extraction, containment and return; and mission operations of integrated robotic and crewed vehicle stack -- all key components of future in-space operations for human missions to the Mars system. After collecting a multi-ton boulder from the asteroid, the robotic spacecraft will redirect the boulder to a crew-accessible orbit around the moon, where NASA plans to conduct a series of proving ground missions in the 2020s that will help validate capabilities needed for NASA's Journey to Mars. http://photojournal.jpl.nasa.gov/catalog/PIA21062

Variable-camber systems integration and operational performance of the AFTI/F-111 mission adaptive wing

NASA Technical Reports Server (NTRS)

Smith, John W.; Lock, Wilton P.; Payne, Gordon A.

1992-01-01

The advanced fighter technology integration, the AFTI/F-111 aircraft, is a preproduction F-111A testbed research airplane that was fitted with a smooth variable-camber mission adaptive wing. The camber was positioned and controlled by flexing the upper skins through rotary actuators and linkages driven by power drive units. The wing camber and control system are described. The measured servoactuator frequency responses are presented along with analytical predictions derived from the integrated characteristics of the control elements. A mission adaptive wing system chronology is used to illustrate and assess the reliability and dependability of the servoactuator system during 1524 hours of ground tests and 145 hours of flight testing.

CCSDS SM and C Mission Operations Interoperability Prototype

NASA Technical Reports Server (NTRS)

Lucord, Steven A.

2010-01-01

This slide presentation reviews the prototype of the Spacecraft Monitor and Control (SM&C) Operations for interoperability among other space agencies. This particular prototype uses the German Space Agency (DLR) to test the ideas for interagency coordination.

The role of smart systems in rendezvous, close proximity operations and docking maneuvers

NASA Astrophysics Data System (ADS)

Szatkowski, Gerard P.

Various missions scenarios (Space Station logistics, LEO and GEO services, and SEI operation) will involve flexibility in mission management. This means operations will be one or a combination of the following: autonomous, supervised autonomous, and machine aided manual control. Smart Systems will likely play a significant role in making these missions successful from a safety/reliability perspective and less costly from an operations perspective. This does not imply that Smart Systems need to be super sophisticated. On the contrary, Smart Systems have been described as automated intelligence that if a person had done it wrong, it would be considered stupid. The first part of this paper will describe the types of Smart System techniques involved in AR and CC, their specifications, duties, and interactions. Next will be a discussion of the work performed under the auspice of the ALS Program to further Expert Systems applications imbedded in the control process, NASA/JSC CRAD, and other related IRAD projects. This will include issues pertaining to the following: integration, speed, knowledge encapsulation, and cooperative systems. Finally, a brief description will be offered to outline the major obstacles for the acceptance of Smart Systems in critical applications.

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.

The LISA Pathfinder Mission: Sub-picometer Interferometry in Space

NASA Astrophysics Data System (ADS)

Slutsky, Jacob; LISA Pathfinder Collaboration

2018-01-01

The European Space Agency’s LISA Pathfinder was a mission built to demonstrate the technologies essential to implement a space-based gravitational wave observatory sensitive in the milli-Hertz frequency band. ESA recently selected the LISA mission as such a future observatory, scheduled to launch in the early 2030s. LISA Pathfinder launched in late 2015 and concluded its final extended mission in July 2017, during which time it placed the two test masses into free fall and successfully measured the relative acceleration between them to a sensitivity that validates a number of critical technologies for LISA. These include drag-free control of the test masses, low noise microNewton thrusters to control the spacecraft, and sub-picometer-level laser metrology in space. The mission also served as a sensitive probe of the environmenal conditions in which LISA will operate. This poster summarizes the recent analysis results, with an eye towards the implications for the LISA 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.

Strengthening the Federal Emergency Management Agency's disaster response capabilities.

PubMed

Cannon, Glenn M

2008-04-01

The Federal Emergency Management Agency's (FEMA) Disaster Operations Directorate provides the core federal response capability to save lives and to protect property in US communities that have been overwhelmed by the impact of a major disaster or emergency. The directorate executes its mission through three main programme areas: operational direction, command and control; operational teams; and operational planning. Based on lessons learned from years of disaster response experience, FEMA is now taking a more proactive and collaborative approach with its partners. This paper discusses how FEMA is placing a greater emphasis on response operations and strengthening capabilities across the full range of operational and support missions by comprehensively revamping its disaster operations model; enhancing its headquarters and regional operations centres; enhancing its headquarters and regional operational planning capabilities; and addressing catastrophic disaster planning and related critical preparedness issues.

Mission activities planning for a Hermes mission by means of AI-technology

NASA Technical Reports Server (NTRS)

Pape, U.; Hajen, G.; Schielow, N.; Mitschdoerfer, P.; Allard, F.

1993-01-01

Mission Activities Planning is a complex task to be performed by mission control centers. AI technology can offer attractive solutions to the planning problem. This paper presents the use of a new AI-based Mission Planning System for crew activity planning. Based on a HERMES servicing mission to the COLUMBUS Man Tended Free Flyer (MTFF) with complex time and resource constraints, approximately 2000 activities with 50 different resources have been generated, processed, and planned with parametric variation of operationally sensitive parameters. The architecture, as well as the performance of the mission planning system, is discussed. An outlook to future planning scenarios, the requirements, and how a system like MARS can fulfill those requirements is given.

NASA Officials in MCC to decide whether to land Apollo 16 or cancel landing

NASA Technical Reports Server (NTRS)

1972-01-01

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. Holcolmb (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.

Around Marshall

NASA Image and Video Library

1982-01-27

The primary payload for Space Shuttle Mission STS-42, launched January 22, 1992, was the International Microgravity Laboratory-1 (IML-1), a pressurized manned Spacelab module. The goal of IML-1 was to explore in depth the complex effects of weightlessness of living organisms and materials processing. Around-the-clock research was performed on the human nervous system's adaptation to low gravity and effects of microgravity on other life forms such as shrimp eggs, lentil seedlings, fruit fly eggs, and bacteria. Materials processing experiments were also conducted, including crystal growth from a variety of substances such as enzymes, mercury iodide, and a virus. 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. Featured is the Critical Point Facility (CPF) team in the SL POCC during the IML-1 mission.

Spacelab

NASA Image and Video Library

1992-01-28

The primary payload for Space Shuttle Mission STS-42, launched January 22, 1992, was the International Microgravity Laboratory-1 (IML-1), a pressurized manned Spacelab module. The goal of IML-1 was to explore in depth the complex effects of weightlessness of living organisms and materials processing. Around-the-clock research was performed on the human nervous system's adaptation to low gravity and effects of microgravity on other life forms such as shrimp eggs, lentil seedlings, fruit fly eggs, and bacteria. Materials processing experiments were also conducted, including crystal growth from a variety of substances such as enzymes, mercury iodide, and a virus. 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. Featured is the Crystal Growth team in the SL POCC during STS-42, IML-1 mission.

Around Marshall

NASA Image and Video Library

1992-01-27

The primary payload for Space Shuttle Mission STS-42, launched January 22, 1992, was the International Microgravity Laboratory-1 (IML-1), a pressurized manned Spacelab module. The goal of IML-1 was to explore in depth the complex effects of weightlessness of living organisms and materials processing. Around-the-clock research was performed on the human nervous system's adaptation to low gravity and effects of microgravity on other life forms such as shrimp eggs, lentil seedlings, fruit fly eggs, and bacteria. Materials processing experiments were also conducted, including crystal growth from a variety of substances such as enzymes, mercury iodide, and a virus. 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. Featured activities are of the Mental Workload and Performance Experiment (MWPE) team in the SL POCC during the IML-1 mission.

Around Marshall

NASA Image and Video Library

1992-01-28

The primary payload for Space Shuttle Mission STS-42, launched January 22, 1992, was the International Microgravity Laboratory-1 (IML-1), a pressurized manned Spacelab module. The goal of IML-1 was to explore in depth the complex effects of weightlessness of living organisms and materials processing. Around-the-clock research was performed on the human nervous system's adaptation to low gravity and effects of microgravity on other life forms such as shrimp eggs, lentil seedlings, fruit fly eggs, and bacteria. Materials processing experiments were also conducted, including crystal growth from a variety of substances such as enzymes, mercury iodide, and a virus. 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. Featured is the Vapor Crystal Growth System (VCGS) team in SL POCC), during STS-42, IML-1 mission.

Around Marshall

NASA Image and Video Library

1992-01-28

The primary payload for Space Shuttle Mission STS-42, launched January 22, 1992, was the International Microgravity Laboratory-1 (IML-1), a pressurized manned Spacelab module. The goal of IML-1 was to explore in depth the complex effects of weightlessness of living organisms and materials processing. Around-the-clock research was performed on the human nervous system's adaptation to low gravity and effects of microgravity on other life forms such as shrimp eggs, lentil seedlings, fruit fly eggs, and bacteria. Materials processing experiments were also conducted, including crystal growth from a variety of substances such as enzymes, mercury iodide, and a virus. 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. Featured is the Mental Workload and Performance Experiment (MWPE) team in the SL POCC) during STS-42, IML-1 mission.

Spacelab

NASA Image and Video Library

1992-01-28

The primary payload for Space Shuttle Mission STS-42, launched January 22, 1992, was the International Microgravity Laboratory-1 (IML-1), a pressurized manned Spacelab module. The goal of IML-1 was to explore in depth the complex effects of weightlessness of living organisms and materials processing. Around-the-clock research was performed on the human nervous system's adaptation to low gravity and effects of microgravity on other life forms such as shrimp eggs, lentil seedlings, fruit fly eggs, and bacteria. Materials processing experiments were also conducted, including crystal growth from a variety of substances such as enzymes, mercury iodide, and a virus. 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. Featured is the Critical Point Facility (CPE) group in the SL POCC during STS-42, IML-1 mission.

Around Marshall

NASA Image and Video Library

1992-01-28

The primary payload for Space Shuttle Mission STS-42, launched January 22, 1992, was the International Microgravity Laboratory-1 (IML-1), a pressurized manned Spacelab module. The goal of IML-1 was to explore in depth the complex effects of weightlessness of living organisms and materials processing. Around-the-clock research was performed on the human nervous system's adaptation to low gravity and effects of microgravity on other life forms such as shrimp eggs, lentil seedlings, fruit fly eggs, and bacteria. Materials processing experiments were also conducted, including crystal growth from a variety of substances such as enzymes, mercury iodide, and a virus. 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. Featured are activities in the SL POCC during STS-42, IML-1 mission.

Human-Centered Automation: The View from Earth Versus the View from Mars

NASA Technical Reports Server (NTRS)

Massimino, Michael J.; Smith, Philip J.; Stilwell, Donald J.; Mitchell, Christine M.; Thurman, David A.; Malin, Jane T.; Jones, Patricia M.

1999-01-01

This panel addresses the topic of human-centered automation in, however, a very different context-manned missions to deep space in which predominantly autonomous systems must control the crew's life-support systems most of the time. The Mars spacecraft and its inhabitants are totally dependent on the proper operation of thousands of control loops and pieces of equipment to maintain the delicate, unbuffered homeostasis of their remote existence. Mission success hangs on a thread that depends on a successful partnership, or symbiosis. between crew and machines, which exceeds anything ever required of ground systems. The need for a new approach to human-centered automation is not a "frill" in future Mars mission, but rather a sine qua non of survival. Thus the issue is design: Can we design systems intended to operate in a predominantly autonomous mode. without a human backup, that are sufficiently safe such that human travel into deep space is possible?

Lessons Learned from the Hubble Space Telescope (HST) Contamination Control Program

NASA Technical Reports Server (NTRS)

Hansen, Patricia A.; Townsend, Jacqueline A.; Hedgeland, Randy J.

2004-01-01

Over the past two decades, the Hubble Space Telescope (HST) Contamination Control Program has evolved from a ground-based integration program to a space-based science-sustaining program. The contamination controls from the new-generation Scientific Instruments and Orbital Replacement Units were incorporated into the HST Contamination Control Program to maintain scientific capability over the life of the telescope. Long-term on-orbit scientific data has shown that these contamination controls implemented for the instruments, Servicing Mission activities (Orbiter, Astronauts, and mission), and on-orbit operations successfully protected the HST &om contamination and the instruments from self-contamination.

Lessons Learned from the Hubble Space Telescope (HST) Contamination Control Program

NASA Technical Reports Server (NTRS)

Hansen, Patricia A.; Townsend, Jacqueline A.; Hedgeland, Randy J.

2004-01-01

Over the past two decades, the Hubble Space Telescope (HST) Contamination Control Program has evolved from a ground-based integration program to a space-based science-sustaining program. The contamination controls from the new-generation Scientific Instruments and Orbital Replacement Units were incorporated into the HST Contamination Control Program to maintain scientific capability over the life of the telescope. Long-term on-orbit scientific data has shown that these contamination controls implemented for the instruments, Servicing Mission activities (Orbiter, Astronauts, and mission), and on-orbit operations successfully protected the HST from contamination and the instruments from self-contamination.

Simulation Based Studies of Low Latency Teleoperations for NASA Exploration Missions

NASA Technical Reports Server (NTRS)

Gernhardt, Michael L.; Crues, Edwin Z.; Bielski, Paul; Dexter, Dan; Litaker, Harry L.; Chappell, Steven P.; Beaton, Kara H.; Bekdash, Omar S.

2017-01-01

Human exploration of Mars will involve both crewed and robotic systems. Many mission concepts involve the deployment and assembly of mission support assets prior to crew arrival on the surface. Some of these deployment and assembly activities will be performed autonomously while others will be performed using teleoperations. However, significant communications latencies between the Earth and Mars make teleoperations challenging. Alternatively, low latency teleoperations are possible from locations in Mars orbit like Mars' moons Phobos and Deimos. To explore these latency opportunities, NASA is conducting a series of studies to investigate the effects of latency on telerobotic deployment and assembly activities. These studies are being conducted in laboratory environments at NASA's Johnson Space Center (JSC), the Human Exploration Research Analog (HERA) at JSC and the NASA Extreme Environment Mission Operations (NEEMO) underwater habitat off the coast of Florida. The studies involve two human-in-the-loop interactive simulations developed by the NASA Exploration Systems Simulations (NExSyS) team at JSC. The first simulation investigates manipulation related activities while the second simulation investigates mobility related activities. The first simulation provides a simple real-time operator interface with displays and controls for a simulated 6 degree of freedom end effector. The initial version of the simulation uses a simple control mode to decouple the robotic kinematic constraints and a communications delay to model latency effects. This provides the basis for early testing with more detailed manipulation simulations planned for the future. Subjects are tested using five operating latencies that represent teleoperation conditions from local surface operations to orbital operations at Phobos, Deimos and ultimately high Martian orbit. Subject performance is measured and correlated with three distance-to-target zones of interest. Each zone represents a target distance ranging from beyond 10m in Zone 1, through 1 cm to contact in Zone 5 with a step size factor of 10. Collected data consists of both objective simulation data (time, distance, hand controller inputs, velocity) and subjective questionnaire data. The second simulation provides a simple real-time operator interface with displays and control of a simulated surface rover. The rover traverses a synthetic Mars-like terrain and must be maneuvered to avoid obstacles while progressing to its destination. Like the manipulator simulation, subjects are tested using five operating latencies that represent teleoperation conditions from local surface operations to orbital operations at Phobos, Deimos and ultimately high Martian orbit. The rover is also operated at three different traverse speeds to assess the correlation between latency and speed. Collected data consisted of both objective simulation data (time, distance, hand controller inputs, braking) and subjective questionnaire data. These studies are exploring relationships between task complexity, operating speeds, operator efficiencies, and communications latencies for low latency teleoperations in support of human planetary exploration. This paper presents early results from these studies along with the current observations and conclusions. These and planned future studies will help to inform NASA on the potential for low latency teleoperations to support human exploration of Mars and inform the design of robotic systems and exploration missions.

T-38 A- AIRCRAFT (NASA 924)

NASA Image and Video Library

1983-12-07

S82-33032 (30 June 1982) --- This scene shows activity at the spacecraft communicator and flight activities officer consoles in the mission operations control room (MOCR) in the Johnson Space Center?s mission control center (MCC). Astronaut Brewster H. Shaw Jr., right, Astronaut Roy D. Bridges Jr. and Marianne J. Dyson are pictured during STS-4?s Day 4 activity. Shaw and Bridges are spacecraft communicators and Dyson is a flight activities officer on the entry team.

ISS Operations Cost Reductions Through Automation of Real-Time Planning Tasks

NASA Technical Reports Server (NTRS)

Hall, Timothy A.

2011-01-01

In 2008 the Johnson Space Center s Mission Operations Directorate (MOD) management team challenged their organization to find ways to reduce the costs of International Space station (ISS) console operations in the Mission Control Center (MCC). Each MOD organization was asked to identify projects that would help them attain a goal of a 30% reduction in operating costs by 2012. The MOD Operations and Planning organization responded to this challenge by launching several software automation projects that would allow them to greatly improve ISS console operations and reduce staffing and operating costs. These projects to date have allowed the MOD Operations organization to remove one full time (7 x 24 x 365) ISS console position in 2010; with the plan of eliminating two full time ISS console support positions by 2012. This will account for an overall 10 EP reduction in staffing for the Operations and Planning organization. These automation projects focused on utilizing software to automate many administrative and often repetitive tasks involved with processing ISS planning and daily operations information. This information was exchanged between the ground flight control teams in Houston and around the globe, as well as with the ISS astronaut crew. These tasks ranged from managing mission plan changes from around the globe, to uploading and downloading information to and from the ISS crew, to even more complex tasks that required multiple decision points to process the data, track approvals and deliver it to the correct recipient across network and security boundaries. The software solutions leveraged several different technologies including customized web applications and implementation of industry standard web services architecture between several planning tools; as well as a engaging a previously research level technology (TRL 2-3) developed by Ames Research Center (ARC) that utilized an intelligent agent based system to manage and automate file traffic flow, archiving f data, and generating console logs. This technology called OCAMS (OCA (Orbital Communication System) Management System), is now considered TRL level 9 and is in daily use in the Mission Control Center in support of ISS operations. These solutions have not only allowed for improved efficiency on console; but since many of the previously manual data transfers are now automated, many of the human error prone steps have been removed, and the quality of the planning products has improved tremendously. This has also allowed our Planning Flight Controllers more time to focus on the abstract areas of the job, (like the complexities of planning a mission for 6 international crew members with a global planning team), instead of being burdened with the administrative tasks that took significant time each console shift to process. The resulting automation solutions have allowed the Operations and Planning organization to realize significant cost savings for the ISS program through 2020 and many of these solutions could be a viable

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.

Supervising and Controlling Unmanned Systems: A Multi-Phase Study with Subject Matter Experts

PubMed Central

Porat, Talya; Oron-Gilad, Tal; Rottem-Hovev, Michal; Silbiger, Jacob

2016-01-01

Proliferation in the use of Unmanned Aerial Systems (UASs) in civil and military operations has presented a multitude of human factors challenges; from how to bridge the gap between demand and availability of trained operators, to how to organize and present data in meaningful ways. Utilizing the Design Research Methodology (DRM), a series of closely related studies with subject matter experts (SMEs) demonstrate how the focus of research gradually shifted from “how many systems can a single operator control” to “how to distribute missions among operators and systems in an efficient way”. The first set of studies aimed to explore the modal number, i.e., how many systems can a single operator supervise and control. It was found that an experienced operator can supervise up to 15 UASs efficiently using moderate levels of automation, and control (mission and payload management) up to three systems. Once this limit was reached, a single operator's performance was compared to a team controlling the same number of systems. In general, teams led to better performances. Hence, shifting design efforts toward developing tools that support teamwork environments of multiple operators with multiple UASs (MOMU). In MOMU settings, when the tasks are similar or when areas of interest overlap, one operator seems to have an advantage over a team who needs to collaborate and coordinate. However, in all other cases, a team was advantageous over a single operator. Other findings and implications, as well as future directions for research are discussed. PMID:27252662

In-Space Propellant Production Using Water

NASA Technical Reports Server (NTRS)

Notardonato, William; Johnson, Wesley; Swanger, Adam; McQuade, William

2012-01-01

A new era of space exploration is being planned. Manned exploration architectures under consideration require the long term storage of cryogenic propellants in space, and larger science mission directorate payloads can be delivered using cryogenic propulsion stages. Several architecture studies have shown that in-space cryogenic propulsion depots offer benefits including lower launch costs, smaller launch vehicles, and enhanced mission flexibility. NASA is currently planning a Cryogenic Propellant Storage and Transfer (CPST) technology demonstration mission that will use existing technology to demonstrate long duration storage, acquisition, mass gauging, and transfer of liquid hydrogen in low Earth orbit. This mission will demonstrate key technologies, but the CPST architecture is not designed for optimal mission operations for a true propellant depot. This paper will consider cryogenic propellant depots that are designed for operability. The operability principles considered are reusability, commonality, designing for the unique environment of space, and use of active control systems, both thermal and fluid. After considering these operability principles, a proposed depot architecture will be presented that uses water launch and on orbit electrolysis and liquefaction. This could serve as the first true space factory. Critical technologies needed for this depot architecture, including on orbit electrolysis, zero-g liquefaction and storage, rendezvous and docking, and propellant transfer, will be discussed and a developmental path forward will be presented. Finally, use of the depot to support the NASA Science Mission Directorate exploration goals will be presented.