OFFICIAL NOTICE CONTENT
Opportunity description
IT Enterprise Service Desk (ESD) Managed Services Request for Information VA-27-00019920 Introduction This Request for Information (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 541512 with a size standard of $34 million. VA seeks market research on industry capability to meet the draft Performance Work Statement (PWS), the feasibility of key requirements, barriers to competition, and recommended changes. Responses should address the specific PWS requirements rather than provide generic marketing or capability statements. Cite relevant PWS paragraph numbers and clearly mark proprietary information. For each numbered question, indicate whether the principal requirements are (a) achievable as written, (b) achievable with modifications, or (c) not currently achievable; explain material limitations and recommend specific changes. Respondents may propose functionally equivalent, technology-neutral solutions. Responses shall be limited to 20 pages, excluding the cover/firm information, comparable-experience summary, and ROM attachment. Respondents shall indicate its company name and address; point of contact, phone, and email; business size and socioeconomic status; applicable NAICS code(s); Unique Entity Identifier (UEI); and available contract vehicles (GWAC, FSS, or MAC). VOSB/SDVOSB respondents should provide proof of SBA certification. Separately provide a concise summary of comparable contracts (agency, contract number, approximate value, and reference contact, if available). Additionally, VOSB/SDVOSB respondents shall indicate your company s intent and ability to meet the set aside requirement in accordance with VAAR 852.219-73 (JAN 2023) (DEVIATION) VA Notice of Total Set-Aside For Certified SDVOSBs and 13 CFR §125.6, which states the contractor will not pay more than 50% of the amount paid by the government to the prime for contract performance to firms that are not certified SDVOSBs listed in the SBA certification database (excluding direct costs to the extent they are not the principal purpose of the acquisition and the SDVOSB/VOSB does not provide the service, such as airline travel, cloud computing services, or mass media purchases). When a contract includes both services and supplies, the 50 percent limitation shall apply only to the service portion of the contract. Your response shall include information as to available personnel and financial resources; full names of proposed team members and the PWS requirements planned to be subcontracted to them, which must include the prime planned percentage or the names of the potential team members that may be used to fulfill the set aside requirement. Your response must address capabilities specific to the services required in the attached PWS and must address the following: 1. Transition-In and Service Continuity (PWS 5.2 and 5.4.6) The draft PWS provides two concurrent transition tracks: Track A for platform/CCI services (approximately Day 60 operational transfer when retaining the current platform or Day 150 for a different platform) and Track B for Tier 0/Tier 1 services (100% workload at required service levels within 150 calendar days), with Quality Gates and 30 days of hypercare after each transfer. Can your company meet these timelines while maintaining uninterrupted functionality and customer experience? Identify the most consequential dependencies, transition risks, baseline verification and operational transfer readiness criteria, and any alternative sequencing or technology approaches that would reduce risk. How should VA address capabilities discovered after award that are absent from the Functional Baseline (Attachment 2)? Identify only authorization, integration, or other deliverable deadlines that materially affect feasibility. 2. Managed Services Delivery Model and Tier 0/Tier 1 Operations (PWS 3.0, 4.2, 5.3, 5.4, 5.5.5, and 5.6) Can your company deliver the integrated Tier 0/Tier 1 service desk, CCI, knowledge management, process integration, quality assurance, and performance reporting requirements through a single managed service, with results independently verified for VA? Identify capability gaps, specialized teaming needs, or requirements that could unnecessarily restrict competition. Comment on feasibility of the draft workload assumptions, including approximately 2,700 knowledge articles (15% annual growth), 520 instructional videos annually, approximately 35 concurrent process-integration initiatives (10% annual growth), Top 10 user support, and Enterprise Command Center support via Tier 1 Incident Management Analysts. What changes or technology-neutral approaches would improve delivery without reducing required outcomes? 3. Artificial Intelligence and Automation Capabilities (PWS 5.8) Can your company implement and operate the AI and automation capabilities described in the PWS, including conversational, generative and agentic AI, robotic process automation, self-service, agent-assist knowledge surfacing, and post-interaction summaries? Distinguish commercially available capabilities from those requiring configuration, integration, or custom development; identify security, data, quality assurance, and operational dependencies. Describe how inaccurate AI-generated content would be detected and corrected before entry into permanent records. Recommend additional capabilities that could materially improve resolution, accessibility, customer experience, or agent productivity, distinguishing demonstrated solutions from emerging functionality. 4. Automation Glide Path Feasibility and Governance (PWS 5.8.3 5.8.5, 5.8.10, 5.8.11, 5.8.14, and 6.1.12) The draft PWS proposes human-handled capacity of 92%, 82%, 72%, 65%, and 60% of a certified baseline in Years 1 5 (50% floor), using approximately 126,000 monthly contacts as the current planning baseline. Are these targets achievable while sustaining service quality? Recommend changes to baseline certification, timing, assumptions, exclusions, and measurement, including the definition of an Automated Resolution (no agent and no repeat contact within seven days), treatment of pre-existing automation, and human-handled contacts per 1,000 End Users. Address how AI-attempted contacts escalated to agents should be counted and reported. Are the proposed approval controls practical (intent-level parity baseline of approximately 90 days, Automation Deployment Package, approximately 15-business-day VA review, and rollback within approximately 15 minutes for voice/chat or four hours for other channels)? Recommend changes that balance deployment speed, auditability, accessible escalation, and protection against unsuccessful deflection. Include any potential price and service level impacts associated with the glide path iterative drops in human-handled capacity. 5. Staffing, Workforce Management, and Surge Capacity (PWS 4.2, 5.1.4, 5.3, and 5.8.7) Can your company meet 24/7/365 support from continental U.S. facilities, the required service levels, and the proposed peak-day planning assumptions (approximately 6,000 contacts on an average business day and 7,850 at the required service levels)? Include your capability to provide incident analysts physically located at the Incident Command Center in the Austin Information Technology Center (AITC). 6. Contact Center Technology and Integration (PWS 5.2.2, 5.4, 5.5, and 5.8.12) Can your company provide or integrate a solution meeting the PWS omnichannel, ITSM interoperability, functional baseline, security, accessibility, and performance requirements without dependence on a particular vendor or product? VA currently uses NICE CXone and ServiceNow, but may change ITSM platforms. Compare, at a high level, retaining the current CCI platform with providing a different CCI or functionally equivalent architecture, including transition, cost, licensing, and integration implications. Address capacity of approximately 126,000 contacts per month across all channels, of which approximately 95,000 are voice, with ~500 simultaneous calls in a 15-minute peak and surge events of up to ~2,500 calls in 15 minutes; up to 550 concurrent licenses; Medallia or equivalent experience-measurement feeds; ADAM integrations; data portability; and transition-out continuity. Identify requirements that may inadvertently favor a specific brand or architecture and propose performance-based alternatives. 7. ITSM Platform Transition and VA s Active Directory Account Management (ADAM) Tool Support (PWS 5.2.8, 5.5.4, 5.5.6, and 5.8.5) VA may direct a change of its ITSM platform during the period of performance. Please identify the ITSM platforms (for example ServiceNow, Salesforce, BMC Helix, or others) on which your company has direct, production experience delivering the services in this PWS. ADAM is an internal account management and identity-access tool used to automate and manage user account lifecycle activities connected to VA's Active Directory environment and integrates with its ITSM platform. Can your company maintain service desk, knowledge, reporting, ADAM, and automation functionality through such a change? Identify the minimum advance decisions, technical information, and notice VA should provide, along with key transition and cost/schedule dependencies. Comment on the proposed ITSM-agnostic integrations, a transition plan due within 30 days of notice, and pausing/revalidating the Glide Path during the change. Would phasing the ITSM replacement after stabilization or another approach materially reduce risk? 8. Security, Data Protection, and Section 508 Accessibility (PWS 5.4.1, 5.4.6, 5.5.2, 5.7, 5.8.3, and 6.1.12) Can your proposed cloud service offering(s) and delivery approach satisfy applicable FedRAMP Moderate, VA Authority to Operate (ATO), interconnection, privacy, data ownership, and Section 508 requirements without a gap at operational transfer? Identify which authorizations or assessment artifacts already exist, what VA-specific approvals would remain, and whether the draft submission dates are feasible for current-platform and alternative-platform approaches. Describe how accessibility would be tested and maintained across IVR, chat, self-service, and AI-enabled paths, including assistive technology testing and remediation as releases change. Identify any requirements that need clarification to avoid unnecessary implementation delay. 9. Change Management Approach for ACD/IVR Supporting the Enterprise Service Desk Describe your organizational change management approach for deploying the ACD and IVR solution supporting the ESD, from before through after deployment to include communications, role-based training, user and support-team readiness, adoption measurement, and post-go-live support. Explain how measured readiness and actual service performance would determine deployment sequencing and hypercare exit, including formal VA acceptance. Describe how your approach complies with VA OIT change management policies and procedures, including change request submission, review and approval board participation, change windows and freeze periods, and release documentation, and identify any assumptions or dependencies. 10. Performance Metrics and Independent Verification (PWS 5.6, 5.8.14.8, and 6.4; Attachment 1) Are the proposed service levels, Critical and Key Performance Indicator designations, independent verification process, Government-held data, and audit rights achievable and suitable for a managed service? Identify metrics that may be impractical, susceptible to inconsistent interpretation, or inappropriate for payment adjustments, and recommend alternatives for customer experience, resolution quality, and automation effectiveness. Comment specifically on Top 10 user targets, 5% abandonment service-impact threshold, reconciliation of differences exceeding 5% within three business days, and Contact Ledger access. Evaluate the proposed approximately 10% quality withhold, 5% monthly adjustment cap, and 30-day cure period, including how these mechanisms should interact without double-counting the same performance issue. 11. Pricing, Contract Structure, and Rough Order of Magnitude (PWS 4.1, 5.1.4, 5.2.2, 5.2.3, 5.4, 5.8.7, 5.8.8, 5.8.14, 5.8.14.6, 5.9, 5.10, and 6.4.2) What contract and pricing structure would best support integrated managed services, platform services, and progressive automation while maintaining quality and competition? Comment on the proposed fixed capacity pricing, approximately 110% volume corridor, approximately 50% Base Unit Price for excess volume, declining platform licenses, optional outcome payment of up to 5%, and handling of VA-driven demand events. Identify workable methods for addressing changing contact complexity, major incidents, ITSM changes, and periodic repricing. Provide a separate, nonbinding Rough Order of Magnitude (ROM) using the response categories below, with assumptions and key cost drivers; detailed personnel assignments are not requested. Provide estimated quantities, units, unit prices, annual and total estimated costs where practical, and a brief explanation of assumptions. State whether pricing reflects commercially available offerings and identify major one-time versus recurring costs. A ROM template is provided for optional use by interested parties, if desired. Utilization of the template is not required; however, the above information should be provided within each submission. Responses are due no later than 9:00AM EST, Tuesday, December 1, 2026 via email to Andrea Caltabilota, Contract Specialist at Andrea.Caltabilota@va.gov and Evan Schlisserman, Contracting Officer at Evan.Schlisserman@va.gov. Please note IT Enterprise Service Desk (ESD) Managed Services 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.
FEDERAL BUYER
Buyer and contracting office
Public points of contact
DOCUMENTS & LINKS
Opportunity documents
That does not mean there are no documents. Open the current SAM.gov notice to see the authoritative attachment and amendment list.
GovBidFit does not invent or cache guessed attachment links. The official SAM.gov notice remains the controlling document source.
NOTICE TIMELINE
GovBidFit change history
This timeline records when GovBidFit first stored the notice and material field changes detected during scheduled SAM.gov refreshes. It is an audit aid, not a substitute for the official amendment history.
GovBidFit first stored this opportunity from the SAM.gov public bulk feed. This does not replace the official posting date shown above.
GOVBIDFIT SCREENING LENS
What deserves attention before you spend bid time
These screening signals are generated from the public notice fields stored for this specific opportunity. They are not eligibility findings or predictions; they are prompts for a faster, more disciplined review of the official solicitation.
This notice appears to be market research rather than a conventional bid invitation. A capability response, technical feedback or evidence of market interest may matter more than a price proposal at this stage.
The stored deadline is within ten days. Build an internal submission deadline and verify whether questions, site visits, registrations or approvals are due earlier.
The current feed does not show a program-specific set-aside restriction. That does not remove other eligibility, responsibility, registration or solicitation-specific requirements.
NAICS 541512 · PSC DE01 is the recorded classification. Use it as a screening clue, then compare the actual scope and deliverables rather than treating the code alone as proof of fit.
GovBidFit stores the source notice text, but its length does not prove the requirements are complete. Review official attachments, clauses, amendments and Q&A before relying on the description.
The source data includes 1 public contracting contact. Use the solicitation's stated communication rules and deadlines before contacting the buyer.
Questions to resolve next
What this opportunity record tells you
SAM.gov identifies this as a sources sought from VETERANS AFFAIRS, DEPARTMENT OF. The record was posted on November 19, 2026 and currently lists December 1, 2026 as the response deadline. GovBidFit keeps source facts separate from its matching guidance so you can see what comes from the federal notice.
The listed product or service classification is NAICS 541512 · Computer Systems Design Services · PSC DE01. The set-aside field is Unrestricted. These fields help narrow your search, but they do not replace the full solicitation, amendments, attachments, clauses or eligibility language on the official source.
Before deciding to bid
GovBidFit lets you browse federal contract opportunities for free and create free bid alerts. It displays public SAM.gov notice data stored in its database, with a compact snapshot as a fallback. GovBidFit is independent and is not a U.S. government website. Data can lag amendments or later source changes, so always verify the current notice, attachments and deadline on SAM.gov before bidding.
Open the official SAM.gov notice →