VA Procurement CWS RFI Question Responses-Nov 17-2025.pdf

VA Procurement CWS RFI Question Responses

November 17, 2025

1. Could the government confirm which VA office will be championing the implementation of this project?

Response – VA Office of Acquisition and Logistics (OAL)

2. Will this tool be used only for VHA contracts or for all contracts across the 3 administrations?

Response – All of VA Procurement, not just administrations

3. What is the size and scope of the user base?

Response – VA is the largest civilian federal procurement workforce.

4. The government requests the ability “to migrate data from current VA systems to the COTS product” under number 4. Could the government please list/describe the VA’s current systems, and the scale of the data migration required?

Response – No official decision has been made as to what systems will be replaced. VA currently uses several systems for acquisition activities including Automated Acquisition Management Solution (AAMS) and CGI Momentum. This could be a large-scale migration of metadata and files in cloud storage that exceeds millions of records and hundreds of terabytes.

5. Do the government have specific efficiency targets it is most eager to address?

Response - No

6. Do the government have requirements for preserving a human-in-the-loop within specific AI-assisted decision workflows? If yes, which workflows and/or decisions?

Response – To be determined. We are seeking to learn what capabilities and flexibilities exist.

7. Under Item 10 - Functionalities, could the government clarify whether ‘Milestones’ pertains to contract action milestones from planning to award or contract PWS milestones for deliverables?

Response – Procurement action milestones within the system

8. Is there an approximate date range for which the Industry Day may be scheduled?

Response – To be determined

9. Is the 25-page limit inclusive of the front matter (i.e., cover page and Table of Contents) or does the 25-page limit exclude cover page and TOC?

Response – The 25-page limit includes the front matter.

10. Is the 25-page limit inclusive of the front matter (i.e., cover page and Table of Contents) or does the 25-page limit exclude cover page and TOC?

Response – The 25-page limit includes the front matter.

11. Is this Contract Writing System modernization effort related to the planned Budget Tracking Tool replacement effort, or are these separate initiatives within VA's modernization portfolio?

Response – This is a separate initiative and not related.

Current System Environment

Q1. Which existing contract writing or acquisition systems (e.g., PRISM, eCMS, IFCAP modules) are currently in use at VA, and are these systems intended to be fully replaced or integrated with the proposed CWS?

Response – No official decision has been made regarding which systems will be replaced. VA currently uses several systems for acquisition activities, including Automated Acquisition Management Solution (AAMS) and CGI Momentum.

Integration with Financial Systems

Q2. Can VA provide additional details on the planned integration approach with iFAMS/Momentum; for example, whether data exchange will occur via web services, APIs, or an intermediary integration layer?

Response – Data exchange will occur via a Service Bus.

Cloud and Hosting Requirements

Q3. Does VA have a preferred cloud deployment model (e.g., FedRAMP Moderate or High;

AWS GovCloud; Azure Government), and will VA require reuse of an existing FedRAMP authorization?

Response – Azure Government. Yes.

Security and ATO Expectations

Q4. Will the VA require a separate Authority to Operate (ATO) under VA’s RMF process, or will a valid FedRAMP authorization package satisfy the security accreditation requirement?

Response – Yes, a separate ATO will likely be required.

Data Migration

Q5. Can VA share information on the estimated volume and structure of legacy contract data (including attachments) to be migrated, as well as whether data dictionaries or schemas will be provided?

Response – This could be a large-scale migration of metadata and files in cloud storage that exceeds millions of records and hundreds of terabytes.

Functional and Workflow Customization

Q6. Does VA anticipate requiring workflow customization at the organizational or VISN level, or will a standardized enterprise configuration be preferred?

Response – We are interested in learning about the capabilities that exist.

Please let us know whether your proposed solution is capable of doing one or both.

Reporting and Analytics

Q7. Does VA currently utilize enterprise analytics tools (e.g., Power BI, Tableau, Qlik) that the CWS should integrate with, or should the solution include an embedded analytics capability?

Response – Yes, but we want to avoid being locked into a specific tool. Our goal is to ensure that any reporting solution we have can connect seamlessly to the data.

User Base and Training

Q8. Approximately how many total and concurrent end users are expected across VA, and does VA prefer a train-the-trainer model or direct contractor-led end-user training?

Response – VA is the largest civilian federal procurement workforce. The VA is interested in both types of training.

Industry Day and Next Steps

Q9. Will VA host an Industry Day for vendors following RFI review, and if so, will participation be a prerequisite for responding to any subsequent solicitation?

Response – To be determined. Participation in an industry day will not be a prerequisite for solicitation.