Search NASA⌕ Search

SEARCH · Search NASA

Results for “Mission planning”

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 433 records · Page 24
All sourcesNASA NTRSDOE OSTI
NASA NTRS2019

Visualization and Analysis of Solar System Small Bodies with NASA's Solar System Treks Project

In its investigations of Vesta and Ceres, NASA’s Dawn mission has returned spectacular data detailing the surfaces of these two prominent small bodies in our Solar System’s asteroid belt. In order to greatly facilitate dissemination, visualization, and analysis of this data, and public understanding of the mission, the Dawn mission has partnered with NASA’s Solar System Treks Project (SSTP). SSTP has recently released an update to the Vesta Trek online portal (https://trek.nasa.gov/vesta/) and has released a new Ceres Trek portal (https://trek.nasa.gov/ceres/). This presentation will showcase the use of the Ceres Trek and Vesta Trek portals and demonstrate how they can be used to visualize and analyze particularly interesting landforms such as the pitted terrain on Vesta and relic cryovolcanoes on Ceres. We will also demonstrate the new VR capability that has been added to the portals, allowing users to generate their own virtual reality flyovers for any user-defined paths along the bodies’ surfaces. In addition to highlighting the portals for Ceres and Vesta, the presentation will preview additional portals being planned/developed for other small bodies. NASA and JAXA have requested the development of a portal for the asteroid Ryugu to facilitate dissemination, visualization, and analysis of data from Japan’s Hayabusa2 mission, and a portal for Mars’ moon Phobos in support of mission planning for Japan’s MMX mission. We are also planning a portal for the asteroid Bennu with data from the OSIRIS-Rex mission. All of these products are efforts in the NASA Solar System Treks Project (SSTP), available at https://trek.nasa.gov. NASA's Solar System Trek online portals provide web-based suites of interactive data visualization and analysis tools to enable mission planners, planetary scientists, students, and the general public to access mapped data products from past and current missions for a growing number of planetary bodies including the Moon, Mars, Vesta, etc. These portals are being used for site selection and analysis by NASA and a number of its international partners, supporting upcoming missions. In addition to demonstrating the capabilities of selected portals in this presentation, we will solicit input from the community for ideas for future enhancements to the portals.

Day, Brian↗
NASA NTRS2016

Efficiency Management in Spaceflight Systems

Efficiency in spaceflight is often approached as “faster, better, cheaper – pick two”. The high levels of performance and reliability required for each mission suggest that planners can only control for two of the three. True efficiency comes by optimizing a system across all three parameters. The functional processes of spaceflight become technical requirements on three operational groups during mission planning: payload, vehicle, and launch operations. Given the interrelationships among the functions performed by the operational groups, optimizing function resources from one operational group to the others affects the efficiency of those groups and therefore the mission overall. This paper helps outline this framework and creates a context in which to understand the effects of resource trades on the overall system, improving the efficiency of the operational groups and the mission as a whole. This allows insight into and optimization of the controlling factors earlier in the mission planning stage.

Murphy, Karen↗
NASA NTRS2016

Efficiency Management in Spaceflight Systems

Efficiency in spaceflight is often approached as "faster, better, cheaper - pick two". The high levels of performance and reliability required for each mission suggest that planners can only control for two of the three. True efficiency comes by optimizing a system across all three parameters. The functional processes of spaceflight become technical requirements on three operational groups during mission planning: payload, vehicle, and launch operations. Given the interrelationships among the functions performed by the operational groups, optimizing function resources from one operational group to the others affects the efficiency of those groups and therefore the mission overall. This paper helps outline this framework and creates a context in which to understand the effects of resource trades on the overall system, improving the efficiency of the operational groups and the mission as a whole. This allows insight into and optimization of the controlling factors earlier in the mission planning stage.

Murphy, Karen↗
NASA NTRS2007

Rapid Contingency Simulation Modeling of the NASA Crew Launch Vehicle

The NASA Crew Launch Vehicle is a two-stage orbital launcher designed to meet NASA's current as well as future needs for human space flight. In order to free the designers to explore more possibilities during the design phase, a need exists for the ability to quickly perform simulation on both the baseline vehicle as well as the vehicle after proposed changes due to mission planning, vehicle configuration and avionics changes, proposed new guidance and control algorithms, and any other contingencies the designers may wish to consider. Further, after the vehicle is designed and built, the need will remain for such analysis in the event of future mission planning. An easily reconfigurable, modular, nonlinear six-degree-of-freedom simulation matching NASA Marshall's in-house high-fidelity simulator is created with the ability to quickly perform simulation and analysis of the Crew Launch Vehicle throughout the entire launch profile. Simulation results are presented and discussed, and an example comparison fly-off between two candidate controllers is presented.

Betts, Kevin M.↗
NASA NTRSDate not supplied

Lucy Mission Design Strategy in a Dynamic Operations Environment from Launch Through First Asteroid Encounter

Lucy, a 12-yearlong NASA Discovery-class mission which launched on October 16, 2021will fly by several Jupiter-Trojan asteroids a t the L4 and L5 La grange points. Prior to theL4 Trojan encounter in 2027 and 2028, Lucy will utilize two Earth gravity-assist flybys and fly by two main-belt a steroids. After the L4 encounters a third Earth flyby will set up the L5 Troja n encounter in 2033. This pa per summarizes the baseline mission plan with focus on the spacecraft trajectory and the corresponding essential trajectory correction maneuvers as well as how the Lucy team adapted to many unforeseen changes to the spacecraft configuration and added an asteroid target of opportunity that required changes to the baseline mission plan. Refinement of asteroid flyby science requirements after launch also required updates to the baseline Lucy trajectory.

James V. Mcadams↗
NASA NTRSDate not supplied

VIPER Lunar Rover Agile Mission Systems

Agile development methods, which have gone from outlier to mainstream in software development, are poised to expand into all aspects of space mission development. Modern software development operates on a principle of continuous deployment, where progress is verified not with conventional metrics, but with a continuous build, available to key stakeholders, enabling direct examination of the state of the code base, and assessment of progress through demonstration of capability. Delivery times are measured in weeks, not months. Stakeholders are part of the process on an ongoing basis. The cost of change is comparatively low and requirements, which often are not precisely defined at the start of a project, may be iteratively refined in a series of agile development cycles. Agile methods are compatible with traditional system engineering methods and may be tailored to the space operations environment. The low cost of change and iterative development cycles of agile enable requirements to be defined as outcomes and constraints, with design details to be refined during the development cycle. We are now at a point where agile methods may be extended beyond software, to Mission Systems, including the Mission Operations System and the Ground Data System. For NASA’s VIPER Lunar Rover Mission, scheduled to land at a lunar pole in late 2023, we are developing the Mission System using agile methods. As in agile software, where the measure of progress is working code, in agile mission system development, the measure of capability is what we can demonstrate. Demonstrations over presentations. We demonstrate mission system capability using simulations. The concept of operations, from commanding, to driving the rover, to how we downlink images for evaluation for a near-real time command cycle, will be tested and proven in simulation, years before we begin the traditional simulation cycle for training. “Say it then simulate it.” We develop and refine our designs using simulations, with an emphasis on new components of the system that are not well known early. For example, the required duration of a mission planning cycle for a lunar surface asset such as VIPER, that operates twenty-four hours a day, seven days a week, with continuous communications and a unique set of constraints based on the physics of the lunar poles and the line of site to Earth, is a unique problem in mission planning that is unlikely to be solved in a series of meetings. A small number of requirements specifying the outcomes may serve as the jumping off point to an agile development cycle, with demonstration in simulations. We have already demonstrated this process with simulations of rover driver decision time. VIPER is driven using near-real time command and control to waypoints. The driver decision time between waypoints is a fundamental enabling unit of productivity to accomplish the mission timeline. We have validated driver decision time in simulations of rover driving at the lunar South Pole, using the prototype mission tools for driving, command and control. The capability to develop and refine designs using simulations as part of agile Mission System development cycle changes the nature of team interactions, creating a focus on doing, rather than analyzing and documenting. Waterfall development cycles were, in part, a product of the significant cost of change in the early days of spaceflight. When the cost of change is high, it is vital to get your requirements right at the outset, because the system will be built to those specifications, and, when change is expensive, you better get it right early. However, modern technology has greatly lowered the cost of change, enabling iterative, rapid development cycles, in which key operations concepts may be tested and refined during development. Extending agile development to the Mission System for VIPER is a significant step in moving agile development methods for space operations beyond software, to the Mission System.

Agile↗
NASA NTRS1990

Small Explorer project: Submillimeter Wave Astronomy Satellite (SWAS). Mission operations and data analysis plan

The Mission Operations and Data Analysis Plan is presented for the Submillimeter Wave Astronomy Satellite (SWAS) Project. It defines organizational responsibilities, discusses target selection and navigation, specifies instrument command and data requirements, defines data reduction and analysis hardware and software requirements, and discusses mission operations center staffing requirements.

Melnick, Gary J.↗
NASA NTRS2000

Streamlining Collaborative Planning in Spacecraft Mission Architectures

During the past two decades, the planning and scheduling community has substantially increased the capability and efficiency of individual planning and scheduling systems. Relatively recently, research work to streamline collaboration between planning systems is gaining attention. Spacecraft missions stand to benefit substantially from this work as they require the coordination of multiple planning organizations and planning systems. Up to the present time this coordination has demanded a great deal of human intervention and/or extensive custom software development efforts. This problem will become acute with increased requirements for cross-mission plan coordination and multi -spacecraft mission planning. The Advanced Architectures and Automation Branch of NASA's Goddard Space Flight Center is taking innovative steps to define collaborative planning architectures, and to identify coordinated planning tools for Cross-Mission Campaigns. Prototypes are being developed to validate these architectures and assess the usefulness of the coordination tools by the planning community. This presentation will focus on one such planning coordination too], named Visual Observation Layout Tool (VOLT), which is currently being developed to streamline the coordination between astronomical missions

Misra, Dhariti↗
NASA NTRSDate not supplied

Case Study for Lunar ISRU Systems Utilizing Polar Water

In-Situ Resource Utilization (ISRU) is key to long term presence at any extraterrestrial destination. Current NASA direction is to achieve a sustainable presence on the lunar surface by 2028. Mission plans currently target the lunar South Pole to leverage the extended periods of solar illumination and allows for potential access to water ice in the permanently shadowed areas around the poles. With water, it is possible to produce both fuel and oxidizer to fully refuel a vehicle. In order to address ISRU infusion into mission planning, a study of an end-to-end ISRU propellant production system was initiated to assess ISRU architectures and obtain mass and power estimates for each. The results of these case studies will be presented. For this study, The ISRU system architecture involved two sites; the mine site in a shadowed crater where water ice is excavated and extracted from the regolith and the propellant production site at an illuminated ridge where the water is processed into liquefied O2 and H2 propellants. Fixed hardware would be emplaced at each site, with two alternating water tankers to transport water between them. Notional lunar sites were identified for this architecture for baseline environmental parameters. Technology solutions for each subsystem were selected based on those with the highest fidelity models or those that have empirical laboratory data to anchor to. While power needs were identified for each location, a power solution was not prescribed, therefore the masses presented do not include surface power systems. The baseline case in this study assumed that 10 mT of oxygen, along with enough hydrogen to support a propulsion mixture ratio of 6, must be produced in 225 days. Therefore 15 mT of water would need to be collected and processed. The baseline solution resulted in a system mass of5 mT and a total required power of 68kW. The majority of the mass was split between the ridge site system and the two water tankers (2.6 mTand 1.8mTrespectively). The majority of the required power was with three subsystems at approximately 20 kW each: hydrogen liquefaction, electrolysis, and the water extractor subsystem. Trades for four key variables are also presented, namely production rate, water concentration, dry overburden depth, and number of water transport trips. This can be compared to a system that targets oxygen from the minerals in the surface regolith material. A carbothermal reduction reactor system was used for this comparison. The use of direct solar thermal energy to process the regolith and the ease of access of the resource resulted in significantly lower values for the oxygen case: approximately 2.7 mT and 11.8 kW. However, the mass trade would favor the water case over successive missions where the hydrogen up-mass of 2 mT per mission will accrue against the oxygen system.1Aerospace Research Engineer, Chemical and Thermal Propulsion Systems Branch, Senior Member.2Mechanical Engineer, Propulsion and Power Division/Energy Conversion Systems, 2101 Nasa Pkwy/Mailcode EP3 Houston, TX 77058, AIAA member.

Lunar↗
NASA NTRS1976

Formulation of detailed consumables management models for the development (preoperational) period of advanced space transportation system: Executive summary

Formulation of models required for the mission planning and scheduling function and establishment of the relation of those models to prelaunch, onboard, ground support, and postmission functions for the development phase of space transportation systems (STS) was conducted. The preoperational space shuttle is used as the design baseline for the subject model formulations. Analytical models were developed which consist of a mission planning processor with appropriate consumables data base and a method of recognizing potential constraint violations in both the planning and flight operations functions. A flight data file for storage/retrieval of information over an extended period which interfaces with a flight operations processor for monitoring of the actual flights was examined.

Torian, J. G.↗
NASA NTRSDate not supplied

Case Studies for Lunar ISRU Systems Utilizing Polar Water

In-Situ Resource Utilization (ISRU) is key to long term presence at any extraterrestrial destination. Current NASA direction is to achieve a sustainable presence on the lunar surface by 2028. Mission plans currently target the lunar South Pole to leverage the extended periods of solar illumination and allows for potential access to water ice in the permanently shadowed areas around the poles. With water, it is possible to produce both fuel and oxidizer to fully refuel a vehicle. In order to address ISRU infusion into mission planning, a study of an end-to-end ISRU propellant production system was initiated to assess ISRU architectures and obtain mass and power estimates for each. The results of these case studies will be presented.

In situ Resource Utilization↗
NASA NTRS2008

A System Trade Study of Remote Infrared Imaging for Space Shuttle Reentry

A trade study reviewing the primary operational parameters concerning the deployment of imaging assets in support of the Hypersonic Thermodynamic Infrared Measurements (HYTHIRM) project was undertaken. The objective was to determine key variables and constraints for obtaining thermal images of the Space Shuttle orbiter during reentry. The trade study investigated the performance characteristics and operating environment of optical instrumentation that may be deployed during a HYTHIRM data collection mission, and specified contributions to the Point Spread Function. It also investigated the constraints that have to be considered in order to optimize deployment through the use of mission planning tools. These tools simulate the radiance modeling of the vehicle as well as the expected spatial resolution based on the Orbiter trajectory and placement of land based or airborne optical sensors for given Mach numbers. Lastly, this report focused on the tools and methodology that have to be in place for real-time mission planning in order to handle the myriad of variables such as trajectory ground track, weather, and instrumentation availability that may only be known in the hours prior to landing.

Schwartz, Richard J.↗
NASA NTRS2018

Space Launch System (SLS) Mission Planner’s Guide

The purpose of this Space Launch System (SLS) Mission Planner’s Guide (MPG) is to provide future payload developers/users with sufficient insight to support preliminary SLS mission planning. Consequently, this SLS MPG is not intended to be a payload requirements document; rather, it organizes and details SLS interfaces/accommodations in a manner similar to that of current Expendable Launch Vehicle (ELV) user guides to support early feasibility assessments. Like ELV programs, specific payload requirements will be defined in unique documentation once manifested to fly on SLS. SLS users requiring additional mission planning information or more detailed technical interchange concerning specific SLS accommodations should contact the SLS Spacecraft/Payload Integration and Evolution (SPIE) office.

Smith, David Alan↗
NASA NTRS1974

Planetary entry aerothermodynamics. II - Computational analyses and flight experience

Limitations concerning the possibility to simulate all the significant flow and thermal phenomena occurring during the entry of a space vehicle into a planetary atmosphere make it necessary to rely on computational analyses to obtain the required data for the design of the spacecraft needed for the NASA missions planned for the next two decades. 'Benchmark' computer programs concerned with complete, detailed, and accurate computational solutions of entry problems are considered along with programs representing engineering approximations for cases in which the accuracy provided by the benchmark programs is not needed. The information obtainable by computational analysis has to be supplemented by actual flight experience in order to meet the goals of the NASA entry-technology program. The individual space missions planned for the coming years are examined together with the possibilities for obtaining the data needed to satisfy the entry requirements in each case.

Olstad, W. B.↗
NASA NTRS1990

Space Station Freedom altitude strategy

The Space Station Freedom (SSF) altitude strategy provides guidelines and assumptions to determine an altitude profile for Freedom. The process for determining an altitude profile incorporates several factors such as where the Space Shuttle will rendezvous with the SSF, when reboosts must occur, and what atmospheric conditions exist causing decay. The altitude strategy has an influence on all areas of SSF development and mission planning. The altitude strategy directly affects the micro-gravity environment for experiments, propulsion and control system sizing, and Space Shuttle delivery manifests. Indirectly the altitude strategy influences almost every system and operation within the Space Station Program. Evolution of the SSF altitude strategy has been a very dynamic process over the past few years. Each altitude strategy in turn has emphasized a different consideration. Examples include a constant Space Shuttle rendezvous altitude for mission planning simplicity, or constant micro-gravity levels with its inherent emphasis on payloads, or lifetime altitudes to provide a safety buffer to loss of control conditions. Currently a new altitude strategy is in development. This altitude strategy will emphasize Space Shuttle delivery optimization. Since propellant is counted against Space Shuttle payload-to-orbit capacity, lowering the rendezvous altitude will not always increase the net payload-to-orbit, since more propellant would be required for reboost. This altitude strategy will also consider altitude biases to account for Space Shuttle launch slips and an unexpected worsening of atmospheric conditions. Safety concerns will define a lower operational altitude limit, while radiation levels will define upper altitude constraints. The evolution of past and current SSF altitude strategies and the development of a new altitude strategy which focuses on operational issues as opposed to design are discussed.

Mcdonald, Brian M.↗
NASA NTRS2012

Designing Spacecraft and Mission Operations Plans to Meet Flight Crew Radiation Dose Requirements: Why is this an "Epic Challenge" for Long-Term Manned Interplanetary Flight

Outline of presentation: (1) Radiation Shielding Concepts and Performance - Galactic Cosmic Rays (GCRs) (1a) Some general considerations (1b) Galactic Cosmic Rays (2)GCR Shielding I: What material should I use and how much do I need? (2a) GCR shielding materials design and verification (2b) Spacecraft materials point dose cosmic ray shielding performance - hydrogen content and atomic number (2c) Accelerator point dose materials testing (2d) Material ranking and selection guidelines (2e) Development directions and return on investment (point dose metric) (2f) Secondary particle showers in the human body (2f-1) limited return of investment for low-Z, high-hydrogen content materials (3) GCR shielding II: How much will it cost? (3a) Spacecraft design and verification for mission radiation dose to the crew (3b) Habitat volume, shielding areal density, total weight, and launch cost for two habitat volumes (3c) It's All about the Money - Historical NASA budgets and budget limits (4) So, what can I do about all this? (4a) Program Design Architecture Trade Space (4b) The Vehicle Design Trade Space (4c) Some Near Term Recommendations

Koontz, Steven↗