Attachment A-418-XO-SCSOW-0122_V_1_0_final.pdf

Effective Date: September 18, 2023 418-XO-SCSOW-0122 Responsible Organization: GeoXO Flight Project/Code 418 Version 1.0

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

GeoXO Spacecraft Statement of Work (SOW)

Signature page

Prepared by:

Electronically approved by: 09/18/2023 Michelle P. Rizzo Date GeoXO Observatory Manager NASA GSFC, Code 418

Reviewed by:

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

Christopher A. Wheeler Date GeoXO Flight Project, Deputy Project Manager NASA NOAA, Code 418

Approved by:

Electronically approved by C Wheeler for: 09/18/2023 Candace Carlisle Date GeoXO Flight Project, Project Manager NASA GSFC, Code 418

/GeoXO Flight Project Spacecraft

SCSOW

418-XO-SCSOW-0122, RM Version, Geostationary eXtended Observations (GeoXO) Spacecraft Statement of Work (SOW)

Version: 1.0 Printed by: rkhoover Printed on: Wednesday, September 27, 2023

No filter applied.

No sort applied.

Generated from DOORS 9.7.2.4

Contents

1 1Introduction

1.1 1Mission Overview

1.2 2Scope

1.3 3Period of Contract Coverage

1.4 3Documents and Terminology

1.4.1 3Applicable Documents

1.4.2 4Reference Documents

1.4.3 4Terminology

2 5Management

2.1 5Project Management

2.2 5Resource Management

2.2.1 6Government Resident Office

2.3 6Risk Management

2.4 7Configuration and Information Management

2.4.1 8Class I and Class II Changes

2.4.2 9Test Data Analysis System (TDAS)

2.5 9Special Engineering Analysis / Task Orders

2.6 9Project Review Requirements

2.6.1 9Kick-off Meeting and Requirements Walkthrough

2.6.2 10Project Management Status Reviews (PMSR)

2.6.3 11Integrated Baseline Review (IBR)

2.6.4 11Peer Reviews

2.6.5 11Spacecraft Milestone Reviews

2.6.5.1 12System Requirements / Definition Review (SRR/SDR)

2.6.5.2 12Preliminary Design Review (PDR)

2.6.5.3 13Critical Design Review (CDR)

2.6.5.4 13Pre-Environmental Review (PER) – Each Satellite

2.6.5.5 13Pre-Storage / Pre-Ship Review (PSR) – Each Satellite

2.6.5.6 13Design Modification Reviews (DMRs)

2.6.6 14Component, Subassembly, and Subsystem Reviews

2.6.7 14Instrument Receiving Review (IRR)

2.6.8 15Manufacturing Readiness Review (MRR)

2.6.9 15Test Reviews

2.6.10 16Hardware Acceptance Review (HAR)

Project: GeoXO Flight Project Spacecraft Module: SCSOW Baseline Version: 1.0

Contents ii

2.6.11 16Program Level Reviews

2.6.12 16Operations Reviews

2.6.13 17Technical Meetings

3 18Systems Engineering

3.1 18Systems Management and Engineering

3.2 19Interface Definition and Control

3.2.1 19Instrument Interfaces

3.2.2 20Ground Interfaces

3.2.3 20Launch Vehicle Interfaces

3.3 21System Analysis and Allocation

3.4 21Contamination Control and Analysis

4 23Software

4.1 23Management and Maintenance

4.2 24Software Reviews

5 25Spares Procurement

5.1 25Testing of Spare Hardware

5.2 25“One Shot” Items

6 27Engineering Development Program

6.1 27Engineering Development Activities

7 29GeoI1 Spacecraft

7.1 29Design and Analysis

7.1.1 29Spacecraft Design and Analysis

7.1.2 30Flight and Ground Test Software Development

7.1.3 31Fault Management

7.1.4 32Image Navigation and Registration (INR)

7.1.5 32Mechanical

7.1.6 33Thermal

7.1.7 33Guidance, Navigation, and Control (GN&C)

7.1.8 34Command and Data Handling (C&DH)

7.1.9 34Communication (COMM)

7.1.10 35Power

7.1.10.1 35Battery

7.1.10.1.1 36Battery Qualification

7.1.10.1.2 37Battery Life Testing

7.1.10.2 37Solar Array

Contents iii

7.1.10.3 37Power Regulation and Conditioning

7.1.11 37Propulsion

7.1.12 38Field Programmable Gate Array (FPGA) Design and Development

7.1.13 38Robotic Servicing

7.2 38Fabrication, and Component and Subassembly Testing

7.3 39Integration and Test

7.3.1 41Satellite I&T

7.3.2 43Functional and Performance Testing

7.3.2.1 43Comprehensive Performance Test (CPT)

7.3.2.2 43Limited Performance Test (LPT)

7.3.2.3 44Aliveness Test

7.3.3 44Structural and Mechanical Testing

7.3.4 45Electromagnetic Interference and Compatibility (EMI/EMC) Testing

7.3.5 45Thermal Testing

7.3.6 46Special Testing

7.3.6.1 46Space to Ground RF Compatibility Test

7.3.6.2 46System Validation Tests (SVTs)

7.4 47Logistics

7.4.1 47Transportation and Handling

7.4.2 47Ground Storage

7.5 48Launch and Operations Support

7.5.1 49Satellite and Launch Vehicle I&T

7.5.2 50Launch Operations

7.6 50Education and Public Outreach

8 51Mission Operations Support

8.1 52Pre-Launch Support

8.2 52End-to-End (ETE) Test Support

8.3 53Post-Launch Test (PLT) Support

8.4 53On-Orbit Anomaly Support

8.5 54Operations Tools

8.5.1 54Operations Database

9 56Ground Support Equipment (GSE)

9.1 56Mechanical Ground Support Equipment

9.2 56Electrical Ground Support Equipment

9.3 57Flight Software Development Environment (FSDE)

9.4 57Ground Test Software Development System

9.5 58Spacecraft Hardware Simulator (SHS)

Contents iv

9.6 59Satellite Software Simulator (S3)

9.7 60Spacecraft to Instrument Interface Simulator (SIIS)

9.8 60Spacecraft Command and Telemetry Simulator (SCTS)

9.9 60Simulator Maintenance

10 62Safety and Mission Assurance

11 65GeoI2

12 66GeoS1

13 67Option 1 - GeoI3

14 68Option 2 - GeoS2

15 69Option 3 - GeoI4

16 70Option 4 - GeoS3

17 72APPENDIX A: Acronyms

18 76APPENDIX B: Glossary

19 77APPENDIX C: Battery and Battery Set Quantity Reference Table

Contents v

Page 1 of 77 Printed Wednesday, September 27, 2023

ID

SCSOW1

SCSOW2

SCSOW3

SCSOW4

SCSOW5

Object Number

1.0-1

1.1

1.1.0-1

1.1.0-2

418-XO-SCSOW-0122, RM Version, Geostationary eXtended Observations (GeoXO) Spacecraft Statement of Work (SOW)

1 Introduction The National Oceanic and Atmospheric Administration (NOAA) operates a system of Geostationary Operational Environmental Satellites (GOES) to provide continuous weather imagery, and monitoring of meteorological and space environment data to protect life and property across the United States. Currently, two NOAA satellites remain operational at all times providing coverage for the eastern United States and most of the Atlantic Ocean, and the western United States and Pacific Ocean basin. The Geostationary eXtended Observations (GeoXO) Program is the follow-on to the GOES-R series. The GeoXO launch capability is planned for 2032. GeoXO is a collaborative development and acquisition effort between NOAA and the National Aeronautics and Space Administration (NASA). The acquisition of the end-to-end GeoXO system includes spacecraft, instruments, launch services, and all associated ground system elements.

The new NOAA GeoXO satellites will provide critical environmental observations for products supporting weather forecasting and warnings, climatologic analysis and prediction, ocean biochemistry, ecosystems management, and safe and efficient commercial and private air and marine transportation. The GeoXO satellites also provide supply support to terrestrial and oceanographic Data Collection System (DCS) Platforms.

1.1 Mission Overview

GeoXO will consist of three satellites operating in geostationary orbit in an east, west and central location. The nominal locations are 75 degrees West, 137 degrees West, and 105 degrees West longitude. The exact orbital locations are dependent on NOAA user needs, GeoXO satellite radio frequency assignments, and orbital conjunction assessment and risk analysis.

The GeoXO satellite consists of the spacecraft, Government Furnished Property (GFP) instruments, and auxiliary communication payload. The auxiliary communication payload is on the satellites in the east and west orbital locations only. The auxiliary communication payload provides hemispheric coverage for Data Collection Platform Report (DCPR) and Data Collection Platform Commands (DCPC). Each GeoXO satellite can accommodate up to three (3) Earth pointing instruments. The satellites in the east and west locations will have an identical payload. The GeoXO baseline includes the following five (5) Earth pointing GFP instruments and a potential partner payload:

⦁ Imager – The GeoXO Imager (GXI) will provide hemispheric, synoptic, and mesoscale environmental data and imagery for weather and hazard forecasting, including severe weather warning, and providing continuity for geostationary Earth orbit imagery data and products.

⦁ Infrared (IR) Hyperspectral Sounder – The GeoXO Sounder (GXS) will provide radiance data as input to Numerical Weather Prediction (NWP) and as input to retrievals of vertical and horizontal temperature and moisture information that will be used to produce routine meteorological analyses and forecasts of temperature, moisture, and winds for severe weather events. Radiance data will also be made available for monitoring longer-term climate change.

⦁ Ocean Color Instrument – The GeoXO Ocean Color Instrument (OCX) will provide new daytime coverage of U.S. Exclusive Economic Zone (EEZ East) plus Great Lakes and EEZ West plus southern Alaska, with commandability to Ocean Color Regions of Interest outside of the primary regions. The OCX remotely collects imagery of the Earth’s coastal waters for harmful algal blooms, water turbidity, and general water quality, fisheries management, habitat quality/assessment/mapping, pollution tracking, biogeochemical processing in coastal regions, warnings, and predictions. OCX will expand knowledge of

Page 2 of 77 Printed Wednesday, September 27, 2023

ID

SCSOW5

SCSOW6

SCSOW7

SCSOW8

SCSOW9

SCSOW10

SCSOW11

SCSOW12

Object Number

1.1.0-2

1.1.0-3

1.1.0-4

1.1.0-5

1.2

1.2.0-1

1.2.0-2

1.2.0-3

418-XO-SCSOW-0122, RM Version, Geostationary eXtended Observations (GeoXO) Spacecraft Statement of Work (SOW) coastal waters and ocean processes in these regions.

⦁ Lightning Mapper – The GeoXO Lightning Mapper (LMX) will allow tracking of each lightning flash within a specific storm cell and calculation of its optical center over time to improve lightning hazards information, storm warning and nowcasting. Data from LMX will also be made available for long-term tracking of decadal changes in lightning activity.

⦁ Atmospheric Composition Instrument – The GeoXO Atmospheric Composition Instrument (ACX) will collect measurements of ozone, nitrogen dioxide, and other pollutants used to determine and product forecasts and warnings of national air quality, hazard, and fire smoke.

The GXI, LMX, and OCX instruments will be on the GeoXO east and west satellites. The GXS and ACX instruments, as well as a potential partner payload (TBD) will be on the central satellite. The naming convention for the east/west and central satellites is:

⦁ East/West satellites: GeoI, “I” for Imager ⦁ Pre-launch these will be GeoI1, GeoI2, GeoI3, and GeoI4.

⦁ On-orbit these will be re-named GOES-20, 21, 22, and 23.

⦁ Central satellites: GeoS, “S” for Sounder ⦁ Pre-launch: GeoS1, GeoS2 and GeoS3.

⦁ On-orbit these satellite names will not change.

The GeoXO satellites will be launched from Kennedy Space Center (KSC). The Government is responsible for launch vehicle procurement, ground networks, and communications required for performing the launch and orbit raising activities. All launch and orbit raising activities will be performed from the NOAA Satellite Operations Facility (NSOF) in Suitland, MD. Once geostationary orbit is achieved, all activities will be performed using the NOAA Command and Data Acquisition Station (CDAS) at Wallops Island, Virginia as the primary ground station, and a Consolidated Backup (CBU) Facility at Fairmont, West Virginia.

During the transition to the GeoXO satellite series, the operational constellation may contain GOES R series (GOES-16 to 19) satellites and incumbent satellites that have not yet been de-orbited.

1.2 Scope

This Statement of Work (SOW) defines those tasks necessary to design, analyze, develop, fabricate, integrate, test, evaluate, ship and launch the GeoXO spacecraft integrated with the GFP instruments; supply and maintain the spacecraft Ground Support Equipment (GSE); and support the Mission Operations in accordance with the Contractual documents listed in the Applicable Documents Section.

The GeoXO spacecraft has a risk classification of Class B in accordance with NPR 8705.4A.

Satellite is a spacecraft integrated with all the instrument payloads.

Page 3 of 77 Printed Wednesday, September 27, 2023

ID

SCSOW13

SCSOW14

SCSOW15

SCSOW16

SCSOW17

SCSOW18

SCSOW19

SCSOW20

SCSOW21

SCSOW22

SCSOW23

SCSOW24

Object Number

1.2.0-4

1.2.0-5

1.2.0-6

1.2.0-7

1.2.0-8

1.2.0-9

1.3

1.3.0-1

1.3.0-2

1.4

1.4.1

1.4.1.0-1

418-XO-SCSOW-0122, RM Version, Geostationary eXtended Observations (GeoXO) Spacecraft Statement of Work (SOW)

The Contractor shall provide the personnel, parts, materials, facilities, and other resources to design, develop, deliver and support under the basic contract the items outlined below and as stated in the contract clause B.1:

a. Two (2) Protoflight spacecraft designated as GeoI1 and GeoS1

b. One spacecraft designated as GeoI2

c. A complete set of parts and materials for each spacecraft to be used as spares to ensure the readiness and launch cadence of GeoI1, GeoI2, and GeoS1.

The Contractor shall provide the personnel, parts, materials, facilities, and other resources to design, develop, deliver, and support the following options as outlined below and stated in the contract clause B.1:

a. Option 1 for an additional GeoI spacecraft designated as GeoI3

b. Option 2 for an additional GeoS spacecraft designated as GeoS2

c. Option 3 for an additional GeoI spacecraft designated as GeoI4

d. Option 4 for an additional GeoS spacecraft designated as GeoS3

The GeoI spacecraft shall accommodate the GXI, LMX, and OCX instruments.

The GeoI spacecraft shall accommodate the auxiliary communication payload as defined in the Data Collection System (DCS) Interface Requirement Document (418-XO-

IRD-0044).

The GeoS spacecraft shall accommodate the GXS, ACX, and Partner Payload instruments.

The GeoS spacecraft shall be able to be delivered, flown, and operated with or without a Partner Payload.

1.3 Period of Contract Coverage

The period of contract coverage is from contract award through the life of the mission, including successful launch, post-launch evaluation, mission operations support, and on-orbit anomaly investigations until all the satellites reach end-of-mission.

The Contractor shall retain all documents and test data produced under this contract for the life of the contract plus six (6) years.

1.4 Documents and Terminology

1.4.1 Applicable Documents

The documents listed in this section apply directly to the performance of the spacecraft contract. These documents establish detailed specifications, requirements, and interface information necessary for the performance of the contract.

1. 418-XO-SCCDRL-0053: Spacecraft Control Data Requirements List

2. 418-XO-PSPEC-0051: Functional and Performance Specification (F&PS)

3. 418-XO-PRAD-0037: Payload Resources Allocation Document (PRAD)

4. 418-XO-SCMAR-0083: Spacecraft Mission Assurance Requirements (SCMAR)

5. 418-XO-GIRD-0041: GeoXO General Interface Requirements Document (GIRD)

6. 418-XO-GXIUIID-0023: GXI Unique Instrument Interface Document (GXIUIID)

7. 418-XO-GXSUIID-0030: GXS Unique Instrument Interface Document (GXSUIID)

8. 418-XO-OCXUIID-0062: OCX Unique Instrument Interface Document

(OCXUIID)

9. 418-XO-LMX-UIID-0067: LMX Unique Instrument Interface Document

Page 4 of 77 Printed Wednesday, September 27, 2023

ID

SCSOW24

SCSOW25

SCSOW26

SCSOW27

SCSOW28

SCSOW29

SCSOW30

SCSOW31

Object Number

1.4.1.0-1

1.4.2

1.4.2.0-1

1.4.3

1.4.3.0-1

1.4.3.0-2

1.4.3.0-3

1.4.3.0-4

418-XO-SCSOW-0122, RM Version, Geostationary eXtended Observations (GeoXO) Spacecraft Statement of Work (SOW)

(LMXUIID)

10. 418-XO-ACXUIID-0072: ACX Unique Instrument Interface Document (ACXUIID)

11. 418-XO-PTRUIID-0141: Partner Payload Unique Instrument Interface

Document (PTRUIID)

12. 418-XO-IRD-0043: SS to Ground Located Command, Control & Communications

(SS-C3S IRD)

13. 418-XO-IRD-0044: SS to Data Collection System (SS-DCS IRD) Interface

Requirements Document

14. NPR 7123.1D NASA System Engineering Processes and Requirements Appendix

E. – Technology Readiness Levels (with Change 2)

15. NASA-STD-8719.24 Annex Rev B w/Change 1: Annex to NASA-STD-8719.24

Nasa Payload Safety Requirements: Requirements Table

16. NASA-STD-8739.8B: Software Assurance and Safety Standard

17. NPR 7150.2D: NASA Software Engineering Requirements

18. NASA-GB-8719.13, NASA Software Safety Guidebook

19. GPR 7120.7B: Funded Schedule Margin and Budget Margin for Flight Projects

20. ISO 14644-1:2015 Cleanrooms and associated controlled environments - Part

1: Classification of air cleanliness by particle concentration, December 15, 2015

1.4.2 Reference Documents

1. NPR 8705.4A: Risk Classification for NASA Payloads

2. NASA-STD-8719.24A: NASA Payload Safety Requirements

3. 418-XO-RPT-0045: Flight Field Programmable Gate Array (FPGA) Review

Methodology

4. 418-XO-RPT-0042: The Radiation Environmental Devices on GeoXO Series

Satellites

5. 418-XO-RPT-0039: GOES Reliable Data Delivery Protocol

6. 410-XO-CONOPS-0004: GeoXO Concept of Operations

7. SAE EIA-649-2: Configuration Management Requirements for NASA Enterprises

1.4.3 Terminology

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

The use of “will” designates a statement of fact or intention of the Government.

The use of “may” designates that permission has been granted by the Government.

The term “Government” shall be defined as Government personnel and Government support contractor personnel.

Page 5 of 77 Printed Wednesday, September 27, 2023

ID

SCSOW32

SCSOW33

SCSOW34

SCSOW35

SCSOW36

SCSOW37

SCSOW38

SCSOW39

SCSOW40

SCSOW41

SCSOW42

SCSOW43

SCSOW915

SCSOW44

SCSOW45

Object Number

2.1

2.1.0-1

2.1.0-2

2.1.0-3

2.1.0-4

2.1.0-5

2.1.0-6

2.1.0-7

2.1.0-8

2.1.0-9

2.1.0-10

2.1.0-11

2.2

2.2.0-1

418-XO-SCSOW-0122, RM Version, Geostationary eXtended Observations (GeoXO) Spacecraft Statement of Work (SOW)

2 Management

2.1 Project Management

The Contractor shall establish a Project Management Office (PMO) responsible for overall project control to assure that all requirements of this contract, the Statement of Work (SOW) and all attachments are accomplished within cost and schedule.

The Contractor shall provide and implement a Project Management Plan (PMP), plus all updates and revisions, that describes the methodology and processes that will be employed to manage the Project from contract award through operational support of the last spacecraft delivered under this contract, in accordance with CDRL # PM-01.

The Contractor shall establish effective communication with the Government Project Office through the Government representative that includes, but is not limited to, e-mail and telephone contact as necessary, weekly telecons with the Government spacecraft team, and one-on-one contact between NASA and Contractor discipline engineers, to be coordinated by the Contracting Officer Representative (COR).

The Contractor shall establish a Subcontract Management and Control System to provide technical direction and effective subcontract management utilizing schedule milestone controls.

The Contractor shall develop and maintain a Master Action Item Database (MAID), or a spreadsheet, listing all Request for Actions (RFAs) or Action Items from formal reviews, Government status reviews, internal technical reviews, peer reviews, all other reviews required by the contract, technical meetings, telecons, etc., listing author and origin (Preliminary Design Review (PDR), telecon, etc.) of the RFA, person responsible for closure, wording of the RFA, response, persons(s) authorizing final closure, due date, date closed, and a column for Government concurrence.

The Contractor shall post the MAID to the GeoXO Portal and the Contractor's Spacecraft Portal.

The Contractor shall retain all closed actions in the MAID.

The Contractor shall conduct weekly management teleconferences to present, review and discuss technical, risks, schedule, and cost information and to address MAID items and issues.

The Contractor shall submit Weekly Status Reports and Telecon Minutes, plus all updates and revisions, in accordance with CDRL # PM-02.

The Contractor shall ensure retention of critical skills, including but not limited to Systems Engineering, Ground Support Equipment, Flight Software and spacecraft/satellite Integration and Test, in order to mitigate technical and schedule risks throughout the period of contract performance.

The Contractor shall develop an Early Launch Contingency Plan in accordance with

CDRL # PM-12.

2.2 Resource Management

The Contractor shall implement an Earned Value Management System to track and report cost and schedule performance.

Page 6 of 77 Printed Wednesday, September 27, 2023

ID

SCSOW46

SCSOW47

SCSOW48

SCSOW49

SCSOW50

SCSOW51

SCSOW52

SCSOW53

SCSOW54

SCSOW55

SCSOW56

SCSOW57

SCSOW58

SCSOW59

SCSOW60

SCSOW61

SCSOW62

Object Number

2.2.0-2

2.2.0-3

2.2.0-4

2.2.0-5

2.2.0-6

2.2.0-7

2.2.1

2.2.1.0-1

2.2.1.0-2

2.2.1.0-3

2.2.1.0-4

2.2.1.0-5

2.2.1.0-6

2.2.1.0-7

2.3

2.3.0-1

2.3.0-2

418-XO-SCSOW-0122, RM Version, Geostationary eXtended Observations (GeoXO) Spacecraft Statement of Work (SOW)

The Contractor shall prepare and deliver an Earned Value Management (EVM) Plan, plus all updates and revisions, in accordance with CDRL # RM-01.

The Contractor shall prepare and deliver Financial Reports, plus all updates and revisions, in accordance with CDRL # RM-02.

The Contractor shall prepare and deliver Integrated Program Management Data and Analysis Report (IPMDAR), plus all updates and revisions, in accordance with CDRL #

RM-03.

The Contractor shall baseline schedule margin in accordance with GPR 7120.7B.

The Contractor shall prepare and deliver a detailed Contract Work Breakdown Structure (CWBS) and CWBS Dictionary, plus all updates and revisions, in accordance with, CDRL # RM-04.

The Contractor shall prepare and deliver Unit Cost Report, plus all updates and revisions, in accordance with CDRL # RM-06.

2.2.1 Government Resident Office

The Contractor shall provide private office space, furniture, copier(s), printers, phones, and high-speed internet access in the vicinity of the PMO for eight (8) Government resident representatives.

In the private office space, the Contractor shall provide three offices with closed doors.

The Contractor shall provide additional office space, furniture, copiers(s), printers, phones, and high-speed internet access for up to twenty-five (25) people in the vicinity of the PMO for use by Government representatives and GFP instrument contractors during reviews, integration and testing, or other functions that will increase the number of on-site Government representatives.

The Contractor shall provide a conference room equipped with a teleconferencing system and video monitor that is available for use by the Government capable of accommodating at least fifteen (15) people.

The Contractor shall facilitate and support access for Government personnel to the NASA Center Network Environment (CNE) in the private office space. CNE facilitation will require an access controlled secure communications closet space.

The Contractor shall provide a live video feed of the spacecraft and satellite Integration and Test Activities to the Government resident office.

The Contractor shall ensure unencumbered non-escort access by the Government and Government support personnel to all Contractor and subcontractor facilities where program work is performed.

2.3 Risk Management

The Contractor shall implement and maintain a Risk Management Program that addresses all programmatic, safety, and technical risks.

The Contractor shall prepare, deliver, and implement a Risk Management Plan, plus updates and revisions, in accordance with CDRL # PM-03.

Page 7 of 77 Printed Wednesday, September 27, 2023

ID

SCSOW63

SCSOW64

SCSOW65

SCSOW66

SCSOW67

SCSOW68

SCSOW69

SCSOW70

SCSOW71

SCSOW72

SCSOW73

SCSOW74

SCSOW75

Object Number

2.3.0-3

2.3.0-4

2.3.0-5

2.3.0-6

2.4

2.4.0-1

2.4.0-2

2.4.0-3

2.4.0-4

2.4.0-5

2.4.0-6

2.4.0-7

2.4.0-8

418-XO-SCSOW-0122, RM Version, Geostationary eXtended Observations (GeoXO) Spacecraft Statement of Work (SOW)

The Contractor shall develop and implement risk management strategies, actions (mitigate, watch or research), and assign tasks and appropriate resources to manage and control the risks.

The Contractor shall ensure all spacecraft technologies are at Technology Readiness Level (TRL) 6 by PDR as defined by NPR 7123.1D - NASA Systems Engineering Processes and Requirements Appendix E. - Technology Readiness Levels.

The Contractor shall:

a. identify and track all risks that are being mitigated on an ongoing basis,

b. capture risk attributes and mitigation information in accordance with the approved Risk Management Plan,

c. establish risk management performance metrics, and

d. examine trends, deviations and anomalies for identification of risks.

The Contractor shall provide the Government remote access to the Contractor's risk management system.

2.4 Configuration and Information Management

The Contractor shall oversee and manage the generation, configuration control, and distribution of all documents required by the contract.

The Contractor shall establish, implement, and maintain a Configuration Management System that provides configuration management control of configured items including all flight hardware, all Ground Support Equipment (GSE) hardware, and all controlled documentation developed under this contract, including drawings, procedures, plans, CDRLs, and program review materials.

The Contractor's Configuration Management System shall adhere to the principles of SAE EIA-649-2, Configuration Management Requirements for NASA Enterprises.

The Government will establish and maintain a secure website, called the GeoXO Portal, accessible by the Contractor and selected Government personnel, for document delivery and the exchange of information only. A folder will be maintained on the portal for each of the instruments and spacecraft, accessible only by the respective Contractor and selected Government-personnel.

The Contractor shall prepare, control, maintain, and place all contract-deliverable documentation produced in accordance with the CDRL DIDs on the GeoXO Portal with a file name that includes the CDRL number.

The Contractor shall perform portal management for the spacecraft section of the GeoXO Portal and organize the CDRL folders by year, spacecraft, and subsystem, as applicable.

The Government will post on the spacecraft section of the GeoXO Portal Government deliverables and technical and contractual documentation generated in support of the GeoXO spacecraft.

The Contractor shall notify the selected Government personnel by e-mail that a document has been posted on the GeoXO Portal. The Government will provide similar notification to the Contractor.

Page 8 of 77 Printed Wednesday, September 27, 2023

ID

SCSOW76

SCSOW77

SCSOW78

SCSOW79

SCSOW80

SCSOW81

SCSOW82

SCSOW83

SCSOW84

SCSOW85

SCSOW86

SCSOW87

SCSOW88

SCSOW89

Object Number

2.4.0-9

2.4.0-10

2.4.0-11

2.4.0-12

2.4.0-13

2.4.0-14

2.4.0-15

2.4.1

2.4.1.0-1

2.4.1.0-2

2.4.1.0-3

2.4.1.0-4

2.4.1.0-5

2.4.1.0-6

418-XO-SCSOW-0122, RM Version, Geostationary eXtended Observations (GeoXO) Spacecraft Statement of Work (SOW)

The Contractor shall also establish and maintain a spacecraft repository or library known as the Contractor’s spacecraft portal which will include configuration controlled and non-configuration controlled documentation.

The Contractor shall place on the Contractor's spacecraft portal, as generated or changed, all technical and programmatic documentation generated on the contract, whether deliverable or not, that includes, but is not limited to, the MAID, system engineering reports, design memos, internal technical memoranda, subcontractor documentation, data, drawings, schematics, design specifications, analyses, test procedures, and reports.

The Contractor shall perform portal management for the Contractor’s spacecraft portal and organize the folders at a minimum by spacecraft and subsystem.

The Contractor shall provide remote access to the Contactor's spacecraft portal for contract documentation to Contracting Officer’s Representative (COR) and COR-recommended Government personnel.

The Contractor shall provide the Government with remote access to Contractor GeoXO series internal systems used for spacecraft production. Internal systems include tools, programs, and sites that are used by the Contractor for engineering, build, test, and mission assurance of the spacecraft.

The Contractor shall provide and implement a Configuration Management Plan, plus updates and revisions, in accordance with CDRL # PM-04.

The Contractor shall implement a Knowledge Management Program so that the knowledge base developed during design and development of the engineering development units and all spacecraft will be available to the spacecraft Project personnel through the life of the mission in accordance with CDRL #PM-01, Project Management Plan.

2.4.1 Class I and Class II Changes

The Contractor shall establish a Configuration Control Board to review and approve changes to the flight hardware, software, GSE, and all controlled documents.

The Contractor shall submit Class I changes to the Government for approval before implementation of the change, in accordance with Configuration Change Requests, Deviations, and Waivers, CDRL # PM-05.

The Contractor shall submit Class II changes to the Government for concurrence with the classification, in accordance with Configuration Change Requests, Deviations, and Waivers, CDRL # PM-05.

The Contractor shall provide technical, schedule, and cost impacts to Government-proposed Class I changes.

The Contractor shall create and maintain two separate folders, one each for Class I and Class II Configuration Change Request categories, in the CDRL # PM-05 folder on the GeoXO portal and post the Deviation and Waiver requests in the appropriate folder according to their Class.

If the Government determines that a Class II classification is incorrect, the Contractor shall resubmit the change as a Class I change.

Page 9 of 77 Printed Wednesday, September 27, 2023

ID

SCSOW90

SCSOW91

SCSOW92

SCSOW917

SCSOW93

SCSOW94

SCSOW95

SCSOW96

SCSOW97

SCSOW98

SCSOW99

SCSOW100

SCSOW101

SCSOW102

SCSOW104

SCSOW105

SCSOW106

Object Number

2.4.2

2.4.2.0-1

2.4.2.0-2

2.4.2.0-3

2.4.2.0-4

2.4.2.0-5

2.4.2.0-6

2.4.2.0-7

2.4.2.0-8

2.5

2.5.0-1

2.5.0-2

2.6

2.6.0-1

2.6.0-2

2.6.0-3

2.6.1

418-XO-SCSOW-0122, RM Version, Geostationary eXtended Observations (GeoXO) Spacecraft Statement of Work (SOW)

2.4.2 Test Data Analysis System (TDAS)

The Contractor shall develop and maintain all of the hardware, software, office space, internet access, and operational support for a Test Data Analysis System (TDAS).

The TDAS shall provide the Government access to spacecraft and integrated instrument processed data, test analyses, and test reports.

The TDAS shall be operational from the start of the first spacecraft I&T through the launch of the last spacecraft.

The TDAS shall provide the Government access to spacecraft and integrated instrument raw test data within 24 hours.

The TDAS shall provide the Government access to spacecraft real time telemetry, and integrated instrument real time telemetry from onsite and remote locations for a minimum of 6 simultaneous users.

The Contractor shall maintain remote access to real time telemetry during local power outages during powered testing.

The TDAS shall establish, implement, maintain, and provide the Government remote access to a data storage and retrieval system to be used for long-term trending and analysis of GeoXO spacecraft telemetry data and EGSE data captured during I&T across multiple spacecraft.

The Contractor shall prepare, present, and deliver Test Data Analysis System (TDAS) Training and Operations Package, plus updates and revisions, in accordance with CDRL # I&T-01.

2.5 Special Engineering Analysis / Task Orders

The Contractor shall execute Special Engineering Analysis / Task Orders relating to the development, implementation, and operation of the spacecraft and ground systems as required and authorized by contract clause H.12.

Upon request by the Contracting Officer, the Contractor shall prepare and submit a Contractor Task Plan for each Special Engineering Analysis / Task Order.

2.6 Project Review Requirements

The Contractor shall provide the technical and administrative support for all Project reviews and meetings including, but not limited to: Spacecraft Design Reviews, Project Management Status Reviews, Technical Meetings, Data Reviews, Design Modification/Upgrade Reviews, Component Reviews, Subassembly Reviews, Subsystem reviews, and Subcontract Reviews.

Unless stipulated otherwise by the Government, the Contractor shall hold all spacecraft Project Reviews and meetings at the Contractor's facility.

The Contractor shall provide a virtual attendance option for all meetings and reviews.

2.6.1 Kick-off Meeting and Requirements Walkthrough

Page 10 of 77 Printed Wednesday, September 27, 2023

ID

SCSOW107

SCSOW108

SCSOW109

SCSOW110

SCSOW111

SCSOW112

SCSOW113

SCSOW114

SCSOW115

Object Number

2.6.1.0-1

2.6.1.0-2

2.6.1.0-3

2.6.1.0-4

2.6.2

2.6.2.0-1

2.6.2.0-2

2.6.2.0-3

2.6.2.0-4

418-XO-SCSOW-0122, RM Version, Geostationary eXtended Observations (GeoXO) Spacecraft Statement of Work (SOW)

Approximately six weeks after award the Contractor shall prepare and conduct a Kick-off Meeting covering an overview of the spacecraft development and subsequently a line-by-line review of the contract schedule and clauses, and the requirements documents, SOW, Spacecraft Functional and Performance Specification (F&PS), Payload Resource Allocation Document (PRAD), General Interface Requirements Document (GIRD), Unique Instrument Interface Documents (UIIDs), Space Segment to DCS Interface Requirements Document (SS-DCS IRD), Space Segment to Ground Located Command, Control and Communications Interface Requirements Document (SS-C3S IRD), Spacecraft Mission Assurance Requirements Document (SCMAR), and Contract Data Requirements List (CDRL).

The Contractor shall plan for a five (5) day Kick-off meeting.

In the first day of the Kick-off meeting, the Contractor shall present:

a. An overview and introduction to the organization and personnel (both Contractor and Government Teams)

b. A top-level look at the total program schedule with a more detailed look at the near-term schedule (between kickoff and Integrated Baseline Review (IBR))

c. A summary of regularly scheduled meetings and a tentative meeting schedule for the first 6 months (PMSRs, table top reviews, peer reviews, project milestone reviews, etc.)

d. An overview of the spacecraft design concept

e. An overview of any technology development work

f. An overview of current risk database and risk management approach

g. Overview of configuration management approach

h. Overview of Safety and Mission Assurance (SMA) and quality processes

i. Overview of Contractor facilities

If the line-by-line review of the Contractual documents is not complete in five (5) days during the Kick-off meeting, the Contractor shall continue to conduct and support the requirements review, at a time to be agreed upon by the Contractor and the Government, until the Government deems the requirements review complete.

2.6.2 Project Management Status Reviews (PMSR)

The Contractor shall prepare and hold Project Management Status Reviews (PMSRs) every other month with the Government for the purpose of reviewing the status of the spacecraft and GSE development, and the overall status of the project. The Government reserves the right to increase the PMSR frequency to monthly in case of schedule slippage that affect critical path by more than one month.

Until the Preliminary Design Review (PDR), at each PMSR, the Contractor shall provide an update to the technology maturation efforts.

Unless modified by mutual consent, the PMSRs shall be conducted as a face-to-face meeting with the Government.

The PMSRs will be held at the Contractor's facility through successful completion of the CDR, then alternate between Government-designated facilities and the Contractor’s facilities. Government may require specific agenda items be included.

Page 11 of 77 Printed Wednesday, September 27, 2023

ID

SCSOW116

SCSOW117

SCSOW118

SCSOW119

SCSOW120

SCSOW121

SCSOW122

SCSOW123

SCSOW124

SCSOW125

SCSOW126

SCSOW127

SCSOW918

SCSOW128

SCSOW919

SCSOW129

SCSOW130

SCSOW131

Object Number

2.6.2.0-5

2.6.2.0-6

2.6.3

2.6.3.0-1

2.6.3.0-2

2.6.3.0-3

2.6.3.0-4

2.6.3.0-5

2.6.4

2.6.4.0-1

2.6.4.0-2

2.6.4.0-3

2.6.4.0-4

2.6.4.0-5

2.6.4.0-6

2.6.5

2.6.5.0-1

2.6.5.0-2

418-XO-SCSOW-0122, RM Version, Geostationary eXtended Observations (GeoXO) Spacecraft Statement of Work (SOW)

The Contractor shall prepare, present, and deliver Project Management Status Reviews - Technical (PMSR-T) and PMSR Business (PMSR-B) Data Package, plus updates and revisions, in accordance with CDRL # PM-06. The GeoXO Project may choose to conduct PMSR-T and PMSR-B separately.

The contractor shall place PMSR-T and PMSR-B Data Packages on the GeoXO portal twelve (12) hours before the start of the Technical and Business PMSRs.

2.6.3 Integrated Baseline Review (IBR)

Approximately 6 months after contract award, the Contractor shall conduct the IBR.

The Contractor shall include a review of the Contractor's earned value assessment and reporting system in the IBR.

The Contractor shall plan for a three (3) day review for the IBR.

The IBR shall follow the WBS based schedule in sufficient depth of detail to show the critical path, all linkages to lower tasks to expose missing dependencies, and to ensure a smooth workflow plan through the delivery of contracted units.

The Contractor shall submit an Integrated Baseline Review Package, plus updates and revisions, in accordance with CDRL # RM-07.

2.6.4 Peer Reviews

The Contractor shall implement and conduct a program of tabletop engineering reviews (Peer Reviews) throughout the development life cycle to identify and resolve concerns as they arise in the design process, and prior to formal, system level reviews.

The Contractor shall prepare and deliver an engineering Peer Review plan for Contractor and subcontractor developed hardware and software in the Systems Engineering Management Plan, CDRL # SE-PLAN-02-1.

The Contractor shall include in the Peer Reviews Government and Contractor's technical experts with significant practical experience relevant to the technology and the requirements for the review.

The Contractor shall staff Peer Reviews with independent reviewers for the hardware under review.

The Contractor shall provide ten (10) days prior notification for Peer Reviews so that Government representatives can be present.

The Contractor shall post the Peer Review materials to the GeoXO portal within seven

(7) days after completion of the Peer Review.

2.6.5 Spacecraft Milestone Reviews

The Contractor shall prepare and conduct Government-chaired spacecraft Milestone Reviews for the Goddard System Review Team (GSRT). The reviews will cover all aspects of flight and ground hardware, software, and operations for which the Contractor has responsibility.

The Contractor shall conduct a dry run of each Milestone Review, with the Government spacecraft team in attendance, approximately 2 weeks prior to the review.

Page 12 of 77 Printed Wednesday, September 27, 2023

ID

SCSOW132

SCSOW133

SCSOW134

SCSOW135

SCSOW136

SCSOW137

SCSOW138

SCSOW920

SCSOW139

SCSOW140

SCSOW141

SCSOW142

SCSOW143

SCSOW144

SCSOW145

SCSOW146

Object Number

2.6.5.0-3

2.6.5.0-4

2.6.5.0-5

2.6.5.0-6

2.6.5.0-7

2.6.5.1

2.6.5.1.0-1

2.6.5.1.0-2

2.6.5.1.0-3

2.6.5.1.0-4

2.6.5.1.0-5

2.6.5.1.0-6

2.6.5.1.0-7

2.6.5.1.0-8

2.6.5.2

2.6.5.2.0-1

418-XO-SCSOW-0122, RM Version, Geostationary eXtended Observations (GeoXO) Spacecraft Statement of Work (SOW)

After each review, the Contractor shall document all RFAs in the MAID within 1 week of receipt.

Each Milestone Review (PDR, CDR, etc.) is not considered complete until approved by the Government. If the Government determines that a delta review is necessary, the Contractor shall conduct such review at a time mutually agreed upon with the COR.

The Contractor shall deliver an outline for the Milestone Review package twenty-one

(21) days before each of the contractually-required spacecraft milestone reviews listed in Sections 2.6.5.1 – 2.6.5.6 below in accordance with CDRLs # SR-01, SR-02, SR-03, SR-04, SR-05 and SR-06.

The Contractor shall deliver the Milestone Review packages seven (7) days before each of the contractually-required spacecraft Milestone Reviews listed in Sections 2.6.5.1 –

2.6.5.6 below in accordance with CDRLS #SR-01, SR-02, SR-03, SR-04, SR-05 and

SR-06.

The spacecraft System Requirements/System Definition Review (SRR/SDR), Preliminary Design Review (PDR), and Critical Design Review (CDR) will serve as the Flight Project reviews leading to the Program’s Mission Definition Review (MDR), Mission PDR and Mission CDR respectively.

2.6.5.1 System Requirements / Definition Review (SRR/SDR)

Approximately three (3) months after kickoff, the Contractor shall prepare and conduct a single SRR/SDR covering both GeoI and GeoS spacecraft system specifications including: spacecraft requirements, interfaces, GSE, and flight software and ground test software requirements.

The Contractor shall prepare and conduct a single SRR/SDR covering GeoI and GeoS spacecraft designs.

The Contractor shall plan for a four (4) day SRR/SDR, not including resolution of RFAs.

The Contractor shall assess the TRL of all components of the spacecraft design at

SRR/SDR.

The Contractor shall provide a schedule explaining how all technologies will achieve TRL 6 by the spacecraft Preliminary Design Review (PDR).

For technologies that have not reached a TRL of 6 at SRR/SDR, the TRL and associated development schedule shall clearly identify all of the work that is planned to be performed to achieve the required technology maturity at PDR.

The Contractor shall seek Government's permission to hold PDR 90 days prior to the PDR date if TRL 6 advancement activities are projected to occur beyond PDR.

The Contractor shall prepare and deliver a System Requirements / System Definition Review (SRR/SDR) Data Package, plus updates and revisions, in accordance with CDRL

# SR-01.

2.6.5.2 Preliminary Design Review (PDR)

The Contractor shall prepare and conduct a single PDR covering GeoI and GeoS spacecraft designs.

Page 13 of 77 Printed Wednesday, September 27, 2023

ID

SCSOW147

SCSOW148

SCSOW149

SCSOW150

SCSOW151

SCSOW152

SCSOW153

SCSOW154

SCSOW155

SCSOW156

SCSOW157

SCSOW158

SCSOW159

SCSOW160

SCSOW161

SCSOW162

SCSOW163

SCSOW164

SCSOW165

SCSOW166

Object Number

2.6.5.2.0-2

2.6.5.2.0-3

2.6.5.2.0-4

2.6.5.2.0-5

2.6.5.3

2.6.5.3.0-1

2.6.5.3.0-2

2.6.5.3.0-3

2.6.5.4

2.6.5.4.0-1

2.6.5.4.0-2

2.6.5.4.0-3

2.6.5.5

2.6.5.5.0-1

2.6.5.5.0-2

2.6.5.5.0-3

2.6.5.5.0-4

2.6.5.5.0-5

2.6.5.5.0-6

2.6.5.6

418-XO-SCSOW-0122, RM Version, Geostationary eXtended Observations (GeoXO) Spacecraft Statement of Work (SOW)

The Contractor shall status the design and testing of the breadboard or brassboard models and EDUs at the PDR.

The Contractor shall plan for a four (4) day PDR, not including resolution of RFAs.

The Contractor shall demonstrate that all technologies in the spacecraft design have achieved TRL 6.

The Contractor shall prepare and deliver a Preliminary Design Review (PDR) Data Package, plus updates and revisions, in accordance with CDRL # SR-02.

2.6.5.3 Critical Design Review (CDR)

The Contractor shall prepare and conduct a single CDR covering GeoI and GeoS prior to the start of manufacture of the flight hardware unless the Contractor requests and the Government concurs with an earlier start.

The Contractor shall plan for a five (5) day CDR, not including resolution of RFAs.

The Contractor shall prepare and deliver a Critical Design Review (CDR) Data Package, plus updates and revisions, in accordance with CDRL # SR-03.

2.6.5.4 Pre-Environmental Review (PER) – Each Satellite

The Contractor shall prepare and conduct a PER prior to the start of environmental testing of each satellite to establish the readiness of the satellite and to evaluate the environmental test plans and procedures.

The Contractor shall plan for a three (3) day PER, not including resolution of RFAs.

The Contractor shall prepare and deliver a PER Data Package, plus updates and revisions, in accordance with CDRL # SR-04.

2.6.5.5 Pre-Storage / Pre-Ship Review (PSR) – Each Satellite

The Contractor shall prepare and conduct a Pre-Storage Review (PSR) prior to placement of each satellite into storage at the Contractor's facilities.

The Contractor shall plan for a three (3) day Pre-Storage Review, not including resolution of RFAs.

The Contractor shall prepare and deliver a Pre-Storage Review Data Package, plus updates and revisions, in accordance with CDRL # SR-05.

The Contractor shall prepare and conduct a Pre-Ship Review prior to the shipment of each satellite to KSC.

The Contractor shall plan for a three (3) day Pre-Ship Review, not including resolution of RFAs.

The Contractor shall prepare and deliver a Pre-Ship Review Data Package, plus updates and revisions, in accordance with CDRL # SR-05.

2.6.5.6 Design Modification Reviews (DMRs)

Page 14 of 77 Printed Wednesday, September 27, 2023

ID

SCSOW167

SCSOW168

SCSOW169

SCSOW170

SCSOW171

SCSOW172

SCSOW174

SCSOW175

SCSOW176

SCSOW177

SCSOW178

SCSOW179

SCSOW180

SCSOW181

SCSOW182

SCSOW183

SCSOW184

Object Number

2.6.5.6.0-1

2.6.5.6.0-2

2.6.5.6.0-3

2.6.6

2.6.6.0-1

2.6.6.0-2

2.6.6.0-3

2.6.6.0-4

2.6.6.0-5

2.6.6.0-6

2.6.6.0-7

2.6.6.0-8

2.6.7

2.6.7.0-1

2.6.7.0-2

2.6.7.0-3

2.6.7.0-4

418-XO-SCSOW-0122, RM Version, Geostationary eXtended Observations (GeoXO) Spacecraft Statement of Work (SOW)

After the CDR, the Government reserves the right to request the Contractor to hold a Design Modification Review (DMR) for Class I CCRs or other significant changes. The timing of the DMR will be upon mutual agreement between the Contractor and the Government.

If a DMR is held, the Contractor shall plan for a two (2) day review, not including resolution of RFAs.

The Contractor shall prepare and deliver a Design Modification Review (DMR) Data Package, plus updates and revisions, in accordance with CDRL # SR-06.

2.6.6 Component, Subassembly, and Subsystem Reviews

The Contractor shall plan and conduct component, subassembly, and subsystem reviews for Contractor developed and subcontracted developed hardware that warrant a formal design review process as identified in the Systems Engineering Management Plan, CDRL # SE-PLAN-02-1.

The Contractor shall conduct PDRs and CDRs for the components, subassemblies, and subsystems identified in CDRL # SE-PLAN-02-1.

The Contractor shall include in the component, subassembly, and subsystem reviews Government and Contractor's personnel and technical experts.

Component, subassembly, and subsystem reviews shall be chaired by the Contractor and staffed by independent reviewers for the hardware under review.

The Contractor shall include a Government representative as a co-chair for all subsystem reviews.

The Contractor shall provide ten (10) days prior notification for component, subassembly, and subsystem reviews so that Government representatives can be present.

The Contractor shall submit Component, Subassembly, and Subsystem Review Data Packages, plus updates and revisions, in accordance with CDRL # SR-07.

The Contractor shall document minutes from component, subassembly, and subsystem reviews and deliver the minutes as an addendum to CDRL # SR-07, Component, Subassembly, and Subsystem Review Data Packages.

2.6.7 Instrument Receiving Review (IRR)

The Contractor shall prepare and conduct an Instrument Receiving Review (IRR) in conjunction with each GFP instrument contractor prior to the shipping of each GFP instrument flight model, and test equipment from the GFP instrument contractor to the spacecraft Contractor facility.

The IRR shall establish the readiness of the spacecraft and include an evaluation of the spacecraft handling plans and procedures.

The Contractor shall plan for a half-day review for each instrument delivery.

Unless stipulated otherwise by the Government, the Contractor shall include Government personnel in the IRRs.

Page 15 of 77 Printed Wednesday, September 27, 2023

ID

SCSOW185

SCSOW186

SCSOW187

SCSOW188

SCSOW189

SCSOW190

SCSOW191

SCSOW192

SCSOW193

SCSOW194

SCSOW195

SCSOW921

SCSOW196

SCSOW197

SCSOW198

SCSOW199

Object Number

2.6.7.0-5

2.6.8

2.6.8.0-1

2.6.8.0-2

2.6.8.0-3

2.6.8.0-4

2.6.9

2.6.9.0-1

2.6.9.0-2

2.6.9.0-3

2.6.9.0-4

2.6.9.0-5

2.6.9.0-6

2.6.9.0-7

2.6.9.0-8

2.6.9.0-9

418-XO-SCSOW-0122, RM Version, Geostationary eXtended Observations (GeoXO) Spacecraft Statement of Work (SOW)

The Contractor shall provide seven (7) days advance notification so that Government representatives can be present.

2.6.8 Manufacturing Readiness Review (MRR)

The Contractor shall prepare and conduct Manufacturing Readiness Reviews (MRRs) prior to the start of manufacturing Printed Circuit Boards and components.

The MRRs shall include a review of any design non-conformances, status of drawings, status of build / manufacturing documentation, board / component level test procedures, facility and ground support equipment readiness, mission assurance / process control, and schedule.

Unless stipulated otherwise by the Government, the Contractor shall include Government personnel in the MRRs.

The Contractor shall provide seven (7) days advance notification so that Government representatives can be present.

2.6.9 Test Reviews

The Contractor shall prepare and conduct Test Readiness Reviews (TRRs) and Test Data Reviews (TDRs) for flight hardware and software.

Unless stipulated otherwise by the Government, the Contractor shall include Government personnel in TRRs and TDRs.

The Contractor shall prepare and conduct a TRR prior to the start of each of the following I&T events, including but not limited to: GFP instrument integration, testing of pressurized systems above Maximum Expected Operating Pressure (MEOP), initial deployments, Radio Frequency (RF) Airlink / Compatibility Testing, Mechanical Environments, Electromagnetic Interference / Electromagnetic Compatibility (EMI/EMC) testing, Thermal Balance testing, Thermal Vacuum testing, and End-to-End (ETE) Testing.

The Contractor shall prepare a TRR specific data package, in a Contractor defined format, and provide that package to the Government no later than five (5) days before the TRR.

The Contractor shall include at a minimum the applicable Test Procedures, GSE status and facility readiness in the TRR data package.

The Contractor shall conduct TDRs for data collected for hardware and software tests, subsystem level tests, spacecraft level tests, and satellite level tests.

The Contractor shall prepare and conduct a TDR of the finalized data and test results following the completion of each of the following I&T events including but not limited to: Regression…