Attachment A - SOW.pdf

Effective Date: TBD

Expiration Date: TBD

Check the SOLAR CM tool Server https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

SOLAR-XRIS-SOW-0007, Rev

Space Weather Observations at L1 (SOLAR) Series, Code 493

Space Weather Observations at L1 to

Advance Readiness (SOLAR)

X-Ray Irradiance Sensor (XRIS)

Statement of Work (SOW)

U.S. Department of Commerce (DOC)

National Oceanic and Atmospheric Administration (NOAA)

NOAA Satellite and Information Service (NESDIS)

National Aeronautics and Space Administration (NASA)

GSFC SOLAR Project CMO

January 13, 2026

Draft

DRAFT

https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm http://www.noaa.gov/ https://www.commerce.gov/

SOLAR X-Ray Irradiance Sensor SOW SOLAR-XRIS-SOW-0007, Rev - Chg 01

Effective Date: TBD ii

Check the SOLAR CM tool Server https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

SOLAR X-Ray Irradiance Sensor (XRIS) Statement of Work

(SOW)

Signature/Approval Page

Prepared by:

Original signed by:

E. Matt Glanfield

SOLAR XRIS Instrument Engineer

SW Next SOLAR

NASA Goddard Space Flight Center

Reviewed by:

C. Hudson DeLee

SOLAR Instrument Systems Manager

SW Next SOLAR

Approved by:

Brennan Nowak

Deputy Project Manager, SW Next SOLAR

James Morrissey

Project Manager, SW Next SOLAR iii

Check the SOLAR CM tool Server https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

CM FOREWORD

This document is under control by the SW Next SOLAR project configuration control board.

Changes to this document require prior approval by the configuration control board chairperson or designee. Proposed changes shall be submitted via a configuration change request along with supportive material justifying the proposed change. Changes to this document will be made by complete revision

In this plan, all mandatory actions (i.e., requirements) are denoted by statements containing the term “shall.” The terms “may” or “can” denote discretionary privilege or permission; “should” denotes a good practice and is recommended but not required; “will” denotes expected outcome;

and “are/is” denotes descriptive material.

Any questions should be addressed to:

SOLAR Configuration Management Office

Mail Stop: 493

Goddard Space Flight Center

Greenbelt, Maryland 20771 iv

Check the SOLAR CM tool Server https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

Change History Log

Revision Effective Date Description of Changes

(Reference the CCR & CCB/ERB Approval Date) v

Check the SOLAR CM tool Server https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

Table of Contents

1 INTRODUCTION

1.1 Program Scope and Management

2 DOCUMENTS

2.1 Applicable Documents

2.2 Reference Documents

3 REQUIREMENT DEFINITIONS

3.1 Requirements Precedence

3.2 Terms and Definitions

4 WORK PERFORMED BY THE CONTRACTOR (CLIN 001)

4.1 Program Management Office

4.2 Resource Management

4.3 Visitor Badging

4.4 Configuration and Information Management

4.4.1 Documentation

4.5 Program Review Requirements

4.5.1 Kick-off Meeting

4.5.2 Working Groups and TIMs

4.5.2.1 Working Group Meetings

4.5.2.2 Technical Interchange Meetings (TIMs)

4.5.3 Peer Reviews

4.5.4 Instrument Design Reviews

4.5.4.1 System Definition Review (SDR)/Systems Requirements Review (SRR)

4.5.4.2 Preliminary Design Review (PDR)

4.5.4.3 Critical Design Review (CDR)

4.5.4.4 Pre-Environmental Review (PER)

4.5.4.5 Pre-Storage/Pre-Shipment Review (PSR)

4.5.5 Observatory Level Reviews

4.5.6 Project Management Reviews

4.5.7 Test Data Reviews

4.5.8 Technical Meetings

4.5.9 Subcontract Subsystem and Instrument Reviews

4.6 Schedule Management

4.7 Risk Management

vi

Check the SOLAR CM tool Server https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

5 SYSTEMS ENGINEERING (CLIN 001)

5.1 Systems Management and Engineering

5.2 Observatory Interface and Accommodation

5.3 System Analysis and Allocations

5.4 Contamination Control and Analysis

5.5 Magnetic Control Plan

5.6 Special Engineering Analysis

6 FLIGHT MODEL (FM) (CLIN 001)

6.1 Design and Analysis

6.1.1 Instrument Design

6.1.2 Flight and Ground Test Software Development and Maintenance

6.1.3 Ground Processing Algorithms (GPA)

6.2 Parts Procurement, Fabrication and Subassembly Testing

6.2.1 Field Programmable Gate Array (FPGA) Design and Development

6.3 Integration and Test

6.3.1 Integration

6.3.2 Performance Verification and Design Qualification

6.3.2.1 Functional and Performance Testing

6.3.2.2 Structural and Mechanical Testing

6.3.2.3 Electromagnetic Compatibility Testing

6.3.2.4 Magnetic Properties Testing

6.3.2.5 Thermal Testing

6.3.3 Calibration

6.4 Logistics

6.4.1 Transportation and Handling

6.4.2 Storage

6.4.3 Flight Spare Delivery

7 GROUND SUPPORT EQUIPMENT (GSE) (CLIN 001)

7.1 Electrical Ground Support Equipment

7.1.1 Electrical System Test Equipment (ESTE)

7.1.2 X-Ray Irradiance Sensor Emulator

7.1.3 Connectors

7.1.4 Other Electrical Ground Support Equipment (EGSE)

7.2 Mechanical Ground Support Equipment (MGSE)

7.3 Ground Processing Development System (GPDS)

vii

Check the SOLAR CM tool Server https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

8 MISSION ASSURANCE (CLIN 001)

9 POST DELIVERY SUPPORT (CLIN 002)

9.1 Post Delivery Support

9.1.1 Observatory Integration and Test Support

9.1.2 Launch Operations Support

9.1.3 Mission Operations Support

9.1.3.1 Delivery of FM and Operations Tools

9.1.4 End-to-End Test Support

9.1.5 Post-Launch Test (PLT) Support

10 PRE-PRICED OPTIONS (CLIN 002)

10.1.1 PPC 1: Observatory Delivery Delay

10.1.2 PPC 2: Observatory Environmental Testing support delay

10.1.3 PPC 3: Launch Delay, Observatory Storage, and Post-Storage Testing

10.1.4 PPC 4: Extended Launch Delay, Observatory Storage, and Post-Storage Testing ... 40

11 SPECIAL STUDIES (CLIN 003)

APPENDIX A ABBREVIATIONS AND ACRONYMS

Check the SOLAR CM tool Server https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

1 INTRODUCTION

1.1 Program Scope and Management

The Space weather Observation at L1 to Advance Readiness (SOLAR) Series Mission is a high priority joint undertaking by the National Aeronautics and Space Administration (NASA) and the Department of the Commerce’s (DOC) National Oceanic and Atmospheric Administration

(NOAA). The SOLAR Mission will procure a minimum of two (2) observatories (A and B) that will provide NOAA with the continuity and resilience of solar wind data and coronal mass ejection (CME) imagery, which is the National Weather Service’s (NWS) highest priority for space weather observations. The X-Ray Irradiance Sensor (XRIS) will monitor X-ray flares that may cause changes in the Earth’s ionosphere and will be flown on SOLAR-B. The SOLAR-B

Observatory is targeted to launch as an individual primary payload in October 2032.

This Statement of Work (SOW) defines those tasks necessary to design, analyze, develop, and fabricate two (2) flight X-Ray Irradiance Sensors.

The SOW also defines the tasks necessary to integrate, test, calibrate, evaluate, and support launch and on-orbit check-out of the X-Ray Irradiance Sensors, supply and maintain the instrument Ground Support Equipment (GSE), Ground Processing Algorithms, and support the

Mission Operations Center (MOC) at the NOAA Satellite Operations Facility (NSOF) through mission hand over to NOAA.

The period of performance for the contract is from contract award through fifteen (15) months

(TBR) after launch of the SOLAR-B Mission. This includes post-delivery support for

Observatory level integration, launch, post launch evaluation, calibration, data validation, operational handover to NOAA of the instruments, and on-orbit anomaly investigations. The first flight unit shall be delivered by November 2029, and the second by May 2030.

The X-Ray Irradiance Sensor is part of the SOLAR project which has a risk classification of C per NASA Procedural Requirements (NPR) 8705.4, Risk Classification for NASA Payloads.

The Contractor shall provide the personnel, materials, facilities, and other resources to design, develop, deliver, provide storage, provide support to spacecraft integration and test, launch, and early mission operations including ground processing algorithm development, under the contract for:

a. One X-Ray Irradiance Sensor Flight Model (FM) Instrument, consisting of a sensor, associated electronics and harnesses, designated Flight Model-1 (FM-1).

b. One spare X-Ray Irradiance Sensor Flight Model (FM) Instrument, consisting of a sensor, associated electronics and harnesses, designated Flight Model-2 (FM-2). FM-2 does not require spacecraft integration and test, launch, or early mission operations, unless it is decided that it should replace FM-1.

c. One Engineering Development Unit (EDU) Instrument, consisting of a sensor, associated electronics and harnesses.

d. Spares.

e. Two sets of the Electrical System Test Equipment (ESTE).

Check the SOLAR CM tool Server https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

f. Four X-Ray Irradiance Sensor Emulators.

g. One Ground Processing Development Systems (GPDS).

h. All additional XRIS Instrument Mechanical and Electrical Ground Support Equipment

(MGSE and EGSE) called out elsewhere in this document.

i. All remaining items and documents specified in contract documents

The work is divided into three CLINs.

CLIN 001 Flight Instrument (SOW section 4-8)

CLIN 002 Post Delivery Support and Pre-Priced Options (SOW Section 9-10)

CLIN 003 Special Studies (SOW Section 11)

Check the SOLAR CM tool Server https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

2 DOCUMENTS

2.1 Applicable Documents

The documents listed in this section apply directly to the performance of the X-Ray Irradiance

Sensor contract. These documents establish detailed specifications, requirements, and interface information necessary for the performance of the contract:

• X-Ray Irradiance Sensor Requirements Specification, SOLAR-XRIS-REQ-0029

• X-Ray Irradiance Sensor Mission Assurance Requirements Document (MAR), SOLAR-

XRIS-REQ-0032

• X-Ray Irradiance Sensor Contract Deliverables Requirements List (CDRL), SOLAR-

XRIS-REQ-0031

• NASA-STD-8739.8B NASA Software Assurance and Software Safety Requirements

• NPR 7150.2D NASA Software Engineering Requirements

• NPR 8705.4, Risk Classification for NASA Payloads

• NPR 7123.1D, NASA Systems Engineering Processes and Requirements Updated w/

Change 2

2.2 Reference Documents

GOLD Rules, Goddard Space Flight Center Rules for the Design, Development, and Operation of Flight Systems Rules, GSFC-STD-1000 (Rev I).

• GSFC-STD-1001A, Criteria for Flight and Flight Support Systems Lifecycle Reviews

Check the SOLAR CM tool Server https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

3 REQUIREMENT DEFINITIONS

3.1 Requirements Precedence

In the event of a conflict in requirements between this SOW and other documentation, the order of precedence shall be: SOW, CDRL, X-Ray Irradiance Sensor Requirements Specification, MAR, and any other Applicable Documents.

The Contractor shall notify the Contracting Officer of any inconsistencies in this SOW, including all attachments and applicable documents. Upon notification of an inconsistency, the

Contracting Officer will clarify which requirement takes precedence, and may modify the contract as deemed appropriate.

3.2 Terms and Definitions

For the purposes of the SOLAR X-Ray Irradiance Sensor contract attachments, the following terms and definitions apply.

A requirement is identified by “shall,” a good practice by “should,” permission by “may” or

“can,” expected outcome or action by “will” and descriptive material by “is” or “are” (or other verb form of “to be”).

The term “TBS” (To Be Supplied) means that the Government will clarify or supply the missing information during the course of the contract. “TBR” (To Be Reviewed) means that the stated information will be reviewed for appropriateness by the Contractor and the Government and the value may be changed prior to final definition by the Government during the course of the contract. Until the value is changed or the “TBR” removed, the Contractor shall comply with the requirement as if the “TBR” notation did not exist. “TBD” (To Be Determined) indicates further research or analysis is needed to determine the information, during the course of the contract, with the final determination to be made by the Government. “TBP” (To Be Proposed) means the

Contractor proposes the information with the Offer submission for Government review and approval. All changes to resolve these “TBX” items will be done through a formal process of configuration change review, approval, and contract modification.

The terms “observatory” and “Observatory” refer to the spacecraft (or Spacecraft) bus fully or partially integrated with one or more flight instruments and is equivalent to the term

“observatory” used in the Rapid IV Contract.

The term “Government” represents the appropriate NASA and/or NOAA SOLAR management office or, where “the Government” is indicated as providing a function for or interface to the spacecraft contractor, the function or interface may be provided by

Government or Government SOLAR or support service contractors.

The terms “SOLAR Project Office,” “SOLAR Project,” and “Project” refers to the

Government SOLAR Project Office.

The terms “instrument team,” “instrument provider,” “instrument developer,” “instrument supplier,” and “instrument contractor” refer to the various instrument contractors and/or to

Government civil servant and Government support contractors interfacing with and or

Check the SOLAR CM tool Server https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

providing the instrument or data for the various instruments (to be revised based on instrument contractor selection).

The terms “X-Ray Irradiance Sensor,” “instrument,” “instruments,” refer to all flight model units of the X-Ray Irradiance Sensor instrument, unless a shall statement specifically limits the requirement to certain Flight Model units (i.e., FM-1 and FM-2).

Check the SOLAR CM tool Server https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

4 WORK PERFORMED BY THE CONTRACTOR (CLIN 001)

4.1 Program Management Office

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

The Contractor shall create a Program Management Plan complying with DID PM-1.

The Contractor shall establish effective communication with the Government Project Office through the Contracting Officer’s Representative (COR) that includes, but is not limited to, e-mail and telephone contact as necessary, weekly telecons with the Government X-Ray Irradiance

Sensor team, and one-on-one contact between NASA and Contractor discipline engineers, for the

COR to coordinate.

The Contractor shall prepare, lead, and provide minutes for biweekly teleconferences with the

Government to discuss status, risks, issues, schedule, and other business-related activities.

Once instrument integration and test (I&T) begins, the Contractor shall include the Government team in the Contractor’s regularly scheduled I&T meetings.

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 Database (MAID), or spreadsheet, listing all Request for Actions (RFA) 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. The database lists author and origin (PDR, telecon, etc.) of the RFA, person responsible for closure, wording of the RFA, response (DID

RVW-7), person(s) authorizing final closure, due date, date closed, and a column for

Government concurrence and comment.

The Contractor shall not delete closed action items from the MAID.

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

4.2 Resource Management

The Contractor shall establish, implement, and maintain a comprehensive Resources

Management System (RMS) for planning, authorizing, and controlling the total resource effort for each tracking payment milestones, technical resources, schedule, and subcontract performance.

The Contractor shall use Microsoft Project (latest version) as the scheduling tool for the generation and reporting of project schedules.

The Contractor shall define and implement a parts program for all flight and GSE parts that minimizes the risk of a schedule delay, in the event of a part or component failure, inadvertent

Check the SOLAR CM tool Server https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

damage, contamination, or by other plausible events or conditions and based on the Contractor’s historical experience, current practices, and lessons learned from similar Class C missions.

The Contractor shall provide private office space with a locking door, furniture, and high-speed internet access in the vicinity of the PMO for one Government resident and one visiting representative. The office shall be available from project PDR until instrument delivery.

The Contractor shall provide property management of NASA Property, including Government

Furnished Equipment (GFE), in accordance with contract clauses.

4.3 Visitor Badging

The Contractor shall accommodate facility access and badging for SOLAR Project representatives throughout the life of the contract. SOLAR Project representatives may be

Government or support contractors.

This shall include short term visitor badging for all Contractor-hosted meetings, Technical

Interchange Meetings (TIMs), Working Groups (WGs), and reviews, as well as long-term, unescorted badging for up to 6 Project representatives in order to accommodate long-duration visits, e.g., during integration and test (I&T) and resident personnel.

If the Contractor requires training for entry into any facilities, the Contractor shall provide the necessary training to Project representatives. The Contractor shall provide this training in a timely manner.

The Contractor shall coordinate with the Government for badging of Contractor personnel for access to NASA and NOAA facilities as required for support of the contract.

The Contractor shall coordinate with the Spacecraft vendor for badging of Contractor personnel for access to Spacecraft facilities as required for support of the contract.

4.4 Configuration and Information Management

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

The Contractor shall establish, implement, and maintain a Government approved Configuration

Management System (as outlined in DID PM-1 Appendix D) that provides Configuration

Management control of configured items including all flight hardware and software, and all GSE hardware and software. This encompasses all documentation developed under this contract, including drawings, procedures, plans, CDRLs, and program review materials.

The Government will establish and maintain a XRIS Box for secure file sharing at https://box.nasa.gov or equivalent. The Government will maintain a folder on the portal for X-

Ray Irradiance Sensor only, accessible by the Contractor and selected Government personnel, for document delivery and the exchange of information.

https://box.nasa.gov/

Check the SOLAR CM tool Server https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

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 establish a Configuration Control Board(s) to review and approve changes to the flight design documentation, software, GSE and all controlled documents.

The Contractor shall submit Class I changes to the Government for approval before implementation of the change. Note: Class I changes affect an item’s fit, form or function

Engineering Change Requests should conform with DID PM-4.

The Contractor shall submit Class II changes to the Government for concurrence with the classification. Note: Class II changes are changes to correct documentation or changes to hardware not otherwise defined as a Class I change.

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

4.4.1 Documentation

The Contractor shall develop, produce, deliver, and maintain all documentation required by and in accordance with the SOLAR X-Ray Irradiance Sensor CDRL.

The Contractor shall comply with applicable export control protocols: Export Administration

Regulation (EAR) or International Traffic in Arms Regulation (ITAR), as determined by the

Contractor or the NASA GSFC Export Control Office. The Contractor shall appropriately mark information provided to the SOLAR Project that is subject to export control restrictions and will leave information unmarked that is not.

All efforts, including the performance of tests and analyses not otherwise explicitly stated in other parts of the SOW, but determined jointly by the Contractor and the Government to be mission critical, shall be performed and documented by the Contractor.

All documentation, data, and analyses generated for or applicable to the contract effort, whether formal or informal, deliverable, or non-deliverable shall be made available to the Government and Government support Contractor’s upon request. This information shall be provided electronically through the XRIS Box or a Contractor provided web portal that provides

Government document download capability.

4.5 Program Review Requirements

The Contractor shall provide the technical and administrative support for all XRIS reviews and meetings.

The Contractor shall provide technical support to observatory system-level reviews, observatory integration and test reviews, mission operations reviews, and monthly and quarterly financial reports (DID RM-1).

Check the SOLAR CM tool Server https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

Unless otherwise stipulated, all reviews and meetings will be held at the Contractor's facility.

4.5.1 Kick-off Meeting

Approximately one month after award the Contractor shall prepare and conduct a Kick-Off

Meeting covering introductions between the Government and Contractor teams, an overview of the instrument, and a line-by-line review of the contract schedule and clauses, SOW, X-Ray

Irradiance Sensor Requirements Specification, XRIS MAR, and XRIS CDRLs.

The Contractor shall provide their interpretation of each line item (“Shall” statements)

The Contractor shall plan for a two-day review.

4.5.2 Working Groups and TIMs

4.5.2.1 Working Group Meetings

A working group is a cross-organizational team that meets periodically to address specific mission functions or implementation processes for each mission. Working group meetings can be combined with other meetings for more effective use of time and travel and may be via teleconference. Not all working groups meet regularly or over the entire implementation lifetime.

For planning purposes, the Contractor shall participate with the appropriate technical support for the working group meetings as defined in Table 1.

Table 1 Working Group Meetings

Working Group/Meeting Period Meeting

Frequency

Length

(hours) hours)

Location Contractor

Role

Safety & Mission Assurance

Working Group

ARO –

LRD

Weekly 1 Telecon Participate

Instrument to Spacecraft

Interface Working Group

ARO –

Final

Instrument

Integration

Bi-Weekly 2 Telecon Participate

Calibration and Algorithm

Working Group

PDR -

PLAR

Monthly

Weekly from

PER -

Commissionin g

1 Telecon Participate

Simulator Working Group PDR-PLAR Monthly 1 Telecon Participate

Check the SOLAR CM tool Server https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

Working Group/Meeting Period Meeting

Frequency

Length

(hours) hours)

Location Contractor

Role

Integration & Test Working

Group

PDR –

CDR

CDR – PER

PER – LRD

Monthly

Telecon Participate

Magnetics Working Group Kickoff –

PLAR

Monthly 2 Telecon Participate

Contamination Control

Working Group

PDR – PSR

3 months prior to each of the milestone reviews

1 Telecon Participate

E2E Working Group

E2E Test 1

- 6 Months

Observatory

PSR

Weekly 1 Telecon Participate

Commissioning Working

Group CDR – PSR Quarterly 2 Telecon Participate

Check the SOLAR CM tool Server https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

4.5.2.2 Technical Interchange Meetings (TIMs)

A TIM is an informal meeting between the Contractor and Government representatives to discuss a system process or feature. For example, a TIM may be conducted to reach understanding of an operation or analysis, present test results, discuss planned interface changes, plan for an upcoming test, etc. TIMs typically are held at the Contractor’s facility. Experts may be dialed-in via teleconference with web-based desktop sharing.

The Contractor shall support a number of TIMs as defined Table 2 with the Government and other Contractors, such as instrument representatives, operations personnel, ground system provider, IV&V personnel, etc.

Table 2 Technical Interchange Meetings

Item Planned Date Length (Days) Location

TIMs 5 per year 1 each Telecon

4.5.3 Peer Reviews

The Contractor shall define and implement a program of periodic tabletop engineering and risk mitigation reviews (peer reviews) throughout the life cycle to identify and resolve concerns as they arise, and prior to formal, system level reviews.

Peer review teams shall comprise of technical experts from the Contractor and the Government with practical experience relevant to the technology and requirements to be reviewed.

The Contractor shall provide Government notification ten business days prior to all peer reviews so that Government representatives can prepare and be present.

4.5.4 Instrument Design Reviews

The Contractor shall prepare and conduct Instrument Design Reviews for the Independent

Integrated Review Team that will be chaired by the Government. The reviews shall cover all aspects of flight and ground hardware, software, and operations for which the Contractor has responsibility.

The Contractor shall conduct a 1-day dry-run chart flip-through via a telecon and/or video conferencing with online collaboration tools for each design review, with the Government X-Ray

Irradiance Sensor team, 2 weeks prior to the review.

After each formal review, the Contractor shall document all RFA's with planned closure date in the MAID within 1 week of receipt.

Each design review, such as the SRR, PDR, CDR, etc., is not considered complete until approved by the Government. If the Government determines that instrument design review criteria is not met, a delta review to address deficiencies would be necessary, the Contractor shall conduct such review at a time to be mutually agreed-upon with the Government.

Check the SOLAR CM tool Server https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

Each formal review shall meet entrance and exit criteria as required by NPR 7123.1D Appendix

G. The Government and Contractor shall review the entrance and exit criteria prior to formal reviews and tailor the criteria, if required. For reference, GSFC-STD-1001A provides guidelines and criteria in support of planning and implementing the project reviews.

The Contractor shall participate in a meeting approximately 6 weeks prior to a formal review to review entrance and exit criteria prior to formal reviews and tailor the criteria, if tailoring is required.

The Contractor shall establish an agenda for each Instrument Review in coordination with the

Government at least four weeks prior to the review.

The Contractor shall participate in a Pre-brief one week prior to formal reviews to ensure all deliverables are delivered or are on schedule for delivery and the Contractor is ready to proceed to the review.

4.5.4.1 System Definition Review (SDR)/Systems Requirements Review (SRR)

The Contractor shall prepare and conduct an SDR/SRR (DID RVW-1) after all requirements have been allocated to the subsystem level.

The Contractor shall plan for a two-day review, not including resolution of RFAs.

4.5.4.2 Preliminary Design Review (PDR)

The Contractor shall prepare and conduct a PDR (DID RVW-1) at the conclusion of the preliminary design efforts and after testing the breadboard or brass board models of critical subassemblies/assemblies.

4.5.4.3 Critical Design Review (CDR)

The Contractor shall prepare and conduct a CDR (DID RVW-1) prior to the start of manufacture of the FM hardware unless the Contractor requests and the Government concurs with an earlier start.

4.5.4.4 Pre-Environmental Review (PER)

The Contractor shall prepare and conduct a PER (DID RVW-1) prior to the start of environmental testing of each FM to establish the readiness of the system and to evaluate the environmental test plans and procedures.

Check the SOLAR CM tool Server https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

4.5.4.5 Pre-Storage/Pre-Shipment Review (PSR)

The Contractor shall prepare and conduct a PSR (DID RVW-1) prior to placement of each FM into storage at the Contractor's facilities.

The Contractor shall plan for a two-day pre-storage review, not including resolution of RFAs.

The Contractor shall prepare and conduct a pre-ship review prior to the shipment of each FM.

The Contractor shall plan for a two-day pre-ship review, not including resolution of RFAs.

4.5.5 Observatory Level Reviews

The Contractor shall provide technical support to all Observatory level and Mission reviews for each FM. The Observatory and Mission reviews, their estimated length, and location is provided in Table 1 Formal Observatory and Mission Reviews.

The Contractor shall support the Observatory level reviews, as required, by presentations and/or documentation; for example, an instrument overview or design summary, test and data evaluation summaries, etc.

Table 3 Formal Observatory and Mission Reviews

Observatory Reviews Review

Length

(Days)

Location

Critical Design Review (CDR) 2 Spacecraft contractor’s facility

Pre-Environmental Review (PER) 2 Spacecraft contractor’s facility /Telecon

Pre-Shipment Review (PSR) 2 Spacecraft contractor’s facility /Telecon

Spacecraft Integration Readiness Review

(SIRR)

1 Telecon

Instrumentation Integration Readiness Review

(IIRR)

1 Spacecraft contractor’s facility

Test Readiness Review (TRRs) 0.5 Spacecraft contractor’s facility

Mission Operations Review 2 Washington, DC area

Post Launch Assessment Review

(PLAR)/Handover Readiness Review (HRR)

1 Washington, DC area

4.5.6 Project Management Reviews

The Contractor shall prepare and hold Project Management Status Reviews (PMSR) once every two months.

The status reviews shall be held at the Contractor's facility and telecon through successful

Check the SOLAR CM tool Server https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

completion of the contract. Specific agenda items may be required by the Government, in addition to those already outlined in DID PM-5.

4.5.7 Test Data Reviews

The Contractor shall conduct a quick look data review in real-time following the execution of all environmental tests and/or between critical sections of tests, e.g. between axes during vibration testing, prior to breaking the test configuration setup to ensure that all necessary data has been collected.

The Contractor shall invite the Government to witness all tests in-person and to participate in the quick look data reviews.

4.5.8 Technical Meetings

The Contractor shall support Technical Interface Meetings (TIMs) and Working Group meetings with the Government and the spacecraft contractor for the purpose of discussing and/or resolving problems or items of interest.

4.5.9 Subcontract Subsystem and Instrument Reviews

The Contractor shall plan a series of subsystem reviews and document that plan as part of the

Program Management Plan.

Major subsystems may be included in instrument-level reviews as determined by the Contractor in the Program Management Plan. When major subsystems are subcontracted, those subcontracts should have reviews and the government invited to those reviews.

The Contractor shall conduct PDR and CDR reviews of all major sub-systems whether these subsystems are provided by the Contractor or by a subcontractor.

Whether internal or external, sub-system reviews shall be chaired by the Contractor and conducted by personnel not directly responsible for design or procurement of the hardware under review. The Government reserves the right to attend these reviews and requires 10 business days of advance notification.

The Contractor shall document the minutes and action items that result from these reviews and provide them to the Government.

The Contractor shall conduct internal software reviews.

The Contractor shall conduct tabletop code walkthroughs; the Government reserves the right to attend and requires three business days advance notice.

4.6 Schedule Management

The Contractor shall establish, implement, and maintain an X-Ray Irradiance Sensor Schedule

(XRISS) in accordance with DID RM-3. Each FM development and delivery shall be tracked in the schedule. The Contractor shall present schedule status at the Program Management Status

Reviews in accordance with DID PM-5.

Check the SOLAR CM tool Server https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

The Contractor shall obtain Government approval for X-Ray Irradiance Sensor Schedule changes that impact Deliverable Items or GFE delivery dates as defined in contract.

4.7 Risk Management

The Contractor shall implement and maintain a Risk Management Program addressing all programmatic, performance and reliability risks, in accordance with DID PM-1 Appendix A.

The Contractor shall evaluate, classify, and prioritize all identified performance, reliability, and quality risks and assess their potential impact on cost and schedule.

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 for each instrument.

The Contractor shall track all risks being mitigated on an ongoing basis; capture risk attributes and mitigation information by collecting data; establish performance metrics; examine trends, deviations, and anomalies; and writing risk mitigation plans as necessary.

Check the SOLAR CM tool Server https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

5 SYSTEMS ENGINEERING (CLIN 001)

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

The Contractor shall generate a X-Ray Irradiance Sensor System Specification (DID SE-3) that includes derived requirements from the X-Ray Irradiance Sensor Requirements Specification, if requirements in the X-Ray Irradiance Sensor MAR, the X-Ray Irradiance Sensor SOW drive the design, the contractor should include them in SE-3.

The Contractor shall use a requirements traceability tool to demonstrate that the X-Ray

Irradiance Sensor design addresses all requirements.

5.1 Systems Management and Engineering

The Contractor shall perform all system studies, trades, risk assessments, and fault management strategy necessary to develop an instrument system design that meets the system performance specifications.

The Contractor shall flow-down the X-Ray Irradiance Sensor performance requirements into engineering functional requirements, detailed equipment, 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, and generate a Detailed Design Specifications document in accordance with DID SE-4.

The Contractor shall establish and maintain a System Performance and Environmental

Verification Program (DID SE-9, DID SE-10, DID SE-11, DID SE-12, & DID SE-13) that demonstrates that each FM meets all mandated and derived performance requirements, and that the GSE meets all design and interface requirements and is safe to use with the flight hardware.

5.2 Observatory Interface and Accommodation

The Contractor shall coordinate with the observatory contractor and support technical interchange meetings to define the instrument accommodations and interfaces between instrument and observatory as well as instrument GSE to observatory GSE interfaces, and instrument GSE to NOAA GSE interfaces.

The Contractor shall provide support in the development of the X-Ray Irradiance Sensor to

Spacecraft (S/C) Interface Control Documents (ICDs) and MICD specified in the X-Ray

Irradiance Sensor specification. The spacecraft contractor will own the documents, the XRIS

Contractor shall be responsible for providing instrument specific input into the ICDs and adhering to the ICDs.

The Contractor shall support the observatory implementation contractor in design and test of all instrument to observatory interfaces: mechanical (including the location of the X-Ray Irradiance

Sensor instruments on the observatory), data interfaces, electrical, and thermal.

Check the SOLAR CM tool Server https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

The Contractor shall support pre-delivery data and electrical interface testing with the instrument emulator in coordination with the spacecraft contractor using a spacecraft contractor provided

Spacecraft to Instrument Interface Simulator (SIIS), at the spacecraft contractor’s facility

(Boulder, CO).

5.3 System Analysis and Allocations

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, magnetic cleanliness, contamination control, thermal, radiation, 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 conduct the analyses required to confirm the integrity of the instrument design, and to ensure that the performance of each instrument performance will be compliant with specifications over the operational design life.

The Contractor shall conduct analyses and simulations required to assure the combined subsystems function properly as an integrated unit.

The Contractor shall conduct data analysis and trending and maintain a trend database during instrument level testing, observatory level testing, post-launch operations, and mission operations in order to ensure stability of each instrument performance (DID I&T-3 & DID I&T-

4).

The Contractor shall conduct end-to-end analyses of the instrument to demonstrate the design will meet all performance requirements.

The Contractor shall develop and maintain over the duration of the contract, a computer simulation(s) and models for these end-to-end X-Ray Irradiance Sensor system analyses.

The Contractor shall provide the export of requirements and traceability linkages in a mutually agreed upon Excel formatted file or in the ReqIF (Requirements Interchange Format) https://www.omg.org/reqif/. (DID SE-3).

5.4 Contamination Control and Analysis

The Program shall meet all the contamination control requirements in the XRIS Specification and the Mission Contamination Control plan including, but not limited to, the venting, surface cleanliness, and outgassing requirements.

Post delivery the Contractor shall be responsible for performing all hands-on on contamination activities – cleaning for the instrument unless delegated to the spacecraft contractor or GSFC by mutual agreement.

https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.omg.org%2Freqif%2F&data=05%7C01%7Calejandra.constanteperez%40nasa.gov%7C1b374fbd081a4a47de4408dbdbd8a072%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638345495667329198%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=eyOn7B%2BafRwlOdI1dquEBqA8wlyDNJwNQ9sLLpRCkqM%3D&reserved=0

Check the SOLAR CM tool Server https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

5.5 Magnetic Control Plan

The Contractor shall implement a magnetic control and verification program to track, manage/report and test to ensure that the instrument-generated magnetic fields do not exceed the field limits during each instrument operation in accordance with DID SE-16.

The Contractor shall participate in the Government led magnetics control program.

5.6 Special Engineering Analysis

The Contractor shall conduct special engineering tasks and/or analyses relating to the development, implementation, and operation of the X-Ray Irradiance Sensor instruments, and ground systems as required and authorized by the appropriate contract clauses. These analyses should be document in an EAR per DID SE-2 as appropriate.

Check the SOLAR CM tool Server https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

6 FLIGHT MODEL (FM) (CLIN 001)

The Contractor shall develop two X-Ray Irradiance Sensor FMs, designated as FM-1 and FM-2.

FM-1 will fly on the SOLAR-B mission, and FM-2 will be designated as a spare.

The effort shall include fabrication, assembly, test, calibration, ground processing algorithm development, maintenance, storage (including cleaning and calibration verification after a TBD timeframe), delivery, and post-delivery support through the end of the contract.

FM-1 shall be functionally tested and environmentally tested to proto-flight qualification levels and durations as defined in the X-Ray Irradiance Sensor Requirements Specification to qualify the designs and procedures.

FM-2 shall be functionally tested prior to storage. FM-2 does not require environmental testing unless required by the contractor to replace FM-1 as the primary flight unit.

If the contractor determines that FM-2 shall replace FM-1 for schedule, technical, or other reasons, the spare shall be fully tested and delivered as required for FM-1 in the contract.

6.1 Design and Analysis

6.1.1 Instrument Design

The Contractor shall design the instrument to meet the performance and interface requirements, and document these designs in instrument block diagrams and approved or controlled drawings per DID SE-8.

To support and gain confidence in the design of critical and high-risk systems the Contractor shall perform subassembly/assembly level design and testing to verify expected performance prior to start of FM instrument fabrication.

The Contractor shall develop and maintain Assembly and Integration Procedures and Drawings.

The Contractor shall develop an Engineering Development Unit (EDU) to reduce, mitigate or retire critical subassembly or assembly risk. The EDU shall include fully functional parts and assemblies, fabrication, assembly, test, calibration, ground processing algorithms development and verification, maintenance, storage (including cleaning and calibration verification after a

TBD timeframe) plans, and techniques.

The EDU shall be functionally tested as defined in the XRIS Requirements Specification to qualify the designs, procedures, planning, and verify requirements, and demonstrate ground processing algorithms.

The Contractor shall conduct life tests of all mechanisms and other critical assemblies as specified in the X-Ray Irradiance Sensor Requirements Specification.

Check the SOLAR CM tool Server https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

The Contractor shall verify the expected performance of any design change before proceeding with fabrication of the changed article.

The Contractor shall ensure that all X-Ray Irradiance Sensor technologies achieve a Technology

Readiness Level (TRL) 6 by PDR.

The Contractor shall provide a list of any X-Ray Irradiance Sensor technologies that are below

TRL 6 at the time of award.

6.1.2 Flight and Ground Test Software Development and Maintenance

The Contractor shall design, develop, test, and implement flight software and GSE ground test software for the FM.

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 accordance with the Software Maintenance Plan.

The Contractor shall establish and maintain a Software Management Program to plan and document software development processes and procedures, software tools, reviews, resources, schedules, and deliverables (DID SW-1).

The contractor shall document and maintain under configuration control all software requirements in the X-Ray Irradiance Sensor Requirements Specification.

The contractor shall identify the person responsible for directing and managing the software assurance program and interfacing with Government assurance personnel.

The contractor shall identify safety critical software per Appendix A of NASA-STD-8739.8B

Software Safety Standard, or contractor standard equivalent.

The Contractor shall assist the Government’s software Independent Assessments, assess all review findings and recommendations, and implement corrective actions to address such findings and recommendations. Detailed justification and rationale shall be provided for any instances where the Contractor decided not to take corrective action on specific software design findings and recommendations.

The Contractor shall document the test approach and methodology in the Software Management

Plan for the software Verification and Validation in accordance with the XRIS MAR and deliver

Acceptance Test Reports within 30 days of software release or within 30 days of test (whichever is sooner).

The Contractor shall specify, design, review, develop, configuration control, and test the software component of firmware, consisting of computer programs and data loaded into a class of memory not dynamically modifiable by the computer during processing in the same rigorous manner as the flight software. These include Programmable Read Only Memories, Programmable Logic Arrays, Digital Signal Processors, Field Programmable Gate Arrays, etc.

Check the SOLAR CM tool Server https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

The Contractor shall develop and maintain one Flight Software Development Environment

(FSDE), including hardware, software, procedures, and associated documentation, to be used for the life cycle management, development, and verification of the flight software at the

Contractor’s facility.

The Contractor shall classify each Computer Software Configuration Item (CSCI) in accordance with the software classifications definitions in Appendix D of NPR 7150.2D.

The Contractor shall maintain a Government approved tailoring compliance matrix against NPR

7150.2D requirements, including those accomplished by subcontracts, for each software classification/CSCI.

The Contractor shall implement the safety requirements of NASA-STD-8739.8B when a system or subsystem is determined to have safety critical software.

The Contractor shall provide Government insight into software design, development and test activities including monitoring integration and verification adequacy, trade study data, auditing the software design and development process, and participation in all software peer reviews and technical interchange meetings.

The contractor shall perform an analysis of unnecessary and/or unreachable code, as defined per

GSFC-STD-1000 (Rev I) Table 3.02-1, on the intended flight load for launch. The analysis shall identify all instances (areas) of unnecessary/unreachable code, the general functionality associated with the code, the reason each is intended to be left within the flight load, and the justification (e.g., mitigating action) that explains why the included code does not provide a risk to the mission.

The contractor shall ensure that SW functional requirements and comprehensive performance verification/validation testing is performed by qualified testers that are independent of the SW designers and developers.

6.1.3 Ground Processing Algorithms (GPA)

The Contractor shall provide Ground Processing Algorithms (GPAs) to produce data to be compliant with the requirements specified in the X-Ray Irradiance Sensor Requirements

Specification. The algorithms shall be documented in a Ground Processing Algorithm Document

(GPAD) (DID OPS-5).

The Contractor shall provide a copy of the GPA source code, both "as-run," and as-updated, for validation. The GPA source code shall be configuration controlled in accordance with the

Contractors software management plan. The Contractor shall provide updated source code when new versions are released. It is strongly recommended that the source code should be in a language on NOAA’s operational baseline (e.g., Python is strongly preferred) and should not depend on libraries or routines that are not in NOAA’s operational baseline.