Search NASA⌕ Search

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.

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

At least 235 records · Page 13
All sourcesNASA NTRSDOE OSTI
NASA NTRS1993

A MOS for all seasons

From a systems perspective, this paper examines the challenges of a single system to support multiple JPL space exploration missions and the need for unitary responsibility for the system. The focus is a Mission Operations System (MOS), which is effectively a mission management organization with direct authority over data system operations, command sequencing, flight operations control, data management, trajectory determination, telemetry and data acquisition, and spacecraft analysis. Stratagems for training and the approach to processes, procedures, and interfaces to facilitate the transition from the present situation to a truly multimission operational environment are developed. The outcome is a paradigm for a MOS that is achievable, that can effectively support multiple projects, and that can take advantage of technological changes without perturbing the entire system.

Bryant, Larry↗
NASA NTRS1994

Magellan Project: Evolving enhanced operations efficiency to maximize science value

Magellan has been one of NASA's most successful spacecraft, returning more science data than all planetary spacecraft combined. The Magellan Spacecraft Team (SCT) has maximized the science return with innovative operational techniques to overcome anomalies and to perform activities for which the spacecraft was not designed. Commanding the spacecraft was originally time consuming because the standard development process was envisioned as manual tasks. The Program understood that reducing mission operations costs were essential for an extended mission. Management created an environment which encouraged automation of routine tasks, allowing staff reduction while maximizing the science data returned. Data analysis and trending, command preparation, and command reviews are some of the tasks that were automated. The SCT has accommodated personnel reductions by improving operations efficiency while returning the maximum science data possible.

Cheuvront, Allan R.↗
NASA NTRS1996

STS-80 Flight Day 13

On this thirteenth day of the STS-80 mission, the flight crew, Cmdr. Kenneth D. Cockrell, Pilot Kent V. Rominger, Mission Specialists, Tamara E. Jernigan, Thomas D. Jones, and F. Story Musgrave, are notified that the remaining spacewalks for the mission are to be canceled following extensive ground analysis and testing of the airlock hatch. Mission managers could not conclusively identify the problem that was causing the hatch to jam, and decided not to risk unnecessary damage to the hatch or seals.

Source record↗
NASA NTRS1996

STS-80 Flight Day 11

On this eleventh day of the STS-80 mission, the flight crew, Cmdr. Kenneth D. Cockrell, Pilot Kent V. Rominger, Mission Specialists, Tamara E. Jernigan, Thomas D. Jones, and F. Story Musgrave, attempt the first of three planned spacewalks. Jernigan and Jones can be seen in the airlock attempting to open a stuck hatch. After several attempts at trying to open the hatch, the mission management team cancels the spacewalk.

Source record↗
NASA NTRS1995

Lunar Prospector Technical Design Review

Topics considered include: Ames Mission Management Office Rolls and Responsibilities; Program Overview/Requirements/Description; Project Status; Management; Science Goals and Objectives; Science Instruments; and Systems Requirements.

Source record↗
NASA NTRS2000

Lessons from Communicating Space Science Over the Web

The Science Directorate at NASA's Marshall Space Flight Center uses the web in an aggressive manner to expand communications beyond the traditional "public affairs" or "media relations" routines. The key to success has been developing a balanced process that A) involves laboratory personnel and the NASA center community through a weekly Science Communications Roundtable, B) vests ownership and development of the product (i.e., the story) in the scientist a writer resident in the laboratory, and C) seeks taps the talents of the outside communications community through the Research/Roadmap Communications activity. The process is flexible and responsive, allowing Science@NASA to provide daily coverage for events, such as two materials science missions managed by NASA/Marshall. In addition to developing materials for the web, Science@NASA has conducted extensive research to determine what subjects people seek on the web, and the best methods to position stories so they will be found and read.

Dooling, David, Jr.↗
NASA NTRS1999

Design Description of the X-33 Avionics Architecture

In this paper, we provide a design description of the X-33 avionics architecture. The X-33 is an autonomous Single Stage to Orbit (SSTO) launch vehicle currently being developed by Lockheed Martin for NASA as a technology demonstrator for the VentureStar Reusable Launch Vehicle (RLV). The X-33 avionics provides autonomous control of die vehicle throughout takeoff, ascent, descent, approach, landing, rollout, and vehicle safing. During flight the avionics provides communication to the range through uplinked commands and downlinked telemetry. During pre-launch and post-safing activities, the avionics provides interfaces to ground support consoles that perform vehicle flight preparations and maintenance. The X-33 Avionics is a hybrid of centralized and distributed processing elements connected by three dual redundant Mil-Std 1553 data buses. These data buses are controlled by a central processing suite located in the avionics bay and composed of triplex redundant Vehicle Mission Computers (VMCs). The VMCs integrate mission management, guidance, navigation, flight control, subsystem control and redundancy management functions. The vehicle sensors, effectors and subsystems are interfaced directly to the centralized VMCs as remote terminals or through dual redundant Data Interface Units (DIUs). The DIUs are located forward and aft of the avionics bay and provide signal conditioning, health monitoring, low level subsystem control and data interface functions. Each VMC is connected to all three redundant 1553 data buses for monitoring and provides a complete identical data set to the processing algorithms. This enables bus faults to be detected and reconfigured through a voted bus control configuration. Data is also shared between VMCs though a cross channel data link that is implemented in hardware and controlled by AlliedSignal's Fault Tolerant Executive (FTE). The FTE synchronizes processors within the VMC and synchronizes redundant VMCs to each other. The FTE provides an output-voting plane to detect, isolate and contain faults due to internal hardware or software faults and reconfigures the VMCs to accommodate these faults. Critical data in the 1553 messages are scheduled and synchronized to specific processing frames in order to minimize data latency. In order to achieve an open architecture, military and commercial off-the-shelf equipment is incorporated using common processors, standard VME backplanes and chassis, the VxWorks operating system, and MartixX for automatic code generation. The use of off-the-shelf tools and equipment helps reduce development time and enables software reuse. The open architecture allows for technology insertion, while the distributed modular elements allow for expansion to increased redundancy levels to meet the higher reliability goals of future RLVs.

Reichenfeld, Curtis J.↗
NASA NTRS2001

STS-102 Countdown Status Briefing

Joel Wells, NASA Public Affairs, introduces Pete Nickolenko, NASA Test Director, Glenn Chin, Leonardo Mission Manager, and Ed Priselac, Shuttle Weather Officer, in this STS-102 prelaunch press conference. Mr. Nickolenko gives an overview of the countdown and built-in hold times, the launch window, and prelaunch activities (such as activation and checkout of the onboard computer systems, closing the payload bay doors, servicing of the onboard cryogenic cell tanks, main engine tests, and power-up of the ground communications systems). Mr. Chin confirms that the payload is in the final flight configuration and is ready for launch. Mr. Priselac gives the weather forecast for the launch date. The men then answer questions from the press.

Source record↗
NASA NTRS2001

STS-105 Countdown Status Briefing

Joel Wells, NASA Public Affairs, introduces Steve Altemus, NASA Test Director, Glenn Chin, STS-105 Mission Manager, and Ed Priselac, Shuttle Weather Officer, in this STS-105 prelaunch press conference. An overview is given of the launch countdown, payload status (Leonardo Multipurpose Logistics Module), and weather forecast. The men then answer questions from the press.

Source record↗
NASA NTRS2001

STS-104 Countdown Status Briefing

George Diller, NASA Public Affairs, introduces Pete Nickolenko, NASA Test Director, Scott Higginbotham, STS-104 Mission Manager, and Ed Priselac, Shuttle Weather Officer, in this STS-104 launch minus two days press conference. An overview is given of the launch vehicle status, countdown procedures, payload status, and weather forecast. The men then answer questions from the press.

Source record↗
NASA NTRS2001

STS-105 Countdown Status Briefing

Bruce Buckingham, NASA Public Affairs, introduces Steve Altemus, NASA Test Director, and Glenn Chin, STS-105 Mission Manager, in this STS-105 prelaunch press conference. An overview is given of the launch countdown, payload status, and weather forecast. The men then answer questions from the press.

Source record↗
NASA NTRS2001

STS-105 Countdown Status Briefing

Joel Wells, NASA Public Affairs, introduces Pete Nickolenko, NASA Test Director, Glen Chin, STS-105 Mission Manager, and Ed Priselac, Shuttle Weather Officer. They give an overview of the countdown to the STS-105 Discovery Orbiter launch, including details on prelaunch tests (activate and check on-board avionics software, payload bay closeout, prepare and clear launch pad, etc.), payload bay status (Leonardo Multipurpose Logistics Module), and the weather forecast. The men then answer questions from the press.

Source record↗
NASA NTRS2001

RIACS Workshop on the Verification and Validation of Autonomous and Adaptive Systems

The long-term future of space exploration at NASA is dependent on the full exploitation of autonomous and adaptive systems: careful monitoring of missions from earth, as is the norm now, will be infeasible due to the sheer number of proposed missions and the communication lag for deep-space missions. Mission managers are however worried about the reliability of these more intelligent systems. The main focus of the workshop was to address these worries and hence we invited NASA engineers working on autonomous and adaptive systems and researchers interested in the verification and validation (V&V) of software systems. The dual purpose of the meeting was to: (1) make NASA engineers aware of the V&V techniques they could be using; and (2) make the V&V community aware of the complexity of the systems NASA is developing.

Pecheur, Charles↗
NASA NTRS2004

Fixing What's Broken

We planned to launch in July 2000. Heading into March that year we were on schedule, under budget, meeting all of our performance requirements, and ready for the final testing Near the end of the day, it was time for the sign burst test. For 200 milliseconds we would put a non-feedback force on our system, which meant we couldn't adjust or halt the test in progress. Something went wrong, terribly wrong during the sign burst test. For 200 milliseconds we would put a non-feedback force on our system, which meant we couldn't adjust or halt the test in process. Something went wrong, terribly wrong during the sign burst test. As mission manager, I was standing just ten feet away from the spacecraft when this happened. It sounded like a clap of thunder. With the test stopped, we moved in closer to see what had happened - and we knew immediately that we had damaged our spacecraft. How much, we didn't know.

Snow, Frank↗
NASA NTRS2004

Testing of Environmental Satellite Bus-Instrument Interfaces Using Engineering Models

This paper discusses the formulation and execution of a laboratory test of the electrical interfaces between multiple atmospheric science instruments and the spacecraft bus that carries them. The testing, performed in 2002, used engineering models of the instruments that will be flown on the Aura s p a c m and of the Aura spacecraft bus electronics. Aura is one of NASA's Earth Observing System @OS) Program missions managed by the Goddard Space Flight Center. The test was designed to evaluate the complex interfaces in the spacecraft and instrument command and data handling (C&DH) subsystems prior to integration of the complete flight instruments on the spacecraft. A problem discovered during (and not before) the flight hardware integration phase can cause significant cost and schedule impacts. The testing successfully surfaced problems and led to their resolution before the full-up integration phase, saving significant cost and schedule time. This approach could be used on future environmental satellite programs involving multiple, complex scientific instruments being integrated onto a bus.

Gagnier, Don↗
NASA NTRS2005

NASA Project Constellation Systems Engineering Approach

NASA's Office of Exploration Systems (OExS) is organized to empower the Vision for Space Exploration with transportation systems that result in achievable, affordable, and sustainable human and robotic journeys to the Moon, Mars, and beyond. In the process of delivering these capabilities, the systems engineering function is key to implementing policies, managing mission requirements, and ensuring technical integration and verification of hardware and support systems in a timely, cost-effective manner. The OExS Development Programs Division includes three main areas: (1) human and robotic technology, (2) Project Prometheus for nuclear propulsion development, and (3) Constellation Systems for space transportation systems development, including a Crew Exploration Vehicle (CEV). Constellation Systems include Earth-to-orbit, in-space, and surface transportation systems; maintenance and science instrumentation; and robotic investigators and assistants. In parallel with development of the CEV, robotic explorers will serve as trailblazers to reduce the risk and costs of future human operations on the Moon, as well as missions to other destinations, including Mars. Additional information is included in the original extended abstract.

Dumbacher, Daniel L.↗
NASA NTRS1998

Improving Safety and Reliability of Space Auxiliary Power Units

Auxiliary Power Units (APU's) play a critical role in space vehicles. On the space shuttle, APU's provide the hydraulic power for the aerodynamic control surfaces, rocket engine gimballing, landing gear, and brakes. Future space vehicles, such as the Reusable Launch Vehicle, will also need APU's to provide electrical power for flight control actuators and other vehicle subsystems. Vehicle designers and mission managers have identified safety, reliability, and maintenance as the primary concerns for space APU's. In 1997, the NASA Lewis Research Center initiated an advanced technology development program to address these concerns.

Viterna, Larry A.↗
NASA NTRS1999

Space Plasma Shown to Make Satellite Solar Arrays Fail

In 1997, scientists and engineers of the Photovoltaic and Space Environments Branch of the NASA Lewis Research Center, Maxwell Technologies, and Space Systems/Loral discovered a new failure mechanism for solar arrays on communications satellites in orbit. Sustained electrical arcs, initiated by the space plasma and powered by the solar arrays themselves, were found to have destroyed solar array substrates on some Space Systems/Loral satellites, leading to array failure. The mechanism was tested at Lewis, and mitigation strategies were developed to prevent such disastrous occurrences on-orbit in the future. Deep Space 1 is a solar-electric-powered space mission to a comet, launched on October 24, 1998. Early in 1998, scientists at Lewis and Ballistic Missile Defense Organization (BMDO) realized that some aspects of the Deep Space 1 solar arrays were nearly identical to those that had led to the failure of solar arrays on Space Systems/Loral satellites. They decided to modify the Deep Space 1 arrays to prevent catastrophic failure in space. The arrays were suitably modified and are now performing optimally in outer space. Finally, the Earth Observing System (EOS) AM1, scheduled for launch in mid-1999, is a NASA mission managed by the Goddard Space Flight Center. Realizing the importance of Lewis testing on the Loral arrays, EOS-AM1 management asked Lewis scientists to test their solar arrays to show that they would not fail in the same way. The first phase of plasma testing showed that sustained arcing would occur on the unmodified EOS-AM1 arrays, so the arrays were removed from the spacecraft and fixed. Now, Lewis scientists have finished plasma testing of the modified array configuration to ensure that EOS-AM1 will have no sustained arcing problems on-orbit.

Ferguson, Dale C.↗