--------------- --------- -------------------------------------------------------
  **Responsible             Code 400/Flight Programs and Projects Directorate
  Office:**                 

  **Title:**      Lessons   
                  Learned   
  --------------- --------- -------------------------------------------------------

###### **[Preface]{.smallcaps}**

1.  **PURPOSE**

    The objective of Lessons Learned is to; a) allow Programs and
    Projects to benefit from experiences gained on prior activities,
    and b) similarly offer insights for future Programs and Projects so
    that best practices can be shared/replicated and prevent problems
    from recurring. Lesson Learned is a process involving the;
    identification, capture, organization, analysis, targeting,
    dissemination, application, and feedback of experience/information
    developed to improve the effectiveness of Programs and Projects.
    This GPG provides procedures and guidelines for applying Lessons
    Learned to GSFC Projects as required by NPG 7120.5, "Program and
    Project Management Processes and Requirements" for the Capture
    Knowledge process.

2.  **APPLICABILITY**

The procedure for capturing and sharing lessons learned shall be applied
to all GSFC Programs and Projects. This procedure shall also be applied
to all deliverable instruments, spacecraft and other GSFC products
designated by the GSFC Center Director. This procedure applies to
Program and Project formulation, approval, implementation and evaluation
subprocesses, including mission operations.

3.  **AUTHORITY**

NPD 7120.4, Program/Project Management

4.  **REFERENCES**

```{=html}
<!-- -->
```
a.  NPG 7120.5, Program and Project Management Processes and
    Requirements.

b.  NPG 8735.1, Procedures for Exchanging PM&P Data Using GIDEP and NASA
    Advisories.

c.  NPG 8715.3, NASA Safety Manual.

d.  NPG 8621.1, NASA Procedures for Mishap Reporting, Investigating and
    Recordkeeping.

e.  NPG 8000.4 Risk Management Procedures and Guidelines.

f.  NASA Federal Acquisition Regulations (FAR) Supplement (NFS) Parts
    1807, 1815, 1823, and 1846.

g.  GPG 7120.1, Program and Project Management.

h.  GPG 7120.4, Risk Management.

i.  GPG 7120.5, Systems Engineering.

j.  GPG 8700.4, Integrated Independent Reviews.

k.  GPG 8700.6, Engineering Peer Reviews.

l.  GPG 1060.2, Management Review And Reporting for Programs and
    Projects.

m.  GPG 1710.1, Corrective and Preventive Action.

n.  GPG 8621.3, Mishap, Incident, and Close Call Investigation.

o.  400-PG-8621-0-1, Anomaly Reporting System for Flight Programs and
    Projects.

```{=html}
<!-- -->
```
5.  **CANCELLATION**

    None

6.  **SAFETY**

None

7.  **TRAINING**

The purpose of training is to make personnel aware of the value, process
and priority associated with sharing Lessons Learned within and among
Programs/Projects. Program/Project teams shall be trained in the process
for sharing Lessons Learned as defined in paragraph 2.4. Current and new
staff (both Government and Contractor) shall be provided with general
familiarization of the process for sharing Lessons Learned and how to
make use of resources and tools to facilitate these activities. Those
individuals with direct responsibilities for implementing the process
for sharing Lessons Learned will receive more detailed training on
specific techniques for how to; identify, capture, disseminate and apply
lessons.

8.  **RECORDS**

**\
**None

9.  **METRICS**

None

**\
P.10** **DEFINITIONS**

a.  [Lesson Learned]{.underline} -- A Lesson Learned is that knowledge
    gained by study or experience that becomes useful as an instructive
    example. Lessons that are learned result from activities where
    something different from an everyday event, or realization that an
    unexpected occurrence has taken place including; a mishap, accident
    or mistake. Outcomes of work practices, either positive or negative,
    successes or failures, 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 represent knowledge that is acquired and as such
    represents a valuable resource to be captured and shared with
    others.

Lessons Learned include stories about successes, failures, 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. Sources of lessons include; management and staff, retirees,
contractors and consultants, stakeholders and Customers.

Specific lessons to capture and share include; a) 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 Dialogs, g) after-action reviews, h) final reports,
and i) case studies.

b.  [Lessons Learned Process]{.underline} -- Figure 1 indicates the
    Lessons Learned process. This process shall be applied within each
    Program Office and Project to ensure that experience gained in the
    course of performing Pre-Formulation, Formulation, Implementation
    and Operations activities are captured and shared among Projects,
    throughout the Center and with Agency partners. Figure 2 presents a
    detailed flow of GSFC activities associated with the Lessons Learned
    process.[\
    ]{.underline}

**Figure 1. Lessons Learned Process**

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

[\
\
\
\
\
\
\
\
]{.underline}**Figure 2. Lessons Learned Activities**[\
\
]{.underline}

c.  [Best Practice]{.underline} -- 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}}[\
    ]{.underline}

d.  [Knowledge Management]{.underline} -- Those Center and Agency
    efforts associated with principles, policies, common tools and
    associated resources applied to address transfer of experience
    throughout the organization. Knowledge Management activities are
    focused on improving processes and institutional aspects within the
    NASA environment to facilitate sharing of explicit and tacit
    knowledge.[\
    \
    \
    \
    ]{.underline}

e.  [Applicable Lessons Learned]{.underline} -- Lessons are considered
    to be applicable if all of the following criteria are met:[\
    ]{.underline} 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.

f.  [Capturing Lessons Learned]{.underline} -- The process for gathering
    Lessons Learned from individuals, Projects and Program Offices.
    Lessons Learned exists 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.

g.  [Community of Practice]{.underline} -- An informal group with common
    professional interests/needs/goals such as; Projects in Formulation,
    Implementation and Operations. The structured environment for such a
    group to exchange information, identify individuals with relevant
    expertise/interests and provide the opportunity for collaboration.[\
    ]{.underline}

h.  [Review and Organization of Lessons Learned]{.underline} -- 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 Lessons Learned Coordinator as part of an
    initial screening, and b) the Program Office's Lessons Learned Lead
    to ensure consistency.

i.  [Root Cause Analysis]{.underline} -- A review of an activity, event,
    condition, result or occurrence to determine the essential common
    basis, underlying reason 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.

j.  [Applicability of Lessons Learned]{.underline} -- Determination of
    what Program Offices, Projects and those individuals with particular
    interests, functional responsibilities or specializations that can
    benefit from a particular lesson.

[\
\
]{.underline}

k.  [Action Plan for Lessons Learned]{.underline} -- Identifying the
    priority for distribution of lessons and what techniques should be
    applied to ensure that the appropriate lessons reach the Programs,
    Projects and individuals when they can best make use of these
    lessons. Priority descriptors for Lessons Learned include the
    following:

    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.  **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.

l.  [Dissemination of Lessons Learned]{.underline} -- Making lessons,
    and/or summaries of lessons available to the 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. Technique 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, meetings, teleconferences, workshops, working
    groups, employee exchange, training, mentoring, conferences.

m.  [Feedback of Lessons Learned]{.underline} -- 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.

n.  [Evaluation of Value]{.underline} -- {[Programs, Projects and/or SMO
    TBR]{.mark}} will develop estimates of the performance, schedule and
    cost benefits associated with implementing 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.

**[Procedures]{.smallcaps}**

1.  **Roles and Responsibilities**

```{=html}
<!-- -->
```
1.  The manager for each functional activity, Program Manager and
    Project Manager, shall have leadership responsibility for
    implementing a Lessons Learned process across the full scope of
    activities within their area of responsibility. That leader,
    hereafter referred to as the Program/Project Manager (PM), is
    ultimately responsible for identifying, capturing, sharing and
    applying Lessons Learned, providing feedback on the Lessons Learned
    process as well as reporting on results of Lessons Learned
    activities to higher level management. The PM defines and documents
    the Program/Project unique aspects of the Lessons Learned process
    and assigns responsibility to team members for implementation of
    Lessons Learned efforts. The PM is responsible for determining the
    value and benefit associated with applying Lessons Learned to
    Program/Project activities.

2.  The PM shall assign specific responsibilities for Lessons Learned
    implementation to Program/Project team members as the PM judges to
    be appropriate. Each major element and/or subsystem lead is expected
    to play a key role in the identification, capture and application of
    Lessons Learned specific to their area of responsibility and
    actively participate in system-level Lessons Learned activities. The
    PM may also assign individuals to conduct additional Lessons Learned
    activities that cross multiple areas.

3.  The implementation of Lessons Learned is organized within each
    Program Office to ensure continuity and consistency of Lessons
    Learned efforts across multiple Projects. Program Offices and
    Project Offices may be expected to utilize the expertise of
    individuals associated with System Engineering, Risk Management and
    Configuration Management to support the identification, capture,
    sharing and application of Lessons Learned.

4.  The implementation of infrastructure, tools, processes and
    procedures for Lessons Learned are part of the safety and mission
    assurance process, specifically known as Knowledge Management. The
    Systems Assurance Manager (SAM) and Systems Safety Manager assigned
    to the Project management team shall define, with PM approval, the
    safety and mission assurance requirements and manage the related
    surveillance activities necessary to effectively assess and support
    implementation of Lessons Learned processes for each Project.

5.  The GSFC Program Management Council (PMC) reviews the capture and
    application of Lessons Learned and verifies that resources are
    adequate as part of each PAPAC process defined within NPG 7120.5.
    The PMC reviews Lessons Learned as part of the monthly status,
    confirmation, and mission readiness review processes. See GPG 1060.2
    for further information on these PMC processes.

6.  The GSFC Flight Programs and Projects Directorate (FPPD) is
    responsible to the Center Director for Lessons Learned policy,
    procedures, guidelines and best practices. These Lessons Learned
    elements shall be consistent with the GSFC Systems Management Office
    (SMO) Knowledge Management policy, procedures, guidelines and best
    practices. The SMO also has the Agency-level responsibility for
    Knowledge Management training and provides Lessons Learned
    consultation to NASA Program/Project teams.

```{=html}
<!-- -->
```
2.  **Requirements**

```{=html}
<!-- -->
```
1.  GSFC Projects shall implement a systems management approach that
    formalizes and integrates the Lessons Learned process throughout the
    system life cycle. All elements of the system shall be addressed
    (e.g., flight, ground and launch vehicle segments, hardware and
    software, critical ground support equipment). All phases of the life
    cycle shall be considered (e.g., fabrication, assembly, integration
    and test, environmental testing, transportation, launch site
    processing, launch deployment, in-orbit check out, operations and
    decommissioning).\
    \
    This implementation shall include the use of tools and methodologies
    to support the identification, capture, and application of Lessons
    Learned in the system design and associated development and
    operations activities.

2.  GSFC projects shall incorporate the requirements of the Knowledge
    Management (KM) initiative as part of the Lessons Learned process.
    The purpose of KM is to convey NASA's focus on sharing knowledge
    among Projects and staff as a means to improve mission success
    throughout NASA.

3.  Project-specific implementation of the Lessons Learned process shall
    be documented for each project in a Lessons Learned Plan (LLP). The
    LLP shall be reviewed by the SAM, approved by the PM and concurred
    by the FPPD Director. The LLP shall be developed, approved and
    implemented early in Project formulation, no later than the mid
    point of the planned formulation period and prior to any mid
    formulation review gates imposed by the funding Enterprise (i.e.,
    Office of Space Science Interim Confirmation Review). The LLP is a
    controlled document and shall be maintained by the PM throughout the
    project life cycle and should be included in each Formulation Plan
    as well as subsequent Project Plans.

The LLP shall include:

a.  Introduction--- Specify the Project Lessons Learned objectives and
    policy toward Lessons Learned. Explain the purpose, scope,
    assumptions, constraints, key ground rules, and policy pertaining to
    the Project Lessons Learned process.

b.  Overview of process---Provide an overview of the Lessons Learned
    process and information flow; describe how the Lessons Learned
    process integrates and relates to other project management and
    system engineering activities. Include strategies for
    identification, capture, organization and application of Lessons
    Learned to be employed throughout Project life cycle.

c.  Organization---Show the organization, roles, and responsibilities of
    Program, Project, customer, and supplier key personnel with regard
    to Lessons Learned. Document how team members will be trained in the
    application of Lessons Learned methodology.

d.  Process details---Provide the Lessons Learned process details and
    related procedures, methods, tools, and metrics. Include here, or in
    an appendix, the specific methodologies to be used for
    identification, capture, organization, and application of Lessons
    Learned. Include the process to be used for continual assessment of
    the value of Lessons Learned applied to the Project. Describe how
    Lessons Learned information will be communicated both internally to
    the Project staff and throughout the NASA management chain.

e.  Documentation of Lessons Learned---Specify the format and data
    elements that will comprise the Project Lessons Learned List, how
    the list will be used and updated. Tell how team members will be
    able to access the current list at any time. Include in the LLP the
    initial set of identified Lessons Learned and the action plan for
    application of each Lesson Learned.

The FPPD website: <http://fpd.gsfc.nasa.gov/> contains Lessons Learned
background information, and other sample LLP's, information on Lessons
Learned techniques and tools.

4.  The PM shall provide Lessons Learned training early in Project
    formulation to the Project team, including major partners and
    suppliers, as defined in the LLP. Training in Lessons Learned is
    available from the FPPD Office. PM's and other senior systems
    management personnel should receive advanced training in Lessons
    Learned and Knowledge Management. The SMO and Headquarters Office of
    Safety and Mission Assurance are sources of advanced training in
    Knowledge Management.

**CHANGE HISTORY LOG**

  -------------- ------------- ---------------------------------------------
  **Revision**   **Effective   **Description of Changes**
                 Date**        

  Baseline                     Initial Release

                               

                               

                               

                               

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

#  

**Figure 3. Lessons Learned Submission Form**

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

                                                                       CATEGORY               
                                                                       (Primary/Alternate):   

  TITLE/SUBJECT:                                                       KEYWORDS:              

  EVENT DESCRIPTION:                                                                          

  LESSON LEARNED:                                                                             

  RECOMMENDATIONS:                                                                            

  ATTACHMENTS:                                           REFERENCES:                          

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

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

**Figure 4. Description of Lessons Learned Submission Form Items**

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

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

  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 Figure 6)

  Building/Room                                                                                       Office location of the submitter

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

**Figure 5. Categories for Lessons Learned Submission Form**

  ------------------ ----------------------- ----------------------- ------------------------------ -------------------- ---------------------------------
  **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                                  Correspondance

                     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                                                                                             
  ------------------ ----------------------- ----------------------- ------------------------------ -------------------- ---------------------------------

**Figure 6. Specializations for Lessons Learned Submission Form**

  ------------------------------------- ---------------------------------
  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 A. Outline for Project/Program Office Lessons Learned Plan**

1.  Introduction

    1.  Applicable Documents

2.  Lessons Learned Process Overview

    1.  Terms and Definitions

    2.  Lessons Learned Process

    3.  Roles and Responsibilities

    4.  Allocation of Resources

3.  Lessons Learned Identification

4.  Lessons Learned Capture

5.  Lessons Learned Organization

6.  Lessons Learned Application

7.  Lessons Learned Valuation

8.  Lessons Learned Documentation and Communications

    1.  Lessons Learned Reports and Reporting Milestones

    2.  Lessons Learned Awareness and Education

    3.  Project Tools

> Appendix A - Lessons Learned Form\
> Appendix B -- Project Lessons Learned Philosophy/Criteria
>
> Appendix C - Acronyms