SEARCH · Engineering Papers

Results for “Mission Timeline”

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 19 records

All sources NASA NTRS DOE OSTI

NASA NTRSDate not supplied

Using Open Standards and NASA Open Source Simulation Tools to Model Artemis Base Camp Mission Timelines

The United States’ National Aeronautics and Space Administration (NASA) has announced that the Artemis Program will return humans to the Moon, establishing a persistent presence with the Artemis Base Camp (ABC), and extend human exploration to Mars. The NASA Exploration Systems Simulations (NExSyS) team at NASA’s Johnson Space Center is using internationally developed simulation interoperability standards and NASA open source simulation tools to support Artemis concept, analysis, designs, development, training, and ultimately operations. The NExSyS team has been tasked to support early ABC architecture and mission analysis using mission time lines developed by the crew operations mission planning team. The NExSyS team is developing a distributed simulation framework with initial Artemis element implementations to model the ABC mission timelines using the international simulation interoperability standard High Level Architecture (HLA), the Simulation Interoperability Standards Organization’s Space Reference Federation Object Model (SpaceFOM), the NASA open source Trick Simulation Environment, and another NASA open source interface package called TrickHLA. The ABC architecture is composed of a number of key surface elements and resources. Some examples of modeled elements (also known as entities) are landers, habitats, rovers, logistics carriers, and astronauts. Some examples of modeled transferable and consumable resources are power, water, oxygen, nitrogen, scientific samples, and food. These entities and resources are modeled in a collection of individual simulations called Federates. A coordinated collection of interoperable federates is called a Federation and when these federates are tied together in a coordinated simulation run, it is referred to as a Federation Execution. The federates communicate through HLA using data exchange formats defined by a collection of machine readable files called Federation Object Models (FOMs). These FOM files are based on extensions to the SpaceFOM. This enables the instantiation and sharing of objects and interactions between federates in the federation. These provide for entity and resource tracking, object transfer, and data collection. Federate interactions are used to trigger events and notify federates of entity or resource transfers. For the initial implementation, the constituent federates are Trick-based simulations that use TrickHLA to provide the required HLA-base interoperability. These Trick-based simulations provide the required modeling for the individual Artemis elements along with the associated element resources. These federates provide a means to explore traverses between surface elements and exploration sites as scheduled in a mission timeline and explore the affects traverse times have on the overall mission timeline. The mission time lines are modeled using a Trick input file event handling capabilities. Each timeline operation is handled as individual simulation events, and triggered based on previous event status, time of operation, and simulated task completions. In addition, the ABC Federation can be used to perform Monte Carlo analysis. The Monte Carlo tool can vary the inputs, timings, and malfunctions to show how various contingencies in the mission can affect the mission timeline.

Keaton Craig Dodd↗

NASA NTRS2012

The Ice, Cloud, and land Elevation Satellite (ICESat) Summary Mission Timeline and Performance Relative to Pre-Launch Mission Success Criteria

The Ice, Cloud and land Elevation Satellite (ICESat) mission was conceived, primarily, to quantify the spatial and temporal variations in the topography of the Greenland and Antarctic ice sheets. It carried on board the Geoscience Laser Altimeter System (GLAS), which measured the round-trip travel time of a laser pulse emitted from the satellite to the surface of the Earth and back. Each range derived from these measurements was combined with precise, concurrent orbit and pointing information to determine the location of the laser spot centroid on the Earth. By developing a time series of precise topographic maps for each ice sheet, changes in their surface elevations can be used to infer their mass balances.

Webb, Charles E.↗

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 NTRS2022

Integrating Mission Timelines and Procedures to Enhance Situational Awareness in Human Spaceflight Operations

Future human spaceflight missions to the Moon, Mars, and beyond will have significant transmission delays and reduced communications bandwidth compared to operations in Low Earth Orbit, requiring increased crew autonomy due to the limited availability of real-time support from Mission Control Center (MCC). In this paper, we argue for the development of technology to enhance situational awareness (SA) for a remote MCC and astronauts onboard the vehicle, describe a usability study conducted towards this aim, and identify key usability features for the design of future integrated timeline tools. By tightly integrating timelines and procedures, future crew systems can predict future constraint violations, suggest resolutions to these violations, and ultimately support more successful missions.

User experience↗

NASA NTRSDate not supplied

Integrating Mission Timelines and Procedures to Enhance Situational Awareness in Human Spaceflight Operations

user experience↗

NASA NTRS1995

Electronic collection system for spacelab mission timeline requirements

This paper describes the Functional Objective Requirements Collection System (FORCS) software tool that has been developed for use by Principal Investigators (PI's) and Payload Element Developers (PED's) on their own personal computers to develop on-orbit timelining requirements for their payloads. The FORCS tool can be used either in a totally stand-alone mode, storing the information in a local file on the user's personal computer hard disk or in a remote mode where the user's computer is linked to a host computer containing the integrated database of the timeline requirements for all of the payloads on a mission. There are a number of features incorporated in the FORCS software to assist the user. The user may move freely back and forth between the various forms for inputting the data. Several methods are used to input the information, depending on the type of the information. These methods range from filling in text boxes, using check boxes and radio buttons, to inputting information into a spreadsheet format. There are automated features provided to assist in developing the proper format for the data, ranging from limit checking on some of the parameters to automatic conversion of different formats of time data inputs to the one standard format used for the timeline scheduling software.

Lindberg, James P.↗

NASA NTRS1992

SEI reference mission

Presentation on the Space Exploration Initiative (SEI). The goal of the reference mission is to expand the human presence to the moon and Mars in order to enhance our understanding of the universe, to seek terrestrial benefits from this exploration, and to establish the beginnings of a sustainable spacefaring civilization. Topics covered here include a phased definition of initial programmatic milestones and follow-on capabilities, near-term mission strategy, a lunar mission timeline, and a Mars mission timeline.

Dwayne Weary↗

NASA NTRS2015

Integrated Medical Model (IMM) 4.0 Enhanced Functionalities

The Integrated Medical Model is a probabilistic simulation model that uses input data on 100 medical conditions to simulate expected medical events, the resources required to treat, and the resulting impact to the mission for specific crew and mission characteristics. The newest development version of IMM, IMM v4.0, adds capabilities that remove some of the conservative assumptions that underlie the current operational version, IMM v3. While IMM v3 provides the framework to simulate whether a medical event occurred, IMMv4 also simulates when the event occurred during a mission timeline. This allows for more accurate estimation of mission time lost and resource utilization. In addition to the mission timeline, IMMv4.0 features two enhancements that address IMM v3 assumptions regarding medical event treatment. Medical events in IMMv3 are assigned the untreated outcome if any resource required to treat the event was unavailable. IMMv4 allows for partially treated outcomes that are proportional to the amount of required resources available, thus removing the dichotomous treatment assumption. An additional capability IMMv4 is to use an alternative medical resource when the primary resource assigned to the condition is depleted, more accurately reflecting the real-world system. The additional capabilities defining IMM v4.0the mission timeline, partial treatment, and alternate drug result in more realistic predicted mission outcomes. The primary model outcomes of IMM v4.0 for the ISS6 mission, including mission time lost, probability of evacuation, and probability of loss of crew life, are be compared to those produced by the current operational version of IMM to showcase enhanced prediction capabilities.

Spae Adaptation Syndrome↗

NASA NTRS2012

Timeline-Based Mission Operations Architecture: An Overview

Some of the challenges in developing a mission operations system and operating a mission can be traced back to the challenge of integrating a mission operations system from its many components and to the challenge of maintaining consistent and accountable information throughout the operations processes. An important contributing factor to both of these challenges is the file-centric nature of today's systems. In this paper, we provide an overview of these challenges and argue the need to move toward an information-centric mission operations system. We propose an information representation called Timeline as an approach to enable such a move, and we provide an overview of a Timeline-based Mission Operations System architecture.

Chung, Seung H.↗

NASA NTRS1971

The effect of mission attitude timelines on consumables requirements for the proposed shuttle orbiter heat rejection systems

Effect of mission attitude timelines on consumables requirements for proposed shuttle orbiter heat rejection systems

Cunningham, J. E.↗

NASA NTRS2011

Full Mission Astronaut Radiation Exposure Assessments for Long Duration Lunar Surface Missions

Risk to astronauts due to ionizing radiation exposure is a primary concern for missions beyond Low Earth Orbit (LEO) and will drive mission architecture requirements, mission timelines, and operational practices. For short missions, radiation risk is dominated by the possibility of a large Solar Particle Event (SPE). Longer duration missions have both SPE and Galactic Cosmic Ray (GCR) risks. SPE exposure can contribute significantly toward cancer induction in combination with GCR. As mission duration increases, mitigation strategies must address the combined risks from SPE and GCR exposure. In this paper, full mission exposure assessments were performed for the proposed long duration lunar surface mission scenarios. In order to accomplish these assessments, previously developed radiation shielding models for a proposed lunar habitat and rover were utilized. End-to-End mission exposure assessments were performed by first calculating exposure rates for locations in the habitat, rover, and during Extra-Vehicular Activities (EVA). Subsequently, total mission exposures were evaluated for the proposed timelines. Mission exposure results, assessed in terms of effective dose, are presented for the proposed timelines and recommendations are made for improved astronaut shielding and safer operational practices.

Adamczyk, Anne↗

NASA NTRS2014

Gas Chromatograph Method Optimization Trade Study for RESOLVE: 20-meter Column v. 8-meter Column

RESOLVE is the payload on a Class D mission, Resource Prospector, which will prospect for water and other volatile resources at a lunar pole. The RESOLVE payload's primary scientific purpose includes determining the presence of water on the moon in the lunar regolith. In order to detect the water, a gas chromatograph (GC) will be used in conjunction with a mass spectrometer (MS). The goal of the experiment was to compare two GC column lengths and recommend which would be best for RESOLVE's purposes. Throughout the experiment, an Inficon Fusion GC and an Inficon Micro GC 3000 were used. The Fusion had a 20m long column with 0.25mm internal diameter (Id). The Micro GC 3000 had an 8m long column with a 0.32mm Id. By varying the column temperature and column pressure while holding all other parameters constant, the ideal conditions for testing with each column length in their individual instrument configurations were determined. The criteria used for determining the optimal method parameters included (in no particular order) (1) quickest run time, (2) peak sharpness, and (3) peak separation. After testing numerous combinations of temperature and pressure, the parameters for each column length that resulted in the most optimal data given my three criteria were selected. The ideal temperature and pressure for the 20m column were 95 C and 50psig. At this temperature and pressure, the peaks were separated and the retention times were shorter compared to other combinations. The Inficon Micro GC 3000 operated better at lower temperature mainly due to the shorter 8m column. The optimal column temperature and pressure were 70 C and 30psig. The Inficon Micro GC 3000 8m column had worse separation than the Inficon Fusion 20m column, but was able to separate water within a shorter run time. Therefore, the most significant tradeoff between the two column lengths was peak separation of the sample versus run time. After performing several tests, it was concluded that better detection via good peak separation with a longer run time is a better asset than moderate peak separation with a shorter run time. Even given that RESOLVE is highly interested in water and that mission timeline is of significant importance given the short seven-to-ten-day mission timeline, worse detection with an 8m column may lead to overlooking other substances existing on the moon that could advance planetary science. Thus, I recommend the 20m column. However, if mission timeline and water separation are deemed the highest priority, the 8m column should be selected due to its ability to separate water within a shorter run time than the 20m column.

Column↗

NASA NTRS2007

Mission Analysis for the Don Quijote Phase-A Study

The Don Quijote Phase-A study is a definition study funded by ESA and devoted to the analysis of the possibilities to deflect a Near Earth Object (NEO) in the range of 300-800 m diameter. DEIMOS Space S.L. and EADS Astrium have teamed up within this study to form one of the three consortia that have analyzed these aspects for ESA. Target asteroids for the mission are 1989 ML, 2002 AT4 and Apophis. This paper presents the mission analysis activities within the consortium providing: low-thrust interplanetary rendezvous Orbiter trajectories to the target asteroids, ballistic interplanetary trajectories for the Impactor, Orbiter arrival description at the asteroids, Orbiter stable orbits characterization at the asteroid, deflection determination by means of a Radio Science Experiment (RSE) as well as the mission timelines and overall mission scenarios.

Cano, Juan L.↗

NASA NTRS2016

In the Hot Seat: STS-115 Lightning Strike Stand Down Debate - NASA Case Study

There is no way the PIC's could have seen any current' was the gist of Mike Griffin's assessment. Griffin was the NASA Administrator at the time. The buck stopped at his desk. Holding a napkin out to Pat Lampton, Griffin showed Lampton the calculations he'd made over dinner that predicted that the Pyrotechnic Initiator Controllers (PIC's) at the base of the Space Shuttle Solid Rocket Boosters (SRBs) were fine. A lightning strike the day before, the worst ever experienced with a Space Shuttle on the launch pad, caused a halt to the launch count down as technicians, engineers, and managers scrambled identify any damage to the launch system. SRB technicians and engineers assessed the data against their Lightning Strike Re-Test Requirements, determining that all but one of the requirements could be checked if they resumed the countdown. For the one remaining requirement, testing the integrity of the PIC's would require 96 hours to set up, test, and reassemble. The engineers were convinced that there was no way to do calculations to show the PIC's were okay. The only option was to stand down. It was SRB Deputy Project Manager (PM) Pat Lampton's responsibility to decide what the SRB project position needed to be to certify that their hardware was safe to fly. He had to communicate that decision to the Mission Management Team (MMT) as a Go or No Go position to resume the count down. If the answer was Go they could still meet a delayed, but acceptable launch schedule. If the answer was No Go, rescheduling the launch would be a grueling shuffling of hardware, personnel, and mission timelines to accommodate Russian missions to the Space Station, supplies for the launch, and personnel manning launch operations. On top of that, Hurricane Ernesto was spinning off the coast of Florida, threatening the need for the Shuttle to roll back to the hangar if they waited too long.

Kummer, Lizette↗

NASA NTRS2015

Systems Engineering Lessons Learned for Class D Missions

One of NASA's goals within human exploration is to determine how to get humans to Mars safely and to live and work on the Martian surface. To accomplish this goal, several smaller missions act as stepping-stones to the larger end goal. NASA uses these smaller missions to develop new technologies and learn about how to survive outside of Low Earth Orbit for long periods. Additionally, keeping a cadence of these missions allows the team to maintain proficiency in the complex art of bringing spacecraft to fruition. Many of these smaller missions are robotic in nature and have smaller timescales, whereas there are others that involve crew and have longer mission timelines. Given the timelines associated with these various missions, different levels of risk and rigor need to be implemented to be more in line with what is appropriate for the mission. Thus, NASA has four different classifications that range from Class A to Class D based on the mission details. One of these projects is the Resource Prospector (RP) Mission, which is a multi-center and multi-institution collaborative project to search for volatiles in the polar regions of the Moon. The RP mission is classified as a Class D mission and as such, has the opportunity to more tightly manage, and therefore accept, greater levels of risk. The requirements for Class D missions were at the forefront of the design and thus presented unique challenges in vehicle development and systems engineering processes. This paper will discuss the systems engineering process at NASA and how that process is tailored for Class D missions, specifically the RP mission.

Rojdev, Kristina↗

NASA NTRS1989

Galileo Science Writers' Briefing

This NASA Kennedy video production presents Part 1 of a press conference held at JPL on August 8, 1989. The briefing in its entirety covers the Galileo Project's mission design from launch to completion in 1997 and is moderated by JPL Public Information Mgr. Robert Macmillan. Part 1 of the 3 part video series includes presentations by Richard J. Spehalski (Galileo Project Manager) and Clayne M. Yeates (Acting Science Mission Design Manager). Mr. Spehalski's presentation includes actual footage of spacecraft preparations at Kennedy Space Center and slides of mission timelines. Dr. Yeates discusses the Galileo mission in chronological order and includes slides of the interplanetary trajectory, encounter geometry, propellant margins vs. launch date, and planned earth images.

Source record↗

NASA NTRS2013

Education and Public Outreach and Engagement at NASA's Analog Missions in 2012

Analog missions are integrated, multi-disciplinary activities that test key features of future human space exploration missions in an integrated fashion to gain a deeper understanding of system-level interactions and operations early in conceptual development. These tests often are conducted in remote and extreme environments that are representative in one or more ways to that of future spaceflight destinations. They may also be conducted at NASA facilities, using advanced modeling and human-in-the-loop scenarios. As NASA develops a capability driven framework to transport crew to a variety of space environments, it will use analog missions to gather requirements and develop the technologies necessary to ensure successful exploration beyond low Earth orbit. NASA s Advanced Exploration Systems (AES) Division conducts these high-fidelity integrated tests, including the coordination and execution of a robust education and public outreach (EPO) and engagement program for each mission. Conducting these mission scenarios in unique environments not only provides an opportunity to test the EPO concepts for the particular future-mission scenario, such as the best methods for conducting events with a communication time delay, but it also provides an avenue to deliver NASA s human space exploration key messages. These analogs are extremely exciting to students and the public, and they are performed in such a way that the public can feel like part of the mission. They also provide an opportunity for crew members to obtain training in education and public outreach activities similar to what they would perform in space. The analog EPO team is responsible for the coordination and execution of the events, the overall social media component for each mission, and public affairs events such as media visits and interviews. They also create new and exciting ways to engage the public, manage and create website content, coordinate video footage for missions, and coordinate and integrate each activity into the mission timeline. In 2012, the AES Analog Missions Project performed three distinct missions - NASA Extreme Environment Mission Operations (NEEMO), which simulated a mission to an asteroid using an undersea laboratory; In-Situ Resource Utilization (ISRU) Field Test, which simulated a robotic mission to the moon searching and drilling for water; and Research and Technology Studies (RATS) integrated tests, which also simulated a mission to an asteroid. This paper will discuss the education and public engagement that occurred during these missions.

Watkins, Wendy L.↗

NASA NTRS2020

Risk and Performance Assessment of Generic Mission Architectures: Showcasing the Artemis Mission

A has initiated a strong push to return face. In this work, we astronaut assess performance and risk for proposed mission architectures using a new Mission Architecture Risk Assessment (MARA) tool. The MARA tool can produce statistics about the availability of components and overall performance of the mission considering potential failures of any of its components. In a Monte Carlo approach, the tool repeats the mission simulation multiple times while a random generator lets modules fail according to their failure rates. The results provide statistically meaningful insights into the overall performance of the chosen architecture. A given mission architecture can be freely replicated in the tool, with the mission timeline and basic characteristics of employed mission modules (habitats, rovers, power generation units, etc.) specified in a configuration file. Crucially, failure rates for each module need to be known or estimated. The tool performs an event-driven simulation of the mission and accounts for random failure events. Failed modules can be repaired, which takes crew time but restores operations. In addition to tracking individual modules, MARA can assess the availability of predefined functions throughout the mission. For instance, the function of resource collection would require a rover to collect the resources, a power generation unit to charge the rover, and a resource processing module. Together, the modules that are required for a given function are called a functional group. Similarly, we can assess how much crew time is available to achieve a mission benefit (e.g. research, building a base, etc) as opposed to spending crew time on repairs. Here we employ the method on the proposed NASA Artemis mission. Artemis aims to return United States astronauts to the lunar surface by 2024. Results provide insights into mission failure probabilities, up- and downtime for individual modules and crew-time resources spent on the repair of failed modules. The tool also allows us to tweak the mission architecture in order to find setups that produce more favorable mission performance. As such, the tool can be an aid in improving the mission architect abling cost-benefit analysis for mission improvement.

Rumpf, Clemens M.↗