Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “checklists”

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

Automation of crew procedures using multifunction display and control systems

A multifunction display and control system (MFDCS) design concept has been developed for the Orbiter spacecraft. The system provides for automation of crew procedures, fault prioritization, incorporation of checklists and procedures into the display and control system and system flexibility in response to mission variation, increased experience and advancing display and control technology. Hardware included in the system includes a multifunction keyboard using programmable legend switches, a medium size flat panel display for presentation of alphanumeric information and a color CRT for the display of schematic diagrams. The access schema for the multifunction display and control system preserves the single function capability of the present set of dedicated switches while also providing for automation of many of the checklists and procedures. A basic design feature of the system is the ability to change the relative level of automation and crew interaction without modifying the system hardware or basic software operating system.

Spiger, R. J.↗

Background issues for on-line aircraft documentation

Currently, almost all aircraft documentation in commercial aircraft cockpits is presented via hardcopy manuals. Several recent projects are aimed at eliminating all paper documentation in cockpits using electronic libraries. Electronic libraries encompass diverse information bases including aircraft system documentation, operations and procedures, checklists, maintenance logs, minimum equipment lists, maps and charts, and flight management information. These electronic libraries are envisioned to be embedded in the avionics so as to provide real time monitoring and display of information. Background issues are examined (motivation, information retrieval models, and preliminary designs) for the on-line presentation of aircraft systems documentation including operations, procedures, and checklists.

Russell, C. Ray↗

On the typography of flight-deck documentation

Many types of paper documentation are employed on the flight-deck. They range from a simple checklist card to a bulky Aircraft Flight Manual (AFM). Some of these documentations have typographical and graphical deficiencies; yet, many cockpit tasks such as conducting checklists, way-point entry, limitations and performance calculations, and many more, require the use of these documents. Moreover, during emergency and abnormal situations, the flight crews' effectiveness in combating the situation is highly dependent on such documentation; accessing and reading procedures has a significant impact on flight safety. Although flight-deck documentation are an important (and sometimes critical) form of display in the modern cockpit, there is a dearth of information on how to effectively design these displays. The object of this report is to provide a summary of the available literature regarding the design and typographical aspects of printed matter. The report attempts 'to bridge' the gap between basic research about typography, and the kind of information needed by designers of flight-deck documentation. The report focuses on typographical factors such as type-faces, character height, use of lower- and upper-case characters, line length, and spacing. Some graphical aspects such as layout, color coding, fonts, and character contrast are also discussed. In addition, several aspects of cockpit reading conditions such as glare, angular alignment, and paper quality are addressed. Finally, a list of recommendations for the graphical design of flight-deck documentation is provided.

Degani, Asaf↗

A matrix safety frame approach to robot safety for space applications

The planned use of autonomous robots in space applications has generated many new safety problems. This thesis assesses safety of autonomous robot systems through the structure of a proposed three-dimensional matrix safety frame. By identifying the common points of accidents and fatalities involving terrestrial robots, reviewing terrestrial robot safety standards, and modifying and extending these results to space applications, hazards are identified and their associated risks assessed. Three components of the safeguarding dimension of the matrix safety frame, safeguarding through design and operation for intrinsic safety, and incorporation of add-on safety systems are explained through examples for both terrestrial and space robots. A space robot hazard identification checklist, a qualitative tool for robot systems designers, is developed using the structure imparted by the matrix safety frame. The development of an expert system from the contents of the checklist is discussed.

Montgomery, T. D.↗

Evaluation of Job Queuing/Scheduling Software: Phase I Report

The recent proliferation of high performance work stations and the increased reliability of parallel systems have illustrated the need for robust job management systems to support parallel applications. To address this issue, the national Aerodynamic Simulation (NAS) supercomputer facility compiled a requirements checklist for job queuing/scheduling software. Next, NAS began an evaluation of the leading job management system (JMS) software packages against the checklist. This report describes the three-phase evaluation process, and presents the results of Phase 1: Capabilities versus Requirements. We show that JMS support for running parallel applications on clusters of workstations and parallel systems is still insufficient, even in the leading JMS's. However, by ranking each JMS evaluated against the requirements, we provide data that will be useful to other sites in selecting a JMS.

Jones, James Patton↗

The Effect of Interruptions on Part 121 Air Carrier Operations

The primary purpose of this study was to determine the relative priorities of various events and activities by examining the probability that a given activity was interrupted by a given event. The analysis will begin by providing frequency of interruption data by crew position (captain versus first officer) and event type. Any differences in the pattern of interruptions between the first officers and the captains will be explored and interpreted in terms of standard operating procedures. Subsequent data analyses will focus on comparing the frequency of interruptions for different types of activities and for the same activities under normal versus emergency conditions. Briefings and checklists will receive particular attention. The frequency with which specific activities are interrupted under multiple- versus single-task conditions also will be examined; because the majority of multiple-task data were obtained under laboratory conditions, LOFT-type tapes offer a unique opportunity to examine concurrent task performance under 'real-world' conditions. A second purpose of this study is to examine the effects of the interruptions on performance. More specifically, when possible, the time to resume specific activities will be compared to determine if pilots are slower to resume certain types of activities. Errors in resumption or failures to resume specific activities will be noted and any patterns in these errors will be identified. Again, particular attention will be given to the effects of interruptions on the completion of checklists and briefings. Other types of errors and missed events (i.e., the crew should have responded to the event but did not) will be examined. Any methodology using interruptions to examine task prioritization must be able to identify when an interruption has occurred and describe the ongoing activities that were interrupted. Both of these methodological problems are discussed In detail in the following section,

Damos, Diane L.↗

Second Evaluation of Job Queuing/Scheduling Software

The recent proliferation of high performance workstations and the increased reliability of parallel systems have illustrated the need for robust job management systems to support parallel applications. To address this issue, NAS compiled a requirements checklist for job queuing/scheduling software. Next, NAS evaluated the leading job management system (JMS) software packages against the checklist. A year has now elapsed since the first comparison was published, and NAS has repeated the evaluation. This report describes this second evaluation, and presents the results of Phase 1: Capabilities versus Requirements. We show that JMS support for running parallel applications on clusters of workstations and parallel systems is still lacking, however, definite progress has been made by the vendors to correct the deficiencies. This report is supplemented by a WWW interface to the data collected, to aid other sites in extracting the evaluation information on specific requirements of interest.

Jones, James Patton↗

Columbia Accident Investigation Board Report. Volume Two

Volume II of the Report contains appendices that were cited in Volume I. The Columbia Accident Investigation Board produced many of these appendices as working papers during the investigation into the February 1, 2003 destruction of the Space Shuttle Columbia. Other appendices were produced by other organizations (mainly NASA) in support of the Board investigation. In the case of documents that have been published by others, they are included here in the interest of establishing a complete record, but often at less than full page size. Contents include: CAIB Technical Documents Cited in the Report: Reader's Guide to Volume II; Appendix D. a Supplement to the Report; Appendix D.b Corrections to Volume I of the Report; Appendix D.1 STS-107 Training Investigation; Appendix D.2 Payload Operations Checklist 3; Appendix D.3 Fault Tree Closure Summary; Appendix D.4 Fault Tree Elements - Not Closed; Appendix D.5 Space Weather Conditions; Appendix D.6 Payload and Payload Integration; Appendix D.7 Working Scenario; Appendix D.8 Debris Transport Analysis; Appendix D.9 Data Review and Timeline Reconstruction Report; Appendix D.10 Debris Recovery; Appendix D.11 STS-107 Columbia Reconstruction Report; Appendix D.12 Impact Modeling; Appendix D.13 STS-107 In-Flight Options Assessment; Appendix D.14 Orbiter Major Modification (OMM) Review; Appendix D.15 Maintenance, Material, and Management Inputs; Appendix D.16 Public Safety Analysis; Appendix D.17 MER Manager's Tiger Team Checklist; Appendix D.18 Past Reports Review; Appendix D.19 Qualification and Interpretation of Sensor Data from STS-107; Appendix D.20 Bolt Catcher Debris Analysis.

CAIB (COLUMBIA ACCIDENT INVESTIGATION BOARD)↗

Software Assists in Extensive Environmental Auditing

The Base Enivronmental Management System (BEMS) is a Web-based application program for managing and tracking audits by the Environmental Office of Stennis Space Center in conformity with standard 14001 of the International Organization for Standardization (ISO 14001). (This standard specifies requirements for an environmental-management system.) BEMS saves time by partly automating what were previously manual processes for creating audit checklists; recording and tracking audit results; issuing, tracking, and implementing corrective-action requests (CARs); tracking continuous improvements (CIs); and tracking audit results and statistics. BEMS consists on an administration module and an auditor module. As its name suggests, the administration module is used to administer the audit. It helps administrators to edit the list of audit questions; edit the list of audit locations; assign manditory questions to locations; track, approve, and edit CARs; and edit completed audits. The auditor module is used by auditors to perform audits and record audit results: It helps the auditors to create audit checklists, complete audits, view completed audits, create CARs, record and acknowledge CIs, and generate reports from audit results.

Callac, Christopher↗

Software Assists in Extensive Environmental Auditing

The Base Environmental Management System (BEMS) is a Web-based application program for managing and tracking audits by the Environmental Office of Stennis Space Center in conformity with standard 14001 of the International Organization for Standardization (ISO 14001). (This standard specifies requirements for an environmental-management system.) BEMS saves time by partly automating what were previously manual processes for creating audit checklists; recording and tracking audit results; issuing, tracking, and implementing corrective-action requests (CARs); tracking continuous improvements (CIs); and tracking audit results and statistics. BEMS consists of an administration module and an auditor module. As its name suggests, the administration module is used to administer the audit. It helps administrators to edit the list of audit questions; edit the list of audit locations; assign mandatory questions to locations; track, approve, and edit CARs; and edit completed audits. The auditor module is used by auditors to perform audits and record audit results: it helps the auditors to create audit checklists, complete audits, view completed audits, create CARs, record and acknowledge CIs, and generate reports from audit results.

Callac, Christopher↗

Advanced Technology Applications for Combat Casualty Care

Exploration Medical Capability (ExMC) is an element of NASA s Human Research Program (HRP). ExMC s goal is to address the risk of the "Inability to Adequately Recognize or Treat an Ill or Injured Crewmember." This poster highlights the approach ExMC has taken to address this goal and our current areas of interest. The Space Medicine Exploration Medical Condition List (SMEMCL) was created to identify medical conditions of concern during exploration missions. The list was derived from space flight medical incidents, the shuttle medical checklist, the International Space Station medical checklist, and expert opinion. The conditions on the list were prioritized according to mission type by a panel comprised of flight surgeons, physician astronauts, engineers, and scientists. From the prioritized list, the ExMC element determined the capabilities needed to address the medical conditions of concern. Where such capabilities were not currently available, a gap was identified. The element s research plan outlines these gaps and the tasks identified to achieve the desired capabilities for exploration missions.

Watkins, Sharmila↗

Aircraft Emergencies: Challenge and Response

Emergency and abnormal situations in aviation present flight crews with a number of challenges. Checklists are essential tools that have been developed to assist them to meet these challenges. However, in order for checklists to be most effective in these situations they must be designed with the operational and situational demands of emergencies and abnormal conditions in mind as well as human performance capabilities and limitations under high stress and workload.

Burian, Barbara K.↗

Exploration Medical Capability

Exploration Medical Capability (ExMC) is an element of NASA's Human Research Program (HRP). ExMC's goal is to address the risk of the Inability to Adequately Recognize or Treat an Ill or Injured Crewmember. This poster highlights the approach ExMC has taken to address this goal and our current areas of interest. The Space Medicine Exploration Medical Condition List (SMEMCL) was created to identify medical conditions of concern during exploration missions. The list was derived from space flight medical incidents, the shuttle medical checklist, the International Space Station medical checklist, and expert opinion. The conditions on the list were prioritized according to mission type by a panel comprised of flight surgeons, physician astronauts, engineers, and scientists. From the prioritized list, the ExMC element determined the capabilities needed to address the medical conditions of concern. Where such capabilities were not currently available, a gap was identified. The element s research plan outlines these gaps and the tasks identified to achieve the desired capabilities for exploration missions. This poster is being presented to inform the audience of the gaps and tasks being investigated by ExMC and to encourage discussions of shared interests and possible future collaborations.

Watkins, Sharmila↗

Shuttle Abort Flight Management (SAFM) - Application Overview

One of the most demanding tasks that must be performed by the Space Shuttle flight crew is the process of determining whether, when and where to abort the vehicle should engine or system failures occur during ascent or entry. Current Shuttle abort procedures involve paging through complicated paper checklists to decide on the type of abort and where to abort. Additional checklists then lead the crew through a series of actions to execute the desired abort. This process is even more difficult and time consuming in the absence of ground communications since the ground flight controllers have the analysis tools and information that is currently not available in the Shuttle cockpit. Crew workload specifically abort procedures will be greatly simplified with the implementation of the Space Shuttle Cockpit Avionics Upgrade (CAU) project. The intent of CAU is to maximize crew situational awareness and reduce flight workload thru enhanced controls and displays, and onboard abort assessment and determination capability. SAFM was developed to help satisfy the CAU objectives by providing the crew with dynamic information about the capability of the vehicle to perform a variety of abort options during ascent and entry. This paper- presents an overview of the SAFM application. As shown in Figure 1, SAFM processes the vehicle navigation state and other guidance information to provide the CAU displays with evaluations of abort options, as well as landing site recommendations. This is accomplished by three main SAFM components: the Sequencer Executive, the Powered Flight Function, and the Glided Flight Function, The Sequencer Executive dispatches the Powered and Glided Flight Functions to evaluate the vehicle's capability to execute the current mission (or current abort), as well as more than IS hypothetical abort options or scenarios. Scenarios are sequenced and evaluated throughout powered and glided flight. Abort scenarios evaluated include Abort to Orbit (ATO), Transatlantic Abort Landing (TAL), East Coast Abort Landing (ECAL) and Return to Launch Site (RTLS). Sequential and simultaneous engine failures are assessed and landing footprint information is provided during actual entry scenarios as well as hypothetical "loss of thrust now" scenarios during ascent.

Hu, Howard↗

The Space Medicine Exploration Medical Condition List

Exploration Medical Capability (ExMC) is an element of NASA s Human Research Program (HRP). ExMC's goal is to address the risk of the "Inability to Adequately Recognize or Treat an Ill or Injured Crewmember." This poster highlights the approach ExMC has taken to address this risk. The Space Medicine Exploration Medical Condition List (SMEMCL) was created to define the set of medical conditions that are most likely to occur during exploration space flight missions. The list was derived from the International Space Station Medical Checklist, the Shuttle Medical Checklist, in-flight occurrence data from the Lifetime Surveillance of Astronaut Health, and NASA subject matter experts. The list of conditions was further prioritized for eight specific design reference missions with the assistance of the ExMC Advisory Group. The purpose of the SMEMCL is to serve as an evidence-based foundation for the conditions that could affect a crewmember during flight. This information is used to ensure that the appropriate medical capabilities are available for exploration missions.

Watkins, Sharmi↗

Onboard Determination of Vehicle Glide Capability for Shuttle Abort Flight Managment (SAFM)

When one or more main engines fail during ascent, the flight crew of the Space Shuttle must make several critical decisions and accurately perform a series of abort procedures. One of the most important decisions for many aborts is the selection ofa landing site. Several factors influence the ability to reach a landing site, including the spacecraft point of atmospheric entry, the energy state at atmospheric entry, the vehicle glide capability from that energy state, and whether one or more suitable landing sites are within the glide capability. Energy assessment is further complicated by the fact that phugoid oscillations in total energy influence glide capability. Once the glide capability is known, the crew must select the "best" site option based upon glide capability and landing site conditions and facilities. Since most of these factors cannot currently be assessed by the crew in flight, extensive planning is required prior to each mission to script a variety of procedures based upon spacecraft velocity at the point of engine failure (or failures). The results of this preflight planning are expressed in tables and diagrams on mission-specific cockpit checklists. Crew checklist procedures involve leafing through several pages of instructions and navigating a decision tree for site selection and flight procedures - all during a time critical abort situation. With the advent of the Cockpit Avionics Upgrade (CAU), the Shuttle will have increased on-board computational power to help alleviate crew workload during aborts and provide valuable situational awareness during nominal operations. One application baselined for the CAU computers is Shuttle Abort Flight Management (SAFM), whose requirements have been designed and prototyped. The SAFM application includes powered and glided flight algorithms. This paper describes the glided flight algorithm which is dispatched by SAFM to determine the vehicle glide capability and make recommendations to the crew for site selection as well as to monitor glide capability while in route to the selected site. Background is provided on Shuttle entry guidance as well as the various types of Shuttle aborts. SAFM entry requirements and cockpit disp lays are discussed briefly to provide background for Glided Flight algorithm design considerations. The central principal of the Glided Flight algorithm is the use of energy-over-weight (EOW) curves to determine range and crossrange boundaries. The major challenges of this technique are exo-atmospheric flight, and phugoid oscillations in energy. During exo-atmospheric flight, energy is constant, so vehicle EOW is not sufficient to determine glide capability. The paper describes how the exo-atmospheric problem is solved by propagating the vehicle state to an "atmospheric pullout" state defined by Shuttle guidance parameters.

Straube, Timothy↗

The Near Earth Asteroid Medical Conditions List

Purpose: The Exploration Medical Capability (ExMC) element is one of six elements within NASA s Human Research Program (HRP) and is responsible for addressing the risk of "the inability to adequately recognize or treat an ill or injured crewmember" for exploration-class missions. The Near Earth Asteroid (NEA) Medical Conditions List, constructed by ExMC, is the first step in addressing the above-mentioned risk for the 13-month long NEA mission. The NEA mission is being designed by NASA's Human Space Flight Architecture Team (HAT). The purpose of the conditions list is to serve as an evidence-based foundation for determining which medical conditions could affect a crewmember during the NEA mission, which of those conditions would be of concern and require treatment, and for which conditions a gap in knowledge or technology development exists. This information is used to focus research efforts and technology development to ensure that the appropriate medical capabilities are available for exploration-class missions. Scope and Approach: The NEA Medical Conditions List is part of a broader Space Medicine Exploration Medical Conditions List (SMEMCL), which incorporates various exploration-class design reference missions (DRMs). The conditions list contains 85 medical conditions which could occur during space flight and which are derived from several sources: Long-Term Surveillance of Astronaut Health (LSAH) in-flight occurrence data, The Space Shuttle (STS) Medical Checklist, The International Space Station (ISS) Medical Checklist, and subject matter expert opinion. Each medical condition listed has been assigned a clinical priority and a clinical priority rationale based on incidence, consequence, and mitigation capability. Implementation: The conditions list is a "living document" and as such, new conditions can be added to the list, and the priority of conditions on the list can be adjusted as the DRM changes, and as screening, diagnosis, or treatment capabilities change. The NEA medical conditions list was used recently as the basis for identifying gaps in in-flight medical evaluation (screening) capabilities. Learning Objectives: The audience will become familiar with the approach taken by NASA's Exploration Medical Capability element in addressing the risk of inability to recognize and treat medical conditions in the setting of a Near Earth Asteroid mission. Which one of the following statements is incorrect? a) The Near Earth Asteroid (NEA) medical conditions list includes 85 medical conditions which could occur during space flight. b) Each condition on the NEA medical conditions list has been assigned a clinical priority and a clinical priority rationale. c) The NEA medical conditions list targets a mission to Mars. d) The NEA medical conditions list should be viewed as a "living document" where new conditions can be added and clinical priorities adjusted to address changes in the design reference mission or medical capabilities. The incorrect answer is c). The NEA medical conditions list targets a mission to a Near Earth Asteroid.

Barr, Yael R.↗

Software Assists in Extensive Environmental Auditing

The Base Environmental Management System (BEMS) is a Web-based application program for managing and tracking audits by the Environmental Office of Stennis Space Center in conformity with standard 14001 of the International Organization for Standardization (ISO 14001). (This standard specifies requirements for an environmental-management system.) BEMS saves time by partly automating what were previously manual processes for creating audit checklists; recording and tracking audit results; issuing, tracking, and implementing corrective-action requests (CARs); tracking continuous improvements (CIs); and tracking audit results and statistics. BEMS consists of an administration module and an auditor module. As its name suggests, the administration module is used to administer the audit. It helps administrators to edit the list of audit questions; edit the list of audit locations; assign mandatory questions to locations; track, approve, and edit CARs; and edit completed audits. The auditor module is used by auditors to perform audits and record audit results: it helps the auditors to create audit checklists, complete audits, view completed audits, create CARs, record and acknowledge CIs, and generate reports from audit results.

Callac, Christopher↗