Search NASA⌕ Search

SEARCH · Search NASA

Results for “Quality Engineering”

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 73 records · Page 4

NASA's Software Safety Standard

NASA relies more and more on software to control, monitor, and verify its safety critical systems, facilities and operations. Since the 1960's there has hardly been a spacecraft launched that does not have a computer on board that will provide command and control services. There have been recent incidents where software has played a role in high-profile mission failures and hazardous incidents. For example, the Mars Orbiter, Mars Polar Lander, the DART (Demonstration of Autonomous Rendezvous Technology), and MER (Mars Exploration Rover) Spirit anomalies were all caused or contributed to by software. The Mission Control Centers for the Shuttle, ISS, and unmanned programs are highly dependant on software for data displays, analysis, and mission planning. Despite this growing dependence on software control and monitoring, there has been little to no consistent application of software safety practices and methodology to NASA's projects with safety critical software. Meanwhile, academia and private industry have been stepping forward with procedures and standards for safety critical systems and software, for example Dr. Nancy Leveson's book Safeware: System Safety and Computers. The NASA Software Safety Standard, originally published in 1997, was widely ignored due to its complexity and poor organization. It also focused on concepts rather than definite procedural requirements organized around a software project lifecycle. Led by NASA Headquarters Office of Safety and Mission Assurance, the NASA Software Safety Standard has recently undergone a significant update. This new standard provides the procedures and guidelines for evaluating a project for safety criticality and then lays out the minimum project lifecycle requirements to assure the software is created, operated, and maintained in the safest possible manner. This update of the standard clearly delineates the minimum set of software safety requirements for a project without detailing the implementation for those requirements. This allows the projects leeway to meet these requirements in many forms that best suit a particular project's needs and safety risk. In other words, it tells the project what to do, not how to do it. This update also incorporated advances in the state of the practice of software safety from academia and private industry. It addresses some of the more common issues now facing software developers in the NASA environment such as the use of Commercial-Off-the-Shelf Software (COTS), Modified OTS (MOTS), Government OTS (GOTS), and reused software. A team from across NASA developed the update and it has had both NASA-wide internal reviews by software engineering, quality, safety, and project management. It has also had expert external review. This presentation and paper will discuss the new NASA Software Safety Standard, its organization, and key features. It will start with a brief discussion of some NASA mission failures and incidents that had software as one of their root causes. It will then give a brief overview of the NASA Software Safety Process. This will include an overview of the key personnel responsibilities and functions that must be performed for safety-critical software.

Ramsay, Christopher M.↗

The Mars Reconnaissance Orbiter Mission: From Launch to the Primary Science Orbit

The Mars Reconnaissance Orbiter (MRO) was launched from Cape Canaveral Air Force Station, Florida, USA, aboard an Atlas V-401 launch vehicle on August 12, 2005. The MRO spacecraft carries a very sophisticated scientific payload. Its primary science mission is to to provide global, regional survey, and targeted observations from a low altitude orbit for one Martian year (687 Earth days). After a seven month interplanetary transit, the spacecraft fired its six main engines and established a highly elliptical capture orbit at Mars. During the post-MOI early check-out period, four instruments acquired engineering-quality data. This was followed by five months of aerobraking operations. After aerobraking was terminated, a series of propulsive maneuvers were used to establish the desired low altitude science orbit. As the spacecraft is readied for its primary science mission, spacecraft and instrument checkout and deployment activities have continued.

orbiters↗

The Mars Science Laboratory (MSL) Entry, Descent And Landing Instrumentation (MEDLI): Hardware Performance and Data Reconstruction

The Mars Science Laboratory (MSL) Entry, Descent and Landing Instrumentation (MEDLI) hardware was a first-of-its-kind sensor system that gathered temperature and pressure readings on the MSL heatshield during Mars entry on August 6, 2012. MEDLI began as challenging instrumentation problem, and has been a model of collaboration across multiple NASA organizations. After the culmination of almost 6 years of effort, the sensors performed extremely well, collecting data from before atmospheric interface through parachute deploy. This paper will summarize the history of the MEDLI project and hardware development, including key lessons learned that can apply to future instrumentation efforts. MEDLI returned an unprecedented amount of high-quality engineering data from a Mars entry vehicle. We will present the performance of the 3 sensor types: pressure, temperature, and isotherm tracking, as well as the performance of the custom-built sensor support electronics. A key component throughout the MEDLI project has been the ground testing and analysis effort required to understand the returned flight data. Although data analysis is ongoing through 2013, this paper will reveal some of the early findings on the aerothermodynamic environment that MSL encountered at Mars, the response of the heatshield material to that heating environment, and the aerodynamic performance of the entry vehicle. The MEDLI data results promise to challenge our engineering assumptions and revolutionize the way we account for margins in entry vehicle design.

Little, Alan↗

Development and Testing of Functionally Operative and Visually Appealing Remote Firing Room Displays and Applications

This internship provided an opportunity for an intern to work with NASA's Ground Support Equipment (GSE) for the Spaceport Command and Control System (SCCS) at Kennedy Space Center as a remote display developer, under NASA technical mentor Kurt Leucht. The main focus was on creating remote displays and applications for the hypergolic and high pressure helium subsystem team to help control the filling of the respective tanks. As a remote display and application developer for the GSE hypergolic and high pressure helium subsystem team the intern was responsible for creating and testing graphical remote displays and applications to be used in the Launch Control Center (LCC) on the Firing Room's computers. To become more familiar with the subsystem, the individual attended multiple project meetings and acquired their specific requirements regarding what needed to be included in the software. After receiving the requirements for the displays, the next step was to create displays that had both visual appeal and logical order using the Display Editor, on the Virtual Machine (VM). In doing so, all Compact Unique Identifiers (CUI), which are associated with specific components within the subsystem, were need to be included in each respective display for the system to run properly. Then, once the display was created it was to be tested to ensure that the display runs as intended by using the Test Driver, also found on the VM. This Test Driver is a specific application that checks to make sure all the CUIs in the display are running properly and returning the correct form of information. After creating and locally testing the display it needed to go through further testing and evaluation before deemed suitable for actual use. For the remote applications the intern was responsible for creating a project that focused on channelizing each component included in each display. The core of the application code was created by setting up spreadsheets and having an auto test generator, generate the complete code structure. This application code was then loaded and ran on a testing environment set to ensure the code runs as anticipated. By the end of the semester-long experience at NASA's Kennedy Space Center, the individual should have gained great knowledge and experience in various areas of both display and application development and testing. They were able to demonstrate this new knowledge obtained by creating multiple successful remote displays that will one day be used by the hypergolic and high pressure helium subsystem team in the LCC's firing rooms to service the new Orion spacecraft. The completed display channelization application will be used to receive verification from NASA quality engineers.

Display Devices↗

Achieving Improved Reliability with Failure Analysis

Reliability is the ability of a product to properly function, within specified performance limits, for a specified period of time, under the life cycle application conditions. Failure analysis is a vital tool in the effort to ensure reliability of electronic products and systems throughout their product lifecycle. Today, organizations involved in activities within the electronics supply chain are facing new challenges, not just from complex assembly styles, harsher lifecycle environments, and sophisticated supply chains, but also from customers who are demanding a quicker turn-around. Unfortunately, root cause failure analysis is often performed incompletely, leading to a poor understanding of failure mechanisms and causes and, customer dissatisfaction due to recurring failures. The PDC starts with an introduction to reliability concepts, physics of failure and an overview of failure mechanisms that affect PCBs, PCBAs and components. The PDC then dives into root cause hypothesizing techniques (Pareto, FMEA, fishbone, FTA), non-destructive and destructive analysis and, materials characterization will be discussed. Numerous failure analysis case studies will be used to illustrate the techniques and analysis principles to arrive at the root cause(s) of field failures on printed circuit boards, active components, and assemblies. What Will You Learn: Topics include: Overview of Reliability Concepts Failure mechanisms of electronic products Root cause analysis Failure analysis techniques -Non-destructive techniques (optical, CSAM etc.) -Destructive analysis (DPA, Decap, FIB etc.) -Materials characterization (XRF, EDS, TMA/DSC etc.) Who Will Benefit: Reliability engineers, failure analysis engineers, engineering managers, design engineers, component engineers, quality assurance functions and, personnel involved with reliability activities within their company.

non-destructive techniques↗

Growing the NASA Safety and Mission Assurance (SMA) Workforce of Tomorrow

The NASA Safety Center (NSC) was established in2006 in response to Columbia Accident Investigation Board (CAIB) recommendations to strengthen NASA’s safety program. The NSC supports all NASA centers and facilities. The NSC fosters world-class Safety and Mission Assurance (SMA) support for NASA programs and projects through professional development activities and the advancement of the following SMA technical disciplines: - Aviation Safety - Operational Safety - Quality Engineering - Reliability and Maintainability - SMA Technical Leadership - Software Assurance - System Safety The NSC’s Technical Excellence Office (TEO) is charged with encouraging technical excellence in NASA’s SMA community primarily through professional development products and services. TEO’s first initiative was the SMA Technical Excellence Program (STEP). STEP is a career-oriented, professional development roadmap for safety professionals, which is designed for the employee to learn specific knowledge and skills to improve performance in their current role.

Safety and Mission Assurance↗

Assuring Quality in High-Consequence Engineering

In high-consequence engineering organizations, such as Sandia, quality assurance may be heavily dependent on staff competency. Competency-dependent quality assurance models are at risk when the environment changes, as it has with increasing attrition rates, budget and schedule cuts, and competing program priorities. Risks in Sandia's competency-dependent culture can be mitigated through changes to hiring, training, and customer engagement approaches to manage people, partners, and products. Sandia's technical quality engineering organization has been able to mitigate corporate-level risks by driving changes that benefit all departments, and in doing so has assured Sandia's commitment to excellence in high-consequence engineering and national service.

42 ENGINEERING↗

Marrying Quality Assurance with Design Engineering - A Winning Partnership! But, a Cultural Divide

Investors would like to be confident that a PV plant will work as promised before investing large sums of money. Data showing that PV modules can withstand thousands of hours of accelerated testing are a comfort, but are not sufficient to characterize the economic useful life (EUL) of the whole PV system. An inability to be confident of every aspect of the system can motivate less favorable contract terms. In the end, a winning partnership is obtained when a carefully engineered, durable design is married with a robust quality management system and the marriage is extended across all parts of the value chain. However, this marriage is challenging because of the conventional cultural divide between design engineers and quality management specialists. International standards are being developed to facilitate this partnership and include technology-specific requirements in the quality management systems used for component manufacture and system design, construction and operation.

14 SOLAR ENERGY↗

Marrying Quality Assurance with Design Engineering - A Winning Partnership! But, a Cultural Divide?: Preprint

Investors would like to be confident that a PV plant will work as promised before investing large sums of money. Data showing that PV modules can withstand thousands of hours of accelerated testing are a comfort, but are not sufficient. An inability to be confident of every aspect of the system can motivate higher interest rates; high degradation or failure rates can substantially decrease the return on investment and the value of the plant for resale later on. In the end, a winning partnership is obtained when a carefully engineered, durable design is married with a robust quality management system and the marriage is extended across all parts of the value chain. However, this marriage is challenging because of the conventional cultural divide between design engineers and quality management specialists. This paper discusses the motivation for increased emphasis on quality assurance and describes three new standards that detail requirements for a higher level of quality assurance for 1) PV module manufacturing, 2) inverter and other balance-of-systems (BOS) manufacturing, and 3) control of the system installation and operation. The paper concludes with a discussion of the challenges and benefits of marrying the quality assurance program with further optimization of the PV system design.

14 SOLAR ENERGY↗

Surface engineering of the quality factor of metal coated microcantilevers

We performed noise measurements to obtain the quality factor (Q) and frequency shift of gold coated microcantilevers before and after surface modification using focused ion beam. As a result of our studies, it is demonstrated that surface engineering offers a promising method to control and increase the Q factor up to 50% for operation in vacuum. Surface modification could also lead to deviations from the known Q ∼ P{sup −1} behavior at low vacuum pressures P within the molecular regime. Finally, at higher pressures within the continuum regime, where Q is less sensitive to surface changes, a power scaling Q ∼ P{sup c} with c ≈ 0.3 was found instead of c = 0.5. The latter is explained via a semi-empirical formulation to account for continuum dissipation mechanisms at significant Reynolds numbers Re ∼ 1.

71 CLASSICAL AND QUANTUM MECHANICS, GENERAL PHYSIC↗

Prototyping and implementing flight qualifiable semicustom CMOS P-well bulk integrated circuits in the JPL environment

Presently, there are many difficulties associated with implementing application specific custom or semi-custom (standard cell based) integrated circuits (ICs) into JPL flight projects. One of the primary difficulties is developing prototype semi-custom integrated circuits for use and evaluation in engineering prototype flight hardware. The prototype semi-custom ICs must be extremely cost-effective and yet still representative of flight qualifiable versions of the design. A second difficulty is encountered in the transport of the design from engineering prototype quality to flight quality. Normally, flight quality integrated circuits have stringent quality standards, must be radiation resistant and should consume minimal power. It is often not necessary or cost effective, however, to impose such stringent quality standards on engineering models developed for systems analysis in controlled lab environments. This article presents work originally initiated for ground based applications that also addresses these two problems. Furthermore, this article suggests a method that has been shown successful in prototyping flight quality semi-custom ICs through the Metal Oxide Semiconductor Implementation Service (MOSIS) program run by the University of Southern California's Information Sciences Institute. The method has been used successfully to design and fabricate through the MOSIS three different semi-custom prototype CMOS p-well chips. The three designs make use of the work presented and were designed consistent with design techniques and structures that are flight qualifiable, allowing one hour transfer of the design from engineering model status to flight qualifiable foundry-ready status through methods outlined in this article.

Olson, E. M.↗

Industrial Engineering Tool Use in Quality Improvement Projects

This paper presents the results of an examination of industrial engineering tool use in Six Sigma projects for a contractor providing specialty manufacturing and service activities for a United States federal government agency.

99 GENERAL AND MISCELLANEOUS↗

Study of small civil turbofan engines applicable to military trainer airplanes

Small turbofan engine design concepts were applied to military trainer airplanes to establish the potential for commonality between civil and military engines. Several trainer configurations were defined and studied. A ""best'' engine was defined for the trainer mission, and sensitivity analyses were performed to determine the effects on airplane size and efficiency of wing loading, power loading, configuration, aerodynamic quality, and engine quality. It is concluded that a small civil aircraft is applicable to military trainer airplanes. Aircraft designed with these engines are smaller, less costly, and more efficient than existing trainer aircraft.

Heldenbrand, R. W.↗

In-flight pilot evaluations of the flying qualities of a four-engine jet transport

The flying qualities of the CV-990 jet transport were evaluated over the normal operating flight envelope and in smooth air to provide baseline data for transport airplanes. Pilot ratings of airplane handling characteristics for specific test conditions and configurations from approach to normal cruise were compared with various flying qualities criteria. In general, the CV-990 flying qualities were evaluated as satisfactory, and the evaluations supported transport flying qualities criteria. The Dutch roll damping was rated more satisfactory than was predicted by the flying qualities criteria. The pilots found rudder coordination for the yaw generated during high roll rates very difficult. They preferred to control with roll and pitch controls and to use the yaw damper to provide the required rudder coordination.

Holleman, E. C.↗

Total Quality Management in Space Shuttle Main Engine manufacturing

The Total Quality Management (TQM) philosophy developed in the Marshall Space Flight Center (MSFC) is briefly reviewed and the ongoing TQM implementation effort which is being pursued through the continuous improvement (CI) process is discussed. TQM is based on organizational excellence which integrates the new supportive culture with the technical tools necessary to identify, assess, and correct manufacturing processes. Particular attention is given to the prime contractor's change to the organizational excellence management philosophy in SSME manufacturing facilities.

Ding, J.↗