USAStorage_3.0_SOO - v1.3 - Final.pdf

USA Storage 3.0

Statement of Objectives (SOO)

Executive Office for United States Attorneys (EOUSA)

Office of the Chief Information Officer (OCIO)

1.0 INTRODUCTION AND PURPOSE

The United States Attorneys organization is comprised of ninety-four (94) Districts with roughly two-hundred fifty (250) offices in geographically dispersed sites throughout the continental United States, Alaska, Guam, the Marianas Islands, Puerto Rico, Hawaii, and the U.S. Virgin Islands. The Executive Office for United States Attorneys (EOUSA) is responsible for providing administrative, technical, and legal support to all United States Attorneys’ offices (USAOs).

The Office of the Chief Information Officer (OCIO) of the Executive Office for United States Attorneys (EOUSA) delivers technology solutions that enable United States Attorney’s Office (USAO) employees to effectively carry out their complex operational duties. OCIO works collaboratively with USAOs and other stakeholders to translate their business needs into effective IT solutions, providing essential tools that support the DOJ’s mission. OCIO designs, develops, and implements enterprise-scale solutions across a range of areas, including custom application development, server and virtual infrastructure, voice and unified communications, video services, cloud storage, and wide and local area networking. Additionally, EOUSA operates the Network Operations Center (NOC), which houses the core hardware infrastructure for each OCIO staff. The NOC also serves as the location for TechOne, EOUSA’s nationwide IT help desk. TechOne provides Tier 2 technical support to all USAOs.

This Statement of Objectives (SOO) is provided in support of a Request for Information (RFI) issued by the Executive Office for United States Attorneys (EOUSA). The purpose of this RFI is to conduct market research to identify commercial capabilities and solution approaches that may support a future acquisition for enterprise Storage as a Service, referred to as USAStorage 3.0. The RFI is for information gathering and planning purposes only and does not constitute solicitation.

2.0 BACKGROUND

EOUSA supporting United States Attorneys’ Offices (USAOs) nationwide requires a modernized, scalable, and secure enterprise storage solution to support evidentiary and mission data. Existing storage capabilities must evolve to address continued data growth, multi-location access requirements, continuity of operations, and enhanced governance, auditability, and security. EOUSA is seeking to understand how industry solutions deployed in FedRAMP-approved Government Cloud environments can meet these needs.

3.0 SCOPE

The scope of this SOO encompasses enterprise-wide storage capabilities supporting approximately 15,000 users across roughly 250 office locations. The solution must support an initial data footprint of nearly 20 petabytes, with the ability to scale indefinitely for usable capacity and support the ongoing growth of the USAOs at approximately two percent month over month, historically. The solution must support access to data from multiple geographic locations, at the nearest logical location to the user, and enable continuity of operations (COOP) for remote users and COOP processes.

4.0 OBJECTIVES

The following objectives define the desired outcomes for the USAStorage 3.0 capability.

Respondents are encouraged to describe how their solutions meet or exceed these objectives. Respondents are required to describe and detail, with specificity, their reliance on third parties and/or subcontractors to meet these requirements.

Respondents must include transparency information regarding any intended use of large language models (LLMs) (e.g., AI-assisted technologies) supplied by the contractor including its acceptable use policy, model/system/data card information, end user resources for the LLM, details regarding the mechanisms for end user feedback (see attached Department Local Clause DOJ-09 Large Language Models (MAR 2026).

Respondents are further required to clearly state any and all assumptions they may make in their response to each of the objectives and sections herein.

4.1 ARCHITECTURE AND ACCESS OBJECTIVES

The solution shall provide centralized, authoritative storage hosted in a Geo-dispersed FedRAMP-approved Government Cloud environment. Users must be able to access all authorized files from multiple locations, including office, remote, virtual private network (VPN), and Contingency of Operations (COOP) environments, through Server Message Block (SMB) functionality and interface. If on-site cache or edge components are utilized, the solution must ensure that all files remain directly accessible from the cloud-based service without dependency on local infrastructure. Any proposed solutions must comply with Local Clauses DOJ-02, DOJ-05, DOJ-07 regarding contractor privacy requirements, security protocols, and auditing controls. The solution will include and support deduplication and compression to reduce the overall cost. The primary user access method shall be SMB-based file shares compatible with Windows operating systems and existing user workflows. The solution shall provide LAN speed access to data regardless of geo-location of user in relation to the data when the accessing system is within the USAO network. The solution shall integrate with and be accessible to cloud-based Virtual Machines (VMs) for processing case data, hosted in the same Gov-cloud instance.

4.2 IDENTITY AND ACCESS CONTROL OBJECTIVES

The solution shall integrate with EOUSA enterprise identity services through OKTA. User authentication shall be performed at the Windows workstation level using PIV-based credentials. File and folder access permissions shall be enforced based on the authenticated user’s enterprise Active Directory management and group memberships.

The solution shall support enterprise-scale authorization and role-based access controls without requiring separate storage-specific credentials.

4.3 SECURITY AND COMPLIANCE OBJECTIVES

The solution shall operate entirely within U.S.-based Government Cloud regions. All system data, backups, replicas, and metadata shall remain within the United States. All contractor personnel who are directly accessing, administering and/or otherwise manipulating the system on behalf of the vendor in performance of this contract, shall be U.S Citizens based in the continental United States. The solution shall support FIPS 140-2 encryption of data at rest and in transit and comply with applicable DOJ security and privacy requirements.

4.4 AVAILABILITY, CONTINUITY, AND RESILIENCE OBJECTIVES

The solution shall provide high availability and resilience suitable for enterprise operations. The system shall support continued access to data during localized site outages and enable continuity of operations for remote users and COOP processes. The solution shall support a target service availability of 99.8 percent and recovery time objectives within 12 hours for district-level or backend infrastructure failures.

4.5 DATA MANAGEMENT AND LIFECYCLE OBJECTIVES

The solution shall support full data lifecycle management, including commonly used industry classifications for tiered storage options. The tiered storage shall align with hot, warm, cold, and archive with each tier defined by clear performance and access characteristics. For example, the hot tier shall provide near real-time access to data with sub-second latency and support high-throughput, frequent access workloads. The warm tier shall support regularly accessed data with moderate latency (typically within seconds) and balanced performance and cost. The cold tier shall be optimized for infrequently accessed data, with retrieval times ranging from minutes to hours and lower storage costs. The archive tier shall support long-term retention of rarely accessed data at the lowest cost, with retrieval times that may extend to several hours or longer.

The solution shall support retention enforcement, write-once-read-many (WORM) capabilities, litigation hold, and long-term evidentiary preservation. These capabilities shall be manageable through centralized administrative controls with attendant and commensurate reporting methods.

The proposed solution shall provide a scalable, high-performance storage capability designed to support future AI integrations, including preparedness for vectorization and large language model (LLM) workloads, across an initial dataset of approximately 20 petabytes, with the flexibility to expand as data volumes and mission needs grow, while ensuring compliance with Increasing Public Trust in Artificial Intelligence Through Unbiased AI Principles OMB M-26-04.. The solution must enable efficient ingestion, cataloging, and indexing of structured and unstructured data to facilitate advanced search, containerization, and vectorization use cases. The architecture should be extensible to incorporate advanced content analysis capabilities, including metadata extraction, classification, and enrichment, allowing future enhancements without significant reengineering.

4.6 MIGRATION OBJECTIVES

The solution shall support the migration of existing data from current enterprise storage platforms, including approximately 18 billion files and 20 petabytes of data, with continued growth during migration. Production migration activities shall be completed within a 24-month period. The migration approach shall minimize disruption to end users, support phased and parallel operations and ensure data integrity and continuity of access throughout the transition.

The solution shall include migration support for thirty-six (36) months, including six (6) months for solution design, architecture development, and beta/testing activities, twenty-four (24) months for full-scale production migration execution, and six (6) months for post-migration operational support and stabilization. At a minimum, the vendor shall ensure the continuous availability of no fewer than two (2) full-time U.S.-based personnel who are U.S. citizens for the entire period of performance, possessing the required technical expertise and any necessary clearances to support secure operations within a Government Cloud environment.

4.7 AUDIT, LOGGING, AND ANALYTICS OBJECTIVES

The solution shall provide comprehensive audit logging in accordance with Standard FISMA and NIST guidelines for file and folder access, administrative actions, and security-relevant events. Audit data shall be centrally available and support integration with EOUSA-approved Security Information and Event Management (SIEM) platforms.

The solution shall provide analytics and reporting capabilities, in both an aggregated fashion and broken out by the 250 geographical office locations, to support usage tracking, capacity planning, and operational oversight.

The solution shall provide a secure, GUI-based billing capability for the hybrid storage environment, delivering centralized and site-level visibility into cost and usage. It must include customizable dashboards for solution management to view near real-time, detailed summaries of all site charges and generate configurable reports. The system shall support API access to all billing and chargeable data for integration and export into editable formats. Site personnel shall have controlled, role-based access (RBAC) to online show back reports, with dashboards that present real-time storage usage and resource details (including tiered and archived data), while allowing management to optionally enable billing visibility. The billing function must also support automated show back reporting, including distribution of cost and usage summaries to designated stakeholders.

The solution shall also provide a GUI-based reporting system with both aggregated and granular visibility into storage usage across site offices. Reporting capabilities must include analysis by file count, size, owner, type, and last access date, as well as recursive folder-level insights with visual representations similar to hierarchical file explorers. The system shall present both individual folder metrics and rolled-up summaries across subfolders, including total size, file count, and access/modification timestamps.

Additionally, the platform must deliver storage utilization reports by site, including capacity consumption, user-level usage, file-type distribution, and access patterns over configurable time intervals (e.g., 30/60/90 days), enabling comprehensive monitoring and data management insights.

4.8 SUPPORT AND SERVICE MANAGEMENT OBJECTIVES

The solution shall include enterprise-grade operational support provided by U.S. Citizens and who are based in the continental United States. Support capabilities shall include 24x7 incident response and phone support using EOUSA ticketing system, system monitoring, and ongoing sustainment appropriate for a mission-critical DOJ environment. The solution shall support knowledge transfer and documentation sufficient to enable effective government oversight.

5.0 INFORMATION REQUESTED

This SOO is provided in support of an RFI. Detailed questions and response instructions will be provided in a separate RFI document.

6.0 DISCLAIMER

This RFI and SOO are issued for informational and planning purposes only and do not constitute a solicitation or a commitment by the Government. The Government is not obligated to issue a solicitation or award a contract as a result of this RFI. Responses are voluntary and will not be returned.

7.0 PROPRIETARY INFORMATION

The Government will protect proprietary information in accordance with applicable laws and regulations. Respondents shall clearly mark any proprietary data submitted in response to this RFI. The Government is not obligated to protect unmarked information.