Attachment 7 - DRAFT SSHINE TO 0001 SOW_RVEP.docx

DOCX document 40 KB Posted

Attached to
Space Systems and Hardware Integration for Novel Experiments (SSHINE) Federal contract opportunity
Solicitation number
Industry-2024-RVEP
Issued by
Department of the Air Force Materiel Command Research Laboratory

About this file

This document is a Statement of Work (SOW) for the Space Systems and Hardware Integration for Novel Experiments (SSHINE) Task Order 0001 Prototypes and Flight Experiments (RVEP) under the broader SSHINE contract.

The SOW outlines the contractor's requirements to provide research and development, systems engineering, mission development, assembly, integration and testing (AI&T) capabilities, and program management expertise for large-scale space technology experiments for the Air Force Research Laboratory (AFRL) Space Vehicles Directorate, Integrated Experiments and Evaluation Division. Key requirements include systems engineering support, model-based systems engineering, modeling and simulation, hardware and software design and development, assembly and integration, launch integration support, and facility management. The contractor must also provide monthly status reports and coordinate with other government agencies and contractors as needed. This SOW is part of the broader SSHINE acquisition, which is anticipated to be a Small Business Set-Aside opportunity. The government will host an Industry Day on July 26, 2024 to provide information on the SSHINE requirements and tour the relevant facilities.

View the file

Other files for this federal contract opportunity

Other files attached to Space Systems and Hardware Integration for Novel Experiments (SSHINE), newest first.
File Type Posted
SSHINE Industry Day - All QAs Final 01 Aug 2024.xlsx XLSX spreadsheet
SSHINE Rules of Engagement Industry Day 25 Jul 24.pdf PDF
Industry Day QAs 24 Jul 2024.xlsx XLSX spreadsheet
Industry Day QAs 16 Jul 2026.xlsx XLSX spreadsheet
Attachment 3 - Contents of A Visit Request.pdf PDF
Attachment 6 - DRAFT_SSHINE_SOW.docx DOCX document
Attachment 3 - VisitorForm Kirtland AFB.pdf PDF
Attachment 1 - SSHINE Industry Day Agenda.pptx PPTX presentation
Attachment 4 - Kirtland Map - West.pptx PPTX presentation
Attachment 7 - DRAFT SSHINE TO 0001 SOW RVEP.docx DOCX document
Attachment 7 - DRAFT SSHINE TO 0002 SOW RVEN.docx DOCX document
Attachment 7 - DRAFT SSHINE TO 0003 SOW RVES.docx DOCX document
dd1423 DRAFT.pdf PDF
Attachment 7 - DRAFT SSHINE TO 0004 SOW_RVEX.docx DOCX document
Attachment 2 - Industry Day Registration.pdf PDF
Attachment 8 - DRAFT SSHINE 254.pdf PDF
Attachment 7 - DRAFT SSHINE TO 0004 SOW_RVEX.docx DOCX document
(CUI) Attachment 3 Contents of A Visit Request.pdf PDF
Attachment 7 - DRAFT SSHINE TO 0003 SOW_RVES.docx DOCX document
Attachment 6 - DRAFT SSHINE IDIQ SOW.docx DOCX document
Attachment 1 - SSHINE Industry Day Agenda.pptx PPTX presentation
Attachment 7 - DRAFT SSHINE TO 0002 SOW_RVEN.docx DOCX document
Attachment 4 - Kirtland Map - West.pptx PPTX presentation
Attachment 5 - DD1423 DRAFT CDRLs.pdf PDF
Show all 24

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

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

SPACE SYSTEMS AND HARDWARE INTEGRATION FOR NOVEL EXPERIMENTS (SSHINE)

TASK ORDER 0001

PROTOTYPES AND FLIGHT EXPERIMENTS (RVEP)

STATEMENT OF WORK (SOW)

DD MMM 202X

1.0 Mission and Background

The objective of the Prototypes and Flight Experiments Task Order is to provide the Air Force Research Laboratory (AFRL) Space Vehicles Directorate (RV), Integrated Experiments and Evaluation Division (RVE), Prototypes and Flight Experiments Branch with research and development, systems engineering, mission development, assembly, integration and testing (AI&T) capabilities, and program management expertise for large scale space technology experiments as defined in the basic contract SOW. Additionally, this task order supports upkeep, upgrade, maintenance, and facility management of the Kirtland Spacecraft Integration facility.

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, and Flight Experiment Prototyping, Assembly, Integration, and Testing functional areas as defined in the basic contract SOW, and is expected to require two additional key personnel:

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 will 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 will provide procurement assistance with long lead hardware/software critical to future flight 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 technology transfer planning and decommissioning support, to include planning in support of technology transition to external mission partners.

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

6.1.11.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.11.2 The contractor shall document experimental processes and results to allow third parties to independently reproduce the experiment, research, or analysis effort.

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

6.1.13.1 The monthly status report may be combined with the other monthly status reports referenced in this task order and the basic contract SOW.

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

6.2 Flight Experiment Prototyping, Assembly, Integration, and Testing:

6.2.1 The contractor shall provide direct analytical, technician, and systems engineering support of the RVE Assembly, Integration, and Testing Infrastructure Lead(s).

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

6.2.2.1 User’s guides.

6.2.2.2 Interface Control Documents (ICDs), Specifications.

6.2.2.3 Test Processes/Procedures.

6.2.2.4 Safety Plans.

6.2.2.5 Risk Management Plans.

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

6.2.2.7 Reliability, operability, interoperability, and performance assessments.

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

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

6.2.3.1.1 Hardware development and integration.

6.2.3.1.2 Hardware testing and experimentation.

6.2.3.1.3 Technology transition support.

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

6.2.3.2.1 Modifying existing software/firmware.

6.2.3.2.2 Writing and documenting new code.

6.2.3.2.3 Integrating and testing new or modified code.

6.2.3.2.4 Maintaining software and related databases.

6.2.3.2.5 Software configuration management.

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

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

6.2.3.3.2 Arrangement of equipment and logistics for the test effort.

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

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

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

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

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

6.2.4 The contractor shall provide assembly and integration support, including:

6.2.4.1 Space technology assembly and integration support.

6.2.4.2 Government integration facility management, including personnel training, facility security, and safety compliance.

6.2.4.3 Spacecraft bus, payload, and experiment assembly and integration within government facilities.

6.2.4.4 High-altitude balloon, payload, and experiment assembly and integration within government facilities.

6.2.4.5 Assistance with hardware/software procurement and other direct costs during assembly and integration.

6.2.4.6 Maintenance and upgrade support for government integration facility capabilities.

6.2.4.7 The contractor shall provide documentation and laboratory safety instruction (e.g. vehicle operations, crane operations, hazardous materials, waste management, explosives, laser radiation, welding, cutting, brazing, chemicals, and electrostatic discharge) in accordance with the Programmatic Environmental Safety and Health Evaluation Plan.

6.2.4.8 The contractor shall identify and provide recommendations to the Government for addressing hazardous situations found in workspaces, manufacturing areas, test facilities, integration areas, storage facilities, pre-launch areas, launch facilities, and post-launch processing.

6.2.4.9 Research, development, and planning for future space system assembly, integration, and testing needs, objective, and programs. Including:

6.2.4.9.1 New assembly, integration, and testing capabilities.

6.2.4.9.2 Planning tools.

6.2.4.9.3 Test operation, plans, and concepts.

6.2.4.9.4 Data reduction, analysis, and reporting tools.

6.2.5 The contractor will provide flight experiment launch integration support, including:

6.2.5.1 Support of integration studies, interface control documents, and briefings.

6.2.5.2 Packing, protecting, and shipping flight experiment and support equipment to the launch site.

6.2.5.3 Support of hardware and software integration efforts in preparation for flight experiment launch, including mechanical installation, functional testing, blanketing, fueling, inspection, fairing closeout, range safety procedures, and day of launch processes.

6.2.5.4 Support of post launch anomaly resolution, telemetry archiving and analysis, as and documentation.

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

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

6.2.9.1 The monthly status report may be combined with the other monthly status reports referenced in this task order and the basic contract SOW.

6.2.9.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 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. These functions may be performed by one or more qualified persons.

7.1.1.1 Facility Management.

7.1.1.1.1 Fuel Tank Custodian in accordance with 377 Mission Support Group training requirements.

7.1.1.1.2 Chemical Hygiene Officer in accordance with AFI 90-821.

7.1.1.1.3 Hazard Communication Program Manager in accordance with 29 CFR 1910.1200.

7.1.1.1.4 Unit Safety Representative in accordance with AFI 91-202.

7.1.1.2 Security Assistant.

7.1.1.2.1 Alarm Custodian in accordance with 377 Security Forces Group requirements.

7.1.1.2.2 General Services Administration Security Container Custodian in accordance with 18 CFR 3a.61.

6.0Security Requirements
6.1Clearance Requirements: The contractor shall establish and implement information and physical security programs governing their efforts in accordance with the Basic Contract DD254 Contract Security Classification Specification. At a minimum, contractor personnel shall be eligible to obtain a Top-Secret Clearance.
7.0Associate Contractor Agreements
7.1The 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.
8.0Deliverables

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.

File details come from the government source that posted it. Updated .