Template Version

SUBJECT: Request for Information (RFI) – Enterprise Data Integration Space Operations Node

(EDISON)

1. Background:

The United States Space Force (USSF) Unified Data Library (UDL) was designated by the United States Space Force (USSF) Chief of Space Operations (CSO) Gen. Raymond (signed 8 January 2021) to be the single source for accessing and managing all data in support of USSF operational. The USSF Data Integration Layer provides a central location to ensure space data is visible, accessible, understandable, linked, trusted, interoperable and secure (VAULTIS) to improve information sharing and discovery for decision-making advantage. It is a core component of the USSF’s efforts to create a digital service to accelerate innovation by using data as a strategic asset.

The stated goal for this Request for Information (RFI) is to canvas industry and academia on their ability to process, protect, persist, integrate/federate with other data repositories, and disseminate a wide variety of mission and operational space data. The anticipated scope is to mature and operationalize the concepts and products prototyped for the UDL platform and space onboarding1 components, maintain and operate the existing capabilities, and integrate with other enterprise-wide systems to meet operational requirements.

This RFI is issued solely for information and planning purposes (market research). This RFI does not constitute a solicitation (Request for Proposal (RFP) or Request for Quotations (RFQ)) 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. Responses to this RFI are not offers and cannot be accepted by the Government to form a binding contract. Furthermore, the Government is not, at this time, seeking proposals and will not accept any unsolicited proposals. 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 responding party’s expense. Not responding to this RFI does not preclude participation in any future solicitation, if any is issued. Any information submitted by respondents to this RFI is strictly voluntary. All submissions become Government property and will not be returned. Proprietary information will be safeguarded in accordance with the applicable Government regulations. Proprietary information or trade secrets shall be clearly identified.

1 Space Onboarding refers to the process of first identifying data providers and concludes with successful data ingestion into the UDL’s datastore. Onboarding follows a gated process of steps, including customer engagement, detailed technical discussions, design and planning, cost estimates and implementation of new schemas and end points if needed, and testing and ingest of data. The Onboarding process should automate to the maximum extent possible the processes to accelerate the onboarding experience for the data providers.

2. Description:

This RFI is for USSF Space Systems Command’s (SSC) System Delta (SYD 85). Additional market research may or may not be conducted. Responses from small businesses are encouraged. This RFI is focused on surveying industry capability. Recent (≤5 years), relevant (see Section 3b) demonstrated success with low cost, rapid delivery of capabilities as described in the attached summarized USSF Data Integration Layer Capability Need Statement (CNS), which may include development that is underway or already fielded. High Technology Readiness Level (TRL) products and services, as well as the re-use of existing capabilities and/or opportunities are of interest. “Low-cost” and “rapid” must result in acceptable programmatic and technical risk to the Government.

3. Requested Information:

The RFI responses must include the following:

a. Company and Security Information:

i. Company name and Parent Company, if applicable

ii. Business Address: Street, City, State, and Zip code

iii. Commercial and Government Entity Code

iv. Unique Entity Code

v. Company Socio-economic Status:

vi. Point of Contact (i.e., POC, Company Representative)

vii. POC Telephone and Email Address)

viii. Provide insight into past teaming arrangements as appropriate (limit to 1 page)

ix. Summary of current accredited facilities and location, workforce, and networks to support CUI (NIPRNet access), Secret (SIPRNet Access), Top Secret (TS), Sensitive Compartmented Information (SCI) (JWICS Access) and Special Access Programs (SAP) (SGN Access) where classified engineering, manufacturing, integration and operations and maintenance may occur.

b. Recent/Relevant Technical Information:

i. Using the attached spreadsheet (To gain access to this spreadsheet and CNS, please email SYD85.BN.DataFederation@spaceforce.mil and the two documents will be provided to you), describe your current experience and capabilities in the 6 attribute areas listed. Your existing solutions do not need to address each of the sub-requirements in column C, nor do your existing solutions need to meet all sub-requirements.

mailto:SYD85.BN.DataFederation@spaceforce.mil

ii. Please describe your expertise and experience related to SAFe and Agile ceremonies, stakeholder involvement, tracking of work in progress, backlog grooming as related to government contracting. Please explain how you manage schedules within the SAFe/Agile frameworks to track planned and actual dates and support traditional Integrated Master Schedule (IMS).

iii. Explain/describe your expertise and experience with programs/projects that require a CI/CD pipeline that complies with Department of War (DoW) DevSecOps principals and strategies. (See https://dodcio.defense.gov/ and search for DevSecOps)

iv. Explain your experience in developing software architecture in cloud environments, outlining services used, and how that architecture is scalable to maximize discoverability, handle large volumes of data, resilient, adaptable and cost effective. Explain the types of cloud models (PaaS, DaaS, IaaS) used as well as types of technologies (microservices, containerization, serverless, etc.)

v. Explain your experience in developing software that meets Modular Open

Systems Approach (MOSA) guidelines. (See https://www.cto.mil/wp-content/uploads/2025/03/MOSA-Implementation-Guidebook-27Feb2025- Cleared.pdf).

vi. Provide your experience with Risk Management Framework (RFM) processes for deploying software in a cloud environment. (See https://csrc.nist.gov/projects/risk-management/about-rmf)

vii. Describe your processes for managing the software lifecycle (from requirements to delivery of capability).

viii. Explain your process for maintaining configuration control of a software baseline?

ix. Describe your experience in taking over an existing code baseline from another vendor to 1) further develop the code, 2) integrate other GOTS/COTS1 solutions and 3) maintaining the current Authority to Operate (ATO). Please provide details on the timelines and what artifacts you may

1 COTS stands for "Commercial Off-the-Shelf," meaning pre-packaged, commercially developed software that can be purchased and adapted for specific needs. GOTS stands for "Government Off-the-Shelf," referring to software developed specifically by or for a government entity to meet unique requirements.

https://dodcio.defense.gov/ require to be successful. Note: Refer to the attached spreadsheet on the current and future capabilities of the code base.

c. Recent/Relevant Programmatic Information:

i. Please describe your process for managing risk.

ii. What contract types would you recommend for the work described above?

iii. Do you have experience in managing a large Indefinite Delivery, Indefinite Quantity (IDIQ) with multiple Task Orders?

iv. Describe your experience with working with multiple stakeholders across multiple organizations and services?

4. Assumptions:

Contractor shall assume the following for the purposes of providing this RFI:

a. The government is seeking companies with development and maintenance of data lakes in a cloud environment. Experience with Program of Record and/or Software Pathway programs is beneficial.

b. Government plans to use this RFI as a possible source to support accessing capable vendors to appropriate security levels for potential follow-on competitive RFP.

5. Request for Information Submission Details

To gain access to the Capability Needs Statement and Excel response spreadsheet, please email SYD85.BN.DataFederation@spaceforce.mil and the two documents will be provided to you.

Submittals shall not exceed fifteen (15) pages total (not including the excel spreadsheet), any pages beyond the limit will not be considered. Response shall be submitted in MS Word 2000 (or newer). Responses will be formatted to match the structure of the RFI as outlined above in 3 a, b, and c. Page size shall be 8.5 x 11 inches; single spaced with text no smaller than 10-point Times New Roman; font size within graphics and tables shall be no smaller than 8 point, Times New Roman. Margins shall be one inch on all sides. The title page and front matter such as transmittal letter, cover page, and table of contents will not count against the page limit.

Respondents shall provide an unclassified response to the RFI to the maximum extent possible. Respondents shall indicate whether their responses contain any proprietary information if the respondents wish for the responses to be handled as such. The Government shall NOT be held liable for any damages incurred if proprietary information is not properly identified. Please be advised that all submissions become Government property and will not be returned.

If a classified annex to the RFI response is submitted, its contents will be limited to only that which is required to be protected as classified information. Classified annex page count will count towards the fifteen (15) page total for the response, not including title page and front matter. A classified annex may be provided via an appropriately classified network (SIC, CORE, SGN, etc.) or classified fax. The contractor may request a POC for submission of the classified annex. Please ensure all files and media are scanned and cleaned with an anti-virus program before transmitting. Oral communications are not acceptable. The government may reach out with clarification questions following contractor submission.

SSC has entered into contracts with Federally Funded Research and Development Center (FFRDC) staff working with the Government. These could include, but are not limited to:

The Aerospace Corporation, and/or MITRE. SSC SYD 85 also receives Systems Engineering and Technical Assistance (SETA) support from Odyssey Consulting. These organizations/companies support the Government by performing technical reviews, systems engineering and integration analyses, cost estimation, and other advisory services.

Respondents are hereby notified that all responses will be provided to SSC support contractors for services to SSC. If Respondents disagree to the release of their RFI response to any of the firms, the Respondent must clearly state this restriction in the cover letter accompanying the RFI response.

Foreign firms are advised that they will not be allowed to participate in this acquisition at the prime contractor level; however, provided they are eligible to do business with the US Government, they may be eligible to participate at the subcontractor level. The research and test data produced under a resultant contract may contain Military Critical Technology List (MCTL) information whose export is restricted by Export Control Act (Title 22, U.S. Sec 2751, et seq.) or the Export Administration Act of 1979, as amended (Title 50, U.S.C., App.

2401, et seq.). Request certification and registration from the Defense Logistics Services Center (DLSC), Federal Center, 74 North Washington, Battle Creek, MI 49016-3412 as soon as possible.

6. Submittal Instructions:

All responses shall be submitted via email to the Contracting POCs identified below. All submissions shall include company name and point of contact information including name, position, telephone number, and email address. Any questions related to the RFI should be directed to all the POCs listed below.

Responses received after the due date may not be considered in the Government’s analysis.

The government may subsequently contact respondents for clarification on the information submitted.

POINTS OF CONTACT:

Contracting POC Capt. Keon Hannibal, keon.hannibal.2@spaceforce.mil Document Request: SYD85.BN.DataFederation@spaceforce.mil

Disclaimer Proprietary information, if any, should be kept to a minimum and MUST BE CLEARLY MARKED. Please be advised that all submissions become Government property and will not be returned.

Other Data for PCO to input into SAM.GOV

Due Date: 23 Feb 2026

NAICS Code: 541511, 541519

Performance Location: USA mailto:keon.hannibal.2@spaceforce.mil

NAICS Code: 541511, 541519