Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Mission Operations”

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 721 records · Page 40

Modular Software Interfaces for Revolutionary Flexibility in Space Operations

To make revolutionary improvements in exploration, space systems need to be flexible, realtime reconfigurable, and able to trade data transparently among themselves and mission operations. Onboard operations systems, space assembly coordination and EVA systems in exploration and construction all require real-time modular reconfigurability and data sharing. But NASA's current exploration systems are still largely legacies from hastily-developed, one-off Apollo-era practices. Today's rovers, vehicles, spacesuits, space stations, and instruments are not able to plug-and-play, Lego-like: into different combinations. Point-to-point dominates - individual suit to individual vehicle, individual instrument to rover. All are locally optimized, all unique, each of the data interfaces has been recoded for each possible combination. This will be an operations and maintenance nightmare in the much larger Project Constellation system of systems. This legacy approach does not scale to the hundreds of networked space components needed for space construction and for new, space-based approaches to Earth-Moon operations. By comparison, battlefield information management systems, which are considered critical to military force projection, have long since abandoned a point-to-point approach to systems integration. From a system-of-systems viewpoint, a clean-sheet redesign of the interfaces of all exploration systems is a necessary prerequisite before designing the interfaces of the individual exploration systems. Existing communications and Global Information Grid and middleware technologies are probably sufficient for command and control and information interfaces, with some hardware and time-delay modifications for space environments. NASA's future advanced space operations must also be information and data compatible with aerospace operations and surveillance systems being developed by other US Government agencies such as the Department of Homeland Security, Federal Aviation Administration and Department of Defense. This paper discusses fundamental system-of-systems infrastructure: approaches and architectures for modular plug-and-play software interfaces for revolutionary improvements in flexibility, modularity, robustness, ease of maintenance, reconfigurability, safety and productivity. Starting with middleware, databases, and mobile communications technologies, our technical challenges will be to apply these ideas to the requirements of constellations of space systems and to implement them initially on prototype space hardware. This is necessary to demonstrate an integrated information sharing architecture and services. It is a bottom-up approach, one that solves the problem of space operations data integration. Exploration demands uniform software mechanisms for application information interchange, and the corresponding uniformly available software services to enhance these mechanisms. We will examine the issues in plug-and-play, real-time-configurable systems, including common definition and management and tracking of data and information among many different space systems. Different field test approaches are discussed, including the use of the International Space Station and terrestrial analog mission operations at field sites.

Glass, Brian↗

Multinational Mars exploration

A primary concern in the formation of a multinational Mars-exploration program is that of technology transfer, which would be most acute in the U.S./U.S.S.R. case but would exist in lesser degree among other nations. Another concern is that of management-complexity, which could inflate total costs and substantially counteract the anticipated benefits of spreading program costs among a number of nations. It is presently suggested that these problems can be substantially reduced by having each nation become responsible for one (or more) complete flight system. Each nation's role in mission operations must be clear, and the cleanliness of interfaces among flight systems must carry over into mission operations.

Rea, Donald G.↗

NASA Sample Return Missions: Recovery Operations

The Utah Test and Training Range (UTTR), southwest of Salt Lake City, Utah, is the site of all NASA unmanned sample return missions. To date these missions include the Genesis solar wind samples (2004) and Stardust cometary and interstellar dust samples (2006). NASA’s OSIRIS-REx Mission will return its first asteroid sample at UTTR in 2023.

Pace, L. F.↗

End of Mission Considerations

While a great deal of effort goes into planning and executing successful mission operations, it is also important to consider the End of the Mission during the planning, design, and operations phases of any mission. Spacecraft and launch vehicles must be disposed of properly in order to limit the generation of orbital debris, and better preserve the orbital environment for all future missions. Figure 30-1 shows a 1990's projected growth of debris with and without the use of responsible disposal techniques. This requires early selection of a responsible disposal scenario, so that the necessary capabilities can be incorporated into the hardware designs. The mission operations must then be conducted in such a way as to preserve, and then actually perform, the planned, appropriate end of mission disposal.

Hull, Scott M.↗

Flight Team Development in Support of LCROSS - A Class D Mission

The LCROSS (Lunar Crater Observation and Sensing Satellite) project presented a number of challenges to the preparation for mission operations. A class D mission under NASA s risk tolerance scale, LCROSS was governed by a $79 million cost cap and a 29 month schedule from "authority to proceed" to flight readiness. LCROSS was NASA Ames Research Center s flagship mission in its return to spacecraft flight operations after many years of pursuing other strategic goals. As such, ARC needed to restore and update its mission support infrastructure, and in parallel, the LCROSS project had to newly define operational practices and to select and train a flight team combining experienced operators and staff from other arenas of ARC research. This paper describes the LCROSS flight team development process, which deeply involved team members in spacecraft and ground system design, implementation and test; leveraged collaborations with strategic partners; and conducted extensive testing and rehearsals that scaled in realism and complexity in coordination with ground system and spacecraft development. As a testament to the approach, LCROSS successfully met its full mission objectives, despite many in-flight challenges, with its impact on the lunar south pole on October 9, 2009.

Tompkins, Paul D.↗

Lessons learned - MO&DA at JPL

The issues of how to avoid future surprise growth in Mission Operations and Data Analysis (MO&DA) costs and how to minimize total MO&DA costs for planetary missions are discussed within the context of JPL mission operations support. It is argued that there is no simple, single solution: the entire Project life-cycle must be addressed. It is concluded that cost models that can predict both MO&DA cost as well as Ground System development costs are needed. The first year MO&DA budget plotted against the total of ground and flight systems developments is shown. In order to better recognize changes and control costs in general, a modified funding line item breakdown is recommended to distinguish between development costs (prelaunch and postlaunch) and MO&DA costs.

Handley, Thomas H., Jr.↗

Feasibility Study of Two Candidate Reaction Wheel/thruster Hybrid Control Architecture Designs for the Cassini Spacecraft

As the first spacecraft to achieve orbit at Saturn in 2004, Cassini has collected science data throughout its four-year prime mission (2004-08), and has since been approved for a first and second extended mission through 2017. Cassini carries a set of three "fixed" reaction wheels and a backup reaction wheel (reaction wheel #4) is mounted on top of an articulable platform. If necessary, this platform could be articulated to orient the backup reaction wheel with the degraded wheel. The reaction wheels are used primarily for attitude control when precise and stable pointing of a science instrument such as the narrow angle camera is required. In 2001-02, reaction wheel #3 exhibited signs of bearing cage instability. As a result, reaction wheel #4 was articulated to align with reaction wheel #3. Beginning in July 2003, Cassini was controlled using wheel #1, #2, and #4. From their first use in the spring of 2000 until today, reaction wheels #1 and #2 have accumulated more than3.5 billions revolutions each. As such, in spite of very carefully management of the wheel spin rates by the mission operation team, there are some observed increases in the drag torque of the wheels' bearings. Hence, the mission operations team must prepare for the contingency scenario in which the reaction wheel #1 (in addition to wheel #3) had degraded. In this hypothetical fault scenario, the two remaining reaction wheels (#2 and #4) will not be able to provide precise and stable three-axis control of the spacecraft. In this study, we evaluate the feasibility of controlling Cassini using the two remaining reaction wheels and four thrusters to meet the science pointing requirements for two key science operational modes: the Optical Remote Sensing and Downlink, Fields, Particles, & Waves operation modes. The performance (e.g., pointing control error, pointing stability, hydrazine consumption rate, etc.) of the hybrid controllers in both operations scenarios will be compared with those achieved using an all-thruster controller design. Strength and weaknesses of the hybrid control architecture are assessed quantitatively.

Cassini↗

Automated Spacecraft Communications Service Demonstration Using NASA's SCaN Testbed

The traditional paradigm for space mission operations relies on inefficient, highly scripted pre-planned activities between space communications & navigation service providers and user ground mission operations centers. Typically there is limited or non-existent automation capabilities on the user spacecraft for requesting space communications services, and on the provider network for request dispositioning and service provisioning. In the past, using these processes for space networks was sufficient with the relatively small number of user spacecraft requesting services. However, with an ever increasing number of satellites being launched to orbit, more complex event-driven science objectives, exploration missions involving collaborative platforms, and more distant missions, approaches that improve automation, flexibility and efficiency are needed. This paper describes NASA's recently completed on-orbit demonstration results of a new space communications service concept called User Initiated Service, and a discussion for infusing this innovation into operations.

waveforms↗

The Ensemble Canon

Ensemble is an open architecture for the development, integration, and deployment of mission operations software. Fundamentally, it is an adaptation of the Eclipse Rich Client Platform (RCP), a widespread, stable, and supported framework for component-based application development. By capitalizing on the maturity and availability of the Eclipse RCP, Ensemble offers a low-risk, politically neutral path towards a tighter integration of operations tools. The Ensemble project is a highly successful, ongoing collaboration among NASA Centers. Since 2004, the Ensemble project has supported the development of mission operations software for NASA's Exploration Systems, Science, and Space Operations Directorates.

applications programs (computers),↗

Operational and Mission Highlights (A Monthly Summary of Top Achievements, November 2022)

On November 16, Los Alamos National Laboratory Director Thom Mason answered questions from the Defense Nuclear Facilities Safety Board (DNFSB) at a public hearing in Santa Fe about the safety of operations at the Laboratory’s plutonium facility and the pit production mission. Mason participated on a panel along with National Nuclear Security Administration’s (NNSA) Administrator Jill Hruby, Deputy NNSA Administrator James McConnell, and NNSA Los Alamos Field Office Manager Ted Wyka.

98 NUCLEAR DISARMAMENT, SAFEGUARDS, AND PHYSICAL P↗

IUS/TUG orbital operations and mission support study. Volume 5: Cost estimates

The costing approach, methodology, and rationale utilized for generating cost data for composite IUS and space tug orbital operations are discussed. Summary cost estimates are given along with cost data initially derived for the IUS program and space tug program individually, and cost estimates for each work breakdown structure element.

Source record↗

The NEEMO Project: A Report on how NASA Utilizes the "Aquarius" Undersea Habitat as an Analog for Long-Duration Space Flight

NEEMO is the NASA Extreme Environment Mission Operations, a cooperative project between NASA and the National Oceanic and Atmospheric Administration (NOAA). NEEMO was created and is managed by the Mission Operations Directorate at the Johnson Space Center in Houston, Texas. On the NOAA side, the National Undersea Research Center (NURC) in Key Largo, FL, with the help of the University of North Carolina at Wilmington, manages and operates the Aquarius Program. NEEMO was developed by astronaut training specialists to utilize an undersea research habitat as a multi-objective mission analog for long-duration space flight. Each mission was designed to expose astronauts to extreme environments for training purposes and to research crew behavior, habitability, and space analog life sciences. All of this was done much in the model of a space mission utilizing specific crew procedures, mission rules and timelines. Objectives of the missions were very diverse and contained many of the typical space mission type activities such as EV As (also known as extra vehicular activities), in-habitat science and research, and educational, public outreach, and media events. Five missions, dubbed NEEMO 1-5, were conducted between October 2001 and July 2003, the longest of which (NEEMO 5) lasted 14 days.

Reagan, Marc↗

Automated Spacecraft Communications Service Demonstration Using NASA's SCaN Testbed

The traditional paradigm for space mission operations relies on inefficient, highly scripted pre-planned activities between space communications and navigation service providers and user ground mission operations centers. Typically there is limited or non-existent automation capabilities on the user spacecraft for requesting space communications services, and on the provider network for request dispositioning and service provisioning. In the past, using these processes for space networks was sufficient with the relatively small number of user spacecraft requesting services. However, with an ever increasing number of satellites being launched to orbit, more complex event-driven science objectives, exploration missions involving collaborative platforms, and more distant missions, approaches that improve automation, flexibility and efficiency are needed. This paper describes NASA's recently completed on-orbit demonstration results of a new space communications service concept called User Initiated Service, and a discussion for infusing this innovation into operations.

transmitters receivers↗

The MARS pathfinder end-to-end information system: A pathfinder for the development of future NASA planetary missions

The development of the Mars pathfinder is considered with emphasis on the End-to-End Information System (EEIS) development approach. The primary mission objective is to successfully develop and deliver a single flight system to the Martian surface, demonstrating entry, descent and landing. The EEIS is a set of functions distributed throughout the flight, ground and Mission Operation Systems (MOS) that inter-operate in order to control, collect, transport, process, store and analyze the uplink and downlink information flows of the mission. Coherence between the mission systems is achieved though the EEIS architecture. The key characteristics of the system are: a concurrent engineering approach for the development of flight, ground and mission operation systems; the fundamental EEIS architectural heuristics; a phased incremental EEIS development and test approach, and an EEIS design deploying flight, ground and MOS operability features, including integrated ground and flight based toolsets.

Cook, Richard A.↗

Report to the administrator by the NASA Aerospace Safety Advisory Panel on the Skylab program. Volume 1: Summary report

Contractor and NASA technical management for the development and manufacture of the Skylab modules is reviewed with emphasis on the following management controls: configuration and interface management; vendor control; and quality control of workmanship. A review of the modified two-stage Saturn V launch vehicle which focused on modifications to accommodate the Skylab payload; resolution of prior flight anomalies; and changes in personnel and management systems is presented along with an evaluation of the possible age-life and storage problems for the Saturn 1-B launch vehicle. The NASA program management's visibility and control of contractor operations, systems engineering and integration, the review process for the evaluation of design and flight hardware, and the planning process for mission operations are investigated. It is concluded that the technical management system for development and fabrication of the modules, spacecraft, and launch vehicles, the process of design and hardware acceptance reviews, and the risk assessment activities are satisfactory. It is indicated that checkout activity, integrated testing, and preparations for and execution of mission operation require management attention.

Source record↗

Reliability inputs to Mariner 9 data explosion

This paper describes the prelaunch and post-launch reliability functions which contributed to the success of the Mariner 9 spacecraft. Examples are included to illustrate how each reliability activity was a vital part of each phase of the project. Prelaunch reliability functions included: (1) establishing, negotiating, and monitoring system and subsystem requirements, (2) participating in spacecraft system and subsystem design/hardware reviews, (3) monitoring preparation of failure mode effects and criticality analyses (FMECA), (4) establishing and managing a problem failure reporting (PFR) system for the spacecraft and its support equipment, (5) monitoring electronic parts activities, and (6) participating in spacecraft reviews. Particular emphasis is placed on mission operations reliability assurance activities, which included: (1) spacecraft problem/failure reporting, (2) managing an integrating failure reporting system which covered all mission operations activities, (3) real-time analysis of spacecraft anomalies, and (4) risk assessment.

Macgregor, D. S.↗

Applied Virtual Reality Research and Applications at NASA/Marshall Space Flight Center

A Virtual Reality (VR) applications program has been under development at NASA/Marshall Space Flight Center (MSFC) since 1989. The objectives of the MSFC VR Applications Program are to develop, assess, validate, and utilize VR in hardware development, operations development and support, mission operations training and science training. Before this technology can be utilized with confidence in these applications, it must be validated for each particular class of application. That is, the precision and reliability with which it maps onto real settings and scenarios, representative of a class, must be calculated and assessed. The approach of the MSFC VR Applications Program is to develop and validate appropriate virtual environments and associated object kinematic and behavior attributes for specific classes of applications. These application-specific environments and associated simulations will be validated, where possible, through empirical comparisons with existing, accepted tools and methodologies. These validated VR analytical tools will then be available for use in the design and development of space systems and operations and in training and mission support systems. Specific validation studies for selected classes of applications have been completed or are currently underway. These include macro-ergonomic "control-room class" design analysis, Spacelab stowage reconfiguration training, a full-body micro-gravity functional reach simulator, and a gross anatomy teaching simulator. This paper describes the MSFC VR Applications Program and the validation studies.

Hale, Joseph P.↗