Attachment A - Statment of Work (SOW) Rev - C.pdf

TSIS-2 Observatory SOW TSIS2-SC-SOW-0002 Revision C

Effective Date: November 26, 2019

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

TSIS-2 Observatory Statement of Work Signature/Approval Page

Prepared by:

Electronic signature on file

11/26/2019

Sergey Krimchansky Date Deputy Project Manager, TSIS-2 NASA Goddard Space Flight Center

Approved by:

Electronic signature on file

11/26/2019

Susan Breon Date Project Manager, TSIS-2 NASA Goddard Space Flight Center ii

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

Preface

This document is under the TSIS-2 project configuration control. Once this document is approved, TSIS-2-approved changes are handled in accordance with Class I and Class II change control requirements as described in the TSIS-2 Configuration Management Procedures, and changes to this document shall be made by complete revision.

Any questions should be addressed to:

TSIS-2 Configuration Management Office

NASA/ GSFC

Code 424 Greenbelt, MD 20771

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

Change History Log

Revision Effective Date Description of Changes

- 08/06/2019 TSIS2-CCR-0011 - Baseline A 08/12/2019 TSIS2-CCR-0017 - Addition of 4.11.2.2.2 Mission Operation

Support for Duration of Mission.

B 10/23/2019 TSIS2-CCR-0026, approved 10/23/2019 C 11/26/2019 TSIS2-CCR-0029, approved 11/26/2019

Table of TBDs/TBRs/TBSs

Action Item No.

Location Summary

1 2.1/Table 1 Applicable Documents 2 2.1/ Table 2 Precedence of Documents 3 3.1 Space Segment 4 3.3 The observatory will be launched from a TBD launch site.

5 4.11.1/Table 6 Mission Rehearsals Subsystem Engineers 6 4.6.5 The contractor shall maintain, calibrate, and certify TSIS-2 spacecraft specific MGSE and EGSE for use at the TBD launch site as required by the TBD launch site ground safety review process.

v

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

Table of Contents

1 INTRODUCTION

1.1 Scope

1.2 Purpose

1.3 Definition of Terms

2 RELATED DOCUMENTATION

2.1 Applicable Documents

2.1.1 Precedence of Documents

2.2 Reference Documents

3 TSIS-2 MISSION OVERVIEW

3.1 Space Segment

3.1.1 Spacecraft

3.2 Ground Segment

3.3 Launch Segment

4 WORK TO BE PERFORMED BY THE CONTRACTOR

4.1 Project Management

4.1.1 Program Support Functions

4.1.2 Government Insight and Surveillance

4.1.3 Subcontractor Management

4.1.4 Non- Disclosure Agreements and Technical Assistance Agreements

4.1.5 Spare Parts

4.1.6 Electronic Distribution

4.1.7 Resident Office Services and Facilities

4.2 Safety and Mission Assurance

4.3 Configuration Management

4.3.1 Waivers and Deviations Process

4.4 Reviews

4.4.1 Spacecraft and Observatory Reviews and Meetings

4.4.1.1 Spacecraft Kick-Off Meeting

4.4.1.2 Spacecraft Preliminary Design Review

4.4.1.3 Spacecraft Critical Design Review

4.4.1.4 Spacecraft / Instrument Integration Readiness Review

4.4.1.5 Test Readiness Reviews

4.4.1.6 Monthly Status Reviews

4.4.1.7 Weekly Status Teleconference

4.4.1.8 Working Group Meetings

4.4.1.9 Technical Interchange Meetings

4.4.1.10 Peer Reviews

4.4.1.11 Observatory Pre-Environmental Review

4.4.1.12 Observatory Pre-Ship Review

4.4.2 Mission Reviews

4.5 System Engineering

4.5.1 Requirements Analysis, Allocations, and Verification

4.5.2 Interface Definition

vi

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

4.5.3 Thermal Math Models

4.5.4 Finite Element Models

4.5.5 Contamination

4.5.6 Goddard Open Learning Design Rules Compliance Assessment

4.6 Spacecraft

4.6.1 Drawings and Diagrams

4.6.2 Blanketing

4.6.3 Flight Software Development

4.6.3.1 NASA IV&V

4.6.3.2 Software Maintenance

4.6.4 Simulators

4.6.4.1 Government Furnished Simulators

4.6.4.2 TSIS-2 Spacecraft Simulators

4.6.4.3 Mission Operations Center Simulator

4.6.5 Ground Support Equipment

4.7 Spacecraft and Observatory Integration and Test

4.7.1 Spacecraft Integration and Testing

4.7.2 Instrument Integration

4.7.3 Observatory Integration and Test

4.8 Ground System

4.8.1 End-to-End (ETE) Testing

4.9 Spacecraft, Observatory and GSE Shipping; Handling and Transportation

4.10 Launch Site Operations

4.10.1 Launch Site Safety

4.10.2 Launch Site Operations Planning

4.10.3 Launch Site Processing Operations

4.10.4 Launch and Early Orbit Support

4.10.5 Reserved

4.10.6 Observatory Storage

4.11 Flight Operations Support

4.11.1 Mission Rehearsals

4.11.2 On-Orbit Performance Verification

4.11.2.1 Spacecraft Initialization and Commissioning

4.11.2.1.1 Spacecraft On-Orbit Performance Reports

4.11.2.1.2 TSIS-2 Instruments Initialization and Commissioning

4.11.2.2 On-Orbit

4.11.2.2.1 On-Orbit Acceptance

4.11.2.2.2 Mission Operations Support for Duration of Mission

4.11.2.2.3 Anomaly/Nonconformances Investigations

4.11.2.2.4 Decommissioning

Appendix A Abbreviations and Acronyms vii

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

List of Figures

Figure 1. TSIS-2 Mission Architecture

List of Tables

Table 1. Applicable Documents Table 2. Precedence of Documents Table 3. Reference Documents Table 4. Spacecraft Reviews and Meetings Table 5. Mission Reviews Table 6. Mission Rehearsals Table 7. Contractor Mission Operations Center Support

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

1 INTRODUCTION

1.1 Scope

The scope of this Statement of Work (SOW) encompasses the required effort from authorization to proceed (ATP) through the spacecraft development, observatory integration, delivery, launch, on-orbit checkout, acceptance, and 3 years Mission Operations and Decommissioning.

1.2 Purpose

The purpose of this SOW is to produce and deliver to the National Aeronautics and Space Administration (NASA) a Total and Spectral solar Irradiance (TSIS)-2 spacecraft.

The Contractor is responsible for the procurement of the separation system (RUAG PAS 381S (15”))between the Observatory and Launch Vehicle. All harnesses external to the instruments shall be provided by the Contractor (all instrument intra-harnesses will be government furnished equipment).

1.3 Definition of Terms

The To Be Supplied (TBS) means that the Government will clarify or supply the missing information during the course of the contract. To Be Reviewed (TBR) 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. To Be Determined (TBD) indicates further research or analysis is needed to determine the information, during the course of the contract. All changes to resolve these items will be completed through a formal process of configuration change review, approval, and contract modification.

Throughout the documentation:

The term “spacecraft” refers to the spacecraft whether or not instruments are integrated. The term “observatory” refers to the spacecraft bus with instruments. Compliance with observatory requirements shall be the responsibility of the spacecraft vendor unless otherwise stated.

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

2 RELATED DOCUMENTATION

These documents establish detailed specifications, requirements, and interface information.

Where a revision is not specified, the version at the time of ATP shall be used. The spacecraft/ observatory shall comply with the documents listed in this section to the extent specified herein.

These documents apply directly to the performance required, and contain provisions that constitute requirements of this SOW.

2.1 Applicable Documents

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

Table 1. Applicable Documents

2.1.1 Precedence of Documents

In the case of conflict between documents, the order of precedence shall be as listed below (except when lower precedent document specifically calls for an exception).

Table 2. Precedence of Documents

Document Title Document Number

TSIS-2 Observatory Contract

TBD

TSIS-2 Observatory SOW

TSIS2-SC-SOW-0002

TSIS-2 Observatory Requirements Document TSIS2-SC-REQ-0005 TSIS-2 Observatory MAR TSIS2-SC-REQ-0006 TSIS-2 Observatory CDRL TSIS2-SC-CDRL-0002 TSIS-2 Spacecraft to Instrument ICD** TBD

Document Title Document Number TSIS-2 Observatory Requirements Document TSIS2-SC-REQ-0005 TSIS-2 Observatory Mission Assurance Requirements (MAR)

TSIS2-SC-REQ-0006

TSIS-2 Observatory Contract Data Requirements List (CDRL)

TSIS2-SC-CDRL-0002

TSIS-2 Spacecraft Instrument Accommodation Requirements Document (IARD)

TSIS2-SC-TN-0003

TSIS-2 Spacecraft to Instrument Interface Control Document (ICD)

TBD

TSIS-2 Observatory to Launch Vehicle ICD* TBD TSIS-2 Mission Operations Center (MOC) to TSIS Science Operations Center (TSOC) ICD

TBD

TSIS-2 MOC to Near Earth Network (NEN)

ICD

TBD

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

TSIS-2 Observatory to Launch Vehicle ICD* TBD TSIS-2 MOC to TSOC ICD TBD TSIS-2 MOC to NEN ICD TBD

*To be provided by the launch vehicle vendor **or IARD until SC to Instrument ICD established

2.2 Reference Documents

The following documents are referenced herein and, amplify or clarify the information presented in this document. These documents are not binding on the content of this SOW.

Table 3. Reference Documents

Goddard Space Flight Center (GSFC) Rules for the Design, Development, Verification, and Operation of Flight Systems GOLD Rules

GSFC-STD-1000 Rev G

Security of Information Technology NASA Procedural Requirement (NPR) 2810.1A

Criteria for Flight and Flight Support System Lifecycle Reviews

GSFC-STD-1001A

Goddard Systems Reviews GSFC Procedural Requirement

(GPR) 8700.4

Risk Management (RM) GPR 7120.4 NASA Space Flight Program and Project Management Requirements

NPR 7120.5

Agency RM Procedural Requirements NPR 8705.4 NASA Systems Engineering Processes and Requirements NPR 7123.1 NEN User Guide 453-UG-002905 NASA Expendable Launch Vehicle Payload Safety Requirements

NASA-STD 8719.24

NASA Procedural Requirements for Limiting Orbital Debris NPR 8715.6 NASA Process for Limiting Orbital Debris NASA-STD-8719.14

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

3 TSIS-2 MISSION OVERVIEW

TSIS-2 is a Category 3/Class D mission with a 3 year mission life after a 60 day on-orbit commissioning period. The TSIS-2 spacecraft shall accommodate the payload, consisting of the Total Irradiance Monitor (TIM) and the Spectral Irradiance Monitor (SIM) with associated electronics and Fine Sun Sensor.

Figure 1 shows the TSIS-2 mission architecture including the Space Segment (SS) and Ground Segment (GS).

Figure 1. TSIS-2 Mission Architecture

3.1 Space Segment

The SS consists of the observatory and the Ground Support Equipment (GSE) that provides the functionality to perform ground-based integration and testing of the observatory prior to launch (the GSE is included in the SS since it is provided by the spacecraft and instrument providers).

The TSIS-2 observatory shall consist of the spacecraft with an integrated TSIS-2 payload.

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

The observatory shall operate in a 600 km sun-synchronous, circular, 98 degree inclination orbit with a 16:00 ± :15 LTAN, with instruments sun-pointing when not in eclipse, and pointing to dark space when in eclipse. It shall function with a large degree of autonomy during all of its modes, including fault detection and management. The observatory shall receive commands via S-band links. The observatory shall transmit stored housekeeping telemetry and TSIS-2 science data via S-band links.

The spacecraft contractor shall create and maintain a communication up-link and down-link budget to show a minimum of 6db of margin.

3.1.1 Spacecraft

In support of the mission objectives, the spacecraft contractor shall provide a spacecraft that accepts the TSIS-2 payload for integration. The spacecraft bus shall perform the standard observatory functions of data collection, communications, command and data handling, attitude and orbit control, power and thermal control, health and safety monitoring (including the payload); and provide fail-safe protection in the event of anomalous conditions.

The spacecraft shall operate for 3 years after the 60 day on-orbit commissioning period. It shall be designed for access to space via Electron, LauncherOne, or ESPA.

The TSIS-2 science and housekeeping data shall be collected and stored onboard the spacecraft.

The TSIS-2 data shall be subsequently downlinked to ground stations, as scheduled by the GS, via an S-band communications link.

3.2 Ground Segment

The GS includes all of the elements necessary to operate the mission, generate data products, and distribute data products to the user community and to Goddard’s Earth Sciences Data and Information Services Center for archiving.

The contractor shall provide the Mission Operations Center (MOC) consisting of a telemetry and command system, mission planning and scheduling system, flight dynamics and maneuver planning system, trending system, local archive system, configuration management (CM) system, autonomous monitoring system, and all of the infrastructure necessary to interface and protect the security of these systems within the MOC facility. The MOC shall rely primarily on its own S-Band antenna, and may use NEN antennas as needed, for commissioning and back-up.

All mission operations for the observatory shall be conducted from the MOC with the exception of the TSIS-2 instruments. TSIS-2 mission operations are conducted primarily from the TSOC although immediate control of the TSIS-2 instruments is maintained in the MOC. The MOC shall monitor health and safety of the TSIS-2 Instrument. Contractor shall demonstrate MOC operational resiliency that shall guarantee access to flight segment, with acceptable down time being twice a month for 2 hours each. Planned MOC maintenance shall be coordinated with the Project at least one week in advance.

The TSOC is located at The Laboratory for Atmospheric and Space Physics (LASP); the TSOC generates, and delivers to the MOC, command loads for the TSIS-2 instrument that conform to the mission planning schedule. The TSOC also receives all TSIS-2 raw mission data from the

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

MOC to monitor the health and safety of the instrument and to process into level 0 science data products. The TSOC delivers the level 0 products to the TSIS Science Data System (TSDS), also located at LASP.

3.3 Launch Segment

The Launch Services Segment consists of the launch vehicle (LV) and the associated facilities, equipment and services needed to place the observatory into orbit. This includes all LV GSE (hardware and software), the payload processing facilities (PPF), and the range support for the LV and the observatory. NASA will procure the LV and associated launch services via the NASA Launch Services Program (LSP). The observatory will be launched from a TBD launch site.

The contractor shall transport the SS and all associated GSE to the range to prepare for launch.

The Government will arrange for a PPF to be assigned at the range to support the final observatory integration and test activities required before launch.

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

4 WORK TO BE PERFORMED BY THE CONTRACTOR

The contractor shall provide all facilities, services, personnel and other resources necessary for the implementation of all efforts to meet the requirements as delineated in the following sections.

4.1 Project Management

The contractor shall provide a project management (PM) function with a single project manager who is responsible for control and coordination of all activities on the TSIS-2 observatory. The project manager shall serve as the central point of contact with the Government for all activities on the TSIS-2 observatory.

The contractor shall provide a TSIS-2 Project Management Plan (CDRL PM-2).

4.1.1 Program Support Functions

The contractor shall document security policies and procedures in a Program Security Plan

(CDRL PM-9).

4.1.2 Government Insight and Surveillance

The contractor shall open attendance to the Government to all contractor and subcontractor internal data, reviews, audits, meetings, and other activities related to the scope of the contract.

For access and insight activity, “Government” includes Government personnel and Government contractor personnel. The contractor shall notify Government quality assurance personnel and the contracting officer representative (COR) of meetings, reviews, or tests in sufficient time (nominally 10 working days) to permit meaningful Government participation.

The Government shall have unrestricted access to the contractor’s TSIS-2 CM and other electronic systems used to manage the TSIS-2 contract, including drawings and requirements verification database. This access shall be available from both inside and outside the contractor’s facility.

The contractor shall provide the Government and Government contractor personnel, for review purposes, access via off-site desktop computer to a secure restricted-access general-purpose electronic library. This library shall contain reports, analyses, as-run test procedures, test conductor logbooks and electronic command logs, requirements documentation, internal technical memoranda, Material Review Boards, Nonconformance Records, change requests and documentation, CDRLs, and all other TSIS-2 specific documents prepared by the contractor.

The contractor shall obtain all required access authorizations and submit any paperwork required for the contractor to access Government controlled facilities. The contractor shall allow access by the Government to all contractor facilities used for TSIS-2.

4.1.3 Subcontractor Management

The contractor shall ensure that technical, cost, and schedule oversight of subcontractors is established and maintained. The contractor shall ensure that all program, technical, insight, and mission assurance requirements are flowed to subcontracts before TSIS-2 work is performed by

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

any subcontractor. Status of all subcontracts shall be reported at each Monthly Status Review (MSR) per SOW paragraph 4.4.1.6. The contractor shall establish appropriate incoming inspection and acceptance testing of subcontractor deliverables.

4.1.4 Non- Disclosure Agreements and Technical Assistance Agreements

The contractor is responsible for executing any Non-Disclosure Agreements deemed necessary to enable information sharing among the TSIS-2 participating product and support contractors and subcontractors. The contractor is responsible for conducting Technical Assistance Agreements (TAAs) as required to implement the spacecraft and instrument integration and verification. Any other formal agreements between the contractor and other TSIS-2 participating contractors relevant to TSIS-2 shall be subject to Government review.

4.1.5 Spare Parts

As part of the Project Management Plan (CDRL PM-2), the contractor shall define and implement a spares program appropriate to support the delivery schedule in accordance with NASA’s project classification NPR 8705.4 Class D.

4.1.6 Electronic Distribution

All documents shall be delivered in electronic format to a GSFC TSIS-2 specified web portal unless otherwise noted. The contracting officer, COR, and CM shall be notified of electronic submission of the deliverable by email. Electronic deliverables shall be delivered in the following formats unless otherwise approved by the government:

Text Documents: MSWord Presentations: PowerPoint Spreadsheets: Microsoft Excel Schedules: PDF and MS Project Schematics and Drawings: Design Web Format (DWF) and PDF Photographs: JPEG or current industry standard.

Video: Any readily available open standard (e.g., AVI, MPEG)

4.1.7 Resident Office Services and Facilities

The contractor shall provide dedicated facilities including at least four desks for exclusive Government use that can accommodate Government in-plant representatives at the spacecraft development/build site. Facilities shall include securable office space, furniture, access to its wireless area network, network access to the contractor’s electronic database, and access to a copier and conference room. During instrument integration and testing, dedicated space shall be provided for the instrument provider.

4.2 Safety and Mission Assurance

The contractor shall develop, implement and maintain a comprehensive TSIS-2 safety and mission assurance program that meets the requirements of the TSIS-2 observatory Mission Assurance Requirements (MAR) document (TSIS2-SC-REQ-0006). The contractor shall perform all tasks required by the MAR and deliver all data and documents prescribed by the MAR and its CDRLs.

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

4.3 Configuration Management

The contractor shall perform CM that meets its institutional standards in support of the TSIS-2 project. The contractor shall provide TSIS-2 observatory configuration control before and after launch. The contractor shall maintain configuration control on the following:

Interface documentation Ground data system design (MOC)

EGSE/MGSE

Flight software Database Procedures Instrument configuration when integrated to observatory

4.3.1 Waivers and Deviations Process

The contractor shall submit in accordance with CDRL PM-4 a waiver or deviation for any flight item that is found to be non-compliant with any Government requirement and is not reworked to be compliant, or is not replaced with a compliant item.

The contractor shall have a change classification and impact assessment process that results in Class I and Class II Configuration Change Requests (CCRs). Class I CCRs shall be forwarded to NASA prior to being boarded. Change classes are defined in CDRL PM-4 . If the Government determines that a change has been incorrectly categorized as Class II the Contractor shall resubmit the change as Class I for approval.

4.4 Reviews

The contractor shall support the spacecraft, observatory, and mission-level critical milestone reviews described in the following sections, and shall submit the required material as specified in Review Data Packages (CDRL PM-10). The Criteria for Flight Project and Flight Support System Lifecycle Reviews (GSFC-STD-1001A) provides a detailed description of each of the Government-chaired reviews, the key evaluation factors, and the entrance and exit criteria.

Critical milestone reviews (identified in Table 4) will be chaired by the Government. The minutes, requests for action (RFA), and any other action items that result from these critical milestone reviews will be documented by the Government.

For those RFAs assigned to the contractor at each of the critical milestone reviews, the contractor shall submit a written response to the Government containing the information required to complete the assigned action. The Government will have approval authority over the RFA responses provided by the contractor; action items are not considered closed until written concurrence is received from the COR. The contractor shall present at each review the status of all open items and RFAs assigned to the contractor up to that point in the implementation, with the corrective action or resolution for each item.

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

4.4.1 Spacecraft and Observatory Reviews and Meetings

The contractor shall host the reviews in Table 4, presenting and discussing the subject matter appropriate for each review as specified in the subsections below. The plan dates and durations shown are notional, and will be re-assessed (within allowable fiscal year budget limitations).

Table 4. Spacecraft Reviews and Meetings

Review Planned Date Site Duration Reference Spacecraft Kick-Off ATP + 1 mo. Contractor 1 day 4.4.1.1

Spacecraft PDR ATP + 5 mos. Contractor 3 days PM – 10 Spacecraft CDR ATP + 9 mos. Contractor 3 days PM – 10

System Integration Review

(SIR)

ATP + 23 mos. Contractor 1 day PM – 10

Test Readiness Reviews 1 week before test Contractor 1 day PM – 10 Monthly Status Reviews Monthly Contractor 0.5 day PM – 1 Weekly Status Telecon Weekly Telecon 0.1 day PM – 1

Working Group Meetings As needed** Various <2 days 4.4.1.8 Technical Interchange

Meetings As needed ** Various <2 days 4.4.1.9

Peer Reviews As needed ** Contractor <1 day 4.4.1.10 Observatory PER First Observatory test – 1 to 2 weeks Contractor 2 days PM – 10

Observatory PSR Ship – 1 to 2 weeks

Contractor 2 days PM – 10

** For planning purposes, assume 6 per year

4.4.1.1 Spacecraft Kick-Off Meeting

The contractor shall present for review the plans, schedules, and activities. The contractor shall assure that the spacecraft baseline requirements are clearly understood and that the proposed design shall meet these requirements. The agenda and information to be presented shall be coordinated with the Government prior to the meeting.

4.4.1.2 Spacecraft Preliminary Design Review

The contractor shall conduct a Preliminary Design Review (PDR) describing the current spacecraft design in accordance with the Review Data Packages (CDRL PM-10) and Criteria for Flight Project and Flight Support System Lifecycle Reviews (GSFC-STD-1001A). The objective of this review is to present the preliminary status of the drawings, analyses, and engineering model development to show the approach meets performance and interface specifications. Preliminary calculations for mechanical loads, stress, torque margins, mass properties, moments of inertia and CG estimates, control stability analyses, thermal performance, radiation design, and expected lifetime shall be presented.

The contractor shall define at PDR all new and existing mechanical and electrical GSE (MGSE and EGSE) needed for the TSIS-2 spacecraft and observatory lifecycle. New GSE shall be designed, built, tested, maintained, and documented throughout the duration of the contract.

Existing GSE shall be recertified as required. MGSE consists of equipment and fixtures required

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

to operate, test, handle, lift, perform optical alignment, and maintain the TSIS-2 spacecraft and observatory at the spacecraft integration facility, and at the launch Site. MGSE also includes equipment required to provide the appropriate thermal and vibration test environments at the contractor’s facilities as specified in the TSIS-2 Observatory Environmental Verification Plan and Test Matrix (CDRL IT-6). The contractor shall provide protective covers that protect any spacecraft fragile components from minor impact as well as contamination. The EGSE consists of the system test equipment and software necessary to command, monitor, and test the TSIS-2 spacecraft and observatory at the contractor’s facilities to support all applicable testing (Comprehensive Performance Tests, Limited Performance Tests, environmental testing, end-to-end [ETE] tests, etc.), as required.

The spacecraft PDR shall be considered complete upon satisfactory closeout of PDR RFAs assigned to the contractor and deemed mandatory by the Government to demonstrate compliance with the criteria for this review and required to proceed into the critical design phase of the spacecraft development.

4.4.1.3 Spacecraft Critical Design Review

The contractor shall conduct a Critical Design Review (CDR) and shall present a final detailed design using substantially completed drawings, analyses, and breadboard/engineering model evaluation test results to show that the design shall meet the final performance and interface specifications and the required design objectives in accordance with the Review Data Packages (CDRL PM-10) and Criteria for Flight Project and Flight Support System Lifecycle Reviews (GSFC-STD-1001A). Changes required to the design from the PDR shall also be included.

Final calculations for mechanical loads, stress, torque margins, mass properties, moments of inertia and CG, control stability analyses, thermal performance, radiation design, power generation and storage, communications architecture, data storage, command and data handling, attitude and orbit control subsystem, and expected lifetime are to be presented. Final software requirements, software design, and updated system performance estimates shall also be presented. Parts selection, derating criteria, and screening results, and the results of the Failure Modes and Effects Analyses (FMEA), Fault Tree Analyses (FTA) and Probabilistic Risk Assessments (PRA) are to be presented.

The spacecraft CDR shall be considered complete upon satisfactory closeout of CDR RFAs assigned to the contractor and deemed mandatory by the Government to demonstrate compliance with the criteria for this review and required to proceed with the implementation phase of the spacecraft development.

4.4.1.4 Spacecraft / Instrument Integration Readiness Review

The contractor shall conduct a System Integration Review (SIR) prior to beginning integration of the TSIS-2 spacecraft and instruments. Successful completion of the SIR shall result in Government concurrence that the spacecraft performance is adequate for the beginning of the instrument integration process, in accordance with the Review Data Packages (CDRL PM-10).

Minutes, RFAs, and any other action items that result from the SIR shall be documented by the contractor.

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

The spacecraft IIRR shall be considered complete upon satisfactory closeout of IIRR RFAs assigned to the contractor and deemed mandatory by the Government to demonstrate compliance with the criteria for this review and required to proceed with integration of the TSIS-2 instrument with the spacecraft.

4.4.1.5 Test Readiness Reviews

The contractor shall conduct Test Readiness Reviews (TRR), in accordance with the Review Data Packages (CDRL PM-10) for each test at the spacecraft and observatory level. The review shall be held one week before the start of the subject test. At each TRR, the contractor shall demonstrate that all test planning, facilities, staffing, procedures, GSE, and documentation are ready for the subject test. For testing that involves the TSIS-2 instrument, the contractor shall coordinate presentation material with the COR. The contractor shall present the pre-test configuration and status of the unit to be tested, identify all anomalies, problem reports, deviations, waivers, and Unverified Failures (UVFs). Minutes, RFAs, and any other action items that result from these TRRs shall be documented by the contractor.

4.4.1.6 Monthly Status Reviews

The contractor shall present MSRs to the Government to review project status in terms of progress, accomplishments, schedule, critical milestone monitoring, technical issues, performance parameters (including margin), manpower, subcontracts progress, and to identify problem areas and assign action items for their solution. The contractor shall be prepared to discuss the past month’s schedule and the future two month’s schedules at MSR. To save time and travel, these meetings may be combined with other reviews, or conducted as teleconferences or videoconferences at the discretion of the Government. MSR minutes with a copy of the review hand-outs shall be submitted as the monthly status report, in accordance with Monthly and Weekly Status Reviews (CDRL PM-1).

4.4.1.7 Weekly Status Teleconference

The contractor shall participate in a scheduled weekly teleconferences with the TSIS-2 project office at GSFC to communicate status, most urgent issues, and schedule progress and plans for the next few weeks. The minimum contractor attendance shall consist of the project manager, systems engineer, and the appropriate technical lead managers as required.

4.4.1.8 Working Group Meetings

A working group is a cross-organizational team that meets as required to address specific mission functions or implementation processes.

4.4.1.9 Technical Interchange Meetings

A Technical Interchange Meeting (TIM) is a meeting between the contractor and Government representatives to discuss a system process or feature. TIMS shall be held as required at the spacecraft contractor facility.

4.4.1.10 Peer Reviews

Peer reviews provide focused, in-depth technical discussions that support the evolving design and development of a product subsystem including critical documentation or data packages. The peer review purpose is to add value and reduce risk through expert knowledge infusion, confirmation of approach, and specific recommendations. A peer review provides a penetrating

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

examination of design, analysis, manufacturing, integration, test and operational details, drawings, processes and data. Peer reviews shall be held for each critical subsystem in the months and weeks prior to a major review as a forum to generate and critique the review material, and also as-needed during the implementation whenever expert involvement is needed, for example, on part, material, test, or process issues. Peer reviews shall take place at the contractor’s facility. Peer reviewers shall be contractor peer representatives as well as Government representatives from within the TSIS-2 project and external to the project.

4.4.1.11 Observatory Pre-Environmental Review

The contractor shall conduct an observatory Pre-Environmental Review (PER) to review all hardware and software test configurations, test plans, procedures, facilities and responsibilities to ensure that the environmental testing will proceed in a controlled manner and that all the necessary requirements and procedures are documented and understood, in accordance with Review Data Packages (CDRL PM-10) and Criteria for Flight Project and Flight Support System Lifecycle Reviews (GSFC-STD-1001A). The PER shall be held no later than one week prior to planned exposure to the first environment, but after completion of comprehensive observatory electrical testing.

The observatory PER shall be considered complete upon satisfactory closeout of PER RFAs assigned to the contractor and deemed mandatory by the Government to demonstrate compliance with the criteria for this review and required to proceed with observatory environmental testing.

4.4.1.12 Observatory Pre-Ship Review

The contractor shall conduct an observatory Pre-Ship Review (PSR) per Criteria for Flight Project and Flight Support System Lifecycle Reviews (GSFC-STD-1001A). The contractor shall present the planned observatory Launch Site Test Procedures (CDRL IT-1).

The observatory PSR shall be considered complete upon satisfactory closeout of PSR RFAs assigned to the contractor and deemed mandatory by the Government to demonstrate compliance with the criteria for this review and required to support shipment of the observatory to the launch site and start of the launch site activities.

4.4.2 Mission Reviews

The contractor shall attend and support the reviews in Table 5, presenting and discussing (for approximately one to two hours) the spacecraft and observatory status, and participating in any other mission discussions and splinter meetings related to the observatory implementation and test. The contractor supplied material to be presented at each mission review will be a subset of the preceding spacecraft or observatory review material, updated as necessary. The material to be presented at each review shall be prepared in coordination with the Government prior to the mission review. The plan dates and durations shown are notional, and will be re-assessed.

Table 5. Mission Reviews

Review Planned Date Location Duration CDRL Mission PDR SC PDR + 1 month GSFC 3 days PM – 10 Mission CDR SC CDR + 1 month GSFC 3 days PM – 10 TSIS-2 Instrument PSR FY 2022* LASP 1 day n/a

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

Review Planned Date Location Duration CDRL Operational Readiness Review L – 40 days SC/Ground

Segment Contractor

2 days PM – 10

Mission Readiness Review L – 25 days GSFC 1 day PM – 10 Safety & Mission Success Review

L – 25 days NASA HQ 1 day PM – 10

Launch Readiness Review L – 2 days Launch Site 1 day PM – 10 Post Launch Assessment Review L + 60 days GSFC 3 days PM – 10

* Actual dates will be determined by the Government in coordination with the TSIS-2 instrument provider and the Contractor.

4.5 System Engineering

The system engineering effort shall include the following:

a) Provide technical clarification and oversight throughout all phases of the program.

b) Lead formal and informal reviews. This shall include responsibility for the preparation of responses to all action items assigned to the contractor during the reviews, documentation of closure, and documentation of the minutes from each review.

c) Establish a comprehensive program of peer reviews. Ensure all peer review actions are closed appropriately and the results of the peer reviews are documented.

d) Conduct Technical Interchange Meetings with the Government, as necessary, and documenting the minutes and actions from these meetings.

e) Support all MSRs.

f) Perform and document all system studies, analysis, and trades and risk assessments necessary to develop the spacecraft design, launch vehicle interfaces, space-ground interfaces, and instrument interfaces. All analysis shall be document in formal controlled engineering reports.

g) Voting member of Failure Review Boards and Test Failure Review Boards.

h) Provide risk reduction and mitigation analysis.

i) Provide a Trend Parameter List and Approach ( CDRL SE-15) and acquire trend data to allow the evaluation of all critical functions, and analyze these data to demonstrate system integrity throughout the spacecraft and observatory test programs.

j) Develop, maintain and provide technical and programmatic documentation required to ensure successful operation of the observatory, including the Observatory User’s Manual containing the observatory flight rules (CDRL SE-13).

k) Review and approve all test procedures and all requirements verification reports.

l) Submit a Previously Qualified Hardware and Software Report in accordance with (CDRL

SE-8).

m) Maintain current best estimate (CBE) for Key Technical Parameters (KTPs) including the spacecraft mass, power, data rate, pointing, etc., and propose the allocation between margin (on Contractor side) and government reserve. Report KTPs and their trend at MSRs (4.4.1.6 and PM-1) and other major reviews.

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

4.5.1 Requirements Analysis, Allocations, and Verification

The contractor shall conduct complete analyses of the mission requirements, which fully establish, define, maintain and control system budget allocations. The results of all analyses shall be made available by the Contractor for Government review upon completion.

The contractor shall ensure all requirements in the TSIS-2 Observatory Requirements Document (TSIS2-SC-REQ-0005), the Spacecraft to Instrument ICD, the Observatory to Launch Vehicle ICD, the MOC to TSOC ICD, and the MOC to NEN ICD are met. These efforts shall include the following:

a) Preparing and maintaining the Performance Verification Plan and Matrix (CDRL SE-6) for use at the spacecraft and observatory levels of integration. The Performance Verification Matrix shall be tied to the contractor’s requirements management tool.

b) Utilizing a requirements management tool that is compatible with Excel.

4.5.2 Interface Definition

The contractor shall generate the Spacecraft to Instrument Interface Control Document. Since the TSIS-2 instruments are already designed, an IARD is provided with information that is required to accommodate the TSIS-2 instruments. The IARD will be superseded by the Spacecraft to Instrument Interface Control Document once it is established. The contractor shall provide inputs to the Observatory to LV ICD and support interface meetings as required.

The contractor shall generate the MOC to TSOC ICD and the MOC to NEN ICD.

4.5.3 Thermal Math Models

A Thermal Math Model (TMM) of the TSIS-2 instruments will be supplied by the Government for use in defining the spacecraft-Instrument interfaces. Per CDRL SE-4, the contractor shall combine the Government Furnished TSIS-2 instrument TMM with the analytical models of the spacecraft to create a system level thermal model of the observatory.

4.5.4 Finite Element Models

Finite Element Models (FEMs) of the TSIS-2 instruments will be supplied by the Government for use in designing the observatory. Per CDRL SE-5, the contractor shall combine the instrument FEMs with the spacecraft FEM to form an integrated comprehensive observatory FEM for launch and on-orbit configurations in support of the coupled load analyses to be performed by the Government launch services contractor.

4.5.5 Contamination

The contractor shall comply with the contamination requirements per MAR (TSIS2-SC-REQ- 0006). Note that there may be some particular instrument needs that shall be documented in the

ICD.

4.5.6 Goddard Open Learning Design Rules Compliance Assessment

The contractor shall complete an assessment of GSFC-STD-1000 4.5.6 Goddard Open Learning Design (GOLD) rules compliance including justification where an assessment of non-compliance is found and submit a GOLD Rules Compliance Matrix per (CDRL SE-17).

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

4.6 Spacecraft

The contractor shall produce the TSIS-2 spacecraft and verify its performance to meet all of the requirements as defined in Section 4.5.1 above.

If starting with a previously-existing proven/flown spacecraft design, the Government may give consideration for waiving any non-compliances to requirements listed in Section 4.5.1 above.

Any such non-compliances shall be addressed as early as possible, no later than two months prior to PDR.

4.6.1 Drawings and Diagrams

The contractor shall provide an Engineering Drawing Tree, Lists of Drawings, and all wiring diagrams covering the system, subsystem, component electronics, and interfaces with electrical/ mechanical GSE per CDRL SE-11 (see CDRL for details).

4.6.2 Blanketing

The spacecraft shall accommodate the interfaces between the instrument blankets and the spacecraft blankets.

4.6.3 Flight Software Development

The contractor shall develop, code, and test the spacecraft flight software, documenting the approach and plans in a Software Development and Management Plan (SDMP; CDRL SW-1).

The contractor shall treat the software component of firmware, which consists of computer programs and data loaded into a class of memory that cannot be dynamically modified by the computer during processing (e.g., programmable read-only memories, digital signal processors, etc.), as flight software.

4.6.3.1 NASA IV&V

The need for the contractor to support Independent Verification and Validation (IV&V) shall be determined later. If it is required, the contractor shall ensure that all software documentation and code required for NASA’s software IV&V effort is made available to NASA IV&V personnel.

This shall include access to all software reviews and reports, developer plans and procedures, software code, software design documentation, and software problem reporting data. The contractor shall permit electronic access to the required information or furnish soft copies of requested information to NASA IV&V personnel.

4.6.3.2 Software Maintenance

The contractor shall identify in the SDMP (CDRL SW-1) the flight software that shall require maintenance during nominal flight operations. Upon Government approval of the SDMP, the contractor shall develop and provide the procedures for this software maintenance and provide this maintenance for the duration of the contract. The contractor shall maintain the tools and utilities required to maintain the flight software (FSW) and simulator software for the duration of the contract. These tools shall be kept at the contractor’s facility.

4.6.4 Simulators

The requirements for simulators are defined in the following sections.

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

4.6.4.1 Government Furnished Simulators

The Government will provide the following simulators:

a) TSIS-2 instrument simulator (TSIM), which will send and receive commands, send Housekeeping (HK) and science telemetry, send science data comparable to flight format per ICD definition, and send analog signals simulating thermistors.

b) TSOC simulator, which will perform per the MOC-to-TSOC ICD. A simulator may not be required if it is agreed that exchange of formatted data is sufficient.

4.6.4.2 TSIS-2 Spacecraft Simulators

The contractor shall develop the TSIS-2 spacecraft simulator (SCSIM) that shall be capable of sending and verifying commands, receiving HK and science telemetry, receiving science data, receiving analog thermistor data, receiving table uploads per ICD definition, and verifying FSW updates.

4.6.4.3 Mission Operations Center Simulator

The MOC simulator shall be provided per MOC-to-TSOC ICD definition. A simulator may not be required if it is agreed that exchange of formatted data is sufficient.

4.6.5 Ground Support Equipment

The contractor shall provide the GSE to integrate, test, and verify the TSIS-2 spacecraft and observatory.

The contractor shall provide accommodations for the TSIS-2 instrument’s electrical and mechanical GSE and the TSIS-2 instrument’s stimuli. Instrument GSE and stimuli equipment to be used in contractor thermal-vacuum chambers for observatory testing will be certified for chamber use by the instrument contractor. All instrument GSE requirements (power, volume, etc.) are to be negotiated during TSIS-2 spacecraft to Instrument ICD development.

The contractor shall maintain, calibrate, and certify TSIS-2 spacecraft specific MGSE and EGSE for use at the TBD launch site as required by the TBD launch site ground safety review process.

In accordance with Chief Information Officer (CIO) directives and with the Agency’s Enterprise Architecture and Technical Reference Model (TRM), this acquisition requires all functionality, capabilities and features to be supported and operational in both a dual-stack IPv4/IPv6 environment and an IPv6 only environment. Furthermore, all management, user interfaces, configuration options, reports and other administrative capabilities that support IPv4 functionality shall support comparable IPv6 functionality. Respondents are required to have their products tested in an IPv6 certified 3rd party test facility to ensure it works in an IPv6 only environment and meets this requirement. The Government reserves the right to require the respondent to provide additional information on any product capabilities that are identified as not being IPv6 capable.

In accordance with FAR 11.002(g), NFS 1811.101-70, and CIO directives, this acquisition must comply with the NIST USGv6 Profile and IPv6 Test Program (http://www-x.antd.nist.gov/usgv6/supply.html). All interested parties responding to this acquisition are

Check the TSIS-2 TDMS Server at https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

required to provide a Suppliers Declaration of Conformity (SDOC) based on the attached “NASA Baseline IPv6 Requirements” or product specific “IPv6 requirements” and in accordance with NIST SP 500-267, NIST SP-273, and NIST SP 500-281.” If an SDOC is not immediately available, respondents must commit in writing to complete the necessary testing and provide the

SDOC.

4.7 Spacecraft and Observatory Integration and Test

4.7.1 Spacecraft Integration and Testing

The contractor shall integrate and functionally and environmentally test all spacecraft subsystems, software and contractor-provided instrument interface hardware for performance and for instrument compatibility at the observatory level.

Prior to instrument integration, the contractor shall qualify the spacecraft structural, thermal and electrical design per the Environmental Verification Plan and Matrix (IT-6), by verifying the design through a combination of analyses and tests. The contractor shall conduct a successful Comprehensive Performance Test (CPT) to demonstrate spacecraft readiness for observatory level integration prior to instrument integration.

The spacecraft shall be tested with calibrated and maintained GSE. The spacecraft GSE shall record and archive all telemetry from the spacecraft anytime telemetry is generated. The contractor shall provide and maintain a test log of the history of all spacecraft integrated testing in accordance with Test and Operations Logs (CDRL IT-5). This log shall also be maintained throughout observatory integration and testing, launch operations, and commissioning.

The contractor shall perform electrical interface testing prior to integration of any assembly, component or subsystem into the next higher assembly.