01_FA880723R0005_Attachment 01 - SOW.pdf

FA8807-23-R-0005 ATTACHMENT 01 STATEMENT OF WORK Page 1 of 50

ATTACHMENT 01

FA880723R0005

STATEMENT OF WORK (SOW)

FOR

MOBILE USER OBJECTIVE SYSTEM (MUOS)

SERVICE LIFE EXTENSION (SLE)

Phase One

Risk Reduction and Early Design

24 MARCH 2023

Version 1.0

Prepared By:

United States Space Force

Space Systems Command (SSC) Acquisition Delta (CGN) Narrowband SATCOM

4301 Pacific Highway San Diego, California 92110-3127

FA8807-23-R-0005 ATTACHMENT 01 STATEMENT OF WORK Page 2 of 50

TABLE OF CONTENTS

1. SCOPE

1.1 Introduction and Purpose

1.2 Overview

2. APPLICABLE DOCUMENTS

3. REQUIREMENTS

3.1 Program Management

3.2 Space Vehicle Design (Space Transport Segment)

3.3 Systems Engineering

4. SECURITY REQUIREMENTS

4.1 Contractor Access to Classified Material

4.2 Covered Defense Information

5. WORK LOCATIONS

6. TRAVEL

7. FIXED PRICE OPTION

7.1 Option Period Management

7.2 Delta-EDR Design Maturity

7.3 Additional Design & Engineering

8. GOVERNMENT FURNISHED INFORMATION

8.1 Common Access Cards

8.2 Document Library

9. APPENDIX A: MISSION ASSURANCE APPLICABLE DOCUMENTS

10. APPENDIX B: DELIVERABLES

11. APPENDIX C: ENABLING CLAUSES

12. APPENDIX D: ACRONYMS

FA8807-23-R-0005 ATTACHMENT 01 STATEMENT OF WORK Page 3 of 50

1. SCOPE

1.1 Introduction and Purpose

The MUOS SLE satellite acquisition seeks to acquire replenishment satellites to extend worldwide Wideband Code Division Multiple Access (WCDMA) communication services into the mid-2030s.

SLE satellite acquisition is divided into two phases with separate contracts for each phase. This Phase 1 contract covers risk reduction and early design activities, forecasts, and execution plans.

The future Phase 2 contract will be competed just between the Phase 1 vendors and covers final design and production as well as launch, checkout, relocation, turnover to operations, and subsequent initial contractor support.

The overall objective of Phase 1 is to execute targeted risk reduction and design activities to reduce as much risk and uncertainty as possible prior to entering Phase 2. Phase 1 is further subdivided into two sections: A Base Period and an Option Period. Base Period deliverables may be used as part of Phase 2 scoping and source selection. The Phase 1 Option Period, if exercised, seeks to mitigate additional risks associated with transition to Phase 2. Note: Option Period tasks may run in parallel with Phase 2 source selection and therefore would not be used in that selection decision.

1.2 Overview

MUOS is an unprotected DoD narrowband SATCOM system that provides secure worldwide Ultra High Frequency (UHF) SATCOM to the warfighter. MUOS supports a worldwide, multi-service population of mobile and fixed-site terminal users. MUOS is comprised of a Space Segment and Ground Segment encompassing communications transport, satellite control, ground infrastructure, network management, and a waveform software application for user terminals.

The Space Segment includes a constellation of four satellites in geostationary orbit, plus one on-orbit spare. Baseline MUOS satellites support both WCDMA and Legacy UHF user terminals.

Please refer to the MUOS Introduction v1.2 “Green Book” for additional background information.

The MUOS SLE sub-program is only successful if the SLE satellites successfully integrate into the existing MUOS constellation, and the resulting system continues to meet or exceed system requirements. The Government will act as lead system integrator, however key system integration, verification, validation (IV&V) support will be required by the SLE satellite contract vendors. Once launched, each new MUOS SLE satellite will replace an existing Baseline MUOS satellite in the operational WCDMA constellation, thus retaining the same 4-ball WCDMA constellation. The first SLE replenishment satellite has a forecast operational need date prior to the end of FY2030. If still operational when replaced, Baseline MUOS satellites may continue operating their Legacy payloads.

2. APPLICABLE DOCUMENTS

All documents cited by reference within this SOW are contractually binding to the extent specified herein. Compliance document requirements “shall” be met. Reference documents indicate the expected scope and typical best practices; these “should” be factored into contract execution. In the event of a conflict between this SOW and the contents of the

FA8807-23-R-0005 ATTACHMENT 01 STATEMENT OF WORK Page 4 of 50 documents cited by reference within this SOW, the SOW shall prevail. Nothing in this SOW shall supersede applicable laws and regulations unless a specific exemption has been obtained.

The following documents, in Table 1, are designated as Compliance and Reference.

Applicable Mission Assurance (MA) documents are listed in Appendix A.

Table 1 – APPLICABLE DOCUMENTS

COMPLIANCE DOCUMENTS

Document Number/Ref Title Date

MUOS CGN-D-23-0025 SLE Satellite Specification 24 Feb

MUOS CGN-D-23-0027

SLE Satellite Specification Classified Annex for Resiliency and Survivability [TS//SI/TK//NF]

24 Feb

SMCI 62-109 SMC Configuration Management Process 24 May

ANSI/EIA GEIA-859 Rev B Data Management Standard Latest

AFI 16-401

Designing and Naming Defense Military Aerospace Vehicles

Latest

SSCI 64-101 Space Systems Command Instruction 64-101 March

APPLICABLE REFERENCES

Document Number/Ref Title Date

MUOS CGN-D-23-0023 Framing Assumptions ICD for STS-SCS WG 27 Feb

MUOS CGN-D-22-0092 Framing Assumptions ICD for STS-GTS WG 5 Dec

MUOS CGN-D-23-0020 Framing Assumptions for IV&V WG 23 Feb

ANSI/EIA

GEIA-HB-649

Rev A Technical Report Latest

DoD MIL-HDBK-61B Configuration Management Guidance 07 Apr

DoD MIL-STD-196G DoD Standard Practice for Joint Electronics Type Designation System Automated System

Latest

DoD MIL-DTL-15024G Plates and Tags for Identification of Equipment, General Specification for

Latest

DoD MIL-STD-1285D Department of Defense Standard Practice: marking of Electrical and Electronic Parts

Latest

DoD MIL-STD-13231 Department of Defense Standard Practice: Marking of Electronic Items

Latest

FA8807-23-R-0005 ATTACHMENT 01 STATEMENT OF WORK Page 5 of 50

JTR Regulation https://www.defensetravel.dod.mil/site/travelreg.cfm Latest

MUOS

Program

Protection Plan Rev C MUOS Program Protection Plan

01 Sep

MUOS

PMW-146-D-16-

MUOS Introduction v1.2 (aka Greenbook) 2017

DoD INST 4140.01 DoD Supply Chain Materiel Management Policy Latest

DFARS 252.204 series System Security Plans Latest

DoDM 5200.01 Vol 4 Controlled Unclassified Information Latest

DoDI 5230.24 Distribution Statements on Technical Documents Latest

MUOS

Security Guide

ID# 06-056.3 MUOS Security Classification Guide 3 Feb

DoDM 5000.04-M-1 Cost and Software Data Reporting (CSDR Manual) Latest

DoDI 4140.67 DoD Counterfeit Prevention Policy Latest

3. REQUIREMENTS

3.1 Program Management

3.1.1 Program Management Plan

3.1.1.1 The Contractor shall deliver and implement a Program Management Plan (PMP) that provides an overview and covers all aspects of program management for the MUOS SLE Space program from contract award through completion of risk reduction and early design. The PMP shall ensure adequate program resources are available to:

a) Execute the program on schedule

b) Staff the program with properly trained and qualified personnel

c) Provide appropriate facilities

3.1.1.2 The Contractor shall provide the necessary resources to plan, manage, direct, control, and report on all activities contributing to the MUOS SLE Space effort. The Contractor shall provide program management including business and administrative planning, organization, directing, coordinating, controlling, and approval actions, designed to accomplish the overall program objectives. The Contractor shall designate a program manager who is the single management interface with the Government and is specifically responsible for accomplishing all tasks set forth in this contract and for directing the efforts of all subcontractors.

Contract Data Requirements List (CDRL) A001: Program Management Plan

3.1.2 The Contractor shall provide status of cost, schedule, and performance as well as program technical progress, issues, and risks.

FA8807-23-R-0005 ATTACHMENT 01 STATEMENT OF WORK Page 6 of 50

CDRL A002: Status Report, Monthly Status Report

3.1.3 The Contractor shall develop and maintain a MUOS SLE Space Phase 1 Integrated Master Schedule (IMS) spanning contract award through completion. The Contractor shall actively manage the program in accordance with the IMS. The Contractor shall coordinate major changes to the schedule with the Government before implementation of the change in schedule.

CDRL A003: Status Report, Integrated Master Schedule

3.1.4 The Contractor shall develop and maintain a MUOS SLE Phase 1 and Phase 2 Summary Report. As the design matures with each milestone (i.e. System Readiness Review / System Functional Review (SRR/SFR), Early Design Review (EDR)) the level of detail provided shall increase. The EDR forecast shall include a detailed list of each long lead item priced by fiscal year quarter with specific risk-benefit justification for investment prior to completion of Critical Design Review (CDR) Q3FY2026.

CDRL A004: Status Report, Phase 1 and Phase 2 Summary Report

3.1.5 The Contractor shall establish a Risk Management Program, using Space and Missile

Systems Center (SMC) Tailoring SMC-T-005 Risk Management Supplement to IEEE-

15288.1 as guidance. The Risk Management Program shall include space vehicle subsystems, satellite control system interfaces, other ground system interfaces, and overall space vehicle level risks that:

a) Identifies all technical, program, cost, and schedule risks

b) Demonstrates how risks will be mitigated

c) Monitors, assesses, and reports the mitigation of these risks in a single repository with near-real time access via the Contractor’s Information Depository Environment

(IDE).

CDRL A005: Status Report, Risk Management Status Report

3.1.6 The Contractor shall conduct a Program Kick-Off Review either at the Contractor’s facility or via video teleconference no later than one month after contract award. The Program Kickoff Review shall present the plans documented in CDRLs A001, A003, and A005.

3.1.7 The Contractor shall conduct Program Management Reviews (PMRs) providing status and forecasts for program cost, schedule, and performance, and insight into program technical progress risks and issues. The PMR presentation materials shall support detailed discussions on Phase 1 and high-level discussions on Phase 2. The PMRs shall be combined with milestone reviews. The Contractor shall conduct PMRs either at the Contractor’s facility or via video teleconference. The PMRs shall present the status documented in CDRLs A002, A003, A004, and A005.

FA8807-23-R-0005 ATTACHMENT 01 STATEMENT OF WORK Page 7 of 50

3.1.8 Cost and Software Data Reporting (CSDR)

The Contractor shall collect, validate, and prepare CSDR for the major Contractor and subcontractor(s) for all elements of the Work Breakdown Structure (WBS) to the Program WBS within all CSDR CDRLs. The Contractor shall create and maintain a Contract Work Breakdown Structure (CWBS) and dictionary that will be mapped to the Program WBS within all CSDR CDRLs.

The Contractor shall provide the Government “estimate at complete” and “actual values at completion” for each Computer Software Configuration Item (CSCI) within the WBS.

The “estimate at complete” shall include a Phase 1 estimate at complete. The estimates and actuals shall contain data regarding the size, effort, schedule, and quality of software products. The Contractor shall comply with DoD Manual 5000.04 Cost and Software Data Reporting in compiling the required information.

The Contractor shall attend and participate in a CSDR Readiness Review meeting (also known as the Post award CSDR conference) which will be held with the Cost Working Group Integrated Product Team (CWIPT) IAW Defense Federal Acquisition Regulation Supplement (DFARS) 242.503-2(b) and DoDM 5000.04 (CSDR Manual). During this meeting, the CWIPT and Contractor will review the Contractor’s process for data collection and reporting to ensure it satisfies the guidelines outlined in the DoDM 5000.04, CSDR Manual, the approved CSDR plan reporting requirement, and the Resource Distribution Table. The Contractor shall demonstrate how costs will be based, to the maximum extent possible, upon actual cost transactions and not cost allocations;

describe how recurring vs. nonrecurring costs will be segregated; demonstrate how the data from its accounting system will be mapped into the reporting categories in the approved CSDR plan. The Contractor shall present the methodologies used for mapping internal cost accounts to the agreed upon WBS, specifically illustrating how individual WBS elements and standard functional categories in the FlexFile (functional data elements in the 1921 series) codes will be populated. The review shall include any reporting issue corrections and identify proposed changes to the approved CSDR Plan as necessary.

CDRL A006: Cost & Software Data Reporting CDRL A007: Quantity Data Report, CSDR CDRL A008: Cost and Hour Report (Flexfile), CSDR CDRL A009: Technical Data Report, CSDR CDRL A010: Contractor Business Data Report, CBDR

3.2 Space Vehicle Design (Space Transport Segment)

In support of the Systems Engineering Technical Review (SETR) events and deliverables described in 3.3.6, the Contractor shall conduct early design and risk reduction activities.

These include the following:

FA8807-23-R-0005 ATTACHMENT 01 STATEMENT OF WORK Page 8 of 50

3.2.1 The Contractor shall provide a System/Subsystem Design Description (SSDD) that describes the satellite and subsystem design of the MUOS SLE spacecraft, payload, subsystem(s), and software. The architecture products shall document traceability from the Government-provided requirements, architecture products and applicable Interface Control Documents (ICDs). The SSDD shall document System and Technical views that are fully traceable to and consistent with the requirements allocations involving the MUOS SLE satellite and applicable ICDs. The SSDD shall include rationale for the architecture design based on trade studies, modeling & simulation, and analytical work to meet or exceed the SLE Satellite specifications.

CDRL A100: Satellite System/Subsystem Design Description

3.2.2 The Contractor shall design/develop and specify the configuration items of the space segment, and satellite vendor aspects of satellite control, ground transport, cybersecurity and satellite test and training simulator as defined in the Government led working groups, modified ICD and performance specifications (including the Test and Training Simulator specifications).

3.2.3 The Contractor shall identify and describe mitigations for SLE risks that could impact ability to place MUOS-6 in service as near as possible to the end of FY2030, or impact ability to meet performance requirements. SLE risks shall include, at a minimum, UHF Passive Intermodulation (PIM) and high power radio frequency (RF) handling, and any previously un-flown and/or to be qualified flight hardware or software/firmware. The Contractors shall provide documentation (e.g., analysis, modelling/simulation, prototypes, qualification and/or flight hardware) demonstrating that early designs will meet or exceed SLE requirements with manageable risk. For early planning and consistency, the Contractor shall assume 6 months from the start of MUOS-6 on orbit checkout to operational handover to place MUOS-6 in service. Report as needed in CDRLs A002 and A005.

3.2.4 The Contractor shall provide a Technical Work Breakdown Structure (TWBS) and technology maturation plan (TMP) IAW A108. The TMP shall describe the Contractor’s plan to achieve a minimum of Technology Readiness Level (TRL) 7 no later than completion of Phase 2 CDR, for all Contractor identified critical technology elements

(CTE).

CDRL A108: Technical Work Breakdown Structure and Technology Maturation Plan, TWBS & TMP

3.2.5 The Contractor shall review the MA standards (Appendix A), guides, and instructions (hereafter generically referred to as “standards”) and provide a MA Tailoring Report describing the risks and benefits associated with the prescribed tailoring in Appendix A and any recommended Contractor unique tailoring or substitution to each standard. This is intended, at a high level, to improve the fidelity for Phase 2 forecasts. It is not intended to adjudicate every detail of every standard.

FA8807-23-R-0005 ATTACHMENT 01 STATEMENT OF WORK Page 9 of 50

3.2.5.1 The Contractor shall host a meeting, or series of meetings, to adjudicate Government disposition of requested tailoring. The Contractor shall document final agreements in a Final MA Tailoring Report.

CDRL A110: Mission Assurance Tailoring, MA Tailoring

3.2.5.2 Typical standards that may benefit from Contractor unique tailoring or near-equivalent corporate best practices include (but is not limited to):

a) AIAA-S-080A Metallic pressurized vessels

b) AIAA-S-081B Composite overwrapped pressurized vessels

c) SMC-S-005 Flight pressurized systems

d) MIL-STD-882E System Safety Program Requirements

e) SMC-S-016 Test Requirements for Launch, Upper-Stage & Space Vehicles

For example, mature spacecraft structures with test-correlated models may not require a modal survey.

f) AFSPCI 13-610 Launch, Range Operations

g) AFSPCMAN 92-710 Space Force Range Safety

h) TOR-2015-02546 RF Ionization Breakdown prevention

i) SMC-S-009 Parts & Material Control Program

j) SMC-S-008 Electromagnetic Compatibility Requirements for Space Equipment and

Systems

k) Program Protection, Cybersecurity system requirements and Risk Management

Framework (RMF) controls

3.3 Systems Engineering

3.3.1 Requirements Management

3.3.1.1 The Contractor shall implement a requirements management program for SLE Space

Vehicle specifications and related information. The Contractor shall use DOORS v9 or a mutually agreed-to alternative for requirements configuration management, hierarchical linking of requirements, and linking to the contract Satellite Specification. The Government will maintain the master program requirements database, and the Contractor shall work with the Government to establish a data standard that allows the Government to automatically link delivered artifacts.

3.3.1.2 The Contractor shall develop and deliver all specifications necessary for preliminary design of the SLE space vehicle as allocated from the SLE Satellite Specification and associated Classified Annex for Resiliency and Survivability [TS/SCI(SI/TK/NF)] to include, at a minimum, Subsystem Specifications and Unit Specifications, and Software Specifications. The Contractor shall demonstrate hierarchical traceability from the SLE Satellite Specification via the requirements management database.

CDRL A101: SLE Satellite Subsystem Specifications CDRL A102: SLE Satellite Unit Specifications CDRL A103: Software Requirements Specification

FA8807-23-R-0005 ATTACHMENT 01 STATEMENT OF WORK Page 10 of 50

3.3.1.3 The Contractor shall document and implement a Requirements Verification Program.

The Contractor’s requirement verification program shall include a review process to demonstrate compliance with each SLE Satellite Specification and associated Classified Annex for Resiliency and Survivability [TS/SCI(SI/TK/NF)] requirement. The Contractor shall deliver a Requirements Verification Matrix and associated rationale in conjunction with the Requirement Verification Program Plan. The Contractor shall document the Requirements Verification Matrix and a summary verification description for each Satellite-level requirement via the requirements management database.

CDRL A202: Requirements Verification Plan, RVP

3.3.2 Systems Engineering Management

3.3.2.1 The Contractor shall document their systems engineering processes and plans for both

Phase 1 and Phase 2 and deliver a Systems Engineering Management Plan (SEMP). The Contractor shall leverage digital engineering (DE) and model-based systems engineering (MBSE) principles to maximum extent practical for the SLE program.

3.3.2.2 The Contractor shall prepare plans for tracking, updating, reporting and corrective actions for Technical Performance Measures (TPMs) of the spacecraft. At a minimum, the Contractor shall track the Government prescribed TPMs as delineated in A107. The Contractor shall propose additional TPMs for parameters related to critical performance requirements, identified performance risks, drivers for key interfaces or critical resources.

CDRL A107: Systems Engineering Management Plan, SEMP

3.3.3 Segment Integration and Interfaces

The Government is the system integrator and the SLE Space Contractor has a critical role in defining changes to system interfaces, required changes to other segments. The Contractor shall participate in four Government-led Working Groups (WG). Two Interface Control WG described below, a third described in 3.3.3.2 and a fourth in section 3.3.6:

a) a WG for Satellite Transport Segment (STS) to Satellite Control Segment (SCS) and Satellite Control Network (SCN) interfaces and integration definition;

b) a WG for STS to Ground Transport Segment (GTS) interfaces and integration definition.

Each WG will be held at least once per month. WG participants include the Government, the Space Contractor, MUOS Ground Contractors, and other stakeholders as necessary. The Government will maintain an accessible library of minutes, actions, references and artifacts for each WG. The WG objectives include but are not limited to:

a) Determine Space and Ground Contractor scope and responsibilities for Phase 2.

b) Determine Government Furnished Equipment (GFE)/Government Furnished

Information (GFI) and Givers and Receivers (G/R) among the stakeholders in

FA8807-23-R-0005 ATTACHMENT 01 STATEMENT OF WORK Page 11 of 50 order to achieve system integration, verification and validation in all areas. G/R lists shall include detailed schedules and dependencies.

c) Determine the functional and physical interfaces necessary to create draft SLE ICDs: SLE STS-SCS, STS-SCN and SLE STS-GTS.

d) Document assumptions and agreements for use in Phase 2 planning and execution.

3.3.3.1 SLE ICDs

The Contractor shall deliver a Draft ICD, SLE STS-SCS and Draft ICD, STS-GTS IAW initial framing assumptions and subsequent WG collaboration.

CDRL A106A: Interface Control Document, STS-GTS CDRL A106B: Interface Control Document, STS-SCS

Note: The Government anticipates providing updated version of the framing assumptions and ICD references with additional details at time of Phase 1 award in preparation for first WG meetings.

3.3.3.2 System Integration, Verification and Validation and Planning

The Contractor shall participate in a Government-led IV&V working group to assist in planning events to reduce and retire system integration risk for SLE satellites and MUOS Ground systems and planning for ground and on-orbit system-level (end-to-end) verification and validation opportunities. Events may include integrated modeling and simulation, prototype testing, qualification or flight hardware testing, hardware in the loop testing, spacecraft sub-system and system level testing, satellite control testing.

The WG objectives include but are not limited to:

a. Determine Space and Ground contractor scope and responsibilities for Phase 2.

b. Determine GFE/GFI and G/R among the stakeholders in order to achieve system integration, verification and validation in all areas. G/R lists shall include detailed schedules and dependencies.

c. Determine end-to-end test event opportunities and schedules.

d. Document assumptions and agreements for use in Phase 2 planning and execution.

The deliverables for this activity may be incorporated into Working Group(s) Summary Reports, Risk Management Plans, and/or other Phase 1 deliverables.

Note: The Government anticipates providing IV&V WG Framing Assumptions with additional details at time of Phase 1 award in preparation for first IV&V WG meetings.

3.3.3.3 Working Group(s) Summary Report

The Contractor shall deliver a report, with a section for each of the four WGs, describing the Space Contractor’s roles and responsibilities for Phase 2. The report shall include a list of assumptions, anticipated data, documents, software, hardware, support, special

FA8807-23-R-0005 ATTACHMENT 01 STATEMENT OF WORK Page 12 of 50 test equipment, and resources IAW initial framing assumptions the Contractor plans to give or receive along with associated Phase 2 schedules.

CDRL A200: Technical Report, WG Summary Report

3.3.4 Modeling and Simulation

The Contractor shall develop and deliver payload models, tools, data, developer run-notes and shall assist the Government in integrating and running models.

3.3.4.1 The Contractor shall develop and deliver a MATLAB model of the digital processing in the Space Vehicle WCDMA Payload in the U2B direction.

3.3.4.2 The Contractor shall deliver input files with formats defined in the IV&V WG for 64 input channels as well as tools required to import data into a MATLAB model.

3.3.4.3 The Contractor shall develop and deliver an output file IAW STS-GTS WG ICD format that matches what will be transmitted down the Ka-Link.

3.3.4.4 The Contractor shall provide data validating the model for both input and output and any intermediate point as defined in the IV&V WG.

CDRL A201: Conceptual Design/Drawings/Models, Digital System Models

3.3.5 Systems Engineering Technical Reviews

The Contractor shall prepare and present two milestone SETR event Technical Review Presentation Packages (TRPP): a combined SRR/SFR and an EDR using IEEE 15288.2- 2014 as a guide. The Contractor shall leverage DE and MBSE tools and processes as practicable for package delivery and event conduct to enhance the value and efficiency of the events.

3.3.5.1 The Contractor shall conduct a combined SRR/SFR event no later than 4 months after contract award. The SRR/SFR shall focus on the contractor criteria that demonstrates risk reduction and program maturity to begin functional allocation and preliminary design. Of the standard IEEE 15288.2 SRR and SFR criteria, the aspects of the review in which the Government is most interested include:

a) Allocation and bi-directional tracing of SV requirements to SV subsystems and elements.

b) Preliminary verification methods and criteria for all requirements.

c) Preliminary definitions of SV interfaces with the SCS, GTS and SCN.

d) Preliminary plans and risks to integration with the SCS, GTS and overall system integration, verification, and validation.

e) Risks to SV design, manufacture, and test.

f) Preliminary demonstration that satellite payload functionality meets WCDMA transport requirements.

g) Cybersecurity considerations and trades, analysis, modeling/simulation, prototypes (Defense in Depth, Zero-Trust, etc.), certifications and documentation, necessary for cybersecurity Test and Evaluations, to demonstrate that early designs are on track to meet requirements for an Authority to Operate.

FA8807-23-R-0005 ATTACHMENT 01 STATEMENT OF WORK Page 13 of 50

h) Risk reduction activities (models and simulation, prototypes, analyses, trade studies, qualification and/or flight hardware) that demonstrates early designs will have high technology maturity and manageable schedule, integration and technical risk in Phase 2.

CDRL A109: Technical Review Presentation Package, TRPP

3.3.5.2 The Contractor shall conduct an EDR, no later than 11 months after contract award, which focuses on the aspects of a Preliminary Design Review (PDR) that are most critical to demonstrating that the Contractor has reduced cost, schedule, and technical risk to the SLE Space Program, has a complete and correct Allocated Baseline and is ready to begin detailed design. Note: the formal PDR will occur at the beginning of Phase 2 and will review progress and changes from execution of the Phase 1 Option Period as well as covering the remaining PDR criteria. In addition to the standard IEEE 15288.2 PDR criteria, the aspects of the review in which CGN is most interested include:

a) Demonstration that the SLE SV preliminary design is sufficiently mature and ready to proceed into detailed design and can meet the stated performance requirements.

b) SV interfaces and the givers/receivers with the Ground Contractor(s) to integrate, verify and validate the SV into the SCS and GTS segments.

c) System integration, verification, and validation approaches, both pre- and post-launch.

d) Cybersecurity considerations and trades, analysis, modeling/simulation, prototypes (Defense in Depth, Zero-Trust, etc.), certifications and documentation, necessary for cybersecurity Test and Evaluations, to demonstrate that early designs are on track to meet requirements for an Authority to Operate.

e) Risk reduction activities (models and simulation, prototypes, analyses, trade studies, qualification and/or flight hardware) that demonstrate early designs will have high technology maturity and manageable schedule, integration and technical risk in Phase 2.

CDRL A109: Technical Review Presentation Package, TRPP

3.3.6 Cybersecurity, System Security, and Program Planning

3.3.6.1 The Contractor shall provide Cybersecurity and System Security engineering early and continuously throughout the satellite development life cycle to reduce cost and schedule risk, ensure the system complies with applicable security requirements, and is able to obtain an Authority to Operate (ATO) and necessary security certifications in accordance with compliance references.

The Contractor shall participate in a Government led System Security Working Group (SSWG) which will be held at least once per month; SSWG participants include the Government, the Space Contractor, and other stakeholders as necessary. The Government will publish an accessible library of minutes, actions, references and artifacts. The Contractor will review minute and complete action items assigned.

FA8807-23-R-0005 ATTACHMENT 01 STATEMENT OF WORK Page 14 of 50

The SSWG objectives include but are not limited to:

a) Tailoring, as necessary, of cybersecurity, system security, and program protection compliance documents.

b) Clarification of cryptographic architectures and key management.

c) Determine scope of responsibilities regarding definition and implementation of RMF security controls and RMF verification plan.

d) Contractor scope of responsibilities regarding System Security Certification using

DoD Instruction 8510.01.

e) Identify and evaluate mitigations for security associated risks.

f) Identification of cyber and system security related analyses and plans required during

Phase 2 (e.g. Attack Plan Analysis, Covert Channel Analysis, Anti-Tamper Plan, Cybersecurity Design, Analysis and Assessment Plan).

g) Definition of cyber and system security related testing during Phase 2 (e.g.

penetration testing).

h) Coordination for command and telemetry design (includes telemetry bypass) IAW NSA requirements.

i) Assessments of compatible Ground ECUs (MYK-16B, MYK-17B, KG-255XJ) and Space ASICs/ECUs (Pegasus/Carousel ASICs, MCU-110C, KG-500, KG-501A, KG- 501B, KG-503, KG-505A) and/or other low risk alternatives for COMSEC and

TRANSEC.

j) Determine GFE/GFI and other G/R among the stakeholders in order to achieve necessary cybersecurity and cryptographic certifications. G/R lists shall include detailed schedules and dependencies.

k) Document assumptions and agreements for use in Phase 2 planning, costing, and execution.

l) Identify, evaluate, and provide trade considerations for approaches for a Defense Architecture, Zero-Trust Architecture, and the Contractors hybrid or proprietary security Architecture.

m) Participation in cybersecurity Test & Evaluation events and activities and/or full or modified Mission Based Risk Assessment Process for Cyber (MRAP-C) early and continuously throughout the satellite development life cycle to ensure the system complies with applicable security requirements and is able to obtain an ATO and necessary security certifications in accordance with references.

The Contractor shall deliver a summary report of the assumptions, agreements, anticipated GFI/GFE, resources the Contractor plans to give or receive along with associated Phase 2 schedules and other pertinent information from the SSWG.

CDRL A200: Technical Report, WG Summary Report

3.3.6.2 The Contractor shall develop, deliver, implement, and maintain a Program Protection program through the Program Protection Implementation Plan (PPIP) that is consistent with the Government’s Program Protection Plan (PPP), DFARS clauses, DD Form 254 and Security Classification Guides (SCGs). Program Protection includes, at a minimum, the following areas: CPI/CC Identification, Trusted Systems and Networks (TSN), Cyber

FA8807-23-R-0005 ATTACHMENT 01 STATEMENT OF WORK Page 15 of 50

Resiliency, Cyber security monitoring, Countering identified cyber threats, Anti-Tamper, Supply Chain Risk Management, and Information Protection.

CDRL A301: Program Protection Implementation Plan, PPIP

3.3.6.3 The Contractor shall develop a System Key Management Plan & Benign Fill Requirements in accordance with the Key Management/Benign Techniques Specification Revision.

CDRL A302: System Key Management Plan, SKMP

3.3.7 Configuration Management, Data Management, and Data Rights

3.3.7.1 Configuration Management

The Contractor shall implement the Configuration Management (CM) functions and principles IAW SMC Instruction SMCI 62-109 SMC Configuration Management (CM) Process, American National Standards Institute/Electronic Industries Alliance (ANSI/EIA)-649 Configuration Management Standard. The Contractor shall establish and maintain a CM Program that includes an organizational structure and CM process IAW tailored version of ANSI/EIA-649-1A Configuration Management Requirements For Defense Contracts. The Contractor shall establish CM procedures for internal and external coordination and approval. The Contractor shall flow-down requirements for configuration and data management to all subcontractors and vendors. Each Contractor/Subcontractor provided MUOS SLE configuration item and deliverable shall be under formal configuration control. Contractor shall use EIA-HB-649 Configuration Management Standard Implementation Guide and MIL-HDBK-61 Configuration Management Guidance as guidance.

The CM Program shall include but is not limited to:

a) Configuration Identification Process

b) Configuration Control Process

c) Configuration Control Board (CCB) responsibilities

d) Configuration Status Accounting (CSA) and Reports

e) Configuration Audit Process

f) Interface Control Process

g) Subcontractor CM

h) Subcontractor Engineering Document Control

3.3.7.1.1 Configuration Identification

The Contractor shall accomplish Configuration Identification on all Hardware Configuration Items (HWCIs), including Firmware, and CSCIs IAW the CM Plan and as specified herein. The Contractor shall assign:

a) Part numbers and Contractor and Government Entities (CAGE) Code for all Contractor delivered hardware and software items

b) Assign specification, document, and procedure numbers

c) Create specification tree and index

d) Create program master index

FA8807-23-R-0005 ATTACHMENT 01 STATEMENT OF WORK Page 16 of 50

The Contractor shall identify the spacecraft IAW AFI 16-401 Designing and Naming Defense Military Aerospace Vehicles. The Contractor shall issue Reference Designators using MIL-STD- 196G Department of Defense Standard Practice Joint Electronics Type Designation System Automated System as guidance. The Contractor shall install nameplates and markings using MIL-DTL-15024G Plates and Tags for Identification of Equipment, General Specification for as guidance. The Contractor shall identify all configuration items including their sets, groups, units, assemblies, subassemblies, parts or other items by marking IAW MIL-STD-130N Identification Marking of U.S. Military Property, MIL-STD-1285D Department of Defense Standard Practice:

Marking of Electrical and Electronic Parts; and/or MIL-STD-13231, Department of Defense Standard Practice: Marking Electronic Items as applicable.

The Contractor shall establish a Configuration Identification numbering schema, acceptance criteria, data management, technical baselines, and definition of interfaces as part of Configuration Identification activities to identify and track applicable major end items, configuration-controlled items, and Government Furnished Property (GFP), and that Item Unique Identification (IUIDs) are integrated in configuration and documentation management.

The product structure is documented to include the identifiers, internal structure, and relationship of system components, associated configuration documentation, and is the result of functional analysis and the allocation process of system engineering; this may be depicted as an indentured listing or graphic.

3.3.7.1.2 Configuration Baselines

The Contractor shall establish the Allocated Baseline (ABL), no later than seven days after the completion of the EDR and shall control baseline changes through formal processes. The Contractor shall provide the Government the right to access, or delivery of data that the Government requires for systems sustainment. The Contractor shall develop and submit for approval a Baseline Description Document (BDD).

CDRL A011: Baseline Description Document, BDD

3.3.7.1.3 Configuration Control

The Contractor shall implement a process of change approval authority within the Integrated Product Team (IPT) environment that allows for change authority at the lowest practical level for changes that do not affect the contract requirements. The Contractor shall also implement a normal progression of approval authority up through the Government for changes that do affect contract requirements.

Once the Contractor has established a configuration baseline, the Contractor shall exercise configuration control authority over that baseline. During the time that the Contractor has configuration control authority, authority for the disposition of Class I and Class II Engineering Change Proposal (ECP) will remain with the Contractor. The Contractor shall notify the MUOS Program Office of all CCB decisions.

The Contractor shall process, track, and status all change requests. The Contractor shall maintain and update all documentation to reflect accurately the configuration baselines. The Contractor shall update the Baseline Description Document and submit for approval.

FA8807-23-R-0005 ATTACHMENT 01 STATEMENT OF WORK Page 17 of 50

3.3.7.1.4 Data Management

The Contractor shall establish, implement, and maintain Data Management (DM) Program IAW ANSI-EIA-859 Data Management to:

a) Capture and control the technical baseline (configuration documentation, technical data, and technical manuals).

b) Provide data correlation and traceability among performance requirements, designs, decisions, rationale, and other related program planning and reporting elements.

c) Support configuration procedures.

d) Serve as a ready reference for the systems engineering effort.

The Contractor shall establish formal data configuration management to ensure the integrity of digital data and enhanced data management by providing:

a) Effective file and database management.

b) Unique identification of documents, files and document representations.

c) Retention of essential file and version relationships.

d) Known data status.

e) Controlled access to digital data.

The Contractor shall implement a data management process that includes all tasks for documenting and maintaining the data throughout the program life cycle. The process shall also include all efforts required to prepare, manage, and deliver all information, documentation, and data required for CDRL delivery electronically. The Contractor shall deliver all unclassified data required that is listed in the CDRL, DD Form 1423, to the Government via TopVue application.

The Contractor shall deliver all classified data for required CDRLs as a separate CDRL appendix in accordance with the DD254 and SCG.

The Contractor shall establish and maintain a cost-effective data management system and appropriate/secure digital environment(s) for hosting all technical data and computer software produced in the performance of this contract. The Contractor shall provide continuous electronic access to its IDE and allow all activities involved with the program to exchange data digitally and to download artifacts. The IDE shall be documented as part of the DM Plan and shall be available within 30 days of contract award.

Contractor shall develop and submit for review and approval a Contractor’s Data Management Plan (CDMP) which includes IDE, identification, control, libraries, status accounting, audits, and data rights.

CDRL A012: Contractor Data Management Plan, CDMP

Contractor shall develop and submit a Data Accession List (DAL). The Contractor shall provide the Government MUOS Program Office team access to and the ability to download all data listed in the DAL. The delivery requirements for CDRL A013: Data Accession List, DAL are detailed in the DD-1423.

CDRL A013: Data Accession List, DAL

FA8807-23-R-0005 ATTACHMENT 01 STATEMENT OF WORK Page 18 of 50

Unless otherwise approved by the Government (e.g., to accommodate MBSE/DE collaboration), the Contractor shall use MS Office 2016 compatible (MS Word 2016, MS Excel 2016, MS Paint 11.2, and MS PowerPoint 2016), and MS Project 2016 compatible applications for the preparation of documents that are to be electronically transferred to the Government. All deliverables shall be delivered in the original electronic format. Adobe Acrobat formatted files are acceptable for documents such as test reports that require original documents to be scanned.

The Contractor shall ensure that the deliverable data product can be recreated in human readable form and processed by the user.

When required, the Contractor shall provide data on physical media, such as CD/DVD, with appropriate identification to identify its contents clearly. When it is impracticable to include all file identifications, the Contractor shall provide a reference to an accompanying listing or to a read me file.

4. SECURITY REQUIREMENTS

4.1 Contractor Access to Classified Material

4.1.1 Requirements of this SOW will be met at the UNCLASSIFIED, SECRET, and TOP

SECRET Special Compartmentalized Information (TS/SCI(SI/TK/NF)) levels and IAW the DD254 and MUOS SCG.

4.1.2 The Contractor shall perform classified work at existing Government facilities and/or Contractor facilities, using existing computer networks and terminals on a not to interfere basis. To the maximum extent possible, the contractor shall use existing facilities and equipment to meet all security and data handling requirements. The Contractor shall assist the Government to pursue Cooperative Use Agreements if needed with other Government customers. If additional, unique, dedicated networks and equipment are required, the Government will facilitate providing the minimum additional infrastructure required to meet the objectives of the contract.

4.2 Covered Defense Information

4.2.1 Covered Defense Information (CDI) Identification and Marking

Contractor(s) and the Government/Program Office shall identify and affirm marking requirements for all covered defense information, as prescribed by DoDM 5200.01 Vol 4, Controlled Unclassified Information, and DoDI 5230.24, Distribution Statements on Technical Documents, to be provided to the Contractor, and/or to be developed by the Contractor, associated with the execution and performance of this contract.

4.2.2 CDI Record of Tier 1 Level Subcontractors, Vendors, and/or Suppliers The Contractor shall document, maintain, and provide to the Government, a record of Tier 1 Level Subcontractors, vendors, and/or suppliers who will receive or develop CDI

– as defined in DFARS Clause 252.204-7012 and associated with the execution and performance of this contract.

4.2.3 CDI Sharing and Flow Down

The Contractor shall restrict unnecessary sharing and/or flow down of CDI – as defined in DFARS Clause 252.204-7012 and associated with the execution and performance of this contract – IAW marking and dissemination requirements specified in the contract and based on a ‘need-to-know’ to execute and perform the requirements of this contract.

FA8807-23-R-0005 ATTACHMENT 01 STATEMENT OF WORK Page 19 of 50

4.2.4 CDI Record of Tier 1 Level Subcontractors, Vendors, and/or Suppliers The Contractor shall flow down the requirements in 4.2.1, 4.2.2, and 4.2.3 to their Tier 1 Level Subcontractors, vendors, and/or suppliers.

5. WORK LOCATIONS

Work will primarily be performed at vendor facilities. Additionally, by direction of the Government, the following facilities may be available:

a) SSC Offices, LA-AFB, Los Angeles, California

b) SSC/CGN Offices and Government Labs, San Diego, California

c) General Dynamics, Scottsdale, Arizona

d) 10-SOPS, Pt. Mugu, Naval Air Systems Command, Port Hueneme, California

6. TRAVEL

The Government does not anticipate any travel requirements. However, if travel is necessary it shall be IAW the Joint Travel Regulations, and local policy. During performance, the Contractor shall coordinate travel and facility clearances with the Contracting Officers Representative (COR).

7. FIXED PRICE OPTION

Upon exercise of an option by the Government, if ordered, the Contractor shall perform the following Phase 1 delta-design tasks. The objective of these tasks is not to inform Phase 2 source selection, but rather to continue targeted design and risk reduction activities necessary to rapidly transition into Phase 2 execution, if selected.

7.1 Option Period Management

7.1.1 The Contractor shall continue to deliver the following periodic CDRLs referenced in

Section 3.1 with the same periodicity.

CDRL B002: Status Report, Monthly Status Report CDRL B003: Status Report, Integrated Master Schedule CDRL B005: Risk Management Status Report

7.1.2 The Contractor shall continue the CSDR reporting, as required, to deliver the following reports with applicable periodicity upon exercise of option.

CDRL B006: Cost & Software Data Report, (SRDR) CDRL B007: Quantity Data Report, CSDR CDRL B008: Cost and Hour Report (Flexfile), CSDR CDRL B009: Technical Data Report, CSDR CDRL B010: Contractor Business Data Report, CBDR

7.2 Delta-EDR Design Maturity

7.2.1 The Contractor shall deliver updated versions of the following Phase 1 base period

CDRLs, in preparation for the possibility of Phase 2 selection, such that the cost, schedule, and technical risks to execute Phase 2 should be minimized.

FA8807-23-R-0005 ATTACHMENT 01 STATEMENT OF WORK Page 20 of 50

CDRL B011: Baseline Description Document, BDD CDRL B013: Data Accession List, DAL CDRL B100: Satellite System/Subsystem Design Description CDRL B107: System Engineering Management Plan, SEMP

7.2.2 The Contractor shall aid in further development and integration of functional digital payload models and other models sufficient to integrate into Ground or System based end-to-end digital threads.

CDRL B201: Conceptual Design/Drawings/Models, Digital System Models

7.3 Additional Design & Engineering

7.3.1 Spectrum Supportability

In order to support Government in updating frequency filings and certifications, the Contractor shall provide technical spectrum data for the MUOS SLE satellites.

CDRL B120: Spectrum Supportability Data

7.3.2 Assembly Integration & Test Plan

The Contractor shall deliver a preliminary SV Assembly, Integration and Test (AI&T) Plan for the build of the MUOS SLE space vehicles detailing the process, order, and facilities in which parts, components, units, subsystems, and space vehicle shall be fabricated, assembled, integrated, and tested.

CDRL B121: Technical Report – Study/Services, AI&T Plan

7.3.3 Parts, Materials, and Processes Plan

The Contractor shall prepare and submit a Parts, Materials, and Processes Plan IAW SMC-S-009 and SMC-S-010. This plan shall define approaches to ensure successful flight hardware production for Phase 2. The plan shall define and maintain processes to provide protections against procurement of counterfeit parts and materials, as described in the PPIP delivered under CDRL A301. This plan shall be accessible on the IDE and reported on the DAL.

CDRL B122: Parts, Materials, and Processes Control Plan

7.3.4 Quality Assurance & Product Assurance

The Contractor shall prepare, submit, and execute a Quality Assurance and Product Assurance Plan (QA/PA) that is consistent with the requirements of AS 9100 (Latest Revision) and SMC-T-009 in order to maintain AS 9100 certification status throughout Phase 2 production. The plan shall describe how the contractor will be conducting their Quality Program beginning in Phase 1 and continuing throughout Phase 2 production.

The Contractor shall maintain supplier and subcontractor quality records and make them available to the Government for review upon request. Quality records shall include, but are not limited to, certification/recertification records, audits, source inspections, sampling records, quality tracking metrics and material review board records. Quality

FA8807-23-R-0005 ATTACHMENT 01 STATEMENT OF WORK Page 21 of 50 reports (if needed) shall be delivered as CDRL and accessible on the IDE and reported on the DAL.

CDRL B123: Quality Program Plan

7.3.5 Software Development Plan

The Contractor shall provide a Software Development Plan (SDP) that describes the plans for conducting the software development effort of the program and shall be accessible on the IDE and reported on the DAL. The term software development is meant to include new development, modification, reuse, the approach to be followed for each activity and project schedules, organization, and resources. The software development environment shall be consistent with the PPIP delivered under A301. The SDP shall be an integrated plan covering the software development activities for all significant software team members as defined in SMCS-012.

CDRL B124: Software Development Plan

7.3.6 Failure Modes, Effects & Criticality Analysis

The Contractor shall develop and provide Failure Modes, Effects and Criticality Analyses (FMECAs) and reliability allocations. The FMECA shall be accessible on the IDE and reported on the DAL.

CDRL…