Attachment A - NS1-SMBA-SOW-0002A_NS1 SMBA SOW_04172025.pdf

Effective Date: April 17, 2025 Expiration Date: April 17, 2030

NS1-SMBA-SOW-0002, Revision A Near Earth Orbit Network (NEON) Series-1 Project, Code 473

Near Earth Orbit Network (NEON) Series-1 Project

Sounder for Microwave-Based Applications Statement of Work

GSFC NEON Series-1 CMO

RELEASED

NOAA/NASA

Goddard Space Flight Center Greenbelt, Maryland

NS1 SMBA SOW NS1-SMBA-SOW-0002, Revision A ii

Near Earth Orbit Network (NEON)Series-1 Project Sounder for Microwave-Based Applications

Statement of Work Review/Signature/Approval Page

Prepared By:

Jessica Knizhnik SMBA Instrument Manager LEO Programs Division NASA Goddard Space Flight Center Code 473

Approved By:

Jessica Knizhnik SMBA Instrument Manager LEO Programs Division NASA Goddard Space Flight Center Code 473

Roger Clason Deputy Program Manager NEON Program NASA Goddard Space Flight Center Code 470

Electronic Approval available on-line at: https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm iii

Preface

This document is under NEON Series-1 (NS1) Project configuration control. Once this document is approved, NS1 approved changes are handled in accordance with Class I and Class II change control requirements as described in the Low Earth Orbit (LEO) Programs Division (LPD) Programs and Projects Configuration Management Procedure (CMP), and changes to this document shall be made by complete revision.

Any questions should be addressed to:

LEO/NEON Configuration Management Office

NASA/GSFC

Code 473 Greenbelt, MD 20771 iv

Change History Log

Revision Effective Date Description of Changes Revision – December 20, 2024 This version incorporates 470-CCR-24-0405 which was approved by the SMBA ERB on March 26, 2024, and incorporates NS1-CCR-0003 by the NS1 SMBA CCB on the effective date shown.

Revision A April 17, 2025 This version incorporates NS1-CCR-0011 which was approved by the NS1 SMBA CCB on the effective date shown.

Editorial change all instances of climate to weather.

v

Table of TBDs/TBRs/TBSs

Item No. Location Summary Individual/

Organization Due Date

1 VI.

Applicable Documents - Data Interface Requirement Document (IRD) (TBS)

Instrument Provider

VI. Applicable Documents - SMBA

Contamination Control Plan (CCP) (TBS)

VI. Applicable Documents - SMBA FVTS

Requirements Specification (TBS)

VI. Applicable Documents - SMBA FVTS

Interface Requirements Control Document

(IRCD) (TBS)

VI. Applicable Documents - Mission Assurance Compliance Matrix for the Sounder for Microwave-Based Applications (SMBA) (TBS)

6 VII.

Reference Documents - SMBA Flight Software and Table Update Delivery Process (TBS)

VII. Reference Documents - SMBA Continuous

Risk Management Plan (TBS)

VII. Reference Documents - Drill Template

Design Guidelines (TBS)

VII. Reference Documents - SMBA Flight

Spare Philosophy (TBS)

10 1.1.1

Government Oversight - The Contractor shall ensure that all software documentation, source code and software design models required for a NASA Software Independent Verification and Validation (IV&V) effort are made available to NASA IV&V personnel as required by the Government (TBR).

11 1.1.2

Government Resident Office Support - The Contractor shall provide facilities to support nominally TBS Government on-site representatives at the instrument development/build site, including private securable office space, furniture, file/storage area, telephones, and printer or printer access, as well as access to a shared conference room from Contract award through satellite on-orbit acceptance (nominally Launch + 6 months).

vi

12 1.1.3

Quality Management System - The developer shall implement a Quality Management System as required by the SMBA IMAR document, as tailored by SMBA Mission Assurance Compliance Matrix (TBS) within Contract TBS, Clause TBS, Attachment TBS. This document can be found in Attachment TBS of the Contract.

13 1.1.4.1 d)

Incorporation of Lower Tier Supplier Information - Problem Reports per the IMAR, as tailored by SMBA Mission Assurance Compliance Matrix (TBS) within Contract TBS, Clause TBS, Attachment TBS, typically summarized at the PMR as required.

14 1.3

Risk Management - The Contractor shall establish and maintain a comprehensive risk management program that meets the requirements of Contractor Risk Management Plans and the NEON Program Continuous Risk Management Plan (TBS).

15 Table 1-1.

Top-Level Instrument Reviews - CDRL References TBS

16 1.5.1.13

Technical Interchange Meetings and Other Reviews and Meetings - Per the IMAR, as tailored by SMBA Mission Assurance Compliance Matrix (TBS) within Contract TBS, Clause TBS, Attachment TBS, the Contractor shall invite the Government to participate in the Contractor’s Failure Review Board (FRB) and Material Review Board (MRB).

17 1.5.1.14

Subcontract and Subsystem Reviews - The Contractor shall submit Subsystem/Subcontract Review Data Packages in accordance with CDRL

(TBD).

18 3.1

Deviations and Waivers - Requests for deviations or waivers to the Government’s requirements shall be submitted to the Government’s Contracting Officer for Government approval per the IMAR, as tailored by SMBA Mission Assurance Compliance Matrix (NS1-SMA-REQ-vii

0002) within Contract TBS, Clause J.1, Attachment N (TBR), and CDRL SE-1.

19 4.2.11.1

Test and Verification - The Contractor shall plan and implement the testing of instrument-spacecraft interfaces with the Spacecraft-Instrument Interface Simulator (SIIS) provided by the spacecraft Contractor (TBR). Technical support will be provided by the spacecraft Contractor at the instrument simulator provider facility.

This will support early risk reduction of instrument-spacecraft interfaces.

20 4.2.12

NASA Independent Verification and Validation Support - The Contractor shall ensure that all software documentation and code required for NASA’s Software IV&V effort is made available to NASA IV&V personnel if directed by the Government

(TBR).

21 4.2.13

Software Maintenance - The delivery of a flight software patch or update shall be executed via the processes specified in the Project Flight Software and Table Update Delivery Process (TBS) (i.e., by sending a CD with the patch or uploading to a SharePoint folder).

22 4.2.15

Flight Software Deliverable - The Contractor shall deliver and periodically update a Flight Software Development Environment (CDRL SW-TBD)

23 4.3.3 Ground Support Equipment - RFI generator (TBR).

24 4.3.3

Ground Support Equipment - The Contractor shall provide two (TBR) additional sets of thermal control equipment for exclusive use at the spacecraft integration facility(ies).

25 5

Test Program - Contractor shall take and maintain test data in accordance with the Sensor Performance Specification, the approved test plan (CDRL IT-1) and the requirements. Problems, anomalies, failures, etc., shall be reported and treated in accordance with the IMAR document, as tailored by SMBA Mission Assurance Compliance Matrix (TBS) within Contract viii

TBS, Clause TBS, Attachment TBS, identified in Section IV for investigation, resolution, and corrective action.

26 5.6.2

Instrument Calibration - The Contractor shall perform calibration at a minimum of three instrument temperatures representing the SMBA instrument low operational, mid operational, and high operational temperatures (TBS).

27 5.6.2 Instrument Calibration - Intercalibration may be done at GSFC (TBR).

28 6.5

Sensor Database Support - The Contractor shall supply XML (TBR) formatted database inputs as required by the ground system.

29 6.6.5.6 a) Mission Rehearsals - Three (3) (TBR) instrument-focused rehearsals and dress rehearsals.

30 6.6.5.6 b) Three (3) (TBR) Support Operations Readiness Exercises as needed to prepare for and/or supplement Mission Rehearsals.

ix

Table of Contents

I. INTRODUCTION

II. SCOPE

III. NEON PROGRAM AND NEON SERIES-1 PROJECT OVERVIEW

IV. THE SOUNDER FOR MICROWAVE-BASED APPLICATIONS

V. DEFINITIONS

VI. APPLICABLE DOCUMENTS

VII. REFERENCE DOCUMENTS

VIII. PRECEDENCE

IX. WORK TO BE PERFORMED

1 MANAGEMENT

1.1 Program Management

1.1.1 Government Oversight

1.1.2 Government Resident Office Support

1.1.3 Quality Management System

1.1.4 Subcontract Management

1.2 Financial Management

1.2.1 Performance Measurement Baseline

1.2.2 Integrated Master Schedule

1.2.3 Work Breakdown Structure

1.2.4 Organization Breakdown Structure

1.2.5 Change Control

1.2.6 Estimate at Completion

1.2.7 Project Management Plan

1.3 Risk Management

1.4 Configuration Management

1.4.1 Configuration/Change Control Board

1.5 Reviews and Meetings

1.5.1 Contractor-Led Meetings and Reviews

1.5.2 Government-Chaired Instrument Reviews

1.5.3 Higher-Level Reviews

1.6 Data Retention

2 SYSTEMS ENGINEERING

2.1 Deviations and Waivers

2.2 Requirements Analyses, Derivations, and Allocations

2.2.1 Technical Performance Metrics

2.2.2 Instrument Interface

2.3 Contamination Control

2.4 Design Engineering

2.5 Design, Analysis, and Verification Documentation

x

2.5.1 Design Analyses

2.5.2 Trending

2.6 Special Studies

2.7 Constraints

3 MISSION ASSURANCE

3.1 Deviations and Waivers

3.2 Equipment Tagging

4 FABRICATION AND ASSEMBLY

4.1 Spares

4.2 Software Development

4.2.1 Software Development Plan

4.2.2 Software Configuration Management

4.2.3 Software Requirements Specification

4.2.4 Software Detailed Design

4.2.5 Instrument Software Development Environment

4.2.6 Software Testing

4.2.7 Software Version Description

4.2.8 Software User Manual

4.2.9 Software Reviews

4.2.10 Software Measures (Metrics)

4.2.11 Operational Simulator Software

4.2.12 NASA Independent Verification and Validation Support

4.2.13 Software Maintenance

4.2.14 Sensor Data Sets

4.2.15 Flight Software Deliverable

4.3 Hardware

4.3.1 Engineering Test Unit

4.3.2 Flight Instruments

4.3.3 Ground Support Equipment

4.3.4 Operational Simulator

4.3.5 Software Testbench

4.4 Deliverable Documentation

5 TEST PROGRAM

5.1 Spectral Response Functions

5.2 Radio Frequency Interference

5.3 Antenna Pattern Measurements

5.3.1 Plane Pattern Cuts

5.3.2 Measurement Polarization

5.3.3 Dynamic Range

5.3.4 Amplitude Accuracy

5.3.5 Angular Range and Interval

5.3.6 Beam Positions Required

5.4 Test Readiness Reviews

5.4.1 Test Process Decision Meetings

xi

5.5 Pre-Environmental Review

5.6 Instrument Test and Calibration

5.6.1 Instrument Program Test Plan

5.6.2 Instrument Calibration

5.6.3 Calibration Test Equipment

5.6.4 Test Software Validation Plan

5.6.5 Test Procedures

5.6.6 Test Reports and Test Data

5.7 Verification and Validation

5.7.1 Verification & Validation Plan

5.7.2 Verification Reports

6 DELIVERY

6.1 Acceptance or End Item Data Package

6.2 Packaging, Handling, Storage, and Transportation

6.3 Pre-Ship Review

6.4 Delivery, Checkout, and Acceptance

6.4.1 Hardware Delivery Documentation

6.4.2 Documentation Delivered with Hardware

6.4.3 Photographic Documentation

6.4.4 Test Data Files

6.5 Sensor Database Support

6.5.1 Sensor Command and Telemetry Database Support

6.5.2 Instrument Mission Data Structure Definition Support

6.5.3 Instrument Memory Table Support

6.6 Instrument Post-Delivery Support

6.6.1 General Roles and Responsibilities (PDSP and PDS Phases)

6.6.2 System Integration and Test Support

6.6.3 Flight Vehicle Test Suite Support

6.6.4 Launch Site Support

6.6.5 Mission System Integration Support

6.6.6 Commissioning and Post-Launch Support

6.6.7 Post Delivery and Post-Launch Sustaining Engineering and Cal/Val

APPENDIX A NPR 7150.2A TAILORED COMPLIANCE MATRIX

APPENDIX B ABBREVIATIONS AND ACRONYMS

List of Figures

Figure III-1. Notional NEON Series-1 Project Architecture Figure 5-1. Notional Noise Power Spectral Density

List of Tables

Table 1-1. Top-Level Instrument Reviews

I. INTRODUCTION

The Sounder for Microwave-Based Applications (SMBA) is a passive microwave instrument that produces global atmospheric temperature and moisture profiles. SMBA provides microwave data to support temperature and humidity sounding data in cloud covered and clear-sky conditions.

The Instrument has a risk classification of tailored Class C as per Goddard Procedural Requirement (GPR) 8705.4A.

This Statement of Work (SOW) covers the work required to develop, fabricate, integrate, test, analyze, verify, deliver, and provide post-launch support for the SMBA instruments required for the Near Earth Orbit Network (NEON) Program.

II. SCOPE

This SOW reflects the Contractor’s scope and period of performance as defined in the Contract.

Throughout the remainder of the document, the instrument supplier will be referred to as the Contractor. The National Aeronautics and Space Administration (NASA)/Goddard Space Flight Center (GSFC), including its support services Contractors, will be referred to as the Government.

This SOW and the Contract Data Requirements List (CDRL) (NS1-SMBA-CDRL-0001) identify the deliverables associated with the SMBA instrument. The Contractor shall meet the requirements of all contractual documents. The Contractor shall facilitate insight by the GSFC Program Office into the instrument progress and status. Compliance with the requirements stated herein shall be the responsibility of the Government and the Contractor.

This SOW defines the minimum effort required of the Contractor that shall include the business and technical management including necessary related Government reviews and discussions, design, engineering analyses, data reduction, data presentations, technical reviews, development, fabrication, integration, test, evaluation, delivery, and support for the SMBA instruments and software in support of the NEON Program. This support shall include post-delivery support from delivery of the SMBA through the period of performance of this Contract. This SOW defines the roles, responsibilities, and obligations between the Government and the Contractor.

The Contractor shall develop this instrument using sound engineering principles founded in industry best practices, stated Government standards and requirements, and agreed-upon Contractor internal standards and policies.

This SOW covers all SMBA instrument builds. Any requirement that is only applicable to the first flight unit or any other unit is specifically called out. Where no clarification regarding applicability is provided, the requirements are applicable to all flight units.

III. NEON PROGRAM AND NEON SERIES-1 PROJECT OVERVIEW

The NEON Program, a part of the National Environmental Satellite, Data, and Information Service Office of Low Earth Orbit (LEO) Observations, provides a framework to provide global measurements of Earth systems. These environmental measurements will be able to support a wide variety of atmospheric, terrestrial, marine, and polar observations. The data includes the numerical weather prediction models, fire and flood models, atmospheric chemistry observations, and multiple land imagery products that have been a crucial piece of the National Oceanic and Atmospheric Administration (NOAA) strategic goal to create a "Weather Ready Nation" and which provide essential information to NOAA's broader environmental stewardship mission. Following the recommendations from the 2017 NOAA Satellite Observation System Architecture (NSOSA) study, the NEON Program intends to use a combination of small and medium satellite platforms in a disaggregated architecture. This approach will provide an efficient means of filling gaps quickly and taking advantage of emerging remote sensing technologies.

To execute a disaggregated LEO architecture and other NSOSA recommendations, the NEON Program plans to:

Use industry’s significant investment of funding, expertise, and innovation in space and space systems technology.

Deploy NOAA observation system assets where and when they are most needed, enabled by shorter development timelines and more frequent launches.

Leverage smaller instruments, satellites, and evolving small launch vehicles; and Achieve greater agility to incorporate continuous advancement, using new business models and partners.

The NEON Program will accomplish these goals by continuing to leverage the multi-decadal partnership between NOAA and NASA.

The NEON Series-1 Project is an initial operational project for the NEON Program featuring the development, integration, test, launch, and science operations of the SMBA instrument – a successor to the Advanced Technology Microwave Sounder (ATMS) instrument, versions of which are on each of the Joint Polar Satellite System (JPSS) satellites. It will allow the NEON Program to provide continuity with the existing JPSS-era microwave sounder measurements as well as leverage newer technological advances to advance the collection of hyperspectral microwave sounding data that is crucial to numerical weather prediction models.

Figure III-1. Notional NEON Series-1 Project Architecture

Utilizing elements and best practices of the commercial space industry to meet federal program level requirements, the NEON Series-1 Project will demonstrate the NEON Program can provide operational hyperspectral microwave sounding observation capabilities with a small satellite that can be flexibly deployed to a variety of operational orbits. This first operational project, consisting of four individual flight missions to two distinct sun synchronous orbits (local time of ascending nodes (LTAN) of 1330 and 1730), will demonstrate the NEON disaggregated mission portfolio that provides the program with the flexibility of placing hyperspectral microwave sounders in either operational orbit (1330 or 1730 LTAN), at any desired launch cadence as the program needs to support hyperspectral microwave sounder needs.

The NEON Series-1 Project will also leverage mission assurance practices relative to established commercial New Space missions and establish a referenceable knowledge base of rapid procurement practices that will benefit the future environmental observation missions planned in the high launch tempo NEON Program.

The NEON Series-1 Project is Class C as per GPR 8705.4, which applies the appropriate NASA management controls, systems engineering processes, mission assurance requirements and risk management processes. Whereas reliability requirements are not levied in this document, select areas of redundancy should be considered that may offer reasonable improvement to mission success.

IV. THE SOUNDER FOR MICROWAVE-BASED APPLICATIONS

SMBA is the principal instrument aboard the NEON Series-1 satellite. The instrument (hereafter referred to as the “SMBA instrument” or simply the “instrument”), is a cross-track microwave sounder that collects hyperspectral microwave radiometric data that are used to calculate the vertical distribution of temperature (T), moisture (q), and pressure in the Earth’s atmosphere.

The instrument measures atmospheric radiances within the microwave range of approximately 20-300 GHz over a swath width of approximately 2,530 km from an altitude of 824 km.

Hyperspectral capability indicates fine spectral resolution. Fine spectral resolution is beneficial for both science and radio frequency interference (RFI) detection capability. Hyperspectral microwave capability refers to microwave sounding systems with approximately 100 or more channels. The increased number of channels results in a finer spectral resolution than is achieved by traditional microwave sounding techniques over the same bandwidth.

Instrument data is acquired continuously, stored on-board the satellite, and subsequently downlinked to a ground network for capture, preprocessing, and routing to meteorological centers.

The instrument produces Raw Data Records (RDR) in an uncalibrated form. Engineering, instrument telemetry, science data, radiometric, and spectral calibration data is provided to enable the RDRs to be calibrated and geolocated. In addition, diagnostic RDR data may be acquired for testing purposes. The data are sent to the NOAA Ground System where they are used as input to science algorithms that generate Temperature Data Records, Sensor Data Records, and Environmental Data Records.

V. DEFINITIONS

Contractor – The developer of the item of reference. If the term Contractor is used in this document without specific reference to an item (e.g., SMBA, ground support equipment (GSE), etc.), then the term shall be interpreted to imply the SMBA Contractor. In all cases, the term Contractor also implies any and all associated suppliers and subcontractors.

Government – Federal Civil Servants and support Contractors (Contractors that represent NASA or are delegates for NASA).

Shall – Compliance by the Contractor is mandatory. Any deviations from these contractually imposed mandatory requirements require the approval of the Contracting Officer.

Should – Preferred good practices are identified by “should” statements. “Should” designates performance, which is requested, but not mandatory. Noncompliance of a “should” statement does not require Government approval but shall be addressed at the earliest applicable project milestone.

May – At the discretion of the Contractor or Government.

Will – Designates the intent of the Government.

Applicable documents – The term “applicable documents” denotes Government-prepared and controlled documents and industry standards documents that levy additional requirements on the Contractor. The Contractor is required to comply with the documents, or the tailored version of the documents provided by the Government.

Reference documents – The term “reference documents” denotes documents that amplify or clarify the information presented in this document. The Contractor is not required to meet any requirements listed within these documents.

TBS – The term “to be supplied” (TBS) refers to a document or information that will be developed or provided.

TBR – The term “to be reviewed” (TBR) means that the stated requirements or values will be reviewed for appropriateness jointly by the Contractor and the Government and the information may be changed. The TBR requirement/value remains a requirement until formal process of configuration change review, approval, and Contract modification.

TBP – The term “to be proposed” (TBP) indicates required Contractor fill-ins as part of the solicitation process.

TBD – The term “to be determined” (TBD) identifies a missing requirement or value; indicates further research or analysis is needed to determine the information. All changes to resolve these items will be completed through a formal process of configuration change review, approval, and Contract modification.

Instrument – The SMBA flight hardware, support equipment (i.e., system test equipment (STE)/GSE), software, documentation and/or data necessary to fulfill the requirements of the Contract and this SOW.

Satellite – The term “satellite” refers to the NEON Series-1 spacecraft bus integrated with the flight instrument(s). The term “satellite” is equivalent to the term “satellite” used in other NASA and NEON Program documents.

Class I – A change that affects a configuration item's form, fit, or function. This could include changes to baselined documentation, technical requirements, Contract end items, interfaces, weight, power, data rate allocations, technical risks, or science performance. All proposed Class I changes require Configuration Control Board (CCB) approval.

Class II – A change that does not affect a configuration item's form, fit, or function. This could include changes to documentation only, minor hardware changes, or drawing changes that do not affect a baseline or interface. Class II changes do not require Project CCB review unless they will be written against CM-controlled documents.

VI. APPLICABLE DOCUMENTS

The Applicable Documents listed in this section apply directly to the performance of this SOW to the extent specified and invoked by this SOW. The Contractor shall comply with the documents to the extent specified herein. The Contract, Attachment N, provides the current issue revision and issue date as well as any additional Configuration Change Requests (CCR) for the applicable documents.

Document No. Document Name NS1-SMBA-CDRL-0001 SMBA Contracts Data Requirements List (CDRL) NS1-SMA-REQ-0002 SMBA Instruments Mission Assurance Requirements (IMAR) NS1-SMBA-REQ-0001 SMBA Performance Requirements Document (PRD) TBS Data Interface Requirement Document (IRD) TBS SMBA Contamination Control Plan (CCP) TBS SMBA FVTS Requirements Specification TBS SMBA FVTS Interface Requirements Control Document (IRCD) TBS Mission Assurance Compliance Matrix for the Sounder for

Microwave-Based Applications (SMBA) GSFC-STD-1001 Criteria for Flight and Flight Support Systems Life Cycle Reviews GPR7120.4 Risk Management GPR 8705.4A Risk Classification Guidelines and Risk-Based SMA Practices for

GSFC Payloads and Systems

VII. REFERENCE DOCUMENTS

The documents listed in this section are those documents referenced in the SOW which contain information relating to the work required, but which do not constitute requirements.

Document No. Document Name TBS SMBA Flight Software and Table Update Delivery Process

TBS SMBA Continuous Risk Management Plan TBS Drill Template Design Guidelines TBS SMBA Flight Spare Philosophy NPR 8715.3 NASA Safety Manual NPR 8000.4 Risk Management Procedural Requirements GSFC-STD-1000 GOLD Rules NPR 7123.1 NASA Systems Engineering Processes and Requirements

NASA SP-2016-6105 NASA Systems Engineering Handbook

GSFC-STD-7000 General Environmental Verification Standard (GEVS)

NPR 7150.2 NASA Software Engineering Requirements GPR 8700.6 Engineering Peer Reviews GPR 8700.4 Integrated Independent Reviews NPR 8621.1 NASA Procedures and Guidelines for Mishap Reporting, Investigating, and Recordkeeping

ANSI/EIA748 Industry Guide for Earned Value Management

IEST-STD-CC1246D Product Cleanliness Levels and Contamination Control Program

470-LEO-PROC-00010 Low Earth Orbit (LEO) Programs Division (LPD) Configuration Management Procedure

VIII. PRECEDENCE

In the case of conflicting requirements, the order of precedence of documents not specifically called out in the Contract is: The Contract takes precedence over the SOW, followed by the CDRL, Instrument Mission Assurance Requirements (IMAR), Performance Requirements Document (PRD), Interface Control Documents (ICD), and the remaining applicable documents.

In the event of an inconsistency between any of the reference documents herein and the requirements of this SOW, the SOW shall take precedence. Any conflicts discovered by the parties between the requirements in this SOW and any referenced specification herein shall be brought to the attention of the other party for resolution.

IX. WORK TO BE PERFORMED

This section, along with the CDRL, GSFC NS1-SMBA-CDRL-0001, describes the specific work to be accomplished by the Contractor. In accordance with the requirements of this document, the Contract, all associated requirements documents, other attachments and applicable documents to this Contract, the Contractor shall provide the effort and resources that include, but are not limited to personnel, materials, equipment, and facilities necessary for the successful and on-time design, analysis, development, fabrication, assembly, integration, test, calibration, qualification, and delivery and support of the instrument. The Contractor shall also provide the personnel, materials, equipment necessary to support Satellite Integration and Test, support to mission-level activities, training, and post-delivery support of the instrument throughout the performance of this Contract.

The Contractor shall deliver to the Government an instrument that is fully tested and calibrated with verified compliance to the requirements of this Contract. The Contractor shall support the development of bilateral instrument documents, analyses, and models, which define the details of the instrument-to-spacecraft interface and instrument accommodation and operating information.

1 MANAGEMENT

1.1 Program Management

The Contractor shall appoint a dedicated Program Manager (PM) to direct and manage the SMBA instrument development. The Contractor’s PM shall have responsibility for the overall technical performance, resource management, and schedule management of the contractual effort and all subcontracts. The Contractor’s designated PM shall report to a level of company management appropriate to ensure prompt resolution of all problems. The PM shall maintain close liaison with the designated Contracting Officer’s Representative (COR) and Instrument Manager and be responsible for effective and timely communication regarding program performance. The Contractor’s PM shall ensure that all requirements of this Contract are accomplished successfully and on-time.

1.1.1 Government Oversight

To meet the mission and schedule requirements, the Government intends to establish a collaborative teaming environment with the Contractor to gain adequate insight of designs, Assembly, Integration, and Test activities, and operations. The Contractor’s management, tracking, control, and reporting processes shall facilitate insight by the GSFC Program Office into the instrument progress and status. The Contractor shall provide the Government virtual access, on and off site, to the instrument configuration management, risk management, and planning and scheduling systems. The Contractor shall provide virtual access, on and off site, to the instrument anomaly reporting system.

The Government will maintain a SharePoint, or similar, on-line collaborative space where the Contractor may share informal information with the Government.

The Government shall have virtual access, from both inside and outside the Contractor’s facility, to documents and data, including drawings and the requirements verification database.

The Contractor shall open Government attendance to Contractor and subcontractor/lower tier suppliers’ internal data, reviews, audits, meetings, and other activities within the scope of the Contract where the Government has determined based on Contractor and/or subcontractor performance and/or risk to the program a need for such oversight. The Contractor shall notify the COR and the Government resident office representatives of meetings, reviews, or tests in sufficient time to permit meaningful Government participation.

The Contractor shall ensure that all software documentation, source code and software design models required for a NASA Software Independent Verification and Validation (IV&V) effort are made available to NASA IV&V personnel as required by the Government (TBR). The Contractor shall allow NASA IV&V review and participation before final product delivery to the Government.

1.1.2 Government Resident Office Support

To facilitate insight, the Government will establish a resident office that will include management, systems engineering, and quality assurance representation. The resident office representatives will attend the Contractor’s daily meetings to stay current on activities and issues.

The Government will staff a contributive impactful resident office at the Contractor’s facility to enable quick and efficient communication, problem resolution, and requirements clarification as necessary. The Government Resident Office will follow the Contractor’s development and observe its processes including assembly, test, and inspections. The intent is to minimize overlaying Government processes and deliverables as much as possible with minimal disruptions to the development schedule. The Contractor shall provide facilities to support nominally TBS Government on-site representatives at the instrument development/build site, including private securable office space, furniture, file/storage area, telephones, and printer or printer access, as well as access to a shared conference room from Contract award through satellite on-orbit acceptance (nominally Launch + 6 months). The Contractor shall provide within these offices high-speed (broadband) internet access and periodic wireless access, as required, to an internet service provider within the Contractor’s facility to allow for access to the GSFC network.

1.1.3 Quality Management System

The developer shall implement a Quality Management System as required by the SMBA IMAR document, as tailored by SMBA Mission Assurance Compliance Matrix (TBS) within Contract TBS, Clause TBS, Attachment TBS. This document can be found in Attachment TBS of the Contract.

1.1.4 Subcontract Management

The Contractor shall actively manage its Lower-Tier Suppliers (LTS) including robust mission and quality assurance focused oversight and technical insight. The Contractor shall routinely verify LTS adherence to both Contractor-flowed down and approved subcontractor processes.

The Contractor shall meet the requirements in the following sections as noted to provide the Government with visibility into LTS activities. The Contractor shall maintain a schedule of onsite visits to its key suppliers or those presenting risk to the program including planned and actual surveillance audits and be available for review at each Project Management Review (PMR). The Government may require onsite personnel at LTS facilities in cases of frequent anomalies.

1.1.4.1 Incorporation of Lower Tier Supplier Information

The Contractor shall provide to the Government the following LTS information at a minimum:

a) Earned Value Management System (EVMS) and financial data as required herein.

b) Schedule and Schedule Reporting, typically via the Integrated Master Schedule (IMS).

c) Project Status Reviews and/or Reports, typically via the PMR.

d) Problem Reports per the IMAR, as tailored by SMBA Mission Assurance Compliance

Matrix (TBS) within Contract TBS, Clause TBS, Attachment TBS, typically summarized at the PMR as required.

e) Design, Manufacturing, Integration and Test Review schedule, and contact information, minutes, or material discussed.

f) LTS Risk items, risk mitigation tasks and status of risks shall be reported and included in each review if required and/or as requested by the Government.

1.1.4.2 Meetings with Lower Tier Suppliers

The Contractor shall invite the Government to all formal/major reviews and acceptance activities at LTSs.

1.1.4.3 Flow Down of Requirements to Lower-Tier Suppliers

The Contractor shall flow all applicable requirements and controls stated or referenced herein to its LTSs. The LTSs shall supply a compliance matrix delineating their compliance with each of the requirements, provided to the Government upon request.

1.1.4.4 End Item Data Packages from Lower Tier Suppliers

The Contractor shall submit End Item Data Packages (EIDP) from LTSs in accordance with

CDRL MA-32.

1.2 Financial Management

The Contractor shall use and maintain in performance of this Contract an EVMS. The Contractor's system shall meet the guidelines and be maintained in accordance with the EVMS requirements described in this Contract, under NASA Federal Acquisition Regulation Supplement Clause 1852.234-2. The EVMS shall be supported by the Contractor's management processes and systems and in accordance with the Contractor’s EVM Plan. Reference the Contract Performance Report delivered as part of the Integrated Program Management Report

(CDRL PM-4).

1.2.1 Performance Measurement Baseline

The Contractor shall define the Performance Measurement Baseline (PMB), completing a time-phased integrated plan to unify technical scope, schedule, and budget into an overall plan in accordance with the Contractor’s EVM Implementation Plan. The Contractor shall define the work scope, establish a schedule for accomplishing the work, and estimate the resources required to accomplish the work. The Government will complete a PMB cost and schedule validation as required.

1.2.2 Integrated Master Schedule

The Contractor shall submit an IMS to be used to manage this instrument development effort.

(Refer to CDRL PM-4.)

The Contractor shall submit and maintain a comprehensive listing of all external Giver-Receiver (G-R) items also referred to as Receive-Deliver items to provide the project a description of each G-R indicated in the IMS. (Refer to CDRL PM-4.)

1.2.3 Work Breakdown Structure

The Contractor shall develop and maintain the Work Breakdown Structure (WBS) and WBS dictionary in accordance with CDRL PM-2. The Contractor uses the WBS as the primary framework for Contract planning, budgeting, and reporting of the cost, schedule, and technical performance status to the Government. The WBS structure shall be established by the Contractor (based on guidelines provided by the Government) and shall be reported to the Government at a minimum of Level 3 decomposition. The Contractor shall maintain a WBS at a minimum one level lower than reporting Level 3. Prior notification to the Government of WBS changes at Level 3 or higher shall be required before implementation (Reference WBS CDRL PM-2). The WBS through level 3 shall be established in conjunction with the NEON Financial Management team prior to submittal of a proposal in accordance with this SOW.

1.2.4 Organization Breakdown Structure

The Contractor shall develop and maintain the Organization Breakdown Structure (OBS), outlining hierarchical arrangement of the Contractor’s management organization, which human entity is responsible for the work and the associated reporting relationships. The OBS shall have the same type of definition as the WBS, accomplished through a charter of functions and responsibilities and is the organizational equivalent to a WBS dictionary.

1.2.5 Change Control

In order to maintain baseline integrity and assure oversight of the baseline change control process, the Contractor shall use a formalized change control process for all Baseline Change Requests (BCR) via the CCB process established by the Contractor. The Government shall be a member of the BCR CCB and shall have approval authority for any BCR over $250,000 or any schedule BCR that impacts the critical path. BCRs incorporating rolling wave changes and/or new scope do not require Government approval. In the event the Government does not attend a CCB, the Contractor shall provide notification, via e-mail submittal, of all BCRs. The Government will respond within three (3) working days, provided that pre-coordination of the BCR has occurred. Notification shall occur prior to implementation of the BCR into the baseline and annotate the type of change, Control Account Manager, Control Account impacted, identification of effects, the value of the change (if applicable), internal Contractor approval, and the accounting month for which the BCR will be implemented.

1.2.6 Estimate at Completion

Once the PMB has been established and approved by the Government, a comprehensive Estimate at Completion shall be developed by the Contractor as part of the recurring detailed budget and planning process.

1.2.7 Project Management Plan

The Contractor shall perform to and maintain a Project Management Plan (PMP) in accordance with CDRL PM-7.

1.3 Risk Management

The Contractor shall establish and maintain a comprehensive risk management program that meets the requirements of Contractor Risk Management Plans and the NEON Program Continuous Risk Management Plan (TBS). All CCB approved, authorized, and funded risk burn-down (mitigation) activities shall be integrated into the IMS. The Contractor shall invite the Government to attend Contractor Risk Management Board meetings. The Contractor shall document, and report all identified risks in accordance with the program’s approved Risk Management Plan (RMP) (CDRL PM-8) and the LPD RMP (470-LEO-PLAN-00009). The Contractor shall address identified risk areas at program status reviews. The Contractor shall maintain a Risk List throughout the program life cycle and add mitigation steps to the IMS, which shall be made available to the Government upon request.

1.4 Configuration Management

The Contractor shall perform configuration management (CM) in accordance with the Configuration Management Plan, in accordance with CDRL PM-6. The Contractor shall maintain and employ a configuration management system to demonstrate that the configuration item conforms to current approved documentation. The Contractor shall maintain configuration of flight hardware, software, electrical ground support equipment (EGSE) and mechanical ground support equipment (MGSE) as well as any equipment which mates to flight hardware throughout all phases of assembly and test. The Software Configuration Management Plan (CDRL SW-3) is discussed in Section 4.3.2.

The Contractor shall perform and document configuration verification as parts and assemblies are incorporated into higher-level assemblies and at major program milestones (in accordance with GSFC-STD-1001).

The Contractor shall submit a waiver or deviation request for any non-compliance to any requirement. Any flight item that is found to be non-compliant may be re-worked or replaced with a compliant item.

The Contractor shall prepare and provide, as a minimum, the following configuration control documentation:

a) CCB status reported at the Monthly Program Management Review in accordance with

CDRL PM-1.

b) Engineering Drawings in accordance with CDRL SE-3.

c) The Configuration Item Identification List and the Computer Software Configuration

Items (CSCI) in accordance with CDRL RE-8.

1.4.1 Configuration/Change Control Board

The Contractor shall be a member of the SMBA GSFC CCB and required to participate in the review of project-level documents which are applicable to the Instrument Contractor (i.e., plans, specs, support of ICD updates, satellite integration and test (I&T) documents, etc.). The Government shall be invited to all Contractor Instrument CCBs having the right to participate at its discretion. Government approval is required prior to the implementation of any Class I change. For Class I and II definitions see 470-LEO-PROC-00010, LPD Configuration Management Procedure. Class I changes are modifications affecting the following:

a) Contractually specified form, fit and function.

b) Government Furnished Equipment.

c) Cost to the Government.

d) Contractual deliveries.

e) Schedule Contract milestones.

f) Interchangeability of any item/unit that has already been delivered (excludes launched hardware).

All other changes are considered Class II or lower and may be incorporated without Government authorization. The Contractor shall notify the Government of change classifications and provide all reasonable evidence required in support of change classifications. The Government reserves the right to upgrade any change classification to Class I if the Government determines the change to be improperly classified according to the Class I/Class II definitions above.

1.4.1.1 Design Changes

The Contractor shall document and control engineering changes as either Class I or Class II. CCRs shall be forwarded to the Government in accordance with CDRL SE-1, Engineering Change Requests.

1.4.1.2 Drawings and Drawing List

The Contractor shall prepare and maintain a complete set of flight equipment drawings and drawings for GSE. The drawings shall be maintained at the Contractor’s facility. The Contractor shall make available to the Government drawings and an Indentured Drawing List for each hardware type upon request.

1.5 Reviews and Meetings

The Contractor shall conduct, host, prepare, and present instrument reviews and provide review packages in accordance with the stated CDRL/Data Item Description (NS1-SMBA-CDRL-0001) for each sensor Instrument as shown in Table 1.

A top-level overview of the reviews to be conducted is provided in Table 1, below. Further details for each review can be found in the subsequent sections of this SOW and the data pack requirements are provided in the CDRL.

Reviews shall be considered complete and approved by the Government when all outstanding action items are closed or a detailed plan for closure is submitted by the Contractor and approved by the Government.

Table 1-1. Top-Level Instrument Reviews Review Applicability CDRL

Reference Chair

Integrated Baseline Review

(IBR)

FM1 RE-TBS Government

System Requirements Review (SRR)

FM1* RE-TBS Government

System Definition Review (SDR)

FM1* RE-TBS Government

Preliminary Design Review

(PDR)

FM1* RE-TBS Government

ETU Pre-Build Review

ETU RE-TBS Contractor

ETU Test Summary Review

ETU RE-TBS Contractor

Critical Design Review (CDR)

FM1* RE-TBS Government

*If any changes are made to the instrument (design, processes, procedures, etc.), this review may be required at the Government’s discretion, depending on the magnitude of the changes.

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

All reviews and meetings shall provide a virtual attendance option.

1.5.1 Contractor-Led Meetings and Reviews

The Contractor shall implement a thorough technical peer review process of component and subsystem designs, conduct independent technical assessments of instrument activities, and hold formal design reviews. The reviews listed in this section should not be considered a complete set of reviews for the Contractor’s program. Additional reviews that the Contractor deems necessary to successfully execute the program will be conducted at the Contractor’s discretion.

The Contractor shall develop and apply a process for capturing and responding to action items assigned during Contractor-led meetings and reviews. The Contractor shall record and deliver meeting minutes for the meetings and reviews called out in this section.

1.5.1.1 Kickoff Meeting

The Contractor shall hold a program kickoff meeting approximately two weeks after the Contract award.

The kickoff meeting agenda shall be developed jointly with the Government and should include:

a) An overview and introduction to the organization and personnel (both vendor and

Government teams).

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

c) A summary of regularly scheduled meetings and a tentative meeting schedule for the first

6 months (PMRs, tabletop reviews, peer reviews, project milestone reviews, etc.).

d) An overview of the instrument 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 & Mission Assurance (SMA) and quality processes.

i) Overview of vendor facilities (tour, if possible).

Review Applicability CDRL Reference

Chair

Manufacturing Readiness Review (MRR)

All Flight Instruments

Contractor

Pre- Environmental Review (PER)

All Flight Instruments

RE-TBS Government

Pre-Ship Review

(PSR)

All Flight Instruments

RE-TBS Government

The kickoff meeting will nominally be held at the vendor facility. Assumed duration is one day.

1.5.1.2 Program Management Review

The Contractor shall provide for monthly PMRs in accordance with CDRL PM-1. These reviews will generally be held at the Contractor’s facility, but may be held at the Government’s facility, with mutual agreement between the Government and Contractor.

The PMR shall be designated to provide a management-level review of technical, schedule, and programmatic activities. A PMR will typically consist of a meeting to review formal status and splinter meetings to address special topics to be mutually determined prior to each review. The addition of special topics will be coordinated between the Government and Contractor Managers.

Up to twice a year, the Government will coordinate an integrated PMR where the Instrument Contractor and the Spacecraft Contractor shall present status and issues. This review will be in lieu of the monthly PMR for that month. The Contractor shall plan to travel to each combined review through delivery. The integrated PMR will rotate between the SMBA Instrument Contractor’s facility and the Spacecraft Contractor’s facility. The semi-annual PMR may be planned periodically at GSFC in Greenbelt, Maryland.

1.5.1.3 Integrated Baseline Review

The Contractor shall conduct an IBR to assess and validate the PMB in accordance with CDRL RE-6. The Contractor shall support a formal IBR conducted by the Government with Government participation. This review will be established by the Government as early as practicable and conducted in accordance with NASA requirements within 180 days of Contract award or formal Contract definitization. Additional baseline reviews may be required when substantial changes are made to the baseline (e.g., subsequent detailed planning, including routine rolling wave planning and program re-planning resulting from incorporation of significant Contract modifications). The IBR will be tailored to meet the needs of the NEON Program.

The Government will coordinate the timeframe and scope of the IBR with the Contractor. The IBR will ensure that the PMB captures the entire scope of work, is consistent with the Contract schedule requirements and has an adequate resource plan. The IBR team shall include Government personnel.

1.5.1.4 Engineering Test Unit Pre-Build Review

The Contractor shall hold an Engineering Test Unit (ETU) Pre-Build Review to get Government agreement for the ETU Program – the scope and fidelity of the ETU and any demonstrators (e.g.

breadboards, simulators, etc.), what testing will be done, and an attempt to define priorities ahead of time to aid in quicker decision making should there be cost, schedule, procurement, or facilities challenges that require an adjustment to the scope or fidelity of the ETU.

The Contractor shall deliver the ETU Pre-Build Review data package in accordance with CDRL

RE-12.

1.5.1.5 ETU Test Summary Review

The Contractor shall hold an ETU Test Summary Review to present the actual testing conducted compared to the plan, the results and any lessons of that testing, and any subsequent changes, either to the ETU and/or the flight design.

The ETU Test Summary Review may be combined with the Critical Design Review (CDR) if mutually agreed by the Contractor and Government.

The Contractor shall deliver the ETU Test Summary Review data package in accordance with

CDRL RE-13.

1.5.1.6 Design Modification Reviews

Whenever there is a design change to the flight instrument that the Government feels cannot be adequately reviewed by other means, the Contractor shall hold a Design Modification Review (DMR) to review these changes at the Government’s request.