Search NASA⌕ Search

SEARCH · Search NASA

Results for “certification by analysis”

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 181 records · Page 10

Demonstration of rapid and sensitive module leak certification for Space Station Freedom

A leak detection and quantification demonstration using perflurocarbon tracer (PFT) technology was successfully performed at the NASA Marshall Space Flight Center on January 25, 1991. The real-time Dual Trap Analyzer (DTA) at one-half hour after the start of the first run gave an estimated leak rate of 0.7 mL/min. This has since been refined to be 1.15 (+ or -) 0.09 mL/min. The leak rates in the next three runs were determined to be 9.8 (+ or -) 0.7, -0.4 (+ or -) 0.3, and 76 (+ or -) 6 mL/min, respectively. The theory on leak quantification in the steady-state and time-dependent modes for a single zone test facility was developed and applied to the above determinations. The laboratory PFT analysis system gave a limit-of-detection (LOD) of 0.05 fL for ocPDCH. This is the tracer of choice and is about 100-fold better than that for the DTA. Applied to leak certification, the LOD is about 0.00002 mL/s (0.000075 L/h), a 5 order-of-magnitude improvement over the original leak certification specification. Furthermore, this limit can be attained in a measurement period of 3 to 4 hours instead of days, weeks, or months. A new Leak Certification Facility is also proposed to provide for zonal (three zones) determination of leak rates. The appropriate multizone equations, their solutions, and error analysis have already been derived. A new concept of seal-integrity certification has been demonstrated for a variety of controlled leaks in the range of module leak testing. High structural integrity leaks were shown to have a linear dependence of flow on (Delta)p. The rapid determination of leak rates at different pressures is proposed and is to be determined while subjecting the module to other external force-generating parameters such as vibration, torque, solar intensity, etc.

Dietz, R. N.↗

Demonstration of Probabilistic Sensitivity Analyses Tools on the Structural Response of a Representative Inflatable Space Structure

This work provides an initial step toward demonstrating a probabilistic numerical simulation capability to support trade studies and the development of a certification plan for inflatable space habitats. This study concentrates on interpreting the results from probabilistic analysis and numerical simulation tools to identify parameter sensitivities for a novel inflatable airlock concept, specifically the Non‐Axisymmetric Inflatable Pressure Structure (NAIPS) that was designed and tested under NASA's Minimalistic Advanced Softgoods Hatch (MASH) Program. A brief overview of the finite element model is provided along with the probabilistic sensitivity analysis approach. The sensitivity studies required a model that was numerically stable and efficient enough that hundreds of simulations could be completed in the allotted time. Therefore, the existing full model was simplified by: extracting a quarter symmetry section of the dome; focusing on a single inflation pressure; and replacing the non‐linear material stress‐strain curves with linear, isotropic materials defined by elastic moduli. Responses of interest include the sensitivity of various structural component loads to material properties, cord lengths, inflation pressure and friction. Multiple sensitivity studies were completed and three are reported here. The first study focused on utilizing wide input parameter ranges to provide an opportunity to assess numerical robustness. The next two studies narrowed the parameter ranges to enable focus on understanding uncertainty at a fixed operating condition. The completion of the sensitivity studies improved understanding of the interdependence of multiple inputs on the responses. In addition, numerical stability of the simulations over wide parameter ranges, shows the feasibility of incorporating uncertainty‐based methods in the design and certification of inflatable space habitats. With the experience and trust gained, it is anticipated that these same methods will be applied to nonlinear, orthotropic models in the future.

Lyle, Karen H.↗

Flat-plate solar collector - installation package

Package includes installation, operation and maintenance manual for collector, analysis of safety hazards, special handling instructions, materials list, installation drawings, and warranty and certification statement. Manual includes instructions for roof preparation and for preparing collector for installation. Several pages are devoted to major and minor repairs.

Source record↗

Flight Dynamics Analysis Branch End of Fiscal Year 1999 Report

This document summarizes the major activities and accomplishments carried out by the Goddard Space Flight Center (GSFC)'s Flight Dynamics Analysis Branch (FDAB), Code 572, in support of flight projects and technology development initiatives in Fiscal Year (FY) 1999. The document is intended to serve as both an introduction to the type of support carried out by the FDAB (Flight Dynamics Analysis Branch), as well as a concise reference summarizing key analysis results and mission experience derived from the various mission support roles assumed over the past year. The major accomplishments in the FDAB in FY99 were: 1) Provided flight dynamics support to the Lunar Prospector and TRIANA missions among a variety of spacecraft missions; 2) Sponsored the Flight Mechanics Symposium; 3) Supported the Consultative Committee for Space Data Systems (CCSDS) workshops; 4) Performed numerous analyses and studies for future missions; 5) Started the Flight Dynamics Analysis Branch Lab for in-house mission analysis and support; and 6) Complied with all requirements in support of GSFC IS09000 certification.

Stengle, Thomas↗

Development of Advanced Verification and Validation Procedures and Tools for the Certification of Learning Systems in Aerospace Applications

Adaptive control technologies that incorporate learning algorithms have been proposed to enable automatic flight control and vehicle recovery, autonomous flight, and to maintain vehicle performance in the face of unknown, changing, or poorly defined operating environments. In order for adaptive control systems to be used in safety-critical aerospace applications, they must be proven to be highly safe and reliable. Rigorous methods for adaptive software verification and validation must be developed to ensure that control system software failures will not occur. Of central importance in this regard is the need to establish reliable methods that guarantee convergent learning, rapid convergence (learning) rate, and algorithm stability. This paper presents the major problems of adaptive control systems that use learning to improve performance. The paper then presents the major procedures and tools presently developed or currently being developed to enable the verification, validation, and ultimate certification of these adaptive control systems. These technologies include the application of automated program analysis methods, techniques to improve the learning process, analytical methods to verify stability, methods to automatically synthesize code, simulation and test methods, and tools to provide on-line software assurance.

Jacklin, Stephen↗

Proceedings of the Third International Workshop on Proof-Carrying Code and Software Certification

This NASA conference publication contains the proceedings of the Third International Workshop on Proof-Carrying Code and Software Certification, held as part of LICS in Los Angeles, CA, USA, on August 15, 2009. Software certification demonstrates the reliability, safety, or security of software systems in such a way that it can be checked by an independent authority with minimal trust in the techniques and tools used in the certification process itself. It can build on existing validation and verification (V&V) techniques but introduces the notion of explicit software certificates, Vvilich contain all the information necessary for an independent assessment of the demonstrated properties. One such example is proof-carrying code (PCC) which is an important and distinctive approach to enhancing trust in programs. It provides a practical framework for independent assurance of program behavior; especially where source code is not available, or the code author and user are unknown to each other. The workshop wiII address theoretical foundations of logic-based software certification as well as practical examples and work on alternative application domains. Here "certificate" is construed broadly, to include not just mathematical derivations and proofs but also safety and assurance cases, or any fonnal evidence that supports the semantic analysis of programs: that is, evidence about an intrinsic property of code and its behaviour that can be independently checked by any user, intermediary, or third party. These guarantees mean that software certificates raise trust in the code itself, distinct from and complementary to any existing trust in the creator of the code, the process used to produce it, or its distributor. In addition to the contributed talks, the workshop featured two invited talks, by Kelly Hayhurst and Andrew Appel. The PCC 2009 website can be found at http://ti.arc.nasa.gov /event/pcc 091.

Ewen, Denney, W.↗

Tethered Space Satellite-1 (TSS-1): Technical Roundabouts

In the early 1990's US and Italian scientists collaborated to study the electrodynamics of dragging a satellite on a tether through the electrically charged portion of Earth's atmosphere called the ionosphere. An electrical current induced in the long wire could be used for power and thrust generation for a satellite. Other tether uses include momentum exchange, artificial gravity, deployment of sensors or antennas, and gravity-gradient stabilization for satellites. Before the Tethered Space Satellite (TSS-1), no long tether had ever been flown, so many questions existed on how it would actually behave. The TSS consisted of a satellite with science experiments attached to a 12.5 mile long, very thin (0.10 inch diameter) copper wire assembly wound around a spool in the deployer reel mechanism. With the Space Shuttle at an altitude of 160 nautical miles above earth, the satellite was to be deployed by raising it from the Shuttle bay on a boom facing away from Earth. Once cleared of the bay, the deployer mechanism was to slowly feed out the 12-plus miles of tether. Scientific data would be collected throughout the operation, after which the satellite would be reeled back in. Pre-flight testing system level tests involved setting up a tether receiver to catch the 12.5 mile tether onto another reel as it was being unwound by the deployer reel mechanism. Testing only the reel mechanism is straightforward. This test becomes more complicated when the TSS is mounted on the flight pallet at Kennedy Space Center (KSC). The system level tests must be passed before the pallet can be installed into the Space Shuttle cargo bay. A few months before flight, the TSS payload had been integrated onto the Spacelab pallet and system level tests, including unreeling and reeling the tether, had been successfully completed. Some of this testing equipment was then shipped back to the contractor Martin Marietta. Systems-level load analyses, which cannot be run until all information about each payload is finalized, was run in parallel with the physical integration of the hardware into the Shuttle payload bay. The coupled loads analysis, as it is called, incorporates any updates to the model due to system level tests, and any changes that were found during integration. The coupled loads analysis revealed that a single bolt attaching the deployer reel mechanism to the support structure had a "negative margin" - which is an indication that it might fail during operation. Hardware certification rules do not allow for hardware to fly with negative margins, so this issue had to be resolved before the flight. Since there is conservatism in engineering analysis, there is an option to "waive" the margin requirement, and fly the experiment as is. On the other hand, a structural failure of one payload could have serious or catastrophic consequences to other payloads and possibly the mission. Minor design changes or fixes might be feasible within the payload bay prior to launch. Any major design changes that required the spooling test to validate the hardware, or for the pallet to be removed, would cause TSS not to be ready for the Shuttle launch.

O'Connor, Brian↗

Flight Testing and Real-Time System Identification Analysis of a UH-60A Black Hawk Helicopter with an Instrumented External Sling Load

Helicopter external air transportation plays an important role in today's world. For both military and civilian helicopters, external sling load operations offer an efficient and expedient method of handling heavy, oversized cargo. With the ability to reach areas otherwise inaccessible by ground transportation, helicopter external load operations are conducted in industries such as logging, construction, and fire fighting, as well as in support of military tactical transport missions. Historically, helicopter and load combinations have been qualified through flight testing, requiring considerable time and cost. With advancements in simulation and flight test techniques there is potential to substantially reduce costs and increase the safety of helicopter sling load certification. Validated simulation tools make possible accurate prediction of operational flight characteristics before initial flight tests. Real time analysis of test data improves the safety and efficiency of the testing programs. To advance these concepts, the U.S. Army and NASA, in cooperation with the Israeli Air Force and Technion, under a Memorandum of Agreement, seek to develop and validate a numerical model of the UH-60 with sling load and demonstrate a method of near real time flight test analysis. This thesis presents results from flight tests of a U.S. Army Black Hawk helicopter with various external loads. Tests were conducted as the U.S. first phase of this MOA task. The primary load was a container express box (CONEX) which contained a compact instrumentation package. The flights covered the airspeed range from hover to 70 knots. Primary maneuvers were pitch and roll frequency sweeps, steps, and doublets. Results of the test determined the effect of the suspended load on both the aircraft's handling qualities and its control system's stability margins. Included were calculations of the stability characteristics of the load's pendular motion. Utilizing CIFER(R) software, a method for near-real time system identification was also demonstrated during the flight test program.

McCoy, Allen H.↗

Aerodynamic comparisons of STS-1 Space Shuttle entry vehicle

A conventional flight-test program, which slowly and cautiously approaches more severe flight conditions, was not possible with the Orbiter. On the first flight, the Orbiter entered the atmosphere at Mach 28 and decelerated through the Mach range. (The subsonic portion of flight was also flown by another orbiter vehicle during the Approach and Landing Test Program.) Certification for the first flight was achieved by an extensive wind-tunnel test and analysis program and by restricting the flight maneuvers severely. The initial flights of the orbiter were heavily instrumented for the purpose of obtaining accurate aerodynamic data. Even without maneuvers to excite the system, the first flight provided comparisons between flight and wind-tunnel-derived predicted data in the areas of aerodynamic performance, longitudinal trim, and reaction-control jet interaction. The aerodynamic performance comparisons are presented.

Young, J. C.↗

Progress through precedent: Going where no helicopter simulator has gone before

Helicopter simulators have been approved by means of special exemption; there are no FAA standards for simulators used in training or airmen Certification checking. The fixed-wing industry provides a precedent which can be used for expediting implementation of helicopter simulators. The analysis in this paper is founded on the experience with that precedent and is driven by a clear definition of helicopter user needs for (1) improved training at lower cost, (2) more comprehensive emergency training at lower risk, (3) increased fidelity of transition and instrument training compared with low-cost aircraft alternatives, and (4) certification credit for improved simulator training.

Adams, Richard J.↗

Compliance with High-Intensity Radiated Fields Regulations - Emitter's Perspective

NASA's Deep Space Network (DSN) uses high-power transmitters on its large antennas to communicate with spacecraft of NASA and its partner agencies. The prime reflectors of the DSN antennas are parabolic, at 34m and 70m in diameter. The DSN transmitters radiate Continuous Wave (CW) signals at 20 kW - 500 kW at X-band and S-band frequencies. The combination of antenna reflector size and high frequency results in a very narrow beam with extensive oscillating near-field pattern. Another unique feature of the DSN antennas is that they (and the radiated beam) move mostly at very slow sidereal rate, essentially identical in magnitude and at the opposite direction of Earth rotation.The DSN is in the process of revamping its documentation to provide analysis of the High Intensity Radiation Fields (HIRF) environment resulting from radio frequency radiation from DSN antennas for comparison to FAA regulations regarding certification of HIRF protection as outlined in the FAA regulations on HIRF protection for aircraft electrical and electronic systems (Title 14, Code of Federal Regulations (14 CFR) [section sign][section sign] 23.1308, 25.1317, 27.1317, and 29.1317).This paper presents work done at JPL, in consultation with the FAA. The work includes analysis of the radiated field structure created by the unique DSN emitters (combination of transmitters and antennas) and comparing it to the fields defined in the environments in the FAA regulations. The paper identifies areas that required special attention, including the implications of the very narrow beam of the DSN emitters and the sidereal rate motion. The paper derives the maximum emitter power allowed without mitigation and the mitigation zones, where required.Finally, the paper presents summary of the results of the analyses of the DSN emitters and the resulting DSN process documentation.

DSN emitters↗

An Assessment of Civil Tiltrotor Concept of Operations in the Next Generation Air Transportation System

Based on a previous Civil Tiltrotor (CTR) National Airspace System (NAS) performance analysis study, CTR operations were evaluated over selected routes and terminal airspace configurations assuming noninterference operations (NIO) and runway-independent operations (RIO). This assessment aims to further identify issues associated with these concepts of operations (ConOps), and their dependency on the airspace configuration and interaction with conventional fixed-wing traffic. Safety analysis following a traditional Safety Management System (SMS) methodology was applied to CTR-unique departure and arrival failures in the selected airspace to identify any operational and certification issues. Additional CTR operational cases were then developed to get a broader understanding of issues and gaps that will need to be addressed in future CTR operational studies. Finally, needed enhancements to National Airspace System performance analysis tools were reviewed, and recommendations were made on improvements in these tools that are likely to be required to support future progress toward CTR fleet operations in the Next Generation Air Transportation System (NextGen).

Chung, William W.↗

The NASA Integrated Information Technology Architecture

This document defines an Information Technology Architecture for the National Aeronautics and Space Administration (NASA), where Information Technology (IT) refers to the hardware, software, standards, protocols and processes that enable the creation, manipulation, storage, organization and sharing of information. An architecture provides an itemization and definition of these IT structures, a view of the relationship of the structures to each other and, most importantly, an accessible view of the whole. It is a fundamental assumption of this document that a useful, interoperable and affordable IT environment is key to the execution of the core NASA scientific and project competencies and business practices. This Architecture represents the highest level system design and guideline for NASA IT related activities and has been created on the authority of the NASA Chief Information Officer (CIO) and will be maintained under the auspices of that office. It addresses all aspects of general purpose, research, administrative and scientific computing and networking throughout the NASA Agency and is applicable to all NASA administrative offices, projects, field centers and remote sites. Through the establishment of five Objectives and six Principles this Architecture provides a blueprint for all NASA IT service providers: civil service, contractor and outsourcer. The most significant of the Objectives and Principles are the commitment to customer-driven IT implementations and the commitment to a simpler, cost-efficient, standards-based, modular IT infrastructure. In order to ensure that the Architecture is presented and defined in the context of the mission, project and business goals of NASA, this Architecture consists of four layers in which each subsequent layer builds on the previous layer. They are: 1) the Business Architecture: the operational functions of the business, or Enterprise, 2) the Systems Architecture: the specific Enterprise activities within the context of IT systems, 3) the Technical Architecture: a common, vendor-independent framework for design, integration and implementation of IT systems and 4) the Product Architecture: vendor=specific IT solutions. The Systems Architecture is effectively a description of the end-user "requirements". Generalized end-user requirements are discussed and subsequently organized into specific mission and project functions. The Technical Architecture depicts the framework, and relationship, of the specific IT components that enable the end-user functionality as described in the Systems Architecture. The primary components as described in the Technical Architecture are: 1) Applications: Basic Client Component, Object Creation Applications, Collaborative Applications, Object Analysis Applications, 2) Services: Messaging, Information Broker, Collaboration, Distributed Processing, and 3) Infrastructure: Network, Security, Directory, Certificate Management, Enterprise Management and File System. This Architecture also provides specific Implementation Recommendations, the most significant of which is the recognition of IT as core to NASA activities and defines a plan, which is aligned with the NASA strategic planning processes, for keeping the Architecture alive and useful.

Baldridge, Tim↗

Fluids and Combustion Facility: Combustion Integrated Rack Modal Model Correlation

The Fluids and Combustion Facility (FCF) is a modular, multi-user, two-rack facility dedicated to combustion and fluids science in the US Laboratory Destiny on the International Space Station. FCF is a permanent facility that is capable of accommodating up to ten combustion and fluid science investigations per year. FCF research in combustion and fluid science supports NASA's Exploration of Space Initiative for on-orbit fire suppression, fire safety, and space system fluids management. The Combustion Integrated Rack (CIR) is one of two racks in the FCF. The CIR major structural elements include the International Standard Payload Rack (ISPR), Experiment Assembly (optics bench and combustion chamber), Air Thermal Control Unit (ATCU), Rack Door, and Lower Structure Assembly (Input/Output Processor and Electrical Power Control Unit). The load path through the rack structure is outlined. The CIR modal survey was conducted to validate the load path predicted by the CIR finite element model (FEM). The modal survey is done by experimentally measuring the CIR frequencies and mode shapes. The CIR model was test correlated by updating the model to represent the test mode shapes. The correlated CIR model delivery is required by NASA JSC at Launch-10.5 months. The test correlated CIR flight FEM is analytically integrated into the Shuttle for a coupled loads analysis of the launch configuration. The analysis frequency range of interest is 0-50 Hz. A coupled loads analysis is the analytical integration of the Shuttle with its cargo element, the Mini Payload Logistics Module (MPLM), in the Shuttle cargo bay. For each Shuttle launch configuration, a verification coupled loads analysis is performed to determine the loads in the cargo bay as part of the structural certification process.

McNelis, Mark E.↗

NASA's UAS [Unmanned Aircraft Systems] Related Activities

NASA continues to operate all sizes of UAS in all classes of airspace both domestically and internationally. Missions range from highly complex operations in coordination with piloted aircraft, ground, and space systems in support of science objectives to single aircraft operations in support of aeronautics research. One such example is a scaled commercial transport aircraft being used to study recovery techniques due to large upsets. NASA's efforts to support routine UAS operations continued on several fronts last year. At the national level in the United States (U.S.), NASA continued its support of the UAS Executive Committee (ExCom) comprised of the Federal Aviation Administration (FAA), Department of Defense (DoD), Department of Homeland Security (DHS), and NASA. The committee was formed in recognition of the need of UAS operated by these agencies to access to the National Airspace System (NAS) to support operational, training, development and research requirements. Recommendations were received on how to operate both manned and unmanned aircraft in class D airspace and plans are being developed to validate and implement those recommendations. In addition the UAS ExCom has begun developing recommendations for how to achieve routine operations in remote areas as well as for small UAS operations in class G airspace. As well as supporting the UAS ExCom, NASA is a participant in the recently formed Aviation Rule Making Committee for UAS. This committee, established by the FAA, is intended to propose regulatory guidance which would enable routine civil UAS operations. As that effort matures NASA stands ready to supply the necessary technical expertise to help that committee achieve its objectives. By supporting both the UAS ExCom and UAS ARC, NASA is positioned to provide its technical expertise across the full spectrum of UAS airspace access related topic areas. The UAS NAS Access Project got underway this past year under the leadership of NASA s Aeronautics Research Mission Directorate. This project is focused on advancing the state of the art and providing research and analysis results in the areas of Separation Assurance, Communications (non-governmental spectrum allocation for UAS), Certification, and Human System Integration (ground control station design/pilot interfaces). The project is working in close coordination with the FAA and industry standards organizations (e.g. RTCA SC 203). More details on this project are provided in a separate article in this year's yearbook

Bauer, Jeffrey↗

Improving Safety on the International Space Station: Transitioning to Electronic Emergency Procedure Books on the International Space Station

The National Aeronautics and Space Administration (NASA) originally designed the International Space Station (ISS) to operate until 2015, but have extended operations until at least 2020. As part of this very dynamic Program, there is an effort underway to simplify the certification of Commercial ]of ]the ]Shelf (COTS) hardware. This change in paradigm allows the ISS Program to take advantage of technologically savvy and commercially available hardware, such as the iPad. The iPad, a line of tablet computers designed and marketed by Apple Inc., was chosen to support this endeavor. The iPad is functional, portable, and could be easily accessed in an emergency situation. The iPad Electronic Flight Bag (EFB), currently approved for use in flight by the Federal Aviation Administration (FAA), is a fraction of the cost of a traditional Class 2 EFB. In addition, the iPad fs ability to use electronic aeronautical data in lieu of paper in route charts and approach plates can cut the annual cost of paper data in half for commercial airlines. ISS may be able to benefit from this type of trade since one of the most important factors considered is information management. Emergency procedures onboard the ISS are currently available to the crew in paper form. Updates to the emergency books can either be launched on an upcoming visiting vehicle such as a Russian Soyuz flight or printed using the onboard ISS printer. In both cases, it is costly to update hardcopy procedures. A new operations concept was proposed to allow for the use of a tablet system that would provide a flexible platform to support space station crew operations. The purpose of the system would be to provide the crew the ability to view and maintain operational data, such as emergency procedures while also allowing Mission Control Houston to update the procedures. The ISS Program is currently evaluating the safety risks associated with the use of iPads versus paper. Paper products can contribute to the flammability risk and require manual updates that take time away from research tasks. The ISS program has recently purchased three iPads for the astronauts and the certification has been approved. The crew is currently using the iPads onboard. The results of this analysis could be used to discern whether the iPad is a viable option for use in emergencies by assessing the risk posture through the development of a quantitative probabilistic risk assessment (PRA).

Carter-Journet, Katrina↗

Towards a Certified Lightweight Array Bound Checker for Java Bytecode

Dynamic array bound checks are crucial elements for the security of a Java Virtual Machines. These dynamic checks are however expensive and several static analysis techniques have been proposed to eliminate explicit bounds checks. Such analyses require advanced numerical and symbolic manipulations that 1) penalize bytecode loading or dynamic compilation, 2) complexify the trusted computing base. Following the Foundational Proof Carrying Code methodology, our goal is to provide a lightweight bytecode verifier for eliminating array bound checks that is both efficient and trustable. In this work, we define a generic relational program analysis for an imperative, stackoriented byte code language with procedures, arrays and global variables and instantiate it with a relational abstract domain as polyhedra. The analysis has automatic inference of loop invariants and method pre-/post-conditions, and efficient checking of analysis results by a simple checker. Invariants, which can be large, can be specialized for proving a safety policy using an automatic pruning technique which reduces their size. The result of the analysis can be checked efficiently by annotating the program with parts of the invariant together with certificates of polyhedral inclusions. The resulting checker is sufficiently simple to be entirely certified within the Coq proof assistant for a simple fragment of the Java bytecode language. During the talk, we will also report on our ongoing effort to scale this approach for the full sequential JVM.

Pichardie, David↗