RFI ERP 1.16.26.pdf

Request for Information (RFI)

The Department of Veterans Enterprise Resource Planning (ERP)

1. Introduction

This RFI is for planning purposes only and shall not be considered an Invitation for Bid, Request for Task Execution Plan, Request for Quotation or a Request for Proposal. Additionally, there is no obligation on the part of the Government to acquire any products or services described in this RFI. Your response to this RFI will be treated only as information for the Government to consider. You will not be entitled to payment for direct or indirect costs that you incur in responding to this RFI. This request does not constitute a solicitation for proposals or the authority to enter into negotiations to award a contract. No funds have been authorized, appropriated or received for this effort. Interested parties are responsible for adequately marking proprietary, restricted or competition sensitive information contained in their response.

The Government does not intend to pay for the information submitted in response to this RFI.

The North American Industry Classification System (NAICS) for this requirement is 541519.

Please reference previous RFI 36C10B26Q0133.

2. Submittal Information:

All responsible sources may submit a response in accordance with the below information.

There is a page limitation for this RFI of 12 pages. The Government will not review any other information or attachments included in excess of the 12-page limit. NO MARKETING MATERIALS ARE ALLOWED AS PART OF THIS RFI. Generic capability statements will not be accepted or reviewed. Your response must include the following:

a. Interested Vendors shall at a minimum, provide the following information in the initial paragraph of the submission:

Name of Company

Address

Point of Contact

Phone Number

Fax Number

Email address

Company Business Size and Status

For VOSB and SDVOSBs, proof of verification in VetCert.

NAICS code(s)

Socioeconomic data

Data Universal Numbering System (DUNS) Number or Unique Entity ID

Existing Contractual Vehicles (GWAC, FSS, or MAC)

b. Provide a summary of your capability to meet the requirements and questions described in section c

• Ability to meet solution requirements identified below

• For each product identified, submit technical documentation demonstrating the products capability to meet the functional requirement.

• Describe the terms of your SaaS agreement.

• Provide your Federal Risk and Authorization Management Program (FedRAMP high) certification status and risk level.

• Provide a list of your available license packages/suites.

c. Your company’s intent and ability to meet the set aside requirement in accordance with VAAR 852.219-73 VA Notice of Total Set-Aside for Verified Service-Disabled Veteran- Owned Small Businesses and 13 CFR §125.6, which states the contractor will not pay more than 50 percent of the amount paid by the Government to it to firms that are not SDVOSBs.

1. Transition Detail and Timeline: Describe how you would transition VA from ServiceNow to your proposed solution? Include steps, the approximate transition timeline, key milestones, how you will ensure minimal disruption to VA services, and whether or not you have successfully made this transition with organizations similar in size to the VA; please provide details as to which Federal Agencies and/or private organizations and when.

2. Scalability and Performance: How does your solution handle scalability and performance for over 600,000 users, particularly in managing large workflows, extensive data tables, large volume reporting and critical processing needs? For example, include your approaches to load balancing, performance optimization, high availability, and disaster recovery, including examples or case studies of successful implementations in large-scale environments.

3. Integration Capabilities: Describe your experience with integrating your platform with federal systems, specifically utilizing secure APIs? Provide detailed information on your use of pre-built connectors (e.g., Power BI connectors, Jira

Spoke, Splunk, Nuvolo, EHRM), examples of custom integrations you have successfully implemented, and any identified gaps in integration capabilities compared to ServiceNow.

4. Data Migration: How would you migrate VA data from ServiceNow to your proposed solution? Include steps to ensure data quality, integrity, and security.

Address handling of sensitive data (PII, PHI), custom applications, encrypted fields and role-based access controls.

5. Compliance and Security: Does your proposed solution comply with regulatory compliance standards and framework such as FedRAMP High, FISMA, HIPAA and 508?

6. Training and Organizational Change Management: Describe your experience in training and ensuring seamless adoption for large-scale user bases with up to 600,000 users.

7. Reporting and Analytics: Describe your platform’s reporting and analytics capabilities, including pre-built reports, customizable dashboards, and data visualization tools. How does it support real-time updates, report generation, KPI tracking, and predictive analytics? How customizable are these for non-technical users?

8. AI Capabilities: How does your platform use AI to enhance the enterprise resource planning (ERP) platform? Provide examples of generative and agentic AI functionalities for example ticket triage, virtual agents, predictive analytics, and real-time assistance Is the AI capability included in the standardized license or is a separate license required for AI functionality?

9. Professional Services and Customization: Describe how you have provided professional services for platform implementation, optimization, and customization that involved developing custom applications, workflows, integrations, and managing large datasets, while maintaining a user friendly experience. Please provide where, when and the scale.

10. Functionality and Vendor Risk Management: Does your OOB solution meet all the requirements of the draft PWS. If not provide what sections you cannot meet.

How does your platform support comprehensive vendor risk management, including centralized vendor management, automated risk assessments, monitoring, issue management, and GRC integration?

Responses are due no later than 4PM EST, January 27th, 2026 via email to John A Adamitis, Contract Specialist at john.adamitis1@va.gov and Heather Utt, Contracting Officer at heather.utt@va.gov. Please note “ERP” in the subject line of your response. Mark your response as “Proprietary Information” if the information is considered business sensitive. The email file size shall not exceed

5 MB.