A Structure for Lessons Learned Capture with Several Lessons from EEE Parts and Printed Circuit Boards
Explore the source record for details and available documents.
Human Factors↗
SEARCH · Engineering Papers
Results for “Lessons learned”
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.
2010 CEOS Field Reflectance Intercomparisons Lessons Learned
This paper summarizes lessons learned from the 2009 and 2010 joint field campaigns to Tuz Golu, Turkey. Emphasis is placed on the 2010 campaign related to understanding the equipment and measurement protocols, processing schemes, and traceability to SI quantities. Participants in both 2009 and 2010 used an array of measurement approaches to determine surface reflectance. One lesson learned is that even with all of the differences in collection between groups, the differences in reflectance are currently dominated by instrumental artifacts including knowledge of the white reference. Processing methodology plays a limited role once the bi-directional reflectance of the white reference is used rather than a hemispheric-directional value. The lack of a basic set of measurement protocols, or best practices, limits a group s ability to ensure SI traceability and the development of proper error budgets. Finally, rigorous attention to sampling methodology and its impact on instrument behavior is needed. The results of the 2009 and 2010 joint campaigns clearly demonstrate both the need and utility of such campaigns and such comparisons must continue in the future to ensure a coherent set of data that can span multiple sensor types and multiple decades.
Thome, Kurtis↗
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↗
Starling CubeSat Swarm: Flight Results and Lessons Learned
A review of lessons learned from the NASA Starling primary mission.
Lessons Learned↗
Best Practices for Researching and Documenting Lessons Learned
Identification, resolution, and avoidance of technical and programmatic issues are important for ensuring safe and successful space missions. Although the importance of applying lessons learned to reduce risk is frequently stressed, there is little material available to help technical and management personnel research and document lessons learned. Collecting, researching, identifying, and documenting lessons learned that will be useful to current and future management and engineering personnel is not always a straightforward task. This white paper presents lessons learned and best practices concerning the research and documentation of technical and organizational lessons learned. It is intended to enable organizations to initiate or improve lessons learned research and documentation efforts. The content of this white paper is based on four technical lessons learned projects conducted by the United Space Alliance (USA) Flight Design and Dynamics Department, in support of the NASA/Johnson Space Center (JSC) Flight Design and Dynamics Division. Each project published a report, titled as follows: (1) GPS Lessons Learned From the ISS, Space Shuttle and X-38; (2) Lessons Learned From Seven Space Shuttle Missions; (3) Space Shuttle Rendezvous and Proximity Operations Experience Report; and (4) Navigation Technical History with Lessons Learned. The four projects were different in availability of subject matter experts and primary source material, subject scope, and the level of effort required to produce the final report. However, generic lessons can be drawn from all of them. The best practices will be discussed by the phases of report research and development: (1) Defining Report Requirements, Project Organization, and Schedule; (2) Collection and Analysis of Source Material; (3) Writing and Integrating the Report; and (4) Review and Revision of the Report.
Goodman, John L.↗
Lessons Learned for Improving Spacecraft Ground Operations
NASA policy requires each Program or Project to develop a plan for how they will address Lessons Learned. Projects have the flexibility to determine how best to promote and implement lessons learned. A large project might budget for a lessons learned position to coordinate elicitation, documentation and archival of the project lessons. The lessons learned process crosses all NASA Centers and includes the contactor community. o The Office of The Chief Engineer at NASA Headquarters in Washington D.C., is the overall process owner, and field locations manage the local implementation. One tool used to transfer knowledge between program and projects is the Lessons Learned Information System (LLIS). Most lessons come from NASA in partnership with support contractors. A search for lessons that might impact a new design is often performed by a contractor team member. Knowledge is not found with only one person, one project team, or one organization. Sometimes, another project team, or person, knows something that can help your project or your task. Knowledge sharing is an everyday activity at the Kennedy Space Center through storytelling, Kennedy Engineering Academy presentations and through searching the Lessons Learned Information system. o Project teams search the lessons repository to ensure the best possible results are delivered. o The ideas from the past are not always directly applicable but usually spark new ideas and innovations. Teams have a great responsibility to collect and disseminate these lessons so that they are shared with future generations of space systems designers. o Leaders should set a goal for themselves to host a set numbers of lesson learned events each year and do more to promote multiple methods of lessons learned activities. o High performing employees are expected to share their lessons, however formal knowledge sharing presentation are not the norm for many employees.
Bell, Michael↗
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's Lessons Learned and Technical Standards: A Logical Marriage
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 NASA's accomplishments for more than forty 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. Lessons Learned have formed the foundation for discoveries, inventions, improvements, textbooks, and Technical Standards.
Gill, Paul↗
The Value of Identifying and Recovering Lost GN&C Lessons Learned: Aeronautical, Spacecraft, and Launch Vehicle Examples
Within the broad aerospace community the importance of identifying, documenting and widely sharing lessons learned during system development, flight test, operational or research programs/projects is broadly acknowledged. Documenting and sharing lessons learned helps managers and engineers to minimize project risk and improve performance of their systems. Often significant lessons learned on a project fail to get captured even though they are well known 'tribal knowledge' amongst the project team members. The physical act of actually writing down and documenting these lessons learned for the next generation of NASA GN&C engineers fails to happen on some projects for various reasons. In this paper we will first review the importance of capturing lessons learned and then will discuss reasons why some lessons are not documented. A simple proven approach called 'Pause and Learn' will be highlighted as a proven low-impact method of organizational learning that could foster the timely capture of critical lessons learned. Lastly some examples of 'lost' GN&C lessons learned from the aeronautics, spacecraft and launch vehicle domains are briefly highlighted. In the context of this paper 'lost' refers to lessons that have not achieved broad visibility within the NASA-wide GN&C CoP because they are either undocumented, masked or poorly documented in the NASA Lessons Learned Information System (LLIS).
Dennehy, Cornelius J.↗
Lessons Learned in Building the Ares Projects
Since being established in 2005, the Ares Projects at Marshall Space Flight Center have been making steady progress designing, building, testing, and flying the next generation of exploration launch vehicles. Ares is committed to rebuilding crucial capabilities from the Apollo era that made the first human flights to the Moon possible, as well as incorporating the latest in computer technology and changes in management philosophy. One example of an Apollo-era practice has been giving NASA overall authority over vehicle integration activities, giving civil service engineers hands-on experience in developing rocket hardware. This knowledge and experience help make the agency a "smart buyer" of products and services. More modern practices have been added to the management tool belt to improve efficiency, cost effectiveness, and institutional knowledge, including knowledge management/capture to gain better insight into design and decision making; earned value management, where Ares won a NASA award for its practice and implementation; designing for operability; and Lean Six Sigma applications to identify and eliminate wasted time and effort. While it is important to learn technical lessons like how to fly and control unique rockets like the Ares I-X flight test vehicle, the Ares management team also has been learning important lessons about how to manage large, long-term projects.
Sumrall, John Phil↗
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.↗
Constellation Program: Lessons Learned: Executive Summary - Volume 1
This document (Volume I) provides an executive summary of the lessons learned from the Constellation Program. A companion Volume II provides more detailed analyses for those seeking further insight and information. In this volume, Section 1.0 introduces the approach in preparing and organizing the content to enable rapid assimilation of the lessons. Section 2.0 describes the contextual framework in which the Constellation Program was formulated and functioned that is necessary to understand most of the lessons. Context of a former program may seem irrelevant in the heady days of new program formulation. However, readers should take some time to understand the context. Many of the lessons would be different in a different context, so the reader should reflect on the similarities and differences in his or her current circumstances. Section 3.0 summarizes key findings developed from the significant lessons learned at the program level that appear in Section 4.0. Readers can use the key findings in Section 3.0 to peruse for particular topics, and will find more supporting detail and analyses in Section 4.0 in a topical format. Appendix A contains a white paper describing the Constellation Program formulation that may be of use to readers wanting more context or background information. The reader will no doubt recognize some very similar themes from previous lessons learned, blue-ribbon committee reviews, National Academy reviews, and advisory panel reviews for this and other large-scale human spaceflight programs; including Apollo, Space Shuttle, Shuttle/Mir, and the ISS. This could represent an inability to learn lessons from previous generations; however, it is more likely that similar challenges persist in the Agency structure and approach to program formulation, budget advocacy, and management. Perhaps the greatest value of these Constellation lessons learned can be found in viewing them in context with these previous efforts to guide and advise the Agency and its stakeholders.
Constellation Program↗
Lessons Learned in Engineering
This Contractor Report (CR) is a compilation of Lessons Learned in approximately 55 years of engineering experience by each James C. Blair, Robert S. Ryan, and Luke A. Schutzenhofer. The lessons are the basis of a course on Lessons Learned that has been taught at Marshall Space Flight Center. The lessons are drawn from NASA space projects and are characterized in terms of generic lessons learned from the project experience, which are further distilled into overarching principles that can be applied to future projects. Included are discussions of the overarching principles followed by a listing of the lessons associated with that principle. The lesson with sub-lessons are stated along with a listing of the project problems the lesson is drawn from, then each problem is illustrated and discussed, with conclusions drawn in terms of Lessons Learned. The purpose of this CR is to provide principles learned from past aerospace experience to help achieve greater success in future programs, and identify application of these principles to space systems design. The problems experienced provide insight into the engineering process and are examples of the subtleties one experiences performing engineering design, manufacturing, and operations.
Blair, J. C.↗
Lessons Learned in Engineering
This Contractor Report (CR) is a compilation of Lessons Learned in approximately 55 years of engineering experience by each James C. Blair, Robert S. Ryan, and Luke A. Schutzenhofer. The lessons are the basis of a course on Lessons Learned that has been taught at Marshall Space Flight Center. The lessons are drawn from NASA space projects and are characterized in terms of generic lessons learned from the project experience, which are further distilled into overarching principles that can be applied to future projects. Included are discussions of the overarching principles followed by a listing of the lessons associated with that principle. The lesson with sub-lessons are stated along with a listing of the project problems the lesson is drawn from, then each problem is illustrated and discussed, with conclusions drawn in terms of Lessons Learned. The purpose of this CR is to provide principles learned from past aerospace experience to help achieve greater success in future programs, and identify application of these principles to space systems design. The problems experienced provide insight into the engineering process and are examples of the subtleties one experiences performing engineering design, manufacturing, and operations. The supplemental CD contains accompanying PowerPoint presentations.
Blair, James C.↗
X-31 Mishap - Lessons Learned
Slide presentation sharing lessons learned from the X-31 mishap.
Larson, Richard R.↗
Ramp Traffic Console (RTC) Lessons Learned
This presentation provides lessons learned for use of ramp traffic control (RTC) and ramp manager traffic console (RMTC) features of the ATD-2 (Airspace Technology Demonstration 2) Integrated Arrival, Departure, and Surface (IADS) system in an operational environment.
Jung, Yoon↗
Airspace Technology Demonstration 2 (ATD-2): CDM CAT NTML Lessons Learned
This presentation conveys lessons learned about data, data sources, and TMIs from the ATD-2 field demonstration.
TMI↗
Transitioning Sixty Years of NASA Spacesuit Knowledge Capture Lessons Learned to Searchable Knowledge Transfer Databases
Sixty years of spacesuit knowledge capture and lessons learned by spacesuit subject matter experts are documented on videos and presentations and archived with the NASA Engineering and Safety Center (NESC) Academy. The NESC Academy is a web-based platform that hosts online courses by technical experts. A process is underway to transition these decades of lessons learned from the U.S. Spacesuit Knowledge Capture Program Library into more quicky searchable databases and to proactively provide this information to those working on spacesuit projects. Hundreds of lessons learned from Project Mercury, Gemini, Apollo, Apollo- Soyuz Test Project, Skylab, Space Shuttle, International Space Station, and Artemis have been captured in a format that can be quickly searched, enabling users to find information directly applicable to their needs. Transitioning this information to a NASA wiki page will further enhance search and retrieval of data immediately useful to users. This paper provides information about how the lessons learned were determined and how to access them.
spacesuit↗