DA01--Enterprise Resource Planning (ERP), System Integrator (SI) Information/Discovery Session

1. VA intends to hold information/discovery sessions with respondents that will serve as the prime contractor who will be responsible as the System Integrator and provide all required licenses and products as a service, by offering their COTS product or solution. Vendors shall identify all OEMs they would intend to partner with to meet the solution. The solution shall meet VA's ERP requirements by acting as the Systems Integrator (SI) responsible for implementing and integrating the proposed solution. Vendors responding solely as subcontractors or without the capability to serve in either of the aforementioned capacities should not respond for inclusion in these sessions. 2. Requirement Status: VA's ERP requirements remain in draft status and are currently undergoing further development, refinement, and revision. Interested vendors should be aware that the Government anticipates changes to the requirements outlined in the Draft Performance Work Statement (PWS) previously provided through earlier RFIs. The previously posted Draft PWS should not be considered final or representative of the Government's finalized requirements. Information gathered through ongoing market research and discovery sessions may further inform the development of the acquisition requirements and strategy. VA plans to post a new draft PWS prior to RFP release. 3. If you have responded to the original posting of RFI 36C10B27Q0032 and confirmed the above there is no need to respond again to this RFI amendment. 4. The Due date remains the unchanged. 10.9.26 3:00 PM EST. 5. For background, the current PWS reflects an approach in which licenses are procured through a Systems Integrator (SI) as a managed service. Platform Architecture: The requirement for a single platform to natively provide all functionality has been removed. SIs may propose multi-tool solutions, provided all requirements are met. Migration Approach: The Government no longer requires that all existing customizations be migrated prior to transitioning to a greenfield environment. A hybrid approach is now permitted, in which the SI may implement a greenfield solution first and subsequently migrate scoped applications. The Government is continuing to develop and refine the scope and functional requirements for these applications, which will be reflected in the forthcoming Request for Proposals (RFP). Systems Integrators (SIs) offering native solutions that address the functionality of applications ultimately included within the scope of the procurement may explain those capabilities. Data Retention: The solution shall retain data in accordance with applicable NARA-approved records retention schedules and VA records management policy [cite specific GRS/VA schedule number if known]. The System Integrator (SI) shall document the retention period, archival method, and disposition process for each data category within the system. Data Reporting: The solution shall provide data reporting and analytics capabilities. Reporting queries, dashboards, and ad hoc analytics shall not degrade the performance of the production environment. Data Migration: Full data migration from legacy systems to the new ERP tool solution is no longer a mandatory requirement. SIs may propose alternative methods of legacy data access in reportable and usable format in lieu of complete migration (e.g., federated access, API-based retrieval, or incremental/selective migration). Any proposed alternative must: Preserve compliance with NARA retention requirements above; Support the production reporting capability described above; Be clearly documented with associated risks, limitations, and long-term support implications. Transition Timeline: The current requirement is a 9-month transition period, consisting of onboarding and implementing the SI's proposed solution. ServiceNow (SN) Licensing: Where an SI proposes a re-platforming solution that may include the incumbent tool, the SI will be responsible for any residual licenses or components required after expiration of the current contract (September 2027). SIs proposing such a solution must include a cost-reduction plan that migrates functionality to the new platform over time, retaining only those incumbent components that cannot reasonably be eliminated. Super Intelligence: Incorporation of Super Intelligence capabilities is now a required element of the proposed solution rather than an optional feature.

1. VA intends to hold information/discovery sessions with respondents that will serve as the prime contractor who will be responsible as the System Integrator and provide all required licenses and products as a service, by offering their COTS product or solution. Vendors shall identify all OEMs they would intend to partner with to meet the solution. The solution shall meet VA's ERP requirements by acting as the Systems Integrator (SI) responsible for implementing and integrating the proposed solution. Vendors responding solely as subcontractors or without the capability to serve in either of the aforementioned capacities should not respond for inclusion in these sessions. 2. Requirement Status: VA's ERP requirements remain in draft status and are currently undergoing further development, refinement, and revision. Interested vendors should be aware that the Government anticipates changes to the requirements outlined in the Draft Performance Work Statement (PWS) previously provided through earlier RFIs. The previously posted Draft PWS should not be considered final or representative of the Government's finalized requirements. Information gathered through ongoing market research and discovery sessions may further inform the development of the acquisition requirements and strategy. VA plans to post a new draft PWS prior to RFP release. 3. If you have responded to the original posting of RFI 36C10B27Q0032 and confirmed the above there is no need to respond again to this RFI amendment. 4. The Due date remains the unchanged. 10.9.26 3:00 PM EST. 5. For background, the current PWS reflects an approach in which licenses are procured through a Systems Integrator (SI) as a managed service. Platform Architecture: The requirement for a single platform to natively provide all functionality has been removed. SIs may propose multi-tool solutions, provided all requirements are met. Migration Approach: The Government no longer requires that all existing customizations be migrated prior to transitioning to a greenfield environment. A hybrid approach is now permitted, in which the SI may implement a greenfield solution first and subsequently migrate scoped applications. The Government is continuing to develop and refine the scope and functional requirements for these applications, which will be reflected in the forthcoming Request for Proposals (RFP). Systems Integrators (SIs) offering native solutions that address the functionality of applications ultimately included within the scope of the procurement may explain those capabilities. Data Retention: The solution shall retain data in accordance with applicable NARA-approved records retention schedules and VA records management policy [cite specific GRS/VA schedule number if known]. The System Integrator (SI) shall document the retention period, archival method, and disposition process for each data category within the system. Data Reporting: The solution shall provide data reporting and analytics capabilities. Reporting queries, dashboards, and ad hoc analytics shall not degrade the performance of the production environment. Data Migration: Full data migration from legacy systems to the new ERP tool solution is no longer a mandatory requirement. SIs may propose alternative methods of legacy data access in reportable and usable format in lieu of complete migration (e.g., federated access, API-based retrieval, or incremental/selective migration). Any proposed alternative must: Preserve compliance with NARA retention requirements above; Support the production reporting capability described above; Be clearly documented with associated risks, limitations, and long-term support implications. Transition Timeline: The current requirement is a 9-month transition period, consisting of onboarding and implementing the SI's proposed solution. ServiceNow (SN) Licensing: Where an SI proposes a re-platforming solution that may include the incumbent tool, the SI will be responsible for any residual licenses or components required after expiration of the current contract (September 2027). SIs proposing such a solution must include a cost-reduction plan that migrates functionality to the new platform over time, retaining only those incumbent components that cannot reasonably be eliminated. Super Intelligence: Incorporation of Super Intelligence capabilities is now a required element of the proposed solution rather than an optional feature.