Read STANDARDS text version

HOOVER POLICE DEPARTMENT

REQUEST FOR PROPOSAL 17- 04

INTEGRATED COMPUTER SOLUTION

RMS Jail CAD Mobile Computing

100 Municipal Drive Hoover, AL 35216 [email protected]

Wednesday, March 31, 2004 CITY OF HOOVER REQUEST FOR PROPOSAL (RFP) PROPOSAL #17-04 Hoover Police Department Integrated Computer System Proposals for an Integrated Computer System for the City of Hoover Police Department will be received by the City Clerk's Office, 100 Municipal Drive, Hoover, Alabama 35216, until Thursday, May 13, 2004, 5:00 p.m. CDT, at which time the proposals will be opened and read in a public forum. Late proposals will not be opened. All proposals must be sealed and marked "REQUEST FOR PROPOSAL for Hoover Police Department Integrated Computer System" with proposal number (#), opening time and date. If you are submitting a "NO PROPOSAL", please indicate this information on the outside of the envelope. Proposals should not include state sales tax or federal excise tax. All proposals and related price quotes will be placed on file and may be examined upon request. Proposals will be evaluated objectively based on the evaluation criteria detailed in Section III, Item B. Proposals receiving serious consideration will be placed on a short-list. The enclosed Letter of Intent (Appendix H) must be postmarked no later than Saturday, April 10, 2004, in order to be considered at the time of opening on May 13, 2004, 5:00 PM CDT. This letter, the specifications, proposal information, and proposal forms will comprise the total RFP package and should be read carefully. Each Proposer should respond to all information requested on the RFP forms. Proposals must be signed in ink and notarized with raised seal. Proposals not submitted as required will not be considered. The City of Hoover will host a Pre-Proposal Conference on Wednesday, April 14, 2004 at 1:00 PM CDT, 200 Municipal Drive (Hoover Library Theatre), Hoover, Alabama. Attendance is not mandatory but is encouraged. Minutes of the meeting will be emailed to all proposers who responded with a Letter of Intent. Questions will be open for discussion at this conference. Answers will not be considered binding until officially answered in writing by the Hoover Police Department. No additional questions will be considered after the Written Questions Due Date of April 28, 2004, 5:00 PM CDT. A walk-through of the Hoover Police Department facilities will be provided on the day of the Pre-Proposal Conference. All questions concerning this RFP must be sent to [email protected], and must be received no later than April 28, 2004, 5:00 PM CDT. All responses from the City will be emailed to all proposers who responded with a Letter of Intent. Responses will be completed by May 5, 2004, 5:00 PM CDT.

Hoover Police Department Integrated Computer System RFP# 17-04

All proposals must be typewritten or printed in ink on the forms provided. Proposals prepared in pencil will be automatically rejected. All proposals must be signed by an official of the company who is duly authorized to sign the proposal. Any proposal submitted without being signed will automatically be rejected. The Proposer is responsible for assuring delivery of the proposal on or before the date and local time specified, as well as for any associated delivery costs. The City is not responsible for lateness of mail, carrier, etc. Proposals may be withdrawn, modified, or resubmitted prior to the stated submission date. Modifications must be clearly marked "Final Proposal" and include the date and time of submission. Modifications submitted in any other manner will not be considered. Proposals will be maintained as public record at the Office of the City Clerk. The City of Hoover reserves the right to reject any and all proposals and to waive all formalities in awarding this proposal. The City is not obligated to award based on Requests for Proposals. If you have any questions concerning this Request for Proposal or any part thereof, please email [email protected] Yours truly,

Linda Crump City Clerk Attachments

Page 2 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

1

1 2 3 4 4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.8 4.9 4.10 4.11 5 5.1 5.2 5.3 5.4 6 6.1 6.2 6.3 6.4 6.5 6.6 6.7 7 7.1 7.2 7.3 7.4 7.5 7.6 7.7 7.8 7.9 7.10 7.11 7.12 7.13 7.14 7.15 8 8.1

TABLE OF CONTENTS

TABLE OF CONTENTS INTRODUCTION AND PROPOSER INSTRUCTIONS PROPOSAL PROCESS INSTRUCTIONS GENERAL REQUIREMENTS STANDARDS NETWORKING SERVICES RELIABILITY MAXIMUM TIME FROM CALL TO RESPONSE USER INTERFACE DATABASE QUERY CAPABILITIES DATA DUPLICATION SCALABILITY ALABAMA REPORTING NEEDS REPORTING GENERAL RMS FUNCTIONS GENERAL RMS FUNCTIONS DETAILED REQUIREMENT FOR MASTER TABLES INTEGRATION WITH CAD TRAINING EVENTS / REPORTS INCIDENT AND SUPPLEMENTAL REPORTING FIELD INTERVIEWS ARREST REPORTS JUVENILE CUSTODY RECORDS EVIDENCE / PROPERTY LOCAL WARRANTS TRAINING SPECIALTY RECORDS AND REPORTS RACIAL PROFILING CRIME SCENE REPORTING TRAFFIC ACCIDENTS DRIVING WHILE INTOXICATED ARRESTS / CHARGES COMPLAINTS SEARCH WARRANT PROCESS COURT ORDER MANAGEMENT CONFIDENTIAL INVESTIGATIVE ACTIVITIES CASE MANAGEMENT WANTED / DANGEROUS / MISSING PERSONS TOWED VEHICLES TRAFFIC VIOLATIONS PARKING CITATIONS PAWNSHOP SUPPORT GENERAL REPORTING FEATURES MAPPING GIS INTERFACES 3 6 15 18 18 18 18 19 20 20 22 22 22 23 23 24 24 25 30 30 30 30 31 32 33 34 37 40 40 40 40 40 41 41 42 42 43 43 45 45 46 46 46 46 47 47

Page 3 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

8.2 9 9.1 9.2 10 10.1 10.2 10.3 10.4 10.5 10.6 10.7 10.8 10.9 10.10 10.11 11 11.1 11.2 11.3 11.4 11.5 12 12.1 12.2 12.3 12.4 12.5 13 13.1 13.2 13.3 TRAINING JAIL MANAGEMENT JAIL MANAGEMENT SYSTEM (JMS) TRAINING CAD REQUIREMENTS GENERAL REQUIREMENTS: HANDLING CALLS FOR SERVICE AND OTHER EVENTS TOWED VEHICLE MODULE DISPATCH INTERFACES CAD MESSAGING PAGING INTERFACE RIP AND RUN PRINTING CAD SUPERVISOR REQUIREMENTS CAD ANALYSIS REPORTS REMOTE CAD FUNCTIONALITY FIREHOUSE INTERFACE TRAINING MOBILE DATA MOBILE DATA SYSTEM (MDS) FUNCTIONS MOBILE DATA REPORTING MESSAGE SWITCH REQUIREMENTS STATE NCIC REQUIREMENTS HOST SYSTEMS INTERFACE ADMINISTRATIVE FUNCTIONS WORK SCHEDULES TRAINING RECORDS AGENCY PROPERTY INVENTORY ELECTRONIC INTERFACES COURT MANAGEMENT SYSTEM (CMS) IMPLEMENTATION INSTALLATION NEEDS FILE MIGRATION / CONVERSION REQUIREMENTS AUDIT AND SECURITY 50 51 51 53 54 54 64 64 65 66 66 67 67 69 69 70 70 70 71 72 74 74 75 75 76 76 76 77 78 78 78 79 80 84 85 86 89 90 91 93 94 95 98 99

GLOSSARY OF TERMS ABBREVIATION OF TERMS APPENDIX A - RESPONDER COVER LETTER APPENDIX B - QUALIFICATIONS AND REFERENCES APPENDIX C - TECHNICAL SPECIFICATIONS APPENDIX D - HARDWARE AND/OR NETWORK DIAGRAMS APPENDIX E - SERVICE AND MAINTENANCE APPENDIX G - PRICE PROPOSAL APPENDIX H - LETTER OF INTENT APPENDIX I - SUPPORT (HOW YOUR SOLUTION WORKS) APPENDIX J - TRAINING / EDUCATION APPENDIX K - POLICE REPORTS

Page 4 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

APPENDIX L - JAIL FORMS APPENDIX M - PROPERTY FORMS APPENDIX N - COURT FORMS APPENDIX O - NCIC 2000 APPENDIX P - RESPONSE WORKSHEET APPENDIX R - ACJIC AUDIT REQUIREMENTS APPENDIX S - TEST REQUIREMENTS APPENDIX T - SECURITY APPENDIX U - CURRENT AS400 CAD HARDWARE CONFIGURATION 100 101 102 103 104 106 107 110 111

Page 5 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

2

INTRODUCTION AND PROPOSER INSTRUCTIONS

Hoover Police Department Background

The Hoover Police Department is a multidimensional public safety agency providing Crime Prevention, Law Enforcement, Corrections, and Fire and EMS Dispatch for the 65,885 Hoover citizens and a large number of workers that travel to the City each business day. The City of Hoover covers 38.95 square miles and is annually expanding its boundaries. The Department has an authorized strength of 190 full time employees, including 139 sworn positions and 51 civilian positions. The City of Hoover's fiscal year is from October 1 through September 30. The Department is divided into three areas: Patrol, Investigations, and the Administrative Unit. It is also responsible for a public safety dispatch center. There are currently eight dispatch workstations. The dispatch center is not only responsible for police calls, but also for nine fire stations and all EMS calls for service. Click here for Hoover Police Organizational Chart. PROJECT INTENT The City of Hoover, Alabama desires to obtain a computerized, fully-integrated, scalable law enforcement information management system, to include Computer Aided Dispatch (CAD), Records Management System (RMS), Jail Management System (JMS), Mobile Data Solution (MDS) and Geographic Information modules. Proposed systems must be capable of integration with the City's computer network, including interface with Hoover Fire Department software program Firehouse Software Enterprise Version, and must be expandable to support future growth in requirements, personnel, facilities, and locations. This will be a "turn-key" solution. The Department expects that a single vendor will propose all project elements, subcontracting certain aspects as needed. Project elements requiring proposals have been divided into three (3) phases as follows:

Application Software

Phase I ­ Projected implementation ­ FY2004-2005 Computer Hardware and Setup Software Implementation Internal and External System Interfaces Data File Conversion ­ All Phases involved Records Management System Jail Management Mapping System Integration Comprehensive Training Hardware Maintenance Software Maintenance

Page 6 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

Phase II ­ Projected implementation ­ FY 2005 Computer Aided Dispatch CAD Client Workstation Setup Comprehensive Training Phase III ­ Projected implementation ­ FY2006 Mobile Data Solution Additionally, the City seeks assurance of: · · · · Effective Project Management Long-Term Useful Life State-of-the-Art Technology Competitive Prices

Consideration shall be given to those Proposers who demonstrate the ability to perform successfully under the terms and conditions of this proposed procurement. Additionally, such matters as software quality, contractor integrity, record of past performance including prior successful implementation of proposed products, and financial and technical resources will be considered. Each Proposer must have established a state and/or national reputation for the planning, supplying, installing and maintaining their systems. Redundant systems must be provided.

Page 7 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

CITY OF HOOVER

PROPOSERS SHOULD RETAIN THESE INSTRUCTIONS, CONDITIONS, AND SPECIFICATIONS FOR FUTURE REFERENCE.

I.

GENERAL INSTRUCTIONS

A. Termination for Non-Appropriations:

Funds for the Contract are payable from City appropriations. In the event no funds or insufficient funds are appropriated and budgeted in any fiscal year for payments due under the Contract, the City shall immediately notify Contractor or its assignee(s) of such occurrence, and the Contract shall create no further obligation of the City as to such current or subsequent fiscal years, and shall be null and void, except for the portions of payments herein agreed upon. In such event, the Contract shall terminate on the last day of the fiscal year for which appropriations were received, without penalty or other expense to the City of any kind. After such termination of the Contract, the City shall have no continuing obligation to make purchases under the Contract. No right of action or damages shall accrue to the benefit of the Contractor or its assignee(s) as to that portion of the Contract, which may so terminate.

II.

DISQUALIFICATION OF PROPOSALS

Proposals may be disqualified before the awarding of the Contract for any of the following: A. Failure to mark envelope as required; B. Failure to sign or notarize the proposal document; C. Failure to include requested information or other details; D. Failure to follow set format using forms and instructions provided; E. Excessive errors in calculating prices or totals; F. Failure to include Bid Bond, if applicable.

III.

METHOD OF AWARD

A. The Contract will be executed within one hundred twenty (120) days of proposal opening to the Proposer with the highest score in the grading process described below. The City of Hoover reserves the right to negotiate a contract with the selected Proposer. If a contract cannot be agreed upon the City of Hoover reserves the right to negotiate a contract with the Proposer having the second highest score, or to begin the Request for Proposal process again.

Page 8 of 111

Hoover Police Department Integrated Computer System RFP# 17-04 B. Evaluation & Award Process Proposals will be evaluated objectively based on conformity with the specifications as determined by the evaluation criteria listed below and a short-list will be developed. Proposers on the short-list will then be evaluated based on references, oral presentations, demonstrations, and site visits to similar installations. Written responses to queries for further clarification may also be required of the Proposer. Contract negotiations will begin immediately with the selected Proposer.

Initial Evaluation Criteria:

Qualifications & Experience Functional Systems Proposal Hardware and Network Proposal Service & Maintenance Proposal Performance Proposal Implementation Proposal Contractual Proposal SCORING LEGEND

Final Evaluation Weighting:

Price Proposal Initial Qualification Criteria References Presentations/Demonstrations Site Visits, if done Best and final offers, if considered

Value Description

5 4 3 2 1 Exists in your current solution Under development Minor customization required Major customization required Not available in your solution

IV.

CONTRACT PERIOD

A. The Contract will be for a period of one year from date of award, and may be renewed for two (2) consecutive one-year periods with agreement from both parties involved.

V.

PRICING

A. Prices are not to exceed four decimal places (i.e., $1.2525). Prices quoted must remain firm for the entire period of the contract. B. Proposers must certify that the prices included in the proposal are accurate and binding, and that all costs are shown and accurately reflect the total proposal cost at a firm, fixed price. (Appendix A) C. The City of Hoover reserves the right to exercise the implementation of Phases II and III as specified in original RFP and to negotiate pricing for subsequent Phases II and III at the lower of either the bid price or the price at the date of implementation.

Page 9 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

VI.

PAYMENT TERMS AND CONDITIONS

A. Payment terms and conditions will be negotiated as part of the Contract using milestones as guidelines. All payments will be made solely to the Contractor.

VII.

QUANTITY, QUALITY AND CONTRACT CONDITIONS

A. The quantity of items specified being purchased herein are minimum amounts. The City of Hoover reserves the right to make additional purchases at the contract price during the contract period. B. The City of Hoover reserves the right to make quality inspections by any reasonable means. C. The Contractor will be solely responsible for performance. The City will rely upon the Contractor for full, complete, and satisfactory performance under the terms and conditions of the Contract. D. If the Contractor proposes use of subcontractors, a list of subcontractors must be submitted to the City with the proposal for approval prior to engagement of any subcontractor. If the Contractor's services provided for hereunder include services, equipment, or materials supplied by a subcontractor, the Contractor must act as the prime contractor for these items and assume full responsibility for performance hereunder. The Contractor will be considered the sole point of contact with regard to all situations, including payment of all charges and the fulfillment of all other requirements. E. If the Contractor proposes to enter into a partnership in order to complete the proposed project, the details must be included in the submitted proposal and approved by the City of Hoover. F. Subcontractors will subject to the same terms and conditions of the Contract as the Contractor. No item substitutes will be allowed on purchase orders without written approval of the authorized City of Hoover representative. G. The Contractor and all subcontractors will be subject to compliance with all federal, state and local laws and ordinances, including Non-Discrimination Clause and Certification of Drug-Free Workplace. H. All change orders, alterations, amendments and other modifications will not be effective unless reduced to writing and approved by the City's authorized representative and the Contractor. All questions, problems, or changes arising after award of the Contract shall be directed to the City's designated representative. I. The Contract may be terminated for any reason by the City of Hoover with thirty (30) days written notice to the Contractor. In the event that the Contract is terminated or canceled upon request of the City without thirty (30) days advance written notice, then the City shall negotiate reasonable termination costs, if applicable.

Page 10 of 111

Hoover Police Department Integrated Computer System RFP# 17-04 J. The Contract may be canceled and terminated by the City at any time within the contract period whenever it is deemed by the City that the Contractor has materially breached or otherwise materially failed to comply with its obligations thereunder. The City will not be liable for termination costs and the thirty (30) day written notice requirement is waived. K. A Contractor who violates the contract will be considered in breach and subject to termination for cause. Contractors may be suspended or debarred from doing business with the City. Examples of Contractor violations include, but are not limited to: · · · Contractor adding items to the contract without approval; Contractor increasing contract price without approval; Misrepresentation of the contract.

L. In the event of non-compliance by the Contractor, the City will provide the Contractor with a Notice to Cure, which will give the Contractor thirty (30) days to remedy the noncompliance. If the remedy is not to the satisfaction of the City, this will serve as just cause for termination of the Contract. M.In the event the City is dissatisfied with any material, services, supplies, products or other items of any type or variety under this agreement, the City will have the right to deal directly with the other suppliers without penalty or interference from Contractor. N. Failure to deliver as specified herein and in accordance with the proposal submitted, including proposed delivery will constitute sufficient grounds for termination of the Contract at the option of the City of Hoover and forfeiture of performance bond, if applicable. O. The City of Hoover may award in any manner that is in the best interest of the City. P. The City of Hoover reserves the right to purchase any item from the State of Alabama Contract.

VIII. DELIVERY

A. The project start date will be within sixty (60) days of executed Contract. Failure to deliver as specified and in accordance with the proposal submitted, including all proposed target dates, will constitute sufficient grounds for termination at the option of the City of Hoover.

IX.

SPECIFICATIONS

A. Use of specific names and numbers is not intended to restrict any seller and/or manufacturer, but is solely for the purpose of indicating the quality of materials, products, and service best adapted to the City's intended use.

Page 11 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

X.

TAXES

A. The City of Hoover is exempt from all taxes. This statement in no way is to be construed as relieving a seller or contractor from such liability. B. The City of Hoover will provide the Contractor with purchase orders.

XI.

CONDITIONS

A. Proposer certifies by submitting a proposal that the Proposer is fully aware of the conditions of service and purpose for which items(s) included in this RFP are to be purchased, and that proposals will meet these requirements of service and purpose to the satisfaction of the City of Hoover. B. During the term of the Contract, the Contractor shall be responsible for obtaining, and maintaining in good standing, all licenses, permits, inspections and related fees for each or any such licenses, permits and /or inspections required by the state, county, city or other government entity or unit to accomplish the work specified in this solicitation and the related Contract. The Contractor will insure that all subcontractors comply with City of Hoover ordinances concerning business license procurement. C. The Contractor shall assume all liability for and shall indemnify and save harmless, the City of Hoover, its servants, agents and employees, from all damages and liability for injury to any person or persons, and injury to or destruction of property, including loss of use thereof, by reason of an accident or occurrence arising from operations under the Contract, whether such operations be by himself or anyone directly or indirectly employed by him, occurring on or about the premises or the ways and means immediately adjacent, during the term of the Contract, or any extension thereof, and shall also assume the liability for injury and/or damage to adjacent or neighboring property by reason of work done under the Contract. D. The Contractor will take all reasonable precautions for the safety of, and shall provide all reasonable protection to prevent damage, injury, or loss to: 1. All employees on the project and all other persons who may be affected thereby; 2. All furnishings, materials, and equipment to be incorporated therein, whether in storage on or off the site, under the care, custody, or control of the supplier; 3. Other property at the City facility or adjacent thereto, including the building and its contents, trees, shrubs, lawns, walks, pavements, and roadways. The Contractor shall promptly remedy all damage or loss to any property referred to above, caused in whole or in part by anyone directly or indirectly employed by the Contractor. E. Contractor shall have sufficient insurance for all claims including those described below, whether such claims are directly or indirectly related to Contractor or subcontractors.

Page 12 of 111

Hoover Police Department Integrated Computer System RFP# 17-04 Minimum limits of liability for each sector of insurance shall be $1,000,000 with a $4,000,000 umbrella or excess policy over each liability category. 1. Claims under workers' or workmen's compensation, disability benefit and other similar employee benefit acts; 2. Claims for damages because of bodily injury, occupational sickness or disease, or death of his employees; 3. Claims for damages because of bodily injury, sickness or disease, or death of any person other than his employee; 4. Claims for damages insured by usual personal injury liability coverage which are sustained: a. by any person as a result of an offense directly or indirectly related to the employment of such person by the Contractor; b. by any other person; 5. Claims for damages, other than to the work itself, because of injury to or destruction of tangible property, including loss of use resulting therefrom; claims for damages because of bodily injury or death of any person or property damage arising out of the ownership, maintenance, or use of any motor vehicle.

XII.

BONDS

The following conditions will be included in the Contract and are the responsibility of the Contractor:

A.

Bid Bond - The State of Alabama Bid Law requires all bids exceeding ten-thousand ($10,000) dollars to be backed by a Bid Bond. The amount of this bond will be five percent (5%) of the total bid. Performance Bond - A Performance Bond equal to the total amount of the Contract price will be required of the Contractor as security for the faithful performance and execution of all Contractors' obligations under the Contract. The bond shall be executed by such sureties as are licensed to conduct business in the State of Alabama.

B.

XIII. CITY OF HOOVER GENERAL CONDITIONS

A. Each Proposer will become fully acquainted with the scope of this RFP. Failure to adhere to this requirement shall in no way relieve such Proposer of any obligation with respect to this proposal or to any Contract resulting hereof. Proposers must notify the City of all costs reasonably expected. Failure to inspect, familiarize themselves with, or otherwise gather information as to the total cost to the City, will, in addition to any and all other remedies available, create cost difference liabilities and claims against the Proposer awarded the Contract.

Page 13 of 111

Hoover Police Department Integrated Computer System RFP# 17-04 B. Every effort has been made to insure that all information needed by the Proposer is included herein. If a proposal cannot be completed without additional information, written questions may be submitted to mailto:[email protected] on or before April 28, 2004, 5:00 PM CDT. All questions and written replies will be made available to all proposers by May 5, 2004, in the form of a written amendment and will be made a part of this RFP. C. If it becomes necessary to revise any part of this RFP, an authorized City representative will issue a written amendment. The City shall not be legally bound by any interpretation that is not in writing. All amendments will be complete by May 5, 2004, 5:00 PM CDT, excepting correction of material inadvertent statements and omissions. D.The Contract to be negotiated will be for a period of (1) year from date of award. The City has the option to extend the Contract for (2) additional years, implementing Phases II and Phase III, based on a review of prices, services rendered, and solution supplied. E. By signing and returning the RFP Cover Letter (Appendix A), the Proposer agrees to meet all the conditions and specifications set forth above in Sections I through XIII.

Page 14 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

3 Proposal Process Instructions

In preparation for the Pre-Proposal Conference, Proposers are encouraged to submit written questions pertaining to the RFP to the email address provided by Monday, April 12, 2004, 5:00 PM CDT. Significant Dates The following dates will govern this procurement:

ACTIVITY

RFP Issue Date Letter of Intention to Propose (Required) Appendix H Pre-Proposal Conference (Optional) Final Written Questions Due All Questions Answered/ All Amendments/Revisions Complete Proposals Due

DATE

03/31/2004 postmarked by 4/10/2004 04/14/2004 04/28/2004 05/05/2004 05/13/2004

TIME

5:00PM CST

1:00PM CDT 5:00PM CDT 5:00 PM CDT 5:00PM CDT

ALL questions about this RFP must be in writing and addressed to: Email Address: [email protected] Submit 19 copies (three original, two electronic and 14 copies) of the proposal to: City of Hoover Attention: Linda Crump, City Clerk 100 Municipal Drive Hoover, Alabama 35216

Mark Package: HPD Integrated Computer System RFP Response

Proposers must follow the format outlined below and complete the forms furnished in the Appendices. The Hoover Police Department will not determine exceptions based on a review of any attached sales or manufacturer's literature. Any costs associated with preparing proposals in response to this RFP are the sole responsibility of the Proposer. All proposals and supporting materials, as well as correspondence relating to the RFP, become the property of the City of Hoover.

Page 15 of 111

Hoover Police Department Integrated Computer System RFP# 17-04 DEFINITIVE LIST OF PROPOSAL CONTENTS In order to fairly evaluate all proposals, a uniform proposal format is required. Proposal are to be bound (loose-leaf binders are sufficient) and numbered using similar sections and page numbering schemes as used in this RFP. Response forms provided in the RFP must be included as part of the pertinent sections. APPENDIX A Cover Letter: Submit a copy of the provided cover letter (Appendix A) signed by the responsible official in your organization, certifying the accuracy of all information in your proposal, and certifying that your proposal will remain valid for one hundred twenty (120) days from the date opened by the City. It should also include the names of individuals within the company to contact for technical, pricing, and contractual questions. APPENDIX B Qualifications and References: Include the form provided (Appendix B) at the end of this section. Each of these areas may be expanded with additional narrative. 1. 2. 3. 4. 5. 6. 7. Company Background Project Office Financial Data Client References reference Similar Customers Use of Subcontractors Contractor and Subcontractor information

APPENDIX C Technical Specifications for Requirements for Proposal (use form provided) APPENDIX D Hardware/Network Proposal Configuration Proposal (use form provided) APPENDIX E Service and Maintenance Proposal (use form provided) APPENDIX F Implementation Proposal with Schedule (use form provided) APPENDIX G Price Proposal (use form provided) APPENDIX H Letter of Intent to Propose (use form provided) APPENDIX I Solution Description ­ How your support works APPENDIX J Training / Education APPENDIX K Police Forms APPENDIX L Jail Forms

Page 16 of 111

Hoover Police Department Integrated Computer System RFP# 17-04 APPENDIX M Property Forms APPENDIX N Court Forms APPENDIX O NCIC 2000 Regulations APPENDIX P Response Worksheet APPENDIX Q Council Pricing Sheet ­ REQUIRED MUST be included as final page of proposal APPENDIX R ACJIC Audit Requirements APPENDIX S Testing APPENDIX T Security APPENDIX U Current AS/400 CAD Hardware configuration

Page 17 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

4

4.1

4.1.1 4.1.2

GENERAL REQUIREMENTS

Standards

The solution MUST be constructed using open standards. The solution MUST be year 2000 compliant. (i.e. MUST utilize a four digit year field to enable arithmetic calculations to be performed on any selected combination of date fields). All software supplied with the solution MUST be certified as Year 2000 compliant and shall be warranted against other date specific errors similar to the Year 2000 limitation The solution MUST be ODBC compliant. The solution should be global JXDM (Justice Extensible Data Model) conformant or can be made conformant. The responder MUST use standards that have been adopted by recognized standards bodies such as International Organization for Standardization (ISO), Institute of Electrical and Electronic Engineers (IEEE), American National Standards Institute (ANSI), and Geographical Information System (OpenGIS, trademark). The responder MUST be compliant and use governmental standards such as National Emergency Numbers Association (NENA), National Crime Information Center (NCIC 2000), Health Insurance Portability and Accountability ACT of 1996 (HIPPA).

4.1.3

4.1.4 4.1.5 4.1.6

4.1.7

4.2

4.2.1

Networking Services

See APPENDIX D.

4.3

4.3.1 4.3.2 4.3.3 4.3.4

Reliability

The solution MUST be capable of providing 24 X 7 operation. The solution MUST have reliability, based upon consecutive 7-day periods. The solution MUST allow for performing backups, while the system data base is in use, without noticeable degradation of performance. The solution MUST provide the capability to eliminate any "single point of failure" for all critical components.

Page 18 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

4.3.5 4.3.6 4.3.7 4.3.8 4.3.9

CAD system reliability MUST be 99.99% availability (a maximum of 50 minutes per year unavailability). RMS system reliability MUST be 99.9% availability (a maximum of 500 minutes per year unavailability). JMS system reliability MUST be 99.9% availability (a maximum of 500 minutes per year unavailability). MDS system reliability MUST be 99.9% availability (a maximum of 500 minutes per year unavailability). Appropriate response times for specific functions are listed below 4.3.9.1 Select and Display Any Master Incident Record 4.3.9.2 Select and Display Master Name Record 4.3.9.3 Search and Display all History of a Specific Person 4.3.9.4 Select and Display Specific Arrest Record 4.3.9.5 Select and Display Court Docket Information Seconds 4.3.9.6 Select and Display all Incidents at a Specific Address (5) Seconds (5) Seconds (5) Seconds (5) Seconds (5) (15) Seconds

4.3.9.7 Search Field Interview File for a Match of Height, Weight, Race and Age in a specific area of municipality (15) Seconds 4.3.10 All RMS transaction and response times are at maximum workload, with a minimum of 1,000,000 cases on file.

4.4

4.4.1 4.4.2 4.4.3

Maximum Time From Call to Response

Telephone response by Responder's Maintenance personnel (first level) MUST be within 30 minutes of initial call for CAD problems On-site response by Responder's maintenance personnel MUST be within 1 hour of initial call for CAD problems Telephone response by Responder's maintenance personnel (first level) MUST be within 90 minutes of initial call for RMS problems On-site response by Responder's maintenance personnel MUST be within 2 hours of initial call for RMS problems

4.4.4

Page 19 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

4.5

4.5.1 4.5.2

User Interface

The solution should provide for a Graphical User Interface (GUI) where applicable. The interface should provide seamless screen navigation based on operation in process (e.g. automatically opening a name window as an incident report is entered). The interface should support generic operations for text (e.g. cut, past, copy) portable across modules. The interface should support multiple input techniques (e.g. mouse, menu selection and / or keyboard). The interface should support multiple options for accomplishing a task (e.g. menu selection, button, and / or accelerator keys). The interface should provide "undo" mechanisms to allow the user to reverse an operation. The solution should provide data validation where applicable. The solution should be capable of populating screens from other modules. Error messages, when used, should be specific and meaningful to the party responsible for correcting the problem. The solution should provide spell check with user-configurable dictionary for all narrative text fields.

4.5.3 4.5.4 4.5.5 4.5.6 4.5.7 4.5.8 4.5.9 4.5.10

4.6

4.6.1 4.6.2 4.6.3 4.6.4 4.6.5

Database Query Capabilities

The solution should employ relational database that supports Standard Query Language (SQL). The solution should provide ad-hoc query capabilities in which users can develop and save their own queries with minimal training. The underlying database should be supported by common ad-hoc query and report generation tools. The solution should provide for effective search capabilities at the user's option: Soundex Searches (e.g. Cathy returns Kathy; Smith returns Smyth; etc)

Page 20 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

4.6.6 4.6.7 4.6.8 4.6.9 4.6.10

Similar Name Searches (e.g. Jim returns James; Chuck returns Charles; etc) Wildcard Searches (e.g. Kat* returns Kathy, Katherine or Kate; etc) Exact Match Searches Text Searches of Narrative Data The solution MUST provide the ability to search for information using any field or combination of fields. For each field to be searched, the user must be able to select the type of search, such as: 4.6.11.1 4.6.11.2 4.6.11.3 4.6.11.4 4.6.11.5 4.6.11.6 4.6.11.7 None Equal to (default search type) Not equal to Less than Greater than Between (date/time, day of week, or other value range) Partial pattern match

4.6.11

4.6.12 4.6.13 4.6.14 4.6.15

Search criteria for a field should be displayed using a right mouse click. Search criteria should not be case sensitive but capable of limiting the search with said criteria. The solution MUST provide the ability to search text fields, including the use of wild card characters. The solution MUST provide the ability to search on parts of names, addresses or other entries, using wild card characters for unspecified sections of the entry. The solution MUST provide the ability to go directly to desired fields to enter search criteria eliminating the requirement to proceed consecutively through numerous preceding fields. The solution MUST provide the ability to list in table form all records matching the search criteria. The user should be able to mark records in this list for inclusion in a final list, with the ability to perform another search in the same table and join the resulting lists together in one list.

4.6.16

4.6.17

Page 21 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

4.6.18 4.6.19

The user MUST be able to select and display the needed record from the above-mentioned list. The solution MUST enable the user to join search results from two different tables by eliminating all records that do not have a link between the two sets.

4.7

4.7.1

Data Duplication

The solution should use master tables for fundamental entities (e.g. persons, addresses, vehicles, incidents, and property) so that these entities can be efficiently linked. The solution should not require duplicate entry of data. For example, once a person's name, date of birth, sex, race, etc., have been entered in an incident report, that person should only have to be referenced in subsequent reports. The solution should prompt the user when identifying information matches previously entered information. That prompt should allow the user to select a matching entry, which should automatically populate appropriate identifying fields. The solution should provide the capability for authorized users to efficiently merge these entities if duplicates are entered in error.

4.7.2

4.7.3

4.7.4

4.8

4.8.1 4.8.2

Scalability

The solution MUST be scalable to support a growing number of concurrent users in the future. The solution MUST be capable for supporting regional or statewide shared information systems that may be created in the future. The solution should support multiple jurisdictions, such that certain data can be private within an agency, and other data can be shared among agencies. For example, officer schedules and training records could be private, while arrests and incident reports could be shared.

4.8.3

4.9

4.9.1 4.9.2

Alabama Reporting Needs

The solution MUST conform to NCIC 2000 requirements for reporting. See Appendix O. Capture and support data for Part 1 Crimes (including state data transmission) along with UCR Summary Reporting

Page 22 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

4.9.3

The solution MUST provide the capability to remove all references of specified information from the various RMS/JMS databases as required by court orders. The solution shall produce a report indicating the "purged" information for return to the court. This functionality must allow Hoover Police personnel the flexibility to expunge specific or global information related to an individual as required by the court order.

4.10 Reporting

4.10.1 The solution MUST be capable of printing required paper documents in final form. Forms are provided in Appendix K (Police Forms), Appendix L (Jail Forms), Appendix M (Property Forms), Appendix N (Court Forms) The solution MUST be capable of printing filtered media reports from the print menu, eliminating user intervention to edit required fields prior to printing. The solution MUST have a basis for preparing various statistical and graphic reports.

4.10.2

4.10.3

4.11 General

4.11.1 4.11.2 The solution should provide automated individual sequence numbering (with override capabilities) for cases and events. The solution MUST be capable of supporting the scanning, storage, and retrieval of documents as well as being able to associate scanned documents with records in the form of images. The solution MUST be capable of archiving data and retrieving archived data. The solution MUST provide a non-production mode of operation to support testing, training and demonstrations. The solution MUST support a multi-agency environment accommodating the Police and Fire Departments as well as the addition of other Public Safety Agencies as needed. The solution shall be user friendly and MUST offer a consistent user interface in order to minimize user training and system administration. The solution MUST be transaction-oriented, designed to support multiple PC workstations. The solution MUST provide a comprehensive audit trail, with the identification of individuals entering and updating each transaction

4.11.3 4.11.4 4.11.5

4.11.6 4.11.7 4.11.8

Page 23 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

4.11.9

The solution MUST provide System Security to restrict access through use of a password system at the terminal, operator, and application levels (both inquiry and update). The solution MUST support ESRI map data

4.11.10

4.11.11 The solution MUST provide for the ability to encrypt data, which will travel via public carriers

5

5.1

5.1.1 5.1.2 5.1.3

RMS Functions

General RMS Functions

The solution should link persons, addresses, property, and vehicles, if required, to each event. The solution should allow for retrieval of information by one or any combination of elements or events. For each event, the solution should be capable of generating a printed report in the format prescribed by the agency. (See Appendix K Police Forms) The solution should provide automated interfaces to other sources of information needed. National Crime Information Center (NCIC) State Criminal Justice Information Systems (CJIS) State Motor Vehicle Registration Files Agency Computer Aided Dispatch System (CAD) Agency Jail Management System (JMS)

5.1.4 5.1.5 5.1.6 5.1.7 5.1.8 5.1.9

5.1.10 Police Property Management 5.1.11 Towing Module 5.1.12 Livescan Fingerprint System 5.1.13 Mugshot System 5.1.14 Municipality Court Management System (CMS) 5.1.15 Municipality Business License Information Systems 5.1.16 Regional Shared Information System (Future)

Page 24 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

5.1.17 Any Recommended Interfaces By Proposer 5.1.18 The solution should provide combined and complete local, state, and federal queries by name and date of birth, any identification number (e.g. driver's license; FBI; State ID number, social security, etc) or any combination of fields selected, through a single request the solution should automatically run or not run a query to NCIC based whether or not sufficient fields are entered. The solution should provide a detailed audit trail of all events and activities, additions, changes, deletions, etc. The solution should provide an audit trail of queries to the state and federal level sufficient to meet all NCIC 2000 and state audit and record requirements ( See Appendix O). The solution should provide the capability for real-time, direct data entry of incident, supplemental, arrest, and all other reports created by officers in the field. The solution should not require duplicate entry of data. For example, once a person's name, date of birth, sex, race, etc., have been entered in an incident report, that person would only have to be referenced in subsequent reports. The solution should enable the user to append existing information of any kind to both new and existing information.

5.1.19 5.1.20

5.1.21

5.1.22

5.1.23

5.2

5.2.1

Detailed Requirement for Master Tables

A central names table must be provided to hold ALL names entered into the system. The name table should accommodate the following types of names: 5.2.1.1 Person 5.2.1.2 Business 5.2.1.3 Group names

5.2.2

Information in the name table must be central to the system in order to eliminate duplicate entry of name information. A name record in the central names table must be accessible by other modules without reentering name information. The solution must provide the capability to link related records to the name record in such a way that the user can display a list of related

5.2.3

Page 25 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

records directly from the name record. The user must then be able to display a related record from that list. 5.2.4 If separate events have been linked to two people, later determined to be the same person, the solution should allow an authorized user to easily merge the data to one person without loss of data or re-entry of any information. Descriptive information on multiple scars, marks and tattoos must be accommodated. The location of the mark on the body must be coded so that users can perform searches based on the location on the body. Coding must conform to NCIC requirements. The solution must provide for any number of alias names, with a physical description for each alias. An inquiry on a name must alert the user that an alias name exists and lead to its known alias(s) or real name. The solution must provide the ability to link digital images and other multimedia content such as sound clips, digital pictures, or movie clips, to the name record. The solution must provide the ability to link document images to the name record. The solution must have the capability to "real time interface" to a Livescan fingerprint system. The solution must provide the ability to record information about the race and ethnicity of persons involved in routine traffic stops and any other law enforcement activities. This information must be able to be used in a management profiling report. The solution must provide a history of all past addresses and home telephone numbers associated with a name record, and any name changes. The solution must accommodate Modus Operandi information for each name and provide the ability to find persons in the system with particular modus operandi. The solution must be capable of appending multiples of any field(s) to an individual. The solution must be capable of providing a user defined "role" indicator table for each association of the master name record with an incident to include but limited to: 5.2.14.1 Suspect

5.2.5

5.2.6

5.2.7

5.2.8 5.2.9 5.2.10

5.2.11

5.2.12

5.2.13 5.2.14

Page 26 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

5.2.14.2 5.2.14.3 5.2.14.4 5.2.14.5 5.2.14.6 5.2.15

Arrested Complainant Witness Victim Owner

Links should include: 5.2.15.1 5.2.15.2 5.2.15.3 5.2.15.4 5.2.15.5 5.2.15.6 5.2.15.7 5.2.15.8 5.2.15.9 Incident History Arrest History Criminal History Jail Records Warrants Summons Citations Field Interviews Complaints

5.2.15.10 Court Orders 5.2.15.11 Orders of protection 5.2.15.12 Vehicles 5.2.15.13 Property, etc. 5.2.16 5.2.17 A master vehicle table must be provided for storing ALL vehicles entered into the system. Information in the vehicle table must be central to the system in order to eliminate duplicate entry of vehicle information. The system must be capable of associating vehicles to persons, incidents, locations, etc. The solution must provide the capability to link related records to the vehicle record in such a way that the user can display a list of related records directly from the vehicle record. The user must then be able to display a full record from that list.

5.2.18

Page 27 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

5.2.19

The solution must capture all necessary vehicle information, including but not limited to the following: 5.2.19.1 5.2.19.2 5.2.19.3 5.2.19.4 5.2.19.5 5.2.19.6 5.2.19.7 5.2.19.8 License plate number Type State VIN (Vehicle Identification Number) Year Make Model Description

5.2.19.8.1 Colors 5.2.19.8.2 Doors 5.2.19.8.3 Characteristics 5.2.19.9 Storage location

5.2.19.10 Tag Status 5.2.19.11 Date received or recovered 5.2.19.12 Responsible agency and officer 5.2.19.13 Owner 5.2.19.14 Related Incident 5.2.19.15 Recovered value 5.2.19.16 Value when Stolen 5.2.19.17 Holds 5.2.19.18 Reason for Hold 5.2.19.19 Insurance Compensation

Page 28 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

5.2.20

The solution must accommodate different types of vehicles, including cars, trucks, motorcycles, boats and airplanes and provide a field for indicating vehicle type. The owner name, as with all names in the system, must become part of the master name table. The solution must allow linking of vehicle information to the owner and applicable incidents, accidents and traffic citations. When a modification is made to the vehicle record, the system must preserve previous data from all fields in a history record. The system must provide the ability to link digital images to the vehicle record. The solution must show clearly why the vehicle is in the system: for example, stolen/not recovered, stolen/recovered, evidence, abandoned, impounded, involved in an accident, driven by criminal suspect, etc. The solution must provide for generation of reports of vehicle information, such as UCR and local status analysis and an audit report to identify possible duplicate vehicle records. The solution should provide an Invalid VIN Report listing of all vehicles added or modified during a specified date range with the VIN Check Digits. If VIN Reporting capability is not offered as part of your solution, an interface is required to allow the same functionality via OEM software (i.e. VIN Assist). Vehicle information should be linked to DMV file information, towing reports, incident reports, and other appropriate reports. The solution should be capable of associating image files with any vehicle. The solution should be capable of associating image files of the parcel and / or structure with any address information. Property Information should have all the fields contained within the Hoover Police Department property receipt form included in (Appendix M). The solution should be capable of associating image files to any property record.

5.2.21 5.2.22 5.2.23 5.2.24 5.2.25

5.2.26

5.2.27

5.2.28

5.2.29 5.2.30 5.2.31 5.2.32

5.2.33

Page 29 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

5.3

5.3.1

Integration with CAD

When the responding officer requests a case number, the solution should assign a unique case number based on the agency's numbering scheme. Case number assignment should come through an interface with the agency's RMS, which will provide the next number in the sequential Case Number assignment scheme. (NOTE: It is unimportant which system actually creates the case number as long as all systems recognize and utilize the numbering scheme in the same manner.) When the Case Number is requested, the CAD should automatically create a shell record within the RMS, attached to that Case Number, to preserve the original CAD information in the permanent record and queue Records personnel that a report should be forthcoming. The CAD system should automatically check for and be able to display "alert" data based on a name or address search of the RMS for hazardous materials, BOLO, warrants, missing persons, medical alerts, vacant houses, residential and business alarm information, weapons permits, Orders of Protection / Restraining Orders, house arrest or confinement, etc Any search initiated in CAD should automatically and seamlessly be performed on the RMS as one of the sources searched.

5.3.2

5.3.3

5.3.4

5.3.5

5.4 Training

5.4.1 Training is required as part of the solution. Do you provide formal classroom training? Include a description of your offerings in APPENDIX J.

6

6.1

6.1.1 6.1.2

Events / Reports

Incident and Supplemental Reporting

A unique case number should identify each reported incident and should be shared with the CAD system. The solution should allow for the addition of supplemental information and reports, which are linked to the original incident by the case number.

6.1.3

Data entered for each incident and / or supplemental should include the listed fields in the Hoover Police Department

Page 30 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

Incident/Offense Report and Incident/ Offense Supplemental Report. (See Appendix K)

6.1.4 6.1.5 6.1.6 6.1.7 6.1.8 The solution should allow for the entry of unlimited narrative text for each incident and / or supplemental report. The solution should allow an officer to enter a partial report without loss of data. The solution should provide computer-assisted reporting such as on-line report writing guidance. The solution should provide spell-checking assistance for narrative entry. The solution should provide on-line assistance for determination of offense classifications to allow officers to enter the Uniform Crime Report (UCR) and / or National Incident Based Reporting System (NIBRS) offense codes for incidents. This should be linked to user defined tables so that any future modifications can be changed by the department The solution should allow for on-line review and approval of all reports. The solution should allow an officer to "flag" a report as complete to freeze existing data. The solution should allow a supervisor to append comments for information to reports returned for correction. The solution should provide messaging to notify an officer when a report has been returned for correction. Investigative reports, supplemental reports and other documentation completed after the original incident report should be handled in the same manner and appended to the original report through the unique case number assigned.

6.1.9 6.1.10 6.1.11 6.1.12 6.1.13

6.2

6.2.1

Field Interviews

Each filed interview should include: 6.2.1.1 Persons 6.2.1.2 Vehicles 6.2.1.3 Location 6.2.1.4 Date/time

Page 31 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

6.2.1.5 Narrative capability as would be applicable any incident or event report 6.2.2 6.2.3 6.2.4 6.2.5 The solution must provide for associating related persons, vehicles and property items with the field interview. The contact name, as with all names in the system, must become part of the master name table. If a vehicle is involved, the vehicle record must become a part of the master vehicle table. The solution must provide for generation of reports of field interview information, including field interviews by day and hour.

6.3

6.3.1

Arrest Reports

The solution should provide an automatic search for warrants, wanted or missing persons when the name of the arrested person is entered, which is to include NCIC/CJIS searches. Data entered for each arrest, in addition to all standard appropriate person identification information, should include at a minimum: 6.3.2.1 Date / Time of Arrest 6.3.2.2 Offense(s) 6.3.2.3 Property Involved 6.3.2.4 Arresting Officer 6.3.2.5 Text based narrative.

6.3.2

6.3.3 6.3.4

Charges should be validated through a comparison to a user defined table as they are entered into the system. The solution should not require personal or descriptive information to be re-entered when a prior arrest or other information exists, unless the information has changed. The solution should allow for modifications to personal and descriptive information when a prior arrest or other information exists, but the prior information should also be preserved as a "multiple" descriptive. The unique case number should link the arrest to an incident, if applicable. The solution should provide a link to digital mug shots of the person for each arrest

6.3.5

6.3.6 6.3.7

Page 32 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

6.3.8 6.3.9

The solution should provide a link to electronic fingerprints (i.e. LiveScan) of the person for each arrest. The solution should provide a link to medical evaluation and other information of the person, maintained within the Jail Management System (JMS), for each arrest. The solution should provide for linking of multiple arrests to one person. If arrests have been linked to two people, later determined to be the same person, the system should allow an authorized user to easily merge the data to one person without loss of data or re-entry of any information. When an arrest clears an outstanding warrant, the system should automatically clear the warrant when the arrest report is entered. When medical evaluations are required for a person arrested, the system should link that information and the results of that evaluation to the arrest report and the inmate medical information section of the JMS record. Automated interfaces, which enable automated importation of pertinent data fields without requiring duplicate data entry, should be maintained with all separate electronic information systems used for fingerprints, mug shots, and other arrest related information. The Hoover Police Department currently uses the Livescan Fingerprint System from Identix and also uses the Mugshot system from DataWorks.

6.3.10 6.3.11

6.3.12 6.3.13

6.3.14

6.4

6.4.1

Juvenile Custody Records

A higher level of security should be required to access Juvenile records. Only Juvenile Investigators and Supervisors of Juvenile Investigations shall have access to these files. All information requirements for adult arrests should apply to juvenile custody records with the addition of any juvenile custody specific information. See APPENDIX K ­ Arrest Report for required juvenile information. Confidential juvenile records MUST be maintained separately from adult records. When medical evaluations are required for a juvenile taken into custody, the solution should link that information and the results of that evaluation to the custody report and the JMS record.

6.4.2

6.4.3 6.4.4

Page 33 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

6.4.5 6.4.6

Juvenile records should indicate if a "pick up" or "commitment order" has been filed. The solution should track Orders of Protection issued in juvenile cases.

6.5

6.5.1 6.5.2 6.5.3 6.5.4 6.5.5

Evidence / Property

The solution should provide for the bar coding of evidence or property at the time of entry into the property room. The solution should allow entry of bar code information by keyboard or bar code reader. The solution should assign a unique evidence number for each item of evidence or property. The solution should provide for linking each item of evidence or property to the originating case number. The solution should enable the user to maintain a complete chain of custody for each item, including at a minimum the date/time of transaction, type of transaction, who transferred/received the item, reason for transfer, and where it was stored. The bar coding interface should support a hand held reader to enable the custodian to quickly inventory all applicable items on location. Evidence records should be linked to the related Incident record. As the charge classification is updated, appropriate fields pertaining to the status of evidence must be automatically updated. The solution must allow the status of multiple evidence records to be changed in a single transaction. A central property table must be provided to hold ALL property entered into the system. Information in the property table MUST be central to the system in order to eliminate duplicate entry of property information. Property information must be easily accessible from many other system tables, including use of alias names. The solution MUST provide the capability to link related records to the property record in such a way that the user can display a list of related records directly from the property record. The user MUST then be able to display a full record from that list. The solution MUST capture property information, including the following:

6.5.6 6.5.7

6.5.8 6.5.9 6.5.10

6.5.11

6.5.12

Page 34 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

6.5.12.1 6.5.12.2 6.5.12.3 6.5.12.4 6.5.12.5 6.5.12.6 6.5.12.7

Type Brand name and model Model year Serial number Owner-applied number Descriptive characteristics (rusted, dented, etc.) UCR code

6.5.12.7.1 Clothing 6.5.12.7.2 Consumable item 6.5.12.7.3 Firearms 6.5.12.8 Quantity with measurement units (gram, ounce, etc.) with normal measure conversions such as grams to ounces to pounds 6.5.12.8.1 Grams 6.5.12.8.2 Ounces 6.5.12.8.3 Pounds 6.5.12.9 Storage location and agency identification number

6.5.12.10 Status 6.5.12.11 Date received or recovered 6.5.12.12 Responsible agency and officer 6.5.12.13 Owner name 6.5.12.14 Address 6.5.12.15 Phone 6.5.12.16 Related Incident 6.5.13 The solution MUST provide for a custody record for each property item, showing a history of custody transfers for the item.

Page 35 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

6.5.14 6.5.15 6.5.16 6.5.17

The solution MUST provide the ability to easily duplicate a change-ofcustody entry for items under the same tag. The solution MUST accommodate UCR-mandated amount recovered and accumulative amount recovered for each item. The owner name, as with all names in the system, MUST become part of the central name table. The solution MUST allow the user to search for property with various criteria, such as, but not limited to: 6.5.17.1 6.5.17.2 6.5.17.3 6.5.17.4 6.5.17.5 6.5.17.6 Item type Serial number Brand Model Evidence identification number Owner name

6.5.18

The solution must show clearly why the property item is in the system: 6.5.18.1 6.5.18.2 6.5.18.3 6.5.18.4 6.5.18.5 Stolen Recovered Lost Found Evidence.

6.5.19

The solution MUST provide the ability to code the item type so that all item types are entered in the same manner, to facilitate inquiries and reporting. The solution MUST provide features to help the agency avoid duplicate entry of information for the same property item. When a modification is made to the property record, the system MUST preserve previous data from all fields in a history record. The solution MUST provide for generation of pre-formatted reports of property information, including a summary of property released.

6.5.20 6.5.21 6.5.22

Page 36 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

6.5.23 6.5.24 6.5.25 6.5.26 6.5.27 6.5.28 6.5.29

The solution should allow for linking of evidence or property information to specific icons / locations within an electronic crime scene diagram. The solution should allow for linking digital images and video of crime scene and evidence or property. The solution should provide for the ability to automatically assign a unique item number for each item entered on a property receipt. The solution should provide for electronic requests from submitting officer for evidence examination and lab test results. The solution should be able to generate a printed or electronic report of all evidence or property related to a specific case. The solution should be able to generate a printed or electronic report of all evidence or property / property related to a specific officer. The solution should be able to support identical functionality for arrestee / inmate property linked to the Jail Management System (JMS) or specific to the JMS. The solution should provide the capability to automatically flag a property as a: 6.5.30.1 6.5.30.2 Misdemeanor Felony

6.5.30

6.5.31

The solution should provide the capability to set expiration schedules based on the type of evidence/property placed in inventory.

6.6

6.6.1

Local Warrants

The solution should be capable of storing all information on a warrant, including but not limited to: 6.6.1.1 6.6.1.2 6.6.1.3 6.6.1.4 6.6.1.5 6.6.1.6 Defendant name and identifying information, Victim name and identifying information, Witness names and identifying information, Date and time of offense, Offense charged, offense charged classification (i.e. felony, misdemeanor), Bonding information if any,

Page 37 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

6.6.1.7 6.6.1.8 6.6.1.9 6.6.1.10 6.6.1.11 6.6.1.12 6.6.1.13 6.6.1.14 6.6.1.15

Sentencing information if appropriate, Status (e.g. active, served, cleared, etc.), Issuing authority Court Number Docket Number Type of Warrant Disposition of Warrant Assigned Officer and Agency Date Issued

6.6.1.15.1 Received 6.6.1.15.2 Served 6.6.1.15.3 Returned 6.6.2 When the user accesses a name record, the solution MUST automatically determine if there is an active warrant (Disposition of warrant is active) for that person. If there is an active warrant, the solution must cause a visual alert to appear throughout the system beside the person's name, describing the nature of the warrant. The solution MUST be capable of displaying the alert on the original name record and on any associated alias name record. 6.6.3.1 Served 6.6.3.2 Active 6.6.3.3 Closed 6.6.4 6.6.5 6.6.6 6.6.7 The solution must allow the wording of the warrant display flag to be defined by the user. The solution must allow the user to change the disposition of the warrant when it is served, subject to security clearance. The solution must allow for logging of multiple service attempts for a warrant. The solution must allow for unlimited active warrants on a person.

6.6.3

Page 38 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

6.6.8 6.6.9 6.6.10

The solution must allow for multiple offenses per warrant. As with all names in the system, the wanted person's name MUST become part of the central name table. The solution must provide for generation of pre-formatted reports of wanted person information, including reports on process expiration and summary of criminal processes served. The solution should provide for a search for outstanding warrants by: 6.6.11.1 6.6.11.2 6.6.11.3 6.6.11.4 6.6.11.5 6.6.11.6 6.6.11.7 6.6.11.8 6.6.11.9 Defendants Name Victim Name Case Number Warrant Number Charge Warrants by Specific Date Defendant Location Information Officer Assigned Issuing Authority.

6.6.11

6.6.12

The solution should allow for tracking of each service attempt, to include at a minimum: date and time of attempt, officer involved, and status of service. A free form remarks field should be included in the tracking element to allow for general comments with each service attempt. A unique number should identify each warrant. The solution should link a warrant to an incident by case number. The related affidavit should be linked to the warrant. The case number should be displayed with warrant number on all screens. The solution should provide the status of the warrant from a user defined table. The solution should provide reporting capabilities for statistical data on warrants received, pending, served, cleared, and by process type.

6.6.13 6.6.14 6.6.15 6.6.16 6.6.17 6.6.18

Page 39 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

6.6.19

The solution should be capable of providing time information based on user ­ defined limits for warrants reviews

6.7

6.7.1

Training

Training is required as part of the solution. Do you provide formal classroom training? Include a description of your offerings in APPENDIX J.

7

7.1

7.1.1

Specialty Records and Reports

Racial Profiling

The solution must provide the ability to record information concerning the race and ethnicity of persons involved with routine traffic stops and any other law enforcement activities. The solution must provide the ability to automatically create a Racial Profiling record for each traffic stop.

7.1.2

7.2

7.2.1

Crime Scene Reporting

The solution should provide electronic crime scene diagramming capability, with the ability to link the diagram to the appropriate case number. The solution should provide the capability to merge GPS information into specific crime scene diagrams to enable accurate, scale placement of evidence or property located within a crime scene. The solution should provide electronic Standard Operating Procedures (SOP) and check lists for major crime scenes enabling the investigating officer to follow the check list. The solution should provide automation of all crime scene investigation documentation, prompting to include evidence or property handling and logging capabilities.

7.2.2

7.2.3

7.2.4

7.3

7.3.1 7.3.2

Traffic Accidents

A unique identifier should be assigned to each traffic accident. Data that should be recorded for a traffic accident includes, at a minimum, persons, accident location, vehicles, offenses, injuries, and officer(s) investigating.

Page 40 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

7.3.3 7.3.4 7.3.5 7.3.6 7.3.7

The solution should provide for GPS information for accident location to ensure appropriate tracking and diagramming of accidents. The solution should provide electronic accident diagramming capability. The solution should allow for on-line review and approval of accident reports. The solution should allow for sale and acquisition of accident reports from a secured City of Hoover Website via the internet. The solution should provide the capability to link citation / arrest information to accident reports as appropriate.

7.4

7.4.1 7.4.2

Driving While Intoxicated Arrests / Charges

A unique identifier should be assigned to each DUI arrest or charge. Data included for DWI arrests / charges, in addition to general arrest information, should include, at a minimum, sobriety test results, breathalyzer test results and blood alcohol test results as appropriate.

7.5

7.5.1 7.5.2 7.5.3

Complaints

Each complaint should be assigned a unique number by the system. The solution should allow linking of complaints to a case number, if applicable. The solution should allow importation of important information (e.g. dates, names, locations, charges, narrative passages etc.), directly from the incident, arrest, supplemental or other information associated with the case number, person, location(s) or property as appropriate. The solution should allow the complaint to be stored as a document. The solution should allow the electronic transfer of a copy of the complaint directly to appropriate court of jurisdiction for incorporation into the warrant. The solution should automatically link unique numbers assigned to complaints or subsequent warrants to the original case number of the incident report. The related complaint should be linked to the search and arrest warrants.

7.5.4 7.5.5

7.5.6

7.5.7

Page 41 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

7.5.8

The solution should provide for printing complaints in an appropriate format, acceptable to the court of jurisdiction, for the type of affidavit.

7.6

7.6.1 7.6.2 7.6.3 7.6.4 7.6.5 7.6.6 7.6.7 7.6.8

Search Warrant Process

A unique number should identify each search warrant. The related affidavit should be linked to the search warrant. The solution should link a search warrant to an incident by case number. The case number should be displayed with the search warrant number on all screens. The solution should provide the status of the search warrant. The solution should provide for the property seized list to be associated to the warrant number and retained for historical purposes. The solution should provide for electronic completion and submission of the proof of service and return for a search warrant. The solution should provide for printing search warrant returns in an appropriate format, acceptable to the court of jurisdiction.

7.7

7.7.1

Court Order Management

The solution should provide for recording and tracking of restraining orders, orders of protection, recalled orders of protection, custody orders, and other orders of the courts as appropriate. Information associated to each court order should include origination date, expiration date, status, complainant, and defendant. The solution should support: 7.7.3.1 Federal 7.7.3.2 State laws 7.7.3.3 Local ordinances 7.7.3.4 Agency's policy for expunging records and orders including: 7.7.3.4.1 7.7.3.4.2 Elimination of mug shots Elimination of fingerprints

7.7.2 7.7.3

Page 42 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

7.7.4 7.7.5

The solution should support the ability to pull digital images from the record. The solution should support the agency's policy for providing and tracking trespass notifications.

7.8

7.8.1 7.8.2 7.8.3 7.8.4 7.8.5 7.8.6 7.8.7 7.8.8 7.8.9 7.8.10

Confidential Investigative Activities

Investigators should have real time query access to all field interview, incident, supplemental, arrest, traffic and parking data. The solution should require a higher level of security to gain access to investigative activities and information. The solution should provide the capability to enter events, persons, or places under investigation. The solution should provide automatic cross-referencing and notification of common events, persons, or places being investigated. Investigators who have been granted access privilege should be able to search for names or places under investigation. The solution should provide the capability to link persons with associates and/or gang members. Known criminal associates should be linked and "flagged". Investigators should be able to maintain confidential informant data to include all identifying information in a secure and restricted environment. The solution should allow for storing informant history, to include reliability, contacts, criminal history, and other pertinent data. The solution should allow for tracking and accounting of confidential funds and other payments to informants as appropriate to comply with federal and state laws, local ordinances and agency policies. The capability should exist to track and generate time line event reports of investigative activities.

7.8.11

7.9

7.9.1

Case Management

The Case Management module must include a case management feature to track all cases assigned to a specific detective(s), from initial incident through completion of the investigation. Case management information must be linked to the incident record.

7.9.2

Page 43 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

7.9.3

Information on victims, suspects, other persons, vehicles and property involved with the incident must be linked to the incident and accessible for case investigative purposes. The solution must provide the ability to automatically assign cases to persons and details based on agency-defined offense codes and solvability factors, and notify the supervisors and individuals when cases are assigned. The solution must retain a history of changes in status for each case being investigated. The case management record must accommodate a long investigation narrative, of virtually unlimited length, within disk storage boundaries. The case management record must provide the ability to record all case file activity, including the amount of time spent on each activity. The solution must produce a list of cases pending or past due. The solution must provide for automatic notification through electronic email for personnel assigned to cases. The solution must enable the user to secure case management records using partitioning or password protection. The solution should provide the capability for assessing solvability factors, as determined by agency policy, for all cases forwarded to investigative supervisors for assignment. To the extent possible, assessing solvability factors should be automated based on information entered into specific fields of the incident report, and should provide non-binding recommendations to the supervisor. The solution should provide recommendations to the supervisors based upon investigator caseload and investigation complexity factors developed by the agency. The solution should provide detailed case status tracking that includes, at a minimum, case number, status, investigator(s) assigned, date assigned, date(s) reviewed, and date closed / cleared. The solution should provide a link to allow closure of a case file only after the event of evidence / property release, destruction, etc. The solution should provide a chronological list of events associated to a case.

7.9.4

7.9.5 7.9.6 7.9.7 7.9.8 7.9.9 7.9.10 7.9.11

7.9.12

7.9.13

7.9.14

7.9.15 7.9.16

Page 44 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

7.10 Wanted / Dangerous / Missing Persons

7.10.1 7.10.2 The solution should allow a user to "flag" a person that is either wanted or missing. If wanted, the system should display the circumstances (e.g. contact investigations for questioning; outstanding warrant; material witness; etc.). The solution should allow a user to "flag" a person as dangerous based on criteria established by the agency. The solution should allow definition of the reasons a person is considered dangerous and should display that definition anytime the "flag" is displayed. The solution should display the wanted, missing or dangerous flag when a search is requested for that name.

7.10.3 7.10.4

7.10.5

7.11 Towed Vehicles

7.11.1 7.11.2 Information on towed vehicles should be automatically imported from the CAD as appropriate. Information on towed vehicles should be entered into the system or imported form DMV files including, at a minimum: 7.11.2.1 7.11.2.2 7.11.2.3 7.11.2.4 7.11.2.5 7.11.2.6 7.11.2.7 7.11.2.8 7.11.2.9 Color Make License Number VIN Location of pickup Officer ordering the tow Storage location Owner name Driver name (if appropriate)

7.11.2.10 Reason for tow 7.11.3 Color and make should be validated before being saved in the database.

Page 45 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

7.11.4 7.11.5

The solution should allow for ad-hoc searches of any combination of towed vehicle data elements. The solution should provide the capability to link a towed vehicle with a case number.

7.12 Traffic Violations

7.12.1 The solution should provide the capability to perform searches on local, state and NCIC databases by vehicle or by person for BOLO (Be On the Look Out), warrant, and delinquent fine information with a single inquiry. Data recorded for moving violations should include, at a minimum: offender identification, operator license number, vehicle information, vehicle ownership, offense location, offense, arresting officer, date, time and place court appearance and bond amount as appropriate. The solution should provide an interface to the Court Management System (CMS) that provides automatic exportation of the citation information into the CMS. The solution should be capable of generating statistical reports to assist local traffic departments in determining need for road upgrades, traffic lights, speed limit revisions, traffic enforcement efforts, etc. The solution should provide search capabilities by name, operator license number, vehicle license number, VIN, vehicle owner, location, issuing officer or other searches designated by the agency.

7.12.2

7.12.3

7.12.4

7.12.5

7.13 Parking Citations

7.13.1 All functionality associated with traffic citations should be applied to Parking Citations.

7.14 Pawnshop Support

7.14.1 The solution should provide a method to capture pawnshop transactions.

7.15 General Reporting Features

7.15.1 The solution must provide for creation of UCR (Uniform Crime Report) consistent with federal and/or State requirements. The UCR program must pull from information routinely entered through the application software and not require special data entry immediately prior to UCR generation. Programs for creating the following returns must be provided:

Page 46 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

7.15.2

Responder must provide Alabama state-specific UCR reports created and approved by the State of Alabama. Vendor solution must provide ability for reports to be submitted electronically (via both disk and email or any other electronic format approved by the State of Alabama.) The solution should provide ad-hoc query capability for incident analysis reporting or investigative searches. The solution should provide capabilities for trend and forecast analysis. The solution should provide the capability to search for words, or text strings in narratives. The solution should be capable of wildcard searches in any appropriate data field or within any narrative texts associated with records. The solution should be capable of providing combined and complete local, state and federal criminal history, wanted, warrants or missing person history by name and date of birth through a single request.

7.15.3 7.15.4 7.15.5 7.15.6 7.15.7

8

8.1

8.1.1

MAPPING

GIS Interfaces

Processing and display of geocoded coordinate-based information (e.g. x / y locations, polygon centroids, etc.) shall be an application feature of both CAD and RMS. All location information entered into either the CAD or RMS by any means must be processed through a geo-verification / geo-validation process. A single master address file must be used for address geo-validation for both CAD and RMS entries The solution should be capable of automated import of master address information from other sources, including but not limited to 911 subscriber list; business license list; etc. The CAD system, should integrate with GIS mapping, assisting dispatchers in providing directions to the incident and in identifying what exists at a given location. (e.g. Streets, highways, parking lots, rivers, and much more can be displayed.) The GIS system should support overlapping geographic coverage data to ensure verification of out-of-jurisdiction calls for service.

8.1.2

8.1.3 8.1.4

8.1.5

8.1.6

Page 47 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

8.1.7

If separate platforms are established for CAD and geographic displays, synchronization of unit location and unit status information should be a CAD/GIS/Mapping System application feature. CAD system should implement time synchronization, referenced to a national time standard. CAD system should be enhanced with a mapping subsystem that displays geographic and status information to the dispatcher. By viewing a map on the screen that shows current call location, pending calls, and active units, dispatchers can access incident information and identify which units should be dispatched to the scene. Mapping systems utilized should be compatible with one or more current GIS applications including but not limited to ArcView, ArcGIS, ArcInfo, MapInfo, Autodesk, etc. GIS systems should integrate graphical mapping tools and relation databases in which every entity on a map has attributes associated with it stored in the database. The operator should be able to query the information, or attributes, by simply pointing and clicking on graphical symbols on the map A user should be able to zoom, rotate, and pan the screen and find exact street addresses by clicking the mouse on a location on the map. The GIS system grid allocation should accept different location formats (e.g., latitude and longitude). GIS system should be capable of supporting GPS capabilities used for Automatic Vehicle Location (AVL) as required. If AVL is utilized, location information processed and transmitted back to a dispatch center should be accomplished by using available satellite, cellular, or other two-way wireless services. The solution should be capable of combining AVL data with the CAD mapping system to plot a vehicle's location on electronic maps. The solution should track and continue to update the unit's position and status on the map display. Maps used in the GIS must have a precision at least as fine as the GPS signal accuracy.

8.1.8 8.1.9 8.1.10

8.1.11

8.1.12

8.1.13 8.1.14 8.1.15 8.1.16 8.1.17

8.1.18 8.1.19 8.1.20

Page 48 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

8.1.21

The GIS system must be capable of supporting functions including, but not limited to, general and specific incident mapping and analysis functions common to manpower allocation, crime analysis, emergency evacuation procedures, critical incident response, etc. The GIS System should support the following map data: 8.1.22.1 8.1.22.2 8.1.22.3 8.1.22.4 8.1.22.5 8.1.22.6 8.1.22.7 Street Centerline Parcel Address Apartment Numbers Owners Names Occupants Name or Business Name Aerial Overlay Interstate Milepost Markers

8.1.22

8.1.23

The Geographic file MUST support and CAD recognize multiple districts and/or agencies, including: 8.1.23.1 8.1.23.2 Police District/Beats Fire and EMS station response areas

8.1.24 8.1.25 8.1.26 8.1.27

The solution MUST support the ability to turn on/off different map layers for showing beats, hydrants, apartments etc. The GIS System MUST have the ability to print the graphic maps to all city networked printers. The solution MUST make user-configurable the default map zoom levels of workstations. The solution MUST automatically verify the incident address from an agency-defined Geographical base of addresses in the jurisdiction(s) supported by the system. The solution MUST provide for automatic address verification against the Geographical base, using Soundex and alias searches when there is no exact match for the address entered. When entering a call address in CAD, the system MUST display the two cross streets nearest the address, and any special directions entered regarding the call address.

8.1.28

8.1.29

Page 49 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

8.1.30

The solution MUST provide address verification for invalid addresses, number ranges, street names, intersections, street aliases, mileposts, rural routes, and commonplace names. The solution MUST enable the user to define apartment/office buildings while allowing for invocation of the X, Y, and Z coordinates in much the same way as street segments, thus enabling the software to Geographical base specific apartments. The solution MUST enable a user to rename a street and retain the old name as an alias-street name. The solution MUST t allow for entry of a non- Geographical base address when necessary. Agency supervisors must later be able to bring up a list of all calls with addresses not valid in the Geographical base, and then make corrections to the address or Geographical base. The solution MUST accommodate the use of standard and uniformed address abbreviations. The Geographical base MUST accommodate the production of pin maps.

8.1.31

8.1.32 8.1.33

8.1.34 8.1.35

8.2

8.2.1

Training

Training is required as part of the solution. Do you provide formal classroom training? Include a description of your offerings in APPENDIX J.

Page 50 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

9

9.1

9.1.1

Jail Management

Jail Management System (JMS)

The solution should interface with all other systems in such a manner as to eliminate the need to enter information that has already been entered elsewhere. The solution should not require personal or descriptive information to be re-entered when a prior arrest exists, unless the information has changed such as address etc. The solution should allow for modifications to personal and descriptive information when a prior arrest exists, while the prior information should also be preserved as a "multiple" descriptive. When a mug shot already exists for a person being entered, that mug shot should be displayed to the user. The solution should provide electronic transfer of fingerprint, mug shot and warrant data to laptops and state and federal agencies as needed. The solution should provide the capability to print inmate identification bracelets that include both the unique bar code and the inmate's mug shot for identification and inmate tracking. The solution should allow for printing mug shot and / or fingerprints on demand. The solution should provide an interface to satisfy all requirements of state and federal laws, local ordinances and agency policies with regard to victim notification rights. The solution should interface to such peripheral programs as fingerprint (LiveScan) and mug shots (DataWorks) such that duplicate data entry of identifying information is eliminated. A unique number should link the inmate record to an arrest and / or incident within the RMS and CMS, if applicable. The solution should be capable of assigning a unique inmate bar code for each inmate incarcerated in the jail. The solution should provide the capability for the agency to create / modify medical screening information to comply with all applicable federal and state laws, local ordinances and agency policy. The solution must provide a user defined table to store these questions.

9.1.2

9.1.3

9.1.4 9.1.5 9.1.6

9.1.7 9.1.8

9.1.9

9.1.10 9.1.11 9.1.12

Page 51 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

9.1.13 9.1.14 9.1.15

The solution should provide the capability to track inmate movements and other accounts through use of the unique bar code assigned. The solution should be capable of storing historical medical screening information as appropriate. The solution should allow the tracking of any inmate medications (both over the counter and prescribed) to comply with all applicable federal and state laws, local ordinances and agency policy. Particular emphasis must be placed on requirements for tracking controlled substances. The solution should be capable of generating a number for the purpose of the tracking of an inmate's property in accordance with federal and state laws, local ordinances and agency policy. The solution should be capable of tracking inmate property either by use of a tracking number or a bar code reader. The solution should generate or store a report of the history of inmate property activities. The solution should be capable of tracking bond requirements and bond receipts as appropriate meet the requirements of federal and state laws, local ordinances and agency policy. An interface between the JMS and RMS should ensure timely sharing the following information for both functions. 9.1.20.1 9.1.20.2 9.1.20.3 9.1.20.4 Bonds Warrants Hearings Court Orders

9.1.16

9.1.17 9.1.18 9.1.19

9.1.20

9.1.21

The solution should be capable of printing an acceptable bond receipt on demand, and should automatically retrieve the appropriate information from the files created / entered by the user. The solution should be capable of accepting data entry of appropriate information for the various forms of paper bonds utilized and print the forms in appropriate format to comply with all federal and state laws, local ordinances and agency policy. Copies of bond and receipts should be automatically transmitted from the receiving system (JMS or CMS) to the other system.

9.1.22

9.1.23

Page 52 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

9.1.24

The solution should be capable of providing for cash accounting in a manners appropriate to comply with all federal and state laws, local ordinances and agency policy. The solution should provide the capability to perform spot audits as appropriate. The solution should be capable of providing authorized users with appropriate historical cash accounting and audit report documentation on demand. The solution should be capable of tracking bed space and usage. The solution should be capable of maintaining a historical record and producing appropriate reports. The solution should be capable of logging off a user after a predetermined time. This time should be user defined. The solution should be capable of easy, cost effective future expansion to include additional functionality as growth of the facility may require. The solution should provide the capability to track the following: 9.1.31.1 9.1.31.2 9.1.31.3 9.1.31.4 9.1.31.5 9.1.31.6 Commissary Functions Canteen Functions Food Service Functions Inmate Work Assignment Functions Visitations Telephones

9.1.25 9.1.26

9.1.27 9.1.28 9.1.29 9.1.30 9.1.31

9.2

9.2.1

Training

Training is required as part of the solution. Do you provide formal classroom training? Include a description of your offerings in APPENDIX J.

Page 53 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

10

10.1 10.1.1 10.1.2 10.1.3

CAD REQUIREMENTS

General Requirements: Handling Calls for Service and Other Events

The solution MUST support CAD Redundancy, by maintaining duplication of CAD on a separate system in a fail-safe configuration. The solution MUST provide the capability for authorized users to monitor dispatch screens without interference with CAD operations. The solution MUST support an MDC (Mobile Data Computer) Interface. This interface should allow MDC units to communicate with dispatch. The interface should also support unit status changes and inquiry into local and state/NCIC information. The solution should allow for customization of all Call Taker and Dispatch screens, as well as the Call Status screen by the system administrator. (The system administrator is assumed to have no programming background.) The agency can receive calls of multiple types, such as assault cases requiring both law enforcement and emergency medical personnel. The solution MUST handle these types of calls, generating multiple full incident reports as well as multiple active calls for dispatching, allowing police/EMS/fire units to be dispatched and tracked separately for the same call. All incidents generated from a single call MUST be crossreferenced. The software should provide for definable function keys, to be created and maintained by the system administrator. The software MUST allow the supervisor to assume any Call Taker position on demand at the supervisor's terminal.

10.1.4

10.1.5

10.1.6 10.1.7

10.1.8 The software MUST support a Medical Priorities Interface. This interface should track the results of the medical questions within the CAD incident. 10.1.9 Based upon call priority and/or user direction, the solution MUST allow dispatchers to view, dispatch and perform other required dispatch functions for a call while the call taker continues to obtain and enter additional information. Updated information should refresh the dispatch screen as appropriate. The solution MUST provide a real-time status display for dispatchers showing unit status, active and pending calls.

10.1.10

Page 54 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

10.1.11 10.1.12

The solution MUST provide the ability for only the supervisor to permanently change and save dispatcher's personal configuration. The solution should enable the supervisor to customize the CAD Status Screen and save the settings as a default personal configuration for each dispatcher. At a minimum, the solution should enable the supervisor to configure the CAD Status Screen windows as follows: 10.1.13.1 Size and position of the windows 10.1.13.2 Text size 10.1.13.3 Colors 10.1.13.4 Add or remove fields from the windows 10.1.13.5 Resize fields 10.1.13.6 Sort Configuration

10.1.13

10.1.14 10.1.15

The solution MUST differentiate between dispatched and pending calls. In the status screen, the solution must enable the user to determine which status column will control the sort order of the calls, and allow the sort order to be changed dynamically. The solution MUST recommend units for dispatch using at least the following sort values: 10.1.16.1 Agency of unit 10.1.16.2 Kind of unit 10.1.16.3 Station of unit 10.1.16.4 Zone of unit 10.1.16.5 Proximity of unit to call 10.1.16.6 Time since last status change

10.1.16

10.1.17 10.1.18

The dispatcher MUST be able to override solution recommendations as necessary. To increase recommended unit flexibility, the solution MUST enable the user to assign primary and secondary uses to a specific unit.

Page 55 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

10.1.19

The solution should provide a way of defining recommended unit plans including: 10.1.19.1 Day and time of day plan is valid 10.1.19.2 Type of unit 10.1.19.3 Unit station 10.1.19.4 Minimum number of units to recommend 10.1.19.5 Special equipment 10.1.19.6 Minimum number of officers to recommend

10.1.20 10.1.21 10.1.22

The solution should provide the ability to assign units to shifts and to dispatch entire shifts if needed. The dispatcher and/or operations supervisor should also be able to update shift assignments quickly. The dispatcher MUST be able to quickly perform inquiries into names or name descriptions, vehicle license plates, past incidents, and into other tables, and perform wanted person checks, from the dispatcher's screen. Results of such queries should automatically become part of the dispatch record. The solution MUST provide the ability to modify calls either from the calltaker's screen or from the dispatch status screen. A dispatcher viewing the call must be able to view the most recent changes to the call. The solution MUST provide for status updates, such as unit arrival onscene and completion of call, of both the call and all responding units. The solution must time-stamp each status update. The solution MUST provide for rapid dispatch of units, with automatic logging of the dispatch times in the Radio Log. These radio log time stamps must be associated with the subsequent full incident report. The solution MUST enable the user to have multiple windows open at once and be able to shift dynamically between these windows. The solution MUST provide the ability to preset timers, coded to the nature of call, for unit dispatch, unit arrival on-scene and call completion. The dispatcher must be visually alerted if a timer expires. Any entry of status change should reset the alarm. Dispatchers should also be able to over ride or alter timers for a specific call, specific call type, or unit.

10.1.23

10.1.24

10.1.25

10.1.26 10.1.27

Page 56 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

10.1.28

The solution MUST provide the ability to easily access call information. Call information displayed must reflect any changes made to the call since initial call entry. The solution MUST alert the user when a name entered or displayed is a wanted person by automatically searching NCIC and local data bases. The solution MUST alert the user if the name entered in the Complainant field of a call record is an alias name. The user MUST be able to inquire into the vehicle records directly from the dispatch solution using descriptive information. License plate queries must be accomplished as a simple command, not requiring full display of the vehicle screen. The solution MUST support an alarm interface. This interface should provide the ability to create an incident/call based upon an alarm registration, and provide the ability to bill for false alarms. The solution MUST provide a user defined table of alarm information such as address, type, contact name/phone, complainant, and call priority. This information should be importable from a municipal business licensee, alarm permit or other pertinent file as directed by the agency. To streamline alarm entry, when an alarm is activated, the solution will allow the dispatcher to enter the alarm number or address of the alarm and the solution must automatically enter this predefined information in the call for service record. The solution MUST provide for a display of agency special instructions and policies linked to specific types/natures of call (e.g., pre arrival instructions for EMS calls). The solution must automatically alert the call-taker when special instructions exist for a call, on the status screen. In addition, the dispatcher must be able to display (and print) these instructions at any time. The solution MUST provide user defined tables for recall of telephone lists, fire department rosters, milepost logs and the like. These lists must be displayed with a simple command and easily updated. The solution MUST provide a method to find employees with a particular skill needed for an incident. The solution MUST allow a closed CAD call to be re-opened, record who reopened the call and the time/date it was reopened The solution will enable the user to open one or more call types associated with the reopened call.

10.1.29 10.1.30 10.1.31

10.1.32

10.1.33

10.1.34

10.1.35

10.1.36 10.1.37

Page 57 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

10.1.38 10.1.39

The solution MUST provide online help for all CAD commands simply by typing help followed by the command in question. The solution MUST be fully graphic user interfaced (GUI) in all operations on the client's side as well as having the option to use the command line entry from within the GUI interface. The solution MUST be able to process multiple dispatch configurations, single agency, single jurisdiction with multiple agencies (e.g. Fire, EMS), or multiple jurisdictions with multiple agencies. The solution MUST have the option to automatically route the event to the Telecommunicator responsible for the location and/or call type entered. All functionality of the solution applicable to use for a single agency configuration MUST function in precisely the same manner when applied to use for multiple agencies and / or jurisdictions. The solution should support multiple dispatch configurations to include, but not limited to, standard dispatch as well as call-taker dispatch configurations. The solution should be able to create an event record when a call comes into the agency. If the call is received on 911, the solution MUST automatically insert Automatic Number Identification and Automatic Location Identification (ANI / ALI) information into the event record. ANI / ALI MUST display all information provided by the telephone company. ANI / ALI information MUST include zone service providers for Fire, Emergency Medical Service (EMS), and Police. If the call is received on administrative lines, caller identification information MUST automatically be inserted into the event records on demand. The Telecommunicator, at any point in the process, MUST be able to verify and correct, if necessary, the caller name, phone number, and address captured by E911 or Administrative Caller ID, while preserving the previously captured information. The solution MUST include a geographic file for address verification and event mapping. This feature MUST be shared by all modules from a single address verification file.

10.1.40

10.1.41

10.1.42

10.1.43

10.1.44 10.1.45

10.1.46 10.1.47 10.1.48

10.1.49

10.1.50

Page 58 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

10.1.51

The solution MUST include a geographic file override capability to allow the user to force an address into the system that does not match the geo-code.

10.1.52 Geographic overrides should be provided in a report. 10.1.53 Data included for an event record should include, at a minimum:

10.1.53.1 Event Type 10.1.53.2 Event Priority 10.1.53.3 Event Address Including 10.1.53.4 Street 10.1.53.5 Building 10.1.53.6 Apartment or Lot Number 10.1.53.7 Police Beat 10.1.53.8 Indication of Premise Alerts 10.1.53.9 Indication of Premise History 10.1.53.10 Alias 10.1.53.11 Commonplace Names 10.1.53.12 Caller's Name 10.1.53.13 Address 10.1.53.14 Phone Number 10.1.53.15 Call Back Number 10.1.53.16 Case Number 10.1.53.17 CAD Event Number 10.1.53.18 Units Assigned 10.1.53.19 High and Low Cross Streets

This field should be optionally omitted by the dispatcher if the caller wants to remain anonymous. This field should be optionally omitted by the dispatcher if the caller wants to remain anonymous. This field should be optionally omitted by the dispatcher if the caller wants to remain anonymous.

Page 59 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

10.1.53.20 Call Taker who entered the event 10.1.53.21 Dispatcher Notes 10.1.53.22 Call Disposition 10.1.53.23 Secondary Locations 10.1.53.24 Suspect Vehicle Information 10.1.53.25 Victim Vehicle Information 10.1.54 10.1.55 The solution should provide the capability to select event type from a list and automatically insert the selection into the field. The solution MUST provide for automatic capture of time of call, time of dispatch, time of arrival, and time of departure and / or other configurable method of times to be collected. Incoming calls MUST be automatically prioritized for dispatch based on the user defined tables and agency policy. The solution MUST also have manual override capability. User defined tables MUST be used for call types, priority codes, and any other appropriate field within the system. (e.g. call response scenario (pre-determined fire run recommendations) etc) Each event record MUST be logged based on a unique system-assigned event number based on agency and / or jurisdiction. The solution MUST provide or allow for the entry of sets of questions that provide the Telecommunicator with online questions to ask the caller. These questions must be incident based. For pre-arrival medical questions the solution MUST provide for the use of third party software such as "Lighthouse" or "Pro QA. If used, the responses to these sets of questions MUST automatically be incorporated into the event information record. If an event is entered which is later determined to be a duplicate of another event, the Telecommunicator should be able to cancel the duplicate event and have that information permanently incorporated (merged) into the primary event. The Telecommunicator MUST be able to interrupt and suspend any event that is being entered in order to service an event that has a higher urgency.

10.1.56

10.1.57

10.1.58 10.1.59

10.1.60 10.1.61

10.1.62

Page 60 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

10.1.63 10.1.64 10.1.65

Event records MUST NOT be required to have a corresponding case number. The dispatch Telecommunicator should be able to select current calls for service by priority, time or specific call type, at a minimum The solution MUST clearly indicate an in-progress call for service. If there is a criminal act in progress it should be clearly indicated on the CAD screen The dispatch Telecommunicator MUST be able to suspend one call for service to take another of higher priority. The dispatch Telecommunicator MUST be able to override the priority level set by the system. The dispatch Telecommunicator MUST have the ability to queue calls for service. The dispatch Telecommunicator MUST be able to supplement, modify, and / or cancel events after entry into the CAD system. An automated search MUST be performed when the following information is entered into designated entry fields: 10.1.70.1 Names 10.1.70.2 Addresses 10.1.70.3 Driver's licenses 10.1.70.4 Vehicle licenses

10.1.66 10.1.67 10.1.68 10.1.69 10.1.70

10.1.71

The system MUST provide the capability to associate "alert" data to a name or an address for hazardous materials, BOLO, warrants, missing persons, medical alerts, vacant houses, residential and business alarm information, weapons permits, Orders of Protection / Restraining Orders, house arrest or confinement, etc. The solution MUST allow for multiple "alert" records to be entered for a single person or location. The solution MUST allow the dispatcher to automatically check for and be able to display "alert" data based on a name or address search of the RMS or other pertinent databases for: 10.1.73.1 Hazardous Materials 10.1.73.2 BOLO

10.1.72 10.1.73

Page 61 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

10.1.73.3 Warrants 10.1.73.4 Missing Persons 10.1.73.5 Medical Alerts 10.1.73.6 Hospice 10.1.73.7 Patrol Requests 10.1.73.8 Vacant Houses 10.1.73.9 Residential and Business Alarm Information 10.1.73.10 Weapons Permits 10.1.73.11 Orders of Protection / Restraining Orders 10.1.73.12 House Arrest or Confinement, etc. 10.1.74 When the responding officer requests a case number, the solution MUST assign a unique case number based on the agency's numbering scheme. Case number assignment MUST come through an interface with the agency's RMS, which will provide the next number in the sequential Case Number assignment scheme. (NOTE: It is unimportant which system actually creates the case number as long as all systems recognize and utilize the numbering scheme in the same manner.) When the Case Number is requested, the CAD MUST automatically create a shell record within the RMS, attached to that Case Number, to preserve the original CAD information in the permanent record and queue Records personnel that a report should be forthcoming. The system MUST include a working mapping solution. This interface MUST provide the ability to plot incidents/calls and units on a street map. The plotting of the incident/unit information should be a by-product of normal dispatch. The dispatcher should be able to control the map from CAD, allowing Zoom, Pan and Layer control. Any mapping solution MUST include "Phase Two" compliance for mapping cell phone calls. the assistance of the Telecommunicators. These capabilities are to include but not limited to:

10.1.75

10.1.76

10.1.77

10.1.78

10.1.79 The Solution MUST provide automated GIS and mapping capabilities for

Page 62 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

10.1.79.1 Street Centerline Maps 10.1.79.2 Current Hoover Police Beat Structure 10.1.79.3 Hoover Fire Station Coverage 10.1.79.4 Police and Fire Jurisdictional Areas 10.1.79.5 Business Districts 10.1.79.6 Apartment Complexes 10.1.79.7 Schools 10.1.79.8 Fire Hydrant Locations 10.1.79.9 Parcels 10.1.79.10 Interstate Mile Markers 10.1.79.11 Imagery Overlay 10.1.79.12 Sex Offender Tracking 10.1.80 10.1.81 The solution MUST identify nearest cross streets, streets on either side of an address, and the jurisdiction. The solution MUST be capable of displaying a map of events associated to a name, address or within a user defined area within a defined period of time, based upon calls for service or event history. The solution MUST be capable of displaying geographical zone maps indicating call-for-service locations and identifying police, fire and EMS units assigned to the calls or their reported locations, distinguishing unit status as defined by user. The solution should be able to provide location status for on-duty personnel. The solution should support to-do lists for officer tasks such as address checks, and should provide automatic time stamping when the officer indicates the task is performed. The solution MUST provide alerts for officers on duty who have not checked-in with-in a user defined time period. The solution MUST allow for the entry of calls that have been previously handled but not yet entered into the system, due to conditions such as system unavailability or other qualifying circumstances, In case of any

10.1.82

10.1.83 10.1.84

10.1.85 10.1.86

Page 63 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

type failure of the CAD, the solution MUST provide the ability to go back and enter calls that have been previously hand written. The user MUST be able to insert these in chronological order.

10.2 Towed Vehicle Module

10.2.1 10.2.2 The solution should allow for special requests of specific wrecker services in accordance with agency policies. Information on towed vehicles should be entered into the system or imported form DMV files including, at a minimum: Color, make, license number, VIN, owner name, location of pickup, officer ordering the tow, reason for the tow, towing company name, storage location, and vehicle driver name (if appropriate). The solution should allow for ad-hoc searches of any combination of towed vehicle data elements. The solution should provide the capability to link a towed vehicle with a case number. Information on towed vehicles should be automatically exported from the CAD /MDS to the RMS and automatically transferred to the Hoover Police Department Tow In Form (See Appendix K).

10.2.3 10.2.4

10.2.5

10.3 Dispatch Interfaces

10.3.1 The solution should provide automated interfaces to other sources of information such as but not limited to: 10.3.1.1 10.3.1.2 10.3.1.3 10.3.1.4 10.3.1.5 10.3.1.6 10.3.1.7 10.3.1.8 10.3.1.9 National Crime Information Center (NCIC) State Criminal Justice Information Systems (CJIS) State Motor Vehicle Registration Files Agency Records Management System (RMS) Agency Jail Management System (JMS) Municipality Court Management System (CMS) Municipality Business License Information Systems Fire Information Management System Other agencies and data bases as needed

Page 64 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

10.3.2

The solution should provide combined and complete local, state, and federal queries by name and date of birth, any identification number (e.g. driver's license; FBI; State ID number, social security, etc) or any combination of fields selected, through a single request. This automated query should be sent only if the dispatcher has entered required fields and the dispatcher's NCIC certification is confirmed. The solution should provide a detailed audit trail of all events and activities, additions, changes, deletions, etc. The solution should provide an audit trail of queries to the state and federal level sufficient to meet all NCIC 2000 requirements. 10.3.4.1 10.3.4.2 (See APPENDIX O for NCIC 2000 audit requirements) (See APPENDIX R for ACJIC audit requirements)

10.3.3 10.3.4

10.3.5

The solution should provide for a user-defined emergency phone number list and recall roster. This roster should be a derivative of the personnel file so that a change in the personnel file changes the roster. The solution should provide the ability to develop statistical reports necessary for department managers to assess resource allocations and requirements. The responder must state how this solution provides this ability and what types of management reports are standard.

10.3.6

10.4 CAD Messaging

10.4.1 The solution should provide online communications that allows telecommunicators to send messages from terminal to terminal, and, if mobile data communication is utilized, vehicle to vehicle or telecommunications to vehicle. If mobile data communication is utilized the system should provide messages to the vehicles with an audible and visual alert notification. If mobile data communication is utilized the system should provide the officer the capability of disabling the audible alert. If mobile data communication is utilized the system should provide an "alert" if information is sent to vehicles. The solution should provide the capability for the Telecommunicator to send a message to any other terminal on the system, including, but not limited to, supervisory terminal(s), JMS terminal(s), Investigations, command, etc.

10.4.2 10.4.3 10.4.4 10.4.5

Page 65 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

10.4.6

The solution should provide the capability for the sender to verify that a sent message has been acknowledged.

10.5 Paging Interface

10.5.1 The solution should allow for CAD users to send short messages (256 characters or less) to Fire and Police staff who have text pagers. 10.5.2 The solution should have an option for group paging 10.5.3 The CAD system shall have the ability to send event notifications to selected pagers. 10.5.4 The system Administrator MUST have the ability to designate which event types or alarm level will trigger an event notification and to whom.

10.5.5

The System Administrator MUST have the ability to pre-define pager groups and save them with a specific name.

10.6 Rip and Run Printing

10.6.1 The solution MUST have the ability for every Fire and/or EMS dispatch to transmit the call to a station printer where each dispatched unit is currently located. The rip and run record MUST have a user defined and maintained table to include but not limited to: 10.6.2.1 10.6.2.2 10.6.2.3 10.6.2.4 10.6.2.5 10.6.2.6 10.6.2.7 10.6.2.8 10.6.2.9 Event Number Event Address Street Alias or Commonplace Name Hazardous Materials Stored On Site Event Type/Nature High and Low Cross Streets Emergency Contact Dispatcher Notes Medical Notes

10.6.2

10.6.2.10 Primary Structure Use 10.6.2.11 Roof Type

Page 66 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

10.6.2.12 Standpipe Location

10.7 CAD Supervisor Requirements

10.7.1 The Supervisor position must have the capability of viewing/overriding any Call Taker or Dispatcher position including Unit, Message and Call Status Monitors. The solution should allow any Supervisor to enter / edit duty rosters anytime during a shift, with automatic update to the Telecommunicators from a supervisor terminal. The solution should allow any senior or supervising dispatcher from any terminal to enter, edit, and delete on-duty personnel assignments as appropriate. The Supervisor position MUST have the capability to maintain Single and Combined Incident Type call priority to maximize efficiency of Dispatchers. Any supervisory position should be able to display all pending incidents, or only those for one or more specific dispatch positions.

10.7.2

10.7.3

10.7.4

10.7.5

10.8 CAD Analysis Reports

10.8.1 10.8.2 10.8.3 10.8.4 10.8.5 10.8.6 10.8.7 10.8.8 10.8.9 10.8.10 The software should provide Area/Section Activity Reports and Detail Listings. The software should provide area activity summary reports. The software should provide Beat Listings. The software should provide Building/GEO Location Listings. The software should be able to provide a CAD Commands Listing. The software should be able to provide a Call Activity Report. The software should be able to provide a Call Breakdown by Month Report. The software should be able to provide a Call Breakdown by Priority and day of week Report. The software should be able to provide a Call Summary by Shift Report. The software should be able to provide a Call for Service Report.

Page 67 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

10.8.11 10.8.12 10.8.13 10.8.14 10.8.15 10.8.16 10.8.17 10.8.18 10.8.19 10.8.20 10.8.21 10.8.22 10.8.23 10.8.24 10.8.25 10.8.26 10.8.27 10.8.28 10.8.29 10.8.30

The software should be able to provide a Crime Summary by Shift Report. The software should be able to provide a Combined Incident/Call Types Listing. The software should be able to provide a Daily Incident/Call Log. The software should be able to provide a GEO Cross Street Listing. The software should be able to provide a GEO Master Listing. The software should be able to provide a GEO Verification Override Report by User. The software should be able to provide a GEO Verification Override Report by Venue. The software should be able to provide a Grid Activity (Summary and Ranking) Report. The software should be able to provide an Hour of Day Activity (Summary and Ranking) Report. The software should be able to provide a House Watch Listing. The software should be able to provide an Incident/Call Activity Report by Beat. The software should be able to provide Incident/Call Analysis Reports. The software should be able to provide Incident/Call Classification by Shift Reports. The software should be able to provide Incident/Call Detail Listings. The software should be able to provide Incident/Call Type Listings. The software should be able to provide a Personnel History Log. The software should be able to provide a Radio Log. The software should be able to provide a Response Time Analysis by Beat/Priority Report. The software should be able to provide a Run- Card Report The software should be able to provide a Shift Activity Summary Report.

Page 68 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

10.8.31 10.8.32

The software should be able to provide a Street Name Listing. The software should provide an activity report of dispatcher's call handling time to include definable by dispatcher, call type, or shift, but not limited to: 10.8.32.1 Call Start 10.8.32.2 Call Route 10.8.32.3 Call Dispatch 10.8.32.4 Call Completion

10.8.33

The solution MUST provide a report for the volume of CAD calls by user defined search criteria.

10.9 Remote CAD Functionality

10.9.1 The solution should provide secure remote access to a fully functional CAD system usable for remote dispatching.

10.9.2

The solution should be available via all of the following connectivity: 10.9.2.1 10.9.2.2 10.9.2.3 dial-up broadband wireless

10.10 Firehouse Interface

Firehouse provides a solution for imports to / from CAD. Do you provide an interface to this product? Additional information can be found at the Firehouse website located at http://www.firehousesoftware.com/ .

Page 69 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

10.11 Training

10.11.1 Training is required as part of the solution. Do you provide formal classroom training? Include a description of your offerings in APPENDIX J.

11

Mobile Data

11.1 Mobile Data System (MDS) Functions

11.1.1 The MDS should allow the officer to perform all the functions available to him / her from any workstation physically located at the office, in a remote capacity from a laptop or similar device. The software must allow for upload of officer reports to the Supervisor via RF, and PC file transfer. The software must support the use of dynamic IP addresses. The Field Reporting module must support the downloading of tables to all mobile devices, eliminating the need to update tables on individual devices. The MDS should provide the same operational functionality as described for each of the reporting events above. The MDS should provide the same operational scenarios for database queries, crime classifications and report approval cycle as described in the Incident and Supplemental reporting event. The MDS should have the capability to received silent dispatch messages whereby call-for-service information is visible to the responding officer. The solution should also have the ability to electronically speak the call to the officer. The solution should allow messaging to and from other mobile units, and to and from dispatch. The solution should provide "alert" messages when a search is performed on the local database, DMV, NCIC and / or from telecommunications. The solution should provide "hot keys" to enter when an officer arrives on duty, arrives / departs the scene of a call for service, incident or crime and the status / clearance of the incident.

11.1.2 11.1.3 11.1.4

11.1.5 11.1.6

11.1.7

11.1.8 11.1.9 11.1.10

11.1.11

Page 70 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

11.1.12 11.1.13 11.1.14

The solution should provide a "hot key" to indicate an officer is in trouble. The solution should allow access to the accident or crime scene diagramming application, which can then be linked to the RMS case. The solution should provide ESRI compliant maps for officers to locate addresses and determine jurisdiction.

11.2 Mobile Data Reporting

11.2.1 The solution should provide access to local databases for real-time entry of: 11.2.1.1 11.2.1.2 11.2.1.3 11.2.1.4 11.2.1.5 11.2.1.6 11.2.1.7 11.2.1.8 11.2.2 11.2.3 11.2.4 11.2.5 11.2.6 11.2.7 11.2.8 Incident Reports Accident Reports Supplemental Reports Field Interviews Traffic Stops Traffic citations Parking citations Towed Vehicle Report

The software must be UCR Part One Crimes Compliant The software must allow an officer to review the report for errors and warnings before submitting to a supervisor. The software must support Supervisor Review The software must allow for upload of officer reports to the Supervisor via diskette. The software must allow for upload of officer reports to the Supervisor via PCMCIA media. The software must support printing of a Field Report prior to being merged into the RMS database The software must allow a user to merge officer reports into an existing Records Management Database, eliminating duplicate entry and any rekeying of data.

Page 71 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

11.2.9 11.2.10 11.2.11 11.2.12 11.2.13

The software should support Password Protection by User. Software should allow an officer to save an incomplete report for completion at another time. Software must support narrative text entry with spell checker. The merge process should support merging one record at a time, allowing the merge administrator to make changes if necessary. The Field Reports should be capable of automatically populating the Fields in the RMS database during the merge process.

11.3 Message Switch Requirements

11.3.1 11.3.2 11.3.3 11.3.4 11.3.5 11.3.6 11.3.7 11.3.8 11.3.9 11.3.10 The Solution should provide support 3DES encryption. The Solution should provide multi-jurisdictional support. The Solution should provide emergency transmission support to all MDS's The Solution MUST provide support for NCIC 2000 standard protocols. The Solution should provide broadcast message capability based on MDS tables (teams, precinct, task force, srt, etc.) The Solution should provide message routing from any device connected to the Message Switch. The Solution should provide message acknowledgements to the sender. The Solution should support officer initiated calls and traffic stops-- sending info from the MDS to the CAD system. The Solution should support (Radio Frequencies) RF. The solution should provide private networks : 11.3.10.1 802.11b/g (wireless) 11.3.10.2 11.3.11 11.3.12 11.3.13 Wired Network

The Solution should support dynamic IP addresses. The Solution should provide function key update of unit status. The Solution should provide an audit trail of all database inquiries.

Page 72 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

11.3.14 11.3.15 11.3.16

The Solution should provide security that prevents unauthorized access to restricted databases on a user by user basis. The Solution should be able to provide statistical reports on communications line usage. The Solution should provide sign on/sign off capability from the MDS under security control which can also be controlled by the system administrator. The Solution should prevent users from signing on without authorization from the system administrator. The Solution should be able to control the number of sign-on attempts through the system administrator. The Solution should provide password security to limit access to specific transactions from any MDS. The Solution should provide the ability to place the MDS into "test" mode - allowing the message switch to ignore transmissions from that MDT. The Solution should allow CAR to CAR message routing. The Solution should provide emergency transmission capability to allow an officer to transmit an emergency message with the touch of one key to all MDS's. The Solution should provide the ability to hold messages for a period of time. If no response, the system should automatically alert the sender. The Solution should provide statistics of message volumes by message type, destination, MDS, etc. The Solution should maintain NCIC ORI numbers for each MDS to facilitate terminal to MDS messages. The Solution should provide message store-and-forward capability, with necessary queuing on an MDS basis for twenty-four hours. The Solution should provide daily statistics of message volumes by message type, destination, host communications statistics including: unsuccessful attempts received, message delivered, number of messages not delivered, and number of times the host link is down. The Solution should provide an audit trail of all device to device messages.

11.3.17 11.3.18 11.3.19 11.3.20 11.3.21 11.3.22

11.3.23 11.3.24 11.3.25 11.3.26 11.3.27

11.3.28

Page 73 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

11.3.29 11.3.30 11.3.31 11.3.32 11.3.33 11.3.34

The Solution should provide the ability to extract an MDS transaction report that can be selected by date and time of day. The Solution should provide the ability to extract statistical reports on usage for specific MDS's. The Solution software should support remote administration. The Solution should provide the capability to download new forms as they are created. The Solution should provide the capability for archiving, retrieval, tracking and user purge. The Solution should provide the capability to direct output to any printer attached to the Message Switch.

11.4 State NCIC Requirements

11.4.1 11.4.2 11.4.3 11.4.4 11.4.5 11.4.6 The Solution should provide message routing between MDS's and State/NCIC networks for inquiry purposes. The Solution should provide the capability for a single query to be directed to the State/NCIC, the local database or both. The Solution should provide the capability for auditing. The Solution should provide the capability for user-defined formats. The Solution should provide the capability for multi-screen formats. The Solution should provide the capability for smart formats that are based on information returned by the State

11.5 Host Systems Interface

11.5.1 11.5.2 11.5.3 The Solution should provide emergency transmission support to all MDS's and CAD dispatchers for the jurisdiction. The Solution should allow an MDS to add narrative to an incident. The Solution should provide for the entry of text information that goes directly to the narrative of a call whether or not the call is active or cleared. The Solution should provide records database inquiry on wants/warrants, hazards, jacket activity, house watches, geo-file verifications, and vehicles.

11.5.4

Page 74 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

11.5.5

The Solution should provide message routing between MDS's and the Computer Aided Dispatch system for the purposes of assisting dispatching, updating unit status, and data base inquiry provided appropriate CAD interfaces are licensed. The Solution should provide the ability to do global name searches. The Solution should provide confirmation messages to the mobile device from CAD when the dispatcher receives Messages, Information, and Unit Status Updates from that mobile device. The Solution should provide one key emergency messages from MDS to CAD. The Solution should provide the ability to initiate "quick calls" from the mobile devices which alert the dispatch center of an event, officer location, license plate number, unusual circumstances and/or other added narrative. The Solution should support voiceless dispatch for law enforcement, fire and EMS personnel. The Solution should provide information on open incidents by ORI status. The Solution should provide information on unit status by ORI display. The Solution should provide information on all units associated with an incident. The Solution should provide sign-on/sign-off dispatch, en route, at scene, clear, to hospital, at hospital functions from MDS to CAD. The solution should provide a method of printing citations on the scene. The solution should provide an interface with the DMV files to insert existing vehicle information (e.g. ownership, VIN, etc.).

11.5.6 11.5.7

11.5.8 11.5.9

11.5.10 11.5.11 11.5.12 11.5.13 11.5.14 11.5.15 11.5.16

12

Administrative Functions

12.1 Work Schedules

12.1.1 12.1.2 The solution should allow for recording of personnel information for all employees of the agency. The solution should allow for officers and staff to enter them self on and off duty.

Page 75 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

12.1.3

The solution should allow for supervisors to enter duty assignments, additional duties, scheduled events and other pertinent shift information to track assignments. The solution should generate regular and overtime work schedules to provide 24-hour coverage. Historical reports should be available to track leave usage, duty assignments and other pertinent functions. Shift information should be automatically exchanged with the CAD to provide the Telecommunicator with a complete picture of personnel availability and assignments. Shift and staff duty information should be exportable to the agency's finance system for payroll, leave accounting and other personnel duty reporting requirements as appropriate.

12.1.4 12.1.5 12.1.6

12.1.7

12.2 Training Records

12.2.1 12.2.2 12.2.3 12.2.4 The solution MUST provide migration / conversion of the current training records. (See http://www.swatsoftware.com/SP%20TRAIN.htm) The solution should allow for recording of training records for each agency employee. The solution should be configurable to set up aging and create lists of employees who are due for specific training / retraining. The solution should allow the search for officers who have specific training.

12.3 Agency Property Inventory

12.3.1 12.3.2 12.3.3 The solution should allow for recording agency property issued to each officer or employee. The solution should be capable of recording agency property issued to specific offices or functions, inside or outside of the agency. The solution should be able to generate agency property inventory reports as required.

12.4 Electronic Interfaces

12.4.1 The solution should provide a seamless interface between all modules so that a single entry of information will become global throughout the entire solution.

Page 76 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

12.4.2

The solution should provide an interface to satisfy all requirements of state and federal laws, local ordinances and agency policies with regard to victim notification rights. The solution should interface to such peripheral programs as fingerprint (LiveScan) and mug shots such that duplicate data entry of identifying information is eliminated. The solution should provide electronic transfer of fingerprint, mug shot and warrant data to laptops and state and federal agencies as needed. The solution should allow for printing mug shot and / or fingerprints on demand. The mug shot should be displayed to the user when a mug shot exists for a person being entered. The solution should allow for automated, electronic generation of lineups, using digital mug shots, from remote workstations (i.e. investigations).

12.4.3

12.4.4 12.4.5 12.4.6 12.4.7

12.5 Court Management System (CMS)

12.5.1 12.5.2 12.5.3 12.5.4 Case dispositions should be shared from the CMS to the RMS and JMS for all applicable cases. Sentencing information should be shared from the CMS to the RMS and JMS for all applicable cases. Bail information should be shared from the CMS to the RMS and JMS for all applicable cases. Acceptance of bail or fine at the Jail should result in the automatic issuance of a printed receipt and electronic update of the CMS, RMS and JMS bail / fines functions. An interface should be provided to allow judges and court staff to review and approve affidavits electronically. Warrant issue and tracking module of the RMS, CMS and JMS systems should electronically share pertinent information. The master name index of the RMS and JMS should automatically be updated to reflect entries made in the CMS and vise versa where applicable.

12.5.5 12.5.6 12.5.7

Page 77 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

13

Implementation

13.1 Installation Needs

13.1.1 Installation / upgrade solutions MUST include the following: 13.1.1.1 13.1.1.2 13.1.1.3 13.1.1.4 13.1.2 13.1.3 13.1.4 13.1.5 High Level Project Plan with a Tentative Schedule Project Focal Point as a point of contact Proposal for a "Turn Key Solution" Hardware / Upgrade requirements if to be installed on current AS/400 systems (include in APPENDIX D response).

The responder MUST provide System Customization The responder MUST provide Validation Testing The responder MUST provide Pre-Production Functional Testing and skills transfer The responder MUST provide Pre-production and Production Performance and Tuning assistance for up to three months after going live in production The responder MUST help to develop Pre-production and Production Backup procedures The responder MUST be capable of providing Onsite support for Migration to production The responder MUST be capable of providing Remote Support during all three phases

13.1.6 13.1.7 13.1.8

13.2 File Migration / Conversion Requirements

13.2.1 In the event your solution is not capable of handling our current DB2 and OS/400 format files, a file conversion solution MUST be included in your solution. Table definitions will be provided to proposers upon request. Key files and current quantities to be converted include, but may not be limited to the files listed in the chart below:

13.2.2 13.2.3

Page 78 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

File Conversion Candidate Table

HTE CMS (RMS) Modules Years Records*

Incident Reports Arrest Reports Juvenile Arrest Reports Field Interviews Evidence/Property Records Evidence/Property Items Records Towed Vehicle Reports Citations Warrant Files Traffic Accident Reports Intelligence Records Case Management Records HTE CAD Records Jalan Jail Booking Records 13.2.4 13.2.5

13 13 13 13 13 13 13 13 13 13 13 13 12 11

62,811 23,795 3,058 3,744 2,789 22,473 12,310 71,525 7,117 48,402 1,473 62,811 1,352,709 46,410

Please provide any available programs you offer for scrubbing Master Name Index information prior to data conversion. CAD and RMS will be implemented first, along with the file conversion / migration programs to provide call incident data to the present record management system. In the event file conversion is required, the responder should have prior experience converting data from the DB2 and other OS/400 file structures.

13.2.6

13.3 Audit and Security

13.3.1 Customization MUST include Security configurations such that authorization must be allowed or denied for all files and transactions.

13.3.2 13.3.3

The solution MUST provide an audit trail and reporting capability which includes access and attempted access violations. The solution MUST provide dynamic access authorization updates to allow and disallow access to application files and transactions.

Page 79 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

GLOSSARY OF TERMS

ANI ­ Automatic Number Identification corresponds to the subscriber's seven digit telephone number. The ANI displays at the PSAP on the digital ANI display console. ALI ­ Automatic Location Identification provides for an address display of the subscriber calling 911. With ALI, the PSAP receives the ANI display and an ALI display on a screen. The ALI display includes the subscriber's address, community, state, type of service and if a business, the name of the business. The PSAP will also get a display of the associated ESN information (police, fire, rescue). API ­ Application Programming Interface, a set of instructions and functions that programs can use to effect tasks through other systems, such as opening windows, writing files, and completing message boxes -- as well as perform more complicated tasks -- by passing a single instruction. AVL ­ Automatic Vehicle Locator, a system for tracking mobile units through GPS satellite technology. Binding ­ A term frequently used in reference to XML applications taken from the field of computer science. In the context of applications that have a public interface that communicates in XML (such as the case with a web service), binding refers to the information required and the process by which an external source connects to, and interacts with it to get data in XML. Call Detail Record - When the 911 call is terminated by the PSAP operator, the ANI will automatically print-out on the teletypewriter located at the PSAP. The printout will contain the time the call came into the PSAP, the time it was picked up by an operator, the operator number, the time the call was transferred, if applicable, the time the call was terminated and the trunk group number associated with the call. Printouts of the ALI display are now also available, if the PSAP has purchased the required equipment. Client ­ A networked PC or terminal that shares "services" with other PCs. These services are stored on or administered by a server. CAD ­ Acronym for Computer Aided Dispatch System, the collection of programs that support call taking and emergency dispatch functions for the Police Department and other dispatched agencies. CJIS ­ Criminal Justice Information System CPU ­ Abbreviation of Central Processing Unit Digital Images ­ A stored electronic object that may include digital renditions of photographs, fingerprints, crime scene or accident diagrams, videos, etc. E911 ­ Enhanced 911: Features available include selective routing, selective transfer, fixed transfer, alternate routing, default routing, Automatic Number Display, Automatic Location Identification, night service, default routing, call detail record. EJB ­ Enterprise Java Beans is an interface specification which a Java class software objects. EDI ­ Electronic Data Interchange. A term referring to the conduct of eBusiness through the exchange of electronic messages. Ethernet ­ A popular LAN technology that uses CSMA/CD (collision detection) to move packets between workstations and runs over a variety of cable types at 10 Mbps. Also called 10BaseT. GPS ­ Global Positioning System used for satellite-based location determination for AVL and Cellular systems. GUI ­ Graphical User Interface provides a computer program or environment that displays options on the screen as icons, i.e., picture symbols, by which users enter commands HIPPA - Health Insurance Portability and Accountability ACT of 1996

Page 80 of 111

Hoover Police Department Integrated Computer System RFP# 17-04 HPD ­ Acronym for the Hoover Police Department. HTML ­ Hypertext Markup Language Incident Command System ­ The combination of facilities equipment, personnel, procedures, and communications operating with a common organizational structure, with responsibility for the management of assigned resources to effectively accomplish stated objectives pertaining to an incident. Interface ­ The process by which a software application interacts with other software or users. In object-oriented programming an (software) "object's" interface is often described separately from the internal logic in a process know as "encapsulation". Essentially the interface encapsulates and hides the internal logic. This allows flexibility to change and improve object code without affecting other objects. An interface description is made public so other objects/applications know how to interact. Software is said to "implement" an interface if it conforms to the behavior as defined in an interface description. Internet ­ A global network connecting millions of computers in more than 100 countries for exchanges of data, news and opinions. The Internet is decentralized by design, with each Internet computer, called a host, being independent. Its operators can choose which Internet services to use and which local services to make available to the global Internet community. Intranet ­ An internal network that leverages some of the same tools popularized on the Internet (browsers for viewing material, HTML for preparing company directories or announcement, etc.) J2EE ­ Java 2 platform Enterprise Edition - A standard platform for hosting J2EE applications, specified as a set of required APIs and policies. JJIS ­ Juvenile Justice Information System, the juvenile counterpart to the CJIS statewide crime database, but for juveniles. LAN ­ Local Area Network. Typically, a network or group of network segments confined to one building or a campus. Compare to WAN. Markup ­ Special characters used by Markup Languages (SGML, XML, HTML) to differentiate data from metadata. SGML allows document authors the flexibility of specifying which characters are used for markup, where as in XML the markup characters are fixed. MDS ­ Mobile Data System , a mobile device used to support wireless data transfer to/from CAD and RMS systems. M.O.: Abbreviation for "modus operandi," Latin for method of operation. MSAG ­ Master Street Address Guide is a ledger in which are assigned the police, fire or rescue agency will serve a given street and number range. NAS ­ Network-Attached Storage appliances are used to help manage large amounts of data by making file storage space available to network clients, gaining benefits similar to sharing printers over a network. NENA ­ National Emergency Number Association, a professional organization which has developed standards for E-911 and related interfaces. Object ­ A term used frequently in relation to XML and computer science. Strictly speaking, an object is a run-time software construct that resides in the Random Access Memory (RAM) of the host computer. Objects are created by applications from code that defines the object's behavior; this code is called a class. In object-oriented programs, objects interact with other objects to create the behavior of the application. Open System ­ The goal of open systems is interoperability between hardware and software that is defined by the industry at large and not one or two vendors.

Page 81 of 111

Hoover Police Department Integrated Computer System RFP# 17-04 OS ­ operating system ­ is a computer program than directs the computer's hardware and can manage a computer's functions, such as allocating memory, scheduling tasks, accessing disk drives, and supplying a user interface. Examples include Windows XP, Mac OS 8, and Unix. OSS ­ Open Source Software ­ as defined by OSSC "Phase Two" ­ Also known as Phase Two ALI ­ The mobile directory number information of wireless end users and the cell site / cell sector information. It also includes the latitude and longitude of the wireless end user. PSAP ­ Public Safety Answering Point is the police, fire and/or rescue groups as determined by the local municipalities that has typically a "ringin" with ANI and ALI capabilities, but may just receive calls or transferred calls from another PSAP. Public (XML) Interface ­ XML may be employed internal to an application or it may be used to communicate information to another systems outside the originating applications environment. The term `Public Interface' refers to XML used by an application or set of homogeneous applications to communicate with other applications across system boundaries. RAID ­ Redundant array of independent disks, is a highly reliable storage method for saving data on more than one disk simultaneously. At its simplest, a RAID-1 array consists of two drives that store identical information. If one drive goes down, the other continues to work, resulting in no downtime for users. To save disk space, RAID-3, -4, and -5 "stripe" data and parity information across multiple drives (RAID-3 and -4 store all parity data on a single drive). If a single disk fails, the parity information can be used to rebuild the lost data. RMS ­ Acronym for Records Management System, the collection of functional applications that satisfy the bulk of Police Department data processing and internal and external reporting requirements. Router ­ Device that moves data between different network segments and can look into a packet header to determine the best path for the packet to travel. Routers may connect network segments that use different protocols. They also allow all users in a network to share a single connection to the Internet or a WAN. SAN ­ Storage Area Networks function similarly to NAS systems for backup and storage of data-intensive servers, utilizing devices that are detached from the server and centralized in a Storage Farm and connected through a high-speed path. Selective Routing - The capability to route a call to the particular PSAP serving the address associated with the phone making the 911 call. Server ­ A computer or even a software program that provides services to clients ­ such as file storage (file server), programs (application server), printer sharing (print server), fax (fax server) or modem sharing (modem server). See also client. SQL ­ Structured Query Language - A language for querying, writing to, and constructing relational databases. Many versions of SQL exist; meaning that an SQL query that works for one database will not necessarily work against another. Switch ­ A networks device that filters and forwards packets between LAN segments. Switches operate at the data link layer (layer 2) and sometimes the network layer (layer 3) of the OSI Reference Model and therefore support any packet protocol. LANs that use switches to join segments are called switched LANs or, in the case of Ethernet networks, switched Ethernet LANs. UCR ­ Uniform Crime Reporting, involving State and FBI-mandated generation of UCR data to for collection of a reliable set of crime statistics for use in law enforcement administration, operation, and management.

Page 82 of 111

Hoover Police Department Integrated Computer System RFP# 17-04 URL / URI / URN ­ Uniform Resource Locators, Uniform Resource Indicators, and Uniform Resource Names are different, related methods of uniformly referencing resources across networked environments. A recently release W3C Note explains the difference. W3C ­ The World Wide Web Consortium provides standards for developing common protocols that promote its evolution and ensure its interoperability. W3C has more than 500 Member organizations from around the world and has earned international recognition for its contributions to the growth of the Web. Web-service ­ A generic term used to refer to the use of Hypertext Transfer Protocol (HTTP) and XML to exchange information. Wireless 911 ­ Support software and systems to enable public safety dispatchers to locate wireless callers, solving the 911 impasse and satisfying Federal Communications Commission (FCC) mandates while providing a range of additional location-enhanced applications. WSRP (Web Services for Remote Portals) ­ Standard is designed to use XML-based Web services technology such as SOAP to make it possible to easily integrate portals and Web services, even if they are built in different languages. XML ­ Extensible Markup Language, abbreviated XML, describes a class of data objects called XML documents and partially describes the behavior of computer programs which process them. XML is an application profile or restricted form of SGML. (XML) API ­ Application Programming Interface. In the context of XML, parsers expose their data to a calling application via an interface. An interface is a specification (which the parser conforms to) that describes how the parser will pass data from an XML document to a calling application. The two accepted XML API's are DOM and SAX. (XML) Attributes ­ In the context of XML, attributes provide a mechanism for attaching additional metadata to an XML element. For example, <element attribute="value"/>. An XML attribute is not equivalent to an object or relational model attribute. Data model entity attributes may be expressed as either XML attributes or elements. (XML) Elements ­ The fundamental unit of information in XML. Elements are encapsulated by tags, and may contain (among other things) attributes (declared inside the opening tag), other elements, or data.

Page 83 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

ABBREVIATION OF TERMS

ANI ­ Automatic Number Identification ALI ­ Automatic Location Identification API ­ Application Programming Interface AVL ­ Automatic Vehicle Locator CAD ­ Computer Aided Dispatch CJIS ­ Criminal Justice Information System CMS ­ Court Management System CPU ­ Abbreviation of Central Processing Unit DMV ­ Department of Motor Vehicles E911 ­ Enhanced 911 EDI ­ Electronic Data Interchange EJB ­ Enterprise Java Beans ESRI ­ Environmental Systems Research Institute GIS ­ Geographic Information Systems GPS ­ Global Positioning System HIPPA - Health Insurance Portability and Accountability ACT HPD ­ Acronym for the Hoover Police Department. HTML ­ Hypertext Markup Language HTTP - Hypertext Transfer Protocol JMS ­ Jail Management System J2EE ­ Java 2 platform Enterprise Edition JJIS ­ Juvenile Justice Information System LAN ­ Local Area Network MDS ­ Mobile Data Solution M.O.: "modus operandi" MSAG ­ Master Street Address Guide NAS ­ Network-Attached Storage NCIC ­ National Crime Information Center NENA ­ National Emergency Number Association. OS ­ operating system OSS ­ Open Source Software PSAP ­ Public Safety Answering Point RAID ­ Redundant Array of Independent Disks RMS ­Records Management System SAN ­ Storage Area Networks SOP ­ Standard Operating Procedures SQL ­ Structured Query Language 3DES ­ Triple Data Encryption Standard UCR ­ Uniform Crime Reporting URL / URI / URN ­ Uniform Resource Locators URI - Uniform Resource Indicators URN - Uniform Resource Names VIN ­ Vehicle Identification Number W3C ­ The World Wide Web Consortium XML ­ Extensible Markup Language

Page 84 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

APPENDIX A - Responder Cover Letter

COVER LETTER (to be submitted with completed proposal) This is to certify that all information attached herein on this proposal is accurate to the best of my knowledge. The prices included in this proposal are accurate and binding, and reflect my total proposal at a firm, fixed price. By signing this cover letter, the offeror certifies that he has not, either directly or indirectly, entered into any agreement, participated in any collusion, or otherwise taken any action in restraint of free competition with this proposal submitted to the City of Hoover. The bidder also agrees to meet all the Conditions and Specifications set forth above. OFFERING COMPANY: __________________________________________________ AUTHORIZED SIGNATURE: ______________________________________________ PRINTED NAME: _______________________________________________________ DATE: ________________________________________________________________

Page 85 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

APPENDIX B - Qualifications and References

Name of Company: ______________________________________________________ Address: _________________________________________________________________ Email Address: ____________________________________________________________ Telephone: ______________________________Fax: __________________________ 1) Company Background: List the company's accomplishments in all areas that pertain to this RFP. (use additional sheets if necessary) ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ 2) Resume of Principle Contact and/or Project Focal Point: Attach biography _______________________________________________________________________ 3) Project Office: State the location of the Project Office from which project management and technical personnel will be assigned. ________________________________________________________________________

Page 86 of 111

Hoover Police Department Integrated Computer System RFP# 17-04 4) Financial Data: To describe the financial condition of the company, provide financial data, including the most recent audited financial statements, or a copy of the most recent tax return, including Dun and Bradstreet number. ________________________________________________________________________ 5) Client References: Submit a complete customer list, in triplicate. ________________________________________________________________________ 6) Similar Customers: Attach project descriptions for other customers of similar size to Hoover Police Department who implemented the same or similar integrated system as the products proposed and which have been implemented in the last three years. Include a name and telephone number with each reference. ________________________________________________________________________ 7) Your Company: a. What is the number of your employees in each of the following categories? i. ii. iii. iv. v. vi. Management Marketing / Sales Administration Customer Support Other (Identify) Total of All Categories _________________________ _________________________ _________________________ _________________________ _________________________ _________________________

8) Number of Installations: b. i. ii. iii. iv. Please provide the following information pertaining to your customer base: Number of installations (all versions Number of installations (current release) Number of installations in Southeast Number of customers our size or larger ____________________ ____________________ ____________________ ____________________

9) Describe in an attachment your most significant strategic alliances/relationships and the length of time those relationships have been in existence.

Page 87 of 111

Hoover Police Department Integrated Computer System RFP# 17-04 10) 11) a. b. c. d. Do you have an established product release schedule? If YES, please include an attachment with defined schedule. Please identify any active user groups (National, Regional, Alabama). __________________________________________________________ __________________________________________________________ __________________________________________________________ __________________________________________________________ PLEASE NOTE: ANY SERVICE PROVIDER WILL BE REQUIRED TO SUBMIT TO A BACKGROUND CHECK.

Page 88 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

APPENDIX C - Technical Specifications

A. Please attach a description of your solution describing how it addresses each phase of the Hoover Police Department Computer System Requirements as identified below. Please be succinct in your response. a) Record Management System b) Jail Management System c) Computer Automated Dispatch d) Mapping e) Reports f) Administrative Services B. Please describe any additional features your solution provides in addition to the previously mentioned functional requirements.

Page 89 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

APPENDIX D - Hardware and/or Network Diagrams

A. Please attach any Hardware and/or Network diagrams used in describing your solution. B. Please provide a description of the configurations included in the diagrams.

Page 90 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

APPENDIX E - Service and Maintenance

A. Please provide a description of the continuing services / maintenance schedules for your proposed solution. Include sample pricing if separate from purchased cost of the solution. B. Please provide sample three(3) and five(5) year maintenance pricing for your solution. This may be included in the overall pricing sheet.

Page 91 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

APPENDIX F - Implementation

A. What types of service will your company provide to assist with the design, configuration, and deployment of hardware / software solution into our existing environment? Please differentiate between services provided at no cost versus fee services. B. Please provide a description of the implementation services included as part of your solution. C. Please provide a description of any additional costs to be incurred for implementation of your solution. D. Please provide as complete as possible a high level description and cost breakdown of the implementation tasks for, but not limited to the following: i. ii. iii. iv. v. Installation Customization Testing Migration New solution short term support

E. Please provide a sample of your installation completion checklist.

Page 92 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

APPENDIX G - Price Proposal

A. Please provide your estimated solution pricing breakdown here as follows: a. i. ii. iii. iv. v. b. i. ii. iii. iv. v. c. i. ii. iii. iv. v. PHASE I Hardware Software Implementation Services Maintenance Miscellaneous PHASE II Hardware Software Implementation Services Maintenance Miscellaneous PHASE III Hardware Software Implementation Services Maintenance Miscellaneous _______________________________ _______________________________ _______________________________ _______________________________ _______________________________ _______________________________ _______________________________ _______________________________ _______________________________ _______________________________ _______________________________ _______________________________ _______________________________ _______________________________ _______________________________

SIGNATURE __________________________________________DATE__________

NOTARY______________________________________________DATE__________

Page 93 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

APPENDIX H - Letter of Intent

LETTER OF INTENT ­ DUE TO CITY OF HOOVER POSTMARKED BY 04/10/2004 Date:______________________ City of Hoover 100 Municipal Drive Hoover, AL 35215 RE: Hoover Police Department Integrated Computer System Attention City Clerk: In accordance with instructions of RFPHPD #, this is to notify the City of Hoover that it is the intent of the undersigned to submit a proposal for Hoover Police Department Integrated Computer System for which proposals will be opened on Thursday, May 05, 2004, 5:00 PM CST. ________________________________________ (Signature) ________________________________________ (Printed Name/Title of Signer) ________________________________________ (Name of Firm) ________________________________________ (Street Address or P.O. Box) ________________________________________ (City, State, Zip Code) ________________________________________ (Telephone Number) ________________________________________ (Email address)

Page 94 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

APPENDIX I - Support (How your solution Works)

Software Support

A. How many installations do you currently support? B. Do you offer any "behind the corporate firewall" maintenance and support capabilities? If YES, detail any infrastructure requirements, i.e., hardware/software, and ongoing fees, licenses, etc. C. Do you offer any other automated maintenance and support not specifically addressed above? Please describe in your attachment. D. Please describe in your attachment in detail any third-party software distribution products or services you are aware of that both enhance/replace the native software distribution capabilities of your products. E. Please describe in your attachment your enterprise-level technical support offerings in detail, including both your non-tiered support offerings and tiered support offerings with increasing levels of responsiveness, features, resources, etc. Specifically identify exclusions. F. Please describe in your attachment support levels, hours of coverage and typical response times to the varying levels of problem criticality. Please specify the elapsed time to the first contact with a technical resource once a customer has submitted an incident report. G. Please describe in your attachment the warranty period and the warranty support, which is included with software license. No charge support services shall be provided from the software installation date through the warranty period. H. Please describe in your attachment the support options available from your company for global 24x7 mission-critical issues. Include the hardware (if any) and software supported within the offering. Please state which systems and configurations (Service Level Agreements) SLAs apply. I. Please describe in your attachment your support policy for heritage versions of your solution.

J. Please describe in your attachment your support services for developers (e.g., reactive services, typically involving defects in the product or "how to" questions related to programming once an application has been coded or is in production. K. Please describe in your attachment your engineering services (e.g., proactive services that involve the design and building of applications and integration with the operating system or other applications). L. Identify the city and country locations of your support centers.

Page 95 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

Availability

M. Please describe in your attachment the software and hardware availability/uptime guarantees provided with your Solution. What remedies are available to your customers if availability/uptime guarantees are not maintained? N. Provide a matrix that identifies the level of priority given to various failures, incidents and problems, and initial response time given to each priority level. How do you identify the priority and response times for problem incidents? Give examples.

Future Product Strategy

O. Please describe your strategy for future application development. Include all information on your plans to develop and support Open Systems. P. Please describe your investment into enhancing your solution, and if supported on multiple platforms, provide descriptions for each. Q. What portion (percentage or dollar amount) of your budget is designated for enhancements and new development of your solution? R. Please describe your investment into supporting open standards. Include contributions you may have made to open standards.

Problem / Incident Reporting

S. Describe the problem/incident escalation process and support team organization, including your emergency response times and the highest level of support resources available. T. What criteria are used to define the severity of a problem/incident? Who defines these criteria? U. Are there limits to who may access the support center? V. Are there limits to the number of incidents opened within defined time periods? W. Do you offer remote monitoring and management? Do you offer automated diagnosis and self-healing? X. Do you offer a priority queue arrangement, which provides a high priority for calls placed under a Mission Critical or Platinum-level Support offering? Do you offer a priority arrangement, which routes calls to a dedicated team of technical resources under a Mission Critical or Platinum-level Support offering? Y. What channels are available to submit incidents (e.g., telephone, Web, e-mail, chat, etc.)? Is the response time varied depending on the channel?

Page 96 of 111

Hoover Police Department Integrated Computer System RFP# 17-04 Z. Do you have any on-line support offerings for enterprise customers? (E.g., Knowledgebase, FAQ's, etc.) AA.Do you have a `phone home' or network-based monitoring center whereby your staff can receive events/alarms and respond accordingly (e.g., Sun Remote Services, IBM Service Director)? If YES, describe your `phone home' or network-based monitoring program in detail. BB.What types of periodic statistical reports are currently being generated for your customers, and what information is contained in these reports? For example, do they provide breakdowns of support contacts by type of problem, severity, platform, and elapsed time from initial contact to resolution? Please provide examples of said reports that you currently offer.

GENERAL

CC. Describe in detail any native performance management, monitoring and reporting capabilities incorporated into your product. DD. Describe in detail any native accounting/client charge-back capabilities incorporated into your product. EE.Has your company been named as a defendant in a lawsuit or are you in arbitration related to this solution?

Page 97 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

APPENDIX J - Training / Education

A. B. C. D. E. Please provide the locations of your education centers. (City, State/Country) Do you provide on-site training? If YES, how many students can you accommodate for a given class? Do you provide web-based training? If so, please provide a listing and describe your offerings. Please provide details of any certification training you offer to customers that is recognized for your solution? Please provide both your current list pricing and your discounted pricing you are offering to Hoover Police Department for any training available.

Page 98 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

APPENDIX K - Police Reports

Refer to the listed links for the Hoover Police Department Reports. All Police Reports (Includes all listed files below as one document) Incident Offense Report Supplement Arrest Report Field Interview Report Wreck Report Wreck Supplemental Truck Bus Supplemental Private Property Wreck Towed Vehicle Report Runaway Report Missing Persons Report

Page 99 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

APPENDIX L - Jail Forms

Refer to the listed links for the Hoover Police Department Jail Forms. All Jail Forms (Includes all listed files below as one document). Arrest Packet Transfer Log Chair Report Court Date Info Detention Incident Inmate Agreement Form Inmate Medical Screening Inmate Physician Report Levels of Resistance Report Personal Property Record Release Pending Warrant Vehicle Release Form

Page 100 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

APPENDIX M - Property Forms

Refer to the listed links for the Hoover Police Department Property Forms All Property Forms (Includes all listed files below as one document). DPS Evidence Submission Property Labels Property Receipt Log Property Receipt

Page 101 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

APPENDIX N - Court Forms

Refer to the listed links for the Hoover Municipal Court Forms All Court Forms (Includes all listed files below as one document). Appearance Bond Complaint Property Release Bond

Page 102 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

APPENDIX O - NCIC 2000

Refer to this link for NCIC 2000 requirements documentation. NCIC 2000

Page 103 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

APPENDIX P - Response Worksheet

Response Worksheet

Page 104 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

APPENDIX Q - Council Pricing Sheet

Submit a copy of the provided cover letter (Appendix A) signed by the responsible official in your organization, certifying the accuracy of all information in your proposal, and certifying that your proposal will remain valid for sixty (60) days from the date opened by the City. It should also include the names of individuals within the company to contact for technical, pricing, and contractual question CITY OF HOOVER REQUEST FOR PROPOSAL FORM PROPOSAL # 17-04 HOOVER POLICE DEPARTMENT INTEGRATED COMPUTER SYSTEM OFFERING COMPANY __________________________________________________ ADDRESS ____________________________________________________________ TELEPHONE # (____)______-_______________________ CONTACT PERSON_____________________________________________________ WEB ADDRESS ________________________________________________________ The following pricing format is solely for the purpose of expediency for the opening and reading of proposals by the Hoover City Council at 5:00 PM, CST, on Thursday, May 13, 2004. This form will not be used in the evaluation process of the proposals attached, however, these prices MUST coincide with prices listed in APPENDIX G. 1) TOTAL BID FOR PHASE I - to include all aspects of implementing Records Management System and Jail Management: $ __________________________________________ 2) TOTAL BID FOR PHASE II - to include all aspects of implementing CAD: $ ____________________________________________________ 3) TOTAL BID FOR PHASE III - to include all aspects of implementing Mobile Computing: $ ___________________________________________________

TOTAL OF LINES 1, 2 & 3: $ _____________________________________________ PROPOSER SIGNATURE ________________________________________________ NOTARY___________________________________________ DATE ______________

Page 105 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

APPENDIX R - ACJIC Audit Requirements

ACJIC Audit Requirements

Page 106 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

APPENDIX S - Test Requirements

FUNCTIONAL SYSTEMS TEST

At least sixty (60) days prior to commencement of the functional systems testing, the vendor shall submit for approval a detailed functional systems test plan based on the general procedures described herein and that shall certify that the desired functionality has been delivered and meets all performance and load benchmarks. The test plan shall document how each functional specification is to be tested, the method of testing and the anticipated results. This documentation shall describe each scenario to be used for each functional specification. The functional systems test shall be conducted jointly by the agency's Project Manager and designees and the vendor. The functional systems test will: · Demonstrate every functional attribute of the software, including system software, operating system, utilities, interfaces, system administration procedures, all ancillary application program modules and all management information requirements. · Verify that all transactions with external systems are performing as specified. · Test and verify that real-time recovery and switching to the backup system(s) operates as specified by the vendor. · Conduct full-scale load benchmarks based on scenarios jointly developed with the vendor and approved by agency staff. The test results shall be included in the test report and the agency's Project Manager or designee shall have the option of conducting an independent test of all or any of the functional requirements, as specified in the Response Document. Within fourteen (14) days after completion of functional systems testing, the vendor shall provide a written report to document completion of the test, and to indicate test results, problems, solutions and a schedule to implement such solutions. When the operating system, software and interfaces have been delivered, installed and fully tested, including the functional systems test, and the system is ready for reliability testing, the vendor shall provide written certification to the agency's Project Manager that the installation phase of the contract has been fully completed and all requirements have been met.

Page 107 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

Reliability Test

The reliability test shall run for a period of thirty (30) consecutive days, twenty-four (24) hours a day for a total of seven hundred twenty (720) consecutive hours after the system is implemented in production mode. This period shall be known as the performance period. During the performance period, the agency shall have the option to run in parallel mode all subsystems that will be replaced by the system until the system is fully accepted. The performance period shall begin on the date the vendor notifies the agency that the system is ready for reliability testing. If there is a system failure, as defined below, deficits shall be corrected and the reliability test and the performance period shall start over. The following criteria constitute the standard of performance: The system shall operate in conformance with the vendor's technical specifications and functional descriptions, which shall satisfy the requirements of this proposal at a 100% accuracy level: · As quoted in the vendor's proposal · As amended in the contract negotiations · As amended throughout the design and development stages · As formally documented Operation use time and downtime shall be measured in hours and whole minutes. System failure downtime is that period of time during which the scheduled productive workload, or simulated workload, being used for reliability testing cannot be continued on the system due to failure of a software system component. If simulated workload is being used for reliability testing, it shall be consistent with the data processing requirements set forth elsewhere in this contract. Operational use time for performance testing for a system is the accumulated time during which the system is in actual operation and can be used by the agency. Downtime for each incident shall start from the time the agency contacts the vendor's designated representative at the prearranged contact point until the system(s) is back in proper operating condition. The vendor shall provide continuous telephone coverage to permit the agency to make such contact. Any single failure or any series of failures of the system software that results in any of the following conditions shall be considered a system failure: · Complete shutdown of the system. This includes failures that cause human intervention to maintain critical operations or to restart the operating system or server applications software to restore the system function. · If three (3) seconds is the specified response time, then an increase to nine (9) seconds or longer in five (5) transactions is a system failure. · An increase in any single transaction response time of four (4) times the response time proposed in the RFP, or longer. For example, if three (3) seconds is the specified response time, then an increase to twelve (12) seconds in one (1) transaction is a system failure. Loss of any of the basic system functions, such as the inability to transfer event messages between workstations, loss of the use of all communication functions, or the inability of the system to maintain folder status or event status on a current basis.

Page 108 of 111

Hoover Police Department Integrated Computer System RFP# 17-04 · Loss of all or a major part of the mobile functions; loss of the ability to communicate with most or all of the mobile devices. · Repeated failures of the same function or equipment component is unacceptable even if it does not cause the conditions listed above for a system failure. · More than two incidents of downtime per week for the same problem. · Any critical entry or information control capability is not available at all active workstation positions. · The loss of the ability of the system to communicate (in either direction) with agency systems, interfaces, data sources. During the reliability test period the system shall be fully available, in excess of seven hundred sixteen (716) hours, i.e., a total of four (4) hours or more of downtime (unavailable time) shall be considered system failure. The agency shall maintain appropriate daily records to satisfy the above requirements and shall notify the vendor in writing of the date of the first day after the successful performance period. The date of acceptance shall be the first day after the successful performance period. If the system fails to meet the standard of performance after ninety (90) calendar days from the installation date or start of the performance period, whichever is later, the agency may at its option request a rescission of the contract and request the immediate removal of the system. The impact on prior payments of such a rescission shall be determined in contract negotiations.

Page 109 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

APPENDIX T - Security

A. Please describe how you solution uses security features such as but not limited to: a. digital signature b. encryption c. cryptography d. access control to files and documents B. Please describe any capabilities relating to transport-level security protocols such as Secure Sockets Layer (SSL). C. Does your solution provide any security assessment tools, utilities, or services offerings? Please describe.

Page 110 of 111

Hoover Police Department Integrated Computer System RFP# 17-04

Appendix U - Current AS400 CAD Hardware Configuration

AS/400 (iSERIES) Hoover2 Configuration

9406-820 Item Current Model 9406-820 Main Storage 1,536.0 MB DASD 85.8 MB RAID YES Processor CPW 370 Interactive CPW 70 Processor Group P20 Comm Lines (6)V.24 Active Twinax Devices Supported 40 PC Server Adapter NO 9348-002 Tape Controller YES Internal 7GB 8MM Tape Unit NO 3575-L06 Tape Controller YES Utilization on Hoover 2 and Hoover 1 are less than 20% on average.

Ask for further details on Hoover 1.

Page 111 of 111

Information

STANDARDS

112 pages

Find more like this

Report File (DMCA)

Our content is added by our users. We aim to remove reported files within 1 working day. Please use this link to notify us:

Report this file as copyright or inappropriate

737581


You might also be interested in

BETA
STANDARDS