Loading...
The URL can be used to link to this page
Your browser does not support the video tag.
Home
My WebLink
About
Contract 34842-A2
CITY SECRETARY UUNfRACT NO. AMENDMENT NO. 2 TO SYSTEM PURCHASE AGREEMENT BETWEEN THE CITY OF FORT WORTH AND TRITECH SOFTWARE SYSTEMS This Amendment No. 2 (this "Amendment") to the System Purchase Agreement known as City Secretary Contract No. 34842 entered into by and between the City of Fort Worth, Texas ("Client") and TriTech Software Systems ("TriTech") dated January 31, 2007 (the "Agreement") is effective as of the last date of signature below (authorized by M&C C-21944). In the event of a conflict between the terms of this Amendment and the terms of the Agreement, the terms of this Amendment shall control. All capitalized terms not defined herein shall have the meaning ascribed to them in the Agreement. WHEREAS, Client and TriTech desire to amend the existing Agreement for allow for the Client's purchase of additional TriTech software licenses as further defined in this Amendment and its Exhibits. NOW, THEREFORE, in consideration of the promises and mutual agreements contained herein, the parties agree as follows: 1. The Project is for the purchase of TriTech Software licenses and services for Inform RMS, Inform FBR, TriTech.com IQ and TriTech.com Analytics, as more fully defined by the following Exhibits attached hereto: Exhibit A Statement of Work Exhibit B Cost Detail and Payment Milestones Exhibit C Initial Project Schedule 2. Acceptance is defined in the Statement of Work. 3. Except as modified herein, the following terms and conditions of the Agreement shall remain in full force and effect with respect to this Amendment: Section 3.0 Definitions Section 3.42 shall be deleted in its entirety Section 4.0 Prices and Payment Section 5.0 Software Licenses Section 6.0 Delivery, Installation, Title and Risk of Loss Section 6.4 - Training will be provided in accordance with the Statement of Work and Project Schedule. 0 Section 7.0 Site Preparation Replace references to Site Preparation and Support Connectivity Guide with TriTech's System Planning Document. -:a K Section 8.0 Services Section 10.0 Confidentiality and Proprietary Rights Section 12.0 Maintenance and Software Support a' Section 12.1 - Support for the TriTech Software provided under this Amendment shall begin upon Go Live. Amendment 2 to System Purchase Agreement Page 1 of 9 Section 12.4 - Client will be providing all Equipment for this Project. Client provided Equipment will meet TriTech's minimum recommended specifications. Section 13.0 Source Code Escrow Section 14.0 Default and Termination Section 15.0 Liability/Indemnity Section 16.0 Insurance Section 17.0 Copyright & Patent Infringement Section 18.0 Dispute Resolution Section 19.0 Sales, Use and Property Tax Section 20.0 Severability Section 21.0 Force Majure/Excusable Delay Section 22.0 Construction and Headings Section 23.0 Waiver Section 24.0 Entire Agreement Section 25.0 Applicable Law/Venue Section 26.0 Assignment Section 27.0 Notices Section 28.0 Order of Precedence The Order of Precedence set forth in Section 6 below shall apply to this Project. Section 29.0 General Terms 4. For purposes of this Amendment, references in the Agreement to Addendum A-1, Statement of Work shall mean the Statement of Work attached hereto as Exhibit A. 5. References in the Agreement to pricing Addenda A-2 through A-9 shall mean the Cost Detail and Payment Milestones attached hereto as Exhibit B. 6. The following Order of Precedence shall apply to this Amendment: (1) This Amendment (2) Cost Detail and Payment Milestones (3) Statement of Work and Initial Project Schedule (4) The Agreement [SIGNATURE PAGE TO FOLLOW] Amendment 2 to System Purchase Agreement Page 2 of 9 EACH PARTY'S ACCEPTANCE HEREOF IS EXPRESSLY LIMITED TO THE TERMS OF THIS AMENDMENT AND NO DIFFERENT OR ADDITIONAL TERMS CONTAINED IN ANY PURCHASE ORDER, CONFIRMATION OR OTHER WRITING SHALL HAVE ANY FORCE OR EFFECT UNLESS EXPRESSLY AGREED TO IN WRITING BY THE PARTIES. CITY OF FORT WORTH TRITECH SOFTWARE SYSTEMS cce ed By (Signature) Accepted By (Signature) Susan Alanis Tony Eales Printed Name Printed Name Assistant City Manager President & CEO Title Title 'I ';�) � � I I ) �2 - 1-7-�i / I '- Date Date APPit®VEi3 AS TO RM Fbt+iD LEGALITY, a; ASSistanf 'd, A411 Vol 0 0 ,. s � � v ° dp* arn p U pGGfl OFFICIAL.RECORD CITY SECRETARY FT.WORTH,TX Amendment(9,to System Purchase Agreement Page 3 of 9 Exhibit A Statement of Work (Attached) Amendment 2 to System Purchase Agreement Page 4 of 9 Exhibit B Cost Detail and Payment Milestones CONFIDENTIAL TriTech Software License Fee(s) Inform FBR User $1,100.00 250 $275,000.00 Inform RMS Accident $13,068.00 1 $13,068.00 Inform RMS Barcode Handheld Reader Software $1,725.00 1 $1,725.00 Inform RMS Evidence and Barcoding $13,070.00 1 $13,070.00 Inform RMS GIS(With CAD) $0.00 1 $0.00 Inform RMS Server Software(D-251-550 Users) $100,000.00 1 $100,000.00 Inform RMS Test or Training System $0.00 1 $0.00 Inform RMS User $1,590.00 225 $357,750.00 Inform RMS Software License Fee(s)Subtotal: $760,613.00 TriTech Upgrade Credit: ($-472,723.00) TriTech Software License Feels) Total: $287,890.00 TriTech Implementation Service Fee(s) Business Analysis for Inform FBR(140 Hours) $21,000.00 1 $21,000.00 Inform RMS 3-Day Workshop and Consultation $4,200.00 5 $21,000.00 Inform RMS Administration Review and Training-(D-251-550 concurrent users) $7,000.00 1 $7,000.00 Inform RMS DOLF(D-251-550 Users) $20,300.00 1 $20,300.00 Inform RMS Output Designer Workshop 3 Day $4,200.00 1 $4,200.00 Inform RMS Position Installation(up to 5 workstations) $3,150.00 1 $3,150.00 Inform RMS Routing/GIS Server Implementation $6,300.00 1 $6,300.00 Inform RMS Server Installation and Configuration $7,700.00 1 $7,700.00 Inform RMS Standard Functional Acceptance and Integration Testing-(D-251-500 users) $10,500.00 1 $10,500.00 Inform RMS System Orientation and Analysis-(D-251 -550 users) $21,000.00 1 $21,000.00 Inform RMS User Training-Field Officers(3 Days) $4,200.00 5 $21,000.00 Inform RMS User Training-Investigations(3 Days) $4,200.00 5 $21,000.00 Inform RMS User Training-Property and Evidence Training(3 Days) $4,200.00 1 $4,200.00 Inform RMS User Training-Records(3 days) $4,200.00 1 $4,200.00 Onsite Go Live Support Services for Inform RMS(2 persons,4 days,single shift) $25,200.00 1 $25,200.00 Amendment 2 to System Purchase Agreement Page 5 of 9 Remote Implementation Services for Inform RMS GIS $2,500.00 1 1 $2,500.00 Inform RMS Implementation Service Fee(s)Subtotal. $200,250.00 TriTech Implementation Service Feels) Total. $200,250.00 Custom Solution(s) CopLogic Interface to Inform RMS $19,250.00 1 $19,250.00 LiveScan Interface-One Way-Inform RMS to Livescan for Fingerprints $15,400.00 1 $15,400.00 TIPS Mugshot Interface Configuration-One Way Inform RMS to TIPS $7,000.00 1 $7,000.00 Custom Solution(s) Total: $41,650.00 Project Related Fee(s) Project Management $162,625.00 1 $162,625.00 Estimated Travel Expenses(To be billed as incurred) $60,025.00 1 $60,025.00 Report Writing Training(3 days) $4,200.00 1 $4,200.00 System Integration Fee $20,800.00 1 $20,800.00 Tiburon TC RMS to Inform RMS Data Conversion $49,000.00 1 $49,000.00 Project Related Feels) Total: $296,650.00 Hardware Barcode Industrial Portable Data Terminal $1,215.00 4 $4,860.00 Barcode PolyPro Labels 4"x 2",1110 labels per roll(4 rolls per case) $195.04 1 $195.04 Barcode Printer Resin Ribbon(12) $169.20 1 $169.20 Barcode TB Zebra,GK420T,Printers,4"Print Width $795.00 3 $2,385.00 Hardware Total. $7,609.24 Annual Maintenance Fee(s) (Year 1) CopLogic Interface to Inform RMS 8 x 5 $3,465.00 Inform FBR User 8 x 5 $49,500.00 Inform RMS Accident 8 x 5 $2,352.24 Inform RMS Barcode Handheld Reader Software 8 x 5 $310.50 Inform RMS Evidence and Barcoding 8 x 5 $2,352.60 Amendment 2 to System Purchase Agreement Page 6 of 9 Inform RMS Server Software(D-251-550 Users) 8 x 5 $18,000.00 Inform RMS Test or Training System Maintenance $1,620.00 Inform RMS User 8 x 5 $64,395.00 LiveScan Interface-One Way-Inform RMS to Livescan for Fingerprints 8 x 5 $2,772.00 Annual Maintenance Fee(s)(Year 1): $112,956.82 Continuous Upgrade Fee(s)(Year 1): $31,810.52 Annual Maintenance Feels)(Year 1) Total: $144,767.34 Project Total: $978,816.58 Optional Items .. e IQ 1/2 Day Admin Training(Remote) $700.00 1 $700.00 IQ 1/2 Day End User Training(Remote) $700.00 1 $700.00 IQ Analytics 1 Day Dashboard End User Training(Remote) $1,400.00 1 $1,400.00 IQ Analytics 1/2 Day Reporting End User Training(Remote) $700.00 1 $700.00 IQ Analytics 5 Concurrent User Bundle One Year Subscription $2,500.00 1 $2,500.00 IQ Analytics Set Up Services(Remote) $700.00 1 $700.00 IQ Search(C-41-250 Concurrent Users)One Year Subscription $7,200.00 1 $7,200.00 IQ Setup and Conversion Services(Up to 5 years for TT Products) $1,100.00 1 $1,100.00 NCIC/State Message Switch Server Software-Inform RMS $20,160.00 1 $20,160.00 NCIC/State Software Inform RMS Concurrent User $500.00 225 $112,500.00 Note: The TriTech Software licenses purchased under this Amendment will be added to Client's Software Support Agreement and invoiced with the terms therein. Amendment 2 to System Purchase Agreement Page 7 of 9 CONFIDENTIAL PAYMENT MILESTONES 20% Due at contract signing $195,763.32 20% Due at Delivery and Installation of core RMS Software $195,763.32 25% Due at completion of RMS DOLF $244,704.14 15% Due at completion of Pre-Go Live End User Training $146,822.48 10% Due at RMS Go Live $97,881.66 10% Due at RMS S stem Acceptance $97,881.66 100% Hardware, third-party software and optional items due at time of order Total $978,816.58 Amendment 2 to System Purchase Agreement Page 8 of 9 Exhibit C Initial Project Schedule (Attached) Amendment 2 to System Purchase Agreement Page 9 of 9 Exhibit A Statement of Work (Attached) Amendment 1 to System Purchase Agreement Page 4 of 9 STATEMENT OF WORK City of Fort Worth RMS FINAL TRITECH SOFTWARE SYSTEMS TriTech Software Systems 9477 Waples Street,Suite 100 San Diego,CA 92121 Fax:858.799.1010 Technical Services: 1.800.987.0911 ©2003-2016 TriTech Software Systems Unpublished: Rights reserved under the copyright laws of the United States. All information in this document is proprietary and confidential and owned by TriTech Software SystemsTM. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose,without the express written permission of TriTech Software Systems. Trademarks Microsoft,Windows,Microsoft Access,Microsoft Excel,Microsoft Exchange, and Microsoft Word are either registered trademarks or trademarks of Microsoft Corporation in the United States and other countries. Inform CAD, Inform Mobile,Inform CAD Browser,Inform RMS, Inform Jail,IQ,Analytics, Inform FBR, and Inform CAD GISLink are trademarks of TriTech Software Systems. ArcGIS,ArcMap and ArcCatalog are registered trademarks of Environmental Systems Research Institute (ESRI)in the United States and other countries. Document Control Date Version Details/Changes Author Sept 7,2016 A SOW Template TriTech Sept 9,2016 DRAFT DRAFT D.Doepke The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech Software Systems. ©2016 TriTech Software Systems Table of Contents DocumentControl.....................................................................................................................ii Tableof Contents.....................................................................................................................iii a) Overview..............................................................................................................................1 1.1 Statement of Work.........................................................................................................................................l 1.2 Project Implementation Definitions...............................................................................................................l 1.3 System Acceptance Process...........................................................................................................................2 1.3.1 Functional Acceptance Testing..............................................................................................................2 1.3.2 Integration Testing.................................................................................................................................2 1.3.3 Reliability Acceptance Period...............................................................................................................3 1.4 General Client Responsibilities.....................................................................................................................3 1.5 Project Exclusions.........................................................................................................................................5 2 Project Deliverables............................................................................................................6 2.1 Overview of Project Deliverables..................................................................................................................6 3 - TriTech Project Roles and Responsibility.........................................................................8 3.1 Overview.......................................................................................................................................................8 3.2 TriTech Project Manager...............................................................................................................................8 3.3 Systems Engineer..........................................................................................................................................8 3.4 GIS Analyst...................................................................................................................................................9 3.5 Inform RMS Business Analyst......................................................................................................................9 3.6 Client Installation Services Team..................................................................................................................9 3.7 Technical Services Group..............................................................................................................................9 3.8 Account Executive.........................................................................................................................................9 4 Recommended Client Roles and Responsibilities..........................................................11 4.1 Overview.....................................................................................................................................................11 4.2 Project Manager...........................................................................................................................................11 4.3 System Administrator..................................................................................................................................11 4.4 Inform RMS Administrator.........................................................................................................................12 4.5 GIS Analyst.................................................................................................................................................12 4.6 Inform RMS and FBR Supervisors..............................................................................................................13 4.7 Subject Matter Experts................................................................................................................................13 4.8 Application Trainers....................................................................................................................................13 5 Project Controlling Processes.........................................................................................14 5.1 Overview.....................................................................................................................................................14 5.1.1 TriTech Responsibilities......................................................................................................................15 5.1.2 Client Responsibilities.........................................................................................................................15 5.2 Change Management Process......................................................................................................................15 5.2.1 TriTech Responsibilities......................................................................................................................16 5.2.2 Client Responsibilities.........................................................................................................................16 5.3 Project Reporting.........................................................................................................................................16 5.3.1 TriTech Responsibilities......................................................................................................................17 5.3.2 Client Responsibilities.........................................................................................................................17 5.4 Document Review.......................................................................................................................................17 The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech Software Systems. 02016 TriTech Software Systems 5.4.2 TriTech Responsibilities................................................................................:.....................................18 5.4.3 Client Responsibilities.........................................................................................................................18 5.5 Third Party Management.............................................................................................................................19 5.5.1 TriTech Responsibilities......................................................................................................................19 5.5.2 Client Responsibilities.....................................................................................:...................................19 6 Project Initiation and Planning.........................................................................................20 6.1 Overview.....................................................................................................................................................20 6.1.1 TriTech Responsibilities......................................................................................................................20 6.1.2 Project Kick Off..................................................................................................................................21 7 Project Execution..............................................................................................................22 7.1 Overview.....................................................................................................................................................22 7.2 System Installation(Inform RMS and Interfaces).......................................................................................22 7.2.1 Review Hardware Specifications.........................................................................................................22 7.2.2 Hardware and Equipment Procurement Process..................................................................................22 7.2.3 Hardware Staging and Preparation for Installation..............................................................................23 7.2.4 TriTech Responsibilities......................................................................................................................23 7.2.5 Basic Server preparation and Network Services..................................................................................25 7.2.6 System Installation..............................................................................................................................25 7.3 Implementation of Inform RMS..................................................................................................................28 7.3.1 Inform RMS System Orientation.........................................................................................................28 7.3.2 Inform RMS Base System Code File Entry.........................................................................................30 7.3.3 Inform RMS Administration and Review Training.............................................................................31 7.3.4 Geographical Information Services.....................................................................................................31 7.3.5 Inform RMS Demonstration of Licensed Functionality(DOLF)........................................................32 7.3.6 Inform RMS Workshops.....................................................................................................................33 7.3.7 Inform RMS Functional Acceptance Testing(FAT)...........................................................................34 7.3.8 Inform RMS Data Conversion.............................................................................................................35 7.3.9 Inform RMS Training..........................................................................................................................37 7.4 Inform RMS Integration Testing.................................................................................................................40 7.4.1 TriTech Responsibilities......................................................................................................................40 7.4.2 Client Responsibilities.........................................................................................................................40 7.5 Implementation of System Interfaces..........................................................................................................40 7.5.1 Inform Standard Interfaces' Requirement Gathering and Configuration.............................................40 7.5.2 Custom Interfaces' Requirement Gathering and Configuration..........................................................41 7.5.3 Interface Functional Acceptance Testing(FAT).................................................................................43 7.6 System and Subsystem Go Live..................................................................................................................44 7.6.1 Inform RMS Go Live..........................................................................................................................44 7.7 Reliability Acceptance Period.....................................................................................................................45 8 Project Closure .................................................................................................................47 8.1 System Transition........................................................................................................................................47 9 Appendix B - Contracted Modifications to Standard TriTech Software Products........48 10 Appendix C - Standard TriTech Interfaces......................................................................49 TestEnvironment:...................................................................................................................................................49 11 Appendix D - Custom TriTech Interfaces ........................................................................50 TestEnvironment:...................................................................................................................................................50 12 Appendix E - Subcontractor(s) Statement(s) of Work....................................................51 The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech iv Software Systems. 02016 TriTech Software Systems The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech v Software Systems. 02016 TriTech Software Systems 1 OVERVIEW 1.1 Statement of Work This Statement of Work(SOW)defines the services and deliverables that TriTech will be providing in accordance with the terms and conditions of the System Purchase Agreement(the"Agreement")between TriTech Software Systems(TriTech) and City of Fort Worth("Client"). This project description includes the services and deliverables specified by the Purchase Agreement, including if applicable,TriTech Software and services, Subcontractor activities,Third Party products and services for the implementation of the System and Subsystems specified in the Purchase Agreement (collectively the"Project"). Statement(s) of Work for applicable TriTech Subcontractor(s) are presented in Appendix E- Subcontractor(s) Statement(s)of Work. In some cases,the framework of Deliverables documented by this SOW for this Project is further defined through additional documents such as: Operational Scenario Documents(OSD); Interface Requirements Documents (IRD);User and Administrator Documentation and Training Materials. The number and type of software licenses,products, or services provided by TriTech or its Subcontractors are specifically listed in the Purchase Agreement and any reference within this document as well as Subcontractors' SOWS(if applicable)does not imply or convey a software, license, or services that are not explicitly listed in the Purchase Agreement. 1.2 Project Implementation Definitions Unless otherwise defined herein,capitalized terms within this document have the meanings described in the Definitions section of the Purchase Agreement and where applicable Software Support Agreement. The following terms are used in this document. Since these terms may be used differently in other settings, these definitions are provided for clarity. • Project Schedule means the schedule providing dates and timeframes for completion of tasks and Deliverables during the course of this Project. The Project Schedule is subject to change at the mutual agreement of TriTech and the Client as further described in this SOW. • Project Management Plan means collectively the Communications Management Plan; Risk Management Plan; and Change Management Plan that provide the criteria for managing those tasks within the Project. • The OSD provides an operational description of a capability or feature within the applicable TriTech solution in sufficient detail that both Client and TriTech team mutually agree to the expected deliverable.The OSD provides the"what","how,"and the information flow(including data flow and data elements,when appropriate)of the capability or feature.The OSD does not provide the technical or internal design of how TriTech's Development team will accomplish the requested feature.An OSD will be provided for each contracted product customization to be developed. Once approved by the Client, the OSD becomes the basis for TriTech's development. Once approved, any further changes requested by the Client to the OSD and/or design may incur additional costs to the Client. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech Software Systems. ©2016 TriTech Software Systems Overview • Standard Interface Requirement Document(IRD)defines the functionality of the Standard Interfaces. These documents are standard,published TriTech documents, and are not specific to a Client. 1.3 System Acceptance Process This project shall follow a standard Acceptance Test methodology which is designed to allow the parties to thoroughly evaluate and verify the functionality and reliability of TriTech System and Subsystems.These procedures include several steps that are described in later sections of this SOW.Upon successful completion of these procedures the system is deemed Accepted. 1.3.1 Functional Acceptance Testing Functional Acceptance Testing(FAT) is conducted on each Subsystem prior to conducting End User Training on these applications and staging them for Go Live. The focus of these tests is to verify that each Subsystem meets the functions as described in TriTech's standard FAT documents, which have been created based on TriTech's standard product specifications. The Functional Acceptance Tests are performed based upon'standard TriTech FAT documents and have a standard content and format. These standard FAT documents will be submitted to the Client for review prior to testing. During the scheduled FAT and according to the FAT documents, TriTech and Client project personnel will work to identify any errors where the Subsystem does not conform materially to the FAT documents. Any such errors will be documented by TriTech on the FAT exceptions list.Errors listed on the FAT exception list will be classified as follows: 1) Pre-Go Live Issues: Issues in the Subsystem that prevent the Client from performing normal daily and monthly operations and therefore must be corrected prior to Go Live. 2) Post Go Live Issues: Issues identified in the FAT testing that do not prevent the Client from performing normal daily and monthly processes and therefore can be corrected after the Subsystem Go Live. These issues will not be used as part of the criteria for Acceptance. In the event that the Client chooses not to follow the Acceptance Test processes defined in the Statement of Work, the Client's cutover to live production status(i.e.,productive use)of any TriTech supplied Subsystem constitutes the Client's acceptance of the Subsystem. 1.3.2 Integration Testing Once the FAT is successfully concluded for all subsystems that are scheduled to go live together and in preparation for Go Live,TriTech and the Client will conduct a one-day Integration Test. The Integration Testing for Inform RMS and its subsystems will be conducted based on a number of scenarios that test the records management process.These scenarios include FBR and Interfaces that can be tested in the pre-production environment and are scheduled to go live at the same time. A small group of the Client staff(1-2 Records Clerks and 1-2 Field Officers)will participate in this test with TriTech.TriTech will work with the Client to define a set of test scenarios that test the Records Management System based on The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 2 Software Systems. 02016 TriTech Software Systems Overview the Client's practices. It is recommended that the Client utilize sample incident, arrests,field interviews, citations, and crash reports from their legacy system. 1.3.3 Reliability Acceptance Period As further defined in the Agreement, immediately upon production cutover(Go Live) of the TriTech Subsystems, a thirty(30)day Acceptance Test Period will begin to verify operational functionality in a live environment. If no Critical Priority or Urgent Priority Software Errors (as those terms are defined in Addendum E to the Agreement)are reported during such thirty(30) day period,the Subsystems shall be deemed to have achieved Final Acceptance. In the event that a Critical Priority or Urgent Priority Software Error occurs during the Acceptance Test Period,TriTech shall commence actions in accordance with the Software Support Agreement to correct the reported error. This process is further defined in section 7.7, Reliability Acceptance Period. 1.4 General Client Responsibilities In addition to those Client responsibilities stated elsewhere in this SOW,the Client is responsible for: 1) Electrical facilities (e.g., outlets, generator and other electrical infrastructure facilities)required for this project,including necessary maintenance. 2) Cabling(e.g.,power,network, interface and other electrical and data transmission lines)required for this project,including necessary maintenance. 3) Network/communications connections (e.g., LAN/WAN, commercial wireless,telephone,VPN, and other voice/data connections), or ongoing network/communications charges associated with -installation, operation or support of the proposed system including the establishment and maintenance of security accounts. 4) Configuration and/or programming of network routers, switches and bridges—this includes providing information to TriTech staff on any firewalls within the overall network that the system will operate and necessary port access for the system to operate in accordance with TriTech documentation. 5) The installation,configuration,maintenance(including patch management and upgrades of Microsoft software required by the System. 6) The installation of servers into racks and the connection of such servers to network switches. 7) The assignment of machine names and IP addresses for servers to be utilized by the System. This includes joining the servers to the network and the assignment of security accounts as specified by TriTech documentation. 8) Any hardware and third party software or services necessary for implementing the System that is not listed in the Purchase Agreement as a TriTech Deliverable(not listed as a line item in the Price and Payment section of the Purchase Agreement). This includes workstations, server hardware,network equipment,telephone or TDD equipment,performance test software, Microsoft licenses,Disaster Recovery Software, and services required to extract legacy data and convert into acceptable data formats. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 3 Software Systems. 02016 TriTech Software Systems Overview 9) Configuration,maintenance,testing, and supporting the Third Party Systems that the Client operates and which will be interfaced with as a part of this project. This project includes the contracted Interfaces listed in Appendix C - Standard TriTech Interfaces and Appendix D -Custom TriTech Interfaces. The Client is responsible for maintaining and supporting these systems in good working order. The Client is responsible for providing Application Programming Interface(API) documentation to these systems that document the integration process for the level of interface integration defined by TriTech's response to the RFP, as described by TriTech responses to the RFP as well as Interface IRD and approved OSDs. The Client is also responsible for any cost associated with the development, or configuration of the Third Party System Vendor side of the Interfaces. 10) Consoles, furniture or fixtures as well as any modifications to install equipment used for Systems or Subsystems specified by the Purchase Agreement into existing consoles, furniture,vehicles or existing facilities. Installation of Workstations into consoles, furniture,vehicles or like items, is the responsibility of the Client. 11) Active participation of the appropriate personnel with the necessary background knowledge and availability in the Project implementation meetings and working sessions during the course of the Project. Examples of such implementation sessions are System Orientation,DOLF,Acceptance Testing, Training,regular Project meetings, discussion regarding Interfaces, system installation planning, and the like. 12) The provision of Code Files and GIS data as requested by TriTech staff. This information must be provided on a timely basis in order to meet the project timelines.This information will be provided in a format requested by TriTech staff in accordance with TriTech Documentation. 13) The timely review and approval of Functional Acceptance Testing(FAT) documents, OSDs,IRDS, Task Completion Reports (TCR)and/or other project documentation as further defined in this SOW. 14) Provide a facility with the required computer and audio-visual equipment for training. 15) Timely completion of acceptance testing for each of the TriTech Subsystems. 16) TriTech pricing for this Project assumes that all Client supplied products and services required to support the project will be delivered according to this agreed to Statement of Work,based upon a mutually agreed upon project schedule.This timeline will require a commitment by Client staff to attend project meetings, attend training, and execute action items in a timely fashion. Should the Client find that it is unable to support the agreed to schedule,TriTech reserves the right to execute a mutually agreed to Project Change Order.The Change Order will make the necessary modifications to schedule and/or scope of the project and,if applicable, allow TriTech to recoup any additional costs which may be incurred by TriTech as a result of Client delays. 17) The Client is responsible for providing remote connectivity to TriTech for the purpose of installation, configuration,testing, and troubleshooting of TriTech's applications at the Client site. TriTech's approved remote connectivity methods are described in the System Planning Document. 18) Connect and configure any Third Party hardware(such as Bar Code Scanners,Bar Code Printers, Biometric Fingerprint Scanners, and Signature Pads)to Client workstations,if these services are not explicitly sold in the System Purchase Agreement. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 4 Software Systems. ©2016 TriTech Software Systems Overview 1.5 Project Exclusions 1) TriTech Software Systems provides software applications that it develops. These applications are sold as is and are considered to be"Commercial Off The Shelf'(COTS) software packages.The functionality of these products will be based on TriTech's current design and functionality of these COTS products,unless otherwise indicated in the Purchase Agreement, or if applicable,TriTech's responses to the RFP. 2) Work, software, services,hardware, Systems, Subsystems,product/software modifications, or any other deliverables not explicitly stated in the Purchase Agreement will not be included in the Project. 3) Any modification to TriTech standard products or customizations to such products that are not explicitly stated in the Purchase Agreement are excluded from the scope of this Project. 4) Changes in scope will only be executed through a mutually agreed upon Change Management Process, as described in the Project Management Plan. 5) TriTech is not responsible for the deficiencies in the Client's internal or contracted network to support remote Inform RMS or other subsystem workstations. 6) TriTech is not responsible for the deficiencies in a Client's internal or contracted network to support some of the extended features of Inform Mobile and Inform Field Based Reporting products due to bandwidth or limitations in wireless coverage. 7) TriTech is not responsible for the removal of the old(legacy)equipment,hardware, furniture, consoles,cabling, as part of the Project implementation unless specifically stated in the Purchase Agreement and this SOW. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 5 Software Systems. 02016 TriTech Software Systems 2 PROJECT DELIVERABLES 2.1 Overview of Project Deliverables This project will provide a combination of software and services that comprise the System for use by the Client's Public Safety Organization(s). The individual Subsystems to be provided comprise the overall System. The Purchase Agreement specifies the software licenses included in this Project by the quantity and environment in which licensed. This includes all Server and User Licenses, Standard and Custom Interfaces, as well as other TriTech tools and utilities. The Purchase Agreement for this project incorporates the following: 1) Inform RMS (Production,Test/Training) 2) Inform RMS Accident Module 3) Inform RMS Evidence and Barcoding Module 4) Inform RMS GIS (with CAD) 5) System Interfaces as listed in the Appendices to this SOW Implementation of different components of the System is performed in a series of interrelated processes. Some processes can be performed concurrently while others are sequential in nature.TriTech has implemented process gates to ensure successful completion of tasks in the optimal order before a subsequent activity begins. The only reference for the number and type of software licenses is the Purchase Agreement.Any reference within this document to services associated with a specific software product does not imply or convey a software license for products that are not listed in the Purchase Agreement. 2.1.1.1 Standard TriTech Software Deliverables The functionality provided by Standard TriTech Software Products,including Interfaces(the core TriTech Software and Interfaces without any Modifications)is defined by TriTech Standard documentation such as User and Administration Guides for TriTech's major Subsystems such as Inform RMS. Standard Interface Requirement Documents(IRD) define the functionality of the Standard Interfaces. These documents are standard,published TriTech documents,and are not specific to a Client. Standard TriTech Interface Software to be delivered through this Project is identified as software licenses in the Purchase Agreement. The functionality provided by Standard TriTech Interface Software is defined by TriTech IRDs. Any Modification to the functionality of Standard TriTech Software within the System, or Subsystems, shall follow the Change Management Process as described in Section 5.2, Change Management Process. The scope of the Modification will be described in an OSD. Release of all Modifications to TriTech's Standard Interfaces will follow Subsystem release cycles (i.e.,Inform CAD,Inform RMS, and the like). 2.1.1.2 Contracted Modifications to Standard TriTech Software Products Any Modifications to Standard TriTech Software Products including Inform that are to be delivered through this Project are listed in the Purchase Agreement.The functional scope of any Modification procured through the Purchase Agreement will be summnarized in this Statement of Work and defined by an OSD for all items The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 6 Software Systems. 02016 TriTech Software Systems Project Deliverables listed under Appendix B -Contracted Modifications to Standard TriTech Software Products for Inform RMS and other major TriTech Subsystems; and under Appendix C - Standard TriTech Interfaces, for modifications to Standard Interfaces.Any and all modifications or enhancements that are not explicitly listed in the Purchase Agreement or TriTech's responses to the RFP are not within the scope of this Project. Any changes in the requirements documented in the System OSDs,post approval of the OSDs are subject to formal Change Order. Note: All enhancements and modifications to any of TriTech's Standard products(including the Interfaces)will only be released with a major version of the applicable subsystem(i.e.,Inform CAD,Inform Mobile,Inform RMS,Inform Jail and the like)based upon the relevance and dependency to these products. Note: Software versioning is the process of assigning either unique version names or unique version numbers to unique states of computer software while a service pack or patch is a piece of software designed to fix problems with,or update a computer program or its supporting data. This includes fixing;security vulnerabilities and other bugs. 2.1.1.3 Contracted Custom Interface Software Custom Interfaces to be created by TriTech are identified as individual software licenses in the Purchase Agreement. A high level description of the intended functionality and scope is attached as part of Appendix D -Custom TriTech Interfaces to this SOW.The detailed functional scope of any custom Interface procured through the Purchase Agreement will be defined by an OSD, which will be developed and delivered to the Client during the project. Any changes in the requirements documented in the System OSDs,post approval of the OSDs are subject to formal Change Order. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 7 Software Systems. 02016 TriTech Software Systems TriTech Project Roles and Responsibility 3 TRITECH PROJECT ROLES AND RESPONSIBILITY 3.1 Overview TriTech will appoint a team of specialized personnel that will implement the Project under the direction of TriTech's Project Manager. The team will be multi-disciplinary and the team members may specialize in different products or Subsystems. Team members may be engaged in different phases of the Project as necessary and in some cases are involved in the Project for a limited timeframe.Any personnel changes by TriTech will be discussed with and agreed upon by the Client in advance. Such agreement will not be unreasonably withheld. The descriptions of personnel roles noted below provide an overview of typical Project team members. Other personnel may be involved under the direction of the TriTech Project Manager in order to complete the requirements of the Project. 3.2 TriTech Project Manager TriTech has appointed a TriTech Project Manager as the principal TriTech contact who will be responsible for managing TriTech's responsibilities related to the implementation of the Project,as described in this SOW and within the scope of the Purchase Agreement. The Project Manager utilizes a standardized methodology for project implementation,project management, and risk identification and management. TriTech's Project Manager is responsible for Project scheduling and management of TriTech Project personnel and applicable Subcontractor/supplier resources,budget management, identification and management of Project risks, and communication with the Client's Project team. The TriTech Project Manager will be responsible for the collaborative coordination of Client resources in an effort to ensure that avoidable Project delays will be minimized. The Project Manager is involved in the Project beginning with the SOW development and continuing through post Go Live Project closure activities.The Project Manager will be an active participant in many of the milestone events through the course of the Project including System Orientation,DOLF, and Go Live. The Project Manager will organize a bi-weekly Project status call with the Client and necessary Project team members. Additionally,the Project Manager will provide the Client with a written Project status report on a monthly basis,as further defined in this SOW. 3.3 Systems Engineer The Systems Engineer is responsible for two primary functions,within the scope of the Project: 1) configuration of Standard TriTech Interfaces (including configuration documentation); and 2)development of software requirements documentation for Custom Interfaces. The Systems Engineer will additionally participate in testing of each of these Subsystems. In some cases,Development Engineers may perform the role of the Systems Engineer for specialized interfaces,particularly for Inform RMS and Inform Jail interfaces. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 8 Software Systems. 02016 TriTech Software Systems TriTech Project Roles and Responsibility 3.4 GIS Analyst As part of the implementation team,TriTech utilizes a GIS Analyst that specializes in geographical Information technology. The GIS Analyst is responsible for 1)performing an analysis regarding the Client's GIS source data; 2)consultation services regarding converting the GIS source data for use in Inform RMS; 3)providing training for applicable TriTech GIS tools as included in the Purchase Agreement; 4)preparing the one-time GIS data configuration for the Inform Product Suite. 3.5 Inform RMS Business Analyst Inform RMS and Inform Jail Business Analyst(s)participate in various activities throughout the implementation of each of these Subsystems.They are primarily responsible for conducting the System Orientation with the Client to observe and evaluate the Client's current business practices and make recominendations for improving efficiency and areas that need to be reviewed.They also conduct the Demonstration of Licensed Functionality(DOLF)or Administration Training,perform Acceptance Testing, and provide consulting support throughout the Project implementation life cycle. After the completion of the DOLF session,ownership for continued Code File configuration and maintenance transfers to the Client.At this stage,the Business Analyst will serve as a consultant for the Client's further configuration of the Client's system until the Client's System is in live operation.These activities are described in later sections of this SOW. The Business Analyst will be an active participant in many of the milestone events through the course of the Project and will participate in bi-weekly Project status calls, as needed. 3.6 Client Installation Services Team TriTech's Client Installation Services (CIS)team is responsible for installation and integration of TriTech Software onto the system hardware that is identified for this Project.This team works closely with the Client's staff to coordinate IP and network addressing, security accounts,network connections, and remote access to the System. This process is described in greater detail in Section 7.2, System Installation of the SOW. 3.7 Technical Services Group Customer service functions and technical support for the Client's System during the Project is coordinated by the TriTech Project Manager.After Go Live, TriTech's Technical Services Group is responsible for providing on-going support for the Client's System as defined in the Purchase Agreement and the Software Support Agreement. 3.8 Account Executive The Account Executive is an important resource to the Client throughout the life of their System.The Account Executive will be the primary contact and liaison for non-technical support issues, system changes and billing questions. They provide support for general customer service requests,manage requests for new software and services, and provide assistance with planning teclmology upgrades post System Go Live. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 9 Software Systems. 02016 TriTech Software Systems TriTech Project Roles and Responsibility Having the Account Executive participate as a key Project member provides an enhanced level of continuity for the Client as they continue their relationship with TriTech. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 10 Software Systems. ©2016 TriTech Software Systems Recommended Client Roles and Responsibilities 4 RECOMMENDED CLIENT ROLES AND RESPONSIBILITIES 4.1 Overview Implementation of the Subsystems in a manner that meets the Client's operational needs requires collaboration with the Client's team.In general,the Client's Project team should include staff experienced in the operation and administration of the Client's current public safety technology systems as applicable to the scope of this project. These"subject matter experts"need to be engaged through the course of the Project from initiation until live operations, and may be involved in the support and maintenance of the System and Subsystems after Go Live. These recommendations do not speak to specific positions.Rather,this information defines specific responsibilities and estimated time commitments.The Client may elect to create individual positions, combine responsibilities,and/or assign responsibilities within their current organizational structure. The Client needs to periodically assess its staffing needs based on changes in the Client's operational use of this technology. Often,there is overlap with these core responsibilities -therefore,the team can generally be kept to a small group, dependent upon the complexity of the system being implemented and the number of Subsystems. In addition,it is recommended that the Client,early within the implementation process, identify those persons that will be responsible for the ongoing maintenance of the Client's System to include the technical and business processes. The application Administrators (Inform RMS), as well as the System Administrator, are very key to the success of the Project. It is paramount that the Client develops this team during the implementation process so that the Client successfully achieves a degree of self-reliance with the understanding of each of the Systems in addition to the generalized technical responsibilities. 4.2 Project Manager The Client's Project Manager is the principal Client contact who will manage a team of Client Project personnel. The Client's Project Manager manages and coordinates Client's resources responsible for completing assigned Project tasks and activities. Activities include facilitating Project Schedules and meetings,timely approval and processing of invoices, review and approval of Task Completion Reports("TCRs"),Project management plans, applicable configuration sheets, OSDs and IRDs, approval of the Project documentation and FAT, and management of the Client's staff. Additionally,the Client's Project Manager is responsible for coordinating the efforts, activities, and communications between TriTech and third party vendors that are not TriTech Subcontractors, as well as any deliverables from these vendors to the Project. 4.3 System Administrator The Client's System Administrator is the individual primarily responsible for managing the technical back- end of the System including Windows, SQL Server,network,hardware, data back-ups and log management. This individual is the primary technical point of contact representing the Client. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 11 Software Systems. 02016 TriTech Software Systems Recommended Client Roles and Responsibilities As identified in the Purchase Agreement and the Software Support Agreement, following the initial system installation, administration, and support for hardware(including the software operating system)and network components are the responsibility of the Client.The Client needs to plan for support and maintenance through the development of Client resources, other departments within the Client's organization,or by contracting for such services. The Client should establish procedures for managing warranty service of hardware. Activities for this position include 1)management of Microsoft Windows Operating System including patches and service packs; 2)management of Microsoft SQL Server including patches and service packs; 3) implementation of software prerequisites(in accordance with TriTech Documentation)on computers as needed for current operations and System upgrades; 4)monitoring,management and maintenance of the Client's network including LANs, WANs,wireless networks, security accounts and support connectivity(in accordance with TriTech Documentation); and 5)hardware maintenance and troubleshooting; file and data back-ups and software and error log management. Time commitment will vary with the number of computers on the system,the complexity of the network (including the use of a WAN) and the number of personnel to be managed in network access. If the System LAN is connected to the Client's administrative LAN/WAN', coordination will be important to avoid problems with the Client's network traffic. Personnel involved in System Administration should attend the applicable TriTech System Administrator Course(s).Where a large team is involved, a core team should attend a System Administrator Course and then the Client's System Administration team should conduct a smaller version of the training for local staff. 4.4 Inform RIVIS Administrator The Inform RMS Administrator will have the responsibilities for the implementation, configuration, and maintenance of TriTech's Inform RMS and Inform FBR. This person or persons will be engaged in the implementation of the TriTech's Inform RMS, and will participate in making decisions as it relates to implementing the TriTech's Inform RMS and Field Based Reporting. Inform RMS Administrator will attend the Inform RMS DOLF during the course of the Project.This person should have a comprehensive understanding of the internal structure and workflow of Inform RMS and Inform FBR users, departmental policies and procedures as well as how the records department interacts with dispatch and field operations personnel. The Inform RMS Administrator will be responsible for building and maintaining the RMS Code Files. Additional activities include TriTech software setup,assignment, and management of the agency specific Code Files, evaluation and implementation of version updates,reporting,prioritization, and management of support issues. Within the Multi-Agency environment, separate local RMS administration staff may be required to manage the components used by each Agency-under the direction of an overall Central RMS Administrator. Any personnel involved in RMS administration should participate in the DOLF session so they are prepared to maintain the RMS Code Files post DOLF. 4.5 GIS Analyst The GIS Analyst is responsible for the mapping components required for Inform RMS. Activities include providing the initial GIS files to TriTech for analysis.The GIS Analyst will be responsible for working with TriTech's GIS Analyst to implement mapping components for Inform RMS. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 12 Software Systems. 02016 TriTech Software Systems Recommended Client Roles and Responsibilities During scheduled activities,the Client should have a fully dedicated person or persons.Post implementation workload is based upon the number and type of GIS data edits that will be necessary for the local operations. 4.6 Inform RMS and FBR Supervisors Input from the Users/Supervisors is important to ensure that the configuration settings approved by the Client's team will be perceived as usable by users of the each of the Subsystems.These Users/Supervisors should participate in meetings defining and evaluating the requirements and configuration of their respective products, such as System Orientation and Administration Training. During scheduled activities,the Client should have a fully dedicated person or persons.Post implementation should be maintenance only. These personnel should attend the applicable User trainings. 4.7 Subject Matter Experts Input from subject matter experts in all applicable areas (Inform RMS,Inform FBR and each of the Interfaces and external Systems that integrate with TriTech Systems) is essential to successful implementation of the system.The subject matter expert(s)in each area are the individuals who are knowledgeable about the current operational and technical specifications of the system,the data flow between and among different applications, and any limitations associated with each application. For Standard and Custom Interfaces, subject matter experts may be from the Client Agency, and third party vendors. If the vendors are not TriTech Subcontractors,the Client will be responsible for engaging them in necessary discussions and documentation of the requirements. The Client should involve a fully dedicated person or persons during the scheduled activities, such as requirements analysis, demonstration of the applications (if applicable),review of requirements documentation,the testing process, and other events that are described in later sections of this SOW.Post implementation,the involvement of the subject matter experts should be limited to maintenance only. 4.8 Application Trainers A team of trainers is needed for training the Client staff on TriTech Software on an on-going basis.Trainers will be responsible for reading TriTech Software release notes and maintaining an understanding of new and existing features. The Client should involve a fully dedicated person or persons during scheduled activities such as training sessions.Post implementation,the involvement of the subject matter experts should be limited to maintenance only. These personnel should attend the applicable product specific training courses. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 13 Software Systems. 02016 TriTech Software Systems 5 PROJECT CONTROLLING PROCESSES 5.1 Overview Project Controlling Processes are established early in the Project life cycle during the Planning Phase and described within the Project Management plans.Project Control is the process that includes completing regularly scheduled Project progress meetings and the use of regularly delivered Project progress reports, as well as implementing the processes needed for Communication Management,Risk Management,and Change Management. The process begins during the initiation process and concludes at the end of the Project. The establishment of defined processes for Client communication(contact persons and reporting methods) provides a basis for effective and regular communication.This supports the previously noted processes necessary for successful Project outcome. As part of the Controlling Processes,TriTech utilizes a series of measurements and management reviews to mitigate the effect of these variances. Checkpoints or milestones are planned into each phase of the Project to measure performance and determine if the Project is ready for the next phase. Checkpoints are key tasks that act as gates to the next phase of a project. A delay in a milestone may cause a delay in starting or completing subsequent tasks; in effect creating a risk to the overall Project.Therefore, TriTech's Project staff closely monitors checkpoint tasks and milestones and promptly notifies the Project Manager of any delay or failure with a milestone task.Milestone delays on the part of either party will trigger an overall review of Project activities so that risks can be assessed and properly managed. In the event that either party becomes aware of a delay,notification shall be provided to the other party as soon as reasonably possible. Evaluation of overall Project status at each checkpoint is essential to ensure that the Project is effectively progressing toward completion and that new risks are not being introduced. In many cases,Project activities leading to a checkpoint are interrelated to later scheduled tasks. Success at checkpoints diminishes the risk to the Project going forward. Incomplete actions at a checkpoint may prompt delays and a rescheduling of the Project. For example, delays in completing or approving Custom Interface OSDs will delay the start and completion of the Interface development work,which may ultimately have an impact on the projected Go Live date. Depending upon the importance of the Deliverable,these kinds of delays can have a cascading effect upon the Project Schedule including training and Go Lives. As part of the Project controlling process,upon completion of significant milestones and or tasks,TriTech will submit a Task Completion Report("TCR")to the Client. The TCR serves as a formal tool for the purpose of verifying with the Client that the work has been performed, services rendered, and products delivered according to the requirements specified within the SOW and/or related documents. TCRs are presented to the Client by TriTech's Project Manager for signature. Some TCRs may trigger a Project payment,in accordance with the payment terms within the Purchase Agreement.Upon execution of a TCR that is tied to a Project payment milestone,the Client will receive an invoice from TriTech's Accounting Department which must be paid based on the terms and conditions of the Purchase Agreement. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 14 Software Systems. ©2016 TriTech Software Systems Project Controlling Processes The TCR will include the following information: 1. Description of Work performed and products delivered. 2. Comments noting any special circumstances. 3. Product/Service deliverables listing the contract line items that are being recognized as delivered and will be invoiced. 4. Related Payment Terms in accordance with the Purchase Agreement, for contract line items that will be invoiced relative to the TCR. 5.1.1 TriTech Responsibilities a) TriTech will prepare and submit TCRs for Client's signature upon completion of the applicable task. b) The TCR will cite the appropriate SOW reference. e) TCRs that trigger a payment will include the payment amount in accordance with the Purchase Agreement payment schedule. 5.1.2 Client Responsibilities a) Client will review and approve(or provide the necessary direction to be approved)TCRs within a five (5)business day period from the time of receipt less any challenges to the validity of the report. b) In the event that Client disagrees with a TCR, Client shall submit to TriTech a written explanation detailing why the Client believes that the subject of the TCR and/or tasks have not been completed in accordance with the Purchase Agreement or this SOW. Such notification from the Client shall be provided to the TriTech Project Manager within five(5)business days of receipt of the TCR. 5.2 Change Management Process Either party can request changes to the scope of the project at any time. Since a change may affect the price, project deliverables,this SOW,the supporting project schedule, and/or the terms of the Purchase Agreement for this SOW,both parties must approve each change in writing and agree on the impact each change may have on the Purchase Agreement and related attachments. The purpose of the Change Management Process is to manage any significant changes to the Project as described in this SOW or related documents as referenced within the SOW. These changes may include,but are not limited to a modification to Project scope, Standard or Custom products' functionality, TriTech and Client's identified roles and responsibilities,Project payment terms, and modifications to the scope or delivery location of services within the Project.All significant changes must be documented through the Change Management Process. The type of documentation needed will depend on the nature and significance of the change. A Project Change Order will be the vehicle for communicating and approval of the changes.Whether initiated by the Client or TriTech,all Change Orders will be documented by the TriTech Project Manager.The Change Order shall describe the requested change,the party requesting the change,and the effect the change will have on the project,including the price,project deliverables,this SOW,the supporting project schedule, and/or the terms of the Purchase Agreement for this SOW. All Change Orders must go through the TriTech's internal approval process before they can be presented to the Client for review and approval. Once the Change Order is generated, the Client Project Manager and The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 15 Software Systems. ©2016 TriTech Software Systems Project Controlling Processes TriTech Project Manager will review the proposed change and communicate as necessary to answer any questions,and/or work to resolve any issues preventing acceptance of the Change Order by both parties.Upon the approval by both parties the Change Order will be authorized for implementation. The creation of some Change Orders may, depending upon the scope of the requested change,require fees in order for TriTech to properly investigate and scope of the requested change. If additional fees are required by TriTech to create a Change Order, those fees will be identified and communicated to the Client Project Manager prior to TriTech's investigation of the requested change. In such situations, TriTech will only proceed with the investigation required to create the Change Order if the Client has agreed to pay the additional fees associated with creation of the Change Order. Additional deliverables or Project deletions in terms of Software and services will require a mutually agreed upon Change Order. It must be noted that the later in the Project that a change is requested,the greater the likely impact in terms of costs,risks, and timescale.It is recommended that the Client not delay any review activity as it is a best practice to discover potential changes as early as possible.In some cases,it may be more appropriate to plan modifications for post Go Live delivery. 5.2.1 TriTech Responsibilities a) Change Orders will be prepared for submission to the Client when required. b) Where Project changes require Engineering-level modifications,TriTech will perform requirements capture necessary to prepare required documentation including a high level description of the change for Client review and approval. c) Where Project changes require Engineering-level modifications, Client will be informed of the delivery mechanism(version and schedule). 5.2.2 Client Responsibilities a) When applicable, the Client will identify the services or deliverables that will be subject to a Change Order,per the Purchase Agreement between both parties. b) When applicable, the Client will identify changes to features or functionality related to Inform RMS, Interfaces, or any other Subsystems that will require a change order. This process may also include participation with the requirements process. c) Client will process Change Orders in a timely manner. There may be a reason not to approve, ie needing correction etc 5.3 Project Reporting TriTech will provide Monthly Status Reports advising the Client Project Manager and key Client Project Stakeholders of the progress and status of project activities.This report will include the significant accomplishments,planned activities, issues,and potential risks associated with TriTech and TriTech's Subcontractors' Deliverables. The Project Status Reports will include the following: a) Accomplishments during the Reporting Period. b) Planned upcoming activities. c) Issues. d) Risks. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 16 Software Systems. 02016 TriTech Software Systems Project Controlling Processes e) Key Action Items. In addition,the TriTech Project Manager will hold bi-weekly status meetings/conference calls to update the Client on the status of the Project and key action items and deliverables. During the course of the Project, one or more Project journals will be created to document Project issues and action items.These journals are generally product specific and are used by the Project Manager and other team members to facilitate successful Project completion.Project journals are reviewed with the Client during bi-weekly Project status calls and on an as needed basis through the course of the Project.The Project Manager is responsible for periodically providing copies of updated journals. TriTech will provide an updated Project Schedule advising the Client Project Manager of the progress of project activities.The Project Schedule may be lacking the detailed tasks for the Client team, and the Client may add such tasks, owners, and durations to the Project in collaboration with TriTech Project Manager.The Project Schedule will consist of the following: a) Major Tasks. b) Task Responsibility. c) Task Duration. d) Major Milestones. e) Tasks Completed. f) Tasks in Progress. 5.3.1 TriTech Responsibilities a) Provide a written report of Project status once a month. b) Track issues and action items to closure through product specific journals.The Client will be periodically provided with updated copies of the journal. c) Conduct status meetings/conference calls every two weeks. d) Maintain an up-to-date Project Schedule. 5.3.2 Client Responsibilities a) Review the written report of Project status and provide feedback within five(5)business days in order to ensure that the documentation is correct. b) Participate in Project status meetings. c) Ensure participation of personnel in tasks and meetings. 5.4 Document Review In the course of the Project,TriTech will deliver several documents to the Client for review.These documents will include but are not limited to the Acceptance Test Procedure, Project Schedule, DOLF report, OSD, and The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 17 Software Systems. 02016 TriTech Software Systems Project Controlling Processes Interface Requirement Documents for the Project. Approved documents are returned to the TriTech Project Manager. All documents will be provided in electronic (soft copy). If Client desires printed (hard copy) documentation, it is their responsibility to print and bind the desire copies.The TriTech Project Manager will retain a copy and provide Client with a copy. Should the Client find any document unacceptable,the Client must provide specific reasons in writing to the TriTech Project Manager. TriTech can then assess any required corrective measures and make revisions or modifications to provide acceptable documents wiihin a mutually satisfactory timeframe. Status Reports are not subject to approval. In order to ensure compliance with the Project Implementation Schedule,the Client is responsible for the review of such documents and providing any comments to TriTech within five(5)business days. 5.4.1.1 Documents Subject to Client Approval a) Change Orders b) Operational Scenario Documents (OSD) c) Application Configuration Sheet d) Functional Acceptance Test Procedure documents e) Task Completion Reports 5.4.1.2 Documents Subject to Client Review not Requiring Approval a) Project Schedule Note: The Project Schedule and any changes shall be mutually agreed upon between the Client and TriTech. b) Project Status Reports e) DOLF Reports for Inform RMS d) Project Journals e) Interface Requirements Documents (IRD) 5.4.2 TriTech Responsibilities a) Distribute the documents to the Client. b) Coordinate the process to consolidate comments and edit documents. c) Manage the signoff process for applicable documents and the distribution of originals to the Client and TriTech for filing. 5.4.3 Client Responsibilities a) Review the documents presented and provide the appropriate information back to TriTech within five(5) business days for configuration sheets, Change Orders and/or Sales Orders. b) Review the documents presented and provide the appropriate information back to TriTech within ten (10)business days for requirements documents defined above.Unless unanticipated changes to the Project Schedule would warrant a shortened turn around,then Client shall review as soon as is reasonably practicable The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 18 Software Systems. 02016 TriTech Software Systems Project Controlling Processes 5.5 Third Party Management TriTech will be responsible for the management of third parties that have been identified as Subcontractors or executed Change Orders to the Purchase Agreement.The identified TriTech Subcontractors under the Contract are the following: 1. None As part of the Subcontractor agreement, all communications between those third parties and the Client will be managed by TriTech.Any communication directly between the Client and third parties that may require or imply the promise of a material change in scope or responsibilities will not be acknowledged by TriTech unless an appropriate Change Order has been prepared. Conversely, the Client will be responsible for the management of third parties that TriTech is not responsible for.The Client will be responsible for the facilitation of discussions and the acquisition of materials from those third parties that are necessary for the configuration and development of the Client's System. 5.5.1 TriTech Responsibilities a) Assume responsibility for third parties that are the responsibility of TriTech within the terms of the Purchase Agreement between TriTech and the Client. b) Process any Change Orders that may arise from a material change in scope where thud parties are concerned. c) Inform the Client when configuration and or programming will require interaction and/or documentation from a third party which is not the responsibility of TriTech under the Purchase Agreement between TriTech and the Client. 5.5.2 Client Responsibilities a) Work directly through TriTech with regard to third parties that are the responsibility of TriTech. b) Review, sign and process any Change Orders that may arise from a material change in scope where third parties are concerned. e) Facilitate interaction between TriTech and third parties not the responsibility of TriTech to include conference calls, answers to questions and documentation as requested. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 19 Software Systems. 02016 TriTech Software Systems 6 PROJECT INITIATION AND PLANNING 6.1 Overview Project Initiation and Planning involves gathering the necessary Project specific information in order to produce a Project Management Plan and a Project Schedule. In short,Project Planning consists of those processes designated to establish when and how the Project will be implemented while further elaborating on Project Deliverables.Most of the information exchange between the Client and TriTech during this process is at a high level and consists of interaction between both Project Managers and a small group of Project stakeholders. Major Deliverables for the Project Planning phase are the specific Project Management Plans,and a baseline Project Schedule. The project must be managed in a manner that will allow for the adjusting the Project Management Plan and Project Schedule to address the circumstances that affect a project during Project Execution. As a result of these changes during the Project life cycle,Project Planning will overlap each subsequent process during the Project. Typically,Project Planning tasks will decrease in frequency as checkpoints are successfully completed and as the Project nears Go Live and Project completion. Note: The Project Schedule is a living document,subject to change during the course of the Project due to several factors such as change in Project scope,scheduling conflicts,delay in approving ;project documents,resource availability,etc. All changes to the Project Schedule will be discussed between both parties and shall be incorporated within a publishedschedule upon written approval from the Client and TriTech. 6.1.1 TriTech Responsibilities a) Assign a Project Manager to the Project to participate in Initiation phase activities. b) Produce required documentation to support Initiation activities(such as Standard IRDS, System Planning Document,etc.) c) Review and finalize the SOW with the Client. d) Identify and engage the TriTech Project team responsible for carrying out Project Execution. e) In collaboration with the Client, develop the Project Management Plan(includes the Communication Management Plan,Risk Management Plan, and Change Management Plan). f) Baseline the Project Schedule. CF g) Prepare and submit the TCRs for Client acceptance of the Project Management Plan as defined above. h) Develop and submit invoice for payment due at execution of the Purchase Agreement. 6.1.1.1 Client Responsibilities a) Assign a Project Manager for the Project to participate in Initiation phase activities. b) Identify and engage the Client's Project team. c) Review and comment on the TriTech Project Management Plan and the Project Schedule. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 20 Software Systems. 02016 TriTech Software Systems Project Initiation and Planning d) Review and comment on TriTech provided documentation to support Initiation activities. e) Finalize and approve(or provide the necessary direction to be approved)the SOW with TriTech. f) Approve(or provide the necessary direction to be approved)the TCRs for the Project Management Plan within 5 business days. 6.1.2 Project Kick Off' During the planning phase,the TriTech Project Manager will hold a Kick-Off meeting with the Client's Project team.During the Kick-Off meeting,the TriTech Project Manager will provide an overview of the following: 1. The TriTech Project Execution Process. 2. A high-level description of Project Deliverables. 3. Roles and responsibilities for the Project team members. 4. A high level review of the preliminary Project Schedule including projected Project milestones and checkpoints. 5. Describe the work that has been either completed, is in progress or is due to begin within the immediate future. 6. Review any project related questions from the Client's team. 6.1.2.1 TriTech Responsibilities a) Prepare the agenda and set a date for the Kick-Off that is convenient and agreeable to the Client and TriTech Team. b) Distribute any documents that the Client should review in advance of the Kick-Off meeting. c) Conduct the Kick-Off meeting. 6.1.2.2 Client Responsibilities a) Work with the TriTech Project Manager to facilitate scheduling a date for the Kick-Off meeting. b) Schedule the appropriate personnel from the Client's team to attend. This should also include key stakeholders that may not participate routinely in Project operations,but who have authority or responsibility over the Project. c) Provide adequate accommodations to include adequate seating and audio-visual equipment including a projector(s), screen, and whiteboard. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 21 Software Systems. ©2016 TriTech Software Systems 7 PROJECT EXECUTION 7.1 Overview Project Execution focuses on the development and delivery of Project Deliverables. Processes will be iterative and consist of. 1)a review of Deliverable documents; 2)Development, configuration,Installation and testing of software and hardware deliverables,and 3)Delivery of Project related services such as Project related training.These processes are iterative in nature with a number of checkpoints to evaluate Project progress and where applicable,to initiate Change Management processes. Each Deliverable has a closing process which consists of specific completion criteria. These Deliverable closing processes are independent from the closing process of the Project. 7.2 System Installation (Inform RMS and Interfaces) System installation is one of the early processes in the Project implementation phase, and has a great impact on and critical dependency on a number of key activities. All tasks and activities related to System Installation are included in this section and will occur in the order presented. Note that other project activities can occur concurrently or between these steps. 7.2.1 Review Hardware Specifications TriTech and Client will review the specifications to ensure that the correct hardware and third software components are procured and installed. TriTech will only be responsible for procurement of the hardware and third party software that is explicitly listed under the Agreement as TriTech Deliverables or Deliverables of TriTech's Subcontractors. 7.2.1.1 TriTech Responsibilities 1) Provide hardware and Third Party specifications to Client. 7.2.1.2 Client Responsibilities 1) Review and validate hardware and Third Party specifications. 7.2.2 Hardware and Equipment Procurement Process Client will procure hardware,third party software,and equipment per TriTech's recommended Specifications. TriTech is only responsible for procurement of the hardware and third party software that is identified as TriTech Deliverables in the Purchase Agreement. If the hardware and third party software is procured by the Client,it is the Client's responsibility to procure the required equipment based on TriTech approved specifications, and to ensure the timely delivery of the hardware and third party software to the site to allow timely implementation of the System and Subsystems. Where the Client is responsible for procuring the server hardware,the Client will be responsible for completing the following steps: 1) Fully configuring the servers with memory and disks. 2) Loading Microsoft Windows or VMware. 3) Partitioning disk drives partitioned and the implementing applicable Raid level based upon TriTech documentation. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 22 Software Systems. 02016 TriTech Software Systems Project Execution 4) Assigning the computer name and IP address based upon TriTech documentation. 7.2.3 Hardware Staging and Preparation for Installation The Client will be performing basic server integration for all servers. Basic server integration includes placing the servers in the racks,joining them to the existing domain,with the Domain Controller in place, running the TriTech pre-requisite DVD on the Inform RMS servers, and establishing remote connectivity capability(VPN and Remote Desktop)for authorized TriTech personnel to perform configuration. These activities will be coordinated between TriTech and the Client IT staff. Guidance will be provided by TriTech's Client Installation Services (CIS)team as required.If the Client is not willing to complete the basic server integration,this task may be performed by TriTech or TriTech's Subcontractors at additional cost. In order to start configuration,the Client must provide remote connectivity to TriTech. The Client must also provide the server names,IP addresses,Administrator Account Information(User Name,Password), Services Account Information, and the location of 3'Party Software media(such as SQL).An Installation Sei vice Request(ISR)will be provided to the Client that organizes this information in to the TriTech preferred format.The Client is responsible for providing the completed ISR to TriTech no later than two (2) weeks prior to the installation activities. The Client is responsible for ensuring that the site is prepared and ready for the installation of hardware, third party software,and TriTech software as detailed in TriTech's documentation including the System Planning Document no later than two(2)weeks prior to the scheduled Installation date. Delay in providing this information in its complete form will result in a delay in the Installation and the activities that follow installation of the System. At least one(1)week prior to installation,a member of the TriTech CIS team will verify: (1) connectivity to the Client site via VPN, (2)connectivity to each of the servers, and(3) access to all required security accounts. If the servers, accounts and connectivity are not ready the Project may be rescheduled, which may have an impact on the overall Project timelines. 7.2.4 TriTech Responsibilities a) Provide the System Planning Document. b) Facilitate a hardware review prior to hardware/OS procurement. c) Procure equipment and third party software if included in the Purchase Agreement as a TriTech deliverable. d) Provide guidance and assistance as necessary if the system equipment is procured by the Client. e) Distribute the Installation Service Request(ISR) document to the Client. f) Assist the Client in completing the ISR. g) Assist the Client with the preparation of a network diagram. h) Review the completed ISR prior to the installation. i) Test the remote connectivity to the site prior to installation of the hardware and software. j) Install the Microsoft SQL software. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 23 Software Systems. ©2016 TriTech Software Systems Project Execution k) Prepare and submit a TCR for Client review and approval upon completion of these activities. 7.2.4.1 Client Responsibilities a) Complete the Installation Service Request(ISR) document and provide to TriTech. b) Prepare a network diagram and provide to TriTech. c) Perform site preparation,as specified in the System Planning Document and ISR. d) Assign the computer name(s)and IP address(es)based upon TriTech documentation. e) Establish remote connectivity capability(VPN and Remote Desktop) for authorized TriTech personnel to perform software installation and configuration. f) Run TriTech Pre-Requisite DVD on all applicable Inform servers prior to any installation work being performed. g) Provide all horizontal and vertical cable runs,pathways, coring, access points, floor cutting or drilling, and related tasks related to cable and equipment installation. h) Provide all Client-supplied telephone, external interface connection points,electrical power and other receptacles within manufacturer recommended distance of the equipment and all peripheral components. i) Provide and install all data communication lines,modems,hubs and routers, cabling, equipment and other components necessary for system operation and maintenance and for remote sites and connection to other systems. All lines will be clearly identified and tested. j) Provide TCP/IP communications and connection to the hub equipment provided in support for any existing networks, workstations and printers that are to have access to the TriTech applications. k) Obtain all necessary IP addresses and schemes. 1) Allow remote access to TriTech to all development and system"root"accounts on all servers running TriTech licensed Software. m) Procure equipment and thud party software if it is the responsibility of the Client according to the Purchase Agreement. n) Install operating system software for Client procured hardware unless the service is specified as a TriTech responsibility in the Purchase Agreement. o) Perform basic server integration including,but not limited to: i. Installation of servers in applicable racks. ii. Joining servers to the existing domain with the domain controller in place. iii. If applicable, install and setup of the VM environment. p) Provide TriTech with all necessary configuration documentation which includes machine naming, IP addresses,Administrator Account information, Service(s)Account information,naming convention, and connectivity as prescribed. q) Provide TriTech with a high level network diagram.The diagram should be provided prior to TriTech Software installation. r) Install all peripheral equipment, including scanners,printers,barcode readers, etc. s) Approve the applicable TCR. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 24 Software Systems. 02016 TriTech Software Systems Project Execution 7.2.5 Basic Server preparation and Network Services Performing the services listed in this section is a responsibility of the Client. If these services are explicitly included in the Purchase Agreement,TriTech or a TriTech Subcontractor will implement 31 party software and/or hardware solutions based upon the following task list.These solutions can include but is not limited to, SAN,Citrix,VMware,and Domain Controller configurations.These services can be performed on site or remotely via a VPN connection.These services will be performed at additional cost to the Client and are not included in TriTech's standard installation services. 7.2.5.1 Client Responsibilities a) Provide the facility suitable to house Server hardware and network infrastructure. b) Have a member of the Client's IT staff available while software/network configuration is being performed. a) When deploying a SAN, configure the applicable RAID configuration, create the LUN(s) and present them to the physical or virtual servers. b) If the VM servers are not procured through TriTech,the Client is responsible for building individual servers. c) When deploying a VMware solution, install the VMware operating system, connect physical host servers to a SAN if applicable,configure vCenter, create a VM Template for Interfaces and business servers, and configure vMotion and High Availability(HA)if applicable.The Client is also responsible for building individual VM servers. d) If required, deploy the Domain Controller by adding the member server to an existing Domain or create a new Domain,promote the member server to Domain Controller, enable and configure DNS, enable and configure DHCP if required. e) Create domain account(s)for TriTech's remote support connectivity and access so that TriTech can assist Client with installation and ongoing maintenance f) Perform all necessary network configurations,to include but not limited to determining the network design routing protocols, subnet mask,redundancy,router and switch configuration. g) Create Networking/Server documentation to illustrate intended configuration. Note: 'VMware,vMotion and HA require a SAN or a way to present'shared'storage to the physical host servers in a VMware virtual faun. Note:Network and Server security are always a responsibility of the client: 7.2.6 System Installation Once the Client have prepared the site based on TriTech documentation, to include the System Planning Document and the applicable ISR form is completed, a TriTech Client Installation Services specialist will perform the TriTech installation services. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 25 Software Systems. 02016 TriTech Software Systems Project Execution These services will be performed remotely,unless otherwise specified in the Purchase Agreement,and include installation of the contracted TriTech Software products on the quantity of servers and workstations as specified in the Purchase Agreement. These installation activities will be coordinated between TriTech and the Client. Notel: All SQL server licenses will be installed by TriTech.The Client is responsible for making the media and license keys available to TriTech for the installation. Note 2: The Installation services for different components of the System may be performed at different times,based on the implementation and deployment timelines for each Subsystem. Note 3: The scope of installation services and the number of servers and workstations to be installed and configured by TriTech is limited to the servers and workstations that have been explicitly: listed in the Purchase Agreement.If the Client has been granted Site Licensing for selected TriTech Software,TriTech is only responsible for the initial installation services,and installation of additional seivers'will be subject to additional charges. Note 4: If Client does not follow the processes and procedures detailed in the TriTech System Planning Document and this results in a need for reinstallation of the hardware or software, the reinstallation effort will be performed at additional cost to the Client. Note 5 At TriTech's discretion,TriTech may perform installation activities for certain components of the system on-site. The following pre-requisites must be in place prior to the start of TriTech Software installation: a) Site preparation is complete as outlined in the sections above. b) Hardware has been installed at Client site. c) Client has provided TriTech with remote connectivity to all applicable servers. d) Client had provided TriTech all relevant documentation as outlined in the sections above to include licensing keys, IP addresses,username/passwords, and the completed ISR. 7.2.6.1 TriTech Responsibilities a) Install and configure Microsoft SQL to operate with each of the applicable TriTech product(s). b) Configure the System servers in the applicable environments (Production,Test,Training, and Disaster Backup environments,if provisioned by the Purchase Agreement). c) Install and configure the Inform RMS on the designated servers and applicable environments as specified in the Purchase Agreement. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 26 Software Systems. 02016 TriTech Software Systems Project Execution d) Provide verbal support to the Client with self-installation procedures for the workstations using the TriTech provided Prerequisite Installation DVD and applicable Launch configurations. e) If applicable, create data dumps for Microsoft SQL database backups (as a backup for Inform RMS databases). f) After completion of the initial installation and configuration of Inform RMS, a member of Technical Services team provides a technical hand-off to designated staff from the Client's information Technology team via a conference call. The following major topics will be discussed during this technical hand-off- i. Proper procedures for performing System Backups: o File Structure—Inclusions and exclusions o Databases o Moving Backups to media ii. Proper procedures for refreshing Test/Training system(and related documentation) iii. Approved configuration and use of Virus Scan software iv. Approved procedure for application of Windows updates V. System Upgrade process and procedures vi. Support Website and TriTech list server access Vii. Managing/Reviewing system logs(RMS, SQL and Event Logs) g) Prepare and submit a TCR upon completion of the installation tasks and activities. 7.2.6.2 Client Responsibilities a) Allocate appropriate onsite Project personnel to support TriTech personnel during configuration tasks as necessary and designate a primary point of contact to be available to address and answer questions that arise during the installation of the baseline application software. Appropriate Client personnel include the necessary IT personnel and database administrator(s)as needed during installation. b) Complete the configuration of workstations(after the installation of the limited number of workstations by TriTech)using the Prerequisite Installation DVD and applicable Launch configurations. e) Put in place TriTech's recommended backup procedures as outlined in the System Planning Document and ensure backup procedures are consistently follow beginning at the completion of this task. d) Install and configure virus scanning software as outlined in the System Planning Document. e) Provide Web Security Certificates for all TriTech web-enabled applications that require a certificate. f) After completion of the initial installation and configuration of System servers,the Client will be responsible for maintaining the System based on TriTech System Document, and the technical hand-off from TriTech Technical Services department. Specifically,the Client's IT staff is responsible completing the following activates related to Inform Subsystem servers: o Updating Training/Test Systems with fresh data(from Production)as needed o Continued updating and monitoring of virus scan software o Application of Windows updates The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 27 Software Systems. 02016 TriTech Software Systems Project Execution o Following the procedures for System Upgrade o Managing/Reviewing system logs (SQL and Event Logs) o Management of Microsoft and other Third Party Software include patch applications and upgrades as needed for new Subsystem versions. o Deployment and use of the Prerequisite Installation DVD for Subsystem upgrades as required. g) Review and approve (or provide the necessary direction to be approved)the applicable TCRs. 7.3 Implementation of Inform RMS Inform RMS (to include FBR if purchased) is implemented through a series of standard steps and process gates.These steps are designed to ensure that the operational needs of the Client are identified,the configurations are verified, and the system is tested to validate the proper functionality of the system prior to deployment. The following sections describe the implementation process for Inform RMS. 7.3.1 Inform RMS System Orientation The Inform RMS System Orientation is conducted at the Client's site and led by a TriTech Business Analyst. The duration of the Inform RMS System Orientation is generally up to eight(8) days and includes a Business Process Review of the Client's operations. Some key discovery points for the Inform RMS System Orientation are as follows: a) Work Flow—Understanding the setup for work flow processes from the field report to the State Submission. This may include time observing Departmental Divisions(such as Records Staff, Investigation,Property and Evidence, and the like)and Ride-Alongs with field units. b) Review reporting requirements(reporting segmentation and the like). c) Event numbering(Incidents) including master incident numbers and case numbers. It is recommended that the number of attendees in the System Orientation is limited to 10-15 to allow for more effective communication during the session. Based on the key discovery points during this session, it is necessary that the attendees include individuals who can properly address these key points and make configuration decisions. During the System Orientation session,the Business Analyst will facilitate an operational review of Inform RMS (to include FBR if purchased)by demonstrating various System functionality and start gathering the configuration information. A System Module Setup worksheet(SMS) and other reference material will be provided to the Client to assist in gathering the required Code Files. Information that cannot be produced during the meeting must be sent to TriTech as specified by the mutually agreed upon schedule. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 28 Software Systems. 02016 TriTech Software Systems Project Execution Note: The Client's provision of Code File information is an early Project checkpoint.Remote Web sessions will be scheduled as a follow up to System Orientation to guide the Client through the Code File data collection process.This information is needed to prepare the DOLF and incomplete,inaccurate or delayed Code File information can have a cascading effect on the Project Schedule., 7.3.1.1 TriTech Responsibilities a) Schedule the System Orientation meeting in accordance with the Client's availability and the Project Schedule. b) Prepare and distribute the meeting agendas and documents for Client review or completion two weeks prior to each meeting. c) Conduct the meetings based on the distributed agenda. d) Document the Client's requirements and configuration specifications resulting from the System Orientation discussions. e) Send the System Module Setup worksheet(SMS) and other reference material to the Client. f) Document and assign owners and due dates to any action items and track all action items to closure. g) Document any gaps between the standard functionality of the System and functionality required by the Purchase Agreement for further analysis and discussion and/or facilitate the change control process. Client requested changes for changes beyond the scope of the Purchase Agreement will be evaluated at this phase,but will have to be evaluated for the potential impact on the Project Schedule and for additional project charges to be paid by the Client. h) Schedule one or more Remote Web sessions as a follow up to System Orientation to guide the Client through the Code File data collection process. i) Produce a System Orientation Report with the key decisions and configuration points as a result of the System Orientation. j) Prepare and submit a TCR upon completion of relevant activities. 7.3.1.2 Client Responsibilities a) Provide adequate facilities to comfortably conduct the System Orientation Sessions to include a computer projector,whiteboards, and adequate seating. Two projectors are preferred. b) Ensure participation of key stakeholders and decision-makers in the System Orientation process. c) Provide subject matter experts that can explain the agency's current workflow and application processes. These persons should have the ability to make decisions regarding any changes in workflow that may arise,through the use of the new Inform RMS System. d) Provide subject matter experts with the ability to gather and provide the data elements used to build Code Files to TriTech. e) Provide subject matter experts that will be the RMS super users, as well as a person or persons that will be responsible for the ongoing maintenance of the RMS Code Files and configuration(RMS Administrator). The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 29 Software Systems. ©2016 TriTech Software Systems Project Execution f) Provide subject matter experts that will be responsible for translating the geopolitical/operational boundaries into data(ESRI shape files) suitable for use within the RMS. g) Provide subject matter experts that will be responsible for the maintenance of the agency's street centerline data. h) Provide subject matter experts that can provide information on technical Systems (Interfaces and Hardware/Network/Applications). i) Review and approve(or provide the necessary direction to be approved)applicable TCRs. 7.3.2 Inform RMS Base System Code File Entry After completion of the Inform RMS System Orientation and receiving requested pre-DOLF data from the Client,the assigned TriTech Business Analyst will work with the Client to start and supervise the initial Code File building process. The Business Analyst will configure the Inform RMS Central Configuration as defined in the System Orientation.The Client will be actively involved and responsible for the Code File configuration process throughout the project. TriTech will deliver the hiform RMS System with the base NCIC Codes. The Client is responsible for building and maintaining the System Codes,Personnel,Property Locations, and Violation Codes(including local ordinances). The TriTech Business Analyst will begin the System Build with a base of 50 personnel entered into the system. The Client is responsible for the remaining Personnel data being entered and maintained. Note: It is the responsibility of the client to complete the UCR mapping to the violation codes. Validation through the DOLF process allows for the initial Code File setup while limiting the risk of rework. This task is considered to have been completed when the Business Analyst has demonstrated the setup of RMS User Personnel, Property Locations, and Violation Codes. 7.3.2.1 TriTech Responsibilities a) Monitor and evaluate Code File submitted by the Client and provide guidance as needed. b) Conduct one or more web meetings to validate the completeness and applicability of Client submitted Code File information,prior to initiating the Code file entry. c) Facilitate updates to the System Module Setup(SMS)building sheet. d) Prepare and submit a TCR to confirm the delivery of the SMS worksheet by the Client. 7.3.2.2 Client Responsibilities a) Provide timely input and updates to the SMS sheet to support the Code File building timelines. b) Participate in the Code File validation conference call. c) Continue building the System Code Files (those not built by TriTech) after DOLF. d) Review and approve(or provide the necessary direction to be approved) applicable TCRs. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 30 Software Systems. 02016 TriTech Software Systems Project Execution 7.3.3 Inform RMS Administration and Review Training The Inform RMS Administration and Review Training is a hands-on course for Inform RMS System Administrators.During the course students will learn how to create users, assign roles,create FBR templates and assign workflows, create and maintain system code tables,and map UCR codes.During the training the Business Analyst will review the Inform RMS system defaults. Students also learn overall administration responsibilities for implementation, configuration, and maintenance of Inform RMS. Participants include key members of TriTech's implementation team and should not generally exceed ten (10)core members of the Client's implementation team. The Client's team should include RMS Central and Local Administrators. The Inform RMS Administration and Review Training will be up to four(4) days onsite. 7.3.3.1 TriTech Responsibilities a) Schedule the Inform RMS Administration and Review Training in accordance with the Client's availability and the Project Schedule. b) Prepare and distribute the meeting agenda and documents for Client review or completion to all required attendees two weeks prior to the training. c) Conduct the meetings based on the distributed agenda. d) Prepare and submit a TCR upon completion of the training. 7.3.3.2 Client Responsibilities a) Provide adequate facilities to comfortably conduct the training activities. b) Ensure participation of the appropriate personnel. c) Continue the code file building activities after completion of this training. d) Review and approve(or provide the necessary direction to be approved)the applicable TCR. 7.3.4 Geographical Information Services 7.3.4.1 Data Evaluation The TriTech GIS Analyst will work with the Client to create the address locator packages and configure the RMS GIS services. GIS data must be from a single integrated source when delivered to TriTech for conversion. 7.3.4.2 TriTech Responsibilities a) Evaluate Client-supplied GIS data to ensure it is formatted correctly for creation of the address locator packages. b) Create the address locator packages, and configure the RMS GIS services c) Prepare and submit a TCR upon completion of this work. 7.3.4.3 Client Responsibilities a) Provide data in the required format, and per Project Schedule. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 31 Software Systems. 02016 TriTech Software Systems Project Execution b) Based on the analysis provided by TriTech,make needed changes to mapping data to allow the resulting GIS data to meet TriTech's mapping data requirements. c) Review and approve(or provide the necessary direction to be approved)the appropriate TCR. 7.3.5 Inform RMS Demonstration of Licensed Functionality(DOLF) Once the initial Code File and configuration phase is complete and RMS is installed at the Client site, a Demonstration of Licensed Functionality(DOLF)is conducted.This working meeting includes a review of the preliminary Code Files and configuration and hands-on training on software utilities for completing the Code File build and on-going Code File management. The DOLF for Inform RMS is up to five(5) days and will be held at the Client's facilities on the Client's system hardware, after it has been configured by TriTech. Client will be responsible for supplying the requested data to TriTech no later than four(4)weeks prior to DOLF to allow sufficient configuration time. The data will be requested as a follow up to the System Orientation for Inform RMS. The configuration of some RMS modules may be delayed based on the Client's decision, and consultation with TriTech Business Analyst. Participants include key members of TriTech's implementation team and should not generally exceed ten (10)core members of the Client's implementation team. The Client's team should include RMS Central and Local Administrators. At the conclusion of the session, a DOLF report is produced which documents the core software configuration, Code Files, and activities to be completed by the Client. Any issues that require follow-up action, including any outstanding Go Live issues will be documented in the applicable Project journal. Any issue that is determined to be outside the scope of this Project, as defined herein,requiring a modification or enhancement to the TriTech Software will be addressed through the Change Control process. Guidance on configuring additional Code Files will be provided during the DOLF. Following the DOLF process, ownership of Code Files transfers to the Client. Post DOLF,the Client will enter the balance of the Code Files(not built by TriTech).The Client also becomes responsible for maintaining Code Files (personnel,Violation Codes,Property Locations, and the like)that must be continuously updated to keep the Code Files in GO-Live ready status. During this phase,the assigned TriTech Business Analyst will provide consultation services. Dote: (Inform RMS DOLF is an event applicable to Inform RMS (and Field Based Reporting if purchased)only.No other Systems or Subsystems will be demonstrated during this session. 7.3.5.1 TriTech Responsibilities a) Schedule the DOLF meeting in accordance with the Client's availability and the Project Schedule. b) Prepare and distribute the meeting agendas to all required attendees a week prior to each meeting. e) Conduct the meetings based on the distributed agenda. d) Provide initial hands on training on the applicable system and introduction to different modules and their configurations. Note: This training is not meant to be comprehensive for end user understanding of the Subsystem: The purpose is to give the participant an understanding of the configuration and administration-- of dministration of Inform RMS (and Field Based Reporting if purchased). The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 32 Software Systems. 02016 TriTech Software Systems Project Execution e) Introduce the Client to, and begin documentation within the Subsystem Journal. f) Document and assign owners and due dates for any action items and track all action items to closure. g) Develop and deliver the DOLF Trip report. h) Handoff the management the Code Files to the Client. i) Provide the Client team with a copy of the Inform RMS User and Administration Guides. j) Prepare and submit a TCR upon completion of the DOLF,and upon delivery of the DOLF Trip report to the Client. 7.3.5.2 Client Responsibilities a) Provide adequate facilities to comfortably conduct the DOLF sessions to include an overhead projector. Two projectors are preferred.DOLF also requires workstations for each participant. b) Ensure complete participation of Central and Local Inform RMS Administrators for the purposes of . reviewing the RMS configuration as-built. c) Provide participants that are versed with the ability to continue the configurations, or Code File build once ownership transfers. d) Assume ownership for the continued build and maintenance of the system under the guidance of the TriTech project team. e) Ensure participation of key stakeholders and decision-makers in the DOLF process. f) Observe the change control process for any requested software changes. g) Review and approve (or provide the necessary direction to be approved)the applicable TCRs. 7.3.6 Inform RMS Workshops After the Inform RMS DOLF has been completed,the TriTech project team will conduct one or more Inform RMS workshops either remotely or at the Client site.This session is intended to be an extension to the Inform RMS DOLF for more complex implementations and multi jurisdictional agencies as specified in the contract. Each Inform RMS workshop will be up to three(3)days onsite. If the Project includes multiple Workshops,they may or may not be scheduled to occur over consecutive weeks. The Project includes: Five(5)Inform RMS Workshops 7.3.6.1 Inform RMS Output Designer Workshop The TriTech project team will conduct the Inform RMS Output Designer Workshop at the Client site.This session is intended for creating custom form outputs using Microsoft SQL Server Reporting Services which can be accessed from the Inform RMS Web Data Entry Templates.Using the Inform RMS Web application utility, attendees will learn to generate a dataset based on the Inform RMS Module template,then utilize SSRS to customize the output based off a pre-defined default output report.Attendees will also learn how to configure the templates to use the custom form output within the Inform RMS Web Data Entry Designer tool.This is an advanced workshop and attendees must have prior experience using SSRS. TriTech will not provide training on SSRS. This workshop will be up to three(3)consecutive days onsite with a class size limitation of 5 students. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 33 Software Systems. 02016 TriTech Software Systems Project Execution 7.3.6.2 TriTech Responsibilities a) Schedule the Inform RMS Workshop in accordance with the Client's availability and the Project Schedule. b) Prepare and distribute the meeting agendas and documents for Client review or completion to all required attendees two weeks prior to each meeting. c) Conduct the meetings based on the distributed agenda. d) Prepare and submit a TCR upon completion of the workshop. 7.3.6.3 Client Responsibilities a) Provide adequate facilities to comfortably hold the training activities. b) Ensure participation of the appropriate personnel. c) Continue the code file building activities after completion of this training. d) Review and approve(or provide the necessary direction to be approved)the applicable TCR. 7.3.7 Inform RMS Functional Acceptance Testing(FAT) Inform RMS Functional Acceptance Testing follows a standard content, approach and format.An Inform RMS Business Analyst performs the acceptance testing with the Client,prior to the start of End User Training. This process will be based on the standard TriTech FAT documents. The FAT documents have a standard content and format. The standard TriTech FAT documents will be sent to the Client for review prior to conducting the tests. The FAT results are documented in a TCR for verification and approval by the Client. Upon completion of FAT,the Client and TriTech will review the list of FAT failures(if any), and perform an assessment of the errors and determine the timeline for remedying the issues (pre versus post Go Live). TriTech will repeat any specific failed FAT tests following the correction of any issues which has caused the test to fail. This process will not include a repeat of the entire tests. Note: TriTech may organize at its discretion,separate breakout FAT sessions for subsections of the FAT documents that are applicable only to one agency(for example,applicable only to a Sheriff's Department or single agency).Each test will be executed once,and all applicable users and agencies must attend the FAT session and observe the tests.. Note: Successful completion of the FAT as part of the Pre-Go Live testing process does not constitute Final System Acceptance if such a Post-Go Live Reliability Testing is defined in the Purchase Agreement. 7.3.7.1 TriTech Responsibilities a) Deliver TriTech's standard FAT documents to the Client no later than two weeks prior to conducting the FAT. b) Provide a TCR to the Client to approve the receipt of the FAT documents. c) Assist the Client in conducting the FAT in accordance with FAT documents. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 34 Software Systems. 02016 TriTech Software Systems Project Execution d) Identify and document any issues discovered during the FAT. e) Upon completion of FAT prepare and submit a TCR to the Client,including a list of any exceptions to FAT. 7.3.7.2 Client Responsibilities a) Work toward the timely completion of all predecessor tasks to include the base code table entry and configuration. b) Provide adequate facilities to execute the FAT. c) Participate in the FAT by providing operational subject matter experts. d) Assist TriTech in documenting FAT findings and results. e) Review and approve(or provide the necessary direction to be approved)the appropriate TCRs. 7.3.8 Inform RMS Data Conversion TriTech proposes a one-time import of City of Fort Worth,TX legacy RMS data from one data source (Tiburon) into Inform RMS. There may be situations where there are differences in the data used in the current system and the proposed TriTech system. Key issues to consider are the standardized data elements that are used by the respective systems and the data integrity rules used by the respective systems for minimum required data. These factors can impact a variety of data types. TriTech understands the critical nature of the Client's legacy RMS data and will work closely with subject matter experts at your agency. TriTech proposes a legacy RMS data conversion to Inform RMS from 1 data source. Entity Source RMS Conversion IQ Feed Master Person Indices(MPI) Master Persons associated to imported entities listed below Yes Tiburon Master Vehicle Indices(MVI) Master Vehicles associated to imported entities listed below Yes Tiburon Master Property Indices Master Property associated to imported entities listed Yes (MPI) Tiburon below Master Location Indices (MLI) Master Locations associated to imported entities listed Yes Tiburon below Arrest Arrest Yes Tiburon Incidents Incidents Yes Tiburon Warrants Warrants Yes Tiburon Evidence Evidences No ,Tiburon The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 35 Software Systems. 02016 TriTech Software Systems Project Execution Assumptions: • The Client will provide at least one initial extract of RMS data for TriTech testing purposes,plus one final extract. • During the data conversion process,TriTech will convert legacy data into the Inform RMS Client (Ul)• • Prior to go-live,the client will provide TriTech a final backup of legacy data.Any data entered or modified in the legacy system after this point will require manual data entry and modification in the Inform RMS system post data conversion. • Inform RMS will be unavailable during the Data Conversion. • Master Indices will not be converted directly as they will be built through the import of the other entities.TriTech standard Master Resolution rules will apply. • The Client will supply a"Data Dictionary"defining all of the data items in the data conversions. This must be in a machine-readable forinat that can be included as a part of the Operational Scenario Document that TriTech will generate. • The Client must perform any necessary"data scrubbing"of their source data and code tables prior to delivery to TriTech. TriTech will assume that all data delivered is legitimate to use in the Data Conversions. • The Client will manually enter a minimum of three(3)representative records into each module of the configured Inform RMS system during the Data Conversion Workshop.TriTech will provide an SME to assist during this process.The data selected for entry will be included and identified in the initial data extraction supplied to TriTech. • Only the fields identified in the Appendix are included as part of the data conversion. • In the event that the Client makes any modification to their original data in order to include it in an Inform RMS record,they must fully document the transformation process used.All transformations so supplied must be able to be implemented via scripts vs. "human-interpretive"processes. These include,but are not limited to names and addresses • The Client must provide a Subject Matter Expert(SME) and make them available for consulting throughout the project. • Once TriTech has installed the initial TriTech RMS database and data entry software at the Agency, the Client will take appropriate steps to acquaint themselves with the modules included in the Data Conversion. • TriTech will provide an Operational Scenario Document(OSD)prior to executing the data conversions. • No additional modifications to existing TriTech products or database fields are required. • The Client is responsible for setting up a dedicated configured copy of the Inform RMS preproduction environment for data conversion activities. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 36 Software Systems. 02016 TriTech Software Systems Project Execution • The Client will create a dedicated data conversion environment that will be used for the final data conversion into the production Inform RMS system. The Client will grant TriTech access to the data conversion environment no less than 4 weeks prior to the scheduled start of the final data conversion. 7.3.8.1.1 TriTech Responsibilities a) Perform an analysis of the legacy data,provided by the Client. b) Collaborate with the Client in defining the data mapping, as well the resolution of the duplicate names. c) Provide an Operational Scenario Document(OSD)prior to developing the scripts for the data conversions. d) Create the necessary scripts for the data transfer. e) Perforin the initial data conversion and import for review by the Client. f) Perforin the final data conversion and import into the Inform RMS. g) Prepare and submit the applicable TCRs. 7.3.8.1.2 Client Responsibilities a) Extract and scrub the legacy data, and deliver it to TriTech in SQL format within thirty(30)days from the date of Inform RMS System Orientation. b) Provide a data dictionary to define all elements of the legacy data. c) Assist TriTech with data mapping exercise. d) Review,provide feedback and approve the OSD document prior to performing the data conversion. e) Review and approve(or provide the necessary direction to be approved) (or provide feedback, detailing the required corrections)for the interim data conversion delivery within ten(10)days of receiving. f) Review and approve(or provide the necessary direction to be approved) (or provide feedback, detailing the required corrections)the final data conversion delivery within ten(10)days of the final conversion. g) Provide a secure and reliable network connection. h) Review and approve(or provide the necessary direction to be approved)the applicable TCRs. 7.3.9 Inform RMS Training Note: Training classes are conducted based on the quantities that are specified in the Purchase Agreement. The appearance of a course description in this Statement of Work does not mean a' course will be conducted—it must be listed in the Purchase Agreement. Inform RMS Training classes are conducted on consecutive weekdays (Tuesday-Friday) during business hours.Alternate training schedules (multiple classes per day, evening, and weekend classes)will be subject to additional charge. Training classes will only be delivered after the Inform RMS FAT has been completed and the results are documented. Descriptions of classes are provided below. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 37 Software Systems. 02016 TriTech Software Systems Project Execution 7.3.9.1 TriTech Responsibilities(for all Inform RMS Classes) a) Conduct a training orientation via conference call between the assigned TriTech Training personnel and the designated Client representative.The objective of this session is to define the Training Schedule, based on the configurations of the Subsystem. b) Schedule the Inform RMS Training class(es) in accordance with the Client's availability and the Project Schedule. c) Prepare and distribute the meeting agendas and documents for Client review or completion to all required attendees two weeks prior to each meeting. d) Develop and provide the Inform RMS Training Plan for all licensed product options to the Client. e) Conduct the training session(s) for the licensed product options on a mutually agreed to schedule. f) Prepare and submit a TCR upon completion of each class, or a group of consecutive classes. 7.3.9.2 Client Responsibilities(for all Inform RMS Classes) a) Participate in the training orientation by providing a decision maker that can articulate the specific business practices that have been used in guiding the build of the Client's System. b) Provide adequate facilities for the execution of the training to include adequate seating for each workstation and an overhead projector. c) Provide a Local RMS Administrator for each class that can answer agency specific questions as related to the build of the Client's system. d) Review and approve (or provide the necessary direction to be approved)the applicable TCRs. 7.3.9.3 Inform RMS End User Training—Records The Inform RMS End User Training for Records is a hands-on course that prepares the students to add, edit, and modify Incident,Arrest, Custody, Crash, Citation,Field Interviews,Pawn,Permits and Licensing, and other Event reports.This class also instructs users on how to search crime report records easily and efficiently. Students learn how to maintain State-reportable UCR/N1BRS reports. This class is recommended for all persomlel responsible for the day-to-day records data entry and maintenance of all departmental reports. This three-day course prepares a core set of end users to use Inform RMS. Training classes are conducted between Tuesday and Friday,with a maximum of ten(10) students per class. Prerequisites: 1)Basic understanding of computers and the Microsoft Windows Environment. 2)A comprehensive understanding of the internal structure of the Records Department and departmental policies and procedures. 3)An understanding of how the Records Department interacts with Dispatch and Patrol. 7.3.9.4 Inform RMS End User Training—Field Officers The Inform RMS End User Training for Field Officers session is a hands-on three-day course.This course trains students to use Inform RMS and includes instructions on how to create and submit Incident,Arrest, Field Interview, Citation, and Crash reports through the workflow process. For the train-the-trainer portion of the class,TriTech prepares selected Client personnel to train other end users on Inform RMS. The goal is to prepare these personnel to apply TriTech's training concepts to train field users on Inform RMS. Training classes are conducted between Tuesday and Friday,with a maximum of ten(10) students per class. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 38 Software Systems. ©2016 TriTech Software Systems Project Execution Prerequisites: 1)Basic understanding of computers and the Microsoft Windows Environment. 2)A comprehensive understanding of the departmental policies and reporting procedures. 3)An understanding of how Patrol interacts with the Records Department and Dispatch. 7.3.9.5 Inform RMS Property and Evidence Training The Inform RMS Property and Evidence training is a hands-on three-day course for personnel responsible for entering,updating, and maintaining evidence records,tracking tow/impounds, and providing written notification for property or impounds. Students learn how to search evidence records,manage evidence items, create item barcodes,and use barcoding for inventory evidence.Training should be conducted directly with the Evidence Technicians at the agency's Evidence room. Training classes are conducted between Tuesday and Friday,with a maximum of ten(10) students per class. Prerequisites: 1)Basic understanding of computers and the Microsoft Windows Environment. 2)A comprehensive understanding of the departmental policies and procedures associated to maintaining Evidence. 3)A thorough understanding of how each of the Agency's Evidence locations are laid out and used. 7.3.9.6 Inform RMS Investigations Training The Inform RMS Investigations training is a hands-on three-day course for Case Managers,Investigative Supervisors, and Investigators(Detectives). Students learn how to assign cases for investigation and track their progress, add case supplements/case materials, create incident supplements, arrests, and update cases as needed. Students will also learn how to add, edit, and search intelligence records,create an RMS case from intelligence data(if applicable), and use the Intelligence Master Index.Training should be conducted directly with detectives that can train other detectives at their agency;this helps ensure proper workflows are discussed and configured. Training classes are conducted between Tuesday and Friday,with a maximum of ten(10) students per class. Prerequisites: 1)Basic understanding of computers and the Microsoft Windows Environment. 2)A comprehensive understanding of the departmental policies and procedures associated to Case Management, Investigations,and the management of Intelligence data(if applicable). 7.3.9.7 Inform RMS Report Writing Class The Inform RMS Report Writing class is a hands-on three-day course that explains when an ad hoc report is needed,how to understand the Inform RMS database structure,and how to create ad hoc reports using the embedded report writer.TriTech recoinmends that the Inform RMS Report Writing training session occur after the agency has had an opportunity to enter a substantial amount of data into the system(usually one to three months after go live). This class is recommended for personnel that will utilize the provided reporting tools to extract data from the Inform RMS. Training classes will be conducted between Tuesday and Friday. The number of students attending the User Training course will be limited to no more than ten(10) students per class. Prerequisites: 1) Completion of Inform RMS Training. 2)Basic understanding of computers and the Microsoft Windows Environment. 3)Understanding of Department Reporting requirements. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 39 Software Systems. 02016 TriTech Software Systems Project Execution 7.4 Inform RMS Integration Testing Once the FAT is concluded for Inform RMS and the Inform FBR Subsystems, and Interfaces that are scheduled to Go Live with Inform RMS and in preparation for Go Live,TriTech and the Client will conduct a one-day Integration Testing. The Integration testing will be conducted based on a number of scenarios that test the records management process.These scenarios involve the Subsystems and Interfaces that are scheduled to Go Live with Infonn RMS and can be tested in the pre-production environment.A small group of the Client staff(1-2 Records staff and field users)should participate in this test with TriTech.TriTech will work with the Client on defining a set of test scenarios that test the system based on the Client's practices. It is recommended that the Client utilizes sample calls from their legacy System. These scenarios must be signed off prior to commencement of the integration testing.At the successful completion of Integration Testing without any issues that prevent the System to be taken Live the Client shall provide written approval that the System is ready for Go Live. 7.4.1 TriTech Responsibilities a) Schedule an Integration Testing with the Client. b) Assist the Client in preparing test scenarios that can be used during this test and closely simulates the normal Client's call flow. c) Prepare and submit a TCR to the Client documenting the tests that will be used for Integration Testing. d) Participate in the Integration Testing with the Client. e) Prepare and submit TCRs upon successful completion of the Integration Testing. 7.4.2 Client Responsibilities a) Provide test scenarios that closely simulate the Client's normal call flow. b) Participate in conducting the Integration Testing. c) Review and approve(or provide the necessary direction to be approved)the applicable TCRs. 7.5 Implementation of System Interfaces 7.5.1 Inform Standard Interfaces' Requirement Gathering and Configuration The functionality and applicable configuration options for each of the TriTech Standard Interfaces are described in the Interface Requirements Documents (IRD). A TriTech Systems Engineer will review the IRDs for each of the applicable Standard Interfaces with the Client's subject matter experts and prepare a configuration worksheet(ICD) detailing the parameters that will be set to meet the desired functionality for the Interface. This process may be performed for different interfaces at different times. This process will be performed remotely via phone conference. The Client is responsible for engaging the third party vendors whose systems are being interfaced with, so that an end to end flow of the data is discussed. TriTech Systems Engineer will configure and install the Standard interfaces on Client's system hardware. IRDS are not Client specific documents, and not subject to edits, changes, or approval. Client specific configurations for Standard Interfaces are documented in configuration worksheets(ICD)and must be approved prior to configuration of the interface. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 40 Software Systems. 02016 TriTech Software Systems Project Execution Installation and configuration of Standard Interfaces can only be performed by qualified members of TriTech System Engineering or Engineering teams,using proprietary tools.Any changes to the requirements of the Records Check Interface from the approved Configuration worksheet will be subject to additional cost and configuration time. Once each of the Standard Interfaces are installed and configured,they can be staged for FAT. TriTech is not responsible for coordination,management,or covering the cost of any software,work, customization,coding or testing that is required to be performed by the third party vendors engaged in the implementation of the standard or custom interfaces,unless the work is defined under a subcontract with TriTech within the scope of this Purchase Agreement. Note 1 Standard Interfaces are developed and enhanced within the TriTech product version process for TriTech software products(such as InforinRMS) Changes to standard Interfaces will require adherence to the development life cycle therein. Changes to standard Interfaces that are delivered within this life cycle will require the Client's system to be on a compatible version. Note 2 The Client's provision of Interface Requirements for Standard Interfaces is an early Project checkpoint.This information is needed to prepare the configuration sheets for Standard Interfaces. Incomplete,inaccurate or delayed information can have a cascading effect on the Project Schedule,and may result in a significant delay in completion of the project, since modification to Standard Interfaces are only released with a major version of Inform RMS, Note 3 Any changes to the configuration of Standard Interfaces made by the Client makes the Interface non-supportable, and all troubleshooting efforts resulted by such changes will be subject to additional cost. Note 4 The Client is responsible for any services or software needed from such Third Party Systems to allow for interaction with the Third Party System or for connecting to TriTech Interfaces Software in the absence of a Third Party API.TriTech is not responsible for any cost associated for the API, any required third party lab or certification testing,cost associated with required programming or custom work by the third party vendors, or,any license fees that may be required by the third party vendors. 7.5.2 Custom Interfaces' Requirement Gathering and Configuration A TriTech Systems Engineer will review requirements specified by the Purchase Agreement applicable to Custom Interfaces, and lead gathering detailed operational requirements within the scope of the Purchase Agreement. This process may be performed for different interfaces at different times.This process will be perforined remotely via phone conference. Once sufficient information has been gathered to describe the operational functionality of the Interface,the Systems Engineer will create Operational Scenario Documents(OSD)detailing the operation of the The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 41 Software Systems. 02016 TriTech Software Systems Project Execution Interface. Client's input in detailing all relevant information regarding the operations of these interfaces and interactions with the external systems are essential to timely and accurate development of the OSDs.The completed OSDs will be provided for Client's review. This document must be approved by both the Client and TriTech prior to development. The Client will be given a TCR that the document was provided,meets the requirements and has been reviewed with the Client. The Client must review the OSD within 10 days from delivery by TriTech, and provide comments and questions back to TriTech or provide approval if no changes or edits is necessary. The Client is responsible for obtaining the API for each of the third party vendors that TriTech applications are interfacing with.The API must be for the version of the third party software that TriTech will be interfacing with. The timelines for providing these documents to TriTech is concurrent with development of the OSD, so that any limitations associated with the level of integration with the third party application can be taken into consideration. Delays in review and approval of the OSDs can impact timely development of the interfaces, and ultimately delay the Go Live of the system. All requirement changes for Custom Interfaces after approval of the OSD shall follow the Change Management process, and may be subject to additional cost and development time. Upon approval of the OSD the custom interfaces are developed by TriTech engineering team. Once developed,these interfaces will be installed on Client equipment and go through testing with the Client and applicable third party vendors who own and administer the vendor side of the interface. The Client is also responsible for coordinating execution of a mutual Non-Disclosure Agreement(NDA) between the third party vendors and TriTech before any technical information or documentation can be exchanged or testing can commence. TriTech is not responsible for coordination,management, or covering the cost of any software, work, customization,coding or testing that is required to be performed by the third party vendors engaged in the implementation of the standard or custom interfaces,unless the work is defined under a subcontract with TriTech within the scope of this Purchase Agreement. Note 1 The Client's provision of Interface requirements for each of the Custom Interfaces is an early Project checkpoint.This information is needed to develop the OSDs for Custom Interfaces. Incomplete,inaccurate, or delayed information can have a cascading effect on the Project Schedule, and may result in a significant delay in completion of the project. Note 2 The Client is responsible for providing Application Programming Interface(API) documentation for the Third Party Systems. The API must document the integration process for the level of interface integration defined by TriTeeh's response to the RFP.The Client is responsible for any services or software needed from such Third Party Systems to allow for integration with the third party system. Note 3 The scope of functionality for the custom interfaces is limited to 1)the capability of the TriTech System being interfaced and 2)the Application Programming Interface(API) capabilities of the external system being interfaced. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 42 Software Systems. 02016 TriTech Software Systems Project Execution Note 4: High level descriptions of each of the custom interfaces in Appendix D-'Custom TriTech Interfaces,will become the basis for the scope,of detailed requirements,described in the OSD.Any changes in the requirements documented in the System OSDs,post approval of the OSDs are subject to formal Change Order. Note 5: The Client is responsible for coordinating the development of the vendor side of all interfaces to the third party applications for the interfaces that the vendor is not a TriTech Subcontractor,based on the Purchase Agreement. Note 6:TriTech is not responsible for any cost associated for the API,any required third party labor certification testing,cost associated with required programming or custom work by the third_ party vendors,or any license fees that may be required by the third party vendors, 7.5.3 Interface Functional Acceptance Testing(FAT) All Standard and Custom Interfaces are subject to Functional Acceptance Testing(FAT). FAT for Standard Interfaces is based on a standard set of TriTech FAT documents for each interface, as they are applicable to Client's configurations. FAT for Custom Interfaces are based on the functionality described in the approved OSD for the interface. This process will be based on an FAT document developed by the Systems Engineer. The test source will be the provided IRDS; therefore all Standard Interfaces will be tested against standard,predefined TriTech FAT documents.These tests have a standard format and will be sent to the Client for review prior to conducting the FAT. TriTech will repeat any failed FAT test following the correction of any issues which has caused the test to fail. 7.5.3.1 TriTech Responsibilities a) Provide the IRD to the Client for review for each of the Standard Interfaces. b) Prepare and submit a TCR to the Client,documenting the delivery of the IRDs to the Client for Standard Interfaces. e) Review the IRI)with the Client for each of the Standard Interfaces and gather and document the configuration options for the Interface. d) Install and Configure the Standard Interfaces based on the agreed upon configurations. e) Gather the operational requirements for each of the Custom Interfaces and develop and OSD. f) Provide the OSD to the Client for review and approval. (for custom interfaces only) g) Prepare and submit a TCR to the Client,documenting Client's approval of the OSD for each of the Custom Interfaces. h) Develop the Custom Interfaces based on the approved OSD. i) Install and configure the Custom Interfaces. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 43 Software Systems. ©2016 TriTech Software Systems Project Execution j) Prepare and submit TCRs upon installation of the Interfaces. k) Develop FAT documents reflecting feature descriptions found within the provided and applicable OSDs. 1) Provide the FAT documents to the Client for review prior to conducting the FAT for each interface. m) Provide a TCR to the Client to approve the receipt of the FAT documents. n) Assist the Client in conducting Acceptance Testing in accordance with FAT documents. o) Prepare and Submit a TCR,documenting completion of FAT including any exceptions to FAT. p) Resolve FAT issues and re-run tests as required. 7.5.3.2 Client Responsibilities a) Participate in the review of the IRDS and provide the configuration information to TriTech in a timely manner. b) Provide the information that are necessary for development of the OSD for each Custom Interface. c) Obtain the API for each of the third party applications that TriTech interfaces with and provide the document to TriTech. d) Review and approve(or provide the necessary direction to be approved)the OSDs based on the required timelines. e) Engage the third party vendors in the requirement gathering, development,testing and other interface development activities. f) Review and approve(or provide the necessary direction to be approved)the FAT documents. g) Participate in the FAT. h) Assist TriTech in documenting FAT findings and results. i) Review and approve(or provide the necessary direction to be approved)the applicable TCRs. 7.6 System and Subsystem Go Live The"cut over"of each of the Inform RMS Subsystems, and Interfaces into the production environment is a highly orchestrated activity that will require a number of resources from both the Client and TriTech teams. 7.6.1 Inform RMS Go Live Once end-user training has been completed and Inform RMS is ready to be placed into production,TriTech will assist the Client in placing the system into operation. In preparation for Go Live,TriTech will assist the Client in cleaning the training data from the Inform RMS System. TriTech will provide the Client with a standard Go Live authorization letter that must be approved by the Client no later than 3 weeks prior to Go Live. This letter will list all the Subsystems that are scheduled for the Go Live, and any exceptions to Go Live applications. It also memorializes the date and time of Go Live, as well as the Client's confirmation that the System and staff are ready for Go Live. At Go Live,the TriTech and Client implementation teams will support the users in the transition to the new System. Any issues are logged and resolved through TriTech Technical Services.A more detailed Go Live plan will be provided with adequate lead time. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 44 Software Systems. 02016 TriTech Software Systems Project Execution The duration of the Go Live support for Inform RMS and its subsystems for this project will be four days (to include pre and post cutover)by 2 people. Go Lives are conducted on consecutive weekdays (Monday- Friday). Go Lives that require TriTech support that begins before or extends beyond weekdays will be subject to additional charge. The breakdown of onsite Go Live Services is as follows: Inform RMS Go Live Coverage: 2 people for 4 days covering single a shift during normal business hours 7.6.1.1 TriTech Responsibilities a) Prepare and submit a Go Live authorization letter to the Client. a) Identify the participants for the Go Live in accordance with the terms of the Purchase Agreement. b) Have specified personnel onsite in advance of the Go Live date to begin the final inspection of the Client's system as part of the Go Live preparations. c) Be on-site to assist the Client in placing the system into production status. d) Assist Client staff in using the system and assist the computer operations staff in supporting the system. e) Provide System monitoring following the actual System cut over as specified within the Purchase Agreement. f) Prepare and submit a TCR upon first Live operation of Inform RMS. 7.6.1.2 Client Responsibilities a) Complete Inform RMS roll out to support the Go Live date. b) Review and approve(or provide the necessary direction to be approved)the Go Live authorization letter no later than 3 weeks prior to each scheduled Go Live. e) Complete all relevant end user training to support the Go Live of the Subsystems. d) Place the software into production and begin operational use in consultation with TriTech and in accordance with the project schedule. e) Provide adequate persons for the supervision and assisting the end users beyond the participation of the TriTech staff. f) Provide dedicated workstations for TriTech support staff during Go Live support period. g) Provide Client IT support to cover all Client end user and TriTech staff hours of operation. h) Develop a process for the reporting and resolution of issues. i) Review and approve (or provide the necessary direction to be approved)the applicable TCR. 7.7 Reliability Acceptance Period Upon Go Live for the Subsystem(s),the Client shall use the Subsystem for a thirty(30)consecutive day period to verify operational functionality in a live environment. If no Critical Priority or Urgent Priority Software Errors (as those terms are defined in Addendum E to the Agreement)are reported during such thirty(30) day period,the Subsystems shall be deemed to have achieved Final Acceptance. In the event that a Critical Priority or Urgent Priority Software Error occurs during the Acceptance Test Period,TriTech shall commence actions in accordance with the Software Support Agreement to correct the reported error. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 45 Software Systems. 02016 TriTech Software Systems Project Execution In the event that a Critical Priority Software Error occurs between day one(1)and day thirty(30)of the Acceptance Test Period,the Acceptance Test Period will be stopped and restarted at day one(1)once the Software Error has been resolved in accordance with the Software Support Agreement. In the event that an Urgent Priority Software Error occurs between day one(1)and day fifteen(15),the Acceptance Test Period will be stopped and restarted from day one(1)once the Software Error has been resolved in accordance with the Software Support Agreement. If the Software Error occurs between day fifteen(15)and day thirty(30),the Acceptance Test Period will be stopped and restarted from the day the resolution has been provided in accordance with the Software Support Agreement. Critical or Urgent Priority software errors caused by factors that are outside of TriTech's control,and/or from variables which are outside the scope of TriTech's responsibilities,will not be counted Critical or Urgent Priority software errors. Examples of such issues could be,but are not limited to: • Power failures • Operator error • External network failure • Availability of components that are not provided by TriTech but interface to/from the TriTech solution • Hardware or Operating System software • Non TriTech supplied software components introduced to the working environment During the Acceptance Test Period,the Subsystem will be frozen, (i.e.,no changes, fixes,and/or updates will be applied,except those that are required to address Downtime Failures associated with the Acceptance Test Period.) At the conclusion of the Acceptance Test Period,as further defined in the Agreement,the Subsystem will be deemed accepted by the Client. 7.7.1.1 TriTech Responsibilities a) Document the start of the Reliability Acceptance Period upon Go Live of the Subsystem in a TCR. b) Address any Reliability Acceptance Period issues that are reported during this test period. c) Document other issues that are not considered"Reliability Acceptance" issues to be addressed as part of the support and maintenance of the Subsystem. d) Provide the appropriate TCR to document the Final Acceptance of the System. 7.7.1.2 Client Responsibilities a) Report issues if and when they develop. b) Review and approve(or provide the necessary direction to be approved)the applicable TCRs. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 46 Software Systems. 02016 TriTech Software Systems Project Closure 8 PROJECT CLOSURE When all pre and post go live project deliverables have been completed,Project Closure activities will take place. Support of the System and Subsystems are transitioned to TriTech's Technical Services Group.Any remaining Project related administrative tasks are completed by TriTech and Client. Project documentation is archived and primary Client interaction is officially handed over from the TriTech Project Manager to the TriTech Account Executive. 8.1 System Transition Following Go Live,there is a transition period where the Client moves from the implementation team to the support team. This transition will change the Client's primary point of contact from the Project Manager back to the Account Executive. Software support will be handled through the Technical Services Group.The Client's issues will be entered,tracked, and managed via a computerized and web-enabled issues tracking system. This tracking system will become available to the Client at system installation. 8.1.1.1 TriTech Responsibilities a) Provide payment reconciliation, final TCRs and final invoices. b) Transition the TriTech point of contact from the Project Manager to the Account Executive and Technical Support Department. c) Provide continued support based on terms of Purchase Agreement. 8.1.1.2 Client Responsibilities a) Provide approval of Project TCRs within five(5)business days. b) Provide payment reconciliation and payment of final invoices. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 47 Software Systems. ©2016 TriTech Software Systems 9 APPENDIX B - CONTRACTED MODIFICATIONS TO STANDARD TRITECH SOFTWARE PRODUCTS Note:Any changes in the requirements documented in the System OSDs,post approval of the OSDs are subject to formal Change Order. List of Product Modification OSDs: There are no product modifications proposed for this project. The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 48 Software Systems. 02016 TriTech Software Systems Appendix C - Standard TriTech Interfaces 10APPENDIX C - STANDARD T (TECH INTERFACES Note: The scope of functionality for these Standard interfaces is limited to 1)the capability of the TriTech System being interfaced and 2)the capabilities of the externa, system being interfaced. Note: High level descriptions of each of the custom interfaces below will become the basis for the scope of detailed requirements,described in the OSD.Any changes in the requirements documented in the System OSDs,post approvalof the OSDs are subject to formal Change Order.' Note: The Client is responsible for coordinating the development of the vendor side of all interfaces to the third party applications for the interfaces that the vendor is not TriTech Subcontractor, , based on the Purchase Agreement. List of Project's Standard Interface: Production Environment: a) None Test Environment: a) None The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 49 Software Systems. ©2016 TriTech Software Systems Appendix D - Custom TriTech Interfaces 11 APPENDIX D - CUSTOM TRITECH INTERFACES Note: The Client is responsible for providing Application Programming Interface documentation to these Third Party Systems that document the integration process for the level of interface integration defined by TriTeeh's response to the RFP.,,,The Client'is,responsible� . for any services or software needed from:such Third Party Systems to allow for interaction with the Third Party',System API or for connecting to TriTechInterfaces Software in the absence of a Third Party API, Note: The scope of functionality for these custom interfaces is limited to 1)the capability'of the TriTech System being interfaced and 2)the Application Programming Interface(APl , capabilities of the external system being interfaced. Note: High level descriptions of each of the custom interfaces below will become the basis for the scope of detailed requirements, described in the OSD.Any changes in the requirements ; documented in the System OSDs,post approval of the OSDs are subject to formal Change Order.i Note: The Client is responsible for coordinating the development of the vendor side of all interfaces to the third party applications for the interfaces that the Vendor is not a TriTech Subcontractor, based on the Purchase Agreement. Production Environment: a) One(1)LiveScan Interface—One Way—Inform RMS to Livescan for Fingerprints (CWI-3737) b) One(1)TIPS Mugshot Interface Configuration—One Way—Inform RMS to TIPS (CWI-3991) C) One (1)CopLogic Interface to Inform RMS (CWI-3221) Test Environment: a) None The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 50 Software Systems. ©2016 TriTech Software Systems 12 APPENDIX E - CONTRACTOR(S) STATEMENT(S) OF WORK The contents of this material are confidential and proprietary to TriTech Software Systems and may not be reproduced,published or disclosed to others without the prior written consent of TriTech 51 Software Systems. ©2016 TriTech Software Systems Exhibit B Cost Detail and Payment Milestones CONFIDENTIAL TriTech Software License Fee(s) w Inform FBR User $1,100.00 250 $275,000.00 Inform RMS Accident $13,068.00 1 $13,068.00 Inform RMS Barcode Handheld Reader Software $1,725.00 1 $1,725.00 Inform RMS Evidence and Barcoding $13,070.00 1 $13,070.00 Inform RMS GIS(With CAD) $0.00 1 $0.00 Inform RMS Server Software(D-251-550 Users) $100,000.00 1 $100,000.00 Inform RMS Test or Training System $0.00 1 $0.00 Inform RMS User $1,590.00 225 $357,750.00 Inform RMS Software License Fee(s)Subtotal. $760,613.00 TriTech Upgrade Credit. ($-472,723.00) TriTech Software License Fee(s) Total; $287,890.00 TriTech Implementation Service Fee(s) Business Analysis for Inform FBR(140 Hours) $21,000.00 1 $21,000.00 Inform RMS 3-Day Workshop and Consultation $4,200.00 5 $21,000.00 Inform RMS Administration Review and Training-(D-251-550 concurrent users) $7,000.00 1 $7,000.00 Inform RMS DOLF(D-251-550 Users) $20,300.00 1 $20,300.00 Inform RMS Output Designer Workshop 3 Day $4,200.00 1 $4,200.00 Inform RMS Position Installation(up to 5 workstations) $3,150.00 1 $3,150.00 Inform RMS Routing/GIS Server Implementation $6,300.00 1 $6,300.00 Inform RMS Server Installation and Configuration $7,700.00 1 $7,700.00 Inform RMS Standard Functional Acceptance and Integration Testing-(D-251-500 users) $10,500.00 1 $10,500.00 Inform RMS System Orientation and Analysis-(D-251-550 users) $21,000.00 1 $21,000.00 Inform RMS User Training-Field Officers(3 Days) $4,200.00 5 $21,000.00 Inform RMS User Training-Investigations(3 Days) $4,200.00 5 $21,000.00 Inform RMS User Training-Property and Evidence Training(3 Days) $4,200.00 1 $4,200.00 Inform RMS User Training-Records(3 days) $4,200.00 1 $4,200.00 Onsite Go Live Support Services for Inform RMS(2 persons,4 days,single shift) $25,200.00 1 $25,200.00 Amendment 1 to System Purchase Agreement Page 5 of 9 Remote Implementation Services for Inform RMS GIS $2,500.00 1 1 $2,500.00 Inform RMS Implementation Service Fee(s)Subtotal: $200,250.00 TriTech Implementation Service Fee(s) Total. $200,250.00 Custom Solution(s) CopLogic Interface to Inform RMS $19,250.00 1 $19,250.00 LiveScan Interface-One Way-Inform RMS to Livescan for Fingerprints $15,400.00 1 $15,400.00 TIPS Mugshot Interface Configuration-One Way-Inform RMS to TIPS $7,000.00 1 $7,000.00 Custom Solution(s) Total. $41,650.00 Project Related Fee(s) Project Management $162,625.00 1 $162,625.00 Estimated Travel Expenses(To be billed as incurred) $60,025.00 1 $60,025.00 Report Writing Training(3 days) $4,200.00 1 $4,200.00 System Integration Fee $20,800.00 1 $20,800.00 Tiburon TC RMS to Inform RMS Data Conversion $49,000.00 1 $49,000.00 Project Related Feels) Total: $296,650.00 Hardware Barcode Industrial Portable Data Terminal $1,215.00 4 $4,860.00 Barcode PolyPro Labels 4"x 2",1110 labels per roll(4 rolls per case) $195.04 1 $195.04 Barcode Printer Resin Ribbon(12) $169.20 1 $169.20 Barcode TB Zebra,GK420T,Printers,4"Print Width $795.00 3 $2,385.00 Hardware Total: $7,609.24 Annual Maintenance Fee(s) (Year 1) CopLogic Interface to Inform RMS 8 x 5 $3,465.00 Inform FBR User 8 x 5 $49,500.00 Inform RMS Accident 8 x 5 $2,352.24 Inform RMS Barcode Handheld Reader Software 8 x 5 $310.50 Inform RMS Evidence and Barcoding 8 x 5 $2,352.60 Amendment 1 to System Purchase Agreement Page 6 of 9