Attachment_3_-_Draft_RISE_TO_0001_SOW_TacticalC3_-_26_Mar_18.pdf

R&D INTEGRATED SPACE EXPERIMENTS (RISE) CONTRACT

FA9453-18-R-0003, ATTACHMENT 3

TASK ORDER 0001

TACTICAL COMMAND, CONTROL, AND COMMUNICATIONS

(TACTICAL C3) SMALL SATELLITES STATEMENT OF WORK

26 MARCH 2018

1.0 Mission and Background

The objective of this Task Order is to provide the Integrated Experiments and Evaluation Division (AFRL/RVE), with research and development, systems engineering, mission development, assembly, integration and test (AI&T) capabilities, and program management for space experiments supporting Tactical Command, Control, and Communications (C3) for Class 2 and Class 3-level satellites.

This effort involves spacecraft component design, optimization and analyses, analytical and experimental testing, and integration of technologies and/or components into system-level spaceflight (or near-space) experiments, including system-level functional and environmental testing, launch vehicle integration, mission operations support, data processing, and analysis. This effort includes: (1) Program Management, (2) Concept Design, (3) Hardware and Software Engineering, (4) Design and Fabrication,

(5) Assembly, Integration, and Test (AI&T), (6) AI&T Laboratory Support (7) Space Worthiness Testing, (8) On Orbit Operations, and (9) Technology transition. This Task Order focuses on Class 2 and 3 efforts as defined in the Basic Contract Statement of Work.

The objective of RVE is to develop and demonstrate space-based capabilities for the Air Force. This work includes mission formulation, system requirements, design and development, AI&T, and on orbit operations. Moreover, the work is comprised of four (4) phases focused on rigorous systems engineering processes:

• Phase A is focused on maturing a concept to Critical Design Review (CDR). At the end of Phase A, a competitive down-select decision occurs.

• Phase B matures the concept from CDR to a Pre-Ship Review (PSR). Phase B concludes with a further down-select where the winning satellite(s) is/are brought to AFRL laboratory facilities.

• Phase C is environmental and performance testing and integration to the launch vehicle at the launch site.

• Phase D involves conducting on-orbit operations.

2.0 Scope

The Government anticipates a demonstration of up to three (3) satellites with Tactical Data Link (TDL) communications payloads. The TDLs which comprise the payload(s) are to be determined (TBD) but could include some/all/more than the following; Link-16, Situational Awareness Data Link (SADL), Intra Flight Data Link (IFDL), Multifunction Advanced Data Link (MADL), Tactical Targeting Network Technology (TTNT), and Protected Tactical Waveform (PTW).

This demonstration of TDLs from space will provide a resilient communications backbone in support of a Multi-Domain Command and Control (MDC2) capability.

Below is a notional schedule for the Tactical C3 Demonstration based on the current Government estimate.

Activity Schedule Pre-acquisition and Gov Reference Design (GRD) development

Q3FY19

System Requirements Review Q2 FY20 Preliminary Design Review Q1FY21 Critical Design Review Q4FY21 Technology Readiness Review Q2FY22 Pre Ship Review Q4FY22 Demo Ops Activities Q2FY23 through Q1FY24

At this time, the Government anticipates the contractor’s support for this Task Order shall consist of program coordination and systems engineering support up to and including CDR in Phase A.

3.0 Compliance and Reference Documents

Compliance and Reference Documents are listed in Attachments 1 and 2 of the Basic Contract Statement of Work.

4.0 Requirements

4.1 Mission Design

4.1.1 The contractor shall support concept development and the refining of large programmatic objectives into mission requirements. This includes mission analysis and documentation for flight (space/air) and/or ground experiments, such as definition of mission objectives and mission success criteria, Concept of Operations (CONOPS) trades, mission constraints, mission alternatives, and refining mission and system objectives.

4.1.2 The contractor shall perform modeling and simulation to support programmatic and engineering trades.

4.2 Implementation

4.2.1 The contractor shall perform systems engineering to support the Tactical C3 program.

Associated with this effort is the refinement of designs (i.e. spacecraft bus subsystems and spacecraft bus design trade-offs), requirements and their flow-down, information assurance/cyber security (ground and space), interface definition (specifically in the areas of Interface Control Documents (ICDs)), interfaces between the Government and mission partners, cost/schedule trades, and space-to-ground data interfaces.

4.2.2 The contractor shall attend and participate in programmatic, technical, and safety reviews (i.e., SRR, PDR, CDR, etc.) through CDR of the mission development. Typical activities include: 1) researching, preparing and presenting formal briefings at program reviews; 2) reviewing briefings and related documents and 3) providing recommendations to the Government.

4.2.3 The contractor shall analyze the complete system design(s) to meet system reliability, mission operability, and performance requirements for the Tactical C3 program.

4.2.4 The contractor shall perform various mechanical and electrical engineering tasks. These tasks include, but are not limited to, confirming system and product capabilities by designing feasibility and testing methods/properties, developing/reviewing engineering specifications to clarify design details and functional criteria of experimental electronics, frequency management and Communications Security (COMSEC) engineering in support of the Tactical C3 program.

4.2.5 The contractor shall develop and implement a tailorable configuration control program, to include payloads, spacecraft, ground-based experiments, and space-based experiments.

4.2.6 The contractor shall perform assessments of components, payloads, test equipment, experiment plans, and/or spacecraft designs to meet the mission architecture and evaluate components against other available payloads and/or spacecraft component designs and technologies.

4.2.7 The contractor shall develop hardware/software to support testing and evaluation of development satellites (i.e. flatsats). Flatsats are used throughout most phases for program scoping, requirements and performance testing, baseline for the flight vehicle, and as operations testing platforms for command verification.

4.2.8 The contractor shall perform subsystem assembly and test in the AFRL/RVE facilities or at field locations, test ranges, and other Government-directed facilities.

4.2.9 The contractor shall leverage commoditized (COTS) components (i.e. avionics, subsystems, payloads, etc.) when possible in meeting mission requirements.

4.2.10 The contractor shall develop, or support the development, of spacecraft flight software as well as ground software to test or evaluate various flight software systems.

5.0 Contract Management

The contractor shall perform Contract Management requirements in accordance with Section 5 of the Basic Statement of Work.

6.0 Security Requirements

The contractor shall establish and implement information and physical security programs governing their efforts in accordance with the Task Order DD254 Contract Security Classification Specification.

At a minimum, contractor personnel shall be eligible to obtain a Secret clearance. [PLEASE CONTACT

CONTRACTING FOR SPECIFIC BILLETING INFORMATION].

7.0 Associate Contractor Agreements

The contractor shall enter into Associate Contractor Agreements (ACA) for any portion of task order performance requiring joint participation in the accomplishment of the Government's requirement.

ACAs shall be executed in accordance with requirements in paragraph 7 of the Basic contract SOW.

8.0 Deliverables

The following list captures the applicable contract data requirements for TO 0001 deliverables:

Item Title Frequency A001 Contract Funds Status Report

Monthly

A002 Status Report

Monthly

A003 Scientific and Technical Report End of contract A004 Test/Inspection Report As needed A005 System Safety Hazard Analysis Report At award A007 Software Design Description As needed A008 Software Requirements Spec As needed A009 Software Test Report As needed A010 Funds and Man-Hours Expenditure Report Monthly A011 Integrated Program Management Report Monthly A012 Purchase Order Quarterly A013 Computer Software Products As needed A014 Software User’s Manual As needed A015 Systems Engineering Management Plan Quarterly A016 Technical and Management Work Plan Quarterly A018 Data Accession List Quarterly A021 Presentation Material As needed A022 Scientific and Technical Reports Summary As needed A023 Interface Control Document As needed A024 Government Property Inventory Report Annually

9.0 Base Support

The contractor shall provide base laboratory support in accordance with Section 9 of the Basic Statement of Work.