Search NASA⌕ Search

SEARCH · Search NASA

Results for “operation scenarios”

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 37 records · Page 2
All sourcesNASA NTRSDOE OSTI
NASA NTRS2011

Spacesuit Portable Life Support System Breadboard (PLSS 1.0) Development and Test Results

A multi-year effort has been carried out at NASA-JSC to develop an advanced Extravehicular Activity (EVA) PLSS design intended to further the current state of the art by increasing operational flexibility, reducing consumables, and increasing robustness. Previous efforts have focused on modeling and analyzing the advanced PLSS architecture, as well as developing key enabling technologies. Like the current International Space Station (ISS) Extravehicular Mobility Unit (EMU) PLSS, the advanced PLSS comprises of three subsystems required to sustain the crew during EVA including the Thermal, Ventilation, and Oxygen Subsystems. This multi-year effort has culminated in the construction and operation of PLSS 1.0, a test rig that simulates full functionality of the advanced PLSS design. PLSS 1.0 integrates commercial off the shelf hardware with prototype technology development components, including the primary and secondary oxygen regulators, ventilation loop fan, Rapid Cycle Amine (RCA) swingbed, and Spacesuit Water Membrane Evaporator (SWME). Testing accumulated 239 hours over 45 days, while executing 172 test points. Specific PLSS 1.0 test objectives assessed during this testing include: confirming key individual components perform in a system level test as they have performed during component level testing; identifying unexpected system-level interactions; operating PLSS 1.0 in nominal steady-state EVA modes to baseline subsystem performance with respect to metabolic rate, ventilation loop pressure and flow rate, and environmental conditions; simulating nominal transient EVA operational scenarios; simulating contingency EVA operational scenarios; and further evaluating individual technology development components. Successful testing of the PLSS 1.0 provided a large database of test results that characterize system level and component performance. With the exception of several minor anomalies, the PLSS 1.0 test rig performed as expected; furthermore, many system responses trended in accordance with pre-test predictions.

Vogel, Matt R.↗
NASA NTRS2012

Photovoltaic Power System and Power Distribution Demonstration for the Desert RATS Program

A stand alone, mobile photovoltaic power system along with a cable deployment system was designed and constructed to take part in the Desert Research And Technology Studies (RATS) lunar surface human interaction evaluation program at Cinder Lake, Arizona. The power system consisted of a photovoltaic array/battery system. It is capable of providing 1 kW of electrical power. The system outputs were 48 V DC, 110 V AC, and 220 V AC. A cable reel with 200 m of power cable was used to provide power from the trailer to a remote location. The cable reel was installed on a small trailer. The reel was powered to provide low to no tension deployment of the cable. The cable was connected to the 220 V AC output of the power system trailer. The power was then converted back to 110 V AC on the cable deployment trailer for use at the remote site. The Scout lunar rover demonstration vehicle was used to tow the cable trailer and deploy the power cable. This deployment was performed under a number of operational scenarios, manned operation, remote operation and tele-robotically. Once deployed, the cable was used to provide power, from the power system trailer, to run various operational tasks at the remote location.

Colozza, Anthony↗
NASA NTRS2018

The OpenSE Cookbook: A Practical, Recipe Based Collection of Patterns, Procedures, and Best Practices for Executable Systems Engineering for the Thirty Meter Telescope

The OpenSE Cookbook is an open-sourced collection of patterns, procedures, and best practices targeted for systems engineers who seek guidance on applying model-based and executable systems engineering (MBSE) using SysML. Its content has emerged from the system level modeling effort on the European Framework Program 6 (FP6) and the Thirty Meter Telescope (TMT). The TMT MBSE approach applied the Executable Systems Engineering Method (ESEM) and the open-source Engineering Environment (OpenMBEE) to specify, analyze, and verify requirements of TMT’s Alignment and Phasing System (APS) and the Narrow Field Infrared Adaptive Optics System (NFIRAOS). In these applications, implicit dependencies are made explicit in a formal model through the use of ESEM, OpenMBEE, and SysML modeling constructs. The value proposition for applying this MBSE approach was to establish precise requirements and fine-grained traceability to system designs, and to verify key requirements beginning early in development. The integration of ESEM and the OpenMBEE tooling infrastructure (providing linked-data and web-operability) is a significant added value for the MBSE approach. The APS is responsible for the overall pre-adaptive optics wavefront quality, using starlight to measure wavefront errors and align the TMT optics. In the formally integrated and executable SysML model, simulations are performed to analyze the impact of changed requirements and verify specified constraints for various operational scenarios. The APS team used several modeling patterns to capture information such as the requirements, the operational scenarios, involved subsystems and their interaction points, the estimated or required time durations, and the mass and power consumption. Adaptive optics systems are designed to sense real-time atmospheric turbulence and correct the telescope’s optical beam to remove its effect. The system model for the adaptive optics operational modes was developed to capture sequence behaviors and operational scenarios to run Monte-Carlo simulations for verifying acquisition time, observing efficiency, and operational behavior requirements. The model is particularly useful for investigating the effect of parallelization, identifying interface issues, and re-ordering sequence acquisition tasks. A former version of the Cookbook (which is now updated to MBSE challenges, goals, and lessons learned) included modeling guidelines and conventions for all system aspects, hierarchy levels, and views, which were developed during for the Active Phasing Experiment (APE), an opto-mechatronical system technology demonstrator for the Extremely Large Telescope (ELT). The Cookbook utilizes the above mentioned system models as real-world case-studies to demonstrate and document the applications of the recipes, providing also instructional examples and addressing the available tooling support. The Cookbook is accompanied by a number of SysML models and aodel libraries which facilitate model authoring and maintenance. The Cookbook covers the different aspects of Systems Engineering such as management of Requirements, Design (behavior and structure), Interfaces, Interdisciplinary Integration, Analysis, Trade Studies, and Technical Resources. This paper presents the background, motivation, architecture, and highlights some key content of the Cookbook. For example, interface management, error budget management, requirements verification, Monte Carlo driven analysis, and timing analysis of operational scenarios. The paper discusses how the capabilities of OpenMBEE contributed significantly to the adoption of executable systems engineering.

Brower, Eric↗
NASA NTRS2012

Spacesuit Portable Life Support System Breadboard (PLSS 1.0) Development and Test Results

A multi-year effort has been carried out at the Johnson Space Center to develop an advanced EVA PLSS design intended to further the current state of the art by increasing operational flexibility, reducing consumables, and increasing robustness. This multi-year effort has culminated in the construction and operation of PLSS 1.0, a test rig that simulates full functionality of the advanced PLSS design. PLSS 1.0 integrates commercial off-the-shelf hardware with prototype technology development components, including the primary and secondary oxygen regulators, ventilation loop fan, Rapid Cycle Amine (RCA) swingbed, and Spacesuit Water Membrane Evaporator (SWME). PLSS 1.0 was tested from June 17th through September 30th, 2011. Testing accumulated 233 hours over 45 days, while executing 119 test points. An additional 164 hours of operational time were accrued during the test series, bringing the total operational time for PLSS 1.0 testing to 397 hours. Specific PLSS 1.0 test objectives assessed during this testing include: (1) Confirming prototype components perform in a system level test as they have performed during component level testing, (2) Identifying unexpected system-level interactions (3) Operating PLSS 1.0 in nominal steady-state EVA modes to baseline subsystem performance with respect to metabolic rate, ventilation loop pressure and flow rate, and environmental conditions (4) Simulating nominal transient EVA operational scenarios (5) Simulating contingency EVA operational scenarios (6) Further evaluating prototype technology development components Successful testing of the PLSS 1.0 provided a large database of test results that characterize system level and component performance. With the exception of several minor anomalies, the PLSS 1.0 test rig performed as expected. Documented anomalies and observations include: (1) Ventilation loop fan controller issues at high fan speeds (near 70,000 rpm, whereas the fan speed during nominal operations would be closer to 35,000 rpm) (2) RCA performance at boundary conditions, including carbon dioxide and water vapor saturation events, as well as reduced vacuum quality (3) SWME valve anomalies (4 documented cases where the SWME failed to respond to a control signal or physically jammed, preventing SWME control) (4) Reduction of SWME hollow fiber hydrophobicity and significant reduction of the SWME degassing capability after significant accumulated test time.

Watts, Carly A.↗
NASA NTRS1999

Payload Operations

The objective of this paper is to provide the future ISS scientist and/or engineer a sense of what ISS payload operations are expected to be. This paper uses a real-time operations scenario to convey this message. The real-time operations scenario begins at the initiation of payload operations and runs through post run experiment analysis. In developing this scenario, it is assumed that the ISS payload operations flight and ground capabilities are fully available for use by the payload user community. Emphasis is placed on telescience operations whose main objective is to enable researchers to utilize experiment hardware onboard the International Space Station as if it were located in their terrestrial laboratory. An overview of the Payload Operations Integration Center (POIC) systems and user ground system options is included to provide an understanding of the systems and interfaces users will utilize to perform payload operations. Detailed information regarding POIC capabilities can be found in the POIC Capabilities Document, SSP 50304.

Cissom, R. D.↗
NASA NTRS2020

Identification of Scenarios for System Interface Design Evaluation: CAST SE-210 Output 2 Report 5 of 6

This report is one in a series of reports describing research to develop enhanced approaches to design and evaluation of flight deck interaction. The research was conducted to support the Commercial Aviation Safety Team (CAST) response to incidents and accidents caused by failure of the flight crew to maintain aircraft attitude or energy state awareness. This report partially responds to Safety Enhancement (SE) 210.2 (CAST, 2014) by describing development of operational scenarios for evaluation of flight crew interaction. Evaluations of human performance with an interface rely on asking humans to perform operational tasks in an appropriate operational context. The report includes the major sources of material for developing operational scenarios—which include system state, operational tasks, operational context, and safety events—and a method for developing an appropriate set of operational scenarios for interface evaluation.

commercial aviation↗
NASA NTRS2007

Surface Operations: Two Case Studies of Simulated Lunar Operations

In September 2007, a team of scientists and engineers from several NASA centers participated in a field exercise at Meteor Crater, Arizona. The tests in this field exercise utilized recently developed robots of varying scales and capabilities and humans in pressurized space suits. Two examples of operations performed in the field are presented: a surface operations scenario involving suited crew supported by a number of mobile robots and setup operations for accessing a crater. The surface operations scenario simulated the end of a crew sortie and involved the following agents: 1) Suit subjects from Johnson Space Center s (JSC) advanced spacesuit laboratory 2) JSC's unpressurized crewed rover testbed, SCOUT 3) The Jet Propulsion Laboratory s (JPL) rough terrain, payload carrying robot, ATHLETE 4) JSC's Astronaut assist robot, Robonaut 5) Ames Research Center's (ARC) inspection robot, K-10. Operations began with ATHLETE positioning a pressurized rover compartment (PRC) as two crew members drove the SCOUT unpressurized rover from the field. The crew dismounted SCOUT, walked to the PRC for recharging. Robonaut then removed a sample box from the SCOUT equipment tray. K-10 then performed a drive around inspection of SCOUT, assembling a mosaic image. Lastly, the SCOUT vehicle was remotely driven to the next site. The setup operations for crater access scenario involved ATHLETE and Robonaut. This scenario began with Robonaut approaching ATHLETE and extracting a tether line. ATHLETE then extracted a drill and drilled an anchor into the surface. Robonaut then reconnected the tether to the anchor and backed away. ATHLETE is then ready to descend into the crater. This descending into the crater step is currently in the planning phase.

Bluethmann, William J.↗
NASA NTRS2011

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.↗
NASA NTRS2015

Operating in "Strange New Worlds" and Measuring Success - Test and Evaluation in Complex Environments

Software tools are being developed by the Autonomy Incubator at NASA's Langley Research Center that will provide an integrated and scalable capability to support research and non-research flight operations across several flight domains, including urban and mixed indoor-outdoor operations. These tools incorporate a full range of data products to support mission planning, approval, flight operations, and post-flight review. The system can support a number of different operational scenarios that can incorporate live and archived data streams for UAS operators, airspace regulators, and other important stakeholders. Example use cases are described that illustrate how the tools will benefit a variety of users in nominal and off-nominal operational scenarios. An overview is presented for the current state of the toolset, including a summary of current demonstrations that have been completed. Details of the final, fully operational capability are also presented, including the interfaces that will be supported to ensure compliance with existing and future airspace operations environments.

Qualls, Garry↗
NASA NTRS1990

Operations influence on Space Station Freedom

The Space Station Freedom is the first experience for NASA and its international partners in building a spacecraft that will be operated and maintained over a multi-year lifetime and that will be permanently manned. To ensure it functions safely and effectively, the operations community has become involved much earlier than in previous U.S. programs. This involvement has taken the form of defining requirements and analyzing the configuration, systems, and elements in terms of operations suitability and supportability. This early participation has had many effects on the definition and design of the Freedom Station. Examples of operations participation include the development of various operations concepts, design reference missions, contingency operations scenarios, and assembly operations assessments.

Accola, Anne L.↗
NASA NTRS2019

Analysis of Interactions Between Urban Air Mobility (UAM) Operations and Conventional Traffic in Urban Areas: Traffic Alert and Collision Avoidance System (TCAS) Study for UAM Operations

This paper presents results on potential interaction effects from UAM (Urban Air Mobility) operations integrated into current operational scenarios by evaluating if/where/how Traffic alert and Collision Avoidance System (TCAS) alerts are triggered on-board commercial aircraft. A range of operational scenarios are evaluated with combinations of UAM vehicle route, speed, altitude, and direction along the DFW (Dallas-Fort Worth) "spine route." The effect of UAM altitude uncertainty on the above is also explored. The analysis was done for both South flow and North flow configurations of DFW. When UAM operations are deterministic, no TCAS RAs (Resolution Advisories) are issued. However, UAM altitude uncertainties point out geographic areas of concern with the associated severity of interactions.

Airspace↗
NASA NTRS2012

Autonomous Mission Operations

NASA's Advanced Exploration Systems Autonomous Mission Operations (AMO) project conducted an empirical investigation of the impact of time-delay on todays mission operations, and of the effect of processes and mission support tools designed to mitigate time-delay related impacts. Mission operation scenarios were designed for NASA's Deep Space Habitat (DSH), an analog spacecraft habitat, covering a range of activities including nominal objectives, DSH system failures, and crew medical emergencies. The scenarios were simulated at time-delay values representative of Lunar (1.2-5 sec), Near Earth Object (NEO) (50 sec) and Mars (300 sec) missions. Each combination of operational scenario and time-delay was tested in a Baseline configuration, designed to reflect present-day operations of the International Space Station, and a Mitigation configuration in which a variety of software tools, information displays, and crew-ground communications protocols were employed to assist both crews and Flight Control Team (FCT) members with the long-delay conditions. Preliminary findings indicate: 1) Workload of both crew members and FCT members generally increased along with increasing time delay. 2) Advanced procedure execution viewers, caution and warning tools, and communications protocols such as text messaging decreased the workload of both flight controllers and crew, and decreased the difficulty of coordinating activities. 3) Whereas crew workload ratings increased between 50 sec and 300 sec of time-delay in the Baseline configuration, workload ratings decreased (or remained flat) in the Mitigation configuration.

Mission Operations↗
NASA NTRS2008

A Scenario-Based Process for Requirements Development: Application to Mission Operations Systems

The notion of using operational scenarios as part of requirements development during mission formulation (Phases A & B) is widely accepted as good system engineering practice. In the context of developing a Mission Operations System (MOS), there are numerous practical challenges to translating that notion into the cost-effective development of a useful set of requirements. These challenges can include such issues as a lack of Project-level focus on operations issues, insufficient or improper flowdown of requirements, flowdown of immature or poor-quality requirements from Project level, and MOS resource constraints (personnel expertise and/or dollars). System engineering theory must be translated into a practice that provides enough structure and standards to serve as guidance, but that retains sufficient flexibility to be tailored to the needs and constraints of a particular MOS or Project. We describe a detailed, scenario-based process for requirements development. Identifying a set of attributes for high quality requirements, we show how the portions of the process address many of those attributes. We also find that the basic process steps are robust, and can be effective even in challenging Project environments.

MOS↗
NASA NTRS2015

A Tool for Model-Based Generation of Scenario-driven Electric Power Load Profiles

Power consumption during all phases of spacecraft flight is of great interest to the aerospace community. As a result, significant analysis effort is exerted to understand the rates of electrical energy generation and consumption under many operational scenarios of the system. Previously, no standard tool existed for creating and maintaining a power equipment list (PEL) of spacecraft components that consume power, and no standard tool existed for generating power load profiles based on this PEL information during mission design phases. This paper presents the Scenario Power Load Analysis Tool (SPLAT) as a model-based systems engineering tool aiming to solve those problems. SPLAT is a plugin for MagicDraw (No Magic, Inc.) that aids in creating and maintaining a PEL, and also generates a power and temporal variable constraint set, in Maple language syntax, based on specified operational scenarios. The constraint set can be solved in Maple to show electric load profiles (i.e. power consumption from loads over time). SPLAT creates these load profiles from three modeled inputs: 1) a list of system components and their respective power modes, 2) a decomposition hierarchy of the system into these components, and 3) the specification of at least one scenario, which consists of temporal constraints on component power modes. In order to demonstrate how this information is represented in a system model, a notional example of a spacecraft planetary flyby is introduced. This example is also used to explain the overall functionality of SPLAT, and how this is used to generate electric power load profiles. Lastly, a cursory review of the usage of SPLAT on the Cold Atom Laboratory project is presented to show how the tool was used in an actual space hardware design application.

power load profile↗
NASA NTRS1986

Study of selected tether applications in space, phase 3, volume 2

The results of a Phase 3 study of two Selected Tether Applications in Space (STAIS); deorbit of a Shuttle and launch of an Orbital Transfer Vehicle (OTV), both from the space station using a tether were examined. The study objectives were to: perform a preliminary engineering design, define operational scenarios, develop a common cost model, perform cost benefits analyses, and develop a Work Breakdown Structure (WBS). Key features of the performance analysis were to identify the net increases in effective Shuttle cargo capability if tethers are used to assist in the deorbit of Shuttles and the launching of the OTVs from the space station and to define deployer system designs required to accomplish these tasks. Deployer concepts were designed and discussed. Operational scenarios, including timelines, for both tethered and nontethered Shuttle and OTV operations at the space station were evaluated. A summary discussion of the Selected Tether Applications Cost Model (STACOM) and the results of the cost benefits analysis are presented. Several critical technologies needed to implement tether assisted deployment of payloads are also discussed. Conclusions and recommendations are presented.

Source record↗
NASA NTRS1990

Navigation accuracies for GPS demonstration on Topex/Poseidon

When Topex/Poseidon, is launched in June 1992, the joint United States/French oceanographic satellite mission will carry a developmental Global Positioning System (GPS) receiver on board to support the planned GPS demonstration experiment. The navigation operations aspect of the demonstration will develop software and operational procedures for the GPS Data Processing Facility (GDPF) at NASA's Jet Propulsion Laboratory. This paper presents simulations and covariance analysis of operational scenarios in support of the GDPF. Multi-orbit filter techniques using GPS carrier phase and P-code pseudo-range are studied both to tune the filter parameters and to determine feasible arc lengths for use in operations. In addition, a baseline operational scenario is presented with performance results given in terms of end-to-end processing times and computational loading based on a prototype version of the operational software.

Williams, B. G.↗
NASA NTRS2011

Method and system for fault accommodation of machines

A method for multi-objective fault accommodation using predictive modeling is disclosed. The method includes using a simulated machine that simulates a faulted actual machine, and using a simulated controller that simulates an actual controller. A multi-objective optimization process is performed, based on specified control settings for the simulated controller and specified operational scenarios for the simulated machine controlled by the simulated controller, to generate a Pareto frontier-based solution space relating performance of the simulated machine to settings of the simulated controller, including adjustment to the operational scenarios to represent a fault condition of the simulated machine. Control settings of the actual controller are adjusted, represented by the simulated controller, for controlling the actual machine, represented by the simulated machine, in response to a fault condition of the actual machine, based on the Pareto frontier-based solution space, to maximize desirable operational conditions and minimize undesirable operational conditions while operating the actual machine in a region of the solution space defined by the Pareto frontier.

Goebel, Kai Frank↗
NASA NTRS2015

In-Space Transportation for NASA's Evolvable Mars Campaign

As the nation embarks on a new and bold journey to Mars, significant work is being done to determine what that mission and those architectural elements will look like. The Evolvable Mars Campaign, or EMC, is being evaluated as a potential approach to getting humans to Mars. Built on the premise of leveraging current technology investments and maximizing element commonality to reduce cost and development schedule, the EMC transportation architecture is focused on developing the elements required to move crew and equipment to Mars as efficiently and effectively as possible both from a performance and a programmatic standpoint. Over the last 18 months the team has been evaluating potential options for those transportation elements. One of the key aspects of the EMC is leveraging investments being made today in missions like the Asteroid Redirect Mission (ARM) mission using derived versions of the Solar Electric Propulsion (SEP) propulsion systems and coupling them with other chemical propulsion elements that maximize commonality across the architecture between both transportation and Mars operations elements. This paper outlines the broad trade space being evaluated including the different technologies being assessed for transportation elements and how those elements are assembled into an architecture. Impacts to potential operational scenarios at Mars are also investigated. Trades are being made on the size and power level of the SEP vehicle for delivering cargo as well as the size of the chemical propulsion systems and various mission aspects including Inspace assembly and sequencing. Maximizing payload delivery to Mars with the SEP vehicle will better support the operational scenarios at Mars by enabling the delivery of landers and habitation elements that are appropriately sized for the mission. The purpose of this investigation is not to find the solution but rather a suite of solutions with potential application to the challenge of sending cargo and crew to Mars. The goal is that, by building an architecture intelligently with all aspects considered, the sustainable Mars program wisely invests limited resources enabling a long-term human Mars exploration program.

Percy, Thomas K.↗