- Due Text
- Wednesday, September 2, 2026 11:59pm
- Posted At
- Wed, Jul 15, 2026 9:51 AM
- Documents
- Operations_Control_Center_&_Data_Collection_Services.pdf, A - Exhibit A - Incumbent OCC Job Descriptions & Wages, B - Exhibit B - OCC Site Plan, C - Exhibit C - OCC Warm Site Plan, D - Exhibit - D - Facility Incident-Repair Request Procedure 04.22.26, E - Exhibit E - Technical Requirements, F - Exhibit F - A.R. 4.45 Contract Worker Background Checks, G - Exhibit G - Security Access & Control, H - Exhibit H - A.R. 2.324 Substance Abuse Policy
- Numeric Id
- 275740
- Description
- The City of Phoenix invites sealed offers for operations control center & data collection 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 July 1, 2027.
The term of this Agreement will be for five (5) years, beginning on the Commencement Date, with one two-year option to extend, which may be exercised by the City in its sole discretion.
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.
Background
The Operations Control Center (OCC) monitors and manages Phoenix’s fixed‑route transit fleet using the CAD/AVL system. By tracking buses in real time, the OCC identifies delays early and works with operators and transit yards to resolve issues before they affect service. This coordination helps maintain efficient bus deployment, schedule adherence, and reliable, customer‑focused transit service across the city and region.
Timeline
Solicitation Issue Date:
July 15, 2026
Pre-Offer Conference (Non-Mandatory):
July 22, 2026, 10:00am
Microsoft Teams meeting
Click the link to join -->
https://teams.microsoft.com/meet/25815019551229?p=3TFSgmrKJmP9TJiwc8
Meeting ID: 258 150 195 512 29
Passcode: si6Qk3JW
Site Visit (Non-Mandatory):
July 23, 2026, 10:00am
Please meet in the lobby of the City of Phoenix Public Transit Building at the meeting time listed above.
City of Phoenix
Public Transit Building
302 N 1st Ave
Phoenix, AZ 85003
Written Inquiries Due Date:
July 29, 2026, 11:59pm
Offer Due Date:
September 2, 2026, 11:59pm
- Document Text
- 1. Introduction
1.1. Contact Information
Ben Arballo
Public Transit
Email: benjamin.arballo@phoenix.gov
Phone: (602) 262-4857
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 (Ben Arballo) at (602) 262-4857/Voice or 711/TTY, or benjamin.arballo@phoenix.gov.
Solicitation Issue Date: July 15, 2026
Pre-Offer Conference (Non-Mandatory): July 22, 2026, 10:00am
Microsoft Teams meeting
Click the link to join -->
https://teams.microsoft.com/meet/25815019551229?p=3TFSgmrKJmP9TJiwc8
Meeting ID: 258 150 195 512 29
Passcode: si6Qk3JW
Site Visit (Non-Mandatory): July 23, 2026, 10:00am
Please meet in the lobby of the City of Phoenix Public Transit Building at the meeting time listed above.
City of Phoenix
Public Transit Building
302 N 1st Ave
Phoenix, AZ 85003
Written Inquiries Due Date: July 29, 2026, 11:59pm
Offer Due Date: September 2, 2026, 11:59pm
2. Instructions
2.1. Description – Statement of Need
The City of Phoenix invites sealed offers for operations control center & data collection 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 July 1, 2027.
The term of this Agreement will be for five (5) years, beginning on the Commencement Date, with one two-year option to extend, which may be exercised by the City in its sole discretion.
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 City 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. Fixed Offer Price Period
All offers shall be firm and fixed for a period of 365 calendar days from the solicitation opening date.
2.4. 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/275740. 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, Public Transit Department, Procurement and Contracts Section, 302 N. 1st Avenue, 9th Floor, Phoenix, AZ 85003. 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.5. 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.6. Inquiries
All questions that arise relating to this solicitation should be directed via City’s OpenGov 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 date of distribution of this solicitation until after 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 OpenGov Procurement Portal.
2.7. 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.8. 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.
2.9. 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.10. 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.11. Submission of Offer
Offers must be in possession of the Department on or prior to the exact time and date indicated in the Schedule of Events. Late offers will not be considered. The prevailing clock will be the City 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/275740. 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 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.12. 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.13. Offer Results
Offers will be opened in OpenGov on the offer due date and time indicated in the Schedule of Events, at which time the name of each Offeror, and the prices may be read. Offers and other information received in response to the solicitation will be shown only to authorized City personnel having a legitimate interest in them or persons assisting the City in the evaluation. 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 a preliminary offer tabulation on the City's Procurement Portal: https://procurement.opengov.com/portal/phoenix/projects/275740 within five business days of the offer opening. The City will post the information on the preliminary tabulation as it was read during the offer opening. The City makes no guarantee as to the accuracy of any information on the preliminary tabulation. Once the City has evaluated the offers, the City will post an award recommendation on the City's Procurement Portal. By signing and submitting its Offer, each Offeror agrees that this posting of the award recommendation to the City's Procurement Portal effectively serves as the Offeror’s receipt of that notice of award recommendation. The City has no obligation to provide any further notification to unsuccessful Offerors.
2.14. Pre-Award Qualifications
Offeror must have been in operation a minimum of five (5) years. The Offeror’s normal business activity during the past five (5) years will have been for providing the goods or services in this solicitation. This information must be provided in Vendor Questionnaire section, under Years in Business and References form of this solicitation.
2.15. Certificates of Insurance
Upon notification of a recommended award, the Offeror will have 14 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 Chief Procurement Officer 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. Site Inspection
A one-time walk-through site inspection tour will be conducted at the date and time indicated in the Schedule of Events. Submission of an offer will be prima facie evidence that the Offeror did, in fact, make a site inspection and is aware of all conditions affecting performance and offer prices.
2.23. 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.24. Determining Responsiveness and Responsibility
Offers will be reviewed for documentation of minimum qualifications, completeness, and compliance with the Solicitation requirements. The City reserves sole discretion to determine responsiveness and responsibility.
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.
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.
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, and facilities for conducting the work to be performed.
The Procurement Officer will review each Offer to determine if the Offeror is responsible. 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.
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.
2.25. Clarifications
The City may request written clarifications for such purposes as information gathering or eliminating minor informalities in offers. Clarifications shall not otherwise afford the Offerors the opportunity to alter or change their offers.
2.26. Equal Low Offer
Contract award will be made by putting the names of the tied vendors in a cup for a blind drawing limited to those bidders with tied offers. If time permits, the offerors involved will be given an opportunity to attend the drawing. The drawing will be witnessed by at least three persons, and the contract file will contain the names and addresses of the witnesses.
2.27. Evaluation of Competitive Sealed Offers
The City will use its discretion in applying the following processes to this solicitation. Any ties in scoring will be resolved with a best and final price request and the lowest price will prevail.
2.28. Detailed Evaluation of Offers and Determination of Competitive Range
The City will appoint an Evaluation Panel, which may consist of City staff, staff from other City departments or transit agencies, and other persons. The City may also appoint a Technical Advisory Team to provide technical assistance to the Evaluation Panel. The Technical Advisory Team may consist of City staff, staff from other City departments or transit agencies, and other persons. The Technical Advisory Team will review the technical portion of each offer for compliance with the RFP specifications. The Procurement Officer will chair the Evaluation Panel, serving in a non-voting capacity.
During deliberations, the Evaluation Panel will reach a consensus score for each evaluation criterion except price. The Procurement Officer will score the price, which will be added to the overall consensus score. The overall consensus scores will determine the Offerors’ rankings and which Offers are within the Competitive Range, when appropriate.
2.29. Offers Not Within the Competitive Range
The City may notify Offerors of Offers that the City determined are not in the Competitive Range.
2.30. Discussions with Offerors in the Competitive Range
The City will notify each Offeror whose Offer is in the Competitive Range or made the ‘short list’ and provide in writing any questions or requests for clarification to the Offeror. Each Offeror so notified may be interviewed by the City and asked to discuss answers to written or oral questions or provide clarifications to any facet of its Offer. The Offerors in the competitive range may be required to provide a demonstration of their product.
Demonstrations - Offerors in the competitive range may be invited to construct a hands-on sample or presentation of their solution at the City of Phoenix. In addition, each finalist may prepare and deliver a presentation of their proposed solution based on the script developed by the evaluation panel. The City may also require a hands-on lab demonstration designed specifically for the evaluation panel. The results of the surveys will be tabulated and delivered to the evaluation team for the final review and solution selection session(s).
If an Offer in the Competitive Range contains conditions, exceptions, reservations or understandings to or about any Contract or Solicitation Scope requirement, the City may discuss or negotiate the conditions, exceptions, reservations or understandings during these meetings. But the City in its sole discretion may reject any and all conditions, exceptions, reservations and understandings, and the City may instruct any Offeror to remove the conditions, exceptions, reservations or understandings. If the Offeror fails to do so, the City may determine the Offer is nonresponsive, and the City may revoke its determination that the Offer is in the Competitive Range.
To the fullest extent permitted by law, the City will not provide any information, financial or otherwise, to any Offeror about other Offers received in response to this solicitation. During discussions with Offerors in the Competitive Range, the City will not give Offerors specific prices or specific financial requirements that Offerors must meet to qualify for further consideration. The City may state that proposed prices are too high with respect to the marketplace or otherwise unacceptable. Offerors will not be told of their relative rankings before Contract award.
2.31. Best and Final Offers (BAFO)
A BAFO is an option available for negotiations. Each Offeror in the Competitive Range, which is determined in the City’s sole discretion, may be afforded the opportunity to amend its Offer and make one BAFO.
If an Offeror’s BAFO modifies its initial Offer, the modifications must be identified in the BAFO. The City will evaluate BAFOs based on the same requirements and criteria applicable to initial Offers. The City will adjust appropriately the initial scores for criteria that have been affected by offer modifications made by a BAFO. Based on the criteria defined in the solicitation as weighted, the City will then perform final scoring and prepare final rankings.
The Evaluation Panel will recommend the Offer that is the best value and most advantageous to the City based on the evaluation criteria.
The City reserves the right to make an award to an Offeror whose Offer is the highest rated, best value, and most advantageous to the City based on the evaluation criteria, without conducting written or oral discussions with any Offeror, without negotiations, and without soliciting BAFOs.
3. Scope of Work
3.1. Background
The primary function of the Operations Control Center (OCC) is to oversee and manage Phoenix’s fixed-route transit fleet through the Computer-Aided Dispatch/Automatic Vehicle Location (CAD/AVL) system. In addition to real-time monitoring, the OCC takes a proactive approach to service management by continuously tracking vehicles in revenue service, identifying potential delays, and coordinating with the transit yards to implement corrective actions before and when service disruptions occur. OCC staff coordinate closely with bus operators and transit yard personnel to mitigate missed service, address equipment or service issues, and ensure that buses are deployed efficiently. This collaboration is critical to maintaining schedule adherence and achieving system-wide on-time performance standards. By leveraging CAD/AVL data and effective communication protocols, the OCC plays a central role in delivering reliable, safe, and customer-focused transit service across the CITY and region.
The OCC also provides several critical regional functions, both independently and in coordination with the CITY. These responsibilities include, but are not limited to:
Data Collection and Reporting: Gathering operational data and producing detailed reports to support performance analysis and compliance.
Transit System Monitoring: Overseeing Phoenix-operated transit services as a function of regional transit operations to ensure service reliability and adherence to schedules.
Emergency Coordination: Acting as a central point for managing incidents and coordinating emergency services across agencies.
Public Communication: Creating and disseminating onboard public service announcements and distributing real-time trip information using the CAD/AVL system.
Farebox Management: Reporting farebox malfunctions to maintain revenue integrity.
Training and Support: Providing CAD/AVL system training to CITY contractors and partner agencies to promote consistent operational standards.
Contract Compliance: Developing operational reports tailored to agency-specific agreements with contracted fixed-route transit service providers.
Through these functions, the OCC plays a vital role in maintaining seamless regional transit operations, fostering collaboration among agencies, and ensuring a safe, efficient, and customer-focused transportation network.
The OCC directly manages transit vehicles engaged in revenue and non-revenue service, deadheading to and from routes, performing special event services, and staging in holding areas. This oversight applies to vehicles operating from the City’s three primary transit facilities: North Facility (located at 2010 West Desert Cove Lane), South Facility (at 2225 West Lower Buckeye Road), and West Facility (at 405 North 79th Avenue). The OCC provides centralized, real-time operational control in an impartial manner, independent of the private firms contracted to deliver transit services. This ensures consistent application of service standards and operational protocols across all facilities, regardless of provider.
OCC personnel are also responsible for gathering operational data to support route planning, performance analysis, and compliance reporting, including submissions to the National Transit Database (NTD).
The OCC is located on the 5th floor of the Public Transit Building at 302 North 1st Avenue, Phoenix, Arizona. The OCC suite currently houses eight CAD/AVL and radio workstations. Adjacent to the suite are two offices designated for the OCC Project Manager and administrative/data collection personnel. To support continuity of operations, additional office and workspace have been designated at the West Transit Facility (located at 405 North 79th Avenue). This secondary location serves as a recovery site, training center, and operations overflow area ensuring resilience and flexibility in managing transit operations under various emergency scenarios. CONTRACTOR is required to staff the secondary site, test equipment, and maintain the location in accordance with this scope of work.
3.2. Operations Control Center Function
The OCC oversees the CITY’s fixed route bus operations, which currently consist of 48 routes and over 21 million service miles per year. On a monthly basis, the OCC responds to over 3,000 phone calls from bus operators, Phoenix Police Department, and Valley Metro (VM) Customer Service personnel. Additionally, the OCC uses the CAD/AVL system to make and respond to over 65,000 radio calls and text messages monthly to facilitate transit service. During peak service, the OCC is responsible for the concurrent oversight of over 400 vehicles in revenue service.
The OCC’s primary responsibility is to monitor revenue service activity for the Phoenix transit fleet in order to minimize service disruptions. The CITY’s transit service reliability goals are as follows:
Achieve a minimum on-time performance of 85% on a per-route basis, defined by buses departing timepoints on-time, within 59 seconds early to 5 minutes and 59 seconds late, except for the last stop where early arrivals are acceptable.
No early departures greater than 59 seconds early from any timepoint for any route and trip.
Operate 100% of scheduled service.
In addition, the OCC provides oversight for:
Deadheading Operations: Vehicles traveling to and from revenue service.
Special Event Services: Coordinating transit support for planned events and directing those vehicles in the provision of special event services as requested by the City.
Vehicle Staging: Managing buses positioned throughout the transit environment as needed.
OCC personnel communicate vital operational information regularly to the CITY’s contracted transit operations dispatch and maintenance teams. The OCC also serves as:
Primary Contact for Emergency Services: Coordinating with Phoenix Police and Fire Departments during emergency requests.
Key Liaison for CITY and Valley Metro: Supporting CITY personnel and the VM Customer Service Center.
Regional Support Role: Aid member agencies of the Regional Public Transportation Authority (RPTA), also known as Valley Metro, as needed.
3.3. Reports and Data Collection
Using the CITY’s CAD/AVL system’s reporting functions, CONTRACTOR will provide or assist the CITY in the preparation of specific, routine or non-specific documents or reports as required by federal, state, county, or agencies and/or the CITY. This may include the preparation of grant applications and related quarterly reports, short and long-range transit plans, annual FTA reports, and ongoing operating and statistical analysis statements. Such reports will be completed in accordance with CITY and federal requirements. Additionally, the CONTRACTOR may be asked to assist with the preparation or generation of regional reports in support of the CITY and its regional partners.
Examples of reports to be provided by CONTRACTOR as requested unless otherwise specified, include, but are not limited to, the following:
OCC Reports:
Operational Reports (daily and monthly)
Emergency Services (daily and monthly)
Priority/Emergency Calls
Detour Database
Daily Maintenance Operations
Vehicles Towed
Road Calls
Accidents
Bus Changes
ADA Incidents
On-Time Performance (daily and monthly; all facilities, per facility, by route, by timepoint, by operator)
Missed Service (daily and monthly)
Missed Trips
Schedule Delays
Call Volume
Vehicle Data Download Status
Incoming Messages
CAD/AVL User Management
Farebox Malfunctions
Creation and Design of As-Needed CAD/AVL Reports
Wheelchair Lift Status
Wheelchair Lift Deployment Count
Automatic Passenger Counter System Status
Mobile Radio Failure Status
GPS Failure Status
Vehicle Count by Garage
Data Collection Function Reports
Monthly National Transit Database (NTD) reports
3.4. Staffing and Personnel Requirements
CONTRACTOR shall maintain a comprehensive staffing plan designed to provide proactive and concurrent oversight of all CITY fixed route vehicles in revenue service and to perform all data collection functions. OCC Staff shall be maintained under a Full-Time Commitment: Ability to work a minimum of 40 hours per week.
On-Site Presence: Physical presence for the OCC Project Manager is required at the Operations Control Center during standard business hours (8:00 a.m. – 5:00 p.m.), with flexibility for occasional after-hours, holidays, and weekend support. Physical presence for the CAD/AVL Controllers is required seven days a week, nearly 24 hours per day.
The Contractor shall ensure that designated Key Personnel/other supervisory personnel, provide continuous operational oversight throughout all required service periods. Key Personnel shall be physically present and actively performing their duties for a minimum of forty (40) hours per week (as shown above) and must remain available and onsite during all standard operating hours unless otherwise authorized in writing by the City. The Contractor acknowledges that operational needs may require Key Personnel to work weekends, holidays, non-standard hours, or respond to emergent situations. Such coverage shall be provided at no additional cost unless expressly approved in writing. In the event Key Personnel are unavailable for any period, the Contractor shall ensure a qualified and pre approved alternate is immediately assigned to maintain uninterrupted supervision and service continuity.
Contractor's staffing plan must ensure:
Adequate Staffing Levels: Sufficient personnel to monitor fleet operations and maintain real-time situational awareness and proactive service monitoring including the bus-to-controller staffing requirements of Section 3.10.F.1.
Cross-training and Skill Diversification: Staff are trained on multiple OCC functions (e.g., dispatch, data collection and emergency coordination) so coverage remains steady during absences or turnover.
Flexible Scheduling and Backup Coverage: Rotating shifts, with a pool of on-call or part-time staff to cover unexpected vacancies or staff leave.
Succession Planning: Maintain trained candidates ready to step into critical roles if needed.
Specialization of Labor: Clearly defined roles and responsibilities to support effective fleet oversight and operational efficiency.
Responsive Communication: Capacity to manage heavy volume of controller-related communications, including phone calls, radio transmissions, and text messages, especially during controller absences, vacations, or other staffing disruptions.
The CITY defers to the offerors and their subject matter expertise in determining appropriate staffing levels necessary to perform the functions outlined in this Scope of Work. This includes incorporating administrative and support positions not explicitly identified in the Scope of Work but that enhance the OCC’s responsiveness, efficiency, and overall ability to manage transit services in a dynamic operating environment. However, the CITY reserves the right to review and approve the CONTRACTOR’s staffing plan (as specified in section 3.4.A. Staffing and Personnel Requirements) and corresponding budget to ensure adequacy, compliance, and alignment with operational requirements and transit industry best practices.
Operations Control Center Function: The OCC currently operates with one (1) Manager and twenty (20) CAD/AVL Controllers, providing services seven days a week, nearly 24 hours per day.
OCC Project Manager: The current OCC Manager oversees revenue transit service operations by supervising and staffing the Operations Control Center, managing CAD/AVL system data, and developing policies to optimize performance. The role also serves as the primary liaison for interagency communication, coordinates with fixed-route contractor management on compliance issues and monitors operational performance to drive continuous improvement. The manager is required to work a minimum of the standard business hours listed above. The manager position also requires strong leadership, communication, and problem-solving abilities, with a proven track record of managing teams in high-pressure environments, and experience in transit operations, OCC management, and proficiency with CAD/AVL systems. The manager must be familiar with OCC technologies, Windows-based applications, and reporting tools, and can maintain effective, unbiased relationships with internal teams, contractors, and external agencies.
Lead OCC Controller(s): The current Lead OCC Controller(s) supervise and guide OCC Controllers in monitoring bus operations, serving as the escalation point for complex issues and coordinating responses to major incidents, emergencies, and service disruptions while maintaining real-time situational awareness of the transit network. They also ensure compliance with operational policies, assist in training and mentoring staff, and prepare incident reports and operational summaries for management review.
OCC Controllers: Current OCC Controllers provide front-line monitoring and support for bus operations, making real-time decisions to assist operators with schedule adherence, safety, and service quality. They also coordinate responses to incidents, security events, and equipment issues while communicating critical information to operators, emergency services, city officials, and other stakeholders.
Data Collection Function: The Data Collection function is currently staffed by (1) one Data Collection Coordinator and (2) two Data Collectors. Services are provided seven days per week across an approximately seventeen-hour operational window; however, reporting deadlines may necessitate work outside the normal operational window.
Data Collection Coordinator: The current Data Collection Coordinator plans, organizes, and manages data workflows for Federal National Transit Database reporting, ensuring compliance with applicable rules, regulations, and timelines established by the CITY. This role also coordinates random trip generation, compiles daily, weekly, monthly, and special reports for transit planning staff, and assists in training and supporting Data Collectors.
Data Collector(s): Current Data Collectors conduct on-board and stationary checks to gather accurate ridership, schedule adherence, and fare payment data for statistical reporting and service improvement. They also evaluate bus stop and shelter usage, collect site-specific information, and distribute survey questionnaires to support transit planning and grant applications.
Refer to Exhibit A – Incumbent OCC Job Descriptions & Wages for the above-described OCC and Data Collection positions.
3.5. Staffing During Contract Transition Period
To ensure continuity of service during contract transition, the CONTRACTOR shall offer to retain, and if the offer is accepted, retain the current employees of the incumbent contractor for a 90-day transition period beginning on the commencement date of the contract, subject to the following:
The CONTRACTOR is not required to offer to retain a current employee of the incumbent contractor if: (1) the CONTRACTOR determines, based on reliable evidence of the employee’s past performance history, that there would be just cause to discharge the employee if employed by the CONTRACTOR; or (2) the employee held a key management position with the incumbent contractor, as specified in 3.4.C.
For purposes of this provision, the term “current employee of the incumbent contractor” means an employee of the incumbent contractor performing services covered by this Scope of Work that was employed by the incumbent contractor on the date of award of this contract to the CONTRACTOR and had been employed continuously by the incumbent contractor for, at a minimum, the sixty (60) day period immediately preceding the date of award or commencement date of the contract to the CONTRACTOR.
During the 90-day transition period, retained employees shall be employed under terms and conditions established by the CONTRACTOR or as required by law; provided, however, that the CONTRACTOR shall pay each retained employee an hourly wage, at the outset of their employment with the CONTRACTOR, that is not less than the hourly wage in effect for such employee on the date of their separation from employment with the incumbent contractor.
If the CONTRACTOR determines that fewer employees are required to deliver the services required under this contract than were required by the incumbent contractor, the CONTRACTOR shall retain current employees of the incumbent contractor by seniority within job classification and maintain a preferential hiring list of current employees not retained by the CONTRACTOR from which the CONTRACTOR may hire additional employees, if needed, during the 180-day transition period.
During the 180-day transition period, the CONTRACTOR shall not discharge an employee retained by the CONTRACTOR pursuant to this provision without cause.
3.6. Service Area
The CITY’s fixed-route transit services are designed to operate as directly and efficiently as possible, ensuring routes are easy to understand and minimize travel time. Each route includes unique movements, layover times, and designated locations.
The service area for the work described in this Scope of Work will be designated by the CITY. Currently, the CITY’s total service area encompasses the metropolitan Phoenix region, including Mesa, Tempe, Chandler, Gilbert, Phoenix, Glendale, Peoria, Scottsdale, Avondale, Goodyear, and Tolleson. A map of the regional service area is available on the Valley Metro website: https://www.valleymetro.org/maps-schedules/system-map.
North and South Transit Facilities: As of FY2026, service consists of 36 fixed transit routes, serving on average 77,900 passengers per day. Fixed route transit services are routes 0, 1, 7, 8, 10, 12, 15, 16, 19, 27, 28, 32, 35, 39, 44, 50, 52, 60, 70, 80, 90, 106, 122, 138, 154, 170, and 186, as well as the I-10 East, I-10 West, I-17, Central/South Mountain East, Central/South Mountain West, SR-51 RAPID routes, and three neighborhood circulators (“DASH,” “SMART,” and “ALEX”). The subject routes are currently operated by Transdev Services. Approximately 270 vehicles from the North and South Transit Facilities are in operation during peak revenue service.
West Transit Facility: As of FY2026, service consists of 12 fixed transit routes, serving on average 45,000 passengers per day. Fixed route transit services are routes 3, 13, 17, 29, 41, 43, 51, 59, 67, 75, and 83, as well as one Phoenix neighborhood circulator (“MARY”). The subject routes are currently operated by Transdev dba First Transit, Inc. Approximately 132 vehicles from the West Transit Facility are in operation during peak service.
3.7. Contractor Responsibilities
CONTRACTOR will be responsible for managing all OCC and data collection functions, delivering the required services, and providing all additional goods and services necessary to fulfill the Scope of Work, even if not explicitly stated.
CONTRACTOR will provide all personnel and support functions necessary for operations, including accounting, budget development, recruitment, payroll, benefits administration, and all other aspects of personnel management. Additionally, the Contractor will provide all required training and refresher training to ensure that OCC Controllers and Data Collection staff can satisfactorily perform their assigned duties.
CONTRACTOR will continue providing the remaining services described throughout the Scope of Work regardless of increases or decreases in services or subsequent to the possible transition of one or more of the functions or positions from the Contractor to the CITY.
CONTRACTOR, in coordination with the CITY’s transit operations contractors, will be responsible for the day-to-day management, control, and oversight of buses in revenue service at CITY operating facilities, preparing for or completing revenue service, or otherwise in the field. The OCC will monitor and resolve impacts to transit services as they occur throughout the transit environment, including but not limited to passenger loads, accidents, vehicle breakdowns, detours, responses to emergencies, and other incidents as they occur.
Decisions by OCC staff will be made in the best interest and safety of the passengers and bus operators, and every effort will be made to coordinate with the transit operations contractor(s) to minimize possible impacts to transit service and published schedules. The Contractor will direct issues concerning vehicle maintenance or personnel/labor to the respective transit service contractor(s) for resolution.
Special Event Support: As directed or authorized by the CITY or its designee, CONTRACTOR will provide support for special event services. These services may vary throughout the term of the contract and can include directing bus deployment during special events, as well as providing emergency response and evacuation support. For certain events, the CONTRACTOR will be required to deliver enhanced levels of management, administration, planning, and oversight during both the preparation and execution of these specialized services.
Light Rail Bus Bridging: As directed or authorized by the CITY or its designee, CONTRACTOR will be required to periodically support coordination with CITY and Valley Metro Light Rail staff to participate in the planning, training, practice exercises, and implementation of bus bridging efforts during times of service interruptions or inoperability of the light rail system for any reason. Light rail bus bridging includes, but is not limited to, the transport of passengers between designated light rail stations and bus stops during light rail service interruptions. All efforts related to special event services and light rail bus bridge planning, including classroom training, meeting attendance, and exercises, shall be considered as part of the CONTRACTOR’s training and operations program and included in the CONTRACTOR’s special event service overall cost.
Automated Annunciators: Contractor will assist CITY Service Planning staff with automated annunciator uploads, if needed.
CONTRACTOR will assist with the generation of electronic automated annunciator data as needed. At the CITY’s request, CONTRACTOR will also assist with the generation of new and/or revised electronic automated annunciator uploads as needed to correct inconsistent/incorrect announcements and to implement public service and operational messages to transit passengers.
The CITY and CONTRACTOR will meet at a minimum of quarterly to determine appropriate schedules and processes for providing the above-mentioned information to meet CONTRACTOR’s work and service schedule update timelines.
As the primary users of the voice recorder application (currently Eventide), CONTRACTOR shall be responsible for understanding system functionality, including running reports and locating and downloading recordings for investigations as needed. CONTRACTOR shall also report any technical issues with the CITY’s voice recording system promptly.
CONTRACTOR shall remain flexible in adopting new technology introduced through system updates or replacements and shall update procedures accordingly to ensure efficient and effective use of such technology.
3.8. Standard Operating Procedures
CONTRACTOR shall maintain a comprehensive written record of all Standard Operating Procedures (SOP) related to transit system monitoring, reporting, and data collection. These SOPs must clearly outline all pertinent processes for managing fixed route services, including protocols for handling emergency service requests and incident notifications. The OCC SOPs shall be updated annually to reflect any technical or operational modifications implemented to enhance safety, improve service efficiency, ensure alignment with transit yard operational SOPs, and maintain compliance with the Scope of Work throughout the period of the contract. The updated SOPs shall be readily available for review by the CITY upon 60 days of request.
In instances where the CONTRACTOR is both a transit service provider and contracted with the CITY to provide OCC and Data Collection Services, the CONTRACTOR shall maintain a comprehensive plan detailing the policies and procedures designed to ensure a clear separation of duties and oversight between the provision of transit services and the management of the OCC and Data Collection functions.
The plan must include:
Distinct Personnel Oversight: Separate and clearly defined personnel management responsibilities at both local and regional levels.
Operational Independence: Measures to prevent conflicts of interest and maintain impartiality in OCC and Data Collection activities.
Availability to the CITY: CONTRACTOR shall provide and maintain a current version of the staffing plan and organizational chart. Updated versions must be made available to the CITY upon request throughout the term of the contract to ensure ongoing compliance.
3.9. Special Projects
At the CITY’s direction, CONTRACTOR shall assist with additional special projects, including, but not limited to, testing, troubleshooting, and/or support during:
Radio and Voice Over Internet Protocol (VOIP) testing
Server failover testing
Radio Tower testing and/or cutover activities
OCC warm-site testing, exercises and maintenance
CAD/AVL system updates, modifications and/or changes
HASTUS map reviews
Special schedule load reviews
New vehicle mobile component testing
Bus-in-Box (BIB), Bus-On-Board (BOB) training, testing, maintenance
Bus bridging exercises
Fare Collection System (FCS) monitoring and testing
Fare Validator system data monitoring and testing
Additionally, the CONTRACTOR shall develop, implement, and facilitate a Transit Service Reliability Working Group to coordinate with the CITY and the respective transit yards to monitor and maintain on-time performance and missed service goals. The working group will meet monthly at inception, transition to meetings every other month as performance stabilizes, and eventually move to quarterly meetings once goals are consistently achieved. The CONTRACTOR shall compile and share relevant transit performance data during working group meetings to support analysis, discussion, and informed decision making. The working group’s primary focus will be improving transit performance; however, it may address additional topics that support continuous improvement of the transit system to include members of City Staff and Operations Contractor Staff. CONTRACTOR will document these meetings and provide meeting minutes and action items within 5 business days of such meetings having taken place.
3.10. Performance Indicator/Liquidated Damages
All performance indicators and liquidated damage provisions will be strictly enforced. CONTRACTOR must adhere to all performance specifications to ensure the highest level of service quality. The CITY reserves the right to monitor CONTRACTOR’s performance under this contract to verify compliance with all requirements.
Performance indicators are metrics established by the CITY to measure CONTRACTOR’s effectiveness. Indicators listed below apply to the first year of service and may be used in subsequent years. CITY representatives may, without prior notice, observe Operations Control Center activities and monitor transit oversight to ensure compliance with this Scope of Work and the contract.
CITY also reserves the right to review and modify performance requirements as necessary to address unusual or extraordinary circumstances affecting transit service and to promote continuous improvement. All final determinations regarding performance levels and liquidated damage assessments will be made by the CITY.
To receive maximum compensation, CONTRACTOR must meet or exceed the following performance standards monthly. If CONTRACTOR fails to achieve the acceptable standards for any of the performance goals listed below, liquidated damages will be assessed and deducted from CONTRACTOR’s total monthly invoice amount.
Liquidated damages may also be imposed by the CITY for each observed violation committed by CONTRACTOR personnel. CONTRACTOR acknowledges and agrees that any violation of the liquidated damages provisions set forth in this contract will result in the CITY incurring damages that are impractical or impossible to precisely determine. The CONTRACTOR further agrees that the monetary assessments specified herein represent a reasonable approximation of such damages and are not intended as a penalty.
Performance Indicators and Associated Liquidated Damages Amounts:
Adherence to Bus to Controller Ratio: During peak service hours (6:00 a.m.–9:00 a.m. and 4:00 p.m.–7:00 p.m.) on weekdays, the CONTRACTOR must maintain a bus-to-controller ratio of at least 1 controller per 50 buses in revenue service. For each documented instance of non-compliance, the CITY will assess liquidated damages of $500.
Late or Inaccurate Reports or Data: If CONTRACTOR fails to meet the CITY’s reporting requirements—either by submitting reports, information, or data late or by providing inaccurate reports if monthly, by the 7th of each month—the City will assess liquidated damages of $500 for each month in which the failure occurs.
If the CONTRACTOR fails to report a critical incident within one hour of occurrence—such as accidents involving passenger injuries, bus-versus-pedestrian collisions, fatalities, media presence, or any other incident the CITY deems reportable—the CITY will assess liquidated damages of $500 per incident in which the notification failure occurs
3.11. Coordination with Other Agencies
At the CITY’s direction, CONTRACTOR shall cooperate with the CITY’s Phoenix Police Department (“PPD”) Transit Unit (“TU”) staff to ensure the safety and security of transit customers, facilities, and equipment by providing assistance with accident investigations, NTD safety/security reporting, emergency preparedness planning and training exercises, and other safety/security matters. CONTRACTOR shall ensure sufficient staffing levels to respond to the CITY, Emergency Services providers, and transit operations CONTRACTOR’S requests in a timely and comprehensive manner.
CONTRACTOR shall notify PPD TU of serious incidents in accordance with the CITY’s emergency notification procedures. The CONTRACTOR will be provided the notification procedures upon contract award.
CONTRACTOR shall implement a notification procedure to notify the CITY of incidents within an hour that may require PPD TU or otherwise require notification as determined by the CITY.
CONTRACTOR shall respond to any emergency services directives received from the CITY.
3.12. City-Provided and Contractor-Provided Equipment
CONTRACTOR shall utilize CITY resources for the benefit of the CITY and the positive performance of the regional transit system. CONTRACTOR shall not use CITY resources for any activity not covered by this contract.
Within 30 calendar days of contract start date, CONTRACTOR shall provide to the CITY internet email addresses capable of reaching all CONTRACTOR staff. This information will be used to communicate critical system information as needed.
The CITY shall have immediate and unrestricted access to all CITY-provided hardware and software and will conduct inspections at the City’s discretion. Any hardware and software deficiencies identified (i.e., items found to be out of compliance with the CITY’s information technology policies, procedures, and/or Administrative Regulations) shall be corrected within five business days of inspection.
3.13. 302 Building - Public Transit Headquarters
Office space for the OCC is located within the Public Transit Headquarters on the fifth floor of the building, located at 302 N. 1st Avenue, Phoenix, Arizona. The facility sits at the northwest corner of 1st Avenue and Van Buren Street. The facility was designed and sized as a professional office building.
Parking Garage
Underground parking garage – 6 floors, 313 spaces
174 spaces occupied by tenants
139 spaces available for hourly public parking
3.14. Space Allocation
CONTRACTOR will be allocated office, work, and storage space within the Public Transit Headquarters/302 Building, 5th Floor, for the purpose of managing the Operations Control Center and Data Collection functions only. CONTRACTOR spaces have been designated in Exhibit B – OCC Site Plan. Under no circumstances shall modifications to any part or system of the facility be made without the CITY’s express, written consent.
Additional office and work space has been designated at the West Transit Facility (located at 405 North 79th Avenue) for use as a recovery (warm) site during instances of technology and/or infrastructure failures (Refer to Exhibit C - OCC Warm Site Plan). Similarly, two OCC overflow/support workstations have been designated at the 302 Building in the office space adjacent to the OCC suite (Refer to Exhibit B - OCC Site Plan). The West Facility warm site and OCC overflow workstation site are available for daily CONTRACTOR use for recovery, testing, standard, and/or overflow operations.
3.15. Furniture
CITY will provide a furnished OCC for CONTRACTOR that includes eight (8) CAD/AVL workstations with work surfaces. The overflow area includes two (2) CAD/AVL workstations with work surfaces. At the OCC redundant (warm) site, the CITY will provide three (3) CAD/AVL workstations with work surfaces. CONTRACTOR shall be responsible for providing and maintaining all workstation chairs for the main OCC suite, overflow area, and warm site, including any replacements or additional chairs needed during the term of the contract.
The OCC suite is equipped with two (2) wall-mounted 47-inch television monitors for controller staff to monitor real-time events as reported by local/national news media. The CITY will provide the existing monitors; however, if either monitor fails during the term of the contract due to damage, vandalism or misuse, the CONTRACTOR shall be responsible for its replacement, and the City will retain ownership of the replacement monitors upon contract termination or expiration. Additional office furniture, equipment, or workstations may not be added to the allocated space without the CITY’s express written consent.
3.16. Facility Maintenance
As the operator of the OCC, CONTRACTOR is responsible for the safe and proper care/operation of the space allocated. Public Transit uses a contractor who is responsible for repairing the facility, its systems and components, as well as any CITY owned or CITY provided equipment. (including work status, scheduling, equipment downtime, etc.). The CITY or its property management contractor will coordinate with the CONTRACTOR to ensure facilities maintenance work is scheduled to minimize disruption. CONTRACTOR shall make reasonable adjustments to its operations to accommodate necessary facilities maintenance work. CONTRACTOR shall also communicate to CITY designated staff any significant impacts and disruptions to its operations caused by issues or problems with facility systems, components, or equipment.
CONTRACTOR must maintain a clean and safe work environment in all areas used by the CONTRACTOR. The CITY provides janitorial services for the Public Transit Building, 5th floor, including the OCC suite and adjacent offices.
The CITY at its sole discretion may perform refurbishments to upgrade or update the facility as deemed necessary. CONTRACTOR shall work collectively with the CITY and the CITY will not be responsible for any costs to the CONTRACTOR incurred due to such activities.
3.17. Facility and Equipment Damage
CONTRACTOR shall be financially responsible for any facility and/or equipment damage caused by CONTRACTOR’s misuse or abuse (accidents, improper operation, theft, etc.). Repairs or replacement will be performed by, and resolved through, the CITY’s facilities maintenance staff. All damage must be immediately reported to the CITY via the Exhibit D - Facility Incident-Repair Request Procedure. The CITY shall invoice CONTRACTOR for any and all damage determined to be the responsibility of the CONTRACTOR. The CITY at its sole and unfettered discretion shall determine the responsible party for all such facility/equipment damage claims.
3.18. Parking
Parking Spaces: The CITY agrees to furnish covered, non-reserved parking spaces within the 302 Building parking facility for CONTRACTOR’s employees. The parking spaces shall be available for use at the same monthly rate charged to CITY employees, which is currently $47 per month per parking space. CONTRACTOR agrees and understands that the prevailing rate charged to CITY employees is subject to increases subsequent to execution of this contract, and CONTRACTOR agrees to pay the increased rate as may be charged to CITY employees. The CITY does not provide reserved parking spaces under this contract
Parking Rules: The CITY reserves the right to adopt, modify, and enforce reasonable rules governing the use of the parking areas from time to time, including any key-card, sticker or other identification or entrance system and hours of operation. The CITY may refuse to permit any person who violates such rules to park in the parking areas, and any violation of the rules shall subject the car to removal from the parking areas. The CONTRACTOR will be provided with the parking rules upon contract award.
3.19. City's Responsibilities
The Public Transit Department, either directly or through its transit service providers, will coordinate all CITY efforts related to the operations of its transit services and will have the primary responsibility for providing all operational and route planning, vehicle and driver scheduling, and long-range and short-range transit planning capabilities. CONTRACTOR shall provide assistance for these activities as needed or as otherwise directed by the CITY.
CITY retains the right to modify transit services at any time. CITY is responsible for creating schedules and modifying the operating characteristics of its transit services. This may include service increases or decreases, routing, allocation of equipment and vehicles, and service to other transit operators or agencies whenever the CITY can operate the service(s) more efficiently.
The cities of Avondale, Glendale, Goodyear, Peoria, Scottsdale, Tolleson, and Youngtown currently purchase transit services from the CITY and may at any time request to operate such services directly. In such instances, the service will be reallocated at the discretion of the applicable city to other service providers. CONTRACTOR shall be given appropriate notice of any of these service changes to minimize the impact on the CONTRACTOR’s workforce.
Minor service adjustments to CONTRACTOR’s contract with the CITY may be affected by written contract amendments. Significant service adjustments may require the approval of the Phoenix City Council. Under such circumstances, the CONTRACTOR will be given written notice of these changes. In the event adjustments need to be made for services which have an unfavorable impact on the service operated under this contract or other conditions occur that make continued operations unreasonable or economically unfeasible, the CITY will give prior written notice and direction to the CONTRACTOR.
CITY will provide certain capital and fixed equipment which will be for the CONTRACTOR’s use. The CITY retains ownership of CITY-provided equipment, and CONTRACTOR retains ownership of CONTRACTOR-provided equipment unless it replaces City equipment that was damaged, vandalized, or misused, in which case ownership transfers to the City. A listing of CITY-provided equipment for the Operations Control Center and Data Collection function is as follows:
Clever Devices workstations
CAD/AVL AVTEC workstation
AVTEC Media Tower and associated peripherals
HASTUS Dispatch Software Module
Bus-in-a-Box (BIB)
2 existing Samsung televisions with wall-mount hardware
1 - CAD/AVL printer in the OCC controller suite
Controller workspace/surfaces
OCC Project Manager and Data Collection Coordinator workspace/surfaces
The CITY will provide telephone service through the CITY’s Information Technology Services Department. The CITY-provided telephone service is to be used for the purposes of providing the services required under this contract. The CONTRACTOR will be responsible for reimbursing the CITY for any charges for personal usage of the telephone system by CONTRACTOR’s employees. The CITY does not provide cell phones or pagers. It is the CONTRACTOR’S responsibility to provide cell phones or pagers to employees if needed for this contract.
The CITY owns all of the aforementioned CITY-provided assets, and the CONTRACTOR shall ensure that the CITY’s interest in the assets and inventory is protected from loss or damage. The Contractor will complete an initial inventory within 60 calendar days of contract start date and annually thereafter.
3.20. City of Phoenix Information Technology Requirements
CONTRACTOR shall comply with the CITY’s Information Technology Requirements. See Exhibit E - Technical Requirements.
3.21. Facility and Building Access
The CITY shall establish and maintain control over the access control system for the facility, including all CONTRACTOR and CITY employees at the facility(ies).
The CITY will issue electronic access cards to CONTRACTOR employees for access and to serve as required identification to facility or building areas only after employees have met the CITY’s background check requirements and have been assigned to work at the facility.
Confirmation requirements for employment or requisite background checks shall be performed at the CONTRACTOR’s sole expense.
CONTRACTOR shall provide a complete background check report for the Maximum Risk level background check for all employees. CONTRACTOR background checks will, at a minimum, comply with the CITY’s A.R. 4.45 – Contractor and Subcontractor Worker Background Screening and A.R. 2.324 Substance Abuse Policy.
Please refer to Exhibit F – A.R. 4.45 Contract Worker Background Checks, Exhibit G – Security Access & Control for additional information, and Exhibit H - A.R. 2.324 Substance Abuse Policy for additional information.
The CITY shall be responsible for the keying system and keys for all doors at the facility. All keys and CITY issued access cards will be inventoried and managed by the CONTRACTOR and regularly audited by the CITY. The CONTRACTOR shall adhere to all CITY rules and regulations for the use and management of identification badges, access cards, and keys.
4. Offer Evaluation Criteria
In accordance with the Administrative Regulation 3.10, Competitive Sealed Proposal awards shall be made to the responsive and responsible Offeror(s) whose Offer is determined in writing to be the most advantageous to the City based upon the evaluation criteria listed below.
The evaluation factors are listed in the relative order of importance and more details are provided in Scope of Work. The Weight (Points) for each Evaluation Criteria are the maximum points that may be assigned for that Criteria. The following evaluation criteria will be used to evaluate all Offers:
1. Expertise and Experience - Offeror's History
Provide a history of Offeror’s company and demonstrate at least five consecutive recent years’ experience in managing operations control centers and data collection in a system similar in scope, size, and complexity to the scope of work proposed (Reference Section 2.14).
Scoring Method:
0-100 Points
Weight (Points):
50 (5% of Total)
2. Expertise and Experience - Operational Oversight
Describe your experience providing operational oversight and/or key support services to a multi‑modal, regional transit agency. In your response, please address the following:
• Experience coordinating across bus, light rail, demand‑response, and other transit modes consistent with the regional responsibilities detailed in Sections 3.1.B and 3.6.
• Experience with special event operations, bus bridging for rail disruptions, or large‑scale service adjustments as described in Sections 3.7.F and 3.7.G
Scoring Method:
0-100 Points
Weight (Points):
100 (10% of Total)
3. Expertise and Experience - CAD/AVL
Describe the Offeror’s experience and the experience of your proposed personnel in working with Computer Aided Dispatch/Automatic Vehicle Location (CAD/AVL) systems or comparable real time transit operations platforms, including Clever Devices branded systems. Include details on system usage such as real time vehicle monitoring, radio and text communications, incident response workflows, reporting functions, troubleshooting, and integration with related operational or scheduling systems (Reference Section 3.2.A)
Scoring Method:
0-100 Points
Weight (Points):
100 (10% of Total)
4. Organizational Structure and Capacity - Key Personnel
Key personnel must be designated and identified. A description of these key positions is included in Staffing and Personnel Requirements (Reference Section 3.4). The following is a list of personnel the City believes are key to this project:
• OCC Project Manager
• Lead OCC Consultant(s)
• OCC Controller(s)
Provide a summary of the qualifications, background, and resumes of each staff member identified as key personnel, along with a description of how their experience and expertise align with and support the roles they will fulfill.
Scoring Method:
0-100 Points
Weight (Points):
60 (6% of Total)
5. Organizational Structure and Capacity - Organizational Chart
The Offeror should provide an organizational chart and structure which identifies how the following functions will be satisfied: Operations Control Center Function (Reference Section 3.2) and Reports and Data Collection (Reference Section 3.3). Please include the number of staff that will support each responsibility.
Scoring Method:
0-100 Points
Weight (Points):
35 (3.5% of Total)
6. Organizational Structure and Capacity - Strategies/SOPs
The Offeror should describe in detail strategies or standard operating procedures that they will provide in order to ensure service quality, achieve on-time performance goals, and the oversight of Operations Control Center and data collection (Reference Section 3.8).
Scoring Method:
0-100 Points
Weight (Points):
45 (4.5% of Total)
7. Organizational Structure and Capacity - Management Availability
Please describe how you ensure that management roles will be available during all required service periods, including evenings, weekends, and holidays as needed. Please detail your approach on how your firm would ensure coverage during absences, and how you will maintain uninterrupted management oversight through the term of the contract (Reference Section 3.4.C).
Scoring Method:
0-100 Points
Weight (Points):
60 (6% of Total)
8. Method of Approach - Staffing Plan
Please describe your approach to implementing a staffing plan that meets all minimum staffing, supervisory, training, and cross training requirements outlined in Sections 3.4. Your response should explain how you will ensure adequate coverage across all shifts, including during employee vacation, sick leave, and other planned or unplanned absences. Please also describe how you will maintain required qualifications, support staff development, and provide operational resilience through effective training and cross-training strategies.
Scoring Method:
0-100 Points
Weight (Points):
60 (6% of Total)
9. Method of Approach - On-Time Performance and Service Reliability
Please describe your approach to assisting the City’s transit operations contractors in meeting on time performance and service reliability goals (Reference Section 3.2.B), as well as ensuring adherence to the required bus to controller ratio (Section 3.10.F.1). Your response should outline the strategies, tools, and oversight methods you will use to support performance monitoring, identify and resolve operational issues, and maintain compliance with all staffing and controller to vehicle requirements.
Scoring Method:
0-100 Points
Weight (Points):
50 (5% of Total)
10. Method of Approach - Data Integrity
Describe your procedures to verify the integrity of operational data collected from CAD/AVL and other CITY systems per Sections 3.1.D, 3.3.A, and 3.7.A. Please include what checks are performed before data is used in performance calculations or NTD reporting.
Scoring Method:
0-100 Points
Weight (Points):
50 (5% of Total)
11. Method of Approach - Maintaining a Qualified Workforce
The Offeror shall describe in detail how they will attract, develop, and maintain a qualified and experienced workforce in accordance with Section 3.4.
Scoring Method:
0-100 Points
Weight (Points):
50 (5% of Total)
12. Method of Approach - Transition
Describe your approach for completing the transition of services prior to the contract start date. Explain the steps you will take to ensure uninterrupted continuity of operations throughout the transition, without delays (Reference Section 3.5)
Scoring Method:
0-100 Points
Weight (Points):
40 (4% of Total)
13. Pricing Proposal
Offerors shall submit pricing information electronically in Section 11 Pricing Proposal.
Scoring Method:
Reward Low Cost
Weight (Points):
300 (30% 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” 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" The City of Phoenix
"Contractor" 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" The legal agreement executed between the City of Phoenix, AZ and the Contractor.
“Days” Means calendar days unless otherwise specified.
“Chief Procurement Officer” The contracting authority for the City of Phoenix, AZ, authorized to sign contracts and amendments thereto on behalf of the City of Phoenix, AZ.
“Employer” 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” 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” Firms, entities or individuals furnishing goods or services to the City.
“Vendor or Seller” 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
Exhibits
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 Contractor 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.
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.
Electronic Signatures: Electronic signatures are valid under Arizona law. Either or all parties may execute this Agreement by scanned or electronic signature, and any such scanned or electronic signature shall be deemed an original, valid, and binding signature if issued with proper signature authority.
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 ("Notice") between the City and Contractor that are required to be given under this Contract shall be in writing and given by (1) personal delivery, (2) email with return receipt requested (read receipt), (3) facsimile transmittal with delivery confirmation, (4) prepaid delivery to any commercial air courier or express delivery service, or (5) registered or certified mail, postage prepaid and return receipt requested, through the United States Postal Service.
Notices to the City shall be sent to: City of Phoenix, Public Transit Department, Procurement Section, 302 N. 1st Avenue, 9th Floor, Phoenix, AZ 85003 or ptdprocurement@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 in Submittal Forms - Offer Page.
5.12. Integration
This Agreement constitutes and embodies the full and complete understanding and agreement of the parties hereto and supersedes all prior understandings, agreements, discussions, proposals, bids, negotiations, communications, and correspondence, whether oral or written. No representation, promise, inducement or statement of intention has been made by any party hereto which is not embodied in this Agreement, and no party will be bound by or liable for any statement of intention not so set forth.
5.13. 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.14. 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.15. 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.16. 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.17. 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.18. 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.19. 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.20. 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.21. Claims or Demands Against the City
Contractor acknowledges and accepts the provisions of Chapter 18, Section 14 of the Charter of the City of Phoenix, pertaining to claims or demands against the City, including provisions therein for set-off of indebtedness to the City against demands on the City, and Contractor agrees to adhere to the prescribed procedure for presentation of claims and demands. Nothing in Chapter 18, Section 14 of the Charter of the City of Phoenix alters, amends or modifies the supplemental and complementary requirements of the State of Arizona Notice of Claim statutes, Arizona Revised Statutes §§ 12-821 and 12-821.01, pertaining to claims or demands against the City. If for any reason it is determined that the City Charter and state law conflict, then state law will control.
Moreover, nothing in this Agreement will constitute a dispute resolution process, an administrative claims process, or contractual term as used in Arizona Revised Statutes § 12-821.01(C), sufficient to affect the date on which the cause of action accrues within Arizona Revised Statutes § 12-821.01(A) and (B).
5.22. 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.23. 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.
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.
6. Special Terms and Conditions
6.1. Term of Contract
The term of this Agreement will be for five (5) years, beginning on the Commencement Date, with one two-year option to extend, which may be exercised by the City in its sole discretion.
6.2. Price
All prices offered shall be firm and fixed for the entire term of the contract. Price decrease requests do not require supporting documentation and are allowed at any time during the contract term.
6.3. 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.4. 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
6.5. Method of Payment
Contractor will be paid on a annual basis in arrears.
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. Estimated Quantities or Dollar Amounts (Requirements Contracts Only)
Quantities and dollar amounts listed are the City’s best estimate and do not obligate the City to order or accept more than City’s actual requirements during the period of this agreement, as determined by actual needs and availability or appropriated funds. It is expressly understood and agreed that the resulting contract is to supply the City with its complete actual requirement for the contract period.
6.8. 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.9. Hours of Work
All work under this contract shall be coordinated with the City’s authorized Department representative. Any changes to the established schedule must have prior written approval by the City’s authorized Department representative.
6.10. Post Award Conference
A post-award conference will be held prior to commencement of any work on the project. The purpose of this conference is to discuss critical elements of the work schedule and operational problems and procedures.
6.11. Performance Interference
Contractor shall notify the City’s authorized Department representative 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.12. 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.13. 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 City.
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. Hiring of Each Other's Personnel
Without the prior written consent of the other party, each party shall not actively target for hire personnel of the other party through the term of this Agreement and for six (6) months after the expiration or termination of the last Statement of Work executed by the parties. This prohibition does not apply to or affect in any way the City's standard recruitment processes. The City will not pay a fee or owe any compensation whatsoever to the Contractor if Contractor's employee files an employment application, competes successfully and is hired into a City position. Individuals who are employed by Contractor agency and who are on assignment at the City may file an application for regular City employment and be considered on the same merits and qualifications as would all other applicants. For this reason, compensation to Contractor would not be appropriate and not incurred if such worker succeeds in the selection process and is appointed to a regular City position.
6.16. 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 City will be the sole judge in determining the liquidated damages.
6.17. Procurement Reports
Contractor shall submit as stated in the scope of work. reports in an electronic format acceptable to the City during the term of this contract commencing one month after the effective date. These reports are due by the N/A day of the month following the reporting period. Total purchases for each department must be shown on a separate line. Report should be rounded to the nearest dollar. Contractor will provide sample forms for approval by the City.
6.18. 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.19. Contractor Assignments
The Contractor hereby agrees that any of its employees who may be assigned to a City site to satisfy obligations under this contract shall be used exclusively for that purpose during the hours when they are working in areas covered by this contract and shall perform no work at other City facilities. If other services, in addition to or separate from, the services specified herein, may be deemed necessary by the Chief Procurement Officer or his authorized representative, the Contractor may be requested to perform the additional or special service.
6.20. Service Locations
To minimize the City’s transportation and handling costs, the Contractor’s location(s) will be a factor in the City’s award decision.
6.21. Transition of Contract
Contractor will, without limitation, provide important information to a successor Contractor and the City to ensure continuity of service at the required level of proficiency and agrees to provide to the City all files, supplies, data, records, and any other properties or materials of the City, which the City owns or has rights to pursuant to this contract and which are in the possession of Contractor. The provisions of this section will survive the expiration or termination of this contract.
6.22. Background Screening
Contractor agrees that all Contractor and subcontractors’ workers (collectively “Contract Worker(s))” pursuant to this Agreement will be subject to background and security checks and screening (collectively “Background Screening”) at Contractor’s sole cost and expense, unless otherwise provided for in the scope of work. Contractor’s background screening will comply with all applicable laws, rules and regulations. Contractor further agrees that the background screening is necessary to preserve and protect the public health, safety and welfare. The City requires a completed Contract Worker Badge/Key/Intrusion Detection Responsibilities Agreement for each Contract Worker who requires a badge or key.
6.23. Background Screening Risk Level
The City has established two levels of risk: Standard and Maximum risk. If the scope of work changes, the City may amend the level of risk, which could require the Contractor to incur additional contract costs to obtain background screens or badges.
6.24. Terms of This Section Applicable to all Contractor’s Contracts and Subcontracts
Contractor will include Contract Worker background screening in all contracts and subcontracts for services furnished under this agreement.
6.25. Materiality of Background Screening Requirements; Indemnity
The background screening requirements are material to City’s entry into this agreement and any breach of these provisions will be deemed a material breach of this contract. In addition to the indemnity provisions set forth in this agreement, Contractor will defend, indemnify and hold harmless the City for all claims arising out of this background screening section including, but not limited to, the disqualifications of a Contract Worker by Contractor. The background screening requirements are the minimum requirements for the Agreement. The City in no way warrants that these minimum requirements are sufficient to protect Contractor from any liabilities that may arise out of the Contractor’s services under this Agreement or Contractor’s failure to comply with this section. Therefore, Contractor and its Contract Workers will take any reasonable, prudent and necessary measures to preserve and protect public health, safety and welfare when providing services under this Agreement.
6.26. Continuing Duty; Audit
Contractor’s obligations and requirements will continue throughout the entire term of this Agreement. Contractor will maintain all records and documents related to all background screenings and the City reserves the right to audit Contractor’s records.
6.27. Variances and Exemptions
Contract Workers who fall under the following areas may be considered exempt from this policy:
Federal Homeland Defense Bureau.
Transportation Security Administration.
Federal Aviation Administration.
Department of Public Safety (DPS) Administration – presenting a current Level One Department of Public Safety fingerprint card.
Arizona or other State Bars.
Other background checks performed within the last three to five years may be approved if they fit all required criteria herein, at the City’s discretion.
6.28. Contractor’s Default; Liquidated Damages; Reservation of Remedies for Material Breach
If Contractor is required to access any City facilities without an escort, City badging is required. Contractor’s default under this section will include, but is not limited to, the following:
Contract Worker gains access to a City facility(s) without the proper badge or key;
Contract Worker uses a badge or key of another to gain access to a City facility;
Contract Worker commences services under this agreement without the proper badge, key or background screening;
Contract Worker or Contractor submits false information or negligently submits wrong information to the City to obtain a badge, key or applicable background screening; or
Contractor fails to collect and timely return Contract Worker’s badge or key upon termination of Contract Worker’s employment, reassignment of Contract Worker to another City facility or upon the expiration, cancellation or termination of this Agreement.
Contractor acknowledges and agrees that the access control, badge and key requirements in this section are necessary to preserve and protect the public health, safety and welfare. Accordingly, Contractor agrees to properly cure any default under this section within three business days (excluding weekends and City holidays) from the date notice of default is sent by the City. The parties agree that Contractor’s failure to properly cure any default under this section will constitute a breach of this section. In addition to any other remedy available to the City at law or in equity, the Contractor will be liable for and pay to the City the sum of $1,000.00 for each breach by Contractor in this section. The parties further agree that the sum fixed above is reasonable and approximates the actual or anticipated loss to the City at the time and making of this agreement if Contractor breaches this section. Further, the parties expressly acknowledge and agree to the fixed sum set forth above because of the difficulty of proving the City’s actual damages if Contractor breaches this section. The parties further agree that three breaches by Contractor in this section arising out of any default within a consecutive period of three months or three breaches by Contractor in this section arising out of the same default within a period of 12 consecutive months will constitute a material breach of this agreement by Contractor and the City expressly reserves all of its rights, remedies and interests under this agreement, at law and in equity including, but not limited to, termination of this agreement.
6.29. Employee Identification and Access
Contract Workers are forbidden access to designated restricted areas. Access to each building will be as directed by the authorized Phoenix authorized representative. Contract Workers are not authorized access other than during scheduled hours. Access to the building will be directed by the City's authorized representative.
Only authorized Contract Workers are allowed on the premises of the City facilities/buildings. Contract Workers are not to be accompanied in the work area by acquaintances, family members, assistants or any other person unless said person is an authorized Contract Worker.
Unless otherwise provided for in the scope of work:
Contract Workers must always have city issued badges and some form of verifiable company identification (badge, uniform, employee id).
Contractor will supply a list of the names and titles of all employees requiring access to the buildings. It is the Contractor's responsibility to provide updates and changes of personnel as necessary.
6.30. Key Access Procedures
If the Contractor Worker’s services require keyed access to enter a City facility(ies), a separate key issue/return form must be completed and submitted by the Contractor for each key issued. Contractor must submit the completed key issue/return form to the appropriate badging office.
Stolen or Lost Badges or Keys
Contractor must immediately report lost or stolen badges or keys to the City’s appropriate badging office. If the badge/key was stolen, Contract Worker’s must report the theft to their local police department. Prior to issuance of a new badge or key, a new badge application or key issue form must be completed, submittal of a police department report for stolen badges, and applicable payment of the fee(s) listed herein.
Return of Badge or Key
All badges and keys are the property of the City and must be returned to the City at the badging office within one business day (excluding weekends and City holidays) of when the Contract Worker’s access to a City facility is no longer required to furnish the services under this agreement. Contractor will collect a Contract Worker’s badge and key(s) upon the termination of the Contract Worker’s employment; when the Contractor Worker’s services are no longer required at a City facility(s); or upon termination, cancellation or expiration of this agreement.
Badge and Key Fees
Refer to Exhibit G – Security Access & Control
The following constitute the badge and key fees under this agreement, which shall be paid for at the Contractor’s sole cost and expense, unless otherwise provided for in the scope of work. The City reserves the right to amend these fees upon a 30-day prior written notice to Contractor.
Initial Badge Fee: $55.00 per application
Replacement Badge Fee: $55.00 per badge
Lost/Stolen Badge Fee: $55.00 per badge
Replacement Key Fee: $55.00 per key
Replacement Locks: $55.00 per lock
6.31. Background Screening – Maximum Risk
Determined Risk Level: The current risk level and background screening required is MAXIMUM RISK.
Maximum Risk Level: A maximum risk background screening will be performed every five years when the Contract Worker’s work assignment will:
work directly with vulnerable adults or children, (under age 18); or
any responsibility for the receipt of payment of City funds or control of inventories, assets, or records that are at risk of misappropriation; or
unescorted access to:
City data centers, money rooms, high-value equipment rooms; or
unescorted access to private residences; or
access to critical infrastructure sites/facilities; or
direct or remote access to Criminal Justice Information Systems (CJIS) infrastructure.
Requirements: The background screening for maximum risk level will include a background check for real identity/legal name and will include felony and misdemeanor records from any county in the United States, the State of Arizona, plus any other jurisdiction where the Contractor worker has lived at any time in the preceding seven years from the Contract Worker’s proposed date of hire. In addition, Maximum screening levels may require additional checks as included herein, depending on the scope of work, and may be amended if the scope of work changes.
6.32. Additional Maximum Risk Background Checks
Maximum screening will additionally require:
Credit Check (for cash handling, accounting, and compliance positions only)
Driving records (for driving positions only)
Fingerprint verification (when Contract Worker is working directly with children or vulnerable adults or scope takes the individual to a City location with Criminal Justice Information System (CJIS) access.)
6.33. Maximum Risk Background Criminal Justice Information Services (CJIS) Check Must Include
Criminal records - Conviction of a misdemeanor(s) (not including traffic or parking violation) or felony(ies).
Sexual offender search
All outstanding warrants
Currently the focus of a criminal investigation
Currently on parole or probation
6.34. Maximum Risk Background Check for Child Care Staff Member
A Federal Bureau of Investigation fingerprint check using Next Generation Identification;
A search of the National Crime Information Center’s National Sex Offender Registry; and
A search of the following registries, repositories, or databases in the State where the child care staff member resides and each State where resided during the preceding five years:
State criminal registry or repository, with the use of fingerprints being:
Required in the State where the staff member resides;
Optional in other States;
State sex offender registry or repository; and
State-based child abuse and neglect registry and database.
6.35. Contractor Certification; City Approval of Maximum Risk Background Screening
Unless otherwise provided for in the Scope of Work, Contractor will be responsible for:
determining whether Contract Worker(s) are disqualified from performing work for the City for maximum risk level background checks; and,
submitting pass/fail results to the City for approval; and,
reviewing the results of the background check every three to five years, dependent on scope; and,
to engage in whatever due diligence is necessary to make the decision on whether to disqualify a Contract Worker; and,
Submitting the list of qualified Contract Workers to the contracting department; and,
If, upon review of the background information, the City will advise the Contractor if it believes a Contract Worker should be disqualified. The Contractor will evaluate the Contract Worker and if the Contractor believes that there are extenuating circumstances that suggest that the person should not be disqualified, the Contractor will discuss those circumstances with the contracting department. The contracting department decision on disqualification of a Contract Worker is final.
For sole proprietors, the Contractor must comply with the background check for himself and any business partners, or members or employees who will assist on the contract and for whom the requirements of the Agreement apply.
By executing this agreement, Contractor certifies and warrants that Contractor has read the background screening requirements and criteria in this section, and that all background screening information furnished to the City is accurate and current.
The City final documented decision will be an “approve” or “deny” for identified Contract Workers.
The City will not keep records related to background checks once they are confirmed. Information to verify the results will be returned to the Contractor, or any contracted agency that assists with review, after the City’s completed review.
By executing this agreement, Contractor further certifies and warrants that Contractor has satisfied all such background screening requirements for the maximum risk background screening, and verified legal worker status, as required.
Contract Workers will not apply for the appropriate City of Phoenix identification and access badge or keys until Contractor has received the City’s written acceptance of Contract Worker’s maximum risk background screening. The City may, in its sole discretion, accept or reject any or all the Contract Workers proposed by Contractor for performing work under this Agreement. A Contract Worker rejected for work at a maximum risk level under this agreement will not be proposed to perform work under other city contracts or engagements without city’s prior written approval.
For any childcare or health worker positions, or Criminal Justice Information Systems access in the scope of work, Contractor is required to send the City updated background checks every three years.
The Contractor will submit prior to scheduling any services, a current list of names, addresses, and social security numbers of all employees requiring access to the facility. The Contractor is responsible for obtaining security clearance from the Police Department for all employees. The City reserves the right to change the restricted areas as needed. The Contractor grants the rights to the Police Department to conduct background checks of all employees entering the building. All employees will submit to the background check before access to the facility is given.
The background checks will be conducted prior to any employee entering to work and will be based upon information provided to the Police Department including, but not limited to: name, address, date and place of birth, social security number, INS number if applicable, and a copy of a valid photo identification. The information will be provided to the City’s authorized Department representative at least five business days (excluding weekends and holidays) in advance of the need for access. The form will be provided by the City’s authorized Department representative. The City’s authorized Department representative will conduct the security check.
The City may, at any time, in its sole discretion, refuse to allow an employee access to an area for any of the following reasons, but not limited to:
Conviction of a felony.
Conviction of a misdemeanor (not including traffic or parking violation).
Any outstanding warrants (including traffic and parking violations).
A person currently on parole or probation.
A person currently involved in an investigation.
6.36. 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.37. 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 City at SOC@phoenix.gov without undue delay within 48 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.38. 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.
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.
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 $4,000,000
Products – Completed Operations Aggregate $2,000,000
Personal and Advertising Injury $2,000,000
Each Occurrence $2,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. Automobile Liability
Bodily Injury and Property Damage coverage for any owned, hired, and non-owned vehicles used in the performance of this Contract.
Combined Single Limit (CSL) $1,000,000
The policy must be endorsed to include the City of Phoenix as an additional insured with respect to liability arising out of the activities performed by, or on behalf of the Contractor, relating to this Contract.
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.5. 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.6. Professional Liability (Errors and Omissions Liability)
The policy must cover professional misconduct or lack of ordinary skill for those positions defined in the Scope of Services of this contract.
Each Claim $1,000,000
Annual Aggregate $2,000,000
In the event that the professional liability insurance required by this Contract is written on a claims-made basis, Contractor warrants that any retroactive date under the policy shall precede the effective date of this Contract; and that either continuous coverage will be maintained or an extended discovery 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 City of Phoenix, Public Transit Department, Procurement Section, 302 N. 1st Avenue, 9th Floor, Phoenix, AZ 85003. .
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+: VII 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 City of Phoenix, Public Transit Department, Procurement Section, 302 N. 1st Avenue, 9th Floor, Phoenix, AZ 85003. . The City project/contract number and project description must be noted on the certificate of insurance.
DO NOT SEND CERTIFICATES OF INSURANCE TO THE CITY’S RISK MANAGEMENT DIVISION.
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 via OpenGov Procurement’s Procurement portal. This Offer will remain in effect for a period of 365 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
The City anticipates considerable activity under the resultant contract(s). However, no guarantee can be made as to actual operations control center & data collection services, that will be purchased under this contract. The City reserves the right to add, change or delete quantities or items as circumstances may require.
Note: Offers taking exception to this option for additional quantities clause shall indicate in their offer.
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. Technical Proposal / Evaluation Criteria Responses (WITHOUT PRICING)*
Please upload your responses to Section 4. Offer Evaluation Criteria, including your firm's cover page.
Please DO NOT include any pricing information in your responses to the evaluation criteria. Offers shall only submit pricing information electronically in Section 11 Pricing Proposal.
*Response required
2. 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
3. Prompt Payment Discount
______% - 30 days or 0% – 45 days
If none is specified, the City will default to 0% - net 45 days.
4. Emergency 24-Hour Service Contact*
Please provide a full contact name, telephone number, alternate contact, and their phone number.
*Response required
5. References*
Please download the below documents, complete, and upload.
References.pdf
*Response required
6. 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
7. 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
8. Do you have any confidential information you would like to include with your response?*
Yes
No
*Response required
When equals "Yes"
8.1. Please upload any confidential information here*
Clearly label the uploaded file
*Response required
When equals "Yes"
8.1. Please upload any exceptions you have*
Clearly label the uploaded file
*Response required
9. 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
10. 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
11. 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. Pricing Proposal
Operations Control Center
Export This Table
Line Item
Description
Quantity
Unit of Measure
Unit Cost
Total
1
Year One (FY27-28) Total Annual Cost for Operations Control Center Services
1
Year
2
Year Two (FY28-29) Total Annual Cost for Operations Control Center Services
1
Year
3
Year Three (FY29-30) Total Annual Cost for Operations Control Center Services
1
Year
4
Year Four (FY30-31) Total Annual Cost for Operations Control Center Services
1
Year
5
Year Five (FY31-32) Total Annual Cost for Operations Control Center Services
1
Year
6
Year Six (FY32-33) Total Annual Cost for Operations Control Center Services
1
Year
7
Year Seven (FY33-34) Total Annual Cost for Operations Control Center Services
1
Year
Total
$0.00
Columns
Data Collection Services
Export This Table
Line Item
Description
Quantity
Unit of Measure
Unit Cost
Total
1
Year One (FY27-28) Total Annual Cost for Data Collection Services
1
Year
2
Year Two (FY28-29) Total Annual Cost for Data Collection Services
1
Year
3
Year Three (FY29-30) Total Annual Cost for Data Collection Services
1
Year
4
Year Four (FY30-31) Total Annual Cost for Data Collection Services
1
Year
5
Year Five (FY31-32) Total Annual Cost for Data Collection Services
1
Year
6
Year Six (FY32-33) Total Annual Cost for Data Collection Services
1
Year
7
Year Seven (FY33-34) Total Annual Cost for Data Collection Services
1
Year
Total
$0.00
Columns
Annual Cost Per Additional Controller
Export This Table
Line Item
Description
Quantity
Unit of Measure
Unit Cost
Total
1
Year One (FY27-28) Total Annual Cost for Each Additional Controller
1
Year
2
Year Two (FY28-29) Total Annual Cost for Each Additional Controller
1
Year
3
Year Three (FY29-30) Total Annual Cost for Each Additional Controller
1
Year
4
Year Four (FY30-31) Total Annual Cost for Each Additional Controller
1
Year
5
Year Five (FY31-32) Total Annual Cost for Each Additional Controller
1
Year
6
Year Six (FY32-33) Total Annual Cost for Each Additional Controller
1
Year
7
Year Seven (FY33-34) Total Annual Cost for Each Additional Controller
1
Year
Total
$0.00
Columns
12. Attachments
A - Exhibit A - Incumbent OCC Job Descriptions & Wages
B - Exhibit B - OCC Site Plan
C - Exhibit C - OCC Warm Site Plan
D - Exhibit - D - Facility Incident-Repair Request Procedure 04.22.26
E - Exhibit E - Technical Requirements
F - Exhibit F - A.R. 4.45 Contract Worker Background Checks
G - Exhibit G - Security Access & Control
H - Exhibit H - A.R. 2.324 Substance Abuse Policy
