Search NASA⌕ Search

SEARCH · Search NASA

Results for “Science 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 505 records · Page 28

Magnetospheric Multiscale Science Mission Profile and Operations

The Magnetospheric Multiscale (MMS) mission and operations are designed to provide the maximum reconnection science. The mission phases are chosen to investigate reconnection at the dayside magnetopause and in the magnetotail. At the dayside, the MMS orbits are chosen to maximize encounters with the magnetopause in regions where the probability of encountering the reconnection diffusion region is high. In the magnetotail, the orbits are chosen to maximize encounters with the neutral sheet, where reconnection is known to occur episodically. Although this targeting is limited by engineering constraints such as total available fuel, high science return orbits exist for launch dates over most of the year. The tetrahedral spacecraft formation has variable spacing to determine the optimum separations for the reconnection regions at the magnetopause and in the magnetotail. In the specific science regions of interest, the spacecraft are operated in a fast survey mode with continuous acquisition of burst mode data. Later, burst mode triggers and a ground-based scientist in the loop are used to determine the highest quality data to downlink for analysis. This operations scheme maximizes the science return for the mission.

Mission Design↗

Challenges of space medical operations and life sciences management

The Kennedy Space Center (KSC) has been the premier launch and landing site for America's space program since the early 1960s. Visitors are cognizant of space vehicles, processing facilities and launch pads which are treasured national resources. However, most are unaware of the unique organization which supports launch and landing activities and manages the center's occupational medicine, environmental health, ecological and environmental monitoring functions, as well as human and plant research programs. Management of this multifaceted organization can be complex because funding its different functions comes from a number of sources. Additionally the diverse disciplines of personnel present a special challenge in maintaining professional competencies while assuring efficiency in cyclical operations. This article explains the organization's structure and reviews some of its accomplishments.

Haddad, S. G.↗

A Concept of Operations for Earth Science Data Archive and Distribution in the Cloud

Science data systems can enable more comprehensive Earth system research by evolving to take advantage of advances in commercial computer technology services. Since their inception twenty five years ago, NASA's Earth Observing System Data and Information System (EOSDIS) Distributed Active Archive Centers (DAACs) have periodically evolved to utilize new technology and expand research using the exponential growth and diversity of Earth observations. Recently, with the advent of a maturing commercial compute services industry and upcoming high data volume missions such as the Surface Water and Ocean Topography (SWOT) mission and the NASA-Indian Space Research Organization Synthetic Aperture Radar (NISAR) mission, options were explored and a decision made to utilize commercial compute and storage services. This paper presents an overview of the concept of operations under development for the DAACs in the Cloud. We highlight the goals and expected advantages of utilizing Cloud services. We outline EOSDIS operations tenets and driving principles. A high-level view of EOSDIS system of systems target architecture serves as context for describing principle interactions. Concepts for key DAAC system and EOSDIS enterprise functions characterize automated end-to-end operations but mark nominal check and recovery points. Concepts are presented for managing Cloud resources, including organizational roles and responsibilities of the NASA project and DAAC personnel. Scenarios we use to further distinguish between what the system will do and what configuration and controls operators will have. Examples include interactions with data providers and data consumers with both in-cloud and on-premise facilities.

Moses, John F.↗

Zero to Integration in Eight Months, the Dawn Ground Data System Engineering Challenge

The Dawn Project has presented the Ground Data System (GDS) with technical challenges driven by cost and schedule constraints commonly associated with National Aeronautics and Space Administration (NASA) Discovery Projects. The Dawn mission consists of a new and exciting Deep Space partnership among: the Jet Propulsion Laboratory (JPL), manages the project and is responsible for flight operation; Orbital Sciences Corporation (OSC), is the spacecraft builder and is responsible for flight system test and integration; and the University of California, at Los Angeles (UCLA), is responsible for science planning and operations. As a cost-capped mission, one of Dawn's implementation strategies is to leverage from both flight and ground heritage. OSC's ground data system is used for flight system test and integration as part of the flight heritage strategy. Mission operations, however, are to be conducted with JPL's ground system. The system engineering challenge of dealing with two heterogeneous ground systems emerged immediately. During the first technical interchange meeting between the JPL's GDS Team and OSC's Flight Software Team, August 2003, the need to integrate the ground system with the flight software was brought to the table. This need was driven by the project's commitment to enable instrument engineering model integration in a spacecraft simulator environment, for both demonstration and risk mitigation purposes, by April 2004. This paper will describe the system engineering approach that was undertaken by JPL's GDS Team in order to meet the technical challenge within a non-negotiable eight-month schedule. Key to the success was adherence to fundamental systems engineering practices: decomposition of the project request into manageable requirements; integration of multiple ground disciplines and experts into a focused team effort; definition of a structured yet flexible development process; definition of an in-process risk reduction plan; and aggregation of the intermediate products to an integrated final product. In addition, this paper will highlight the role of lessons learned from the integration experience. The lessons learned from an early GDS deployment have served as the foundation for the design and implementation of the Dawn Ground Data System.

Ground Data System (GDS)↗

Medical operations and life sciences activities on space station

Space station health maintenance facilities, habitability, personnel, and research in the medical sciences and in biology are discussed. It is assumed that the space station structure will consist of several modules, each being consistent with Orbiter payload bay limits in size, weight, and center of gravity.

Johnson, P. C.↗

Telescience, an operational approach to science investigation

The NASA Science and Applications Information System, which is based on telescience and must provide remote interaction between information system services in space and on the ground, is discussed. An infrastructure of networked facilities and institutionally provided support services is being developed. The technologies involved with providing telescience capability are examined, including automated data management services, new data acquisition systems, user support environment for system access, and the capability to access heterogeneous data bases and computational facilities from remote locations.

Weiss, James R.↗

The NASA spring 1984 stratosphere-troposphere exchange experiment - Science objectives and operations

The first experiment of the Stratosphere-Troposphere Exchange Project to identify modes of transport during large-scale cyclogenesis is reviewed. The U-2 aircraft instrument payload is described and the flight paths are shown in relation to their meteorological situations. The procedures used to predict large-scale cyclogenesis and associated tropopause folding and to direct the aircraft are reviewed.

Russell, P. B.↗

Zero to Integration in Eight Months, the Dawn Ground Data System Engineering Challange

The Dawn Project has presented the Ground Data System (GDS) with technical challenges driven by cost and schedule constraints commonly associated with National Aeronautics and Space Administration (NASA) Discovery Projects. The Dawn mission consists of a new and exciting Deep Space partnership among: the Jet Propulsion Laboratory (JPL), responsible for project management and flight operations; Orbital Sciences Corporation (OSC), spacecraft builder and responsible for flight system test and integration; and the University of California, at Los Angeles (UCLA), responsible for science planning and operations. As a cost-capped mission, one of Dawn s implementation strategies is to leverage from both flight and ground heritage. OSC's ground data system is used for flight system test and integration as part of the flight heritage strategy. Mission operations, however, are to be conducted with JPL s ground system. The system engineering challenge of dealing with two heterogeneous ground systems emerged immediately. During the first technical interchange meeting between the JPL s GDS Team and OSC's Flight Software Team, August 2003, the need to integrate the ground system with the flight software was brought to the table. This need was driven by the project s commitment to enable instrument engineering model integration in a spacecraft simulator environment, for both demonstration and risk mitigation purposes, by April 2004. This paper will describe the system engineering approach that was undertaken by JPL's GDS Team in order to meet the technical challenge within a non-negotiable eight-month schedule. Key to the success was adherence to an overall systems engineering process and fundamental systems engineering practices: decomposition of the project request into manageable requirements; definition of a structured yet flexible development process; integration of multiple ground disciplines and experts into a focused team effort; in-process risk management; and aggregation of the intermediate products to an integrated final product. In addition, this paper will highlight the role of lessons learned from the integration experience. The lessons learned from an early GDS deployment have served as the foundation for the design and implementation of the Dawn Ground Data System.

systems engineering↗

Prospecting for Polar Volatiles: Results from the Resolve Field

Both the Moon and Mercury evidently host ice and other volatile compounds in cold traps at the planets poles. Determining the form, spatial distribution, and abundance of these volatiles at the lunar poles can help us understand how and when they were delivered and emplaced. This bears directly on the delivery of water and prebiotic compounds to the inner planets over the solar system s history, and also informs plans for utilizing the volatiles as resources for sustained human exploration as well as the commercial development of space. Temperature models and orbital data suggest near-surface volatile concentrations may exist at polar locations not strictly in permanent shadow. Remote operation of a robotic lunar rover mission for the 7-10 days of available sunlight would permit key questions to be answered. But such a short, quick-tempo mission has unique challenges and requires a new concept of operations. Both science and rover operations decisionmaking must be done in real time, requiring immediate situational awareness, data analysis, and decision support tools.

Elphic, Richard C.↗

International Earth Science Constellation Mission Operations Working Group September 27-29, 2016 Aqua Spring 2017 IAM Series

This Aqua Spring 2017 IAM Series powerpoint presentation will be presented at the MOWG meeting in Albuquerque, NM. Topics to be discussed are: recap Aqua 2016 IAM campaign maneuver results and post 2016 IAM MLT evolution; current DMU strategy; 2017 IAM campaign dates and planning; Aqua latest lifetime MLT team predictions. Susan Good is a contractor who supports David Tracewell in code 595 therefore this is being routed through 595. Eric Moyer, ESMO Deputy Project Manager-Technical has reviewed and approved this presentation.

Constellation↗