SEARCH · Search NASA

Results for “Operations coordination plan”

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 37 records · Page 2

All sources NASA NTRS DOE OSTI

NASA NTRSDate not supplied

NASA’s Simulation Activities for Evaluating UAM Concept of Operations

NASA’s vision for Advanced Air Mobility (AAM) is to help emerging aviation markets to safely develop an air transportation system that moves people and cargo between places previously not served or underserved by aviation using revolutionary new aircraft types. Urban Air Mobility (UAM), the concept of expanding transportation networks by serving short flights to transport people and goods around metropolitan areas, is part of a larger paradigm shift toward AAM, in which new technologies and business models are enabling transformational applications of aviation. In NASA’s Concept of Operations for UAM, Providers of Services for UAM (PSU) play a key role to enable safe and efficient UAM operations by sharing operational data among UAM operators. PSUs provide a pre-departure strategic conflict management service that establishes operational plans for new flights and coordinates them with all relevant operations in shared airspace. The strategic conflict management aims to minimize the need for tactical separation provision, while considering anticipated traffic demand, vertiport capacity and availability, forecasted weather, and airspace restrictions. NASA is currently preparing a new lab evaluation activity with aviation industry partners, called the X4 simulation, to demonstrate their airspace services and capabilities and test new information exchange requirements for UAM operations. This simulation activity will support NASA’s National Campaign (NC) flight tests which are planned over the next several years to guide the collective community and stakeholders through a series of scenario-based test activities that involve vehicles and airspace management services operating in a live test environment. This presentation will provide an overview of the X4 simulation, including objectives, scenarios, assumptions, system architecture, and test schedule. The X4 simulation will evaluate the interconnectivity and operational intent sharing between PSUs for multiple operators, as well as the performance of strategic conflict management.

Urban Air Mobility, Simulation, Advanced Air Mobil↗

NASA NTRS2004

Flying the Earth Observing Constellations

Prior to the launch of the Earth Observing System (EOS) Terra and Landsat-7 satellites in 1999, the Project Scientists for the two missions and the Earth Science Data and Information System (ESDIS) Project at the Goddard Space Flight Center signed an inter-project agreement document describing their plan to fly in loose formation, approximately 20 minutes within each other. In November 2000, a technology demonstration satellite, Earth Observer-1 (EO-1), was launched into the same orbit as that of Landsat-7 and Terra, with a goal of flying within a minute from Landsat-7. The SAC-C satellite, developed and operated by the government of Argentina, was launched along with EO-1, with a goal of flying near both Terra and Landsat-7. This formation enables the scientists to make use of the scientific synergy among the instruments on the different spacecraft. This group of satellites constitutes the morning constellation, which is led by the Landsat-7, which has a mean local time (MLT) at 10:00 a.m. In May 2002, the EOS Aqua satellite was launched into an orbit with an altitude of 705 km. and a 1:30 p.m. MLT. Two smaller satellites, CALIPSO (a joint U.S./French mission), and CloudSat (a joint NASA/Colorado State University/Air Force mission), plan to fly in tight formation, within 15 seconds of each other. In addition, CALIPSO and CloudSat also plan to be within 30 to 60 seconds of the Aqua satellite. A third satellite, PARASOL, managed by the French Space Agency, CNES, will be placed within a minute of the CALIPSO satellite. In 2004, the Aura satellite will be launched and phased in relation to the Aqua satellite, such that the instruments on Aura will be able to view the same mass of air no later than 8 minutes after the instruments on Aqua have observed it. Representatives from each mission are currently documenting a plan on how they will coordinate on-orbit operations. Why are all these satellites planning to fly as a constellation? The answer is that as a constellation. the scientists will be able to acquire science data not only from their specific instruments on a single satellite, but science data from the other satellites which will have been taken at approximately the same time, thus resulting in coordinated science observation data. This leads to better quality science. This paper describes how the mission design has been driven by the science requirements. The morning and the afternoon constellations present operational challenges, which had not previously been encountered. Operations planning must address not only how the satellites of each constellation operate safely together, but also, how the two constellations fly on the same orbits without interfering with each other as they downlink data to their respective ground stations. This paper describes the operations experience gained from the morning constellation and the planning for the afternoon constellation.

Kelly, Angelita C.↗

NASA NTRS2002

Lessons Learned In Developing Multiple Distributed Planning Systems for the International Space Station

The planning processes for the International Space Station (ISS) Program are quite complex. Detailed mission planning for ISS on-orbit operations is a distributed function. Pieces of the on-orbit plan are developed by multiple planning organizations, located around the world, based on their respective expertise and responsibilities. The "pieces" are then integrated to yield the final detailed plan that will be executed onboard the ISS. Previous space programs have not distributed the planning and scheduling functions to this extent. Major ISS planning organizations are currently located in the United States (at both the NASA Johnson Space Center (JSC) and NASA Marshall Space Flight Center (MSFC)), in Russia, in Europe, and in Japan. Software systems have been developed by each of these planning organizations to support their assigned planning and scheduling functions. Although there is some cooperative development and sharing of key software components, each planning system has been tailored to meet the unique requirements and operational environment of the facility in which it operates. However, all the systems must operate in a coordinated fashion in order to effectively and efficiently produce a single integrated plan of ISS operations, in accordance with the established planning processes. This paper addresses lessons learned during the development of these multiple distributed planning systems, from the perspective of the developer of one of the software systems. The lessons focus on the coordination required to allow the multiple systems to operate together, rather than on the problems associated with the development of any particular system. Included in the paper is a discussion of typical problems faced during the development and coordination process, such as incompatible development schedules, difficulties in defining system interfaces, technical coordination and funding for shared tools, continually evolving planning concepts/requirements, programmatic and budget issues, and external influences. Techniques that mitigated some of these problems will also be addressed, along with recommendations for any future programs involving the development of multiple planning and scheduling systems. Many of these lessons learned are not unique to the area of planning and scheduling systems, so may be applied to other distributed ground systems that must operate in concert to successfully support space mission operations.

Maxwell, Theresa G.↗

NASA NTRS2002

Lessons Learned in Developing Multiple Distributed Planning Systems for the International Space Station

The planning processes for the International Space Station (ISS) Program are quite complex. Detailed mission planning for ISS on-orbit operations is a distributed function. Pieces of the on-orbit plan are developed by multiple planning organizations, located around the world, based on their respective expertise and responsibilities. The pieces are then integrated to yield the final detailed plan that will be executed onboard the ISS. Previous space programs have not distributed the planning and scheduling functions to this extent. Major ISS planning organizations are currently located in the United States (at both the NASA Johnson Space Center (JSC) and NASA Marshall Space Flight Center (MSFC)), in Russia, in Europe, and in Japan. Software systems have been developed by each of these planning organizations to support their assigned planning and scheduling functions. Although there is some cooperative development and sharing of key software components, each planning system has been tailored to meet the unique requirements and operational environment of the facility in which it operates. However, all the systems must operate in a coordinated fashion in order to effectively and efficiently produce a single integrated plan of ISS operations, in accordance with the established planning processes. This paper addresses lessons learned during the development of these multiple distributed planning systems, from the perspective of the developer of one of the software systems. The lessons focus on the coordination required to allow the multiple systems to operate together, rather than on the problems associated with the development of any particular system. Included in the paper is a discussion of typical problems faced during the development and coordination process, such as incompatible development schedules, difficulties in defining system interfaces, technical coordination and funding for shared tools, continually evolving planning concepts/requirements, programmatic and budget issues, and external influences. Techniques that mitigated some of these problems will also be addressed, along with recommendations for any future programs involving the development of multiple planning and scheduling systems. Many of these lessons learned are not unique to the area of planning and scheduling systems, so may be applied to other distributed ground systems that must operate in concert to successfully support space mission operations.

Maxwell, Theresa G.↗

NASA NTRS2016

NEEMO 20: Science Training, Operations, and Tool Development

The 20th mission of the National Aeronautics and Space Administration (NASA) Extreme Environment Mission Operations (NEEMO) was a highly integrated evaluation of operational protocols and tools designed to enable future exploration beyond low-Earth orbit. NEEMO 20 was conducted from the Aquarius habitat off the coast of Key Largo, FL in July 2015. The habitat and its surroundings provide a convincing analog for space exploration. A crew of six (comprised of astronauts, engineers, and habitat technicians) lived and worked in and around the unique underwater laboratory over a mission duration of 14-days. Incorporated into NEEMO 20 was a diverse Science Team (ST) comprised of geoscientists from the Astromaterials Research and Exploration Science (ARES/XI) Division from the Johnson Space Center (JSC), as well as marine scientists from the Department of Biological Sciences at Florida International University (FIU). This team trained the crew on the science to be conducted, defined sampling techniques and operational procedures, and planned and coordinated the science focused Extra Vehicular Activities (EVAs). The primary science objectives of NEEMO 20 was to study planetary sampling techniques and tools in partial gravity environments under realistic mission communication time delays and operational pressures. To facilitate these objectives two types of science sites were employed 1) geoscience sites with available rocks and regolith for testing sampling procedures and tools and, 2) marine science sites dedicated to specific research focused on assessing the photosynthetic capability of corals and their genetic connectivity between deep and shallow reefs. These marine sites and associated research objectives included deployment of handheld instrumentation, context descriptions, imaging, and sampling; thus acted as a suitable proxy for planetary surface exploration activities. This abstract briefly summarizes the scientific training, scientific operations, and tool development conducted during NEEMO 20 with an emphasis on the primary lessons learned.

Graff, T.↗

NASA NTRS1994

The SILEX experiment system operations

The European Space Agency is going to conduct an inter orbit link experiment which will connect a low Earth orbiting satellite and a Geostationary satellite via optical terminals. This experiment has been called SILEX (Semiconductor Inter satellite Link EXperiment). Two payloads will be built. One called PASTEL (PASsager de TELecommunication) will be embarked on the French Earth observation satellite SPOT4. The future European experimental data relay satellite ARTEMIS (Advanced Relay and TEchnology MISsion) will carry the OPALE terminal (Optical PAyload Experiment). The principal characteristic of the mission is a 50 Megabits flow of data transmitted via the optical satellite link. The relay satellite will route the data via its feeder link thus permitting a real time reception in the European region of images taken by the observation satellite. The PASTEL terminal has been designed to cover up to 9 communication sessions per day with an average of 5. The number of daily contact opportunities with the low earth orbiting satellite will be increased and the duration will be much longer than the traditional passes over a ground station. The terminals have an autonomy of 24 hours with respect to ground control. Each terminal will contain its own orbit model and that of its counter terminal for orbit prediction and for precise computation of pointing direction. Due to the very narrow field of view of the communication laser beam, the orbit propagation calculation needs to be done with a very high accuracy. The European Space Agency is responsible for the operation of both terminals. A PASTEL Mission Control System (PMCS) is being developed to control the PASTEL terminal on board SPOT4. The PMCS will interface with the SPOT4 Control Centre for the execution of the PASTEL operations. The PMCS will also interface with the ARTEMIS Mission Control System for the planning and the coordination of the operation. It is the first time that laser technology will be used to support inter-satellite links in Europe. Due to the complexity and experimental character of this new optical technology, the SILEX experiment control facilities will be designed to allow as much operational flexibility as possible.

Demelenne, B.↗

NASA NTRS2008

Targeting and Localization for Mars Rover Operations

A design and a partially developed application framework were presented for improving localization and targeting for surface spacecraft. The program has value for the Mars Science Laboratory mission, and has been delivered to support the Mars Exploration Rovers as part of the latest version of the Maestro science planning tool. It also has applications for future missions involving either surface-based or low-altitude atmospheric robotic vehicles. The targeting and localization solutions solve the problem of how to integrate localization estimate updates into operational planning tools, operational data product generalizations, and flight software by adding expanded flexibility to flight software, the operations data product pipeline, and operations planning tools based on coordinate frame updates during a planning cycle.

Powell, Mark W.↗

NASA NTRSDate not supplied

NASA Research to Expand UAS Operations for Disaster Response

Natural disasters can result in the loss of life and cost governments and private industry billions to recover each year. Over the past decade the rate and severity of natural disasters such as wildfires and hurricanes have resulted in increasingly negative impacts to communities, public health, natural ecosystems, and the economy. To help reduce these impacts, NASA’s Aeronautics Research Mission Directorate is working to advance technologies and enable the safe and efficient inclusion of novel aviation applications to better assist in disaster response. To execute on these efforts, NASA’s Advanced Capabilities for Emergency Response Operations (ACERO) and System-Wide Safety (SWS) projects have developed coordinated strategic research plans focused on aviation operations for disaster response. The ACERO project will be a multi-year effort that focuses on enabling the use of uncrewed aircraft systems (UAS) to improve firefighter safety and efficiency and enable the use of UAS to conduct new missions such as logistics and aerial suppression. The ACERO project will demonstrate technologies that support the Second Shift concept, enabling UAS and ground technologies to support aerial suppression in degraded visual conditions (e.g., heavy smoke, nighttime). The SWS project will be a multi-year effort that focuses on addressing the key safety barriers that are preventing the authorization of UAS operations in a variety of increasingly complex disaster response applications: post-hurricane response, medical courier, and urban disaster response. The SWS project will demonstrate an In-Time Aviation Safety Management System (IASMS) designed to effectively monitor, assess, and mitigate safety risks associated with hazards to UAS operations for disaster response. This paper will provide a deeper insight into NASA’s research and development plans and discuss how solutions developed in partnership with industry stakeholders and federal agencies will improve disaster response across the globe.

disaster response↗

DOE OSTI2024

Interregional Transmission Operational Coordination

This presentation will discuss challenges and opportunities on interregional coordination in the areas of interchange transaction, congestion management, reserve sharing and deliverability across multi-stage operational processes. It will then provide an overview of the interregional transmission operational coordination (IRTOC) project that currently focuses on congestion management, including Inter-regional transmission coordination in real time operations and operational planning, HVDC optimization (intra- and interregional), ancillary service deliverability (intra- and interregional). In addition, it will discuss the Sienna-Decomposition tool development to systematically study interregional coordination methods.

congestion management↗

NASA NTRS2017

Flight Deck Surface Trajectory-Based Operations

Surface Trajectory-Based Operations (STBO) is a future concept for surface operations where time requirements are incorporated into taxi operations to support surface planning and coordination. Pilot-in-the-loop flight deck simulations have been conducted to study flight deck displays algorithms to aid pilots in complying with the time requirements of time-based taxi operations (i.e., at discrete locations in 3 12 D operations or at all points along the route in 4DT operations). The results of these studies (conformance, time-of-arrival error, eye-tracking data, and safety ratings) are presented. Flight deck simulation work done in collaboration with DLR is described. Flight deck research issues in future auto-taxi operations are also introduced.

flight deck↗

NASA NTRS1982

NASA deep space network operations planning and preparation

The responsibilities and structural organization of the Operations Planning Group of NASA Deep Space Network (DSN) Operations are outlined. The Operations Planning group establishes an early interface with a user's planning organization to educate the user on DSN capabilities and limitations for deep space tracking support. A team of one or two individuals works through all phases of the spacecraft launch and also provides planning and preparation for specific events such as planetary encounters. Coordinating interface is also provided for nonflight projects such as radio astronomy and VLBI experiments. The group is divided into a Long Range Support Planning element and a Near Term Operations Coordination element.

Jensen, W. N.↗

NASA NTRSDate not supplied

The Contribution of Pilots to Resilience in Normal Operations. Part II: A closer look at briefings: Anticipation and Monitoring Also Known as Planning and Coordination

Much of our knowledge about human performance in flight safety has come from the analysis of undesired events, whether accidents, incidents, or crew behaviors identified via flight exceedance monitoring or observational techniques. In recent years, there has been an acknowledgement that operational personnel are not merely sources of “human error”, but also make a unique human contribution to safe outcomes. In a few celebrated cases, this takes the form of “heroic saves”, but on many more occasions, operational personnel contribute to safety through everyday, often-unnoticed actions that turn potentially hazardous situations into non-events. An emerging approach to safety, frequently referred to as “Safety II,” proposes that the positive human contribution is an important and largely untapped source of safety information. Some airlines have successfully trained observers to identify and record the positive behaviors exhibited by the crew over the course of a flight. In other cases, flight crew are interviewed about good practices or positive behaviors. However, each of these methods are relatively limited in scale and resource intensive. A survey could provide a relatively low-cost approach to systematically gather this information on a larger scale. The primary purpose of the research was to develop and assess a surveys methodology for assessing crews' activities in normal flights and the operational perturbations encountered during normal operations. We hope that such a survey could be both a research tool as well as a safety management aid for the aviation industry. We collected responses concerning revenue flights from two groups of airline pilots (N = 25 & N= 65). The results indicated that relatively few flights proceeded exactly as in the original flight plan. Pilots routinely anticipated and adapted to changing circumstances. We will review the challenges encountered in developing the survey and summarize preliminary findings from two administrations of the survey to airline pilots.

human contribution safety↗

NASA NTRS2008

Automated and Adaptive Mission Planning for Orbital Express

The Orbital Express space mission was a Defense Advanced Research Projects Agency (DARPA) lead demonstration of on-orbit satellite servicing scenarios, autonomous rendezvous, fluid transfers of hydrazine propellant, and robotic arm transfers of Orbital Replacement Unit (ORU) components. Boeing's Autonomous Space Transport Robotic Operations (ASTRO) vehicle provided the servicing to the Ball Aerospace's Next Generation Serviceable Satellite (NextSat) client. For communication opportunities, operations used the high-bandwidth ground-based Air Force Satellite Control Network (AFSCN) along with the relatively low-bandwidth GEO-Synchronous space-borne Tracking and Data Relay Satellite System (TDRSS) network. Mission operations were conducted out of the RDT&E Support Complex (RSC) at the Kirtland Air Force Base in New Mexico. All mission objectives were met successfully: The first of several autonomous rendezvous was demonstrated on May 5, 2007; autonomous free-flyer capture was demonstrated on June 22, 2007; the fluid and ORU transfers throughout the mission were successful. Planning operations for the mission were conducted by a team of personnel including Flight Directors, who were responsible for verifying the steps and contacts within the procedures, the Rendezvous Planners who would compute the locations and visibilities of the spacecraft, the Scenario Resource Planners (SRPs), who were concerned with assignment of communications windows, monitoring of resources, and sending commands to the ASTRO spacecraft, and the Mission planners who would interface with the real-time operations environment, process planning products and coordinate activities with the SRP. The SRP position was staffed by JPL personnel who used the Automated Scheduling and Planning ENvironment (ASPEN) to model and enforce mission and satellite constraints. The lifecycle of a plan began three weeks outside its execution on-board. During the planning timeframe, many aspects could change the plan, causing the need for re-planning. These variable factors, ranging from shifting contact times to ground-station closures and required maintenance times, are discussed along with the flexibility of the ASPEN tool to accommodate changes to procedures and the daily or long-range plan, which contributed to the success of the mission. This paper will present an introduction to ASPEN, a more in-depth discussion on its use on the Orbital Express mission, and other relative work. A description of ground operations after the SRP deliveries were made is included, and we briefly discuss lessons learned from the planning perspective and future work.

scheduling↗

NASA NTRS1993

Navigation of space VLBI missions: Radioastron and VSOP

In the mid-1990s, Russian and Japanese space agencies will each place into highly elliptic earth orbit a radio telescope consisting of a large antenna and radio astronomy receivers. Very long baseline interferometry (VLBI) techniques will be used to obtain high resolution images of radio sources observed by the space and ground based antennas. Stringent navigation accuracy requirements are imposed on the space VLBI missions by the need to transfer an ultra-stable ground reference frequency standard to the spacecraft and by the demands of the VLBI correlation process. Orbit determination for the mission will be the joint responsibility of navigation centers in the U.S., Russia, and Japan with orbit estimates based on combining tracking data from NASA, Russian, and Japanese sites. This paper describes the operational plans, the inter-agency coordination, and data exchange between the navigation centers required for space VLBI navigation.

Ellis, Jordan↗

NASA NTRSDate not supplied

Firmware Architecture of the ARMADAS Bolting Robot

The Automated Reconfigurable Mission Adaptive Digital Assembly Systems (ARMADAS) project, under development at NASA Ames Research Center, has demonstrated on-ground autonomous robotic assembly of extensive digital structures, and it is now moving forward towards in-space demonstration. The ARMADAS system comprises of the operation software, the operation user interface (opsUI), and a swarm of robots. The robotic system consists of a multitude of collaborative agents specifically designed to transport, place and bolt the building blocks, called voxels (volumetric pixels). This paper focuses on the bolting robot, referred to as Mobile Metamaterial Internal Co-Integrator (MMIC-I). MMIC-I is a battery-powered crawling robot. It navigates the structure through extension, contraction and gripping. Two distinct controller boards operate the robot's two symmetric modules, referred to as module A and B. Board A is the master board: it coordinates motion planning and motion primitives execution, hosts the WiFi client, performs periodic self-assessment and system idle check and triggers faults if anomalies are detected. Board B periodically sends a heartbeat to board A, through a wired communication channel that uses the Serial protocol. Additionally, board A's WiFi client receives heartbeat packet requests or motion/bolting commands from a dedicated server board, and acknowledges reception sending back a response heartbeat packet containing information about the overall robot status, e. g. electrical current and voltage values, target and actual angles, operating mode, fault status. Whenever a motion command is sent, the motion planning section of the firmware determines the current robot configuration, using Inertial Measurement Unit readings and the motors Pulse Width Modulation values. Afterwards, it calculates the list of primitives needed to reach the target state, and controls their execution in the proper order. MMIC-I can receive and execute motion and bolting commands only when it is in operational mode. MMIC-I has three operating modes: standby, operational and safed. Standby mode is automatically entered upon startup. While in standby mode, all motors are powered off, and the only accepted commands are the ones relative to a change of mode and heartbeat packet request. Fault detection causes the robot to automatically enter safed or standby mode. Whenever the detected fault occurs within a motion and requires immediate intervention, e. g. an over-current situation, the robot enters safed mode. Safed mode powers off all motors except for the locomotion module, thus preventing the robot from collapsing. Conversely, when the detected fault doesn't require immediate intervention (low battery warning, for instance), the robot enters standby mode after completing the ongoing motion. This paper provides a detailed discussion of MMIC-I's firmware architecture. It accurately describes the implementation approach for each module: sensor data reading, motor control and actuation, WiFi server-client communication, intra-boards Serial communication, operating modes and autonomous fault detection, motion planning, coordination and execution, etc. Moreover, in support of the software description, this paper includes a thorough characterization of MMIC-I's hardware and avionics.

In-space assembly↗

DOE OSTI2025

Cyber Conservative Operations

In an era of increasingly sophisticated and pervasive cyber threats, robust cyber resilience strategies are more critical than ever. This paper introduces the concept of Cyber Conservative Operations, a proactive approach designed to assist critical infrastructure owners and operators in managing risk and maintaining resilience in the face of imminent, yet not occurring, cyber events. By leveraging the principles of Cyber-Informed Engineering (CIE) and the energy sector’s practice of conservative operations, Cyber Conservative Operations offer a framework for planning and executing coordinated active defense and resilience-oriented actions ahead of cyber events. This approach aims to minimize the consequences of digitally-enabled hazards and ensure swift recovery from anticipated cyber threats. Cyber Conservative Operations enhance the ability of owners and operators to execute pre-planned defense and resilience actions, thereby reducing the impact of digitally-enabled hazards. These operations are crucial for addressing impacts that cannot be precisely quantified or forecasted and for preparing organizations for rapid recovery from imminent digital threats. The paper begins with a discussion of conservative operations as applied to the bulk power system (BPS), a current mechanism allowing BPS entities to enact defensive operating plans to mitigate impending grid unreliability. Building on this model, we present a concept for implementing cyber conservative operations at asset owner facilities. The paper concludes with two case studies of cyber conservative operations drawn from high-profile cyber events, illustrating the practical application and benefits of this proactive approach.

42 - ENGINEERING↗

DOE OSTI2024

A Case Study in NREL DERMS Asset Management Implementation

The National Renewable Energy Laboratory (NREL) and Smarter Grid Solutions (SGS) plan to present a case study on their implementation of SGS' Strata Grid Distributed Energy Resource Management System at NREL's Energy Systems Integration Facility (ESIF). The ESIF is one of the nation's premier energy systems integration laboratory facilities focused on development and deployment of clean energy technologies and resilient delivery systems. NREL looked for a DERMS to install at the ESIF that is capable of replicating real world scenarios to control and monitor distributed devices from small residential scale to the grid substation level. The DERMS system demonstrates the use cases of beneficial operation and coordination of modern grid devices, leverage DERs for improved grid planning and operation, demand-side management and customer engagement through bidirectional communication with utilities and energy market operations. The presentation will cover the delivery strategy of NREL and SGS, how the use cases help NREL's research, and NREL and SGS plan to expand the system and use cases.

ARIES↗

NASA NTRS2015

Identifying Key Issues and Potential Solutions for Integrated Arrival, Departure, Surface Operations by Surveying Stakeholder Preferences

NASA's Aeronautics Research Mission Directorate (ARMD) collaborates with the FAA and industry to provide concepts and technologies that enhance the transition to the next-generation air-traffic management system (NextGen). To facilitate this collaboration, ARMD has a series of Airspace Technology Demonstration (ATD) sub-projects that develop, demonstrate, and transitions NASA technologies and concepts for implementation in the National Airspace System (NAS). The second of these sub-projects, ATD-2, is focused on the potential benefits to NAS stakeholders of integrated arrival, departure, surface (IADS) operations. To determine the project objectives and assess the benefits of a potential solution, NASA surveyed NAS stakeholders to understand the existing issues in arrival, departure, and surface operations, and the perceived benefits of better integrating these operations. NASA surveyed a broad cross-section of stakeholders representing the airlines, airports, air-navigation service providers, and industry providers of NAS tools. The survey indicated that improving the predictability of flight times (schedules) could improve efficiency in arrival, departure, and surface operations. Stakeholders also mentioned the need for better strategic and tactical information on traffic constraints as well as better information sharing and a coupled collaborative planning process that allows stakeholders to coordinate IADS operations. To assess the impact of a potential solution, NASA sketched an initial departure scheduling concept and assessed its viability by surveying a select group of stakeholders for a second time. The objective of the departure scheduler was to enable flights to move continuously from gate to cruise with minimal interruption in a busy metroplex airspace environment using strategic and tactical scheduling enhanced by collaborative planning between airlines and service providers. The stakeholders agreed that this departure concept could improve schedule predictability and suggested several key attributes that were necessary to make the concept successful. The goals and objectives of the planned ATD-2 sub-project will incorporate the results of this stakeholder feedback.

integrated arrival/departure/surface operations↗