SEARCH · Engineering Papers

Results for “coordinated operation”

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 217 records · Page 12

All sources NASA NTRS DOE OSTI

NASA NTRS2016

R2U2 in Space: System and Software Health Management for Small Satellites

In order for small but complex systems like rovers, SmallSats, or Unmanned Aircraft (UAS) to operate autonomously, they must have a real-time solution for assessing their own system health. System and Software Health Management (SHM) enables better detection of faulty sensors and software problems, and enables better fault management including mitigation of unpredicted fault scenarios in the absence of a human on-board. In recent work, we have developed a Responsive, Realizable, Unobtrusive Unit (R2U2) for on-board SHM of autonomous UAS and demonstrated its ability to detect faults during flight time. These faults, from sensor failures, to software problems, to malicious security attacks, can present as transient temporal faults that even humans are challenged to find. An R2U2 congfiuration is a modular combination of multiple types of temporal logic runtime observers with fault-specic Bayesian Nets and sensor filters. R2U2 reasons about both on-board hardware and software components; R2U2 itself can be instantiated as an independent FPGA (Field-Programmable Gate Array)-based conguration or as a software component running independently from other software on-board. Small satellites, such as CubeSats, also require on-board SHM and failure mitigation, as limited telemetry bandwidth does not allow the transmission of the entire system state for ground-based health management. However, the autonomous operation of satellites brings a set of challenges different from UAS, including the effects of radiation on non-rad-hard, low-cost components, and the harsher environment of space. We surmise that a new extension of R2U2 could be adapted to help better detect, for example, radiation errors in cheaper COTS (Commercial Off the Shelf) (not rad-hard) components often used in small space systems. Since small satellites often operate in coordination, we will also examine new ways of distributed monitoring of their communication and cooperation and real-time detection of off-nominal situations utilizing multiple satellites. This talk will discuss preliminary work and ideas for building on terrestrial success of system and software health management for the harsher, and differently challenging, environment of space.

Runtime Verification & Validation↗

NASA NTRSDate not supplied

Initial Development of A Digital Twin Model for an Electrified Aircraft Propulsion Emulation Rig

In support of aviation fuel burn and emission reduction goals, NASA is pursing high-payoff research investments that promise to transform aviation. This includes investments in Electrified Aircraft Propulsion (EAP), which relies on the generation, storage, transmission, and use of electrical power for producing thrust and optimizing propulsion system efficiency. Multiple technology challenges must be addressed to unlock the full potential of EAP. This includes advances in propulsion controls, which will be vital for ensuring coordinated efficient operation of the complex integrated subsystems that comprise EAP architectures. To support EAP controls research, the NASA Glenn Research Center has developed the Hybrid Propulsion Emulation Rig (HyPER). The HyPER laboratory hardware includes shaft-mounted electric machines, power converters, power supplies, power distribution cables, and an energy storage device that can be reconfigured to represent a variety of EAP architectures. It also includes an integrated real-time computer system that hosts developed EAP control software and turbomachinery simulations. This enables the electrical system and rotating shafts of EAP designs to be implemented in actual hardware and integrated with turbomachinery simulations and system-level EAP control logic implemented in software. In this form, the HyPER laboratory provides a partially simulated, partially hardware-in-the-loop test environment enabling the initial development and evaluation of EAP control technology. A prerequisite for the development of EAP control designs is the availability of a system model that accurately reflects the operation of the electrical system hardware. To support this need, a digital twin model of the HyPER electrical system hardware is under development. This model is being coded in the MATLAB Simulink environment and uses the NASA-developed Electrical Modeling and Thermal Analysis Toolbox (EMTAT) to construct a digital twin framework. EMTAT contains generic electrical component building blocks that are simulated at turbomachinery timescales. Associated inputs and outputs allow the blocks to be combined to model complete electrical systems. The EMTAT blocks also contain adjustable internal maps and parameters that can be set to reflect the operation of a specific electrical component. For the HyPER digital twin, the settings of these EMTAT block internal maps and parameters is determined through machine learning approaches applied to characterization run data collected from the laboratory. During characterization runs the laboratory electrical system hardware is subjected to a full range of torque, speed, and power settings. Acquired data is then used to estimate EMTAT block parameters using a variety of machine learning techniques. The resulting digital twin model is found to match the operation of actual HyPER hardware with an accuracy suitable for control development purposes. It also holds promise for other applications including modeling the performance of HyPER laboratory reconfigurations and model-based anomaly detection. Planned follow-on work to automate post-processing of acquired laboratory data to update the HyPER digital twin model will also be presented and discussed.

Electrified Aircraft Propulsion↗

DOE OSTI2024

Development of Supervisory Control System for Thermal Energy Distribution System

The integrated energy system (IES) refers to the combination of nuclear energy generation with other energy sources to enable the efficiency and reliability of power generations. To create technologically viable and economically competitive systems, supervisory control strategies are critical for optimizing performance and ensuring stability across different energy generation, transportation, and utilization. This work focuses on the control strategies for the thermal energy distribution system (TEDS), which is a cornerstone of the Dynamic Energy Transport and Integration Laboratory at Idaho National Laboratory. TEDS currently relies on operators to coordinate across different components to manage energy storage and ensure efficiency. This work demonstrates the use of model predictive control (MPC) with surrogate models in determining optimal setpoints for major TEDS components. The capability of MPC-based supervisory control system is evaluated by autonomously matching the power outputs from a Dymola-based TEDS with target heat demands.

22 - GENERAL STUDIES OF NUCLEAR REACTORS↗

NASA NTRSDate not supplied

Safety Benefit Analysis of Conformance Monitoring for Situation Awareness in UTM

This work presents an analytical approach to address situations in drone operations when strategic coordination alone cannot ensure safety, requiring support from the Conformance Monitoring for Situation Awareness service and potentially other deconfliction services. This study focuses on evaluating the impact of off-nominal operations on both UA-to-UA collision risk and ground injury risk. It first establishes a relationship between the likelihood of off-nominal flights and the effectiveness of strategic coordination. The analysis then derives operational conditions where strategic coordination alone is insufficient to meet target safety requirements, particularly when the likelihood of off-nominal operations exceeds a certain threshold. The results indicate that higher operational tempo or density requires a lower likelihood of offnominal operations for strategic coordination to remain effective and meet safety targets. These findings provide quantitative operational thresholds for when CMSA services are necessary. This work contributes to the safety case for both strategic coordination and CMSA services, offering analysis on when CMSA should be employed to support strategic coordination in achieving the desired safety levels. It also establishes a framework for incorporating other deconfliction services in future safety case analyses.

Strategic deconfliction↗

NASA NTRSDate not supplied

Safety Benefit Analysis of Conformance Monitoring for Situation Awareness in UTM

Strategic deconfliction↗

NASA NTRS2010

MaROS Strategic Relay Planning and Coordination Interfaces

The Mars Relay Operations Service (MaROS) is designed to provide planning and analysis tools in support of ongoing Mars Network relay operations. Strategic relay planning requires coordination between lander and orbiter mission ground data system (GDS) teams to schedule and execute relay communications passes. MaROS centralizes this process, correlating all data relevant to relay coordination to provide a cohesive picture of the relay state. Service users interact with the system through thin-layer command line and web user interface client applications. Users provide and utilize data such as lander view periods of orbiters, Deep Space Network (DSN) antenna tracks, and reports of relay pass performance. Users upload and download relevant relay data via formally defined and documented file structures including some described in Extensible Markup Language (XML). Clients interface with the system via an http-based Representational State Transfer (ReST) pattern using Javascript Object Notation (JSON) formats. This paper will provide a general overview of the service architecture and detail the software interfaces and considerations for interface design.

Allard, Daniel A.↗

DOE OSTI2022

FLISR in the Presence of DERs ADMS Test Bed Use Case

Fault location, isolation, and restoration (FLISR) is one of the distribution automation applications that utilities are most interested in. It operates groups of switches on distribution feeders to improve the reliability of power delivery after localizing outages. FLISR is an essential function for enabling a self-healing grid, and it directly affects grid reliability and resilience. The presence of DERs brings both new opportunities and challenges for FLISR applications. For instance, some DERs can work as backup generation sources and help energize local networks so more switching options can be achieved with the coordination of FLISR operations; however, the existence of DERs also brings new challenges. The bidirectional power flow resulting from DERs might require dynamic changes to protective devices' fault current settings, and thus the FLISR application will need to dynamically adjust its operations in coordination with the dynamic protection settings. Also, some FLISR applications make their service restoration decisions and close tie-switches based on predefined rules; however, the presence of DERs and their impact on altering net loads on the local feeder network are not considered. For this use case, the project team is using the FLISR application of the Survalent ADMS operating on a real-time simulation of a feeder from Central Georgia EMC, a cooperative electric utility. The performance of the FLISR application is being evaluated for different locations and combinations of DERs, including grid-forming battery energy storage systems.

ADMS↗

NASA NTRS2014

Coordination Between Sectors in Shared Airspace Operations

Recent studies have shown that a more efficient use of airspace may involve shared airspace operations, i.e., temporal as well as spatial separation of arrival and departure flows [1][2]. Temporal separation would permit a departure aircraft to fly through an arrival flow, depending on an available gap. This would necessitate careful and precise coordination between controllers in different sectors. Three methods of coordination which permit the penetration of a controller's airspace by another controller's aircraft are described: point out, look-and-go, and prearranged coordination procedure. Requirements of each method are given, along with associated problems that have surfaced in the field as described by Aviation Safety and Reporting System (ASRS) and other reports. A Human-in-the-Loop simulation was designed to compare two of the methods: point out and prearranged coordination procedures. In prearranged coordination procedures (P-ACP), the controllers control an aircraft in another controller's airspace according to specified prearranged procedures, without coordinating each individual aircraft with another controller, as is done with point outs. In the simulation, three experienced controllers rotated through two arrival sectors and a non-involved arrival sector of a Terminal Radar Approach Control (TRACON) airspace. Results of eighteen one-hour simulation runs (nine in each of the two conditions) showed no impact of the coordination method on separation violations nor on arrival times for 208 departing aircraft crossing an arrival stream. Participant assessment indicated that although both coordination conditions were acceptable, the prearranged coordination procedure condition was slightly safer, more efficient, timely, and overall, worked better operationally. Problems arose in the point out condition regarding controllers noticing acceptance of point outs. Also, in about half of the point-out runs, time pressure was felt to have had an impact on when and if the departures could cross an arrival stream. An additional problem with point outs may be confusion in the field about which controller has responsibility for separating point-out aircraft from other aircraft.

Parke, Bonny↗

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 NTRS1984

Operational air traffic control requirements for the new Voice Switching and Control System

Final user requirements defined for the Voice Switching and Control System (VSCS) to be implemented for ATC functions as part of the Area Control Facility (ACF) concept for the National Airspace System (NAS) are described. The VSCS will be communications equipment at operational stations, supervisory positions, and support systems, the switching system itself, and interfaces between the VSCS and other systems. Supervisory users will include the Area Manager, Traffic Management Coordinator, a Military Operations Specialists, a Weather Coordinator, a NAS manager, Maintenance, and a flight Data Communications Specialist. The VSCS will supply computerized communications capability within and among ATC centers. Details of the efforts used to define the system requirements are recounted, noting the heavy reliance on recommendations from active ATC personnel.

Leon, N.↗

NASA NTRSDate not supplied

Coordination between Federated Scheduling and Conflict Resolution in UAM Operations

This work proposes a federated scheduling algorithm and explores two mechanisms for coordinating federated scheduling and conflict resolution functions - two core traffic management functions in urban air mobility operations. A federated scheduling algorithm is first developed, together with data that needs to be shared among schedulers. Two mechanisms for coordinating scheduling and conflict resolution functions are then introduced and studied as conflicts in high-density operations may not be completely resolved by conflict resolution function alone. The first coordination mechanism is constructed based on the arrival scheduler at the destination and another one utilizes the departure scheduler at the origin. Experiments and trade space studies are conducted to compare these two mechanisms using fast-time traffic simulations. Results show that both mechanisms perform well in coordinating scheduling and conflict resolution functions and helping resolve all potential conflicts. Experiments also show that with proper parameter selection, both mechanisms can achieve better efficiency (less delay) while maintaining zero losses of separation.

Federated scheduling↗

NASA NTRS2021

Coordination between Federated Scheduling and Conflict Resolution in UAM Operations

Federated scheduling↗

NASA NTRS1998

Quantity, Revisited: An Object-Oriented Reusable Class

"Quantity", a prototype implementation of an object-oriented class, was developed for two reasons: to help engineers and scientists manipulate the many types of quantities encountered during routine analysis, and to create a reusable software component to for large domain-specific applications. From being used as a stand-alone application to being incorporated into an existing computational mechanics toolkit, "Quantity" appears to be a useful and powerful object. "Quantity" has been designed to maintain the full engineering meaning of values with respect to units and coordinate systems. A value is a scalar, vector, tensor, or matrix, each of which is composed of Value Components, each of which may be an integer, floating point number, fuzzy number, etc., and its associated physical unit. Operations such as coordinate transformation and arithmetic operations are handled by member functions of "Quantity". The prototype has successfully tested such characteristics as maintaining a numeric value, an associated unit, and an annotation. In this paper we further explore the design of "Quantity", with particular attention to coordinate systems.

Funston, Monica Gayle↗

NASA NTRS1974

The problem of organization of a coastal coordinating computer center

The fundamental principles of the operation of a coastal coordinating and computing center under conditions of automation are presented. Special attention is devoted to the work of Coastal Computer Center of the Arctic and Antarctic Scientific Research Institute. This center generalizes from data collected in expeditions and also from observations made at polar stations.

Dyubkin, I. A.↗

NASA NTRS2015

AMO EXPRESS: A Command and Control Experiment for Crew Autonomy

NASA is investigating a range of future human spaceflight missions, including both Mars-distance and Near Earth Object (NEO) targets. Of significant importance for these missions is the balance between crew autonomy and vehicle automation. As distance from Earth results in increasing communication delays, future crews need both the capability and authority to independently make decisions. However, small crews cannot take on all functions performed by ground today, and so vehicles must be more automated to reduce the crew workload for such missions. NASA's Advanced Exploration Systems Program funded Autonomous Mission Operations (AMO) project conducted an autonomous command and control demonstration of intelligent procedures to automatically initialize a rack onboard the International Space Station (ISS) with power and thermal interfaces, and involving core and payload command and telemetry processing, without support from ground controllers. This autonomous operations capability is enabling in scenarios such as a crew medical emergency, and representative of other spacecraft autonomy challenges. The experiment was conducted using the Expedite the Processing of Experiments for Space Station (EXPRESS) rack 7, which was located in the Port 2 location within the U.S Laboratory onboard the International Space Station (ISS). Activation and deactivation of this facility is time consuming and operationally intensive, requiring coordination of three flight control positions, 47 nominal steps, 57 commands, 276 telemetry checks, and coordination of multiple ISS systems (both core and payload). The autonomous operations concept includes a reduction of the amount of data a crew operator is required to verify during activation or de-activation, as well as integration of procedure execution status and relevant data in a single integrated display. During execution, the auto-procedures provide a step-by-step messaging paradigm and a high level status upon termination. This messaging and high level status is the only data generated for operator display. To enhance situational awareness of the operator, the Web-based Procedure Display (WebPD) provides a novel approach to the issues of procedure display and execution tracking. For this demonstration, the procedure was initiated and monitored from the ground. As the Timeliner sequences executed, their high level execution status was transmitted to ground, for WebPD consumption.

Stetson, Howard K.↗

NASA NTRSDate not supplied

TPSAS-NF1676L-14864-DND

Anna Trujillo↗

NASA NTRSDate not supplied

TPSAS-NF1676L-14989-DND

Objective 1: Develop a research test-bed and database to provide data/proof of concept for Ground Control Station (GCS) NAS operations. Objective 2: Coordinate with standards organizations to develop human factors guidelines for GCS operation in the NAS. Interest in UAS routine access: 1) Federal government – DHS, NOAA, Commerce, Interior, FBI, DOT 2) Military 3) Local governments – police, fire, port authority 4) Commercial – utilities, news agencies, private security, photographers, hobbyists

Anna Trujillo↗