08-25-14 Council Packet - Laserfiche WebLink

Home Search

Springbrook send tures, Finance General Ledger, Accounts Payable, Bank Reconciliation, Accounts Receivable, ACH, Misc. Cash Receipts, Project Management, Workflow (automated approvals) Payroll Direct Deposit, Employee Time Entry, Payroll, Workflow (Electronic Approvals) Utility Billing Meter Interface Community Development Special Assessments The modules and features listed in this section are considered essential and required for Phase One of the Implementation. This list is limited to key modules and features and is not considered a complete list of all of the features that will be addressed during Phase One of the Implementation. Modules and features purchased with professional services but not listed in this section will be implemented in later Phases of the Implementation project based on Springbrook's Standard project scheduling and forecasting practices. Definitions Masters: static information and data, based on a single individual or entity. An example of a Master file is Customer, Employee or Vendor contact information. History: Information that is updated or added on a regular basis that is tied to a Master File. An example of History includes Checks, Billings or Receipts. Client Requirements Client must perform all data extraction from their legacy system and populate Springbrook Software, Inc.'s then current Standard Templates. Standard Templates and field listings are available for review by client upon request. Client must validate the accuracy of data. Data in legacy system which is incorrect or does not balance will need to be altered by Client, or incorrect results will be carried through to new system. Client must provide data according to the schedule mutually agreed upon with Project Manager, or project may incur changes to schedule or additional fees. Client must provide field descriptions and/or definitions for data that is being extracted from the legacy system. Vendor Requirements Vendor will provide the software base application. The base for the Springbrook application includes System Setup, General Ledger Shell, Cash Receipts Shell, and Clearing House. The Springbrook base is included in all purchases. Vendor will evaluate data provided from client to ensure that all required fields have been populated, that the formats provided meet the necessary criteria, and the limitations of field ranges. Vendor will provide consulting services to assist client in analyzing whether data inputs meet criteria specified, and assist in testing to validate inputs are converted correctly to the SSI System. Vendor will provide a secure method for electronic data transmission. Vendor will ensure that all data provided in finalized templates are converted correctly into the corresponding fields or tables within the Springbrook Software, Inc. applications. Once Client has offered final approval of data sets, Vendor will provide three (3) data conversions into the Live UB System and one (1) data conversion into the Live system for all other Applicable as specified on table above. Acceptance Period Upon completion of the implementation of each Licensed Software Product purchased by the Client as set forth in the appropriate Order Form or Statement of Work, Client will have 3o calendar days to validate that the Products are performing in accordance with this Addendum, the Master Agreement, and any related Addenda. Each Application will be considered accepted by the Client if and when any one of the following has occurred; (a) Client provides vendor written affirmation that the Application is performing within the terms of this Addendum, the Master Agreement and any related Addenda; (a) 3o days has passed since the implementation ("Go -Live") of the Application without written notice of non-acceptance; (b) Client is using the Licensed Software Product at issue for its intended purpose; or (c) One calendar year has passed since the Effective Date. Client agrees to grant Vendor access to any system where Licensed Software Products are installed to audit Client's use of the Licensed Software Products and compliance with this Addendum. Core Modules Statement of Work The Core Modules Statement of Work shall mean the statement of work that outlines the work necessary to implement the core functionality of the client requested modules. Acceptance of Core Modules of Statement of work shall be deemed complete for billing purposes unless Client has provided written notice of non-acceptance within 15 days of receipt of the Core Modules Statement of Work. 6