QE-26-3 RFP.docx
DOCX document 183 KB Posted
- Attached to
- City of Manitowoc - Maritime Metro Transit - CAD/AVL Software, Hardware and Professional Services
- Solicitation number
- QE-26-3
- Issued by
- Marquette County, Wisconsin
About this file
Request for Proposal Summary: Computer Aided Dispatch/Automatic Vehicle Location System
This Request for Proposal (RFP QE-26-3) is issued by the City of Manitowoc – Maritime Metro Transit seeking a qualified contractor to provide a comprehensive Computer Aided Dispatch/Automatic Vehicle Location (CAD/AVL) software and hardware system. The solicitation requires the vendor to deliver CAD/AVL software, hardware components including mobile data terminals (MDTs), next-stop LED screens, and public vehicle location displays, and complete installation services for eleven revenue vehicles (nine 35-foot Gilligs buses, one Ford Transit van, and one Chrysler Pacifica van). The RFP was issued on May 13, 2026, with questions due by May 27, 2026 at 2:00 PM CT and proposals due by June 19, 2026 at 2:00 PM CT. Evaluation is estimated to begin June 22, 2026, with evaluations completed by July 10, 2026 and contract award estimated for July 13, 2026. The contract will commence October 1, 2026, with a required beta testing period from November 1 through November 15, 2026, and system go-live by November 30, 2026. One contract will be awarded for a base term of one year with four optional one-year renewal periods, providing potential contract duration of up to five years. The system must be delivered as a turnkey, cloud-based solution with 24/7 support capabilities, comprehensive reporting features, integration with existing equipment, GTFS data management, and automated voice announcements for ADA compliance.
Pricing for the base year must be submitted as a firm-fixed price covering all software, hardware, installation, training, and support costs with no additional expenses beyond the proposal price. Proposers must also submit fixed prices for optional renewal years two through five, with pricing evaluation based on the total cost of the base year and all option years combined. This procurement is partially funded with $240,074 in federal transit operating funds under Section 5311, requiring compliance with federal clauses, Buy America Act provisions, and applicable certifications. The successful contractor must demonstrate minimum qualifications including at least three years of organizational history providing CAD/AVL systems, proven ability to deliver a turnkey product, and successful installation/implementation at a minimum of three public transit systems. Maritime Metro Transit currently operates UniteGPS for routing and fleet management and has no existing CAD/AVL system. Vendor responses must include comprehensive documentation addressing technical specifications, service background, financial stability, insurance coverage, key personnel qualifications, references from at least three similar transit agencies, and acceptance of all standard terms and conditions without modification or negotiation.
View the file
Other files
Show all 13
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
REQUEST FOR PROPOSAL
COVER SHEET
Maritime Metro Transit
SOLICITATION NUMBER (must be included on all proposal documents that are submitted)
QE-26-3
THIS SOLICITATION CLOSES ON
6/19/2026 at 2 PM CT
Proposals must be submitted by this date and time. Late PROPOSALS or offers will not be accepted.
SUBMIT PROPOSALS/OFFERS TO
sbirr@manitowocwi.gov
FOR INFORMATION ON THIS PROCUREMENT, CONTACT
Kevin Bottesi kbottesi@manitowocwi.gov
ITEMS OR SERVICES TO BE PURCHASED
Computer Aided Dispatch / Automatic Vehicle Location
SIGNIFICANT EVENTS/DATES
ISSUE DATE
5/13/2026
LAST DAY TO SUBMIT QUESTIONS
5/27/2026 at 2 PM CT
PROPOSAL CLOSING DATE
6/19/2026 at 2 PM CT
EVALUATIONS BEGIN (Estimated)
6/22/2026
EVALUATIONS COMPLETED (Estimated)
7/10/2026
ESTIMATED CONTRACT AWARD DATE
7/13/2026
ESTIMATED CONTRACT START DATE
10/1/2026
There will not be a public opening for this RFP
REQUEST FOR PROPOSALS
Goods and Services
| Issued By |
| City of Manitowoc |
| Date Issued |
| 5/13/2026 |
| Proposals must be submitted no later than |
| 6/19/2026 at 2 PM CT |
· Late PROPOSALS will be rejected. PROPOSALS MUST be date and time stamped by the soliciting purchasing office on or before the date and time that the Proposal is due.
· PROPOSALS dated and time stamped in another office will be rejected. Receipt of a Proposal by the mail system does not constitute receipt of a Proposal by the purchasing office.
· Any Proposal which is inadvertently opened as a result of not being properly and clearly marked is subject to rejection. PROPOSALS must be submitted separately, i.e., not included with sample packages or other PROPOSALS.
· Records will be available for public inspection after issuance of the notice of intent to award or the award of the contract.
· Proposer should contact the person named below for an appointment to view the Proposal record. PROPOSALS shall be firm for acceptance for sixty (60) days from date of Proposal opening, unless otherwise noted.
· The attached terms and conditions apply to any subsequent award.
· There will be no public proposal openings
SUBMITTING THE PROPOSAL
Offerors must submit proposals via the following method:
One electronic copy delivered though email sbirr@manitowocwi.gov The submittal must include all required documentation organized and named as detailed in this RFP.
Table of Contents
| 1.0 | GENERAL INFORMATION | 12 |
| 1.1 | General Description | 12 |
| 1.2 | Contract Term | 12 |
| 1.3 | Number of Contracts | 12 |
| 1.4 | Procurement Manager | 12 |
| 1.5 | Federal Participation | 13 |
| 1.6 | Estimated Number of Vehicles Quantity | 13 |
| 1.7 | Contractor Selection | 13 |
| 1.8 | Contract Term Price Options | 14 |
| 1.9 | Contract Modifications | 14 |
| 1.10 | Completeness and Validity of Offers | 15 |
| 1.11 | Correspondence Related to the Solicitation | 15 |
| 1.12 | Reasonable Accommodations | 15 |
| 1.13 | Wisconsin Public Records Law | 15 |
| 1.14 | Federal Public Records Law | 15 |
| 1.15 | Order of Precedene | 16 |
| 2.0 | PRE-PROPOSAL CONFERENCE | 16 |
| 3.0 | PROPOSAL SCHEDULE | 16 |
| 4.0 | GENERAL PROPOSAL SUBMISSION REQUIREMENTS | 17 |
| 5.0 | Proposal Format | 18 |
| 5.1 | Proposal Format | 18 |
| 5.2 | Cover Letter | 18 |
| 6.0 | Contract Deliverables | 18 |
| 6.1 | Minimum Qualifications | 19 |
| 6.2 | Services / Items Required | 20 |
| 6.3 | Anticipated Timeline | 21 |
| 6.4 | Detailed Specification | 21 |
| 6.5 | Warranty | 32 |
| 6.6 | Training | 32 |
| 6.7 | Hardware | 33 |
| 6.8 | Installation | 35 |
| 7.0 | Proposal Content | 36 |
| 7.1 | Offeror Identification | 36 |
| 7.2 | Offeror’s Legal Status | 36 |
| 7.3 | Chief Executive or Administrator of the Organization | 36 |
| 7.4 | Offeror’s Authorized Representative | 36 |
| 7.5 | Offeror’s Business Function | 36 |
| 7.6 | Minimum Qualifications | 37 |
| 7.7 | Services / Items Required | 37 |
| 7.8 | Timeline | 37 |
| 7.9 | Detailed Specificaiton | 37 |
| 7.10 | Warranty | 37 |
| 7.11 | Training | 37 |
| 7.12 | Hardware | 37 |
| 7.13 | Installation | 37 |
| 7.14 | Service Background | 38 |
| 7.15 | References | 38 |
| 7.16 | Key Personnel | 38 |
| 7.17 | Financial Stability Documentation | 38 |
| 7.18 | Insurance Coverage | 38 |
| 7.19 | Record-Keeping | 39 |
| 7.20 | Pricing Proposal | 39 |
| 7.21 | Federal Clauses for Federal Contracts – Appendix I | 39 |
| 7.22 | Standard Terms and Conditions - Appendix G and H | 39 |
| 7.23 | Additional Relevant Information | 39 |
| 8.0 | EVALUATION AND AWARD PROCESS | 40 |
| 8.1 | Evaluation Committee | 40 |
| 8.2 | Preliminary Evaluation | 40 |
| 8.3 | Right to Reject Proposals | 40 |
| 8.4 | Scoring of Technical Proposals | 40 |
| 8.5 | Additional Factors for Proposal Consideration (prior to evaluating price) | 41 |
| 8.6 | Final Evaluation | 41 |
| 8.7 | Evaluation Summary | 42 |
| 8.8 | Contract Award | 44 |
| 8.9 | Notification of Intent to Award | 45 |
| 8.10 | Appeals Process | 45 |
| 9.0 | Contract Administration Information | 46 |
| 9.1 | Contract Administrator | 46 |
| 9.2 | Technical Administrator | 46 |
| 9.3 | Inspection Administrator | 47 |
| 9.4 | Contract Payment Administrator | 47 |
| 10.0 | Contract Clauses (See Appendix I For Federal Clauses for Federal Contracts) | 47 |
| 10.1 | Force Majeure | 47 |
| 10.2 | Hold Harmless/Imdemnifaction | 47 |
| 10.3 | Payment Terms | 48 |
| 10.4 | Contract Funding | 48 |
| 10.5 | Reference to Contract | 48 |
| 10.6 | Shipping | 48 |
| 10.7 | Assignment, Transfer and Subcontracting | 48 |
| 10.8 | Conformance with Contract | 48 |
| 10.9 | Federal Funding and Special Requirements | 49 |
| 11.0 | PROPOSAL PROCEDURE AND INSTRUCTIONS | 49 |
| 11.1 | Solicitation Examination | 49 |
| 11.2 | Alteration of Solicitation Document | 50 |
| 11.3 | Interpretations or Representations | 50 |
| 11.4 | Satisfactory of Requirements | 50 |
| 11.5 | U.S. Funds | 50 |
| 11.6 | Proposal Prices | 50 |
| 11.7 | RFP Consideration of All Inherent Costs | 51 |
| 11.8 | RFP Fixed Pricing | 51 |
| 11.9 | EXTENSION OF PROPOSAL PRICES | 51 |
| 11.10 | Vendor Questions and Clarifications | 51 |
| 11.11 | RFP Clarifications | 52 |
| 11.12 | SOLICITATION AMENDMENTS | 52 |
| 11.13 | LATE PROPOSALS AND PROPOSALS | 53 |
| 11.14 | Method of Proposal | 53 |
| 11.15 | Multiple Proposals | 53 |
| 11.16 | Incurring Costs | 54 |
| 11.17 | Withdrawal of PROPOSALS | 54 |
| 12.0 | Representations, Certifications, and Other Statements of Proposers/Offerors | 54 |
| 12.1 | Debarment | 54 |
| 12.2 | Registration and Licenses | 54 |
| 12.3 | Warranties | 55 |
| 12.4 | Disadvantage Business Enterprise (DBE) | 55 |
| 13.0 | Proposal Submission | 55 |
| 13.1 | RFP General Instructions | 55 |
| 13.2 | RFP Proposal Submittal | 56 |
| 13.3 | Email Submittal(s) | 56 |
| 13.4 | RFP Pricing Proposal Submission | 56 |
| 13.5 | RFP Proposal Organization and Format | 56 |
| 13.6 | RFP Presentations and Demonstrations | 58 |
| 13.7 | Late Proposals, Proposal Modifications, or Proposal Withdrawals | 59 |
| 13.8 | Authorized Signature | 59 |
| 13.9 | Descriptive Literature | 60 |
| 13.10 | RFP Complete Responses | 60 |
| 13.11 | Vendor References | 60 |
| 14.0 | Selection and award process | 60 |
| 14.1 | Preliminary Review and Acceptance of Proposal | 60 |
| 14.2 | RFP Evaluation Committee | 61 |
| 14.3 | RFP Accepted Proposals | 61 |
| 14.4 | RFP Award and Final Offers | 61 |
| 14.5 | CONTRACT AWARD | 62 |
Appendix A - Pricing Proposal (Excel) Appendix B - Proposal Signature Page Appendix C – Affidavid of Non-Collusion Appendix D – Proposer Information Appendix E – References Appendix F – Designation of Confidential and Proprietary Information Appendix G – Standard Terms & Conditions (DOA-3054 (R08/2016)) Appendix H - Supplemental Standard Terms and Conditions for Procurements for Services (DOA-3681 (R01/2022)) Appendix J – Manitowoc’s Cellcom Contract (For Informaitonal Purposes Only) Appendix I - Federal Clauses for Federal Contracts (Separate Document) Appendix K – Insurance Appendix L – Record Keeping Definitions For the purposes of this Request for Proposal and resulting Contract(s), the following definitions of terms shall apply, unless otherwise indicated.
| Acceptance Period |
| The number of calendar days available to the Issuing Agency for awarding a contract from the date specified in this solicitation for receipt of PROPOSALS. |
| Agency |
| City of Manitowoc – Maritime Metro Transit |
| Proposer |
| The entity submitting a Proposal in response to this RFP. |
| CAD / AVL |
| Computer Aided Dispatch / Automatic Vehicle Location |
| Contract Administrator |
| The Agency employee responsible for oversight of the implementation, administration, and completion of the Contract. |
| Contract Manager |
| The employee of an Agency responsible for 1) resolving contractual matters that cannot be resolved with the Contract Administrator; and 2) facilitating and/or completing all official actions under the Contract including but not limited to amendments, renewals and termination. |
| Contract |
| The final version of any contractually binding agreement between the State and the Contractor relating to the subject matter of this RFP; references to the Contract include all exhibits, attachments and other documents attached thereto or incorporated therein by reference. |
| Contractor |
| The person or entity that has been awarded the Contract as a result of this RFP, and who is required to provide equipment, materials, supplies, contractual services, or leasing real property to, the Procuring Agency. |
| Disadvantage Business Enterprise (DBE) |
| DBEs are for-profit small business concerns where socially and economically disadvantaged individuals own at least a 51% interest and also control management and daily business operations. |
| Mandatory |
| A requirement labeled as such must be present in the proposed solution, exactly as stated, or the solution will not be considered by the Procuring Agency. The terms “must,” “shall,” and “will” are considered mandatory. |
| May |
| Indicates something that is not mandatory but permissible. |
| MMT |
| Maritime Metro Transit |
| Procurement Manager |
| The person responsible for managing this procurement process. |
| Responsible |
| A Proposer who has furnished information and data to prove that the financial resources, service, facilities, personnel, service reputation, and experience are adequate to make satisfactory delivery of such Services and Deliverables set forth in the RFP. |
| Responsive |
| A proposal that conforms in all material respects to the requirements set forth in the RFP. |
| RFP |
| This Request for Proposal. |
| State Holidays |
| January 1, Martin Luther King Jr. birthday, Memorial Day, July 4, Labor Day, Thanksgiving Day, December 24, December 25, and December 31 |
| Supplier: |
| A person or entity that has been awarded the Contract as a result of this Proposal, and who is required to provide the agreed upon good and/or services. The term Supplier is used throughout this document in lieu of Contractor. |
| Turn Key: |
| A turnkey CAD/AVL (Computer-Aided Dispatch/Automatic Vehicle Location) system is a comprehensive, ready-to-use transit management solution provided by a single vendor. The vendor takes full responsibility for planning, designing, installing, testing, and maintaining both the hardware (e.g., GPS units, mobile data terminals) and software, allowing the transit agency to start operations immediately upon handover |
| Vendor: |
| A person or firm submitting a response to a solicitation and a set of specifications. The term Vendor is used throughout this document in lieu of Proposer or Proposer. |
1.0 GENERAL INFORMATION
General Description The City of Manitowoc – Maritime Metro Transit is seeking Proposals from qualified contractors to provide:
· Computer Aided Dispatch and Automatic Vehicle Location Software
· Computer Aided Dispatch and Automatic Vehicle Location Hardware
· Installation of Aided Dispatch and Automatic Vehicle Location Hardware The PROCURING AGENCY intends to use the results of this solicitation to award a contract to a Proposer for the aforementioned services.
The PROCURING AGENCY makes no express or implied warranties whatsoever that any particular quantity or dollar amount of Services will be procured. The PROCURING AGENCY reserves the right to cancel this RFP for any reason prior to the issuance of a notice of intent to award.
MMT does not have a current CAD/AVL system. It currently uses UniteGPS for routing, planning and fleet view.
Contract Term One (1) contract will be awarded. The contract will be for a base term of one (1) year estimated to begin October 1st 1, 2026, and may be renewed with an option of up to 4 – one (1) year renewal options for a potential contract term not to exceed five (5) years.
Supplier must not invoice agency for any costs accrued prior to this contract start date.
Any Contract resulting from this solicitation shall not be, in whole or in part, subcontracted, assigned or otherwise transferred to any other Supplier without prior written approval from the Agency.
Number of Contracts It is the intention of the agency to award One Contract for the services and goods required in this solicitation.
Procurement Manager All communication and/or questions on all matters regarding this Proposal must be made in writing and refer to Request for Proposal number QE-26-3 and be directed to the agency Procurement Manager: Kevin Bottesi at kbottesi@manitowocwi.gov.
Any contact or communication with any employee or officer concerning this RFP except the Procurement Manager is strictly prohibited from the date this RFP is released until the date the notice of intent to award is issued. The Procurement Manager may authorize in writing contact or communication with another State employee or officer as circumstances dictate. Vendors who hold a current Contract may continue to communicate with the appropriate Contract Administrator regarding the performance of that current Contract.
Federal Participation This procurement is subsidized with state and federal transit operating funds. Federal grant monies $240,074 fund this contract, in whole or in part (Section 5311). Applicable Federal clauses are set forth in Appendix I of the solicitation.
· As such, agencies receiving such funds and contractors awarded contracts that use such funds must comply with certain Federal certifications and clause requirements. This includes compliance with Buy America Act Estimated Number of Vehicles Quantity The Agency’s current vehicles vehicle numbers and types are detailed below. These numbers are estimates only and do not guarantee a minimum or maximum number of vehicles that could use the services from this contact, as programs and funding are ongoing and subject to change.
| Types of Vehicles |
| No. of Vehicles |
| Products required for Vehicle |
| 35’ Gilligs Buses |
| 9 |
| Software, MDT’s and Public Vehicle Location Displays |
| Ford Transit Van |
| 1 |
| Software and MDT |
| Chrysler Pacifica Van |
| 1 |
| Software and MDT |
Software pricing submitted for this RFP is for unlimited amount of vehicles.
Contractor Selection The Municipality reserves the right to award a contract to a Vendor without clarifications, discussions, or negotiations following an evaluation of which Vendor is determined to be the highest scoring (technical factors and price considered) based on the factors discussed below. As such, Vendors should always submit their best technical and price proposal from the onset.
1. Company Experience and Qualifications
2. Compliance with Scope of Work and Implementation Plan
3. Customer Service and Support including Comprehensive Training Plan
4. Pricing Contract Term Price Options Proposers must price a one (1) base year contract price at the time of proposal submission in order to be considered for award. The price sheet submitted by the successful Proposer will be incorporated in the resultant contract as the contract’s Pricing Schedule.
This is a firm-fixed price contract for a base term of one (1) year estimated to begin October 1st, 2026, and may be renewed or extended with an option of up to 4 – one (1) year renewal options for a potential contract term not to exceed five (5) years.
Proposers are required to submit a firm-fixed price for the contract base period (first contract year) that covers all operating and administrative costs of performing the service. Proposers must also submit fixed prices for Option Years 2, 3, 4 & 5.
The competitiveness of the offered prices will be based on the total price of the sum of Section A of the pricing proposal.
Pricing proposal format will include software agreement, hardware and installation for contract year-one. The additional four (4) 1-year renewal options will only include software subscriptions and maintaince.
Contract Modifications The resulting Contract must only be used to purchase services within the scope and intent of the original Request for Proposal. Any modifications made to the resulting Contract must fall within the scope of the Proposal.
All modifications must be made in writing and signed by both parties.
Completeness and Validity of Offers Vendors must complete and submit all required forms with their Proposals. This includes the “Affidavit of Non-Collusion” which Vendors must submit with their pricing proposal.
Vendors must acknowledge receipt of any solicitation amendments. Offers must remain valid for a minimum of 90 days after Proposals are submitted.
Correspondence Related to the Solicitation Questions, noted errors, discrepancies, ambiguities, exceptions, additions, or deficiencies noted in this solicitation must be submitted by e-mail to the identified Procurement Administrator prior to the specified solicitation closing date.
Any changes in the solicitation (including specification) will be made by amendment issued to all Vendors.
Reasonable Accommodations City of Manitowoc – Maritime Metro Transit can provide reasonable accommodations, including the provision of informational material in an alternative format for qualified individuals with disabilities upon request. If a Vendor needs accommodations at the outset of this solicitation process, please contact the Procurement Manager.
Wisconsin Public Records Law WisDOT and all records it retains are subject to Wisconsin Public Records law, sec. 19.31, et seq, Wis. Stats. WisDOT will advise proposer request for records it has designated as proprietary or confidential. All records shall be retained in a safe and secure place for a period of four (4) years after the end of the final contract year.
Federal Public Records Law The Supplier must maintain the following records which will be available to the Wisconsin Department of Transportation for inspection upon demand. All records, whether handwritten or electronic, must be accurate, organized, and legible. All records shall be retained in a safe and secure place for a period of four (4) years after the end of the final contract year and the grant has been closed.
Order of Precedene In the event of contract award, the contents of this RFP (including all attachments), RFP addenda and revisions, the bid response from the successful bidder, and additional terms agreed to, in writing, by WisDOT and Contractor shall become part of the contract.
The following priority for contract documents will be used if there are conflicts or disputes:
1. The Contract Document
2. Official Purchase Order
3. Proposal response as accepted by The Agency
4. The Agency’s Published Request for Proposals
2.0 PRE-PROPOSAL CONFERENCE
City of Manitowoc – Maritime Metro will not be hosting a pre-proposal conference.
3.0 PROPOSAL SCHEDULE
City of Manitowoc – Maritime Metro intends to adhere to a schedule in procuring these services. The schedule below is provided for informational purposes, may be affected by unforeseen circumstances, and is subject to change.
Listed below are dates and times of actions related to this solicitation. The events with specific dates must be completed as indicated unless otherwise amended. In the event that the Agency finds it necessary to change any of the specific dates and times in the calendar of events listed below, it will do so by issuing an amendment to this solicitation. There may or may not be a formal notification issued for changes in the estimated dates and times.
At the time of issuance, the procurement schedule shall be as follows:
| Date |
| Event |
| 5/13/2026 |
| Issue Request for Proposals (RFP) |
| 5/27/2026 at 2 PM CT |
| Due date for submitting questions |
| 6/3/2026 |
| Issue written response to questions - Estimated |
| 6/19/2026 at 2 PM CT |
| Due date for submitting Proposals - Late submissions will not be accepted |
| 6/22/2026 |
| Proposal Evaluation Starts - Estimated |
| Week of 6/29/2026 |
| Oral presentations, as needed (1 hour each, if needed) - Estimated |
| 7/2/2026 |
| Call for Best and Final Offers (if needed) - Estimated |
| 7/3/2026 |
| Due date for submitting Best and Final Offers - Estimated |
| 7/10/2026 |
| Final approvals for award - Estimated |
| 7/10/2026 |
| Notification of Inent to Award - Estimated |
| 7/27/2026 |
| Issue “Notice to Proceed”- Estimated |
| October 1st, 2026 |
| Contract Start Date – Estimated |
4.0 GENERAL PROPOSAL SUBMISSION REQUIREMENTS
Proposals which do not comply with the format set forth below may be rejected without further consideration. These restrictions are not intended to hamper proposal preparation but to provide uniformity in evaluating responses to this RFP.
A. Corporations, individuals, or other organizations interested in providing service should so indicate by answering all questions included throughout this RFP. Vendors must respond to any questions and forms included throughout this RFP.
B. The completeness and responsiveness to the RFP’s stated requirements (Scope of Work), questions, tables, and forms will be used in evaluating Proposals in accordance with solicitation’s evaluation factors and the assigned weights for such factors. For Proposals to remain eligible, all information provided must be true and accurate and reasonably verifiable.
C. Proposals received after the due date and time will be considered late Proposals and will not be accepted. Reliance upon public carriers for delivery of Proposals is at the Offeror’s risk. Proposals submitted via fax will not be accepted.
D. The pricing proposal must be submitted on the form shown in Appendix A, and must be signed by an individual authorized to contractually obligate the Offeror. The provided pricing sheet should not be modified or altered to present different or additional information than what the form is asking for.
E. The pricing proposal (Appendix A) shall be placed in a separately sealed envelope and its contents not disclosed or revealed elsewhere within the submitted RFP package. The rate shall cover all operating and administrative costs of performing the service.
5.0 Proposal Format
Proposal Format Each proposal shall include complete and detailed written responses to the items below. Each Offeror’s response to these items will be evaluated in accordance with the criteria stated in this RFP Hard Copy or email
0. Each proposal should be in Microsoft Word, Adobe Acrobat, or equivalent format, using 12-point font and a standard 8 ½” x 11” page format.
Cover Letter The Cover Letter must specifically state that the information contained in the Offeror’s proposal is accurate and complete as of the date of submission; that the information is true and reasonably verifiable as of the date of submission; and that the Offeror is willing to comply with all stated contractual requirements.
6.0 Contract Deliverables
The City of Manitowoc – Maritime Metro Transit, (hereinafter referred to as Municipality or City), is soliciting Proposals from firms (also may be referred to as Offeror or Contractor) to provide Computer Aided Dispatch and Automatic Vehicle Location software and hardware.
All deliverables in this section are considered the minimum deliverable for the services required. The following deliverables must be met at no additional cost above the pricing provided in the Proposal. Failure to meet any minimal deliverables may result in the disqualification of the Proposal. In the event no Vendor is able to meet individual specifications, the agency reserves the right to continue the review of Proposals and to select the Proposal that most closely meets the specifications detailed in this RFP.
The following contract deliverables must be met at no additional cost above the pricing provided in the Proposal.
Before the award of any Contract, the Agency shall be satisfied that the Vendor has sufficient qualified resources available for performing the work described in this Proposal. It is the Vendor’s responsibility to acquaint the Agency with these qualifications by submitting appropriate or supporting documentation.
Minimum Qualifications IMPORTANT – EACH OFFEROR MUST DEMONSTRATE IN ITS PROPOSAL THAT IT MEETS ALL OF THE MINIMUM QUALIFICATIONS SET FORTH BELOW AS OF THE DATE THAT IT SUBMITS ITS OFFER. OFFERORS THAT DO NOT CONFORM TO THESE REQUIREMENTS WILL NOT BE CONSIDERED.
6.1.1 Organizational History
Vendor must have at least three (3) years prior organizational history in the transit software management system.
At time of proposal, vendor must provide proof of at least three (3) years prior organizational history of providing CAD/AVL systems.
6.1.2 Turn-Key Requirement
The CAD/AVL system must provide MMT with a turn-key product.
At time of proposal, vendor must provide a written summary proving that it’s CAD/AVL system can provide MMT with a turn-key product.
6.1.3 Impimentation History
Vendors must have successfully installed/implemented proposed full ITS system, including Bus Tracker App and integrations, like Automatic Vehicle Annunciation (AVA), at a minimum of three (3) public transit systems.
At time of proposal, vendor must provide summary of at least three (3) successfully installed/implemented proposed full ITS system.
6.1.5 Vendor Provided Equipment
Vendor must provide everything required for the services included in the RFP including:
· Hardware/Components - The system must allow for the integration of new vehicles into the system.
· Software - At the time of implementation, vendor’s software must be the current version and compatible with the vendor’s hardware. The software solution shall require no installation of any kind on MMT’s computers or servers with everything stored on vendor’s servers/cloud. Vendor must always ensure that MMT is utilizing the latest approved and beta tested software version available.
· Installation, mounting system/hardware - Hardware and associated integrations will be physically installed in all designated MMT vehicles in our vehicle storage facility (2655 S. 35th St, Manitowoc, WI).
· Cellular data must to be compliant with City’s cellular and data contract (Currently Cellcom)
· All shipping and delivery costs included in pricing.
At time of proposal, vendor must provide proof they can provide everything required for the services included in the RFP.
Services / Items Required City of Manitowoc – Maritime Metro Transit is seeking a Vehicle Tracking System utilizing GPS technology in conjunction with a vehicle location and mapping software to track vehicle locations on route and in real-time and provide a visual mapping display. The primary purpose of the system is to improve the quality of Maritime Metro Transit’s fixed-route service and emergency response capabilities to the public. This system must provide route and vehicle information in real-time via web interface to passengers, the dispatcher, and managerial personnel. The system must be equipped with reporting capabilities to accurately data stream operation service information (e.g., route timing, passenger wait time, trip counts, operator performance, vehicle speed and movement). This is essential for the completion of performance metrics, the analysis of daily operation, and long term project planning and analysis. The Vehicle Tracking System must include the functionality for hardware/software components to be installed.
Required elements must include but not be limited to; mobile data terminals (MDT), automatic voice annunciation system (AVA), integration with existing Hanover signs, implantation of new digital signage, integration with other contracted services, and both static and real time GTFS that is available and accessible to any vendor of Maritime Metro Transit’s choosing. This solution must be a well-proven, turn-key, industry-standard, cloud-hosted system. The hardware and software must assist in capturing data and providing feedback to better manage and operate a more efficient Maritime Metro Transit system. The proposal must demonstrate how the features will provide a significant operational upgrade for Maritime Metro Transit.
Anticipated Timeline The Vendor must must follow the anticipated timeline below. Consider these timeline dates when responding point by point to Section 7 Timeline.
The Agency’s anticipated schedule is as follows:
· Contract Start Date: October 1, 2026
· Begin BETA Testing: November 1, 2026
· BETA Testing Completed: by November 15th , 2026
· Estimated Go‑Live Date: Novemeber 30th, 2026
· Please note vendor must have system installed, fully functioning, tested and operational by this date.
Detailed Specification I. General Software Requirements At the time of implementation, vendor’s software must be the current version and compatible with the vendor’s hardware. The software solution shall require no installation of any kind on MMT computers or servers with everything stored on vendor’s servers/cloud. Vendor must always ensure that MMT is utilizing the latest approved and beta tested software version available.
The system will be hosted by the supplier (or an agent of the supplier), accessible by way of the Internet (i.e., “cloud” or SaaS), and will run in a standard web browser currently under support by its manufacturer.
System should be able to run on a standard PC with an operating system currently supported by its manufacturer, without the need to install any software or plug-ins.
II. Management Software MMT prefers CAD/AVL software solution that is 100% cloud-based with web portal access provided anytime of the day (24 hours a day, 7 days a week, 365 days a year). The CAD/AVL software shall provide the following minimum capabilities for MMT management staff.
· Utilize GPS to provide automatic vehicle location (AVL) in conjunction with mapping
· Graphic User Interface (GUI) map display viewable through various devices (smartphone, smart TV, kiosk, PC, etc.)
· Map display shall clearly display vehicle icon and location. Map shall include the entire MMT service area. Map shall have the ability to expand into additional communities if service expands. Further layered information shall include bus route, streets, highways, points of interest, time points, bus stops, run, operator ID, vehicle ID and speed. Include ability to limit display of this information according to permissions or map version. For example, the public map would not display operator name, etc, but may include mobility device securement equipment details or securement area configurations specific to each individual bus. Map display features shall include zoom in or out, pan in any direction and point-and click on features and vehicles to retrieve information. The map should be expandable to full screen view.
· AVL and mapping will include all fixed-routes and event based routes.
· AVL location data will begin when the ignition is turned on and continue reporting until the ignition is turned off. Location of vehicles with no assigned route will also be tracked and visible in mapping for the private transit system site.
· Dispatcher’s GUI real-time display will provide bus arrival times at each bus stop based on average speed of the bus and traffic impacts. The vehicle icon should clearly indicate vehicle ID, route, directional status, arrival time, and departure time.
· Map will display last known position on any unit suffering loss of GPS signal and shall visually display and provide an alert to show a vehicle that is not in communication.
· Map will clearly mark each route and vehicle when more than one travels on the same street segment.
· Geo-spatial management portion will provide administrators a visual creator with the ability to add, delete or revise service data (route, stop, schedule, etc.) without contacting vendor.
· Added or edited service data will be effective immediately or scheduled for a later implementation date.
· Administrative and Dispatcher interface shall be simple, intuitive and easy to use.
· Allow for certain management functions to be accessed from internet-enabled smartphones.
· Ability to send user pre-defined canned and brief custom messages to MDT(s) by selecting individuals, operators, or all vehicles with sender notification of success or failure of the transaction.
· System must be able to run on a standard PC and operate on future Microsoft operating systems. The user interface must be accessed from commonly used Internet Browser without the need to install any software or plug-ins.
Vendor shall back-up and protect, for a minimum of sixty (60) days, any software configuration settings, any MMT provided data that has been modified for use by the software and any new data produced by the software itself.
At the time of implementation, vendor’s software must be the current version and compatible with the vendor’s hardware. MMT desires a solution that requires no installation of any kind on MMT Transit’s computers or servers with everything stored on vendor’s servers/cloud. Vendor must always ensure that MMT is utilizing the latest approved and beta tested software version available.
III. Website and Bus Tracking App The CAD/AVL system will include a public interface that provides customers with bus location information based on real time location data. Website map and app will show steady vehicle movement on map without reloading. Motion of vehicle(s) tracked on website or app shall appear smooth and fluid. The public interface includes website, smartphone, smart TV, and monitor display access.
The public website shall provide:
· Users with the ability to select routes or areas of interest on map and view bus location.
· Static and real-time arrival estimates by bus stop
· Ability for MMT’s logo/graphics to website
· A module allowing content to be provided on MMT’s website.
· Ability to differentiate estimated arrival times for inbound and outbound stops along a specific route.
· Continuous updates to the web page without the user being required to refresh.
· Returning customers with route remembrance for previous visits
· Ability for riders to subscribe to a notification service, select one or multiple routes and receive notifications when next bus is arriving.
· Ability to display and push service alerts or other messages to riders.
· System shall provide a module that allows Trip planner and other content to be provided on Customer’s own website.
· System shall continuously update the web page (whenever a new estimated time of arrival (ETA) is determined, bus is added/removed, etc.), without the user being required to refresh the webpage.
Smartphone App access shall provide:
· Users with the ability to select routes of interest and view bus location.
· Static and real-time arrival estimates by bus stop
· Users will receive static route schedule and real-time bus stop arrival estimate based on AVL data
· Geolocation feature to allow riders to identify location on map (for phones with GPS capability)
· Ability to integrate with future on-demand apps allowing users to toggle between services in one app
· Free to download native iPhone and Android application. Monthly download reports from app stores
· Ability for riders to subscribe to a bus arrival service. Ability to select stops, set a schedule and receive notifications when next bus is arriving at a specified bus stop within the time period selected. Alerts then notify the user in advance (10-15 minutes) of bus arrival.
· Translation of content to other languages
· App accessibility features to accommodate riders with disabilities
· User display shall offer detailed maps, preferably using customer-friendly maps
· Ability to display and push service announcements, alerts or other messages to riders
· Trip planning
The system will have cellular-based vehicle location capability to capture and transmit vehicle location information on a real-time or near real-time basis transit system-wide and route specific. Cellular data fees shall be included in the vendor’s base price.
System shall provide the ability to display a version of the bus tracking map on public flat screen monitors and smart TVs. MMT would potentially purchase and install monitors and smart TVs at its downtown transit center and possibly other strategic locations in its service area. The display would require no user interaction and automatically refresh on LCD screens at all times. The display shall include the ability to identify a specific vehicle, view route name and differentiate routes by design or color. The ITS system shall maintain map, route and other information to ensure it is current.
IV. Covert Alarm MMT requires the CAD/AVL system to provide a covert alarm feature that allows drivers to discretely contact dispatch when an emergency exists or when radio communication is not an option. When triggered by the driver, the triggering action and subsequent alarm would be covert onboard, meaning it would not alert passengers. However, the alarm would visibly and audibly alert dispatchers and admin personnel viewing the software. MMT would prefer the option to send a text notification with pertinent information to designated cell phones when the covert alarm is triggered as well. When triggered, the covert alarm would also integrate with each vehicle’s destination signs and display an appropriate message on exterior signs. To trigger the alarm, MMT would consider a covert button/function built into the proposer’s hardware solution.
V. Automated Voice Announcments (AVA) MMT requires CAD/AVL system to provide Automated Voice Announcements (AVA) of bus stops, major intersections, or other designated locations over an interior speaker system. The announcement capability shall be designed to allow MMT to comply with applicable ADA (Americans with Disabilities Act) requirements and guidance. The AVA system shall include the following:
· Announcements must be able to be made at a predetermined distance from a bus stop. Announcements shall be paused while a bus operates off-route.
· Use of GPS vehicle location data and GPS geo fences/trigger zones to determine announcement timing. The trigger zone shall use default values or allow MMT to over-write by route and/or individual location.
· The system shall detect reacquisition of the route, at any point along the route, and automatically determine and announce the next valid bus stop or other designated location.
· A configuration utility that allows MMT the ability to fine tune announcements. This includes creation and selection of which bus stops and routes are announced; edit of current stop announcements by turning ‘off’ or ‘on’; creation of custom trigger zones to identify bus stop locations and other trigger locations; and configure pivot points that trigger a change to the destination sign.
· When a new route or stop is created in the web portal, CAD/AVL system shall provide a digitized voice synthesizer tool or professionally recorded audio announcements for locations selected for announcement. If recorded audio is provided by vendor, changes or additions to audio files must be provided for the life of the contract and available within 2 business days of MMT’s request.
· Audio announcements shall be played in English and up to two additional languages (e.g., Spanish and Hmong)
· In addition to the next stop announcements, the annunciation system shall be capable of making vehicle operator-initiated announcements. The operator can select from a list of pre-compiled announcements via the MDT.
· Vehicle operator use of the PA system shall override any automated announcements.
· Provide scrolling text data (route name & number, stop name for designated stop and date & time) to the interior LED sign or digital onboard displays.
VI. Reporting CAD/AVL system shall provide reports that allow MMT to run more efficiently, improve safety and share data. Vendor shall provide a variety of tools that allow users to analyze, monitor and diagnose fixed routes and their operations. Minimal required reportable data and events includes:
· Route Performance (run times, average vehicle speed and schedule adherence)
· On-time performance
· Service hour and miles
· Vehicle speed and movement
· User-Defined Exceptions: Off-route, speed, route adherence, etc.
· On-board announcements (when & where announcements were played)
· Website usage reports
Reports shall allow for time-based comparison and historical data. Reports shall include filters by driver, route and run. Reports shall be exportable instantly to Microsoft Excel and Word. Reports should also be available in PDF format.
The system shall automatically email selected reports to a list of MMT supplied email addresses.
VII. System Intergration CAD/AVL system must offer complete system integration that accommodates existing equipment onboard MMT buses without compromising efficacy of overall system. The existing equipment includes, but is not limited to, the items listed in “Current Onboard Equipment” and “Current CAD/AVL System” sections above. The CAD/AVL system must integrate with each vehicle’s destination signs, interior displays/signs, speakers, as well as electronic fare media technology with no additional hardware needed. At a minimum, the CAD/AVL system will integrate with the destination signs to change messaging automatically to a different route based on vehicle location; The CAD/AVL system must have the ability to expand and be open to integration with future systems, like Automatic Passenger Counters (APC) and other future electronic fare media technology.
In the event of CAD/AVL system malfunction, the existing control unit provided by the destination sign manufacturer shall remain functional for driver override. If MMT’s destination sign control units on the older vehicles require upgrades to allow for integration, MMT will work with the awarded vendor to coordinate and supply necessary upgrades. The text displayed on the destination signs shall automatically update as the bus traverses the route. MMT will have the ability to define points along the route and corresponding destination sign text. The system must determine by bus location when it is necessary to change the destination sign.
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.
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.
VIII. General Transit Feed Specification (GTFS) The City of Manitowoc currently maintains MMT’s GTFS data. Route and bus stop data is maintained/edited within UniteGPS software. Calendar, fare, transfer and other data is manually edited.
The CAD/AVL system must manage all GTFS data and provide a simple GTFS export feature when feed update files are required. GTFS data must use naming conventions throughout. The GTFS data files must be available to MMT at all times, continue to be open to developers and published on the City of Manitowoc’s website (https://www.manitowoc.org) and other websites containing transit feeds.
IX. Support The CAD/AVL system vendor will provide 24/7 support when needed in case of severe emergencies. Vendor’s support will be accessible via phone, web and email with a turnaround response time of less than 3 hours for any mission critical components. Base support shall be available during normal business hours. Standby support shall be available at all other times, including weekends, nights and holidays.
The vendor shall offer one full year of full technical support as part of its cost proposal. This technical support shall include, but not necessarily be limited to:
· Phone & email support with service technician/engineer during normal business hours maintained by MMT.
· Provision of diagnostics/repairs via remote control access to system hardware/software.
· On-site technical support when required.
· Product upgrades, new releases, patches, etc. when issued by the vendor.
· Software enhancements (point releases) shall be included for the duration of the project.
X. Open Data The system should provide optional capability and integration of Real-Time Transit Data API, including easy to use developer documentation that allows for querying data from AVL services, with JSON document as output. The API should provide real-time vehicle location data and estimated arrival times for vehicles as they approach bus stops.
Open data shall be updated regularly to reflect changes in routes, schedule and/or bus stops. Access to all real-time and archived vehicle location data must be available to third party applications for external development purposes. MMT strives to make data developer-friendly and requires a vendor that provides open data to other third-party developers. The real-time AVL feed would potentially be used by this technology.
XI. System and Data Security Cloud services and login must be over a secure connection. Data must be encrypted to the latest standards. All data stored in the Cloud must be free from any Personally Identifiable Information (PII). Any PII data requires appropriate protection and shall not be publicly available. Vendors will confirm these items and explain full security measures in their Written Proposal Response.
XII. Data Ownership and Protection All data in the Cloud environment is understood to be the property of the MMT. If the agreement between MMT and cloud provider or vendor is cancelled, it is understood that all data can be exported to MMT. In the event of a contract termination, the contractor agrees to make all necessary good-faith efforts to cooperate in the transition of MMT information back to MMT or to other, new vendors.
The Contractor shall not use, disclose, or distribute any data provided by MMT except as may be requested to MMT and for MMT purposes. In the event the Contractor is contacted by any law enforcement or regulatory agency with any lawful order regarding MMT data, the Contractor shall promptly notify MMT of such contact to the extent allowed by law. The Contractor shall provide copies of MMT data to MMT upon request.
GPS data, and specifically route identifiers and location coordinates, are not considered potentially sensitive data. Both parties understand that this GPS data will be an integral element of this system and that temporary access to this GPS data may, in fact, may be disclosed to the public through the public’s use of an associated application or website to enhance the public’s use of MMT.
XIII. Project Management All information and correspondence shall flow through MMT’s identified project manager or designee, who will be responsible for providing direction to the vendor. Vendor must supply an implementation plan, which identifies the project timeline and milestones.
The awarded vendor shall name one (1) individual from their firm that will be designated as project manager. This individual shall have complete authority and control over all aspects of the project. The awarded vendor’s project manager shall be the sole point of contact between the vendor and MMT. A list of other project installations directly under the control of this individual shall be named in the proposal.
MMT requires the vendor to provide and share access to project management software (e.g., Trello) with a dashboard focused on this project. Ongoing project status meetings would use the software’s workspace to document and address phase planning & implementation status, feature requests, bug reports & issue resolution, open questions and deliverables.
XIV. Kick-Off Meeting A kick-off meeting will be held on-site in Manitowoc or virtually to introduce the project manager and project team. The kick-off meeting will cover lines of communication, project schedule and project work plan. This meeting will also serve to enable MMT to gain a complete understanding of the selected system requirements. The requirements will be summarized and provided as a draft report to MMT.
XV. Vehicle Hardware Installation Hardware and associated integrations will be physically installed in all designated MMT vehicles in our vehicle storage facility (2655 S. 35th St, Manitowoc, WI). All installs must be completed to withstand the shock and vibrations generated by transit vehicles in service. Each bus installation shall be done uniformly. As each vehicle’s installation is complete, a designated MMT representative will inspect areas like cabling, sealed connections and equipment mounts to ensure proper installation. MMT will coordinate with the selected vendor’s project manager to test and confirm operability, integrations and data related to the onboard equipment.
The selected vendor will provide a schematic of install, guidance, and training to enable MMT mechanics to perform installs when future vehicles are added to the fleet.
XVI. System Testing System testing must be performed so that every MMT revenue service vehicle has a fully functioning CAD/AVL system according to this RFP and the vendor’s proposal. The awarded vendor’s project manager and/or a duly qualified staff person shall be on-site during the initial testing of all products.
MMT shall not be constrained by the testing and reserves the right to make the following requests which shall be acted upon by the Contractor:
· Procedural changes and other reasonable tests to assure the CAD/AVL system’s performance and conformance
· Investigation into any apparent troubles, flaws, or abnormalities with respect to the CAD/AVL system
When full install is complete; the system is prepared with applicable data; and staff training is complete; the awarded vendor’s project manager shall coordinate with MMT staff on scheduling of system tests to ensure correct operation. The awarded vendor will:
· Conduct performance testing of entire system using current MMT data and verify with MMT staff that all system components and functions perform according to the requirements and specifications in the resulting contract with MMT.
· Review results of tests with MMT and make all corrections as necessary.
XVII. Support and Maintenance Ongoing product support shall be included in annual product fee. Vendor’s support will be accessible via phone, web and email with a turnaround response time of less than 3 hours for any mission critical components. Base support shall be available during normal business hours. Standby support shall be available at all other times, including weekends, nights and holidays when needed in case of emergencies.
Software patches and minor enhancements shall be included for the duration of the contract. MMT prefers all major revisions be included as well. Security patches must always be free and implemented with high priority.
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 .