VetRide - FY27 RFI - Draft.docx
DOCX document 226 KB Posted
- Solicitation number
- 36C10B27Q0139
About this file
This is a Draft Performance Work Statement (PWS) for the VetRide Transportation Solution, a veteran transportation software platform to be provided to the Department of Veterans Affairs Veterans Health Administration. The VA seeks a fully operational, enterprise-wide licensed transportation scheduling and management system hosted within the VA Enterprise Cloud that supports over 20,000 existing users and accommodates at least 15,000 concurrent users across multiple VA Medical Centers without system degradation. The solution must transition from Mobile Data Computer (MDC) infrastructure to Government Furnished Equipment (GFE) mobile devices running iOS and Android applications, integrate with the Electronic Health Record Modernization (EHRM) system, support the Highly Rural Transportation Grant (HRTG) Portal for trip entry and budgeting, provide vendor APIs for third-party integration, and include automated scheduling with dynamic routing and rerouting capabilities for common carrier and special mode transportation services.
The contractor shall deliver comprehensive hosting, maintenance, integration support, telecommunications, and support services as a single point of contact throughout a 12-month base period followed by up to four optional 12-month periods. Key deliverables include a Contractor Project Management Plan, weekly and monthly progress reports with infrastructure monitoring data, and comprehensive technical documentation covering system architecture, security controls, CI/CD processes, and operational runbooks. The solution must comply with extensive VA security requirements including VA Critical Security Controls effective July 1, 2025, Federal Identity Credential and Access Management (FICAM) requirements with PIV card authentication at Identity Assurance Level 3, IPv6-only capability, Trusted Internet Connection standards, HIPAA compliance for Protected Health Information, Section 508 accessibility standards, and AI governance requirements if generative AI is incorporated. The contractor must implement NIST SP 800-37 Risk Management Framework controls, maintain an Authorization to Operate (ATO), conduct annual security assessments including penetration testing and vulnerability scanning, and immediately report security incidents within one hour of discovery. All custom-developed code and technical documentation must be delivered to VA with unlimited rights in accordance with the SHARE IT Act, and the contractor must maintain VA personnel's continuous read/write access to all requirements management systems throughout the contract period and upon transition.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 36C10B27Q0139.docx | DOCX document |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
VetRide Transportation Solution
VA-27-00009483
DRAFT PERFORMANCE WORK STATEMENT
DEPARTMENT OF VETERANS AFFAIRS
Veterans Health Administration Veterans Transportation Service
VetRide Transportation Solution
Date: 11/20/2026
VA-27-00009483
PWS Version Number: 1.4
Contents
| 1.0 | BACKGROUND | 4 |
| 2.0 | APPLICABLE DOCUMENTS | 4 |
| 3.0 | SCOPE OF WORK | 8 |
| 3.1 | System Requirements | 8 |
| 3.2 | Removal of MDCs: Transition to GFE Mobile Devices | 9 |
| 3.3 | Driver Application: VetRide Mobile Application Compliance | 9 |
| 3.4 | Highly Rural Transportation Grant (HRTG) Portal-External: Trip Entry, Budgeting, and Tracking | 9 |
| 3.5 | Emergency Vendor Portal: Emergent Transport Invoicing | 9 |
| 3.6 | EHRM Integration: Appointment, Forms, and Run Reports | 9 |
| 3.7 | GFE Application Support: Android and Apple Platforms | 9 |
| 3.8 | Automated Scheduling: Trip Assignment and Third-Party Dispatch | 9 |
| 3.9 | Vendor API: Information Transfer Capabilities | 10 |
| 4.0 | PERFORMANCE DETAILS | 10 |
| 4.1 | PERFORMANCE PERIOD | 10 |
| 4.2 | PLACE OF PERFORMANCE | 10 |
| 4.3 | TRAVEL | 10 |
| 5.0 | PROJECT MANAGEMENT | 11 |
| 5.1 | CONTRACTOR PROJECT MANAGEMENT PLAN | 11 |
| 5.2 | Kick-Off Meeting | 11 |
| 5.3 | Reporting Requirements | 11 |
| 5.3.1 | Weekly progress reports | 11 |
| 5.3.2 | Monthly Delivery and Monitoring Report and Roster | 12 |
| 5.4 | Documentation Updates | 12 |
| 5.4.1 | Technical Documentation Expansion | 12 |
| 5.4.2 | Requirements Development and Approval | 12 |
| 5.4.3 | Defect Resolution and Hotfixes | 13 |
| 5.5 | VETRIDE SCHEDULING SOFTWARE SYSTEM | 13 |
| 5.6 | Highly Rural Transportation Grants (HRTG) Portal/Users | 14 |
| 6.0 | GENERAL REQUIREMENTS | 15 |
| 6.1 | ENTERPRISE AND IT FRAMEWORK | 15 |
| 6.2 | VA TECHNICAL REFERENCE MODEL | 15 |
| 6.3 | ZERO TRUST – VA CRITICAL SECURITY CONTROLS | 15 |
| 6.4 | FEDERAL IDENTITY, CREDENTIAL, AND ACCESS MANAGEMENT (FICAM) | 15 |
| 6.5 | INTERNET PROTOCOL VERSION 6 (IPv6) | 17 |
| 6.6 | TRUSTED INTERNET CONNECTION (TIC) | 17 |
| 6.7 | STANDARD COMPUTER CONFIGURATION | 17 |
| 6.8 | VETERAN FOCUSED INTEGRATION PROCESS (VIP) AND PRODUCT LINE MANAGEMENT (PLM) | 18 |
| 6.9 | PROCESS ASSET LIBRARY (PAL) | 19 |
| 6.10 | AUTHORITATIVE DATA SOURCES | 19 |
| 6.11 | SOCIAL SECURITY NUMBER (SSN) REDUCTION | 20 |
| 6.12 | SOFTWARE AND LICENSING REQUIREMENTS | 20 |
| 6.13 | GENERATIVE ARTIFICIAL INTELLIGENCE REQUIREMENTS | 20 |
| 6.14 | AI SYSTEM/LLM DEVELOPMENT AND OPERATION DOCUMENTATION REQUIREMENTS | 22 |
| 6.15 | MONITORING, REPORTING, AND CORRECTIVE ACTION | 24 |
| 6.16 | AI MODEL UPDATES AND CHANGE DISCLOSURES | 24 |
| 6.17 | SOURCE CODE HARMONIZATION AND REUSE IN INFORMATION TECHNOLOGY (SHARE IT Act) | 24 |
| ADDENDUM A – ADDITIONAL VA REQUIREMENTS, CONSOLIDATED | 25 | |
| ADDENDUM B – VA INFORMATION AND INFORMATION SYSTEM SECURITY/ PRIVACY LANGUAGE | 30 |
BACKGROUND
The Department of Veterans Affairs (VA), Veterans Health Administration (VHA), and Member Services (MS) Veterans Transportation Program (VTP) require the VetRide Transportation Solution, which provides scheduling software, routing systems, invoice processing for contracted and non-contracted vendors, and hardware deployment across VA medical centers. The solution delivers integrated transportation capabilities including vehicle, passenger, clinic, and Beneficiary Travel (BT) eligibility, dynamic and automated routing and scheduling, and comprehensive reporting. It supports decentralized operations in which each VA medical center manages transportation for Veterans in its service area and offers reimbursement for medically related travel.
Hosted in the VA Enterprise Cloud (VAEC), the VetRide solution is used by Veterans, vendors, and VA staff to coordinate transportation, offers free rides to eligible Veterans, includes an administrative portal for managing requests and scheduling, tracks Veteran Beneficiary Travel Eligibility, Special Mode of Transportation (SMT), and Common Carrier, which enhances access to healthcare by ensuring systematic transportation for medical appointments.
The VA seeks to improve access to health care through a VetRide Transportation solution. VetRide provides a systematic approach to providing Veterans with rides to and from VA health care facilities for scheduled medical appointments. Transportation services are improved by providing VA health care facilities staff to support ride coordination, ride scheduling/routing and driving.
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 CryptogCACaphic Modules”, March 22, 2019
3. FIPS Pub 199. “Standards for Security Categorization of Federal Information and Information Systems,” February 2AC004
4. FIPS Pub 200, “Minimum Security Requirements for Federal Information and Information Systems,” March 2006
5. FIPS Pub 201-3, “Personal Identity Verification of Federal Employees and Contractors,” January 2022
6. 10 U.S.C. § 2224, "Defense Information Assurance Program", as amended
7. 5 U.S.C. § 552a, as amended, “The Privacy Act of 1974”
8. Public Law 109-461 (P.L. 109-461), Veterans Benefits, Health Care, and Information Technology Act of 2006, as amended, Title IX, Information Security Matters
9. 42 U.S.C. § 2000d “Title VI of the Civil Rights Act of 1964”, as amended
10. VA Directive 0710, “Personnel Vetting Program,” September 8, 2025, https://www.va.gov/vapubs/index.cfm
11. VA Handbook 0710, “Personnel Vetting Program,” September 8, 2025, https://www.va.gov/vapubs/index.cfm
12. VA Directive 6102, “Internet/Intranet Services,” August 5, 2019
13. 36 C.F.R. Part 1194 “Information and Communication Technology Standards and Guidelines,” as amended
14. Office of Management and Budget (OMB) Circular A-130, “Managing Federal Information as a Strategic Resource,” July 28, 2016
15. 32 C.F.R. Part 199, “Civilian Health and Medical Program of the Uniformed Services (CHAMPUS)”, as amended
16. NIST SP 800-66 Rev. 2, “Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule: A Cybersecurity Resource Guide,” February 2024
17. 45 C.F.R Parts 160 and 164, Subparts A and E, the Standards for Privacy of Individually Identifiable Health Information (“Privacy Rule”); and 45 C.F.R. Parts 160 and 164, Subparts A and C, the Security Standard (“Security Rule”); as amended
18. Sections 504 and 508 of the Rehabilitation Act (29 U.S.C. § 794d), as amended
19. Homeland Security Presidential Directive (12) (HSPD-12), August 27, 2004
20. VA Directive 6500, “VA Cybersecurity Program,” February 24, 2021 (see VA NOTICE 24-18, dated September 27, 2024, “Update to VA Directive 6500 Cybersecurity Program”, and VA Notice 25-07, dated 3/18/25, “Amending VA Directive 6500 to incorporate M-24-15”)
21. VA Handbook 6500, “Risk Management Framework for VA Information Systems VA Information Security Program,” February 24, 2021 (see VA Notice 25-01, dated October 15, 2024, “Update to VA Handbook 6500 Risk Management Framework for VA Information Systems VA Information Security Program”, and VA Notice 25-06, dated 3/18/25, “Amending VA Directive 6500 to incorporate M-24-15”, VA Notice 25-16, dated September 15, 2025, “Amending VA Handbook 6500 to Replace Enterprise Mission Assurance Support Services Tool With Office of Information Technology Governance Risk Compliance Tool, and VA Notice 25-17, dated September 22, 2025, “Rescission Of Office Of Information Security (OIS) Deputy Assistant Secretary (DAS) Memorandum – Requirements of Proper Plan of Action and Milestones (POA&M) Completion)
22. VA Handbook 6500.2, “Management of Breaches Involving Sensitive Personal Information (SPI),” June 30, 2023
23. VA Handbook 6500.6, “Contract Security,” March 12, 2010 (see VA Notice 24-12, dated April 22, 2024, “Update to VA Handbook 6500.6, Contract Security, Appendix C VA Information and Information System Security/Privacy Language For Inclusion Into Contracts, As Appropriate”)
24. VA Handbook 6500.8, “Information System Contingency Planning,” March 25, 2025
25. VA Handbook 6500.10, “Mobile Device Security Policy,” February 15, 2018 (see VA NOTICE 25-10, dated June 9, 2025, “Use of Personally Owned Mobile Devices Policy Amendment of Department of Veterans Affairs Handbook 6500.10”, and VA Notice 25-15, dated August 22, 2025, “Update to VA Handbook 6500.10 Mobile Device Security Policy”)
26. VA Handbook 6500.11, “VA Firewall Configuration,” August 22, 2017
27. OIT Process Asset Library (PAL), OIT Process Asset Library.
28. One-VA Technical Reference Model (TRM) (reference at https://www.va.gov/trm/TRMHomePage.aspx)
29. VA Directive 6508, “Implementation of Privacy Threshold Analysis and Privacy Impact Assessment,” October 15, 2014
30. VA Directive 6510, “VA Identity, Credential and Access Management,” September 3, 2024
31. VA Handbook 6510, “VA Identity, Credential and Access Management,” September 27, 2024
32. VA Directive and Handbook 6513, “Secure External Connections,” October 12, 2017
33. VA Directive 6300, “Records and Information Management,” September 21, 2018
34. VA Handbook, 6300.1, “Records Management Procedures,“ March 24, 2010
35. NIST SP 800-37 Rev 2, “Risk Management Framework for Information Systems and Organizations: A System Life Cycle Approach for Security and Privacy,” December 2018
36. NIST SP 800-53 Rev. 5, “Security and Privacy Controls for Federal Information Systems and Organizations,” September 23, 2020 (includes updates as of 12/10/2020)
37. VA Directive 0735, “Homeland Security Presidential Directive 12 (HSPD-12) Program,” October 26, 2015
38. VA Handbook 0735, “Homeland Security Presidential Directive 12 (HSPD-12) Program,” March 24, 2014
39. OMB Memorandum 05-24, “Implementation of Homeland Security Presidential Directive (HSPD) 12 – Policy for a Common Identification Standard for Federal Employees and Contractors,” August 5, 2005
40. OMB Memorandum M-19-17, “Enabling Mission Delivery Through Improved Identity, Credential, and Access Management,” May 21, 2019
41. OMB Memorandum, “Guidance for Homeland Security Presidential Directive (HSPD) 12 Implementation,” May 23, 2008
42. Federal Identity, Credential, and Access Management (FICAM) Architecture, June 30, 2023 (FICAM Architecture (idmanagement.gov))
43. NIST SP 800-116 Rev 1, “Guidelines for the Use of Personal Identity Verification (PIV) Credentials in Facility Access,“ June 2018
44. NIST SP 800-63 Rev 4, 800-63A-4, 800-63B-4, 800-63C-4, “Digital Identity Guidelines,” August 1, 2025
45. NIST SP 800-157, “Guidelines for Derived PIV Credentials,” December 2014
46. VA Memorandum, VAIQ #7100147, “Continued Implementation of Homeland Security Presidential Directive 12 (HSPD-12),” April 29, 2011 (reference https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514)
47. IAM Identity Management Business Requirements Guidance document, May 2013, (reference Enterprise Architecture Section, PIV/IAM (reference https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514)
48. VA Memorandum “Personal Identity Verification (PIV) Logical Access Policy Clarification,” July 17, 2019, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4896
49. Trusted Internet Connections (TIC) 3.0 Core Guidance Documents, https://www.cisa.gov/publication/tic-30-core-guidance-documents
50. OMB Memorandum M-19-26, “Update to the Trusted Internet Connections (TIC) Initiative,” September 12, 2019
51. OMB Memorandum M-08-23, “Securing the Federal Government’s Domain Name System Infrastructure,” August 22, 2008
52. Sections 524 and 525 of the Energy Independence and Security Act of 2007, (P.L. 110–140), December 19, 2007
53. Section 104 of the Energy Policy Act of 2005, (P.L. 109–58), August 8, 2005
54. Executive Order 13221, “Energy-Efficient Standby Power Devices,” August 2, 2001
55. Executive Order 14148, “Initial Rescissions of Harmful Executive Orders and Actions,” dated January 20, 2025
56. VA Directive 0057, “VA Environmental Management Program,” October 25, 2022
57. OIS VAIQ #7424808 Memorandum, “Remote Access,” January 15, 2014, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28
58. Clinger-Cohen Act of 1996, 40 U.S.C. §11101 and §11103
59. “Veteran Focused Integration Process (VIP) Guide 4.0,” March 2021, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371
60. VA Memorandum “Proper Use of Email and Other Messaging Services,” January 2, 2018, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28
61. “Product Line Management Transformation Playbook” version 3.1, August 2023, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4946
62. NIST SP 500-267B Revision 1, “USGv6 Profile,” November 2020
63. OMB Memorandum M-21-07, “Completing the Transition to Internet Protocol Version 6 (IPv6),” November 19, 2020
64. Social Security Number (SSN) Fraud Prevention Act of 2017
65. Section 240 of the Consolidated Appropriations Act (CAA) 2018, March 23, 2018
66. C.F.R Title 15 Part 7, “Securing the Information and Communications Technology and Services (ICTS) Supply Chain”, as amended
67. Executive Order 14028, “Executive Order on Improving the Nation's Cybersecurity,” May 12, 2021, https://bidenwhitehouse.archives.gov/briefing-room/presidential-actions/2025/01/16/executive-order-on-strengthening-and-promoting-innovation-in-the-nations-cybersecurity/
68. OMB Memorandum M-22-09, “Moving the U.S. Government Toward Zero Trust Cybersecurity Principles”, January 26, 2022, https://www.whitehouse.gov/wp-content/uploads/2022/01/M-22-09.pdf.
69. NIST SP 800-52 Revision 2, “Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations
70. OMB M-26-05, “Adopting a Risk-based Approach to Software and Hardware Security,” January 23, 2026
71. OMB M-21-31, “Improving the Federal Government’s Investigative and Remediation Capabilities Related to Cybersecurity Incidents,” August 27, 2021
72. NIST SP 800-88 Revision 1 “Guidelines for Media Sanitization,” December 2014
73. CISA Binding Operational Directive (BOD) 19-02: “Vulnerability Remediation Requirements of Internet-Accessible Systems,” April 29, 2019, BOD 19-02: Vulnerability Remediation Requirements for Internet-Accessible Systems | CISA
74. CISA BOD 22-01: “Reducing the Significant Risk of Known Exploited Vulnerabilities,” November 3, 2021, BOD 22-01: Reducing the Significant Risk of Known Exploited Vulnerabilities | CISA
75. CISA BOD 23-01: Improving Asset Visibility and Vulnerability Detection on Federal Networks.” Cybersecurity & Infrastructure Security Agency (CISA), BOD 23-01: Improving Asset Visibility and Vulnerability Detection on Federal Networks | CISA
76. VA Directive 6550, Pre-Procurement Assessment and Implementation of Medical Devices/Systems, June 03, 2019
77. VA Memorandum, “VA Security Controls,” January 17, 2025, https://www.voa.va.gov/DocumentView.aspx?DocumentID=5010
78. E.O. 13960, “Promoting the Use of Trustworthy Artificial Intelligence in the Federal Government,” December 3, 2020
79. E.O. 14319, “Preventing Woke AI in the Federal Government,” July 23, 2025
80. OMB Memorandum M-25-21, “Accelerating Federal Use of AI through Innovation, Governance, and Public Trust,” April 3, 2025
81. OMB Memorandum M-25-22, “Driving Efficient Acquisition of Artificial Intelligence in Government,” April 3, 2025
82. OMB Memorandum M-26-04, “Increasing Public Trust in Artificial Intelligence (AI) Through Unbiased AI Principles,” December 11, 2025
SCOPE OF WORK
The Contractor shall provide a fully operational VTP VetRide Transportation Solution that supports Veteran transportation operations across the Department of Veterans Affairs (VA). The Contractor shall deliver all required hosting, integration support to align with evolving legislative and stakeholder requirements, maintenance, telecommunications, support services and shall act as the single point of contact for all solution-related activities. The VetRide Solution shall be hosted within the VAEC. The solution shall be fully operational and available for use at the start of the Period of Performance. The hosting environment shall meet all VA technical and security requirements and maintain a full Authorization to Operate (ATO).
The VTP solution shall integrate with Government-Furnished Equipment (GFE) to support real-time communication across Common Carrier and SMT Transport. Support integration with VA clinical systems, community transportation providers, and other required interfaces. Provide Veteran-facing self-service capabilities for scheduling, notifications, and trip status. Support high-volume data processing and reports with consistent performance.
The Contractor shall provide, maintain, and enhance the entire VetRide Platform, including all integrations and interfaces, to support VA transportation operations and all associated personnel and resources.
System Requirements These revised requirements establish the VetRide platform, as a secure, reliable and scalable solution transitioning from Mobile Data Computers (MDCs) to GFE mobile devices, issued to eligible users, while supporting vendor integration through dedicated Application Programming Interfaces (API). The platform must be iPhone Operating System (iOS) and Android compliant for GFE-based users, integrate with key VA portals and systems, support automated scheduling, and provide vendor API capabilities for external vendor systems. The Contractor is responsible for ensuring the platform meets current operational, technical, and compliance needs.
Removal of MDCs: Transition to GFE Mobile Devices References to MDCs are hereby removed from the VetRide platform requirements. The platform will utilize GFE mobile devices, which will be provided to drivers and personnel. These devices must support secure and reliable communications and be compliant with VA security standards.
Driver Application: VetRide Mobile Application Compliance The VetRide driver application must be fully compliant with iOS, ensuring seamless operation on Apple mobile devices. The platform must also support Android devices, providing cross-platform compatibility for all GFE mobile devices issued by the VA. This update eliminates the need for MDCs and requires robust app support for both Apple and Android operating systems.
Highly Rural Transportation Grant (HRTG) Portal-External: Trip Entry, Budgeting, and Tracking The VetRide platform must integrate with the HRTG Portal-External, enabling users to enter trips, manage budgeting, and track transportation activities. This integration is essential for effective resource allocation and oversight of transportation services.
Emergency Vendor Portal: Emergent Transport Invoicing Integration with the Emergency Vendor Portal is required to allow vendors to submit invoices for emergent transports directly through the platform. This streamlines the billing process and ensures timely payment for urgent transportation services.
EHRM Integration: Appointment, Forms, and Run Reports The VetRide platform must integrate with the Electronic Health Record Modernization (EHRM) system. This integration will enable the ability to view appointment information, power forms, and encounters, as well as allow the uploading of ambulance run reports. These capabilities are critical for maintaining accurate records and determining transport eligibility.
GFE Application Support: Android and Apple Platforms The VetRide platform must provide robust application support for both Android and Apple GFE mobile devices. MDCs are no longer part of the solution; all mobile functionality must be delivered via GFE-provided smartphones or tablets. The application must offer secure, reliable, and accessible features for drivers and dispatch personnel across both platforms.
Automated Scheduling: Trip Assignment and Third-Party Dispatch Automated scheduling functionality is required. The platform must be capable of adding trips to runs for VA Transportation Service (VTS) drivers and support potential third-party dispatch operations. Scheduling should be efficient, minimize manual intervention, and optimize transportation resources to increase access to care for Veterans.
Vendor API: Information Transfer Capabilities The VetRide platform must provide an Application Programming Interface (API) for vendors, enabling secure information transfer and integration with external systems. This API will facilitate data exchange for trip coordination, invoice submission, and other operational needs, enhancing interoperability and vendor engagement.
PERFORMANCE DETAILS
PERFORMANCE PERIOD
The period of Performance (PoP) shall be one 12-Month Base Period, followed by up to four additional 12-month option periods, and one optional task if exercised.
Any work at a Government site shall not take place on Federal holidays or weekends unless directed by the Contracting Officer (CO).
There are 11 Federal holidays set by law (USC Title 5 Section 6103) that VA follows:
Under current definitions, five are set by date:
| New Year's Day | January 1 | |
| Juneteenth | June 19 | |
| Independence Day | July 4 | |
| Veterans Day | November 11 | |
| Christmas Day | December 25 |
If any of the above falls on a Saturday, then Friday shall be observed as a holiday. Similarly, if one falls on a Sunday, then Monday shall be observed as a holiday.
The other six are set by a day of the week and month:
| Martin Luther King's Birthday | Third Monday in January |
| Washington's Birthday | Third Monday in February |
| Memorial Day | Last Monday in May |
| Labor Day | First Monday in September |
| Columbus Day | Second Monday in October |
| Thanksgiving | Fourth Thursday in November |
PLACE OF PERFORMANCE
Tasks under this PWS shall be performed at Contractor facilities. The Contractor shall identify the Contractor’s place of performance in their proposal submission.
TRAVEL
The Contractor must plan for up to four annual trips to meet with the program office for team meetings. Each trip is anticipated to last no more than two consecutive days. Meeting locations shall be designated by the Contracting Officer’s Representative (COR) or Program Manager (PM) and remain within the continental US. All travel costs shall be at the Contractor’s expense and shall not be separately billable to the VA.
All work must adhere to federal holiday restrictions unless specifically authorized by the Contracting Officer.
Travel shall be in accordance with the Federal Travel Regulations (FTR) and requires advanced concurrence by the COR.
PROJECT MANAGEMENT
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 Program Manager (PM) approved CPMP throughout the PoP.
Deliverable:
A. Contractor Project Management Plan
Kick-Off Meeting The Contractor will coordinate and conduct the kick-off meeting, provide the meeting agenda, present the planned approach and work plan, and update the presentation following the discussion. Additionally, the Contractor will support the production of meeting minutes.
Deliverables:
A. Kickoff Meeting Agenda B. Kickoff Meeting Minutes
Reporting Requirements Weekly progress reports The Contractor shall provide weekly progress reports that outline the work completed, the work planned for the upcoming period, any issues encountered along with their resolutions, and plans for addressing any unresolved issues.
Deliverables:
· Weekly Progress Report
Monthly Delivery and Monitoring Report and Roster The Contractor shall provide a single monthly report, detailing and providing links to all stories, epics, and other work completed in accordance with Base Contract paragraph 5.2.4. This includes a plain language description of all work accepted by the Government Product Owner and COR at the end of each sprint. This report shall include, in plain language, additional details about the project status, sprint team velocity, sprint team goal completion, and highlight project risks. The report shall also highlight and provide links to key infrastructure and application monitoring data. The report shall also include details with links to documentation for any critical incidents or outage events that resulted in service outages or significant service degradations. The Contractor shall attach or provide links to postmortem documentation for all critical incidents or outage events. Should there not be any reported incidents during the reporting period, a link to the relevant monitoring tools is sufficient. The specific data points and format of this monthly report shall be determined by the Contractor in collaboration with the Government Product Owner and COR. Additionally, the Contractor shall submit a roster as part of the Delivery and Monitoring Report and Roster including a Status of all Government Furnished Equipment (GFE). The Delivery and Monitoring Report and Roster shall be uploaded to a VA provided SharePoint.
Deliverables:
· Delivery and Monitoring Report and Roster (Monthly)
Documentation Updates Update all VA-required documentation annually or as required, including: System Security Plan (SSP), Configuration Management Plan (CMP), Disaster Recovery Plan (DRP), Incident Response Plan (IRP), Information System Contingency Plan (ISCP), Interconnection Security Agreement/Memorandum of Understanding (ISA/MOU), Privacy Impact Assessment (PIA), Privacy Threshold Analysis (PTA), Risk Assessment, Nessus Vulnerability Scan, Web Application Security Assessment/Mobile Application Security Assessment (WASA/MASA), Penetration Test (Pentest), Security Design Review (SDR), Quarterly Compliance Review (QCR), Significant Change Request (SCR), Security Control Assessment (SCA), etc)
Technical Documentation Expansion
The Contractor must maintain and deliver comprehensive documentation at each release, at contract completion, during transition-out activities, and whenever requested by the VA. This documentation must include system architecture, security architecture, infrastructure architecture, the database schema, a complete data dictionary, entity relationship diagrams and data flow diagrams, API and external integration documentation, CI/CD documentation, architectural decision records, runbooks, operations manuals, test documentation, and release notes.
Requirements Development and Approval The Contractor shall support the development, refinement, and documentation of functional and non-functional requirements in collaboration with the VA Product Owner and relevant stakeholders. All changes; stakeholder-driven changes, compliance updates and integration requirements are implemented as needed to align with evolving VA policy, enterprise architectures, and system dependencies, ensuring the solution remain current, interoperable, and responsive to mission needs. All new or modified requirements shall be documented and maintained in VA-accessible Jira project(s) or VA required Program Management Software with VA personnel (including but not limited to the Product Owner and COR) granted and maintaining full, continuous read/write access at all times throughout the period of performance. The Contractor shall not host, migrate, or maintain requirements, backlog items, or associated artifacts in any Jira instance, project, or workspace to which VA personnel do not have direct, persistent access.
All requirements shall require review and approval by the Product Owner prior to inclusion in a sprint goal or sprint backlog. The Contractor shall ensure requirements are sufficiently detailed, testable, and traceable to support development, testing, and acceptance activities.
Upon contract expiration, termination, or transition to a successor contractor, the Contractor shall ensure VA retains full and unimpeded access to all Jira projects, requirements, backlog items, and associated historical data, and shall not take any action that restricts, revokes, or degrades VA's access at any point during or after the period of performance.
Defect Resolution and Hotfixes The Contractor shall triage all identified defects according to severity in coordination with the Product Owner and VA Stakeholders. Defects classified as critical or high-severity, including those impacting system availability, data integrity, security, or Veteran-facing functionality, shall be addressed on an expedited basis outside of the standard sprint cycle as necessary to restore operations or mitigate risk.
The Contractor shall be authorized to deploy a hotfix only when no COR/Product Owner acceptable workaround approved by the VA exists and the underlying defect is critical in nature. Where a COR/Product Owner acceptable workaround is available, or the defect does not rise to critical severity, the Contractor shall address the defect through the standard sprint release cycle rather than an emergency hotfix. The Contractor shall document, for each proposed hotfix, the justification for emergency deployment, including confirmation that no workaround was available/approved by the COR/Product Owner or that the defect was critical in nature.
All hotfixes shall be documented, including root cause, remediation steps, and validation testing performed; this documentation shall be incorporated into the system documentation and configuration records, with the Technical Writing function defined in Section 5.2 responsible for maintaining the resulting records.
VETRIDE SCHEDULING SOFTWARE SYSTEM
The VetRide Scheduling Software System shall deliver all functionality described within this PWS. The system currently supports over 20,000+ users without degradation and must support at least 15,000+ concurrent users across multiple VAMCs without degradation. Licensing for the VetRide system shall be an enterprise-wide license with no user limitations at additional cost.
The solution must accommodate VTP Program Office approval processes. Routing capabilities shall include interactive routing and rerouting, advanced waypoint matrix calculations, multi-vehicle optimization, time and location clustering, and real-time route adjustments that support immediate driver notification. Vehicle suitability rules for Common Carrier and SMT must be incorporated.
Additional clarification requests highlight the need to determine specific scheduling workflows used across outpatient, specialty clinics, community care, ambulance services, wheelchair transportation, and shuttle operations. Further details are required to document VAMC-specific business rules, user roles, supported trip types, conflict-prevention mechanisms, minimum wait-time rules, and integration with VA systems such as VistA and Oracle Health. Requirements for API documentation, reporting, analytics, ad hoc reporting needs, dashboards, export formats, transaction volumes, authentication methods, protection of sensitive PII and PHI, and hosting requirements in the VA Enterprise Cloud must be confirmed. Infrastructure-as-Code requirements, provisioning processes, and migration support must also be documented.
Highly Rural Transportation Grants (HRTG) Portal/Users The HRTG Portal shall allow organizations to track, manage, and report transportation services delivered to Veterans in highly rural areas.
Core Features The portal must support secure organization-specific authentication methods. It shall provide detailed trip logging with start and end times, routes taken, and the Veteran’s served. Metrics tracking shall include time and funds expended, trips completed, distances traveled, Veterans served, and all locations visited. The application must include capabilities for quarterly narrative reports and annual Federal Financial Reports. Reporting and analytics shall offer dashboards, exportable reports, filter options, and automated FFR generation. Push-based notifications and alerts must support assignment updates and deadline reminders.
User Experience Drivers shall have streamlined interfaces for rapid logging of trip details, while coordinators and administrators shall have efficient workflows for scheduling, dashboard review, and exporting FFR-related documentation. User experience design shall account for the distinct roles and access levels of drivers, coordinators, and administrators, consistent with the role-based access requirements needed. Testing &
Quality Assurance Unit testing, integration testing, UI testing, and complete performance and security validation are required. User Acceptance Testing (UAT) shall be conducted in the Pre-Production Environment consistent with Sections 5.2.3.1 and 5.2.3.2, with results documented and subject to Product Owner sign-off prior to production deployment. Following production deployment, Production Verification Testing (PVT) shall be performed to validate that the deployed production environment and release match what was approved during UAT, with results documented and provided to the COR and/or Product Owner. Any discrepancies identified during PVT shall be triaged and addressed consistent with the defect resolution and hotfix procedures defined in Section 5.2.3.3.
Deployment & Support
Deployment must support ongoing updates, and sustained maintenance. HRTG organizations cannot use VA-internal systems such as the Admin Portal, as their staff are not VA employees; the solution's architecture and access controls shall account for this distinction to ensure HRTG users do not require or receive VA-internal system credentials or access.
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-4, VA Handbook 6500, and VA IAM enterprise requirements for direct, assertion based authentication, and/or trust based authentication, as determined by the ETGs. Direct authentication at a minimum must include Public Key Infrastructure (PKI) based authentication supportive of PIV card and/or Common Access Card (CAC), as determined by the business need.
The Contractor shall ensure all Contractor delivered applications and systems conform to the specific Identity and Access Management PIV requirements set forth in the Office of Management and Budget (OMB) Memoranda M-05-24, M-19-17, M-22-09, and NIST Federal Information Processing Standard (FIPS) 201-3. Contractor delivered applications and systems shall be on the FIPS 201 Approved Product List (APL). If the Contractor delivered application and system is not on the APL, the Contractor shall be responsible for taking the application and system through the FIPS 201 Evaluation Program.
The Contractor shall ensure all Contractor delivered applications and systems support:
1. Automated provisioning and are able to use enterprise provisioning service.
2. Interfacing with VA’s Master Person Index (MPI) to provision identity attributes, if the solution relies on VA user identities. MPI is the authoritative source for VA user identity data.
3. The VA defined unique identity (Secure Identifier [SEC ID] / Integrated Control Number [ICN]).
4. Multiple authenticators for a given identity and authenticators at every Authenticator Assurance Level (AAL) appropriate for the solution.
5. Identity proofing for each Identity Assurance Level (IAL) appropriate for the solution.
6. Federation for each Federation Assurance Level (FAL) appropriate for the solution, if applicable.
7. Two-factor authentication (2FA) through an applicable Technology Guideline as outlined in VA ETG.
8. A Security Assertion Markup Language (SAML) implementation if the solution relies on assertion-based authentication. Additional assertion implementations, besides the required SAML assertion, may be provided as long as they are compliant with NIST SP 800-63-4 guidelines.
9. Authentication/account binding based on trusted Hypertext Transfer Protocol (HTTP) headers if the solution relies on Trust based authentication.
10. Role Based Access Control.
11. Auditing and reporting capabilities.
12. Compliance with VIEWS 00155984, PIV Logical Access Policy Clarification https://www.voa.va.gov/DocumentView.aspx?DocumentID=4896.
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 11, Edge (Chromium based), and 365 Apps for enterprise. Applications delivered to VA and intended to be deployed to 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 historical Authority to Operate (ATO) status of all VA Information Systems prior to migrating to ServiceNow Continuous Authorization and Monitoring (SNowCAM) until it is determined the migration is completed and eMASS is sunset. eMASS contains the historical Authority to Operate (ATO) status of all VA Information Systems prior to September 30, 2025, with all status provided through SNowCAM once migration is completed.
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.
SOFTWARE AND LICENSING REQUIREMENTS
The Contractor shall be responsible for the provision of all software licenses and any associated licensing maintenance required for any development, delivery, integration, operation, and/or maintenance associated with its proposed application(s), software products, software solution, and/or system including, but not limited to, any and all application(s), software and/or…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .