My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
CITCOM, INC. 2 -2012
Clerk
>
Contracts / Agreements
>
C
>
CITCOM, INC. 2 -2012
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/28/2014 9:43:46 AM
Creation date
8/27/2012 11:20:33 AM
Metadata
Fields
Template:
Contracts
Company Name
CITCOM, INC.
Contract #
N-2012-089
Agency
POLICE
Insurance Exp Date
9/15/2015
Destruction Year
0
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
32
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).
View images
View plain text
- Economies of scale in terms of financial investments (both initial and recurring <br />support/maintenance) <br />- Ability to share information with public safety partners: regionally, statewide, and <br />nationally <br />- More cromplete, ac?-urate, timely, and accessible information will improve reporting <br />and trend analysis, streamline data processing and workflow, and will ultimately <br />enhance public and personnel safety <br />• Potential risks associated with failutg to modernize. the existing technology, including: <br />- Financial (support, replacement and other recurring costs) <br />- Operational (reliability and accuracy of existing systems) <br />- Anecdotal (loss and tragedy attributable to the absence or failure of required <br />technology) <br />T<:si; t-^: ?'?r_-hr?:?3•?ue P`?cqustti?n <br />"1'he initial step in compiling the procurement documents involves the documentation of the new <br />systems design, approach, Features and capabilities. Whenever possible, consideration would he <br />given to expansion capacity for the next five to ten years. The request for proposal (RFP) design and <br />configuration would include the following: <br />• Identification of Required Modules <br />• Interface Requirements <br />• Security and Access Controls <br />• Speed and Accuracy Requirements <br />• Mobile Accessibility and Reporting Requirements <br />• GIS/Mapping Integration Requirements <br />• NCIC/CLETS/DMV lnterfacc Requirements <br />• Internal and External Reportutg Requirements <br />Additionally, we would document user requirements including, but not limited to: <br />• Reliability Requirements <br />• Peripheral Requirements <br />• Documentation and Training Requirements <br />• Security and Access Controls <br />• Performance, Response Time, Implementation and Timeframe Requirements <br />• Adherence to standards, including: the Global Justice XML, NiEM, NextGen 91 1 <br />m <br />Following the inclusion oFsystemic requirements, we would prepare and include the following RFP °Q <br />0 <br />chapters: ? <br />rao <br />l . Project Background, Purpose and Goals <br />2. Current Environment o <br />3. Current and Estimated Volumes c? <br />
The URL can be used to link to this page
Your browser does not support the video tag.