Lighthouse AdvisorySLED AI Adoption Intelligence
← Back to results

From the VAST Data edition of October 31, 2026

Public-sector association guidanceEmergingPeer review status unknownNew this fortnight

New York's Empire AI issues a $160M Gamma RFI that names Beta's 20 PB of VAST as incumbent storage Gamma must interoperate with

Empire AI Consortium, Inc. (New York State public-private research consortium; University at Buffalo host site) · State-sponsored shared AI research computing / higher education · United States (Buffalo and Amherst, New York)

Publisher
GovTribe (text version of Empire AI RFI No. EAI-2026-102902)
Original publication
2026-10-29
Source retrieved
2026-11-01
Read original source

What happened

Empire AI's Gamma RFI (issued October 29, 2026; responses due December 4) seeks input on up to 5 MW of AI/HPC compute and white space for its UB North Campus facility, with a roughly $160 million budget split across Gamma and Delta tranches. It records that Beta (online August 2026) includes 20 PB of VAST and 10 PB of DDN storage, and asks respondents to describe storage capacity, sustained throughput, metadata performance, data protection and integration with the existing VAST and DDN systems, whether or not Beta is relocated. It reports 1,631 active users, 314 projects and over 80 percent utilization on Alpha and Beta.

Why it matters

Direct state and higher-education relevance: a New York State-established consortium serving ten institutions is planning its next AI system, and VAST is the incumbent all-flash platform. The RFI is vendor-neutral, so it signals an interoperability and data-strategy requirement, not a VAST award.

Evidence and measured results

Primary procurement document from a state-sponsored public-private consortium (requirements and context, not an evaluation). Retrieved as GovTribe's text version (pages 1-24 of 40 shown); posting date and responses-due date corroborated by the Govly listing of New York State Contract Reporter #2140363. UB CCR's Empire AI user guide independently states that no data on Empire AI systems is backed up. No VAST performance or outcome data is provided.

Limitations and uncertainty

The RFI is not a solicitation and awards nothing; naming VAST reflects the installed base, not a preference. The text was read through a third-party portal's extracted version, which showed only part of the 40-page document; the original portal posting requires an account. Interpretation (not source finding): interoperability language may favour incumbents in a later RFP, but Empire AI explicitly states it does not prescribe a manufacturer.

Put this evidence to work

Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-31; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.

Sales

Role takeaway
Customer problem
A state AI research consortium must expand capacity while keeping data usable across an incumbent VAST/DDN system and a new facility.
Stakeholders
  • Empire AI Consortium leadership and designated procurement contact
  • UB Center for Computational Research operations
  • Member-institution research computing leads
  • Research security and compliance officers
Discovery questions
  • Will Beta be relocated, and how will data be split if it is not?
  • What data-protection and backup posture is required for Gamma?
  • Which regulated-data workloads (HIPAA, NIST 800-171, ITAR) must Gamma storage support?
Value hypothesis
Interoperating with the incumbent VAST namespace could reduce data movement and retraining for 1,600+ users; this is a hypothesis, not a finding of the RFI.
Potential engagement
Support a respondent's storage and data-strategy section for the RFI or a subsequent RFP, within Procurement Lobbying Law contact rules.
Unsupported claims
  • That Empire AI will select VAST for Gamma
  • Any measured VAST performance on Beta
  • Cost savings from interoperability

Pre-sales engineering

Role takeaway
Fit
Relevant to multi-site academic AI clusters that must extend an incumbent all-flash tier alongside a parallel file system.
Architecture and integration
Gamma storage must integrate with Beta's 20 PB VAST and 10 PB DDN over a campus link if Beta is not relocated; NYSERNet and UB links exist at 100 Gbps each for Beta.
Prerequisites
  • Decision on Beta relocation
  • Reference workloads promised for the RFP
  • Data-protection and backup requirements
Constraints
  • Campus link addresses bandwidth but not latency
  • No current backups on Empire AI systems
  • Procurement Lobbying Law restricts contact during the restricted period
Security
Regulated-data support (HIPAA, NIST SP 800-171/800-53, ITAR), identity federation, segregation, encryption and audit logging are required and must be demonstrated, not assumed.
Proof of value
  • Measure sustained throughput and metadata rates with Empire AI reference workloads
  • Test cross-site data access latency between Beta and Gamma
  • Validate backup and restore for a regulated-data tier

Delivery

Role takeaway
Work
Plan Gamma storage deployment and migration or bridging from Beta while sustaining allocation, quota and purge operations.
Dependencies
  • Base building completion (Q4 2027)
  • RFP issuance (about January 15, 2027)
  • Member-institution allocation processes
Ownership
Empire AI Consortium with UB CCR as host operator, or a managed-service respondent if chosen.
Skills and adoption
Operators need multi-site data management and regulated-data controls; users need guidance on where data lives across Beta and Gamma.
Governance checkpoints
  • Beta relocation decision
  • Regulated-data tier approval
  • Acceptance testing before Gamma power-on
Acceptance criteria
  • Proposed: documented recovery objectives and tested restore for project data
  • Proposed: measured cross-site access latency within agreed limits
  • Proposed: per-institution storage accounting reported in the allocation system
Risks
  • Data split across sites degrading workflows
  • Unprotected research data with no backups
  • Incumbent lock-in perceptions affecting procurement fairness

Implementation considerations

Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.

Architecture and integration

What must connect, and where does the AI sit in the workflow?

Gamma storage must interoperate with Beta's VAST and DDN tiers. If Beta stays in the downtown CCR data center, data and workflows may split across sites connected by a campus link that the RFI notes addresses bandwidth but not latency, so namespace, replication and data-placement design become central.

Governance

Who approves, reviews and stays accountable for outcomes?

Vendor-neutral RFI under New York's Procurement Lobbying Law (restricted contacts); responses are subject to FOIL. Institution-level service-unit allocations and fair-share scheduling govern access; the RFI asks for accounting and reporting by institution and project.

Security and privacy

What data, permissions and controls need testing?

Gamma must support sensitive and regulated research data (HIPAA, NIST SP 800-171 and 800-53, ITAR) with identity federation, segregation, encryption and audit logging. Current Empire AI user guidance says no data is backed up, a gap any regulated-data tier would need to close.

Accessibility and workforce

Who is affected, and what skills or accommodations follow?

Users range from experienced HPC practitioners to domain scientists new to accelerated computing; only 36 percent of approved projects have activated usage, so onboarding and training remain a constraint.

Procurement

What should contracts, pricing and exit terms secure?

Indicative pricing must include three-year support with optional five-year terms and software licensing terms at expiration; white space work carries MBE/WBE/SDVOB goals and possible PLA. Storage vendors will likely participate via integrators or OEM teams.

Operating model

Which teams own the service once it runs?

Empire AI is weighing owner-operated, managed-service or hybrid operation; institution-level service-unit allocations with fair-share scheduling continue.

Publication history

  1. 2026-10-31VAST Data · Issue 032 resources
Read preserved resource versions (JSON)

Stable resource ID: empire-ai-gamma-rfi-vast-interoperability-20261029