My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
CIT COM INC. 2A -2013
Clerk
>
Contracts / Agreements
>
C
>
CIT COM INC. 2A -2013
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/28/2014 9:43:00 AM
Creation date
4/28/2014 12:03:27 PM
Metadata
Fields
Template:
Contracts
Company Name
CIT COM INC.
Contract #
A-2013-174
Agency
POLICE
Council Approval Date
11/18/2013
Insurance Exp Date
9/15/2015
Destruction Year
0
Notes
N-2012-089
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
37
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 pubiic safety partners: regionally, statewide, and <br />nationally <br />— More complete, accurate, timely, and accessible information will improve reporting <br />and trend analvsls, streamline data processing and workflow, and wilt ultimately <br />enhance public and personnel safety <br />• Potential risks associated with failing to modernize the existing technology, including: <br />— Financial (support, replacement and other recurring costs) <br />— Operatlonal (reliability and accuracy of existing systems) <br />— Anecdotal (loss and tragedy attributable to the absence or failure of required <br />technology) <br />TLisk 1 -3: Tet;hnology Acquisition <br />The initial step in compiling the procurement documents involves the documentation of the new <br />systems design, approach, Features and capabilities. Whenever possible, consideration would be <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 interface Requirements <br />• Internal and External Reporting 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 Tune, Implementation and Timeframe Requirements <br />• Adherence to standards, including; the Global Justice XML, NIEM, NextGen 911 <br />m <br />Following the inclusion of systemic requirements, we would prepare and include the following RFP o <br />chapters: <br />c <br />1. Project Background, Purpose and Goals <br />2. Current Environment <br />0 <br />3. Current and Estunated Volumes L) <br />t4 <br />
The URL can be used to link to this page
Your browser does not support the video tag.