HaloSat-SOW-0008_Rev-Final_2016_06_13tp.pdf

CHECK http://traviata.physics.uiowa.edu/mediawiki/index.php

TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE.

Statement Of Work

HaloSat Spacecraft

HaloSat-SOW-0008

Revision -

Effective Date: May 18, 2016

Prepared By: Tom Johnson/800

Goddard Space Flight Center

Wallops Flight Facility http://traviata.physics.uiowa.edu/mediawiki/index.php

HALOSAT-SOW-0008

ii

CM FOREWORD

This document is a HaloSat Project controlled document. Changes to this document require prior approval of the HaloSat Project Configuration Control Board (CCB) chairperson or designee. Proposed changes shall be submitted per HaloSat Configuration Management Plan (HaloSat-PLAN-0004)

Questions or comments concerning this document should be addressed to:

Thomas Johnson HaloSat Project Manager Wallops Flight Facility Wallops Island, VA 23337 iii

Review/Approval Page

Prepared by:

/s/

Thomas Johnson

HaloSat Project Manager

NASA/GSFC/WFF Code 800

Date

Reviewed by

Luis Santos

HaloSat Systems Engineer

NASA/GSFC Code 599

Michael Mathews

HaloSat Systems Engineer

NASA/GSFC/WFF Code 589

Approved by:

Philip Kaaret

HaloSat Principal Investigator

University of Iowa

Date Keith Jahoda

HaloSat Scientist

NASA/GSFC Code 662 iv

HaloSat Project

DOCUMENT CHANGE RECORD

REV

LEVEL

DESCRIPTION OF CHANGE

DATE

APPROVED

Rev. -

Baseline Release. Approved by CCR - 001

5/18/2016 v

Table of Contents

1.0 Introduction

1.1 Purpose

1.2 Scope

1.3 Applicable Documents

1.4 Reference Documents

2.0 Spacecraft Description

2.1 Spacecraft Development Plan

3.0 Period of Performance, Frequency, and Duration for Requirements, Option, Meetings, Reviews, and Associated Data Deliverables

4.0 Deliverables

4.1 Contractor Data Deliverables

4.2 Contractor Support for HaloSat Project Documentation and Deliverables

4.3 Contractor Hardware Deliverables

4.4 NASA Deliverables to Contractor

5.0 Safety and Mission Assurance

vi

List of Figures

Figure 1: HaloSat Conceptual Design

List of Tables

Table 1: Applicable Documents

Table 2: Reference Documents

Table 2.1: Spacecraft Description

Table 3.1: Period of Performance, Frequency, and Duration for Requirements, Option, Meetings, and Reviews

Table 4.1: Contract Data Requirements List

Table 4.2: Contractor Support of HaloSat Mission Deliverables

Table 4.3: Contractor Hardware Deliverables

Table 4.4: NASA Deliverables

Appendix A. List of Acronyms

1.0 Introduction

The objective of the HaloSat mission is to help resolve the missing baryon problem by mapping the hot gas in the Milky Way to determine if the halo is extended or compact.

This objective will be accomplished by using a commercially available 6U CubeSat spacecraft bus and commercially available X-ray detectors to minimize cost and development risk. Figure 1 shows a conceptual design of HaloSat

Figure 1. Conceptual design of HaloSat using a 6U CubeSat and three X-ray detectors

HaloSat is a Principal Investigator (PI) led mission and the PI resides at the University of

Iowa. A team from the University of Iowa, GSFC, and Johns Hopkins will be developing the science instrument, which has three identical X-Ray detectors and will fly on a 6U

CubeSat Spacecraft. Wallops Flight Facility will provide management support, mission systems engineering, and is responsible for procuring a commercial 6U CubeSat

Spacecraft.

1.1 Purpose

NASA Goddard’s Wallops Flight Facility seeks a commercially available 6U CubeSat

Spacecraft for the HaloSat mission.

1.2 Scope

This Statement of Work (SOW) describes the 6U CubeSat Spacecraft that is required to implement the HaloSat Mission. The spacecraft shall provide a 6U mechanical structure, power system, attitude determination and control, command and data handling, communication, and be capable of supporting three identical science instruments. The spacecraft bus is allocated 2U of the overall 6U volume and the science instruments are allocated the remaining 4U.

The HaloSat Requirements Document (HaloSat-RQMT-0002) references a “spacecraft bus” and “observatory”. The “observatory” is the spacecraft bus with a Government furnished payload integrated to the spacecraft bus.

1.3 Applicable Documents

The HaloSat Spacecraft shall meet all requirements as defined in the following applicable documents.

Document Title Document Number

HaloSat Mission Requirements Document HaloSat-RQMT-0002

HaloSat Instrument Interface Control Document HaloSat-ICD-0007

NASA General Safety Program Requirement NPR 8715.3

NASA Research and Technology Program and

Project Management Requirements

NPR 7120.8

Table 1: Applicable Documents

1.4 Reference Documents

The following table includes a list of documents referenced throughout this document.

Document Title Document Number

NASA Procedural Requirements for Limiting Orbital

Debris

NPR 8715.6A

Launch Services Program Program Level Dispenser and CubeSat Requirements Document

LSP-REQ-317.01 Rev B

ICD Between NanoRacks CubeSats and NanoRacks

CubeSat Deployer

NR-SRD-029

HaloSat Concept of Operations HaloSat-PLAN-0003

HaloSat Configuration Management Plan HaloSat-PLAN-0004

CubeSat Design Specification (Cal Poly SLO) Latest Revision

GSFC System Engineering Requirements GPR 7123.1B

GSFC Rules for the Design, Development, Verification and Operation of flight Systems

GSFC-STD-1000

NASA General Environmental Verification Standard GSFC-STD-7000

Planetary Systems Corporation 6U Payload

Specification

2002367 Rev A

Standard Materials and Processes Requirements for

Spacecraft

NASA-STD-6016

Configuration Management GPR 1410.2

Table 2: Reference Documents

2.0 Spacecraft Description

The HaloSat Spacecraft Bus will be procured from a commercial vendor. A science instrument with three identical detectors will be designed, developed, integrated, and tested by the Instrument Team based at the University of Iowa. The baseline plan is for the Wallops Flight Facility to perform integration and subsequent testing of the science instruments to the spacecraft bus. However, an option has been included in this SOW for commercial vendors to bid on performing this requirement.

The spacecraft bus shall provide a 6U (2Ux3U) form factor mechanical structure, power system, attitude determination and control, command and data handling, communication, and be capable of supporting the science instrument. The spacecraft bus is allocated approximately 2U of the overall 6U volume and the science instrument is allocated the remaining 4U.

The 6U spacecraft bus shall meet the requirements specified in HaloSat-RQMT-0002, HaloSat Mission Requirements Document.

The operational scenario for the mission is provided in the HaloSat Concept of

Operations, HaloSat-PLAN-0003.

2.1 Spacecraft Development Plan

The HaloSat 6U Spacecraft Bus should be based on a mature design and all subsystems shall have prior spaceflight or development heritage. Table 2.1 below defines the requirements and option that are proposed for the HaloSat Mission.

Table 2.1 – Spacecraft Requirements Descriptions

Period DESCRIPTION SECTION

Base Requirements Phase: ATP-SRR 2.1.1

Base Design Phase: CDR 2.1.2

Base Implementation Phase: PER 2.1.3

Base Environmental Testing Phase: PSR 2.1.4

Base Launch Vehicle Integration Support 2.1.5

Base Engineering and Operations Support 2.1.6

Option 1 Spacecraft Bus and Science Instrument Integration and Testing

2.1.7

2.1.1 Requirements Phase: Authority To Proceed (ATP) – Systems Requirements

Review (SRR)

An Authority to Proceed (ATP) kick-off meeting shall be held at the Contractor facility no more than two weeks following contract award. The NASA project manager and systems engineer shall present a project overview, HaloSat requirements and project milestones. The Contractor shall present an overview of their design approach, processes and systems in place for Safety and Mission Assurance, Configuration Management and

Risk Management to ensure that the processes that the Contractor has in place meet the intent of NASA policies and procedures. The Contractor shall provide an overall project schedule and a facility tour.

At the Systems Requirements Review NASA assumes that the Contractor will present a mature spacecraft bus design that complies with the applicable documents listed in

Section 1.3, Table 1. Alternative solutions that meet the intent of the requirements will be considered. Particular attention should be given to areas requiring new development or modification and risks associated with the allocated requirements. A summary of the systems engineering process that generated the allocated technical requirements and the systems engineering planning for the next phase will be included. Analyses or trade studies associated with meeting the project requirements shall be presented. Since the applicable documents will be made available to the contractor well in advance of the

ATP, the SRR could be held in conjunction with the ATP. If the SRR is not held in conjunction with the ATP it shall be held no later than one month following the ATP.

2.1.2 Design Phase - Spacecraft Bus Critical Design Review

Upon completion of the ATP and SRR, the Contractor shall proceed to the design phase.

A long lead procurement status shall be provided as well as a flight hardware delivery receipt and acceptance process. The Contractor shall refine the design and the corresponding verification matrix, resolve any TBD’s, close out any SRR actions, and demonstrate a solution that meets mission requirements with acceptable margins.

Since it is expected that the spacecraft design is very mature, a single Critical Design

Review (CDR) will be held. At the CDR the contractor shall demonstrate that the design is sufficiently mature to support proceeding with full-scale fabrication, assembly, integration, flight software coding, and testing. At this review, the Contractor shall establish that it is on track to complete flight spacecraft development and that the spacecraft meets science instrument interface requirements.

2.1.3 Implementation Phase: Pre-Environmental Review (PER)

Upon successful completion of the Critical Design Review the Contractor shall proceed to the implementation phase. The Contractor shall begin fabrication of test and flight article components, assemblies and subsystems, close out any CDR actions and finalize test plans and procedures. A HaloSat Team Member shall be allowed at the Contractor facility during this phase to develop familiarity with spacecraft operations.

At the PER, the Contractor shall demonstrate that the flight spacecraft bus is ready for environmental testing. An initial comprehensive systems test shall have been performed successfully and the spacecraft bus (hardware/software), test facility, support personnel, and procedures are ready for testing. All procurements, GFE and GSE should be received, and facilities ready for use. Through a complete and comprehensive evaluation of the project status, the PER establishes readiness to proceed with environmental testing of the integrated flight spacecraft bus. The PER shall also demonstrate that the project is on track to complete flight and ground system development and to perform mission operations within the allocated cost and schedule resources.

2.1.4 Environmental Testing Phase: Pre-Ship Review (PSR)

Upon successful completion of the PER the Contractor shall proceed to the environmental testing phase. In this phase, the flight spacecraft bus shall be environmentally tested as specified in HaloSat-RQMT-0002, HaloSat Mission

Requirements. This shall include vibration testing and four thermal vacuum cycles. All flight hardware and software shall be verified to function as required before, during, and following environmental testing. This includes the deployment of all mechanisms following vibration and turn on at cold survival temperature. The flight-qualified system shall be delivered in place for storage at the Contractor facility for up to 30 days.

At the PSR the Contractor shall establish that all flight and applicable ground system verification activities have been successfully completed. The PSR examines the flight spacecraft bus, its end products, documentation, test data and support verification. It also ensures that the system has sufficient flight readiness to authorize its shipment to the designated storage facility or launch site. The PSR is conducted after successful completion of all verification activities, including environmental and functional performance testing as well as ground system and network compatibility testing. The contractor shall provide a shipping plan and the required shipping containers for the spacecraft.

The Contractor shall be responsible for final shipment of the spacecraft bus to a location within the continental United States as specified by NASA.

2.1.5 Launch Vehicle Integration Support

The contractor shall provide engineering support for test and integration of the spacecraft with the selected launch dispenser. This shall include two weeks of support, including travel, at a launch site in the United States. The launch will be provided by NASA’s

CubeSat Launch Initiative (CSLI) program. Depending upon the launch provider this support may not be required and this requiredment and associated funding would be descoped.

2.1.6 Engineering and Operations Support

The Contractor shall provide 320 hours of engineering and operations support as approved by the NASA Contracting Officer and assigned by the NASA Project Manager.

Examples of subject matter expert support can include mission unique trade studies, engineering and operational readiness test support, mission simulations, on-console support, on-orbit calibration and checkout support and anomaly resolution.

The Contractor shall budget travel costs for four (4) 1-week trips to NASA WFF by subject matter experts for engineering and operations support.

2.1.7 Option #1 – Spacecraft Bus and Science Instrument Integration and Testing

Perform integration of the government furnished science instrument to the spacecraft bus and perform functional and environmental testing of the full flight system. If the vendor is awarded this option, environmental testing of the spacecraft bus can be deferred to full system level (spacecraft bus and science instrument). The combination of the spacecraft bus and science instrument (i.e. payload) is defined as the observatory.

3.0 Period of Performance, Frequency, and Duration for Requirements, Option, Meetings, Reviews, and Associated Data Deliverables

The period of performance, frequency, and duration for the requirements, option, meetings, reviews, and associated data deliverables detailed in section 2.1 are defined in

Table 3.1.

Table 3.1 - Period of Performance, Frequency, and Duration for Requirements, Option, Meetings, Reviews, and Data Deliverables

Period DESCRIPTION PERIOD OF

PERFORMANCE

OF

REQUIREMENT/

REVIEW

FREQUENCY/

DURATION

OF

REVIEW/MTG

MTG

LOCATION

Base Project Kick-Off

Mtg

ATP + 1 week Once/1 day Contractor

Base Monthly Status

Mtg/Report-

Shall include technical progress, technical budgets and margins, risks (technical and schedule), schedule

(including top three critical paths and schedule variances), concerns, and issues.

Monthly/ 1 hour Telecom/Web

Ex

Weekly Report-

Provide accomplishments for the week, plan for the week ahead, concerns, issues, and risks.

Base Requirements

Phase: ATP-SRR

Presentation:

ATP + 1 month

Delivered 1 week prior to date of review

Once/1 day

Contractor

Base Design Phase:

CDR:

Presentation:

ATP + 2 months

ATP + 3 months

Delivered 1 week

Once/1 day

Base Implementation

Phase:

PER:

Presentation

ATP + 7 months

ATP + 10 months

Once /1 day

Base Environmental

Testing Phase:

PSR:

Presentation:

2 months

ATP +1 year

Once/1 Day

Base Launch Vehicle

Integration

Support

2 weeks

Base Engineering and

Operations

Support

ATP – Launch + 2 months

Option 1 Science

Instrument

Integration and

Testing

4 months

The overall period of performance for the delivery of the spacecraft bus shall be one year or less. The period of performances for requirements listed above are guidelines and the contractor can adjust the durations as desired as long as the overall period of performance for the requirements up through the environmental testing phase is less than or equal to 1 year.

4.0 Deliverables

4.1 Contractor Data Deliverables

The Contractor shall deliver the items shown in the Contract Data Requirements List

(CDRL) provided in Table 4.1

Table 4.1 - Contract Data Requirements List

CDRL Deliverable Description

01 Configuration

Management Plan

Provide a configuration management plan as defined in Section 7 of this SOW

02 Spacecraft EIDP End Item Data Package. Draft due at CDR and

Final at PSR. Shall include the following:

1. Spacecraft Systems Specification

2. Spacecraft System Interface Control Document

3. Spacecraft drawings including MICD and EICD

4. Spacecraft System Limitations and Constraints

5. Spacecraft Handling Procedure

6. Spacecraft Requirements Verification Matrix

7. Spacecraft System CMD/TLM Database

8. Spacecraft System Test Plans, Procedures, and

Reports

9. Spacecraft System Test Flow Chart

10. Spacecraft System Operations Manual

11. Spacecraft Configuration Item Data List

12. Spacecraft Flight Software Build

13. Limited Life/Age Sensitive Item List and

Records

14. Flight Connector Mating Records

15. Spacecraft Non-Conformance Reports

16. List of all Request for Waivers/Deviations

17. Record of Open and Deferred Work

18. Red Tag/Green Tag Items

19. Photo documentation

20. Declared Materials, Processes, and Parts List

21. Spacecraft Fault Management Document

22. Qualification and/or Acceptance Testing Report for all spacecraft components

23. Spacecraft DD250 Delivery Document

4.2 Contractor Support for HaloSat Project Documentation and Deliverables

The Contractor shall provide inputs and technical support for HaloSat Mission level deliverables as listed in Table 5.2.

Table 4.2 – Contractor Support of HaloSat Mission Deliverables

Required Input Contractor Support

ODAR Spacecraft Input for the Orbital Debris Assessment

Report. Draft due at SRR and final due at CDR

Safety Data Package Draft inputs due LRD – 6 months (TBD)

Final inputs due LRD – 3 months

NTIA License Required technical inputs required for submittal of NTIA license by NASA

Concept of Operations Technical inputs for the Missions Concept of Operations

4.3 Contractor Hardware Deliverables

The Contractor shall deliver the items listed in Table 4.3

Table 4.3 – Hardware Deliverables

Deliverable Description

Spacecraft Interface Simulator One Spacecraft Interface Simulator (SIS) to test the science instruments and support mission operation development. NASA anticipates that the contractor has a Commercial Off The Shelf (COTS) SIS available and will provide a description and cost of the SIS in the response to this SOW. Due CDR + 4 months

Spacecraft Bus Flight Spacecraft Bus to be delivered at PSR

Spacecraft Bus EGSE Electrical Ground Support Equipment that is required to perform functional testing of the Spacecraft bus. Due at

PSR.

Spacecraft Bus MGSE Mechanical Ground Support Equipment, including handling fixtures and shipping container. Due at PSR

Flight Spare Hardware In the event of flight hardware malfunction, the contractor shall provide flight spare hardware within 30 days of request by NASA. As an alternative, the vender can provide a repair and warranty plan. The contractor shall provide the associated cost of each of these options.

Launch Vehicle Integration

GSE

Spacecraft GSE that is required to support launch vehicle integration. Due at launch vehicle integration

Full Scale Spacecraft Models Two full-scale rapid prototype (3D printed) models for project reviews, presentations, outreach, and technical assistance. Deployables should be provided in deployed position. Due at CDR + 2 months

4.4 NASA Deliverables to Contractor

NASA shall deliver the items listed in Table 4.4 to the contractor

Table 4.4 – NASA Deliverables

Deliverable Description

Instrument Simulator One Instrument Simulator. Due Mission CDR + 4 months

3D model of instrument 3D model of the instrument. Model to include mass properties. First version due at Spacecraft kick-off, Final due at Mission CDR

Instrument Thermal Model Thermal model of the instrument. First version due at

Spacecraft kick-off, Final due at Mission CDR

Deployer test unit Deployer to be used for vibration testing of the spacecraft bus

5.0 Safety and Mission Assurance

As noted in section 1.3 of this document, the HaloSat Spacecraft Contractor is required to comply with NPR 8715.3 NASA General Safety Program Requirement. The primary objective of this Program Requirement for the HaloSat Mission is to ensure the safety of the employees supporting HaloSat and to have a positive effect on the overall success of the HaloSat Mission.

6.0 Configuration Management

The spacecraft contractor shall perform configuration management (CM) of flight hardware, mission-critical ground support equipment (GSE), and associated documents and drawings for the HaloSat Mission. This includes configuration baselines, configuration item identification, controlling changes to configuration items and controlled documents, maintaining status tracking/accounting records, and information dissemination.

The contractor shall provide NASA a plan on how they will perform configuration management for the HaloSat spacecraft. The HaloSat Configuration Management Plan

(HaloSat-PLAN-004) can be used as a guideline in developing this plan.

Appendix A – Acronyms

ATP Authority To Proceed

C

CDR

CDRL

CM

Celsius

Critical Design Review

Contract Data Requirements List

Configuration Management

CMD

CMO

Command

Configuration Management Office

COTS

CSLI

EIDP

EO

Commercial Off The Shelf

CubeSat Launch Initiative

End Item Data Package

Engineering Order

FRR

HaloSat

ISS

GPR

Flight Readiness Review

CubeSat mission to measure the oxygen line emissions from the hot Galactic halo

International Space Station

Goddard Procedural Requirements

GSE

GSFC

Ground Support Equipment

Goddard Space Flight Center

ICD Interface Control Document

I&T Integration and Test

N/A

NASA

NPR

Not Applicable

National Aeronautics and Space Administration

NASA Procedural Requirements

NTIA

ODAR

PDR

PER

PG

National Telecommunications and Information Administration

Orbital Debris Assessment Report

Preliminary Design Review

Pre-Environmental Review

Procedures and Guidelines

PIP

PSR

Project Implementation Plan

Pre-Ship Review

QA

QE

Quality Assurance

Quality Engineer

RFA

SOW

SRR

Request For Action

Statement of Work

Systems Requirements Review

SE Systems Engineer