RFP-26-009-FH_Addendum_No._1.pdf

RFP-26-009-FH

CraneRIDES Operator Services

Addendum No. 1

DATE: February 11, 2026 TO: All Respondents and Interested Parties FROM: Fabio Henao, CPO

Be advised of the following changes, additions, deletions, information, and/or clarifications to the subject solicitation. Only written questions answered in writing by formal Addendum will be binding. Oral and other interpretations or clarifications will be without legal effect. Questions received after the due date for questions will not be given any consideration. Respondents are reminded to review the original solicitation and all issued addenda, if applicable. Respondents must acknowledge all issued addenda, if any. Failure to acknowledge may result in the Respondent’s submittal being deemed non-responsive.

The Solicitation is hereby changed accordingly:

A. THE DUE DATE FOR THE PROPOSALS IS HEREBY EXTENDED AS LISTED BELOW:

From: February 17, 2026, by 11:00 a.m. ET

TO: FEBRUARY 24, 2026, BY 11:00 A.M. ET

B. QUESTIONS RECEIVED:

Q1: What is the desired timeline for the start of on-demand service and all associated requirements like GTFS-Flex?

A1: There is no timeline at the moment for on-demand services. The requirements and expectations for on-demand service, including any GTFS-Flex-related deliverables are addressed in the Solicitation Exhibits, including Exhibit A and Exhibit D. Bidders shall base their response on those Exhibits.

Q2: When is the East Altamonte route expansion expected to be added to the route network?

A2: There is no timeline at the moment for the East Altamonte route expansion. The implementation shall be in accordance with the contact and the requirements identified in the Solicitation Exhibits. Bidders should assume the City will coordinate final implementation timing with the selected vendor. The Bidder should include the operational and capital cost and project plan associated with the operation of the East Altamonte Route in addition to main CraneRIDES route.

Q3: Under Quality of Service, service uptime of 99% is mentioned, but under Service Uptime and Continuity, a minimum of 95% uptime is required. Can the City please clarify the discrepancy between the two?

A3: Quality-of-service performance requirements shall maintain a minimum 95% uptime.

Q4: What are the expectations of the required LED lighting features on the exterior?

A4: Bidders shall address lighting/visibility features as part of the Project Aesthetics requirement and provide renderings and narrative describing the proposed treatment (including embedded lighting, as applicable).

Q5: Do all vehicle requirements, like passenger capacity, apply to future fleets for use cases like on-demand? If not, are there any vehicle requirements applicable to on-demand?

A5: Vehicle requirements (including any future fleet and/or on-demand service needs) are defined in the Solicitation scope requirements, including Exhibit A. Bidders must include vehicle specifications, operational assumptions, and any supporting systems/infrastructure needed to deliver the service. Requirements outlined in the RFP are the requirements at the current state for the entire fleet.

Q6: How does the City define redundancy requirements for signal phases?

A6: Seminole County maintains the traffic signals within the project area. The City cannot require Seminole County to install, modify, or add third-party equipment at County-maintained signal locations. Proposers shall not assume that additional signal equipment, communication devices, or other infrastructure will be installed by the County to support the service.

It is the Contractor’s responsibility to provide an operational approach and technical solution that safely serves the project area with appropriate redundancy and continuity of operations. The proposed solution shall account for existing field conditions and third-party constraints and include fallback/safe-mode strategies to maintain safe operations when desired signal integrations or connectivity are not available.

Q7: What are the anticipated hours of operation for the 7-day service schedule?

A7: Operating days and service expectations are defined clearly in the scope requirements in Exhibit A. Bidders shall include the proposed staffing plan, service delivery approach, and hours of operation consistent with those requirements and stated here: Monday through Friday from 7:00AM to 9:00PM and weekends from 10:00AM to 2:00PM and 4:00PM to 10:00PM.

Q8: Will the City contract with FDOT and Seminole County for integration or would that fall to the vendor?

A8: The City will manage coordination with partner agencies (including FDOT and Seminole

County) as needed. The selected vendor will be responsible for supporting integration and coordination efforts required to deliver the services described in the RFP scope and contract requirements.

Q9: Please confirm that the City plans to integrate standardized transit data feeds (e.g., GTFS and GTFS-RT) to support their internal website updates such as service alerts and detours.

A9: Yes. GTFS-related deliverables are included in the Solicitation package. Bidders shall comply with the requirements in Exhibit D and any associated scope requirements in Exhibit A.

Q10: Please confirm that temporary route modifications for construction, extensions, or special events are expected to utilize routes mapped as part of the initial core service launch, and that any additional routing not previously mapped will require a change order.

A10: Temporary route modifications that remain within the contacted scope may be handled operationally through coordination with the City. Modifications that change the contractual scope, deliverables, or requirements may require a contract amendment/ change order consistent with the Solicitation and resulting agreement. The Proposer/Contractor is responsible for maintaining continuous service delivery. During special events or other conditions that result in roadway or access closures, the Contractor shall implement an alternate “event route” or detour routing necessary to maintain safe, reliable operations and passenger access to the extent practicable. The Contractor is responsible for proactively identifying potential conflicts (including planned road closures, event impacts, and temporary access restrictions), coordinating with the City as needed, and ensuring the service remains operational.

Temporary routing changes made to preserve operations during events and closures may be implemented without a contract amendment provided the change remains within the intent of the service and does not materially change the contract scope, fleet requirements, or pricing. Changes that materially modify the scope, service area, service level, or contractual deliverables may require a contract amendment/change order in accordance with the Solicitation and resulting agreement.

Q11: Are all stations ADA compliant? If not, who is responsible for assuring compliance?

A11: ADA requirements and any associated station/stop responsibilities will be maintained by the City. The vendor is responsible for relaying ADA concerns or issues along the route and/or stops with the City.

Q12: Is the City responsible for all route signage?

A12: The City is responsible for all route signage.

Q13: Is the proposer financially responsible for capital and recurring costs of upgraded or new installation for storage and charging infrastructure?

A13: All bidders must identify all infrastructure needed to support operations (including charging and storage needs) and include those assumptions and responsibilities clearly in their proposal. Allocation of responsibilities will be governed by the contract and the Scope of Services. If specific cost responsibility is not explicitly stated in the scope, bidders should clearly state assumptions in their pricing and approach.

Q14: Will the City accept a two-week deadline extension request?

A14: The City will accept a one-week deadline extension.