Results for “ConOps” — Page 4

NASA NTRS2007

Space Medicine Issues and Healthcare Systems for Space Exploration Medicine

This viewgraph presentation reviews issues of health care in space. Some of the issues reviewed are: (1) Physiological adaptation to microgravity, partial gravity, (2) Medical events during spaceflight, (3) Space Vehicle and Environmental and Surface Health Risks, (4) Medical Concept of Operations (CONOPS), (4a) Current CONOPS & Medical Hardware for Shuttle (STS) and ISS, (4b) Planned Exploration Medical CONOPS & Hardware needs, (5) Exploration Plans for Lunar Return Mission & Mars, and (6) Developing Medical Support Systems.

Scheuring, Richard A.↗

NASA NTRS2006

Tools to Support Human Factors and Systems Engineering Interactions During Early Analysis

We describe an approach and existing software tool support for effective interactions between human factors engineers and systems engineers in early analysis activities during system acquisition. We examine the tasks performed during this stage, emphasizing those tasks where system engineers and human engineers interact. The Concept of Operations (ConOps) document is an important product during this phase, and particular attention is paid to its influences on subsequent acquisition activities. Understanding this influence helps ConOps authors describe a complete system concept that guides subsequent acquisition activities. We identify commonly used system engineering and human engineering tools and examine how they can support the specific tasks associated with system definition. We identify possible gaps in the support of these tasks, the largest of which appears to be creating the ConOps document itself. Finally, we outline the goals of our future empirical investigations of tools to support system concept definition.

Thronesbery, Carroll↗

NASA NTRS2005

Tools to Support Human Factors and Systems Engineering Interactions During Early Analysis

We describe an approach and existing software tool support for effective interactions between human factors engineers and systems engineers in early analysis activities during system acquisition. We examine the tasks performed during this stage, emphasizing those tasks where system engineers and human engineers interact. The Concept of Operations (ConOps) document is an important product during this phase, and particular attention is paid to its influences on subsequent acquisition activities. Understanding this influence helps ConOps authors describe a complete system concept that guides subsequent acquisition activities. We identify commonly used system engineering and human engineering tools and examine how they can support the specific tasks associated with system definition. We identify possible gaps in the support of these tasks, the largest of which appears to be creating the ConOps document itself. Finally, we outline the goals of our future empirical investigations of tools to support system concept definition.

Thronesbery, Carroll↗

NASA NTRS2013

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

NASA NTRS2016

A Tailored Concept of Operations for NASA LSP Integrated Operations

An integral part of the Systems Engineering process is the creation of a Concept of Operations (ConOps) for a given system, with the ConOps initially established early in the system design process and evolved as the system definition and design matures. As Integration Engineers in NASA's Launch Services Program (LSP) at Kennedy Space Center (KSC), our job is to manage the interface requirements for all the robotic space missions that come to our Program for a Launch Service. LSP procures and manages a launch service from one of our many commercial Launch Vehicle Contractors (LVCs) and these commercial companies are then responsible for developing the Interface Control Document (ICD), the verification of the requirements in that document, and all the services pertaining to integrating the spacecraft and launching it into orbit. However, one of the systems engineering tools that have not been employed within LSP to date is a Concept of Operations. The goal of this project is to research the format and content that goes into these various aerospace industry ConOps and tailor the format and content into template form, so the template may be used as an engineering tool for spacecraft integration with future LSP procured launch services.

Systems↗

NASA NTRSDate not supplied

Developing a Medical System Concept of Operations for Level of Care IV: Long-Duration Lunar Orbital and Surface Operations

A goal of the Human Research Program (HRP) Exploration Medical Capability (ExMC) Element Systems Engineering (SE) team is to define the technical system needed to support crew medical system capabilities for future exploration missions, including a mission with lunar orbital and long duration surface operations. The medical system concept of operations (ConOps) is the starting point of creating a foundation for a medical system that meets Level of Care IV requirements, as defined by NASA’s space flight human-system standards. This ConOps illustrates how NASA can provide a Level of Care IV medical system for crews within the various cis-lunar orbit and lunar surface habitat environments. The use case scenarios included in this ConOps illustrate required medical system capabilities for Level of Care IV and enable the ExMC SE team to develop integrated medical system requirements and identify capabilities required to meet those requirements. This discussion will focus on how this concept of operations was constructed – by utilizing the lessons learned from ExMC’s existing Short-Duration Lunar Orbit Medical System Concept of Operations, by employing Model-Based Systems Engineering, and by collaborating with stakeholders in order to ensure the necessary assumptions were made.

M. Kaetzer↗

NASA NTRSDate not supplied

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↗

NASA NTRSDate not supplied

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↗

NASA NTRSDate not supplied

Corridor Design and Analysis for UAM Operations

The Urban Air Mobility (UAM) concept is a part of Advanced Air Mobility (AAM), a joint initiative between the Federal Aviation Administration (FAA), NASA, and industry to develop an air transportation system that uses new electric (i.e., green) air vehicles in geographical areas previously underserved by traditional aviation. Market forecast studies predict that there will be demand for alternate modes of air transportation using electric Vertical Take-off and Landing aircraft. UAM expands transportation networks by introducing short flights to move people and goods around metropolitan areas. UAM is expected to improve mobility for the public, decongest road traffic, reduce trip time, and decrease strain on existing public transportation networks. Various challenges exist to make the introduction of UAM operations successful in the U.S. National Airspace System (NAS). These include but are not limited to integration with existing airports and airspace, provision of air traffic services (e.g., separation), vehicle design and certification, and community acceptance. The focus of this paper is on integration of UAM operations into the NAS via introduction of new airspace structures. UAM will operate within a regulatory, operational, and technical environment that is incorporated into the NAS. As per the UAM Concept of Operations (ConOps), the FAA retains regulatory authority and is responsible for establishing operational parameters and maintaining oversight. The FAA’s UAM ConOps describes flights at low altitudes (below 5,000 ft) with minimal disruption to established conventional aircraft traffic and limited voice interactions with the Air Traffic Control (ATC). Early stages of UAM may use existing procedures to safely integrate UAM with conventional flights. This would involve flying under Part 91 Visual Flight Rules (VFR) and using voice for communications. The initial UAM ecosystem will utilize the current infrastructure such as routes, helipads, and ATC services, where practicable. A NASA study explored the use of existing helicopter routes in Dallas Fort Worth (DFW) airspace for initial UAM operations with a Letter of Agreement (LOA) that included procedures to request a Class B (controlled airspace) clearance. The research showed that the chosen approach was feasible for near-term, low-demand UAM traffic, but was not scalable. The growth of operations in today’s aviation system has resulted in airspace reorganization and procedures to ensure safety and efficiency as traffic rates increase. One proposed operating innovation that can help with the scalability of UAM is establishing routes and corridors. This may look similar to the Area Navigation (RNAV) procedures used today to streamline operations into busy airports. However, instead of FAA automation systems and ATC managing the flow of traffic, some UAM concepts envision a third-party service provider performing this role as part of the Provider of Services for UAM (PSU) network. The FAA’s UAM ConOps posits that new airspace structures such as UAM corridors include the following design criteria: 1) Minimal impact on existing NAS operations, 2) no or minimal additional ATC services, 3) public interest considerations such as noise, safety, and security, and 4) customer needs. The airspace available in urban environments is limited by the height of buildings, the effect of weather including wind gusts, privacy needs, and a clearance envelope. The new airspace structure would need to be designed around large airports and urban areas where the initial market demand is likely to exist. NASA has started evaluating airspace in the Dallas Fort Worth area to design new airspace structures, keeping the first two design criteria in mind. It is assumed that there will be an on-board pilot-in-command, and the flights will operate under VFR in Visual Meteorological Conditions. Corridors will be required in controlled airspace, whereas UAM operations can fly in uncontrolled Class G and E airspace using current day rules. Keeler et. al identified factors and heuristics for development of routes for UAM operations for integration with airspace close to large airports such as Dallas Fort Worth and Dallas Love Field. This paper describes the heuristics applied to define the corridors, analyzes them with respect to legacy traffic and presents key results.

Urban Air Mobility↗

NASA NTRSDate not supplied

Earth-Independent Medical Operations (EIMO) Concept of Operations

Compared to the current paradigm for crew health in low-Earth orbit and Lunar missions that rely on constant communication with Mission Control, there is an anticipated shift in medical operations for deep-space exploration missions. This shift stems from mission constraints imposed by the considerable distance from Earth, which include resource limitations due to a lack of resupply, mass, power, volume, and data limitations, challenges imposed by communication latency and the inability to evacuate in case of emergencies. To transition towards a more self-reliant medical approach, a comprehensive strategy is essential to progressively enable crew autonomy and mitigate mission success risks in the challenging environment of space. This transformative shift is collectively referred to as "Earth-Independent Medical Operations" (EIMO), signifying the gradual transfer of medical care and decision-making from terrestrial resources to space-based assets. This transition is aimed at bolstering astronaut health and performance while simultaneously reducing the overall risks associated with space missions. The constraints related to EIMO necessitate an integrated development of medical systems, featuring interoperability with mission planning, vehicle design, spacesuit design, and data architecture. This integration is vital in establishing a robust medical infrastructure that not only supports the well-being of astronauts but also ensures the success of the mission as a whole. The Human Research Program (HRP) Exploration Medical Capability (ExMC) Element has developed a model-based Concept of Operations (ConOps) outlining an initial vision for EIMO. Within this ConOps, a comprehensive view is presented, encompassing stakeholder needs, system objectives, and system goals associated with EIMO. Additionally, it provides illustrative examples of the various activities (scenarios) for which the system will be employed during missions. The selection of these activities has been meticulous, aiming to encompass a wide spectrum of medical conditions, including those falling under different risk categories, such as low-likelihood-low-consequence, low-likelihood-high-consequence, and high-likelihood-low-consequence. The selection of these activities (scenarios) effectively encompasses the wide range of medical events situated within an assumed probability-consequence bell curve. In each scenario, at least one of the five main EIMO components identified is captured. Those EIMO components are: Pre-mission Planning, Acute and Emergent Management Decision Making, Prolonged Medical Management Decision Making, Supplies and Resource Management, and Task Load Management. The ConOps was developed by a multidisciplinary team consisting of systems engineers, scientists, and clinicians across NASA and aims to serve as an initial recommendation to gradually and safely enabling crew autonomy for Mars missions and beyond.

Earth Independent Medical Operations↗

NASA NTRSDate not supplied

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↗

NASA NTRSDate not supplied

Developing Concepts of Operations Using Multi-Step Tool Techniques With Large Language Models

The National Aeronautics and Space Administration (NASA) Air Mobility Pathfinders (AMP) project is developing and evaluating concepts of operations (ConOps) for safe, secure, and scalable Urban Air Mobility (UAM) operations. The AMP project’s Operational Concepts, Architecture, and Requirements Integration (OCARI) Team is using a Model Based System Engineering (MBSE) approach for integration, interoperability, and traceability of Advanced Air Mobility (AAM) ecosystems centered around urban air taxi services. The team’s goal is to define structures and behaviors needed for system feasibility, readiness, and interoperability, establish a UAM knowledge base, and trace and validate assumptions and requirements relevant to AAM. NASA Langley Research Center (LaRC) is spearheading an innovative digital engineering approach to integrate, communicate, and facilitate the research of multi-modal transportation systems. The Knowledge-based Digital Platform (KbDP) is a concept being developed that ties the workflows of Project Managers (PM), Principal Investigators (PI), and System Engineers together across organizational boundaries. It does so through the management of an information database defined by mathematical, data science, and system engineering principles. Machine Learning (ML) algorithms play a key role in this concept by extracting meaningful knowledge from relational and graph databases, document repositories, and system artifacts, which the human user leverages to greatly improve the efficiency and effectiveness of their research. Recent advancements in the field of Large Language Models (LLMs), specifically models trained for tool use, such as Command-R , now allow for the reliable implementation of single-step and multi-step tool-centric systems. These techniques provide the LLM with a set of tools, in our case Python functions, that can be called on to answer a much wider range of questions compared to LLMs implemented using a traditional single-source or Retrieval Augmented Generation (RAG) approach. Through this method, the LLM can pull information from multiple data sources, such as relational or graph databases, document repositories, application programming interfaces (APIs), and SysML artifacts depending on the user’s question. The LLM can also output the information in a variety of different formats, using output generation tools, such as CSV, UML, or SysML artifacts. Additionally, tools can be assigned roles and can work together to provide answers to queries in an “agent” like approach, similar to that implemented by Microsoft’s AutoGen framework where different agents can converse with each other to accomplish tasks. Previously, our team developed a chatbot system with “agent like” functionality in the form of different “modes” the user could select from a user interface (UI), this architecture can be seen on the left in figure 1. Three different modes were implemented, the first mode allowed the LLM to utilize the structures and algorithms within a graph database to trace UAM requirements. The second mode gave the LLM access to a vector search capable of providing relevant information from thousands of document pages related to UAM ConOps and requirements. The third mode served as a general assistant where users could enter open-ended questions and custom prompts to utilize the LLM for different use-cases. This system improved the process surrounding generating and analyzing information related to UAM requirements, however, the implementation provided a clunky user experience. Users were required to know what mode to select within the UI in advance before entering their question to the selected tool. Moreover, the different tools were isolated from each other, they lacked bidirectional links that would allow for tools to collaborate to generate better responses. Our team is working on a new architecture, seen on the right in the below figure, with the goal to address many of the UX shortcomings of our original system while improving the accuracy and depth of responses from the LLM. This new system will automatically select the appropriate tool to use based off the user’s question. Each tool will be capable of calling on any of the other tools available to the LLM, resulting in a collaborative pipeline where tools can pass data between other tools until enough data is received to generate an answer to the user’s question. Using a locally deployed, open-source, LLM, the NASA OCARI team, in collaboration with Collins Aerospace, will implement a prototype application that will bridge knowledge across multiple sources to assist System Engineers (SEs) with requirements discovery and tracing, research question and use case identification, and assumption validation. Such a system will also allow SEs to more easily, and intuitively, explore the AAM ecosystem, ultimately improving the efficiency and effectiveness of the SE's research and decision-making processes surrounding ConOps development and validation. In this session, our team will provide a video demonstration of our new prototype architecture in action. We will also present an overview of our prototype system architecture and talk about its advantages over traditional LLM deployments along with how those advantages can provide additional value to the field of System Engineering.

systems engineering↗

NASA NTRSDate not supplied

Earth-Independent Medical Operations (EIMO) Concept of Operations

In contrast to the current crew health paradigm for low-Earth orbit and Lunar missions, which depends on real-time communication with Mission Control, deep-space exploration missions will require a significant shift in medical operations. This shift is driven by the constraints of operating at a considerable distance from Earth, such as resource limitations—lack of resupply, restricted mass, power, volume, and data—as well as communication delays and the inability to evacuate back to Earth during emergencies. To move toward a more self-reliant medical model, a strategy is needed to gradually increase space-based crew autonomy and reduce risks to mission success in the challenging environment of deep space. This transformative change, known as "Earth-Independent Medical Operations" (EIMO), explores the gradual transfer of medical care and decision-making from Earth-based support to space-based systems. The goal of this transition is to enhance astronaut health and performance while minimizing mission risks. EIMO requires the development of a medical system that integrates seamlessly with mission planning, vehicle and spacesuit design, and data architecture. This integration is crucial for building a robust medical infrastructure that not only safeguards astronaut well-being but also ensures overall mission success. The Human Research Program (HRP) Exploration Medical Capability (ExMC) Element has revised the EIMO model-based Concept of Operations (ConOps) which outlines an initial vision for EIMO. The ConOps, which is built on the stakeholders’ need, system goals, and objectives (NGOs), presents an array of in-mission scenarios that span a wide range of medical conditions demonstrating the system’s capabilities from basic to complex events. Developed by a multidisciplinary team of systems engineers, scientists, and clinicians within ExMC, the ConOps revision includes two new scenarios(Barotrauma and Self-Medical Management and Behavioral Health and Chronic Medical Care), and implementation of findings from EIMO technical interchange meetings that focused on data and training. The envisioned EIMO Medical System (MS) operates as a system of systems, gathering data from various sources such as reference databases, real-time wearable sensors, point-of-care diagnostics, and environmental controls. The MS also incorporates advanced training tools to support autonomous medical care, assisting the Crew Medical Officer (CMO) during medical events where Ground Support is either unavailable or communication-delayed beyond practicality. Furthermore, MS functions and capabilities were decomposed from the scenarios to establish foundational requirements for EIMO and traced to the NASA Spaceflight Human-System Standard(NASA-STD-3001, Volumes 1 and 2). These traces were performed to gain insights on the alignment of EIMO requirements with the NASA standard. This work serves as an initial recommendation to increase crew autonomy gradually and safely for Mars missions and future deep-space exploration.

medical system↗

NASA NTRS2017

Concept of Operations for RCO SPO

Reduced crew operations (RCO) refers to the reduction of crew members flying long-haul or military operations with more than one pilot onboard. Single pilot operations (SPO) refers to flying a commercial transport aircraft with only one pilot on board the aircraft, assisted by advanced onboard automation andor ground operators providing piloting support services. Properly implemented, RCO/SPO could provide operating cost savings while maintaining a level of safety no less than conventional two-pilot commercial operations. A concept of operations (ConOps) for any paradigm describes the characteristics of its various components and their integration in a multi-dimensional design space. This paper presents key options for humanautomation function allocation being considered by NASA in its ongoing development of RCO/SPO ConOps.

ConOps↗

NASA NTRS2021

High-Density Automated Vertiport Concept of Operations

The National Aeronautics and Space Administration (NASA) vision for Advanced Air Mobility (AAM) includes Urban Air Mobility (UAM) – a concept involving vertical takeoff and landing (VTOL) aircraft, decentralized (or federated) traffic management, and new infrastructure to support urban, suburban, and rural flight operations. High-density performance-based routes or corridors enable prompt transportation of people and goods from node to node, where each node represents a vertiport, defined as an identifiable ground or elevated area used for the takeoff and landing of VTOL aircraft. In the presence of uncertainty surrounding aircraft turnaround time on the ground, vertiports are the critical end points in scheduling, sequencing, and spacing (SSS) of aircraft in dense metropolitan environments. This Concept of Operations (ConOps) includes vertiports of varying sizes, configurations, service offerings, and locations. UAM air vehicles include conventional rotorcraft, unmanned VTOL aircraft, and novel piloted VTOL aircraft. This ConOps focuses on operations at a high-density vertiport, supported by a Vertiport Automation System (VAS) with high-throughput operation capabilities under conditions defined as NASA’s Urban Air Mobility Maturity Level Four (UML-4).

UAM↗

NASA NTRS2021

High-Density Automated Vertiport Concept of Operations

The National Aeronautics and Space Administration (NASA) vision for Advanced Air Mobility (AAM) includes Urban Air Mobility (UAM) – a concept involving vertical takeoff and landing (VTOL) aircraft, decentralized (or federated) traffic management, and new infrastructure to support urban, suburban, and rural flight operations. High-density performance-based routes or corridors enable prompt transportation of people and goods from node to node, where each node represents a vertiport, defined as an identifiable ground or elevated area used for the takeoff and landing of VTOL aircraft. In the presence of uncertainty surrounding aircraft turnaround time on the ground, vertiports are the critical end points in scheduling, sequencing, and spacing (SSS) of aircraft in dense metropolitan environments. This Concept of Operations (ConOps) includes vertiports of varying sizes, configurations, service offerings, and locations. UAM air vehicles include conventional rotorcraft, unmanned VTOL aircraft, and novel piloted VTOL aircraft. This ConOps focuses on operations at a high-density vertiport, supported by a Vertiport Automation System (VAS) with high-throughput operation capabilities under conditions defined as NASA’s Urban Air Mobility Maturity Level Four (UML-4).

Urban Air Mobility↗

DOE OSTI2024

Integration of New Technology Considering the Trade-Offs Between Operational Benefits and Risks: A Case Study of Dynamic Line Rating

Electric grid operators are adept at handling complexity and uncertainty. However, with increasing introduction of renewable generation, distributed energy resources, and more frequent severe weather events, operators will experience new workload and challenging decision scenarios. Here, this paper quantifies risks and benefits from an operator's perspective of introducing weather based forecast Dynamic Line Ratings (DLR) using variable wind conditions in addition to ambient temperature to relieve transmission congestion and facilitating more offshore wind (OSW). A concept of operations (CONOPS) applied to a forecast DLR implementation and its integration with OSW is defined. A method for evaluating tradeoffs of derating to make the rating more conservative but decreasing the benefit was developed and applied to a case study for two existing overhead transmission lines on Long Island, New York. The CONOPS uses historical day-ahead and hour-ahead High Resolution Rapid Refresh weather forecasts and weather station data to support planning and real-time operations. The analysis determines the risk of downgrades in real-time operational rating compared to the forecast and quantifies the frequency and severity of last-minute downgrades. The risk is compared against the benefits in increased capacity to provide insights on the additional amount of uncertainty DLR and OSW will add to the operator's workload.

17 WIND ENERGY↗

NASA NTRS2003

Small Aircraft Transportation System Simulation Analysis of the HVO and ERO Concepts

It is acknowledged that the aviation and aerospace industries are primary forces influencing the industrial development and economic well being of the United States and many countries around the world. For decades the US national air transportation system has been the model of success - safely and efficiently moving people, cargo, goods and services and generating countless benefits throughout the global community; however, the finite nature of the system and many of its components is becoming apparent. Without measurable increases in the capacity of the national air transportation system, delays and service delivery failures will eventually become intolerable. Although the recent economic slowdown has lowered immediate travel demands, that trend is reversing and cargo movement remains high. Research data indicates a conservative 2.5-3.0% annual increase in aircraft operations nationwide through 2017. Such growth will place additional strains upon a system already experiencing capacity constraints. The stakeholders of the system will continue to endure ever-increasing delays and abide lesser levels of service to many lower population density areas of the country unless more efficient uses of existing and new transportation resources are implemented. NASA s Small Aircraft Transportation System program (SATS) is one of several technologies under development that are aimed at using such resources more effectively. As part of this development effort, this report is the first in a series outlining the findings and recommendations resulting from a comprehensive program of multi-level analyses and system engineering efforts undertaken by NASA Langley Research Center s Systems Analysis Branch (SAB). These efforts are guided by a commitment to provide systems-level analysis support for the SATS program. Subsequent efforts will build upon this early work to produce additional analyses and benefits studies needed to provide the technical and economic basis for national investment and policy decisions related to further development and potential deployment of a small aircraft transportation system. This report primarily serves two purposes. First, it presents results attained from an initial evaluation and analysis of the Higher Volume Operations (HVO) and EnRoute Operations (ERO) concepts - both designated operational capabilities within the SATS Program s Concept of Operations (CONOPS) document. It further outlines areas of the concepts that would benefit from follow-on analyses and system engineering efforts. It is intended that these processes will aid continued maturation of the concepts and promote additional studies of their effects and influences in combination with other designated CONOPS currently under development. In essence, it establishes a baseline of data upon which subsequent analyses and studies can be built and identifies performance characteristics the concept must exhibit in order to provide, at minimum, levels of safety and usage equal to or better than the current system.

Millsaps, Gary D.↗