Search NASA⌕ Search

SEARCH · Search NASA

Results for “Concept of Operations”

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 289 records · Page 16
All sourcesNASA NTRSDOE OSTI
NASA NTRS2002

Flight Test Evaluation of the Airborne Information for Lateral Spacing (AILS) Concept

The Airborne Information for Lateral Spacing (AILS) concept is designed to support independent parallel approach operations to runways spaced as close as 2,500 feet. This report briefly describes the AILS operational concept and the results of a flight test of one implementation of this concept. The focus of this flight test experiment was to validate a prior simulator study, evaluating pilot performance, pilot acceptability, and minimum miss-distances for the rare situation in which an aircraft on one approach intrudes into the path of an aircraft on the other approach. Although the flight data set was not meant to be a statistically valid sample, the trends acquired in flight followed those of the simulator and therefore met the intent of validating the findings from the simulator. Results from this study showed that the design-goal mean miss-distance of 1,200 feet to potential collision situations was surpassed with an actual mean miss-distance of 1,859 feet. Pilot reaction times to the alerting system, which was an operational concern, averaged 0.65 seconds, were well below the design goal reaction time of 2.0 seconds. From the results of both of these tests, it can be concluded that this operational concept, with supporting technology and procedures, may provide an operationally viable means for conducting simultaneous, independent instrument approaches to runways spaced as close as 2500 ft.

Abbott, Terence S.↗
NASA NTRS2020

In-time System-wide Safety Assurance (ISSA) Concept of Operations and Design Considerations for Urban Air Mobility (UAM)

Emerging operations involving Advanced Air Mobility (AAM), such as Urban Air Mobility (UAM), pose a challenge to safety assurance and to accessibility within the National Airspace System (NAS).In particular, the public has a low tolerance for risk in aviation and the current NAS tends to be labor-intensive with limited ability to scale up for UAM. In response to this landscape, NASA is collaborating with industry to define a Concept of Operations (ConOps) for In-time System-Wide Safety Assurance (ISSA) for scalable UAM involving a service-oriented architecture. This architecture focuses safety investments for technological solutions that can overcome safety related barriers for emerging operations. By working with industry, consensus can be reached on desirable system traits that are based on integration and fusion of data and leverage increasingly autonomous and automated systems. These complex systems can identify anomalies, precursors, and trends that together enable more proactive management of operational risks. AAM and UAM elevate the need for risk management in relation to increasing density and heterogeneity of vehicles and operations. Whereas safety in today’s NAS is built on a history of programs and technologies that react to incidents and accidents, AAM presents an opportunity to leverage that experience and its implications and proactively integrate safety into the earliest designs of vehicles and systems. In a perfect world AAM and UAM would not be inherently dangerous but until then ensuring the highest quality of safety requirements is the bridge to mitigating risks.

In-Time System-Wide Safety Assurance↗
NASA NTRSDate not supplied

Implementation of a SysML Model-Based Concept of Operations for Level of Care IV: Long-Duration Lunar Orbital and Surface Operations

One 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 orbital and surface operations for long duration lunar missions. This is accomplished through the development of a Medical System Foundation, which communicates medical system requirements, capabilities, conditions, and resources that define a starting point for a medical system that meets the specification for design reference missions and associated Levels of Care (as defined by NASA-STD-3001). The starting point for creating this Medical System Foundation Model is the development of a Concept of Operations (ConOps) that describes the operation of the system from the point of view of the users. It includes a comprehensive and thoroughly vetted list of the users, their specific needs, the goals of the system, key assumptions about the system, and definitions of the system’s operational environments. The use case scenarios included in the 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. For this “Long Duration” Medical System Foundation development effort, ExMC replaced the traditional document-based ConOps with a model-based ConOps using model-based systems engineering. This approach has several advantages, including the facilitation of more efficient understanding of the material through information-dense images with less opportunity for misinterpretation than text alone, the roll-out of changes to the ConOps to stakeholders in real-time as they are approved, and the consolidation of all salient information into one centralized location. This discussion will focus on both how the model represents the ConOps content and how the SE team utilized lessons learned in an agile environment to improve the way this information was created and presented to stakeholders.

M Kaetzer↗
NASA NTRSDate not supplied

Implementation of a SysML Model-Based Concept of Operations for Level of Care IV: Long-Duration Lunar Orbital and Surface Operations

One 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 orbital and surface operations for long duration lunar missions. This is accomplished through the development of a Medical System Foundation, which communicates medical system requirements, capabilities, conditions, and resources that define a starting point for a medical system that meets the specification for design reference missions and associated Levels of Care (as defined by NASA-STD-3001). The starting point for creating this Medical System Foundation Model is the development of a Concept of Operations (ConOps) that describes the operation of the system from the point of view of the users. It includes a comprehensive and thoroughly vetted list of the users, their specific needs, the goals of the system, key assumptions about the system, and definitions of the system’s operational environments. The use case scenarios included in the 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. For this “Long Duration” Medical System Foundation development effort, ExMC replaced the traditional document-based ConOps with a model-based ConOps using model-based systems engineering. This approach has several advantages, including the facilitation of more efficient understanding of the material through information-dense images with less opportunity for misinterpretation than text alone, the roll-out of changes to the ConOps to stakeholders in real-time as they are approved, and the consolidation of all salient information into one centralized location. This discussion will focus on both how the model represents the ConOps content and how the SE team utilized lessons learned in an agile environment to improve the way this information was created and presented to stakeholders.

Mary Susan Kaetzer↗
NASA NTRS2012

Mission Concepts and Operations for Asteroid Mitigation Involving Multiple Gravity Tractors

The gravity tractor concept is a proposed method to deflect an imminent asteroid impact through gravitational tugging over a time scale of years. In this study, we present mission scenarios and operational considerations for asteroid mitigation efforts involving multiple gravity tractors. We quantify the deflection performance improvement provided by a multiple gravity tractor campaign and assess its sensitivity to staggered launches. We next explore several proximity operation strategies to accommodate multiple gravity tractors at a single asteroid including formation-flying and mechanically-docked configurations. Finally, we utilize 99942 Apophis as an illustrative example to assess the performance of a multiple gravity tractor campaign.

Foster, Cyrus↗
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. These ambitious goals will require significant changes to in-flight and habitat medical care due to constraints on mass, volume, power, crew time and medical evacuation capabilities. These constraints make it absolutely necessary to develop transformative solutions using new technologies. 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. The Clinical Decision Support (CDS) project addresses the gap Medical-701 within the Inflight Medical Conditions risk: Enhance medical capabilities within an exploration medical system. For long-duration, deep space missions, computational and data resources will play an important role in maintaining crew health, wellness and performance where the crew will need to be more self-reliant. The aim of the CDS project is to develop and provide recommended requirements for an in-vehicle CDSS that acts as an assistant for delivering optimal health and performance and medical care during exploration missions. The CDSS is envisioned as a software-based tool that will augment a crewmembers’ knowledge, skills and abilities to assist in decision-making and crew health and performance (CHP) management thus increasing CHP systems capabilities. The human interface will be context aware and lessen the cognitive load to assimilate and use information as well as combine large disparate data sets in such a manner that provides the crew with actionable insight to decisions related to crew medical, health and performance management. Crew autonomy will be provided through a CDS that 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. The CDS project addresses the need for crew members to operate independently during long duration space exploration missions that require medical Levels of Care (LoC) V, the highest level specified by NASA-STD-3001 and described in more detail by the ExMC interpretation of LoC document (NASA/TM-2017-219290), where significant changes to in-flight and habitat medical care necessitate increasing crew autonomy in decision making and task performance. The CDS project will develop and test a series of iterative and increasingly more complex system prototypes. These annual demonstrations of the data system integration with the crew health and performance domain will inform exploration medical system requirements for an on-board Clinical Decision Support System (CDSS) through a series of use cases that guide CDS prototype functionality. CDS concepts are based on ExMC Concept of Operations documents (presented separately) and will highlight architecture extensibility to other more complex analyses and tests using core crew health and performance integrated data management, processing and visualization capabilities. This approach also establishes how externally developed analyses and approaches could be added to expand a clinical decision support system and thus highlight how a comprehensive system can be commercially and/or globally developed. The CDS project will build upon the concept of an integrated data management approach based on the Medical Data Architecture (MDA) project to more fully address challenges associated with in-flight and habitat medical, health and performance care due to constraints on mass, volume, power, crew time and medical evacuation capabilities required for medical LoC V. These requirements will be derived through systems engineering approaches and software prototype developments over the course of the multi-year CDS project to address crew health and performance decision-making and task performance, often autonomously executed by the crew, in a manner that is consistent with the appropriate medical level of care for the mission. This presentation will provide an overview of the vision for the CDS project and highlight the initial accomplishments in project planning, implementation and requirements identification in fiscal year 2020.

clinical decision support↗
NASA NTRS2019

IMPACT Concept of Operations

NASA’s future exploration missions mandate a significant paradigm change for mission planning, spacecraft design, human systems integration, and in-flight medical care due to constraints on mass, volume, power, resupply missions, and medical evacuation capabilities. These constraints require further development of the human health and performance system, which includes the medical, task performance, wellness, data, human and other systems necessary to keep the crew healthy and functioning optimally. The human health and performance system will be tightly integrated with mission and habitat design to provide a sufficient human health and performance infrastructure to enable mission success. A suite of systems engineering tools will aid in the decision making process for the development of such a human health and performance system. This Concept of Operations provides a vision for a tool suite to conduct evaluations of human health and performance system options, inform research prioritization, and provide trade study support, based on evidence, risks, and systems engineering principles. The integrated tool suite under development is IMPACT.

Lumpkins, Sara↗
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↗
NASA NTRS2021

Concept of Operations for OSIRIS-REx Optical Navigation Image Planning

Optical navigation (OpNav) is a critical subsystem of the OSIRIS-REx asteroid sample return mission, which operated in the vicinity of near-Earth asteroid (101955) Bennu from August 2018 through April 2021. A substantial amount of mission resources across multiple subsystems and institutions is required to ensure that the OpNav data are successfully acquired. The KinetX OpNav team, part of the Flight Dynamics System (FDS), is responsible for performing required analysis to develop the OpNav operations plans; requesting, reviewing and verifying the plans; and ultimately using the image data for critical navigation operations. The FDS team, responsible for the mission navigation, is operated by KinetX Aerospace with management and operations support from NASA’s Goddard Space Flight Center. The Science Processing and Operations Center (SPOC), located at the University of Arizona’s Lunar and Planetary Laboratory, is responsible for generating the planning products for all science and most OpNav data. These plans are integrated into the spacecraft sequences, tested, and commanded by the Mission Support Area (MSA) at Lockheed Martin Space. To ensure mission-critical navigation image data are successfully acquired, the plan is developed through a waterfall of planning cycles over the course of 3 months prior to onboard plan execution. During the initial strategic planning for a mission phase, detailed analysis is performed by the OpNav team to conceptualize the concept of operations (ConOps) for image data collection. This phase OpNav Narrative is included along with other strategic planning documents for the key ground segment stakeholders to review and provide feedback. The detailed OpNav plans get defined in the tactical planning cycle, which spans 8 to 3 weeks before the week-long integrated sequence is executed on-board the spacecraft. During the tactical cycle, the initial OpNav Request is submitted along with the science requests, kicking off development of the science and OpNav plans. Once the initial plan is drafted, interfaces are exercised so that the plan can be reviewed and iterated, if necessary. A rigorous schedule is followed by the planning teams during the implementation cycle, spanning the last 18 days before uplink, to ensure all the necessary integration, testing, and reviewing can occur on time. The development of the OpNav planning ConOps, including responsibilities, interfaces, timelines, and procedures, took extensive collaboration across mission elements and institutions. The process was robust throughout the 137 weeks of continuous Optical Navigation Operations at Bennu, which concluded on April 9th, 2021.

Coralie D. Adam↗
NASA NTRS2018

Air Traffic Management Technology Demonstration - 3 (ATD-3) Multi-Flight Common Route (MFCR) Concept of Operations Version 1.0

NASA's Multi Flight Common Route (MFCR) automation represents one element of those technologies focusing primarily on delay recovery in the en route phase of flight. Delay recovery is an attenuation of flight-time delay, accomplished by periodically revising weather-avoidance routing as the convective weather system evolves. MFCR is intended for use by Traffic Management Coordinators (TMCs) in Air Route Traffic Control Centers (ARTCCs, or Centers) and traffic management specialists (TMSs) in the Air Traffic Control System Command Center (ATCSCC). MFCR leverages existing weather, airspace, and traffic data, as well as improvements in navigation, surveillance, communication, and digital information technologies, to build on existing ATM automation and address some of the shortcomings associated with strategic traffic flow management initiatives and weather forecasting uncertainties. These capabilities provide significant potential benefits in the form of time, fuel, and cost savings. The concept of operations described in this document describes MFCR functionality as delivered by NASA to the FAA in December 2017, including a list of potential enhancements that may be realized when the system is fielded.

conops↗
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↗
NASA NTRSDate not supplied

Assessment of a Surface Propellant Transportation System Concept for Operations on Mars

NASA is working to define the architecture needed for a Mars exploration campaign. One potential architecture option allows for pre-deployment of essential cargo and equipment to support a crew landing, including the pre-positioning of a Mars Ascent Vehicle (MAV). This MAV is likely to represent the largest single payload that must be landed on the Martian surface. Its size would be influenced by the amount of mass that state-of-the-art Entry, Descent, and Landing (EDL) systems would be capable of placing on Mars. One possible method of increasing the usable size of the MAV without exceeding available EDL capabilities is to land the MAV without its ascent propellant on board. Following such a method may necessitate a strategy to acquire sufficient ascent propellant to allow a crew to safely depart the Martian surface. This paper describes a conceptual return propellant strategy that uses a liquid transportation skid, or pallet, to be used in conjunction with a rover mobility system to transfer cryogenic propellant, consisting of oxygen and methane, across the Martian surface from a delivery lander to the MAV to enable its launch. Design considerations, concept of operations, and rover energetics will be discussed in this paper.

Propellant↗
NASA NTRSDate not supplied

Assessment of a Surface Propellant Transportation System Concept for Operations on Mars

NASA is working to define the architecture needed for a Mars exploration campaign. One potential architecture option allows for pre-deployment of essential cargo and equipment to support a crew landing, including the pre-positioning of a Mars Ascent Vehicle (MAV). This MAV is likely to represent the largest single payload that must be landed on the Martian surface. Its size would be influenced by the amount of mass that state-of-the-art Entry, Descent, and Landing (EDL) systems would be capable of placing on Mars. One possible method of increasing the usable size of the MAV without exceeding available EDL capabilities is to land the MAV without its ascent propellant on board. Following such a method may necessitate a strategy to acquire sufficient ascent propellant to allow a crew to safely depart the Martian surface. This presentation describes a conceptual return propellant strategy that uses a liquid transportation skid, or pallet, to be used in conjunction with a rover mobility system to transfer cryogenic propellant, consisting of oxygen and methane, across the Martian surface from a delivery lander to the MAV to enable its launch. Design considerations, concept of operations, and rover energetics will be discussed in this presentation.

Surface↗
NASA NTRSDate not supplied

Crew Performance Support System to Aid in Anomaly Resolution: Concept of Operations

As missions progress into deep space, communication delays and disruptions will disenable the crew’s reliance on Earth experts. There are also limitations in the amount of data that can be downlinked to the ground. It is prudent to assume that critical, complex vehicle or habitat sub-systems will malfunction at a time when a lunar or Mars’ crew cannot rely on the Earth-Support team to detect, diagnose and resolve the problem and it is impractical to expect a small crew to step-in with the same level of expertise as 50+ authorities. The crew will need novel processes and advanced technological support to independently identify and resolve safety- and time-critical anomalies. That a self-reliant crew is unable to respond appropriately to time-critical anomalies is a significant risk to crew safety and mission success. This risk is driven by several factors; novel and unanticipated anomalies would not have been trained pre-flight, the crew could forget their pre-flight training or spaceflight stressors could impair the crew’s problem-solving ability. At last year’s IWS, Beard reported that a single spaceflight stressor (elevated CO2) could undermine the crew’s ability to independently respond to emergencies. Concept of Operations (ConOps) provide a common view of future system functions to all stakeholders. For the current project, a ConOps was developed that describes the operational processes, practices and capabilities needed by a crew of astronauts on deep space missions to autonomously respond to anticipated and unanticipated anomalies. It is crucial to recognize that, as of August 2018 existing technologies are unable to effectively support crew anomaly response to unanticipated events. “Intelligent technology” has not reached a maturity level that permits generalizing a solution to novel situations. For example, to train intelligent technology requires volumes of data that do not exist. The complexities involved in a manned mission to Mars cannot be compared to sending rovers to Mars using scripted software. This ConOps proposes a Crew Performance Support System (CPSS) that will push NASA and its industry partners toward what will be required for a safe and successful manned mission to Mars. Anomaly resolution during a deep space mission will take place within a dynamic, or changing, context. The figure to the left shows five broad contextual variables: the organizational culture, mission context, system characteristics, team characteristics and individual characteristics. The yellow arrow indicates that spaceflight and task-related stressors can affect system, team and individual crewmember characteristics and therefore anomaly response potential. The figure depicts a protective umbrella of Human-System Integration (HSI) principles that should be instituted during CPSS development including a balanced workload, shared situation awareness and building an appropriate level of trust in the automation. The figure also depicts two interrelated and cooperative components, an HSI Data System and other Enabling Capabilities will be required to support crew anomaly response and Earth-Support situation awareness. As we journey from ISS to Gateway to Mars, multiple, simultaneous and integrated research and development efforts (i.e., support systems co-evolution) must be implemented to meet the problem-solving challenges a self-reliant crew will face on a Mars’ mission. The crossovers between the capabilities are just as important as the discrete capabilities themselves. As the capabilities mature, the lines between the support subdomains will blur and an integrated system will emerge. The ConOps summarizes current knowledge about how highly trained people solve anomalies in safety- and time-critical situations, describes a group of capabilities that could help to reduce the extant risk and documents requirements levied on additional systems that provides critical inputs to the CPSS. Scenarios are used to promote a shared understanding of processes, practices and technological goals needed for safe and productive manned missions beyond LEO.

HSIA risk↗
NASA NTRS2011

Telemedicine in Space Flight - Summary of a NASA Workshop

The Exploration Medical Capability Element of the Human Research Program at NASA Johnson Space Center hosted the Telemedicine Workshop in January 2011 to discuss the medical operational concept for a crewed mission to a near-Earth asteroid (NEA) and to identify areas for future work and collaboration. With the increased likelihood of a medical incident on a long duration exploration mission to a near-Earth asteroid, as well as the fact that there will likely be limited medical capabilities and resources available to diagnose and treat medical conditions, it is anticipated that a more structured use of telemedicine will become highly desirable. The workshop was convened to solicit expert opinion on current telemedicine practices and on medical care in remote environments. Workshop Objectives: The workshop brought together leaders in telemedicine and remote medicine from The University of Texas Medical Branch, Henry Ford Hospital, Ontario Telemedicine Network, U.S. Army Institute of Surgical Research, University of Miami, American Telemedicine Association, Doctors Without Borders, and the Pan American Health Organization. The primary objectives of the workshop were to document the medical operations concept for a crewed mission to a NEA, to determine gaps between current capabilities and the capabilities outlined in the operations concept, to identify research required to close these gaps, and to discuss potential collaborations with external-to-NASA organizations with similar challenges. Summary of Discussions and Conclusions: The discussions held during the workshop and the conclusions reached by the workshop participants were grouped into seven categories: Crew Medical Officers, Patient Area in Spacecraft, Training, Electronic Medical Records, Intelligent Care Systems, Consultation Protocols, Prophylactic Surgical Procedures, and Data Prioritization. The key points discussed under each category will be presented.

Barsten, K. N.↗
NASA NTRS1996

Spaceport Florida Authority: Business Plan

The Spaceport Florida Authority (SFA) was established under Florida Statute by the Governor and Legislature to assist the development of our nation's space transportation industry and to generate new space-related jobs, investment and opportunities statewide. Included in the Authorities' business plan is the statement of work and list of team members involved in creating the report, SFA's current operating concept, market analysis, assessment of accomplishments, a sample operating concept and a "roadmap to success".

Source record↗
NASA NTRS2013

Precision Departure Release Capability (PDRC) Concept of Operations

After takeoff, aircraft must merge into en route (Center) airspace traffic flows which may be subject to constraints that create localized demandcapacity imbalances. When demand exceeds capacity Traffic Management Coordinators (TMCs) often use tactical departure scheduling to manage the flow of departures into the constrained Center traffic flow. Tactical departure scheduling usually involves use of a Call for Release (CFR) procedure wherein the Tower must call the Center TMC to coordinate a release time prior to allowing the flight to depart. In present-day operations release times are computed by the Center Traffic Management Advisor (TMA) decision support tool based upon manual estimates of aircraft ready time verbally communicated from the Tower to the Center. The TMA-computed release is verbally communicated from the Center back to the Tower where it is relayed to the Local controller as a release window that is typically three minutes wide. The Local controller will manage the departure to meet the coordinated release time window. Manual ready time prediction and verbal release time coordination are labor intensive and prone to inaccuracy. Also, use of release time windows adds uncertainty to the tactical departure process. Analysis of more than one million flights from January 2011 indicates that a significant number of tactically scheduled aircraft missed their en route slot due to ready time prediction uncertainty. Uncertainty in ready time estimates may result in missed opportunities to merge into constrained en route flows and lead to lost throughput. Next Generation Air Transportation System (NextGen) plans call for development of Tower automation systems capable of computing surface trajectory-based ready time estimates. NASA has developed the Precision Departure Release Capability (PDRC) concept that uses this technology to improve tactical departure scheduling by automatically communicating surface trajectory-based ready time predictions to the Center scheduling tool. The PDRC concept also incorporates earlier NASA and FAA research into automation-assisted CFR coordination. The PDRC concept helps reduce uncertainty by automatically communicating coordinated release times with seconds-level precision enabling TMCs to work with target times rather than windows. NASA has developed a PDRC prototype system that integrates the Center's TMA system with a research prototype Tower decision support tool. A two-phase field evaluation was conducted at NASA's North Texas Research Station (NTX) in DallasFort Worth. The field evaluation validated the PDRC concept and demonstrated reduced release time uncertainty while being used for tactical departure scheduling of more than 230 operational flights over 29 weeks of operations. This paper presents the Concept of Operations. Companion papers include the Final Report and a Technology Description. ? SUBJECT:

tactical departure scheduling↗