Request for Information Enterprise Resource Manager (ERM).pdf

Space Systems Command (SSC)

BC3 Tactical Office (BCT)

Los Angeles Air Force Base, California (LAAFB, CA)

Enterprise Resource Manager (ERM)

Request for Information (RFI)

1. Background

The Space Systems Command BC3 Tactical Office (SSC/BCT) previously released 3 RFIs1 that have highlighted different areas of ERM’s evolving mission:

• The November 2021 RFI focused on how a system could manage pools of ground resources across diverse networks/service providers to optimize the scheduled resources.

• The May 2022 RFI provided an updated set of capability needs for the system that were intended to support mission scheduling, antenna resource automation, and phased array implementation.

Additionally, it included some Special Access Program (SAP)-level requirements.

• The August 2023 RFI focused on required infrastructure solution (e.g., public, private, hybrid, on-prem clouds), Platform-as-a-Service (PaaS), existing services that should be leveraged, DevSecOps pipeline, and updates to previous submissions.

In January 2025, the Space Systems Command BC3 Tactical Office, Antenna Services (SSC/BCTA) also released a Request for Prototype Proposal (RPP) on the Space Enterprise Consortium (SpEC) which sought to develop and deploy the core, cloud-based capabilities necessary to support the enterprise Joint Antenna

Marketplace (JAM) solution.

As a result of those efforts, the Government is further focusing on both unclassified and classified mission requirements.

2. Program Description

SSC/BCT is now seeking information from industry regarding the best way to leverage industry capabilities and the results of the ongoing aforementioned prototyping efforts to cost-effectively develop an advanced attribute-based satellite communications scheduling and resource management capability that can support the scheduling needs of diverse mission sets with diverse ground resources; operate at the highest classification levels, be hosted in either a community cloud or cloud/on-prem hybrid; provide scheduling, RF deconfliction, and orchestration services for enterprise-scale applications; and support multiple classification levels, in a dynamic and responsive Telemetry, Tracking, and Command (TT&C) environment.

1 If respondents require copies of these previous RFIs, please contact the SSC point of contact Maj Ikaika K.

Ramos, ikaika.ramos.1@spaceforce.mil mailto:ikaika.ramos.1@spaceforce.mil

The purpose of this RFI is to assess the current state of industry technologies, maturity levels, and availabilities to inform SSC in its planning and formulation of the ERM acquisition strategy. Additionally, information gathered from this RFI will be used to further inform requirements for ERM.

This RFI is being issued solely for information and planning purposes. It does not constitute a Request for

Prototype Proposal (RPP), a Request for Proposal (RFP), or a promise to issue a solicitation in the future.

This RFI does not commit the Government to contract for any supply or service whatsoever. Further, the

Government is not at this time seeking proposals and will not accept unsolicited proposals. RFI respondents are advised that the Government will not pay for any information or administrative costs incurred in response to this RFI; all costs associated with responding to this RFI will be solely at the interested party’s expense. Not responding to this RFI does not preclude participation in any future RFPs/RPPs, if any are issued.

3. Use of Non-Government Advisors

The Government intends to use US Government (USG) personnel to review the RFI responses. The

Government reserves the right to use contractor personnel, including, but not limited to, SSC-affiliated

Federally Funded Research and Development Centers (FFRDC), System Engineering & Integration (SE&I) contractors, and Systems Engineering and Technical Assistance (SETA) contractors. Contractor support will be bound by appropriate Non-Disclosure Agreements (NDAs) to protect proprietary and sensitive information. Additional NDAs will not be required as responses to this RFI will be considered implicit acknowledgment and acceptance that non-Government advisors will be assisting the Government in the review process.

4. Requested Information

Respondents should describe how they might propose to leverage existing investments to deliver a solution that can manage pools of ground resources across diverse networks/service providers while optimizing the scheduled resources to support multiple users. Respondents should provide insight into solutions that can support Government customers at multiple security classification levels and identify existing Data Rights on software that will be utilized.

The government is particularly interested in the following areas. The ERM solution should be capable of:

1. Scheduling operations at levels from individual satellites up to constellation-level constructs.

2. Scheduling resources for ALL orbital regimes, including Cislunar, and Lagrange points.

3. Automated scheduling via machine-machine interfaces with

a. Multiple Ground Entry Points (GEPs) at various geographic locations with multiple apertures per location.

b. Diverse GEP types (e.g., parabolic antennas, phased arrays).

c. Deconfliction of GEPs.

4. Performing orbital analysis utilizing all available space vehicle (SV) ephemeris or other information to inform scheduling algorithm(s).

5. Conducting Radio Frequency Interference (RFI) deconfliction for all available assets (ground, space) to inform scheduling algorithm(s).

a. Incorporating flexible RF windows as needed or upon user customer request.

6. Scheduling of linked contacts events.

7. Supporting multi-contact uplink and downlink operations scenarios.

8. Supporting Dynamic Space Operations.

9. Maintaining a rolling window schedule that

a. Responds dynamically with schedule updates.

b. Has ability to schedule requests and consistently respond to users without “Thrashing” i.e., slowing of responses due to, for example, processing overloads.

i. NOTE: Respondents may describe scheduling responsiveness with respect to algorithmic processing of solutions, and request/display updates as a function of resources to schedule and loading, if available, or as estimates.

c. Ensures and implements user-authorized rolling window views of sufficient utility and detail with respect to scheduling.

10. Enforcing overrides based on

a. Priority levels.

b. Tasking authority.

11. Performing automated rescheduling once user requests are submitted if required.

Note: it is intended that a schedule request will be automated, and the requestor will not have to identify a particular GEP.

12. Incorporating business rules for all available networks which may include link budget parameters for optimized scheduling.

13. Supporting full scalability.

In addition, The Government is also interested if the respondents could:

1. Describe its approach to standardized interfaces in conjunction with a multi-security level environment requiring Cross Domain Solutions (CDSs).

2. Describe approach to deliver CDS in a zero-trust architecture.

3. Describe approaches, capabilities, and experience (operational or otherwise) with cloud-based designs and implementations that have

a. Required system availability.

b. Rapid system scalability requirements (elasticity).

4. Describe cyber-resiliency approach with respect to leveraging commercial GEPs and associated interfaces and Concept of Operations (CONOPS) to leverage those resources.

5. Describe other modalities to consider in scheduling (e.g., scheduling of multiplexed commanding and telemetry streams).

6. Describe capabilities and/or approaches for leveraging

a. Artificial Intelligence.

b. Machine Learning.

c. Multi-temporal considerations in dynamic scheduling.

7. Describe the maturity of approaches under consideration in sufficient detail for the government to establish if commercial off the shelve products are available or if prototyping is required to achieve required capabilities.

8. Generally describe any other modalities to consider in scheduling and scaling for ERM.

9. Discuss potential development/performance contributions from non-traditional defense contractors.

5. Terms & Definitions

Term Definition

Aperture and Beams Includes single-beam parabolic dish capabilities, advanced multi-beam phased-array capabilities with variable beamwidths, beam-splitting, and beam combining to effect dynamic space operations

Community Cloud Shared cloud computing environment that is limited to a specific set of stakeholders/organizations, which may include commercial services

Dynamic Space Operations Space environment where spacecraft can transition from a static role to one where they can act in real-time

Event A schedulable object representing a time for which resources or capabilities are required

Space Vehicles Spacecraft – a vehicle that flies and operates in outer space

Thrashing Situation where race conditions prevent the scheduling algorithm from converging on a solution in the required timeline

6. Responses

Interested parties are requested to respond to this RFI utilizing the following guidelines:

• Deliver all submissions no later than 1700 PDT 30 days from RFI posting

• Electronically submit unclassified responses via NIPR to the following SSC Point Of Contact(s):

- Ikaika K. Ramos, Maj, ikaika.ramos.1@spaceforce.mil

• Coordinate with Major Ramos regarding any classified submissions.

• Label and portion-mark RFI responses appropriately.

• Limit responses to 10 single-sided pages, including diagrams. This excludes coversheets, Table of

Contents, Statement of Works, and acronyms.

• Utilize 8.5 x 11-inch portrait formatted pages - landscape format is acceptable for charts and graphs.

• Include a cover sheet with company name, address, date, RFI response POC with an email address and phone number.

• Deliver submissions in either a PDF or Microsoft Word document.

• Ensure that proprietary information, if any, is kept to a minimum and IS CLEARLY MARKED. Be advised that all submissions become Government property and will not be returned. To review RFI responses, PROPRIETARY information may be given to and/or Advisory and Assistance Services

(A&AS) contractors working for the Government.

• Provide a proposed Statement of Work with associated Rough Order of Magnitude (ROM) cost and proposed ROM schedule.

SSC/BCT will NOT consider unnecessary brochures or proposals.

SSC/BCT will welcome one-on-ones with interested contractor teams. If a one-on-one meeting is desired, please contact the following SSC Point Of Contact(s):

- Ikaika K. Ramos, Maj, ikaika.ramos.1@spaceforce.mil

For this RFI, respondents should assume:

• The Government will provide additional details from the unclassified and classified prototyping efforts as part of any RFP or RPP. This will include providing those solutions as Government

Furnished Equipment (GFX).

• All solutions will be hosted in a Government community or hybrid cloud solution.