Res 2009-171 - Laserfiche WebLink

Home Browse Search

brazas ATTACHMENT "B" - TABLE OF FUNCTIONAL REQUIREMENTS RFP 209-028 Hand Held Ticket Writer System General Item # Function Requirement Response Criticality 1 . General The System will be able to The Brazos Solution can capture as many signatures as Must Have capture electronic desired by the City (both violator and officer signatures) and handwritten signatures. can print the signatures on the copy given to the violator. All of this is configured and controlled by the City via BuildlT. 2. General The System will allow all All data captured during a traffic stop are stored in non- Must Have captured input data volatile memory on the handheld unit. Once the citation is elements to be stored and uploaded, all data elements reside on the eCitation server. retrieved. They are then available for reporting in a number of different formats. One format is the Citation Detail report which looks exactly like what was presented to the violator. This report can also show all pictures, video, audio notes and officers notes upon demand. 3. General The System will allow user The City can set any data fields to be required via the BuildIT Must Have to designate required input web-based management platform. fields. 4. General The System will allow for The City has the capability to change any and all field Must Have Graphical User Interface characteristics, screen layouts, and citation printouts via (GUI) and field BuildlT (web-based screen designer). customization. S. General The System will provide an The Brazos Solution contains standard audit reports, which Must Have audit trail for all activity. the City can change or add to at any time. Anytime a user logs into the system, the date and time are recorded. In addition, the login information and date/time are recorded for every transaction that the user executes on the system. 6. General The System will provide The Brazos Solution requires users to log in at two levels - Must Have multiple levels of role- into the device and into the website. User roles for both based security. levels are defined by the County via Build IT. Roles are assigned to users, tasks, and fields which controls what any user can see or do on both the handhelds and the eCitation server. 7. General The System should be able Rules regarding autofill of information on a field-by-field basis Expected to auto fill data fields (i.e. is defined and controlled by the City via BuildIT. All data are city, state, and county by stored in lookup tables that the system will reference to zip code). autofill subsequent fields. The City has complete control over these lookup table fields via the eCitation server and can also define any default field values. For example when you select the make of a vehicle, the related models are presented to the user. Another example is when the user selects a city, only the zip codes valid for that city are presented to the user. 8. General The System should allow The City can define a complete Quality Assurance (QA) Expected for the creation and support server that can both push and receive information from the of a training/testing system devices. Devices are then marked as QA which allows the environment that mirrors user to define which server should be used to push and/or t he production system but pull the data. This QA server can be completely autonomous does not impact it. to the production server. 9. General The System should provide The Brazos Solution allows context-sensitive help by clicking Desired context sensitive help. on the label of a field. The help text that is displayed is completely configurable by the City via BuildlT.