11-REVISED RFP 549315.pdf

City of Detroit Office of Contracting and Procurement (OCP)

Request for Proposal – 549315 Accessible and Autonomous Mobility Services

Revised 7/28/2026 Page 1 of 27

CITY OF DETROIT

OFFICE OF CONTRACTING AND PROCUREMENT

REQUEST FOR PROPOSALS

REVISED RFP NO. 549315

Accessible and Autonomous Mobility Services

Buyer: Aroya Rush

EVENT / ACTIVITY DUE DATE / TIME

ADVERTISEMENT DATE Wednesday, August 19, 2026

PRE-PROPOSAL

CONFERENCE

Monday, August 31, 2026 @ 2:00pm EST Location: Microsoft Teams (Virtual) Link: https://tinyurl.com/38hascvd

Meeting ID: 288 587 427 728 300 Passcode: 6rJ7Mn6D

Dial in by phone +1 469-998-6602,,522584301# Phone conference

ID: 522 584 301#

QUESTIONS DUE Wednesday, September 2, 2026 by 2:00pm EST

All questions must be submitted online in the Supplier Portal as indicated in Section 3.3 of this

RFP.

ANSWERS DISTRIBUTED Friday, September 11, 2026 by 2:00pm EST

PROPOSAL DUE DATE * Wednesday, September 30, 2026 by 2:00pm EST

In the Supplier Portal as specified in Section 4.5 of this RFP.

* Respondents must register in EUNA Bonfire to download bid documents and submit bids. The City cannot guarantee the accuracy of any bid documents obtained from outside of EUNA, and bids submitted outside of EUNA Bonfire will not be accepted. Detailed resources about registering and bidding, including video tutorials and live, virtual office hours, are available at www.detroitmi.gov/suppliersupport.

Questions about the specifics of this RFP must be asked within the EUNA Bonfire Messages interface for the bid on or before the date and time indicated above. Questions asked via phone, email, and/or other means will not be answered.

Proposals must be uploaded in EUNA Bonfire on or prior to the date and time indicated above.

Late and/or emailed proposals will not be accepted.

https://tinyurl.com/38hascvd https://detroit.bonfirehub.com/ http://www.detroitmi.gov/suppliersupport

Request for Proposal – 549315 Accessible and Autonomous Mobility Services

Revised 7/28/2026 Page 2 of 27

TABLE OF CONTENTS

Section 1. Project Summary and Background

1.1. PROJECT REQUEST

1.2. BACKGROUND/DESCRIPTION OF ENVIRONMENT

1.3. AWARD CLAUSE INCLUDING RENEWAL OPTIONS

Section 2. Statement of Work

2.1 SERVICES TO BE PERFORMED

2.2 OPERATIONAL INFORMATION

2.3 TECHNICAL INFORMATION

2.4 INSURANCE

Section 3. Proposal Evaluation and Selection Process

3.1 MINIMUM QUALIFICATIONS

3.2. ADHERENCE TO TERMS OF PROPOSALS

3.3. PRE-BID CONFERENCE

3.4. QUESTION DEADLINE

3.5. EVALUATION CRITERIA

3.6. EVALUATION PROCEDURE

3.7. ORAL PRESENTATION/DEMONSTRATION

3.8. REJECTIONS, MODIFICATIONS, CANCELLATIONS

3.9. PROTESTS

Section 4. Required Proposal Content and Submission Process

4.1. ACCURACY AND COMPLETENESS OF INFORMATION

4.2. REQUIRED PROPOSAL CONTENT AND FORMAT

4.3. REQUIRED COST PROPOSAL

4.4. ECONOMY OF PREPARATION

4.5. SUBMITTAL INSTRUCTIONS

Support Channels for Technical Difficulties and Questions Section 5. General Conditions and Requirements for RFP

5.1. CONTRACT APPROVAL

5.2. PAYMENT

5.3. INVOICES

5.4. ASSIGNMENT

5.5. MODIFICATION OF SERVICES AFTER CONTRACT APPROVAL

5.6. NEWS RELEASE

5.7. MISCELLANEOUS

5.8. OFFICE OF INSPECTOR GENERAL

RFP Attachments List

Revised 7/28/2026 Page 3 of 27

Section 1. Project Summary and Background

1.1. PROJECT REQUEST

The City of Detroit Office of Contracting and Procurement (OCP) on behalf of the Office of Mobility Innovation (OMI) and the Department of Transportation (DDOT) requests proposals from qualified Respondents to render certain technical or professional services ("Services") as set forth in this RFP to provide a phased Accessible & Autonomous Mobility Service, known as Accessibili- D 2.0. This initiative builds upon the original Accessibili-D pilot and advances a sustainable hybrid model combining manually operated and SAE Level 3 autonomous vehicle (AV) operations. The selected vendor will launch an interim manually operated service (Phase 1), transition to a hybrid manual-plus-AV model (Phase 2), and scale toward majority autonomous service over the contract term (Phase 3).

1.2. BACKGROUND/DESCRIPTION OF ENVIRONMENT

The City of Detroit is looking for a qualified vendor to provide a phased Accessible & Autonomous Mobility Service, known as Accessibili-D 2.0. This service is being procured to provide supplementary transportation for older adults (age 62 and over), people with disabilities, veterans, and survivors of gun violence within the defined service area. The service is intended to improve mobility and independence for these populations while demonstrating the operational and cost feasibility of integrating autonomous vehicles into an accessible, on-demand municipal transportation service.

The purpose of this RFP is to procure a single mobility partner capable of:

• Launching an interim manually operated accessible service;

• Transitioning to a hybrid manual-plus-AV deployment model;

• Scaling toward majority autonomous service;

• Demonstrating cost-per-ride reduction and operational sustainability; and

• Demonstrating compatibility with the City’s wireless (inductive) charging roadway infrastructure.

Accessibili-D 2.0 builds on the City's original Accessibili-D pilot, which demonstrated demand for supplementary, accessible, on-demand transportation among older adults, residents with disabilities, veterans, and survivors of gun violence. The program's mission is to expand safe, reliable, and independent mobility for these populations while positioning Detroit as a national leader in accessible autonomous transportation.

The current technology environment includes: (a) the City's wireless (inductive) charging roadway infrastructure, with which the City may pursue interoperability demonstrations during the contract term; and (b) the Detroit Department of Transportation (DDOT) call-center infrastructure, with which the vendor's booking system must integrate. Telephone bookings will be handled through DDOT call centers; the vendor is responsible for providing a booking application and browser-based booking channel and for the technical integration of its dispatch platform with the DDOT call-center intake (see Sections 2.1 and 2.3). The booking application may be a standard, commercially available booking/dispatch product; a custom-built application is not required.

Primary stakeholders include eligible riders and their caregivers, DDOT, the Office of Mobility Innovation, MDOT as the funding agency, and City leadership.

Revised 7/28/2026 Page 4 of 27

1.3. AWARD CLAUSE INCLUDING RENEWAL OPTIONS

If a contract is awarded as a result of this RFP, it will be a City of Detroit Technology Contract, Attachment E (the “Contract”). The term of the contract will be for two (2) years. This award is for a pilot. The City intends this procurement to establish and operate a pilot service that the City may continue as a long-term service if the pilot is successful. If the pilot is not continued, the City reserves the right to terminate the Contract for convenience, in whole or in part, as set forth in Article 12 of Attachment E, including to conclude the pilot. Any renewal option exercised under this Contract is effective only after the approval of the Detroit City Council and signed by the Chief Procurement Officer. The City anticipates one (1) award as a result of the RFP.

The terms of the Contract must be accepted by the successful Respondents. Any exceptions to the terms of the Contract must be included in the proposal. PLEASE NOTE: Any exceptions to the terms of the Contract may reflect negatively in the consideration of the proposal.

Revised 7/28/2026 Page 5 of 27

Section 2. Statement of Work

2.1 SERVICES TO BE PERFORMED

The selected vendor shall provide the phased mobility service described below. Unless otherwise stated, all requirements in this Section and in the Specifications (Section 2.3) are minimum requirements the vendor must meet. Where this RFP identifies a “Preferred” standard, vendors are encouraged but not required to meet it, and proposals will be evaluated accordingly.

A. PHASE 1 — INTERIM MANUALLY OPERATED SERVICE

“Manually operated service” means accessible, on-demand passenger transportation provided using the vehicles specified in Section 2.3 (D), operated by a trained human driver (i.e., not in autonomous mode). This phase establishes service to riders while the autonomous components are mapped, tested, and approved.

o Deploy the manually operated accessible service within ninety (90) days of contract approval;

o Deploy a minimum of three (3) manual vehicles to serve eligible riders (seniors 62+, residents with disabilities, veterans, and survivors of gun violence), subject to the rider-verification approach utilized by a separate contractor;

o Provide centralized dispatch and booking. The vendor must provide a booking application (a standard, commercially available product is acceptable) and a browser-based booking channel, and must integrate its dispatch platform with DDOT call centers, which will supplement telephone bookings;

Meet the minimum service levels (days, hours, wait time, and vehicle counts) stated in Section 2.2-A

B. PHASE 2 — HYBRID DEPLOYMENT (MANUAL + AV)

o Deploy a minimum of one (1) SAE Level 3 autonomous vehicle integrated into the same dispatch and booking system used in Phase 1 (See Section 2.2-A);

o Operate a unified fleet-management system capable of dynamic trip assignment across manual and autonomous vehicles;

o Maintain an integrated booking experience and consistent customer experience across manual and autonomous service types.

C. PHASE 3 — AV SERVICE EXPANSION

o Provide a minimum of two (2) autonomous shuttles meeting the Automated Vehicle

Specifications in Section 2.3 (E) for partial city coverage;

o Deliver HD mapping, validation testing, and all regulatory approvals required to operate autonomously in the service area;

o Implement ongoing performance optimization and cost-compression strategies over the contract term (See Section 2.2-A).

Because SAE Level 3 vehicles with dedicated wheelchair accessibility are not yet reliably available in the market, none of the autonomous vehicles are required to be individually wheelchair accessible. However, a minimum of one wheelchair accessible vehicle, autonomous or manual, must be in service at all times during Phase 3 (See Sections 2.2-A and 2.3-D).

Accessible service for riders who do not qualify for this Accessibili-D project who require a wheelchair-accessible vehicle is currently provided by the City at all times through the ADA-compliant manual fleet consistent with the equivalent-service standard for demand-responsive systems and will continue to be provided by the City throughout the entirety of this project.

Revised 7/28/2026 Page 6 of 27

Phase Completion and Advancement Criteria Each phase is complete, and the vendor may advance to the next phase, only upon the City's written acceptance that the criteria below have been met. All acceptances are documented and correspond to the milestone payments described in Section 5.2.

• Phase 1 is complete when: all required manual vehicles are deployed and service is fully available to eligible pilot participants; the booking application and browser-based channel are deployed and readily usable; dispatch is integrated and aligned with DDOT call centers; and at least 50 rides must have been completed.

• Advancement to Phase 2 is complete when: an agreed partial (approximately one-half) service area has been HD mapped and validated, and at least one (1) vehicle in the fleet is operating autonomously.

• Advancement to Phase 3 when: at least two (2) vehicles in the fleet are operating autonomously; the entire defined service area has been HD (High-Definition) mapped and validated; and vehicles have been operating autonomously for a minimum of 3 months.

All dates in the Project Milestones schedule remain estimates. Advancement and payment is governed by the City’s satisfaction and the acceptance criteria above, not by calendar date alone.

D. VENDOR AND CITY RESPONSIBILITIES

Vendor Responsibilities

• Provide all vehicles, staffing, dispatch, and operations required to deliver the service;

• Submit itemized invoices and required performance and ridership reports;

• Maintain insurance, licensing, and regulatory compliance throughout the term;

• Contract and manage all subcontractors

• Participate in community engagement and outreach. At the City's discretion, the successful Respondent shall participate in up to two (2) community engagement events per month for the entirety of the project, which may include collaborating with the program's Ambassador Program to onboard and intake potential riders.

• Provide and maintain a storage site to house the vehicles overnight; shall provide designated City and program personnel access to the storage site whenever the successful Respondent or a vehicle operator is on site.

• The successful Respondent shall initiate data downloads at a cadence agreed upon with the City and provide direct access to the data management platform used by the successful Respondent.

City Responsibilities

• Provide City-held information necessary to perform the service area and pickup/drop off locations (e.g., service-area data, coordination contacts);

• Review deliverables and process payments per the Contract;

• Coordinate MDOT approvals and any City infrastructure elements (e.g., wireless-charging pilots).

• DDOT call centers will supplementally handle telephone bookings.

Revised 7/28/2026 Page 7 of 27

2.2 OPERATIONAL INFORMATION

The successful Respondent will work closely with City agency staff.

The successful Respondent is expected to provide service in accordance with the terms of the executed Contract and under the rules, regulations, and supervision of the City.

A. Service Requirements

The following operational parameters define the minimum service the vendor must propose.

Respondents shall confirm their ability to meet each parameter and describe how they will do so.

Parameter Minimum Requirement Notes

Days of service Monday–Friday 7 days/week preferred.

Hours of service 8:00 AM – 5:00 PM EST Preferred: 7:00 AM – 7:00 PM, 7 days/week (see Section 2.3).

Minimum riders served Minimum of 50 riders per day serviced

Minimum daily ridership capacity the service must support.

Maximum rider wait time Maximum wait time of 45 minutes per trip

On-demand response-time standard from booking to pickup; sized for the coverage-zone geography.

Minimum vehicles in service Fleet of 3 manual vehicles, minimum 2 in service during service hours; 2 AV (Phase 3) for a total of 4 vehicles in the fleet

Must match Sections 2.1 (A-C) and 2.3.

Service area See Section 2.3 and Attachment F map

On-demand within the defined coverage zone.

Wheelchair accessibility All manual vehicles ADA-compliant with min. 1 wheelchair space; min. 1 wheelchair-accessible vehicle in service at all times

See Section 2.3 vehicle specifications and the AV accessibility note.

Booking channels Booking app (standard product acceptable) + browser booking;

telephone via DDOT call-center integration

Vendor provides the app and browser channels and owns the DDOT integration.

Revised 7/28/2026 Page 8 of 27

Applicable Standards The successful Respondent shall comply with all applicable federal, state, and local laws, ordinances, rules, and regulations, including but not limited to:

• Americans with Disabilities Act (ADA) accessibility requirements for vehicles, booking, and service;

• SAE International J3016 Levels of Driving Automation (for AV classification);

• All Federal Transit Administration (FTA) requirements and federal contract clauses applicable to MDOT-funded projects;

• Applicable Michigan Department of Transportation (MDOT) requirements and grant conditions;

• All applicable federal, state, and local motor-vehicle, licensing, and safety regulations.

Booking Platform Accessibility The booking application and browser-based booking web-based platform shall be accessible to the populations this service is intended to serve. At a minimum, the booking platform shall:

• Conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA for both the web and mobile application booking channels.

• Be screen-reader compatible and navigable using assistive technologies.

• Provide multilingual capability appropriate to the service area population for the following languages:

o Arabic, Bengali, English, Spanish, and French

• Provide an accessible means for authorized riders to request service, view schedule and status information, and be notified when service is interrupted (for example, due to weather or technical issues).

Telephone booking through DDOT call centers remains available as a supplemental alternative channel for riders who cannot or prefer not to use the application or web channel. Bookings will be exchanged manually on a case-by-case basis as determined DDOT.

Vehicle Licensing and Roadway Operation All vehicles operated under this contract must be legally permitted to operate on the public right of way. At a minimum, vehicles shall comply with all applicable National Highway Traffic Safety Administration (NHTSA) requirements and the Federal Motor Vehicle Safety Standards (FMVSS).

• If any vehicle in the proposed fleet does not fully comply with FMVSS, the Contractor must hold and provide a valid NHTSA exemption or waiver establishing the legality of operating that vehicle on the public right of way, and must maintain that authorization for the duration of such operation.

• The successful Respondent will be responsible for obtaining and maintaining all federal, state, and local licenses, permits, registrations, and approvals required to deploy and operate the vehicles, including any Michigan authorizations applicable to automated vehicle operation.

• Evidence of NHTSA/FMVSS compliance, or of a valid exemption or waiver, shall be provided to the City before any affected vehicle enters revenue service.

Revised 7/28/2026 Page 9 of 27

PROJECT MILESTONES

The milestones below represent the City’s current planning schedule for the project following contract execution. Vendors must include in their proposal a project timeline demonstrating their ability to meet these milestones, or proposing an alternative schedule with justification. All dates are estimates and are subject to the completion of the City’s procurement and award process.

Milestone Estimated Timing

Acquire operations depot; hiring and training November – December 2026

Phase 1 — Interim manual service launch Within 90 days of contract execution (target January 2027)

Phase 1 HD mapping January – March 2027

Phase 1 testing and validation April 2027

Phase 2 — Hybrid (manual + AV) deployment

May-July 2027

Phase 3 — AV service expansion (2 shuttles) August 2027 – March 2028

Contract completion (funds-limited) Approximately mid-2028

2.3 TECHNICAL INFORMATION

This section states the complete technical and service specifications for the vehicles and operations.

All items listed as “Minimum Requirements” are mandatory. The specifications below consolidate every requirement referenced elsewhere in this RFP; vendors should treat this section as the controlling technical requirement set.

The City is open to proposals in which some or all vehicles are autonomous-capable. Autonomous capability is permitted and encouraged; however, it does not alter any accessibility, staffing, or phasing requirement of this RFP. An autonomous-capable vehicle operating in manual mode is treated as a manual vehicle for all purposes under Phase 1 and counts toward the Phase 1 minimum vehicle requirements. All vehicles, regardless of autonomous capability, shall be ADA-compliant and shall enter service in manual mode until mapping and validation are complete, after which autonomous-capable vehicles are required to phase into autonomous operation as described in Phase 2. As noted prior, none of the autonomous vehicles are required to be individually wheelchair accessible.

A. Service Area The service area is a single contiguous coverage zone defined by the polygon shown on the map in Attachment F, encompassing much of Detroit's central and east side. The zone extends from the Detroit riverfront near downtown northeast along the East Jefferson and Grosse Pointe corridor, north to the Coleman A. Young International Airport and the Harper Woods edge, and west toward the New Center, North End, and Hamtramck areas, with a southwestern arm following the river toward the Clark Park/Southwest Detroit area. The coverage zone measures approximately 7.5 miles north-to-south by up to 10 miles east-to-west.

For precise reference, the coverage zone is bounded by the following approximate corner coordinates (decimal degrees), proceeding around the perimeter: (42.3124, -83.0980) at the southwest river edge; (42.3302, -83.0300) at the downtown riverfront; (42.3670, -82.9404) and (42.3878, -82.9497) along the eastern Grosse Pointe edge; (42.3949, -82.9249) and (42.4116, -82.9150) at the northeast (Harper Woods) corner; (42.4227, -82.9284) at the northernmost point; (42.4055, -82.9757) and (42.4004, -83.0108) near the airport; (42.3705, - 83.0561), (42.3857, -83.0664), (42.3893, -83.0770), and (42.3774, -83.1165) along the

Revised 7/28/2026 Page 10 of 27 western (New Center/Hamtramck) edge; and (42.3406, -83.0904) and (42.3294, -83.1069) returning along the southwestern boundary. The authoritative boundary is the polygon depicted in Appendix A.

Within this zone, blue pinpoints indicate primary pick-up locations, which are predominantly residences; green pinpoints indicate primary drop-off locations, which are destinations such as medical facilities, services, and community sites. All trips will originate and terminate within the coverage zone, and the on-demand service must be capable of serving any pairing of pick-up and drop-off points within it.

B. Wireless Charging Compatibility The Successful Respondent shall identify any vehicle(s) within the fleet portfolio pertinent to the pilot deployment that is currently compatible with, or could reasonably be adapted for, wireless (inductive) charging demonstrations. While not a requirement of this procurement, the City may pursue pilot projects with the successful Respondent during the Contract term to demonstrate interoperability with the City’s wireless charging infrastructure. Respondents should describe any relevant compatibility.

C. Service Specifications

Guideline Minimum Preferred Service capabilities On-demand service On-demand service Hours of operation Daily, 5 days/week M-F, 8:00 AM

– 5:00 PM EST

Daily, 7 days/week, 7:00 AM –

7:00 PM EST

Trip planning Booking app + web scheduling + phone scheduling via DDOT call-center integration

Same, with enhanced self-service features

Rider access controls Manually confirmed rider verification

Tech-enabled verification (RFID, location check-in)

In-vehicle trip updates Verbal updates Verbal + visual updates with online tracking

Unplanned downtime < 2 hrs/week < 30 min/week Monitor vehicle operations & safety

Daily Near real-time

Incident management system Vendor-initiated Integrated with City services (e.g., Project Green Light)

Safety attendant 1 per shuttle 1 per shuttle Site manager Remote + on-site visits On-site / locally based Vehicle inspection Daily Daily Software updates/sensor calibration/maintenance

As needed As needed

Operational support hours Daily, 5 days/week, 8:00 AM – 5:00 PM EST (Last scheduled pickup time)

Daily, 7 days/week, 7:00 AM –

7:00 PM EST

Subcontractors Vendor contracts all subcontractors

Vendor contracts all subcontractors

Field staffing approach Qualified, trained staff Workforce development / local hiring (see note)

Revised 7/28/2026 Page 11 of 27

D. Manual Vehicle Specifications

E. Automated Vehicle Specifications

For the definitions of autonomy levels referenced below, this RFP uses the SAE International J3016 Levels of Driving Automation. Level 3 ("Conditional Driving Automation") means the vehicle can perform all aspects of the dynamic driving task within its defined operational design domain, but requires a fallback-ready human operator who is receptive to a request to intervene and who responds appropriately when prompted by the system.

Guideline Minimum Requirement Preferred Powertrain Hybrid Electric Range 70 miles 120 miles Non-wheelchair passengers 3 12 Wheelchair spaces (in addition to above)

Minimum 1 2

Accessibility All vehicles ADA compliant All vehicles ADA compliant Climate controls Internal heating and cooling Internal heating and cooling Vehicle wrap Program logo/signage Program logo/signage

Guideline Minimum Requirement Preferred Autonomy level (SAE J3016) Level 3 Level 4 Powertrain Hybrid Electric Top autonomous speed 25 mph 35 mph Range 70 miles 120 miles Roadway maneuvers Must perform all maneuvers in

Attachment G

Non-wheelchair passengers (excl.

safety attendant)

3 8

Wheelchair spaces (in addition to above)

0 1

Accessibility 0 vehicles ADA compliant All vehicles ADA compliant Internal safety camera Monitoring Surveillance & alerts Safety button / stop request mechanism

Required Required

Climate controls Internal heating and cooling Internal heating and cooling Vehicle wrap Program logo/signage Program logo/signage

Revised 7/28/2026 Page 12 of 27

F. Vehicle Operator Drivers must be subject to a criminal background check performed as described more fully below. The successful Respondent shall be responsible for performing such background checks. The background checks shall include all types of felony and misdemeanor arrests and convictions, not just vehicular ones, and shall meet the standards of the City of Detroit and the State of Michigan. The drivers shall be secured by the successful Respondent and shall not be considered employees or agents of the City.

To continue operating in revenue service, each driver must, on an ongoing basis, furnish the successful Respondent with a renewed, up-to-date criminal background check, as prescribed above. Background checks must be performed at a minimum of once every two (2) years.

The following penal code infractions would trigger an individual to be disqualified from hiring.

a. any offense relating to the use, sale, possession or transportation of narcotics or addictive or dangerous drugs, including cannabis;

b. any act involving force, violence, threat or intimidation against persons;

c. any sexual offense;

d. any act involving moral turpitude, including fraud or intentional dishonesty for personal gain;

e. any offense involving the possession of a firearm or dangerous weapon;

f. any offense involving the solicitation or agreement to engage in or engagement in any act of prostitution;

g. of any offense involving resisting, delaying or obstructing a peace officer, public officer or emergency medical technician;

h. for theft in any degree;

i. any offense which results in a felony conviction;

Vehicle operators shall meet the following standards, and all standards required by the State of Michigan:

a. A driver candidate who has significant job-related convictions, including, without limitation, more than three (3) points on his or her driving record in the past three (3) years is not eligible to drive a vehicle under this contract.

b. Background checks conducted in response to this requirement must comply with all applicable state and federal regulations. The background check must be a fingerprint-based check (e.g. Live Scan) and a Federal Bureau of Investigation (FBI) check as well.

c. Drivers must have an acceptable fingerprint-based background check report on file that is no more than two (2) years old.

d. At the time of hire, drivers may not have had more than three (3) points on their recent driver record in the past 36 months. In addition, drivers may not have had any single violation of two points in the past 36 months. Once hired, drivers may have no more than two points per year. A single violation of two points may be grounds to deem a driver unqualified to provide service under the contract.

e. Possesses a valid Michigan Class A, B, or Class C driver's license, as appropriate, and current medical examination certificate for all drivers regardless of vehicles operated, as well as any other license required by applicable federal, state, and local regulations are required when operating any vehicle assigned under this contract.

Revised 7/28/2026 Page 13 of 27

f. Drivers must be able to effectively communicate in English and are required to treat all passengers with kindness, courtesy, and respect.

g. DDOT may require, in its sole discretion, that any driver be removed from transporting passengers in this contract due to any performance concern, including, but not limited to, excessive complaints, rudeness, or other inappropriate behavior or appearance.

Vehicle Operator Training:

Any driver operating within the Accessibili-D service must be "certified" in the following areas:

• Disability Awareness

• Sensitivity Training

• Passenger Assistance, Safety, and Sensitivity training (PASS)

This training may be supplemented by DDOT Paratransit trainers, or by an entity under contract to DDOT. The hours of instruction for the instructor will be paid for by DDOT.

DDOT will not directly compensate vendor time to participate in the training.

This specialized training is intended to be a supplement to the basic driver training conducted by the successful Respondent.

G. Vehicle Maintenance All maintenance and repairs of vehicles shall be completed in accordance with the City specified standards, whether performed by the Contractor or authorized subcontractors.

The successful Respondent is solely responsible for keeping all vehicles in safe, clean, and fully operational condition at all times. If any vehicle does not meet the cleanliness or safety standards as determined by the City, the successful Respondent shall remove that vehicle from revenue service at its own cost and shall not return it to service until the deficiency has been corrected. The Contractor determines and bears the cost of all required repairs. Removal of a vehicle for maintenance or safety reasons does not relieve the successful Respondent of its obligation to meet the minimum vehicles-in-service and accessibility requirements of this RFP.

DDOT, or its designee, may inspect the vehicles at any time either at the successful Respondent or subcontractor's location or while the vehicle is in service within the operating area. If, in DDOT's opinion, the vehicle does not meet the cleanliness or safety standards, it may be "red tagged," thereby preventing it from going into service, or it may be taken out of revenue service until such time as any problems associated with it have been resolved.

Each driver shall do a daily operational inspection (i.e., vehicle pre-trip) that shall comply with all State of Michigan requirements.

The successful Respondent will be responsible for ensuring all required maintenance on vehicles is conducted and completed in a satisfactory manner. The successful Respondent will be required to take all vehicles for inspection at an agreed upon location.

All vehicles shall display the logo approved by the City and the Office of Mobility Innovation on both sides of the vehicle when in service.

Revised 7/28/2026 Page 14 of 27

H. Other Duties, Responsibilities, and Requirements:

Performance Standards: The On Time Performance (OTP) standard for this service is 95% (cumulative). OTP will be measured using two (2) timepoints: the time of the request and the time of the pick-up. Compliance with the OTP Performance Standard will be measured in three (3) ways.

• 0-30 minutes at 95%

• 0-45 minutes at 97%

• 0-60 minutes at 100%

Key Performance Indicators and Reporting In addition to the On-Time Performance standard above, the successful Respondent shall track and report the following performance indicators on a monthly basis post-deployment. Reports shall be submitted to the City no later than the second Friday of each month with the exception of the first month of deployment when a report must be provided within 30 days of the first day of deployment. Definitions and reporting shall be consistent with the metrics required for demand-response (DR) service in the Federal Transit Administration's National Transit Database (NTD), so that the City's reporting to MDOT and federal agencies can draw directly from the Contractor's data.

• Unlinked passenger trips (ridership), reported monthly.

• Vehicle revenue miles and vehicle revenue hours.

• Trip denials and unmet requests (trips that could not be scheduled within service parameters).

• Trips completed, no-shows, and cancellations.

• On-time performance against the standard defined above.

• Safety and security events, including collisions, injuries, and other reportable incidents, consistent with NTD Safety & Security event reporting thresholds.

• Vehicle availability and unplanned service downtime (consistent with Section 2.3).

• Preventive maintenance completed on schedule (percentage of scheduled PM performed on time).

• Road-calls / mechanical failures affecting service.

• Customer satisfaction and complaint volume, including complaint resolution time.

Reporting cadence, formats, and data-field definitions will be finalized with the Contractor prior to launch and shall be provided in a machine-readable format suitable for the City's and MDOT's reporting obligations.

I. Drug & Alcohol Testing The successful Respondent must agree to:

1. Participate in the DDOT drug and alcohol program established in compliance with 49 CFR 653 and 654. The successful Respondent will be responsible for any costs incurred from the drug and alcohol testing.

2. To comply with the following Federal substance abuse regulations: a. Drug-Free Workplace. U.S. DOT regulations, "Drug-Free Workplace Requirements (Grants), 49 C.F.R. Part 29, Subpart F, as modified by 41 U.S.C. §§§§ 702 et seq. b. Alcohol Misuse and Drug Use. FTA regulations, "Prevention of Alcohol Misuse and Prohibited Drug Use in Transit Operations," 49 CFR Part 655, to the extent applicable.

Revised 7/28/2026 Page 15 of 27

J. Data, Privacy, Cybersecurity, and Business Continuity This service generates sensitive data about vulnerable riders. The following requirements will govern the data, its ownership and protection, and the continuity of the service itself. Proposers must describe their proposed solution and related functionality to capture and track all steps of the described processes, including but not limited to data migration, data validation, data storage, data security, auditing capabilities, reporting, case tracking, interfaces, and system requirements at the desktop and network level. The substance of the successful Respondent's response to this section will be incorporated into the final Contract.

Data Ownership

• The City owns all program data generated in the delivery of this service, including rider information, ride history and manifests, trip and dispatch records, GPS and location data, booking-system data, analytics, and all operational and performance reports. The successful Respondent will only be allowed limited permission to use this data as necessary to comply with the Contract.

• The City shall have the ability to use and govern this data as it deems necessary, including centralizing it, porting it into other systems, and using it for additional and future organizational needs.

• On expiration or termination of the contract, the successful Respondent shall return all program data to the City in a usable, non-proprietary format at no additional charge, and shall certify secure deletion of City data from successful Respondent systems, subject to any retention required by law or grant conditions.

• The successful Respondent will be required to disclose all collected data with the City.

Data Access and Standards The City is committed to centralizing and warehousing data to improve service delivery and enable cross-departmental analytics. The successful Respondent and any resulting software platforms shall enable data access, data interoperability, storing and warehousing of resulting data, and adherence to City data standards. At a minimum, the City requires:

• Access to any data via APIs in a machine-readable format. Acceptable machine-readable formats are JSON, CSV, and XML.

• Full documentation of APIs, including field names and objects, and the database schema used by the application.

• The ability for the City to push data as needed to these software systems to update base datasets.

• Any location-based data or platform shall utilize the City's base units geocoder, Base Units Database, and/or address data standards as applicable (see https://base-units-detroitmi.hub.arcgis.com/pages/about-base-units).

Additionally, the City prefers the following; any of these that are met will be factored positively into the overall score:

• The system or platform can store field-level metadata and display it in the user interface when appropriate.

• The API can provide data in a JSON format.

• Data system or data exports integrate easily with ESRI products, including feature services.

Revised 7/28/2026 Page 16 of 27

• The system or platform supports data exchanges (pushes and pulls) that can happen dynamically.

Data Sharing

• Certain data is expected to be shared with the successful Respondent in real time, while other data sets will be provided in bulk at an agreed-upon cadence. Bulk data transfers shall be accomplished using internet service, hard-wired systems, or hard-drive transfers as agreed upon with the City.

• Redactions from shared data shall be made to protect rider privacy and any successful Respondent business-sensitive information.

Rider Privacy and Data Protection

• The successful Respondent shall protect the personally identifiable information (PII) of riders and shall collect, use, and disclose rider data only as necessary to comply with the Contract or as required by law. Rider PII shall not be sold or used for any commercial purpose.

• The successful Respondent shall keep track of ridership at an individual level (for example, a check-in and check-out process) sufficient to provide a record of when an individual was onboard a vehicle, while protecting that information consistent with this section.

• The successful Respondent shall comply with all applicable federal and Michigan data-privacy and public-records obligations, including the Michigan Freedom of Information Act as it applies to records held on the City's behalf.

Software Licensing and Policies The successful Respondent shall succinctly state, and provide complete copies where the proposal would require the City to agree to them:

• The duration of any software licenses ( perpetual or at least the duration of the Contract).

• The City's rights under the license (for example, use, disclosure, sale).

• Any other license restrictions.

• Any terms or conditions within the license that contradict or conflict with the provisions of the City's contract.

• The successful Respondent’s acceptable use policies and privacy policies.

Cybersecurity

• The successful Respondent shall maintain a documented information-security program consistent with a recognized framework (for example, the NIST Cybersecurity Framework) and appropriate to the sensitivity of the data.

• At a minimum, the successful Respondent shall encrypt sensitive data in transit and at rest, enforce role-based access controls and multi-factor authentication for administrative access, and maintain audit logging of access to rider data.

• The successful Respondent's proposed solution and any hosting environment shall be subject to review by the City's Department of Innovation and Technology (DoIT), the City's cybersecurity function, and the Law Department prior to go-live, and the successful Respondent shall reasonably support that review.

Revised 7/28/2026 Page 17 of 27

• The successful Respondent shall notify the City without undue delay, and in no case later than the timeframe required by applicable Michigan law, upon discovery of any data breach or security incident affecting City or rider data, and shall cooperate in investigation and remediation.

• Any integration with City or DDOT systems, including the DDOT call-center intake, shall meet the security requirements of those systems.

Business Continuity and Disaster Recovery

• The successful Respondent shall maintain a business continuity and disaster recovery plan addressing system outages, cyber incidents, and interruption of the successful Respondent's own operations, so that transportation service and the booking channels can be restored within a defined recovery timeframe.

• The successful Respondent shall provide riders with an accessible means to learn when service is interrupted (for example, due to weather or technical failure) and, where feasible, a fallback booking or dispatch method during an outage.

• The plan shall address continuity of data (backup and recovery) such that program data is not lost in an outage or incident.

Proposers shall describe their approach to each of the above. If any item is inapplicable to the proposed solution, the proposer shall state so with a brief justification.

2.4 INSURANCE

TYPE AMOUNT NOT LESS THAN:

Automobile Liability Insurance (covering all owned, hired and non-owned vehicles with personal and property protection insurance, including residual liability insurance under Michigan no fault insurance law)

$5,000,000.00 combined single limit for bodily injury and property damage

Commercial General Liability Insurance (Broad Form Comprehensive)

$5,000,000.00 each occurrence $10,000,000.00 aggregate

Workers' Compensation Michigan Statutory minimum Employers' Liability $500,000.00 minimum each disease

$500,000.00 minimum each person $500,000.00 minimum each accident

Umbrella/Excess As determined Errors and Omissions/Cybersecurity As determined

Revised 7/28/2026 Page 18 of 27

Section 3. Proposal Evaluation and Selection Process

3.1 MINIMUM QUALIFICATIONS

Proposals will only be accepted from those firms demonstrating the following:

A minimum of three (3) years’ experience providing services of similar scope and size and provide three (3) references as proof of this experience.

A minimum of one (1) year providing public deployment with passengers. Must provide reference(s) as proof.

Evidence of ability to obtain and operate a SAE Level 3 or greater autonomous vehicle(s)

(AV)

3.2. ADHERENCE TO TERMS OF PROPOSALS

A proposal, once accepted by the City of Detroit, may become a binding contractual obligation of the Respondent. The failure of a successful Respondent to accept this obligation and to adhere to the terms of the Respondent’s proposal may result in rejection of the proposal and the cancellation of any provisional award to the respondent. Respondents are not permitted to take advantage of any errors or omissions in specifications since full instructions will be given should they be discovered before bid submission date.

3.3. PRE-BID CONFERENCE

A pre-bid conference will be held virtually. Attendance is optional. The session will be recorded and posted to the EUNA Bonfire procurement system so that all relevant vendors have access to the information presented.

3.4. QUESTION DEADLINE

All questions regarding the RFP shall be submitted through the Supplier Portal no later than the time and date specified in the solicitation. In the interest of transparency, only written questions will be accepted. Answers to questions will be posted within the Supplier Portal. The City of Detroit does not guarantee a response to questions submitted after the question deadline.

Should a Respondent be in doubt as to the true meaning of any portion of this RFP or find any patent ambiguity, inconsistency, or omission herein, the Respondent must make a written request for an official interpretation or correction in accordance with the instructions for submitting questions as specified in this RFP.

Respondents are advised that no oral interpretation, information or instruction by an officer or employee of the City of Detroit shall be binding upon the City of Detroit.

Respondents requesting changes to the RFPs terms and conditions, specifications, quantities, etc.;

or if clarifications are needed, must make the request in writing by the stated bid submission deadline.

http://www.michigan.gov/SIGMAVSS

Revised 7/28/2026 Page 19 of 27

3.5. EVALUATION CRITERIA

Technical Proposals will be evaluated before Cost Proposals are reviewed.

Proposal Evaluation Criteria Possible Points

1. Experience and Qualifications 30

2. Proposed Plan/Technical Approach 25

3. Quality and Reliability of Proposed Vehicles/Equipment 25

4. Pricing (Calculated with the following equation: lowest proposal price divided by the price of the proposal being evaluated x allotted points.) 20

Total Points Possible 100

Experience and Qualifications The City will evaluate the Respondent's organizational experience and qualifications, including:

o Organizational experience providing autonomous mobility deployment o Organizational experience providing ADA-compliant transportation services o Organizational experience managing on-demand transportation services o Experience integrating dispatch, booking, and fleet management systems o Experience performing similar work for public sector or municipal clients o Qualifications and experience of the proposed project team o Past performance on projects of similar size, scope, and complexity

Proposed Plan/Technical Approach The City will evaluate the Respondent's proposed technical approach, including:

o AV deployment strategy o Implementation schedule and project phasing o System integration with DDOT call center and booking platform o Risk mitigation and contingency planning o Safety plan and operational approach o Cybersecurity and data management approach o Business continuity and disaster recovery

Quality and Reliability of Proposed Vehicles/Equipment o Vehicle quality and reliability o ADA accessibility o Fleet maintenance o Autonomous vehicle technology o Equipment compatibility

Price o Overall proposed cost

Revised 7/28/2026 Page 20 of 27

3.6. EVALUATION PROCEDURE

Following the receipt of proposals, a City designated Evaluation Committee will evaluate each response. All PROPOSALS, which meet the required format of this RFP, will be evaluated. Any proposals determined to be non-responsive to the specifications or other requirements of the RFP, including instructions governing submission and format, will be disqualified unless the City determines, in its sole discretion, that non-compliance is not substantial or that an alternative proposed by the Respondent is acceptable.

The City may also, at its discretion, request oral presentations, make site visits at Respondent’s facility, and may request a demonstration of Respondent’s operations. If scheduled, a final determination will be made after the oral presentations and/or demonstrations are complete. The original scoring of evaluation criteria may be modified based on the presentations and/or demonstrations results.

The City may also, at its sole discretion, elect to rank order the qualified proposals, and negotiate with some limited number of the highest scored qualified respondents. A final determination would include the cumulative inputs of this evaluation procedure. All decisions reached by the Evaluation Committee will be by consensus.

Any of the additional data specs and standards described in Section 2.3 that are met will be factored positively into the overall score.

3.7. ORAL PRESENTATION/DEMONSTRATION

The City reserves the right, at its own discretion, to request oral presentations regarding proposals submitted in response to the RFP, as a means of proposal clarity. Failure to make an oral presentation will be grounds for rejection of your proposal. Respondents will be notified by the Office of Contracting and Procurement of the date, time and location for oral presentations.

3.8. REJECTIONS, MODIFICATIONS, CANCELLATIONS

The City of Detroit expressly reserves the right to:

1) accept or reject, in whole or in part, any and all proposals received;

2) waive any non-conformity;

3) re-advertise for proposals;

4) withhold the award for any reason the City determines;

5) cancel and/or postpone the request for proposals, in part or in its entirety, and/or,

6) take any other appropriate action that is in the best interest of the City.

This RFP does not commit the City of Detroit to award a contract, to pay any cost incurred in the preparation of a proposal under this request, or to procure or contract for services.

Revised 7/28/2026 Page 21 of 27

3.9. PROTESTS

Protests can be filed with the Office of Procurement. Interested parties aggrieved by a solicitation or the award of any resulting contract, may file written notice of protest to the following:

City of Detroit Chief Procurement Officer 2 Woodward Avenue, Suite 1008

Detroit, MI 48226 “Procurement Protest”

At a minimum, such protests shall include:

1) name of protestor.

2) solicitation/contract number and description; and

3) statement of grounds for protest (reference specific text in the solicitation, bid or contract document that is at issue).

An actual or prospective bidder or offeror whose direct economic interest would be affected by the award of a contract or the failure to award a contract has the right to protest any aspect of the solicitation, evaluation, or selection process of a City of Detroit procurement.

A protest by a prospective bidder which challenges the terms of the solicitation itself must be received by the City no later than 4:00 p.m. EST of the business day prior to the date scheduled for the bid closure. Failure to meet this deadline shall result in a protester waiving its ability to challenge the terms of the solicitation.

A protest by a bidder which challenges a contract award must be received no later than 4:00 p.m.

EST five (5) business days after the award of a City procurement. Failure to meet this deadline shall result in a protester waiving its ability to challenge the contract award.

All protests must be submitted in writing and received by the required timeframe.

The Chief Procurement Officer (CPO) or as delegated, the Deputy CPO, has the sole authority to respond to, decide and act upon supplier protests.

The decision of the Chief…