Engineering topics

Garcia, Danny

Publications and source records attributed to Garcia, Danny.

10 records

NASA NTRS2005

Engineering Lessons Learned and Systems Engineering Applications

Systems Engineering is fundamental to good engineering, which in turn depends on the integration and application of engineering lessons learned. Thus, good Systems Engineering also depends on systems engineering lessons learned from within the aerospace industry being documented and applied. About ten percent of the engineering lessons learned documented in the NASA Lessons Learned Information System are directly related to Systems Engineering. A key issue associated with lessons learned datasets is the communication and incorporation of this information into engineering processes. As part of the NASA Technical Standards Program activities, engineering lessons learned datasets have been identified from a number of sources. These are being searched and screened for those having a relation to Technical Standards. This paper will address some of these Systems Engineering Lessons Learned and how they are being related to Technical Standards within the NASA Technical Standards Program, including linking to the Agency's Interactive Engineering Discipline Training Courses and the life cycle for a flight vehicle development program.

Gill, Paul S.↗

NASA NTRS2005

Engineering Lessons Learned and Systems Engineering Applications

Systems Engineering is fundamental to good engineering, which in turn depends on the integration and application of engineering lessons learned and technical standards. Thus, good Systems Engineering also depends on systems engineering lessons learned from within the aerospace industry being documented and applied. About ten percent of the engineering lessons learned documented in the NASA Lessons Learned Information System are directly related to Systems Engineering. A key issue associated with lessons learned datasets is the communication and incorporation of this information into engineering processes. Systems Engineering has been defined (EINIS-632) as "an interdisciplinary approach encompassing the entire technical effort to evolve and verify an integrated and life-cycle balanced set of system people, product, and process solutions that satisfy customer needs". Designing reliable space-based systems has always been a goal for NASA, and many painful lessons have been learned along the way. One of the continuing functions of a system engineer is to compile development and operations "lessons learned" documents and ensure their integration into future systems development activities. They can produce insights and information for risk identification identification and characterization. on a new project. Lessons learned files from previous projects are especially valuable in risk

Gill, Paul S.↗

NASA NTRS2003

NASA Materials Related Lessons Learned

Lessons Learned have been the basis for our accomplishments throughout the ages. They have been passed down from father to son, mother to daughter, teacher to pupil, and older to younger worker. Lessons Learned have also been the basis for the nation s accomplishments for more than 200 years. Both government and industry have long recognized the need to systematically document and utilize the knowledge gained from past experiences in order to avoid the repetition of failures and mishaps. Through the knowledge captured and recorded in Lessons Learned from more than 80 years of flight in the Earth s atmosphere, NASA s materials researchers are constantly working to develop stronger, lighter, and more durable materials that can withstand the challenges of space. The Agency s talented materials engineers and scientists continue to build on that rich tradition by using the knowledge and wisdom gained from past experiences to create futuristic materials and technologies that will be used in the next generation of advanced spacecraft and satellites that may one day enable mankind to land men on another planet or explore our nearest star. These same materials may also have application here on Earth to make commercial aircraft more economical to build and fly. With the explosion in technical accomplishments over the last decade, the ability to capture knowledge and have the capability to rapidly communicate this knowledge at lightning speed throughout an organization like NASA has become critical. Use of Lessons Learned is a principal component of an organizational culture committed to continuous improvement.

Garcia, Danny↗

NASA NTRS2003

Engineering Lessons Learned and Technical Standards Integration: Capturing Key Technologies for Future Space Missions

Capturing engineering lessons learned derived from past experiences and new technologies, then integrating them with technical standards, provides a viable process for enhancing engineering capabilities. The development of future space missions will require ready access, not only to the latest technical standards, but also to lessons learned derived from past experiences and new technologies. The integration of this information such that it is readily accessible by engineering and programmatic personnel is a key aspect of enabling technology. This paper addresses the development of a new and innovative Lessons Learned/Best Practices/Applications Notes--Standards Integration System, including experiences with its initial implementation as a pilot effort within the NASA Technical Standards Program. Included are metrics on the Program, feedbacks from users, future plans, and key issues that are being addressed to expand the System's utility. The objective is the enhancement of engineering capabilities on all aspects of systems development applicable to the success of future space missions.

Mellen, Daniele P.↗

NASA NTRS2002

NASA Materials Related Lessons Learned

Lessons Learned have been the basis for our accomplishments throughout the ages. They have been passed down from father to son, mother to daughter, teacher to pupil, and older to younger worker. Lessons Learned have also been the basis for the nation's accomplishments for more than 200 years. Both government and industry have long recognized the need to systematically document and utilize the knowledge gained from past experiences in order to avoid the repetition of failures and mishaps. Through the knowledge captured and recorded in Lessons Learned from more than 80 years of flight in the Earth's atmosphere, NASA's materials researchers are constantly working to develop stronger, lighter, and more durable materials that can withstand the challenges of space. The Agency's talented materials engineers and scientists continue to build on that rich tradition by using the knowledge and wisdom gained from past experiences to create futurist materials and technologies that will be used in the next generation of advanced spacecraft and satellites that may one day enable mankind to land men on another planet or explore our nearest star. These same materials may also have application here on Earth to make commercial aircraft more economical to build and fly. With the explosion in technical accomplishments over the last decade, the ability to capture knowledge and have the capability to rapidly communicate this knowledge at lightning speed throughout an organization like NASA has become critical. Use of Lessons Learned is a principal component of an organizational culture committed to continuous improvement.

Garcia, Danny↗

NASA NTRS2002

NASA Technical Standards Program and Implications for Lessons Learned and Technical Standard Integration

The National Aeronautics and Space Agency consists of fourteen Facilities throughout the United States. They are organized to support the Agency's principal Enterprises: (1) Space Science, (2) Earth Science, (3) Aerospace Technology, (4) Human Exploration and Development of Space, and (5) Biological and Physical Research. Technical Standards are important to the activities of each Enterprise and have been an integral part in the development and operation of NASA Programs and Projects since the Agency was established in 1959. However, for years each Center was responsible for its own standards development and selection of non-NASA technical standards that met the needs of Programs and Projects for which they were responsible. There were few Agencywide applicable Technical Standards, mainly those in area of safety. Department of Defense Standards and Specifications were the foundation and main source for Technical Standards used by the Agency. This process existed until about 1997 when NASA embarked on a Program to convert NASA's Center-developed Technical Standards into Agencywide endorsed NASA Preferred Technical Standards. In addition, action was taken regarding the formal adoption of non-NASA Technical Standards (DOD, SAE, ASTM, ASME, IEEE, etc.) as NASA Preferred Technical Standards.

Gill, Paul S.↗

NASA NTRS2002

Lessons Learned and Technical Standards: A Logical Marriage for Future Space Systems Design

A comprehensive database of engineering lessons learned that corresponds with relevant technical standards will be a valuable asset to those engaged in studies on future space vehicle developments, especially for structures, materials, propulsion, control, operations and associated elements. In addition, this will enable the capturing of technology developments applicable to the design, development, and operation of future space vehicles as planned in the Space Launch Initiative. Using the time-honored tradition of passing on lessons learned while utilizing the newest information technology, NASA has launched an intensive effort to link lessons learned acquired through various Internet databases with applicable technical standards. This paper will discuss the importance of lessons learned, the difficulty in finding relevant lessons learned while engaged in a space vehicle development, and the new NASA effort to relate them to technical standards that can help alleviate this difficulty.

Gill, Paul S.↗

NASA NTRS2001

NASA's Lessons Learned and Technical Standards: A Logical Marriage

Gill, Paul↗

NASA NTRS2001

Lessons Learned and Technical Standards: A Logical Marriage

A comprehensive database of lessons learned that corresponds with relevant technical standards would be a boon to technical personnel and standards developers. The authors discuss the emergence of one such database within NASA, and show how and why the incorporation of lessons learned into technical standards databases can be an indispensable tool for government and industry. Passed down from parent to child, teacher to pupil, and from senior to junior employees, lessons learned have been the basis for our accomplishments throughout the ages. Government and industry, too, have long recognized the need to systematically document And utilize the knowledge gained from past experiences in order to avoid the repetition of failures and mishaps. The use of lessons learned is a principle component of any organizational culture committed to continuous improvement. They have formed the foundation for discoveries, inventions, improvements, textbooks, and technical standards. Technical standards are a very logical way to communicate these lessons. Using the time-honored tradition of passing on lessons learned while utilizing the newest in information technology, the National Aeronautics and Space Administration (NASA) has launched an intensive effort to link lessons learned with specific technical standards through various Internet databases. This article will discuss the importance of lessons learned to engineers, the difficulty in finding relevant lessons learned while engaged in an engineering project, and the new NASA project that can help alleviate this difficulty. The article will conclude with recommendations for more expanded cross-sectoral uses of lessons learned with reference to technical standards.

Gill, Paul↗

NASA NTRS1996

Failure-Modes-And-Effects Analysis Of Software Logic

Rigorous analysis applied early in design effort. Method of identifying potential inadequacies and modes and effects of failures caused by inadequacies (failure-modes-and-effects analysis or "FMEA" for short) devised for application to software logic.

Garcia, Danny↗