SEARCH · Search NASA

Results for “mission execution”

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 523 records · Page 29

All sources NASA NTRS DOE OSTI

NASA NTRSDate not supplied

Space Launch System Artemis I CubeSats: SmallSat Vanguards of Exploration, Science and Technology

When NASA’s Space Launch System (SLS) rocket launches in 2021 with the Orion crew vehicle, it will lay the foundation for NASA’s goal of landing the first woman and the next man on the Moon as part of the Artemis program. This first flight—Artemis I—will also mark a milestone for smallsats. Thirteen6U CubeSats are manifested on the Artemis I flight, the first fleet of CubeSats carried as a ride share opportunity to deep space.(NASA’s first CubeSats to deep space, the twin Mars Cube One [MarCO] spacecraft, were an integral part of the InSight Mars lander mission). The Artemis I CubeSat manifest represents a diverse collection of smallsats performing an array of science missions and technology demonstrations. Payloads from NASA, international partners, academia and industry will execute a variety of experiments. Several smallsats will perform lunar-focused missions that may return data that addresses Strategic Knowledge Gaps (SKGs) in the agency’s lunar exploration program. Indeed, the Artemis I CubeSats will be in the vanguard of the agency’s 21st-century lunar program. The Artemis I missions will produce data to support space radiation awareness,crewed landings and in-situ resource utilization, helping to support a sustained human lunar presence. Several of the Artemis I CubeSats are demonstrating new technologies, including propulsion capabilities. Among the Artemis I CubeSats are three selected through NASA’s Cube Quest Challenge, part of the Centennial Challenges program. These three missions will compete for prize money while meeting specific technical development goals. Payloads from the Japanese and Italian space agencies provide an early opportunity for international involvement in the Artemis program. Student involvement in almost half of the payloads allow STEM engagement with NASA’s Artemis program. The SLS Block 1 vehicle for the Artemis I flight is manufactured with several elements delivered to Kennedy Space Center (KSC) and being prepared for stacking and integration. The new-development of the program, the 212-footcore stage with its four RS-25 engines installed is currently at Stennis Space Center (SSC) for “green run” testing. Following the green run test campaign, the stage will ship to KSC, where it will be integrated with the rest of the vehicle, including the upper stage adapter, where the Artemis I smallsats will be housed.

Kimberly F Robinson↗

NASA NTRS1986

Intelligent user interface concept for space station

The space station computing system must interface with a wide variety of users, from highly skilled operations personnel to payload specialists from all over the world. The interface must accommodate a wide variety of operations from the space platform, ground control centers and from remote sites. As a result, there is a need for a robust, highly configurable and portable user interface that can accommodate the various space station missions. The concept of an intelligent user interface executive, written in Ada, that would support a number of advanced human interaction techniques, such as windowing, icons, color graphics, animation, and natural language processing is presented. The user interface would provide intelligent interaction by understanding the various user roles, the operations and mission, the current state of the environment and the current working context of the users. In addition, the intelligent user interface executive must be supported by a set of tools that would allow the executive to be easily configured and to allow rapid prototyping of proposed user dialogs. This capability would allow human engineering specialists acting in the role of dialog authors to define and validate various user scenarios. The set of tools required to support development of this intelligent human interface capability is discussed and the prototyping and validation efforts required for development of the Space Station's user interface are outlined.

Comer, Edward↗

NASA NTRS2020

Characterization of How CO2 Level May Impact Crew Performance Related to the HSIA Risk

Safety and mission critical anomalies are inevitable on NASA exploration missions. Delays and interruptions in communication with Earth-experts drives the requirement that crew resolve these anomalies on their own. The Human Factors and Behavioral Performance (HFBP) element of the NASA Human Research Program (HRP) recently stood-up the Human-System Integration Architecture (HSIA) risk. The specific risk statement is: “Given decreasing real-time ground support for execution of complex operations during future exploration missions, there is a possibility of adverse performance outcomes including that crew are unable to adequately respond to unanticipated critical malfunctions or detect safety critical procedural errors.” Reliable, on-board capabilities will need to support the crew - not only to resolve anomalies, but also to promote situation awareness (SA) and to reduce workload. Unfortunately, the present level of technological advancement limits the range of achievable intelligent support (Wu & Vera, 2019). The Human Capabilities Assessment for Autonomous Missions (HCAAM) projects were devised to identify how technology may benefit crew situation awareness and enhance crew trust in the intelligent systems. A suite of time-critical and complex exploration tasks have been identified (Holden et al., 2019) that may advance human-integration Concept of Operations (ConOps) development. This ConOps (a future HFBP directed task) along with standards and guidelines (Holden et al., 2019) may be used as the foundation for human-system requirements for a self-reliant crew. Spaceflight CO2 levels are elevated relative to terrestrial levels. Above 2.5 mmHg there is an increase in the incidence of crew headaches (Law et al., 2014) and Mission Control reports of mood and performance changes in the crew. The concern is that elevated CO2 effects may exacerbate the HSIA risk. Unfortunately, effects of higher concentrations of CO2 on performance decrements are not well established. The main goal of the current report is to identify how elevated CO2 impacts the HSIA risk. The approach taken is to trace the relationship between cognitive and motor abilities required for anomaly response with critical mission tasks and the level of technological advancement to support anomaly resolution to identify how elevated CO2 may impact the HSIA risk. The conclusion is that elevated CO2 could exacerbate the HSIA risk. Several research gaps are identified.

cognition↗

NASA NTRS1972

Analysis of advanced programs (Study 2.3). Volume 1: Executive summary

An analysis of advanced programs for space missions is presented. The subjects discussed are (1) alternate space shuttle configurations, (2) space transportation systems, (3) computer programs and methodology to estimate program cost implications of space vehicle program uncertainties, (4) vehicle synthesis program, (5) relative effectiveness of various proposals for space vehicles, and (6) cost analysis of solid propellant rocket engine program to support space shuttle vehicle.

Source record↗

NASA NTRS1979

Maneuver analysis

The maneuver design for Viking was accomplished in two phases. First, there was the preflight design and strategy development that was dictated by mission objectives and requirements. Orbit determination and maneuver execution accuracy statistics were used, together with propellant budget considerations, to determine specific maneuver requirements and strategies. The second phase of the maneuver design occurred in flight. The maneuver analyses that were performed in flight, the software that was employed, and the actual inflight results for the entire orbital phase of the nominal Viking Mission are described with emphasis on prelanding objectives and geometry considerations. The actual adaptive design and implementation of the maneuvers as the mission progressed are considered. This design process included the minimization of both propellant usage and the effects of maneuver execution errors, while complying with several mechanization constraints.

Mitchell, R. T.↗

NASA NTRS2003

An Autonomous Control System for an Intra-Vehicular Spacecraft Mobile Monitor Prototype

This paper presents an overview of an ongoing research and development effort at the NASA Ames Research Center to create an autonomous control system for an internal spacecraft autonomous mobile monitor. It primary functions are to provide crew support and perform intra- vehicular sensing activities by autonomously navigating onboard the International Space Station. We describe the mission roles and high-level functional requirements for an autonomous mobile monitor. The mobile monitor prototypes, of which two are operational and one is actively being designed, physical test facilities used to perform ground testing, including a 3D micro-gravity test facility, and simulators are briefly described. We provide an overview of the autonomy framework and describe each of its components, including those used for automated planning, goal-oriented task execution, diagnosis, and fault recovery. A sample mission test scenario is also described.

Dorais, Gregory A.↗

NASA NTRS2013

NASA's Space Launch System: One Vehicle, Many Destinations

The National Aeronautics and Space Administration's (NASA) Space Launch System (SLS) Program, managed at the Marshall Space Flight Center, is making progress toward delivering a new capability for exploration beyond Earth orbit (BEO). Developed with the goals of safety, affordability and sustainability in mind, SLS will start with 10 percent more thrust than the Saturn V rocket that launched astronauts to the Moon 40 years ago. From there it will evolve into the most powerful launch vehicle ever flown, via an upgrade approach that will provide building blocks for future space exploration and development. The International Space Exploration Coordination Group, representing 12 of the world's space agencies, has worked together to create the Global Exploration Roadmap, which outlines paths towards a human landing on Mars, beginning with capability-demonstrating missions to the Moon or an asteroid. The Roadmap and corresponding NASA research outline the requirements for reference missions for all three destinations. This paper will explore the requirements needed for missions to BEO destinations, and the capability of SLS to meet those requirements and enable those missions. It will explain how NASA will execute this development within flat budgetary guidelines by using existing engines assets and heritage technology, from the initial 70 metric ton (t) lift capability through a block upgrade approach to an evolved 130-t capability. The SLS will offer a robust way to transport international crews and the air, water, food, and equipment they would need for extended trips to asteroids, the Moon, and Mars. In addition, this paper will detail SLS's capability to support missions beyond the human exploration roadmap, including robotic precursor missions to other worlds or uniquely high-mass space operation facilities in Earth orbit. As this paper will explain, the SLS provides game-changing mass and volume lift capability that makes it enhancing or enabling for a variety of unprecedented human and robotic missions.

May, Todd A.↗

NASA NTRS1978

Simulation of mission timelines for the Spacelab program

The paper describes the structure of the Special Purpose Simulation Language (SPSL) designed to overcome certain problems encountered in the use of the General Purpose Simulation Language (GPSL) when applied to simulation and validation of Spacelab mission timelines. The current analysis system is GROPE (Ground Resource Operations Planning Executive), the main data base models of which are the ground operations model, the mission model, the resource model, and the traffic model. Some of the simulation problem areas are mentioned, and unique features of the SPSL are highlighted.

Roberts, J. S.↗

NASA NTRS2000

Autonomy Architectures for a Constellation of Spacecraft

Until the past few years, missions typically involved fairly large expensive spacecraft. Such missions have primarily favored using older proven technologies over more recently developed ones, and humans controlled spacecraft by manually generating detailed command sequences with low-level tools and then transmitting the sequences for subsequent execution on a spacecraft controller. This approach toward controlling a spacecraft has worked spectacularly on previous missions, but it has limitations deriving from communications restrictions - scheduling time to communicate with a particular spacecraft involves competing with other projects due to the limited number of deep space network antennae. This implies that a spacecraft can spend a long time just waiting whenever a command sequence fails. This is one reason why the New Millennium program has an objective to migrate parts of mission control tasks onboard a spacecraft to reduce wait time by making spacecraft more robust. The migrated software is called a "remote agent" and has 4 components: a mission manager to generate the high level goals, a planner/scheduler to turn goals into activities while reasoning about future expected situations, an executive/diagnostics engine to initiate and maintain activities while interpreting sensed events by reasoning about past and present situations, and a conventional real-time subsystem to interface with the spacecraft to implement an activity's primitive actions. In addition to needing remote planning and execution for isolated spacecraft, a trend toward multiple-spacecraft missions points to the need for remote distributed planning and execution. The past few years have seen missions with growing numbers of probes. Pathfinder has its rover (Sojourner), Cassini has its lander (Huygens), and the New Millenium Deep Space 3 (DS3) proposal involves a constellation of 3 spacecraft for interferometric mapping. This trend is expected to continue to progressively larger fleets. For example, one mission proposed to succeed DS3 would have 18 spacecraft flying in formation in order to detect earth-sized planets orbiting other stars. A proposed magnetospheric constellation would involve 5 to 500 spacecraft in Earth orbit to measure global phenomena within the magnetosphere. This work describes and compares three autonomy architectures for a system that continuously plans to control a fleet of spacecraft using collective mission goals instead of goals or command sequences for each spacecraft. A fleet of self-commanding spacecraft would autonomously coordinate itself to satisfy high level science and engineering goals in a changing partially-understood environment making feasible the operation of tens or even a hundred spacecraft (such as for interferometry or plasma physics missions). The easiest way to adapt autonomous spacecraft research to controlling constellations involves treating the constellation as a single spacecraft. Here one spacecraft directly controls the others as if they were connected. The controlling "master" spacecraft performs all autonomy reasoning, and the slaves only have real-time subsystems to execute the master's commands and transmit local telemetry/observations. The executive/diagnostics module starts actions and the master's real-time subsystem controls the action either locally or remotely through a slave. While the master/slave approach benefits from conceptual simplicity, it relies on an assumption that the master spacecraft's executive can continuously monitor the slaves' real-time subsystems, and this relies on high-bandwidth highly-reliable communications. Since unintended results occur fairly rarely, one way to relax the bandwidth requirements involves only monitoring unexpected events in spacecraft. Unfortunately, this disables the ability to monitor for unexpected events between spacecraft and leads to a host of coordination problems among the slaves. Also, failures in the communications system can result in losing slaves. The other two architectures improve robustness while reducing communications by progressively distributing more of the other three remote agent components across the constellation. In a teamwork architecture, all spacecraft have executives and real-time subsystems - only the leader has the planner/scheduler and mission manager. Finally, distributing all remote agent components leads to a peer-to-peer approach toward constellation control.

Barrett, Anthony↗

NASA NTRS2016

Monte Carlo Analysis as a Trajectory Design Driver for the TESS Mission

The Transiting Exoplanet Survey Satellite (TESS) will be injected into a highly eccentric Earth orbit and fly 3.5 phasing loops followed by a lunar flyby to enter a mission orbit with lunar 2:1 resonance. Through the phasing loops and mission orbit, the trajectory is significantly affected by lunar and solar gravity. We have developed a trajectory design to achieve the mission orbit and meet mission constraints, including eclipse avoidance and a 30-year geostationary orbit avoidance requirement. A parallelized Monte Carlo simulation was performed to validate the trajectory after injecting common perturbations, including launch dispersions, orbit determination errors, and maneuver execution errors. The Monte Carlo analysis helped identify mission risks and is used in the trajectory selection process.

trajectory↗

NASA NTRS2016

Monte Carlo Analysis as a Trajectory Design Driver for the Transiting Exoplanet Survey Satellite (TESS) Mission

monte carlo↗

NASA NTRS2018

Orion's Powered Flight Guidance Burn Options for Near Term Exploration Missions

NASA's Orion exploration spacecraft will fly more demanding mission profiles than previous NASA human flight spacecraft. Missions currently under development are destined for cislunar space. The EM-1 mission will fly unmanned to a Distant Retrograde Orbit (DRO) around the Moon. EM-2 will fly astronauts on a mission to the lunar vicinity. To fly these missions, Orion requires powered flight guidance that is more sophisticated than the orbital guidance flown on Apollo and the Space Shuttle. Orion's powered flight guidance software contains five burn guidance options. These five options are integrated into an architecture based on a proven shuttle heritage design, with a simple closed-loop guidance strategy. The architecture provides modularity, simplicity, versatility, and adaptability to future, yet-to-be-defined, exploration mission profiles. This paper provides a summary of the executive guidance architecture and details the five burn options to support both the nominal and abort profiles for the EM-1 and EM-2 missions.

Fill, Thomas↗

NASA NTRS2018

Orion Powered Flight Guidance Burn Options for Near Term Exploration

Fill, Tom↗

NASA NTRS2007

General Mission Analysis Tool (GMAT) Architectural Specification. Draft

Early in 2002, Goddard Space Flight Center (GSFC) began to identify requirements for the flight dynamics software needed to fly upcoming missions that use formations of spacecraft to collect data. These requirements ranged from low level modeling features to large scale interoperability requirements. In 2003 we began work on a system designed to meet these requirement; this system is GMAT. The General Mission Analysis Tool (GMAT) is a general purpose flight dynamics modeling tool built on open source principles. The GMAT code is written in C++, and uses modern C++ constructs extensively. GMAT can be run through either a fully functional Graphical User Interface (GUI) or as a command line program with minimal user feedback. The system is built and runs on Microsoft Windows, Linux, and Macintosh OS X platforms. The GMAT GUI is written using wxWidgets, a cross platform library of components that streamlines the development and extension of the user interface Flight dynamics modeling is performed in GMAT by building components that represent the players in the analysis problem that is being modeled. These components interact through the sequential execution of instructions, embodied in the GMAT Mission Sequence. A typical Mission Sequence will model the trajectories of a set of spacecraft evolving over time, calculating relevant parameters during this propagation, and maneuvering individual spacecraft to maintain a set of mission constraints as established by the mission analyst. All of the elements used in GMAT for mission analysis can be viewed in the GMAT GUI or through a custom scripting language. Analysis problems modeled in GMAT are saved as script files, and these files can be read into GMAT. When a script is read into the GMAT GUI, the corresponding user interface elements are constructed in the GMAT GUI. The GMAT system was developed from the ground up to run in a platform agnostic environment. The source code compiles on numerous different platforms, and is regularly exercised running on Windows, Linux and Macintosh computers by the development and analysis teams working on the project. The system can be run using either a graphical user interface, written using the open source wxWidgets framework, or from a text console. The GMAT source code was written using open source tools. GSFC has released the code using the NASA open source license.

Hughes, Steven P.↗

NASA NTRS2016

Promoting a Culture of Tailoring for Systems Engineering Policy Expectations

NASA's Marshall Space Flight Center (MSFC) has developed an integrated systems engineering approach to promote a culture of tailoring for program and project policy requirements. MSFC's culture encourages and supports tailoring, with an emphasis on risk-based decision making, for enhanced affordability and efficiency. MSFC's policy structure integrates the various Agency requirements into a single, streamlined implementation approach which serves as a "one-stop-shop" for our programs and projects to follow. The engineers gain an enhanced understanding of policy and technical expectations, as well as lesson's learned from MSFC's history of spaceflight and science missions, to enable them to make appropriate, risk-based tailoring recommendations. The tailoring approach utilizes a standard methodology to classify projects into predefined levels using selected mission and programmatic scaling factors related to risk tolerance. Policy requirements are then selectively applied and tailored, with appropriate rationale, and approved by the governing authorities, to support risk-informed decisions to achieve the desired cost and schedule efficiencies. The policy is further augmented by implementation tools and lifecycle planning aids which help promote and support the cultural shift toward more tailoring. The MSFC Customization Tool is an integrated spreadsheet that ties together everything that projects need to understand, navigate, and tailor the policy. It helps them classify their project, understand the intent of the requirements, determine their tailoring approach, and document the necessary governance approvals. It also helps them plan for and conduct technical reviews throughout the lifecycle. Policy tailoring is thus established as a normal part of project execution, with the tools provided to facilitate and enable the tailoring process. MSFC's approach to changing the culture emphasizes risk-based tailoring of policy to achieve increased flexibility, efficiency, and effectiveness in project execution, while maintaining appropriate rigor to ensure mission success.

Blankenship, Van A.↗

NASA NTRS2013

Execution-Error Modeling and Analysis of the GRAIL Spacecraft Pair

The GRAIL spacecraft, Ebb and Flow (aka GRAIL-A and GRAIL-B), completed their prime mission in June and extended mission in December 2012. The excellent performance of the propulsion and attitude control subsystems contributed significantly to the mission's success. In order to better understand this performance, the Navigation Team has analyzed and refined the execution-error models for delta-v maneuvers. There were enough maneuvers in the prime mission to form the basis of a model update that was used in the extended mission. This paper documents the evolution of the execution-error models along with the analysis and software used.

preprocessing↗

NASA NTRS2005

State-based models for planning and execution coordination

Many traditional planners are built on top of existing execution engines that were not necessarily intended to be operated by a planner. The Mission Data System has been designed from the onset to have both an execution and planning engine and provides a framework for producing state-based models that can be used to coordinate planning and execution. The models provide a basis for ensuring the consistency of assumptions made by the execution engine and planner, and the frameworks provide a basis for run time communications between the planner and execution engines.

planning↗

NASA NTRS2020

Europa Clipper Mission: Onward to Implementation!

Europa, the fourth largest moon of Jupiter, is believed to be one of the best places in the solar system to look for extant life beyond Earth, and the Europa Clipper Mission is preparing to investigate. Now entering the fifth year of life as a formal project, the Europa Clipper Mission has completed its major design phase and is preparing for implementation. The mission envisions sending a flight system, consisting of a spacecraft equipped with a payload of NASA-selected scientific instruments, to execute numerous flybys of Europa while in Jupiter orbit. The mission is being formulated and implemented by a joint Jet Propulsion Laboratory (JPL) and Applied Physics Laboratory (APL) Project team. At the Project Preliminary Design Review (PDR) in August 2018, it was determined that the unique integration of the REASON instrument’s antennas with the spacecraft’s solar arrays required additional time for maturity and review. The required maturity was demonstrated, and in June 2019 the Clipper Mission passed its Delta Preliminary Design Review, and formal confirmation for entry into Phase C was announced by NASA in August 2019. The earliest launch opportunity is now in July 2023, one year later than originally planned. The Project is now working toward its Critical Design Review in May 2020. This paper will describe the progress of the Europa Clipper Mission since January 2019, including maturation of the spacecraft, subsystem and instrument designs, the beginning of fabrication of engineering models and the first flight models, planning for the verification & validation phase, and planning for operations.

Jackson, Maddalena↗