Physical_Security_Event_Monitoring_System.pdf

PDF 549 KB Posted

Attached to
Physical Security Event Monitoring System
Solicitation number
RFP GGS-27-0439
Issued by
Maricopa County, Phoenix City, Arizona

About this file

Physical Security Event Monitoring System - Request for Proposal Summary

This is a Request for Proposal (RFP GGS-27-0439) issued by the City of Phoenix Water Services Department for integrator services to replace the legacy Physical Security Event Monitoring System (PSEMS). The City seeks a contractor to provide labor for software installation and upgrades, system component installation and replacement, preventative maintenance inspections (PMI), and equipment repair. The solicitation was released on November 13, 2026, with a non-mandatory pre-offer conference scheduled for November 20, 2026 at 10:00 AM via Webex. Written inquiries are due by December 4, 2026 at 2:00 PM, and sealed offers must be submitted by December 21, 2026 at 2:00 PM through the City's OpenGov Procurement Portal. The contract term is five years beginning on March 31, 2027 (or upon Phoenix City Council approval, whichever is later), with no options to extend. The agreement will terminate upon reaching the end of the term or through termination provisions outlined in the contract.

The evaluation criteria include Experience and Capability (480 points), Method of Approach (475 points), and Pricing Proposal (106 points). All offers must remain firm and fixed for 180 calendar days from the solicitation opening date. The contractor must demonstrate stable ownership and core staffing for at least five years, maintain continuous experience providing electronic security system services, and hold Certified Integrator Certification for Software House CCURE 9000 software and hardware. Key personnel must have at least five years of continuous experience in electronic security systems, with designated technicians holding CCURE Installer/Maintainer training and certification. The contractor is responsible for all labor costs, equipment, tools, vehicles, permitting, and emergency response (initial response within 30 minutes, onsite within two hours). The City will not reimburse travel time, mileage, or per diem costs, which must be included in hourly labor rates. Certificate of insurance in minimum required amounts must be submitted within 14 calendar days of award notification. No specific dollar funding amount is identified in the solicitation, as pricing will be evaluated as part of the competitive process.

View the file

Other files

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

REQUEST FOR PROPOSAL - GOODS AND SERVICES

RFP GGS-27-0439

PHYSICAL SECURITY EVENT MONITORING SYSTEM

CITY OF PHOENIX

WATER SERVICES

200 W. WASHINGTON

PHOENIX, AZ

85003

RELEASE DATE: November 13, 2026

DEADLINE FOR QUESTIONS: December 4, 2026

RESPONSE DEADLINE: December 21, 2026, 2:00 pm

City of Phoenix

REQUEST FOR PROPOSAL - GOODS AND SERVICES

RFP GGS-27-0439

Physical Security Event Monitoring System

1. INTRODUCTION

2. INSTRUCTIONS

3. SCOPE OF WORK

4. EVALUATION PROCESS

5. STANDARD TERMS AND CONDITIONS

6. SPECIAL TERMS AND CONDITIONS

7. DEFENSE AND INDEMNIFICATION

8. INSURANCE REQUIREMENTS

9. SUBMITTALS

10. PRICING PROPOSAL

Attachments:

A - Acceptance of Offer Form 2026

B - Exhibit 1 MOP

Request For Proposal - Goods and Services #RFP GGS-27-0439 Title: Physical Security Event Monitoring System

1. Introduction

1.1. Contact Information

Jennifer Nieschulz

Water Services

Email: jennifer.nieschulz@phoenix.gov

Phone: (602) 256-4317

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 (Jennifer Nieschulz) at (602) 256-4317/Voice or 711/TTY, or jennifer.nieschulz@phoenix.gov, no later than five (5) business days prior to the meeting.

Solicitation Issue Date: November 13, 2026

Pre-Offer Conference (Non-Mandatory): November 20, 2026, 10:00am

When it's time, join your Webex meeting here.

Join meeting

More ways to join:

Join from the meeting link https://cityofphoenix.webex.com/cityofphoen ix/j.php?MTID=md3b8f905b679aef2262bdb ba01e1e6d4

Join by meeting number

Meeting number (access code): 2337 233

Meeting password: 4XdzRPuFC77

Tap to join from a mobile device (attendees only)

+1-415-655-0001,,23372334969## US Toll

Need help? Go to https://help.webex.com https://cityofphoenix.webex.com/cityofphoenix/j.php?MTID=md3b8f905b679aef2262bdbba01e1e6d4 https://cityofphoenix.webex.com/cityofphoenix/j.php?MTID=md3b8f905b679aef2262bdbba01e1e6d4 https://cityofphoenix.webex.com/cityofphoenix/j.php?MTID=md3b8f905b679aef2262bdbba01e1e6d4 https://help.webex.com/

Written Inquiries Due Date: December 4, 2026, 2:00pm

Offer Due Date: December 21, 2026, 2:00pm

2. Instructions

2.1. Description – Statement of Need

The City of Phoenix invites sealed offers for a Contractor to perform integrator services for the replacement Physical Event Monitoring System (PSEM) application. The selected contractor will provide labor to install and upgrade software, install and replace system components, provide

Preventative Maintenance Inspections (PMI) and repair faulty equipment..

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 upon March 31, 2027, which is on or after the ordinance approved start date or the contract term start date that the Phoenix City

Council approves or the Effective Date, whichever is later.

The term of this Agreement will be for 5 years, beginning on the Commencement Date, with no options to extend.

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:

A. Consider applicable laws and/or economic conditions that may affect cost, progress, performance, or furnishing of the products or services.

B. Study and carefully correlate Offeror’s knowledge and observations with the solicitation and other related data.

mailto:procurement-support@opengov.com

C. Promptly notify the City of all conflicts, errors, ambiguities, or discrepancies that Offeror has discovered in or between the solicitation and other related documents.

D. 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.

E. 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.

F. 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.

G. 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.

H. Offeror shall limit its narrative response to no more than twenty (20) pages, excluding cover letter, reference questionnaires, manufacturer price lists and/or catalogs, Pre-Award qualification documents, and resumes.

2.3. Fixed Offer Price Period

All offers shall be firm and fixed for a period of 180 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/292910/. 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 https://procurement.opengov.com/portal/phoenix/projects/292910 https://solicitations.phoenix.gov/ 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/292910. 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 on the offer due date, time and location 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/292910 within five business days of the offer opening. The City will post the information on the preliminary tabulation as it https://procurement.opengov.com/portal/phoenix/projects/292910 https://procurement.opengov.com/signup https://opengov.my.site.com/support/s/article/ca6d1285-1e48-4a21-bb0d-715edb7794ed https://opengov.my.site.com/support/s/article/ca6d1285-1e48-4a21-bb0d-715edb7794ed https://procurement.opengov.com/portal/phoenix/projects/292910 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

Pre-award qualifications must be demonstrated by key personnel resumes, references, and responses to the questions in the Vendor Questionnaire section of this solicitation.

Offeror shall:

A. Demonstrate stable ownership and core staffing for at least five (5) years and disclose any mergers, acquisitions, or organizational changes that may affect key personnel or business processes represented in the proposal.

B. Demonstrate normal activity during the past five (5) years which includes continuous experience providing electronic security system services.

C. Demonstrate Certified Integrator Certification for proposed Software House software and hardware.

2.15. Data Privacy Risk Screening

Because the resulting Contract may involve processing personal or other sensitive data, the City will conduct a Data Privacy Risk Screening as a minimum qualification using the Data Privacy

Questionnaire included in the Vendor Questionnaire section. Only Offerors that pass this screening will proceed to further evaluation.

Failure to submit the Data Privacy Questionnaire, or failure to meet the minimum standard, will result in the Offer being deemed non-responsive.

The City may verify statements, request clarifications regarding the Data Privacy Questionnaire or supporting documents and reject Offers that contain misrepresentations.

2.16. 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.17. 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.

A. Factors that may be considered by the City include:

1. 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,

2. Demonstrated availability of the necessary manpower (both supervisory and operational personnel) and necessary equipment to accomplish the scope of work in the Solicitation; and,

3. Safety record; and,

4. Offeror history of complaints and termination for convenience or cause.

B. 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.

C. 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.18. 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.19. 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.20. 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.21. 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.22. 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.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. 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.26. 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.27. Detailed Evaluation of Offers and Determination of Competitive Range

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.28. Offers Not Within the Competitive Range

The City may notify Offerors of Offers that the City determined are not in the Competitive

Range.

2.29. 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.30. 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. Purpose

The City of Phoenix (City) Water Services Department (WSD) is seeking a contractor to perform integrator services for the replacement of the legacy Physical Security Event Monitoring System

(PSEMS), which has reached-end-of life and is no longer supported. The new PSEM will deliver enhanced functionality, improved management of access rights, and greater visibility of site access and event monitoring. The selected contractor will:

A. Provide the labor to install and upgrade software

B. Install and replace system components

C. Provide preventative maintenance inspections and repair faulty equipment

D. Complete component replacement and system deployment in a live operational environment.

To ensure minimal disruptions to ongoing operations, the selected Contractor must work collaboratively with the Water Services Process Control Technology Services (PCTS) division and site owners. This coordination is essential for managing any impacts to existing access configurations and ensuring continuity of operations throughout the duration of the services.

3.2. Background

A. WSD utilizes and maintains a Physical Security Event Monitoring System (PSEMS) application to physically control and provide secure access to water, wastewater, and remote facilities to all City WSD facilities within Maricopa County.

B. WSD’s standard PSEMS platform is Software House C•CURE 9000. While the majority of sites are already migrated, several sites still require migration to achieve full standardization.

C. The PSEMS includes software and equipment, such as badging workstations, application servers, card readers, and access controllers utilized to ensure the security of key sensitive areas and their assets.

D. Securing the sites ensures WSD meets regulatory performance requirements, in compliance with federal, state and local regulations.

E. Improper maintenance and system support can result in unauthorized site access with the potential of system process interruptions to prevent WSD from providing safe and reliable services to its customers.

3.3. Definitions/Acronyms

A. DSM – Door Switch Monitor

B. Normal Business Hours - Monday through Friday from 6 AM – 6PM

C. PCTS - Process Control Technology Services

D. PMI – Preventative Maintenance Inspections

E. Premium Hours – All other times outside of normal business hours. Premium hourly rate includes evenings, weekends and all City of Phoenix observed holidays. Premium hours must be approved by PCTS staff prior to work being performed. Failure to obtain

PCTS staff approval may result in a delay of payment.

F. PSEMS – Physical Security Event Monitoring System

G. Reimbursable labor hour(s) – begin when the technician arrives at the designated sign in location and terminate when the technician signs out at the designated location.

H. REX – Request to exit

I. Site Method of Procedure (MOP) – Document submitted by Contractor prior to execution to include: pre checks, a cutover plan, and a rollback procedure; City approval required prior to execution.

J. WSD – Water Services Department

3.4. Contractor General Requirements

The Contractor shall perform the following services and responsibilities:

A. On-Site Installation Services

Provide on-site services to install controllers, PSEMS security components, and any other material necessary to support and ensure the security of WSD site.

B. PSEM Component Expertise

Have the knowledge and ability to install, replace, and convert PSEMS components.

C. System and Software Support

Provide labor to install and upgrade software, install and replace system components, perform preventative maintenance, and repair faulty equipment as needed.

D. Permitting

Obtain all required permits necessary to perform the work

E. Engineering Documentation

Provide engineering documentation for point-to-point wiring diagrams, submittal materials, and Input/Output (I/O) summary for all installed equipment and services.

Documentation must be delivered in both hard copy and digital formats.

F. Emergency Service Response Requirements

1. Upon initial notification by PCTS staff, Contractor's initial response must be (via telephone or email) within 30 minutes.

2. Provide onsite physical presence within two (2) hours of initial notification.

G. Quotes and Project Estimates

1. Furnish an itemized quote or project estimate within three (3) business days of each site assessment or initial request from PCTS staff. At a minimum, quotes shall include:

a. Estimated project completion date

b. Estimated labor hours

c. Material costs, including licensing requirements

d. Removal of existing equipment

e. Site clean up

f. Initial visit, commissioning and final site visits to complete the installation and integration of PSEMS hardware and software

g. Permit fees, if applicable

h. Rental equipment estimated cost in accordance with subsection 3.10, if applicable.

i. Note: Travel time to and from job site will not be reimbursable. All mileage, travel costs, and per diem, must be included in the hourly labor rate.

2. Obtain approval from PCTS staff prior to commencement of any work or project

a. Proceed upon receipt of a Purchase Order (PO) for standard scheduled work.

b. For emergency repairs, obtain verbal approval to expedite service; PCTS staff will issue a PO as soon as it is practical.

H. Equipment Installation and Coordination

1. Provide installation services for City owned equipment or install new equipment as requested by PCTS staff.

2. Relocate or remove equipment as directed. All removed equipment will remain the

City's property and must be returned to the City within five (5) business days after completion of the service

3. Coordinate with PCTS staff to obtain device configuration information prior to installation. Upon completing device installations, contact PCTS staff for final walk through inspection and obtain project approval prior to submitting an invoice for payment processing.

4. Correct any work performance and deliverables the City deems unsatisfactory upon receiving the City's notification. All deficient work must be fully corrected within twenty-four (24) hours of the City's notice and completed at no additional cost to the

City.

5. Complete the work within the agreed upon timeframe.

6. Perform component replacement and system deployment with a live operational environment.

3.5. Contractor Business Requirements

The Contractor shall meet the following business requirements:

A. Organizational Stability

Demonstrate stable ownership and core staffing for at least five (5) years and disclose any mergers, acquisitions, or organizational changes that may affect key personnel or business processes represented in the proposal.

B. Business Activity

Demonstrate normal business activity during the past five (5) years which includes continuous experience providing electronic security system services.

C. Certified Integrator Status

Be a certified integrator of the proposed Software House software and hardware

Security System product(s) and be eligible for the City to request Contractor inclusion as the Software House approved dealer of record.

3.6. Contractor Key Personnel Requirements

The Contractor shall comply with the following personnel requirements:

A. Primary Service Representative

Assign a service representative who will be the primary contact under this Contract and who has complete authority to act on behalf of the Contractor. The assigned service representative or designee must be available 24 hours a day, seven (7) days a week including holidays, to support emergency needs.

B. Experience Requirements for Key Personnel

Ensure Key Personnel have at least five (5) years of continuous, documented experience providing electronic security system services including design, installation, integration, and maintenance.

C. Technical Certification

Designate Key Personnel who have completed C•CURE Installer/Maintainer training and certification for validation and commissioning of each deployment.

D. Technician Experience Oversight

Assign Key Personnel who will ensure that assigned technicians possess a minimum of one (1) year experience installing, maintaining, and supporting electronic security systems such as access control and intrusion detection. Experience must include projects of comparable size, complexity, and environment (e.g., multi-site, high security, mission-critical systems).

E. Supervision of Non-Certified Technicians

Ensure that installer technicians who do not hold manufacturer certification or licenses follow industry best practices under the guidance of Key Personnel.

F. Safety and Licensing Compliance

Ensure technicians maintain a current OSHA-10 minimum or equivalent safety training certificate and any required local and state licenses.

G. Background Check Compliance

Verify and document technician background check compliance prior to assigning any technicians to City sites and Contractor shall provide confirmation of clearance to the

City upon request.

H. Authorization for Subcontracted Services

Obtain written authorization from PCTS staff before subcontracting or engaging any third parties to perform services under the resultant Contract.

I. Contractor Responsibility for Subcontractors

Contractor’s use of any subcontractors or third parties to perform services and provide technical knowledge does not relieve, release, or affect contractors’ duties, liabilities or obligations, and Contractor shall remain fully liable.

J. Coordination of Site Access

Coordinate with PCTS staff to provide subcontractor information to Security

Management Unit (SMU) for access to City Sites without badging. NOTE:

Subcontractor(s) shall be escorted by City staff, not the contractor.

K. Personnel Sign-In Requirements

Ensure all contractor personnel sign in and out at each visit, including when leaving the premises for supplies, meals, breaks, etc. Contractor may use the City’s approved time management system to document when they arrive on the job site to begin service work and when they leave the job site. The Contractor can use their own inhouse “time clock” system and provide weekly attendance reports to the City, if applicable.

L. Time Documentation for Invoicing

Ensure that upon arrival, and before beginning any work on the premises, personnel record their start and finish times and submit documentation with the invoice for each project.

M. Emergency Service Arrival Notification

Ensure personnel signs in and out for all services. Failure to comply may result in delays or non-payment of services. For emergency services, the contractor shall contact PCTS staff when they arrive onsite and when work is complete.

3.7. Application Technical Requirements

The Following technical requirements outline the necessary system architecture, security protocols, and operational standards for the implementation and management of the new

PSEMS application. These specifications are designed to ensure the solution operates securely within the City’s PCTS Security Network, aligns with industry best practices, and supports the

City’s long-term operational and security objectives.

A. Architecture

1. There shall be no remote connection or internet access from the secured PCTS

Security Network.

2. All PSEMS databases and application management shall be housed on-site on the

PCTS isolated Security Network as an on-premise deployment.

3. All system upgrades, updates, and licensing shall be done through offline activation with the collaboration of PCTS Physical Security team.

4. Software version updates within the same model or series (e.g., minor and incremental model/version releases that do not constitute a major product migration) shall be included in the software cost at no additional charge to the City.

5. The Contractor shall integrate the remaining sites into the City’s existing on prem

C•CURE 9000 “R” environment, matching the City approved build/hotfix and controller/reader standards.

6. Future migration options may be exercised only upon written City authorization/amendment.

B. Security

1. Comply with laptop check out and check in process with PCTS staff member at the beginning and end of the workday.

2. Ensure checked-out laptops remain on-site during off hours including weekends and holidays.

3. Adhere to relevant industry standards and best practices applicable to the project domain, including but not limited to:

a. OSHA (Occupational Safety and Health Administration) Regulations

b. NIST (National Institute of Standards and Technology) Cybersecurity Framework

c. ISA (International Society of Automation) Standards for Industrial Automation

d. American Society of Civil Engineers (ASCE)/American Water Works Association

(AWWA)

1. Adhere to guidelines for the Physical Security of Water Utilities security requirements to protect sensitive information, data, and systems from unauthorized access, disclosure, or manipulation.

2. Ensure security measures align with industry best practices and standards, including encryption, access controls, intrusion detection, and incident response protocols.

3. Adhere to PCTS documentation securing protocols utilizing the Cybersecurity Traffic

Light Protocol, for securing critical information within the PCTS network.

3.8. Training Requirements

The Contractor shall coordinate both initial and ongoing training to support PSEMS provisioning and deployment. At a minimum, the training will include:

A. Coordinate In-Person Training

1. Subcontract with Software House to deliver the City approved C•CURE courses listed Attachment B - Pricing Proposal at two (2) WSD sites designated by City Staff.

2. Be responsible for scheduling, coordinating rosters and facilities, and billing.

3. Bill course fees at actual cost with no markup.

4. Coordinate manufacturer-provided C•CURE initial and ongoing training to support

PSEMS provisioning and deployment.

B. Coordinate Training Documentation

1. Coordinate written content from Software House for use as reference guides to assist City of Phoenix PCTS staff to manage day-to-day operations. The required content shall be provided in draft form for review and approval by PCTS

Infrastructure and Physical Security Supervisor.

2. Any revisions requested by PCTS shall be incorporated by the Contractor at no additional cost.

3.9. Preventative Maintenance Inspection Requirements

The Contractor shall conduct Preventative Maintenance Inspections (PMI) as identified and requested by the PCTS Infrastructure and Physical Security Supervisor. PMI includes physically visiting each site access control enclosure and performing the following:

A. Preventative Maintenance Inspection Activities

1. Replace batteries

2. Test battery charger output power

3. Remove dust/debris from internal enclosure

4. Check for loose termination/connections and tighten, as needed

5. Operate site and test alarm output signals

6. Check environmental wear and tear

7. Provide a finding report with recommended action items.

3.10. Specialized Equipment

The Contractor shall comply with the following requirements related to tools, equipment, and specialized rental items:

A. Standard Equipment Provision

Provide the tools, equipment, and vehicles standard to the trade at no additional cost to the City.

B. Rental of Specialized Equipment

Rent any special equipment, including lifts or scaffolding, as necessary to perform the work specified in the Scope of Work or any services requested by the City.

C. Prior Approval for Rentals

Obtain prior written approval from PCTS staff before renting any specialized equipment required to complete the job.

D. Rental Quote Submittals

Submit a minimum of three (3) rental quotes for any specialized equipment to PCTS staff for review and approval.

E. Rental Cost Reimbursement

Reimbursement for equipment rental will be for the actual cost to the contractor.

Documentation of the cost must be included with the final invoice, and no mark-up will be permitted. The City will not accept any invoice that has been altered in any manner.

F. Temporary On-Site Storage

Specialized equipment may be stored temporarily on-site if PCTS staff is able to coordinate a storage location/space. During the temporary storage on-site, the City is not responsible for lost, stolen or damaged equipment. It is the responsibility of the

Contractor to secure this equipment.

G. Equipment Purchased on behalf of the City

Purchase equipment inventory such as spare parts and equipment on behalf of the City for various project needs, as requested by the City.

3.11. Milestones, Deliverables, and Acceptance

The Contractor shall meet the following requirements related to quality, safety, deliverables and acceptance:

A. Quality of Work

Provide work of the highest quality, meeting or exceeding the standards and specifications outlined in the project requirements and agreements.

B. Defect-Free Deliverables

Ensure work is free from defects, errors, and deficiencies that may impact on the functionality, reliability, or safety of the deliverables.

C. Safety Compliance

Implement and maintain safety measures throughout the project to protect the health and well-being of workers and stakeholders.

D. Required Milestones and Acceptance Activities

1. Site Method of Procedure (MOP)

For each site, Contractor shall submit a MOP (see Exhibit 1 for sample) with pre-checks, a cutover plan, and a rollback procedure; City approval required prior…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .