Search NASA⌕ Search

SEARCH · Search NASA

Results for “Mission Control”

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.

At least 217 records · Page 12
All sourcesNASA NTRSDOE OSTI
NASA NTRS2016

Designing the Next Generation of Human Spacecraft

Lunar Space Station Common Module: A new concept for a module for a lunar space station attempts to reduce the module's mass by abandoning the traditional rack structure currently used on the ISS for the mounting of internal hardware and replacing it with a core structure. By using this design, the pressure shell will not have to carry the loads resulting from the internal mass. I worked with another intern to create the initial design for the module, with him focusing on the core and myself focusing on the pressure shell. To start, I was given the shell overall dimensions and material and tasked with sizing the wall thickness and placing stiffeners such that the shell could withstand the required loads. At the same time, I had to keep the mass to a minimum to keep the overall module within the allowable launch mass. Once I had done initial sizing based on pressure loads, I combined the pressure shell with the inner core to perform optimization of the design. Currently, the design involves circumferential stiffeners along the entire length of the pressure shell with longitudinal stiffeners on either end. In addition, extra wall thickness was added around each of the hatches. At this stage, the design shows a comparable mass to a more traditional design, but we are hopeful that, through optimization, we will be able to reduce the mass even further. There is currently a patent pending for the module design, for which I am listed as a co-inventor. ALON Material Testing: I was given samples of aluminum oxynitride (ALON) that had been impacted by a previous intern on which to perform residual strength tests as part of a plan to approve them for space use. Before testing, I measured the pucks and their damages using a ruler and optical micrometer in order to verify that the puck dimensions were within the tolerances set by the test guidelines and that the damages had not grown when the pucks were thinned. The test was a ring-ring test, which used two concentric rings to place the ring in axisymmetric bending, with the puck set up so that the damaged side was always in tension. Though I was unable to do the setup of the test or run the load machine due to a period of changing test procedures, I was able to observe the testing and perform the data collection. The pucks behaved as expected, breaking at the damage, as did the strengths calculated from the data, being lower than for the unimpacted pucks and having less scatter between the puck values. The attached image is of myself during the ALON strength testing. Over the course of my internship, I was able to learn much more about real-life structural analysis and about the behavior of materials, and it confirmed my previous interest in structural analysis. At the same time, due to the opportunities offered to interns, I was able to learn a lot about mission control, and, in doing so, I developed a second interest in working in mission control. In addition, being able to meet the people here and learn about the type of work NASA does made me want to come back to work for NASA full time.

Simmons, Emily↗
NASA NTRS1972

Apollo 15 and 16 ground-commanded television assembly.

During the Apollo 15 and 16 missions, a special camera provided the scientific community and the home viewer with real-time coverage of the lunar exploration. The lunar blast-off of the Apollo 16 ascent module was tracked by the mission controller at NASA's Manned Space Center and watched 250,000 miles away on earth. The operation of this television camera and the remote control unit are described and block diagrams given. Ground-command capability from the Mission Control Center permitted versatility and optimization of the TV coverage, without diverting the astronauts from their primary role of lunar exploration.

Soltoff, B. M.↗
NASA NTRS1994

The NASA Mission Operations and Control Architecture Program

The conflict between increases in space mission complexity and rapidly declining space mission budgets has created strong pressures to radically reduce the costs of designing and operating spacecraft. A key approach to achieving such reductions is through reducing the development and operations costs of the supporting mission operations systems. One of the efforts which the Communications and Data Systems Division at NASA Headquarters is using to meet this challenge is the Mission Operations Control Architecture (MOCA) project. Technical direction of this effort has been delegated to the Mission Operations Division (MOD) of the Goddard Space Flight Center (GSFC). MOCA is to develop a mission control and data acquisition architecture, and supporting standards, to guide the development of future spacecraft and mission control facilities at GSFC. The architecture will reduce the need for around-the-clock operations staffing, obtain a high level of reuse of flight and ground software elements from mission to mission, and increase overall system flexibility by enabling the migration of appropriate functions from the ground to the spacecraft. The end results are to be an established way of designing the spacecraft-ground system interface for GSFC's in-house developed spacecraft, and a specification of the end to end spacecraft control process, including data structures, interfaces, and protocols, suitable for inclusion in solicitation documents for future flight spacecraft. A flight software kernel may be developed and maintained in a condition that it can be offered as Government Furnished Equipment in solicitations. This paper describes the MOCA project, its current status, and the results to date.

Ondrus, Paul J.↗
NASA NTRS2005

STS-114: Discovery Post MMT Briefing

On flight day 13, Leroy Cain, STS-114 Ascent/Entry Flight Director, discusses the condition of the Space Shuttle Discovery, and the weather outlook for landing. He answers questions from the news media about his feelings about re-entry since the Columbia tragedy, possible new information during re-entry, critical moments in the Mission Control Room during landing, and differences between night landing and day landing. Footage of the Mission Control Room and a talk with Soichi Noguchi in orbit is shown. Also, footage of the truss structure of the International Space Station, Destiny Laboratory, crew cabin of Discovery, and the Orbiter Docking System linked up to forward docking port on Discovery is shown. Eileen Collins and Wendy Lawrence are shown in the flight deck of Discovery. Charles Camarda is also shown in the mid-deck. Downlink television from Discovery shows spacewalk choreographer Andy Thomas with Stephen Robinson and Soichi Noguchi preparing for depressurization and pre-breathing activities that will lead to the opening of the hatch. The installation of a replacement GPS antenna, images of the port wing of Discovery and Canadarm moving with the Orbital Boom Sensor System (OBSS) extension is shown.

Source record↗
NASA NTRS1979

Viking adaptive mission sequence and control operations

Viking mission operations were required to provide an adaptive sequencing capability in which future observations could be influenced by the latest information about Mars as it was obtained and analyzed. The mission operations strategy that was developed met this requirement and provided the capability to respond smoothly and efficiently to spacecraft subsystem anomalies with minimum impact on the science data gathering process. A description of the major elements of this adaptive man-in-the-loop control system is provided. Specific cases showing how it was utilized to enhance scientific return and to respond to spacecraft anomalies are also provided.

Larman, B. T.↗
NASA NTRS2011

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

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

Hall, Timothy A.↗
NASA NTRS2004

Future Concepts for Realtime Data Interfaces for Control Centers

Existing methods of exchanging realtime data between the major control centers in the International Space Station program have resulted in a patchwork of local formats being imposed on each Mission Control Center. This puts the burden on a data customer to comply with the proprietary data formats of each data supplier. This has increased the cost and complexity for each participant, limited access to mission data and hampered the development of efficient and flexible operations concepts. Ideally, a universal format should be promoted in the industry to prevent the unnecessary burden of each center processing a different data format standard for every external interface with another center. With the broad acceptance of XML and other conventions used in other industries, it is now time for the Aerospace industry to fully engage and establish such a standard. This paper will briefly consider the components that would be required by such a standard (XML schema, data dictionaries, etc.) in order to accomplish the goal of a universal low-cost interface, and acquire broad industry acceptance. We will then examine current approaches being developed by standards bodies and other groups. The current state of CCSDS panel work will be reviewed, with a survey of the degree of industry acceptance. Other widely accepted commercial approaches will be considered, sometimes complimentary to the standards work, but sometimes not. The question is whether de facto industry standards are in concert with, or in conflict with the direction of the standards bodies. And given that state of affairs, the author will consider whether a new program establishing its Mission Control Center should implement a data interface based on those standards. The author proposes that broad industry support to unify the various efforts will enable collaboration between control centers and space programs to a wider degree than is currently available. This will reduce the cost for programs to provide realtime access to their data, hence reducing the cost of access to space, and benefiting the industry as a whole.

Kearney, Mike W., III↗
NASA NTRS2009

Formal Methods for Automated Diagnosis of Autosub 6000

This is a progress report on applying formal methods in the context of building an automated diagnosis and recovery system for Autosub 6000, an Autonomous Underwater Vehicle (AUV). The diagnosis task involves building abstract models of the control system of the AUV. The diagnosis engine is based on Livingstone 2, a model-based diagnoser originally built for aerospace applications. Large parts of the diagnosis model can be built without concrete knowledge about each mission, but actual mission scripts and configuration parameters that carry important information for diagnosis are changed for every mission. Thus we use formal methods for generating the mission control part of the diagnosis model automatically from the mission script and perform a number of invariant checks to validate the configuration. After the diagnosis model is augmented with the generated mission control component model, it needs to be validated using verification techniques.

Ernits, Juhan↗
NASA NTRS2001

Human interactions in space: results from Shuttle/Mir

Background: Anecdotal reports from space and results from simulation studies on Earth have suggested that space crewmembers may experience decrements in their interpersonal environment over time and may displace tension and dysphoria to mission control personnel. Methods: To evaluate these issues, we studied 5 American astronauts, 8 Russian cosmonauts, and 42 American and 16 Russian mission control personnel who participated in the Shuttle/Mir space program. Subjects completed questions from subscales of the Profile of Mood States, the Group Environment Scale, and the Work Environment Scale on a weekly basis before, during, and after the missions. Results: Among the crewmembers, there was little evidence for significant time effects based on triphasic (U-shaped) or linear models for the 21 subscales tested, although the presence of an initial novelty effect that declined over time was found in three subscales for the astronauts. Compared with work groups on Earth, the crewmembers reported less dysphoria and perceived their crew environment as more constraining, cohesive, and guided by leadership. There was no change in ratings of mood and interpersonal environment before, during, and after the missions. Conclusions: There was little support for the presence of a moderate to strong time effect that influenced the space crews. Crewmembers perceived their work environment differently from people on Earth, and they demonstrated equanimity in mood and group perceptions, both in space and on the ground. Grant numbers: NAS9-19411. c 2001. Elsevier Science Ltd. All rights reserved.

Soyuz Project↗
NASA NTRS1996

State modeling and pass automation in spacecraft control

The integrated monitoring and control commercial off-the-shelf system (IMACCS), which demonstrates the feasibility of automating spacecraft monitoring and control activities through the use of state modeling, is described together with its use. The use of the system for the control and ground support of the solar, anomalous and magnetic particle explorer (SAMPEX) spacecraft is considered. A key component of IMACCS is the Altair mission control system which implements finite state modeling as an element of its expert system capability. Using the finite state modeling and state transition capabilities of the Altair mission control system, IMACCS features automated monitoring, routine pass support, anomaly resolution and emergency 'lights on again' response. Automatic orbit determination and the production of typical flight dynamics products exists. These functionalities are described.

Klein, J.↗
NASA NTRS2014

Use of Semi-Autonomous Tools for ISS Commanding and Monitoring

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.

Brzezinski, Amy S.↗
NASA NTRS2012

Trajectory Software With Upper Atmosphere Model

The Trajectory Software Applications 6.0 for the Dec Alpha platform has an implementation of the Jacchia-Lineberry Upper Atmosphere Density Model used in the Mission Control Center for International Space Station support. Previous trajectory software required an upper atmosphere to support atmosphere drag calculations in the Mission Control Center. The Functional operation will differ depending on the end-use of the module. In general, the calling routine will use function-calling arguments to specify input to the processor. The atmosphere model will then compute and return atmospheric density at the time of interest.

Barrett, Charles↗
NASA NTRS1994

Operator procedure verification with a rapidly reconfigurable simulator

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.

Iwasaki, Yumi↗
NASA NTRS2006

Control Room Training for the Hyper-X Program Utilizing Aircraft Simulation

The NASA Dryden Flight Research Center flew two Hyper-X Research Vehicles and achieved hypersonic speeds over the Pacific Ocean in March and November 2004. To train the flight and mission control room crew, the NASA Dryden simulation capability was utilized to generate telemetry and radar data, which was used in nominal and emergency mission scenarios. During these control room training sessions, personnel were able to evaluate and refine data displays, flight cards, mission parameter allowable limits, and emergency procedure checklists. Practice in the mission control room ensured that all primary and backup Hyper-X staff were familiar with the nominal mission and knew how to respond to anomalous conditions quickly and successfully. This paper describes the technology in the simulation environment and the mission control center, the need for and benefit of control room training, and the rationale and results of specific scenarios unique to the Hyper-X research missions.

Lux-Baumann, Jessica R.↗
NASA NTRS2006

Control Room Training for the Hyper-X Project Utilizing Aircraft Simulation

The NASA Dryden Flight Research Center flew two Hyper-X research vehicles and achieved hypersonic speeds over the Pacific Ocean in March and November 2004. To train the flight and mission control room crew, the NASA Dryden simulation capability was utilized to generate telemetry and radar data, which was used in nominal and emergency mission scenarios. During these control room training sessions personnel were able to evaluate and refine data displays, flight cards, mission parameter allowable limits, and emergency procedure checklists. Practice in the mission control room ensured that all primary and backup Hyper-X staff were familiar with the nominal mission and knew how to respond to anomalous conditions quickly and successfully. This report describes the technology in the simulation environment and the Mission Control Center, the need for and benefit of control room training, and the rationale and results of specific scenarios unique to the Hyper-X research missions.

Lux-Baumann, Jesica↗
NASA NTRS1999

Plug and Play Integration through Space Object Standardization

Plug and play is an industry standard promoted by Intel and Microsoft, and others that allows users to add and remove various input and output devices without making specific customizations to their systems. The idea behind concept is that using standard products eases integration of components and promotes capabilities of conforming products. The concept works because vendors comply with a standard specification. This paper reports the development of a reference architecture for the mission control domain, which is leveraging off this revolutionary concept. Standards are being developed at the application layer, which enable "plug and play" of mission software products. A Mission Control, reference architecture has been defined. For each sub-domain, the interfaces are modeled in Interface Definition Language (IDL). A subset of the IDL has been developed within both commercial off-the-shelf (COTS) and government (GOTS) products. Selected vendors have agreed to modify their products to be compatible with the defined IDL. The plug and play integration of these different products has been validated in a demonstration testbed.

Boyce, Leslye↗