Attachment A - Agreement 26C069 — Palm Springs City Council, May 12, 2026

ATTACHMENT “A”
Cooperative Agreement 26C069
55575.18100\42906602.1

BB&K (2024)

COOPERATIVE PURCHASE OF SOFTWARE SERVICES AGREEMENT NO. 26C069

This Cooperative Purchase of Software Services Agreement (“Agreement”) is entered into by and between the City of Palm Springs, a California charter city and municipal corporation (“City”) and Vertosoft, a limited liability company of Virginia (“Contractor”). City and Contractor are sometimes individually referred to as a “Party” or collectively as the “Parties” in this Agreement.

1. Background.
a. This Agreement is made and entered into in reference to the competitively solicited Sourcewell Contract No. 060624-VTO (“Cooperative Agreement”). b. The City desires to implement OpenGov software solutions for enterprise asset management, 311 constituent relationship management, code enforcement, and procurement and contracting management services , attached hereto as Attachment “A”, the content of which is incorporated by reference to this Agreement as if fully set out here in its entirety.
c. Contractor desires to perform said services on the terms and conditions set forth in this Agreement.

2. Term. The term of this Agreement is for five-years, beginning on June 1, 2026, and continuing through May 31, 2031, unless extended by mutual written agreement of the Parties.

3. Compensation and Payment. This Agreement shall be for an amount not to exceed Two Million One Hundred Seventeen Thousand Three Hundred Eighty-Three Dollars and Seventy- Nine Cents ($2,117,383.79), subject to approved amendments and changes. All pricing must be in accordance with the attached Quote, as shown as Attachment “B,” which is incorporated by reference into this Agreement, as if fully set out here in its entirety.

4. Appropriations. This Agreement is subject to, and contingent upon, funds being appropriated by the City Council for each fiscal year. If such appropriations are not made, this Agreement shall automatically terminate without penalty to the City.

5. Insurance. Contractor shall procure and maintain, at its sole cost and expense, policies of insurance as set forth in the attached Attachment "C", incorporated herein by reference. If no insurance is required, Attachment “C” will reflect that there are no insurance requirements set forth for this Agreement.

6. Indemnification. To the fullest extent permitted by law, Contractor shall defend (at Contractor’s sole cost and expense), indemnify, protect, and hold harmless City, its elected officials, officers, employees, agents, and volunteers (collectively the “Indemnified Parties”) , from and against any and all liabilities, actions, suits, claims, demands, losses, costs, judgments, arbitration awards, settlements, damages, demands, orders, penalties, and expenses, including legal costs and attorney fees (collectivel y “Claims”), including but not limited to , Claims arising from injuries to or death of persons (Contractor’s employees

55575.18100\42906602.1

BB&K (2024)

included), for damage to property, including property owned by City, for any violation of any federal, state, or local law or ordinance or in any manner arising out of, pertaining to, or incident to any acts, errors or omissions, or willful misconduct comm itted by Contractor, its officers, employees, representatives, and agents, that arise out of or relate to Contractor’s performance of Services or this Agreement. This indemnification clause excludes Claims arising from the sole negligence or willful misconduct of the Indemnified Parties. Under no circumstances shall the insurance requirements and limits set forth in this Agreement (if required and incorporated as part of this Agreement) be construed to limit Contractor’s indemnification obligation or other liability under this Agreement. Contractor’s indemnification obligation shall survive the expiration or earlier termination of this Agreement, until all actions against the Indemnified Parties for such matters indemnified are fully and finally barred by the applicable statute of limitations or, if an action is timely filed, until such action is final.

7. Notice. Any notices required under this Agreement must be given by fax, hand delivery, or certified mail, postage prepaid, and is deemed received on the day faxed, or hand delivered or on the third day after postmark if sent by certified mail. Notice shall be sent as follows:

IF TO THE CITY: IF TO THE CONTRACTOR:

City of Palm Springs Vertosoft LLC
Attn: Scott Stiles; Brenda Pree Attn: Nur Rahman
Title: City Manager / City Clerk Title: Vice President, Operations Address: 3200 E Tahquitz Canyon Way Address: 1602 Village Market Blvd, STE 230 Palm Springs, CA 92262 Leesburg, VA 20175
Phone: (760) 323-8204 Phone: (571) 707-4130
Email: [email protected] Email: [email protected]

8. Compliance with Law. Contractor shall comply with all applicable federal, state, and local laws, statutes and ordinances and all lawful orders, rules, and regulations when performing the Services. Contractor shall be liable for all violations of such laws and regulations in connection with this Agreement.

9. Changes. In the event any change or changes in the work is requested by City, the Parties shall execute a written amendment to this Agreement, specifying all proposed amendments, including, but not limited to, any additional fees. An amendment may be entered into:

A. To provide for revisions or modifications to documents, work product, or Work, when required by the enactment or revision of any subsequent law; or B. To provide for additional work not included in this Agreement or not customarily furnished in accordance with generally accepted practice in Contractor’s profession.

10. Termination Prior to Expiration of Term. The City may terminate this Agreement at any time, with or without cause, upon thirty ( 30) days written notice to Contractor. Where termination is due to the fault of Contractor and constitutes an immediate danger to health, safety, and general welfare, the period of notice shall be such shorter time as may be determined by the City , in its sole and absolute discretion. Upon receipt of the notice of termination, Contractor shall immediately cease all Services except such as may be specifically approved by the Contract Officer. Contractor shall be entitled to compensation for 55575.18100\42906602.1

BB&K (2024)

all Services rendered prior to receipt of the notice of termination and for any Services authorized by the Contract Officer after such notice. The City shall not be liable for any costs other than the charges or portions thereof which are specified herein. Contractor shall not be entitled to payment for unperformed Services and shall not be entitled to damages or compensation for termination of Work. If the termination is for cause, the City shall have the right to take whatever steps it deems necessary to correct Contractor's deficiencies and charge the cost thereof to Contractor, who shall be liable for the full cost of the City's corrective action. Contractor may not terminate this Agreement except for cause, upon thirty ( 30) days written notice to the City.

11. Covenant Against Discrimination. In connection with its performance under this Agreement, Contractor shall not discriminate against any employee or applicant for employment because of actual or perceived race, religion, color, sex, age, marital status, ancestry, national origin (i.e., place of origin, immigration status, cultural or linguistic characteristics, or ethnicity), sexual orientation, gender identity, gender expression, physical or mental disability, or medical condition (each a “prohibited basis”). Contractor shall ensure that applicants are employed, and that employees are treated during their employment, without regard to any prohibited basis. As a condition precedent to the City’s lawful capacity to enter this Agreement, and in executing this Agreement, Contractor certifies that its actions and omissions hereunder shall not incorporate any discrimination arising from or related to any prohibited basis in any Contractor activi ty, including but not limited to, the following: employment, upgrading, demotion or transfer; recruitment or recruitment advertising; layoff or termination; rates of pay or other forms of compensation; and selection for training, including apprenticeship; and further, that Contractor is i n full compliance with the provisions of Palm Springs Municipal Code Section 7.05.02 , including without limitation the provision of benefits, relating to non- discrimination in City contracting.

12. Compliance with Economic Sanctions in Response to Russia's Actions in Ukraine.

When funding for the services is provided, in whole or in part, by an agency controlled of the State of California, Consultant shall fully and adequately comply with California Executive Order N-6-22 (“Russian Sanctions Program”). As part of this compliance process, Consultant shall also certify compliance with the Russian Sanctions Program by completing the form located in Attachment “D” (Russian Sanctions Certification), attached hereto and incorporated herein by reference. Consultant shall also require any subconsultants to comply with the Russian Sanctions Program and certify compliance pursuant to this section.

13. Entire Agreement. This Agreement, along with the Cooperative Agreement constitutes the entire agreement between the P arties concerning the subject matter of this Agreement and supersedes all prior negotiations, arrangements, agreements and understandings, either oral or written between the P arties. In the event of conflict or inconsistency between this Agreement and the Cooperative Agreement, this terms and conditions in this Agreement shall prevail.

[Signature Page on Following Page]

55575.18100\42906602.1

BB&K (2024)

SIGNATURE PAGE TO COOPERATIVE PURCHASE OF SOFTWARE SERVICES

AGREEMENT

BETWEEN THE CITY OF PALM SPRINGS

AND VERTOSOFT LLC

IN WITNESS WHEREOF, the Parties have executed this Agreement as of the dates stated below.

CONTRACTOR:

By: _____________________________ By: _____________________________ Signature Signature

Date: ___________________________ Date: ___________________________

CITY OF PALM SPRINGS:

APPROVED BY CITY COUNCIL:

Date: 5/12/2026______ Item No. ________

APPROVED AS TO FORM: ATTEST:

By: _____________________________ By: _____________________________ City Attorney City Clerk

APPROVED:

By: _____________________________ Date: ____________________________ City Manager – up to $150,000
Deputy/Assistant City Manager – up to $50,000
Director – up to $25,000
Manager – up to $5,000
55575.18100\42906602.1

BB&K (2024)

ATTACHMENT “A”

SCOPE OF WORK

PS-10349.1
1 OpenGov
City of Palm Springs, CA

Creation Date: 4/3/2026
SoW Expiration Date: 7/3/2026
Document Number: PS-10349.1
Created by: Josh Volpert

PS-10349.1
2 Table of Contents
Contractor Statement of Work 4

1. Project Scope and Understanding 4

2. Exhibits 4

3. Contractor Responsibilities 4

4. City Responsibilities 4

5. Project Delivery 5

6. Estimated Schedule 5

7. Acceptance Procedure 5

8. Modiﬁcations 6

9. Communication and Escalation Procedure 6
Exhibit 1: Implementation Activities 7
Contractor Implementation Methodology Overview 7
Procurement & Contract Management: 7
Initiate 7
Validate 8
Conﬁgure 8
Train 10
Launch 10
Permitting & Licensing 11
Initiate 11
Validate 11
Conﬁgure 12
Train 13
Launch 14
Enterprise Asset Management 14
Initiate 15
Validate 15
Conﬁgure 15
Train 17
Launch 20
311 Request Management 21
Initiate 21
Validate 21
Configure 22
Train 29
Launch 30
Exhibit 2: Technical Requirements 32
Procurement Technical Requirements 32
PS-10349.1
3 Permitting & Licensing Technical Requirements 32
Government App Builder Technical Requirements 33
PS-10349.1
4 Contractor Statement of Work

1. Project Scope and Understanding
This Statement of Work (“SOW”) outlines the Professional Services Contractor will provide to the City of Palm Springs, CA (“City”) under the applicable Order Form.

Professional Services or technical requirements not listed in this SOW are out of scope.

2. Exhibits
The following exhibits are incorporated by reference and are part of this SOW:

2.1. Exhibit 1: Implementation Activities

2.1.1. Procurement & Contract Management

2.1.2. Permitting & Licensing

2.1.3. Enterprise Asset Management (EAM)

2.1.4. Government App Builder

2.2. Exhibit 2: Technical Requirements

2.2.1. Procurement & Contract Management

2.2.2. Permitting & Licensing

2.2.3. Government App Builder

3. Contractor Responsibilities
Contractor will provide a framework for planning, communication, progress tracking, and coordination for activities in Exhibit 1. In collaboration with City, Contractor will develop and maintain the Project Plan. The “Project Plan” is a detailed, living document that deﬁnes how the project will be executed, including tasks, timelines, milestones, and team assignments. Contractor will monitor progress against the Project Plan, coordinate adjustments to tasks and schedules as needed, and conduct status meetings as agreed to by the parties. Contractor will provide weekly status reports, a Project Charter, and a RAID register (Risks, Actions, Issues, and Decisions). The “Project Charter” is a high-level document outlining the project’s purpose, goals, key stakeholders, success criteria, and major milestones.

4. City Responsibilities
The City will appoint a primary point of contact with authority to make binding decisions (“City’s Project Manager”). This person will coordinate internal resources, assign subject matter experts (“SMEs”), and oversee implementation.

Responsibilities include attending status meetings, making timely decisions, providing requested information, escalating issues internally, and collaborating on the Project Plan and Change Order process, if applicable.

City acknowledges that the success of this project is contingent on its full participation.

City must provide data within ten (10) business days of a PS-10349.1
5 request, maintain consistent data formats and access throughout the project, and allocate the necessary City resources and time to support deliverables and meet agreed-upon timelines.

Any failure by City to meet its responsibilities under this SOW (each, a “City Delay”) will automatically suspend the affected obligations of Contractor for the duration of the City Delay and for a reasonable restart period thereafter. All affected milestones, delivery dates, and service-level commitments will be extended on a day-for-day basis (or as otherwise reasonably necessary) to account for the City Delay, and may result in an adjustment of the fees if Contractor incurs additional time, materials, or other costs as a result. Under no circumstances will any consequence of a City Delay constitute a breach by Contractor of this SOW or of the Agreement, nor will Contractor be liable for any failure to meet a performance obligation that is caused, in whole or in part, by a City Delay.

5. Project Delivery
Contractor will perform services under this SOW remotely and provide up to [1] onsite trips for project-related activities. City will provide a suitable workspace, including a conference room with attendee capacity, non-public Wi-Fi, and AV equipment. Travel expenses are estimated not to exceed $2,800. Contractor may use a combination of Contractor personnel and Contractor-trained implementation partners to deliver the services described in this SOW.

6. Estimated Schedule
The speciﬁc timeline, including order of delivery of the product(s), will be determined during the project planning activities in the Initiate Phase. Services are estimated to begin within two (2) weeks and no later than four (4) weeks from contract signature. Contractor reserves the right to adjust the schedule based on the availability of City or Contractor resources, and the timeliness of deliverables provided by the City.

7. Acceptance Procedure
Contractor will submit completed deliverables to the City’s Project Manager for review. Within ﬁve (5) business days of receipt, the City’s Project Manager will either provide written acceptance or a list of requested revisions. In the event there are requested revisions, the subsequent review period for acceptance will follow the same timeline until ﬁnal acceptance. If City does not respond within this PS-10349.1
6 period, the deliverable will be deemed accepted. Once a deliverable is accepted, any requested changes will require a paid Change Order.

Acceptance milestones and review timelines will be tracked in the Project Plan.

Both parties acknowledge that delays in task completion or unresolved issues may impact the project timeline. If Contractor determines in good faith that City is not fulﬁlling its responsibilities under this SOW, Contractor may place services on hold following a minimum of ﬁve (5) business days’ written notice. The notice will specify the actions needed to progress the project. During the hold period, Contractor may reallocate resources without penalty and will not be responsible for resulting delays.

8. Modiﬁcations
The fees and estimated timeline are based on the scope and assumptions in this SOW. If either party determines that a change to the scope is necessary, the parties will collaborate to deﬁne the required modiﬁcation, which may result in fee adjustments based on Contractor’s standard rates. All modiﬁcations must be documented in a written Change Order and signed by both parties (“Change Order”) .

Examples of changes include revisions to the project timeline, deliverables, or resource allocation.

9. Communication and Escalation Procedure
Contractor and City agree to maintain regular communication in alignment with the Project Plan to ensure progress, resolve questions promptly, and minimize risk.

Both parties will raise any issues or concerns in a timely manner. If challenges are not resolved through standard project discussions, City and Contractor Project Managers will escalate to their respective executive leadership teams to jointly determine a resolution and align on a path to successful implementation.

PS-10349.1
7 Exhibit 1: Implementation Activities
Contractor Implementation Methodology Overview

Every Contractor implementation follows a ﬁve-phase hybrid methodology designed to ensure a structured and collaborative deployment. The phases are:

1. Initiate – Contractor provisions access and performs initial system setup.

2. Validate – Contractor works with the City to conﬁrm requirements and review initial conﬁgurations.

3. Conﬁgure – Contractor completes system conﬁguration as outlined in this SOW.

4. Train – Contractor provides training to system administrators and/or end users, as applicable.

5. Launch – Contractor provides post-go-live support and transitions the City to Contractor’s City Success Team.

Each implementation is structured around these phases. Deliverables, sign-offs, and completion criteria are aligned to the relevant phase.

Procurement & Contract Management:

Use Cases Build for Procurement:
● Solicitation Development
● Supplier Engagement, Evaluation and Awards

Initiate
Provisioning Procurement Website Instance
Contractor will:
● Conﬁgure City portal and upload City’s logo. City will:
● Provide logo.
● Conﬁrm access to the Portal.

Completion Criteria
● City veriﬁes access to the site.

PS-10349.1
8 Validate
Technical Project Review
Contractor will:
● Provide up to one (1) two-hour working session at the beginning of the project to:
o Conﬁrm list of templates
o Review technical requirements
o Provide documentation on requirements and processes
Contractor Assumptions:
● Boilerplate language will be provided within two (2) weeks immediately following the kick-off meeting.

City will:
● Identify relevant participants for attendance.
● Conﬁrm deliverables.
● Gather and provide relevant data for the project.

Completion Criteria
● City sign-off on the project plan.

Conﬁgure
Supplier Engagement, Evaluation and Award Conﬁguration
Vendor Portal
Contractor will:
● Provide the City with iframe code and documentation to create the Vendor Portal. ● Import the list of vendors provided by City.

Contractor Assumptions:
● City will provide a complete and accurate vendor list for import to Contractor. Contractor clean up/correction of imported ﬁles are not included in the scope of this project.

City will:
● Allocate resources to create the Vendor Portal.
● Provide vendor email list and send vendor email/letter. ● Ensure that Vendor Portal will be active before Contractor begins conﬁguration of templates or the Solicitation Development phase.

Completion Criteria
● City sign-off that Vendor Portal has been conﬁgured.

Sourcing Template
Contractor will:
● Deploy generic template.
● Provide Contractor's “Paper to Paperless Language Transition Guide” to assist transition from paper to electronic.

City will:
● Provide a copy of the next solicitation document.
● Provide information to complete the generic solicitation upload template including forms and an example recent solicitation.
● Provide the category code set used by the agency (NIGP, NAICS, or UNSPSC).

Completion Criteria
PS-10349.1
9 ● City sign-off that the Generic Template has been conﬁgured.

Solicitation Template Development Solution
Contractor will:
● Review and conﬁrm the Solicitation Templates and documents provided by the City. ● Conﬁgure up to three (3) total Solicitation Templates from City provided standard templates:
○ Two (2) Non-Construction Solicitation Templates will be built based on examples collected from the City up to one hundred (100) pages in length. ○ One (1) Construction Solicitation Template will be built based on examples collected from the City up to two hundred (200) pages in length.
● Work with City to design and get sign off on the template(s).

Contractor Assumption:
● If templates were not provided by the City prior to the creation of the SOW and the City provides templates during the project that exceed the assumptions above, the Change Order Process will be followed.

City will:
● Provide templates.
● Provide forms associated with solicitation templates. ● Provide admin documents.
● Select the ﬁrst solicitation type (usually ITB or RFP), to work with Contractor for the design ● Test the conﬁguration of each template by creating test projects and provide feedback. ● Validate and provide signoff on Solicitation Templates.

Completion Criteria
● City sign-off that the Solicitation template(s) have been conﬁgured.

Admin Documents and Checklist Conﬁguration
Contractor will:
● Review & conﬁgure up to four (4) standard Admin Documents :
○ Proposal Viewer Agreement
○ Interview Invitation
○ Non-Award Letter
○ Notice of Intent to Award
City will:
● Provide Admin Documents.

Completion Criteria
● Admin Documents and Checklist have been conﬁgured.

Single Sign On (SSO) Implementation
Contractor will:
● Contractor implement identity provider initiated SSO for Microsoft ADFS, Microsoft Azure AD, or Okta.

City will:
● Complete the SSO enablement form.
● Provide the information from the identity provided required to establish SAML or HTTPS certiﬁcation.
● Add Contractor as a new application in City identity provider.

PS-10349.1
10 Completion Criteria
● Single Sign On has been conﬁgured.

Train
Procurement Training
Contractor will:
● Provide training on system functionality. Topics include:
○ Supplier Engagement
■ Creating Bids with Sourcing Templates
■ Live Bid Management & Vendor Experience
■ Evaluation and Awarding
○ Solicitation Development
■ Writing Solicitations using templates
City will:
● Attend training sessions as scheduled by the Project Manager and agreed to in the Project Plan.

Completion Criteria
● Training has been conducted.

Working Sessions
Contractor will:
● Assign practice exercises to City to gain familiarization. ● Assist City during ﬁrst real-life solicitation posting, and opening (if during deployment).
● Respond to questions regarding conﬁgured system functionality.

City will:
● Complete practice exercises to gain familiarization.
● Identify internal Admin Users & security permissions for all other users.

Completion Criteria
● Working sessions have been conducted.

Launch
HyperAdopt
Contractor will:
● Provide up to eight (8) hours of remote working session(s) to answer any questions following solution acceptance.
● Send Solution Acceptance Document
● Transition for project team to City Success. City
will:
● Identify issues and attend sessions.
● Sign Solution Acceptance Document
Completion Criteria
● City sign-off that the project has been completed.

PS-10349.1
11 Permitting & Licensing
Use Cases for Permitting & Licensing:
● Code Enforcement

Initiate
Provisioning Permitting & Licensing Platform

Contractor will:
● Contractor will provision City’s Contractor entity and verify City has access to all purchased modules.

City will:
● Conﬁrm access to entity and modules.

Completion Criteria
● City veriﬁes access to the site.

Data Initiation

Contractor will:
● Provide the needed data and format to the City.
● Discuss data needs for the foundational initiation of the software. ● Assign a Project Manager once the data has been collected.

City will:
● Provide the required data in a timely manner.

Completion Criteria
● City sign-off that the Integrations are complete and the data is being captured as planned.

Validate
Technical Project Review

Contractor will:
● Provide up to one (1) one-hour working sessions at the beginning of the project to:
o Review deliverables
o Review technical requirements
o Provide documentation on requirements and processes
Contractor Assumptions:
● City will provide relevant data within two (2) weeks immediately following the kick-off meeting.

City will:
● Identify relevant participants for attendance.

PS-10349.1
12 ● Conﬁrm deliverables.
● Gather and provide relevant data for the project.

Completion Criteria
● City sign-off on project plan.

Conﬁgure
Record Types Deliverables
Contractor will conﬁgure the following standard record types, including sub-types, drafts of City’s record types in the Permitting & Licensing system including Form, Workﬂow, Output Document and Fees:

Code Enforcement Service Area
Up to number (X) record types from the following list:
● Code Violation
City will:
● Attend working sessions to validate, review, and iterate upon draft records. ● Test all conﬁgured record types
Completion Criteria
● City sign-off that the Record Types have been conﬁgured. Sign-off will occur with each completed Record Type.

Data Deliverables
Master Address Table (MAT) Integration
Contractor will:
● Provide a template ﬁle to be utilized by the City to populate MAT information. ● Import the completed template ﬁle and validate against the completed template ﬁle.

City will:
● Populate and validate the MAT template.

Completion Criteria
● City sign-off that the Master Address Table has been conﬁgured.

Esri ArcGIS Server Integration
Contractor will:
● Integrate with the City’s ArcGIS public API endpoint.

Completion Criteria
● City sign-off on the Esri Integration.

GIS Flag Integration
Contractor will:
● Provide a template ﬁle to be utilized by the City to populate GIS Flag information. ● Import the populated template ﬁle after acceptance.
● Enable the GIS Flag Integration.

PS-10349.1
13 City will:
● Populate and validate the ﬂag template ﬁle.

Completion Criteria
● City sign-off on the GIS Flag Integration.

Accounting and Finance Export
Contractor will:
● Provide an export of ﬁnancial data, based on the City’s provided format, to the City’s FTPS as often as nightly.

City will:
● Agree upon speciﬁcations prior to export.

Completion Criteria
● City sign-off on the Accounting and Finance Export.

Autoﬁll Integration
Contractor will:
● Provide up to one (1) Autoﬁlls, using source data from Contractor or provided by the City.

City will:
● Provide the source data, if applicable.
● Agree upon speciﬁcations prior to upload.

Completion Criteria
● City sign-off on the Autoﬁll Integration.

Single Sign On (SSO) Integration
Contractor will:
● Provide the SSO enablement form.
● Implement identity provider initiated SSO for Microsoft ADFS, Microsoft Azure AD, or Okta.

City will:
● Complete the SSO enablement form.
● Provide the information from the identity provided required to establish SAML or HTTPS certiﬁcation and add Contractor as a new application in the identity provider.

Completion Criteria
● City sign-off on the SSO Integration.

Train
Administrator Training
Contractor will:
● Provide up to twelve (12) hours of Permitting & Licensing system administrator training to enable system administrators on the following topics:
○ Setting up the public portal
○ Employee app settings
○ Creating and editing record types
○ Managing Forms
PS-10349.1
14 ○ Editing Documents
○ Creating Workﬂows
○ Setting up Inspections
○ Reporting & Transparency
■ Download and upload data
■ How to create reports and dashboards
○ Mobile app
City will:
● Identify the relevant participants to attend each training session.

Completion Criteria
● Administrator Training has been conducted.

End User Training
Contractor will:
● Provide up to twelve (12) hours of end-user trainings designed for Plan Review, Inspectors, Finance Staff, etc. to cover the following topics:
○ Navigation of the system
○ Manage inbox and tasks
○ Take payments
○ Conduct inspections
○ Create records
○ Mobile app
City will:
● Identify the relevant participants to attend each training session.

Completion Criteria
● End User Training has been conducted.

Launch

HyperAdopt
Contractor will:
● Provide up to eight (8) hours of HyperAdopt support from the Contractor Project Team post Go-Live to ensure successful adoption.

City will:
● Identify issues and attend sessions
Completion Criteria
● City sign-off that the project has been completed.

Enterprise Asset Management
Use Cases Build for Enterprise Asset Management:

PS-10349.1
15 ● Transportation
● Walkability
● Parks and Rec
● Facilities
Contractor Enterprise Asset Management
Initiate
Contractor will:
● Setup a hosted sandbox and a hosted production Contractor Asset Management environment, if one does not already exist
● Conduct one (1) remote session to review City assets (see asset section below), source data, GIS capabilities, Esri authentication, and single sign on identity provider (if applicable).

Contractor Assumptions:
● Contractor assumes that the City is responsible for performing quality control measures on its data in EAM.

Completion Criteria:
● The project kicked off with an initial project timeline delivered.

Validate
Contractor will:
● Provide a remote, up to sixteen (16) hours validation workshop to increase our understanding of City business and functional goals. Through workshops and interviews, Contractor will identify best ﬁt scenarios for Contractor Asset Management and provide a brief including any challenges as well as recommendations for Contractor Asset Management best practices relevant to City implementation.
● Provide a template ﬁle to be utilized by City staff to populate resources, libraries, and users/roles data that Contractor will import into Contractor Enterprise Asset Management.
● Provide up to two (2) remote sessions for City technical GIS staff to conﬁgure Esri Feature Services for the bidirectional GIS integration and authentication.

Completion Criteria:
● Completion of validation workshop.

Conﬁgure

Conﬁgurations
Contractor will:

PS-10349.1
16 ● Provide conﬁguration services, including:
o Up to ten (10) custom ﬁelds and up to two (2) custom layouts per asset type listed in the Assets section below
o Up to thirty (30) custom ﬁelds and up to ten (10) custom layouts to be utilized in any of the shared areas of the system, such as Tasks o Up to twenty (20) automations
o Up to twenty (20) preventative maintenance plans
● Provide up to three (3) sessions of conﬁguration review to ensure conﬁgurations resulting from the validation workshop effectively support all workﬂows and processes discussed, and to reinforce such conﬁgurations with City stakeholders to adequately prepare to train-the-trainer training.

Contractor Assumptions:
● Implementation of any custom modiﬁcation developed by Contractor; your internal staff; or any third-party is not included in the scope of this project unless speciﬁcally listed above.

Data Services
Contractor will:
● Provide one sandbox and one production data load service through standard import/export functionality. Contractor will provide template documents for data population. Once populated by City staff, Contractor will load the data into City sandbox or production Contractor Asset Management environment. Data loads may include data such as:
o Parent level asset records
o Asset location (spatial x/y) attributes
o Parent level resource (Labor, Equipment Material, Vendor) records o Resource Rate (Labor, Equipment, Material) records
o Standard system libraries
● Provide service for City historical data listed below:
o Brightly data related to: assets, work history, total cost history, up to 250k records, and up to ten asset types.
o For the custom data conversion service(s) listed above, Contractor will provide:
▪ A review of the historical data along with recommendations for Contractor Asset Management best ﬁt.
▪ A ﬁeld map workshop, which will identify where and how historical data will appear within Contractor Asset Management
▪ A test conversion service to facilitate data conversion validation and testing
▪ One revision of the ﬁeld map used for the test conversion service ▪ A production conversion service utilizing the ﬁnal, approved ﬁeld map
o All data must be accessible to Contractor from a SQL DB, SQL View, Access DB or Comma Delimited Files.

PS-10349.1
17 o Exclusions:
▪ Child records and associated child-level attributes condition inspection history, request history, attachments, and resources.

Contractor Assumptions:
● Contractor assumes that the City is responsible for performing quality control measures on its data in EAM.
● Data conversion services from other software system(s) or sources (including Navigator databases) are not included in the scope of this project unless speciﬁcally listed above.

Assets
Contractor will:
● Provide installation and training on the following asset types:
o Transportation (8)
▪ Bridge; Light Fixture; Pavement; Sign; Guardrail; Marking; Pavement Area; Support
o Walkability (7)
▪ ADA Ramp; Pavement Area: Sign; Tree; Light Fixture; Sidewalk; Support
o Parks and Recreation (10)
▪ Athletic Space; Fence; Park; Park Structure; Playground Equipment; Bench; Landscape Area; Park Amenity; Playground; Tree
o Facilities (25)
▪ Facility; Other Site Construction; Selective Building Demolition; Site Improvement; Site Preparation; Facility Floor; Basement Construction; Conveying; Exterior Enclosures; Facility
Electrical; Facility Equipment; Fire
Protection; Foundations; Furnishings; HVAC; Interior
Construction; Interior Finishes; Plumbing; Rooﬁng; Site Electrical Utilities; Site Mechanical Utilities; Spaces; Special Construction; Stairs; Superstructure

Completion Criteria:
● City sign-off on ability to login and access to the sandbox.

Train
Foundational Training
● Provide remote train-the-trainer training, up to two (2) hours, on overall system navigation and functionality to help familiarize City staff with the software environment and its common functions. Training topics include:
o Dashboards
o Standard KPI/ROI Gadgets
PS-10349.1
18 o Logins/Permission
o Layers
o Filters
o Maps
o Grids
o System Navigation
o Views (List & Detail)
o Standard Reports
o Attachments
o Requests, Work, Assets, Resources, Reports, and Administrator Tabs

Contractor assumptions:
● Contractor assumes that the City is responsible for testing its workﬂows, automations, integrations, and conﬁgurations within the EAM and will update the conﬁgurations as part of its testing and training activities.

Train the Trainer Training Event
● Provide a three-day (3-day) onsite "train-the-trainer" training event. The training agenda will be deﬁned and agreed upon by both Contractor and City project manager. To avoid redundancy, and to utilize service time efficiently, training may cover a subset of the assets listed in the Asset section of the scope. Topics may include any of the following:
o Request Management:
▪ Requests
▪ Requesters
▪ Task Creation from Requests
▪ Issue library (including settings such as Applies to Asset and Non-Location)
▪ Contractor recommended best practices for Request and Requester Management
o Work Management:
▪ Create Task(s) (Asset/Non-Asset)
▪ Assignments (Add, Edit, Remove)
▪ Task Menu Actions
▪ Related Work Items
▪ Create Work Order
▪ Associate Task to Work Order
▪ Repeat Work Orders
▪ Work Order Menu Actions
▪ Enter Resources
▪ Timesheets
▪ Activity library (including settings such as Applies to Asset, Inspection, Key Dates, Cost, and Productivity)
▪ Contractor recommended best practices for Work Management o Asset Management:
▪ Asset Details
▪ Preventative Maintenance Plans
PS-10349.1
19 ▪ Inspections
▪ Linked assets (if applicable)
▪ Container/Component Relationships (if applicable)
▪ Contractor recommended best practices for Asset
Management o Resource Management:
▪ Resource Details
▪ Labor/Equipment Rates
▪ Material Management (Stock, Usage, Adjustments)
▪ Vendor Price Quotes
▪ Contractor recommended best practices for Resource
Management o Contractor Mobile:
▪ Overall system functionality (Navigation, Interface, Maps, Attachments, Sorting)
▪ Work Management
● Create and Update Tasks (Asset/Non-Asset)
● Assign Tasks
● Enter Resources
● Inspections
▪ Asset Management
● Create and Update Assets
▪ Request Management
● View and Update Requests
● View Requester information
● Create Task from Request
▪ Contractor recommended best practices for mobile device use o Administrator:
▪ Administrator:
● User Administration, Role Administration, Asset Administration, Record Filter Administration, Import/Export, Scheduled Process Log, Error Log
▪ Settings:
● System Settings, Map Administration, Geocode Settings, GIS Integration settings, Asset Color Manager
▪ Manager:
● Layout Manager, Library Manager, Preventative Maintenance, Asset Condition Manager, Notiﬁcation Manager, Structure Manager, Automation Manager
Core Training:
● Provide remote train-the-trainer training, up to two (2) sessions on Contractor Asset Builder. Training topics include:
o Contractor Asset Management Administrator
▪ Structure Manager
▪ Library Manager
▪ Layout Manager
PS-10349.1
20 ▪ User/Role Conﬁgurations
o Contractor recommended best practices for expanding the system’s use and/or building assets
● Provide Preventative Maintenance Plans remote train-the-trainer training, up to two (2) sessions. Training topics include:
o Preventative Maintenance
o Contractor recommended best practices for proactive asset management ● Provide Advanced Inspections, Asset Condition Manager, and Asset Risk remote train-the-trainer training, up to three (3) sessions. Training topics include:
o Performance Management
▪ Prediction Groups
▪ Minimum Condition Groups
▪ Activities and Impacts
▪ Criticality Factor
▪ Install/Replaced Dates
o Business Risk Exposure
▪ Risk
▪ Consequence of Failure
▪ Probability of Failure
o Contractor recommended best practices for Asset Risk Functionality , advanced inspections and condition management
● Provide Internal Request remote train-the-trainer training, up to two (2) sessions.

Training topics include:
o Internal Requests
▪ Users
▪ Views
▪ Issue Library settings and management
o Contractor recommended best practices for advanced request management Completion Criteria
● Core Training and train-the-trainer has been conducted.

Launch

Contractor will:
● Provide remote, up to eight (8) hours, web conferences, of working sessions to answer any questions following solution acceptance.

Completion Criteria:
● Go Live Support has been conducted.

PS-10349.1
21 311 Request Management
Initiate
Contractor will:
● Conduct a project kickoff to align goals, roles, scope, and approach. ● Provision Government App Builder environment; conﬁgure initial roles ● Run discovery/working sessions to conﬁrm high‑level requirements across channels (web, and mobile‑browser).
● Create initial conﬁguration backlog in shared workspace City will:
● Identify stakeholders; ensure attendance at kickoff and working sessions. ● Conﬁrm environment access and user roles.
● Provide process documentation (current service catalog, scripts, categories), reporting examples, and regulatory/retention requirements. ● Review and approve initial conﬁguration backlog and project schedule.

Assumptions:
● Contractor will use standard templates and intake patterns unless otherwise agreed in writing.
● Branding and content style guides provided by City (if applicable) Completion Criteria:
● Kickoff completed with documented actions.
● Access conﬁrmed for core users.
● Initial backlog and plan approved.
● Shared workspace established.

Validate
Contractor will:
● Facilitate validation workshop to conﬁrm requirements, dependencies, and acceptance criteria across intake channels, routing rules, SLAs, and reporting. ● Present reﬁned backlog, timeline, and resource plan for sign‑off. ● Validate user access, permissions, and environment readiness. ● Update artifacts based on feedback prior to conﬁguration.

City will:
● Attend validation with decision‑makers and SMEs (call center, departmental responders, IT/GIS).
● Conﬁrm access to needed systems and tools (GIS, work order/asset mgmt, ERP/ﬁnance, SSO, legacy data).
● Review and sign off on backlog and plan.
● Resolve internal dependencies that could block conﬁguration.

Assumptions:
● Any additional requirements identiﬁed will be assessed for scope and schedule impact.

Completion Criteria:

PS-10349.1
22 ● City sign‑off on plan and backlog.
● Access validated.
● No outstanding blockers to start Conﬁgure.
● Readiness checkpoint logged in project documentation.

Conﬁgure
Service Catalog
Contractor will:
● Deﬁne catalog taxonomy and metadata; conﬁgure categories, subcategories, and article templates
● Provide enablement on ongoing content governance.

City will:
● Supply existing catalog lists and knowledge content; designate content owners ● Review layouts and content structure; approve ﬁnal catalog and initial article set.

Assumptions:
● Content writing and localization are City responsibilities unless otherwise contracted.
● External website CMS updates (outside of the 311 portal) are out of scope.

Completion Criteria:
● Service catalog conﬁgured and linked to intake workﬂows. ● Initial knowledge base articles published.
● Governance approach documented.

Service Request Intake & Form (Web & Browser Accessible Mobile) Contractor will:
● Conﬁgure up to twenty (20) service request types.
● Request types must follow a common template structure and share substantially similar ﬁelds, logic, routing, and layout patterns.
● Request types that materially differ in workﬂow, data structure, routing logic, or integration behavior may be considered out of scope subject to change order. ● Support request types spanning no more than ten (10) distinct departments. ● Conﬁgure:
○ Standard Fields (text, dropdown, multi-select, date, etc.) ○ Required/optional ﬁeld validation
○ Conditional visibility logic (limited to standard platform capabilities) ○ File attachments (standard limits apply)
○ Standard layouts using existing form components
● Conﬁgure Internal (non-public) request types within the same thirty request total. ○ No additional request type allotment is provided for internal-only forms. ○ Internal forms must follow the same structural guardrails as public forms. ● Implement address capture and geocoding using standard Contractor capabilities and/or existing GIS integrations where in scope.
● Geofencing will follow one of the following supported models:
○ A single global geofence applied across all requests types, or PS-10349.1
23 ○ Department-level geofencing applied consistently across all request types within that department.
● Unique geofencing per individual request type is limited and must remain within standard conﬁguration capabilities.
○ Complex geospatial logic, custom map layers, new GIS data creation, or advanced spatial analysis is out of scope unless otherwise speciﬁed. ● Anonymous Portal:
○ Contractor will conﬁgure an anonymous submission experience using a service account for intake processing.
○ reCAPTCHA or equivalent bot-prevention controls.
● Anonymous Submissions:
○ Must use the same conﬁgured public request types (no additional forms created for anonymous intake)
○ Cannot be used for internal-only request types.
○ Will not support follow-up requests for additional information. ○ Cannot be converted to registered-user submission after submission. ○ May be rejected or routed to EAM for work order consideration where applicable.
● Two-way communication, anonymous status tracking beyond standard conﬁrmation messaging, or anonymous-to-registered account conversion is out of scope unless explicitly stated.
●
Constituent Dashboard:
○ Conﬁguration will leverage existing template-based constituent dashboards using standard platform components.
○ Contractor will provide advisory guidance on accessibility and user experience best practices.
○ Custom UI development, custom front-end coding, or standalone website development is not included
● External resources or websites may be added as buttons or tiles that function as standard hyperlinks redirecting users to publicly available URLs. Embedding external systems or custom integrations is out of scope unless otherwise speciﬁed. ● Conduct review sessions and iterate to ﬁnalize.

City will:
● Provide ﬁeld‑level requirements, current scripts, categories, and mandatory data elements.
● Participate in reviews; provide consolidated feedback. ● Validate permissions, logic, and layouts for internal and resident users ● Approve ﬁnal conﬁgurations.

Assumptions:
● Designs leverage standard form capabilities and controls ● Public site branding assets provided by City.

Completion Criteria:
● Forms/tables conﬁgured and tested
● Address capture/geocoding validated (if in scope).
● Required data capture conﬁrmed
● City approval received.

PS-10349.1
24 Mobile Application (iOS & Android)
Mobile Access (iOS & Android)
● Contractor will provide a mobile application experience for iOS and Android devices designed to support constituent-facing 311/CRM request submission and status visibility.

Scope of Mobile Functionality:
● The mobile application will support core constituent workﬂows, including:
○ Submission of service requests using conﬁgured public request types ○ Address/location capture (subject to device capabilities and conﬁgured GIS services)
○ Photo/ﬁle attachments (subject to standard platform limits) ○ Viewing request status updates (where applicable)
○ Standard conﬁrmation and notiﬁcation behavior
● The mobile experience will leverage the same conﬁgured public request types as deﬁned in the Service Request Intake & Form section.

Functional Boundaries:
● The mobile application is designed primarily for constituent request intake and status viewing.
● Administrative conﬁguration, workﬂow management, reporting, advanced triage, SLA management, and internal processing features are supported through the web application only unless otherwise speciﬁed.
● Feature parity between mobile and web applications is not assumed. ● Advanced UI customization, custom mobile workﬂows, or device -speciﬁc enhancements beyond standard capabilities are out of scope unless explicitly stated.

Assumptions:
● The mobile application will use standard platform components and supported device capabilities.
● Submission performance and certain functionality may vary based on device type, operating system version, connectivity, and permissions granted by the end user. ● Publication to Apple App Store and Google Play will follow standard platform release processes and approval timelines.

Completion Criteria:
● Mobile application available for iOS and Android distribution. ● Core request submission functionality tested and validated. ● City approval received.

Workﬂow, Triage & Routing
Contractor will:
● Conﬁgure routing rules, ownership groups, task states, reassignment, and collaboration steps.
● Conﬁgure workﬂow states for up to thirty (30) service requests types using a shared workﬂow framework.
● Establish routing rules based on:
○ Request Type
○ Department
PS-10349.1
25 ○ Standard priority level
○ Location (if applicable)
● Conﬁgure department-level ownership groups and queues aligned to the deﬁned (less than or equal to 10), including:
○ A primary queue per department (additional sub-queues or specialty are out of scope unless explicitly stated).
○ Queue visibility based on assigned department role.
● Conﬁgure standard task states using a standardized lifecycle (e.g., Submitted, In Progress, Oh Hold, Closed, Completed), including an optional standardized RFI (Request for Information) pattern where supported.
○ Department-speciﬁc workﬂow/state variants must remain minimal and within standard conﬁguration capabilities.
○ Complex, highly branched workﬂows or materially different state model per department/request type may require change order.
● Document agreed workﬂows at a high level and conduct structured testing sessions.
●
Queue Assignment Model
○ Assignments will occur at the department queue level only. ○ Only one (1) queue per department is included in scope. ○ Automatic assignment to speciﬁc individuals is out of scope. ○ Load balancing, workload distribution logic, skill-based routing, or availability-based assignment is not included.
○ Vacation rules, backup assignments, and dynamic reassignment automation are not included.
○ Escalation routing beyond initial department-level assignment is not included unless otherwise speciﬁed.

City will:
● Deﬁne departmental ownership of groups (less than or equal to 10 departments). ● Identify users assigned to each departmental group queue (limited to scope role counts).
● Provide current process maps, ownership matrices, and escalation criteria for conﬁguration.
● Participate in testing and provide consolidated feedback; approval ﬁnal logic in writing.
● Resolve GIS boundary questions, including conﬂicts/overlaps in service areas, if location-based routing is required.

Assumptions:
● Routing an assignment will be department-based, not user-based. ● No custom assignment logic will be developed.
● Workﬂow states will be standardized across departments wherever possible. ● Automation will use standard workﬂow options; custom code is out of scope unless listed.
● Location‑based routing requires GIS layers and data provided by City. ● Reﬁnement is limited to up to two (2) rounds of consolidated changes following workﬂow review sessions. Additional iterations may require a change order.

Completion Criteria:

PS-10349.1
26 ● Workﬂows live with routing functioning.
● Ownership groups and queues conﬁgured.
● Approval received from City.

SLAs, Notiﬁcations & Escalation
Contractor will:
● Conﬁgure SLA tracking using standard Contractor 311/CRM capabilities, including SLA timers for:
○ Acknowledgement
○ First Response
○ Resolution
● Conﬁgure standard SLA indicators and monitoring views/dashboards available within the platform.
● Conﬁgure resident notiﬁcations and status updates using standard communication capabilities:
○ Email and/or SMS (when in scope and when City provides required communication templates)
● Conﬁgure escalations to supervisors and leadership.
● SLA conﬁguration is limited to up to three (3) SLA policies across all request types unless otherwise speciﬁed.
○ An “SLA Policy” is deﬁned as a single set of thresholds and calendar rules that may apply to multiple request types/departments.
● Escalations do not include automatic reassignment, rerouting to additional queues, or dynamic workload redistribution.
● Notiﬁcations are limited to standard event -based updates (e.g., submission received, status changed, closed) using standard template capabilities. Custom notiﬁcation logic beyond standard triggers may require a change order.

City will:
● Provide SLA deﬁnitions per category and business hours/holiday calendars. (policy name, threshold values, and applicability by request type/department) ● Approve notiﬁcation templates and escalation paths.
● Validate end‑to‑end SLA behavior.

Assumptions:
● SMS/email providers and associated fees are City responsibilities unless otherwise contracted.
● Two‑way messaging outside of standard capabilities may require a Change Order.

Completion Criteria:
● *SLAs operational with monitoring in dashboards
● Notiﬁcations and escalations tested
● City approval received.

Integration with Contractor Enterprise Asset Management (EAM) Contractor will:
● Conﬁgure an integration between Contractor 311/Constituent Request Management (CRM) and Contractor EAM using standard, supported capabilities so that:

PS-10349.1
27 ○ Eligible 311 requests may create 311 requests, which will enable users to issue work orders, and
○ EAM work order status updates may be reﬂected back in 311 (including the public status page where applicable).
● Deﬁne decision rules for work-order creation (e.g., by category/high-alert ﬂag). ● Conﬁgure ﬁeld mapping between 311/CRM and EAM for a standard integration set, including (as applicable):
○ 311 Request ID / External Reference
○ Request Type
○ Location/Address
○ Requester(or)
○ Description/Comments
○ File Attachment(s)
● Conﬁgure status mapping for resident -facing visibility (e.g., translating EAM internal statuses into simpliﬁed public statuses) using standard platform capabilities.
● Implement standard API -based integration or agreed method; handle error validation and retries.
● Conﬁgure read-backs of EAM status/progress for resident -friendly display on the status page.
● Provide technical runbook and data-mapping documentation. ● Integration is limited to one (1) EAM request type creation pathway per eligible request type.
● Field mapping is limited to twenty (20) mapped ﬁelds, or the limit already conﬁgured in EAM, unless otherwise speciﬁed.
● The integration does not support:
○ Custom middleware, custom EAM extensions, or non-standard API capabilities.
● Advanced exception handling (custom alerting workﬂows, automated replay tooling, or custom integration dashboards) is out of scope unless explicitly stated.

City Responsibilities:
● Provide or conﬁrm EAM environment details, credentials, and test data; conﬁrm asset/address cross-walks.
● Validate mapping, status cross-reference, and acceptance criteria. ● Coordinate with any internal EAM administrators for endpoint access/windows.

Boundaries & Assumptions
● Scope is limited to Contractor 311 Request Management ↔ Contractor EAM integration; other third-party systems are out of scope. ● Integration follows standard, supported API capabilities; custom EAM extensions are excluded.
● Delays in access, credentials, or test data availability may impact delivery timeline.

Completion Criteria:
● End-to-end tests demonstrate work -order creation and status synchronization; integration documentation delivered; stakeholder approval received.

PS-10349.1
28 Integration with Contractor Permitting and Licensing (PLC) Contractor will:
● Conﬁgure an integration between Contractor 311/Constituent Request Management (CRM) and Contractor PLC using standard, supported capabilities so that:
○ Eligible 311 requests may create 311 requests, which will enable users to issue work orders for code enforcement requests, and
○ PLC work order status updates may be reﬂected back in 311 (including the public status page where applicable).
● Deﬁne decision rules for work-order creation (e.g., by category/high-alert ﬂag). ● Conﬁgure ﬁeld mapping between 311/CRM and PLC for a standard integration set, including (as applicable):
○ 311 Request ID / External Reference
○ Request Type
○ Location/Address
○ Requester(or)
○ Description/Comments
○ File Attachment(s)
● Conﬁgure status mapping for resident-facing visibility (e.g., translating PLC internal statuses into simpliﬁed public statuses) using standard platform capabilities. ● Implement standard API-based integration or agreed method; handle error validation and retries.
● Conﬁgure read-backs of PLC status/progress for resident-friendly display on the status page.
● Provide technical runbook and data-mapping documentation. ● Integration is limited to one (1) PLC request type creation pathway per eligible request type.
● Field mapping is limited to twenty (20) mapped ﬁelds, or the limit already conﬁgured in PLC, unless otherwise speciﬁed.
● The integration does not support:
○ Custom middleware, custom PLC extensions, or non-standard API capabilities.
● Advanced exception handling (custom alerting workﬂows, automated replay tooling, or custom integration dashboards) is out of scope unless explicitly stated.

City Responsibilities:
● Provide or conﬁrm PLC environment details, credentials, and test data; conﬁrm asset/address cross-walks.
● Validate mapping, status cross-reference, and acceptance criteria. ● Coordinate with any internal PLC administrators for endpoint access/windows.

Boundaries & Assumptions
● Scope is limited to Contractor 311 Request Management ↔ Contractor PLC integration; other third-party systems are out of scope. ● Integration follows standard, supported API capabilities; custom PLC extensions are excluded.
● Delays in access, credentials, or test data availability may impact delivery timeline.

PS-10349.1
29 Completion Criteria:
● End-to-end tests demonstrate work-order creation and status synchronization; integration documentation delivered; stakeholder approval received.

Reporting & Dashboards
Contractor will:
● Conﬁgure reports (up to 10), ﬁlters, and visualizations; enable exports suitable for council/board/public dashboards (up to 6 unique dashboards) ● Provide enablement on managing report parameters and publishing.

City will:
● Deﬁne KPIs and reporting needs; provide examples of internal and public reporting. ● Review layouts and logic; test exports; designate owners for ongoing reporting.

Assumptions:
● Reports rely on data available in conﬁgured tables or approved imports/integrations.
● Complex, custom templates outside of standard exports may require a Change Order.

Completion Criteria:
● Reports and dashboards live with accurate data.
● Permissions veriﬁed; export formats tested
● City approval received.

Train
Administrator & Dispatcher Training
Contractor will:
● Deliver live virtual training; provide documentation and recordings. ● Cover core admin tasks (form edits, report creation, workﬂow adjustments, SLA conﬁguration, permission controls).
● Assign practice scenarios.

City will:
● Identify admin/dispatcher users; attend training; complete practice exercises; conﬁrm understanding of responsibilities.

Assumptions:
● Training delivered remotely unless otherwise speciﬁed. ● Attendees are available at scheduled times.

Completion Criteria:
● Admin training completed; access conﬁrmed for relevant users. ● Practice scenarios validated
PS-10349.1
30 ● City conﬁrms readiness to manage conﬁguration post‑launch.

Agent/Field Staff Enablement
Contractor will:
● Deliver role‑based sessions and quick‑reference guides. ● Demonstrate status updates, assignment, and completion workﬂows.

City will:
● Ensure attendance; provide device policies and any mobile restrictions. ● Validate that training aligns to ﬁeld operation needs.

Assumptions:
● Device procurement and management are City responsibilities. ● Offline mode support is limited to generally available capabilities.

Completion Criteria:
● Agent/ﬁeld sessions delivered; materials distributed. ● Readiness sign‑off received from departmental leads.

Public/User-Facing Collateral
Contractor will:
● Draft how‑to guides with screenshots and FAQs; deliver PDF and web‑optimized formats.
● Review drafts with City for accuracy; ﬁnalize collateral.

City will:
● Review and provide feedback; approve ﬁnal content; handle distribution and any localization.

Assumptions:
● Content reﬂects current forms and processes at go‑live. ● Accessibility/translation needs identiﬁed by City.

Completion Criteria:
● Guides ﬁnalized and approved; published via City channels.

Launch
Contractor will:
● Monitor adoption; resolve conﬁguration questions and issues. ● Conduct ﬁnal stakeholder review; transition to City Success.

City will:
● Monitor usage; report issues; attend ﬁnal review; sign solution acceptance.

PS-10349.1
31 Assumptions:
● Hypercare support is time‑boxed per the Project Plan. ● Post‑launch enhancements will be prioritized via City Success or Change Orders.

Completion Criteria:
● Hypercare window closed; known issues addressed or queued. ● Stakeholder review completed; solution acceptance signed.

PS-10349.1
32 Exhibit 2: Technical Requirements
Procurement Technical Requirements
Logo
● .png or .jpg ﬁle
● At least 300KB but not larger than 500KB
Vendor List
● Single Flat ﬁle
● .csv or .xlsx format
Historical/Active Contracts
● Single Flat ﬁle based on mapping document provided by Contractor ● .csv or .xlsx format
Sample Documents or Boilerplate Templates
● PDF or Word format, including all related attachments and documents.

Templates
● All templates are assumed to be samples unless speciﬁed as a boilerplate. A boilerplate template document that can be reused more than once without any substantive change. ● All templates assume up to 50 pages in length each unless otherwise speciﬁed in Exhibit 1.

Page count includes all attachments, forms, notices, and other documentation ● All templates are assumed to be non-construction unless otherwise speciﬁed in Exhibit 1. A “Construction” template refers to templates inclusive of requirements, speciﬁcations, and conditions for construction projects: including any of the following examples but not limited to: regulations, codes, and standards, risk management, insurance management, dispute resolution mechanisms, phases, tasks, dependencies, materials, equipment, construction methods, liability and warranty periods.

Admin Documents
● PDF or Word format

Permitting & Licensing Technical Requirements
Master Address Table
● All addresses must have a unique ID
● Flat ﬁle, .csv, .xls, .xlsx, .txt with headers
● Parcels and address points recommended
● Recommended source data: Esri GIS, Alternative source options include: Assessor’s database, E911
Esri ArcGIS
● A single publicly-accessible secure Esri REST API URL PS-10349.1
33 ArcGIS Flags
● Polygon Layer(s) via Esri REST API URL, Polylines and points are not supported ● Flags will be populated via the same Publicly-accessible secure Esri REST API URL as provided for the Esri ArcGIS integration.

Financial and Record Exports
● Required format (columns) and sample document
Autoﬁlls using City source data
● Flat ﬁle, .csv, .xls, .xlsx, .txt with headers
Bluebeam
● Bluebeam Core or Complete license(s)
● User(s) must have Bluebeam Revu 21 downloaded
Current application forms, workﬂows, fee structures, and output documents ● PDF, Word, .csv, .xls, .xlsx with headers
SSO
● SAML or HTTPS certiﬁcate, Whitelist Contractor in City VPN or ﬁrewall

Government App Builder Technical Requirements
● Migration
○ All data must be accessible to Contractor in Excel or CSV format ○ Maximum historical record count: 500
● Flat File Integrations
○ City must
■ Provide Contractor with the export ﬁle (a delimited ﬁle) from the external system
■ Automate the export and/or import of data into and out of the external system.
● API Integrations
○ City is responsible for:
■ Fees associated with purchasing the external system
■ Providing Contractor with access to the API and/or access to technical staff from that vendor.
■ Access to a test instance of the third party API including a URL, authentication credentials, and relevant documentation. ■ Changes to scope resulting from a change in the third-party vendor’s API. ■ Testing expected workﬂows and data in both test and production environments
○ To display a location on a map, the third party system must be able to provide location data via their API, as shapes or coordinates. Text addresses are limited to populating address ﬁelds.
55575.18100\42906602.1

BB&K (2024)

ATTACHMENT “B”

QUOTE / PRICING

1602 Village Market Blvd SE, Suite 320
Leesburg, VA20175 USA
Cage Code: 7QV38
UEI Number Y7D5MXRU2839
DUNS# 080431574
Federal Tax ID: 81-3911287
Business Size: Small Business
Date: 4/23/2026, 4:43 PM
Phone: 571 707-4130
Fax: 571-291-4119
Email: [email protected]
Vertosoft Contact: Carly Moore
Phone: (540) 998-8361
Email: [email protected]
Vertosoft Quote for OpenGov - City of Palm Springs, CA
Contract: Sourcewell: 060624-VTO
Quote #: Q-22041
Expires On: 5/29/2026
Ship To
City of Palm Springs, CA
Quote For:

Name:

Company: City of Palm Springs, CA
Email:

Phone:

PAYMENT TERMS DELIVERY METHOD PAYMENT METHOD VERTOSOFT CUST ID SUPPLIER REF Net 60 Electronic Check/ACH/Credit Card
Overall POP Start Date: 6/1/2026
Overall POP End Date: 5/31/2031
Term 1 6/1/2026 - 5/31/2027
PART # DESCRIPTION QTY MSRP UNIT PRICE EXTENDED

OG-TWHX-
B300500M-AR-3Y
Asset Management Base Bundle - Between $300-
500 Million - 3Y

1.00 103,360.00 $40,655.19 $40,655.19

OG-TWEJ-
B300500M-AR-3Y
Asset Management Expert Services: Accelerate -
Between $300-500 Million - 3Y

1.00 36,750.00 $16,061.22 $16,061.22

OG-TWAW-
B300500M-AR-3Y
Facilities Domain - Between $300-500 Million -
3Y

1.00 79,735.00 $34,847.58 $34,847.58

OG-TWHT-
B300500M-AR-3Y
OpenGov 311 - Between $300-500 Million - 3Y 1.00 86,953.00 $38,001.82 $38,001.82

OG-TWHG-
B300500M-AR-3Y
OpenGov Constituent Relationship Management -
Between $300-500 Million - 3Y

1.00 134,744.00 $58,888.35 $58,888.35

Page 1 of 5 ends

PART # DESCRIPTION QTY MSRP UNIT PRICE EXTENDED

OG-TWAY-
B300500M-AR-3Y
Parks & Recreation Domain - Between $300-500
Million - 3Y

1.00 71,884.00 $31,416.42 $31,416.42

OG-TWIB-
B300500M-AR-3Y
Permitting and Licensing - Code Enforcement
Bundle - Between $300-500 Million - 3Y

1.00 55,173.00 $21,701.77 $21,701.77

OG-SWFU-
B300500M-AR-3Y
Solicitation Development - Between $300-500
Million - 3Y

1.00 30,246.00 $13,218.87 $13,218.87

OG-SWFS-
B300500M-AR-3Y
Supplier Engagement, Evaluations and Awards -
Between $300-500 Million - 3Y

1.00 30,246.00 $13,218.87 $13,218.87

OG-TWBC-
B300500M-AR-3Y
Transportation Domain - Between $300-500
Million - 3Y

1.00 79,735.00 $34,847.58 $34,847.58

OG-PSBG-
B300500M-OT-0Y
Professional Services Deployment - Prepaid -
Between $300-500 Million - 0Y
829.00 294.00 $210.00 $174,090.00
OG-Travel-Expense-
Reimb
OpenGov - designed for reimbursable travel
expenditures. **Estimate expense

On-Site Implementation

BILLED AS INCURRED NOT TO EXCEED
2,800.00 100,000.00 $1.00 $2,800.00
Term 1 TOTAL: $479,747.67
Term 2 6/1/2027 - 5/31/2028
PART # DESCRIPTION QTY MSRP UNIT PRICE EXTENDED

OG-TWHX-
B300500M-AR-3Y
Asset Management Base Bundle - Between $300-
500 Million - 3Y

1.00 103,360.00 $42,687.97 $42,687.97

OG-TWEJ-
B300500M-AR-3Y
Asset Management Expert Services: Accelerate -
Between $300-500 Million - 3Y

1.00 36,750.00 $16,864.28 $16,864.28

OG-TWAW-
B300500M-AR-3Y
Facilities Domain - Between $300-500 Million -
3Y

1.00 79,735.00 $36,589.96 $36,589.96

OG-TWHT-
B300500M-AR-3Y
OpenGov 311 - Between $300-500 Million - 3Y 1.00 86,953.00 $39,901.90 $39,901.90

OG-TWHG-
B300500M-AR-3Y
OpenGov Constituent Relationship Management -
Between $300-500 Million - 3Y

1.00 134,744.00 $61,832.76 $61,832.76

OG-TWAY-
B300500M-AR-3Y
Parks & Recreation Domain - Between $300-500
Million - 3Y

1.00 71,884.00 $32,987.24 $32,987.24

OG-TWIB-
B300500M-AR-3Y
Permitting and Licensing - Code Enforcement
Bundle - Between $300-500 Million - 3Y

1.00 55,173.00 $22,786.86 $22,786.86

OG-TWBA-
B300500M-AR-3Y
Signal Domain - Between $300-500 Million - 3Y 1.00 67,500.00 $30,975.20 $30,975.20

OG-SWFU-
B300500M-AR-3Y
Solicitation Development - Between $300-500
Million - 3Y

1.00 30,246.00 $13,879.82 $13,879.82

OG-SWFS-
B300500M-AR-3Y
Supplier Engagement, Evaluations and Awards -
Between $300-500 Million - 3Y

1.00 30,246.00 $13,879.82 $13,879.82

OG-TWBC-
B300500M-AR-3Y
Transportation Domain - Between $300-500
Million - 3Y

1.00 79,735.00 $36,589.96 $36,589.96

Page 2 of 5 ends

PART # DESCRIPTION QTY MSRP UNIT PRICE EXTENDED

OG-TWBD-
B300500M-AR-3Y
Walkability Domain - Between $300-500 Million -
3Y

1.00 67,500.00 $30,975.20 $30,975.20
Term 2 TOTAL: $379,950.97
Term 3 6/1/2028 - 5/31/2029
PART # DESCRIPTION QTY MSRP UNIT PRICE EXTENDED

OG-TWHX-
B300500M-AR-3Y
Asset Management Base Bundle - Between $300-
500 Million - 3Y

1.00 103,360.00 $44,822.35 $44,822.35

OG-TWEJ-
B300500M-AR-3Y
Asset Management Expert Services: Accelerate -
Between $300-500 Million - 3Y

1.00 36,750.00 $17,707.49 $17,707.49

OG-TWAW-
B300500M-AR-3Y
Facilities Domain - Between $300-500 Million -
3Y

1.00 79,735.00 $38,419.45 $38,419.45

OG-TWHT-
B300500M-AR-3Y
OpenGov 311 - Between $300-500 Million - 3Y 1.00 86,953.00 $41,897.00 $41,897.00

OG-TWHG-
B300500M-AR-3Y
OpenGov Constituent Relationship Management -
Between $300-500 Million - 3Y

1.00 134,744.00 $64,924.41 $64,924.41

OG-TWAY-
B300500M-AR-3Y
Parks & Recreation Domain - Between $300-500
Million - 3Y

1.00 71,884.00 $34,636.60 $34,636.60

OG-TWIB-
B300500M-AR-3Y
Permitting and Licensing - Code Enforcement
Bundle - Between $300-500 Million - 3Y

1.00 55,173.00 $23,926.22 $23,926.22

OG-TWBA-
B300500M-AR-3Y
Signal Domain - Between $300-500 Million - 3Y 1.00 67,500.00 $32,523.97 $32,523.97

OG-SWFU-
B300500M-AR-3Y
Solicitation Development - Between $300-500
Million - 3Y

1.00 30,246.00 $14,573.81 $14,573.81

OG-SWFS-
B300500M-AR-3Y
Supplier Engagement, Evaluations and Awards -
Between $300-500 Million - 3Y

1.00 30,246.00 $14,573.81 $14,573.81

OG-TWBD-
B300500M-AR-3Y
Walkability Domain - Between $300-500 Million -
3Y

1.00 67,500.00 $38,419.45 $38,419.45

OG-TWBC-
B300500M-AR-3Y
Transportation Domain - Between $300-500
Million - 3Y

1.00 79,735.00 $32,523.97 $32,523.97
Term 3 TOTAL: $398,948.53
Term 4 6/1/2029 - 5/31/2030
PART # DESCRIPTION QTY MSRP UNIT PRICE EXTENDED

OG-TWHX-
B300500M-AR-3Y
Asset Management Base Bundle - Between $300-
500 Million - 3Y

1.00 103,360.00 $47,063.48 $47,063.48

OG-TWEJ-
B300500M-AR-3Y
Asset Management Expert Services: Accelerate -
Between $300-500 Million - 3Y

1.00 36,750.00 $18,592.87 $18,592.87

OG-TWAW-
B300500M-AR-3Y
Facilities Domain - Between $300-500 Million -
3Y

1.00 79,735.00 $40,340.43 $40,340.43

OG-TWHT-
B300500M-AR-3Y
OpenGov 311 - Between $300-500 Million - 3Y 1.00 86,953.00 $43,991.85 $43,991.85

Page 3 of 5 ends

PART # DESCRIPTION QTY MSRP UNIT PRICE EXTENDED

OG-TWHG-
B300500M-AR-3Y
OpenGov Constituent Relationship Management -
Between $300-500 Million - 3Y

1.00 134,744.00 $68,170.62 $68,170.62

OG-TWAY-
B300500M-AR-3Y
Parks & Recreation Domain - Between $300-500
Million - 3Y

1.00 71,884.00 $36,368.43 $36,368.43

OG-TWIB-
B300500M-AR-3Y
Permitting and Licensing - Code Enforcement
Bundle - Between $300-500 Million - 3Y

1.00 55,173.00 $25,122.51 $25,122.51

OG-TWBA-
B300500M-AR-3Y
Signal Domain - Between $300-500 Million - 3Y 1.00 67,500.00 $34,150.16 $34,150.16

OG-SWFU-
B300500M-AR-3Y
Solicitation Development - Between $300-500
Million - 3Y

1.00 30,246.00 $15,302.49 $15,302.49

OG-SWFS-
B300500M-AR-3Y
Supplier Engagement, Evaluations and Awards -
Between $300-500 Million - 3Y

1.00 30,246.00 $15,302.49 $15,302.49

OG-TWBC-
B300500M-AR-3Y
Transportation Domain - Between $300-500
Million - 3Y

1.00 79,735.00 $40,340.43 $40,340.43

OG-TWBD-
B300500M-AR-3Y
Walkability Domain - Between $300-500 Million -
3Y

1.00 67,500.00 $34,150.16 $34,150.16
Term 4 TOTAL: $418,895.92
Term 5 6/1/2030 - 5/31/2031
PART # DESCRIPTION QTY MSRP UNIT PRICE EXTENDED

OG-TWHX-
B300500M-AR-3Y
Asset Management Base Bundle - Between $300-
500 Million - 3Y

1.00 103,360.00 $49,416.65 $49,416.65

OG-TWEJ-
B300500M-AR-3Y
Asset Management Expert Services: Accelerate -
Between $300-500 Million - 3Y

1.00 36,750.00 $19,522.51 $19,522.51

OG-TWAW-
B300500M-AR-3Y
Facilities Domain - Between $300-500 Million -
3Y

1.00 79,735.00 $42,357.45 $42,357.45

OG-TWHT-
B300500M-AR-3Y
OpenGov 311 - Between $300-500 Million - 3Y 1.00 86,953.00 $46,191.44 $46,191.44

OG-TWHG-
B300500M-AR-3Y
OpenGov Constituent Relationship Management -
Between $300-500 Million - 3Y

1.00 134,744.00 $71,579.16 $71,579.16

OG-TWAY-
B300500M-AR-3Y
Parks & Recreation Domain - Between $300-500
Million - 3Y

1.00 71,884.00 $38,186.85 $38,186.85

OG-TWIB-
B300500M-AR-3Y
Permitting and Licensing - Code Enforcement
Bundle - Between $300-500 Million - 3Y

1.00 55,173.00 $26,378.61 $26,378.61

OG-TWBA-
B300500M-AR-3Y
Signal Domain - Between $300-500 Million - 3Y 1.00 67,500.00 $35,857.68 $35,857.68

OG-SWFU-
B300500M-AR-3Y
Solicitation Development - Between $300-500
Million - 3Y

1.00 30,246.00 $16,067.61 $16,067.61

OG-SWFS-
B300500M-AR-3Y
Supplier Engagement, Evaluations and Awards -
Between $300-500 Million - 3Y

1.00 30,246.00 $16,067.61 $16,067.61

OG-TWBC-
B300500M-AR-3Y
Transportation Domain - Between $300-500
Million - 3Y

1.00 79,735.00 $42,357.45 $42,357.45

Page 4 of 5 ends

PART # DESCRIPTION QTY MSRP UNIT PRICE EXTENDED

OG-TWBD-
B300500M-AR-3Y
Walkability Domain - Between $300-500 Million -
3Y

1.00 67,500.00 $35,857.68 $35,857.68
Term 5 TOTAL: $439,840.70
TOTAL: $479,747.67
Annual invoices will be delivered by the start of each consecutive annual period. Payment of invoices shall be annually in advance. Any Professional Services shall be performed pursuant to the attached Statement of Work, if any.

Quote Terms

By purchasing the products and services described in this order form, the Customer is expressly agreeing to the End User Agreement published at https://www.vertosoft.com/terms-and-conditions-opengov

Taxes: Sales tax shall be added at the time of an invoice, unless a copy of a valid tax exemption or resale certificate is provided.

Credit Card Orders: Additional fees may apply if paying by credit card.

All Purchase Orders must include: End User Name, Phone Number, Email Address, Purchase Order Number, Government Contract Number or Our Quote Number, Bill-To and Ship-To Address (Cannot ship to a PO Box), Period of Performance (if applicable), and a Signature of a duly Authorized Representative.

Page 5 of 5 ends

55575.18100\42906602.1

BB&K (2024)

ATTACHMENT “C”

INSURANCE REQUIREMENTS

1.1 Types of Insurance. Contractor shall procure and maintain, at its sole cost and expense, the insurance described herein. The insurance shall be for the duration of this Agreement and includes any extensions, unless otherwise specified in this Agreement. The insurance shall be procured in a form and content satisfactory to City. The insurance shall apply against claims which may arise from the Contractor's performance of Work under this Agreement, including Contractor's agents, representatives, or employees. In the event the City Manager determines that the Work or Services to be performed under this Agreement creates an increased or decreased risk of loss to the City, the Contractor agrees that the minimum limits of the insurance policies may be changed accordingly upon r eceipt of written notice from the City Manager or his designee. Contractor shall immediately substitute any insurer whose A.M. Best rating drops below the levels specified in this Agreement. Except as otherwise authorized below for contract liability (errors and omissions) insurance, all insurance provided under this Agreement shall be on an occurrence basis. The minimum amount of insurance required shall be as follows:

A. Errors and Omissions Insurance. Contractor shall obtain and maintain in full force and effect throughout the term of this Agreement, standard industry form contract liability (errors and omissions) insurance coverage in an amount of not less than one million dollars ($1,000,000.00) per occurrence and two- million dollars ($2,000,000.00) annual aggregate, in accordance with the provisions of this section.
required
X is not required;
(1) Contractor shall either: (a) certify in writing to the City that Contractor is unaware of any contract liability claims made against Contractor and is unaware of any facts which may lead to such a claim against Contractor; or (b) if Contractor does not provide the certification under (a), Contractor shall procure from the contract liability insurer an endorsement providing that the required limits of the policy shall apply separately to claims arising from errors and omissions in the rendition of services under this Agreement. (2) If the policy of insurance is written on a “claims made” basis, the policy shall be continued in full force and effect at all times during the term of this Agreement, and for a period of three (3) years from the date of the completion of the Services provided hereunder. In the event of termination of the policy during this period, Contractor shall obtain continuing insurance coverage for the prior acts or omissions of Contractor during the course of performing Services under the terms of this Agreem ent. The coverage shall be evidenced by either a new policy evidencing no gap in coverage, or by obtaining separate extended “tail” coverage with the present or new carrier or other insurance arrangements providing for complete coverage, either of which shall be subject to the written approval by the City Manager. (3) In the event the policy of insurance is written on an “occurrence” basis, the policy shall be continued in full force and effect during the term of this Agreement, or until completion of the Services provided for in this Agreement, whichever is later . In the event of termination of the policy during this period, new coverage shall immediately be obtained to ensure coverage during the entire course of performing the Services under the terms of this Agreement.

B. Workers’ Compensation Insurance. Contractor shall obtain and maintain, 55575.18100\42906602.1

BB&K (2024)

in full force and effect throughout the term of this Agreement, workers’ compensation insurance in at least the minimum statutory amounts, and in compliance with all other statutory requirements, as required by the State of California. Contractor agrees t o waive and obtain endorsements from its workers’ compensation insurer waiving subrogation rights under its workers’ compensation insurance policy against the City and to require each of its subcontractors, if any, to do likewise under their workers’ compensation insurance policies. If Contractor has no employees, Contractor shall complete the City’s Request for Waiver of Workers’ Compensation Insurance Requirement form.

C. Commercial General Liability Insurance . Contractor shall obtain and maintain, in full force and effect throughout the term of this Agreement, a policy of commercial general liability insurance written on a per occurrence basis with a combined single limit of at least one million dollars ($1,000,000.00) and two million dollars ($2,000,000.00) general aggregate for bodily injury and property damage including coverages for contractual liability, personal injury, independent contractors, broad form property damage, products and completed operations.

D. Business Automobile Insurance. Contractor shall obtain and maintain, in full force and effect throughout the term of this Agreement, a policy of business automobile liability insurance written on a per occurrence basis with a single limit liability in the amount of one million dollars ($1,000,000.00) bodily injury and property damage. The policy shall include coverage for owned, non-owned, leased, and hired cars.

E. Employer Liability Insurance. Contractor shall obtain and maintain, in full force and effect throughout the term of this Agreement, a policy of employer liability insurance written on a per occurrence basis with a policy limit of at least one million dollars ($1,000,000.00) for bodily injury or disease. 1.2 Deductibles and Self -Insured Retentions. Any deductibles or self-insured retentions must be declared to and approved by the City Manager or his/her designee prior to commencing any work or services under this Agreement. Contractor guarantees payment of all deductibles and self-insured retentions. City reserves the right to reject deductibles or self -insured retentions in excess of $10,000, and the City Manager or his/her designee may require evidence of pending claims and claims history as well as evidence of Contractor’s ability to pay claims for all deductible amounts and self-insured retentions proposed in excess of $10,000.

1.3 Other Insurance Requirements. The following provisions shall apply to the insurance policies required of Contractor under this Agreement:

A. For any claims related to this Agreement, Contractor’s coverage shall be primary insurance with respect to the City and its officers, council members, officials, employees, agents, and volunteers. Any insurance or self -insurance maintained by the City and its officers, council members, officials, employees, agents, and volunteers shall be in excess of Contractor’s insurance and shall not contribute with it.

B. Any failure to comply with reporting or other provisions of the policies, including breaches of warranties, shall not affect coverage provided to City and its officers, council members, officials, employees, agents, and volunteers.

C. All insurance coverage and limits provided by Contractor and available or applicable to this Agreement are intended to apply to each insured, including additional insureds, against whom a claim is made or suit is brought to the full extent of the policies. Nothing contained in this Agreement or any other agreement relating to the City or its operations shall limit the application of such insurance coverage.
55575.18100\42906602.1

BB&K (2024)

D. No required insurance coverages may include any limiting endorsement which substantially impairs the coverages set forth in this Agreement (e.g., elimination of contractual liability or reduction of discovery period), unless the endorsement has first been submitted to the City Manager and approved in writing.

E. Contractor agrees to require its insurer to modify insurance endorsements to delete any exculpatory wording stating that failure of the insurer to mail written notice of cancellation imposes no obligation, or that any party will "endeavor" (as opposed to being required) to comply with the requirements of the endorsements. Certificates of insurance will not be accepted in lieu of required endorsements, and submittal of certificates without required endorsements may delay commencement of the Project. It is Contractor’s obligation to ensure timely compliance with all insurance submittal requirements as provided in this Agreement.

F. Contractor agrees to ensure that subcontractors, and any other parties involved with the Project who are brought onto or involved in the Project by Contractor, provide the same minimum insurance coverage required of Contractor. Contractor agrees to monitor and review all such coverage and assumes all responsibility for ensuring that such coverage is provided in conformity with the requirements of this section. Contractor agrees that upon request, all agreements with subcontractors and others engaged in the Project will be submitted to the City for review.

G. Contractor acknowledges and agrees that any actual or alleged failure on the part of the City to inform Contractor of non-compliance with any insurance requirement in no way imposes any additional obligations on the City nor does it waive any rights in this or any other regard.

H. Contractor shall provide proof that policies of insurance required in this Agreement, expiring during the term of this Agreement, have been renewed or replaced with other policies providing at least the same coverage. Proof that such coverage has been ordered shall be submitted prior to expiration. Endorsements as required in this Agreement applicable to the renewing or new coverage shall be provided to City no later than ten (10) days prior to expiration of the lapsing coverage.

I. Requirements of specific insurance coverage features or limits contained in this section are not intended as limitations on coverage, limits, or other requirements, or as a waiver of any coverage normally provided by any given policy. Specific reference to a given coverage feature is for purposes of clarification only as it pertains to a given issue, and is not intended by any party or insured to be limiting or all-inclusive.

J. The requirements in this section supersede all other sections and provisions of this Agreement to the extent that any other section or provision conflicts with or impair the provisions of this section.

K. Contractor agrees to provide immediate notice to City of any claim or loss against Contractor arising out of the Work performed under this Agreement and for any other claim or loss which may reduce the insurance available to pay claims arising out of this Agreement. City assumes no obligation or liability by such notice, but has the right (but not the duty) to monitor the handling of any such claim or claims if they are likely to involve City, or to reduce or dilute insurance available for payment of potential claims.

L. Contractor agrees that the provisions of this section shall not be construed as limiting in any way the extent to which the Contractor may be held responsible for the payment of damages resulting from the Contractor’s activities or the activities of any person or person for 55575.18100\42906602.1

BB&K (2024)

which the Contractor is otherwise responsible.

1.4 Sufficiency of Insurers. Insurance required in this Agreement shall be provided by authorized insurers in good standing with the State of California. Coverage shall be provided by insurers admitted in the State of California with an A.M. Best’s Key Rating of B++, Class VII, or better, unless such requirements are waived in writing by the City Manager or his designee due to unique circumstances.

1.5 Verification of Coverage. Contractor shall furnish City with both certificates of insurance and endorsements, including additional insured endorsements, affecting all of the coverages required by this Agreement. The certificates and endorsements are to be signed by a person authorized by that insurer to bind coverage on its behalf. All proof of insurance is to be received and approved by the City before work commences. City reserves the right to require Contractor’s insurers to provide complete, certified copies of all required insurance policies at any time. Additional insured endorsements are not required for Errors and Omissions and Workers’ Compensation policies.

Verification of Insurance coverage may be provided by: (1) an approved General and/or Auto Liability Endorsement Form for the City of Palm Springs or (2) an acceptable Certificate of Liability Insurance Coverage with an approved Additional Insured Endorsement with the following endorsements stated on the certificate:

A. "The City of Palm Springs, its officials, employees, and agents are named as an additional insured…” ("as respects City of Palm Springs Contract No.___" or "for any and all work performed with the City" may be included in this statement).

B. "This insurance is primary and non -contributory over any insurance or self - insurance the City may have..." ("as respects City of Palm Springs Contract No.___ " or "for any and all work performed with the City" may be included in this statement).

C. "Should any of the above described policies be canceled before the expiration date thereof, the issuing company will mail 30 days written notice to the Certificate Holder named. " Language such as, “endeavor to” mail and "but failure to mail such notice shall impose no obligation or liability of any kind upon the company, its agents or representative" is not acceptable and must be crossed out.

D. Both the Workers’ Compensation and Employers' Liability policies shall contain the insurer's waiver of subrogation in favor of City, its elected officials, officers, employees, agents, and volunteers.

In addition to the endorsements listed above, the City of Palm Springs shall be named the certificate holder on the policies. All certificates of insurance and endorsements are to be received and approved by the City before work commences. All certificat es of insurance must be authorized by a person with authority to bind coverage, whether that is the authorized agent/broker or insurance underwriter. Failure to obtain the required documents prior to the commencement of work shall not waive the Contractor’s obligation to provide them.

55575.18100\42906602.1

BB&K (2024)

ATTACHMENT “D”

EXECUTIVE ORDER N-6-22 CERTIFICATION

Executive Order N -6-22 issued by Governor Gavin Newsom on March 4, 2022, directs all agencies and departments that are subject to the Governor’s authority to (a) terminate any contracts with any individuals or entities that are determined to be a target of economic sanctions against Russia and Russian entities and individuals; and (b) refrain from entering into any new contracts with such individuals or entities while the aforementioned sanctions are in effect.

Executive Order N-6-22 also requires that any contractor that: (1) currently has a contract with the City of Palm Springs funded through grant funds provided by the State of California; and/or (2) submits a bid or proposal or otherwise proposes to or enter into or renew a contract with the City of Palm Springs with State of California grant funds, certify that the person is not the target of any economic sanctions against Russia and Russian entities and individuals.

The contractor hereby certifies, SUBJECT TO PENALTY FOR PERJURY, that a) the contractor is not a target of any economic sanctions against Russian and Russian entities and individuals as discussed in Executive Order N -6-22 and b) the person signing below is duly authorized to legally bind the Contractor. This certification is made under the laws of the State of California.

Signature:

Printed Name:

Title:

Firm Name:

Date:

Palm Springs City CouncilMay 12, 2026

Palm Springs City Council
May 12, 2026