P02 MR SS Draft PWS.docx

Sources Sought Notice Attachment: Draft PWS

DRAFT PERFORMANCE WORK STATEMENT

DEPARTMENT OF VETERANS AFFAIRS

Office of Suicide Prevention Staff Sergeant Parker Gordon Fox Suicide Prevention Grant Program for

Data Technical Assistance and Training

Date: July 14, 2025 DRAFT PWS Version 1.0

Contents

BACKGROUND

Staff Sergeant Parker Gordon Fox Suicide Prevention Grant Program (SSG Fox SPGP) is part of the Office of Suicide Prevention. SSG Fox SPGP’s mission is to reduce military and Veteran suicide by focusing on clinical interventions and community-based outreach prevention strategies. The SSG Fox SPGP is authorized by Public Law 116-171 and implemented by final rule, promulgating 38 C.F.R part 78 regulations implementing Public Law 116-171 by establishing the SSG Fox SPGP. Through this program, VA has offered grants to eligible entities, identified in the regulations, for providing or coordinating suicide prevention services to Veterans and their families. The goal of the program is to identify Veterans who are at risk of suicide and their family members and to provide them with suicide prevention services either through VA or the community.

Per 38 C.F.R. part 78, grantees may provide the following suicide prevention services to program participants: Outreach to identify those at risk of suicide; Baseline mental health screening to eligible individuals; Education of communities, Veterans and families on suicide risk and prevention, how to identify those at risk of suicide, how and when to make referrals for care, and the types of suicide prevention resources available within the area; Provision of clinical services for emergency treatment; Case management services; Peer support services; VA benefits assistance for eligible individuals and their families; Assistance with obtaining and coordinating other benefits provided by the federal VA, a state or local VA, or an eligible entity; Assistance with emergent needs relating to health care services, daily living services, personal financial planning and counseling, transportation services, temporary income support services, fiduciary and representative payee services, legal services to assist the eligible individual with issues that may contribute to the risk of suicide, and child care. In addition, grantees may provide nontraditional and innovative approaches and treatment practices, as determined appropriate by VA.

In November 2021, VA awarded an effort to The MITRE Corporation for Federally Funded Research and Development Center (FFRDC) services to perform an Analysis of Alternatives (AoA) concerning functional prototypes for data collection tools and processes for grantees for the SSG Fox SPGP. The FFRDC was required to explore the potential use of up to five existing applications currently deployed at VA and deliver an AoA with findings, risks, and an overall recommendation. That analysis was delivered to VA, and the VA Office of Suicide Prevention selected the VA existing Behavioral Health Lab (BHL) Touch platform to configure for SSG Fox SPGP. The BHL Platform collected several of the same data within VA by VHA providers as was needed to collect from the grantees (not directly affiliated with VA).

The FFRDC conducted the BHL Touch system configuration to allow for additional data collection via BHL interview forms to comply with Congressional statute for a data collection tool. From 2022 through 2024, VA continued to refine the Data Collection Tool (DCT), identifying and testing additional data collection needs to meet Statute requirements. The DCT operates in VA’s Enterprise Cloud environment and achieved an Authority to Operate in June of 2025 for a 2-year period. The DCT functional prototype allowed VA to demonstrate the ability to securely collect sensitive de-identified Veteran mental health/suicide risk data, which by law has been included in the Interim Congressionally Mandated Report (CMR) and is in the process of being included in the Final CMR. VA demonstrated the success of the functional prototype and is now able to continue operation of the DCT in their production environment, which will allow the program to onboard additional grantees to the program for 2026 and beyond. The DCT platform is now undergoing transition back to VA or to commercial contractors to continue to manage the DCT environment, as mandated by the Statute.

SSG Fox SPGP is preparing to enter its fourth year. VA published the Notice of Funding Opportunity (NOFO) for Fiscal Year (FY) 2026 SSG Fox SPGP services on May 15, 2025. The NOFO assumes that Congress will extend the authority beyond September 2025 and appropriate funds consistent with section 201 of the Hannon Act as currently written. Applications are due July 18, 2025, and the awards will be announced by September 30, 2025. The Office of Suicide Prevention is prepared to allocate up to $52M to avoid a disruption in services through this NOFO, and once Congress finalizes legislative extension and appropriations as is anticipated, another NOFO could soon follow. There are presently 5-6 active bills in Congress relating to SSG Fox SPGP extension with the timeline of September 2025 in awareness.

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. Federal Information Processing Standard (FIPS) Publication 140-2, “Security Requirements for Cryptographic Modules.”

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

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

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

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 Security and Suitability Program,” June 4, 2024, https://www.va.gov/vapubs/index.cfm.

11. VA Handbook 0710, “Personnel Security and Suitability Program,” May 2, 2016, https://www.va.gov/vapubs/index.cfm.

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

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

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

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

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

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

18. 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”).

19. OIT Process Asset Library (PAL), OIT Process Asset Library. Reference Process Maps at https://www.va.gov/process/maps.asp and Artifact templates at https://www.va.gov/process/artifacts.asp.

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

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

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

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

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

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

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

27. 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).

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

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

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

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

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

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

34. NIST SP 800-63-3, 800-63A, 800-63B, 800-63C, “Digital Identity Guidelines,” updated March 02, 2020.

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

36. 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).

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

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

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

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

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

42. Office of Information Security (OIS) VAIQ #7424808 Memorandum, “Remote Access,” January 15, 2014, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28.

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

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

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

46. OMB M-22-18, “Enhancing the Security of the Software Supply Chain through Secure Software Development Practices,” September 14, 2022.

47. OMB M-23-16, “Update to Memorandum M-22-18,” June 9, 2023.

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

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

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

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

SCOPE OF WORK

The contractor shall provide data technical assistance and training for the SSG Fox grantee DCT and provide recommendations for process improvements to support on-boarding new grantees. Onboarding includes training grantees on how to use the DCT and the best ways to collect data for the system. The contractor shall leverage its experience in human-centered design and usability approaches to enhance existing dashboards using PowerBI or other business intelligence tools. The contractor shall recommend approvements to streamline business processes and workflows and identify opportunities to improve data collection and preparation processes to reduce administrative burdens.

PERFORMANCE DETAILS

PERFORMANCE PERIOD

The Period of Performance (PoP) for this Task Order (TO) is a 12-month base period, with two 12-month option periods.

The total duration of this TO, including the exercise of any option, shall not exceed 36 months.

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

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

Under current definitions, five are set by date:

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

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

PLACE OF PERFORMANCE

Tasks under this PWS shall be performed primarily at Contractor facilities. The Contractor shall identify the Contractor’s place of performance in their submission.

In the event that VA requires the Contract to travel to a VA site, any work at a VA site shall not take place on Federal holidays or weekends unless directed by the CO or the Contracting Officer’s Representative (COR).

TRAVEL

The Government anticipates travel under this effort to perform the tasks associated with the effort. Travel costs will not be directly reimbursed by the Government as a separate line item. Contractor attendance is required for two in-person conferences per year where the contractor, the VA, and the grantees enrolled in SSG Fox SPGP attend.

The specific destination for the travel will not be known until during contractor performance. All travel will be within the contiguous United States. The following is VA’s estimated long-distance travel (per year):

Estimated Travel:

Travel shall be in accordance with the Federal Travel Regulations and requires advanced concurrence by the COR.

SPECIFIC TASKS AND DELIVERABLES

The contractor shall perform the following:

PROJECT MANAGEMENT

The Contractor shall provide the COR with a Contractor Project Management Plan (CPMP) in electronic form formatted in Microsoft Word and/or Microsoft Project. The CPMP shall lay out the Contractor’s approach, timeline, and tools to be used in execution of the TO. The CPMP shall cover all work completed during the reporting period and work planned for the subsequent reporting period. The report shall 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 the Contractor’s plan and timeframe for resolving the issue. The report shall also include an itemized list of all Information and Communication Technology (ICT) deliverables and their current Section 508 conformance status. The Contractor shall monitor performance against the CPMP and report any deviations. It is expected that the Contractor will keep in communication with VA accordingly so that issues that arise are transparent to both parties to prevent escalation of outstanding issues.

The report shall include future timelines and plans, and detailed instructions and explanations for each required data element to ensure that data is accurate and consistent. The CPMPs shall reflect data as of the last day of the preceding month. The CPMP shall include how the Contractor coordinates and executes planned, routine, and ad hoc data collection reporting requests as identified within the PWS. Within ten days from TO award, the Contractor shall submit to the COR the initial baseline CPMP. The Contractor shall work with the COR to gain Government concurrence. In addition, the Contractor shall update the CPMP monthly in accordance with Section B of the contract. The Contractor shall meet with the COR monthly to review and provide updates to the CPMP. The Contractor shall work with the COR to gain Government approval of the updated CPMP.

Base Period Deliverable:

Monthly Contractor Project Management Plan.

Option Period 1 Deliverable:

Monthly Contractor Project Management Plan.

Option Period 2 Deliverable:

Monthly Contractor Project Management Plan.

DATA TECHNICAL ASSISTANCE AND TRAINING

The Contractor shall provide technical assistance and training to SSG Fox grantees on the use of the DCT. The Contractor shall redesign the database to allow VA to look at episodes of service for the same individual over various points in time (i.e., return to program - when an individual comes in and out of a grant program). Currently, the data schematic doesn't consider designating episodes of services. The redesign of the database shall account for individuals to come in and out of the program more than once. The Contractor shall also develop a new form for grantees to indicate someone is re-entering the program, as well as develop new rules for calculating pre- and post-assessment data as part of the evaluation process.

As the program grows, VA anticipates the need to expand capabilities for improved efficiencies. The Contractor shall implement recommended process improvements to gain greater efficiencies in grantee data reporting, including working with grantees on data quality improvements. The Contractor shall collect and submit grantee feedback to VA for review. The Contractor shall recommend prioritization of grantee recommendations for process improvements. VA will determine the feasibility of grantee recommendations for improvements to the process. As the identified areas for improvement are approved by the COR, the Contractor shall implement the process improvement(s). The goal is to enable faster, more flexible analysis as the grantee datasets grow.

The Contractor shall provide technical assistance and training to grantees by conducting weekly scheduled office hours for grantees that need additional onboarding for the DCT and use of the dashboards, additional assistance for the DCT and use of the dashboards, performing ad-hoc troubleshooting with grantees on the best way to resolve incorrect data reporting, including processes for archiving and resubmittal of data, and updating online training materials as needed to ensure currency and optimal processing and data accuracy. The Contractor shall track these engagements monthly, monitor dashboards across all grantees to help inform VA of any grantee compliance issues in data reporting, and provide quarterly analysis on the impacts of training.

Contractor Training activities shall include:

The Contractor shall provide Monthly Reports on Grantee Training and Quarterly Analysis Reports on Training Impacts. The Contractor shall develop and update existing online training as new program requirements or policies are rolled out that might impact data collection and reporting processes and provide the Updated Online Training Materials. The Contractor shall monitor dashboards in the DCT across all grantees to track program progress. This will help to inform VA of any grantee compliance issues in data reporting.

The Contractor shall provide a Usability and Recommendations Report that captures the results of the Contractor’s usability testing of existing dashboards with recommendations for redesign or enhancements to dashboards that can help improve grantee program performance.

Technical Assistance activities shall include:

With the guidance and direction of the VA, the Contractor shall work with VA as the data steward of the data pipeline from the DCT to the data analytics platform, managing the Extract, Transform, and Load processes.

The Contractor shall provide updates to Business Logic for database redesign, dashboard enhancements for Return to Program Functionality, and dashboard updates to address outstanding usability issues. The Contractor shall provide a redesign document of the database for Return to Program called a Return to Database Redesign White Paper. The Contractor shall enhance the database for access by VA business intelligence tools for Return to Program and deliver the Database Enhancement Technical Documentation.

The Contractor shall provide recommendations for expansion of the current toolset to include more efficient, cloud-based analytics capabilities.

The Contractor shall conduct usability testing of the existing dashboards and provide recommendations for redesign or enhancements to dashboards.

The Contractor shall document and implement updates to the dashboards to support new or evolving program requirements aligned with program objectives and to enhance dashboard usability and effectiveness for end-users.

Base Period Deliverables:

A. Quarterly Analysis Report on Training Impacts.

B. Monthly Report on Grantee Training.

C. Updated Online Training Materials.

D. Usability and Recommendations Report.

E. Return to Database Redesign White Paper.

F. Database Enhancement Technical Documentation.

Option Period 1 Deliverables:

A. Quarterly Analysis Report on Training Impacts.

B. Monthly Report on Grantee Training.

C. Updated Online Training Materials.

D. Usability and Recommendations Report.

E. Return to Database Redesign White Paper.

F. Database Enhancement Technical Documentation.

Option Period 2 Deliverables:

A. Quarterly Analysis Report on Training Impacts.

B. Monthly Report on Grantee Training.

C. Updated Online Training Materials.

D. Usability and Recommendations Report.

E. Return to Database Redesign White Paper.

F. Database Enhancement Technical Documentation.

GENERAL REQUIREMENTS

ENTERPRISE AND IT FRAMEWORK

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.

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.

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-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-3, 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-3 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.

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

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.

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 at the Cybersecurity & Infrastructure Security Agency (CISA) (https://www.cisa.gov/publication/tic-30-core-guidance-documents).

STANDARD COMPUTER CONFIGURATION

The Contractor IT end user solution that is developed for use on standard VA computers shall be compatible with and be supported on the standard VA operating system, Windows 10 (64bit) and Windows 11, Edge (Chromium based), and 365 Apps for enterprise. Applications delivered to VA and intended to be deployed to Windows 10 and or Windows 11 workstations shall be delivered as a signed .msi package with switches for silent and unattended installation and updates shall be delivered in signed .msp file formats for easy deployment using Microsoft Endpoint Configuration Manager (CM) VA’s current desktop application deployment tool. Signing of the software code shall be through a vendor provided certificate that is trusted by VA using a code signing authority such as Verizon/Cybertrust or Symantec/VeriSign. The Contractor shall also ensure and certify that their solution functions as expected when used from a standard VA computer, with non-admin, standard user rights that have been configured using the Defense Information Systems Agency (DISA) Secure Technical Implementation Guide (STIG) specific to the particular client operating system being used.

VETERAN FOCUSED INTEGRATION PROCESS (VIP) AND PRODUCT LINE MANAGEMENT (PLM)

The Contractor shall support VA efforts IAW the Veteran-Focused Integration Process (VIP) Guide and Product Line Management (PLM) Playbook. The major focus of VIP is on Enterprise Oversight, Governance, reporting, and establishing practices that focus on outcomes and continuously delivering sustainable IT capabilities to benefit the Veteran. PLM is a framework that focuses on delivering functional products that provide the highest priority work to customers while delivering simplified, reliable, and practical solutions to the business, medical staff, and our Veterans. The VIP Guide is a companion guide to the PLM Transformation Playbook and can be found at: https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371 and the PLM Transformation Playbook can be found at https://www.voa.va.gov/DocumentView.aspx?DocumentID=4946. VIP and PLM are the authoritative processes that IT projects must follow to ensure development and delivery of IT products.

The VIP Guide provides guidance for transitioning from project-centric to product-centric delivery. The VIP guide applies to all OIT Office of Management and Budget (OMB) reportable products that are required to collect and report costs, schedules, risks, and other valuable information in VA PARS (whether products are procured or developed by VA) and any VA Information Technology project effort in Software Product Management (SPM) and Infrastructure Operations (IO), or their successors, that touch the VA network regardless of IT organizational alignment (whether it spends government funding from VA's Congressional IT Appropriation or any other appropriation).

The PLM Transformation Playbook details how OIT leadership expects Product Lines (PLs) to implement PLM, DevOps, and Lean-Agile principles, methods, practices, and techniques through levels of maturity. The PLM Transformation Playbook applies to all Information Technology (IT) products aligned to PLs in the Software Product Management, Infrastructure Operations and Product Engineering organizations within the OIT organization.

Others outside the referenced groups or organizations may use the VIP Guide and PLM Transformation Playbook for situational awareness as needed.

PROCESS ASSET LIBRARY (PAL)

The Contractor shall perform their duties consistent with the processes defined in the OIT Process Asset Library (PAL). The PAL includes a spectrum of OIT functions and activities, such as project management, operations, service delivery, communications, acquisition, and resource management. PAL serves as an authoritative and informative repository of searchable processes, activities or tasks, roles, artifacts, tools and applicable standards and guides to assist the OIT workforce, Government and Contractor personnel. OIT utilizes PAL processes to ensure compliance with policies and regulations and to meet VA quality standards. The PAL includes the contractor onboarding process consistent with Section 6.2.2 and can be found at process_CONB_ext.docx (live.com). The main PAL can be accessed at www.va.gov/process.

AUTHORITATIVE DATA SOURCES

The VA Enterprise Architecture Repository (VEAR) is one component within the overall EA that establishes the common framework for data taxonomy for describing the data architecture used to develop, operate, and maintain enterprise applications. The Contractor shall comply with the department’s Authoritative Data Source (ADS) requirement that VA systems, services, and processes throughout the enterprise shall access VA data solely through official VA ADSs where applicable, see below. The Information Classes which compose each ADS are located in the VEAR, in the Data & Information domain. The Contractor shall ensure that all delivered applications and system solutions support:

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

2. Interfacing with Capital Asset Inventory (CAI) to conduct real property record management actions, if the solution relies on real property records data. CAI is the authoritative source for VA real property record management data.

3. Interfacing with electronic Contract Management System (eCMS) for access to contract, contract line item, purchase requisition, offering vendor, and solicitation information above the micro-purchase threshold, if the solution relies on procurement data. ECMS is the authoritative source for VA procurement actions data.

4. Interfacing with HRSmart Human Resources Information System to conduct personnel action processing, on-boarding, benefits management, and compensation management, if the solution relies on personnel data. HRSmart is the authoritative source for VA personnel information data.

5. Interfacing with VA Profile to access personal contact information, if the solution relies on VA Veteran personal contact information data. VA Profile is the authoritative source for VA Veteran Personal Contact Data.

6. Interfacing with VA/Department of Defense (DoD) Identity Repository (VADIR) for determining eligibility for VA benefits under Title 38, if the solution relies on qualifying active duty military service data. VADIR is the authoritative source for qualifying active duty military service in VA.

7. Interfacing with VA Systems Inventory (VASI) to access VA systems information, if the solution relies on VA system information. VASI is the authoritative source for VA Information Technology systems.

8. Interfacing with Enterprise Mission Assurance Support Service (eMASS) to access the Authority to Operate (ATO) status of all VA Information Systems. eMASS contains the official Authority to Operate (ATO) status of all VA Information Systems.

SOCIAL SECURITY NUMBER (SSN) REDUCTION

The Contractor solution shall support the Social Security Number (SSN) Fraud Prevention Act (FPA) of 2017 which prohibits the inclusion of SSNs on any document sent by mail. The Contractor support shall also be performed in accordance with Section 240 of the Consolidated Appropriations Act (CAA) 2018, enacted March 23, 2018, which mandates VA to discontinue using SSNs to identify individuals in all VA information systems as the Primary Identifier. The Contractor shall ensure that any new IT solution discontinues the use of SSN as the Primary Identifier to replace the SSN with the ICN in all VA information systems for all individuals. The Contractor shall ensure that all Contractor delivered applications and systems integrate with the VA MPI for identity traits to include the use of the ICN as the Primary Identifier. The Contractor solution may only use a Social Security Number to identify an individual in an information system if and only if the use of such number is required to obtain information VA requires from an information system that is not under the jurisdiction of VA.

SECURITY AND PRIVACY REQUIREMENTS

It has been determined that protected health information will not be disclosed or accessed, and a signed Business Associate Agreement (BAA) is not required.

POSITION/TASK RISK DESIGNATION LEVEL(S)

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

Position Sensitivity and Background Investigation Requirements by Task

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

Under both tasks in this requirement, there are no national security duties and no public trust duties. According to the US Office of Personnel Management, the positions required for this requirement are considered non-sensitive, low risk, and Tier 1.

CONTRACTOR PERSONNEL SECURITY REQUIREMENTS

Contractor Responsibilities:

1. The Contractor shall prescreen all personnel requiring access to the computer systems to ensure they maintain the appropriate Background Investigation, and are able to read, write, speak, and understand the English language.

1. Within 3 business days after award, the Contractor shall provide a roster of Contractor and Subcontractor employees to the COR to begin their background investigations in accordance with the PAL template artifact. The Contractor Staff Roster shall contain the Contractor’s Full Name, Date of Birth, Place of Birth, individual background investigation level requirement (based upon Section 6.2 Tasks), etc. The Contractor shall submit full Social Security Numbers either within the Contractor Staff Roster or under separate cover to the COR. The Contractor Staff Roster shall be updated and provided to VA within 1 day of any changes in employee status, training certification completion status, Background Investigation level status, additions/removal of employees, etc. throughout the Period of Performance. The Contractor Staff Roster shall remain a historical document indicating all past information and the Contractor shall indicate in the Comment field, employees no longer supporting this contract. The preferred method to send the Contractor Staff Roster or Social Security Number is by encrypted e-mail. If unable to send encrypted e-mail, other methods which comply with FIPS 140-2 (or its successor) are to encrypt the file, use a secure fax, or use a traceable mail service. (Note that by September 22, 2026, all FIPS 140-2 certificate validations will be placed on the Historical List. See FIPS Transition Effort Timeline for more details: https://csrc.nist.gov/projects/fips-140-3-transition-effort#schedule)

1. The Contractor should coordinate with the location of the nearest VA fingerprinting office through the COR. Only electronic fingerprints are authorized. The Contractor shall bring their completed Security and Investigations Center (SIC) Fingerprint request form with them (see paragraph d.4. below) when getting fingerprints taken.

c. The Contractor shall ensure the following required forms are submitted to the COR within 5 days after contract award:

1) Optional Form 306

2) Self-Certification of Continuous Service

3) VA Form 0710

4) Completed SIC Fingerprint Request Form

The Contractor personnel shall submit all required information related to their background investigations (completion of the investigation documents (SF85, SF85P, or SF 86) utilizing the Office of Personnel Management’s (OPM) Electronic Questionnaire for Investigations Processing (e-QIP) after receiving an email notification from the SIC.

The Contractor employee shall certify and release the e-QIP document, print, and sign the signature pages, and send them encrypted to the COR for electronic submission to the SIC. These documents shall be submitted to the COR within 3 business days of receipt of the e-QIP notification email. (Note: OPM is moving towards a “click to sign” process. If click to sign is used, the Contractor employee should notify the COR within 3 business days that documents were signed via e-QIP).

1. The Contractor shall be responsible for the actions of all personnel provided to work for VA under this contract. In the event that damages arise from work performed by Contractor provided personnel, under the auspices of this contract, the Contractor shall be responsible for all resources necessary to remedy the incident.

1. A Contractor may be granted unescorted access to VA facilities and/or access to VA Information Technology resources (network and/or protected data) with a favorably adjudicated Special Agreement Check (SAC), completed training delineated in VA Handbook 6500.6 (Appendix C, Section 4), signed “Contractor Rules of Behavior”, and with a valid, operational Personal Identity Verification (PIV) credential for PIV-only logical access to VA’s network. A PIV card credential can be issued once your SAC has been favorably adjudicated and your background investigation has been scheduled by OPM. However, the Contractor will be responsible for the actions of the Contractor personnel they provide to perform work for VA. The investigative history for Contractor personnel working under this contract must be maintained in the database of OPM.

1. The Contractor, when notified of an unfavorably adjudicated background investigation on a Contractor employee as determined by the Government, shall withdraw the employee from consideration in working under the contract.

Failure to comply with the Contractor personnel security investigative requirements may result in loss of physical and/or logical access to VA facilities and systems by Contractor and Subcontractor employees and/or termination of the contract for default.

PIV Credential Holders must follow all HSPD-12 policies and procedures as well as use and protect their assigned identity credentials in accordance with VA policies and procedures, displaying their badges at all times, and returning the identity credentials upon termination of their relationship with VA.

Deliverable:

Contractor Staff Roster.

METHOD AND DISTRIBUTION OF DELIVERABLES

The Contractor shall deliver documentation in electronic format, unless otherwise directed in Section B of the TO. Acceptable electronic media include: Microsoft 365 suite, MS Word, MS Excel, MS PowerPoint, MS Project, MS Access, MS Visio, AutoCAD, and Adobe Postscript Data Format (PDF).

PERFORMANCE METRICS

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

2. Efficient and effective in meeting requirements

3. Meets technical needs and mission requirements

4. Provides quality services/products

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

Satisfactory or higher

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

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

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

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

FACILITY/RESOURCE PROVISIONS

The Government will provide office space, telephone service and system access when authorized contract staff work at a Government location as required in order to accomplish the Tasks associated with this PWS. All procedural guides, reference materials, and program documentation for the project and other Government applications will also be provided on an as-needed basis.

The Contractor shall request other Government documentation deemed pertinent to the work accomplishment directly from the Government officials with whom the Contractor has contact. The Contractor shall consider the COR as the final source for needed Government documentation when the Contractor fails to secure the documents by other means. The Contractor is expected to use common knowledge and resourcefulness in securing all other reference materials, standard industry publications, and related materials that are pertinent to the work.

VA may provide remote access to VA specific systems/network in accordance with VA Handbook 6500, which requires the use of a VA approved method to connect external equipment/systems to VA’s network. Citrix Access Gateway (CAG) and now the Azure Virtual Desktop (AVD) (as VA is currently transitioning from CAG to the AVD), are the current and only VA approved methods for remote access users when using or manipulating VA information for official VA Business. VA permits CAG remote access through approved Personally Owned Equipment (POE) and Other Equipment (OE) provided the equipment meets all applicable 6500 Handbook requirements for POE/OE. All of the security controls required for Government furnished equipment (GFE) must be utilized in approved POE or OE.