PWS EMCAO RFI 11.12.25.docx

Enterprise Messaging, Collaboration, Authentication and Office 365 Services Support Contract

VA-26-00011030

TRANSFORMATION TWENTY-ONE TOTAL TECHNOLOGY NEXT GENERATION (T4NG)

PERFORMANCE WORK STATEMENT (PWS)

DEPARTMENT OF VETERANS AFFAIRS

Office of Information & Technology Communication & Collaboration Services (CCS) Collaboration Services (CS)

Enterprise Messaging, Collaboration, Authentication and Office 365 Services Support Contract

Date: September 08, 2025

VA-26-00011030

Task Order PWS Version Number: 1.0

Disclaimer: The TAC accepts no liability for the completeness or correctness concerning the Information Technology content of this template. This template is a means to simply assist the requiring activity in developing their requirements. It is the Requiring Activity’s responsibility to ensure the correctness of all requirements within their final Performance Work Statement

Contents

BACKGROUND

The mission of the Department of Veterans Affairs (VA), Office of Information & Technology (OIT), Communication & Collaboration Services (CCS), Collaboration Services (CS) team is to provide benefits and services to Veterans of the United States. In meeting these goals, OIT strives to provide high quality, effective, and efficient Information Technology (IT) services to those responsible for providing care to the Veterans at the point-of-care, as well as throughout all the points of the Veterans’ healthcare in an effective, timely and compassionate manner. VA depends on Information Management / Information Technology (IM/IT) systems to meet mission goals.

Collaboration Services (CS), with support from Microsoft, is responsible for the management of all current Microsoft 365 applications, and any future Microsoft 365 applications that are added to the Software as a Service suite of applications that are included in our licensing agreement. The applications currently consist of, but are not limited to, Exchange, OneDrive, SharePoint, Teams, Azure Information Protection (AIP), Rights Management Server (RMS), etc.

Collaboration Services (CS) is also responsible for on-premises systems and applications that relate to the Microsoft 365 Software as a Service (SaaS) suite.

Support requests for the Microsoft 365 applications are submitted directly to Collaboration Services (CS) through email or via Service Now (SNOW) tickets.

In addition, this contract also provides support for both the Public Key Infrastructure (PKI) Service Line and the Enterprise Endpoint Management and Reporting (EEMR) division.

APPLICABLE DOCUMENTS

The documents in Paragraph 2.0 in the T4NG Basic PWS apply to the performance of this effort, there are no additional referenced documents.

SCOPE OF WORK

The Contractor shall provide administrative and operational support for VA messaging, collaboration, authentication, and configuration products and environments to include, but not limited to, Microsoft 365, Exchange, OneDrive, SharePoint, Teams, Purview \ eDiscovery, Azure Information Protection, Windows Server, PKI, SCCM, etc.

APPLICABILITY

This Task Order (TO) is within the scope of paragraph(s) 5.2, 5.3, 5.4, 5.5, and 5.6 of the T4NG Basic PWS.

ORDER TYPE

The effort shall be proposed on a Firm Fixed Price (FFP) basis.

PERFORMANCE DETAILS

PERFORMANCE PERIOD

The Period of Performance (PoP) shall be one 10-month base period with four option periods of 12 months each, if exercised.

PLACE OF PERFORMANCE

Tasks under this TO shall be performed in the nearest VA OI&T facility. Work may be performed at remote locations with prior approval of the Contracting Officer’s Representative. The Contractor shall maintain an online presence 24 hours a day, 365 days a year.

TRAVEL OR SPECIAL REQUIREMENTS

The Government does not anticipate travel to perform the tasks associated with this effort.

CONTRACT MANAGEMENT

All requirements of Sections 7.0 and 8.0 of the T4NG Basic PWS apply to this effort. This TO shall be addressed in the Contractor’s Progress, Status and Management Report as set forth in the T4NG Basic contract.

GOVERNMENT FURNISHED PROPERTY

The Government has multiple remote access solutions available to include Azure Virtual Desktop (AVD), Citrix Access Gateway (CAG), and Cisco AnyConnect VPN.

The Government’s issuance of Government Furnished Equipment (GFE) is limited to Contractor personnel requiring direct access to the network to: development environments; install, configure and run Technical Reference Model (TRM) approved software and tools (e.g., Oracle, Fortify, Eclipse, SoapUI, WebLogic, LoadRunner); upload/download/manipulate code; run scripts; apply patches; configure and change system settings; check logs; troubleshoot/debug; test/QA.

The Government will furnish desktops or laptops, for use by the Contractor to access VA networks, systems, or applications to meet the requirements of this PWS. The overarching goal is to determine the most cost-effective approach to providing needed access to the VA environment coupled with the need to ensure proper Change Management principles are followed. Contractor personnel shall adhere to all VA system access requirements for on-site and remote users in accordance with VA standards, local security regulations, policies and rules of behavior. Government Furnished Equipment (GFE) shall be approved by the Contracting Officer Representative (COR) and the Program Manager (PM) on a case-by-case basis prior to issuance.

Based upon the Government assessment of remote access solutions and requirements of this TO, the Government estimates that the following GFE will be required by this TO:

1. 35 laptops

The Government will not provide IT accessories, including but not limited to, mobile Wi-Fi hotspots, wireless access points, additional or specialized keyboards or mice, laptop bags, extra charging cables, extra Personal Identity Verification (PIV) card readers, peripheral devices, or additional Random Access Memory (RAM). The Contractor is responsible for providing these types of IT accessories in support of the TO as necessary and any VA installation required for these IT accessories shall be coordinated with the COR.

The Status of Government Furnished Equipment Report under the T4NG Basic Contract requirements is applicable to this TO and shall be delivered to the COR/VA PM as required.

SECURITY AND PRIVACY

All requirements in Section 6.0 of the T4NG Basic PWS apply to this effort. Specific TO requirements relating to Addendum B, Section B 4.0, paragraphs j and k supersede the corresponding T4NG Basic PWS paragraphs, and are as follows:

j. The vendor shall notify VA within 24 hours of the discovery or disclosure of successful exploits of the vulnerability which can compromise the security of the Systems (including the confidentiality or integrity of its data and operations, or the availability of the system). Such issues shall be remediated as quickly as is practical, but in no event longer than 10 days.

k. When the Security Fixes involve installing third party patches (such as Microsoft OS patches), the vendor will provide written notice to VA that the patch has been validated as not affecting the Systems within 10 working days. When the vendor is responsible for operations or maintenance of the Systems, they shall apply the Security Fixes within 15 days.

All requirements in Section 6.0 of the T4NG Basic PWS apply. Addendum B requirements have been tailored to reflect the security and privacy requirements of this specific TO.

POSITION/TASK RISK DESIGNATION LEVEL(S)

In accordance with VA Handbook 0710, Personnel Security and Suitability Program, the position sensitivity and the level of background investigation commensurate with the required level of access for the following tasks within the PWS are:

Position Sensitivity and Background Investigation Requirements by Task Task Number Tier1 Low Risk Tier 2 Moderate Risk Tier 4 High Risk

The Tasks identified above and the resulting Position Sensitivity and Background Investigation requirements identify, in effect, the Background Investigation requirements for Contractor individuals, based upon the tasks the particular Contractor individual will be working. The submitted Contractor Staff Roster must indicate the required Background Investigation Level for each Contractor individual based upon the tasks the Contractor individual will be working, in accordance with their submitted proposal.

SPECIFIC TASKS AND DELIVERABLES

The Contractor shall perform the following:

PROJECT MANAGEMENT

Historically, the support for this task has been covered by one FTE.

CONTRACTOR PROJECT MANAGEMENT PLAN

The Contractor Project Manager shall deliver a Contractor Project Management Plan (CPMP) that lays out the Contractor’s approach, timeline and tools to be used in execution of this TO 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 TO. The Contractor shall update and maintain the VA Program Manager (PM) approved CPMP throughout the PoP.

Deliverable:

A. Contractor Project Management Plan (CPMP)

REPORTING REQUIREMENTS

The Contractor shall prepare weekly, monthly, quarterly and yearly reports, in electronic format. The report shall contain the number of SNOW tickets opened / closed related to each of the areas of support for that time period. Changes to reporting information may be made to provide the VA with metrics as needed.

Deliverable:

A. Status Reports

TECHNICAL KICKOFF MEETING

A technical kickoff meeting shall be held within 10 days after TO award. The Contractor shall coordinate the date, time, and location (can be virtual) with the Contracting Officer (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) calendar days prior to the meeting. Upon Government approval of a final agenda, the Contractor shall distribute the agenda 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 the Collaboration Services Support Contract.” The Contractor shall submit the final updated presentation to the CO for review and signature within three (3) calendar days after the meeting. The Contractor shall also work with the Contract Specialist, 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) calendar days after the meeting. The Contractor shall obtain concurrence from the Contract Specialist on the content of the meeting minutes prior to distribution of the document.

Work Plan The purpose of the bi-weekly (every two weeks) work plan is to provide a tool to allow VA to effectively manage this TO, as well as reprioritize activities on a bi-weekly basis. The Contractor shall prepare a Bi-Weekly Work Plan, which includes information on all activities currently ongoing as part of this contract. Specifically, the Bi-Weekly Work Plan shall include the following data elements for each activity ongoing under this PWS:

1. Project and specific activities.

2. Overview and description of the activity.

3. Overall high-level assessment of progress of the activity.

4. All work in progress and completed for the activity during the period.

5. Identification of any contract related issues uncovered during the previous period and especially highlight those areas with a high probability of impacting schedule, cost or performance goals and their likely impact on schedule, cost, or performance goals.

6. Explanations for any unresolved issues, including possible solutions and any actions required of the Government and/or Contractor to resolve or mitigate any identified issue, including a plan and timeframe for resolution.

7. Status on previously identified issues, actions taken to mitigate the situation and/or progress made in rectifying the situation.

8. Work planned for the subsequent period.

9. Current activity schedule overlaid on original activity schedule showing any delays or advancement in schedule.

10. Current expenditures overlaid over the original budget showing any deviations in the actual expenditures versus the original budget and versus the current budget.

11. Workforce staffing data showing all Contractor personnel performing on the effort during the previous period. After the initial labor baseline is provided, each Bi-Weekly Work Plan Report shall identify any changes in staffing identifying each person who was added to the activity, removed, and/or moved from one product to another from the TO. This should also include any planned travel for the activity.

12. Original schedule of deliverables and the corresponding deliverables made during the previous period.

13. Bi-Weekly-On-Boarding Status Reports in electronic form. This data shall include but is not limited to status of personnel during on-boarding activities including anticipated personnel, training status and Security Clearance status.

14. Strategic Planning-Analysis Activity Summary.

Additionally, the Contractor shall conduct a bi-weekly meeting to present the Bi-Weekly Work Plan. These reports shall not be the only means of communication between the Contractor, COR and the PM to advise of performance/schedule issues and to develop strategies for addressing the issues. The Contractor shall continuously monitor performance and report any deviation from the CPMP or previous Work Plan to the COR and PM during routine, regular communications. The Contractor shall respond to all COR queries related to project milestones and schedule within four business hours of receipt of written request.

Deliverable:

A. Bi-Weekly Work Plan On boarding / off boarding The Contractor shall be responsible for the on-boarding \ off-boarding of all Contractor staff on the contract.

For on-boarding, the Contractor shall:

1. Collect signed rules of behavior documents, signed non-disclosure agreements, training certificates, applications for access to VA information systems, Personal Identity Verification (PIV) card requests and other related information, for assigned Product Team’s, and provide secure storage for the documents and files, in accordance with VA guidance.

2. Provide the documents, files and information to the VA PM, COR or IT staff for review/approval/signature, when requested, to support VA’s on-boarding process for granting access to VA systems.

3. Prepare and submit access requests, including TMS applications, PIV card applications, and current VA approved contractor request forms. After receipt of a favorable Special Agreement Check (SAC) determination, and COR approval, the Contractor shall create Helpdesk tickets to request VA user accounts (for e-mail and remote access).

4. Monitor the submission of the artifacts and follow up to ensure that all artifacts submitted are complete and correct. The Contractor shall track VA system access requests, for assigned Product Teams to completion.

The Contractor shall provide a summary of the on-boarding support activities in the Contractor’s Progress Status and Management Report (CPSMR). For off-boarding the contractor shall manage the off-boarding process for VA access, and to individual system/environment access, for all Contractors on this contract. The Contractor shall prepare all forms necessary for termination of access to VA information systems, in accordance with VA guidance. The Contractor shall assist in confirming whether the GFE equipment, associated documentation, and PIV card has been returned to the proper receiving authorities in accordance with VA policy. All findings shall be documented in the Bi-Weekly Work Plan required under this PWS.

Deliverables:

A. Monthly Resource Management Report B. Contractor’s Progress Status and Management Report Help desk support The Contractor shall support help desk tickets related to issues with the applications covered in PWS sections 5.3 – 5.9. The Government estimates there will be approximately 4,000 – 6,000 tickets per month across all applications cited in PWS sections 5.3 – 5.7.

The contractor is responsible for managing all CS ticket queues and ticket assignments to include escalating critical and high priority tickets to appropriate groups within CS to ensure that service level agreements (SLA) are met.

The contractor shall also provide incident response for all high priority incidents (HPI) and critical priority incidents (CPI) that require support from CS, and will escalate if unable to answer the questions or resolve the issue.

Service Level Agreement (SLA) The Contractor shall adhere to the following response/resolution times for new tickets entered to the queue.

The contractor shall work with VA to develop and maintain Standard Operating Procedures (SOPs) for each supported application. The SOPs shall detail the step-by-step processes required to work on and resolve tickets. These will be dynamic documents related to the latest applications and issues being supported.

main microsoft 365 applications The Contractor shall provide 24x7x365 support for all applications that are part of the VA’s Microsoft 365 tenant. The contractor shall provide end-to-end support for Microsoft 365 environments using VA Directive 6004 and VA Handbook 6500. This support includes all current Microsoft 365 applications, and all future Microsoft 365 applications. Microsoft 365 is in a hybrid state, with the on-premises Active Directory being authoritative. At a minimum, this support shall include, but is not limited to the following:

Messaging Responsibilities include, but are not limited to:

1.Monitor and address support requests in the Tier 3 Service Now ticket queue

a. Active Directory User Account Intra/Inter Domain Moves

b. Provision, configure and manage Shared Mailboxes and Distribution Groups

c. Possess basic PowerShell skills to bulk provision mailboxes / groups.

d. Monitor / resolve alerts associated with the on-premises and cloud-based messaging and collaboration infrastructure

e. Troubleshoot and resolve Service Now tickets related to email encryption support in Outlook for AIP, PKI or any version of RMS.

OneDrive Responsibilities include, but are not limited to:

1. First time setup training

2. Usage and feature training

a. Secure sharing

b. Adding additional owners

3. Troubleshooting

a. Sign in issues

b. Sync issues

c. Sing in and sharing issues after M365 reactivation

d. Missing files Sharepoint Responsibilities include, but are not limited to:

1. Provide technical support for SharePoint Online site collection administrators

2. Configure and troubleshoot SharePoint permissions

3. Create and administer SharePoint Online site collections and sub-sites.

4. Create, customize, and support SharePoint lists and libraries

5. Troubleshoot SharePoint Designer workflows and Power Automate flows.

6. Create, customize, and troubleshoot Microsoft InfoPath forms and data connections

7. Provide technical support for Microsoft Teams integration with SharePoint and OneDrive.

8. Utilize PowerShell to administer SharePoint Online sites, groups, users, and service configurations.

9. Maintain and customize SharePoint Online site collection templates such as Communications sites, Microsoft 365 Group sites, Team sites, and Project sites.

10. Support Microsoft PowerApps to create SharePoint Online integrated forms and applications

11. Support Microsoft Power Automate to create SharePoint online integrated Flows

12. Provide technical support of OneDrive for Business including SharePoint Online personal site and OneDrive sync client issues.

Teams Responsibilities include, but are not limited to:

1. Administration and support of Microsoft Teams application and any applications embedded within the Microsoft Teams application.

2. Support end user functionality

3. Creation and enhancement of Team’s related user knowledge articles, FAQ’s, training materials and Service Now Knowledge Base articles.

4. Licensing, activating and troubleshooting new users within the VA enterprise.

ancillary microsoft 365 applications The Contractor shall provide 24x7x365 support for all applications that are part of the VA’s Microsoft 365 tenant. The contractor shall provide end-to-end support for Microsoft 365 environments using VA Directive 6004 and VA Handbook 6500. This support includes all current Microsoft 365 applications, and all future Microsoft 365 applications. Microsoft 365 is in a hybrid state, with the on-premises Active Directory being authoritative. At a minimum, this support shall include, but is not limited to the following: Microsoft Bookings, Lists, Planner, Stream, ToDo, Whiteboard, etc.

MICROSOFT SPECIALIZED SUPPORT

The contractor shall provide product support that is equal to the support currently provided by the three dedicated VA Microsoft Support Technical Engineers to consist of, but not limited to, product support needs, product engineering needs, high level scripting, special projects, project escalations, and will deal with Microsoft directly when needed. Responsibilities include, but are not limited to:

1. Tier 4 AIP product support similar to the work performed by the Microsoft person in that role (Stephen Crane). Support of the AIP product suite, Data Loss Prevention (DLP) policies, Controlled Unclassified Information (CUI) configuration, issue escalation to Microsoft Product Groups, etc.

2. Tier 4 Messaging product support similar to the work performed by the Microsoft person in that role (Willima Dvorak). Support of the internal and external cloud based Microsoft Exchange platforms, high level scripting, issue escalation to Microsoft Product Groups, etc.

3. Tier 4 Teams product support similar to the work performed by the Microsoft person in that role (Shyam Patel). Support of the Teams environment, escalation to Microsoft Product Groups, etc.

E-DISCOVERY

Responsibilities include, but are not limited to:

Performing mailbox extractions in Microsoft 365 cloud for various VA clients, including the Office of Inspector General (OIG), Office of General Counsel (OGC), Department of Justice (DOJ), International Organization for Standardization (ISO), Veterans Affairs Central Office (VACO), Veterans Integrated Service Networks (VISN), Administrative Investigation Board (AIB), Office of the Secretary, U.S. Dept. of Veterans Affairs (OSVA), among others.

1. eDiscovery Case Management:

a) Create, configure, and manage eDiscovery Purview cases.

b) Identify custodians and data sources across Exchange Online, SharePoint, OneDrive, and Teams.

c) Place legal holds to preserve data required for litigation or investigations.

d) Ensure compliance with legal, regulatory, and internal policies.

2. Search & Collection:

a) Run content searches across Microsoft 365 workloads.

b) Perform mailbox keyword searches using the Discovery Attender tool.

c) Optimize search queries to ensure relevant, accurate, and defensible results.

3. Review & Analysis:

a) Provide secure access to review sets for legal and compliance teams.

b) Use built-in analytics (themes, email threading, near-duplicate detection).

c) Apply tagging, coding, redaction, and annotation for review workflows.

4. Export & Reporting:

a) Export collected data in legally defensible formats (e.g., EDRM).

b) Maintain chain-of-custody documentation.

c) Generate reports on searches, holds, and review activities.

5. Compliance & Security:

a) Monitor, audit, and document all eDiscovery activities.

b) Ensure compliance with GDPR, HIPAA, SOX, and other regulatory standards.

c) Follow data minimization and confidentiality practices.

6. Collaboration & Support:

a) Partner with Legal, Compliance, HR, and Security teams to support investigations.

b) Provide training and guidance to stakeholders on eDiscovery best practices.

c) Act as a point of escalation for complex discovery issues.

7. Continuous Improvement:

a) Stay updated on Microsoft Purview features and updates.

b) Recommend process improvements for search, review, and case management.

c) Support automation initiatives to increase efficiency.

8. Decryption of Encrypted Content:

a) Perform decryption of S/MIME and RMS-encrypted emails for discovery and review purposes.

b) Ensure decrypted data is properly protected and accessible only to authorized personnel.

9. Ticket & Workflow Management:

a) Review and manage DSC intake tickets to process new eDiscovery requests.

b) Prioritize, track, and resolve tickets in alignment with SLA and compliance requirements.

c) Document actions taken for auditing and transparency.

10. Restoring individual lost or missing mailbox items in the Office 365 cloud.

11. Coordinating the collection of data from OneDrive and SharePoint.

12. Creating accounts and providing training to support Office of General Counsel reviews.

13.Managing eDiscovery through the Microsoft Purview admin center and Windows PowerShell cmdlet.

14. Supporting ITOPS in developing policies, procedures, and processes, both written and process flow maps.

15. Providing support to ITOPS SMEs with eDiscovery requests in the Microsoft Exchange and Microsoft 365 environments utilizing eDiscovery tools.

INTERAGENCY COLLABORTATION AND AUTHENTICATION

VA does interagency collaboration with external agencies \ partners, and the goal is to support that collaboration using the Microsoft Entra ID Business to Business (B2B) solution or equivalent. Responsibilities include, but are not limited to:

1. Program Management of Inter-Agency B2B initiatives:

a. Provide comprehensive program management services to facilitate inter-agency B2B collaboration.

b. Coordinate with all stakeholders to ensure issue resolution within 72 hours.

2. Engineering and Site Integration:

a. Perform detailed site assessments to integrate B2B solutions.

b. Develop and implement Integration Plans that align with agency-specific requirements.

c. Ensure all integrations comply with federal standards and security protocols.

d. Responsible for successful execution of site / program enablement’s.

e. Manage enablement intake procedures.

3. Support Help Desk Operations:

a. Establish and maintain a B2B support help desk to provide operational assistance.

b. Scale support staffing as sites / programs are enabled at an acceptable ratio; VA anticipates the following number of support requests or tickets based on portfolio tier:

i. Full B2B organization integration: approximately 40 tickets per month, per site or per program.

ii. Partial B2B organizational or ‘Shared Team’ type of integration: approximately 20 tickets per month, per site or per program.

iii. Individual contributor support: approximately 500 tickets per month.

c. Provide Tier 1 through Tier 3 support services, ensuring issue resolution and user satisfaction within 24 hours.

4. Release Management, Training, and Documentation:

a. Coordinate releases among teams and B2B stakeholders to ensure communication and precise execution of site / program enablement’s or changes.

b. Ensure recurrent training, community of practice, and program updates are communicated to user base and stakeholders.

c. Update and manage B2B and related technology knowledge repositories at a normalized cadence and in accordance with VA standards and requirements.

5. Enterprise B2B Security Engineering:

a. Deploy enterprise-level security engineers to support B2B cybersecurity requirements.

b. Develop and maintain cyber documentation practices, including compliance with federal cybersecurity standards, VA cybersecurity and authorization to operate, authorization to connect.

c. Implement and monitor security measures to safeguard B2B integrations and data.

d. Intervene and support any B2B related incidents.

6. B2B Application Integration and Custom Engineering:

a. Perform application integration and custom engineering to meet specific agency B2B requirements.

b. Ensure all applications and custom solutions are secure, scalable, and compliant with VA, partner stakeholders, and federal regulations.

Deliverables:

A. Project Plans, Schedules, and Progress Reports.

B. Release Management Processes for B2B applications and services.

C. Training sessions and materials tailored to end-user and administrator needs.

D. Memorandum of Understanding, Memorandum of Agreement, Memorandum for the Record, or Interconnect Security Agreement

SECURITY TEHCNICATION ADMINSTRATION AND OPERATIONAL SUPPORT

Responsibilities include, but are not limited to:

1. Provide technical support to the Public Key Infrastructure (PKI) Service Line.

2. Troubleshoot end user certificate usage issues.

3. Troubleshoot applicant certificate usage and validation issues.

4. Support of Linux based OCSP Responders.

5. Support of Linux based CRL Distribution Points.

6. Support of Validation Authorities.

7. Support of Simple Certificate Enrollment Protocol (SCEP) technology.

8. Support of Linux based HSMs.

9. Support of C, C++, Perl, python, java, CGI and Shell Scripting.

10. Providing guidance and consulting for architectural design of Public Key Infrastructure (PKI).

11. Support of RedHat Certificate System.

12. Troubleshooting of Linux and UNIX based systems regarding PKI certificates.

ENTERPRISE ENDPOINT ENGINEERING (SCCM)

The contractor shall serve as a consultant for the Department of Veterans Affairs (VA), Office of Information and Technology (OIT), End User Operations (EUO), Endpoint Engineering (EE), Enterprise Endpoint Management and Reporting (EEMR) division. The Contractor shall work with the division director and other EEMR team members to provide services in support of a technical framework including systems engineering, report development, optimization, design improvement, testing, integration, infrastructure support, and interoperability support throughout the enterprise.

Responsibilities include, but are not limited to:

1. Architecture design, implementation, and support of Endpoint Management technologies within the VA Enterprise environment

2. Systems engineering and system administration

3. Level 4 Customer Support

4. Enterprise reporting using Microsoft SQL Server Reporting Services and Microsoft Power BI

5. Establishment, documentation, and implementation of standardized best practices

6. Infrastructure as a Service (IaaS) support of Endpoint Management systems within an Entra ID cloud environment

7. Support of Microsoft System Center Configuration Manager (SCCM)

8. Support of Microsoft Intune

9. Support of 1E Nomad Branch

10. Support of 1E Tachyon

11. Support of Microsoft SharePoint

PHASE IN/ PHASE OUT TRANSITION PLAN

The Contractor shall develop and deliver a Transition Plan 30 days prior to the end date of the contract, and the end date of each option year.

The following list is a Transition Checklist. The Contractor shall address each of the Transition Checklist items in the Transition Plan:

1. Inventory, review, evaluation, and transition of VA-furnished information and other items such as:

a. Hardware / software

b. Laptops / PCs

2. Inventory and transition of historical data (specifically memos, letters, correspondence, regulations, reports, documents, transition agreement documents, software licensing agreements, hardware maintenance agreement, memorandums of agreement/ understanding, and inter-service agreements, and system administration passwords, system logs, database logs)

3. Any SLA’s and SOPs used in day-to-day operations

4. An orientation phase to introduce the Contractor personnel, programs, and users to the incoming team, explaining tools, methodologies, and business processes

5. Procedures to introduce VA personnel, programs, and users to the Contractor's team, tools, methodologies, and business processes

6. The Contractor strategy regarding personnel staffing and training during the transition period

7. Process for transfer of existing on-hand inventory

8. Signed turnover agreements

Deliverables:

A. Transition Plan Report

OPTION PERIOD ONE

If Option Period One is exercised by the Government, the Contractor shall perform all the tasks and deliverables defined in Sections 5.1, 5.2, 5.3, 5.4, 5.5, 5.6, and 5.7 for a 12-month PoP.

OPTION PERIOD TWO

If Option Period Two is exercised by the Government, the Contractor shall perform all the tasks and deliverables defined in Sections 5.1, 5.2, 5.3, 5.4, 5.5, 5.6, and 5.7 for a 12-month PoP.

OPTION PERIOD THREE

If Option Period Three is exercised by the Government, the Contractor shall perform all the tasks and deliverables defined in Sections 5.1, 5.2, 5.3, 5.4, 5.5, 5.6, and 5.7 for a 12-month PoP.

OPTION PERIOD FOUR

If Option Period Four is exercised by the Government, the Contractor shall perform all the tasks and deliverables defined in Sections 5.1, 5.2, 5.3, 5.4, 5.5, 5.6, and 5.7 for a 12-month PoP.

GENERAL REQUIREMENTS

PERFORMANCE METRICS

The table below defines the Performance Standards and Acceptable Levels of Performance associated with this effort.

2. Efficient and effective in meeting requirements

3. Meets technical needs and mission requirements

4. Provides quality services/products

5. Incorporates “ease of use” Human Centered Design principles in any software developed.

Satisfactory or higher

2. Products completed, reviewed, delivered in accordance with the established schedule

3. Notifies customer in advance of potential problems Satisfactory or higher

2. Personnel possess necessary knowledge, skills and abilities to perform tasks

Satisfactory or higher

The COR will utilize a Quality Assurance Surveillance Plan (QASP) throughout the life of the TO to ensure that the Contractor is performing the services required by this PWS in an acceptable level of performance. The Government reserves the right to alter or change the QASP at its own discretion. A Performance Based Service Assessment will be used by the COR in accordance with the QASP to assess Contractor performance.

SECTION 508 – INFORMATION AND COMMUNICATION TECHNOLOGY (ICT) STANDARDS

On January 18, 2017, the Access Board issued a final rule that updated accessibility requirements covered by Section 508 and refreshed guidelines for telecommunications equipment subject to Section 255 of the Communications Act. The final rule went into effect on January 18, 2018. The revisions and updates to the Section 508-based standards and Section 255-based guidelines are intended to ensure that information and communication technology (ICT) covered by the respective statutes is accessible to and usable by individuals with disabilities.

The following Section 508 Requirements supersede Addendum A, Section A3 from the T4NG Basic PWS.

The Section 508 standards established by the Access Board are incorporated into, and made part of all VA orders, solicitations and purchase orders developed to procure ICT. These standards are found in their entirety at: Revised 508 Standards and 255 Guidelines (access-board.gov). A single PDF file version of the Revised Section 508 Standards and 255 Guidelines will be supplied upon request, or can be obtained from the Access Board website. Federal agencies must comply with the Rehabilitation Act of 1973, as amended.

The Contractor shall comply with “508 Chapter 2: Scoping Requirements” for all electronic ICT and content delivered under this contract. Specifically, as appropriate for the technology and its functionality, the Contractor shall comply with the technical standards marked here:

COMPATIBILITY WITH ASSISTIVE TECHNOLOGY

The standards do not require installation of specific accessibility-related software or attachment of an assistive technology device. Section 508 requires that ICT be compatible with such software and devices so that ICT can be accessible to and usable by individuals using assistive technology, including but not limited to screen readers, screen magnifiers, and speech recognition software.

ACCEPTANCE AND ACCEPTANCE TESTING

Deliverables resulting from this solicitation will be accepted based in part on satisfaction of the Section 508 Chapter 2: Scoping Requirements standards identified above.

The Government reserves the right to test for Section 508 Compliance before delivery. The Contractor shall be able to demonstrate Section 508 Compliance upon delivery.

ENTERPRISE AND IT FRAMEWORK

A signed waiver has been obtained from the VA OI&T CIO Office that the IPv6 requirement within Section 3.8.3 of the T4NG Basic Contract cannot be met, and as a result, IPv6 is not a requirement for this TO effort.

T4NG TO Performance Work Statement Template_JUL_28_2025 T4NG TO PWS Template Revision History

T4NG TO Performance Work Statement Template_JUL_28_2025 image1.jpeg