> **ESPO-DOC-420---XX-XX**
>
> **Earth Science Program Office**
>
> **Lessons Learned Implementation Plan**
>
> **November 13, 2023**

![](media/image1.png)

**Earth Science Program Office (ESPO)**

**Lessons Learned Implementation Plan**

November 13, 2023

APPROVED BY:

> \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
>
> Program Office System Engineer
>
> Earth Science Program Office
>
> GSFC -- Code 420
>
> \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
>
> Program Manager
>
> Earth Science Program Office
>
> GSFC -- Code 420

Goddard Space Flight Center

Greenbelt, Maryland

**Earth Science Program Office (ESPO)**

**Lessons Learned Implementation Plan**

November 13, 2023

CONCURRED BY:

  -------------------------------- -- -----------------------------------
                                      

                                      

                                      

                                      

                                      

                                      

                                      

                                      
  -------------------------------- -- -----------------------------------

Goddard Space Flight Center

Greenbelt, Maryland

CHANGE RECORD PAGE

  ----------- ---------- ------------------------------- --------------------
  **ISSUE**   **DATE**   **PAGES AFFECTED**              **DESCRIPTION**

  Original    TBD        All                             Baseline

                                                         

                                                         

                                                         

                                                         

                                                         

                                                         

                                                         

                                                         

                                                         

                                                         

                                                         

                                                         

                                                         

                                                         

                                                         

                                                         

                                                         

                                                         

                                                         

                                                         

                                                         

                                                         
  ----------- ---------- ------------------------------- --------------------

LIST OF AFFECTED PAGES

  -------- -------------- -------- -------------- -------- -------------- -------- --------------
  **Page   **Revision**   **Page   **Revision**   **Page   **Revision**   **Page   **Revision**
  \#**                    \#**                    \#**                    \#**     

                                                                                   

                                                                                   

                                                                                   

                                                                                   

                                                                                   

                                                                                   

                                                                                   

                                                                                   

                                                                                   

                                                                                   

                                                                                   

                                                                                   

                                                                                   

                                                                                   

                                                                                   

                                                                                   

                                                                                   

                                                                                   

                                                                                   

                                                                                   

                                                                                   

                                                                                   

                                                                                   

                                                                                   

                                                                                   

                                                                                   

                                                                                   

                                                                                   

                                                                                   

                                                                                   

                                                                                   
  -------- -------------- -------- -------------- -------- -------------- -------- --------------

**TABLE OF CONTENTS**

[**1.** **Introduction 7**](#introduction)

[1.1. Applicable Documents 8](#applicable-documents)

[2. Lessons Learned Process Overview
9](#lessons-learned-process-overview)

[2.1. Terms and Definitions 9](#terms-and-definitions)

[2.2. Lessons Learned Process 11](#lessons-learned-process)

[2.3. Roles and Responsibilities 14](#roles-and-responsibilities)

[2.4. Allocation of Lessons Learned Resources
15](#allocation-of-lessons-learned-resources)

[3. Lessons Learned Identification 16](#lessons-learned-identification)

[4. Lessons Learned Capture 17](#lessons-learned-capture)

[5. Lessons Learned Dissemination 19](#lessons-learned-dissemination)

[6. Lessons Learned Application 20](#lessons-learned-application)

[6.1. Lessons Learned Impact Assessment
20](#lessons-learned-impact-assessment)

[6.1.1. Impact Categories 20](#impact-categories)

[6.1.2. Impact Definitions 21](#impact-definitions)

[6.1.3. Estimation of Value 22](#estimation-of-value)

[7. Lessons Learned Documentation and Communication
23](#lessons-learned-documentation-and-communication)

[7.1. Lesson Learned Reports and Reporting Milestones
23](#lesson-learned-reports-and-reporting-milestones)

[7.2. Lesson Learned Awareness and Education
24](#lesson-learned-awareness-and-education)

[7.3. Recourse 24](#recourse)

[Appendix A -- Lessons Learned Input Form
25](#appendix-a-lessons-learned-input-form)

[Appendix B -- Description of Lessons Learned Submission Form Items
26](#appendix-b-description-of-lessons-learned-submission-form-items)

[Appendix C -- Categories for Lessons Learned Submission Form
27](#appendix-c-categories-for-lessons-learned-submission-form)

[Appendix D -- Specializations for Lessons Learned Submission Form
29](#appendix-d-specializations-for-lessons-learned-submission-form)

[Appendix E -- Acronym List 30](#appendix-e-acronym-list)

# Introduction 

NASA GSFC has embraced a Lessons Learned philosophy and has placed
expectations on projects to incorporate this practice in all elements
and across their entire life cycle. The Lessons Learned approach
contained in this document is based upon the Lessons Learned Procedures
and Guidelines GPG-[TBD]{.mark} for the NASA GSFC Flight Programs and
Projects Directorate and is consistent with NASA NPG 7120.5B NASA
Program and Project Management Processes and Requirements. Exhibit 1-1
shows the basic continuous Lessons Learned process.

Exhibit 1‑1. The Continuous Lessons Learned Process

The Lessons Learned approach has been tailored to the Earth Science
Program Office Projects (to best fulfill the project's needs to capture,
share and apply knowledge gained from this and other projects. The ESPO
has developed a Lessons Learned process that fits the needs of the
various project elements. The process places responsibility for
identifying, capturing, sharing and applying Lessons Learned in the
hands of the organizational level in which it impacts, while still
communicating these Lessons Learned up through Program/Project
management. This process is further described in Section 2.

The purpose of this Lessons Learned Plan (LLP) is to provide guidance
for the ESPO Projects to identify, capture, share and apply Lessons
Learned at all levels within the project. Project Lessons Learned is
integrated into the Project Systems Engineering and Management Processes
with the objective of incorporating Lessons Learned into the daily
activities of the project and staff. All Project staff members are
encouraged to participate in this process by identifying, capturing and
applying Lessons Learned.

The Lessons Learned Coordinator (LLC) is integral to the success of
Project Lessons Learned. The LLC provides a unique intersection of
engineering and programmatic Lessons Learned support. Programmatically,
the LLC maintains ownership of this Lessons Learned process and is
responsible for its overall implementation. The LLC establishes the
means for identification, capture and dissemination of Lessons Learned,
facilitates communication and evaluation of the value associated with
applying Lessons Learned on the Project. The LLC also plays an important
role in the Project by actively participating in and across the elements
and mission teams to assist in and perform efforts in support of sharing
Lessons Learned.

The Lessons Learned Process will continue to evolve as the Project
matures. For example, the Formulation/Project Manager (PM) and Mission
Systems Engineer (SE) will be involved in Lessons Learned activities
throughout the Project life cycle. As the element teams grow, much of
the Lessons Learned process will be handled at the element level and
lower. The same basic Lessons Learned approach will be utilized, but the
responsibilities and communication mechanisms will evolve during the
Project life cycle, with the PM remaining responsible for its
implementation.

## Applicable Documents

[NASA Program and Project Management Processes and
Requirements]{.underline}, NPG 7120.5B, NASA Procedures and Guidelines,
November 21, 2002

[Lessons Learned]{.underline}, GPG [TBD]{.mark} Goddard Procedures and
Guidelines, [TBD]{.mark}

[Systems Engineering]{.underline}, [GPG 71xx.x]{.mark}, System
Engineering Processes and Requirements, [TBD]{.mark}

[Systems Engineering Management Plan]{.underline}, GSFC 420.2-02-001-01,
Original, February 1, 2002

#  Lessons Learned Process Overview

Each Project utilizes a Lessons Learned approach that considers the
needs for Lessons Learned from a project, individual and organizational
perspective.

## Terms and Definitions

**Lesson Learned --** A lesson learned is defined as knowledge gained
that may have a positive or negative impact on a Project, individual or
other organizational element within NASA. A lesson learned fits into one
of four categories:

1.  **Red -- Urgent**; Item related to immediate concern with physical
    security, personnel health and safety, direct impact on mission
    success or significant expected effect on performance, schedule
    and/or cost.

2.  **Yellow -- Caution**; Item has the potential for impact to physical
    security, personnel health and safety, possible effect on mission
    success or influence on performance, schedule and/or cost.

3.  **Blue -- Information**; Item is provided for background information
    to protect physical security, personnel health and safety, mission
    success, performance, schedule and/or cost.

4.  

5.  

6.  

7.  

> 4\. **Green -- Good Work Practice**; Item is a positive example of an
> action, activity or practice that improves; physical security,
> personnel health and safety, mission success, performance, schedule
> and/or cost.

Lessons that are learned result from activities where something
different from an everyday event, or realization that an unexpected
occurrence, has taken place including an event, result or occurrence
that represents a success or failure. Outcomes of work practices, either
positive or negative, are also representative of Lessons Learned. The
value of an innovative approach or a path that did not produce the
desired effect are useful Lessons Learned. Lessons are learned during
the course of, and at the completion of, planned activities. Lessons
Learned include stories about insights and experience of interest and
value to others, examples of novel and innovative developments as well
as suggestions on how processes can be improved.

Lessons Learned are a method used to answer typical questions asked by
projects and individuals that include:

-   What are the standard/best practices for a particular function?

-   How did another project do this?

-   What is an example of a success in this area?

-   What difficulties were encountered and how were they resolved?

-   Has this problem been seen before?

-   Who has experience in dealing with this area?

-   What information resources exist?

-   How can this be communicated to others?

**Applicable Lessons Learned** -- Lessons are considered to be
applicable if all of the following criteria are met:

1.  Relevancy; a) significant bearing within NASA, and b) useful for
    applications outside of NASA,

2.  Understandable by someone; a) not intimately familiar with the
    Project or functional area, and b) with reasonable skill,

3.  Beneficial; a) recognizable impact within NASA, b) reasonable
    possibility that someone else could face a similar situation, c)
    provides an opportunity for saving effort, time or money, or d)
    allows improvements in performance, safety, reliability or
    probability of mission success,

4.  Validity; a) factually and logically correct, b) consistent with
    laws, regulations and policies, c) well-grounded or justifiable,
    and d) expectation that a similar outcome either will (for a
    positive lesson), or will not (for a negative lesson) be repeated,

5.  Realizable; a) capable of being implemented, and b) offers a
    practical, not hypothetical solution,

6.  Consistent; a) lesson fits within categories, b) an independent
    check of the lesson is possible, c) root cause analysis can be
    applied, and d) applicability, priority and target for
    implementation can be identified

Lessons Learned can be identified, captured, shared, applied and
evaluated for impact at five functional levels within the Project
organization. Exhibit 2-2 illustrates those hierarchical levels and
their associated scope. The table provides guidance to the element
managers who are responsible for defining the assembly level
responsibilities within their organization. Team members at each level
are responsible for assessing Lesson Learned impact as they apply to
that person's realm of control within the hierarchy.

  -------------- ----------------------------------------------------------
  **Level**      **Impact Scope**

  Mission        Lessons Learned that impact overall Project success

  Element        Lessons Learned that impact ability of a particular
                 element to achieve its operational or scientific
                 objectives

  Subsystem      Lessons Learned that impact performance of a subsystem

  Component      Lessons Learned that impact the functional effectiveness
                 of a particular component. Examples include the spacecraft
                 Box level or software program level

  Subcomponent   Lessons Learned that impact function or performance of a
                 particular subcomponent. Example includes the spacecraft
                 card level or software module level.
  -------------- ----------------------------------------------------------

Exhibit 2‑2. Functional Levels

**Best Practice** -- Those activities, based on experience, considered
to provide desirable outcomes for a particular process. {[These best
practices are typically identified by performing organizations and are
organized, reviewed and disseminated by the Systems Management
Office.]{.mark}}

## Lessons Learned Process 

The Continuous Lessons Learned Process set forth in this document is
illustrated in Exhibit 1-1 and consists of eight steps:

-   Identification

-   Capture

-   Organization

-   Analysis

-   Targeting

-   Dissemination

-   Application

-   Feedback

**Identification of Lessons Learned** -- Determining that an event,
experience, or outcome is of sufficient and appropriate interest and
value to; a) the current Project, b) future Projects, c) other
individuals, and d) the NASA organization, that it should be captured
and made available for others to benefit from the insight and knowledge
gained, to ensure that positive results can be repeated and that
negative results will not be repeated.

**Capture of Lessons Learned** - The process for gathering Lessons
Learned from individuals, groups and Projects. Lessons Learned exist in
the knowledge that people have and in documents, these only have value
to others if these sources of insight and experience are captured,
organized and made available.

**Organization of Lessons Learned** - The categorization, ranking and
assessment of validity for a Lesson Learned that has been submitted.
These efforts will be performed by; a) each Project's LLC as part of an
initial screening, and b) the Program Office's LLC to ensure
consistency.

**Analysis of Lessons Learned** - Review of an activity, event,
condition, result or occurrence to determine the essential common basis,
underlying reason(s) or systemic elements that gave rise to this
condition. The purpose of root cause analysis is to identify the
contributing systemic factors, train of events, and common threads so
that; a) a recurrence of negative outcomes can be prevented in the
future, and b) best practices for positive outcomes can be identified.

**Targeting of Lessons Learned** - Determination of what Program
Offices, Projects, individuals and areas within the NASA organization
with particular needs, interests, functional responsibilities or
specializations can benefit from a particular lesson.

**Dissemination of Lessons Learned** -- Making lessons, and/or summaries
of lessons available to Programs, Projects and individuals that have the
opportunity to apply them. Dissemination of Lessons Learned includes
both providing convenient access to resources of direct and indirect
interest and forwarding alerts/updates to individuals willing to receive
such information without having to search for it. Techniques that
support dissemination of Lessons Learned include; NASA LLIS Web site,
NASA Technical Standards Web Site, EOS Pilot for Lessons Learned Web
Site/Community of Practice Portal, email distribution of alerts/updates,
Webcasts, meetings, teleconferences, workshops, working groups, employee
exchange, training, mentoring, conferences.

**Application of Lessons Learned** -- The use of prior Lessons Learned
to provide benefit for Projects, individuals, and the NASA organization
either in terms of repeating positive outcomes or by avoiding negative
consequences.

**Feedback on Lessons Learned** -- Programs, Projects and individuals
that receive lessons will provide periodic reports on the application
and value of Lessons Learned within their areas of responsibility.
Suggestions will also be provided regarding improvements to the process
for sharing Lessons Learned.

As lessons are analyzed and addressed throughout the Lessons Learned
Process, they follow the various stages per Exhibit 2-3. The Lessons
Learned status is intended to facilitate the review and reporting of
Lessons Learned.

+------------+---------------------------------------------------------+
| **Lesson   | **Activities Performed During This Phase**              |
| Learned    |                                                         |
| Phase**    |                                                         |
+------------+---------------------------------------------------------+
| **In       | -   Identify and capture new lessons                    |
| itiation** |                                                         |
+------------+---------------------------------------------------------+
| **Orga     | -   Categorize, rank and assess the validity for each   |
| nization** |     lesson                                              |
+------------+---------------------------------------------------------+
| **Ev       | -   Perform root cause analysis to determine common     |
| aluation** |     threads and underlying systemic factors             |
|            |                                                         |
|            | -   Assign a priority to each lesson                    |
|            |                                                         |
|            | -   Identify where each Lesson Learned can be applied   |
+------------+---------------------------------------------------------+
| **Disse    | -   Determine how, when and to whom each lesson should  |
| mination** |     be distributed                                      |
|            |                                                         |
|            | -   Forward lessons and confirm that the right lessons  |
|            |     get to the right people on the appropriate Projects |
|            |     when they are needed                                |
+------------+---------------------------------------------------------+
| **App      | -   Identify those lessons that are applicable and      |
| lication** |     appropriate for the Project                         |
|            |                                                         |
|            | -   Assign a responsible Project representative to      |
|            |     address each lesson                                 |
|            |                                                         |
|            | -   Assess the value of lessons relevant to the Project |
+------------+---------------------------------------------------------+

Exhibit 2‑3. Lessons Learned Phase

The Project's Lessons Learned activities fit within the context of
efforts being performed by the; Earth Science Program Office, Flight
Programs and Projects Directorate and Goddard Space Flight Center
Knowledge Management initiatives. Exhibit 2‑4 indicates the overall
scope of Lessons Learned activities within GSFC.

![](media/image3.wmf){width="7.20748031496063in"
height="5.47007874015748in"}

Exhibit 2‑5. Overall GSFC Lessons Learned Process

## Roles and Responsibilities

Program Lessons Learned is a responsibility shared by the PM, LLC, and
Project Staff. Specific roles and responsibilities are explained in
Exhibit 2-6.

+---------------+------------------------------------------------------+
| **Role**      | **Responsibility**                                   |
+---------------+------------------------------------------------------+
| Formul        | -   Responsible for overall Project Lessons Learned  |
| ation/Project |     activities                                       |
| Manager       |                                                      |
|               | -   Ultimate project authority for identification,   |
|               |     capture, application and evaluation of Lessons   |
|               |     Learned                                          |
|               |                                                      |
|               | -   Assigns roles and responsibilities for project   |
|               |     Lessons Learned efforts                          |
|               |                                                      |
|               | -   Assists in and performs identification and       |
|               |     capture for mission level Lessons Learned        |
|               |     especially those associated with programmatic,   |
|               |     schedule, and cost aspects                       |
|               |                                                      |
|               | -   Provides guidelines for evaluation of Lessons    |
|               |     Learned applied on the project                   |
+---------------+------------------------------------------------------+
| Mission       | -   Responsible for all technical mission level      |
| Systems       |     Lessons Learned                                  |
| Engineer      |                                                      |
|               | -   Reviews Lessons Learned brought forth from the   |
|               |     Element SEs                                      |
|               |                                                      |
|               | -   Assists in and performs identification, capture  |
|               |     and application for mission level Lessons        |
|               |     Learned especially technical/performance and     |
|               |     safety--related items                            |
+---------------+------------------------------------------------------+
| Lessons       | -   Responsible for ensuring that all assembly       |
| Learned       |     levels are following the Lessons Learned process |
| Coordinator   |                                                      |
| (function may | -   Regularly reports any Lessons Learned issues to  |
| be shared     |     the Mission SE/PM and to the Program Office LLC  |
| and/or        |                                                      |
| combined with | -   Facilitates the development and implementation   |
| Configuration |     of plans and activities for the identification,  |
| Ma            |     capture, and application of Lessons Learned      |
| nagement/Risk |                                                      |
| Management)   | -   Performs or assists team in evaluation of        |
|               |     Lessons Learned                                  |
|               |                                                      |
|               | -   Communicates Lessons Learned-related aspects of  |
|               |     interest to the Project staff such as training,  |
|               |     workshops, mentoring, mini-courses, Webcasts,    |
|               |     in-reach, awards, tools and resources            |
|               |                                                      |
|               | -   Determines the impact of activities and resource |
|               |     requirements associated with the Lessons Learned |
|               |     process                                          |
+---------------+------------------------------------------------------+
| Support Staff | -   Responsible for ensuring that the subsystem,     |
|               |     component, and sub-component assembly levels are |
|               |     following the Lessons Learned Process            |
|               |                                                      |
|               | -   Define Lessons Learned responsibilities and      |
|               |     impact definitions within their element          |
|               |                                                      |
|               | -   Review and/or apply lessons escalated from the   |
|               |     subsystem level                                  |
|               |                                                      |
|               | -   Responsible for identifying, capturing and       |
|               |     applying element level Lessons Learned for their |
|               |     respective element                               |
|               |                                                      |
|               | -   Escalate lessons, as necessary, to the Project   |
|               |     SE and/or PM                                     |
+---------------+------------------------------------------------------+
| Project Staff | -   Responsible for identifying, capturing and       |
|               |     applying lessons at their respective levels      |
|               |                                                      |
|               | -   Ensure that appropriate lessons are escalated to |
|               |     the appropriate assembly levels                  |
+---------------+------------------------------------------------------+
| Customers and | -   Recommend/Identify new lessons to be captured    |
| Suppliers     |     and applied                                      |
|               |                                                      |
|               | -   Provide input and insight into the identified    |
|               |     lessons as pertaining to their involvement with  |
|               |     Project activities or external organizations     |
|               |                                                      |
|               | -   Lessons Learned requirements may be levied on    |
|               |     suppliers on a case-by-case basis based on scope |
|               |     of work and level of involvement with the        |
|               |     project                                          |
+---------------+------------------------------------------------------+
| External      | -   Invited to attend the Project Lessons Learned    |
| Reviewers and |     reviews                                          |
| Assessors     |                                                      |
|               | -   Provide input and insight into the identified    |
|               |     lessons being reviewed                           |
|               |                                                      |
|               | -   Recommend/Identify new lessons to be captured    |
|               |     and applied                                      |
+---------------+------------------------------------------------------+

Exhibit 2‑6. Lessons Learned Roles and Responsibilities

## Allocation of Lessons Learned Resources

Resources for Lessons Learned activities will be included in the Project
budget. The Project will also maintains a contingency budget to
accommodate special circumstance that may arise, including additional
effort to support identification, capture, sharing, application and
evaluation of Lessons Learned if needed. Each element manager is
responsible for managing the Lessons Learned budget for their respective
elements. Any requests for additional resources must be made to the PM.
The Manager(s) responsible for any given Lesson Learned will need to
make Lessons Learned resource decisions on a case-by-case basis.

# Lessons Learned Identification

The first step in the Lessons Learned Process, as outlined in Section
[2.2]{.mark}, is to identify Lessons Learned. An environment of
continuous Lessons Learned identification will take place during each
project phase to support capture, sharing and application of lessons
during Formulation, Implementation and Operations.

Identification of relevant lessons can be initiated in several ways.
Lessons Learned from experiences on current and previous projects can
provide valuable insights for identifying potential new lessons.

The following is a list of resources that may assist in the
identification of lessons:

-   Weekly Activity Reports, Design Reviews, Workshops, Working Group
    meetings,

-   Project and Element Team Meetings,

-   Internal/External Reviews,

-   Trade studies, design, analysis, manufacturing, integration and test
    results,

-   Project staff, functional staff, management

All Project staff members participate in the Lessons Learned Process and
are encouraged to submit a Lessons Learned for any lessons that are
identified. [{All staff members should be trained in NASA Continuous
Lessons Learned (CLL), which is taught by the Systems Management Office,
NASA Goddard Space Flight Center.}]{.mark} This training will assist in
educating the Project staff to understand why lessons need to be shared
and how to properly identify, capture, share and apply Lessons Learned.

# Lessons Learned Capture

The process for gathering Lessons Learned is from individuals or groups,
including; results of meetings, reviews and activities as well as
extraction of lessons from Project-related documents. All Project staff
should prepare a weekly activity report, all Project meetings should
result in the generation of meeting minutes, after every Project review
there should be a meeting summary provided, and all contractors shall
deliver a Lessons Learned report as a CDRL requirement. These documents
represent sources of insights and experience containing Lessons Learned.

Specific lessons to capture and share include: a) results from;
problems, failures, incidents, anomalies and risks, b) issues, needs,
results, and trends, c) best practices and pitfalls to avoid, d)
design/decision processes and rationale. Lessons may be gleaned from
numerous existing resources such as; a) weekly activity reports and
monthly status reviews, b) independent review team reports, c) top-ten
lists, d) requests for actions and associated closure reports, e) award
fee letters, f) Quarterly Executive Dialogues, g) after-action reviews,
h) final reports, and i) case studies.

Individuals shall submit Lessons Learned, as relevant items are
identified, by filling out the form in Appendix A and providing this to
the Project LLC. The Project LLC shall inform the PM and Program Office
Lessons Learned Coordinator on a weekly basis of those lessons that have
been submitted.

Team review techniques for capturing Lessons Learned at key points
during the Project life cycle include:

1.  **After Action/Incident Reviews** (AAR/AIR): A short review (less
    than 2 hours) covering:

    a.  What was supposed to happen?

    b.  What actually happened?

    c.  Why were there differences?

    d.  What can you or others learn from this experience?

> After Action/Incident Reviews shall be conducted after the following
> events; Project kickoff, study completion, budget submission,
> Technical Interchange Meetings (TIMs), Workshops, unit, subsystem and
> system-level tests, Request for Proposal release, proposal evaluation,
> contract kickoff, contract closeout, post-launch, and on-orbit
> anomalies.

2.  **Significant Milestone Review** (SMR): A review (less than 4 hours)
    covering:

    a.  What went well or not?

    b.  Why did it succeed or not?

    c.  If you were to start again, what would you do differently?

    d.  What did you learn that is specific to this Project?

    e.  What could others learn from your experience?

> Significant Milestone Reviews shall be conducted after the following
> events; Mission Confirmation Review, Internal/External Independent
> Reviews, Mission Definition Review, Initial Confirmation Review,
> System Requirements Review, System Concept Review, Preliminary Design
> Review, Mission Confirmation Review, Critical Design Review, Mission
> Operations Review, Pre-environmental Review, Flight Operations Review,
> Pre-Ship Review, Operations Readiness Review, Mission Readiness
> Review, Flight Readiness Review, Launch Readiness Review, and
> Decommissioning Review.

3.  **Post Project Review** (PPR): A team review (less than 8 hours)
    covering:

    a.  What were the key objectives of the Project and how well were
        these achieved?

    b.  What lessons were learned during the course of the Project?

    c.  What lessons are the most important?

    d.  How should future efforts be modified based on these Lessons
        Learned?

> Post Project Reviews shall take place; after launch and early-orbit
> checkout, and after decommissioning.

# Lessons Learned Dissemination

After Lessons Learned have gone through the organization and analysis
phases, they will be targeted to specific Projects, individuals and NASA
organizations with the interest and need to benefit from these
experiences. Several methods of dissemination will be applied to Lessons
Learned. For those Projects, individuals and NASA organizations with
identified interests and needs, Lessons Learned will be disseminated by
email notification of alerts and updates. Additional techniques that
support dissemination of Lessons Learned include; NASA LLIS Web site,
NASA Technical Standards Web Site, EOS Pilot for Lessons Learned Web
Site/Community of Practice Portal, Webcasts, newletters, Lessons Learned
summaries/reports, workshops, working groups, employee exchange,
training, mentoring, and conferences.

# Lessons Learned Application

## Lessons Learned Impact Assessment

### Impact Categories

To help assess the impact of a lesson, several Impact Categories have
been identified. Exhibit 6-7 lists the Impact Categories and example
indicators. The indicators are meant to provide guidance in assessing
the Lesson Learned impact for each category.

+--------------------+-------------------------------------------------+
| > **Impact         | **Example Indicators**                          |
| > Category**       |                                                 |
+--------------------+-------------------------------------------------+
| > **Techn          | > Mass                                          |
| ical/Performance** |                                                 |
+--------------------+-------------------------------------------------+
|                    | > Physical Dimensions                           |
+--------------------+-------------------------------------------------+
|                    | > Memory Utilization                            |
+--------------------+-------------------------------------------------+
|                    | > Power Requirements                            |
+--------------------+-------------------------------------------------+
|                    | > Design Maturity                               |
+--------------------+-------------------------------------------------+
|                    | > Failure Rate Does Not Support Design Life     |
+--------------------+-------------------------------------------------+
|                    | > Design Complexity                             |
+--------------------+-------------------------------------------------+
|                    | > Environmental Conditions                      |
+--------------------+-------------------------------------------------+
| > **Programmatic** | > Technical event that is not Project           |
|                    | > Responsibility                                |
+--------------------+-------------------------------------------------+
|                    | > Schedule event that is not Project            |
|                    | > Responsibility                                |
+--------------------+-------------------------------------------------+
|                    | > Cost event that is not Project Responsibility |
+--------------------+-------------------------------------------------+
|                    | > Level 1 Requirements Drivers                  |
+--------------------+-------------------------------------------------+
|                    | > NASA Constraints                              |
+--------------------+-------------------------------------------------+
|                    | > Partner Contributions/Shortfalls              |
+--------------------+-------------------------------------------------+
|                    | > Budget Restrictions from HQ                   |
+--------------------+-------------------------------------------------+
|                    | > Resource Adequacy/Availability                |
+--------------------+-------------------------------------------------+
| > **Schedule**     | > Component Availability                        |
+--------------------+-------------------------------------------------+
|                    | > Launch Windows                                |
+--------------------+-------------------------------------------------+
|                    | > Instrument Delivery Schedules                 |
+--------------------+-------------------------------------------------+
|                    | > Development Schedule                          |
+--------------------+-------------------------------------------------+
| > **Cost**         | > Actual Cost Beyond Budget Allocation          |
+--------------------+-------------------------------------------------+
|                    | > Replacement Impacts due to Cost (e.g.,        |
|                    | > alternate LV)                                 |
+--------------------+-------------------------------------------------+
|                    | > Independent Cost Estimate Inputs              |
+--------------------+-------------------------------------------------+
| > **Safety**       | > Personnel Related Safety (e.g., electrical    |
|                    | > shock)                                        |
+--------------------+-------------------------------------------------+
|                    | > Environmental considerations (e.g., the use   |
|                    | > of such materials as beryllium, volatile      |
|                    | > fuels, or water contaminates)                 |
+--------------------+-------------------------------------------------+

Exhibit 6‑7. Impact Categories and Indicators

### Impact Definitions

An impact rating is determined for each Impact Category based on the
predefined impact definitions. Impact definitions are specific to each
assembly level. Exhibit 6-8 provides the impact definitions for the
mission level, which have been assigned by the Project Office. Exhibit
6-3 provides impact definitions for the mission elements. Impact
definitions for assembly Levels below the element level are also the
responsibility of the element SEs. The element SEs utilize their team's
expertise at each assembly level to provide the appropriate impact
definitions. The LLC will provide guidance to the element SEs to ensure
that the definitions are documented and are consistent with the Lessons
Learned approach.

  ---------- --------------- ------------------ --------------- ------------ ---------------
  **Impact   **Technical /   **Programmatic**   **Schedule**    **Cost**     **Safety**
  Rating**   Performance**                                                   

  A          Minimal         Requires Element   Minimal or none Minimal or   Meets Safety
             Performance     Manager Decision                   none         Requirements
             Margin                                                          
             Reduction;                                                      
             Exceeds Level 1                                                 
             Req.                                                            

  B          Some            Requires           Additional      \< 5% of     Negligible, No
             Performance     Formulation/       resources       affected     Adverse Affect
             Margin          Project Manager    required to     Element      to Personal
             reduction;      Notification       meet need date               Safety or
             Exceeds Level 1                                                 Health
             Req.                                                            

  C          Significant     Requires           Minor slip in   5 to 7% of   Moderate, May
             Performance     Formulation/       need date       affected     Cause Minor
             Margin          Project Manager                    Element      Injury or
             Reduction; One  Decision                                        Occupational
             or More Level 1                                                 Illness
             Req. Barely Met                                                 

  D          Fails to meet a Requires EOS       Major slip in   7 to 10% of  Critical, May
             Level 2 Req.,   Program Office &   key milestone   affected     Cause Severe
             Level 1 Req.    GSFC PMC Decision                  Element      Injury or
             Met                                                             Occupational
                                                                             Illness

  E          Fails to Meet a Requires NASA      Unrecoverable   \>10% of     Catastrophic,
             Level 1 Req.    Associate          project delay   affected     May Cause Death
                             Administrator                      Element      or Permanently
                             Decision                                        Disabling
                                                                             Injury
  ---------- --------------- ------------------ --------------- ------------ ---------------

Note: These definitions are for the establishment of impact level only
and do not preclude or redefine standard reporting/reviews of cost,
schedule, performance, or safety status and issues.

Exhibit 6‑8. Mission Level Impact Definitions

  ---------- --------------- ------------------ --------------- ------------ ---------------
  **Impact   **Technical /   **Programmatic**   **Schedule**    **Cost**     **Safety**
  Rating**   Performance**                                                   

  A          Minimal         Requires Subsystem Minimal or none Minimal or   Meets Safety
             Performance     Manager Decision                   none         Requirements
             Margin                                                          
             Reduction;                                                      
             Exceeds Level 2                                                 
             Req.                                                            

  B          Some            Requires Element   Additional      \< 5% of     Negligible, No
             Performance.    Manager            resources       affected     Adverse Affect
             Margin          Notification       required to     subsystem    to Personal
             reduction;                         meet need date               Safety or
             Exceeds Level 2                                                 Health
             Req.                                                            

  C          Significant     Requires           Minor slip in   5 to 7%      Moderate, May
             Performance     Formulation/       need date       subsystem    Cause Minor
             Margin          Element Manager                                 Injury or
             Reduction; One  Decision                                        Occupational
             or More Level 2                                                 Illness
             Req. Barely Met                                                 

  D          Fails to meet a Requires           Major slip in   7 to 10%     Critical, May
             Level 3 Req.,   Formulation/       key milestone   subsystem    Cause Severe
             Level 2 Req.    Project Manager                                 Injury or
             Met             Decision                                        Occupational
                                                                             Illness

  E          Fails to Meet a Requires           Unrecoverable   \>10%        Catastrophic,
             Level 2 Req.    Formulation/       project delay   subsystem    May Cause Death
                             Project Manager                                 or Permanently
                             Decision                                        Disabling
                                                                             Injury
  ---------- --------------- ------------------ --------------- ------------ ---------------

Note: These definitions are for the establishment of impact level only
and do not preclude or redefine standard reporting/reviews of cost,
schedule, performance, or safety status and issues.

Exhibit 6‑3. Mission Element Impact Definitions

### Estimation of Value

The {[Project/Program Office/SMO TBR]{.mark}} will develop estimates of
the performance, schedule and cost benefits associated with applying
Lessons Learned. The impact of applying Lessons Learned will also be
assessed with regard to; mission success, safety, reliability, value to
stakeholders/customers, and furtherance of Center/Agency objectives.
Staff is encouraged to indicate their view of Lessons Learned with
respect to; improving the quality of their workplace experience,
professional development benefit, and other aspects of personal priority
to them.

#  Lessons Learned Documentation and Communication

Lesson Learned documentation and communication are key elements in
Project Lessons Learned. All Lessons Learned are documented and tracked
within the Lessons Learned database. The LLC is responsible for ensuring
that all appropriate communication related to Lessons Learned and
problems takes place.

## Lesson Learned Reports and Reporting Milestones

Regular Lesson Learned reports are produced from the Lesson Learned
database and distributed appropriately to the Project team. These
reports include but are not limited to:

-   Mission Level Primary Lesson Learned list

-   Element Level Primary Lesson Learned lists

-   List of all Project Lessons Learned sorted by assembly level or
    element

-   Accepted Lessons Learned list

-   New Lessons Learned from external sources

-   Historical Lessons Learned from external sources that may be
    applicable to current Project activities

Weekly staff meetings are used for internal reporting where Lesson
Learned will be a regular agenda item. These weekly meetings are used as
a forum to report Lessons Learned to Project Management and to assess
the effectiveness of the Lessons Learned Process. The Senior Staff
meeting reviews the Lesson Learned list at the mission level. Element
staff meetings cover Lessons Learned at the element level and lower. As
required, subsystem Lesson Learned meetings cover subsystem and lower
level Lessons Learned. Periodic Project Lesson Learned meetings will be
coordinated with GSFC and NASA HQ organizational entities to review and
communicate Project Lessons Learned and status. Summary reports of
Lesson Learned activity are generated monthly. The LLC will facilitate
generation of the appropriate Lesson Learned materials for various
meetings where discussion of Lesson Learned is featured.

Status with regard to identification, capturing, sharing and application
of Lessons Learned shall be addressed during the following:

-   Monthly Status and significant milestone reviews as indicated in
    Section 4,

-   Design reviews,

-   Internal/External Independent reviews, and

-   Internal/External Project management meetings.

## Lesson Learned Awareness and Education

The Project is dedicated to the swift identification, capture, sharing,
and application of Lessons Learned. All Project staff members are
encouraged to participate in the identification, capture and application
of Lessons Learned and will be trained in Continuous Lessons Learned
processes, consistent with the Continuous Lessons Learned Practices
defined by the Systems Management Office at NASA GSFC. Project staff
members are immediately notified of updates or changes to the Lessons
Learned process or procedures. Weekly staff meetings utilized for Lesson
Learned discussion and review provide the opportunity for continuous
improvement of the Project Lessons Learned Process. The LLC will track
and document all changes instituted by the team and make recommendations
for improvement where possible. These modifications will be communicated
to the Project team as necessary. Additionally, the LLC will review and,
if needed, update the Lessons Learned Plan as required.

## Recourse

If any member of the Project team feels that a Lesson Learned has been
improperly handled or addressed, that team member may address those
concerns with the LLC, PM, SE, or the Project Safety Assurance Manager
(SAM). The concerns can be brought to the LLC who provides assistance in
identifying how the Lesson Learned was improperly handled and any
recourse or action that needs to be taken. The LLC documents the
concerns and addresses them with the PM and SE as appropriate. Status
and resolution of the concerns are then reported back to the original
team member. The Project SAM is an independent alternate resource in the
event the Lesson Learned Identifier feels insufficient action may have
been taken to address the concerns. Based on the SAM's opinion, he may
choose to facilitate resolution with the PM or elevate the issue to GSFC
Management. The Project PM and SE also maintain an 'open door' policy to
any team member desiring reconsideration of specific Lessons Learned or
resolution of their concerns.

# Appendix A -- Lessons Learned Input Form {#appendix-a-lessons-learned-input-form .unnumbered}

  ------------------ ------------- ----------------- ------------- ---------------------- -------------
  LESSON LEARNED                                                   FILE NO.               Page of

                                                                   CATEGORY               
                                                                   (Primary/Alternate):   

  TITLE/SUBJECT:                                                   KEYWORDS:              

  EVENT DESCRIPTION:                                                                      

  LESSON LEARNED:                                                                         

  RECOMMENDATIONS:                                                                        

  ATTACHMENTS:                                       REFERENCES:                          

  SUBMITTED BY:      /OFFICE:      ORG./COMPANY:                   LOCATION:              DATE OF
                                                                                          OCCURRENCE:

  TELEPHONE:         EMAIL:        SPECIALIZATION:                 BUILDING/ROOM:         DATE
                                                                                          SUBMITTED:
  ------------------ ------------- ----------------- ------------- ---------------------- -------------

# Appendix B -- Description of Lessons Learned Submission Form Items {#appendix-b-description-of-lessons-learned-submission-form-items .unnumbered}

  --------------------------------------------------------------------------------------------------- ----------------------------------------------
  **To be provided by Submitter**                                                                     **Comments**

  Category (Primary/Alternate)\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\--\>                             Identify functional areas where the lesson
                                                                                                      falls within (see Appendix C)

  Title/Subject                                                                                       Provide a short, specific and complete
                                                                                                      reference

  Keywords                                                                                            Use terms that describe concepts to facilitate
                                                                                                      retrieval via search

  Event Description                                                                                   Summarize key events and facts, avoid
                                                                                                      attribution to individuals or organizations

  Lesson Learned                                                                                      Brief primary theme along with applicability

  Recommendations                                                                                     Specific future actions for improvement

  Attachments                                                                                         Supporting documentation associated with the
                                                                                                      lesson

  References                                                                                          Relevant documentation and/or individuals
                                                                                                      (with contact information)

  Submitted by                                                                                        Individual who prepared the lesson learned

  Project/Office                                                                                      Project or organizational activity that the
                                                                                                      originator is associated with

  Organization/Company                                                                                NASA organization code or contractor where the
                                                                                                      originator is employed

  Location                                                                                            Site where the submitter is located

  Date of Occurrence                                                                                  Date when the event occurred

  Telephone                                                                                           Office telephone of the submitter

  Email                                                                                               Office email address of the submitter

  Specialization\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\--\>   Expertise of the submitter (see Appendix D)

  Building/Room                                                                                       Office location of the submitter

  Date submitted                                                                                      Date of the lesson submission
  --------------------------------------------------------------------------------------------------- ----------------------------------------------

# Appendix C -- Categories for Lessons Learned Submission Form {#appendix-c-categories-for-lessons-learned-submission-form .unnumbered}

  ------------------ ----------------------- ----------------------- ------------------------------ -------------------- ---------------------------------
  **Management**                             **System Engineering**                                 **Access to Space**  

                     Agreements                                      Allocations                                         Launch Facilities

                     Business                                        Configuration Management                            Launch Processing

                     Contracts                                       Contamination Control                               Launch Services

                     External Relations                              Environmental Protection                            Launch Systems

                     Finance                                         Environments                                        Range Support

                     Lessons Learned                                 IRDs/ICDs/IIDs                                      

                     Meetings and Reviews                            Requirements                   **Operations**       

                     Organization-Staffing                           Review Boards                                       Algorithms

                     Procurement                                     Studies & Analyses                                  Anomalies, Incidents, Failures

                     Resources                                       Verification                                        Command

                     Schedule                                        WBS                                                 Data Acquisition

                                                                                                                         Data Dissemination

  **Mission**                                **Engineering                                                               Data Management
                                             (Hardware/Software)**                                                       

                     Space segment                                   Analyses                                            Data Processing

                     Instruments                                     Design                                              Data Products

                     Observatory                                     Development                                         Data Storage and Retrieval

                     Spacecraft                                      Integration                                         Flight Software

                     Launch segment                                  Manufacturing/Coding                                Ground Software

                     Flight Support                                  Materials                                           Mission Engineering
                     Equipment                                                                                           

                     Ground Support                                  Parts                                               Mission Planning
                     Equipment                                                                                           

                     Launch Vehicle                                  Processes                                           Operations Concepts

                     Ground segment                                  Specifications                                      Telecommunications & Networking

                     Communications                                  Test                                                Telemetry

                     Mission Data Processing                         Test Support Equipment                              

                     TTC&M                   **Engineering                                          **Administrative**   
                                             Specialization**                                                            

                                                                     Mechanical/Structural Systems  ** **                Action Items

  **Science**                                                        Electromechanical/Mechanisms                        Contacts

                     Assessment                                      Electrical Systems                                  Correspondence

                     Calibration                                     Power Systems                                       Education

                     Data Assimilation                               RF/Microwave Communications                         Facilities

                     Measurements                                    Guidance, Navigation, and                           Human Resources
                                                                     Control Systems                                     

                     Models                                          Optical Systems                                     ITAR

                     Research                                        Electro-optics/Lasers                               Library/Technical Information
                                                                                                                         Services

                     Science Working Group                           Microwave Systems                                   Logistics/Transportation/Supply

                     Validation                                      Detector Systems                                    MIS/IT

  **Science                                                          Cryogenics                                          Outreach
  Specialization**                                                                                                       

                     Atmospheric Science                             Software                                            Presentations (Internal/External)

                     Geophysical/Geologic                                                                                Project Support
                     Science                                                                                             

                     Oceanographic Science   **Mission Assurance**                                                       Public Affairs

                     Biospheric/Biologic                             Independent Reviews &                               Reports (Weekly/Monthly)
                     Science                                         Investigations                                      

                     Hydrologic Science                              Product Assurance                                   Scheduling

                                                                     Problem Reporting                                   Security

  **Technology**                                                     Quality Assurance                                   Training

                     Apertures                                       Reliability                                         Travel

                     Bus Subsystems                                  Risk Management                                     Workshops

                     Components                                      Safety                                              

                     Data Distribution                               Software Assurance                                  

                     Data Integration                                                                                    

                     Data Stream Processing                                                                              

                     Detectors                                                                                           

                     Instrument Technology                                                                               

                     Sensors                                                                                             
  ------------------ ----------------------- ----------------------- ------------------------------ -------------------- ---------------------------------

# Appendix D -- Specializations for Lessons Learned Submission Form {#appendix-d-specializations-for-lessons-learned-submission-form .unnumbered}

  ------------------------------------- ---------------------------------
  Project/Program/Instrument Management Cryogenics
  (PM, DPM, DPMR\'s)                    

  Reliability Engineering               Materials

  Mission Assurance                     Contamination
  Management/Engineering                

  Flight/Ground Systems Safety          Industrial Safety
  Engineering                           

  Systems Engineering                   Environmental
                                        Protection/Engineering

  Software Engineering Methods,         Facilities Engineering,
  Standards, Processes, and Reliability Maintenance, and Operations

  Flight/Ground Engineering Data        Applied Math/Computational
  Systems - Software                    Science and Analysis

  Flight/Ground Data Systems - Hardware Atmospheric Science

  Administrative Computing              Geophysical/Geologic Science

  Mission Operations Engineering        Oceanographic Science

  Telecommunications and Networking     Biospheric/Biologic Science

  Mechanical/Structural Systems         Hydrologic Science
  Development, Integration, and Test    

  Electromechanical/Mechanism           General Business/Administrative

  Electrical Systems Development,       Financial/Resources
  Integration, and Test                 Management/Program Analysis

  Power Systems Development,            Logistics/Supply/Transportation
  Integration and Test                  

  RF/Microwave Communications           Technical Information
                                        Services/Library Science

  Radiation Effects and Component       Security
  Technologies                          

  Guidance, Navigation, and Control     Procurement
  Systems Development, I&T              

  Optical Systems                       Public Affairs

  Electro-optics/Lasers                 Education

  Microwave Systems                     Secretarial/General Clerical

  Detector Systems                       
  ------------------------------------- ---------------------------------

# Appendix E -- Acronym List {#appendix-e-acronym-list .unnumbered}

AAR After Action Review

AIR After Incident Review

CDR Critical Design Review

ESPO Earth Science Program Office

GSFC Goddard Space Flight Center

HQ Headquarters

LLC Lessons Learned Coordination

NASA National Aeronautics and Space Administration

NPG NASA Procedures and Guidelines

PDR Preliminary Design Review

PM Project Manager

PMC Program Management Council

PPR Post-Project Review

PSR Project Status Review

SAM Safety Assurance Manager

SE System Engineer

SMR Significant Milestone Review

TBD To Be Determined

TBP To Be Provided

TBR To Be Resolved