P02-RFI v2.pdf

Department of Veterans Affairs Request for Information

January 27, 2025

1. Introduction

This Request for Information (RFI) is issued solely for market research and acquisition planning purposes in accordance with Federal Acquisition Regulation (FAR) 10 and FAR 15.201(e). This notice does not constitute a Request for Quote (RFQ), Request for Proposal (RFP), Invitation for Bid (IFB) or any commitment by the Government to issue a solicitation for or award a contract.

The Department of Veterans Affairs (VA) is conducting market research in support of a planned future solicitation for a Multiple Award Task Order Contract (MATOC) that is anticipated to include four (4) distinct service domains, as described in the attached draft Performance Work Statements (PWSs).

The objectives of this RFI are to:

• Assess current industry capabilities and capacity to support enterprise-scale IT infrastructure operations.

• Obtain industry feedback on the clarity, feasibility, and proposal-readiness of the attached draft PWSs

• Understand the socioeconomic composition of potential offerors to inform acquisition strategy.

• Identify potential risks, best practices, and opportunities to enhance competition and execution prior to RFP issuance.

Responses to this RFI are not offers and will not be accepted by the Government to form a binding contract.

2. Disclaimer

• The Government will not reimburse any costs incurred in responding to this RFI.

• Submission of a response is voluntary, and non-response will not preclude participation in any future solicitation.

• The Government may use the information received to refine requirements, acquisition strategy, and solicitation structure.

• The Government does not intend to provide individual feedback or engage in follow-up discussions.

• All submitted information becomes Government property and will not be returned.

• Respondents are responsible for clearly marking any proprietary, restricted, or competition-sensitive information.

• The Government is not responsible for any cost incurred by industry in providing information.

3. Anticipated Acquisition Overview (Planning Information Only)

The VA is contemplating a competitive MATOC to support enterprise IT infrastructure operations across three service domains described in the attached draft PWSs. The Government is seeking industry input to validate whether the scope, structure, and performance expectations are clear, executable, and conducive to robust competition.

Nothing in this section should be construed as final or binding.

4. Response Instructions

4.1 Submission Deadline

Responses are due no later than February 6, 2026, at 4:00 PM Eastern Time.

4.2 Submission Method

Responses shall be submitted electronically to:

• anthony.araujo@va.gov

• claudetta.smith@va.gov

Email Subject Line:

Response to RFI Number 36C10A25Q0090 v2

4.3 Response Structure and Page Limits

To facilitate meaningful market research while minimizing industry burden, respondents shall organize their submissions using the structure below.

Section A – Capability Statement

• Maximum Length: Five (5) pages total

• Purpose: To assess industry experience, capacity, and technical capability relevant to the draft PWS domains.

Section B – Industry Feedback on Draft PWSs

• Maximum Length: Five (5) pages total

• Purpose: To obtain candid, actionable feedback on the clarity, feasibility, and proposal-readiness of the draft requirements.

Section C – Administrative Information

• No page limit

• Does not count toward page limits mailto:anthony.araujo@va.gov mailto:claudetta.smith@va.gov

• May be submitted in table or bullet format.

4.4 Formatting Requirements

• File format: Microsoft Word

• Page size: 8.5 x 11 inches (landscape permitted for charts/tables)

• Font: Arial, 12-point

• Margins: 1 inch

• File size: Not to exceed 40 MB

• Pages must be numbered and labeled with the RFI number

• Charts, tables, and graphics count toward applicable page limits

5. Requested Response Content

Section A – Capability Statement (Up to 5 Pages)

Respondents shall provide a concise capability statement describing their organization’s ability to perform one or more of the draft Performance Work Statement (PWS) domains. Respondents are encouraged to clearly identify the specific domain(s) addressed.

The capability statement shall focus on the respondent’s experience designing, leading, and delivering enterprise-level solutions, as opposed to performing discrete or staff-augmentation tasks under the direction of another entity.

A.1 PWS Domain(s) Addressed

Identify the draft PWS domain(s) for which your organization is capable of providing services.

• Application Hosting Compute & Storage

• Application Services

• Datacenter Facility Operations

• Infrastructure Engineering & Operations

A.2 Relevant Enterprise Experience (Prime-Level Leadership and Delivery)

Describe your organization’s relevant experience delivering enterprise-scale solutions for large, complex organizations (e.g., large federal agencies or commercial enterprises with multi billionaire-dollar operations of comparable scale and complexity). Responses are not required to demonstrate experience across all domains; responses should focus on the domain(s) most relevant to the respondent’s demonstrated capabilities.

Responses shall clearly distinguish experiences where the respondent led and owned the solution from those where the respondent provided support or execution-only services.

At a minimum, address the following:

• Scope and Complexity

Describe the size, scope, and complexity of the environments supported, such as enterprise infrastructure operations, hybrid or multi-cloud environments, geographically dispersed facilities, or mission-critical systems.

• Role and Level of Responsibility

Clearly identify your organization’s role (e.g., prime contractor, lead systems integrator, solution architect).

Describe your responsibility for strategy development, architectural design, technical decision-making, governance, and trade-off decisions, as applicable.

• Outcomes and Impact

Summarize measurable outcomes achieved through your leadership, such as:

o Cost savings or cost avoidance o Improvements in performance, availability, resiliency, or scalability o Modernization or operational efficiency gains

• Lessons Learned

Identify key lessons learned from delivering enterprise-level solutions and explain how those lessons inform your current technical, operational, and management approach.

Note: The Government is seeking to understand respondents’ experience owning and delivering enterprise outcomes, not solely executing tasks or providing staff support under another organization’s direction.

A.3 Enterprise Scale and Technical Capability

Describe your organization’s capability to support enterprise-scale operations, including:

• Size and complexity of environments supported

• Experience with hybrid and multi-cloud architectures

• Use of automation, monitoring, and performance management tools

• Ability to scale services while maintaining reliability, security, and performance

A.4 Performance-Based Delivery Experience

Describe your experience delivering services under performance-based contracts, including:

• Use of Service Level Agreements (SLAs), Key Performance Indicators (KPIs), or other performance metrics

• Governance, reporting, and continuous improvement practices

• Experience meeting acceptance criteria and driving measurable outcomes

A.5 Summary

Provide a brief summary highlighting why your organization is well-positioned to successfully perform the identified PWS domain(s) at the enterprise scale contemplated.

Section B – Industry Feedback on Draft PWSs (Up to 5 Pages)

The VA seeks specific, actionable feedback on the attached draft Performance Work Statements. Please cite section and paragraph numbers where applicable and provide plain-language recommendations.

1. Proposal-Ability (Go / No-Go)

As written, would your company submit a proposal if this requirement were released as an RFP? Why or why not? Identify the top three (3) enablers or blockers (e.g., scope clarity, SLAs, acceptance criteria, staffing assumptions, OCI concerns, data rights, period of performance).

2. Clarity and Completeness

Is the PWS sufficiently clear, complete, and internally consistent to allow accurate pricing and execution? Identify ambiguous, conflicting, overly prescriptive, or missing requirements and recommend specific wording improvements.

3. Performance Metrics and Acceptance

Are the performance metrics, SLAs, and acceptance criteria measurable, realistic, and verifiable? Recommend thresholds, targets, observation methods, or acceptance checklists that improve enforceability.

4. Key Risks and Implementation Challenges

Identify key risks, assumptions, or challenges that could impede successful performance. Recommend specific changes that would mitigate risk and improve feasibility.

5. Ability to Scale

Describe your experience supporting enterprise-scale infrastructure operations, including:

• Size and complexity of environments supported

• Hybrid and multi-cloud experience

• Automation, monitoring, and reliability practices

Section C – Administrative Information (No Page Limit)

Provide the following information:

Cover Sheet

• Company name and address

• Point of Contact (name, phone number, email)

• SAM UEI

• Company website

Socioeconomic Status

Identify your current socioeconomic category(ies) as registered in SAM, including (if applicable):

• Small Business

• 8(a)

• HUBZone

• SDVOSB

• VOSB

• WOSB / EDWOSB

• Small Disadvantaged Business

• Large Business

Also identify size status under NAICS 541512 or 541513:/ PSC DC01.

Existing Contract Vehicles

Identify any Multiple Award Contract vehicles available for Government use, including:

• Vehicle name

• Contract number

• Award date

6. Place Of Performance (Planning)

Services may be required at Government facilities and remote/cloud environments.

Primary locations may include (subject to change):

• Austin, TX

• Hines, IL

• Philadelphia, PA

• Falling Waters, WV

• Quantico, VA

• Additional regional and remote locations as required

7. Proprietary Information

All proprietary or company-confidential information shall be clearly marked on each page containing such information.