Attachment 1 - TPE SOW.pdf

HQ085020R0002 Attachment 1

Tracking Phenomenology Experiment Statement of Work

1.0 Scope and Requirements

1.1 Scope

The Space Development Agency (SDA) seeks to launch one OPIR experimental satellite in 2021. This space vehicle, the “Tracking Phenomenology Experiment,” will characterize scene backgrounds for a range of satellite viewing conditions (including diverse solar/satellite viewing geometries, weather conditions, and terrestrial backgrounds), to optimize algorithms, CONOPS, and wavebands for advanced missile detection and tracking.

The Tracking Phenomenology Experiment shall be delivered to a nominal 1000 km circular orbit inclined at 60-90° as soon after GFE OPIR payload delivery as possible and no later than 31 March 2022. Government may consider proposals to fly at a lower orbital altitude.

Under a separate contract activity, an OPIR payload, with a payload mass expected to be < 60 kg, is being designed and manufactured for the government. SDA shall take ownership of this payload and shall deliver it as Government Furnished Equipment (GFE) for this contract activity not later than October 29, 2021. In this document, that payload is called the “GFE OPIR sensor” or “OPIR payload.”

This Statement of Work (SOW) defines the Contractor requirements to provide a satellite bus for the GFE OPIR sensor, satellite integration, launch integration, launch, and operations services to the Government for the Tracking Phenomenology Experiment.

1.2 Objectives

The objectives of this effort are to:

a. Integrate the GFE OPIR sensor into a Contractor-provided satellite bus and provide integration and engineering services.

b. Integrate the space vehicle onto a Contractor-provided domestic launch vehicle using a satellite adaptor as required.

c. Provide launch services to deliver the satellite to the specified orbit within the specified schedule.

d. Supply ground operations to support commanding and monitoring of the satellite and moving satellite telemetry and GFE OPIR sensor data to a government center for evaluation.

e. Incorporate best commercial and safety practices and regulations.

f. Comply with all classification guidance, ITAR, and US launch policy and statutes, as required. Contractor must be able to integrate and launch non-sight sensitive components.

1.3 General Roles and Responsibilities

The Contractor shall furnish all services to launch the Tracking Phenomenology Experiment including, but not limited to program management, spacecraft bus fabrication, satellite integration, mission integration, shipment of satellite to launch site, launch site support, ground and flight system safety, satellite bus and OPIR payload data delivery, and performance assurance.

SDA shall be responsible for the shipment of the GFE OPIR sensor to the location of satellite integration. SDA and/or its sensor Contractor shall be responsible for confirming no harm was incurred during shipment.

The Contractor shall be responsible for obtaining any necessary approval/licensing (e.g., Federal Aviation Administration) to successfully deliver the procured launch and operations services.

The Contractor shall be responsible for all integration and range services necessary to successfully deliver the launch service. The Contractor shall make all arrangements with the responsible authorities for the required launch range authorization and support for vehicle processing; integrated satellite payload/vehicle processing, launch; and launch site maintenance and modifications, and ground operations if required.

Government personnel shall attend relevant meetings and will provide technical support as needed.

1.4 Program Management

The Contractor shall perform program management tasks required to deliver the Tracking Phenomenology Experiment to the defined orbit and satisfy mission requirements. These tasks shall include as a minimum:

a. Participate in mission-level reviews, e.g., Preliminary Design Review (PDR), Critical Design Review (CDR), Pre-Environmental Test Review, Pre-Ship Review (PSR), and Launch Readiness Review (LRR). Determine the need for specific reviews with the Government and conduct them as necessary.

b. Conduct periodic satellite integration technical interchange meetings (TIMs) to work through satellite interface issues and provide evidence of bus & OPIR payload progress toward launch readiness.

c. Conduct periodic launch vehicle TIMs to work through interface issues and provide evidence of launch vehicle progress towards launch readiness.

d. Develop and maintain an integrated master schedule reflecting Contractor milestones and tasks necessary for spacecraft delivery, satellite integration, transportation, launch, and ground operations services.

e. Obtain all applicable licenses, permits, and approvals required by federal, state, and/or local regulatory agencies to include those required for launch and frequency allocation;

prepare and submit any environmental impact statements that may be necessary for the provisioning of the launch service.

f. The Contractor shall provide a single point of contact (POC) to the Government for mission management. The Contractor POC shall provide recurring status updates to the Government team reflecting progress on mission integration and launch operations.

1.5 Satellite Bus Performance

a. The satellite bus shall meet the functional and performance requirements in Attachment 3

– Technical Requirements Document.

b. Contractor shall describe its approach to, and obtain Government concurrence on, mitigation of any potential Electromagnetic Interference and Compatibility (EMI/EMC) concerns for bus and GFE OPIR payload performance during launch and on-orbit operations.

1.6 Launch Performance

a. The launch should occur no later than March 31, 2022. The Contractor shall identify a GFE OPIR payload need date for an earlier launch option, if an earlier launch is available. The Government reserves the right to exercise the option for the earlier launch date based on the GFE OPIR payload availability.

b. The Contractor shall deploy the Tracking Phenomenology Experiment to a nominal 1000 km circular orbit inclined at 60-90°. The Contractor may use any additional payload capacity for other purposes or clients, as long as the Tracking Phenomenology Experiment schedule, orbital parameters, and mission requirements are met.

c. The Contractor shall perform the launch vehicle planning, analysis, design, development, production, integration, and testing required to provide the launch service appropriate to transport the satellite to the desired orbit.

d. Launch loads shall not damage or degrade the satellite bus or GFE sensor.

1.7 Ground Operations

The Contractor shall monitor the satellite Health & Status and perform necessary steps to maintain its orbit characteristics to enable the imaging mission for the lifetime of the mission.

The Contractor shall download satellite telemetry and OPIR payload data and deliver it to the Government in a way determined by the Contractor and agreed to by the Government. This method should be secure and timely but is not required to be machine-to-machine.

On-orbit activities may take several forms, and examples of notional missions can be found in the following vignettes:

a. OPIR sensor calibration and characterization -- to tune and establish OPIR payload performance across the continuum of the technical envelope. These activities would notionally occur as often as daily and will require off-earth pointing for stellar measurements.

b. Background scene collections -- to measure the infrared signature of the ambient environment in which a target of interest might be included. These activities would notionally occur several times per day.

c. Commanded collections -- to assess the performance of operational techniques, tactics and procedures. These activities would notionally occur several times per day. Uplink of stored command sequences is expected to be available for scheduling commands for bus and OPIR payload.

The Contractor shall coordinate with the GFE OPIR sensor Contractor and Government to determine how the OPIR sensor will be operated on orbit.

The minimum duration for on-orbit operations is six months. Option(s) should be included to extend the Tracking Phenomenology Experiment mission to up to 1 year.

1.8 Compliance Documents

51 U.S.C. § 50131(a) requires the Federal Government to acquire space transportation services from U.S. commercial providers whenever such services are required in the course of its activities. To the maximum extent practicable, the Federal Government shall plan missions to accommodate the space transportation services of U.S. commercial providers. The National Space Transportation Policy (NSTP) provides that U.S. Government launch payloads shall be launched on vehicles manufactured in the United States.

Consistent with these requirements, the launch services for the Tracking Phenomenology Experiment are required to be provided by a U.S. commercial provider, using a launch vehicle manufactured in the United States. Proposers will be required to demonstrate that they have satisfied these requirements. The awarded contract will also require the contractor to continue to comply with 51 U.S.C. § 50131 and the NSTP.

2.0 Launch Vehicle Analysis, Design

The Contractor shall interface with the Contractor for the GFE OPIR sensor to determine the environment to which the OPIR payload is designed and to address launch vehicle environmental issues at the interface between the satellite bus and the OPIR payload, should they be found to exist. Potential mitigation approaches should be identified for any environments that exceed typical design levels for small satellites.

3.0 Development and Production

The Contractor shall be responsible for procuring the launch vehicle and for the manufacture, assembly, test and transport of the satellite and all mission hardware to the launch site; the Contractor shall provide all materials and equipment necessary for these tasks.

The Contractor shall self-insure itself to the extent required by public law.

4.0 Integration

The Contractor shall provide a satellite bus and integrate the GFE OPIR sensor. Working with the Government the Contractor shall determine and conduct integrated payload-bus testing with the integrated satellite to resolve issues caused by workmanship. The Contractor shall coordinate with the GFE OPIR sensor Contractor to develop any required interface documents.

The Contractor shall develop and manage any required interface documents.

The Contractor shall deliver draft and final Interface Control Documents (ICDs) at specified dates proposed by the Contractor.

The Contractor shall integrate and test the GFE OPIR sensor per small satellite best practices and provide results to the Government.

5.0 Launch Preparation

The Contractor shall perform the following tasks:

a. The Contractor shall integrate the Tracking Phenomenology Experiment onto the launch vehicle.

b. The Contractor shall identify and secure a launch site or range to meet the requirements of the launch service.

c. The Contractor shall deliver the satellite to the launch site.

d. The Contractor shall conduct a Launch Readiness Review (LRR), to provide evidence that the vehicle, range, and satellite are ready for launch.

e. The Contractor shall provide a safe environment for satellite storage prior to integration with the launch vehicle.

f. The Contractor shall coordinate with the Government and the GFE OPIR sensor

Contractor to ensure provisions during satellite transport and at the launch range are made to secure a satellite that is sensitive but unclassified. In addition, the Contractor should have, or be able to obtain, a SECRET facility clearance (TBR).

6.0 Launch Site Access

The Contractor shall provide access for Government and GFE OPIR sensor Contractor personnel at the launch site. Support should be consistent with the Contractor’s day of launch available information, which may include access to real‐time telemetry, voice communication channels, video and telephones, etc.

7.0 Security, Safety and Quality

The Contractor shall establish, implement, and maintain risk management, safety, quality and mission assurance programs in accordance with commercial best practices.

SDA anticipates the selected performer will require access and safeguarding for the sensitive but unclassified Tracking Phenomenology Experiment. SDA will issue a DD Form 254 attached as part of the contract award. As a result, the selected performer must have, or otherwise be able to obtain a SECRET Facility Clearance. Applicants will ensure all industrial and personnel security requirements are in place, and any Foreign Ownership, Control, and Influence (FOCI) issues are mitigated prior to receipt of the satellite. Additional information regarding facility clearances and FOCI can be found at www.dss.mil.

Proposers should include with their proposal any proposed solution(s) to security requirements unique to this program. Common program security requirements include, but are not limited to:

operational security (OPSEC) contracting/sub-contracting plans; foreign participation or materials utilization plans, manufacturing and integration plans; range utilization and support plans (air, sea, land, space, and cyber); data dissemination plans; asset transportation plans;

classified test activity plans; disaster recovery plans; classified material / asset disposition plans, and public affairs / communications plans.

Non-U.S. organizations and/or individuals may participate to the extent that such participants comply with any necessary nondisclosure agreements, security regulations, export control laws, and other governing statutes applicable under the circumstances.

8.0 Data Deliverables

The following data deliverables will be required as part of this effort. The Contractor shall produce and make the appropriate distribution of all data deliverables. The frequency for all deliverables is a one-time delivery plus any revisions, or as specified below.

a. Contract Kick-off documentation – (ATP + 30 days)

b. Technical interchange meeting documentation (approximately monthly)

c. Design and readiness review documentation for PDR, CDR and LRR (Read-ahead provided 3 working days prior to review)

d. Integrated OPIR payload-bus test plan (30 days prior to Test Event)

e. OPIR payload-to-bus interface control document (ATP + 60 days)

f. Bus specification (ATP + 60 days)

g. Documentation to verify mission and interface requirements have been met (7 days prior to pre-ship review of TPE to launch integration facility)

h. Post-launch report (including details of satellite-related items such as measured launch environments and satellite state vector at injection) (5 days after launch event)

i. Satellite bus and OPIR payload telemetry and data, delivered in a secure and timely fashion, throughout the duration of contracted operations