47QMCA26N0077.Q.A.Matrix.Gov. Resp.2026.10.01pdf.pdf

Question Matrix

Question

Question # Section/Paragraph and page number Reference. Question Government Response

1 Section 4.a, page 3

Will GSA provide a current list of toll authorities, interoperability networks, facilities, and transaction volumes by authority that must be supported at launch?

GSA can provide an approximate list of toll authorities and volumes that must be supported at launch but it will not be complete. GSA is looking for the selected vendor to advise on interoperability network approaches. GSA will likely roll out in a phased approach.

2 Section 3, page 3 Does GSA expect the contractor to supply and own transponders, or may devices remain authority-issued and authority-owned?

GSA is open to a device-less offering but if the contractor was to provide devices. GSA does not expect or prefer the contractor to own transponders. GSA would prefer to own them, or have our customer agencies own them.

3 Section 4.h.i, page 4 Which Fleet Charge Card program, issuer, processing network, settlement process, and transaction controls must the solution support?

4 Section 4.d.ii, page 4

Do disputes need to be submitted directly from the contractor portal to each authority, or is case management and evidence tracking sufficient where an authority lacks an interface?

GSA prefers a vendor that can do both but would prefer direct API/portal integration wherever available which is vastly superior to simple case management.

5 Section 5, page 4 What channels, languages, hours, staffing locations, accessibility requirements, and target service levels are anticipated?

6 Section 6, pages 4 to 5 What federal security impact level and authorization approach does GSA anticipate, and will an agency authorization be considered?

The ideal vendor will aggregate toll authority data by plate and pass transactions directly to GSA's secure internal network via encrypted SFTP or API. Ideally, the vendor does not store or host agency fleet data or PII on vendor-managed cloud environments. It is prefered that any software components provided are deployable within the agency's own pre-authorized IT infrastructure to negate the requirement for external FedRAMP authorization.

7 Section 6.g, page 5 Which interfaces and deliverables require Section 508 conformance, and will GSA require a current Accessibility Conformance Report?

WEX, Inc. is GSA's Fleet Charge card provider. GSA Fleet Management Regulations, tolls are explicitly excluded from GSA Fleet lease rates and cannot be charged to a GSA Fleet card. The contractor will likely be required to invoice the GSA Finance Office through the Department of Treasury’s, Invoice Processing Platform (IPP) web portal, https://ipp.for.fiscal.treasury.gov/ and then click on “Collector (Supplier).” GSA is open to other solutions if they allow GSA to

We will require tolling coverage over the contiguous United states. GSA is seeking a support team that can assist GSA in the management of the program and provide a response time within GSA's 10 person program management team within 24 hours. Contractors are not anticipated to interact with GSA's federal agency customers. When federal agencies buy, build, maintain, or use Information and Communication Technology (ICT), Section 508 of the Rehabilitation Act of 1973 requires that agencies must provide people with disabilities access to information

The following interfaces and deliverables require Section 508 Conformance: Websites and web applications used by employees or the public; Software and mobile apps delivered or used under federal contracts; Electronic documents including PDFs, Word documents, spreadsheets, and

8 Section 7.b, page 5

Can GSA provide annual toll transaction counts, transponder quantities, invoice volumes, violation volumes, payment volumes, and historical customer-service contacts for pricing?

At this time GSA only has numbers for California. San Bernardino County Transportation Authority reported 251 transactions (64 vehicles total) transactions during 2026. The Transportation Corridor Agencies reported 1,023 transactions in 2026 (253 vehicles total).

9 Overview, pages 1 to 2 Should the optional agency-owned fleet be priced as an option, separate ordering pool, or shared service under the same environment?

GSA will likely structure the award as a BPA and use seperate CLINs for different offerings and either allow different pricing by volume or allow for individual agency self ordering.

10 Overview, page 1 Currently GSA works with WEX, Inc. but GSA will not use WEX for this solution.

The solution must handle toll account management/payments on behalf of the vehicle fleet and include license plate or VIN. The contractor will likely be required to invoice the GSA Finance Office through the Department of Treasury’s, Invoice Processing Platform (IPP) web portal, https://ipp.for.fiscal.treasury.gov/ and then click on “Collector (Supplier).” GSA is open to other solutions if they allow GSA to maintain compliant with the Federal Fleet Management Policy guidelines, which required tolling charges to be classified and processed strictly as travel expenses (versus fleet expenses).

11 General

Is there an expected implementation timeline? Is a phased approach an option versus all authorities on day 1? Full authority integration would be expensive and time consuming. A phased approach may make more sense while keeping an aggregated approach for day 1. GSA will take a phased approach to implementing the awarded tolling solution.

12 General Is data conversion required for day 1 operations (historical tolling, device, or fleet data)?

Some GSA customers have little to no oversight into tolling operations.We would like to be able to have visibility and a mechanism for paying past bills from before the start of offering the tolling solution.

13 Overview, O.1

The Overview references more than 230,000 GSA Fleet vehicles and potentially more than 200,000 agency-owned vehicles, but later states the likely populations are approximately 200,000 and 150,000, respectively.

Which vehicle populations should respondents use for capacity planning and indicative pricing?

Respondents should use the latter numbers which takes into account where GSA believes the vehicles are operating and their likelihood of operting in localities with tolls. The numbers may ultimately be even smaller.

Overview, pp. 1-2; 7(d), p.

For agency-owned fleets, does GSA envision optional ordering under a common GSA contract or BPA, separate agency task or delivery orders, or agency-specific agreements? How should agency funding, data segregation, billing, and program governance be structured?

GSA envisions establishing a BPA that GSA can use to place orders. GSA requires aggregation of data at the plate or VIN level to be able to perform agency, sub-agency or other specific billing groupings.

Overview, pp. 1-2; 4(d)(i) and 4(g), p. 4

Should the solution treat GSA Fleet as a single enterprise customer, or support a hierarchical account structure with agency, regional or state, organizational, operational, acquisition, and finnce subaccounts? Please identify the expected segregation of users, approvals, billing, reporting, and data.

GSA Fleet should be treated as a single enterprise customer but the integration must be at the tag or VIN level to allow GSA to break down costs, data and transactions to hierarchal levels (agencies, sub-agencies, licence plate, VIN, billing account code etc.). GSA may also decide to open the BPA to agencies for self-ordering.

16 4(a), p. 3

Does GSA expect production coverage for every U.S. toll authority at initial launch, or may coverage be phased based on actual GSA travel patterns? If phased, will GSA identify prority authorities or networks and the minimum coverage required for launch?

We expect production coverage of the entire U.S. toll authority at the initial launch but if not feasible will work with the selected provider to ensure coverage in areas traveled by pilot agencies/vehicles.

Overview, pp. 1-2;

7(a)-(d), p. 5

Does GSA envision acquiring a fully managed service in which the contractor provides the technology, staffing, and ongoing operations; a technology platform that GSA would staff and operate; or a hybrid model?

If a hybrid model is contemplated, which functions should be contractor-operated versus Government-operated?

We envision a hybrid managed service in which the contractor provides a tolling solution (to potentially include devices) that consolidates toll transactions by vehicle plate or VIN. We will require customer service and account management staff to support customer service needs.

Overview, p. 1; 4(a) and

4(h), pp. 3-4

Does GSA expect the contractor to be the legal toll-account holder and settlement party for all participating authorities, or may the contractor coordinate authority accounts, interoperability hubs, and qualified partners under a single managed-service and consolidated-reporting model?

Ideally, GSA would like the contractor to be the legal toll-account holder and settlement party for all participating authorties.

Overview, p. 1; 7(a)-(b),

p. 5

Should the contractor advance toll payments and carry the associated working-capital -capital exposure until reimbursement, or does GSA anticipate prefunded accounts, direct Government payment, or another settlement arrangement? Please clarify expected billing, funding, and reimbursement timing.

GSA is expecting the contractor to advance toll payments and carry the associated working-capital. This is to reduce the risk of late fees. GSA would expect the contractor to submit monthly invoices and backing files. These invoices are verified, and approved, by GSA.

Once approved, the invoices are processed for payment via the Invoice Processing Platform.

20 3(b)-(f), p. 3

For transponders and related devices, does GSA prefer Government-owned, authority-issued, authority- issued, contractor-provided, or leased hardware? Which party should be responsible for procurement, inventory, shipment, installation support, activation, replacement, transfer, warranty, return, and disposal?

We prefer contractor provided, government owned equipment. The contractor will be responsible for shipment, integration and toll authority management. The government will complete installation, manage inventory and handle disposal.

3(b)-(g), p. 3; Overview,

p. 1

What vehicle classes and special configurations must the solution support, such as passenger vehicles, light or heavy trucks, buses, trailers, specialty vehicles, or armored vehicles? Are there agency-specific mounting, security, plate-management, or device constraints?

The solution should support any of the following subject to U.S. tolls: passenger vehicles, SUVs and vans, light and heavy trucks, buses, box trucks, dump trucks, utility vehicles and specialty vehicles such as refrigerator trucks, ambulances, tractors and trailers. For more information, view GSA's Federal Vehicle Standards and the Federal Fleet report:

https://catalog.gsafleet.gov/public/fvs/vehicle-standards https://www.gsa.gov/policy-regulations/policy/motor-vehicle-management-policy/federal-fleet-re port-ffr

22 4(d)-(f), p. 4

Which GSA fleet-management, billing, financial, identity, and systems-of-record platforms must the solution integrate with? Are interface specifications, APIs, file formats, authentication standards, data volumes, and refresh requirements available for market research?

There must be an intergration with GSA's system of record . An API would be needed to support ingestion, management, and reconciliation of finacial and vehicle-related data.

Specifically, it must enable the secure ingestion on a daily basis. In terms of billing, GSA uses IPP (Interoperable Portability Protocol / Invoicing and Payment Processing) through a three-tier data synchronization architecture that links toll road transactions to the fleet's existing asset database.

23 4(h)(i), p. 4

How does GSA anticipate Fleet Charge Cards will be used: to pay contractor invoices, fund toll accounts, settle individual toll transactions, or support another payment flow? Please identify the applicable payment program and required transaction-level data, reconciliation, and reporting.

Fleet credit cards will not be used as a form of payment. The Contractor will likely be required to submit the invoice to the GSA Finance Office through the Department of Treasury’s, Invoice Processing Platform (IPP) web portal, GSA will need integration in GSA's system of record, , in order to bill our agency customers.

24 4( d)(ii), p. 4

Should the contractor be authorized to submit disputes or protests directly to toll authorities on GSA's behalf? If so, will GSA provide the necessary authorization and decision thresholds, or should disputes be routed to GSA or the participating agency for approval before submission?

The contractor will be authorized to submit disputes or protest directly to the toll authorities on GSA's behalf. GSA will provide clear guidance on authorization and decision thresholds. All disputes should be routed to GSA before request is submitted.

25 5(a)-(b), p. 4

What customer-service operating model should respondents assume for pricing, including required live-agent hours and time zones, 24x7 critical-incident coverage, self-service availability, language requirements, and target service levels or performance measures?

GSA is seeking a support team that can assist GSA in the management of the program and provide a response time within GSA's 10 person program management team within 24 hours.

Contractors are not anticipated to interact with GSA's federal agency customers. English is required.

26 6(a)-(c), pp. 4-5

What security categorization and FedRAMP impact level should respondents assume? Must the proposed application or Saas, underlying cloud environment, and supporting components be within a FedRAMP-authorized boundary at award or production launch, or will GSA consider FedRAMP-authorized infrastructure with a defined

Ideally, the contractor will aggregate toll authority data and pass transactions directly to the agency's secure internal network via encrypted SFTP or API. The vendor must not store or host agency fleet data or PII on vendor-managed cloud environments. Any software components provided must be deployable within the agency's own pre-authorized IT infrastructure to negate the requirement for external FedRAMP authorization.

27 4(f)-(g), p. 4

What data classification, retention schedule, records-management, residency, audit, export or portability, and post-termination deletion requirements should respondents assume for fleet, transaction, image or evidence, payment, and customer-service data?

28 Industry Day Do you plan to include tolling for Short Term Rental units? We can help with that too!

Undecided at this time. Currently GSA's rental providers manage tolling. As tolls are used and incurred, the tolling authority bills the rental provider directly and they submit a bill/claim to GSA. We review and remit payment to the vendor, which triggers a billback to our customer. We do not managed at the vehicle level.

GSAFleet.gov https://ipp.for.fiscal.treasury.gov/.

GSAFleet.gov

Assume no data may be deleted or retained outside agency direction. GSA will provide or approve the controlling records schedule, legal-hold instructions, privacy requirements, and disposition authority.

29 Industry Day Will there be a contact center requirement for end user support?

GSA will require the awarded contractor provides customer support -- at the very least supporting the GSA team managing this offering.

30 Industry Day Will this new GSA contract superceed current agency-direct contracts for toll services? Or will their current contracts run to expiration? Agencies will have an option to opt out of GSA Fleet's Toll Management solution.

31 Industry Day Are you looking to have only 1 universal tag across all 50 states (pass that covers Ezpass, sunpass, etc)

32 Industry Day Will this contract include a Hybrid approach to transponders IE. order trasponders for certain situations

Yes, we expect to take a hybrid approach. While we prefer our vehicles to be managed without a device but we understand that there will be some cases, in the interest of the customer, or in certain geographic locations, where a device is needed.

33 Industry Day Will the contract include citation/violations processing for all GSA plates?

Or only for enrolled vehicles in toll services?

We primarily are focused on toll violations, but we will likely include an optional CLIN for citation and violation processing.

34 Industry Day What is the anticipated go-live date for the pilot portion of the fleet? The go-live date for a pilot would be shortly after the future solicitation is awared.

35 Industry Day Do you know which month this fall the solicitation is expected to be released, and what the submission due date will be? Not at this time.

We are looking for the most cost effective and efficient means of managing our entire fleet, spanning the continguous United States. Some of our vehicles will likely require devices and others will not. If using a single tag per vehicle is the best solution, that is the approach we would like to take

36 Industry Day In our future solicition, we will ask each offeror to include the process, including the data requirements, for registering federal plates through the selected provider.

37 Email

GSA plans to issue a statement of objectives rather than a statement of work, partly to empower vendors to use their expertise to propose creative, cost-effective, or technically superior methods.

If transponder-based is more ecost-effective, we encourage the vendor to share that in their response.

38 Email GSA will likely not enroll all vehicles in toll services. GSA anticipates enrolling vehicles in toll violation/citation mitigation services as well which will likely be a seperate CLIN.

Follow up to my question for covering citations and violations across all GSA vehicles versus only vehicles “enrolled” in toll management services.

A registration plate can only be added to one account for toll coverage at a time. Therefore, if the interest is for coverage of all tolling activity captured by plate imaging (toll-by-plate, transponder misreads, open road tolling, using a transponder-only lane, etc.) then all GSA plates would need to be registered through the selected provider.

This is not necessarily the most cost-effective solution as many agencies offer reduced pricing for transponder-based tolls which frequently results in fleets desiring transponders.

Ultimately, it would need to be decided if the provider is covering all GSA vehicles or only vehicles electing to be enrolled in services. Commonly, this is divided into two different program types – toll management versus toll violation/citation mitigation for complete coverage and cost effectiveness.

Otherwise, GSA will continue to receive the invoices, violations, and/or citations from plate captured transactions as the registered owner of the vehicle, if the vehicle is not registered in a toll program at the agency level.