ROOSTER-6 Integration & Support RFI

Description

{"description":" Please see the attached document titled Rooster 6 Integration Support in Attachments for full description and Instructions to responders: \n\n \n SCOPE AND DEFINITIONS: \nSpace Systems Command (SSC), SYD-89 Capability Development System Program Manager (SPM) \n(SSC/SYD89/SYA) is soliciting information about potential sources for the ROOSTER-6 Integration & \nSupport Contract, to perform the integration of a secondary payload ring/platform capable of hosting \nmultiple payloads to support national security missions. The integration of payloads will be for mission \nsets spanning across SSC and potentially other USSF or DoW partners. Missions can vary from \nexperimental/prototyping to operational. These platforms will launch on National Security Space Launch \n(NSSL) missions and can include payloads up to the highest classified levels. The Government seeks \ninformation on existing integration expertise with the ESPAStar-D platform and integrating multiple \nmission payloads and associated acquisition/contract structure, technical, cost, and schedule feasibility. \nTwo types of payloads are expected to be manifested on the platforms furnished to the ROOSTER-6 \nIntegration & Support Contract: 1) on-orbit separable payloads, and 2) on-orbit non-separable payloads. \nThe two types of payloads intended for integration as well as any encryption devices (if needed) will be \nprovided as Government Furnished Equipment (GFE). Separable payloads are integrated on to the multimission \nhost ring/platform and are deployed days to months after launch. The specific port that the \npayload will be “fully integrated” into will be on a Northrup Grumman built ESPAStar-D class secondary \npayload ring. Non-separable payloads are integrated on the host ring/platform and remain with it for the \nentire mission duration. The term “fully integrated” is used to describe a platform with payloads \nmounted and integrated into available secondary payload ring ports and fully tested at the system (ring) \nlevel. \n\n \n CAPABILITY REQUIREMENT: \nSYD 89/SYA seeks an experienced integrator for this flexible and modular propulsive host satellite \nring/platform that will accommodate multiple payloads (separable and hosted) in support of different \nmission sets primarily in a GEO Orbit. The capability to operate in other orbital regimes is also under \nconsideration. The host ring/platform will have a minimum operational design life of 2 years. These \nmissions will be launched on NSSL missions as part of an Integrated Payload Stack (IPS) that is expected \nto include other spacecraft or payload adapters. As part of the launch manifest, integrated vehicles must \nmeet all launch safety requirements including coupled loads analysis, thermal analysis, and testing to \nactual or forecasted launch environments. The propulsive host ring/platform shall at a minimum be \ncapable of hosting six ESPAStar-D Class Payloads. Functional testing of the integrated propulsive host \nvehicle in a simulated space environment is also expected. Support for workarounds, such as testing with \npayload mass simulators, is expected to accommodate payloads that will not arrive until processing at the \nlaunch site. The propulsive host ring/platform structure is intended for attachment and separation from the \nlaunch vehicle Payload Attachment Fitting (PAF) or another payload adapter of the same size. Once \nseparated from the launch vehicle, the multi-mission host ring/platform must support separable payloads \nuntil they are deployed into their intended orbits and continue to support non-separable payloads for \nmission duration. \n\n \n GENERAL DESCRIPTION OF WORK REQUIRED: \nPayloads may have greatly differing mission sets, which will create a wide range of different \nrequirements for each. Generally, however, the integration to the propulsive host ring/platform to the \npayloads should include structural, maneuver, power, software, and data/communication links required to \nmonitor and sustain the non-separated spacecraft and perform hosted payloads’ on-orbit mission. To \nintegrate payloads into the host ring/platform the Government expects the following general work \nrequirements: \n\n \n• Contractor will fully integrate separable and non-separable payloads into the host platform \n\n •Contractor will support standard space vehicle environmental testing of the integrated host ring/platform \n\n •Contractor will support launch and early on-orbit operations, including anomaly resolution \n\n •Ability to support payloads at various classification levels up to and including TS/SCI and SAP, to include personnel, facilities, security, communication systems, processes, etc \n\n •Ability to support late manifested payloads (less than L-12 months) \n"} Solicitation Number: ROOSTER_RFI_FY26_0001 Type: Sources Sought Base Type: Sources Sought NAICS: 336414 Classification Code: 1555 Response Deadline: 2026-02-27T16:30:00-08:00 Office Address: EL SEGUNDO, CA Place of Performance: El Segundo, California, 90245 POC: Capt Abigail Arestides, abigail.arestides.2@spaceforce.mil POC: Peter Vaccaro, CTR, peter.vaccaro.ctr@spaceforce.mil {"description":" Please see the attached document titled Rooster 6 Integration Support in Attachments for full description and Instructions to responders: \n\n \n SCOPE AND DEFINITIONS: \nSpace Systems Command (SSC), SYD-89 Capability Development System Program Manager (SPM) \n(SSC/SYD89/SYA) is soliciting information about potential sources for the ROOSTER-6 Integration & \nSupport Contract, to perform the integration of a secondary payload ring/platform capable of hosting \nmultiple payloads to support national security missions. The integration of payloads will be for mission \nsets spanning across SSC and potentially other USSF or DoW partners. Missions can vary from \nexperimental/prototyping to operational. These platforms will launch on National Security Space Launch \n(NSSL) missions and can include payloads up to the highest classified levels. The Government seeks \ninformation on existing integration expertise with the ESPAStar-D platform and integrating multiple \nmission payloads and associated acquisition/contract structure, technical, cost, and schedule feasibility. \nTwo types of payloads are expected to be manifested on the platforms furnished to the ROOSTER-6 \nIntegration & Support Contract: 1) on-orbit separable payloads, and 2) on-orbit non-separable payloads. \nThe two types of payloads intended for integration as well as any encryption devices (if needed) will be \nprovided as Government Furnished Equipment (GFE). Separable payloads are integrated on to the multimission \nhost ring/platform and are deployed days to months after launch. The specific port that the \npayload will be “fully integrated” into will be on a Northrup Grumman built ESPAStar-D class secondary \npayload ring. Non-separable payloads are integrated on the host ring/platform and remain with it for the \nentire mission duration. The term “fully integrated” is used to describe a platform with payloads \nmounted and integrated into available secondary payload ring ports and fully tested at the system (ring) \nlevel. \n\n \n CAPABILITY REQUIREMENT: \nSYD 89/SYA seeks an experienced integrator for this flexible and modular propulsive host satellite \nring/platform that will accommodate multiple payloads (separable and hosted) in support of different \nmission sets primarily in a GEO Orbit. The capability to operate in other orbital regimes is also under \nconsideration. The host ring/platform will have a minimum operational design life of 2 years. These \nmissions will be launched on NSSL missions as part of an Integrated Payload Stack (IPS) that is expected \nto include other spacecraft or payload adapters. As part of the launch manifest, integrated vehicles must \nmeet all launch safety requirements including coupled loads analysis, thermal analysis, and testing to \nactual or forecasted launch environments. The propulsive host ring/platform shall at a minimum be \ncapable of hosting six ESPAStar-D Class Payloads. Functional testing of the integrated propulsive host \nvehicle in a simulated space environment is also expected. Support for workarounds, such as testing with \npayload mass simulators, is expected to accommodate payloads that will not arrive until processing at the \nlaunch site. The propulsive host ring/platform structure is intended for attachment and separation from the \nlaunch vehicle Payload Attachment Fitting (PAF) or another payload adapter of the same size. Once \nseparated from the launch vehicle, the multi-mission host ring/platform must support separable payloads \nuntil they are deployed into their intended orbits and continue to support non-separable payloads for \nmission duration. \n\n \n GENERAL DESCRIPTION OF WORK REQUIRED: \nPayloads may have greatly differing mission sets, which will create a wide range of different \nrequirements for each. Generally, however, the integration to the propulsive host ring/platform to the \npayloads should include structural, maneuver, power, software, and data/communication links required to \nmonitor and sustain the non-separated spacecraft and perform hosted payloads’ on-orbit mission. To \nintegrate payloads into the host ring/platform the Government expects the following general work \nrequirements: \n\n \n• Contractor will fully integrate separable and non-separable payloads into the host platform \n\n •Contractor will support standard space vehicle environmental testing of the integrated host ring/platform \n\n •Contractor will support launch and early on-orbit operations, including anomaly resolution \n\n •Ability to support payloads at various classification levels up to and including TS/SCI and SAP, to include personnel, facilities, security, communication systems, processes, etc \n\n •Ability to support late manifested payloads (less than L-12 months) \n"}