SSHINE TO 02 RVEN SOW 10 Sep 2024.docx
DOCX document 55 KB Posted
- Attached to
- Space Systems and Hardware Integration for Novel Experiments (SSHINE) Federal contract opportunity
- Solicitation number
- FA9453-24-R-X006
About this file
The document is a Statement of Work (SOW) for the Space Systems and Hardware Integration for Novel Experiments (SSHINE) Task Order 0002 under the Small Satellite Portfolio (RVEN). The SOW outlines the requirements for the contractor 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. Key requirements include supporting the development of government flight experiment and space technology requirements, Model Based Systems Engineering (MBSE), modeling and simulation, Systems Engineering, procurement assistance, technology transfer planning, space experiment prototyping and AI&T, flight experiment operations, and ground system development. The contractor must have personnel with Top-Secret Clearance with SCI and SAP accesses. The SOW is part of the overall SSHINE contract opportunity being solicited by the Air Force Research Laboratory (AFRL) Space Vehicles Directorate.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| Attachment 3 - SSHINE SOW Supplemental Requirements.docx | DOCX document | |
| Solicitation - FA945324RX006.pdf | ||
| Draft CDRLs 19 Sep 24.pdf | ||
| SSHINE IDIQ SOW 10 Sep 24.docx | DOCX document | |
| SSHINE TO 01 RVEP SOW 10 Sep 24.docx | DOCX document | |
| SSHINE TO 03 RVEX SOW 10 Sep 24.docx | DOCX document | |
| Solicitation - FA945324RX006.pdf | ||
| Attachment 7 - SSHINE TO 03 SOW RVES.docx | DOCX document | |
| Attachment 5 - SSHINE TO 01 SOW RVEP.docx | DOCX document | |
| Attach 1 SSHINE 254 (CO Signed).pdf | ||
| Attachment 6 - SSHINE TO 02 SOW RVEN.docx | DOCX document | |
| Comment Resolution Matrix - Draft RFP 29 Aug 2024 (SSHINE) (Blank).xlsx | XLSX spreadsheet | |
| Attachment 4 - SSHINE IDIQ SOW.docx | DOCX document | |
| Attachment 3 - SSHINE SOW Supplemental Requirements.docx | DOCX document | |
| Attachment 8 - SSHINE TO 04 SOW RVEX .docx | DOCX document | |
| dd1423 DRAFT.pdf |
Show all 16
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
SPACE SYSTEMS AND HARDWARE INTEGRATION FOR NOVEL EXPERIMENTS (SSHINE)
TASK ORDER 0002
SMALL SATELLITE PORTFOLIO (RVEN)
STATEMENT OF WORK (SOW)
10 Sep 2024
1.0 Mission and Background
The objective of the Small Satellite Portfolio Task Order is to provide the Air Force Research Laboratory (AFRL) Space Vehicles Directorate (RV), Integrated Experiments and Evaluation Division (RVE), Small Satellites Portfolio 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 RVE Ground System Capabilities.
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, Ground 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.1 | The contractor will support 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.1 | Refinement of programmatic objectives into actionable requirements. | |
| 4.1.2 | Analyses and documentation for laboratory, range, ground, near-space, and/or space flight experiments. | |
| 4.1.2.1 | Iteration of requirements, flow-downs, concept of operations; the refining of objectives; and interface management. | |
| 4.1.2.2 | The contractor will support analyses and evaluations accomplished through relevant experimental testing, modeling and simulation, and engineering analysis. | |
| 4.1.2.3 | The contractor will support documentation tasks 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.3 | 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.3.1 | Development of MBSE models. | |
| 4.1.3.2 | Evaluation of models delivered by outside performers. | |
| 4.1.3.3 | Exercise and test of models in support of RVE objectives. | |
| 4.1.4 | The contractor will support modeling and simulation tasks, including: | |
| 4.1.4.1 | Development of modeling capabilities to simulate, emulate and evaluate technology options identified by RVE. | |
| 4.1.4.2 | Testing and operation of modeling and simulation capabilities. | |
| 4.1.4.3 | Analyses comparing model and simulation results to experimental findings. | |
| 4.1.4.4 | Analyses identifying requirement shortfalls, missing functionality, and model improvements. | |
| 4.1.5 | 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.6 | The contractor will support comprehensive cybersecurity and information assurance tasks, including compliance with Department of Defense (DoD) risk management frameworks, and other security requirements. | |
| 4.1.7 | The contractor will support in the development of space technology and flight experiment requirements, design, and interface control documentation. | |
| 4.1.8 | The contractor will support program management tasks, including attendance at technical meetings, reviews, off-sites, or technical conferences. | |
| 4.1.9 | The contractor will support procurement assistance with long lead hardware/software critical to future flight experiment program success. | |
| 4.1.9.1 | The contractor will have the ability to support the procurement of available commercial and non-commercial space-rated/grade related hardware. | |
| 4.1.9.2 | Reserved. | |
| 4.1.10 | The contractor will support technology transfer planning and decommissioning tasks, to include planning in support of technology transition to external mission partners. | |
| 4.1.11 | The contractor will support the design and fabrication ground-based proofs-of-concept, experiments, and demonstrations. | |
| 4.1.11.1 | The contractor will support the documentation of data acquisition, processing, analysis, and modeling/simulation tools to be used in the experiment, research, or analysis effort for evaluations. | |
| 4.1.11.2 | The contractor will support the documentation of experimental processes and results to allow third parties to independently reproduce the experiment, research, or analysis effort. | |
| 4.1.12 | The contractor will support direct analytical, systems engineering, and administrative tasks to the University Nanosatellite Program (UNP). | |
| 4.1.12.1 | The contractor will support lead event planning, venue rental/booking, and procurements for UNP activities. | |
| 4.1.13 | 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.1.14 | The contractor will prepare monthly status reports on activity under the scope of section 4.1 and document lessons learned. | |
| 4.1.14.1 | The monthly status report may be combined with the other monthly status reports referenced in this task order and the basic contract SOW. | |
| 4.1.14.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.0 | Reserved. | |
| 4.2.1 | The contractor will draft, prepare, revise, and review design documentation including, but not limited to: | |
| 4.2.1.1 | User’s guides. | |
| 4.2.1.2 | Interface Control Documents (ICDs), Specifications. | |
| 4.2.1.3 | Test Processes/Procedures. | |
| 4.2.1.4 | Safety Plans. | |
| 4.2.1.5 | Risk Management Plans. | |
| 4.2.1.6 | Attendance and participation in programmatic, technical and safety reviews. | |
| 4.2.1.7 | Reliability, operability, interoperability, and performance assessments. | |
| 4.2.2 | The contractor will support full life-cycle technology implementation tasks, including: | |
| 4.2.2.1 | Space technology, spacecraft, and high-altitude balloon flight hardware design and fabrication. | |
| 4.2.2.1.1 | Hardware development and integration. | |
| 4.2.2.1.2 | Hardware testing and experimentation. | |
| 4.2.2.1.3 | Technology transition support. | |
| 4.2.2.2 | Space technology, spacecraft, and high-altitude balloon flight software/firmware design and development. | |
| 4.2.2.2.1 | Modifying existing software/firmware. | |
| 4.2.2.2.2 | Writing and documenting new code. | |
| 4.2.2.2.3 | Integrating and testing new or modified code. | |
| 4.2.2.2.4 | Maintaining software and related databases. | |
| 4.2.2.2.5 | Software configuration management. | |
| 4.2.2.3 | Laboratory research, test and assessment design, technology validation testing and experimentation. | |
| 4.2.2.3.1 | Ground/laboratory test planning and procedures development, test design and fabrication, test preparation and coordination. | |
| 4.2.2.3.2 | Arrangement of equipment and logistics for the test effort. | |
| 4.2.2.3.3 | Systems-level tests to evaluate performance of spacecraft, balloon, and ground systems/subsystems. | |
| 4.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. | |
| 4.2.2.3.5 | Documented data acquisition, processing, analysis, and modeling/simulation tools to be used in a technology validation effort. | |
| 4.2.2.3.6 | Documenting experimental processes and results to allow third parties to independently reproduce the evaluation effort. | |
| 4.2.2.4 | Re-engineering and re-design of software and hardware after testing. | |
| 4.2.3 | The contractor will support assembly and integration tasks, including: | |
| 4.2.3.1 | Space technology assembly and integration support. | |
| 4.2.3.2 | Government integration facility management, including personnel training, facility security, and safety compliance. | |
| 4.2.3.3 | Spacecraft bus, payload, and experiment assembly and integration within government facilities. | |
| 4.2.3.4 | High-altitude balloon, payload, and experiment assembly and integration within government facilities. | |
| 4.2.3.5 | Assistance with hardware/software procurement and other direct costs during assembly and integration. | |
| 4.2.3.6 | The contractor will 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. | |
| 4.2.3.7 | The contractor will 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. | |
| 4.2.4 | The contractor will support flight experiment launch integration tasks, including: | |
| 4.2.4.1 | Support of integration studies, interface control documents, and briefings. | |
| 4.2.4.2 | Packing, protecting, and shipping flight experiment and support equipment to the launch site. | |
| 4.2.4.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. | |
| 4.2.4.4 | Support of post launch anomaly resolution, telemetry archiving and analysis, as and documentation. | |
| 4.2.5 | The contractor will support the Government in shipping and receiving of flight experiment and assembly, integration, and testing hardware/software. | |
| 4.2.6 | 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.6.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.7 | 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.2.8 | The contractor will prepare monthly status reports on activity under the scope of section 4.2 and document lessons learned. | |
| 4.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 SOW. | |
| 4.2.8.2 | The contractor will present monthly status reports and lessons learned to internal and/or external audiences as directed by the government. | |
| 4.3 | Flight Experiment Operations. | |
| 4.3.1 | The contractor will support direct analytical, systems engineering, and technical tasks of the RVE Operations Cadre lead, or mission-specific operations lead as delegated | |
| 4.3.2 | The contractor will support flight experiment mission and operations planning including: | |
| 4.3.2.1 | Procedure development for all phases of the mission. | |
| 4.3.2.2 | CONOPS development. | |
| 4.3.2.3 | Launch and Early Operations (LEOps) plan | |
| 4.3.2.4 | Operational testing via simulator (to include setup, configuration, and use of various virtual simulations and flatsats). | |
| 4.3.2.5 | Ground system testing to include operations acceptance testing, factory compatibility tests, and launch-base compatibility tests. | |
| 4.3.2.6 | Mission operations center planning to include facility planning, layout, and preparation. | |
| 4.3.2.7 | Training material generation to support crew readiness events. | |
| 4.3.2.8 | Coordination with systems team on various operational documents such as launch and early orbit | |
| 4.3.3 | Participation in events such as day in the life tests, exercises, rehearsals, and mission dress rehearsals as an operator, systems expert, or mission planner. | |
| 4.3.3.1 | 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. | |
| 4.3.3.2 | Participation in (and leading as appropriate) various operations IPT’s on a weekly basis. | |
| 4.3.3.3 | Participation in a weekly Ops Cadre internal meeting. | |
| 4.3.3.4 | Software tool development and test in support of operational needs. | |
| 4.3.3.5 | Development of automatic functions or scripts to support operations as required. | |
| 4.3.3.6 | Completion and coordination of on-boarding actions associated with various antenna networks including both SCN, commercial, and AFRL networks. | |
| 4.3.3.7 | Assisting the operations lead in crew logistics management such as badging, entry-access lists, 2875 account creation, and training event planning. | |
| 4.3.4 | The contractor will directly support flight operations, including: | |
| 4.3.4.1 | Spacecraft on-orbit operations and experimentation including on-call support as required. | |
| 4.3.4.1.1 | Reference section 4.3.3.1 for completion of required training for certification purposes. | |
| 4.3.4.1.2 | The minimum number of shifts per month for currency will be tracked and adhered to. | |
| 4.3.4.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. | |
| 4.3.4.2 | Operations acceptance testing to include regression testing of new operational components and processes. | |
| 4.3.4.3 | Development of forward-looking anomaly prediction and detection algorithms and software. | |
| 4.3.4.4 | Development of historical data aggregation and trending analysis algorithms and software. | |
| 4.3.4.5 | Development of vehicle fault detection reporting systems. | |
| 4.3.4.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. | |
| 4.3.4.7 | Anomaly resolution support and reporting. | |
| 4.3.4.8 | In the event the government requests a root cause analysis for a specific issue occurring during operations, the contractor will produce within 30 days of notice the following: | |
| 4.3.4.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. | |
| 4.3.5 | The contractor will support government technology transfer tasks, including: | |
| 4.3.5.1 | Training of external mission partners on flight operations. | |
| 4.3.5.2 | Technical reach back support for mission partners after technology transition. | |
| 4.3.5.3 | The contractor will prepare documentation for all systems engineering activities related to transition of flight assets to operational users. | |
| 4.3.6 | The contractor will have the ability to support a surge capability to meet requirements of section 4.3 within unexpected or tightened program constraints. | |
| 4.3.6.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.3.7 | 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.3.8 | The contractor will travel to conduct work covered under section 4.3 at other laboratories, field locations, test ranges, other Government locations, and other industry locations. | |
| 4.3.9 | The contractor will prepare monthly status reports on activity under the scope of section 4.3 and document lessons learned. | |
| 4.3.9.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. | |
| 4.3.9.2 | The contractor will present monthly status reports and lessons learned to internal and/or external audiences as directed by the government. | |
| 4.4 | Ground System Development. | |
| 4.4.1 | The contractor will support direct analytical, systems engineering, and software development tasks to the RVE Ground Systems efforts. | |
| 4.4.2 | The contractor will support ground system infrastructure development and testing, including: | |
| 4.4.2.1 | Design and implementation of software tools. | |
| 4.4.2.1.1 | Modifying existing software/firmware. | |
| 4.4.2.1.2 | Writing and documenting new code. | |
| 4.4.2.1.3 | Integrating and testing new or modified code. | |
| 4.4.2.1.4 | Maintaining software and related databases. | |
| 4.4.2.1.5 | Software configuration management. | |
| 4.4.2.1 | Management of agile and emerging division directed ground system requirements. | |
| 4.4.3 | The contractor will support the development of 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.2.1 | Support of RVE disaggregated development network | |
| 4.4.3.2.2 | Support RVE ability to contract with other commercial ground stations for mission support. | |
| 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 may be combined with the other monthly status reports referenced in this task order and the basic contract SOW. | |
| 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. |
5.0 Contract Management
The contractor will perform contract requirements in accordance with the basic contract SOW.
| 6.0 | Security Requirements |
| 6.1 | Clearance Requirements: The contractor will 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 will be eligible to obtain a Top-Secret Clearance with SCI and SAP accesses. Access to SIPR, JWICS and other classified systems as required. |
| 7.0 | Associate Contractor Agreements |
| 7.1 | 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.0 | Deliverables |
The contractor will deliver all deliverables in accordance with the Contract Data Requirements List (CDRLs) defined in the basic SOW.
9.0 Base Support
The Government will provide base laboratory support in accordance with basic contract SOW.
| 10. | Government Property/Contractor Acquired Property |
| 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 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.1.5 | The contractor will 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 will 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 will 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 .