Taxi_RCS_Document_PDF.pdf

REVENUE CONTRACT SOLICITATION

RCS 25-0612

TAXICAB SERVICES AT PHOENIX SKY HARBOR

INTERNATIONAL AIRPORT

City of Phoenix Aviation Department 2485 E. Buckeye Rd Phoenix, AZ 85034

RELEASE DATE: June 27, 2025

DEADLINE FOR QUESTIONS: July 18, 2025, 1:00 pm

RESPONSE DEADLINE: August 19, 2025, 11:00 am

City of Phoenix

REVENUE CONTRACT SOLICITATION

RCS 25-0612

Taxicab Services at Phoenix Sky Harbor International Airport

1. Introduction

2. Group 1 - Large Company Requirements

3. Group 2A - Small Company - 100% Owner Operator Company Requirements

4. Group 2B - Small Company - Non - 100% Owner Operator Company Requirements

5. General Terms and Conditions of the RCS - All Groups

6. Respondent Questionnaire Attachments:

A - AFFIDAVIT

B - LETTER OF DECLARATION

C - CONFLICT OF INTEREST AND TRANSPARENCY FORM

D - BUSINESS REFERENCES

E - ESTABLISHED BUSINESS FORM

F - QUALIFICATIONS AND EXPERIENCE OF RESPONDENT - GROUP 1 - LARGE

COMPANY

G - QUALIFICATIONS AND EXPERIENCE OF GM - GROUP 1 - LARGE COMPANY

H - QUALIFICATIONS AND EXP OF RESPONDENT - GROUP 2 - SMALL COMPANY

I - QUALIFICATIONS AND EXP OF GM – GROUP 2 - SMALL COMPANY

J – DRAFT AGREEMENT – GROUP 1 - LARGE COMPANY

K – DRAFT AGREEMENT – GROUP 2A – SMALL COMPANY – 100% OWNER/OPERATOR

L – DRAFT AGREEMENT – GROUP 2B – SMALL COMPANY – NON-100%

OWNER/OPERATOR

Revenue Contract Solicitation #25-0612 Title: Taxicab Services at Phoenix Sky Harbor International Airport

1. Introduction The City of Phoenix (City) Aviation Department (Aviation) is seeking responses from qualified Respondents to provide taxicab services at Phoenix Sky Harbor International Airport (Airport or PHX). The Successful Respondent will enter into an Agreement (Contract or Agreement) with the City. Copies of the draft Agreements are attached as Attachments J, K, and L.

The City encourages competition in all of its solicitations. The City’s desired outcomes from this solicitation process are to:

• Provide passengers with high quality transportation services twenty-four hours per day, seven (7) days a week, including holidays.

• Incorporate the Airport's sustainability initiatives.

• Increase opportunity for local and small business participation.

• Provide high quality customer service and accessible transportation options for passengers with disabilities.

• Incorporate new technologies, including new security and payment options.

• Select Respondents, including their joint venture partner(s) (if any), who have experience in the successful operation of taxicab services operations.

• Select Respondents based on a number of factors including Respondents’ ability to provide the highest quality customer service, safety, and convenience to the traveling public, in addition to the expectation of reasonable revenues.

Selection will be based on the entire Response and the Evaluation Criteria. All Respondents must demonstrate not only taxicab service experience and financial capability but also demonstrate experience and capability to provide customer service initiatives that will enhance the customer experience.

1.1. Background

Pursuant to Chapter 4, Article IV of the Phoenix City Code, the City has the authority to promulgate and enforce ground transportation regulations and issue operating privileges for taxicab services at Phoenix Sky Harbor International Airport (PHX).

PHX is the 5th busiest airport in the U.S. in terms of operations, serving over 52 million passengers through two terminals in calendar year 2024. As the largest economic engine in the State of Arizona, Phoenix Sky Harbor International Airport strives to deliver a world-class experience to every customer every day. PHX is America’s Friendliest Airport® and strives to ensure that all services provided meet those standards. More PHX statistics are available at https://www.skyharbor.com/About/Information/AirportStatistics.

https://www.skyharbor.com/About/Information/AirportStatistics http://phxskyharbor.com/about/AirportStats.html

The City anticipates entering into four (4) contracts to provide taxicab services at PHX. These four contracts include two (2) Large Company contract opportunities and two (2) small company contract opportunities. Below is a list of these four contract opportunities with their required fleet sizes, for a total base fleet of 190 vehicles to be operated at PHX.

CONTRACTING OPPORTUNITIES

GROUP #

# OF CONTRACTS

TO BE AWARDED COMPANY SIZE

REQUIRED

FLEET

GROUP #1 2 LARGE COMPANY (60 per contract) 120

GROUP #2A 1

SMALL COMPANY - 100%

OWNER/OPERATOR 35

GROUP #2B 1

SMALL COMPANY - NON-100%

OWNER/OPERATOR 35

TOTAL BASE FLEET 190

The small company contract opportunities are limited to Respondents that meet the Small Business Administration (SBA) small business size standards for North American Industry Classification System (NAICS) Code 485310—Taxi Service. This industry comprises establishments primarily engaged in providing passenger transportation by automobile or van, not operated over regular routes or on regular schedules. The average gross sales receipts over the past five (5) years for the Respondent must not exceed $19 million per year to be considered a small business.

One of the two small company contract opportunities is reserved for a small business respondent whose ownership consists of 100% owner/operators. However, if one or more of the four (4) contracts are not awarded, then the City reserves the right to allocate all or some portion of the base fleet for that contract opportunity to one or more of the other responsive and responsible Respondents in a manner that best meets the City's operational needs. If the City allocates all or some portion of the base fleet for a Contract opportunity that was not awarded, City may allocate vehicles to Contractors using an equal percentage to each Contractor’s base fleet.

The City reserves the right during the term of the Contract(s) to decrease and increase the number of vehicles in each Contractor's fleet to best meet the City's operational needs due to seasonal demands. At the sole discretion of the Aviation Director, the adjustment will be applied using an equal percentage to each Contractor’s base fleet.

The Airport Ground Transportation Office background and statistical data for the last three (3) years of outbound trips conducted by the current taxicab services providers is shown below:

The City makes no representation or warranties, expressed or implied, as to the accuracy or relevancy of the statistical data. The Respondent assumes all risk associated with using the data, including its accuracy, relevance, and/or materiality to the formulation of its Response.

1.2. Schedule of Events

The City reserves the right to change dates, times, and locations, as necessary. The City does not always hold a Pre-Offer Conference or Site Visit. All times in the Schedule of Events are Local Phoenix, AZ Time.

To request a reasonable accommodation or alternative format for any public meeting, please contact the Procurement Officer (Amy Turner) at (602) 273-3349/Voice or 711/TTY, or amy.m.turner@phoenix.gov, no later than one (1) week prior to the meeting.

Solicitation Issue Date: June 27, 2025

Pre-Proposal Conference (Non-Mandatory): July 8, 2025, 10:30am

Hybrid: Via Webex and at Aviation Headquarters Building:

2485 E Buckeye Road Phoenix, AZ 85034

To RSVP**:

https://cityofphoenix.webex.com/weblink/regi ster/r24dd9caca6053aaec5bc9cd0083629bf

(Meeting details will be forward upon RSVP)

Written Inquiries Due Date: July 18, 2025, 1:00pm

Proposal Due Date: August 19, 2025, 11:00am https://procurement.opengov.com/portal/phoe nix/projects/155684

Public Proposal Opening will be held at 11:30a.m.

Join online:

https://cityofphoenix.webex.com/cityofphoeni x/j.php?MTID=mcb23ae1fce056e3b748d2ae 8f507b5b9

Join by phone:

+1-415-655-0001 US Toll

Access code: 2334 606 6665

Evaluations of Response/Offers: October 2025

City Council Approval: April 2026

**Please Note: Registration or RSVP to participate in the Pre-Response Meeting is required in order to obtain the Pre-Response Meeting information. A Respondent who wishes to join the Pre- Response Meeting for this Solicitation is required to register using the weblink or access code provided prior to the meeting. Upon completion of registration, the Pre-Response Meeting information will be forwarded to the registered email address.

https://cityofphoenix.webex.com/weblink/register/r24dd9caca6053aaec5bc9cd0083629bf https://cityofphoenix.webex.com/weblink/register/r24dd9caca6053aaec5bc9cd0083629bf https://procurement.opengov.com/portal/phoenix/projects/155684 https://procurement.opengov.com/portal/phoenix/projects/155684 https://cityofphoenix.webex.com/cityofphoenix/j.php?MTID=mcb23ae1fce056e3b748d2ae8f507b5b9 https://cityofphoenix.webex.com/cityofphoenix/j.php?MTID=mcb23ae1fce056e3b748d2ae8f507b5b9 https://cityofphoenix.webex.com/cityofphoenix/j.php?MTID=mcb23ae1fce056e3b748d2ae8f507b5b9

1.3. Definitions

The following definitions apply to this Revenue Contract Solicitation (RCS). There are additional definitions in the attachments, exhibits and appendices. If there is a conflict between these definitions and the definitions in the attachments, exhibits and appendices then the definitions in the attachments, exhibits, and appendices govern those documents.

AGREEMENT OR CONTRACT includes any and all City of Phoenix Aviation Department contracts, subcontracts, agreements, leases, subleases, licenses, permits, concessions or other documents, however denominated that grant or convey a right or privilege on an Airport.

AGGRIEVED PARTY means a person or a business that intends a Response that alleges a mistake, impropriety or defect in the Solicitation will harm the person or business.

AIRPORT means Phoenix Sky Harbor International Airport, Phoenix Deer Valley Airport and/or Phoenix Goodyear Airport, in accordance with the context of the Contract.

AVIATION DEPARTMENT means the city of Phoenix Department responsible for the solicitation and contract management of any resulting agreement.

COMMERCIAL HOLD LOT(C-LOT) means parking area where taxis stage prior to being dispatched for a taxi service request

DAYS means calendar days, except as otherwise expressly provided in this RCS.

DISCUSSIONS means an exchange between the Procurement Officer and one or more Respondents submitting Responses determined to be Reasonably Susceptible Responses.

FRANCHISEE or OWNER/OPERATOR means the business granted (for a periodic fee or share of profits) the right to operate taxicab services, at PHX under the Contractor’s name. Franchisee is used interchangeably with Owner/Operator throughout this document.

GOOD CAUSE means substantial grounds or evidence based upon facts not in dispute as determined by the Procurement Officer that the failure by an aggrieved party or a Respondent to submit a timely Response, protest or appeal was beyond its control due to misinformation relayed in writing by a city employee.

JOINT VENTURE (JV) means an association between two or more persons, partnerships, corporations, or any combination thereof, formed to carry on a single business activity.

PHX means Phoenix Sky Harbor International Airport

PHX SKY TRAIN means the automated train that transports passengers throughout the Airport

OWNER/OPERATOR Any individual or small business who independently owns and operates a passenger fleet vehicle used for transporting customers

REASONABLY SUSCEPTIBLE RESPONSE means a Response that, based on the evaluation criteria, has a substantial chance of resulting in a contract award.

RESPONDENT/OFFEROR means an individual, partnership, JV, corporation or firm that submits a Response to the City to perform services requested by a Revenue Contract Solicitation (RCS).

RESPONSE/OFFER means a written response to this RCS.

RESPONSIBLE means to be fully capable of meeting all of the requirements of the Solicitation, including possessing the capacity, operational and financial capability, and integrity to perform as contractually required.

RESPONSIVE means an offer or Response that on its face satisfies all material requirements of the Solicitation.

REVENUE CONTRACT SOLICITATION (RCS) A solicitation for revenue contracts, including all amendments or supplements thereto.

SUBCONTRACTOR means an individual, partnership, JV, corporation or firm that holds a contract at any tier below the Lease, including a vendor under a purchase order.

SUCCESSFUL RESPONDENT means an individual, corporation, firm or JV that has been selected by the City to perform services requested by a RCS.

1.4. Good Standing

Any Respondent and Partners, as defined in the ”Response Limitation to this RCS section”, that currently contracts with the City must be in good standing for its Response to be considered responsive. For purposes of this RCS, good standing refers to compliance with all contractual provisions, including payment of financial obligations.

1.5. City’s Vendor Self-Registration and Notification

Vendors must be registered in the City’s Procurement Portal at https://procurement.opengov.com/portal/phoenix to respond to solicitations and access procurement information.

Vendors must also be registered in the City’s procurePHX Self-Registration System at https://www.phoenix.gov/procure prior to contract execution.

1.6. Equal Pay Requirements

In 2015, Phoenix City Council amended Phoenix City Code Section IV, Article V, 18-21 Equal Opportunity Requirements, known as the Equal Pay Act, to define expectations of all Contractors with the City of Phoenix. Attachment B - Letter of Declaration (Equal Pay) details the Act, as well as Federal and State provisions. As part of the Response for this RCS, Respondents are required to provide information on how they support, communicate, ensure and comply with these requirements. Respondents are expected to be as detailed as possible.

https://procurement.opengov.com/portal/phoenix https://www.phoenix.gov/procure

1.7. Contract Term and Contractual Relationship

The information in this RCS is not intended to completely define the proposed contractual relationship to be entered into by the City and the Successful Respondent. The Agreement terms may be amended at the sole discretion of the City at any time during the RCS process and/or prior to execution of the Agreement.

The Agreement will be effective upon the date of execution by the City (Effective Date). The Primary Term of the Agreement will be for five (5) -years with one 2-year option to extend, which shall be exercised at the sole discretion of the Aviation Director.

Respondents are advised to read the draft Agreements included as Attachments J, K and L to which the Successful Respondent and its Partners, as defined in the ”Response Limitation to This RCS” section shall be bound. See Attachment A – Affidavit, Paragraph 12 of Assurances.

This RCS is for a non-exclusive Agreement with the City. The City will not enter into an exclusive Agreement with a Successful Respondent. At any time, the City has the right to award Agreements to other operators for taxicab services to operate at the Airport.

1.8. Pre-Proposal Meeting

Respondents are strongly encouraged to attend the Pre-Response meeting that will be held via WebEx and in person at the City of Phoenix Aviation Department Headquarters, Phoenix Aviation Advisory Board (PAAB) Room, located at 2485 East Buckeye Road, on the date, time, and meeting link listed in the Schedule of Events.

To request a reasonable accommodation, please contact the Procurement Officer Amy Turner at Amy.m.turner@phoenix.gov, no later than seven (7) calendar days prior to the date and time listed in the Schedule of Events.

Please register for this meeting by visiting:

https://cityofphoenix.webex.com/weblink/register/r24dd9caca6053aaec5bc9cd0083629bf

**Please note, pre-registration or RSVP to participate in the Pre-Offer Conference is required in order to obtain the Pre-Offer Conference meeting information. An Offeror who wishes to join the Pre-Offer Conference for this solicitation is required to register using the weblink provided prior to the meeting. Upon completion of pre-registration, the Pre-Offer Conference meeting information will be forwarded to the registered email address.

1.9. Questions and Answers (Q&A) Process

Respondents are strongly encouraged to read this RCS in its entirety, including all attachments, exhibits and appendices. Failure to read and/or understand any portion of this RCS shall not be cause for waiver of any portion of the RCS or subsequent Agreement.

If Respondents discover any mistakes, improprieties or defects, they should submit a report of any mistakes, improprieties or defects in writing to the Procurement Officer no later than the question deadline listed in the Schedule of Events.

mailto:Amy.m.turner@phoenix.gov https://cityofphoenix.webex.com/weblink/register/r24dd9caca6053aaec5bc9cd0083629bf

Respondents and their Partners, as defined in the Response Limitation to this RCS section are encouraged to submit questions as a team rather than individually to avoid submitting repetitive questions, which will allow the Aviation Department to answer all questions more efficiently.

All questions about this RCS, including the draft Agreement(s), should be directed via the City’s OpenGov Procurement Portal and must be received by the due date indicated in the Schedule of Events. All written questions will be responded to in writing and available at the City's Procurement Portal.

1.10. Addenda to the RCS

Aviation may amend this RCS before or after the Solicitation deadline listed in the Schedule of Events. Changes to this RCS will be in writing as an addendum and posted at the City's Procurement Portal. Respondents are responsible for checking the website and reviewing all updates and postings.

Respondents may not rely on any statement by any City employee, consultant or official regarding this RCS unless the statement made is published as an addendum or confirmed in writing as part of the Q&A process.

1.11. Respondent Exceptions

The City will award the Agreement(s) on a fair and competitive basis and will not accept any changes to the material provisions or requirements of this RCS or Agreement(s). Respondents that take exception to add to or subtract from any material provision or requirement of this RCS or Agreement(s) may be considered as attempting to change the provisions or requirements of this RCS to gain an unfair advantage over other Respondents. Responses including such exceptions or changes, or that are conditional, are subject to rejection as non-responsive Responses. Non-material exceptions or changes will only be considered if approved by the City during the Q&A process.

NO NEW EXCEPTIONS OR CHANGES TO THE RCS OR THE LEASE WILL BE CONSIDERED

AFTER THE Q&A PROCESS.

1.12. Airport Security

Individuals assigned to work at PHX as a result of this RCS must pass a criminal background check as defined in Phoenix City Code (PCC) Chapter 4, Article IV, Section 4-68 and in compliance with Airport Rule & Regulation 08-01: PHX Ground Transportation Operating Requirements.

1.13. Virtual Queuing Rights

City reserves the right to develop, implement, and operate a virtual queuing system (Virtual Queuing) during the contract term. Virtual Queuing will allow Contractor’s drivers to virtually join a queue at Phoenix Sky Harbor International Airport (PHX) to wait for their turn to pick up passengers, rather than waiting at the pre-designated Commercial Hold Lot (C- Lot) physically.

City agrees to provide the Contractor with written notice of its intent to develop a Virtual Queuing a minimum of one (1) year prior to implementation. During the implementation process, City agrees to engage with the Contractor to conduct test run of Virtual Queuing and gather input to meet operational needs; however, City shall retain final decision-making authority regarding all aspects of the Virtual Queuing. If City implements a Virtual Queuing operation, Contractor, along with franchisee, owner/operator, joint venture partners and authorized drivers will be required to utilize this Virtual Queuing and costs associated with the Virtual Queuing will be assessed to Contractor.

1.14. Response Limitation to this RCS

The City is issuing a single RCS for the award of up to four (4) separate contracts.

A. A Respondent may submit a response for only ONE Category: the Large Company category or the Small Company category. A Respondent may submit as follows:

1. Group 1 - Large Company category - Only one response for the Large Company category OR

2. Group 2A and 2B - Small Company category: A Respondent may submit up to two

(2) responses within the Small Company category. Respondent may submit only ONE response for each contracting opportunity under the Small Company category, as follows:

a. One response for Group 2A - Small Company category for 100% owner/operator

b. One response for Group 2B - Small Company category for non - 100% owner/operator OR

c. One response for Group 2A - Small Company category for the 100% owner/operator AND one response for Group 2B - Small Company category for the non-100% owner/operator.

B. Aviation will review all responses submitted in response to this RCS. However, no Respondent or a business or person affiliated with the Respondent may submit multiple responses for a single category. The following will be deemed multiple responses:

1. The City receives more than one (1) response for Group 1 - Large Company category from a Respondent or a business or person affiliated with the Respondent.

2. The City receives one or more responses for Group 1 - Large Company category and one or more responses for Group 2A and Group 2B - Small Company category from a Respondent or a business or person affiliated with the Respondent.

3. The City receives more than one response for Group 2A - Small Company category for the 100% owner/operator opportunity from a Respondent or a business or person affiliated with the Respondent.

4. The City receives more than one response for Group 2B - Small Company category for the non-100% owner/operator opportunity from a Respondent or a business or person affiliated with the Respondent.

C. If Multiple Responses for this RCS are received from a Respondent, all Responses from that Respondent shall be deemed non-responsive and rejected.

D. Respondent and an entity or person affiliated with the Respondent (Partner) include:

1. A parent and its subsidiary.

2. A holding company and its constituent company.

3. Constituent companies of a single common holding company.

4. Subsidiaries of a common parent.

5. A limited liability company and a member or manager of the limited liability company.

6. Limited liability companies with common members or managers.

7. A partnership and one of its partners, or multiple partners in a single partnership.

8. A person or entity proposing as a joint venture partner or joint venture on separate Responses.

9. A person or entity proposing as a prime or sole Respondent also proposing as a joint venture partner on a separate Response.

10. Two or more Respondents where the president, vice president, officer (including chief operating officer, chief executive officer, and chief financial officer), agent, majority owner or stockholder, management employee, managing or controlling partner, or controlling owner of one Respondent is also the president, vice president, officer (including chief operating officer, chief executive officer, and chief financial officer), agent, majority owner or stockholder, management employee, managing partner, or controlling owner of any other Respondent.

E. It is the intent of the City that this prohibition applies regardless of whether the affiliated person or entity submits a response independently or as a partner of a joint venture or other partnership.

F. The prohibition on Multiple Responses does not preclude a person or business from participating on more than one Response for either Large or Small Company categories as a small business or owner/operator portion only, or submitting a response as a Respondent and participating as a small business or owner/operator on a different Respondent’s team, provided that the form of response does not result in one person or business being awarded more than one (1) contract under this Solicitation. Again, regardless of the form of the entity or persons submitting a response, that person or business may be awarded only one (1) contract under this Solicitation.

G. Each response stands on its own.

CONTINGENT RESPONSES WILL BE REJECTED.

1.15. Execution of the Agreement(s)

The City will send the final Agreements to the recommended Respondents after Phoenix City Council approves the Award Recommendations. Within 30 days from the date the Agreements are sent, the respective recommended Respondents must sign and submit the final Agreement to the City. The City may request City Council approval to award the Agreement to the next highest qualified Respondent in the event the City does not receive the signed Agreement and all other required documentation from the recommended Respondent within 30 days. The Agreement terms may be amended at the sole discretion of the City at any time during the RCS process and/or prior to execution.

If the recommended Respondent is subject to regulation by the Arizona Corporation Commission (ACC), it must be authorized to transact business in Arizona and be in good standing with the ACC at the time it signs the Agreement.

2. Group 1 - Large Company Requirements

2.1. Minimum Qualifications

A. Each Respondent must submit documentation in its Response to demonstrate it meets the required minimum qualifications and includes all information requested in the Solicitation or the Response will be rejected as non-responsive. The City of Phoenix Aviation Department reserves the sole right to determine if Respondents meet the minimum qualifications.

B. Respondents who do not meet the minimum qualifications are encouraged to joint venture partner or subcontract with more established firm(s).

C. RESPONDENT EXPERIENCE REQUIREMENTS

1. Each Respondent must have a minimum of three (3) continuous years of experience operating a taxicab service at a medium or large hub airport as defined by the Federal Aviation Administration (FAA).

2. A Respondent may not use a subcontractor's experience to meet the Respondent's minimum qualifications.

3. Respondent must provide sufficient documentation to demonstrate it meets the minimum qualifications or its proposal will be disqualified as non-responsive.

4. Each Respondent must provide experience information in Attachment F, Qualifications and Experience of Respondent - Large Company.

5. Each Respondent submitting a response for the Large Company category must provide a minimum of three (3) qualifying references in Attachment D, Business References.

D. GENERAL MANAGER EXPERIENCE

1. Each Respondent must propose a general manager (GM) who will serve as Aviation’s primary contact and will be responsible for fulfilling the Respondent’s contractual obligations. The Respondent’s proposed GM may not be changed during the course of the City’s RCS process, including the time up to contract award.

2. The proposed GM must possess a minimum of three (3) continuous years of experience managing the operations of a minimum 35 dispatched-vehicle passenger service fleet. For the purpose of this RCS, “management experience” is defined as being responsible for and performing the following job duties at the same time for dispatched-vehicle passenger services operation:

a. Managed driver and dispatch staffing and personnel issues

b. Resolved customer concerns

c. Managed fleet availability and maintenance

3. Each Respondent must provide experience information in Attachment G, Qualifications and Experience of GM - Large Company for the proposed GM detailing their experience ensuring it meets the minimum requirements.

4. The proposed General Manager must pass a security background check per Section 1.12 within thirty (30) days of contract award.

2.2. Guarantee Instruments

A. Response Guarantee:

1. Responses must be accompanied by a ten-thousand-dollar ($10,000.00) Response Guarantee in the form of a cashier’s check payable, without condition or restrictive endorsement, to the “City of Phoenix, Aviation Department”. Each Respondent’s Response Guarantee must be submitted in a separate sealed envelope clearly marked “Response Guarantee” along with the Response.

2. Response Guarantees submitted by unsuccessful Respondents, including Respondents whose submittals were deemed non-responsive, will be returned, without interest, immediately after formal award of the Contract has been made by the Phoenix City Council or after all responses have been rejected by the City.

3. The Response Guarantee of the Successful Respondent will be returned, without interest, immediately after Successful Respondent has furnished the City with the Performance Guarantee instruments and insurance policies required by the Contract.

Should the Successful Respondent fail to execute the Contract or furnish the Performance Guarantee instruments or insurance within 30 days from the date the Contract was sent, then the Successful Respondent’s Response Guarantee will be forfeited as liquidated damages.

B. Performance Guarantee:

1. Prior to execution of the Contract, the Successful Respondent will be required to post and maintain with the City a Performance Guarantee in the form of a Letter of Credit (LOC) or Cash Deposit in the amount of fifty-thousand dollars ($50,000).

2. Letter of Credit or Cash:

a. If the Performance Guarantee is in the form of an irrevocable standby Letter of Credit (LOC), then the Successful Respondent shall use the City’s LOC form, attached hereto and marked Attachment J, Exhibit 9.

i. The LOC shall be issued by either a financial institution with counters in the Phoenix metropolitan area at which the City may make draws on the LOC or A financial institution with headquarters in the United States on which City may make telefacsimile draws.

ii. Unless City receives a written extension of the LOC in a form acceptable to City at least sixty (60) days before the end of the term of the LOC, City, without notice to Successful Respondent, may draw upon the full amount of the LOC and retain all proceeds as a cash performance guarantee.

iii. Any changes to the LOC provisions must be approved in advance by the Aviation Director

b. If the Performance Guarantee is in the form of cash, Respondent shall deliver to City a completed Cash Deposit for Performance Guarantee Form attached hereto and marked Attachment J, Exhibit 10.

3. Adjustments to Performance Guarantee: City may increase the amount of the Performance Guarantee from time to time. City may increase the amount of the Performance Guarantee by giving the Successful Respondent at least thirty (30) days prior notice of the amount of the increase. The amount of the Performance Guarantee may be increased for any reason the City deems appropriate, including:

a. An increase of the Successful Respondent’s financial obligations under the Contract.

b. Successful Respondents failure to pay any fees, additional payment, or any other amount when due.

c. Successful Respondent’s financial condition changes to the extent that City is concerned about Successful Respondent’s ability to perform under the Contract.

d. Successful Respondent shall pay to City the additional amount necessary to increase the Performance Guarantee upon notice from City.

4. Duty to Restore: The Performance Guarantee ensures the full and timely performance by Successful Respondent of all its obligations under the Contract and is security for payment by Successful Respondent of all claims by City. City may draw on or make a claim against the Performance Guarantee if Successful Respondent breaches or fails to perform under the Contract. If City draws on or makes a claim against the Performance Guarantee, then Successful Respondent, upon demand from City, shall replenish the Performance Guarantee to its previous amount within thirty

(30) days of City’s draw or claim.

5. Return: After the expiration or earlier termination of the Contract, City will return the Performance Guarantee to the Successful Respondent less any Fees, Additional Payment, or any other amount due to City.

2.3. Established Business

If Respondent is a business, then Respondent must provide the City with documentation showing Respondent’s legal status, date of formation, and state of formation. For example, if Respondent is a corporation, then it must provide a copy of its articles of incorporation and bylaws. If Respondent is a limited liability company, then it must provide a copy of its articles of organization, certificate of formation, or similar document. If Respondent is a joint venture partnership, general partnership, or limited partnership, then it must provide a copy of its partnership agreement.

All responses are required to include Attachment E - Established Business Form to demonstrate the Respondent meets this requirement as an established business at time of response submission.

2.4. Scope Overview

Each successful Respondent will have the non-exclusive right to park vehicles in a designated area to be dispatched to PHX terminals and to transport customers over the private entrance and exit roadways from PHX to passengers’ destinations within the service area depicted in Attachment J - Exhibit 1. All taxicab services must be provided in compliance with Phoenix City Code §4-67 through §4-87 and per contractual requirements. Respondent should fully read and understand the Scope of Work requirements outlined in the draft Agreement(s) attached herein as Attachment J.

Each successful Respondent must meet all contractual requirements including:

A. Pay a per-trip fee for each trip as provided by the Phoenix City Code Chapter 4, Article IV, Section 4-78.

B. Provide a base fleet of sixty (60) vehicles, with a minimum of ten percent (10%) of vehicles that comply with Americans with Disabilities Act (ADA) and be wheelchair and mobility device accessible.

C. Have a minimum 15% of fleet vehicles operated by franchisees or owner/operators.

D. Meet alternative fuel requirements outlined in Attachment J, Section 2.13(Q).

E. Limit customer wait times to fifteen (15) minutes or less at all times.

F. Comply with the Franchisee and Owner/Operator Plan, Customer Service Plan, Driver Recruitment, Retention, Training and Conduct Plan as outlined in Attachment J, Exhibits 4-6.

G. All vehicles in fleet must install rear-seat electronic credit card terminals.

H. Provide outstanding customer service while providing taxicab services.

I. Provide supervisors to monitor services and provide timely responses to Aviation staff as requested.

J. Participate in the taxi voucher program in the event of a PHX Sky Train service disruption as outlined in Attachment J, Section 2.16.

2.5. Fleet Acquisition

Contractor will provide to the Aviation Department Representative (ADR), within thirty (30) days of contract award, a contract, purchase order, bill of sale, vehicle purchase agreement, or merchandise bill of sale for the minimum fleet of vehicles meeting the requirements set in Attachment J. If Contractor, or owner/operators that will operate under Contractor’s contract, have possession of vehicles meeting the requirements set forth in Attachment J, Contractor must, within thirty (30) days from contract execution, provide to the ADR a vehicle fleet list of such vehicles indicating, for each vehicle, the following:

A. Vehicle Owner

B. Vehicle Year

C. Vehicle Make

D. Vehicle Model

E. Vehicle Identification Number (VIN)

F. License Plate Number

G. Fleet Number

H. Mileage at the time of submittal of the list

I. Vehicle Fuel Type

J. Statement identifying vehicles as ADA Wheelchair Accessible, if applicable.

Within sixty (60) days of contract execution, Contractor must present vehicles to ADR for inspection to ensure vehicles meet the requirements set forth in Attachment J and to affix to each vehicle an Automated Vehicle Identification (AVI) tag and an Airport Annual Decal.

Within ninety (90) days of contract execution, Contractor must commence service with its base fleet.

2.6. Fleet Specifications

All new or replacement vehicles providing taxicab service as a result of this RCS must:

A. At the time of commencement of service have less than 100,000 miles and be five (5) years old or less.

B. Be limited to a service life of 400,000 miles and must not be older than eight (8) years at any time during the term of the Contract.

C. For any replacement vehicle, at the time of replacement, have the lesser of:

1. 100,000 miles

2. Fewer miles than the vehicle it replaces.

D. Be large-size or mid-size vehicles as determined by 40 C.F.R. §600.315-08, Classes of Comparable Automobiles:

1. Vehicles must have a designated minimum seating capacity of four (4) passengers, not including the driver, with separate cargo space.

2. Vehicles must have usable cargo space greater than or equal to 15 cubic feet.

3. ADA compliant vehicles must be wheelchair and mobility device accessible and have a designated minimum seating capacity of four (4) passengers, not including the driver, which includes one (1) forward facing wheelchair position with, at a minimum, four-point tie down securement in functional order.

E. Be in compliance with the Alternative Fuel Requirements set forth in Attachment J, Section 2.13(Q).

F. Be in compliance with the Taximeter requirements listed in Attachment J, Section 2.13(P).

2.7. Trip Fee

A. Contractor will pay a trip fee for each trip in the amount set by Phoenix City Code Chapter

4, Article IV, Section 4-78.

B. Trip fees will increase annually at the lesser of three (3) percent or the percent of change in the most current Consumer Price Index for Phoenix-Mesa-Scottsdale, All Urban Consumers, published by the U.S. Department of Labor, Bureau of Labor Statistics, or such revised index that may be subsequently published by the Bureau. Any adjustment to the trip fee will be reflected in the Phoenix City Code, Chapter 4, Article IV, Section 4-78.

C. Contractor will be responsible for payment of trip fees for the applicable vehicle rate as provided in the Airport Rules and Regulations 08-01: PHX Ground Transportation Operating Requirements.

D. Respondent WILL NOT propose any other fees or revenues to be paid to the City in its response. Any fees or revenues proposed to be paid to the City WILL NOT be considered for purposes of evaluation.

E. Contractor is responsible for payment of all trip fees to the City. Contractor must not collect trip fees, directly or indirectly, from drivers, independent contractors, franchisees, owner/operators, except in cases where drivers, franchisees, or owner/operators have an ownership stake in the Contractor’s company. Contractor must not collect trip fees, directly or indirectly, from passengers.

F. The City will invoice Contractor monthly for trip fees, which Contractor must pay in full within thirty (30) days of the invoice date. All sums unpaid after thirty (30) days will be subject to a delinquent account fee in an amount set by Airport Rules and Regulations 08- 01: PHX Ground Transportation Operating Requirements. Contractor’s refusal or failure to pay the applicable trip fee, including any delinquent account fees, will be considered a breach of contract and subject Contractor’s privileges under the Contract to immediate suspension or termination.

2.8. Insurance Requirements

Contractor must provide evidence of ability to obtain required insurance coverages, such as a commitment letter from an underwriter or a current certificate of insurance showing comparable insurance limits, confirming that the Respondent is insurable for the required coverages at the required limits as defined in Attachment J, Section 6. The City reserves the sole right to determine if the Respondent will meet the required insurance limits as defined in this Solicitation.

2.9. Customer Data and Security

The Successful Respondent should consider the security of customer data, including credit card numbers, phone numbers, and any other identifying information, and have methods in place to ensure that customer data is adequately protected. The Successful Respondent should submit proof of Payment Card Industry Data Security Standard (PCI DSS) Certification with the Response. The PCI DSS Certification will ensure that the Successful Respondent has all required measures in place to secure customer credit card payments.

2.10. Evaluation Criteria

All responsive and responsible Responses will be evaluated based on the following criteria. The criteria will be evaluated for the Respondent and all Partners of the Respondent, if any. The sub-criteria listed will be considered by the evaluation panel(s) but are neither individually weighted nor listed in order of importance. The score for each Evaluation Criteria will be up to the Points listed for that Criteria.

Additional information can be found in the Organization of the Response Section below.

A. Business and Operations Plan (0-300 points) Respondent must provide an Operations Plan which includes an overall approach to scope of taxicab services to include details on fleet acquisition, driver recruitment and retention plan, driver training and conduct plan, technological solutions being utilized, daily fleet utilization and vehicle maintenance plans.

Respondent must also provide details on the Respondent's business financial plan, demonstrating Respondent's financial capability to perform the services as requested in this RCS.

B. Qualifications and Experience of Respondent (0-200 points) Respondent must provide detailed information demonstrating the qualifications and experience of the Respondent, which includes the history of the Respondent's relevant experience including the number of years and experience providing taxicab services at a medium or large hub airport and how the Respondent has met vehicle operational standards, driver hiring, training and conduct standards, and met customer service standards.

C. Qualifications and Experience of Proposed General Manager (0-200 points) Respondent must provide detailed information for the General Manager (GM) to include a minimum of three (3) years of experience managing the operations of a thirty-five (35) dispatched vehicle passenger service fleet. Respondent must also provide details of experience managing driver and dispatch staffing and personnel issues, customer concerns, and managed fleet availability and maintenance.

D. Customer Service Plan (0-150 points) Respondent must provide detailed information on Respondent's plan to provide excellent customer service including details on Respondent's customer service strategy, lost and found plan, emergency procedure plan, ADA compliance plan, and PHX request response plan.

E. Franchisee and Owner/Operator Plan (0-150 points) Respondent must provide detailed information on providing interested potential franchisees and/or owner/operators with information about opportunities to partner with Respondent, maintaining the 15% owner/operator requirement, plan to ensure franchisees and/or owner/operators meet fleet and maintenance requirements as well as dispute resolution plans.

2.11. Submission of Offer

A. Offers must be in possession of the Department on or prior to the exact time and date indicated in the Schedule of Events. Late offers will not be considered. The prevailing clock will be the Aviation Department’s clock.

B. Offers should be submitted electronically via the City’s e-Procurement Portal by clicking on “Draft Response” via https://procurement.opengov.com/portal/phoenix/projects/155684. Offerors that are unable to submit electronically should contact the Procurement Officer (Amy Turner, amy.m.turner@phoenix.gov ) to discuss the logistics of hard copy submittals. Offerors must be registered with OpenGov by signing up via https://procurement.opengov.com/signup. Vendor training guides can be found at: https://opengov.my.site.com/support/s/article/ca6d1285-1e48-4a21-bb0d- 715edb7794ed

C. Any original documents (such as bonds, guaranties, powers of attorney), if required by the Solicitation, must be separately delivered to and received by the City on or prior to the exact time and date indicated in the Schedule of Events, with a clear indication of the Offer for which it is attributed.

https://procurement.opengov.com/portal/phoenix/projects/155684 mailto:amy.m.turner@phoenix.gov https://procurement.opengov.com/signup https://opengov.my.site.com/support/s/article/ca6d1285-1e48-4a21-bb0d-715edb7794ed

D. It is the responsibility of the Offeror to ensure that the Offer is timely and to confirm that there are no technical reasons that any offer submitted electronically may be delayed. The date and time on the upload as received/stamped by the City’s e-Procurement Portal will provide proof of submission and verification whether the Offer was received on or prior to the exact time and date indicated in the Schedule of Events.

E. For assistance with submittals, vendors are welcome to use the OpenGov support chat (blue chat bubble in the bottom right corner) to connect with a member of OpenGov's support team who will be able to assist you with your submission.

F. Please DO NOT submit links to Google Docs, Dropbox Paper, or similar services.

Your offer may be deemed non-responsive if your offer is supplied utilizing these services.

2.12. Delivery of Responses

A. Respondents' response must include the following:

1. Affidavit that has been notarized, with authorized original signature of Respondent (Attachment A)

2. Letter of Declaration (Equal Pay)(Attachment B)

3. Conflict of Interest and Solicitation Transparency Disclosure Form (Attachment C)

4. Business References (Attachment D)

5. Established Business Form (Attachment E)

6. Bank’s Letter of Commitment - Respondent must provide a letter from its bank communicating the bank’s commitment to provide the Respondent, if successful, with a Letter of Credit or Cash Deposit, as defined in the Performance Guarantee Section

7. Evidence of ability to obtain required insurance coverages, such as a commitment letter from an underwriter or a current certificate of insurance showing comparable insurance limits, confirming that the Respondent is insurable for the required coverages at the required limits as defined in Attachment J

8. Proof of Payment Card Industry Data Security Standard (PCI DSS) Certification

9. In a separate sealed envelope marked “Response Guarantee”, the ten-thousand dollars ($10,000.00) Response Guarantee check

B. The actual Response Guarantee and notarized affidavit must be received at the Aviation Headquarters located at 2485 East Buckeye Road, Phoenix, AZ 85034 by the Solicitation deadline as indicated in the Schedule of Events.

C. Respondents may submit electronic signatures on documents that do not require a Notary Public. The City does not accept electronic signatures for notarized documents;

these documents must be submitted in paper form (hard copy) with original or “wet signatures” prior to the time of the Solicitation deadline.

2.13. Organization of the Response

All responses should include all the following and must be organized using the Tab numbers listed below:

TAB 1 – GENERAL INFORMATION

A. Cover Letter (2-page limit) including the following information on the letter:

1. Name of Respondent; if Respondent is a joint venture, then indicate all partners and each partner’s percentage of ownership interest in joint venture

2. Names of all franchisees or owner/operators, if any

3. Response must clearly identify for which category and opportunity (Large or Small Company, 100% Owner/Operator or Non-100% Owner/Operator) the response is being submitted for

B. Table of Contents for entire Response with page numbers included

TAB 2 – EVALUATION CRITERIA NO. 1 - Business and Operations Plan - 300 points

Respondents should provide a narrative regarding the Business and Operations Plan and include the following in Tab 2 of their Response:

A. Operations Plan (limit 30 pages) - Respondent should include information detailing their operations plan which should include at a minimum:

1. Fleet Acquisition Plan that includes:

a. Any agreement, contract, or relationship in place with a vehicle dealer that Respondent will leverage to acquire vehicles.

b. Timeline for acquisition of vehicles

c. Type of vehicles and fuel systems to be acquired

d. Plan to paint and configure vehicles according to fleet requirements listed in Attachment J, Section 2.13.

2. Marketing Plan or Statement - Respondent is NOT required to conduct marketing. If Respondent does intend to conduct marketing, the evaluation panel may consider the proposed plan. If Respondent is intending to conduct marketing, the Respondent must provide documentation demonstrating the Respondent's method of marketing, i.e. billboards, internet advertisements, or customer surveys.

3. Driver Recruitment and Retention Plan that demonstrates the Respondent's:

a. Plan detailing the Respondent's recruiting, retention and employee policies

b. Plan detailing communicating these policies to taxicab operators

c. Benefits Plan

4. Driver Training Plan that at a minimum should include how the Respondent will provide training on:

a. ADA compliance, disability sensitivity, and proficiency in assisting customers with disabilities

b. Transporting wheelchairs and mobility devices safely and utilizing vehicle mobility device lifts

c. Knowledge and compliance with Airport Rules and Regulations

d. Customer service and communication skills

e. Knowledge of the Phoenix metropolitan area

f. Vehicle safety procedures

g. Responding in emergency situations

h. Vehicle breakdown procedures while transporting customers

i. Use of credit/debit transaction system

5. Driver Conduct Plan should include how the Respondent will address:

a. Acceptable and unacceptable driver conduct

b. Corrective action plan for drivers who violate Airport Rules and Regulations or federal, state, county and city laws

c. Personal hygiene standards

d. Appropriate work attire or uniform standards

6. Technological Solutions Plan to address how the Respondent will provide:

a. Safe and secure electronic…