Laserfiche WebLink
E. Implementation Assumptions <br />1.During and after implementation of IPA, the Client may identify software defects, or additional <br />desired functional requirements. Client shall be responsible for working within Innovative’s normal <br />established support and enhancement request processes to report issues or provide input on <br />additional desired functional requirements. <br />2.Client must provide the IPA configuration and profiling information. Client will use settings which <br />are closest to what they currently have in place with their existing notification system.The <br />Innovative IPA outbound configuration and profiling information can be summarized as: <br />i. Which voice should be used for each IPA message: male or female voice? <br />ii. What caller ID number should be used for phone calls? This must be an actual phone <br />number that the Client has, but it does not need to be connected to a phone line. It is <br />recommended that Client selects one of the available phone numbers that will be offered <br />for their area code rather than porting over any existing notification process phone <br />number because of the time it will take to port the number and the downtime this will <br />cause for phone notices. The Client cannot use the phone number while porting is in <br />progress. <br />iii. What caller ID name should be used for phone calls? This name will display along with <br />the phone number when calling the patron (e.g., Innovative PL - 555-555-5555).Note: <br />there is a 15 character limit including spaces for the Caller ID name. <br />iv. Complete text for each IPA message that will be used. Up to 100 individual branch <br />Hold Pickup messages may be configured within the scope of this SOW. Any branches <br />added after completion of Services will be subject to a new SOW. Changes to messages <br />after configuration may incur additional charges. For example, "Hello, this is your local <br />library calling. Our records indicate that you have the item, %%title%% being held for you. <br />This item can be picked up at the %%branch%% location, until %%date%%. Thank you, <br />goodbye." <br />v. Client must allow outbound FTP (for transmission of the notice files) and inbound PAPI <br />connections (for posting notices to the database). <br />vi. Any additional information necessary to complete installation and implementation. <br />F. Fees and Payment Terms <br />Fees for Services delivered under this SOW will be charged on a fixed price basis as set forth in <br />the attached Order Form herewith and are made in good faith based on the activities,approach, <br />and assumptions contained within the SOW. Payment terms for this SOW are as set forth in the <br />Agreement. Any additional Change Requests will be performed at a blended rate of $200 per hour <br />for all resources. Additionally, Client is responsible for all reasonable out-of-pocket costs and <br />expenses incurred during this SOW. Pricing assumes that deliverables in this Statement of Work <br />are completed within six months or additional Services fees will apply.