Laserfiche WebLink
ii?brazos <br />RFP 209-028 <br />Hand Held Ticket Writer System <br />42. User T he System should provide T he Brazos Solution is not 'device-centric' and has a 'server- Expected <br />I nterface u ser defined seeded pick c entric' methodology. Any customizations (such as user <br /> li sts, f avorite violations) are set on the server and not on the <br /> device. The value of this is that all devices operate exactly <br /> t he same. Competitive systems that allow for customization <br /> on the device loose all customizations when a device is sent <br /> i n for repair or assigned to another user. With our system, <br /> t he new device is registered with San Marcos, and then <br /> operates exactly as the each user expects. <br />43. User The System should include Please see item #35 above. Expected <br /> Interface a memo for free form <br /> entries. <br />44. User The System should provide The City can define the business rules and control how data Expected <br /> Interface validation of data entry. are validated from Build IT. Each field can be validated for <br /> data type, length, required, unique, and many other types. <br /> Each field validation is defined by the City and set via <br /> BuildlT. Any additions or changes to these business rules in <br /> the future can be either performed by the City or by Brazos <br /> at no additional charge. <br />45. User The System should provide Upon data entry, the Brazos Solution will compare the data Expected <br /> Interface prompts or alerts to entered against the existing business rules defined by the <br /> validate data entry within a City. If the data fall out of the accepted range, the user will <br /> predefined range. receive an error alert and be taken to the field in question. <br /> The citation cannot be saved until the user corrects the error. <br />46. User The System should provide As described above for both business rules and alerts, any Expected <br /> Interface intelligent normal range validation required by the City can be accomplished at no <br /> value suggestions. additional charge. For example, when a DOB is entered that <br /> is greater than the current date, the officer is notified that the <br /> DOB is invalid and prompted to reenter the DOB. <br />47. User The System should provide All help documentation is provided online via the eCitation Expected <br /> Interface on-line help for commands, server. Documents can be created by the City (or Brazos) <br /> functions, forms and form and uploaded to the help documentation. <br /> fields. <br />48. User The System should provide Once a user logs into the system, the username, date, time, Expected <br /> Interface users with an onscreen and customer name are presented at the top of the screen. <br /> reference area that <br /> provides the following <br /> information: current time, <br /> current date, ID of user <br /> signed on to system. <br />49. User The System should provide We currently do have not have a full knowledge base Desired <br /> Interface a customizable knowledge deployed to our customers. Our current help strategy is to <br /> base and/or information provide specific documentation and allow customers to add <br /> repository. additional documents. We have an internal knowledge base <br /> for our technical support staff and would be willing to work <br /> with the City on customizing this capability if desired.