Search NASA⌕ Search

SEARCH · Search NASA

Results for “Human centered design”

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 109 records · Page 6
All sourcesNASA NTRSDOE OSTI
NASA NTRS2016

Next Generation Flight Displays Using HTML5

The Human Integrated Vehicles and Environments (HIVE) lab at Johnson Space Center (JSC) is focused on bringing together inter-disciplinary talent to design and integrate innovative human interface technologies for next generation manned spacecraft. As part of this objective, my summer internship project centered on an ongoing investigation in to building flight displays using the HTML5 standard. Specifically, the goals of my project were to build and demo "flight-like" crew and wearable displays as well as create a webserver for live systems being developed by the Advanced Exploration Systems (AES) program. In parallel to my project, a LabVIEW application, called a display server, was created by the HIVE that uses an XTCE (XML (Extensible Markup Language) Telemetry and Command Exchange) parser and CCSDS (Consultative Committee for Space Data System) space packet decoder to translate telemetry items sent by the CFS (Core Flight Software) over User Datagram Protocol (UDP). It was the webserver's job to receive these UDP messages and send them to the displays. To accomplish this functionality, I utilized Node.js and the accompanying Express framework. On the display side, I was responsible for creating the power system (AMPS) displays. I did this by using HTML5, CSS and JavaScript to create web pages that could update and change dynamically based on the data they received from the webserver. At this point, I have not started on the commanding, being able to send back to the CFS, portion of the displays but hope to have this functionality working by the completion of my internship. I also created a way to test the webserver's functionality without the display server by making a JavaScript application that read in a comma-separate values (CSV) file and converted it to XML which was then sent over UDP. One of the major requirements of my project was to build everything using as little preexisting code as possible, which I accomplished by only using a handful of JavaScript libraries. As a side project, I created a model of the HIVE lab and Building 29 using SketchUp. I obtained the floorplans of the building from the JSC Geographic Information Systems (GIS), which were computer-aided design (CAD) files, and imported them into SketchUp. I then took those floorplans and created a 3D model of the building from them. Working in conjunction with the Hybrid Reality lab in Building 32, the SketchUp model was imported into Unreal Engine for use with the HTC Vive. Using the Vive, I was able to interact with the model I created in virtual reality (VR). The purpose of this side project was to be able to visualize potential lab layouts and mockup designs as they are in development in order to finalize design decisions. Pending approval, the model that I created will be used in the Build-As-You-Test: Can Hybrid Reality Improve the SE/HSI Design Process project in the fall. Getting the opportunity to work at NASA has been one of the most memorable experiences of my life. Over the course of my internship, I improved my programming and web development abilities substantially. I will take all the skills and experiences I have had while at NASA back to school with me in the fall and hope to pursue a career in the aerospace industry after graduating in the spring.

Greenwood, Brian↗
NASA NTRS2008

Early Impacts of a Human-in-the-Loop Evaluation in a Space Vehicle Mock-up Facility

The development of a new space vehicle, the Orion Crew Exploration Vehicle (CEV), provides Human Factors engineers an excellent opportunity to have an impact early in the design process. This case study highlights a Human-in-the-Loop (HITL) evaluation conducted in a Space Vehicle Mock-Up Facility and will describe the human-centered approach and how the findings are impacting design and operational concepts early in space vehicle design. The focus of this HITL evaluation centered on the activities that astronaut crewmembers would be expected to perform within the functional internal volume of the Crew Module (CM) of the space vehicle. The primary objective was to determine if there are aspects of a baseline vehicle configuration that would limit or prevent the performance of dynamically volume-driving activities (e.g. six crewmembers donning their suits in an evacuation scenario). A second objective was to step through concepts of operations for known systems and evaluate them in integrated scenarios. The functional volume for crewmember activities is closely tied to every aspect of system design (e.g. avionics, safety, stowage, seats, suits, and structural support placement). As this evaluation took place before the Preliminary Design Review of the space vehicle with some designs very early in the development, it was not meant to determine definitely that the crewmembers could complete every activity, but rather to provide inputs that could improve developing designs and concepts of operations definition refinement.

Byrne, Vicky↗
NASA NTRS1999

New frontiers in design synthesis

The Intelligent Synthesis Environment (ISE), which is one of the major strategic technologies under development at NASA centers and the University of Virginia, is described. One of the major objectives of ISE is to significantly enhance the rapid creation of innovative affordable products and missions. ISE uses a synergistic combination of leading-edge technologies, including high performance computing, high capacity communications and networking, human-centered computing, knowledge-based engineering, computational intelligence, virtual product development, and product information management. The environment will link scientists, design teams, manufacturers, suppliers, and consultants who participate in the mission synthesis as well as in the creation and operation of the aerospace system. It will radically advance the process by which complex science missions are synthesized, and high-tech engineering Systems are designed, manufactured and operated. The five major components critical to ISE are human-centered computing, infrastructure for distributed collaboration, rapid synthesis and simulation tools, life cycle integration and validation, and cultural change in both the engineering and science creative process. The five components and their subelements are described. Related U.S. government programs are outlined and the future impact of ISE on engineering research and education is discussed.

User-Computer Interface↗
NASA NTRS2004

Human Motion Tracking at Marshall Space Flight Center's Collaborative Engineering Center ANVIL

The installation and use of electromagnetic human motion trackers requires a specially designed and metal-free environment for optimal performance. Such an area is not readily available at the Marshall Space Flight Center Collaborative Engineering Center ANVIL. Our paper details a systems engineering approach to installing and operating Ascension Technologies Ethernet MotionStar tracking system in a sub-optimal environment, used with the JACK human computer model's motion capture capabilities. We also discuss how this system is integrated into the Marshall Space Flight Center's Human Engineering process.

Henderson, Steven J.↗
NASA NTRS2013

Evolution of International Space Station Program Safety Review Processes and Tools

The International Space Station Program at NASA is constantly seeking to improve the processes and systems that support safe space operations. To that end, the ISS Program decided to upgrade their Safety and Hazard data systems with 3 goals: make safety and hazard data more accessible; better support the interconnection of different types of safety data; and increase the efficiency (and compliance) of safety-related processes. These goals are accomplished by moving data into a web-based structured data system that includes strong process support and supports integration with other information systems. Along with the data systems, ISS is evolving its submission requirements and safety process requirements to support the improved model. In contrast to existing operations (where paper processes and electronic file repositories are used for safety data management) the web-based solution provides the program with dramatically faster access to records, the ability to search for and reference specific data within records, reduced workload for hazard updates and approval, and process support including digital signatures and controlled record workflow. In addition, integration with other key data systems provides assistance with assessments of flight readiness, more efficient review and approval of operational controls and better tracking of international safety certifications. This approach will also provide new opportunities to streamline the sharing of data with ISS international partners while maintaining compliance with applicable laws and respecting restrictions on proprietary data. One goal of this paper is to outline the approach taken by the ISS Progrm to determine requirements for the new system and to devise a practical and efficient implementation strategy. From conception through implementation, ISS and NASA partners utilized a user-centered software development approach focused on user research and iterative design methods. The user-centered approach used on the new ISS hazard system utilized focused user research and iterative design methods employed by the Human Computer Interaction Group at NASA Ames Research Center. Particularly, the approach emphasized the reduction of workload associated with document and data management activities so more resources can be allocated to the operational use of data in problem solving, safety analysis, and recurrence control. The methods and techniques used to understand existing processes and systems, to recognize opportunities for improvement, and to design and review improvements are described with the intent that similar techniques can be employed elsewhere in safety operations. A second goal of this paper is to provide and overview of the web-based data system implemented by ISS. The software selected for the ISS hazard systemMission Assurance System (MAS)is a NASA-customized vairant of the open source software project Bugzilla. The origin and history of MAS as a NASA software project and the rationale for (and advantages of) using open-source software are documented elsewhere (Green, et al., 2009).

Ratterman, Christian D.↗
NASA NTRS1989

The use of graphics in the design of the human-telerobot interface

The Man-Systems Telerobotics Laboratory (MSTL) of NASA's Johnson Space Center employs computer graphics tools in their design and evaluation of the Flight Telerobotic Servicer (FTS) human/telerobot interface on the Shuttle and on the Space Station. It has been determined by the MSTL that the use of computer graphics can promote more expedient and less costly design endeavors. Several specific examples of computer graphics applied to the FTS user interface by the MSTL are described.

Stuart, Mark A.↗
NASA NTRS2010

Re-Engineering Complex Legacy Systems at NASA

The Flight Production Process (FPP) Re-engineering project has established a Model-Based Systems Engineering (MBSE) methodology and the technological infrastructure for the design and development of a reference, product-line architecture as well as an integrated workflow model for the Mission Operations System (MOS) for human space exploration missions at NASA Johnson Space Center. The design and architectural artifacts have been developed based on the expertise and knowledge of numerous Subject Matter Experts (SMEs). The technological infrastructure developed by the FPP Re-engineering project has enabled the structured collection and integration of this knowledge and further provides simulation and analysis capabilities for optimization purposes. A key strength of this strategy has been the judicious combination of COTS products with custom coding. The lean management approach that has led to the success of this project is based on having a strong vision for the whole lifecycle of the project and its progress over time, a goal-based design and development approach, a small team of highly specialized people in areas that are critical to the project, and an interactive approach for infusing new technologies into existing processes. This project, which has had a relatively small amount of funding, is on the cutting edge with respect to the utilization of model-based design and systems engineering. An overarching challenge that was overcome by this project was to convince upper management of the needs and merits of giving up more conventional design methodologies (such as paper-based documents and unwieldy and unstructured flow diagrams and schedules) in favor of advanced model-based systems engineering approaches.

Ruszkowski, James↗
NASA NTRS2023

Human Factors Support for On-Orbit Servicing, Assembly and Manufacturing Mission 1 (OSAM-1)

The NASA Engineering and Safety Center (NESC) Human Factors Technical Discipline Team was requested by the Satellite Servicing Projects Division at Goddard Space Flight Center to provide support in assessing the design of the On-Orbit Servicing, Assembly and Manufacturing Mission 1 (OSAM-1) Mission Operations Center in light of concerns about overcrowding and potential for distractions, as well as assistance in creating a Human-Machine Interface style guide for OSAM-1 user interface design. This report contains the outcome of the NESC assessment.

On-Orbit Servicing, Assembly and Manufacturing Mis↗
NASA NTRS2015

SLS Test Stand Site Selection

Test site selection is a critical element of the design, development and production of a new system. With the advent of the new Space Launch System (SLS), the National Aeronautics and Space Administration (NASA) had a number of test site selection decisions that needed to be made early enough in the Program to support the planned Launch Readiness Date (LRD). This case study focuses on decisions that needed to be made in 2011 and 2012 in preparation for the April 2013 DPMC decision about where to execute the Main Propulsion Test that is commonly referred to as "Green Run." Those decisions relied upon cooperative analysis between the Program, the Test Lab and Center Operations. The SLS is a human spaceflight vehicle designed to carry a crew farther into space than humans have previously flown. The vehicle consists of four parts: the crew capsule, the upper stage, the core stage, and the first stage solid rocket boosters. The crew capsule carries the astronauts, while the upper stage, the core stage, and solid rocket boosters provide thrust for the vehicle. In other words, the stages provide the "lift" part of the lift vehicle. In conjunction with the solid rocket boosters, the core stage provides the initial "get-off-the-ground" thrust to the vehicle. The ignition of the four core stage engines and two solid rocket boosters is the first step in the launch portion of the mission. The solid rocket boosters burn out after about 2 minutes of flight, and are then jettisoned. The core stage provides thrust until the vehicle reaches a specific altitude and speed, at which point the core stage is shut off and jettisoned, and the upper stage provides vehicle thrust for subsequent mission trajectories. The integrated core stage primarily consists of a liquid oxygen tank, a liquid hydrogen tank, and the four core stage engines. For the SLS program, four RS-25 engines were selected as the four core stage engines. The RS-25 engine is the same engine that was used for Space Shuttle. The test plan for the integrated core stage was broken down into several segments: Component testing, system level testing, and element level testing. In this context, components are items such as valves, controllers, sensors, etc. Systems are items such as an entire engine, a tank, or the outer stage body. The core stage itself is considered to be an element. The rocket engines are also considered an element. At the program level, it was decided to perform a single green run test on the integrated core stage prior to shipment of it to Kennedy Space Center (KSC) for use in the EM-1 test flight of the SLS vehicle. A green run test is the first live fire of the new integrated core stage and engine elements - without boosters of course. The SLS Program had to decide where to perform SLS green run testing.

Crowe, Kathryn↗
NASA NTRS1993

Functional categories for future flight deck designs

With the addition of each new system on the flight deck, the danger of increasing overall operator workload while reducing crew understanding of critical mission information exists. The introduction of more powerful onboard computers, larger databases, and the increased use of electronic display media may lead to a situation of flight deck 'sophistication' at the expense of losses in flight crew capabilities and situational awareness. To counter this potentially negative impact of new technology, research activities are underway to reassess the flight deck design process. The fundamental premise of these activities is that a human-centered, systems-oriented approach to the development of advanced civil aircraft flight decks will be required for future designs to remain ergonomically sound and economically competitive. One of the initial steps in an integrated flight deck process is to define the primary flight deck functions needed to support the mission goals of the vehicle. This would allow the design team to evaluate candidate concepts in relation to their effectiveness in meeting the functional requirements. In addition, this would provide a framework to aid in categorizing and bookkeeping all of the activities that are required to be performed on the flight deck, not just activities of the crew or of a specific system. This could then allow for a better understanding and allocation of activities in the design, an understanding of the impact of a specific system on overall system performance, and an awareness of the total crew performance requirements for the design. One candidate set of functional categories that could be used to guide an advanced flight deck design are described.

Abbott, Terence S.↗
NASA NTRS2003

NASA's MERBoard: An Interactive Collaborative Workspace Platform

This chapter describes the ongoing process by which a multidisciplinary group at NASA's Ames Research Center is designing and implementing a large interactive work surface called the MERBoard Collaborative Workspace. A MERBoard system involves several distributed, large, touch-enabled, plasma display systems with custom MERBoard software. A centralized server and database back the system. We are continually tuning MERBoard to support over two hundred scientists and engineers during the surface operations of the Mars Exploration Rover Missions. These scientists and engineers come from various disciplines and are working both in small and large groups over a span of space and time. We describe the multidisciplinary, human-centered process by which this h4ERBoard system is being designed, the usage patterns and social interactions that we have observed, and issues we are currently facing.

Trimble, Jay↗
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 NTRS2013

Composite Design and Manufacturing Development for Human Spacecrafts

The Structural Engineering Division at the NASA Johnson Space Center (JSC) has begun work on lightweight, multi‐functional pressurized composite structures. The first candidate vehicle for technology development is the Multi‐Mission Space Exploration Vehicle (MMSEV) cabin, known as the Gen 2B cabin, which has been built at JSC by the Robotics Division. Of the habitable MMSEV vehicle prototypes designed to date, this is the first one specifically analyzed and tested to hold internal pressure and the only one made out of composite materials. This design uses a laminate base with zoned reinforcement and external stringers, intended to demonstrate certain capabilities, and to prepare for the next cabin design, which will be a composite sandwich panel construction with multi‐functional capabilities. As part of this advanced development process, a number of new technologies were used to assist in the design and manufacturing process. One of the methods, new to JSC, was to build the Gen 2B cabin with Out of Autoclave technology to permit the creation of larger parts with fewer joints. An 8‐ply pre‐preg layup was constructed to form the cabin body. Prior to lay‐up, a design optimization software called FiberSIM was used to create each ply pattern. This software is integrated with Pro/Engineer to allow for customized draping of each fabric ply over the complex tool surface. Slits and darts are made in the software model to create an optimal design that maintains proper fiber placement and orientation. The flat pattern of each ply is then exported and sent to an automated cutting table where the patterns are cut out of graphite material. Additionally, to assist in lay‐up, a laser projection system (LPT) is used to project outlines of each ply directly onto the tool face for accurate fiber placement and ply build‐up. Finally, as part of the OoA process, a large oven was procured to post‐cure each part. After manufacturing complete, the cabin underwent modal and pressure testing (currently in progress at date of writing) and will go on to be outfitted and used for further ops usage.

Litteken, Douglas↗
NASA NTRS2003

Robonaut: a robot designed to work with humans in space

The Robotics Technology Branch at the NASA Johnson Space Center is developing robotic systems to assist astronauts in space. One such system, Robonaut, is a humanoid robot with the dexterity approaching that of a suited astronaut. Robonaut currently has two dexterous arms and hands, a three degree-of-freedom articulating waist, and a two degree-of-freedom neck used as a camera and sensor platform. In contrast to other space manipulator systems, Robonaut is designed to work within existing corridors and use the same tools as space walking astronauts. Robonaut is envisioned as working with astronauts, both autonomously and by teleoperation, performing a variety of tasks including, routine maintenance, setting up and breaking down worksites, assisting crew members while outside of spacecraft, and serving in a rapid response capacity.

Man-Machine Systems↗
NASA NTRS1992

Microgravity human factors workstation development

Microgravity evaluations of workstation hardware as well as its system components were found to be very useful for determining the expected needs of the Space Station crew and for refining overall workstation design. Research at the Johnson Space Center has been carried out to provide optimal workstation design and human interface. The research included evaluations of hand controller configurations for robots and free flyers, the identification of cursor control device requirements, and the examination of anthropometric issues of workstation design such as reach, viewing distance, and head clearance.

Whitmore, Mihriban↗
NASA NTRS2010

Constellation Program Human-System Integration Requirements

The Human-Systems Integration Requirements (HSIR) in this document drive the design of space vehicles, their systems, and equipment with which humans interface in the Constellation Program (CxP). These requirements ensure that the design of Constellation (Cx) systems is centered on the needs, capabilities, and limitations of the human. The HSIR provides requirements to ensure proper integration of human-to-system interfaces. These requirements apply to all mission phases, including pre-launch, ascent, Earth orbit, trans-lunar flight, lunar orbit, lunar landing, lunar ascent, Earth return, Earth entry, Earth landing, post-landing, and recovery. The Constellation Program must meet NASA's Agency-level human rating requirements, which are intended to ensure crew survival without permanent disability. The HSIR provides a key mechanism for achieving human rating of Constellation systems.

Dory, Jonathan↗
NASA NTRS1998

Field Guide for Designing Human Interaction with Intelligent Systems

The characteristics of this Field Guide approach address the problems of designing innovative software to support user tasks. The requirements for novel software are difficult to specify a priori, because there is not sufficient understanding of how the users' tasks should be supported, and there are not obvious pre-existing design solutions. When the design team is in unfamiliar territory, care must be taken to avoid rushing into detailed design, requirements specification, or implementation of the wrong product. The challenge is to get the right design and requirements in an efficient, cost-effective manner. This document's purpose is to describe the methods we are using to design human interactions with intelligent systems which support Space Shuttle flight controllers in the Mission Control Center at NASA/Johnson Space Center. Although these software systems usually have some intelligent features, the design challenges arise primarily from the innovation needed in the software design. While these methods are tailored to our specific context, they should be extensible, and helpful to designers of human interaction with other types of automated systems. We review the unique features of this context so that you can determine how to apply these methods to your project Throughout this Field Guide, goals of the design methods are discussed. This should help designers understand how a specific method might need to be adapted to the project at hand.

Malin, Jane T.↗
NASA NTRS1989

The telerobot workstation testbed for the shuttle aft flight deck: A project plan for integrating human factors into system design

The human factors design process in developing a shuttle orbiter aft flight deck workstation testbed is described. In developing an operator workstation to control various laboratory telerobots, strong elements of human factors engineering and ergonomics are integrated into the design process. The integration of human factors is performed by incorporating user feedback at key stages in the project life-cycle. An operator centered design approach helps insure the system users are working with the system designer in the design and operation of the system. The design methodology is presented along with the results of the design and the solutions regarding human factors design principles.

Sauerwein, Timothy↗