RFI_Enterprise_Cloud_Storage_Solution.pdf

REQUEST FOR INFORMATION (RFI)

Title: Enterprise Cloud Storage Solution

Issuing Office: Ground Vehicle System Center (GVSC) Software Engineering Center (SEC)

1.0 INTRODUCTION & PURPOSE

This is a Request for Information (RFI) for market research purposes only. This RFI is issued to identify sources capable of providing a secure, scalable, and cost-effective enterprise-level cloud storage solution.

2.0 BACKGROUND

The Software Engineering Center requires a cloud service solution to store, manage, and secure mission-critical data. The solution must be capable of handling large data volumes with high availability and robust security controls. The United State Government (USG) is seeking to understand the range of available commercial-off-the-shelf (COTS) and government-provided cloud solutions that can meet our operational needs.

3.0 SCOPE AND DESIRED CAPABILITIES

The USG is seeking a solution that meets the following key performance parameters and capabilities:

3.1 Impact Level: The solution must be authorized to operate at DoD Impact Level 5 (IL5) to handle

Controlled Unclassified Information (CUI).

3.2 Storage Capacity: The initial requirement is for 25 Terabytes (TB) of storage, with the ability to scale as data needs grow.

3.3 Storage Concept & Redundancy: The solution should provide high availability and data durability.

Describe your support for concepts such as Locally-Redundant Storage (LRS) and Read-Access Geo-

Redundant Storage (RA-GRS) or equivalent.

3.4 Authentication: The solution must provide secure access controls. Common Access Card (CAC) authentication is a primary requirement. If your solution does not support CAC, describe your alternative authentication methods (e.g., security keys, multi-factor authentication).

3.5 Data Transfer (Ingress/Egress): Respondents must clearly detail their cost structure for data ingress and egress. Solutions that offer fixed-rate pricing with no variable egress fees are of significant interest.

3.6 Access Methods: The solution should support modern data access protocols and tools, including

HTTPS, REST APIs (GET/PUT operations), Command Line Interfaces (e.g., AWS CLI), and desktop applications (e.g., Azure Storage Explorer).

3.7 Data Management: The solution should include features for data versioning (similar to AWS S3

Versioning), automated backups (with configurable daily/monthly schedules and retention policies), and user account management.

3.8 Cloud Service Provider (CSP): The solution may be built on any IL5-authorized CSP, including but not limited to AWS GovCloud, Microsoft Azure Government, Oracle Cloud Infrastructure (OCI), or a

DISA-provided offering.

4.0 INFORMATION REQUESTED FROM RESPONDENTS

Please provide the following information in your response:

4.1 Corporate Information:

Company Name, Address, Point of Contact, CAGE Code, and Company Website.

Business Size and any socio-economic classifications.

A brief overview of your company's experience providing cloud solutions to DoD or other federal agencies.

4.2 Technical Approach:

A detailed description of your proposed cloud solution and the underlying CSP it utilizes.

A clear explanation of how your solution meets each of the capabilities listed in Section 3.0.

Specifically address your IL5 authorization status and your method for CAC authentication.

A description of the onboarding process for new users and the available technical support.

4.3 Rough Order of Magnitude (ROM) Costing:

Provide a ROM for a 25 TB solution. The ROM should be broken down into:

Annual and/or monthly subscription costs.

A detailed explanation of ingress/egress charges, including an estimated cost for moderate usage.

Costs for any optional features, such as additional user accounts or enhanced backup/retention plans.

Any one-time setup or non-recurring fees.

4.4 Contract Vehicles:

A list of existing government contract vehicles (e.g., CHESS, DoD ESI, GSA Schedules, SEWP) through which your solution can be procured.

5.0 RESPONSE INSTRUCTIONS

Responses should be submitted electronically to rachel.l.serra.civ@army.mil no later than 3:00

P.M. EST on March 13, 2026.

The subject line of the email should read: "RFI Response to Enterprise Cloud Storage Solution: [Your

Company Name]".

All responses must be Unclassified. Electronic responses are required in any of the following formats: Microsoft Word or Adobe Acrobat. The document shall not exceed 15 page limit (not including attachments and title page, using Time New Roman, font size 12 with one-inch margins.

The maximum size of each email message should be no more than ten (10) megabytes.

All interested firms, regardless of size are encouraged to respond to this RFI.

It is not necessary to respond to this RFI to be eligible for future awards.

6.0 DISCLAIMER

This RFI Notice is for informational purposes only. The information in this notice is subject to change and is not binding on the USG. This is not a Request for Proposal (RFP), does not constitute a solicitation, and shall not be construed as a commitment by the USG to purchase enhancements, hardware, or services for the GVSC. Responses in any form are not considered offers and the USG is under no obligation to award a contract as a result of this announcement. Funds are NOT available to pay for preparation of responses to this announcement. Any information submitted by respondents to this RFI Notice is strictly voluntary.

Since this is not an RFP, respondents WILL NOT be notified regarding information obtained related to this RFI Notice. Responses will not be returned nor will detailed feedback be made available.

7.0 PROPRIETARY INFORMATON

The USG acknowledges its obligations under the Federal Acquisition Regulation (FAR) and 18 United

States Code (U.S.C.) §1905 to protect confidential information provided to the USG. Pursuant to this statute, the USG is willing to accept any trade secrets or proprietary restrictions placed upon data presented in response to this RFI and to protect such information from unauthorized disclosure, subject to the following:

• Data must be clearly marked PROPRIETARY and be accompanied by an explanatory text so that the USG is clearly notified on what data is proprietary.

• Mark only data that is truly confidential. Use circling, underscoring, highlighting or any other appropriate means to indicate those portions of a single page which are to be protected.

• Do not mark data that is already in the public domain or is already in possession of the USG or third parties on an unrestricted basis.

• Do not submit any classified data in response to this RFI.

• Proprietary data transmitted electronically must have the PROPRIETARY legend on both the cover of the transmittal e-mail as well as at the beginning of the file. Proprietary information contained within the correspondence or file shall use the legends: “PROPRIETARY PORTION

BEGINS” and “PROPRIETARY PORTION ENDS.”

• The USG is not obligated to protect unmarked data. Additionally, marked data that is already in the public domain or in the possession of the USG or third parties, or is afterward placed into the public domain by the owner or another party through no fault of the USG will not be protected once in the public domain. Data already in the possession of the USG will be protected in accordance with the USG’s rights in the data.

In any reproductions of technical data or any portions thereof subject to asserted restrictions, the USG shall also reproduce the asserted restriction legend and any explanatory text. Data submitted in response to this RFI will not be returned.