ESD Tier One - PWS RFI DRAFT 7.29.26.docx

Enterprise Service Desk (ESD) Tier One Support

VA-26-00084022

PERFORMANCE WORK STATEMENT (PWS)

DEPARTMENT OF VETERANS AFFAIRS

Office of Information & Technology Enterprise Command Operations (ECO)

Enterprise Service Desk (ESD) Tier One Support

Date: July 22, 2026

VA-26-00084022

PWS Version Number: 1.0

Contents

BACKGROUND

The Department of Veterans Affairs (VA or “Government”) is committed to creating an interactive experience for its technology users that is easy, pleasant, effective, and personalized. As part of this commitment, the VA is seeking to improve its efficiency and effectiveness of interactions by maintaining Tier-0 (Self-Service Services) and Tier-1 (Enterprise Service Desk (ESD) Services) via a Multi-Vendor Service Provider (MVSP) approach, inclusive of a Tier-1 (ESD) prime vendor as well as a Contract Center Infrastructure (CCI) vendor from a separate contract.

The purpose of this PWS is to establish a Task Order (TO) that enhances service delivery, reduces cost, increases business focus, and improves the quality of Information Technology (IT) Services to End Users.

The following are key business objectives the VA expects to maintain and enhance the end user experience through vendors partnering via an MVSP environment:

· Improve VA End User efficiency and effectiveness by adopting and leveraging existing knowledge databases within VA’s IT Service Management (ITSM) tool and leading IT service management practices in the areas of customer logging, tracking, reporting, and resolving of IT Tickets and service Requests.

· Improve efficiency and effectiveness by, early identification and Problem Resolution of Root Causes of technical issues including working with specialized Resolver Groups, such as VA staff and designated third parties, before they become trends.

· Improve IT customer service and Ticket Resolution speed through continuous Service Availability (24x7x365), self-service capabilities, and skilled personnel in the areas of industry standard IT products and services.

Each vendor shall collaborate in an environment where Incidents and Requests for all applications and related infrastructure services related to End User Tier-0 and Tier-1 Services, are received, monitored, tracked, and successfully resolved. IT service management practices used to support the delivery of Services shall be based on Information Technology Infrastructure Library (ITIL) best practices and any subsequent version of ITIL adopted in the IT industry and approved for use by VA. This ITIL based framework is a product of VA Office of Information and Technology’s (OIT) collaboration with business partners and industry and is being adopted to identify areas of improvement within the VA’s current organizational landscape.

The Tier-1 (ESD) vendor and CCI vendor shall provide a comprehensive Managed Services solution to support VA requirements for the Services briefly described below and as further defined within Section 5.4 (Managed Services Requirements). The MVSP shall support all VA staff located in Continental United States (CONUS) or Outside of the Continental United States (OCONUS) (e.g., American Samoa, Guam, Philippines, and Germany). All Services are to be provided in the English language, with Spanish Speaking service option as outlined in Optional Task Two.

The scope of the ESD is to provide IT support to all End Users, VA designated executives/executive assistants/ VIP End Users, on a 24x7x365 basis. The Tier-1 (ESD) vendor shall serve as the Single Point of Contact (SPOC) for all VA End Users (VA employees and VA designated third parties that use or have access to VA approved applications, hardware, software, data, and services that enable them to conduct daily business). The Contractor also shall be responsible for the end-to-end ticketing of all approved VA technologies and will work with the VA’s IT Department and appropriate third parties that provide IT support or services to ensure VA employees, and VA designated third parties are not impeded by, or prevented from, conducting daily business operations due to issues with VA applications, hardware, software, or data networks. In addition, the Contractor shall provide the ability to remotely manage, diagnose, and resolve issues related to VA desktops, laptops and notebooks, and software. Remote management services are those Services required to manage and control such devices and software over the network. This includes, maintaining and troubleshooting the operating systems and supported applications on such devices electronically to minimize the need to dispatch technical personnel, as well as fulfill approved service Requests (including access Requests).

NOTICE: As part of the Services, a separate Contact Center Infrastructure (CCI) vendor provides, manages, and maintains an Automated Call Distributor (ACD) and Interactive Voice Response (IVR) system, currently the NICE CXOne platform, that integrates with the VA Information Technology Service Management (ITSM) Tool, and delivers services in accordance with ITIL service-based management processes and procedures. The CCI vendor provides, in accordance with the CCI contract, VA’s ESD management with independent reports on the ESD Tier 1 vendor’s SLA compliance and overall ESD Tier 1 performance, manages and oversees the formal ESD Quality Assurance program and conducts regular and recurring QA audits on ESD Tier 1 agent interactions. In addition, the vendor develops and conducts customer satisfaction surveys (also in accordance with the CCI contract) to measure, analyze, and report results to improve End User Service. Accordingly, the CCI vendor has an organizational conflict of interest with this ESD Tier 1 Support work that cannot be avoided, neutralized or mitigated.

APPLICABLE DOCUMENTS

In the performance of the tasks associated with this Performance Work Statement, the Contractor shall comply with the following:

1. “Federal Information Security Modernization Act of 2014”

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

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

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

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

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

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

8. 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

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

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

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

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

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

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

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

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

17. 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

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

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

20. VA Directive 6500, “VA Cybersecurity Program,” February 24, 2021 (see VA NOTICE 24-18, dated September 27, 2024, “Update to VA Directive 6500 Cybersecurity Program”, and VA Notice 25-07, dated 3/18/25, “Amending VA Directive 6500 to incorporate M-24-15”)

21. 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”, and VA Notice 25-06, dated 3/18/25, “Amending VA Directive 6500 to incorporate M-24-15”, 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)

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

23. VA Handbook 6500.6, “Contract Security,” March 12, 2010 (see VA Notice 24-12, dated April 22, 2024, “Update to VA Handbook 6500.6, Contract Security, Appendix C VA Information and Information System Security/Privacy Language For Inclusion Into Contracts, As Appropriate”)

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

25. VA Handbook 6500.10, “Mobile Device Security Policy,” February 15, 2018 (see VA NOTICE 25-10, dated June 9, 2025, “Use of Personally Owned Mobile Devices Policy Amendment of Department of Veterans Affairs Handbook 6500.10”, and VA Notice 25-15, dated August 22, 2025, “Update to VA Handbook 6500.10 Mobile Device Security Policy”)

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

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

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

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

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

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

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

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

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

35. 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

36. NIST SP 800-53 Rev. 5, “Security and Privacy Controls for Federal Information Systems and Organizations,” September 23, 2020 (includes updates as of 12/10/2020)

37. VA Directive 0735, “Homeland Security Presidential Directive 12 (HSPD-12) Program,” October 26, 2015

38. VA Handbook 0735, “Homeland Security Presidential Directive 12 (HSPD-12) Program,” March 24, 2014

39. 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

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

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

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

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

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

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

46. VA Memorandum, VAIQ #7100147, “Continued Implementation of Homeland Security Presidential Directive 12 (HSPD-12),” April 29, 2011 (reference https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514)

47. IAM Identity Management Business Requirements Guidance document, May 2013, (reference Enterprise Architecture Section, PIV/IAM (reference https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

67. 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/

68. 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.

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

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

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

72. NIST SP 800-88 Revision 1 “Guidelines for Media Sanitization,” December 2014

73. CISA Binding Operational Directive (BOD) 19-02: “Vulnerability Remediation Requirements of Internet-Accessible Systems,” April 29, 2019, BOD 19-02: Vulnerability Remediation Requirements for Internet-Accessible Systems | CISA

74. CISA BOD 22-01: “Reducing the Significant Risk of Known Exploited Vulnerabilities,” November 3, 2021, BOD 22-01: Reducing the Significant Risk of Known Exploited Vulnerabilities | CISA

75. 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

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

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

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

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

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

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

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

SCOPE OF WORK

The Contractor shall serve as one of the vendors in the MVSP environment to provide Tier-0 and Tier-1 Services. The Contractor shall handle Tier 0/Tier 1 ITSM Incident and Service Requests in accordance with standard operating procedures and Service Level Agreement thresholds. These Services will include the technical, logistical, and programmatic services to fulfill the requirements of this PWS.

The Contractor’s solution shall utilize VA’s selected ITSM tool, currently ServiceNow (SNOW), however, this may change during Period of Performance (PoP). The industry standard ITSM to be utilized will be selected by VA. Should the ITSM tool be updated, the contractor will be required to transition to the new tool. As such, the Contractor shall be required to perform a second transition to the selected ITSM Tool after Transition-In.

This Service delivery environment will be supported by an ACD and IVR system, currently the NICE CXone platform, that is provided and managed by a Contact Center Infrastructure vendor in the MVSP environment. Existing capabilities of the deployed NICE CXone platform include, tailored call tree, front-end messaging capabilities, skills-based routing, integration with the existing ITSM suite to facilitate work item routing of LiveChat and self-service tickets, as well as SMS/text, callback, scheduled callback and Workforce Management forecasting and scheduling capabilities.

The Contractor’s Services shall be able to dynamically scale in real-time to VA’s volumes, including temporary surges of demand, with no degradation of committed Service Levels. The VA ESD covers approximately the following:

· Customer Base: ~600K VA internal employees/contractors with anticipated growth of approximately 5% per year and each customer generating 4.5 contacts per year

· Supports: ~ 900 Applications

· Call Volume: ~190K calls offered per month

· Chat Volume: ~ 4k chats offered per month

· Self-Service Ticket Volume: ~ 40K per month

· SMS/text Volume: pending release

· Average Handle Time: approx. 12.5 mins across all channels

The ESD provides a 24/7/365 operation that is a centralized desk supporting all VA internal employees/contractors including VIPs (~ 1700 senior executives and their executive assistants), that can respond to a host of issues involving hardware, and affected, software, applications, system access, password reset, facility and security.

The Tier 1 support model involves a singular contact queue inclusive of all agents with all agents handling all contact types (calls, LiveChat, self-service tickets and SMS/text) irrespective of the issue presented. Agents utilize extensive knowledge, inclusive of ~2500 Tier 0/1 knowledge articles in the ITSM Knowledge Base, to triage issues presented and provide request fulfillment, incident resolution or routing of incidents and requests to appropriate resolver groups when first-contact resolution cannot be provided.

The performance/functions outlined throughout the PWS are considered non-inherently governmental functions IAW Federal Acquisition Regulation (FAR) Subpart 7.7, and non-personal services IAW FAR 37.104.

PERFORMANCE DETAILS

PERFORMANCE PERIOD

The PoP shall be a six-month base period, four twelve-month option periods, one six-month option period and three optional tasks, to be exercised at the Government’s discretion.

The base period shall include tasks described in PWS sections 5.0 through 5.5. All Option Periods shall include tasks described in PWS sections 5.0, 5.1, 5.2, 5.4, and 5.5.

Included are Optional tasks for VIP Service Desk (5.5.1), Spanish Speaking Support (5.5.2), Scalable Cross-Functional Enterprise Project and Program Management (5.5.3), and Transition-out Services (5.5.4).

The total PoP shall not exceed 60 months.

Any work at the Government site shall not take place on Federal holidays or weekends unless directed by the Contracting Officer (CO).

There are 11 Federal holidays set by law (USC Title 5 Section 6103) that VA follows:

Under current definitions, five are set by date:

If any of the above falls on a Saturday, then Friday shall be observed as a holiday. Similarly, if one falls on a Sunday, then Monday shall be observed as a holiday.

The other six are set by a day of the week and month:

PLACE OF PERFORMANCE

Efforts under this contract shall be performed at Contractor facilities that shall be located within the continental United States. The Contractor shall identify the Contractor’s place(s) of performance in the Contractor Project Management Plan (CPMP). Remote telework by contractor personnel must be pre-approved by the COR. No work under this task order shall take place outside the United States. Remote telework for agents providing Tier 1 services must be distraction free to prevent degradation of services. Any degradation in services shall be grounds to revoke telework capabilities at the sole discretion of VA through modification of the contract.

Incident Management tasks identified under PWS 5.4.3.5 shall be performed at the VA Austin Information Technology Center (AITC).

ON-SITE ACCESS FOR GOVERNMENT PERSONNEL

The Contractor shall provide a workspace at the Contractor facilities for two VA employees. This workspace will provide VA employees with the ability to view real time managed Services performance data, and the rights to pull service agent activity and Call traffic related reports while at the Contractor facilities. The Contractor shall provide or make available reasonable office equipment and supplies for VA personnel to assist in the administration of the Services, including the following:

· Workspace

· Telephone

· Access to a printer

· Local Area Network (LAN) access (either wired or wireless)

HOURS OF COVERAGE

Services shall be provided to End Users 24 hours a day, 7 days a week, 365 days a year (24x7x365).

TRAVEL

During the base period, and any of the option periods, if exercised, VA anticipates requiring two people for four trips per year to either Washington, DC or Austin, TX for executive level meetings. The duration of each trip will be four calendar days. These costs will not be directly reimbursed by the VA.

VA additionally anticipates travel under this effort to attend enterprise project and program-related meetings or conferences in accordance with PWS 5.2.9 throughout the PoP. Include all estimated travel costs in your firm-fixed price line items. These costs will not be directly reimbursed by the Government.

Travel shall be in accordance with the Federal Travel Regulations (FTR) and requires advanced concurrence by the COR. Contractor travel within the local commuting area will not be reimbursed.

SPECIFIC TASKS AND DELIVERABLES

The Contractor shall provide the Services identified in this Section in the manner described in this PWS.

The Contractor shall provide all technical and management services to support the task, including program management, technology management, information and relationship management, human resources management, performance management, quality assurance/quality improvement, management reports, security, contingency/disaster recovery, and value engineering, as described in this PWS. All deliverables/work products shall be considered the intellectual property of VA. Intellectual property shall not be used outside of this contract without the express written consent of the Contracting Officer (CO) in coordination with the VA PM.

The Contractor shall furnish the necessary facilities, personnel, equipment, supplies, and services, as required, to meet the requirements of VA as established herein with the capability to support a wide range of communication channels (e.g., telephone, text, WebChat). In addition, the Contractor shall use existing enterprise toll-free numbers unless otherwise directed. The Contractor shall provide Services and perform all technical and management functions, as described in this PWS, to plan, design, implement, operate Tier-1 solutions. The Contractor shall also manage Tier-0 or self-service support (e.g., triaging tickets submitted through the self-service portal).

The Contractor must be prepared to, and will be required to, perform all Services relative to all actual contact volumes during the aforementioned PoP, notwithstanding the estimated volumes identified herein.

1.1 MULTI VENDOR SERVICE PROVIDER ENVIRONMENT

ESD services will be provided in a MVSP environment. Disparate contractors will provide complementary services, including the contact center infrastructure (CCI) and Tier 1 agent services. The Government requires a prime contractor providing the CCI services and a different prime contractor providing the Tier 1 (ESD) agent services, simultaneously. The Government expects these contractors to work cooperatively to the maximum extent possible to ensure seamless, high quality customer service.

The Contractor shall attend all VA-required (virtual and/or onsite) meetings in conjunction with other MVSPs to coordinate with other contractors and entities as described herein.

All materials and communications used to accomplish the work under this Contract shall be non-proprietary and be able to be used collaboratively by MVSP.

As such the Contractor shall ensure activities in support of this Contract are effectively coordinated with ESD stakeholders and other contractors. Where multiple contractors (under separate contracting vehicles) are involved in a task, the Contractor shall not communicate with other contractors without prior notification and approval from the CO, COR, and VA PM.

Activities and areas requiring Contractor coordination and cooperation shall include, but are not limited to, the following:

1. Comprehensive cross-area support and consistent messaging. This includes areas where functional area processes overlap with other program area processes, common data re-use requirements, and data and report submission standards. This interaction and coordination will be ongoing and applies broadly to all aspects of this Contract (e.g., common call flows and scripts, QA monitoring and reporting).

2. The functions/capabilities handoffs between the Contractor, ESD stakeholders, and other MVSP contractors, ensuring coordination and collaboration to provide holistic strategies, solutions, and reporting. For example:

a. Participation in call-flow testing as well as test calls before go-live events to assess performance and capture any lessons learned.

b. Developing or revising procedures, scripts, and use cases to ensure successful execution of services and transfer of tickets and tasks.

c. Knowledge management and sharing.

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

4. Share all deliverables, systems, data, and tools created from this Contract with stakeholders, at the request of the COR.

5. Contractors shall work cooperatively to identify service improvements and other efficiency projects relevant to CCI and Tier 1 processes and, if any are identified, the Contractor shall assign sufficient staff support to seek to develop process solutions that could be implemented.

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

7. Contractor shall fully cooperate with ESD and its contractors during timeframes when other contractors are in transition phases such as transition in and out.

1.2 PROJECT MANAGEMENT

1.2.1 CONTRACTOR PROJECT MANAGEMENT PLAN

The Contractor shall deliver a CPMP that lays out the Contractor’s approach, timeline, and tools to be used in execution of this contract effort. The CPMP should take the form of both a narrative and graphic format that displays the schedule, milestones, risks, and resource support. The CPMP shall also include how the Contractor shall coordinate and execute planned, routine, and ad hoc data collection reporting requests as identified within the PWS. The initial baseline CPMP shall be concurred upon and updated in accordance with Section B of the contract. The Contractor shall update and maintain the VA Program Manager (PM) approved CPMP throughout the PoP. The Plan shall include a subsection on how the Contractor intends to encourage and facilitate the hiring of Veterans in accordance with the PWS.

Deliverable:

A. Contractor Project Management Plan

1.2.2 TECHNICAL KICK-OFF MEETING

A technical kickoff meeting shall be held within 10 business days after award. The Contractor shall coordinate the date, time, and location (can be virtual) with the CO, as the Post-Award Conference Chairperson, the VA PM, as the Co-Chairperson, the Contract Specialist (CS), and the COR. The Contractor shall provide a draft agenda to the CO and VA PM at least five (5) business days prior to the meeting. Upon Government approval of a final agenda, the Contractor shall distribute to all meeting attendees. During the kickoff-meeting, the Contractor shall present, for review and approval by the Government, the details of the 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” which shall include notes on any major issues, agreements, or disagreements discussed during the kickoff meeting and the following 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 ESD Tier 1 Support. The Contractor shall submit the final updated presentation to the CO for review and signature within three (3) business days after the meeting. The Contractor shall also work with the CS, the Government’s designated note taker, to prepare and distribute the meeting minutes of the kickoff meeting to the CO, COR, and all attendees within three (3) business days after the meeting. The Contractor shall obtain concurrence from the CS on the content of the meeting minutes prior to distribution of the document.

Deliverables:

1. Kick-off Meeting Agenda

1. Kick-off Meeting Minutes

1. PowerPoint presentation with Summary Report

1.2.3 ESTABLISHMENT OF EXECUTIVE OVERSIGHT COMMITTEE

The Contractor shall designate representative members with the appropriate skills and experience to serve on the Executive Oversight Committee (EOC) which will be chaired by VA and comprised of several key executives from the Contractor and VA, which will meet, at a minimum, on a quarterly basis, and at such time as its members deem appropriate, to perform the following activities:

· Review and analyze the monthly performance reports for the preceding period, including any schedule overruns, Service Level attainment of targets, and any issues or Service Outages that affect Contractors’ overall performance.

· Review and discuss progress on the Resolution of issues.

· Attempt to Resolve, or designate individuals to attempt to Resolve, escalated Issues.

· Review and attempt to address escalated decisions.

· Prepare and deliver a Quarterly Review presentation. Presentation shall be delivered no later than two business days prior to the scheduled EOC meeting.

Contractor members of the Executive Oversight Team will include the Contractor Account Executive Sponsor, and Contractor Account Executive(s) providing oversight to this contract. The Contractor shall provide to VA for review and approval an EOC charter amendment identifying the members, roles/responsibilities, and processes for the EOC.

Deliverable:

A. EOC Charter Amendment B. EOC Review Presentation

1.2.4 ESTABLISHMENT OF A MANAGED SERVICES OVERSIGHT COUNCIL

The Contractor shall designate representative members with the appropriate skills and experience to the Managed Services Oversight Council (MSOC) which will be chaired by the VA Supplier Management Executive and will meet 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 will provide oversight to this contract and will serve as the Contractor’s highest-ranking representative on such council and have the authority to commit the Contractor (subject to VA reviews and approvals) to implement the course of action as deemed necessary by VA.

· Prepare and deliver a Monthly Review presentation. Presentation shall be delivered no later than two business days prior to the scheduled MSOC meeting.

Deliverable:

A. MSOC Review Presentation

1.2.5 REGULAR MEETINGS AND CONFERENCE CALLS

Contractor and VA representatives shall meet periodically to discuss matters arising under this PWS. Such meetings shall include the following:

· The meetings by the committee and council noted above.

· Such other meetings of VA and the Contractor personnel, including senior management of the Contractor, as the Government may reasonably request.

For each such meeting, the Contractor shall prepare an agenda which will incorporate the topics designated by VA. The Contractor shall distribute the agenda within five (5) business days of each meeting so that the meeting participants can prepare. In addition, the Contractor shall record, and distribute minutes for every meeting for review and concurrence by the Contracting Officer’s Representative (COR) within three (3) business days.

The Contractor shall notify the COR in advance of scheduled meetings with VA representatives or designated alternates (other than meetings pertaining to the provision of specific Services on a day-to-day basis) and shall invite the COR (or whomever the COR designates) to attend such meetings.

Deliverable:

A. Regular Meeting Agenda B. Regular Meeting Minutes

1.2.6 CONTRACTOR PERSONNEL

The Contractor shall ensure that all supervisory and/or management personnel and support staff (not to include agents) are ITIL Foundations certified to the latest ITIL version. The Contractor shall also ensure that all Incident Managers have specific incident management experience (preferably 3 years or more) in the VA environment. The contractor shall ensure all personnel with active VA network access accounts remain active.

1.2.7 REPORTING REQUIREMENTS

The Contractor shall provide the COR with weekly progress reports in electronic format. VA preference for these reports is Microsoft (MS) Word and MS Project formats. These reports shall reflect data as of the last day of the preceding week. The weekly progress reports shall cover all work completed during the reporting period and work planned for the subsequent reporting period. The weekly progress report shall include detailed instructions and explanations for each required data element to ensure that data is accurate and consistent. The report shall identify any issues that arose and a description of how the issues were resolved. If issues have not been completely resolved, the report shall include a discussion of the issue, actions taken to resolve, and an explanation of the Contractor’s plan and timeframe for resolving the issue. The report shall also include an itemized list of all Information and Communication Technology (ICT) deliverables and their current Section 508 conformance status. The Contractor shall monitor performance against the CPMP and report any deviations. The Contractor shall keep in communication with VA as needed to ensure that issues that arise are transparent to both parties.

The table below describes the Service reports in addition to the weekly progress report to be provided by Contractor to the VA in accordance with this PWS. It includes a summary description of the content and frequency of such Service reports.

· Review of resource allocation for past year and progress as compared to road map (goals and objectives).

· Attrition rate for the previous month Monthly

· List of solutions and capabilities needed to meet emerging requirements for ESD support Quarterly

Deliverables:

A. Progress Report B. Security and Virus Incidents Report C. Service Management Report D. Service Portfolio Management Report E. Contractor Personnel Certifications

1.2.8 ONBOARDING/OFFBOARDING

The Contractor shall manage the onboarding and offboarding of its staff. Onboarding includes steps to obtain a VA Personal Identification Verification (PIV) card, network and email account, complete VA required training, initiate background investigations, and gain physical and logical access. In addition, the Contractor shall identify individuals who may require elevated privileges to the necessary development and test environments for the various Systems.

A Contractor Onboarding SPOC shall be designated by the Contractor that tracks the onboarding and offboarding status of all Contractor personnel. The Contractor Onboarding SPOC shall be responsible for complete, accurate and timely submission of all required VA onboarding and offboarding paperwork to the VA COR. The Contractor shall be responsible for tracking the status of all its staff’s onboarding activities to include the names of all personnel engaged on the task, their initial training date for VA Privacy and Information Security training, their next required training date and PIV status. The Contractor Onboarding SPOC shall also report the status at the staff level during status meetings. The Contractor shall provide an Onboarding/Offboarding Status Report weekly for any staff with outstanding onboarding requests for review by the COR. The Contractor shall provide a bi-weekly all staff rosters.

Deliverable:

A. Onboarding/Offboarding Status Report B. All Staff Roster

1.2.9 CROSS-FUNCTIONAL ENTERPRISE PROJECT AND PROGRAM MANAGEMENT

The Contractor shall provide comprehensive program and project management, technical and subject matter expertise, to support executive leadership oversight of enterprise priorities, to include but not limited to Tier 1 End User Services support, cross-organizational analysis/design initiatives, proof of concepts, and related enterprise-level services coordination. The Contractor shall deliver an Enterprise Monthly Status report that documents work activities performed.

It is anticipated that the services performed under this task may require up to six (6) Full Time Equivalents (FTE).

The Contractor shall attend on-site program related meetings, up to two (2) per month per FTE . Anticipated locations include VA Medical Centers (e.g. Brooklyn, NY; Atlanta, GA; Orlando, FL; Palo Alto, CA; San Juan, PR), estimated at three (3) days in duration.

Deliverables:

A. Enterprise Monthly Status Report

1.3 TRANSITION-IN

The Contractor shall have one hundred and fifty (150) calendar days from contract award to service 100% of the Enterprise Service Desk (ESD) workload at a performance level that meets the Service Level Agreements (SLAs). The Contractor shall identify a Project Manager to plan, execute and monitor Transition-in activities and work with the Government and the outgoing Contractor to ensure a smooth, timely and complete transfer of services.

To maintain continuity of services and minimize potential negative effects during transitional phases, the Contractor shall develop a comprehensive Transition-In plan that describes the activities and processes needed to complete the Transition-in phases within the 180-day timeframe, which includes a 30-day stabilization period.

The Contractor shall:

1. Provide phase-in transition planning and execution of all PWS-specific tasks during the transition period handing off work from outgoing Contractor to the incoming Contractor.

2. Work closely with VA and other stakeholders to ensure knowledge transfer is thorough and all encompassing, to include: The transfer of all applicable hardware, software, licenses, services, information stores, configuration and asset repositories, operational and development processes, documentation, knowledge stores, and any other resource associated with the services. The transition planning shall include capturing knowledge of the current ESD design, implementation, and operations.

3. Conduct an initial Transition-in Planning meeting within five (5) business days after the contract kickoff meeting, with the VA COR, VA organizations identified by the COR, the ESD PMO, and outgoing Contractor resources.

4. Document the approach and milestones to transfer the full support requirements responsibilities in a Transition-in Plan.

The Transition-in Plan shall include at a minimum:

1. Review of program documentation.

2. Milestone schedule of transition activities.

3. Roles and Responsibilities matrix showing key personnel.

4. The plan to transition current support services.

5. Details on accessing and assessment of systems and tools.

6. Transition coordination schedule to meet with Government and Contractor representatives, including all VA organizations that hold responsibilities, to confirm demarcation of responsibilities and interface points for performance of work elements.

7. Transition schedule with tasks, duration, milestones, resource allocation, knowledge transfer sessions, and dates for completion of work transfer to Contractor.

8. Risks and associated risk mitigation plans.

9. Summary and schedule for Government-required training, clearance, and certifications.

Updates to the Transition-in plan can occur as needed and must be approved by the Government. Approved changes to the Transition-in plan shall be captured in a revised version of the plan, which shall be disseminated to all stakeholders.

The Contractor shall develop an On-Boarding Plan to ensure onboarding actions are performed in an accurate and timely manner throughout the period of performance, especially actions related to access to VA computer systems, and other security requirements. Additionally, the Contractor shall develop a Contractor Resource Continuity Plan that supports Contractor resource continuity, focused on retaining quality contract resources and provisions for timely resource backfill during unprogrammed turnover and/or a surge in service requirements.

Deliverables:

A. Transition-In Plan B. On-Boarding Plan C. Contractor Resource Continuity Plan

1.3.1 TRANSITION-IN PHASES

The Transition-in is comprised of the following phases, as described more fully below:

1. Onboarding – onboarding of Contractor personnel following contract award.

2. Pre-Planning – All activity associated with preparation in advance of engaging VA’s subject matter expert (SME) community and the out-going contractor for knowledge acquisition.

3. Tier 1 Services Transfer – All activity associated with the transfer of Tier 1 services to the re-compete Task Order GS-35F-393CA 36C10B24F0413. This phase shall be conducted in two stages. For Stage 1 the Contractor shall assume 100% of customer contacts and meet the majority of SLA metrics, for Stage 2 the Contractor shall meet all SLA metrics.

The Government will utilize the following gates to evaluate the Contractor’s readiness to proceed to the next stage/phase. Evaluation of the Contractor’s readiness will be based on the incoming Contractor’s performance in meeting its SLA metrics.

If the Contractor is deemed “not ready” to enter the next phase by the Government, then the Contractor shall issue a credit. The credit is calculated as 12.5 percent of the Monthly Recurring Charge (MRC) for that service. Further, if the Contractor fails to meet the SLA performance objective for two consecutive months, the Contractor must credit the Agency 25 percent of the MRC for that service; failure to meet the SLA performance objective for three consecutive months requires a credit of 50 percent of the MRC for that service. After the third consecutive month of failure to perform at the specified level, the Agency may discontinue the service through termination of contract.

1. Quality Gate #1 – Exit Detailed Pre-Planning Phase - Entry into Tier 1 Services Transfer Phase

2. Quality Gate #2 – Exit Tier 1 Services Transfer Phase Stage 1 - Entry of Stage 2

3. Quality Gate #3 – Exit Tier 1 Services Transfer Phase Stage 2

The following is a detailed description of the phases and the requirements of each:

ONBOARDING PHASE

a. Overall Approach The Onboarding phase consists of the activities associated with bringing Contractor personnel into the VA environment in a manner consistent with the contract. This is a continuous process throughout the PoP of the contract and may run concurrently with the other phases described herein.

b. Contractor Onboarding Requirements.

1. Provide qualified staffing resources to deliver Tier 1 services in a manner that meets SLAs as defined in this PWS.

2. Escalate any on-boarding issues immediately to the PM, COR, and CO.

3. Report on-boarding/off-boarding status/metrics in the weekly status report.

PRE-PLANNING PHASE

a. Overall Approach Pre-planning is a period in which Contractor develops the overall transition approach for the Services, prepares the Contractor personnel through education and training before the Tier 1 Services Transfer phase.

b. The Pre-planning phase shall include, but may not be limited to, the following activities:

1. Ensure proper access to required resources, systems, including telephony, and application is granted for all onboarded agents.

2. Ensure all required VA training is completed by all onboarded agents.

3. Develop familiarity and knowledge of the Services and the VA environment including review of Documentation, run books, Problem logs, training materials.

4. Update, as necessary, the Transition-in Plan for VA approval.

5. Deliver Quality Gate #1 presentation demonstrating that all of these activities have been executed to…