Attachment 8 - SSHINE TO 04 SOW RVEX .docx

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

SPACE SYSTEMS AND HARDWARE INTEGRATION FOR NOVEL EXPERIMENTS (SSHINE)

TASK ORDER 0004

RAPID ARCHITECTURE PROTOTYPING AND INTEGRATION DEVELOPMENT (RVEX)

STATEMENT OF WORK (SOW)

12 Jul 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 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 shall provide direct technical and systems engineering support to the RAPID Lead, Program Manager, Deputy Program Manager(s), Engineering Lead, Systems Engineers, or other designated program leads.

4.1.2. The contractor shall provide systems engineering and analytical support to RAPID mission and space system designs.

4.1.3. The contractor will aid in the development of government 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 shall perform analyses and evaluations accomplished through relevant experimental testing, modeling and simulation, and engineering analysis.

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

4.1.6. The contractor will provide 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 RAPID objectives.

4.1.7. The contractor will provide modeling and simulation support, including:

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

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 provide Systems Engineering, including mechanical, thermal, electrical, structural, software, security, and other specialized engineering to support mission development for space technology, spacecraft, and high-altitude balloon experiment designs.

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

4.1.10. Design and implementation of software tools.

4.1.10.1. Modifying existing software/firmware.

4.1.10.2. Writing and documenting new code.

4.1.10.3. Integrating and testing new or modified code.

4.1.10.4. Maintaining software and related databases.

4.1.10.5. Software configuration management.

4.1.11. Physical system maintenance.

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

4.1.13. The contractor shall assist in the development of space technology and laboratory, ground and flight experiment requirements, design, and interface control documentation.

4.1.14. The contractor shall assist with program management, including attendance at technical meetings, reviews, off-sites, or technical conferences.

4.1.15. The contractor shall provide procurement assistance with hardware/software critical to future experiment program success.

4.1.16. The contractor shall have the ability to procure available commercial and non-commercial consumer-grade, industry-grade, military-grade, and/or space-rated hardware/software as appropriate.

4.1.17. The contractor shall provide procurement assistance with miscellaneous tasks such as trade studies, demonstrations and various analysis as directed by the Government Program Manager.

4.1.18. The contractor shall provide technology transfer planning and decommissioning support, to include planning in support of technology transition to external mission partners.

4.1.19. The contractor shall design and fabricate ground-based proofs-of-concept, experiments, and demonstrations.

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

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

4.1.22. The contractor shall 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.23. The contractor shall prepare monthly status reports on activity under the scope of section 4.1 and document lessons learned.

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

4.1.25. The contractor 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 shall draft, prepare, revise, and review design documentation including, but not limited to:

4.2.2. User’s guides.

4.2.3. Interface Control Documents (ICDs), Specifications.

4.2.4. Test Processes/Procedures.

4.2.5. Safety Plans.

4.2.6. Risk Management Plans.

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

4.2.8. Reliability, operability, interoperability, and performance assessments.

4.2.9. The contractor shall provide full life-cycle technology implementation support, including:

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

4.2.9.1.1. Hardware development and integration.

4.2.9.1.2. Hardware testing and experimentation.

4.2.9.2. Technology transition support.

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

4.2.10.1. Modifying existing software/firmware.

4.2.10.2. Writing and documenting new code.

4.2.10.2.1. Integrating and testing new or modified code.

4.2.10.2.2. Maintaining software and related databases.

4.2.10.2.3. Software configuration management.

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

4.2.12. Ground/laboratory test planning and procedures development, test design and fabrication, test preparation and coordination.

4.2.12.1. Arrangement of equipment and logistics for the test effort.

4.2.13. Systems-level tests to evaluate performance of spacecraft, balloon, and ground systems/subsystems.

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

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

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

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

4.2.16. The contractor shall support the Government in shipping and receiving of experiment and assembly, integration, and testing hardware/software.

4.2.17. Surge Capability: For the purposes of this contract, surge capability refers to the ability to meet requirements when mission needs have exceeded baseline resource capacity. This may occur as a result of in-scope changes or extending task periods of performance, as well as short-term labor fluctuations due to unanticipated increases in concept development, mission design, integration, test, delivery, or operations requirements.

4.2.18. The contractor shall have the ability to provide a surge capability to meet requirements of section 4.2 within unexpected or tightened program constraints.

4.2.18.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.19. The contractor shall 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.20. The contractor shall prepare monthly status reports on activity under the scope of section 4.2 and document lessons learned.

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

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

4.3. Ground-Based Demonstrations, Experiments, and Supporting Network/Communications Infrastructure.

4.3.1. The contractor shall provide direct IT and network engineering support to RAPID facilities and team members.

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

4.3.3. The contractor shall provide direct technical and network engineering support for prototyping and communications experiments.

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

5. Contract Management The contractor shall perform contract requirements in accordance with the basic contract SOW (Section 4.0 Contract Management).

6. 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 4.2 Personnel Management):

6.1. SYSTEM ENGINEER (MID-LEVEL)

6.1.1. 5+ years of systems engineering experience on complex defense systems (communications systems is highly preferred)

6.1.2. Active Top Secret SCI clearance

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

6.2. TEST ENGINEER (MID-LEVEL)

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

6.2.2. Active Top Secret SCI clearance

6.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.

6.3. FACILITY IT MANAGER (MID-LEVEL)

6.3.1. 5+ years of experience managing and maintaining government IT systems

6.3.2. Active Top Secret SCI clearance

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

7. Security Requirements

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

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

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

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

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

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

11. Government Property/Contractor Acquired Property

11.1. 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:

11.1.1. Purchases must be authorized by a Government Technical Lead.

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

11.1.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.

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

11.1.5. The contractor shall maintain a current inventory of Government Property (including Contractor Acquired Property).

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

12. Data Rights:

The Government shall 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 shall be available for review at any time per Government request.

13. LOCATION OF PRIMARY PERFORMANCE

13.1. Performance shall 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.

13.2. 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 shall 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.

13.3. 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 shall conform to customer agency normal operating hours. The Contractor personnel are restricted from opening and closing secured areas within the on-site Government facility.

13.4. The Contractor shall 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.

13.5. On occasion, the President has been known to declare a federal holiday on a day that is not recognized in this PWS. If such an occasion arises, the Contractor shall provide 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

13.6. The Contractor will provide 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 shall 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.

14. ORGANIZATIONAL CONFLICT OF INTEREST (OCI)

14.1. 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 shall provide the Contracting Officer with the complete information as well as address how it will handle the situation in an OCI mitigation plan.

14.2. 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 shall provide an OCI mitigation plan addressing how it will ensure that engineering solutions do not favor research conducted under these efforts.

14.3. 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 shall provide the Contracting Officer with the complete information as well as address how it will handle the situation in an OCI mitigation plan.