SEARCH · Search NASA

Results for “mission management”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 253 records · Page 14

All sources NASA NTRS DOE OSTI

NASA NTRS2005

STS-114: Discovery Post MMT Press Conference

This press conference focuses on the outcome of the Mission Management Team (MMT) meeting. The launch and status of the Space Shuttle Discovery is discussed. George Diller from NASA Public Affairs introduces the panel which consists of: Wayne Hale, Space Shuttle Program Deputy Manager and Mike Wetmore, Director of Space Shuttle Processing at Nasa Kennedy Space Center. The news media asks questions about the history of the low level sensors in the hydrogen tank, the cryogenic atmosphere around the sensors, troubleshooting, astronaut activities, possible rollback procedures.

Source record↗

NASA NTRS2005

STS-114: Discovery L-1 Countdown Status Briefing STS-114/Discovery L-2 Countdown Status Briefing

Bruce Buckingham from NASA Public Affairs introduces Jeff Spaulding, NASA Test Director and Kathy Winters, Shuttle Weather Officer in this L-2 countdown status briefing. Spaulding gives the Space Shuttle launch countdown status before lift-off on July 26th. He expresses that vehicle launch and ground systems are performing well and that there are no significant issues in preparation for the launch. The crew arrival time to the launching pad and the launch window for Discovery is also discussed. He ends his countdown status by expressing that the Discovery Orbiter is the safest Shuttle to date. Kathy Winters gives her weather forecast for the launch day. She presents a satellite picture of tropical storm Franklin and charts showing the STS-114 Tanking Forecast, Launch Forecast, Solid Rocket Booster (SRB) recovery, Continental United States (CONUS) launch, Transoceanic Abort Landing (TAL) launch, 24 and 48 Hour Delay, CONUS 24 and 48 hour delay, and TAL 24 and 48 hr delay. Questions from the news media about the mood of the test engineers as launch day is approached are answered. Jessica Rye from NASA Public Affairs introduces Pete Nikolento, NASA Test Director; Scott Higgenbotham, STS-114 Payload Mission Manager; and Kathy Winters, Space Shuttle Weather Officer in this L-1 Countdown Status Briefing. Nikolento expresses that the completion of the main engine system check-outs and servicing of on-board fuel-cell reactants have been completed. He also talks about pad closeouts and external cryogenic loads prior to launch. Scott Higgenbotham gives the payload status and Kathy Winters talks about her weather forecast for launch. Questions about the ecosensors, TAL sites, weather forecast and thoughts about return to flight are addressed.

Source record↗

NASA NTRS2005

Apex Reference Manual 3.0 Beta

Apex is a toolkit for constructing software that behaves intelligently and responsively in demanding task environments. Reflecting its origin at NASA where Apex continues to be developed, current applications include: a) Providing autonomous mission management and tactical control capabilities for unmanned aerial vehicles including an autonomous surveillance helicopter and a simulation prototype of an unmanned fixed-wing aircraft to be used for wildfire mapping; b) Simulating human air traffic controllers, pilots and astronauts to help predict how people might respond to changes in equipment or procedures; and c) Predicting the precise duration and sequence of routine human behaviors based on a human-computer interaction engineering technique called CPM-GOMS. Among Apex s components are a set of implemented reasoning services, such as those for reactive planning and temporal pattern recognition; a software architecture that embeds and integrates these services and allows additional reasoning elements to be added as extensions; a formal language for specifying agent knowledge; a simulation environment to facilitate prototyping and analysis; and Sherpa, a set of tools for visualizing autonomy logic and runtime behavior. In combination, these are meant to provide a flexible and usable framework for creating, testing, and deploying intelligent agent software. Overall, our goal in developing Apex is to lower economic barriers to developing intelligent software agents. New ideas about how to extend or modify the system are evaluated in terms of their impact in reducing the time, expertise, and inventiveness required to build and maintain applications. For example, potential enhancements to the AI reasoning capabilities in the system are reviewed not only for usefulness and distinctiveness, but also for their impact on the readability and general usability of Apex s behavior representation language (PDL) and on the transparency of resulting behavior. A second central part of our approach is to iteratively refine Apex based on lessons learned from as diverse a set of applications as possible. Many applications have been developed by users outside the core development team including engineers, researchers, and students. Usability is thus a central concern for every aspect of Apex visible to a user, including PDL, Sherpa, the Apex installation process, APIs, and user documentation. Apex users vary in their areas of expertise and in their familiarity with autonomy technology. Focusing on usability, a development philosophy summarized by the project motto "Usable Autonomy," has been important part of enabling diverse users to employ Apex successfully and to provide feedback needed to guide iterative, user-centered refinement.

Freed, Michael A.↗

NASA NTRS2003

Multi-mission ground data systems - breakthroughs and challenges

Given the cost-constrained nature of JPL Flight Projects, especially Discovery Class missions, there is more and more pressure to reduce the costs associated with mission operations, particularly the costs for the Ground Data System. This paper explores the successes (and failures) of using the Mission Management Office (MMO) GDS team to provide a common set of services, tools, procedures, and products to JPL Flight Projects.

GDS↗

NASA NTRS2003

Machine learning challenges in Mars rover traverse science

The successful implementation of machine learning in autonomous rover traverse science requires addressing challenges that range from the analytical technical realm, to the fuzzy, philosophical domain of entrenched belief systems within scientists and mission managers.

OASIS onboard autonomous science investigation sys↗

NASA NTRS2007

Flight and Integrated Testing: Blazing the Trail for the Ares Launch Vehicles

It has been 30 years since the United States last designed and built a human-rated launch vehicle. The National Aeronautics and Space Administration (NASA) has marshaled unique resources from the government and private sectors that will carry the next generation of astronauts into space safer and more efficiently than ever and send them to the Moon to develop a permanent outpost. NASA's Flight and Integrated Test Office (FITO) located at Marshall Space Flight Center and the Ares I-X Mission Management Office have primary responsibility for developing and conducting critical ground and flight tests for the Ares I and Ares V launch vehicles. These tests will draw upon Saturn and the Space Shuttle experiences, which taught the value of using sound systems engineering practices, while also applying aerospace best practices such as "test as you fly" and other lessons learned. FITO will use a variety of methods to reduce the technical, schedule, and cost risks of flying humans safely aboard a launch vehicle.

Taylor, James L.↗

NASA NTRS2008

International Space Station Medical Operations

NASA is currently the leader, in conjunction with our Russian counterpart co-leads, of the Multilateral Medical Policy Board (MMPB), the Multilateral Medical Operations Panel (MMOP), which coordinates medical system support for International Space Station (ISS) crews, and the Multilateral Space Medicine Board (MSMB), which medically certifies all crewmembers for space flight on-board the ISS. These three organizations have representatives from NASA, RSA-IMBP (Russian Space Agency- Institute for Biomedical Problems), GCTC (Gagarin Cosmonaut Training Center), ESA (European Space Agency), JAXA (Japanese Space Agency), and CSA (Canadian Space Agency). The policy and strategic coordination of ISS medical operations occurs at this level, and includes interactions with MMOP working groups in Radiation Health, Countermeasures, Extra Vehicular Activity (EVA), Informatics, Environmental Health, Behavioral Health and Performance, Nutrition, Clinical Medicine, Standards, Post-flight Activities and Rehabilitation, and Training. Each ISS Expedition has a lead Crew Surgeon from NASA and a Russian Crew Surgeon from GCTC assigned to the mission. Day-to-day issues are worked real-time by the flight surgeons and biomedical engineers (also called the Integrated Medical Group) on consoles at the MCC (Mission Control Center) in Houston and the TsUP (Center for Flight Control) in Moscow/Korolev. In the future, this may also include mission control centers in Europe and Japan, when their modules are added onto the ISS. Private medical conferences (PMCs) are conducted regularly and upon crew request with the ISS crew via private audio and video communication links from the biomedical MPSR (multipurpose support room) at MCC Houston. When issues arise in the day-to-day medical support of ISS crews, they are discussed and resolved at the SMOT (space medical operations team) meetings, which occur weekly among the International Partners. Any medical or life science issue that is not resolved at the SMOT can be taken to the Mission Management Team meeting, which occurs biweekly from MCC-Houston. This meeting includes the other International Partners and all flight support and console position representatives via teleconference. ISS Crew Surgeons have handled many medical conditions on orbit; including skin rashes, dental abscesses, lacerations, and STT segment EKG changes. Fortunately to date, there have not been any forced medical evacuations from the ISS. This speaks well for the implementation of the primary, secondary and even tertiary prevention strategies invoked by the Integrated Medical Group, as there were several medical evacuations during the previous Russian space stations.

Jones, Jeffrey A.↗

NASA NTRS2008

Aerobraking Maneuver (ABM) Report Generator

abmREPORT Version 3.1 is a Perl script that extracts vital summarization information from the Mars Reconnaissance Orbiter (MRO) aerobraking ABM build process. This information facilitates sequence reviews, and provides a high-level summarization of the sequence for mission management. The script extracts information from the ENV, SSF, FRF, SCMFmax, and OPTG files and burn magnitude configuration files and presents them in a single, easy-to-check report that provides the majority of the parameters necessary for cross check and verification during the sequence review process. This means that needed information, formerly spread across a number of different files and each in a different format, is all available in this one application. This program is built on the capabilities developed in dragReport and then the scripts evolved as the two tools continued to be developed in parallel.

Fisher, Forrest↗

NASA NTRS2010

Marshall Application Realignment System (MARS) Architecture

The Marshall Application Realignment System (MARS) Architecture project was established to meet the certification requirements of the Department of Defense Architecture Framework (DoDAF) V2.0 Federal Enterprise Architecture Certification (FEAC) Institute program and to provide added value to the Marshall Space Flight Center (MSFC) Application Portfolio Management process. The MARS Architecture aims to: (1) address the NASA MSFC Chief Information Officer (CIO) strategic initiative to improve Application Portfolio Management (APM) by optimizing investments and improving portfolio performance, and (2) develop a decision-aiding capability by which applications registered within the MSFC application portfolio can be analyzed and considered for retirement or decommission. The MARS Architecture describes a to-be target capability that supports application portfolio analysis against scoring measures (based on value) and overall portfolio performance objectives (based on enterprise needs and policies). This scoring and decision-aiding capability supports the process by which MSFC application investments are realigned or retired from the application portfolio. The MARS Architecture is a multi-phase effort to: (1) conduct strategic architecture planning and knowledge development based on the DoDAF V2.0 six-step methodology, (2) describe one architecture through multiple viewpoints, (3) conduct portfolio analyses based on a defined operational concept, and (4) enable a new capability to support the MSFC enterprise IT management mission, vision, and goals. This report documents Phase 1 (Strategy and Design), which includes discovery, planning, and development of initial architecture viewpoints. Phase 2 will move forward the process of building the architecture, widening the scope to include application realignment (in addition to application retirement), and validating the underlying architecture logic before moving into Phase 3. The MARS Architecture key stakeholders are most interested in Phase 3 because this is where the data analysis, scoring, and recommendation capability is realized. Stakeholders want to see the benefits derived from reducing the steady-state application base and identify opportunities for portfolio performance improvement and application realignment.

Belshe, Andrea↗

NASA NTRS2010

Ares I-X: First Step in a New Era of Exploration

Since 2005, NASA's Constellation Program has been designing, building, and testing the next generation of launch and space vehicles to carry humans beyond low-Earth orbit (LEO). On October 28, 2009, the Ares Projects successfully launched the first suborbital development flight test of the Ares I crew launch vehicle, Ares I-X, from Kennedy Space Center (KSC). Although the final Constellation Program architecture is under review, data and lessons obtained from Ares I-X can be applied to any launch vehicle. This presentation will discuss the mission background and future impacts of the flight. Ares I is designed to carry up to four astronauts to the International Space Station (ISS). It also can be used with the Ares V cargo launch vehicle for a variety of missions beyond LEO. The Ares I-X development flight test was conceived in 2006 to acquire early engineering, operations, and environment data during liftoff, ascent, and first stage recovery. Engineers are using the test flight data to improve the Ares I design before its critical design review the final review before manufacturing of the flight vehicle begins. The Ares I-X flight test vehicle incorporated a mix of flight and mockup hardware, reflecting a similar length and mass to the operational vehicle. It was powered by a four-segment SRB from the Space Shuttle inventory, and was modified to include a fifth, spacer segment that made the booster approximately the same size as the five-segment SRB. The Ares I-X flight closely approximated flight conditions the Ares I will experience through Mach 4.5, performing a first stage separation at an altitude of 125,000 feet and reaching a maximum dynamic pressure ("Max Q") of approximately 850 pounds per square foot. The Ares I-X Mission Management Office (MMO) was organized functionally to address all the major test elements, including: first stage, avionics, and roll control (Marshall Space Flight Center); upper stage simulator (Glenn Research Center); crew module/launch abort system simulator (Langley Research Center); and ground systems and operations (KSC). Interfaces between vehicle elements and vehicle-ground elements, as well as environment analyses were performed by a systems engineering and integration team at Langley. Experience and lessons learned from these integrated product teams area are already being integrated into the Ares Projects to support the next generation of exploration launch vehicles.

Davis, Stephan R.↗

NASA NTRS2003

Predicting and Managing Lighting and Visibility for Human Operations in Space

Lighting is critical to human visual performance. On earth this problem is well understood and solutions are well defined and executed. Because the sun rises and sets on average every 45 minutes during Earth orbit, humans working in space must cope with ~ extremely dynamic lighting conditions varying from very low light conditions to severe glare and contrast conditions. For critical operations, it is essential that lighting conditions be predictable and manageable. Mission planners need to detelmine whether low-light video cameras are required or whether additional luminaires, or lamps, need to be flown . Crew and flight directors need to have up to date daylight orbit time lines showing the best and worst viewing conditions for sunlight and shadowing. Where applicable and possible, lighting conditions need to be part of crew training. In addition, it is desirable to optimize the quantity and quality of light because of the potential impacts on crew safety, delivery costs, electrical power and equipment maintainability for both exterior and interior conditions. Addressing these issues, an illumination modeling system has been developed in the Space Human Factors Laboratory at ASA Johnson Space Center. The system is the integration of a physically based ray-tracing package ("Radiance"), developed at the Lawrence Berkeley Laboratories, a human factors oriented geometric modeling system developed by NASA and an extensive database of humans and their work environments. Measured and published data has been collected for exterior and interior surface reflectivity; luminaire beam spread distribution, color and intensity and video camera light sensitivity and has been associated with their corresponding geometric models. Selecting an eye-point and one or more light sources, including sun and earthshine, a ~ snapshot of the light energy reaching the surfaces or reaching the eye point is computed. This energy map is then used to extract the required information needed for useful predictions. Using a validated, comprehensive illumination model integrated with empirically derived data, predictions of lighting and viewing conditions have been successfully used for Shuttle and Space Station planning and assembly operations. It has successfully balanced the needs for adequate human performance with the utili zation of resources. Keywords: Modeling, ray tracing, luminaires, refl ectivity, luminance, illuminance.

Maida, James C.↗

NASA NTRS2005

Using Simulation for Launch Team Training and Evaluation

This document describes some of the histor y and uses of simulation systems and processes for the training and evaluation of Launch Processing, Mission Control, and Mission Management teams. It documents some of the types of simulations that are used at Kennedy Space Center (KSC) today and that could be utilized (and possibly enhanced) for future launch vehicles. This article is intended to provide an initial baseline for further research into simulation for launch team training in the near future.

Peaden, Cary J.↗

NASA NTRS2011

Contact Graph Routing

Contact Graph Routing (CGR) is a dynamic routing system that computes routes through a time-varying topology of scheduled communication contacts in a network based on the DTN (Delay-Tolerant Networking) architecture. It is designed to enable dynamic selection of data transmission routes in a space network based on DTN. This dynamic responsiveness in route computation should be significantly more effective and less expensive than static routing, increasing total data return while at the same time reducing mission operations cost and risk. The basic strategy of CGR is to take advantage of the fact that, since flight mission communication operations are planned in detail, the communication routes between any pair of bundle agents in a population of nodes that have all been informed of one another's plans can be inferred from those plans rather than discovered via dialogue (which is impractical over long one-way-light-time space links). Messages that convey this planning information are used to construct contact graphs (time-varying models of network connectivity) from which CGR automatically computes efficient routes for bundles. Automatic route selection increases the flexibility and resilience of the space network, simplifying cross-support and reducing mission management costs. Note that there are no routing tables in Contact Graph Routing. The best route for a bundle destined for a given node may routinely be different from the best route for a different bundle destined for the same node, depending on bundle priority, bundle expiration time, and changes in the current lengths of transmission queues for neighboring nodes; routes must be computed individually for each bundle, from the Bundle Protocol agent's current network connectivity model for the bundle s destination node (the contact graph). Clearly this places a premium on optimizing the implementation of the route computation algorithm. The scalability of CGR to very large networks remains a research topic. The information carried by CGR contact plan messages is useful not only for dynamic route computation, but also for the implementation of rate control, congestion forecasting, transmission episode initiation and termination, timeout interval computation, and retransmission timer suspension and resumption.

Burleigh, Scott C.↗

NASA NTRS2013

Millimeter-Wave Localizers for Aircraft-to-Aircraft Approach Navigation

Aerial refueling technology for both manned and unmanned aircraft is critical for operations where extended aircraft flight time is required. Existing refueling assets are typically manned aircraft, which couple to a second aircraft through the use of a refueling boom. Alignment and mating of the two aircraft continues to rely on human control with use of high-resolution cameras. With the recent advances in unmanned aircraft, it would be highly advantageous to remove/reduce human control from the refueling process, simplifying the amount of remote mission management and enabling new operational scenarios. Existing aerial refueling uses a camera, making it non-autonomous and prone to human error. Existing commercial localizer technology has proven robust and reliable, but not suited for aircraft-to-aircraft approaches like in aerial refueling scenarios since the resolution is too coarse (approximately one meter). A localizer approach system for aircraft-to-aircraft docking can be constructed using the same modulation with a millimeterwave carrier to provide high resolution. One technology used to remotely align commercial aircraft on approach to a runway are ILS (instrument landing systems). ILS have been in service within the U.S. for almost 50 years. In a commercial ILS, two partially overlapping beams of UHF (109 to 126 MHz) are broadcast from an antenna array so that their overlapping region defines the centerline of the runway. This is called a localizer system and is responsible for horizontal alignment of the approach. One beam is modulated with a 150-Hz tone, while the other with a 90-Hz tone. Through comparison of the modulation depths of both tones, an autopilot system aligns the approaching aircraft with the runway centerline. A similar system called a glide-slope (GS) exists in the 320-to-330MHz band for vertical alignment of the approach. While this technology has been proven reliable for millions of commercial flights annually, its UHF nature limits its ability to operate beyond the 1-to-2-meter precisions associated with commercial runway width. A prototype ILS-type system operates at millimeter-wave frequencies to provide automatic and robust approach control for aerial refueling. The system allows for the coupling process to remain completely autonomous, as a boom operator is no longer required. Operating beyond 100 GHz provides enough resolution and a narrow enough beamwidth that an approach corridor of centimeter scales can be maintained. Two modules were used to accomplish this task. The first module is a localizer/glide-slope module that can be fitted on a refueling aircraft. This module provides the navigation beams for aligning the approaching aircraft. The second module is navigational receiver fitted onto the approaching aircraft to be re fueled that can detect the approach beams. Since unmanned aircraft have a limited payload size and limited electrical power, the receiver portion was implemented in CMOS (complementary metal oxide semiconductor) technology based on a super-regenerative receiver (SRR) architecture. The SRR achieves mW-level power consumption and chip sizes less than l mm2. While super-regenerative techniques have small bandwidths that limit use in communication systems, their advantages of high sensitivity, low complexity, and low power make them ideal in this situation where modulating tones of less than 1 kHz are used.

Tang, Adrian J.↗

NASA NTRS2013

Recommended Figures of Merit for Green Monopropellants

Hydrazine propellant has historically been used as a rocket thruster monopropellant since the mid-1960s. Mission managers are well aware of its characteristics and performance. However, it is a known toxic chemical and a wide effort is underway to reduce and/or eliminate its use worldwide. Several new propellant combinations have been developed in the last few years which tout or promise to provide same or better performance as hydrazine while being "non-toxic" or "green". Yet, there is no consistent definition for what constitutes "non-toxic" or "green", and thus no good figure of merit for which to compare. This paper seeks to review the three major categories of figures of merit, and discusses how they might be used to assess the viability of a propellant.

Marshall, William M.↗

NASA NTRS2013

Recommended Figures of Merit for Green Monopropellants

Marshall. William M.↗

NASA NTRS2014

Overview of Intelligent Power Controller Development for Human Deep Space Exploration

Intelligent or autonomous control of an entire spacecraft is a major technology that must be developed to enable NASA to meet its human exploration goals. NASA's current long term human space platform, the International Space Station, is in low earth orbit with almost continuous communication with the ground based mission control. This permits the near real-time control by the ground of all of the core systems including power. As NASA moves beyond Low Earth Orbit, the issues of communication time-lag and lack of communication bandwidth beyond geosynchronous orbit does not permit this type of operation. This paper presents the work currently ongoing at NASA to develop an architecture for an autonomous power control system as well as the effort to assemble that controller into the framework of the vehicle mission manager and other subsystem controllers to enable autonomous control of the complete spacecraft. Due to the common problems faced in both space power systems and terrestrial power system, the potential for spin-off applications of this technology for use in micro-grids located at the edge or user end of terrestrial power grids for peak power accommodation and reliability are described.

Space Flight↗

NASA NTRS2014

Overview of Intelligent Power Controller Development for Human Deep Space Exploration

Intelligent or autonomous control of an entire spacecraft is a major technology that must be developed to enable NASA to meet its human exploration goals. NASAs current long term human space platform, the International Space Station, is in low earth orbit with almost continuous communication with the ground based mission control. This permits the near real-time control by the ground of all of the core systems including power. As NASA moves beyond Low Earth Orbit, the issues of communication time-lag and lack of communication bandwidth beyond geosynchronous orbit does not permit this type of operation. This paper presents the work currently ongoing at NASA to develop an architecture for an autonomous power control system as well as the effort to assemble that controller into the framework of the vehicle mission manager and other subsystem controllers to enable autonomous control of the complete spacecraft. Due to the common problems faced in both space power systems and terrestrial power system, the potential for spin-off applications of this technology for use in micro-grids located at the edge or user end of terrestrial power grids for peak power accommodation and reliability are described.

Space Flight↗