Engineering Papers⌕ Search

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.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 181 records · Page 10
All sourcesNASA NTRSDOE OSTI
NASA NTRS1991

Airborne Four-Dimensional Flight Management in a Time-based Air Traffic Control Environment

Advanced Air Traffic Control (ATC) systems are being developed which contain time-based (4D) trajectory predictions of aircraft. Airborne flight management systems (FMS) exist or are being developed with similar 4D trajectory generation capabilities. Differences between the ATC generated profiles and those generated by the airborne 4D FMS may introduce system problems. A simulation experiment was conducted to explore integration of a 4D equipped aircraft into a 4D ATC system. The NASA Langley Transport Systems Research Vehicle cockpit simulator was linked in real time to the NASA Ames Descent Advisor ATC simulation for this effort. Candidate procedures for handling 4D equipped aircraft were devised and traffic scenarios established which required time delays absorbed through speed control alone or in combination with path stretching. Dissimilarities in 4D speed strategies between airborne and ATC generated trajectories were tested in these scenarios. The 4D procedures and FMS operation were well received by airline pilot test subjects, who achieved an arrival accuracy at the metering fix of 2.9 seconds standard deviation time error. The amount and nature of the information transmitted during a time clearance were found to be somewhat of a problem using the voice radio communication channel. Dissimilarities between airborne and ATC-generated speed strategies were found to be a problem when the traffic remained on established routes. It was more efficient for 4D equipped aircraft to fly trajectories with similar, though less fuel efficient, speeds which conform to the ATC strategy. Heavy traffic conditions, where time delays forced off-route path stretching, were found to produce a potential operational benefit of the airborne 4D FMS.

Williams, David H.↗
NASA NTRS1989

Reactivation of a tin oxide-containing catalyst

A method for the reactivation of a tin oxide-containing catalyst of a CO.sub.2 laser is provided. First, the catalyst is pretreated by a standard procedure. When the catalyst experiences diminished activity during usage, the heated zone surrounding the catalyst is raised to a temperature which is the operating temperature of the laser and 400.degree. C. for approximately one hour. The catalyst is exposed to the same laser gas mixture during this period. The temperature of the heated zone is then lowered to the operating temperature of the CO.sub.2 laser.

Upchurch, Billy T.↗
NASA NTRS1977

Handbook of estimating data, factors, and procedures

Elements to be considered in estimating production costs are discussed in this manual. Guidelines, objectives, and methods for analyzing requirements and work structure are given. Time standards for specific specfic operations are listed for machining, sheet metal working, electroplating and metal treating; painting; silk screening, etching and encapsulating; coil winding; wire preparation and wiring; soldering; and the fabrication of etched circuits and terminal boards. The relation of the various elements of cost to the total cost as proposed for various programs by various contractors is compared with government estimates.

Freeman, L. M.↗
NASA NTRS1989

Executive overview and introduction to the SMAP information system life-cycle and documentation standards

An overview of the five volume set of Information System Life-Cycle and Documentation Standards is provided with information on its use. The overview covers description, objectives, key definitions, structure and application of the standards, and document structure decisions. These standards were created to provide consistent NASA-wide structures for coordinating, controlling, and documenting the engineering of an information system (hardware, software, and operational procedures components) phase by phase.

Source record↗
NASA NTRS1989

Management control and status reports documentation standard and Data Item Descriptions (DID). Volume of the information system life-cycle and documentation standards, volume 5

This is the fifth of five volumes on Information System Life-Cycle and Documentation Standards. This volume provides a well organized, easily used standard for management control and status reports used in monitoring and controlling the management, development, and assurance of informations systems and software, hardware, and operational procedures components, and related processes.

Callender, E. David↗
NASA NTRS1991

Standard formatted data units-control authority operations

The purpose of this document is to illustrate a Control Authority's (CA) possible operation. The document is an interpretation and expansion of the concept found in the CA Procedures Recommendation. The CA is described in terms of the functions it performs for the management and control of data descriptions (metadata). Functions pertaining to the organization of Member Agency Control Authority Offices (MACAOs) (e.g., creating and disbanding) are not discussed. The document also provides an illustrative operational view of a CA through scenarios describing interaction between those roles involved in collecting, controlling, and accessing registered metadata. The roles interacting with the CA are identified by their actions in requesting and responding to requests for metadata, and by the type of information exchanged. The scenarios and examples presented in this document are illustrative only. They represent possible interactions supported by either a manual or automated system. These scenarios identify requirements for an automated system. These requirements are expressed by identifying the information to be exchanged and the services that may be provided by a CA for that exchange.

Source record↗
NASA NTRS1976

A suggested classification system for standard on-orbit shuttle flight phases

The definition of standard flight segments of phases, representing flight profile components which can be combined in various sequences to satisfy particular objectives, is a necessity for simplifying operational procedures and for minimizing the cost of flight planning, software development, and training. The critical elements are (1) a greater variety of generic segment types that may be incorporated into a given flight profile, (2) a greater variability of the order in which segments may be combined to construct a particular flight profile, and (3) a greater variation of detail within a given generic segment type. All of these variations arise basically from shuttle payload characteristics. They are manifested in a number of ways, including changes in the shuttle configuration from one flight to another.

Wilson, S. W.↗
NASA NTRS1978

Development of systems and techniques for landing an aircraft using onboard television

A flight program was conducted to develop a landing technique with which a pilot could consistently and safely land a remotely piloted research vehicle (RPRV) without outside visual reference except through television. Otherwise, instrumentation was standard. Such factors as the selection of video parameters, the pilot's understanding of the television presentation, the pilot's ground cockpit environment, and the operational procedures for landing were considered. About 30 landings were necessary for a pilot to become sufficiently familiar and competent with the test aircraft to make powered approaches and landings with outside visual references only through television. When steep approaches and landings were made by remote control, the pilot's workload was extremely high. The test aircraft was used as a simulator for the F-15 RPRV, and as such was considered to be essential to the success of landing the F-15 RPRV.

Gee, S. W.↗
NASA NTRS1990

Extracting Geocoded Images From SAR Data

SAR imagery automatically put onto map in desired projection. MAPJTC designed to rectify and transform standard image output of digital synthetic-aperture-radar (SAR) correlator into image registered with geocoded map, without manual tiepointing or other interaction with operator. Reduces procedure to two one-dimensional passes, thereby saving computer time. Program written in FORTRAN (84 percent), APAL (2 percent), and MAXL (14 percent).

Curlander, John C.↗
NASA NTRS1996

Manufacturing of Igniters for NHB 8060.1 Testing

The purpose of this WJI is to incorporate a standard procedure to prepare, certify, and ship standard NHB 8060.1B and NHB 8060.1C igniters for flammability testing and to update LJI-320-35-18. The operations are divided into five parts as follows: A. Preparing the igniter mix; B. Extruding the igniters; C. Curing, cutting, and weighing the igniters; D. Certifying the igniters and E. Packaging, storing, and shipping the igniters

Williams, James↗
NASA NTRS1976

A methodology for small scale rural land use mapping in semi-arid developing countries using orbital imagery. Part 5: Experimental and operational techniques of mapping land use

The author has identified the following significant results. Scope of the preprocessing techniques was restricted to standard material from the EROS Data Center accompanied by some enlarging procedures and the use of the diazo process. Investigation has shown that the most appropriate sampling strategy for this study is the stratified random technique. A viable sampling procedure, together with a method for determining minimum number of sample points in order to test results of any interpretation are presented.

Vangenderen, J. L.↗
NASA NTRS2014

Autonomous Real Time Requirements Tracing

One of the more challenging aspects of software development is the ability to verify and validate the functional software requirements dictated by the Software Requirements Specification (SRS) and the Software Detail Design (SDD). Insuring the software has achieved the intended requirements is the responsibility of the Software Quality team and the Software Test team. The utilization of Timeliner-TLX(sup TM) Auto-Procedures for relocating ground operations positions to ISS automated on-board operations has begun the transition that would be required for manned deep space missions with minimal crew requirements. This transition also moves the auto-procedures from the procedure realm into the flight software arena and as such the operational requirements and testing will be more structured and rigorous. The autoprocedures would be required to meet NASA software standards as specified in the Software Safety Standard (NASASTD- 8719), the Software Engineering Requirements (NPR 7150), the Software Assurance Standard (NASA-STD-8739) and also the Human Rating Requirements (NPR-8705). The Autonomous Fluid Transfer System (AFTS) test-bed utilizes the Timeliner-TLX(sup TM) Language for development of autonomous command and control software. The Timeliner- TLX(sup TM) system has the unique feature of providing the current line of the statement in execution during real-time execution of the software. The feature of execution line number internal reporting unlocks the capability of monitoring the execution autonomously by use of a companion Timeliner-TLX(sup TM) sequence as the line number reporting is embedded inside the Timeliner-TLX(sup TM) execution engine. This negates I/O processing of this type data as the line number status of executing sequences is built-in as a function reference. This paper will outline the design and capabilities of the AFTS Autonomous Requirements Tracker, which traces and logs SRS requirements as they are being met during real-time execution of the targeted system. It is envisioned that real time requirements tracing will greatly assist the movement of autoprocedures to flight software enhancing the software assurance of auto-procedures and also their acceptance as reliable commanders

Plattsmier, George I.↗
NASA NTRS2014

Autonomous Real Time Requirements Tracing

One of the more challenging aspects of software development is the ability to verify and validate the functional software requirements dictated by the Software Requirements Specification (SRS) and the Software Detail Design (SDD). Insuring the software has achieved the intended requirements is the responsibility of the Software Quality team and the Software Test team. The utilization of Timeliner-TLX(sup TM) Auto- Procedures for relocating ground operations positions to ISS automated on-board operations has begun the transition that would be required for manned deep space missions with minimal crew requirements. This transition also moves the auto-procedures from the procedure realm into the flight software arena and as such the operational requirements and testing will be more structured and rigorous. The autoprocedures would be required to meet NASA software standards as specified in the Software Safety Standard (NASASTD- 8719), the Software Engineering Requirements (NPR 7150), the Software Assurance Standard (NASA-STD-8739) and also the Human Rating Requirements (NPR-8705). The Autonomous Fluid Transfer System (AFTS) test-bed utilizes the Timeliner-TLX(sup TM) Language for development of autonomous command and control software. The Timeliner-TLX(sup TM) system has the unique feature of providing the current line of the statement in execution during real-time execution of the software. The feature of execution line number internal reporting unlocks the capability of monitoring the execution autonomously by use of a companion Timeliner-TLX(sup TM) sequence as the line number reporting is embedded inside the Timeliner-TLX(sup TM) execution engine. This negates I/O processing of this type data as the line number status of executing sequences is built-in as a function reference. This paper will outline the design and capabilities of the AFTS Autonomous Requirements Tracker, which traces and logs SRS requirements as they are being met during real-time execution of the targeted system. It is envisioned that real time requirements tracing will greatly assist the movement of autoprocedures to flight software enhancing the software assurance of auto-procedures and also their acceptance as reliable commanders.

Plattsmier, George↗
NASA NTRS1977

The impact of satellite soundings upon the NMC analysis and forecast system

The importance of satellite-derived soundings on National Meteorological Center weather analysis and forecast was studied by comparing summertime DST (Aug. 18-Sept. 4, 1975) forecasts generated by analyses with and without both the operational VTPR soundings from NOAA-4 and the experimental soundings derived from the infrared and microwave instruments aboard Nimbus-6. Objective and subjective procedures, including evaluation of standard skill scores and judgment by skilled synopticians, was used to evaluate the importance of satellite data. The investigation shows that satellite data do not aid numerical weather prediction in the Northern Hemisphere.

Tracton, M. S.↗
NASA NTRS2009

Flammability, Offgassing, and Compatibility Requirements and Test Procedures

This Interim Standard establishes requirements for evaluation, testing, and selection of materials that are intended for use in space vehicles, associated Ground Support Equipment (GSE), and facilities used during assembly, test, and flight operations. Included are requirements, criteria, and test methods for evaluating the flammability, offgassing, and compatibility of materials.

Source record↗
NASA NTRS1981

A software system for emission spectrometry

A computer system was developed for an emission spectrometry facility consisting of a direct current (DC) argon arc spectrograph optically coupled to an inductively coupled plasma multichannel spectrometer. Custom hardware and software were designed to control analytical functions and perform data acquisition. The software system was designed to make operation of the facility simple for routine operation and flexible for research and development. Special software was written to collect data under controlled conditions to characterize and monitor system response. One sequence collects intensity versus time data on all channels and displays the data graphically. These profiles are useful in studying the effects of operating parameters on measurement precision. Another special sequence performs calibration using a spline curve fit procedure. Routines were also written to measure dark currents and signals from a standard tungsten halogen lamp mounted in place of the DC arc. For quality control purposes, histories of these values are kept and monitored for excess scatter or drift.

Auping, J. V.↗
NASA NTRS2014

Human Integration Design Processes (HIDP)

The purpose of the Human Integration Design Processes (HIDP) document is to provide human-systems integration design processes, including methodologies and best practices that NASA has used to meet human systems and human rating requirements for developing crewed spacecraft. HIDP content is framed around human-centered design methodologies and processes in support of human-system integration requirements and human rating. NASA-STD-3001, Space Flight Human-System Standard, is a two-volume set of National Aeronautics and Space Administration (NASA) Agency-level standards established by the Office of the Chief Health and Medical Officer, directed at minimizing health and performance risks for flight crews in human space flight programs. Volume 1 of NASA-STD-3001, Crew Health, sets standards for fitness for duty, space flight permissible exposure limits, permissible outcome limits, levels of medical care, medical diagnosis, intervention, treatment and care, and countermeasures. Volume 2 of NASASTD- 3001, Human Factors, Habitability, and Environmental Health, focuses on human physical and cognitive capabilities and limitations and defines standards for spacecraft (including orbiters, habitats, and suits), internal environments, facilities, payloads, and related equipment, hardware, and software with which the crew interfaces during space operations. The NASA Procedural Requirements (NPR) 8705.2B, Human-Rating Requirements for Space Systems, specifies the Agency's human-rating processes, procedures, and requirements. The HIDP was written to share NASA's knowledge of processes directed toward achieving human certification of a spacecraft through implementation of human-systems integration requirements. Although the HIDP speaks directly to implementation of NASA-STD-3001 and NPR 8705.2B requirements, the human-centered design, evaluation, and design processes described in this document can be applied to any set of human-systems requirements and are independent of reference missions. The HIDP is a reference document that is intended to be used during the development of crewed space systems and operations to guide human-systems development process activities.

Boyer, Jennifer↗
NASA NTRS1976

Simulation studies of air transport operational problems

An experimental evaluation of the monitored approach procedure for conducting low visibility instrument approaches is described. Four airline crews each flew 16 approaches using the monitored procedure and 16 using a modified standard procedure in a DC-10 simulator under various conditions of visibility, wind shear and turbulence, and radar vectoring scenarios. In terms of system measures of aircrew performance, no major differences were found. Pilot opinion data indicate that there are some desirable characteristics of the monitored procedure, particularly with reference to the increased role of the flight engineer in conducting low visibility approaches. Rationale for developing approach procedures is discussed.

Lauber, J. K.↗