Attachment 7 - SSHINE TO 03 SOW RVES.docx

SPACE SYSTEMS AND HARDWARE INTEGRATION FOR NOVEL EXPERIMENTS (SSHINE)

TASK ORDER 0003

SIMULATION AND TECHNOLOGY ASSESSMENT (RVES)

STATEMENT OF WORK (SOW)

25 Jun 2024

1.0 Mission and Background

The objective of the Simulation and Technology Assessment Task Order is to provide the Air Force Research Laboratory (AFRL) Space Vehicles Directorate (RV), Integrated Experiments and Evaluation Division (RVE), Simulation and Technology Assessment Branch (RVES) 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 statement of work. Additionally, this task order supports upkeep, upgrade, maintenance, and facility management of RVE Mission Operations Centers.

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, Flight Experiment Operations functional areas as defined in the basic contract statement of work.

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 flight 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 shall assist in the development of space technology and flight experiment requirements, design, and interface control documentation.

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

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

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

6.1.10.1 The monthly status report may be combined with the other monthly status reports referenced in this task order and the basic contract statement of work.

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

6.2 Flight Experiment Operations.

6.2.1 The contractor shall provide direct analytical, systems engineering, and technical support of the RVE Operations Cadre lead, or mission-specific operations lead as delegated

6.2.2 The contractor shall provide flight experiment mission and operations planning including:

6.2.2.1 Procedure development for all phases of the mission.

6.2.2.2 CONOPS development.

6.2.2.3 Launch and Early Operations (LEOps) plan

6.2.2.4 Operational testing via simulator (to include setup, configuration, and use of various virtual simulations and flatsats).

6.2.2.5 Ground system testing to include operations acceptance testing, factory compatibility tests, and launch-base compatibility tests.

6.2.2.6 Mission operations center planning to include facility planning, layout, and preparation.

6.2.2.7 Training material generation to support crew readiness events.

6.2.2.8 Coordination with systems team on various operational documents such as launch and early orbit

6.2.2.9 Participation in events such as day in the life tests, exercises, rehearsals, and mission dress rehearsals as an operator, systems expert, or mission planner (see section 2.1.3.2.3).

6.2.2.10 Completion of required AFRL training to certify as a member of the flight operations team. Assume ~8 hours of classroom training, 8 hours of practical training, and ~40 hours of on-console event training spread across ~6 months.

6.2.2.11 Participation in (and leading as appropriate) various operations IPT’s on a weekly basis.

6.2.2.12 Participation in a weekly Ops Cadre internal meeting.

6.2.2.13 Software tool development and test in support of operational needs.

6.2.2.14 Development of automatic functions or scripts to support operations as required.

6.2.2.15 Completion and coordination of on-boarding actions associated with various antenna networks including both SCN, commercial, and AFRL networks.

6.2.2.16 Assisting the operations lead in crew logistics management such as badging, entry-access lists, 2875 account creation, and training event planning.

6.2.3 The contractor shall directly support flight operations, including:

6.2.3.1 Spacecraft on-orbit operations and experimentation including on-call support as required.

6.2.3.1.1 Reference section 2.1.2.7 for completion of required training for certification purposes.

6.2.3.1.2 The minimum number of shifts per month for currency will be tracked and adhered to.

6.2.3.1.3 Operations may include (but not limited to): Antenna resource scheduling, vehicle planning, systems support, command block building, command block verification, and release of commands to the vehicle at the direction of a government flight director.

6.2.3.2 Operations acceptance testing to include regression testing of new operational components and processes.

6.2.3.3 Development of forward-looking anomaly prediction and detection algorithms and software.

6.2.3.4 Development of historical data aggregation and trending analysis algorithms and software.

6.2.3.5 Development of vehicle fault detection reporting systems.

6.2.3.6 Support configuration management processes of procedures, scripts, vehicle tables, vehicle parameters, vehicle fault detection and response trees, and ground software items throughout the life of the mission.

6.2.3.7 Anomaly resolution support and reporting.

6.2.3.8 In the event the government requests a root cause analysis for a specific issue occurring during operations, the contractor shall produce within 30 days of notice the following:

6.2.3.8.1 A root cause analysis by an independent party to collect and document information leading up to failure including identifying contributing factors, identifying a mitigation plan, and providing other recommendations as needed.

6.2.4 The contractor shall provide support to government technology transfer efforts, including:

6.2.4.1 Training of external mission partners on flight operations.

6.2.4.2 Technical reach back support for mission partners after technology transition.

6.2.4.3 The contractor shall provide documentation for all systems engineering activities related to transition of flight assets to operational users.

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

6.2.5.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.6 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.7 The contractor shall travel to conduct work covered under section 4.3 at other laboratories, field locations, test ranges, other Government locations, and other industry locations.

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

6.2.8.1 The monthly status report may be combined with the other monthly status reports referenced in this task order and the basic contract statement of work.

6.2.8.2 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 statement of work.

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