SEARCH · Search NASA

Results for “assurance case”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 181 records · Page 10

All sources NASA NTRS DOE OSTI

NASA NTRS1990

Project EGRESS: The design of an assured crew return vehicle for the space station

Keeping preliminary studies by NASA in mind, an Assured Crew Return Vehicle (ACRV) was developed. The system allows the escape of one or more crew members from Space Station Freedom in case of emergency. The design of the vehicle addresses propulsion, orbital operations, reentry, landing and recovery, power and communication, and life support. In light of recent modifications in Space Station design, Project EGRESS (Earthbound Guaranteed ReEntry from Space Station) pays particular attention to its impact on Space Station operations, interfaces and docking facilities, and maintenance needs. A water landing, medium lift vehicle was found to best satisfy project goals of simplicity and cost efficiency without sacrificing the safety and reliability requirements. With a single vehicle, one injured crew member could be returned to Earth with minimal pilot involvement. Since the craft is capable of returning up to five crew members, two such permanently docked vehicles would allow full evacuation of the Space Station. The craft could be constructed entirely with available 1990 technology and launched aboard a shuttle orbiter.

Source record↗

NASA NTRS2008

Reliability Practice at NASA Goddard Space Flight Center

This paper describes in brief the Reliability and Maintainability (R&M) Programs performed directly by the reliability branch at Goddard Space Flight Center (GSFC). The mission assurance requirements flow down is explained. GSFC practices for PRA, reliability prediction/fault tree analysis/reliability block diagram, FMEA, part stress and derating analysis, worst case analysis, trend analysis, limit life items are presented. Lessons learned are summarized and recommendations on improvement are identified.

Pruessner, Paula S.↗

NASA NTRS2011

History of POIC Capabilities and Limitations to Conduct International Space Station Payload Operations

Payload science operations on the International Space Station (ISS) have been conducted continuously twenty-four hours per day, 365 days a year beginning February, 2001 and continuing through present day. The Payload Operations Integration Center (POIC), located at the Marshall Space Flight Center in Huntsville, Alabama, has been a leader in integrating and managing NASA distributed payload operations. The ability to conduct science operations is a delicate balance of crew time, onboard vehicle resources, hardware up-mass to the vehicle, and ground based flight control team manpower. Over the span of the last ten years, the POIC flight control team size, function, and structure has been modified several times commensurate with the capabilities and limitations of the ISS program. As the ISS vehicle has been expanded and its systems changed throughout the assembly process, the resources available to conduct science and research have also changed. Likewise, as ISS program financial resources have demanded more efficiency from organizations across the program, utilization organizations have also had to adjust their functionality and structure to adapt accordingly. The POIC has responded to these often difficult challenges by adapting our team concept to maximize science research return within the utilization allocations and vehicle limitations that existed at the time. In some cases, the ISS and systems limitations became the limiting factor in conducting science. In other cases, the POIC structure and flight control team size were the limiting factors, so other constraints had to be put into place to assure successful science operations within the capabilities of the POIC. This paper will present the POIC flight control team organizational changes responding to significant events of the ISS and Shuttle programs.

Grimaldi, Rebecca↗

NASA NTRS2006

The Modern Design of Experiments for Configuration Aerodynamics: A Case Study

The effects of slowly varying and persisting covariate effects on the accuracy and precision of experimental result is reviewed, as is the rationale for run-order randomization as a quality assurance tactic employed in the Modern Design of Experiments (MDOE) to defend against such effects. Considerable analytical complexity is introduced by restrictions on randomization in configuration aerodynamics tests because they involve hard-to-change configuration variables that cannot be randomized conveniently. Tradeoffs are examined between quality and productivity associated with varying degrees of rigor in accounting for such randomization restrictions. Certain characteristics of a configuration aerodynamics test are considered that may justify a relaxed accounting for randomization restrictions to achieve a significant reduction in analytical complexity with a comparably negligible adverse impact on the validity of the experimental results.

DeLoach, Richard↗

NASA NTRS1989

Space shuttle Production Verification Motor 1 (PV-1) static fire

All inspection and instrumentation data indicate that the PV-1 static test firing conducted 18 Aug. 1988 was successful. With the exception of the intentionally flawed joints and static test modifications, PV-1 was flight configuration. Fail-safe flaws guaranteeing pressure to test the sealing capability of primary O-rings were included in the aft field joint, case-to-nozzle joint, and nozzle internal Joint 5. The test was conducted at ambient conditions, with the exception of the field joints and case/nozzle joints which were maintained at a minimum of 75 F. Ballistics performance values were within specification requirements. The PV-1 motor exhibited chamber pressure oscillations similar to previously tested Space Shuttle redesigned solid rocket motors, particularly QM-7. The first longitudinal mode oscillations experienced by PV-1 were the strongest ever measured in a Space Shuttle motor. Investigation into this observation is being conducted. Joint insulation performed as designed with no evidence of gas flow within unflawed forward field joints. The intentionally flawed center and aft case field joint insulation performance was excellent. There was no evidence of hot gas past the center field joint capture feature O-ring, the case-to-nozzle joint primary O-ring, or the aft field joint primary O-ring. O-ring seals and barriers with assured pressure at the flaws showed erosion and heat effect, but all sealed against passage of hot gases with the exception of the aft field joint capture feature O-ring. There was no evidence of erosion, heat effect, or blowby on any O-ring seals or barriers at the unflawed joints. Nozzle performance was nominal with typical erosion. Post-test examination revealed that the forward nose ring was of the old high performance motor design configuration with the 150-deg ply angle. All nozzle components remained intact for post-test evaluation. The thrust vector control system operated correctly. The water deluge system, CO2 quench, and other test equipment performed as planned during all required test operations.

Source record↗

NASA NTRS2009

Evaluation of Margins of Safety in Brazed Joints

One of the essential steps in assuring reliable performance of high cost critical brazed structures is the assessment of the Margin of Safety (MS) of the brazed joints. In many cases the experimental determination of the failure loads by destructive testing of the brazed assembly is not practical and cost prohibitive. In such cases the evaluation of the MS is performed analytically by comparing the maximum design loads with the allowable ones and incorporating various safety or knock down factors imposed by the customer. Unfortunately, an industry standard methodology for the design and analysis of brazed joints has not been developed. This paper provides an example of an approach that was used to analyze an AlBeMet 162 (38%Be-62%Al) structure brazed with the AWS BAlSi-4 (Al-12%Si) filler metal. A practical and conservative interaction equation combining shear and tensile allowables was developed and validated to evaluate an acceptable (safe) combination of tensile and shear stresses acting in the brazed joint. These allowables are obtained from testing of standard tensile and lap shear brazed specimens. The proposed equation enables the assessment of the load carrying capability of complex brazed joints subjected to multi-axial loading.

Flom, Yury↗

NASA NTRS2020

NASA quality assurance in an MBSE world

We explore the impact and consequences of the MBSE Value items discussed above and how they impact the disciplines of quality assurance, reliability and maintainability, system safety, and software assurance. We provide insight into how the MBSE modeling tools can be used to define S&MA processes (ideally as a result of Use Case [1] elaboration of processes represented in MagicDraw®), produce S&MA products (ViewEditor output of various items), and represent S&MA disciplines (S&MA inside of MagicDraw). We also provide insight into the degree to which some elements can be directly integrated into a SysML® model and when, as often happens, an interface to some external source must be provided.

Evans, John W.↗

NASA NTRS2015

Check-Cases for Verification of 6-Degree-of-Freedom Flight Vehicle Simulations

The rise of innovative unmanned aeronautical systems and the emergence of commercial space activities have resulted in a number of relatively new aerospace organizations that are designing innovative systems and solutions. These organizations use a variety of commercial off-the-shelf and in-house-developed simulation and analysis tools including 6-degree-of-freedom (6-DOF) flight simulation tools. The increased affordability of computing capability has made highfidelity flight simulation practical for all participants. Verification of the tools' equations-of-motion and environment models (e.g., atmosphere, gravitation, and geodesy) is desirable to assure accuracy of results. However, aside from simple textbook examples, minimal verification data exists in open literature for 6-DOF flight simulation problems. This assessment compared multiple solution trajectories to a set of verification check-cases that covered atmospheric and exo-atmospheric (i.e., orbital) flight. Each scenario consisted of predefined flight vehicles, initial conditions, and maneuvers. These scenarios were implemented and executed in a variety of analytical and real-time simulation tools. This tool-set included simulation tools in a variety of programming languages based on modified flat-Earth, round- Earth, and rotating oblate spheroidal Earth geodesy and gravitation models, and independently derived equations-of-motion and propagation techniques. The resulting simulated parameter trajectories were compared by over-plotting and difference-plotting to yield a family of solutions. In total, seven simulation tools were exercised.

Murri, Daniel G.↗

NASA NTRS1977

Feeding the feeder

Too often the equipment used to move difficult to handle powdery material from a hopper to process creates a complex of devices whose end result falls short on good performance...simply because equipment design, in many cases, has not kept up with advanced technological concepts in fine powder handling. The Feeder, being the key to an efficient feed system, must be assured a continuous flow from the storage tank...without bridging, arching, spasmodic flow or uncontrolled flushing. The causes and effects of flow problems are discussed and also solutions are offered based on the combination of theoretical and practical experience.

Kurylchek, A. L.↗

NASA NTRS1985

Motivational contracting in space programs - Government and industry prospectives

NASA's Marshall Space Flight Center has used incentive-free policies in contracting for Apollo's Saturn Launch vehicle hardware, as well as award-fee contracts for major development and early production programs in the case of the Space Shuttle Program. These programs have evolved to a point at which multiple incentive fees are useful in motivating cost reductions and assuring timely achievement of delivery requirements and flight mission goals. An examination is presently conducted of the relative success of these motivation-oriented techniques, drawing on the comments of both government and industry personnel.

Clough, D. R.↗

NASA NTRS2010

Obtaining Valid Safety Data for Software Safety Measurement and Process Improvement

We report on a preliminary case study to examine software safety risk in the early design phase of the NASA Constellation spaceflight program. Our goal is to provide NASA quality assurance managers with information regarding the ongoing state of software safety across the program. We examined 154 hazard reports created during the preliminary design phase of three major flight hardware systems within the Constellation program. Our purpose was two-fold: 1) to quantify the relative importance of software with respect to system safety; and 2) to identify potential risks due to incorrect application of the safety process, deficiencies in the safety process, or the lack of a defined process. One early outcome of this work was to show that there are structural deficiencies in collecting valid safety data that make software safety different from hardware safety. In our conclusions we present some of these deficiencies.

Basili, Victor r.↗

NASA NTRS1998

Case-Based Capture and Reuse of Aerospace Design Rationale

The goal of this project is to apply artificial intelligence techniques to facilitate capture and reuse of aerospace design rationale. The project applies case-based reasoning (CBR) and concept mapping (CMAP) tools to the task of capturing, organizing, and interactively accessing experiences or "cases" encapsulating the methods and rationale underlying expert aerospace design. As stipulated in the award, Indiana University and Ames personnel are collaborating on performance of research and determining the direction of research, to assure that the project focuses on high-value tasks. In the first five months of the project, we have made two visits to Ames Research Center to consult with our NASA collaborators, to learn about the advanced aerospace design tools being developed there, and to identify specific needs for intelligent design support. These meetings identified a number of task areas for applying CBR and concept mapping technology. We jointly selected a first task area to focus on: Acquiring the convergence criteria that experts use to guide the selection of useful data from a set of numerical simulations of high-lift systems. During the first funding period, we developed two software systems. First, we have adapted a CBR system developed at Indiana University into a prototype case-based reasoning shell to capture and retrieve information about design experiences, with the sample task of capturing and reusing experts' intuitive criteria for determining convergence (work conducted at Indiana University). Second, we have also adapted and refined existing concept mapping tools that will be used to clarify and capture the rationale underlying those experiences, to facilitate understanding of the expert's reasoning and guide future reuse of captured information (work conducted at the University of West Florida). The tools we have developed are designed to be the basis for a general framework for facilitating tasks within systems developed by the Advanced Design Technologies Testbed (ADTT) project at ARC. The tenets of our framework are (1) that the systems developed should leverage a designer's knowledge, rather than attempting to replace it; (2) that learning and user feedback must play a central role, so that the system can adapt to how it is used, and (3) that the learning and feedback processes must be as natural and as unobtrusive as possible. In the second funding period we will extend our current work, applying the tools to capturing higher-level design rationale.

Leake, David B.↗

NASA NTRS2004

Comparing NASA and ESA Cost Estimating Methods for Human Missions to Mars

To compare working methodologies between the cost engineering functions in NASA Marshall Space Flight Center (MSFC) and ESA European Space Research and Technology Centre (ESTEC), as well as to set-up cost engineering capabilities for future manned Mars projects and other studies which involve similar subsystem technologies in MSFC and ESTEC, a demonstration cost estimate exercise was organized. This exercise was a direct way of enhancing not only cooperation between agencies but also both agencies commitment to credible cost analyses. Cost engineers in MSFC and ESTEC independently prepared life-cycle cost estimates for a reference human Mars project and subsequently compared the results and estimate methods in detail. As a non-sensitive, public domain reference case for human Mars projects, the Mars Direct concept was chosen. In this paper the results of the exercise are shown; the differences and similarities in estimate methodologies, philosophies, and databases between MSFC and ESTEC, as well as the estimate results for the Mars Direct concept. The most significant differences are explained and possible estimate improvements identified. In addition, the Mars Direct plan and the extensive cost breakdown structure jointly set-up by MSFC and ESTEC for this concept are presented. It was found that NASA applied estimate models mainly based on historic Apollo and Space Shuttle cost data, taking into account the changes in technology since then. ESA used models mostly based on European satellite and launcher cost data, taking into account the higher equipment and testing standards for human space flight. Most of NASA's and ESA s estimates for the Mars Direct case are comparable, but there are some important, consistent differences in the estimates for: 1) Large Structures and Thermal Control subsystems; 2) System Level Management, Engineering, Product Assurance and Assembly, Integration and Test/Verification activities; 3) Mission Control; 4) Space Agency Program Level activities.

Hunt, Charles D.↗

NASA NTRS2006

Emerging technologies for V&V of ISHM software for space exploration

Systems1,2 required to exhibit high operational reliability often rely on some form of fault protection to recognize and respond to faults, preventing faults' escalation to catastrophic failures. Integrated System Health Management (ISHM) extends the functionality of fault protection to both scale to more complex systems (and systems of systems), and to maintain capability rather than just avert catastrophe. Forms of ISHM have been utilized to good effect in the maintenance phase of systems' total lifecycles (often referred to as 'condition-based mainte-nance'), but less so in a 'fault protection' role during actual operations. One of the impediments to such use lies in the challenges of verification, validation and certification of ISHM systems themselves. This paper makes the case that state-of-the-practice V&V and certification techniques will not suffice for emerging forms of ISHM systems; however, a number of maturing software engineering assurance technologies show particular promise for addressing these ISHM V&V challenges.

fault detection, isolation, and recovery↗

NASA NTRS2016

Model Based Mission Assurance: NASA's Assurance Future

Model Based Systems Engineering (MBSE) is seeing increased application in planning and design of NASA’s missions. This suggests the question: what will be the corresponding practice of Model Based Mission Assurance (MBMA)? Contemporaneously, NASA’s Office of Safety and Mission Assurance (OSMA) is evaluating a new objectives based approach to standards to ensure that the Safety and Mission Assurance disciplines and programs are addressing the challenges of NASA’s changing missions, acquisition and engineering practices, and technology. MBSE is a prominent example of a changing engineering practice. We use NASA’s objectives-based strategy for Reliability and Maintainability as a means to examine how MBSE will affect assurance. We surveyed MBSE literature to look specifically for these affects, and find a variety of them discussed (some are anticipated, some are reported from applications to date). Predominantly these apply to the early stages of design, although there are also extrapolations of how MBSE practices will have benefits for testing phases. As the effort to develop MBMA continues, it will need to clearly and unambiguously establish the roles of uncertainty and risk in the system model. This will enable a variety of uncertainty-based analyses to be performed much more rapidly than ever before and has the promise to increase the integration of CRM (Continuous Risk Management) and PRA (Probabilistic Risk Analyses) even more fully into the project development life cycle. Various views and viewpoints will be required for assurance disciplines, and an over-arching viewpoint will then be able to more completely characterize the state of the project/program as well as (possibly) enabling the safety case approach for overall risk awareness and communication.

Evans, John↗

NASA NTRSDate not supplied

Runway Sign Classifier: A DAL C Certifiable Machine Learning System

In recent years, the remarkable progress of Machine Learning (ML) technologies within the domain of Artificial Intelligence (AI) systems has presented unprecedented opportunities for the aviation industry, paving the way for further advancements in automation, including the potential for single pilot or fully autonomous operation of large commercial airplanes. However, ML technology faces major incompatibilities with existing airborne certification standards, such as ML model traceability and explainability issues or the inadequacy of traditional coverage metrics. Certification of ML-based airborne systems using current standards is problematic due to these challenges. This paper presents a case study of an airborne system utilizing a Deep Neural Network (DNN) for airport sign detection and classification. Building upon our previous work, which demonstrates compliance with Design Assurance Level (DAL) ”D”, we upgrade the system to meet the more stringent requirements of Design Assurance Level ”C”. To achieve DAL C, we employ an established architectural mitigation technique involving two redundant and dissimilar Deep Neural Networks. The application of novel ML-specific data management techniques further enhances this approach. This work is intended to illustrate how the certification challenges of ML-based systems can be addressed for medium criticality airborne applications.

Flight Software↗

NASA NTRS2011

NASA's Human Rating Requirements - A Historical Interpretive Perspective

Section 3.0 of NASA's Human Rating Requirements for Space Systems, NPR 8705.2, represents technical engineering requirements that the Agenc y requires of Human Space Systems. In many cases the requirements are not unlike requirements for any space system, crewed or uncrewed, th ey deal with successfully accomplishing the mission objectives. Howev er, they go one step further and have requirements that go beyond suc cessful completion of the mission and dictate functions or actions ne cessary to assure the survival of the crew. In that regard they are u nique from other space system requirements. Even with their uniquenes s the technical requirements of the NPR 8705.2 have been relatively u nchanged in overall intent over the revisions. They all have provided for system redundancy, crew habitable environment, crew situational awareness, crew operation, system control, emergency egress and abort systems. In a few cases the intent of the requirement was changed in tentionally, either to restrict certain types of systems or their fun ctions, or to encompass lessons learned from previous programs. For t he most part the requirements are non controversial and represent the current best practices for human space systems, however, a few requi rements are always debated and have evolved over revisions of the NPR due to studies conducted with various programs like the Orbital Spac e Plane and the Constellation Programs. Those requirements will be di scussed using results of trade studies conducted during past programs highlighting how these particular requirements have evolved through the revisions of the NPR. Comments will also be provided for requirem ents that although not debated, have provided challenges in interpret ation.

Langford, Gerald↗

NASA NTRS1990

Project EGRESS: Earthbound Guaranteed Reentry from Space Station. the Design of an Assured Crew Recovery Vehicle for the Space Station

Unlike previously designed space-based working environments, the shuttle orbiter servicing the space station will not remain docked the entire time the station is occupied. While an Apollo capsule was permanently available on Skylab, plans for Space Station Freedom call for a shuttle orbiter to be docked at the space station for no more than two weeks four times each year. Consideration of crew safety inspired the design of an Assured Crew Recovery Vehicle (ACRV). A conceptual design of an ACRV was developed. The system allows the escape of one or more crew members from Space Station Freedom in case of emergency. The design of the vehicle addresses propulsion, orbital operations, reentry, landing and recovery, power and communication, and life support. In light of recent modifications in space station design, Project EGRESS (Earthbound Guaranteed ReEntry from Space Station) pays particular attention to its impact on space station operations, interfaces and docking facilities, and maintenance needs. A water-landing medium-lift vehicle was found to best satisfy project goals of simplicity and cost efficiency without sacrificing safety and reliability requirements. One or more seriously injured crew members could be returned to an earth-based health facility with minimal pilot involvement. Since the craft is capable of returning up to five crew members, two such permanently docked vehicles would allow a full evacuation of the space station. The craft could be constructed entirely with available 1990 technology, and launched aboard a shuttle orbiter.

Source record↗