Attachment F - CDRL.pdf

DRAFT

Effective Date: July 14, 2022 418-XO-GXICDRL-0055 Responsible Organization: GeoXO Flight Project/Code 418 DRAFT Version 1.0 with PC-X00113

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

Geostationary eXtended Observations (GeoXO) Flight Project

Imager (GXI) Contract Data Requirements List (GXICDRL)

Signature page

Prepared by:

Sivakumar K. Tadikonda Date GeoXO Flight Project, Systems Engineer NASA GSFC, Code 418

Reviewed by:

Steven W. Bidwell Date GeoXO Flight Project, Mission Systems Engineer NASA GSFC, Code 418

Megan Gorham Date GeoXO Flight Project, Deputy Mission Systems Engineer NASA GSFC, Code 418

Approved by:

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

/GeoXO Flight Project Imager

GXICDRL

418-XO-GXICDRL-0055, RM Version, Geostationary and eXtended Observations (Flight Project) Imager (GXI) Contract Data Requirement List (CDRL)

Version: 0.6 Printed by: hlhedger Printed on: Thursday, July 14, 2022

No filter applied.

No sort applied.

Generated from DOORS 9.7.2.4

DRA

Contents

1 1Introduction

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

1.2 3Applicable Documents

1.3 3Reference Documents

2 4Contract Data Requirements List

3 20Data Item Descriptions

3.1 20Project Management

3.1.1 20PM-01: Project Management Plan

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

3.1.3 23PM-03: Risk Management Plan

3.1.4 25PM-04: Configuration Management Plan

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

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

(PMSR-B)

3.1.7 30PM-07: Spare Parts Plan and List

3.1.8 31PM-08: Digital Image and Video Records

3.1.9 32PM-09: Document Tree

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

3.2 33Resource management

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

3.2.2 34RM-02: Financial Reports

3.2.3 35RM-03: Integrated Program Management Report (IPMR)

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

3.2.5 40RM-05: Contract Integrated Master Schedule (IMS)

3.2.6 47RM-06: Unit Cost Report

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

3.3 49System Review

3.3.1 49SR-01: System Requirements Review (SRR) / System Definition Review (SDR) Data Package

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

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

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

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

Project: GeoXO Flight Project Imager Module: GXICDRL Baseline Version: 0.6

Contents ii

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

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

3.4 71Systems Engineering

3.4.1 71SE 1: Specifications

3.4.1.1 71SE 1-1: Instrument System Specification

3.4.1.2 72SE 1-2: Detailed Design Specifications

3.4.1.3 73SE 1-3: Environmental Verification Specification

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

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

3.4.1.6 76SE 1-6: Drawing Tree

3.4.2 77SE 2: Plans

3.4.2.1 77SE 2-1: Systems Engineering Management Plan

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

3.4.2.3 82SE 2-3: Contamination Control Plan

3.4.2.4 83SE 2-4: FPGA Development Plan

3.4.2.5 85SE 2-5: Electrostatic Discharge Control Plan

3.4.2.6 86SE 2-6: Radiation Effects Control Plan

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

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

3.4.2.9 88SE 2-9: Trend Analysis Plan

3.4.2.10 89SE 2-10: Individual Test Plans

3.4.2.11 90SE 2-11: Life Test Plan

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

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

3.4.3 93SE 3: Procedures

3.4.3.1 93SE 3-1: Test and Calibration Procedures

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

3.4.4 96SE 4: Models, Analyses, and Reports

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

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

3.4.4.3 101SE 4-3: Solid Math Model

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

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

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

3.4.4.7 104SE 4-7: Trend Reports

3.4.4.8 105SE 4-8: Test Reports

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

3.4.4.10 107SE 4-10: System Performance Verification Reports

Contents iii

3.4.4.11 108SE 4-11: INR Design Document

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

3.4.4.13 110SE 4-13: Instrument Pointing System Dynamics and Control Math Model and Report

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

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

3.4.4.16 113SE 4-16: Optical Model and Report

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

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

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

3.4.4.20 116SE 4-20: FPGA Design Data Package

3.4.5 116SE 5: Calibration

3.4.5.1 116SE 5-1: Calibration Plan

3.4.5.2 117SE 5-2: Ground Processing Algorithm Document

3.4.5.3 118SE 5-3: Calibration Data Book

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

3.4.5.5 120SE 5-5: Ground Software Acceptance Plan Input

3.4.5.6 120SE 5-6: Instrument Packetized Data

3.5 121Software

3.5.1 121SW-01: Software Management Plan

3.5.2 123SW-02: Software Maintenance Plan

3.5.3 125SW-03: Software Requirements Specification

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

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

3.5.6 128SW-06: Software Design Document

3.5.7 129SW-07: Software Test Plan

3.5.8 130SW-08: Software Test Procedures

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

3.5.10 132SW-10: Software Test Report

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

3.5.12 134SW-12: Software Delivery Package

3.6 136Integration & Test

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

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

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

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

3.6.5 140I&T-05: Operations Procedures for the Lifting and Handling Fixture and GN2 Purge Cart

Contents iv

3.6.6 141I&T-06: Operations, Test, and Maintenance Manual for Electrical System Test Equipment (ESTE)

3.7 141Operations

3.7.1 141OPS-01: Instrument Telemetry and Command Database

3.7.2 142OPS-02: Instrument Telemetry and Command Handbook

3.7.3 143OPS-03: Instrument Operations Handbook

3.7.4 146OPS-04: Instrument Operations Training Package

3.7.5 147OPS-05: Instrument Operations Configurable Items

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

3.7.7 149OPS-07: Instrument Post Launch Test Reports

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

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

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

3.8 151Mission Assurance

3.8.1 151System Safety and Mission Assurance

3.8.1.1 151MA 1-1: Mission Assurance Implementation Plan and Compliance Matrix

3.8.1.2 153MA 1-2: Active Suppliers List

3.8.2 154Quality Management System

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

3.8.3 156System Safety Deliverables

3.8.3.1 156MA 3-1: System Safety Program Plan

3.8.3.2 156MA 3-2: Safety Requirements Compliance Checklist

3.8.3.3 157MA 3-3: Instrument Safety Assessment Report (ISAR) and Verification Tracking Log (VTL)

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

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

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

3.8.4 162Reliability

3.8.4.1 163MA 4-1: Reliability Program Plan

3.8.4.2 163MA 4-2: Failure Modes Effects and Corrective Analysis (FMECA) and Critical Items List (CIL)

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

3.8.4.4 165MA 4-4: Parts Stress Analysis Report

3.8.4.5 165MA 4-5: Worst Case Analysis Report

3.8.4.6 166MA 4-6: Reliability Assessments and Predictions

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

3.8.5 167Software Assurance

Contents v

3.8.5.1 167MA 5-1: Software Assurance Plan

3.8.6 168Workmanship Standards

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

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

3.8.7 170EEE Parts

3.8.7.1 170MA 7-1: EEE Parts Control Plan

3.8.7.2 171MA 7-2: Master EEE Parts List

3.8.8 173Materials, Processes and Lubrication Requirements

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

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

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

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

3.8.9.1 177MA 11-1: Responses to Alerts

4 178Acronym List

Contents vi

Page 1 of 181 Printed Thursday, July 14, 2022

ID

GXICDRL1

GXICDRL2

GXICDRL3

GXICDRL4

Object Number

1.0-1

1.1

1.1.0-1

418-XO-GXICDRL-0055, RM Version, Geostationary and eXtended Observations (Flight Project) Imager (GXI) Contract Data

Requirement List (CDRL)

1 Introduction

This Contract Data Requirements List (CDRL) document defines the requirements for deliverable Data to be provided by the GeoXO Instrument GXI Contractor.

“Instrument” as referred to in this document applies to GXI. 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

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

Page 2 of 181 Printed Thursday, July 14, 2022

ID

GXICDRL4

GXICDRL1605

GXICDRL5

GXICDRL6

GXICDRL7

GXICDRL8

GXICDRL9

GXICDRL10

GXICDRL11

Object Number

1.1.0-1

1.1.0-2

1.1.0-3

1.1.0-4

1.1.0-5

1.1.0-6

1.1.0-7

1.1.0-8

1.1.0-9

418-XO-GXICDRL-0055, RM Version, Geostationary and eXtended Observations (Flight Project) Imager (GXI) Contract Data

Requirement List (CDRL) 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.

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.

Page 3 of 181 Printed Thursday, July 14, 2022

ID

GXICDRL12

GXICDRL13

GXICDRL14

GXICDRL15

GXICDRL16

Object Number

1.1.0-10

1.2

1.2.0-1

1.3

1.3.0-1

418-XO-GXICDRL-0055, RM Version, Geostationary and eXtended Observations (Flight Project) Imager (GXI) Contract Data

Requirement List (CDRL)

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 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 20 of 181 Printed Thursday, July 14, 2022

ID

GXICDRL19

GXICDRL20

GXICDRL21

GXICDRL22

GXICDRL23

GXICDRL24

GXICDRL25

GXICDRL26

GXICDRL27

GXICDRL28

GXICDRL29

GXICDRL30

GXICDRL31

GXICDRL32

GXICDRL33

GXICDRL34

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

3.1.1.0-12

3.1.1.0-13

418-XO-GXICDRL-0055, RM Version, Geostationary and eXtended Observations (Flight Project) Imager (GXI) Contract Data

Requirement List (CDRL)

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.

Page 21 of 181 Printed Thursday, July 14, 2022

ID

GXICDRL35

GXICDRL36

GXICDRL37

GXICDRL39

GXICDRL40

GXICDRL41

GXICDRL42

GXICDRL43

GXICDRL44

GXICDRL45

GXICDRL46

Object Number

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

3.1.1.0-23

3.1.1.0-24

418-XO-GXICDRL-0055, RM Version, Geostationary and eXtended Observations (Flight Project) Imager (GXI) Contract Data

Requirement List (CDRL)

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.

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.

Page 22 of 181 Printed Thursday, July 14, 2022

ID

GXICDRL47

GXICDRL48

GXICDRL49

GXICDRL50

GXICDRL51

GXICDRL52

GXICDRL53

GXICDRL54

GXICDRL55

GXICDRL56

GXICDRL57

GXICDRL58

GXICDRL59

GXICDRL60

GXICDRL61

GXICDRL62

GXICDRL63

GXICDRL64

GXICDRL65

Object Number

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.1.0-33

3.1.1.0-34

3.1.1.0-35

3.1.1.0-36

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

3.1.2.0-6

418-XO-GXICDRL-0055, RM Version, Geostationary and eXtended Observations (Flight Project) Imager (GXI) Contract Data

Requirement List (CDRL)

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

Schedule

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

Page 23 of 181 Printed Thursday, July 14, 2022

ID

GXICDRL66

GXICDRL67

GXICDRL68

GXICDRL69

GXICDRL70

GXICDRL71

GXICDRL72

GXICDRL73

GXICDRL74

GXICDRL75

GXICDRL76

GXICDRL77

GXICDRL78

GXICDRL79

GXICDRL80

GXICDRL81

GXICDRL82

Object Number

3.1.2.0-7

3.1.2.0-8

3.1.2.0-9

3.1.2.0-10

3.1.2.0-11

3.1.2.0-12

3.1.2.0-13

3.1.2.0-14

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

3.1.3.0-7

3.1.3.0-8

418-XO-GXICDRL-0055, RM Version, Geostationary and eXtended Observations (Flight Project) Imager (GXI) Contract Data

Requirement List (CDRL)

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.

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 Contractor shall prepare and update a Risk Management Plan.

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.

Page 24 of 181 Printed Thursday, July 14, 2022

ID

GXICDRL83

GXICDRL84

GXICDRL85

GXICDRL86

GXICDRL87

GXICDRL88

Object Number

3.1.3.0-9

3.1.3.0-10

3.1.3.0-11

3.1.3.0-12

3.1.3.0-13

3.1.3.0-14

418-XO-GXICDRL-0055, RM Version, Geostationary and eXtended Observations (Flight Project) Imager (GXI) Contract Data

Requirement List (CDRL)

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.), COTS, 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.

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

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, Risk Management

2. NPR 8000.4B, Risk Management Procedural Requirements

Page 25 of 181 Printed Thursday, July 14, 2022

ID

GXICDRL89

GXICDRL90

GXICDRL91

GXICDRL92

GXICDRL93

GXICDRL94

GXICDRL95

GXICDRL96

GXICDRL97

GXICDRL98

Object Number

3.1.3.0-15

3.1.4

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.4.0-6

3.1.4.0-7

3.1.4.0-8

418-XO-GXICDRL-0055, RM Version, Geostationary and eXtended Observations (Flight Project) Imager (GXI) Contract Data

Requirement List (CDRL)

3.1.4 PM-04: Configuration Management Plan

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 throughout the applicable phases of the product’s life cycle.

Page 26 of 181 Printed Thursday, July 14, 2022

ID

GXICDRL99

GXICDRL100

GXICDRL101

GXICDRL102

GXICDRL103

GXICDRL104

GXICDRL105

GXICDRL106

GXICDRL107

GXICDRL108

GXICDRL109

Object Number

3.1.4.0-9

3.1.5

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.5.0-9

418-XO-GXICDRL-0055, RM Version, Geostationary and eXtended Observations (Flight Project) Imager (GXI) Contract Data

Requirement List (CDRL)

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

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.

Page 27 of 181 Printed Thursday, July 14, 2022

ID

GXICDRL110

GXICDRL111

GXICDRL1623

GXICDRL112

GXICDRL113

GXICDRL114

GXICDRL115

GXICDRL116

GXICDRL118

GXICDRL119

GXICDRL120

Object Number

3.1.5.0-10

3.1.5.0-11

3.1.5.0-12

3.1.6

3.1.6.0-1

3.1.6.0-2

3.1.6.0-3

3.1.6.0-4

3.1.6.0-5

3.1.6.0-6

3.1.6.0-7

418-XO-GXICDRL-0055, RM Version, Geostationary and eXtended Observations (Flight Project) Imager (GXI) Contract Data

Requirement List (CDRL)

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

Page 28 of 181 Printed Thursday, July 14, 2022

ID

GXICDRL120

Object Number

3.1.6.0-7

418-XO-GXICDRL-0055, RM Version, Geostationary and eXtended Observations (Flight Project) Imager (GXI) Contract Data

Requirement List (CDRL)

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

Page 29 of 181 Printed Thursday, July 14, 2022

ID

GXICDRL120

GXICDRL121

GXICDRL122

Object Number

3.1.6.0-7

3.1.6.0-8

3.1.6.0-9

418-XO-GXICDRL-0055, RM Version, Geostationary and eXtended Observations (Flight Project) Imager (GXI) Contract Data

Requirement List (CDRL)

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

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

Page 30 of 181 Printed Thursday, July 14, 2022

ID

GXICDRL122

GXICDRL123

GXICDRL124

GXICDRL125

GXICDRL126

GXICDRL127

GXICDRL128

GXICDRL129

GXICDRL130

GXICDRL131

GXICDRL132

GXICDRL133

Object Number

3.1.6.0-9

3.1.6.0-10

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.7.0-9

418-XO-GXICDRL-0055, RM Version, Geostationary and eXtended Observations (Flight Project) Imager (GXI) Contract Data

Requirement List (CDRL) 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

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 may cause schedule problems if out of stock.

Page 31 of 181 Printed Thursday, July 14, 2022

ID

GXICDRL134

GXICDRL135

GXICDRL1606

GXICDRL136

GXICDRL137

GXICDRL138

GXICDRL139

GXICDRL140

GXICDRL141

GXICDRL142

GXICDRL143

GXICDRL144

GXICDRL145

GXICDRL146

GXICDRL147

GXICDRL148

Object Number

3.1.7.0-10

3.1.7.0-11

3.1.7.0-12

3.1.8

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

418-XO-GXICDRL-0055, RM Version, Geostationary and eXtended Observations (Flight Project) Imager (GXI) Contract Data

Requirement List (CDRL)

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

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

Page 32 of 181 Printed Thursday, July 14, 2022

ID

GXICDRL149

GXICDRL150

GXICDRL152

GXICDRL153

GXICDRL1631

GXICDRL154

GXICDRL155

GXICDRL156

GXICDRL157

GXICDRL158

GXICDRL159

GXICDRL160

GXICDRL161

GXICDRL162

GXICDRL163

GXICDRL164

GXICDRL165

GXICDRL166

Object Number

3.1.8.0-13

3.1.8.0-14

3.1.8.0-15

3.1.8.0-16

3.1.8.0-17

3.1.9

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.9.0-6

3.1.9.0-7

3.1.9.0-8

3.1.9.0-9

3.1.10

3.1.10.0-1

3.1.10.0-2

418-XO-GXICDRL-0055, RM Version, Geostationary and eXtended Observations (Flight Project) Imager (GXI) Contract Data

Requirement List (CDRL)

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 of components, and

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

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

Page 33 of 181 Printed Thursday, July 14, 2022

ID

GXICDRL167

GXICDRL168

GXICDRL169

GXICDRL170

GXICDRL172

GXICDRL173

GXICDRL174

GXICDRL175

GXICDRL176

GXICDRL177

GXICDRL178

GXICDRL179

GXICDRL180

Object Number

3.1.10.0-3

3.1.10.0-4

3.1.10.0-5

3.1.10.0-6

3.2

3.2.1

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

418-XO-GXICDRL-0055, RM Version, Geostationary and eXtended Observations (Flight Project) Imager (GXI) Contract Data

Requirement List (CDRL)

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 PORD, UIID and 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 build 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

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 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) the processes to determine and implement solutions to resolve the causes of variances,

e) Developing ongoing comprehensive estimates at completion,

f) Flowing down requirements to all applicable subcontracts, and

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

Page 34 of 181 Printed Thursday, July 14, 2022

ID

GXICDRL181

GXICDRL182

GXICDRL183

GXICDRL184

GXICDRL185

GXICDRL186

GXICDRL187

GXICDRL188

GXICDRL189

GXICDRL190

GXICDRL191

GXICDRL192

Object Number

3.2.1.0-8

3.2.1.0-9

3.2.1.0-10

3.2.2

3.2.2.0-1

3.2.2.0-2

3.2.2.0-3

3.2.2.0-4

3.2.2.0-5

3.2.2.0-6

3.2.2.0-7

3.2.2.0-8

418-XO-GXICDRL-0055, RM Version, Geostationary and eXtended Observations (Flight Project) Imager (GXI) Contract Data

Requirement List (CDRL)

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

Guidelines are available in the Earned Value Management Systems EIA-748-C Intent Guide Appendix Compliance Map Template.

FORMAT: Contractor-selected formats are acceptable.

APPLICABLE DOCUMENTS:

1) Industry Guidelines for Earned Value Management Systems, EIA-748

2) Earned Value Management System, NFS 1852.234-2 (or Alternate I)

3) Earned Value Management Systems EIA-748 Intent Guide Appendix Compliance Map Template

3.2.2 RM-02: Financial Reports

DATA ITEM DESCRIPTION

1. CDRL No.: RM-02

2. Title: FINANCIAL REPORTS

3. Use: To provide data necessary for:

a. Projecting costs and hours to ensure that cost and labor resources realistically support the Project and its schedules,

b. Evaluating Contractor’s actual cost and fee data in relation to negotiated contract value, estimated costs, and budget forecast data,

c. Planning, monitoring, and controlling Project resources, and

d. Accruing cost in NASA’s accounting system.

4. Preparation Information:

The Contractor shall submit Financial Reports on NASA’s 533 series reports, in accordance with the instructions on the reverse of the forms, NASA Procedural Requirements (NPR) 9501.2, NASA Contractor Financial Management Reporting (current version), and additional instructions issued by the contracting officer.

The…