Search NASA⌕ Search

SEARCH · Search NASA

Results for “The Concept of Operations (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 73 records · Page 4

A Concept of Operations for an Integrated Vehicle Health Assurance System

This document describes a Concept of Operations (ConOps) for an Integrated Vehicle Health Assurance System (IVHAS). This ConOps is associated with the Maintain Vehicle Safety (MVS) between Major Inspections Technical Challenge in the Vehicle Systems Safety Technologies (VSST) Project within NASA s Aviation Safety Program. In particular, this document seeks to describe an integrated system concept for vehicle health assurance that integrates ground-based inspection and repair information with in-flight measurement data for airframe, propulsion, and avionics subsystems. The MVS Technical Challenge intends to maintain vehicle safety between major inspections by developing and demonstrating new integrated health management and failure prevention technologies to assure the integrity of vehicle systems between major inspection intervals and maintain vehicle state awareness during flight. The approach provided by this ConOps is intended to help optimize technology selection and development, as well as allow the initial integration and demonstration of these subsystem technologies over the 5 year span of the VSST program, and serve as a guideline for developing IVHAS technologies under the Aviation Safety Program within the next 5 to 15 years. A long-term vision of IVHAS is provided to describe a basic roadmap for more intelligent and autonomous vehicle systems.

Hunter, Gary W.↗

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↗

Analysis of WakeVAS Benefits Using ACES Build 3.2.1

The FAA and NASA are currently engaged in a Wake Turbulence Research Program to revise wake turbulence separation standards, procedures, and criteria to increase airport capacity while maintaining or increasing safety. The research program is divided into three phases: Phase I near term procedural enhancements; Phase II wind dependent Wake Vortex Advisory System (WakeVAS) Concepts of Operations (ConOps); and Phase III farther term ConOps based on wake prediction and sensing. This report contains an analysis that evaluates the benefits of a closely spaced parallel runway (CSPR) Phase I ConOps, a single runway and CSPR Phase II ConOps and a single runway Phase III ConOps. A series of simulation runs were performed using the Airspace Concepts Evaluation System (ACES) Build 3.21 air traffic simulator to provide an initial assessment of the reduction in delay and cost savings obtained by the use of a WakeVAS at selected U.S. airports. The ACES simulator is being developed by NASA Ames Research Center as part of the Virtual Airspace Modelling and Simulation (VAMS) program.

Smith, Jeremy C.↗

Cislunar Trajectory Design and Maneuver Autonomy for NASA's Moon to Mars Architecture

NASA’s Moon to Mars architecture is an ambitious roadmap of manned cislunar and deep space exploration. The extensive amount of orbital assets required will place a significant burden on ground-based resources, such as communication networks and operations facilities. Spacecraft autonomy is essential for maintaining a vast number of complex missions beyond Earth orbit. To achieve full autonomy, spacecraft must be able to employ methods of robust maneuver design without an explicit dependence on commands sent from the ground. This level of autonomy is needed not only for stationkeeping, but also for outbound transfers. To address the need of spacecraft maneuver design autonomy, this work investigates the use of neural networks (NNs) in a supervised learning environment. A supervised learning approach for NNs allows for a curated training data set, consisting exclusively of perturbations applied to a desired mission concept of operations (ConOps). The proposed approach allows humans on the ground to design a specific mission ConOps before flight, then employ NNs to fly the mission robustly and autonomously. This investigation numerically tests maneuver autonomy in four highly sensitive regions of flight: orbit raising, translunar injection burns, powered lunar flybys, and invariant manifold insertion burns. These straining cases are contextualized by testing them in a demonstration mission, targeting an Earth-Moon L3 orbit. The study first establishes feasibility by automating impulsive burn maneuvers. However, some guidance algorithms will need more intensive commands, such as inertial pointing and angular rates. To validate this method, NN maneuver autonomy is applied to a finite burn model of the demonstration mission. The use of sequential, mission specific maneuvers provide an appropriate testbed to demonstrate the robustness of a NN trained on feasible perturbed states. Moreover, these scenarios provide preliminary proof-of-concept for fully autonomous missions that execute maneuvers without dependence upon explicit command uplinks. As a result, the technological advancement proposed in this work may significantly ease the strain on ground-based mission operations. This would enable complex and autonomous mission execution in cislunar and deep space regimes, filling a technology gap required to support future manned missions.

NASA↗

NASA's ATM Technology Demonstration-1: Integrated Concept of Arrival Operations

This paper describes operations and procedures envisioned for NASA s Air Traffic Management (ATM) Technology Demonstration #1 (ATD-1). The ATD-1 Concept of Operations (ConOps) demonstration will integrate three NASA technologies to achieve high throughput, fuel-efficient arrival operations into busy terminal airspace. They are Traffic Management Advisor with Terminal Metering (TMA-TM) for precise time-based schedules to the runway and points within the terminal area, Controller-Managed Spacing (CMS) decision support tools for terminal controllers to better manage aircraft delay using speed control, and Flight deck Interval Management (FIM) avionics and flight crew procedures to conduct airborne spacing operations. The ATD-1 concept provides de-conflicted and efficient operations of multiple arrival streams of aircraft, passing through multiple merge points, from top-of-descent (TOD) to touchdown. It also enables aircraft to conduct Optimized Profile Descents (OPDs) from en route altitude to the runway, using primarily speed control to maintain separation and schedule. The ATD-1 project is currently addressing the challenges of integrating the three technologies, and implantation into an operational environment. Goals of the ATD-1 demonstration include increasing the throughput of high-density airports, reducing controller workload, increasing efficiency of arrival operations and the frequency of trajectory-based operations, and promoting aircraft ADS-B equipage.

Baxley, Brian T.↗

Design and Verification

As future space missions become longer, an important aspect to consider is the habitability of the spacecraft. The amount of habitable volume affects not only astronaut comfort, but safety and mission success as well. However, as the volume is increased to aid in task performance, the weight of the vehicle and cost of the mission escalates in proportion. Pressure to reduce mission cost is constant, but the risk to mission success and crew survival must remain the priorities. The Constellation Program's Altair Lunar Lander is designed for short duration surface operation missions of seven to ten days. For short duration missions, humans will tolerate fairly primitive environmental situations provided the basic physiological arrangements are acceptable. However, for long-duration lunar surface operations, the living and operational spaces within which the crew work must provide both the essentials of life, as well as the support necessary for the crew to be productive in accomplishing their mission. The Altair is still in the preliminary design phase, which is the optimal time for Human Factors data to be provided to designers and engineers. A Human Centered Design (HCD) approach is being taken with our Human Factors evaluations. Human-in-the-loop testing is conducted using low-medium fidelity mock-ups of proposed lunar architecture. Based on current ConOps (Concept of Operations) procedures, a task analysis is performed in which individual tasks are combined into larger operational scenarios. Subjective and objective performance measures are gathered at both the task and scenario level. These scores are used to determine the functionality of the vehicle in terms of task performance. Results from these evaluations will highlight areas for design or operational improvement.

Thompson, Shelby G.↗

An Integrated Gate Turnaround Management Concept Leveraging Big Data Analytics for NAS Performance Improvements

"Gate Turnaround" plays a key role in the National Air Space (NAS) gate-to-gate performance by receiving aircraft when they reach their destination airport, and delivering aircraft into the NAS upon departing from the gate and subsequent takeoff. The time spent at the gate in meeting the planned departure time is influenced by many factors and often with considerable uncertainties. Uncertainties such as weather, early or late arrivals, disembarking and boarding passengers, unloading/reloading cargo, aircraft logistics/maintenance services and ground handling, traffic in ramp and movement areas for taxi-in and taxi-out, and departure queue management for takeoff are likely encountered on the daily basis. The Integrated Gate Turnaround Management (IGTM) concept is leveraging relevant historical data to support optimization of the gate operations, which include arrival, at the gate, departure based on constraints (e.g., available gates at the arrival, ground crew and equipment for the gate turnaround, and over capacity demand upon departure), and collaborative decision-making. The IGTM concept provides effective information services and decision tools to the stakeholders, such as airline dispatchers, gate agents, airport operators, ramp controllers, and air traffic control (ATC) traffic managers and ground controllers to mitigate uncertainties arising from both nominal and off-nominal airport gate operations. IGTM will provide NAS stakeholders customized decision making tools through a User Interface (UI) by leveraging historical data (Big Data), net-enabled Air Traffic Management (ATM) live data, and analytics according to dependencies among NAS parameters for the stakeholders to manage and optimize the NAS performance in the gate turnaround domain. The application will give stakeholders predictable results based on the past and current NAS performance according to selected decision trees through the UI. The predictable results are generated based on analysis of the unique airport attributes (e.g., runway, taxiway, terminal, and gate configurations and tenants), and combined statistics from past data and live data based on a specific set of ATM concept-of-operations (ConOps) and operational parameters via systems analysis using an analytic network learning model. The IGTM tool will then bound the uncertainties that arise from nominal and off-nominal operational conditions with direct assessment of the gate turnaround status and the impact of a certain operational decision on the NAS performance, and provide a set of recommended actions to optimize the NAS performance by allowing stakeholders to take mitigation actions to reduce uncertainty and time deviation of planned operational events. An IGTM prototype was developed at NASA Ames Simulation Laboratories (SimLabs) to demonstrate the benefits and applicability of the concept. A data network, using the System Wide Information Management (SWIM)-like messaging application using the ActiveMQ message service, was connected to the simulated data warehouse, scheduled flight plans, a fast-time airport simulator, and a graphic UI. A fast-time simulation was integrated with the data warehouse or Big Data/Analytics (BAI), scheduled flight plans from Aeronautical Operational Control AOC, IGTM Controller, and a UI via a SWIM-like data messaging network using the ActiveMQ message service, illustrated in Figure 1, to demonstrate selected use-cases showing the benefits of the IGTM concept on the NAS performance.

Efficent ATM systems↗

Overview of an Exploratory, Real-Time, Multi-Pilot Simulation Study of Early eVTOL Operations at Non-Towered Vertiports

This paper provides a report out on an exploratory, multi-aircraft/multi-pilot, real-time simulation study conducted by NASA of early commercial powered-lift, Urban Air Mobility (UAM) operations at a non-towered vertiport. As used in this paper, vertiport refers to the primary ground and airspace elements facilitating the takeoff and landing of electric vertical takeoff and landing (eVTOL) aircraft with central emphasis on a vertipad, i.e. the physical touch-down and lift-off area and surrounding approach , departure, local pattern procedures. The study, known as the Piloted UML-2 ConOps Study (PUCS), had two high-level goals. The first goal was providing preliminary insights and observations relevant to the piloting and flight operations of early, commercial UAM operations aligned with the initial stage of the FAA’s Advanced Air Mobility (AAM) Implementation Plan and the second level NASA’s UAM Maturity Level (UML) scale. The second goal was evaluating a novel, medium-fidelity, extensible, many-pilot, real-time simulation capability known as the UAM Flyers developed by NASA. The Flyers are intended to allow rapid development, screening, evaluation, and demonstrations of potential Concepts of Operation (ConOps) for UAM flight operations and airspace management in a modular and low-cost, real-time, human-in-the-loop rapid simulation prototyping environment. For this study, ten Flyer cockpits were configured to evaluate flight operations through a non-towered vertiport with pilot interfaces and displays (external and in-cockpit) appropriate for operations under visual flight rules (VFR) and employing flight and communication procedures representative of current operations at non-towered airports. The presented results include an achieved operational tempo; durations of individual flight tasks for approaches and departures; off-nominal events and triggers; and pilot comments regarding potential procedural and technology improvements.

Urban Air Mobility↗

Overview of an Exploratory, Multi-Pilot Simulation Study of Early eVTOL Operations at Non-Towered Vertiports

This paper provides a report out on an exploratory, multi-aircraft/multi-pilot, real-time simulation study conducted by NASA of early commercial powered-lift, Urban Air Mobility (UAM) operations at a non-towered vertiport. As used in this paper, vertiport refers to the primary ground and airspace elements facilitating the takeoff and landing of electric vertical takeoff and landing (eVTOL) aircraft with central emphasis on a vertipad, i.e. the physical touch-down and lift-off area and surrounding approach , departure, local pattern procedures. The study, known as the Piloted UML-2 ConOps Study (PUCS), had two high-level goals. The first goal was providing preliminary insights and observations relevant to the piloting and flight operations of early, commercial UAM operations aligned with the initial stage of the FAA’s Advanced Air Mobility (AAM) Implementation Plan and the second level NASA’s UAM Maturity Level (UML) scale. The second goal was evaluating a novel, medium-fidelity, extensible, many-pilot, real-time simulation capability known as the UAM Flyers developed by NASA. The Flyers are intended to allow rapid development, screening, evaluation, and demonstrations of potential Concepts of Operation (ConOps) for UAM flight operations and airspace management in a modular and low-cost, real-time, human-in-the-loop rapid simulation prototyping environment. For this study, ten Flyer cockpits were configured to evaluate flight operations through a non-towered vertiport with pilot interfaces and displays (external and in-cockpit) appropriate for operations under visual flight rules (VFR) and employing flight and communication procedures representative of current operations at non-towered airports. The presented results include an achieved operational tempo; durations of individual flight tasks for approaches and departures; off-nominal events and triggers; and pilot comments regarding potential procedural and technology improvements.

Urban Air Mobility↗

Assessing Utility of Different Orbits for a Lunar PNT Constellation

"As the Artemis program establishes a long-term presence on the lunar surface, lunar surface users will need an accurate source of Position, Navigation, and Timing (PNT). Under the LunaNet framework, NASA has proposed the Lunar Navigation System (LNS), a constellation of satellites in lunar orbit which will broadcast LunaNet’s Augmented Forward Signal (AFS) [1] to the lunar surface. LNS will have the objective of providing user position accuracies of 10 m and timing accuracies of 10 microseconds on the lunar surface and up to 200 km above the surface. Several classes of orbits are possibilities for the LNS constellation, including circular orbits, eccentric orbits, and various families of 3-body orbits. Each of these orbit classes have both advantages and disadvantages in their utility as PNT constellations. In this study we examine a wide variety of potential LNS constellations and evaluate their performance against several metrics, including: a. Dilution of Precision (DOP) performance over the lunar service volume and the South Pole region, during both the constellation buildup and after the constellation is completed. b. Number of satellites required to achieve required DOP performance. c. Relative dynamics of LNS satellites with respect to surface users. d. Signal in space error (SISE) performance, assuming orbit determination that includes the Global Positioning System (GPS), crosslinks, and monitor sites on the surface of the moon. e. Constellation insertion, station keeping, and disposal costs. f. Specific Concept of Operations (CONOPS) and engineering challenges associated with establishing and operating the constellations. (E.g., frequent station keeping, variable signal strength, divergent CONOPS for different planes of the constellation.) The system’s performance is considered both independently and in combination with other proposed systems, such as NASA’s Lunar Communication Relay and Navigation System (LCRNS) and ESA’s Moonlight constellation. The study concludes that a 3-plane Walker constellation at 6 lunar radii (slightly higher than GPS’s 4.2 earth radii from a geometry perspective, but significantly closer in an absolute sense) is a good candidate for the LNS constellation, providing the user with good SISE and DOP performance, while not requiring excessive station keeping or complex CONOPS. However, other viable concepts exist and could be chosen if early South Pole coverage is a driving factor in the system design."

navigation↗

Concept of Operations for Commercial and Business Aircraft Synthetic Vision Systems

A concept of operations (CONOPS) for the Commercial and Business (CaB) aircraft synthetic vision systems (SVS) is described. The CaB SVS is expected to provide increased safety and operational benefits in normal and low visibility conditions. Providing operational benefits will promote SVS implementation in the Net, improve aviation safety, and assist in meeting the national aviation safety goal. SVS will enhance safety and enable consistent gate-to-gate aircraft operations in normal and low visibility conditions. The goal for developing SVS is to support operational minima as low as Category 3b in a variety of environments. For departure and ground operations, the SVS goal is to enable operations with a runway visual range of 300 feet. The system is an integrated display concept that provides a virtual visual environment. The SVS virtual visual environment is composed of three components: an enhanced intuitive view of the flight environment, hazard and obstacle defection and display, and precision navigation guidance. The virtual visual environment will support enhanced operations procedures during all phases of flight - ground operations, departure, en route, and arrival. The applications selected for emphasis in this document include low visibility departures and arrivals including parallel runway operations, and low visibility airport surface operations. These particular applications were selected because of significant potential benefits afforded by SVS.

Williams Daniel M.↗

Testing a Run-Time Assurance Framework Coupled with Integrated Risk Mitigation Capabilities for Autonomous Urban UAS Flights

The In-Time Aviation Safety Management System (IASMS) Concept of Operations (ConOps) envisions new capabilities to monitor, assess, and mitigate flight safety risks. Systems will be tailored to mission type, vehicle/equipage type, operational environment, and safety risk tolerance. Within an IASMS framework, several capabilities may be implemented spanning three operational phases (pre-flight, in-flight, and post-flight/off-line); and consisting of lower level functions and information services which may reside onboard the aircraft, on third-party server(s), and/or on ground/operator station(s). Each capability will be designed to produce and disseminate safety-relevant information; perform detection, diagnosis, and prediction of unsafe situations; and/or execute mitigation actions when hazardous events warrant such changes. This paper focuses on recent testing of airborne capabilities that demonstrate inflight aspects of the overarching concept for autonomous unmanned aircraft systems (UAS) operations in urban environments. A flight test architecture is described that applies run-time assurance principles (e.g., executes independent of the unassured autopilot), real-time risk assessment, and a technique to execute contingencies if necessary either automatically or via pilot intervention. Several tests using small UAS were conducted to verify the assured in-flight risk mitigation capability. The paper draws significantly from a larger NASA technical report and recent prior conference papers, providing additional details. Data is analyzed for two representative flights to illustrate the performance for various sequential and simultaneous hazards used during testing. During each automated flight, several hazards are encountered at various points along the flight path. At each point, the hazard is mitigated by the system, with the vehicle then continuing to subsequent points. The paper concludes with lessons-learned regarding relevant aspects of the overarching IASMS concept and how it may be updated and further advanced in the future.

population activity↗

Feasibility of a Networked Air Traffic Infrastructure Validation Environment for Advanced NextGen Concepts

Abstract-Next Generation Air Transportation System (NextGen) applications reliant upon aircraft data links such as Automatic Dependent Surveillance-Broadcast (ADS-B) offer a sweeping modernization of the National Airspace System (NAS), but the aviation stakeholder community has not yet established a positive business case for equipage and message content standards remain in flux. It is necessary to transition promising Air Traffic Management (ATM) Concepts of Operations (ConOps) from simulation environments to full-scale flight tests in order to validate user benefits and solidify message standards. However, flight tests are prohibitively expensive and message standards for Commercial-off-the-Shelf (COTS) systems cannot support many advanced ConOps. It is therefore proposed to simulate future aircraft surveillance and communications equipage and employ an existing commercial data link to exchange data during dedicated flight tests. This capability, referred to as the Networked Air Traffic Infrastructure Validation Environment (NATIVE), would emulate aircraft data links such as ADS-B using in-flight Internet and easily-installed test equipment. By utilizing low-cost equipment that is easy to install and certify for testing, advanced ATM ConOps can be validated, message content standards can be solidified, and new standards can be established through full-scale flight trials without necessary or expensive equipage or extensive flight test preparation. This paper presents results of a feasibility study of the NATIVE concept. To determine requirements, six NATIVE design configurations were developed for two NASA ConOps that rely on ADS-B. The performance characteristics of three existing in-flight Internet services were investigated to determine whether performance is adequate to support the concept. Next, a study of requisite hardware and software was conducted to examine whether and how the NATIVE concept might be realized. Finally, to determine a business case, economic factors were evaluated and a preliminary cost-benefit analysis was performed.

McCormack, Michael J.↗

HALE UAS Concept of Operations. Version 3.0

This document is a system level Concept of Operations (CONOPS) from the perspective of future High Altitude Long Endurance (HALE) Unmanned Aircraft Systems (UAS) service providers and National Airspace System (NAS) users. It describes current systems (existing UAS), describes HALE UAS functions and operations to be performed (via sample missions), and offers insight into the user s environment (i.e., the UAS as a system of systems). It is intended to be a source document for NAS UAS operational requirements, and provides a construct for government agencies to use in guiding their regulatory decisions, architecture requirements, and investment strategies. Although it does not describe the technical capabilities of a specific HALE UAS system (which do, and will vary widely), it is intended to aid in requirements capture and to be used as input to the functional requirements and analysis process. The document provides a basis for development of functional requirements and operational guidelines to achieve unrestricted access into the NAS. This document is an FY06 update to the FY05 Access 5 Project-approved Concept of Operations document previously published in the Public Domain on the Access 5 open website. This version is recommended to be approved for public release also. The updates are a reorganization of materials from the previous version with the addition of an updated set of operational requirements, inclusion of sample mission scenarios, and identification of roles and responsibilities of interfaces within flight phases.

Source record↗

Risk-Reduction Autonomy Implementation to Enable NASA Artemis Missions

To achieve NASA’s Artemis program mission objectives a high level of autonomy that is ubiquitous throughout the systems that are being developed will be necessary. The autonomous systems of Artemis will require a distributed autonomy capability, with autonomous systems organized functionally in a hierarchical architecture, where systems at higher levels of the hierarchy have authority over systems at lower levels. The challenge of developing autonomy technologies and Concepts of Operations (ConOps) for Artemis has been undertaken by the NASA Gateway Working Group. This group has developed requirements, architectures, ConOps, and interface control documents (ICDs), in the context of a hierarchical distributed architecture that includes the following: a Vehicle System Manager (VSM) that autonomously manages the entire Gateway; Module System Managers (MSMs) that autonomously manage each module; and System Managers (SMs) that autonomously manage systems within a module (i.e. ECLSS). A substantially high level of autonomy needs to be achieved by each element of the hierarchy (VSM, MSM, SM) to meet requirements for uncrewed operations; this includes conditions that will have minimal and/or delayed ground intervention (i.e. requirements for sustainability for months of operation without crew or ground support). To advance an implementation of this autonomy design (Gateway Autonomy Design – GAD), a collaboration was established between the Autonomous Systems Laboratory (ASL) at NASA Stennis Space Center and Lockheed Martin. The objectives of this partnership were the following: (1) to implement autonomy at the VSM, MSM, and SM levels; (2) to implement communications among a VSM, 2 MSMs, ORION (a visiting vehicle somewhat equivalent to a module) and 1 SM (a power system), and (3) test autonomous operations with representative use cases. A SM backed by a high-fidelity simulation was created to facilitate demonstrations of use cases that originated in a system of a module. Communication between the VSM and MSMs was implemented according to Concepts of Operations and Interface Control Documents (ICDs). Demonstrations were conducted to address nominal and off-nominal operations and multi-module interactions with the VSM. Additionally, user interfaces were created to provide awareness about ongoing processes and results while enhancing the demonstration. Demonstrations included the following use cases: (1) Orion as visiting vehicle registers with VSM; (2) VSM reschedules a module’s timelines when another module’s MSM task fails; and (3) a module’s Power System Manager (PSM) demonstration that included component failure diagnostics, tracing component failure to effected components, which in turn, reports failure information up to the VSM for acknowledgement and display. This paper will describe the detailed technology and autonomous systems developed, and the integrated multi-module demonstrations conducted. Also, challenges that must be met to fully implement the GAD defined by Gateway will be addressed.

Fernando Figueroa↗

Parametric Studies of Human Mars Entry, Descent, and Landing Systems

This paper will present a parametric analysis for entry, descent, and landing (EDL) concepts, enabling rapid systems assessment and tradespace exploration. The entry system uses a hypersonic inflatable aerodynamic decelerator (HIAD) technology. The baseline system includes elements for Mars aerocapture (AC) and EDL segments of the mission. The mission concept of operations (ConOps) begins at Mars arrival in a polar inclination. After performing an aerocapture (AC) maneuver into a pre-defined Mars parking orbit, the AC HIAD is jettisoned. The rest of thevehicle stays in the parking orbit for up to one year. The EDL sequence starts with a deorbit burn at the apoapsis of the parking orbit. After hypersonic entry with the EDL HIAD, the entry system uses a supersonic retropropulsion maneuver to slow the vehicle for the descent and landing segments of the mission. The vehicle will maintain a constant velocity of 2.5 m/s for 5 seconds prior to landing.The system includes a Mars Ascent Vehicle (MAV), Mars Descent Module (MDM), and two HIADs. The MDM includes a primary structure, tanks, engines, and radiators. The primary structure is an aluminum-lithium (Al-Li)cruciform design similar to the structural design of the Apollo Lunar Module. The cruciform planform layout results in four outer bays, with adequate volume in the corners between outer bays to package four landing gears. The central bay is reserved for packaging the MAV and the recessed MAV engines. Two of the outer bays accommodate main propellant tanks, with one LOX and one CH4 tank in each bay. The two remaining outer bays each house four rocket engine systems and associated support structure. Each HIAD comprises an inflatable structure, flexible thermal protection system, gas, and gas generators. The HIAD design used in this study is a stacked-toroid concept with pairing loop straps and radial/chevron straps. The baseline system lands a 20-t payload on the Mars surface. It is assumed the vehicle arrives at 6.2 km/s relative velocity at 90° inclination and is captured to a 1-Sol parking orbit.The baseline design includes many assumptions such as margins, arrival state, ConOps options, parking orbit, physical dimensions, propellant options, and technology concepts. The impact of these parameters are quantified through systems-level sensitivity analyses, which capture the global impact—not at a component level—but at the systems level. The systems-level sensitivities expose major design drivers and importance of each assumption for a design.Through tradespace exploration, a wide range of systems parameters are examined and compared for several feasible design options. Studies have been completed for the following input parameters: payload mass, propellant options, AC/EDL ballistic coefficient, lander thrust to weight ratio (T/W) (surrogate for the maximum EDL g’s),engine specific impulse (Isp), parking orbit, and inclination.The final paper will present and discuss the parametric approach used in the study. It will also include the results of recent systems analyses, sensitivity analyses, and tradespace exploration

Jamshid Samareh↗

m:N ConOps/R&R Remote Simulation

This presentation details the experimental design of an investigation of small unmanned aircraft system (sUAS) operations involving multiple vehicle management by a remote operator. The study is part of an ongoing effort to explore multiple vehicle control by multiple operators, i.e., the control of N vehicles by m operators (m:N operations). For this effort, NASA and collaborators have developed prototypes of a concept of operations (ConOps), roles and responsibilities (R&R) for operators and supervisors, and a ground control station (GCS), including software displays and interfaces. Participants in this study acted as the pilot-in-command of twelve aircraft flying pre-approved routes in a simulation of a food delivery operation utilizing sUAS in the San Diego, CA area. Each participant experienced four experimental trials. Twice within the course of each trial, participants were responsible for responding to a sudden, unanticipated, and high-priority contingency: an airspace restriction for sUAS operations known as a UAS Volume Reservation (UVR). Upon issuance of a UVR, pilots were expected to reroute affected vehicles around the airspace. The level of automation (LoA) and workload of the flight rerouting task were varied. The LoA was manipulated by providing reroute suggestions ("auto" condition) for aircraft or by requiring pilots to manually reroute ("manual" condition) affected vehicles. Workload was varied as a function of the number of vehicles affected by the UVR contingencies: 2 vehicles ("low workload" condition) versus 4 vehicles ("high workload" condition). Additionally, some vehicles required pilots to adjust for terrain conflicts while avoiding the UVR region. Due to the COVID-19 pandemic, in-person data collection for this study was not possible. Researchers adapted to this circumstance through the development of remote data collection protocol. Participants were able to view adapted GCS displays using the Microsoft Teams teleconferencing platform and responded to events by using a verbal protocol developed for the experiment. Using this protocol, participants provided instructions for actions to a researcher, referred to as the surrogate, to carry out on their behalf. This presentation describes the experiment design, including special details for remote data collection via a subject-surrogate configuration, and concludes with planned data analysis and results to be presented at a later date.

multi-UAS↗