- Documents
- Airport_Technology_Consulting_Services.pdf, A - Supplemental-Terms-And-Conditions-To-All-Airport-Contracts Rev 4-29-26, B - Sensitive Security Information Acknowledgement Form, C - Acceptance of Offer Form 2026
- Numeric Id
- 276938
- Document Text
- 1. Introduction
1.1. Contact Information
Michael Soto III
Aviation
Email: michael.soto@phoenix.gov
Phone: (602) 683-2670
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 (Michael Soto III) at (602) 683-2670/Voice or 711/TTY, or michael.soto@phoenix.gov, no later than five (5) days prior to the meeting.
Solicitation Issue Date: October 13, 2026
Pre-Offer Conference (Non-Mandatory): October 21, 2026, 9:00am
TO RSVP / register, please visit:
https://cityofphoenix.webex.com/weblink/register/rb983e8ffa0099539ab1269a32976bf37
Written Inquiries Due Date: October 26, 2026, 3:00pm
Offer Due Date: December 3, 2026, 3:00pm
Meeting Link:
https://cityofphoenix.webex.com/cityofphoenix/j.php?MTID=m8b98e0fd5d40a86f5d7d84ca1601e009
Join by phone:
+1-415-655-0001 US Toll
Access code: 2340 738 5724
Please note: 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 or access code provided prior to the meeting. Upon completion of registration, the Pre-Offer Conference meeting information will be forwarded to the registered email address.
2. Instructions
2.1. Description – Statement of Need
The City of Phoenix invites sealed offers for Airport Technology Consulting Services.
The Effective Date of this Agreement will be upon final signature and recording by the City Clerk’s department.
The Commencement Date of this Agreement will be on or about April 1, 2027, which is on or after the ordinance approved start date or the Effective Date, whichever is later.
The term of this Agreement will be for a five (5)-year contract term beginning on the Commencement Date, with two (2) one-year options to extend, which may be exercised by the sole discretion of the Aviation Director.
This Solicitation is available through the City’s Procurement Portal. For technical support issues related to the City's Procurement Portal, Offeror may use the support bubble on the bottom right, or email procurement-support@opengov.com for any assistance. For other issues related to this Solicitation please contact the Procurement Officer listed under Contact Information.
Notwithstanding the foregoing, this Agreement will terminate upon the earliest occurrence: by reaching the end of the term including any extensions exercised, or termination pursuant to the provisions of this Agreement.
2.2. Preparation of Offer
All forms provided must be completed and submitted with the Offer. The signed and completed Conflict of Interest and Transparency form must be included or your Offer may be deemed non-responsive.
It is permissible to copy Submittal forms if necessary. Erasures, interlineations, or other modifications of the Offer must be initialed in original ink by the authorized person signing the Offer. No offer will be altered, amended or withdrawn after the specified offer due date and time. The City is not responsible for Offeror’s errors or omissions.
All time periods stated as a number of days will be calendar days.
It is the responsibility of all Offerors to examine the entire Solicitation and seek clarification of any requirement that may not be clear and to check all responses for accuracy before submitting an offer. Negligence in preparing an offer confers no right of withdrawal after due date and time. Offerors are strongly encouraged to:
Consider applicable laws and/or economic conditions that may affect cost, progress, performance, or furnishing of the products or services.
Study and carefully correlate Offeror’s knowledge and observations with the Solicitation and other related data.
Promptly notify the Procurement Officer of all conflicts, errors, ambiguities, or discrepancies that Offeror has discovered in or between the Solicitation and other related documents.
The City does not reimburse the cost of developing, presenting or providing any response to this Solicitation. Offers submitted for consideration should be prepared simply and economically, providing adequate information in a straightforward and concise manner. The Offeror is responsible for all costs incurred in responding to this Solicitation. All materials and documents submitted in response to this Solicitation become the property of the City and will not be returned.
Offerors are reminded that the specifications stated in the Solicitation are the minimum level required and that offers submitted must be for products or services that meet or exceed the minimum level of all features specifically listed in this Solicitation. Offers offering less than any minimum specifications or criteria specified are not responsive and should not be submitted.
Offer responses submitted for products considered by the seller to be acceptable alternates to the brand names or manufacturer’s catalog references specified herein must be submitted with technical literature and/or detailed product brochures for the City’s use to evaluate the products offered. Offers submitted without this product information may be considered as non-responsive and rejected. The City will be the sole judge as to the acceptability of alternate products offered.
Prices will be submitted on a per unit basis by line item, when applicable. In the event of a disparity between the unit price and extended price, the unit price will prevail unless obviously in error.
2.3. Obtaining a Copy of the Solicitation and Addenda
Interested Offerors may download the complete Solicitation and addenda from the City's Procurement Portal: https://procurement.opengov.com/portal/phoenix/projects/276938. Any interested Offerors without internet access may obtain this Solicitation by calling the Procurement Officer or picking up a copy during regular business hours at the City of Phoenix, Aviation Headquarters, 2485 East Buckeye Road, Phoenix, Arizona 85034. It is the Offeror’s responsibility to check the City's Procurement Portal, read the entire Solicitation, and verify all required information is submitted with their Offer.
2.4. Exceptions
Offeror must not take any exceptions to any terms, conditions or material requirements of this Solicitation. Offers submitted with exceptions may be deemed non-responsive and disqualified from further consideration in the City’s sole discretion. Offerors must conform to all the requirements specified in the Solicitation. The City encourages Offerors to send inquiries to the Procurement Officer rather than including exceptions in their Offer.
2.5. Inquiries
All questions that arise relating to this Solicitation should be directed via City’s Procurement Portal and must be received by the due date indicated in the Schedule of Events. The City will not consider questions received after the deadline.
No informal contact initiated by Offerors on the proposed service will be allowed with members of City’s staff from the date of distribution of this Solicitation until after the City Council awards the contract. All questions concerning or issues related to this Solicitation must be presented in writing.
The Procurement Officer will answer written inquiries in an addendum and publish any addenda on the City’s Procurement Portal.
2.6. Addenda
The City of Phoenix will not be responsible for any oral instructions made by any employees or officers of the City of Phoenix regarding this Solicitation. Any changes will be in the form of an addendum. The Offeror must acknowledge receipt of any/all addenda through the City's Procurement Portal.
Changes to terms and conditions of the Solicitation and resulting Agreement made pursuant to an addendum shall be memorialized in the Solicitation and resulting Agreement document. To that end, a parenthetical will be added to applicable provision(s) referencing the addendum that imposed the change. The language in the final provision will reflect the updated version.
2.7. Licenses
If required by law for the operation of the business or work related to this Offer, Offeror must possess all valid certifications and/or licenses as required by federal, state or local laws at the time of submittal.
2.8. Certifications
By signature in the Offer section of the Offer and Acceptance page(s), Offeror certifies:
The submission of the Offer did not involve collusion or other anti-competitive practices.
The Offeror must not discriminate against any employee, or applicant for employment in violation of Federal or State Law.
The Offeror has not given, offered to give, nor intends to give at any time hereafter, any economic opportunity, future employment, gift, loan, gratuity, special discount, trip, favor, or service to a public servant in connection with the submitted Offer.
2.9. Submission of Offer
Offers must be in possession of the Aviation 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.
Offers should be submitted electronically via the City’s Procurement Portal by clicking on “Draft Response” via https://procurement.opengov.com/portal/phoenix/projects/276938. Offerors that are unable to submit electronically should contact the Procurement Officer 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
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.
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 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.
For technical 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.
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.10. Withdrawal of Offer
At any time prior to the Solicitation due date and time, an Offeror (or designated representative) may withdraw the Offer by clicking “Unsubmit Response” on the Offer submission via the City’s Procurement Portal.
2.11. Offer Results
Offer openings will take place on their designated date and time indicated in the Schedule of Events, through remote video and telephone conference with the link and dial-in phone number below:
Meeting Link:
https://cityofphoenix.webex.com/cityofphoenix/j.php?MTID=m731f31137567bb9e9c7b2c511ff85644
Join by phone:
+1-415-655-0001 US Toll
Access code:
2348 024 7094
The name of each Offeror may be read and/or viewed. Offers are not available for public inspection until after the City has posted the award recommendation on the City's Procurement Portal.
The City will post the Offeror’s name on the City's Procurement Portal: https://procurement.opengov.com/portal/phoenix/projects/276938 within five business days of the offer opening. Offers are not available for public inspection until after the City has posted the award recommendation on the City's Procurement Portal. Once the City has reviewed the offers, the City will post an award recommendation on the City's Procurement Portal. The City will not provide any further notification to unsuccessful Offerors.
2.12. Content of Response
The Offeror's response will include the following:
Qualifications and Experience: For all groups Offer is interested in submitting for, the Offeror must provide a detailed description (Not to exceed 5 pages total) of their relevant experience or their subcontractor’s experience for each group. Offerors are allowed and encouraged to subcontract (if necessary) to meet any group qualifications they are submitting for. Offerors must provide resumes for all key personnel, including subcontractors, whose qualifications are being used to meet the minimum requirements for any group. Resumes should detail relevant experience, certifications, education, and prior project work, particularly in airport or public sector environments.
Group 1: General IT Consulting
Proven experience assessing, designing and integrating scalable IT systems in complex airport or public sector environments.
Experience conducting workforce assessments, change management and aligning IT workforce capabilities with organizational objectives, and digital transformation goals.
Demonstrated capability in providing strategic technology consulting, including IT roadmaps, modernization planning, and enterprise architecture advisory services.
Group 2: Enterprise IT Systems
Demonstrated ability to analyze complex datasets, implement enterprise analytics platforms and deliver actionable insights across airport systems.
Proficient in system design principles, cloud platforms, and enterprise integration frameworks.
Proven experience with implementing and optimizing Business Intelligence (BI) tools such (e.g., Tableau, Power BI) to build dashboards and support data driven decision making.
Expertise designing and implementing Customer Relationship Management (CRM) platforms (e.g. Salesforce, Dynamics 365) and customer data workflows.
Demonstrated capability enhancing of Enterprise Asset Management Systems (EAMS) for tracking, maintaining and optimizing enterprise assets.
Group 3: Artificial Intelligence (AI) / Machine Learning (ML) & Emerging Technologies
Experience assessing AI readiness and deploying AI/ML solutions in operational settings with adaptability to rapid tech evolution.
Group 4: Airport Technology Strategy & Integration
Proven success implementing smart infrastructure, passenger-facing technologies and operational systems that enhance airport efficiency and passenger- facing experience.
Expertise designing and deploying digital systems in an airport setting, ensuring minimal disruption to operations.
Proven experience assessing and deploying and optimizing private LTE/5G or CBRS infrastructure and networks in enterprise or public-sector environments.
Demonstrated expertise in developing digital twin strategies, digital twin modeling, indoor precision systems (IPS) design & development, or drone data integration.
Proven success supporting airport scenarios, including terminal flow simulation, perimeter security technologies, and infrastructure visualization in complex airport environments.
Offeror's Statement of Work:
Offeror must provide a detailed description (Not to exceed 20 pages total) to include:
List of Technology Consulting Services identified in Section 3 - Scope of Work, Paragraph 3.3. - Technology Consulting Services, for which the Offeror is qualified to provide.
Provide a detailed description of previous Technology Consulting Services at other large hub airports.
2.13. Evaluation and Selection
In accordance with Administrative Regulation 3.10, Qualifications Based Selection, a list of qualified Offerors will be established based on the minimum qualifications criteria detailed in Section 2 – Instructions, Paragraph 2.12 – Minimum Qualifications of this RFQu. The City will evaluate the Offeror(s) as pass or fail for each qualification criteria and only those Offerors that receive a pass for all qualification criteria may be recommended for the Qualified Vendors List (QVL).
The Offerors under consideration for this RFQu will be evaluated by the Procurement Officer. The City reserves the right to request clarification information that the Procurement Officer deems necessary to make a recommendation to establish a QVL. The Procurement Officer’s review may be supplemented by subject matter experts, outside professionals, or professionals from other City departments who can provide additional expertise.
Upon completion of the evaluation process and in accordance with Administrative Regulation 3.10, the City may establish a QVL and may assign a detailed scope of work to the selected Contractors, and may negotiate fees for services. The City will develop the order of the QVL based on the order that the responses are received. Placement on a QVL established by the City does not represent or guarantee that the City will assign work to a Contractor on a QVL. An established QVL merely provides the City with an option to request work from a Contractor at the City’s discretion.
2.14. Agreement
The City will require the selected Offeror to participate in negotiations and to submit such cost, technical or other revisions of the submittals as may result from negotiations. The City shall draft all final contracts and documents that result from this RFQu.
The language contained in this RFQu and the Offeror's statement of qualifications will form the basis of any resulting Contract. However, this RFQu does not commit the City to enter a Contract, to pay any costs incurred in the preparation of an Offer to this request or in subsequent negotiations, or to procure a contract for the project(s).
2.15. Certificates of Insurance
Upon notification of a recommended award, the Offeror will have 30 calendar days to submit a complete certificate of insurance in the minimum amounts and the coverages as required in the Insurance Requirements of this Solicitation. Insurance requirements are non-negotiable.
2.16. Award of Contract
Unless otherwise indicated, award(s) will be made to responsive, responsible Offeror(s) who are regularly established in the service, or providing the goods, contained in this Solicitation and who have demonstrated the ability to perform in an acceptable manner.
Factors that may be considered by the City include:
Technical capability of the Offeror to accomplish the scope of work required in the Solicitation. This may include performance history on past and current government or industrial contracts; and,
Demonstrated availability of the necessary manpower (both supervisory and operational personnel) and necessary equipment to accomplish the scope of work in the Solicitation; and,
Safety record; and,
Offeror history of complaints and termination for convenience or cause.
Notwithstanding any other provision of this Solicitation, the City reserves the right to: (1) waive any immaterial defect or informality; or (2) reject any or all offers or portions thereof; or (3) reissue a Solicitation.
A response to a Solicitation is an offer to contract with the City based upon the terms, conditions, and specifications contained in the City’s Solicitation. Offers do not become contracts until they are executed by the Deputy Aviation Director or Department Director. A contract has its inception in the award, eliminating a formal signing of a separate contract. For that reason, all of the terms, conditions and specifications of the procurement contract are contained in the Solicitation, and in any addendum or contract amendment.
2.17. Solicitation Transparency Policy
Commencing on the date and time a Solicitation is published, potential or actual Offerors or respondents (including their representatives) shall only discuss matters associated with the Solicitation with the Mayor, any members of City Council, the City Manager, any Deputy City Manager, or any department director directly associated with the Solicitation (including in each case their assigned staff, except for the designated Procurement Officer) at a public meeting, posted under Arizona Statutes, until the resulting contract(s) are awarded to all offers or responses are rejected and the Solicitation is cancelled without any announcement by the Procurement Officer of the City’s intent to reissue the same or similar Solicitation.
As long as the Solicitation is not discussed, Offerors may continue to conduct business with the City and discuss business that is unrelated to the Solicitation with the City staff. Offerors may not discuss the Solicitation with any City employees or evaluation panel members.
Offerors may discuss their proposal or the Solicitation with the Mayor or one or more members of the Phoenix City Council, provided such meetings are scheduled through the Procurement Officer, and are posted as open meetings with the City Clerk at least 24 hours prior to the scheduled meetings. The City Clerk will be responsible for posting the meetings. The posted notice shall identify the participants and the subject matter, as well as invite the public to participate.
With respect to the selection of the successful Offerors, the City Manager and/or City Manager's Office will continue the past practice of exerting no undue influence on the process. In all Solicitations of bids and proposals, any direction on the selection from the City Manager and/or City Manager's Office and Department Head (or representative) to the proposal review panel or selecting authority must be provided in writing to all prospective Offerors.
This policy is intended to create a level playing field for all Offerors, assure that contracts are awarded in public, and protect the integrity of the selection process. OFFERORS THAT VIOLATE THIS POLICY SHALL BE DISQUALIFIED. After official Notice is received by the City for disqualification, the Offeror may follow the Protest process, unless the Solicitation is cancelled without notice of intent to re-issue.
“To discuss” means any contact by the Offeror, regardless of whether the City responds to the contact. Offerors that violate this policy will be disqualified until the resulting contract(s) are awarded, or all offers or responses are rejected and the Solicitation is cancelled without any announcement by the Procurement Officer of the City’s intent to reissue the same or a similar Solicitation. The City interprets the policy as continuing through a cancellation of a Solicitation until Council award of the contract, as long as the City cancels with a statement that the City will rebid the Solicitation.
2.18. Protest Process
Offeror may protest the contents of a Solicitation no later than seven days before the Solicitation deadline when the protest is based on an apparent alleged mistake, impropriety or defect in the Solicitation. Protests filed regarding the Solicitation may be addressed by an amendment to the Solicitation or denied by the City. If denied, the opening and award will proceed unless the City determines that it is in the City’s best interests to set new deadlines, amend the Solicitation, cancel or re-bid.
Therefore, unless otherwise notified by a formal amendment, the Protester must adhere to all Solicitation dates and deadlines, including timely filing of an offer, regardless of filing a protest.
Offeror may protest an adverse determination issued by the City regarding responsibility and responsiveness, within seven days of the date the Offeror was notified of the adverse determination.
Offeror may protest an award recommendation if the Offeror can establish that it had a substantial chance of being awarded the contract and will be harmed by the recommended award. The City will post recommendations on the City’s Procurement Portal to award the contract(s) to an Offeror(s). Offeror must submit award protests within seven days after the posting of the award recommendation, with exceptions only for good cause shown, within the City’s full and final discretion.
All protests will be in writing, filed with the Procurement Officer identified in the Solicitation and include the following:
Identification of the Solicitation number;
The name, address and telephone number of the protester;
A detailed statement describing the legal and factual grounds for the protest, including copies of relevant documents;
The form of relief requested; and
The signature of the protester or its authorized representative.
The Procurement Officer will render a written decision within a reasonable period after the protest is filed. The City will not request City Council authorization to award the contract until the protest process is complete. All protests and appeals must be submitted in accordance with the City’s Procurement Code, (Phoenix City Code, Ch. 43) and any protests or appeals not submitted within the time requirements will not be considered. Protests must be filed with the Procurement Officer.
2.19. Public Record
All Offers submitted in response to this Solicitation will become the property of the City and become a matter of public record available for review pursuant to Arizona State law. If an Offeror believes that a specific section of its Offer response is confidential, the Offeror will isolate the pages marked confidential in a specific and clearly labeled section of its Offer response. An Offeror may request specific information contained within its Offer is treated by the Procurement Officer as confidential provided the Offeror clearly labels the information “confidential.” To the extent necessary for the evaluation process, information marked as “confidential” will not be treated as confidential. Once the procurement file becomes available for public inspection, the Procurement Officer will not make any information identified by the Offerors as “confidential” available to the public unless necessary to support the evaluation process or if specifically requested in accordance with applicable public records law. When a public records request for such information is received, the Procurement Officer will notify the Offeror in writing of any request to view any portion of its Offer marked “confidential.” The Offeror will have the time set forth in the notice to obtain a court order enjoining such disclosure. If the Offeror does not provide the Procurement Officer with a court order enjoining release of the information during the designated time, the Procurement Officer will make the information requested available for inspection.
2.20. Late Offers
Late Offers must be rejected, except for good cause. If a late Offer is submitted, the Department will document the date and time of the submittal of the late Offer, keep the Offer and notify the Offeror that its Offer was disqualified for being a late Offer.
2.21. Right to Disqualify
The City reserves the right to disqualify any Offeror who fails to provide information or data requested or who provides materially inaccurate or misleading information or data. The City further reserves the right to disqualify any Offeror on the basis of any real or apparent conflict of interest that is disclosed by the Offer submitted or any other data or information available to the City. This disqualification is at the sole discretion of the City. By submission of a Solicitation response, the Offeror waives any right to object now or at any future time, before any agency or body including, but not limited to, the City Council of the City or any court as to the exercise by the City of such right to disqualify or as to any disqualification by reason of real or apparent conflict of interest determined by the City. The City reserves the right to replace the disqualified Offeror.
2.22. Contract Award
The City reserves the right to award a contract by individual line items, by group, all or none, or any other combination most advantageous to the City. The City reserves the right to award multiple contracts.
2.23. Determining Responsiveness and Responsibility
A. Offers will be reviewed for the documentation of qualifications, completeness, and compliance with the Solicitation requirements. The City reserves sole discretion to determine responsiveness and responsibility.
B. Responsiveness: Nonresponsive Offers will not be considered in the evaluation process. The Solicitation states criteria that determine responsiveness, and the Solicitation includes terms and conditions that if included or excluded from Offers (as the case may be) will render an Offer nonresponsive.
C. Exceptions, conditions, reservations, or understandings are presumed to be unacceptable, and an Offer that includes unacceptable exceptions, conditions, reservations, or understandings may be rejected as nonresponsive. Alternatively, the City in its sole discretion may instruct in writing that any Offeror remove the conditions, exceptions, reservations, or understandings. If the Offeror fails to do so in writing, the City may determine the Offer to be nonresponsive.
D. Responsibility: To obtain true economy, the City must conduct Solicitations to minimize the possibility of a subsequent default by the contractor, late deliveries, or other unsatisfactory performance that may result in additional administrative costs. It is important that the Offeror be a responsible contractor. Responsibility includes the Offeror’s integrity, skill, capacity, experience, financial ability, and facilities for conducting the work to be performed.
E. The Procurement Officer will review each Offer to determine if the Offeror is responsible and responsive. The City’s determination as to whether an Offeror is responsible will be based on all information furnished by the Offeror, interviews (if any), and information received from Offeror’s references, including information about Offeror’s history, terminations for convenience or cause, Contract breach lawsuits or notices of claim and any other sources the City deems appropriate. Award of the Contract resulting from the Solicitation will not be made until any necessary investigation, which each Offeror agrees to permit by submitting its Offer, is made by the City as it deems necessary. A review of responsibility may occur up to Contract award.
F. The Offeror’s unreasonable failure to promptly supply information about an inquiry with respect to responsibility may be grounds for a determination of non-responsibility with respect to such Offeror.
3. Scope of Work
3.1. Introduction
The Aviation Department is seeking qualified Contractors to support the evolving technological needs of Phoenix Sky Harbor International Airport. This QVL is being established to provide a streamlined and strategic mechanism for procuring high-quality consulting and professional services. The QVL is designed to ensure access to specialized expertise across four (4) critical IT service domains, each tailored to enhance operational efficiency, security, innovation, IT strategy, and workforce readiness within the aviation environment.
Group 1 – General IT Consulting – Includes design, assessment, strategic planning, workforce planning, change management and delivering scalable, integrated systems that support mission-critical airport functions and long-term digital transformation.
Group 2 – Enterprise IT Systems - Includes data analytics, IT Architecture and Business Intelligence as well as enabling data-driven decision making and operational insights.
Group 3 – Artificial Intelligence (AI) / Machine Learning (ML) and Emerging Technologies – Includes advancing smart infrastructure and passenger services through intelligent automation.
Group 4 – Airport Technology Strategy & Integration – Includes design and deployment of advanced technologies that drive Airport 4.0.
The IT Consulting Service Groups resulting from this QVL will be solicited on an as-needed basis and pricing must be all-inclusive. An established QVL merely provides the City with an option to request work from a Contractor at the City’s discretion. There is no guarantee that a Contractor and its IT Consulting Services will be selected for service after being added to the QVL.
3.2. Aviation Department Representative
The Aviation Department Representatives (ADR) for this Contract will be Genie Usher. The ADR or her designee will coordinate all invoicing and will have sole responsibility for evaluating the acceptability and quality of the services provided under this Contract. The ADR or her designee will be consulted on any concerns and issues arising during performance. The ADR can be reached at genie.usher@phoenix.gov or (602) 273-3402.
3.3. Technology Consulting Services
Group 1 – General IT Consulting: This group requires Contractors with demonstrated expertise in designing, assessing, and implementing scalable IT solutions that support airport operations. Services may include enterprise architecture, systems integration for aviation or public sector environment. Contractors may also be expected to provide strategic IT consulting, such as technology assessments, roadmap development, workforce planning, change management and governance advisory to ensure alignment with organizational objectives and Airport 4.0 framework. IT Consulting Services may include but are not limited to:
IT solution design and implementation for enterprise and operational systems.
IT strategy and roadmap development.
Architecture of software, hardware, and network infrastructure.
Integration of legacy and modern systems for seamless data flow.
IT workforce planning, change management and organizational development.
Competency modeling and workforce alignment in complex, multi-system environments.
Technology modernization planning and enterprise architecture advisory.
Documentation and knowledge transfer for long-term maintainability.
Assessment of current IT environments and development of transformation strategies.
Consulting on IT governance, standards alignment, and digital infrastructure planning.
Group 2 – (Enterprise IT Systems) Data Analytics, IT Architecture and Business Intelligence: This group includes Contractors with demonstrated expertise in the assessment, design, and implementation of enterprise-level data analytics, business intelligence and IT architecture. Services support operational insights, performance optimization, and data-driven decision-making across airport systems and departments. IT Consulting Services may include but are not limited to:
Assessment and implementation of advanced analytics infrastructure.
Development of dashboards and reporting tools for operational insights.
Integration of data from airport systems for real-time and historical analysis.
Predictive modeling for resource planning and operational efficiency.
Optimization of terminal capacity and passenger flow using data analytics.
Support for enterprise-wide business intelligence initiatives.
Configure and optimize BI tools to support real-time dashboards, reporting, and analytics.
Integrate CRM systems with airport operations and customer data sources to enable personalized services and feedback loops.
Develop automated CRM workflows for customer service, incident tracking, and loyalty programs.
Enhance existing EAMS platforms to improve asset tracking, lifecycle management, and maintenance scheduling.
Implement optimization strategies for asset utilization, downtime reduction, and cost control.
Integrate EAMS with IoT sensors, GIS systems, and mobile inspection tools to support smart asset management.
Group 3 – AI/ML and Emerging Technologies: This group includes Contractors with demonstrated expertise in AI, including generative AI, agentic AI, ML, computer vision, and other emerging technologies applicable to the advancement of airport operations, infrastructure, and passenger services. Due to the rapid pace of innovation in AI, Contractors must demonstrate adaptability to rapid technological change and maintain or acquire the necessary qualifications and capabilities to meet the evolving requirements throughout the duration of the contract. IT Consulting Services may include but are not limited to:
Establishing AI governance frameworks for ethical, secure, and effective deployment.
Supporting smart infrastructure initiatives with predictive and autonomous AI capabilities.
Enhancing passenger experience through AI-enabled personalization and real-time responsiveness.
Custom LML model development.
Implementing AI-driven threat detection and model integrity safeguards.
Leveraging predictive maintenance to reduce downtime and extend asset life.
Deploying AI-powered surveillance for anomaly detection and incident response.
Enabling operational alerting through AI-integrated SCADA and IoT systems.
Developing AI models for terminal energy forecasting and dynamic optimization.
Analyzing passenger demographics, flight schedules, and foot traffic to optimize concession planning.
Group 4 – Airport Technology Strategy & Integration: This group includes Contractors with proven expertise in researching, piloting, deploying, and optimizing advanced technologies within airport environments. Services are aligned with Airport 4.0 framework and aim to enhance passenger experience, streamline operations, increase revenue, and drive innovation. Contractors must demonstrate a deep understanding of aviation-specific challenges and the integration of IT/OT systems in complex airport ecosystems. IT Consulting Services may include but are not limited to:
Passenger experience technology design and implementation (e.g., self-bag drop, mobile apps, passenger flow, remote check-in).
Evaluation and optimization of airport operational technologies (e.g., AODB, RMS, BHS, ramp turnaround).
Development of digital twin strategies and roadmaps for airport environments.
Modeling of terminals, airfields, facilities, and systems to simulate operations and predict outcomes.
Development of smart airport strategies using IoT, sensors, and connected infrastructure.
Integration of digital systems across landside, airside, and terminal operations support for pilot programs, technology trials, and innovation roadmaps.
Private Wireless network architecture and backhaul design.
Site surveys and RF propagation modeling.
CBRS spectrum access system (SAS) integration.
Wireless network slicing and QoS configuration for critical applications.
Ongoing monitoring, optimization, and managed services.
Deployment of CBSDs, radio access network (RAN) base stations.
Each group includes representative services that illustrate the types of engagements anticipated under this contract. These examples are not exhaustive. As technology continues to evolve and throughout the contract period, the City may propose additional representative services within each group to ensure the QVL remains responsive to emerging needs while maintaining access to a vetted pool of Contractors capable of supporting strategic initiatives, accelerating innovation, and delivering resilient, future-ready IT operations.
3.4. Subcontracting Requirements
If a Contractor relies on a subcontractor to meet any minimum qualification or experience requirement for a specific Group, the City requires that the same subcontractor actively perform the work associated with that Group for all resulting Statements of Work (SOWs) issued under the Qualified Vendors List (QVL). The subcontractor’s role, responsibilities, and level of involvement must be consistent with the qualifications used to establish eligibility for that Group.
Offerors shall clearly identify any such subcontractors in their Offer, including the specific Group(s) for which the subcontractor’s qualifications are being submitted. Upon award to the QVL, the Offeror shall ensure the proposed subcontractor remains engaged for the performance of work within that Group unless otherwise approved in writing by the City. Requests to replace, remove, or materially reduce a qualifying subcontractor’s participation will not be accepted without prior written approval by the ADR or her designee and may result in removal from the QVL for that Group.
B. Continuous Compliance and Verification
The Contractor and subcontractor must maintain compliance with all requirements for the full duration of the Contract. The Airport reserves the right to verify qualifications, request documentation, or audit performance at any time.
3.5. Payments
Each invoice will be accompanied with itemized receipts, if applicable. The invoice will be submitted free of mathematical errors and/or missing supporting documentation. All appropriate documentation will be provided that supports the charges reflected in the invoice. Upon finding an error and/or missing documentation, the City will return the invoice to Contractor. Contractor will promptly resubmit the revised invoice to the City. Each revised invoice will document the date that the revised invoice is submitted to the City.
Contractor’s requests for payment must be submitted with documentation of dates and hours worked, hourly rate charged, and a detailed description of the services performed. Failure of the City to identify an error does not waive any of the City's rights.
3.6. Additional Work Unrelated to Aviation Projects
Contractor will not engage with or solicit other Aviation business partners without prior approval of the ADR or her designee.
Aviation will not pay for any hours Contractor and/or its' employees spend on contract administration and/or Contractor's staff meetings.
Any additional work unrelated to projects approved by Technology will not be charged to Aviation without prior approval of the ADR or her designee.
3.7. Reimbursable Expenses
Pre-approved reimbursable expenses, if applicable, will be reimbursed with no additional charges for overhead, benefits, administrative support, or related expenses. All reimbursable expenses must be pre-approved by the ADR or her designee in writing and must be reasonable and prudent. Travel will be reimbursable for Aviation projects that require travel. Travel will only be reimbursable with prior written approval from the ADR or her designee.
3.8. Parking Accomodations
The City will provide parking in the vicinity of the work site for up to six (6) contract employees. Parking privileges assigned to contract employees may be used only during assigned work hours. The Contractor will be assessed an administrative fee and a monthly fee for each contract employee requiring a parking access card in accordance with Phoenix City Code §4-58 (C). The administrative fee and the monthly fee are considered reimbursable. Replacement cards due to loss or damage will be assessed fees in accordance with Phoenix City Code §4-58 (C); these fees are not reimbursable.
3.9. Remote Access to City Networked Assets
Access to any City networked asset is only granted to the Contractor and its subcontractors if Aviation’s Assistant Chief Information Officer or his/her designee determines there is a contractual reason for such remote access. Privileged Remote Access is the term used by Aviation for remote access given to contractors who require access to certain City-networked assets such as, but not limited to, servers, business applications, and data.
Each individual requesting a Privileged Remote Access account must successfully complete a background screening and security check at Contractor’s sole cost and expense. The background screening provided by the Contractor will comply with all applicable laws, rules, and regulations.
Contractor and its subcontractors understand that the City may, from time to time and at its sole discretion, make changes to the security infrastructure in order to protect the interests of its citizens. Such changes may require the Contractor and its subcontractor to reconfigure or change elements of their access to Privileged Remote Access and that such changes may occur without prior notification. Any changes in Privileged Remote Access methods are wholly the responsibility of the Contractor and its subcontractors and the City will not be liable for any expenses incurred by the Contractor and its subcontractors in having to update their Privileged Remote Access. A current list of acceptable operating systems, anti-virus, and firewalls may be made available upon request by the Contractor.
Contractor and its subcontractors will comply with all applicable City standards, policies, and procedures for access privileges, copies of which may be made available to Contractor and its subcontractors upon request.
Contractor's and its subcontractors' access will be immediately revoked by the City upon termination, cancellation, or expiration of this Contract.
The City requires Contractor or its subcontractor to access its systems remotely using secure Multi-Factor Authentication (MFA) method. The Contractor or its subcontractor must be able to use City’s MFA solution in order to gain remote access. Contractor or its subcontractor may not be able to get an exception for this cybersecurity requirement where remote access is required.
3.10. Account Management Procedures
Every individual who uses a City computer system will be assigned a unique user ID in accordance with City information technology standards and procedures. Every City-issued user ID and related password is intended for the exclusive use of a specific individual. While user IDs can be shared in electronic mail messages and in other places, passwords will never be shared with anyone.
Individuals are responsible for all activity that takes place with their City provided user ID and password or other authentication mechanism. Individuals will change their passwords immediately if they suspect they have been discovered or used by another person.
Individuals will log off from multi-user systems connected to any City internal network when they leave their desks for more than a few minutes.
Individuals will not test or attempt to compromise computer or communication system security measures. Incidents involving unapproved system hacking, password guessing, file decryption, bootleg software copying, or similar unauthorized attempts to compromise security measures may be unlawful and may result in immediate termination of this Contract without notice. Shortcuts bypassing systems security measures, pranks, and practical jokes involving the compromise of systems security measures are absolutely prohibited.
Contractor will report all significant changes in staff duties or employment status promptly to the system administrator responsible for applicable user IDs.
Contractor will immediately notify the ADR if other access control mechanisms are broken or if it suspects that these mechanisms have been compromised.
3.11. Change Management Procedures
Contractor will comply with all applicable change management procedures as prescribed by the Aviation Department.
4. Minimum Qualifications
To be considered for inclusion on the QVL, the qualified and responsive Offeror must meet the minimum qualifications listed below. Offerors may submit Offers for any groups for which they meet the specified qualifications. Offerors are allowed and encouraged to subcontract, as necessary, to ensure they can meet all required group qualifications described in this Solicitation. Any proposed subcontracting arrangements must comply with all applicable requirements of the Solicitation and must be clearly identified in the Offeror’s Offer. The Offeror, whether through its own qualifications or those of its subcontractors, must meet the minimum qualifications for each Group. Failure to meet the minimum qualifications for any Group will result in the Offeror being deemed nonresponsive for that Group.
1. Group 1 - General IT Consulting
Offeror must have experience in providing General IT Consulting services for a minimum of five (5) consecutive years in the last ten (10) years.
Scoring Method:
Pass / Fail
Weight (Points):
1 (20% of Total)
2. Group 2 - Enterprise IT Systems
Offeror must have experience in providing Enterprise IT Systems services for a minimum of five (5) consecutive years in the last ten (10) years.
Scoring Method:
Pass / Fail
Weight (Points):
1 (20% of Total)
3. Group 3 - AI/ML & Emerging Technologies
Offeror must have experience in providing AI/ML & Emerging Technology services for a minimum of three (3) consecutive years in the last five (5) years.
Scoring Method:
Pass / Fail
Weight (Points):
1 (20% of Total)
4. Group 4 - Airport Technology Strategy & Integration
Offeror must have experience in providing Airport Technology Strategy & Integration services for a minimum of five (5) consecutive years in the last ten (10) years.
Scoring Method:
Pass / Fail
Weight (Points):
1 (20% of Total)
5. Additional Evaluation Factors
Because the resulting Contract may involve processing personal or other sensitive data, the City will conduct a Data Privacy Screening as a minimum qualification using the Data Privacy Questionnaire included in the Vendor Questionnaire. Only Offerors that pass this screening will proceed to further evaluation.
The City will assess the Offeror’s risk profile based on this document, aiming to determine if the Offeror’s IT security practices align with the required security standards and present an acceptable level of risk. The risk assessment results will be a significant factor in determining the Offeror’s pre-award qualification status. Offerors who do not receive favorable risk assessment may be disqualified from further consideration in the procurement process.
Failure to submit the Data Privacy Questionnaire, or failure to meet the minimum standard, will result in the Offer being deemed nonresponsive.
The City may verify statements, request clarifications regarding the Data Privacy Questionnaire or supporting documents and reject Offers that contain misrepresentations.
Scoring Method:
Pass / Fail
Weight (Points):
1 (20% of Total)
5. Standard Terms and Conditions
5.1. Definition of Key Words Used in the Solicitation
Shall, Will, Must: Indicates a mandatory requirement. Failure to meet these mandatory requirements may result in the rejection of Offer as non-responsive.
Should: Indicates something that is recommended but not mandatory. If the Offeror fails to provide recommended information, the City may, at its sole option, ask the Offeror to provide the information or evaluate the Offer without the information.
May: Indicates something that is not mandatory but permissible.
For purposes of this Solicitation, the following definitions will apply:
“A.R.S.” Arizona Revised Statute
“Buyer” or “Procurement Officer” means the City of Phoenix staff person responsible for the Solicitation. The City employee or employees who have specifically been designated to act as a contact person or persons to the Contractor, and responsible for monitoring and overseeing the Contractor's performance under this contract.
"City" means the City of Phoenix
"Contractor" means the individual, partnership, or corporation who, as a result of the competitive process, is awarded a contract by the City of Phoenix.
"Contract” or “Agreement" means the legal agreement executed between the City of Phoenix and the Contractor.
“Days” mean calendar days unless otherwise specified.
“Chief Procurement Officer” means the contracting authority for the City of Phoenix authorized to sign contracts and amendments thereto on behalf of the City of Phoenix.
“Employer” means any individual or type of organization that transacts business in this state, that has a license issued by an agency in this state and employs one or more employees in this state. Employer includes this state, any political subdivision of this state and self-employed persons. In the case of an independent contractor, employer means the independent contractor and does not mean the person or organization that uses contract labor. (A.R.S. 23-211).
“Offer” means a response from a Supplier, Contractor, or Service Provider to a Solicitation request that, if awarded, binds the Supplier, Contractor, or Service Provider to perform in accordance with the contract. Same as bid, proposal, quotation or tender.
“Offeror” means any Vendor, Seller or Supplier submitting a competitive offer in response to a Solicitation from the City. Same as Bidder or Proposer.
“Solicitation” means an Invitation for Bid (IFB), Request for Proposal (RFP), Request for Quotations (RFQ), Request for Qualifications (RFQu) and request for sealed Offers, or any other type of formal procurement which the City makes public through advertising, mailings, or some other method of communication. It is the process by which the City seeks information, proposals, Offers, or quotes from suppliers.
“Suppliers” means firms, entities or individuals furnishing goods or services to the City.
“Vendor or Seller” means a seller of goods or services.
5.2. 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 are required to register in the City’s procurePHX Self-Registration System (https://eprocurement.phoenix.gov/irj/portal) prior to contract execution. Registration is not required at the time of offer submission. However, the City will not execute a contract with any awarded vendor until registration is complete.
5.3. Business in Arizona
The City will not enter contracts with Offerors (or any company(ies)) not granted authority to transact business, or not in good standing, in the state of Arizona by the Arizona Corporation Commission, unless the Offeror asserts a statutory exception prior to entering a contract with the City.
5.4. Contract Interpretation
Applicable Law: This Contract will be governed by the law of the State of Arizona, and suits pertaining to this Contract will be brought only in Federal or State courts in Maricopa County, State of Arizona.
Contract Order of Precedence: In the event of a conflict in the provisions of the Contract, as accepted by the City and as they may be amended, the following will prevail in the order set forth below:
Federal terms and conditions, if any
Special terms and conditions
Standard terms and conditions
Amendments
Statement or Scope of Work
Specifications
Attachments
Instructions to Contractors
Other documents referenced or included in the Solicitation
Organization – Employment Disclaimer: The Agreement resulting hereunder is not intended to constitute, create, give rise to or otherwise recognize a joint venture Agreement or relationship, partnership or formal business organization of any kind, and the rights and obligations of the parties will be only those expressly set forth in the Agreement. The parties agree that no persons supplied by the Contractor in the performance of Contractor’s obligations under the Agreement are considered to be City’s employees and that no rights of City civil service, retirement or personnel rules accrue to such persons. The Contractor will have total responsibility for all salaries, wage bonuses, retirement, withholdings, workmen’s compensation, occupational disease compensation, unemployment compensation, other employee benefits and all taxes and premiums appurtenant thereto concerning such persons, and will save and hold the City harmless with respect thereto.
Severability: The provisions of this Contract are severable to the extent that any provision or application held to be invalid will not affect any other provision or application of the contract which may remain in effect without the invalid provision or application.
Non-Waiver of Liability: The City of Phoenix as a public entity supported by tax monies, in execution of its public trust, cannot agree to waive any lawful or legitimate right to recover monies lawfully due it. Therefore, any Contractor agrees that it will not insist upon or demand any statement whereby the City agrees to limit in advance or waive any right the City might have to recover actual lawful damages in any court of law under applicable Arizona law.
Parol Evidence: This Agreement is intended by the parties as a final expression of their agreement and is intended also as a complete and exclusive statement of the terms of this agreement. No course of prior dealings between the parties and no usage in the trade will be relevant to supplement or explain any term used in this Contract. Acceptance or acquiescence in a course of performance rendered under this contract will not be relevant to determine the meaning of this Contract even though the accepting or acquiescing party has knowledge of the nature of the performance and opportunity to object.
5.5. Contract Administration and Operation
Records: All books, accounts, reports, files and other records relating to the contract will be subject at all reasonable times to inspection and audit by the City for five years after completion of the contract. Such records will be produced at a City of Phoenix office as designated by the City. Confidentiality will be maintained, and City will not violate any proprietary or other confidentiality agreements vendor has in place.
Discrimination Prohibited: Contractor agrees to abide by the provisions of the Phoenix City Code Chapter 18, Article V as amended. Any contractor, in performing under this contract, will not discriminate against any worker, employee or applicant, or any member of the public, because of race, color, religion, sex, national origin, age or disability nor otherwise commit an unfair employment practice. The supplier and/or lessee will take action to ensure that applicants are employed, and employees are dealt with during employment without regard to their race, color, religion, sex, or national origin, age or disability and adhere to a policy to pay equal compensation to men and women who perform jobs that require substantially equal skill, effort and responsibility, and that are performed within the same establishment under similar working conditions. Such action will include but not be limited to the following: Employment, promotion, demotion or transfer, recruitment or recruitment advertising, layoff or termination; rates of pay or other forms of compensation; and selection for training; including apprenticeship. The supplier further agrees that this clause will be incorporated in all subcontracts with all labor organizations furnishing skilled, unskilled and union labor, or who may perform any such labor or services in connection with this contract. Contractor further agrees that this clause will be incorporated in all subcontracts, job-contractor agreements or subleases of this agreement entered into by supplier/lessee.
Equal Employment Opportunity and Pay: In order to do business with the City, Contractor must comply with Phoenix City Code, 1969, Chapter 18, Article V, as amended, Equal Employment Opportunity Requirements. Contractor will direct any questions in regard to these requirements to the Equal Opportunity Department, (602) 262-6790.
For a Contractor with 35 employees or fewer: Contractor in performing under this Agreement shall not discriminate against any worker, employee or applicant, or any member of the public, because of race, color, religion, sex, national origin, age, or disability, nor otherwise commit an unfair employment practice. The Contractor will ensure that applicants are employed, and employees are dealt with during employment without regard to their race, color, religion, sex, national origin, age, or disability. Such action shall include but not be limited to the following: employment, promotion, demotion or transfer, recruitment or recruitment advertising, layoff or termination; rates of pay or other forms of compensation; and selection for training; including apprenticeship. The Contractor further agrees that this clause will be incorporated in all subcontracts related to this Agreement that involve furnishing skilled, unskilled and union labor, or who may perform any such labor or services in connection with this Agreement. Contractor further agrees that this clause will be incorporated in all subcontracts, Contractor agreements or subleases of this agreement entered into by supplier/lessee.
For a Contractor with more than 35 employees: Contractor in performing under this Agreement shall not discriminate against any worker, employee or applicant, or any member of the public, because of race, color, religion, sex, national origin, age, or disability, nor otherwise commit an unfair employment practice. The Contractor will ensure that applicants are employed, and employees are dealt with during employment without regard to their race, color, religion, sex, national origin, age, or disability, and shall adhere to a policy to pay equal compensation to men and women who perform jobs that require substantially equal skill, effort, and responsibility, and that are performed within the same establishment under similar working conditions. Such action shall include but not be limited to the following: employment, promotion, demotion or transfer, recruitment or recruitment advertising, layoff or termination; rates of pay or other forms of compensation; and selection for training; including apprenticeship. The Contractor further agrees that this clause will be incorporated in all subcontracts with all labor organizations furnishing skilled, unskilled and union labor, or who may perform any such labor or services in connection with this contract. Contractor further agrees that this clause will be incorporated in all subcontracts, job-Contractor agreements or subleases of this Agreement entered into by supplier/lessee. The Contractor further agrees not to discriminate against any worker, employee or applicant, or any member of the public, because of sexual orientation or gender identity or expression and shall ensure that applicants are employed, and employees are dealt with during employment without regard to their sexual orientation or gender identity or expression.
Documentation: Suppliers and lessees may be required to provide additional documentation to the Equal Opportunity Department affirming that a nondiscriminatory policy is being utilized.
Monitoring: The Equal Opportunity Department shall monitor the employment policies and practices of suppliers and lessees subject to this article as deemed necessary. The Equal Opportunity Department is authorized to conduct on-site compliance reviews of selected firms, which may include an audit of personnel and payroll records, if necessary.
Legal Worker Requirements: The City of Phoenix is prohibited by A.R.S. § 41-4401 from awarding a contract to any Contractor who fails, or whose subcontractors fail, to comply with A.R.S. § 23-214(A). Therefore, Contractor agrees that:
Contractor and each subcontractor it uses warrants their compliance with all federal immigration laws and regulations that relate to their employees and their compliance with A.R.S. § 23-214, subsection A.
A breach of a warranty under paragraph 1 will be deemed a material breach of the contract that is subject to penalties up to and including termination of the contract.
The City of Phoenix retains the legal right to inspect the papers of any Contractor or subcontractor employee who works on the contract to ensure that the Contractor or subcontractor is complying with the warranty under paragraph 1.
Health, Environmental, and Safety Requirements: The Contractor’s products, services and facilities will be in full compliance with all applicable Federal, State and local health, environmental and safety laws, regulations, standards, codes and ordinances, regardless of whether or not they are referred to by the City. At the request of City representatives, the Contractor will provide the City:
Environmental, safety and health regulatory compliance documents (written safety programs, training records, permits, etc.) applicable to services provided by the Contractor in this contract.
A list of all federal, state, or local (EPA, OSHA, Maricopa County, etc.) citations or notice of violations issued against their firm or their subcontractors including dates, reasons, dispositions and resolutions.
The City will have the right, but not the obligation to inspect the facilities, transportation vehicles or vessels, containers and disposal facilities provided by the Contractor or subcontractor. The City will also have the right to inspect operations conducted by the Contractor or subcontractor in the performance of this agreement. The City further reserves the right to make unannounced inspections of the Contractor’s facilities (during normal business hours).
Compliance with Laws: Contractor agrees to fully observe and comply with all applicable Federal, State and local laws, regulations, standards, codes and ordinances when performing under this Contract regardless of whether they are being referred to by the City. Contractor agrees to permit City inspection of Contractor’s business records, including personnel records to verify any such compliance. Because the contractor will be acting as an independent contractor, the City assumes no responsibility for the Contractor’s acts. Contractor shall comply with the provisions of the Supplemental Terms and Conditions to All Airport Contracts attached, marked Attachment A, and incorporated herein by this reference.
Lawful Presence Requirement: Pursuant to A.R.S. §§ 1-501 and -502, the City of Phoenix is prohibited from awarding a contract to any natural person who cannot establish that he or she is lawfully present in the United States. In order to establish lawful presence, this person must produce qualifying identification and sign a City-provided affidavit affirming that the identification provided is genuine. This requirement will be imposed at the time of contract award. In the event the prevailing responder is unable to satisfy this requirement, the City will offer the award to the next-highest scoring responder. The law does not apply to fictitious entities such as corporations, partnerships and limited liability companies.
Continuation During Disputes: Contractor agrees that notwithstanding the existence of any dispute between the parties, insofar as is possible, under the terms of the contract, the Contractor will continue to perform the obligations required of Contractor during the continuation of any such dispute unless enjoined or prohibited by an Arizona Court of competent jurisdiction.
Emergency Purchases: The City reserves the right to purchase from other sources those items which are required on an emergency basis and cannot be supplied immediately from stock by the Contractor.
5.6. Costs and Payments
General: Any prompt payment terms offered must be clearly noted by the Contractor on all invoices submitted to the City for the payment of goods or services received. The City will make every effort to process payment for the purchase of material or services within thirty to forty-five calendar days after receipt of a correct invoice, unless a good faith dispute exists to any obligation to pay all or a portion of the account. Payment terms are specified in the Offer.
Payment Deduction Offset Provision: Contractor acknowledges that the City Charter requires that no payment be made to any Contractor as long as there is an outstanding obligation due to the City. Contractor agrees that any obligation it owes to the City will be offset against any payment due to the Contractor from the City.
Late Submission of Claim by Contractor: The City will not honor any invoices or claims which are tendered one year after the last item of the account accrued.
Discounts: If applicable, payment discounts will be computed from the date of receiving acceptable products, materials and/or services or correct invoice, whichever is later to the date payment is mailed.
No Advance Payments: Advance payments are not authorized. Payment will be made only for actual services or commodities that have been received, unless addressed specifically in the Scope of work for subscription services.
Fund Appropriation Contingency: The Contractor recognizes that any agreement entered into will commence upon the day first provided and continue in full force and effect until termination in accordance with its provisions. The Contractor and the City herein recognize that the continuation of any contract after the close of any given fiscal year of the City, which ends on June 30th of each year, will be subject to the approval of the budget of the City providing for or covering such contract item as an expenditure therein. The City does not represent that said budget item will be actually adopted, said determination being the determination of the City Council at the time of the adoption of the budget.
Maximum Prices: The City will not be invoiced at prices higher than those stated in any contract resulting from this Offer. Contractor certifies, by signing this Offer that the prices offered are no higher than the lowest price the Contractor charges other buyers for similar quantities under similar conditions, as applicable and shown by quotes for like services and goods. Contractor further agrees that any reductions in the price of the goods or services covered by this Offer and occurring after award will apply to the undelivered balance. The Contractor will promptly notify the City of such price reductions.
F.O.B. Point: All prices are to be quoted F.O.B. destination, unless specified elsewhere in this Solicitation.
5.7. Contract Changes
Contract Amendments: Contracts will be modified only by a written contract amendment signed by persons duly authorized to enter into contracts on behalf of the Contractor. No verbal agreement or conversation with any officer, agent, or employee of the City either before or after execution of the contract, will affect or modify any of the terms or obligations contained or to be contained in the contract. Any such verbal agreements or conversation shall be considered as unofficial information and in no way binding upon the City or the Contractor. All agreements shall be in writing and contract changes shall be by written amendment signed by both parties.
Assignment - Delegation: No right or interest in this contract nor monies due hereunder will be assigned in whole or in part without written permission of the City, and no delegation of any duty of Contractor will be made without prior written permission of the City, which may be withheld for good cause. Any assignment or delegation made in violation of this section will be void.
Non-Exclusive Contract: Any contract resulting from this Solicitation will be awarded with the understanding and agreement that it is for the sole convenience of the City. The City reserves the right to obtain like goods or services from another source when necessary.
5.8. Risk of Loss and Liability
Title and Risk of Loss: The title and risk of loss of material or service will not pass to the City until the City actually receives the material or service at the point of delivery; and such loss, injury, or destruction will not release seller from any obligation hereunder.
Acceptance: All material or service is subject to final inspection and acceptance by the City. Material or service failing to conform to the specifications of this contract will be held at Contractor's risk and may be returned to the Contractor. If so returned, all costs are the responsibility of the Contractor. Noncompliance will conform to the cancellation clause set forth in this document.
Force Majeure: Except for payment of sums due, neither party will be liable to the other nor deemed in default under this contract if and to the extent that such party's performance of this contract is prevented by reason of force majeure. The term "force majeure" means an occurrence that is beyond the control of the party affected and occurs without its fault or negligence. Force majeure will not include late performance by a subcontractor unless the delay arises out of a force majeure occurrence in accordance with this force majeure term and condition. If either party is delayed at any time in the progress of the work by force majeure, the delayed party will notify the other party in writing of such delay, as soon as is practical, of the commencement thereof and will specify the causes of such delay in such notice. Such notice will be hand-delivered or mailed certified-return receipt and will make a specific reference to this provision, thereby invoking its provisions. The delayed party will cause such delay to cease as soon as practicable and will notify the other party in writing when it has done so. The time of completion will be extended by contract modification for a period of time equal to the time that results or effects of such delay prevent the delayed party from performing in accordance with this contract.
Loss of Materials: The City does not assume any responsibility, at any time, for the protection of or for loss of materials, from the time that the contract operations have commenced until the final acceptance of the work by the City.
Contract Performance: Contractor will furnish all necessary labor, tools, equipment, and supplies to perform the required services at the City facilities designated, unless otherwise specifically addressed in the scope, or elsewhere in this Agreement. The City's authorized representative will decide all questions which may arise as to the quality and acceptability of any work performed under the contract. If, in the opinion of the City's authorized representative, performance becomes unsatisfactory, the City will notify the Contractor. The Contractor will have 30 days from that time to correct any specific instances of unsatisfactory performance, unless a different amount of time is specified in the agreement. In the event the unsatisfactory performance is not corrected within the time specified, the City will have the immediate right to complete the work to its satisfaction and will deduct the cost to cover from any balances due or to become due the Contractor. Repeated incidences of unsatisfactory performance may result in cancellation of the agreement for default.
Damage to City Property: Contractor will perform all work so that no damage to the building or grounds results. Contractor will repair any damage caused to the satisfaction of the City at no cost to the City. Contractor will take care to avoid damage to adjacent finished materials that are to remain. If finished materials are damaged, Contractor will repair and finish to match existing material as approved by the City at Contractor's expense.
5.9. City's Contractual Rights
Whenever one party to this contract in good faith has reason to question the other party's intent to perform, the former party may demand that the other party give a written assurance of this intent to perform. In the event that a demand is made and no written assurance is given within five days, the demanding party may treat this failure as an anticipatory repudiation of this contract.
Non-Exclusive Remedies: The rights and remedies of the City under this Contract are non-exclusive.
Default in One Installment to Constitute Breach: Each installment or lot of the agreement is dependent on every other installment or lot and a delivery of non-conforming goods or a default of any nature under one installment or lot will impair the value of the whole agreement and constitutes a total breach of the agreement as a whole.
On Time Delivery: Because the City is providing services which involve health, safety and welfare of the general public, delivery time is of the essence. Delivery must be made in accordance with the delivery schedule promised by the Contractor.
Default: In case of default by the Contractor, the City may, by written notice, cancel this contract and repurchase from another source and may recover the excess costs by (1) deduction from an unpaid balance due; (2) collection against the Solicitation and/or Performance Bond, or (3) a combination of the aforementioned remedies or other remedies as provided by law.
Covenant Against Contingent Fees: Seller warrants that no person or selling agent has been employed or retained to solicit or secure this contract upon an agreement or understanding for a commission, percentage, brokerage, or contingent fee, excepting bona fide employers or bona fide established commercial or selling agencies maintained by the seller for the purpose of securing business. For breach or violation of this warranty, the City will have the right to annul the contract without liability or in its discretion to deduct from the contract price a consideration, or otherwise recover the full amount of such commission, brokerage or contingent fee.
Cost Justification: In the event only one response is received, the City may require that the Contractor submit a cost proposal in sufficient detail for the City to perform a cost/price analysis to determine if the Offer price is fair and reasonable.
Work Product, Equipment, and Materials: All work product, equipment, or materials created or purchased under this contract belongs to the City and must be delivered to the City at City’s request upon termination of this contract. Contractor agrees to assign to City all rights and interests Contractor may have in materials prepared under this contract that are “works for hire” within the meaning of the copyright laws of the United States, including any right to derivative use of the material.
5.10. Contract Termination
Gratuities: The City may, by written notice to the Contractor, cancel this contract if it is found that gratuities, in the form of entertainment, gifts or otherwise, were offered or given by the Contractor or any agent or representative of the Contractor, to any officer or employee of the City making any determinations with respect to the performing of such contract. In the event this contract is canceled by the City pursuant to this provision, the City will be entitled, in addition to any other rights and remedies, to recover or withhold from the Contractor the amount of the gratuity.
Conditions and Causes for Termination:
This contract may be terminated at any time by mutual written consent, or by the City, with or without cause, upon giving thirty-day written notice to Contractor. The City at its convenience, by written notice, may terminate this contract, in whole or in part. If this contract is terminated, the City will be liable only for payment under the payment provisions of this contract for services rendered and accepted material received by the City before the effective date of termination. Title to all materials, work-in-process and completed but undeliverable goods, will pass to the City after costs are claimed and allowed. The Seller will submit detailed cost claims in an acceptable manner and will permit the City to examine such books and records as may be necessary in order to verify the reasonableness of any claims.
The City reserves the right to cancel the whole or any part of this contract due to failure of Contractor to carry out any term, promise, or condition of the contract. The City will issue a written notice of default to Contractor for acting or failing to act as in any of the following:
In the opinion of the City, Contractor provides personnel who do not meet the requirements of the contract;
In the opinion of the City, Contractor fails to perform adequately the stipulations, conditions or services/specifications required in this contract;
In the opinion of the City, Contractor attempts to impose on the City personnel or materials, products or workmanship, which is of an unacceptable quality;
Contractor fails to furnish the required service and/or product within the time stipulated in the contract;
In the opinion of the City, Contractor fails to make progress in the performance of the requirements of the contract and/or gives the City a positive indication that Contractor will not or cannot perform to the requirements of the contract.
Contract Cancellation: All parties acknowledge that this contract is subject to cancellation by the City of Phoenix pursuant to the provision of Section 38-511, Arizona Revised Statutes.
5.11. Notice
All notices, consents, approvals, and other communications (notices) between the City and Contractor that are required to be given under this Contract shall be in writing and given by (A) personal delivery, (B) email with return receipt requested (read receipt), (C) facsimile transmittal with delivery confirmation, (D) prepaid delivery to any commercial air courier or express delivery service, or (E) registered or certified mail, postage prepaid and return receipt requested, through the United States Postal Service.
Notices to the City shall be sent to both:
City of Phoenix Aviation Department
Aviation Headquarters
ATTN: Procurement & Compliance Services Division
2485 East Buckeye Road
Phoenix, AZ 85034
Facsimile: 602-273-2080
Email: avn.contract.services@phoenix.gov
City of Phoenix Aviation Department
Technology Division
ATTN: Genie, Usher, Management Assistant II
2485 East Buckeye Road
Phoenix, AZ 85034
Email: genie.usher@phoenix.gov
Notice to Contractor shall be sent to the person at the mailing address, email address, or fax number listed by Contractor in its Offer Page of this Contract.
Notice given in compliance with this Section is deemed received (A) on the day it is personally delivered, (B) on the day it is sent by email, (C) on the day it is sent by facsimile transmittal, (D) two (2) days after it is deposited with any commercial air courier or express delivery service, or (E) five (5) days after it is sent by registered or certified mail as provided above. Any time period stated in a notice shall commence on the date the notice is deemed received. Actual receipt is not required.
If notice is sent by email or facsimile transmittal, then a paper copy shall be sent by prepaid regular first-class mail through the United States Postal Service to the Party at the address listed above. Duplicate notice is merely a courtesy and does not change or extend the effective date of the notice. The failure to receive the duplicate notice does not affect the validity of the notice sent by email or facsimile transmittal.
5.12. State and Local Transaction Privilege Taxes
In accordance with state and local law, transaction privilege taxes may be applicable to this transaction. The state and local transaction privilege (sales) tax burden and legal liability to remit taxes are on the Contractor that is conducting business in Arizona and the City of Phoenix. Any failure by the Contractor to collect applicable taxes from the City will not relieve the Contractor from its obligation to remit taxes. It is the responsibility of the prospective bidder to determine any applicable taxes. The City will look at the price or offer submitted and will not deduct, add or alter pricing based on any taxes, nor will the City provide advice or guidance. If you have questions regarding your tax liability, please seek advice from a tax professional prior to submitting your Offer. You may also find information at https://www.phoenix.gov/finance/plt or https://www.azdor.gov/Business. Once your Offer is submitted, the Offer is valid for the time specified in this Solicitation, regardless of mistake or omission of tax liability. If the City finds over payment of a project due to tax consideration that was not due, the Contractor will be liable to the City for that amount, and by contracting with the City, the Contractor agrees to remit any overpayments back to the City for miscalculations on taxes included in an offer price.
5.13. Tax Indemnification
Contractor will pay all federal, state and local taxes applicable to its operation and any persons employed by the Contractor, and require the same of all subcontractors. Contractor will hold the City harmless from any responsibility for: taxes, penalties and interest, if applicable, contributions required under federal, and/or state and local laws and regulations, and any other costs including unemployment compensation insurance, Social Security and Worker's Compensation, and require the same of all subcontractors.
5.14. Tax Responsibility Qualification
Contractor may be required to establish, to the satisfaction of City, that any and all fees and taxes due to the City or the State of Arizona for any License or Transaction Privilege taxes, Use Taxes or similar excise taxes, are currently paid (except for matters under legal protest). Contractor agrees to a waiver of the confidentiality provisions contained in the City Finance Code and any similar confidentiality provisions contained in Arizona statutes relative to State Transaction Privilege Taxes or Use Taxes. Contractor agrees to provide written authorization to the City Finance Department and to the Arizona Department of Revenue to release tax information relative to Arizona Transaction Privilege Taxes or Arizona Use Taxes in order to assist the Department in evaluating Contractor's qualifications for and compliance with contract for duration of the term of contract.
5.15. No Israel Boycott
If this Contract is valued at $100,000 or more and requires Contractor (a company engaging in for-profit activity and having ten or more full-time employees) to acquire or dispose of services, supplies, information technology, or construction, then Contractor must certify and agree that it does not and will not boycott goods or services from Israel, pursuant to Title 35, Chapter 2, Article 9 of the Arizona Revised Statutes. Provided that these statutory requirements are applicable, Contractor by entering this Contract now certifies that it is not currently engaged in, and agrees for the duration of the Contract to not engage in, a boycott of goods or services from Israel.
5.16. No Forced Labor of Ethnic Uyghurs
If this Contract requires Contractor (a company engaging in for-profit activity and having ten or more full-time employees) to acquire or dispose of services, supplies, information technology, goods, or construction, then pursuant to Title 35, Chapter 2, Article 10 of the Arizona Revised Statutes Contractor must certify and agree that it and any contractors, subcontractors, or suppliers it utilizes do not and will not use the forced labor of ethnic Uyghurs in the People’s Republic of China or any goods or services produced by such forced labor. Provided these statutory requirements are applicable, Contractor, by entering this Contract, now certifies it is not currently engaged in, and agrees for the duration of the Contract to not engage in, (a) the use of forced labor of ethnic Uyghurs in the People’s Republic of China; (b) the use of any goods or services produced by the forced labor of ethnic Uyghurs in the People’s Republic of China; or (c) the use of any contractors, subcontractors, or suppliers that use the forced labor or any goods or services produced by the forced labor of ethnic Uyghurs in the People’s Republic of China.
5.17. Advertising
Except as required by law, Contractor shall not publish, release, disclose or announce to any member of the public, press, official body, or any other third party any information or documents concerning this Agreement or any part thereof without the prior written consent of the City. The name of any City site on which services are performed by the Contractor pursuant to this Agreement shall not be used in any advertising or other promotional context by Contractor without the prior written consent of the City. Please refer to the Aviation Department's Contractor Communication Procedures at https://www.skyharbor.com/airport-business/on-airport-business/consultants-contractors-tenants/.
5.18. Strict Performance
Failure of either party to insist upon the strict performance of any item or condition of the contract or to exercise or delay the exercise of any right or remedy provided in the contract, or by law, or the acceptance of materials or services, obligations imposed by this contract, or by law, will not be deemed a waiver of any right of either party to insist upon the strict performance of the contract.
5.19. Authorized Changes
The City reserves the right at any time to make changes in any one or more of the following: (a) specifications; (b) methods of shipment or packing; (c) place of delivery; (d) time of delivery; and/or (e) quantities. If the change causes an increase or decrease in the cost of or the time required for performance, an equitable adjustment may be made in the price or delivery schedule, or both. Any claim for adjustment will be deemed waived unless asserted in writing within sixty days from the receipt of the change. Price increases or extensions of delivery time will not be binding on the City unless evidenced in writing and approved by the Chief Procurement Officer prior to the institution of the change.
5.20. Attorney Fees
In any contested action related to or arising out of this Contract, the prevailing party shall recover its attorney fees, court costs, and other expenses from the other party. Where there are no competing claims, “prevailing party” means the party that substantially obtained the relief sought. Where there are competing claims, the prevailing party is the net winner or the party who prevailed in a totality of the litigation.
5.21. Headings
Headings for articles, sections, and paragraphs are for reference only and do not limit the content or scope of any provision of this Contract.
5.22. National Emergency
This Contract is subject to the right of the United States to control, operate, and regulate the Airport and to use of the Airport during the time of war or national emergency.
5.23. No Impairment of Title
Contractor and its agents, employees, and contractors shall not cause or allow any person or entity to cause any lien, cloud, charge, or encumbrance to be filed, recorded, or imposed on the Airport or any portion thereof.
5.24. No Personal Liability
The City’s officers, officials, agents, and employees are not personally liable to Contractor for any default or breach of this Contract by the City, are not liable for any amount that may become due to Contractor, and are not obligated to perform under any provision of this Contract.
5.25. Successors and Assigns
This Contract binds the parties and their owners, officers, directors, managers, members, agents, employees, representatives, trustees, executors, personal representatives, and successors.
5.26. Termination for Non-Appropriation of Funds
This Contract is contingent on the appropriation of adequate funds by the Phoenix City Council for each fiscal year during the term of this Contract. If adequate funds are not appropriated, then this Contract shall terminate on June 30 of the last fiscal year for which funds were appropriated. The termination shall be without penalty or any liability by the City.
5.27. Breach and Remedies for Breach
The occurrence of any of the following events shall be deemed a material breach of this Contract by Contractor:
Contractor fails to pay any amount when due and the failure continues for ten (10) days after notice from the City.
Except for the non-monetary events of breach listed below, Contractor fails to perform any non-monetary obligation under this Contract and the failure continues for ten (10) days after notice from the City.
Contractor fails to procure and maintain the insurance coverages required under this Contract and the failure continues for one (1) day after notice from the City.
Contractor breaches any other lease, contract, agreement, or permit it has with the City.
Contractor files a voluntary petition in bankruptcy; is adjudicated bankrupt or insolvent; takes the benefit of any law applicable to bankrupt or insolvent debtors; files a petition or action seeking reorganization, arrangement, composition, readjustment, liquidation, dissolution, or similar relief; seeks or acquiesces to the appointment of a trustee, receiver, or liquidator of all or a substantial part of Contractor’s assets; or makes any general assignment for the benefit of creditors.
Contractor violates any federal, state, or local law, rule, regulation, or ordinance related to this Contract and the violation continues for ten (10) days after notice from the City.
Upon the occurrence of any breach by Contractor, the City may elect to do any or all the following at one time or over a period of time:
File a civil action or actions to, among other things, enforce this Contract and recover all amounts due, all attorney fees, court costs, and other expenses incurred.
Exercise any and all remedies allowed at law or in equity.
Recover all attorney fees, court costs, and other expenses incurred, whether or not a civil action or other judicial proceeding is filed.
The City’s exercise of any remedy does not terminate and shall not be construed to terminate this Contract. Termination of this Contract must be evidenced by a writing signed by the City for that purpose. The foregoing list of remedies is not exhaustive, and the rights and remedies of the City under this Contract are non-exclusive.
5.28. Claims Against the City
Contractor shall comply with the procedures set forth in Chapter XVIII, § 14 of the Charter of the City of Phoenix (claims or demands against the City) and A.R.S. § 12-821 and § 12-821.01 (notice of claim statutes) for presenting claims or demands against the City. Nothing in this Contract constitutes a contractual term that requires a dispute resolution process, an administrative claims process, or review process, as those terms are used in A.R.S. § 12-821.01(C), so as to affect the date on which a cause of action accrues under A.R.S. § 12-821.01(A) and (B).
5.29. Delinquent Account Fee
Any amount that is not paid by Contractor when due is deemed delinquent. If the delinquent amount remains unpaid for ten (10) days, then a delinquent account fee of eighteen percent (18%) per annum shall be assessed according to Phoenix City Code § 4-7. Delinquent account fees shall be computed and accrued on a daily basis and assessed until the account balance, including delinquent account fees, is paid in full. Delinquent account fees are due from Contractor upon demand by the City.
5.30. Entire Agreement
This Contract constitutes the entire agreement between the parties and supersedes all prior written and oral agreements, understandings, discussions, proposals, negotiations, communications, representations, and correspondence related to this Contract. The parties are not bound by any obligation not provided for in this Contract. Contractor certifies that it was not induced to enter into this Contract by any misrepresentation, undue influence, or coercion by the City or any of its officers, officials, agents, or employees. The Exhibits attached to this Contract are material parts of this Contract and are incorporated herein by this reference.
5.31. Fair Interpretation
Contractor agrees that the rule that ambiguous or vague language in a contract is construed against the drafter is waived and does not apply to this Contract. Contractor agrees that this Contract shall be interpreted fairly and not against the City simply because the City drafted this Contract.
5.32. No Third-Party Beneficiaries
Except as expressly provided in this Contract, nothing contained herein creates or may be construed to create any right or privilege in any person or entity that is not a party to this Contract.
5.33. Contractor Requirements for the Mitigation of Heat-Related Illnesses and Injuries in the Workplace
Any Contractor whose employees and contract workers perform work in an outdoor environment under this contract must keep on file a written heat safety plan. The City may request a copy of this plan and documentation of all heat safety and mitigation efforts currently implemented to prevent heat-related illnesses and injuries in the workplace. The plan must also be posted in English and Spanish on a bulletin board in a break room where it is accessible to employees. If a Contractor does not have a break room, the heat safety plan must be physically placed in a conspicuous location in the workplace where notices to employees are customarily posted. The heat safety plan must also include a contact number of the contractor that all employees and contract workers can call if they need to inquire or report any heat safety issues and contain language that the contractor will not retaliate against any employee or contract worker who reports an alleged heat safety violation or who otherwise avails themselves of the protections provided in this article. At a minimum, the heat safety and mitigation plan and documentation required under this provision shall include each of the following as it relates to heat safety and mitigation:
Availability of sanitized cool drinking water free of charge at locations that are accessible to all employees and contract workers.
Ability to take regular and necessary breaks as needed and additional breaks for hydration.
Access to shaded areas and/or air conditioning.
Access to air conditioning in vehicles with enclosed cabs. Beginning on April 1, 2026, all Contractors shall regularly monitor vehicles to ensure all vehicles with enclosed cabs have properly functioning air conditioning per the manufacturer specifications. The heat safety and mitigation plan shall include how the Contractor will monitor vehicle air conditioning to comply with this subsection.
Effective acclimatization practices to promote the physiological adaptations of employees or contract workers newly assigned or reassigned to work in an outside environment.
Conduct training and make it available and understandable to all employees and contract workers on heat illness and injury that focuses on the environmental and personal risk factors, prevention, how to recognize and report signs and symptoms of heat illness and injury, how to administer appropriate first aid measures and how to report heat illness and injury to emergency medical personnel.
In addition to the documents required in subsections A - F above, upon request Contractors shall provide additional documentation verifying that mitigation efforts to protect against heat related illness or injury in the workplace are being utilized.
Contractor shall sign and return to the City a submittal acknowledging and confirming Contractor’s ability to comply with Phoenix City Code Sections 18-413, 414, and 415.
The Contractor further agrees that this clause will be incorporated in all subcontracts with subcontractors, sublicensees or sublessees who may perform labor or services in connection with this Contract. Additionally, the Contractor agrees to require all subcontractors, sublicensees or sublessees to include this clause in all contracts with any third party who is contracted to perform labor or services in connection with this contract. It is the obligation of the Contractor to ensure compliance by its subcontractors.
5.34. Release of Information - Advertising and Promotion
Contractor will not publish, release, disclose or announce to any member of the public, press, official body, or any other third party: (1) any information concerning this Agreement, the Services, or any part thereof; or (2) any documentation or the contents thereof, without the prior written consent of the City, except as required by law. The name of any site on which Services are performed will not be used in any advertising or other promotional context by Contractor without the prior written consent of the City.
6. Special Terms and Conditions
6.1. Term of Contract
The term of this Contract will commence on or about April 1, 2027 and will continue for a period of five (5) years thereafter. This Contract includes two (2) one-year options to extend the term, for an aggregate seven (7) years, which may be exercised by the sole discretion of the Aviation Director.
6.2. Method of Ordering
Contractor shall deliver items and/or services only upon receipt of a written purchase order. All Contractor invoices and packing/delivery tickets must include the City of Phoenix purchase order number.
6.3. Method of Invoicing
Invoice must be emailed in .pdf format to invoices@phoenix.gov and must include the following:
City purchase order number or shopping cart number
Items listed individually by the written description and part number
Unit price, extended and totaled
Quantity ordered, back ordered, and shipped
Applicable tax
Invoice number and date
Delivery address
Payment terms
FOB terms
Remit to address
If applicable, retail and cost after margin discount/change shall be conspicuously set forth on all invoices. Both the list price and resulting net price must be included.
6.4. Method of Payment
Payment to be made from Contractor’s invoice and a copy of the signed delivery/service ticket submitted to cover items received and accepted during the billing period.
6.5. Partial Payments
Partial payments are authorized on individual purchase orders. Payment will be made for actual goods and services received and accepted by the City.
6.6. Supplier Profile Changes
It is the responsibility of the Contractor to promptly update their profile in procurePHX at https://www.phoenix.gov/procure. If Contractor’s legal identity has changed, the Procurement Officer must be notified immediately. Failure to do so may result in non-payment of invoices and contract termination.
6.7. Suspensions of Work
The City reserves the right to suspend work wholly or in part if deemed necessary for the best interest of the City. This suspension will be without compensation to the Contractor, other than to adjust the contract completion/delivery requirements.
6.8. Hours of Work
All work under this contract shall be coordinated with the ADR or her designee. Any changes to the established schedule must have prior written approval by the ADR or her designee.
6.9. Performance Interference
Contractor shall notify the ADR or her designee immediately of any occurrence and/or condition that interferes with the full performance of the contract and confirm it in writing within 24 hours.
6.10. Cooperative Agreement
In addition to the City and with approval of the Contractor, this contract may be extended for use by other municipalities, public agencies owning public-use airports, and government agencies in the State of Arizona as well as other states.
6.11. Exclusive Possession
All services, information, computer program elements, reports, and other deliverables which may be created under this contract are the sole property of the City of Phoenix and will not be used by the Contractor or any other person except with prior written permission by the ADR or her designee.
6.12. Licenses and Permits
Contractor will keep current Federal, State, and local licenses and permits required for the operation of the business conducted by the Contractor as applicable to this contract.
6.13. Delivery / Service Ticket
Contractor shall provide a packing list or service ticket for items delivered to the City or services provided to the City. Tickets should include the following and a legible copy shall be provided to the City:
Date
City purchase order number
Written description of services which were provided
Itemized list of materials which were delivered, including quantity
A unique identification number and Contractor name
Signature of City employee who accepted for the materials/services
6.14. Miscellaneous Fees
Additional charges for fuel surcharges, delivery charges, dealer prep, environmental fees, waste disposal, shop supplies, set-up, freight and/or shipping and handling, etc. will not be paid. These costs must be incorporated in the pricing provided.
Labor rates (Shop and On-site) shall be charged as a flat hourly rate and are allowed only in performance of services under this agreement. Travel hours and other incidental fees will not be permitted under this agreement. Labor hours will be from “check-in” to “check-out” at the worksite.
6.15. Liquidated Damages
If the Contractor fails to deliver the supplies or perform the services within the time specified in its contract, or any extension thereof, the actual damages to the City for the delay will be difficult or impossible to determine. Therefore, in lieu of actual damages, the Contractor shall pay to the City as fixed, agreed and liquidated damages for each calendar day of the delay, the amount of $500. The City may terminate this contract in whole or in part as provided in the “Default” provision. In that event, the Contractor shall be liable for such liquidated damages accruing until the City may reasonably obtain delivery or performance of similar supplies and services. The Contractor shall not be charged with liquidated damages when the delay arises out of causes beyond its control and without fault or negligence, as determined by the City. The Chief Procurement Officer will be the sole judge in determining the liquidated damages.
6.16. Warranty
Contractor warrants the hardware, software, application(s), or other technology assets provided to the City pursuant to this contract (collectively, the “Technology Assets”), for a period of one year starting with the date of final acceptance (the “Warranty Period”), to be substantially free of any condition which would make the Technology Assets fail to perform in material accordance with the requirements set forth in this Agreement, including any statement-of-work or scope-of-work document (each such condition to be considered an “Error”). Contractor specifically warrants that all software Technology Assets shall be free of any condition which could make them fail to perform in material accordance with this agreement (each such condition to also be considered an “Error”) for a period of nine months after actual installation of the software. If the City reports to Contractor any errors in the system during the Warranty Period, then Contractor shall, at its expense, use reasonable commercial efforts to modify, replace, or otherwise remedy the faulty hardware, software, electrical component or other Technology Assets as quickly as reasonably practicable. Where possible, both parties shall attempt to resolve Errors through telephone instruction, issuance of updated documentation, corrective code, or hardware replacement or modification.
Standards and Practices: Technology Assets shall conform to the generally accepted standards and practices of the trade or industry involved. All work shall be executed by personnel skilled in their respective lines of work.
Qualifications: Contractor represents that it is fully experienced and properly qualified; is in compliance with all applicable license requirements; and, is equipped, organized, and financed to provide and/or perform the goods and/or services purchased by the City pursuant to this agreement.
Intellectual Property Warranties: Contractor warrants that:
The Technology Assets will be free of the rightful claim of any third party for or by way of infringement or misappropriation of patent, copyright, trade secret, trademark or other rights arising under the laws of the United States;
No act or omission of Contractor will result in a third party holding any other claim that interferes with the City’s enjoyment or use of the Technology Assets;
Contractor owns or possesses all right(s), titles(s) and license(s) necessary to perform its obligations hereunder; and
As of the effective date and throughout the term of this Agreement, Contractor has not conveyed and will not convey any rights or licenses to any third party regarding the Technology Assets, except to the extent the Technology Assets consist of commercial-off-the-shelf or similar software product(s).
6.17. Communication in English
It is mandatory that the Contractor’s lead person assigned to any City facility can speak, read, and write in English to effectively communicate with City staff.
6.18. Contractor Worker Background Screening
Contractor agrees that all Contract Workers that Contractor allows to perform work under this Contract shall be subject to background and security checks and screening (Background Screening). Contractor must pay for the cost of all Background Screenings, unless otherwise provided in the Scope of Work. Contractor agrees that Background Screenings required by this Section is necessary to preserve and protect public health, safety, and welfare. The Background Screening requirements set forth in this Section are the minimum requirements for this Contract. The City does not warrant or represent that the minimum requirements are sufficient to protect Contractor from any liability that may arise out of Contractor’s work under this Contract or Contractor’s failure to comply with this Section. Therefore, in addition to the Background Screening measures set forth below, Contractor and its Contract Workers shall take such other reasonable, prudent, and necessary measures to further preserve and protect public health, safety, and welfare when providing work under this Contract.
As used in this Section, “Contract Worker” means a person performing work for the City, including (1) a person or entity that has a contract with the City, (2) a worker of a person or entity that has a contract with the City, (3) a worker of a subcontractor of a person or entity that has a contract with the City, and (4) a worker of a tenant of the City. (City of Phoenix A.R. 4.45)
6.19. Legal Worker Background Check
Pursuant to Arizona Revised Statutes (A.R.S.) § 41-4401, Contractor must verify the legal Arizona worker status of each Contract Worker. Contractor must conduct and all Contract Workers must pass a background check for their real identity and legal name prior to performing any work under this Contract.
6.20. City Rights Regarding Security Inquiries
In addition to a Legal Worker Background Check, the City reserves the right to require Contractor to:
Have a Contract Worker provide fingerprints and execute any document that is necessary to obtain criminal justice information pursuant to A.R.S. § 41-1750(G)(4) or Phoenix City Code § 4-22 or both;
Act on newly acquired information, whether or not the information should have been previously discovered;
Unilaterally change its standards and criteria related to the acceptability of Contract Workers; and
Object, at any time and for any reason, to a Contract Worker performing work under this Contract, including supervision and oversight services.
6.21. Contractor Certification
By entering into this Contract, Contractor certifies that Contractor has read the Background Screening requirements and criteria in this Section, understands them, and that all Background Screening information furnished to the City is accurate, complete, and current. A Contract Worker that is rejected for work under this Contract shall not perform any work under any other contract or engagement Contractor has with the City without the City’s prior written approval.
6.22. Contractor's Contracts and Subcontracts
Contractor shall include the terms of this Section for Contract Worker Background Screening in all contracts and subcontracts for work performed under this Contract, including supervision and oversight services.
6.23. Materiality of Background Screening Requirements and Indemnity
The Background Screening requirements of this Section are material to the City’s decision to enter into this Contract. Any breach of this Section by Contractor shall be deemed as a material breach of this Contract. In addition to any other indemnification provision in this Contract, Contractor shall defend, indemnify, and hold harmless the City from and against any and all claims, actions, liabilities, damages, losses, and expenses (Claims) arising out of this Background Screening Section, including the Contractor’s disqualification of any Contract Worker or the City’s failure to enforce this Section.
6.24. Continuing Duty and Audit
Contractor’s obligations to ensure that all Contract Workers pass a Background Screening pursuant to Section shall continue throughout the entire term of this Contract. Contractor shall immediately notify the City of any changes to a Contract Worker’s Background Screening. Contractor shall maintain all records and documents related to all Background Screenings and the City reserves the right to audit Contractor’s compliance with this Section.
6.25. Contract Worker Access Controls and Airport Security Badge Requirements
Contractor shall not allow a Contract Worker to begin work under this Contract until Contractor has completed the Background Screening required by the City and the City has issued the appropriate airport security badge to the Contract Worker. The airport security badge will grant the Contract Worker unescorted access authority only to the area or areas of the Airport that the Contract Worker must enter in order to perform work under this Contract. When a Contract Worker’s work in any area ends, the Contract Worker’s access authority to that area ends. Any Contract Worker that attempts to enter a restricted area or sterile area, as those terms are defined below, of the Airport without proper authority is an immediate breach of this Contract.
6.26. Security Identification Display Area (SIDA) Badge Process
Each Contract Worker that needs unescorted access authority to a restricted or sterile area of the Airport in order to perform work under this Contract must receive a security identification display area (SIDA) badge from the Aviation Department’s Public Safety and Security Division’s Badging Office. Contractor must make arrangements with the City to have each Contract Worker proceed to the Badging Office for processing. The Badging Office will not issue a SIDA badge until the Contract Worker passes a fingerprint-based criminal history background check (CHRC) required by federal law (49 C.F.R. § 1542.209) and § 4-22(C) of the Phoenix City Code and passes a security threat assessment as mandated by the TSA through a security directive (49 C.F.R. § 1542.303). The Contract Worker shall comply with all requirements of and furnish all information requested by the Badging Office. Contractor shall pay for all fees associated with SIDA badging process, unless otherwise provided in the Scope of Work. Fees will be assessed according to § 4-22(D) of the Phoenix City Code. Current badging procedures and fees are available for review at: https://www.skyharbor.com/airport-business/security-badging/.
As used in this Section, “restricted area” means the secured area and SIDA area of the Airport. “Secured area” means the part of the Airport in which certain federal security measures are implemented and where airlines enplane and deplane passengers and load baggage. “SIDA area” means the secured area and other areas designated by the Aviation Department, which include air operation areas, ground transportation areas, and the Rental Car Center security doors. “Sterile area” means the part of the Airport that provides passengers access to board aircraft and is controlled by the TSA or the airline by screening of persons and property. See § 4-22 of the Phoenix City Code and Rules 05-01 and 05-09 of the Aviation Department Rules and Regulations for a complete definition of the foregoing terms.
6.27. Risk-Based Background Check Process
The City has established two levels of risk for Contract Worker background checks: standard risk and maximum risk. If the Scope of Work changes, the City may change the level of risk, which may require Contractor conduct additional investigations and incur additional costs in order to process a background check and obtain the required airport security badge. Contract Workers who receive a SIDA badge are exempt from a standard and maximum risk background check.
A STANDARD BACKGROUND CHECK is required for all non-exempt Contract Workers performing work under this Contract. If the Consultant's scope of work includes responsibility or access to City identified critical infrastructure sites, City networks or data, cyber/IT/network assets, digital or cyber assets, workstations, or servers, either through remote or direct access, then a Maximum Risk Background Check may be required. If the City determines that a Maximum Risk Background Check is required, the City will indicate such requirements with the scope of services and the requirement will be re-communicated prior to the start of work for each engagement.
As used in this Section, “background check” means the fact-gathering process described in City of Phoenix A.R. 4.45 that is conducted to obtain information regarding a Contract Worker’s legal Arizona eligibility, criminal history, driving history, certifications, and other matters that may affect the Contract Worker’s ability or fitness to perform work under this Contract.
Before any work is performed under this Contract, Contractor shall provide the City with a list of its Contract Workers.
If any dispute arises related to a background check process or criminal history check information, then Contractor and the affected Contract Worker will resolve the dispute. The City will not get involved in resolving any such dispute.
In making the determination whether information in a background check renders the Contract Worker disqualified, Contractor should be guided by the following principles and guidelines:
Disqualification should not be based solely on a criminal conviction, unless the conviction related to performance under this Contract.
Arrests that did not result in a conviction being entered or charges being filed may not be considered.
Not all criminal convictions or other negative information obtained in a background check will disqualify a Contract Worker from working under this Contract.
Contractor must evaluate the relevance of the information to the work the Contract Worker will perform under this Contract.
Contractor must consider the following factors in determining whether negative background information disqualifies a Contract Worker:
Duties of the position
Time, nature, and number of negative events and convictions
Attempts and extent of rehabilitation efforts
The relation between the duties of the position and the nature of the crime committed
D. The analysis of whether any information in a background check is a potentially disqualifying factor involves looking at the requirements of the Contract, the Scope of Work, where the work will be performed, the need for access to restricted areas, and the type of persons or places the Contract Worker will encounter. Contractor should review the background check results and determine whether the nature of the conviction or crime reported would create a risk to the City based on the Contract’s requirements .
For a Contract Worker requiring a standard risk background check, potentially disqualifying convictions include a record of theft, identity theft, computer fraud or abuse, burglary, arson, crimes against property, violent crimes, or other crimes involving dishonesty, or embezzlement.
For a Contract Worker requiring a maximum risk background check, potentially disqualifying convictions include a record of child molestation, assault, sexual assault, crimes against a person, public indecency, drug offenses, forgery, theft, burglary, arson, crimes against property, violent crimes, crimes for financial gain, identity theft, computer fraud or abuse, and embezzlement.
E. If a background check shows that the disposition of an arrest is unknown, then Contractor must determine the disposition of the arrest.
F. Contractor will obtain a Contract Worker disclosure from each Contract Worker who will perform work under this Contract. Contractor will provide the Contract Worker disclosures to the City upon request. “Contract Worker disclosure” means an affidavit by a Contract Worker disclosing his or her prior criminal record. The Contract Worker disclosure must list all criminal convictions, including the nature of the crime, the date of the conviction, and the location where the crime and conviction occurred. The Contract Worker disclosure also grants to the City the right to review the background check results. (City of Phoenix A.R. 4.45).
G. In a standard risk background check, Contractor must review the results of the background check and decide if a Contract Worker should be disqualified for work under this Contract. Contractor must engage in whatever due diligence is necessary to make necessary to make the decision on whether to disqualify a Contract Worker. After Contractor has made its decisions, a list of names of qualified Contract Workers will be provided to the City.
H. In a maximum risk background check, Contractor must conduct the same review as in a standard risk background check. However, when submitting its list of qualified Contract Workers, Contractor must also submit the results of the background checks to the City for review. After its review, the City will either approve or deny each Contract Worker.
If the City approves a Contract Worker, then the City will notify Contractor of that fact and the Aviation Department will issue the appropriate airport security badge to the Contract Worker.
If the City denies a Contract Worker, then the City will notify Contractor of that fact and Contractor will reevaluate the Contract Worker to determine whether the person should be disqualified. If Contractor believes there are extenuating circumstances that suggest that the Contract Worker should not be disqualified, then Contractor will discuss those circumstances with the City. The City will review the matter and its decision on disqualification is final.
The City may set up a secure folder or drop box for confidential materials related to maximum risk background checks. The City will not keep records related to maximum risk background checks after they are reviewed.
I. If Contractor is a sole proprietor, Contractor must submit to the City a copy of his or her own background check and a background check for all business partners, member, and employees that will work under this Contract and for whom the background check requirements of City of Phoenix A.R. 4.45 apply.
J. Contractor shall determine whether a Contract Worker is disqualified from performing work under this Contract.
6.28. Standard Risk Background Check
A standard risk background check must be conducted for the term of this Contract or five (5) years, whichever is shorter. Contractor shall conduct a standard risk background check on all Contract Workers whose work under this Contract requires:
An airport security badge or key for access to City facilities,
Access to sensitive information, confidential records, personal identifying information, or restricted City information, or
Unescorted access to City facilities during normal and non-business hours.
“Personal identifying information” is defined by City of Phoenix A.R. 4.45.
6.29. Scope of the Standard Risk Background Check
The standard risk background check conducted by Contractor must be based on the real identity and legal name of the Contract Worker and include felony and misdemeanor records checks from any county in the United States, the state of Arizona, and any other jurisdiction where the Contractor Worker has lived at any time in the last seven (7) years.
6.30. Maximum Risk Background Check
A maximum risk background check must be conducted for the term of this Contract or five (5) years, whichever is shorter. Contractor shall conduct a maximum risk background check on all Contract Workers whose work under this Contract requires:
Any responsibility for the receipt of payment of City funds or control of inventories, assets, or records that are at risk of misappropriation,
Unescorted access to City data centers, money rooms, high-valve equipment rooms,
Access to a private residence,
Access to Homeland Defense Bureau-identified critical infrastructure sites or facilities, or
Responsibility or access to City-identified critical infrastructure sites, City networks or data, cyber/IT/network assets, digital or cyber assets, workstations, or servers, by either remote or direct access.
6.31. Scope of the Maximum Risk Background Check
The maximum risk background check conducted by Contractor must include the search criteria conducted under a standard risk background check in addition to a search for all felony and misdemeanor convictions (not including traffic or parking violations), a sex offender check, and a search for all outstanding warrants. Based on the Scope of Work, Contractor shall also conduct a credit check (for cash handling, accounting, and compliance positions only), driving records check (for driving positions only), and fingerprint verification when the Contract Worker is working directly with a child under age 18 or a vulnerable adult or the work under the Contract will take the Contract Worker to a criminal justice information system (CJIS) location.
Maximum risk background checks are valid for the term of this Contract or three (3) years, whichever is shorter.
6.32. Criminal Justice Information System (CJIS) Maximum Risk Background Check
If the Scope of Work of this Contract requires unescorted access to a CJIS location or if Contractor will have access to a CJIS infrastructure or information, then a CJIS maximum risk background check will be conducted, reviewed, and approved by the Phoenix Police Department or the Arizona Department of Public Safety.
6.33. Airport Security Badge Handling Procedures
Contractor will comply with the following airport security badge handling procedures:
Key Access Procedures. If a Contract Worker requires keyed access to enter a City facility, then a separate key will be issued and Contractor must complete a return form and submit it to the City for each key issued.
Stolen or Lost Badges or Keys. Contractor shall immediately report any lost or stolen airport security badge or key to the City. A new airport security badge application or key issue form must be completed and submitted along with payment of the applicable fee prior to issuance of a new airport security badge or key.
Return of Badges or Keys. All airport security badges and keys are the property of the City and must be returned to the Badging Office within one (1) business day after the Contract Worker’s access to a City facility is no longer required under this Contract. Contractor shall collect a Contract Worker’s airport security badge and all keys (1) when the Contract Worker’s employment is terminated, (2) when the Contract Worker’s services are no longer required at a City facility, or (3) when this Contract terminates, is cancelled, or expires, whichever occurs first.
Employee Identification and Access. Contract Workers must have an airport security badge and some form of verifiable company identification in their possession at all times while working under this Contract, unless otherwise provided in the Scope of Work. Contract Workers are strictly prohibited from entering any area of the Airport that is not authorized by the airport security badge or key issued to them by the Badging Office. The Aviation Department will determine who will have access to the Airport. Contract Workers access authority is only valid during their scheduled hours. Contractor shall provide the City with updates and changes in personnel as they occur.
Badge Fees. Contractor shall pay the airport security badge fees set forth in § 4-22(D) of the Phoenix City Code.
6.34. Contractor's Breach of Aviation Security Procedures
Contractor agrees that the access control, airport security badge, and key requirements in this Section are necessary to preserve and protect public health, safety, and welfare. Therefore, Contractor shall be deemed in immediate breach of this Section upon the occurrence of any of the following:
A Contract Worker gains access to a City facility or a restricted or secured area of the Airport without the proper airport security badge or key
A Contract Worker uses another person’s airport security badge or key to gain or attempt to gain access to a City facility or a restricted or secured area of the Airport
A Contract Worker begins work under this Contract without passing the appropriate Background Screening and being issued the proper airport security badge or key
A Contract Worker or Contractor submits false, incomplete, or misleading Background Screening information or submits any false, incomplete, or misleading information in an attempt to improperly obtain an airport security badge or key
Contractor fails to collect and timely return a Contract Worker’s airport security badge or key to the City within three days of the (1) date the Contract Worker’s employment terminates, (2) the date the Contract Worker is assignment to another City facility, or (3) when this Contract terminates, is cancelled, or expires, whichever occurs first
6.35. Liquidated Damages and Remedies for Breach of Aviation Security Procedures
In addition to any other remedy available to the City at law or in equity, including the right to terminate this Contract, Contractor shall be liable for and shall pay to the City a stipulated damage in the amount of $1,000.00 for each breach of Aviation Security Procedures and for each time a Contract Worker entered a restricted or secured area of the Airport without proper authority. Contractor agrees that the stipulated damage amount is not a penalty, but is a reasonable estimate of the actual harm to the City caused by a breach and that the harm was very difficult to estimate at the time this Contract was entered into.
6.36. Contractor Certification
Contractor certifies to the City that Contractor has read the foregoing Background Screening requirements and that all Background Screening information Contractor furnished to the City is accurate, complete, and current. Contractor further certifies to the City that Contractor has satisfied all Background Screening requirements and verified the legal worker status of each Contract Worker as required under this Section.
6.37. Confidentiality
“Confidential Information” means all non-public, sensitive, or proprietary information disclosed or made available by City to Contractor or its affiliates, employees, contractors, partners, or agents (collectively “Recipient”), whether disclosed before or after the Effective Date, whether disclosed orally, in writing, or via permitted electronic access, and whether or not marked, designated, or otherwise identified as confidential. Confidential Information includes, but is not limited to: user contents, electronic data, meta data, employment data, network configurations, information security practices, strategic plans, financial accounts, protected personal data, protected health information, protected criminal justice information, and any other information that by the nature and circumstance of the disclosure should be deemed confidential. Confidential Information does not include this document or information that: (a) is now or subsequently becomes generally available to the public through no wrongful act or omission of Recipient; (b) Recipient can demonstrate by its written records to lawfully have had in its possession prior to receiving such information from the City; (c) Recipient can demonstrate by its written records to have been independently developed by Recipient without direct or indirect use of any Confidential Information; (d) Recipient lawfully obtains from a third party who has the right to transfer or disclose it; or (e) the City has approved in writing for disclosure.
Recipient shall: (a) protect and safeguard Confidential Information with at least the same degree of care as Recipient would protect its own Confidential Information, but in no event with less than a commercially reasonable degree of care, such as ensuring data is encrypted in transit and at rest and maintaining appropriate technical and organizational measures in performing the services under the Agreement; (b) not use Confidential Information, or permit it to be accessed or used, for any purpose other than in accordance with the Agreement; (c) not use Confidential Information, or permit it to be accessed or used, in any manner that would constitute a violation of law, including without limitation export control and data privacy laws; and (d) not disclose Confidential Information except to the minimum number of recipients who have a need to know and who have been informed of and agree to abide by confidentiality obligations that are no less restrictive than the terms of this Agreement. If Recipient is required by law or court order to disclose any Confidential Information, Recipient will first give written notice to the City and provide the City with a meaningful opportunity to seek a protective order or limit disclosure.
Upon the City’s written request or expiration of this Agreement, whichever is earlier, Recipient shall, at no additional costs to the City, promptly return or destroy all Confidential Information belonging to the City that Recipient has in its possession or control. After return or destruction of the Confidential Information, Recipient shall certify in writing as to its compliance with this paragraph.
If applicable, Contractor agrees to comply with all City information technology policies and security standards, as may be updated from time to time, when accessing City networks and computerized systems whether onsite or remotely.
A violation of this Section shall be deemed to cause irreparable harm that justifies injunctive relief in court. A violation of this Section may at the City’s discretion result in immediate termination of the Agreement without notice. The obligations of Contractor under this Section shall survive the termination of the Agreement.
6.38. Sensitive Security Information (SSI)
Contractor shall comply with the requirements 49 C.F.R. Parts 15 and 1520, prohibiting the unauthorized release of Sensitive Security Documents, which includes photographs and/or videos taken of secured areas of the Airport. Upon the receipt or creation of any SSI documents, including photographs and/or videos taken of secured areas of the Airport, Contractor shall be required to complete and submit the attached City of Phoenix Aviation Department Sensitive Security Information Acknowledgment Form, marked Exhibit B and incorporated herein by this reference. Information on the maintenance, safeguarding and disclosure of SSI is available at https://www.tsa.gov/sites/default/files/ssi-best-practices-guide-for-non-dhs-employees.pdf.
6.39. Data Protection
The parties agree this Section shall apply to the City’s Confidential Information and all categories of legally protected personally identifiable information (collectively “City Data”) that Contractor processes when providing products or services to the City. “Personally identifiable information” is defined as in the Federal Privacy Council’s Glossary available at: https://www.fpc.gov/resources/glossary/.
As between the parties, the City is the data controller and owner of City Data and Contractor is a data processor. In this Section, the term “process,” “processing,” or its other variants shall mean: an operation or set of operations which is performed on City Data, whether or not by automated means, including without limitation: collection, recording, copying, analyzing, caching, organizing, structuring, storage, adaptation, alteration, retrieval, transmission, dissemination, alignment, combination, restriction, erasure, or destruction.
When Contractor processes City Data, Contractor shall, at no additional cost to the City:
process City Data only within the United States, only for the intended purpose of providing the products or services to the City, and not for Contractor’s own purposes, including product research, product development, marketing, or commercial data mining, even if the City Data has been aggregated, anonymized, or pseudonymized;
not input City Data into an artificial intelligence tool or prompt, unless expressly permitted by the City;
implement and maintain appropriate technical and organizational measures to protect City Data against unauthorized or unlawful processing and against accidental loss, destruction, damage, theft, alteration or disclosure, including at a minimum, and as applicable, those measures specified by the National Institute of Standards and Technology (NIST) SP800-53; NIST Privacy Framework; NIST AI Risk Management Framework; Arizona Revised Statutes (A.R.S.) § 18-552 (Notification of security system breaches); A.R.S. § 44-7601 (Discarding and disposing of records containing personal identifying information); Health Information Technology for Economic and Clinical Health (HITECH) Act; Payment Card Industry Data Security Standards; and good industry practice; (When considering what measures are appropriate and in line with good industry practice, Contractor shall keep abreast of current regulatory trends in data security and the state of technological development to ensure a level of security appropriate to the nature of the data to be protected and the harm that might result from such unauthorized or unlawful processing or accidental loss, destruction, damage, theft, alteration or disclosure. At minimum, Contractor will timely remediate any vulnerabilities found within its network that are rated medium or more critical by the Common Vulnerability Scoring System (CVSS); however, Contractor must remediate vulnerabilities that are rated critical within 14 days and vulnerabilities that are rated high within 30 days. If requested by the City, Contractor shall promptly provide a written description of the technical and organizational methods it employs for processing City Data).
as applicable, implement and maintain appropriate policies and procedures to manage payment card service providers with whom Contractor shares sensitive financial information or cardholder data; and provide the City with a Qualified Security Assessor Attestation of Compliance for Payment Card Industry Data Security Standards on an annual basis, but no later than within 30 days of attestation report completion;
not subcontract the processing of City Data to any third party (including affiliates, group companies or sub-contractors) without providing notice to the City and allowing the City a reasonable opportunity to object;
ensure that any permitted sub-processor appointed by Contractor abide by data protection obligations that are no less restrictive than the terms of this Section; and remain fully liable to the City for the processing of City Data conducted by a sub-processor appointed by Contractor;
take reasonable steps to ensure the competence and reliability of Contractor’s personnel or sub-processor who have access to the City Data, including verifications and background checks appropriate to the security level required for such data access;
maintain written records of all information reasonably necessary to demonstrate Contractor’s compliance with this Agreement and applicable laws;
allow the City or its authorized agents to conduct annual audit inspection for compliance with this Section; provided however, the City may at its sole discretion accept a qualified and industry recognized independent third-party assessment report or certification (such as SSAE 18 SOC 2 Type 2 or ISO/IEC 27001) provided by Contractor at no cost to the City in lieu of the audit inspection rights of this Section.
If Contractor becomes aware of a security incident as defined by A.R.S. § 18-551 affecting City Data in the custody or control of Contractor or its sub-processor (each an “Incident”), Contractor shall notify the Airport Security Coordinator at 602-273-3388 and the City at SOC@phoenix.gov without undue delay within 24 hours; and:
provide the City with a detailed description of the Incident, the type of data that was the subject of the Incident, and the identity of each affected person as soon as such information can be collected or otherwise becomes available;
act immediately, at Contractor’s own expense, to investigate the Incident and to identify, prevent, and mitigate the effects of the Incident and to carry out any recovery or other action necessary to remedy the Incident;
cooperate with the City in investigating the occurrence, including making available all relevant records, logs, files, data reporting, and other materials required to comply with applicable laws or as otherwise required by the City; and
not directly contact any individuals who may be impacted by the Incident or release or publish any filing, communication, notice, press release, or report concerning the Incident without the City’s prior written approval (except where required to do so by applicable laws).
In addition to, and not in lieu of, all other rights and remedies available to the City, Contractor will defend, indemnify, and hold the City harmless against all losses, claims, costs, attorneys’ fees, damages or proceedings arising out of Contractor’s breach of this Section. A violation of this Section shall be deemed to cause irreparable harm that justifies injunctive relief in court. A violation of this Section may at the City’s discretion result in immediate termination of the Agreement without notice. The obligations of Contractor under this Section shall survive the termination of the Agreement.
6.40. Security Inquiries
Contractor acknowledges that all of the employees that it provides pursuant to this Contract shall, at Contractor’s expense, be subject to background and security checks and screening at the request of the City. Contractor shall perform all such security inquiries and shall make the results available to the City for all employees considered for performing work (including supervision and oversight) under this Contract. City may make further security inquiries. Whether or not further security inquiries are made by the City, City may, at its sole, absolute and unfettered discretion, accept or reject any or all of the employees proposed by the Contractor for performing work under this Contract. Employees rejected by the City for performing services under this Contract may still be engaged by Contractor for other work not involving the City. An employee rejected for work under this Contract shall not be proposed to perform work under other City contracts or engagements without the City’s prior approval. The City, in its sole discretion, reserves the right, but not the obligation to:
require an employee/prospective employee of the Contractor to provide fingerprints and execute such other documentation as may be necessary to obtain criminal justice information pursuant to A.R.S. 41-1750 (G) (4);
act on newly acquired information whether or not such information should have been previously discovered;
unilaterally change its standards and criteria relative to the acceptability of Contractor’s employees and/or prospective employees; and
object, at any time and for any reason, to an employee of Contractor performing work (including supervision and oversight) under this Agreement. Contractor will bear the costs of all inquiries requested by the City.
6.41. Offshore Work Prohibited
In performing the Services provided pursuant to the Agreement, Contractor will only utilize personnel and labor resources located within the defined territories of the United States. This provision applies to work performed by subcontractors at all tiers.
6.42. Cybersecurity
Regardless of whether the Contractor processes PII or not, the City requires the Contractor to have a Vulnerability Remediation program in place in order to remediate such vulnerabilities in the system. Vulnerabilities within the IT or OT (operational technology) components of the system that may utilize Windows or other operating systems, to include specialty software or components, can pose a significant cybersecurity risk. At minimum, Contractor will remediate any vulnerabilities found within its hardware or software that are rated medium by the Common Vulnerability Scoring System (CVSS) in a timely manner; however, Contractor must remediate vulnerabilities that are rated critical within 14 days and vulnerabilities that are rated high within 30 days.
In addition to, and not in lieu of, all other rights and remedies available to the City, Contractor will defend, indemnify, and hold the City harmless against all losses, claims, costs, attorneys’ fees, damages or proceedings arising out of Contractor’s breach of this Section (Data Protection). Contractor’s obligations pursuant to this Section (Data Protection) shall not be subject to any limits of liability or exclusions as may be stated elsewhere in the Agreement.
A violation of this Section shall be deemed to cause irreparable harm that justifies injunctive relief in court. A violation of this Section may at the City’s discretion result in immediate termination of this Agreement without notice. The obligations of Contractor under this Section shall survive the termination of this Agreement.
6.43. Intellectual Property Rights
The Contractor hereby irrevocably transfers, conveys, and assigns to the City all right, title, and interest (including any and all copyrights) in any software and other technology assets created pursuant to or as a result of this Agreement (collectively, the “Work Product”). The City shall have the exclusive right to apply for or register any copyrights and other proprietary protections with respect to the Work Product. The Contractor shall execute such documents, render such assistance, and take such other action as the City may reasonably request, at the City’s reasonable expense, to apply for, register, perfect, confirm, and protect the City’s foregoing ownership interests and copyright and other proprietary protections. To the extent that the foregoing transfer does not provide the City with full ownership, right, title, and interest in and to the Work Product, the Contractor hereby grants the City a perpetual, irrevocable, fully paid, royalty-free, worldwide license to reproduce, create derivative works from, distribute, publicly display, publicly perform, and use the Work Product, with the right to transfer and/or sublicense each and every such right. The rights granted in this section will survive any termination or expiration of this Agreement.
7. Defense and Indemnification
7.1. Standard General Defense and Indemnification
Contractor (“Indemnitor”) must defend, indemnify, and hold harmless the City of Phoenix and its officers, officials (elected or appointed), agents, and employees (“Indemnitee”) from and against any and all claims, actions, liabilities, damages, losses or expenses (including but not limited to court costs, attorney fees, expert fees, and costs of claim processing, investigation and litigation) of any nature or kind whatsoever (“Losses”) caused, or alleged to be caused, in whole or in part, by the wrongful, negligent or willful acts, or errors or omissions of Indemnitor or any of its owners, officers, directors, members, managers, agents, employees or subcontractors (“Indemnitor’s Agents”) arising out of or in connection with this Contract. This defense and indemnity obligation includes holding Indemnitee harmless for any Losses arising out of or recovered under any state’s Workers’ Compensation Law or arising out of the failure of Indemnitor or Indemnitor’s Agents to conform to any federal, state or local law, statute, ordinance, rule, regulation or court decree. Indemnitor’s duty to defend Indemnitee accrues immediately at the time a claim is threatened, or a claim is made against Indemnitee, whichever is first. Indemnitor’s duty to defend exists regardless of whether Indemnitor is ultimately found liable. Indemnitor must indemnify Indemnitee from and against any and all Losses, except where it is proven that those Losses are solely a result of Indemnitee’s own negligent or willful acts or omissions. Indemnitor will be responsible for primary loss investigation, defense and judgment costs where this indemnification applies. In consideration of the award of this Contract, Indemnitor waives all rights of subrogation against Indemnitee for losses arising from the work performed by Indemnitor or Indemnitor’s Agents for the City of Phoenix. The obligations of Indemnitor under this provision survive the termination or expiration of this Contract.
7.2. Technology Software and Hardware Contracts
INDEMNIFICATION – PATENT, COPYRIGHT AND TRADEMARK
In addition to any other indemnification required by this Agreement, Contractor agrees to defend, at its own expense, and to indemnify and hold harmless the City and its officers, agents, and employees from and against all judgments, claims, damages, suits, liabilities, settlements, costs and demands, including reasonable attorneys’ fees, suffered or incurred by the City as a result of any claim that the Technology Assets infringe the patents, copyrights, or other intellectual property rights of third parties, provided that Contractor is notified in writing of such claim. The City will reasonably cooperate with Contractor, at Contractor’s expense, to facilitate the settlement or defense of such claim. Without limiting in any way the Contractor obligations set forth herein, if, as a result of any claim of infringement with respect to the Technology Assets, the City is enjoined from using the Technology Assets, or if Contractor reasonably believes that the Technology Assets are likely to become the subject of a claim of infringement, Contractor may, at Contractor’s option and expense, (1) procure the right for the City to continue to use the Technology Assets, or (2) replace or modify the Technology Assets so as to make them non-infringing and of equal or superior functionality and capability for the purpose(s) for which the Technology Assets were provided.
The Contractor’s obligation to indemnify, defend, and hold harmless the City pursuant to this subsection shall be reduced to the extent the applicable infringement is caused or alleged to be caused by the alteration or modification of the Technology Assets by the City (including its employees and contractors other than the Contractor and its subcontractors) other than in connection with the ordinary or expected use of the Technology Assets.
8. Insurance Requirements
8.1. Contractor's Insurance
Contractors and subcontractors must procure insurance against claims that may arise from or relate to performance of the work hereunder by Contractor and its agents, representatives, employees and subcontractors. Contractor and subcontractors must maintain that insurance until all their obligations have been discharged, including any warranty periods under this Contract.
The City in no way warrants that the limits stated in this section are sufficient to protect the Contractor from liabilities that might arise out of the performance of the work under this Contract by the Contractor, its agents, representatives, employees or subcontractors and Contractor may purchase additional insurance as they determine necessary.
8.2. Scope and Limits of Insurance
Contractor must provide coverage with limits of liability not less than those stated below. An excess liability policy or umbrella liability policy may be used to meet the liability limits provided that (1) the coverage is written on a “following form” basis, and (2) all terms under each line of coverage below are met.
8.3. Commercial General Liability – Occurrence Form
General Aggregate $2,000,000
Products – Completed Operations Aggregate $1,000,000
Personal and Advertising Injury $1,000,000
Each Occurrence $1,000,000
The policy must name the City of Phoenix as an additional insured with respect to liability for bodily injury, property damage and personal and advertising injury with respect to premises, ongoing operations, products and completed operations and liability assumed under an insured contract arising out of the activities performed by, or on behalf of the Contractor related to this Contract.
There shall be no endorsement or modification which limits the scope of coverage or the policy limits available to the City of Phoenix as an additional insured.
City of Phoenix is an additional insured to the full limits of liability purchased by the Contractor.
The Contractor’s insurance coverage must be primary and non-contributory with respect to any insurance or self-insurance carried by the City.
8.4. Worker’s Compensation and Employers’ Liability
Workers’ Compensation Statutory
Employers’ Liability:
Each Accident $1,000,000
Disease – Each Employee $1,000,000
Disease – Policy Limit $1,000,000
Policy must contain a waiver of subrogation in favor of the City of Phoenix. “Transfer of rights of recovery against others to us” may be used in place of “waiver of subrogation”.
This requirement does not apply when a contractor or subcontractor is exempt under A.R.S. §23-902(E), AND when such contractor or subcontractor executes the appropriate sole proprietor waiver form. To forego application of this requirement, Contractor must submit to the City a valid copy of the form on behalf of themselves and/or applicable subcontractors.
8.5. Technology Errors and Omissions Liability
Each Claim $1,000,000
Annual Aggregate $1,000,000
The policy must cover errors and omissions or negligent acts in the delivery of products, services, and/or licensed programs for those services as defined in the Scope of Services of this Contract.
Contractor warrants that any retroactive date under the policy must precede the effective date of this Contract; and that either continuous coverage will be maintained, or an extended reporting period will be exercised for a period of two (2) years beginning at the time work under this Contract is completed.
8.6. Network Security and Privacy Liability (required if Contractor has access to personal or confidential data)
Each Claim $1,000,000
Annual Aggregate $1,000,000
Policy must cover but not be limited to (1) coverage for third party claims and losses with respect to network risk and invasion of privacy (2) crisis management and third-party identity theft response costs and (3) cyber extortion.
Contractor warrants that any retroactive date under the policy must precede the effective date of this Contract; and that either continuous coverage will be maintained, or an extended reporting period will be exercised for a period of two (2) years beginning at the time work under this Contract is completed.
8.7. Notice of Cancellation
For each insurance policy required by the insurance provisions of this Contract, the Contractor must provide to the City, within 5 business days of receipt, a notice if a policy is suspended, voided or cancelled for any reason. Such notice must be mailed, emailed, or hand delivered to n/a.
8.8. Acceptability of Insurers
Insurance is to be placed with insurers duly licensed or authorized to do business in the state of Arizona and with an “A.M. Best” rating of B+: VI or a Standard & Poor’s Rating (if rated) of not less than BBB. The City in no way warrants that the required minimum insurer rating is sufficient to protect the Contractor from potential insurer insolvency.
8.9. Verification of Coverage
Contractor must furnish the City with certificates of insurance (ACORD form or equivalent approved by the City) as required by this Contract. The certificates for each insurance policy are to be signed by a person authorized by that insurer to bind coverage on its behalf.
All certificates and any required endorsements are to be received and approved by the City before work commences. Each insurance policy required by this Contract must be in effect at or prior to commencement of work under this Contract and remain in effect for the duration of the project. Failure to maintain the insurance policies as required by this Contract or to provide evidence of renewal is a material breach of contract.
Contractors shall furnish the City with original certificates and amendatory endorsements or copies of the applicable policy language affecting coverage required by this clause. All certificates and endorsements are to be received and approved by the city before work commences. However, failure to obtain the required documents prior to the work beginning shall not waive the Contractor’s obligation to provide them. The City reserves the right to review complete certified copies of all required insurance policies, including endorsements required by these specifications, at any time. In the event of a claim or coverage dispute, the City reserves the right to require complete certified copies of all required insurance policies, including endorsements required by these specifications.
Where the City is named as an additional insured, coverage must be as broad as CG 20 10 11 85 or a combination of CG 20 10 or CG 20 26 or CG 20 23 22, 10 01 Editions or equivalent.
All certificates required by this Contract must be sent directly to the name and address listed below. The City project/contract number and project description must be noted on the certificate of insurance. The City reserves the right to review complete copies of all insurance policies required by this Contract at any time. DO NOT SEND CERTIFICATES OF INSURANCE TO THE CITY’S RISK MANAGEMENT DIVISION.
The initial certificates required by this Contract shall be sent directly to:
City of Phoenix Aviation Department
Contract & Services Division
2485 E. Buckeye Rd.
Phoenix, AZ 85034
michael.soto@phoenix.gov
All subsequent and renewal certificates of insurance shall be sent directly to:
City of Phoenix Aviation Department
c/o EXIGIS Insurance Compliance Services
PO Box 4668 - ecm #35050
New York, NY 10163-4668
Email: inbox@cop.complianz.com
8.10. Subcontractors
Contractor’s certificates shall include all subcontractors as additional insureds under its policies OR Contractor shall be responsible for ensuring and verifying that all subcontractors have valid and collectable insurance. At any time throughout the life of the contract, the City of Phoenix reserves the right to require proof from the Contractor that its subcontractors have insurance coverage. All subcontractors providing services included under this Contract’s Scope of Services are subject to the insurance coverages identified above and must include the City of Phoenix as an additional insured. In certain circumstances, the Contractor may, on behalf of its subcontractors, waive a specific type of coverage or limit of liability where appropriate to the type of work being performed under the subcontract. Contractor assumes liability for all subcontractors with respect to this Contract.
8.11. Approval
Any modification or variation from the insurance coverages and conditions in this Contract must be documented by an executed contract amendment.
9. Submittals
9.1. Submission of Offer
Please do not lock the files with password protection so that the City may digitally incorporate the successful offer into the awarded contract.
Please submit offers electronically through the City's Procurement Portal. This Offer will remain in effect for a period of 180 calendar days from the opening date, and is irrevocable unless it is in the City’s best interest to release offer(s).
9.2. Additional Quantities
10. Vendor Questionnaire
Instructions for Downloading Required Documents
Offerors must download all documents required to be completed and/or signed as part of the Vendor Questionnaire directly from the OpenGov Procurement Portal. Do not use the links in the downloaded Solicitation document, as those links may not function properly.
1. PAYMENT TERMS & OPTIONS: Vendors must choose an option, if a box is not checked, the City will default to 0% - net 45 days:*
Contractor offers a prompt payment discount of either ______% - 30 days or 0% – 45 days - to apply after receipt of invoice or final acceptance of the products (invoice approval), whichever date is later, starts the 30 days. If no prompt payment discount is offered, the default is 0%, net 45 days; effective after receipt of invoice or final acceptance of the products, whichever is later. Payment terms offering a discount will not be considered in the price evaluation of your offer.
Contractor may be paid immediately upon invoice approval, if enrollment is made to the Single Use Account (SUA) Program, administered by the City’s servicing bank (“Bank”). By checking this box, the vendor accepts transaction costs charged by their merchant bank and agrees not to transfer to the City those extra charges. The City will not pay an increase in our services for the SUA charges; if an audit uncovers an upcharge for the SUA charges the vendor will owe the City all costs. The vendor may opt-out of the SUA program once, but then may not rejoin during the same contract term. For more information about the SUA program or to enroll, send email to mailbox.sua@phoenix.gov.
*Response required
2. Prompt Payment Discount
______% - 30 days or 0% – 45 days
If none is specified, the City will default to 0% - net 45 days.
3. References*
including information about Offeror's history.
References.pdf
*Response required
4. Certification Regarding Debarment, Suspension, and Other Ineligibility and Voluntary Exclusion*
Please download the below documents, complete, sign, and upload.
Failure to submit a signed Certification Regarding Debarment, Suspension, and Other Ineligibility and Voluntary Exclusion will deem your offer non-responsive and result in disqualification from further consideration.
Certification_Regarding_Debarment,_Suspension,_and_Other_Ineligibility_and_Voluntary_Exclusion.pdf
*Response required
5. Heat Safety Compliance*
Please download the below documents, complete, sign, and upload.
Failure to submit a signed Heat Safety Compliance will deem your offer non-responsive and result in disqualification from further consideration.
Heat_Safety_Compliance.pdf
*Response required
6. Data Privacy Questionnaire *
Per Section 4 Minimum Qualifications, Paragraph 5 - Additional Evaluation Factors, the Data Privacy Questionnaire must be completed and uploaded.
Data_Privacy_Questionnaire.pdf
*Response required
7. Has your organization implemented a privacy program that covers privacy risk across all operations, services, projects, programs and systems that process personal data?*
If marked "No", please explain why.
Yes
No
*Response required
8. Does your organization have an incident/breach escalation and response plan? *
If marked "No", please explain why.
Yes
No
*Response required
9. Has your organization experienced any reportable privacy or security breaches within the last 2 years?*
If marked "Yes", please provide details (do not include any sensitive information).
Yes
No
*Response required
10. Qualifications and Experience *
For all groups, the Offeror must provide a detailed description (Not to exceed 5 pages total) of their relevant experience or their subcontractor's experience for each group.
*Response required
11. Statement of Work *
Offeror must provide a detailed description (Not to exceed 20 pages total) to include:
List of Technology Consulting Services identified in Section V - Scope of Work, Paragraph 3 - Technology Consulting Services, for which the Offeror is qualified to provide.
Detailed description of previous Technology Consulting Services at other large hub airports.
*Response required
12. Sensitive Security Information Acknowledgement Form*
Please download the below documents, complete, sign, and upload.
Failure to submit a signed Sensitive Security Information Acknowledgement Form may deem your offer non-responsive and result in disqualification from further consideration.
Aviation_Only_-_Sensitive_Security_Information_Acknowledgement_Form.docx
*Response required
13. Offer *
Please download the below documents, complete, sign, and upload.
Failure to submit a signed Offer Page will deem your offer non-responsive and result in disqualification from further consideration.
Submittals_-_Offer_Page.pdf
*Response required
14. Conflict of Interest and Transparency*
Please download the below documents, complete, sign, and upload.
Failure to submit a signed Conflict of Interest and Transparency form will deem your offer non-responsive and result in disqualification from further consideration.
Conflict_of_Interest_and_Transparency.pdf
*Response required
15. Please confirm that all required documents have been duly signed and uploaded, including but not limited to: the Offer Page, Conflict of Interest and Transparency, and any other mandatory forms requiring signature.*
Failure to submit all required signed documents may deem our offer non-responsive and result in disqualification from further consideration.
Please confirm
*Response required
11. Attachments
A - Supplemental-Terms-And-Conditions-To-All-Airport-Contracts Rev 4-29-26
B - Sensitive Security Information Acknowledgement Form
C - Acceptance of Offer Form 2026
City of PhoenixIssuing agency·Phoenix, AZ·via the City of Phoenix OpenGov procurement portal