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 127 records · Page 7

All sources NASA NTRS DOE OSTI

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 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.↗

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↗

NASA NTRS1977

Coordinated crew performance in commercial aircraft operations

A specific methodology is proposed for an improved system of coding and analyzing crew member interaction. The complexity and lack of precision of many crew and task variables suggest the usefulness of fuzzy linguistic techniques for modeling and computer simulation of the crew performance process. Other research methodologies and concepts that have promise for increasing the effectiveness of research on crew performance are identified.

Murphy, M. R.↗

NASA NTRS2006

Atmospheric Radiation Measurements Aerosol Intensive Operating Period: Comparison of Aerosol Scattering during Coordinated Flights

In May 2003, a Twin Otter airplane, equipped with instruments for making in situ measurements of aerosol optical properties, was deployed during the Atmospheric Radiation Measurements (ARM) Program s Aerosol Intensive Operational Period in Oklahoma. Several of the Twin Otter flights were flown in formation with an instrumented light aircraft (Cessna 172XP) that makes routine in situ aerosol profile flights over the site. This paper presents comparisons of measured scattering coefficients at 467 nm, 530 nm, and 675 nm between identical commercial nephelometers aboard each aircraft. Overall, the agreement between the two nephelometers decreases with longer wavelength. During the majority of the flights, the Twin Otter flew with a diffuser inlet while the Cessna had a 1 mm impactor, allowing for an estimation of the fine mode fraction aloft. The fine mode fraction aloft was then compared to the results of a ground-based nephelometer. Comparisons are also provided in which both nephelometers operated with identical 1 mm impactors. These scattering coefficient comparisons are favorable at the longer wavelengths (i.e., 530 nm and 675 nm), yet differed by approximately 30% at 467 nm. Mie scattering calculations were performed using size distribution measurements, made during the level flight legs. Results are also presented from Cadenza, a new continuous wave cavity ring-down (CW-CRD) instrument, which compared favorably (i.e., agreed within 2%) with data from other instruments aboard the Twin Otter. With this paper, we highlight the significant implications of coarse mode (larger than 1 mm) aerosol aloft with respect to aerosol optical properties.

Hallar, A. G.↗

NASA NTRS2020

UAS Service Supplier Network Performance

This report summarizes the performance of Unmanned Aircraft System (UAS) Service Suppliers (USS) in the Technical Capability Level 4 (TCL4) flight test performed by NASA and its partners in support of the UAS Traffic Management (UTM) concept. TCL4 is the final in a series of TCL demonstrations of a traffic management system for small UAS (sUAS). All demonstrations have been executed in collaboration with industry partners. The [FAA 2018] UTM Concept of Operations document describes UTM as:...the manner in which the FAA will support operations for predominantly sUAS operating in low altitude airspace. UTM utilizes industry’s ability to supply services under FAA’s regulatory authority where these services do not currently exist. It is a community-based traffic management system, where the Operators are responsible for the coordination, execution, and management of operations, with rules of the road established by FAA. UTM is designed to support the demand and expectations for a broad spectrum of operations with ever-increasing complexity and risk. UTM should be considered a collection of services rather than a monolithic application. The following section describes the architecture at a high level. For further insight, the FAA’s concept document [FAA 2018] or NASA’s earlier concept publication [NASA 2016] should be consulted.

Rios, Joseph L.↗

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 NTRS2023

NAIRAS Ionizing Radiation Model: Extension from Atmosphere to Space

The Nowcast of Aerospace Ionizing RAdiation System (NAIRAS) model is a real-time, global, physics-based model originally developed to predict exposure from cosmic radiation to air travelers from both galactic and solar sources. A prototype operational NAIRAS model has provided tabular and graphical data products via its public web site for about ten years. A new version of the NAIRAS model has been developed that incorporates an extension of the model domain from the atmospheric ionizing radiation environment to the space radiation environment, with the addition of the trapped inner belt proton source and altitude-dependent and rigidity-dependent geomagnetic shielding of the galactic cosmic rays (GCR) and solar energetic particle (SEP) protons. New output products of differential and integral particle flux have been developed for the characterization of single-event effects (SEE), expanding the application of NAIRAS from human radiation exposure assessment to allowing end-users to quantify radiation environment risks to aviation and spacecraft microelectronic systems. The NAIRAS model has transitioned to prototype operations at the Community Coordinated Modeling Center (CCMC) where the model now operates in two modes: (1) real-time global predictions of the atmospheric radiation environment and (2) a run-on-request (RoR) service allowing the user to select a specific time period for the global dosimetric calculations, or to upload an aircraft, balloon, or spaceflight trajectory file to provide predictions of the dosimetric and particle flux quantities along the flight path. The new features of NAIRAS version 3.0 are described in this paper and example results of the new output products for low-Earth orbit (LEO), medium-Earth orbit (MEO), and free-space radiation environments are presented

Christopher J. Mertens↗