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 127 records · Page 7

All sources NASA NTRS DOE OSTI

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

NASA NTRS1986

Local flow management/profile descent algorithm. Fuel-efficient, time-controlled profiles for the NASA TSRV airplane

The Local Flow Management/Profile Descent (LFM/PD) algorithm designed for the NASA Transport System Research Vehicle program is described. The algorithm provides fuel-efficient altitude and airspeed profiles consistent with ATC restrictions in a time-based metering environment over a fixed ground track. The model design constraints include accommodation of both published profile descent procedures and unpublished profile descents, incorporation of fuel efficiency as a flight profile criterion, operation within the performance capabilities of the Boeing 737-100 airplane with JT8D-7 engines, and conformity to standard air traffic navigation and control procedures. Holding and path stretching capabilities are included for long delay situations.

Groce, J. L.↗

NASA NTRS1975

The design, development, fabrication and testing of two (2) Non-Spin Platforms, (NSP)

The non spin platform is a means for achieving the very low acceleration requirements for cost effective space processing experiments on research rocket flights. These platforms have a low initial cost, are re-usable and have extremely low refurbishment cost. In order to attain this goal, commercially available components were used and only the necessary quality control standards were imposed. A detailed system description, the very few design problems encountered, the operational procedures (both pre-flight and post-flight), and the maintenance requirements are described.

Source record↗

NASA NTRS1982

Possible safety hazards associated with the operation of the 0.3-m transonic cryogenic tunnel at the NASA Langley Research Center

The 0.3 m Transonic Cryogenic Tunnel (TCT) at the NASA Langley Research Center was built in 1973 as a facility intended to be used for no more than 60 hours in order to verify the validity of the cryogenic wind tunnel concept at transonic speeds. The role of the 0.3 m TCT has gradually changed until now, after over 3000 hours of operation, it is classified as a major NASA research facility and, under the administration of the Experimental Techniques Branch, it is used extensively for the testing of airfoils at high Reynolds numbers and for the development of various technologies related to the efficient operation and use of cryogenic wind tunnels. The purpose of this report is to document the results of a recent safety analysis of the 0.3 m TCT facility. This analysis was made as part of an on going program with the Experimental Techniques Branch designed to ensure that the existing equipment and current operating procedures of the 0.3 m TCT facility are acceptable in terms of today's standards of safety for cryogenic systems.

Webster, T. J.↗

NASA NTRS1990

NASTRAN migration to UNIX

COSMIC/NASTRAN, as it is supported and maintained by COSMIC, runs on four main-frame computers - CDC, VAX, IBM and UNIVAC. COSMIC/NASTRAN on other computers, such as CRAY, AMDAHL, PRIME, CONVEX, etc., is available commercially from a number of third party organizations. All these computers, with their own one-of-a-kind operating systems, make NASTRAN machine dependent. The job control language (JCL), the file management, and the program execution procedure of these computers are vastly different, although 95 percent of NASTRAN source code was written in standard ANSI FORTRAN 77. The advantage of the UNIX operating system is that it has no machine boundary. UNIX is becoming widely used in many workstations, mini's, super-PC's, and even some main-frame computers. NASTRAN for the UNIX operating system is definitely the way to go in the future, and makes NASTRAN available to a host of computers, big and small. Since 1985, many NASTRAN improvements and enhancements were made to conform to the ANSI FORTRAN 77 standards. A major UNIX migration effort was incorporated into COSMIC NASTRAN 1990 release. As a pioneer work for the UNIX environment, a version of COSMIC 89 NASTRAN was officially released in October 1989 for DEC ULTRIX VAXstation 3100 (with VMS extensions). A COSMIC 90 NASTRAN version for DEC ULTRIX DECstation 3100 (with RISC) is planned for April 1990 release. Both workstations are UNIX based computers. The COSMIC 90 NASTRAN will be made available on a TK50 tape for the DEC ULTRIX workstations. Previously in 1988, an 88 NASTRAN version was tested successfully on a SiliconGraphics workstation.

Chan, Gordon C.↗

NASA NTRS1986

Operation of the HP2250 with the HP9000 series 200 using PASCAL 3.0

A computer program has been written to provide an interface between the HP Series 200 desktop computers, operating under HP Standard Pascal 3.0, and the HP2250 Data Acquisition and Control System. Pascal 3.0 for the HP9000 desktop computer gives a number of procedures for handling bus communication at various levels. It is necessary, however, to reach the lowest possible level in Pascal to handle the bus protocols required by the HP2250. This makes programming extremely complex since these protocols are not documented. The program described solves those problems and allows the user to immediately program, simply and efficiently, any measurement and control language (MCL/50) application with a few procedure calls. The complete set of procedures is available on a 5 1/4 inch diskette from Cosmic. Included in this group of procedures is an Exerciser which allows the user to exercise his HP2250 interactively. The exerciser operates in a fashion similar to the Series 200 operating system programs, but is adapted to the requirements of the HP2250. The programs on the diskette and the user's manual assume the user is acquainted with both the MCL/50 programming language and HP Standard Pascal 3.0 for the HP series 200 desktop computers.

Perry, John↗

NASA NTRS1972

Concurrent variation of response bias and sensitivity in an operant-psychophysical test.

The yes-no signal detection procedure was applied to a single-response operant paradigm in which rats discriminated between a standard auditory intensity and attenuated comparison values. The payoff matrix was symmetrical (with reinforcing brain stimulation for correct detections and brief time-out for errors), but signal probability and intensity differences were varied to generate a family of isobias and isosensitivity functions. The d' parameter remained fairly constant across a wide range of bias levels. Isobias functions deviated from a strict matching strategy as discrimination difficulty increased, although an orderly relation was maintained between signal probability value and the degree and direction of response bias.

Terman, M.↗

NASA NTRS1987

Comparison of two procedures for predicting rocket engine nozzle performance

Two nozzle performance prediction procedures which are based on the standardized JANNAF methodology are presented and compared for four rocket engine nozzles. The first procedure required operator intercedence to transfer data between the individual performance programs. The second procedure is more automated in that all necessary programs are collected into a single computer code, thereby eliminating the need for data reformatting. Results from both procedures show similar trends but quantitative differences. Agreement was best in the predictions of specific impulse and local skin friction coefficient. Other compared quantities include characteristic velocity, thrust coefficient, thrust decrement, boundary layer displacement thickness, momentum thickness, and heat loss rate to the wall. Effects of wall temperature profile used as an input to the programs was investigated by running three wall temperature profiles. It was found that this change greatly affected the boundary layer displacement thickness and heat loss to the wall. The other quantities, however, were not drastically affected by the wall temperature profile change.

Davidian, Kenneth J.↗

NASA NTRS1987

Comparison of two procedures for predicting rocket engine nozzle performance

Davidian, Kenneth J.↗

NASA NTRS1995

Evaluation of Winter Operational Runway Friction Measurement Equipment, Procedures, and Research

This document produced by the FAA/Industry Winter Runway Friction Measurement and Reporting Working Group, is designed to provide an overview of current information on the present guidance, practices, and procedures for reporting runway pavement surface conditions during winter operations at airports. It contains recommendations on the desirability of providing the best procedural consistency and standardization and discusses the available means to implement the guidance that will result in improved aviation safety at airports during hazardous winter conditions.

Source record↗

NASA NTRS2006

Control of Technology Transfer at JPL

Controlled Technology: 1) Design: preliminary or critical design data, schematics, technical flow charts, SNV code/diagnostics, logic flow diagrams, wirelist, ICDs, detailed specifications or requirements. 2) Development: constraints, computations, configurations, technical analyses, acceptance criteria, anomaly resolution, detailed test plans, detailed technical proposals. 3) Production: process or how-to: assemble, operated, repair, maintain, modify. 4) Manufacturing: technical instructions, specific parts, specific materials, specific qualities, specific processes, specific flow. 5) Operations: how-to operate, contingency or standard operating plans, Ops handbooks. 6) Repair: repair instructions, troubleshooting schemes, detailed schematics. 7) Test: specific procedures, data, analysis, detailed test plan and retest plans, detailed anomaly resolutions, detailed failure causes and corrective actions, troubleshooting, trended test data, flight readiness data. 8) Maintenance: maintenance schedules and plans, methods for regular upkeep, overhaul instructions. 9) Modification: modification instructions, upgrades kit parts, including software

Jet Propulsion Laboratory (JPL)↗

NASA NTRS2014

Target Trailing With Safe Navigation With Colregs for Maritime Autonomous Surface Vehicles

Systems and methods for operating autonomous waterborne vessels in a safe manner. The systems include hardware for identifying the locations and motions of other vessels, as well as the locations of stationary objects that represent navigation hazards. By applying a computational method that uses a maritime navigation algorithm for avoiding hazards and obeying COLREGS using Velocity Obstacles to the data obtained, the autonomous vessel computes a safe and effective path to be followed in order to accomplish a desired navigational end result, while operating in a manner so as to avoid hazards and to maintain compliance with standard navigational procedures defined by international agreement. The systems and methods have been successfully demonstrated on water with radar and stereo cameras as the perception sensors, and integrated with a higher level planner for trailing a maneuvering target.

Kuwata, Yoshiaki↗

NASA NTRS2009

Data Base and Guidelines Document Developed for Lithium-Ion Battery

Lithium-Ion (Li-Ion) batteries are fast becoming the battery chemistry of choice for aerospace applications requiring (rechargeable) power supplies. These batteries offer high-energy density and high-specific energy combined with excellent rate capability and cycle potential. The increased energy content and operational characteristics of this system require defined safety and handling procedures to ensure the safe implementation. Standardized approaches to defining, determining, and addressing safety, handling, and qualification for Li-Ion batteries have been developed and published as an NESC-sponsored Li-Ion Battery Guidelines Document. A data base was established cataloging cells and batteries that have been considered for aerospace applications.

Data Base and Guidelines↗

NASA NTRS2015

Electronic Procedures for Medical Operations

Electronic procedures are replacing text-based documents for recording the steps in performing medical operations aboard the International Space Station. S&K Aerospace, LLC, has developed a content-based electronic system-based on the Extensible Markup Language (XML) standard-that separates text from formatting standards and tags items contained in procedures so they can be recognized by other electronic systems. For example, to change a standard format, electronic procedures are changed in a single batch process, and the entire body of procedures will have the new format. Procedures can be quickly searched to determine which are affected by software and hardware changes. Similarly, procedures are easily shared with other electronic systems. The system also enables real-time data capture and automatic bookmarking of current procedure steps. In Phase II of the project, S&K Aerospace developed a Procedure Representation Language (PRL) and tools to support the creation and maintenance of electronic procedures for medical operations. The goal is to develop these tools in such a way that new advances can be inserted easily, leading to an eventual medical decision support system.

Source record↗

NASA NTRS2016

Understanding Current Safety Issues for Trajectory Based Operations

Increases in procedural complexity were investigated as a possible contributor to flight path deviations in airline operations. Understanding current operational issues and their causes must be embraced to maintain current safety standards while increasing future functionality. ASRS data and expert narratives were used to discover factors relating to pilot deviations. Our investigation pointed to ATC intervention, automation confusion, procedure design, and mixed equipment as primary issues. Future work will need to include objective data and mitigation strategies.

RNAV STAR↗

NASA NTRS2007

Revisiting Training and Verification Process Implementation for Risk Reduction on New Missions at NASA Jet Propulsion Laboratory

In 2003 we proposed an effort to develop a core program of standardized training and verification practices and standards against which the implementation of these practices could be measured. The purpose was to provide another means of risk reduction for deep space missions to preclude the likelihood of a repeat of the tragedies of the 1998 Mars missions. We identified six areas where the application of standards and standardization would benefit the overall readiness process for flight projects at JPL. These are Individual Training, Team Training, Interface and Procedure Development, Personnel Certification, Interface and procedure Verification, and Operations Readiness Testing. In this paper we will discuss the progress that has been made in the tasks of developing the proposed infrastructure in each of these areas. Specifically we will address the Position Training and Certification Standards that are now available for each operational position found on our Flight Operations Teams (FOT). We will also discuss the MGSS Baseline Flight Operations Team Training Plan which can be tailored for each new flight project at JPL. As these tasks have been progressing, the climate and emphasis for Training and for V and V at JPL has changed, and we have learned about the expansion, growth, and limitations in the roles of traditional positions at JPL such as the Project's Training Engineer, V and V Engineer, and Operations Engineer. The need to keep a tight rein on budgets has led to a merging and/or reduction in these positions which pose challenges to individual capacities and capabilities. We examine the evolution of these processes and the roles involved while taking a look at the impact or potential impact of our proposed training related infrastructure tasks. As we conclude our examination of the changes taking place for new flight projects, we see that the importance of proceeding with our proposed tasks and adapting them to the changing climate remains an important element in reducing the risk in the challenging business of space exploration.

verifications↗

NASA NTRS1989

Management plan documentation standard and Data Item Descriptions (DID). Volume of the information system life-cycle and documentation standards, volume 2

This is the second of five volumes of the Information System Life-Cycle and Documentation Standards. This volume provides a well-organized, easily used standard for management plans used in acquiring, assuring, and developing information systems and software, hardware, and operational procedures components, and related processes.

Callender, E. David↗

NASA NTRS2015

Terminal Sequencing and Spacing (TSS)

The Federal Aviation Administration's (FAA) Next Generation Air Transportation System (or NextGen) is being designed to support the predicted increases in traffic volume and to increase the capacity, efficiency and safety of the National Airspace System (NAS). The Federal Aviation Administration (FAA) identifies Performance-Based Navigation (PBN) as a key enabling capability of NextGen and is actively publishing PBN procedures at major airports throughout the United States. Standard Terminal Arrival Routes (STARs), procedures, and approaches are designed to facilitate fuel-efficient continuous descent operations. However, their use is limited during periods of high traffic demand due to the complexity of merging multiple streams of aircraft to the same airport. As a result, most arrivals in the Terminal Radar Approach Control (TRACON) area continue to be controlled using radar vectoring and step-down descents, resulting in high workload for controllers and diverting aircraft from efficient PBN trajectories. To address this issue, NASA developed the Terminal Sequencing and Spacing (TSS) system, an advanced arrival management technology that combines time-based scheduling and controller-based precision spacing tools. TSS is a ground-based controller automation tool that facilitates sequencing and merging arrivals on Performance-Based Navigation (PBN) routes, especially during highly congested demand periods. The two main components of TSS are: 1) a scheduler that de-conflicts merging arrivals in the terminal area by computing appropriate arrival times to the runway threshold and upstream terminal merge points, and 2) a set of Controller-Managed Spacing (CMS) decision support tools to efficiently assist schedule conformance. Sixteen high-fidelity human-in-the-loop simulations involving more than five hundred hours of evaluation time, were conducted to mature TSS from proof-of-concept design to a fully functional prototype. Results indicate high controller use and acceptability of the CMS tools as well as improved PBN route conformance (Figure 2). The TSS technology was transferred to the FAA in 2014, and it is targeted for deployment to several busy airports in the U.S. starting in 2018. Potential enhancements to TSS using DataComm will also be presented.

controller-managed spacing↗