Loading...
HomeMy WebLinkAbout2020-150-E IT - Tyler Technologies EnerGov contract amendment DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 tyler•••..• • technologies LICENSE AND SERVICES AGREEMENT This License and Services Agreement is made between Tyler Technologies, Inc. and Client. WHEREAS, Client selected Tyler to license the software products and perform the services set forth in the Investment Summary and Tyler desires to perform such actions 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 License and Services Agreement, including the Exhibits and Schedules thereto, and as further defined in Section 1(11). • '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 Orange County, North Carolina, a body politic and corporate of the State of North Carolina. • "Defect" means a failure of the Tyler Software to substantially conform to the Functional Requirements or their functional equivalent. Any functional equivalent to cure a defect will be mutually agreeable to both parties and will be substantially similar in how it conforms to the original Functional Requirement. 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. A"Defect" does not include a lack of functionality in the Tyler Software identified solely as a result of a change in your Internal Business Purposes. • "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 on which your authorized representative signs 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. • "Functional Requirements" refer to our affirmative responses to the functional requirements described in your RFP and set forth in our Proposal,which responses are incorporated herein by reference. For the avoidance of doubt, an "affirmative response" means that we indicated the functionality exists as a standard feature within the Tyler Software, or could be made available to you as a custom modifications. Functional Requirements that are associated with a custom modification are only in-scope to the extent you have purchased the development services to deliver the custom modification. • "Internal Business Purposes" means those administrative and operational functions you perform in DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 the ordinary course of your business.This shall be understood to include the shared services land management and development functions performed by inter-governmental agencies and municipal users who, in the normal course of their business, have the need to access and/or review the land management records you generate, or that originate with you, or who desire to generate land management records unique to that agency or municipality within the licensed instance of the Tyler Software, and subject to the limitations set forth in this Agreement. • "Investment Summary" means the agreed upon cost proposal for the software, products, and services attached as Exhibit A. • "Invoicing and Payment Policy" means the invoicing and payment policy attached as Exhibit B. • "Maintenance and Support Agreement" means the terms and conditions governing the provision of maintenance and support services attached as Exhibit C. • "Proposal" means our written response to your RFP, including the written clarifications submitted post-Proposal (EnerGov Part 1 Responses to Cost and SOW Post Demo Follow-Up, EnerGov Part 2 Functionality Post Demo Follow-Up, EnerGov Cost Proposal Clarifications, and EnerGov Technical and GIS Clarification Follow-Up) as well as Appendix A—Final with OC comments re: non-compliance issues. • "Request for Proposal" or"RFP" means the procurement documentation you issued for the software and services that are the subject of this Agreement, identified as RFP#5202 and subsequent amendments. • "Statement of Work" means the document, set forth at Exhibit D, setting forth the terms and conditions under which Tyler will deliver the in-scope professional services to implement the Tyler Software. • "Support Call Process" means the support call process attached as Schedule 1 to Exhibit C. • "Tyler" means Tyler Technologies, Inc., a Delaware corporation. • "Tyler Software" means our proprietary software and related interfaces identified in the Investment Summary and licensed to you through this Agreement. • "we", "us", "our" and similar terms mean Tyler. • "you"and similar terms mean Client. SECTION B—SOFTWARE LICENSE 1. License Grant and Restrictions. 1.1 We grant to you a license to use the Tyler Software for your Internal Business Purposes only. You may make copies of the Tyler Software for backup and testing purposes, so long as such copies are not used in production and the testing is for internal use only. Upon payment in full under Section B(2),your rights to use the Tyler Software are perpetual but may be revoked if you do not comply with the terms of this Section B(1). 1.2 You understand the scope of your license is limited to the number of licenses set forth in the Investment Summary. Therefore,you agree that any inter-governmental agency or municipal user, within the scope of your Internal Business Purposes, must be allocated one of the named user licenses set forth in the Investment Summary, or you must acquire additional named user licenses for those users on the terms and conditions set forth in this Agreement. You further understand and agree that you are responsible for those users' compliance with the terms and conditions of this Section B, as if those users were your employees or agents, and any breach of those terms and conditions will be ••-o . tyler 2 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 considered a breach by you. 1.3 The Documentation is licensed to you and may be used and copied by your employees for internal, non-commercial reference purposes only, except where disclosure is required in accordance with Section 1(17). 1.4 You may not: (a)transfer or assign the Tyler Software to a third party; (b) reverse engineer, decompile, or disassemble the Tyler Software; (c) rent, lease, lend, or provide commercial hosting services with the Tyler Software; or(d) publish or otherwise disclose the Tyler Software or Documentation to third parties. 1.5 The license terms in this Agreement apply to updates and enhancements we may provide to you or make available to you through your Maintenance and Support Agreement. 1.6 The right to transfer the Tyler Software to a replacement hardware system is included in your license. You will give us advance written notice of any such transfer and will pay us for any required or requested technical assistance associated with such transfer. As of the Effective Date,the transfer process takes eight (8)to sixteen (16) service hours, which we would provide according to the provisions of Section I(1). 1.7 We reserve all intellectual property rights, including but not limited to licensing rights, not expressly granted to you in this Agreement. The Tyler Software and Documentation are protected by copyright and other intellectual property laws and treaties. We own the title, copyright, and other intellectual property rights in the Tyler Software and the Documentation. The Tyler Software is licensed, not sold. 2. License Fees. You agree to pay us the license fees in the amounts set forth in the Investment Summary. Those amounts are payable in accordance with our Invoicing and Payment Policy. 3. Escrow. We agree to maintain an escrow agreement with a third party under which we place the source code for each major release of the Tyler Software. You may be added as a beneficiary to the escrow agreement by completing a standard beneficiary enrollment form, a copy of which is provided at Exhibit F, and paying the then-current annual beneficiary fee to the escrow agent, unless we invoice you on the escrow agent's behalf.The current annual beneficiary fee is$750. You will be responsible for maintaining your ongoing status as a beneficiary, including payment of the then-current annual beneficiary fees. Release of source code for the Tyler Software is strictly governed by the terms of the escrow agreement. 4. Limited Warranty. We warrant that the Tyler Software will be without Defect(s) as long as you have a Maintenance and Support Agreement in effect. If the Tyler Software does not perform as warranted,we will use all reasonable efforts, consistent with industry standards, to cure the Defect as set forth in the Maintenance and Support Agreement. SECTION C—PROFESSIONAL SERVICES 1. Services. We will provide you the various implementation-related services itemized in the Investment Summary. You will receive those services according to the Statement of Work, which includes a task for preparing a project plan. A sample project plan has been provided for your reference at Exhibit G. 2. Professional Services Fees. You agree to pay us the professional services fees at the rates set forth in the Investment Summary. Amounts are payable in accordance with our Invoicing and Payment Policy. You ••-o . tyler 3 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 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. 3. Additional Services. The Investment Summary contains the scope of services and related costs (including programming and/or interface estimates) required for the project based on the specifications you supplied in your RFP and/or that we addressed in our Proposal. If additional work is required other than the re- performance of services as set forth under Section C(5) or to fix a Defect as set forth under Section B(4), 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. We make all reasonable efforts to schedule our personnel for travel, including arranging travel reservations, at least two (2) weeks in advance of commitments. Therefore, if you cancel services less than two (2)weeks in advance (other than for Force Majeure or breach by us),you will be liable for all (a) non-refundable expenses incurred by us on your behalf, and (b) daily fees associated with cancelled professional services if we are unable to reassign our personnel. We will make all reasonable efforts to reassign personnel in the event you cancel within two (2)weeks of scheduled commitments. 5. Services Warranty. We are qualified to perform the services requested under this Agreement. We will perform those services in a highly professional,workmanlike manner, consistent with industry standards and applicable laws and regulations. Without limiting Section C(7), we are responsible for the professional quality of our services and deliverables outlined in the Statement of Work, and our services will be delivered according to the project schedule established under that Statement of Work. We will deliver a project plan for your review within the timeframe we mutually agree to during project kick-off. 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, using all reasonable efforts to do so in a timely manner. 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. You further agree to provide a reasonably suitable environment, location, and space for the installation of the Tyler Software, including, without limitation, sufficient electrical circuits, cables, and other reasonably necessary items required for the installation and operation of the Tyler Software. EnerGov System Requirements are set forth at Attachment C to the Statement of Work. 7. 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). 8. Personnel. After the Effective Date, and in coordination with the project kick-off activities identified in the Statement of Work,we will make our project staffing assignments. The personnel we assign will have the necessary knowledge, skills and experience to perform their assigned duties. We will provide you with project resumes, demonstrating relevant past project experience,for project team members that are •0 -0'. tyler 4 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 allocated for potential onsite services. With the exception of the resumes for the Project Manager and Principal Implementation Consultant (hereinafter"Key Personnel"),those resumes are for your information and planning purposes only. With regards to Key Personnel, however,you may(a) meet with and/or interview by phone the proposed Key Personnel, with any travel expenses for onsite meetings or onsite interviews you request to be billable to you; (b) conduct, at your expense, project reference checks on the proposed Key Personnel; and (c) approve or reject the assignment of the proposed Key Personnel. In exercising those options,you understand and agree that (d) any meeting, interview or reference check must be requested and conducted within a timeframe to be mutually agreed to; and (e) if you reject the proposed Key Personnel,you must timely notify us of that rejection, and work with us to adjust any impacted project dates and activities to accommodate a repeat of the process described above. You further understand and agree that staffing assignments, including the assignment of the Key Personnel, are subject to our reasonable discretion, and that our resources are finite. Accordingly,your approval of the proposed Key Personnel will not be unreasonably withheld. Reasonableness, in this context, will be measured by the proposed Key Personnel's ability to satisfy the standards for their respective roles and their positive reference checks. Key Personnel will have led at least one (1) prior implementation of the Tyler Software through all stages to a successful completion. The Project Manager shall incorporate the core values of the Project Management Institute in their project management methodology, and the Project Manager shall be trained in, and shall use, our proprietary project management techniques,which we deploy through repeated online and onsite training and professional development opportunities. Once our project team is assembled and your counterparts have been identified, consistent with the roles described in Attachment D to the Statement of Work, we agree that we will not remove that staff and personnel from their assigned project roles without reasonable advance notice and good cause, and that we will work with you to mitigate project impacts after any such removal. The parties will also work together to manage the project impact resulting from the temporary unavailability of project staff from either party. In the event our personnel is/are not providing services consistent with our service warranty, you will notify us of that deficiency and give us a reasonable opportunity to correct it. In the event the deficiency persists such that project progress is impeded and/or your project team has assumed our project member's responsibilities to mitigate impact on project progress,we will replace that project member upon your written request. Replacement staff will be assigned following the same processes set forth above, shall have at minimum the reasonably equivalent experience as the person being replaced, and shall be non-billable to you for the first two weeks of their project assignment (whether their services are being provided onsite or remotely,with only travel expenses being billable to you in the event they must appear onsite), allowing the individual to come up to speed and to diminish the impact to the project. SECTION D—MAINTENANCE AND SUPPORT This Agreement includes the period of free maintenance and support services identified in the Invoicing and Payment Policy. You have purchased ongoing maintenance and support services, and if you continue to make timely payments for them according to our Invoicing and Payment Policy, we will provide you with maintenance and support services for the Tyler Software under the terms of our standard Maintenance and Support Agreement. If, in the future,you opt not to purchase ongoing maintenance and support services for the Tyler Software, the Maintenance and Support Agreement will not apply to you. Instead,you will only receive ongoing maintenance and support on the Tyler Software on a time and materials basis. In addition,you will: ••-o . tyler 5 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 (i) receive the lowest priority under our Support Call Process; (ii) be required to purchase new releases of the Tyler Software, including fixes, enhancements and patches; (iii) be charged our then-current rates for support services, or such other rates that we may consider necessary to account for your lack of ongoing training on the Tyler Software; (iv) be charged for a minimum of two (2) hours of support services for every support call; and (v) not be granted access to the support website for the Tyler Software or the Tyler Community Forum. SECTION E—MyGovPay/VirtualPay The MyGovPay/VirtualPay functionality, to the extent identified as in-scope in the Investment Summary,will be provided according to the terms of this Agreement, as well as the terms set forth at Exhibit E. SECTION F—CONTRACT AMOUNT; INVOICING AND PAYMENT; INVOICE DISPUTES 1. Invoicing and Payment. We will invoice you the fees for the license(s), products, and services in the Investment Summary per our Invoicing and Payment Policy, subject to Section F(2). 2. Invoice Disputes. If you believe any delivered product or service does not conform to this Agreement,you will provide us with written notice within thirty(30) days of your receipt of the applicable invoice. The initial written notice must identify the invoiced product or service line item(s)you contend are in dispute. Within five (5) business days of that initial written notice,you will provide details explaining why you are disputing the invoiced product or service so that we can provide a written response to you that will include either a justification of the invoice, an adjustment to the invoice, or a proposal addressing the issues presented in your notice. We will work together 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 only withhold payment of the amount(s) actually in dispute until we complete the action items outlined in the action plan. Both parties shall perform under the action plan in a manner consistent with this Agreement. We reserve the right to suspend delivery of all services, including maintenance and support services, if you fail to submit payment within forty-five (45) days of an invoice not disputed as described above. 3. Contract Amount. Consistent with N.C.G.S. § 159-28(a),the following maximum amounts are established under this Agreement:The maximum amount payable under this contract for software licenses is three hundred forty-seven thousand, seven hundred twenty-two dollars ($347,722). The maximum amount payable under this contract for professional services is five hundred thirty eight thousand four hundred dollars ($538,400.00) and related business travel expenses of fifty one thousand dollars ($51,000.00). The maximum amount payable under this contract for Maintenance and Support is five hundred twenty-one thousand nine hundred twenty-three dollars ($521,923). These amounts shall not be exceeded without a duly executed written amendment or change order to this Agreement. SECTION G—TERMINATION 1. For Cause. You may terminate this Agreement for cause in the event we don't cure, or create a mutually ••-o . tyler 6 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 agreeable action plan to address, a material breach of this Agreement within forty-five (45) days of receiving notice from you under Section 1(3), Dispute Resolution. 2. Lack of Appropriations. Any payments under this Agreement that are due beyond the current fiscal year are conditioned on appropriation of sufficient funds to cover the purposes set forth in this Agreement. This Agreement shall terminate at the start of any fiscal year where you do not appropriate or otherwise make available funds sufficient to purchase, lease, operate, or maintain the products or services set forth in this Agreement. In the event of such non-appropriation,you will make all good faith efforts to provide us with reasonable advance notice of that non-appropriation. 3. Force Majeure. Either party has the right to terminate this Agreement if a Force Majeure event suspends performance of scheduled tasks for a period of ninety(90) days or more. 4. Termination for Convenience. You may terminate this Agreement for your convenience upon thirty(30) days' advance written notice to us. 5. Termination for Change of Control. In the event of a merger, acquisition, or sale of substantially all of our assets,you may terminate this Agreement within one hundred eighty days of the effective date of the change of control event upon thirty (30) days'written notice to our then-current parent. 6. Payment Obligations upon Termination. In the event of termination for cause,you will pay us for all undisputed fees and expenses related to the software, products, and/or services you have received, or undisputed expenses we have incurred, prior to the effective date of termination. Disputed fees will be subject to the dispute resolution process set forth in 1(3). You may dispute fees associated with termination for cause, even if you had not previously submitted them to the invoice provision of Section F(2). In a termination for non-appropriation, or for convenience, Force Majeure, or a change in control, any disputed fees must have been submitted to the invoice dispute process set forth in Section F(2) prior to your notice of termination. In the event of termination for lack of appropriations, no further payment shall be made or due under this Agreement except those due up to and through the last day of service for the current fiscal year. In the event of any other termination hereunder,you will pay us for all undisputed fees and expenses related to the software, products, and/or services you have received, or undisputed expenses we have incurred, prior to the effective date of termination. You will not be entitled to a refund or offset of previously paid license and other fees, except that we will issue a pro rata refund of any prepaid but unused annual maintenance fees. For the avoidance of doubt, expenses payable upon termination are those expenses incurred consistent with the provisions of the Invoicing and Payment Policy. Within a reasonable timeframe following termination, we will provide any deliverables you have paid for but not yet received, and we will return any of your electronic data and files in our possession. SECTION H—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 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, as permitted under North Carolina law. You agree to provide us with reasonable assistance, cooperation, and information in ••-o . tyler 7 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 defending the claim at our expense. 1.2 Our obligations under this Section H(1)will not apply to the extent the claim or adverse final judgment is based on your: (a) use of a previous version of the Tyler Software and the claim would have been avoided had you installed and used the current version of the Tyler Software, which was provided to you under your Maintenance Agreement; (b) combining the Tyler Software with any product or device not provided, contemplated, or approved by us; (c) altering or modifying the Tyler Software, including any modification by third parties at your direction or otherwise permitted by you; (d) use of the Tyler Software in contradiction of this Agreement, including with non-licensed third parties; or(e)willful infringement, including use of the Tyler Software after we notify you to discontinue use due to such a claim. 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. 1.4 If, as a result of an infringement or misappropriation claim, 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. In the event these options are not reasonably available to us, and/or you desire to pursue other remedies available under applicable law, we will engage in the dispute resolution process set forth in Section 1(3). 2. Property Damage and Personal Injury Indemnification. We will indemnify and hold harmless you and your agents, officials, and employees from and against any and all direct claims, losses, liabilities, damages, costs, and expenses (including reasonable attorney's fees and costs) for personal injury or property damage to the extent caused by our negligence or willful misconduct. 3. DISCLAIMER. EXCEPT FOR THE EXPRESS WARRANTIES PROVIDED IN THIS AGREEMENT AND TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, EACH PARTY HEREBY DISCLAIMS 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. 4. LIMITATION OF LIABILITY. EXCEPT AS OTHERWISE EXPRESSLY SET FORTH IN THIS AGREEMENT AND TO THE MAXIMUM EXTENT ALLOWED UNDER NORTH CAROLINA LAW, 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 A PARTY'S ACTUAL DIRECT DAMAGES. THE PRICES SET FORTH IN THIS AGREEMENT ARE SET IN RELIANCE UPON THIS LIMITATION OF LIABILITY. THE FOREGOING LIMITATION OF LIABILITY SHALL NOT APPLY TO CLAIMS THAT ARE SUBJECT TO SECTIONS H(1)AND H(2). 5. EXCLUSION OF CERTAIN DAMAGES. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL EITHER PARTY BE LIABLE FOR ANY SPECIAL, INCIDENTAL, PUNITIVE, INDIRECT, OR CONSEQUENTIAL DAMAGES WHATSOEVER, EVEN IF A PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. •= I tyler 8 • DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 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; and (d) Workers Compensation complying with applicable statutory requirements. We will add you as an additional insured on the General Liability and Auto Liability policies and provide you with copies of certificates of insurance reflecting all policies required hereunder. In the event of a cancellation of a policy required hereunder,we will provide you with commercially reasonable notice and updated certificates of insurance. SECTION I—GENERAL TERMS AND CONDITIONS 1. Additional Products and Services. You may purchase additional products and services, including but not limited to services to transfer the Tyler Software to a replacement hardware system or to perform post- implementation system performance and testing services, at the rates set forth in the Investment Summary for twenty-four(24) months from the Effective Date for services, and thirty-six (36) months from the Effective Date for products, and thereafter at our then-current list price, 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 twenty-four(24) months for services and thirty-six(36) months for products from the Effective Date. 3. Dispute Resolution. For all disputes other than invoice disputes subject to Section F(2),you agree to provide us with written notice no later than forty-five (45) 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 the other party's appointed senior representative. Senior representatives will meet at your office within forty-five (45) days of our receipt 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, either of us may assert our respective rights and remedies in court. Any and all suits or actions to enforce, interpret or seek damages with respect to any provision of this Agreement, or the performance or non-performance of this Agreement, must be brought in the General Court of Justice of North Carolina sitting in Orange County, unless the claim must be brought in federal court, in which case it must be brought in the federal district court in or serving Orange County. Nothing in this section shall prevent you or us from seeking necessary injunctive relief during the dispute resolution procedures, and the parties may agree to nonbinding mediation of any dispute prior to bringing a claim in court. 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 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 ••-o . tyler 9 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 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. Pursuant to the terms of North Carolina General Statute 1S3A-449(b), no North Carolina county may enter into a contract with a contractor unless the contractor and the contractor's subcontractors comply with the requirements of Article 2, Chapter 64 of the North Carolina General Statutes. Where applicable, failure to maintain such compliance constitutes breach of contract. We affirm our compliance with the requirements of Article 2, Chapter 64. 7. Subcontractors. We will not subcontract any services under this Agreement without your prior written consent, not to be unreasonably withheld. 8. No Assignment. Neither party may assign this Agreement without the prior written consent of the other party; provided, however, that your consent is not required in the event we have a change of control. 9. Force Maieure. 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 End User License Agreement(s). 11. Entire Agreement; Amendment. This Agreement, including the RFP and Proposal,which are incorporated herein by reference, 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. This Agreement may only be modified by a written amendment signed by an authorized representative of each party. In the event of conflict between the Agreement,the RFP, and the Proposal,the order of priority shall be (a)the Agreement; (b)the Proposal; and (c)the RFP. Any reference to future functionality that may be identified in our Proposal is not subject to this Agreement. 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 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. •0 -0'. tyler 10 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 15. Notices. All notices or communications required or permitted as a part of this Agreement 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. If you terminate this Agreement, we agree to remove your name from any then- current client lists or then-current webpages identifying our clients. 17. Confidentiality. While both parties recognize and agree to adhere to North Carolina's public records law, set forth at Chapter 132 of the North Carolina General Statutes, both parties also 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. The parties agree that the Investment Summary provided as Exhibit 1 and the pricing proposal contained within Tyler's Proposal will not be treated as confidential information, but the functional requirements checklist contained within Tyler's Proposal will be treated as a trade secret and redacted from any public disclosure in response to an open records request. We agree to indemnify and hold harmless Orange County and each of its officers, employees, and agents from all costs, damages, and expenses incurred in connection with refusing to disclose any material,which Tyler has designated as a trade secret. 18. Certifications; Business License. If the activities related to the performance of this Agreement require specific licenses, certifications or related credentials,we represent that we and/or our employees, agents and subcontractors engaged in such activities possess such licenses, certifications or credentials, and that such licenses, certifications or credentials are current, active and not in a state of suspension or revocation. In the event a local business license is required for us to perform services hereunder,you will •• . tyler DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 assist us with the necessary paperwork and/or contact information so that we may timely obtain such license. 19. Governing Law. This Agreement will be governed by and construed in accordance with the laws of North Carolina,without regard to its rules on conflicts of law. 20. Multiple Originals and 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. This Agreement,together with any amendment or modifications thereto, may be executed electronically. All electronic signatures affixed hereto evidence the intent of the parties to comply with Article 11A and Article 40 of the North Carolina General Statutes Chapter 66. 21. 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 Maintenance and Support Agreement Schedule 1: Support Call Process Exhibit D Statement of Work Exhibit E MyGovPay/IVR Terms Exhibit F Source Code Escrow Enrollment Exhibit G Sample Project Plan 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. Orange County, North Carolina Doc uSignod by: ocuSigned by: ByC ctl kk �b 4� BC�6' in�n if. RA*ALv5[" 3DE92F@F9n24@3... 3799d6755E477... Name: Dane Womble Name: Bonnie Hammersley Title: President, Local Government Division Title: Orange County Manager Date: 2/12/2016 Date: 2/16/2016 Address for Notices: Address for Notices: Tyler Technologies, Inc. Orange County, NC 5519 53rd Street 131 West Margaret Lane, Suite 300* Lubbock,Texas 79414 Hillsborough, NC 27278 Attention: Dane Womble Attention: Information Technologies *use PO Box 8181 for USPS ••-o . tyler 12 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 This instrument has been preaudited in the manner oocusigneaby: 3overnment Budget and Fiscal Control Act. 4 � 2/16/2016 704E51S1ACC 1409.. 6aiy vviiaiv..)vi i, L, itz, Financial Officer •• . tyler 13 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 • •••'•• tyler0 . • technologies Exhibit A Investment Summary The following Investment Summary details the software, products, and services to be delivered by us to you under the Agreement. This Investment Summary is effective as of the Effective Date. Capitalized terms not otherwise defined will have the meaning assigned to such terms in the Agreement. EnerGov — Software License Purchase Support/Description Cost Access Annual Maintenance EnerGov Permitting & Land Mgmt. Suite Discounted software (PLM) $123,556 55 Users $27,800 pricing=$2,246/user +18%ASM EnerGov License&Regulatory Mgmt. Discounted software Suite(LRM) $69,776 30 Users $15,700 pricing=$2,325/user +18%ASM EnerGov eReviews(Electronic Plan Does not include Review $47,999 Site license $10,800 BlueBeam Revu or Adobe Acrobat Pro Includes Viewer, EnerGov GIS(Requires ArcGIS Server GeoRule Engine, 10 or higher) $24,400 Site license $5,490 History Writer,Spatial Collections,Parcel Split Manager Intelligent Automation EnerGov Advanced Server Ext. Bundle $11,999 Site license $2,700 Agent,Intelligent Object Engine, EnerGov oData EnerGov Reporting Toolkit $3,999 Site license $900 Includes Access to iG Inspect and iG Enforce EnerGov CSS Portal PLM/LRM $48,000 Site license $10,800 EnerGov CSS Portal PLM/LRM 000 EnerGov IVR Telephony $10,000 Site license $2,250 Includes mins/monthnth Discounted software iG Workforce Mobile $7,992 10 Users $1,798 pricing=$799.20/ user+18%ASM Total Software: $347,722 ASM: $78,237 •• . tyler 14 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 Project Management & Implementation Services SupportDescription Services Cost Estimated Annual Hours Maintenance Project Management Services $80,000 500 n/a System Configuration Services $320,000 2000 n/a Totals: $400,000 2500 Training Services SupportDescription Services Cost Estimated Annual Hours Maintenance System Fundamentals Training (Administrative) $ 12,800 80 n/a End User Training & Production Support $38,400 240 n/a Services Totals: $ 51,200 320 Reporting Development SupportDescription Services Cost Estimated Annual Hours Maintenance Report Development $51,200 320 n/a Totals: $ 51,200 320 Integration Services SupportDescription Services Cost Estimated Annual Hours Maintenance Orange County CAMA $9,000 40 $ 1,620 Export from EnerGov to CAMA Totals: $9,000 40 •• . tyler 15 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 Conversion Services SupportDescription Services Cost Estimated Annual Hours Maintenance Data Conversion Source 1 — $0* 320 n/a PermitsPlus PermitsPlus `Discounted$72,000 Data Conversion Source 2—Licensed $0* 40 n/a MS Access Haulers `Discounted$9,000 Data Conversion Source 3—Legacy $ 18,000 80 n/a MS Access System Records Data Conversion Source 4—Mobile $0* 40 n/a MS Excel Home Park `Discounted$9,000 Data Conversion Source 5—GIS $9,000 40 n/a Well Point Coordinates Totals: $27,000 520 Travel Expenses Description Trips Cost/Rate Total Cost Notes $1,700/trip/ Additional trips can be Includes: All transportation, lodging and 000 added upon request— per diem 30 resource $51, estimate only,travel (estimate) billed at actual cost Totals: 30 $51,000 Optional Tyler Software (Not included in Grand Total Below) Discounted Standard Discounted Description Standard Cost Cost Annual Support Annual Support I /Maintenance Maintenance EnerGov Public Maintenance $2,999 per user $2,399 per user $600 per user $540 per user Management(PMM) Total Software: n/a n/a n/a n/a •• . tyler 16 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 Proposal Summary One-Time Costs Annual Support Fees Total Tyler Software: $ 347,722 $78,237 Total Tyler Services: $ 538,400 $1,620 Total Software&Services: $886,122 Estimated Travel Expenses: $ 51,000 Grand Total Cost: $937,122 $79,857 ********************************************************************************************************************************************* ******************************************** Summary of ASM and Pro Services Rates Summary of ASM Increases Pro Services Rates* ASM Rate Amount Pro Service Role Rate Year 1 Free Free Project Management $160/hour Year 2 0% $79,857 Configuration $160/hour Year 3 3% $82,253 Training $160/hour Year 4 3% $84,720 Reporting $160/hour Year 5 3% $87,262 Data Conversion $225/hour Year 6 5% $91,625 Integration Services $225/hour Year 7 5% $96,206 Contract Total *Pro Services Rates above to be held for 24 months from contract ASM $521,923 execution .,a m tyler 17 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 •. .�. tyler • tech nolagie Exhibit B Invoicing and Payment Policy We will provide you with the software, products, and services set forth in the Investment Summary of your Agreement. Capitalized terms not otherwise defined will have the meaning assigned to such terms in your Agreement. Invoicing: We will invoice you for the applicable license fees, products, and services in the Investment Summary as set forth below. Your rights to dispute any invoice are set forth in your Agreement. 1. Tyler Software. 1.1 License Fees: License fees are invoiced as follows: (a) 25%on the Effective Date; (b) 50%on the date when we make the applicable Tyler Software available to you for downloading (the "Available Download Date"); and (c) 25% upon sign-off of the Verification and System Acceptance Stage (Stage 513), as set forth in the Statement of Work, not to exceed the date set forth in the mutually agreeable project schedule, unless that date is deferred because of delays within our exclusive control. In the event of any such delays, payment shall be due on the actual date of Client's sign- off of Stage 5B. 1.2 Maintenance and Support Fees: Maintenance and support fees are waived for one (1)year from the Available Download Date. Subsequent maintenance and support fees, at Tyler's then-current rates, are invoiced annually in advance on the anniversary of that date. Notwithstanding the foregoing,Tyler agrees not to increase maintenance rates in year 2, by more than three (3) percent,year-over-year, in years 3 through 5, and by no more than five (5) percent,year-over- year, in years 6 and 7. That Maintenance and Support fee schedule is set forth in the Investment Summary. 2. Professional Services. 2.1 Implementation and Other Professional Services(including training): Implementation and other professional services (including training) are billed at hourly rates and invoiced monthly as delivered, subject to a five (5) percent retention. Retention amounts will be released upon sign-off of the Verification and System Acceptance Stage (Stage 513), as set forth in the Statement of Work. 2.2 Requested Modifications to the Tyler Software: Requested modifications to Tyler Software are invoiced 50% upon delivery of specifications and 50% upon delivery and acceptance of the applicable modification. Acceptance will occur when the modification performs without Priority Level 1 Defect for thirty(30) days after delivery. In the event of any such Priority Level 1 Defect, the 30-day acceptance window will repeat upon delivery of the hot fix for resolving the Priority ••-o . tyler 18 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 Level 1 Defect. 3. Expenses. The service rates in the Investment Summary do not include travel expenses, which are set forth as an estimate only. Actual expenses will be billed as incurred and only in accordance with the Business Travel Policy. Our current Business Travel Policy is attached to this Exhibit B at Schedule 1. Copies of receipts will be provided for no additional fee. Receipts for miscellaneous items less than twenty-five dollars and mileage logs are not available. We agree that our Business Travel Policy will not materially change the manner in which we are restricted in incurring expenses, and will provide written notice to you of any other changes. Payment. Payment for undisputed invoices is due within forty-five (45) days of the invoice date. Maintenance and support fees are due on each anniversary of the Available Download Date. We prefer to receive payments electronically. Our electronic payment information is: Bank: Wells Fargo Bank, N.A. 420 Montgomery San Francisco, CA 94104 ABA: 121000248 Account: 4124302472 Beneficiary: Tyler Technologies, Inc.—Operating ••-o . tyler 19 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 • •••'•• tyler0 . • technologies Exhibit B Schedule 1 Business Travel Policy 1. Air Travel A. Reservations &Tickets Tyler's Travel Management Company(TMC)will provide an employee with a direct flight within two hours before or after the requested departure time, assuming that flight does not add more than three hours to the employee's total trip duration and the fare is within $100 (each way) of the lowest logical fare. If a net savings of$200 or more (each way) is possible through a connecting flight that is within two hours before or after the requested departure time and that does not add more than three hours to the employee's total trip duration,the connecting flight should be accepted. Employees are encouraged to make advanced reservations to take full advantage of discount opportunities. Employees should use all reasonable efforts to make travel arrangements at least two(2) weeks in advance of commitments. A seven day advance booking requirement is mandatory. When booking less than seven days in advance, management approval will be required. In the event we book travel less than seven days in advance for reasons within our control,Tyler will only invoice the advance fare that would have been payable for reimbursement. Except in the case of international travel where a segment of continuous air travel is scheduled to exceed six hours,only economy or coach class seating is reimbursable. B. Baggage Fees Reimbursement of personal baggage charges are based on trip duration as follows: • Up to five days=one checked bag • Six or more days=two checked bags Baggage fees for sports equipment are not reimbursable. 2. Ground Transportation A. Private Automobile Mileage Allowance—Business use of an employee's private automobile will be reimbursed at the current IRS allowable rate, plus out of pocket costs for tolls and parking. Mileage will be calculated by using the employee's office as the starting and ending point, in compliance with IRS regulations. Employees who •• . tyler 20 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 have been designated a home office should calculate miles from their home. B. Rental Car Employees are authorized to rent cars only in conjunction with air travel when cost, convenience,and the specific situation reasonably require their use. When renting a car for Tyler business,employees should select a "mid-size"or"intermediate"car. "Full" size cars may be rented when three or more employees are traveling together. Tyler carries leased vehicle coverage for business car rentals;additional insurance on the rental agreement should be declined. C. Public Transportation Taxi or airport limousine services may be considered when traveling in and around cities or to and from airports when less expensive means of transportation are unavailable or impractical. The actual fare plus a reasonable tip(15-18%) are reimbursable. In the case of a free hotel shuttle to the airport,tips are included in the per diem rates and will not be reimbursed separately. D. Parking&Tolls When parking at the airport, employees must use longer term parking areas that are measured in days as opposed to hours. Park and fly options located near some airports may also be used. For extended trips that would result in excessive parking charges, public transportation to/from the airport should be considered. Tolls will be reimbursed when receipts are presented. 3. Lodging Tyler's TMC will select hotel chains that are well established, reasonable in price, and conveniently located in relation to the traveler's work assignment. Typical hotel chains include Courtyard, Fairfield Inn, Hampton Inn, and Holiday Inn Express. If the employee has a discount rate with a local hotel,the hotel reservation should note that discount and the employee should confirm the lower rate with the hotel upon arrival. Employee memberships in travel clubs such as AAA should be noted in their travel profiles so that the employee can take advantage of any lower club rates. "No shows"or cancellation fees are not reimbursable if the employee does not comply with the hotel's cancellation policy. Tips for maids and other hotel staff are included in the per diem rate and are not reimbursed separately. 4. Meals and Incidental Expenses Employee meals and incidental expenses while on travel status are in accordance with the federal per diem rates published by the General Services Administration. Incidental expenses include tips to maids, hotel staff,and shuttle drivers and other minor travel expenses. Per diem rates are available at www.gsa.gov/perdiem. •0 -0'. tyler 21 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 A. Overnight Travel For each full day of travel,all three meals are reimbursable. Per diems on the first and last day of a trip are governed as set forth below. Departure Day Depart before 12:00 noon Lunch and dinner Depart after 12:00 noon Dinner Return Day Return before 12:00 noon Breakfast Return between 12:00 noon&7:00 p.m. Breakfast and lunch Return after 7:00 p.m.* Breakfast, lunch and dinner *7:00 p.m. is defined as direct travel time and does not include time taken to stop for dinner The reimbursement rates for individual meals are calculated as a percentage of the full day per diem as follows: • Breakfast 15% • Lunch 25% • Dinner 60% B. Same Day Travel Employees traveling at least 100 miles to a site and returning in the same day are eligible to claim lunch on an expense report. Employees on same day travel status are eligible to claim dinner in the event they return home after 7:00 p.m.* *7:00 p.m. is defined as direct travel time and does not include time taken to stop for dinner 5. Internet Access—Hotels and Airports Employees who travel may need to access their e-mail at night. Many hotels provide free high speed internet access and Tyler employees are encouraged to use such hotels whenever possible. If an employee's hotel charges for internet access it is reimbursable up to$10.00 per day. Charges for internet access at airports are not reimbursable. ••-o . tyler 22 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 • •••'•• tyler0 . • technologies Exhibit C Maintenance and Support Agreement We will provide you with the following maintenance and support services for the Tyler Software. Capitalized terms not otherwise defined will have the meaning assigned to such terms in the Agreement. 1. Term. We provide maintenance and support services on an annual basis. The initial term commences on the date when we make the applicable Tyler Software available to you for downloading (the "Available Download Date") and remains in effect for one (1)year. The term will renew automatically for additional one (1)year terms unless terminated in writing by either party at least thirty(30) days prior to the end of the then-current term. 2. Maintenance and Support Fees. Your initial maintenance and support fees for the Tyler Software licensed to you are listed in the Investment Summary of your Agreement. Those amounts are payable in accordance with our Invoicing and Payment Policy. We reserve the right to suspend maintenance and support services, after fifteen (15) days' notice, if you fail to pay undisputed maintenance and support fees within sixty (60) days of the due date. We will reinstate maintenance and support services only if you pay all undisputed past due maintenance and support fees as well as sixty percent (60%) of fees for the periods during which services were suspended. 3. Maintenance and Support Services. As long as you are trained on the Tyler Software such that you are not using the Help Desk as a substitute for training, and timely pay your undisputed maintenance and support fees,we will, consistent with our then-current Support Call Process: 3.1 perform our maintenance and support obligations in a professional, good, and workmanlike manner, consistent with industry standards,to conform the Tyler Software to the warranty set forth in your Agreement; provided, however, that if you modify the Tyler Software without our consent, our obligation to provide maintenance and support services on and warrant the affected Tyler Software will be void; 3.2 provide telephone support during our established support hours, as set forth in the Support Call Process; 3.3 maintain personnel that are sufficiently trained to be familiar with the Tyler Software and Third Party Software in order to provide maintenance and support services; 3.4 provide you with a copy of 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 3.5 resolve Defects in at least the then-current release and the immediately prior release, and provide •0 -0'. tyler 23 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 Help Desk support (ie. answer user questions) on all versions of the Tyler Software that Tyler continues to support for the Tyler Software customer base generally. 4. Client Responsibilities. We will use all reasonable efforts to perform any maintenance and support services remotely. Currently, we use a third-party secure unattended connectivity tool called Bomgar, as well as GotoAssist by Citrix. We will also support unattended connectivity through a CISCO VPN. 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 can't resolve a support issue remotely, we may be required to provide onsite services. In such event,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 a VPN for backup connectivity purposes. 5. Excluded Services. Maintenance and support fees do not include fees for the following services: (a) initial installation or implementation of the Tyler Software; (b) onsite maintenance and support (unless Tyler cannot remotely correct a Defect); (c) application design; (d) other consulting services; (e) maintenance and support of an operating system or hardware; (f) support outside our normal business hours as listed in our then-current Support Call Process; or(g) installation, training services, or third party product costs related to a new release. Any such out-of-scope maintenance and support services that you request will be billed to you at our then current service rates, subject to Section I(1). We reserve the right to decline support calls from users who have not received the required training on the Tyler Software and who are using the Help Desk to receive that training. 6. Current Support Call Process. Our current Support Call Process for the Tyler Software is attached to this Exhibit C at Schedule 1. We agree that we will not materially alter the manner in which we provide support services and will provide written notice to you of any other alterations. ••-o . tyler 24 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 • • •'• • tyler • •• •,• technologies Exhibit C Schedule 1 EnerGov Support Call Process Support Channels We provide the following channels of EnerGov software support: (1) Telephone—for urgent or complex questions, users receive toll-free, unlimited telephone software support. (2) Email—for less urgent situations, users may submit unlimited emails directly to the software support group. Email will be used for responses. (3) On-line submission—for less urgent and project-based questions, users may create unlimited support incidents through the customer relationship management portal available at the Tyler Technologies website. (4) Tyler Community—an on-line resource,Tyler Community provides a venue for all Tyler clients with current maintenance agreements to support one another, share best practices and resources, and access documentation. During the Implementation to Support handoff meeting, at the conclusion of the client's project,Tyler representatives will provide the most current toll-free telephone number and email address for submitting support incidents, based on the software licensed. Support Availability Our established software support hours are Monday through Friday from 8:00 AM—8:00 PM Eastern Time. Tyler's holiday schedule is outlined below.There will be no support coverage on these days. New Year's Day Thanksgiving Day Memorial Day Day after Thanksgiving Independence Day Christmas Eve Labor Day Christmas Day Issue Handling ❑ Incident Tracking When a support incident is logged,the client receives an incident tracking number for that issue. The incident tracking number is used to track and reference open issues when clients contact support. ••o . tyler 25 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 ❑ Incident Escalation Tyler's software support consists of four levels of personnel: (1) Software Support Analysts—front-line representatives (2) Software Support Advisors—more senior in their support role,the Advisors assist Software Support Analysts and take on escalated issues (3) Software Support Team Leads—responsible for the day-to-day supervision of Analysts and Advisors and may assist in incident escalations (4) Software Support Managers—responsible for the management of support teams for either a single product or a product group On occasion,the priority or immediacy of a software support incident may change after initiation.Tyler encourages clients to communicate the level of urgency or priority of software support issues so that we can respond appropriately. A software support incident can be escalated by any of the following methods: (1) Telephone—for immediate response, call toll-free to either escalate an incident's priority or to escalate an issue through management channels as described above. (2) Email—clients can send an email to software support in order to escalate the priority of an issue (3) On-line Support Incident Portal—by logging into the client incident portal and referencing the appropriate incident tracking number, clients can modify the priority of an issue. ❑ Incident Priority Each incident is assigned a priority number,which corresponds to the client's needs and deadlines.The client is responsible for reasonably setting the priority of the incident per the below chart. The goal of this structure is to clearly understand and communicate the importance of the issue and to describe expected responses and resolutions. Issue Priorities& Resolutions Priority Characteristics of Support Resolution Targets Development Level Incident Actions Support incident that causes (a) Tyler shall provide an initial response to complete application failure or Priority Level 1 incidents within one (1) application unavailability; (b) business hour of receipt of the support application failure or incident. Tyler shall use commercially Hot Fix— 1 unavailability in one or more of reasonable efforts to resolve such support Emergency patch the client's remote location; or incidents or provide a circumvention to software as (c) systemic loss of multiple procedure within one (1) business soon as possible essential system functions. day. Tyler's responsibility for loss or corrupted data is limited to assisting the client in restoring its last available database. •• . tyler 26 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 Issue Priorities& Resolutions Priority Characteristics of Support Resolution Targets Development Level Incident Actions Support incident that causes (a) Tyler shall provide an initial response to repeated, consistent failure of Priority Level 2 incidents within four(4) essential functionality affecting business hours of receipt of the support more than one user or (b) loss incident. Tyler shall use commercially 2 or corruption of data. reasonable efforts to resolve such support regularly- incidentspatch— or provide a circumvention scheduled patch procedures within five (5) business days. Tyler's responsibility for loss or corrupted data is limited to assisting the client in restoring its last available database. Priority Level 1 incident with an Tyler shall provide an initial response to existing circumvention Priority Level 3 incidents within one (1) procedure, or a Priority Level 2 business day of receipt of the support incident that affects only one incident. Tyler shall use commercially user or for which there is an reasonable efforts to resolve such support Next Release— 3 existing circumvention incidents without the need for a Scheduled for the procedure. circumvention procedure with the next next major published maintenance update or service release pack, which shall occur at least quarterly. Tyler's responsibility for lost or corrupted data is limited to assisting the client in restoring its last available database. Support incident that causes Tyler shall provide an initial response to failure of non-essential Priority Level 4 incidents within two (2) functionality or a cosmetic or business days. Tyler shall use commercially Future release— 4 other issue that does not qualify reasonable efforts to resolve such support not scheduled; as any other Priority Level. incidents within two version release cycles reviewed at next and a cosmetic or other support incident planning stage that does not qualify as any other Priority Level incident with a future version release. Hardware and Other Systems If in the process of diagnosing a software support issue it is discovered that a peripheral system or its software is the cause of the issue, we will notify the client so that the client may contact the support agency for that peripheral system. We cannot support or maintain third-party software or hardware. In order for us to provide the highest level of software support,the client bears the following responsibility related to hardware and software: ••-o . tyler 27 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 (1) All infrastructure executing Tyler software shall be managed by the client. (2) Support contracts for all third-party software (ex: operating systems, database management systems) associated with Tyler software shall be maintained. Tyler does not support these third-party products. (3) Daily database backups must be performed; client shall verify the backups are successful. As a standard part of Tyler's process,Tyler will provide to client Tyler's recommended backup process, which the client is expected to acknowledge in writing. Client may also engage Tyler to provide disaster recovery services,which Tyler will provide upon request at Tyler's then-current rates. •0 -0'. tyler 28 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 EXHIBIT D • • V . energov a tyler planning, permitting & licensing solution Statement of Work For EnerGov Implementation Prepared for: Orange County, NC Prepared by: Tyler Technologies, Inc. 2160 Satellite Blvd, Suite 300 Duluth, GA 30097 888.355.1093 www.tylertechnolo gies.com ••� tyler 29 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 TYLER RESOURCES PURCHASED The total professional services hours set forth in the Investment Summary have been allocated to the project as follows: • Project Management Services=500 resource hours • System Configuration Services=2000 resource hours • System Administration/Fundamentals Training=80 resource hours • End User Training&Production Support =240 resource hours • Report Development Services =320 resource hours • Data Conversion Services =520 resource hours • Please see Appendix 1 for additional information on Data Conversion • Integration Services=40 resource hours • Travel=30 on-site trips(where a"trip"is defined as onsite travel of up to five business days) • The project plan,addressed below,will give detail on when Tyler expects to be traveling onsite over the course of the project. • Tyler expects 2 trips will be required for fundamentals training,and 6 trips will be required for end-user training and production support. RESOURCE ALLOCATION MATRIX BY STAGE By Stage,we expect to allocate the resources identified above as set forth in the table below. These allocations are estimates,and subject to change as the dynamics and specifics of the project get confirmed during Stage 1. Stage 0-Software Delivery Est.Hours per Stage Stage 1—Planning&Initiation 205 Stage 2-Assess&Define 625 Stage 3A—System Configuration 750 Stage 36—Configuration Internal Test 250 Stage 4A-Build Spec 220 Stage 4B-Build 660 Stage 5A-Acceptance Planning 250 Stage 5B-Verification&Acceptance 500 Stage 6—User Training 160 Stage 7-Production 80 Total Hours 3700 The overwhelming majority of configuration from the County's data sources(as identified in Stage 4A)to the defined EnerGov structure occurs during Stage 3A;a much smaller amount occurs during Stage 5B(with the focus of such configuration being on fine-tuning and reconfigurations based on testing results). Appendix 1 summarizes the overall conversion approach over the stages of the project. Initial conversion cannot be completed until configuration is complete. On average,no more than 5%of service hours are used for ePortal,IVR and iG Workforce. �. tyler 30 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 TASKS The following tasks have been arranged for this project,with responsibility definitions for both Tyler and Customer as follows: • Own—Ownership of the task throughout • Participate—Active,ongoing participation in the task throughout • Advise—Advisory role as needed by the other party • None—No planned/required involvement by the designated party Upon completion of a task,the customer will have an opportunity to review the deliverable,if any,associated with the task. The customer will have ten business days to identify to Tyler a deviation from the warranties provided in the parties' agreement,except as otherwise agreed over the course of project planning and baseline scheduling during Stage 1. Over the course of the project,the parties may mutually agree to an extended timeframe for the customer's deliverable review on a deliverable-by-deliverable basis. In the event a deviation is identified and confirmed,Tyler will address the deviation according to the terms of the Support Call Process or the services warranty provision set forth in the Agreement,as applicable. When a corrected deliverable has been resubmitted for review,that process shall repeat. Upon Stage completion,Tyler will provide the customer with a Work Acceptance Form to document that all tasks(as previously reviewed and accepted according to the process set forth above)within the Stage have been successfully delivered. The customer must return the completed Work Acceptance form within five business days of receipt or advise Tyler that it requires more time to return the sign-off,including an identification of the issue preventing timely sign-off, with any additional time for such sign-off to be mutually agreed to by the parties.Absent any such notice,the Stage will be deemed"accepted"after the five(5)days have passed,even if the customer does not return a signed form. A sample Work Acceptance Form is provided at SOW Attachment A. Each stage is dependent on the results of the previous stage and therefore,each stage of the methodology cannot begin until the previous stage is completed and approved. Stage 0- Software Delivery; Third Party License Acquisitions Objectives: o Tyler software is made available the customer o Customer purchases third-party licenses and field units to facilitate Stage 1 Fundamentals training. Tasks: Software Delivery Tasks Tyler Customer Tyler makes the licensed software available on the project Own None SharePoint site for downloading Customer purchases Adobe and/or Bluebeam Revu licenses None Own Customer ensures that sufficient field units are available for None Own customer personnel participating in Fundamentals Training Stage 1—Planning&Initiation Prior to the system configuration,the project teams will plan and define project expectations. The contract and this Statement of Work will be reviewed,project planning activities will be completed,and Tyler will begin to instill end-user acceptance and transfer system knowledge. Objectives: o Project kick-off,with introduction to project and detailed review of Stages,Tasks and Milestones/Deliverables . tyler 31 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 o Distribution of forms and gathering of high-level organizational and process information o Establishment of communication channels(Project Manager, SMEs,Permitting Systems Coordinator, etc.)and communication paths(status reporting,issue and risk management reporting,and deliverable signoff procedures) o Review roles and responsibilities o Assessment of IT infrastructure and needs o Coordinate project logistics,including work locations o Planning for staff mobilization&allocation o Team Training—System Admin/EnerGov Fundamentals training on EnerGov software,made available during Stage 0 and installed during this Stage 1. o Create project plan addressing all system components,including baseline project schedule Tasks: Planning&Initiation Tasks Tyler Custo Conduct Planning/Initiation Introductory Phone Call Own Participate Assign Project Team Members Advise Own Provide/Assign facilities for Tyler on-site activities Advise Own Identify non-working days(i.e.vacations,holidays,etc.) Own Participate Define procurement and configuration plan for necessary Advise Own hardware,non-EnerGov systems software and networking infrastructure by the customer as specified by SOW Attachment C Provide Tyler remote access(when needed)to required Advise Own server for Tyler software installation and system configuration Tyler remotely installs the software Own Participate Deliver and review Process and Configuration Collection Own Participate Templates Create SharePoint site to manage project deliverables, Own None documents,and UAT Deliver and review Project Status Report Template Own Participate Deliver and review Sample Signoff Form Own Participate Deliver and review GIS requirements and best practices Own Participate documentation Deliver and review Data Conversion Template Database Own Participate (DCT-DB),ERDs and usage documentation to answer questions and provide guidance to OC staff in preparation for initial data load from legacy systems. Prepare programs/databases for integration by Advise Own cleansing/scrubbing customer data to prepare for populating the template database Identify and document project risks and resolutions Own Participate Deliver and review Project Plan(including project schedule) Own Participate Other tasks as identified Own for Own for respective team respective team Team Training-System Admin/EnerGov Fundamentals Own Participate Deliver Project Planning&Initiation Stage Sign Off to Own None Customer Return Project Planning&Initiation Stage Sign Off to Tyler None Own •'•• tyler 32 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 Milestone/Deliverable: Signoff of Initiation and Planning Stage 0 .,a m t y I e r 33 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 Stage 2 -Assess&Define This stage involves onsite and offsite comprehensive business process,change management,and systems assessment and analysis.The goal is to examine the customer's current business process("assess")and translate those findings into a defined and documented future state process("define")to best automate the unique customer processes. With guidance and mapping assistance from Tyler,as set forth in Stage 1,County will also analyze and prepare data sources to be converted based on the structure of the DCT-DB,which will be an ongoing/iterative process up through the final conversion pass. For the avoidance of doubt, scope for converted data sources set forth in the table in Stage 4A is limited 5 iterative passes from the DCT-DB to the EnerGov master database.A data source load/population to the DCT-DB does not count against those 5 iterations. Objectives: o Comprehensive review and analysis of customer's business processes to be automated o Translate business understanding into the"to-be"documented EnerGov configuration definition documentation,which will serve as the basis for system configuration o Refinement of project plan,including identification of project risks or additional infrastructure requirements o Perform gap analysis between EnerGov standard reports,key performance indicators,and existing document output requirements so as to confirm that sufficient report development services are in scope and to build a master list of the reports to be specified and developed in subsequent stages. o Conduct prototype sessions o Determine integration strategy,including definition of system integrations and scope confirmation. o Determine data migration strategy. o Address any additional scope requirements through a mutually agreeable change order. A sample Change Order request form is provided at SOW Attachment B,a sample Custom Programming request form is provided at SOW Attachment E.and a Custom Report request form is provided at SOW Attachment F. Definition: As discussed above,during this stage the parties analyze the customer's business processes. As part of this process,the parties identify the"Business Case Transactions,"also known as workflows,which are the defined configuration of an automated business process in which documents and/or other information is passed from one participant to another(or others)for action according to a set of shared procedural rules. Where several transactions rely on the same set of procedural rules,a single configuration will apply to the otherwise unique workflows. Where one transaction depends on the automation of one or more distinct procedural rule(s),a new configuration will be required for that transaction. The configuration consists of the following components,where uniqueness of these components constitutes a new and unique business case transaction: o The to-be configured business process workflow,including output actions o Automation logic o Fee assessment and configuration definition o Custom fields and forms definition. The final business case transaction documents finalized during Assess&Define stage will serve as the baseline "scope"for the EnerGov system configuration within the subsequent Configuration stage. Tasks: Assess&Define Tasks Tyler Customer Identify Business Transactions/Case Types(i.e.Permit Advise Own —Types,Plan Types,Inspection Types,etc.) Scope and document EnerGov configuration design Own Participate document per business transaction/process . tyler 34 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 Return process and configuration collection templates to Advise Own Tyler Deliver ArcGIS base map service(s)to Tyler Advise Own Deliver"Report Inventory"with sample reports. None Own Develop Project Definition Documents to include Own Participate comprehensive collection of business processes, —configuration and other details identified during this Stage Conduct initial and analysis and preparation of data to Participate Own be converted based on the structure of the DCT-D13 Amend project scope/SOW as needed Own Participate Deliver and review Project Definition Documents Own Participate Other tasks as identified Own for Own for respective team respective team Deliver Assess&Define Stage Sign Off to Customer Own None Return Assess&Define Stage Sign Off to Tyler None Own Milestone/Deliverable: Signoff of Assess&Define Stage Stage 3A—System Configuration Stage 3A initiates a process that concludes with Stage 413. That process consists of system configuration around the requirements collected and established during the preceding stages,and documented in the project definition documents. Data conversion,development and/or configuration of interfaces,and report development also occur during these stages, and internal system reviews are performed with the EnerGov executive review committee. Objectives: o Configure the core EnerGov software in accordance with configuration definitions from Assess& Define stage o Collaborate onsite system review sessions for configuration validation Tasks: System Configuration Tasks Tyler Customer Deploy Pre-production environment to house the Advise Own configuration system as defined and reviews by Tyler's Hardware/Infrastructure requirements documentation Configure the software based upon the EnerGov Own Participate configuration definitions established in the previous Assess &Define stage Perform ongoing reviews with customer as configuration Own Participate progresses Deliver populated Data Conversion Template Database None Own (DCT-DB) Complete Basic Configuration Reviews Own Participate Deliver System Configuration Stage Sign Off to Customer Own None Return System Configuration Stage Sign Off to Tyler None Own Milestone/Deliverable: Signoff of System Configuration Stage . tyler 35 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 Stage 3B—Configuration-Internal Test Objectives: o Conduct initial operational test to ensure that Tyler has the information and configurations necessary to complete report development and data conversions o Confirm basic system configuration to ensure proper operation Tasks: Internal Test Tasks Tyler Customer Provide users logins for key Customer staff Own None Conduct basic system configuration testing/retesting Own Participate walkthrough Record testing results in SharePoint None Own Resolve any system issues identified Own None Other tasks as identified Own for Own for respective team respective team Deliver Internal Testing Stage Sign Off to Customer Own None Return Internal Testing Stage Sign Off to Tyler None Own Milestone/Deliverable: Signoff of Internal Test Stage Stage 4A-Build Specifications Objectives: o Define custom report requirements and prioritize custom report requirements to prepare or refine customer report hours estimate or to determine whether additional hours are needed via a change order o Define and map data conversion requirements(see section titled Data Conversion) o Define integration specifications,as applicable o Define and map,based on provided API's,interface requirements,as applicable Data op S stem Name Details =ffComments Permits Plus 320 service hours Licensed Haulers 40 service hours Legacy System Records 80 service hours Mobile Home Park 40 service hours GIS 40 service hours System Name Details CAMA 40 service hours Tasks: Build Specifications Tasks Tyler Customer Deliver and review list out-of-the-box standard reports, Own Participate documents,dashboards and search consoles in order to identify any gaps in report coverage that may require custom report development Develop Report Specifications(including formula for any None Own field calculations/summaries)and PDF samples for any required custom reports,if necessary tyler 36 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 Deliver Custom Report Development estimate(hours and Own Participate cost)and accompanying Change Order(if necessary) Deliver APIs for integrations,as necessary None Own Develop integration specifications Own None Deliver and review integration specifications to Customer Own Participate Other tasks as identified Own for Own for respective team respective team Deliver Build Specifications Stage Sign Off to Customer Own None Return Build Specifications Stage Sign Off to Tyler None Own Milestone/Deliverable: Signoff of Build Specifications Stage Stage 4B-Build Objectives: o Develop Custom Reports per defined requirements,if any o Import data from Data Conversion Template Database(DCT-DB)into master EnerGov database o Development of scoped and defined integrations,as applicable Tasks: Tasks Tyler Customer Deliver and review populated Data Conversion Template Advise Own Database(DCT-DB)with EnerGov Data Services team member(s) Import data into EnerGov master database from populated Own None Data Conversion Template Database(DCT-DB) DCT-DB-> EnerGov master DB Iteration 1 Produce,deliver and review internally tested import of legacy Own Participate data into EnerGov master database Produce,deliver and review internally tested custom reports Own Participate per defined requirements(if necessary) Produce,deliver and review internally tested integrations per Own Participate defined requirements Provide and review the documented cut over strategy Own Participate Other tasks as identified Own for Own for respective team respective team Deliver Build Stage Sign Off to Customer Own None Return Build Stage Sign Off to Tyler None Own Milestone/Deliverable: Signoff of Build Stage Stage 5A- System Acceptance Planning Stages 5A and 5B focus on administrative knowledge transfer and the validation of the prior due diligence and configuration stages before the system is moved to a production environment. Objectives: o Create test scripts based on pre-determined functionality requirements criteria o Provide system overview and administrator training and knowledge transfer for power users(i.e. customer testers,administrators and IT) o Conduct testing and system validation for promotion to end user training Tasks: AcceptanceSystem �. tyler 37 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 Tasks Tyler Customer Develop and review acceptance schedule and criteria, Own Participate —including training materials Coordinate training logistics and schedule Own Participate Provide facilities suitable to training and testing needs Advise Own Provide,if requested by Customer,Tyler's training lab Own Advise Recommend test strategies,scenarios and best acceptance Own Participate —practices Provide sample test scripts,as requested Own Advise Develop test scripts and testing criteria(based on Advise Own documented business processes,interfaces,imports, —reporting,etc. Provide System Overview and Administrator training for Own Participate Power Users Deliver fully configured database for pre-System Acceptance None Own Testing data import to EnerGov Populate Data Conversion Template Database(DCT-DB) None Own with latest conversion iteration for System Acceptance Testing Conduct pre-System Acceptance Testing import of data from Own None Data Conversion Template Database(DCT-DB)in master EnerGov database and deliver to Customer DCT-DB-> EnerGov master DB(Iterations 2 and 3) Deploy fully configured and imported master EnerGov None Own database into the Production testing environment Other tasks as identified Own for Own for respective team respective team Deliver System Acceptance Planning Stage Sign Off to Own None Customer Return System Acceptance Planning Stage Sign Off to Tyler None Own Milestone/Deliverable: Signoff of System Acceptance Planning Stage Stage 5B—Verification and System Acceptance Objectives: o Test and signoff on each delivered business process,suite or component(including configurations, reports,data,integrations,and custom development features)based on defined criteria and scope o Confirm that the full system is ready for production,as defined immediately below,and promoted to a production and/or training environment ■ "Ready for production"means that items that are not features enhancement or bugs that will allow the customer to move forward to User Training(Stage 6)and then go-live are addressed Tasks: Verification and System Acceptance Tasks Tyler Customer Conduct testing of custom(if necessary)and standard reports Advise Own Conduct testing of main EnerGov forms and end-to-end Advise Own —system functionality Conduct testing of produced integrations Advise Own Conduct testing of imported data Advise Own ••� tyler 38 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 Record testing results in SharePoint None Own Resolve material System Acceptance Testing issues(ie. Own Participate issues that would prevent moving the system into a —production environment Retest until acceptance criteria developed in Stage 5A are Participate Own met such that go-live can occur Identify out-of-scope configuration changes that do not Own Participate impact System Acceptance based on predefined scope for postgo-live change order Other tasks as identified Own for Own for respective team respective team Deliver Verification and System Acceptance Stage Sign Off Own None to Customer Return Verification and System Acceptance Stage Sign Off None Own to Tyler Milestone/Deliverable: Signoff of Verification and System Acceptance Stage Stage 6-User Training This stage concentrates on completing the knowledge transfer process. A tailored training program will be delivered to address the customer's business processes,workflows,and terminology and how those components are captured within the configured system. Objectives: o Provide requisite hours of classroom and one-on-one training and knowledge transfer on all system components Tasks: User Training Tasks Tyler Customer Produce,deliver and review customer-specific training Own Participate materials for end user training Coordinate training logistics and schedule Own Participate Provide facilities suitable to training needs Advise Own Provide,if requested by Customer,Tyler's training lab Own Advise Deliver fully configured database for pre-User Training data None Own —import to EnerGov Populate Data Conversion Template Database(DCT-DB) None Own with latest iteration for User Training Conduct pre-User Training import of data from Data Own None Conversion Template Database(DCT-DB)in master EnerGov database and deliver to Customer(DCT-DB-> EnerGov master DB(Iteration 4) Deploy fully configured and imported master EnerGov None Own database into the Production testing environment Conduct customer training Own Participate If"train the trainer"approach,conduct end-user training None Own Other tasks as identified Own for Own for respective team respective team Deliver User Training Stage Sign Off to Customer Own None Return User Training Stage Sign Off to Tyler None Own ••• tyler 39 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 Milestone/Deliverable: Signoff of User Training Stage Stage 7—Production &Production Support During this stage,Tyler delivers project team support on the"live"system. As that support and consultation is delivered, the project team will also facilitate the customer's transition to Tyler's help desk support staff. Objectives: o Conduct final data import cutover o Conduct final integration deployment o Tyler to provide on-site production support prior to cutover to Help Desk(Maintenance and Support) o Project closure Tasks: Production Production Support Tasks Tyler Customer Deliver fully configured database for Production data import None Own to EnerGov Populate Data Conversion Template Database(DCT-DB) None Own with latest iteration for Production Conduct Production import of data from Data Conversion Own None Template Database(DCT-DB)in master EnerGov database and deliver to Customer(DCT-DB->EnerGov master DB (Iteration 5) Deploy fully configured and imported master EnerGov None Own database into the Production environment Provide onsite pre and post production support Participate Own Define support logistics and schedule Own Advise Provide technical and functional user support Participate Own Develop and maintain post-production issues list in Participate Own SharePoint Ensure key/critical personal are present and available to Advise Own —participate Other tasks as identified Own for Own for respective team respective team Deliver Production&Production Support Stage Sign Off to Own None Customer Return Production&Production Support Stage Sign Off to None Own —Tyler Milestone/Deliverable: Signoff of Production&Production Support Stage,representing project closure *DATA CONVERSION (see tasks associated with data transfer, above) Tyler's data conversion strategy is based on industry best practices. The rules and mapping processes applied during the data conversion process are set forth below. As noted in the tasks set forth above,Tyler will provide the data conversion template(DCT),which is Tyler's recommended format for data conversion. The resulting data format will be based on the completed data conversion iterations described in Stage 2,where an iteration is a completed importation from the DCT-DB to the EnerGov Master DB. ❑ Data Format The customer must provide data to Tyler in the Data Conversion Template Database(DCT-DB)structure,as set forth in the . tyler 40 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 SOW Attachments G and H. Providing data in this format will ensure that data is properly imported into the system. Data not provided in this structure will not be considered for import. ❑ Data scrubbing/cleansing Any data scrubbing should be done by the customer prior to populating the DCT-DB. Data scrubbing and cleansing is not included in the EnerGov proposal. ❑ Required Fields Problems in data conversions typically result from customer data that has not been scrubbed prior to the data conversion process. There are certain fields in the EnerGov software which are required fields,and we cannot write records to the EnerGov master DB without populating these columns. Sometimes,these required fields will not be available in the legacy source data,so a simple default value can be written to the DCT-DB to fulfill the NOT NULL constraint. Tyler would write the default value as part of the conversion process. ❑ Custom Fields Most legacy systems will have some attribute fields that are not specified in the corresponding master table within DCT- DB. In the EnerGov software,we will refer to these as custom fields. Within each module,there will be a child table for such custom fields. Since these are specific to the legacy system(s),the customer may add columns to these tables in DCT- DB to accommodate any needed custom fields in the migration. ❑ Parsing data The data format is defined based on the fields that exist in the EnerGov module(street number and street name,for example). If the customer would like that data to be converted,the customer will have to break out its legacy data so that it matches the EnerGov data fields. Address Data: Tyler does not parse out address information for optimization purposes.Rather the customer is responsible to deliver the address information in the requested(preferred format).Tyler will import the address data delivered(format) and map the fields to the best possible location in the EnerGov system. Tyler is not responsible for cleanup of inconsistent addressing. Phone Numbers:Phone numbers are imported in the format in which the data is delivered to Tyler. Tyler is not responsible for cleanup of inconsistent numbering or sequencing. Individuals/Names: Individual names are imported in the format in which the data is delivered to Tyler. Tyler is not responsible for parsing out single name fields into First,Last,Middle,Company,etc. Contacts Data: Tyler creates a unique Contact ID for each contact in the EnerGov system,along with duplicate detection measures,to ensure that a contact is entered once,and only once. If contact data is not keyed in such a way that each instance of a person has one,and only one,contact record(the record with all of their attributes such as name,address, company,phone,etc.)in the data source,then the contacts associated with a record will typically be imported into a general information tab rather than into the EnerGov Enterprise Contacts Manager. ❑ Business-Specific Rules Business specific rules are handled in the software configuration process and cannot typically be mapped within the data conversion process.This includes but is not limited to EnerGov Intelligent Objects and EnerGov Case Workflows. ❑ Calendars&Scheduling EnerGov software can import scheduled hearings and meeting details;however any data residing on an actual calendar control is excluded from the scope of the data conversion. . tyler 41 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 KEY PROJECT ASSUMPTIONS ❑ Tyler shall initially implement the most current version of the Tyler software at the time of the contract signing.During the implementation Tyler will provide newer releases of the software that meet or exceed the version available at contract signing,in coordination with project schedule and status.After Go-Live, the customer is responsible for installing newer releases. Release notes are provided for all new versions. As of the Effective Date, system upgrades typically take approximately four(4)service hours when performed by a Tyler customer of industry standard IT capabilities. Tyler currently provides 3 to 4 releases per calendar year to customers under a current maintenance agreement with Tyler,with the early adopter release generally predating the general availability release by 1-2 months.Tyler does not subscribe to the Beta/RC/Gold release schedule. ❑ Customer will maintain primary responsibility for the scheduling of customer employees and facilities in support of project activities. ❑ Customer will provide/purchase/acquire the appropriate hardware,software and infrastructure assets to support all purchased Tyler software products in both support/testing and production environments. Standard environments include production,testing and training. ❑ Customer is responsible for proper site preparation,hardware,software and network configuration in accordance with Tyler specifications. ❑ Customer has,or will provide, access licenses and documentation of existing system to which Tyler will read,write or exchange data. ❑ Customer has,or will provide,a development/testing environment for import and interface testing as they are developed by Tyler. ❑ Tyler will provide Customer with a weekly status reports that outline the tasks completed and other project- level information,and that are generated from Tyler's PSA system.Those reports are sent from the Tyler Project Manager directly to the customer Project Manager.Tyler will also provide details regarding the upcoming tasks that need to be completed during the coming weeks,the resources needed(from customer)to complete the tasks,a current or updated version of the project plan,and a listing of any issues that may be placing the project at risk(e.g.,issues that may delay the project or jeopardize one or more of the production dates)as needed.Tyler will initiate Project Manager meetings,which will typically be held once per week, although that frequency may increase if the project is particularly busy.Go-To-Meeting calls are used if there is a need to present an item on a monitor to be reviewed by all participants. This becomes more frequent when the teams are reviewing documentation or software configurations for sign-off. ❑ Tyler personnel shall attend executive project review committee meetings(internal)as needed. In Tyler's experience,executive project review committee meetings typically occur on a quarterly basis. ❑ Out of scope deliverables will only be provided via a change order that is mutually agreed to. Change orders shall be addressed over the course of the project,if and when the need arises. . tyler 42 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 RISK / MITIGATION STRATEGY Project Schedule Risk: Impact of various factors on baseline project schedule. Mitigation: Given the fact that project schedules are working documents that change over the course of the project,Tyler will work closely with the customer to update,monitor,agree,and communicate any required changes to the project schedule. Activity Focus Risk: Minor activities consume time that should be dedicated to major activities of the project with the end result that time and/or costs overruns budget. Examples include meetings of little substance,or time spent investigating undocumented functionality or other activities not in scope. Mitigation:Project Managers for both parties must focus squarely on meeting deadlines,services,and configuration requirements of the implementation as planned and documented in the planning,assessment and definition stages. Incomplete Legacy Interface Documentation Risk: During the project,certain third party documentation will be required for such tasks as interface development and import of legacy data and others. Mitigation: Customer should insure that APIs for interfacing to other systems,and/or a customer expert that understands the legacy database,are available to Tyler. If no such documentation or customer expertise exists,the customer will be responsible for coordinating with the third-party vendor to advise Tyler,at a potential additional expense to the customer(although not necessarily from Tyler). Technology Age Risk: This risk is highly dependent on the choice of Tyler products and whether the customer is hosting any of those products. If the customer will be hosting the Tyler software,then the technology hosting that software should be robust and durable. Technology that barely meets minimum requirements today will be insufficient as the needs of the system grow. Mitigation:Tyler will assist the customer in determining optimal technology and plans to guard against pre- mature obsolescence.The customer will also complete a hardware survey,initiated by our deployment team,to confirm that the customer's hardware is sufficient for the upcoming implementation. CRITICAL SUCCESS FACTORS In order to successfully execute the services described herein,there are several critical success factors for the project that must be closely monitored. ❑ Knowledge Transfer-While Tyler cannot guarantee specific expertise for customer staff as a result of participating in the project,Tyler shall make reasonable efforts to transfer knowledge to the customer. Tyler will cooperate with the customer's efforts to track and gauge the success of the knowledge transfer process, and will offer informal assessments of the efficacy of the knowledge transfer process where Tyler has reasonable insight into customer's absorption of system knowledge. To facilitate the knowledge transfer process,customer personnel must participate in the analysis,configuration and deployment of the Tyler software in order to ensure success and to transfer knowledge across the organization.While Tyler will initially configure the EnerGov system,after completion of the production phase(Stage 7),the customer will be responsible for administering the configuration and introduction of new processes in the Tyler system. ❑ Dedicated Customer Participation—Tyler understands that customer staff members have daily %�% tyler 43 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 responsibilities that compete with the amount of time that can be dedicated to the Tyler implementation project. However,it is critical that the customer acknowledges that its staff must be actively involved throughout the entire duration of the project as defined in the Project Plan.Tyler will communicate insufficient participation in Project Status Reports. ❑ Managing Project Scope-To implement the project on time and within budget,both the customer must acknowledge the scope of the project set forth in the parties' agreement,and,for services,refined over the course of the early project Stages described in this Statement of Work. Change Orders for additional items outside the scope must be submitted in advanced and signed by project stakeholders before work can begin on those items. Likewise,reductions of the defined scope will also require a Change Order. PROJECT MANAGEMENT Tyler performs ongoing project management services throughout the implementation in order to plan and monitor execution of the project.Project Management includes the following tasks: ❑ Risk management ❑ Monitoring project budget ❑ Project Plan management using our expense and time-tracking tool/Excel ❑ Project document management using SharePoint ❑ Issue log management and escalation ❑ Status reporting ❑ Change order management ❑ Project workspace management ❑ Resource management ❑ Executive project oversight via Executive Director and Project Review Committee By mutual agreement,some project management tasks are shared between the Tyler project team and the customer Project Manager/stakeholders. Notwithstanding the foregoing,Tyler recognizes that it is to lead the project management activities, including the coordination with the customer Project Manager and his/her team. Tyler's failure to provide industry standard project management services will be addressed by the parties according to the terms of Sections C(5)and C(7). Development Tools Configuration tools(the same ones Tyler will use to implement the system)are built-into the software. The customer has full access to them,and its administrators will be trained on them. EnerGov reports are developed in Crystal Reports,so any changes to customer reports does require a licensed copy of Crystal Reports. The EnerGov system does include a Crystal Report reader, so view-only users do not require a Crystal Reports license. Tyler does not provide training on Crystal Reports. Documentation Tyler-provided documentation This Statement of Work includes the SOW Attachments identified in Appendix 2. In addition,over the course of the staged implementation lifecycle,the Tyler project team will provide stage-specific documentation in a range of formats(both editable and non-editable).Examples include: • Data Collection docs(MS Excel)for configuration • Data Mapping docs(MS Excel)for data conversion • ERDs&Data Dictionaries for IT(PDF and CHM) • API Documentation(PDF) �. tyler 44 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 • Training Documentation Templates(MS Word and MS PowerPoint) • Release Notes for Service Packs(PDF) • Other documentation as required for the specifics of the project. Customer-provided documentation A definitive list of Customer-provide documentation is not possible until all aspects of the implementation are determined, usually in the beginning stages of the project. Tyler does not expect the customer to generate documents that do not exist in the regular course of customer's business. Customer's assistance in completing the Tyler-provided forms and requests for configuration information is essential to a successful project. Documentation originated by the Customer may include: • API's for any third-party software system to which the Tyler software will interface and exchange data • Import data documentation and in a format suitable for import into the Tyler software(please see section titled Data Conversion) • Workflow documentation on the customer's current business processes • Copies of pertinent ordinances or other controlling authorities • Fee schedules • Copies of existing permits,licenses,other documents presented to the public and expected to be derived from the Tyler software . tyler 45 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 Appendix 1 Data Conversion The tasks set forth below have been identified to provide a more comprehensive overview of the conversion iterations over the project stages set forth above. Stage Task Type Task which mentions the Data Conversion Template Notes Database DCT-DB) 1 Deliver/review Deliver and review Data Conversion Template Database(DCT- (initial) DB),ERDs and usage documentation to answer questions and provide guidance to OC staff in preparation for initial data load from legacy systems. 3A Deliver Deliver populated Data Conversion Template Database (DCT-DB) 4B Deliver/review Deliver and review populated Data Conversion Template Database(DCT-DB)with EnerGov Data Services team member(s) 4B Import into Import data into EnerGov master database from populated DCT-DB EnerGov EnerGov Data Conversion Template Database(DCT-DB) Master DB(Iteration 1) 5A Populate Populate Data Conversion Template Database(DCT-DB) with latest iteration for System Acceptance Testing 5 A Import into Conduct pre-System Acceptance Testing import of data DCT-DB 4 EnerGov EnerGov from Data Conversion Template Database(DCT-DB)in Master DB(Iteration 2& master EnerGov database and deliver to Customer 3) 6 Populate Populate Data Conversion Template Database(DCT-DB) with latest iteration for User Training 6 Import into Conduct pre-User Training import of data from Data DCT-DB 4 EnerGov EnerGov Conversion Template Database(DCT-DB)to master Master DB (Iteration 4) EnerGov database and deliver to Customer 7 Populate Populate Data Conversion Template Database(DCT-DB) with latest iteration for Production 7 Import into Conduct Production import of data from Data Conversion DCT-DB 4 EnerGov EnerGov Template Database(DCT-DB)to master EnerGov Master DB(Iteration 5) database and deliver to Customer . tyler 46 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 Overall Architecture of Conversion: There are 3 SQL Se rver data hales involved in the conversion process. 1. EG Template M{this database houses the data from each legacy data source) 2. Mapping$Conversion Cade_DD{this database contains all conversion p—esses and mappingtables.This is maintained by Tyler's data conversion team.This db takes the data from EG_Tempate DB,translates it,and populates it into the EnerGov_DB. 3. EnerGov_DB(the production EnerGov RDBMS) EG Template 1(5QL server) !: Gmversion ►i 17 6..- --.A Progression of Conversion Process: Data conversion is an iterative process with most projects involving 3—4 complete passes leading up to final crrtover. With respect to timing and position within the overall SOW, conversion-related activities typically begin no later than Stage 4-Build/Build Specifications Data Review Ec Templ &dreept O¢ Data lead BA= s reactor Da Dan Lead Tenw le —Load M.M.v Ds TFm➢lore Data Load Data¢eview EG Template ® Dan Review Mappi�& CbnYefsYOn code Tming s• •. tyler 47 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 Appendix 2 SOW Attachments The attachments that follow are part of this Statement of Work: A:Work Acceptance Form B: Change Order Request Form C:EnerGov System Requirements D: Customer Roles/Skills Recommendations E: Custom Programming Request Form F: Custom Report Request Form G: Template DB Data Model and Guide H:Data Conversion Process for EnerGov Enterprise Server . tyler 48 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 . SOW Attachment A energov a tyler technologies solution Acceptance Sign Off Tyler Technologies Use Only Client ❑ Deliverable does NOT denote a payment milestone. Date Milestone ❑ This deliverable denotes a payment milestone. Amount Due: $0.00 Deliverable(s) Performed By Notes Additional Signoff Notes: ❑ I am satisfied with the work performed during this stage and approve the payment listed above (if applicable). ❑ I am NOT satisfied with the work performed during this stage. (Note: the project cannot continue to next phase until this phase is completed satisfactorily). Print Name Signature Date Customer Notes: EnerGov Enterprise Server ■�■ May 8,2015 ©2014 Tyler Technologies.All Rights Reserved. 1 1 Page DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 • SOW Attachment B '''''•Change Order Request �n e r ov r a tyler technologies solution Client: Date: Generated By: INTERNAL USE ONLY: Approved change orders should Authorized By: be routed through Tyler Finance Change Overview: Description of Change: Impact of Change: Schedule Impact: Delay of milestone & sub-tasks on Tyler Technologies Implementation Project Plan including: ------------------------ Task Name: Proposed Date Changes............................. ----------------------- _ --------------------------------------------------------------------------------------------------------------_------------------------------------------------ Cost Impact: Change Detail Credit Debit Total ----------------------- - ----------------------------- —---------------- ----------------------------------------------- ' I ' Revision No: No changes may be made to this project without the agreement of the Project Manager(s), and must be approved by the Project Director. Submit endorsed Change Order to the Tyler Technology Project Manager Date Comments Approved By Signature • •��•�� EnerGov Enterprise Server :�•,• May 8,2015 02014 Tyler Technologies.All Rights Reserved. 1 1 Page DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 . .�. ler 0 technologies 000000 ENERGOV SYSTEM REQUIREMENTS Tyler Technologies' EnerGov is designed to operate on networks and operating systems that meet certain requirements. Systems that do not meet the required specifications may not provide reliable or adequate performance, and Tyler cannot guarantee acceptable results. SITE ASSESSMENT Your site's system requirements are contingent upon several factors. Tyler uses a point system to help determine which specifications and configurations work best for your site. This document will help Tyler determine which setup is best for you. For each of the following applications that your site will use, indicate your site's quantity for each application variable. Each quantity has a pre-determined Point Value in parentheses, which is used to tabulate your "Total Point Value" below. EnerGov # Core Users ® NA (0) ® 1 - 25 Concurrent Core Users (4) ® 25 - 50 Concurrent Core Users (7) ®50 - 100 Concurrent Core Users (I I) 0100 + Concurrent Core Users (16) Citizen Portal Citizen Portal Option ®NA (0) ®Citizen Web Portal (2) Total Point Value EnerGov Solution System Requirements DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 SERVER SPECIFICATIONS For the following table, use your Total Point Value from the previous Site Assessment to determine which specifications are required for your site's business needs. ■ The single server configuration is denoted as "Single". ■ Multi-server configurations are broken into Application Server(AS), Data base Server(DB), and Web Server(Web) requirements. � r • � Specifications TOTAL POINT VALUE 1-6 7-10 11-15 15+ Single AS DB Web AS DB Web Processor Xeon Hex •• •• •• •• •• •• Core' Contact Tyler Memory GB RAM 16 16 32 16 32 32 32 for custom Available Bus 1—SAS 100 100 100 100 100 100 100 specifications. Disk GB GB GB GB GB GB GB Space` Bus 2—SAS 500 N/A 500 N/A N/A 750 N/A GB GB GB • One processor required; ••Two processors required. ' If running in a virtual environment,four virtual cores are needed. 2 Tyler's standard maintenance plan includes an automatic backup of your database in this disk space. 3 Entities that plan on having over 100 concurrent users should consider clustering of SQL servers. 4If using scanned documents, additional disk space is required. REQUIREMENTS CONFIGURATION DIAGRAM ........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................... Citizen Web Portal 141 ;r I Remote APP/IIs and SQL Database Computer File Servers Server Workstation Workstation EnerGov Solution System Requirements 2 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 SERVER SPECIFICATIONS 111181 , 1 Requirement Dedicated Server General Server MS Windows Certified Server' Removable Media (far backups) Gigabit Ethernet Operating System MS Windows 2008 R2 Server' System Software MS Office 2007 or 2010 and IIS Citrix Software Citrix Presentation Server Advanced (concurrent users) Database Component MS SQL Server 2008 R2 Clustered Network Environment Domain wl Active Directory Services' For OS SAS RA!D 1 Hard Drive Arrays For SQL, Transaction Logs, DB files, and SAS RAIDS or program files SAS RAID10 5 Nationally recognized brand. 6 If>32 GB of RAM,then Windows Server 2008 Enterprise. 'For larger clients, MS SQL Server 2008 R2 Standard or Enterprise may be required. ENERGOV WEB SERVER The EnerGov Web Server will host all the externally accessible EnerGov systems such as Citizen Access Portal (CAP) EnerGov IVR, eReview Portal and MobileGov Web Services. In instances where the client has users who need full access to the EnerGov .NET system, another instance of it will be hosted and accessible on this box. WORKSTATION Requirement Hardware Microsoft Windows Certified PC' Processor Pentium Core 2 Duo Memory 4 GB RAM Disk Space 10 GB available disk space Operating System Windows XP Professional or Windows 7 Professional' Network Gigabit Ethernet Network Environment Workstation is a member of the Domains Nationally recognized brand 'Windows 95J981ME, XP Home, and Vista Home editions and workgroup or peer-to-peer networks are not supported. "Tyler's servers and workstations must authenticate with and be members of a Microsoft Active Directory network. Workgroup and peer-to-peer networks are not supported. EnerGov Solution System Requirements 3 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 BROWSER COMPATIBILITY • I E 7+12 • Chrome12 • Flrefox12 • Safari 12 These browsers are tested regularly for compatibility;the others are not tested regularly but are supported. Tyler recommends the Silverlight Plug-in. MOBILE APPLICATIONS EnerGov's MobileGov Solution is capable of running on Tablet PCs, Laptops or Windows Mobile Smartphone. It is highly recommended that these devices be suitable for"feld use" (i.e. ruggedized). If Wi-Fi or reliable AirCard signal is readily available, users are also capable of running the full EnerGov.NET application in the field (Laptops and Tablet PCs only).Additionally,field printing systems are recommended for on-the-spot printing of NOVs,failed inspection notices and other relevant documents in the field. It is best suited that these field units communicate via Bluetooth for simple wireless functionality in the field. Device Type Recommended ■ Panasonic Toughbook 30 Laptop ■ AirCard or Gobi Mobiel Broadband (or readily available Wi-Fi ■ HP ❑fficejet H470 Mobile Printer ■ Panasonic Toughbook H1 Field Tablet PC Gobi Mobile Broadband (or readily available Wi-Fi) ■ Zebra Technologies RW420 Mobile Printer ■ iPad2 or higher Wad3G or wifi capability Smartphone ■ Windows Mobile 7 OS (preferred) ■ Zebra Technologies RW420 Mobile Printer Scanner Compatibility Scanner Brand Scanner Mode Canon 0 DR-M 140 ■ DR-M 160 Fujitsu ■ Fi-614OZ ■ Fi-6240Z ■ Fi-623OZ E Fi-6130Z 14TWAIN compatible scanners are supported. EnerGov Solution System Requirements 4 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 RECOMMENDED BACKUP PROCEDURES Developing a consistent backup strategy is a vital part of any organization's business continuity plan.A good backup plan ensures that you do not lose the hard work and time you invested in data entry if a hardware failure or natural disaster occurs.A plan such as this is easy to develop and usually easy to implement.This section outlines the steps you should take to properly back up your data. Assessing Your Backup Needs Backups occur differently,depending on the size of the database being used. The differences directly impact how quickly you can resolve problems and how much effort you must expend. Tyler recommends that you implement a backup plan based on the point values determined in your initial Site Assessment. Rotating Tapes First,establish a good tape rotation for your backups.Tyler recommends that you use,at a minimum,the following 6-tape rotation: M T W Th F1 ITTM M T W Th F2 This rotation is sufficient for most customers because you can go back a few business days to find files. However, if you feel you need a little more protection,you can use a different set of tapes for Mon-Thurs of Week 2,and/or you can keep a Fri 3 and Fri 4 tape so that you have a month's worth of Friday backups.We also recommend that you periodically(monthly,quarterly,etc.) pull a tape permanently out of rotation to store off site Backing up Your SQL Database For EnerGov,the default databases should consist of at least FY databases, Base,Sec and State database. There are a few different methods for backing up your SQL database. • SQL Backup Function:The Microsoft SQL Server 2008 R2 Management Studio has built-in backup tools that can cause SQL to dump the EnerGov database to a backup file in the SQL default backup folder while the SQL services are running.This location is: C:IProgram FilesiMicrosoft SQL ServeriMSSQLISackvpI • Third-Party Backup Agent: This method requires that you have some sort of third-party backup program (e.g., Symantec Backup Exec, Brightstor ARC Serve, etc.) which uses a SQL backup agent. These special backup agents allow the Microsoft SQL databases to be backed up while they are online. • The Microsoft SQL Server installation path may vary slightly per installation. EnerGov Solution System Requirements 5 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 Other Directories in EnerGov Even though program files and run times can be replaced by Tyler,Tyler strongly recommends that you back up the entire C:\Web and/or C:\iVisions folder be backed up on the web server. Watching for Signs of Failure Monitor your backup status every morning. If there is a noticeable problem,such as an error light blinking on your tape drive, a tape being ejected without your knowledge,or an error message displaying about your backup, please contact us or your IT staff so that the problem can be resolved quickly. Accepting Responsibility Having good backups of EnerGov data is your responsibility. However,Tyler Technologies offers additional services that can help monitor your local backups,transmit your data to off-site locations,and even provide access to your EnerGov software and data over the Internet in case of disaster or serious equipment failure at your site. Disaster Recovery In case of system failure due to unforeseen disaster,Tyler recommends that you have a Business Continuity Plan, which should include a disaster recovery service.Tyler offers a disaster recovery service for an additional fee. If you haven't already purchased this plan,contact Technical Services or Sales at 1-888-654-3293 for more information. EnerGov Solution System Requirements 6 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 SOW Attachment D �iCustomer Roles/Skills Recommendations tyler • l±chnolo Ern pmering people who smw the public• Project Collaboration A successful Tyler enterprise implementation is a collaborative endeavor in which both Tyler Project Team members and agency personnel occupy specific roles (and the responsibilities associated therewith). While definitive client-side roles and skills may vary from project to project (depending on the agency's resource availability)the following designations represent the typical and recommended resource involvement for most agencies. Project Stakeholder Committee: This committee is formed by executive or managerial staff of every effected business group to be implemented. Typical individuals Include a committee of the following: CIO / Community Development Director/ Finance Director/ CBO/Planning Director/Public Works Director etc... Responsibilities include: • Ensure proper change management and leadership to departmental staff. • Determine beneficial process change through automation as it is presented cross-departmentally. • Monitor project from high level. Project Manager: This role is typically a non-business group member(IT or support staff)of the agency's project team. Typical positions: IT or applications support project manager Responsibilities include: • Serve as coordinator of the agency's Implementation team/subject matter experts. • Assist in managing the project scope, deliverables and timeline with assistance from the Tyler Project Manager. • Ensure that the project team stays focused,tasks are completed on schedule, and that the project stays on track. • Develop and maintain the project resource plan in conjunction with the Tyler Project Manager. • Schedule and coordinate project tasks with assistance from the Tyler Project Manager. • Coordinate agency's Implementation team resources with all departments. • Participate in daily project activities and track progress on project tasks. • Hold meetings with project stakeholders to update on project status and to reach verdict on any escalated process decisions that need to be made. • High-level oversight throughout the stages of the project; ROI initiatives oversight. Desired Skills/Experience: • Previous project management experience as project manager • Strong IT technical background • Bachelor's Degree in Computer Science or equivalent experience • Experienced with an iterative-based development approach • SharePoint& Microsoft Project experience a plus • Excellent knowledge of Customer Business Practices and Processes ©2013 Tyler Technologies. All Rights Reserved Confidential Information Page 1 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 a tyler Customer Roles/Skills Recommendations l±cr,nolo Project Sponsor: Ern powerfng people who serve the public• This role is typically an executive or managerial sponsor of either the IT group or a dominate business group that is ultimately responsible for the success of the project. Typical positions: IT Director/Department or Division Director Responsibilities include: • Ultimate responsibility for the success of the project; serves as project champion. • Creating an positive environment that promotes project buy-in. • Driving the project through all levels of the agency. • High-level oversight throughout the stages of the project; ROI initiatives oversight. Departmental System Administrators: A user representative for each affected department is typically appointed for the entire lifecycle of the implementation and to serve as ongoing configuration support or"Systems Administrator" post the production phase of the EnerGov system. Typical positions: Departmental or division subject matter expert and typically a direct member of the business group or of the business applications support group. Responsibilities include: • Being trained on the EnerGov.NET system at a System Administration level. • Being fully engaged in the business analysis system configuration, reviews and UAT activities. • Assist internal efforts towards the creation of reports, interfaces&conversions. • Actively participate in the full implementation of Tyler's EnerGov software solution. • Serve as ongoing departmental or division system configuration support post the production phase of the project Desired Skills/Experience: • Proficient in Crystal Reports • Analytical/Problem Solving Skills • Experience with other"configurable"enterprise applications such as PeopleSoft, SAP, etc. Departmental Business Leads: A user representative for each affected department must be appointed for the entire lifecycle of the implementation. Assigning competent business leads to assist in the project is highly recommended and can often determine the success of the implementation for their respective areas. These Business Leads are typically transitioned into Tyler "Power Users". Typical positions: Departmental or division "power user"and member of the business group. Responsibilities include: • Attending assessment workshop sessions. • Willing and able to gather data and make decisions about business processes. • Assist as a knowledge-base in the creation of specifications for reports, interfaces&conversions. • Review and test the system configuration. ©2013 Tyler Technologies. All Rights Reserved Confidential Information Page 2 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 a tyler Customer Roles/Skills Recommendations l±cr,no.o Technical Lead: Ern powering people who serve th a public• A technical individual from the Information technology group that is responsible for the technical infrastructure support of the implementation and to serve as ongoing technical infrastructure support post the production phase of the EnerGov software system. Typical positions: Network/IT Administrator Responsibilities include: • Primary responsibility for the technical environment during the software implementation • Ensure that servers, databases, network, desktops, printers, are available for system implementation and meet minimum standards • Work with Tyler's technical personnel during implementation • Maintain the testing and production databases • Install software updates and releases • Act as the primary technical resource for troubleshooting technical problems • Establish and maintain backup, archival, and other maintenance activities ©2013 Tyler Technologies. All Rights Reserved Confidential Information Page 3 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 0 SOW Attachment E tyler Custom Programming Request Form • tEchno;ogies EMpowerirtg people who serue the public' Client: Date of Request: Contact Name: Expiration Date: (Quote is valid for 30 days) Feature Request [Short Narrative Here] Option 1 — [Custom Programming Item Name], [Hour Estimate] [Details here] Tyler Technologies Use Only (Custom programming fees are calculated using a$10,000 impact fee plus an hourly development fee) Impact Fee: Development Hours: 0 Development($249/hr.): $0 Estimated Release Date: See Dates Below Implementation Cost: $0 Estimated Release Version: see Dates Below Training Cost: $0 Documentation Cost: $0 Yearly Support/Maintenance (18% of Development cost): $0 R&D Authorization: Sales Rep Authorization: Total Cost: $0 Authorized: Property of Tyler Technologies Professional Services May 8,2015 2013 Tyler Technologies.All Rights Reserved. 11 Page DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 0 SOW Attachment E tyler Custom Programming Request Form • techno;ogies Empowering people who nerve the public" Release Schedule Release Schedule Estimated Date [EnerGov Software Beta Release date] DATE [EnerGov Software RC Release date] DATE [EnerGov Software Gold Release date] DATE *Release dates are subject to change Accepted and Ordered by Customer: Please sign,date and return by fax: Signature: Tyler Technologies,Inc. Name (print): Phone: 888-355-1093 Title: Fax: 678-474-1002 Date: sales@energov.com Payment Schedule Milestone/Due Date Amount Description Order Placement $0 75% due upon order placement Order Delivery $0 25% due upon order delivery Payment Schedule (Support/Maintenance) Due Date Amount Description January 1 of every year $0.00 1st quarter Support/Maintenance April 1 of every year $0.00 2nd quarter Support/Maintenance July 1 of every year $0.00 3rd quarter Support/Maintenance October 1 of every year $0.00 4th quarter Support/Maintenance * Support and Maintenance amounts listed above will be added to your regular support and maintenance fees. Property of Tyler Technologies Professional Services May 8,2015 2013 Tyler Technologies.All Rights Reserved. 2 1 Page DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 SOW Attachment F Instructions • ••• Fill out this form as completely and with as much detail as possible. Please attach any sample reports or other supporting documentation and be sure to save a copy for your t ler�iM• records. The more detail provided,the better the report designer can develop the report �• technologies without additional follow-up. Not all items will apply to each report;you need only complete those items that are relevant to the request. Exceptions to these requirements Report Request Form may be noted under Additional Details. To save time for a large number of similar report EnerGov Custom Re n requests,save basic information as a template. Client Name: Report Requestor/Point of Contact: Request Date EnerGov Module Requested ❑ Impact Management ❑ Project Management ❑Application Management ❑ inspection Management ❑ Rental Prop Management Completion Date: ❑ Business License ❑ Object Management ❑ Request Management ❑ Cashier ❑ Permit Management ❑ ❑ 1 ❑ 2 ❑ 3 ❑Tax Remittance Management Priority(1=High, ]4❑ 5 Low): ❑ Code Management ❑ Plan Management ❑System ❑ Contact Management ❑ Professional License ❑ Other Report Name: Report Type: El Report El Document Report Description/Business Need: Request Type: ❑ New ❑ Modification Based On Or Similar To Existing Standard or Custom Report: Report Target: ❑ Client ❑ Customer ❑ EnerGov Format Design: Report Style: ❑ Replicate Sample Exactly OR ❑ Listing ❑ Letter ❑ Free Form ❑ Certificate ❑ Dashboard Report Orientation: Report Output: Paper Type: ❑ Portrait ❑ Landscape ❑ Print/PDF ❑ Excel/CSV ❑ Letter ❑ Legal ❑ Ledger ❑ Printed Form ❑ Other Include Print Date/Time: Include Page Numbers: Date/Time Formats: ❑Time ❑ Header ❑ Left ❑ Page N ❑ Header ❑ Left ❑ MM/DD/YYYY ❑ HH:MM ?M ❑ Date ❑ Footer ❑ Center ❑ Page N of M ❑ Footer ❑ Center ❑ M/D/YY ❑ HH:MM ?m ❑ Right ❑ Right ❑ M M M D,YYYY ❑ H:MM ?M Default Font Information(Times New Roman, 10 point, Black if not specified): El MMM,YYYY ❑ H:MM ?m❑ DD/MM/YY ❑ HH:MM Font Name: Font Size: Font Color: Black or ❑ MM/DD/YY ❑ HHMM (24) Technical Design: Identify Attached Specification/Sample Documents(XLS, DOC,PDF,etc.): Primary SQL Stored Procedure(for existing reports) : EnerGov Parameter: ❑ Date Range ❑ Module ID ❑ Other Record Selection Inclusion/Exclusion Filter Or Parameters(please put additional filters in the Notes For Developer): Filter#1: Filter#2: Filter#3: Parameter: ❑ User ❑Static ❑ Dynamic Parameter: ❑ User ❑Static ❑ Dynamic Parameter: ❑ User ❑Static ❑ Dynamic How Report Data Is To Be Sorted or Grouped (please put additional sort/groupings in the Notes For Developer): Primary Sort: Secondary Sort: Tertiary Sort: ❑Group ❑Group ❑ Group Copyright©2014 Tyler Technologies EnerGov Custom Crystal Reports Request Form 20140311 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 Additional Details Notes For Developer: CIA Instructions/Test Case Scenarios: Client Services Notes: Client Notes: Approvals Ready To Develop Checklist ❑ All static and data elements have been identified in the report specification ❑ All formatting requirements have been identified in the report specification ❑ Indicate in the report specification whether to list one address type,all address types,or prioritization of address types ❑ Indicate in the report specification whether to list one contact type,all contact types or prioritization of contact types ❑ Indicate in the report specification whether to list one phone number,all phone numbers or prioritization of phone numbers ❑ All custom fields have been created in the client database ❑ All custom fields have been configured on appropriate Additional Info dialogs ❑ All record types,classes,statuses,etc.necessary to the report have been configured ❑ All fees and fee templates necessary to the report have been configured ❑ All address types necessary to the report have been configured ❑ All contact types necessary to the report have been configured ❑ All objects,impact conditions,certifications,and other elements necessary to the report have been configured ❑ All workflow steps and actions necessary to the report have been configured ❑ All support data(Bonds,Hearings, Parcels,Tasks, Users,Zones,etc.)necessary to the report have been configured ❑ Client has approved custom report request specification Specification Report Developer Specification Date Estimated Initial Dev/QA Hours Estimated Initial Dev/QA Cost Client Services Representative Submitted Date Billable Type: ❑ Contracted ❑ Purchase Order Client Approval I agree that the above and associated documents accurately reflect the requirements for this Custom Report Request. Client Name Client Signature Date Copyright©2014 Tyler Technologies EnerGov Custom Crystal Reports Request Form 20140311 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 Understanding the EnerGov . . . ler 0* TM technologies Custom Report Request Form The following describes each item on the EnerGov Custom Report Form: General Information ❖ Client Name—Name of the project client. ❖ Report Requestor/Point of Contact—Name of original customer or Tyler source of report requirements. ❖ Request Date—The date the request form is filled out. ❖ EnerGov Module—Check the box for the module for which the report is being developed. ❖ Requested Completion Date—The date the report has been promised to the customer. ❖ Priority—The importance of the report to the client(high priorities will be completed first). ❖ Report Name—The name the report is to be called (will be used for the RPT and SQL file names). ❖ Report Type—Whether the report is a batch-style report or single case document. ❖ Report Description/Business Need-Describe the purpose or use of the report. ❖ Request Type—Whether request is based on,or modification to,an existing report or a new report. ❖ Based On Or Similar To Existing Standard or Custom Report—Identify an existing report that should be used as a starting point for further development. ❖ Report Target—Indicate if this report is for EnerGov use, internal Client use, or will be delivered to end Customers. Format Design ❖ Report Style—Whether the report style is a listing format(table), Letter(to be mailed), Form(completed or to be filled out),Certificate(such as license or permit), Dashboard (summary analysis of data)or Exact(identical to the sample report). ❖ Report Orientation—Whether the report page orientation is Portrait or Landscape. ❖ Report Output—Whether report is intended to be read (Print/PDF) or exported (Excel/CSV). ❖ Paper Type—Select the type of paper the report will be printed on (letter, legal, ledger, pre-printed form, or other paper size). If selecting other, please identify in Additional Notes. ❖ Include Print Date/Time—Select whether to include the print date and/or time in the report header/footer and to justify it center, left or right. ❖ Include Page Numbers—Select whether to include Page Number and or Page Total in the report header/footer and to justify it center, left or right. ❖ Date/Time Formats—Select the default style of date and time to be used in the report. ❖ Default Font Information—If the default font size, style and color not specified:Times New Roman, 10pt, Black. Technical Design ❖ Identify Attached Specification/Sample Documents-List the file names of additional requirements specifications or sample documents. ❖ Primary SQL Stored Procedure—The name of any existing stored procedure to be used for the report. ❖ EnerGov Parameter—Indicate if the key report parameter is a date range, an EnerGov Module ID or other field. ❖ Record Selection Inclusion/Exclusion Filter Or Parameters—List any filters to include or exclude records, in addition to any EnerGov Parameter,that should be applied to the data record selection or SQL Stored Procedure. If the filter is to be a user-prompted parameter, indicate whether the user will enter a value,select from a list of static values,or select from a dynamic list of values. If more than three, please list in Notes For Developer. ❖ How The Report Is To Be Sorted or Grouped—List any primary,secondary or tertiary sorting. Note if the report should be grouped by the sort value. If any group summary totals and/or if more than three sort/group levels are required, please list in Notes For Developer. Additional Details ❖ Notes for Developer—Any additional information that will aid in the design and development of the report. ❖ CIA Instructions/Test Case Scenarios—Special testing information to facilitate report testing and validation. ❖ Client Services Notes—Any additional comments about the report for the Implementation Team. ❖ Client Notes—Any additional comments about the report for the client. Copyright©2014 Tyler Technologies EnerGov Custom Crystal Reports Request Form 20140311 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 Approval ❖ Ready To Develop Checklist—List of items for Implementation to make sure are complete before submitting the Report Request. o All static and data elements have been identified in the report specification o All formatting requirements have been identified in the report specification o Indicate in the report specification whether to list one address type,all address types,or prioritization of address types o Indicate in the report specification whether to list one contact type,all contact types or prioritization of contact types o Indicate in the report specification whether to list one phone number, all phone numbers or prioritization of phone numbers o All custom fields have been created in the client database o All custom fields have been configured on appropriate Additional Info dialogs o All record types,classes, statuses,etc. necessary to the report have been configured o All fees and fee templates necessary to the report have been configured o All address types necessary to the report have been configured o All contact types necessary to the report have been configured o All objects, impact conditions,certifications, and other elements necessary to the report have been configured o All workflow steps and actions necessary to the report have been configured o All support data (Bonds, Hearings, Parcels,Tasks, Users,Zones,etc.) necessary to the report have been configured o Client has approved custom report request specification ❖ Specification Report Developer—The name of the Report Developer assisting in the requirements gathering and report specification. ❖ Specification Date—The date the specification was completed. ❖ Estimated Initial Development/QA Hours—The number of hours expected for initial report development and CIA. Revisions and subsequent changes to the specification may require additional hours. ❖ Estimated Initial Development/QA Cost—The expected billable cost for initial report development and CIA. Revisions and subsequent changes to the specification may lead to additional billable costs. ❖ Client Services Representative—The name of the Client Services Representative working with the client. ❖ Submitted Date—The date the approved Custom Report Request is submitted to the Report Development Team. ❖ Billable Type—Whether this report is part of a contracted set of development hours,or will be billed against a client purchase order. ❖ Client Approval—Authorization by the client verifying that the report requirements are correct. Copyright©2014 Tyler Technologies EnerGov Custom Crystal Reports Request Form 20140311 DocuSign Envelope ID: 1CCA18DC-6CC1-428C-A15D-5173EE24B471 0 SOW Attachment G o Cn Data Conversion for EnerGov Enterprise Server Sa m m Template DB Data Model and Guide CD 00 0 W n O The tables in the EG_Template db are grouped together and named such that they correspond closely with the structure of the EnerGov core 44 product, which is broken out into different units/modules. Below, each module will contain a listing of the tables, a brief description, and an ERD diagram. All of these ERD diagrams are present within the EG_Template db (under the Database Diagrams folder in SQL Server). Cn TI W O O Cn O n J W N J 00 00 DocuSign Envelope ID: 1CCA18DC-6CC1-428C-A15D-5173EE24B471 0 0 c Cn cn m Contact Repository: CD 0 m contact 00 This contains the master list of contacts to convert. Duplicates should be kept to a minimum. The goal would be to have one contact record for each actual 0 person or company. Every module within EnerGov will utilize this same contact master table for its case contacts. CO Ip contact address J V The various addresses associated to the contact. Address type is available to distinguish different addresses (mailing, location, billing, etc.). T N TI contact certification W This is used to hold certifications or licenses that are desired for historical purposes, but are not being managed in EnerGov with Professional Licensing or Ip Business Licensing. n J W N J M contact 00 QI contact id contact—address company—name contact id first_narre address,-type midd le_narre street_n un ber last_na rre pre_d iredion is—company street_narre is individual street—type erreil post_direction contact_certificatian webstte unit suite ru n ber contact id Jcertification—type business phone address_line_3 home phone city J li�nse_nurrber J rmbile_phone state_code issued date other—phone zip notes expiration_date fax country_a3de notes title last_update_date last—update—date _ last_update_user last_update_user eg_mailing address_id gnore_remrd Legacy_data—source_name DocuSign Envelope ID: 1CCA18DC-6CC1-428C-A15D-5173EE24B471 0 0 Cn Professional Licensing: Ba m contact CD 0 See Contact Repository. CD 0 00 professional license 0 M Usually a license related to an individual or contractor of some sort. n Ip professional license note J J Simply a place for logging memos on the license. N TI professional license additional fields Cn 00 Add any other fields which are not provided in the template model. U1 n J W contact J �J contact id professiona!_license °' 1 company name _ Q contact—id first name license—number 4� professional license note Jmiddle name I license_type �dJ contact id last_n J license_suh_type J license—number is compapz ny J license—status ' note text Jindividual I apply date note user Jemail J J website issue_chte note date J expire date business—phone I license des cdption Jhome—phone J by issued_ _user J mcbile—phone J lost_update_date professional f Jother hone last_update_user J contact id Jfax J license year J license—number title ignare_recard J last_update_date legacy data source name Jlast_update_user Jignore_record Jlegacy_data_sour ce_name DocuSign Envelope ID: 1CCA18DC-6CC1-428C-A15D-5173EE24B471 0 0 c Business Licensing: to m contact-See Contact Repository. CD 0 m Business-The business table relates 1-to-1 with the contact table.This table simply holds extra attributes of the contact, and allows the contact to interact with 00 the business license module of EnerGov as a business entity. 0 W n business parcel - For integration with GIS, simply provide the parcel number(or PID) of the business location. J n V business contact - For business contacts that link up to the master contact repository. T N TI business contact no key- For contacts that are not part of the master contact repository. These are usually stored as attributes of the business record in the on legacy db (Applicant, Owner, Manager, President, etc.). Cn M business inspection - For routine inspections associated to business licenses. w N J business license- Holds licenses related to a company. 00 business license note -Simply a place for logging memos on the license. business license additional fields-Add any other fields which are not provided in the template model (at the license level). contact business__pa rcel a contact_id business contact_A compar -me `6� contoot_id parcel_number business—license business—license—note f rst_name I ou rship_type 3 contact_id I ccntact_id J middle_name I Iceatim ai _type mn p a license number 1 license number Jlast_name , husiness_status license type J note text lcmpany o l distric ice sub type l note user is_individual J open_date l J Hari note_date small business contact apply—date business desorption J —bsite J contact_id issue_date closed date I Jhusin shone l federal_id_num6er contact_type J expire date Jcontact name home—phone � state id number J license_description J mobile—phone l dha I address_line_i issued by user business_license_additional_fields J other—phone I I address_line_2 J last_update_date contact_id _r ignoreecord J fax I address_line_3 I egary_data_source_name I last_update_user license_number title JI prone-1 licenseyear last_update_date J Phu.2 Ignore_rscord last_update_user J email legary_data_source_name Ignore_record contactnare business_contact le gacy_data_source_name aj contact_id_of_husiness dJ ccntact_id J contacu_type business_inspection J d primary_hilll n�contact [;_c�—umher DocuSign Envelope ID: 1CCA18DC-6CC1-428C-A15D-5173EE24B471 0 0 Cn Code Enforcement: m m code case—Self-explanatory. a 0 code case address o The various addresses associated to the case. Address type is available to distinguish different addresses (location, owner, etc.). W 1P code parcel - For integration with GIS, simply provide the parcel number(or PID) of the case location. V TI A code case contact - For case contacts that link up to the master contact repository. Cn 00 code contact no key- For contacts that are not part of the master contact repository. These are usually stored as attributes of the case record in the legacy db o (Complainant, Owner,Tenant, etc.). n J code inspection - For inspections associated to code cases. 00 00 code case history log—If history of updates to the case are really needed, they can be logged here. code case note-Simply a place for logging memos on the case. code case additional fields -Add any other fields which are not provided in the template model (at the case level). code case violation—Violations associated to the case. These usually reference city/county code numbers. code case activity—A place to log various events that have occurred against the case. DocuSign Envelope ID: 1CCA18DC-6CC1-428C-A15D-5173EE24B471 0 0 0 c code—case—contact code—case—additional fields J casenumber m code—case—address — :3 case number J case_numbe J contact id m 0 main address J contact type m address type primary_billing_contact p 0 street number 0) pre_direction W n street name code—case—contact_no_key ;° code case J case number v street type _l case_numher contact type v post direction Ti ca.type J contact name code—case—violation unit_suite_number Jcase N CO case_sub ber _type �7 address_line_3 address_line_i violation code W city J case status en address_line_2 district I I violation status O state code J address_line_3 J o� op.date vidation-]xiarity zip J re_1 m case description I phone 2 J violation note W country code J dosed date J J corrective_action_memo V J email last_update_date m assigned_to_user � contact note citation date OD Jcreated-by-user compliance date eg_mailingaddress_id last_update_date � resolved date Jlast_update_user ignore record code—case—activity IN Jlegacy_data_scurce_name I case_number code—case parcel O° activity-type J case number J J activity number parcel-number activity_com merit Jmalnparcel code—inspection � activity user code_case_history_log code case L-- _bei J activi ty date cas_number _ _ number ignore_record - c _num ber created date ase note text created by user note user J history_type_name note date old value Jnew value history notes DocuSign Envelope ID: 1CCA18DC-6CC1-428C-A15D-5173EE24B471 0 0 Cn Permits: m permit—Self-explanatory. There is a parent-child relationship available within this table (for sub-permits). CD 0 CD permit address The various addresses associated to the permit. Address type is available to distinguish different addresses. W n permit parcel - For integration with GIS, simply provide the parcel number (or PID) of the permit location. J n J permit contact - For case contacts that link up to the master contact repository. N TI permit contact no key- For contacts that are not part of the master contact repository. These are usually stored as attributes of the permit record in the Cn legacy db (Applicant, Owner, Contractor, etc.). permit inspection - For inspections associated to permits. w N J Permit history log—If history of updates to the permit are really needed,they can be logged here. 00 permit note-Simply a place for logging memos on the permit. permit additional fields-Add any other fields which are not provided in the template model (at the permit level). permit activity—A place to log various events that have occurred against the permit. permit hold—For instances where a stop work, or a hold was/is issued against a permit. permit zone—Simply provides a place to link zones to a permit. This is available, but is usually not used (custom fields are usually setup in EnerGov to hold zone codes of various types). permit fee—Simply shown for reference here. Also see the Financial Tables section. DocuSign Envelope ID: 1CCA18DC-6CC1-428C-A15D-5173EE24B471 0 0 0 c permit address permit_pa reel permit_m ri ben m permit contact_na_key J permit number I main-address N Jpermit number J parcel number I address type 0 J �contact t _ype main�arcel I street_numher CD J contact name J 00 pre direction 00 Jaddress line_i street name w Jaddress line 2 J street type n J address line_3 permit J post direction 10 J phone_1 J unit_suite_number Ti 4, permit number v Jphone 2 permit type J address line 3 email I permit hold N J permit sub type I city contact-note permit number _n permit status hold type en W J district O hold user J apply date permit contact J Hold date cn J J permit_description permit_note LaEtive n permit number end date v CC permit number issue-date ommentcontactid - J note text expire datecontacttype flag Jfinal date note user primary_billing_contact last update date J note date OD Jlast update user last—Inspection—date permit—additional—fields permit_history_log J parentnermit number J permit number Jpermit number valuation Jcreated date J square_footage Jcreated_br_user ignore record J history_type_name le J permit activity permit-number new value J activity-type J new v history_notes activity number permit_inspection J a ctivity_comment J permit zone 4 permit number `] activity user Q permit number inspection number activity-date J zone_code ignore_recad permit—fee J primary zone permit_fee_id Jpermit-number fee type Jfee amount fee date Jcreated-by-user Jinput_yalue DocuSign Envelope ID: 1CCA18DC-6CC1-428C-A15D-5173EE24B471 0 0 Cn Plans: m plan case—Self-explanatory. CD 0 CD plan address The various addresses associated to the case. Address type is available to distinguish different addresses. W n plan parcel - For integration with GIS, simply provide the parcel number(or PID) of the plan location. Where multiple parcels are on a case, one should be designated as the main parcel. n plan contact - For case contacts that link up to the master contact repository. Cn 00 plan contact no key- For contacts that are not part of the master contact repository. These are usually stored as attributes of the case record in the legacy db (Applicant, Owner, Contractor, etc.). Cn n J W plan inspection - For inspections associated to cases. 4 00 plan history log—If history of updates to the case are really needed,they can be logged here. plan note-Simply a place for logging memos on the case. plan additional fields-Add any other fields which are not provided in the template model (at the case level). plan activity—A place to log various events that have occurred against the case. For conversions, reviews would likely go here. plan hold— For instances where a stop work, or a hold was/is issued against a case. plan zone—Simply provides a place to link zones to a case. This is available, but is usually not used (custom fields are usually setup in EnerGov to hold zone codes of various types). plan fee—Simply shown for reference here. Also see the Financial Tables section. DocuSign Envelope ID: 1CCA18DC-6CC1-428C-A15D-5173EE24B471 0 0 0 c plan address T J plan number m main_address � < CD Jaddress 0 plan_contact_n0_key Plan _0 �arcel J street number CD plain number J plan number p JJ J pre_drection contact type J parcel number 0 street name � J contact name main—par cel W street type T J address_line,_1 I � post_direction J address_line,_2 1P J unit_site number v Jaddress_line_3 J address_line_3 V J phone-1 plan- case J city stat J phone-2 plan number N J e_code n J email I plan type Go J zip CIl J contact note I plain sub—type J O _ country code Jplan status J last_update_date J apply date n Iast_update_user TI_ J e�ipired_date plan hold N Jcompleted date J plan number pian_contact J assigned to I hold—type OD Jplan—number J completed plan—note hold user Jcontact id J district J plan number I hold date contact_type J last_update_user J note tent Il hold_end_date primary_billing contact J last_update_date J note_user K I Jplan_description J note date Japproval_eore_date plan—history—log J plan-status-change-date plan—additional—fields J plan number J value plan_numher j Jcreated date J squa-e_foctage created_by user J ignore_record history_type_name I—data tour plan_actil J old value T, J plan number Jnow value J activity type histuy_notes J activity—number plan—inspection plan—zone J activity-comment plan fee J plan number A plan number J activity user _ M J Jinspection—number A zoneode activity date plan_fee_id 4 _c plan number J primary zone i--record fee type fee amount Jfee—date Jcreated_by_user Jinput—value Jeg_feed Jfee note DocuSign Envelope ID: 1CCA18DC-6CC1-428C-A15D-5173EE24B471 0 0 Cn Inspections: m inspection—This holds the details of each inspection occurrence. Each inspection should be linked to the case that it relates to by using the cross reference CID 0 tables below. CID 0 CO plan inspection - For inspections associated to plan cases. 0 Cip n permit inspection - For inspections associated to permits. 1P J TI V code inspection - For inspections associated to code cases. N TI business inspection - For inspections associated to businesses. Cn 0 inspection note-Simply a place for logging memos on the inspection. Cn n J 03 inspection checklist item—These can be used for categorized checklist info,violations, etc. 4 00 00 inspection—checklist—Rem Inspection J inspection number QI lnspectim number checklist item inspection type J rptes inspection stairs passed create date inspedion_note irspectim_number requested for_date pte text Jscheduled fa_date rpte user attempt number J _ pte_date completed Jlast update_date Jlast update_user Jegirspectim_id Jinspector J i gna-e_record permit—inspection business—inspection plan—inspection code—inspection JQI permit number al cartact id plan number case number irspected_date_start Jinspected_date_end J inspectim_number Lt mber lnspecban_number irspecbon_number DocuSign Envelope ID: 1CCA18DC-6CC1-428C-A15D-5173EE24B471 0 0 0 c Cn Financial Tables: m permit fee—Holds the details for fees associated to permits. CID 0 -a CID plan fee—Holds the details for fees associated to plans. CO 0 payment—Records representing funds received. n 1P payment reversal—Records representing funds going back to a customer(or voided). The types of transactions here would likely be voids, NSFs, and refunds. These should be linked back to the original payment record that they are reversing. N TI permit payment detail—records the amount applied to each individual fee (line item)within a payment. Cri 0 plan payment detail—records the amount applied to each individual fee (line item)within a payment. n J 03 permit payment reversal detail—records the amount applied to each individual fee (line item) within a reversal. 4 CO CO plan payment reversal detail—records the amount applied to each individual fee (line item)within a reversal. payment permit_payment_detail 4 payment_id plan—payment_detail plan—fee rmit fee permit fee_id — `dl receipt—number J plan_fee_id C6Ian fee id � permit_fee_id <dI payment_id I plan_nimber per payment_method �I payment_id permit number paid amount fee type J J check—number � paid_amount fee_type Jpayment amourt J fee amount fee_amwnt J payment_date J fee date Jfee date created by user J created_by_user created_try_user Jinprt_va'ue � eg-transaction_id J input_value J egfee_id payment—rite J eg_fee_id Jfee—note fee note perm lit—pa yment_reversal_detail plan—payment—reversal—detail ,,I permit fee_id payment_reve real plan fee_id J payment_reversal_id QI payment_reversal_id 4 payment_reversal ld 4� J reversal type reversed amount J reversed_amwnt Jreceipt—number Jreversal_amount reversal date Jcreated_by user Jpayment_id Jeg-transaction ld reversal_ncte DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 SOW Attachment H Data Conversion Process for EnerGov Enterprise Server (Template DB Option) Overview: This document is an intro to the SQL Server EG_Template database and how to populate it. Modularized Design: As with the EnerGov software,the EG_Template db is sectioned off into modules. Each contains one master table at the top of the chain (ex. 'permit' for the Permit module). Within each module,there will be various child tables branching out below the master table for that module (ex. 'permit_address', 'permit_note', etc.). There are tables that cross multiple modules. The most notable of these involve inspections and payment transactions. Database diagrams have been included in the EG_Template database. These show the tables and their relationships for each module. Required Fields: There are certain fields in the EnerGov software which are required fields, and we cannot write records to the EnerGov db without populating these columns. Sometimes,these required fields will not be available in the legacy source data, so a simple default value can be written to the EG_Template db to fulfill any NOT NULL constraint. Some of these fields are drop-down lists in EnerGov,which means that we will be restricted in the values that we can write to these required fields in the EnerGov db. For drop-down fields,there is no restriction on what can be written in the EG_Template db. So, exact spelling or careful matching to the EnerGov configured values is not an issue for fields that are destined for EnerGov drop-down fields. We will run these through a separate mapping table to translate the values to the appropriate EnerGov value during conversion. These mappings will be negotiated during the development phase of the conversion. Custom Fields(any fields not available in the master table for the module in question): Most legacy systems will have some attribute fields that are not specified in the corresponding master table within EG_Template. In EnerGov,we will refer to these as custom fields. Within each module, there will be a child table for such custom fields. Since these are specific to the legacy system(s),you may add columns to these tables in EG_Template to accommodate any needed custom fields in the migration. For example, 'permit_additional_fields' is the table for extra fields relating to the 'permit' records. Gap Handling(where legacy data doesn't fit anywhere within EG_Template): There are sometimes special features of a legacy system which EnerGov does not account for in the EG_Template db. We may have to work out a custom solution to handle these special cases. Contacts: This is always a big topic for data migrations. These generally fall into two categories: 1. Those contacts that were managed with each person/company having one contact record, which is kept up to date over time. As this person/company is associated with records over time (getting a business license, pulling permits, being associated to a code violation),that one contact record is attached to the permit, license, code case, etc. With this model,there is generally no duplication of contact records (except when created by mistake). 2. Contacts where the user keys the contact attribute info on each permit, case, license, etc. With this model, there is no single master record representing the contact itself. So, if a contact has been associated to 10 different permits overtime,there would be 10 records with the contact attributes (each one will likely have slightly different values in the various fields like name, address, phone, etc.). With this model,there is considerable duplication of contacts. DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 In the EnerGov model, contacts are stored as in category 1 above. Those contacts put into EG_Template without a master'contact' record link (category 2 above) will be migrated into custom field memo boxes to avoid duplication of contacts within the EnerGov contact repository. For example,when populating the permit contacts,those contacts for category 1 should go into the 'permit_contact' table. Those contacts for category 2 should go into the 'permit_contact_no_key'table. Multiple Legacy Data Sources: There are usually multiple data sources to convert in a project. The plan is to have all data sources populated into the EG_Template db. At the main table level,there is an optional column where the legacy data source can be populated for reference. This is provided as a way to easily count up or research records originating from a particular legacy data source. Overall Architecture of Conversion: There are 3 SQL Server databases involved in the conversion process. 1. EG_Template (for legacy data) 2. EnerGov (the production EnerGov db) 3. A database containing all conversion processes and mapping tables. This is maintained by Tyler's data conversion team. This db takes the data from EG_Tempate,translates it, and populates it into the EnerGov db. Mapping EG—Ternplate Conversion . D: .. - All legacy data sources will be This db will be used to This is the EnerGov db used by the loaded into this one db,within the map/translate data before it passes EnerGov software. provided table structure. into EnerGov. Stored procedures and functions will exist in this db, which will essentially be the conversion source code. DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 Progression of Conversion Development Process: Provide empty EG_Template Tyler • Database format will be SQL Server database to client Load legacy data into Client • If there are multiple legacy data sources, all should template database be loaded into the one template SQL database. Mapping process Tyler/Client • Dependent on completed EnerGov configuration • Spreadsheets will be used to communicate mapping values. 0 Mapping questions may arise and both parties may need to discuss these until answers are agreed upon. Import-specific configuration Tyler • Certain fields or values may need to exist for changes to EnerGov imported records only. These usually require some minor EnerGov configuration changes. '- Customize conversion scripts Tyler • Minor customization can be expected for many conversions, based on special requests from client. • Any special requests would also be added into the conversion scripts at this time. Conversion execution Tyler . Resulting EnerGov database will be provided to client team for review. Review and either sign-off or Client • Client team will review the data and the interaction request changes with it in the EnerGov software. • If it meets the client's needs, sign-off will occur. If not, certain steps above may need to be repeated until client signs off on the conversion. Progression of Final Conversion Cutover Process(Go-Live): Load legacy data into Client • This should just be an up-to-date extract of the template database legacy data into the template db. Conversion execution Tyler • Resulting EnerGov database will be provided to client team. This will be the production EnerGov db. Go Live Tyler/Client • Verification of EnerGov db and site functionality • Data Conversion sign-off • Move to production phase DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 •••••• tyler • technologies Exhibit E MYGOVPAY/VIRTUAL PAY 1. MyGovPay/VirtualPay Licensing. Access to MyGovPay and/or Virtual Pay is hereby granted if Customer elects to use MyGovPay or VirtualPay, products of Tyler Technologies (Powered by Persolvent), designed for Citizen Users to use for processing online payments. (a) Special MyGovPay/VirtualPay Definitions. "Merchant Agreement"means the agreement between Customer and Persolvent that provides for the Merchant Fees. "Merchant Fees"means direct costs levied by Visa/Mastercard/Discover or other payment card companies for Interchange Fees, Dues,Assessments and Occurrence Fees,over which Tyler Technologies has no authority. "MyGovPay"means the Product of Tyler Technologies that allows members of the public to pay for Customer's services with a credit or other payment card on the Customer's citizen-facing web portal. "Persolvent"means BankCard Services Worldwide,a Payment Card Industry(PCI)compliant processing agent through which the EnerGov Software passes credit card transactions. "Use Fees"means the fees listed in Use Fees Table in Section 2,titled MyGovPay/VirtualPay.. "VirtualPay"means the Product of Tyler Technologies that allows the Customer to accept and process citizen user's credit or other payment card using the EnerGov Software. (b) Conditions of Use. If customer elects to use MyGovPay and/or VirtualPay the following terms apply: (1) Customer must apply for and agree to a Merchant Agreement with Persolvent. (2) Customer agrees that Citizen Users will be subject to Use Fees as listed in Use Fees table in Section 2. (3) Customer agrees that Use Fees are separate from and independent of Merchant Fees. (4) Customer agrees that this Agreement does not represent any modification to Customer's Merchant Agreement with Persolvent. (5) Customer agrees that Use Fees are for use on the MyGovPay/VirtualPay online system and will not be deposited or owed to Customer in any way. (6) Customer agrees that MyGovPay's and VirtualPay's ability to assess Use Fees is dictated by the Card Associations whose rules may change at any time and for any reason. If MyGovPay and/or VirtualPay,for any reason, are unable to process payments using Use Fees, Customer agrees that MyGovPay/VirtualPay reserves the right to negotiate a new pricing model with Customer for the continued use of MyGovPay and/or VirtualPay. 2. MyGovPay/VirtualPay Fees. Customer agrees that the Use Fees set forth on the following page will apply if ••o . tyler 49 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 Customer elects to use MyGovPay/VirtualPay. Use Fees EnerGov's MyGovPay(Online/card-not-present payments)** MyGovPay(Online MyGovPay(Online Payments) Payments) Percentage Based Fee +Transaction Fee Option 1: Government Entity 2.79% $0.20 Paid Option 2: 3.29/o N/A Patron Paid **ACH processing is available for a fee of$20 per month and$0.30 per transaction. EnerGov's VirtualPay(retail card present) VirtualPay(Retail Virtual Pay(Retail Payments) Payments) Percentage Based Fee +Transaction Fee Option 1: Government Entity 2.59% $0.15 Paid Option 2: 2.990 N/A Patron Paid � Patron Paid fees will be communicated as "Service Fees"to the cardholder, at the time of transaction. In the event that the average transaction amount is below$30, we reserve the right to apply an additional$0.20 service fee above the quoted rates above. 3. Interactive Voice Response ("IVR"). If IVR is selected by Customer and included in the pricing,the following additional terms and conditions shall apply of this Agreement: (a) Network Security. Customer acknowledges that a third-party is used by Tyler Technologies to process IVR data. Customer's content will pass through and be stored on the third-party servers and will not be segregated or in a separate physical location from servers on which other customers'content is or will be transmitted or stored. (b) Content. Customer is responsible for the creation,editorial content,control,and all other aspects of content to be used solely in conjunction with the EnerGov Software. (c) Lawful Purposes.Customer shall not use the IVR system for any unlawful purpose. (d) Critical Application. Customer will not use the IVR system for any life-support application or other critical application where failure or potential failure of the IVR system can cause injury, harm, death,or other grave problems, including,without limitation, loss of aircraft control, hospital life-support system, and delays in getting medical care or other emergency services. ••-o . tyler 50 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 (e) No Harmful Code. Customer represents and warrants that no content designed to delete, disable, deactivate, interfere with or otherwise harm any aspect of the IVR system now or in the future, shall be knowingly transmitted by Customer. (f) IVR WARRANTY. Except as expressly set forth in this Agreement,TYLER TECHNOLOGIES MAKES NO REPRESENTATION AND EXTENDS NO WARRANTIES OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING WARRANTIES OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE FOR IVR. • tyler 51 • DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 tyler technologies Exhibit F Source Code Escrow Agreement IN CONSIDERATION OF the terms and conditions of the Agreement and other good and valuable consideration,the parties hereto agree as follows: ESCROW AGREEMENT. Tyler Technologies agrees to name (hereinafter CLIENT)as a beneficiary in accordance with the provisions of the Software Escrow Service Agreement Tyler Technologies maintains with an independent escrow service. PRICE. CLIENT agrees to pay an initial start-up fee of$750.00,due upon execution of this agreement. Future annual payments will be invoiced in the month prior to the renewal date and will be due in full for this agreement to continue in effect. SOFTWARE SOURCE CODE COVERED. This Agreement applies to all Tyler Software for which CLIENT has paid the full agreed upon price of the Tyler Software license. If CLIENT acquires additional Tyler Software in the future,such software shall also be covered by this Agreement. If CLIENT fails to pay the Escrow fee when due,Tyler Technologies shall have the right in its sole discretion to suspend its performance or terminate this Agreement. TERM. This Agreement shall become effective on the date executed by an officer of Tyler Technologies and shall have a term ending upon the last day of the month one year following that date. A. This Agreement will automatically renew for subsequent one year terms unless either party gives the other party at least thirty days prior written notice of its intent not to renew. Fees for subsequent years are subject to change. PROVISIONS. As a minimum requirement, Tyler Technologies agrees to provide the following service to CLIENT through an escrow agreement: A. Tyler Technologies will maintain a software escrow service agreement with an independent escrow service provider. B. Tyler Technologies will deposit a current copy of source code for all licensed Tyler Software and will update the deposit when a major revision of the software is released. C. If Tyler Technologies chooses to change the provider of the escrow service,Tyler Technologies will notify CLIENT of the name and address of the new escrow service provider. D. The provisions included in the escrow service agreement will include provisions for the beneficiary to receive access to the Tyler Software source code when the escrow service provider has received written instruction directly from Tyler Technologies,Tyler Technology's trustee in bankruptcy,or a court of competent jurisdiction and payment to the escrow service provider of the deposit copying and delivery fees,then the escrow service provider will release a copy of the deposit materials to CLIENT. ACCEPTED BY: ACCEPTED BY: Tyler Technologies,Inc. CLIENT Name By: By: Signature Signature Title Title Date Date . tyler 52 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 • •••'•• tyler • technologies Exhibit G Sample Project Plan Project timelines are living documents, subject to refinement during the project planning stage and over the course of project deployment.The project plan set forth below is provided for your reference purposes.The parties will collaborate on a baseline project schedule during Stage 1 of the project, as set forth in the Statement of Work. •0 -0'. tyler 53 DocuSign Envelope ID: 1CCA18DC-6CC1-428C-A15D-5173EE24B471 0 0 0 c ID JTask Name Duration Start Finish Predecessors m 1 City of Danville, CA- Project Plan (V.3) 582 days Thu 12/19/13 Fri 3/11/16 CD 0 2Stage 1 1 • . 1 1 1 m 43/20/15 37 : 1 • . w 38 EnerGov On-Site(Assess& Define) (2 People) 10 days Mon 3/23/15 Fri 4/3/15 0_ 39 Workflow Reviews 10 days Mon 3/23/15 Fri 4/3/15 1 4 40 Collect Fee Schedules and Discuss Fees per Business Processes 10 days Mon 3/23/15 Fri 4/3/15 41 Review and Document Intake Requirements, Forms and Fields 10 days Mon 3/23/15 Fri 4/3/15 co 42 Review and Document Output Requirements (Documents, Letters, Reports) 10 days Mon 3/23/15 Fri 4/3/15Cn W 43 Collect Employee Names and Associated Roles, Define User Profile Specifics 10 days Mon 3/23/15 Fri 4/3/15 co 44 Collect Legacy Data Source Samples, Data Diagrams and Files for Data Import 10 days Mon 3/23/15 Fri 4/3/15 45 Review GIS Data and Discuss Public Map Service 10 days Mon 3/23/15 Fri 4/3/15 w 46 Confirm Hardware and Infrastructure Requirements 10 days Mon 3/23/15 Fri 4/3/15 m 47 EnerGov Off-Site (Assess& Define) 40 days Mon 4/6/15 Fri 5/29/15 co 48 Deliver Revised Project Plan 40 days Mon 4/6/15 Fri 5/29/15 49 Change Orders/Scope Revisions (As Needed) 40 days Mon 4/6/15 Fri 5/29/15 50 Document Project Risks 40 days Mon 4/6/15 Fri 5/29/15 51 Design Workflows 40 days Mon 4/6/15 Fri 5/29/15 52 Weekly Status Calls 40 days Mon 4/6/15 Fri 5/29/15 53 EnerGov Off-Site 40 days Mon 4/6/15 Fri 5/29/15 54 Revise Workflows 40 days Mon 4/6/15 Fri 5/29/15 55 Complete Custom Field Documentation 40 days Mon 4/6/15 Fri 5/29/15 56 Complete System Setup Spreadsheet Documentation 40 days Mon 4/6/15 Fri 5/29/15 57 EnerGov 9 Installation 40 days Mon 4/6/15 Fri 5/29/15 58 Citizen Access Portal (CAP) Installation 40 days Mon 4/6/15 Fri 5/29/15 59 eReviews Installation 40 days Mon 4/6/15 Fri 5/29/15 60 iG Workforce Installation 40 days Mon 4/6/15 Fri 5/29/15 61 BSCW(Credit Card Processing) Contact Setup (If Applicable) 40 days Mon 4/6/15 Fri 5/29/15 62 Weekly Status Calls 40 days Mon 4/6/15 Fri 5/29/15 63 Memorial Day(Danville &Tyler 1 day Mon 5/25/15 Mon 5/25/20 64 Assess& Define Sign-Off 1 day Fri 5/29/15 Fri 5/29/15 65 66 EnerGov On-Site 5 days Mon 6/8/15 Fri 6/12/15 67 Configuration reviews 5 days Mon 6/8/15 Fri 6/12/15 Page 1 DocuSign Envelope ID: 1CCA18DC-6CC1-428C-A15D-5173EE24B471 0 0 0 0 ID Task Name Duration Start Finish Predecessors 0 D m 0 68 EnerGov Off-Site 55 days Mon 6/1/15 Fri 8/14/15 69 Configurations 55 days Mon 6/1/15 Fri 8/14/15 70 Weekly Status Calls 55 days Mon 6/1/15 Fri 8/14/15 71 EnerGov Off-Site 55 days Mon 6/1/15 Fri 8/14/15 W 72 Building (L&I) Configuration 55 days Mon 6/1/15 Fri 8/14/15 n 73 Business Licensing (L&I) Configuration 5 days Mon 6/1/15 Fri 6/5/15 74 Housing Code Enforcement Configuration 55 days Mon 6/1/15 Fri 8/14/15 T 75 Planning&Zoning Configuration 55 days Mon 6/1/15 Fri 8/14/15 N 76 Department of Public Works Configuration 55 days Mon 6/1/15 Fri 8/14/15 W 77 ePortal Configuration 55 days Mon 6/1/15 Fri 8/14/15Ell o 78 iG Workforce Configuration 55 days Mon 6/1/15 Fri 8/14/15 79 Weekly Status Calls 55 days Mon 6/1/15 Fri 8/14/15 80 EnerGov Off-Site 55 days Mon 6/1/15 Fri 8/14/15 81 Final configuration Reviews 55 days Mon 6/1/15 Fri 8/14/15 co 82 Final EnerGov Configuration Changes 55 days Mon 6/1/15 Fri 8/14/15 83 Final GIS Configuration Changes 55 days Mon 6/1/15 Fri 8/14/15 84 Final ePortal Changes 55 days Mon 6/1/15 Fri 8/14/15 85 Final iG Workforce Configuration Changes 55 days Mon 6/1/15 Fri 8/14/15 86 Prepare Internal Testing Scripts 55 days Mon 6/1/15 Fri 8/14/15 87 Weekly Status Calls 55 days Mon 6/1/15 Fri 8/14/15 88 Independence Day(Danville &Tyler) 1 day'W Fri 7/3/1V Fri 7/3/15 89 Basic System Configuration Sign-Off 6 days Fri 8/7/12 Fri 8/14/15 90 . . 91 EnerGov Off-Site 5 days Mon 8/17/15 Fri 8/21/15 92 Configuration Review& Internal Testing Preparation 5 days Mon 8/17/15 Fri 8/21/15 93 EnerGov Off-Site (Operational Testing) 35 days Mon 8/17/15 Fri 10/2/15 94 Conduct Basic System Testing 35 days Mon 8/17/15 Fri 10/2/15 95 Record Testing Results and Identified Issues in Share Point 35 days Mon 8/17/15 Fri 10/2/15 96 Resolve System Configuration Issues 35 days Mon 8/17/15 Fri 10/2/15 97 Labor Day(Danville &Tyler) 1 day Mon 9/7/15 Mon 9/7/15 98 Internal Testing Sign-Off ' 1 day Fri 10/2/15 Fri 10/2/15 99 Stage 5- Build Specifications(88 Hours) ff,Rw"IMMUITRIM 100 EnerGov Off-Site 20 days Mon 10/5/15 Fri 10/30/15 101 Legacy Data Conversion Mapping Documentation 20 days Mon 10/5/15 Fri 10/30/15 Page 2 DocuSign Envelope ID: 1CCA18DC-6CC1-428C-A15D-5173EE24B471 0 0 0 c ID TaskNarne Duration Start Finish Predecessors m 102 Interface Development Specification Documetation 15 days Mon 10/5/15 Fri 10/23/15 CD 103 Custom Report Specification Documentation 20 days iMon 10/5/15 Fri 10/30/15 CD 104 Build Specifications Sign-Off 1 day Fri 10/30/15 Fri 10/30/1 co 105 . 0) w 106 EnerGov Off-Site 15 days Mon 11/2/15 Fri 11/20/15 C 107 Interface Development 15 days Mon 11/2/15 Fri 11/20/15 108 Custom Report Development 15 days Mon 11/2/15 Fri 11/20/15 109 Legacy Data Conversion Development 15 days Mon 11/2/15 Fri 11/20/15 co 110 "Build ran's Day (Danvill 1 day Wed 11/11/1�W � W 111ign-Off 1 day Fri 11/20/15 Fri 11/20/15 Cn 112 2� 113 EnerGov On-Site 5 days Mon 11/16/1!Fri 11/20/15 w 114 UAT Training 5 days Mon 11/16/1�Fri 11/20/15 115 EnerGov Off-Site 4 days Mon 11/23/1!Thu 11/26/15 co 116 Create Test Script and System Acceptance Tracking Documentation 3 days Mon 11/23/1-'Wed 11/25/1-' 117 Review System Acceptance Test Strategies and Best Practices 2 days Mon 11/23/1-'Tue 11/24/15 118 Thanksgiving (Danville &Tyler) 2 days Thu 11/26/15 Fri 11/27/15 119 System Acceptance Planning Sign-Off 1 day Wed 11/25/1!Wed 11/25/1! 120 Mon 11/30/1! 121 EnerGov Off-Site 55 days Mon 11/30/1!Fri 2/12/16 122 System Acceptance Testing Execution 55 days Mon 11/30/1�Fri 2/12/16 123 System Acceptance Testing Issue Resolution 55 days Mon 11/30/1�Fri 2/12/16 124 Develop Cutover Strategy Documentation 55 days Mon 11/30/1�Fri 2/12/16 125 Production System Readiness 55 days Mon 11/30/1�Fri 2/12/16 126 Christmas (Danville) 2 days Fri 12/25/15 Mon 12/28/7 127 Christmas (Tyler) 2 days Thu 12/24/15 Fri 12/25/15 128 Holiday Furlough (Danville) 3 days Tue 12/29/15 Thu 12/31/15 129 New Year's Day(Danville &Tyler) 1 day Fri 1/1/16 Fri 1/1/16 130 Martin Luther King Day(Danville) 1 day Mon 1/18/16 Mon 1/18/16 131 Verification and System Acceptance Testing Sign-Off 1 day Fri 2/12/16 Fri 2/12/16 132 . . 133 EnerGov Off-Site 5 days Mon 2/15/16 Fri 2/19/16 134 End User Training Preperation 5 days Mon 2/15/16 Fri 2/19/16 135 EnerGov On-Site(End User Training) 5 days Mon 2/22/16 Fri 2/26/16 Page 3 DocuSign Envelope ID: 1CCA18DC-6CC1-428C-A15D-5173EE24B471 0 0 0 c ID T"me Duration Start Finish Predecessors m 136 Comperhensive End User Training 5 days Mon 2/22/16 Fri 2/26/16 CD 137 End User Training Sign-Off 1 day Fri 2/26/16 Fri 2/26/16 CD 138 President's Day(Danville) 1 day Mon 2/15/16 Mon 2/15/16 139 . . .. . .. 0) w 140 Go Live 1 day Mon 2/29/16 Mon 2/29/16 C 141 EnerGov Off-Site 1 day Mon 2/29/16 Mon 2/29/16 142 Final Legacy Data Conversion Cutover 1 day Mon 2/29/16 Mon 2/29/16 143 EnerGov On-Site(Production Support) (2 People) 5 days Mon 2/29/16 Fri 3/4/16 N 144 Production Support 5 days Mon 2/29/16 Fri 3/4/16Cn W 145 Production Issue Resolution 5 days Mon 2/29/16 Fri 3/4/16 co 146 Develop Post-Production Issues List 5 days Mon 3/7/16 Fri 3/11/16 147 Production & Production Support Sign-Off 1 day Fri 3/11/16 Fri 3/11/16 w w N V co co Page 4 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 ® DATE(MM/DD/YYYY) ACORN CERTIFICATE OF LIABILITY INSURANCE 11/13/2015 THIS CERTIFICATE IS ISSUED AS A MATTER OF INFORMATION ONLY AND CONFERS NO RIGHTS UPON THE CERTIFICATE HOLDER. THIS CERTIFICATE DOES NOT AFFIRMATIVELY OR NEGATIVELY AMEND, EXTEND OR ALTER THE COVERAGE AFFORDED BY THE POLICIES BELOW. THIS CERTIFICATE OF INSURANCE DOES NOT CONSTITUTE A CONTRACT BETWEEN THE ISSUING INSURER(S), AUTHORIZED REPRESENTATIVE OR PRODUCER,AND THE CERTIFICATE HOLDER. IMPORTANT: If the certificate holder is an ADDITIONAL INSURED, the policy(ies) must be endorsed. If SUBROGATION IS WAIVED, subject to the terms and conditions of the policy,certain policies may require an endorsement. A statement on this certificate does not confer rights to the certificate holder in lieu of such endorsement(s). PRODUCER CONTACT Producer HOUSE NAME: Hays Companies PHONE (617)723-7775 n/c No: 133 Federal Street, 2nd Floor ADDRESS:DDRESS: INSURERS AFFORDING COVERAGE NAIC# Boston MA 02110 INSURERA:Atlantic Specialty Insurance 27154 INSURED INSURER B:Trumbull Insurance Company 27120 Tyler Technologies, Inc. INSURERc:Certain Underwriters at Lloyds 5101 Tennyson Parkway INSURER D: INSURER E: Plano TX 75024 INSURERF: COVERAGES CERTIFICATE NUMBER:11.1.15-3.1.16 GL, Auto, REVISION NUMBER: THIS IS TO CERTIFY THAT THE POLICIES OF INSURANCE LISTED BELOW HAVE BEEN ISSUED TO THE INSURED NAMED ABOVE FOR THE POLICY PERIOD INDICATED. NOTWITHSTANDING ANY REQUIREMENT, TERM OR CONDITION OF ANY CONTRACT OR OTHER DOCUMENT WITH RESPECT TO WHICH THIS CERTIFICATE MAY BE ISSUED OR MAY PERTAIN, THE INSURANCE AFFORDED BY THE POLICIES DESCRIBED HEREIN IS SUBJECT TO ALL THE TERMS, EXCLUSIONS AND CONDITIONS OF SUCH POLICIES.LIMITS SHOWN MAY HAVE BEEN REDUCED BY PAID CLAIMS. INSR TYPE OF INSURANCE ADDL SUBR POLICY EFF POLICY EXP LIMITS LTR INSR POLICY NUMBER MM/DD/YYYY MM/DD/YYYY GENERAL LIABILITY EACH OCCURRENCE $ 1,000,000 DAMAGE To R X COMMERCIAL GENERAL LIABILITY PREM SES Ea occTur ence $ 1,000,000 A CLAIMS-MADE Fx_] OCCUR 711013784-0002 3/1/2015 3/1/2016 MED EXP(Any one person) $ 10,000 PERSONAL&ADV INJURY $ 1,000,000 GENERAL AGGREGATE $ 2,000,000 GEN'L AGGREGATE LIMIT APPLIES PER: PRODUCTS-COMP/OP AGG $ 2,000,000 x- POLICY PRO LOC $ AUTOMOBILE LIABILITY Ea aBINEDtSINGLE LIMIT 1,000,000 A X ANY AUTO BODILY INJURY(Per person) $ ALL OWNED SCHEDULED 711013784-0002 3/1/2015 3/1/2016 BODILY INJURY(Peraccident) $ AUTOS AUTOS X }( NON-OWNED PROPERTY DAMAGE $ HIRED AUTOS AUTOS Per accident X UMBRELLA LIAB OCCUR EACH OCCURRENCE $ 15,000,000 A EXCESS LIAB CLAIMS-MADE AGGREGATE $ 15,000,000 DED I I RETENTION$ 711013784-0002 3/1/2015 3/1/2016 $ B WORKERS COMPENSATION X WC STALIMTU- OTH- AND EMPLOYERS'LIABILITY Y/N ER ANY PROPRI N/A ETOR/PARTNER/EXECUTIVE❑ E.L.EACH ACCIDENT $ 1,000,000 OF EXCLUDED? n (Mandatory in NH) 08WBCS5886 /1/2015 3/1/2016 E.L.DISEASE-EA EMPLOYE $ 1,000,000 If yes,describe under DESCRIPTION OF OPERATIONS below E.L.DISEASE-POLICY LIMIT $ 1,000,000 C Professional Liability 0901LI1414036000 11/17/2015 11/17/2016 Occurence Limit: $20,000,000 C Professional Liability 0901LI1414036000 11/17/2015 11/17/2016 Aggregate Limit: $20,000,000 DESCRIPTION OF OPERATIONS/LOCATIONS/VEHICLES (Attach ACORD 101,Additional Remarks Schedule,if more space is required) CERTIFICATE HOLDER CANCELLATION SHOULD ANY OF THE ABOVE DESCRIBED POLICIES BE CANCELLED BEFORE THE EXPIRATION DATE THEREOF, NOTICE WILL BE DELIVERED IN Evidence of Insurance ACCORDANCE WITH THE POLICY PROVISIONS. AUTHORIZED REPRESENTATIVE James Hays/SKING — ACORD 25(2010/05) ©1988-2010 ACORD CORPORATION. All rights reserved. INS095r9ntnn,,im Thn ArYnPrl nn—­4 1n nrn rnnicf—rl m rlrc of Af`fl!Drl DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 130621 PTYLE000215 PRIMARY LAYER DECLARATIONS Attaching to and forming part of em"B Plntection hsuan e POLICY NUMBER:B0621PTYLE000215 This Insurance is effected with Certain Underwriters at Lloyd's, London(not incorporated) THIS POLICY IS A CLAIMS MADE AND REPORTED POLICY. EXCEPT AS OTHERWISE PROVIDED HEREIN, THIS POLICY COVERS ONLY CLAIMS FIRST MADE AND REPORTED TO US DURING THE POLICY PERIOD AND ON OR AFTER THE RETROACTIVE DATE BUT BEFORE THE END OF THE POLICY PERIOD OR ANY EXTENDED REPORTING PERIOD, IF APPLICABLE. ALL CLAIMS ARE SUBJECT TO THE APPLICABLE LIMITS OF LIABILITY AND THE APPLICABLE RETENTION(S). PLEASE NOTE THAT THE LIMITS OF LIABILITY FOR INSURING AGREEMENTS 1, 2, 3, AND 5 INCLUDE CLAIM EXPENSES. PLEASE REVIEW THE COVERAGE AFFORDED UNDER THIS INSURANCE POLICY CAREFULLY AND DISCUSS THE COVERAGE HEREUNDER WITH YOUR INSURANCE AGENT OR BROKER. 1 NAMED INSURED: Tyler Technologies, Inc ADDRESS 5101 Tennyson Parkway, Plano, TX 75024 2 POLICY PERIOD. FROM_ 171"November 2015 TO: 1Th November 2016 (Both days at 12 01 A.M. standard time at the address shown in Item 1.) 3 POLICY LIMITS OF LIABILITY AND COVERAGES PURCHASED You have purchased some or all of the following Insuring Agreements. Only those Insuring Agreement(s)that specify a Limit of Liability below have been purchased. If an Insuring Agreement has not been purchased that portion of this policy is not applicable. LIMITS OF LIABILITY 3A LIMIT OF LIABILITY: (1) INSURING AGREEMENT 1. PROFESSIONAL SERVICES USD20,000,000 Each claim and in the aggregate-including claims expenses DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 www miller-insurance com Page 16 80621 PTYLE000215 PRIMARY LAYER (2) INSURING AGREEMENT 2, MULTIMEDIA LIABILITY: USD20,000,000 Each claim and in the aggregate-including claims expenses (3) INSURING AGREEMENT 3, SECURITY AND PRIVACY LIABILITY. USD 20,000,000 Each claim and in the aggregate-including claims expenses (4) INSURING AGREEMENT 4, DATA RECOVERY AND LOSS OF BUSINESS INCOME COVERAGE: USD 20,000,000 Each claim and in the aggregate (5) INSURING AGREEMENT 5, PRIVACY REGULATORY DEFENSE AND PENALTIES: USD 20,000,000 Each claim and in the aggregate-including claims expenses (6) INSURING AGREEMENT 6, CRISIS MANAGEMENT, CUSTOMER NOTIFICATION COSTS, AND CUSTOMER SUPPORT AND CREDIT MONITORING EXPENSES USD 20,000.000 Each claim and in the aggregate (7) INSURING AGREEMENT 7, DATA EXTORTION USD 20,000,000 Each claim and in the aggregate 3B. TOTAL LIMIT OF LIABILITY UNDER THE POLICY: USD 20,000,000 is the Total Limit of Liability under the policy. 3C. Notwithstanding the aggregate Limit of Liability under each Insuring Agreement as set forth in item 3(A)above,all payments made under the policy, regardless of the number of Insuring Agreements that apply,will reduce the total Limit of Liability as set forth in item 3(B) above. In no event will Underwriters pay more than the total Limit of Liability as set forth in item 3(B)above. 4 RETENTION and WAITING PERIOD: Insuring Agreement 1, Professional Services USD500,000 Each claim-including claims expenses Insuring Agreement 2, Multimedia Liability DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 B0621 PTYLE000215 PRIMARY LAYER USD500,000 Each claim-including claims expenses Insuring Agreement 3, Security and Privacy Liability USD500,000 Each claim-including claims expenses Insuring Agreement 4, Data Recovery and Loss of Business Income Coverage Data Recovery USD500,000 Each claim Loss of Business Income Coverage 12 Hours waiting period Insuring Agreement 5, Privacy Regulatory Defense and Penalties USD500,000 Each claim Insuring Agreement 6, Crisis Management, Customer Notification Costs, and Customer Support and Credit Monitoring Expenses USD500,000 Each claim Insuring Agreement 7, Data Extortion USD500,000 Each claim 5 RETROACTIVE DATE: Insuring Agreement 1 —V January 1996 Insuring Agreement 2—1st January 1996 Insuring Agreement 3—291h June 2006 Insuring Agreement 4—Not applicable Insuring Agreement 5—29'"June 2006 Insuring Agreement 6--Not applicable Insuring Agreement 7—Not applicable 6 ANNUAL PREMIUM: USD236,500.00 7 NOTICE OF CLAIM TO: Kari Timm Bates Carey 191 North Wacker Drive Suite 2400 Chicago, IL 60606 S NOTICE OF ELECTION: Hays Companies 1 South Wacker Drive Chicago 60606 Illinois S SERVICE OF SUIT: Mendes&Mount,LLP. 750 Seventh Avenue New York,NY 10019 10 CHOICE OF LAW. New York DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 www.miller-insurance cam Page 18 B0621 PTYLE000215 PRIMARY LAYER f1 TERRITORY: Anywhere in the world- 12 TECHNOLOGY PROFESSIONAL SERVICES FOR WHICH COVERAGE HAS BEEN PURCHASED: As per attached endorsement DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 • •••'•• tyler • technologies AMENDMENT This amendment("Amendment") is effective as of the date of signature of the last party to sign as indicated below ("Amendment Effective Date"), by and between Tyler Technologies, Inc. with offices at One Tyler Drive,Yarmouth, Maine 04096 ("Tyler") and Orange County, North Carolina,with offices at 131 West Margaret Lane, Hillsborough, North Carolina 27278 ("Client"). WHEREAS,Tyler and the Client are parties to an agreement dated February 16, 2016 ("Agreement"); and WHEREAS,Tyler and Client desire to amend the terms of the Agreement as provided herein. NOW THEREFORE, in consideration of the mutual promises hereinafter contained,Tyler and the Client agree as follows: 1. The Integration Service: Orange County CAMA, at a contract price of$9,000, is hereby removed from the Agreement as of the Amendment Effective Date. 2. Annual software maintenance and support for the Tyler Software products set forth below is removed from the Agreement as of the Amendment Effective Date. In recognition of maintenance fees paid to Tyler for such software,Tyler hereby issues to Client credit as outlined below: Description Term Invoice# Annual Fee Paid EnerGov Support—IVR Telephony 3/26/18-3/25/19 045-211577 $2,317.50 EnerGov Support—Orange County CAMA 3/26/18-3/25/19 045-211577 $1,668,60 EnerGov Support—IVR Telephony 3/26/19-3/25/20 045-257853 $2,387.03 EnerGov Support—Orange County CAMA 3/26/19-3/25/20 045-257853 $1,718.66 Total Credit: $8,091.79 Client may apply such credit, in its discretion,to any fees due to Tyler under the Agreement. 3. This Amendment, upon execution, shall serve as Client's documentation for the credit issued (the executed Amendment is your credit invoice from Tyler). 4. This Amendment shall be governed by and construed in accordance with the terms and conditions of the Agreement. 5. Except as expressly indicated in this Amendment, all other terms and conditions of the Agreement shall remain in full force and effect. SIGNATURE PAGE FOLLOWS Page 1 of 2 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 IN WITNESS WHEREOF,the parties hereto have executed this Amendment as of the dates set forth below. Tyler Technologies, Inc. Orange County, NC DocuSigned by: DocuSigned by: By: �6� LV�in t —�Un St In By: , ik 4&yv f BBB7231CF3934'B... C11BA91E73A64DF... Name: Rob Kennedy-7ensen Name: Jim Northrup Title: Director of Contracts Title: Orange County Chief Information Officer Date: 2/12/2020 Date: 2/27/2020 Page 2 of 2 DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 AC"R"0 Fil TE(MM/DD/YYYY) CERTIFICATE OF LIABILITY INSURANCE 2/16/2019 THIS CERTIFICATE IS ISSUED AS A MATTER OF INFORMATION ONLY AND CONFERS NO RIGHTS UPON THE CERTIFICATE HOLDER. THIS CERTIFICATE DOES NOT AFFIRMATIVELY OR NEGATIVELY AMEND, EXTEND OR ALTER THE COVERAGE AFFORDED BY THE POLICIES BELOW. THIS CERTIFICATE OF INSURANCE DOES NOT CONSTITUTE A CONTRACT BETWEEN THE ISSUING INSURER(S), AUTHORIZED REPRESENTATIVE OR PRODUCER,AND THE CERTIFICATE HOLDER. IMPORTANT: If the certificate holder is an ADDITIONAL INSURED, the policy(ies) must be endorsed. If SUBROGATION IS WAIVED, subject to the terms and conditions of the policy,certain policies may require an endorsement. A statement on this certificate does not confer rights to the certificate holder in lieu of such endorsement(s). PRODUCER CONTACT Moira Crosby Y Hays Companies Inc. PHONE FAX AIC No Ext: (A/C, A/C No): 133 Federal Street, 4th Floor E-MAIL mcrosb @ha scornp anies.com ADDRESS: Y �' INSURER(S)AFFORDING COVERAGE NAIC# Boston MA 02110 INSURER A:Hartford Fire Insurance Company 19682 INSURED INSURER B:Hartford Casualty Insurance Company 29424 Tyler Technologies, Inc. INSURERC:Llo ds of London Syndicates 048337 & 5101 Tennyson Parkway INSURERD: 048945 INSURER E: Plano TX 75024 INSURER F: COVERAGES CERTIFICATE NUMBER:12.17.19-4.1.20 GL Auto REVISION NUMBER: THIS IS TO CERTIFY THAT THE POLICIES OF INSURANCE LISTED BELOW HAVE BEEN ISSUED TO THE INSURED NAMED ABOVE FOR THE POLICY PERIOD INDICATED. NOTWITHSTANDING ANY REQUIREMENT, TERM OR CONDITION OF ANY CONTRACT OR OTHER DOCUMENT WITH RESPECT TO WHICH THIS CERTIFICATE MAY BE ISSUED OR MAY PERTAIN, THE INSURANCE AFFORDED BY THE POLICIES DESCRIBED HEREIN IS SUBJECT TO ALL THE TERMS, EXCLUSIONS AND CONDITIONS OF SUCH POLICIES.LIMITS SHOWN MAY HAVE BEEN REDUCED BY PAID CLAIMS. INSR TYPE OF INSURANCE ADDL SUBR POLICY EFF POLICY EXP LIMITS LTR POLICY NUMBER MM/DD/YYYY MM/DD/YYYY X COMMERCIAL GENERAL LIABILITY EACH OCCURRENCE $ 1,000,000 A CLAIMS-MADE AMAGE TO RENTED 1,000,000 OCCUR D PREMISES Ea occurrence $ 08UENAY8572 4/1/2019 4/1/2020 MED EXP(Any one person) $ 10,000 PERSONAL&ADV INJURY $ 1,000,000 GEN'L AGGREGATE LIMIT APPLIES PER: GENERAL AGGREGATE $ 2,000,000 X POLICY PRO ❑ LOC PRODUCTS-COMP/OPAGG $ 2,000,000 PRO- OTHER: $ AUTOMOBILE LIABILITY COEa aMBINEDccident SINGLE LIMIT $ 1,000,000 X ANY AUTO BODILY INJURY(Per person) $ A ALL OWNED SCHEDULED AUTOS AUTOS 08UENAY8572 4/1/2019 4/1/2020 BODILY INJURY(Per accident) $ NON-OWNED PROPERTY DAMAGE HIRED AUTOS AUTOS er X UMBRELLA LIAB X OCCUR EACH OCCURRENCE $ 25,000,000 B EXCESS LIAB CLAIMS-MADE AGGREGATE $ 25,000,000 DIED RETENTION$ 08XHUAZ8392 4/1/2019 4/1/2020 $ WORKERS COMPENSATION X PER OTH- AND EMPLOYERS'LIABILITY Y/N STATUTE ER ANY PROPRIETOR/PARTNER/EXECUTI . E.L.EACH ACCIDENT $ 1,000,000 OFFICER/MEMBER EXCLUDED? ❑ N/A B (Mandatory in NH) 08WEEL5271 4/1/2019 4/1/2020 E.L.DISEASE-EA EMPLOYE $ 1,000,000 If yes,describe under DESCRIPTION OF OPERATIONS below E.L.DISEASE-POLICY LIMIT $ 1,000,000 C Cyber/Privacy Prof Liab B0621PTYLE000219 12/17/2019 12/17/2020 Limit $20,000,000 C Cyber/Privacy Prof Liab B0621PTYLE000319 12/17/2019 12/17/2020 Excess Limit $10,000,000 DESCRIPTION OF OPERATIONS/LOCATIONS/VEHICLES (ACORD 101,Additional Remarks Schedule,may be attached if more space is required) CERTIFICATE HOLDER CANCELLATION SHOULD ANY OF THE ABOVE DESCRIBED POLICIES BE CANCELLED BEFORE Evidence of Insurance THE EXPIRATION DATE THEREOF, NOTICE WILL BE DELIVERED IN ACCORDANCE WITH THE POLICY PROVISIONS. AUTHORIZED REPRESENTATIVE James Hays/MCROSB ©1988-2014 ACORD CORPORATION. All rights reserved. ACORD 25(2014/01) The ACORD name and logo are registered marks of ACORD I N S025(201401)