Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “conops”

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 181 records · Page 10

Using Earth-based Operational Field Tests as High-Fidelity Analogs for Planetary Surface Exploration

NASA is preparing to land the first woman and first person of color on the Moon within the next decade and establishing a permanent sustainable human presence before sending humans onto Mars. To ensure the success of these missions, NASA has performed operational testing in terrestrial, aquatic, and laboratory analog environments that simulate Lunar and Martian environmental characteristics to evaluate exploration concepts of operations (ConOps), engineering design requirements, science support needs, mission operations techniques, and crew training.

B. A. Janoiko↗

Defining Services, Functions, and Capabilities for an Advanced Air Mobility (AAM) In-time Aviation Safety Management System (IASMS)

NASA’s vision for Advanced Air Mobility (AAM) Mission is to help emerging aviation markets to safely develop an air transportation system that moves people and cargo between places previously not served or underserved by aviation. The integration of new operational paradigms and vehicle classes in this system requires a transformation of the National Airspace System (NAS) that includes substantive changes critical for assuring safety. These changes are compelled by unique challenges posed by AAM to the safety management system (SMS). These challenges were assessed by committees of the National Academies in their reports on a vision for an In-time Aviation Safety Management System (IASMS) and a blueprint for AAM [1,2]. In their description of an IASMS, the top recommendation was development of a concept of operations (ConOps) for IASMS. This paper describes the high-priority recommendations from the National Academies for its IASMS vision and how they are addressed through a distributed system-of-systems architecture. The IASMS architecture is structured on the services, functions, and capabilities (SFCs) necessary for In-time System-wide Safety Assurance (ISSA)initially developed for urban air mobility (UAM). The paper then posits where these SFCs would reside across vehicles, airspace, or service suppliers such as Supplemental Data Service Providers (SDSPs), and how SFCs scale with increasing complexity in design and operations of AAM. SFCs are foundational building blocks for a system that targets an individual or family of risks using a Monitor-Assess-Mitigate risk paradigm for anomalies, precursors and trends. An IASMS could be conceived that uses a portfolio of SFCs for AAM in general or prioritizes SFCs for a specific domain or operation.

K Ellis↗

An Approach for Identifying IASMS Services, Functions, and Capabilities From Data Sources

Assuring safety in the NAS with the inclusion of new entrants that are part of Advanced Air Mobility (AAM) will require overcoming unique safety challenges that result from combining innovative technologies with novel airspace concepts for moving people and cargo using semi-autonomous/autonomous vehicles. Overcoming these AAM safety assurance challenges is the focus of the In-time Aviation Safety Management System (IASMS). The IASMS Concept of Operations (ConOps) describes an interconnected set of services, functions, and capabilities (SFCs)designed to manage operational risks, identify unknown risks, and inform system design to mitigate risk. This paper describes a broad approach for identifying SFCs involving technology trends in research, assessment of known and unknown risks in safety reports, and causal and contributing factors in aviation accidents and incidents. This approach leverages these sources to identify potential SFCs that enable the Monitor, Assess, and Mitigate (M-A-M)functionality that represents the enabling framework of the IASMS.

Kyle Ellis↗

Vertiport Automation Software Architecture and Requirements

The purpose of Vertiport Automation Software Architecture and Requirements was developed to mature the Vertiport Automation System (VAS) described in the High-Density Automated Vertiport ConOps, into a set of artifacts that enable the development of a VAS prototype. The scope of document was to develop: (1) A VAS Software Architecture diagram that logically organizes VAS functionality into specific software components; (2) VAS Software Trade Study identifying existing commercial products and NASA research that can be used in part or with modifications to fulfill VAS functionality. (3) A set of VAS Functional Requirements which decompose the VAS concept into software functionality, including any interfaces and data flows needed; (4) A set of VAS Test Approaches describing a methodology for verification of the VAS Functional Requirements; and (5) An application user experience (UX) design study describing the general features needed in a VAS user interface.

Advanced Air Mobility↗

Dynamic Radioisotope Power System (DRPS) Permanently Shadowed Region (PSR) Demonstrator Rover

This conceptual design study investigated trading several Dynamic Radioisotope Power Systems (DRPS) in development to supply power to a lunar science rover which operates for long periods (months) in permanently shadowed regions (PSR) over many years. The design was conducted by the Compass team and relied heavily on the planned VIPER rover design, which is limited to only a few hours of operations in PSRs and less than a month near the south pole. As such this conceptual design shows what a DRPS can do for a follow-on type VIPER rover. In addition to the long duration, go anywhere DRPS power system, the Compass team added a communications system that utilizes the Gateway spacecraft as a relay node for nearly 24/7 communications link to the DRPS rover in lunar craters not visible from the earth. The Compass design includes a notional conops, launch and delivery, subsystem designs of power, mobility, structures, science, command and data handling, communications, guidance and control, and thermal. The thermal design was especially important due the low temperatures in PSRs where the science environment needs to be shielded from the waste heat from the DRPS.

Dynamic Radioisotope Power Systems↗

Evolving the Design of a Volcanic Monitoring UAS over Several Flight Campaigns

A multi-organization effort has been underway for several years to develop and validate the use of small unmanned aircraft systems (UAS) for volcanic monitoring. The overall goal is to develop the aircraft, supporting systems, concept of operations, scientific payloads and regulatory framework to allow regular and reliable sampling in challenging and dynamic atmospheric conditions around volcanic summits. Central to this effort has been the development and refinement of the “S2” aircraft, which contains a tightly integrated system consisting of the airframe, avionics, and payload sensors specifically designed to measure atmospheric properties around volcanic plumes. The aircraft has a 3-meter wingspan and can carry a 2.3 kg payload for up to 100 km while operating at altitudes up to 6,000 m. To date, the system has been flown in Costa Rica to sample CO2 gases around Turrialba Volcano (Costa Rica), in Hawaii to assess the 2018 eruption of Kīlauea with several different sensors, and is currently planned for deployment in Alaska for gas sampling and photogrammetry at Makushin Volcano. Before and after each deployment, all aspects of the system and concept of operations (CONOPS) were extensively examined and modified to improve the safety and performance. This has culminated in the upcoming deployment which will fly up to 30 km - beyond visual line of sight for the first time. This expansion of the operational range through additional safety features and redundancy will pave the way for monitoring and accessing areas that were previously very difficult to reach from both a technical and regulatory perspective. These developments can be extended to a variety of missions requiring UAS for atmospheric sampling, specifically ones that would benefit from beyond visual line of sight operations or flights into harsh or difficult atmospheric environments.

UAS↗

SWS TechTalk: System Modeling in Support of IASMS Definition

Topic: System modeling in support of IASMS definition 1. What is system modeling? 2. What are the building blocks necessary for a formal model of the IASMS concept of operations, or “conops”, and “architectures”? 3. Scenario modeling to support safety demonstrator planning and technology integration The System Wide Safety Tech Talks will offer a great opportunity to keep up on each other’s work and accomplishments, as well as an opportunity to find areas of potential collaboration. The topics of these technical talks will cover any papers, presentations, special trips, or meetings that are a part of SWS.

IASMS↗

A Model-Based Systems Engineering Evaluation of the Evolution to an In-Time Aviation Safety Management System

In 2018, as result of a recommendation from the National Academies, NASA began to prototype an In-Time Aviation Safety Management System (IASMS). The purpose of the IASMS is to enable innovative aviation operations and greater heterogeneity of the overall National Airspace (NAS) by automating much of the safety monitoring, assessment, and risk and hazard mitigation function present in today’s Safety Management Systems (SMS). NASA has worked together with early industry collaborators to understand how such a system might work and has published several early Concepts of Operation (ConOps) and other technical memoranda that illustrate the primary considerations for selected aviation domains. The shift from an SMS to an IASMS is predicated on several assumptions, including: 1.) automating safety functions will decrease the amount of time necessary for risk and hazard identification and analysis, making it more likely that safety concerns are understood ‘in-time’ to mitigate them, and 2.) an IASMS will allow easier tailoring of safety management processes to the particular risks and hazards inherent to that aviation operation. In this paper, we begin to validate these assumptions through the use of Model-Based Systems Engineering (MBSE).

IASMS↗

Gateway bi-propellant refueling development testing and model validation activities

The Gateway is an upcoming long term lunar exploration program to be completed by NASA in partnership with ESA and other US and international partners. The system design of the Gateway contains both a high performance Xenon based Solar Electric Propulsion system, as well as a bi-propellant attitude control system. Both propulsion systems are designed for on-orbit refueling to enable long life performance of the Gateway. The ESPRIT-RM is a module which will expand the pressurized volume of Gateway, while also providing refueling capability for both the Xenon and Bipropellant propulsion systems, therefore extending the Gateway life on orbit. As part of the Gateway bi-propellant refueling system development, a simplified fluidic breadboard system was created to evaluate system performance and response using simulant fluids. The test plan includes verification activities with simulant (water, HFE-7100) to verify joined subsystem behavior in the critical operations, including propellant transfer demonstration between modules, transient tests and venting tests. Integrated testing occurred at TASUK in collaboration with NASA to support joint verification activities to de-risk the major functions of the ESPRIT BTS and the overall CONOPS of the refueling of the Gateway chemical propulsion system. Initially collected test data from the system testing is presented, as well as initial model validation, and correlated to collected high frequency test data and system response is shown. Initially collected data has shown the architected system performance is closing initial design assumptions, but much forward work remains to characterize and develop the system.

Christopher Daniel Radke↗

Demand Capacity Balancing at Vertiports for Initial Strategic Conflict Management of Urban Air Mobility Operations

Urban Air Mobility (UAM) is a new transportation concept that enables highly automated, cooperative, passenger or cargo-carrying air transportation services in and around urban areas. To achieve the high level of operational density and complexity desired by the UAM community, an airspace system that allows UAM operators to readily access and operate safely and efficiently in the airspace is needed. This airspace system will require air traffic management designed to reduce the risk of conflicts and loss of separation between UAM flights. In general, strategic conflict management is considered as the first layer of conflict management for safe flight operations to condition the traffic to reduce the need for airborne separation provision, the second layer of conflict management. Demand Capacity Balancing (DCB) is one of the concept components to achieve strategic conflict management. DCB strategically evaluates traffic demand and resource capacities to allow UAM operators to determine when, where and how they operate, while mitigating conflicting needs for airspace and vertiport capacity. DCB can be applied whenever UAM demand exceeds the capacity in airspace or at vertiports. As the UAM ecosystem evolves with advanced technologies and matured operational procedures, more complicated conflict management will likely be needed. In the current UAM ‘Concept of Operation (ConOps) 1.0’ operational stage defined by FAA, however, it will be meaningful to explore the demand capacity balancing at vertiports only, as an initial strategic conflict management approach for UAM operations because vertiport capacity seems to be a bottleneck of UAM traffic. For this research, we developed a demand-capacity imbalance detection and resolution service for UAM. This DCB service identifies the demand from operators and compares the demand to a given capacity at the shared resources (i.e., vertiports) over the upcoming time horizon which is divided into time bins having a constant interval. When a new flight plan is submitted, the algorithm embedded in the DCB service checks the available time bins based on the desired departure time and estimated arrival time at origin and destination vertiports, respectively. If the time bins for the originally desired times are already occupied by other flights (i.e., demand is at or above capacity), the algorithm finds the next available time bins for takeoff and landing and shifts the conflicting departure time to the earliest time that satisfies the capacity constraints at both origin and destination vertiports. The details of the algorithm will be described in the final manuscript. Figure 1 shows that the proposed DCB algorithm works well for a sample traffic scenario. In this example, a total of 144 flights, split between two operators, are planned over 2 hours, traveling 10 routes between five vertiports. In the heatmaps, the horizontal axis shows 12 time bins where each bin represents a 12-minute interval, and the vertical axis shows five vertiports. The number in each cell shows the number of operations, counting both departures and arrivals, at a specific vertiport in each time bin. For the given capacity of 2 operations/vertiport/bin, Figure 1 shows that the original demand sometimes exceeds the capacity, but the modified demand is reduced to the given capacity after resolving demand-capacity imbalances. When UAM flights are operated, it is expected that many practical issues would arise in the federated system architecture with multiple operators. UAM operators may experience a time synchronization issue due to communication delay between operator and vehicle. UAM vehicles would fly at different flight speeds, depending on vehicle models. Actual departure and arrival times can have large variations, compared to the schedule. The lead time from flight plan submission to desired departure time can vary by service type (e.g., regular shuttle service vs. on-demand service). Using the proposed DCB algorithm, we also investigated how the actual flight schedule and DCB performance are affected by these uncertainties such as unsynchronized times between operators, flight speed differences, lead time differences, and departure time errors. The final manuscript will include the background of this research work, the description of the DCB algorithm and its use cases with traffic scenarios. It will also provide the analytical results about the impact of various uncertainties that can occur in actual UAM operations on the DCB at vertiports, in terms of demand distribution changes, number of simultaneous operations, and delay propagation.

Urban Air Mobility↗

Joint Development Testing of the Integrated Gateway-Esprit Bipropellant Refuelling System

The Gateway is an upcoming long term lunar exploration program to be completed by NASA in partnership with ESA and other US and international partners. The system design of the Gateway contains both a high performance Xenon based Solar Electric Propulsion system, as well as a bi-propellant attitude control system. Both propulsion systems are designed for on-orbit refuelling to enable long life performance of the Gateway. The ESPRIT-RM is a module which will expand the pressurized volume of Gateway, while also providing refuelling capability for both the Xenon and Bipropellant propulsion systems, therefore extending the Gateway life on orbit. As part of the Gateway bi-propellant refuelling system development, a simplified fluidic breadboard system was created to evaluate system performance and response using simulant fluids. The test plan includes verification activities with simulant (water, HFE-7100) to verify joined subsystem behaviour in the critical operations, including propellant transfer demonstration between modules, transient tests and venting tests. Integrated testing will occur at TASUK in collaboration with NASA to support joint verification activities to de-risk the major functions of the ESPRIT Bipropellant Transfer Subsystem (BTS) and the overall CONOPS of the refuelling of the Gateway chemical propulsion system. Initially collected test data is presented and has shown the architected system performance is closing initial design assumptions, but much forward work is identified to continue to characterize and develop the system.

Sebastian Hill↗

A Model-Based Systems Engineering Evaluation of the Evolution to an In-Time Aviation Safety Management System

In 2018, as result of a recommendation from the National Academies, NASA began to prototype an In-Time Aviation Safety Management System(IASMS). The purpose of the IASMS is to enable innovative aviation operations and greater heterogeneity of the overall National Airspace (NAS) by automating much of the safety monitoring, assessment, and risk and hazard mitigation functionspresent in today’s Safety Management Systems (SMS). NASA has worked together with early industry collaborators to understand how such a system might work and has published several early Concepts of Operation (ConOps) and other technical memoranda that illustrate the primary considerations for selected aviation domains. The shift from an SMS to an IASMS is predicated on several assumptions, including: 1.) automating safety functions will decrease the amount of time necessary for risk and hazard identification and analysis, making it more likely that safety concerns are understood ‘in-time’ to mitigate them, and 2.) an IASMS will allow easier tailoring of safety management processes to the particular risks and hazards inherent to that aviation operation. In this paper, we begin to validate these assumptions through the use of Model-Based Systems Engineering (MBSE).

In-time Aviation Safety Management System↗

Design and Analysis of Corridors for UAM Operations

Urban Air Mobility (UAM) is predicted to provide alternate modes of transportation for cargo and passengers in the urban areas. Integration of UAM operations into the National Airspace System is a challenge especially around large airport. The Federal Aviation Administration’s (FAA) UAM Concept of Operations (ConOps) suggests new airspace structures for UAM operations such as corridors where FAA air traffic control (ATC) will not be expected to provide services. This paper presents a design for corridors in the Dallas Fort Worth (DFW) area that attempts to minimize air traffic controller interactions with UAM pilots and operators. The corridor and vertiports are then analyzed with respect to Class B separation criteria and wake advisory criteria. The results show that for the corridors designed for the DFW area and presented in this research, in some cases Class B separation criteria are not available between UAM corridors and legacy traffic due to the geometry of the airport. It shows that wake advisory criteria were not met for some segments in North Flow traffic but were generally met in South Flow. This means that some corridor segments at DFW airport will not be available for a given airport flow and may need new placements, which need further investigation.

Urban Air Mobility↗

Discovery Synchronization Service (DSS) for UAM

NASA's ATM-X UAM Subproject recently completed the “X4 Strategic Conflict Management Simulation” with seven NC-1 airspace partners to develop and test initial UAM airspace management capabilities, including the Provider of Services for UAM (PSU), to enable strategic conflict management of UAM operations. The simulation environment leveraged the notional architecture from FAA NextGen UAM ConOps v1.0 and used technologies developed as part of UTM standards and applied them to UAM. One of the main technologies used was the Discovery and Synchronization Service (DSS) and some gaps in applying it to UAM were identified during X4. In this Technical Interchange Meeting (TIM), we will share the technical findings from the simulation and welcome industry feedback.

UAM↗

Validation of Fitness for Duty Standards Using Pre- and Post-Flight Capsule Egress and Suited Functional Performance Tasks in Simulated Reduced Gravity

The transition between gravity environments will involve one of the most complex, high-risk phases of any mission. For example, the reduced functional capacity caused by physiological deconditioning adaptations in microgravity coupled with the stressors of re-entry into partial gravity environments will increase risks to crew, even with rigorous adherence to inflight countermeasures. Quantification of the astronauts’ post-landing functional performance is necessary to design ConOps for exploration missions. Specifically, these two high-risk scenarios may be required to be performed soon after gravity transitions: • Nominal and/or emergency unassisted capsule egress task after return to Earth • Planetary extravehicular activity (EVA) soon after landing on Mars or the Moon This study is broken down into two phases. Phase 1: A feasibility study that will assess the overall feasibility and demonstrate the capability to do these tasks shortly after landing. Phase 2: the full Egress Fitness study, which is part of the CIPHER complement. This study uses a task-based approach to characterize functional performance of these high-risk scenarios in long-duration ISS crewmembers before flight and shortly after return to Earth. Prior to any testing, each astronaut subject completes a suit fit check to ensure adequate sizing and a mobility assessment to confirm completion of the EVA tasks. Pilot Egress Fitness pre-flight and post-flight testing includes an Earth-based emergency egress out of a functional capsule mockup and a short Mars gravity EVA simulation including suit donning, hatch egress, ladder descent, task board cable operations, baggage transfer over sand/rocky regolith, alignment with a rear entry port, and suit egress. Pre-flight testing will occur at any time point prior to flight. Post-flight assessment is much more critical with the capsule egress test that will occur 1–4 hours after landing and the planetary EVA approximately 18–36 hours after landing. The CIPHER study will incorporate additional pre-flight sessions, longer EVA tasks that include traverse and geology sampling, and post-flight sessions on R+1, 4, and 8 to characterize the timeframe of recovery. Data collected for both tasks include task completion time, photo, and video. The EVA portion also includes collection of metabolic and heart rate. Pilot Egress Fitness study has completed both baseline and post-flight testing on four astronaut subjects, with all four able to complete post-flight EVA testing and three able to complete postflight capsule egress testing. Preliminary results observe individual physiological variations, which were to be expected but also suggest the need to carefully track the timeline from undock to landing to testing. Furthermore, some task performance instructions and equipment may need to be adjusted to ensure results are primarily physiological. These and other lessons learned will be addressed with minor protocol changes in the full CIPHER Egress Fitness study.

J R Norcross↗

HAT m:N Activity Overview

Since 2020, researchers from the Human Autonomy Teaming (HAT) Laboratory at NASA Ames Research Center have conducted human-in-the-loop (HITL) simulation research to study a new control paradigm for operations involving multiple remotely piloted aircraft systems (RPAS). Colloquially referred to as "m:N," this paradigm is characterized by multiple operators collaboratively controlling multiple vehicles between them. The m:N name expresses a ratio whereby m is the number of operators and N is the number of vehicles shared between them. In this presentation, HAT Lab researchers provide a high-level overview of the m:N studies that have been performed to-date. These include a study of the m:N concept of operations (CONOPS) and the attending roles and responsibilities ("ConOps/R&R Sim"), a study focused on contingency management involving dynamic, inter-operator transfers of vehicles ("Handoff Sim"), and a study examining the effects of pilot-ATC communication systems on workload ("UAM Comms Sim"). A selection of key results are provided. The presentation concludes with a brief discussion of planned research into m:N operations.

m:N↗

Concept of Operations for an In-time Aviation Safety Management System (IASMS) for Upper E Airspace

The National Airspace System undergoes continuous change including in the Upper Class E airspace involving increasingly complex operations and a widening diversity of vehicles. To secure a safe future system, the National Academies recommended an In-time Aviation Safety Management System (IASMS) that is extensible to Upper E. Current Air Traffic Management is not cost-effective to scale for future Upper E operations and diversity of vehicles so the Federal Aviation Administration developed an Upper E Traffic Management ConOps to safely integrate the diverse operations and vehicles having different performance characteristics and flight missions without disrupting current operations including space launch and reentry, suborbital flights, supersonic and hypersonic flights, slow moving or stationary unmanned balloons, and long endurance fixed wing vehicles that are slow, stationary, or high speed. IASMS integrates state-of-the-art predictive modeling with reactive and proactive analytics to detect hazards and mitigate risk precursors for Upper E operators. IASMS identifies emergent safety risks exposed by transformation of the NAS with new and increasingly complex operations. Safety intelligence will also expand the data available and offer insight to new approaches for implementing safety improvements to mitigate risk with more seamless “in-time” integration across the policy, risk management, safety assurance, and promotion pillars of SMS.

K Ellis↗

Airspace Automation Flight Tabletop Exercise

Interconnections of new systems are needed for airspace automation capabilities required in Urban Air Mobility (UAM). FAA Concept of Operations (CONOPS) V1.0 shows Provider of Services for UAM (PSU) at the center of the notional architecture; however, the functional role of the PSU in data exchange and the path to get there is unclear. In partnership with Wisk Aero, Avision, ANRA, Collins Aerospace, OneSky, SkyGrid, and AURA, the NASA National Campaign held discussions and tabletop exercises to test the functional allocations and work flows between an aircraft operator, airspace providers, Command and Control Communication Service Providers (C2CSP), and FAA air traffic in a real-world scenario. The exercise included preplanning and execution of a passenger mission with nominal, contingency, and conflict management scenarios for initial UAM operations. This working paper describes initial conditions for the flight tabletop exercise, exercise summaries, lessons learned, and recommendations for future work.

National Campaign↗