Search NASA⌕ Search

Engineering topics

Lalli, Vincent R.

Publications and source records attributed to Lalli, Vincent R..

9 records
All sourcesNASA NTRSDOE OSTI
NASA NTRS2000

Reliability and Maintainability (RAM) Training

The theme of this manual is failure physics-the study of how products, hardware, software, and systems fail and what can be done about it. The intent is to impart useful information, to extend the limits of production capability, and to assist in achieving low-cost reliable products. In a broader sense the manual should do more. It should underscore the urgent need CI for mature attitudes toward reliability. Five of the chapters were originally presented as a classroom course to over 1000 Martin Marietta engineers and technicians. Another four chapters and three appendixes have been added, We begin with a view of reliability from the years 1940 to 2000. Chapter 2 starts the training material with a review of mathematics and a description of what elements contribute to product failures. The remaining chapters elucidate basic reliability theory and the disciplines that allow us to control and eliminate failures.

Lalli, Vincent R.↗
NASA NTRS1997

Software Design Improvements: Software Quality and the Design and Inspection Process - Part 2

The application of assurance engineering techniques improves the duration of failure-free performance of software. The totality of features and characteristics of a software product are what determine its ability to satisfy customer needs. Software in safety-critical systems is very important to NASA. We follow the System Safety Working Groups definition for system safety software as: 'The optimization of system safety in the design, development, use and maintenance of software and its integration with safety-critical systems in an operational environment. 'If it is not safe, say so' has become our motto. This paper goes over methods that have been used by NASA to make software design improvements by focusing on software quality and the design and inspection process.

Lalli, Vincent R.↗
NASA NTRS1997

Designing for Maintainability and System Availability

The final goal for a delivered system (whether a car, aircraft, avionics box or computer) should be its availability to operate and perform its intended function over its expected design life. Hence, in designing a system, we cannot think in terms of delivering the system and just walking away. The system supplier needs to provide support throughout the operating life of the product. Here, supportability requires an effective combination of reliability, maintainability, logistics and operations engineering (as well as safety engineering) to have a system that is available for its intended use throughout its designated mission lifetime. Maintainability is a key driving element in the effective support and upkeep of the system as well as providing the ability to modify and upgrade the system throughout its lifetime. This paper then, will concentrate on maintainability and its integration into the system engineering and design process. The topics to be covered include elements of maintainability, the total cost of ownership, how system availability, maintenance and logistics costs and spare parts cost effect the overall program costs. System analysis and maintainability will show how maintainability fits into the overall systems approach to project development. Maintainability processes and documents will focus on how maintainability is to be performed and what documents are typically generated for a large scale program. Maintainability analysis shows how trade-offs can be performed for various alternative components. The conclusions summarize the paper and are followed by specific problems for hands-on training.

Lalli, Vincent R.↗
NASA NTRS1997

Software Design Improvements: Software Benefits and Limitations - Part 1

Computer hardware and associated software have been used for many years to process accounting information, to analyze test data and to perform engineering analysis. Now computers and software also control everything from automobiles to washing machines and the number and type of applications are growing at an exponential rate. The size of individual program has shown similar growth. Furthermore, software and hardware are used to monitor and/or control potentially dangerous products and safety-critical systems. These uses include everything from airplanes and braking systems to medical devices and nuclear plants. The question is: how can this hardware and software be made more reliable? Also, how can software quality be improved? What methodology needs to be provided on large and small software products to improve the design and how can software be verified?

Lalli, Vincent R.↗
NASA NTRS1997

Training Manual for Elements of Interface Definition and Control

The primary thrust of this manual is to ensure that the format and information needed to control interfaces between equipment are clear and understandable. The emphasis is on controlling the engineering design of the interface and not on the functional performance requirements of the system or the internal workings of the interfacing equipment. Interface control should take place, with rare exception, at the interfacing elements and no further. There are two essential sections of the manual. Chapter 2, Principles of Interface Control, discusses how interfaces are defined. It describes different types of interfaces to be considered and recommends a format for the documentation necessary for adequate interface control. Chapter 3, The Process: Through the Design Phases, provides tailored guidance for interface definition and control. This manual can be used to improve planned or existing interface control processes during system design and development. It can also be used to refresh and update the corporate knowledge base. The information presented herein will reduce the amount of paper and data required in interface definition and control processes by as much as 50 percent and will shorten the time required to prepare an interface control document. It also highlights the essential technical parameters that ensure that flight subsystems will indeed fit together and function as intended after assembly and checkout.

Lalli, Vincent R.↗
NASA NTRS1994

Design for reliability: NASA reliability preferred practices for design and test

This tutorial summarizes reliability experience from both NASA and industry and reflects engineering practices that support current and future civil space programs. These practices were collected from various NASA field centers and were reviewed by a committee of senior technical representatives from the participating centers (members are listed at the end). The material for this tutorial was taken from the publication issued by the NASA Reliability and Maintainability Steering Committee (NASA Reliability Preferred Practices for Design and Test. NASA TM-4322, 1991). Reliability must be an integral part of the systems engineering process. Although both disciplines must be weighed equally with other technical and programmatic demands, the application of sound reliability principles will be the key to the effectiveness and affordability of America's space program. Our space programs have shown that reliability efforts must focus on the design characteristics that affect the frequency of failure. Herein, we emphasize that these identified design characteristics must be controlled by applying conservative engineering principles.

Lalli, Vincent R.↗
NASA NTRS1992

Reliability training

Discussed here is failure physics, the study of how products, hardware, software, and systems fail and what can be done about it. The intent is to impart useful information, to extend the limits of production capability, and to assist in achieving low cost reliable products. A review of reliability for the years 1940 to 2000 is given. Next, a review of mathematics is given as well as a description of what elements contribute to product failures. Basic reliability theory and the disciplines that allow us to control and eliminate failures are elucidated.

Lalli, Vincent R.↗
NASA NTRS1989

Model 0A wind turbine generator FMEA

The results of Failure Modes and Effects Analysis (FMEA) conducted for the Wind Turbine Generators are presented. The FMEA was performed for the functional modes of each system, subsystem, or component. The single-point failures were eliminated for most of the systems. The blade system was the only exception. The qualitative probability of a blade separating was estimated at level D-remote. Many changes were made to the hardware as a result of this analysis. The most significant change was the addition of the safety system. Operational experience and need to improve machine availability have resulted in subsequent changes to the various systems which are also reflected in this FMEA.

Klein, William E.↗