R499--Request for Information Digital GI Bill Automation and Modernization

RFI Digital GI Bill and Education Services Automation & Modernization
2

DIGITAL GI BILL AND EDUCATION SERVICES
DEPARTMENT OF VETERANS AFFAIRS (VA) VETERANS BENEFITS ADMINISTRATION (VBA)
Digital GI Bill and Education Services Automation & Modernization
Date: July 16, 2026
Request for Information (RFI)




Request for Information Digital GI Bill and Education Services Automation and Modernization
Introduction: The Department of Veterans Affairs (VA) is seeking industry input on solutions to complete the remaining development and modernization of the Digital GI Bill (DGIB) platform, transition the platform from its current Managed Service Vendor to VA-owned/managed infrastructure, and continue advancing automation across DGIB's claims processing capabilities. The Government aims to transform the DGIB ecosystem into a secure, scalable, cloud-based enterprise platform. This platform will facilitate comprehensive claims processing, optimize automation where feasible, lessen dependence on outdated systems, improve the experiences of both Veterans and employees, and offer the adaptability needed for future legislative, policy, and technological shifts. Through this Request for Information (RFI), the VA is seeking insights from industry on the most effective technical and acquisition strategies to reach this goal. This includes suggestions on solution architecture, implementation plans, and contract frameworks.
This is an RFI issued for conducting market research and for eliciting industry input as to the Government s requirement for DGIB and Education Services Automation and Modernization. This RFI constitutes neither a Request for Proposal/Quote (RFP/RFQ) nor a guarantee that one will ever be issued by the Government; furthermore, it does not commit the Government to contract for any services described herein. Please do not include a price or proposal in your response.
The VA is not, at this time, seeking proposals or quotes, and therefore will not accept, review, or evaluate unsolicited proposals or quotes received in response hereto. This notice is not to be construed as a commitment on the part of the Government to award a contract/order, nor does the Government intend to pay for any information submitted because of this request. The Government does not reimburse respondents for any costs associated with the submission of the information being requested, or reimburse expenses incurred for responses to this RFI. Please do not include pricing information in your response.
The information provided may be used by VA in developing its acquisition strategy and Performance Work Statement (PWS). Not responding to this RFI does not preclude participation in any future RFP/RFQ, if issued. Any information submitted by respondents to this RFI is strictly voluntary; however, any information received shall become the property of the Government and will not be returned to the respondent. Interested parties are responsible for adequately marking proprietary, restricted, or competition sensitive information contained in their response. This is a request for information and does not obligate the Government in any way, nor does it commit the Government to any specific course of action. RFI responses will not be evaluated for technical merit and will not provide any competitive advantage in any potential future procurements.
NAICS Code: VA is considering NAICS 541512 (Computer Systems Design Services). Industry feedback on NAICS capability is welcome.
Background: The DGIB program administers education benefits under Chapters 30, 33, 35, and 1606 of Title 38, U.S. Code, serving Veterans, servicemembers, and their dependents annually. The program processes more than $12 billion in education benefits each year and represents one of VA's most mission-critical technology platforms. What is a claim ? In the DGIB context, a claim is a request submitted by a Veteran, servicemember, or eligible dependent for determination and/or payment of education benefits under Title 38, U.S. Code. There are two types of claims: Original Claim The initial application or request for benefits the first entry point into education benefits. Based on the specific benefit being applied for, eligibility rules are run to validate service history, eligibility, and entitlement. This results in one of two decisions: Certificate of Eligibility (COE), or a denial
Supplemental Claim Every action that occurs after an Original Claim has been established. Supplemental claims can include additional eligibility information, enrollment certification from a school or training provider, or any other type of follow-on request. These result in a determination of eligibility (benefit level, payment rates, etc.) award, and/or disbursement of payment.
Claim Cycle (for DGIB purposes) A claim cycle begins at the entry point of an application or supplemental action item using either My Education Benefits (MEB) or Enrollment Manager (EM) for enrollment certifications and ends at successful delivery of payment information to VA's payment processing system, eMPWR. All claims received, via MEB or EM, are processed through one of two systems: the Digital GI Bill Ch33 Processing System for Chapter 33 claims or Benefits Manager (BM) for all non-Chapter 33 claims. Regardless of which system processes the claim, each benefit chapter has its own distinct rules governing eligibility and payment determinations. Claims may be resolved through full end-to-end (E2E) automation, partial automation, or manual adjudication by a Veteran Claims Examiner (VCE). Automation levels for claims are defined as: Automated Claim: A claim received, processed and authorized by automated adjudication without any human intervention.
Partially Automated Claim: A claim where automation initiates the claim, applies processing rules, but must be authorized manually (by a human).
Manual Claim: A claim received or generated outside of DGIB (EM or MEB) and created and authorized by manual adjudication.
The current DGIB operating environment relies on a Managed Service Vendor (MSV) responsible for application development, infrastructure hosting, and operations and maintenance across a complex, mature platform that includes 700+ repositories, 50+ databases (Oracle 19C, PostgreSQL 14, Amazon Redshift, DynamoDB), and extensive CI/CD infrastructure. Other current systems configuration includes: 76 EC2 compute instances (Windows Server and Red Hat Enterprise Linux), 590+ compiled software artifacts , 30+ S3 object storage buckets and 90+ vendor, open-source, and hardware licenses. The system currently holds an active Authority to Operate (ATO) in a vendor-managed AWS GovCloud environment. VBA is conducting market research to modernize, migrate, and enhance the DGIB platform in alignment with VA's cloud-first strategy and broader enterprise modernization goals. VBA is exploring five primary capability areas, described in the Requirement section below, and is seeking industry input to inform its evaluation of potential approaches.
Current Systems
The DGIB ecosystem consists of legacy systems slated for replacement and modern systems built to replace them but not yet at full operational capability. DGIB processes more than $12 billion in education benefits annually. Automation rates vary by chapter and have improved meaningfully year-over-year, with an overall automation rate of approximately 60% across all benefit chapters. Automated claims are resolved in approximately one day across all chapters, compared to 9.5 18.7 days for manually adjudicated claims, depending on chapter. Quality across both pathways have an overall automation quality rate of 95+%.
Systems Being Replaced (Legacy)
The Image Management System (TIMS) Legacy claims processing queue and work-assignment tool. Used by Veteran Claims Examiners to receive, prioritize, and work claims. Function to be replaced by Workload Manager.
Web Enabled Approval Management System (WEAMS) Legacy system supporting school and training program approval i.e., determining and tracking which institutions and programs are approved for GI Bill benefit use. Function to be replaced by Approval Manager.
eForce Legacy system also supporting school/program approval case management, operating alongside WEAMS. Function to be replaced by Approval Manager.
Systems Being Built/Matured (Current MVP State)
My Education Benefits (MEB) MEB is VA's enterprise digital platform that modernizes the delivery of education benefits by providing a secure, user-friendly application experience for Veterans, service members, and eligible beneficiaries. MEB leverages automated decisioning to process claims in real time, allowing applicants to receive an immediate eligibility decision and Certificate of Eligibility (COE) when all required information is available and no additional review is needed. The goal is to continue modernizing the platform so that the majority of all submissions result in an immediate decision.
Enrollment Manager (EM) EM is an Education Service web-based system used by schools and training facilities to certify enrollments and report changes for Veterans and other eligible beneficiaries receiving VA education benefits. EM streamlines communication between educational institutions and VA by enabling electronic submission of enrollment certifications for all EDU benefits and timely delivery of education benefits.
Workload Manager System (WLMS) WLMS will be a modernized replacement for TIMS that goes beyond simple work-queue replacement. In addition to virtual evidence storage and queue management, Workload Manager takes on Regional Processing Office (RPO) workload assignment, management, and reporting using a competency-based framework to automatically match in-progress work products to qualified adjudicators, and producing reporting and monitoring mechanisms at the individual, team, and RPO level.
Approval Manager(AM) AM will be a modernized replacement for both WEAMS and eForce, assuming their full school and program approval case management functionality. Approval Manager will also be enhanced to support claim automation by ensuring submissions are aligned with school and program approval and will include compliance and risk measures to proactively identify potentially at-risk schools and instances of fraud, waste, and abuse.
Data Mart Analytics Platform (DMAP) A separate analytics layer that serves as the back-end for all data-based applications within the DGIB environment. DMAP stores, processes, and retrieves adjudication, workload (including WLMS), user, and automation data, along with broader education (EDU) benefits data such as outcome measures and beneficiary data, to create and continually enhance reporting products that enable intelligent, data-driven decision-making
Claims Processing Platforms (Consolidation Target) VBA currently uses two platforms to process claims received via MEB and EM. VBA is exploring consolidating these two into a single unified processing platform.
Digital GI Bill Ch33 Processing System Handles automated and manual processing specifically for Chapter 33 (Post-9/11 GI Bill) and VET TEC claims.
Benefits Manager (BM) Handles processing for all non-Chapter 33 claims (Chapters 30, 35, 1606).
Requirement: VBA seeks to maximize innovation and automation solutions supporting Digital GI Bill Automation and Modernization. VBA is seeking industry input on the viability of solutions that would deliver rapid implementation and aggressive automation, while preserving Government oversight and accountability of the processes to ensure that our Veterans and their beneficiaries receive world class services in the most efficient manner possible. 
VA Cloud Migration In addition to continued development of a world-class claims automation and management platform, VA anticipates a transition of all Digital GI Bill components from the managed service vendor to a VA owned/managed infrastructure, which can be executed as an option to improve efficiency, eliminate single vendor lock-in solutions, align with VA's cloud-first strategy and reduce costs to the American taxpayer. Any proposed solution would have to reside on the VA owned/managed infrastructure and maintain a valid ATO.
Workload Manager VA is exploring continued development and enhancement of the Workload Manager beyond its planned Minimum Viable Product (MVP) state to achieve full operational capability, enabling the replacement and decommissioning of TIMS (The Image Management System) and work assignment tool used by veteran claims examiners (VCEs).
Approval Manager VA is exploring continued development and enhancement of Approval Manager beyond its planned MVP state to achieve full operational capability, enabling the replacement and decommissioning of both WEAMS (Web Enabled Approval Management System) and eForce.
Data Mart Analytics Platform (DMAP) VA is exploring continued development and enhancement of DMAP beyond its planned Minimum Viable Product (MVP) state to achieve full operational capability, enabling enhanced reporting metrics.
Claims Processing System Consolidation VA is exploring the consolidation of the Digital GI Ch33 processing system and Benefits manager (benefits processing system for all non-33 claims) into a unified processing platform, reducing operational complexity and system redundancy.
Claims Automation Advancement VA is exploring continued enhancement of automated claims adjudication capabilities to progressively increase and maintain automation rate and quality accuracy of E2E processing across all GI Bill benefits. This includes expansion of original and supplemental automation, offramp refinement, and ongoing improvement to automation logic as legislative and policy changes occur.
Streamlined Manual Claims Processing VA is exploring ongoing human-centered design research and iterative improvement manual claims processing for VCEs. With the goal of reducing processing time, improving accuracy, enhancing the examiner experience and potential automation capability.
This RFI is being issued to solicit industry input on the viability of a DGIB and Education Services Automation and Modernization process requirement and to obtain associated data that will help inform and shape a potential acquisition. The requirements described above reflect the current DGIB operational landscape but do not constitute final requirements. VA encourages responses from qualified vendors capable of operating, modernizing, or migrating systems of comparable scale and mission criticality.
Responses: Please submit the below requested information NLT 5:00 pm EST August 28, 2026, via email only to Stephen.Winkler@va.gov. The e-mail subject line shall be Digital GI Bill and Education Services Automation and Modernization [Insert Business Name] . VA reserves the right not to respond to any, all, or select responses or materials submitted. All VA current requirements identified herein are subject to change at any time. Questions regarding this RFI may be submitted to the same email address. VA may or may not respond directly but will consider all questions during market research. VA appreciates your time and anticipated response.
As part of your RFI response, please provide the following information:
GENERAL
Include the following identification information: Company Name Unique Entity Identifier Number under which company is registered in SAM.gov Confirmation of registration in VetBiz.gov if claiming SDVOSB/VOSB Company Address Point of contact name Telephone number Email address
What specific experience does your organization have at providing similar operation and maintenance, development and system migration services of size and scope to other Federal agencies and/or industry? For Federal contracts, provide contract number and agency points of contact. VBA is seeking industry s input on the optimal period of performance structure to balance transition risk with development continuity. Is a base + 4 option structure appropriate, or does industry recommend an alternative structure (e.g., separate O&M and development task orders, a shorter base with more granular option periods)? What period of performance structure best supports a zero-downtime transition approach?
ADDITIONAL QUESTIONS FROM THE GOVERNMENT
The current DGIB system architecture holds an active ATO in a vendor-managed AWS GovCloud environment. VA anticipates that migration to a VAEC or other VA-controlled environment will require ATO reauthorization. What strategies has industry employed to maintain continuous authorization during large-scale cloud migrations? What is a realistic timeline for ATO reauthorization for a system of DGIB's complexity, and what Government actions are prerequisites? What known or unknown factors drive your timeline estimate?
The current DGIB platform involves a highly complex, mature codebase with 700+ repositories, 50+ databases (Oracle 19C, PostgreSQL 14, Amazon Redshift, DynamoDB), and extensive CI/CD infrastructure. Other current systems configuration includes: 76 EC2 compute instances (Windows Server and Red Hat Enterprise Linux) , 590+ compiled software artifacts , 30+ S3 object storage buckets and 90+ vendor, open-source, and hardware licenses. What is a realistic transition-in and transition-out period for a contractor assuming operations of a system of this scale? What Government-provided information or access is most critical to a successful transition-in? What transition-in and transition-out risks does industry consider most significant and how are they typically mitigated? What licenses will the Government need to purchase and the anticipated cost to acquire and maintain those?
Transition Risk and Complexity are major considerations for DGIB modernization. What specific technical strategies does industry recommend to reduce transition risk for a system of DGIB's complexity including dual-run architectures, phased cutover, traffic shadowing, or other approaches? What is the minimum acceptable parallel/dual-run period to validate the migrated environment before production cutover?
VBA seeks industry input on appropriate "Definition of Done" criteria for a system of DGIB's scale and mission criticality before initiating a cloud migration. What operational and technical stability thresholds does industry consider necessary preconditions for a low-risk migration? Are there industry frameworks or federal precedents should VA consider?
What is industry's experience with dual-run or parallel operations for large-scale Government cloud migrations? What are the primary cost drivers and risks during a parallel operations period? What is a realistic dual-run duration for a system processing $12B+ in benefits annually with zero downtime tolerance?
Are there any aspects contained in this RFI that industry believes are unclear, infeasible, or inconsistent with current best practices? What changes do industry recommend? Are there emerging technologies, commercial standards, or federal precedents that VA should consider in developing its potential approach to DGIB modernization?
What tools or templates (e.g., checklists, trackers, standard operating procedures) would you use to support seamless transition-in and transition-out tasks with no interruption or degradation in service or output volumes? Is it unreasonable to ask for references demonstrating successful transitions for similar complex contracts? What support would usually be required from the VA to facilitate a successful transition?
Provide examples of successful modernization and automation initiatives from comparable contracts. What key elements should a roadmap include to ensure effective ongoing maintenance, support, and upgrades as technologies and requirements evolve? What collaboration or support would typically be required from VA to maintain continued success in modernization and automation initiatives?
What is the best approach to continued modernization beyond initial automation or upgrades? How do you stay abreast of emerging technologies and incorporate them into claims processing workflows especially with increased automation?
VENDOR RESPONSE The vendor response shall address their company s approach to satisfy the objectives, constraints, and requirements described in the RFI. Vendor responses shall not include proposed solutions, designs, or architectures intended for direct evaluation; instead responses should provide general experience-based insights and market research input.
INSTRUCTIONS RESPONDING TO THIS RFI
Interested parties are directed to respond to this RFI in Microsoft Word for Office or compatible format and shall not exceed twenty-five (25) pages plus a cover page. A page is defined as each face of an 8.5 x 11 sheet with information contained within a one-inch margin on all sides. Font type shall be Arial 12 point unless provided in table format. Tables can utilize Arial 10 point. All narrative and table content count towards the 25-page limit.
Proprietary information, if any, should be minimized and MUST BE CLEARLY MARKED. To aid the Government, please segregate proprietary information. POST RFI REVIEW PHASE
VA envisions that after RFI responses are reviewed, some responders may be invited to participate in face-to-face or telephonic meeting(s) with VA personnel to answer additional questions with respect to the responses given. The intent of face-to-face or telephonic meeting(s), if conducted, would be for further understanding of potential capability. VA retains sole discretion of whether any post RFI meeting(s) are warranted, and which industry partners, if any, may be invited to provide additional market research information. Participation in post-RFI meeting does not indicate down selection, pre qualification, or competitive advantage in any future procurement.