Attachment A SOW 418 XO LMXSOW 0116 Version 1.00.pdf

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

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

Geostationary Extended Observations (GeoXO) Lightning Mapper (LMX) Statement of Work (SOW)

Signature page

Prepared by:

Electronically approved by: 06/23/2023

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

Reviewed by:

Electronically approved by: 06/28/2023

Tina Gentry Date GeoXO Flight Project, Instrument Manager NOAA GSFC, Code 418

Approved by:

Electronically approved by: 06/29/2023

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

/GeoXO Flight Project LMX Lightning Mapper

LMXSOW

418-XO-LMXSOW-0116, RM Version, Geostationary eXtended Observations (GeoXO) Lightning Mapper (LMX) Statement of Work (SOW) Phase B

Version: 1.0 Printed by: hlhedger Printed on: Thursday, June 29, 2023

No filter applied.

No sort applied.

Generated from DOORS 9.7.2.4

Contents

1 1Program Scope and Management

1.1 1Period of Contract Coverage

1.2 2Documents and Terminology

1.2.1 2Applicable Documents

1.2.2 2Reference Documents

1.2.3 2Terminology

1.3 3Project Management

1.4 3Resource Management

1.5 4Risk Management

1.6 4Configuration and Information Management

1.7 6Special Engineering Analysis / Task Orders

1.8 6Project Review Requirements

1.8.1 6Kick-off Meeting and Requirements Walkthrough

1.8.2 7Project Management Status Reviews

1.8.3 7Integrated Baseline Review (IBR)

1.8.4 8Peer Reviews

1.8.5 8Instrument Milestone Reviews

1.8.5.1 9System Requirements/Definition Review (SRR/SDR)

1.8.5.2 9Preliminary Design Review (PDR)

1.8.5.3 9Critical Design Review (CDR)

1.8.5.4 9Pre-Environmental Review (PER) - Each Flight Model

1.8.5.5 10Pre-Storage/Pre-Shipment Review (PSR) - Each Flight Model

1.8.5.6 10Design Modification Reviews

1.8.6 10RESERVED

1.8.7 10Spacecraft and Satellite-level Review Support

1.8.7.1 10Spacecraft Review Support

1.8.7.2 11Satellite-level Review Support

1.8.8 11Program-level Reviews

1.8.9 11Operations Reviews - Each Flight Model

1.8.10 12Test Readiness and Data Reviews

1.8.11 12Technical Meetings

1.8.12 12Subcontract and Subsystem Reviews

2 14Systems Engineering

2.1 14Systems Management and Engineering

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

Contents ii

2.2 15Spacecraft Interface and Accommodation

2.3 15System Analysis and Allocations

2.4 16Contamination Control and Analysis

3 17Software

3.1 17Management and Maintenance

3.2 18Software Reviews

4 19Parts and Spares Procurement

4.1 19Testing of Spare Hardware

4.2 19"One-shot" items

5 21Engineering Development Program

5.1 22Engineering Development Activities

5.2 22EDM Functional and Performance Testing (if applicable)

6 23Flight Model-1 (FM-1)

6.1 23Design and Analysis

6.1.1 23Instrument Design

6.1.2 24Flight and Ground Test Software Development

6.1.3 25Ground Processing Algorithms (GPA)

6.1.4 26Field Programmable Gate Array (FPGA) Design and Development

6.2 27Fabrication and Subassembly Testing

6.3 27Integration and Test (I&T)

6.3.1 28Integration

6.3.2 28Performance Verification and Design Qualification

6.3.3 28Functional and Performance Testing

6.3.3.1 28Comprehensive Performance Test (CPT)

6.3.3.2 29Limited Performance Test (LPT)

6.3.4 29Structural and Mechanical Testing

6.3.5 30Electromagnetic Compatibility Testing

6.3.6 30Thermal Testing

6.3.7 31Calibration

6.4 33Logistics

6.4.1 33Transportation and Handling

6.4.2 33Storage

6.5 34Post-shipment Support

6.5.1 34RESERVED

6.5.2 34Instrument and GSE Checkout

6.5.3 34Satellite-level Instrument Integration and Test Support

Contents iii

6.5.4 36Launch Operations Support

7 37Mission Operations Support

7.1 37Pre-Launch Support

7.2 38End-to-End Test Support

7.3 38Post-Launch Test (PLT) Support

7.4 38On-orbit Anomaly Support

8 40Ground Support Equipment (GSE)

8.1 40Electrical Ground Support Equipment (EGSE)

8.1.1 40Electrical System Test Equipment (ESTE)

8.1.2 40Connectors and Connector Savers

8.1.3 40Other Electrical Ground Support Equipment (EGSE)

8.2 41Mechanical and Optical Ground Support Equipment

8.3 41Flight Software Development Environment (FSDE)

8.4 41Ground Test Software Development System

8.5 41Ground Processing Demonstration System (GPDS)

8.6 42Instrument Hardware Simulator (IHS)

8.7 42Instrument Software Simulator (ISS)

9 44Mission Assurance

10 47Flight Model-2 (FM-2)

11 48Flight Model-3 (FM-3)

12 49Flight Model-4 (FM-4)

13 50Definitions

14 52Acronyms

Contents iv

Page 1 of 54 Printed Thursday, June 29, 2023

ID

LMXSOW1

LMXSOW2

LMXSOW3

LMXSOW4

LMXSOW5

LMXSOW20

LMXSOW24

LMXSOW25

LMXSOW26

Object Number

1.0-1

1.0-2

1.0-3

1.0-4

1.0-5

1.1

1.1.0-1

1.1.0-2

418-XO-LMXSOW-0116, RM Version, Geostationary eXtended Observations (GeoXO) Lightning Mapper (LMX) Statement of Work

(SOW) Phase B

1 Program Scope and Management

This Statement of Work (SOW) defines those tasks necessary to design, analyze, develop, fabricate, integrate, test, evaluate, and support launch of the Geostationary (GEO) - eXtended Observations (GeoXO) Lightning Mapper (LMX), hereupon called Instrument, supply and maintain the Instrument Ground Support Equipment (GSE), and support the Mission Operations at the National Oceanic and Atmospheric Administration (NOAA) Satellite Operations Facility (NSOF) in accordance with the Contractual documents listed in the Applicable Documents Section.

The Instrument has a risk classification of tailored Class C.

Satellite is a Spacecraft integrated with all the instrument payloads.

The Contractor shall provide the personnel, materials, facilities and other resources to design, develop, deliver (to the designated destination) and support under the basic contract:

a) Parts and materials for an Engineering Development Model (EDM) (if proposed) and four Flight Models for Instrument

b) One Instrument Proto-Flight Model (PFM) designated as Flight Model-1 (FM-1) and one FM-2

c) Spares parts/components to enable the timely repair of the flight models

d) Three sets of the Electrical System Test Equipment (ESTE)

e) Four Instrument Hardware Simulators (IHS)

f) One Instrument Software Simulator (ISS) executable

g) One Flight Software Development Environment (FSDE)

h) One Ground Processing Demonstration System (GPDS)

i) All additional Instrument Mechanical, Electrical, and Optical Ground Support Equipment (MGSE, EGSE, and OGSE) and needed spare parts

j) All items and documents specified in all contract documents

k) Test and Flight Thermal Blankets

l) Mating connectors and Connector Savers

The Contractor shall provide the personnel, materials, facilities and other resources to design, develop, deliver, and support:

a) Option 1 for an additional Flight Model (FM-3)

b) Option 2 for an additional Flight Model (FM-4)

1.1 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, and on-orbit anomaly investigations until all the FMs reach end-of-life.

The Contractor shall retain all documents and test data produced under this contract for the life of the contract.

Page 2 of 54 Printed Thursday, June 29, 2023

ID

LMXSOW811

LMXSOW27

LMXSOW28

LMXSOW29

LMXSOW36

LMXSOW37

LMXSOW807

LMXSOW808

LMXSOW809

Object Number

1.1.0-3

1.2

1.2.1

1.2.1.0-1

1.2.2

1.2.2.0-1

1.2.3

1.2.3.0-1

1.2.3.0-2

418-XO-LMXSOW-0116, RM Version, Geostationary eXtended Observations (GeoXO) Lightning Mapper (LMX) Statement of Work

(SOW) Phase B

The Government reserves the right to evaluate the markings on the data delivered under the contract at the time of delivery, in accordance with contract clause I.7.

1.2 Documents and Terminology

1.2.1 Applicable Documents

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

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

2. LMX Performance and Operational Requirements Document (PORD), 418-XO-

LMXPORD-0120.

3. LMX Unique Instrument Interface Document (UIID), 418-XO-LMXUIID-0067.

4. LMX Contract Data Requirements List (CDRL) 418-XO-LMXCDRL-0068.

5. GeoXO Instrument Mission Assurance Requirements (IMAR), 418-XO-

IMAR-0026.

6. NPR 7123.1C - NASA Systems Engineering Processes and Requirements Appendix E. - Technology Readiness Levels (with change 2).

1.2.2 Reference Documents

1. Guidelines for Evaluating and Expressing the Uncertainty of NIST Measurement Results, B. N. Taylor and C. E. Kuyatt, NIST Technical Note 1297, 1994 Edition.

Available at: http://physics.nist.gov/TN1297

2. General Requirements for the Competence of Testing and Calibration Laboratories, ISO/IEC 17025, 2017

3. Guide to the Expression of Uncertainty in Measurement (GUM), ISO/IEC Guide 98-3:2008

4. International Vocabulary of Basic and General Terms in Metrology (VIM), ISO/IEC Guide 99:2007

5. NPR 7150.2D: NASA Software Engineering Requirements

6. 500-PG-8700.2.7B: Design of Space Flight Field Programmable Gate Arrays.

7. 500-PG-8700.2.8B: FPGA Development Methodology

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

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

10. Flight Field Programmable Gate Array (FPGA) Review Methodology, 418-XO-

RPT-0045

11. NASA-STD-8739.8B, Software Assurance and Safety Standard

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

Page 3 of 54 Printed Thursday, June 29, 2023

ID

LMXSOW810

LMXSOW48

LMXSOW49

LMXSOW50

LMXSOW51

LMXSOW52

LMXSOW53

LMXSOW54

LMXSOW55

LMXSOW56

LMXSOW57

LMXSOW58

LMXSOW59

LMXSOW60

LMXSOW61

Object Number

1.2.3.0-3

1.3

1.3.0-1

1.3.0-2

1.3.0-3

1.3.0-4

1.3.0-5

1.3.0-6

1.3.0-7

1.3.0-8

1.4

1.4.0-1

1.4.0-2

1.4.0-3

1.4.0-4

418-XO-LMXSOW-0116, RM Version, Geostationary eXtended Observations (GeoXO) Lightning Mapper (LMX) Statement of Work

(SOW) Phase B

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

1.3 Project Management

The Contractor shall establish a Project Management Office (PMO) responsible for the leadership and overall direction of all phases of the work specified in this SOW.

The Contractor shall provide and implement a Project Management Plan, plus all updates and revisions, that describes the methodology and processes that will be employed to manage the Instrument Project from contract award through operational support of the last instrument 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 Instrument team, and one-on-one contact between National Aeronautics and Space Administration (NASA) and Contractor discipline engineers, to be coordinated by the Contracting Officer's Representative (COR).

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

The Contractor shall develop and maintain a Master Action Item Data base (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 Instrument Portal.

The Contractor shall retain all closed actions in the MAID.

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

1.4 Resource Management

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

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 the Integrated Program Management Data and Analysis Report (IPMDAR), plus all updates and revisions, in accordance with CDRL

# RM-03.

Page 4 of 54 Printed Thursday, June 29, 2023

ID

LMXSOW62

LMXSOW63

LMXSOW64

LMXSOW65

LMXSOW66

LMXSOW67

LMXSOW68

LMXSOW69

LMXSOW70

LMXSOW71

LMXSOW789

LMXSOW72

LMXSOW77

LMXSOW78

Object Number

1.4.0-5

1.4.0-6

1.4.0-7

1.4.0-8

1.4.0-9

1.4.0-10

1.5

1.5.0-1

1.5.0-2

1.5.0-3

1.5.0-4

1.5.0-5

1.5.0-6

1.6

418-XO-LMXSOW-0116, RM Version, Geostationary eXtended Observations (GeoXO) Lightning Mapper (LMX) Statement of Work

(SOW) Phase B

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.

Reserved

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

The Contractor shall provide private office space, furniture, copier(s), facsimile machine(s), phones, and high-speed internet access in the vicinity of the PMO for two Government resident representatives, including QA, and three visiting representatives.

The contractor shall provide additional office space for up to ten (10) people in the vicinity of the PMO for use by Government representatives during reviews or other functions that will increase the number of on-site Government representatives.

The Contractor shall provide office space, furniture, copier(s), printer, phones, and high-speed internet access for up to ten (10) visiting Government representatives during instrument integration and testing, in the vicinity of the activity.

1.5 Risk Management

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

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

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 Instrument technologies are at Technology Readiness Level (TRL) 6 by PDR as defined by NPR 7123.1C - 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 performance metrics, and

d) examine trends, deviations and anomalies.

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

1.6 Configuration and Information Management

Page 5 of 54 Printed Thursday, June 29, 2023

ID

LMXSOW79

LMXSOW80

LMXSOW81

LMXSOW82

LMXSOW83

LMXSOW86

LMXSOW84

LMXSOW85

LMXSOW87

LMXSOW88

LMXSOW89

LMXSOW90

LMXSOW91

LMXSOW92

Object Number

1.6.0-1

1.6.0-2

1.6.0-3

1.6.0-4

1.6.0-5

1.6.0-6

1.6.0-7

1.6.0-8

1.6.0-9

1.6.0-10

1.6.0-11

1.6.0-12

1.6.0-13

1.6.0-14

418-XO-LMXSOW-0116, RM Version, Geostationary eXtended Observations (GeoXO) Lightning Mapper (LMX) Statement of Work

(SOW) Phase B

The Contractor shall establish, implement, and maintain a Configuration Management System that provides Configuration Management control of configured items including all flight hardware, all 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 Contractor shall oversee and manage the generation, configuration control and distribution of all documents required by the contract.

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, accessible only by the respective Contractor and selected Government-personnel, for document delivery and the exchange of information only.

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

The Contractor shall perform portal management for the Instrument section of the GeoXO portal and organize the CDRL folders by year, FM, and by subsystem as appropriate.

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

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

The Contractor shall provide access to the Contractor's Instrument portal for released documents to COR and COR-recommended Government-personnel.

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.

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

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.

Page 6 of 54 Printed Thursday, June 29, 2023

ID

LMXSOW93

LMXSOW94

LMXSOW95

LMXSOW96

LMXSOW97

LMXSOW98

LMXSOW99

LMXSOW100

LMXSOW101

LMXSOW102

LMXSOW103

LMXSOW104

LMXSOW105

LMXSOW106

LMXSOW107

Object Number

1.6.0-15

1.6.0-16

1.6.0-17

1.6.0-18

1.7

1.7.0-1

1.7.0-2

1.8

1.8.0-1

1.8.0-2

1.8.0-3

1.8.1

1.8.1.0-1

1.8.1.0-2

1.8.1.0-3

418-XO-LMXSOW-0116, RM Version, Geostationary eXtended Observations (GeoXO) Lightning Mapper (LMX) Statement of Work

(SOW) Phase B

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.

The Contractor shall implement a Knowledge Management Program so that the knowledge base developed during design and development of the EDM and all FMs will be available to the Instrument Project personnel through the life of the mission.

1.7 Special Engineering Analysis / Task Orders

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

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

1.8 Project Review Requirements

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

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

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

1.8.1 Kick-off Meeting and Requirements Walkthrough

Approximately six weeks after award the Contractor shall prepare and conduct a Kick-off Meeting covering an overview of the Instrument development and subsequently a line-by-line review of the contract schedule and clauses, and the requirements documents SOW, Instrument Performance and Operational Requirements Document (PORD), General Interface Requirements Document (GIRD), Unique Instrument Interface Document (UIID), Instrument Mission Assurance Requirements Document (IMAR), and Contract Data Requirements List (CDRL).

The Contractor shall plan for a five-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 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 kickoff and Integrated Baseline Review (IBR))

Page 7 of 54 Printed Thursday, June 29, 2023

ID

LMXSOW107

LMXSOW117

LMXSOW118

LMXSOW119

LMXSOW790

LMXSOW120

LMXSOW121

LMXSOW122

LMXSOW123

LMXSOW124

LMXSOW127

LMXSOW128

LMXSOW129

Object Number

1.8.1.0-3

1.8.1.0-4

1.8.2

1.8.2.0-1

1.8.2.0-2

1.8.2.0-3

1.8.2.0-4

1.8.2.0-5

1.8.2.0-6

1.8.3

1.8.3.0-1

1.8.3.0-2

1.8.3.0-3

418-XO-LMXSOW-0116, RM Version, Geostationary eXtended Observations (GeoXO) Lightning Mapper (LMX) Statement of Work

(SOW) Phase B

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 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 and Mission Assurance (SMA) and quality processes

i) Overview of vendor facilities

If the line-by-line review of the Contractual documents is not complete in five days during the five-day 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.

1.8.2 Project Management Status Reviews

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

The Contractor shall prepare, present, and deliver Project Management Status Review - 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, respectively.

1.8.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-day review for the IBR.

Page 8 of 54 Printed Thursday, June 29, 2023

ID

LMXSOW130

LMXSOW131

LMXSOW132

LMXSOW133

LMXSOW134

LMXSOW135

LMXSOW136

LMXSOW137

LMXSOW138

LMXSOW139

LMXSOW140

LMXSOW141

LMXSOW142

LMXSOW143

LMXSOW144

LMXSOW145

Object Number

1.8.3.0-4

1.8.3.0-5

1.8.4

1.8.4.0-1

1.8.4.0-2

1.8.4.0-3

1.8.4.0-4

1.8.4.0-5

1.8.4.0-6

1.8.5

1.8.5.0-1

1.8.5.0-2

1.8.5.0-3

1.8.5.0-4

1.8.5.0-5

1.8.5.0-6

418-XO-LMXSOW-0116, RM Version, Geostationary eXtended Observations (GeoXO) Lightning Mapper (LMX) Statement of Work

(SOW) Phase B

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.

1.8.4 Peer Reviews

The Contractor shall implement and conduct a program of tabletop engineering and subsystem 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. For subsystem engineering peer reviews, a Government representative is co-chair.

The Contractor shall prepare and deliver an engineering peer review plan in accordance with the Systems Engineering Management Plan, CDRL # SE 2-1.

Unless stipulated otherwise by the Government, the Contractor shall include Government technical experts in the Peer Reviews.

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 provide ten (10) days prior notification for Peer Reviews so that Government representatives can be present.

The Contractor shall post the Peer Review data packages in the Peer Review / Subsystem / Subcontract Review Data Packages folder, CDRL # SR-07.

1.8.5 Instrument Milestone Reviews

The Contractor shall prepare and conduct Government-chaired Instrument Milestone Reviews (SRR, PDR, CDR, etc.) listed in Sections 1.8.5.1 - 1.8.5.6 below 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 Instrument team in attendance, approximately 2 weeks prior to the review.

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

Each milestone review 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 Government.

The Contractor shall deliver an outline for the milestone Review Package twenty-one

(21) days before each of the contractually-required Instrument Milestone Reviews.

The Contractor shall deliver the Milestone Review Package seven (7) days before each of the contractually-required Instrument Milestone Reviews listed in Sections 1.8.5.1 -

1.8.5.6 below.

Page 9 of 54 Printed Thursday, June 29, 2023

ID

LMXSOW146

LMXSOW147

LMXSOW148

LMXSOW791

LMXSOW792

LMXSOW793

LMXSOW812

LMXSOW149

LMXSOW150

LMXSOW151

LMXSOW152

LMXSOW153

LMXSOW794

LMXSOW154

LMXSOW155

LMXSOW156

LMXSOW157

LMXSOW158

LMXSOW159

Object Number

1.8.5.1

1.8.5.1.0-1

1.8.5.1.0-2

1.8.5.1.0-3

1.8.5.1.0-4

1.8.5.1.0-5

1.8.5.1.0-6

1.8.5.1.0-7

1.8.5.2

1.8.5.2.0-1

1.8.5.2.0-2

1.8.5.2.0-3

1.8.5.2.0-4

1.8.5.2.0-5

1.8.5.3

1.8.5.3.0-1

1.8.5.3.0-2

1.8.5.3.0-3

1.8.5.4

418-XO-LMXSOW-0116, RM Version, Geostationary eXtended Observations (GeoXO) Lightning Mapper (LMX) Statement of Work

(SOW) Phase B

1.8.5.1 System Requirements/Definition Review (SRR/SDR)

Approximately 3 months after kickoff the Contractor shall prepare and conduct an SRR/SDR covering the Instrument system specification including: instrument requirements, interfaces, GSE, flight software and ground test software requirements, and ground processing algorithms requirements.

The Contractor shall plan for a three-day SRR/SDR, not including resolution of RFAs.

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

SRR/SDR.

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

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 if TRL 6 advancement activities are projected to occur beyond PDR.

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

SR-01.

1.8.5.2 Preliminary Design Review (PDR)

The Contractor shall prepare and conduct a PDR.

The Contractor shall status the design and testing of the breadboard or brassboard models of critical subassemblies/assemblies at the PDR.

The Contractor shall plan for a three-day PDR, not including resolution of RFAs.

The Contractor shall demonstrate that all technologies in the Instrument 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.

1.8.5.3 Critical Design Review (CDR)

The Contractor shall prepare and conduct a CDR prior to the start of manufacture of the PFM hardware unless the Contractor requests and the Government concurs with an earlier start.

The Contractor shall plan for a four-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.

1.8.5.4 Pre-Environmental Review (PER) - Each Flight Model

Page 10 of 54 Printed Thursday, June 29, 2023

ID

LMXSOW160

LMXSOW161

LMXSOW162

LMXSOW163

LMXSOW164

LMXSOW165

LMXSOW166

LMXSOW167

LMXSOW168

LMXSOW169

LMXSOW170

LMXSOW171

LMXSOW172

LMXSOW173

LMXSOW174

LMXSOW179

LMXSOW180

LMXSOW181

Object Number

1.8.5.4.0-1

1.8.5.4.0-2

1.8.5.4.0-3

1.8.5.5

1.8.5.5.0-1

1.8.5.5.0-2

1.8.5.5.0-3

1.8.5.5.0-4

1.8.5.5.0-5

1.8.5.5.0-6

1.8.5.6

1.8.5.6.0-1

1.8.5.6.0-2

1.8.5.6.0-3

1.8.6

1.8.7

1.8.7.1

1.8.7.1.0-1

418-XO-LMXSOW-0116, RM Version, Geostationary eXtended Observations (GeoXO) Lightning Mapper (LMX) Statement of Work

(SOW) Phase B

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

The Contractor shall plan for a three-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.

1.8.5.5 Pre-Storage/Pre-Shipment Review (PSR) - Each Flight Model

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

The Contractor shall plan for a three-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.

For the instrument stored-in-place, the Contractor shall prepare and conduct a Pre-Ship Review prior to the shipment of each FM.

The Contractor shall plan for a three-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.

1.8.5.6 Design Modification Reviews

After the CDR, the Government reserves the right to request the Contractor to hold a Design Modification Review (DMR) for Class I CCRs. 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-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.

1.8.6 RESERVED

1.8.7 Spacecraft and Satellite-level Review Support

1.8.7.1 Spacecraft Review Support

The Contractor shall provide technical support to all Spacecraft Reviews conducted at the Spacecraft Contractor's facility.

Page 11 of 54 Printed Thursday, June 29, 2023

ID

LMXSOW182

LMXSOW186

LMXSOW187

LMXSOW188

LMXSOW189

LMXSOW194

LMXSOW195

LMXSOW196

LMXSOW197

LMXSOW201

LMXSOW202

LMXSOW203

LMXSOW204

Object Number

1.8.7.1.0-2

1.8.7.2

1.8.7.2.0-1

1.8.7.2.0-2

1.8.7.2.0-3

1.8.7.2.0-4

1.8.8

1.8.8.0-1

1.8.8.0-2

1.8.8.0-3

1.8.9

1.8.9.0-1

1.8.9.0-2

418-XO-LMXSOW-0116, RM Version, Geostationary eXtended Observations (GeoXO) Lightning Mapper (LMX) Statement of Work

(SOW) Phase B

The Contractor shall attend all Spacecraft Reviews including but not necessarily limited to:

a) Spacecraft System Definition Review (3 days)

b) Spacecraft Preliminary Design Review (3 days)

c) Spacecraft Critical Design Review (3 days)

1.8.7.2 Satellite-level Review Support

The Contractor shall provide technical support to all Satellite-level reviews, including Satellite integration and test reviews, conducted at the Spacecraft Contractor's facility.

The Contractor shall support the Satellite-level reviews by presentations and/or documentation; for example, by providing and/or presenting instrument overview or design summary, test and data evaluation summaries, etc.

The Contractor shall attend all Satellite-level Reviews including but not necessarily limited to:

a) Instrument Receiving Review (IRR) (1 day for each FM)

b) Satellite Pre-environmental Review (3 days for FM-1; 2 days for each FM follow on)

c) Satellite Pre-storage Review (3 days for FM-1; 2 days for each FM follow on)

d) Satellite Pre-ship Review (3 days for FM-1; 2 days for each FM follow on)

The Contractor shall provide technical input to the Spacecraft Contractor for creating the Satellite Data Books.

1.8.8 Program-level Reviews

The Contractor shall support the Program-level Reviews by presentations and/or documentation; for example, an instrument overview or design summary, test and data evaluation summaries, etc.

The Contractor shall support the following Program-level Reviews:

a) Mission Preliminary Design Review (MPDR) (3 days)

b) Mission Critical Design Review (MCDR) (3 days)

c) System Integration Review (SIR) (3 days for each FM)

Reviews a) and b) listed in LMXSOW197 occur at NASA Goddard Space Flight Center (GSFC), review c) occurs at the Spacecraft Contractor facility.

1.8.9 Operations Reviews - Each Flight Model

The Contractor shall support the Operations Reviews for each FM by presentations and documentation; for example, by providing and/or presenting instrument overview and design summary, test and data evaluation summaries, etc.

The Contractor shall support the following Operations Reviews for each FM at NSOF:

a) Mission Operations Review (MOR) (3 days)

Page 12 of 54 Printed Thursday, June 29, 2023

ID

LMXSOW204

LMXSOW209

LMXSOW210

LMXSOW216

LMXSOW217

LMXSOW218

LMXSOW219

LMXSOW220

LMXSOW221

LMXSOW222

LMXSOW223

LMXSOW224

LMXSOW225

LMXSOW226

LMXSOW227

Object Number

1.8.9.0-2

1.8.10

1.8.10.0-1

1.8.11

1.8.11.0-1

1.8.11.0-2

1.8.11.0-3

1.8.11.0-4

1.8.12

1.8.12.0-1

1.8.12.0-2

1.8.12.0-3

1.8.12.0-4

1.8.12.0-5

1.8.12.0-6

418-XO-LMXSOW-0116, RM Version, Geostationary eXtended Observations (GeoXO) Lightning Mapper (LMX) Statement of Work

(SOW) Phase B

b) Flight Operations Review (FOR) (3 days)

c) Operational Readiness Review (ORR) (3 days)

d) Post Launch Assessment Review (PLAR) (2 days)

1.8.10 Test Readiness and Data Reviews

The Contractor shall prepare and conduct Test Readiness Reviews (TRRs) and Test Data Reviews (TDRs) for flight hardware and software with Government personnel in participation.

1.8.11 Technical Meetings

The Contractor shall hold Technical Meetings and reviews as deemed necessary by the Government for the purpose of discussing and/or resolving problems or items of interest.

Unless stipulated otherwise by the Government, the Contractor shall include Government personnel in Technical Meetings, and test readiness and acceptance reviews for subcontracted assemblies.

The Contractor shall conduct Technical Meetings with Subcontractors for the selection of Instrument critical assemblies, and subassemblies, and provide the Government seven (7) days advanced notice so that Government representatives can attend. Critical subassemblies are: e.g., focal plane array, detector, optical elements, radiator, mechanisms, etc.

The Contractor shall participate in 24 monthly technical interchange teleconferences and 4 (2/year) technical interchange meetings at Government-defined locations.

1.8.12 Subcontract and Subsystem Reviews

The Contractor shall plan and conduct Subcontract and Subsystem Reviews per the Project Management Plan, CDRL # PM-01.

Unless stipulated otherwise by the Government, the Contractor shall include Government personnel in Subcontract and Subsystem Reviews.

The Contractor shall conduct PDRs and CDRs for the major subsystems identified in CDRL # PM-01, whether the subsystems are provided by the Contractor or by a Subcontractor.

Whether internal or external, Subcontract and Subsystem reviews shall be conducted by the Contractor and chaired and staffed by independent reviewers for the hardware under review. The Government reserves the right to attend these reviews and requires ten (10) business days notification.

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

The Contractor shall document minutes from Subsystem / Subcontract Reviews for each review and deliver the minutes as an addendum to the Subsystem / Subcontract Review Data Package.

Page 13 of 54 Printed Thursday, June 29, 2023

ID

LMXSOW228

Object Number

1.8.12.0-7

418-XO-LMXSOW-0116, RM Version, Geostationary eXtended Observations (GeoXO) Lightning Mapper (LMX) Statement of Work

(SOW) Phase B

The Contractor shall document all action items from Subsystem / Subcontract Reviews in the MAID.

Page 14 of 54 Printed Thursday, June 29, 2023

ID

LMXSOW229

LMXSOW230

LMXSOW231

LMXSOW232

LMXSOW234

LMXSOW235

LMXSOW236

LMXSOW237

LMXSOW238

LMXSOW239

LMXSOW240

LMXSOW241

LMXSOW242

LMXSOW243

LMXSOW244

LMXSOW245

Object Number

2.0-1

2.0-2

2.0-3

2.0-4

2.0-5

2.0-6

2.0-7

2.0-8

2.0-9

2.0-10

2.0-11

2.1

2.1.0-1

2.1.0-2

2.1.0-3

418-XO-LMXSOW-0116, RM Version, Geostationary eXtended Observations (GeoXO) Lightning Mapper (LMX) Statement of Work

(SOW) Phase B

2 Systems Engineering

The Contractor shall establish and maintain a Systems Engineering Program for directing, specifying, and overseeing the design and technical development of the Instrument, GSE, and ground algorithms.

The Contractor shall prepare, deliver, and implement a Systems Engineering Management Plan, plus updates and revisions, in accordance with CDRL # SE 2-1.

The Contractor shall utilize Rational Dynamic Object Oriented Requirements System (DOORS®) as the Requirements Management tool to capture, link, trace, analyze, and manage changes to all requirements documentation.

The Contractor shall perform all systems analyses, provide systems engineering support to derive lower-level performance requirements, and develop the instrument system specification and design specifications for the instrument subsystems.

The Contractor shall document the allocation of requirements to the lower level specifications, showing the traceability of all requirements including performance and design drivers, and explicitly identifying any derived requirements.

The Contractor shall link the lower level DOORS requirements to the GIRD, and Instrument PORD and UIID requirements.

Starting with SRR, the Contractor shall provide monthly drops of DOORS dpa module for Level 4 through Level 6 requirements. The cadence may be reduced after PFM delivery, upon approval from the Government.

The Contractor shall provide verification reports for all the requirements in the GIRD, and Instrument PORD and UIID.

The Contractor shall map all requirements to specific verification test plans and procedures utilizing the DOORS database.

The Contractor shall map all requirement verifications to specific verification test reports, as-run procedures, and analysis reports utilizing the DOORS database for each

FM.

The Contractor shall verify that the lower level requirements are met.

2.1 Systems Management and Engineering

The Contractor shall perform all system studies, trades, and risk assessments necessary to develop an instrument system design that meets the Instrument performance, operational, and interface requirements.

The Contractor shall flow down the Instrument performance, operational, and interface requirements into engineering functional requirements, detailed equipment requirements, and end item design requirements.

The Contractor shall ensure that all subsystems, both individually and in combination, meet the intended design and performance specifications and that the design specifications are sufficient to meet the mission life requirements.

Page 15 of 54 Printed Thursday, June 29, 2023

ID

LMXSOW246

LMXSOW247

LMXSOW248

LMXSOW249

LMXSOW250

LMXSOW251

LMXSOW252

LMXSOW254

LMXSOW255

LMXSOW256

LMXSOW257

LMXSOW258

LMXSOW259

LMXSOW260

LMXSOW261

Object Number

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

2.2.0-1

2.2.0-2

2.2.0-3

2.2.0-4

2.2.0-5

2.2.0-6

2.3

418-XO-LMXSOW-0116, RM Version, Geostationary eXtended Observations (GeoXO) Lightning Mapper (LMX) Statement of Work

(SOW) Phase B

The Contractor shall prepare, deliver, and maintain the Instrument System Specification in accordance with CDRL # SE 1-1.

The Contractor shall prepare, deliver, and maintain a Drawing Tree(s) that includes all instrument and GSE drawings to the lowest level, plus updates and revisions in accordance with CDRL # SE 1-6.

The Contractor shall prepare, deliver, and maintain a Document Tree(s) that includes all instrument and GSE design documentation, plus updates and revisions in accordance with CDRL # PM-09.

The Contractor shall establish and maintain a System Performance and Environmental Verification Program to demonstrate that the FMs meet all mandated and derived performance requirements and that the GSE meets all design and interface requirements.

The Contractor shall prepare, deliver, and implement a System Performance Verification Plan and Compliance, plus updates and revisions, including a Systems Performance Verification Matrix that documents the System Performance Verification Program at assembly, subsystem, and instrument level of assembly, in accordance with

CDRL # SE 2-2.

The System Performance Verification Matrix shall be delivered in a DOORS compatible format.

The Contractor shall provide System Performance Verification Reports, plus updates and revisions, in accordance with CDRL #SE 4-10.

2.2 Spacecraft Interface and Accommodation

The Contractor shall coordinate with the Spacecraft Contractor and support technical interchange meetings to refine the instrument accommodations and interfaces between the Instrument and the Spacecraft as well as Instrument GSE to Spacecraft GSE interfaces for data analysis.

Starting with Spacecraft SRR, the Contractor shall participate in monthly interface meetings with the Spacecraft Contractor, including for the ICD development. The Instrument ICD is expected to be first released at the Spacecraft PDR and updated at subsequent Spacecraft milestone reviews.

The Contractor shall document all interfaces in an Instrument Description Document (IDD), plus updates and revisions, in accordance with CDRL # SE 1-5.

The Contractor shall provide inputs and support the development of the Instrument-to- Spacecraft Interface Control Document (ICD).

The Contractor shall support the Spacecraft Contractor in the design and test of all Instrument-to-Spacecraft interfaces: mechanical, including the location of the Instrument on the spacecraft, electrical, and thermal.

The Contractor shall support the Spacecraft Contractor to ensure that the stowed, deploying, and final deployed positions of instrument assemblies clear all other instruments and obstacles, including obstacles posed by the Satellite components.

2.3 System Analysis and Allocations

Page 16 of 54 Printed Thursday, June 29, 2023

ID

LMXSOW262

LMXSOW263

LMXSOW264

LMXSOW265

LMXSOW266

LMXSOW267

LMXSOW268

LMXSOW269

LMXSOW270

LMXSOW271

Object Number

2.3.0-1

2.3.0-2

2.3.0-3

2.3.0-4

2.4

2.4.0-1

2.4.0-2

2.4.0-3

2.4.0-4

2.4.0-5

418-XO-LMXSOW-0116, RM Version, Geostationary eXtended Observations (GeoXO) Lightning Mapper (LMX) Statement of Work

(SOW) Phase B

The Contractor shall conduct complete analyses of the technical requirements that fully establish and define budget allocations for all required performance and design parameters, including but not limited to, mass, power, and volume allocations, alignment, Image Navigation and Registration (INR), contamination control, thermal, on-board processing resources, and data timeliness.

The Contractor shall maintain and control budgets (i.e. allocations and margins) for all instrument resources.

The Contractor shall deliver Mass Properties and Power Report, plus updates and revisions, in accordance with CDRL # SE 4-1.

The Contractor shall develop alignment budgets necessary to meet the performance requirements of the Instrument.

2.4 Contamination Control and Analysis

The Contractor shall establish a Contamination Control Program and provide the resources necessary to assure that appropriate contamination control is maintained through all phases of instrument manufacture, build-up/assembly, integration and test, and Satellite integration and test, launch site processing, and on-orbit operation.

The Contractor shall prepare, deliver, and implement a Contamination Control Plan, plus updates and revisions, to define the contamination control requirements as well as those procedures and processes that are in place to ensure compliance, in accordance with CDRL # SE 2-3.

The Contractor shall implement a Foreign Object Debris (FOD) control program.

The Contractor shall conduct a mass transport analysis and a particle generation analysis for the instrument.

The Contractor shall prepare and deliver mass transport analysis results, plus updates and revisions, in accordance with CDRL # SE 4-6.

Page 17 of 54 Printed Thursday, June 29, 2023

ID

LMXSOW272

LMXSOW273

LMXSOW274

LMXSOW275

LMXSOW276

LMXSOW277

LMXSOW278

LMXSOW279

LMXSOW280

LMXSOW795

LMXSOW796

LMXSOW281

LMXSOW282

LMXSOW283

LMXSOW797

Object Number

3.1

3.1.0-1

3.1.0-2

3.1.0-3

3.1.0-4

3.1.0-5

3.1.0-6

3.1.0-7

3.1.0-8

3.1.0-9

3.1.0-10

3.1.0-11

3.1.0-12

3.1.0-13

418-XO-LMXSOW-0116, RM Version, Geostationary eXtended Observations (GeoXO) Lightning Mapper (LMX) Statement of Work

(SOW) Phase B

3 Software

3.1 Management and Maintenance

The Contractor shall establish and maintain a Software Management Program to plan and document flight and ground software development processes and procedures, software tools, ground test software, reviews, resources, schedules and deliverables required for support of the FM integration, test and verification program, and on-orbit operations.

The Contractor shall develop, implement, and maintain a Software Configuration Management System that provides baseline management and control of software requirements, design, source code, data and documentation.

The Contractor shall employ a source code version control tool to check in/check out current or previous versions of a source file.

The Contractor shall prepare and deliver the Software Management Plan, plus updates and revisions, in accordance with CDRL # SW-01.

The contractor shall document the Instrument Software Verification and Validation (V&V) program in the Software Management Plan, in accordance with CDRL # SW-01.

The Contractor shall update and maintain all flight software, ground test software, processes, procedures, and software tools required for support of the FM integration, test and verification program, and on-orbit operations in the Software Maintenance Plan, plus updates and revisions, in accordance with CDRL # SW-02.

The Contractor shall classify all Instrument startup (SUROM or equivalent) and health and safety flight software as Class B software, as defined NPR 7150.2D.

The Contractor shall classify all other Instrument flight software as Class C as defined in NPR 7150.2D. All other software developed under the contract may be Class C or lower.

The Contractor shall document the classification listed in the Software Management Plan, CDRL SW-01.

For all Class B software as defined in NPR 7150.2D, the personnel responsible for the development of software test documents (e.g. Software Test Plans, Software Test Procedures, Software Test Descriptions) shall be different from those personnel responsible for the design and development of that CSCI.

The Contractor shall submit for Government approval, a preliminary classification for each Computer Software Configuration Item (CSCI) in accordance with the software classification definitions in Appendix D of NPR 7150.2D.

If the Instrument is selected for the NASA Independent Verification and Validation (IV&V) effort, the Contractor shall ensure that the IV&V team is provided access to development artifacts, products, source code, and data required to perform the IV&V analysis.

The Contractor shall provide responses to issues and risks submitted by the IV&V team, and track these issues and risks to closure.

Page 18 of 54 Printed Thursday, June 29, 2023

ID

LMXSOW284

LMXSOW285

LMXSOW286

LMXSOW287

LMXSOW288

LMXSOW289

LMXSOW290

LMXSOW291

LMXSOW292

LMXSOW298

LMXSOW299

LMXSOW300

LMXSOW301

Object Number

3.1.0-14

3.1.0-15

3.1.0-16

3.2

3.2.0-…