Attachment F CDRL 418 XO LMXCDRL 0068 Version 1.00.pdf

Effective Date: June 29, 2023 418-XO-LMXCDRL-0068 Responsible Organization: GeoXO Flight Project/Code 418 Baseline Version 1.0

To verify the correct version of this document, please contact the GeoXO Series Configuration Management

Office.

ii

Geostationary Extended Observations (GeoXO) Lightning Mapper (LMX)

Contract Data Requirement List (CDRL) Signature page

Prepared by:

Electronically approved by: 06/26/2023

Ruth W. Cholvibul Date GeoXO Flight Project, Instrument Systems Engineer NASA GSFC, Code 418

Reviewed by:

Electronically approved by: 05/31/2023

Sivakumara K. Tadikonda Date GeoXO Flight Project, System Engineer

Electronically approved by: 06/28/2023

Tina Gentry Date GeoXO Flight Project, Instrument Manager

Approved by:

Electronically approved by: 06/26/2023

Steve Bidwell Date GeoXO Flight Project, Mission Systems Engineer

Effective Date: June 28, 2023 418-XO-LMXCDRL-0068 Responsible Organization: GeoXO Flight Project/Code 418 Baseline Version 1.0

To verify the correct version of this document, please contact the GeoXO Series Configuration Management Office.

iii

Approved by:

Electronically approved by: 06/29/2023

Monica Todirita Date GeoXO Flight Project, Deputy Project Manager NOAA GSFC, Code 418

/GeoXO Flight Project LMX Lightning Mapper

LMXCDRL

418-XO-LMXCDRL-0068, RM Version, Geostationary eXtended Observations (GeoXO) Lightning Mapper (LMX) Contract Data Requirements List (CDRL) Phase B

Version: 1.0 Printed by: rkhoover Printed on: Friday, June 30, 2023

No filter applied.

No sort applied.

Generated from DOORS 9.7.2.4

Contents

1 1Introduction

1.1 1Definition of Due Dates/Maturity, Definition of Categories, and Delivery

1.2 3Applicable Documents

1.3 3Reference Documents

2 4Contract Data Requirements List

3 16Data Item Descriptions

3.1 16Project Management

3.1.1 16PM-01: Project Management Plan

3.1.2 18PM-02: Weekly Status Reports and Telecon Minutes

3.1.3 19PM-03: Risk Management Plan

3.1.4 20PM-04: Configuration Management Plan

3.1.5 21PM-05: Configuration Change Requests, Deviations, and Waivers

3.1.6 22PM-06: Project Management Status Reviews – Technical (PMSR -T), Business

(PMSR-B)

3.1.7 26PM-07: Spare Parts Plan and List

3.1.8 26PM-08: Digital Image and Video Records

3.1.9 27PM-09: Document Tree

3.1.10 28PM-10: Engineering Design Unit (EDU), Prototype, and Engineering Development Model (EDM) Activities Report

3.2 28Resource management

3.2.1 28RM-01: Earned Value Management (EVM) Plan

3.2.2 29RM-02: Financial Reports

3.2.3 30RM-03: Integrated Program Management Data and Analysis Report (IPMDAR)

3.2.4 38RM-04: Contract Work Breakdown Structure (CWBS) and CWBS Dictionary

3.2.5 40RM-05: RESERVED

3.2.6 40RM-06: Unit Cost Report

3.2.7 40RM-07: Integrated Baseline Review (IBR) Package

3.3 42System Review

3.3.1 42SR-01: System Requirements Review (SRR) / System Definition Review (SDR)

Data Package

3.3.2 46SR-02: Preliminary Design Review (PDR) Data Package

3.3.3 50SR-03: Critical Design Review (CDR) Data Package

3.3.4 56SR-04: Pre-Environmental Review (PER) Data Package

3.3.5 59SR-05: Pre-Storage/Pre-Ship Review Data Package

Project: GeoXO Flight Project LMX Lightning Mapper Module: LMXCDRL Baseline Version: 1.0

Contents ii

3.3.6 61SR-06: Design Modification Review (DMR) Data Package

3.3.7 63SR-07: Peer Review / Subsystem / Subcontract Review Data Packages

3.4 63Systems Engineering

3.4.1 63SE 1: Specifications

3.4.1.1 63SE 1-1: Instrument System Specification

3.4.1.2 64SE 1-2: RESERVED

3.4.1.3 64SE 1-3: RESERVED

3.4.1.4 64SE 1-4: Instrument Electrical Block Diagrams and Approved or Controlled

3.4.1.5 65SE 1-5: Instrument Description Document (IDD)

3.4.1.6 67SE 1-6: Drawing Tree

3.4.2 67SE 2: Plans

3.4.2.1 67SE 2-1: Systems Engineering Management Plan

3.4.2.2 69SE 2-2: System Performance Verification Plan and Compliance

3.4.2.3 71SE 2-3: Contamination Control Plan

3.4.2.4 73SE 2-4: RESERVED

3.4.2.5 73SE 2-5: Electrostatic Discharge Control Plan

3.4.2.6 73SE 2-6: RESERVED

3.4.2.7 73SE 2-7: EMC/EMI Compatibility Plan

3.4.2.8 74SE 2-8: On-Orbit Electro-Static Discharge Control Plan

3.4.2.9 74SE 2-9: Trend Analysis Plan

3.4.2.10 75SE 2-10: Individual Test Plans

3.4.2.11 76SE 2-11: Life Test Plan

3.4.2.12 77SE 2-12: Image Navigation and Registration (INR) Modeling and Analysis Plan

3.4.2.13 78SE 2-13: Engineering Development and Test Plan

3.4.3 79SE 3: Procedures

3.4.3.1 79SE 3-1: Test and Calibration Procedures

3.4.3.2 81SE 3-2: Instrument Assembly and Integration Procedures/Drawings

3.4.4 81SE 4: Models, Analyses, and Reports

3.4.4.1 81SE 4-1: Mass Properties and Power Report

3.4.4.2 82SE 4-2: Thermal Math Models and Reports

3.4.4.3 86SE 4-3: Solid Math Model

3.4.4.4 86SE 4-4: Structural Math Model and Reports

3.4.4.5 87SE 4-5: Radiation Shielding and Dose Analysis Report

3.4.4.6 88SE 4-6: Engineering Analysis Reports (EAR)

3.4.4.7 89SE 4-7: Trend Reports

3.4.4.8 89SE 4-8: Test Reports

3.4.4.9 91SE 4-9: Test Reports for Subcontracted Items

3.4.4.10 92SE 4-10: System Performance Verification Reports

Contents iii

3.4.4.11 92SE 4-11: INR Design Document

3.4.4.12 93SE 4-12: Line-of-Sight Math Model and Report

3.4.4.13 94RESERVED

3.4.4.14 94SE 4-14: End-to-End INR Simulation Math Model and Report

3.4.4.15 95SE 4-15: Radiometric Math Model and Report

3.4.4.16 95SE 4-16: Optical Model and Report

3.4.4.17 96SE 4-17: Stray Light Model and Report

3.4.4.18 96SE 4-18: Life Test Report for Lubricated Mechanisms

3.4.4.19 97SE 4-19: Structural, Thermal, and Optical Performance (STOP) Analysis Report

3.4.4.20 98SE 4-20: FPGA Design Data Package

3.4.5 99SE 5: Calibration

3.4.5.1 99SE 5-1: Calibration Plan

3.4.5.2 99SE 5-2: Ground Processing Algorithm Document

3.4.5.3 100SE 5-3: Calibration Data Book

3.4.5.4 101SE 5-4: Ground Processing Algorithms Test and Validation Plan

3.4.5.5 102SE 5-5: Ground System Software Acceptance Plan Input

3.4.5.6 102SE 5-6: Instrument Packetized Data

3.5 102Software

3.5.1 102SW-01: Software Management Plan

3.5.2 104SW-02: Software Maintenance Plan

3.5.3 106SW-03: Software Requirements Specification

3.5.4 107SW-04: Software Preliminary Design Review (SWPDR) Data Package

3.5.5 109SW-05: Software Critical Design Review (SWCDR) Data Package

3.5.6 109SW-06: Software Design Document

3.5.7 110SW-07: Software Test Plan

3.5.8 112SW-08: Software Test Procedures

3.5.9 112SW-09: Software Test Readiness Review (SWTRR) Data Package

3.5.10 113SW-10: Software Test Report

3.5.11 114SW-11: Software Acceptance Review (SWAR) Data Package

3.5.12 114SW-12: Software Delivery Package

3.6 116Integration & Test

3.6.1 116I&T-01: Transportation and Handling Plan and Procedures

3.6.2 117I&T-02: Storage and Test Plan

3.6.3 118I&T-03: Satellite-level Test Plan and Procedures

3.6.4 119I&T-04: Satellite-level Test Report and On-site Data Analysis Reports

3.6.5 120RESERVED

3.6.6 120RESERVED

3.7 120Operations

Contents iv

3.7.1 120OPS-01: Instrument Telemetry and Command Database

3.7.2 121OPS-02: Instrument Telemetry and Command Handbook

3.7.3 122OPS-03: Instrument Operations Handbook

3.7.4 124OPS-04: Instrument Operations Training Package

3.7.5 125OPS-05: Instrument Operations Configurable Items

3.7.6 125OPS-06: Instrument Post-Launch Test Plan and Procedures

3.7.7 126OPS-07: Instrument Post-Launch Test Reports

3.7.8 127OPS-08: On-orbit Instrument Anomaly Reports

3.7.9 127SIM-01: Operations, Test, and Maintenance Manual for the Instrument Hardware

Simulator

3.7.10 128SIM-02: Operations, Test, and Maintenance Manual for the Instrument Software

Simulator

3.8 128Mission Assurance

3.8.1 128System Safety and Mission Assurance

3.8.1.1 128MA 1-1: Mission Assurance Compliance Matrix

3.8.1.2 129MA 1-2: Suppliers List

3.8.2 130Quality Management System

3.8.2.1 130MA 2-1: Non-Conformance Report - Material Review Board (MRB) and Failure

Review Board (FRB)

3.8.3 131System Safety Deliverables

3.8.3.1 131MA 3-1: System Safety Program Plan

3.8.3.2 132MA 3-2: Safety Requirements Compliance Checklist

3.8.3.3 132MA 3-3: Instrument Safety Assessment Report (ISAR) and Verification Tracking

Log (VTL)

3.8.3.4 134MA 3-4: Operations Hazard Analysis and Verification Tracking Log

3.8.3.5 135MA 3-5: Hazardous Procedures for Payload I&T and Pre-launch Processing

3.8.3.6 136MA 3-6: Pre-Mishap Plan and Mishap Reports

3.8.4 138Reliability

3.8.4.1 138MA 4-1: Reliability Program Plan

3.8.4.2 138MA 4-2: Failure Modes, Effects, and Criticality Analysis (FMECA) and Critical Items

List (CIL)

3.8.4.3 139MA 4-3: Fault Tree Analysis (FTA) Report

3.8.4.4 140MA 4-4: Parts Stress Analysis Report

3.8.4.5 140MA 4-5: Worst Case Analysis Report

3.8.4.6 141MA 4-6: Reliability Assessments and Predictions

3.8.4.7 142MA 4-7: Limited-Life Items List

3.8.5 142Software Assurance

3.8.5.1 142MA 5-1: Software Assurance Plan

3.8.6 143Workmanship Standards

3.8.6.1 143MA 6-1: Printed Circuit Board Procurement Specification

Contents v

3.8.6.2 144MA 6-2: Printed Circuit Board (PCB) Coupon Evaluation Reports and Lot Acceptance and Quality Conformance Testing Results for Printed Circuit Boards

3.8.7 145EEE Parts

3.8.7.1 145MA 7-1: EEE Parts Control Plan

3.8.7.2 145MA 7-2: Master EEE Parts List

3.8.8 147Materials, Processes and Lubrication Requirements

3.8.8.1 147MA 8-1: Materials and Processes Selection, Control, and Implementation Plan

3.8.8.2 149MA 8-2: Materials Usage Agreement (MUA)

3.8.8.3 150MA 8-3: Materials Identification and Usage List (MIUL)

3.8.9 150Government-Industry Data Exchange Program (GIDEP) Alerts and Problem Advisories

3.8.9.1 151MA 11-1: Responses to Alerts

4 152Acronym List

Contents vi

Page 1 of 155 Printed Friday, June 30, 2023

ID

LMXCDRL1

LMXCDRL2

LMXCDRL3

Object Number

1.0-1

1.1

418-XO-LMXCDRL-0068, RM Version, Geostationary eXtended Observations (GeoXO) Lightning Mapper (LMX) Contract Data

Requirements List (CDRL) Phase B

1 Introduction This Contract Data Requirements List (CDRL) document defines the requirements for deliverable Data to be provided by the Geostationary eXtended Observations (GeoXO) Instrument Contractor. “Instrument” as referred to in this document applies to the GeoXO Lightning Mapper (LMX). Section 1.1 includes definitions and instructions for distribution. Section 2 presents the CDRL item by item with due dates. Section 3.0 provides the Data Item Description (DID), a description of each item and describes use, and Preparation Information.

1.1 Definition of Due Dates/Maturity, Definition of Categories, and Delivery Instructions

Page 2 of 155 Printed Friday, June 30, 2023

ID

LMXCDRL4

LMXCDRL5

LMXCDRL6

Object Number

1.1.0-1

1.1.0-2

1.1.0-3

418-XO-LMXCDRL-0068, RM Version, Geostationary eXtended Observations (GeoXO) Lightning Mapper (LMX) Contract Data

Requirements List (CDRL) Phase B

The following definitions apply to the "DUE DATE, MATURITY" column in the Table in Section 2.

a) DUE DATE:

1) Proposal. Items that are provided with the proposal.

2) CDR, PER, PSR, etc. Critical Design Review, Pre-Environmental Review, Pre-Ship Review, etc., respectively.

3) As Generated. After each initial edition, revision, addition, etc.

4) As Directed. Per direction by the CO.

5) Monthly. Monthly by the 15th of each month or as required or as modified by the Contracting Officer (CO).

6) Weekly. With weekly status reports by Monday 12 noon ET or as modified by CO.

7) L. Launch Date.

8) DACA. Days after contract award. Unless otherwise noted, the data in the due date column titled "days" are to be interpreted as calendar days.

9) NLT: No Later Than

10) ATP: Authorization to Proceed

b) MATURITY:

1) Preliminary: The first submission of an item. Applies to milestone deliveries. To be completed with available information as of the time of preparation for the due date.

2) Initial: The first submission of an item for deliveries that are periodic – weekly, monthly, etc. To be updated with available information as of the time of preparation for the due date.

3) Update: The best up-to-date information available at the time.

4) Final: The complete thorough submission of an item. This does not preclude updating later.

c) NASA Acceptance Code

A Approval: Documents in this category require approval by the Goddard Space Flight Center (GSFC) Contracting Officer’s Representative (COR) prior to use by the Contractor.

R Review: Documents in this category require delivery to the Government prior to use and within the time period specified in the "Due Date" column of the Instrument Contract Data Requirement List in Section 2 of this document. They are subject to evaluation by the Government or its designated representatives to determine Contractor effectiveness in meeting contract objectives.

I Information: Data in this category require delivery to the Government within the time period specified in the “Due Date” column of the Contract Data Requirement List in Section 2 of this document for the purpose of determining current program status, progress, and future planning requirements.

The following requirements terminology is used throughout this document:

a) The use of “shall” designates a requirement that must be met.

b) The use of “will” designates a statement of fact or intention of the

Government.

c) The use of “may” designates that permission has been granted by the

Government.

The Contractor shall transmit items with an “As Generated” due date that are critical to schedule, performance, or interface to GSFC within 48 hours of formal release.

Page 3 of 155 Printed Friday, June 30, 2023

ID

LMXCDRL7

LMXCDRL8

LMXCDRL9

LMXCDRL10

LMXCDRL11

LMXCDRL12

LMXCDRL13

LMXCDRL14

LMXCDRL15

LMXCDRL16

LMXCDRL17

Object Number

1.1.0-4

1.1.0-5

1.1.0-6

1.1.0-7

1.1.0-8

1.1.0-9

1.1.0-10

1.2

1.2.0-1

1.3

1.3.0-1

418-XO-LMXCDRL-0068, RM Version, Geostationary eXtended Observations (GeoXO) Lightning Mapper (LMX) Contract Data

Requirements List (CDRL) Phase B

Unless specified otherwise, any updates to items of “Final” maturity shall require the same "approval/review" process as was required for the previous submissions.

Receipt of “Approval”, “Review”, and “Information” coded items by the Government shall occur within the time specified in the “Due Date” column of the Contract Data Requirement List in Section 2 of this document.

Requirements for re-submission of “Approval” coded items shall be as specified in the letters of disapproval. For most cases, the Contractor will be required to resubmit the document within 30 days of receiving comments from the Government.

If the Contractor has not received response from GSFC within 30 days of delivery of an “Approval” coded CDRL item (15 days for test procedures), the Contractor may proceed as if the document has been approved.

When Government evaluations of “Review” coded items reveal inadequacies, the Contractor shall correct the documents within 30 days of receiving comments or provide a plan approved by the Government for closing deficiencies.

All Data items shall be delivered in electronic format to the GeoXO portal unless otherwise noted in the Contract Data Requirement List in Section 2 of this document.

Electronic deliverables shall be delivered in the following formats unless otherwise approved by the Government:

a) Text Documents: PDF (searchable) or MSWord.

b) Presentations: PDF (searchable) or PowerPoint.

c) Spreadsheets: Microsoft Excel.

d) Database: Unless specified otherwise, delimited ASCII files accompanied with database schema document defining tables and entries.

e) Schedules: MS Project compatible.

f) Schematics and Drawings: PDF.

g) Photographs: JPEG or current industry standard.

h) Video: Any readily available open standard (e.g., AVI, MPEG).

i) System Specifications in Direct Object-Oriented Requirements System

(DOORS) (DPA, DMA updates) and PDF.

1.2 Applicable Documents

The following documents form a part of this specification to the extent specified herein:

1.3 Reference Documents

The following documents contain information relating to the work required but which do not constitute requirements:

Page 16 of 155 Printed Friday, June 30, 2023

ID

LMXCDRL20

LMXCDRL21

LMXCDRL22

LMXCDRL23

LMXCDRL933

LMXCDRL24

LMXCDRL25

LMXCDRL26

LMXCDRL27

LMXCDRL28

LMXCDRL29

LMXCDRL30

LMXCDRL31

LMXCDRL32

Object Number

3.1

3.1.1

3.1.1.0-1

3.1.1.0-2

3.1.1.0-3

3.1.1.0-4

3.1.1.0-5

3.1.1.0-6

3.1.1.0-7

3.1.1.0-8

3.1.1.0-9

3.1.1.0-10

3.1.1.0-11

418-XO-LMXCDRL-0068, RM Version, Geostationary eXtended Observations (GeoXO) Lightning Mapper (LMX) Contract Data

Requirements List (CDRL) Phase B

3 Data Item Descriptions

3.1 Project Management

3.1.1 PM-01: Project Management Plan

DATA ITEM DESCRIPTION

1. CDRL No.: PM-01

2. Title: PROJECT MANAGEMENT PLAN

3. Use: Describes how the Project is organized and managed. It provides the management structure, its system of operation, responsible lines of communications, and key personnel assignments.

4. Preparation Information:

General

The Project Management Plan shall address the overall organization, management approach, and structure of the Program plus its interrelationships with the parent company and the Subcontractors, and relationship with the Government.

The Project Management Plan shall address interfaces with the Government and with any Government Furnished Equipment (GFE) suppliers.

The Project Management Plan shall delineate how the requirements of the Statement of Work (SOW) will be achieved and include a description of planned activities for identifiable SOW requirements.

The Project Management Plan shall describe the concept of the nature of the tasks and related potential problems. Discuss the approach to problem avoidance and/or solution.

The Project Management Plan shall define the technical, schedule and cost control plan and describe management techniques to be employed in minimizing program costs and schedule impacts for all activities, including controls to be exercised over Subcontractors and suppliers.

The Project Management Plan shall describe make/buy strategies, acquisition plans, sparing philosophy, Project dependencies, facility requirements, internal review strategies and plans, significant work elements on critical paths, long-lead items.

The Project Management Plan shall identify how Contractor’s risk management system and processes are integrated into the daily management, decision making, and strategic direction of the Project and how you foresee Government participation in that process.

The Project Management Plan shall describe how issues will be identified in a timely manner and at the proper levels.

The Project Management Plan shall identify additional definition of spacecraft interfaces and mission design and the need date.

Page 17 of 155 Printed Friday, June 30, 2023

ID

LMXCDRL33

LMXCDRL34

LMXCDRL35

LMXCDRL36

LMXCDRL37

LMXCDRL38

LMXCDRL39

LMXCDRL40

LMXCDRL41

LMXCDRL42

LMXCDRL43

Object Number

3.1.1.0-12

3.1.1.0-13

3.1.1.0-14

3.1.1.0-15

3.1.1.0-16

3.1.1.0-17

3.1.1.0-18

3.1.1.0-19

3.1.1.0-20

3.1.1.0-21

3.1.1.0-22

418-XO-LMXCDRL-0068, RM Version, Geostationary eXtended Observations (GeoXO) Lightning Mapper (LMX) Contract Data

Requirements List (CDRL) Phase B

The Project Management Plan shall identify and list the subsystems and subcontracts that warrant a formal design review process due to their criticality or development risk.

The Project Management Plan shall provide contractual procedures proposed for the Project to effect administrative and engineering changes, describing any differences from existing procedures.

The Project Management Plan shall describe how and where the program will operate during all phases of the contract.

Organization

The Project Management Plan shall provide an organizational chart(s) and sufficient supplemental narrative to describe fully the organization proposed for carrying out the Project showing inter- relationships of technical management, business management, and subcontract management, from lower level through intermediate management to top-level management with detailed explanation of:

a) How and by whom interdepartmental work will be monitored and the authority of the program manager over interdepartmental work.

b) Process to be followed by the program manager in obtaining decisions beyond his/her authority and in resolving priority conflicts for resources and functions not under the program manager’s direct control such as personnel, finances, and facilities.

c) The authority of the Program Manager relative to other ongoing programs and applicable support organizations within the company structure.

d) Discuss the program manager’s control over essential resources and functions necessary to accomplish the work.

The Project Management Plan shall discuss the availability of the technical, test, manufacturing and system safety/quality assurance/ reliability/ configuration management personnel required for this program (as indicated in your proposed labor hours).

The Project Management Plan shall state the number and skillset of persons who would have to be hired and plans to obtain them.

Mission Assurance

The Project Management Plan shall discuss and illustrate the proposed Mission Assurance organizational structure, including staffing plans, reporting channels, authority and responsibilities, and management visibility.

The Project Management Plan shall state the independence of the system safety/quality assurance functions.

Schedule

Page 18 of 155 Printed Friday, June 30, 2023

ID

LMXCDRL44

LMXCDRL45

LMXCDRL46

LMXCDRL47

LMXCDRL48

LMXCDRL49

LMXCDRL50

LMXCDRL51

LMXCDRL52

LMXCDRL53

LMXCDRL54

LMXCDRL55

LMXCDRL56

LMXCDRL57

LMXCDRL58

LMXCDRL59

Object Number

3.1.1.0-23

3.1.1.0-24

3.1.1.0-25

3.1.1.0-26

3.1.1.0-27

3.1.1.0-28

3.1.1.0-29

3.1.1.0-30

3.1.1.0-31

3.1.1.0-32

3.1.2

3.1.2.0-1

3.1.2.0-2

3.1.2.0-3

3.1.2.0-4

3.1.2.0-5

418-XO-LMXCDRL-0068, RM Version, Geostationary eXtended Observations (GeoXO) Lightning Mapper (LMX) Contract Data

Requirements List (CDRL) Phase B

The Project Management Plan shall describe how the schedules are developed, maintained, and updated.

The Project Management Plan shall explain/describe the schedule administration/control.

The Project Management Plan shall explain the internal review cycle of the scheduling process.

The Project Management Plan shall explain how subcontract schedules are maintained and reported in the master schedule.

The Project Management Plan shall explain how internal audits/reviews ensure that scheduling data reported to the Government accurately reflects the work status.

Knowledge Management

The Project Management Plan shall describe how lessons learned from Instrument development, integration, and test will be captured.

The Project Management Plan shall describe how training will be performed to convey lessons learned as they apply to the development, integration, and test of future flight models.

The Project Management Plan shall describe how lessons learned will be captured and applied to Subcontractor development of critical subassemblies and assemblies.

The Project Management Plan shall describe the overall training plan for project personnel.

3.1.2 PM-02: Weekly Status Reports and Telecon Minutes

DATA ITEM DESCRIPTION

1. CDRL No.: PM-02

2. Title: WEEKLY STATUS REPORTS AND TELECON MINUTES

3. Use: Program status reviews; system, subsystem, and assembly packaging evaluations; and trouble shooting. This weekly report is intended to be timely and informal and should detail the above topics as changes or problems occur.

4. Preparation Information:

The Weekly Status Report shall address the work completed during the week against the work planned.

The Weekly Status Report shall include technical progress, including significant accomplishments and obstacles.

The Weekly Status Report shall contain Program Management (PM), Systems Engineering (SE), engineering disciplines, Integration and Test (I&T), Software (SW), and Mission Assurance (MA) status.

The PM section shall indicate any actual or anticipated slip in schedule, long lead items status, and status on any red risk item.

Page 19 of 155 Printed Friday, June 30, 2023

ID

LMXCDRL60

LMXCDRL61

LMXCDRL62

LMXCDRL63

LMXCDRL934

LMXCDRL64

LMXCDRL65

LMXCDRL67

LMXCDRL68

LMXCDRL69

LMXCDRL70

LMXCDRL71

Object Number

3.1.2.0-6

3.1.2.0-7

3.1.2.0-8

3.1.2.0-9

3.1.2.0-10

3.1.3

3.1.3.0-1

3.1.3.0-2

3.1.3.0-3

3.1.3.0-4

3.1.3.0-5

3.1.3.0-6

418-XO-LMXCDRL-0068, RM Version, Geostationary eXtended Observations (GeoXO) Lightning Mapper (LMX) Contract Data

Requirements List (CDRL) Phase B

The Weekly Status Report shall detail the work planned for the following week and summarize the work planned for the next month.

The Weekly Status Report shall contain telecon minutes for the previous week's weekly telecon and all technical meetings.

The Weekly Status Report shall contain Action Item Status and contain telecon minutes from the previous week's weekly telecon.

The Weekly Status Report shall contain status of any open Non-Conformance Reports.

The Weekly Status Report shall contain status on any open contract actions, including Special Engineering Analyses/Task Orders.

3.1.3 PM-03: Risk Management Plan

DATA ITEM DESCRIPTION

1. CDRL No.: PM-03

2. Title: RISK MANAGEMENT PLAN (RMP)

3. Use: The Risk Management Plan is the basis for identifying and managing all performance, reliability, schedule, cost, and safety risks on the Contractor’s Project. The identification, characterization, mitigation plan, and mitigation responsibilities associated with specific risks are described and specific risk abatement strategies or contingency planning processes are discussed. “Risk” refers to anything that can prevent a team from meeting the Delivery Order objectives.

4. Preparation Information:

The Risk Management Plan shall describe Contractor’s process for Risk Identification, Risk Analysis, Risk Handling and Risk Monitoring.

This Risk Management Plan shall include a process for tracking and reporting risk status and changes.

The Risk Management Plan shall clearly describe:

a) Overview of the risk management process.

b) Organizational responsibilities.

c) Risk identification approach.

d) Risk mitigation planning.

e) Interface of risk management to schedule and financial/cost management.

f) Risk tracking/documentation.

g) Risk management list reporting.

The Risk Management Plan shall include risks associated with hardware and software (e.g., technical challenges, new technology qualification, etc.), commercial off-the-shelf (COTS) items, system safety, performance, cost, and schedule (i.e., programmatic risks).

The Risk Management Plan shall identify which tools and techniques will be used to manage the risks.

Page 20 of 155 Printed Friday, June 30, 2023

ID

LMXCDRL72

LMXCDRL73

LMXCDRL935

LMXCDRL970

LMXCDRL74

Object Number

3.1.3.0-7

3.1.3.0-8

3.1.3.0-9

3.1.3.0-10

3.1.4

418-XO-LMXCDRL-0068, RM Version, Geostationary eXtended Observations (GeoXO) Lightning Mapper (LMX) Contract Data

Requirements List (CDRL) Phase B

The Risk Management Plan shall use the GSFC risk 5x5 definitions as described in LMXCDRL970.

The Risk Management Plan shall form risk statements in the format as expressed in the following: “Given the [condition], there is a possibility that [consequence] will occur with the result that [outcome].”

Reference:

1. GPR 7120.4D, GSFC Guideline for Performing Risk Assessments

2. NPR 8000.4C, Risk Management Procedural Requirements

Likelihood Safety Estimated likelihood of Safety event occurrence

Technical Estimated likelihood of not meeting performance requirements

Cost Schedule Estimated likelihood of not meeting cost or schedule commitment

5 Very High (PSE> 10-1) (PT > 50%) (PCS > 75%)

4 High (10-2 < PSE < 10-1) (25% < PT < 50%) (50% < PCS < 75%)

3 Moderate (10-3 < PSE < 10-2) (15% < PT < 25%) (25% < PCS < 50%)

2 Low (10-5 < PSE < 10-3) (2% < PT < 15%) (10% < PCS < 25%)

1 Very Low (10-6 < PSE < 10-5) (0.1% < PT < 2%) (2% < PCS < 10%)

Consequence Categories

LOW RISK

MODERATE

RISK

HIGH RISK

Risk 1 Very Low 2 Low 3 Moderate 4 High 5 Very High

Safety

Negligible or not impact

Could cause the need for only minor first aid treatment

May cause minor injury or occupational illness or minor property damage.

May cause severe injury or occupational illness or major property damage.

May cause death or permanently disabling injury or destruction of property.

Technical

No impact to full mission success criteria

Minor impact to full mission success criteria

Moderate impact to full mission success criteria. Minimum mission success criteria is achievable with margin

Major impact to full mission success criteria. Minimum mission success criteria is achievable

Minimum mission success criteria is not achievable

Schedule

Negligible or no schedule impact

Minor impact to schedule milestones;

accommodates within reserves;

no impact to critical path

Impact to schedule milestones;

accommodates within reserves;

moderate impact to critical path

Major impact to schedule milestones; major impact to critical path

Cannot meet schedule and program milestones

Cost

< 2% increase over allocated and negligible impact on reserve

Between 2% and 5% increase over allocated and can handle with reserve

Between 5% and 7% increase over allocated and cannot handle with reserve

Between 7% and 10% increase over allocated, and/or exceeds proper reserves

> 10% increase over allocated, and/or can’t handle with reserves

3.1.4 PM-04: Configuration Management Plan

Page 21 of 155 Printed Friday, June 30, 2023

ID

LMXCDRL75

LMXCDRL76

LMXCDRL77

LMXCDRL78

LMXCDRL79

LMXCDRL80

Object Number

3.1.4.0-1

3.1.4.0-2

3.1.4.0-3

3.1.4.0-4

3.1.4.0-5

3.1.5

418-XO-LMXCDRL-0068, RM Version, Geostationary eXtended Observations (GeoXO) Lightning Mapper (LMX) Contract Data

Requirements List (CDRL) Phase B

DATA ITEM DESCRIPTION

1. CDRL No.: PM-04

2. Title: CONFIGURATION MANAGEMENT PLAN

3. Use: Defines the Contractor’s configuration management system

(including policies and procedures) that will be implemented for the Instrument flight hardware.

4. Preparation Information:

The Contractor’s configuration management plan shall be prepared in accordance with the Contractor’s standards.

The Configuration Management Plan shall describe in detail all flight hardware configuration management processes, methods, and procedures the Contractor intends to use on the Instrument.

The Configuration Management Plan shall describe how the Contractor plans to:

a) Accomplish hardware and software configuration management,

b) Achieve consistency between product definition, the product’s configuration, and the configuration management records, and

c) Maintain configuration management throughout the applicable phases of the product’s life cycle.

The Configuration Management Plan shall describe the Contractor’s approach, methodology, and application of configuration management principles and practices, including:

a) General product definition and scope.

b) Description of configuration management activities and procedures for each of the following configuration management functions:

1) Configuration planning and management.

2) Configuration identification.

3) Configuration Change management.

4) Configuration status accounting.

5) Configuration verification and audit.

6) Configuration management of digital data.

7) Configuration management of software.

c) Organization, roles, responsibilities, and resources.

d) Definition of terms.

e) Programmatic and organizational interfaces.

f) Subcontract flow down of configuration management.

3.1.5 PM-05: Configuration Change Requests, Deviations, and

Waivers

Page 22 of 155 Printed Friday, June 30, 2023

ID

LMXCDRL81

LMXCDRL82

LMXCDRL83

LMXCDRL84

LMXCDRL85

LMXCDRL86

LMXCDRL87

LMXCDRL88

LMXCDRL89

LMXCDRL90

Object Number

3.1.5.0-1

3.1.5.0-2

3.1.5.0-3

3.1.5.0-4

3.1.5.0-5

3.1.5.0-6

3.1.5.0-7

3.1.5.0-8

3.1.6

3.1.6.0-1

418-XO-LMXCDRL-0068, RM Version, Geostationary eXtended Observations (GeoXO) Lightning Mapper (LMX) Contract Data

Requirements List (CDRL) Phase B

DATA ITEM DESCRIPTION

1. CDRL No.: PM-05

2. Title: CONFIGURATION CHANGE REQUESTS, DEVIATIONS, AND

WAIVERS

3. Use: To facilitate the orderly processing of engineering change requests to specifications or requirements, changes to plans or procedures, specification deviations, waivers, to appropriate level of review, classification, and approval authority for disposition.

4. Preparation Information:

Consistent with the Contractor’s Configuration Management Plan (CMP), the Contractor shall prepare, and submit Configuration Change Requests (CCR) for Government review.

CCRs shall be either Class I or Class II.

In addition to the change description, the CCR shall contain sufficient information in the form of attachments, drawings, test results, etc., to allow the Government to evaluate the total impact of the proposed change. The Government Contracting Officer may direct the Contractor to prepare CCRs under the “Changes” clause of the contract.

A Class I CCR is a change that:

a) Affects any Government Contract requirement, specification, or interface requirement.

b) Affects schedules of end item deliverables to the Government.

c) Impacts Government Furnished Equipment.

d) Affects configuration to the extent that changes would be required to prior deliverables in order to maintain specified performance.

e) Creates a new Single Point Failure possibility.

A change may be classified Class II when it does not fall within the definition of a Class I change as given above. Examples of Class II changes are:

a) A change in documentation only (for example, correction of errors, addition or clarifying notes or views).

b) A minor change in hardware (for example, substitution with an approved alternative material) which does not affect any item listed under Class I changes.

c) Drawing changes that do not affect a baseline, interface, etc.

Class II changes normally do not require Government Configuration Control Board (CCB) approval unless they are written against Government CM-controlled documents.

Waivers and Deviations are considered CCRs and will follow the CCR approval process.

3.1.6 PM-06: Project Management Status Reviews – Technical

(PMSR -T), Business (PMSR-B)

DATA ITEM DESCRIPTION

1. CDRL No.: PM-06

2. Title: PROJECT MANAGEMENT STATUS REVIEWS – TECHNICAL

Page 23 of 155 Printed Friday, June 30, 2023

ID

LMXCDRL90

LMXCDRL91

LMXCDRL92

Object Number

3.1.6.0-1

3.1.6.0-2

3.1.6.0-3

418-XO-LMXCDRL-0068, RM Version, Geostationary eXtended Observations (GeoXO) Lightning Mapper (LMX) Contract Data

Requirements List (CDRL) Phase B

(PMSR -T) AND BUSINESS (PMSR-B)

3. Use: To evaluate contract status. These reports will be used to provide an opportunity for face-to-face discussions between the Contractor and the Government regarding Project status, plans, and issues. The Contractor provides a management level review of technical, schedule, financial, and programmatic activities to the Government. These reviews will typically address the topics listed below as required. Addition of special topics will be coordinated between Government and Contractor prior to each meeting.

4. Preparation Information:

The Project Management Status Review (PMSR) shall include all aspects of the contract effort. The final scheduled monthly Project management review will occur the month following the delivery of the last FM under contract.

The PMSR-T data package shall address the following:

a) Program Manager’s Assessment and Program Summary.

b) Current organization chart, including names of individuals fulfilling the roles identified and updates as necessary.

c) Report of Key Technical Parameters and trends for each Technical

Performance Metric (TPM). The list of reported Key Technical Parameters will be per mutual agreement with the Government. The parameters presented will be at least to the major component level of the subsystems, e.g., Mechanisms, Power supplies, heaters, cabling, etc.

At a minimum, the TPMs (Current Best Estimate (CBE) and Margin) against the specification for:

1) Mass (Kg)

2) Operational Peak and Average Power (W)

3) Survival Peak and Average Power (W)

4) Pointing knowledge and control error budgets

5) Average Data Rate (Mbps)

6) Peak Data Rate (Mbps)

7) Memory Utilization

8) CPU Utilization

9) Science metrics that are selected to show the satisfaction and stability of the science performance requirements

10) Accuracy of the values and units

11) Status of margins and contingency

d) Technical status for system and subsystem design and development activities, including technology maturity efforts for reaching Technology Readiness Level (TRL) 6 by PDR, and subcontract technical performance.

e) Design Status (when design work is being accomplished) covering the design activities for the previous month, including schedule and technical status of development, manufacturing status, qualification and test status, issues and concerns, and Configuration Change status:

1) List of Class I in process and approved changes.

2) List of Class II approved Changes available upon request.

f) Summary of Integrated Master Schedule Status, including a brief description of the status of each subsystem or subassembly

Page 24 of 155 Printed Friday, June 30, 2023

ID

LMXCDRL92

Object Number

3.1.6.0-3

418-XO-LMXCDRL-0068, RM Version, Geostationary eXtended Observations (GeoXO) Lightning Mapper (LMX) Contract Data

Requirements List (CDRL) Phase B along with descriptions of any existing or potential problem areas.

g) Critical path and near critical paths explained along with possible workarounds being considered to maintain the schedule. A slack metric with at least 1 month of aging (prior month slack) will be maintained and provided for major subassemblies and activities.

h) Schedule Risk Analysis (SRA) results, including projected delivery date based on SRA

i) Integration & Test Status such as Test Issues, Test Results, Performance Trends.

j) Verification & Validation status and issues (as required).

k) Mission Assurance status such as summary of MRB actions and status; summary of FRB actions and status; failure investigations and corrective actions

l) Lower Tier Suppliers Status (as required).

m) Problems (problems that are significant in nature, questionable

“significance” should be discussed with and determined by the Instrument Manager or COR) encountered during the reporting period, and anticipated approaches for resolution (including, as appropriate, technical issues, manpower and staffing, supplier and Subcontractor issues, etc.).

n) Status of open issues and problems from prior reporting periods.

o) Risk Status for top 10 risks, including the status of mitigations plans of each.

p) Schedule and Cost Threats summary based on quantified values of all risks with schedule and cost impacts

q) Status of Master Action Items Database (MAID) action items with focus brought to those actions which are not closing in a timely manner.

r) Identification and status of long-lead purchases/acquisitions planned.

s) Prohibited Materials Compliance Status (as required):

1) GeoXO Product Alert evaluation status.

2) Production Readiness Issues (as required).

t) Significant plans and activities for the following month, including upcoming milestone events depicting critical items of Project status.

u) Contract Status:

1) Summary of current proposals, proposal preparations and expected completion dates.

2) Summary of current and expected Configuration Change

Requests (CCRs).

3) Summary of potential future proposals and CCRs, including Deviations and Waivers.

v) Summary of Task Orders.

1) Status of current task orders and estimated completion dates.

2) Discussion of impediments to timely completion of tasks.

3) Discussion of potential future tasks.

w) CDRL Status Report that includes the following information for each document delivered in accordance with the CDRL or overdue from previous reporting periods:

1) Document Number

Page 25 of 155 Printed Friday, June 30, 2023

ID

LMXCDRL92

LMXCDRL93

LMXCDRL94

Object Number

3.1.6.0-3

3.1.6.0-4

3.1.6.0-5

418-XO-LMXCDRL-0068, RM Version, Geostationary eXtended Observations (GeoXO) Lightning Mapper (LMX) Contract Data

Requirements List (CDRL) Phase B

2) Document Title

3) Scheduled Due Date

4) Actual Submittal Date

5) Current Status

6) List of documents planned for delivery during the next reporting period, listed by document number, title, and scheduled submittal date.

x) Award Fee (AF) Milestone Status.

1) List of Current AF Milestones with current due date and expected completion dates.

2) Summary of issues that may be hindering the timely completion of each AF milestone.

The PMSR-T presentation material may be in Contractor format.

The PMSR-B data package shall address the following:

a) Program Manager’s Assessment and Program Summary

b) Summary of Integrated Master Schedule Status, including a brief description of the status of each subsystem or subassembly along with descriptions of any existing or potential problem areas.

c) Explanation for the critical path and near critical paths along with possible workarounds being considered to maintain the schedule.

A slack metric with at least 1 month of aging (prior month slack) is to be maintained and provided for major subassemblies and activities (the Government and Contractor managers will determine which items are to be tracked at least quarterly).

d) A detailed 12-month “rolling-wave” schedule (3 months of actual, plus 9 months of forecast)

e) Metrics summarizing all milestones depicting planned versus actual accomplishments and explanations for variances, e.g., graphic display of planned versus actual cumulative milestone status, xx of 1,000 milestones are behind plan and why, etc.

f) Summary explanation of key EVM parameter performance and trends

g) Metrics by Integrated Product Team (IPT) and Total Project, summarizing Baseline, Forecast and Actual Headcounts where a head equals one equivalent work-month of effort. Include explanation of variance from plan.

h) Review of Management Reserve (MR) Liens or other unfunded risk mitigations including estimated cost and impact

i) Status of action items with focus brought to those actions which are not closing in a timely manner

j) Business issues, including personnel changes

k) Summary of Contract Status:

1) Summary of current contract Funding vs contract cost and Termination Liability requirements

2) Projection of future funding requirements

3) Summary of proposals (Current and in process)

l) Summary of Task Orders in a tabular format:

1) Task Order number and title

2) Authorized value

3) Period of Performance

Page 26 of 155 Printed Friday, June 30, 2023

ID

LMXCDRL94

LMXCDRL95

LMXCDRL96

LMXCDRL97

LMXCDRL98

LMXCDRL99

LMXCDRL100

LMXCDRL101

LMXCDRL102

LMXCDRL103

LMXCDRL104

LMXCDRL105

Object Number

3.1.6.0-5

3.1.6.0-6

3.1.7

3.1.7.0-1

3.1.7.0-2

3.1.7.0-3

3.1.7.0-4

3.1.7.0-5

3.1.7.0-6

3.1.7.0-7

3.1.7.0-8

3.1.8

418-XO-LMXCDRL-0068, RM Version, Geostationary eXtended Observations (GeoXO) Lightning Mapper (LMX) Contract Data

Requirements List (CDRL) Phase B

4) Actual Cost to date

5) Actual Cost of money to date

6) Estimate at completion

7) Estimated completion Date

8) Total estimated estimate at completion for all closed and open tasks v the total authorized task pool value

9) Status – Open or Closed

10) Discussion of impediments to completing tasks in a timely and cost-effective manner, if applicable

The PMSR-B presentation material may be in Contractor format.

3.1.7 PM-07: Spare Parts Plan and List

DATA ITEM DESCRIPTION

1. CDRL No.: PM-07

2. Title: SPARE PARTS PLAN AND LIST

3. Use: To review Contractor’s spares plan and parts list.

4. Preparation Information:

The Spare Parts Plan shall define and justify the Contractor’s position for the spares proposed for the Instrument.

The Spare Parts Plan shall present the schedule and method for obtaining the spares.

The Spare Parts Plan shall provide a listing of Spare Parts and assemblies.

For the purposes of this CDRL, the information sought is for parts and assemblies that are not commonly available or those that may cause schedule problems if out of stock.

The Spare Parts Plan shall consider the judicious definition, procurement, and stock of a set of these critical spares to help minimize potential schedule impact created by subsystem failures, by contamination, or by other plausible events or conditions.

The spares may be retained as fully assembled, partially assembled or piece part spares. Since the need to use a spare may be a failure condition in the Instrument and, depending on the specifics of the fault, the spare itself may need rework or repair, simple substitution of a spare may not be a viable approach.

With this consideration in mind, the Contractor shall establish the assembly level of sparing.

In defining the spare parts program, the Contractor shall consider the reliability, handling, and environment conditions of subsystems, components, and parts under consideration for sparing, including the likelihood that these items need to be replaced.

3.1.8 PM-08: Digital Image and Video Records

Page 27 of 155 Printed Friday, June 30, 2023

ID

LMXCDRL106

LMXCDRL107

LMXCDRL108

LMXCDRL109

LMXCDRL110

LMXCDRL111

LMXCDRL112

LMXCDRL113

LMXCDRL114

LMXCDRL115

LMXCDRL116

LMXCDRL117

LMXCDRL937

LMXCDRL118

Object Number

3.1.8.0-1

3.1.8.0-2

3.1.8.0-3

3.1.8.0-4

3.1.8.0-5

3.1.8.0-6

3.1.8.0-7

3.1.8.0-8

3.1.8.0-9

3.1.8.0-10

3.1.8.0-11

3.1.8.0-12

3.1.8.0-13

3.1.9

418-XO-LMXCDRL-0068, RM Version, Geostationary eXtended Observations (GeoXO) Lightning Mapper (LMX) Contract Data

Requirements List (CDRL) Phase B

DATA ITEM DESCRIPTION

1. CDRL No.: PM-08

2. Title: DIGITAL IMAGE AND VIDEO RECORDS

3. Use: Program status reviews, system, subsystem, and assembly packaging evaluations, and troubleshooting.

4. Preparation Information:

The Contractor shall produce closeout photographic documentation of all assemblies during the manufacturing process and of the final integrated configuration "as flown."

The photographs shall be of sufficiently high resolution to reasonably support anomaly resolutions.

The Contractor shall archive photographic documentation of the hardware not posted to the GeoXO portal and make it available to the Government upon request.

The photographs shall include images of major subsystems, critical assemblies, the full-up system, and major Ground Support Equipment (GSE) items.

The photographs shall serve as a record of the build-up of major subassemblies and assemblies, e.g., a typical electronic card, motherboard, electronic subsystem with cover off, etc.

Each Image shall be identified with a label containing the following information:

assembly number, serial number, description (e.g., name of the assembly), date of image, and the supplier's company name.

The subject of the photograph shall appropriately fill the digital frame to allow for effective magnification.

Images shall include pictures of environmental test fixtures.

Images shall be of sufficient resolution to:

a) show component placement,

b) show part marking,

c) show details that are covered or obscured at subsequent levels of assembly and/or any other operation that renders subsequent inspection impractical,

d) permit identification of components, and

e) permit verification of wire routings.

Recorded video shall include assembly of the Instrument of sufficient detail to be used for future assembly training and possible failure investigation.

Recorded video shall include the packaging, handling, and movement of major Instrument components.

The photos and videos shall be organized in a logical manner (i.e., by timeline, subsystem, etc.).

3.1.9 PM-09: Document Tree

Page 28 of 155 Printed Friday, June 30, 2023

ID

LMXCDRL119

LMXCDRL120

LMXCDRL121

LMXCDRL122

LMXCDRL123

LMXCDRL124

LMXCDRL125

LMXCDRL126

LMXCDRL127

LMXCDRL128

Object Number

3.1.9.0-1

3.1.9.0-2

3.1.9.0-3

3.1.9.0-4

3.1.9.0-5

3.1.10

3.1.10.0-1

3.1.10.0-2

3.2

3.2.1

418-XO-LMXCDRL-0068, RM Version, Geostationary eXtended Observations (GeoXO) Lightning Mapper (LMX) Contract Data

Requirements List (CDRL) Phase B

DATA ITEM DESCRIPTION

1. CDRL No.: PM-09

2. Title: DOCUMENT TREE

3. Use: For ready reference list of all Instrument and GSE documents.

4. Preparation Information:

The Document Tree shall list all documents for the Instrument.

The Document Tree shall be organized and identified to serve as a ready reference list.

The Document Tree shall identify documents by name and number.

The Document Tree shall include a brief description defining the scope of each document.

3.1.10 PM-10: Engineering Design Unit (EDU), Prototype, and

Engineering Development Model (EDM) Activities Report

DATA ITEM DESCRIPTION

1. CDRL No.: PM-10

2. Title: ENGINEERING DESGIN UNIT (EDU), PROTOTYPE, AND

ENGINEERING DEVELOPMENT MODEL (EDM) ACTIVITIES

REPORT AND DATA PACKAGE

3. Use: The EDU, Prototype, and EDM activities report provides performance assessment to raise confidence in the Instrument design and minimize risk to Flight Model development.

4. Preparation Information:

The EDM Activities Report shall include a comprehensive performance assessment including, but not limited to:

a) Assessment against the objectives of the EDU, Prototype, and EDM development over the Program lifecycle

b) Assessment against performance requirements in the Performance and Operational Requirements Document (PORD), Unique Instrument Interface Document (UIID) and GeoXO General Interface Requirements Document (GIRD) requirements

c) Trending of key parameters during the EDU, Prototype, and EDM development

d) Risks mitigated

e) Design modifications that need to be implemented for the FMs

f) As built parts and material list, highlighting differences from the FM

g) Lessons learned about integration, Flight Software (FSW), Ground

Software (GSW), and Ground Processing Algorithm (GPA).

3.2 Resource management

3.2.1 RM-01: Earned Value Management (EVM) Plan

Page 29 of 155 Printed Friday, June 30, 2023

ID

LMXCDRL129

LMXCDRL130

LMXCDRL131

LMXCDRL132

LMXCDRL971

LMXCDRL133

LMXCDRL134

LMXCDRL135

Object Number

3.2.1.0-1

3.2.1.0-2

3.2.1.0-3

3.2.1.0-4

3.2.1.0-5

3.2.1.0-6

3.2.2

3.2.2.0-1

418-XO-LMXCDRL-0068, RM Version, Geostationary eXtended Observations (GeoXO) Lightning Mapper (LMX) Contract Data

Requirements List (CDRL) Phase B

DATA ITEM DESCRIPTION

1. CDRL No.: RM-01

2. Title: EARNED VALUE MANAGEMENT (EVM) PLAN

3. Use: To provide a comprehensive description of the Contractor’s plan for utilizing an EVM System (EVMS) that complies with the Electronic Industries Alliance (EIA)-748 guidelines.

4. Preparation Information:

The EVM Plan shall present the Contractor's approach to comply with the EIA-748-D guidelines.

The EVMS description or EVM Plan shall address:

a) Establishing and maintaining the Project Management Baseline (PMB),

b) The processes for changing the PMB through Baseline Change Requests

(BCRs),

c) The processes for conducting variance analysis,

d) Developing ongoing comprehensive estimates at completion,

e) Flowing down requirements to all applicable subcontracts, and

f) Managing technical scope, schedule, cost, and risk.

The EVMS description or EVM Plan shall address the requirements of NASA’s Federal Acquisition Regulation (FAR) Supplement (NFS) 1852.234-2 or Alternate I.