Automated Network Orchestration RFI FA2541-24-007.docx

RFI/Sources Sought Automated SATCOM Network Orchestration for Commercial Satellite Communications Services United States Space Force Space Systems Command Commercial Service Office

RFI FA2541-24-007:

The Government is seeking industry feedback, recommendations, and best practices for this response. Please be direct and succinct in your responses to the questions below. In several instances we ask for opinions. Opinions should be accompanied with justification or rationale. Please DO NOT provide generic capability statements; they will be deleted. The Government is seeking well defined responses with supporting documentation to assist with developing any potential acquisition strategy. All responses must be submitted via email to the contacts identified below. This is for informational purposes only and the Government will not be obligated to award to any interested suppliers that present information in response to this Request For Information (RFI)/ Sources Sought. The Government currently has no firm plans to issue a Request For Proposal/Request For Quote (RFP/RFQ) related to this notice.

***All information provided is optional; however, it will be used to assist the Government in determining its acquisition strategy***

Description of need:

For the purposes of this RFI, Network Orchestration refers to the actions required to dynamically configure multi-system hybrid (commercial and military) Satellite Communications (SATCOM) networks to achieve the desired objectives of reliable, resilient and affordable end-to-end satellite communications services for Department of Defense (DOD) Mission Partners. Network orchestration implies automating interactions across multiple types of devices, domains, and even potentially other related systems within the overall multi-domain (system) network. Orchestration typically requires the ability to interact with many device types and suppliers, and across multiple domains and management systems.

The United States Space Force (USSF) Commercial Satellite Communications Office (CSCO) is evaluating the feasibility and options of approaches that can provide automated network orchestration of multiple SATCOM networks in order to provide reliable, resilient and affordable SATCOM to Mission Partners across DOD. For this RFI USSF/CSCO is seeking feedback and advice from Satellite Service providers as well as providers of automated network orchestration tools.

All approaches to providing multi-system connectivity are being considered. This includes centralized orchestration systems that interface with the underlying commercial and DOD SATCOM systems, decentralized, policy-driven approaches and any other method of accomplishing the desired effect of reliable, resilient, affordable multi-system SATCOM.

The questions below are intended to increase CSCO’s awareness of the current state of the art, the art of the possible and approaches that may not have received sufficient consideration in forming an acquisition strategy.

Questions for Industry:

1. Please characterize they type of business you represent:

a. Satellite Owner/Operator: ☐

b. Satellite Services Integrator/Reseller: ☐

c. Satellite Equipment Manufacturer/Supplier: ☐

d. Network Orchestration Manufacturer/Supplier: ☐

e. Other: ☐ Please Specify: ______________________

2. Do you provide products or solutions for automated network orchestration? If so, please briefly describe them (1 paragraph) and provide a URL or attach white paper(s) for more detailed information about the offering.

3. Questions for Satellite Owner/Operators, service providers and integrators:

Some centralized automated network orchestration systems require the SATCOM systems that are being orchestrated to provide a standards compliant Application Program Interface (API) in order to enable the dynamic exchange of network resource availability information and facilitate the ability to automate the management of interconnections and transit services by the automated orchestration system in tactically responsive timeframes. An example of such an API is the open-source Federation API as defined and published by the Outernet Council. If CSCO were to require such an API to be implemented and offered as part of the COMSATCOM services you sell:

a. Could such an API be implemented for the COMSATCOM services you sell or integrate?

b. What impacts (functionality/cost/other) would you anticipate arising from incorporating such an API?

c. Do you see any advantages to yourself and/or DOD to having such an API?

d. Do you see any disadvantages to yourself and/or DOD to having such an API?

e. How would you structure a business model and pricing plan for resources obtained and controlled through such an API?

4. Questions for automated network orchestration providers:

Regarding the API mentioned Question 3 above:

a. Do you see any benefits or impediments created by incorporating such an API into the services purchased by CSCO with respect to your ability to provide automated network orchestration tools/services?

b. How does your automated network orchestrator deal with the “chicken and egg” problem of establishing initial connectivity to a remote terminal?

c. What, if any, role does your automated network orchestrator delegate to remote terminals? How does your orchestrator address the need for remote terminals to detect and react autonomously to local phenomena that should affect orchestration decisions but cannot be detected by the orchestrator itself?

5. Questions for all:

a. Should the government be considering centralized or decentralized automated network orchestrators, and why?

b. One of the stated goals is “affordable” SATCOM services, what role do you see automated network orchestrators playing in making SATCOM more affordable to DOD Mission partners?

c. When evaluating potential automated network orchestrations approaches, what should the government use as evaluation criteria in order to pick a winner? Is there a path that avoids picking a winner at all while allowing the government to benefit from the best features across all available automatic network orchestration technologies?

d. What sort of performance parameters are appropriate for evaluating the operation of automated network orchestrators? How should they be measured?

Requested Information:

In addition to providing direct and succinct responses to the questions above and justification or rationale for the opinions rendered, interested suppliers are asked to submit the following information:

A. Supplier Information Requested

a. Name of Business

b. Cage Code

c. Primary

d. North American Industry Classification System (NAICS) Code

e. Business Type Small Business/Large

f. POC: Name/Phone number/email B. Please provide, in separate documents from the RFI response, any other relevant information you are willing to share regarding capabilities, features, and roadmaps related to the topics covered in the questions.

C. Any recommendations for current industry best practices not listed.

D. If company is a small business, please describe ability to meet the requirements outlined in 52.219-14, Limitations on Subcontracting.

There is no limit to response length, however the Government seeks succinct and efficient responses and will not review generic capability statements. All responses shall be submitted NLT 25 Oct 2024 at 1700EST. Please submit your responses to the following individuals (include all):

John Seacrist, Contracting Officer. Email: john.seacrist@spaceforce.mil

Upon conclusion of market research efforts, the Government may or may not release a formal solicitation for this effort. Should you have any questions please reach out to the individuals above.

image1.png image2.png image3.emf