SEARCH · Engineering Papers

Results for “standard operating procedure”

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 109 records · Page 6

All sources NASA NTRS DOE OSTI

NASA NTRSDate not supplied

Evaluating the Use of High-Fidelity Simulator Research Methods to Study Airline Flight Crew Resilience

As it evolves, aviation will continue to require integration of a wide range of safety systems and practices, some of which are already in place and others that are yet to be developed. New concepts in system safety thinking have emerged to consider not only what may go wrong, but also what can be learned when things go right during commercial flight operations. Taken together, these complementary perspectives form a more comprehensive approach to systemsafety thinking that can help to recognize and preserve the resilient performance capabilities currently provided by humans. A need exists, however, for research methods to enable better understanding of the human contributions to aviation safety. NASA’s System-Wide Safety Project supports research on using flight simulation methods to study operator resilience and safety-producing behaviors. Building on prior NASA efforts investigating procedural non-adherences during area navigation standard terminal route arrivals, a high-fidelity commercial aviation line operational simulation (LOS) experiment has been designed to study how flight crews anticipate, monitor for, respond to, and learn from expected and unexpected disturbances during these operations. A diverse set of LOS scenarios were developed to simulate highly realistic, complex, but routinely encountered operational situations. Each scenario provided multiple opportunities to collect data on how flight crews manage threats and errors, as well as novel opportunities to observe resilient and safety-producing behaviors. The experimental design, implications for the study of safety-producing behaviors using simulation, and considerations for airline pilot training will be discussed.

Chad L Stephens↗

NASA NTRS2022

PAAV Concept Document

The Pathfinding for Airspace with Autonomous Vehicles (PAAV) Concept Document, version 1.0, lays out the key challenges and potential solutions for the use of uncrewed aircraft (UA) technology for future regional air cargo operations. The challenges and solutions described in this document were informed by communications with the UA industry community (e.g., RTCA, the Federal Aviation Administration, and regional air cargo business operators), as well as the PAAV team’s research activities during the last two years including four tabletop exercises, a human-in-the-loop simulation study, a numerical simulation study, a functional allocation study, and flight data analysis (Appendix A). This document first describes the expected operational context of PAAV (Section 2), such as the flight mission, baseline UAS components, nominal operations, m:N operations (i.e., "m" remote pilots per "N" aircraft), and off-nominal operations. This context sets the scope for the PAAV concept development work. PAAV concept development assumes that UA operations will be increasingly autonomous. Thus, near- and far-term assumptions are defined (Section 3). PAAV identified seven key challenges for UA operations (Section 4): - Flight route planning - Separation and flow management - Traffic pattern integration - Contingency management - Taxi, takeoff, and landing - m:N operations - Communications operations The following 13 potential solutions to these challenges are then described (Section 5): - Scalable communications architecture - Data link - Designated UAS corridors - Crew planning for m:N operations - Flight route optimization - Traffic load-level control - Trajectory solutions with data link - Automated hazard avoidance for m:N operations - Traffic pattern integration (TPI) tool - Standard lost command and control (C2) link (LC2L) procedures - Automated hazard avoidance under LC2L - Auto-taxi, auto-takeoff, and auto-land - Ground control station (GCS) user interface for m:N operations The document attempts to link each of these solutions to one or more of the challenge areas. Novel solutions involving numerous automation technologies are needed to mitigate traffic and airspace management challenges, especially for realizing m:N operations and ensuring safety under LC2L conditions. The purpose of this document is to help understand alternatives and tradeoffs among potential solutions and provide a foundation for a cohesive PAAV concept that will be described and refined in subsequent concept versions.

Unmanned aircraft, uncrewed aircraft, regional air↗

NASA NTRS2011

JSC Design and Procedural Standards, JSC-STD-8080

This document provides design and procedural requirements appropriate for inclusion in specifications for any human spaceflight program, project, spacecraft, system, or end item. The term "spacecraft" as used in the standards includes launch vehicles, orbital vehicles, non-terrestrial surface vehicles, and modules. The standards are developed and maintained as directed by Johnson Space Center (JSC) Policy Directive JPD 8080.2, JSC Design and Procedural Standards for Human Space Flight Equipment. The Design and Procedural Standards contained in this manual represent human spacecraft design and operational knowledge applicable to a wide range of spaceflight activities. These standards are imposed on JSC human spaceflight equipment through JPD 8080.2. Designers shall comply with all design standards applicable to their design effort.

Punch, Danny T.↗

NASA NTRS1989

Information system life-cycle and documentation standards, volume 1

The Software Management and Assurance Program (SMAP) Information System Life-Cycle and Documentation Standards Document describes the Version 4 standard information system life-cycle in terms of processes, products, and reviews. The description of the products includes detailed documentation standards. The standards in this document set can be applied to the life-cycle, i.e., to each phase in the system's development, and to the documentation of all NASA information systems. This provides consistency across the agency as well as visibility into the completeness of the information recorded. An information system is software-intensive, but consists of any combination of software, hardware, and operational procedures required to process, store, or transmit data. This document defines a standard life-cycle model and content for associated documentation.

Callender, E. David↗

NASA NTRS1995

Geophysical data analysis and visualization using the Grid Analysis and Display System

Several problems posed by the rapidly growing volume of geophysical data are described, and a selected set of existing solutions to these problems is outlined. A recently developed desktop software tool called the Grid Analysis and Display System (GrADS) is presented. The GrADS' user interface is a natural extension of the standard procedures scientists apply to their geophysical data analysis problems. The basic GrADS operations have defaults that naturally map to data analysis actions, and there is a programmable interface for customizing data access and manipulation. The fundamental concept of the GrADS' dimension environment, which defines both the space in which the geophysical data reside and the 'slice' of data which is being analyzed at a given time, is expressed The GrADS' data storage and access model is described. An argument is made in favor of describable data formats rather than standard data formats. The manner in which GrADS users may perform operations on their data and display the results is also described. It is argued that two-dimensional graphics provides a powerful quantitative data analysis tool whose value is underestimated in the current development environment which emphasizes three dimensional structure modeling.

Doty, Brian E.↗

NASA NTRS2005

Considerations in the Integration of Small Aircraft Transportation System Higher Volume Operations (SATSHVO) in the National Airspace System (NAS)

The Small Aircraft Transportation System Higher Volume Operations (SATS HVO) concept holds the promise for increased efficiency and throughput at many of the nations under-used airports. This concept allows for concurrent operations at uncontrolled airports that under today s procedures are restricted to one arrival or one departure operation at a time, when current-day IFR separation standards are applied. To allow for concurrent operations, SATS HVO proposes several fundamental changes to today's system. These changes include: creation of dedicated airspace, development of new procedures and communications (phraseologies), and assignment of roles and responsibilities for pilots and controllers, among others. These changes would affect operations on the airborne side (pilot) as well as the groundside (controller and air traffic flow process). The focus of this paper is to discuss some of the issues and potential problems that have been considered in the development of the SATS HVO concept, in particular from the ground side perspective. Reasonable solutions to the issues raised here have been proposed by the SATS HVO team, and are discussed in this paper.

Lohr, Gary W.↗

NASA NTRS1989

Assurance specification documentation standard and Data Item Descriptions (DID). Volume of the information system life-cycle and documentation standards, volume 4

This is the fourth of five volumes on Information System Life-Cycle and Documentation Standards. This volume provides a well organized, easily used standard for assurance documentation for information systems and software, hardware, and operational procedures components, and related processes. The specifications are developed in conjunction with the corresponding management plans specifying the assurance activities to be performed.

Callender, E. David↗

NASA NTRS1993

Piloting Vertical Flight Aircraft: A Conference on Flying Qualities and Human Factors

This document contains papers from a specialists' meeting entitled "Piloting Vertical Flight Aircraft. A Conference on Flying Qualities and Human Factors." The conference was co-sponsored by the American Helicopter Society--San Francisco Bay Chapter, and the NASA Ames Research Center. It was held January 20-22, 1993 at the Sheraton Hotel Fisherman's Wharf, San Francisco, California. Vertical flight aircraft, including helicopters and a variety of Vertical Takeoff and Landing (VTOL) concepts, place unique requirements on human perception, control, and performance for the conduct of their design missions. The intent of this conference was to examine, for these vehicles, advances in: (1) design of flight control systems for ADS-33C standards; (2) assessment of human factors influences of cockpit displays and operational procedures; (3) development of VTOL design and operational criteria; and (4) development of theoretical methods or models for predicting pilot-vehicle performance and mission suitability. Recognizing that human capabilities and limitations form an integral aspect of the operations for these classes of vehicles, a secondary goal of the conference was to provide an initial venue for enhanced interaction between human factors and handling qualities specialists.

Helicopter↗

NASA NTRS2006

An Approach to Reliability Testing of Microcircuits at Cryogenic Conditions

This viewgraph presentation reviews an approach to testing microcircuits at cryogenic temperatures. Standard testing procedures are not adequate to test microcircuits that are to operate at cryogenic temperatures. It is therefore necessary to perform analysis of operation conditions and reliability conditions for planning qualification testing of microcircuits at cryogenic temperatures. The major degradations for microcircuits operating at low temperatures depend on the number of switching cycles rather than on the duration of part operation. Therefore instead of accelerating degradation of the parts by increasing the level of stress, the possibility of which is very limited at cryogenic temperatures, the reliability testing can be based on the number of switching cycles.

Teverovsky, Alexander↗

NASA NTRS2020

Adapting Apollo-Era Instrumentation for Cold Sample Processing While Maintaining Curatorial Standard Practices

The goal of the Apollo Next Generation Sample Analysis (ANGSA) Program is to study “specially curated samples,” that is, unstudied Apollo samples that have been preserved under unique conditions. A subset of the funded ANGSA work includes the study of Apollo samples stored under cold conditions since their return from the Moon. Ongoing ANGSA processing and future returned samples require cold curation strategies to preserve the integrity of organic and other temperature-sensitive constituents within those samples. Standard Apollo curation processing hardware and procedures are designed for room temperature operations, not cold conditions. This abstract details the major modifications of a heritage lunar cabinet in preparation for the first cold curation processing at Johnson Space Center. Future publications will provide greater detail on the low temperature materials and operation procedures. This work not only supports Apollo but also future cold sample return missions.

Amick, Cecilia L.↗

NASA NTRS1996

Quality and Control of Water Vapor Winds

Water vapor imagery from the geostationary satellites such as GOES, Meteosat, and GMS provides synoptic views of dynamical events on a continual basis. Because the imagery represents a non-linear combination of mid- and upper-tropospheric thermodynamic parameters (three-dimensional variations in temperature and humidity), video loops of these image products provide enlightening views of regional flow fields, the movement of tropical and extratropical storm systems, the transfer of moisture between hemispheres and from the tropics to the mid- latitudes, and the dominance of high pressure systems over particular regions of the Earth. Despite the obvious larger scale features, the water vapor imagery contains significant image variability down to the single 8 km GOES pixel. These features can be quantitatively identified and tracked from one time to the next using various image processing techniques. Merrill et al. (1991), Hayden and Schmidt (1992), and Laurent (1993) have documented the operational procedures and capabilities of NOAA and ESOC to produce cloud and water vapor winds. These techniques employ standard correlation and template matching approaches to wind tracking and use qualitative and quantitative procedures to eliminate bad wind vectors from the wind data set. Techniques have also been developed to improve the quality of the operational winds though robust editing procedures (Hayden and Veldon 1991). These quality and control approaches have limitations, are often subjective, and constrain wind variability to be consistent with model derived wind fields. This paper describes research focused on the refinement of objective quality and control parameters for water vapor wind vector data sets. New quality and control measures are developed and employed to provide a more robust wind data set for climate analysis, data assimilation studies, as well as operational weather forecasting. The parameters are applicable to cloud-tracked winds as well with minor modifications. The improvement in winds through use of these new quality and control parameters is measured without the use of rawinsonde or modeled wind field data and compared with other approaches.

Jedlovec, Gary J.↗

NASA NTRS1990

Automated procedure execution for space vehicle autonomous control

Increased operational autonomy and reduced operating costs have become critical design objectives in next-generation NASA and DoD space programs. The objective is to develop a semi-automated system for intelligent spacecraft operations support. The Spacecraft Operations and Anomaly Resolution System (SOARS) is presented as a standardized, model-based architecture for performing High-Level Tasking, Status Monitoring and automated Procedure Execution Control for a variety of spacecraft. The particular focus is on the Procedure Execution Control module. A hierarchical procedure network is proposed as the fundamental means for specifying and representing arbitrary operational procedures. A separate procedure interpreter controls automatic execution of the procedure, taking into account the current status of the spacecraft as maintained in an object-oriented spacecraft model.

Broten, Thomas A.↗

NASA NTRS1992

The need for GPS standardization

A desirable and necessary step for improvement of the accuracy of Global Positioning System (GPS) time comparisons is the establishment of common GPS standards. For this reason, the CCDS proposed the creation of a special group of experts with the objective of recommending procedures and models for operational time transfer by GPS common-view method. Since the announcement of the implementation of Selective Availability at the end of last spring, action has become much more urgent and this CCDS Group on GPS Time Transfer Standards has now been set up. It operates under the auspices of the permanent CCDS Working Group on TAI and works in close cooperation with the Sub-Committee on Time of the Civil GPS Service Interface Committee (CGSIC). Taking as an example the implementation of SA during the first week of July 1991, this paper illustrates the need to develop urgently at least two standardized procedures in GPS receiver software: monitoring GPS tracks with a common time scale and retaining broadcast ephemeris parameters throughout the duration of a track. Other matters requiring action are the adoption of common models for atmospheric delay, a common approach to hardware design and agreement about short-term data processing. Several examples of such deficiencies in standardization are presented.

W. Lewandowski↗

NASA NTRS2011

Cryogenic Quenching Process for Electronic Part Screening

The use of electronic parts at cryogenic temperatures (less than 100 C) for extreme environments is not well controlled or developed from a product quality and reliability point of view. This is in contrast to the very rigorous and well-documented procedures to qualify electronic parts for mission use in the 55 to 125 C temperature range. A similarly rigorous methodology for screening and evaluating electronic parts needs to be developed so that mission planners can expect the same level of high reliability performance for parts operated at cryogenic temperatures. A formal methodology for screening and qualifying electronic parts at cryogenic temperatures has been proposed. The methodology focuses on the base physics of failure of the devices at cryogenic temperatures. All electronic part reliability is based on the bathtub curve, high amounts of initial failures (infant mortals), a long period of normal use (random failures), and then an increasing number of failures (end of life). Unique to this is the development of custom screening procedures to eliminate early failures at cold temperatures. The ability to screen out defects will specifically impact reliability at cold temperatures. Cryogenic reliability is limited by electron trap creation in the oxide and defect sites at conductor interfaces. Non-uniform conduction processes due to process marginalities will be magnified at cryogenic temperatures. Carrier mobilities change by orders of magnitude at cryogenic temperatures, significantly enhancing the effects of electric field. Marginal contacts, impurities in oxides, and defects in conductor/conductor interfaces can all be magnified at low temperatures. The novelty is the use of an ultra-low temperature, short-duration quenching process for defect screening. The quenching process is designed to identify those defects that will precisely (and negatively) affect long-term, cryogenic part operation. This quenching process occurs at a temperature that is at least 25 C colder than the coldest expected operating temperature. This quenching process is the opposite of the standard burn-in procedure. Normal burn-in raises the temperature (and voltage) to activate quickly any possible manufacturing defects remaining in the device that were not already rejected at a functional test step. The proposed inverse burn-in or quenching process is custom-tailored to the electronic device being used. The doping profiles, materials, minimum dimensions, interfaces, and thermal expansion coefficients are all taken into account in determining the ramp rate, dwell time, and temperature.

Sheldon, Douglas J.↗

NASA NTRS1974

Parametric study of STOL short-haul engine cycles and operational techniques to minimize community noise impact

The effect of aircraft operational techniques in the terminal area on community noise impact of future short-haul aircraft was investigated. These operational techniques affected altitude, flap retraction rate, thrust cutback altitude, amount of thrust cutback, and amount of turning. During landing the parameters varied were glide slope angle, change in slope angle (two segment approach), and flap extension rate. One mechanical-flap (MF) aircraft and one externally-blown-flap (EBF) aircraft were used to study by noise impact at four U.S. airports, Hanscom Field (Boston); Washington National; Midway (Chicago); and Orange County (California). With the exception of Washington National (DCA), the study showed that a reduction of approximately 40 percent in the number of people highly annoyed (as defined in the study) can be obtained by using these operational techniques. At DCA the number of people highly annoyed using the standard procedure was quite low, but it is significant that the minimumimpact case for Runway 36 reduced the number of people highly annoyed to zero using a power cutback and a turning departure path. The evaluation procedures and methodology developed in this study represents an advance in acoustical state-of-the-art and should provide an effective and useful tool for determining aircraft noise impact upon the airport community.

Source record↗

NASA NTRS1979

A rocket ozonesonde for geophysical research and satellite intercomparison

The in-situ rocketsonde for ozone profile measurements developed and flown for geophysical research and satellite comparison is reviewed. The measurement principle involves the chemiluminescence caused by ambient ozone striking a detector and passive pumping as a means of sampling the atmosphere as the sonde descends through the atmosphere on a parachute. The sonde is flown on a meteorological sounding rocket, and flight data are telemetered via the standard meteorological GMD ground receiving system. The payload operation, sensor performance, and calibration procedures simulating flight conditions are described. An error analysis indicated an absolute accuracy of about 12 percent and a precision of about 8 percent. These are combined to give a measurement error of 14 percent.

Hilsenrath, E.↗

NASA NTRS1989

Shuttle remote manipulator system mission preparation and operations

The preflight planning, analysis, procedures development, and operations support for the Space Transportation System payload deployment and retrieval missions utilizing the Shuttle Remote Manipulator System are summarized. Analysis of the normal operational loads and failure induced loads and motion are factored into all procedures. Both the astronaut flight crews and the Mission Control Center flight control teams receive considerable training for standard and mission specific operations. The real time flight control team activities are described.

Smith, Ernest E., Jr.↗

NASA NTRS2007

NASA's Software Safety Standard

NASA relies more and more on software to control, monitor, and verify its safety critical systems, facilities and operations. Since the 1960's there has hardly been a spacecraft launched that does not have a computer on board that will provide command and control services. There have been recent incidents where software has played a role in high-profile mission failures and hazardous incidents. For example, the Mars Orbiter, Mars Polar Lander, the DART (Demonstration of Autonomous Rendezvous Technology), and MER (Mars Exploration Rover) Spirit anomalies were all caused or contributed to by software. The Mission Control Centers for the Shuttle, ISS, and unmanned programs are highly dependant on software for data displays, analysis, and mission planning. Despite this growing dependence on software control and monitoring, there has been little to no consistent application of software safety practices and methodology to NASA's projects with safety critical software. Meanwhile, academia and private industry have been stepping forward with procedures and standards for safety critical systems and software, for example Dr. Nancy Leveson's book Safeware: System Safety and Computers. The NASA Software Safety Standard, originally published in 1997, was widely ignored due to its complexity and poor organization. It also focused on concepts rather than definite procedural requirements organized around a software project lifecycle. Led by NASA Headquarters Office of Safety and Mission Assurance, the NASA Software Safety Standard has recently undergone a significant update. This new standard provides the procedures and guidelines for evaluating a project for safety criticality and then lays out the minimum project lifecycle requirements to assure the software is created, operated, and maintained in the safest possible manner. This update of the standard clearly delineates the minimum set of software safety requirements for a project without detailing the implementation for those requirements. This allows the projects leeway to meet these requirements in many forms that best suit a particular project's needs and safety risk. In other words, it tells the project what to do, not how to do it. This update also incorporated advances in the state of the practice of software safety from academia and private industry. It addresses some of the more common issues now facing software developers in the NASA environment such as the use of Commercial-Off-the-Shelf Software (COTS), Modified OTS (MOTS), Government OTS (GOTS), and reused software. A team from across NASA developed the update and it has had both NASA-wide internal reviews by software engineering, quality, safety, and project management. It has also had expert external review. This presentation and paper will discuss the new NASA Software Safety Standard, its organization, and key features. It will start with a brief discussion of some NASA mission failures and incidents that had software as one of their root causes. It will then give a brief overview of the NASA Software Safety Process. This will include an overview of the key personnel responsibilities and functions that must be performed for safety-critical software.

Ramsay, Christopher M.↗