Attachment 1 Statement of Work (SOW).pdf

Acquisition Delta, Innovation and Prototyping Space Test Program (STP)

Space Test Experiments Platform 2.0 (STEP 2.0)

Attachment 1 Statement of Work (SOW)

RFP: FA8809-24R-B001

Version 1 Space Systems Command

Acquisition Delta, Innovation and Prototyping DoD Space Test Program

(SSC/SZIS)

Kirtland Air Force Base Albuquerque, NM 87117

STEP 2.0 IDIQ

Attachment 1 Statement of Work (SOW) FA8809-24-R-B001 ii

Acquisition Delta, Innovation and Prototyping Space Test Program (STP)

Space Test Experiment Platform 2.0 (STEP 2.0)

SUBMITTED BY:

DAVID J LORE, Maj, USSF Date Signed Program Manager, STEP 2.0

APPROVED BY:

BRIAN A SHIMEK, Lt Colonel, USSF Date Signed Director, DoD Space Test Program iii

Change History

Version Effective Date Prepared by Changes

1.0 10 May 2024 Maj LORE, DoD STP Document Creation

TABLE OF CONTENTS

1. INTRODUCTION

1.1 Purpose

1.2 Department of Defense (DoD) Space Test Program (STP) Background

2. STEP 2.0 SCOPE

3. PERIOD OF PERFORMANCE

4. CONTRACT MANAGEMENT

4.1 STP Contract Management

4.2 Associate Contractor Agreements and Non-Disclosure Agreements

4.2.1 Associate Contractor Agreements

4.2.2 Non-Disclosure Agreement

4.2.3 Contractor Responsibility Watch List

4.2.4 Federally Funded Research and Development Centers

4.2.5 International Traffic in Arms Regulations (ITAR)

5. DOCUMENTS NOTES

5.1 Key Definitions

5.2 Applicable, Compliance and Regulatory Documents

5.2.1 Applicable Documents

5.2.2 Compliance and Regulatory Documents

5.2.3 Deliverables

6. PROGRAM MANAGEMENT

6.1 Program Management

6.2 Working Groups and Meeting Support

6.2.1 Kick-Off Meetings

6.2.2 Management Integrated Product Team Meeting

6.2.3 Quarterly Management Meeting

6.2.4 Reserved

6.2.5 SV and Ground Operations Working Group

6.2.6 Technical Interchange Meeting

6.2.7 Configuration Change Meeting

6.2.8 Failure Review Board Meetings

6.2.9 LV Integration Meetings

6.2.10 Periodic Technical Interchange Meeting – Launch Campaign

6.2.11 Payload On-Orbit Operations Working Group Meetings

6.2.12 SC-to-PL Integration Working Group Meetings

6.3 General Contracting Requirements

6.3.1 Funds and Labor Hour Report

6.3.2 Cost and Software Data Reporting

6.3.3 Contracts and Subcontracts Management

6.4 Program Management Plan and Integrated Master Schedule

6.4.1 Key Events and Milestones

6.5 Contractor Integrated Performance Management

6.6 Government Property

6.6.1 Government Furnished Property

6.7 System Safety

6.8 Government Visiting Team Support

7. GENERAL ENGINEERING REQUIREMENTS

7.1 Systems Engineering

7.2 System Engineering Processes and Plans

7.2.1 Systems Engineering Management Plan

7.2.2 Configuration Management Process and Plan

7.2.3 Risk Management Plan

7.2.4 Software Configuration Management Plan

7.2.5 Parts, Materials and Processes

7.2.6 Contamination and Environmental Controls

7.2.7 Quality Assurance

7.2.8 Electromagnetic Interference and Electromagnetic Compatibility Design Practices and

Control

7.3 Reserved

7.4 Model Based System Engineering

7.5 Specialty Engineering

7.6 Reliability

7.7 Spectrum

7.8 Requirements Verification Matrix

7.9 Hardware and System Configuration Identification

7.10 Special Studies

8. SPACECRAFT REQUIREMENTS

8.1 Spacecraft and Ground Technical Specifications Sheet

8.2 Spacecraft Subsystems

8.2.1 Mechanical Subsystem

8.2.2 Avionics

8.2.3 Guidance, Navigation and Control

8.2.4 Electrical Power Subsystem

8.2.5 Communications Subsystem

8.2.6 Thermal Control Subsystem

8.2.7 Flight Software

8.2.8 Harness

8.3 SC Integration

8.3.1 Component Testing

8.3.2 SC Assembly, Integration and Test

8.4 Cryptographic Equipment Integration

9. PAYLOAD INTERFACE REQUIREMENTS

9.1 Payload Accommodation

9.1.1 Payload User’s Guide

9.1.2 Payload Accommodation Design Review

9.2 Spacecraft-to-Payload ICD

9.3 Classified Payloads

9.4 Mechanical Interface Hardware

9.5 Thermal Control Subsystem

9.6 Electrical Interface Hardware

9.7 Payload Integration

9.8 Oversight and Interface Verification

9.9 Simulator or Engineering Model

9.10 Payload Integration Readiness Review

10. SPACE VEHICLE REQUIREMENTS

10.1 SV Models

10.1.1 Finite Element Model

10.1.2 CAD Model

10.1.3 Thermal Model

10.2 Mass Properties

10.3 Electrical and Mechanical Drawings/Schematics and Specifications

10.4 Integration and Test

10.4.1 SV Test Readiness Review

10.4.2 SV Assembly, Integration, and Test

10.4.3 Environmental Test Requirements

10.4.4 Week in the Life Testing

10.4.5 Radio Frequency and Ground Segment Compatibility Testing

10.5 Ground Support Equipment

10.6 Pre-Ship Review

11. STORAGE

12. TRANSPORTATION AND HANDLING

13. LAUNCH INTEGRATION REQUIREMENTS

13.1 SV-to-LV ICD

13.2 Launch Range Requirement Inputs

13.3 Launch Vehicle Interface and Interface Management

13.4 Mechanical Interface

13.4.1 LV Fit Checks

13.4.2 Separation System

13.4.3 SV Mass Model

13.5 Electrical Interface

13.5.1 Charging and Monitoring Harness

13.6 Miscellaneous Hardware

13.7 Miscellaneous Support

13.8 Launch Site Activities

13.8.1 SV to LV Integration

13.8.2 Post-Integration Support and Battery Charge

13.9 Environmental Impact Analysis Inputs

13.10 Mission Readiness Review

14. PAYLOAD GROUND/MISSION OPERATIONS

14.1 Ground Segment

14.1.1 Ground Segment Architecture

14.1.2 SV-to-Ground ICD

14.1.3 PL-to-Ground ICD

14.1.4 Ground Segment Readiness Review

14.1.5 Ground Segment Verification Testing

14.1.6 Ground Segment Certifications and Accreditations

14.1.7 Ground Segment Cryptographic Equipment

14.2 Operations and Mission Execution

14.2.1 Concept of Operations

14.2.2 Training

14.2.3 Launch and Early Orbit Phase

14.2.4 SV On-Orbit Operations

15. SECURITY AND COMMUNICATIONS SECURITY REQUIREMENTS

15.1 Facilities and Security

15.2 Cryptographic Security Plan

15.3 COMSEC Key Management Plan

15.4 Cyber Security

APPENDIX A – DEFINITIONS

APPENDIX B – SUPPLEMENTAL ACQUISITION GUIDANCE

TABLE OF TABLES

TABLE 1 KEY DEFINITIONS

TABLE 2 MEETINGS AND REVIEWS

TABLE 3 STEP 2.0 KEY EVENTS AND MILESTONES

1. INTRODUCTION

1.1 Purpose

The purpose of this document is to define the contract requirements that must be met and tasks that must be accomplished to satisfy the Department of Defense (DoD) Space Test Program (STP) for space vehicles procured under the STP Space Test Experiments Platform 2.0 (STEP 2.0) Indefinite Delivery/Indefinite Quantity (IDIQ) contract. The STEP 2.0 IDIQ contract intends to provide STP rapid access to space for science and technology payloads on space vehicles ranging in sizes from 6U CubeSat to Multi-Manifest Design Specification Rev 1.0A Class 2 Space Vehicle (SV) for either low Earth or geosynchronous orbit.

STEP 2.0 program is the STP contract vehicle for a multiple award IDIQ contract with separate Delivery Orders (DOs) to procure proven spacecraft (SC) and space access for Science and Technology (S&T) experiments. The STEP 2.0 IDIQ contract vehicle provides STP the ability to execute contract DO(s) aligning payload(s) (PL) access to space, SV, and launch vehicle (LV) schedules.

At the IDIQ level, all pool participants must possess the capability to produce a Space Vehicle with payload integration and delivery not to exceed 24 months on any subsequent delivery order.

Delivery periods for Space Vehicles on Delivery Orders (DOs) may not exceed 24 months as enumerated at the IDIQ level. Moreover, the delivery period for each subsequent Delivery Order is dependent upon payload delivery specifications.

This Statement of Work (SOW) delineates Space Vehicle Contractor (SVC) responsibilities in support of the STEP 2.0 IDIQ contract. The requiring organization is the DoD STP, Space System Command (SSC) / Acquisition Delta, Innovation and Prototyping (SZIS), and any of its mission partners. This STEP 2.0 IDIQ may also be utilized by other government organizations to procure SC and PL integration services.

The information provided in the IDIQ SOW combined with the IDIQ System Requirements Document (SRD), DO SRD, DO Payload Requirements Document (PLRD), and DO SOW serves as the foundation of each STEP 2.0 mission.

1.2 Department of Defense (DoD) Space Test Program (STP) Background

DoD STP is a multi-service program supporting Army, Navy, Air Force, and Space Force space experimentation missions. DoD STP provides space access for S&T experiments throughout the DoD. S&T experiments are provided by the DoD Laboratories, (e.g., Air Force Research Lab (AFRL) and Naval Research Laboratory (NRL)) and any experimenter that has a DoD sponsor (e.g., universities, interagency cooperation, and international partners).

S&T is the backbone of emerging technologies therefore space experimentation is critical to continued Space Superiority support to the DoD Space Experiments Review Board (SERB) and International Space Access Review Board (ISARB). DoD STP currently has limited in-house capability to procure and launch spacecraft with S&T payloads (PLs).

2. STEP 2.0 SCOPE

The scope of work covered by this STEP 2.0 IDIQ SOW includes all hardware (HW), software (SW), firmware, data, services, labor, facilities, equipment, materials, and documentation needed to design, develop, produce, assemble, integrate, test, store, and deliver the integrated STP space vehicle. It includes technical support necessary to complete launch preparation, pre-launch readiness, launch operations, on-orbit initialization, on-orbit testing/checkout, payload activation, and on-orbit operations support including delivery of data to STP’s PL customers and end-of-life disposal or transition to another end user. The STEP 2.0 IDIQ contract also includes technical support needed to investigate and resolve on-orbit anomalies and to perform on-orbit SC performance trending analysis. The classification of many of the missions is expected to be Unclassified or Controlled Unclassified Information (CUI), with some mission(s) at higher classification level(s).

3. PERIOD OF PERFORMANCE

The STEP 2.0 IDIQ contract is a 5-year contracting vehicle with an additional 5-year option period, if exercised. The Government will define mission specific period of performance for each DO.

4. CONTRACT MANAGEMENT

4.1 STP Contract Management

The Government will assign a Contracting Officer's Representative (COR). The COR will act as the primary interface with the SVC and provide contract surveillance (i.e., quality assurance) in accordance with STEP 2.0’s Quality Assurance Surveillance Plan (QASP), on behalf of the Procuring Contracting Officer (PCO). Only the PCO and any/all appropriately designated COR may provide direction under this contract. The COR will assess the contractor’s conformance to each supply delivered and make a final recommendation to the PCO. Performance will be evaluated in accordance with Federal Acquisition Regulation (FAR) 52.246-2, FAR 52.246-3, FAR 52.246-7 and

FAR 52.246-8.

The Government will also assign a Mission Manager (MM) for each DO. The MM will be responsible for leading a multi-disciplined Integrated Product Team (IPT) to identify, coordinate, and manage the full breadth of mission planning and activities required to deliver payloads successfully to orbit.

4.2 Associate Contractor Agreements and Non-Disclosure Agreements

4.2.1 Associate Contractor Agreements

The SVC shall be capable of entering into Associate Contractor Agreements (ACA) for any portion of the contract requiring joint participation in the accomplishment of the Government’s requirement(s).

The SVC shall ensure the ACAs include the basis for sharing information, data, technical knowledge, expertise, and/or resources essential to the conduct of the mission.

The SVC shall ensure the greatest degree of cooperation between associate contractors for the successful completion of each DO to meet the terms of the contract.

Associate contractors will be provided to the SVC in each DO SOW.

ACAs should include the following general information:

• Identify the associate contractors and their relationships.

• Identify the program involved and the relevant Government contracts of the associate contractors.

• Describe the associate contractor interfaces by general subject matter.

• Specify the categories of information to be exchanged or support to be provided.

• Include the ACA expiration date (or event).

• Identify potential conflicts between relevant Government contracts and the ACA; include agreements on protection of proprietary data and restrictions on employees.

The SVC shall provide a copy of such agreements to the PCO for review before execution of the document by the cooperating contractors.

The SVC is not relieved of any contract requirements or entitled to any adjustments to the contract terms because of a failure to resolve a disagreement with an associate contractor. Liability for the improper disclosure of any proprietary data contained in or referenced by any agreement shall rest with the parties to the agreement, and not the Government. All costs associated with the agreements are included in the negotiated costs / prices of applicable orders issued under this contract. The Government will notify the SVC when the associate contractor is succeeded by a new contractor and requires an update to the ACA.

4.2.2 Non-Disclosure Agreement

The SVC shall establish Non-Disclosure Agreements (NDA) with other contractors performing related services for the Government such as STP’s PL sponsoring organizations, Non-Government advisors responsible for review and analysis on behalf of the DoD STP including Federally Funded Research and Development Centers (FFRDCs), and Systems Engineering and Technical Assistance (SETA) support contractors. The SVC shall comply with current NDA requirements on existing contracts as appropriate.

4.2.3 Contractor Responsibility Watch List

Space Systems Command (SSC) Instruction (SSCI) 64-101, Space Contractor Responsibility Watch List (CRWL), applies to this contract. Accordingly, if at any time during the performance of this contract the contractor is placed on the CRWL, before executing a modification resulting from an engineering change proposal or exercising an option on this contract, the Contracting Officer must determine whether to recommend proceeding with the modification or option exercise and if so, obtain approval to proceed from the SSC Commander. To support the Contracting Officer’s determination on whether to proceed with the modification or option, the contractor must submit documentation describing how it has addressed the conditions that resulted in its inclusion on the CRWL and why those conditions will not impact performance on this contract. The Contracting Officer will consider this information as well as other available information in making a determination.

In addition, in accordance with either FAR clause 52.212-4 (if commercial) or the SSC Class Deviation of FAR clause 52.244-2, Subcontracts (if non-commercial) in this contract, the contractor must receive written consent of the Contracting Officer prior to subcontracting with any proposed subcontractor included on the CRWL when the subcontract is valued in excess of $3M or 5% of the prime contract value, whichever is lesser. Before providing this consent, the Contracting Officer must determine whether to recommend granting consent and if so, obtain approval to proceed from the SSC Commander. For subcontracts subject to CRWL requirements, prime contractors must inform their proposed subcontractors that they must notify the prime contractor if they have been notified by the SSC Commander that they have been included on the CRWL. The prime contractor must submit a written consent to subcontract request to the Contracting Officer, the prime contractor’s determination of subcontractor responsibility in accordance with FAR 9.104-4(a), and documentation describing how the proposed subcontractor has addressed the conditions that resulted in its inclusion on the CRWL and why those conditions will not impact its performance on a subcontract to this contract.

The proposed subcontractor may submit information related to its CRWL inclusion through the prime contractor or directly to the Contracting Officer. The Contracting Officer will consider information provided by the prime contractor and the proposed subcontractor as well as other available information in making a determination. The contractor is encouraged to inform the Contracting Officer of any subcontractor concerns or issues that may jeopardize successful contract performance.

4.2.4 Federally Funded Research and Development Centers

Appendix B of this SOW incorporates supplemental acquisition guidance for Enabling Requirements for SSC Program Contracts Requiring Interface with Aerospace FFRDC Contract Support.

4.2.5 International Traffic in Arms Regulations (ITAR)

In the event a foreign PL is included in a specific DO under this contract, contractors should be prepared to comply with U.S. Export Control guidelines as stipulated under 22 CFR Chapter 1, Subchapter M, Parts 120-130, and seek appropriate export licensing as required.

5. DOCUMENTS NOTES

5.1 Key Definitions

The words “may”, “shall”, “will”, “spacecraft”, “space vehicle”, and “space vehicle contractor” have explicit meaning in this document. The definitions of these words as they apply to this document are listed here in Table 1 and in Appendix A Definitions:

Term Definition Shall Denotes a requirement that must be implemented, and the implementation is subject to verification by one or more contractually defined method(s) that gives rise to an auditable product (analysis, test report, etc.) that is contractually deliverable and managed as part of the product baseline.

Will Denotes a requirement that must be implemented, but the implementation is not subject to verification.

Should Denotes a requirement that is recommended.

May Denotes a non-mandatory condition, outcome, or course of action, which is deemed within allowable specification limits.

Payload (PL) An instrument that provides mission utility to an end user which is hosted on a spacecraft.

Spacecraft (SC) Refers to the satellite bus without payloads.

Space Vehicle (SV) Refers to the SC plus the integrated payloads. The integrated satellite.

Space Vehicle Contractor (SVC) Refers to the STEP 2.0 awardee(s).

TABLE 1 KEY DEFINITIONS

5.2 Applicable, Compliance and Regulatory Documents

Contract Data Requirements List (CDRL)s, Compliance and Regulatory Documents will be tailored for each DO award.

5.2.1 Applicable Documents

The SVC shall meet the requirements of the following documents in the order of precedence:

1. STEP 2.0 Delivery Order (DO) Statement of Work (SOW)

2. STEP 2.0 Delivery Order (DO) Systems Requirements Document (SRD)

3. STEP 2.0 Delivery Order (DO) Payload Requirements Document (PLRD)

4. STEP 2.0 Indefinite Delivery Indefinite Quantity (IDIQ) Statement of Work (SOW)

5. STEP 2.0 Indefinite Delivery Indefinite Quantity (IDIQ) Systems Requirements Document

(SRD)

5.2.2 Compliance and Regulatory Documents

The SVC shall comply with the documents listed in Appendix C that apply directly to the performance required and contain provisions that constitute requirements of STEP 2.0 SOW and IDIQ SRD to the degree specified in each section of this document. All mission specific applicable documents, including, but not limited to, those listed in Appendix C, will be specified on each DO.

Tailoring of compliance documents might be executed within each DO. The SVC may submit proposed tailoring for Government approval. Unless the government has approved specific tailoring for a given document, the SVC shall comply with the document in its entirety. In the event of a conflict in requirements, compliance documents take precedence over reference and guidance documents.

5.2.3 Deliverables

The SVC shall provide all deliverables in the specified format and deliver electronically. The SVC shall reference the SF 1423s to identify specific delivery dates, formatting, and data to deliver to the Government. Deliverables, included in the IDIQ but not limited to those in the IDIQ SOW, might be tailored for each DO.

6. PROGRAM MANAGEMENT

6.1 Program Management

The SVC shall provide a Program Manager (PM) who shall act as the primary liaison between the SVC and the Government. The SVC shall provide the program management necessary to ensure the DO program objectives are meeting cost, schedule, and performance requirements. The SVC shall provide cost control, schedule control, subcontract management, financial analysis, tracking, forecasts, planning and reporting for the program. The SVC shall support program related travel as required.

6.2 Working Groups and Meeting Support

The SVC shall participate and/or organize working groups and meetings as directed by the government team. Only contractors with active SV DOs are responsible for organizing meetings.

Both the SVC and Government must mutually agree to meeting times, platform, and content.

Content may change as required. The SVC shall provide meeting minutes within seven calendar days of each meeting. Table 2 below is an overview of the required working groups, review boards, and meetings, as required.

Meeting Title Meeting Platform Meeting Frequency Attendees

Kick-Off Meeting (IDIQ Award) Section 6.2.1

In-Person or Virtual

Once, within 7 calendar days of contract award

SVC, Government

Kick-Off Meeting (per DO) Section 6.2.1

In-Person or Virtual

Once, within 21 calendar days of DO award SVC, Government

Management Integrated Product Team Meetings

Section 6.2.2 Virtual As required SVC, Government

Quarterly Management Meeting Section 6.2.3

In-person or Virtual Quarterly SVC, Government

Reserved 6.2.4 Virtual As required SVC Government SV and Ground Operations Working Group Meetings

Section 6.2.5 Virtual As required SVC, Government

Periodic Technical Interchange Meeting Section

6.2.6

In-person or Virtual As required SVC, Government

Periodic Configuration Control Board Meeting

Section 6.2.7 Virtual As required SVC, Subcontractors, Government

LV Integration Meeting Section 6.2.8

In-person or Virtual As required SVC, LV Contractor, Government Periodic Technical

Interchange Meeting- Launch Campaign Section

6.2.9

In-person or Virtual

As required and/or daily at launch site

SVC, LV Contractor, Government, Payload On-orbit Operations Working Group Section

6.2.10

In-person or Virtual As required

SVC, Ground Segment contractor (if sub), Government, PL sponsoring organization SC-to-PL Integration

Working Group Section 6.2.11

In-person or Virtual

As required SVC, Government, PL sponsoring organization

TABLE 2 MEETINGS AND REVIEWS

6.2.1 Kick-Off Meetings

IDIQ and DO Award Kickoff Meetings will be conducted jointly by the Government and SVC. The SVC’s Program Manager, Chief Engineer, Contracting Representative and other personnel deemed necessary by the SVC will attend. Kick-off meetings shall emphasize personnel deemed necessary, communications, requirements, deliverables, schedule, key events and milestones, and risk. The SVC shall translate mission requirements into system requirements to establish the formal system requirements baseline to be reviewed at the DO Kick-off Meeting. The SVC shall ensure that the requirements are understood by all stakeholders.

6.2.2 Management Integrated Product Team Meeting

IPT Meetings shall emphasize budgeted versus actual cost, schedule and technical status, SC/SV development, integration and test, and mission operations status, program overview with most important topics addressed, weekly planned activities, issues and risk, and action item status requiring Government and SVC coordination.

6.2.3 Quarterly Management Meeting

Quarterly Management Meetings shall clearly state the work accomplished on the project during the reporting period and emphasize:

• Program overview with most important topics addressed.

• Technical Performance Measurement (TPM) status

• Budgeted versus actual cost.

• Brief description of milestones and significant accomplishments scheduled for completion during the reporting period and actual/relative status.

• Integrated Master Schedule (IMS), milestone update/status, detailed schedule status.

o SVC shall provide the baseline IMS at the first quarterly meeting.

o To include delays and get-well plans.

• Current and potential program issues, risk management activities, and technical trades to include resolution plans.

o The SVC shall summarize problem areas together with a schedule and performance impact summary and a discussion of the corrective actions and recovery plans.

• Technical risks and configuration changes status.

• Quality assurance execution and updates.

• Supply chain, production, critical parts and long lead item status, etc.

• SC/SV development, integration and test status, PL accommodation status, mission operations status, and ground solution status.

• Action items status requiring Government and SVC coordination.

• Cumulative list depicting closed items, open items, status, Point of Contact working action, and estimated completion dates (ECDs).

The SVC shall develop format and detailed content of these presentations in conjunction with and subject to Government approval.

[CDRL F001/O001 - Quarterly Management Meeting Minutes]

6.2.4 Reserved

6.2.5 SV and Ground Operations Working Group

SV and Ground Operations Working Group shall plan, coordinate, and track status of the ground operations integration to the SV and delivery of PL data.

The SVC shall provide a Ground Specification Document (GSD) detailing the design and interface requirements for government review for each DO.

The SVC’s GSD shall include:

• Roles and responsibilities.

• Payload Success Criteria.

• Mission Operations Requirements.

• Payload Operations Requirements.

• Support Requirements.

• Orbital Management Requirements.

• Telemetry Requirements.

• Post-pass Telemetry Processing and Data Product Requirements

• Test Support Requirements.

• Training Requirements.

• Mission Security Requirements.

• LEOP.

• End of Life.

[CDRL F001/O001– SV and Ground Operations Working Group Minutes]; F022/O022 – Ground Specification Document (GSD)

6.2.6 Technical Interchange Meeting

Periodic Technical Interchange Meetings shall emphasize specific mission issues of concern that require the combined attention of the Government, supporting contractors, and the SVC.

6.2.7 Configuration Change Meeting

The SVC shall hold, on an as-needed basis, Engineering Change Board (ECBs) and Configuration Control Board (CCB) meetings to review and process any technical or programmatic and documentation baseline changes that occur during the execution of this contract. All agreed to changes will be appropriately documented.

ECB and CCB meetings will include the Contractor, Subcontractor(s), and the Government depending on the nature of the change(s) discussed.

The SVC shall notify the Government in advance of any ECB and CCB meeting scheduled.

The Government’s representative shall be an approving member of each ECB and CCB.

6.2.8 Failure Review Board Meetings

The SVC shall hold Failure Review Board (FRB) meetings for the purpose of resolving product defects that are identified during testing.

FRB meetings will include the Contractor, Subcontractor(s), and the Government depending on the nature of the failure(s) identified and discussed.

The SVC shall notify the Government in advance of any FRB meeting scheduled.

The Government’s representative shall be an approving member of each FRB.

6.2.9 LV Integration Meetings

The SVC shall support LV integration working group meetings. LV integration meetings will emphasize mission launch operations to include the development of the SV-to-LV Interface Control Document (ICD), launch planning, SV handling and shipping, Ground Support Equipment (GSE) requirements, SV final check-out and any hazardous operations prior to integration, SV integration with the LV/Integrated Payload Stack (IPS), system safety and flight LV procedures.

6.2.10 Periodic Technical Interchange Meeting – Launch Campaign

The SVC shall support in-person or teleconference Technical Interchange Meetings (TIMs) during the launch campaign to discuss planned work and daily schedule, as required.

6.2.11 Payload On-Orbit Operations Working Group Meetings

Payload On-Orbit Operations Working Groups shall define, facilitate, and coordinate all mission operations regarding the PL(s) to develop and execute the SV concept of operations (CONOPS).

The SVC shall organize and lead the Payload On-Orbit Operations Working Groups.

6.2.12 SC-to-PL Integration Working Group Meetings

The SVC shall work with the PL provider, and Government during the development of the SV-to-Payload ICDs and to facilitate the integration of the PL to the SC, ensuring compatibility between the SC and PL throughout the Assembly, Integration, and Test (AI&T) process.

6.3 General Contracting Requirements

6.3.1 Funds and Labor Hour Report

The SVC shall provide a monthly Funds and Labor Hour Report (FLHR) for any cost type CLINs.

[CDRL F002/O002– FLHR Report]

6.3.2 Cost and Software Data Reporting

The SVC shall prepare and submit Cost and Software Data Reporting (CSDR) in accordance with DODI 5000.73 and DoD 5000.04-M-1.

The SVC shall prepare and submit a Contract Work Breakdown Structure (CWBS), Cost and Hour Report (Flexfile), and CSDR Technical Data Report.

[CDRLs F016/O016 – CWBS; F017/O017 – Cost and Hour Report (Flexfile); F018/O018 – CSDR Technical Data Report]

6.3.3 Contracts and Subcontracts Management

If required, the SVC shall establish and implement a subcontract management and controls system sufficient to provide timely, in-depth, and accurate visibility into the subcontractor’s technical, quality assurance, financial, and schedule performance. The SVC shall provide a Small Business Subcontractor Report.

[CDRL F005/O005 – Small Business Subcontractor Report]

6.4 Program Management Plan and Integrated Master Schedule

The SVC shall develop and maintain a logically networked schedule for each DO detailing planned events and milestones, accomplishments, and activities from contract award to the completion of the contract.

The SVC shall provide a Program Management Plan (PMP) and an IMS.

[CDRLs F006/O006 – PMP; F013/O013 – IMS]

6.4.1 Key Events and Milestones

Significant accomplishments and criteria for each program key event descriptions are in STEP 2.0 Key Events and Milestones as shown in table 3 and shall be used as a guideline for Milestone events.

ID Event Section A IDIQ Contract Kickoff Overview of IDIQ spacecraft and program plans, with a specific emphasis on chains of command and communication pathways (Section 6.2.1).

B DO Kickoff Overview of DO spacecraft and program plans, with a specific emphasis on chains of command and communication pathways (Section 6.2.1).

C Payload Accommodation Design

Review (PADR)

Ensure that any Action Items are tracked through resolution and STEP 2.0 interface requirements are met at all levels. (Section 9.1.2).

D Spacecraft Integration Readiness Review (SIRR)

Ensures SVC’s readiness to assemble the SC (Section 8.3.2).

E Spacecraft Acceptance Review Ensures SC assembly meets the SVC’s SC design requirements (Section 8.3.2).

F Payload Integration Readiness Review (PIRR)

Ensures PL integration procedures, functional check-outs, and facilities are in place for integration (Section

9.11).

G SV Test Readiness Review (TRR) Ensures procedures and facilities are in place for system level testing (Section 10.4.1).

H Test Data Review (TDR) Should include all testing of the complete vehicle including TVAC, dynamics, list of anomalies and how they were mitigated, etc. (Section 10.4.3).

I SV Pre-Ship Review (PSR) Verify that the completed SV meets requirements and is ready to ship to the launch integration site (Section

10.6).

J Ground Segment Readiness Review (GSRR)

Critical review of SV ground segment readiness to perform mission operations rehearsal and integrated

SV testing (Section 14.1.4).

K Mission Readiness Review (MRR) Demonstrate the integrated SV is ready for launch, the ground segment, and the SV, PL teams’ readiness for experiment operations (Section 13.10).

L Nominal Operations Readiness

Review (NORR) Validates completion of Launch and Early Operation Phase (LEOP) activities and review SV readiness to begin experiment operations (Section 14.2.3).

M Reserved – Storage Storage of STEP 2.0 SV as directed by Government

(Section 11).

TABLE 3 STEP 2.0 KEY EVENTS AND MILESTONES

6.5 Contractor Integrated Performance Management

The SVC shall establish, maintain, and use integrated performance management in the performance of this contract.

The SVC’s integrated performance management shall include the IMS, CWBS, change management, material management, procurement, cost estimating, and accounting.

Correlation and integration of these systems and processes will provide for early indication of cost, schedule, and technical performance.

6.6 Government Property

The SVC shall mark the delivered SV with a single Item Unique Identification (IUID) number.

The SV IUID will be the tracking number for the DO’s Period of Performance (PoP).

The SVC shall complete the Material Inspection and Receiving Report for the Government to accept the SV following Nominal Operations Readiness Review (NORR).

6.6.1 Government Furnished Property

The SVC shall manage Government Furnished Property (GFP) IAW the FAR, Defense Federal Acquisition Regulation Supplement (DFARS), and pertinent property accountability guidance (i.e., IUID).

The SVC shall provide an IUID Marking Activity, Validation and Verification Report.

The Government will provide GFP to the SVC no later than the dates indicated in the DO or as agreed to between the SVC and the Government.

The PL team might furnish PL mass/engineering model(s) to the SVC as GFP.

The Government might provide National Security Agency (NSA) certified cryptographic equipment in support of a DO.

HW deliveries include any special handling, test equipment HW, SW, and sparing required for integration, alignment, and PL functional testing (as required).

[CDRL F003/O013 – Item Unique Identification (IUID) Marking Activity, Validation and Verification Report]

6.7 System Safety

The SVC will ensure this effort complies with industrial safety requirements in performance of all efforts associated with Military Standard (MIL-STD)-882E.

The SVC shall provide a System Safety Program Plan (SSPP) and System Safety Reports in accordance with MIL-STD-882E and Air Force Instruction (AFI) 91-202, paragraph 11.2.2.2.

The SVC shall provide Accident / Incident reports, as required.

The SVC shall provide a Safety Assessment Report (SAR) in accordance with Air Force Space Command (AFSPC) supplement to AFI 91-202 paragraph 11.2.5.1.

The SVC shall provide a Preliminary Hazard List (hazard tracking log).

The SVC shall support range safety plans and activities as required by the launch site selected by the program and provide inputs to the mission’s Missile System Pre-launch Safety Package (MSPSP) in accordance with Space Systems Command Manual (SSCMAN) 91-710 V3.

The SVC shall provide a Combined Space Vehicle Debris Assessment Report/End-of-Life Plan (SDAR/EOLP) in accordance with AFI 91-202.

The SVC will provide inputs to STP’s Spaceflight Worthiness Certification (SFWC) in accordance with SSC Guide Space Missile Command (SMC)-G-1202.

[CDRLs F014/O014 – SSPP; F009/O009 – Accident/Incident Report; F021/O021 – SAR;

F015/O015 – Preliminary Hazard List; F020/O020 – Inputs, MSPSP; F008/O008 – SDAR/EOLP;

F008/O008 – Inputs, SFWC]

6.8 Government Visiting Team Support

The SVC shall provide facilities and services necessary to support Government visiting personnel as required for each DO.

The SVC’s facilities shall include telephones and computer network connections with access to the internet for the entire period of the visit.

The SVC shall provide visiting Government personnel unescorted access to all areas dedicated to this program and prearranged escorted access to the other areas used by this program.

7. GENERAL ENGINEERING REQUIREMENTS

7.1 Systems Engineering

The SVC shall provide the System Engineering (SE) and technical management support required to ensure that the SC and the Ground Segment meet all technical performance requirements identified in each DO.

The SVC SE Team shall:

• Develop a system requirements baseline and functional architecture that can be used to identify, track, and manage key TPMs and technical budgets.

• Provide requirements flow down and verification at the SC level. The SVC SE team shall verify requirements are met through SV AI&T and LV AI&T activities.

• Conduct internal peer, design, and readiness reviews prior to and at major mission events and transitions.

• Track and report key mission TPMs at the Quarterly Management Meeting.

• Track risks and implement risk mitigation plans as necessary.

• Provide fault management analysis and documentation.

• Ensure all SC/SV requirements are met and verified.

• Assure that specialty engineering, key to successful integration of the specialty engineering functions, is incorporated into the initial design studies, and throughout the duration of the contract.

7.2 System Engineering Processes and Plans

The SVC shall design, fabricate, and test the SC and SV adhering to standard commercial aerospace processes. The SVC shall document relevant processes and methodologies in various process plans.

7.2.1 Systems Engineering Management Plan

The SVC shall provide a System Engineering Management Plan (SEMP) detailing its overall systems engineering management approach to satisfying STEP 2.0’s requirements.

The SEMP shall describe:

• Technical effort and technical processes on what will be used and how the processes will be applied using appropriate activities.

• Project structure to accomplish activities, information flow, and decision-making.

• Resources required for accomplishing STEP 2.0 activities.

• Project critical event’s objectives during any phase of a project’s life cycle.

• Work product outputs of the processes and how the processes are integrated.

• Communication standards between project management engineering teams and entry/exit criteria of work products during project phases.

[CDRL F010/O010 – SEMP]

7.2.2 Configuration Management Process and Plan

The SVC shall provide Configuration Management (CM) to include a Configuration Management Plan (CMP) detailing how it intends to meet CM requirements from SC assembly to experiment on-orbit operations.

The SVC shall deliver a Data Accession List (DAL) identifying SVC generated data in compliance with DO work efforts.

The SVC’s CMP shall describe, at a minimum:

• Organizational relationship of CM authority and functions within the company and the program.

• Policies and procedures for release and control of configuration identification media including drawings, specifications, processes, manufacturing and test procedures, and computer SW as applicable.

• Membership, functions, responsibilities, and the SVC’s CCB operating procedures.

• Authority and responsibilities of the person(s) designated to manage CM activities.

• Methods of verification and configuration accounting to ensure implementation of approved design configuration and changes.

• Policies, procedures, and methods for ensuring compatible CM operations at sub-tier suppliers and at other company divisions.

• Special or abridged CM operations peculiar to the needs of this procurement.

The SVC’s CMP shall:

• Identify and document the functional and physical deliverable HW/system characteristics - Configuration Identification.

• Control changes to those characteristics - Configuration Control.

• Record and report change processing and implementation status - Configuration Accounting.

All CM operations are subject to Government audit against the requirements of this SOW, provisions of applicable Quality and Reliability Standards, and the SVC’s approved CMP.

All Class I configuration changes to approved baselines shall be documented on an engineering change proposal and be submitted to the Government (STP) for approval.

The SVC shall be responsible for configuration management of lower tier suppliers in general accordance with requirements herein.

[CDRLs F010/O010 – CMP; F004/O010 – DAL]

7.2.3 Risk Management Plan

The SVC shall develop and provide a Risk Management Plan (RMP). The SVC shall submit and maintain a Risk Database which shall include ranked groups of risks with detailed risk burn-down plans.

The risk burn-down plans shall have risk reduction activities that tie to key program milestones.

The SVC shall review and update the RMP and identify risk exposure to include likelihood and consequence throughout the life of the contract.

The SVC shall report program risk status in management meetings, or as needed and directed by the designated by the Government (STP).

[CDRL F007/O007 – RMP]

7.2.4 Software Configuration Management Plan

The SVC shall provide a configuration control system for SW code and the documentation developed for application and operational use, or used to support qualification, acceptance of flight hardware and delivered GSE.

The SVC shall document its configuration management process, to include flight SW, in a Contractor’s SW Management Plan (SMP) / SW Development Plan (SDP).

The SVC shall obtain Government (IDIQ COR) approval for all changes to standard interface code and/or documentation via recertification or review unless waived on an individual case basis by both the Government (DO COR) and the SVC.

[CDRL F010/O010 – SMP/SDP]

7.2.4.1 Configuration Control

The SVC configuration control process shall be in place for fabrication, assembly and test of the existing flight unit and its associated test equipment and test and analysis SW.

The SVC’s configuration control system shall ensure that only current configuration identification documents and authorized changes are used for procurement, assembly, integration, inspection and test of the existing flight unit and its associated test equipment and test analysis SW.

The SVC shall establish a formal CCB of program and functional management personnel to evaluate and approve/disapprove all formal change requests to the procurement, assembly, integration, inspection and test of space and ground segments.

The SVC shall maintain “as-built” configuration records, which will enable positive configuration verification and retrieval to the lowest level of manufacturing and test history necessary to prepare part pedigree reports consistent with data rights assertion documented in final DO. The SVC shall submit changes to “as-built” and pedigree reports for CCB review. For COTS, this shall be limited to the commercial product level, as commercially procured items might not provide part pedigree supporting data to the lowest level of manufacturing and test history.

All Class I changes to approved baselines shall be documented through an Engineering Change Proposal (ECP) process and be approved by the Government (STP) before implementation.

Class I changes are defined as changes that affect form, fit, function, cost, or schedule of the final assembly. Class II changes are defined as changes to correct documentation (including typographical changes) or changes to hardware not defined as Class I changes. Class II changes shall be listed by number and title in the monthly status reports for review. Departures from or non-compliance with approved baselines shall be requested using a deviation/waiver request. The SVC’s configuration accounting system shall provide for traceability of Class I change implementation to the lowest level of hardware and test procedure impacted.

The SVC shall obtain Government (STP) approval for configuration changes to the ground segment and SV post End-to-End testing, and prior to NORR, unless required for anomaly resolution. The SVC shall request Government approval for post NORR flight software changes unless required for anomaly resolution. When configuration changes are required for anomaly resolution, the SVC shall provide the configuration change to the Government (STP) in a timely manner.

7.2.5 Parts, Materials and Processes

The SVC shall provide and implement a Parts, Materials, and Process Control Plan describing parts/materials selection, screening, qualification, application, the approval process, parts obsolescence, and how it will implement hardware/SW quality assurance. The SVC shall design and implement a Level 2 parts program per Goddard Space Flight Center (GSFC) EEE-INST- 002 to provide reliability and parts engineering for the electrical, electronic, and electromechanical parts of the SV. Radiation levels for analysis and test per EEE-INST-002 will be specified for each DO. The SVC shall provide risk/issue management regarding the procurement of space hardware. The SVC should conduct quality and site surveys of major suppliers.

[CDRL F010/O010 – Parts, Materials & Process Control Plan]

7.2.6 Contamination and Environmental Controls

The SVC shall provide a Contamination Control Plan describing how its contamination and environmental program will minimize the risk of contamination and maintain cleanliness, temperature, and humidity of PLs throughout all phases of assembly, integration, transportation, and launch.

[CDRL F008/O008 – Contamination Control Plan]

7.2.7 Quality Assurance

The SVC shall employ quality and reliability standards to ensure STEP 2.0 requirements can be satisfied throughout a mission’s lifecycle. The SVC shall provide and implement bus level product assurance and document its methodology in a Product Assurance Plan. The SVC shall provide and implement a Quality Assurance Plan.

[CDRLs F010/O010 – Quality Assurance Plan; F010/O010 – Product Assurance Plan]

7.2.8 Electromagnetic Interference and Electromagnetic Compatibility Design Practices and Control

The SVC shall provide Electromagnetic Interference (EMI) and Electromagnetic Compatibility (EMC) design, practices, and control to meet the requirements in the IDIQ SRD.

[CDRL F008/O008 – EMI/EMC Design Practices and Control]

7.3 Reserved

7.4 Model Based System Engineering

The use of Model Based Systems Engineering will be determined for each DO.

If the Systems Engineering Model is required, the SVC shall develop, maintain, and provide to the Government descriptive SysML-compliant models, in the native format generated by the modeling tools, that capture essential data to document the system architecture in a System Engineering Model (SEM); to include:

• Requirements for the spacecraft and ground segment.

• Interface requirements for spacecraft to payload, spacecraft to ground, spacecraft to launch vehicle, and payload to ground interfaces.

• System architecture including system CONOPS, behavior, logical/physical definition of system structure and function, and external interfaces.

• Traceability between system requirements, architecture, system design, and verification, validation & test.

• Meet the intent of the Requirements Verification Matrix as defined in IDIQ SOW Section

7.8.

If the Systems Engineering Model is required, the SVC shall collaborate with the Government at the System Level Engineering Meeting to define Systems Engineering Model views and content that satisfy stakeholder needs. If the Systems Engineering Model is required, the SVC shall address the development, data management, configuration management, and verification & validation planning of model-based processes in the SEMP.

[CDRL F026/O026 – System Engineering Model (SEM)]

7.5 Specialty Engineering

The SVC will use specialty engineering concepts throughout the entire contract period of performance to include throughout the system architecture definition, the design phase, and test phase to minimize program risk and improve system effectiveness. Specialty engineering typically includes reliability, failure mode analysis, maintainability, dependability, logistics, fabrication/production, test, transportation, human factors, quality assurance, and human and HW safety.

7.6 Reliability

The SVC shall implement a reliability program that describes how SVC systems comply with the IDIQ SRD and DO requirements to include Failure Mode Effects Analysis (FMEA). The SVC shall provide a reliability prediction at 1 year following launch for the SC using the parts count method as defined in MIL-HDBK-217F as guidance.

[CDRLs F011/O011 – Reliability Predictions; F012/O012 – FMEA]

7.7 Spectrum

The SVC shall lead all Federal Communications Commission (FCC) licensing efforts and support the Government’s efforts to obtain National Telecommunication Information

Administration (NTIA) certification and frequency assignment for the SC and ground segment throughout a DO’s period of performance.

The SVC’s SC HW and performance shall have demonstrated compliance with FCC/NTIA licensing requirements, on a previous mission, prior to award. The SVC shall deliver existing historical documentation demonstrating proof of FCC/NTIA compliance. Relevant historical documentation should include relevant measured data, FCC Licenses, NTIA Certifications, RFAs, 1494s, E3VPs, E3VRs, E3IARs, SSRAs, and updates. The SVC shall maintain compliance throughout a DO’s PoP.

[CDRLs F022/O022 – Inputs, NTIA Allocation Request; F022/O022 – Inputs, E3 Analysis;

F023/O023 – E3 Verification Procedures (E3VP); F024/O024 – E3 Integration and Analysis Report (E3IAR); F025/O025 – E3 Verification Report (E3VR); F022/O022 – Historical Spectrum Documentation; F022/O022 – FCC Call Sign]

7.8 Requirements Verification Matrix

The SVC shall provide a Requirements Verification Matrix (RVM) document consisting of SV requirements and a traceability matrix demonstrating flow down from source program requirements (e.g., DO SRD, DO PLRD, DO SOW, and various ICDs) to the subsystem level.

The RVM shall delineate the method of verification of all program requirements to include an SV design summary and for each requirement the level(s) of assembly at which verification is performed, the method of verification, and data results to be submitted in the Mission Readiness Review (MRR).

The SVC shall use the appropriate inspection, demonstration, test, and analysis techniques to verify all requirements.

[CDRL F019/O019 – RVM]

7.9 Hardware and System Configuration Identification

The SVC configuration control process shall be in place for fabrication, assembly and test of the existing flight unit and its associated test equipment and test and analysis HW.

The SVC’s configuration control system shall ensure that only current configuration identification documents and authorized changes are used for procurement, assembly,…