DA01--VA OIT BAM Product Line Appeals Modernization - RFI

Form / Attachment / Pricing Sheet

This document outlines the baseline requirements for a case management application, likely related to appeals processing. It details functional and non-functional requirements across various modules.

• Intake: Requirements for receiving and processing various types of requests, including VA forms, additional documentation, and external requests.
• Queue Management: Functionality for viewing, managing, and distributing requests to users and teams, including auto-distribution rules and search/filter capabilities.
• Request Management: Features for viewing, editing, adding notes, assigning tasks, and managing motions related to requests.
• Hearings: Requirements for scheduling, managing, and conducting hearings, including videoconferencing and transcription capabilities.
• Decision: Functionality for drafting, signing, and dispatching appeal decisions, including integration with MS Word and boilerplate content management.
• Dispatch: Processes for reviewing, printing, and sending decisions and request responses.
• Follow-On Request Work: Capabilities for splitting, merging, and processing post-decision actions.
• Quality Review: Features for evaluating completed requests, documenting errors, and tracking corrective actions.
• Reader: Requirements for viewing and managing documents and evidence, including search, annotation, and status tracking.
• Integrations: Needs for integrating with various VA systems for data exchange, communication, and account management.
• Custom Workflows & Business Rules: Ability to create and manage custom workflows and business rules.
• User and Team Account Management: Functionality for managing user permissions, teams, and accounts.
• Data Management: Requirements for a relational, state-based database, AMA reporting, and data capture.
• Reporting: Capabilities for standardized and ad hoc reporting and dashboards.
• Regulatory Compliance: Adherence to AMA requirements and federal regulations.
• Legacy Appeal Support: Functionality to support the identification, visibility, and processing of legacy appeals.
• User Interface: Customizable dashboards and saved user preferences.
• Notifications: System for user alerts.
• Artificial Intelligence (AI): Capabilities for document translation, issue extraction, task generation, document consolidation, intelligent reporting, and relevance flagging.

This document serves as a detailed specification of functional and non-functional requirements for a case management system. Bidders should use this to understand the full scope of capabilities expected for the system, which will inform their proposal development, technical approach, and pricing.

Form / Attachment / Pricing Sheet

This document, "Attachment A – Caseflow Baseline Requirements," outlines the foundational requirements for the Board of Veterans' Appeals (Board) case management and appeals processing systems. It serves as a baseline for understanding the current systems and future needs, guiding potential bidders on the capabilities required for modernizing or replacing these systems.

• Background: Describes the high volume of appeals (over 100,000 annually) and the complexity of managing documents, scheduling hearings, and adapting workflows.
• Current Systems: Details the incumbent systems:
  • Caseflow: A modern, AWS GovCloud-hosted system built with Ruby on Rails, managing over 475,000 appeals and supporting over 30,000 VA users. It includes form/data intake, case/task management, hearing scheduling, document viewing/annotation, and acts as a system of record with an API for data sharing.
  • VACOLS: A 40-year-old, in-house developed client/server application built with PowerBuilder, used for legacy appeals and a subset of Appeals Modernization Act (AMA) appeals.
  • Interactive Decision Template (IDT): A Microsoft Word plugin integrating with Caseflow, VACOLS, and SharePoint for drafting correspondence and decisions, utilizing templates and standardized text snippets.
• Future Requirements: Encompasses a broad range of capabilities for a total "Appeals Processing System," including:
  • Appeal Request Intake and Management
  • Work Queue Management
  • Judicial Hearings Management
  • Appeal Decision Drafting (integrated with Microsoft Word)
  • Appeal Dispatch and Request Response
  • Follow-on Request Capabilities
  • Quality Review
  • Document Review and Evidence Management
  • Integration with various VA systems via APIs
  • Custom Workflows and Business Rules
  • User and Team Account Management
  • Data Management, Storage, and Maintenance
  • Reporting Capabilities (custom and standard)
  • Compliance with policies and regulations
  • Processing of legacy appeals
  • Modern User Interface
  • System-generated notifications
  • Artificial Intelligence capabilities

This attachment provides critical context on the existing technological landscape and the comprehensive functional requirements for the Board's appeals processing. Bidders should use this document to understand the scope, complexity, and specific capabilities needed to propose solutions that can either replace or integrate with the current systems, addressing both legacy and modernized appeal processing needs.

Request for Information (RFI)

This RFI is for planning purposes to identify vendors with commercial-off-the-shelf (COTS) solutions for managing appeals and related requests for the Department of Veterans Affairs (VA) Office of Information Technology (OIT). The government seeks to understand current market capabilities.

Vendors are expected to demonstrate COTS solutions that can manage appeals and related requests. Specific requirements are detailed in the attached "Product Description Appeals Application" and "Caseflow Baseline Requirements" documents.

This RFI involves a two-step process:

Part 1: Virtual Demonstrations

• Interested vendors with solutions meeting all or a majority of requirements should request a demonstration.
• Requests, including a 5-page product sheet detailing requirement alignment and business support models, are due by May 29, 2026, 1 PM EST.
• Demonstrations will be virtual via Microsoft Teams during the week of June 8, 2026.
• Each demonstration will not exceed one (1) hour and is limited to five (5) vendor personnel.

Part 2: Written Response

• After demonstrations, vendors will receive specific questions to answer in writing.

In addition to the demonstration request, vendors must provide:

• Company Name, Address, Point of Contact, Phone, Fax, Email

• Company Business Size and Status (with proof of SBA certification for VOSB/SDVOSBs)

• NAICS Code(s) (541512 anticipated, with a $34 million size standard)

• Socioeconomic data

• Unique Entity Identifier (UEI) Number

• Existing Contractual Vehicles (GWAC, FSS, MAC)

• This RFI is for information gathering only and does not constitute a solicitation or commitment to award a contract.

• No payment will be made for information submitted.

• Proprietary information must be marked.

• Attachments referenced: "Product Description Appeals Application" and "Caseflow Baseline Requirements."