Res 2009-171 - Laserfiche WebLink

Home Browse Search

brazes RFP 209-028 Hand Held Ticket Writer System 35. User The System will provide The Brazos Solution allows for as many different free text Must Have Interface free text fields for fields as requested by the City, with each field having up to narratives/comments. 750 characters. These notes fields can be dropdowns or pre filled to speed up the data entry and will not print on the violator's copy of citation unless specified by the City. All notes fields are available to the officer at any time from the web-based server via a Citation Detail report that contains the citation (exactly as the defendant received it), pictures, notes, diagrams, and voice notes. We can also provide specific fields (i.e., Weather, Attitude, etc.) and provide dropdowns for pre-filling the notes fields if desired. 36. User The System will have an The entire Brazos eCitation server is web-based and controls Must Have Interface administrative user every aspect of our solution. Via BuildlT, the administrator interface for reporting and can manage all aspects of the devices - users, access system configuration. levels, reporting, and automated software download. The administrator can also manage fields, screen layouts, and citation print layouts via Build IT as well. 37 User The System should reduce The City can define the fields that are commonly repeated Expected Interface repetitive keying for fields and set the defaults for all devices. Users can also be such as dates, city, state, allowed to overwrite the default values. For example, when etc. and include defaults for the officer clicks the Start Citation button, the Issue date and commonly repeated fields time as well as Offense date and time are set automatically. (i.e. city, state, We also calculate the court date field based upon the issue organization, etc.). or offense date. Any field can be either defaulted to a specific value or marked as 'carry forward'. The carry forward option allows the officer to enter the information (i.e. location, offense) and that value is carried forward from one citation to the next. An example would be when the traffic officers are running a school zone, the location and maybe the offense would already be populated after the first citation. The officer would only swipe the DL, scan the registration sticker, complete the violation supporting info (i.e. alleged speed or insurance expired date) and print the citation. 38. User The System should allow The City can designate which dropdowns are limited to the Expected Interface for data to be entered that values in the list and which allow the officer to enter is in addition to the additional values. The streets field is a common example of established pick lists. allowing the officer to enter a new street that has not been added to the established pick list. 39. User The System should allow The sequence in which data fields must be completed is at Expected Interface for data entry to any data the discretion of the City. All of our solutions are tab-based field in any sequence, and can be filled out in any order. All validation is done when the officer prints or saves the citation. 40. User The System should prompt The citation will not print or save if required fields are not Expected Interface for incomplete fields prior to complete. Whenever the system encounters an error or closing record. missing required information, the officer will receive an error message and will automatically be taken to the field in question for correction. 41. User The System should provide The City can define any number of interactive prompts. For Expected I nterface i nteractive prompts. example, if the suspect's DOB is after today, the user is immediately notified that the DOB is invalid. Additionally if the age of the suspect is less than 17 (based upon the DOB) the user is immediately notified that the suspect is a juvenile.