Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Scenario Development”

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 109 records · Page 6

Communication Platform Payload Definition (CPPD) study. Volume 1: Executive summary

This is Volume 1 (Executive Summary) of the Ford Aerospace & Communications Corporation Final Report for the Communication Platform Payload Definition (CPPD) Study program conducted for NASA Lewis Research Center under contract No. NAS3-24235. This report presents the results of the study effort leading to five potential platform payloads to service CONUS and WARC Region 2 traffic demand as projected to the year 2008. The report addresses establishing the data bases, developing service aggregation scenarios, selecting and developing 5 payload concepts, performing detailed definition of the 5 payloads, costing them, identifying critical technology, and finally comparing the payloads with each other and also with non-aggregated equivalent services.

Hunter, E. M.↗

Communication Platform Payload Definition (CPPD) study. Volume 2: Technical report

This is Volume 2 (Technical Report) of the Ford Aerospace & Communications Corporation Final Report for the Communication Platform Payload Definition (CPPD) Study program conducted for NASA Lewis Research Center under contract No. NAS3-24235. This report presents the results of the study effort leading to five potential platform payloads to service CONUS and WARC Region 2 traffic demand as projected to the year 2008. The report addresses establishing the data bases, developing service aggregation scenarios, selecting and developing 5 payload concepts, performing detailed definition of the 5 payloads, costing them, identifying critical technology, and finally comparing the payloads with each other and also with non-aggregated equivalent services.

Hunter, E. M.↗

Communication Platform Payload Definition (CPPD) study. Volume 3: Addendum

This is Volume 3 (Addendum) of the Ford Aerospace & Communications Corporation Final Report for the Communication Platform Payload Definition (CPPD) Study Program conducted for NASA Lewis Research Center under contract No. NAS3-24235. This report presents the results of the study effort leading to five potential platform payloads to service CONUS and WARC Region 2 traffic demand as projected to the year 2008. The report addresses establishing the data bases, developing service aggregation scenarios, selecting and developing 5 payload concepts, performing detailed definition of the 5 payloads, costing them, identifying critical technology, and finally comparing the payloads with each other and also with non-aggregated equivalent services.

Hunter, E. M.↗

NASA Mission Operations Directorate Preparations for the COTS Visiting Vehicles

With the retirement of the Space Shuttle looming, a series of new spacecraft is under development to assist in providing for the growing logistical needs of the International Space Station (ISS). Two of these vehicles are being built under a NASA initiative known as the Commercial Orbital Transportation Services (COTS) program. These visiting vehicles ; Space X s Dragon and Orbital Science Corporation s Cygnus , are to be domestically produced in the United States and designed to add to the capabilities of the Russian Progress and Soyuz workhorses, the European Automated Transfer Vehicle (ATV) and the Japanese H-2 Transfer Vehicle (HTV). Most of what is known about the COTS program has focused on the work of Orbital and SpaceX in designing, building, and testing their respective launch and cargo vehicles. However, there is also a team within the Mission Operations Directorate (MOD) at NASA s Johnson Space Center working with their operational counterparts in these companies to provide operational safety oversight and mission assurance via the development of operational scenarios and products needed for these missions. Ensuring that the operational aspect is addressed for the initial demonstration flights of these vehicles is the topic of this paper. Integrating Dragon and Cygnus into the ISS operational environment has posed a unique challenge to NASA and their partner companies. This is due in part to the short time span of the COTS program, as measured from initial contract award until first launch, as well as other factors that will be explored in the text. Operational scenarios and products developed for each COTS vehicle will be discussed based on the following categories: timelines, on-orbit checkout, ground documentation, crew procedures, software updates and training materials. Also addressed is an outline of the commonalities associated with the operations for each vehicle. It is the intent of the authors to provide their audience with a better understanding of the mission assurance that MOD brings to commercial ventures to the ISS

Shull, Sarah A.↗

Crew Health and Performance Integrated Data System Platform Project Updates

Future human exploration missions introduce a new paradigm as crews move further from the resupply and near real-time ground support typical of Low Earth Orbit missions today. Without immediate support from ground-based personnel, exploration crews will be more reliant on inflight data and technology to respond to emergencies and anomalies. Today, in-flight data is often siloed, unsynchronized, and largely inaccessible in real time. Many data sets require manual entry and/or data transfer between vehicles and the ground. These issues contribute to risks in supporting crew autonomy for future exploration missions. An integrated data system platform is needed to mitigate these risks by supporting a new generation of technologies and employing advanced analytical and predictive modeling techniques to enable crew autonomy for future exploration missions. The Crew Health and Performance Integrated Data System Platform (CHP-IDSP) project is laying a foundation for future in-flight informatics by providing a back-end architecture for collecting, storing, and integrating multiple sources of data generated by and around the crew. This cohesive integration point will streamline the management of CHP data (e.g., environmental, exercise, medical, sleep, performance, etc.) and facilitate situation awareness and decision support required by the crew and remote support of exploration missions. This presentation will describe the ongoing development effort of the path-to-flight CHP-IDSP software and the demonstration of its core capabilities. This includes a brief history of the project, the human-centered process used to identify data needs and workflows feeding the development of scenarios and requirements, and current subsystem development status. Current integrations, including the Chiron exploration electronic health record application, will be discussed. Future work includes collaboration with additional CHP domains and a flight technology demonstration.

Data integration↗

Crew Health and Performance Integrated Data Service Platform (CHP-IDSP): Project Updates

Future human exploration missions introduce a new paradigm as crews move further from the resupply and near real-time ground support typical of Low Earth Orbit missions today. Without immediate support from ground-based personnel, exploration crews will be more reliant on inflight data and technology to respond to emergencies and anomalies. Today, in-flight data is often siloed, unsynchronized, and largely inaccessible in real time. Many data sets require manual entry and/or data transfer between vehicles and the ground. These issues contribute to risks in supporting crew autonomy for future exploration missions. An integrated data services platform is needed to mitigate these risks by supporting a new generation of technologies and employing advanced analytical and predictive modeling techniques to enable crew autonomy for future exploration missions. The Crew Health and Performance Integrated Data System Platform (CHP-IDSP) project is laying a foundation for future in-flight informatics by providing a back-end architecture for collecting, storing, and integrating multiple sources of data generated by and around the crew. This cohesive integration point will streamline the management of CHP data (e.g., environmental, exercise, medical, sleep, performance, etc.) and facilitate situation awareness and decision support required by the crew and remote support of exploration missions. This presentation will describe the ongoing development effort of the path-to-flight CHP-IDSP software and the demonstration of its core capabilities. This includes a brief history of the project, the human-centered process used to identify data needs and workflows feeding the development of scenarios and requirements, and current subsystem development status. Current integrations, including the Chiron exploration electronic health record application, will be discussed. Future work includes collaboration with additional CHP domains and a flight technology demonstration.

Software↗

Development of OCSS In-Suit Urine Collection and Removal System for Cabin Depressurization Scenario

NASA is developing a waste management system for use in a pressurizable space suit for future Orion missions. Driven by Orion's cabin depress operational scenario, specific life support equipment is needed for crew survival. Immediate life-sustaining resources can be provided by the Orion launch and entry suit as a pressurizable safe haven. Before long, though, the crew would also need an appropriate waste management system to maintain their crew health in a confined environment, especially over multiple days. Long-duration waste management hardware for use with a space suit has not been designed or utilized since the Apollo program, and there are numerous technical challenges associated with its implementation. In conjunction both NASA's Orion Crew Survival Systems (OCSS) and Omni Medical Systems are addressing such challenges through their on-going hardware design efforts to support future Orion missions. This paper details some of the initial design and testing efforts that have been completed while discussing the major challenges that have arisen in the process.

Harvie, Mark↗

On-orbit operational scenarios, tools and techniques

This paper concentrates on methods and techniques used to develop operational scenarios for orbital missions, including development of models to analyze alternatives, modification of tools and refinement of techniques for future missions. Many of these tools and techniques have been derived from previous tools, techniques and experience from the Orbital Maneuvering Vehicle (OMV) program. Results from use of these tools show the current Cargo Transfer Vehicle nominal mission scenario, with 95 discrete events defined for the CTV mission from the NLS Heavy Lift Launch Vehicle (HLLV) to Space Station Freedom (SSF).

Jennings, Jerry L.↗

Integrating Models and Observations

For the past ten years, the coronal loops community has held bi-annual workshops to discuss the analysis of coronal loop observations and the latest efforts to model the loop structures. During this time, several heating scenarios have been proposed to explain loop observations. These heating scenarios rely on different heating frequencies, locations, and durations, as well as different loop sub-structure. Often the scenarios are developed to explain an observation, hence all heating scenarios match some observational criteria. The key to discriminating between the competing heating scenarios is to first identify the distinguishing observables. For instance, both effectively steady and nanoflare-heating scenarios can produce quasi-steady intensities. Observing quasi-steady intensities, then, does not help determine which heating scenario is most likely. These heating scenarios may, however, predict different velocities or different emission measure distributions. In this talk, I will discuss a few of the expected observations for some simple heating scenarios. I will ask the modeling community to calculate similar observations for the different heating scenarios to generate a standard list of expected observations. After the community develops this list, comparisons with actual loop observations can then distinguish the most likely heating scenario.

Womebarger, Amy↗

Development of a Prototype Automation Simulation Scenario Generator for Air Traffic Management Software Simulations

A technique for automated development of scenarios for use in the Multi-Center Traffic Management Advisor (McTMA) software simulations is described. The resulting software is designed and implemented to automate the generation of simulation scenarios with the intent of reducing the time it currently takes using an observational approach. The software program is effective in achieving this goal. The scenarios created for use in the McTMA simulations are based on data taken from data files from the McTMA system, and were manually edited before incorporation into the simulations to ensure accuracy. Despite the software s overall favorable performance, several key software issues are identified. Proposed solutions to these issues are discussed. Future enhancements to the scenario generator software may address the limitations identified in this paper.

Khambatta, Cyrus F.↗

Commercial Aircraft Emission Scenario for 2020: Database Development and Analysis

This report describes the development of a three-dimensional database of aircraft fuel use and emissions (NO(x), CO, and hydrocarbons) for the commercial aircraft fleet projected to 2020. Global totals of emissions and fuel burn for 2020 are compared to global totals from previous aircraft emission scenario calculations.

Sutkus, Donald J., Jr.↗

Creating a Scenario Suitable for Multiple Caregivers

The HPS can be utilized for the training of a wide variety of caregivers, ranging from physicians to laypeople. Methods: A single scenario was developed and adapted for a number of clinical scenarios and operational environments, ranging from in-flight to the immediate postflight timeline. In this way, different caregivers, from astronauts to search and rescue forces to specialty-boarded physicians, could make use of a single clinical situation. Five crew medical officer analogs and sixty anesthesia residents, serving as flight surgeon analogs, and, were briefed on space medicine and physiology, then were exposed to the scenario and asked to manage the patient as if they were part of the in-flight or recovery team. Results: Basic themes, such as crisis resource management, were standard across the student audiences. Discussion: A single clinical script can easily be adapted for multiple uses.

Doerr, Harold↗

Clinical Decision Support - Concepts of Operation

We are entering a new era in space exploration to return to the moon and explore Mars. Crew members operating independently during long duration space exploration missions will require a clinical decision support system (CDSS) to increase autonomy by augmenting their knowledge, skills and abilities in different scenarios. Significant changes to in-flight and habitat medical care due to constraints on mass, volume, power, crew time and medical evacuation capabilities are needed to increase crew autonomy and self-reliance in decision making and task performance. The Exploration Medical Capability (ExMC) Element of the Human Research Program (HRP) pushes the boundary of space medical systems to advance the care of astronauts on future exploration missions beyond low Earth orbit by identifying and testing next-generation medical care and crew health maintenance technologies. Clinical decision support (CDS) presents knowledge and data in a context aware manner to augment a crew members’ knowledge, skills and abilities during the process of observation, orientation, decisions and action. A comprehensive crew health and performance CDSS is required to augment crew capability and will be used in different scenarios for several reasons. In general, the CDSS’s role is to assist the crew in prevention, detection, diagnosis and treatment of crew health and performance related conditions that may arise in exploration spaceflight. For example, CDSS would assist a high acuity scenario such as a heart attack by supplying clear instructions, vital signs and treatment reminders. A lower severity scenario such as kidney stone risk could interface to vehicle systems and display more complex predictive data during a diagnosis. A CDSS needs to contribute to successful missions by maintaining a high performing crew who can potentially exhibit countless medical conditions related to derangements from the space environment (sleep, cognition, nutrition and exercise) as well as conditions intrinsic to humans anywhere. While supporting the crew’s ability to make sound clinical decisions is desirable in any mission, it is essential for exploration missions with significant communication delays, no evacuation capability, and extended exposure to the flight environment. Such missions correspond with medical Level of Care V (LOC V), the highest level specified in NASA-STD-3001. The project focuses on CDS implementation research to derive requirements for LOC V, where the need for increased autonomy results in new practices and the inclusion of non-clinical data, such as vehicle environmental measures and physical exercise results, from other human and vehicle domains and advanced analytics. The CDS project describes how the CDSS is intended to be used by defining concepts of operations (ConOps). The process to derive ConOps focuses on increased autonomy that reduces the likelihood and consequences of accepted medical conditions. These crew health and performance inputs are grouped by common datasets and analysis models. Use cases are derived to research new clinical scenarios, architectural development and workflows. Implementation research is conducted with protypes to inform assumptions and derive requirements. The project also establishes how externally developed analysis and approaches can be added to expand a clinical decision support system and thus highlight how a comprehensive system can be globally developed with collaborators. This presentation will cover example scenarios from the CDS ConOps and the method to derive them. One example scenario will be CDSS alerting an increased kidney stone risk during a mission, with diagnosis and treatment options provided during the intervention.

clinical decision support↗

Clinical Decision Support - Concepts of Operation

We are entering a new era in space exploration to return to the moon and explore Mars. Crew members operating independently during long duration space exploration missions will require a clinical decision support system (CDSS) to increase autonomy by augmenting their knowledge, skills and abilities in different scenarios. Significant changes to in-flight and habitat medical care due to constraints on mass, volume, power, crew time and medical evacuation capabilities are needed to increase crew autonomy and self-reliance in decision making and task performance. The Exploration Medical Capability (ExMC) Element of the Human Research Program (HRP) pushes the boundary of space medical systems to advance the care of astronauts on future exploration missions beyond low Earth orbit by identifying and testing next-generation medical care and crew health maintenance technologies. Clinical decision support (CDS) presents knowledge and data in a context aware manner to augment a crew members’ knowledge, skills and abilities during the process of observation, orientation, decisions and action. A comprehensive crew health and performance CDSS is required to augment crew capability and will be used in different scenarios for several reasons. In general, the CDSS’s role is to assist the crew in prevention, detection, diagnosis and treatment of crew health and performance related conditions that may arise in exploration spaceflight. For example, CDSS would assist a high acuity scenario such as a heart attack by supplying clear instructions, vital signs and treatment reminders. A lower severity scenario such as kidney stone risk could interface to vehicle systems and display more complex predictive data during a diagnosis. A CDSS needs to contribute to successful missions by maintaining a high performing crew who can potentially exhibit countless medical conditions related to derangements from the space environment (sleep, cognition, nutrition and exercise) as well as conditions intrinsic to humans anywhere. While supporting the crew’s ability to make sound clinical decisions is desirable in any mission, it is essential for exploration missions with significant communication delays, no evacuation capability, and extended exposure to the flight environment. Such missions correspond with medical Level of Care V (LOC V), the highest level specified in NASA-STD-3001. The project focuses on CDS implementation research to derive requirements for LOC V, where the need for increased autonomy results in new practices and the inclusion of non-clinical data, such as vehicle environmental measures and physical exercise results, from other human and vehicle domains and advanced analytics. The CDS project describes how the CDSS is intended to be used by defining concepts of operations (ConOps). The process to derive ConOps focuses on increased autonomy that reduces the likelihood and consequences of accepted medical conditions. These crew health and performance inputs are grouped by common datasets and analysis models. Use cases are derived to research new clinical scenarios, architectural development and workflows. Implementation research is conducted with protypes to inform assumptions and derive requirements. The project also establishes how externally developed analysis and approaches can be added to expand a clinical decision support system and thus highlight how a comprehensive system can be globally developed with collaborators. This presentation will cover example scenarios from the CDS ConOps and the method to derive them. One example scenario will be CDSS alerting an increased kidney stone risk during a mission, with diagnosis and treatment options provided during the intervention.

clinical decision support↗

Past Performance analysis of HPOTP bearings

The past performance analysis conducted on three High Pressure Oxygen Turbopump (HPOTP) bearings from the Space Shuttle Main Engine is presented. Metallurgical analysis of failed bearing balls and races, and wear track and crack configuration analyses were carried out. In addition, one bearing was tested in laboratory at very high axial loads. The results showed that the cracks were surface initiated and propagated into subsurface locations at relatively small angles. Subsurface cracks were much more extensive than was appeared on the surface. The location of major cracks in the races corresponded to high radial loads rather than high axial loads. There was evidence to suggest that the inner races were heated to elevated temperatures. A failure scenario was developed based on the above findings. According to this scenario the HPOTP bearings are heated by a combination of high loads and high coefficient of friction (poor lubrication). Different methods of extending the HPOTP bearing life are also discussed. These include reduction of axial loads, improvements in bearing design, lubrication and cooling, and use of improved bearing materials.

Bhat, B. N.↗

SimSup's Loop: A Control Theory Approach to Spacecraft Operator Training

Immersive simulation is a staple of training for many complex system operators, including astronauts and ground operators of spacecraft. However, while much has been written about simulators, simulation facilities, and operator certification programs, the topic of how one develops simulation scenarios to train a spacecraft operator is relatively understated in the literature. In this paper, an approach is presented for using control theory as the basis for developing the immersive simulation scenarios for a spacecraft operator training program. The operator is effectively modeled as a high level controller of lower level hardware and software control loops that affect a select set of system state variables. Simulation scenarios are derived from a STAMP-based hazard analysis of the operator's high and low level control loops. The immersive simulation aspect of the overall training program is characterized by selecting a set of scenarios that expose the operator to the various inadequate control actions that stem from control flaws and inadequate control executions in the different sections of the typical control loop. Results from the application of this approach to the Lunar Atmosphere and Dust Environment Explorer (LADEE) mission are provided through an analysis of the simulation scenarios used for operator training and the actual anomalies that occurred during the mission. The simulation scenarios and inflight anomalies are mapped to specific control flaws and inadequate control executions in the different sections of the typical control loop to illustrate the characteristics of anomalies arising from the different sections of the typical control loop (and why it is important for operators to have exposure to these characteristics). Additionally, similarities between the simulation scenarios and inflight anomalies are highlighted to make the case that the simulation scenarios prepared the operators for the mission.

LADEE↗

Technical Interchange Meeting Guidelines Breakout

Along with concept developers, the Systems Evaluation and Assessment (SEA) sub-element of VAMS will develop those scenarios and metrics required for testing the new concepts that reside within the System-Level Integrated Concepts (SLIC) sub-element in the VAMS project. These concepts will come from the NRA process, space act agreements, a university group, and other NASA researchers. The emphasis of those concepts is to increase capacity while at least maintaining the current safety level. The concept providers will initially develop their own scenarios and metrics for self-evaluation. In about a year, the SEA sub-element will become responsible for conducting initial evaluations of the concepts using a common scenario and metric set. This set may derive many components from the scenarios and metrics used by the concept providers. Ultimately, the common scenario\metric set will be used to help determine the most feasible and beneficial concepts. A set of 15 questions and issues, discussed below, pertaining to the scenario and metric set, and its use for assessing concepts, was submitted by the SEA sub-element for consideration during the breakout session. The questions were divided among the three breakout groups. Each breakout group deliberated on its set of questions and provided a report on its discussion.

Fong, Rob↗