Attachment A - SOW - L1 Series SWIPS 1-09-2024.pdf

Effective Date: January 9, 2024 Expiration Date: January 9, 2024

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

L1SERIES-SWiPS-SOW-0003, Revision Chg - 01

Space Weather Next L1 Series, Code 493

Space Weather Next (SW Next) Lagrange 1 (L1) Series Project

Solar Wind Plasma Sensor (SWiPS) Statement of Work (SOW)

U.S. Department of Commerce (DOC) National Oceanic and Atmospheric Administration (NOAA) National Environmental Satellite, Data, and Information Service (NESDIS) National Aeronautics and Space Administration (NASA)

GSFC SW Next L1 Series CMO

January 12, 2024

Released

L1 Series SWiPS SOW L1SERIES-SWiPS-SOW-0003, Revision – Chg 01 ii

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

L1 Series Solar Wind Plasma Sensor (SWiPS) Statement of Work Signature/Approval Page

Prepared by:

Originally signed on 1/11/2024 by:

Alejandra Constante L1 Series STIS Instrument Engineer SW Next L1 Series NASA Goddard Space Flight Center

Reviewed by:

Originally signed on 1/12/2024 by:

Charles Hudson DeLee L1 Series Instrument Systems Manager SW Next L1 Series

Approved by:

Brennan Nowak Deputy Project Manager, SW Next L1 Series

J. Timothy Van Sant Project Manager, SW Next L1 Series iii

Check the L1 Series CM tool Server at 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 Space Weather Next (SW Next) Lagrange 1 (L1) Series 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.

Questions or comments concerning this document should be addressed to:

SW Next L1 Series Configuration Management Office Mail Stop: 493 Goddard Space Flight Center Greenbelt, Maryland 20771 iv

Check the L1 Series CM tool Server at 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) Revision - December 1, 2023 This was CCR L1SERIES-CCR-0021 to baseline the document and was approved on December 1, 2023 Revision –

Chg 01 January 9, 2024 The changes in this document were reviewed in CCR

L1SERIES-CCR-0049 and approved on January 9, 2024 v

Check the L1 Series CM tool Server at 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 REQUIREMENTS PRECEDENCE

3.1 Requirements Precedence

3.2 Terms and Definitions

4 WORK PERFORMED BY THE CONTRACTOR

4.1 Program Management Office

4.2 Resource Management

4.3 Contractor Integrated Performance Measurement

4.4 Integrated Baseline Reviews (IBRs)

4.5 Visitor Badging

4.6 Configuration and Information Management

4.6.1 Documentation

4.7 Program Review Requirements

4.7.1 Kick-off Meeting

4.7.2 Reserved

4.7.3 Peer Reviews

4.7.4 Instrument Design Reviews

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

4.7.4.2 Preliminary Design Review (PDR)

4.7.4.3 Critical Design Review (CDR)

4.7.4.4 Pre-Environmental Review (PER)

4.7.4.5 Pre-Storage/Pre-Shipment Review

4.7.5 Observatory Level Reviews

4.7.6 Project Management Reviews

4.7.7 Test Data Reviews

4.7.8 Technical Meetings

4.7.9 Subcontract Subsystem and Instrument Reviews

4.8 Schedule Management

4.9 Risk Management

5 SYSTEMS ENGINEERING

vi

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

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)

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.5 Post Delivery Support

6.5.1 Observatory Integration and Test Support

6.5.2 Launch Operations Support

6.5.3 Mission Operations Support

6.5.3.1 Delivery of FM and Operations Tools

6.5.4 End-to-End Test Support

6.5.5 Post-Launch Test Support

7 GROUND SUPPORT EQUIPEMENT (GSE)

7.1 Electrical Ground Support Equipment

7.1.1 Electrical System Test Equipment (ESTE)

7.1.2 Solar Wind Plasma Sensor Emulator (SWiPSE)

vii

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

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)

8 MISSION ASSURANCE

APPENDIX A ABBREVIATIONS AND ACRONYMS

APPENDIX B DEFINITIONS

Check the L1 Series CM tool Server at 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 Lagrange 1 (L1) 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 L1 Series Mission will procure a minimum of two (2) observatories 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 L1 Series Observatories are targeted to launch as individual primary payloads, December 2028 and October 2032.

This Statement of Work (SOW) defines those tasks necessary to design, analyze, develop, and fabricate two (2) flight Solar Wind Plasma Sensor (SWiPS) instruments.

The SOW also defines the tasks necessary to integrate, test, calibrate, evaluate, and support launch and on-orbit check-out of the SWiPS instruments, 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 second 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 September 2027, the second by June 2029.

SWiPS is part of the L1 Series of satellites which have a risk classification of C per 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. Two SWiPS Flight Models (FMs) Instrument, consisting associated electronics and harnesses between the various boxes, designated Flight Model-1 and Flight Model-2 (FM-1 and FM-2)

b. One Engineering Development Unit (EDU) Instrument, consisting of associated electronics and harnesses between the various boxes

c. Spares and built up and tested sub-assemblies

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

e. Four SWiPS Emulators

f. One Ground Processing Development Systems (GPDS)

g. All additional SWiPS Instrument Mechanical and Electrical Ground Support Equipment

(MGSE and EGSE) called out elsewhere in this document

h. All remaining items and documents specified in contract documents

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

Other Scope

The Contractor shall perform special studies relating to the development, implementation, characterization, qualification, and operation of the instruments as authorized by the Government, and in accordance with the ordering mechanism for Special Studies and Task Order clauses of the contract.

Acceptance criteria for Special Studies will be specified in the associated DO or Task Order.

Check the L1 Series CM tool Server at 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 SWiPS contract.

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

Solar Wind Plasma Sensor Requirements Specification, L1SERIES-SWiPS-REQ-0010 Solar Wind Plasma Sensor Mission Assurance Requirements Document (MAR), L1SERIES-SWIPS-REQ-0021

Solar Wind Plasma Sensor Contract Deliverables Requirements List (CDRL), L1SERIES-SWiPS-REQ-0015 NASA-STD-8719.13C NASA Software Safety Standard NPR 7150.2B NASA Software Engineering Requirements NASA Procedural Requirements (NPR) 8705.4, Risk Classification for NASA Payloads

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

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

3 REQUIREMENTS PRECEDENCE

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, Contract Deliverables Requirements List (CDRL), SWiPS Requirements Specification, SWiPS Mission Assurance Requirements (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 L1 Series SWiPS 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 L1 Series 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 L1 Series or support service contractors.

The terms “L1 Series Project Office,” “L1 Series Project,” and “Project” refers to the Government L1 Series Project Office.

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

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

Government civil servant and Government support contractors interfacing with and or providing the instrument or data for the various instruments (to be revised based on instrument vendor selection).

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

Check the L1 Series CM tool Server at 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

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 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 SWiPS team, and one-on-one contact between NASA and Contractor discipline engineers, for the COOR to coordinate.

The Contractor shall prepare, lead, and provide minutes for weekly 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 or spreadsheet includes a listing author and origin (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 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 Work Breakdown Structure (WBS) element, by instrument, and for providing timely and adequate visibility into manpower, materials, cost, schedule, travel, and subcontract performance.

The RMS shall be consistent with the contract WBS and provide timely and traceable incorporation of contract changes and document the effect on the resource management baseline.

The Contractor shall maintain and provide the WBS to the government once it is baselined and after any significant changes due to project changes or contract modifications.

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

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 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, copier(s), facsimile machine(s), phones and high-speed internet access in the vicinity of the PMO for one Government resident and one visiting representative.

The Contractor shall provide property management of NASA Government Furnished Equipment (GFE) and GSE.

Any major Sub-contractor that may be providing one or more of the SWiPS Subassemblies shall provide private office space, furniture, copier(s), facsimile machine(s), phones and high-speed internet access in the vicinity of the project office for one Government representative.

4.3 Contractor Performance Monitoring

4.3.1 Earned Value Management Plan

The contractor’s validated EVMS description or plan shall present the contractor's approach to comply with the EIA-748 guidelines.

The EVMS description or plan shall address the processes for conducting variance analysis;

developing ongoing comprehensive estimates at completion; flowing down requirements to all applicable subcontracts; and managing technical scope, schedule, cost, and risk.

4.3.2 Work Breakdown Structure

The work breakdown structure (WBS) identifies the work elements for estimating resources, budgeting and pricing and serves as the framework for recording cost, schedule and technical performance on the contract.

The WBS in SWiPS DID RM-6 (Contract Work Breakdown Structure and Dictionary) shall be utilized for recording of all contract related costs.

During this contract, the WBS shall be updated by the contractor with government approval, as necessary, to reflect new work, modifications/changes, changes in work element distribution, and configuration changes.

The contractor shall be responsible for traceability of subcontractor data supporting its WBS elements. The contractor may establish with a subcontractor any WBS that permits the prime contractor to fulfill its WBS requirements and that provides adequate control of the subcontract.

4.3.3 NASA Financial Report

The contractor shall submit NASA Contractor Financial Management Reports on NASA Forms 533 in accordance with the instructions in NPR 9501.2E, NASA Contractor Financial Management Reporting (DID RM-2 Financial Reports).

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

The detailed reporting categories to be used, which shall correlate with technical and schedule reporting, shall be set forth in the schedule.

Contractor implementation of reporting requirements shall include NASA approval of the definitions of the content of each reporting category and give due regard to the contractor's established financial management information system.

4.3.4 Risk Management Plan

Within the risk management process the contractor shall identify risks (technical, cost and schedule) on the project/program and establish mitigation plans.

This risk management process shall include a process for tracking and reporting risk status and changes.

Risk management board (RMB) approved mitigation plans for realized risks that pose cost/schedule impacts shall be accounted for in the IMS and encumbered in the project budget.

Cost/schedule impacts for unrealized risks shall be accounted for as threats or liens against project budget reserve.

IMS activities and encumbrances/liens/threats associated with risk mitigation shall be tied to the appropriate work breakdown structure (WBS) identifier and clearly associated with the risk within the risk management system.

4.3.5 Integrated Program Management Data and Analysis Report (IMPDAR)

The contractor shall include data pertaining to all authorized contract work, including both priced and un-priced effort that has been authorized at a not-to-exceed amount in accordance with the contracting officer's direction.

The contractor shall submit the integrated program management data and analysis report (IPMDAR) that shall separate direct and indirect costs and identify elements of cost for all direct reporting.

The IPMDAR period end date shall reconcile with the schedule status date and financial calendar period end date.

4.4 Integrated Baseline Reviews (IBRs)

The contractor shall provide and review its performance measurement baseline (PMB) plan to the Government within six months after contract award, and subsequently, when required, following major changes to the baseline or PMB.

The Government will verify during the IBRs that the contractor has established and maintains an integrated performance measurement baseline.

The contractor will ensure that the baseline includes the entire contract technical scope of work consistent with contract schedule requirements, and has adequate resources assigned.

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

The contractor will assure the Government that effective earned value methods are used to accurately status contract technical performance, schedule status and cost performance. The contractor will perform and provide a self-assessment of the cost and schedule risk for the IBR.

The IBR will be used to achieve a mutual understanding of the baseline plan, schedule and costs risks to the plan, and the underlying management processes used for planning and controlling the project.

4.5 Visitor Badging

The Contractor shall accommodate facility access and badging for L1 Series Project representatives throughout the life of the contract. L1 Series 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.6 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 that provides Configuration Management control of configured items including all flight hardware and software, all GSE hardware and software. This also encompasses all documentation developed under this contract, including drawings, procedures, plans, CDRLs, and program review materials.

The Contractor shall provide all documents called out in the CDRL plus all updates and revisions in accordance with the CDRL.

The Contractor shall produce, control, and maintain contract documentation in accordance with the CDRL. The Government will establish and maintain a secure website, called the L1 Series Portal. The Government will maintain a folder on the portal for SWiPS only, accessible by the Contractor and selected Government personnel, for document delivery and the exchange of information only.

Check the L1 Series CM tool Server at 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 document and drawing tree.

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

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 GSFC determines that a Class II classification is incorrect, the Contractor shall resubmit the change as a Class I change.

4.6.1 Documentation

The Contractor shall develop, produce, deliver, and maintain all documentation required by and in accordance with the L1 Series SWiPS 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 NASA GSFC Export Control Office.

The Contractor shall appropriately mark information provided to the L1 Series 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 a Contractor provided web portal that provides Government document download capability.

4.7 Program Review Requirements

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

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

The Contractor shall provide technical support to observatory system-level reviews, observatory integration and test reviews and mission operations reviews.

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

4.7.1 Kick-off Meeting

Approximately one month after award the Contractor shall prepare and conduct a Kick-Off Meeting covering a line-by-line review of the contract schedule and clauses, SOW, SWiPS Requirements Specification, SWiPS MAR, and SWiPS CDRLs.

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

The Contractor shall plan for a two-day review.

4.7.2 Reserved

4.7.3 Peer Reviews

The Contractor shall work with the Government to 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 be comprised of technical experts from the Contractor and the Government with significant 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.7.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 dry-run chart flip-through via a telecon and/or video conferencing with online collaboration tools for each design review, with the Government SWiPS team, two (2) weeks prior to the review.

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

Each dry-run and design review, such as the PDR, CDR, etc., is not considered complete until approved by the Government. If the Government determines that a delta review is necessary, the Contractor shall conduct such review at a time to be mutually agreed-upon with the Government.

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

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

The Contractor shall prepare and conduct an SDR/SRR 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.7.4.2 Preliminary Design Review (PDR)

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

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

4.7.4.3 Critical Design Review (CDR)

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

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

The Contractor shall prepare and conduct a Delta-CDR for each flight model after the first unit.

The Government may waive the requirement for a Delta-CDR if no changes have occurred.

4.7.4.4 Pre-Environmental Review (PER)

The Contractor shall prepare and conduct a PER 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.

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

4.7.4.5 Pre-Storage/Pre-Shipment Review

The Contractor shall prepare and conduct a pre-storage review prior to placement of each Flight Model 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 instrument.

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

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

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

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

Table 1 Formal Observatory and Mission Reviews

Observatory Reviews Review Length

(Days) Location

System Requirements Review (SRR) 2

Spacecraft Contractor’s Facility/Telecon

Preliminary Design Review (PDR) 2 Spacecraft Contractor’s

Facility/Telecon

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

Instrument Integration Readiness Review (IIRR) 1 Spacecraft Contractor’s

Facility

Test Readiness Reviews (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.7.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 through successful completion of the CDR, then alternate between a Government designated facility and the Contractor's facility.

Specific agenda items may be required by the Government.

4.7.7 Test Data Reviews

The Contractor shall prepare and conduct table-top test data reviews with Government personnel on the overall instrument status and performance for each FM.

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

The Contractor shall conduct data reviews prior to the shipment of deliverable GSE.

The Contractor shall prepare and conduct reviews of the interim data following any instrument or system level performance verification or calibration test prior to the breakdown of any test setup to ensure collection of good data, and prior to the Pre-Storage and Pre-Shipment Reviews to determine readiness.

The Government reserves the right to attend all Test Data Reviews and requires ten (10) business days of advance notification.

4.7.8 Technical Meetings

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

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

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 make them available on the Government website.

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.8 Schedule Management

The Contractor shall establish, implement, and maintain a Solar Wind Plasma Sensor Instrument Schedule (SWiPSIS). Each FM development and delivery shall be tracked in the schedule. The Contractor shall present schedule status at the Program Management Status Reviews.

The Contractor shall obtain Government approval for SWiPSIS changes that impact Deliverable Items or GFE delivery dates as defined in contract.

4.9 Risk Management

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

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

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 L1 Series CM tool Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

5 SYSTEMS ENGINEERING

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

The Contractor shall generate a SWiPS System Specification that includes derived requirements from the SWiPS Requirements Specification, the SWiPS MAR, and the SWiPS SOW.

The Contractor shall use a requirements traceability tool to demonstrate that the SWiPS design meets 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 SWiPS 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.

The Contractor shall establish and maintain a System Performance and Environmental Verification Program that demonstrates that the 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 SWiPS to Spacecraft (S/C) Interface Control Documents (ICDs) and MICD specified in the SWiPS specification.

The Contractor shall support the observatory implementation contractor in design and test of all instrument to observatory interfaces: mechanical, including the location of the SWiPS instruments on the observatory, electrical, and thermal.

The Contractor shall support at the Spacecraft Contractor’s or the instrument facility (TBR) pre-delivery data and electrical power interface testing with the instrument emulator or EDU in coordination with the spacecraft vendor using a spacecraft vendor provided spacecraft to Instrument Interface Simulator.

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

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.

The Contractor shall conduct end-to-end analyses of the instruments to demonstrate the designs 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 SWiPS 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 Contractor shall establish a Contamination Control Program (CCP) and provide the resources necessary to assure that appropriate contamination control is exercised through all phases of instrument manufacture, build-up/assembly, integration and test, and observatory integration and test, launch site processing, and on-orbit operation. This includes assuring that SWiPS will not produce contamination that degrades companion instruments and spacecraft subsystem performance

Supplemental CCP documents shall be developed for cleanroom operations, contamination protocols, cleaning procedures, monitoring plans, vacuum bake out plans, I&T plans, launch site processing, and any contamination-related plans for the on-orbit phase.

The Contractor shall establish and document contamination allowances and budgets for performance degradation of sensitive surfaces, components, and thermal contamination-sensitive hardware such that, even when degraded by contamination within the stated allowance, the hardware will meet its end-of-life mission objectives.

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

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

For molecular contaminants, the Contractor begins by choosing low Total Mass Loss (TML)/Volatile Condensable Mass (VCM) materials, schedules bake-outs of parts, components, harnesses, etc., and performs a mass transport analysis for molecular contamination demonstrating that the SWiPS is not a contamination source for the other more sensitive instruments, such as L1 Series Coronagraph.

For particulates, the Contractor shall demonstrate that the instruments are not a source of particulate contamination. This would generally include choosing low particulate-generating, non-shedding materials and coatings, performing particulate testing and monitoring during each mission phase, and scheduling frequent cleaning/verification of SWiPS surfaces.

The Contractor shall perform all cleaning that is required to maintain contamination at defined levels.

The Contractor shall report the status of all contamination control activities at Instrument Design Reviews, technical meetings and PMSRs.

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.

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 SWiPS instruments and ground systems, as required and authorized by the appropriate contract clauses.

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

6 FLIGHT MODEL (FM)

The Contractor shall develop two SWiPS FMs, designated as FM-1 and FM-2, to fly on the L1 Series missions.

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.

The first FM shall be functionally tested and environmentally tested to proto-flight qualification levels and durations as defined in the SWiPS Requirements Specification to qualify the designs and procedures. After successful qualification of the first FM, subsequent units may be tested at acceptance levels if they are exact duplicates of the first flight instrument, if agreed and approved by the Government. The Second sensor unit in the set of SWiPS can be environmentally tested to acceptance levels if it is an exact duplicate of the first sensor flight model and environmentally tested separately from the first sensor.

6.1 Design and Analysis

6.1.1 Instrument Design

The Contractor shall design the instrument to meet the performance and interface requirements.

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 SWiPS Instrument Requirements Specification to qualify the designs, procedures, planning, and verify requirements, and demonstrate ground processing algorithms.

The EDU shall be designed such that it is portable.

The Contractor shall conduct life tests of all mechanisms and other critical assemblies as specified in the SWiPS Requirements Specification.

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

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

The Contractor shall ensure that all SWiPS technologies achieve a Technology Readiness Level (TRL) 6 by PDR.

The Contractor shall provide a list of any SWiPS 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 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.

The Contractor shall document and maintain under configuration control all software requirements in the SWiPS 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-8719.13 Software Safety Standard, or equivalent, with NASA/GSFC COR approval.

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 SWiPS MAR and deliver Acceptance Test Reports within 30 days of software release or within 30 days of test (whichever is sooner).

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

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 in the same rigorous manner as the flight software. These classes include Programmable Read Only Memories, Programmable Logic Arrays, Digital Signal Processors, Field Programmable Gate Arrays, etc.

The Contractor shall develop and maintain one Flight Software Development Environment (FSDE), including hardware, software, procedures, and associated documentation, to be used for

Check the L1 Series CM tool Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that…