SF243-D014.pdf

Standard Form PDF 52 KB Posted

Attached to
Responsive, Radiation-hardened GEO Rideshare Capability
Solicitation number
SF243-D014
Issued by

About this file

This document is a Statement of Objectives (SOO) for a Space Force Small Business Innovation Research (SBIR) topic addressing responsive, radiation-hardened geostationary orbit (GEO) rideshare capability.

The primary objective is to flight qualify a dispenser and associated hardware capable of rapidly manifesting critical rideshare payloads on primary GEO missions within 30-60 days of launch without disrupting existing schedules. A secondary objective requires demonstrating the capability to operate, store, maintain thermal and power requirements, and responsively deploy payloads in a GEO environment for predetermined extended periods. The technology addresses the DoD's need to overcome manifest and GEO-access challenges while reducing costs and schedule risks associated with payload manifesting and de-manifesting. The solution must establish a non-unique, standardized interface between rideshare payloads and primary missions, enabling responsive payload deployment independent of the primary mission for potentially multiple years until operational need arises.

This topic targets technology proven ready for Phase II development; Phase I awards will not be made. Applicants must demonstrate Phase I-type feasibility study accomplishment in their proposal, including validated product-mission fit with USAF and/or USSF stakeholders and a clear, actionable integration plan with the Department of Air Force customer. Phase II will focus on developing and flight qualifying the dispenser hardware and demonstrating extended payload storage and operation capabilities in GEO. Phase III dual-use applications include commercial satellite deployment services and military mission resilience for rapid payload deployment. The technology falls under ITAR restrictions (22 CFR Parts 120-130) and EAR controls. No CMMC level requirement applies. No Technical Point of Contact is listed.

View the file

Other versions and copies of SF 243

File Revision Posted Attached to
SF243-D013.pdf Revision not stated CCDM (Camouflage, Concealment, Deception, and Maneuver) Interrogation
SF243-D012.pdf Revision not stated Foreign Space Launch Detection
SF243-0003.pdf Revision not stated Reentry Events and Impact Location Prediction
SF243-D002.pdf Revision not stated Low Earth Orbit Space Domain Awareness Optical Fence
SF243-D011.pdf Revision not stated Launch Cycle Initiation Detection
SF243-D017.pdf Revision not stated Advancing Expeditionary Space Domain Awareness
SF243-D008.pdf Revision not stated RETURN (Returning ExoaTmospheric Unique Research is Novel)
SF243-0004.pdf Revision not stated Responsible Space Behavior Event Classification
SF243-D003.pdf Revision not stated Characterization and Typing of Hard-to-Acquire Targets using Advanced Machine Learning Methods on WFOV Staring Data
SF243-D009.pdf Revision not stated ASAT Launch Detection and Threat Assessment
SF243-D016.pdf Revision not stated Tactical High Orbit Fast Transfer
SF243-0001.pdf Revision not stated Event Based Data Fusion for Temporal Super Resolution in Image Based Tracking
SF243-D018.pdf Revision not stated Space Sustainment & Maneuver: Advancing Strategic Superiority in Orbital Operations
SF243-D010.pdf Revision not stated Object Transiting Tracking
SF243-D006.pdf Revision not stated Future Space Architectures through Advanced Mission Design and In-Space Development Platforms
SF243-D004.pdf Revision not stated Nitramine Cost Reduction Development
SF243-D015.pdf Revision not stated Advancing Space Capabilities for Joint Warfighting Opportunities
SF243-0002.pdf Revision not stated Spectral-Binning Focal Plane Array for Infrared Spectroscopy
SF243-D001.pdf Revision not stated Manufacturing of New Nosetip Materials for Reentry Vehicles
SF243-D005.pdf Revision not stated Event-Based Sensor Readout Integrated Circuit
Show all 20

Who attaches SF 243

Other files

File Type Posted
AF_SBIR_243_DP2_v4.pdf PDF

On GovTribe

Work with this file

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

Text version

SF243-D014: Responsive, Radiation-hardened GEO Rideshare Capability

PROJECTED CMMC LEVEL REQUIREMENT:

N/A

TECHNOLOGY AREAS:

Battlespace | Space Platforms

MODERNIZATION PRIORITIES:

Space Technology

KEYWORDS:

Responsive space, Rideshare missions, Geostationary orbit (GEO), Flight qualification, Dispenser hardware, Payload storage, Mission resiliency

ADDITIONAL INFORMATION

N/A

OBJECTIVE:

The objectives of this topic are to:

1.) Flight qualify a dispenser and associated hardware that has the capability to rapidly (i.e., within 30-60 days of launch and without perturbing/delaying existing schedules) manifest critical rideshare payloads on a primary mission intended for a geostationary orbit (GEO).

2.) Demonstrate, either operationally on-orbit or on the ground, the capability to operate, store, maintain thermal and power requirements in a GEO environment for the payload(s) for a pre-determined period of time, and then responsively deploy the payload(s) upon command.

ITAR:

The technology within this topic is restricted under the International Traffic in Arms Regulation (ITAR), 22 CFR Parts 120-130, which controls the export and import of defense-related material and services, including export of sensitive technical data, or the Export Administration Regulation (EAR), 15 CFR Parts 730-774, which controls dual use items. Offerors must disclose any proposed use of foreign nationals (FNs), their country(ies) of origin, the type of visa or work permit possessed, and the statement of work (SOW) tasks intended for accomplishment by the FN(s) in accordance with section 3.5 of the Announcement. Offerors are advised foreign nationals proposed to perform on this topic may be restricted due to the technical data under US Export Control Laws.

DESCRIPTION:

Despite advances in responsive space, the ability to manifest and de-manifest satellites/payloads from a mission, particularly rideshare payloads, still requires either flying a mass simulator in place of a de-manifested payload or re-running a costly and schedule intensive coupled loads analysis (CLA). In both cases, there will be a monetary cost and possible mission delays associated with the change(s). Increases in cost or changes to schedule can be even more deleterious for missions intended for GEO, which can already be difficult for small rideshare payloads to reach. The U.S. Department of Defense (DoD) needs a demonstrated capability that can overcome both manifest and GEO-access issues. This capability would enable responsive manifesting/de-manifesting of payloads on the ground without penalties to cost or schedule. Furthermore, this capability would reduce the interface between any rideshares and the primary mission to a non-unique, standardized interface. Once on orbit, the capability would demonstrate the ability to host and maintain the health of payloads in GEO independent of the primary mission for, potentially, multiple years until the payload is needed to respond to a threat and the capability responsively deploys it.

PHASE I:

This topic is intended for technology proven ready to move directly into Phase II. Therefore, Phase I awards will not be made for this topic. The applicant is required to provide detail and documentation in the D2P2 proposal which demonstrates accomplishment of a “Phase I-type” effort, including a feasibility study. This includes determining, insofar as possible, the scientific and technical merit and feasibility of ideas appearing to have commercial potential. It must have validated the product-mission fit between the proposed solution and a potential U.S. Air Force (USAF) and/or U.S. Space Force (USSF) stakeholder. The applicant should have defined a clear, immediately actionable plan with the proposed solution and the U.S. Department of Air Force (DAF) customer and end-user.

The feasibility study should have:

1. Clearly identified potential stakeholders of the adapted solution for solving USAF and/or USSF need(s).

2. Described the pathway to integrating with DAF operations, to include how the applicant plans to accomplish core technology development, navigate applicable regulatory processes, and integrate with other relevant systems and/or processes.

3. Describe if and how the solution can be used by other DoD or U.S. Government (USG) customers.

PHASE II:

In Phase II, the objective is to develop and flight qualify a dispenser and associated hardware capable of rapidly manifesting critical rideshare payloads for primary missions intended for Geostationary Orbit (GEO). Additionally, the phase involves demonstrating the capability to store, maintain, and then operate payloads in a GEO environment for extended durations, ensuring mission resiliency and reducing costs and schedule risks associated with manifesting and de-manifesting payloads intended for GEO.

PHASE III DUAL USE APPLICATIONS:

In Phase III and for dual-use applications, the matured capabilities can be seamlessly integrated into both commercial and military space endeavors necessitating agile payload deployment and replenishment of systems within GEO. For commercial satellite deployment services, this technology offers streamlined payload manifesting, minimizing costs attributed to launch disruptions or revisions on commercial GEO launches. On the military front, these capabilities fortify mission resilience, facilitating swift deployment of vital payloads to counter emergent threats, thereby reinforcing national security interests in space.

REFERENCES:

https://spacenews.com/nro-to-conduct-responsive-space-mission-with-firefly-and-xtenti/.1.

https://www.prnewswire.com/news-releases/firefly-aerospace-and-xtenti-collaborate-to-conduct-responsive-space-demonstration-in-support-of-the-nro-301894888.html.

2.

How Hard Is Going To Space?. Many people believe the complexity and… | by Tory Bruno | Medium <https://medium.com/@ToryBrunoULA/how-hard-is-going-to-space-20637c846ea3>.

3.

TECHNICAL POINT OF CONTACT (TPOC):

None

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