Res 2009-171 - Laserfiche WebLink

Home Browse Search

v?:, brazos RFP 209-028 Hand Held Ticket Writer System User Interface Errors Item # Category Requirement Required Response Priority Description 88 Interface The System should Data validation rules are enforced when the officer tries to Expected Errors produce error messages print or save a record. The error is presented to the officer (i.e. user enters text in a and then the officer is taken to the offending field for numeric field). completion. 89 Interface Error messages should be The City can define and/or modify any error message Expected Errors able to be created and presented to the user. modified by the City Administrator. B usiness Continuity Item # Category Requirement Required Response Priority Description 90 Business The Proponent should The size requirements of the server will depend upon the Expected Continuity provide archival capacity number of devices (which is not stated in the RFP) as well as estimates (in terms of GB the projected number of tickets stored, whether the City of storage) for the system wants video, and the additional applications desired by the proposed. City. Our initial recommendation would be to have no fewer than three 72GB hard drives in a RAID 5 configuration which would amount to 144GB of storage space for both the database and web servers. This will allow up to 2 more 72GB hard drives in the future for further expansion. Of course, if the City elects to utilize a SAN, these requirements can be reduced. 91 Business The System should include The Brazos system allows users (with proper access) to Expected Continuity a method to delete a record delete records, but those records are only marked for and all associated child deletion and can be recovered by an administrator. We records. currently do not actually delete any records, we just don't report on the ones marked for deletion. Hard deletes (where they are removed completely from the system) are only performed by Administrators and include all child records. 92 Business The System should include The current method for purging data is at the Administrator Expected Continuity a method of purging level by running scripts directly on the database. We have archived data from the elected to not have any full deletes or purges via the production database(s). eCitation server interface in order to prevent any accidental data removal. 93 Business The Proponent should The current implementation of the eCitation server does not Expected Continuity explain the process for ever automatically remove historical data. We strongly archived historical data. believe one of the significant benefits of our system over time Include information on is the historical information collected. Therefore all data, archiving, retrieval, and detail reports, pictures, video, and audio are retained until purging attached manually purged by an Administrator. documents. 94 Business The System should be able The time it takes for us to restore a database (about 25GB Expected Continuity to be restored quickly after for 1 million records) is about 10 minutes. A full restore on the operating system is the web server (which includes pictures, audio, etc.) can take installed. Assume 100mbs about 1.5 hours for a full restore. We would expect the City's backbone, 100 GB restore to happen much faster. database, 100 GB image store.