Space Operations at NASA’s Marshall Space Flight Center
Explore the source record for details and available documents.
Robert Mason Hall↗
SEARCH · Search NASA
Results for “Space Operations Center”
Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.
Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.
The Right Stuff: A Look Back at Three Decades of Flight Controller Training for Space Shuttle Mission Operations
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.
Dittemore, Gary D.↗
The Final Count Down: A Review of Three Decades of Flight Controller Training Methods for Space Shuttle Mission Operations
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.
Dittermore, Gary↗
Standards-and Component-Based Mission Operations Architecture at NASA's Goddard Space Flight Center
NASA Goddard Space Flight Center (GSFC) manages many of NASA s earth and space science satellite missions. A wide variety of commercial products and GSFC-developed software components are typically integrated into a unique system configuration for each mission. Independent development of the many mission operations center systems has led to systems that are expensive to integrate, difficult to infuse with new capabilities developed for other programs, and cumbersome to maintain. This traditional approach becomes even more problematic as NASA moves towards satellite constellations, new operations concepts, and even further budgets reductions. The GSFC Mission Services Evolution Center (GMSEC) is creating a new architecture for future missions at GSFC. Instead of selecting the best-in-class components and creating a standard control center system, GMSEC is developing component interface standards so that multiple products can plug-and-play into the configuration. Missions can then select the best components based on the merits of the product and not simply based on recent integration history at NASA. The GMSEC system utilizes a publish/subscribe information bus and standard XML-based key message interfaces. Functional components can either match directly to the interface standard, or adapters can be developed to match the product's interface to the GMSEC standard with out impacting the source product. Applications Program Interfaces (API's) are being developed to isolate the underlying middleware from the applications software and to allow the middleware product to be switched if necessary. Interface Control Documents (ICDs) between each pair of communicating components is replaced by a single message/API specification document. New applications must simply match to the information bus standards and need not worry about all of the other applications in the system. For legacy software, adapters can be developed to facilitate communications between the application and the information bus. As the approach has matured, it has become apparent that it can provide innovative solutions to some of the multi-satellite challenges facing GSFC.
Smith, Danford↗
Console Log Keeping Made Easier - Tools and Techniques for Improving Quality of Flight Controller Activity Logs
At the Marshall Space Flight Center's (MSFC) Payload Operations Integration Center (POIC) for International Space Station (ISS), each flight controller maintains detailed logs of activities and communications at their console position. These logs are critical for accurately controlling flight in real-time as well as providing a historical record and troubleshooting tool. This paper describes logging methods and electronic formats used at the POIC and provides food for thought on their strengths and limitations, plus proposes some innovative extensions. It also describes an inexpensive PC-based scheme for capturing and/or transcribing audio clips from communications consoles. Flight control activity (e.g. interpreting computer displays, entering data/issuing electronic commands, and communicating with others) can become extremely intense. It's essential to document it well, but the effort to do so may conflict with actual activity. This can be more than just annoying, as what's in the logs (or just as importantly not in them) often feeds back directly into the quality of future operations, whether short-term or long-term. In earlier programs, such as Spacelab, log keeping was done on paper, often using position-specific shorthand, and the other reader was at the mercy of the writer's penmanship. Today, user-friendly software solves the legibility problem and can automate date/time entry, but some content may take longer to finish due to individual typing speed and less use of symbols. File layout can be used to great advantage in making types of information easy to find, and creating searchable master logs for a given position is very easy and a real lifesaver in reconstructing events or researching a given topic. We'll examine log formats from several console position, and the types of information that are included and (just as importantly) excluded. We'll also look at when a summary or synopsis is effective, and when extensive detail is needed.
Scott, David W.↗
The Imaging X-Ray Polarimetry Explorer (IXPE): Overview
Mission background: Imaging x-ray polarimetry in 2–8 kiloelectronvolt band; NASA Astrophysics Small Explorer (SMEX) selected in 2017 January. Orbit: Pegasus-XL (airborne) launch in 2021, from Kwajalein; Equatorial circular orbit at greater than or approximately equal to 540 kilometers (620 kilometers, goal) altitude. Flight system: Spacecraft, payload structure, and integration by Ball Aerospace - Deployable payload boom from Orbital-ATK, under contract to Ball; X-ray Mirror Module Assemblies by NASA/MSFC; X-ray (polarization-sensitive) Instruments by IAPS/INAF (Istituto di Astrofisica e Planetologia Spaziali / Istituto Nazionale di Astrofisica) and INFN (Istituto Nazionale di Fisica Nucleare). Ground system: ASI (Agenzia Spaziale Italiana) Malindi ground station, with Singapore backup; Mission Operations Center at LASP (Laboratory for Atmospheric and Space Physics, University of Colorado); Science Operations Center at NASA/MSFC; Data archive at HEASARC (High Energy Astrophysics Science Archive Research Center), (NASA/GSFC), mirror at ASI Data Center. Science: Active galactic nuclei; Microquasars; Radio pulsars and pulsar wind nebulae; Supernova remnants; Magnetars; Accreting x-ray pulsars.
X-ray polarimetry space missio↗
Launch and Landing Effects Ground Operations (LLEGO) Model
LLEGO is a model for understanding recurring launch and landing operations costs at Kennedy Space Center for human space flight. Launch and landing operations are often referred to as ground processing, or ground operations. Currently, this function is specific to the ground operations for the Space Shuttle Space Transportation System within the Space Shuttle Program. The Constellation system to follow the Space Shuttle consists of the crewed Orion spacecraft atop an Ares I launch vehicle and the uncrewed Ares V cargo launch vehicle. The Constellation flight and ground systems build upon many elements of the existing Shuttle flight and ground hardware, as well as upon existing organizations and processes. In turn, the LLEGO model builds upon past ground operations research, modeling, data, and experience in estimating for future programs. Rather than to simply provide estimates, the LLEGO model s main purpose is to improve expenses by relating complex relationships among functions (ground operations contractor, subcontractors, civil service technical, center management, operations, etc.) to tangible drivers. Drivers include flight system complexity and reliability, as well as operations and supply chain management processes and technology. Together these factors define the operability and potential improvements for any future system, from the most direct to the least direct expenses.
Source record↗
Software Sharing Enables Smarter Content Management
In 2004, NASA established a technology partnership with Xerox Corporation to develop high-tech knowledge management systems while providing new tools and applications that support the Vision for Space Exploration. In return, NASA provides research and development assistance to Xerox to progress its product line. The first result of the technology partnership was a new system called the NX Knowledge Network (based on Xerox DocuShare CPX). Created specifically for NASA's purposes, this system combines Netmark-practical database content management software created by the Intelligent Systems Division of NASA's Ames Research Center-with complementary software from Xerox's global research centers and DocuShare. NX Knowledge Network was tested at the NASA Astrobiology Institute, and is widely used for document management at Ames, Langley Research Center, within the Mission Operations Directorate at Johnson Space Center, and at the Jet Propulsion Laboratory, for mission-related tasks.
Source record↗
Reinventing User Applications for Mission Control
In 2006, NASA Ames Research Center's (ARC) Intelligent Systems Division, and NASA Johnson Space Centers (JSC) Mission Operations Directorate (MOD) began a collaboration to move user applications for JSC's mission control center to a new software architecture, intended to replace the existing user applications being used for the Space Shuttle and the International Space Station. It must also carry NASA/JSC mission operations forward to the future, meeting the needs for NASA's exploration programs beyond low Earth orbit. Key requirements for the new architecture, called Mission Control Technologies (MCT) are that end users must be able to compose and build their own software displays without the need for programming, or direct support and approval from a platform services organization. Developers must be able to build MCT components using industry standard languages and tools. Each component of MCT must be interoperable with other components, regardless of what organization develops them. For platform service providers and MOD management, MCT must be cost effective, maintainable and evolvable. MCT software is built from components that are presented to users as composable user objects. A user object is an entity that represents a domain object such as a telemetry point, a command, a timeline, an activity, or a step in a procedure. User objects may be composed and reused, for example a telemetry point may be used in a traditional monitoring display, and that same telemetry user object may be composed into a procedure step. In either display, that same telemetry point may be shown in different views, such as a plot, an alpha numeric, or a meta-data view and those views may be changed live and in place. MCT presents users with a single unified user environment that contains all the objects required to perform applicable flight controller tasks, thus users do not have to use multiple applications, the traditional boundaries that exist between multiple heterogeneous applications disappear, leaving open the possibility of new operations concepts that are not constrained by the traditional applications paradigm.
Trimble, Jay Phillip↗
Experimental facilities for electric propulsion testing
Experimental facilities for electric propulsion testing at the University of Tennessee Space Institute, jointly operated by the Center for Advanced Space Propulsion, include a cryogenically cooled, computer-controlled, 9 ft diameter by 20 ft long vacuum chamber, capable of maintaining a baseline pressure of 10(exp -7) Torr, a 30 cm diameter ion thruster, and laser diagnostic and electrical diagnostic instrumentation. These facilities are described here in some detail, with emphasis on the measurement of ion thruster parameters such as neutral and ion densities, temperature, and velocity in the exhaust, as well as plasma potential and electron temperature.
Ruyten, Wilhelmus M.↗
Close-Call Action Log Form
"Close Call Action Log Form" ("CCALF") is the name of both a computer program and a Web-based service provided by the program for creating an enhanced database of close calls (in the colloquial sense of mishaps that were avoided by small margins) assigned to the Center Operations Directorate (COD) at Johnson Space Center. CCALF provides a single facility for on-line collaborative review of close calls. Through CCALF, managers can delegate responses to employees. CCALF utilizes a pre-existing e-mail system to notify managers that there are close calls to review, but eliminates the need for the prior practices of passing multiple e-mail messages around the COD, then collecting and consolidating them into final responses: CCALF now collects comments from all responders for incorporation into reports that it generates. Also, whereas it was previously necessary to manually calculate metrics (e.g., numbers of maintenance-work orders necessitated by close calls) for inclusion in the reports, CCALF now computes the metrics, summarizes them, and displays them in graphical form. The reports and all pertinent information used to generate the reports are logged, tracked, and retained by CCALF for historical purposes.
Spuler, Linda M.↗
Immersive Simulations and Engineering Environment (iSEE): Increasing the Realism of Simulations
The Immersive Simulations and Engineering Environment (iSEE) lab at Kennedy Space Center has been operating with its current team since 2017. The lab provides National Aeronautics and Space Administration (NASA) with simulations that show the stress and strain that a strenuous task can cause on a body. Previously the lab was using software that was efficient in ergonomic analysis of a human body, but limited in creating a realistic simulation. To produce a more realistic simulation, the iSEE invested in new software that could potentially create an environment that could show the viewer a simulation that was closer to reality.
Hodge, Brianna↗
The Final Count Down: A Review of Three Decades of Flight Controller Training Methods for Space Shuttle Mission Operations
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.
Dittemore, Gary D.↗
Conducting Research on the International Space Station Using the EXPRESS Rack Facilities
Conducting Research on the International Space Station using the EXPRESS Rack Facilities. Sean W. Thompson and Robert E. Lake. NASA Marshall Space Flight Center, Huntsville, AL, USA. Eight "Expedite the Processing of Experiments to Space Station" (EXPRESS) Rack facilities are located within the International Space Station (ISS) laboratories to provide standard resources and interfaces for the simultaneous and independent operation of multiple experiments within each rack. Each EXPRESS Rack provides eight Middeck Locker Equivalent locations and two drawer locations for powered experiment equipment, also referred to as sub-rack payloads. Payload developers may provide their own structure to occupy the equivalent volume of one, two, or four lockers as a single unit. Resources provided for each location include power (28 Vdc, 0-500 W), command and data handling (Ethernet, RS-422, 5 Vdc discrete, +/- 5 Vdc analog), video (NTSC/RS 170A), and air cooling (0-200 W). Each rack also provides water cooling (500 W) for two locations, one vacuum exhaust interface, and one gaseous nitrogen interface. Standard interfacing cables and hoses are provided on-orbit. One laptop computer is provided with each rack to control the rack and to accommodate payload application software. Four of the racks are equipped with the Active Rack Isolation System to reduce vibration between the ISS and the rack. EXPRESS Racks are operated by the Payload Operations Integration Center at Marshall Space Flight Center and the sub-rack experiments are operated remotely by the investigating organization. Payload Integration Managers serve as a focal to assist organizations developing payloads for an EXPRESS Rack. NASA provides EXPRESS Rack simulator software for payload developers to checkout payload command and data handling at the development site before integrating the payload with the EXPRESS Functional Checkout Unit for an end-to-end test before flight. EXPRESS Racks began supporting investigations onboard ISS on April 24, 2001 and will continue through the life of the ISS.
Thompson, Sean W.↗
Application of statistical distribution theory to launch-on-time for space construction logistic support
The ability to launch-on-time and to send payloads into space has progressed dramatically since the days of the earliest missile and space programs. Causes for delay during launch, i.e., unplanned 'holds', are attributable to several sources: weather, range activities, vehicle conditions, human performance, etc. Recent developments in space program, particularly the need for highly reliable logistic support of space construction and the subsequent planned operation of space stations, large unmanned space structures, lunar and Mars bases, and the necessity of providing 'guaranteed' commercial launches have placed increased emphasis on understanding and mastering every aspect of launch vehicle operations. The Center of Space Construction has acquired historical launch vehicle data and is applying these data to the analysis of space launch vehicle logistic support of space construction. This analysis will include development of a better understanding of launch-on-time capability and simulation of required support systems for vehicle assembly and launch which are necessary to support national space program construction schedules. In this paper, the author presents actual launch data on unscheduled 'hold' distributions of various launch vehicles. The data have been supplied by industrial associate companies of the Center for Space Construction. The paper seeks to determine suitable probability models which describe these historical data and that can be used for several purposes such as: inputs to broader simulations of launch vehicle logistic space construction support processes and the determination of which launch operations sources cause the majority of the unscheduled 'holds', and hence to suggest changes which might improve launch-on-time. In particular, the paper investigates the ability of a compound distribution probability model to fit actual data, versus alternative models, and recommends the most productive avenues for future statistical work.
Morgenthaler, George W.↗
Lessons Learned on Implementing Fault Detection, Isolation, and Recovery (FDIR) in a Ground Launch Environment
This paper's main purpose is to detail issues and lessons learned regarding designing, integrating, and implementing Fault Detection Isolation and Recovery (FDIR) for Constellation Exploration Program (CxP) Ground Operations at Kennedy Space Center (KSC). Part of the0 overall implementation of National Aeronautics and Space Administration's (NASA's) CxP, FDIR is being implemented in three main components of the program (Ares, Orion, and Ground Operations/Processing). While not initially part of the design baseline for the CxP Ground Operations, NASA felt that FDIR is important enough to develop, that NASA's Exploration Systems Mission Directorate's (ESMD's) Exploration Technology Development Program (ETDP) initiated a task for it under their Integrated System Health Management (ISHM) research area. This task, referred to as the FDIIR project, is a multi-year multi-center effort. The primary purpose of the FDIR project is to develop a prototype and pathway upon which Fault Detection and Isolation (FDI) may be transitioned into the Ground Operations baseline. Currently, Qualtech Systems Inc (QSI) Commercial Off The Shelf (COTS) software products Testability Engineering and Maintenance System (TEAMS) Designer and TEAMS RDS/RT are being utilized in the implementation of FDI within the FDIR project. The TEAMS Designer COTS software product is being utilized to model the system with Functional Fault Models (FFMs). A limited set of systems in Ground Operations are being modeled by the FDIR project, and the entire Ares Launch Vehicle is being modeled under the Functional Fault Analysis (FFA) project at Marshall Space Flight Center (MSFC). Integration of the Ares FFMs and the Ground Processing FFMs is being done under the FDIR project also utilizing the TEAMS Designer COTS software product. One of the most significant challenges related to integration is to ensure that FFMs developed by different organizations can be integrated easily and without errors. Software Interface Control Documents (ICDs) for the FFMs and their usage will be addressed as the solution to this issue. In particular, the advantages and disadvantages of these ICDs across physically separate development groups will be delineated.
Ferrell, Bob A.↗
Re-Engineering the ISS Payload Operations Control Center During Increased Utilization and Critical Onboard Events
With an increase in utilization and hours of payload operations being executed onboard the International Space Station (ISS), upgrading the NASA Marshall Space Flight Center (MSFC) Huntsville Operations Support Center (HOSC) ISS Payload Control Area (PCA) was essential to gaining efficiencies and assurance of current and future payload health and science return. PCA houses the Payload Operations Integration Center (POIC) responsible for the execution of all NASA payloads onboard the ISS. POIC Flight Controllers are responsible for the operation of voice, stowage, command, telemetry, video, power, thermal, and environmental control in support of ISS science experiments. The methodologies and execution of the PCA refurbishment were planned and performed within a four-month period in order to assure uninterrupted operation of ISS payloads and minimal impacts to payload operations teams. To vacate the PCA, three additional HOSC control rooms were reconfigured to handle ISS real-time operations, Backup Control Center (BCC) to Mission Control in Houston, simulations, and testing functions. This involved coordination and cooperation from teams of ISS operations controllers, multiple engineering and design disciplines, management, and construction companies performing an array of activities simultaneously and in sync delivering a final product with no issues that impacted the schedule. For each console operator discipline, studies of Information Technology (IT) tools and equipment layouts, ergonomics, and lines of sight were performed. Infusing some of the latest IT into the project was an essential goal in ensuring future growth and success of the ISS payload science returns. Engineering evaluations led to a state of the art Video Wall implementation and more efficient ethernet cabling distribution providing the latest products and the best solution for the POIC. These engineering innovations led to cost savings for the project. Constraints involved in the management of the project included executing over 450 crew-hours of ISS real-time payload operations including a major onboard communications upgrade, SpaceX un-berth, a Soyuz launch, roll-out of ISS live video and interviews from the POIC, annual BCC certification and hurricane season, and ISS simulations and testing. Continuous ISS payload operations were possible during the PCA facility modifications with the reconfiguration of four control rooms and standup of two temporary control areas. Another major restriction to the project was an ongoing facility upgrade that included a NASA Headquarters mandated replacement of all electrical and mechanical systems and replacement of an external generator. These upgrades required a facility power outage during the PCA upgrades. The project also encompassed console layout designs and ordering, amenities selections and ordering, excessing of old equipment, moves, disposal of old IT equipment, camera installations, facility tour re-schedules, and contract justifications. These were just some of the tasks needed for a successful project. This paper describes the logistics and lessons learned in upgrading a control center capability in the middle of complex real-time operations. Combining the efficiencies of controller interaction and new technology infusion were prime drivers for this upgrade to handle the increased utilization of science research on ISS. The success of this project could not jeopardize the current operations while these facility upgrades occurred.
Dudley, Stephanie R. B.↗
The Next Generation of Ground Operations Command and Control; Scripting in C no. and Visual Basic
Scripting languages have become a common method for implementing command and control solutions in space ground operations. The Systems Test and Operations Language (STOL), the Huntsville Operations Support Center (HOSC) Scripting Language Processor (SLP), and the Spacecraft Control Language (SCL) offer script-commands that wrap tedious operations tasks into single calls. Since script-commands are interpreted, they also offer a certain amount of hands-on control that is highly valued in space ground operations. Although compiled programs seem to be unsuited for interactive user control and are more complex to develop, Marshall Space flight Center (MSFC) has developed a product called the Enhanced and Redesign Scripting (ERS) that makes use of the graphical and logical richness of a programming language while offering the hands-on and ease of control of a scripting language. ERS is currently used by the International Space Station (ISS) Payload Operations Integration Center (POIC) Cadre team members. ERS integrates spacecraft command mnemonics, telemetry measurements, and command and telemetry control procedures into a standard programming language, while making use of Microsoft's Visual Studio for developing Visual Basic (VB) or C# ground operations procedures. ERS also allows for script-style user control during procedure execution using a robust graphical user input and output feature. The availability of VB and C# programmers, and the richness of the languages and their development environment, has allowed ERS to lower our "script" development time and maintenance costs at the Marshall POIC.
Ritter, George↗