2.1 System Configuration 2.1.1 The County’s Project Team shall designate appropriate County personnel to gather and provide information to Contractor as necessary for Contractor to configure the system. 2.1.2 Unless agreed upon otherwise in writing, configuration of the Contractor’s ERP System is to be completed by Contractor, with guidance provided by designated County personnel as necessary. Configuration shall include, but not be limited to: 2.1.2.1 Creating/migrating all general ledger accounts; 2.1.2.2 Creating/migrating all positions and personnel records; 2.1.2.3 Creating/migrating all fixed asset records; 2.1.2.4 Migrating and/or populating all existing financial, position, personnel and fixed asset data from the current ERP System with any necessary or agreed upon format conversions; 2.1.2.5 Setting-up initial users, user groups and user group permissions; and 2.1.2.6 Adding and configuring all configurable settings including, but not limited to forms, defaults, pick lists, etc. 2.1.3 Contractor shall configure entire system to a Go-Live ready state. 2.2 Report and Form Customization 2.2.1 Prior to Go-Live, Contractor shall ensure that all the materials presented in Attachment C – County Reports and Documents can be generated by the system to a reasonable facsimile in terms of content and layout which shall be determined at the sole discretion of the County. 2.2.2 If any customizations are required to any default reports available within the ERP System in order to generate the materials presented in Attachment C – County Reports and Documents, Contractor shall perform all necessary customizations at no additional cost. 2.2.3 If any customizations to Contractor’s report generating engine are performed by Contractor to generate the materials presented in Attachment C – County Reports and Documents, Contractor shall ensure that the ability to generate these reports and documents with any customizations is carried over to, and incorporated in, any future updates and upgrades to the system by Contractor at no additional cost to the County. 2.3 Training 2.3.1 Prior to training, Contractor shall set-up a fully functional test environment populated with data migrated/converted from the County’s existing ERP System. This will ensure end-users train with real data they are familiar with and will help them identify any potential conversion issues for Contractor to resolve. 2.3.2 Contractor shall provide training on all aspects of the system to County end users in accordance with the training plan laid out in Contractor’s proposal unless otherwise agreed to in writing. 2.3.3 Contractor’s ERP Solution shall have on-line help reference documents providing users with guidance in performing common functions and tasks.
