12-Addendum 2.pdf

1 | P a g e

CITY OF DETROIT

OFFICE OF CONTRACTING AND PROCUREMENT

REQUEST FOR PROPOSAL

RFP NO. 549315

Accessible and Autonomous Mobility Services

Addendum Two Issue Date: September 10, 2026

Questions Submitted through Oracle by September 2, 2026

This addendum is being issued to answer questions submitted by the question deadline.

I. MODIFICATIONS:

1. ADD: Addendum added with answers to submitted questions.

II. ANSWERS TO SUBMITTED QUESTIONS:

# Questions Answers 1 Section 2.3(C) sets unplanned downtime at under 2 hours per week. Please confirm whether this is measured per vehicle or fleet-wide, whether scheduled preventive maintenance and City-directed vehicle removals are excluded, and how downtime is calculated.

Per vehicle. Preventative maintenance and City-directed removals are excluded.

Downtime is calculated by the amount of time the vehicles are unavailable for service due to a mechanical failure, damage, or other condition not scheduled in advance, and then measured from the point the vehicle is removed from (or fails to enter) scheduled service until it is returned to road-ready status.

2 Will failure to meet the OTP standard or the monthly KPIs result in liquidated damages, payment deductions or default? If so, please state the mechanism, and confirm that performance is excused for force majeure, City- or DDOT-caused delay, and third-party dependencies.

This will be negotiated with successful respondent.

3 Section 2.2(A) requires a minimum of 50 riders per day, while the Phase 1 completion criterion in Section 2.1 requires that at least 50 rides have been completed. Please confirm the relationship between the two and whether the 50/day figure is a capacity obligation rather than a guaranteed-volume obligation.

50 riders per day is a capacity obligation, but for Phase 1 completion, 50 rides must have been completed to proceed to phase 2.

4 Please confirm the Michigan statutory pathway the City expects for driverless or automated operation (including any requirement to operate under the SAVE project framework or to be affiliated with a motor vehicle manufacturer), identify which entity the City expects to be the responsible party of record for the automated driving system, and describe the specific MDOT approvals the City will coordinate under its Section 2.1(D) responsibilities and the expected timeline.

There are no specific MDOT approvals needed for automated vehicles to operate under Michigan law. Common Michigan law and the Michigan vehicle code govern automated vehicle operations.

2 | P a g e

5 Section 2.3(A) requires the on-demand service to serve any pairing of pick-up and drop-off points. For autonomous trips specifically, will the City accept service to designated accessible pick-up/drop-off zones or virtual stops rather than arbitrary door-to-door curbside stops, consistent with Attachment G's reference to "designated stops or service zones"?

The City will accept, and has already planned pick-up and drop-off locations (PUDO) for the automated vehicles. The service-area polygon is a reference that encompasses the planned designated PUDOs.

6 Given ongoing roadway construction in Detroit, will the City provide advance notice of construction, closures and signal or geometry changes affecting the mapped area, and will HD map updates required by third-party roadway changes after initial validation be treated as reimbursable or as a change order rather than being absorbed within the fixed monthly rate?

Yes, and it would dependent upon contractual negotiation for the successful respondent.

7 Attachment G does not list work zones, emergency-vehicle interactions, railroad crossings, school buses, or first-responder direction. Please confirm whether these scenarios are intentionally excluded from the required maneuver set.

Please also confirm whether the Attachment G maneuvers must be demonstrated fully driverless or whether performance under the supervision of the onboard safety attendant satisfies the requirement, and whether the City will define a test and acceptance protocol for the validation testing in Section 2.3.

These interactions are not intentionally exclude. Attachment G is not limited to the maneuvers listed. Performance under supervision of a safety attendant is reasonable such that the vehicles meet SAE autonomy level 3. The City will not design a test and acceptance protocol. The responsibility for testing and validation falls under the successful respondent, and successful respondent must share said protocols with the City.

8 Will the City accept defined weather and environmental ODD limits (snow accumulation obscuring lane markings, ice, heavy precipitation, low visibility) with automatic fallback to manual operation, and confirm that trips served manually during such conditions count toward service-level and availability requirements without penalty?

Yes and yes, but manual takeovers must be reported.

9 Section 2.3(E) sets a minimum autonomous top speed of 25 mph, while significant corridors within the service area (e.g., East Jefferson) carry posted speeds of 35–45 mph. Will the City accept an ODD in which certain higher-speed segments are excluded from autonomous operation and served in manual mode, and confirm that this does not constitute non-compliance?

Yes and yes. Said segments must be shared with the City.

10 For the minimum qualifications in Section 3.1, may the required three (3) years of similar-scope experience, the one (1) year of public passenger deployment, and the evidence of ability to operate an SAE Level 3+ AV be satisfied in the aggregate by the prime, its parent/affiliates, and named subcontractors? Will deployments performed outside the United States satisfy the public-deployment reference requirement?

Yes and yes.

11 Please identify the specific funding source(s) (FTA program and/or MDOT state funds) and confirm which federal requirements flow down beyond those in Attachment H — in particular whether a DBE goal applies to this contract, whether FTA labor protections under 49 U.S.C. § 5333(b) apply to the operating workforce, and whether the City's living wage ordinance or any prevailing wage requirement applies to drivers and attendants.

The funding source is a Michigan Department of Transportation State Grant through their Office of Passenger Transit.

However, they have required us to adopt FTA requirements. MDOT approved our solicitation and all documents/requirements published in it. All of the requirements identified in attachment H apply to this solicitation, including DBE Goals. All of the parts of 49 U.S.C. referenced in attachment H apply. The living wage

3 | P a g e ordinance is not applicable to drivers, but respondents are encouraged to supply employees with competitive wages for sustainability purposes.

12 Attachment C provides a single not-to-exceed figure. Please confirm: (a) whether the total is for the full two-year term; (b) how the fixed monthly service rate and the three milestone payments should be reflected in the sheet; (c) whether Respondents may add rows (e.g., insurance, maintenance, community engagement, contingency); and (d) whether prices must be firm-fixed for the full term or whether the City will accept annual escalation and a change-in-law/tariff adjustment mechanism for imported vehicles and AV hardware.

The total is for the two year term, but operations are expected to be a minimum of 18 months.

The fixed monthly service rate should be reflected to encompass fully-loaded operations such as labor, maintenance, etc.

Respondents may add rows as they see fit.

The City is open to negotiation.

13 Who bears the cost of depot charging infrastructure (make-ready, service upgrade, chargers)? If the City pursues the wireless (inductive) charging interoperability demonstration referenced in Section 2.3(B), will that be scoped and funded as a separate change order rather than included in the fixed monthly rate?

The successful respondent would bear the cost of the infrastructure, if not already constructed at the depot. It is preferred that the option is included in the fee schedule, but the City will accept a change order and rescoping as well.

14 Does the City have a City-owned or City-controlled facility available for the operations depot? If not, are there constraints on depot location (inside the service area?), and will the City assist with permitting, zoning or utility service for EV charging capacity?

No, but the City has connections to potential depot locations. There are no constraints for depot locations so long as on time performance and minimum service operations are met. The City will assist with permitting and other mechanisms to move the project forward as needed.

15 Section 2.1(A) refers to rider eligibility being "subject to the rider-verification approach utilized by a separate contractor." Please identify that contractor and the verification system, and confirm how eligibility data will be exchanged (API, file transfer, manual), who bears the integration cost, and when that interface will be available relative to Phase 1 launch.

We cannot identify the contractor. The verification system is a self-identifying fillable form vetted by said contractor.

Eligibility data will be provided via file transfer. Integration cost will be covered by said contractor via API.

16 Is the service fare-free to riders, or is fare collection required? If fares are charged, who sets them, who collects them, and does the Contractor retain or remit the revenue? Does the fixed monthly rate assume no farebox revenue?

The service is free to eligible riders. Fixed monthly rate assumes no farebox revenue.

17 Will the City provide historical ridership data from the original Accessibili-D pilot — monthly unlinked passenger trips, average trip length and duration, origin-destination distribution, peak-hour concentration, no-show and cancellation rates, and the number of currently enrolled eligible riders?

Yes.

18 Section 2.1(A) requires deployment of the manually operated service within ninety (90) days of contract approval, while Section 2.3 places depot acquisition, hiring and training in November–December 2026. Within 90 days of contract execution a Contractor must complete: procurement of ADA-compliant accessible vehicles (chassis order plus wheelchair-accessible conversion and upfit, for which current market lead times materially exceed 90 days); securing, commissioning and insuring a depot; recruitment, fingerprint/FBI (Live Scan) background checks, PASS and disability-awareness certification of drivers; deployment of the booking application and browser channel; technical integration with the DDOT call-center intake; and the

a) Yes

b) Yes, it is preferred to launch the service as quickly as possible.

c) Timeline is a factor in the evaluation criteria.

e) d) Yes, within reason subject to negotiation.

4 | P a g e

DoIT/Law Department security review required by Section 2.3(J) prior to go-live.

a) Would the City consider extending the Phase 1 deployment period from ninety (90) to one hundred eighty (180) days?

b) Alternatively, would the City consider a phased Phase 1 launch — for example, commencing revenue service with an initial accessible vehicle within 90 days and reaching the full three-vehicle minimum within 180 days?

c) Consistent with Section 2.3, will the City confirm that a Respondent proposing a justified alternative schedule of this nature will not be scored adversely or deemed non-responsive?

d) Will delays arising from matters outside the Contractor's control — vehicle manufacturer and upfitter lead times, NHTSA/FMVSS exemption or waiver processing, Michigan automated-vehicle authorizations, the City's DoIT/Law security review, and DDOT integration dependencies — constitute excusable delay with corresponding milestone adjustment and no penalty?

19 Could the City please provide objective acceptance/test criteria, City review periods, cure/retest rights and deemed-acceptance provisions for each phase.

This will be discussed during the negotiation period of the successful respondent.

20 Could the City please provide the available project funding/budget or maximum anticipated contract value.

The City will not be disclosing the budget at this time.

21 Please clarify the reference to “per Section 8 basis” for vehicle lease/purchase pricing.

There isn’t a section 8.

22 Could the City please confirm that the requirements of RFP 549315 will prevail over inconsistent or generic references in the Technology Contract and Attachment C, and clarify the correct contract term, termination article and pricing-sheet references?

The contract attached to the RFP is a form that will be conformed to the details of the project, including the requirements of the RFP. Attachment E is a template.

Attachment C is a fillable price sheet.

Contract term, termination article and pricing-sheet references will all be discussed in the negotiation period of successful respondent.

23 Could the City please confirm whether the requirement that all System components be dedicated exclusively to the City permits the use of shared or multi-tenant cloud infrastructure and common software services, provided that City Data and the City’s tenant environment are logically segregated, access-controlled, and appropriately secured? Please confirm that Attachment C displaying RFP 549836 is the correct pricing sheet for RFP 549315 and provide a corrected version if necessary.

Attachment C has been revised. The city has limitations on applications being hosted in shard or multi-tenant cloud infrastructure with or without common software services based on the sensitivity of the data being processed / stored and operational/safety risk of the application. The most restrictive applications requiring dedicated environments include those processing data covered by CJIS, IRS Publication 1075, HIPAA, or PCI. This bid does not appear to include data of that sensitivity level. The operational and safety impact of the application do not appear to be of the level that would require dedicated environments.

5 | P a g e

24 For purposes of responding to Attachment E, could the City please confirm whether Respondents should submit contractual exceptions through an exceptions/deviations schedule, a redlined version of Attachment E, or another preferred format?

Please provide a separate, alternative schedule.

25 Could the City please confirm that City ownership of project data and Work Product will not extend to the Contractor's pre-existing or independently developed intellectual property, including proprietary software, ADS algorithms, models, platforms, tools, know-how, and other background technology?

Yes. City ownership is subject to the current project.

26 Could the City please confirm which insurance requirements and coverage limits will apply to the final Contract where the RFP and Technology Contract specify different limits? Please confirm the final controlling insurance requirements, particularly auto, CGL, umbrella/excess and cyber/E&O.

The requirements of the Contract will prevail.

27 Could the City please confirm whether it would consider including an aggregate liability cap for the contractor, with customary exceptions such as fraud, gross negligence, willful misconduct, IP infringement and confidentiality/data breaches?

The city’s default position is no limitation of liability. It is industry standard for IP infringement to be unlimited.

28 In the event of termination for convenience, will the City reimburse reasonable and documented non-cancellable project commitments, including vehicle/equipment leases, subcontractor costs, facility commitments and demobilization costs?

The City’s Default position is no, but we can negotiate reasonably.

29 Would the City consider an advance or mobilization payment upon contract execution to support upfront project costs such as vehicle commitments, depot setup, staffing, insurance, integration, and deployment preparation? If so, what percentage of the total contract value would the City consider as an advance or mobilization payment?

Yes, and this would be negotiated with the successful respondent.

30 Could the City please clarify how the fixed monthly service payments and milestone payments will interact, and confirm the deliverables associated with the Phase 3 milestone payment, including whether automated vehicle deployment and the three-month automated operating requirement are included?

The fixed monthly payments and milestone payments will happen in-parallel. Lump sum payments related to the milestones will be disbursed upon completion, and fixed monthly service payments will always be disbursed within 30 days of the City receiving a proper invoice.

31 Could the City please confirm when the 90-day period for the Phase 1 service launch begins, and whether the schedule will commence only after the Contract is fully effective and the contractor has received the applicable authorization to proceed/SPO?

The schedule will only commence after the contract with the successful respondent in executed.

32 Could the City please confirm whether objective and measurable acceptance criteria, review timelines and cure rights will be defined for each project phase and associated milestone payment?

This will be discussed during the negotiation period of the successful respondent.

33 Could the City please clarify the required level of integration with the DDOT call center, as the RFP refers both to technical integration of the dispatch platform and to telephone bookings being exchanged manually on a case-by-case basis? If technical integration is required, could the City provide the available interface/API specifications?

The level of integration is dependent upon the type of platform being used.

6 | P a g e

34 Could the City please clarify how the 45-minute maximum wait time should be interpreted in relation to the OTP table, which allows up to 3% of trips to fall between 45 and 60 minutes?

The 3% of trips allowed to fall between the 45-60 minute period will be denoted as “delayed” trips. Passed 60 minutes, the trips will be considered “severely delayed”

35 Could the City please clarify whether the requirement to serve a minimum of 50 riders per day is a required service capacity or a minimum actual completed ridership KPI, particularly where actual rider demand is outside the contractor's control?

It is a service capacity requirement.

36 Could the City please confirm whether the Phase 1 manual transportation operation, including vehicles, drivers and related operations, may be performed through a qualified subcontracted/local operating partner under the prime contractor's responsibility?

Yes.

37 Could the City please confirm which Buy America requirements apply to this procurement, specifically with respect to vehicles, leased vehicles, automated driving hardware, sensors, computing equipment and software, and whether any applicable waiver or exemption pathway is available?

Buy America does not apply to this bid.

38 The RFP refers to two AVs providing 'partial city coverage,' while the Phase 3 acceptance criteria require the entire defined service area to be HD mapped and validated. Could the City please clarify the expected automated operational coverage during Phase 3?

Partial city coverage refers to the ODD, which encompasses the greater downtown and east side. Expectations include the ability to add pick up and drop off locations as requested by the City within the footprint. A list of locations will be provided.

39 Could the City please confirm whether the automated vehicles are expected to serve any origin-destination pairing across the entire defined service area, or whether specific AV routes/corridors or operational zones may be agreed and progressively expanded?

The vehicles are ultimately expected to serve any pairing, but the City is open to negotiating progressive AV expansion.

40 Do you anticipate the RFP deadline being extended, as the answers to questions' release date is too close to the deadline, or should we plan for the September 18 deadline to remain as scheduled?

An addendum was sent out to shift the submission deadline to 9/30/2026 by 2:00pm EST.

41 The RFP refers to three manual vehicles and two AVs in Phase 3, while also stating a total fleet of four vehicles. Could the City please confirm the required fleet composition and minimum number of vehicles by phase? Is the minimum fleet four vehicles total or three manual vehicles plus two AVs?

The minimum total is 4 vehicles, with at least 2 of those vehicles being AV. One of the 3 manual vehicles would be expected to be replaced by an AV.

42 Could the City please confirm whether the manual vehicles deployed in Phase 1 may be different from the automated vehicles introduced in Phases 2 and 3, or whether the same autonomous-capable vehicles are expected to transition from manual to automated operation?

Yes, they may be different.

43 Just to reiterate and clarify, will submitted RFP responses be made publicly available? If so, would we be permitted to submit a redacted version to protect sensitive or confidential information?

Submitted RFP are subject to the Freedom of Information Act (FOIA), meaning there is a possibility the responses could be requested by someone. If a redacted version is submitted, the City will evaluate the response appropriately against the grading mechanism.

7 | P a g e

44 Do you anticipate any extension to the RFP submission deadline, or is the current September 18 deadline expected to remain firm?

An addendum was sent out to shift the

45 Proof of vehicle procurement or lease agreement:

What would the City view as evidence of the above:

1) Purchase order for the vehicles from leasing entity to vehicle manufacturer?

2) Letter from HOLON's Managing Director confirming availability of the vehicles by May 2027?

The City would prefer a purchase order for the vehicles indicating the date the vehicles would be available.

46 Can the City indicate the anticipated annual contract value or budget envelope for this project?

The City will not disclose budget at this time.

47 Can the City provider ridership data from the original Accessibili-D pilot, including trip volumes, origin and destination patterns, wheelchair accessible trip share and peak demand profile?

Yes.

48 If we have concerns about the mentioned attachments but don't have enough time for the specialist counsel to review, would the city consider some changes after submission/at award OR is the City of Detroit 'Firm' on their documents?

An addendum was sent out to shift the submission deadline to 9/30/2026 by 2:00pm EST.

49 Could the deadline submission be extended by two weeks, given all the documents to be revised by legal, commercial and procurement teams?

An addendum was sent out to shift the

50 What trip booking/scheduling application does the City of Detroit currently use?

Ecolane.

51 May the five-year landscaping/tree-planting-and-care experience requirement be satisfied through a named major subcontractor, teaming partner or joint-venture member, or must the prime respondent independently possess the full five years? This question is not relevant to the current RFP.

This question is not relevant to the current

RFP.

52 At the conclusion of the pilot, what software, licenses, APIs, databases, dashboards, source data, documentation, and other technology must remain available to the City?

The City will own all non-proprietary technology and data at the conclusion of this project. All data and technology must be provided to the City with documentation, including schema, data dictionary, and other documentation needed to utilize.

53 What technical interface, API, workflow, staffing, and data-exchange requirements apply to integration with the DDOT call center?

This is dependent upon the platform used by the respondents.

API Schema requires secure, Restful endpoint communication via JSON over HTTPS to support the following:

• Create a Booking Request (POST /API/v1/trips/book) including checking Vehicle Capacity, validate accessibility needs, pick-up and dropoff location and time, 8 | P a g e and log the trip information directly into the AV Fleet Management engine.

• Ride Status & Telemetry Webhook (POST /API/v1/webhooks/ride-status) including booking ID ,Vehicle ID, Status, Telemetry, ETA, capacity available Wheelchair slots, and alerts.

Staffing:

• Dedicated AV Mobility

Dispatchers to monitor live and digital dashboards and voice queues and maintain communication with on-board autonomous safety Operator.

Certified in ADA paratransit rules and handles multi language requests.

• Level 2 / Tier 2 technical support staff for resolving API disconnects or vehicle telemetry and communication issues.

• On-Board safety operators to take over for safety issues, re-routes, trip interruptions and communicate with Dispatchers.

Data Exchange Requirements

• Privacy - Secure, encrypted exchange (HTTPS/TLS 1.3) adhering strictly to Nondisclosure Agreements and Detroit data privacy rules.

• Telemetry - Real-time GPS coordinates, vehicle speed, occupancy levels, and space availability via secure API webhooks.

• Accessibility - Detailed payload mapping specific needs (e.g., motorized wheelchair, service animal, boarding ramp request).

• Reporting - Comprehensive data packages covering total rides, response times, safety notifications, and ride satisfaction analytics.

Dispatch Workflows

• Rider contacts Dispatch Center

• Agent Captures details, pick-up , drop-off , Mobility Needs then

9 | P a g e checks if the route is in the AV area and Weather.

o If Weather is not clear or route is outside Geofence AV Area, “Route to Manual Backup Fleet” o Dispatch Accessible Van / Taxi o If Weather is clear, Query AV Fleet Capacity and in the Geofence AV area.

o Query AV Fleet Capacity

API

o Assign and dispatch AV vehicle if available and meets ADA requirements or

Route to manual Backup fleet or Dispatch Accessible Van / Taxi o Monitor Live Ride.

o If the ride is normal (AV arrives, Ramps Deploy, trip ends) o Trip complete - Log Analytics and

Performance Data o If Exception Detected, Call center

Escalation Deploy Manual Vehicle Dispatch to Pick up rider.

o Trip complete – Log Analytics and Performance Data

Technology Requirements:

• Any requirements for connectivity to and from application provider and end users, o Infrastructure / Network Connectivity (VPN/VPN Tunnel) o Ports o Firewall requirements o Browsers o Desktop Application(s)

54 What City-owned assets will be available to the successful respondent—depot space, charging infrastructure, parking, communications infrastructure, office space, dispatch resources, or other facilities?

The Detroit Charge Ahead | City of Detroit link provides visibility for our free level 2 charging infrastructure available for successful respondent.

55 Is actual use of the City's inductive charging infrastructure a mandatory performance requirement, or is demonstrated technical compatibility sufficient?

Use of the inductive charging infrastructure is not mandatory. The demonstrated technical compatibility is sufficient.

56 Who owns the HD maps, validation data, operational data, and other mapping assets developed using City contract funds?

The City will own all non-proprietary technology and data at the conclusion of this project.

https://detroitmi.gov/government/mayors-office/office-mobility-innovation/detroit-charge-ahead

10 | P a g e

57 Should respondents price only the minimum service area shown in the RFP, or should proposals include an optional price for expanded geographic coverage?

Does the City anticipate expanding the service area during the two-year pilot?

Expanded optional geographic coverage is welcomed. The City plans on first grounding the service in sustainable funding before assessing geographic expansion.

58 Must every autonomous vehicle proposed be wheelchair accessible, or may the overall fleet contain a combination of accessible and non-accessible AVs provided accessible service remains available at all times?

No, the overall fleet may contain a combination of accessible and non-accessible AVs.

59 As the service transitions into Phases 2 and 3, do the autonomous vehicles supplement the Phase 1 manual fleet, or may AVs replace manual vehicles while maintaining the City's required minimum in-service capacity?

The total fleet needs to have at least 4 vehicles with a minimum of 2 of those vehicles demonstrating level 3 or higher AV capability by phase 3. AVs may replace manual vehicles so long as ADA requirements of the service are met.

60 Is the requirement to accommodate at least 50 riders per day a guaranteed service demand, a minimum available system capacity, or a performance requirement regardless of actual rider requests?

Minimum 50 riders per day is a minimum available system capacity and performance requirement.

61 Will the City provide historical operating data from the original Accessibili-D pilot, including monthly ridership, trips per day, peak demand periods, average trip distance, average wait time, cancellations/no-shows, wheelchair trips, service hours, cost per ride, and origin/destination patterns?

Yes.

62 What specific acceptance criteria will Detroit use to authorize progression from Phase 1 to Phase 2 and from Phase 2 to Phase 3?

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.

63 If Phase 2 or Phase 3 is delayed because of regulatory approvals, permitting, mapping approvals, or another matter outside the contractor's reasonable control, will the contractor continue to be compensated for Phase 1/manual operations? Would such a regulatory delay constitute contractor nonperformance?

This is an item that would be discussed during the negotiation period for the successful respondent.

64 May the minimum qualifications be satisfied collectively through a formal joint venture, teaming arrangement, or named major subcontractor, or must the prime respondent independently satisfy each minimum qualification?

Yes.

11 | P a g e

65 The introductory language in Section 2.3 states that all vehicles, regardless of autonomous capability, shall be ADA-compliant. Section 2.3(E), however, lists the minimum accessibility requirement for automated vehicles as “0 vehicles ADA compliant,” and Section 2.1(C) states that autonomous vehicles are not required to be individually wheelchair accessible. Please clarify the controlling accessibility requirement for automated vehicles and, if appropriate, issue corrected language by addendum.

Autonomous vehicles are NOT required to be wheelchair accessible, rather, the system as a whole must be ADA compliant. This means that there must be a minimum of one wheelchair accessible vehicle in the fleet regardless of AV capabilities.

66 Section 2.2(A), Minimum Vehicles in Service, requires a fleet of three manual vehicles and two automated vehicles in Phase 3, “for a total of 4 vehicles in the fleet.” Three manual vehicles plus two automated vehicles would total five vehicles. Please clarify the minimum total fleet required during Phase 3 and whether an automated vehicle is intended to replace or result from the conversion of one of the Phase 1 manual vehicles.

An automated vehicle is intended to replace one of the 3 manual vehicles. There should be a minimum total fleet of 4 vehicles and at least 2 of those vehicles being automated.

67 Attachment C – Price Sheet is labeled “City of Detroit Price Sheet | RFP 549836,” while the solicitation and other attachments identify this procurement as RFP 549315. Please confirm that Attachment C applies to RFP 549315 and advise whether a corrected price sheet will be issued.

The attachment C has been revised.

68 Please clarify the required retention period and exportability of internal safety-camera footage and whether it must be time-synchronized with vehicle-state and intervention logs. Please also clarify whether a City-designated academic evaluator may publish findings from deidentified program data, subject to agreed privacy, security, and City review requirements.

The City requires that all internal safety-camera footage be available and usable in the event of an incident. To be usable in the event of an incident it should be time-synchronized with other systems and logs.

The data should be retained for a minimum of 90 days and in the event of an incident all logs and video related to the incident be exported for archival in mutually agreed upon formats. No video or data can be part of any publication without first being approved by the Mayors Communications Department.

69 Must trip-level exports include a stable deidentified rider identifier; trip purpose; mobility-device, securement, and assistance information; booking channel; request, assignment, arrival, pickup, and drop-off timestamps; trip disposition; and cancellation, denial, or failure reason codes?

Yes.

70 Must the successful respondent retain and export timestamped records of requested operating state, actual operating state, system-health state, manual takeovers, operator interventions, remote-assistance events, controlled stops, fallback events, and associated reason codes? Must vehicle miles and hours be reported separately by manual and autonomous operating mode?

Yes and Yes.

71 Does the City anticipate designating an independent academic evaluator for Accessibili-D 2.0? If so, will the successful respondent be required to cooperate with that evaluator and provide timely access to deidentified trip-level data, operational records, platform documentation, and relevant personnel

Yes and Yes.

72 To help mitigate potential trip denials and maximize service reliability for eligible riders, would the City consider allowing the selected vendor to partner with Transportation Network Companies (TNCs) to handle overflow demand?

Yes.

12 | P a g e

73 What documentation will the City accept as sufficient evidence that a respondent has the ability to obtain and operate SAE Level 3 or greater autonomous vehicles? Also... Must the proposed autonomous vehicles already be commercially deployed at the time of proposal submission, or may a respondent identify vehicles that will be acquired, leased, or provided through an AV technology partner after award?

Deployment experience and any media attached to said deployment experience.

The proposed autonomous vehicles may identify the vehicles that will be acquired, leased, or provided after award, but it is not preferred.