ATTACHMENT D - CONTRACTOR QUESTIONS w GOVERNMENT RESPONSES 0001.xlsx
XLSX spreadsheet 25 KB Posted
- Solicitation number
- 36C10X26R0016
About this file
This file is a Contractor Questions and Government Responses document addressing 18 clarifications submitted by potential offerors regarding solicitation 36C10X26R0016 for rideshare transportation services supporting Veterans enrolled in the Veterans Health Administration (VHA) Homeless Programs.
The Government clarified several key requirements: the contract is a new procurement established under Section 403 of the Elizabeth Dole Act and will not be separated by geographic area despite requests to establish American Samoa as a distinct requirement; offerors must submit enterprise-wide proposals covering all 50 states, District of Columbia, and U.S. territories (Puerto Rico, Northern Mariana Islands, American Samoa, Guam, U.S. Virgin Islands); the VA estimates 30,000 rides per month across the entire enterprise, with VISN 21 (VA Pacific Islands Healthcare System), VISN 8, and VISN 16 projected as high utilizers; expedited rides (CLIN 0001AB) are those requested with fewer than three business days' notice, while standard rides (CLIN 0001AA) require three or more business days' notice; the 7-day platform access requirement following contract award cannot be adjusted for VA Authority to Operate (ATO) processing, though existing FedRAMP-authorized or VA ATO-cleared platforms may be used if they meet all functional and security requirements; taxi and car-service options may satisfy the two-provider comparison requirement in areas with fewer than two rideshare providers; the Not-to-Exceed ceiling for CLIN 0001 is $12,240,000, and services will pause if costs reach this limit without a Government modification; and payment of properly submitted monthly invoices, including transportation costs, is anticipated within 30 days in accordance with the Prompt Payment Act with no requirement for contractor financing beyond the standard monthly cycle. The Government also confirmed it does not anticipate identifying specific labor categories subject to Service Contract Labor Standards and that subcontracting decisions remain at the prime contractor's discretion.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| S06 36C10X26R0016 0001.pdf | ||
| ATTACHMENT C - PAST PERFORMANCE QUESTIONNAIRE.pdf | ||
| S02 36C10X26R0016 Final.pdf | ||
| ATTACHMENT B - PAST PERFORMANCE REFERENCES.pdf | ||
| ATTACHMENT A - PRICE SCHEDULE.xlsx | XLSX spreadsheet | |
| ATTACHMENT D - CONTRACTOR QUESTIONS.xlsx | XLSX spreadsheet |
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
Sheet1
| # | Section Header/Page | Contractor Questions | Government Response |
| 1 | We would like to know if this is a brand new contract OR if there is (was) an incumbent performing these services. If not brand new, could you please provide the current / previous contract number? | This contract is a new procurement established to fulfill the requirements outlined in Section 403 of the Elizabeth Dole Act for rideshare services supporting homeless Veterans. Although a similar effort existed under the COVID‑era authorities in Section 4201, that contract is distinct and governed by different parameters. As such, this solicitation represents a new requirement, and no prior contract number applies to the services described for this solicitation. | |
| 2 | Will the VA consider amending the solicitation to establish American Samoa as a separate geographic service area or CLIN? | The VA is not considering amending the solicitation to separate service areas at this time. | |
| 3 | May Prime submit a technical and price proposal limited to services performed in American Samoa? | Offerors must propose for the entire enterprise-wide requirement. Submitting a proposal limited to only American Samoa would be considered incomplete and may not meet the solicitation’s requirements. | |
| 4 | If the VA determines that American Samoa constitutes a distinct requirement and the applicable acquisition conditions are satisfied, will the VA consider an SDVOSB sole-source award to Prime under VAAR 819.7008 and the Veterans First Contracting Program? | VA is not considering American Samoa as a distinct requirement. Accordingly, an SDVOSB sole‑source award under VAAR 819.7008 is not under consideration. The requirement will continue to be solicited and evaluated as part of the enterprise‑wide scope. | |
| 5 | Alternatively, will the VA consider another authorized acquisition method that recognizes Prime’s SDVOSB and HUBZone certifications and unique local capability? | VA is not considering alternative acquisition methods for this requirement. The solicitation will continue to be competed under the current enterprise‑wide SDVOSB set‑aside structure, and no separate or modified approach based on individual certifications or localized capabilities is being contemplated at this time. | |
| 6 | If a separate prime contract is not available, will the VA require or strongly encourage the nationwide contractor to partner with a qualified, locally based American Samoa SDVOSB to manage services within the territory? | Subcontracting decisions remain at the discretion of the prime contractor, subject to applicable subcontracting and performance requirements established in the solicitation. | |
| 7 | Can the VA provide the estimated annual number of standard and expedited rides, historical ride volume, anticipated pickup and destination locations, and estimated annual transportation expenditure for American Samoa? | VA does not have historical or estimates for individual communities, however the VA estimates 30,000 ride per month across the entire enterprise. The VA projects VISN 21, which includes the VA Pacific Islands Healthcare System, as a high utilizer. | |
| 8 | Will the VA consider territory-specific alternatives to the electronic-platform requirements where conventional nationwide rideshare applications and transportation-provider networks are unavailable? | VA is not considering territory‑specific alternatives to the electronic‑platform requirements. Offerors are expected to meet all solicitation requirements as written, including the use of the designated electronic platforms, regardless of geographic location. | |
| 9 | PWS 6.1 (p.7-8); Delivery Schedule (p.12) | Platform Authority to Operate (ATO) Timeline. PWS 6.1 requires the contractor's secure electronic interface platform to obtain a VA ATO (and FedRAMP authorization if cloud-hosted), while the Delivery Schedule requires platform access within 7 days of contract award. Given standard VA ATO processing timelines, will the Government (a) allow conditional platform access pending ATO completion, or (b) adjust the 7-day deliverable to align with the ATO process? Please clarify the expected sequence. | Due to the required implementation timeline, the Government is unable to permit conditional platform access prior to ATO completion and cannot adjust the 7‑day deliverable. Contractors should plan to meet the established requirements as stated in the PWS and Delivery Schedule. |
| 10 | PWS 6.1 (p.7-8) | Use of Existing Authorized Platforms. Would a commercially available rideshare coordination platform that already holds FedRAMP authorization and/or an existing VA ATO satisfy the PWS 6.1 platform requirement, provided all functional and security requirements are met? | A commercially available rideshare coordination platform that already holds a valid FedRAMP authorization and/or an existing VA ATO may be used, provided it fully meets all functional, security, and performance requirements outlined in PWS 6.1. The Government will still require verification that the existing authorizations remain current and applicable to the specific solution being proposed. |
| 11 | B.3 Price/Cost Schedule (p.26); C.2 (i)(1)(ii)(D) (p.33) | Definition of "Expedited Ride" (CLIN 0001AB). Please confirm that CLIN 0001AB applies to rides requested with less than three (3) business days' notice, and that CLIN 0001AA applies to all rides requested with three or more business days' notice. Are there additional criteria distinguishing the two CLINs? | That is correct. SLIN 0001AB applies to rides requested with fewer than three business days’ notice, while SLIN 0001AA applies to rides requested with three or more business days’ notice. There are no additional criteria distinguishing the two CLINs. |
| 12 | PWS 2 Scope item (i) (p.6); PWS 6.2 (p.8) | Taxi/Car-Service in Comparative Analysis. PWS Scope item (i) directs the contractor to develop agreements enabling access to a broad network of rideshare, taxi, and car-service options, while PWS 6.2 requires comparing at least two commercially available "rideshare providers." Please confirm whether taxi and car-service options satisfy the two-provider comparison requirement, particularly in geographic areas (rural locations, U.S. territories) where fewer than two rideshare providers operate. | Yes. Taxi and car‑service options may be used to satisfy the two‑provider comparison requirement when fewer than two commercially available rideshare providers operate in a given area, including rural locations or U.S. territories. The key requirement is that the contractor demonstrates a comparative analysis between at least two viable transportation options that meet all PWS functional and security requirements. |
| 13 | 52.222-41; 52.222-49; E.1 Addendum A.4 (p.48) | Service Contract Labor Standards Applicability. Please confirm which labor categories, if any, the Government anticipates being subject to SCA wage determinations under this contract, given that transportation is performed by third-party commercial rideshare drivers billed as ODCs and contractor personnel perform coordination, support, and administrative functions. | VA does not anticipate identifying specific labor categories as subject to the Service Contract Labor Standards for this requirement. Transportation services are performed by third‑party commercial rideshare providers, while contractor personnel perform coordination and administrative functions. It is the contractor’s responsibility to determine the applicability of SCA labor categories based on its proposed staffing and approach. |
| 14 | B.3 Price/Cost Schedule (p.26); PWS 6.5 (p.9-10) | Ride Volume Distribution. Can the Government provide historical or estimated ride volume distribution by VISN and/or an urban/rural split? This information materially affects staffing, support coverage, and comparative pricing feasibility. | VA does not have access to historical data to provide specific breakdowns or volume by VISN/communities, however the VA estimates the highest volumes to be within VISN 8, 21, and 16. |
| 15 | B.3 CLIN 0001 (p.26); C.2 (i)(2)-(3) (p.33) | NTE Ceiling Administration. If actual ride costs approach the $12,240,000 Not-to-Exceed amount for CLIN 0001 before the end of the base period, please confirm the contractor's obligation is limited to notification in accordance with FAR 52.212-4 Alternate I paragraphs (i)(2) and (i)(3), and that services pause absent a Government-issued ceiling increase. | The contractor’s obligations regarding the Not‑to‑Exceed ceiling are limited to the notification requirements described in FAR 52.212‑4 Alternate I, paragraphs (i)(2) and (i)(3). Should actual ride costs reach the established ceiling, performance will pause unless and until the Government issues a modification increasing the ceiling. |
| 16 | E.1 Addendum b. Volume II (p.51); E.2 para 3 (p.54) | Past Performance Relevance. Will the Government consider past performance in closely related transportation coordination services (e.g., federal medical courier and patient transport contracts) as relevant under the size/scope/complexity determination, or is relevance limited strictly to rideshare brokerage services? | VA will evaluate past performance in accordance with the criteria set forth in the solicitation. Closely related transportation coordination efforts may be considered relevant when comparable in size, scope, and complexity. However, past performance directly aligned with rideshare brokerage services will be most indicative of the required capability and therefore most strongly weighted. |
| 17 | B.1 para 3 (p.3); PWS 6.7 (p.11); C.2 (i) (p.31-33) | Payment Timing for Transportation ODCs. The contractor must pay transportation providers at the time of service but invoices the Government monthly in arrears. Please confirm that (a) properly submitted monthly invoices, including transportation ODCs, will be paid within thirty (30) days in accordance with the Prompt Payment Act, and (b) the Government anticipates no requirement for contractor financing of ride costs beyond the standard monthly invoice cycle. If payment beyond Net-30 is anticipated, please advise so offerors may account for carrying costs in the proposed administrative fee. | VA anticipates that properly submitted monthly invoices, including transportation ODCs, will be processed in accordance with the Prompt Payment Act’s Net‑30 requirements. The Government does not anticipate any requirement for the contractor to finance ride costs beyond the standard monthly invoice cycle. If circumstances arise that would result in payment beyond Net‑30, the Government would communicate that requirement so offerors may account for any associated carrying costs in their proposed administrative fee. |
| 18 | E.1 Addendum A.8 Volume table (p.50); Attachments B & C (p.45) | Volume II File Naming. The proposal submission table specifies the Volume II file name as "[Offeror Name] Attachment C Perf.pdf"; however, Volume II content consists of Attachment B (Past Performance References), while Attachment C Past Performance Questionnaires are submitted directly by references to the Contracting Officer. Please confirm the intended Volume II file name and contents. | Offerors may submit Attachment B as Attachment B Perf.pdf |
| 19 | |||
| 20 | |||
| 21 | |||
| 22 | |||
| 23 | |||
| 24 | |||
| 25 | |||
| 26 | |||
| 27 | |||
| 28 | |||
| 29 | |||
| 30 | |||
| 31 | |||
| 32 | |||
| 33 | |||
| 34 | |||
| 35 | |||
| 36 | |||
| 37 | |||
| 38 | |||
| 39 | |||
| 40 | |||
| 41 | |||
| 42 | |||
| 43 | |||
| 44 | |||
| 45 | |||
| 46 | |||
| 47 | |||
| 48 | |||
| 49 | |||
| 50 | |||
| 51 | |||
| 52 | |||
| 53 | |||
| 54 | |||
| 55 | |||
| 56 | |||
| 57 | |||
| 58 | |||
| 59 | |||
| 60 | |||
| 61 | |||
| 62 | |||
| 63 | |||
| 64 | |||
| 65 | |||
| 66 | |||
| 67 | |||
| 68 | |||
| 69 | |||
| 70 | |||
| 71 | |||
| 72 | |||
| 73 | |||
| 74 | |||
| 75 | |||
| 76 | |||
| 77 | |||
| 78 | |||
| 79 | |||
| 80 | |||
| 81 | |||
| 82 | |||
| 83 | |||
| 84 | |||
| 85 | |||
| 86 | |||
| 87 | |||
| 88 | |||
| 89 | |||
| 90 | |||
| 91 | |||
| 92 | |||
| 93 | |||
| 94 | |||
| 95 | |||
| 96 | |||
| 97 | |||
| 98 | |||
| 99 | |||
| 100 |
File details come from the government source that posted it. Updated .