Laserfiche WebLink
l) <br /> <br />2) <br /> <br />3) <br /> <br />4) <br /> <br />rvlASYS has been a provider for the Elk River Police Department for a long period <br />of time. Our experiences with this company have been less than satisfactory. <br />They use subcontracted employees to provide maintenance service, some of who <br />travel from out of state and are not available for emergency repairs. :in recent <br />years, calls for service have resulted in very poor service and lengthy response <br />times. HASYS also formally had a user base of over 30 departments in <br />Minnesota. That number is shrinking as more and more departments leave for <br />other vendors. :It would appear that by the year 2,000 there will be less than 12 <br />departments on line in Minnesota using any MASYS products. This creates grave <br />concerns for what type of support and product development will be available <br />over the next 5-10 years. <br /> <br />MASYS has offered a shared records system but has been very unclear as to <br />what we will receive once the system is finally installed. Promises of dispatch and <br />records integration on the county end have failed to materialize. They county <br />records staff has in fact reported that the new system has failed to perform as <br />expected and in most cases is causing a slowdown in daily work. <br /> <br />The hardware specifications were very vague. When these were put out for bids, <br />the companies had a very difficult time specifying what we would have installed. <br />:It took months to finally receive a suitable bid as the company had to build the <br />specifications themselves by researching the software and configuration <br />proposed by HASYS. <br /> <br />Once a final bid had been received and it appeared the cost would be around <br />$:[7,000, we gave the go ahead to start network installation. The vendor decided <br />to double check with Sherburne County on one last hardware issue. :In doing so, <br />they discovered that MASYS had failed to inform Sherburne of our local area <br />network configuration. Sherburne did not consent to our network hooking up as <br />planned due to security concerns on their end. They agreed to the shared <br />records portion of the agreement, but had no prior information as to how we <br />were going to tie in. <br /> <br />s) <br /> <br />6) <br /> <br />Several meetings were held, and a new configuration was designed which would <br />allow Elk River to tie in with Sherburne's system. The cost increased to $23,000 <br />due to additional hardware which we would have to purchase. <br /> <br />During these meetings, it became apparent that Sherburne was not totally <br />pleased with the performance of the system, and that there were still many <br />unanswered questions about how this was all going to work. Our department <br />faith in rvlASYS during all this began to diminish. <br /> <br /> <br />