Search NASA⌕ Search

SEARCH · Search NASA

Results for “separation 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 289 records · Page 16
All sourcesNASA NTRSDOE OSTI
NASA NTRS1997

Identification of Error Patterns in Terminal-Area ATC Communications

Advancing air traffic management technologies have enabled a greater number of aircraft to use the same airspace more effectively. As aircraft separations are reduced and final approaches are more finely timed, there is less room for error. The present study examined 122 terminal-area, loss-of-separation and procedure violation incidents reported to the Aviation Safety Reporting System (ASRS) by air traffic controllers. Narrative description codes were used for the incidents for type of violation, contributing factors, recovery strategies, and consequences. Usually multiple errors occurred prior to the violation. Error sequences were analyzed and common patterns of errors were identified. In half of the incidents, errors were noticed in time to correct mistakes. Of these, almost 43% committed additional errors during the recovery attempt. This analysis shows that redundancies in the present air traffic control system may not be sufficient to support large increases in traffic density. Error prevention and design considerations for air traffic management systems are discussed.

Quinn, Cheryl↗
NASA NTRS2002

Regaining Lost Separation in a Piloted Simulation of Autonomous Aircraft Operations

NASA is currently investigating a new concept of operations for the National Airspace System, designed to improve capacity while maintaining or improving current levels of safety. This concept, known as Distributed Air/Ground Traffic Management (DAG-TM), allows appropriately equipped autonomous aircraft to maneuver freely for flight optimization while resolving conflicts with other traffic and staying out of special use airspace and hazardous weather. While Airborne Separation Assurance System (ASAS) tools would normally allow pilots to resolve conflicts before they become hazardous, evaluation of system performance in sudden, near-term conflicts is needed in order to determine concept feasibility. If an acceptable safety level can be demonstrated in these situations, then operations may be conducted with lower separation minimums. An experiment was conducted in NASA Langley s Air Traffic Operations Lab to address issues associated with resolving near-term conflicts and the potential use of lower separation minimums. Sixteen commercial airline pilots flew a total of 32 traffic scenarios that required them to use prototype ASAS tools to resolve close range pop-up conflicts. Required separation standards were set at either 3 or 5 NM lateral spacing, with 1000 ft vertical separation being used for both cases. Reducing the lateral separation from 5 to 3 NM did not appear to increase operational risk, as indicated by the proximity to the intruder aircraft. Pilots performed better when they followed tactical guidance cues provided by ASAS than when they didn't follow the guidance. As air-air separation concepts are evolved, further studies will consider integration issues between ASAS and existing Airborne Collision Avoidance Systems (ACAS).These types of non-normal events will require the ASAS to provide effective alerts and resolutions prior to the time that an Airborne Collision Avoidance System (ACAS) would give a Resolution Advisory (RA). When an RA is issued, a pilot must take immediate action in order to avoid a potential near miss. The Traffic Alert and Collision Avoidance System (TCAS) II currently functions as an ACAS aboard commercial aircraft. Depending on the own aircraft s altitude, TCAS only issues RA s 15-35 seconds prior to the Closest Point of Approach (CPA). Prior to an RA, DAG-TM pilots operating autonomous aircraft must rely solely on ASAS for resolution guidance. An additional area of DAG-TM concept feasibility relates to a potential reduction in separation standards. Lower separation standards are likely needed in order to improve NAS efficiency and capacity. Current separation minimums are based in large part on the capabilities of older radar systems. Safety assessments are needed to determine the feasibility of reduced separation minimums. They will give strong consideration to surveillance system performance, including accuracy, integrity, and availability. Candidate surveillance systems include Automatic Dependent Surveillance-Broadcast (ADS-B) and multi-lateration systems. Considering studies done for Reduced Vertical Separation Minimums (RVSM) operations, it is likely that flight technical errors will also be considered. In addition to a thorough evaluation of surveillance system performance, a potential decision to lower the separation standards should also take operational considerations into account. An ASAS Safety Assessment study identified improper maneuvering in response to a conflict (due to ambiguous or improper resolution commands or a pilot s failure to comply with the resolution) as a potential safety risk. If near-term conflicts with lower separation minimums were determined to be more challenging for pilots, the severity of these risks could be even greater.

Barhydt, Richard↗
NASA NTRS1994

On-Orbit Propellant Motion Resulting from an Impulsive Acceleration

In-space docking and separation maneuvers of spacecraft that have large fluid mass fractions may cause undesirable spacecraft motion in response to the impulsive-acceleration-induced fluid motion. An example of this potential low-gravity fluid management problem arose during the development of the shuttle/Centaur vehicle. Experimentally verified numerical modeling techniques were developed to establish the propellant dynamics, and subsequent vehicle motion, associated with the separation of the Centaur vehicle from the shuttle cargo bay. Although the shuttle/Centaur development activity has been suspended, the numerical modeling techniques are available to predict on-orbit liquid motion resulting from impulsive accelerations for other missions and spacecraft.

Hochstein, John I.↗
NASA NTRS1973

Multifunction display system

The design and characteristics of a multifunction display system are discussed. The system is a general purpose, time-shared, electro-optical display driven by onboard data management systems. It is capable of presenting information in forms such as alphanumerics, symbolics, and graphics, separately or in combination. The components of the system are: (1) data terminal simulator/input loader, (2) keyboard controller, (3) CRT display indicator, and (4) programmable symbol generator.

Kendall, K.↗
NASA NTRS1986

Spaceborne optical disk controller development

The current status and potential applications of an optical-disk buffer (ODB) memory system being developed by an interagency consortium including NASA and the USAF are reviewed. The design goals for the ODB include usable capacity 1 Tb, maximum data rate 1.6 Gb/s, read error rate less than 10 to the -12th, time to initial access less than 100 ms, and unlimited read/write cycles. Present efforts focus on a brassboard ODB which employs 12 14-inch magnetooptic disks and 24 nine-diode read/write heads. A typical space application of an optical disk mass memory system (ODMMS) is discussed: as communications buffer, temporary storage, and/or multiuser I/O buffer for data management on the Space Station Earth Observing System. Environmental, operational, system-architecture, and functional-separation factors; critical design issues; and standardization questions for spaceborne ODMMSs are examined in detail.

Shull, Thomas A.↗
NASA NTRS1994

Telecommunications end-to-end systems monitoring on TOPEX/Poseidon: Tools and techniques

The TOPEX/Poseidon Project Satellite Performance Analysis Team's (SPAT) roles and responsibilities have grown to include functions that are typically performed by other teams on JPL Flight Projects. In particular, SPAT Telecommunication's role has expanded beyond the nominal function of monitoring, assessing, characterizing, and trending the spacecraft (S/C) RF/Telecom subsystem to one of End-to-End Information Systems (EEIS) monitoring. This has been accomplished by taking advantage of the spacecraft and ground data system structures and protocols. By processing both the received spacecraft telemetry minor frame ground generated CRC flags and NASCOM block poly error flags, bit error rates (BER) for each link segment can be determined. This provides the capability to characterize the separate link segments, determine science data recovery, and perform fault/anomaly detection and isolation. By monitoring and managing the links, TOPEX has successfully recovered approximately 99.9 percent of the science data with an integrity (BER) of better than 1 x 10(exp 8). This paper presents the algorithms used to process the above flags and the techniques used for EEIS monitoring.

Calanche, Bruno J.↗
NASA NTRS2014

Assessment of MSFCs Process for the Development and Activation of Space Act Agreements

A Space Act Agreement (SAA) is a contractual vehicle that NASA utilizes to form partnerships with non-NASA entities to stimulate cutting-edge innovation within the science and technology communities while concurrently supporting the NASA missions. SAAs are similar to traditional contracts in that they involve the commitment of Agency resources but allow more flexibility and are more cost effective to implement than traditional contracts. Consequently, the use of SAAs to develop partnerships has greatly increased over the past several years. To facilitate this influx of SAAs, Marshall Space Flight Center (MSFC) developed a process during a kaizen event to streamline and improve the quality of SAAs developed at the Center level. This study assessed the current SAA process to determine if improvements could be implemented to increase productivity, decrease time to activation, and improve the quality of deliverables. Using a combination of direct procedural observation, personnel interviews, and statistical analysis, elements of the process in need of remediation were identified and potential solutions developed. The findings focus primarily on the difficulties surrounding tracking and enforcing process adherence and communication issues among stakeholders. Potential solutions include utilizing customer relationship management (CRM) software to facilitate process coordination and co-locating or potentially merging the two separate organizations involved in SAA development and activation at MSFC.

Daugherty, Rachel A.↗
NASA NTRS2004

Initiating the 2002 Mars Science Laboratory (MSL) Technology Program

The Mars Science Laboratory (MSL) Project is an aggressive mission launching in 2009 to investigate the Martian environment and requires new capabilities that are currently are not available. The MSL Technology Program is developing a wide-range of technologies needed for this Mission and potentially other space missions. The MSL Technology Program reports to both the MSL Project and the Mars Technology Program (MTP). The dual reporting process creates a challenging management situation, but ensures the new technology meets both the specific MSL requirements and the broader Mars Program requirements. MTP is a NASA-wide technology development program managed by JPL and is divided into a Focused Program and a Base Program. The MSL Technology Program is under the focused program and is tightly coupled to MSL's mission milestones and deliverables. The technology budget is separate from the flight Project budget, but the technology's requirements and the development process are tightly coordinated with the Project. The MSL Technology Program combines the proven management techniques of flight projects with the commercial technology management strategies of industry and academia, to create a technology management program that meets the short-term requirements of MSL and the long-term requirements of MTP. This paper examines the initiation of 2002 MSL Technology program. Some of the areas discussed in this paper include technology definition, task selection, technology management, and technology assessment. This paper also provides an update of the 2003 MSL technology program and examines some of the drivers that changed the program from its initiation.

Caffrey, Robert T.↗
NASA NTRS2010

Display Sharing: An Alternative Paradigm

The current Johnson Space Center (JSC) Mission Control Center (MCC) Video Transport System (VTS) provides flight controllers and management the ability to meld raw video from various sources with telemetry to improve situational awareness. However, maintaining a separate infrastructure for video delivery and integration of video content with data adds significant complexity and cost to the system. When considering alternative architectures for a VTS, the current system's ability to share specific computer displays in their entirety to other locations, such as large projector systems, flight control rooms, and back supporting rooms throughout the facilities and centers must be incorporated into any new architecture. Internet Protocol (IP)-based systems also support video delivery and integration. IP-based systems generally have an advantage in terms of cost and maintainability. Although IP-based systems are versatile, the task of sharing a computer display from one workstation to another can be time consuming for an end-user and inconvenient to administer at a system level. The objective of this paper is to present a prototype display sharing enterprise solution. Display sharing is a system which delivers image sharing across the LAN while simultaneously managing bandwidth, supporting encryption, enabling recovery and resynchronization following a loss of signal, and, minimizing latency. Additional critical elements will include image scaling support, multi -sharing, ease of initial integration and configuration, integration with desktop window managers, collaboration tools, host and recipient controls. This goal of this paper is to summarize the various elements of an IP-based display sharing system that can be used in today's control center environment.

Brown, Michael A.↗
NASA NTRS2016

Separation Assurance and Scheduling Coordination in the Arrival Environment

Separation assurance (SA) automation has been proposed as either a ground-based or airborne paradigm. The arrival environment is complex because aircraft are being sequenced and spaced to the arrival fix. This paper examines the effect of the allocation of the SA and scheduling functions on the performance of the system. Two coordination configurations between an SA and an arrival management system are tested using both ground and airborne implementations. All configurations have a conflict detection and resolution (CD&R) system and either an integrated or separated scheduler. Performance metrics are presented for the ground and airborne systems based on arrival traffic headed to Dallas/ Fort Worth International airport. The total delay, time-spacing conformance, and schedule conformance are used to measure efficiency. The goal of the analysis is to use the metrics to identify performance differences between the configurations that are based on different function allocations. A surveillance range limitation of 100 nmi and a time delay for sharing updated trajectory intent of 30 seconds were implemented for the airborne system. Overall, these results indicate that the surveillance range and the sharing of trajectories and aircraft schedules are important factors in determining the efficiency of an airborne arrival management system. These parameters are not relevant to the ground-based system as modeled for this study because it has instantaneous access to all aircraft trajectories and intent. Creating a schedule external to the CD&R and the scheduling conformance system was seen to reduce total delays for the airborne system, and had a minor effect on the ground-based system. The effect of an external scheduler on other metrics was mixed.

function allocation↗
NASA NTRS1995

Helicopter Human Factors

Even under optimal conditions, helicopter flight is a most demanding form of human-machine interaction, imposing continuous manual, visual, communications, and mental demands on pilots. It is made even more challenging by small margins for error created by the close proximity of terrain in NOE flight and missions flown at night and in low visibility. Although technology advances have satisfied some current and proposed requirements, hardware solutions alone are not sufficient to ensure acceptable system performance and pilot workload. However, human factors data needed to improve the design and use of helicopters lag behind advances in sensor, display, and control technology. Thus, it is difficult for designers to consider human capabilities and limitations when making design decisions. This results in costly accidents, design mistakes, unrealistic mission requirements, excessive training costs, and challenge human adaptability. NASA, in collaboration with DOD, industry, and academia, has initiated a program of research to develop scientific data bases and design principles to improve the pilot/vehicle interface, optimize training time and cost, and maintain pilot workload and system performance at an acceptable level. Work performed at Ames, and by other research laboratories, will be reviewed to summarize the most critical helicopter human factors problems and the results of research that has been performed to: (1) Quantify/model pilots use of visual cues for vehicle control; (2) Improve pilots' performance with helmet displays of thermal imagery and night vision goggles for situation awareness and vehicle control; (3) Model the processes by which pilots encode maps and compare them to the visual scene to develop perceptually and cognitively compatible electronic map formats; (4) Evaluate the use of spatially localized auditory displays for geographical orientation, target localization, radio frequency separation; (5) Develop and flight test control/display concepts; (6) Quantify, model, predict, and improve pilots, workload-management strategies; and (7) Design computer-game trainers to reduce training time and cost.

Hart, Sandra G.↗
NASA NTRS2011

Trajectory-Based Complexity (TBX): A Modified Aircraft Count to Predict Sector Complexity During Trajectory-Based Operations

In this paper we introduce a new complexity metric to predict -in real-time- sector complexity for trajectory-based operations (TBO). TBO will be implemented in the Next Generation Air Transportation System (NextGen). Trajectory-Based Complexity (TBX) is a modified aircraft count that can easily be computed and communicated in a TBO environment based upon predictions of aircraft and weather trajectories. TBX is scaled to aircraft count and represents an alternate and additional means to manage air traffic demand and capacity with more consideration of dynamic factors such as weather, aircraft equipage or predicted separation violations, as well as static factors such as sector size. We have developed and evaluated TBX in the Airspace Operations Laboratory (AOL) at the NASA Ames Research Center during human-in-the-loop studies of trajectory-based concepts since 2009. In this paper we will describe the TBX computation in detail and present the underlying algorithm. Next, we will describe the specific TBX used in an experiment at NASA's AOL. We will evaluate the performance of this metric using data collected during a controller-inthe- loop study on trajectory-based operations at different equipage levels. In this study controllers were prompted at regular intervals to rate their current workload on a numeric scale. When comparing this real-time workload rating to the TBX values predicted for these time periods we demonstrate that TBX is a better predictor of workload than aircraft count. Furthermore we demonstrate that TBX is well suited to be used for complexity management in TBO and can easily be adjusted to future operational concepts.

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

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 NTRS1976

Distributed management of scientific projects - An analysis of two computer-conferencing experiments at NASA

Between August 1975 and March 1976, two NASA projects with geographically separated participants used a computer-conferencing system developed by the Institute for the Future for portions of their work. Monthly usage statistics for the system were collected in order to examine the group and individual participation figures for all conferences. The conference transcripts were analysed to derive observations about the use of the medium. In addition to the results of these analyses, the attitudes of users and the major components of the costs of computer conferencing are discussed.

Vallee, J.↗
NASA NTRSDate not supplied

Lunar Passive Fuel Cell Technologies: Evaporator + Fluid Polishing Elements

This project investigates key elements of a fully-passive, fuel-cell based, surface power generation concept. The overall concept replaces the actively pumped thermal management of a state of the art (SOA) fuel cell/electrolyzer stack with a passive 2-phase thermosyphon for heat transport and a passive shape memory actuating radiator for temperature management. The elements of the concept investigated in this project are: Evaporator Element: Evaluating the compatibility of common fuel-cell interconnect materials in the evaporator of a 2-phase water thermosyphon Fluid Polishing element: The use of membrane gas separation and resin water polishing to address non-condensable gas removal and water purity.

Fuel Cell↗
NASA NTRS2011

Health Monitor for Multitasking, Safety-Critical, Real-Time Software

Health Manager can detect Bad Health prior to a failure occurring by periodically monitoring the application software by looking for code corruption errors, and sanity-checking each critical data value prior to use. A processor s memory can fail and corrupt the software, or the software can accidentally write to the wrong address and overwrite the executing software. This innovation will continuously calculate a checksum of the software load to detect corrupted code. This will allow a system to detect a failure before it happens. This innovation monitors each software task (thread) so that if any task reports "bad health," or does not report to the Health Manager, the system is declared bad. The Health Manager reports overall system health to the outside world by outputting a square wave signal. If the square wave stops, this indicates that system health is bad or hung and cannot report. Either way, "bad health" can be detected, whether caused by an error, corrupted data, or a hung processor. A separate Health Monitor Task is started and run periodically in a loop that starts and stops pending on a semaphore. Each monitored task registers with the Health Manager, which maintains a count for the task. The registering task must indicate if it will run more or less often than the Health Manager. If the task runs more often than the Health Manager, the monitored task calls a health function that increments the count and verifies it did not go over max-count. When the periodic Health Manager runs, it verifies that the count did not go over the max-count and zeroes it. If the task runs less often than the Health Manager, the periodic Health Manager will increment the count. The monitored task zeroes the count, and both the Health Manager and monitored task verify that the count did not go over the max-count.

Zoerner, Roger↗