Space flight operations
Space flight operations - launch site, deep space instrumentation facility, operations complex, launch site, communications facility, and checkout facility
SEARCH · Search NASA
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.
Space flight operations - launch site, deep space instrumentation facility, operations complex, launch site, communications facility, and checkout facility
Space science - launching and space flight operations
In space flight operations rapid understanding of the state of the space vehicle is essential. Representation of knowledge depicting space vehicle status in a dynamic environment presents a difficult challenge. The NASA Jet Propulsion Laboratory has pursued areas of technology associated with the advancement of spacecraft operations environment. This has led to the development of several advanced mission systems which incorporate enhanced graphics capabilities. These systems include: (1) Spacecraft Health Automated Reasoning Prototype (SHARP); (2) Spacecraft Monitoring Environment (SME); (3) Electrical Power Data Monitor (EPDM); (4) Generic Payload Operations Control Center (GPOCC); and (5) Telemetry System Monitor Prototype (TSM). Knowledge representation in these systems provides a direct representation of the intrinsic images associated with the instrument and satellite telemetry and telecommunications systems. The man-machine interface includes easily interpreted contextual graphic displays. These interactive video displays contain multiple display screens with pop-up windows and intelligent, high resolution graphics linked through context and mouse-sensitive icons and text.
Surveyor Mission G flight operations from transit phase to second lunar day
The Space Flight Operations Center is a networked system of workstation-class computers that will provide ground support for NASA's next generation of deep-space missions. The author recounts the development of the SFOC system security policy and discusses the various management and technology issues involved. Particular attention is given to risk assessment, security plan development, security implications of design requirements, automatic safeguards, and procedural safeguards.
DSN command system operation from Space Flight Operations Facility supporting Mariner Mars 1971 mission
Space flight operations plan for Mariner Mars flyby mission
Communications are a critical link in space flight operations. Specific communications phraseology and techniques have been developed to allow rapid and clear transfer of information. Communications will be clear and brief through the use of procedural words and phrases. Communications protocols standardize the required information transferred. The voicing of letters and numbers is discussed. The protocols used in air-to-ground communications are given. A glossary of communications terminology is presented in the appendix.
A generic decommutation capability has been created as part of the Space Flight Operation Center's goal of developing a multimission telemetry system. Generic decommutation involves separating the algorithmic description for extracting data from the actual implementation of decommutation. This was done by creating a decommutation map language, which allows mission designers to describe decommutation algorithms without the restrictions imposed by a standard programming language. A decommutation map compiler converts this description into C code, which is then linked with a decommutation library to provide an executable decommutation program. So far, this approach has been used successfully to decommutate several different types of data.
This paper is a retrospective look at the Space Flight Operations Center Project; a large, complex, multimission ground data system which is currently under development at the Jet Propulsion Laboratory (JPL), Pasadena. The Project was established in February 1984 and will be completed in April 1992 when the Magellan, Voyager, Ulysses, Galileo and Mars Observer Projects will be fully supported. The first phase of this project covers the development of a subset of multimission Baseline subsystems, the development of the mission-specific adaptations to this Baseline set for the Magellan Project, the development of a Magellan-specific high rate processor together with the delivery of these subsystems to operations. This first phase became operational in January 1989 in readiness for the Magellan launch in May 1989.
The existing Mission Control and Computer Center at JPL will be replaced by the Space Flight Operations Center (SFOC). One part of the SFOC is the LAN-based distribution system. The purpose of the LAN is to distribute the processed data among the various elements of the SFOC. The SFOC LAN will provide a robust subsystem that will support the Magellan launch configuration and future project adaptation. Its capabilities include (1) a proven cable medium as the backbone for the entire network; (2) hardware components that are reliable, varied, and follow OSI standards; (3) accurate and detailed documentation for fault isolation and future expansion; and (4) proven monitoring and maintenance tools.
Word processing was one of the earliest uses for small workstations, but we quickly learned that desktop computers were far more than e-typewriters. Similarly, "Web 2.0" capabilities, particularly advanced search engines, chats, wikis, blogs, social networking, and the like, offer tools that could significantly improve our efficiency at managing the avalanche of information and decisions needed to operate space vehicles in realtime. However, could does not necessarily equal should. We must wield two-edged swords carefully to avoid stabbing ourselves. This paper examines some Web 2.0 tools, with an emphasis on social media, and suggests which ones might be useful or harmful in real-time space operations co rnotl environments, based on the author s experience as a Payload Crew Communicator (PAYCOM) at Marshall Space Flight Center s (MSFC) Payload Operations Integration Center (POIC) for the International Space Station (ISS) and on discussions with other space flight operations control organizations and centers. There is also some discussion of an offering or two that may come from beyond the current cyber-horizon.
This paper describes the Magellan spacecraft designed to collect information from the surface of Venus while orbiting this planet. Special attention is given to the attitude and articulation control of the spacecraft; the command, data, and data storage; the thermal control; and instrumentation. The operations at Venus, which will include Venus orbit insertion and in-orbit checkout and to both routine and nonroutine (at a period when Venus will be in superior conjunction, and the solar plasma will drive Magellan's telecommunications signal-to-noise ratio to a very high value) mapping of the surface, are discussed. Also discussed are operations on earth, carried out by the new Space Flight Operations Control Center.
The topics are covered in view graph form and include the following: (1) major elements of deep space flight programs; (2) development schedule; (3) primary design goals; (4) Space Flight Operations Center (SFOC) data systems architecture; (5) technical guidelines; (6) SFOC data system functional architecture; (7) typical SFOC node; (8) SFOC components; (9) SFOC software categories; (10) planned subsystem core diagram for Mars observer; (11) SFOC use of public domain/3rd party software; (12) SFOC hardware; (13) SFOC target six mission configuration; and (14) SFOC development status and plans.
This paper presents an overview of the Jet Propulsion Laboratory's (JPL) plan for developing a multi-mission facility called the Space Flight Operations Center (SFOC). The SFOC development is a five-year project with the objective of developing and adapting up-to-date computing, networking and data management technology to meet the future data processing and data management requirements for JPL's flight project mission operations. Presented are the project background, basic goals and objectives, design concept and project implementation approach.
Under contract to the National Aeronautics and Space Administration, the Jet Propulsion Laboratory (JPL) of the California Institute of Technology manages and operates the ground facilities required to support unmanned spacecraft in missions to the moon, the planets, and beyond. A worldwide network of tracking stations, known as the Deep Space Network (DSN), was established to communicate with spacecraft. The Mission Control and Computing Center at JPL houses the mission control personnel and the computer facilities that command and control spacecraft in flight. Communications between the MCCC and the tracking stations, as well as communications among the stations, are the responsibility of the DSN Ground Communications Facility, which connects all parts of the ground system with telephone, teletype, and high-speed data lines. The operation of the ground system is outlined, and the various missions which were successfully supported are described.
The Mission Operations Directorate (MOD) at the Johnson Space Center (JSC) has put in place a Model Based Systems Engineering (MBSE) technological framework for the development and execution of the Flight Production Process (FPP). This framework has provided much added value and return on investment to date. This paper describes a vision for a model based Decision Support System (DSS) for the development and execution of the FPP and its design and development process. The envisioned system extends the existing MBSE methodology and technological framework which is currently in use. The MBSE technological framework currently in place enables the systematic collection and integration of data required for building an FPP model for a diverse set of missions. This framework includes the technology, people and processes required for rapid development of architectural artifacts. It is used to build a feasible FPP model for the first flight of spacecraft and for recurrent flights throughout the life of the program. This model greatly enhances our ability to effectively engage with a new customer. It provides a preliminary work breakdown structure, data flow information and a master schedule based on its existing knowledge base. These artifacts are then refined and iterated upon with the customer for the development of a robust end-to-end, high-level integrated master schedule and its associated dependencies. The vision is to enhance this framework to enable its application for uncertainty management, decision support and optimization of the design and execution of the FPP by the program. Furthermore, this enhanced framework will enable the agile response and redesign of the FPP based on observed system behavior. The discrepancy of the anticipated system behavior and the observed behavior may be due to the processing of tasks internally, or due to external factors such as changes in program requirements or conditions associated with other organizations that are outside of MOD. The paper provides a roadmap for the three increments of this vision. These increments include (1) hardware and software system components and interfaces with the NASA ground system, (2) uncertainty management and (3) re-planning and automated execution. Each of these increments provide value independently; but some may also enable building of a subsequent increment.
The Mission Operations Directorate (MOD) at the Johnson Space Center (JSC) has put in place a Model Based Systems Engineering (MBSE) technological framework for the development and execution of the Flight Production Process (FPP). This framework has provided much added value and return on investment to date. This paper describes a vision for a model based Decision Support System (DSS) for the development and execution of the FPP and its design and development process. The envisioned system extends the existing MBSE methodology and technological framework which is currently in use. The MBSE technological framework currently in place enables the systematic collection and integration of data required for building an FPP model for a diverse set of missions. This framework includes the technology, people and processes required for rapid development of architectural artifacts. It is used to build a feasible FPP model for the first flight of spacecraft and for recurrent flights throughout the life of the program. This model greatly enhances our ability to effectively engage with a new customer. It provides a preliminary work breakdown structure, data flow information and a master schedule based on its existing knowledge base. These artifacts are then refined and iterated upon with the customer for the development of a robust end-to-end, high-level integrated master schedule and its associated dependencies. The vision is to enhance this framework to enable its application for uncertainty management, decision support and optimization of the design and execution of the FPP by the program. Furthermore, this enhanced framework will enable the agile response and redesign of the FPP based on observed system behavior. The differences between the anticipated system behavior and the observed behavior may be due to the processing of tasks internally, or due to external factors such as changes in program requirements or conditions associated with other organizations that are outside of MOD. The paper provides a roadmap for the four increments of this vision. These increments include (1) the existing capabilities (2) hardware and software system components and interfaces with the NASA ground system, (3) uncertainty management and (4) re-planning and automated execution. Each of these increments provides value independently; but some may also enable building of a subsequent increment.