The file's text, extracted by GovTribe without its formatting.
ADDENDUM NO. 01
PROPOSAL DATE DUE 6/19/2026 - 2:00 PM CST
| Solicitation Number: QE-26-3 |
| Solicitation Name: Computer Aided Dispatch / Automatic Vehicle Location |
Date Addendum Issued : 6/1/2026
AMENDMENT TO THE SOLICITATION - #1
The following sections of the solicitation are amended to read:
1. QE-26-3 RFP - Section 6.1.5 Vendor Provided Equipment
· Any and all cellular data/equipment must be provided by the vendor.
· App J - Manitowoc's Cellcom Contract is included in this procurement for information purposes only. There is no requirement for the vendor to use this contract.
· Multifactor security for hosted cloud content.
2. QE-26-3 RFP - Section 6.4 VII. System Integration
· “Current Onboard Equipment” and “Current CAD/AVL System” includes:
· Sign - Hanover
1. Side – DD044AI1NON5210 Model
2. Front – DD028AI1NON50 Model
· Cameras – Seon
· Speakers – Mobilpage
· Galaxy Tab A7 Lite
Vendor must include a signed copy of this Addendum with their proposal.
Vendor Company Name
Authorized Signature
Date
Above name printed or typewritten
Questions and Answers
| Quest. No. |
| Question |
| Answer |
| 1. |
| Is it possible for you to share the company who supports your existing CAD/AVL system? |
| Current Fleet Management Program is UniteGPS. |
| 2. |
| Is there an estimated project budget ceiling beyond the identified federal participation amount of $240,074? |
| Per section 7.20, “Provide your best pricing”. |
| 3. |
| What are the current daily and peak trip volumes for this fixed route service? |
| Monday through Friday 7am till 5pm, Saturdays from 9am till 3pm. |
| 4. |
| Can MMT clarify whether the implementation experience requirement described in Section 6.1.3 may be satisfied through: |
• comparable fixed-route CAD/AVL and transit ITS deployments,
• subcontractor/teaming partner experience,
• or transit technology implementations that include similar integrations and passenger information functionality, even if Automatic Vehicle Annunciation (AVA) functionality was not deployed as part of every referenced implementation?
All proposers who meet the Minimum Qualifications in section 6.1 will be considered for award.
| 5. |
| Additionally, will MMT consider the overall qualifications, integration capabilities, and demonstrated experience of the proposer and its implementation partners collectively when evaluating compliance with the implementation experience requirements? |
| Yes, evaluation committee will consider the combined qualifications of the proposer and all subcontractors. Please note, the prime is responsible for all subcontractors. MMT’s relationship will only be with the prime vendor. |
| 6. |
| Could MMT provide the number of system users by role (dispatchers, schedulers, call center agents, drivers, administrators)? |
| The current number of system users are: 2 dispatchers/call center agents, 2 schedulers/admins, 1 mechanic, and 18 drivers. |
However, this is subject to change.
| 7. |
| Can MMT provide additional details regarding the current UniteGPS environment, including which specific modules/functions are actively being used today (e.g., routing, GTFS management, fleet tracking, scheduling, dispatching)? |
| Routing and fleet tracking. |
| 8. |
| Does MMT anticipate future expansion of service areas or routes outside the current Manitowoc and Two Rivers service area during the contract term? |
| There are no concrete plans to expand the service area and routes. However, there is a possibility. |
| 9. |
| Does MMT currently maintain fixed-route schedules internally, or does any third-party consultant/software assist with route planning, scheduling, blocking, or run-cutting? |
a. Is the awarded vendor expected to provide any transit planning, route scheduling, blocking, run-cutting, rostering, or timetable development services as part of this procurement?
MMT maintains fixed route schedule. The awarded vendor must implement our current schedule. MMT expects a turn key process.
| 10. |
| Can MMT clarify whether the system must support CAD functionality for ADA paratransit or demand response trips? |
a. Are the Ford Transit and Chrysler Pacifica vehicles used for ADA paratransit, demand response, supervisor support, or another operational purpose?
The system, along with the fixed route, must also support demand response trips.
| 11. |
| Does MMT currently have an existing rider app or passenger information website that must be replaced or integrated? |
a. Does MMT require white-labeled mobile applications under the Maritime Metro Transit branding?
MMT currently manages the rider app through GoodBarber.
| 12. |
| Can MMT confirm the target go-live timeline for this service? |
| Please see section 6.3 for anticipated timeline. |
| 13. |
| What is the approximate volume of Active riders & Historical trip records (beyond the required 2 years)? |
| Approximately 280,000 rides per year |
| 14. |
| Approximately how many MMT will require training per role? |
| Currently, MMT requires 2 admin to be trained on the software and 1 mechanic to be trained on the hardware. |
However, this is subject to change.
| 15. |
| Will the awarded vendor be responsible for migration/import of all current GTFS data into the proposed CAD/AVL system? |
a. Is MMT expecting the awarded system to generate GTFS feeds automatically from service data, or simply manage/export feeds already maintained by MMT staff?
No, see RFP for requirements.
| 16. |
| Will MMT require a dedicated account manager or project manager throughout implementation and operations? |
| No, see RFP for requirements. |
| 17. |
| Is there any cybersecurity, MFA, CJIS, NIST, SOC 2, or other IT security standards required for the hosted cloud environment? |
| Multifactor. Please see amendment 1 for details. |
| 18. |
| Is a train-the-trainer model acceptable in addition to on-site training? |
| Approved. |
| 19. |
| Can you please confirm if the vehicles in the fleet already have existing MDTs which can be reused under this RFP? |
a. If yes, could MMT provide tablet/device specifications (model, OS version, connectivity)?
b. If vendors need to provide new MDTs, please confirm the required hardware specification (Android, iOS and OS) The fleet does not have any MDTs that can be reused.
MMT does not have a preference of an OS, as long as it follows requirements stated in the RFP.
| 20. |
| Can MMT clarify whether cellular modems/SIMs will be vendor-provided or if the City’s existing Cellcom contract and data plans must be utilized? |
| Please see amendment 1 for details. |
| 21. |
| Can MMT clarify whether optional modules/features may be priced separately from mandatory requirements? |
| Provide your best pricing for the RFP requirements. |
| 22. |
| Is MMT expecting all integrations, AVA, public apps, signage, GTFS, and reporting modules to be fully operational by Go-Live? |
| Yes |
| 23. |
| If existing onboard speakers, interior display, public display monitors and sign equipment systems are available, can MMT confirm whether vendors may integrate with those existing systems instead of supplying entirely new speaker/display hardware? |
| Yes |
| 24. |
| Does MMT prefer professionally recorded announcements or synthesized text-to-speech announcements and If professionally recorded audio is preferred, will MMT provide recordings, or is the vendor expected to produce them? |
Please see section 6.5 for requirement.
| 25. |
| Does MMT require exterior announcements for ADA compliance in addition to interior announcements? |
| No |
| 26. |
| Are interior speakers currently installed and operational on all fixed-route buses? |
| Yes, all 9 buses have pre-installed interior speakers that are operational. |
| 27. |
| MMT confirm that there are no DBE participation goals associated with this procurement? |
a. Should the vendor be DBE in WI to participate in this RFP?
b. Can MMT confirm there are no bonding requirements associated with this solicitation?
Please see section 12.4 for information regarding the DBE program.
There is no bonding requirements for this RFP.
| 28. |
| What are MMT’s top success metrics/KPIs for this project in the first year? |
| MMT has no KPI’s. |
| 29. |
| Can you please confirm if the pricing proposal needs to be submitted separately? |
| Please refer to Section 4 and Section 13.5. |
| 30. |
| What are the minimum qualifications for a vendor/company to be considered a valid bidder responding to this RFP? |
a. What is the minimum qualifying score required to advance to the final evaluation?
Please see section 6.1 for minimum qualifications.
| 31. |
| Could MMT extend the submission deadline to allow vendors to submit more detailed and informed proposals? |
| No. |
| 32. |
| Please confirm whether Maritime Metro Transit currently has cellular routers and antennas installed that can be utilized for this project, or if the successful vendor is required to supply these components. |
If existing equipment is available, please provide the make, model, and quantity.
Please see amendment 1 for details.
| 33. |
| The RFP references compliance with the City’s Cellcom contract while also indicating that vendors may need to provide cellular data plans. Please confirm whether the selected vendor is responsible for providing cellular data services. |
| Please see amendment 1 for details. |
| 34. |
| Please confirm the make and model of existing Hanover destination signs and any internal LED next-stop signage that will require integration. |
| Please see amendment 1 for details. |
| 35. |
| Please clarify whether the real-time map display referenced in the RFP is intended only for public-facing displays (e.g., Smart TVs) or if there is any requirement for onboard display within vehicles. |
| Real time map would be for app usage and at transfer center. Onboard display would be for next stop signage. |
| 36. |
| Please confirm which languages are required for the public website, mobile applications, and automated announcements (e.g., English, Spanish, Hmong). |
| The public website, mobile applications, and automated announcements must be available in English, Spanish and Hmong. |
| 37. |
| Will the agency consider solutions that do not include a rider subscription-based “next bus” notification service but meet all other stated requirements? |
| No |
| 38. |
| Will proposals be considered if the system does not currently support on-board multi-language announcements? |
| All proposers who meet the Minimum Qualifications in section 6.1 will be considered for award. |
| 39. |
| Will proposals be considered if the system does not include turn-by-turn navigation on the MDT? |
| All proposers who meet the Minimum Qualifications in section 6.1 will be considered for award. |
| 40. |
| Could you please provide a detailed listing of onboard equipment (routers, fare collection, destination signs, etc.) so that we may include a complete listing of integration capabilities? |
| Please see amendment 1 for details. |
| 41. |
| Public Vehicle Location Displays – Could you please confirm if there are existing displays on board and if so, provide specifications? It would also be helpful to have any pictures of preferred mounting location so that we can quote the applicable mounting hardware. |
| There are no existing displays on board. |
| 42. |
| APC units – could you please confirm the following; Are there APC units currently installed, if so, could you please provide specifications. If new APC units are desired as a possible expansion item, would you like that quoted as an option under the original contract? |
| MMT is not currently looking for APC’s. Please see RFP for requirement. |
| 43. |
| Mobile Data Terminals – Given the integration requirements for on-board systems, do you have a preference between a separate MDT + Vehicle Logic Unit setup (better equipped to handle integrations) as opposed to an all-in-one tablet solution? |
| MMT does not have a preference. Please see RFP for requirements. |
| 44. |
| Would you be interested in an additional, optional contract term for 3 years with 2 one year options to provide maximum flexibility on pricing? |
| No. Please see section 1.2 for Contract Term details. |
| 45. |
| In regard to AVA internal signage and Public Vehicle Location Displays- Can you please clarify if you would like internal LED signage or Infotainment LCD signage on the vehicles? |
| See 6.7 for requirements. |
| 46. |
| Can Maritime Metro Transit clarify the vehicle total? |
| Please see section 1.6 for Estimated Number of Vehicles Quantity. |
| 47. |
| Would you like Automatic Passenger Counting included in the pricing as optional? If so, please specify if these are single of two door vehicles. |
| Per 7.20, “The total cost provided must be all inclusive to carry out the services included in this RFP, in accordance with the terms and conditions of this RFP.” |
| 48. |
| Can MMT expand on what is being asked for in “The public website shall provide a module for allowing content to be provided on MMT’s website”? Is MMT looking to show schedules, routes, real-time vehicle information on the MMT website? |
| Yes. See section 6.4 for requirements. |
| 49. |
| For the smartphone app requirement “Translation of content to other languages” which other languages are preferred/required? |
| The public website, mobile applications, and automated announcements must be available in English, Spanish and Hmong. |
| 50. |
| For “ITS system will allow for future integration with on-demand app (first-mile/last-mile) and/or mobile ticketing app into proposer’s bus tracking app & public website” does MMT have a specific on demand platform and mobile ticketing app in mind? |
| No. |
| 51. |
| For “MMT’s vision includes development of a future enterprise database to organize and manage data from multiple systems. ITS system integration would include a recurring transfer of selected data in a format usable by the enterprise database” what format is usable by the database? |
| A standard spreadsheet application is acceptable for this task. |
| 52. |
| For “System shall provide the ability for Customer to use new or existing flat screen monitors to display a version of the System that requires no user interaction (for example, an LCD/LED screen in a building lobby)” does MMT want the vendor to provide pricing for LCD screens? If so, how many and what size? |
| Per 7.20, “The total cost provided must be all inclusive to carry out the services included in this RFP, in accordance with the terms and conditions of this RFP.” |
Please see section 6.7 for Hardware requirements.
| 53. |
| For the above, does MMT want the vendor to propose a content management system for the LCD screens? |
| Yes. See section 6.4 for requirement. |
| 54. |
| It mentions that the City has a contract with Cellcom and that cell data must be compliant with this. However it is also mentioned that the vendor should include cell data costs in the proposal. Can you please clarify if cell data is needed to be provided in equipment as required from the vendor? |
| Please see amendment 1 for details. |
| 55. |
| Section 6.2 Services / Items Required states working with the implementation of new digital signage. Are there other digital signs procured that need integration with? If so, can MMT please provide the make, model, and integration expected for the digital signs? |
| No. |
| 56. |
| Under section 6.7 - Public Vehicle Location Displays - The RFP mentions next stop signs on each bus - Is MMT looking for infotainment with these signs or just a visual map of the routes for passengers? |
| Both are acceptable. |
| 57. |
| Section 6.4.VII mentions a list of “Current Onboard Equipment”. We were not able to find this in the RFP or provided documentation. Could MMT please point to where that information is? |
| Hanover |
| 58. |
| Will the City provide a comprehensive fleet list, including vehicle information (bus number, make, model year) and model numbers for all existing onboard systems and integration targets on each vehicle (Hanover signs, covert alarm button, etc.)? |
| Yes, at time of contract MMT will provide the detail fleet list. |
| 59. |
| 6.1.5 Vendor Provided Equipment: “Cellular data must to be compliant with City’s cellular and data contract (Currently Cellcom)” – Please clarify: |
1. What specific requirements are necessary for compliance with the City’s current cellular/data contract?
1. Who is the City’s current underlying cellular carrier/provider (e.g., AT&T, Verizon, T-Mobile)?
1. Is the successful proposer expected to provide and manage cellular connectivity hardware/services (including modems and data plans), or will connectivity be provided by the City?
Please see amendment 1 for details.
| 60. |
| 6.4 Detailed Specification: IV. Covert Alarm – Can the City confirm whether the Gillig vehicles are currently equipped with covert alarm systems integrated with the destination sign system? Is the City open to proposers integrating with existing covert alarm functionality through the Gillig CAN bus rather than installing separate covert alarm hardware? |
| Yes, there is a current covert alarm which changes exterior signage on bus only. |
| 61. |
| 6.4 Detailed Specification: V. Automated Voice Announcements (AVA) – Please confirm that AVA functionality is required only on the nine (9) Gillig buses and not on the smaller van vehicles identified in the fleet inventory. |
| Next stop signage is only required for the 9 Gillig buses. |
| 62. |
| 6.4 Detailed Specification: VII. System Integration – This section references “Current Onboard Equipment” and “Current CAD/AVL System” sections in the RFP that appear to have been omitted. Can the City please provide these sections in an addendum? |
| Please see amendment 1 for details. |
| 63. |
| 6.5 Warranty - Industry-standard transit ITS support models often utilize agency maintenance staff for routine field replacement of failed hardware components, with the vendor providing replacement hardware under warranty. Can the City confirm whether the one-year warranty requirement may be satisfied through replacement hardware fulfillment for agency-performed routine component swaps, rather than requiring onsite labor dispatch by the successful proposer for minor hardware replacement activities? |
| The Agency can confirm that the 1 year warranty requirement can be satisfied by routine component swaps. |
| 64. |
| 6.7 Hardware: Public Vehicle Location Displays – Please confirm that this section is primarily referring to public-facing displays/monitors located at facilities such as transit centers or government buildings, rather than additional onboard passenger information displays within vehicles. |
| It covers public facing displays and monitors located at the transfer center or other government facility. |