Laserfiche WebLink
A more detailed description of the evaluation process, comparative costs, and team recommendations <br />can be found in the Permit Tra cking Software Project Plan presented to the BOCC on Ap ril 23, 2015 . <br />Initial recommendation <br />After completing an evaluation comparing purchasing with developing in-house, and considering the <br />related costs and resource requirements, the team recommended the BOCC reject all RFPs and direct <br />staff to build the application in-house. <br />Commissioner's direction <br />On April 23, 2015, the BOCC considered the team's recommendation and approved the following: <br />1. The RFPs would remain open; <br />2. IT may proceed developing permit tracking software; but first <br />3. The team must provide an acceptable response to the following questions: <br />Changes <br />1) Who is accountable for settling disputes that might arise over design, content, and <br />functionality ofthe application? <br />2) Provide a plan B in case the development of the application cannot be completed or <br />cannot meet the needs of the users. <br />3) Come up with 3 alternative names to Sasquatch. <br />4) There is a statement that hiring the web developer will save 60 calendar days of <br />development, is that accurate and if so does hiring the web developer provide <br />additional benefit to justify the $138,OOO? <br />5) Are there alternatives to hiring a web developer, and if so, what are they and what is <br />the cost? <br />6) Who in the departments will be assigned to work with IT in designing the application <br />and how will we ensure it is part of their job duties? <br />IT staffing and priorities <br />After April 2015, staff began to work on answers to the BOCC's questions posed. In the meantime, the IT <br />department's web developer resigned requiring other staff to shift priorities, and a higher priority was <br />given to the county's Laserfiche implementation. These factors all lead to a delay in follow-up on the <br />questions posed in April. When the group started to reconvene in October 2015, there were concerns <br />raised about the fact that we were far behind the initial timeline proposed and that IT staffing issues had <br />not yet been resolved. Additionally, CDS was under more and more of a time crunch for getting a fully <br />functioning system in place. <br />Exploring a new plan <br />Because of these concerns, staff no longer had a unified Plan A. It was proposed that we start pursuing <br />more aggressively our Plan B option which was to reexamine the off-the-shelf permit software products . <br />Paladin's SMARTGov software was of particular interest for several reasons . CDS staff had spoken to <br />Page 2 of 10