ESD_Managed_Services_PWS_DRAFT for RFI 11.19.docx

DOCX document 181 KB Posted

Attached to
DE01--Enterprise Service Desk (ESD) Managed Services (VA-27-00019920)
Solicitation number
36C10B27Q0134
Issued by

About this file

This is a Performance Work Statement (PWS) for the Department of Veterans Affairs (VA) Enterprise Service Desk (ESD) Managed Services with Automation Glide Path, issued as a draft for a Request for Information (RFI) on November 19, 2026. The VA's Office of Information & Technology seeks to consolidate IT Enterprise Service Desk services currently provided by two separate vendors into a single managed services contract. The contractor will assume responsibility for Tier 0/Tier 1 agent services and managed Contact Center Infrastructure (CCI) operations, including the contact center platform, quality assurance, performance reporting, and customer satisfaction surveys. Current services under two task orders end on March 29, 2027. The requirement covers approximately 600,000 VA employees and contractors with estimated annual growth of 5%, handling approximately 126,000 contacts per month across multiple channels (76% phone, 21% self-service tickets, 1.7% chat, 1.2% Microsoft Teams, with additional SMS/text capability). Platform capacity must accommodate surge events of up to 2,500 calls within 15 minutes.

The PWS establishes four primary objectives: maintaining current service levels and performance without degradation, preserving all existing customer-facing and back-office functions, reducing live Tier 1 agent contact volume through automation, self-service, and AI-enabled channels via a Government-controlled glide path, and strengthening identity assurance through voice biometrics and related security controls. The VA currently uses ServiceNow as its IT Service Management (ITSM) platform and Microsoft for productivity and collaboration; however, the PWS notes that the VA is assessing long-term solution strategies that may involve transitioning to alternative platforms during the contract performance period, though no decisions have been finalized and any transition would be addressed separately. All data, recordings, and analytics must remain under VA ownership and control with Government-independent performance verification. The NAICS code is 541512 with a size standard of $34 million.

View the file

Other files

File Type Posted
ESD_RFI_ROM_Template.xlsx XLSX spreadsheet
36C10B27Q0134.docx DOCX document

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

PERFORMANCE WORK STATEMENT (PWS)

DEPARTMENT OF VETERANS AFFAIRS

Office of Information & Technology (OIT) Enterprise Command Operations IT Enterprise Service Desk (ESD) Managed Services with Automation Glide Path Date: November 19, 2026 | PWS Version 0.4 rev8.14

VA-27-00019920

1.0 BACKGROUND

The Department of Veterans Affairs (VA), Office of Information & Technology (OIT), Enterprise Command Operations, strives to provide high quality, effective, and efficient Information Technology (IT) services to those responsible for providing care to Veterans at the point-of-care as well as throughout all the points of the Veteran’s health care in an effective, timely and compassionate manner. VA depends on Information Management/Information Technology (IM/IT) systems to meet mission goals. The IT Enterprise Service Desk (ESD) is the single point of contact for IT support to VA employees, contractors, and VA-designated third parties.

VA currently obtains ESD services through two separate task orders, each performed by a different vendor in a Multi-Vendor Service Provider (MVSP) environment: (1) Tier 0/Tier 1 agent services, and (2) a managed Contact Center Infrastructure (CCI) service that includes the contact center platform, quality assurance, performance reporting, and customer satisfaction surveys. Both task orders end on March 29, 2027. VA intends to obtain these services as managed services from a single Contractor and, over the life of the contract, to move appropriate contact volume from live Tier 1 agents to automated, self-service, and AI-enabled channels through a committed and Government-controlled “Glide Path.”

VA currently utilizes ServiceNow as its IT Service Management (ITSM) platform and Microsoft as its productivity and collaboration suite. VA is currently assessing long-term solution strategies where, during the period of performance of any resulting contract, VA may transition off its current ITSM platform and Microsoft to other solutions. Separately, VA may transition its CCI platform (automatic call distributor (ACD) and interactive voice response (IVR) system that routes and handles incoming service desk calls) to another VA-developed, in-house solution during the period of performance. The CCI transition could occur before, during, or after an ITSM platform change. No decision has been made on either transition, and the timing, scope, and nature of any transition are not known at this time. This background is provided for informational purposes only to give awareness of potential changes in the operating environment. It does not establish, and shall not be construed as establishing, a requirement for the Contractor to perform any task, transition, migration, or service. If VA decides to pursue any such transition and requires contractor support, VA will address support through a separate requirement, modification, or task order in accordance with the contract terms.

1.1 Objectives

1. Maintain, without degradation, the services and performance VA receives today from both task orders (the “Baseline”).

1. Preserve every existing customer-facing and back-office function listed in the Functional Baseline (Attachment 2) from the date the Contractor assumes operational responsibility.

1. Reduce the share of contacts that require a live Tier 1 agent by adopting automation, self-service, and AI where it can be shown, using VA data, to meet or improve customer experience.

1. Strengthen identity assurance and security for callers through voice biometrics and related controls.

1. Keep all data, recordings, and analytics under VA ownership and control, with Government-independent verification of performance.

1.2 Current Environment (Informational)

The information below is provided for planning only. It is drawn from the current task orders and will be validated through the Current-State Baseline process in Section 5.2.4. Volumes are estimates, and the Contractor shall perform all services for actual contact volumes.

Item
Current estimate / description
Customer base
~600,000 VA employees and contractors; ~5% annual growth; ~4.5 contacts per customer per year; ~1,700 VIP users
Contact volume (handled)
~126,000 contacts handled per month across all channels, which is the average over the past 12 months and is the planning baseline for this PWS (October 2026: 126,272; trailing 12-month average 126,503; trailing 3-month average 130,335). Volume reflects automation of PIV exemption requests, formerly the largest call driver (see Attachment 2).
Platform capacity requirement
Platform sized for ~126,000 contacts per month across all channels (~95,000 voice); Contractor must have capacity to cover surges, including ~500 simultaneous calls in a 15-minute period and surge events up to ~2,500 calls in 15 minutes (surge figures are CCI task order sizing estimates, not current traffic)
Channel mix (handled, October 2026)
Phone ~76% (96,004); self-service tickets ~21% (26,460); chat ~1.7% (2,178); Microsoft Teams ~1.2% (1,577); SMS/text <0.1% (53)
Daily demand pattern (received, trailing 12 months)
Business-day average ~6,000 contacts (phone ~4,600); 95th percentile ~7,850; maximum ~10,165. Weekend days average ~641 to ~712 handled contacts. Peaks fall mostly on Mondays. Daily abandonment exceeded 10% on about 15 days in the trailing 12 months. The Contractor shall size staffing and capacity for peak days, not the average.
Average handle time
~12.5 minutes across all channels
Applications supported / knowledge
~900 applications; ~2,700 Tier 0/1 knowledge articles (Tier 1 PWS estimate)
Hours of coverage
24 hours a day, 7 days a week, 365 days a year
Contact center platform
Cloud-based ACD/IVR platform, currently NICE CXone, integrated with the VA ITSM tool.
ITSM tool
The current ITSM tool is ServiceNow. VA may select a different ITSM tool during the period of performance (see Section 5.2.8).
Independent experience measurement
VA independently monitors CSAT, QA, and SLA performance through Medallia, which is part of the current platform, or through other software that provides the same functionality with no loss of functionality. Independent verification under this PWS will be performed for VA by a separate Independent Verification Contractor (see Section 5.6).

2.0 APPLICABLE DOCUMENTS

In the performance of the tasks associated with this PWS, the Contractor shall comply with the following:

1. “Federal Information Security Modernization Act of 2014”

1. Federal Information Processing Standards (FIPS) Publication 140-3, “Security Requirements for Cryptographic Modules”, March 22, 2019

1. FIPS Pub 199. “Standards for Security Categorization of Federal Information and Information Systems,” February 2004

1. FIPS Pub 200, “Minimum Security Requirements for Federal Information and Information Systems,” March 2006

1. FIPS Pub 201-3, “Personal Identity Verification of Federal Employees and Contractors,” January 2022

1. 10 U.S.C. § 2224, "Defense Information Assurance Program", as amended

1. 5 U.S.C. § 552a, as amended, “The Privacy Act of 1974”

1. Public Law 109-461 (P.L. 109-461), Veterans Benefits, Health Care, and Information Technology Act of 2006, as amended, Title IX, Information Security Matters

1. 42 U.S.C. § 2000d “Title VI of the Civil Rights Act of 1964”, as amended

1. VA Directive 0710, “Personnel Vetting Program,” September 8, 2025, https://www.va.gov/vapubs/index.cfm

1. VA Handbook 0710, “Personnel Vetting Program,” September 8, 2025, https://www.va.gov/vapubs/index.cfm

1. VA Directive 6102, “Internet/Intranet Services,” August 5, 2019

1. 36 C.F.R. Part 1194 “Information and Communication Technology Standards and Guidelines,” as amended

1. Office of Management and Budget (OMB) Circular A-130, “Managing Federal Information as a Strategic Resource,” July 28, 2016

1. 32 C.F.R. Part 199, “Civilian Health and Medical Program of the Uniformed Services (CHAMPUS)”, as amended

1. NIST SP 800-66 Rev. 2, “Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule: A Cybersecurity Resource Guide,” February 2024

1. 45 C.F.R Parts 160 and 164, Subparts A and E, the Standards for Privacy of Individually Identifiable Health Information (“Privacy Rule”); and 45 C.F.R. Parts 160 and 164, Subparts A and C, the Security Standard (“Security Rule”); as amended

1. Sections 504 and 508 of the Rehabilitation Act (29 U.S.C. § 794d), as amended

1. Homeland Security Presidential Directive (12) (HSPD-12), August 27, 2004

1. VA Directive 6500, “VA Cybersecurity Program,” September 22, 2026

1. VA Handbook 6500, “Risk Management Framework for VA Information Systems VA Information Security Program,” February 24, 2021 (see VA Notice 25-01, dated October 15, 2024, “Update to VA Handbook 6500 Risk Management Framework for VA Information Systems VA Information Security Program”, VA Notice 25-16, dated September 15, 2025, “Amending VA Handbook 6500 to Replace Enterprise Mission Assurance Support Services Tool With Office of Information Technology Governance Risk Compliance Tool, and VA Notice 25-17, dated September 22, 2025, “Rescission Of Office Of Information Security (OIS) Deputy Assistant Secretary (DAS) Memorandum – Requirements of Proper Plan of Action and Milestones (POA&M) Completion)

1. VA Handbook 6500.2, “Management of Breaches Involving Sensitive Personal Information (SPI),” June 30, 2023

1. VA Handbook 6500.6, “Acquisition Cybersecurity,” October 2, 2026

1. VA Handbook 6500.8, “Information System Contingency Planning,” March 25, 2025

1. VA Handbook 6500.10, “Mobile Device Security Policy,” August 24, 2026

1. VA Handbook 6500.11, “VA Firewall Configuration,” August 22, 2017

1. OIT Process Asset Library (PAL), OIT Process Asset Library.

1. One-VA Technical Reference Model (TRM) (reference at https://www.va.gov/trm/TRMHomePage.aspx)

1. VA Directive 6508, “Implementation of Privacy Threshold Analysis and Privacy Impact Assessment,” October 15, 2014

1. VA Directive 6510, “VA Identity, Credential and Access Management,” September 3, 2024

1. VA Handbook 6510, “VA Identity, Credential and Access Management,” September 27, 2024

1. VA Directive and Handbook 6513, “Secure External Connections,” October 12, 2017

1. VA Directive 6300, “Records and Information Management,” September 21, 2018

1. VA Handbook, 6300.1, “Records Management Procedures,“ March 24, 2010

1. NIST SP 800-37 Rev 2, “Risk Management Framework for Information Systems and Organizations: A System Life Cycle Approach for Security and Privacy,” December 2018

1. NIST SP 800-53 Rev. 5.2.0 “Security and Privacy Controls for Information Systems and Organizations,” August 27, 2025

1. VA Directive 0735, “Homeland Security Presidential Directive 12 (HSPD-12), Personal Identity Verification, Credential Management Program,” September 19, 2025

1. VA Handbook 0735, “Homeland Security Presidential Directive 12 (HSPD-12), Personal Identity Verification, Credential Management Program,” September 18, 2025

1. OMB Memorandum 05-24, “Implementation of Homeland Security Presidential Directive (HSPD) 12 – Policy for a Common Identification Standard for Federal Employees and Contractors,” August 5, 2005

1. OMB Memorandum M-19-17, “Enabling Mission Delivery Through Improved Identity, Credential, and Access Management,” May 21, 2019

1. OMB Memorandum, “Guidance for Homeland Security Presidential Directive (HSPD) 12 Implementation,” May 23, 2008

1. Federal Identity, Credential, and Access Management (FICAM) Architecture, June 30, 2023 (FICAM Architecture (idmanagement.gov))

1. NIST SP 800-116 Rev 1, “Guidelines for the Use of Personal Identity Verification (PIV) Credentials in Facility Access,“ June 2018

1. NIST SP 800-63 Rev 4, 800-63A-4, 800-63B-4, 800-63C-4, “Digital Identity Guidelines,” August 1, 2025

1. NIST SP 800-157, “Guidelines for Derived PIV Credentials,” December 2014

1. VA Memorandum “Personal Identity Verification (PIV) Logical Access Policy Clarification,” July 17, 2019, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4896

1. Trusted Internet Connections (TIC) 3.0 Core Guidance Documents, https://www.cisa.gov/publication/tic-30-core-guidance-documents

1. OMB Memorandum M-19-26, “Update to the Trusted Internet Connections (TIC) Initiative,” September 12, 2019

1. OMB Memorandum M-08-23, “Securing the Federal Government’s Domain Name System Infrastructure,” August 22, 2008

1. Sections 524 and 525 of the Energy Independence and Security Act of 2007, (P.L. 110–140), December 19, 2007

1. Section 104 of the Energy Policy Act of 2005, (P.L. 109–58), August 8, 2005

1. Executive Order 13221, “Energy-Efficient Standby Power Devices,” August 2, 2001

1. Executive Order 14148, “Initial Rescissions of Harmful Executive Orders and Actions,” dated January 20, 2025

1. VA Directive 0057, “VA Environmental Management Program,” October 25, 2022

1. OIS VAIQ #7424808 Memorandum, “Remote Access,” January 15, 2014, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

1. Clinger-Cohen Act of 1996, 40 U.S.C. §11101 and §11103

1. “Veteran Focused Integration Process (VIP) Guide 4.0,” March 2021, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371

1. VA Memorandum “Proper Use of Email and Other Messaging Services,” January 2, 2018, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

1. “Product Line Management Transformation Playbook” version 3.1, August 2023, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4946

1. NIST SP 500-267B Revision 1, “USGv6 Profile,” November 2020

1. OMB Memorandum M-21-07, “Completing the Transition to Internet Protocol Version 6 (IPv6),” November 19, 2020

1. Social Security Number (SSN) Fraud Prevention Act of 2017

1. Section 240 of the Consolidated Appropriations Act (CAA) 2018, March 23, 2018

1. C.F.R Title 15 Part 7, “Securing the Information and Communications Technology and Services (ICTS) Supply Chain”, as amended

1. Executive Order 14028, “Executive Order on Improving the Nation's Cybersecurity,” May 12, 2021, https://bidenwhitehouse.archives.gov/briefing-room/presidential-actions/2025/01/16/executive-order-on-strengthening-and-promoting-innovation-in-the-nations-cybersecurity/

1. OMB Memorandum M-22-09, “Moving the U.S. Government Toward Zero Trust Cybersecurity Principles”, January 26, 2022, https://www.whitehouse.gov/wp-content/uploads/2022/01/M-22-09.pdf.

1. NIST SP 800-52 Revision 2, “Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations

1. OMB M-26-05, “Adopting a Risk-based Approach to Software and Hardware Security,” January 23, 2026

1. OMB M-21-31, “Improving the Federal Government’s Investigative and Remediation Capabilities Related to Cybersecurity Incidents,” August 27, 2021

1. NIST SP 800-88 Revision 2 “Guidelines for Media Sanitization,” September 26, 2025

1. CISA BOD 23-01: Improving Asset Visibility and Vulnerability Detection on Federal Networks. Cybersecurity & Infrastructure Security Agency (CISA), BOD 23-01: Improving Asset Visibility and Vulnerability Detection on Federal Networks | CISA

1. CISA BOD 26-04: Prioritizing Security Updates Based on Risk, June 10, 2026

1. VA Directive 6550, Pre-Procurement Assessment and Implementation of Medical Devices/Systems, June 03, 2019

1. VA Memorandum, “VA Security Controls,” January 17, 2025, https://www.voa.va.gov/DocumentView.aspx?DocumentID=5010

1. E.O. 13960, “Promoting the Use of Trustworthy Artificial Intelligence in the Federal Government,” December 3, 2020

1. E.O. 14319, “Preventing Woke AI in the Federal Government,” July 23, 2025

1. OMB Memorandum M-25-21, “Accelerating Federal Use of AI through Innovation, Governance, and Public Trust,” April 3, 2025

1. OMB Memorandum M-25-22, “Driving Efficient Acquisition of Artificial Intelligence in Government,” April 3, 2025

1. OMB Memorandum M-26-04, “Increasing Public Trust in Artificial Intelligence (AI) Through Unbiased AI Principles,” December 11, 2025

1. OMB Memorandum M-26-10, “Reinforcing Transparency, Accountability, and Oversight of Federal Technology”, March 31, 2026

1. NIST AI 100-1, “Artificial Intelligence Risk Management Framework (AI RMF 1.0)”

1. VA Trustworthy AI Framework and VA guidance on generative AI use (referenced in PWS 6.1.12)

1. ITIL best practices as adopted by VA OIT version 4

1. ESD QA Practicum Form and VA Tier 1 Playbooks (Government-furnished; Attachment 4)

1. Privacy Act System of Records Notice(s) and Privacy Impact Assessment applicable to voice biometrics and call recordings

3.0 SCOPE OF WORK

The Contractor shall, as the single prime Contractor for the VA ESD contact center, provide the following integrated services on a non-personal-services basis:

1. Tier 0/Tier 1 services: agent-based and self-service IT support across all contact channels (Section 5.3).

1. Contact center platform services: a secure, managed, cloud-based contact center capability, including operations, maintenance, availability, and disaster recovery (Section 5.4).

1. Base integrated functionality: the Functional Baseline, voice biometrics, experience-measurement integration, and ITSM integration (Section 5.5).

1. Quality assurance, performance measurement, and reporting produced by the Contractor and independently verified by VA (Section 5.6).

1. Data, recordings, and records management under VA ownership (Section 5.7).

1. Automation transformation delivered through the Glide Path (Section 5.8).

The requirements in this PWS describe required capabilities and outcomes. Except where Section 1.2 describes the current environment, no requirement shall be read as requiring a specific commercial product. The Contractor may propose, subject to Government approval under Section 5.8, the tools it will use to deliver automation. All proposed tools shall meet the security, privacy, interoperability, and data-ownership requirements of this PWS.

4.0 PERFORMANCE DETAILS

4.1 PERFORMANCE PERIOD

The Period of Performance (PoP) shall be 12 months from date of award, with four 12-month option period(s) and four Optional Tasks. The overall PoP shall not exceed 60 months. The Transition-In activities in Section 5.2 are part of the first period of performance.

4.2 PLACE OF PERFORMANCE

Tasks under this PWS shall be performed at Contractor facilities located within the continental United States. The Contractor shall identify its places of performance in its proposal submission. No work shall take place outside the United States. Remote telework by Contractor personnel must be pre-approved by the Contracting Officer’s Representative (COR). Remote telework for agents providing Tier 1 services must be distraction-free to prevent degradation of services. Degradation of service is grounds for VA to revoke telework approval.

The Contractor shall provide workspace at its primary contact center facility for two (2) VA employees, with access to real-time performance data and the ability to pull agent activity and call traffic reports, together with a telephone, printer access, and LAN access.

Incident analysts shall be physically located at the Incident Command Center in the Austin Information Technology Center (AITC), 1615 Woodward Street, Austin, Texas 78741, and shall report to the Incident Command Center Supervisor. The incident analysts serve as a first-response team for Major Incidents. Incident analysts are not authorized to telework or to perform this work at Contractor facilities. The Contractor remains responsible for the personnel administration of its employees, and the CO and COR retain all authority to change the contract.

4.3 HOURS OF COVERAGE

Services shall be provided 24 hours a day, 7 days a week, 365 days a year.

4.4 TRAVEL

The Government anticipates four people for four trips per year to Washington, DC or Austin, TX for executive-level meetings, each approximately three calendar days, plus travel to enterprise program meetings under PWS 5.1. Include all estimated travel costs in firm-fixed-price line items. These costs will not be directly reimbursed. Travel shall be in accordance with the Federal Travel Regulations and requires advance COR concurrence.

5.0 SPECIFIC TASKS AND DELIVERABLES

The Contractor shall perform the following:

5.1 PROJECT MANAGEMENT

5.1.1 Contractor Project Management Plan

The Contractor shall implement and follow the Project Management Institute (PMI) Project Management Body of Knowledge (PMBOK) industry-standard framework, including guidance, governance, and reporting using PMBOK and Microsoft tools such as Word, Excel, PowerPoint, Project, and Visio. The Contractor shall deliver a Contractor Project Management Plan (CPMP) describing its approach, timeline, deliverables, and tools for executing all tasks, in both narrative and graphic schedule form, including milestones, risks and the risk management approach, resources and staffing plan, the two Transition-In tracks (Section 5.2), and the Glide Path (Section 5.8). The CPMP shall describe how the Contractor coordinates and executes the effort, including planned, routine, and ad hoc data collection and reporting requests and change management; list VA and Contractor personnel with real-time access to the platform, Contractor performance reports, data collected, and quality assurance and reporting responsibilities; identify roles and responsibilities for VA, the Contractor, and any third-party vendors; and include a subsection on how the Contractor intends to encourage and facilitate the hiring of Veterans. The initial baseline CPMP shall be concurred upon and updated in accordance with Section B of the contract. The CPMP is a living document, and the Contractor shall update and maintain the Government-approved CPMP throughout the PoP.

Deliverable:

A. Contractor Project Management Plan

5.1.2 Reporting Requirements

The Contractor shall provide the COR weekly Progress Reports, or Progress Reports at another frequency as determined by the COR, covering work completed, work planned, problems and resolutions, deviations from the CPMP, Section 508 conformance status of ICT deliverables, Glide Path status, and the Weekly Transition-In Status Report content defined in Section 5.2 during the transition period. If this contract results in the acquisition of AI, cloud, software, or related IT, the Contractor shall also provide a quarterly Price and Utilization Report using the OMB M-26-10 template.

In addition to the progress report, the Contractor shall provide the following service reports.

1. Service Management Report: a summary of accomplishments, work in progress, and planned work; a review of resource allocation for the past year and progress compared to the road map (goals and objectives); and the attrition rate for the previous month.

2. Service Portfolio Management Report: a review of the latest systems and applications, and a list of solutions and capabilities needed to meet emerging requirements for ESD support.

3. Contractor Personnel Certifications: the status of IT Infrastructure Library (ITIL) Foundation certification of all required Contractor personnel, with certification level, currency (valid or expired), and renewal status.

4. Security and Virus Incidents Report: logical security violations reported to security administration, including the nature of each violation and the status of, and plan to remedy, the violation.

Deliverables:

A. Progress Report B. Price and Utilization Report (OMB M-26-10) C. Service Management Report D. Service Portfolio Management Report E. Contractor Personnel Certifications F. Security and Virus Incidents Report

5.1.3 Governance

The Contractor shall participate in the following VA governance forums and shall submit agendas and minutes for each.

1. Executive Oversight Committee (EOC). The Contractor shall designate representatives with appropriate skills and experience to serve on the EOC, which is chaired by VA and made up of key executives from the Contractor and VA. The EOC meets at least quarterly, and when its members deem appropriate, to review and analyze the monthly performance reports for the preceding period (including schedule overruns, service level attainment, and issues or outages that affect overall performance); review progress on the resolution of issues; attempt to resolve, or designate individuals to resolve, escalated issues; and review and attempt to address escalated decisions. Contractor members shall include the Contractor Account Executive Sponsor and the Account Executive(s) providing oversight of this contract. The Contractor shall provide an EOC charter identifying members, roles and responsibilities, and processes for VA approval; prepare a Quarterly Review presentation covering the past quarter’s activities and plans for the upcoming quarter; and provide minutes including all related discussions and action items, which shall be included in the Monthly ESD Report (Section 5.6.2).

2. Managed Services Oversight Council (MSOC). The Contractor shall designate representatives with appropriate skills and experience to the MSOC, which is chaired by the VA Supplier Management Executive and meets monthly to address business requirements, contract performance, performance standards, continuous improvement, benchmarking, quality assurance, and escalated issues and disputes. The Contractor shall identify a Single Point of Contact (SPOC) who provides oversight of this contract, serves as the Contractor’s highest-ranking representative on the council, and has the authority to commit the Contractor (subject to VA review and approval) to the course of action VA deems necessary. The Contractor shall prepare a Monthly Review presentation covering the past month’s activities and plans for the upcoming month, and provide minutes including all related discussions and action items, which shall be included in the Monthly ESD Report.

3. Quarterly calibration meetings. The Contractor shall conduct quarterly calibration meetings with VA to ensure all parties use standardized processes and procedures when evaluating platform and individual agent performance. The Contractor shall present its methodology and results, including issues, anomalies, and observations from the applicable reports (Monthly ESD Status Report, Monthly ESD Report, Incident Management Report, Service Level Report, and Demand Management Report) and from the quality assurance effort, and shall recommend improvements to platform or agent performance, monitoring, or overall efficiency.

4. Glide Path Review Board (Section 5.8.6).

Deliverables:

A. Executive Oversight Committee Charter B. Executive Oversight Committee Review Presentation C. Managed Services Oversight Council Review Presentation D. Meeting agendas and minutes

5.1.4 Key Personnel and Workforce Continuity

The Contractor shall designate an Account Executive as essential personnel and single point of contact for VA. The Contractor shall also provide a Contractor Resource Continuity Plan addressing retention, backfill for unplanned turnover, surge staffing, and workforce transition as automation reduces agent volume (Section 5.8.7). The Contractor shall maintain an on-boarding/off-boarding status report and an all-staff roster.

The Contractor shall ensure that all supervisory and management personnel and support staff (not including agents) are ITIL Foundation certified to the latest ITIL version; that platform support personnel are certified at ITIL 4 Foundation or higher; that quality assurance personnel are ITIL Foundation certified; that all Incident Managers have specific incident management experience (preferably three years or more) in the VA environment; and that all personnel with active VA network access accounts keep those accounts active.

The Contractor shall manage onboarding and offboarding of its staff. Onboarding includes the steps to obtain a VA Personal Identity Verification (PIV) card, network and email accounts, complete VA-required training, initiate background investigations, and gain physical and logical access, and the identification of individuals who may require elevated privileges. The Contractor shall designate an Onboarding SPOC who tracks the onboarding and offboarding status of all Contractor personnel and is responsible for complete, accurate, and timely submission of all required VA onboarding and offboarding paperwork to the COR. The Contractor shall track the status of all staff onboarding activities, including the names of all personnel engaged on the task, the initial training date for VA Privacy and Information Security training, the next required training date, and PIV status, and the Onboarding SPOC shall report status at the staff level during status meetings.

Deliverables:

A. Contractor Resource Continuity Plan B. Onboarding/Offboarding Status Report C. All-Staff Roster D. Contractor Staff Roster (Section 6.2.1)

5.1.5 Technical Kickoff Meeting

A technical kickoff meeting shall be held after award. The Contractor shall coordinate the date, time, and location (which may be virtual) with the Contracting Officer (CO), as Post-Award Conference Chairperson, the VA PM, as Co-Chairperson, the Contract Specialist (CS), and the COR. The Contractor shall provide a draft agenda to the CO and VA PM in advance of the meeting and, upon Government approval of a final agenda, distribute it to all attendees. During the meeting the Contractor shall present for Government review and approval the details of its intended approach, work plan, and project schedule for each effort via a Microsoft Office PowerPoint presentation. At the conclusion of the meeting, the Contractor shall update the presentation with a final slide entitled “Summary Report,” noting any major issues, agreements, or disagreements discussed and including the statement: “As the Post-Award Conference Chairperson, I have reviewed the entirety of this presentation and assert that it is an accurate representation and summary of the discussions held during the Technical Kickoff Meeting for the IT ESD Managed Services.” The Contractor shall submit the final presentation to the CO for review and signature, and shall work with the CS, the Government’s designated note taker, to prepare and distribute the meeting minutes to the CO, COR, and all attendees, obtaining CS concurrence on the minutes before distribution.

Deliverables:

A. Kickoff Meeting Agenda B. Kickoff Meeting Minutes C. PowerPoint presentation with Summary Report

5.1.6 Regular Meetings and Conference Calls

Contractor and VA representatives shall meet periodically to discuss matters arising under this PWS, including the committee and council meetings in Section 5.1.3 and other meetings of VA and Contractor personnel, including Contractor senior management, as the Government reasonably requests. For each meeting the Contractor shall prepare an agenda that incorporates the topics designated by VA and distribute it in advance, and shall record and distribute minutes for review and concurrence by the COR. The Contractor shall notify the COR in advance of scheduled meetings with VA representatives or designated alternates (other than meetings about the day-to-day provision of specific services) and invite the COR or designee to attend.

Deliverables:

A. Regular Meeting Agenda B. Regular Meeting Minutes

5.1.7 Coordination with Other VA Contractors and Stakeholders ESD services are provided alongside other VA organizations and contractors, including Tier 2 and Tier 3 support and enterprise service providers. The Contractor shall attend VA-required meetings (virtual or on-site) to coordinate with them, shall ensure all materials and communications used to accomplish the work are non-proprietary and usable collaboratively, and shall not communicate with other contractors under separate contract vehicles about contract tasks without prior notification to and approval from the CO, COR, and VA PM. Coordination areas include, but are not limited to:

1. Comprehensive cross-area support and consistent messaging, including areas where functional processes overlap with other program areas, common data re-use requirements, and data and report submission standards (for example common call flows and scripts, and quality assurance monitoring and reporting).

2. Functional and capability handoffs between the Contractor, ESD stakeholders, and other contractors, including participation in call-flow testing and test calls before go-live events, development or revision of procedures, scripts, and use cases to ensure successful execution of services and transfer of tickets and tasks, and knowledge management and sharing.

3. Adherence to VA-approved communications, governance, and quality assurance processes.

4. Sharing all deliverables, systems, data, and tools created under this contract with stakeholders at the request of the COR.

5. Working cooperatively to identify service improvements and efficiency projects, and assigning sufficient staff to develop process solutions that could be implemented.

6. Collaboration that maintains a balance of interests, transparency, and open, honest, frequent, and comprehensive communication to build and maintain relationships of trust and respect.

7. Full cooperation with ESD and its other contractors during periods when other contractors are in transition-in or transition-out.

5.2 TRANSITION-IN

5.2.1 General

The Contractor shall transition services from the incumbent Contractors with no loss of functionality and no degradation of customer experience. Transition-In has two tracks that run concurrently: Track A (platform and contact center infrastructure services) and Track B (Tier 0/Tier 1 agent services). Track A’s timeframe depends on the platform under Section 5.2.2. Track B has 150 calendar days from award (Section 5.2.3). The Contractor shall deliver a Transition-In Plan, an On-Boarding Plan, and a Communications Plan, hold a transition planning meeting within five (5) business days after kickoff, and provide a weekly Transition-In Status Report covering percent complete of activities, staffing, risks, and knowledge transfer.

Deliverables:

A. Transition-In Plan B. On-Boarding Plan C. Communications Plan D. Weekly Transition-In Status Report

5.2.2 Track A: Platform and CCI Services

Track A begins with a baseline verification period that applies to every Contractor (item 1). After that, Track A depends on the platform the Contractor operates. A Contractor that operates the platform VA uses at award, assuming VA’s existing environment, configuration, and authorization without building or migrating to a new one, follows item 2 (the “Current Platform”). A Contractor that operates any other platform follows item 3 (the “Replacement Platform”). The platform is identified in the Contractor’s contract and shall not change without the Contracting Officer’s written approval. Item 4 applies to both.

1. Overlap and baseline verification (Days [1–30]; all Contractors). The incumbent CCI Contractor remains responsible for operating the platform. The Contractor shall work alongside the incumbent to obtain knowledge transfer and observe operations; review the incumbent Current-State Baseline (Section 5.2.4), the Functional Baseline (Section 5.2.5), configurations, integrations, call flows, scripts, prompts, queues, skills, reports, and documentation; and obtain the access and credentials needed to observe and verify the platform and its configuration.

1. Current Platform (Days [31–60]). The Contractor shall assume operational responsibility on the Operational Transfer Date, which the Contracting Officer will set in writing and which shall be no earlier than Day [31] and no later than Day [60]. [Offerors may propose an earlier date.] Until the Operational Transfer Date, the incumbent CCI Contractor remains responsible for operating the platform and for the service levels in effect under its order. The Operational Transfer Date shall not be set until the Contracting Officer has confirmed that [failover and disaster recovery have been tested, telephone numbers and channels have been transferred, and functional verification against the Functional Baseline is complete].

1. Replacement Platform (Days [31–150]). The Contractor shall assume operational responsibility on the Operational Transfer Date, which the Contracting Officer will set in writing and which shall be no earlier than Day [31] and no later than Day [150]. [Offerors may propose an earlier date.] Until the Operational Transfer Date, the incumbent CCI Contractor remains responsible for operating the platform and for the service levels in effect under its order. The Contractor shall be fully onboarded by the Operational Transfer Date. The Operational Transfer Date shall not be set until the Contracting Officer has confirmed that [failover and disaster recovery have been tested, telephone numbers and channels have been transferred, and functional verification against the Functional Baseline is complete].

1. Accountability (all Contractors). From the Operational Transfer Date, the Contractor is responsible for meeting all Track A service levels in Section 6.4. The Contractor shall measure and report them, and they are subject to surveillance under the QASP, to corrective action, and to payment reductions under Section 5.2.7. Inherited conditions identified in the Current-State Baseline under Section 5.2.4 are addressed as stated in that section. During the first [30] days after the Operational Transfer Date, the Contractor shall provide the heightened monitoring and reporting described in Section 5.2.5.

1. The Contractor shall hold, or obtain through the transition, all authorizations required to operate the platform, including a FedRAMP authorization at the Moderate level and VA Authority to Operate, with no gap in authorization.

5.2.3 Track B: Tier 0/Tier 1 Agent Services (150 Days)

The Contractor shall have one hundred fifty (150) calendar days from award to be servicing 100% of the Tier 0/Tier 1 workload at the required service levels. Track B comprises the phases below.

1. Onboarding. Bring Contractor personnel into the VA environment (access, background investigation, training). Continuous throughout the PoP.

1. Pre-Planning (Quality Gate 1). Access, training, knowledge acquisition, plan approval. Exit when VA approves the plans, validates training, and validates that staff have access to all required systems.

1. Tier 1 Services Transfer, Stage 1 (Quality Gate 2). Contractor assumes 100% of customer contacts (calls, chats, and tickets in queue) and meets the Track B service levels designated in Section 6.4 as Stage 1 metrics.

1. Tier 1 Services Transfer, Stage 2 (Quality Gate 3). By Day [150], the Contractor meets all Track B service levels and delivers Standard Operating Procedures.

The Contractor shall deliver a presentation at each Quality Gate demonstrating readiness, including staff onboarded, staff trained to work independently, and performance against service levels. If VA determines the Contractor is not ready to proceed, the Contractor shall issue a credit as specified in Section B of the contract. Quality Gate credits apply only through Day 180 and shall not be applied in addition to the quality withhold in Section 6.4.2 for the same month.

Deliverables:

A. Quality Gate 1 Presentation B. Quality Gate 2 Presentation C. Quality Gate 3 Presentation D. Standard Operating Procedures

5.2.4 Current-State Baseline Acceptance

The incumbent Contractors will provide VA a written statement of current state that includes, at a minimum: performance against each service level, volumes by channel and intent, open backlog, known defects and issues, knowledge article status, staffing, and configuration. VA, with support from the IVC, will validate each statement against Government data (including Medallia, ACD and ITSM data, and call recordings) before release to the Contractor. The Contractor shall:

1. Within thirty (30) days after Day 1 (Day 30 for both tracks), review the validated statements and agree or disagree, item by item, with supporting evidence.

1. Resolve disagreements with the Contracting Officer and COR using Government data. An item that the Contractor does not dispute within the review window is deemed accepted.

1. Understand that, once the Current-State Baseline is locked, the Contractor is bound by it and may not later claim as an inherited condition any item it did not raise during the review window.

Deliverable:

A. Current-State Baseline Response

5.2.5 Functional Baseline and Verification

The Contractor shall provide and maintain every function listed in the Functional Baseline (Attachment 2), either through the product currently providing it or through other software that provides the same functionality with no loss of functionality. The Contractor shall not remove, disable, or materially change any customer-facing function in the Functional Baseline without written Government approval. The Contractor shall complete a functional verification against the Functional Baseline at the end of the baseline verification period (Day [30]) and again at the Operational Transfer Date, shall report gaps, and correct each gap within the period approved by the COR. The Contractor shall also report any current-state functionality discovered during the first [90] days that is not in the Functional Baseline, for addition to the Baseline.

During the first [30] days after the Contractor assumes operational responsibility for each track, the Contractor shall provide heightened monitoring (hypercare), including [daily] reporting on IVR containment and drop-off, transfers, abandonment, and customer satisfaction trends.

Deliverables:

A. Functional Verification Reports B. Hypercare Report

5.2.6 Incumbent Coordination

The Contractor shall work with VA and the outgoing Contractors to transfer all applicable licenses, configuration and asset repositories, documentation, knowledge stores, processes, and contact channels (including telephone numbers, email addresses, and chat URLs). The Contractor shall confirm demarcation of responsibilities and interface points with all VA organizations and contractors.

5.2.7 Payment During Transition-In

Reductions in payment for missed service levels under Section 6.4 shall not begin before the date the service level is due. For Track A, service levels apply from the Operational Transfer Date under Section 5.2.2. For Track B, the Stage 1 service levels apply from Quality Gate 2 and the Stage 2 service levels apply from Quality Gate 3, as shown in Section 6.4.3. Any Quality Gate credit under Section 5.2.3 is separate from payment reductions for missed service levels, but it shall not be applied in addition to the quality withhold in Section 6.4.2 for the same month.

5.2.8 ITSM Tool Transition

VA may select a different ITSM tool during the PoP. If it does, the Contractor shall transition to the selected tool, re-establish all integrations in the Functional Baseline (including routing, surveys, reporting, and analytics integrations), validate them, and maintain the Functional Baseline throughout. The Contractor shall submit an ITSM Transition Plan within [30] days of VA notice. During an ITSM transition, the Glide Path is subject to the pause and re-validation rules in Section 5.8.5.

Deliverable:

A. ITSM Transition Plan

5.3 TIER 0 / TIER 1 CONTACT CENTER SERVICES

5.3.1 Single Point of Contact and Channels

The Contractor shall serve as the Single Point of Contact (SPOC) for all VA End Users, including Top 10 users, for IT incidents, service requests, and status inquiries. The Contractor shall provide Tier 0 (self-service) and Tier 1 services through all contact channels in use or introduced during the PoP, including telephone, live chat, self-service tickets and the service portal, SMS/text, and the Microsoft Teams channel. The Contractor shall execute Tier 0/Tier 1 services in accordance with ITIL practices as adopted by VA. The Contractor shall dynamically scale in real time to VA volumes, including surges, with no degradation of committed service levels, and shall use existing enterprise toll-free numbers unless directed otherwise. Top 10 users shall have a dedicated phone number that connects them directly with an agent trained to provide Top 10 user support, as documented in the training plan. Any call from the VA-designated priority customer list (currently ten customers) that requires a ticket to be escalated to another resolver group shall be accompanied by an instant message communication (currently Microsoft Teams), and the immediate handoff of the ticket shall be documented in the ITSM tool.

5.3.2 Incident and Request Management

1. Triage and resolve or route Incident tickets assigned to Tier 1 queues (in the ITSM tool or the contact center platform) in accordance with the relevant Knowledge Article and within service level thresholds.

2. Act as SPOC for user-initiated status inquiries about all Incidents.

3. Triage and resolve or route business-critical and Top 10 user Incidents in accordance with established VA operating procedures.

4. Fully document and process all customer interactions determined to be an Incident using the VA-provided ITSM tool, including an accurate description, comprehensive work notes, and attachment of the relevant Knowledge Article used to resolve or route the Incident.

5. Establish and maintain a dedicated, internal Incident Management Team (24 hours a day, 7 days a week, 365 days a year) to proactively identify potential Major Incidents presented to the Service Desk and actively participate in the VA Major Incident Management process. Incident analysts on this team shall be physically located at the Incident Command Center in Austin, Texas, and shall report to the Incident Command Center Supervisor as a first-response team for Major Incidents (Section 4.2).

6. Proactively identify, assess, and validate potential Major Incidents; escalate validated Major Incidents to the VA Major Incident Management Team; and communicate them to all Tier 1 staff and other service providers as directed by VA. Where validation through authoritative sources identified by VA is not possible, direct the escalation of the Major Incident with the Major Incident Management team.

7. Triage and fulfill or route Request tickets assigned to Tier 1 queues (in the ITSM tool or the contact center platform) in accordance with standard operating procedures and service level thresholds.

8. Act as SPOC for user-initiated status inquiries about all Requests.

9. Triage and fulfill or route urgent, business-critical, and Top 10 user Requests in accordance with established VA operating procedures.

10. Document and process all customer interactions related to Requests in the ITSM tool.

11. Collaborate with other IT entities (for example Change Management, Event Management, Major Incident Management, and Problem Management) to contribute the Tier 0/Tier 1 perspective, as requested by VA.

12. Use only VA-approved tools for customer interactions and triage.

5.3.3 Knowledge Management

1. The Contractor is wholly responsible for Tier 0 (self-service) and Tier 1 Knowledge Articles (KAs) located in a repository within the VA ITSM suite, inclusive of approximately 2,700 individual KAs requiring twice-yearly reviews and subsequent updates, as determined by the appropriate subject matter expert (SME). Projected growth of Tier 0 and Tier 1 KAs is 15 percent annually, with requests for new knowledge originating primarily from customers via the self-service portal, the ESD Process Integration team in support of intake efforts, or Tier 1 operational teams.

2. The Contractor shall ensure all Tier 0 and Tier 1 Knowledge Management (KM) staff have direct experience supporting a formal KM program in an operational environment and a fully documented training plan to facilitate operational readiness. KM certification for all KM staff is preferred.

3. The Contractor shall use the existing VA ITSM platform to fully document all Tier 0 and Tier 1 KA actions, including but not limited to creating, updating, and retiring KAs.

4. The Contractor shall ensure all Tier 0 and Tier 1 KAs are written at an eighth-grade reading level with clear and concise wording, proper grammar and syntax, free of editorial errors, following VA-specified format and style guides, where applicable, as determined by VA.

5. The Contractor shall use the VA-provided list of SMEs to identify the most knowledgeable and appropriate SME for each Tier 0 and Tier 1 KA. Where an appropriate SME cannot be identified from the VA-provided list, the Contractor shall coordinate with VA to identify a new SME and ensure all necessary tools and artifacts are made available to the newly appointed SME.

6. The Contractor shall follow all applicable VA KM processes while creating, updating, and retiring Tier 0 and Tier 1 KAs (for example the KA creation and update checklist, the KA publication process, and the “No Knowledge Article Found” process) and obtain written approval from VA before deviating from any established VA process. Where no process exists, the Contractor shall request specific guidance in writing from VA, ensuring any internally developed processes are coordinated with and approved by VA and stored in a centralized repository as specified by VA.

7. The Contractor shall ensure an internal quality review of each KA created or updated, using the VA-specified Article Quality Index (AQI) checklist and scoring rubric, before publication of any KA. This does not replace the random-sampling AQI conducted by VA to ensure service level compliance.

8. The Contractor shall ensure all submissions to create, update, or retire KAs are assigned within two business hours and completed within five business days of the request, based on guidance from the VA-specified SME for the applicable KA. Where a SME cannot be identified or reached within five business days, the Contractor shall notify VA before the timeline expires.

9. The Contractor shall create and attach at least 520 self-service instructional videos annually, including closed captioning, for all Tier 0 KAs, until all relevant Tier 0 KAs, as specified by VA, have a corresponding video.

10. The Contractor shall attend all ESD Process Integration (PI) intake meetings to facilitate proper KA creation or updates of applicable KAs as…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .