Base_Agreement.pdf

PDF 241 KB Posted

Attached to
Eclypsium / Smart Compliance Active Firmware Scanning Software
Solicitation number
IFB- 25 - 082
Issued by
Pinellas County, Florida

About this file

This document is a Technology Purchase Agreement between the City of St. Petersburg, Florida and an unnamed contractor for the purchase of technology-related goods, services, or intellectual property rights. The agreement establishes the framework for procuring technology deliverables, with components including a Standard Technology Addendum and potentially other city-produced documents, contractor proposals, scopes of work, and standard terms and conditions. The agreement will continue in effect until the end of its established term, with potential for renewal, and can be terminated earlier according to its provisions.

The agreement includes comprehensive provisions covering intellectual property rights, data security, insurance requirements, and indemnification. The contractor is required to carry multiple types of insurance, including commercial general liability (minimum $1,000,000 per occurrence), cyber liability insurance (minimum $1,000,000 per occurrence), and workers' compensation insurance. The document emphasizes strict standards for data protection, security issue reporting, and compliance with Florida public records laws. The City of St. Petersburg reserves the right to budget and appropriate funds annually, with no guarantee of continued funding beyond the current fiscal year, and maintains sovereign immunity limitations on potential liability.

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

AT-01 / 00614644 / v18 1 of 4

CITY OF ST. PETERSBURG

TECHNOLOGY PURCHASE AGREEMENT

This technology purchase agreement (as may be amended from time-to-time, the “Agree-ment”) is made between the City of St. Petersburg, a Florida municipal corporation, (the “City”) and [] (the “Contractor”) for the purchase of certain technology-related goods, services, or intel-lectual property rights (each a “Deliverable”).

1. Components of Agreement. The Agreement consists of this document and the documents listed below, each of which is attached to this Agreement as an exhibit (unless otherwise noted as being incorporated by reference):

(a) City of St. Petersburg Standard Technology Addendum (the “Addendum”).

(b) [any City-produced documents (scope of work, requirements, etc.)]

(c) The following Contractor or third-party documents (each, an “External Document”):

(i) [proposal / quote]

(ii) [Contractor-written scope of work]

(iii) [Contractor standard terms and conditions]

(iv) [Any other Contractor or third-party document]

2. Effective date; term. The Agreement is effective when this document has been signed by all parties. If the date established for Contractor’s initial performance predates the date on which this document is signed by all parties, the Agreement is effective retroactive to the date of the Contractor’s initial performance, and that date of that initial performance is deemed the effective date of the Agreement. Otherwise, the date on which the last party signs this document is deemed the effective date of the Agreement. The Agreement will continue in effect until the end of the term established by or pursuant to the Agreement unless (i) terminated on an earlier date in ac-cordance with the Agreement or (ii) renewed in accordance with the terms of the Agreement.

3. Conflict. In the event of a conflict between any documents comprising the Agreement, a document listed higher in section 1 will control over a document that is listed lower, and if there is a conflict between any documents listed at the same level in section 1 (e.g., two External Docu-ments), a later document will control over an earlier document, and a document specific to this transaction will control over a document that is general in nature.

AT-01 / 00614644 / v18 2 of 4

4. Entire Agreement. The Agreement constitutes the entire agreement between the parties with respect to its subject matter, and it supersedes any previous representation, proposal, or agree-ment as to its subject matter, whether oral or written.

5. Execution. Any component of the Agreement may be signed in any number of counter-parts, each of which is deemed to be an original, and such counterparts collectively constitute a single original copy of the Agreement. Additionally, each party is authorized to sign any compo-nent of the Agreement electronically using any method authorized by applicable law and City policy. If a party signs the Agreement but fails to date its signature, the date the City receives the signing party's signature will be deemed to be the date the signing party signed the Agreement.

[SIGNATURE PAGES FOLLOW]

AT-01 / 00614644 / v18 3 of 4

Each party is signing this document on the date stated adjacent to that party’s signature.

Date: ________________________

CITY OF ST. PETERSBURG, FLORIDA

By: _________________________________

Name: _________________________________

Title: _________________________________

ATTEST

Chandrahasa Srinivasa, City Clerk

(SEAL)

Approved as to Content and Form

City Attorney (Designee)

[ADDITIONAL SIGNATURE PAGE FOLLOWS]

AT-01 / 00614644 / v18 4 of 4

Date: ________________________

[ACME WIDGET CO.]

By: _________________________________

Name: _________________________________

Title: _________________________________

AT-01 / 00614644 / v18 1 of 10

CITY OF ST. PETERSBURG

STANDARD TECHNOLOGY ADDENDUM

This City of St. Petersburg Standard Technology Addendum (the “Addendum”) addresses certain contractual terms required by Florida law, City Code, or City policy, as follows:

1. Incorporated Terms. For purposes of this Addendum, the following defined terms are incorporated by reference from the document to which this Addendum is attached or incorporated:

“Agreement,” “City,” “Contractor,” and “Deliverable.”

2. City Forms. The City may issue standard-form documents for the purpose of exercising its rights under the Agreement (each a “City Form”) in accordance with the following:

(a) The City may issue any number of City Forms, alone or in combination, to exercise any right available to it under the Agreement (e.g., purchasing a Deliverable or renewing or extending the Agreement), and a City Form is subject to the terms of the Agreement re-gardless of whether that City Form expressly incorporates or refers to the Agreement.

(b) A City Form may take the form of a blanket purchase agreement, contract purchase agree-ment, purchase order, or any other standard-form document issued by or through a City administrative system or procedure, and it includes any document that is attached or incor-porated by reference (e.g., a Contractor proposal with descriptions and fees for the specific Deliverables being purchased through that City Form).

(c) The following provisions in a City Form are void: (i) any provision that is inconsistent with the Addendum and (ii) any provision that would incorporate new terms and conditions through a URL. Otherwise, any provision in a City Form that is inconsistent with the Agree-ment is effective only with respect to that City Form.

3. Notice. Any notice to the City under the Agreement must be delivered in writing to a phys-ical or electronic address explicitly designated in writing by the City for that purpose, and the City may modify such designation from time to time. The City’s initial designation for such notice is City of St. Petersburg, Procurement and Supply Management Department, ATTN: Director, P. O.

Box 2842, St. Petersburg, FL 33731.

4. Invoicing and payment. This City is obligated to pay the Contractor for performance un-der the Agreement only if the Contractor has submitted an invoice in accordance with the City’s procedures for submission of such an invoice, and the City must be provided with at least 45 days to make payment under each invoice. Additionally, if the Contractor has not satisfied all require-ments of the Agreement at the time an invoice is submitted, the City may withhold payment on that invoice until such date as the Contractor has satisfied all requirements of the Agreement and

AT-01 / 00614644 / v18 2 of 10 has submitted a new invoice that demonstrates correction of each deficiency to the City’s satisfac-tion. During any period in which the City withholds payment pursuant to this section 4, the Contractor shall not terminate, suspend, impair, degrade, or otherwise limit any service or right provided to the City pursuant to the Agreement.

5. Renewal terms. The term of the Agreement may be renewed or extended for an additional period of time (each a “Renewal Term”) only if the City provides written consent to the Renewal Term. Accordingly, any “automatic” renewal or extension of the Agreement that would purport to occur without written consent of the City is void. If a City Form is issued with the intent of con-tinuing the relationship between the parties under the terms of the Agreement, that City Form is effective as written consent to a Renewal Term pursuant to this section, even if it does expressly state that it is a “renewal” or “extension” of the Agreement. Accordingly, at the beginning of each Renewal Term, the Agreement will continue on the same terms that were in effect at the conclusion of the immediately preceding term unless the parties provide express written agreement to amend the terms in conjunction with the issuance of that City Form.

6. Intellectual property rights. For purposes of the Agreement, “Intellectual Property” in-cludes any copyright, patent right, trademark, trade secret, or other form of intellectual property, regardless of jurisdiction, along with any application, registration, or renewal for any of the fore-going, regardless of jurisdiction. If the Contractor, pursuant to the Agreement, grants, transfers, sublicenses, assigns, or otherwise conveys to the City any license, sublicense, or other right pur-suant to which the City may access or use any Deliverable that constitutes or contains Intellectual Property (each a “Licensed Deliverable”), the following provisions apply:

(a) Subject only to a limit on the number of authorized users explicitly stated in the Agreement, any officer, employee, agent, contractor, subcontractor, elected or appointed official, or volunteer of the City has the non-exclusive, right and license to use a Licensed Deliverable in the course of any lawful business or function of the City without the payment of any royalty or fee other than as explicitly stated in the Agreement and without geographic lim-itation, subject only to those limitations imposed by law or explicitly stated in this Agreement.

(b) The City may copy any Licensed Deliverable for archival backup, disaster-recovery, or other internal purposes. Such internal purposes include installation of software Deliverable in non-production environments for testing and configuration purposes. But unless explic-itly authorized by the Agreement, the City shall not intentionally (i) remove or modify any markings or notice of the Contractor’s proprietary rights to the Licensed Deliverable or

(ii) copy, reverse engineer, disassemble, or decompile a Licensed Deliverable that is soft-ware.

AT-01 / 00614644 / v18 3 of 10

(c) The owner of any Licensed Deliverable, whether the Contractor or a third party, retains exclusive ownership of all Intellectual Property contained in that Licensed Deliverable un-less otherwise provided for in a document that explicitly transfers ownership of that Licensed Deliverable in whole or in part to the City.

7. City information. With respect to any information, data, or other content that is provided to the Contractor in connection with the Agreement or that is uploaded, submitted, posted, trans-ferred, transmitted, stored, or otherwise made available to or through any Deliverable that is a technology system (collectively “City Information”), the Contractor shall use City Information only for the purposes described in the Agreement, and the Contractor acknowledges that the City does not transfer any right of ownership of City Information to the Contractor or to any third party through the City’s execution or performance of the Agreement. Furthermore, the Contractor shall not disclose any City Information that is marked or explicitly designated as “confidential” or “pro-prietary” unless explicitly authorized in writing by the City or required by law. This section 7 survives termination of the Agreement.

8. Redundancy, data backup, and disaster recovery. If no Deliverable is “cloud-based” software provided to the City through the internet (“Hosted Software”), this section 8 is void and of no effect. Otherwise, the Contractor shall, in accordance with the provisions of this section 8, maintain disaster-avoidance procedures designed to safeguard and maintain access to City Infor-mation and the capability and availability of the Hosted Software. The force majeure provisions of the Agreement do not limit Contractor’s obligations under this Section 8.

(a) The Contractor shall ensure that the primary system from which the Hosted Software is provided is located in the contiguous United States.

(b) The Contractor shall simultaneously operate a mirror system for the Hosted Software at a hardened data center facility in the contiguous United States that is geographically remote from the primary system from which the Hosted Software is provided (the “Secondary Backup Facility”). Except for its location and housing facility, the mirror system shall:

(i) be identical in all respects to the primary system; (ii) have hardware and software, net-work connectivity, power supplies, backup generators, and other similar equipment and services that operate independently of the primary system; (iii) have fully current backups of all City Information stored on the primary system; and (iv) have the ability to provide the Hosted Software is in accordance with the Agreement during the performance of rou-tine and remedial maintenance or any outage or failure of the primary system. The Contractor shall operate, monitor, and maintain such mirror system so that it may be acti-vated within one minute of any failure of the primary system.

AT-01 / 00614644 / v18 4 of 10

(c) Unless otherwise explicitly stated in the Agreement, there is no limit on the amount of City Information that may be stored in the Hosted Software, and the City’s payment under the Agreement covers all storage of City Information in the Hosted Software. The Contractor shall conduct backups of City Information at least every four hours and store such backup City Information in a location and manner that is consistent with industry best practices.

Unless otherwise explicitly stated in the Agreement, the Contractor shall not count any such backup of City Information in allotting or calculating any data storage actually used or permitted to be used by City or any associated fee.

(d) The Contractor shall maintain a business continuity and disaster-recovery plan for the Hosted Software (the “BCDR Plan”) and provide the City, upon request, with a current copy of the BCDR Plan, along with any reports or summaries relating to past testing of or pursuant to the BCDR Plan. Additionally, the Contractor shall actively test, review and update the BCDR Plan on at least an annual basis using industry best practices as guidance, and any such update to the BCDR Plan is be subject to the requirements of this subsec-tion (d). In the event of any unplanned interruption of access to the Hosted Software, the Contractor shall implement the BCDR Plan. And if the Contractor fails to restore access to the Hosted Software is within the period of time set forth in the BCDR Plan, the City may, in addition to any other remedies available hereunder, in its sole discretion, immediately terminate the Agreement.

(e) If the City requests a comprehensive export of all City Information stored in the Hosted Software, the Contractor shall provide such export no more than ten days after receiving such request. If that City Information is stored in its native format (e.g., Word, Excel, Pow-erPoint, PDF, etc.), it must be exported in that native format. Otherwise, that City Information must be exported in Excel, comma-separated values, or other agreed-upon for-mat. If any City Information is stored in a database and exported in table format, the Contractor shall provide the City with the database schema for those tables within ten days of request by the City. This subsection (e) survives for 90 days following expiration or earlier termination of the Agreement.

9. Security issues. If the Contractor has actual or constructive knowledge of any potential or actual vulnerability, security breach, or unauthorized access to any Deliverable; to any software or technology system provided, maintained, or supported by the Contractor; or to any City Infor-mation stored in or processed by such Deliverable, software, or technology system (each, a “Security Issue”), the following provisions apply:

(a) The Contractor shall report the Security Issue to the City and may delay that report only to the extent authorized by law or needed to determine the general nature of the Security Issue and develop recommendations for the City to prevent or mitigate the Security Issue. The

AT-01 / 00614644 / v18 5 of 10

Contractor shall not delay that report for purposes of performing any action required under subsection 9(b).

(b) The Contractor shall remedy the Security Issue in a timely manner and deliver to the City a root cause assessment and future incident mitigation plan with regard to the Security Issue that sets out written details regarding the Contractor’s investigation of the Security Issue and, upon the City’s written request, provide a second, more in-depth investigation and results of its findings.

(c) If, before completion of the actions required under subsection 9(b), the Contractor identi-fies information that would assist the City in mitigating or otherwise responding to the Security Issue, the Contractor shall immediately provide that information to the City unless prohibited by law from doing so.

(d) The Contractor shall not send notice of any Security Issue to any law enforcement agency, regulatory authority, consumer, or other person or entity for or on behalf of the City unless required to do so by law or explicitly requested to do so in writing by the City. But if the City requests that the Contactor send any such notice, the Contractor shall prepare and send each such notice at its sole expense following review and approval of the notice and distri-bution list by the City.

(e) If City determines that the Security Issue was caused, in whole or in part, by any act or omission of the Contractor, the Contractor shall reimburse the City for any cost or expense incurred by the City in providing notice of the Security Issue in a manner consistent with applicable law, City policy or procedure, or industry best practice.

10. Credit card security. If no Deliverable processes credit card information, this section 10 is void and of no effect. Otherwise, the following provisions apply with respect to any Deliverable that processes credit card information:

(a) The Contractor acknowledges that the applicable Deliverable is subject to the following data security standards, as each may be amended from time to time (collectively, the “Credit Card Security Standards”): (i) the Fair and Accurate Credit Transactions Act of 2003 and any associated regulation; (ii) the most recent version of the Payment Application Data Security Standard (PA‑DSS); and (iii) any applicable Payment Card Information (PCI) rule, practice, standard, or program (including Visa CISP, MasterCard SDP, Discover DISC, and American Express DSOP).

(b) Accordingly, the Contractor shall ensure that the applicable Deliverable complies with each applicable Credit Card Security Standard at all times and provide the City with documen-tation of such compliance upon request by the City.

AT-01 / 00614644 / v18 6 of 10

11. Warranties. The Contractor warrants that each Deliverable (i) will be free from defects in materials and workmanship; (ii) will be fit for the purpose for which that Deliverable is ordinarily employed and for any other purpose set forth in this Agreement; (iii) will satisfy all requirements expressly stated in this Agreement; and (iv) will have clear title and be free of any lien, claim, or encumbrance of any kind other than those expressly stated in this Agreement.

12. Third-party terms. If the Agreement incorporates any terms that are dictated by a third party, rather than controlled by the Contractor, (e.g., an end-user license agreement for a software Deliverable owned by a company other than the Contractor) and that third party elects to change any of those terms, the Contractor shall notify the City in writing of each change no more than 10 calendar days after learning of the change. In the 30 calendar days following either receipt of such a notice or the City’s independent determination that the third party has elected to make such a change, whichever occurs first, the City may elect to terminate the Agreement without penalty by providing written notice of such termination to the Contractor. No more than 30 calendar days after receiving such notice from the City, the Contractor shall provide the City with a pro rata refund of any amount pre-paid by the City for usage or support of a Deliverable. Such refund does not in-clude any amount paid for initial costs attributable to implementation, setup, training, or a perpetual right to use a Licensed Deliverable.

13. Third-party performance. If a third party provides any Deliverable under the Agreement, in whole or in part, the following provisions apply, regardless of the legal or business relationship between the Contractor and that third party:

(a) The third party may perform any obligation of the Contractor under the Agreement or per-form any action that the Contractor has permission or discretion to take under the Agreement. But the Contractor shall ensure that such performance by the third party fulfills the requirements of the Agreement in full, and any deviation from the requirements of the Agreement by the third party constitutes a breach of the Agreement by the Contractor.

(b) If the Contractor is prohibited from taking any action under the Agreement, the Contractor shall ensure that the third party does not take that prohibited action. Accordingly, if the third party takes any action that the Contractor is prohibited from taking, it constitutes a breach of the Agreement by the Contractor.

(c) Any recital, representation, declaration, statement of fact, warranty, or consent in the Agreement that is made by the Contractor with respect to the third party or with respect to an action to be performed by the third party is deemed to be made by the Contractor for itself and on behalf of the third party. Accordingly, if any such recital, representation, dec-laration, statement of fact, warranty, or consent is or becomes false or is otherwise not

AT-01 / 00614644 / v18 7 of 10 fulfilled by the Contractor or the third party, it constitutes a breach of the Agreement by the Contractor.

(d) Any breach caused in whole or in part by the third party is deemed to be the sole responsi-bility of the Contractor for purposes of the Agreement, and the Contractor shall cure such breach in accordance with section 22.

(e) The Contractor acknowledges (i) that the City may withhold payment on an invoice pursu-ant to section 4 even if the applicable failure to satisfy a requirement of the Agreement is the fault of the third party, in whole or in part; (ii) that section 5 applies to any license, sublicense, or other right to access or use Intellectual Property that flows from a third party;

and (iii) that the Contractor’s obligations under section 17 apply to any Claim arising from the action or inaction of the third party as well as any Claim asserted by the third party.

14. Applicable law.

(a) The Contractor shall comply with all applicable federal, state, and local law in the perfor-mance of the Agreement, and the Contractor hereby consents to amendment of any provision of the Agreement that is contrary to any such law to the extent necessary to be permissible under such law.

(b) By executing, amending, or renewing the Agreement, the Contractor is deemed to have made all certifications required under Florida Statutes section 287.135 at the time of the applicable execution, amendment, or renewal. Additionally, the Contractor acknowledges that the City may terminate the Agreement as provided in Florida Statutes sections 287.135 or 448.095, as each may be amended from time-to-time.

(c) The Agreement will be interpreted under Florida law. Venue for any action arising out of the Agreement brought in state court shall be in Pinellas County, St. Petersburg Division, and venue for any action arising out of the Agreement brought in federal court shall be in the Middle District of Florida, Tampa Division, unless a division shall be created in St.

Petersburg or Pinellas County, in which case the action shall be brought in that division.

Each party waives any defense, whether asserted by motion or pleading, that the courts specified in this section are an improper or inconvenient venue. Moreover, the parties con-sent to the personal jurisdiction of the courts specified in this section and irrevocably waive any objections to said jurisdiction.

15. Public records. With respect to Florida law regarding public records (including Florida Statutes chapter 119, generally, and Florida Statutes subsections 119.0701(2)–(3), specifically):

AT-01 / 00614644 / v18 8 of 10

(a) The Contractor shall retain each record with respect to the Agreement and make such rec-ord open to examination or audit by the City (i) during the term of the Agreement and

(ii) after the term of the Agreement for the applicable retention period set forth in the most recent General Records Schedule GS1-SL for Florida State and Local Government Agen-cies.

(b) Florida law regarding public records supersedes all other the terms of the Agreement, in-cluding any confidentiality provision that would prohibit the City from releasing any record related to the Agreement.

(c) Nothing in the Agreement allows destruction of any record that must be retained for a longer period of time pursuant to Florida law regarding public records. Accordingly, the City may retain any record related to the Agreement (including any Intellectual Property of the Contractor or any third party) as needed to comply with all applicable law, including Florida law regarding public records.

(d) IF CONTRACTOR HAS QUESTIONS REGARDING THE APPLI-

CATION OF CHAPTER 119, FLORIDA STATUTES, AS TO

CONTRACTOR’S DUTY TO PROVIDE PUBLIC RECORDS RE-

LATING TO THE AGREEMENT, CONTRACTOR SHALL

CONTACT THE CITY CLERK’S OFFICE (THE CUSTODIAN

OF PUBLIC RECORDS) AT 727-893-7448,

CITY.CLERK@STPETE.ORG, OR 175 FIFTH ST. N., ST. PE-

TERSBURG, FL 33701.

16. Non-Appropriation. Notwithstanding anything in the Agreement to the contrary, the ob-ligation of the City as to any payment or funding required pursuant to the Agreement (including any acceleration of payment or penalty resulting from termination of the Agreement before the end of the then-current term) shall be limited to an obligation in any given year to budget, appropriate, and pay from legally available funds, after monies for essential city services have been budgeted and appropriated, sufficient monies for the funding that is required during that year. Notwithstand-ing the foregoing, the City shall not be prohibited from pledging any legally available non-ad-valorem revenues for any obligations heretofore or hereafter incurred, which pledge shall be prior and superior to any obligation of the City pursuant to the Agreement.

17. Indemnity. The Contractor shall defend at its expense, pay on behalf of, hold harmless, and indemnify the City, its officers, employees, agents, elected and appointed officials, and volun-teers (collectively, “Indemnified Parties”) from and against any and all claims, demands, liens, liabilities, penalties, fines, fees, judgments, losses, and damages (collectively, “Claims”), whether

AT-01 / 00614644 / v18 9 of 10 or not a lawsuit is filed, including, but not limited to Claims for damage to property or bodily or personal injuries, including death at any time resulting therefrom, sustained by any persons or entities, and costs, expenses, and attorneys’ and experts’ fees at trial and on appeal, which Claims are alleged or claimed to have arisen out of or in connection with, in whole or in part, directly or indirectly, the Agreement. The provisions of this section 17 (i) are independent of and are not be limited by any insurance obtained by Contractor pursuant to the Agreement or otherwise and

(ii) survive the expiration or earlier termination of the Agreement with respect to any Claims aris-ing out of or in connection with any event occurring prior to such expiration or termination.

18. Insurance coverage. The Contractor shall carry the following types and amounts of insur-ance coverage at its own expense and shall, upon request, provide the City with proof of all such coverage on a certificate of insurance on a standard ACORD form:

(a) Commercial general liability insurance in an amount of at least $1,000,000 per occurrence, $2,000,000 aggregate in occurrences form. This policy must include coverage for (i) bodily injury; (ii) property damage; (iii) personal and advertising injury; (iv) products and com-pleted operations; and (v) contractual liability under the Agreement. Such contractual liability coverage must provide and pay for a defense for all claims or demands covered by the Contractor’s indemnification obligations under the Agreement and have an amount suf-ficient to cover the Contractor’s obligations under section 17.

(b) Cyber liability insurance in an amount of at least $1,000,000 per occurrence. This policy must include coverage for (i) security and privacy liability, including privacy breach re-sponse costs, regulatory fines and penalties, and cyber extortion; (ii) media liability, including infringement of copyright, trademark, and trade dress; and (iii) errors and omis-sions in any Deliverable.

(c) Workers’ Compensation insurance as required by applicable law and Employers’ Liability Insurance in an amount of at least $100,000 each accident, $100,000 per employee, and $500,000 for diseases.

(d) Any other insurance coverage (i) that is required under applicable law; (ii) that would be reasonably associated with the provision of the Deliverables; or (iii) that is actually carried by the Contractor, even if such coverage is broader in scope or has greater limits than those stated elsewhere in this section 18.

19. Insurance standards. With respect to all insurance coverage required by section 18: (a) all policies other than workers’ compensation must name the Indemnified Parties as additional in-sured; (b) all coverage must be provided by a responsible insurer licensed in the State of Florida and rated at least A- in the then-current edition of AM Best’s Rating Services; (c) if any coverage is made on a “claims made” basis, such coverage must include the retro date of coverage; (d) with

AT-01 / 00614644 / v18 10 of 10 respect to all coverage, Contractor hereby waives all subrogation rights of its insurance carriers in favor of the Indemnified Parties; and (e) all coverage must be made on a primary and noncontrib-utory basis.

20. Force Majeure. If either party to the Agreement is delayed, hindered, or prevented from the performance required under the Agreement by reason of strike, lockout, labor trouble, power failure, riot, insurrection, war, act of God, public health emergency, or other similar event that is not the fault of the party delayed, hindered, or prevented from that performance (each a “Permitted Delay”), that party (the “Delayed Party”) is excused from performance under the Agreement for the period of time equivalent to the delay caused by that Permitted Delay if that Delayed Party requests an extension from the other party in the 10 calendar days following the date on which the Delayed Party had actual or constructive knowledge of the Permitted Delay.

21. City liability. To the extent permitted under applicable law, the City accepts no liability, responsibility, or indemnity obligation for any third-party claim or damage arising out of or in connection with the Agreement or the possession or use of any Deliverable. Nothing in the Agree-ment is intended to serve as a waiver of sovereign immunity by the City or acceptance by the City of any liability in excess of limits provided to the City under applicable law.

22. Dispute resolution. Notice of any alleged breach of the Agreement by the City must be delivered to the City in writing and provide the City with at least 30 calendar days to cure that alleged breach. During any such cure period, the Contractor shall not terminate, suspend, impair, degrade, or otherwise limit any service or right provided to the City pursuant to the Agreement.

Additionally, City does not (a) consent to mandatory arbitration or mediation; (b) consent to any limit on the amount of Contractor’s liability under the Agreement or any exception to Contractor’s obligations under section 17; (c) consent to any cure period for breach of the Agreement by the Contractor that would exceed 30 days without express written consent of the City; or (d) waive any remedy available to the City in law or equity.

23. Assignment. The Agreement may not be assigned or transferred by either party without the prior written consent of the other party, and any purported attempt to assign or transfer the Agreement in violation of this provision is void.

Amendment. No amendment or termination of the Agreement is effective without mutual written consent of the parties. Accordingly, no click-through, click-wrap, browse-wrap, or other contrac-tual provision presented by or through a Deliverable as a condition of installation or use may serve as an amendment to the Agreement, and this Addendum supersedes any such provision with re-spect to the City and with respect to any person who uses the applicable Deliverable pursuant to the Agreement.

AT-01 / 00614644 / v18

EXTERNAL DOCUMENTS

[REPLACE WITH ALL OTHER ATTACHED DOCUMENTS]

City of St. Petersburg Technology Purchase Agreement
1. Components of Agreement. The Agreement consists of this document and the documents listed below, each of which is attached to this Agreement as an exhibit (unless otherwise noted as being incorporated by reference):
(a) City of St. Petersburg Standard Technology Addendum (the “Addendum”).
(b) [any City-produced documents (scope of work, requirements, etc.)]
(c) The following Contractor or third-party documents (each, an “External Document”):
(i) [proposal / quote]
(ii) [Contractor-written scope of work]
(iii) [Contractor standard terms and conditions]
(iv) [Any other Contractor or third-party document]
2. Effective date; term. The Agreement is effective when this document has been signed by all parties. If the date established for Contractor’s initial performance predates the date on which this document is signed by all parties, the Agreement is eff...
3. Conflict. In the event of a conflict between any documents comprising the Agreement, a document listed higher in section 1 will control over a document that is listed lower, and if there is a conflict between any documents listed at the same level ...
4. Entire Agreement. The Agreement constitutes the entire agreement between the parties with respect to its subject matter, and it supersedes any previous representation, proposal, or agreement as to its subject matter, whether oral or written.
5. Execution. Any component of the Agreement may be signed in any number of counterparts, each of which is deemed to be an original, and such counterparts collectively constitute a single original copy of the Agreement. Additionally, each party is aut...
City of St. Petersburg Standard Technology Addendum
1. Incorporated Terms. For purposes of this Addendum, the following defined terms are incorporated by reference from the document to which this Addendum is attached or incorporated: “Agreement,” “City,” “Contractor,” and “Deliverable.”
2. City Forms. The City may issue standard-form documents for the purpose of exercising its rights under the Agreement (each a “City Form”) in accordance with the following:
(a) The City may issue any number of City Forms, alone or in combination, to exercise any right available to it under the Agreement (e.g., purchasing a Deliverable or renewing or extending the Agreement), and a City Form is subject to the terms of the...
(b) A City Form may take the form of a blanket purchase agreement, contract purchase agreement, purchase order, or any other standard-form document issued by or through a City administrative system or procedure, and it includes any document that is at...
(c) The following provisions in a City Form are void: (i) any provision that is inconsistent with the Addendum and (ii) any provision that would incorporate new terms and conditions through a URL. Otherwise, any provision in a City Form that is incons...
3. Notice. Any notice to the City under the Agreement must be delivered in writing to a physical or electronic address explicitly designated in writing by the City for that purpose, and the City may modify such designation from time to time. The City’...
4. Invoicing and payment. This City is obligated to pay the Contractor for performance under the Agreement only if the Contractor has submitted an invoice in accordance with the City’s procedures for submission of such an invoice, and the City must be...
5. Renewal terms. The term of the Agreement may be renewed or extended for an additional period of time (each a “Renewal Term”) only if the City provides written consent to the Renewal Term. Accordingly, any “automatic” renewal or extension of the Agr...
6. Intellectual property rights. For purposes of the Agreement, “Intellectual Property” includes any copyright, patent right, trademark, trade secret, or other form of intellectual property, regardless of jurisdiction, along with any application, regi...
(a) Subject only to a limit on the number of authorized users explicitly stated in the Agreement, any officer, employee, agent, contractor, subcontractor, elected or appointed official, or volunteer of the City has the non-exclusive, right and license...
(b) The City may copy any Licensed Deliverable for archival backup, disaster-recovery, or other internal purposes. Such internal purposes include installation of software Deliverable in non-production environments for testing and configuration purpose...
(c) The owner of any Licensed Deliverable, whether the Contractor or a third party, retains exclusive ownership of all Intellectual Property contained in that Licensed Deliverable unless otherwise provided for in a document that explicitly transfers o...
7. City information. With respect to any information, data, or other content that is provided to the Contractor in connection with the Agreement or that is uploaded, submitted, posted, transferred, transmitted, stored, or otherwise made available to o...
8. Redundancy, data backup, and disaster recovery. If no Deliverable is “cloud-based” software provided to the City through the internet (“Hosted Software”), this section 8 is void and of no effect. Otherwise, the Contractor shall, in accordance with ...
(a) The Contractor shall ensure that the primary system from which the Hosted Software is provided is located in the contiguous United States.
(b) The Contractor shall simultaneously operate a mirror system for the Hosted Software at a hardened data center facility in the contiguous United States that is geographically remote from the primary system from which the Hosted Software is provided...
(c) Unless otherwise explicitly stated in the Agreement, there is no limit on the amount of City Information that may be stored in the Hosted Software, and the City’s payment under the Agreement covers all storage of City Information in the Hosted Sof...
(d) The Contractor shall maintain a business continuity and disaster-recovery plan for the Hosted Software (the “BCDR Plan”) and provide the City, upon request, with a current copy of the BCDR Plan, along with any reports or summaries relating to past...
(e) If the City requests a comprehensive export of all City Information stored in the Hosted Software, the Contractor shall provide such export no more than ten days after receiving such request. If that City Information is stored in its native format...
9. Security issues. If the Contractor has actual or constructive knowledge of any potential or actual vulnerability, security breach, or unauthorized access to any Deliverable; to any software or technology system provided, maintained, or supported by...
(a) The Contractor shall report the Security Issue to the City and may delay that report only to the extent authorized by law or needed to determine the general nature of the Security Issue and develop recommendations for the City to prevent or mitiga...
(b) The Contractor shall remedy the Security Issue in a timely manner and deliver to the City a root cause assessment and future incident mitigation plan with regard to the Security Issue that sets out written details regarding the Contractor’s invest...
(c) If, before completion of the actions required under subsection 9(b), the Contractor identifies information that would assist the City in mitigating or otherwise responding to the Security Issue, the Contractor shall immediately provide that inform...
(d) The Contractor shall not send notice of any Security Issue to any law enforcement agency, regulatory authority, consumer, or other person or entity for or on behalf of the City unless required to do so by law or explicitly requested to do so in wr...
(e) If City determines that the Security Issue was caused, in whole or in part, by any act or omission of the Contractor, the Contractor shall reimburse the City for any cost or expense incurred by the City in providing notice of the Security Issue in...
10. Credit card security. If no Deliverable processes credit card information, this section 10 is void and of no effect. Otherwise, the following provisions apply with respect to any Deliverable that processes credit card information:
(a) The Contractor acknowledges that the applicable Deliverable is subject to the following data security standards, as each may be amended from time to time (collectively, the “Credit Card Security Standards”): (i) the Fair and Accurate Credit Transa...
(b) Accordingly, the Contractor shall ensure that the applicable Deliverable complies with each applicable Credit Card Security Standard at all times and provide the City with documentation of such compliance upon request by the City.
11. Warranties. The Contractor warrants that each Deliverable (i) will be free from defects in materials and workmanship; (ii) will be fit for the purpose for which that Deliverable is ordinarily employed and for any other purpose set forth in this Ag...
12. Third-party terms. If the Agreement incorporates any terms that are dictated by a third party, rather than controlled by the Contractor, (e.g., an end-user license agreement for a software Deliverable owned by a company other than the Contractor) ...
13. Third-party performance. If a third party provides any Deliverable under the Agreement, in whole or in part, the following provisions apply, regardless of the legal or business relationship between the Contractor and that third party:
(a) The third party may perform any obligation of the Contractor under the Agreement or perform any action that the Contractor has permission or discretion to take under the Agreement. But the Contractor shall ensure that such performance by the third...
(b) If the Contractor is prohibited from taking any action under the Agreement, the Contractor shall ensure that the third party does not take that prohibited action. Accordingly, if the third party takes any action that the Contractor is prohibited f...
(c) Any recital, representation, declaration, statement of fact, warranty, or consent in the Agreement that is made by the Contractor with respect to the third party or with respect to an action to be performed by the third party is deemed to be made ...
(d) Any breach caused in whole or in part by the third party is deemed to be the sole responsibility of the Contractor for purposes of the Agreement, and the Contractor shall cure such breach in accordance with section 22.
(e) The Contractor acknowledges (i) that the City may withhold payment on an invoice pursuant to section 4 even if the applicable failure to satisfy a requirement of the Agreement is the fault of the third party, in whole or in part; (ii) that section...
14. Applicable law.
(a) The Contractor shall comply with all applicable federal, state, and local law in the performance of the Agreement, and the Contractor hereby consents to amendment of any provision of the Agreement that is contrary to any such law to the extent nec...
(b) By executing, amending, or renewing the Agreement, the Contractor is deemed to have made all certifications required under Florida Statutes section 287.135 at the time of the applicable execution, amendment, or renewal. Additionally, the Contracto...
(c) The Agreement will be interpreted under Florida law. Venue for any action arising out of the Agreement brought in state court shall be in Pinellas County, St. Petersburg Division, and venue for any action arising out of the Agreement brought in fe...
15. Public records. With respect to Florida law regarding public records (including Florida Statutes chapter 119, generally, and Florida Statutes subsections 119.0701(2)–(3), specifically):
(a) The Contractor shall retain each record with respect to the Agreement and make such record open to examination or audit by the City (i) during the term of the Agreement and (ii) after the term of the Agreement for the applicable retention period s...
(b) Florida law regarding public records supersedes all other the terms of the Agreement, including any confidentiality provision that would prohibit the City from releasing any record related to the Agreement.
(c) Nothing in the Agreement allows destruction of any record that must be retained for a longer period of time pursuant to Florida law regarding public records. Accordingly, the City may retain any record related to the Agreement (including any Intel...
(d) If Contractor has questions regarding the application of Chapter 119, Florida Statutes, as to Contractor’s duty to provide public records relating to the Agreement, Contractor shall contact the City Clerk’s office (the custodian of public records...
16. Non-Appropriation. Notwithstanding anything in the Agreement to the contrary, the obligation of the City as to any payment or funding required pursuant to the Agreement (including any acceleration of payment or penalty resulting from termination o...
17. Indemnity. The Contractor shall defend at its expense, pay on behalf of, hold harmless, and indemnify the City, its officers, employees, agents, elected and appointed officials, and volunteers (collectively, “Indemnified Parties”) from and against...
18. Insurance coverage. The Contractor shall carry the following types and amounts of insurance coverage at its own expense and shall, upon request, provide the City with proof of all such coverage on a certificate of insurance on a standard ACORD form:
(a) Commercial general liability insurance in an amount of at least $1,000,000 per occurrence, $2,000,000 aggregate in occurrences form. This policy must include coverage for (i) bodily injury; (ii) property damage; (iii) personal and advertising inju...
(b) Cyber liability insurance in an amount of at least $1,000,000 per occurrence. This policy must include coverage for (i) security and privacy liability, including privacy breach response costs, regulatory fines and penalties, and cyber extortion; (...
(c) Workers’ Compensation insurance as required by applicable law and Employers’ Liability Insurance in an amount of at least $100,000 each accident, $100,000 per employee, and $500,000 for diseases.
(d) Any other insurance coverage (i) that is required under applicable law; (ii) that would be reasonably associated with the provision of the Deliverables; or (iii) that is actually carried by the Contractor, even if such coverage is broader in scope...
19. Insurance standards. With respect to all insurance coverage required by section 18: (a) all policies other than workers’ compensation must name the Indemnified Parties as additional insured; (b) all coverage must be provided by a responsible insur...
20. Force Majeure. If either party to the Agreement is delayed, hindered, or prevented from the performance required under the Agreement by reason of strike, lockout, labor trouble, power failure, riot, insurrection, war, act of God, public health eme...
21. City liability. To the extent permitted under applicable law, the City accepts no liability, responsibility, or indemnity obligation for any third-party claim or damage arising out of or in connection with the Agreement or the possession or use of...
22. Dispute resolution. Notice of any alleged breach of the Agreement by the City must be delivered to the City in writing and provide the City with at least 30 calendar days to cure that alleged breach. During any such cure period, the Contractor sha...
23. Assignment. The Agreement may not be assigned or transferred by either party without the prior written consent of the other party, and any purported attempt to assign or transfer the Agreement in violation of this provision is void.

External Documents

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