Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “standard performance”

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

Eighth Goddard Conference on Mass Storage Systems and Technologies in Cooperation with the Seventeenth IEEE Symposium on Mass Storage Systems

This document contains copies of those technical papers received in time for publication prior to the Eighth Goddard Conference on Mass Storage Systems and Technologies which is being held in cooperation with the Seventeenth IEEE Symposium on Mass Storage Systems at the University of Maryland University College Inn and Conference Center March 27-30, 2000. As one of an ongoing series, this Conference continues to provide a forum for discussion of issues relevant to the management of large volumes of data. The Conference encourages all interested organizations to discuss long term mass storage requirements and experiences in fielding solutions. Emphasis is on current and future practical solutions addressing issues in data management, storage systems and media, data acquisition, long term retention of data, and data distribution. This year's discussion topics include architecture, future of current technology, new technology with a special emphasis on holographic storage, performance, standards, site reports, vendor solutions. Tutorials will be available on stability of optical media, disk subsystem performance evaluation, I/O and storage tuning, functionality and performance evaluation of file systems for storage area networks.

Kobler, Benjamin↗

Finite Element Simulation of Three Full-Scale Crash Tests for Cessna 172 Aircraft

The NASA Emergency Locator Transmitter Survivability and Reliability (ELT-SAR) project was initiated in 2013 to assess the crash performance standards for the next generation of emergency locator transmitter (ELT) systems. Three Cessna 172 aircraft were acquired to perform crash testing at NASA Langley Research Center's Landing and Impact Research Facility. Full-scale crash tests were conducted in the summer of 2015 and each test article was subjected to severe, but survivable, impact conditions including a flare-to-stall during emergency landing, and two controlled-flight-into-terrain scenarios. Full-scale finite element analyses were performed using a commercial explicit solver, ABAQUS. The first test simulated impacting a concrete surface represented analytically by a rigid plane. Tests 2 and 3 simulated impacting a dirt surface represented analytically by an Eulerian grid of brick elements using a Mohr-Coulomb material model. The objective of this paper is to summarize the test and analysis results for the three full-scale crash tests. Simulation models of the airframe which correlate well with the tests are needed for future studies of alternate ELT mounting configurations.

Mason, Brian H.↗

Finite Element Simulation of Three Full-Scale Crash Tests for Cessna 172 Aircraft

The NASA Emergency Locator Transmitter Survivability and Reliability project was initiated in 2013 to assess the crash performance standards for the next generation of emergency locator transmitter (ELT) systems. Three Cessna 172 aircraft were acquired to perform crash testing at the NASA Langley Research Center Landing and Impact Research Facility. Full-scale crash tests were conducted in the summer of 2015 and each test article was subjected to severe, but survivable, impact conditions including a flare-to-stall during emergency landing, and two controlled-flight-into-terrain scenarios. Finite element analyses were performed to numerically simulate the aircraft response to the crash tests. The first test simulated impacting a concrete surface represented analytically by a rigid plane. Tests 2 and 3 simulated impacting a dirt surface represented analytically by an Eulerian grid of bric k elements using a Mohr-Coulomb material model. The objective of this paper is to summarize the test and analysis results for the three full-scale crash tests. Simulation models of the airframe which correlate well with the tests are needed for future studies of alternate ELT mounting configurations.

Finite Element Analysis↗

Finite Element Simulation of Three Full-Scale Crash Tests for Cessna 172 Aircraft

The NASA Emergency Locator Transmitter Survivability and Reliability project was initiated in 2013 to assess the crash performance standards for the next generation of emergency locator transmitter (ELT) systems. Three Cessna 172 aircraft were acquired to perform crash testing at the NASA Langley Research Center Landing and Impact Research Facility. Full-scale crash tests were conducted in the summer of 2015, and each test article was subjected to severe, but survivable, impact conditions including a flare-to-stall during emergency landing and two controlled-flight-into-terrain scenarios. Finite element analyses were performed to numerically simulate the aircraft response to the crash tests. The first test simulated impacting a concrete surface represented analytically by a rigid plane. Tests 2 and 3 simulated impacting a dirt surface represented analytically by an Eulerian grid of brick elements using a Mohr–Coulomb material model. The objective of this paper is to summarize the test and analysis results for the three full-scale crash tests. Simulation models of the airframe that correlate well with the tests are needed for future studies of alternate ELT mounting configurations.

Finite Element Analysis↗

The Rise and Fall of the Type Ib Supernova iPTF13bvn Not a Massive Wolf-Rayet Star

Context. We investigate iPTF13bvn, a core-collapse (CC) supernova (SN) in the nearby spiral galaxy NGC 5806. This object was discovered by the intermediate Palomar Transient Factory (iPTF) very close to the estimated explosion date and was classified as a stripped-envelope CC SN, likely of Type Ib. Furthermore, a possible progenitor detection in pre-explosion Hubble Space Telescope (HST) images was reported, making this the only SN Ib with such an identification. Based on the luminosity and color of the progenitor candidate, as well as on early-time spectra and photometry of the SN, it was argued that the progenitor candidate is consistent with a single, massive Wolf-Rayet (WR) star. Aims. We aim to confirm the progenitor detection, to robustly classify the SN using additional spectroscopy, and to investigate if our follow-up photometric and spectroscopic data on iPTF13bvn are consistent with a single-star WR progenitor scenario. Methods. We present a large set of observational data, consisting of multi-band light curves (UBVRI, g′r′i′z′) and optical spectra. We perform standard spectral line analysis to track the evolution of the SN ejecta. We also construct a bolometric light curve and perform hydrodynamical calculations to model this light curve to constrain the synthesized radioactive nickel mass and the total ejecta mass of the SN. Late-time photometry is analyzed to constrain the amount of oxygen. Furthermore, image registration of pre- and post-explosion HST images is performed. Results. Our HST astrometry confirms the location of the progenitor candidate of iPTF13bvn, and follow-up spectra securely classify this as a SN Ib. We use our hydrodynamical model to fit the observed bolometric light curve, estimating the total ejecta mass to be 1.9 solar mass and the radioactive nickel mass to be 0.05 solar mass. The model fit requires the nickel synthesized in the explosion to be highly mixed out in the ejecta. We also find that the late-time nebular r′-band luminosity is not consistent with predictions based on the expected oxygen nucleosynthesis in very massive stars. Conclusions. We find that our bolometric light curve of iPTF13bvn is not consistent with the previously proposed single massive WR-star progenitor scenario. The total ejecta mass and, in particular, the late-time oxygen emission are both significantly lower than what would be expected from a single WR progenitor with a main-sequence mass of at least 30 solar mass.

massive↗

A Vehicle Management End-to-End Testing and Analysis Platform for Validation of Mission and Fault Management Algorithms to Reduce Risk for NASAs Space Launch System

The engineering development of the National Aeronautics and Space Administration's (NASA) new Space Launch System (SLS) requires cross discipline teams with extensive knowledge of launch vehicle subsystems, information theory, and autonomous algorithms dealing with all operations from pre-launch through on orbit operations. The nominal and off-nominal characteristics of SLS's elements and subsystems must be understood and matched with the autonomous algorithm monitoring and mitigation capabilities for accurate control and response to abnormal conditions throughout all vehicle mission flight phases, including precipitating safing actions and crew aborts. This presents a large and complex systems engineering challenge, which is being addressed in part by focusing on the specific subsystems involved in the handling of off-nominal mission and fault tolerance with response management. Using traditional model-based system and software engineering design principles from the Unified Modeling Language (UML) and Systems Modeling Language (SysML), the Mission and Fault Management (M&FM) algorithms for the vehicle are crafted and vetted in Integrated Development Teams (IDTs) composed of multiple development disciplines such as Systems Engineering (SE), Flight Software (FSW), Safety and Mission Assurance (S&MA) and the major subsystems and vehicle elements such as Main Propulsion Systems (MPS), boosters, avionics, Guidance, Navigation, and Control (GNC), Thrust Vector Control (TVC), and liquid engines. These model-based algorithms and their development lifecycle from inception through FSW certification are an important focus of SLS's development effort to further ensure reliable detection and response to off-nominal vehicle states during all phases of vehicle operation from pre-launch through end of flight. To test and validate these M&FM algorithms a dedicated test-bed was developed for full Vehicle Management End-to-End Testing (VMET). For addressing fault management (FM) early in the development lifecycle for the SLS program, NASA formed the M&FM team as part of the Integrated Systems Health Management and Automation Branch under the Spacecraft Vehicle Systems Department at the Marshall Space Flight Center (MSFC). To support the development of the FM algorithms, the VMET developed by the M&FM team provides the ability to integrate the algorithms, perform test cases, and integrate vendor-supplied physics-based launch vehicle (LV) subsystem models. Additionally, the team has developed processes for implementing and validating the M&FM algorithms for concept validation and risk reduction. The flexibility of the VMET capabilities enables thorough testing of the M&FM algorithms by providing configurable suites of both nominal and off-nominal test cases to validate the developed algorithms utilizing actual subsystem models such as MPS, GNC, and others. One of the principal functions of VMET is to validate the M&FM algorithms and substantiate them with performance baselines for each of the target vehicle subsystems in an independent platform exterior to the flight software test and validation processes. In any software development process there is inherent risk in the interpretation and implementation of concepts from requirements and test cases into flight software compounded with potential human errors throughout the development and regression testing lifecycle. Risk reduction is addressed by the M&FM group but in particular by the Analysis Team working with other organizations such as S&MA, Structures and Environments, GNC, Orion, Crew Office, Flight Operations, and Ground Operations by assessing performance of the M&FM algorithms in terms of their ability to reduce Loss of Mission (LOM) and Loss of Crew (LOC) probabilities. In addition, through state machine and diagnostic modeling, analysis efforts investigate a broader suite of failure effects and associated detection and responses to be tested in VMET to ensure reliable failure detection, and confirm responses do not create additional risks or cause undesired states through interactive dynamic effects with other algorithms and systems. VMET further contributes to risk reduction by prototyping and exercising the M&FM algorithms early in their implementation and without any inherent hindrances such as meeting FSW processor scheduling constraints due to their target platform - the ARINC 6535-partitioned Operating System, resource limitations, and other factors related to integration with other subsystems not directly involved with M&FM such as telemetry packing and processing. The baseline plan for use of VMET encompasses testing the original M&FM algorithms coded in the same C++ language and state machine architectural concepts as that used by FSW. This enables the development of performance standards and test cases to characterize the M&FM algorithms and sets a benchmark from which to measure their effectiveness and performance in the exterior FSW development and test processes. This paper is outlined in a systematic fashion analogous to a lifecycle process flow for engineering development of algorithms into software and testing. Section I describes the NASA SLS M&FM context, presenting the current infrastructure, leading principles, methods, and participants. Section II defines the testing philosophy of the M&FM algorithms as related to VMET followed by section III, which presents the modeling methods of the algorithms to be tested and validated in VMET. Its details are then further presented in section IV followed by Section V presenting integration, test status, and state analysis. Finally, section VI addresses the summary and forward directions followed by the appendices presenting relevant information on terminology and documentation.

Trevino, Luis↗

ACES M and S: Unmitigated Factorial Encounter Study on DAA/TCAS Interoperability

Realization of the expected proliferation of Unmanned Aircraft System (UAS) operations in the National Airspace System (NAS) depends on the development and validation of standards for UAS Detect and Avoid (DAA) Systems. The RTCA Special Committee 228 is charged with leading the development of draft Minimum Operational Performance Standards (MOPS) for UAS DAA Systems. NASA, as a participating member of RTCA SC-228 is committed to supporting the development and validation of draft requirements for DAA alerting and guidance systems. This presentation contains the results of two combinatorial encounter analysis studies using NASA's SAA Control fast-time simulation capability for this purpose. In these studies, encounters between two aircraft were simulated one at a time for the full factorial combination of encounter geometries (e.g., encounter angle, CPA offset) and aircraft performance (e.g., ownership and intruder ground speeds and vertical rates). The first study analyzes the relationships (e.g., timeline) between the different alerting-safety regions in the SC-228 MOPS (in order of increasing severity): 1) DAA warning alert, 2) well clear recovery (WCR) guidance, 3) DAA-Collision Avoidance (CA), and 4) TCAS RA. This study will focus primarily on encounter situations in which TCAS RA occurs prior to any of the other alerting-safety boundaries. In particular, this study will investigate whether using vertical distance or vertical distance at closest point of approach (i.e., vertical miss distance or VMD) is more appropriate for the definition of the DAA-CA region. In addition, cases where transitions between different regions skip an intermediate region will be analyzed. The second study in this presentation explores a proposal to use an altitude rate error threshold to determine if vertical maneuvers are acceptable for DAA WCR guidance against non-cooperative intruders. This study incorporates the radar from the Honeywell sensor model and examines a series of pairwise encounters between a non-cooperative intruder and a UAS ownship, with different combinations of intruder states and ownship performance levels. The study uses SAA Control as a simulation platform and pilot model, and Omnibands to provide DWC recovery guidance. Two simulation sets, one that allows vertical DWC recovery guidance and one that does not, are compared to determine if encounters with altitude rate errors above 250 feet-per-minute are more likely to have more severe losses of well clear, as determined by the Loss of Well-Clear Severity metric.

SaaControl↗

Development of a calibration workstation for SIR-C

The paper describes the status of a comprehensive synthetic aperture radar (SAR) software package developed specifically to aid the calibration of a multifrequency and multipolarization radar like the Shuttle Imaging Radar, SIR-C. The primary data types processed are engineering telemetry, point targets (corner reflectors and polarimetric active radar calibrators), distributed targets (clutter), tone-generators, and ground receivers. The parameters derived to aid the calibration of the production processor include measurements of relative radiometric channel to channel imbalance, absolute calibration constants, antenna pattern corrections, noise levels, polarimetric cross-talk, and geometric offsets. The software reports standard performance measurements such as resolution, peak and integrated sidelobes, radiometric response accuracy, and geometrical distortions such as scale errors, position bias and standard deviation, and image skew. Furthermore, the inclusion of software to allow updates of the shuttle-state vector (position and velocity) is considered.

Madsen, S. N.↗

Project FIRES. Volume 1: Program Overview and Summary, Phase 1B

Overall performance requirements and evaluation methods for firefighters protective equipment were established and published as the Protective Ensemble Performance Standards (PEPS). Current firefighters protective equipment was tested and evaluated against the PEPS requirements, and the preliminary design of a prototype protective ensemble was performed. In phase 1B, the design of the prototype ensemble was finalized. Prototype ensembles were fabricated and then subjected to a series of qualification tests which were based upon the PEPS requirements. Engineering drawings and purchase specifications were prepared for the new protective ensemble.

Abeles, F. J.↗

ISO 15859 Propellant and Fluid Specifications: A Review and Comparison with Military and NASA Specifications

This work presents an overview of the International Organization for Standardization (ISO) 15859 International Standard for Space Systems Fluid Characteristics, Sampling and Test Methods Parts 1 through 13 issued in June 2004. These standards establish requirements for fluid characteristics, sampling, and test methods for 13 fluids of concern to the propellant community and propellant characterization laboratories: oxygen, hydrogen, nitrogen, helium, nitrogen tetroxide, monomethylhydrazine, hydrazine, kerosene, argon, water, ammonia, carbon dioxide, and breathing air. A comparison of the fluid characteristics, sampling, and test methods required by the ISO standards to the current military and NASA specifications, which are in use at NASA facilities and elsewhere, is presented. Many ISO standards composition limits and other content agree with those found in the applicable parts of NASA SE-S-0073, NASA SSP 30573, military performance standards and details, and Compressed Gas Association (CGA) commodity specifications. The status of a current project managed at NASA Johnson Space Center White Sands Test Facility (WSTF) to rewrite these documents is discussed.

Greene, Ben↗

A Vehicle Management End-to-End Testing and Analysis Platform for Validation of Mission and Fault Management Algorithms to Reduce Risk for NASA's Space Launch System

The engineering development of the new Space Launch System (SLS) launch vehicle requires cross discipline teams with extensive knowledge of launch vehicle subsystems, information theory, and autonomous algorithms dealing with all operations from pre-launch through on orbit operations. The characteristics of these spacecraft systems must be matched with the autonomous algorithm monitoring and mitigation capabilities for accurate control and response to abnormal conditions throughout all vehicle mission flight phases, including precipitating safing actions and crew aborts. This presents a large and complex system engineering challenge, which is being addressed in part by focusing on the specific subsystems involved in the handling of off-nominal mission and fault tolerance with response management. Using traditional model based system and software engineering design principles from the Unified Modeling Language (UML) and Systems Modeling Language (SysML), the Mission and Fault Management (M&FM) algorithms for the vehicle are crafted and vetted in specialized Integrated Development Teams (IDTs) composed of multiple development disciplines such as Systems Engineering (SE), Flight Software (FSW), Safety and Mission Assurance (S&MA) and the major subsystems and vehicle elements such as Main Propulsion Systems (MPS), boosters, avionics, Guidance, Navigation, and Control (GNC), Thrust Vector Control (TVC), and liquid engines. These model based algorithms and their development lifecycle from inception through Flight Software certification are an important focus of this development effort to further insure reliable detection and response to off-nominal vehicle states during all phases of vehicle operation from pre-launch through end of flight. NASA formed a dedicated M&FM team for addressing fault management early in the development lifecycle for the SLS initiative. As part of the development of the M&FM capabilities, this team has developed a dedicated testbed that integrates specific M&FM algorithms, specialized nominal and off-nominal test cases, and vendor-supplied physics-based launch vehicle subsystem models. Additionally, the team has developed processes for implementing and validating these algorithms for concept validation and risk reduction for the SLS program. The flexibility of the Vehicle Management End-to-end Testbed (VMET) enables thorough testing of the M&FM algorithms by providing configurable suites of both nominal and off-nominal test cases to validate the developed algorithms utilizing actual subsystem models such as MPS. The intent of VMET is to validate the M&FM algorithms and substantiate them with performance baselines for each of the target vehicle subsystems in an independent platform exterior to the flight software development infrastructure and its related testing entities. In any software development process there is inherent risk in the interpretation and implementation of concepts into software through requirements and test cases into flight software compounded with potential human errors throughout the development lifecycle. Risk reduction is addressed by the M&FM analysis group working with other organizations such as S&MA, Structures and Environments, GNC, Orion, the Crew Office, Flight Operations, and Ground Operations by assessing performance of the M&FM algorithms in terms of their ability to reduce Loss of Mission and Loss of Crew probabilities. In addition, through state machine and diagnostic modeling, analysis efforts investigate a broader suite of failure effects and associated detection and responses that can be tested in VMET to ensure that failures can be detected, and confirm that responses do not create additional risks or cause undesired states through interactive dynamic effects with other algorithms and systems. VMET further contributes to risk reduction by prototyping and exercising the M&FM algorithms early in their implementation and without any inherent hindrances such as meeting FSW processor scheduling constraints due to their target platform - ARINC 653 partitioned OS, resource limitations, and other factors related to integration with other subsystems not directly involved with M&FM such as telemetry packing and processing. The baseline plan for use of VMET encompasses testing the original M&FM algorithms coded in the same C++ language and state machine architectural concepts as that used by Flight Software. This enables the development of performance standards and test cases to characterize the M&FM algorithms and sets a benchmark from which to measure the effectiveness of M&FM algorithms performance in the FSW development and test processes.

Trevino, Luis↗

A Vehicle Management End-to-End Testing and Analysis Platform for Validation of Mission and Fault Management Algorithms to Reduce Risk for NASA's Space Launch System

The development of the Space Launch System (SLS) launch vehicle requires cross discipline teams with extensive knowledge of launch vehicle subsystems, information theory, and autonomous algorithms dealing with all operations from pre-launch through on orbit operations. The characteristics of these systems must be matched with the autonomous algorithm monitoring and mitigation capabilities for accurate control and response to abnormal conditions throughout all vehicle mission flight phases, including precipitating safing actions and crew aborts. This presents a large complex systems engineering challenge being addressed in part by focusing on the specific subsystems handling of off-nominal mission and fault tolerance. Using traditional model based system and software engineering design principles from the Unified Modeling Language (UML), the Mission and Fault Management (M&FM) algorithms are crafted and vetted in specialized Integrated Development Teams composed of multiple development disciplines. NASA also has formed an M&FM team for addressing fault management early in the development lifecycle. This team has developed a dedicated Vehicle Management End-to-End Testbed (VMET) that integrates specific M&FM algorithms, specialized nominal and off-nominal test cases, and vendor-supplied physics-based launch vehicle subsystem models. The flexibility of VMET enables thorough testing of the M&FM algorithms by providing configurable suites of both nominal and off-nominal test cases to validate the algorithms utilizing actual subsystem models. The intent is to validate the algorithms and substantiate them with performance baselines for each of the vehicle subsystems in an independent platform exterior to flight software test processes. In any software development process there is inherent risk in the interpretation and implementation of concepts into software through requirements and test processes. Risk reduction is addressed by working with other organizations such as S&MA, Structures and Environments, GNC, Orion, the Crew Office, Flight Operations, and Ground Operations by assessing performance of the M&FM algorithms in terms of their ability to reduce Loss of Mission and Loss of Crew probabilities. In addition, through state machine and diagnostic modeling, analysis efforts investigate a broader suite of failure effects and detection and responses that can be tested in VMET and confirm that responses do not create additional risks or cause undesired states through interactive dynamic effects with other algorithms and systems. VMET further contributes to risk reduction by prototyping and exercising the M&FM algorithms early in their implementation and without any inherent hindrances such as meeting FSW processor scheduling constraints due to their target platform - ARINC 653 partitioned OS, resource limitations, and other factors related to integration with other subsystems not directly involved with M&FM. The plan for VMET encompasses testing the original M&FM algorithms coded in the same C++ language and state machine architectural concepts as that used by Flight Software. This enables the development of performance standards and test cases to characterize the M&FM algorithms and sets a benchmark from which to measure the effectiveness of M&FM algorithms performance in the FSW development and test processes. This paper is outlined in a systematic fashion analogous to a lifecycle process flow for engineering development of algorithms into software and testing. Section I describes the NASA SLS M&FM context, presenting the current infrastructure, leading principles, methods, and participants. Section II defines the testing philosophy of the M&FM algorithms as related to VMET followed by section III, which presents the modeling methods of the algorithms to be tested and validated in VMET. Its details are then further presented in section IV followed by Section V presenting integration, test status, and state analysis. Finally, section VI addresses the summary and forward directions followed by the appendices presenting relevant information on terminology and documentation.

Trevino, Luis↗

Human Capabilities Assessments for Autonomous Missions: A Multi-Team Research Effort to Reduce Risk in the Human-System Integration Architecture for Future Deep-Space Missions

In future exploration missions beyond low earth-orbit, crew will have to execute complex operations and respond to off-nominal events, without real-time support from Mission Control. It is anticipated that increased reliance on automated systems, including human-centric vehicle and information architecture, will need to be designed to support the crew; increased risk to performance, health, and safety may occur if these are not implemented appropriately. The Human Factors and Behavioral Performance Element (HFBP) in the NASA Human Research Program supports research to characterize and mitigate such human health and performance risks, including the Risk of Adverse Outcome Due to Inadequate Human Systems Integration Architecture (HSIA). The HSIA risk addresses the integration of onboard capability and the crew roles and responsibilities necessary to enable the crew to respond effectively and efficiently in the increasingly autonomous mission operations environment. In 2017, HFBP released the “Human Capabilities Assessments for Autonomous Missions” (HCAAM) research topic to address HSIA related questions. HCAAM is a major NASA research effort that has assembled a multidisciplinary team from seven institutions to work closely with design and engineering efforts on research towards developing and refining human performance standards, guidelines and automation tools. The scientific focus is on quantitative assessment of human capabilities relevant to future deep-space missions during which earth/spacecraft communication is so delayed and intermittent that the crew must be able to function autonomously. The integrated strategy of the HCAAM project characterizes human capabilities and limitations related to potential performance decrements during long duration exploration mission spaceflight as relevant to both routine and complex task performance; defines system characteristics that reduce the likelihood or impact of potential decrements in human performance capabilities; performs integrated assessment of intelligent system responses within the context of an operational environment with relevant NASA tools, systems, and data structures in order to determine positive or negative interactions and validate recommended approaches; and proposes specific updates to existing standards and guidelines for inclusion in NASA handbooks for the design of future spacecraft intelligent systems that provide crew performance assessment/feedback, and to also serve as decision-support aids for the onboard crew (i.e., NASA-STD-3001, and NASA/SP-Human Integration Design Handbook (HIDH)). The scientific research vectors being addressed by the seven HCAAM teams include: - crew task performance (accuracy, efficiency) (crew + automation) - crew performance (accuracy, efficiency) - crew Situation Awareness - procedure design and multi-modal enhancement - concurrent tasking (mixed manual + some level of autonomy) - task handover - crew self-planning and time-lining - task design - trust in automation, real-time calibration - human multi-sensory feedback and guidance - human trust in on-board software-based intelligent assistants - virtual assistants The presentation will highlight plans and progress made in each of these research areas as well as the methods by which surrogate astronaut crews in the NASA JSC HERA spaceflight analog facility will function as human test subjects for all of the HCAAM research projects.

HCAAM VNSCOR↗

On orbit mission planning using the shuttle trajectory and launch window expert system

With the Space Transportation System (STS) entering the operational era, the need for standardized, automated, mission planning computer tools has become apparent. In order to support an increased flight rate without an increase in manpower, quicker and more efficient methods are needed to perform standard tasks. The Shuttle Trajectory and Launch Window Expert System (STALEX) was developed to automate many aspects of early mission planning for space shuttle missions carrying geosynchronous communications satellites. Most of the commercial Shuttle missions planned for the next 3 years will carry at least one of this type of satellite. The applications of STALEX include payload deployment scheduling, launch window analysis, orbital trajectory determination, and landing opportunity selection.

Ahlf, P. R.↗

Terminal Area Test Vector Development

This presentation provides an overview of work being done to develop test vectors for the terminal area, in coordination with RTCA Special Committee 228, an organization developing the Minimum Operational Performance Standards (MOPS) for Unmanned Aircraft Systems (UAS) Detect and Avoid (DAA) systems. The work leverages existing encounter data to develop a set of encounters to be used to define and refine both performance-based and functionally-based terminal area MOPS requirements. The encounter set would be used across various organizations supporting MOPS terminal area requirements development to provide some level of consistency in terms of terminal area assumptions. The work will investigate other potentially applicable data sets and make any similarly needed adjustments to arrive at a consolidated set of terminal area encounters.

terminal area↗

Progress on the Development of the UAS C2 Link and Supporting Spectrum - from LOS to BLOS

In order to provide for the safe integration of unmanned aircraft systems (UAS) into the National Airspace System, the control and non-payload communications (CNPC) link connecting the ground-based pilot with the unmanned aircraft must be highly reliable and robust, based upon standards that enable certification. Both line-of-sight (LOS) links using terrestrial-based communications and beyond-line-of-sight (BLOS) links using satellite communications are required to support UAS operations. The development of standards has been undertaken by RTCA Special Committee 228 (SC-228), with supporting technical data developed by NASA under the UAS in the National Airspace (NAS) Project. As a result of this work minimum operational performance standards (MOPS) have been completed and published for the LOS CNPC system. The second phase of work, for both NASA and RTCA involves the BLOS CNPC systems. The development of technical data to support MOPS development for UAS BLOS satellite-based CNPC links has now been initiated by NASA, and RTCA SC-228 has organized itself to begin the MOPS development process. This paper will provide an overview of the work that has been completed to date by the Communications Subproject in support of LOS C2 communications for UAS followed by an update of plans and progress for the BLOS phase of the project, with the focus on the UAS C2 spectrum aspects.

Pilotless aircraft↗

System Performance of an Integrated Airborne Spacing Algorithm with Ground Automation

The National Aeronautics and Space Administration's (NASA's) first Air Traffic Management (ATM) Technology Demonstration (ATD-1) was created to facilitate the transition of mature ATM technologies from the laboratory to operational use. The technologies selected for demonstration are the Traffic Management Advisor with Terminal Metering (TMA-TM), which provides precise time-based scheduling in the Terminal airspace; Controller Managed Spacing (CMS), which provides controllers with decision support tools to enable precise schedule conformance; and Interval Management (IM), which consists of flight deck automation that enables aircraft to achieve or maintain precise spacing behind another aircraft. Recent simulations and IM algorithm development at NASA have focused on trajectory-based IM operations where aircraft equipped with IM avionics are expected to achieve a spacing goal, assigned by air traffic controllers, at the final approach fix. The recently published IM Minimum Operational Performance Standards describe five types of IM operations. This paper discusses the results and conclusions of a human-in-the-loop simulation that investigated three of those IM operations. The results presented in this paper focus on system performance and integration metrics. Overall, the IM operations conducted in this simulation integrated well with ground-based decisions support tools and certain types of IM operational were able to provide improved spacing precision at the final approach fix; however, some issues were identified that should be addressed prior to implementing IM procedures into real-world operations.

Swieringa, Kurt A.↗

A Cognitive Systems Engineering Approach to Developing HMI Requirements for New Technologies

This document examines the challenges inherent in designing and regulating to support human-automation interaction for new technologies that will deployed into complex systems. A key question for new technologies, is how work will be accomplished by the human and machine agents. This question has traditionally been framed as how functions should be allocated between humans and machines. Such framing misses the coordination and synchronization that is needed for the different human and machine roles in the system to accomplish their goals. Coordination and synchronization demands are driven by the underlying human-automation architecture of the new technology, which are typically not specified explicitly by the designers. The human machine interface (HMI) which is intended to facilitate human-machine interaction and cooperation, however, typically is defined explicitly and therefore serves as a proxy for human-automation cooperation requirements with respect to technical standards for technologies. Unfortunately, mismatches between the HMI and the coordination and synchronization demands of the underlying human-automation architecture, can lead to system breakdowns. A methodology is needed that both designers and regulators can utilize to evaluate the expected performance of a new technology given potential human-automation architectures. Three experiments were conducted to inform the minimum HMI requirements a detect and avoid system for unmanned aircraft systems (UAS). The results of the experiments provided empirical input to specific minimum operational performance standards that UAS manufacturers will have to meet in order to operate UAS in the National Airspace System (NAS). These studies represent a success story for how to objectively and systematically evaluate prototype technologies as part of the process for developing regulatory requirements. They also provide an opportunity to reflect on the lessons learned from a recent research effort in order to improve the methodology for defining technology requirements for regulators in the future. The biggest shortcoming of the presented research program was the absence of the explicit definition, generation and analysis of potential human-automation architectures. Failure to execute this step in the research process resulted in less efficient evaluation of the candidate prototypes technologies in addition to the complete absence of different approaches to human-automation cooperation. For example, all of the prototype technologies that were evaluated in the research program assumed a human-automation architecture that relied on serial processing from the automation to the human. While this type of human-automation architecture is typical across many different technologies and in many different domains, it ignores different architectures where humans and automation work in parallel. Defining potential human-automation architectures a priori also allows regulators to develop scenarios that will stress the performance boundaries of the technology during the evaluation phase. The importance of adding this step of generating and evaluating candidate human-automation architectures prior to formal empirical evaluation is discussed.

human systems integration↗