Attachment 7 - SSHINE_SOW_TO_03_RVEX_12 Nov 24.pdf

SPACE SYSTEMS AND HARDWARE INTEGRATION FOR NOVEL

EXPERIMENTS (SSHINE)

TASK ORDER 0003

RAPID ARCHITECTURE PROTOTYPING AND INTEGRATION

DEVELOPMENT (RVEX)

STATEMENT OF WORK (SOW)

12 November 2024

1. Mission and Background The RAPID mission is to ease and accelerate the efforts of the United States Space Force (USSF) to pivot to new architectures and concepts of operations described in future Force Designs based on recommendations by the Space Warfighting Analysis Center (SWAC). RAPID executes this mission three ways: Feed back (to inform SWAC analytics), Feed forward (to inform future requirements and acquisitions) and Provide Options (to expand the trade space for the future force). RAPID conducts hardware- and software-in-the-loop experimentation – to include modeling, simulation and field experiments, and integrates and exercises technologies to validate that real-world performance meets expectations.

The purpose of RAPID is to streamline the acquisition process between the stages of Analysis, Prototyping, Enterprise Testing, and Program of Record by involving multiple organizations from each stage in the process of providing products to fulfil USSF needs. The objective of the Rapid Architecture Prototyping and Integration Development (RAPID) Task Order is to provide the Air Force Research Laboratory (AFRL) Space Vehicles Directorate (RV), Integrated Experiments and Evaluation Division (RVE), RAPID Branch with research and development, systems engineering, mission development, modeling and simulation, and ground and flight operations support for both large and small space technology experiments as defined in the basic contract SOW.

2. Scope The Government anticipates numerous general efforts over the total contract period of performance on this task order. This effort involves the Mission and Space System Development, Space Experiment Prototyping, Assembly, Integration, and Testing, and Ground System Development functional areas as defined in the basic contract SOW.

3. Compliance and Reference Documents Compliance and Reference Documents are listed in the basic contract SOW (Section 3.0 Compliance and Reference).

4. Requirements

STATEMENT OF WORK: RAPID ARCHITECTURE PROTOTYPING AND INTEGRATION DEVELOPMENT (RAPID)

The following requirements are applicable to RAPID. The contractor may be required to travel to other Government agencies and/or other contractor locations to perform design, integration, and test activities in support of RAPID.

4.1 Mission and Space System Development.

4.1.1 The contractor will support direct technical and systems engineering tasks to RAPID Program Managers, Deputy Program Managers, Chief Engineers, Systems Engineers, or other designated program leads.

4.1.2 Reserved.

4.1.3 The contractor will support in the development of government flight experiment and space technology requirements, mission scope, design tradeoffs/alternatives, concepts of operation, mission constraints, conceptual designs, and mission analyses, including:

4.1.3.1 Refinement of programmatic objectives into actionable requirements.

4.1.3.2 Analyses and documentation for laboratory, range, ground, near-space, and/or space flight experiments.

4.1.3.3 Iteration of requirements, flow-downs, concept of operations; the refining of objectives; and interface management.

4.1.4 The contractor will perform analyses and evaluations accomplished through relevant experimental testing, modeling and simulation, and engineering analysis.

4.1.5 The contractor will prepare documentation for all systems engineering activities related to space technology programs and individual flight experiments, to include technical input into development of Government Reference Designs (GRD).

4.1.6 The contractor will support Model Based Systems Engineering (MBSE) when/where applicable/requested, including requirements definition, design, analysis, and verification/validation activities beginning in the conceptual design phase and continuing throughout program life cycle, including:

4.1.6.1 Development of MBSE models.

4.1.6.2 Evaluation of models delivered by outside performers.

4.1.6.3 Exercise and test of models in support of RVE objectives.

4.1.7 The contractor will support modeling and simulation tasks, including:

4.1.7.1 Development of modeling capabilities to simulate, emulate and evaluate technology options identified by RVE.

4.1.7.2 Testing and operation of modeling and simulation capabilities.

4.1.7.3 Analyses comparing model and simulation results to experimental findings.

4.1.7.4 Analyses identifying requirement shortfalls, missing functionality, and model improvements.

4.1.8 The contractor will support Systems Engineering tasks, including mechanical, thermal, electrical, structural, and other specialized engineering to support mission development for space technology, spacecraft, and high-altitude balloon experiment designs.

4.1.9 The contractor will support Hardware/Software-in-the-Loop and Cloud Computing Architecture development and administration tasks including:

4.1.9.1 Design and development of cloud computing architectures supporting RVE hardware/software-in-the-loop testing environments.

4.1.9.2 Implementation of cross-domain solutions to move data between different classification levels, external connections, and point-to-point transmissions.

4.1.9.3 Develop, maintain, and upgrade RVE hardware/software-in-the-loop testing environments.

4.1.9.4 Comprehensive cybersecurity and information assurance support, including compliance with Department of Defense (DoD) risk management frameworks, and other security requirements.

4.1.9.5 Implementation of cryptographic and cross-domain solutions to move data between different classification levels, external connections, and point-to-point transmissions.

4.1.9.6 Design and implementation of software tools.

4.1.9.7 Modifying existing software/firmware.

4.1.9.8 Writing and documenting new code.

4.1.9.9 Integrating and testing new or modified code.

4.1.9.10 Maintaining software and related databases.

4.1.9.11 Software configuration management.

4.1.9.12 Physical system maintenance.

4.1.10 The contractor will support in the development of space technology and flight experiment requirements, design, and interface control documentation.

4.1.11 The contractor will support with program management tasks, including attendance at technical meetings, reviews, off-sites, or technical conferences.

4.1.12 The contractor will support procurement assistance with long lead hardware/software critical to future space experiment program success.

4.1.12.1 The contractor will support the procurement of available commercial and non-commercial space-rated/grade related hardware.

4.1.13 The contractor will support miscellaneous tasks such as trade studies, demonstrations and various analysis as directed by the Government Program Manager.

4.1.14 The contractor will support technology transfer planning and decommissioning support, to include planning in support of technology transition to external mission partners.

4.1.15 The contractor will support the design and fabrication of ground-based proofs-of-concept, experiments, and demonstrations.

4.1.15.1 The contractor will prepare documented data acquisition, processing, analysis, and modeling/simulation tools to be used in the experiment, research, or analysis effort for evaluations.

4.1.15.2 The contractor will document experimental processes and results to allow third parties to independently reproduce the experiment, research, or analysis effort.

4.1.16 Reserved.

4.1.17 The contractor will travel to other Government agencies and/or other contractor locations, as required, in support of design and test requirements reviews, briefings to industry, conferences and other meetings related to RAPID integration and test programs.

4.1.18 The contractor will prepare monthly status reports on activity under the scope of section 4.1 and document lessons learned.

4.1.18.1 The monthly status report may be combined with the other monthly status reports in section 4.

4.1.18.2 The contractor will present monthly status reports and lessons learned to internal and/or external audiences as directed by the government.

4.2 Space Experiment Prototyping, Assembly, Integration, and Testing:

4.2.1 The contractor will support direct analytical, technician, and systems engineering tasks of the RVE Assembly, Integration, and Testing Infrastructure Lead(s).

4.2.2 The contractor will draft, prepare, revise, and review design documentation including, but not limited to:

4.2.2.1 User’s guides.

4.2.2.2 Interface Control Documents (ICDs), Specifications.

4.2.2.3 Test Processes/Procedures.

4.2.2.4 Safety Plans.

4.2.2.5 Risk Management Plans.

4.2.2.6 Attendance and participation in programmatic, technical and safety reviews.

4.2.2.7 Reliability, operability, interoperability, and performance assessments.

4.2.3 The contractor will support full life-cycle technology implementation tasks, including:

4.2.3.1 Space technology, spacecraft, and high-altitude balloon flight hardware design and fabrication.

4.2.3.1.1 Hardware development and integration.

4.2.3.1.2 Hardware testing and experimentation.

4.2.3.1.3 Technology transition support.

4.2.3.2 Space technology, spacecraft, and high-altitude balloon flight software/firmware design and development.

4.2.3.2.1 Modifying existing software/firmware.

4.2.3.2.2 Writing and documenting new code.

4.2.3.2.3 Integrating and testing new or modified code.

4.2.3.2.4 Maintaining software and related databases.

4.2.3.2.5 Software configuration management.

4.2.3.3 Laboratory research, test and assessment design, technology validation testing and experimentation.

4.2.3.3.1 Ground/laboratory test planning and procedures

development, test design and fabrication, test preparation and coordination.

4.2.3.3.2 Arrangement of equipment and logistics for the test effort.

4.2.3.3.3 Systems-level tests to evaluate performance of

spacecraft, balloon, and ground systems/subsystems.

4.2.3.3.4 Data reduction, analyses, and review the results of functional and environmental testing of spacecraft, high-altitude balloon, and ground systems/subsystems.

4.2.3.3.5 Documented data acquisition, processing, analysis, and modeling/simulation tools to be used in a technology validation effort.

4.2.3.3.6 Documenting experimental processes and results to allow third parties to independently reproduce the evaluation effort.

4.2.3.4 Re-engineering and re-design of software and hardware after testing.

4.2.4 Reserved.

4.2.5 Reserved.

4.2.6 Reserved.

4.2.7 The contractor will support the Government in shipping and receiving of flight experiment and assembly, integration, and testing hardware/software.

4.2.8 The contractor will have the ability to support a surge capability to meet requirements of section 4.2 within unexpected or tightened program constraints.

4.2.8.1 In the event surge requirements drive a change to the contract, the contractor will be notified through a Request for Proposal (RFP), contract/task order modification, or contracts letter, as appropriate.

4.2.9 The contractor will travel to other Government agencies and/or other contractor locations, as required, in support of design and test requirements reviews, briefings to industry, conferences and other meetings related to RAPID integration and test programs.

4.2.10 The contractor will prepare monthly status reports on activity under the scope of section 4.2 and document lessons learned.

4.2.10.1 The monthly status report will be combined with the other monthly status reports in section 4.

4.2.10.2 The contractor will present monthly status reports and lessons learned to internal and/or external audiences as directed by the government.

4.3 Reserved.

4.4 Ground System Development.

4.4.1 Reserved.

4.4.2 Reserved.

4.4.3 The contractor will support RVE in-house ground system integration and deployment tasks, including:

4.4.3.1 Physical and cloud-based ground system maintenance.

4.4.3.2 Maintenance and upkeep of Mission Operations Center connections and equipment.

4.4.3.3 Procurement of cloud computing access and storage.

4.4.3.3.1 Support of RVE disaggregated development network

4.4.3.3.2 Support RVE ability to contract with other commercial ground stations for mission support.

4.4.3.4 The contractor will support direct IT and network engineering tasks to RAPID facilities and team members.

4.4.3.5 The contractor will lead the stand-up, installation, accreditation, and maintenance of classified and unclassified IT systems.

4.4.3.6 The contractor will support direct technical and network engineering tasks for prototyping and communications experiments.

4.4.3.7 The contractor will prepare and submit Authorization to Operate (ATO) packages in support of standing up information networks and information network experiments.

4.4.4 The contractor will accomplish ground architecture cybersecurity accreditations on behalf of RVE, including:

4.4.4.1 Obtaining and maintaining compliance with Authorities to Operate.

4.4.5 The contractor will travel to other Government agencies and/or other contractor locations, as required, in support of design and test requirements reviews, briefings to industry, conferences and other meetings related to RVE integration and test programs.

4.4.6 The contractor will prepare monthly status reports on activity under the scope of section 4.4 and document lessons learned.

4.4.6.1 The monthly status report will be combined with the other monthly status reports in section 4.

4.4.6.2 The contractor will present monthly status reports and lessons learned to internal and/or external audiences as directed by the government.

4 Contract Management

The contractor will perform contract requirements in accordance with the basic contract SOW (Section 5.0 Contract Management).

5 Key Personnel

The functions below are considered essential to the work being performed on contract in addition to those required by the basic contract SOW (Section 5.2 Personnel Management):

5.2 SYSTEM ENGINEER (MID-LEVEL)

5.2.1 5+ years of systems engineering experience on complex defense systems

(communications systems is highly preferred)

5.2.2 Active Top Secret SCI clearance

5.2.3 Desired education: Master's degree in science, Technology, Engineering, or Mathematics (STEM), Information Technology, computer science or similar from a regionally accredited institution.

5.3 TEST ENGINEER (MID-LEVEL)

5.3.1 5+ years of test experience on complex defense systems (communications systems is highly preferred)

5.3.2 Active Top Secret SCI clearance

5.3.3 Desired education: Master's degree in Science, Technology, Engineering, or Mathematics (STEM), Information Technology, computer science or similar from a regionally accredited institution.

5.4 FACILITY IT MANAGER (MID-LEVEL)

5.4.1 5+ years of experience managing and maintaining government IT systems

5.4.2 Active Top Secret SCI clearance

5.4.3 Desired education: Bachelor’s degree in Science, Technology, Engineering, or Mathematics (STEM), Information Technology, computer science or similar from a regionally accredited institution.

6 Security Requirements

6.2 Clearance Requirements: The contractor will establish and implement information and physical security programs governing their efforts in accordance with the Task Order DD254 Contract Security Classification Specification. At a minimum, contractor personnel will be eligible to obtain a Top-Secret Clearance.

6.3 At a minimum, contractor personnel will be eligible to obtain a Top-Secret Clearance with SCI and SAP accesses. Access to SIPR, JWICS and other classified systems is required.

6.4 The Government will provide the contractor with system/program Security Classification Guidance and other instructions on adherence to security requirements.

7 Associate Contractor Agreements

The Contractor will enter into Associate Contractor Agreements (ACA) for any portion of task order performance requiring joint participation in the accomplishment of the Government's requirement. ACAs will be executed in accordance with requirements in the basic contract

SOW.

8 Deliverables The contractor will deliver all deliverables in accordance with the Contract Data Requirements List (CDRLs) defined in the basic contract (Section 14.0 Contract Data Requirements List).

9 Base Support

The Government will provide base laboratory support in accordance with basic contract SOW (Section 15.0 Base Support).

10 Government Property/Contractor Acquired Property

10.2 The contractor may be required to procure/acquire property or equipment during the performance of a task order. The following rules apply to all such tasks:

10.2.1 Purchases must be authorized by a Government Technical Lead.

10.2.2 Purchases exceeding the Standard Simplified Acquisition Threshold must be authorized by the contracting officer.

10.2.3 Any equipment or property procured and all Government-provided records, files, documents, and work papers or those generated in support of this work effort are Government property.

10.2.4 All property and materials associated with these efforts will be coordinated with a Government technical lead and be managed in accordance with the contractor’s property management policies, procedures, practices, and systems.

10.2.5 The contractor will maintain a current inventory of Government Property (including Contractor Acquired Property).

10.2.6 If the contractor wishes to reutilize any government property not meeting the abandonment or destruction criteria of FAR 45.603, the proposed reutilization will be submitted to a government technical lead for concurrence.

11 Data Rights:

The Government will retain unlimited rights to all data and deliverables developed under the SSHINE contract exclusively at Government expense. For all other data, the Government requires Government Purpose Rights (GPR) or better. If the contractor identifies technical data to be delivered with restrictions, the contractor must assert in accordance with DFARS 252.227- 7017. Throughout the period of performance of the contract, records, documents, and associated papers will be available for review at any time per Government request.

12 Location Of Primary Performance

12.2 Performance will primarily be conducted at the Phillips Research Site (PRS) laboratories located at Kirtland AFB, NM. On occasion, work may be performed at Holloman AFB, NM, remote field sites, or other research, integration and launch facilities in the U.S. and/or overseas, as specified in task orders.

12.3 Work accomplished at the Contractor’s facility must maintain the appropriate facility clearance requirements for the work to be performed. In such cases, the Contractor will be responsible for providing adequate facilities, equipment, and support for off-site Contractor personnel. The Government is responsible for all Information Technology (IT) equipment and support (including software licenses) for all Contractor owned and managed activities conducted off-site, or at alternate locations.

12.4 Normal workdays are Monday through Friday except U.S. National Federal Holidays. Normal hours of work are from 0800-1600 daily. The Contractor’s staff typically work eight (8) hours per day, 40 hours per week. All employees are expected to be available during normal hours. The Contractor work hours should not exceed 40 hours per week without express written consent of the CO. This does not preclude the Contractor from performing at other times or days when reasonably necessary to accomplish the objectives described herein. The Contractor personnel working at Government facilities will conform to customer agency normal operating hours. The Contractor personnel are restricted from opening and closing secured areas within the on-site Government facility.

12.5 The Contractor will not have staff present at the Government installation facilities on federal holidays. The federal holidays observed are, as follows: New Year’s Day, Martin Luther King Jr.'s Birthday, Washington's Birthday, Memorial Day, Juneteenth, Independence Day, Labor Day, Columbus Day, Veteran’s Day, Thanksgiving Day, and Christmas Day.

12.6 On occasion, the President has been known to declare a federal holiday on a day that is not recognized in this SOW. If such an occasion arises, the Contractor will support alternate work options for employees according to their corporate policy regarding Government office closures. The Contractor personnel will follow their corporate policy in these situations. Weather and Emergency Situations for On-site Personnel

12.7 The Contractor will support alternate work sites for Contractor personnel during local emergency situations when the Base Commander has declared an emergency and has stated personnel should not report to the Base or should leave the Base during a workday. The Contractor is not authorized to perform any work that may require access to classified information outside of AFRL provided facilities. The Contractor will follow their corporate policy and the guidance of the installation containing their place of performance to determine reporting schedules due to a base closure, inclement weather, or shelter-in-place scenarios.

13 Organizational Conflict of Interest (OCI)

13.2 If during the contract period of performance, the contractor is or becomes aware of any other actual or potential OCI that could impact the SSHINE contract, the contractor will support the Contracting Officer with the complete information as well as address how it will handle the situation in an OCI mitigation plan.

13.3 The Government is aware of potential conflicts of interest in the areas of Small Business Innovative Research (SBIR) contracts. In its role as the SSHINE contractor, a conflicted contractor could influence the selection of technology choices/options away from technologies that compete with a corporate affiliate’s technology (i.e., SBIR technology). If the contractor has active SBIR contracts or plans to compete for future SBIR contracts within AFRL/RV or AFRL/RD, the contractor will provide an OCI mitigation plan addressing how it will ensure that engineering solutions do not favor research conducted under these efforts.