Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Development assurance”

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 883 records · Page 49

Evaluation of the Self-Nulling Rotating Eddy Current Probe System

In order to detect multi-site fatigue cracks located under flush-head rivets, automated eddy current equipment is required. To assure a reliable system, the eddy current probe must be centered easily over the installed rivets. To meet these requirements, the NDE Group at NASA LaRC developed the Self-Nulling Rotating Eddy Current Probe System (SNRECPS) which will be referred to as RPS in this document. The system was evaluated at the FAA, NDI Validation Center, in Albuquerque, New Mexico. The system was capable of detecting a 0.032 inch long crack with a 90/95% PoD. Further evaluations were conducted at Boeing in Long Beach, California. These evaluations included fatigue cracks and notches in a range from 0.025 to 0.100 inch long under flush-head aluminum rivets, and titanium or steel flush-head fasteners. The results of these tests are reported herein. Subsequently, the system was loaned to the USAF Structures Laboratory for the purpose of detecting and measuring short cracks under flush-head rivets in a variety of fatigue test specimens. The inspection task was to detect and plot crack growth from numbered fasteners in lettered rows. In January, 1998, the system was taken to Northwest Airlines Maintenance Base, in Atlanta, to inspect a DC-9, for multi-site cracks in three circumferential splices. The aircraft had 83,000 cycles. The inspection was conducted at 30 kHz from longeron 5 left to longeron 5 right. The system was calibrated using a 0,030 EDM first layer notch. The instrument gain was set to 19 mV from the notch. The reject level was set at 10 mV and the unflawed fasteners yielded a signal amplitude of 2 to 3 mV. Only one fastener location, out of about 2,500 tested, yielded a signal of 58 mV. The rivet was removed and visually evaluated. It appeared to be a slight gouge in the counter-sink zone. No fatigue cracks were detected. The same fastener locations were also inspected using the Boeing MAUS system at 60 kHz. No cracks were detected. Thus far, the rotating probe eddy current system has been found to be very user friendly and capable of detecting first layer cracks on the order of 0.030 inch long or longer.

Hagemaier, Don↗

Magnetized Target Fusion Driven by Plasma Liners

Magnetized target fusion (MTF) attempts to combine the favorable attributes of magnetic confinement fusion (MCF) for energy confinement with the attributes of inertial confinement fusion (ICF) for efficient compression heating and wall-free containment of the fusing plasma. It uses a material liner to compress and contain a magnetized plasma. For practical applications, standoff drivers to deliver the imploding momentum flux to the target plasma remotely are required. Spherically converging plasma jets have been proposed as standoff drivers for this purpose. The concept involves the dynamic formation of a spherical plasma liner by the merging of plasma jets, and the use of the liner so formed to compress a spheromak or a field reversed configuration (FRC). For the successful implementation of the scheme, plasma jets of the requisite momentum flux density need to be produced. Their transport over sufficiently large distances (a few meters) needs to be assured. When they collide and merge into a liner, relative differences in velocity, density and temperature of the jets could give rise to instabilities in the development of the liner. Variation in the jet properties must be controlled to ensure that the growth rate of the instabilities are not significant over the time scale of the liner formation before engaging with the target plasma. On impact with the target plasma, some plasma interpenetration might occur between the liner and the target. The operating parameter space needs to be identified to ensure that a reasonably robust and conducting contact surface is formed between the liner and the target. A mismatch in the "impedance" between the liner and the target plasma could give rise to undesirable shock heating of the liner leading to increased entropy (thermal losses) in the liner. Any irregularities in the liner will accentuate the Rayleigh-Taylor instabilities during the compression of the target plasma by the liner.

Thio, Y. C. Francis↗

Human Factors Engineering as a System in the Vision for Exploration

In order to accomplish NASA's Vision for Exploration, while assuring crew safety and productivity, human performance issues must be well integrated into system design from mission conception. To that end, a two-year Technology Development Project (TDP) was funded by NASA Headquarters to develop a systematic method for including the human as a system in NASA's Vision for Exploration. The specific goals of this project are to review current Human Systems Integration (HSI) standards (i.e., industry, military, NASA) and tailor them to selected NASA Exploration activities. Once the methods are proven in the selected domains, a plan will be developed to expand the effort to a wider scope of Exploration activities. The methods will be documented for inclusion in NASA-specific documents (such as the Human Systems Integration Standards, NASA-STD-3000) to be used in future space systems. The current project builds on a previous TDP dealing with Human Factors Engineering processes. That project identified the key phases of the current NASA design lifecycle, and outlined the recommended HFE activities that should be incorporated at each phase. The project also resulted in a prototype of a webbased HFE process tool that could be used to support an ideal HFE development process at NASA. This will help to augment the limited human factors resources available by providing a web-based tool that explains the importance of human factors, teaches a recommended process, and then provides the instructions, templates and examples to carry out the process steps. The HFE activities identified by the previous TDP are being tested in situ for the current effort through support to a specific NASA Exploration activity. Currently, HFE personnel are working with systems engineering personnel to identify HSI impacts for lunar exploration by facilitating the generation of system-level Concepts of Operations (ConOps). For example, medical operations scenarios have been generated for lunar habitation in order to identify HSI requirements for the lunar communications architecture. Throughout these ConOps exercises, HFE personnel are testing various tools and methodologies that have been identified in the literature. A key part of the effort is the identification of optimal processes, methods, and tools for these early development phase activities, such as ConOps, requirements development, and early conceptual design. An overview of the activities completed thus far, as well as the tools and methods investigated will be presented.

Mihriban Whitmore↗

Evaluation of the Trade Space Between UAS Maneuver Performance and SAA System Performance Requirements

A need exists to safely integrate Unmanned Aircraft Systems (UAS) into the National Airspace System. Replacing manned aircraft's see-and-avoid capability in the absence of an onboard pilot is one of the key challenges associated with safe integration. Sense-and-avoid (SAA) systems will have to achieve yet-to-be-determined required separation distances for a wide range of encounters. They will also need to account for the maneuver performance of the UAS they are paired with. The work described in this paper is aimed at developing an understanding of the trade space between UAS maneuver performance and SAA system performance requirements. An assessment of current manned and unmanned aircraft performance was used to establish potential UAS performance test matrix bounds. Then, nearterm UAS integration work was used to narrow down the scope. A simulator was developed with sufficient fidelity to assess SAA system performance requirements for a wide range of encounters. The simulator generates closest-point-of-approach (CPA) data from the wide range of UAS performance models maneuvering against a single intruder with various encounter geometries. The simulator is described herein and has both a graphical user interface and batch interface to support detailed analysis of individual UAS encounters and macro analysis of a very large set of UAS and encounter models, respectively. Results from the simulator using approximate performance data from a well-known manned aircraft is presented to provide insight into the problem and as verification and validation of the simulator. Analysis of climb, descent, and level turn maneuvers to avoid a collision is presented. Noting the diversity of backgrounds in the UAS community, a description of the UAS aerodynamic and propulsive design and performance parameters is included. Initial attempts to model the results made it clear that developing maneuver performance groups is required. Discussion of the performance groups developed and how to know in which group an aircraft belongs for a given flight condition and encounter is included. The groups are specific to airplane, flight condition, and encounter, rather than airplane-only specific. Results and methodology for developing UAS maneuver performance requirements are presented for each maneuver as well. Results for the vertical maneuver indicate that a minimum specific excess power value can assure a minimum CPA for a given time-to-go prediction. However, smaller values of specific excess power may achieve or exceed the same CPA if the UAS has sufficient speed to trade for altitude. Level turn results are less impacted by specific excess power and are presented as a function of turn rate. The effect of altitude is also discussed for the turns. Next steps and future work are discussed. Future studies will lead to better quantification of the preliminary results and cover the remainder of the proposed test matrix. It is anticipated that this will be done in conjunction with RTCA SC-228 over the next few months.

Jack, Devin P.↗

AE (Acoustic Emission) for Flip-Chip CGA/FCBGA Defect Detection

C-mode scanning acoustic microscopy (C-SAM) is a nondestructive inspection technique that uses ultrasound to show the internal feature of a specimen. A very high or ultra-high-frequency ultrasound passes through a specimen to produce a visible acoustic microimage (AMI) of its inner features. As ultrasound travels into a specimen, the wave is absorbed, scattered or reflected. The response is highly sensitive to the elastic properties of the materials and is especially sensitive to air gaps. This specific characteristic makes AMI the preferred method for finding "air gaps" such as delamination, cracks, voids, and porosity. C-SAM analysis, which is a type of AMI, was widely used in the past for evaluation of plastic microelectronic circuits, especially for detecting delamination of direct die bonding. With the introduction of the flip-chip die attachment in a package; its use has been expanded to nondestructive characterization of the flip-chip solder bumps and underfill. Figure 1.1 compares visual and C-SAM inspection approaches for defect detection, especially for solder joint interconnections and hidden defects. C-SAM is specifically useful for package features like internal cracks and delamination. C-SAM not only allows for the visualization of the interior features, it has the ability to produce images on layer-by-layer basis. Visual inspection; however, is only superior to C-SAM for the exposed features including solder dewetting, microcracks, and contamination. Ideally, a combination of various inspection techniques - visual, optical and SEM microscopy, C-SAM, and X-ray - need to be performed in order to assure quality at part, package, and system levels. This reports presents evaluations performed on various advanced packages/assemblies, especially the flip-chip die version of ball grid array/column grid array (BGA/CGA) using C-SAM equipment. Both external and internal equipment was used for evaluation. The outside facility provided images of the key features that could be detected using the most advanced C-SAM equipment with a skilled operator. Investigation continued using in-house equipment with its limitations. For comparison, representative X-rays of the assemblies were also gathered to show key defect detection features of these non-destructive techniques. Key images gathered and compared are: Compared the images of 2D X-ray and C-SAM for a plastic LGA assembly showing features that could be detected by either NDE technique. For this specific case, X-ray was a clear winner. Evaluated flip-chip CGA and FCBGA assemblies with and without heat sink by C-SAM. Only the FCCGA package that had no heat sink could be fully analyzed for underfill and bump quality. Cross-sectional microscopy did not revealed peripheral delamination features detected by C-SAM. Analyzed a number of fine pitch PBGA assemblies by C-SAM. Even though the internal features of the package assemblies could be detected, C-SAM was unable to detect solder joint failure at either the package or board level. Twenty times touch ups by solder iron with 700degF tip temperature, each with about 5 second duration, did not induce defects to be detected by C-SAM images. Other techniques need to be considered to induce known defects for characterization. Given NASA's emphasis on the use of microelectronic packages and assemblies and quality assurance on workmanship defect detection, understanding key features of various inspection systems that detect defects in the early stages of package and assembly is critical to developing approaches that will minimize future failures. Additional specific, tailored non-destructive inspection approaches could enable low-risk insertion of these advanced electronic packages having hidden and fine features.

Ghaffarian, Reza↗

Evaluation of Agency Non-Code Layered Pressure Vessels (LPVs)

In coordination with the Office of Safety and Mission Assurance and the respective Center Pressure System Managers (PSMs), the NASA Engineering and Safety Center (NESC) was requested to formulate a consensus draft proposal for the development of additional testing and analysis methods to establish the technical validity, and any limitation thereof, for the continued safe operation of facility non-code layered pressure vessels. The PSMs from each NASA Center were asked to participate as part of the assessment team by providing, collecting, and reviewing data regarding current operations of these vessels. This report contains the outcome of the assessment and the findings, observations, and NESC recommendations to the Agency and individual NASA Centers.

Prosser, William H.↗

Evaluation of Agency Non-Code Layered Pressure Vessels (LPVs) : Appendices - Volume 2

In coordination with the Office of Safety and Mission Assurance and the respective Center Pressure System Managers (PSMs), the NASA Engineering and Safety Center (NESC) was requested to formulate a consensus draft proposal for the development of additional testing and analysis methods to establish the technical validity, and any limitation thereof, for the continued safe operation of facility non-code layered pressure vessels. The PSMs from each NASA Center were asked to participate as part of the assessment team by providing, collecting, and reviewing data regarding current operations of these vessels. This document contains the appendices to the main report.

Prosser, William H.↗

Evaluation of Agency Non-Code Layered Pressure Vessels (LPVs)

In coordination with the Office of Safety and Mission Assurance and the respective Center Pressure System Managers (PSMs), the NASA Engineering and Safety Center (NESC) was requested to formulate a consensus draft proposal for the development of additional testing and analysis methods to establish the technical validity, and any limitation thereof, for the continued safe operation of facility non-code layered pressure vessels. The PSMs from each NASA Center were asked to participate as part of the assessment team by providing, collecting, and reviewing data regarding current operations of these vessels. This report contains the outcome of the assessment and the findings, observations, and NESC recommendations to the Agency and individual NASA Centers.

Prosser, William H.↗

A Study to Estimate the Effectiveness of Visual Testing Training for Aviation Maintenance Management

The Air Commerce Act of 1926 set the beginning for standards in aviation maintenance. Even after deregulation in the late l970s, maintenance standards and requirements still have not changed far from their initial criteria. After a potential candidate completes Federal Aviation Administration training prerequisites, they may test for their Airframe and Powerplant (A&P) certificate. Performing maintenance in the aviation industry for a minimum of three years, the technician may then test for their Inspection Authorization (IA). After receiving their Airframe and Powerplant certificate, a technician is said to have a license to perform. At no time within the three years to eligibility for Inspection Authorization are they required to attend higher-level inspection training. What a technician learns in the aviation maintenance industry is handed down from a seasoned technician to the new hire or is developed from lessons learned on the job. Only in Europe has the Joint Aviation Authorities (JAA) required higher-level training for their aviation maintenance technicians in order to control maintenance related accidents (Lu, 2005). Throughout the 1990s both the General Accounting Office (GAO) and the National Transportation Safety Board (NTSB) made public that the FAA is historically understaffed (GAO, 1996). In a safety recommendation the NTSB stated "The Safety Board continues to lack confidence in the FAA's commitment to provide effective quality assurance and safety oversight of the ATC system (NTSB, 1990)." The Federal Aviation Administration (FAA) has been known to be proactive in creating safer skies. With such reports you would suspect the FAA to also be proactive in developing more stringent inspection training for aviation maintenance technicians. The purpose of this study is to estimate the effectiveness of higher-level inspection training, such as Visual Testing (VT) for aviation maintenance technicians, to improve the safety of aircraft and to make recommendations to management with regard to the value of such training.

Law, Lewis Lyle↗

Design, Development, and Testing of a UAV Hardware-in-the-Loop Testbed for Aviation and Airspace Prognostics Research

The airspace is becoming more and more complicated, and will continue to do so in the future with the integration of Unmanned Aerial Vehicles (UAVs), autonomy, spacecraft, other forms of aviation technology into the airspace. The new technology and complexity increases the importance and difficulty of safety assurance. Additionally, testing new technologies on complex aviation systems & systems of systems can be very difficult, expensive, and sometimes unsafe in real life scenarios. Prognostic methodology provides an estimate of the health and risks of a component, vehicle, or airspace and knowledge of how that will change over time. That measure is especially useful in safety determination, mission planning, and maintenance scheduling. The developed testbed will be used to validate prediction algorithms for the real-time safety monitoring of the National Airspace System (NAS) and the prediction of unsafe events. The framework injects flight related anomalies related to ground systems, routing, airport congestion, etc. to test and verify algorithms for NAS safety. In our research work, we develop a live, distributed, hardware-in-the-loop testbed for aviation and airspace prognostics along with exploring further research possibilities to verify and validate future algorithms for NAS safety. The testbed integrates virtual aircraft using the X-Plane simulator and X-PlaneConnect toolbox, UAVs using onboard sensors and cellular communications, and hardware in the loop components. In addition, the testbed includes an additional research framework to support and simplify future research activities. It enables safe, accurate, and inexpensive experimentation and research into airspace and vehicle prognosis that would not have been possible otherwise. This paper describes the design, development, and testing of this system. Software reliability, safety and latency are some of the critical design considerations in development of the testbed. Integration of HITL elements in the development phases and veri cation/ validation are key elements to this report.

HITL↗

Independent Verification and Validation (IV and V) - Adding Mission Assurance to NASA Flight Software

The NASA Independent Verification and Validation (IV&V) Facility objective is to identify potential defects in flight software using independent analysis techniques. This paper describes the tailored IV&V techniques that have been developed in support of critical interactions on the Mars Science Laboratory (MSL) project, scheduled to launch in November, 2011. The IV&V techniques for interface analysis use independently developed sequence diagrams of critical scenarios. The results from these analyses have had a positive impact on the requirements flow down, consistency amongst MSL requirements and identification of missing requirements. The results of these analyses and the positive impact to the MSL project are provided.

performance evaluation↗

From BERTopic to SysML: Informing Model-Based Failure Analysis With Natural Language Processing for Complex Aerospace Systems

The development of emerging complex aerospace systems will require new approaches for capturing safety incident scenarios as early as possible in the design phase. However, for novel systems, relevant data available is limited. In this work, we propose a framework informing model-based mission assurance activities with historical incident reports, lessons learned, or other relevant engineering documents using natural language processing. In doing so, we investigate whether there is useful information in data sets that are relevant, if not identical, to the system under design and whether, through rigorous systems engineering practice, this information can be effectively leveraged through model-based failure analysis. In a worked case study, we apply state-of-the-art topic modeling techniques to two data sets, a mission relevant data set and a system relevant data set. The sets of topics are merged and interpreted to form a preliminary list of failure topics that can be used to inform the identification of off-nominal modes in the model-based failure modes and effects analysis development. Once data from the system in operation is available, it can be used to update the topics identified. By extracting information about likely failures from relevant historical data sets and utilizing model-based mission assurance to ensure relevance and rigor, unanticipated failures can be reduced, and projects can more effectively learn from past missions.

Failure Analysis↗

From BERTopic to SysML: Informing Model-Based Failure Analysis With Natural Language Processing for Complex Aerospace Systems

The development of emerging complex aerospace systems will require new approaches for capturing safety incident scenarios as early as possible in the design phase. However, for novel systems, relevant data available is limited. In this work, we propose a framework informing model-based mission assurance activities with historical incident reports, lessons learned, or other relevant engineering documents using natural language processing. In doing so, we investigate whether there is useful information in data sets that are relevant, if not identical, to the system under design and whether, through rigorous systems engineering practice, this information can be effectively leveraged through model-based failure analysis. In a worked case study, we apply state-of-the-art topic modeling techniques to two data sets, a mission relevant data set and a system relevant data set. The sets of topics are merged and interpreted to form a preliminary list of failure topics that can be used to inform the identification of off-nominal modes in the model-based failure modes and effects analysis development. Once data from the system in operation is available, it can be used to update the topics identified. By extracting information about likely failures from relevant historical data sets and utilizing model-based mission assurance to ensure relevance and rigor, unanticipated failures can be reduced, and projects can more effectively learn from past missions.

Failure Analysis↗

The Role of Independent V&V in Upstream Software Development Processes

This paper describes the role of Verification and Validation (V&V) during the requirements and high level design processes, and in particular the role of Independent V&V (IV&V). The job of IV&V during these phases is to ensure that the requirements are complete, consistent and valid, and to ensure that the high level design meets the requirements. This contrasts with the role of Quality Assurance (QA), which ensures that appropriate standards and process models are defined and applied. This paper describes the current state of practice for IV&V, concentrating on the process model used in NASA projects. We describe a case study, showing the processes by which problem reporting and tracking takes place, and how IV&V feeds into decision making by the development team. We then describe the problems faced in implementing IV&V. We conclude that despite a well defined process model, and tools to support it, IV&V is still beset by communication and coordination problems.

Easterbrook, Steve↗

A Discussion of the Software Quality Assurance Role

The basic idea underlying this paper is that the conventional understanding of the role of a Software Quality Assurance (SQA) engineer is unduly limited. This is because few have asked who the customers of a SQA engineer are. Once you do this, you can better define what tasks a SQA engineer should perform, as well as identify the knowledge and skills that such a person should have. The consequence of doing this is that a SQA engineer can provide greater value to his or her customers. It is the position of this paper that a SQA engineer providing significant value to his or her customers must not only assume the role of an auditor, but also that of a software and systems engineer. This is because software engineers and their managers particularly value contributions that directly impact products and their development. These ideas are summarized as lessons learned, based on my experience at Jet Propulsion Laboratory (JPL).

experience↗

MODIS Land Data Products: Generation, Quality Assurance and Validation

The Moderate Resolution Imaging Spectrometer (MODIS) on-board NASA's Earth Observing System (EOS) Terra and Aqua Satellites are key instruments for providing data on global land, atmosphere, and ocean dynamics. Derived MODIS land, atmosphere and ocean products are central to NASA's mission to monitor and understand the Earth system. NASA has developed and generated on a systematic basis a suite of MODIS products starting with the first Terra MODIS data sensed February 22, 2000 and continuing with the first MODIS-Aqua data sensed July 2, 2002. The MODIS Land products are divided into three product suites: radiation budget products, ecosystem products, and land cover characterization products. The production and distribution of the MODIS Land products are described, from initial software delivery by the MODIS Land Science Team, to operational product generation and quality assurance, delivery to EOS archival and distribution centers, and product accuracy assessment and validation. Progress and lessons learned since the first MODIS data were in early 2000 are described.

Masuoka, Edward↗

Earth Observatory Satellite system definition study. Report no. 4: Management approach recommendations

A management approach for the Earth Observatory Satellite (EOS) which will meet the challenge of a constrained cost environment is presented. Areas of consideration are contracting techniques, test philosophy, reliability and quality assurance requirements, commonality options, and documentation and control requirements. The various functional areas which were examined for cost reduction possibilities are identified. The recommended management approach is developed to show the primary and alternative methods.

Source record↗

Standardized multiple output power supply

A comprehensive program to develop a prototype model of a standardized multiple output power supply for use in space flight applications is described. The prototype unit was tested and evaluated to assure that the design would provide near optimum performance for the planned application. The prototype design used a dc-to-dc converter incorporating reqenerative current feedback with a time-ratio controlled duty cycle to achieve high efficiency over a wide variation of input voltage and output loads. The packaging concept uses a mainframe capable of accommodating up to four inverter/regulator modules with one common input filter and housekeeping module. Each inverter/regulator module provides a maximum of 100 watts or 10 amperes. Each module is adaptable to operate at any voltage between 4.0 volts and 108 volts. The prototype unit contains +5, + or - 15 and +28 volt modules.

Ragusa, E. V.↗