Performance Work Statement ILEAD_V2.0_DRAFT.pdf

PERFORMANCE WORK STATEMENT (PWS)

DEPARTMENT OF VETERANS AFFAIRS

Office of Information & Technology (OIT) Information Technology Operations and Services, Infrastructure Operations

Institute of Learning, Education and Development (ILEAD) Information Technology (IT) Services Support

Date: August 24, 2026

VA-27-00002336

PWS Version Number: 2.0

Contents

1.0 BACKGROUND

2.0 APPLICABLE DOCUMENTS

3.0 SCOPE OF WORK

3.1 ORDER TYPE

4.0 PERFORMANCE DETAILS

4.1 PERFORMANCE PERIOD

4.2 PLACE OF PERFORMANCE

4.3 TRAVEL

5.0 SPECIFIC TASKS AND DELIVERABLES

5.1 PROJECT MANAGEMENT

5.1.1 TECHNICAL KICKOFF MEETING

5.1.2 CONTRACTOR PROJECT MANAGEMENT PLAN

5.1.3 WEEKLY REPORTING REQUIREMENTS

5.1.4 PRIVACY TRAINING

5.2 ILEAD NETWORK INFRASTRUCTURE SUPPORT

5.3 SYSTEMS ADMINISTRATION

5.4 OFFICE OF INFORMATION AND TECHNOLOGY VIRTUAL mACHINE (oi&t

vm) SERVERS

5.5 APPLICATIONS DATABASE SUPPORT

5.6 BUSINESS SYSTEMS ANALYSIS

5.7 CORE BUSINESS SYSTEMS INFRASTRUCTURE SUPPORT SERVICES . 16

5.7.1 ILEAD BROADCAST AND VIDEO DEVICE ARCHITECTURE

5.7.1.1 AVID EDITING ENVIRONMENT

5.7.1.2 AVOCENT HMX DIGITAL HIGH PERFORMANCE KVM ENVIRONMENT

5.7.1.3 BIT CENTRAL ON AIR AUTOMATION SYSTEM

5.7.1.4 ON AIR BROADCAST TRAFFIC SCHEDULING SYSTEM

5.7.1.5 MEDIA ASSET MANAGEMENT (MAM) SYSTEM

6.0 GENERAL REQUIREMENTS

6.1 ENTERPRISE AND IT FRAMEWORK

6.1.1 VA TECHNICAL REFERENCE MODEL

6.1.2 ZERO TRUST – VA CRITICAL SECURITY CONTROLS

6.1.3 FEDERAL IDENTITY, CREDENTIAL, AND ACCESS MANAGEMENT

(FICAM)

6.1.4 INTERNET PROTOCOL VERSION 6 (IPv6)

6.1.5 TRUSTED INTERNET CONNECTION (TIC)

6.1.6 STANDARD COMPUTER CONFIGURATION

6.1.7 VETERAN FOCUSED INTEGRATION PROCESS (VIP) AND PRODUCT

LINE MANAGEMENT (PLM)

6.1.8 PROCESS ASSET LIBRARY (PAL)

6.1.9 AUTHORITATIVE DATA SOURCES

6.1.10 SOCIAL SECURITY NUMBER (SSN) REDUCTION

6.1.11 GENERATIVE ARTIFICIAL INTELLIGENCE REQUIREMENTS

6.1.11.1 AI SYSTEM/LLM DEVELOPMENT AND OPERATION

DOCUMENTATION REQUIREMENTS

6.1.11.2 MONITORING, REPORTING, AND CORRECTIVE ACTION

6.1.11.3 AI MODEL UPDATES AND CHANGE DISCLOSURES

6.2 SECURITY AND PRIVACY REQUIREMENTS

6.2.1 POSITION/TASK RISK DESIGNATION LEVEL(S)

6.2.2 CONTRACTOR PERSONNEL SECURITY REQUIREMENTS

6.3 METHOD AND DISTRIBUTION OF DELIVERABLES

6.4 PERFORMANCE METRICS

6.5 FACILITY/RESOURCE PROVISIONS

6.6 GOVERNMENT FURNISHED PROPERTY

ADDENDUM A – ADDITIONAL VA REQUIREMENTS, CONSOLIDATED

ADDENDUM B – VA INFORMATION AND INFORMATION SYSTEM SECURITY/

PRIVACY LANGUAGE

ADDENDUM C - VA OWNED HARDWARE/SOFTWARE

1.0 BACKGROUND

The mission of the Department of Veterans Affairs (VA), Office of Information and Technology (OIT), Information Technology Operations and Services (ITOPS), Infrastructure Operations (IO), 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’ health care in an effective, timely and compassionate manner. VA depends on Information Management/Information Technology (IM/IT) systems to meet mission goals.

ITOPS delivers enterprise-wide IT infrastructure engineering and operations services effectively, efficiently and securely to enhance customer experience and enable VA to optimize service delivery to Veterans.

1.1 Institute for Learning, Education and Development (ILEAD)

The Institute for Learning, Education and Development (ILEAD) partners with VA, Veterans Health Administration’s (VHA) program offices, Veterans Integrated Service Networks and medical facilities to provide quality workforce education and training products to improve outcomes in Veteran clinical care, health care operations and administration. This mission directly supports the Assistant Deputy Undersecretary for Health for Workforce Services’ Human Capital Lifecycle Model strategic initiative. From an employee’s first day with VA and across the life cycle of their careers with VA, employees benefit from ILEAD-developed learning programs, products and distribution technologies that advance their careers and enhance the quality of care provided to our nation’s Veterans. ILEAD’s impact on VA’s workforce through training and product development is designed to:

• Onboard and orient staff to VA

• Learn the most effective means to care for the Veteran patient population

• Maintain licenses and certifications through high-quality accredited content

• Acquire skills to close the knowledge and skills gap

• Empower employees and others to be transformation change-agents

• Develop supervisory and leadership abilities to lead VA into the future

The ILEAD Broadcast and Video division is the backbone of ILEAD’s content development and distribution technologies. ILEAD’s Broadcast and Video production equipment and broadcast systems are primarily integrated/housed in Building 56 on the Jefferson Barrack’s VA Medical Center campus. The facility includes a studio sound stage, a video production control room, a live satellite uplink control room, video equipment core and 6 video editing suites. A smaller post-production facility in the Wallace F. Bennet building in downtown Salt Lake City, UT receives virtual support under this Performance Work Statement (PWS). ILEAD Broadcast and Video staff, comprised of Executive Video Producers, Video Editors, AV Production Specialists and Video Engineers work as a team to develop 100’s of VA training products annually. The

ILEAD Broadcast and Video Engineering staff are responsible and facilitate hosting and live streaming thousands of hours of content to VA staff year in and year out. Many of ILEAD’s training delivery systems and supporting technology resides both on and off the VA network. ILEAD Broadcast and Video Engineers work with OI&T staff and their representatives on a daily basis to coordinate with OI&T on activities that may impact broadcast and post-production operations. OI&T and OI&T contractors are a critical component to support ILEAD’s mission to deliver VA learning products and VA leadership outreach messaging to staff and Veterans; anywhere, anytime to any device.

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”

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 https://www.va.gov/vapubs/index.cfm https://www.va.gov/vapubs/index.cfm http://www.va.gov/vapubs http://www.va.gov/vapubs

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, https://digital.va.gov/process-asset-library/ https://www.va.gov/trm/TRMHomePage.aspx

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 https://www.idmanagement.gov/arch/#:~:text=FICAM%20is%20the%20federal%20government%E2%80%99s%20enterprise%20approach%20to,identity%20processes%2C%20practices%2C%20policies%2C%20and%20information%20security%20disciplines.

https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514 https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514 https://www.voa.va.gov/DocumentView.aspx?DocumentID=4896 https://www.cisa.gov/publication/tic-30-core-guidance-documents

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,

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,

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,

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

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 https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28 https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371 https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28 https://www.voa.va.gov/DocumentView.aspx?DocumentID=4946 https://bidenwhitehouse.archives.gov/briefing-room/presidential-actions/2025/01/16/executive-order-on-strengthening-and-promoting-innovation-in-the-nations-cybersecurity/ https://bidenwhitehouse.archives.gov/briefing-room/presidential-actions/2025/01/16/executive-order-on-strengthening-and-promoting-innovation-in-the-nations-cybersecurity/ https://bidenwhitehouse.archives.gov/briefing-room/presidential-actions/2025/01/16/executive-order-on-strengthening-and-promoting-innovation-in-the-nations-cybersecurity/ https://www.whitehouse.gov/wp-content/uploads/2022/01/M-22-09.pdf https://www.cisa.gov/news-events/directives/bod-19-02-vulnerability-remediation-requirements-internet-accessible-systems https://www.cisa.gov/news-events/directives/bod-19-02-vulnerability-remediation-requirements-internet-accessible-systems https://www.cisa.gov/news-events/directives/bod-19-02-vulnerability-remediation-requirements-internet-accessible-systems https://www.cisa.gov/news-events/directives/bod-22-01-reducing-significant-risk-known-exploited-vulnerabilities https://www.cisa.gov/news-events/directives/bod-22-01-reducing-significant-risk-known-exploited-vulnerabilities

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

83. Attachment A - Avid Networking Port Usage Guide, February 27, 2026

Please be advised that any hyperlinks contained within this document, if any, are for convenience purposes, only. Due to the dynamic nature of hyperlinks and the information accessed through or imbedded therein, it is incumbent upon the Contractor to ensure that all information required to successfully complete the requirements established herein is independently located, verified for accuracy, and confirmed to be the most up-to-date version available, prior to use.

3.0 SCOPE OF WORK

The Contractor shall provide on-premise and remote support services to include Network Administration and Network Infrastructure support, Core Infrastructure support, System Administration, Inventory Control, and System’s Database support. The support services shall include VA networked and non-networked systems. The support may require collaboration with local OIT support staff, Institute for Learning, Education and Development (ILEAD) Broadcast and Video Engineering team, and other OIT national program support offices.

3.1 ORDER TYPE

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

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 Periods. The overall PoP shall not exceed 60 months.

https://www.cisa.gov/news-events/directives/bod-23-01-improving-asset-visibility-and-vulnerability-detection-federal-networks https://www.cisa.gov/news-events/directives/bod-23-01-improving-asset-visibility-and-vulnerability-detection-federal-networks https://www.voa.va.gov/DocumentView.aspx?DocumentID=5010 https://www.whitehouse.gov/wp-content/uploads/2025/02/M-25-21-Accelerating-Federal-Use-of-AI-through-Innovation-Governance-and-Public-Trust.pdf https://www.whitehouse.gov/wp-content/uploads/2025/02/M-25-22-Driving-Efficient-Acquisition-of-Artificial-Intelligence-in-Government.pdf https://www.whitehouse.gov/wp-content/uploads/2025/12/M-26-04-Increasing-Public-Trust-in-Artificial-Intelligence-Through-Unbiased-AI-Principles-1.pdf?_bhlid=c0113a16495d987bc33f63e3dccf35c28d6bfd15

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:

New Year's Day January 1 Juneteenth June 19 Independence Day July 4 Veterans Day November 11 Christmas Day December 25

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:

Martin Luther King's Birthday Third Monday in January Washington's Birthday Third Monday in February Memorial Day Last Monday in May Labor Day First Monday in September Columbus Day Second Monday in October Thanksgiving Fourth Thursday in November

4.2 PLACE OF PERFORMANCE

Tasks under this PWS shall be performed in VA facilities located in St. Louis VA Medical Center (VAMC) Campus at 1 Jefferson Barracks Drive, St. Louis, MO 63125 as well as virtually support the Wallace F. Bennet building at 125 S State St, Salt Lake City, UT 84138. Work may be performed at remote locations with prior written concurrence from the Contracting Officer’s Representative (COR).

Normal business hours are 7:00am – 5:00pm Central Time, Monday thru Friday, except on federally observed holidays. Occasional emergency weekend support may be required for, e.g. updates, patches, etc., and flexi hours are available when required by

VA.

4.3 TRAVEL

The Government does not anticipate any travel in the performance of this contract.

5.0 SPECIFIC TASKS AND DELIVERABLES

The Contractor shall perform the following tasks in the Base Period and, if exercised, each Option Period.

5.1 PROJECT MANAGEMENT

5.1.1 TECHNICAL KICKOFF MEETING

A technical kickoff meeting shall be held within five (5) 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 Program Manager (PM), as the Co-Chairperson, the Contract Specialist (CS), and the COR. The Contractor shall provide a draft agenda to the CO and VA PMs at least three (3) calendar 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 the “Institute for Learning, Education and Development (ILEAD) and Information Technology Services Support”. 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 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) calendar 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.

5.1.2 CONTRACTOR PROJECT MANAGEMENT PLAN

The Contractor 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 PM approved CPMP throughout the PoP.

Deliverable:

A. Contractor Project Management Plan

5.1.3 WEEKLY REPORTING REQUIREMENTS

The Contractor shall provide the COR and VA PMs with Weekly Progress Reports in electronic form in Microsoft (MS) Word format. The report shall include detailed instructions/explanations for each required data element to ensure that data is accurate and consistent. 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 month and work planned for the subsequent reporting period. The report shall also identify any problems that arose and a description of how the problems were resolved. If problems have not been completely resolved, the Contractor shall provide an explanation, status, and expected resolution date. 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. In addition, the Weekly Progress Report shall specifically include information regarding:

A. Active Issues B. Recent Accomplishments C. Key Activities D. Events or Outages

In addition, the Contractor shall keep in communication with VA and convene ad-hoc conference call’s with ILEAD Support Team at their request to discuss integration status and pending operational issues to prevent escalation of outstanding issues.

A. Weekly Progress Report

5.1.4 PRIVACY TRAINING

The Contractor shall submit status reporting of VA Privacy and Information Security Awareness training for all individuals engaged on the task order. The status reporting shall identify: a single Contractor Security Point of Contact (POC), the names of all personnel engaged on the task order, their initial training date for VA Privacy and Information Security training, and their next required training date. This status reporting shall be submitted as part of the Weekly Progress Report.

The Contractor shall submit VA Privacy and Information Security training certificates in accordance with Section 9, Training, from Appendix C of the VA Handbook 6500.6, “Contract Security” and Contractor Signed Rules of Behavior for all Contractor staff within one week after award and one week after on-boarding of a new employee.

Contractor shall perform this training and submit certificates annually as required throughout the period of performance for all Contractor employees.

A. VA Privacy and Information Security Training Certificates for all Contractor staff

B. Contractor Signed Rules of Behavior

5.2 ILEAD NETWORK INFRASTRUCTURE SUPPORT

The Jefferson Barracks VA Medical Center campus in St. Louis, Missouri, Building 56, serves as the location for ILEAD’s data core, video streaming systems, and air-gapped satellite delivery infrastructure. The ILEAD network is a purpose‑built, segregated broadcast and video‑production environment comprised of dedicated servers, network switching equipment, media production systems, storage arrays, uplink and downlink components, and associated telecommunications circuits. This network is maintained independently from the VA enterprise IT environment due to the operational incompatibility of its specialized broadcast systems with VA‑mandated security‑hardened configurations, thereby requiring an isolated architecture to ensure continuous and compliant mission support. Reference Addendum C for the detailed Visio network diagram.

The Contractor shall work with the ILEAD’s video engineering staff and provide external networking and admin support for ILEAD’s air-gapped, private broadcast video network consisting of 23 virtual machines supporting AVID, Quantum and Internet Service Provider (ISP), and 3 CISCO switches, identified in Addendum C, 1 and 2. The Contractor shall perform tasks as assigned to include:

1. Mange the demarcation (demarc) site connectivity to the VA backbone.

2. Support 3 USC-C220-M5SX CISCO ESXi hosts.

Provide network support for the enterprise Keyboard, Video, Mouse (KVM) system to include trouble shooting and restoration of workstation/s operations which includes 15 receivers and 38 transmitters.

3. Manage Sensophone Network Infrastructure.

4. Coordinate proper disposal/turn-in of ILEAD equipment as required.

5. Maintain appropriate physical security controls, Uninterruptable Power Supply

(UPS) protection, emergency power and environmental controls for WAN equipment installed at the facilities.

6. Add/Remove/Move networking equipment as necessary.

7. Test physical and IP connectivity.

The Contractor shall update the VA IT COR-approved network diagram.

A. VA IT COR-approved network diagram.

5.3 SYSTEMS ADMINISTRATION

Reference Addendum C for the detailed Visio network diagram for a detailed list of server configurations and IP addresses. The Contractor shall perform systems administration to include:

1. Serve as a liaison between VA OIT and ILEAD broadcast engineering staff on technical issues.

2. Analyze system logs and identify potential issues with ILEAD systems.

3. Recommend and integrate VA approved new technologies into existing ILEAD systems and environments.

4. Perform monthly audit of ILEAD systems and software.

5. Apply monthly OS updates, patches, and configuration changes.

6. Install and configure new hardware and software when required on ILEAD equipment.

7. Assist with account management to ILEAD systems by adding, removing, updating or resetting passwords of user accounts not managed by OIT.

8. Manage group policy systems access for authorized eToken users

9. Answer virtual technical queries from VA IT staff and provide assistance when required.

10. Maintain security of ILEAD hardware, software, and data file access.

11. Maintain SanDisk SSD Assignments.

12. Maintain Video Production Workstation and Laptop inventory and assignments.

13. Support patching of designated playout channels 1 and 2 ingest for BitCentral and remote access scheduling.

14. Update and follow VA Standard Operating Procedures (SOP) to build out approved ILEAD equipment.

15. Troubleshoot and resolve reported problems.

16. Provide ILEAD system performance tuning.

17. Configure, add, and delete ILEAD file systems.

18. Decommission ILEAD as required.

19. Restart the system after crashes and power spikes.

20. Update and maintain the Rack Elevation Drawings.

21. Update the ILEAD Facility Layout Document maintaining a narrative description of the overall design of the server farms.

22. Update and maintain the listing of all ILEAD File Servers including server name, location, functionality, and IP addresses.

Deliverables:

A. Standard Operating Procedures (SOP) for ILEAD equipment.

B. Rack Elevation Drawings C. Facility Layout Document D. Listing of All ILEAD File Servers

5.4 OFFICE OF INFORMATION AND TECHNOLOGY VIRTUAL MACHINE

(OI&T VM) SERVERS

Reference Addendum C for the OI&T VM design document. The final component of the ITOPS IO – ILEAD Server Farm is an OI&T VM virtual server platform. The OI&T VM platform includes Cisco Unified Computing System (UCS) servers, Cisco network infrastructure, Cisco Fabric Interconnects, and NetApp Fabric Attached Storage (FAS) storage arrays.

The Contractor shall provide virtual server administration to include updating the following documents:

1. ITOPS IO-ILEAD OI&T VM Server Farm Design and Topology Document

2. SOP for VA Compliant Server Build

3. SOP for Microsoft 2016/2019 R2 and non-Windows to include Redhat and

CentOS Server Builds

Deliverables:

A. ITOPS IO-ILEAD OI&T VM Server Farm Design and Topology Document B. SOP for VA Compliant Server Build C. SOP for Microsoft 2016/2019 R2 and non-Windows to include Redhat and

CentOS Server Builds

5.5 APPLICATIONS DATABASE SUPPORT

The Contractor shall provide database administration for existing ITOPS IO databases including maintaining the code of in-house developed ITOPS IO web applications as it pertains to accessing those databases. VA ITOPS IO staff will provide the database/system access that the Contractor requires to accomplish these tasks and will also serve as liaison with the business owner if needed. These databases/applications shall include:

1. Media Asset Management (MAM)

The Contractor shall:

1. Keep databases up to date.

2. Design and develop new databases based on the specifications.

3. Manage database access.

4. Design maintenance procedures and put them into operation.

5. Liaise with programmers, applications/operational staff, IT project managers and other technical staff.

6. Manage database security/integrity and backup procedures.

7. Implement security measures as approved by VA.

8. Define objectives through consultation with staff at all levels.

9. Test and modify databases to ensure that they operate.

10. Archive incremental data nightly with a full back up weekly.

11. Manage customizable database functions related to ILEAD application installs, security updates, and firmware upgrades.

12. Maintain ILEAD database interfaces with customers COTS and in-house applications.

13. Monitor and troubleshoot database errors related to ILEAD applications.

14. Develop vendor interfaces based on the specifications provided by VA ILEAD

IT staff.

15. Perform data extraction, transformation and loading (ETL) operations.

16. Performance monitoring and tuning.

17. Troubleshoot and fix performance issues

18. Perform capacity planning and monitor database growth.

19. Support data migration and workflows for ILEAD applications for COTS and in-house applications.

The Contractor shall provide current status in the Weekly Progress Report (PWS 5.1.3) stating whether all databases are fully operational and meet VA OI&T compliance standards and actions to resolve any issues that exist.

5.6 BUSINESS SYSTEMS ANALYSIS

The Contractor shall provide business systems analysis support for all ILEAD networks, projects, applications, and initiatives. The Contractor shall:

1. Prepare ad hoc system usage reports approximately monthly as requested by ILEAD management and include in the Weekly Progress Report.

2. Prepare ad hoc technical reports approximately monthly as requested by ILEAD management by collecting, analyzing, and summarizing information and trends and include in the Weekly Progress Report.

3. Coordinate with the business systems owners to provide input to necessary to the POA&Ms, 508, SOPs, DR, and other documents as required.

5.7 CORE BUSINESS SYSTEMS INFRASTRUCTURE SUPPORT SERVICES

The Contractor shall maintain core business infrastructure architectures that take all factors of networks into consideration such as VA IT compliance, functional requirements, technical considerations, business processes and end users. The Contractor shall:

1. Interface with the system business owners(s) and sponsor(s) and all other stakeholders in order to determine high level requirements.

2. Ensure that this set of high level requirements are operationally defined.

3. Ensure that all core infrastructure services and products operational readiness is maintained.

4. Provide and maintain the ILEAD IO Business Systems Design and Topology

Document.

https://en.wikipedia.org/wiki/User_(computing) https://en.wikipedia.org/wiki/Sponsor_(commercial) https://en.wikipedia.org/wiki/Stakeholder_(corporate) https://en.wikipedia.org/wiki/Operational_definition

A. ILEAD IO Business Systems Design and Topology Document

5.7.1 ILEAD BROADCAST AND VIDEO DEVICE ARCHITECTURE

The Contractor shall support the ILEAD Broadcast and Video Device Architecture major system(s) as required in the following paragraphs.

5.7.1.1 AVID EDITING ENVIRONMENT

The Avid non-linear edit environment systems are used to ingest and edit video assets stored on solid state drives, networked and cloud based storage arrays. Digitally manipulating large HD and 4K video files requires advanced, high speed computing systems and high speed 10Gbps networks. The Avid environment includes high end work stations, fiber connected network switches, virtual application servers, digital video playout servers, on premise storage arrays, and video project parking application (Marquis) that interfaces with an LTO-8 tape archive system.

The Contractor shall provide network, server and workstation support for the AVID editing environment systems to include workstation, storage and network support.

5.7.1.2 AVOCENT HMX DIGITAL HIGH PERFORMANCE KVM ENVIRONMENT

The Avocent HMX Digital High Performance KVM Environment system is designed for organizations that need to provide workers the ability to seamlessly access and share one or more computing resource(s) which are physically separated from their work station. The current environment consists of 15 receivers and 38 transmitters; the system is expandable to 50 receivers and 50 transmitters.

The Contractor shall provide network support for the enterprise KVM system to include trouble shooting and restoration of workstation/s operations.

5.7.1.3 BIT CENTRAL ON AIR AUTOMATION SYSTEM

The Bit Central On Air Automation system comprised of an ingest, playout and database server is used to ingest content and play that content out to both VA Knowledge Network program channels; VA1 and the Veteran News Network (VNN).

The automation system interfaces with a broadcast traffic system to download program playlists to air video content 24/7/365. The automation system is also comprised on an archive system that purges expired content and or archives the same content to an LTO-8 tape system for future retrieval.

The Contractor shall provide network support for the Bit Central playback automation system to include trouble shooting and restoration of ingest server, playback server and associated database.

5.7.1.4 ON AIR BROADCAST TRAFFIC SCHEDULING SYSTEM

The On Air Broadcast Traffic Scheduling System is comprised of a Linux RedHat 7 application server and connected clients. The system is used to track and schedule VA Knowledge Network content to air by sending channel playlists to the broadcast automation platform.

The Contractor shall provide network support, critical RH7 updates and interface with the manufacturer and system business owner to address client server issues when necessary.

5.7.1.5 MEDIA ASSET MANAGEMENT (MAM) SYSTEM

The MAM (Media Asset Management) is a platform used to store, retrieve and archive ILEAD’s file-based media assets. The MAM solution focuses on active management of content and media assets using metadata to tag media assets. The MAM platform interfaces between proprietary video editing devices, source/destination record/playback devices and IT centric storage technology. The MAM is fully integrated with the broadcast automation system, broadcast traffic system, production and post-production resources. MAM systems are server-based software applications serving in a “middleware role” between the media network devices and storage networks. Storage networks include online, near line and far line archive storage tiers. The most basic functions of MAM is the automated retrieval of high-resolution digital content and the archiving of digital masters. Assets tagging in a MAM platform ensures media delivery from either a user workstation, playout or editing device. The MAM system is used to facilitate media file searches and other file based workflows; editing, file deletion, video file transfers, file transcoding, video file rewrapping for delivery to media distribution systems. The MAM can also facilitate offsite file disaster recovery, file transcode and file analysis workflows.

The Contractor shall provide network and server support for the Media Asset Management systems, associated database, on premise storage arrays and an LTO-8 tape archive system.

The Contractor shall Interface with ILEAD Broadcast and Video engineering staff to ensure the MAM is fully functional and meeting the needs of media staff. The Contractor provide a MAM Network Design and Topology Document that includes:

1. A narrative description of the overall design of the MAM network.

2. A high-level ILEAD MAM network design and topology drawing which identifies the MAM installation and connectivity.

MAM Network Design and Topology Document

6.0 GENERAL REQUIREMENTS

6.1 ENTERPRISE AND IT FRAMEWORK

6.1.1 VA TECHNICAL REFERENCE MODEL

The Contractor shall comply with the VA OIT Technical Reference Model (VA TRM).

Compliance with the VA TRM is achieved by using only technologies and standards that are listed as approved for use in the VA TRM. The Contractor shall provide all necessary information requested by VA to ensure TRM approval is obtained prior to use on VA’s network.

6.1.2 ZERO TRUST – VA CRITICAL SECURITY CONTROLS

VA has established minimum mandatory security requirements and requires that any network connected software system or service must meet the VA Critical Security Controls as outlined in the VA Memorandum, “VA Security Controls”, https://www.voa.va.gov/DocumentView.aspx?DocumentID=5010. VA Critical Security Controls identify the minimum mandatory requirements that must be implemented across all VA enterprise infrastructure, cloud computing environments, information systems, networks, and specialized devices (medical devices/systems, special-purpose systems, and research scientific computing devices) that process, store, and/or transmit VA data. Effective July 1, 2025, the Contractor shall implement these VA Critical Security Controls, within any network connected software system or service prior to being authorized for use in the VA. This functional requirement is not negotiable, and Plan of Action & Milestones (POAM) will not be accepted in the event these controls cannot be implemented for new systems. Critical Security Controls are intended to increase VA’s security posture and provide security and privacy risk visibility into the VA network and is not a new requirement. The Contractor’s failure to maintain these VA Critical Controls after implementation will result in VA discontinuing the use of the system.

6.1.3 FEDERAL IDENTITY, CREDENTIAL, AND ACCESS MANAGEMENT

(FICAM)

The Contractor shall ensure Commercial Off-The-Shelf (COTS) product(s), software configuration and customization, and/or new software are Personal Identity Verification (PIV) card-enabled by accepting HSPD-12 PIV credentials using VA Enterprise Architecture (EA), and VA Identity and Access Management (IAM) approved Enterprise Technology Guidelines (ETG). The Contractor shall ensure all Contractor delivered applications and systems comply with the VA Identity, Credential, and Access Management policies and guidelines set forth in Executive Order 14028, VA Handbook 6510 VA Identity and Access Management, VA Handbook 0735 Homeland Security Presidential Directive 12 (HSPD-12) Program, CISA Binding Operational Directive 23-https://www.voa.va.gov/DocumentView.aspx?DocumentID=5010 https://www.ea.oit.va.gov/ https://www.ea.oit.va.gov/ https://digital.va.gov/office-of-information-and-technology/reference-library/enterprise-technology-guidelines/ https://digital.va.gov/office-of-information-and-technology/reference-library/enterprise-technology-guidelines/

01, and align with the Federal Identity, Credential, and Access Management Roadmap and Implementation Guidance v2.0.

The Contractor shall ensure all Contractor delivered applications and systems provide user authentication services compliant with the National Institute of Standards and Technology (NIST) Special Publication (SP) 800-63-4, VA Handbook 6500, and VA IAM enterprise requirements for direct, assertion based authentication, and/or trust based authentication, as determined by the ETGs. Direct authentication at a minimum must include Public Key Infrastructure (PKI) based authentication supportive of PIV card and/or Common Access Card (CAC), as determined by the business need.

The Contractor shall ensure all Contractor delivered applications and systems conform to the specific Identity and Access Management PIV requirements set forth in the Office of Management and Budget (OMB) Memoranda M-05-24, M-19-17, M-22-09, and NIST Federal Information Processing Standard (FIPS) 201-3. Contractor delivered applications and systems shall be on the FIPS 201 Approved Product List (APL). If the Contractor delivered application and system is not on the APL, the Contractor shall be responsible for taking the application and system through the FIPS 201 Evaluation Program.

The Contractor shall ensure all Contractor delivered applications and systems support:

1. Automated provisioning and are able to use enterprise provisioning service.

2. Interfacing with VA’s Master Person Index (MPI) to provision identity attributes, if the solution relies on VA user identities. MPI is the authoritative source for VA user identity data.

3. The VA defined unique identity (Secure Identifier [SEC ID] / Integrated Control Number [ICN]).

4. Multiple authenticators for a given identity and authenticators at every Authenticator Assurance Level (AAL) appropriate for the solution.

5. Identity proofing for each Identity Assurance Level (IAL) appropriate for the solution.

6. Federation for each Federation Assurance Level (FAL) appropriate for the solution, if applicable.

7. Two-factor authentication (2FA) through an applicable Technology Guideline as outlined in VA ETG.

8. A Security Assertion Markup Language (SAML) implementation if the solution relies on assertion-based authentication. Additional assertion implementations, besides the required SAML assertion, may be provided as long as they are compliant with NIST SP 800-63-4 guidelines.

9. Authentication/account binding based on trusted Hypertext Transfer Protocol (HTTP) headers if the solution relies on Trust based authentication.

10. Role Based Access Control.

11. Auditing and reporting capabilities.

12. Compliance with VIEWS 00155984, PIV Logical Access Policy Clarification https://www.voa.va.gov/DocumentView.aspx?DocumentID=4896.

https://bidenwhitehouse.archives.gov/wp-content/uploads/legacy_drupal_files/omb/memoranda/2005/m05-24.pdf https://bidenwhitehouse.archives.gov/wp-content/uploads/2019/05/M-19-17.pdf https://bidenwhitehouse.archives.gov/wp-content/uploads/2022/01/M-22-09.pdf https://www.voa.va.gov/DocumentView.aspx?DocumentID=4896

The required Assurance Levels for this specific effort are Identity Assurance Level 3, Authenticator Assurance Level 3, and Federation Assurance Level 3.

6.1.4 INTERNET PROTOCOL VERSION 6 (IPv6)

The Contractor solution shall support IPv6-Only based upon the memo issued by the Office of Management and Budget (OMB) on November 19, 2020 (https://www.whitehouse.gov/wp-content/uploads/2020/11/M-21-07.pdf). Which defines IPv6-only as the state of an operational system or service when IPv4 protocol functions (addressing, packet forwarding) are not in use. The NIST USGv6 profile defines technical requirements for a product to be capable of operating in IPv6-Only environments. IPv6-Only technology, in accordance with the USGv6 Program (https://www.nist.gov/programs-projects/usgv6-program/usgv6-revision-1), NIST Special Publication (SP) 500-267B Revision 1 “USGv6 Profile” (https://doi.org/10.6028/NIST.SP.500-267Br1), and NIST SP 800-119 “Guidelines for the Secure Deployment of IPv6” (https://doi.org/10.6028/NIST.SP.800-119), compliance shall be included in all IT infrastructures, application designs, application development, operational systems and sub-systems, and their integration. In addition to the above requirements, all devices, applications, and systems shall support all applicable functionality on native IPv6-Only as well as dual stack (IPv6 / IPv4) connectivity without additional memory or other resources being provided by the Government, so that they can function in a mixed environment. All public/external facing servers and services (e.g., web, email, DNS, ISP services, etc.) shall support native IPv6-Only and dual stack (IPv6 / IPv4) users and all internal infrastructure and applications shall support using native IPv6-Only and dual stack (IPv6 / IPv4) for all functionality and operations.

6.1.5 TRUSTED INTERNET CONNECTION (TIC)

The Contractor solution shall meet the requirements outlined in Office of Management and Budget Memorandum M-19-26, “Update to the Trusted Internet Connections (TIC) Initiative“ (https://www.whitehouse.gov/wp-content/uploads/2019/09/M-19-26.pdf), VA Directive 6513 “Secure External Connections”, and shall comply with the TIC 3.0 Core Guidance Documents, including all Volumes and TIC Use Cases, found…