Search NASA⌕ Search

SEARCH · Search NASA

Results for “conflict management”

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 91 records · Page 5

Impact of Conflict Avoidance Responsibility Allocation on Pilot Workload in a Distributed Air Traffic Management System

Pilot workload was examined during simulated flights requiring flight deck-based merging and spacing while avoiding weather. Pilots used flight deck tools to avoid convective weather and space behind a lead aircraft during an arrival into Louisville International airport. Three conflict avoidance management concepts were studied: pilot, controller or automation primarily responsible. A modified Air Traffic Workload Input Technique (ATWIT) metric showed highest workload during the approach phase of flight and lowest during the en-route phase of flight (before deviating for weather). In general, the modified ATWIT was shown to be a valid and reliable workload measure, providing more detailed information than post-run subjective workload metrics. The trend across multiple workload metrics revealed lowest workload when pilots had both conflict alerting and responsibility of the three concepts, while all objective and subjective measures showed highest workload when pilots had no conflict alerting or responsibility. This suggests that pilot workload was not tied primarily to responsibility for resolving conflicts, but to gaining and/or maintaining situation awareness when conflict alerting is unavailable.

Ligda, Sarah V.↗

Integration of Automated Systems Test Campaign NC-IAS

NASA’s 2022 strategic plan included the goal to catalyze economic growth and drive innovation in the aviation industry, and to address challenges in air transportation and airspace management within the National Airspace System (NAS). The Aeronautics Research Mission Directorate (ARMD) specifically was tasked with leading aviation innovation to enable safe and sustainable air transportation through revolutionary vehicle advances and efficient flight operations. As a part of meeting these objectives and advancing air mobility concepts, NASA initiated the National Campaign (NC) in the Advanced Air Mobility (AAM) Project within the Airspace Operations and Safety Program (AOSP). The NC was designed to support operational demonstrations with industry as well as the research and development needed to support NASA-led research flight demonstrations. Within NC, the Integration of Automated Systems (IAS), an NC activity, tested and evaluated flight deck automation and airspace operations management functions needed to enable Urban Air Mobility (UAM) operations. This was accomplished through a partnership with Sikorsky Aircraft (specifically Sikorsky Innovations), a Lockheed Martin company, and DARPA (Defense Advanced Research Projects Agency), by leveraging two automation-enabled helicopters equipped with unique capabilities that enabled NASA to develop and test two-ship conflict encounters to demonstrate flight path management and hazard avoidance technologies. The enabler in this testing was NASA-developed “Middleware” (MW) software (also known as Expandable Variable Autonomy Architecture, or EVAA), which among other things allowed multiple algorithms to be incorporated into one software build that was hosted on the dissimilar-type Sikorsky helicopters. The IAS test campaign period of performance was from March 2022 through October 2023 and was structured as a phased, or spiral, approach that ultimately led to the first-ever demonstration of two-ship UAM/AAM operations designed to safely choreograph specific conflict encounters and mission scenarios to test the research algorithms for strategic and tactical aircraft deconfliction. Lessons learned are included in the body of the report. Data collected will be used to inform FAA and industry standards groups on the increasingly automated systems needed for future AAM operations. The test encounters developed for these flight tests were proven to be highly predictable, repeatable, and safely exercised flight path planning and Detect and Avoid (DAA) algorithms. These same test encounters should be leveraged by future flight test campaigns to verify that operational safety is not compromised as the AAM architecture matures. Next steps include repeating similar encounters using unmanned aircraft carrying DAA sensors in the National Airspace.

AAM↗

The Airspace Concepts Evaluation System Architecture and System Plant

The Airspace Concepts Evaluation System is a simulation of the National Airspace System. It includes models of flights, airports, airspaces, air traffic controls, traffic flow managements, and airline operation centers operating throughout the United States. It is used to predict system delays in response to future capacity and demand scenarios and perform benefits assessments of current and future airspace technologies and operational concepts. Facilitation of these studies requires that the simulation architecture supports plug and play of different air traffic control, traffic flow management, and airline operation center models and multi-fidelity modeling of flights, airports, and airspaces. The simulation is divided into two parts that are named, borrowing from classical control theory terminology, control and plant. The control consists of air traffic control, traffic flow management, and airline operation center models, and the plant consists of flight, airport, and airspace models. The plant can run open loop, in the absence of the control. However, undesired affects, such as conflicts and over congestions in the airspaces and airports, can occur. Different controls are applied, "plug and played", to the plant. A particular control is evaluated by analyzing how well it managed conflicts and congestions. Furthermore, the terminal area plants consist of models of airports and terminal airspaces. Each model consists of a set of nodes and links which are connected by the user to form a network. Nodes model runways, fixes, taxi intersections, gates, and/or other points of interest, and links model taxiways, departure paths, and arrival paths. Metering, flow distribution, and sequencing functions can be applied at nodes. Different fidelity model of how a flight transits are can be used by links. The fidelity of the model can be adjusted by the user by either changing the complexity of the node/link network-or the way that the link models how the flights transit from one node to the other.

Windhorst, Robert↗

Scenario Complexity for Unmanned Aircraft System Traffic

This work introduces an approach to estimate the complexity of a low-altitude air traffic scenario involving multiple UASs using mathematical programming. Given a set of multi-point UAS flight trajectories, vehicle dynamics, and a conflict resolution algorithm, an abstract model is developed such that it can be solved quickly using a mathematical programming optimization software without running high-fidelity simulations that can be computationally expensive and may not suit real-time apA quick and accurate assessment of complexity for a given traffic scenario can help plan and schedule flights to alleviate traffic bottleneck and mitigate operation risks, especially for unmanned aerial system traffic management where high traffic density or complexity is expected. This work introduces a traffic scenario complexity metric that was constructed based on the number of potential conflicts weighted by the conflict resolution cost associated. The cost associated with a conflict is calculated based on the corresponding conflict resolution maneuvers. To obtain the conflict resolution maneuvers, a MILP-based optimization was formulated with the vehicle model and conflict management parameters incorporated. To evaluate the complexity metrics, an approach of using measurements from high-fidelity simulations was proposed. The scenario complexity measurements for 920 random-generated scenarios were obtained through high-fidelity simulations and treated as the ground truth. Two statistics methods: Pearson and Alternative Conditional Expectations were applied for analysis. The results showed that the number of flights has low correlation with the scenario complexity according to the correlation coefficients calculated by both methods. The Alternative Conditional Expectations method shows that the proposed scenario complexity metric has better correlation with the ground truth than the number of potential conflicts.plications. In the abstract model, each vehicle is represented by a time-varied vector associated with position, speed, and heading information. The total extra distance that aircraft need to divert from their original routes to avoid collisions is computed and used to setup a quadratic programming formula. The metrics including the number of conflicts and extra distances travelled by all vehicles are then utilized to estimate the complexity of a given UAS flight scenario. Results and verification against high-fidelity simulations will be provided in the final draft.

traffic complexity↗

Africa Food Security & Agriculture: Predicting the Likelihood of Human-elephant Conflict and Assessing Elephant Habitat Conditions During Extreme Drought and Crop Deficit in the Kavango-Zambezi Area

Human-wildlife conflict is increasingly more common due to human population growth, habitat fragmentation, and changing climatic conditions. This conflict is particularly evident in the Kavango-Zambezi area, where over three million people share the landscape with an abundant megafauna population. As the changing climate continues to exacerbate drought severity and subsequent food availability, conflict between humans and wildlife has become more prevalent. In the Kavango-Zambezi area, conflict between elephants and humans has resulted in crop loss, property damage, and threats to public safety. In order to manage current and future conflict, The Ecoexist Project and Connected Conservation have been working to empower farmers and conserve the natural habitat. This DEVELOP project employed Earth observations to conduct a time series analysis of vegetation health change, elephant movement, and climate conditions, from 2017 to 2020. Data were aggregated into the wet (November through April) and dry (May through October) seasons. The resulting analysis demonstrated the potential to use Landsat 8 Operational Land Imager (OLI), Global Precipitation Measurement’s Integrated Multi-satellite Retrievals for GPM (GPM IMERG), and TerraClimate data to identify potential areas of conflict under increased seasonal variability. An improved understanding of conflict drivers will help support sustainable wildlife conservation and food security in the future.

DEVELOP Project Summary↗

Africa Food Security & Agriculture: Predicting the Likelihood of Human-elephant Conflict and Assessing Elephant Habitat Conditions During Extreme Drought and Crop Deficit in the Kavango-Zambezi Area

Human-wildlife conflict is increasingly more common due to human population growth, habitat fragmentation, and changing climatic conditions. This conflict is particularly evident in the Kavango-Zambezi area, where over three million people share the landscape with an abundant megafauna population. As the changing climate continues to exacerbate drought severity and subsequent food availability, conflict between humans and wildlife has become more prevalent. In the Kavango-Zambezi area, conflict between elephants and humans has resulted in crop loss, property damage, and threats to public safety. In order to manage current and future conflict, The Ecoexist Project and Connected Conservation have been working to empower farmers and conserve the natural habitat. This DEVELOP project employed Earth observations to conduct a time series analysis of vegetation health change, elephant movement, and climate conditions, from 2017 to 2020. Data were aggregated into the wet (November through April) and dry (May through October) seasons. The resulting analysis demonstrated the potential to use Landsat 8 Operational Land Imager (OLI), Global Precipitation Measurement’s Integrated Multi-satellite Retrievals for GPM (GPM IMERG), and TerraClimate data to identify potential areas of conflict under increased seasonal variability. An improved understanding of conflict drivers will help support sustainable wildlife conservation and food security in the future.

DEVELOP Tech Paper↗

An Impedance-Based Complexity Metric for Unmanned Aircraft System Traffic Scenario Classification

This paper introduces an impedance-based metric to capture the complexity of a given unmanned aircraft system traffic scenario. The metric accounts for both the number of aircraft and the traffic flow pattern. The work presented here extends an earlier approach that introduced another scenario complexity metric based on the number of potential conflicts weighted by the conflict resolution cost associated. Complexity measurements for randomly-generated scenarios were produced through high-fidelity fast-time simulations and treated as baseline. Then the impedance based metric was evaluated, for the same scenarios, without the need for an actual flight simulation and a conflict resolution method. The results show that the impedance-based metric has a strong correlation to the baseline data and performs marginally better than the weighted conflict-based complexity metric introduced in the earlier work. The metric computation generates impedance maps which are useful for identifying high complexity regions in a scenario, where flight plan changes might be necessitated. This metric can therefore be used, in conjunction with other complexity metrics, to inform adequate traffic management strategies and classify a traffic scenario as acceptable, unacceptable or acceptable with changes made to flight plans that pass through the high complexity regions. The metric can also be used as a guidance metric for strategic conflict management methods.

Complexity↗

Introduction to Air Traffic Management

The presentation introduces students and faculty to air traffic management with focus on air traffic data for data-science. Starting with the common attributes of transportation systems — highway transportation, air transportation and data transportation, the initial set of slides discuss the purpose of data-science in air traffic management, reasons why air traffic management is challenging, and the multidisciplinary nature of air traffic management research. The history of flight from 1903 — Wright Flyer — to 1987 — formation of the National Air Traffic Controllers Association — is briefly discussed. The national airspace system is described in terms of airports in the U. S., air traffic control facilities (flight service stations, terminal, enroute and system command center), airspace geometry (sectors, airways and navaids), governing regulations and directives, airspace classification (Class A through G), special use airspace, visual flight rules and instrument flight rules. The contents of a flight-plan are described. Weather briefing is discussed. The surveillance equipment used for surface, terminal area and enroute are described, and the aircraft states obtained using the surveillance data are listed. Airline operations control functions — schedule development, flight planning, resource scheduling and flight following — are noted. Next, the roles and responsibilities of air traffic controllers and traffic flow managers are discussed. Separation standards and conflict resolution techniques are outlined. Finally, traffic flow management techniques are reviewed with an illustrative example.

Air Traffic Management↗

Introduction to Air Traffic Management

The presentation introduces students and faculty to air traffic management with focus on air traffic data for data-science. Starting with the common attributes of transportation systems — highway transportation, air transportation and data transportation, the initial set of slides discuss the purpose of data-science in air traffic management, reasons why air traffic management is challenging, and the multidisciplinary nature of air traffic management research. The history of flight from 1903 — Wright Flyer — to 1987 — formation of the National Air Traffic Controllers Association — is briefly discussed. The national airspace system is described in terms of airports in the U. S., air traffic control facilities (flight service stations, terminal, enroute and system command center), airspace geometry (sectors, airways and navaids), governing regulations and directives, airspace classification (Class A through G), special use airspace, visual flight rules and instrument flight rules. The contents of a flight-plan are described. Weather briefing is discussed. The surveillance equipment used for surface, terminal area and enroute are described, and the aircraft states obtained using the surveillance data are listed. Airline operations control functions — schedule development, flight planning, resource scheduling and flight following — are noted. Next, the roles and responsibilities of air traffic controllers and traffic flow managers are discussed. Separation standards and conflict resolution techniques are outlined. Finally, traffic flow management techniques are reviewed with an illustrative example.

Air Traffic Management↗

Pilot and Controller Evaluations of Separation Function Allocation in Air Traffic Management

Two human-in-the-loop simulation experiments were conducted in coordinated fashion to investigate the allocation of separation assurance functions between ground and air and between humans and automation. The experiments modeled a mixed-operations concept in which aircraft receiving ground-based separation services shared the airspace with aircraft providing their own separation service (i.e., self-separation). Ground-based separation was provided by air traffic controllers without automation tools, with tools, or by ground-based automation with controllers in a managing role. Airborne self-separation was provided by airline pilots using self-separation automation enabled by airborne surveillance technology. The two experiments, one pilot-focused and the other controller-focused, addressed selected key issues of mixed operations, assuming the starting point of current-day operations and modeling an emergence of NextGen technologies and procedures. In the controller-focused experiment, the impact of mixed operations on controller performance was assessed at four stages of NextGen implementation. In the pilot-focused experiment, the limits to which pilots with automation tools could take full responsibility for separation from ground-controlled aircraft were tested. Results indicate that the presence of self-separating aircraft had little impact on the controllers' ability to provide separation services for ground-controlled aircraft. Overall performance was best in the most automated environment in which all aircraft were data communications equipped, ground-based separation was highly automated, and self-separating aircraft had access to trajectory intent information for all aircraft. In this environment, safe, efficient, and highly acceptable operations could be achieved for twice today's peak airspace throughput. In less automated environments, reduced trajectory intent exchange and manual air traffic control limited the safely achievable airspace throughput and negatively impacted the maneuver efficiency of self-separating aircraft through high-density airspace. In a test of scripted conflicts with ground-managed aircraft, flight crews of self-separating aircraft prevented separation loss in all conflicts with detection time greater than one minute. In debrief, pilots indicated a preference for at least five minute's alerting notice and trajectory intent information on all aircraft. When intent information on ground-managed aircraft was available, self-separating aircraft benefited from fewer conflict alerts and fewer required deviations from trajectory-based operations.

Wing, David↗

Ombuds Office 2023 Biennial Report

The Los Alamos National Laboratory (LANL) Ombuds Charter requires the Ombuds Office to issue a report every two years to the Laboratory Director. The prior Ombuds Biennial Report was published in July of 2021, celebrating 25 years of Ombuds history at the Lab. This 2023 report details office transitions and new initiatives over the past two years, along with our ongoing conflict resolution work of one-on-one discussions, classes, presentations, workshops, and facilitations. The Ombuds Office supports the mission of LANL in myriad ways. We champion the LANL culture statement of “ How we do work is as important as What we do,” and we reinforce LANL’s values of integrity, service, excellence, and teamwork. Accordingly, the mission of the Ombuds Office is to support employees in their work, enhance communication, mitigate conflict, and encourage a positive working environment. The Ombuds Office adheres to the International Ombuds Association’s (IOA) Standards of Practice and Code of Ethics (see Appendix). As such, the Ombuds Office is informal, confidential, impartial, and independent. We do not advocate for managers or employees. We don’t tell people what to do; we don’t give advice. All of our services are voluntary. LANL employees seek out the Ombuds Office as a neutral place where they can collect their thoughts, whether in person, on the phone, or online. We help individuals explore and navigate tough issues. Employees expand their understanding of their options, assess what is within their control, and decide what is in their best interest. The Ombuds Office promotes smart, professional conflict management. This report highlights the work of the Ombuds Office and provides a closer look at both quantitative and qualitative data, including anecdotal information and endorsements. It concludes with a discussion of further opportunities to expand the reach of the Ombuds Office to more LANL employees.

99 GENERAL AND MISCELLANEOUS↗

TRACC_PB SOSS Integrated Traffic Simulation for CLT Ramp Operation

This presentation provides the current task under the NASA-DLR research collaboration for airport surface. It presents the effort done to adapt TRACC and SOSS software components to simulate airport (CLT) ramp area traffic management using TRACC's conflict free taxi trajectory optimization and SOSS's fast time simulation platform.

surface operations↗

Transitioning from Free-Flight to TRACON Airspace: The Ground Perspective of User-Preferred Descents

Free-flight is considered to play a major role in the future air traffic environment. Studies are underway addressing different concepts for free-flight and self separation in enroute airspace. One common opinion throughout the different concepts is that the airspace surrounding major airports, the Terminal Radar Approach CONtrol (TRACON) will not be a free flight area. This means that aircraft in this area are completely controlled by air traffic controllers, who may be supported by decision support system like the Center TRACON Automation System (CTAS). How the transition from the free-flight area (enroute airspace) to the terminal area will take place is currently unclear, This paper describes a study at NASA Ames Research Center addressing the perspective of air traffic controllers handling user-preferred (FMS-optimized) descent trajectories during this transition phase. Two major issues in enabling user preferred descents from the controllers' point of view are predictability and controllability. In an environment in which the air traffic services are highly responsive to user preferences controllers need to know, where and when aircraft will change their trajectory and they need to have appropriate means and procedures at hand to control the aircraft according to the overall traffic situation. Predictability shall be enhanced by: 1) Indicating airspace corridors for descending aircraft; 2) Modify the controller interface; 3) Using a ground based conflict probe; 4) Making use of downlinked intent information from the aircraft FMS; and 5) Requiring to fly pilots on user preferred trajectories coupled to the FMS in the lateral and vertical axis. Additional controllability shall be achieved by supporting the controllers with CTAS center tools: 1) Traffic Management Advisor (TMA); 2) Conflict Probing and Trial Planning (CP/TP); and 3) Enroute Descent Advisor (E/DA). The paper describes the general concept and the modifications to current systems required to enable the concept. It explains the experiment design and discusses the results with regard to controller acceptability and usability. Potential benefits and drawbacks of the overall concept are indicated.

Prevot, Thomas↗

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↗

A Distributed Trajectory-Oriented Approach to Managing Traffic Complexity

In order to handle the expected increase in air traffic volume, the next generation air transportation system is moving towards a distributed control architecture, in which ground-based service providers such as controllers and traffic managers and air-based users such as pilots share responsibility for aircraft trajectory generation and management. While its architecture becomes more distributed, the goal of the Air Traffic Management (ATM) system remains to achieve objectives such as maintaining safety and efficiency. It is, therefore, critical to design appropriate control elements to ensure that aircraft and groundbased actions result in achieving these objectives without unduly restricting user-preferred trajectories. This paper presents a trajectory-oriented approach containing two such elements. One is a trajectory flexibility preservation function, by which aircraft plan their trajectories to preserve flexibility to accommodate unforeseen events. And the other is a trajectory constraint minimization function by which ground-based agents, in collaboration with air-based agents, impose just-enough restrictions on trajectories to achieve ATM objectives, such as separation assurance and flow management. The underlying hypothesis is that preserving trajectory flexibility of each individual aircraft naturally achieves the aggregate objective of avoiding excessive traffic complexity, and that trajectory flexibility is increased by minimizing constraints without jeopardizing the intended ATM objectives. The paper presents conceptually how the two functions operate in a distributed control architecture that includes self separation. The paper illustrates the concept through hypothetical scenarios involving conflict resolution and flow management. It presents a functional analysis of the interaction and information flow between the functions. It also presents an analytical framework for defining metrics and developing methods to preserve trajectory flexibility and minimize its constraints. In this framework flexibility is defined in terms of robustness and adaptability to disturbances and the impact of constraints is illustrated through analysis of a trajectory solution space with limited degrees of freedom and in simple constraint situations involving meeting multiple times of arrival and resolving a conflict.

Idris, Husni↗

Roadmap to Cooperative Operating Practices for Strategic Conflict Detection and Resolution in the Upper Class E Traffic Management Concept

As the governing body of flight operations in the highly anticipated emergent area of Upper Class E airspace (60,000 ft and above), the Federal Aviation Administration (FAA) has recognized the potential for a possible extensible traffic management system for new entrants into this domain. Following the successes with Unmanned Aircraft Systems (UAS) Traffic Management (UTM) and Advanced / Urban Air Mobility (AAM / UAM) Traffic Management programs, FAA put forth an initial concept of operations for supporting the start of the Upper Class E Traffic Management (ETM) concept. Like UTM and AAM / UAM, ETM is envisioned to also be a community-based, industry driven cooperative management concept. However, tailoring it to be adaptable to the atmospheric communication, navigation, and surveillance deficits, as well as the diverse vehicle and mission profiles operating in the ETM environment will be the challenge. As such, the National Aeronautics and Space Administration (NASA) Ames Research Center has been investigating several technologies that will help enable industry in the development of this new type of cooperative operating environment. These technologies are being prototyped and will be tested in a collaborative evaluation of an initial ETM system in late 2023. The evaluation will concentrate on building out ETM system technologies that will inform the participants regarding operational intent sharing, strategic conflict detection, and the resultant deconfliction process. In addition to the technical aspects, key roles and responsibilities will need to be defined. This will be done through exploring community-agreed upon Cooperative Operating Practices (COPs) that include procedures and capabilities to aid in timely, strategic conflict identification and resolution to be developed during the evaluation. As an initial step to the evaluation, the ETM research team at NASA Ames solicited industry feedback on various aspects of ETM operations from subject matter experts. A virtual tabletop walkthrough session was held over a two-day period to follow a roadmap through the functional steps needed to build COPs, focusing on strategic conflict detection and resolution.

Upper Class E Traffic Management (ETM)↗

A Model-based Approach to Reactive Self-Configuring Systems

This paper describes Livingstone, an implemented kernel for a self-reconfiguring autonomous system, that is reactive and uses component-based declarative models. The paper presents a formal characterization of the representation formalism used in Livingstone, and reports on our experience with the implementation in a variety of domains. Livingstone's representation formalism achieves broad coverage of hybrid software/hardware systems by coupling the concurrent transition system models underlying concurrent reactive languages with the discrete qualitative representations developed in model-based reasoning. We achieve a reactive system that performs significant deductions in the sense/response loop by drawing on our past experience at building fast prepositional conflict-based algorithms for model-based diagnosis, and by framing a model-based configuration manager as a prepositional, conflict-based feedback controller that generates focused, optimal responses. Livingstone automates all these tasks using a single model and a single core deductive engine, thus making significant progress towards achieving a central goal of model-based reasoning. Livingstone, together with the HSTS planning and scheduling engine and the RAPS executive, has been selected as the core autonomy architecture for Deep Space One, the first spacecraft for NASA's New Millennium program.

Williams, Brian C.↗

Collaborative Resource Allocation

Collaborative Resource Allocation Networking Environment (CRANE) Version 0.5 is a prototype created to prove the newest concept of using a distributed environment to schedule Deep Space Network (DSN) antenna times in a collaborative fashion. This program is for all space-flight and terrestrial science project users and DSN schedulers to perform scheduling activities and conflict resolution, both synchronously and asynchronously. Project schedulers can, for the first time, participate directly in scheduling their tracking times into the official DSN schedule, and negotiate directly with other projects in an integrated scheduling system. A master schedule covers long-range, mid-range, near-real-time, and real-time scheduling time frames all in one, rather than the current method of separate functions that are supported by different processes and tools. CRANE also provides private workspaces (both dynamic and static), data sharing, scenario management, user control, rapid messaging (based on Java Message Service), data/time synchronization, workflow management, notification (including emails), conflict checking, and a linkage to a schedule generation engine. The data structure with corresponding database design combines object trees with multiple associated mortal instances and relational database to provide unprecedented traceability and simplify the existing DSN XML schedule representation. These technologies are used to provide traceability, schedule negotiation, conflict resolution, and load forecasting from real-time operations to long-range loading analysis up to 20 years in the future. CRANE includes a database, a stored procedure layer, an agent-based middle tier, a Web service wrapper, a Windows Integrated Analysis Environment (IAE), a Java application, and a Web page interface.

Wang, Yeou-Fang↗