Yuba City City Council
July 2, 2024

6.7 Tyler Training Plan ................................................................................................................ 33

6.7.1 Scheduling and Attendance ......................................................................................... 34

6.7.2 Responsibilities ............................................................................................................ 34

6.7.3 Train the Trainer versus Tyler Led End User Training .................................................. 34

6.7.4 Training Documents ..................................................................................................... 35

6.8 Solution Validation ............................................................................................................... 37 Section 7 Ongoing Maintenance and Support ................................................................................. 39

7.1 Help Desk ............................................................................................................................. 39

7.1.1 Focused by Application ................................................................................................ 40

7.1.2 Incident Tracking .......................................................................................................... 41

7.1.3 Software Updates & Maintenance ............................................................................... 42

7.2 System Monitoring ............................................................................................................... 42

7.3 Post-Implementation Evaluation Report (PIER) ................................................................... 43

7.4 Application Upgrades ........................................................................................................... 43

7.5 Change Management ........................................................................................................... 45

7.6 User Group/Conferences ..................................................................................................... 46

7.6.1 Local User Groups ........................................................................................................ 46

7.6.2 Annual User Conference .............................................................................................. 46 Section 8 Pricing ............................................................................................................................... 47

8.1 Appendix B ........................................................................................................................... 47

8.2 Tyler Investment Summary .................................................................................................. 48 Section 9 Software Licensing and Maintenance Agreements ......................................................... 49

9.1 Sample Contract ................................................................................................................... 49

City of Yuba City Executive Summary
ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 1
Section 1 Executive Summary
Section 1 - Executive Summary
This section of the proposal should provide a brief and concise synopsis of Proposer’s proposal and a description of the Proposer’s credentials to deliver the services sought under the RFP. This is to include identification of Proposer solution and identification of use of any third-party applications and/or subcontractors, and the scope of work to be performed by each subcontractor.

The Executive Summary should not exceed three (3) pages.

Public sector organizations around the nation are facing some of most difficult challenges in the financial and human resources management arenas today. Managers seldom find they’re burdened with a shortage of data. Rather, the difficulty is assimilating, compiling, and analyzing this wealth of information to make informed, timely business decisions on a day-to-day basis. With Tyler’s Enterprise Resource Planning (ERP) solution, the City of Yuba City will be able to take the first step in implementing an off-the-shelf, scalable solution that can be tailored to fit your specific needs and requirements. Tyler is uniquely positioned to offer the city our industry-leading fully integrated Enterprise ERP solutions to meet the entire scope of the requirements requested.

Why Partner with Tyler?
Tyler has been providing software to municipalities in California and throughout the Country for more than 35 years. What’s more, our software solutions have undergone numerous revisions over this time—yet as a Tyler client you will never have to pay for an upgrade and will be provided with a continuous improvement initiative that includes training and consulting to ensure you get the most from your investment. This is what Tyler calls our Evergreen and EverGuide™ Philosophies. This approach, combined with our public sector focus, proven history of success, easy-to-use feature-rich software, and role-tailored security, ensures the City of Yuba City will enjoy the best return on investment available.

Tyler Technologies is the leading provider of integrated software systems and information technology services for the Public Sector. Tyler’s ERP solution is currently being used in over 2,000 Public Sector entities across the US and is our flagship offering for Municipal Governments. We have been very busy growing our client base over the last several decades, especially in the State of California. Below are just a few of the partners we have in the State; Tyler’s Enterprise ERP is now installed in over One Hundred Seventy (170) sites across the State.

Tyler’s proven success in local government, our understanding of your needs and requirements, and our ability to deliver industry-leading software and services in a timely manner and within budget, distinguishes Tyler’s ERP and related productivity solutions as a clear choice for the City of Yuba City. We believe that our comprehensive Tyler ERP suite, designed to fully integrate and provide seamless functionality, is the best option to meet the City’s goals today and well into the future. 9 A fully integrated ERP solution, so your users can consolidate budget, procurement, payroll, human resources, and general ledger/financial information, and decrease information silos, duplicate data entry and disparate systems. Tyler’s ERP’s integrated modules seamlessly share information in real time, allowing users to transition from one area to another and follow the trail of transactions throughout the system.

City of Yuba City Executive Summary
ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 2
9 Easy and user-friendly access to information through the Tyler Hub Dashboard provides users of all levels, from data entry clerks to your high-level decision makers, with direct access to pertinent, up-to-date information relevant to each user’s position in the organization. Dashboards are user configurable, and templates are available centrally to facilitate deployment and maintenance. 9 Built-in, configurable electronic workflow that will allow the City to design electronic approval routing through the system, linking back to electronic documentation stored in Content Manager, the fully integrated Content Management solution built-in to the Tyler ERP solution. 9 Accessibility and transparency, providing intuitive, easy-to-use tools to a user base that consistently demands better control over their information. With productivity tools such asEnterprise Analytics and Reporting with Executive Insights, your users can complete tasks and access decision-supporting information any time, and from anywhere—and your citizens have immediate access to the financial and personal data you need them to see. From accessible HTML5 and responsive design technology, to convenient Web access and dynamic mobile applications, Tyler ERP enables staff, citizens, and stakeholders to interact with the city in an easier and more productive manner than ever before.
9 Reporting solutions that range from hundreds of pre-designed reports—many with a variety of reporting options designed for quick and easy standard data review—to data analysis, each is tailored to different aspects and levels of your ERP users. Tyler ERP reporting options also provide programming features so you can extend and customize your reporting functionality. Utilizing Microsoft® SQL Server® Reporting Services
(SSRS), it’s now possible for your system or report administrator to design interactive, tabular, graphical, ad hoc, and free-form reports from a variety of data sources. Designed for use with Microsoft SQL Server, the City of Yuba City can create these custom reports using powerful wizards and built-in features and functionality. When you add charts, drill downs, parameters, and hyperlinks your reports are immediately transformed into interactive documents or Web content. To top it all off, analysis tools such as field highlighting, running totals, and sorting let you examine trends, expose relationships, and zero in on key performance metrics.
9 A rich internal, as well as third-party, integration/interface solution—because Tyler is committed to providing our clients with the most comprehensive, versatile, and easy-to-use solutions possible. As part of this commitment, Tyler’s ERP solution includes numerous integration points. This means your staff benefits from the use of standardized, time-tested integration points that are readily available and already used by thousands of Tyler ERP clients. Tyler has heavily embraced web services as the future of application architecture and integration with other applications using industry standards. Tyler ERP includes a robust and growing library of APIs and can leverage them for real time integration with third party systems interfaces.

Your Investment
Investment in the growth of software companies is paramount to success—for both the company and the clients it serves. Tyler recognizes this and embraces an integral philosophy that promotes sound Research and Development that includes client-centric usability; prudent, leading-edge technology; sound business practices; and a focus on the unique requirements and needs of our clients in the public sector. And Tyler understands that public sector offices advance and acquire technology in different ways and at different rates. With more than 40,000 clients, Tyler has worked with agencies in all phases of automation, from paper-based manual processes to advanced digital analytics and paperless efficiencies.

And while the Tyler ERP functionality is key to your overall solution, Tyler understands that it takes much more than software to achieve a successful implementation. With this in mind, we have proposed a project strategy that is founded on several key principles.

City of Yuba City Executive Summary
ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 3
Implementation Methodology
Tyler’s Implementation Methodology is based on our 30+ years of continuous adjustments based on feedback and lessons learned from thousands of public sector clients just like the City of Yuba City to improve the process and develop tools and technologies to make implementation more intuitive and effective. The Tyler ERP software modules and services proposed are based on our thorough review of the RFP, and interpretations of the City’s vision and expectations for a partnership with a new ERP provider.

California Qualifications
Tyler also has a long history of working with California clients. In fact, the Tyler ERP is currently used by more than one-hundred seventy (170) California organizations already. And as part of that ongoing commitment, you’ll enjoy dedicated California Tyler ERP User Group, a State Reporting department dedicated to California, and regional and local implementation and support resources—ensuring the City of Yuba City receives the support and attention needed for a successful, perpetual partnership.

In Summary
As your primary vendor for the City’s ERP solution, Tyler is pleased to offer the City of Yuba City, the Tyler ERP software and services solution which brings to the city the following:
x An industry-leading local government-specific solution with a proven track record in software design, implementation, and support
x A strong focus on bringing repeatable success to local government entities like the City of Yuba City x A highly functional software solution designed to meet the unique requirements and challenges of our clients across the U.S.
x An Evergreen and everGuide practice that keeps our clients successful with ongoing and perpetual upgrades, training, guidance, and user group participation.

We are confident a partnership between the City of Yuba City and Tyler Technologies will provide the city with the most fiscally prudent and functionally effective software solution available—with the products, tools, services, and partnership you need to keep the city on track, on budget, and on point. The City of Laguna Beach’s partnership with Tyler will enable you to chart the path of robust, efficient, easy-to-use technology benefitting all City stakeholders now, and for decades to come.

City of Scottsdale Company Background
ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 4
Section 2 Company Background
Section 2 – Company Background
This section of the proposal should identify the following:

2.1 – A brief description of the Proposer’s background.

Tyler Technologies is the largest and most established provider of integrated software and technology services focused on the public sector. Tyler's end-to-end solutions empower local, state, and federal government entities to operate more efficiently and connect more transparently with their constituents and with each other. By connecting data and processes across disparate systems, Tyler's solutions are transforming how clients gain actionable insights that solve problems in their communities. Tyler has more than 37,000 successful installations across more than 12,000 sites, with clients in all 50 states, Canada, the Caribbean, Australia, and other international locations.

2.1 Our Products
With decades of exclusive public sector experience, Tyler is the market leader providing integrated software and services. Subject matter experts and in-depth products result in a sustainable client partnership that delivers the industry’s most comprehensive solution. We provide the industry’s broadest line of software products and offer clients a single source for all their information technology needs in several major areas:

Property & Recording, ERP, Civic Services, Health & Human Services, Courts & Justice, Public Safety, Data & Insights, and Schools.

We are known for long-standing client relationships, functional and feature-rich products, and the latest technology. In addition to software products, Tyler provides related professional services including installation, data conversion, consulting, training, customization, support, disaster recovery, and application and data hosting.

2.2 About Tyler Technologies
x Empowering government and schools to create safer, smarter and more vibrant communities x Solutions include: Property & Recording, Civic Services, Courts & Justice, Data & Insights, ERP, Health & Human Services, Public Safety, and Schools
x Headquartered in Plano, Texas, with 68 office locations across the U.S., Manila, and Canada x Tyler was incorporated in Delaware in November 1989
x Tyler is a publicly traded corporation on the NYSE (TYL) x Founded in 1966
x Exclusively focused on local government since 1997
x More than 37,000 successful installations across 12,000 sites, with clients in all 50 states, Canada, the Caribbean, Australia and other international locations
x Client retention rate of 98%
x 6,600+ employees
x Annual revenues of $1.85 billion (2022)
x Reinvestment of $123M into Research & Development
x Scalable products with the smallest jurisdiction (Loving County, Texas, with a population of 82) to the largest (Los Angeles County, California, with a population of 10.1M)

City of Scottsdale Company Background
ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 5

2.3 Industry Leadership
Tyler strives to provide the best client services in the industry. Our products undergo testing by trained quality assurance and certified usability analysts, therefore our clients benefit from products that work logically based upon user experience and input. We also focus our implementation and support professionals on specific groups of applications so they can offer more specialized services.

Our commitment at Tyler is to ensure the highest level of client satisfaction through the efforts of Tyler’s most valued resource: its people. We challenge our employees to pursue new initiatives aggressively and become industry leaders in their respective fields. Tyler employs 6,600+ individuals, many of whom are seasoned professionals with unique and proprietary skills and years of industry experience. In fact, our employee turnover rate is very low – in recent years, about half of the industry average.

2.4 Our Experience
Tyler Technologies’ solutions offer the widest breadth of products in the industry, the latest technology available, and an integrated system that can operate in diverse offices throughout a jurisdiction. More importantly, Tyler’s vision and skill in executing that vision is what ultimately leads to a successful implementation and long-term solution for our clients. Our experienced team consists of industry leaders that keep our team moving and making sure we can give you the tools to succeed.

2.2 – Identify the location of headquarters, technical support, and field offices and the location of the office that would service the City.

Tyler is headquartered in Plano, TX. Technical support for EERP is located Maine. For a complete listing of Tyler office locations, please visit About Us: Tyler Technologies' Office Locations

2.3 – Identify Proposer’s annual company revenues and profit for the last three fiscal years.

The Background section should not exceed two (2) pages.

Tyler consistently maintains a solid balance sheet and strong cash flow and low debt, experiencing consistent revenue growth with 41 consecutive quarters of profitability, and a total revenue for 2022 of $1.85 billion. While experiencing significant growth opportunities from an increase in staff and expanding territories, we anticipate additional product offerings and new technology will accelerate this growth substantially in the future. We believe a low-debt balance sheet, substantial cash reserves, and a committed customer base put Tyler in a great position in our industry to weather any unexpected turbulence in the economy.

For additional revenue information please visit www.tylertech.com eriencing
ue for 2022 of
f and

City of Scottsdale Company Qualifications
ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 6
Section 3 Company Qualifications
Section 3 – Company Qualifications
In this section, Proposers should identify company qualifications and experience in implementing solutions similar to what the City is seeking:

3.1 – Describe the Proposer’s familiarity with public sector ERP systems and associated business processes, and experience with the requirements of municipalities.

3.1 Public Sector Focus
Tyler’s business units have provided software and services to clients for more than 50 years and have longstanding reputations in the local government market for quality products and customer service. Tyler is the largest company in the United States focused solely on providing software solutions to the public sector.

While many of our competitors compete in multiple vertical markets, Tyler is singularly focused on the public sector. It is 100 percent of our business.

Tyler recognizes that the public sector is generally stable and risk-averse, and craves community accessibility, security and transparency. That is why local government and school entities seek reliable and efficient software and services from Tyler – a vendor who is professional, reputable and dedicated and achieves results. Tyler has the experience to understand the unique requirements of the public sector, the necessary resources to invest in its products and the ability to deliver quality services.

Tyler’s expansive offering of professional services is designed to complement its software offerings and produce the optimum working environment for local government customers. x Consulting
x Conversion
x Customization
x Training
x Live ongoing support
x Network management

3.2 – Identify the Proposer’s client base including the number of existing clients using the version/release of the software being proposed. Specifically identify experience with similar sized California municipalities.

The Company Qualifications section should not exceed two (2) pages.

With more than 2,000 Munis clients nationally, Tyler Technologies continues to help public-sector agencies by providing solutions and services that streamline business processes, increase efficiency, and minimize the risks that are inherent in complex Implementations of new business services solutions. We’ve experienced some great success with implementations in Arizona with our total client installations in the state at just shy of 30 sites. In Arizona specifically there is 1 other site similar size and scope to that of the City of Scottsdale.

However, nationally, there are roughly 25 sites similar size and scope to the City of Scottsdale that we have implemented.

City of Yuba City References
ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 7
Section 4 References
Section 4 - References
Proposers must provide at least five (5) references with at least three (3) of the references for systems that have been implemented in the last five years. The City prefers references from California municipalities of similar size and complexity to the City. For each reference, Proposer must provide the following information:

4.1 - Name and contact information (i.e. name, title, address, direct phone, and email)

4.2 - Brief project description, including identifying the software version, modules, and interfaces implemented

4.3 - Implementation timeline, Go Live date, and budgetary cost vs. actual cost The References section should not exceed five (5) pages.

Tyler Technologies continues to help public sector/ local government agencies by providing solutions and services that can streamline business processes, increase efficiency, and minimize the risks that are inherent in complex Implementations of new business Enterprise Resource Planning (ERP) solutions. We have been very busy in the State of California over the past several years. We now have over 170 Munis clients in the State.

Tyler’s Munis Enterprise Resource Planning (ERP) solutions have been selected by several of your peers and all of these sites are in some phase of the implementation process now:

Here is a list of some of the latest CA clients from 2021, 2022 and 2023:
x City of Laguna Beach, CA
x City of La Habra, CA
x City of Los Altos, CA
x City of Glendora, CA
x City of Livermore, CA
x City of Port Hueneme,
x City of Fresno, CA
x City of Vernon, CA
x City of San Juan Capistrano, CA
x City of Fullerton, CA
x City of Lemoore, CA
x City of Temecula, CA
x Yuba County, CA
x City of Oroville, CA
x City of Woodland, CA
x City of Morgan Hill, CA
x City of Lancaster, CA
x City of Lincoln, CA
x San Diego Association of Governments, CA
x Town of Los Gatos, CA
x City of Huntington Park, CA

City of Yuba City References
ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 8
Meaning…
You’re Not Alone
Tyler Technologies hosted over 75 remote local Munis User Groups across the Country in 2022 and the two California groups were the most widely attended across the Nation. In California, we offer two local user group meetings every year: one for our northern clients and one for our clients in Southern California. These groups are a great way for Tyler clients to interact with peers, ask questions, find out what’s new within Tyler, earn CPA credits for attending and for new clients, this is a great way to understand other sites “lessons learned” who have gone through the Tyler implementation process…You’re not on an island with Tyler Technologies - you’re not alone.

Because of Tyler’s success, not only in California, but across the County, and because 100% of our company’s efforts are focused on the Public-Sector, we have the ability and the resources to be more client focused.

Over the several decades, these types of user groups have been instrumental in being one of the main conduits to our development group. We have taken on development projects such as adding additional Excel cubes for end-user reporting, adding additional API’s, revamped the Enterprise ERP/Munis accounts receivables/ general billing suites, and we added budget-based water rates specifically for California Municipalities within our Tyler ERP utility billing suite – Also, based on specific conversations during this past year’s CA user group meeting, we have enhanced the FLSA and retro-pay capabilities with our ERP to make these processes more user friendly while at the same time adhering to the rules and regulations outlined by the State of California…With our Evergreen Development approach, all these enhancements, all these new features, new functionalities, are all available to the entire Tyler/ Munis client base.

Customer name: City of Fresno, CA
Customer contact: Dennis Jones, Systems & Applications Manger Customer phone number: 559-621-7117
Customer E-mail address [email protected]
The City of Fresno purchased Tyler’s Munis/Enterprise ERP solution in 2021. The city is implementing with a phased approach, Financials first and then Payroll/HCM. The City of Fresno went live on Financials July of 2022. They will be going live on HCM early 2024.

Customer name: City of Pleasanton, CA
Customer contact: Rebecca Peixoto-Perry, ERP Project Manager Customer phone number: 925-931-5413
Customer E-mail address [email protected]
The City of Pleasanton purchased Tyler’s Munis/Enterprise ERP solution in 2015. They implemented in 3 phases with Financials first and then Payroll/Human Capital Management and Utility Billing/Tyler Cashiering in the last phase.

City of Yuba City References
ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 9
Customer name: City of Tracy, CA
Customer contact: Robert Harmon, Finance & Budget Director Customer phone number: 209-831-6828
Customer E-mail address [email protected]
System which Solution Replaced Harris/Cayenta
Describe Nature of Project and Services Provided to This Client:

The City of Tracy purchased Tyler’s Munis/Enterprise ERP solution in 2014. They implemented in 3 phases with Financials first and then Payroll/Human Capital Management and Utility Billing/Tyler Cashiering in the last phase. Since their initial purchase, the city has added many modules including ExecuTime and Socrata Data/Insight.

Customer name: City of Simi Valley, CA
Customer contact: Donna Price, Enterprise Systems Analyst Customer phone number: 805-583-6327
Customer E-mail address [email protected]
The City of Simi Valley purchased Tyler’s Munis/Enterprise ERP solution in 2015. They implemented in a phased approach with Financials first and then Payroll/Human Capital Management. The City’s project with both phases lasted approximately 24 months. A few years after the City’s initial investment with Tyler they extended our partnership and purchased Tyler’s EnerGov solution.

Customer name: City of El Cajon, CA
Customer contact: Sara Diaz, Director of IT
Customer phone number: 619-820-8345
Customer E-mail address [email protected]
System which Solution Replaced Central Square
Describe Nature of Project and Services Provided to This Client:

The City of El Cajon purchased Tyler’s Munis/Enterprise ERP solution in 2020. They implemented in a phased approach with Financials first and then Payroll/Human Capital Management. The City’s project with both phases lasted approximately 24 months. Prior to implementing Munis, the City was already a Tyler customer with our EnerGov product which they purchased in 2018.

Customer name: Napa County

City of Yuba City References
ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 10
Customer contact: Tracy Schulze, County Auditor
Customer phone number: 707-299-1733
Customer E-mail address [email protected]
Napa County replaced Oracle in 2020 with Enterprise ERP (powered by Munis). The County implemented in a phased approach with Financials in phase 1, going live late 2021, and Payroll/Human Capital Management, Time Entry in phase 2.

Customer name: Yuba County
Customer contact: Richard Eberle, County Auditor
Customer phone number: 503-749-7810
Customer E-mail address [email protected]
Yuba County started with Tyler’s EnerGov land mgmt. solutions and added Enterprise ERP in early 2021. The County purchased Tyler’s Enterprise ERP Financials solution.

City of Yuba City Proposed Solution
ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 11
Section 5 Proposed Solution
Section 5 - Proposed Solution
In this section, Proposers should describe their solution by providing the following:

5.1 Solution Details

5.1 – Solution Details
Name and origin of solution
Tyler’s EERP software solution is developed by Tyler Technologies.

Release history and current release being proposed
Tyler application upgrades are released quarterly. Software corrections, known as cumulative updates, are made available for download between quarterly releases. All releases are cumulative allowing clients to upgrade to the latest application version directly. EERP release 2023.x is being proposed.

Proposed modules with detailed information regarding their functionality Please see Tyler’s Investment Summary for proposed modules.

Mobile capabilities of the proposed modules
Tyler provides applications across multiple platforms, including mobile and touch screen tablets, offering endusers with on-the-go access from virtually anywhere. Responsive web applications automatically orient screen layout for optimal user experience, whether accessed from a desktop monitor or smartphone. Native mobile apps leverage device resources such as GPS or camera; and integrated store-and-forward functionality allow the use of apps without a data connection, and automatically syncs when back online. Many of the backoffice browser applications are also accessible from mobile devices, and some are even optimized for touch providing near identical functionality regardless of the platform or device used.

Enterprise ERP
Enterprise ERP Application Suite
All Enterprise ERP applications are HTML5 web-based solutions, providing end user access from any modern device.

Requirements
Software: Enterprise ERP version 2018.1+
Supported Platforms: All major platforms with HTML5 browser support1 2 Community Access
Tyler’s Community Access programs offer a direct interface to ERP data specific for Employees (maintain benefits, time off, expense reports, etc.), Citizens (pay utility, personal property tax, real estate tax, and motor vehicle bills, apply for permits and inspections, submit non-emergency requests, etc.), and Vendors (access 1099s, W-2s, AP checks, invoices, purchase orders, bids, etc.). All Community access programs are supported from nearly every web browser including those found on iPad and Windows tablets.

Requirements

City of Yuba City Proposed Solution
ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 12
Software: Employee
Supported Platforms: All major platforms1
Employee Self Service
Employee Self Service provides a portal for employees that can be accessed from anywhere, anytime.

Employees can easily monitor and maintain personal and employment information including paid time-off accruals and requests, pay history, W2 information, and more. Managers can view their employee requests and approve them easily within the app. Human resource representatives are also freed to spend more time acting in a consultant role, rather than administrative, while employees have instant access to the answers they need.

Requirements
Software: Enterprise ERP version 11.1+ with Employee Self Service Supported Platforms: Android, iPhone
Workflow Actions via Email
Need to approve an emergency requisition while you are out of the office? Now you can act on any workflow item directly from your email on your mobile device.

Requirements
Software: Enterprise ERP version 9.0+
Supported Platforms: All major platforms1
My Work Mobile
My Work Mobile provides staff real-time access to workflow actions and allows users to complete workflow tasks right from their mobile devices. With alerts, notifications, and workflow review on your phone or tablet, My Work gives the manager on the go the ability to review, approve, reject, or forward work to another employee. Keep the office work flowing from wherever you are.

Requirements
Software: Enterprise ERP version 10.3+
Supported Platforms: Android smartphone, iPhone, Windows 10 tablet Identification of use of subcontractors and/or third-party application providers including:
o Company background
o Scope of work to be performed
o Experience and references specific to scope of work to be performed o Identification of where Proposer and subcontractor and/or third-party application provider has successfully worked together in the past
o Description of how Proposer will manage any subcontractor and/or third-party application provider to ensure successful delivery of subcontractor and/or thirdparty application provider scope of work Not Applicable

City of Yuba City Proposed Solution
ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 13

5.2 Application Integration/Interface

5.2 – Application Integration/Interface
Required integration/interfaces are identified in Appendix A - Technical. Please describe the following for each integration/interface:
o Proposer’s integration/interface solution [web services, Application Programming Interfaces (APIs), etc.] Tyler solutions offer a variety of methods of interfacing with external third-party systems, including file-based import and exports and real-time web service integration through plug-and-play App Connectors, and API Toolkits and Connectors.

Tyler Integrated Solutions
Tyler’s family of ERP and Civic solutions provide robust, native integration, eliminating the need to manage third-party interfaces and integrations entirely. This includes Enterprise Permitting & Licensing, Enterprise ERP,Enterprise Asset Management, Cashiering and Payments for point-of-sale and online payment processing, Content Manager’s streamlined access to records and documents, and Enterprise Service Request Access to manage non-emergency inquiries, incident reporting, complaints, and service requests.

File-based integration
Multiple file-based interfaces are included, and all are integrated as part of the application, designed for end users. Unlike systems that require a database administrator to import or export data with their system, users can easily import or export data through point-and-click user interface. User-defined templates specify the data layout for a specific system, so users can quickly choose the appropriate template at the time of import/export. Templates for commonly used third-party systems are also included out of the box. File-based interfaces can be scheduled for one-time or recurring, automated processing.

Imports can be configured with Workflow to send automated notifications or approval requests before the data updates a record. Workflow business rules can be set on a variety of data conditions specific to the imported data. This includes if data causes an account to go over budget, is over a certain dollar amount, or is related to a specific segment of your general ledger. Only after all workflow rules have been approved does the import update production data. Depending on the process, imports can also be rejected at the item or file level; rejected imports can be resubmitted at any time.

Productivity Software Support
Application data can be downloaded to a variety of formats including PDF, XLS, DOC, XML, and CSV. Any productivity suite capable of opening these file types can be used, such as Microsoft Office and Google Workspace. Data can also be uploaded to the system in these formats through the integrated import applications.

Most output include hyperlinks to the corresponding application record for easy access. Most output can also be automatically archived to Content Manager for quick retrieval at any time. Some applications also include mail merge support, allowing users to easily create and maintain form templates for completely customized presentation of application data. Any SMTP/IMAP server can be used to send email notifications, such as Microsoft Exchange and Gmail.

City of Yuba City Proposed Solution
ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 14
‘Plug-and-Play’ Application Support
Plug-and-play application support provides out-of-the-box integrations for a variety of third-party applications through pre-packaged web services. Tyler develops and maintains these integrations, requiring no development expertise from the client to configure.

API Catalog
API (Application Programming Interface) Toolkits and API Connectors add value to your organization by enabling you to create your own integrations to share data between Tyler and non-Tyler applications.

API Toolkits contain all exposed resources (or endpoints) available in a specific Tyler application module such as Enterprise ERP General Ledger, Accounts Receivable, or Enterprise Asset Management. API Connectors contain a subset or cross-section of API Toolkit resources with the purpose of facilitating a specific type of integration such as third-party cashiering, IVR, or applicant tracking systems.

The API Developer Portal is a powerful RESTful API gateway that makes accessing Tyler application data and processes through Toolkits and Connectors easy and intuitive. The Portal conforms to OpenAPI 3.0 and is secured with OAuth 2.0 through Tyler Identity. API resources include example calls and produce properly formatted commands, allowing you to easily exercise them against your data.

The API Developer Portal features include:
x Simplified, structured API documentation
x Industry standard OpenAPI 3.0 interface
x Authentication using OAuth 2.0 standard, offering multiple login flows to suit different app implementation scenarios.
x Data models and examples for each resource
x Produces HTTP URI and CURL commands to exercise resources from within the documentation and return data
x Real-time validation
x Standard HTTP status codes
x Documentation to aid in identifying and understanding normal resources used to complete a given integration.
o Data availability/transfer (real-time, nightly, etc.) Data is accessible through browser-based Tyler applications, many of which include the ability to export data to a variety of formats including Excel, Word, PDF, XML, and CSV. Data is also accessible from most applications through a hosted ad-hoc reporting environment, RESTful APIs, integrated bulk export applications, and read-only database access.

All key transactions are performed in real-time unless otherwise noted. The only batch processing that takes place are for reports or select process that are proactively scheduled. o How Proposer will ensure data security
Information Security is important to Tyler Technologies and to every agency and jurisdiction we serve. We encourage agencies considering a cloud solution to evaluate their providers and the security measures they have in place. Important considerations include compliance standards, layers of network security, adherence to best practices and qualified staff.

Tyler Technologies, Inc. maintains a comprehensive, written information security program that contains administrative, technical, and physical safeguards that are appropriate to:

City of Yuba City Proposed Solution
ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 15
x The size, scope, and type of Tyler’s business.
x The type of information that Tyler will store.
x The need for security and confidentiality of such information.

Administrative Controls
Organizational Security Controls
Internal Organizational Structure
Tyler Technologies has an organizational structure that establishes delegation of authority. Jobs have been defined within the organizational structure, which provides for segregation of duties.

IT Department Oversight
The IT department has a management structure that provides for oversight and monitoring of activities. The director of IT Infrastructure is responsible for oversight of the corporate network and reports to the chief information officer (CIO). An information security plan (ISP) has been established to help govern the protection of client information and is available to all Tyler employees. Execution of the ISP is overseen by a fulltime security staff who monitors execution of security controls, conducts risk assessments, and stays apprised of evolving threats.

Hiring and Orientation Practices
Tyler follows a standard recruiting process when hiring new employees. Job opportunities are communicated internally through email, as well as externally through third-party job search sites. Prior to hire, criminal, and motor vehicle background checks as well as FBI fingerprint checks, as applicable, are performed. A new-hire checklist is used during the on-boarding process to help ensure required tasks are performed.

Orientation is conducted for new employees in person or via the phone. Additionally, new employees are invited to attend Tyler Days, a more in-depth orientation focusing on the company and the specific departments in that division.

A member of the HR department notifies the IT department when a new employee is hired to provision the user's corporate network access. A username and password are required to access the corporate network.

Employee access to the corporate network resources and confidential information on the network is limited to active employees based on their job functions. Access is removed upon notification of termination from the HR department.

Corporate network administrative-level access is limited to employees that require access to perform their job functions. Corporate network user access reviews are performed monthly.

Identity and Access Management
Tyler implements a role-based access control methodology to ensure only authorized people with a need for access are given it. To the extent Tyler users have access, Tyler employs a least privileged access strategy, meaning that individuals are given and use only the least administrative rights possible to do the task at hand. Tyler compliments these strategies with controls and monitoring to ensure only those authorized users can access the systems allowed.

Employee Handbook
An employee handbook documents company policies. The employee handbook is reviewed by the Human Resources (HR) department and updated at regular intervals. Employees are required to sign an employee handbook acknowledgement, which includes security policies, upon hire. Employees are required to sign a confidentiality/non-disclosure agreement upon hire.

City of Yuba City Proposed Solution
ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 16
Termination Practices
Employee termination procedures exist to help ensure required tasks are performed. Managers are responsible for contacting the HR department to inform them of an employee termination. Upon notification, the HR department will create an information technology (IT) ticket to inform the responsible parties to disable the employee's access, and a termination notice email is sent to a distribution group. When appropriate, the HR department conducts an exit interview with the terminated employee.

Employee Training and Meetings
Tyler provides management with ongoing training. Division-wide meetings are held regularly for each division of Tyler to communicate company-wide policies and updates as well as division specific content.

Cloud Solutions Operations department meetings are held on a quarterly basis to discuss changes, updates on status of projects, and relevant topics that may have an impact on Cloud Solutions clients. Additionally, team meetings are held weekly for the management team within the Cloud Solutions Operations department to discuss ongoing issues and events.

Employees are required to complete security awareness training on a regular basis. This training highlights Tyler’s security policies. It also covers recommended security best practices regarding topics such as phishing, social engineering, malware, and confidential data handling.

Regulatory Compliance & Certifications
Tyler Cloud Operations employ best practice security controls and are subject to annual assurance audits.

Audits include SOC 1 Type 2 and SOC 2 Type 2 conducted by an independent AICPA firm, and PCI Security Council PA-DSS and PCI-DSS validation for Tyler’s payment and payment gateway applications.

More information on Tyler Industry & Regulatory Compliance, including how to obtain a copy of Tyler’s SOC Report can be found at: https://www.tylertech.com/about-us/compliance Incident Response
To effectively protect Tyler’s business and the client data in our care, a Security Incident Response Procedure is in place, defines employee responsibilities, and is available to all employees. Tyler’s incident response plan, based on the NIST 800-53 Framework, defines a measured, repeatable process for determining, handling, and recording when an incident occurs. Tyler Technologies’ handling of incidents, including notification to customers, conforms to applicable state and federal law.

Design, implementation, and maintenance of the IRP are the responsibility of Tyler’s Information Security Office. The IRP establishes procedures for responding to and reporting of security incidents. A Post Incident Review is conducted once a threat has been successfully eliminated. The Incident Response Plan is tested no less than annually.

Tyler regularly monitors the networks, systems, environments, and applications within its control. As part of that monitoring, if Tyler identifies a potential security incident, Tyler follows established policies and procedures to contain, respond to and mitigate such incidents. Tyler’s standard practice is to treat the details of any such incident as confidential, given that releasing those details to the public itself creates a security risk, and/or because those details may include a client’s confidential information.

Further information regarding Tyler’s incident response plan can be found in our most recent Type 2 Service Organization Controls No. 2 (SOC 2) report.

City of Yuba City Proposed Solution
ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 17
Secure Software Development Life Cycle
Tyler employs an enterprise Secure Software Development Life Cycle (SDLC) dedicated to continuously reviewing and enhancing the security posture of Tyler’s products. Tyler uses enterprise-level dynamic and static security scanning tools as part of our software development lifecycle. In addition to scanning tools, Tyler’s application security team executes manual assessments on Tyler products using a testing methodology based upon the OWASP Testing Framework.

Vulnerability Disclosure Program
Tyler has an enterprise-wide vulnerability disclosure program which includes Tyler products in its scope. Tyler makes available a communication channel for clients, partners, and the security community to report vulnerabilities in our products.

Tyler’s Enterprise Application Security Team is responsible for triaging and managing product related vulnerability reports. This process involves confirming the vulnerability exists, assigning risk and impact, working with development on a fix, testing the fix, releasing the fix, and communicating the fix to clients.

Technical Controls
Dedicated Datasets
Tyler’s cloud infrastructure, platforms, and resources are multi-tenant, shared by multiple clients, however each client is provided with their own dedicated datasets. This complete data segregation adds an additional layer of security between environments.

Data Encryption
Transport Layer Security (TLS) encryption protects communication with Tyler applications, including end-user access through TLS-protected HTTPS. This widely adopted protocol secures sensitive data by preventing reading or modifying information transferred.

Tyler solutions run on AWS storage services, including Elastic Block Store (EBS) and Amazon Simple Storage Service (S3). The use of server-side encryption with AWS Key Management Service (AWS KMS) keys is used to encrypt at-rest data. This encryption is known as SSE-KMS. SSE-KMS uses one of the strongest block ciphers available to encrypt your data, 256-bit Advanced Encryption Standard (AES-256).

Tyler employs a FIPS-compliant enterprise backup solution certified for CJIS and GovCloud use. Data transfer and storage is encrypted as defined in FIPS140-2 and FIPS140-3 standards over private connections within the AWS network.

Network Security
Tyler’s dedicated Network Operations Center (NOC) provides 24x7 utilization and network activity monitoring of all cloud solutions. Tyler employs a variety of industry-standard solutions for monitoring and intrusion detection and prevention. Safeguards include Amazon Inspector automated vulnerability management, Amazon GuardDuty continuous threat detection, and AWS Shield distributed denial of service (DDoS) protection.

Application Authentication
Identity Workforce is a zero-trust, cloud Identity-as-a-Service (IDaaS) solution for Tyler’s back-office applications. Built on Okta, the industry leader in identity management, Identity Workforce enables secure, cloud-based authentication for all users, regardless of location, device, or network.

City of Yuba City Proposed Solution
ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 18
Identity Workforce supports federation with industry standard identity providers (IdP’s) providing clients with seamless, single sign-on across all Tyler back-office solutions. This also enables clients to use their own login and password policies, including the use of multifactor authentication for enhanced identity verification. The Tyler Identity User Store can be used to create and manage accounts that do not exist in the client’s IdP, such as contractors or seasonal staff, or clients without a supported IdP.

The following identity providers (IdP's) are currently supported for use with Identity Workforce: Microsoft Active Directory through Azure AD, ADFS or Okta AD agent, Google Cloud Identity, Identity Automation RapidIdentity, and Okta. Support for additional IdP's may require additional costs, available upon request.

Identity Community is Tyler’s authentication framework for community users external to an organization, such as vendors, businesses, and residents. Identity Community supports self-service account creation and management using an email or social identity providers, such as Google, Apple, Microsoft, and Facebook.

End-users can optionally enable multifactor authentication through any of these options.

Application Authorization
Tyler solutions employ a comprehensive Role Based Access Control (RBAC) security model to facilitate enduser access to applications, processes, and data. Roles can be tailored to offer a flexible level of access control within each Tyler solution. Access can be granted by solution, process, record – including read, update, and delete access – and field. Role permissions can span multiple modules within a solution providing streamlined administration for users who “wear multiple hats”. If overlapping or conflicting permissions are applied to a user, the highest priority / least restrictive access is granted to that user.

User and role administration is performed using easy-to-use, integrated applications, requiring very little technical expertise. In fact, while security can be centrally administered by a single department such as an organizations IT department, clients can also decentralize security by application module. Decentralizing security administration to subject matter experts such as a department head puts those most familiar an organizations’ processes in control of ensuring appropriate access control is adhered to.

Physical Controls
Data Center Controls
AWS’s data centers are state of the art, using innovative architectural and engineering approaches. Amazon has many years of experience in designing, constructing, and operating large-scale data centers. This experience has been applied to the AWS Cloud. The following subsections address some frequently asked questions about data center security.
x Physical and Environmental Security – AWS data centers are housed in nondescript facilities for anonymity. Physical access is strictly controlled at both the perimeter and at building ingress points by professional security staff using video surveillance, intrusion detection systems, and other electronic means. Authorized staff must pass two-factor authentication a minimum of two times to access data center floors. All visitors and contractors are required to present identification and are signed in and continually escorted by authorized staff. AWS only provides data center access and information to employees and contractors who have a legitimate business need for such privileges.

When an employee no longer has a business need for these privileges, his or her access is immediately revoked, even if they continue to be an employee of Amazon or AWS. All physical access to data centers by AWS employees is logged and audited. x Fire Detection and Suppression – Automatic fire detection and suppression equipment has been installed to reduce risk. The fire detection system utilizes smoke detection sensors in all data center environments, mechanical and electrical infrastructure spaces, chiller rooms and generator

City of Yuba City Proposed Solution
ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 19
equipment rooms. These areas are protected by either wet-pipe, double-interlocked pre-action, or gaseous sprinkler systems.
x Power – The data center electrical power systems are designed to be fully redundant and maintainable without impact to operations 24 hours a day and seven days a week. Uninterruptible power supply (UPS) units provide backup power in the event of an electrical failure for critical and essential loads in the facility. Data centers use generators to provide backup power for the entire facility.
x Climate and Temperature – Climate control is required to maintain a constant operating temperature for servers and other hardware, which prevents overheating and reduces the possibility of service outages. Data centers are conditioned to maintain atmospheric conditions at optimal levels.

Personnel and systems monitor and control temperature and humidity at appropriate levels. x Physical Plant Management – AWS monitors electrical, mechanical, and life support systems and equipment so that any issues are immediately identified. Preventative maintenance is performed to maintain the continued operability of equipment.
x Storage Device Decommissioning – As part of AWS’s storage decommissioning process, when a storage device has reached the end of its useful life, AWS procedures include a decommissioning process that is designed to prevent customer data from being exposed to unauthorized individuals.

AWS uses the techniques detailed in National Institute of Standards and Technology (NIST) 800-88 (Guidelines for Media Sanitization) as part of the decommissioning process.

The AWS Security Center provides up-to-date information on AWS audits by independent third-party auditors.

Tyler Office Access
Access to Tyler offices and facilities requires a key card. Key cards are issued to active employees and authorized vendors. Upon notice of termination, facility access is removed. A visitor log is maintained to track visitor’s access to the facility.

Confidential Destruction
Waste from Tyler offices containing confidential data is placed in locked shredding bins and destroyed by a third-party company.
o The involvement, if any, that is required from the owners of the applications to be integrated/interfaced to the ERP
Interface validation with third-party solutions is the responsibility of the client and their respective third-party system, unless contracted with Tyler otherwise. Dedicated testing environments and API developer portal built on swagger UI is included with Tyler application APIs. Testing API’s will allow for standard HTTP return status codes. Tyler solutions rely on application-based audits and logs for any database transactional hits.

Tyler is a partner and reseller of SnapLogic, one of the industry leading Integration Platform-as-a-Service (iPaaS). SnapLogic includes a library of out-of-the-box integrations with popular third-party solutions, including Tyler API’s. SnapLogic provides a number of additional tools and utilities for all phases of interface development, testing, and management.
o If Proposer has previous experience developing/implementing the relevant integration/interface Yes, and Tyler provides frontǦline support for select interfaces to thirdǦparty products. It is typically the customers responsibility to facilitate communication between Tyler and the third-party vendor. Interface support depends on the customer maintaining an active support agreement with the identified third-party

City of Yuba City Proposed Solution
ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 20
system as well as a current version actively supported by the manufacturer/developer of the product installed. Interfaces using Tyler APIs must be developed and managed by the client.

5.3 Data Storage and Backup

5.3 – Data Storage and Backup
Describe approach to data storage
Tyler solutions run on AWS storage services, including Elastic Block Store (EBS) and Amazon Simple Storage Service (S3). Tyler’s standard SaaS service includes unlimited data storage for all applications except Content Manager (CM). CM storage is limited to 1TB and is typically enough for CM Core deployments. Additional storage for CM can be purchased for an annual fee of $5,000 per TB. Integrated purge and retention tools are fully available to help manage CM content.

All production data is backed up automatically and retained based on the following application-specific retention policies:

Enterprise Permitting & Licensing, Time & Attendance, Enterprise ERP, Enterprise Asset Management Daily: 7-days
Weekly: 5-weeks
Monthly: 12-months
Content Manager
Daily: 7-days
Describe data backup process
As part of Tyler’s defined business continuity plan, full server snapshots are replicated across multiple Availability Zones. Availability Zones are connected to each other with fast, private fiber-optic networking, providing automatic fail-over for minimal disruption. Tyler employs a FIPS-compliant enterprise backup solution certified for CJIS and GovCloud use. Data transfer and storage is encrypted as defined in FIPS140-2 and FIPS140-3 standards over private connections within the AWS network.

Backups are retained as defined by application-specific retention policies. Data restoration requests must be submitted through the standard support ticketing process by client approved personnel only.

Describe the network bandwidth required between the City and hosting facilities Bandwidth usage can vary depending on application user type and daily functions; however, Tyler recommends 30 Kbps per concurrent user session for bandwidth utilization estimates Describe what options are available for dedicated bandwidth (if available) Not available.

Describe scalability options for computing power (CPU, RAM, and storage) Tyler provides fully scalable solutions to meet the requirements of all organizations, regardless of size, and can grow to meet increasing demands. Tyler’s applications perform well on modest networks with a handful of users—or on large, distributed networks with hundreds of users. Tyler applications have features to ensure large organizations run effectively. And smaller clients don’t outgrow Tyler solutions—they easily expand to meet clients changing needs.

City of Yuba City Proposed Solution
ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 21
Tyler applications are based on an n-tier architecture and can scale both vertically or horizontally; eliminating limitations for user growth. Additional user count licensing and disk space allocation can be increased as required.

Based on client feedback and experience, internal testing, and providing SaaS to our clients; Tyler has learned to tailor our solution deployments and infrastructure specific to a client's size and needs.

Indicate hosting provider (e.g. Azure, Amazon Web Services, etc.) Tyler’s subscription-based cloud applications run on AWS, the world’s most comprehensive and broadly adopted cloud platform. Applications are available securely from any internet connection, anywhere, anytime. Tyler Technologies manages all client cloud operations, including application upgrades and platform administration, providing clients with a single point of contact for all software and hosting needs.

Clients receive clear and concise documentation, defining all aspects of the relationship including contract (commitment to partner) and service level agreement (measurable expectations of availability).

Features
Tyler SaaS solutions eliminate heavy up-front and unpredictable ongoing on-premises infrastructure fees.

Many administration tasks are offloaded to Tyler support staff, allowing client IT staff to focus on other mission critical initiatives. Services include:
x System Administration. Tyler performs routine administrative tasks to provide application access at industry standard performance levels. This includes the installation, upgrade, support, and maintenance of the Tyler applications, platforms, and infrastructure. Tyler’s dedicated Network Operations Center (NOC) provides 24x7 performance and security monitoring of all cloud solutions. x Enhanced Security Controls. Tyler employ’s security controls through compliance standards, layers of network security, adherence to best practices, and qualified staff. All client data is secured and protected both in-transit and at-rest data using industry standard encryption protocols. Annual assurance audits include Service Organization Controls (SOC) 1 Type 2 and SOC 2 Type 2 conducted by an independent AICPA firm, and PCI Security Council PA-DSS and PCI-DSS validation for Tyler’s payment processing applications.
x Streamlined Account Management. Tyler solutions include zero-trust identity management built on technology from Okta, the industry leader in identity management. Support for industry standard identity providers (IdP’s) such as Microsoft Azure AD and Google Cloud Identity provides clients with seamless, single sign-on to Tyler back-office solutions. This also enables clients to use their own login and password policies, including the use of multifactor authentication for enhanced identity verification.
x Business Continuity & Disaster Recovery. Tyler solutions run on AWS, built to guard against outages and incidents, minimizing impact on customers and the continuity of services. Solutions and data are replicated across multiple AWS Availability Zones, connected to each other with fast, private fiberoptic networking, providing automatic fail-over for minimal disruption. Client data is backed up and retained using a FIPS-compliant enterprise backup solution certified for CJIS and GovCloud use and encrypted using FIPS140-2 and FIPS140-3 standards.

Benefits
x Reduce IT workload: IT resources are freed up to enable work on more strategic initiatives. x Eliminate server acquisitions and maintenance costs: Costly hardware purchases, upgrades, and maintenance are avoided.

City of Yuba City Proposed Solution
ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 22
x Easy budgeting: Tyler's SaaS subscription is a set fee, flattening the peaks and valleys associated with the acquisition of software and services. Subscribing dramatically lowers initial costs and provides consistent ongoing costs that can be easily budgeted for the duration of the agreement. x No secondary operational fees: Maintenance, support, and hosting fees are included. x Expandable: Additional Tyler solutions applications are easily added, as needed. saas x 24/7/365: Tyler provides round-the-clock, on-call coverage for critical outages.

5.4 Data Access and Security

5.4 – Data Access and Security
Describe how data access (functional vs. data roles) is managed Tyler applications feature a comprehensive Role Based Access Control (RBAC) security model for centrally granting access to the system across all application modules. Based on the standards written by the National Institute of Standards and Technology, RBAC facilitates the management of application access through groups of permissions—roles—and assigning those roles to any number of users. This allows administrators to maintain access for multiple users who may share common responsibilities simultaneously rather than on an individual, user basis.

Administrators create and customize an unlimited number of roles, consisting of permissions and parameters.

Users are added to the system manually, imported from Active Directory, or for clients with Enterprise ERP Human Resources Management, imported from the employee record. Finally, any number of roles can be assigned to a user, providing access to the system. All of this is done using easy-to-use, integrated applications, requiring very little technical expertise.

Traditionally, application security is centrally administered by a site's IT department. While this is still possible with Tyler, a unique and useful feature commonly employed by clients, is to decentralize security administration by application module to specific users or groups of users. This ensures those most familiar with the processes and records of a specific module are responsible for maintaining appropriate security rather than those in IT who may be less familiar.

Roles can be customized to offer an extremely flexible level of access control to all aspects of the solution.

This includes product, module, and menu item access (i.e., applications users can open), functional access (i.e., actions users can perform), and record and field level access (i.e., data users can access). Role permissions can also span multiple modules providing easy administration for those individuals who may “wear multiple hats”. If overlapping or conflicting permissions are applied to a user, the highest priority / least restrictive access is granted.

No role or user has access to a function or data unless explicitly assigned through a security role. When role permissions are changed, those changes are immediately applied to all users the role is assigned to. In addition, effective dates can also be applied to any role assigned to a user. This is extremely useful for times when a user may be filling in for another user during a known period. Rather than manually adding / removing roles to a user, an administrator can set effective start and end dates when the role permissions will automatically be applied and revoked. Finally, administrators can also choose to synchronize role assignments based on Active Directory security group membership, automating security administration entirely.

The result for clients is greater overall security, reduced IT administration costs and enhanced workflow. The RBAC security approach and unique ability to decentralize administration streamlines the process of adding new users and maintaining access, saving users valuable time.

City of Yuba City Proposed Solution
ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 23
Describe the environment (single or multi-tenant)
Tyler’s cloud infrastructure, platforms, and resources are multi-tenant, shared by multiple clients, however each client is provided with their own dedicated datasets. This complete data segregation adds an additional layer of security between environments.

If a multi-tenant environment, describe how is the data segregated Refer to previous response.

If a multi-tenant environment, describe how is security managed Refer to previous response.

5.5 Business Continuity and Disaster Recovery

5.5 – Business Continuity and Disaster Recovery
Describe approach to business continuity and disaster recovery Tyler solutions run on Amazon Web Service (AWS) state of the art data centers using innovative architectural and engineering approaches. Amazon has many years of experience in designing, constructing, and operating large-scale data centers. This experience has been applied to the AWS Cloud.

AWS builds to guard against outages and incidents, and accounts for them in the design of their services; so, when disruptions do occur, their impact on customers and the continuity of services is as minimal as possible.

AWS data centers operate in alignment with Tier III+ guidelines. More information regarding Uptime Institute guidelines employed can be found at: https://aws.amazon.com/compliance/uptimeinstitute/ As part of Tyler’s defined business continuity plan, full server snapshots are replicated across multiple Availability Zones. Availability Zones consist of one or more discrete data centers, each with redundant power, networking, and connectivity, and housed in separate facilities. They are connected to each other with fast, private fiber-optic networking, providing automatic fail-over for minimal disruption. Tyler employs a FIPS-compliant enterprise backup solution certified for CJIS and GovCloud use. Data transfer and storage is encrypted as defined in FIPS140-2 and FIPS140-3 standards over private connections within the AWS network. Backup of client production data occurs nightly and are retained as defined by application-specific retention policies. Data restoration requests must be submitted through the standard support ticketing process by client approved personnel only.

Tyler Technologies warrants its service to its standard service level agreement (SLA). The SLA defines service availability (% of uptime), and recovery point objective (RPO) and recovery time objective (RTO) for data centers used for Tyler SaaS hosting. Tyler’s business continuity plan is tested annually, and backup restore tests are performed weekly. Further information regarding Tyler’s business continuity plan can be found in Tyler’s most recent Type 2 Service Organization Controls No. 2 (SOC 2) report.

5.6 Service Level Agreements

5.6 – Service Level Agreements (SLA’s)
Describe supported SLA options (e.g. reliability, availability, performance, issue resolution, system response time, etc.)

City of Yuba City Proposed Solution
ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 24
Tyler Technologies warrants its service to its standard service level agreement (SLA). The SLA defines service availability (% of uptime), and recovery point objective (RPO) and recovery time objective (RTO) for Tyler cloud solutions.

If a client is unable to access Tyler applications for any reason, opening a support ticket is all that is required to report, and track downtime counted against Tyler’s SLA.

For more details, refer to the included sample Service Level Agreement Contract in Section 9.

5.7 Transition

5.7 – Transition
Describe proposed exit strategy at end of contract (contract transition) Upon termination or expiration of the SaaS contract, all application access is revoked. Clients are provided with a secure download of backups for all production databases in the native format they are currently hosted in. All client data is deleted from production environments 30 days following end of contract. Backup data is removed as defined by application specific retention schedule.

City of Yuba City Proposed Solution
ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 25

5.8 Response to Appendix A - Requirements

5.8 – Response to Appendix A – Requirements:

The City will provide a copy of RFP Appendix A in MS Word. To address this section, Proposers should use that file to address each requirement in Appendix A. Please see Appendix A for additional instructions.

The Proposed Solution section should not exceed fifteen (20) pages, excluding the response to 5.8 – Response to Appendix A – Requirements.

NOTES AND ASSUMPTIONS
Tyler Reporting Services
Wherever Tyler Technologies, Inc. has responded affirmatively to certain functional checklist questions/requirements/specifications as requiring the use of Tyler Reporting Services, (SSRS), the City of Yuba City is solely responsible for development of the necessary/required report(s), unless specifically indicated otherwise.

Interfaces / Customizations
Interface requirements agreed to by Tyler within this response will depend on the customer maintaining an active support agreement with the identified third-party system as well as a current version actively supported by the manufacturer/developer of the product installed.

Custom Modifications
Custom modifications, if quoted with a specific dollar value, are priced based upon the total proposed software package and the requirements set forth in the RFP. To the extent system components and/or requirements change, pricing for custom modifications may also change. If a custom modification is identified without a price, that identification is provided as an alert that the functionality is not available “out of the box,” and additional information is required from the customer before Tyler can price the modification. During the contract negotiation process, Tyler expects to work with the customer to identify the custom modifications that will be considered within the project scope, and to finalize the associated price. Those modifications will be delivered during the project on the schedule the parties mutually agree to during the contracting and/or project planning process(es). Any custom modifications that the customer requests post-contracting will be subject to an amendment or change order, which will address at least the pricing and schedule impacts of adding the subject modification to the original project scope and schedule.

Future Functionality
Future Functionality, when and if provided, will be released on the same timeline as the functionality is made generally available to customers under a maintenance agreement with Tyler. If a customer requires that such functionality be committed to within the contract, the functionality will be treated as a custom modification, payable by the customer.

Please reference the following pages.

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 1 Table of Contents INTRODUCTIONProprietary and Confidential – Subject to Restrictions on Disclosure ........................................................................................................................................................................................... 4 GENERAL ................................................................................................................................................................................................. 5 USER INTERFACE ..................................................................................................................................................................................... 5WORKFLOW ............................................................................................................................................................................................ 6DOCUMENT MANAGEMENT ..................................................................................................................................................................... 7REPORTING AND ANALYSIS ..................................................................................................................................................................... 7 FINANCE ................................................................................................................................................................................................ 10 GENERAL LEDGER/ACCOUNTING .......................................................................................................................................................... 10 GENERAL ...................................................................................................................................................................................................................... 10 CHART OF ACCOUNTS .................................................................................................................................................................................................. 12 JOURNAL PROCESSING ................................................................................................................................................................................................. 13 BANK RECONCILIATION ............................................................................................................................................................................................... 13 CLOSING ....................................................................................................................................................................................................................... 15 COST ALLOCATION ...................................................................................................................................................................................................... 16 REPORTING ................................................................................................................................................................................................................... 17 BUDGETING (OPTIONAL) ........................................................................................................................................................................ 17 GENERAL ...................................................................................................................................................................................................................... 17 REPORTING ................................................................................................................................................................................................................... 20 VENDOR MANAGEMENT ........................................................................................................................................................................ 20 GENERAL ...................................................................................................................................................................................................................... 20 REPORTING ................................................................................................................................................................................................................... 22 PROCUREMENT/PURCHASING ................................................................................................................................................................ 23 REQUISITIONS .............................................................................................................................................................................................................. 23 ENCUMBRANCES .......................................................................................................................................................................................................... 24 PURCHASE ORDERS ...................................................................................................................................................................................................... 24 CAL-CARDS ................................................................................................................................................................................................................. 25

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 2 YProprietary and Confidential – Subject to Restrictions on Disclosure EAR END .................................................................................................................................................................................................................... 26 REPORTING ................................................................................................................................................................................................................... 27 CONTRACT MANAGEMENT .................................................................................................................................................................... 27ACCOUNTS PAYABLE ............................................................................................................................................................................. 28 GENERAL ...................................................................................................................................................................................................................... 28 INVOICE RECEIPT/ENTRY ............................................................................................................................................................................................. 28 PAYMENT CALCULATION ............................................................................................................................................................................................. 29 PAYMENT PROCESS ...................................................................................................................................................................................................... 29 CHECK GENERATION .................................................................................................................................................................................................... 30 EMPLOYEE EXPENSE REPORTING ......................................................................................................................................................... 30FIXED ASSET ACCOUNTING ................................................................................................................................................................... 31 GENERAL ...................................................................................................................................................................................................................... 31 REPORTING ................................................................................................................................................................................................................... 32 GENERAL BILLING/ACCOUNTS RECEIVABLE ........................................................................................................................................ 32 GENERAL ...................................................................................................................................................................................................................... 32 REPORTING ................................................................................................................................................................................................................... 34 CASH RECEIPTS (CASHIERING) ............................................................................................................................................................ 34 GENERAL ...................................................................................................................................................................................................................... 34 REPORTING ................................................................................................................................................................................................................... 37 PROJECT AND GRANT ACCOUNTING .................................................................................................................................................... 37 HUMAN RESOURCES ........................................................................................................................................................................... 39 POSITION CONTROL .............................................................................................................................................................................. 39RECRUITING (OPTIONAL)....................................................................................................................................................................... 39 GENERAL ...................................................................................................................................................................................................................... 39 REPORTING ................................................................................................................................................................................................................... 40 ONBOARDING (OPTIONAL) ..................................................................................................................................................................... 40EMPLOYEE MASTER FILE ...................................................................................................................................................................... 41 GENERAL ...................................................................................................................................................................................................................... 41 REPORTING ................................................................................................................................................................................................................... 42 BENEFITS ADMINISTRATION .................................................................................................................................................................. 43 GENERAL ...................................................................................................................................................................................................................... 43 REPORTING ................................................................................................................................................................................................................... 44 LEAVE ADMINISTRATION ...................................................................................................................................................................... 45

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 3 Proprietary and Confidential – Subject to Restrictions on Disclosure PERSONNEL ACTIONS ............................................................................................................................................................................ 46TRAINING AND CERTIFICATIONS ........................................................................................................................................................... 46PERFORMANCE REVIEWS (OPTIONAL) ................................................................................................................................................... 47 EMPLOYEE SELF SERVICE (ESS) ......................................................................................................................................................... 47PAY ADMINISTRATION ......................................................................................................................................................................... 48 GENERAL ...................................................................................................................................................................................................................... 48 REPORTING ................................................................................................................................................................................................................... 51 TIME ENTRY ........................................................................................................................................................................................ 52 GENERAL ...................................................................................................................................................................................................................... 52 REPORTING ................................................................................................................................................................................................................... 53 PAYROLL PROCESSING ........................................................................................................................................................................ 53 GENERAL ...................................................................................................................................................................................................................... 53 PAYSTUB ...................................................................................................................................................................................................................... 56 REPORTING ................................................................................................................................................................................................................... 56 SEPARATION/OFFBOARDING ................................................................................................................................................................ 57 TECHNICAL ........................................................................................................................................................................................... 58 GENERAL ............................................................................................................................................................................................... 58REGULATORY COMPLIANCE/CERTIFICATIONS ..................................................................................................................................... 59SYSTEM AND DATA SECURITY ............................................................................................................................................................... 59INTEROPERABILITY/SYSTEM INTERFACE .............................................................................................................................................. 60DATA STORAGE ..................................................................................................................................................................................... 62DATA BREACHES AND AUDIT LOGGING ................................................................................................................................................. 63DISASTER RECOVERY ............................................................................................................................................................................ 64

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 4 Introduction As stated in RFP Section 4.2, Proposers must use this document to respond to the ERP requirements included herein. Proposers must respond to all of the requirements. Proposers muProprietary and Confidential – Subject to Restrictions on Disclosure st respond to each of these requirements with one of the following response codes:
x Y – Meets Requirement
x N – Does Not Meet Requirement
x F – Planned for future release
x W/C – Workaround Proposed or Customization Needed to Meet Requirement x T – Third-Party Solution to Meet Requirement
Note that response codes “Y” and “N” do not require written responses.

However, the other response codes “F,” “W/C,” and “T” do require written responses. For these codes, Proposers must describe how the requirement will be met in the “Response/Comment” column. For response code “F,” Proposers must provide a statement indicating the release number and date as to when the release is scheduled to occur. For response code “W/C,” Proposers must provide a statement indicating when any customization will be completed. For response code “T,” Proposers must describe the third-party solution, who is to support the implementation of it, and how and by whom the interface will be completed. Some requirements are marked “optional” (Budgeting, Recruiting, Onboarding and Performance Reviews), which means the City may or may not purchase them. Even though this is the case, proposers must respond to these requirements with the codes defined above, and ensure these requirements are accounted for in the Price Sheets. Note that while the costs for these need to be accounted for in the Pricing Sheets, since they are optional, they should be separate and not included in the total.

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 5 Proprietary and Confidential – Subject to Restrictions on Disclosure General
User Interface
# Requirement Response Code Response/Comments
Provides a browser-based user interface Y Supports mobile technologies (e.g. smartphones, tablets) Y
Provides the ability to drill-down and drill-across from a transaction view to the supporting source data and documents Y
Provides fully integrated functionality such that data is entered only one-time and available throughout the system(s) modules and available in near real time (single-points of data entry) to eliminate re-keying of information Y
Provides organized screen layouts (dashboards) that can be modified and made unique by each user Y Via Hub
Provides shortcuts for frequently accessed processes, screens, reports, etc.

Y
Provides search functions that reach across all applications and attachments Y May require SQL Server Reporting Services
Provides online help that is context sensitive and content appropriate with manuals also available for download Y
Provides auto population of fields based on entry of information in another field across all modules (i.e. entering a PO number will automatically fill in vendor information) Y Where available
Allows user to enter effective date of transactions throughout modules including future and past dates (based on defined security roles) Y Where applicable

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 6 Proprietary and Confidential – Subject to Restrictions on Disclosure Workflow
# Requirement Response Code Response/Comments
Provides integrated workflow management including generation, routing, notification and approval or rejection of forms, reports, other documents and processes (e.g. payable processing, purchase order requisitions, GL transactions, HR transactions, time entry, payroll processing, budgeting, personnel action forms, etc.) for all modules Y
Supports rules-based workflow routing to multiple approvers that can be concurrent or consecutive with prioritization, alerts, and electronic signatures Y
Provides ability to establish multiple approval levels based on user-defined criteria (e.g. dollar amounts, types of items purchased, document types, etc.) Y
Allows out of office approval delegation Y Integrates with the email system to assist in the notification/request of approvals, reject, corrections, and approval through/from email and mobile devices Y
Allows document attachment for review through all levels of workflow approval for all core modules Y Attachments via Content Manager
Provides rule-based alerts (including e-mail) for pastdue workflow items Y Provides user visibility of workflow queue for items within the system Y

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 7 Proprietary and Confidential – Subject to Restrictions on Disclosure Document Management
# Requirement Response Code Response/Comments
Provides the ability to create, store, and retrieve electronic images (e.g. purchase orders, payroll checks, accounts payable invoices, etc.) that are attached to the appropriate transaction record for all modules Y Via Content Manager
Supports multiple media formats (e.g. audio, video, image, etc.) and file types (e.g. Excel, Word, PDF, etc.) Y Via Content Manager
Offers drill-down/drill across features for users to view documents associated with financial, payroll, and personnel transactions Y Via Content Manager
Supports document scanning and attachment and makes documents accessible throughout all modules (i.e. requisition, purchase order, packing slips, accounts payable, budget, onboarding, leave, etc.) Y Via Content Manager
Reporting and Analysis
# Requirement Response Code Response/Comments
Provides a user-friendly inquiry and reporting tool that does not require specialized knowledge or training Y
Provides modeling tools to do ‘what if’ analysis and forecasting (i.e. analysis of revenue/expenditure trends and the ability to develop forecast projections) Y Via Budget scenarios program
Processes transactions in real-time and are immediately available for inquiry and reporting Y
Allows users to drilldown from reports and inquiries to source transaction Y

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 8 Proprietary and Confidential – Subject to Restrictions on Disclosure # Requirement Response Code Response/Comments
Provides full integration with MS Excel for all modules (e.g. worksheet export to Excel, data imported from Excel, etc.) and allows users to export reports to Excel that include formulas/formatting Y Formulas do not export to Excel in SQL Server Reporting Services, but formatting does
Provides the ability to copy and customize standard reports Y Standard SQL Server Reporting Services reports that are deployed with Munis can be copied, customized, and run from the native SQL Server Reporting Services web application. Standard/canned reports in Munis cannot be customized.

Provides the ability for reports to access data across all modules Y Via SQL Server Reporting Services
Provides the ability to create report notification groups and inform/alert groups when a new report is available Y EERP includes a Scheduler feature that provides this
functionality
Provides the ability to choose a format when exporting a report (e.g. Excel, Adobe, flat file, delimited, etc.) Y
Provides the ability for a dashboard/scorecard to include, at a minimum, user defined metrics, key performance indicators (KPIs), reports, charts, etc.

Y Via Hub
Provides the ability for reporting to be based on user security setting Y
Provides the ability to save and “publish” ad hoc reports for use by report author and others, and to generate these automatically at desired intervals Y May require SQL Server Reporting Services – reports can be attached via attachments in Content Manager, additionally EERP includes a Scheduler feature that provides interval generation functionality Provides the ability to report/query on any field within an application Y May require SQL Server Reporting Services
Allows for multiple output options (e.g. display, print, email, etc.) Y
Provides the ability to automatically run scheduled reports for distribution to a group or individuals.

Y EERP includes a Scheduler feature that provides this
functionality

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 9 Proprietary and Confidential – Subject to Restrictions on Disclosure # Requirement Response Code Response/Comments
Provides the ability to define report from/to dates, including dates across multiple fiscal years Y Some specific parameters may require SQL Server Reporting Services
Provides the ability to obtain summary level or detail level reports Y
Provides the ability to define sorting parameters for reports (i.e. by date, department, fund, etc.) Y Assumes use of existing sort parameters where applicable Provides the ability to stay current with changes in State and Federal payroll reporting requirements Y Tyler will commit to providing all state and federal
mandated reports or data file submissions required to be submitted to the state that are not already provided through standard reports or inquiry functions. In addition, any changes to mandated State/Federal specified file layouts will be provided for no additional license/maintenance fees to all clients who have a current Maintenance Agreement in place.

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 10 Proprietary and Confidential – Subject to Restrictions on Disclosure Finance
General Ledger/Accounting
General

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 11 Proprietary and Confidential – Subject to Restrictions on Disclosure # Requirement Response Code Response/Comments
Supports accrual, modified accrual, and cash accounting methods Y Enterprise ERP operates on a modified accrual basis of accounting. ACFR Statement Builder operates on a full accrual basis and can be used for reporting to show as cash based or full accrual.

Provides support for project accounting that crosses multiple fiscal years Y Via Project & Grant Accounting
Maintains accounts for transactions via elements such as fund, sub-fund, department, division, program, project, object, or any other element needed to meet the needs of the City Y EERP has a flexible chart of accounts structure that supports one fund (up to four characters), one object (up to six characters), one project (if applicable) (up to five characters), and up to seven configurable segments (up to 10 characters each) for a maximum account length of 45 alphanumeric characters across 10 segments.

Supports posting of transactions individually and/or in summary to the general ledger regardless of the transaction source ensuring each entry is balanced and auditable Y More information may be needed to confirm ‘summary’
posting requirements. Each journal entry is posted with detail information and includes any necessary balancing entries and are fully auditable.

Provides a message/warning if transactions are not balanced Y
Creates appropriate entries needed at the end of a period and for purposes of opening a new period (e.g. rolling forward account balances or reversing certain year end entries) Y
Provides the ability to add notes/comments to transactions that post to the GL Y
Enforces rules for entry validation based on roles at departmental/user level to prevent incorrect account coding Y
Captures multiple dates (e.g. transactional, posting, data entry, etc.) Y

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 12 Proprietary and Confidential – Subject to Restrictions on Disclosure # Requirement Response Code Response/Comments
Provides pooled cash accounting from multiple funds to a single bank account Y
Provides the ability to manage and reconcile multiple bank accounts and to transfer funds between the accounts Y Via Cash Management
Provides the ability to automate fund account allocations for certain transactions Y Via allocation codes
Allows multiple periods to be open at the same time Y
Chart of Accounts
# Requirement Response Code Response/Comments
Supports a flexible COA structure with room for growth within each field and expanded use of segments in the future Y Could establish Chart of Accounts and use leading characters to account for segment expansion. Tyler’s Enterprise ERP solution has a flexible chart of accounts structure that supports one fund (up to four characters), one object (up to six characters), one project (if applicable) (up to five characters), and up to seven configurable segments (up to 10 characters each) for a maximum account length of 45 alphanumeric characters across 10 segments.

Provides the ability to support the City as paying agent for Narcotics enforcement, LAFCO, Sutter Butte Flood Control Agency, and Sutter Animal Control Y Assuming proper COA setup
Provides ability to reclassify the COA as necessary in support of organizational changes without having to create an entirely new COA Y Provides ability to reclassify the COA as necessary in support of organizational changes without having to create an entirely new COA Accommodates potential City department reorganization by mapping historical transactional data across old to new account structures Y Account Change and Account Merge ability allows for
restructure assistance.

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 13 Proprietary and Confidential – Subject to Restrictions on Disclosure Journal Processing
# Requirement Response Code Response/Comments
Supports the following journal processing capabilities: one-time, standing, automated recurring, allocations & distributions, automatic reversals (accruals), imports, and corrections Y
Identifies the source of journals (e.g. budget, subsystem, import, etc.) Y Manages due to/due from transactions Y Allows multiple options for creating a journal (e.g. onscreen, import from Excel, copy a prior journal, etc.) Y Manual, Import, Recurring
Provides multiple description fields for the Journal Entries (i.e. long, short, free form, etc.) and document attachment Y Attachments through the proposed and recommended
integrated Content Manager document management solution Provides the ability to search for posted journal entries by date, keyword, creator, etc.

Y Some may require custom reporting via SQL Server Reporting Services
Provides the ability to save work in process and return to it at another date/time Y
Prevents the use of Journal Entry numbers Y Assume this is supposed to read ‘prevent the use of duplicate Journal entry numbers. Provides the ability to attach and view supporting documents for journal entries Y Attachments via Content Manager
Bank Reconciliation

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 14 Proprietary and Confidential – Subject to Restrictions on Disclosure # Requirement Response Code Response/Comments
Provides the ability to manage and automate reconciling of multiple bank accounts, including check clearing, stop pays, and credit cards Y Enterprise Cash Management provides access to the Bank Reconciliation program, which facilitates reconciliation between an organization’s bank cash account and corresponding EERP cash accounts. Users can enter a bank balance, including cleared and outstanding AP, Payroll, AR deposits, and general adjustments against the cash accounts, an EERP balance, and a reconciliation balance. Reconciliations are processed for a bank account and date range. Cleared and outstanding amounts are automatically calculated from EERP data when the reconciliation record is entered and the update is processed.

Other benefits of Enterprise Cash Management include the following:
x Ability to create multiple bank account numbers for each bank code.
x Ability to search bank items by bank code, account, date range, item type (adjustments, deposits or both), and status (cleared/not cleared/all). x Supports automated BAI file imports. x Transactions are cleared manually or automatically via BIA import or by using an XML interface with the bank.

Drill down allows users to view transaction details for cleared and outstanding totals within a date range
Provides the ability to transfer funds between bank accounts Y
Provides the ability to allocate interest, with weighting, to appropriate funds Y
Provides the ability to manage and automate reconciling of multiple bank accounts, including check clearing, stop pays, and credit cards Y See comment to 2.1.27 above
Provides the ability to transfer funds between bank accounts Y

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 15 Proprietary and Confidential – Subject to Restrictions on Disclosure # Requirement Response Code Response/Comments
Provides the ability to allocate interest, with weighting, to appropriate funds Y
Tracks cash balances on all funds by sub-fund and project Y Pooled cash
Automatically calculates and allocates interest earnings based on average daily balance and included interest charges for negative balances Y
Allows user-defined interest allocation methodology N Provides the ability for interest to be posted to a different fund/sub-fund from earning source Y
Provides for positive pay support with bank integration Y With compatible file
Closing
# Requirement Response Code Response/Comments
Supports period end soft close processes (i.e. secures new entries to a closed accounting period for specific modules) Y
Provides automated year-end closing of revenue and expenditure accounts and the automated roll forward of balance sheet accounts (as appropriate) to establish and maintain subsequent year beginning balances Y
Allocates interest earning, gain/loss on investments, and expenses as a percentage of daily cash balances, prepares journals of the allocations for review and posting Y
Allows multiple year-end closings periods (i.e. period 13, period 14, etc.) Y 14 periods available for posting (0-13) Period 13 is used for posting year-end close transactions as well as adjustments after closing. Multiple adjustments can be posted, but all post to period 13, and all year-end and open year balances are

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 16 Proprietary and Confidential – Subject to Restrictions on Disclosure # Requirement Response Code Response/Comments
adjusted accordingly.

Cost Allocation
# Requirement Response Code Response/Comments
Provides the ability to allocate total costs related to an internal service fund or activity across multiple
departments / divisions based on user defined factors
(i.e. employee count; square feet of office space; number of desktop computers)
Y Recurring Journal Entry
Provides the ability to bill from a
department/division/project to another
department/division/project or within a department
Y Interdepartmental Billing supported via Enterprise ERP General Billing.

Provides the ability to select specific revenue and
expenditure accounts to be compiled for future
allocation/billing
Y Allocation Codes
Provides the ability to generate a scheduled (monthly,
quarterly, annually) journal voucher for the
allocations/billings
Y Recurring Journals with Allocation Codes

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 17 Proprietary and Confidential – Subject to Restrictions on Disclosure Reporting
# Requirement Response Code Response/Comments
Provides automated month-end reporting Y Provides the ability to categorize and summarize transactional data in support of the Comprehensive
Annual Financial Report (CAFR)
Y VIA ACFR Statement Builder
Provides automated, flexible, and efficient monthǦend, quarterly and yearǦend reports Y
Provides the ability to download transaction data to
and upload data from Microsoft Excel
Y Where applicable assuming use of compatible formats
Provides the ability to drill down into transaction
data to view transaction details and related
transactions
Y
Provides a report to assist Journal Entry
approval/review and includes GL accounts and
names, amounts, descriptions, etc.

Y
Budgeting (optional)
General
# Requirement Response Code Response/Comments
Supports multiple budgeting methods (e.g. zero base, program base, line-item, rollover, etc.) Y
Calculates projected fund balances automatically (reflecting projected reserves, revenues, expenses and inter-fund transfers that would result in an ending fund balance) Y
Allows users to change key underlying assumptions to impact forecasts Y

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 18 Proprietary and Confidential – Subject to Restrictions on Disclosure # Requirement Response Code Response/Comments
Provides an automated electronic budget process with decentralized entry, workflow, and related notifications/alerts Y
Supports tracking budget revisions and mid-year amendments (e.g. mid-year estimates calculated by Departments) Y
Supports multiple budget years for expenditures, revenue, and projections Y
Supports Capital Improvement Planning, Project, and Grant budgeting Y
Tracks various budget versions (i.e. Submitted, Proposed, Amended, Approved), etc.

Y
Provides the option to initiate budgets as zerobased, with historical data (e.g. last year’s actuals) or with increasing/decreasing factors down to the object level Y
Allows departmental entry of justifications and background data (including attachments) related to requests; this information must stay with line item entries through budget level-up cycles Y
Processes mass changes to various accounts during budget process such as a reorganization, rates changes, etc.

Y
Offers the ability to control budget rollups at multiple levels, including mid-year estimates Y
Offers the ability to add/delete/reallocate/shift positions and update proposed budgets in real-time Y
Allocates employee costs by percentage to multiple accounts Y

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 19 Proprietary and Confidential – Subject to Restrictions on Disclosure # Requirement Response Code Response/Comments
Utilizes position control to facilitate personnel budget development Y Via Position Control functionality included with Human Resources & Talent Management
Automates roll-forward for selected operational and multi-year Capital Improvement Plan (CIP) project budgets Y
Provides modeling for “what if” scenarios and forecasting tools for 5 and 10 Year Budget/Cash Flow Projections Y Via Budget Scenarios
Provides an ability to apply “what if”/factor scenarios across funds, departments, programs, and/or objects as designated by staff Y
Offers the ability to restrict staff access, through security/rights, to specific funds, departments, objects, and/or object categories Y
Provides the ability to budget capital projects as single year or multiple years Y
Provides the ability to define and use statistics (e.g. invoices paid, recruitments completed, etc.) as performance measurements Y Via Performance Based Budgeting
Provides status tracking relative to departmental budget approvals Y
Offers the ability to define a maximum budget amount per funds, department, division, object, and report against the defined maximum Y
Provides multi-year budgeting, object, justification, description, etc. fields for each budgeting year Y
Allows negative amounts to be entered Y

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 20 Proprietary and Confidential – Subject to Restrictions on Disclosure Reporting
# Requirement Response Code Response/Comments
Provides the ability to generate a statement of special fund activity (projected fund balance with current appropriations) Y
Provides the ability to report/inquire by organization budget, amended budget, year-to-date budget, etc.

Y
Provides the ability to report on justification comments by budget line item Y
Offers the ability to see budget-to-actuals in realtime with drill-down capabilities Y Supports publication of the “annual budget document” via direct leveraging of system outputs/forms/reports T Via third party PatternStream
Provides full integration with MS Excel for budget development (e.g. worksheet export to Excel, data imported from Excel, Excel-based forecasting, etc.) Y Assumes use of compatible file formats
Vendor Management
General
# Requirement Response Code Response/Comments
Provides the ability to maintain vendor information to process payments Y
Supports auto-numbering of vendors Y +1 functionality for adding new vendors Provides the ability to categorize vendors by type Y Provides the ability to auto-generate vendor descriptions by type N
Supports decentralized vendor entry with workflow to approve vendor prior to availability for use Y

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 21 Proprietary and Confidential – Subject to Restrictions on Disclosure # Requirement Response Code Response/Comments
Provides the ability to attach supporting documentation Y Attachments via Content Manager
Provides the ability to add notes to a vendor record Y Provides the ability to identify vendors as active or inactive Y
Provides the ability to view changes to vendor records (i.e. address, name, phone, etc.) Y
Provide workflow to approve vendor changes Y Provides the ability to track insurance requirements and related certificates needed for doing business with the City Y
Ensures a W-9 is on file prior to setting up a PO or contract encumbrance Y
Identifies the last time a W-9 form was updated Y Via alerts Prevents duplicate entry of vendor records Y Based on SSN/TID Notifies staff if insurance requirements are near/past expiration Y May require SQL Server Reporting Services
Supports multiple remittance addresses for a vendor Y Provides the ability to check any contracts and PO’s associated with a vendor Y

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 22 Proprietary and Confidential – Subject to Restrictions on Disclosure # Requirement Response Code Response/Comments
Provides a vendor self-service portal with functions that include:
x Provide vendor related forms online x Submit requests to become “registered” vendors
x Register to receive notifications for formal
bids, and download information and upload bids accordingly x Check invoice/payment status x View appropriate transactional history associated with purchase orders (POs)
x Make changes to address, phone, primary
contact, etc.
x Ability to submit and track submitted
documents
Y Vendor Access
Provides appropriate levels of security to ensure vendor information is secure Y
Reporting
# Requirement Response Code Response/Comments
Provides the ability to report on payments made to a vendor in a specific year Y May require SQL Server Reporting Services
Supports CA Employment Development Department (EDD) reporting requirements (cumulative payments over $600 within a given year) for independent contractors Y Tyler will commit to providing all state and federal mandated reports or data file submissions required to be submitted to the state that are not already provided through standard reports or inquiry functions. In addition, any changes to mandated State/Federal specified file layouts will be provided for no additional license/maintenance fees to all clients who have a current Maintenance Agreement in place

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 23 Proprietary and Confidential – Subject to Restrictions on Disclosure Procurement/Purchasing
Requisitions
# Requirement Response Code Response/Comments
Provides the ability to configure alerts (percentage/dollar-based) when an invoice (or combination of invoices) is on the verge of exceeding the approved PO amount or the approved budget Y
Enforces the purchasing policy rules for “Open Market” purchases (i.e. under policy thresholds that do not require a PO), general purchases, informal bidding, formal bidding, authority limits, sole source, and emergency purchasing procedures Y Via Workflow
Performs budget checking during requisition, PO creation, and invoice processing Y
Supports the purchase of recurring services by automatically generating a requisition/PO based on pre-established criteria (e.g. health insurance, cleaning services, and leased vehicles) Y Copy a previous requisition for future purchase
Provides the ability to categorize a requisition as “in review” N
Provides the ability to hold a requisition before turning it into a PO Y Via workflow
Provides the ability to attach supporting documentation to requisitions Y Attachments via content manager
Provides the ability to enter notes or comments on a requisition Y
Provides the ability to indicate a requisition as a Fixed Asset Y
Provides the ability to pre-populate requisition fields as applicable Y Many fields can be defaulted based on selected department, vendor, commodity, etc with proper setup.

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 24 Proprietary and Confidential – Subject to Restrictions on Disclosure # Requirement Response Code Response/Comments
Provides the ability to capture various units of measure Y
Provides the ability to ID a requisition as taxable or non-taxable Y
Encumbrances
# Requirement Response Code Response/Comments
Provides the ability to pre-encumber/encumber requisitions and purchases, and the ability to override transactions that fail budget check Y
When a requisition or PO is cancelled, or closed, automatically reverses pre-encumbrance and encumbrance amounts as appropriate Y
Provides the ability to encumber service and construction contracts to separate numbers for PO Y
Purchase Orders
# Requirement Response Code Response/Comments
Provides the ability to have a single PO associated with multiple departments and/or funding sources (i.e. cross department PO’s) Y
Supports recurring/routine departmental PO’s based on dollar limits Y Via copy requisition
Supports annual, blanket, multi-department PO types
Y Types of purchase orders: Normal, Blanket, Dept/Emergency, RFP/BID, and Exported
Supports multiple line items per PO with the option of associating different GL accounts with each line Y
Captures internal or external justifications, notes, or comments on PO; internal comments must only be Y

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 25 Proprietary and Confidential – Subject to Restrictions on Disclosure # Requirement Response Code Response/Comments
visible to staff
Limits which users are authorized to override established PO limits Y
Provides near real-time expense tracking on all PO’s, including blanket PO’s Y
Prevents a PO from being issued to an inactive vendor
Y Warning received that the vendor is inactive. Additional stats of “stop” is available to prevent all activity against a vendor.

Provides options for distributing the PO (e.g. printmail, email, etc.) Y Provides the ability to re-open a purchase order that has been closed including recording the encumbrance (for current, not past FY) Y
CAL-Cards
# Requirement Response Code Response/Comments
Supports management and staff utilization of CALCards Y Assumes CAL-Cards are synonymous with Enterprise ‘P- Cards’. Answers are based on using the Purchase Card Statement functionality
Provides the ability to capture card issuance details Y Supports the ability to exclude items from CAL-Card purchases (e.g. entertainment, gas, meals, etc.) Y
Supports single purchase and overall transaction limits as indicated in the City’s CAL-Card Procedures Document Y Limits can be set on cards during setup, and warnings will be issued, but payments not stopped (as the purchase already occurred) Allows for CAL-Card single purchase and monthly limits to be increased on either a temporary or permanent basis and provide workflow approvals of limit increases N Limits can be tracked and updated, but are not sent through workflow
Provides the ability to flag sales tax Y Provides the ability to scan and attach receipts Y

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 26 Proprietary and Confidential – Subject to Restrictions on Disclosure # Requirement Response Code Response/Comments
Provides mobile access for the uploading of receipts N Supports interface with US Bank for CAL-Card statements, reconciliation, and monthly payments from City to bank Y
Provides automated notification to staff when statements are received from US Bank Y
Provides the ability to assign purchases to different GL accounts Y
Provides approval workflow (based on City’s Purchasing Policy) for purchase approvals Y
Provides the ability to close CAL-Card transactions on a monthly basis Y
Year End
# Requirement Response Code Response/Comments
Defines close and roll-over dates at system and module level Y System level only
Supports the maintenance of open POs over multiple years Y
Supports year-end activities such as conditional PO closure and the ability to roll purchase orders to the new fiscal year Y
Ensures old year GL reflects PO and encumbrance balances after roll-forward Y
Supports rolling of PO to different account number in the new year Y
Automates PO rollover process for individual or groups of POs including appropriate treatment of carryover budget amounts Y
Allows users to enter POs for the new fiscal year prior to the start of that fiscal year Y With proper setup

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 27 Proprietary and Confidential – Subject to Restrictions on Disclosure Reporting
# Requirement Response Code Response/Comments
Provides the ability to report/inquire on funds encumbered to date Y
Provides the ability to report “large” PO’s for a specific time period Y May require use of custom reporting depending on needs Provides the ability to report on P-Card exception items and trends Y May require use of custom reporting
Contract Management
# Requirement Response Code Response/Comments
Supports tracking and managing of master agreements (and their individual task orders) and contract status (e.g. milestone payment schedule, payment terms, payments, incentives, amendments/change orders, renewal status, expiration dates, insurance certificates, remaining balances, payments per deliverable, etc.) Y
Associates contracts to projects, grants, and/or purchase orders Y
Provides the ability to alert/notify of expiring contract items (e.g. contract end, insurance documents, licenses etc.) Y Via alerts

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 28 Proprietary and Confidential – Subject to Restrictions on Disclosure Accounts Payable
General
# Requirement Response Code Response/Comments
Supports payments to various entities including, but not limited to, vendors for services or goods, employees’ expenses, and retirees Y Employee expenses through employee expense
reimbursement
Provides and applies appropriate controls over all payments Y
Provides the ability to generate an annual report to calculate the City’s sales tax liability vendors did not collect Y
Invoice Receipt/Entry
# Requirement Response Code Response/Comments
Supports receipt and entry of hardcopy and electronic invoices Y
Checks the status of all open/pending invoices Y Provides the ability to identify duplicate invoices from vendor Y Based on invoice number/vendor number combination
Automates matching the PO, receiver, and invoice Y Manages vendor invoice credits with associated adjustments to encumbrances and PO balances Y
Supports checking available PO balance Y
Provides the ability to define a threshold for payments to process if it exceeds PO balance (e.g. due to taxes, shipping, etc.) Y

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 29 Proprietary and Confidential – Subject to Restrictions on Disclosure Payment Calculation
# Requirement Response Code Response/Comments
Alerts staff of and calculates payment discounts Y Supports automatically calculating shipping and taxes as appropriate for items being paid at time of data entry Y
Provides the ability to automatically calculate retainage using percentage indicated on a purchase order N Retainage exists at the vendor and invoice level
Allows for the tracking, deduction, and reporting of garnishments Y
Allows payments that can be set/scheduled with associated tracking of payment terms Y
Provides the ability to allocate pre-payment amounts across accounting periods (i.e. for software maintenance agreements) Y
Provides the ability to include sales tax owed if the vendor did not include the amount on the invoice Y This could be entered manually during Invoice entry as long as proper setup exists
Payment Process
# Requirement Response Code Response/Comments
For multi-line item POs, allows selection of one or more of those line items during invoice processing Y
Creates positive pay files Y Supports processing of 1099’s and 1099 reporting requirements Y
Supports refund and retention payment processing Y Provides the ability to short close POs based on user defined parameters Y

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 30 Proprietary and Confidential – Subject to Restrictions on Disclosure # Requirement Response Code Response/Comments
Provides for ACH and wire transfer payments to vendors with a system generated email notification that payment was sent Y
Provides alerts for invoices that are aging and where penalties may apply Y
Supports the creation of automated splits by fund, department, and/or account according to userspecified requirements Y Via allocation code
Check Generation
# Requirement Response Code Response/Comments
Provides an option for more than one check for a vendor during a check process Y
Supports generating multiple page checks Y Provides an option for on demand manual checks Y Allows reprinting checks without void and reissue if an error occurs during check printing Y
Employee Expense Reporting
# Requirement Response Code Response/Comments
Provides for web-based employee expense reimbursement
Y Via Employee Expense Reimbursement
Provides access via mobile devices Y Provides electronic workflow for review and approval Y

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 31 Proprietary and Confidential – Subject to Restrictions on Disclosure Fixed Asset Accounting
General
# Requirement Response Code Response/Comments
Provides functionality to capture and maintain information associated with leased and capitalized assets Y
Provides the ability to import new fixed assets and attributes Y
Supports barcoding/scanning of fixed asset tags Y Via Assets Mobile Provides, or interfaces with, asset tag solution Y Via Assets Mobile Provides parent/child associations for assets Y Allows multiple funding sources per asset, including grant funding sources Y
Provides the ability to link an asset(s) to a CIP project Y
Provides the ability to track non-capitalized assets Y Supports various asset depreciation schedules, the ability to change depreciation methodologies, and (from a point in time) recalculates depreciation based on the remaining life Y Each asset stores the depreciation method, which defines the frequency at which the depreciation occurs for the asset. The asset also stores the first year/period for recording depreciation and depreciation principal.

Allows for creation of an asset as part of purchase requisition Y
Tracks asset maintenance, including enhancement and transfers, and projected associated costs Y Improvements and transfers tracked through Capital Assets Transactions
Tracks asset disposal and salvage values Y Provides journal entries to record depreciation expense to the General Ledger Y
Supports the ability for an image to be attached to the asset record Y Via Content Manager

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 32 Proprietary and Confidential – Subject to Restrictions on Disclosure Reporting
# Requirement Response Code Response/Comments
Allows user to define fields for asset reporting to assist with analysis (e.g. APN, motor vehicles, buildings, equipment etc.) Y With user defined fields and SQL Server Reporting Services Reports on assets nearing full depreciation Y Assets by location, fund, depreciation, department, category. Reconciles to GL. For reconciliation, a report with all information on one line is important. Additions, disposal, or retirement reports Y Via SQL Server Reporting Services
General Billing/Accounts Receivable
General
# Requirement Response Code Response/Comments
Provides customizable invoice entry templates used to initiate invoice process Y
Supports invoicing of various entities including, but not limited to, citizens, former employees, businesses, developers, and other governmental entities Y
Supports invoicing for a variety of items, but not limited to false alarms, grants, property damage, COBRA, NSF check fee, and other miscellaneous items and services Y
Provides electronic workflow to route initial invoice entry document to user-defined reviewers and approvers before invoice is generated and receivable is established Y
Provides the ability to send copies of invoices via email Y

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 33 Proprietary and Confidential – Subject to Restrictions on Disclosure # Requirement Response Code Response/Comments
Provides functionality to record receivable and payments against customer accounts Y
Provides the ability to add user-defined messages to invoices and statements Y
Provides options for off-cycle and regular batch bill runs Y
Ensures appropriate cross-references to payment history and open balances for refunds processing Y
Provides statements of cumulative activity (vs. invoices only) Y
Provides comprehensive NSF check processing including reversing payments, appropriate reversing of accounting transactions, rebilling with NSF check charge(s), and associating these events with the customer’s account Y
Provides NSF support in the way of application of additional fees, adjustments to receivables, etc.

Y
Provides on demand and interval-based (i.e. weekly) past due payments Y
Provides accounts aging data sufficient to support collection activities Y
Automates 2nd and 3rd notices of missed payments Y Scheduler-enabled exports Provides the ability to reverse payments and prepare write off journal entries Y
Provides the ability to edit and revise invoices (i.e. address, comments, etc.) including the amount and will also record (adjustments) the revised amount to the General Ledger Y
Supports recurring invoices Y

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 34 Proprietary and Confidential – Subject to Restrictions on Disclosure # Requirement Response Code Response/Comments
Provides an option for payments to immediately affect customer account balances while batches are still open Y
Provides the ability to search items identified as uncollectable Y
Reporting
# Requirement Response Code Response/Comments
Provides end of month balancing reports Y Provides cash receipting, invoice detail (for what is billed), unapplied credit, and customer aging reports Y
Cash Receipts (Cashiering)
General
# Requirement Response Code Response/Comments
Provides a centralized cashiering module to collect and manage transactions (e.g. cash, checks, credit cards, ApplePay, electronic payments, etc.) from multiple locations on a daily basis Y Via Cashiering
Supports online payments Y Online payments can be processed via optionally proposed Enterprise ERP Payments Supports various payment processors Y 2 preferred processors: Tyler Payments & Open Edge.

Additionally, a credit card API is available that allows 3rd party processor to integrate with Cashiering. The development work, however, will fall on the 3rd party processor.

Supports daily tracking of deposits by user and type for end of day balancing Y

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 35 Proprietary and Confidential – Subject to Restrictions on Disclosure # Requirement Response Code Response/Comments
Provides summary and detail information regarding a day’s activity (e.g. number and amount of checks, number of cash transactions and cash total, etc.) Y
Supports immediate recognition of payments received by credit card Y
Supports the daily tracking of deposits by user and type for end of day balancing Y
Supports posting of all transaction receipts (cash, credit cards, checks, wires, etc.) Y
Provides daily reports in order to prepare deposit slips, track cash receipted in by denomination, check, electronic deposits, etc.

Y
Provides the ability to track deposits in transit/cash in vault Y
Provides the ability to track and report all monthly cash (and cash equivalents) receipted in and disbursed out Y Via SQL Server Reporting Services
Provides the ability to track and report number of specific types of transactions by certain time frame (e.g. number of EFT’s in a specific month, number of ACH’s executed during the year, number of deposits on a specific date, etc.) Y Via SQL Server Reporting Services
Provides bank interfacing, using transaction codes defined by the bank and the City Y
Provides bar code functionality to capture customer billing information (including amount due), with bar code appearing on bills, and ability to scan and retrieve customer billing information Y Scan line available for retrieval of billing information Provides for chip and Pi/PCI compliance capabilities Y Our processors are PCI compliant Supports breaking down of trial balance into the five unique GASB 54 categories Y

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 36 Proprietary and Confidential – Subject to Restrictions on Disclosure

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 37 Proprietary and Confidential – Subject to Restrictions on Disclosure Reporting
# Requirement Response Code Response/Comments
Supports reporting broken down by user, various date range and batch reports, Monthly Report of Cash Receipts, GL entries that hit cash, check register reports by account, and reports for cleared checks, uncleared checks, and voided checks Y Additional discovery to confirm information requirements, however, should be supported via custom report using SQL Server Reporting Services.

Project and Grant Accounting
# Requirement Response Code Response/Comments
Provides functionality to manage capital projects and grants, including tracking funding sources and budget to actual expenditures Y
Provides functionality to divide projects/grants into multiple categories and subcategories Y
Distributes costs and units (including labor hours) to an unlimited number of projects/grants (job phases) and sub-divisions (job-sub-phases) Y
Provides fields to record the type of grant (local, state, and federal), grantor information, match terms, grant begin and end date, and grant drawdown activity Y
Allows users to track activities and manage reimbursements/billings related to grants and to associate those grants with projects as appropriate Y
Supports multi-year projects/grants Y Supports multiple funding sources Y Provides real-time project and grant budget balances with the option to include pending staff time or pending invoices in process Y

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 38 Proprietary and Confidential – Subject to Restrictions on Disclosure # Requirement Response Code Response/Comments
Supports recording revenues and expenditures against the project/grant Y
Tracks actual, committed, and estimated (or budgeted) costs Y
Provides the ability to establish overhead rates Y Captures staff time and associates it directly to a project using a blended hourly rate (or actual rate) based on defined project rules Y
Reports on project and grant activity by period and over the life of the project/grant award Y
Supports collecting of reimbursements at a project level Y

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 39 Proprietary and Confidential – Subject to Restrictions on Disclosure Human Resources
Position Control
# Requirement Response Code Response/Comments
Provide reporting by position type, allocations, filled positions, vacant positions, changes during a userdefined time period, etc.

Y May require SQL Server Reporting Services
Associates positions with funding source Y Reserves a position upon request to fill a vacancy Y Identifies positions that are overfilled, under-filled, and/or double-filled Y
Identifies positions that are grant funded and has a position end date (end of grant date) Y
Supports the ability for positions to split funding across multiple funds, departments, and/or divisions Y
Tracks full-time, part-time, temporary, and seasonal employees Y
Contains a comments/notes field to capture details of position changes Y
Recruiting (optional)
General
# Requirement Response Code Response/Comments
Provides a web portal for recruitment information to be posted and allows applicants to submit applications and related documents Y
Supports the ranking of candidates Y Supports scheduling of interviews Y Supports sharing and display of candidate resumes among interview panelists Y

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 40 Proprietary and Confidential – Subject to Restrictions on Disclosure # Requirement Response Code Response/Comments
Reports point-in-time status of the completion of recruitment tasks Y May require SQL Server Reporting Services
Provides notification to hiring manager when a candidate accepts an offer Y
Reporting
# Requirement Response Code Response/Comments
Supports EEOE reporting requirements Y EEO4/5
Onboarding (optional)
# Requirement Response Code Response/Comments
Works with employee self-service web portal to facilitate on-boarding process, including completion and submission of documents, benefit enrollment forms, etc.

Y
Reports on status of completion of specific onboarding tasks including employee orientation, forms completion, etc.

Y
Facilitates sharing of new hire information between hiring department, IT, etc.

Y
Provides the ability to accept electronic signatures by new hires to sign enrollment forms, acknowledge receiving City equipment, safety training, etc.

Y

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 41 Proprietary and Confidential – Subject to Restrictions on Disclosure Employee Master File
General
# Requirement Response Code Response/Comments
Maintains data elements including but not limited to employee ID, basic demographics, address information, emergency contacts, survivor/beneficiary information, dependent information, history of salary changes (effective start and end dates) including eligibility for stipends, training/certification, and history of personnel actions Y
Provides the ability to store and view employee photo
Y Via Employee Inquiry
Provides the ability to attach documents to an employee file Y Via Content Manager
Provides employee directory functionality, and development of organization charts Y Directory assumes use of compatible export. Integrated org chart available
Provides the ability to track City property (badge, phone, vehicle, etc.) provided to the employee throughout tenure with the City Y
Provides the ability to track special assignments, including designation as Disaster Service Worker, assigned role in Emergency Management, etc.

Y
Notifies designated staff (i.e. Emergency Manager) when an employee can no longer fulfill their assigned role do to separation, leave, or other reasons Y
Supports setting maximum deduction for 457 deferred comp accounts (parent code that controls child codes) Y
Provides the ability to report on data required for labor costing/negotiations Y May require SQL Server Reporting Services

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 42 Proprietary and Confidential – Subject to Restrictions on Disclosure Reporting
# Requirement Response Code Response/Comments
Provides Seniority Listing, including Time in Grade Y Provide flexible organization chart reporting functions Y Assumes use of existing org chart functionality
Provides ability to select data required for labor costing/negotiations (e.g., ASRS, health, pay, employment dates, position title, etc.) Y May require SQL Server Reporting Services
Provides Federal and State government mandated reporting, including but not limited to:
x IRS 1099 x IRS 941 x SSA W-2 x EEOC EEO-4 x DOL VETS 100 x SCO Employee Compensation x EDD New Hire x EDD Quarterly Contribution Return and Report of Wages (DE9 and DE9C)
x EDD Report of Independent Contractors
(DE542)
x EDD SDI and UI
Y Tyler will commit to providing all state and federal mandated reports or data file submissions required to be submitted to the state that are not already provided through standard reports or inquiry functions. In addition, any changes to mandated State/Federal specified file layouts will be provided for no additional license/maintenance fees to all clients who have a current Maintenance Agreement in place.

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 43 Proprietary and Confidential – Subject to Restrictions on Disclosure Benefits Administration
General
# Requirement Response Code Response/Comments
Provides flexible, rules-based benefit management functionality to manage public employee benefits (including transition to retiree benefits) such as medical, dental, disability, life insurance, recreation, etc. as provided via EPIC, UNUM, AFLAC, etc.

Y
Complies with current and future Affordable Care Act (ACA) requirements, including automatic notification to employee when a dependent is at age 19 for full-time student status, and an annual courtesy check until age 25, with coverage discontinuance at age 26 Y Tyler will commit to providing all state and federal mandated reports or data file submissions required to be submitted to the state that are not already provided through standard reports or inquiry functions. In addition, any changes to mandated State/Federal specified file layouts will be provided for no additional license/maintenance fees to all clients who have a current Maintenance Agreement in place Complies with Consolidated Omnibus Budget Reconciliation Act (COBRA) requirements N
Supports California Public Employees Retirement System (CalPERS) to manage pension, health, and retirement benefits Y
Supports the pre-tax withholding of deferred compensation for part time, seasonal, and temporary employees in lieu of Social Security withholding and 457 plan for full time employees Y
Maintains eligibility dates for different plans based on different rules and which may differ from hire dates Y

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 44 Proprietary and Confidential – Subject to Restrictions on Disclosure # Requirement Response Code Response/Comments
Updates employee and retiree benefit records and reflects changes in pay in HR and payroll systems/modules and applicable 3rd party benefit providers whenever there are changes due to a life event, changes in eligibility rules, or requests for benefits Y
Supports the ability to track and invoice health care deduction amounts for retirees and COBRA participants through Accounts Receivable Y With integrated AR/GB
Supports administration of flexible spending reimbursement accounts Y
Supports the tracking of hours worked for seasonal and part-time employees up to the 1,000 hours which triggers PERS coverage, and 1,456 hours which triggers City benefits Y
Provides the ability to establish benefits tiers according to employee type (based on Date of Hire) (e.g. Board Members, full-time employees, parttime employees, retirees, etc.) Y
Reporting
# Requirement Response Code Response/Comments
Supports carrier billing/self-bill reconciliation and reporting Y
Provides ACA reporting form 1095C
Y Tyler will commit to providing all state and federal mandated reports or data file submissions required to be submitted to the state that are not already provided through standard reports or inquiry functions. In addition, any changes to mandated State/Federal specified file layouts will be provided for no additional license/maintenance fees to all clients who have a current Maintenance Agreement in place

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 45 Proprietary and Confidential – Subject to Restrictions on Disclosure # Requirement Response Code Response/Comments
Provides the ability to generate reports detailing amounts paid by the City for specific benefits versus amounts paid by employees Y May require SQL Server Reporting Services
Leave Administration
# Requirement Response Code Response/Comments
Supports managing available leave balances, including leave earned and taken, for all types of leave (PTO, vacation, sick, FLMA, disability, worker’s comp, modified duty, donated, etc.

Y
Allows for flexible rules for taking leave when balances are at zero, but accrual is pending Y
Provides the ability to cap accruals such as vacation, etc. and to cap dollars for deferred comp, etc.

Y
Notifies employees of leave that will be lost, cease to accrue, or automatically paid Y
Supports transfer of leave accrued by City employees to a catastrophic leave bank, and subsequent transfer of hours to other City employees for catastrophic health Y
Supports unlimited number of leave types/banks Y Types A-Z, 0-9 Allows employees to supplement disability pay with leave hours and calculate pay Y
Provides integration with time entry system for vacation/leave requests Y With integrated Time & Attendance
Supports leave accruals at different rates for different employee classifications Y
Support cash out of leave at different rates Y Provides the ability to generate ad hoc leave balance report by employee Y May require SQL Server Reporting Services

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 46 Proprietary and Confidential – Subject to Restrictions on Disclosure Personnel Actions
# Requirement Response Code Response/Comments
Provides online personnel action forms
Y Assumes use of existing personnel actions workflow
functionality. Various site defined personnel action types are supported. Review and approval by authorized users based on setup. Redaction according to role-based security (i.e. SSN). Approver ID serves as digital signature for approval. Attachments via Content Manager Provides functionality to manage personnel actions from initiation, review, authorization, and approval for actions such as promotions, demotions, salary increase, discipline, separations, leave, etc.

Y
Updates employee records in HR and payroll systems/modules to reflect changes in pay if needed Y
Provides the ability to set effective date and time of a personnel action (e.g. promotion, COLA, etc.) Y Effective date
Uses end dates to automatically stop the action at a specified time (e.g. discontinue administrative leave without pay, leave of absence, etc.) Y
Training and Certifications
# Requirement Response Code Response/Comments
Supports tracking of required position-specific job certifications, licenses, mandatory training, expirations, etc.

Y
Provides automated notification of expiring certifications/licenses to supervisors and employees based on user-defined rules N Not automatic, there are Hub cards that feature icons for expiring certs but no workflow, etc.

Associates certifications with applicable pay codes such that employees are paid or not paid based on N This would need to be handled manually by adding/removing pay codes from Emp Job Salary

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 47 Proprietary and Confidential – Subject to Restrictions on Disclosure # Requirement Response Code Response/Comments
the status of their certification
Updates employee records in HR and payroll systems/modules such that changes in pay can occur based on completion of training/certification events Y This could be handled through Actions as part of a process.

Does not happen automatically when certification or training record added.

Performance Reviews (optional)
# Requirement Response Code Response/Comments
Provides functionality to manage performance reviews/evaluations including tracking notifications, initiation, review results, and approvals Y
Provides notification of performance reviews coming due to supervisors and managers based on userdefined rules Y Assumes use of existing functionality, i.e. Hub card
Provides workflow to manage/approve electronic employee performance review/evaluation Y
Provides the ability to define and manage electronic evaluations/forms that are different by department and by job classification Y
Provides the ability to attach external forms and documents throughout the workflow Y Attachments via Content Manager to records associated with workflow where applicable
Provides alerts on past due evaluations and escalation notifications Y
Employee Self Service (ESS)
# Requirement Response Code Response/Comments
Provides an ESS portal that allows access and update to designated employee information Y

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 48 Proprietary and Confidential – Subject to Restrictions on Disclosure # Requirement Response Code Response/Comments
Updates employee records in HR and payroll systems/modules and applicable external systems (e.g. CalPERS, 3rd Party Benefit Providers, etc.) and allows HR staff to review and approve the changes Y Third party system updates require manual intervention outside of proposed system along with assumed use of compatible export file formats Provides the ability to view and print paycheck history, W2 history, personnel actions, leave balances, etc.

Y
Provides the ability to update/change benefits during open enrollment or due to a life event, and profile data (e.g. address, phone number, emergency contact beneficiaries, dependents, etc.) Y
Provides the ability for employee to reset password Y Supports access to the ESS portal from various types of mobile devices Y
Supports various employee requests (e.g. time off, expense reimbursement, etc.) and workflow for managers to approve electronically Y
Pay Administration
General
# Requirement Response Code Response/Comments
Provides functionality to manage employee pay including wages, Special Pay, State and Federal taxes, and accruals Y
Provides the ability to configure multiple accrual types (comp time, leave, workers compensation, vacation, etc.) Y
Provides the ability to manage multiple garnishment cycles (e.g. 24 pay periods and 26 pay periods) Y

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 49 Proprietary and Confidential – Subject to Restrictions on Disclosure # Requirement Response Code Response/Comments
Provides the ability to establish multiple garnishments using the same garnishment code for a single employee and automatically calculate garnishment limitation amounts Y Would require proper setup (i.e. date driven)
Supports multiple earning/pay codes including, but not limited to, Special Pays, Longevity Pays, Certification Pays, etc. that may change between pay periods Y
Enforces required pay type based upon activity (e.g. certain overtime reasons can only accrue as paid overtime instead of comp time) N
Allows for deductions to be taken every pay cycle, second pay cycle, or combination of the two Y
Supports employee groups with different benefits (e.g. differing leave accrual level, differing premiums, etc.) Y
Provides the ability to work under multiple jobs at different rates Y
Tracks when employees are eligible for scheduled pay raises and provides automated workflow to notify supervisor of scheduled pay raise. Upon supervisor approval, triggers automated notification that:
• Automatically notifies employees and their
supervisors
• Automatically updates employee records in HR
and Payroll systems/modules to reflect changes in pay
Y EERP provides notifications using Personnel Actions and automatic increases can be applied using the Mass Salary Change application which will update employee pay records. Employee raise eligibility can be identified using SSRS depending on the eligibility criteria. Employee notification of raise approval is not automatic.

Supports flexible definition of shift work, split shifts, and work schedules (e.g. 4/10, 9/80, 5/40, 48/96, etc.) Y
Supports flexible definition of shift work and work schedules to ensure compliance with FLSA legislation Y

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 50 Proprietary and Confidential – Subject to Restrictions on Disclosure # Requirement Response Code Response/Comments
Automatically generates payables for payroll deductions (e.g. insurance, pension, taxes, etc.) Y
Provides the ability to do ‘what-if’ analysis and modeling for salary increases, benefit changes, etc.

Y Via Salary and Benefits projections and/or Paycheck
Simulator through Employee Access
Calculates step, increment, and percentage pay adjustments for effective dating for all or a group of employees (e.g. bargaining units, classes, etc.) Y
Provides an automated process for retroactive pays based on the effective date of the retroactive pay (e.g. salary, benefits, contributions, and deductions) Y
Provides the ability to generate an annual estimate of the cost of Medicare for retirees including monthly, quarterly, and annual payment amounts Y Salary and Benefit Projections
Provides the ability to intercept reimbursements for accidental, personal CAL-Card use by an employee via authorized payroll deduction Y By adding the deduction to the employee. Easiest method likely utilizing import into Earnings and Deductions.

Tracks beginning of benefit date, benefit used date, etc.

Y
Supports creating an accrual for FMLA so that the leave can be recorded as part of employee time entry Y
Provides notification to HR, department admin, and the employee when an accrual balance is nearing a City-defined threshold N Employee can be notified when approaching a high or low limit, but no notifications to other departments or individuals.

Provides the ability to allocate payroll expenses across fiscal years when a pay period includes workdays across fiscal years Y
Supports multiple employee groups with different MOA requirements and benefits (e.g. differing leave accrual level, differing premiums, etc.) Y
Provides the ability to configure multiple accrual types (comp time, leave, workers compensation, vacation, etc.) Y

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 51 Proprietary and Confidential – Subject to Restrictions on Disclosure # Requirement Response Code Response/Comments
Supports mass change capability (e.g. COLAs) with review prior to accepting the mass change Y
Provides the flexibility to define “PERSable” codes including different setups for different employee groups, salaries, benefits, and other similar accumulators Y
Reporting
# Requirement Response Code Response/Comments
Provides the ability to maintain and report Fair Labor Standards Act (FLSA) information as required by legislation Y May require SQL Server Reporting Services
Provides the ability to report Family Medical Leave Act (FMLA) leave on an employee time entry Y May require SQL Server Reporting Services
Allows for reporting accrual and usage of benefits Y May require SQL Server Reporting Services Provides the ability to generate a report of worker’s compensation payments Y May require SQL Server Reporting Services
Supports other payroll administration reporting, including CalPERS, payroll journal, bank code tables, etc.

Y May require SQL Server Reporting Services

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 52 Proprietary and Confidential – Subject to Restrictions on Disclosure Time Entry
General
# Requirement Response Code Response/Comments
Provides functionality to collect time from various sources (e.g. Employee Self Service, mobile devices, employee badges used for facility entry, etc.), perform exception-based time entry for exempt employees, and time adjustments to multiple work schedules Y
Provides the ability to define and validate business rules at time of collection (i.e. prevents employees from entering adjustments that will cause employee leave balances to be exceeded) Y
Prevents employees from entering invalid data (i.e. earnings or pay codes they are not authorized to use) Y
Provides the ability to include notes or comments associated with time submitted Y
Requires notes or comments for certain activity types Y Provides functionality to allow time entered to be coded to projects, grants, or to another department with each line of time entered Y
Allows multiple pay periods to be open for time entry purposes Y
Provides workflow to collect time, perform exception based time entry, and time adjustments to multiple work schedules, including approval and submission to payroll system/module at the department level Y
Enforces minimum hour entry for certain activity types (e.g. Police court time) N Minimum Requested Amount setting on pay codes is for
accrued or non-accrued benefit codes only.

Provides the ability to track hours to special time codes (e.g. 4850, FMLA, etc.) Y

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 53 Proprietary and Confidential – Subject to Restrictions on Disclosure # Requirement Response Code Response/Comments
Provides pop-up notification at time of entry when employee is close to 1,000 hours worked for part time staff and retired annuitants Y Via work limits - When a work limit threshold is exceeded, the program displays graphical indicators on the Employee Time Maintenance and Supervisor Roster screens.

Provides system generated email notification to staff (employee and supervisor) who have not completed required time entry N System does provide other visual indicators and reports.

Provides the ability to identify and track part-time employee work hours on a weekly basis to ensure adherence to annual limits Y
Supports adjustment of leave accruals when employee is working less than full time or are in an unpaid status Y
Reporting
# Requirement Response Code Response/Comments
Provides reporting to support timekeeping rules (e.g. 1,000 hours worked report for part time staff, public safety grant overtime reports, changed time recap by employee, etc.) Y Reporting may require SQL Server Reporting Services
Supports exception reporting, including missing timesheets Y Reporting may require SQL Server Reporting Services
Payroll Processing
General
# Requirement Response Code Response/Comments
Provides functionality to calculate employee payroll, deductions, and accruals based on components managed in the benefits and pay administration module Y

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 54 Proprietary and Confidential – Subject to Restrictions on Disclosure # Requirement Response Code Response/Comments
Provides ability to select data required for labor costing/negotiations (e.g. CalPERS, health, pay, employment dates, position title, etc.) Y May require SQL Server Reporting Services
Provides the CalPERS required payroll report in xml format, as well as the ability to inquire/run CalPERS information for research purposes Y Tyler will commit to providing all state and federal mandated reports with data file submissions required to be submitted to the state that are not already provided through standard reports or inquiry functions. In addition, any changes to mandated State/Federal specified file layouts will be provided for no additional license/maintenance fees to all clients who have a current Maintenance Agreement in place.

Supports importing and entering time Y Imports assume use of compatible file format Provides functionality to calculate employee payroll, deductions, and accruals based on components managed in the HR benefit and pay administration module Y
Processes payments for government and 3rd party
agencies (e.g. benefits, retirement, etc.)
Y
Supports State and Federal tax filings
Y Tyler will commit to providing all state and federal mandated reports with data file submissions required to be submitted to the state that are not already provided through standard reports or inquiry functions. In addition, any changes to mandated State/Federal specified file layouts will be provided for no additional license/maintenance fees to all clients who have a current Maintenance Agreement in place.

Supports multiple concurrently open payrolls (e.g. vacation, sick or comp time cash outs, etc.) Y
Provides and enforces rule-based validation and prevents duplicate earning codes at employee level, etc.

Y
Provides user-defined exception hours’ analysis Y May require SQL Server Reporting Services

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 55 Proprietary and Confidential – Subject to Restrictions on Disclosure # Requirement Response Code Response/Comments
Supports multiple ‘re-runs’ of payroll prior to final payroll run Y
Generates paychecks, direct deposits (supporting deposits across multiple accounts on a single check), EFT files, bank files, and related positive pay files Y
Supports creation of annual pay and benefit letters, W2s, and ACA annual documents Y May require Mail Merge.

Tyler will commit to providing all state and federal mandated reports with data file submissions required to be submitted to the state that are not already provided through standard reports or inquiry functions. In addition, any changes to mandated State/Federal specified file layouts will be provided for no additional license/maintenance fees to all clients who have a current Maintenance Agreement in place.

The Proposer has reviewed the MOAs and associated documents listed on the following website: https://www.yubacity.net/city_hall/departments/hu man_resources/bargaining_unitThe proposed system will provide the functionality to meet the items included in the MOAs and associated documents. Any exceptions are to be communicated.

Y Tyler has successfully provided software to dozens of County’s with similar MOU’s to what has been provided here for review. Based on the responses to the functional requirements in the checklist, we feel as though Tyler’s Enterprise ERP is a strong fit for what the county will require. Additional discovery would be beneficial to confirm all functionality is standard.

Automatically generates journal entries to record payroll expenses to the General Ledger after payroll process is complete, including year-end splits and reversals Y
Supports bulk change capability (e.g. COLAs, bargaining unit changes, etc.) with review prior to accepting the bulk change) Y Via Mass Salary Changes
Supports the ability to run reports on staff for multiple years and pay codes Y May require SQL Server Reporting Services

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 56 Proprietary and Confidential – Subject to Restrictions on Disclosure # Requirement Response Code Response/Comments
Supports the ability to run employment verification reports for Public Safety that breaks down stipends Y May require SQL Server Reporting Services
Paystub
# Requirement Response Code Response/Comments
Identifies all elements used to calculate pay on the paystub Y
Identifies key information for employee (leave balances, allocation of direct deposit accounts, employee vs. employer pay benefits, etc.) on the paystub; ensures all required items are printed Y Via use of existing forms options
Generates PDF/electronic copy and automatically posts stub, W2, and ACA documents to the employee self-service portal Y
Reporting
# Requirement Response Code Response/Comments
Provides the ability to report on leave taken by department, division, employee, specific leave banks, etc.

Y May require SQL Server Reporting Services
Provides reporting of hours recorded for all employee types (e.g. full time, part time, retired annuitants, etc.) Y May require SQL Server Reporting Services
Supports exception reporting, including missing timesheets Y May require SQL Server Reporting Services
Supports the ability to run reports on staff for multiple years and pay codes Y May require SQL Server Reporting Services
Provides the ability to generate year-end payroll compensation reports by employee Y May require SQL Server Reporting Services

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 57 Proprietary and Confidential – Subject to Restrictions on Disclosure Separation/Offboarding
# Requirement Response Code Response/Comments
Provides functionality to manage processes and procedures for employee separation due to termination, retirement, resignation, or transfer Y
Supports initiation of the process and a checklist of tasks that need to be performed to successfully exit an employee based on type of separation Y
Updates employee records in HR and payroll systems/modules and applicable external systems (e.g. CalPERS, 3rd Party Benefit Providers, etc.) Y External system updates would require manual intervention.

Assumes use of compatible export files
Provides electronic employee separation workflow Y Supports recovery of equipment previously issued to employee Y As part of checklist
Supports the ability to deactivate or suspend seasonal employees as necessary Y

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 58 Proprietary and Confidential – Subject to Restrictions on Disclosure Technical
General
# Requirement Response Code Response/Comments
Provides a production, training, test, and development environment Y Production, Train, Test, and Implementation included in standard deployment. Additional application environments available, butwith additional subscription for cost for Tyler SaaS hosted customers.

Provides the ability to configure workflows, report parameters, and other elements to meet specific business needs using configuration and operating parameters provided by City and without the assistance of the software vendor Y
Provides for upgrades to accommodate changes in laws, regulations, best practices, and new technology Y
Integrates with Active Directory Y Provides system availability 24 hours a day, 365 days a year (not including Force Majeure Events or scheduled downtime) Y
Ensures scheduled downtime is pre-approved by the City one week in advance Y
Provides system uptime of 99.99%
N Tyler SaaS uptime SLA is 99.7% based on application
availability. For more details, refer to the included sample Service Level Agreement.

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 59 Proprietary and Confidential – Subject to Restrictions on Disclosure Regulatory Compliance/Certifications
# Requirement Response Code Response/Comments
Government Cloud Certified
N Tyler’s subscription-based cloud applications run on the AWS public cloud, the world’s most comprehensive and broadly adopted cloud platform.

Provides solution that is PCI compliant Y Cashiering is PAǦDSS validated to assist with PCI compliance.Provides a “Trusted System” according to the State of California Y
Provides hosting facility that is SSAE 16 certified
Y Tyler SaaS hosting operations is subject to annual independent audits. SOXǦ404 Financial and IT General Control conducted by an independent CPA firm, SOC 1 Type 2 and SOC 2 Type 2 conducted by an independent AICPA firm, and PCI Security Council PAǦDSS and PCIǦDSS validation for Tyler’s payment and payment gateway applications. More information on Tyler Industry & Regulatory Compliance, including how to obtain a copy of Tyler’s SOC Report Bridge Letter can be found at: https://www.tylertech.com/aboutǦ us/compliance.

System and Data Security
# Requirement Response Code Response/Comments
Utilizes Role Based Access Control or similar methodology for setting up functional and data roles Y Role-based security
Allows the system administrator to:
x Configure control access to the application,
modules, transactions, data and reports
x Define access rights (e.g. create, read,
update, delete) by user ID or functional role
x Define functional access rights (e.g.
processes, screens, fields, and reports) by user ID or functional role Y Ability to restrict user access to specific programs, access rights where available, and restrict to sensitive data where available.

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 60 Proprietary and Confidential – Subject to Restrictions on Disclosure # Requirement Response Code Response/Comments
x Restrict access to sensitive data elements
(e.g. social security numbers, banking data, etc.) by user ID, user groups or functional role Provides an audit trail with user, date, and time stamp throughout all modules, including field level change tracking (before/after values) as well as record level activity, including creation, viewing, editing, deletion and exporting (where applicable) Y
Provides the ability to view multiple levels of audit history in the application, not just the last change Y
Interoperability/System Interface
# Requirement Response Code Response/Comments
Provides an Application Program Interface (API) to enable the exchange of information (both inbound and outbound) with other business applications using a variety of protocols including but not limited to JSON, XML, and other flat text/delimited sources
Y
Provides security and auditing of data exported and imported via any API interface Y
Provides a configurable API such that new interfaces can be defined, or existing interfaces can be modified by an administrator without requiring the support of the software provider N The Proposed Tyler API toolkits create the flexibility for consumers to develop integrations tailored to their specific needs. Toolkit use requires work on the part of the Town and/or its designated vendor. The Tyler offering creates doorways into the system – including various parameters for flexibility. It does not, however, provide ad-hoc definition / modification of interfaces, or similar, at run-time.

Provides the ability to specify the editing criteria (including both field validation and consistency edits) to be applied to inbound transactions and ensures Y Inbound transactions will follow application business rules and get validated and show error log. Editing of field validation is not available

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 61 Proprietary and Confidential – Subject to Restrictions on Disclosure # Requirement Response Code Response/Comments
that transactions submitted via the API are subject to the same business rules as transactions submitted via the user interface Provides the ability to specify whether outbound interface transactions should be sent immediately or stored and forwarded at a specific time or at specific intervals Y Can be scheduled or run-on demand
Provides a notification to users of transactions that fail edits and provides a way for user to view, update, delete, and automatically resubmit transactions for processing or to be returned to the originating applications Y
Integrates or interfaces with the systems below through scheduled file exchanges and/or manually processed imports:

N/A N/A
x ClearGov (budget) Y Assumes use of compatible import/export files x DocuPhase (document management) Y Client is able to create the integration utilizing Tyler’s Content Manager Web Service API module. x Accela (BL, permitting and code enforcement
cash receipts)
Y Assumes use of flexible journal import functionality and/or leveraging of APIs via the optionally proposed Enterprise ERP API toolkit bundle x OpenCounter (cash receipts)
Y Assumes use of flexible journal import functionality and/or leveraging of APIs via the optionally proposed Enterprise ERP API toolkit bundle x Vector Scheduling (Fire scheduling) Y Could utilize Custom Generic Export Mapping XML or flat file x ESO or Telestaff/Firehouse (cash receipts) Y Assumes use of flexible journal import functionality and/or leveraging of APIs via the optionally proposed Enterprise ERP API toolkit bundle x Police Scheduling Software Solutions (POSS)
(time entry)
Y Could utilize generic time entry import
x Visual Computer Solutions (VCS) (Police Y Could utilize Custom Generic Export Mapping XML or flat file

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 62 Proprietary and Confidential – Subject to Restrictions on Disclosure # Requirement Response Code Response/Comments
Scheduling)
x CivicRec (cash receipts)
Y Assumes use of flexible journal import functionality and/or leveraging of APIs via the optionally proposed Enterprise ERP API toolkit bundle x LabWorks (invoices))
Y Assumes use of flexible journal import functionality and/or leveraging of APIs via the optionally proposed Enterprise ERP API toolkit bundle x NeoGov (recruiting)
Y Via compatible import/export file formats and/or leveraging of applicable optionally proposed Applicant Tracking API connector included within API toolkit bundle x CentralSquare CommunityPlus (UB) Y Assumes use of compatible import/export file formats and/or leveraging of applicable API offerings x Chameleon (cash receipts) Y Assumes use of flexible journal import functionality and/or leveraging of APIs via the optionally proposed Enterprise ERP API toolkit bundle x InfoSend (UB bills and online payment portal) Y Assumes use of compatible import/export file formats and/or leveraging of applicable API offerings x Third-Party Benefit Providers (WorkTerra, AFLAC, UNUM, CalPERS, Deferred Comp (RHS), Basic Pacific, Claremont, Vector Solutions) Y Assumes use of compatible import/export file formats where applicable
x US Bank (CAL-Cards) Y Assumes use of standard p-card import with Tyler’s Enterprise Accounts Payable x Wells Fargo Bank (Banking) Y Assumes use of flexible journal import functionality x AdobeSign (electronic signature) N No, however CM provides an electronic signature solution. x DebtBook (GASB 87 and 96) Y Assumes use of compatible import/export files and Fixed asset module is utilized Data Storage

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 63 Proprietary and Confidential – Subject to Restrictions on Disclosure # Requirement Response Code Response/Comments
Stores data in the Continental U.S. Y
Data Breaches and Audit Logging
# Requirement Response Code Response/Comments
Maintains audit logging to record access activity:
x Login/logout attempts by user and
workstation
x User submitted transactions x Initiated processes x System overrides x Additions, changes, or deletes to applicationmaintained data Y
Upon discovery or reasonable belief of any data breach, notifies the City by the fastest means available, and also in writing within 24 hours. Notification should include:
x The nature of the breach x The data accessed, used, or disclosed x The person(s) who accessed, used, disclosed, and/or received data (if known)
x What has been done to quarantine and
mitigate the breach
x What corrective actions has been taken to
prevent future breaches
Y Tyler Technologies’ handling of security breaches, including notification to customers, conforms to applicable state and federal law.

Provides daily updates regarding findings and actions performed until the breach has been effectively resolved to the City’s satisfaction Y When possible or required by state law ordinances.

Provides a report containing the results of the investigation of the breach Y When possible or required by state law ordinances.

ERP RFP 23-03 Appendix A – Requirements
City of Yuba City 64 Proprietary and Confidential – Subject to Restrictions on Disclosure Disaster Recovery
# Requirement Response Code Response/Comments
In the event of a disaster or catastrophic failure, informs the City:
x Within one hour x The scale and quantity of the data loss x What Proposer has done to recover the data and mitigate any effect of the data loss
x What corrective action Proposer has taken to
prevent future data loss
Y Tyler Technologies’ handling of disasters or catastrophic failure will conform to Tyler’s Service Level Agreement. We would be happy to talk with the City and address any concerns with Data access and security.

City of Yuba City Implementation Approach and Work Plan

ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 26
Section 6 Implementation Approach and Work Plan
Section 6 - Implementation Approach and Schedule
Proposers are to describe project implementation approach and schedule according to the following:

Tyler’s implementation process demonstrates our long-term commitment to our clients, with a methodology tailored specifically to the public sector. Your organization benefits from the fact that we perform our own implementations and know our software better than anyone. As a Tyler client, you receive guidance throughout implementation from experienced Tyler professionals who have implemented Tyler products in more than 10,000 public sector implementation projects. Tyler’s methodology is based on three vital foundations:
x Industry experience
x A globally recognized project management approach
x In-house expertise
Tyler utilizes its depth of implementation experience, working in tandem with our clients to put our methodology into practice. While each Project is unique, all will follow Tyler’s six-stage methodology. Each of the six stages is comprised of multiple work packages, and each work package includes a narrative description, objectives, tasks, inputs, outputs/deliverables, assumptions, and a responsibility matrix.

Tailored specifically for Tyler’s public sector clients, the project methodology contains Stage Acceptance Control Points throughout each Phase to ensure adherence to scope, budget, timeline controls, effective communications, and quality standards. Clearly defined, the project methodology repeats consistently across Phases, and is scaled to meet the Client’s complexity and organizational needs.

The methodology adapts to both single-phase and multiple-phase projects. To achieve Project success, it is imperative that both the City of Yuba City and Tyler commit to including the necessary leadership and governance. During each stage of the Project, it is expected that the City of Yuba City and Tyler Project teams work collaboratively to complete tasks. An underlying principle of Tyler’s Implementation process is to employ an iterative model where City of Yuba City business processes are assessed, configured, validated, and refined cyclically in line with the project budget. This approach is used in multiple stages and work packages as illustrated in the graphic below.

City of Yuba City Implementation Approach and Work Plan

ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 27
The delivery approach is systematic, which reduces variability and mitigates risks to ensure project success. As illustrated, some stages, along with work packages and tasks, are intended to be overlapping by nature to, efficiently and effectively complete the Project.

6.1 Work Breakdown Structure
The Work Breakdown Structure (WBS) is a hierarchical representation of a project or phase broken down into smaller, more manageable components. The top-level components are called “stages” and the second level components are called “work packages”. The work packages, shown below each stage, contain the high-level work to be done. The detailed project schedule, developed during project/phase planning and finalized during subsequent stages, lists the tasks to be completed within each work package. Each stage ends with a “control point”, confirming the work performed during that stage of the Project has been accepted by the City of Yuba City.

City of Yuba City Implementation Approach and Work Plan ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 28

6.2 Project Organization

6.1 – Project Organization
Provide a project organization chart highlighting Proposer and any subcontractor and/or third-party application provider key staff who will be assigned to the project Identify the responsibilities of each key staff member
Provide resumes and references for each key staff member The City reserves the right to request and check references for proposed key staff

6.2.1 Project Organizational Chart
Every implementation project is comprised of both client resources and Tyler resources working together at varying levels of involvement to ensure a successful implementation. The chart below outlines each of those resource groups. Please keep in mind that some resources in your organizations may fall into multiple groups.

6.2.2 Project Governance
Communication and transparency are essential to any successful implementation. Tyler and the City resources collaborate to determine core business needs, objectives and priorities. Project teams work together to navigate challenges as they arise according to the escalation paths outlined in the organization charts.

The chart below illustrates an overall team perspective where Tyler and the City collaborate to resolve project challenges according to defined escalation paths. In the event that project managers do not possess authority to determine a solution, resolve an issue, or mitigate a risk, Tyler implementation management and the City steering committee become the escalation points to triage responses prior to escalation to the City and Tyler executive sponsors. As part of the escalation process, each project governance tier presents recommendations and supporting information to facilitate knowledge transfer and issue resolution. The City and Tyler executive sponsors serve as the final escalation point.

City of Yuba City Implementation Approach and Work Plan ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 29

6.2.3 Tyler Resources
Tyler actively seeks the best talent to help us implement our solutions for our clients. Our staff consists of seasoned professionals with unique and proprietary skills, and years of industry experience, who are focused on specific products and in dedicated regions
Assembling a quality project team that suits for project needs is important. We appreciate your patience as we plan to allocate resources for your project phases. Upon award of contract, Tyler assigns a project manager and quality project team to ensure your implementation success. Tyler staff perform services in a professional, workman-like manner, consistent with industry standards.

The resumes presented in this proposal reflect the caliber and experience that Tyler will assign to this project.

Due to the variable duration of selection and contract processes, it is difficult for us to predict resources that would be available at project commencement.

Please see attached document, Sample Resumes.

6.3 Project Management

6.2 – Project Management
Describe the project management methodology/approach
Provide a Project Plan that describes your approach to Schedule Management, Cost Management, Scope Management, Communications Management, Issues Management, Risk Management, Change Management, etc.

6.3.1 Project Management
Our approach to project governance has been continuously improved during Tyler’s more than 35+ years of experience implementing software exclusively with public sector clients. No one knows the system better than Tyler staff. That’s exactly why we don’t contract third parties to do our implementation for us. We do it best. Project managers will be assigned to each phase of your project in order to staff the project with subject

City of Yuba City Implementation Approach and Work Plan

ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 30
matter experts during each part of the project. Our staff consists of seasoned professionals with unique and proprietary skills and years of experience, focused into dedicated departments.

6.3.1.1 Project Communication
Tyler understands the importance of having current, accurate, easily accessible during an implementation project. As part of implementation, each new Tyler client will be provided a project portal. The purpose of this site is to furnish the project teams with a central location to plan, store and access pertinent documentation and information relating to your Implementation project.

This site will be jointly maintained by the project teams for the duration of the implementation. Once the client has gone live, the portal will be maintained by Tyler’s client services team for the first year of live processing.

6.3.1.2 Management and Scope
The Tyler project manager (PM) and implementation teams will communicate regularly with your project team. All implementation deliverables generate reports which contain detailed assessments of task completion, staff participation and material absorption. The Tyler PM(s) will evaluate and measure the report results, communicating the gaps and adjusting the plan accordingly. Should issues arise during the project, there are several escalation paths that can be used laid out in the communication plan.

6.3.2 Project Planning
Project Planning is an important piece of any implementation. Tyler takes a custom approach to every project we lead. The project schedule is developed collaboratively with both project teams in order to meet your needs, while keeping in mind Tyler’s guidelines for implementation. Periodic project meetings will be scheduled where changes in scope, project length, or cost will be reviewed.

Tyler is open to discussing the project schedule in more detail and working out a mutually agreed upon plan that considers all project risks, requests, and resource constraints.

Tyler recommends a phased implementation approach, staggering start, and live dates for each phase of the project. Live dates will be targets but should not place unnecessary constraints on the project. The following schedule takes into consideration the City of Yuba City goals and Tyler’s recommended approach, and assumes the product will be used as is, without additional go-live customizations.

6.3.2.1 Proposed Project Phases
Proprietary and Confidential – Subject to Restrictions on Disclosure 2023 2024 2025
Phase Module
Project Plan in Months
2 5 7 9 11 12 13 14
Duration in
Months 1 3 4 6 8 10
Financials 12
2 1
12 Human Resource
Management
15 16 17 18

6.3.3 Schedule Management
During the planning stage of the project, a custom project plan will be created by the project teams that will serve as a working document throughout the entire project. These teams will meet regularly throughout the project to foster communication and ensure that all tasks are on schedule. In addition, periodic reviews and

City of Yuba City Implementation Approach and Work Plan ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 31
project meetings will be scheduled regularly where changes in scope, project length, or cost will be discussed.

Any change to the project plan, will be agreed to by the two project teams. The original project plan, as well as any subsequent versions of the document will be posted on the project portal and available to all project participants. This open access to project documents helps to ensure good communication among all project stakeholders.

Please reference attached Project Management Plan.

6.4 Implementation Schedule

6.3 – Implementation Schedule
As previously mentioned, the City will be using American Rescue Plan Act (ARPA) funds for this project. As such, adherence to any proposed schedule is critical. With this in mind, and considering a number of other factors, the City has identified the following base requirements pertaining to the implementation schedule:

Implementation to begin approx. January 2024
The COA must be implemented first
The City would like to be live on payroll as soon as possible, assuming this can be done in a logical and effective manner
Implementation must end by December 31, 2026
While adhering to the above, Proposers are to describe an implementation approach and schedule that addresses the following:

Describe the overall implementation methodology and approach Describe the implementation schedule, including the order (phasing) of major functionality (Finance and HR), including any overlap, as well as the timing of specific modules within those phases The schedule must identify phases, tasks, activities, dates, durations, resources, deliverables, and milestones
Please reference Implementation Approach and Work Plan above for implementation methodology and approach. Phasing schedule is shown above in Proposed Project Phases. For detailed phasing and implementation schedule please reference attached City of Yuba Gantt Chart.

6.5 Implementation Support Specifics

6.4 –Implementation Support Specifics
Identify the specific roles/responsibilities to be filled by Proposer, subcontractor, or thirdparty applications provider staff versus those to be filled by City staff. Include estimated level of effort for each staff person and when that person would be required (what part of implementation). Proposers should provide this information in Table 5.

City of Yuba City Implementation Approach and Work Plan ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 32
NOTE - In consideration of the overall implementation scope of work, the City expects staff to be available approximately 40% of the time. As such, the Proposer team’s implementation hours should be estimated accordingly. If this number changes, the City reserves the right to negotiate the amount of time to be provided by Proposer resources.

Table 5 – Roles and Level of Effort
Phase Task Start and
End Date
Proposer Staff
Role
City Staff
Role
Task
Hours
Work Split
(%
Proposer/
% City)
All Project Management 1/1/2024-
7/1/2025 Project Manager Project Manager 3344
60%/40%
with 25%
Dedicated
PM
throughout
project
All System Administration 1/1/2024-
7/1/2025
System
Administrator
System
Administrator
656 60%/40%
1 Financials
Implementation
1/1/2024-
1/1/2025
Implementation
Consultant
Functional
Lead(s) & Core
User(s)
7965 60%/40%
1 Financials
Implementation
1/1/2024-
1/1/2025 Conversions Lead Conversions
Lead 705 60%/40%
2 Human Resource
Management
Implementation
7/1/2024-
7/1/2025
Implementation
Consultant
Functional
Lead(s) & Core
User(s)
4212 60%/40%
2 Human Resource
Management
Implementation
7/1/2024-
7/1/2025 Conversions Lead Conversions
Lead 245 60%/40%
Describe the data conversion strategy, including what data should be converted, the number of years to convert, and the conversion methodology (extract, transform, and load). Describe previous experience with converting data.

Describe the training methodology/approach and how you ensure users are prepared to utilize the proposed solution. Include a description of how you address different learning styles (classroom, online, hands-on, etc.). The City may or may not be able to support the train-the-trainer approach, so Proposers are to identify alternatives (e.g. Proposer led training) and any related costs in RFP Appendix C – Price Sheets.

The City also expects the Proposer to develop training materials tailored specifically for the City to support the training effort.

City of Yuba City Implementation Approach and Work Plan ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 33
Describe testing methodology/approach, including the criteria, methods, and timing to ensure successful completion of user acceptance testing (UAT) prior to go live. Identify the specific roles/responsibilities pertaining to City staff vs. Proposer staff. The City expects the Proposer to develop the UAT plan and related test scripts, as well as any other testing materials necessary to support the testing effort, so Proposers are to identify any related costs in RFP Appendix C – Price Sheets.

The Implementation Approach and Work Plan section should not exceed fifteen (15) pages, excluding the project schedule.

6.6 Data Conversion
The data conversion process can be the most time-critical element of your project plan. Tyler develops crucial steps in our implementation process to support a successful data conversions plan. Our data experts conduct hundreds of data conversions every year mapping legacy data through custom written programs.

The purpose of this task is to transition the City of Yuba City’s data from your source (“legacy”) system(s) to the Tyler system(s). The data will need to be mapped from the legacy system into the new Tyler system format. A well-executed data conversion is key to a successful cutover to the new system(s).

With guidance from Tyler, the City of Yuba City will review specific data elements within the system and identify and/or report discrepancies. Iteratively, Tyler will collaborate with the City of Yuba City to address conversion discrepancies. This process will allow for clean, reconciled data to transfer from the source system(s) to the Tyler system(s).

6.6.1 Data Conversion Standards & Responsibilities
While Tyler’s data experts have extensive experience with data mining, conversion, and migration, it is your responsibility to provide Tyler with readable conversion data and to review the converted data for accuracy and completeness. Tyler recommends that you conduct due diligence to ensure that your team delivers clean data, to make data validation efforts seamless resulting in a high-quality migration.

6.7 Tyler Training Plan
Everyone’s learning style is different. That’s why Tyler offers several training formats to accommodate our diverse clients’ needs. Training by Tyler staff provides hands-on learning in your own labs. Your resources

City of Yuba City Implementation Approach and Work Plan

ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 34
receive consultative knowledge transfer sessions that are a combination of lecture and hands-on education, using your organization’s own data.

A mutually developed education plan lays out the process of transferring knowledge between you and Tyler.

The purpose of the education plan is to:
x Communicate the process to stakeholders and functional leaders x Answer specific questions (where classrooms will be established, what database environment will be utilized, etc.)
x Establish action items and link project personnel as owners x Define measurement criteria to ensure the plan has been successfully followed Your organization is set up for success with Tyler’s train the trainer approach to training and education plan developed over years of industry experience.

6.7.1 Scheduling and Attendance
Tyler prefers a classroom and curriculum approach for training to ensure knowledge transfer, comprehension, and retention. A successful user training session is in a classroom environment with a computer for each user, whiteboard, printer in the room or nearby, and one computer connected to a projector.

Class size should be limited to twelve (12) users in attendance to the training is critical to gain hands-on experience with the system.

6.7.2 Responsibilities
Tyler knows the value of being prepared for the use of our software in production. Our goal is to partner with you and lend our expertise based on experience, in order to allow your resources to be successful at go-live.

Both teams collaborate on all aspects of
training, discussed, and documented
during the planning stage of the project.

The expectation is for Tyler to provide
one or more occurrence of each
scheduled training. You will be
responsible for the logistics of the
training by completing such tasks as
scheduling resources and ensuring
facilities are available. These sessions are
to be attended by your key staff
members (i.e. functional leads and power
users) so that they can then disseminate
the information they learn to others in your organization if or when necessary.

6.7.3 Train the Trainer versus Tyler Led End User Training Tyler has implemented all projects with either Train the Trainer (TTT) or Tyler-Led End User Training. In both case, Tyler proposes several hours/days for each application. During the project planning stage for each application, these days will be broken up and the detailed tasks will be spelled out as well as the days/hours

City of Yuba City Implementation Approach and Work Plan

ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 35
included for each task will be outlined. Tyler’s standard preferred approach is TTT, and our Investment Summary includes a TTT, not Tyler-led End User Training approach.

Tyler-led End User Training sessions consist of training end users on the specific processing and reporting tasks they will be responsible for. Attendees will need computers and hands on training will be done at this time. One of the primary benefits of Tyler-led End User Training is freeing up Core Team time to allow for completion of final tasks before Go-Live such as conversions proofing. We often hear from our clients that as Implementation is wrapping up End User training and creation of documentation for said training becomes a secondary thought. Conversely, Tyler-led End User Training sessions may cause Core Power Users to take less ownership of the process.

The Train the Trainer approach allows your resources (the Power Users and Functional Leaders) to be involved in the initial training and software configuration while limiting the amount of time that End Users are involved in the project. Product Documentation, Hands on Training, Assigned Homework, Parallel Processing, and Testing Plans will all be employed to educate your resources. Tyler always tailors’ sessions to the participants, offering different levels of detail to users based on their use of the system and role.

In the TTT Approach, the Power Users and Functional Leaders are responsible for conducting training the end user community after all configuration is complete, which helps to increase adoption, solidify knowledge transfer, and lessen resistance to training and process changes. Additionally, your team will have access to the tools and services designed to support your internal training leads - TylerU, Tyler Community, Technical Support, State User Groups, Annual User Conference, client resources, knowledge articles and online help.

In both Train the Trainer and the Tyler-Led End User Training approaches, Tyler recommends training class sizes for end users to be no larger than 10-12 users per class. The most important thing is each person being trained has access to their own computer and they are in an environment away from their normal tasks. Our vast experience has also taught us that end users with access to customized training manuals, based on their site’s policies and procedures, retain information better and are more self-directed when doing work within the system following Go-Live. Access to these desk top procedure manuals aids in tempering the anxiety many end users feel about changing over to a new system.

6.7.4 Training Documents
Enterprise ERP applications include context-sensitive online help that provides field-level and procedural information to assist your resources in completing program tasks. When you are in a program and open help, the program displays a help screen generally consisting of an overview of the program or the selected program screen, procedures for completing the tasks within the program, and descriptions of the fields on the screen. The online help also includes a table of contents, from which you can select help for other programs within a product, review release notes, and access related resources.

City of Yuba City Implementation Approach and Work Plan ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 36
Help links to client resources and knowledge articles allowing for immediate access to additional information and resources directly from the help screen, as well as to Enterprise ERP Technical Support, for ease in requesting assistance from an Enterprise ERP expert. Online help is not customizable to clients.

Tyler incorporates computer-based training into our Training and Knowledge Transfer. Tyler U (University) delivers prerequisite and baseline information to all project participants. This approach allows Tyler’s Implementation Consultants to focus on more complex subjects and to focus on ensuring that all participants are moving along at the same pace. Tyler U is included for all clients at no additional charge.

What makes Tyler U so invaluable in the learning process is that it overlays your Production, Train, and Test databases. This means that the coursework is using your actual data that is specific to the user’s work. In addition, it does not require user management, usernames, or passwords since the classes are taken directly from the programs and the associated user permissions are already applied. Tyler U also submits a weekly report on classes taken and provides the information directly so an assessment can be performed as to the level of study and difficulty that is ongoing.

City of Yuba City Implementation Approach and Work Plan ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 37
Tyler Hub is a powerful platform that can improve the
efficiency of all Enterprise ERP users. By connecting
powerful and diverse data sources, Tyler Hub enables you to monitor key processes, quickly execute routine tasks and eliminate time-consuming data searches. Tyler Hub is built on a series of preconfigured cards designed to
visualize standard sets of data for various job functions and tasks. Select from the sets of cards — or content
packs — for accounts payable, asset management, payroll, utility billing, human resources, purchasing, inventory, and more. Users have the option to adjust the data as needed and specify how it is presented — or simply to use the
cards as they are.

A Hub page can be assembled to focus on a specific process such as hiring or benefit tasks or can be configured to reach across Enterprise ERP solutions to combine cards from Utility Billing, Accounts Receivable, and the General Ledger. A page can combine data analytics, reporting, and task functions, and users can add modify and add pages to their platform stack as their job functions evolve. Real-time data analytics and active links give Hub users an advantage. Instead of taking the time to open multiple programs to find data, Hub centralizes the data you need and makes it instantly accessible — quickly click on line items to access transactional details, locate a site on a map, approve or reject a transaction, or other action. By having everything visible and accessible, Hub users have more time to analyze their data rather than searching for it.

Finally, Tyler also maintains a complete set of documentation that is available to all users through our client resources, including our knowledge articles with our knowledge centered service focus. Our client resources provide users with a single, easily accessible location to find all existing documentation on the Tyler product(s). Included are procedure documents, file layouts, user guides, installation manuals, setup documents, system administrator documents, data schemas, training exercises and much more.

Tyler does not provide custom documentation to our clients as part of the traditional implementation process. Custom documentation is available through our Business Process Consulting offering. If you would like more information about this service, please ask your Sales Account Executive. However, Tyler’s implementation methodology supports the creation of custom documentation by your project team members as a training method and tool, which helps to reinforce the transfer of knowledge to resources during all phases of the project.

6.8 Solution Validation
Making sure your new system works the way you need it to be is paramount to the success of the implementation. Tyler’s quality management and validation plan addresses both the project and the product, while ensuring project objectives are met. The project teams validate the solution throughout the life of the project to expose issues that would normally only be revealed in a production environment. A comprehensive validation plan is set in place and may include system infrastructure audits, conversions, and modification delivery.

A controlled environment is created for high-level product modification validation, import and export interface, functional flow, and reliability.

The goal of validation is for end users to gain extensive product experience, develop a high level of confidence in Tyler’s products, and understand their specific functions within the solution.

City of Yuba City Implementation Approach and Work Plan

ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 38
Expected benefits from the completion of validation also include:
x The infrastructure of hardware and network design is thoroughly vetted x Modifications are delivered and fully integrated into the solution x A managed issues list is fully quantified
Issue tracking, resolution accountability, and completed issue resolution are necessary in a successfully completed project. The validation phase is a shared responsibility and must be recognized as such.

City of Yuba City Ongoing Maintenance and Support
ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 39
Section 7 Ongoing Maintenance and Support
Section 7 – Ongoing Maintenance and Support

7.1 Help Desk

7.1 – Help Desk
Help desk location(s), staffing, ticketing system utilized, processes, and procedures Ticket prioritization, response time commitments, and escalation procedures Support hours (in Pacific Time)
Number of help tickets per year and average resolution time by priority level Our mission is to deliver superior service by providing a timely response, issue resolution and operational support, resulting in a high-level of client satisfaction. Unlike some companies who outsource their application support to a third party, Tyler offers a complete solution of customer support services provided by our in-house experts.

Transparency is important, that’s why every support incident is logged into Tyler’s Customer Relationship Management System and given a unique incident number. This system tracks the history of each incident and each incident is assigned a priority number, which corresponds to your needs and deadlines. Clients can track the progress of these incidents online using Tyler’s support portal.

Tyler provides online and continuing education resources for our clients, including but not limited to the following resources.

City of Yuba City Ongoing Maintenance and Support

ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 40
x Tyler Search – an online query tool that provides answers for your questions by culling through all Tyler’s online resources using Knowledge Centered Service x Tyler Knowledgebase- a documentation library in a single, easily accessible location x Tyler Community – Tyler’s online forum available 24/7 x Tyler University- Tyler’s e-learning solution to enhance support and training of your employees using your data
x Tyler Release Management Console- Shows all release version information, with a summary of each release and associated enhancements, open, closed and non-critical issues x Online Help- context sensitive field help and procedural information to assist your team in completing program tasks
x Answer Panel- As you begin entering your case details, Tyler Search presents results in the panel that matches your question. Answers provided are the most relevant to your question, regardless of the source of the information.
x MyView- MyView is a screen capture tool to give Support more information to assist clients with a case. The recording is linked to the case and visible in the Online Support Incidents portal. x Online Support Portal- log or manage incidents and attach documentation and screenshots x GoToAssist & Bomgar- remote assistance from Support used to connect to your desktop x Phone- Tyler provides a dedicated 800 number that places no limits on who from your team may contact Support, or the number of calls placed
x State User Groups – forums organized by Tyler staff and attended by existing clients to get the latest information on Tyler products
x Annual Conference – Tyler Connect features online courses taught by Tyler subject matter experts hosted in a different city each year

7.1.1 Focused by Application
Regardless of how your team contact us, we are here to help. Tyler Technical Support is divided into application specific teams to enable product specialization and provide timely resolution of support incidents.

This application specific approach allows our Technical Support Representatives to focus on a small group of applications offering a high level of product expertise to our clients. Customer support’s goal is to return all requests for Support within one business hour.

City of Yuba City Ongoing Maintenance and Support

ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 41

7.1.2 Incident Tracking
Tyler records all your contacts and incidents in a customer relationship management system. This system tracks the history of each incident, including the contact, time, priority level, case description, correspondence, attached files, support recommendations, your feedback, and the resolution. The priority is assigned to each case as it is logged based upon the initial information provided and can be modified.

Last year we fielded 190.487 incidents. 64% were responded to within one hour of the client’s contact. 23% of incidents were resolved within one hour of the client’s contact.

Below are the resolution times, in days, by level of criticality thus far for 2023

1 -
Critical 2 - High 3 - Medium
4 – NonCritical
Financials 1 2 2 2

City of Yuba City Ongoing Maintenance and Support
ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 42
Human Resource
Management
122 1
Reporting Services 2 3 3 1
Revenue 3 3 3 2
TSM 1 3 4 1
TSM ExecuTime 1 3 3 1
TSM SaaS 1 2 2 4
Tyler Forms & TCM 2 4 4 1
Utility Billing 2 3 1 6

7.1.3 Software Updates & Maintenance
Tyler deploys industry leading technology and features that are continually enhanced through a process of perpetual upgrades as part of our Evergreen Philosophy. This includes a continuous stream of significant, yet manageable updates deployed over the life of the application with minimal disruption to our clients.

Tyler application upgrades are released quarterly. Software corrections, known as cumulative updates, are made available for download between quarterly releases. All releases are cumulative allowing clients to upgrade to the latest application version directly.

7.2 System Monitoring

7.2 – System Monitoring
Describe how the system will be monitored and how and when the City will be informed of system performance issues, etc.

Tyler hosting services include a dedicated Network Operations Center (NOC) for 24x7 monitoring of system utilization and network activity. Tyler employs a variety of industry standard solutions for monitoring and intrusion detection and prevention. A variety of routine scans are performed regularly including vulnerability scans, external penetration tests, and static and dynamic security scanning. Tyler also leverages a third-party service for 3rd party for DDoS detection and mitigation.

To effectively protect Tyler’s business and the client data in our care, a Security Incident Response Procedure is in place, defines employee responsibilities, and is available to all employees. Tyler’s incident response plan, based on the NIST 800-53 Framework, defines a measured, repeatable process for determining, handling, and recording when an incident occurs. Tyler Technologies’ handling of incidents, including notification to customers, conforms to applicable state and federal law.

Design, implementation, and maintenance of the IRP are the responsibility of Tyler’s Information Security Office. The IRP establishes procedures for responding to and reporting of security incidents. A Post Incident Review is conducted once a threat has been successfully eliminated. The Incident Response Plan is tested no less than annually.

City of Yuba City Ongoing Maintenance and Support
ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 43
Tyler regularly monitors the networks, systems, environments, and applications within its control. As part of that monitoring, if Tyler identifies a potential security incident, Tyler follows established policies and procedures to contain, respond to and mitigate such incidents. Tyler’s standard practice is to treat the details of any such incident as confidential, given that releasing those details to the public itself creates a security risk, and/or because those details may include a client’s confidential information.

Further information regarding Tyler’s incident response plan can be found in our most recent Type 2 Service Organization Controls No. 2 (SOC 2) report.

7.3 Post-Implementation Evaluation Report (PIER)

7.3 – Post-Implementation Evaluation Report (PIER)
Proposers must develop one PIER six months after the Finance implementation and one six months after the HR implementation. Describe how Proposer would support these PIER assessments, including the expected PIER content, how gaps in system utilization would be identified, and how those gaps would be addressed through additional training [minimum one full week (40 hours) of Proposer led, onsite training after each of the two implementations].

As part of your implementation project, Enterprise ERP proposed post-implementation evaluation. We recognize your desire to engage a lifecycle plan with Tyler. We have proposed reserved resources to carry out the post-implementation analysis and recommendations, as well as resources to carry out the recommendation made during analysis for each phase. Please reference the included investment summary for the associated cost.

7.4 Application Upgrades

7.4 – Application Upgrades
Describe the upgrade process, including:
o Identify the frequency of upgrades over the past two (2) years Tyler application upgrades are released quarterly. Software corrections, known as cumulative updates, are made available for download between quarterly releases. All releases are cumulative allowing clients to upgrade to the latest application version directly.
o Identify the typical upgrade schedule
Tyler Technologies employs a comprehensive and easy-to-use Release Life-Cycle Policy for its software. The release life-cycle policy is designed to balance clients' need for flexibility and stability, while meeting the demands for strategic product enhancements. This policy benefits clients by providing:
x Consistent and predictable product release timelines and maturity levels x The ability to accurately budget, plan, and schedule upgrade resources around major processing events
x The assurance of continually operating on a fully supported release Each application upgrade release evolves through the following phases as part of the Release Life-Cycle Policy.

City of Yuba City Ongoing Maintenance and Support

ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 44
Early Adoption (EA). Release is available to select clients participating Tyler’s Early Adopter Program. This ‘real world’ testing enables Tyler to deliver the highest quality, customer-tested releases. This phase takes place 1- 2 months prior to General Availability.

General Availability (GA). Release is available to all clients for installation and actively supported. This phase lasts 12-15 months before a version is retired.

Product Retired (PR). Release receives minimal support services and no development activity. Clients must upgrade to a newer release to receive future update.
o Describe the testing performed on potential upgrades
Tyler provides a dedicated Test environment for most application deployments. This environment is solely intended to install new updates for clients to familiarize themselves with new features and enhancements prior to installing to the Production environment.

Clients are responsible for testing against their own environment. However, Tyler provides several resources to assist users in learning about and training users on new functionality including webinars, "what to test" documents, and detailed release notes.
o Describe how upgrades would be performed
Tyler’s industry leading technologies and features are continually enhanced through perpetual upgrades as part of our Evergreen Philosophy. Clients are provided with the flexibility to choose what and when application updates are applied as defined by Tyler’s Release Life Cycle Policy.

Application release upgrades are installed by Tyler’s Systems Management support services at the request of the client. Most Tyler applications also include incremental update packages clients can install on their own.

Update packages can be manually installed or scheduled for automated installation. Release upgrades and update packages are cumulative, allowing to upgrade directly to latest release regardless of the version upgraded from.
o Describe any downtime related to upgrades
Applications are typically unavailable to end-users during the upgrade process. This duration varies on several factors including update type, number of updates, and application database size. Installation of application upgrades can take up to several hours; application updates typically range between serval minutes to an hour.
o Describe how the City would be notified of such upgrades and how much lead time would be provided Tyler provides several resources to receive information regarding upcoming releases. Tyler Community provides a secure, online setting where clients can subscribe to release update notifications. Release notes are published for all applications. Tyler also regularly provides free webinars highlighting new features and functionality included in application releases.
o Describe the City’s ability to delay, test, accept, and/or deny applying upgrades Clients are provided with the flexibility to choose what and when application updates are applied as defined by Tyler’s Release Life Cycle Policy. Clients can choose to upgrade to each new release or to skip releases if they upgrade once per year.

City of Yuba City Ongoing Maintenance and Support
ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 45

7.5 Change Management

7.5 – Change Management (post implementation)
Describe the post-implementation Change Management process Code Administration & Updates
Tyler will work with your project team to load any fixes, customizations, and code required during the project.

All of these items are accessed through Tyler Deploy. Tyler will train your resources on the use of this utility, will assist and guide as needed during the project. Any chances that occur in the proposed processing is discussed and tested by your personnel to ensure that a detailed knowledge transfer occurs.

Implementation Support
During implementation, Tyler’s project team will act as your primary support. Tyler’s client services teams are available to assist with any issues that arise but will typically be involved by the Tyler project team resources.

Go Live Support
Tyler’s project team resources will assist through the transition from implementation to live processing with Munis. Project team members will be on-site during the go live, as well as during identified critical process during the first 30 – 45 days of production. This is meant to ensure that your implementation is successful and is capable of conducting all aspects of business using Munis.

Support Account Management
Tyler believes that product support is a critical aspect of the work that we do, and we provide substantial resources, tools, and collaboration options for our clients. In addition to these options, we provide client direction during the important transition from implementation to go-live through the use of specialized Support Account Management (SAM). Our SAM process is designed to guide new clients during the first year of live processing in Munis. During the implementation process, each client develops a strong relationship with their assigned Munis implementation team. In order to facilitate the transition process to the Munis support team after go-live, Tyler developed our SAM team to help plan for key processes and build new relationships with the 100+ client services team members. SAM’s proactive team members work to aid new clients with:
x Understanding the support tools and processes
x Preparing for key processes (fiscal year end, budgeting, reconciliation, first upgrade) x Staying current with Munis releases and the life cycle of each version; enabling clients to take advantage of new functionality
x Utilizing custom modifications fully and to fulfill any unique business practices/goals post-live Each client is assigned a product SAM, who proactively works for the client on upcoming key processes, provides insight and advice for success.

Help Desk Strategy
Please refer to the client services section of this RFP for information on Tyler’s client services and post implementation tools available.

City of Yuba City Ongoing Maintenance and Support
ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 46

7.6 User Group/Conferences

7.6 – User Groups/Conferences
Identify any solution user groups and/or user conferences including frequency and location of events, topics, etc.

The Ongoing Maintenance and Support section should be no longer than ten (10) pages.

7.6.1 Local User Groups
Tyler clients benefit from networking and peer-to-peer collaboration through local user groups. The majority of user groups are run by clients, who set the meeting agenda, location and frequency, assign topics, and involve the Tyler resources they need. In large states, there may be several user groups or different sessions planned.

Tyler provides staff to demonstrate new functionality and assist with materials and collateral. During the sessions, Tyler representatives collect important feedback and report back to product managers. Many clients form lasting connections with other Tyler users within these groups and help to make each other better users of the software.

7.6.2 Annual User Conference
Each year Tyler hosts an annual user conference, which brings together staff and clients from across all Tyler products. Tyler has appropriately named our conference Connect, and each year thousands of clients come to learn about Tyler, our products, and to connect with peers and staff. This premier event helps clients get the maximum use of their Tyler software. Clients can learn more about existing or proposed functionality through dozens of classes over several days. Development product managers attend the event to share their plans for the next upgrade and to solicit feedback from clients.

Tyler was able to quickly pivot in the spring of 2020, with the global pandemic, to move all our classes virtually. As of this year, Tyler has over 4700 registrants and over 600 classes being offered on our virtual platform for our annual conference.

Our clients’ input from past conferences continues to significantly impact the direction of software enhancements and changes. Client attendance each year ensures that appropriate needs are reflected in product development strategies. Connect is held in different locations every year to accommodate our geographically diverse client base and to provide fresh and exciting activities for our clients outside of the classes and labs.

City of Yuba City Pricing
ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 47
Section 8 Pricing
Section 8 – Pricing
The City seeks a clear and comprehensive understanding of all costs associated with the implementation and ongoing maintenance of the proposed system.

To address pricing, the City will provide a copy of RFP Appendix B – Price Sheets - in MS Excel. To address this section, Proposers must complete all the price sheets in Appendix B.

Proposers must itemize all costs associated with the implementation and ongoing maintenance. The City will evaluate information based on the “Total Cost to Implement (TCI)” and the “Total Cost to Operate (TCO).” TCI will include all costs required for a successful implementation. The TCO will be calculated based on TCI plus five (5) years of annual hosting fees.

The Proposer’s implementation pricing must identify all costs required to include:

Implementation Services
Project management
Software configuration
Data conversion and migration
Interface development
Training and documentation
Testing
Go-Live
Travel
The Proposer’s ongoing hosting (SaaS) prices should clearly identify the annual costs for five (5) years to include:

Hosting
Post Implementation Evaluation Report (PIER) and associated training (one six months after the Financial implementation and one six months after the HR implementation) The City will evaluate Proposer price information based solely off the information provided in Appendix B. Appendix B includes space for Proposers to identify any assumptions or comments that will ensure the City understands what is being proposed.

NOTE: In their assumptions, Proposer’s must identify when the ongoing hosting costs are due and payable for their SaaS solutions.

8.1 Appendix B
Please reference the following pages.

Proprietary and Confidential - Subject to Restrictions on Disclosure Software Hosting Price Sheet Year 1 Year 2 Year 3 Year 4 Year 5
Accounting 34,812 $ 34,812 $ 34,812 $ 34,812 $ 34,812 $ Accounts Payable 10,392 $ 10,392 $ 10,392 $ 10,392 $ 10,392 $ Assets Mobile 3,075 $ 3,075 $ 3,075 $ 3,075 $ 3,075 $
Bid Management 4,488 $ 4,488 $ 4,488 $ 4,488 $ 4,488 $
Budgeting 10,392 $ 10,392 $ 10,392 $ 10,392 $ 10,392 $
Capital Assets 10,029 $ 10,029 $ 10,029 $ 10,029 $ 10,029 $ Cash Management 7,113 $ 7,113 $ 7,113 $ 7,113 $ 7,113 $ Contract Management 4,483 $ 4,483 $ 4,483 $ 4,483 $ 4,483 $ eProcurement (Vendor Access & Punch O 6,305 $ 6,305 $ 6,305 $ 6,305 $ 6,305 $ Project & Grant Accounting 7,504 $ 7,504 $ 7,504 $ 7,504 $ 7,504 $ Purchasing 17,105 $ 17,105 $ 17,105 $ 17,105 $ 17,105 $ Accounts Receivable 8,702 $ 8,702 $ 8,702 $ 8,702 $ 8,702 $ Cashiering 13,213 $ 13,213 $ 13,213 $ 13,213 $ 13,213 $ General Billing 4,909 $ 4,909 $ 4,909 $ 4,909 $ 4,909 $ ACFR Statement Builder 5,801 $ 5,801 $ 5,801 $ 5,801 $ 5,801 $ Subtotal - Finance Modules 148,323 $ 148,323 $ 148,323 $ 148,323 $ 148,323 $ Employee Expense Reimbursement 3,915 $ 3,915 $ 3,915 $ 3,915 $ 3,915 $ Human Resources & Talent Mgt. 6,175 $ 6,175 $ 6,175 $ 6,175 $ 6,175 $ Payroll with Employee Access 8,964 $ 8,964 $ 8,964 $ 8,964 $ 8,964 $ Recruiting 1,423 $ 1,423 $ 1,423 $ 1,423 $ 1,423 $
Time & Attendance w/Mobile Access 9,025 $ 9,025 $ 9,025 $ 9,025 $ 9,025 $ up to 350 employees - $ - $ - $ - $ - $
- $ - $ - $ - $ - $
- $ - $ - $ - $ - $
- $ - $ - $ - $ - $
- $ - $ - $ - $ - $
Subtotal - HR Modules 29,502 $ 29,502 $ 29,502 $ 29,502 $ 29,502 $ Content Manager Core incl. Onboarding 11,141 $ 11,141 $ 11,141 $ 11,141 $ 11,141 $ Enterprise Analytics & Reporting w/ Exec 17,928 $ 17,928 $ 17,928 $ 17,928 $ 17,928 $ Enterprise Forms Processing (incl. Comm 6,419 $ 6,419 $ 6,419 $ 6,419 $ 6,419 $ Hardware Annual Maintenance Fee 566 $ 566 $ 566 $ 566 $ 566 $ - $ - $ - $ - $ - $
- $ - $ - $ - $ - $
Subtotal - Other Modules 36,054 $ 36,054 $ 36,054 $ 36,054 $ 36,054 $ Annual Fee Discount (21,332) $ (21,332) $ (21,332) $ (21,332) $ (21,332) $ Total Application Hosting Fees 192,547 $ 192,547 $ 192,547 $ 192,547 $ 192,547 $ Proposer Name: Tyler Technologies
Other Modules (i.e. system tools, reporting, etc.)
Annual Hosting Fees
Vendor Notes and/or Assumptions Description
Financial ModulesHuman Resources (HR) Modules
Yuba City - ERP RFP - Appendix B - Price Sheets Page 1

Proprietary and Confidential - Subject to Restrictions on Disclosure Implementation Services Price Sheet Service Category Hours Rate Implementation Fee Notes / Assumptions Project Management - - $ 105,600 $ 25% Dedicated Project Management, 12 months for Financials with overlap for HCMConfiguration 456 - $ 94,050 $ blended rate calculated and inserted into Implementation FeeTesting 273 - $ 56,300 $ blended rate calculated and inserted into Implementation FeeTraining 912 - $ 188,100 $ blended rate calculated and inserted into Implementation FeeGo Live Support 183 - $ 37,750 $ blended rate calculated and inserted into Implementation FeeCustom Report Develoment -As Needed 40 200.00 $ 8,000 $ remote, as neeed, can be used for either phase (total 80 hours)PIER 60 225.00 $ 13,500 $ Post Go-Live Support 40 225.00 $ 9,000 $ Pcard Import Format - - $ 5,500 $ flat feeExecutive Insights Implementation - - $ 8,400 $ flat fee Subtotal - Finance Modules Implementation 1,964 526,200 $ Service Category Hours Rate Implementation Fee Notes / Assumptions Project Management - - $ 70,400 $ 25% Dedicated Project Management, overlap with Financials - 20 month total PM ServicesConfiguration 228 - $ 47,025 $ blended rate calculated and inserted into Implementation FeeTesting 136 - $ 28,050 $ blended rate calculated and inserted into Implementation FeeTraining 456 - $ 94,050 $ blended rate calculated and inserted into Implementation FeeGo Live Support 92 - $ 18,975 $ blended rate calculated and inserted into Implementation FeeCustom Report Development - As Needed 40 200.00 $ 8,000 $ remote, as neeed, can be used for either phase (total 80 hours)PIER 60 225.00 $ 13,500 $ Post Go-Live Support 40 225.00 $ 9,000 $ - - $ - $ Subtotal - HR Modules Implementation 1,052 289,000 $
Service Category Hours Rate Implementation Fee Notes / Assumptions Project Management - - $ - $ included aboveConfiguration 76 - $ 15,675 $ blended rate calculated and inserted into Implementation FeeTesting 45 - $ 9,275 $ blended rate calculated and inserted into Implementation FeeTraining 152 - $ 31,350 $ blended rate calculated and inserted into Implementation FeeGo Live Support 31 - $ 6,400 $ blended rate calculated and inserted into Implementation FeeOther (add as necessary) - - $ - $ - - $ - $
- - $ - $ - - $ - $
Subtotal - Other Modules Implementation 304 62,700 $ Total - All Implementation Services 3,320 877,900 $ Other Modules Implementation
Proposer Name:

Financial Modules Implementation
Human Resources (HR) Modules Implementation
Yuba City - ERP RFP - Appendix B - Price Sheets Page 2

Proprietary and Confidential - Subject to Restrictions on Disclosure Data Conversion Price Sheet Proposer Name:

Item Hours / Module Rate Conversion Fee Conversion Assumptions Capital Assets Import Hours 20 200.00 $ 4,000 $
COA Import Hours 12 200.00 $ 2,400 $
Payroll Accruals Import Hours 8 200.00 $ 1,400 $
Payroll Deductions Import Hours 12 200.00 $ 2,100 $ Position Control Import Hours 8 200.00 $ 1,400 $ Accounting Conversion - - $ 5,000 $ flat fee
Accounts Payable Conversion 10,300 $ flat feeContracts Conversion 5,000 $ flat feeProject Accounting 5,000 $ flat feePurchase Orders 6,000 $ flat fee Human Resources Management 14,300 $ flat feeGeneral Billing - - $ 9,800 $ flat fee - - $ - $
Total - Conversion 60 66,700 $
Data Conversion
Yuba City - ERP RFP - Appendix B - Price Sheets Page 3

Proprietary and Confidential - Subject to Restrictions on Disclosure 3rd Party Products Price Sheet Proposer Name:
3rd Party Product Description Cost Notes / Assumptions
Barcode Printer Kit 1,445 $ 1 quoted
Barcode Scanner - NX6 Rugged Mobile Scanning Device 1,695 $ 1 quotedCash Drawer 260 $ 1 quoted Hand Held Scanner - Model 1950GSR 450 $ 1 quotedHand Held Scanner Stand 30 $ 1 quoted Printer (TM-S900011) 1,623 $ 1 quotedTouchscreen 10: Barcode Reader 2,510 $ 1 quoted - $ maintenance for hardware can be found on Application annual costs - $ - $
Total - 3rd Party Products 8,013 $
Yuba City - ERP RFP - Appendix B - Price Sheets Page 4

Proprietary and Confidential - Subject to Restrictions on Disclosure Other/Optional Offerings Price Sheet Proposer Name:

Product/Solution Description Cost Notes / Assumptions
Recruiting - $ proposed within scope - detailed cost and hours can be found on investment summaryOnboarding - $ Other - $ - $ - $ - $ - $ - $ - $ - $
Total - Other or Optional Offerings - $
Yuba City - ERP RFP - Appendix B - Price Sheets Page 5

Proprietary and Confidential - Subject to Restrictions on Disclosure Travel Price Sheet (travel related to Implementation Services) Proposer Name:

Trip Descriptions # of Trips Cost Per Trip Total Notes / Assumptions Estimated Travel 32 1,500.00 $ 48,000 $ 32 on-site trips. - - $ - $
- - $ - $
- - $ - $
- - $ - $
- - $ - $
- - $ - $
- - $ - $
- - $ - $
Total Travel Expenses 32 48,000 $
Yuba City - ERP RFP - Appendix B - Price Sheets Page 6

Proprietary and Confidential - Subject to Restrictions on Disclosure Professional Services Rates Price Sheet [for any additional hours needed during implementation and or hosting (operations and maintenance)].

Resource Category Hourly Rate Notes / Assumptions
Project Manager - $ 25% dedicated PM services $8800/monthTrainer - $ $200 remote, $225 onsiteData Conversion Specialist - $ Conversions quoted as flat feeProgrammer 250.00 $ Business/Systems Analyst - $ $200 remote, $225 onsiteTesting Specialist - $ $200 remote, $225 onsiteOther (add as necessary) - $ - $ - $ - $ - $ Yuba City - ERP RFP - Appendix B - Price Sheets Page 7

City of Yuba City Pricing

ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 48

8.2 Tyler Investment Summary
Please reference the following pages.

City of Yuba City Software Licensing and Maintenance Agreements ERP System and Implementation Services Tyler Technologies, Inc.

RFP 23-03 Page 49
Section 9 Software Licensing and Maintenance
Agreements
Section 9 – Software Licensing and Maintenance Agreements To address this section, the Proposer must provide any software licensing and maintenance agreements that will be required to implement the Proposer’s solution.

9.1 Sample Contract
Please reference the following pages.

1 SOFTWARE AS A SERVICE AGREEMENT
This Software as a Service Agreement is made between Tyler Technologies, Inc. and Client.

WHEREAS, Client selected Tyler to provide certain products and services set forth in the Investment Summary, including providing Client with access to Tyler’s proprietary software products, and Tyler desires to provide such products and services under the terms of this Agreement; NOW THEREFORE, in consideration of the foregoing and of the mutual covenants and promises set forth in this Agreement, Tyler and Client agree as follows:

SECTION A – DEFINITIONS
 “Agreement” means this Software as a Service Agreement.  “Business Travel Policy” means our business travel policy. A copy of our current Business Travel Policy is attached as Schedule 1 to Exhibit B.
 “Client” means the INSERT CLIENT NAME.
 “Data” means your data necessary to utilize the Tyler Software.  “Data Storage Capacity” means the contracted amount of storage capacity for your Data identified in the Investment Summary.
 “Defect” means a failure of the Tyler Software to substantially conform to the functional descriptions set forth in our written proposal to you, or their functional equivalent. Future functionality may be updated, modified, or otherwise enhanced through our maintenance and support services, and the governing functional descriptions for such future functionality will be set forth in our then-current Documentation.
 “Defined Users” means the number of users that are authorized to use the SaaS Services. The Defined Users for the Agreement are as identified in the Investment Summary. If Exhibit A contains Enterprise Permitting & Licensing labeled software, defined users mean the maximum number of named users that are authorized to use the Enterprise Permitting & Licensing labeled modules as indicated in the Investment Summary.
 “Developer” means a third party who owns the intellectual property rights to Third Party Software.
 “Documentation” means any online or written documentation related to the use or functionality of the Tyler Software that we provide or otherwise make available to you, including instructions, user guides, manuals and other training or self-help documentation.  “Effective Date” means the date by which both your and our authorized representatives have signed the Agreement.
 “Force Majeure” means an event beyond the reasonable control of you or us, including, without limitation, governmental action, war, riot or civil commotion, fire, natural disaster, or any other cause that could not with reasonable diligence be foreseen or prevented by you or us.  “Investment Summary” means the agreed upon cost proposal for the products and services attached as Exhibit A.

2  “Invoicing and Payment Policy” means the invoicing and payment policy. A copy of our current Invoicing and Payment Policy is attached as Exhibit B.
 “Order Form” means an ordering document that includes a quote or investment summary and specifying the items to be provided by Tyler to Client, including any addenda and supplements thereto.
 “SaaS Fees” means the fees for the SaaS Services identified in the Investment Summary.  “SaaS Services” means software as a service consisting of system administration, system management, and system monitoring activities that Tyler performs for the Tyler Software, and includes the right to access and use the Tyler Software, receive maintenance and support on the Tyler Software, including Downtime resolution under the terms of the SLA, and Data storage and archiving. SaaS Services do not include support of an operating system or hardware, support outside of our normal business hours, or training, consulting or other professional services.  “SLA” means the service level agreement. A copy of our current SLA is attached hereto as Exhibit C.
 “Statement of Work” means the industry standard implementation plan describing how our professional services will be provided to implement the Tyler Software, and outlining your and our roles and responsibilities in connection with that implementation. The Statement of Work is attached as Exhibit E.
 “Support Call Process” means the support call process applicable to all of our customers who have licensed the Tyler Software. A copy of our current Support Call Process is attached as Schedule 1 to Exhibit C.
 “Third Party Hardware” means the third party hardware, if any, identified in the Investment Summary.
 “Third Party Products” means the Third Party Software and Third Party Hardware.  “Third Party SaaS Services” means software as a service provided by a third party, if any, identified in the Investment Summary.
 “Third Party Services” means the third party services, if any, identified in the Investment Summary.
 “Third Party Software” means the third party software, if any, identified in the Investment Summary.
 “Third Party Terms” means, if any, the end user license agreement(s) or similar terms for the Third Party Products or other parties’ products or services, as applicable, and attached or indicated at Exhibit D.
 “Tyler” means Tyler Technologies, Inc., a Delaware corporation.  “Tyler Software” means our proprietary software, including any integrations, custom modifications, and/or other related interfaces identified in the Investment Summary and licensed by us to you through this Agreement.
 “we”, “us”, “our” and similar terms mean Tyler.
 “you” and similar terms mean Client.

SECTION B – SAAS SERVICES

1. Rights Granted. We grant to you the non-exclusive, non-assignable limited right to use the SaaS Services solely for your internal business purposes for the number of Defined Users only. The Tyler Software will be made available to you according to the terms of the SLA. You acknowledge that we have no delivery obligations and we will not ship copies of the Tyler Software as part of the SaaS Services. You may use the SaaS Services to access updates and enhancements to the Tyler Software,

3 as further described in Section C(9). The foregoing notwithstanding, to the extent we have sold you perpetual licenses for Tyler Software, if and listed in the Investment Summary, for which you are receiving SaaS Services, your rights to use such Tyler Software are perpetual, subject to the terms and conditions of this Agreement including, without limitation, Section B(4). We will make any such software available to you for download.

2. SaaS Fees. You agree to pay us the SaaS Fees. Those amounts are payable in accordance with our Invoicing and Payment Policy. The SaaS Fees are based on the number of Defined Users and amount of Data Storage Capacity. You may add additional users or additional data storage capacity on the terms set forth in Section H(1). In the event you regularly and/or meaningfully exceed the Defined Users or Data Storage Capacity, we reserve the right to charge you additional fees commensurate with the overage(s).

3. Ownership.

3.1 We retain all ownership and intellectual property rights to the SaaS Services, the Tyler Software, and anything developed by us under this Agreement. You do not acquire under this Agreement any license to use the Tyler Software in excess of the scope and/or duration of the SaaS Services.

3.2 The Documentation is licensed to you and may be used and copied by your employees for internal, non-commercial reference purposes only.

3.3 You retain all ownership and intellectual property rights to the Data. You expressly recognize that except to the extent necessary to carry out our obligations contained in this Agreement, we do not create or endorse any Data used in connection with the SaaS Services.

4. Restrictions. You may not: (a) make the Tyler Software or Documentation resulting from the SaaS Services available in any manner to any third party for use in the third party’s business operations; (b) modify, make derivative works of, disassemble, reverse compile, or reverse engineer any part of the SaaS Services; (c) access or use the SaaS Services in order to build or support, and/or assist a third party in building or supporting, products or services competitive to us; or (d) license, sell, rent, lease, transfer, assign, distribute, display, host, outsource, disclose, permit timesharing or service bureau use, or otherwise commercially exploit or make the SaaS Services, Tyler Software, or Documentation available to any third party other than as expressly permitted by this Agreement.

5. Software Warranty. We warrant that the Tyler Software will perform without Defects during the term of this Agreement. If the Tyler Software does not perform as warranted, we will use all reasonable efforts, consistent with industry standards, to cure the Defect in accordance with the maintenance and support process set forth in Section C(9), below, the SLA and our then current Support Call Process.

6. SaaS Services.

6.1 Our SaaS Services are audited at least yearly in accordance with the AICPA’s Statement on Standards for Attestation Engagements (“SSAE”) No. 21. We have attained, and will maintain, SOC 1 and SOC 2 compliance, or its equivalent, for so long as you are timely paying for SaaS Services. The scope of audit coverage varies for some Tyler Software solutions. Upon execution of a mutually agreeable Non-Disclosure Agreement (“NDA”), we will provide you with a

4 summary of our compliance report(s) or its equivalent. Every year thereafter, for so long as the NDA is in effect and in which you make a written request, we will provide that same information. If our SaaS Services are provided using a 3rd party data center, we will provide available compliance reports for that data center.

6.2 You will be hosted on shared hardware in a Tyler data center or in a third-party data center. In either event, databases containing your Data will be dedicated to you and inaccessible to our other customers.

6.3 Our Tyler data centers have fully-redundant telecommunications access, electrical power, and the required hardware to provide access to the Tyler Software in the event of a disaster or component failure. In the event of a data center failure, we reserve the right to employ our disaster recovery plan for resumption of the SaaS Services. In that event, we commit to a Recovery Point Objective (“RPO”) of 24 hours and a Recovery Time Objective (“RTO”) of 24 hours. RPO represents the maximum duration of time between the most recent recoverable copy of your hosted Data and subsequent data center failure. RTO represents the maximum duration of time following data center failure within which your access to the Tyler Software must be restored.

6.4 We conduct annual penetration testing of either the production network and/or web application to be performed. We will maintain industry standard intrusion detection and prevention systems to monitor malicious activity in the network and to log and block any such activity. We will provide you with a written or electronic record of the actions taken by us in the event that any unauthorized access to your database(s) is detected as a result of our security protocols. We will undertake an additional security audit, on terms and timing to be mutually agreed to by the parties, at your written request. You may not attempt to bypass or subvert security restrictions in the SaaS Services or environments related to the Tyler Software.

Unauthorized attempts to access files, passwords or other confidential information, and unauthorized vulnerability and penetration test scanning of our network and systems (hosted or otherwise) is prohibited without the prior written approval of our IT Security Officer.

6.5 We test our disaster recovery plan on an annual basis. Our standard test is not client-specific.

Should you request a client-specific disaster recovery test, we will work with you to schedule and execute such a test on a mutually agreeable schedule. At your written request, we will provide test results to you within a commercially reasonable timeframe after receipt of the request.

6.6 We will be responsible for importing back-up and verifying that you can log-in. You will be responsible for running reports and testing critical processes to verify the returned Data.

6.7 We provide secure Data transmission paths between each of your workstations and our servers.

6.8 Tyler data centers are accessible only by authorized personnel with a unique key entry. All other visitors to Tyler data centers must be signed in and accompanied by authorized personnel.

Entry attempts to the data center are regularly audited by internal staff and external auditors to ensure no unauthorized access.

6.9 Where applicable with respect to our applications that take or process card payment data, we

5 are responsible for the security of cardholder data that we possess, including functions relating to storing, processing, and transmitting of the cardholder data and affirm that, as of the Effective Date, we comply with applicable requirements to be considered PCI DSS compliant and have performed the necessary steps to validate compliance with the PCI DSS. We agree to supply the current status of our PCI DSS compliance program in the form of an official Attestation of Compliance, which can be found at https://www.tylertech.com/aboutus/compliance, and in the event of any change in our status, will comply with applicable notice requirements.

SECTION C – PROFESSIONAL SERVICES

1. Professional Services. We will provide you the various implementation-related services itemized in the Investment Summary and described in the Statement of Work.

2. Professional Services Fees. You agree to pay us the professional services fees in the amounts set forth in the Investment Summary. Those amounts are payable in accordance with our Invoicing and Payment Policy. You acknowledge that the fees stated in the Investment Summary are good-faith estimates of the amount of time and materials required for your implementation. We will bill you the actual fees incurred based on the in-scope services provided to you. Any discrepancies in the total values set forth in the Investment Summary will be resolved by multiplying the applicable hourly rate by the quoted hours.

3. Additional Services. The Investment Summary contains, and the Statement of Work describes, the scope of services and related costs (including programming and/or interface estimates) required for the project based on our understanding of the specifications you supplied. If additional work is required, or if you use or request additional services, we will provide you with an addendum or change order, as applicable, outlining the costs for the additional work. The price quotes in the addendum or change order will be valid for thirty (30) days from the date of the quote.

4. Cancellation. If you cancel services less than four (4) weeks in advance (other than for Force Majeure or breach by us), you will be liable for all (a) daily fees associated with cancelled professional services if we are unable to reassign our personnel and (b) any non-refundable travel expenses already incurred by us on your behalf. We will make all reasonable efforts to reassign personnel in the event you cancel within four (4) weeks of scheduled commitments.

5. Services Warranty. We will perform the services in a professional, workmanlike manner, consistent with industry standards. In the event we provide services that do not conform to this warranty, we will re-perform such services at no additional cost to you.

6. Site Access and Requirements. At no cost to us, you agree to provide us with full and free access to your personnel, facilities, and equipment as may be reasonably necessary for us to provide implementation services, subject to any reasonable security protocols or other written policies provided to us as of the Effective Date, and thereafter as mutually agreed to by you and us.

7. Background Checks. For at least the past twelve (12) years, all of our employees have undergone criminal background checks prior to hire. All employees sign our confidentiality agreement and security policies.

6 8. Client Assistance. You acknowledge that the implementation of the Tyler Software is a cooperative process requiring the time and resources of your personnel. You agree to use all reasonable efforts to cooperate with and assist us as may be reasonably required to meet the agreed upon project deadlines and other milestones for implementation. This cooperation includes at least working with us to schedule the implementation-related services outlined in this Agreement. We will not be liable for failure to meet any deadlines and milestones when such failure is due to Force Majeure or to the failure by your personnel to provide such cooperation and assistance (either through action or omission).

9. Maintenance and Support. For so long as you timely pay your SaaS Fees according to the Invoicing and Payment Policy, then in addition to the terms set forth in the SLA and the Support Call Process, we will:

9.1 perform our maintenance and support obligations in a professional, good, and workmanlike manner, consistent with industry standards, to resolve Defects in the Tyler Software (subject to any applicable release life cycle policy);

9.2 provide support during our established support hours;

9.3 maintain personnel that are sufficiently trained to be familiar with the Tyler Software and Third Party Software, if any, in order to provide maintenance and support services;

9.4 make available to you all releases to the Tyler Software (including updates and enhancements) that we make generally available without additional charge to customers who have a maintenance and support agreement in effect; and

9.5 provide non-Defect resolution support of prior releases of the Tyler Software in accordance with any applicable release life cycle policy.

We will use all reasonable efforts to perform support services remotely. Currently, we use a third-party secure unattended connectivity tool called Bomgar, as well as GotoAssist by Citrix. Therefore, you agree to maintain a high-speed internet connection capable of connecting us to your PCs and server(s). You agree to provide us with a login account and local administrative privileges as we may reasonably require to perform remote services. We will, at our option, use the secure connection to assist with proper diagnosis and resolution, subject to any reasonably applicable security protocols. If we cannot resolve a support issue remotely, we may be required to provide onsite services. In such event, we will be responsible for our travel expenses, unless it is determined that the reason onsite support was required was a reason outside our control. Either way, you agree to provide us with full and free access to the Tyler Software, working space, adequate facilities within a reasonable distance from the equipment, and use of machines, attachments, features, or other equipment reasonably necessary for us to provide the maintenance and support services, all at no charge to us. We strongly recommend that you also maintain your VPN for backup connectivity purposes.

For the avoidance of doubt, SaaS Fees do not include the following services: (a) onsite support (unless Tyler cannot remotely correct a Defect in the Tyler Software, as set forth above); (b) application design; (c) other consulting services; or (d) support outside our normal business hours as listed in our thencurrent Support Call Process. Requested services such as those outlined in this section will be billed to you on a time and materials basis at our then current rates. You must request those services with at

7 least one (1) weeks’ advance notice.

SECTION D – THIRD PARTY PRODUCTS

1. Third Party Hardware. We will sell, deliver, and install onsite the Third Party Hardware, if you have purchased any, for the price set forth in the Investment Summary. Those amounts are payable in accordance with our Invoicing and Payment Policy.

2. Third Party Software. As part of the SaaS Services, you will receive access to the Third Party Software and related documentation for internal business purposes only. Your rights to the Third Party Software will be governed by the Third Party Terms.

3. Third Party Products Warranties.

3.1 We are authorized by each Developer to grant access to the Third Party Software.

3.2 The Third Party Hardware will be new and unused, and upon payment in full, you will receive free and clear title to the Third Party Hardware.

3.3 You acknowledge that we are not the manufacturer of the Third Party Products. We do not warrant or guarantee the performance of the Third Party Products. However, we grant and pass through to you any warranty that we may receive from the Developer or supplier of the Third Party Products.

4. Third Party Services. If you have purchased Third Party Services, those services will be provided independent of Tyler by such third-party at the rates set forth in the Investment Summary and in accordance with our Invoicing and Payment Policy.

SECTION E - INVOICING AND PAYMENT; INVOICE DISPUTES

1. Invoicing and Payment. We will invoice you the SaaS Fees and fees for other professional services in the Investment Summary per our Invoicing and Payment Policy, subject to Section E(2).

2. Invoice Disputes. If you believe any delivered software or service does not conform to the warranties in this Agreement, you will provide us with written notice within thirty (30) days of your receipt of the applicable invoice. The written notice must contain reasonable detail of the issues you contend are in dispute so that we can confirm the issue and respond to your notice with either a justification of the invoice, an adjustment to the invoice, or a proposal addressing the issues presented in your notice. We will work with you as may be necessary to develop an action plan that outlines reasonable steps to be taken by each of us to resolve any issues presented in your notice.

You may withhold payment of the amount(s) actually in dispute, and only those amounts, until we complete the action items outlined in the plan. If we are unable to complete the action items outlined in the action plan because of your failure to complete the items agreed to be done by you, then you will remit full payment of the invoice. We reserve the right to suspend delivery of all SaaS Services, including maintenance and support services, if you fail to pay an invoice not disputed as described above within fifteen (15) days of notice of our intent to do so.

SECTION F – TERM AND TERMINATION

8 1. Term. The initial term of this Agreement is equal to the number of years indicated for SaaS Services in Exhibit A, commencing on the first day of the first month following the Effective Date, unless earlier terminated as set forth below. If no duration is indicated in Exhibit A, the initial term is one (1) year. Upon expiration of the initial term, this Agreement will renew automatically for additional one (1) year renewal terms at our then-current SaaS Fees unless terminated in writing by either party at least sixty (60) days prior to the end of the then-current renewal term. Your right to access or use the Tyler Software and the SaaS Services will terminate at the end of this Agreement.

2. Termination. This Agreement may be terminated as set forth below. In the event of termination, you will pay us for all undisputed fees and expenses related to the software, products, and/or services you have received, or we have incurred or delivered, prior to the effective date of termination. Disputed fees and expenses in all terminations other than your termination for cause must have been submitted as invoice disputes in accordance with Section E(2).

2.1 Failure to Pay SaaS Fees. You acknowledge that continued access to the SaaS Services is contingent upon your timely payment of SaaS Fees. If you fail to timely pay the SaaS Fees, we may discontinue the SaaS Services and deny your access to the Tyler Software. We may also terminate this Agreement if you don’t cure such failure to pay within forty-five (45) days of receiving written notice of our intent to terminate.

2.2 For Cause. If you believe we have materially breached this Agreement, you will invoke the Dispute Resolution clause set forth in Section H(3). You may terminate this Agreement for cause in the event we do not cure, or create a mutually agreeable action plan to address, a material breach of this Agreement within the thirty (30) day window set forth in Section H(3).

2.3 Force Majeure. Either party has the right to terminate this Agreement if a Force Majeure event suspends performance of the SaaS Services for a period of forty-five (45) days or more.

2.4 Lack of Appropriations. If you should not appropriate or otherwise make available funds sufficient to utilize the SaaS Services, you may unilaterally terminate this Agreement upon thirty (30) days written notice to us. You will not be entitled to a refund or offset of previously paid, but unused SaaS Fees. You agree not to use termination for lack of appropriations as a substitute for termination for convenience.

SECTION G – INDEMNIFICATION, LIMITATION OF LIABILITY AND INSURANCE

1. Intellectual Property Infringement Indemnification.

1.1 We will defend you against any third party claim(s) that the Tyler Software or Documentation infringes that third party’s patent, copyright, or trademark, or misappropriates its trade secrets, and will pay the amount of any resulting adverse final judgment (or settlement to which we consent). You must notify us promptly in writing of the claim and give us sole control over its defense or settlement. You agree to provide us with reasonable assistance, cooperation, and information in defending the claim at our expense.

1.2 Our obligations under this Section G(1) will not apply to the extent the claim or adverse final judgment is based on your use of the Tyler Software in contradiction of this Agreement,

9 including with non-licensed third parties, or your willful infringement.

1.3 If we receive information concerning an infringement or misappropriation claim related to the Tyler Software, we may, at our expense and without obligation to do so, either: (a) procure for you the right to continue its use; (b) modify it to make it non-infringing; or (c) replace it with a functional equivalent, in which case you will stop running the allegedly infringing Tyler Software immediately. Alternatively, we may decide to litigate the claim to judgment, in which case you may continue to use the Tyler Software consistent with the terms of this Agreement.

1.4 If an infringement or misappropriation claim is fully litigated and your use of the Tyler Software is enjoined by a court of competent jurisdiction, in addition to paying any adverse final judgment (or settlement to which we consent), we will, at our option, either: (a) procure the right to continue its use; (b) modify it to make it non-infringing; or (c) replace it with a functional equivalent. This section provides your exclusive remedy for third party copyright, patent, or trademark infringement and trade secret misappropriation claims.

2. General Indemnification.

2.1 We will indemnify and hold harmless you and your agents, officials, and employees from and against any and all third-party claims, losses, liabilities, damages, costs, and expenses (including reasonable attorney's fees and costs) for (a) personal injury or property damage to the extent caused by our negligence or willful misconduct; or (b) our violation of PCI-DSS requirements or a law applicable to our performance under this Agreement. You must notify us promptly in writing of the claim and give us sole control over its defense or settlement. You agree to provide us with reasonable assistance, cooperation, and information in defending the claim at our expense.

2.2 To the extent permitted by applicable law, you will indemnify and hold harmless us and our agents, officials, and employees from and against any and all third-party claims, losses, liabilities, damages, costs, and expenses (including reasonable attorney's fees and costs) for (a) personal injury or property damage to the extent caused by your negligence or willful misconduct; or (b) your violation of a law applicable to your performance under this Agreement.

We will notify you promptly in writing of the claim and will give you sole control over its defense or settlement. We agree to provide you with reasonable assistance, cooperation, and information in defending the claim at your expense.

3. DISCLAIMER. EXCEPT FOR THE EXPRESS WARRANTIES PROVIDED IN THIS AGREEMENT AND TO

THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, WE HEREBY DISCLAIM ALL OTHER

WARRANTIES AND CONDITIONS, WHETHER EXPRESS, IMPLIED, OR STATUTORY, INCLUDING, BUT

NOT LIMITED TO, ANY IMPLIED WARRANTIES, DUTIES, OR CONDITIONS OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. CLIENT UNDERSTANDS AND AGREES THAT TYLER DISCLAIMS ANY LIABILITY FOR ERRORS THAT RELATE TO USER ERROR.

4. LIMITATION OF LIABILITY. EXCEPT AS OTHERWISE EXPRESSLY SET FORTH IN THIS AGREEMENT,

OUR LIABILITY FOR DAMAGES ARISING OUT OF THIS AGREEMENT, WHETHER BASED ON A THEORY

OF CONTRACT OR TORT, INCLUDING NEGLIGENCE AND STRICT LIABILITY, SHALL BE LIMITED TO

YOUR ACTUAL DIRECT DAMAGES, NOT TO EXCEED (A) DURING THE INITIAL TERM, AS SET FORTH IN SECTION F(1), TOTAL FEES PAID AS OF THE TIME OF THE CLAIM; OR (B) DURING ANY RENEWAL

10 TERM, THE THEN-CURRENT ANNUAL SAAS FEES PAYABLE IN THAT RENEWAL TERM. THE PARTIES

ACKNOWLEDGE AND AGREE THAT THE PRICES SET FORTH IN THIS AGREEMENT ARE SET IN

RELIANCE UPON THIS LIMITATION OF LIABILITY AND TO THE MAXIMUM EXTENT ALLOWED UNDER

APPLICABLE LAW, THE EXCLUSION OF CERTAIN DAMAGES, AND EACH SHALL APPLY REGARDLESS OF THE FAILURE OF AN ESSENTIAL PURPOSE OF ANY REMEDY. THE FOREGOING LIMITATION OF LIABILITY SHALL NOT APPLY TO CLAIMS THAT ARE SUBJECT TO SECTIONS G(1) AND G(2).

5. EXCLUSION OF CERTAIN DAMAGES. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW,

IN NO EVENT SHALL WE BE LIABLE FOR ANY SPECIAL, INCIDENTAL, PUNITIVE, INDIRECT, OR

CONSEQUENTIAL DAMAGES WHATSOEVER, EVEN IF WE HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

6. Insurance. During the course of performing services under this Agreement, we agree to maintain the following levels of insurance: (a) Commercial General Liability of at least $1,000,000; (b) Automobile Liability of at least $1,000,000; (c) Professional Liability of at least $1,000,000; (d) Workers Compensation complying with applicable statutory requirements; and (e) Excess/Umbrella Liability of at least $5,000,000. We will add you as an additional insured to our Commercial General Liability and Automobile Liability policies, which will automatically add you as an additional insured to our Excess/Umbrella Liability policy as well. We will provide you with copies of certificates of insurance upon your written request.

SECTION H – GENERAL TERMS AND CONDITIONS

1. Additional Products and Services. You may purchase additional products and services at the rates set forth in the Investment Summary for twelve (12) months from the Effective Date by executing a mutually agreed addendum. If no rate is provided in the Investment Summary, or those twelve (12) months have expired, you may purchase additional products and services at our then-current list price, also by executing a mutually agreed addendum. The terms of this Agreement will control any such additional purchase(s), unless otherwise specifically provided in the addendum.

2. Optional Items. Pricing for any listed optional products and services in the Investment Summary will be valid for twelve (12) months from the Effective Date.

3. Dispute Resolution. You agree to provide us with written notice within thirty (30) days of becoming aware of a dispute. You agree to cooperate with us in trying to reasonably resolve all disputes, including, if requested by either party, appointing a senior representative to meet and engage in good faith negotiations with our appointed senior representative. Senior representatives will convene within thirty (30) days of the written dispute notice, unless otherwise agreed. All meetings and discussions between senior representatives will be deemed confidential settlement discussions not subject to disclosure under Federal Rule of Evidence 408 or any similar applicable state rule. If we fail to resolve the dispute, then the parties shall participate in non-binding mediation in an effort to resolve the dispute. If the dispute remains unresolved after mediation, then either of us may assert our respective rights and remedies in a court of competent jurisdiction. Nothing in this section shall prevent you or us from seeking necessary injunctive relief during the dispute resolution procedures.

4. Taxes. The fees in the Investment Summary do not include any taxes, including, without limitation, sales, use, or excise tax. If you are a tax-exempt entity, you agree to provide us with a tax-exempt

11 certificate. Otherwise, we will pay all applicable taxes to the proper authorities and you will reimburse us for such taxes. If you have a valid direct-pay permit, you agree to provide us with a copy. For clarity, we are responsible for paying our income taxes, both federal and state, as applicable, arising from our performance of this Agreement.

5. Nondiscrimination. We will not discriminate against any person employed or applying for employment concerning the performance of our responsibilities under this Agreement. This discrimination prohibition will apply to all matters of initial employment, tenure, and terms of employment, or otherwise with respect to any matter directly or indirectly relating to employment concerning race, color, religion, national origin, age, sex, sexual orientation, ancestry, disability that is unrelated to the individual's ability to perform the duties of a particular job or position, height, weight, marital status, or political affiliation. We will post, where appropriate, all notices related to nondiscrimination as may be required by applicable law.

6. E-Verify. We have complied, and will comply, with the E-Verify procedures administered by the U.S.

Citizenship and Immigration Services Verification Division for all of our employees assigned to your project.

7. Subcontractors. We will not subcontract any services under this Agreement without your prior written consent, not to be unreasonably withheld.

8. Binding Effect; No Assignment. This Agreement shall be binding on, and shall be for the benefit of, either your or our successor(s) or permitted assign(s). Neither party may assign this Agreement without the prior written consent of the other party; provided, however, your consent is not required for an assignment by us as a result of a corporate reorganization, merger, acquisition, or purchase of substantially all of our assets.

9. Force Majeure. Except for your payment obligations, neither party will be liable for delays in performing its obligations under this Agreement to the extent that the delay is caused by Force Majeure; provided, however, that within ten (10) business days of the Force Majeure event, the party whose performance is delayed provides the other party with written notice explaining the cause and extent thereof, as well as a request for a reasonable time extension equal to the estimated duration of the Force Majeure event.

10. No Intended Third Party Beneficiaries. This Agreement is entered into solely for the benefit of you and us. No third party will be deemed a beneficiary of this Agreement, and no third party will have the right to make any claim or assert any right under this Agreement. This provision does not affect the rights of third parties under any Third Party Terms.

11. Entire Agreement; Amendment. This Agreement represents the entire agreement between you and us with respect to the subject matter hereof, and supersedes any prior agreements, understandings, and representations, whether written, oral, expressed, implied, or statutory. Purchase orders submitted by you, if any, are for your internal administrative purposes only, and the terms and conditions contained in those purchase orders will have no force or effect. This Agreement may only be modified by a written amendment signed by an authorized representative of each party.

12. Severability. If any term or provision of this Agreement is held invalid or unenforceable, the remainder of this Agreement will be considered valid and enforceable to the fullest extent

12 permitted by law.

13. No Waiver. In the event that the terms and conditions of this Agreement are not strictly enforced by either party, such non-enforcement will not act as or be deemed to act as a waiver or modification of this Agreement, nor will such non-enforcement prevent such party from enforcing each and every term of this Agreement thereafter.

14. Independent Contractor. We are an independent contractor for all purposes under this Agreement.

15. Notices. All notices or communications required or permitted as a part of this Agreement, such as notice of an alleged material breach for a termination for cause or a dispute that must be submitted to dispute resolution, must be in writing and will be deemed delivered upon the earlier of the following: (a) actual receipt by the receiving party; (b) upon receipt by sender of a certified mail, return receipt signed by an employee or agent of the receiving party; (c) upon receipt by sender of proof of email delivery; or (d) if not actually received, five (5) days after deposit with the United States Postal Service authorized mail center with proper postage (certified mail, return receipt requested) affixed and addressed to the other party at the address set forth on the signature page hereto or such other address as the party may have designated by proper notice. The consequences for the failure to receive a notice due to improper notification by the intended receiving party of a change in address will be borne by the intended receiving party.

16. Client Lists. You agree that we may identify you by name in client lists, marketing presentations, and promotional materials.

17. Confidentiality. Both parties recognize that their respective employees and agents, in the course of performance of this Agreement, may be exposed to confidential information and that disclosure of such information could violate rights to private individuals and entities, including the parties.

Confidential information is nonpublic information that a reasonable person would believe to be confidential and includes, without limitation, personal identifying information (e.g., social security numbers) and trade secrets, each as defined by applicable state law. Each party agrees that it will not disclose any confidential information of the other party and further agrees to take all reasonable and appropriate action to prevent such disclosure by its employees or agents. The confidentiality covenants contained herein will survive the termination or cancellation of this Agreement. This obligation of confidentiality will not apply to information that:
(a) is in the public domain, either at the time of disclosure or afterwards, except by breach of this Agreement by a party or its employees or agents;
(b) a party can establish by reasonable proof was in that party's possession at the time of initial disclosure;
(c) a party receives from a third party who has a right to disclose it to the receiving party; or (d) is the subject of a legitimate disclosure request under the open records laws or similar applicable public disclosure laws governing this Agreement; provided, however, that in the event you receive an open records or other similar applicable request, you will give us prompt notice and otherwise perform the functions required by applicable law.

18. Quarantining of Client Data. Some services provided by Tyler require us to be in possession of your Data. In the event we detect malware or other conditions associated with your Data that are reasonably suspected of putting Tyler resources or other Tyler clients’ data at risk, we reserve the absolute right to move your Data from its location within a multi-tenancy Tyler hosted environment

13 to an isolated “quarantined” environment without advance notice. Your Data will remain in such quarantine for a period of at least six (6) months during which time we will review the Data, and all traffic associated with the Data, for signs of malware or other similar issues. If no issues are detected through such reviews during the six (6) month period of quarantine, we will coordinate with you the restoration of your Data to a non-quarantined environment. In the event your Data must remain in quarantine beyond this six (6) month period through no fault of Tyler’s, we reserve the right to require payment of additional fees for the extended duration of quarantine. We will provide an estimate of what those costs will be upon your request.

19. Business License. In the event a local business license is required for us to perform services hereunder, you will promptly notify us and provide us with the necessary paperwork and/or contact information so that we may timely obtain such license.

20. Governing Law. This Agreement will be governed by and construed in accordance with the laws of your state of domicile, without regard to its rules on conflicts of law.

21. Multiple Originals and Authorized Signatures. This Agreement may be executed in multiple originals, any of which will be independently treated as an original document. Any electronic, faxed, scanned, photocopied, or similarly reproduced signature on this Agreement or any amendment hereto will be deemed an original signature and will be fully enforceable as if an original signature.

Each party represents to the other that the signatory set forth below is duly authorized to bind that party to this Agreement.

22. Cooperative Procurement. To the maximum extent permitted by applicable law, we agree that this Agreement may be used as a cooperative procurement vehicle by eligible jurisdictions. We reserve the right to negotiate and customize the terms and conditions set forth herein, including but not limited to pricing, to the scope and circumstances of that cooperative procurement.

23. Data & Insights Solution Terms. Your use of certain Tyler solutions includes Tyler’s Data & Insights data platform. Your rights, and the rights of any of your end users, to use Tyler’s Data & Insights data platform is subject to the Data & Insights SaaS Services Terms of Service, available at https://www.tylertech.com/terms/data-insights-saas-services-terms-of-service. By signing a Tyler Agreement or Order Form, or accessing, installing, or using any of the Tyler solutions listed at the linked terms, you certify that you have reviewed, understand, and agree to said terms.

24. Contract Documents. This Agreement includes the following exhibits:

Exhibit A Investment Summary
Exhibit B Invoicing and Payment Policy
Schedule 1: Business Travel Policy
Exhibit C Service Level Agreement
Schedule 1: Support Call Process
Exhibit D Third Party Terms
Exhibit E Statement of Work

14 IN WITNESS WHEREOF, a duly authorized representative of each party has executed this Agreement as of the date(s) set forth below.

Tyler Technologies, Inc. INSERT CLIENT NAME
By: By:

Name: Name:

Title: Title:

Date: Date:

Address for Notices: Address for Notices:

Tyler Technologies, Inc. INSERT CLIENT NAME
One Tyler Drive CLIENT ADDRESS
Yarmouth, ME 04096 CLIENT ADDRESS
Attention: Chief Legal Officer Attention: ______________________________

Exhibit A

1 Exhibit A
Investment Summary
The following Investment Summary details the software and services to be delivered by us to you under the Agreement. This Investment Summary is effective as of the Effective Date, despite any expiration date in the Investment Summary that may have lapsed as of the Effective Date.

Tyler sales quotation to be inserted prior to Agreement execution.

REMAINDER OF PAGE INTENTIONALLY LEFT BLANK

Exhibit B

1 Exhibit B
Invoicing and Payment Policy
We will provide you with the software and services set forth in the Investment Summary of the Agreement. Capitalized terms not otherwise defined will have the meaning assigned to such terms in the Agreement.

Invoicing: We will invoice you for the applicable software and services in the Investment Summary as set forth below. Your rights to dispute any invoice are set forth in the Agreement.

1. SaaS Fees. SaaS Fees are invoiced on an annual basis, beginning on the commencement of the initial term as set forth in Section F (1) of this Agreement. Your annual SaaS fees for the initial term are set forth in the Investment Summary. Upon expiration of the initial term, your annual SaaS fees will be at our then-current rates.

2. Other Tyler Software and Services.

2.1 Implementation and Other Professional Services (including training): Implementation and other professional services (including training) are billed and invoiced as delivered, at the rates set forth in the Investment Summary.

2.2 Consulting Services: If you have purchased any Business Process Consulting services, if they have been quoted as fixed-fee services, they will be invoiced 50% upon your acceptance of the Best Practice Recommendations, by module, and 50% upon your acceptance of custom desktop procedures, by module. If you have purchased any Business Process Consulting services and they are quoted as an estimate, then we will bill you the actual services delivered on a time and materials basis.

2.3 Conversions: Fixed-fee conversions are invoiced 50% upon initial delivery of the converted Data, by conversion option, and 50% upon Client acceptance to load the converted Data into Live/Production environment, by conversion option. Where conversions are quoted as estimated, we will bill you the actual services delivered on a time and materials basis.

2.4 Requested Modifications to the Tyler Software: Requested modifications to the Tyler Software are invoiced 50% upon delivery of specifications and 50% upon delivery of the applicable modification. You must report any failure of the modification to conform to the specifications within thirty (30) days of delivery; otherwise, the modification will be deemed to be in compliance with the specifications after the 30-day window has passed. You may still report Defects to us as set forth in this Agreement.

2.5 Other Fixed Price Services: Other fixed price services are invoiced as delivered, at the rates set forth in the Investment Summary. For the avoidance of doubt, where “Project Planning Services” are provided, payment will be due upon delivery of the Implementation Planning document. Dedicated Project Management services, if any, will be billed monthly in arrears, beginning on the first day of the month immediately following initiation of project planning.

2.6 Web Services: Annual fees for web services are payable in advance, commencing upon the availability of the service. Your annual fees for the initial term are set forth in the