Request for Information 36C10B26Q0376 SCM DSO DRAFT PWS.pdf

PERFORMANCE WORK STATEMENT (PWS)

DEPARTMENT OF VETERANS AFFAIRS

Office of Information & Technology (OIT) Digital Service Delivery (DSD)

Health Services Portfolio Healthcare Environment and Logistics Management (HELM)

Supply Chain Management Development Security Operations (SCMDSO) Integration

Date: April 21, 2026

VA-26-00021946

PWS Version Number: 1.0

Supply Chain Development Security Operations (SCDSO) Integration

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

4.4 LABOR CATEGORY SKILLSET AND CERTIFICATION

5.0 SPECIFIC TASKS AND DELIVERABLES

5.1 PROJECT MANAGEMENT (FFP)

5.1.1 CONTRACTOR PROJECT MANAGEMENT PLAN

5.1.2 REPORTING REQUIREMENTS

5.1.3 PROGRESS REPORTS

5.1.4 TECHNICAL KICKOFF MEEETING

5.1.5 VA MANDATORY TRAINING

5.1.6 ONBOARDING / OFFBOARDING

5.1.6.1 ONBOARDING ACTIVITIES

5.1.6.2 OFFBOARDING ACTIVITIES

5.2 HELM PRODUCT LINE MANAGEMENT SUPPORT (FFP)

5.2.1 HELM PRODUCT LINE SUPPORT

5.2.2 INTAKE PROCESS

5.2.3 PROGRAM INCREMENT PLANNING

5.2.4 INNOVATION TREND ANALYSIS AND PLANNING

5.3 SCRUM TEAM SUPPORT (OPTIONAL TASK 1) (FFP)

5.3.1 MICRO SCRUM TEAM

5.3.2 SMALL SCRUM TEAM

5.3.3 MEDIUM SCRUM TEAM

5.3.4 LARGE SCRUM TEAM

5.4 HIGHLY TECHNICAL SCRUM TEAM support (Optional task 2) (ffp)

5.4.1 MICRO HIGHLY TECHNICAL SCRUM TEAM (OPTIONAL TASK) (FFP) 24

5.4.2 SMALL HIGHLY TECHNICAL SCRUM TEAM

5.4.3 MEDIUM HIGHLY TECHNICAL SCRUM TEAM

5.4.4 LARGE HIGHLY TECHNICAL SCRUM TEAM

5.5 SUPPLY CHAIN PRODUCT SUPPORT (teamS) (optional HELM PL

PRODUCT/PROJECT)

5.5.1 SOFTWARE DEVELOPMENT LIFECYCLE (SDLC) ACTIVITIES

5.5.2 CONFIGURATION MANAGEMENT

5.5.3 RISK & ISSUE MANAGEMENT

5.5.4 SCHEDULE MANAGEMENT

5.5.5 USER EXPERIENCE MANAGEMENT

5.5.6 USER RESEARCH

5.5.7 AGILE REQUIREMENTS ELABORATION

5.5.8 CONTENT DESIGN

5.5.9 PRODUCT TESTING

5.5.9.1 INTEGRATED TESTING ACTIVITIES

5.5.9.2 TEST PLANNING AND DOCUMENTATION

5.5.9.3 DEFECT MANAGEMENT

5.5.9.4 REPORTING

5.5.9.5 RELEASE READINESS CRITERIA

5.5.10 PRODUCT ARCHITECTURE

5.5.11 DATA MANAGEMENT AND MIGRATION SUPPORT

5.5.11.1 DATA TOOLS DEVELOPMENT AND TESTING SUPPORT

5.5.11.2 DATA EXTRACTION AND ANALYTICS

5.5.11.3 DATA MAPPING AND VALIDATION

5.5.11.4 MIGRATION PLANNING, ENVIRONMENT SUPPORT, AND

TESTING 36

5.5.12 TRAINING SUPPORT

5.5.13 AI/ML OPTIMIZATION AND PREDICTIVE ANALYTICS

5.6 RELEASE SUPPORT (optional HELM PL PRODUCT/PROJECT)

5.6.1 PRERELEASE SUPPORT

5.6.2 ASSESSMENT AND AUTHORIZATION (A&A) SUPPORT

5.6.3 INITIAL OPERATING CAPABILITY (IOC) SUPPORT

5.6.4 RELEASE AND DEPLOYMENT SUPPORT

5.7 POST DEPLOYMENT SUPPORT (optional HELM PL PRODUCT/PROJECT)

5.7.1 AFTER BUSINESS HOUR SUPPORT

5.8 VALIP SUSTAINMENT SUPPORT (optional HELM PL PRODUCT/PROJECT)

5.8.1 VALIP CLOUD ECOSYSTEM DEVELOPMENT AND MANAGEMENT

5.8.2 INTEGRATION AND INTEROPERABILITY

5.9 BUILD AND DEVELOPMENT (optional HELM PL PRODUCT/PROJECT)

5.9.1 SOLUTION ARCHITECTURE PLANNING AND EXECUTION

5.9.2 BUILD PLANNING

5.9.3 SPRINT PLANNING

5.9.4 SPRINT EXECUTION

5.10 APPLICATION PERFORMANCE MONITORING AND ALERTING (optional

HELM PL PRODUCT/PROJECT)

5.10.1 APPLICATION PERFORMANCE MONITORING (APM)

5.10.2 APPLICATION MONITORING PLAN (AMP)

5.10.3 DECOMISSIONING SUPPORT

5.10.3.1 ALTERNATE SOLUTIONS FOR DECOMISSIONING SYSTEMS

5.10.3.2 DECOMISSIONING PLAN

5.10.3.3 TECHNICAL SUPPORT FOR DECOMISSIONING

5.11 MIGRATION TO CLOUD ENVIRONMENT & HOSTING SUPPORT (optional

HELM PL PRODUCT/PROJECT)

5.11.1 VAEC CLOUD HOSTING

5.11.2 EXTERNAL HOSTED APPLICATION

5.12 INFRASTRUCTURE AND SECURITY REQUIREMENTS (optional HELM PL

PRODUCT/PROJECT)

5.13 ADDITIONAL IMPLEMENTATION SUPPORT (OPTIONAL TASK 3) (T&M) .. 58

5.13.1 OPTIONAL TASK – HELM SCM DSO SUPPORT SERVICES (T&M)

5.14 TRANSITION SUPPORT (OPTIONAL TASK FOUR)

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.1.12 SOURCE CODE HARMONIZATION AND REUSE IN INFORMATION

TECHNOLOGY (SHARE IT Act)

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

1.0 BACKGROUND

The Department of Veterans Affairs (VA) Office of Information and Technology (OIT) Product Delivery Services (PDS) delivers integrated digital capabilities that support Veteran care nationwide. Within PDS, the Health Services Portfolio’s Healthcare Environment and Logistics Management (HELM) Product Line (PL) implements, modernizes, sustains, standardizes, and streamlines software solutions for supply chain, logistics, expendables, assets, inventory, facilities, prosthetics, and environmental compliance HELM provides the enterprise capabilities needed to support a unified, efficient, and data driven supply chain and logistics environment across VA.

VA does not currently operate with standardized, enterprise-wide supply chain business processes or technical systems. Numerous functional and capability gaps have been identified through Government Accountability Office (GAO) and Office of Inspector General (OIG) audits and internal assessments. VA requires accurate, reliable, and accessible supply chain data to improve ordering, fulfillment, and operational performance. These needs align with VA’s Strategic Supply Chain (SC) Prioritization and Digital Modernization Strategy, which emphasize modernizing legacy systems, strengthening cybersecurity and resilience, improving data quality, enhancing user experience for logisticians, and establishing consistent, interoperable processes across VHA, VACO, VBA, and NCA.

VA currently relies on approximately 63 disparate legacy systems across 174 sites, resulting in fragmented operations, limited enterprise visibility, and inefficiencies.

Standardization and modernization are required to transform Supply Chain systems into integrated, enterprise-wide system of systems that supports responsive, efficient clinical and nonclinical supply operations.

To meet mission needs, VA requires a full service, standardized, scalable healthcare logistics software solutions with modern supply chain management capabilities. A unified digital environment shall enable lifecycle management efficiencies, data driven decision making, and seamless integration with major initiatives such as the Electronic Health Record Modernization (EHRM) and Financial Management Business Transformation (FMBT) programs. HELM’s mission and modernization efforts directly support these enterprise requirements by advancing cloud-based logistics capabilities, modernizing legacy applications, and enabling consistent processes across VA’s supply chain functions. In addition to modernization activities, several HELM products require ongoing Operation & Maintenance (O&M) support, enhancements, operation stability, security and Lifecyle support.

HELM is organized into five subproduct lines (SPL): Environmental and Healthcare Management, Healthcare Technology and Asset Management, Expendable Inventory Management, Prosthetics, and Technical Services. Additional products scheduled such as Enterprise Asset Management Computerized Maintenance Management System (EAM CMMS), Enterprise Expendable Inventory Management (EEIM) to be incorporated into the product line over the course of this contract Period of Performance (PoP), see Attachment 1 - HELM Products. Attachment 1 represents both products that

HELM provides full Software Development Life Cycle (SDLC) support and ownership, and VHA owned products where HELM provides varying levels of support.

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

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,

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,

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

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,

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

56. Executive Order 14148, “Initial Rescissions of Harmful Executive Orders and

Actions,” dated January 20, 2025

57. Office of Information Security (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 https://www.idmanagement.gov/arch/#:%7E: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 https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28 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 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.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-22-01-reducing-significant-risk-known-exploited-vulnerabilities https://www.cisa.gov/news-events/directives/bod-22-01-reducing-significant-risk-known-exploited-vulnerabilities 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.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

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

83. VA Enterprise Cloud Technical Reference Guide, Version 2.0, November 10,

84. Attachment (1) HELM Products

85. Attachment (2) TBD

86. Agile Lifecycle Management Library alm-library.aspx

3.0 SCOPE OF WORK

This scope applies to existing HELM IT products and any new products introduced during the period of performance. The Government shall provide necessary requirements, system access, and stakeholder coordination. All work shall comply with applicable VA security, privacy, and quality standards and shall align with OIT HELM PL’s mission to modernize, secure, streamline, and sustain VA supply chain and logistics capabilities. The Contractor shall provide comprehensive technical, functional, and lifecycle support for existing legacy and future HELM PL products, and new systems incorporated into the product line, in alignment with VA’s enterprise digital modernization, cybersecurity, and supply chain transformation strategies. This support shall enable VA’s strategic objectives to modernize platforms, standardize, enhance interoperability, strengthen cybersecurity posture, improve supply chain visibility, and deliver resilient, and decommission products.

The scope of work includes full SDLC services; O&M; cybersecurity and regulatory compliance; enterprise deployment; incremental enhancements; implementation and integration support; interface development; platform management; training, Cloud Migration and Hosting services consistent with VA Enterprise Cloud (VAEC) standards;

and modernization activities supporting Asset Management, Inventory Management, Prosthetics, and all HELM PL managed solutions.

The Contractor shall apply advanced DevSecOps and engineering capabilities aligned with VA’s Zero Trust Architecture Strategy, VA Digital Modernization Strategy, and supply chain modernization objectives. Required activities include secure software development, Continuous Integration and Continuous Delivery (CI/CD) automation, pipeline optimization, continuous monitoring, security assessment and authorization support, configuration and release management, architecture and interoperability analysis, training, data validation and analytics, supply chain risk assessment, and development of technical roadmaps and recommendations that advance VA’s enterprise modernization goals.

The Contractor shall also provide program management, technical governance, intake and prioritization support, business process analysis, Risk Management Framework activities, Agile delivery management, and required documentation to ensure secure, efficient, and compliant delivery of HELM capabilities. All services shall adhere to VA cybersecurity, privacy, Section 508, and quality standards and shall integrate with VA enterprise platforms and shared services.

https://dvagov.sharepoint.com/sites/oitjiraoptimization/SitePages/alm-library.aspx?isSPOFile=1&xsdata=MDV8MDJ8fGRjNDQ0NzMzOTE4NDRlYzljYzNiMDhkZTliZmIwZjMzfGU5NWYxYjIzYWJhZjQ1ZWU4MjFkYjdhYjI1MWFiM2JmfDB8MHw2MzkxMTk2OTk3MjczMzg1NTV8VW5rbm93bnxWR1ZoYlhOVFpXTjFjbWwwZVZObGNuWnBZMlY4ZXlKRFFTSTZJbFJsWVcxelgwRlVVRk5sY25acFkyVmZVMUJQVEU5R0lpd2lWaUk2SWpBdU1DNHdNREF3SWl3aVVDSTZJbGRwYmpNeUlpd2lRVTRpT2lKUGRHaGxjaUlzSWxkVUlqb3hNWDA9fDF8TDJOb1lYUnpMekU1T2pBelpqazVNV0pqTFdObU5ERXRORGsxWXkxaFlUUm1MVFJrWkRSaU9HWXpPRGcxWmw5aE56UTRNMkUxTXkxbU1HVmtMVFExWXpVdE9URXlNQzFoTmpOaVpUZ3hZek5rWXpWQWRXNXhMbWRpYkM1emNHRmpaWE12YldWemMyRm5aWE12TVRjM05qTTNNekUzTURnd01nPT18Y2Y5YTNmNTdhYjAwNDZmMmNjM2IwOGRlOWJmYjBmMzN8OTQ1ODE5YzhiMDg3NGEwZGEyNzM3ODM2NmM3OWNlMjY%3D&sdata=Zy80eG9uRW0rMnRIQm1pRjB5K3plSmI4dTRxQ004WlA2akNVUmVncStjOD0%3D&ovuser=e95f1b23-abaf-45ee-821d-b7ab251ab3bf%2CAaron.Drew%40va.gov

3.1 ORDER TYPE

The effort shall be proposed as a hybrid Firm-Fixed Price (FFP) Base with Time and Materials (T&M) optional tasks and a Cost Reimbursable Travel Line.

4.0 PERFORMANCE DETAILS

4.1 PERFORMANCE PERIOD

The PoP shall be one 12-month base period with four 12-month option periods and four optional tasks, if exercised. The overall 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). (If required, the CO or Contracting Officer’s Representative (COR) or may direct the Contractor to work during holidays and weekends).

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 at Contractor facilities. The Contractor shall identify the Contractors place of performance in their proposal submission. Work may be performed at remote locations with prior concurrence from the COR and Alternate Contracting Representative (ACOR)

When travel is required, work at the Government site may be required to take place on holidays, or weekends or after business hours and shall be directed by CO or the

COR/ACOR. Travel to a Government facility needed to perform the services doesn’t change the Place of Performance to the Government Site.

4.3 TRAVEL

The Government encourages the Contractor to maximize its use of teleconferencing and video conferencing for meetings.

The Government anticipates travel to perform the tasks associated with the effort, as well as to attend program-related meetings or conferences throughout the PoP.

Travel and per diem shall be in accordance with the Federal Travel Regulations (FTR) and require advanced concurrence by the COR. The Contractor shall provide cost estimates with each travel request. Each Contractor invoice must include copies of all receipts that support the travel costs claimed in the invoice. Local travel within a 50-mile radius from the Contractor’s normal duty location is considered the cost of doing business and shall not be reimbursed. This includes travel, subsistence, and associated labor charges for travel time. Travel performed for personal convenience and daily travel to and from work at the Contractor’s facility shall not be reimbursed. Travel, subsistence, and associated labor charges for travel time for travel beyond a 50-mile radius of the Contractor’s facility are authorized on a case-by-case basis and must be pre-approved by the COR.

The total number of trips in support of this effort for each 12-month PoP is 12 trips, with 2 people traveling for an average of 8 days per trip.

Anticipated travel can be all CONUS VA Facility locations, and are not limited to the following:

1. Washington, DC

2. Austin, TX

3. Denver (DALC)

4. Florida (Orlando, Bay Pines)

4.4 LABOR CATEGORY SKILLSET AND CERTIFICATION

The contractor shall ensure all personnel assigned to support this requirement meet the applicable Labor Category (LCAT) levels, qualifications, and certifications. The Contractor shall provide resources with a blend of specific expertise and experience in Scaled Agile Framework (SAFe) Agile, Product Management, DevSecOps, engineering, and Data Migration. The Contractor shall adhere to industry standards and requirements referenced in Attachment 2 Labor Category Skillset in filling all positions.

The Contractor shall provide cross-functional SAFe resources for the development of enhancements to the HELM products and underlying infrastructure in alignment with VA policies and procedures. The Contractor shall also provide key personnel contractors that are considered/certified Supply Chain Technical Expertise.

5.0 SPECIFIC TASKS AND DELIVERABLES

The Contractor shall perform the following tasks and provide the specific deliverables described below for each product/project initiated within the performance period stated in this PWS.

The Contractor and/or its subcontractors shall be required, as part of performance under this Task Order, to work with other Government Contractors. In performance of this TO the Contractor shall provide full cooperation with all contractors working for and on behalf of the VA. The Contractor is not authorized to provide guidance, direction, and /or approval of any Contractor’s work activities, work products, or deliverables; VA shall provide all directions and/or approval.

Upon award, the COR shall establish initial contact between the Contractor and other Contractors. All interested parties shall participate as applicable. Nondisclosure forms between VA and Contractors shall be executed as appropriate.

The Contractor shall utilize the Agile framework for product management to deliver iteratively & incrementally which regularly produces high quality results in a cost effective, timely, and highly collaborative.

The contractor shall utilize VA Technical Reference Model (TRM) compliant tools in performance of Agile Product Management, test results, scenarios, and results for each product.

The Contractor shall adhere to VA policies by ensuring compliance with DevSecOps practices, implementing Agile methodologies, and supporting other OIT strategic initiatives. To achieve this, the Contractor shall provide a team of subject matter experts (SMEs) to facilitate integration and oversight of capabilities at both the product line and product/solution levels, working collaboratively with stakeholders and partners.

VA shall follow an intake process outlined in PWS Section 5.2.2 when new products/applications/systems require support services from the contract.

5.1 PROJECT MANAGEMENT (FFP)

5.1.1 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 the contract. 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 Product Manager (PM)/COR/ACOR approved CPMP throughout the PoP. The Contractor shall provide contractor functional organization chart to ensure contractor leads along with SMEs are clearly delineated.

Deliverable:

A. Contractor Project Management Plan

5.1.2 REPORTING REQUIREMENTS

The Contractor shall use the VA’s implementation of the Jira, GitHub or other VA approved toolset to provide a single Agile project/product lifecycle management tool to track execution details. The VA approved toolset Project/Product Data and Artifact Repository shall be used to provide a single authoritative project and product data and artifact repository. All OIT HELM project data and artifacts shall be required to be managed in this data and artifact repository daily. All checked out artifacts shall be checked back in daily and any data updated daily. VA approved toolset synchronizes all changed information immediately for all team members to access work proficiently without the concern of working on aged information.

The Contractor shall utilize the VA approved toolset to:

a. Input and manage scheduled project/product sprints and backlog

b. Input and manage project/product Agile requirements

c. Input and manage project/product risks and issues

d. Input and manage project/product configurations and changes

e. Input and manage project/product test plans and execution

f. Input and manage project/product planning and engineering documentation

g. Input and manage project/product user guides and training materials

h. Input and manage linkages to correlate requirements to change orders to configurable items to risks, impediments, and issues to test cases and test results to show full traceability.

i. Input and manage linkages to correlate requirements to change orders to configurable items to risks, impediments, and issues to test cases and test results to show full traceability.

j. Input and manage Enterprise-wide implementation

k. Input and manage integration with interfaces

The Contractor shall show all Agile requirements, changes, tests performed and test results in the VA approved toolset to show evidence of code coverage and test coverage of all the requirements specified. This expectation shall allow VA to have high confidence in a fully documented, requirements traceability matrix, as evidenced by data in the tools. The Contractor shall track for each product. The Contractor shall support the VA COR in the creation and management of a SharePoint based deliverable library and associated approval workflow. The Contractor shall provide Monthly Deliverable Schedule and Consolidated Performance Report. Format and details will be coordinated with COR and Contractor.

Deliverables:

A. Monthly Deliverable Schedule B. Consolidated Performance Report

5.1.3 PROGRESS REPORTS

The Contractor shall provide the COR with Monthly Progress Reports in electronic form in Microsoft Word and Project formats and stored in shared repository such as a Teams Channel. 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 Month.

The Monthly Progress Reports shall cover all work completed during the reporting period and work planned for the subsequent reporting period. The report shall also identify any problems that arose and provide a description of how the problems were resolved. If problems have not been completely resolved, the Contractor shall provide an explanation including their 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. It is expected that the Contractor shall keep in communication with VA accordingly so that issues that arise are transparent to both parties to prevent escalation of outstanding issues.

A. Monthly Progress Report

5.1.4 TECHNICAL KICKOFF MEEETING

A technical kickoff meeting shall be held within 10 days after award. The Contractor shall coordinate the date, time, and location (can be virtual) with the CO, the VA PM, the Contract Specialist (CS), and the COR/ACOR. The Contractor shall provide a draft agenda to the CO and VA PM at least five calendar days prior to the meeting. Upon Government approval of the 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. The Contractor shall distribute the updated presentation and meeting minutes to the CO, COR/ACOR and all attendees within three calendar days after the meeting.

A. Summary Report

5.1.5 VA MANDATORY TRAINING

All resources are required to have access to the VA network and shall complete all the required VA Talent Management System (TMS) training courses within three business days of submitting an onboarding package. The Contractor shall work with its respective onboarding point of contact and COR/ACOR, to obtain access to TMS to complete the mandatory training courses.

As an action under the Continuous Readiness in Information Security Program, VA's Assistant Secretary for Information and Technology issued a memorandum requiring all VA government and contract staff to complete information security awareness and applicable role-based training. The Contractor shall ensure Training completion and track TMS Training Certificates for VA Privacy and Information Security Awareness, Rules of Behavior, Health Insurance Portability and Accountability Act (HIPAA). If elevated privileges are required Role-Based training shall be identified for completion prior to gaining additional access. The Contractor shall provide and update the master onboarding tracking document of TMS training status.

Deliverable:

A. Master Onboarding tracking document of TMS training status with updates and TMS Training Certificates of Completion

5.1.6 ONBOARDING / OFFBOARDING

The Contractor shall support the onboarding and offboarding of its staff. The Contractor shall provide a Contract lead to support onboarding and offboarding actions in the IAM Portal. The Contractor shall provide a Weekly Onboarding/Offboarding Status Report as described in sections 5.1.6.1 and 5.1.6.2. The format for the weekly onboarding and offboarding status reports shall be developed collaboratively and approved by the COR/ACOR and the Contractor which shall be saved with all other deliverables.

5.1.6.1 ONBOARDING ACTIVITIES

Onboarding includes steps to obtain a VA PIV card, network and email account, complete training, initiate background investigations, and obtain Government Furnished Equipment (GFE). In addition, the Contractor shall identify individuals which may require elevated privileges to the necessary development and test environments for the various systems to be developed or enhanced.

A single Contractor Onboarding point of contact (POC) and back up POC shall be designated by the Contractor that tracks the onboarding status of all Contractor personnel. The Contractor Onboarding POCs shall be responsible for accurate and timely submission of all required VA onboarding paperwork to the VA COR/ACOR or applicable systems used for onboarding. 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, commercial email address, phone numbers, immediate contract supervisor, onboarding milestone dates, and their initial training date for VA Privacy and Information Security training. The Contractor shall provide an onboarding status in the Weekly Onboarding/Offboarding Status Report for review by the COR/ACOR, VA PM or Government designee. The report shall include:

• Current onboarding status for all personnel.

• Pending onboarding actions.

• Estimated completion dates for outstanding steps.

• Issues or delays impacting onboarding timelines.

The Contractor shall maintain a comprehensive onboarding status tracker that includes:

• Names of all personnel engaged on the task.

• Commercial email address and phone number.

• Immediate contract CTR supervisor.

• Onboarding milestone dates.

• Initial VA Privacy and Information Security training date.

• Percentage of support of resource allocation to what specific product

5.1.6.2 OFFBOARDING ACTIVITIES

The Contractor shall ensure timely offboarding of personnel, including:

• Return of GFE.

• Revocation of elevated privileges.

• Deactivation of network and email accounts.

• Notification to COR/ACOR of personnel departure.

The Contractor shall provide an offboarding status in the Weekly Onboarding/Offboarding Status Report to the COR/ACOR, VA PM, or Government designee, detailing the status of all offboarding activities.

A. Weekly Onboarding/Offboarding Status Report

5.2 HELM PRODUCT LINE MANAGEMENT SUPPORT (FFP)

5.2.1 HELM PRODUCT LINE SUPPORT

The Contractor shall holistically advance the systems engineering maturity of the HELM PL by ensuring compliance with DevSecOps practices, implementing Agile methodologies, and supporting VA’s Strategic Supply Chain Prioritization and Digital Modernization Strategy. To achieve this, the Contractor shall provide a qualified team of SMEs to facilitate the integration and oversight of capabilities & practices at both the product line and value stream levels, working collaboratively with stakeholders and partners. The Contractor shall support development of HELM PL briefing slides to include monthly Program Management Reviews (PMR) and Program Increment (PI) Planning committed and uncommitted objectives. The Contractor shall provide cross-functional SAFe resources to include SC Technical Expertise for the development of enhancements to the HELM products and underlying infrastructure in alignment with VA policies and procedures.

The Contractor shall:

• Track, process and manage Authority to Operate (ATO) activitiesfor PL by working with each product and SMEs to ensure compliance.

• Provide technical leads/SAFe Roles for PL management for Cyber Security, Solution, Architect/Engineer Architecture, Testing, Technical Lead, Overarching Program Lead, DevSecOps Engineer/Security Specialist

• Assist in defining new application implementation requirements, to include the generation of Epics and translation to Features and User Stories which make up the Product Roadmap and Product Increment Plans while mitigating dependencies between them.

• Consolidate requirements or sequencing to generate product line efficiencies

• Understand future state requirements for the successful implementation of new applications in VA and identify impacts to legacy or dependent systems.

• Provide guidance on dependencies between implementation requirements within and outside the product to reduce risk as new capabilities are introduced and current systems are retired.

• Identify and analyze the systems targeted for integration and the design and technologies needed to implement them.

• Assist with database solutions and designs for data migrations for implementations at VA sites.

• Provide product line analyses of risks and issues to identify trends and possible opportunities for responses and mitigations.

• Understand current and future-state data flows, networking, cybersecurity, and infrastructure requirements.

• Testing, training, sustainment

5.2.2 INTAKE PROCESS

HELM PL requires a standardized, repeatable, and transparent intake process to manage Government provided requirements for existing products, ongoing work, and any new capabilities introduced during the PoP. The Contractor shall partner with the Government to mature, operate, and continuously improve the existing HELM intake process, ensuring all requests are evaluated consistently and accurately.

The Contractor shall not create a new custom-made intake application or standalone web portal. Instead, the Contractor shall use and enhance VA approved platforms (e.g., Jira, SharePoint, Confluence, Power Apps/Automate, or other approved tools) to support intake activities, workflow routing, estimation, documentation, and reporting.

Within the first 60 days of the Base Period of PoP, the Contractor shall implement the following Intake Process components:

Centralized Intake Workflow

• Establish a single, unified intake workflow for HELM PL requirements—both new and existing.

• Receive, capture, and track all intake requests using VA approved tools.

• Ensure all requests remain visible to HELM PL leadership, COR/ACOR, VA PMs, product owners, and appropriate VA stakeholders.

• Coordinate with requestors to clarify scope, dependencies, constraints, and priority factors.

Requirements Analysis & Level of Effort (LOE)

• Analyze each request to determine estimated Level of Effort (LOE), required skill sets, potential scrum team sizing, risk factors, and estimated timeline.

• Conduct interviews, workshops, or follow up sessions with VA requestors and stakeholders, as needed.

• Document assumptions, dependencies, and constraints associated with each estimate.

• Provide standardized LOE outputs to support HELM PL governance and prioritization.

Technical Maturity & DevSecOps Readiness Assessments

• Perform a DevSecOps maturity assessment to document applicable processes, compliance gaps, and technical readiness.

• Conduct high-level architectural assessments to identify reuse opportunities, alignment with Enterprise Architecture, and compatibility with Product Line standards.

• Identify potential impacts to ATO, security posture, and environments.

Architecture Repository & Reuse Library

• Establish and maintain a HELM Architecture Repository within VA approved tools.

• Store vetted design patterns, reusable components, solution templates, and interface patterns.

• Ensure intake analysis includes review of existing patterns to encourage reuse, reduce duplication, and increase technical consistency.

Intake Workflows, SOPs, and Documentation

• Develop and maintain Intake Standard Operating Procedures (SOPs), including required data elements, routing logic, approval steps, timelines, and artifacts.

• Ensure SOPs reflect the actual tools and processes used by HELM PL teams.

• Provide updates to SOPs with each Option Period or as directed by HELM governance.

Requirements Analysis Proposal (RAP) For each intake request, the Contractor shall develop a RAP for each Option Period, Optional Task and any new requirements that includes:

• Scope, high level objectives, and functional/nonfunctional requirements.

• Estimated LOE, required skill sets, and recommended scrum team composition.

• Expected labor mix and a burndown plan illustrating resource utilization across the Period of Performance.

• High level schedule, milestones, and major dependencies.

• Identified risks, impediments, and mitigation recommendations.

• Required deliverables and applicable HELM PL processes.

The Contractor shall document and manage all agreed upon deviations from the RAP— resulting from Agile development adjustments, changes in Government priorities, or unforeseen barriers. All changes must be reviewed and approved by HELM PL Leadership and the COR/ACOR.

Integration with HELM Governance

• Ensure intake results (LOE estimates, RAPs, architectural considerations, risk summaries) are formatted to support HELM PL governance and prioritization processes.

• Support monthly and quarterly governance reviews by providing updated backlog statistics, intake disposition, and forecasts.

• Provide Monthly Backlog Report, showing intake volume, disposition, LOE summaries, and aging analysis.

• Intake Dashboard within VA approved tools, updated weekly, reflecting real-time status.

Deliverables A. Intake Analysis and Process Guide (SOPs, workflows, forms, estimation model, architecture reuse guidance) B. Requirements Analysis Proposal (RAP) for each intake item C. Monthly Backlog Report D. HELM Product Team Request Intake Tool/Workspace (within existing VA approved systems)

5.2.3 PROGRAM INCREMENT PLANNING

The Contractor shall support and deliver HELM PI Quarterly Planning activities to ensure alignment of product development objectives with VA strategic priorities. PI Planning shall be conducted in accordance with SAFe principles and HELM governance standards.

The Contractor shall:

• Facilitate and participate in HELM PI Planning sessions on a quarterly basis.

• Prepare and deliver all required planning artifacts, including PI Planning Agenda, Feature and Capability Backlogs aligned to VA priorities, Capacity Planning for HELM teams and resources, Dependency Identification and Resolution Plans across teams and programs, and Risk Assessment and Mitigation Strategies documented in a PI Risk Register.

• Coordinate with VA stakeholders to ensure all backlogs (initiatives, epics and stories) are prepared and prioritized and organized into Pre-Read Materials demonstrating that PL/SPL and Architecture visions are aligned, and SWOT analysis are completed prior to planning sessions and prepare PI Planning Summary Report and Objectives.

• Engage with other contractor teams and enterprise stakeholders during PI Planning to ensure shared understanding of dependencies, promote collaboration, and support efficient, non-duplicative execution of product development activities.

• Provide logistical and technical…