How One Functional Human Performance Requirement Influenced a Rocket: NASA Human Systems Integration Success Story
Explore the source record for details and available documents.
SEARCH · Engineering Papers
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.
Explore the source record for details and available documents.
NASA's Human Research Program (HRP) supports research to reduce human health and performance risks inherent in future human space exploration missions. Understanding risk outcomes and contributing factors in an integrated manner allows HRP research to support development of efficient and effective mitigations from cross‐disciplinary perspectives, and to enable resilient human and engineered systems for spaceflight. The purpose of this work is to support scientific collaborations and research portfolio management by utilizing modeling for analysis and visualization of current and potential future interdisciplinary efforts.
Explore the source record for details and available documents.
In the realm of aerospace engineering and the physical sciences, we have developed laws of physics based on empirical and research evidence that reliably guide design, research, and development efforts. For instance, an engineer designs a system based on data and experience that can be consistently and repeatedly verified. This reproducibility depends on the consistency and dependability of the materials on which the engineer works and is subject to physics, geometry and convention. In life sciences and medicine, these apply as well, but individuality introduces a host of variables into the mix, resulting in characteristics and outcomes that can be quite broad within a population of individuals. This individuality ranges from differences at the genetic and cellular level to differences in an individuals personality and abilities due to sex and gender, environment, education, etc.
Space system design optimization based on human requirements during acceleration
Physical and numeric models of the human circulation are constructed for a number of objectives, including studies and training in physiologic control, interpretation of clinical observations, and testing of prosthetic cardiovascular devices. For many of these purposes it is important to quantitatively validate the dynamic response of the models in terms of the input impedance (Z = oscillatory pressure/oscillatory flow). To address this need, the authors developed an improved physical model. Using a computer study, the authors first identified the configuration of lumped parameter elements in a model of the systemic circulation; the result was a good match with human aortic input impedance with a minimum number of elements. Design, construction, and testing of a hydraulic model analogous to the computer model followed. Numeric results showed that a three element model with two resistors and one compliance produced reasonable matching without undue complication. The subsequent analogous hydraulic model included adjustable resistors incorporating a sliding plate to vary the flow area through a porous material and an adjustable compliance consisting of a variable-volume air chamber. The response of the hydraulic model compared favorably with other circulation models.
Explore the source record for details and available documents.
The National Aeronautics and Space Administration (NASA) Constellation Program is responsible for planning and implementing those programs necessary to send human explorers back to the moon, onward to Mars and other destinations in the solar system, and to support missions to the International Space Station. The Constellation Program has the technical management responsibility for all Constellation Projects, including both human rated and non-human rated vehicles such as the Crew Exploration Vehicle, EVA Systems, the Lunar Lander, Lunar Surface Systems, and the Ares I and Ares V rockets. With NASA s new Vision for Space Exploration to send humans beyond Earth orbit, it is critical to consider the human as a system that demands early and continuous user involvement, inclusion in trade offs and analyses, and an iterative "prototype/test/ redesign" process. Personnel at the NASA Johnson Space Center are involved in the Constellation Program at both the Program and Project levels as human system integrators. They ensure that the human is considered as a system, equal to hardware and software vehicle systems. Systems to deliver and support extended human habitation on the moon are extremely complex and unique, presenting new opportunities to employ Human Systems Integration, or HSI practices in the Constellation Program. The purpose of the paper is to show examples of where human systems integration work is successfully employed in the Constellation Program and related Projects, such as in the areas of habitation and early requirements and design concepts.
The NASA Engineering and Safety Center (NESC) Human Factors (HF) Technical Discipline Team (TDT) funded a preliminary study in 2017 that was narrowly focused within the Range Data Display System (RDDS) scope of display design requirements based on schedule and resources. Wallops Flight Facility (WFF) personnel involved in the previous study asked for a broader Human Systems Integration (HSI) involvement that would span both the RDDS and Flight Termination System (FTS) projects and assist with identifying HSI best practices, via appropriate standards and guidelines, that if properly implemented should result in a more effective and efficient Range Safety Operations. WFF Range Safety Operations has expressed a need to assess the roles, responsibilities, and functions of the various personnel on console during launches to identify existing and potential efficiencies and incorporate them in the new system design. This assessment addresses that need.
Helmet-mounted displays of infrared imagery (forward-looking infrared (FLIR)) allow helicopter pilots to perform low level missions at night and in low visibility. However, pilots experience high visual and cognitive workload during these missions, and their performance capabilities may be reduced. Human factors problems inherent in existing systems stem from three primary sources: the nature of thermal imagery; the characteristics of specific FLIR systems; and the difficulty of using FLIR system for flying and/or visually acquiring and tracking objects in the environment. The pilot night vision system (PNVS) in the Apache AH-64 provides a monochrome, 30 by 40 deg helmet-mounted display of infrared imagery. Thermal imagery is inferior to television imagery in both resolution and contrast ratio. Gray shades represent temperatures differences rather than brightness variability, and images undergo significant changes over time. The limited field of view, displacement of the sensor from the pilot's eye position, and monocular presentation of a bright FLIR image (while the other eye remains dark-adapted) are all potential sources of disorientation, limitations in depth and distance estimation, sensations of apparent motion, and difficulties in target and obstacle detection. Insufficient information about human perceptual and performance limitations restrains the ability of human factors specialists to provide significantly improved specifications, training programs, or alternative designs. Additional research is required to determine the most critical problem areas and to propose solutions that consider the human as well as the development of technology.
Explore the source record for details and available documents.
A human-centered approach to computer systems design involves reframing analysis in terms of people interacting with each other, not only human-machine interaction. The primary concern is not how people can interact with computers, but how shall we design computers to help people work together? An analysis of astronaut interactions with CapCom on Earth during one traverse of Apollo 17 shows what kind of information was conveyed and what might be automated today. A variety of agent and robotic technologies are proposed that deal with recurrent problems in communication and coordination during the analyzed traverse.
Space system design optimization based on mission and human requirements as they pertain to acceleration, discussing boost, abort, earth entry and restricting of accelerations
Throughout the history of human spaceflight, NASA has relied on a team of ground-based experts on Earth to manage its missions, vehicles, and crews to ensure crew safety and mission success. However, as missions progress beyond low-Earth orbit (LEO), this paradigm of dependence on ground must evolve. Beyond LEO, in missions to the moon and Mars, crews will confront new challenges: limited evacuation options, reduced resupply capabilities, and significant communication delays that impede real-time support from experts on the ground. This reduction in ground support amplifies the likelihood that crews will be unable to adequately respond to unanticipated, safety-critical events. Understanding the scope of these risks and identifying effective countermeasures hinges on understanding the impact of communication delays on complex operations, especially in urgent, unforeseen events. Real-time communication currently provides the crew with continuous access to a large, extensively resourced ground team skilled in anomaly resolution. However, as communication delays grow, the need to transfer some responsibilities from ground experts to onboard crew becomes evident. NASA has been exploring this shift in operational responsibilities and its effectiveness in managing complex operations for decades. Nevertheless, a comprehensive understanding of the specific challenges posed by communication delays and the necessary countermeasures to mitigate them remains a gap. In this paper, we present an update on our systematic review of the literature on communication delays, the first in-depth review since 2013 (Rader et al.). We introduce a coding taxonomy to capture key constructs from papers of interest and discuss preliminary findings. These preliminary results suggest two significant research gaps: limited studies have been conducted 1) with lunar-like latencies and 2) on problem-solving strategies for the maximum latencies expected in Mars missions. We outline plans and propose recommendations to address these gaps through ongoing and future research.
This document provides definition of technology human interface requirements for Collision Avoidance (CA). This was performed through a review of CA-related, HSI requirements documents, standards, and recommended practices. Technology concepts in use by the Access 5 CA work package were considered... Beginning with the HSI high-level functional requirement for CA, and CA technology elements, HSI requirements for the interface to the pilot were identified. Results of the analysis describe (1) the information required by the pilot to have knowledge CA system status, and (2) the control capability needed by the pilot to obtain CA information and affect an avoidance maneuver. Fundamentally, these requirements provide the candidate CA technology concepts with the necessary human-related elements to make them compatible with human capabilities and limitations. The results of the analysis describe how CA operations and functions should interface with the pilot to provide the necessary CA functionality to the UA-pilot system .Requirements and guidelines for CA are partitioned into four categories: (1) General, (2) Alerting, (3) Guidance, and (4) Cockpit Display of Traffic Information. Each requirement is stated and is supported with a rationale and associated reference(s).
This document provides guidance to the FAA on important human factors considerations that can be used to support the certification of a UAS Aircraft Control Station (ACS). This document provides a synopsis of the human factors analysis, design and test activities to be performed to provide a basis for FAA certification. The data from these analyses, design activities, and tests, along with data from certification/qualification tests of other key components should be used to establish the ACS certification basis. It is expected that this information will be useful to manufacturers in developing the ACS Certification Plan,, and in supporting the design of their ACS.
Launch processing at Kennedy Space Center (KSC) is primarily accomplished by human users of expensive and specialized equipment. In order to reduce the likelihood of human error, to reduce personal injuries, damage to hardware, and loss of mission the design process for the hardware needs to include the human's relationship with the hardware. Just as there is electrical, mechanical, and fluids, the human aspect is just as important. The focus of this presentation is to illustrate how KSC accomplishes the inclusion of the human aspect in the design using human centered hardware modeling and engineering. The presentations also explain the current and future plans for research and development for improving our human factors analysis tools and processes.
This document involves definition of technology interface requirements for Contingency Management. This was performed through a review of Contingency Management-related, HSI requirements documents, standards, and recommended practices. Technology concepts in use by the Contingency Management Work Package were considered. Beginning with HSI high-level functional requirements for Contingency Management, and Contingency Management technology elements, HSI requirements for the interface to the pilot were identified. Results of the analysis describe (1) the information required by the pilot to have knowledge of system failures and associated contingency procedures, and (2) the control capability needed by the pilot to obtain system status and procedure information. Fundamentally, these requirements provide the candidate Contingency Management technology concepts with the necessary human-related elements to make them compatible with human capabilities and limitations. The results of the analysis describe how Contingency Management operations and functions should interface with the pilot to provide the necessary Contingency Management functionality to the UA-pilot system. Requirements and guidelines for Contingency Management are partitioned into four categories: (1) Health and Status and (2) Contingency Management. Each requirement is stated and is supported with a rationale and associated reference(s).