Search NASA⌕ Search

SEARCH · Search NASA

Results for “Operations”

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 109 records · Page 6
All sourcesNASA NTRSDOE OSTI
NASA NTRS1998

Development and Preliminary Results of CTAS on Airline Operational Control Center Operations

Continued growth and expansion of air traffic and increased air carrier economic pressures have mandated greater flexibility and collaboration in air traffic management. The ability of airspace users to select their own routes, so called "free-flight", and to more actively manage their fleet operations for maximum economic advantage are receiving great attention. A first step toward greater airspace user and service provider collaboration is information sharing. In this work, arrival scheduling and airspace management data generated by the NASA/FAA Center/TRACON Automation System (CTAS) and used by the FAA service provider is shared with an airline with extensive operations within the CTAS operational domain. The design and development of a specialized airline CTAS "repeater" system is described, as well as some preliminary results of the impact and benefits of this information on the air carrier's operations. FAA controller per aircraft scheduling information, such as that provided by CTAS, has never before been shared in real-time with an airline. Expected airline benefits include improved fleet planning and arrival gate management, more informed "hold-go" decisions, and avoidance of costly aircraft diversions to alternate airports when faced with uncertain airborne arrival delays.

Zelenka, Richard↗
NASA NTRS2002

Crew Factors in Flight Operations XIV: Alertness Management in Regional Flight Operations Education Module

Regional operations encompass a broad range of pilots and equipment. This module is intended to help all those involved in regional aviation, including pilots, schedulers, dispatchers, maintenance technicians, policy makers, and others, to understand the physiological factors underlying fatigue, how flight operations affect fatigue, and what can be done to counteract fatigue and maximize alertness and performance in their operations. The overall purpose of this module is to promote aviation safety, performance, and productivity. It is intended to meet three specific objectives: (1) to explain the current state of knowledge about the physiological mechanisms underlying fatigue; (2) to demonstrate how this knowledge can be applied to improving flight crew sleep, performance, and alertness; and (3) to offer strategies for alertness management. Aviation Safety Reporting System (ASRS) and National Transportation Safety Board (NISH) reports are used throughout this module to demonstrate that fatigue is a safety issue in the regional operations community. The appendices at the end of this module include the ASRS reports used for the examples contained in this publication, brief introductions to sleep disorders and relaxation techniques, summaries of relevant NASA publications, and a list of general readings on sleep, sleep disorders, and circadian rhythms.

Rosekind, Mark R.↗
NASA NTRS2001

Crew Factors in Flight Operations X: Alertness Management in Flight Operations

In response to a 1980 congressional request, NASA Ames Research Center initiated a Fatigue/Jet Lag Program to examine fatigue, sleep loss, and circadian disruption in aviation. Research has examined fatigue in a variety of flight environments using a range of measures (from self-report to performance to physiological). In 1991, the program evolved into the Fatigue Countermeasures Program, emphasizing the development and evaluation of strategies to maintain alertness and performance in operational settings. Over the years, the Federal Aviation Administration (FAA) has become a collaborative partner in support of fatigue research and other Program activities. From the inception of the Program, a principal goal was to return the information learned from research and other Program activities to the operational community. The objectives of this Education and Training Module are to explain what has been learned about the physiological mechanisms that underlie fatigue, demonstrate the application of this information in flight operations, and offer some specific fatigue countermeasure recommendations. It is intended for all segments of the aeronautics industry, including pilots, flight attendants, managers, schedulers, safety and policy personnel, maintenance crews, and others involved in an operational environment that challenges human physiological capabilities because of fatigue, sleep loss, and circadian disruption.

Rosekind, Mark R.↗
NASA NTRS2004

Development and Preliminary Results of CTAS on Airline Operational Control Center Operations

Continued growth and expansion of air traffic and increased air carrier economic pressures have mandated greater flexibility and collaboration in air traffic management. The ability of airspace users to select their own routes, so called "free-flight", and to more actively manage their fleet operations for maximum economic advantage are receiving great attention. A first step toward greater airspace user and service provider collaboration is information sharing. In this work, arrival scheduling and airspace management data generated by the NASA/FAA Center/TRACON Automation System (CTAS) and used by the FAA service provider is shared with an airline with extensive operations within the CTAS operational domain. The design and development of a specialized airline CTAS "repeater" system is described, as well as some preliminary results of the impact and benefits of this information on the air carrier's operations. FAA controller per aircraft scheduling information, such as that provided by CTAS, has never before been shared in real-time with an airline. Expected airline benefits include improved fleet planning and arrival gate management, more informed "hold-go decisions, and avoidance of costly aircraft diversions to alternate airports when faced with uncertain airborne arrival delays.

Zelenka, Richard↗
NASA NTRS2007

The Apollo Medical Operations Project: Recommendations to Improve Crew Health and Performance for Future Exploration Missions and Lunar Surface Operations

Medical requirements for the future Crew Exploration Vehicle (CEV), Lunar Surface Access Module (LSAM), advanced Extravehicular Activity (EVA) suits and Lunar habitat are currently being developed. Crews returning to the lunar surface will construct the lunar habitat and conduct scientific research. Inherent in aggressive surface activities is the potential risk of injury to crewmembers. Physiological responses to and the operational environment of short forays during the Apollo lunar missions were studied and documented. Little is known about the operational environment in which crews will live and work and the hardware that will be used for long-duration lunar surface operations.Additional information is needed regarding productivity and the events that affect crew function such as a compressed timeline. The Space Medicine Division at the NASA Johnson Space Center (JSC) requested a study in December 2005 to identify Apollo mission issues relevant to medical operations that had impact to crew health and/or performance. The operationally oriented goals of this project were to develop or modify medical requirements for new exploration vehicles and habitats, create a centralized database for future access, and share relevant Apollo information with the multiple entities at NASA and abroad participating in the exploration effort.

Scheuring, Richard A.↗
NASA NTRS1990

Method for concurrent execution of primitive operations by dynamically assigning operations based upon computational marked graph and availability of data

Computationally complex primitive operations of an algorithm are executed concurrently in a plurality of functional units under the control of an assignment manager. The algorithm is preferably defined as a computationally marked graph contianing data status edges (paths) corresponding to each of the data flow edges. The assignment manager assigns primitive operations to the functional units and monitors completion of the primitive operations to determine data availability using the computational marked graph of the algorithm. All data accessing of the primitive operations is performed by the functional units independently of the assignment manager.

Stoughton, John W.↗
NASA NTRS2008

Testing the Efficacy of Synthetic Vision during Non-Normal Operations as an Enabling Technology for Equivalent Visual Operations

Synthetic Vision (SV) may serve as a revolutionary crew/vehicle interface enabling technology to meet the challenges of the Next Generation Air Transportation System Equivalent Visual Operations (EVO) concept that is, the ability to achieve or even improve on the safety of Visual Flight Rules (VFR) operations, maintain the operational tempos of VFR, and potentially retain VFR procedures independent of actual weather and visibility conditions. One significant challenge lies in the definition of required equipage on the aircraft and on the airport to enable the EVO concept objective. An experiment was conducted to evaluate the effects of the presence or absence of SV, the location (head-up or head-down) of this information during an instrument approach, and the type of airport lighting information on landing minima. Another key element of the testing entailed investigating the pilot s awareness and reaction to non-normal events (i.e., failure conditions) that were unexpectedly introduced into the experiment. These non-normals are critical determinants in the underlying safety of all-weather operations. This paper presents the experimental results specific to pilot response to non-normal events using head-up and head-down synthetic vision displays.

Kramer, Lynda J.↗
NASA NTRS1947

Investigation of the I-40 Jet-Propulsion Engine in the Cleveland Altitude Wind Tunnel. V - Operational Characteristics: Operational Characteristics - 5

An investigation has been conducted in the Cleveland altitude wind tunnel to determine the operational characteristics of the I-40 jet-propulsion engine over a range of pressure altitudes from 10,000 to 50,000 feet and ram-pressure ratios from 1.00 to 1.76. Engine operational data were obtained with the engine in the standard configuration and with various modifications of the fuel system, the electrical system, and the combustion chambers. The effects of altitude and airspeed on operating speed range, starting, windmilli.ng, acceleration, speed regulation, cooling, and vibration of the standard and modified engines were determined, and damage to parts was noted. Maximum engine speed was obtainable at all altitudes and airspeeds wi th each fuel-control system investigated. The minimum idling speed was raised by increases in altitude and airspeed. The lowest minimum stable speeds were obtained with the standard configuration using 40-gallon nozzles with individual metering plugs. The engine was started normally at altitudes as high as 20,000 feet with all of the fuel systems and ignition combinations except one. Ignition at 70,000 feet was difficult and, although successful ignition occurred, acceleration was slow and usually characterized by excessive tail-pipe temperature. During windmilling investigations of the engine equipped with the standard fuel system, the engine could not be started at ram-pressure ratios of 1.1 to 1.7 at altitudes of 10,000, 20,000 and 30,000 feet. When equipped with the production barometric and Monarch 40-gallon nozzles, the engine accelerated in 12 seconds from an engine speed of 6000 rpm to 11,000 rpm at 20,000 feet and an average tail-pipe temperature of 11000 F. At the same altitude and temperature, all the engine configurations had approximately the same rate of acceleration. The Woodward governor produced the safest accelerations, inasmuch as it could be adjusted to automatically prevent acceleration blow out. The engine speed was held constant by the Woodward governor and the Edwards regulator during simulated dives and climbs at constant throttle position. The bearing cooling system was satisfactory at all altitudes and airspeeds. The engines operated without serious failure, although the exhaust cone, the tail pipe, and the airplane fuselage were damaged during altitude starts.

Golladay, Richard L.↗
NASA NTRS2011

Flight Dynamics Operations: Methods and Lessons Learned from Space Shuttle Orbit Operations

The Flight Dynamics Officer is responsible for trajectory maintenance of the Space Shuttle. This paper will cover high level operational considerations, methodology, procedures, and lessons learned involved in performing the functions of orbit and rendezvous Flight Dynamics Officer and leading the team of flight dynamics specialists during different phases of flight. The primary functions that will be address are: onboard state vector maintenance, ground ephemeris maintenance, calculation of ground and spacecraft acquisitions, collision avoidance, burn targeting for the primary mission, rendezvous, deorbit and contingencies, separation sequences, emergency deorbit preparation, mass properties coordination, payload deployment planning, coordination with the International Space Station, and coordination with worldwide trajectory customers. Each of these tasks require the Flight Dynamics Officer to have cognizance of the current trajectory state as well as the impact of future events on the trajectory plan in order to properly analyze and react to real-time changes. Additionally, considerations are made to prepare flexible alternative trajectory plans in the case timeline changes or a systems failure impact the primary plan. The evolution of the methodology, procedures, and techniques used by the Flight Dynamics Officer to perform these tasks will be discussed. Particular attention will be given to how specific Space Shuttle mission and training simulation experiences, particularly off-nominal or unexpected events such as shortened mission durations, tank failures, contingency deorbit, navigation errors, conjunctions, and unexpected payload deployments, have influenced the operational procedures and training for performing Space Shuttle flight dynamics operations over the history of the program. These lessons learned can then be extended to future vehicle trajectory operations.

Cutri-Kohart, Rebecca M.↗
NASA NTRS2011

Autonomous Satellite Operations Via Secure Virtual Mission Operations Center

The science community is interested in improving their ability to respond to rapidly evolving, transient phenomena via autonomous rapid reconfiguration, which derives from the ability to assemble separate but collaborating sensors and data forecasting systems to meet a broad range of research and application needs. Current satellite systems typically require human intervention to respond to triggers from dissimilar sensor systems. Additionally, satellite ground services often need to be coordinated days or weeks in advance. Finally, the boundaries between the various sensor systems that make up such a Sensor Web are defined by such things as link delay and connectivity, data and error rate asymmetry, data reliability, quality of service provisions, and trust, complicating autonomous operations. Over the past ten years, researchers from the NASA Glenn Research Center (GRC), General Dynamics, Surrey Satellite Technology Limited (SSTL), Cisco, Universal Space Networks (USN), the U.S. Geological Survey (USGS), the Naval Research Laboratory, the DoD Operationally Responsive Space (ORS) Office, and others have worked collaboratively to develop a virtual mission operations capability. Called VMOC (Virtual Mission Operations Center), this new capability allows cross-system queuing of dissimilar mission unique systems through the use of a common security scheme and published application programming interfaces (APIs). Collaborative VMOC demonstrations over the last several years have supported the standardization of spacecraft to ground interfaces needed to reduce costs, maximize space effects to the user, and allow the generation of new tactics, techniques and procedures that lead to responsive space employment.

Miller, Eric↗
NASA NTRS2012

The HAL 9000 Space Operating System Real-Time Planning Engine Design and Operations Requirements

In support of future deep space manned missions, an autonomous/automated vehicle, providing crew autonomy and an autonomous response planning system, will be required due to the light time delays in communication. Vehicle capabilities as a whole must provide for tactical response to vehicle system failures and space environmental effects induced failures, for risk mitigation of permanent loss of communication with Earth, and for assured crew return capabilities. The complexity of human rated space systems and the limited crew sizes and crew skills mix drive the need for a robust autonomous capability on-board the vehicle. The HAL 9000 Space Operating System[2] designed for such missions and space craft includes the first distributed real-time planning / re-planning system. This paper will detail the software architecture of the multiple planning engine system, and the interface design for plan changes, approval and implementation that is performed autonomously. Operations scenarios will be defined for analysis of the planning engines operations and its requirements for nominal / off nominal activities. An assessment of the distributed realtime re-planning system, in the defined operations environment, will be provided as well as findings as it pertains to the vehicle, crew, and mission control requirements needed for implementation.

Stetson, Howard↗
NASA NTRS2013

Flight Deck Surface Trajectory-based Operations (STBO): Results of Piloted Simulations and Implications for Concepts of Operation (ConOps)

The results offour piloted medium-fidelity simulations investigating flight deck surface trajectory-based operations (STBO) will be reviewed. In these flight deck STBO simulations, commercial transport pilots were given taxi clearances with time and/or speed components and required to taxi to the departing runway or an intermediate traffic intersection. Under a variety of concept of operations (ConOps) and flight deck information conditions, pilots' ability to taxi in compliance with the required time of arrival (RTA) at the designated airport location was measured. ConOps and flight deck information conditions explored included: Availability of taxi clearance speed and elapsed time information; Intermediate RTAs at intermediate time constraint points (e.g., intersection traffic flow points); STBO taxi clearances via ATC voice speed commands or datal ink; and, Availability of flight deck display algorithms to reduce STBO RTA error. Flight Deck Implications. Pilot RTA conformance for STBO clearances, in the form of ATC taxi clearances with associated speed requirements, was found to be relatively poor, unless the pilot is required to follow a precise speed and acceleration/deceleration profile. However, following such a precise speed profile results in inordinate head-down tracking of current ground speed, leading to potentially unsafe operations. Mitigating these results, and providing good taxi RTA performance without the associated safety issues, is a flight deck avionics or electronic flight bag (EFB) solution. Such a solution enables pilots to meet the taxi route RTA without moment-by-moment tracking of ground speed. An avionics or EFB "error-nulling" algorithm allows the pilot to view the STBO information when the pilot determines it is necessary and when workload alloys, thus enabling the pilot to spread his/her attention appropriately and strategically on aircraft separation airport navigation, and the many other flight deck tasks concurrently required. Surface Traffic Management (STM) System Implications. The data indicate a number of implications regarding specific parameters for ATC/STM algorithm development. Pilots have a tendency to arrive at RTA points early with slow required speeds, on time for moderate speeds, and late with faster required speeds. This implies that ATC/STM algorithms should operate with middle-range speeds, similar to that of non-STBO taxi performance. Route length has a related effect: Long taxi routes increase the earliness with slow speeds and the lateness with faster speeds. This is likely due to the" open-loop" nature of the task in which the speed error compounds over a longer time with longer routes. Results showed that this may be mitigated by imposing a small number oftime constraint points each with their own RTAs effectively tuming a long route into a series of shorter routes - and thus improving RTA performance. STBO ConOps Implications. Most important is the impact that these data have for NextGen STM system ConOps development. The results of these experiments imply that it is not reasonable to expect pilots to taxi under a "Full STBO" ConOps in which pilots are expected to be at a predictable (x,y) airport location for every time (t). An STBO ConOps with a small number of intermediate time constraint points and the departing runway, however, is feasible, but only with flight deck equipage enabling the use of a display similar to the "error-nulling algorithm/display" tested.

Foyle, David C.↗
NASA NTRS2006

Independent Space Operators: Gaining a Voice in Design for Operability

Affordable and sustainable space exploration remains an elusive goal. We explore the competitive advantages of evolving towards independent operators for space transportation in our economy. We consider the pros and cons of evolving business organizations that operate and maintain space transportation system assets independently from flight system manufacturers and from host spaceports. The case is made that a more competitive business climate for creating inherently operable, dependable, and supportable space transportation systems can evolve out of today's traditional vertical business model-a model within which the voice of the operator is often heard, but rarely acted upon during crucial design commitments and critical design processes. Thus new business models may be required, driven less by hardware consumption and more by space system utilization.

incentives↗
NASA NTRS2018

Increased Operational Availability and Simplified Operations Using Dither Gyro Scale Factor Calibration

The traditional approach to on-orbit gyro scale factor calibration has been to perform large angle rotations about each gyro axis. The maneuvers require the science instruments to be taken offline, reducing operational availability and require a significant amount of interaction from the ground. To increase operational availability and to reduce the burden on mission operators, a novel approach to gyro scale factor calibration was developed, modeled and successfully demonstrated on the Geostationary Operational Environmental Satellite (GOES-16) to estimate gyro scale factor errors to within 1500 parts per million (ppm) without taking the science instruments offline.

Reth, Alan D.↗
NASA NTRS2019

Analysis of Interactions Between Urban Air Mobility (UAM) Operations and Conventional Traffic in Urban Areas: Traffic Alert and Collision Avoidance System (TCAS) Study for UAM Operations

This paper presents results on potential interaction effects from UAM (Urban Air Mobility) operations integrated into current operational scenarios by evaluating if/where/how Traffic alert and Collision Avoidance System (TCAS) alerts are triggered on-board commercial aircraft. A range of operational scenarios are evaluated with combinations of UAM vehicle route, speed, altitude, and direction along the DFW (Dallas-Fort Worth) "spine route." The effect of UAM altitude uncertainty on the above is also explored. The analysis was done for both South flow and North flow configurations of DFW. When UAM operations are deterministic, no TCAS RAs (Resolution Advisories) are issued. However, UAM altitude uncertainties point out geographic areas of concern with the associated severity of interactions.

Airspace↗
NASA NTRS2019

Analysis of Interactions Between Urban Air Mobility (UAM) Operations and Conventional Traffic in Urban Areas: Traffic Alert and Collision Avoidance (TCAS) Study for UAM Operations

This paper presents a preliminary modeling and analysis of interactions between proposed UAM operations and present-day conventional traffic if UAM operations occurred along FAA- approved helicopter routes and altitude ceilings. It assesses the extent to which the UAM operations will trigger TCAS resolution advisories (RA) aboard the conventional aircraft in the Dallas/Fort Worth (DFW) terminal airspace. It is observed that under deterministic UAM operational conditions, no RAs will be triggered. Furthermore, the impact of UAM altitude uncertainty is also evaluated. It is observed that restricting the UAM cruise altitudes to 990 feet above Mean Sea Level (MSL) or below reduced the chance of triggering an RA to under five percent throughout the day, even in the presence of maximum altitude error of 30 feet.

Bulusu, Vishwanath↗
NASA NTRSDate not supplied

Developing a Medical System Concept of Operations for Level of Care IV: Long-Duration Lunar Orbital and Surface Operations

A goal of the Human Research Program (HRP) Exploration Medical Capability (ExMC) Element Systems Engineering (SE) team is to define the technical system needed to support crew medical system capabilities for future exploration missions, including a mission with lunar orbital and long duration surface operations. The medical system concept of operations (ConOps) is the starting point of creating a foundation for a medical system that meets Level of Care IV requirements, as defined by NASA’s space flight human-system standards. This ConOps illustrates how NASA can provide a Level of Care IV medical system for crews within the various cis-lunar orbit and lunar surface habitat environments. The use case scenarios included in this ConOps illustrate required medical system capabilities for Level of Care IV and enable the ExMC SE team to develop integrated medical system requirements and identify capabilities required to meet those requirements. This discussion will focus on how this concept of operations was constructed – by utilizing the lessons learned from ExMC’s existing Short-Duration Lunar Orbit Medical System Concept of Operations, by employing Model-Based Systems Engineering, and by collaborating with stakeholders in order to ensure the necessary assumptions were made.

M. Kaetzer↗
NASA NTRSDate not supplied

Implementation of a SysML Model-Based Concept of Operations for Level of Care IV: Long-Duration Lunar Orbital and Surface Operations

One goal of the Human Research Program (HRP) Exploration Medical Capability (ExMC) Element Systems Engineering (SE) team is to define the technical system needed to support crew medical system capabilities for future exploration missions, including orbital and surface operations for long duration lunar missions. This is accomplished through the development of a Medical System Foundation, which communicates medical system requirements, capabilities, conditions, and resources that define a starting point for a medical system that meets the specification for design reference missions and associated Levels of Care (as defined by NASA-STD-3001). The starting point for creating this Medical System Foundation Model is the development of a Concept of Operations (ConOps) that describes the operation of the system from the point of view of the users. It includes a comprehensive and thoroughly vetted list of the users, their specific needs, the goals of the system, key assumptions about the system, and definitions of the system’s operational environments. The use case scenarios included in the ConOps illustrate required medical system capabilities for Level of Care IV and enable the ExMC SE team to develop integrated medical system requirements and identify capabilities required to meet those requirements. For this “Long Duration” Medical System Foundation development effort, ExMC replaced the traditional document-based ConOps with a model-based ConOps using model-based systems engineering. This approach has several advantages, including the facilitation of more efficient understanding of the material through information-dense images with less opportunity for misinterpretation than text alone, the roll-out of changes to the ConOps to stakeholders in real-time as they are approved, and the consolidation of all salient information into one centralized location. This discussion will focus on both how the model represents the ConOps content and how the SE team utilized lessons learned in an agile environment to improve the way this information was created and presented to stakeholders.

M Kaetzer↗