Attachment 7 - DRAFT SSHINE TO 0004 SOW_RVEX.docx

STATEMENT OF WORK: SPACE SOLAR POWER INCREMENTAL DEMONSTRATIONS & RESEARCH (SSPIDR)

SPACE SYSTEMS AND HARDWARE INTEGRATION FOR NOVEL EXPERIMENTS (SSHINE)

TASK ORDER 0004

RAPID ARCHITECTURE PROTOTYPING AND INTEGRATION DEVELOPMENT (RVEX)

STATEMENT OF WORK (SOW)

DD MMM 202X

1.0 Mission and Background

The objective of the Rapid Architecture Prototyping and Integration Development Task Order is to provide the Air Force Research Laboratory (AFRL) Space Vehicles Directorate (RV), Integrated Experiments and Evaluation Division (RVE), Rapid Architecture Prototyping and Integration Development Branch with research and development, systems engineering, mission development, modeling and simulation, and flight operations support for both large and small space technology experiments as defined in the basic contract SOW.

2.0 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.0 Compliance and Reference Documents

Compliance and Reference Documents are listed in the basic contract SOW.

4.0 Requirements

The following requirements are applicable to the listed RVE functional areas in section 2. 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 AFRL/RVE integration and test programs.

4.0 5.0 6.0

6.1 Mission and Space System Development.

6.1.1 The contractor shall provide direct technical and systems engineering support to RVE Program Managers, Deputy Program Managers, Chief Engineers, Systems Engineers, or other designated program leads.

6.1.2 The contractor shall provide systems engineering and analytical support to AFRL mission and space system designs.

6.1.2.1 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:

6.1.2.1.1 Refinement of programmatic objectives into actionable requirements.

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

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

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

6.1.2.3 The contractor shall provide 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).

6.1.3 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:

6.1.3.1 Development of MBSE models.

6.1.3.2 Evaluation of models delivered by outside performers.

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

6.1.4 The contractor will provide modeling and simulation support, including:

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

6.1.4.2 Testing and operation of modeling and simulation capabilities.

6.1.4.3 Analyses comparing model and simulation results to experimental findings.

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

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

6.1.6 The contractor will provide Hardware/Software-in-the-Loop and Cloud Computing Architecture development and administration.

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

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

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

6.1.6.4 Design and implementation of software tools.

6.1.6.4.1 Modifying existing software/firmware.

6.1.6.4.2 Writing and documenting new code.

6.1.6.4.3 Integrating and testing new or modified code.

6.1.6.4.4 Maintaining software and related databases.

6.1.6.4.5 Software configuration management.

6.1.6.5 Physical and cloud-based system maintenance.

6.1.6.6 Procurement of cloud computing access and storage.

6.1.6.6.1 Support of RVE disaggregated development networks

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

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

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

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

6.1.9.1 The contractor shall have the ability to procure available commercial and non-commercial space-rated/grade related hardware.

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

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

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

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

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

6.1.13 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 RVE integration and test programs.

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

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

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

6.2 Space Experiment Prototyping, Assembly, Integration, and Testing.

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

6.2.1.1 User’s guides.

6.2.1.2 Interface Control Documents (ICDs), Specifications.

6.2.1.3 Test Processes/Procedures.

6.2.1.4 Safety Plans.

6.2.1.5 Risk Management Plans.

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

6.2.1.7 Reliability, operability, interoperability, and performance assessments.

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

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

6.2.2.1.1 Hardware development and integration.

6.2.2.1.2 Hardware testing and experimentation.

6.2.2.1.3 Technology transition support.

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

6.2.2.2.1 Modifying existing software/firmware.

6.2.2.2.2 Writing and documenting new code.

6.2.2.2.3 Integrating and testing new or modified code.

6.2.2.2.4 Maintaining software and related databases.

6.2.2.2.5 Software configuration management.

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

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

6.2.2.3.2 Arrangement of equipment and logistics for the test effort.

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

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

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

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

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

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

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

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

6.2.5 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 RVE integration and test programs.

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

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

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

5.0 Contract Management

The contractor shall perform contract requirements in accordance with the basic contract SOW.

7.0

7.1 Key Personnel.

7.1.1 The functions below are considered essential to the work being performed on contract in addition to those required by the basic contract SOW.

7.1.1.1 Lead Cybersecurity Engineer

7.1.1.1.1 5+ years cybersecurity experience on complex defense systems leveraging Risk Management Framework

7.1.1.1.2 Active Top Secret SCI clearance

7.1.1.1.3 Required Certification: Security+ or similar, as well as demonstration of continued education.

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

8.0

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

9.0 Base Support

The Government shall provide base laboratory support in accordance with basic contract SOW.

10. Government Property/Contractor Acquired Property 1.0 2.0 3.0 4.0 5.0 6.0 7.0 8.0 9.0 10.0

10.1 Contractor Procured/Acquired Property: 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.1.1 Purchases must be authorized by a Government Technical Lead.

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

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

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

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

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

11.0 Organizational Conflict of Interest (OCI)

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.