Results for “assurance case” — Page 18

NASA NTRSDate not supplied

Acquisition of and Access to Research Omics Data

Omics data are essential for understanding the myriad and complex effects of space environments on humans. To assure maximum benefit from these kinds of data, the NASA Human Research Program Data Management Plan stipulates that human omics data should be archived within and accessed through the NASA Life Sciences Portal (NLSP). The NLSP has the capability to acquire and provision access to omics (and other kinds of) research results for individual and ad-hoc groups of subjects at the direction of institutional review boards, or other authorizing bodies or individuals, per institutional, program and investigation-specific policies and procedures. However, because some single-subject omics data, like CT scans and other kinds of large, complex biomedical data, could be used to identify heretofore unknown risks to the subject’s health, or, in certain cases, be used to identify a subject, NASA Policy Directive 7170.1 describes various policies regarding the management of and access to “research genetic testing” data, which includes many kinds of omics data. For example, NPD 7170.1 prohibits access to human research genetic data by NASA personnel who make employment decisions for the subjects from whom the data were obtained. To meet the objective of acquiring research omics data for NLSP in compliance with the policies in NPD 7170.1 and other applicable NASA policies, we designed NOMADS (the NLSP Omics Multimodal Acquisition of Data System), a new component that supports the transfer of large research data files, including research genetic testing data, using one of several different transfer mechanisms. The choice of mechanism is made by the submitter of the data, with guiding information from the system, and is likely to often be determined in large part by the nature and source location of the data. For example, for small files where the source data files are not already stored in a cloud storage system, users are likely to prefer to transfer their data to the NLSP via a web browser. Conversely, for large sets of files already organized and stored in a cloud storage system, users may opt for NOMAD’s cloud-to-cloud transfer method. All omics datasets targeted for the NASA Life Sciences Data Archive must pass a variety of quality checks to ensure data integrity and adherence to the standards defined by the LSDA Data Submission Guidelines (DSG) (see https://nlsp.nasa.gov/explore/lsdahome/datasubmit). These include requirements that data are consistent with open standards established by the omics community. Non-compliant data will not be accepted however archivists are available to advise submitters on how to revise data submissions and re-submit until compliance is achieved. Following compliance with the LSDA DSG, omics data next undergo a variety of additional quality checks to ensure the data meet omics community standards. Domain specific Omics data quality control tools and techniques are continually evolving and linked to the advancements in omics assays utilized and thus, the tools and techniques utilized by the LSDA for data quality control and validation will need to be sustained accordingly. All human omics data will be access controlled according to the policies described above, and requiring IRB approval for any additional access grants once the data are acquired (including access for analysis using the NLSP workspace tools).

Omics↗

NASA NTRS2024

Acquisition of and Access to Research Omics Data

Omics data are essential for understanding the myriad and complex effects of space environments on humans. To assure maximum benefit from these kinds of data, the NASA Human Research Program Data Management Plan stipulates that human omics data should be archived within and accessed through the NASA Life Sciences Portal (NLSP). The NLSP has the capability to acquire and provision access to omics (and other kinds of) research results for individual and ad-hoc groups of subjects at the direction of institutional review boards, or other authorizing bodies or individuals, per institutional, program and investigation-specific policies and procedures. However, because some single-subject omics data, like CT scans and other kinds of large, complex biomedical data, could be used to identify heretofore unknown risks to the subject’s health, or, in certain cases, be used to identify a subject, NASA Policy Directive 7170.1 describes various policies regarding the management of and access to “research genetic testing” data, which includes many kinds of omics data. For example, NPD 7170.1 prohibits access to human research genetic data by NASA personnel who make employment decisions for the subjects from whom the data were obtained. To meet the objective of acquiring research omics data for NLSP in compliance with the policies in NPD 7170.1 and other applicable NASA policies, we designed NOMADS (the NLSP Omics Multimodal Acquisition of Data System), a new component that supports the transfer of large research data files, including research genetic testing data, using one of several different transfer mechanisms. The choice of mechanism is made by the submitter of the data, with guiding information from the system, and is likely to often be determined in large part by the nature and source location of the data. For example, for small files where the source data files are not already stored in a cloud storage system, users are likely to prefer to transfer their data to the NLSP via a web browser. Conversely, for large sets of files already organized and stored in a cloud storage system, users may opt for NOMAD’s cloud-to-cloud transfer method. All omics datasets targeted for the NASA Life Sciences Data Archive must pass a variety of quality checks to ensure data integrity and adherence to the standards defined by the LSDA Data Submission Guidelines (DSG) (see https://nlsp.nasa.gov/explore/lsdahome/datasubmit). These include requirements that data are consistent with open standards established by the omics community. Non-compliant data will not be accepted however archivists are available to advise submitters on how to revise data submissions and re-submit until compliance is achieved. Following compliance with the LSDA DSG, omics data next undergo a variety of additional quality checks to ensure the data meet omics community standards. Domain specific Omics data quality control tools and techniques are continually evolving and linked to the advancements in omics assays utilized and thus, the tools and techniques utilized by the LSDA for data quality control and validation will need to be sustained accordingly. All human omics data will be access controlled according to the policies described above, and requiring IRB approval for any additional access grants once the data are acquired (including access for analysis using the NLSP workspace tools).

Omics↗

NASA NTRSDate not supplied

A Blockchain Case Study for Urban Air Mobility Operational Intent

The next generation of aerial passenger and cargo transportation may leverage the concept of Urban Air Mobility (UAM). UAM is a concept that proposes to develop short-range, point-to-point transportation systems in metropolitan areas using vertical takeoff and landing (VTOL) or short takeoff and landing (STOL) aircraft to overcome increasing surface congestion [1]. The UAM concept leverages a decentralized service-based architecture for airspace solutions. Within the environment, UAM operators work collaboratively to manage aerial vehicles in the urban environment. Providers of Services for UAM (PSU), UAM operators, and Supplemental Data Service Providers (SDSP) provide services to support flight operations within the UAM environment. Also, various views of UAM flight information are provided to the public and public safety entities [2]. The Federal Aviation Administration (FAA) can coordinate flight information between the FAA controlled National Airspace System (NAS) and the UAM environments through the FAA-Industry Data Exchange Protocol (FIDXP). To realize the potential of UAM, an assurance of cybersecurity is critical for public acceptance. Cybersecurity has come to the forefront highlighting the need to protect these networks and systems from cyberattacks. The growth in the development of UAM systems, and the associated data exchange and service interactions will be at risk due to numerous types of cybersecurity attacks. As these threats evolve, the UAM cybersecurity capabilities must adapt to these changes as well [3]. This research focuses on the secure data exchange and storage of this decentralized UAM environment to address these challenges. This research intends to leverage a permissioned blockchain approach to address cybersecurity threats that may impact a UAM environment. Blockchain technologies can be used for tracking transactions and verifying negotiated agreements between stakeholders in the NAS environment. For example, the record of the submitted flight plan and the approved flight plan could be verified using the Blockchain-based immutable ledger.

UAM↗

NASA NTRS2000

Stardust Navigation Covariance Analysis

The Stardust spacecraft was launched on February 7, 1999 aboard a Boeing Delta-II rocket. Mission participants include the National Aeronautics and Space Administration (NASA), the Jet Propulsion Laboratory (JPL), Lockheed Martin Astronautics (LMA) and the University of Washington. The primary objective of the mission is to collect in-situ samples of the coma of comet Wild-2 and return those samples to the Earth for analysis. Mission design and operational navigation for Stardust is performed by the Jet Propulsion Laboratory (JPL). This paper will describe the extensive JPL effort in support of the Stardust pre-launch analysis of the orbit determination component of the mission covariance study. A description of the mission and it's trajectory will be provided first, followed by a discussion of the covariance procedure and models. Predicted accuracy's will be examined as they relate to navigation delivery requirements for specific critical events during the mission. Stardust was launched into a heliocentric trajectory in early 1999. It will perform an Earth Gravity Assist (EGA) on January 15, 2001 to acquire an orbit for the eventual rendezvous with comet Wild-2. The spacecraft will fly through the coma (atmosphere) on the dayside of Wild-2 on January 2, 2004. At that time samples will be obtained using an aerogel collector. After the comet encounter Stardust will return to Earth when the Sample Return Capsule (SRC) will separate and land at the Utah Test Site (UTTR) on January 15, 2006. The spacecraft will however be deflected off into a heliocentric orbit. The mission is divided into three phases for the covariance analysis. They are 1) Launch to EGA, 2) EGA to Wild-2 encounter and 3) Wild-2 encounter to Earth reentry. Orbit determination assumptions for each phase are provided. These include estimated and consider parameters and their associated a-priori uncertainties. Major perturbations to the trajectory include 19 deterministic and statistical maneuvers planned for the mission. The spacecraft is three axis stabilized and has unbalanced thrusters for attitude control. Accelerations due to the attitude control system are treated stochastically. The tracking scenario for the study is patterned after the actual schedule employed during the different phases of the mission. Conventional X-band two-way Doppler and SRA range data was simulated and the standard accuracy for these data types was assumed throughout most of the mission. However, a deweighting scheme was used for the Doppler data during times of low Sun-Earth-Probe angles, especially in the case of the DSM. Optical data is assumed to be available starting at 50 days prior to the comet encounter. The optical data will be used to improve the ephemeris of Wild-2, which is considered crucial to properly target the comet flyby. Results of the covariance analysis are presented for all mission phases. Navigation capability will be discussed in terms of the uncertainty in the encounter B-Plane (B.R and B.T) and linearized time of flight. Delivery errors based on the final maneuver prior to the comet encounter will be presented. The most stringent navigation requirement is for the Earth reentry. The uncertainty in the flight path angle must be less than 0.02 degree (orbit determination and maneuver performance) to assure successful recovery of the SRC. Results presented show that this requirement can be met.

Menon, Premkumar R.↗

NASA NTRS2003

Use of a Prototype Airborne Separation Assurance System for Resolving Near-Term Conflicts During Autonomous Aircraft Operations

NASA is currently investigating a new concept of operations for the National Airspace System, designed to improve capacity while maintaining or improving current levels of safety. This concept, known as Distributed Air/Ground Traffic Management (DAGTM), allows appropriately equipped autonomous aircraft to maneuver freely for flight optimization while resolving conflicts with other traffic and staying out of special use airspace and hazardous weather. In order to perform these tasks, pilots use prototype conflict detection, prevention, and resolution tools, collectively known as an Airborne Separation Assurance System (ASAS). While ASAS would normally allow pilots to resolve conflicts before they become hazardous, evaluation of system performance in sudden, near-term conflicts is needed in order to determine concept feasibility. An experiment was conducted in NASA Langley's Air Traffic Operations Lab to evaluate the prototype ASAS for enabling pilots to resolve near-term conflicts and examine possible operational effects associated with the use of lower separation minimums. Sixteen commercial airline pilots flew a total of 32 traffic scenarios that required them to use prototype ASAS tools to resolve close range pop-up conflicts. Required separation standards were set at either 3 or 5 NM lateral spacing, with 1000 ft vertical separation being used for both cases. Reducing the lateral separation from 5 to 3 NM did not appear to increase operational risk, as indicated by the proximity to the intruder aircraft. Pilots performed better when they followed tactical guidance cues provided by ASAS than when they didn't follow the guidance. In an effort to improve compliance rate, ASAS design changes are currently under consideration. Further studies will of evaluate these design changes and consider integration issues between ASAS and existing Airborne Collision Avoidance Systems (ACAS).

Barhydt, Richard↗

NASA NTRS2004

Suppression of Low Strain Rate Nonpremixed Flames by an Agent

The extinction and structure of non-premixed methane/air flames were investigated in normal gravity and microgravity through the comparison of experiments and calculations using a counterflow configuration. From a fire safety perspective, low strain rate conditions are important for several reasons. In normal gravity, many fires start from small ignition sources where the convective flow and strain rates are weak. Fires in microgravity conditions, such as a manned spacecraft, may also occur in near quiescent conditions where strain rates are very low. When designing a fire suppression system, worst-case conditions should be considered. Most diffusion flames become more robust as the strain rate is decreased. The goal of this project is to investigate the extinction limits of non-premixed flames using various agents and to compare reduced gravity and normal gravity conditions. Experiments at the NASA Glenn Research Center's 2.2-second drop tower were conducted to attain extinction and temperature measurements in low-strain non-premixed flames. Extinction measurements using nitrogen added to the fuel stream were performed for global strain rates from 7/s to 50/s. The results confirmed the "turning point" behavior observed previously by Maruta et al. in a 10 s drop tower. The maximum nitrogen volume fraction in the fuel stream needed to assure extinction for all strain rates was measured to be 0.855+/-0.016, associated with the turning point determined to occur at a strain rate of 15/s. The critical nitrogen volume fraction in the fuel stream needed for extinction of 0-g flames was measured to be higher than that of 1-g flames.

Olson, Sandra L.↗

NASA NTRS1999

Navier-Stokes Analysis of the Flowfield Characteristics of an Ice Contaminated Aircraft Wing

An analytical study was performed as part of the NASA Lewis support of a National Transportation Safety Board (NTSB) aircraft accident investigation. The study was focused on the performance degradation associated with ice contamination on the wing of a commercial turbo-prop-powered aircraft. Based upon the results of an earlier numerical study conducted by the authors, a prominent ridged-ice formation on the subject aircraft wing was selected for detailed flow analysis using 2-dimensional (2-D), as well as, 3-dimensional (3-D) Navier-Stokes computations. This configuration was selected because it caused the largest lift decrease and drag increase among all the ice shapes investigated in the earlier study. A grid sensitivity test was performed to find out the influence of grid spacing on the lift, drag, and associated angle-of-attack for the maximum lift (C(sub lmax)). This study showed that grid resolution is important and a sensitivity analysis is an essential element of the process in order to assure that the final solution is independent of the grid. The 2-D results suggested that a severe stability and control difficulty could have occurred at a slightly higher angle-of-attack (AOA) than the one recorded by the Flight Data Recorder (FDR). This stability and control problem was thought to have resulted from a decreased differential lift on the wings with respect to the normal loading for the configuration. The analysis also indicated that this stability and control problem could have occurred whether or not natural ice shedding took place. Numerical results using an assumed 3-D ice shape showed an increase of the angle at which this phenomena occurred of about 4 degrees. As it occurred with the 2-D case, the trailing edge separation was observed but started only when the AOA was very close to the angle at which the maximum lift occurred.

Chung, J.↗

NASA NTRS2022

SpaceVPX Interoperability Assessment

The existing VMEbus (VersaModular Eurocard bus) International Trade Association (VITA)-78 industry standard, also known as SpaceVPX, is an avionics board- and chassis-level standard derived from the OpenVPX standard as defined in VITA-65. While VITA-65 defines backplane and board-level profiles from COTS vendors to ensure interoperability of products used in developing systems and subsystems, the VITA-78 standard defines SpaceVPX to incorporate fault tolerance features that are required by many spaceflight systems. However, VITA-78 allows so much flexibility that interoperability between modules cannot be assured. This assessment provides guidelines on the use of, and extensions to, the VITA-78 standard to enable avionics interoperability for future NASA missions. The assessment team was comprised of subject matter experts (SMEs) from Goddard Space Flight Center (GSFC), the Jet Propulsion Laboratory (JPL), Johnson Space Center (JSC), and Langley Research Center (LaRC). The team included valuable external consulting support from a SME who was a key participant in the development of the VITA-78 standard. The team had extensive collaboration with the NASA Space Technology Mission Directorate (STMD) High Performance Spaceflight Computing (HPSC) project, specifically in the development of SpaceVPX interconnect findings, observations, and NESC recommendations. To provide an understanding of the breadth of implementations that SpaceVPX must accommodate, multiple NASA use cases were analyzed to assess the requirements for SpaceVPX implementations across a wide range of NASA missions (Appendix C). Applications included crewed missions, science missions, and orbital and surface robotic systems. Product surveys were conducted to assess the level of industry support for SpaceVPX, applications, and the variations in their implementations (Appendix D). In-depth analysis was conducted in the areas of: (a) power management and distribution, (b) form factors and daughtercards, (c) interconnect, and (d) fault tolerance. Leveraging the use cases, product surveys, and SMEs from multiple NASA Centers, these areas were analyzed to determine the range of implementations permitted by the VITA-78 standard and potential interoperability issues. Applicable findings and NESC recommendations were provided for each area. During this assessment, there were multiple opportunities to engage with other agencies to learn about their interest in SpaceVPX, their strategies for implementing SpaceVPX-based systems, and their internal development efforts. These engagements also generated findings and NESC recommendations. Based on this assessment analysis, NESC recommendations were made regarding the feature set and module profiles to support NASA SpaceVPX implementations. This feature set includes restrictions on features in VITA-78, and extensions to the standard. Key recommendations in this area include the use of 10 Gigabit Ethernet and Peripheral Component Interconnect Express (PCIe) as high bandwidth interconnect on the backplane, the retention of SpaceWire interconnect for control functions, and support for 3U (unit) and 6U, form factors for NASA systems. Restrictions were proposed on the usage of user-defined signals to promote interoperability, and specific power managements and distribution schemes for 3U systems. Beyond the technical implementation of SpaceVPX, recommendations were made on areas that warrant further investigation. Primary among these is the recommendation for NASA to collaborate with other space-going agencies and industry to incorporate recommendations into a future ‘dot spec’ of VITA-78. This would ensure wide adoption and availability of the modules that comply with the specification. The assessment includes appendices with candidate module profiles that can be considered as a starting point for this activity, and example systems based on the recommendations. Follow-on studies are recommended for architectures beyond SpaceVPX to address potential enhancements including condensed set of interconnect, software required to implement protocol layers on the interconnect (and other features), alternative power architectures, and system-level testability.

SpaceVPX↗

NASA NTRS2007

Full Life-Cycle Defect Management Assessment: Initial Inspection Data Collection Results and Research Questions for Further Study

It is often the case in software projects that when schedule and budget resources are limited, the Verification and Validation (V&V) activities suffer. Fewer V&V activities can be afforded and moreover, short-term challenges can result in V&V activities being scaled back or dropped altogether. As a result, too often the default solution is to save activities for improving software quality until too late in the life-cycle, relying on late-term code inspections followed by thorough testing activities to reduce defect counts to acceptable levels. As many project managers realize, however, this is a resource-intensive way of achieving the required quality for software. The Full Life-cycle Defect Management Assessment Initiative, funded by NASA s Office of Safety and Mission Assurance under the Software Assurance Research Program, aims to address these problems by: Improving the effectiveness of early life-cycle V&V activities to make their benefits more attractive to team leads. Specifically, we focus on software inspection, a proven method that can be applied to any software work product, long before executable code has been developed; Better communicating this effectiveness to software development teams, along with suggestions for parameters to improve in the future to increase effectiveness; Analyzing the impact of early life-cycle V&V on the effectiveness and cost required for late life-cycle V&V activities, such as testing, in order to make the tradeoffs more apparent. This white paper reports on an initial milestone in this work, the development of a preliminary model of inspection effectiveness across multiple NASA Centers. This model contributes toward reaching our project goals by: Allowing an examination of inspection parameters, across different types of projects and different work products, for an analysis of factors that impact defect detection effectiveness. Allowing a comparison of this NASA-specific model to existing recommendations in the literature regarding how to plan effective inspections. Forming a baseline model which can be extended to incorporate factors describing: the numbers and types of defects that are missed by inspections; how such defects flow downstream through software development phases; how effectively they can be caught by testing activities in the late stages of development. The model has been implemented in a prototype web-enabled decision-support tool which allows developers to enter their inspection data and receive feedback based on a comparison against the model. The tool also allows users to access reusable materials (such as checklists) from projects included in the baseline. Both the tool itself and the model underlying it will continue to be extended throughout the remainder of this initiative. As results of analyzing inspection effectiveness for defect containment are determined, they can be shared via the tool and also via updates to existing training courses on metrics and software inspections. Moreover, the tool will help satisfy key CMMI requirements for the NASA Centers, as it will enable NASA to take a global view across peer review results for various types of projects to identify systemic problems. This analysis can result in continuous improvements to the approach to verification.

Shull, Forrest↗

NASA NTRS2014

Evaluation of Polymer Hermetically Sealed Tantalum Capacitors

Polymer cathode tantalum capacitors have lower ESR (equivalent series resistance) compared to other types of tantalum capacitors and for this reason have gained popularity in the electronics design community. Their use allows improved performance of power supply systems along with substantial reduction of size and weight of the components used. However, these parts have poor thermal stability and can degrade in humid environments. Polymer hermetically sealed (PHS) capacitors avoid problems related to environmental degradation of molded case parts and can potentially replace current wet and solid hermetically sealed capacitors. In this work, PHS capacitors manufactured per DLA LAM DWG#13030 are evaluated for space applications. Several lots of capacitors manufactured over period from 2010 to 2014 were tested for the consistency of performance, electrical and thermal characteristics, highly accelerated life testing, and robustness under reverse bias and random vibration conditions. Special attention was given to analysis of leakage currents and the effect of long-term high temperature storage on capacitors in as is condition and after hermeticity loss. The results show that PHS capacitors might be especially effective for low-temperature applications or for system requiring a cold start-up. Additional screening and qualification testing have been recommended to assure the necessary quality of capacitors for space projects.

ferrite beads↗

NASA NTRS2005

A Review of Diagnostic Techniques for ISHM Applications

System diagnosis is an integral part of any Integrated System Health Management application. Diagnostic applications make use of system information from the design phase, such as safety and mission assurance analysis, failure modes and effects analysis, hazards analysis, functional models, fault propagation models, and testability analysis. In modern process control and equipment monitoring systems, topological and analytic , models of the nominal system, derived from design documents, are also employed for fault isolation and identification. Depending on the complexity of the monitored signals from the physical system, diagnostic applications may involve straightforward trending and feature extraction techniques to retrieve the parameters of importance from the sensor streams. They also may involve very complex analysis routines, such as signal processing, learning or classification methods to derive the parameters of importance to diagnosis. The process that is used to diagnose anomalous conditions from monitored system signals varies widely across the different approaches to system diagnosis. Rule-based expert systems, case-based reasoning systems, model-based reasoning systems, learning systems, and probabilistic reasoning systems are examples of the many diverse approaches ta diagnostic reasoning. Many engineering disciplines have specific approaches to modeling, monitoring and diagnosing anomalous conditions. Therefore, there is no "one-size-fits-all" approach to building diagnostic and health monitoring capabilities for a system. For instance, the conventional approaches to diagnosing failures in rotorcraft applications are very different from those used in communications systems. Further, online and offline automated diagnostic applications are integrated into an operations framework with flight crews, flight controllers and maintenance teams. While the emphasis of this paper is automation of health management functions, striking the correct balance between automated and human-performed tasks is a vital concern.

Patterson-Hine, Ann↗

NASA NTRS2015

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↗

NASA NTRS2022

A Framework for Dynamic Architecture and Functional Allocations for Increasing Airspace Autonomy

To enable scalability of air travel for use cases such as cargo delivery, it is anticipated that future air traffic operations will involve unmanned aircraft operated by remote pilots. Of particular interest are schemes where a small number of pilots operate a large number of vehicles, mitigating high cost and pilot shortage issues. Such architectures require increased levels of automation and supervisory control modes. They also require ensuring safe operations when the command and control link to the vehicle is degraded or lost completely, rendering the vehicle autonomous. To evaluate these variable and dynamic architectures, this paper will present a framework for decomposing the functions necessary to ensure safe, orderly, and expeditious air travel, assessing the agents in the system, and classifying the levels of autonomy. Then, an example allocation to agents of roles for the function of separation assurance is presented, highlighting the dependency of the allocation on three main factors: time criticality of a potential separation violation, the ratio of pilots to vehicles, and the loss of the command and control link.

air traffic management, function allocation, auton↗

NASA NTRS2022

A Framework for Dynamic Architecture and Functional Allocations for Increasing Airspace Autonomy

To enable scalability of air travel for use cases such as cargo delivery, it is anticipated that future air traffic operations will involve unmanned aircraft operated by remote pilots. Of particular interest are schemes where a small number of pilots operate a large number of vehicles, mitigating high cost and pilot shortage issues. Such architectures require increased levels of automation and supervisory control modes. They also require ensuring safe operations when the command and control link to the vehicle is degraded or lost completely, rendering the vehicle autonomous. To evaluate these variable and dynamic architectures, this paper will present a framework for decomposing the functions necessary to ensure safe, orderly, and expeditious air travel, assessing the agents in the system, and classifying the levels of autonomy. Then, an example allocation to agents of roles for the function of separation assurance is presented, highlighting the dependency of the allocation on three main factors; time criticality of a potential separation violation, the ratio of pilots to vehicles, and the loss of the command and control link.

air traffic management↗

NASA NTRS2002

Regaining Lost Separation in a Piloted Simulation of Autonomous Aircraft Operations

NASA is currently investigating a new concept of operations for the National Airspace System, designed to improve capacity while maintaining or improving current levels of safety. This concept, known as Distributed Air/Ground Traffic Management (DAG-TM), allows appropriately equipped autonomous aircraft to maneuver freely for flight optimization while resolving conflicts with other traffic and staying out of special use airspace and hazardous weather. While Airborne Separation Assurance System (ASAS) tools would normally allow pilots to resolve conflicts before they become hazardous, evaluation of system performance in sudden, near-term conflicts is needed in order to determine concept feasibility. If an acceptable safety level can be demonstrated in these situations, then operations may be conducted with lower separation minimums. An experiment was conducted in NASA Langley s Air Traffic Operations Lab to address issues associated with resolving near-term conflicts and the potential use of lower separation minimums. Sixteen commercial airline pilots flew a total of 32 traffic scenarios that required them to use prototype ASAS tools to resolve close range pop-up conflicts. Required separation standards were set at either 3 or 5 NM lateral spacing, with 1000 ft vertical separation being used for both cases. Reducing the lateral separation from 5 to 3 NM did not appear to increase operational risk, as indicated by the proximity to the intruder aircraft. Pilots performed better when they followed tactical guidance cues provided by ASAS than when they didn't follow the guidance. As air-air separation concepts are evolved, further studies will consider integration issues between ASAS and existing Airborne Collision Avoidance Systems (ACAS).These types of non-normal events will require the ASAS to provide effective alerts and resolutions prior to the time that an Airborne Collision Avoidance System (ACAS) would give a Resolution Advisory (RA). When an RA is issued, a pilot must take immediate action in order to avoid a potential near miss. The Traffic Alert and Collision Avoidance System (TCAS) II currently functions as an ACAS aboard commercial aircraft. Depending on the own aircraft s altitude, TCAS only issues RA s 15-35 seconds prior to the Closest Point of Approach (CPA). Prior to an RA, DAG-TM pilots operating autonomous aircraft must rely solely on ASAS for resolution guidance. An additional area of DAG-TM concept feasibility relates to a potential reduction in separation standards. Lower separation standards are likely needed in order to improve NAS efficiency and capacity. Current separation minimums are based in large part on the capabilities of older radar systems. Safety assessments are needed to determine the feasibility of reduced separation minimums. They will give strong consideration to surveillance system performance, including accuracy, integrity, and availability. Candidate surveillance systems include Automatic Dependent Surveillance-Broadcast (ADS-B) and multi-lateration systems. Considering studies done for Reduced Vertical Separation Minimums (RVSM) operations, it is likely that flight technical errors will also be considered. In addition to a thorough evaluation of surveillance system performance, a potential decision to lower the separation standards should also take operational considerations into account. An ASAS Safety Assessment study identified improper maneuvering in response to a conflict (due to ambiguous or improper resolution commands or a pilot s failure to comply with the resolution) as a potential safety risk. If near-term conflicts with lower separation minimums were determined to be more challenging for pilots, the severity of these risks could be even greater.

Barhydt, Richard↗

NASA NTRS2006

Evaluation of Risk and Possible Mitigation Schemes for Previously Unidentified Hazards

In April 2004, the NASA Engineering and Safety Center (NESC) was commissioned by NASA's Chief Safety and Mission Assurance (S&MA) Officer to review and render a technical opinion on the probability of a catastrophic failure related to this scenario: The Space Shuttle Program (SSP) recognized a zero-fault-tolerant design related to an inadvertent firing of the primary reaction control system (RCS) jets on the Orbiter during mated operations with the International Space Station (ISS). It was determined that an un-commanded firing of an RCS jet could cause serious damage or loss of both the SSP Orbiter and the ISS. Several scenarios were suggested in which an un-commanded firing of the RCS jet is possible. These scenarios include an arc track event in the 28-volt heater circuits that could result in a wire-to-wire short to the adjacent reaction control jet wire. In this worst-case scenario, enough current and power could be applied to activate the reaction control jet valves and fire a thruster. The following report summarizes the work that was sponsored by the NESC as part of their assessment of the Orbiter inadvertent firing of a RCS thruster while attached to the ISS.

Linzey, William↗

NASA NTRS1975

Interim Report of the Astronomy Spacelab Payloads Study: Ultraviolet and Optical Astronomy - Volume 2

The Space Shuttle will comprise NASA's primary transportation system into near-earth orbit during the 1980s. The Shuttle will provide the astronomical community with a major new capability to send a wide variety of instrumentation into orbit, to utilize it there under manned or automatic control for periods from seven to thirty days, and to return it to the ground. To this end the European Space Research Organization (ESRO) is developing Spacelab, an array of interchangeable components -pressurized manned modules, unpressurized pallets and related support systems - to be mounted in the Shuttle payload bay. Spacelab will offer important opportunities to carry out astronomical research with instruments optimized for specific objectives. With a high flight frequency and with the ability to modify or interchange telescopes and instruments between flights, one will not need to make rigid long-term commitments to specific and compromised telescope/instrument/ detector combinations as is the case for automated satellites. Observational techniques demanding the physical return of data and equipment - in particular the use of photographic film, instruments requiring tight calibration controls, cryogens, high-risk detectors and degradeable optical coatings -will open research areas not readily addressed by automated satellites. Although Shuttle flight duration will be limited to periods from seven to thirty days, substantial data can be obtained with a single instrument on short missions, if targets are carefully selected and prioritized, and a large number of instruments can be accommodated on a single flight. Important astronomical data are regularly obtained on sounding rocket flights of five minutes duration. Spacelab will provide far longer observing periods for large and small telescopes, with resources greatly exceeding those of sounding rockets, while retaining much of the sounding rocket philosophy in terms of instrument flexibility, simplicity, reliability assurance and development costs. The Ultraviolet and Optical Astronomy Program on Spacelab is being planned to provide optical astronomers with relatively simple and regular access to the extended wavelength coverage, the superior image quality and the darkness of the night sky available above the earth's atmosphere. In a rapidly evolving science one cannot predict what problems will be timely in the 1980s. Extrapolating from the current epoch, however, one can envision a continuing interest in such areas as the structure, composition and phenomenology of planetary surfaces and atmospheres; the composition and physical nature of the interstellar medium; the composition, structure and life history of stars, especially those in advanced stages of evolution; the stellar population of other galaxies; such enigmatic phenomena as X-ray binary black holes, pulsars, active galactic nuclei and quasars; large scale interactions between galaxies and the nature of the intergalactic medium; precise calibration of the Hubble law for the expansion of the universe; the average density of the universe; and the existence of extraterrestrial life.

Source record↗

NASA NTRS1996

CFD Analysis of the 24-inch JIRAD Hybrid Rocket Motor

A series of multispecies, multiphase computational fluid dynamics (CFD) analyses of the 24-inch diameter joint government industry industrial research and development (JIRAD) hybrid rocket motor is described. The 24-inch JIRAD hybrid motor operates by injection of liquid oxygen (LOX) into a vaporization plenum chamber upstream of ports in the hydroxyl-terminated polybutadiene (HTPB) solid fuel. The injector spray pattern had a strong influence on combustion stability of the JIRAD motor so a CFD study was initiated to define the injector end flow field under different oxidizer spray patterns and operating conditions. By using CFD to gain a clear picture of the flow field and temperature distribution within the JIRAD motor, it is hoped that the fundamental mechanisms of hybrid combustion instability may be identified and then suppressed by simple alterations to the oxidizer injection parameters such as injection angle and velocity. The simulations in this study were carried out using the General Algorithm for Analysis of Combustion SYstems (GALACSY) multiphase combustion codes. GALACSY consists of a comprehensive set of droplet dynamic submodels (atomization, evaporation, etc.) and a computationally efficient hydrocarbon chemistry package built around a robust Navier-Stokes solver optimized for low Mach number flows. Lagrangian tracking of dispersed particles describes a closely coupled spray phase. The CFD cases described in this paper represent various levels of simplification of the problem. They include: (A) gaseous oxygen with combusting fuel vapor blowing off the walls at various oxidizer injection angles and velocities, (B) gaseous oxygen with combusting fuel vapor blowing off the walls, and (C) liquid oxygen with combusting fuel vapor blowing off the walls. The study used an axisymmetric model and the results indicate that the injector design significantly effects the flow field in the injector end of the motor. Markedly different recirculation patterns are observed in the vaporization chamber as the oxygen velocity and/or spray pattern is varied. The ability of these recirculation patterns to stabilize the diffusion flame above the surface of the solid fuel gives a plausible explanation for the experimentally determined combustion stability characteristics of the JIRAD motor, and suggests how combustion stability can be assured by modifications to the injector design.

Liang, Pak-Yan↗