Attachment_3_Proposer_Questionnaire.docx
DOCX document 69 KB Posted
- Attached to
- EXT ADM | Telematics Services
- Solicitation number
- SFGOV-0000012088
- Issued by
- San Francisco County, California
About this file
Summary of Attachment 3: Proposer Questionnaire and References
This document is a Proposer Questionnaire and References form for Sourcing Event #0000012088, administered by the City and County of San Francisco. The questionnaire requires proposers to provide telematics solutions for fleet management, with specific focus on devices compatible with OBD-II, UDS, and CAN-bus protocols that support 4G/5G/LTE networks and possess FCC certification. Proposers must demonstrate prior experience as project leads deploying a minimum of 1,000 currently active telematics devices across at least two local government projects within the past five years, with at least one California-based project. The RFQ issue date is referenced as September 16, 2026, and proposers must meet various compliance and registration requirements with the City prior to submission, including registration with the San Francisco Supplier Portal, enrollment in Paymode-X for electronic payments, and registration with the San Francisco Treasurer & Tax Collector.
Proposers must attest to multiple technical and operational capabilities, including CARB Clean Truck Check (CTC) eligibility, California Bureau of Automotive Repair Continuous Testing Program (CTP) participation, 99% platform uptime performance, five-year data retention capability, AES-256 encryption, and integration with fleet-related technology platforms such as Bluedot, Epic Charging, PowerFlex, or AssetWorks. The document requires proposers to provide contactable references for each project, documentation of staff qualifications with five years of telematics/fleet deployment experience, API functionality for integration with Snowflake, Web Content Accessibility Guidelines (WCAG) 2.1 AA compliance, and completion of third-party cyber security certifications. Proposers claiming Local Business Enterprise (LBE) preference must be certified in one or more LBE categories by the proposal deadline. The City reserves the right to request reference letters from customers within five days of notification, with failure to provide such documentation resulting in proposal rejection.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Attachment_4_Written_Proposal_Template.docx | DOCX document | |
| RFQ_-_Fleet_Telematics__0000012088.pdf | ||
| EXT_ADM_____Telematics_Services.xml | XML file | |
| Attachment_5_Price_Proposal_Template.xlsx | XLSX spreadsheet | |
| Attachment_2_Scope_of_Work.docx | DOCX document | |
| Attachment_1_City_s_Contract_Terms.docx | DOCX document | |
| EXT_ADM_____Telematics_Services.pdf |
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
Sourcing Event #0000012088
ATTACHMENT 3
Proposer Questionnaire and References Part I Proposer Information Name of Firm:
Headquarter Address:
Phone No.:
Contact Name & Title:
E-mail:
SF Supplier ID:
Federal Tax ID:
Payment Terms:
Person Preparing Proposal:
Local Representative Name and Number:
Warehouse Address:
Contact Information for Placing Orders:
Telephone:
Email:
Website:
24-hour Emergency #:
Part II Proposer Questionnaire
| Question |
| Yes |
| No |
1. Do you certify that you have complied and will continue to comply with Section 7.2 of this RFQ entitled “Limitation on Communications during Solicitation”?
2. Have you registered as a Bidder or Supplier, through the Supplier Portal (https://sfcitypartner.sfgov.org/)?
If yes, what is your Bidder ID or Supplier ID? _________________
3. Has your company enrolled with Paymode-X to receive electronic payments from the City?
https://www.sf.gov/get-paid-your-vendor-services
4. Have you registered your business with the San Francisco Treasurer & Tax Collector as required prior to submission of any Proposal?
Enter your Business Tax Registration ID here: __________________________________
5. Are you claiming LBE preference on this solicitation per Chapter 14B?
To claim LBE preference for this solicitation, you must be certified in one or more LBE certification categories by the Proposals Deadline.
Part III Proposer Checklist and References
All Proposers, including the current Contractor (if any), must provide information as described below. Any Proposer that fails to accurately and thoroughly complete this Attachment 3 will not be eligible for further consideration in the City’s sole discretion.
The City may request further details as part of its evaluation to validate the experience described in this Attachment. Any Proposer who does not provide information requested by the City to demonstrate or validate the experience in this Attachment or as part of the RFQ Evaluation Process, will be eliminated from further consideration for City contract award.
Each Proposer must attest through its responses to this Part III that it has:
| ATTESTATION AREA #1, PRIOR EXPERIENCE AND REFERENCES. |
| Yes |
| No |
Proposer attests that it has delivered and deployed as the project lead and contract signatory a minimum of 1,000 currently active telematics devices each for two local government telematics projects with at least one that is California-based in the last five (5) years from the RFQ issue date.
For each of the projects (see below), Proposer must provide the following information and attestations:
(a) contactable references for verification;
(b) attestation that the Proposer is an approved participant in California Air Resources Board Clean Truck Check (“CARB CTC” or “CTC”) and California Bureau of Automotive Repair Continuous Testing Program for smog checks (“BAR CTP” or “CTP”); AND
(c) attestation that the Proposer has at least one integration example (Bluedot/Epic Charging, PowerFlex, AssetWorks, or other fleet-related technology platforms).
For each of the two required projects, please provide the following information.
| 1. |
| Name of Customer #1 |
Address (street, city, state, zip)
Customer Contact Name
Customer Phone No.
Customer Email
Project Description and Product Type(s)
Proposer’s Role and Responsibilities on Project (Contract Signatory, Project Lead, etc.)
Names of Proposer’s Lead Person and Key Staff on this Project
Dates of Project (start to completion) and Total Years (e.g. Jan 2022 to Feb 2026 = Total 4 years, 1 month)
Total Quantity of Telematics Devices Delivered, Deployed to, and Currently Active for Organization/Company (must be >1,000 units)
For this Project, Proposer attests that it is a CTC/CTP approved participant Yes No
| For this Project, Proposer attests that it has at least one fleet-related technology platform integration such as Bluedot/Epic Charging, PowerFlex, AssetWorks or Other - provide name(s) of platform(s) |
| Yes No |
Name(s) of Platform Integration(s):
| 2. |
| Name of Customer #2 |
Address (street, city, state, zip)
Customer Contact Name
Customer Phone No.
Customer Email
Project Description and Product Type(s)
Proposer’s Role and Responsibilities on Project (Contract Signatory, Project Lead, etc.)
Names of Proposer’s Lead Person and Key Staff on this Project
Dates of Project (start to completion) and Total Years (e.g. Jan 2022 to Feb 2026 = Total 4 years, 1 month)
Total Quantity of Telematics Devices Delivered, Deployed to, and Currently Active for Organization/Company (must be >1,000 units)
For this Project, Proposer attests that it is a CTC/CTP approved participant Yes No
| For this Project, Proposer attests that it has at least one fleet-related technology platform integration such as Bluedot/Epic Charging, PowerFlex, AssetWorks or Other - provide name(s) of platform(s) |
| Yes No |
Name(s) of Platform Integration(s):
Upon request, Proposer(s) may also be required to submit a letter of reference from each customer listed within five (5) days of notification. Failure to do so may result in rejection of proposal.
| ATTESTATION AREA #2, TECHNICAL STANDARDS AND DEVICE SPECIFICATIONS. Proposer attests that its proposed devices: |
| Yes |
| No |
(a) are compatible with OBD-II, UDS, and CAN-bus protocols;
(b) support 4G/5G/LTE networks; AND
(c) have FCC certification.
| ATTESTATION AREA #3, CARB CLEAN TRUCK CHECK (CTC) ELIGIBILITY. Proposer attests that its proposed devices: |
| Yes |
| No |
(a) are CTC‑eligible out‑of‑the‑box;
(b) support continuous OBD emissions monitoring; AND
(c) fully support SAE J1939 and SAE J1979 protocols.
Proposer has provided a link to CARB’s CTC‑approved device listing here: (provide link)
| ATTESTATION AREA #4, BAR CONTINUOUS TESTING PROGRAM (CTP) PARTICIPATION. Proposer attests that its platform: |
| Yes |
| No |
(a) is currently participating in BAR CTP;
(b) supports daily data feeds, VIN validation, and pass/fail reporting to BAR; AND
(c) maintains data integrity sufficient to meet BAR requirements.
Proposer has provided a link to BAR CTP participant listing showing Proposer name here: (provide link)
| ATTESTATION AREA #5, SYSTEM UPTIME, DATA RETENTION & PLATFORM CAPABILITIES, INCLUDING WARRANTY. Proposer attests that its platform: |
| Yes |
| No |
(a) uptime has met or exceeded 99% over the past 12 months for the prior projects referenced in ATTESTATION AREA #1;
(b) supports required data retention period (minimum of 5 years); AND
(c) delivers real‑time GPS, diagnostics, alerts, historical playback, and reporting;
Proposer offers hardware replacement and device health coverage through a warranty.
| ATTESTATION AREA #6, SECURITY & REGULATORY COMPLIANCE. Proposer attests that its platform complies with or maintains: |
| Yes |
| No |
(a) AES-256 data encryption;
(b) HTTPS/TLS 1.2+;
(c) regular penetration testing; AND
Proposer attests that its platform has the capability to toggle on/off privacy mode and to turn off GPS completely.
Proposer attests that its platform is able to provide a structured user access hierarchy that allows different view and/or administration roles for different groups within overall account.
Proposer has completed a third-party cyber security certification (e.g. SOC 2 Type II, FedRAMP, StateRAMP, IS 27001 certificate or similar).
| ATTESTATION AREA #7, INTEGRATION & API READINESS. |
| Yes |
| No |
(a) Proposer attests that its platform provides REST APIs that support vehicle location, engine diagnostics, and event-based alerts;
(b) To allow City integration of APIs with Snowflake, Proposer attests that any APIs are fully functional/implemented.
Proposer has attached a single-page API overview or link to developer portal: attach document or provide a link.
| ATTESTATION AREA #8, PROJECT STAFFING. |
| Yes |
| No |
Proposer attests that both the installation lead and customer support lead (or leads for project implementation and operations) assigned to the work described in the RFQ each have ≥5 years of telematics/fleet deployment experience.
Proposer has attached a 2-page staff summary demonstrating that the experience of the proposed project implementation and operations leads (installation and customer support leads) meet this requirement.
| ATTESTATION AREA #9, PILOT PROGRAM PROJECT PLAN. |
| Yes |
| No |
Proposer attests that it can provide a telematics solution that can provide accurate data collection and proactive notifications for timely decision-making to resolve issues.
Proposer attests that its solution will be designed to include the Pilot Contract Performance requirements described in Section 3.1 of Attachment 2: Scope of Work
| ATTESTATION AREA #10, ACCESSIBILITY. Proposer attests that its platform: |
| Yes |
| No |
(a) conforms to Web Content Accessibility Guidelines (WCAG) 2.1 AA to make its web content accessible to people with disabilities;
(b) provides mobile-friendly UI (responsive interface or mobile app); AND
(c) dashboards are configurable by customer administrator(s) and users.
Proposer has attached or provided a link to a Voluntary Product Accessibility Template (VPAT) summary or a 1‑page accessibility conformance statement.
Proposer has attached a screenshot or provided a link showing dashboard customization capability.
Part IV Proposer Release of Liability for References The undersigned hereby fully and forever release, exonerate, discharge and covenant not to sue the City, its commissions and boards, officers and employees, and all individuals, entities and firms providing information, comments, or conclusions ("Reference Information") in response to inquiries that the City may make regarding the qualifications or experience of a Prime proposer, proposed joint venture partner, proposed subconsultant or proposed key/lead team member in connection with the selection process for Sourcing Event #00000XXXXX from and for any and all claims, causes of action, demands, damages, and any and all liabilities of any kind or description, in law, equity, or otherwise arising out of the provision of said Reference Information. This Release and Waiver is freely given and will be applicable whether or not the responses by said individuals, entities or firms are accurate or not, or made willfully or negligently.
Company Name
Signature of Authorized Representative of Company Date
Print Name and Title
Part V.
Proposer Certification of Truth, Accuracy, and Completeness
I certify that based on information and belief formed after reasonable inquiry, the statements and information contained in this document are true, accurate, and complete. Additionally, by submitting this bid/proposal, I attest that I have reviewed and accepted all terms found in this solicitation, any and all addenda issued to this solicitation, and City’s contract terms.
Company Name
Signature of Authorized Representative of Company Date
Print Name and Title
P-697 (04-26): Attachment 3 Sourcing Event #0000012088 Proposer Questionnaire and References Septebmer 16, 2026 image1.png image2.svg
File details come from the government source that posted it. Updated .