Search NASA⌕ Search

SEARCH · Search NASA

Results for “multi mission”

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 253 records · Page 14
All sourcesNASA NTRSDOE OSTI
NASA NTRSDate not supplied

NASA Capture, Containment, and Return System: Bringing Mars Samples to Earth

The Capture, Containment, and Return System (CCRS) project is NASA’s last step in bringing back Mars samples. CCRS will close a decades-long multi-mission and multi-agency effort to bring Mars surface samples back to Earth for scientific studies. CCRS will launch in 2027 on the European Earth Return Orbiter (ERO) spacecraft, which will provide communications relay for the Mars Sample Return ground missions, Perseverance rover and the Sample Retrieval Lander (SRL) (to be launched in 2028). The main mission for CCRS begins when the first-ever orbital planetary capture operation occurs with CCRS catching and securing the Orbiting Sample (OS)in low Mars orbit. From this point, the system will perform additional "firsts": it will autonomously contain the OS with heat-shrink-fit, sterilize the outside surface, and assemble the Earth entry capsule, named Earth Entry System (EES), in orbit around Mars using a gantry mechanism. At approximately 2.8 Lunar distances from Earth, or 3-days from entry into Earth’s atmosphere, CCRS will open its micrometeoroid shield and release the EES on a ballistic trajectory to Earth. The EES is designed to be a fully passive system that will enter the atmosphere and land without parachute at the Utah Test and Training Range (UTTR).

Mars mission, Sample return, Mission design↗
NASA NTRS2016

Weathering the Storm: Unmanned Aircraft Systems in the Maritime, Atmospheric and Polar Environments

Unmanned systems have the potential to efficiently, effectively, economically, and safely bridge critical observation requirements in an environmentally friendly manner. As the United States Atmospheric, Marine and Arctic areas of interest expand and include hard-to-reach regions of the Earth (such as the Arctic and remote oceanic areas) optimizing unmanned capabilities will be needed to advance the United States science, technology and security efforts. Through increased multi-mission and multi-agency operations using improved inter-operable and autonomous unmanned systems, the research and operations communities will better collect environmental intelligence and better protect our country against hazardous weather, environmental, marine and polar hazards. This presentation will examine UAS (Unmanned Aircraft Systems) operations which includes developing a coordinated effort to maximize the efficiency and capabilities of unmanned systems across the federal government and research partners. Numerous intra- and inter-agency operational demonstrations and assessments have been made to verify and validated these UAS observations. The NASA-specific elements will consist of an overview of NASA UAVs (Unmanned Aerial Vehicles) available to science and recent missions.

Atmospheric↗
NASA NTRS2007

NASA Strategy to Safely Live and Work in the Space Radiation Environment

In space, astronauts are constantly bombarded with energetic particles. The goal of the National Aeronautics and Space Agency and the NASA Space Radiation Project is to ensure that astronauts can safely live and work in the space radiation environment. The space radiation environment poses both acute and chronic risks to crew health and safety, but unlike some other aspects of space travel, space radiation exposure has clinically relevant implications for the lifetime of the crew. Among the identified radiation risks are cancer, acute and late CNS damage, chronic and degenerative tissue decease, and acute radiation syndrome. The term "safely" means that risks are sufficiently understood such that acceptable limits on mission, post-mission and multi-mission consequences can be defined. The NASA Space Radiation Project strategy has several elements. The first element is to use a peer-reviewed research program to increase our mechanistic knowledge and genetic capabilities to develop tools for individual risk projection, thereby reducing our dependency on epidemiological data and population-based risk assessment. The second element is to use the NASA Space Radiation Laboratory to provide a ground-based facility to study the health effects/mechanisms of damage from space radiation exposure and the development and validation of biological models of risk, as well as methods for extrapolation to human risk. The third element is a risk modeling effort that integrates the results from research efforts into models of human risk to reduce uncertainties in predicting the identified radiation risks. To understand the biological basis for risk, we must also understand the physical aspects of the crew environment. Thus, the fourth element develops computer algorithms to predict radiation transport properties, evaluate integrated shielding technologies and provide design optimization recommendations for the design of human space systems. Understanding the risks and determining methods to mitigate the risks are keys to a successful radiation protection strategy.

Cucinotta, Francis A.↗
NASA NTRS2006

A Strategy to Safely Live and Work in the Space Radiation Environment

The goal of the National Aeronautics and Space Agency and the Space Radiation Project is to ensure that astronauts can safely live and work in the space radiation environment. The space radiation environment poses both acute and chronic risks to crew health and safety, but unlike some other aspects of space travel, space radiation exposure has clinically relevant implications for the lifetime of the crew. The term safely means that risks are sufficiently understood such that acceptable limits on mission, post-mission and multi-mission consequences (for example, excess lifetime fatal cancer risk) can be defined. The Space Radiation Project strategy has several elements. The first element is to use a peer-reviewed research program to increase our mechanistic knowledge and genetic capabilities to develop tools for individual risk projection, thereby reducing our dependency on epidemiological data and population-based risk assessment. The second element is to use the NASA Space Radiation Laboratory to provide a ground-based facility to study the understanding of health effects/mechanisms of damage from space radiation exposure and the development and validation of biological models of risk, as well as methods for extrapolation to human risk. The third element is a risk modeling effort that integrates the results from research efforts into models of human risk to reduce uncertainties in predicting risk of carcinogenesis, central nervous system damage, degenerative tissue disease, and acute radiation effects. To understand the biological basis for risk, we must also understand the physical aspects of the crew environment. Thus the fourth element develops computer codes to predict radiation transport properties, evaluate integrated shielding technologies and provide design optimization recommendations for the design of human space systems. Understanding the risks and determining methods to mitigate the risks are keys to a successful radiation protection strategy.

Corbin, Barbara J.↗
NASA NTRS2012

Integrated Data Modeling and Simulation on the Joint Polar Satellite System Program

The Joint Polar Satellite System is a modern, large-scale, complex, multi-mission aerospace program, and presents a variety of design, testing and operational challenges due to: (1) System Scope: multi-mission coordination, role, responsibility and accountability challenges stemming from porous/ill-defined system and organizational boundaries (including foreign policy interactions) (2) Degree of Concurrency: design, implementation, integration, verification and operation occurring simultaneously, at multiple scales in the system hierarchy (3) Multi-Decadal Lifecycle: technical obsolesce, reliability and sustainment concerns, including those related to organizational and industrial base. Additionally, these systems tend to become embedded in the broader societal infrastructure, resulting in new system stakeholders with perhaps different preferences (4) Barriers to Effective Communications: process and cultural issues that emerge due to geographic dispersion and as one spans boundaries including gov./contractor, NASA/Other USG, and international relationships.

Roberts, Christopher J.↗
NASA NTRSDate not supplied

Validation of a Probabilistic Continuity Assessment Method for Earth Observation Portfolios

With the increased reliance on spaceborne Earth observation data among the Earth science community and other end users, it is important that efforts are made to promote data continuity for a range of parameters of interest. Continuity gaps may occur between missions measuring like parameters due to mission development delays or early termination and introduce the potential of increased uncertainty for retrieved parameters. To inform portfolio-level decisions for Earth observing missions, Ivanco et al. developed a method that enables the assessment of the probability of continuity gaps for multi-mission architectures and provides a framework to assess this probability in the context of multiple scenarios that represent possible future states of the architecture [Ivanco et al., “A Scenario-Based Approach to Assess Continuity Gaps in Earth Observations,” IEEE Aerospace Conf., 2024]. While this method was previously applied to assess continuity gaps for a specific multi-mission architecture, it had not yet been validated with historical data. This paper outlines the process of validating the probabilistic gap assessment method by utilizing data obtained from past NASA Earth Science mission formulation documents and provides a discussion of the results and takeaways from the validation. Future areas of improvement pertaining to both the modeling and simulation methodologies and underlying assumptions are identified and discussed.

Katharine Burn↗
NASA NTRS2010

MPS Editor - An Integrated Sequencing Environment

In today's operations environment, the teams are smaller and need to be more efficient while still ensuring the safety and success of the mission. In addition, teams often begin working on a mission in its early development phases and continue on the team through actual operations. For these reasons the operations teams want to be presented with a software environment that integrates multiple needed software applications as well as providing them with context sensitive editing support for entering commands and sequences of commands. At Jet Propulsion Laboratory, the Multi-Mission Planning and Sequencing (MPS) Editor provided by the Multi-Mission Ground Systems and Services (MGSS) supports those operational needs.

Streiffert, Barbara A.↗
NASA NTRS2010

Planetary Image Geometry Library

The Planetary Image Geometry (PIG) library is a multi-mission library used for projecting images (EDRs, or Experiment Data Records) and managing their geometry for in-situ missions. A collection of models describes cameras and their articulation, allowing application programs such as mosaickers, terrain generators, and pointing correction tools to be written in a multi-mission manner, without any knowledge of parameters specific to the supported missions. Camera model objects allow transformation of image coordinates to and from view vectors in XYZ space. Pointing models, specific to each mission, describe how to orient the camera models based on telemetry or other information. Surface models describe the surface in general terms. Coordinate system objects manage the various coordinate systems involved in most missions. File objects manage access to metadata (labels, including telemetry information) in the input EDRs and RDRs (Reduced Data Records). Label models manage metadata information in output files. Site objects keep track of different locations where the spacecraft might be at a given time. Radiometry models allow correction of radiometry for an image. Mission objects contain basic mission parameters. Pointing adjustment ("nav") files allow pointing to be corrected. The object-oriented structure (C++) makes it easy to subclass just the pieces of the library that are truly mission-specific. Typically, this involves just the pointing model and coordinate systems, and parts of the file model. Once the library was developed (initially for Mars Polar Lander, MPL), adding new missions ranged from two days to a few months, resulting in significant cost savings as compared to rewriting all the application programs for each mission. Currently supported missions include Mars Pathfinder (MPF), MPL, Mars Exploration Rover (MER), Phoenix, and Mars Science Lab (MSL). Applications based on this library create the majority of operational image RDRs for those missions. A Java wrapper around the library allows parts of it to be used from Java code (via a native JNI interface). Future conversions of all or part of the library to Java are contemplated.

Deen, Robert C.↗
NASA NTRS2014

Using Modern Methodologies with Maintenance Software

Jet Propulsion Laboratory uses multi-mission software produced by the Mission Planning and Sequencing (MPS) team to process, simulate, translate, and package the commands that are sent to a spacecraft. MPS works under the auspices of the Multi-Mission Ground Systems and Services (MGSS). This software consists of nineteen applications that are in maintenance. The MPS software is classified as either class B (mission critical) or class C (mission important). The scheduling of tasks is difficult because mission needs must be addressed prior to performing any other tasks and those needs often spring up unexpectedly. Keeping track of the tasks that everyone is working on is also difficult because each person is working on a different software component. Recently the group adopted the Scrum methodology for planning and scheduling tasks. Scrum is one of the newer methodologies typically used in agile development. In the Scrum development environment, teams pick their tasks that are to be completed within a sprint based on priority. The team specifies the sprint length usually a month or less. Scrum is typically used for new development of one application. In the Scrum methodology there is a scrum master who is a facilitator who tries to make sure that everything moves smoothly, a product owner who represents the user(s) of the software and the team. MPS is not the traditional environment for the Scrum methodology. MPS has many software applications in maintenance, team members who are working on disparate applications, many users, and is interruptible based on mission needs, issues and requirements. In order to use scrum, the methodology needed adaptation to MPS. Scrum was chosen because it is adaptable. This paper is about the development of the process for using scrum, a new development methodology, with a team that works on disparate interruptible tasks on multiple software applications.

Scrum↗
NASA NTRS2015

Deployment Technology of a Heliogyro Solar Sail for Long Duration Propulsion

Interplanetary, multi-mission, station-keeping capabilities will require that a spacecraft employ a highly efficient propulsion-navigation system. The majority of space propulsion systems are fuel-based and require the vehicle to carry and consume fuel as part of the mission. Once the fuel is consumed, the mission is set, thereby limiting the potential capability. Alternatively, a method that derives its acceleration and direction from solar photon pressure using a solar sail would eliminate the requirement of onboard fuel to meet mission objectives. MacNeal theorized that the heliogyro-configured solar sail architecture would be lighter, less complex, cheaper, and less risky to deploy a large sail area versus a masted sail. As sail size increases, the masted sail requires longer booms resulting in increased mass, and chaotic uncontrollable deployment. With a heliogyro, the sail membrane is stowed as a roll of thin film forming a blade when deployed that can extend up to kilometers. Thus, a benefit of using a heliogyro-configured solar sail propulsion technology is the mission scalability as compared to masted versions, which are size constrained. Studies have shown that interplanetary travel is achievable by the heliogyro solar sail concept. Heliogyro solar sail concept also enables multi-mission missions such as sample returns, and supply transportation from Earth to Mars as well as station-keeping missions to provide enhanced warning of solar storm. This paper describes deployment technology being developed at NASA Langley Research Center to deploy and control the center-of-mass/center-of-pressure using a twin bladed heliogyro solar sail 6-unit (6U) CubeSat. The 6U comprises 2x2U blade deployers and 2U for payload. The 2U blade deployers can be mounted to 6U or larger scaled systems to serve as a non-chemical in-space propulsion system. A single solar sail blade length is estimated to be 2.4 km with a total area from two blades of 720 m2; total allowable weight of a 6U CubeSat is approximately 8 kg. This makes the theoretical characteristic acceleration of approximately 0.75 mm/s2 at I AU (astronomical unit), when compared to IKAROS (0.005 mm/s2) and NanoSail-D (0.02 mm/s2).

Peerawan, Wiwattananon↗
NASA NTRS1981

Sea based support aircraft alternatives

Multi-mission, CTOL, STOL and V/STOL aircraft concepts were sized for the Navy ASW/ASUW missions and comparatively evaluated. Initially, technology levels in the areas of lift, control systems, propulsion, advanced materials and avionics were established for the early 1990's. The aircraft were compared to determine the impact of multi-mission requirements, operational considerations, chiefly takeoff mode, as well as the technology advancements. Results presented include performance envelopes, weight statements, growth factors, impact of technology on weight reduction and the impact of design constraints.

Priestley, R. T.↗
NASA NTRS1981

Generic functional requirements for a NASA general-purpose data base management system

Generic functional requirements for a general-purpose, multi-mission data base management system (DBMS) for application to remotely sensed scientific data bases are detailed. The motivation for utilizing DBMS technology in this environment is explained. The major requirements include: (1) a DBMS for scientific observational data; (2) a multi-mission capability; (3) user-friendly; (4) extensive and integrated information about data; (5) robust languages for defining data structures and formats; (6) scientific data types and structures; (7) flexible physical access mechanisms; (8) ways of representing spatial relationships; (9) a high level nonprocedural interactive query and data manipulation language; (10) data base maintenance utilities; (11) high rate input/output and large data volume storage; and adaptability to a distributed data base and/or data base machine configuration. Detailed functions are specified in a top-down hierarchic fashion. Implementation, performance, and support requirements are also given.

Lohman, G. M.↗
NASA NTRS2002

REACH: Real-Time Data Awareness in Multi-Spacecraft Missions

NASA's Advanced Architectures and Automation Branch at the Goddard Space Flight Center (Code 588) saw the potential to reduce the cost of constellation missions by creating new user interfaces to the ground system health-and-safety data. The goal is to enable a small Flight Operations Team (FOT) to remain aware and responsive to the increased amount of ground system information in a multi-spacecraft environment. Rather than abandon the tried and true, these interfaces were developed to run alongside existing ground system software to provide additional support to the FOT. These new user interfaces have been combined in a tool called REACH. REACH-the Real-time Evaluation and Analysis of Consolidated Health-is a software product that uses advanced visualization techniques to make spacecraft anomalies easy to spot, no matter how many spacecraft are in the constellation. REACH reads numerous real-time streams of data from the ground system(s) and displays synthesized information to the FOT such that anomalies are easy to pick out and investigate.

Maks, Lori↗
NASA NTRS2017

NASA's Current Initiative to Improve Operations Planning

As a follow-on to the Technical Capability Assessment Team, in 2015 NASA began seven Agency-wide efforts to seek out opportunities to improve the effectiveness of NASA operations. One of these technical teams is the Mission Operations Planning team, charged with increasing interactions and efficiency for planning of mission activities. That team is chaired by the author with representatives from eight other centers across the Agency. As the strategic architects for the vision of agency-wide ops planning, the team has identified a number of new initiatives and techniques to improve planning, including: breaking down walls within centers which obstruct multi-mission planning; breaking down walls agency-wide which obstruct the sharing of ops planning lessons and capabilities; strengthening the community of practice of ops planning capability developers; establishing best practices for a variety of types of ops planning; defining standards for activity plans and timelines, and plan inputs; and recommending the presence of "multi-mission operations champions" within each center to implement these recommendations into the next decade.

Seal, David↗
NASA NTRS2007

Automatic Command Sequence Generation

Automatic Sequence Generator (Autogen) Version 3.0 software automatically generates command sequences for the Mars Reconnaissance Orbiter (MRO) and several other JPL spacecraft operated by the multi-mission support team. Autogen uses standard JPL sequencing tools like APGEN, ASP, SEQGEN, and the DOM database to automate the generation of uplink command products, Spacecraft Command Message Format (SCMF) files, and the corresponding ground command products, DSN Keywords Files (DKF). Autogen supports all the major multi-mission mission phases including the cruise, aerobraking, mapping/science, and relay mission phases. Autogen is a Perl script, which functions within the mission operations UNIX environment. It consists of two parts: a set of model files and the autogen Perl script. Autogen encodes the behaviors of the system into a model and encodes algorithms for context sensitive customizations of the modeled behaviors. The model includes knowledge of different mission phases and how the resultant command products must differ for these phases. The executable software portion of Autogen, automates the setup and use of APGEN for constructing a spacecraft activity sequence file (SASF). The setup includes file retrieval through the DOM (Distributed Object Manager), an object database used to store project files. This step retrieves all the needed input files for generating the command products. Depending on the mission phase, Autogen also uses the ASP (Automated Sequence Processor) and SEQGEN to generate the command product sent to the spacecraft. Autogen also provides the means for customizing sequences through the use of configuration files. By automating the majority of the sequencing generation process, Autogen eliminates many sequence generation errors commonly introduced by manually constructing spacecraft command sequences. Through the layering of commands into the sequence by a series of scheduling algorithms, users are able to rapidly and reliably construct the desired uplink command products. With the aid of Autogen, sequences may be produced in a matter of hours instead of weeks, with a significant reduction in the number of people on the sequence team. As a result, the uplink product generation process is significantly streamlined and mission risk is significantly reduced. Autogen is used for operations of MRO, Mars Global Surveyor (MGS), Mars Exploration Rover (MER), Mars Odyssey, and will be used for operations of Phoenix. Autogen Version 3.0 is the operational version of Autogen including the MRO adaptation for the cruise mission phase, and was also used for development of the aerobraking and mapping mission phases for MRO.

Fisher, Forest↗
NASA NTRS2002

Low Energy Calibration for Multi-Spacecraft Missions

Instruments designed for low-energy measurements have their own specific challenges in design and calibration. They may have a non-uniform response at lower energies and may encounter sources of error due to stray fields in the lab and in flight. In addition, the particle source beams for testing and calibration have to be spatially broad, monoenergetic, and monodirectional at the lower energies. Again, the same challenges for the uniform response and removal of stray fields comes into play for these sources. We will discuss our experiences in the low energy calibration of recent flight in-situ instruments and conclude with ideas for multi-spacecraft instruments calibrations. This discussion with others will support the ISSI Scientific Report on Calibration Techniques for In-Situ Plasma Instrumentation.

Coffey, Victoria↗
NASA NTRS2010

MOS 2.0: The Next Generation in Mission Operations Systems

A Mission Operations System (MOS) or Ground System constitutes that portion of an overall space mission Enterprise that resides here on Earth. Over the past two decades, technological innovations in computing and software technologies have allowed an MOS to support ever more complex missions while consuming a decreasing fraction of Project development budgets. Despite (or perhaps, because of) such successes, it is routine to hear concerns about the cost of MOS development. At the same time, demand continues for Ground Systems which will plan more spacecraft activities with fewer commanding errors, provide scientists and engineers with more autonomous functionality, process and manage larger and more complex data more quickly, all while requiring fewer people to develop, deploy, operate and maintain them. One successful approach to such concerns over this period is a multimission approach, based on the reuse of portions (most often software) developed and used in previous missions. The Advanced Multi-Mission Operations System (AMMOS), developed for deep-space science missions, is one successful example of such an approach. Like many computing-intensive systems, it has grown up in a near-organic fashion from a relatively simple set of tools into a complexly interrelated set of capabilities. Such systems, like a city lacking any concept of urban planning, can and will grow in ways that are neither efficient nor particularly easy to sustain. To meet the growing demands and unyielding constraints placed on ground systems, a new approach is necessary. Under the aegis of a multi-year effort to revitalize the AMMOS's multimission operations capabilities, we are utilizing modern practices in systems architecting and model-based engineering to create the next step in Ground Systems: MOS 2.0. In this paper we outline our work (ongoing and planned) to architect and design a multimission MOS 2.0, describe our goals and measureable objectives, and discuss some of the benefits that this top-down, architectural approach holds for creating a more flexible and capable MOS for Missions while holding the line on cost.

ground systems↗