Search NASA⌕ Search

SEARCH · Search NASA

Results for “CERTIFICATION”

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 55 records · Page 3

Experimental control in software reliability certification

There is growing interest in software 'certification', i.e., confirmation that software has performed satisfactorily under a defined certification protocol. Regulatory agencies, customers, and prospective reusers all want assurance that a defined product standard has been met. In other industries, products are typically certified under protocols in which random samples of the product are drawn, tests characteristic of operational use are applied, analytical or statistical inferences are made, and products meeting a standard are 'certified' as fit for use. A warranty statement is often issued upon satisfactory completion of a certification protocol. This paper outlines specific engineering practices that must be used to preserve the validity of the statistical certification testing protocol. The assumptions associated with a statistical experiment are given, and their implications for statistical testing of software are described.

Trammell, Carmen J.↗

Human factors certification in the development of future air traffic control systems

If human factors certification of aviation technologies aims to encompass the wide range of issues which need to be addressed for any new system, then human factors involvement must be present throughout the whole design process in a manner which relates to final certification. A certification process cannot simply be applied to the final product of design. Standards and guidelines will be required by designers at the outset of design for reference in preparing for certification. The most effective use of human factors principles, methods, and measures is made as part of an iterative design process, leading to a system which reflects these as far as possible. This particularly applies where the technology is complex and may be represented by a number of components or sub-systems. Some aspects of the system are best certified during early prototyping, when there is still scope to make changes to software or hardware. At this stage in design, financial and/or time pressures will not rule out the possibility of necessary changes, as may be the case later. Other aspects of the system will be best certified during the final phases of design when the system is in a more complete form and in a realistic environment.

Evans, Alyson E.↗

Midcourse Space Experiment Data Certification and Technology Transfer

The University of Alabama in Huntsville contributes to the Technical Management of the Midcourse Space Experiment Program, to the Certification of the Level 2 data produced by the Midcourse Space Experiment's suite of in-orbit imaging radiometers, imaging spectro-radiometers and an interferometer and to the Transfer of the Midcourse Space Experiment Technology to other Government Programs. The Technical Management of the Midcourse Space Experiment Program is expected to continue through out the spacecraft's useful life time. The Transfer of Midcourse Space Experiment Technology to other government elements is expected to be on a demand basis by the United States Government and other organizations. The University, of Alabama Huntsville' contribution specifically supports the Principal Investigator's Executive Committee, the Deputy Principal Investigator for Data Certification and Technology Transfer team, the nine Ultraviolet Visible Imagers and Spectrographic Imagers (UVISI) and the Pointing and Alignment of all eleven of the science instruments. The science instruments effectively cover the 0.1 to 28 micron spectral region. The Midcourse Space Experiment spacecraft, launched April 24, 1996, is expected to have a 5 year useful lifetime. The cryogenically cooled IR sensor, SPIRIT III, performed through February, 1997 when its cryogen expired. A pre-launch, ground based calibration of the instruments provided a basis for the pre-launch certification of the Level 2 data base these instruments produce. With the spacecraft in-orbit the certification of the instrument's Level 2 data base was extended to the in-orbit environment.

Pollock, David B.↗

Certification Processes for Safety-Critical and Mission-Critical Aerospace Software

This document is a quick reference guide with an overview of the processes required to certify safety-critical and mission-critical flight software at selected NASA centers and the FAA. Researchers and software developers can use this guide to jumpstart their understanding of how to get new or enhanced software onboard an aircraft or spacecraft. The introduction contains aerospace industry definitions of safety and safety-critical software, as well as, the current rationale for certification of safety-critical software. The Standards for Safety-Critical Aerospace Software section lists and describes current standards including NASA standards and RTCA DO-178B. The Mission-Critical versus Safety-Critical software section explains the difference between two important classes of software: safety-critical software involving the potential for loss of life due to software failure and mission-critical software involving the potential for aborting a mission due to software failure. The DO-178B Safety-critical Certification Requirements section describes special processes and methods required to obtain a safety-critical certification for aerospace software flying on vehicles under auspices of the FAA. The final two sections give an overview of the certification process used at Dryden Flight Research Center and the approval process at the Jet Propulsion Lab (JPL).

Nelson, Stacy↗

Certification Processes for Safety-Critical and Mission-Critical Aerospace Software

This document is a quick reference guide with an overview of the processes required to certify safety-critical and mission-critical flight software at selected NASA centers and the FAA. Researchers and software developers can use this guide to jumpstart their understanding of how to get new or enhanced software onboard an aircraft or spacecraft. The introduction contains aerospace industry definitions of safety and safety-critical software, as well as, the current rationale for certification of safety-critical software. The Standards for Safety-Critical Aerospace Software section lists and describes current standards including NASA standards and RTCA DO-178B. The Mission-Critical versus Safety-Critical software section explains the difference between two important classes of software: safety-critical software involving the potential for loss of life due to software failure and mission-critical software involving the potential for aborting a mission due to software failure. The DO-178B Safety-critical Certification Requirements section describes special processes and methods required to obtain a safety-critical certification for aerospace software flying on vehicles under auspices of the FAA. The final two sections give an overview of the certification process used at Dryden Flight Research Center and the approval process at the Jet Propulsion Lab (JPL).

Nelson, Stacy↗

Classification of Unmanned Aircraft Systems. UAS Classification/Categorization for Certification

Category, class, and type designations are primary means to identify appropriate aircraft certification basis, operating rules/limitations, and pilot qualifications to operate in the National Airspace System (NAS). The question is whether UAS fit into existing aircraft categories or classes, or are unique enough to justify the creation of a new category/class. In addition, the characteristics or capabilities, which define when an UAS becomes a regulated aircraft, must also be decided. This issue focuses on UAS classification for certification purposes. Several approaches have been considered for classifying UAS. They basically group into either using a weight/mass basis, or a safety risk basis, factoring in the performance of the UAS, including where the UAS would operate. Under existing standards, aircraft must have a Type Certificate and Certificate of Airworthiness, in order to be used for "compensation or hire", a major difference from model aircraft. Newer technologies may make it possible for very small UAS to conduct commercial services, but that is left for a future discussion to extend the regulated aircraft to a lower level. The Access 5 position is that UAS are aircraft and should be regulated above the weight threshold differentiating them from model airplanes. The recommended classification grouping is summarized in a chart.

Source record↗

Human Systems Integration: Unmanned Aircraft Control Station Certification Plan Guidance

This document provides guidance to the FAA on important human factors considerations that can be used to support the certification of a UAS Aircraft Control Station (ACS). This document provides a synopsis of the human factors analysis, design and test activities to be performed to provide a basis for FAA certification. The data from these analyses, design activities, and tests, along with data from certification/qualification tests of other key components should be used to establish the ACS certification basis. It is expected that this information will be useful to manufacturers in developing the ACS Certification Plan,, and in supporting the design of their ACS.

Source record↗

Certification of COTS Software in NASA Human Rated Flight Systems

Adoption of commercial off-the-shelf (COTS) products in safety critical systems has been seen as a promising acquisition strategy to improve mission affordability and, yet, has come with significant barriers and challenges. Attempts to integrate COTS software components into NASA human rated flight systems have been, for the most part, complicated by verification and validation (V&V) requirements necessary for flight certification per NASA s own standards. For software that is from COTS sources, and, in general from 3rd party sources, either commercial, government, modified or open source, the expectation is that it meets the same certification criteria as those used for in-house and that it does so as if it were built in-house. The latter is a critical and hidden issue. This paper examines the longstanding barriers and challenges in the use of 3rd party software in safety critical systems and cover recent efforts to use COTS software in NASA s Multi-Purpose Crew Vehicle (MPCV) project. It identifies some core artifacts that without them, the use of COTS and 3rd party software is, for all practical purposes, a nonstarter for affordable and timely insertion into flight critical systems. The paper covers the first use in a flight critical system by NASA of COTS software that has prior FAA certification heritage, which was shown to meet the RTCA-DO-178B standard, and how this certification may, in some cases, be leveraged to allow the use of analysis in lieu of testing. Finally, the paper proposes the establishment of an open source forum for development of safety critical 3rd party software.

Goforth, Andre↗

Certification of Safety-Critical Software Under DO-178C and DO-278A

The RTCA has recently released DO-178C and DO-278A as new certification guidance for the production of airborne and ground-based air traffic management software, respectively. Additionally, RTCA special committee SC-205 has also produced, at the same time, five other companion documents. These documents are RTCA DO-248C, DO-330, DO-331, DO- 332, and DO-333. These supplements address frequently asked questions about software certification, provide guidance on tool qualification requirements, and illustrate the modifications recommended to DO-178C when using model-based software design, object oriented programming, and formal methods. The objective of this paper is to first explain the relationship of DO-178C to the former DO-178B in order to give those familiar with DO- 178B an indication of what has been changed and what has not been changed. With this background, the relationship of DO-178C and DO-278 to the new DO-278A document for ground-based software development is shown. Last, an overview of the new guidance contained in the tool qualification document and the three new supplements to DO-178C and DO-278A is presented. For those unfamiliar with DO-178B, this paper serves to provide an entry point to this new certification guidance for airborne and ground-based CNS/ATM software certification.

Jacklin, Stephen A.↗

An Operational Safety and Certification Assessment of a TASAR EFB Application

This paper presents an overview of a Traffic Aware Strategic Aircrew Requests (TASAR) Electronic Flight Bag application intended to inform the pilot of trajectory improvement opportunities while en route that result in operational benefits. The results of safety analyses and a detailed review of Federal Aviation Administration (FAA) regulatory documents that establish certification and operational approval requirements are presented for TASAR. The safety analyses indicate that TASAR has a likely Failure Effects Classification of “No Effect,” and at most, is no worse than “Minor Effect.” Based on this safety assessment and the detailed review of FAA regulatory documents that determine certification and operational approval requirements, this study concludes that TASAR can be implemented in the flight deck as a Type B software application hosted on a Class 2 Portable Electronic Device (PED) Electronic Flight Bag (EFB). This implementation approach would provide a relatively low-cost path to certification and operational approval for both retrofit and forward fit implementation, while at the same time facilitating the business case for early ADS-B IN equipage. A preliminary review by FAA certification and operational approvers of the analyses presented here confirmed that the conclusions are appropriate and that TASAR will be considered a Type B application.

Koczo, Stefan↗

Recommendations on Evidence and Process for Certification of Learning-enabled Components in Aerospace Systems

This report primarily identifies a collection of relevant and necessary evidence for assurance of machine learnt components (MLCs)—also known as learning-enabled components—integrated into aircraft systems, and gives preliminary suggestions on the elements of a certification process that invoke the identified evidence. The main focus is on feedforward neural networks that are static and trained offline through supervised learning. A brief background on the generic elements of the lifecycle of an MLC is given to contextualize the assurance considerations and, consequently, the evidence that is relevant and necessary to support certification. At the level of an MLC, those considerations relate to: (i) the consistency and correctness of MLC contributions to system functions in the context of a validated functional intent; and (ii) the absence of MLC contributions to aircraft-level failure conditions. At an ML model level, confidence in model and data properties contribute to assurance of the containing MLC, in particular: (a) generalizability and robustness of models, in the presence of inputs not previously seen during training, disturbances to inputs, and unexpected inputs; and (b) valid data, i.e., data that are at least representative, relevant, complete, and accurate. Evidence for the above span the elements of the ML lifecycle, and includes, at a minimum, lifecycle artifacts that pertain to: (1) properties of requirements capturing functional intent, safety constraints, and aspects of the intended use and operating environment; (2) model performance, model complexity and design, and algorithm choice; (3) achievement of required performance at the levels of a trained model during model development, a trained model after model development is complete, and a trained model that is transformed into an executable equivalent; (4) model implementation aspects necessary for transforming a trained model into the executable equivalent; (5) integration of the executable trained model into the containing MLC, and eventually the larger system; and, (6) lastly, the verification and validation (V&V) of each of the above. Such V&V lifecycle artifacts themselves include: aspects of coverage, e.g., of various levels of requirements by the input space of the model and the data; traceability (where applicable); application of formal methods for property specification, analysis, and checking. Examples of evidence generation methods and tools further ground the discussion on what constitutes evidence, and the contribution to assurance during certification. The identified assurance considerations and supporting evidence is not a comprehensive set. Additionally, neither what should be considered as sufficient evidence relative to the assigned criticality of an MLC, nor how criticality ought to be determined and adjusted, have been considered in this report. However, suggestions are made for potential activities of the ML lifecycle that are aimed at providing confidence that an MLC can be relied upon when integrated into its containing (aircraft) system. Those activities are proposed as candidate elements of a certification process for MLCs. The main purpose of this report to inform regulatory guidance and consensus standards that may be used to meet the safety intent of the applicable regulations.

Aviation safety↗

Software Certification - Coding, Code, and Coders

We describe a certification approach for software development that has been adopted at our organization. JPL develops robotic spacecraft for the exploration of the solar system. The flight software that controls these spacecraft is considered to be mission critical. We argue that the goal of a software certification process cannot be the development of "perfect" software, i.e., software that can be formally proven to be correct under all imaginable and unimaginable circumstances. More realistically, the goal is to guarantee a software development process that is conducted by knowledgeable engineers, who follow generally accepted procedures to control known risks, while meeting agreed upon standards of workmanship. We target three specific issues that must be addressed in such a certification procedure: the coding process, the code that is developed, and the skills of the coders. The coding process is driven by standards (e.g., a coding standard) and tools. The code is mechanically checked against the standard with the help of state-of-the-art static source code analyzers. The coders, finally, are certified in on-site training courses that include formal exams.

training↗

A Battery Certification Testbed for Small Satellite Missions

A battery pack consisting of standard cylindrical 18650 lithium-ion cells has been chosen for small satellite missions based on previous flight heritage and compliance with NASA battery safety requirements. However, for batteries that transit through the International Space Station (ISS), additional certification tests are required for individual cells as well as the battery packs. In this manuscript, we discuss the development of generalized testbeds for testing and certifying different types of batteries critical to small satellite missions. Test procedures developed and executed for this certification effort include: a detailed physical inspection before and after experiments; electrical cycling characterization at the cell and pack levels; battery-pack overcharge, over-discharge, external short testing; battery-pack vacuum leak and vibration testing. The overall goals of these certification procedures are to conform to requirements set forth by the agency and identify unique safety hazards. The testbeds, procedures, and experimental results are discussed for batteries chosen for small satellite missions to be launched from the ISS.

Certification↗

A Guide for Aircraft Certification by Analysis

Analysis-based means of compliance for airplane and engine certification, commonly known as "Certification by Analysis" (CbA), provides a strong motivation for the development and maturation of current and future flight and engine modeling technology. The many benefits of CbA include streamlined product certification testing programs at lower cost while maintaining equivalent levels of safety. Flight and engine testing represent a substantial cost to airplane and engine development programs. This report provides a far-reaching vision for CbA and presents a research roadmap for computational technology development to enable CbA.

certification by analysis↗

Apollo experience report: Certification test program

A review of the Apollo spacecraft certification (qualification) test program is presented. The approach to devising the spectrum of dynamic and climatic environments, the formulation of test durations, and the relative significance of the formal certification test program compared with development testing and acceptance testing are reviewed. Management controls for the formulation of test requirements, test techniques, data review, and acceptance of test results are considered. Significant experience gained from the Apollo spacecraft certification test program which may be applicable to future manned spacecraft is presented.

Levine, J. H.↗

Certification aspects of airplanes which may operate with significant natural laminar flow

Recent research by NASA indicates that extensive natural laminar flow (NLF) is attainable on modern high performance airplanes currently under development. Modern airframe construction methods and materials, such as milled aluminum skins, bonded aluminum skins, and composite materials, offer the potential for production of aerodynamic surfaces having waviness and roughness below the values which are critical for boundary layer transition. Areas of concern with the certification aspects of Natural Laminar Flow (NLF) are identified to stimulate thought and discussion of the possible problems. During its development, consideration has been given to the recent research information available on several small business and experimental airplanes and the certification and operating rules for general aviation airplanes. The certification considerations discussed are generally applicable to both large and small airplanes. However, from the information available at this time, researchers expect more extensive NLF on small airplanes because of their lower operating Reynolds numbers and cleaner leading edges (due to lack of leading-edge high lift devices). Further, the use of composite materials for aerodynamic surfaces, which will permit incorporation of NLF technology, is currently beginning to appear in small airplanes.

Gabriel, Edward A.↗

GCS plan for software aspects of certification

As part of the Guidance and Control Software (GCS) research project being sponsored by NASA to evaluate the failure processes of software, standard industry software development procedures are being employed. To ensure that these procedures are authentic, the guidelines outlined in the Radio Technical Commission for Aeronautics (RTCA/DO-178A document entitled, software considerations in airborne systems and equipment certification, were adopted. A major aspect of these guidelines is proper documentation. As such, this report, the plan for software aspects of certification, was produced in accordance with DO-178A. An overview is given of the GCS research project, including the goals of the project, project organization, and project schedules. It also specifies the plans for all aspects of the project which relate to the certification of the GCS implementations developed under a NASA contract. These plans include decisions made regarding the software specification, accuracy requirements, configuration management, implementation development and verification, and the development of the GCS simulator.

Shagnea, Anita M.↗

PVDaCS - A prototype knowledge-based expert system for certification of spacecraft data

On-line data management techniques to certify spacecraft information are mandated by increasing telemetry rates. Knowledge-based expert systems offer the ability to certify data electronically without the need for time-consuming human interaction. Issues of automatic certification are explored by designing a knowledge-based expert system to certify data from a scientific instrument, the Orbiter Ultraviolet Spectrometer, on an operating NASA planetary spacecraft, Pioneer Venus. The resulting rule-based system, called PVDaCS (Pioneer Venus Data Certification System), is a functional prototype demonstrating the concepts of a larger system design. A key element of the system design is the representation of an expert's knowledge through the usage of well ordered sequences. PVDaCS produces a certification value derived from expert knowledge and an analysis of the instrument's operation. Results of system performance are presented.

Wharton, Cathleen↗