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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 163 records · Page 9

All sources NASA NTRS DOE OSTI

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 NTRSDate not supplied

Mars Sample Return Mars Ascent Vehicle Separation Analysis Utilizing the CLVTOPS Toolchain

A key element of the joint NASA and European Space Agency (ESA) Mars Sample Return (MSR) Campaign is the Mars Ascent Vehicle (MAV), which is being developed primarily by NASA Marshall Space Flight Center (MSFC), in association with NASA’s Jet Propulsion Laboratory (JPL) and Langley Research Center (LaRC). The MAV is a Mars-launched rocket that is responsible for transporting soil samples collected by the Perseverance rover from the Martian surface into orbit, where they will be captured by ESA's Earth Return Orbiter (ERO) for the return journey to Earth. The MAV design concept developed during the MAV Systems Requirement Cycle (SRC) and Preliminary Design Cycle (PDC) consisted of a two-solid-stage configuration, where the second stage is completely unguided in order to reduce vehicle and overall mission mass. The unguided second stage design presents technical challenges for the stage separation event, as the second stage trajectory and the payload’s ability to rendezvous with the ERO is extremely sensitive to disturbances during vehicle staging. The MSFC-developed CLVTOPS multibody dynamics toolchain was utilized to quickly assess multiple stage separation hardware options and to optimize the separation Concept of Operations (ConOps) in order to ensure successful near-field stage separation performance and maximize the orbital accuracy of the payload. This paper will describe how the CLVTOPS toolchain was used to assess the MAV stage separation event and help inform and optimize the MAV design and ConOps.

MSR↗

DOE OSTI2020

Quantifying Human Behavior and Decision Errors in Security Screening Operations

The potential for human errors in conducting security related screening operations can lead to inadvertent and adverse decision outcomes. This paper overviews an initial mathematical framework designed to model and quantify the various human factors and decision outcomes that may occur in conducting security screening operations, such as U.S. port of entry radiological and nuclear (rad/nuc) security screening. This framework is based on the Human Error Assessment and Reduction (HEART) technique. As applied here, the framework incorporates a set of rules for human engagement, including a prescribed concept of operations (CONOPS) and deviations that may occur from this established CONOPS due to inadvertent personnel decision errors. We also review some of the various factors that may adversely influence such decisions by security screening personnel. Some of these factors include current workload, environmental conditions, training, and various other intangible factors. Using the HEART methodology, we translate each of these factors into error producing conditions, their effects on error, an assessed proportion of effects, and finally the overall probability of human error at each stage of the screening process. We then include a small scale example to demonstrate the methodology and results based on an assumed set of input conditions at a notional port of entry.

Brigantic, Robert T.↗

DOE OSTI2024

AGN-201 Digital Twin Concept of Operations

The AGN-201 is a nuclear reactor at Idaho State University (ISU) and is currently being used in the development of a digital twin (DT) with Idaho National Laboratory (INL). The goal is to create a DT (called the AGN-201 DT) which can monitor an operating nuclear reactor to determine when the reactor is being operated normally; normal operations are any operations that is declared by the ISU staff. To accomplish this, researchers at INL developed a DT ecosystem which can ingest data from the AGN-201 reactor. This data is fed into a series of machine learning (ML) and reactor physics models. The ML and reactor physics models assess the data and determine if the reactor is operating normally. Event(s) that are flagged as anomalies are investigated by the INL staff to determine if any undeclared experiments were conducted. The AGN-201 DT was verified in July/August 2023, when the ISU staff performed undeclared experiments and the INL staff were able to assess the anomalous events and determine what likely caused each event. This project was a steppingstone to promote the use of DTs for international safeguards and marks the first time a DT was able to monitor a nuclear reactor for this purpose. This document provides the concept of operations (CONOPS) for the AGN-201 digital twin (DT). The CONOPS describes how the AGN-201 and AGN-201 DT are expected to operate and details how each are established.

21 SPECIFIC NUCLEAR REACTORS AND ASSOCIATED PLANTS↗

DOE OSTI2025

Rancor Integrated Procedure System (RIPS): A Computer-Based Procedure Platform for Advanced Reactor Research

The Rancor Microworld Simulator is a simplified, pressurized water, small modular reactor simulator that includes a multi-unit plant model server, an advanced digital human-machine control interface, and the Rancor Integrated Procedure System (RIPS). Rancor provides a research and development tool that can be used for collecting operator performance data and for prototyping concepts of operations (ConOps) for advanced reactor development. RIPS is meant as a research tool and includes many unique features: (1) RIPS has a robust procedure authoring system. (2) RIPS has the capability to run any of the three IEEE-Std-1786 computer-based procedure types. (3) RIPS can be configured to take on the look and feel of different vendors’ computer-based procedure systems for the purpose of developing and evaluating different ConOps for plant upgrades or new builds. (4) RIPS includes the capability for logging operator procedure use, including integrating procedure logs with Rancor simulator logs, thereby allowing automated data collection of operator scenario runs. (5) RIPS integrates with the Human Unimodel for Nuclear Technology to Enhance Reliability (HUNTER), a dynamic human reliability analysis environment that creates a digital human twin or virtual operator to mimic reactor operator performance. (6) RIPS includes support for automation of plant monitoring and control functions. While RIPS is explicitly built into Rancor, it may also be used with full-scope training simulators. This functionality allows RIPS to be used for existing plants and advanced reactors under development.

99 - GENERAL AND MISCELLANEOUS↗

DOE OSTI2023

Office of Nuclear Verification FY 2023 Quarterly Report TSVT Q1

This project encompasses the continued development and training of a U.S. operational team, the Test Site Verification Team (TSVT), supporting verification of nuclear testing activities. TSVT builds on decades of U.S. nuclear testing history and nuclear explosion monitoring experience. The Team maintains readiness to deploy internationally on short notice to provide field-based support of verification of declared or undeclared nuclear testing and associated activities, as well as follow-on activities including monitoring and capability disablement and dismantlement, as established by negotiated agreement or treaty. The roles and structure of the TSVT are integrated with other NA-243 deployable verification teams and the interagency. FY23 TSVT activities focus on continued capability buildup within the team, including Team trainings and exercises with a focus on missions in confined spaces (e.g., tunnels, mines, other underground facilities), increased familiarity with foreign nuclear weapons testing programs, demonstration of Team capacity to deploy, train, and practice sustained OPSEC in non-western locations, establishment of sustainable storage and maintenance of equipment, specification and procurement of additional equipment to support field observations, further evolution of concepts of operation documents (CONOPs), and mission coordination with Headquarters and associated Stakeholders. Activities will culminate with a full-scale domestic team exercise at the end of FY23 focusing on underground activities signatures/observations and safety including advanced outdoor safety and familiarity in working around explosive test environments. In addition, we will be further articulating approaches and capacity relevant to the identification of nuclear tests, as well as monitoring of nuclear testing activities and/or dismantlement of nuclear test sites and anticipate developing additional equipment requests in support of this evolution. The TSVT Team Leads will also coordinate with its Senior Advisor, the TSVT Logistics and Readiness (L&R) Training Lead, and NNSA Headquarters to draft a five-year TSVT training and exercise plan, that strategically and incrementally builds capacity and expertise in key areas of significance for the continuum of nuclear and nuclear-related testing activities that fall within the team’s mission space.

42 ENGINEERING↗

NASA NTRSDate not supplied

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↗

NASA NTRSDate not supplied

A Science-Focused Artificial Intelligence (AI) Responding in Real-Time to New Information: Capability Demonstration for Ocean World Missions

Introduction: Artificial intelligence (AI) has long been considered a potential mechanism to explore increasingly challenging environments, including those with extreme temperatures and pressures, limited communication capabilities, or those with demanding terrain. We posit that missions in extreme environments could deploy an onboard AI focused on science observations and goals in order to augment a traditional concept(s) of operations (ConOps). An onboard AI capability could perform functions such as data analysis in order to make high-level decisions, including prioritized data transmission for analysis by ground-based teams or autonomously-guided follow-on analyses that maximize science return. Such a capability would empower missions to respond to scientific data of interest in real-time; a mission could make observations and perform a preliminary analysis to alert ground-based scientists to an observation of interest, enabling an informed, rapid response from Earth-based teams. Enceladus Case Study for Onboard AI: We are developing an onboard AI capability for real-time telemetry response that formulates and carries-out informed decisions in service to established mission goals, enabling increased science return of a mission. We focus our AI development for use on a constellation of SmallSats orbiting Enceladus. Our Enceladus case study tests autonomous decision-making capabilities in scenarios with complex orbital dynamics, plume ejecta, extreme cold environments, power restrictions, and a requirement to maximize science return for a potential positive detection of life, while critically evaluating the potential for false positives. Telemetry includes simulated scientific data, spacecraft onboard operational data (e.g., position, velocity, and rotation), and engineering hardware performance data. Enceladus SmallSat Constellation. Our constellation includes eight SmallSat spacecraft in an 8:35 resonant orbit-based formation, leveraging Saturn’s gravitational forces to maintain stable orbits with global coverage around Enceladus. To our knowledge, we simulate the first stable configuration of multiple spacecraft in closed orbits around Enceladus, using a full ephemeris force model (Russell and Lara, 2009). Each spacecraft’s orbit will precess, causing an eastward ground track shift (from an orbiter’s perspective) of each spacecraft for each orbit. However, all spacecraft return to their original positions relative to Enceladus after eight Enceladus revolutions around Saturn. We model communication pathways between SmallSats to understand how information would need to be transmitted across the constellation to enable AI-driven decision-making and resource allocation across the fleet. Capability Demonstration. Our simulated capability demonstration inputs position, velocity, and rotation telemetry from our Enceladus-focused constellation simulations, and mass spectrometry data collected from abiotic and biotic laboratory-analog ocean world experiments (Theiling et al., 2018; Theiling, 2021; Da Poian et al., 2023). Data from these experiments are used to simulate MS measurements and different scenarios of science observations for onboard analysis performed on each of the eight spacecraft. For these demonstrations, we integrate 24 machine learning (ML) algorithms into an onboard intelligence as a ‘knowledge base’, including algorithms evaluating data quality and those predicting (with % confidence) gas composition, ocean aqueous chemistry, and whether the sample was influenced by microbial life. The onboard AI capability is designed to use the knowledge base to come to a consensus-based decision in the interpretation of the observed data in order to request additional action outside of a pre-defined ConOps. Requested actions could include e.g., prioritized downlink to Earth (for analysis by ground-based teams) or follow-on analyses performed across the constellation. The spacecraft’s intelligent onboard planner must then determine whether sufficient resources (e.g., time, power, etc.) are available and weigh the request with mission priorities. In our simulation, the constellation is able to identify potential biosignatures using onboard ML algorithms, evaluate the confidence of that prediction, and perform follow-on analyses across the fleet to confirm the detection, in order to best prepare a transmission of these data to Earth-based teams.

astrobiology↗

NASA NTRS2011

Update - Concept of Operations for Integrated Model-Centric Engineering at JPL

The increasingly ambitious requirements levied on JPL's space science missions, and the development pace of such missions, challenge our current engineering practices. All the engineering disciplines face this growth in complexity to some degree, but the challenges are greatest in systems engineering where numerous competing interests must be reconciled and where complex system level interactions must be identified and managed. Undesired system-level interactions are increasingly a major risk factor that cannot be reliably exposed by testing, and natural-language single-viewpoint specifications areinadequate to capture and expose system level interactions and characteristics. Systems engineering practices must improve to meet these challenges, and the most promising approach today is the movement toward a more integrated and model-centric approach to mission conception, design, implementation and operations. This approach elevates engineering models to a principal role in systems engineering, gradually replacing traditional document centric engineering practices.

The Concept of Operations (ConOps)↗

NASA NTRSDate not supplied

SDSP Lessons Learned from UTM CONOPS

Presentation on Supplemental Data Service Providers from the UAS Traffic Management Concept of Operations

Unmanned Aviation System Traffic Management↗

NASA NTRS2018

Concept of Operations for Management by Trajectory

This document describes Management by Trajectory (MBT), a concept for future air traffic management (ATM) in which every flight operates in accordance with a four-dimensional trajectory (4DT) that is negotiated between the airspace user and the Federal Aviation Administration (FAA) to respect the airspace user's goals while complying with National Airspace System (NAS) constraints. In the present-day NAS, the ATM system attempts to predict the trajectory for each flight based on the approved flight plan and scheduled or controlled departure time. However, once the aircraft starts to move, controllers tactically manage the aircraft to implement traffic management restrictions, separate otherwise conflicting aircraft, and address arising NAS constraints. Tactical controller actions are not directly communicated to the automation systems or other stakeholders. Furthermore, the initial trajectory prediction does not anticipate these disruptions or how they will impact the flight. Consequently, and compounded by gaps in required data and models, trajectory predictions are less accurate than possible, which affects Traffic Flow Management (TFM) performance. A cornerstone of the MBT concept is that all air vehicles have, at all times, an assigned 4DT from their current state to their destination. These assigned trajectories consist of trajectory constraints and descriptions. Pilots and air traffic controllers, with the aid of automation, operate the aircraft to comply with the assigned trajectory, unless first negotiating a revision. Equipped aircraft have substantial responsibility for complying with the assigned trajectory without controller intervention. To maximize the operational flexibility available to the airspace user, the assigned trajectory only imposes trajectory constraints as required to achieve the ATM goals of NAS constraint compliance and aircraft separation. Trajectory descriptions are added to the assigned trajectory to ensure sufficient predictability. To further improve trajectory prediction accuracy, airspace users supplement the assigned trajectory by broadcasting intent information and updating it as necessary. Air vehicle intent is a more detailed description of the airspace user's plan for how the flight will fly the assigned trajectory. Air vehicle intent can change freely, without negotiation, as long as it remains in compliance with the assigned trajectory. Aircraft assigned trajectories, air vehicle intent, and predicted trajectories are shared, creating a common view among stakeholders. A NAS Constraint Service gathers and publishes information about all known NAS constraints, enabling airspace users to be informed participants in trajectory negotiation. Trajectory constraints in the assigned trajectory are mapped to NAS constraints to facilitate identifying which aircraft are affected when NAS constraints change. To support efficient trajectory negotiation, all aircraft provide current information about air vehicle capabilities. Assigned trajectories are constructed to satisfy all known NAS constraints, improving trajectory stability and predictability. Uncertainty and disruptions are handled by modifying the assigned trajectory as far in advance as possible. By proactively negotiating changes to the assigned trajectory, rather than relying on controller-selected tactical actions such as vectors to resolve traffic conflicts or implement miles-in-trail restrictions, MBT keeps aircraft on closed trajectories that are fully known to all stakeholders. Since reactive air traffic control actions cannot be predicted in advance, the downstream trajectory cannot be accurately predicted until they happen. Reliable trajectory predictions allow the system to identify needed modifications to trajectories further in advance, where they can be negotiated and communicated as amendments (i.e., additional or altered trajectory constraints) to the assigned trajectory. Decision Support Tools (DSTs) aid controllers in rapidly defining and communicating closed trajectories to the aircraft and support all stakeholders in trajectory negotiation. Anticipated MBT benefit mechanisms include more accurate trajectory predictions, improved ATM performance and robustness to off-nominal conditions, increased flexibility and operational efficiency, reduced impediments to emerging classes of airspace users accessing NAS resources, reduced environmental impacts, and enhanced safety.

ConOps↗

NASA NTRS2011

Deep Space Habitat Team: HEFT Phase 2 Effects

HEFT was a NASA-wide team that performed analyses of architectures for human exploration beyond LEO, evaluating technical, programmatic, and budgetary issues to support decisions at the highest level of the agency in HSF planning. HEFT Phase I (April - September, 2010) and Phase II (September - December, 2010) examined a broad set of Human Exploration of Near Earth Objects (NEOs) Design Reference Missions (DRMs), evaluating such factors as elements, performance, technologies, schedule, and cost. At end of HEFT Phase 1, an architecture concept known as DRM 4a represented the best available option for a full capability NEO mission. Within DRM4a, the habitation system was provided by Deep Space Habitat (DSH), Multi-Mission Space Exploration Vehicle (MMSEV), and Crew Transfer Vehicle (CTV) pressurized elements. HEFT Phase 2 extended DRM4a, resulting in DRM4b. Scrubbed element-level functionality assumptions and mission Concepts of Operations. Habitation Team developed more detailed concepts of the DSH and the DSH/MMSEV/CTV Conops, including functionality and accommodations, mass & volume estimates, technology requirements, and DDT&E costs. DRM 5 represented an effort to reduce cost by scaling back on technologies and eliminating the need for the development of an MMSEV.

Toups, Larry D.↗

NASA NTRSDate not supplied

SysML Success Tree for DAVINCI In-Situ Campaign Requirements Validation and Redundancy Assessment

The DAVINCI mission will scientifically study the Venusian atmosphere to better understand the current state of the planet and its evolutionary history. This will be accomplished by deploying a descent probe to collect in-situ atmospheric dynamic and spectroscopic measurements, characterize ambient temperatures and pressures during descent, and surface imaging below the cloud layer. To better characterize the DAVINCI In-Situ Campaign, a success tree, developed in the SysML tool, MagicDraw, was created to define the events necessary to have a successful in-situ campaign, for each phase of the campaign. This success tree was also used to validate DAVINCI Program, Mission, and Element level requirements. In addition, because DAVINCI is a single-string mission, the success tree was also used to identify areas of redundancy and resiliency throughout the campaign. The initial redundancy assessment recommended further on-orbit evaluation of the probe’s communication system, as well as further evaluation of the ability of the mass spectrometer turbo-molecular pump to handle the expected decent environment. During the integration and test phase of the overall mission, the success tree will be used to guide the mission validation process, helping to ensure that the in-situ mission elements can perform in accordance with the DAVINCI In-Situ Concept of Operations document.

ConOps↗

NASA NTRS2010

UAS Integration into the NAS Project

The goal of the UAS Integration in the NAS Project is to contribute capabilities that reduce technical barriers related to the safety and operational challenges associated with enabling routine UAS access to the NAS This goal will be accomplished through a two-phased approach of system-level integration of key concepts, technologies and/or procedures, and demonstrations of integrated capabilities in an operationally relevant environment. Technical objectives include: PHASE 1: a) Validating the key technical areas identified by this project. System-level analyses, a State of the Art Analysis (SOAA), and a ConOps will identify the challenges and barriers preventing routine UAS access to the NAS. b) Developing a national roadmap and gap analysis identifying specific deliverables in the area of operations, procedures, and technologies that will impact future policy decisions. PHASE 2: a) Provide regulators with a methodology for developing airworthiness requirements for UAS and data to support development of certifications standards and regulatory guidance. b) Provide systems-level integrated testing of concepts and/or capabilities that address barriers to routine access to the NAS. Through simulation and flight testing, address issues including separation assurance, communications requirements, and Pilot Aircraft Interfaces (PAIs) in operationally relevant environments

Bauer, Jeff↗

NASA NTRSDate not supplied

SysML Success Tree for DAVINCI In-Situ Campaign Requirements Validation and Redundancy Assessment

model-based↗

NASA NTRSDate not supplied

SysML Success Tree for DAVINCI In-Situ Campaign Requirements Validation and Redundancy Assessment

model-based↗

NASA NTRS2010

Constellation Architecture Team-Lunar Scenario 12.0 Habitation Overview

This paper will describe an overview of the Constellation Architecture Team Lunar Scenario 12.0 (LS-12) surface habitation approach and concept performed during the study definition. The Lunar Scenario 12 architecture study focused on two primary habitation approaches: a horizontally-oriented habitation module (LS-12.0) and a vertically-oriented habitation module (LS-12.1). This paper will provide an overview of the 12.0 lunar surface campaign, the associated outpost architecture, habitation functionality, concept description, system integration strategy, mass and power resource estimates. The Scenario 12 architecture resulted from combining three previous scenario attributes from Scenario 4 "Optimized Exploration", Scenario 5 "Fission Surface Power System" and Scenario 8 "Initial Extensive Mobility" into Scenario 12 along with an added emphasis on defining the excursion ConOps while the crew is away from the outpost location. This paper will describe an overview of the CxAT-Lunar Scenario 12.0 habitation concepts and their functionality. The Crew Operations area includes basic crew accommodations such as sleeping, eating, hygiene and stowage. The EVA Operations area includes additional EVA capability beyond the suitlock function such as suit maintenance, spares stowage, and suit stowage. The Logistics Operations area includes the enhanced accommodations for 180 days such as enhanced life support systems hardware, consumable stowage, spares stowage, interconnection to the other habitation elements, a common interface mechanism for future growth, and mating to a pressurized rover or Pressurized Logistics Module (PLM). The Mission & Science Operations area includes enhanced outpost autonomy such as an IVA glove box, life support, medical operations, and exercise equipment.

Kennedy, Kriss J.↗

NASA NTRS2018

Air Traffic Management Technology Demonstration - 3 (ATD-3) Dynamic Weather Routes Domestic En Route Concept of Operations Synopsis Version 1.0

NASA conducted a survey in 2015 of stakeholders in industry, flight operators, and others to collect data on the most pressing air traffic management (ATM) issues impacting en route operations. Weather related delays and interruptions were identified as the most significant and costly problem impacting en route operations in today's system. Additionally, future traffic demands will place greater demands on the FAA's air traffic control system, necessitate a more efficient and integrated traffic management system and provide controller tools to leverage human productivity. Consequently, NASA is assembling a suite of integrated ground and aircraft-based technologies and decision-making aids under the Airspace Technology Demonstrations 3 (ATD-3) project to continuously search for more efficient weather-avoidance routes and to rapidly respond to weather changes and associated traffic management initiatives. These route efficiency enhancements are targeted at en route airspace and will enable continued use of en route and arrival metering in the presence of weather. NASA's Dynamic Weather Routes (DWR) concept represents a subset of those technologies and focuses primarily on the cruise phase of flight. It leverages existing air traffic weather, airspace, and traffic data, as well as improvements in navigation, surveillance, communication and digital network technologies, and builds upon existing ATM automation to address the shortcomings associated with strategic traffic flow management initiatives and weather forecasting uncertainties. The potential benefits in the form of time, fuel, and cost savings are significant. This concept of operations synopsis provides a detailed description of DWR, its potential benefits and notional implementation paths.

DWR↗