Updated Attachment F - OCX CDRL.pdf

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

Effective Date: 418-XO-OCXCDRL-0063 Responsible Organization: GeoXO Flight Project/Code 418 DRAFT Version 0.0

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

Approved by:

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

/GeoXO Flight Project OCX

OCXCDRL

418-XO-OCXCDRL-0063, RM Version, Geostationary eXtended Observations ( O) Ocean Color (OCX) Contract Data Requirements List (CDRL) Phase B

Version:

Printe y: rkhoover Pri d on: Friday, July 7, 2

No filter ed.

No sort applie

Generated from DOORS 9.7.2.4

DRAFT

Contents

1 1Introduction

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

1.2 3Applicable Documents

1.3 3Reference Documents

2 4Contract Data Requirements List

3 15Data Item Descriptions

3.1 15Project Management

3.1.1 15PM-01: Project Management Plan

3.1.2 17PM-02: Weekly Status Reports and Telecon Mi s

3.1.3 18PM-03: Risk Management Plan

3.1.4 19PM-04: Configuration Man nt Plan

3.1.5 20PM-05: Configuration Chan Requ eviations, and W s

3.1.6 21PM-06: Project Managemen atus Review nical (PMSR -T), Business

(PMSR-B)

3.1.7 24PM-07: Spare Parts Plan and Li

3.1.8 25PM-08 g ge and Video ords

3.1.9 26PM : Document ee

3.1.10 26M-10: Engineer Design Unit (ED Prototype, and Engineering Development Model (EDM) A ties Report

3.2 27ource m gement

3.2.1 27RM ned Value Management (EVM) Plan

28RM-02: ncial Reports

3.2.3 29M-03: Inte ed Program Management Report (IPMR)

3.2.4 32R 4: Contrac ork Breakdown Structure (CWBS) and CWBS Dictionary

3.2.5 33RM Contract Integrated Master Schedule (IMS)

3.2.6 40RM Unit Cost Report

3.2.7 40RM : Integrated Baseline Review (IBR) Package

3.3 42stem Review 3 43SR-01: System Requirements Review (SRR) / System Definition Review (SDR)

Data Package

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

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

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

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

Project: GeoXO Flight Project OCX Module: OCXCDRL Baseline Version: 0.4

Contents ii

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

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

3.4 64Systems Engineering

3.4.1 64SE 1: Specifications

3.4.1.1 64SE 1-1: Instrument System Specification

3.4.1.2 65SE 1-2: RESERVED

3.4.1.3 65SE 1-3: RESERVED

3.4.1.4 65SE 1-4: Instrument Electrical Block Diagrams and Approve Controlle

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

3.4.1.6 68SE 1-6: Drawing Tree

3.4.2 68SE 2: Plans

3.4.2.1 68SE 2-1: Systems Engineering Management n

3.4.2.2 70SE 2-2: System Performance Verification P nd Compli

3.4.2.3 72SE 2-3: Contamination Control Plan

3.4.2.4 74SE 2-4: RESERVED

3.4.2.5 74SE 2-5: Electrostatic Disch Control Plan

3.4.2.6 74SE 2-6: RESERVED

3.4.2.7 74SE 2-7: EMC/EMI Compatibi Plan

3.4.2.8 75SE 2-8: On-Orbit Electro-Stati scharg ontrol Pla

3.4.2.9 75SE 2-9: Tre d Analysis Plan

3.4.2.10 76SE 2- Individ Test Plans

3.4.2.11 77S 11: Life Test n

3.4.2.12 78E 2-12: Image N igation and Regis ion (INR) Modeling and Analysis Plan

3.4.2.13 79E 2-13: Eng t and Test Plan

3.4.3 80SE Pro ures 3 1 80SE 3-1 st and Calibration Procedures

3.4.3.2 82SE 3-2: In ment Assembly and Integration Procedures/Drawings

3.4.4 82 4: Models, lyses, and Reports

3.4.4.1 82SE : Mass Properties and Power Report

3.4.4.2 83SE Thermal Math Models and Reports

3.4.4.3 87SE : Solid Math Model

4 4.4 87S -4: Structural Math Model and Reports

3. 5 88SE 4-5: Radiation Shielding and Dose Analysis Report

3.4.4. 89SE 4-6: Engineering Analysis Reports (EAR)

3.4.4.7 90SE 4-7: Trend Reports

3.4.4.8 90SE 4-8: Test Reports

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

3.4.4.10 93SE 4-10: System Performance Verification Reports

Project: GeoXO Flight Project OCX Module: OCXCDRL Baseline Version: 0.4

Contents iii

3.4.4.11 93SE 4-11: INR Design Document

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

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

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

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

3.4.4.16 97SE 4-16: Optical Model and Report

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

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

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

3.4.4.20 100SE 4-20: FPGA Design Data Package

3.4.5 101SE 5: Calibration

3.4.5.1 101SE 5-1: Calibration Plan

3.4.5.2 101SE 5-2: Ground Processing Algorithm Doc t

3.4.5.3 102SE 5-3: Calibration Data Book

3.4.5.4 103SE 5-4: Ground Processing Algorithms Test and Va ion Plan

3.4.5.5 104SE 5-5: Ground System S Acceptance Plan Inp

3.4.5.6 104SE 5-6: Instrument Packet d Dat

3.4.5.7 105SE 5-7: Visualization Algorit Document

3.4.5.8 106SE 5-8: Visualization Algorithm est and idation P

3.5 106Software

3.5.1 106SW-0 oftwar nagement Pl

3.5.2 108S 2: Software ntenance Plan

3.5.3 110W-03: Software quirements Spec tion

3.5.4 111W-04: Softw i n Review (SWPDR) Data Package

3.5.5 113S : S ware Critical Design Review (SWCDR) Data Package 3 6 113SW-06 ftware Design Document

3.5.7 114SW-07: So re Test Plan

3.5.8 11608: Softw Test Procedures

3.5.9 116SW : Software Test Readiness Review (SWTRR) Data Package

3.5.10 117SW Software Test Report

3.5.11 118SW : Software Acceptance Review (SWAR) Data Package

5.12 118S 12: Software Delivery Package 120ntegration & Test

3.6. 120I&T-01: Transportation and Handling Plan and Procedures

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

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

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

3.6.5 124RESERVED

Project: GeoXO Flight Project OCX Module: OCXCDRL Baseline Version: 0.4

Contents iv

3.6.6 124RESERVED

3.7 124Operations

3.7.1 124OPS-01: Instrument Telemetry and Command Database

3.7.2 125OPS-02: Instrument Telemetry and Command Handbook

3.7.3 126OPS-03: Instrument Operations Handbook

3.7.4 128OPS-04: Instrument Operations Training Package

3.7.5 129OPS-05: Instrument Operations Configurable Items

3.7.6 129OPS-06: Instrument Post-Launch Test Plan and Procedure

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

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

3.7.9 131SIM-01: Operations, Test, and Maintenance M al for the Instrument Hardware

Simulator

3.7.10 132SIM-02: Operations, Test, and Maintenan Manual for the rument Software

Simulator

3.8 132Mission Assurance

3.8.1 132System Safety and Mission Assurance

3.8.1.1 132MA 1-1: Mission Assuran C nce Matrix

3.8.1.2 133MA 1-2: Suppliers List

3.8.2 134Quality Management System

3.8.2.1 134MA 2-1: Non-Conformance Rep - Ma al Review Bo rd (MRB) and Failure

Review Bo d (FRB)

3.8.3 135Syste afety D erables

3.8.3.1 135M -1: System S y Program Pla

3.8.3.2 136MA 3-2: Safety R uirements Compli e Checklist

3.8.3.3 136A 3-3: Instr ment Report (ISAR) and Verification Tracking

L (VTL)

3.8.3.4 137MA 3 perations Hazard Analysis and Verification Tracking Log

139MA 3-5: rdous Procedures for Payload I&T and Pre-launch Processing

3.8.3.6 139 3-6: Pre ap Plan and Mishap Reports

3.8.4 141R bility

3.8.4.1 141MA : Reliability Program Plan

3.8.4.2 141MA : Failure Modes Effects and Criticality Analysis (FMECA) and Critical Items

Lis IL)

4.3 142 4-3: Fault Tree Analysis (FTA) Report

3.8 143MA 4-4: Parts Stress Analysis Report

3.8.4.5 143MA 4-5: Worst Case Analysis Report

3.8.4.6 144MA 4-6: Reliability Assessments and Predictions

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

3.8.5 145Software Assurance

3.8.5.1 145MA 5-1: Software Assurance Plan

Project: GeoXO Flight Project OCX Module: OCXCDRL Baseline Version: 0.4

Contents v

3.8.6 146Workmanship Standards

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

3.8.6.2 147MA 6-2: Printed Circuit Board (PCB) Coupon Evaluation Reports and Lot

Acceptance and Quality Conformance Testing Results for Printed Circuit Boards

3.8.7 148EEE Parts

3.8.7.1 148MA 7-1: EEE Parts Control Plan

3.8.7.2 149MA 7-2: Master EEE Parts List

3.8.8 150Materials, Processes and Lubrication Requirements

3.8.8.1 150MA 8-1: Materials and Processes Selection, Control, and Implementation Pl

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

3.8.8.3 153MA 8-3: Materials Identification and Usage List UL)

3.8.9 154Government-Industry Data Exchange Progr (GIDEP) Alerts and Problem Advisories

3.8.9.1 154MA 11-1: Responses to Alerts

4 155Acronym List

Project: GeoXO Flight Project OCX Module: OCXCDRL Baseline Version: 0.4

Contents vi

Project: GeoXO Flight Project OCX Module: OCXCDRL Baseline Version: 0.4

Page 1 of 158 Printed Friday, July 7, 2023

ID

OCXCDRL1

OCXCDRL2

OCXCDRL3

Object Number

1.0-1

1.1

418-XO-OCXCDRL-0063, RM Version, Geostationary eXtended Observations (GeoXO) Ocean Color (OCX) Contract Data

Requirements List (CDRL) Phase B

1 Introduction This Contract Data Requirements List (CDRL) document defines requirements for deliverable Data to be provided by the Geostationary eXtend bservations (GeoXO) Instrument Contractor. “Instrument” as referred to in this ent applies to the GeoXO Ocean Color (OCX). Section 1.1 includes definiti and ructions for distribution. Section 2 presents the CDRL item by item th due d Section 3.0 provides the Data Item Description (DID), a descripti n of each item d describes use, and Preparation Information.

1.1 Definition of Due Dates/Ma ity, Definition of Categ es, and Delivery Instructions

Page 2 of 158 Printed Friday, July 7, 2023

ID

OCXCDRL4

OCXCDRL5

OCXCDRL6

Object Number

1.1.0-1

1.1.0-2

1.1.0-3

418-XO-OCXCDRL-0063, RM Version, Geostationary eXtended Observations (GeoXO) Ocean Color (OCX) 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 propos

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

3) As Generated. After each initial edition, re on, add etc.

4) As Directed. Per direction by the CO.

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

6) Weekly. With weekly status re s by Monday 12 noon ET or a dified by CO.

7) L. Launch Date.

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

9) NLT: No Later Than

10) ATP: Authorization to Proceed

b) MATURITY:

1) Prelimin ry: The first submission item. Applies to milestone deliver ompleted with avail information as of the time of prepara for t date.

2) Initial: T first subm f an item for eliveries that are periodic – weekly, m hly, etc. To up d with available information as of the time of prep tion fo e due date

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

Final: The com e thorough submission of an item. This does not eclude updati ater.

c) NAS cceptance Co

A proval: Docum s in this category require approval by the Goddard pace Flight Center SFC) Contracting Officer’s Representative (COR) by the Contractor.

Review ents 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 nformation: 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 158 Printed Friday, July 7, 2023

ID

OCXCDRL7

OCXCDRL8

OCXCDRL9

OCXCDRL10

OCXCDRL11

OCXCDRL12

OCXCDRL13

OCXCD 4

O DRL15

O DRL16

OCXCD 7

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-OCXCDRL-0063, RM Version, Geostationary eXtended Observations (GeoXO) Ocean Color (OCX) 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 su issions.

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

Requirements for re-submission of “Approval” coded ms shall b specified in the letters of disapproval. For most cases, the Contractor will be required submit the document within 30 days of receiving commen om the Government.

If the Contractor has not received respon rom GSFC within 30 days of deli of an “Approval” coded CDRL item (15 days test procedures), the Contractor may p ceed as if the document has been approv

When Government evaluations of “Re ” coded ms reveal inadequacies, the Contractor shall correct the documents n 3 ays of receiving comments or provide a plan approved by the Governmen closing deficiencies.

All Data items shall d livered in electronic fo to the GeoXO portal unless otherwise noted in C Data Requirement in Section 2 of this document.

Electronic deliverables all be deliv the following formats unless otherwise approved by the Gover ent:

a) Text Documen PDF ( chable) or Word.

b) Presentations: F ( chable) or PowerPoint.

readsheets: M oft Excel.

d) D base: Unless cified otherwise, delimited ASCII files accompanied with d ase schema d ment defining tables and entries.

e) S dules: MS Proje ompatible.

f) hematics and Draw s: PDF.

g) JPEG or current industry standard.

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

) System Specifications in Direct Object-Oriented Requirements System

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

1.2 plicable Documents

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

.3 Reference Documents he following documents contain information relating to the work required but which do not constitute requirements:DRAFT

Page 15 of 158 Printed Friday, July 7, 2023

ID

OCXCDRL20

OCXCDRL21

OCXCDRL22

OCXCDRL23

OCXCDRL933

OCXCDRL24

OCXCDRL25

OCXCDRL26

OCXCDRL27

OCXCDRL28

O CDRL29

OCXCDRL3

OCXCDRL31

OCXCDRL32

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-OCXCDRL-0063, RM Version, Geostationary eXtended Observations (GeoXO) Ocean Color (OCX) 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 MANAGEMEN PLAN

3. Use: Describes how the P ct is organized and manag It provides the man ment structure, its system of op ion, responsible lin communications, and key personne assignments

4. Preparation Information:

General

The Project Management Plan shall ad s the overall organization, management a roach, and structure of Program plus its interrelationships with the pare c y and the Subcontra and relationship with the Government.

The Project Man ment Plan s interfaces with the Government and with any Governm Furnish Equipm GFE) suppliers.

Project Manage lan shall delineate how the requirements of the Sta nt of Work (S W) will be achieved and include a description of planned activi for identifiabl OW requirements.

The P ect Managemen n shall describe the concept of the nature of the ks and related pote tial problems. Discuss the approach to problem n.

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

The P oject 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 16 of 158 Printed Friday, July 7, 2023

ID

OCXCDRL33

OCXCDRL34

OCXCDRL35

OCXCDRL36

OCXCDRL37

OCXCDR

OC RL39

OCXCDRL4

OCXCDRL41

OCXCDRL42

OCXCDRL43

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 7

3.1.1.0-18

3.1.1.0-19

3.1.1.0-21

3.1.1.0-22

418-XO-OCXCDRL-0063, RM Version, Geostationary eXtended Observations (GeoXO) Ocean Color (OCX) 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 du their criticality or development risk.

The Project Management Plan shall provide contract rocedures proposed for the Project to effect administrative an ng ring changes, describing any differences from existin ocedur

The Project Management Plan shall describe how and where th program will operate during all phases o e contract.

Organization

The Project Management Plan all provide an o nizational chart(s) and sufficient supplemental n tive to describ ully the organization proposed for carrying out the Pr t showi nter- relationships of technical management, business m ge nt, and subcontract management, from lower level throug ermediate management to top-level management with detailed exp tion of:

a) How whom interdepartmen work will be monitored and the a ority program manage r interdepartmental work.

b) Process e followed th m manager in obtaining decisions ond hi er authority nd in resolving priority conflicts fo o es and functions not under the program manager’s d control such as personnel, finances, and facilities.

c) he authority of Program Manager relative to other ongoing programs and ap able support organizations within the structure.

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

he Project Management Plan shall discuss the availability of the technical, manufacturing and system safety/quality assurance/ reliability/ con ration 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 17 of 158 Printed Friday, July 7, 2023

ID

OCXCDRL44

OCXCDRL45

OCXCDRL46

OCXCDRL47

OCXCDRL48

OCXCDRL49

OCXCDRL50

OCXCDRL51

OCXCDRL52

OCXCDRL53

OCXCDRL54

OCXCDRL55

OCXCDRL

OCXCDRL57

OCXCDRL58

OCXCDRL59

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

3.1.2.0-5

418-XO-OCXCDRL-0063, RM Version, Geostationary eXtended Observations (GeoXO) Ocean Color (OCX) 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 th hedule administration/control.

The Project Management Plan shall explain the rnal re w cycle of the scheduling process.

The Project Management Plan shall expl how subcontract sche s are maintained and reported in the maste hedule.

The Project Management Plan sh explain how internal audits/reviews ensure that scheduling data r ted to the Gove ment accurately reflects the work status.

Knowledge Management

The Project Management Plan shall de e how lessons learned from Instrument de ment, integration, and will be captured.

The Project M gemen shall describe h raining will be performed to convey lessons rned as the to the devel pment, integration, and test of future flight mod

The Project Manag nt n shall describe how lessons learned will be ed and applie ubcontractor development of critical subassemblies and asse es.

The P ect Managemen an shall describe the overall training plan for project pers el.

3.1.2 M 02: Status Reports and Telecon Minutes

DATA ITEM DESCRIPTION

1. CDRL No.: PM-02

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 18 of 158 Printed Friday, July 7, 2023

ID

OCXCDRL60

OCXCDRL61

OCXCDRL62

OCXCDRL63

OCXCDRL934

OCXCDRL64

OCXCDRL65

OCXCDRL67

OCXCDRL68

OCXCDR

OCXCDRL70

OCXCDRL71

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

3.1.3.0-3

3.1.3

3 5

3.1.3.0-6

418-XO-OCXCDRL-0063, RM Version, Geostationary eXtended Observations (GeoXO) Ocean Color (OCX) 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 minute the previous week's weekly telecon and all technical meetings.

The Weekly Status Report shall contain Action I Statu d contain telecon minutes from the previous week's weekly tele

The Weekly Status Report shall contain us of any open Non-C rmance Reports.

The Weekly Status Report shall tain status on any open contract actio including Special Engineering lyses/Task Orde

3.1.3 PM-03: Risk Managem t Plan

DATA ITEM DESCRIPTION

1. CDRL No.: PM-03

2. Title: ISK MANAGEMENT PLA MP)

3. Use: T k Management Plan he basis for identifying and manag erformance, re ity, schedule, cost, and afety risks o ntractor’s Project. The identification, aracteriz n, m plan, and mitigation responsibilities ociate with specific ri ks are described and specific risk a e nt strategies or contingency planning processes are dis ed. “Risk” refers to anything that can prevent a team from eeting the Delivery Order objectives.

4. P aration Inform on:

The k Management Pla hall describe Contractor’s process for Risk I Analysis, Risk Handling and Risk Monitoring.

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

e Risk Management Plan shall clearly describe:

) Overview of the risk management process.

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 19 of 158 Printed Friday, July 7, 2023

ID

OCXCDRL72

OCXCDRL73

OCXCDRL935

OCXCDRL970

OC RL74

CDRL75

OCXCDRL76

OCXCDRL77

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

3.1.4.0-1

3.1.4.0-2

3.1.4.0-3

418-XO-OCXCDRL-0063, RM Version, Geostationary eXtended Observations (GeoXO) Ocean Color (OCX) Contract Data

Requirements List (CDRL) Phase B

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

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

Reference:

1. GPR 7120.4D, Risk Management

2. NPR 8000.4C, Risk Management cedural Requirements

Likelihood

5 Very High

4 High

3 Moderate

2 Low

1 Very Low

Safety Technical chedule Estimated likelihood of not meeting performanc requirements

Estimated likelihood of Safety event occurrence d likelihood meeting cost or edule commitment

Con gories

LOW RISK

MODERATE

RISK

HIGH RISK

Risk

Safety

1 Very Low 2 Low 3 M 4 High 5 Very High

Technica

Schedule t

Negligible or not impact use the n only mi aid trea

May c inju o nal illness or property mage vere occup ness or major property damage.

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

o impact to full ion success a

Minor im mission su criteria

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

Minimum mission success criteria is not achievable

Major impact to full mission success criteria. Minimum mission success criteria is achievable ble or no ule impact

Minor impact to schedule milestone accommodates with reserves; no impact t critical path pact to schedule stones;

mmodates within ves; moderate mpact to critical path

Major impact to schedule milestones; major impact to critical path

Cannot meet schedule and program milestones

<2% increa allocated and negligible impact on reserve incr 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

(PSE > 10-1)

(10-2 < PSE = 10-1)

(10-3 < PSE = 10-2)

(10-5 < PSE = 10-3)

(PT > 50

(25% < PT = 50%)

(15% < PT = 25%)

(2% < PT = 15%)

(0 1% < PT = 2%)

(PCS > 75%)

PCS = 75%

(25

(2% < PCS = 1 (10-6 < PSE

(10% < P %)

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

Page 20 of 158 Printed Friday, July 7, 2023

ID

OCXCDRL78

OCXCDRL79

OCXCDRL80

OCXCDRL81

OCX L82

OCXCDRL83

OCXCDRL84

Object Number

3.1.4.0-4

3.1.4.0-5

3.1.5

3.1.5.0

3.1.5.0-2

5.0

3.1 0-4

418-XO-OCXCDRL-0063, RM Version, Geostationary eXtended Observations (GeoXO) Ocean Color (OCX) Contract Data

Requirements List (CDRL) Phase B

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

a) Accomplish hardware and software configuratio anagement,

b) Achieve consistency between product definiti the product’s configuration, and the configuration mana ent records, and

c) Maintain configuration management th gh he applicable phases of the product’s life cycle.

The Configuration Management Plan sh ll describe the Contr ’s approach, methodology, and application of confi ation management prin and practices, including:

a) General product definiti and scope.

b) Description of config ion management activities and procedu es for each of the follow configuration m gement functions:

1) Configuration nning and m agement.

2) Configuration id ficatio

3) Configuration Chan agement.

4) Configuration status unting.

5) Configuration verificatio d audit.

uration managemen digital data.

7 Config n management o ftware.

c) Org ation, role nsibilities, an resources.

d) Defin n of terms

e) Progra atic an ganizati nterfaces.

f) Subcon t fl down of configuration management.

1.5 PM 05: Config ation Change Requests, Deviations, and

Wa ers

DAT TEM DESCRIPT N

1 D PM-05

Title: IGURATION 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.

Page 21 of 158 Printed Friday, July 7, 2023

ID

OCXCDRL85

OCXCDRL86

OCXCDRL87

OCXCDRL88

OCXCDRL89

OCXCDRL90

OCXCDRL9

OCXCDRL92

Object Number

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

3.1.6.0-2

3.1.6.0-3

418-XO-OCXCDRL-0063, RM Version, Geostationary eXtended Observations (GeoXO) Ocean Color (OCX) Contract Data

Requirements List (CDRL) Phase B

A Class I CCR is a change that:

a) Affects any Government Contract requirement, specif ion, or interface requirement.

b) Affects schedules of end item deliverables to th vernment.

c) Impacts Government Furnished Equipment.

d) Affects configuration to the extent that ch es ld be required to prior deliverables in order to maintain s fied per ance.

e) Creates a new Single Point Failure pos ility.

A change may be classified Class II whe does not fall within the nition of a Class I change as given above. Exam s of Class II changes are:

a) A change in documentatio nly (for example, correction of erro addition or clarifying no or views).

b) A minor change in h are (for exampl ubstitution with an approved alternative material) w does not a t any item listed under Class I changes.

c) Drawing changes that do n ff a baseline, interface, etc.

Class II change normally do not require ernment Configuration Control Board (CCB) l unless they are writte ainst Government CM-controlled documents.

Waivers and De ons are con CCRs and will follow the CCR approval process.

3.1 PM-06: Proje M nagement Status Reviews – Technical

(P SR -T), Bus ess (PMSR-B)

DATA EM DESCRIP ON

1. RL No.: PM-06

2. le PROJEC MANAGEMENT STATUS REVIEWS – TECHNICAL

R -T) AND BUSINESS (PMSR-B)

. 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

Page 22 of 158 Printed Friday, July 7, 2023

ID

OCXCDRL92

Object Number

3.1.6.0-3

418-XO-OCXCDRL-0063, RM Version, Geostationary eXtended Observations (GeoXO) Ocean Color (OCX) Contract Data

Requirements List (CDRL) Phase B

Parameters will be per mutual agreement with the Government. The parameters presented will be at least to the major co onent level of the subsystems, e.g., Mechanisms, Power supplies aters, cabling, etc.

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

1) Mass (Kg)

2) Operational Peak and Average P er (W)

3) Survival Peak and Average Po r (W)

4) Pointing knowledge and c ntrol error budgets

5) Average Data Rate (Mb

6) Peak Data Rate (Mb

7) Memory Utilizatio

8) CPU Utilization

9) Science met hat are selecte show the satisfaction and stability of the nce perfor nce requirements

10) Accuracy of the s an ts

11) Status of margins a ngency

d) Technical status for system an bsystem design and develo ent activities, including nology maturity efforts for reach g ology Readiness Lev RL) 6 by PDR, and subco ct te performance.

e) Design tus (when work is being accomplished) covering design ac ie previous month, including schedule techni status of d lopment, manufacturing status, qua ati and test status, issues and concerns, and Configuratio nge status:

1) List o ass I in process and approved changes.

2) List of ss II approved Changes available upon request f Summary of Inte ed Master Schedule Status, including a brief i n of the status of each subsystem or subassembly along riptions 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.

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.

Page 23 of 158 Printed Friday, July 7, 2023

ID

OCXCDRL92

OCXCDRL93

OCXCDRL94

Object Number

3.1.6.0-3

6.0

3.1. 0-5

418-XO-OCXCDRL-0063, RM Version, Geostationary eXtended Observations (GeoXO) Ocean Color (OCX) Contract Data

Requirements List (CDRL) Phase B

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

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

q) Status of Master Action Items Database (MAI ction items with focus brought to those actions which are n clo in a timely manner.

r) Identification and status of long-lead p chases/acqu ns planned.

s) Prohibited Materials Complianc atus (as required):

1) GeoXO Product Alert aluation status.

2) Production Readin Issues (as required).

t) Significant plans and a ies for the following month, including upcoming milestone nts depicting cri items of Project status.

u) Contract Status:

1) Summary of curren als, proposal preparations and expected complet dates.

2) Summary of current and cted Configuration Change

R ts (CCRs).

3) Summ otential future p sals and CCRs, luding De and Waivers

v) Summar f Task Ord

1) S s of cu nt task ord and estimated completion da

2) Disc n of impediments to timely completion of tasks.

3) Discu n of potential future tasks.

w DRL Status R rt that includes the following information for ach document vered in accordance with the CDRL or overdue from pre us reporting periods:

Document Number

2) ent 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

Page 24 of 158 Printed Friday, July 7, 2023

ID

OCXCDRL94

OCXCD 5

OCXCDRL96

OCXCDRL97

OCXCDRL98

Object Number

3.1.6.0-5

3.1.6.0-6

3.1.7

3 1

3.1.7.0-2

418-XO-OCXCDRL-0063, RM Version, Geostationary eXtended Observations (GeoXO) Ocean Color (OCX) Contract Data

Requirements List (CDRL) Phase B possible workarounds being considered to maintain the schedule.

A slack metric with at least 1 month of aging (prior m h slack) is to be maintained and provided for major subass lies and activities (the Government and Contractor man s will determine which items are to be tracked at l quarterly).

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

e) Metrics summarizing all milestones dep ting planned us actual accomplishments and expla ations for variances, graphic display of planned vers ctual cumulative milesto status, xx of 1,000 mileston e behind plan and why, etc.

f) Summary explanation of k EVM parameter performance and trends

g) Metrics by Integrate oduct Team (IPT nd Total Project, summarizing Baseline, cast and al Headcounts where a head equals one equivale ork-m th of effort. Include explanation of variance from

h) Review of Management Reser MR) Liens or other unfunded risk mi ations including estimat st and impact

i) Statu of items with focus br t to those actions which are no losing ely manner

j) Busines sues, inclu rsonnel chan es

k) Summar f Contract S u

1) Sum ry of c ent contra unding vs contract cost and Term tio ability requirements

2) Projec f future funding requirements

3) Summa of proposals (Current and in process)

l) ummary of T Orders in a tabular format:

1) Task Orde umber and title

2) Authorized ue iod of Pe formance

4) st 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.

Page 25 of 158 Printed Friday, July 7, 2023

ID

OCXCDRL99

OCXCDRL100

OCXCDRL101

OCXCDRL102

OCXCDRL103

OCXCDRL104

OCXCDRL105

OCXCDRL106

OCXCDRL1

CDRL108

OCXCD 09

OCXCDRL110

OCXCDRL111

Object Number

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

3.1.8.0-1

3.1.8.0-3

3.1.8.0-4

3.1.8.0-6

418-XO-OCXCDRL-0063, RM Version, Geostationary eXtended Observations (GeoXO) Ocean Color (OCX) Contract Data

Requirements List (CDRL) Phase B

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

The Spare Parts Plan shall provide a listing of Spare Pa nd assemblies.

For the purposes of this CDRL, the information sou i parts and assemblies that are not commonly available or those that m ause dule problems if out of stock.

The Spare Parts Plan shall consider the cious definition, procu nt, and stock of a set of these critical spares t elp minimize potential sche impact created by subsystem failures, by c amination, or by other plausible ts or conditions.

The spares may be retained lly assembled rtially assembled or piece part spares. Since the need to use a e may b failure condition in the Instrument and, depending on the cifi f the fault, the spare itself may need rework or repair, simple substitution pare may not be a viable approach.

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

In defining the are par am, the Contra shall consider the reliability, handling, and e onment con f subsystems, components, and parts under considerat for sparin nclu likelihood that these items need to be replaced.

3 08: Digital mage and Video Records

DATA EM DESCRIP ON

1. CD No.: PM-08

2. T DIGITA MAGE AND VIDEO RECORDS

3 P ogram status reviews, system, subsystem, and assembly p aging evaluations, and troubleshooting.

4. Preparation Information:

The Contractor shall produce closeout photographic documentation of all emblies during the manufacturing process and of the final integrated c uration "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.

Page 26 of 158 Printed Friday, July 7, 2023

ID

OCXCDRL112

OCXCDRL113

OCXCDRL114

OCXCDRL115

OCXCDRL116

OCXCDRL117

OCXCDRL937

OCXCDRL118

OCXCDRL119

OCXCDRL1

OCXC L121

O DRL122

OCXCD 23

OCXCDRL124

Object Number

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

3.1.9.0-1

3.1.9.0-

3.1.9.0-4

3.1.9.0-5

1.10

418-XO-OCXCDRL-0063, RM Version, Geostationary eXtended Observations (GeoXO) Ocean Color (OCX) Contract Data

Requirements List (CDRL) Phase B

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

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

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

Images shall include pictures of environment est fixtures.

Images shall be of sufficient resolution t

a) show component placement,

b) show part marking,

c) show details that are co d or obscured at subsequent levels of assembly and/or any er operation tha nders subsequent inspection impractical,

d) permit identification of c onents d

e) permit verification of wire n

Recorded video shall include assembly e Instrument of sufficient detail to be used for futur mbly training and poss failure investigation.

Recorded vide hall inc packaging, ha g, and movement of major Instrument com nents.

The photos and vi s shal e organized a logical manner (i.e., by timeline, subsystem, etc.).

.1.9 PM 9: Docum t Tree

DATA EM DESCRIP N

1. CD L No.: PM-09

2 DOCUMENT TREE

Use: eady reference list of all Instrument and GSE documents.

4. Preparation Information:

The Document Tree shall list all documents for the Instrument.

Document Tree shall be organized and identified to serve as a ready refe ce 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 ReportDRAFT

Page 27 of 158 Printed Friday, July 7, 2023

ID

OCXCDRL125

OCXCDRL126

OCXCDRL127

OCXCDRL128

OCXCDRL129

XCDRL130

OCXCD 31

Object Number

3.1.10.0-1

3.1.10.0-2

3.2

3.2.1

3.2.1.0

3.2.1.0-2

3.2.1.0-3

418-XO-OCXCDRL-0063, RM Version, Geostationary eXtended Observations (GeoXO) Ocean Color (OCX) Contract Data

Requirements List (CDRL) Phase B

DATA ITEM DESCRIPTION

1. CDRL No.: PM-10

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

ENGINEERING DEVELOPMENT MODEL DM) ACTIVITIES

REPORT AND DATA PACKAGE

3. Use: The EDU, Prototype, and EDM a ti port provides performance assessment to r confide in the Instrument design and minimize risk to ght Model de pment.

4. Preparation Information:

The EDM Activities Report shall inclu a comprehensive performanc assessment including, but not limit o:

a) Assessment against the ectives of the EDU, Prototype, and EDM development over th ogram lifecycle

b) Assessment against p mance requ ments in the Performance and Operational Requiremen cume ORD), Unique Instrument Interface Document (UIID) XO General Interface Requirements Document (GIRD) requiremen

c) Trendin of key parameters durin e EDU, Prototype, and EDM deve m

d) Risks igate

e) Design difications ed to be imp mented for the FMs

f) As built p s and mate hlighting differences from the FM

g) Lessons l ned abo ntegratio ght Software (FSW), Ground

Software ( W), Ground Processing Algorithm (GPA).

2 Res rce manag ment

3.2.1 RM 1: Earned V ue Management (EVM) Plan

DA ITEM DESCRIPTION

CDRL 1

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

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) Developing ongoing comprehensive estimates at completion,

e) Flowing down requirements to all applicable subcontracts, and

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

Page 28 of 158 Printed Friday, July 7, 2023

ID

OCXCDRL132

OCXCDRL971

OCXCDRL133

OCXCDRL134

OCXCDRL135

OCXCDRL136

OCXCDRL

O CDRL138

OCX 139

Object Number

3.2.1.0-4

3.2.1.0-5

3.2.1.0-6

3.2.2

3.2.2.0-1

3.2.2.

3.2.2.0-4

3.2.2.0-5

418-XO-OCXCDRL-0063, RM Version, Geostationary eXtended Observations (GeoXO) Ocean Color (OCX) Contract Data

Requirements List (CDRL) Phase B

The EVMS description or EVM Plan shall address the requirements of NASA’s Federal Acquisition Regulation (FAR) Supplement (NFS) 1852 4-2 or Alternate I. Guidelines are available in the Earned Value Managemen ystems EIA-748-C Intent Guide Appendix Compliance Map Template.

FORMAT: Contractor-selected formats are acceptable.

Applicable Documents:

1) Industry Guidelines for Earned Value Management Syst EIA-748

2) Earned Value Management Syst NFS 1852.234-2 (or A ate I)

3) Earned Value Management S ms EIA-748 Intent Guide Ap dix

Compliance Map Template

3.2.2 RM-02: Financial Rep ts

DATA ITEM DESCRIPTION

1. CDRL No.: RM-02

2. Title: FINANCIAL REPOR

3. Use: To provide data neces for:

) Projecting costs a ours to ensure that cost and labor ources realistically port the Project and its s

b) Evalu tractor’s actual cost and fee data in rela n to neg d contract value, estimated costs, a budget forecast data, anning, monitoring, and controlling Project resources, and d Accruing cost in NASA’s accounting system.

4. Pre ation Informat

The ntractor shall subm t Financial Reports on NASA’s 533 series reports, in a tructions on the reverse of the forms, NASA Procedural equirements (NPR) 501.2, NASA Contractor Financial Management Reporting

(current version), and additional instructions issued by the contracting officer.

he Contractor shall include in the 533 series Financial Reports, a summary of l contract costs.

The ntractor shall include in the 533 series Financial Reports, a breakdown of hours and costs by WBS element One.

The Contractor shall include in the 533 series Financial Reports, a narrative explanation for variances exceeding plus or minus 10 percent between the total direct labor hours (prime and Subcontractors) and total estimated cost amount shown in the prior month, and the actual total direct labor hours and actual total cost amount shown in the current month at the total contract level (for example, the “Estimated Cost Hours to Complete” amount shown for June in column 8a in the May NASA Form (NF) 533M report and the “Cost Incurred Actual” June total cost amount shown in column 7a in the June NF 533M report) in accordance with Section 3.6 of NPR 9501.2.

Page 29 of 158 Printed Friday, July 7, 2023

ID

OCXCDRL140

OCXCDRL141

OCXCDRL142

OCXCDRL143

OCXCDRL938

OCXCDRL144

OCXCDRL145

Object Number

3.2.2.0-6

3.2.2.0-7

3.2.2.0-8

3.2.2.0-9

3.2.2.0-10

3.2.3

3.2.3 0

418-XO-OCXCDRL-0063, RM Version, Geostationary eXtended Observations (GeoXO) Ocean Color (OCX) Contract Data

Requirements List (CDRL) Phase B

For each variance narrative, the Contractor shall include in the 533 series Financial Reports:

a) Reason(s) for the variance,

b) Impact(s) on the core baseline and/or each in ual task order, and

c) Specific corrective action(s) being taken or t taken.

The Contractor shall distribute 533 reports to e addres indicated in the Contract Clause entitled, "Financial Manageme Reporting."

The Contractor shall include in the 533 es Financial Reports, a inimum, cost data (using accruals to match th hedule and earned value ma ement monthly data and end date) by the ntractors element of cost categor nd Provisionally-billed and Provision earned but unbilled Fee.

Financial period end date sha concile with schedule status date and the earned value management calen period date.

Applicable…