Laserfiche WebLink
21Tech Response: <br />San Leandro’s Information Technology RFQ for Accela Development Services Page 24 of 28 <br />#TASK NAME REQUIREMENT TYPE RESPONSE <br />(HRS) <br />LOW <br />(HRS) <br />HIGH <br />3.Existing Report Modification Work with staff to identify the working <br />reports that need to be modified and <br />changed to meet the needs of the <br />specific departments <br />Fix Reports Work effort to modify existing reports <br />includes business analysis, mock-up, <br />development of Crystal report, load and <br />configuration within Accela's Report <br />Manager, unit testing, and user <br />acceptance testing. Our numbers were <br />based on the average time to repair, <br />modify and redeploy a report (8 hours). <br />30 50 <br />4. Credit Card Convince Fee Provide a method to add a 3% fee to <br />the total fee if a customer wants to pay <br />by credit card. This will need to be <br />implemented in all departments that <br />take payment across all record types <br />and fee schedules. <br />Custom <br />Development <br />This task will involve a cross <br />departmental effort that will affect fee <br />schedules across the entire organization. <br />We will need a SME from each <br />department that is able to assist with <br />specific requirements for the affected <br />departments. <br />97 127 <br />5.GIS Integration Provide Assistance to San Leandro IT <br />Department in the implementation of <br />APO GIS Integration into their current <br />environment. <br />Implementation This task will require San Leandro IT GIS <br />Personnel to be involved and assist with <br />task that require specific knowledge of <br />the San Leandro GIS system. <br />60 100 <br />6. Additional Record Types Work with staff to design and <br />implement the new record types as <br />needed in the individual departments <br />to further streamline their business <br />processes. <br />Configuration Additional record types will need to be <br />tested extensively by the Specific <br />departments to insure it is working as <br />expected prior to production deployment <br />20 40 <br />264