Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “transition operator”

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 NTRS1981

Operations analysis of gravity assisted rapid transit

Gravity assisted rapid transit (GART) with 6 percent grades before and after each station are compared with conventional systems in terms of energy consumption, run time, line capacity and schedule stability under abnormal circumstances. Parametric analyses of run times and energy consumption include the impact of alternate accelerating and braking levels. The capcity analysis uses a network simulation program to determine the location and severity of all signal delays. Based on results of initial simulations, the block design was revised to eliminate bottlenecks in normal operations. The systems are then compared at headways of 80 to 180 seconds. One month of incidence reports of a modern operating transit system are reviewed to determine the failures to be simulated. The impact of failures resulting in station delays (30 to 360 seconds), speed limit reduction (20 mph and 30 mph to one or more trains), vehicle performance (75 percent acceleration) are compared at scheduled headway of 90 to 180 seconds.

Source record↗
NASA NTRS2014

Adding "Missed" Science to Cassini's Ops Plan

The phenomenal success of the Cassini Mission at Saturn is largely due to flagship instruments, in a target rich environment, for a long period of time, executing almost error free complex mission operations. A smooth transition from cruise operations through the prime science mission and extended science (Equinox) mission culminating in the currently executing Solstice mission has folded in necessary procedural alterations due to improved understanding of the spacecraft, instruments, uplink and planning systems as well as additional science objectives. These have come with the maturation of the mission along with management of workforce reductions. One important set of operational changes has been initiated due to scientific findings highlighting "missed" science opportunities. This is the case for the Titan Meteorology Campaigns and Saturn Storm Watch Campaigns. These observations involve long term monitoring of the atmospheres of Titan and Saturn while the spacecraft and science teams are focused on other high priority targets of opportunity (like Enceladus). Our objective in this paper is to emphasize how a non-invasive strategy to get additional remarkable science was conceived and implemented in a mission with an already well defined operational plan. To illustrate this we will detail Titan Meteorology Campaign and Saturn Storm Watch Campaign integration and implementation strategies as well as the scientific goals and achievements of both.

Roy, Mou↗
NASA NTRS2014

Adding "Missed" Science to Cassini's Ops Plan

The phenomenal success of the Cassini Mission at Saturn is largely due to flagship instruments, in a target rich environment, for a long period of time, executing almost error free complex mission operations. A smooth transition from cruise operations through the prime science mission and extended science (Equinox) mission culminating in the currently executing Solstice mission has folded in necessary procedural alterations due to improved understanding of the spacecraft, instruments, uplink and planning systems as well as additional science objectives. These have come with the maturation of the mission along with management of workforce reductions. One important set of operational changes has been initiated due to scientific findings highlighting "missed" science opportunities. This is the case for the Titan Meteorology Campaigns and Saturn Storm Watch Campaigns. These observations involve long term monitoring of the atmospheres of Titan and Saturn while the spacecraft and science teams are focused on other high priority targets of opportunity (like Enceladus). Our objective in this paper is to emphasize how a non-invasive strategy to get additional remarkable science was conceived and implemented in a mission with an already well defined operational plan. To illustrate this we will detail Titan Meteorology Campaign and Saturn Storm Watch Campaign integration and implementation strategies as well as the scientific goals and achievements of both.

Roy, Mou↗
NASA NTRS1980

Overview of escalator applications in rail transit

The difference in operating environment and in construction between escalators in transit and nontransit use, the impact of recent escalator innovations, and areas which could benefit from urban mass transportation administration sponsored research and development are determined. Several factors causing a more severe transit escalator operating environment are identified. There are no significant design differences between transit and nontransit escalators. Recent innovations that have affected performance and cost include outdoor escalators, extra flat steps at both landings, and modular escalators. Data were collected by interviews at transit agencies. Long term, unscheduled, escalator maintenance records were available for analysis from one property. A description of escalator operating principles is provided. Transit represents less than 5% of the U.S. escalator market. Transit agencies have limited leverage on escalator industry practices. A substantial impact on transit escalator cost and performance can be achieved by research identifying when and how to apply and specify several of the more recent innovations. Purchase of escalators under long term (25 year) maintenance contracts is one method that has been used to promote escalators manufactured for minimum life cycle cost.

Deshpande, G.↗
NASA NTRS2014

Investigating the Impacts of a Separation Standard for UAS Operations in Enroute and Transition Airspace

Unmanned aircraft systems will be required to equip with a detect and avoid system in order to satisfy the federal aviation regulations to remain well clear of other aircraft. To comply with regulations in today’s operations manned aircraft must “see and avoid” other aircraft and use subjective judgment to determine whether those aircraft are well clear. For a detect-and- avoid (DAA) system to satisfy the requirement to stay well clear, a quantitative definition of well clear needs to be defined and evaluated. Definitions for the boundary of well clear have been proposed by the Unmanned Aircraft System (UAS) Executive Committee Science and Research Panel (SaRP) and the Radio Technical Commission for Aeronautics (RTCA) Special Committee 228 on Detect and Avoid Systems. This study investigates the interoperability implications of UAS using proposed well clear definitions as a separation standard for conducting operations in the national airspace system. The first analysis in the study focuses on the effect of variations in well clear definition parameters on the rate of losses of well clear per flight hour. The second analysis considers three well clear definitions and presents the relative state conditions of intruder aircraft as they encroach upon the well clear boundary. The third analysis focuses on the definition of the alerting criteria needed to inform the UAS operator of a potential loss of well clear. All three analyses are conducted in a NAS-wide fast-time simulation environment using UAS aircraft models, proposed UAS missions, and historical air defense radar data to populate the background traffic operating under visual flight rules. The results from the three analyses presented in this study inform the safety case, requirements development, and the operational environment for the DAA minimum operational performance standards.

UAS Seperation Standard↗
NASA NTRS1989

Expert system development methodology and the transition from prototyping to operations: FIESTA, a case study

A major barrier in taking expert systems from prototype to operational status involves instilling end user confidence in the operational system. The software of different life cycle models is examined and the advantages and disadvantages of each when applied to expert system development are explored. The Fault Isolation Expert System for Tracking and data relay satellite system Applications (FIESTA) is presented as a case study of development of an expert system. The end user confidence necessary for operational use of this system is accentuated by the fact that it will handle real-time data in a secure environment, allowing little tolerance for errors. How FIESTA is dealing with transition problems as it moves from an off-line standalone prototype to an on-line real-time system is discussed.

Happell, Nadine↗
NASA NTRS1989

Expert system development methodology and the transition from prototyping to operations - Fiesta, a case study

A major barrier in taking expert systems from prototype to operational status involves instilling end user confidence in the operational system. The software of different life cycle models is examined and the advantages and disadvantages of each when applied to expert system development are explored. The Fault Isolation Expert System for Tracking and data relay satellite system Applications (FIESTA) is presented as a case study of development of an expert system. The end user confidence necessary for operational use of this system is accentuated by the fact that it will handle real-time data in a secure environment, allowing little tolerance for errors. How FIESTA is dealing with transition problems as it moves from an off-line standalone prototype to an on-line real-time system is discussed.

Happell, Nadine↗
NASA NTRS2014

The Main Pillar: Assessment of Space Weather Observational Asset Performance Supporting Nowcasting, Forecasting and Research to Operations

Space weather forecasting critically depends upon availability of timely and reliable observational data. It is therefore particularly important to understand how existing and newly planned observational assets perform during periods of severe space weather. Extreme space weather creates challenging conditions under which instrumentation and spacecraft may be impeded or in which parameters reach values that are outside the nominal observational range. This paper analyzes existing and upcoming observational capabilities for forecasting, and discusses how the findings may impact space weather research and its transition to operations. A single limitation to the assessment is lack of information provided to us on radiation monitor performance, which caused us not to fully assess (i.e., not assess short term) radiation storm forecasting. The assessment finds that at least two widely spaced coronagraphs including L4 would provide reliability for Earth-bound CMEs. Furthermore, all magnetic field measurements assessed fully meet requirements. However, with current or even with near term new assets in place, in the worst-case scenario there could be a near-complete lack of key near-real-time solar wind plasma data of severe disturbances heading toward and impacting Earth's magnetosphere. Models that attempt to simulate the effects of these disturbances in near real time or with archival data require solar wind plasma observations as input. Moreover, the study finds that near-future observational assets will be less capable of advancing the understanding of extreme geomagnetic disturbances at Earth, which might make the resulting space weather models unsuitable for transition to operations.

Extreme events↗
NASA NTRS1988

Laser transit anemometer experiences in supersonic flow

The purpose of this paper is to present examples of velocity measurements obtained in supersonic flow fields with the laser transit anemometer system. Velocity measurements of a supersonic jet exhausting in a transonic flow field, a cone boundary survey in a Mach 4 flow field, and a determination of the periodic disturbance frequencies of a sonic nozzle flow field are presented. Each of the above three cases also serves to illustrate different modes of laser transit anemometer operation. A brief description of the laser transit anemometer system is also presented.

Hunter, William W., Jr.↗
NASA NTRSDate not supplied

Crop Production In Support Of Exploration

The History of Food and Exploration, an Overview of the History of Space Food Systems, the Vision of Space Crop Production and its Role in Exploration, an Overview of Challenges and Knowledge Gaps with Reference to Recent Flight Testing on the International Space Station, Crop Production Challenges Beyond Low Earth Orbit including the Lunar Operations, the Transit Mission to Mars and Mars Surface Operations.

Crop production↗
NASA NTRS1977

Launch processing system transition from development to operation

The Launch Processing System has been under development at Kennedy Space Center since 1973. A prototype system was developed and delivered to Marshall Space Flight Center for Solid Rocket Booster checkout in July 1976. The first production hardware arrived in late 1976. The System uses a distributed computer network for command and monitoring and is supported by a dual large scale computer system for 'off line' processing. A high level of automation is anticipated for Shuttle and Payload testing and launch operations to gain the advantages of short turnaround capability, repeatability of operations, and minimization of operations and maintenance (O&M) manpower. Learning how to efficiently apply the system is our current problem. We are searching for more effective ways to convey LPS system performance characteristics from the designer to a large number of users. Once we have done this, we can realize the advantages of LPS system design.

Paul, H. C.↗
NASA NTRS1988

Spacelab data processing facility (SLDPF) Quality Assurance (QA)/Data Accounting (DA) expert systems: Transition from prototypes to operational systems

The SLDPF is responsible for the capture, quality monitoring processing, accounting, and shipment of Spacelab and/or Attached Shuttle Payloads (ASP) telemetry data to various user facilities. Expert systems will aid in the performance of the quality assurance and data accounting functions of the two SLDPF functional elements: the Spacelab Input Processing System (SIPS) and the Spacelab Output Processing System (SOPS). Prototypes were developed for each as independent efforts. The SIPS Knowledge System Prototype (KSP) used the commercial shell OPS5+ on an IBM PC/AT; the SOPS Expert System Prototype used the expert system shell CLIPS implemented on a Macintosh personal computer. Both prototypes emulate the duties of the respective QA/DA analysts based upon analyst input and predetermined mission criteria parameters, and recommended instructions and decisions governing the reprocessing, release, or holding for further analysis of data. These prototypes demonstrated feasibility and high potential for operational systems. Increase in productivity, decrease of tedium, consistency, concise historial records, and a training tool for new analyses were the principal advantages. An operational configuration, taking advantage of the SLDPF network capabilities, is under development with the expert systems being installed on SUN workstations. This new configuration in conjunction with the potential of the expert systems will enhance the efficiency, in both time and quality, of the SLDPF's release of Spacelab/AST data products.

Basile, Lisa↗
NASA NTRS1988

Spacelab data processing facility (SLDPF) quality assurance (QA)/data accounting (DA) expert systems - Transition from prototypes to operational systems

The SLDPF is responsible for the capture, quality monitoring processing, accounting, and shipment of Spacelab and/or Attached Shuttle Payloads (ASP) telemetry data to various user facilities. Expert systems will aid in the performance of the quality assurance and data accounting functions of the two SLDPF functional elements: the Spacelab Input Processing System (SIPS) and the Spacelab Output Processing System (SOPS). Prototypes were developed for each as independent efforts. The SIPS Knowledge System Prototype (KSP) used the commercial shell OPS5+ on an IBM PC/AT; the SOPS Expert System Prototype used the expert system shell CLIPS implemented on a Macintosh personal computer. Both prototypes emulate the duties of the respective QA/DA analysts based upon analyst input and predetermined mission criteria parameters, and recommended instructions and decisions governing the reprocessing, release, or holding for further analysis of data. These prototypes demonstrated feasibility and high potential for operational systems. Increase in productivity, decrease of tedium, consistency, concise historical records, and a training tool for new analyses were the principal advantages. An operational configuration, taking advantage of the SLDPF network capabilities, is under development with the expert systems being installed on SUN workstations. This new configuration in conjunction with the potential of the expert systems will enhance the efficiency, in both time and quality, of the SLDPF's release of Spacelab/AST data products.

Basile, Lisa↗
NASA NTRS2002

A Ground Systems Architecture Transition for A Distributed Operations System

The Marshall Space Flight Center (MSFC) Ground Systems Department (GSD) recently undertook an architecture change in the product line that serves the ISS program. As a result, the architecture tradeoffs between data system product lines that serve remote users versus those that serve control center flight control teams were explored extensively. This paper describes the resulting architecture that will be used in the ISS payloads program, and the resulting functional breakdown of the products that support that architecture. It also describes the lessons learned from the path that was followed, as a migration of products cause the need to reevaluate the allocation of functions across the architecture. The result is a set of innovative ground system solutions that is scalable so it can support facilities of wide-ranging sizes, from a small site up to large control centers. Effective use of system automation, custom components, design optimization for data management, data storage, data transmissions, and advanced local and wide area networking architectures, plus the effective use of Commercial-Off-The-Shelf (COTS) products, provides flexible Remote Ground System options that can be tailored to the needs of each user. This paper offers a description of the efficiency and effectiveness of the Ground Systems architectural options that have been implemented, and includes successful implementation examples and lessons learned.

Sellers, Donna↗
NASA NTRS2003

A Ground Systems Architecture Transition for a Distributed Operations System

The Marshall Space Flight Center (MSFC) Ground Systems Department (GSD) recently undertook an architecture change in the product line that serves the ISS program. As a result, the architecture tradeoffs between data system product lines that serve remote users versus those that serve control center flight control teams were explored extensively. This paper describes the resulting architecture that will be used in the International Space Station (ISS) payloads program, and the resulting functional breakdown of the products that support this architecture. It also describes the lessons learned from the path that was followed, as a migration of products cause the need to reevaluate the allocation of functions across the architecture. The result is a set of innovative ground system solutions that is scalable so it can support facilities of wide-ranging sizes, from a small site up to large control centers. Effective use of system automation, custom components, design optimization for data management, data storage, data transmissions, and advanced local and wide area networking architectures, plus the effective use of Commercial-Off-The-Shelf (COTS) products, provides flexible Remote Ground System options that can be tailored to the needs of each user. This paper offers a description of the efficiency and effectiveness of the Ground Systems architectural options that have been implemented, and includes successful implementation examples and lessons learned.

Sellers, Donna↗
NASA NTRS2018

Lessons Learned During the Transition of SORCE Science Operations to Daylight Only Operations

In July 2013, NASA's Solar Radiation and Climate Experiment experienced a battery anomaly which placed it into safemode halting all science observations. Initial attempts to recover the spacecraft to an operational configuration failed due to the reduced capacity of the battery. As the keystone mission for measuring total solar irradiance, and the cornerstone mission for measuring the solar spectral irradiance there was a strong motivation for developing a new operations concept that would allow SORCE to resume daily measurements of the Sun. The operations team faced many challenges over the next several months. For a five-day period in late 2013 the operations team was able resume science observations to cross-calibrate SORCE data with a new instrument launched in November 2013. After the cross-calibration campaign was completed a new operations concept was deployed which allowed SORCE to perform daylight only operations. In this mode of operations all non-essential components are powered off at each eclipse entry and then turned back on at sunrise. In March 2014 SORCE resumed making daily measurements of the Sun. This paper will review the events and lessons learned from the six-month recovery effort.

Spacecraft Anomaly↗