My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Res 2009-171
San-Marcos
>
City Clerk
>
03 Resolutions
>
2000 s
>
2009
>
Res 2009-171
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/15/2010 9:35:16 AM
Creation date
12/23/2009 8:30:54 AM
Metadata
Fields
Template:
City Clerk
City Clerk - Document
Resolutions
City Clerk - Type
Agreement
Number
2009-171
Date
12/16/2009
Volume Book
184
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
71
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
Brazos <br />RFP 209-028 <br />Hand Held Ticket Writer System <br />68 System If the System should use Oracle The Brazos Solution does not use Oracle as the primary Expected <br /> Application then the version must be 11 i or server but can be integrated with Oracle for pushing and <br /> Software above. pulling of data. <br />69 System The System should provide a The Brazos system has an easily recognizable data structure Expected <br /> Application database structure that supports that makes integrations with'other systems very <br /> Software data exchange between Systems straightforward. The City can also make use of database <br /> and other databases. views and the Brazos Import/export Wizard to facilitate <br /> moving of data to and from other systems. <br />70 System Provide a Data schema of the Please refer to Appendix C for the ERD. We have not Expected <br /> Application proposed System. provided a complete data dictionary - just an ERD for the <br /> Software purposes of this response. If the City is willing to sign an <br /> NDA, we will provide a complete data dictionary before <br /> award. Of course, if the City selects Brazos as the vendor, <br /> we will provide a complete data dictionary as well as updated <br /> documents as the model changes. <br />Item # Category Re uirement Description : Required Response Priori <br />71 System The System should use relational The preferred DBMS is MS SQL Server 2008, but we also Expected <br /> Application database management support MS SQL Server 2005. All of these features are built <br /> Software technology to support mirror into SQL Server and can be utilized upon the City's request. <br /> imaging, stored procedures, We currently use many of these features as our strategy for <br /> triggers, portability, and performance, security, and disaster recovery. <br /> replication. <br />72 System The System should provide All data communication between the devices/servers utilize Expected <br /> Application documentation of application/data internet technologies and web services (ports 80 and 443). <br /> Software traffic including protocols and We strongly recommend all implementations (even local) <br /> ports. leverage SSL on all traffic. We also provide the ability for <br /> the City to define specific ports for each communication type <br /> if desired. While all network traffic can use SSL, we still <br /> compress and encrypt all data moving to/from any <br /> components of our system. <br />73 System The System should be able to On the eCitation server, the location of the DBMS files and Expected <br /> Application attach to computer storage stored data (pictures, video, etc) are completely configurable <br /> Software devices (SAN). for each installation. If the City desires to utilize a SAN, it will <br /> work out of the box once configured by the City. <br />74 System The System should generate MS SQL Server Reporting Services has some ability to Expected <br /> Application report and data extract files in an extract reports in XML format, but all report definitions are in <br /> Software XML format. XML format. Additionally, the import/export wizard allows the <br /> City to produce any export based upon an XSD file and save <br /> the file anywhere on the City's network. <br />75 System The application should retain data All of our systems are build with the intention of minimizing Expected <br /> Application while users are navigating data entry time and errors. For example, if the officers <br /> Software between related screens and/or complete an accident report with 2 people and 2 vehicles, <br /> applications. that information can be imported into the citation and/or tow <br /> report application without having to re-enter any information. <br />76 System The application should support There is no limit to the number of or format of the user Expected <br /> Application user-defined fields, and defined fields. Administrators add an element via BuildlT <br /> Software Application Administrators should and define where that element will be saved. They give the <br /> be able to incorporate (enter, element the appropriate properties (label name, business <br /> store, and retrieve) information in rules, etc) and place the field on the screen using the web- <br /> the form of data elements that are based screen designer. Once they test and release the <br /> not part of the standard config, all devices will download those changes during a <br /> application. sync. The Administrators will have to add those fields to the <br /> applicable reports via Reporting Services and to any <br /> imports/exports using the import/export wizard. It is <br /> important to note here: the Brazos Maintenance Agreement <br /> allows the City to make any change, at any time, to any <br /> application at no additional charge. This is through the <br /> Brazos support team or through City personnel. It is not <br /> required for the City to learn this process in order to avoid <br /> change <br />Item # Category Requirement Description Required Response Prior!
The URL can be used to link to this page
Your browser does not support the video tag.