HomeMy WebLinkAboutRFP - P847 COMPUTER AIDED DISPATCH (8)City of Fort Collins i Proposal P-847
REQUEST FOR PROPOSAL
Proposal Number P-847
The City of Fort Collins is seeking proposals from qualified firms to provide, install, and support
a new Computer Aided Dispatch (CAD), Records Management System (RMS), Jail
Management System (JMS).
Please request a copy of the proposal by e-mailing Keith I. Ashby at Kashby@fcgov.com
Vendors will respond on the Microsoft Excel® spreadsheet format provided by the City and
deliver sixteen (16) electronic copies of proposals (on CD Rom), to the City of Fort Collins'
Purchasing Division, 215 North Mason St., 2nd floor, Fort Collins, Colorado 80524. Proposals
will be received before 3:00 p.m. (our clock), August 2, 2002. Proposal No. P-847. Please
submit proposals on CD Rom via overnight mail to City of Fort Collins, Purchasing Division,
215 North Mason Street, 2nd Floor, Fort Collins, Colorado 80524.
Questions concerning the scope of the project should be directed to Larry Vail, Project Manager
at (970) 416-2706 (Office) or (970) 217-1270 (Cell)
Questions regarding proposals submittal or process should be directed to Keith I. Ashby, CPPO,
Buyer, (970) 416-2191.
Sales Prohibited/Conflict of Interest: No officer, employee, or member of City Council, shall have
a financial interest in the sale to the City of any real or personal property, equipment, material,
supplies or services where such officer or employee exercises directly or indirectly any decision-
making authority concerning such sale or any supervisory authority over the services to be
rendered. This rule also applies to subcontracts with the City. Soliciting or accepting any gift,
gratuity favor, entertainment, kickback or any items of monetary value from any person who has
or is seeking to do business with the City of Fort Collins is prohibited.
Collusive or sham proposals: Any proposal deemed to be collusive or a sham proposal will be
rejected and reported to authorities as such. Your authorized signature of this proposal assures
that such proposal is genuine and is not a collusive or sham proposal.
The City of Fort Collins reserves the right to reject any and all proposals and to waive any
irregularities or informalities.
Sincerely,
James B. O'Neill II, CPPO, FNIGP
Director of Purchasing & Risk Management
City of Fort Collins i Proposal P-847
TABLE OF CONTENTS
1 - General Information................................................................................................................... 1
1-1 Larimer County Background........................................................................................... 1
1-2 Participating Agency Profiles..........................................................................................1
1-3 Description of Current Systems.......................................................................................3
1-3.1 PECC CAD and Communications...........................................................................3
1-3.2 LCSO CAD and Communications...........................................................................4
1-3.3 FCPS Records Management System....................................................................... 5
1-3.4 LCSO Records and Jail Management System.........................................................5
1-3.5 Mobile Data............................................................................................................. 5
1-3.6 Court System........................................................................................................... 5
1-3.7 Office Automation Systems - Fort Collins.............................................................. 5
1-3.8 Office Automation Systems - Larimer County........................................................5
1-3.9 Office Automation Systems - Other Agencies........................................................ 6
1-3.10 Computer Room and Network Description - All Agencies.....................................6
1-4 Statement of Purpose....................................................................................................... 6
1-5 Project Goals....................................................................................................................6
1-6 Purchasing Procedures.....................................................................................................8
1-7 Proposal Process and Response Methodology................................................................ 8
1-8 Critical Issues Identified..................................................................................................9
1-9 Significant Dates..............................................................................................................9
1-10 Pre-Proposal Conference............................................................................................... 10
1-11 Written Questions.......................................................................................................... 11
1-12 Contact with the Participating Agencies........................................................................11
1-13 Proposal Delivery Instructions.......................................................................................11
1-14 Terms and Conditions.................................................................................................... 12
1-15 Insurance........................................................................................................................14
1-16 Introduction, Qualifications and References................................................................. 15
1-17 Pricing Proposal.............................................................................................................16
1-18 Vendor Experience Requirements..................................................................................17
1-19 Evaluation & Award Process......................................................................................... 17
1-19.1 Evaluation Criteria Weighting............................................................................... 18
1-20 Contact Information.......................................................................................................18
1-21 Acronym Glossary.........................................................................................................20
2 - Global System Specifications...................................................................................................24
2-1 CAD Full Integration.....................................................................................................24
2-2 RMS and JMS Full Integration......................................................................................24
2-3 System Hardware and Software.....................................................................................24
2-3.1 Documentation.......................................................................................................24
2-3.2 Help Functions.......................................................................................................25
2-3.3 Hardware Specification - Production Database.....................................................25
2-3.4 Hardware Specification - Crime Analysis Database............................................. 26
2-3.5 Hardware Specification - Desk & Mobile Workstations....................................... 26
2-3.6 Nearline Archive Storage...................................................................................... 28
2-3.7 Backup Strategy.....................................................................................................29
City of Fort Collins ii Proposal P-847
2-3.8 Operating Systems.................................................................................................29
2-3.9 Database and Software Specifications...................................................................29
2-3.10 Network Protocol...................................................................................................31
2-3.11 Y2K Compliance................................................................................................... 31
2-3.12 System Implementation......................................................................................... 31
2-3.13 System Warranty....................................................................................................32
2-3.14 System Training.....................................................................................................33
2-4 System Administration.................................................................................................. 34
2-4.1 General System Security....................................................................................... 34
2-4.2 CAD Specific Security Functions..........................................................................36
2-4.3 RMS/JMS Specific Security Functions................................................................. 37
2-4.4 Personnel Module Specific Security Functions.....................................................38
2-5 System Interface Specifications.....................................................................................38
2-5.1 General Requirements........................................................................................... 39
2-5.2 Computer Aided Dispatch..................................................................................... 39
2-5.3 E911 Interface........................................................................................................39
2-5.4 ProQA Interface.....................................................................................................40
2-5.5 TDD Interface........................................................................................................40
2-5.6 Master Timing Source........................................................................................... 40
2-5.7 CCIC/NCIC Interface............................................................................................ 41
2-5.8 SunPro Fire Records Mangement System............................................................. 43
2-5.9 Toning/Pager Interfaces.........................................................................................43
2-5.10 Colorado IBRS and NIBRS...................................................................................43
2-5.11 Document Imaging (FCPS and LCSO)................................................................. 44
2-5.12 Municipal Court System Interface.........................................................................46
2-5.13 Voice...................................................................................................................... 46
2-5.14 Livescan.................................................................................................................47
2-5.15 Certex.....................................................................................................................47
2-5.16 Commissary........................................................................................................... 47
2-6 Database Conversion Specifications............................................................................. 47
2-6.1 CAD Data (PECC and LCSO)...............................................................................47
2-6.2 RMS data (Fort Collins Police Services)...............................................................48
2-6.3 RMS/JMS data (Larimer County Sheriff’s Office)............................................... 48
2-7 Data Search Specifications............................................................................................ 48
2-7.1 Searches and Inquiries........................................................................................... 48
2-8 Data Entry Specifications.............................................................................................. 50
2-9 Master Indexes...............................................................................................................52
2-9.1 General Provisions.................................................................................................52
2-9.2 Master Name Index................................................................................................53
2-9.3 Master Location Index...........................................................................................56
2-9.4 Master Vehicle Index............................................................................................. 57
2-9.5 Master Property Index........................................................................................... 59
2-10 Mugshot Module............................................................................................................60
2-11 Known Offender Module...............................................................................................61
2-12 Web Based Functionality...............................................................................................62
2-13 Workflow Process Specifications.................................................................................. 63
City of Fort Collins iii Proposal P-847
2-14 Report Generation Specifications..................................................................................63
2-14.1 General Requirements........................................................................................... 63
2-14.2 System Administration Reports.............................................................................64
2-15 Location Specifications................................................................................................. 65
2-16 Mapping.........................................................................................................................65
2-16.1 General Requirements........................................................................................... 65
2-16.2 Vendor Supplied Geofile........................................................................................66
2-16.3 Geofile Maintenance Tools....................................................................................68
2-16.4 Map Display...........................................................................................................69
2-17 Personnel Database........................................................................................................70
2-17.1 General Requirements........................................................................................... 70
2-17.2 Evaluation Process.................................................................................................73
2-17.3 Internal Affairs.......................................................................................................74
2-17.4 Hiring Process........................................................................................................74
2-17.5 Scheduling and Attendance................................................................................... 76
2-17.6 CAD Interface to Personnel...................................................................................79
2-17.7 Personnel Reports.................................................................................................. 80
2-18 Training Database..........................................................................................................81
2-18.2 Training Reports.................................................................................................... 83
2-18.3 Academy Process...................................................................................................85
2-18.4 Academy Reports...................................................................................................87
2-19 Supplies, Equipment and Facility Management system................................................89
2-19.1 Supply Order and Tracking....................................................................................89
2-19.2 Equipment Inventory and Maintenance.................................................................90
2-19.3 Facility Management............................................................................................. 92
2-19.4 Vendor Database.................................................................................................... 93
2-20 Miscellaneous Functions............................................................................................... 94
2-20.1 Lookouts................................................................................................................ 94
3 - Computer Aided Dispatch........................................................................................................96
3-1 System Design............................................................................................................... 96
3-1.1 General Requirements........................................................................................... 96
3-2 CAD Client.................................................................................................................... 97
3-2.1 General Requirements........................................................................................... 97
3-2.2 Location and Number of CAD Clients.................................................................. 98
3-2.3 User Interface.........................................................................................................98
3-2.4 Event and Unit Status Monitors and Functions................................................... 101
3-2.5 Log On/Off Commands....................................................................................... 104
3-3 Call Taking and Initiation............................................................................................ 105
3-3.1 Event Initiation Processing..................................................................................105
3-3.2 Address Validation...............................................................................................108
3-3.3 Street Addresses...................................................................................................109
3-3.4 Intersections......................................................................................................... 110
3-3.5 Commonplace Names..........................................................................................110
3-3.6 Street Aliases....................................................................................................... 111
3-3.7 Event Updates...................................................................................................... 111
3-4 Event Processing..........................................................................................................111
City of Fort Collins iv Proposal P-847
3-4.1 General Requirements..........................................................................................111
3-4.2 Event Priorities.................................................................................................... 113
3-4.3 Event Routing...................................................................................................... 113
3-4.4 Resource Recommendations................................................................................113
3-4.5 Hazard and Premise Files.................................................................................... 114
3-4.6 Event and Case (report) Numbering.................................................................... 117
3-5 Dispatch Functions...................................................................................................... 117
3-5.1 General Requirements..........................................................................................117
3-5.2 Event Control Functions......................................................................................120
3-5.3 Unit Control Functions........................................................................................ 123
3-5.4 System Actions.................................................................................................... 125
3-5.5 Tow Request Rotation..........................................................................................127
3-5.6 Fire/Ambulance Dispatching...............................................................................128
3-5.7 Automated On-Line SSM Control Features........................................................ 131
3-6 Mobile Data Computer................................................................................................ 135
3-7 Mapping and Geofile Functions.................................................................................. 142
3-7.1 General Requirements......................................................................................... 142
3-7.2 Map Display.........................................................................................................142
3-8 System Administration Functions............................................................................... 144
3-8.1 Default and Restricted Values..............................................................................144
3-8.2 General Inquiry Requirements.............................................................................145
3-9 Reports and Search Functions..................................................................................... 146
3-9.1 General Requirements and Reports..................................................................... 146
3-9.2 Event Related Reports......................................................................................... 147
3-9.3 Unit and Employee Related Reports................................................................... 149
3-9.4 Search Functions..................................................................................................150
3-10 Security Features......................................................................................................... 151
3-10.1 Audit Log.............................................................................................................151
3-10.2 CAD Management Information System.............................................................. 152
3-10.3 Personnel Module Interface.................................................................................152
3-11 Other CAD Requirements............................................................................................153
3-11.1 Computer Assisted CAD Training.......................................................................153
3-11.2 Scratch Pad.......................................................................................................... 153
3-11.3 Electronic Mail and Messaging Functions.......................................................... 153
3-11.4 Memos/Reminders...............................................................................................154
3-11.5 Information Files................................................................................................. 155
4 - Records Management.............................................................................................................156
4-1 System Design............................................................................................................. 156
4-1.1 General Requirements and Design Features........................................................156
4-1.2 Location and Number of RMS/JMS Clients........................................................158
4-1.3 RMS Printing Services........................................................................................ 158
4-2 Case Report Entry and Processing...............................................................................160
4-2.1 General Requirements......................................................................................... 160
4-2.2 Case Report and Data Entry................................................................................ 160
4-2.3 Case Report Processing....................................................................................... 162
4-3 Traffic Enforcement.....................................................................................................166
City of Fort Collins v Proposal P-847
4-4 Field Reporting............................................................................................................ 168
4-4.1 General Requirements......................................................................................... 168
4-5 Arrest Processing.........................................................................................................169
4-6 Criminal Investigation & Analysis.............................................................................. 172
4-6.1 Investigations.......................................................................................................172
4-6.2 Crime Analysis.................................................................................................... 174
4-7 Case Management........................................................................................................175
4-8 Warrants Tracking........................................................................................................180
4-9 Civil Service Process................................................................................................... 181
4-10 Property and Evidence Management System.............................................................. 184
4-10.1 General Requirements......................................................................................... 184
4-10.2 Evidence Entry and Processing........................................................................... 186
4-10.3 Property Administration...................................................................................... 187
4-10.4 Laboratory Examination...................................................................................... 189
4-11 Victim’s Response Module..........................................................................................190
4-12 Community Policing Support System......................................................................... 190
4-13 Crime Reporting Requirements................................................................................... 192
4-14 Miscellaneous Applications.........................................................................................193
4-14.1 Pawn Module.......................................................................................................193
4-14.2 Towing and Impoundment Records.....................................................................195
4-14.3 Field Interview.....................................................................................................196
4-14.4 Licenses............................................................................................................... 196
4-14.5 Bicycle Registration.............................................................................................197
4-14.6 Alarm Tracking....................................................................................................198
4-15 RMS Reports............................................................................................................... 199
4-15.1 Crime and Event Reports.....................................................................................199
4-15.2 Investigative & Crime Analysis Reports............................................................. 200
4-15.3 Case Management Reports.................................................................................. 201
4-15.4 Arrest Reports......................................................................................................203
4-15.5 Property and Evidence Reports........................................................................... 203
4-15.6 Traffic Reports.....................................................................................................203
4-15.7 Police Management Reports................................................................................205
5 - Jail Management.....................................................................................................................207
5-1 General Requirements................................................................................................. 207
5-1.1 Workflow Process................................................................................................207
5-1.2 Scheduling........................................................................................................... 207
5-1.3 Process Notification.............................................................................................208
5-1.4 Other General Requirements............................................................................... 210
5-2 Booking and Release Process...................................................................................... 210
5-2.1 Booking - Person Entry....................................................................................... 210
5-2.2 Booking - Charge Entry and Tracking.................................................................213
5-2.3 Booking - Property Entry and Tracking.............................................................. 215
5-2.4 Property Issued.................................................................................................... 215
5-2.5 Sentence Calculation........................................................................................... 216
5-2.6 Release Process....................................................................................................217
5-3 Inmate Housing and Movement...................................................................................217
City of Fort Collins vi Proposal P-847
5-3.1 Classification....................................................................................................... 217
5-3.2 Housing................................................................................................................218
5-3.3 Housing Logs.......................................................................................................219
5-3.4 Movement............................................................................................................219
5-3.5 Transportation......................................................................................................220
5-4 Programs and Services.................................................................................................220
5-4.1 Inmate Accounting...............................................................................................220
5-4.2 Programs..............................................................................................................222
5-4.3 Visitation Processing........................................................................................... 223
5-4.4 Commissary......................................................................................................... 223
5-4.5 Food Services.......................................................................................................224
5-4.6 Medical................................................................................................................ 225
5-4.7 Mental Health...................................................................................................... 227
5-5 Administrative Functionality.......................................................................................228
5-5.1 JMS Incident and Disciplinary Reporting (JMSIDR)......................................... 228
5-5.2 ACA Validation and Certification....................................................................... 230
5-5.3 Social Security Administration............................................................................230
5-6 Alternative Sentencing Programs................................................................................ 230
5-6.2 Work Release....................................................................................................... 231
5-6.3 Workender............................................................................................................232
5-6.4 Useful Public Service.......................................................................................... 232
5-6.5 Home Detention...................................................................................................233
City of Fort Collins i Proposal P-847
1. GENERAL INFORMATION
1-1 LARIMER COUNTY BACKGROUND
Larimer County is the fifth largest county in the state of Colorado and is located on the
front range of Colorado at the Wyoming border. Within Larimer County are six Law
Enforcement agencies, two full-time staffed Fire Departments and two full-time staffed
Emergency Medical Services (EMS) districts as well as numerous partially staffed or all
volunteer Fire and EMS agencies. The Law Enforcement agencies are: Fort Collins
Police Services (FCPS), Larimer County Sheriff's Office (LCSO), Loveland Police
Department (LPD), Colorado State University Police Department (CSUPD), Estes Park
Police Department (EPPD), and Berthoud Police Department (BPD). The Fire
Departments are: Poudre Fire Authority (PFA) and Loveland Fire Department (LFD) as
well as volunteer departments. The EMS agencies are: Poudre Valley Ambulance
(PVA) and Thompson Valley Ambulance (TVA) as well as volunteer EMT and fire
personnel to respond to medical calls in rural areas. All of these agencies are
dispatched through one of five public safety answering points (PSAPs) for 911 calls
with all five PSAPs operating their own communications centers.
It is the intent of this Request for Proposal (RFP) to procure a complete information
management system for all Larimer County emergency services agencies (hereafter
referred to as the “Participating Agencies”) that includes Computer Aided Dispatch
(CAD), Records Management System (RMS), Jail Management System (JMS), Mobile
Data Computers (MDC), Automatic Vehicle Location (AVL) and interactive mapping
systems. For brevities sake this RFP will make reference to “The System” throughout
this RFP. The use of the term “system” is inclusive of any singular component or the
system as a whole as identified herein. Because of its role as the largest city in Larimer
County, the City of Fort Collins will act as the purchasing agent for this system.
1-2 PARTICIPATING AGENCY PROFILES
Fort Collins Police Services
FCPS is comprised of 240 employees of which 152 are sworn police officers, 26 are
emergency communications operators, 18 are records technicians and 44 other
personnel that fill other administrative positions. The City of Fort Collins covers
approximately 60 square miles and has a population of approximately 125,000 people.
The FCPS communications center is properly referred to as the Poudre Emergency
Communications Center (PECC) to indicate their role in dispatching the largest fire
agency, Poudre Fire Authority, in Larimer County.
FCPS received approximately 120,149 calls for service the last calendar year (2001)
which generated approximately 23,407 incident reports for the same period. FCPS
utilizes a one to one fleet management program wherein each sworn officer is assigned
a vehicle.
Poudre Fire Authority
City of Fort Collins ii Proposal P-847
PFA is comprised of 155 employees of which 145 are firefighters. PFA covers
approximately 250 square miles with a population of approximately 154,000 people.
PFA has 16 facilities consisting of 14 fire stations an administrative office building and
a training facility. PFA responded to approximately 10,000 incidents in 2001.
Poudre Valley Hospital Ambulance
PVH Ambulance Service is comprised of 22 full and 24 part time paramedic and
emergency medical technicians. PVH covers approximately 2200 square miles of
northern Larimer County and responded to approximately 9000 incidents in 2001.
Larimer County Sheriff's Office
LCSO is comprised of 366 employees of which 105 are sworn patrol and investigations
deputies, 183 are sworn jail deputies, 15 are emergency communications operators, 14
are records technicians and 39 that fill other administrative positions. The County of
Larimer covers approximately 2,650 square miles and has an overall population of
approximately 272,000 people, approximately 75,000 of which live in the
unincorporated areas of Larimer County.
LCSO received approximately 70,000 calls for service the last calendar year which
generated approximately 14,000 incident reports for the same period. LCSO utilizes a
one to one fleet management program wherein each sworn patrol and investigations
deputy is assigned a vehicle. The jail booked approximately 22,000 prisoners during
the last calendar year and has a capacity for approximately 520 inmates in the hard jail.
LCSO has an active alternative sentencing unit that is currently tracking over 1,000
inmates in various programs.
Loveland Police Department
LPD is comprised of 123 employees of which 83 are sworn police officers, 18 are
emergency communications operators, 15 are records technicians and 7 that fill other
administrative positions. The City of Loveland covers approximately 35 square miles
and has a population of approximately 55,000 people.
LPD received approximately 58,000 calls for service the last calendar year which
generated approximately 16,000 incident reports for the same period. FCPS utilizes a
one to one fleet management program wherein each sworn officer is assigned a vehicle.
Loveland Fire Department
No information available
Thompson Valley Ambulance
No information available
City of Fort Collins iii Proposal P-847
Note: Loveland Police, Fire and Thompson Valley Ambulance currently dispatch
out of the Loveland PSAP using a North American Tri-Tech CAD system and a
MASI RMS. At this time there is no commitment on the part of Loveland
agencies to move to the new system but specifications for the system are intended
to allow such a move at a later date.
Colorado State University Police Department
CSUPD is comprised of 45 employees of which 27 are sworn police officers, 6 are
emergency communications operators, 2 are records technicians and 10 that fill other
administrative positions. Colorado State University owns various properties throughout
Larimer County. The main campus covers approximately 1 square mile and is located
within the city limits of Fort Collins. The registered student population is
approximately 24,000 students.
CSUPD received approximately 17,000 calls for service the last calendar year which
generated approximately 3,600 incident reports for the same period. CSUPD utilizes a
pool car fleet management program wherein each sworn officer checks out a vehicle for
each shift.
Estes Park Police Department
EPPD is comprised of 26 employees of which 16 are sworn police officers, 8 are
emergency communications operators, 2 are records technicians. The Town of Estes
Park covers approximately 10 square miles and has a population of approximately 6,000
people.
EPPD received approximately 18,000 calls for service the last calendar year which
generated approximately 2,700 incident reports for the same period. EPPD utilizes a
pool car fleet management program wherein each sworn officer checks out a vehicle for
each shift.
Berthoud Police Department
BPD is comprised of 8 employees of which 7 are sworn police officers, and one
functions as both the dispatcher and records technician. The Town of Berthoud covers
approximately 10 square miles and has a population of approximately 5,000 people.
BPD received approximately 8,000 calls for service the last calendar year which
generated approximately 2,000 incident reports for the same period. BPD utilizes a one
to one fleet management program wherein each sworn officer is assigned a vehicle.
1-3 DESCRIPTION OF CURRENT SYSTEMS
1-3.1 PECC CAD AND COMMUNICATIONS
The Police Department maintains a 24-hour emergency communications center. The
Center is presently equipped with seven dispatcher positions. Communications with
City of Fort Collins iv Proposal P-847
field units is handled primarily through an 800 MHz trunked radio system that is shared
with other agencies in Larimer County. Typically FCPS dispatchers have responsibility
for controlling patrol, investigative units, fire response, EMS response, and animal
control.
PECC currently has a PRC Computer Aided Dispatch (CAD) system purchased in
1983. The system runs on a VaxServer. Dispatchers and call takers interact with the
CAD system via a proprietary PRC terminal application running on a variety of PC
workstations. The PRC CAD is presently interfaced with the following external
systems:
Plant Equipment Vesta 911 Controller.
Colorado Bureau of Investigation (CBI) Inquiry Interface.
PRC Records Management System.
PRC Mobile Clients via CDPD.
SunPro Fire Records Management System.
Zetron Fire Alert System.
Pager Interfaces
1-3.2 LCSO CAD AND COMMUNICATIONS
The Sheriff’s Office maintains a 24-hour emergency communications center. The
Center is presently equipped with eight dispatcher positions. Communications with
field units is handled primarily through a VHF radio system that is shared with other
agencies in Larimer County. Typically LCSO dispatchers have responsibility for
controlling patrol, investigative units, fire response, EMS response, and animal control.
LCSO currently has a Printrak Computer Aided Dispatch (CAD) system purchased in
1994. The system runs on a Compaq (Tandem) Server. The CAD system is shared with
CSUPD, EPPD, and BPD. Dispatchers and call takers interact with the CAD system
via a proprietary Printrak client application running on a variety of PC workstations.
The Printrak CAD is presently interfaced with the following external systems:
Plant Equipment Vesta 911 Controller (at 3 PSAPs).
Colorado Bureau of Investigation (CBI) Inquiry Interface.
Larimer County Records and Jail Management System.
Zetron 2200 Pager System.
City of Fort Collins v Proposal P-847
1-3.3 FCPS RECORDS MANAGEMENT SYSTEM
In 1983, the city purchased a law enforcement records management system from PRC,
Inc. The system runs on a VaxServer with an Oracle v6 database. At present, the
records system contains incident, arrest, and other kinds of records from 1983 until the
present. The RMS is shared with CSUPD.
1-3.4 LCSO RECORDS AND JAIL MANAGEMENT SYSTEM
In 1987, the county developed an in-house law enforcement records and jail
management system that runs on a Unisys 2200/500 mainframe with an Unisys DMS
1100 database. At present, the records system contains incident, arrest, booking, and
other kinds of records from 1987 until the present. The RMS is shared with EPPD, and
BPD.
1-3.5 MOBILE DATA
FCPS, Poudre Fire Authority (PFA) and Poudre Valley Ambulance (PVA) deploys
MDC’s in all of their vehicles using CDPD connectivity to CAD/RMS as well as
CCIC/NCIC (law enforcement only) and car to car messaging. Wireless connectivity,
other than CDPD, is being investigated to allow other agencies wireless access to the
system.
1-3.6 COURT SYSTEM
In 1999 the City of Fort Collins Municipal Court purchased and deployed a court
management system from Justice Systems, Inc. of Albuquerque, N.M. The system is a
Windows NT-based system running on top of an Oracle relational database on PC
hardware.
1-3.7 OFFICE AUTOMATION SYSTEMS - FORT COLLINS
In addition to the CAD and RMS computers, FCPS currently maintains its office
automation systems on an Intel based server. Adhering to the city's system standards,
FCPS uses GroupWise for email, calendaring, and other communications tasks. The
city uses Microsoft Office products for its office automation. Currently the city is
implementing a SIRE document imaging system from Alpha Numeric Systems city
wide. SIRE image and document management system is a standard used by the City of
Fort Collins and should be interfaced with the new RMS/JMS as specified in the
interface section.
1-3.8 OFFICE AUTOMATION SYSTEMS - LARIMER COUNTY
In addition to the CAD, RMS/JMS computers, LCSO currently maintains its office
automation systems on an Intel based server. Adhering to the county's system
standards, LCSO uses GroupWise for email, calendaring, and other communications
tasks. The county uses Microsoft Office products for its office automation. Currently
the county is implementing a FileNET document imaging system county wide.
City of Fort Collins vi Proposal P-847
FileNET image and document management system is a standard used by Larimer
County and should be interfaced with the new RMS/JMS as specified in the interface
section.
1-3.9 OFFICE AUTOMATION SYSTEMS - OTHER AGENCIES
In general the other agencies maintain their office automation systems on Intel based
servers. The other agencies use either GroupWise or Outlook for email, calendaring,
and other communications tasks. All of the other agencies use Microsoft Office
products for their office automation.
1-3.10 COMPUTER ROOM AND NETWORK DESCRIPTION - ALL AGENCIES
Both PECC and LCSO have the ability to provide protected space to house needed
system hardware that will be capable meeting any reasonable specification the vendor
may have for space, temperature, power, access, and connectivity. Vendor must clearly
specify all hardware requirements for the proposed system.
The larger participating agencies are currently connected to one another over a high
speed, privately owned, fiber optic network. The networks are currently configured as
10-Base-T using the TCP/IP protocol via a routed connection between agencies. Future
plans include upgrading the agency interconnections to 100mb/s circuits via a
combination of point-to-point fiber and/or VPN circuits via our shared ISP. EPPD and
BPD are connected at slower speeds (down to T-1 frame relay), and there are offsite
substations that are connected at speeds down to 56K frame relay. Vendor must clearly
specify communications requirements. A network diagram of the existing WAN will be
provided on request.
1-4 STATEMENT OF PURPOSE
The participating agencies are soliciting proposals from qualified firms in response to this
Request for Proposal (RFP) to provide, install, and support a new CAD/RMS/JMS. The
integrated system should contain all the functionality defined by this RFP.
Briefly, the acquisition and implementation of new CAD, RMS, and JMS applications are
intended to improve the technology support for daily operations and enhance the
organizational knowledge base. In order to meet the needs of all participating agencies the
systems proposed in response to this RFP must be as fully integrated (defined below) as
possible to provide the participating agencies with full inter-agency inter-operability.
1-5 PROJECT GOALS
The primary goals of this project are as follows:
To procure a system which meets the requirements of this RFP and which can
demonstrate the ability to meet the future needs of the participating agencies.
To procure a proven, advanced public safety computer system, from a single vendor.
City of Fort Collins vii Proposal P-847
To procure a records management system which will allow the participating agencies
to migrate to Colorado IBRS reporting.
To procure a system which captures relevant and discreet information about the
delivery of public safety services, the occurrence of crime and other disorder events,
and is able to provide the participating agencies with a comprehensive understanding
of service demands and resource utilization.
To procure a highly-integrated CAD/RMS/JMS which automatically shares relevant
information between the applications and modules so that users are able to cross
reference disparate information more efficiently.
To procure a system which creates a single inter-agency knowledge base regardless of
where the information was first captured or with which module it is associated.
To procure a system which allows users to access the knowledge base effectively
regardless of whether they are operating in a desktop or mobile, LAN or WAN
environment.
To procure a system which allows all users to access the knowledge base effectively
regardless of whether they are occasional users or they have received advanced
training in the construction and use of query tools and languages.
To procure a system which ensures the timely recording and delivery of information.
To procure a system which is designed to provide relevant information to the user
proactively.
To procure a system which incorporates consistency in the design of the user interface
and the operation of the system across the various applications and modules so as to
minimize the user’s learning curve.
To procure a system which is able to perform such that users will never have to wait
for critical information and will rarely have to wait for routine information.
To procure a CAD application which minimizes the number of routine tasks which the
user is required to do through the implementation of automated routines and system
interfaces.
To procure a system which is highly reliable in terms of application availability and
which can demonstrate superior data integrity.
To procure a system from a vendor with a proven track record for delivering reliable,
high-performance, effective information systems for law enforcement agencies in a
timely manner.
City of Fort Collins viii Proposal P-847
To procure a system which has demonstrated exceptional reliability in other customer
sites.
To procure a system which can be maintained by the participating agencies with
minimal vendor intervention.
1-6 PURCHASING PROCEDURES
Fort Collins Police Services will act as the procurement authority for this project.
Definitions:
All specifications will be rated as to need in one of three categories:
Critical - Without this functionality this system will not be purchased,
Priority - Functionality that is considered very important but that could be sacrificed if
overall functionality meets the participating agencies need,
Preferred - Functionality that the participating agencies would like to have if possible
but not required for purchase approval.
Note: All specifications that are rated as “Critical” will be clearly identified in the RFP.
For the purposes of this document the word "system" is intended to include the
combination of applications and equipment which make up the complete vendor
supplied solution. The term "application" is used to refer to one of the proposed
applications, such as CAD or RMS.
The words “shall” and “must” in the following specifications indicate functions which
are seen as a high priority to the participating agencies.
The words “desired” and “preferred” are used to indicate highly desirable functions that
the participating agencies would like to achieve but may be willing to sacrifice to obtain
greater priority functionality.
1-7 PROPOSAL PROCESS AND RESPONSE METHODOLOGY
This RFP was created with Microsoft Word and Excel 2000/XP and will be provided to the
vendors in electronic format only. Sections 2 through 5 (specifications) are provided both
in this Word document and in an Excel 2000/XP spreadsheet. There is a separate Excel
spreadsheet for the vendor pricing response. The vendor’s proposal must contain a Word
document with responses to Sections 1-16 (Introduction, Qualifications, and References),
Section 1-17 (Pricing Proposal), and 1-18 (Vendor Experience Requirements) as well as
comments related to the spreadsheets provided for Sections 2 through 5 (System
Specifications). This Word document is for reference purposes only. All vendor response
to this RFP must be in a separate Word document and the Excel 2000/XP spreadsheets
provided. No other response will be accepted.
City of Fort Collins ix Proposal P-847
Proposers will answer within the Excel spreadsheet with one of the following responses
only:
Yes - The proposed system currently meets all the requirements of the section and is
included in the proposed system, at the proposed cost.
No - The proposed system does not currently meet all of the requirements of the
section, the non-complying functionality is not included in the proposed solution, and
the vendor does not anticipate development to address this requirement.
Alternate (Alt) - The proposed system meets the intent of the section but does not
accomplish it in the same manner as it has been described. When using this answer the
vendor shall attach a separate sequentially numbered Word addendum to the end of the
section explaining in detail how their product meets the intent of the requirement.
Modification Required (MR) - The proposed system does not currently meet all the
requirements of the section, but the vendor will address the requirement through new
development. When using this answer the vendor is committing to deliver the function
as a part of this project (i.e. it is required for final acceptance). If the vendor is charging
the participating agencies for developing this functionality the additional cost shall be
clearly stated in a pricing proposal.
Note: It is not acceptable for the vendor to answer “Yes” to a specification when the
functionality exists only in a product currently in development. It is expected that any
“Yes” answer will be functionality currently installed and running at an agency where a
site visit could be performed.
1-8 CRITICAL ISSUES IDENTIFIED
CAD/RMS/JMS Operating System Must be IBM AS400 OS or Sun Microsystems’s
Unix. - See 2-3.3 (3)“The hardware platform for the CAD/RMS/JMS”
CAD/RMS/JMS Database Management Systems Must be IBM DB2 or Oracle. - See 2-
3.9 (3)“CAD/RMS/JMS production database”
RMS and JMS Full Integration. - See 2-2 “RMS and JMS Full Integration”
CAD APCO Phase II Wireless Compliant. - See 2-5.3 (1) “APCO Phase II Wireless
Compliance”
CAD Command Line Function. - See 3-2.3 (1) “Command Line Interface”
CAD Pro Q&A Interface. - See 2-5.4 “Interface for ProQA”
1-9 SIGNIFICANT DATES
Due Date for Written Questions is July 12, 2002 @ 4 PM.
Pre-Proposal Conference is scheduled for July 17, 2002 @ 10 AM.
Proposals Due by August 2, 2002 @ 3 PM.
City of Fort Collins x Proposal P-847
Complete Final Evaluation - TBD
Complete Contract Negotiations - TBD
Project Kick-off - TBD
Note: All dates and times given are local times for Fort Collins, Colorado.
1-10 PRE-PROPOSAL CONFERENCE
Pre-proposal conference is planned for the date listed in the Significant Dates section
above. The meeting will be held at City Council Chambers, 300 La Porte Ave, Fort
Collins, CO. A walk-through of any of the participating agencies facilities will be
conducted as desired immediately after the bidder’s conference. Separate arrangements
can be made for technical representatives to visit any of the facilities at a later date, if
necessary.
Agency locations:
Fort Collins Police Services
300 LaPorte Avenue
Fort Collins, CO 80521
970 221-6540
Poudre Fire Authority
102 Remington
Fort Collins, CO 80521
970 221-6570
Poudre Valley Hospital (Ambulance)
1024 Lemay Avenue
Fort Collins, CO 80524
970 495-7000
Larimer County Sheriff’s Office
2501 Midpoint Drive
Fort Collins, CO 80525
970 498-5100
Loveland Police Department
810 E. 10th Street
Loveland, CO 80537
970 667-2151
Colorado State University Police Department
Green Hall, CSU
Fort Collins, CO 80523
970 491-6425
City of Fort Collins xi Proposal P-847
Estes Park Police Department
170 East MacGregor
Estes Park, CO 80517
970 586-4000
Berthoud Police Department
328 Massachusetts Avenue
Berthoud, CO 80513
970 532-2611
1-11 WRITTEN QUESTIONS
The City of Fort Collins will accept questions and requests for clarifications of the RFP
until the date listed in the Significant Dates section above. Questions should be submitted
in writing to:
Larry Vail
Project Manager
Fort Collins Police Services
300 La Porte Avenue
P.O. Box 580
Fort Collins, CO 80522
970 416-2706
970 217-1270 (mobile)
lvail@fcgov.com
Answers to these questions will be provided in writing at the pre-proposal conference.
Vendors may also ask follow-up questions related to their initial questions at the pre-
proposal conference. Written answers to these questions will be provided within two
weeks after the completion of the conference.
1-12 CONTACT WITH THE PARTICIPATING AGENCIES
After the announcement of the RFP vendors shall direct all questions and inquiries to Larry
Vail. Any attempt to initiate contact with another employee or contractor for any of the
participating agencies, other than those listed herein as technical contacts, or discussion of
this RFP with any employee or contractor shall be grounds for immediate disqualification.
1-13 PROPOSAL DELIVERY INSTRUCTIONS
Proposers shall respond as previously directed in the electronic format required by the City
of Fort Collins. Hard copies of the RFP will not be accepted or evaluated.
Proposals must be delivered to the City of Fort Collins by August 2, 2002 @ 3 PM.
Proposals shall be addressed and delivered to:
City of Fort Collins xii Proposal P-847
City of Fort Collins
Purchasing Department
Attn: Keith Ashby
215 N. Mason
Fort Collins, CO 80521
The proposal shall prominently display the vendor's name and return mailing address and
the RFP title and number as it appears on the cover page of this RFP.
It will be the sole responsibility of the proposer to have their proposal delivered to the City
of Fort Collins before the closing hour and date shown for receipt of proposals.
Late proposals will not be accepted. Proposers submitting late proposals will be notified
of their rejection within 10 days. Proposals will be deleted from any electronic storage
maintained by the City of Fort Collins and any disks will be destroyed.
The city will direct all correspondence to the vendor address to which the initial
announcement of the RFP was sent. It shall be the vendor’s responsibility to ensure that
all communications are routed correctly within their own organization. The city will bear
no responsibility for delays associated with the improper routing of official
communications. The city will change the mailing address for communications upon
written request to:
City of Fort Collins
Purchasing Department
Attn: Keith Ashb
215 N. Mason
Fort Collins, CO 80521
1-14 TERMS AND CONDITIONS
Proposals must follow the proposal format described in this Chapter.
Proposers must fill in all of the blank spaces on the electronic response spreadsheet.
All costs associated with preparing proposals and conducting on-site oral presentations are
the sole responsibility of the vendors.
Original proposals must show the company name and indicate the company officer or
employee who has the authority to bind the company or firm by their signature.
The proposer must certify that the proposed system, applications, interfaces and
functionality described within the proposal are a bona fide offer by the corporation and that
the vendor will supply same for the quoted price if selected by the city.
The proposer must certify that the prices, terms and conditions in the proposal will be firm
for a period of one hundred eighty (180) days from the date of proposal opening.
City of Fort Collins xiii Proposal P-847
Proposals may not be withdrawn before the expiration of one hundred eighty (180) days.
Prices shall be firm, with no escalator clauses.
All items proposed shall be shipped F.O.B. to one of two final destinations within the City
of Fort Collins. No additional delivery costs of any kind will be paid by the city.
In the event of default on the part of the proposer after notice of award, the city may take
such action as it deems appropriate including legal action for damages or specific
performance.
The vendor shall obtain and pay for all permits, licenses and approvals necessary for the
execution of the contract. The firm shall comply with all of the laws, ordinances, rules,
orders, and regulations relating to performance of work.
The City of Fort Collins and all other participating agencies are exempt from any taxes
imposed by the State and Federal government. Exemption certificates will be provided
upon request.
For the purpose of evaluation, proposer shall indicate any exception to the requirements
contained herein. The city will not determine exceptions based on a review of the proposal
or any attached sales or manufacturer's literature. Where deviations from the requirements
may result in lower cost and/or improved performance, vendors are encouraged to
describe, in writing, equipment or software which is in full agreement with the
specification as well as suggested alternates in sufficient detail to permit evaluation.
Vendors shall explain why the alternate configuration will provide equivalent or improved
performance and/or lower cost.
The city reserves the right to accept or reject any or all proposals or parts of proposals, to
waive irregularities and technicalities, and to request changes to proposals or re-proposals.
The city also reserves the right to award the contract on such items the city deems will best
serve the interests of the city and the participating agencies. The city further reserves the
right to award the contract on a "split order" basis, or such combination as shall best serve
the interests of the participating agencies unless otherwise specified. The city reserves the
right to negotiate with vendors regarding variations to the original proposal(s) which may
be in the best interest of the city and participating agencies.
The city may alter the scope and requirements of this RFP at any time in order to obtain a
system which will best meet the needs of the participating agencies. The city shall not be
required to reissue the RFP even if the scope or price of the selected system has changed
substantially from the original proposal.
The city is not required to accept the lowest cost proposal for this project.
The city shall not be responsible for oral interpretations given by any city personnel,
representative or others. Only written responses from the city shall be binding.
All proposals and supporting materials as well as correspondence relating to the RFP shall
become the property of the city when received.
City of Fort Collins xiv Proposal P-847
The City of Fort Collins is subject to public information laws, which permit access to most
records and documents. Proprietary information in your response must be clearly
identified and placed in a separate section. Information so identified will be protected to
the extent legally permissible. Proposals may not be marked “Proprietary” in their
entirety. Information considered proprietary is limited to material treated as confidential in
the normal conduct of business, trade secrets, discount information, and individual product
or service pricing. Summary price information may not be designated as proprietary.
All proposals will become the property of the city once they have been submitted.
Vendor must submit a statement designating a responsible official in your organization
who certifies the accuracy of all information in your proposal, and certifies that your
proposal will remain valid for 180 days from the date you submit it. It should also include
the names of individuals within the company to contact for technical, pricing, and
contractual questions.
1-15 INSURANCE
Vendors shall maintain and provide evidence of a $1,000,000 Combined Single Limit
Commercial General Liability Broad Form Endorsement/or the following as minimum
requirements:
Products and completed operations
Broad form property damage
Premises/Operations
Independent Contractors
(Blanket) Broad form Contractual
Personal Injury - delete contractual exclusion “A”
Additional Insureds
Employees and elected and appointed officials of Customer
Worker’s Compensation as required by law
$100,000 Employers’ Liability
$1,000,000 combined Single Limit Automobile Liability, including hired and leased
vehicles, and owned and non-owned autos. No Fault coverage as required by law.
Professional Liability Insurance with minimum limits of $1,000,000 per occurrence
and $1,000,000 aggregate.
GENERAL CERTIFICATES OF INSURANCE
All Certificates of Insurance and duplicate policies of any outside vendor or subcontractor
shall contain the following clauses:
City of Fort Collins xv Proposal P-847
“The insurance company(s) issuing the policy or policies shall have no recourse
against the City of Fort Collins for payment of any premiums or for assessments under
any form of policy.”
“Any and all deductibles in the above described insurance policies shall be assumed
by and before the account of, and at sole risk of the contractor.”
All Certificates are to provide thirty (30) days notice of material change or
cancellation. Certificates of Insurance and insurance binders must be provided no less
than ten (10) working days before commencement of work to the City of Fort Collins
Office of Risk Management carriers are subject to the approval of the City of Fort
Collins, which shall not be unreasonably withheld.
1-16 INTRODUCTION, QUALIFICATIONS AND REFERENCES
All submissions required by this chapter shall be electronically submitted in a Microsoft
Word 97/2000/XP document.
Executive Summary: Submit an introductory narrative of your proposed solution covering
the main features and benefits that distinguish it from others. We recommend that this
document not exceed fifteen pages.
Company Profile: submit a narrative description of your firm including a brief history of
how it became involved in providing public safety products, the major products and
services you now supply, the number of employees, the organization of the company, and
other information you believe is relevant. Also discuss the company’s accomplishments in
the development and installation of public safety information systems.
Project Approach: Describe your approach to the installation, implementation, and
management of public safety information systems. If your services include on-site project
management, electronic status or trouble ticket systems describe these as well.
Personnel and Office: Provide the resume of up to three proposed project managers for this
project. If technical or other personnel will have a substantial role in the project their
resumes should also be included. State the location of the Project Office from which
project management and technical personnel will operate.
Financial Data: Provide financial data which will substantiate your ability to complete the
project on a phased payment schedule and your ability to continue business activities for
the long term. Include your most recent audited financial statements or a copy of your
most recent tax return.
Client References: Submit a complete list of past and present customers for public safety
information systems. Include a list of the products acquired by each customer, the year of
acquisition, the year of implementation and a contact name and phone number for each
site. If the customer no longer uses your products the proposal shall state the reason for
the termination. This section shall also include a one or two page description of not less
than three projects that are similar to the requirements of this RFP.
City of Fort Collins xvi Proposal P-847
Previous Legal Actions: Include a complete description of each and every legal action to
which the company has been party, be they defendant or plaintiff. Such descriptions shall
also include any arbitration proceedings to which the company has been a party, except
those brought by employees for work related grievances.
Use of Sub-Contractors: Discuss the work that will be accomplished by subcontractors, if
applicable, and provide references for previous projects for the subcontractors, and for
occasions when the vendor/subcontractor relationship was the same as that being proposed
for this project, if applicable.
NOTE 1: Vendors that fail to provide a complete list of past and present customers may be
excluded from further consideration.
NOTE 2: Vendors that fail to provide a complete list of litigation and arbitration may be
excluded from further consideration.
1-17 PRICING PROPOSAL
Vendor price proposals shall include four major sections; hardware, software, services, and
options.
The hardware pricing section will include the following itemized prices:
Unit and total price for each type of proposed servers.
Unit and total price for each type of proposed workstation and monitor.
Unit and total price for each type of bar code reader or label printer.
Unit and total price for each other item of hardware proposed for the system.
Itemized cost of warranty for each proposed item of hardware.
The software pricing section will include the following itemized prices:
Unit and total price for each systems software application proposed for servers
including operating system license, relational database software, system utilities and
other applications. Specify the total number of users or concurrent users, whichever is
more restrictive.
Unit and total price for each systems software application proposed for the
workstations, regardless of whether they are being provided by the vendor, including
operating system license, system utilities and other applications.
Unit and total price for all application software which will reside on the servers.
Unit and total price for all application software which will reside on the workstations.
Unit and total price for all third party applications which will reside on the
workstations or servers.
The unit cost for interfaces if they are off-the-shelf applications.
City of Fort Collins xvii Proposal P-847
The services pricing section will include the following itemized prices:
The quantity, cost per hour and total cost for project management services.
The quantity, cost per hour and total cost for each proposed training class.
The quantity, cost per hour and total cost for proposed technical services such as
system installation and tailoring, geofile production, and data conversion.
The quantity, cost per hour and total cost for interface design and build services.
The options pricing section will include an itemized cost for any optional hardware,
software or services which are not required to meet the base requirements of this RFP,
but which the vendor feels may be useful to the city.
The cost proposal will include a summary of the pricing which lists the sub-total for
each category and the total cost for the complete system as proposed.
Vendors may add explanatory notes to their pricing clarifying how the prices in the
proposal were derived.
We are seeking the optimal solution for all participating agencies thus, alternative
functional proposals are encouraged. Follow the same procedure outlined above, but
clearly mark alternative proposals as such.
1-18 VENDOR EXPERIENCE REQUIREMENTS
In order to be considered for this project the prime contractor must submit a statement that
they meet the following conditions along with the qualifying information requested:
The vendor shall have been conducting business for a period of more than five years.
The vendor shall be primarily engaged in the provision of information systems for
public agencies and private companies.
The vendor shall have installed systems similar in scope and functionality for at least
three jurisdictions with service area populations over 200,000 within the last three
years. Provide the names of agencies and contact information.
1-19 EVALUATION & AWARD PROCESS
Proposal responses will first be evaluated for their completeness and adherence to the form
and format requirements.
Proposals will then be objectively evaluated by a qualified team based on the evaluation
criteria in this Chapter. - See 1-19.1 “Evaluation Criteria Weighting”
Based on their scores, the city will select up to four finalists for further evaluation.
In the second phase finalists will be asked to make on-site oral presentations, answer
questions and demonstrate their products to selected members of the participating
City of Fort Collins xviii Proposal P-847
agencies. It is expected that vendors demonstrate, on a fully functional system, all
specifications listed as capable in the RFP response. Vendors will be granted up to five
days, at the city’s discretion, for these on-site demonstrations.
Following the on-site demonstrations the city will select two to three vendors for further
evaluation. During this third phase the city will conduct due diligence evaluations of each
vendor's reliability and performance on other public safety projects. In addition members
of the participating agencies may choose to visit sites where the proposed system is
installed, visit the proposer's headquarters or conduct other evaluations as the city deems
useful in their evaluation.
After Phase Three evaluations have been completed the evaluation committee will rank
order the finalists according to their proposal score, their past history as a supplier of
public safety systems, and the committee's evaluation of which proposed system will best
meet participating agencies near and long-term requirements.
Contract negotiations with the highest ranked vendor will begin immediately.
Milestone payment schedules will be specified in the contract.
1-19.1 EVALUATION CRITERIA WEIGHTING
Proposals will be evaluated according to the following criteria:
Category Weighting
Software Functionality 30
System Architecture & Hardware Functionality 15
Qualifications and References 15
Warranty and Service Program 15
Price Proposal 15
Implementation Plan 10
Final scoring in each category will be multiplied by the weighting factor and then added
together to achieve a final overall score.
1-20 CONTACT INFORMATION
Fort Collins Police Services:
Larry Vail
Project Manager
Fort Collins Police Services
300 La Porte Avenue
P.O. Box 580
Fort Collins, CO 80522
970 416-2706
City of Fort Collins xix Proposal P-847
970 217-1270 (mobile)
lvail@fcgov.com (e-mail)
Larimer County Sheriff's Office:
Steven Bebell, Lieutenant
Information Services Manager
Larimer County Sheriff's Office
2501 Midpoint Drive
Fort Collins, CO 80525
970 498-5102
970 214-6822 (mobile)
bebell@co.larimer.co.us (e-mail)
PRC CAD/RMS:
Mr. Mike Poth
Vice President
Customer Service
PRC, Inc.
Northrop Grumman Information Technology
12005 Sunrise Valley Dr.
Reston, VA 20191
703 264-5466
Plant Equipment:
Mr. Fred Miller
Technical Support
Plant Equipment
42505 Rio Nedo
PO Box 9007
Temecula, CA 92589
909 719-2100 (Main Office)
858 945-5800
800 618-4998 (Mobile)
CBI Interface:
Mr. Russ D. Arch
Operating Systems Manager, IT Unit
Colorado Bureau of Investigation
690 Kipling Street, Suite 3000
Denver, CO 80215
303-239-4289
Municipal Court System:
City of Fort Collins xx Proposal P-847
Ernie Sego
Justice Systems, Inc.
4600 - D McLeod N.E.
Albuquerque, NM 87109
505-883-3987
FileNET Corporation:
Henry Martinez
303 256-5660
303 888-4112
AlphaCorp (SIRE):
Pete Pehrson
3759 West 2340 South, Unit G
Salt Lake City, UT 84120
801 977-8608
1-21 ACRONYM GLOSSARY
The following is a listing of the Acronyms used in this RFP and their associated meanings.
Acronym Description
.DBF Database Format File (file name extension)
.GIF Graphics Interchange Format (file name extension)
.JPG Joint Photographic Experts Group (file name extension)
.PCX Picture Image (file name extension)
.PDF Portable Document File (file name extension), Adobe Acrobat format
.TIF Tagged Image File Format
ACA American Correctional Association
AFIS Automated Fingerprint Identification System
ALI Automatic Location Identification
Alt Alternate
ANI Automatic Number Identification
APCO Association of Public-Safety Communications Officials
ASCII American Standard Code for Information Interchange (text format)
ASU Alternative Sentencing Unit
AVL Automatic Vehicle Location
BOLO Be On The Lookout For
BPD Berthoud Police Department
CAD Computer Aided Dispatch
CBI Colorado Bureau of Investigations
CCIC Colorado Crime Information Computer
CCW Carrying Concealed Weapon
CD Compact Disc
CDPD Cellular Digital Packet Data
City of Fort Collins xxi Proposal P-847
CIC Crime Information Center
CICJIS Colorado Integrated Criminal Justice Information System
CRISCO Criminal Records Information System of Colorado
CRT Cathode Ray Tube
CSOC County Sheriff’s of Colorado
CSU Colorado State University
CSUPD Colorado State University Police Department
DBI Digital Biometrics Incorporated
DBMS Database Management System
DMS Database Management System
DMV Department of Motor Vehicles
DOB Date of Birth
DOR Department of Revenue
DUI Driving Under the Influence
EDMS Electronic Document Management Software
EMS Emergency Medical Services
EPPD Estes Park Police Department
ESN Emergency Service Number
ESRI Environmental Systems Research Institute, ArcView & ArcInfo
ESZ Emergency Service Zone
FBI Federal Bureau of Investigations
FCPS Fort Collins Police Services
FTA Failed to Appear
GED General Equivalency Diploma
GIS Geographical Information System
HAZMAT Hazardous Material
HD Home Detention
IBM International Business Machines
IBRS Incident Based Reporting
IMS Information Management Services
ISP Internet Service Provider
JMS Jail Management System
JMSIDR Jail Management System, Incident and Disciplinary Reporting
LAN Local Area Network
LCD Liquid Crystal Display
LCSO Larimer County Sheriff's Office
LEOKA Law Enforcement Officers Killed or Assaulted
LFD Loveland Fire Department
LIVESCAN Electronic Fingerprint Capture
LPD Loveland Police Department
MDC Mobile Data Computers
MDT Mobile Data Terminal
MIS Management Information System
MLI Master Location Record
MNI Master Name Record
City of Fort Collins xxii Proposal P-847
MO Modus Operandi
MPD Medical Program Director
MPI Master Property Record
MR Modification Required
MSAG Master Street Address Guide
MVI Master Vehicle Record
NCIC National Crime Information Computer
NENA National Emergency Number Association
NEWCOM CCIC User Client Interface
NIBRS National Incident Based Reporting
NIC National Information Center
NLETS National Law Enforcement Telecommunication System
PBT Portable Breath Test
PECC Poudre Emergency Communications Center
PFA Poudre Fire Authority
PO Post Office
PSAP Public Safety Answering Point
PVA Poudre Valley Ambulance
PVC Polyvinyl Chloride
PVH Poudre Valley Hospital
RAM Random Access Memory
RFP Request for Proposal
RMS Records Management System
RO Registered Owner
ROI Record of Interest
ROM Read Only Memory
RTY Record Type, as used by the CBI
SIU Special Investigations Unit, Drug Task Force
SRDB Selective Routing Database
SSM System Status Management
SSP System Status Plan
SVGA Super Video Graphics Array (800x600 lines)
TCP/IP Transmission Control Protocol / Internet Protocol
TDD Telecommunications Device for the Deaf
TID Terminal Identifier, as used by the CBI
TVA Thompson Valley Ambulance
TTY Derives from "Teletype"
UCR Uniform Crime Reporting
UPS Useful Public Service
VOICE Victim/Offender Information, Computer Enhancement
VPN Virtual Private Network
WAN Wide Area Network
WD Withdrew
WE Workender
WR Work Release
City of Fort Collins xxiii Proposal P-847
X-Y Refers to NAD83, State Plane
City of Fort Collins xxiv Proposal P-847
2 - GLOBAL SYSTEM SPECIFICATIONS
2-1 CAD FULL INTEGRATION
Full integration between CAD, mobile client (MDC’s) and Mapping is seen as a high
priority. Additionally, it is also highly desired that the CAD system be integrated with the
RMS/JMS, however integration with RMS/JMS is not as important as full integration
within the CAD environment.
2-2 RMS AND JMS FULL INTEGRATION
****CRITICAL FUNCTIONALITY**** Much of the RMS/JMS functionality is listed
under General System Requirements as the RMS/JMS system is required to be a fully
integrated system that shares the identical look and feel for both RMS and JMS. It is
understood that many vendors now consider the term “Integrated” to be seamlessly
interchangeable with the term “Interfaced” because of the perception on the part of many
buyers that integrated is better than interfaced. For the purposes of this RFP the terms are
not to be interchanged. To clarify these terms the participating agencies define an
integrated system as a RMS/JMS designed and programmed to function as a single
database, fully programmed and fully supported by a single vendor, with one client, one
name file, one vehicle file, one property file, one server, one database engine, one
operating system, and so on (the participating agencies reserve the right to further define
this term). Any proposed system or module that does not fall within this definition is to be
considered an “Interfaced” system.
Ideally the preferred system would have been designed and programmed from its inception
to be both a RMS and JMS so that all levels of development were completed on a single
database. If the proposed system was originally developed as two separate systems that
were then brought together at a later date this fact must be disclosed and the process used
to bring them together fully described. If any feature described in this section operates
differently in any way in RMS as opposed to JMS or if any feature described is present in
only RMS or JMS then that difference must also be clearly identified and described.
Full integration in RMS/JMS is seen as a critical issue to the participating agencies. Only
those systems that have achieved high levels of integration between RMS and JMS will be
considered for purchase.
2-3 SYSTEM HARDWARE AND SOFTWARE
2-3.1 DOCUMENTATION
2-3.1 (1) THE VENDOR SHALL SUPPLY COMPREHENSIVE DOCUMENTATION
FOR THE PROPOSED CAD/RMS/JMS AND ASSOCIATED APPLICATIONS
WHICH COVERS AT LEAST THE FOLLOWING SUBJECTS:
2-3.1 (1.1) SYSTEM USE,
2-3.1 (1.2) SYSTEM ADMINISTRATION (SERVER AND WORKSTATION),
City of Fort Collins xxv Proposal P-847
2-3.1 (1.3) DATABASE SET UP AND MAINTENANCE,
2-3.1 (1.4) INTERFACE DESIGN, USE AND MAINTENANCE,
2-3.1 (1.5) REPORT CREATION AND MAINTENANCE,
2-3.1 (1.6) DOCUMENTATION OF THE AD-HOC REPORTING SYSTEM,
2-3.1 (1.7) AND BACKUP AND RECOVERY FUNCTIONS.
2-3.1 (2) THE PROPOSED APPLICATION DOCUMENTATION SHALL BE
CONSISTENT WITH THE INSTRUCTIONS SUPPLIED BY THE ON-LINE
HELP SYSTEMS FOR THE APPLICATION.
2-3.1 (3) THE VENDOR SHALL UPDATE DOCUMENTATION AND ALL ON-LINE
HELP SYSTEMS AS NEEDED WHEN ANY SOFTWARE CHANGES
OCCUR.
2-3.2 HELP FUNCTIONS
2-3.2 (1) THE CAD/RMS/JMS APPLICATION SHALL PROVIDE ON-LINE, FIELD
OR CONTEXT SENSITIVE HELP FOR ALL FORMS AND COMMANDS.
2-3.2 (2) THE SYSTEM ADMINISTRATOR OR AUTHORIZED USERS SHALL
HAVE THE ABILITY TO ADD, MODIFY AND DELETE THE ON-LINE,
FIELD OR CONTEXT SENSITIVE HELP FILES.
2-3.3 HARDWARE SPECIFICATION - PRODUCTION DATABASE
It is expected that the vendor of the CAD/RMS/JMS will fully specify and cost all
needed server hardware and peripherals required to achieve a fully functioning system
as specified in this RFP. None the less, the participating agencies reserve the right to
purchase any and all server hardware and peripherals at their discretion without
negatively impacting the remaining costs for software, installation, training, support, or
any other vendor provided good or services.
2-3.3 (1) THE PROPOSING VENDOR SHALL ALLOW AND SUPPORT, AT THE
DISCRETION OF THE PARTICIPATING AGENCIES, THE DIRECT
ACQUISITION OF ALL SERVER HARDWARE AND PERIPHERALS BY
THE PARTICIPATING AGENCIES FROM SOURCES OTHER THAN
THROUGH THE PROPOSING VENDOR.
2-3.3 (2) THE PROPOSING VENDOR SHALL ALLOW SUCH ACQUISITION
SERVER HARDWARE AND PERIPHERALS WITHOUT IMPOSING ANY
ADDITIONAL FEES OF ANY KIND TO THE PARTICIPATING AGENCIES.
City of Fort Collins xxvi Proposal P-847
2-3.3 (3) ****CRITICAL FUNCTIONALITY**** THE HARDWARE PLATFORM
FOR THE CAD/RMS/JMS SHALL BE EITHER AN IBM AS400 (OS400) OR
SUN MICROSYSTEMS (UNIX) SERVER.
2-3.3 (4) SERVER REDUNDANCY IS EXPECTED; NO SINGLE PRODUCTION
SERVER FAILURE SHALL RENDER THE CAD/RMS/JMS NON-
FUNCTIONAL.
2-3.3 (5) EXPECTED TOPOLOGY FOR CAD IS FOR THE PRIMARY CAD
FUNCTIONS TO OPERATE ON A SERVER HOUSED AT THE FORT
COLLINS POLICE SERVICES BUILDING, WITH FAIL OVER TO A
SERVER RUNNING AT THE LARIMER COUNTY SHERIFF'S OFFICE.
2-3.3 (6) EXPECTED TOPOLOGY FOR RMS/JMS IS FOR PRIMARY RMS/JMS
FUNCTIONS TO OPERATE ON A SERVER HOUSED AT THE LARIMER
COUNTY SHERIFF'S OFFICE BUILDING, WITH FAIL OVER TO A
SERVER RUNNING AT FORT COLLINS POLICE SERVICES.
2-3.3 (7) SYSTEM SERVERS SHALL BE SIZED TO ENSURE RAPID RESPONSE TO
STANDARD USER QUERY AND ENTRY (RAPID RESPONSE IS
CONSIDERED AN AVERAGE OF ONE SECOND RESPONSE).
2-3.3 (8) SYSTEM SERVERS SHALL BE SPECIFIED WITH SUFFICIENT
STORAGE TO MAINTAIN A MINIMUM OF 15 YEARS OF ONLINE DATA
FOR ALL APPLICATIONS, ALL PARTICIPATING AGENCIES.
2-3.3 (9) VENDOR MUST PROVIDE AN ELECTRONIC DIAGRAM OF THE
TOPOLOGY OF ALL PROPOSED HARDWARE THAT IDENTIFIES ALL
COMPONENTS AND CLEARLY IDENTIFIES THEIR PURPOSE.
2-3.4 HARDWARE SPECIFICATION - CRIME ANALYSIS DATABASE
2-3.4 (1) IT IS EXPECTED THAT AN ADDITIONAL SERVER INTENDED FOR
CRIME ANALYSIS PERSONNEL TO PERFORM EXTENDED DATABASE
QUERIES WILL BE SPECIFIED SO THAT THE PRODUCTION
DATABASE PERFORMANCE IS NOT DEGRADED. THIS SERVER WILL
BE SPECIFIED TO HOUSE A DATABASE OF ALL OF THE CAD/RMS/JMS
FILES THAT ARE NOT PROTECTED BY RESTRICTED USER ACCESS
(INTELLIGENCE FILES, CONFIDENTIAL REPORTS, ETC.).
2-3.4 (2) THE HARDWARE PLATFORM FOR THE CAD/RMS/JMS CRIME
ANALYSIS DATABASE SHALL CONFORM TO INDUSTRY STANDARD
SERVER ARCHITECTURE THAT UTILIZES MICROSOFT WINDOWS®
2000 SERVER OS OR THE SAME OPERATING SYSTEM AS THE
PRODUCTION SERVER.
City of Fort Collins xxvii Proposal P-847
2-3.5 HARDWARE SPECIFICATION - DESK & MOBILE WORKSTATIONS
The participating agencies currently own a variety of industry standard, IBM
compatible, micro computer hardware and peripherals. It should be expected that the
participating agencies will acquire any additional needed micro computer hardware and
peripherals from sources other than the proposing vendor. The intent of this
specification is to establish the minimum configuration of user hardware the vendor
would require to ensure full operational capability from all software that the vendor
would provide. Full operational capability is defined as all functions of the software
being available to the user with load and run times not to exceed 10 seconds, and
operational screen paints and forms selection to occur with no appreciable delay (within
one second). Vendor should assume their software will be running with other high end
software in a multitasking environment.
2-3.5 (1) THE PROPOSING VENDOR SHALL SPECIFICALLY ALLOW AND
SUPPORT THE DIRECT ACQUISITION OF ALL IBM COMPATIBLE,
INDUSTRY STANDARD, MICRO COMPUTER HARDWARE AND
PERIPHERALS BY THE PARTICIPATING AGENCIES FROM SOURCES
OTHER THAN THROUGH THE PROPOSING VENDOR.
2-3.5 (2) THE PROPOSING VENDOR SHALL ALLOW SUCH ACQUISITION OF
IBM COMPATIBLE, INDUSTRY STANDARD, MICRO COMPUTER
HARDWARE AND PERIPHERALS WITHOUT IMPOSING ANY
ADDITIONAL FEES OF ANY KIND TO THE PARTICIPATING AGENCIES.
2-3.5 (3) ALL CLIENT SERVICES SHALL RUN WITH FULL OPERATIONAL
CAPABILITIES ON A DESKTOP COMPUTER WITH AN INTEL PENTIUM
III PROCESSOR (OR GREATER) RUNNING AT 400 MHZ (OR GREATER),
WITH A 20 GIGABYTE (OR GREATER) HARD DRIVE (LOADED TO 40%
CAPACITY BEFORE VENDOR’S SOFTWARE IS LOADED), WITH 112
MEGABYTE (OR GREATER) OF SYSTEM RAM, WITH 8 MEGABYTE
(OR GREATER) VIDEO RAM, WITH A 16X (OR GREATER) CD ROM
DRIVE, WITH 3½" FLOPPY DRIVE, WITH A 17" SVGA (OR GREATER)
CAPABLE MONITOR (CRT OR LCD), WITH BASIC INTEGRATED
SOUND (OR GREATER), WITH 101 KEY INDUSTRY STANDARD
KEYBOARD, WITH A TWO BUTTON MOUSE OR POINTING DEVICE.
2-3.5 (3.1) IF THE VENDOR CAN’T ACHIEVE FULL OPERATIONAL
CAPABILITIES WITH THE DEFINED DESKTOP HARDWARE THE
VENDOR MUST PROVIDE A COMPLETE SPECIFICATION OF THE
MINIMUM REQUIRED HARDWARE THAT WILL ACHIEVE FULL
OPERATIONAL CAPABILITIES.
2-3.5 (3.2) IF THE VENDOR CAN’T ACHIEVE FULL OPERATIONAL
CAPABILITIES WITH THE DEFINED DESKTOP HARDWARE THE
VENDOR MUST DETAIL THE LEVEL OF OPERATIONAL
City of Fort Collins xxviii Proposal P-847
CAPABILITY THAT CAN BE ACHIEVED WITH THE DEFINED
DESKTOP CONFIGURATION.
2-3.5 (4) ALL CLIENT SERVICES SHALL RUN WITH FULL OPERATIONAL
CAPABILITIES ON A NOTEBOOK COMPUTER WITH AN INTEL
PENTIUM III PROCESSOR (OR GREATER) RUNNING AT 400 MHZ (OR
GREATER), WITH A 20 GIGABYTE (OR GREATER) HARD DRIVE
(LOADED TO 40% CAPACITY BEFORE VENDOR’S SOFTWARE IS
LOADED), WITH 112 MEGABYTE (OR GREATER) OF SYSTEM RAM,
WITH A 16X (OR GREATER) CD ROM DRIVE, WITH 3½" FLOPPY
DRIVE (SWAP OUT WITH CD ROM DRIVE), WITH A 12" LCD DISPLAY
(OR GREATER), WITH BASIC INTEGRATED SOUND (OR GREATER),
WITH BUILT IN COMPRESSED KEYBOARD, WITH A TWO BUTTON
POINTING DEVICE.
2-3.5 (4.1) IF THE VENDOR CAN’T ACHIEVE FULL OPERATIONAL
CAPABILITIES WITH THE DEFINED NOTEBOOK HARDWARE THE
VENDOR MUST PROVIDE A COMPLETE SPECIFICATION OF THE
MINIMUM REQUIRED HARDWARE THAT WILL ACHIEVE FULL
OPERATIONAL CAPABILITIES.
2-3.5 (4.2) IF THE VENDOR CAN’T ACHIEVE FULL OPERATIONAL
CAPABILITIES WITH THE DEFINED NOTEBOOK HARDWARE THE
VENDOR MUST DETAIL THE LEVEL OF OPERATIONAL
CAPABILITY THAT CAN BE ACHIEVED WITH THE DEFINED
NOTEBOOK CONFIGURATION.
2-3.5 (5) THE SYSTEM SHALL SUPPORT THE CONNECTION, SETUP, CONTROL
AND FORMATTING OF PRINT JOBS TO THE FOLLOWING:
2-3.5 (5.1) LASERJET PRINTERS (SHEET FEED) (DUPLEX) (BOTH BLACK AND
WHITE AND COLOR),
2-3.5 (5.2) DOT MATRIX PRINTER (CONTINUOUS SHEET FEED),
2-3.5 (5.3) DOT MATRIX OR DESKJET PRINTER (CONTINUOUS LABEL FEED),
2-3.5 (5.4) DESKJET PRINTER (SHEET FEED) (BOTH BLACK AND WHITE AND
COLOR),
2-3.5 (5.5) DYE SUBLIMATION PRINTER (SHEET FEED) (BOTH BLACK AND
WHITE AND COLOR),
2-3.5 (5.6) DYE SUBLIMATION PRINTER (PVC CARD FEED) (BOTH BLACK AND
WHITE AND COLOR),
2-3.5 (5.7) CITATION PRINTER (MOBILE PRINTER IN THE CAR) (MUST BE
DEFINED BY THE VENDOR),
City of Fort Collins xxix Proposal P-847
2-3.5 (5.8) AND DESIGNJET 36" PLOTTER (CONTINUOUS ROLL FEED).
2-3.5 (6) IN ADDITION TO STANDARD INPUT DEVICES (KEYBOARD, POINTING
DEVICE, DISK DRIVES, ETC.) THE SYSTEM SHALL ACCEPT INPUTS
FROM (AND PROVIDE THE ABILITY TO CONTROL AS NEEDED) A
VARIETY OF INPUT DEVICES AS FOLLOWS:
2-3.5 (6.1) FLATBED SCANNER,
2-3.5 (6.2) FLATBED SCANNER WITH AUTOMATIC FEED,
2-3.5 (6.3) HIGH-SPEED DUPLEX SCANNER,
2-3.5 (6.4) BARCODE SCANNER (HANDHELD, OFF AND ONLINE CAPTURE),
2-3.5 (6.5) DIGITAL CAMERA,
2-3.5 (6.6) LIVE VIDEO CAPTURE,
2-3.5 (6.7) MICROPHONE AUDIO,
2-3.5 (6.8) AND LINE AUDIO.
2-3.6 NEARLINE ARCHIVE STORAGE
2-3.6 (1) THE SYSTEM SHALL HAVE THE ABILITY TO FULLY SUPPORT
NEARLINE ARCHIVAL AND STORAGE OF AGED DATA AS DEFINED
AND CONTROLLED BY THE PARTICIPATING AGENCIES.
2-3.6 (2) IT IS ANTICIPATED THAT THE PROPOSED NEARLINE STORAGE
SYSTEM SHALL USE HIGH DENSITY OPTICAL STORAGE MEDIA
(OTHER MEDIA MAY BE PROPOSED FOR CONSIDERATION BUT THE
MEDIA OR DATA MUST BE PORTABLE FOR OFF SITE STORAGE).
2-3.6 (3) THE SYSTEM SHALL AUTOMATICALLY MOVE DATA FROM ONLINE
TO NEARLINE, BUILD AND MAINTAIN ALL INDEXES TO THE
NEARLINE DATA, AND ALLOW FOR BASIC SYSTEM SEARCHES
(NAME, MNI, CASE (REPORT) NUMBER, BOOKING NUMBER,
INCIDENT NUMBER, LOCATION, ETC.) TO IDENTIFY THE
AVAILABILITY OF NEARLINE DATA.
2-3.6 (4) UPON USER REQUEST THE SYSTEM SHALL AUTOMATICALLY
RELOAD REQUESTED NEARLINE DATA TO THE ONLINE SYSTEM,
DESTROY ALL INDEXES TO THE NEARLINE DATA, AND SET A NEW
AGING DATE FOR FUTURE RE-ARCHIVAL OF THAT DATA.
City of Fort Collins xxx Proposal P-847
2-3.6 (5) NO DATA SHALL ARCHIVE TO THE NEARLINE SYSTEM THAT IS
STILL BEING ACTIVELY MODIFIED REGARDLESS OF AGING DATE
(ACTIVE IS DEFINED AS MODIFIED WITHIN THE LAST SIX MONTHS).
2-3.6 (6) THE SYSTEM SHALL HAVE THE ABILITY TO FULLY PURGE ALL
REFERENCE TO NEARLINE DATA AT SYSTEM ADMINISTRATOR
REQUEST (I.E. DESTROY ALL REFERENCE TO A DISC THAT IS
SCHEDULED FOR DESTRUCTION DUE TO AGE OF DATA).
2-3.7 BACKUP STRATEGY
2-3.7 (1) ALL SOFTWARE AND DATA OF ANY KIND RESIDING ON ANY SERVER
OR STORAGE SYSTEM PROPOSED BY THE VENDOR SHALL HAVE A
SYSTEM AND METHODOLOGY TO MAKE BACKUP COPIES OF THAT
SOFTWARE AND DATA.
2-3.7 (2) BACKUP SYSTEMS MUST BATCH PROCESS ALL BACKUPS SO THAT
SOFTWARE AND DATA IS NOT HELD AT RISK IN A CONTINUOUS
WRITE STATE ON ANY SERVER OR STORAGE DEVICE (BACKUP
MEDIA MUST BE FREED BY THE SYSTEM FOR OFFSITE STORAGE IN
A TIMELY MANNER).
2-3.7 (3) BACKUP PROCESS MUST HAVE THE ABILITY TO MAKE MULTIPLE
COPIES OF THE SAME DATA FOR STORAGE AT MULTIPLE
LOCATIONS.
2-3.7 (4) BACKUP SCHEDULES MUST BE DEFINABLE AND CONTROLLABLE BY
THE PARTICIPATING AGENCIES.
2-3.7 (5) THE VENDOR MUST PROVIDE THE ABILITY TO THE PARTICIPATING
AGENCIES TO RESTORE ANY SOFTWARE OR DATA AT THE
DISCRETION OF THE PARTICIPATING AGENCIES’ SYSTEM
ADMINISTRATORS.
2-3.7 (6) THE VENDOR MUST PROVIDE THE ABILITY TO THE PARTICIPATING
AGENCIES TO TEST THE BACKUPS OF ANY SOFTWARE OR DATA AT
THE DISCRETION OF THE PARTICIPATING AGENCIES’ SYSTEM
ADMINISTRATORS.
2-3.8 OPERATING SYSTEMS
2-3.8 (1) CAD/RMS/JMS PRODUCTION SERVER OPERATING SYSTEM MUST BE
IBM AS400 OS OR SUN MICROSYSTEMS SOLARIS 8 UNIX (LATEST
VERSIONS).
2-3.8 (2) CRIME ANALYSIS SERVER MUST USE AN INDUSTRY STANDARD
OPERATION SYSTEM.
City of Fort Collins xxxi Proposal P-847
2-3.8 (3) NETWORK ATTACHED WORKSTATIONS WILL USE THE MICROSOFT
WINDOWS® OPERATING SYSTEM IN VERSIONS, 98, ME, NT40 SP6, 2000
SP2, AND XP PROFESSIONAL. ALL PROPOSED WORKSTATION
SOFTWARE MUST RUN IN THESE VERSIONS OF WINDOWS.
2-3.8 (4) NOTEBOOK COMPUTER SYSTEMS WILL USE THE MICROSOFT
WINDOWS® OPERATING SYSTEM IN VERSIONS, 98, 2000 SP2, AND XP
PROFESSIONAL. ALL PROPOSED WORKSTATION SOFTWARE MUST
RUN IN THESE VERSIONS OF WINDOWS.
2-3.9 DATABASE AND SOFTWARE SPECIFICATIONS
2-3.9 (1) THE PROPOSED CAD/RMS/JMS APPLICATION SHALL INCLUDE A
GRAPHICAL USER INTERFACE FOR ALL CLIENT OPERATIONS.
2-3.9 (2) THE DESIGN OF THE USER INTERFACE WILL ASSIST BOTH
EXPERIENCED AND NOVICE USERS TO COMPLETE INDIVIDUAL
SYSTEM FUNCTIONS.
2-3.9 (3) ****CRITICAL FUNCTIONALITY**** CAD/RMS/JMS PRODUCTION
DATABASE MANAGEMENT SYSTEM MUST BE IBM DB2 OR ORACLE
(LATEST VERSIONS).
2-3.9 (4) CRIME ANALYSIS DATABASE MUST BE AN INDUSTRY STANDARD
DATABASE THAT PERFORMS IN AN OPEN SYSTEM ARCHITECTURE,
STORING ALL DATA IN A NON-PROPRIETARY FORMAT, ACROSS
SEVERAL HARDWARE PLATFORMS, THAT SUPPORTS ALL MODERN
THIRD PARTY REPORTING AND ANALYSIS TOOLS.
2-3.9 (5) ALL DATABASES SPECIFIED BY THE VENDOR DATABASE SHALL BE
SQL COMPLIANT.
2-3.9 (6) ALL DATABASES SPECIFIED BY THE VENDOR MUST SUPPORT ODBC
INDUSTRY STANDARDS.
2-3.9 (7) VENDOR MUST PROVIDE A DIAGRAM OF THE DATABASE
STRUCTURE DOWN TO THE FIELD LEVEL.
2-3.9 (8) VENDOR MUST HAVE PROVISIONS IN PLACE TO PROTECT ALL
CUSTOM FEATURES AND CONFIGURATIONS OF THE SYSTEM
THROUGHOUT AN UPGRADE PROCESS WITHOUT INCURRING
ADDITIONAL COST TO THE PARTICIPATING AGENCIES TO RE-
ESTABLISH CUSTOM FEATURES OR CONFIGURATIONS.
2-3.9 (9) IT IS PREFERRED THAT ALL APPLICATION SUPPORT MICROSOFT
WINDOWS® PRINTING.
City of Fort Collins xxxii Proposal P-847
2-3.9 (10) THE PROPOSED CAD/RMS/JMS APPLICATION SHALL ALLOW THE
USER TO CHANGE THE DEFAULT PRINTER.
2-3.9 (11) VENDOR MUST BE WILLING TO IDENTIFY THE PROGRAMMING
LANGUAGE OF ALL APPLICATION SOFTWARE.
2-3.9 (12) VENDOR MUST BE WILLING TO (AT MINIMUM) ESCROW THE
SOURCE CODE FOR ALL APPLICATION PROGRAMMING.
2-3.9 (13) THE PROPOSED CAD/RMS/JMS APPLICATION DATABASE SHALL
HAVE THE ABILITY TO STORE ELECTRONIC ATTACHMENTS OF ALL
KINDS (WORD DOCUMENTS, MULTIMEDIA FILES, ETC.).
2-3.9 (14) THE PROPOSED CAD/RMS/JMS APPLICATION DATABASE SHALL
HAVE THE ABILITY LIMIT THE SIZE OF ELECTRONIC
ATTACHMENTS OF ALL KINDS (WORD DOCUMENTS, MULTIMEDIA
FILES, ETC.).
2-3.9 (15) THE PROPOSED APPLICATION SHALL EMPLOY A COMBINATION OF
FIELD-LEVEL LOCKING AND RECORD LEVEL LOCKING. EXAMPLE;
SO THAT TWO USERS CAN RETRIEVE, VIEW, AND ADD REPORT
NARRATIVES AT THE SAME TIME, BUT TWO USERS CANNOT
RETRIEVE, VIEW, AND EDIT DIFFERENT PARTS OF A SINGLE FORM
AT THE SAME TIME.
2-3.9 (16) THE PROPOSED CAD/RMS/JMS APPLICATION SHALL HAVE A SIMPLE
MEANS OF EXPORTING DATA AND SEARCH RESULTS IN COMMON
FORMATS SUCH AS ASCII TEXT, .PDF, .DBF, ETC.
2-3.9 (17) THE PROPOSED CAD/RMS/JMS APPLICATION SHALL ALLOW THE
PARTICIPATING AGENCIES TO DESIGN AND ADD THEIR OWN DATA
FIELDS TO THE EXISTING APPLICATION (THE VENDOR SHALL
EXPLAIN ANY CONSEQUENCES OR LIMITATIONS RESULTING FROM
THE ADDITION OF NEW FIELDS TO THE SYSTEM).
2-3.9 (18) THE PROPOSED APPLICATION SHALL ALLOW THE SYSTEM
ADMINISTRATOR OR OTHER AUTHORIZED USER TO ADD NEW DATA
ELEMENTS TO THE DATABASE, TO FORMS, OR TO REPORT
FORMATS.
2-3.9 (19) THE PROPOSED APPLICATION SHALL ALLOW THE SYSTEM
ADMINISTRATOR OR OTHER AUTHORIZED USER TO MODIFY THE
LAYOUT AND DATA ELEMENTS DISPLAYED ON VENDOR SUPPLIED
FORMS AND SCREEN MASKS.
2-3.9 (20) THE PROPOSED CAD/RMS/JMS APPLICATION SHALL ALLOW THE
SYSTEM ADMINISTRATOR OR OTHER AUTHORIZED USER TO
CREATE MACROS FOR COMPLETING COMMON USER FUNCTIONS.
City of Fort Collins xxxiii Proposal P-847
2-3.9 (21) THE PROPOSED APPLICATION SHALL ALLOW THE SYSTEM
ADMINISTRATOR OR OTHER AUTHORIZED USER TO ADD AN
INTERNALLY DEVELOPED REPORT, MACRO, OR OTHER FUNCTIONS
TO THE APPLICATION MENU.
2-3.9 (22) THERE SHALL BE NO LIMITS IMPOSED ON FORMS ATTACHED TO
MASTER CASE RECORDS. FOR EXAMPLE, THERE SHALL BE NO
LIMITS ON THE NUMBER OF PERSONS, ITEMS OF PROPERTY,
STATEMENTS, ARREST REPORTS, SUSPECT DESCRIPTIONS, OR
SUPPLEMENTAL REPORTS.
2-3.10 NETWORK PROTOCOL
2-3.10 (1) THE ONLY ACCEPTABLE MID-LAYERS NETWORK
COMMUNICATIONS PROTOCOL IS TCP/IP. ALL COMMUNICATIONS
HARDWARE AND SOFTWARE (INCLUDING ALL INTERFACES) MUST
BE CAPABLE OF UTILIZING A MODERN, SHARED, WIDE AREA
NETWORK (WIRED OR WIRELESS) WITH TCP/IP AS THE ONLY
COMMUNICATIONS PROTOCOL.
2-3.11 Y2K COMPLIANCE
2-3.11 (1) THE VENDOR MUST WARRANT THAT THE HARDWARE, SOFTWARE,
FIRMWARE, OR SUPPLIES DELIVERED, OR SERVICES PERFORMED
ARE “YEAR 2000 COMPLIANT.” “YEAR 2000 COMPLIANT” MEANS
FAULT-FREE PERFORMANCE IN THE PROCESSING OF DATE AND
DATE-RELATED DATA (INCLUDING, BUT NOT LIMITED TO
CALCULATING, COMPARING, AND SEQUENCING) BY ALL
HARDWARE, SOFTWARE, FIRMWARE, AND SUPPLIES, INDIVIDUALLY
AND IN COMBINATION AS A SYSTEM, WHEN USED IN ACCORDANCE
WITH THE PRODUCT DOCUMENTATION PROVIDED BY THE VENDOR.
FAULT-FREE PERFORMANCE MEANS NO INVALID OR INCORRECT
RESULTS OR ABNORMAL TERMINATION AS A RESULT OF DATE OR
DATE-RELATED DATA OR DATA PROCESSING THAT REPRESENTS OR
REFERENCES DIFFERENT CENTURIES OR MORE THAN ONE
CENTURY; AND PROPER CALCULATION AND HANDLING OF LEAP
YEARS; AND EXCEPT FOR NORMAL USER INTERFACES (E.G. FOUR
DIGIT DATE ENTRY) IDENTIFIED IN THE CONTRACTOR’S OR
VENDOR’S DOCUMENTATION. SUCH DATE DATA PROCESSING
SHALL BE TRANSPARENT TO THE USER.
2-3.12 SYSTEM IMPLEMENTATION
Upon contract award, the vendor will be responsible for developing an
installation/integration plan. The plan will be reviewed and must be approved by the
participating agencies’ Project Management Team. The plan must detail the tasks to be
accomplished, milestones/deliverables, the required resources (both Agencies and
City of Fort Collins xxxiv Proposal P-847
Vendor), and a project schedule/timeline. Payments to the Vendor will be tied to
milestones/deliverables.
The first milestone will be a 30 day trial evaluation of the system. The Vendor will
install the hardware and software onsite and provide in-depth training for a subset of
users. A trainer will remain onsite for full-time operational oversight for the 30 days.
During the 30-day trial, acceptance testing will be conducted by the Agencies’ Project
Team.
Acceptance tests must demonstrate that all software components function in accordance
with the contract and all requirements have been successfully met.
Acceptance tests must demonstrate that all software components acquired function
separately and interact appropriately.
Items that do not pass acceptance testing will be documented and submitted to the
Vendor as soon as they are apparent to the Agencies. The Vendor will have the
opportunity to respond to the noted deficiency. The Vendor’s response must include
details on how the deficiency will be rectified, including a timeline for completion of
the modification. Failure to respond to, or rectify, a noted deficiency within 30 days of
notification will likely result in the termination of the contract.
Installation shall be considered complete only when all software acquired has been
installed and a full set of acceptance tests are successfully conducted jointly by the
vendor and the Agencies.
Costs for training and oversight during the 30 day trial must be separately itemized in
the cost proposal. Since the installation for the 30 day trial will be the final location of
the system, the Agencies do not expect to incur installation costs above and beyond
those proposed for the typical installation. If the contract is terminated during, or
immediately following, the 30 day trial, the Agencies will reimburse the Vendor only
for the actual costs of the training, oversight and installation services performed. No
hardware or software costs will be reimbursed. All estimates and actual cost
notwithstanding the participating agencies limit their liability for this 30 day acceptance
evaluation to no more than $20,000.00.
2-3.13 SYSTEM WARRANTY
2-3.13 (1) VENDOR MUST FURNISH WITH THE PROPOSAL AN EXPLANATION
OF BOTH CONTRACTOR’S AND MANUFACTURER’S WARRANTIES
FOR THE PROPOSED HARDWARE AND SOFTWARE SOLUTION(S) AND
SHALL INDICATE ANY COST DURING WARRANTY PERIOD TO THE
PARTICIPATING AGENCIES, INCLUDING SHIPPING COSTS. A
MINIMUM OF ONE (1) YEAR TO A MAXIMUM OF (5) WARRANTY
SHALL BE PROPOSED WITH ALL COSTS IDENTIFIED PER ANNUM.
City of Fort Collins xxxv Proposal P-847
2-3.13 (2) VENDOR MUST INITIALLY PROVIDE TWO (2) YEARS OF SUPPORT
WITH THIS ACQUISITION AND FIX THE PRICE FOR SUPPORT FOR AN
ADDITIONAL 3 YEARS (ALL COSTS MUST BE IDENTIFIED).
2-3.13 (2.1) SUPPORT MUST BE AVAILABLE ON A 24 X 7 (TWENTY-FOUR (24)
HOURS A DAY, SEVEN (7) DAYS A WEEK) BASIS FOR BOTH
HARDWARE AND SOFTWARE SOLUTION(S). THE MAINTENANCE
PERIOD MUST BE IN ADDITION TO THE WARRANTY PERIOD.
SUPPORT AND MAINTENANCE MUST INCLUDE THE FOLLOWING:
2-3.13 (2.1.1) FIXED SUPPORT SERVICE COSTS FOR TERM OF AGREEMENT (5
YEARS),
2-3.13 (2.1.2) INCLUDE TRAVEL & PER DIEM,
2-3.13 (2.1.3) ON-SITE RESPONSE TIME OF FORTY-EIGHT (24) HOURS FROM
TIME OF REQUEST,
2-3.13 (2.1.4) CONTACT RESPONSE TIME OF FOUR (4) HOURS,
2-3.13 (2.1.5) AN ASSIGNED ENGINEER TO THE ACCOUNT,
2-3.13 (2.1.6) AUTOMATIC SOFTWARE UPDATES AND INSTALLATION,
2-3.13 (2.1.7) UNLIMITED TELEPHONE ACCESS TO SUPPORT
CENTER/ENGINEERS,
2-3.13 (2.1.8) AND SOFTWARE PROBLEM SOLVING AND USAGE ASSISTANCE.
2-3.14 SYSTEM TRAINING
2-3.14 (1) TRAINING IS IN ADDITION TO THE TRAINING PROVIDED DURING
THE 30 DAY SYSTEM ACCEPTANCE EVALUATION TRAINING AND
MUST BE PROVIDED JUST PRIOR TO FULL IMPLEMENTATION (GO
LIVE) OF EACH SOFTWARE MODULE PER AGENCY.
2-3.14 (2) VENDOR MUST PROVIDE BOTH TECHNICAL & SYSTEM OPERATIONS
TRAINING AND END-USER TRAINING.
2-3.14 (3) VENDOR MUST PROVIDE TRAINING SCHEDULE WITHIN
CONSTRAINTS OF PROJECT SCHEDULE.
2-3.14 (4) TRAINING MUST INCLUDE ALL PHASES OF SOFTWARE OPERATION,
DAILY MAINTENANCE, SYSTEM START-UP & SHUT-DOWN
PROCEDURES.
City of Fort Collins xxxvi Proposal P-847
2-3.14 (5) TRAINING MUST PROVIDE ADEQUATE KNOWLEDGE TRANSFER FOR
PARTICIPATING AGENCIES TO PROVIDE MANAGEMENT AND
SUPPORT OF SOFTWARE UPON PROJECT IMPLEMENTATION.
2-3.14 (6) VENDOR MUST PROVIDE COSTS AND DETAILS FOR EACH TRAINING
CLASS TO INCLUDE:
2-3.14 (6.1) EACH LEVEL OF TRAINING,
2-3.14 (6.2) FOR EACH LEVEL, EXPERIENCE LEVEL REQUIRED FOR PERSONS
BEING TRAINED,
2-3.14 (6.3) NUMBER OF INSTRUCTION HOURS/DAYS AND SESSIONS
REQUIRED FOR EACH LEVEL,
2-3.14 (6.4) DESCRIPTION OF CLASS CONTENT,
2-3.14 (6.5) CLASS SIZE FOR HANDS ON (MAX 10),
2-3.14 (6.6) CLASS SIZE FOR CLASSROOM ONLY (MAX 40 PERSONS),
2-3.14 (6.7) IDENTIFY INSTRUCTOR(S) SCHEDULED TO CONDUCT TRAINING,
2-3.14 (6.8) PROVIDE INSTRUCTOR QUALIFICATIONS,
2-3.14 (6.9) AND INCLUDE CONTRACTOR TRAVEL COSTS AND ALL
ASSOCIATED COSTS IN COST OF CLASS.
2-3.14 (7) ALL TRAINING PARTICIPANTS MUST BE SUPPLIED A COPY OF
TRAINING MATERIALS.
2-3.14 (8) TRAINING MATERIALS MUST BE CUSTOMIZED FOR THE
IMPLEMENTED SOLUTION (INCLUDING ALL CUSTOM INTERFACES).
2-3.14 (9) VENDOR MUST CONDUCT TRAINING CLASSES ON-SITE IN FT.
COLLINS (TRAINING LAB PROVIDED BY THE AGENCIES).
2-4 SYSTEM ADMINISTRATION
2-4.1 GENERAL SYSTEM SECURITY
2-4.1 (1) THE PROPOSED SYSTEM ADMINISTRATION INTERFACE SHALL BE A
GRAPHICAL APPLICATION.
2-4.1 (2) ALL LOOKUP TABLES, AGENCY DEFINED VALUES, CONFIGURATION
SETTINGS, ETC. ARE TO BE FULLY CONTROLLED AND MAINTAINED
BY THE PARTICIPATING AGENCIES SYSTEM ADMINISTRATORS, NOT
BY THE VENDOR’S PERSONNEL AT A COST FOR EACH CHANGE.
City of Fort Collins xxxvii Proposal P-847
2-4.1 (3) THE PROPOSED SYSTEM SHALL INCLUDE A SOPHISTICATED
SECURITY MODULE WHICH CONTROLS THE USER’S ABILITY TO:
2-4.1 (3.1) CREATE,
2-4.1 (3.2) READ,
2-4.1 (3.3) WRITE,
2-4.1 (3.4) MODIFY (EDIT),
2-4.1 (3.5) PRINT,
2-4.1 (3.6) DELETE,
2-4.1 (3.7) AND FILE SCAN,
2-4.1 (3.8) OR EMAIL REPORTS.
2-4.1 (4) THE ABOVE SECURITY MODULE CONTROLS SHALL APPLY TO ALL
OF THE VENDOR SUPPLIED:
2-4.1 (4.1) APPLICATIONS,
2-4.1 (4.2) FORMS,
2-4.1 (4.3) FIELDS,
2-4.1 (4.4) REPORTS,
2-4.1 (4.5) INTERFACES, AND
2-4.1 (4.6) OTHER INPUT OR OUTPUT MECHANISMS.
2-4.1 (5) THE PROPOSED APPLICATION SHALL PROVIDE SECURITY FOR
BOTH THE OPERATING SYSTEM AND DATABASE MANAGEMENT
SOFTWARE TO PREVENT UNAUTHORIZED PERSONS FROM
ACCESSING DATA BY CIRCUMVENTING THE APPLICATION.
2-4.1 (6) THE SYSTEM SHALL HAVE THE ABILITY FOR THE SYSTEM
ADMINISTRATOR TO DEFINE ANY DATABASE FIELD AS MANDATORY.
2-4.1 (7) THE SYSTEM SHALL BE ABLE TO “HIGHLIGHT” (OR OTHERWISE
INDICATE) ANY MANDATORY FIELDS WHEN ANY ENTRY FORM IS
OPENED.
2-4.1 (8) IF DATA IS NOT ENTERED IN THESE FIELDS, IT SHOULD
AUTOMATICALLY STAND OUT OR BE FLAGGED DURING THE
REVIEW PROCESS.
City of Fort Collins xxxviii Proposal P-847
2-4.1 (9) THE PROPOSED APPLICATION SHALL ALLOW THESE FIELDS TO BE
CUSTOMIZED TO USERS NEEDS TO ENSURE CERTAIN DATA IS BEING
CAPTURED.
2-4.1 (10) THE SYSTEM SHALL HAVE THE ABILITY TO PERFORM ALL
OPERATIONS, DEPENDANT ON OPERATOR SECURITY, AT ANY
CLIENT LOCATION, INCLUDING SIMULTANEOUS IDENTICAL
OPERATIONS AT ONE TIME.
2-4.1 (11) THE SYSTEM SHALL HAVE THE ABILITY TO LIMIT OPERATIONAL
CAPABILITIES BY THE PHYSICAL LOCATION OF THE CLIENT.
2-4.1 (12) IT IS PREFERRED THAT THE SYSTEM HAVE THE ABILITY TO DEFINE
SYSTEM ADMINISTRATORS WITH VARYING CAPABILITIES (MULTI-
LEVEL ADMINISTRATION).
2-4.1 (13) THE PROPOSED CAD/RMS/JMS APPLICATION MUST BE PERMISSION
BASED, ALLOWING THE SYSTEM ADMINISTRATOR OR OTHER
AUTHORIZED USER TO DEVELOP SECURITY PROFILES FOR GROUPS
OF LIKE USERS.
2-4.1 (14) THE PROPOSED SYSTEM SHALL ALLOW THE SYSTEM
ADMINISTRATOR OR OTHER AUTHORIZED USER TO ASSIGN ANY
NUMBER OF USERS TO A GIVEN SECURITY PROFILE.
2-4.1 (15) IT IS PREFERRED THAT THE PROPOSED CAD/RMS/JMS APPLICATION
ALLOW FOR DRAG AND DROP OF INDIVIDUALS INTO DIFFERENT
SECURITY PROFILES IF THEY CHANGE POSITIONS WITHIN THE
DEPARTMENT.
2-4.1 (16) THE PROPOSED SYSTEM SHALL ALLOW THE SYSTEM
ADMINISTRATOR OR OTHER AUTHORIZED USER TO ASSIGN A USER
TO MORE THAN ONE SECURITY PROFILE.
2-4.1 (17) THE PROPOSED SYSTEM SHALL ALLOW THE SYSTEM
ADMINISTRATOR OR OTHER AUTHORIZED USER TO RETRIEVE,
MODIFY AND SAVE A SECURITY PROFILE UNDER A NEW NAME.
2-4.1 (18) THE PROPOSED APPLICATION SHALL ALLOW FOR EACH
PARTICIPATING AGENCY JURISDICTION IN THE DATABASE THE
ABILITY TO DEFINE AND ALLOW DIFFERENT USERS, AGENCY
INFORMATION AND CONFIGURATION.
2-4.1 (19) THE PROPOSED SYSTEM SHALL REQUIRE USERS TO HAVE A VALID
SECURITY PROFILE, USER NAME AND PASSWORD ON FILE PRIOR TO
BEING ABLE TO LOGON TO AND USE ANY VENDOR SUPPLIED
APPLICATION.
City of Fort Collins xxxix Proposal P-847
2-4.1 (20) THE PROPOSED SYSTEM SHALL ALLOW USERS TO CHANGE THEIR
OWN PASSWORD AT ANY TIME.
2-4.1 (21) THE PROPOSED APPLICATION WILL MAINTAIN A COMPLETE AUDIT
TRAIL OF ALL USER ACTIONS INCLUDING:
2-4.1 (21.1) DATE AND TIME OF EACH USER LOGIN AND LOG OFF,
2-4.1 (21.2) CASE RECORDS OR FORMS ACCESSED, AND
2-4.1 (21.3) CRIME AND EVENT REPORTS PRINTED.
2-4.1 (21.4) THE SYSTEM ADMINISTRATOR OR AUTHORIZED USER SHALL
HAVE THE ABILITY TO CHOOSE WHETHER TO USE THIS FEATURE
ON A FUNCTION BASIS.
2-4.1 (21.5) THIS FUNCTION SHALL BE AVAILABLE FOR EXPORT FROM THE
LOG FILE.
2-4.1 (21.6) THE PROPOSED APPLICATION WILL MAINTAIN A COMPLETE
AUDIT TRAIL OF ALL CHANGES TO CAD RECORDS, DATABASE
RECORDS OR FORMS CHANGED, INCLUDING THE FOLLOWING
INFORMATION:
2-4.1 (21.7) IDENTIFICATION OF THE USER MAKING THE CHANGE,
2-4.1 (21.8) IDENTIFICATION OF THE RECORD BEING CHANGED,
2-4.1 (21.9) THE OLD AND NEW VALUE OF THE FIELD CHANGED, AND
2-4.1 (21.10) THE DATE, TIME AND LOCATION FROM WHICH THE CHANGES
WERE MADE.
2-4.1 (22) THE PROPOSED APPLICATION SHOULD ALLOW THE USER TO
SELECT WHAT IS DISPLAYED WHEN THE AUDIT TRAIL IS
DISPLAYED. FOR EXAMPLE, ONLY LOGONS AND LOGOFFS.
2-4.1 (23) THE PROPOSED APPLICATION SHALL AUTOMATICALLY PURGE THE
AUDIT TRAIL INFORMATION AFTER A PERIOD SET BY THE SYSTEM
ADMINISTRATOR.
2-4.2 CAD SPECIFIC SECURITY FUNCTIONS
2-4.2 (1) THE PROPOSED CAD APPLICATION SHALL INCLUDE A FUNCTION
FOR DEFINING WHICH INCIDENT TYPES AUTOMATICALLY
GENERATE A CASE (REPORT) NUMBER.
2-4.2 (2) AT THE APPLICATION LEVEL THE CAD SYSTEM SHALL SECURE
ACCESS TO THE FOLLOWING:
City of Fort Collins xl Proposal P-847
2-4.2 (2.1) CAD COMMANDS,
2-4.2 (2.2) FUNCTION OR HOT KEYS,
2-4.2 (2.3) AND INDIVIDUAL INTERFACES.
2-4.3 RMS/JMS SPECIFIC SECURITY FUNCTIONS
2-4.3 (1) THE PROPOSED RMS/JMS APPLICATION SHALL INCLUDE
AUTOMATED AND SEMI-AUTOMATED ROUTINES TO ASSIST THE
SYSTEM ADMINISTRATOR OR OTHER AUTHORIZED USER WITH
MANAGING THE INDEXES. THE PURPOSE OF THESE FEATURES
WILL BE TO ENSURE THAT INDEX ASSOCIATIONS ARE CORRECT
AND TO PREVENT, AS MUCH AS POSSIBLE, CASES FROM BEING
ASSOCIATED WITH THE WRONG ENTRY IN AN INDEX. FOR
EXAMPLE, THE PROPOSED APPLICATION SHALL BE ABLE TO
IDENTIFY WHEN A RECORD DOES NOT HAVE AN ASSOCIATED
MASTER INDEX ENTRY, OR IF A MASTER INDEX ENTRY HAS A
DUPLICATE RECORD.
2-4.3 (2) THE PROPOSED RMS APPLICATION SHALL ALLOW THE SYSTEM
ADMINISTRATOR OR OTHER AUTHORIZED USER TO DEFINE WHICH
FIELDS ARE MANDATORY BASED ON:
2-4.3 (2.1) THE EVENT,
2-4.3 (2.2) INCIDENT TYPE, OR
2-4.3 (2.3) OFFENSE TYPE
2-4.3 (3) THE PROPOSED JMS APPLICATION SHALL ALLOW THE SYSTEM
ADMINISTRATOR OR OTHER AUTHORIZED USER TO DEFINE WHICH
FIELDS ARE MANDATORY BASED ON BOOKING TYPE.
2-4.3 (4) THE PROPOSED APPLICATION SHALL PROVIDE THE SYSTEM
ADMINISTRATOR OR OTHER AUTHORIZED USER WITH A LOG
WHICH LISTS THE CAD RECORDS WHICH WERE TRANSFERRED TO
RMS AND IF THERE WERE ANY ERRORS IN THE TRANSFERS.
2-4.3 (5) THE PROPOSED RMS/JMS APPLICATION SHALL INCLUDE A TABLE
FOR CONVERTING STATE AND MUNICIPAL STATUTE CODES TO THE
APPROPRIATE IBRS CODE.
2-4.3 (6) THE PROPOSED RMS APPLICATION SHALL INCLUDE A
CONFIGURATION TABLE THAT ALLOWS THE SYSTEM
ADMINISTRATOR OR AUTHORIZED USER TO DETERMINE THE
ROUTING OF CASE REPORTS TO NAMED PERSONS, OR TO POSITION
TITLES BASED ON THE:
City of Fort Collins xli Proposal P-847
2-4.3 (6.1) OFFENSE TYPE, OR
2-4.3 (6.2) THE LOCATION OF THE OFFENSE, OR
2-4.3 (6.3) OFFICER ID.
2-4.3 (7) THE PROPOSED RMS APPLICATION SHALL INCLUDE A
CONFIGURATION TABLE THAT ALLOWS THE SYSTEM
ADMINISTRATOR OR OTHER AUTHORIZED USER TO DETERMINE
THE COPYING OF CASE REPORTS TO NAMED PERSONS, OR TO
POSITION TITLES BASED ON THE:
2-4.3 (7.1) OFFENSE TYPE, OR
2-4.3 (7.2) THE LOCATION OF THE OFFENSE.
2-4.3 (8) THE PROPOSED RMS APPLICATION SHALL ALLOW FOR
DISTRIBUTION TO NAMED PERSONS OR POSITION TITLES FOR
PRINTED REPORTS.
2-4.3 (9) THE PROPOSED RMS APPLICATION SHALL ALLOW THE SYSTEM
ADMINISTRATOR OR OTHER AUTHORIZED USER TO DEFINE
POSITION TITLES AND ASSOCIATE THEM WITH NAMED
INDIVIDUALS.
2-4.3 (10) THE PROPOSED RMS/JMS APPLICATION SHALL ALLOW THE SYSTEM
ADMINISTRATOR OR OTHER AUTHORIZED USER TO DEFINE THE
CHAIN OF COMMAND, I.E. WHO REPORTS TO WHOM, SO THAT
REPORTS CAN BE ROUTED TO THE CORRECT SUPERVISOR.
2-4.3 (11) THE PROPOSED RMS/JMS APPLICATION SHALL BE ABLE TO FLAG
OFFENSES INVOLVING JUVENILES BASED ON AGE AT TIME OF
OCCURRENCE VERSUS OFFENSES INVOLVING ADULTS.
2-4.3 (12) THE PROPOSED RMS/JMS APPLICATION SHALL HAVE THE ABILITY
TO EXPUNGE RECORDS FROM THE DATABASE. WHEN RECORDS
ARE EXPUNGED, THEY SHALL NO LONGER BE RETRIEVABLE BY
THE NAME ASSOCIATED WITH THE EXPUNGED RECORD.
HOWEVER, THEY MUST STILL BE ACCESSIBLE FOR LAW
ENFORCEMENT PURPOSES.
2-4.3 (13) THE PROPOSED RMS APPLICATION SHALL RECORD THE DATE,
TIME, AND USER ID FOR ALL REPORT HOLDS AND RELEASES.
2-4.3 (14) THE PROPOSED RMS APPLICATION SHALL ALLOW THE
INVESTIGATOR ASSIGNED TO A CASE OR HIS/HER SUPERVISOR TO
LIMIT ACCESS TO A SELECTED INVESTIGATION TO NAMED
INDIVIDUALS.
City of Fort Collins xlii Proposal P-847
2-4.3 (15) THE PROPOSED RMS APPLICATION SHALL INCLUDE THE ABILITY
TO CLASSIFY CASES (E.G. SPECIAL, SEXUAL VIOLENCE OR
NARCOTICS).
2-4.3 (15.1) THE PROPOSED RMS APPLICATION SHALL ALLOW THE SYSTEM
ADMINISTRATOR TO DETERMINE ACCESS TO FOR EACH CASE
CLASSIFICATION.
2-4.4 PERSONNEL MODULE SPECIFIC SECURITY FUNCTIONS
2-4.4 (1) THE PROPOSED APPLICATION SHALL PROVIDE SUFFICIENT
SECURITY TO PREVENT EMPLOYEE RECORDS FROM BEING VIEWED
BY ANYONE OTHER THAN THE EMPLOYEE OR APPROPRIATE
SUPERVISORY OR MANAGERIAL EMPLOYEES.
2-5 SYSTEM INTERFACE SPECIFICATIONS
Prices must include costs for the following interfaces. Interface prices should detail any
known expenses that you will expect the participating agencies to meet, including costs
with other vendors, communication line costs, etc. All costing must be broken out by
interface with the specific understanding that the participating agencies may accept or
reject having the vendor complete each interface on a case by case basis.
2-5.1 GENERAL REQUIREMENTS
2-5.1 (1) IN THE EVENT THAT AN INTERFACED SYSTEM TO WHICH THE
CAD/RMS/JMS IS CONNECTED TO BECOMES UNAVAILABLE, THE
CAD/RMS/JMS SHALL NOTIFY THE LOGGED ON USERS AND SYSTEM
ADMINISTRATOR OR OTHER AUTHORIZED USER THAT THE
INTERFACED SYSTEM IS FAILING TO RESPOND.
2-5.1 (1.1) IN THE EVENT THAT A USER LOGS ONTO THE SYSTEM AFTER THE
NOTIFICATION OF FAILURE HAS BEEN SENT, AND THAT USER
THEN ATTEMPTS TO USE THE FAILED INTERFACE, THE SYSTEM
SHALL CLEARLY RESPOND TO THAT USER WITH THE
NOTIFICATION OF FAILURE.
2-5.1 (1.2) PRIOR TO TRANSMITTING ANY ADDITIONAL INQUIRIES TO THE
REMOTE SYSTEM THE CAD/RMS/JMS APPLICATIONS SHALL
MAKE PERIODIC ATTEMPTS TO REESTABLISH
COMMUNICATIONS, AND WHEN SUCCESSFUL, NOTIFY THE
LOGGED ON USERS THAT THE INTERFACE IS WORKING AGAIN.
2-5.1 (1.3) IN THE EVENT THAT ANY TRANSACTIONS WERE SUBMITTED BUT
NOT COMPLETED PRIOR TO THE FAILURE OF A REMOTE SYSTEM,
THE SYSTEM SHALL COMPLETE THE INQUIRIES ONCE THE
REMOTE SYSTEM RESUMES OPERATION.
City of Fort Collins xliii Proposal P-847
2-5.2 COMPUTER AIDED DISPATCH
Because it is highly desired for the successful RMS/JMS vendor to also be the vendor
for a new CAD system for all participating agencies there will probably be no need for
any CAD interface. However the vendor must provide separate costing for each of two
possible scenarios:
1. All participating agencies will use the CAD system provided by the same vendor as
RMS/JMS.
2. All participating vendors will use a CAD system provided by another vendor.
In all cases the proposed RMS/JMS must be able to receive electronically transferred
call related information from the CAD system(s) used by all participating agencies to
start the case reporting or booking process within the vendors RMS/JMS.
2-5.3 E911 INTERFACE
2-5.3 (1) ****CRITICAL FUNCTIONALITY**** THE PROPOSED APPLICATION
SHALL BE APCO PHASE II WIRELESS COMPLIANT.
2-5.3 (2) THE PROPOSED APPLICATION SHALL BE INTERFACED WITH PLANT
EQUIPMENT VESTA 911 CONTROLLERS AT SEVERAL AGENCIES. AT
A MINIMUM THE INTERFACE SHALL SUPPORT THE FOLLOWING
FEATURES:
2-5.3 (2.1) THE CAD SYSTEM SHALL BE ABLE TO RECEIVE ANI/ALI
INFORMATION DIRECTLY FROM THE 911 CONTROLLER,
TRANSFER IT TO THE CAD POSITION WHICH IS HANDLING THE
VOICE CALL ASSOCIATED WITH THE ANI/ALI RECORD, AND
INSERT THE DATA IN THE APPROPRIATE FIELDS ON THE NEW
CALL FORM.
2-5.3 (2.2) THE CAD SHALL BE ABLE TO RECEIVE AND INCLUDE IN EACH
CALL RECORD THE TIME THAT THE CALL TAKER RECEIVED THE
911 CALL.
2-5.4 ProQA INTERFACE
2-5.4 (1) ****CRITICAL FUNCTIONALITY**** THE PROPOSED APPLICATION
SHALL PROVIDE AN INTERFACE FOR MEDICAL PRIORITY DISPATCH
PROQA SOFTWARE.
2-5.4 (1.1) WHEN A MEDICAL CALL IS RECEIVED, THE DISPATCHER SHALL
BE ABLE TO ACCESS THIS SOFTWARE WITH ONE KEY OR
KEYSTROKE COMBINATION.
City of Fort Collins xliv Proposal P-847
2-5.4 (1.2) ALL PERTINENT INFORMATION INCLUDING TIMES SHALL BE
AUTOMATICALLY TRANSFERRED FROM THE PROQA SOFTWARE
TO THE INCIDENT AUDIT TRAIL
2-5.4 (1.3) THE TRANSFER OF THIS INFORMATION SHALL BE DONE SO THE
INFORMATION IS EASILY DECIPHERABLE BY FIELD UNITS
UTILIZING MOBILE TERMINALS.
2-5.4 (1.4) THE APPLICATION SHALL ALLOW PROQA TO BE ACCESSIBLE AS
A STAND-ALONE PROGRAM SHOULD THE CAD APPLICATION
CRASH FOR ANY REASON.
2-5.5 TDD INTERFACE
2-5.5 (1) THE PROPOSED APPLICATION SHALL BE INTERFACED WITH PLANT
EQUIPMENT VESTA PHONE SYSTEM AT SEVERAL AGENCIES SO AS
TO SUPPORT FULL TDD CAPABILITIES ON THE CAD CLIENT. AT A
MINIMUM THE INTERFACE SHALL SUPPORT THE FOLLOWING
FEATURES:
2-5.5 (1.1) TRANSFER A TDD CALL THAT WAS INITIATED ON THE VESTA
CONSOLE TO THE CAD CLIENT,
2-5.5 (1.2) ALLOW FOR FULL TWO WAY COMMUNICATION WITH THE TDD
CALLER USING THE KEYBOARD THAT DRIVES THE CAD CLIENT,
2-5.5 (1.3) PROVIDE WITH A POP UP WINDOW ON THE CAD CLIENT
COMPUTER TO DISPLAY THE CONVERSATION THAT CAN BE
POSITIONED AND SIZED AT THE DISPATCHER’S DISCRETION,
2-5.5 (1.4) AND RECORD BOTH INCOMING AND OUTGOING TEXT IN THE
AUDIT TRAIL OF THE CAD SYSTEM.
2-5.6 MASTER TIMING SOURCE
2-5.6 (1) THE PROPOSED SYSTEM SHALL RECEIVE AND INCORPORATE A
MASTER TIMING SIGNAL FROM THE SPECTRACOM NETCLOCK II
MASTER TIMING DEVICE THAT IS USED BY MOST OF THE
PARTICIPATING AGENCIES SUCH THAT THE TIMES RECORDED BY
ALL APPLICATIONS DO NOT DIFFER FROM THOSE FOUND ON ANY
OTHER SYSTEM CONNECTED TO THE MASTER TIMING SOURCE.
2-5.7 CCIC/NCIC INTERFACE
This is the interface to the state criminal computer system. The interface must provide
for a mechanism to most functions of the CCIC system through the same user client that
is used for CAD/RMS/JMS.
City of Fort Collins xlv Proposal P-847
2-5.7 (1) THE PROPOSED SYSTEM SHALL INCLUDE AN INTERFACE TO THE
COLORADO CRIME INFORMATION CENTER AND THE NATIONAL
CRIME INFORMATION CENTER (CCIC/NCIC).
2-5.7 (2) THE PROPOSED APPLICATION SHALL CONFORM TO THE
COLORADO BUREAU OF INVESTIGATION’S REQUIREMENTS FOR
EXCHANGING DATA BETWEEN THE VENDOR’S SYSTEM AND THE
CCIC.
2-5.7 (3) THE PROPOSED APPLICATION SHALL COMMUNICATE TO THE
COLORADO BUREAU OF INVESTIGATION BY UTILIZING THE
MODERN NETWORK INFRASTRUCTURE PROVIDED BE THE CBI TO
THE PARTICIPATING AGENCIES USING TCP/IP COMMUNICATION
PROTOCOLS.
2-5.7 (4) THE PROPOSED APPLICATION SHALL CONFORM TO NCIC 2000
SYSTEM STANDARDS.
2-5.7 (5) THE PROPOSED SYSTEM SHALL INCLUDE A MESSAGE SWITCHING
FUNCTION SUCH THAT WHEN A DESKTOP OR MOBILE USER
SUBMITS AN INQUIRY TO RMS/JMS WHICH IS ALSO SUPPORTED BY
CCIC/NCIC, THE SYSTEM CAN (AT THE PARTICIPATING AGENCIES
DISCRETION) AUTOMATICALLY INITIATE AND TRANSMIT THAT
INQUIRY TO CCIC/NCIC
2-5.7 (6) THE PROPOSED SYSTEM SHALL ALLOW AUTHORIZED USERS OF
ANY APPLICATION OR MODULE TO INITIATE AND COMPLETE ANY
CCIC/NCIC SUPPORTED INQUIRY, UPDATE OR MESSAGE.
2-5.7 (7) AT A MINIMUM THE PROPOSED SYSTEM SHALL PROVIDE ACCESS
TO THE FOLLOWING CCIC/NCIC INQUIRIES VIA A FORM FOR ALL
USERS AND ADDITIONALLY FROM THE COMMAND LINE FOR CAD
USERS:
2-5.7 (7.1) GENERATE HIT CONFIRMATION,
2-5.7 (7.2) ENTER/MODIFY/CANCEL/LOCATE VEHICLE,
2-5.7 (7.3) ENTER/MODIFY/CANCEL/LOCATE MISSING PERSON,
2-5.7 (7.4) ENTER/MODIFY/CANCEL/LOCATE WARRANT,
2-5.7 (7.5) ENTER/MODIFY/CANCEL/CLEAR/LOCATE SEX OFFENDER,
2-5.7 (7.6) QUERY CRIMINAL HISTORY,
2-5.7 (7.7) QUERY RAP SHEET,
City of Fort Collins xlvi Proposal P-847
2-5.7 (7.8) ENTER/MODIFY/CANCEL/LOCATE ARTICLES,
2-5.7 (7.9) ENTER/MODIFY/CANCEL/LOCATE GUNS,
2-5.7 (7.10) TID QUERY,
2-5.7 (7.11) QUERY DRIVER’S HISTORY,
2-5.7 (7.12) DRIVER LICENSE QUERY,
2-5.7 (7.13) BOLO FORM,
2-5.7 (7.14) QUERY QUERY,
2-5.7 (7.15) QUERY DRIVER ALPHA,
2-5.7 (7.16) QUERY SOCIAL SECURITY NUMBERS.
2-5.7 (8) THE PROPOSED SYSTEM SHALL AUTOMATICALLY ROUTE
INFORMATION ENTERED INTO A CCIC/NCIC INQUIRY OR UPDATE
FORM TO CCIC/NCIC IN A FORMAT ACCEPTABLE TO CCIC/NCIC.
2-5.7 (9) THE CCIC/NCIC INTERFACE SHALL MAINTAIN A LOG OF ALL
INQUIRIES, UPDATES, AND MESSAGES SENT TO CCIC/NCIC VIA THE
INTERFACE.
2-5.7 (10) THE CCIC/NCIC INTERFACE SHALL MAINTAIN A LOG OF ALL
RESPONSE TO INQUIRIES, UPDATES, AND MESSAGES SENT TO
CCIC/NCIC VIA THE INTERFACE.
2-5.7 (11) THE PROPOSED CCIC/NCIC INTERFACE SHALL ALLOW A USER TO
SEARCH PREVIOUS CCIC/NCIC INQUIRIES RECORDS AT A LATER
DATE WITH THE FOLLOWING SEARCH KEYS:
2-5.7 (11.1) VEHICLE LICENSE PLATE NUMBER,
2-5.7 (11.2) BOAT REGISTRATION NUMBER,
2-5.7 (11.3) SUBJECT NAME OR ALIAS, RACE, GENDER AND DATE OF BIRTH,
2-5.7 (11.4) SUBJECT SOCIAL SECURITY NUMBER,
2-5.7 (11.5) GUN SERIAL NUMBER AND MANUFACTURER,
2-5.7 (11.6) ARTICLE SERIAL NUMBER AND MANUFACTURER,
2-5.7 (11.7) VEHICLE IDENTIFICATION NUMBERS,
2-5.7 (11.8) AND OPERATOR LICENSE NUMBER.
City of Fort Collins xlvii Proposal P-847
2-5.7 (12) IN ADDITION TO THE ABOVE IT WOULD BE PREFERRED THAT THE
PROPOSED CCIC/NCIC INTERFACE WILL ALLOW A USER TO SEARCH
PREVIOUS CCIC/NCIC INQUIRIES RECORDS AT A LATER DATE WITH
THE FOLLOWING SEARCH KEYS:
2-5.7 (12.1) DATE OF INQUIRY,
2-5.7 (12.2) TIME RANGE,
2-5.7 (12.3) INITIATING OFFICER,
2-5.7 (12.4) OR INITIATING UNIT NUMBER,
2-5.7 (12.5) INITIATING AGENCY.
2-5.7 (13) THE PROPOSED APPLICATION SHALL ALLOW FOR NO FEWER THAN
EIGHT PRE-DEFINED RESPONSE FORMS. THESE FORMS ARE FOR
RESPONDING TO ANOTHER AGENCIES QUERY ON
WANTS/WARRANTS OR STOLEN ITEMS ETC.
2-5.8 SUNPRO FIRE RECORDS MANGEMENT SYSTEM
2-5.8 (1) THE VENDOR SHALL SUPPLY AN INTERFACE TO THE EXISTING
POUDRE FIRE AUTHORITY SUNPRO RMS WHICH PROVIDES THE
FOLLOWING CAPABILITIES:
2-5.8 (1.1) TRANSFER OF ALL CAD INCIDENT INFORMATION THAT IS
REQUIRED BY THE SUNPRO RMS.
2-5.9 TONING/PAGER INTERFACES
The CAD/RMS/JMS system must be interfaced to a number of toning/paging systems
and services. Most notably the Zetron model 25 and 26 Fire Station toners used by the
PFA, and the Zetron model 2200 paging terminal used by Larimer County.
2-5.9 (1) THE PROPOSED SYSTEM SHALL INCORPORATE AN INTERFACE TO
THE ZETRON MODEL 25 AND 26 FIRE STATION TONERS USED BY THE
PFA. THE INTERFACE SHOULD UTILIZE ALL AVAILABLE FEATURES
OF THESE SYSTEMS PROVIDE.
2-5.9 (2) THE PROPOSED SYSTEM SHALL INCORPORATE AN INTERFACE TO
THE ZETRON MODEL 2200 PAGING TERMINAL USED BY LARIMER
COUNTY. THE INTERFACE SHOULD UTILIZE ALL AVAILABLE
FEATURES OF THIS SYSTEM PROVIDES.
2-5.9 (3) THE PROPOSED SYSTEM SHALL INCORPORATE AN INTERFACE TO
COMMERCIAL PAGING SYSTEMS SUCH AS METROCALL, AT&T, PAGE
ONE, NEXTEL, ETC.
City of Fort Collins xlviii Proposal P-847
2-5.9 (3.1) IT IS EXPECTED THAT THE VENDOR WILL IDENTIFY PAGING
COMPANIES IN USE BY THE PARTICIPATING AGENCIES TO
ENSURE THAT ALL DESIRED INTERFACES ARE ACCOMPLISHED
(THE VENDOR CAN ASSUME FOUR INTERFACES FOR RFP
COSTING).
2-5.9 (3.2) THESE INTERFACES MUST BE FULLY ACHIEVED BY THE VENDOR
WITHOUT THE PARTICIPATING AGENCIES INVOLVEMENT
(BEYOND A LETTER OF REQUEST).
2-5.9 (3.3) IT IS EXPECTED THAT THE VENDOR WILL IDENTIFY ALL
RESOURCES, COSTS (INSTALLATION AND ONGOING) AND
NECESSARY AGREEMENTS TO ACHIEVE THESE INTERFACES.
2-5.10 COLORADO IBRS AND NIBRS
2-5.10 (1) THE PROPOSED SYSTEM MUST BE ABLE TO INTERFACE TO THE CBI
IN SUCH A WAY THAT THE DATA REQUIRED BY THE STATE TO
SATISFY THE STATISTICAL REPORTING NEED OF THE COLORADO
IBRS PROGRAM AND NATIONAL INCIDENT BASED REPORTING
SYSTEM (NIBRS) ARE SATISFIED WITHOUT ONGOING
INTERVENTION BY THE SYSTEM ADMINISTRATORS.
2-5.11 DOCUMENT IMAGING (FCPS AND LCSO)
The City of Ft. Collins standard electronic document management software (EDMS)
system is SIRE File Center and SIRE Capture from AlphaCorp (www.alphacorp.cc).
This system is planned for deployment in the Police Department on July 1, 2002.
The county has designated that the standard electronic document management software
(EDMS) to be utilized countywide is FileNET’s Content Services 5.2, eProcess Service
3.2, and Workflo 4.2 (utilizing SQL Server 2000) with Kofax Ascent Capture 5.5
software. The implementation of the system at the Sheriff’s office will begin prior to
the implementation of the CAD/RMS/JMS.
The proposer is expected to utilize and interface with these EDMS systems for the
management of images and documents captured as part of the CAD/RMS/JMS.
2-5.11 (1) THE PROPOSED APPLICATION SHALL USE FILENET CONTENT
SERVICES FOR THE COUNTY SHERIFF TO MANAGE GRAPHICAL
IMAGES SUCH AS FLOOR PLANS, AERIAL PHOTOGRAPHS, AND
DIAGRAMS.
2-5.11 (2) THE PROPOSED APPLICATION SHALL USE ALPHACORP'S SIRE FOR
THE CITY POLICE DEPARTMENT TO MANAGE GRAPHICAL IMAGES
SUCH AS FLOOR PLANS, AERIAL PHOTOGRAPHS, AND DIAGRAMS.
City of Fort Collins xlix Proposal P-847
2-5.11 (3) THE PROPOSED APPLICATION SHALL PROVIDE SEARCH,
RETRIEVAL AND DISPLAY OF IMAGES, REGARDLESS OF THEIR
LOCATION (FILENET OR SIRE), TO ALLOW SHARING OF IMAGES
BETWEEN ORGANIZATIONS. DESCRIBE THE PROPOSED METHOD
FOR ACCOMPLISHING THIS REQUIREMENT.
2-5.11 (4) IT IS PREFERRED THAT THE PROPOSED APPLICATION NOT REQUIRE
A SEPARATE LOGON TO ACCESS IMAGES IN EITHER IMAGING
SYSTEM.
2-5.11 (5) THE CAD/RMS/JMS SHALL ALLOW THE PROPOSED APPLICATION TO
PROVIDE THE DIRECT RETRIEVAL OF ANY ASSOCIATED IMAGES
FROM A RECORD THAT IS CURRENTLY VIEWED (E.G. INCIDENT
REPORT) RATHER THAN PERFORMING A SEPARATE SEARCH FOR
THE IMAGE.
2-5.11 (6) IT IS PREFERRED THAT THE INTERFACE TO THE GRAPHICAL
IMAGING SYSTEM FACILITATE THE USE OF THE GRAPHICAL
IMAGES BY BOTH OCCASIONAL USERS OF TECHNOLOGY AND
USERS IN HIGH STRESS ENVIRONMENTS. AS SUCH THE PROPOSED
APPLICATION SHALL BE EASY TO USE, READILY ACCESSIBLE,
OFFER PANNING AND ZOOMING CONTROLS, AND ALLOW FOR A
SIMPLE METHOD OF DETERMINING WHETHER A GRAPHIC EXISTS
FOR A PARTICULAR ADDRESS OR AREA. SPECIFY WHETHER THE
NATIVE FILENET AND SIRE VIEWERS WILL BE USED.
2-5.11 (6.1) IT IS PREFERRED THAT THE APPLICATION INTERFACE WITH THE
GIS DATABASE TO MAKE ALL IMAGES ACCESSIBLE FROM THE
MAPPING APPLICATION ON A PER-BUILDING/STRUCTURE BASIS.
2-5.11 (7) SPECIFY THE METHOD OF IMAGE CAPTURE. IT IS PREFERRED
THAT THE ORGANIZATIONS UTILIZE THEIR CURRENT CAPTURE
SOFTWARE (KOFAX ASCENT CAPTURE AT THE COUNTY SHERIFF
AND SIRE CAPTURE AT THE CITY POLICE DEPARTMENT).
2-5.11 (7.1) IT IS PREFERRED THAT THE CAPTURE SOFTWARE PROPOSED FOR
THE COUNTY SHERIFF SUPPORTS KODAK VRS (VIRTUAL RESCAN)
TECHNOLOGY.
2-5.11 (7.2) THE PROPOSED CAPTURE APPLICATION SHALL POPULATE INDEX
INFORMATION IN BOTH THE IMAGING SYSTEMS AND THE
CAD/RMS/JMS SYSTEM TO ELIMINATE REDUNDANT DATA ENTRY.
2-5.11 (7.3) SYSTEM MUST WRITE THE FOLLOWING IMAGING INDEX VALUES
TO THE IMAGING SYSTEM (FILENET CONTENT SERVICES OR
ALPHACORP'S SIRE) AT A MINIMUM:
2-5.11 (7.3.1) CAD INCIDENT NUMBER,
City of Fort Collins l Proposal P-847
2-5.11 (7.3.2) CASE (REPORT) NUMBER,
2-5.11 (7.3.3) ARREST/BOOKING NUMBER,
2-5.11 (7.3.4) POINT COORDINATE INFORMATION (X-Y) (REQUIRES FUZZY
LOGIC),
2-5.11 (7.3.5) MNI NUMBER,
2-5.11 (7.3.6) MLI NUMBER,
2-5.11 (7.3.7) MVI NUMBER,
2-5.11 (7.3.8) AND MPI NUMBER.
2-5.11 (7.4) IF VENDOR WILL USE A CAPTURE SYSTEM OTHER THAN THE
IMAGE SYSTEM MANUFACTURER’S CAPTURE SOFTWARE THE
PROPOSED CAPTURE APPLICATION MUST SUPPORT DOCUMENT
SCANNERS INCLUDING FLATBED, AUTOMATIC FEED, AND HIGH-
SPEED DUPLEX SCANNERS FROM MULTIPLE MANUFACTURERS.
2-5.11 (7.5) IMAGE QC MUST INCLUDE VISUAL VERIFICATION OF EACH PAGE
OF EACH DOCUMENT IMAGE. OPERATOR SHOULD BE ABLE TO
CHOOSE HOW THE IMAGES ARE DISPLAYED (I.E., ONE IMAGE PER
SCREEN, OR MULTIPLE THUMBNAILS TO BROWSE THROUGH).
2-5.11 (7.6) SCANNING CONTROLS MUST BE ACCESSIBLE TO OPERATORS
THROUGH THE APPLICATION SOFTWARE FOR ANY MANUAL
ADJUSTMENTS THAT MAY BE NECESSARY, SUCH AS DESKEW,
DESPECKLE, REMOVAL OF BORDERS, CONTRAST, BRIGHTNESS,
ETC.
2-5.11 (7.7) THE PROPOSED CAPTURE APPLICATION MUST PROVIDE ABILITY
TO DELETE, RE-SCAN AND REPLACE POOR QUALITY IMAGES AND
MISSING PAGES.
2-5.11 (7.8) THE PROPOSED CAPTURE APPLICATION MUST PROVIDE ABILITY
TO READ BAR CODES.
2-5.11 (7.9) IT IS PREFERRED THAT THE PROPOSED CAPTURE APPLICATION
PROVIDE OPTICAL AND INTELLIGENT CHARACTER
RECOGNITION (OCR/ICR) CAPABILITIES.
2-5.12 MUNICIPAL COURT SYSTEM INTERFACE
2-5.12 (1) THE VENDOR SHALL SUPPLY AN INTERFACE TO THE EXISTING CITY
OF FORT COLLINS, JUSTICE SYSTEMS COURT RECORDS SYSTEM
WHICH PROVIDES THE FOLLOWING CAPABILITIES:
City of Fort Collins li Proposal P-847
2-5.12 (1.1) TRANSFER CITATION INFORMATION WHICH HAS BEEN ENTERED
INTO THE RMS TO THE FULL COURT SYSTEM.
2-5.12 (1.2) ACCEPT THE TRANSFER OF CITATION INFORMATION WHICH HAS
BEEN ENTERED INTO THE FULL COURT SYSTEM AND STORE IT IN
THE APPROPRIATE FIELDS IN THE PROPOSED RMS APPLICATION.
2-5.12 (1.3) ACCEPT THE TRANSFER OF CASE DISPOSITION INFORMATION
WHICH HAS BEEN ENTERED INTO THE COURT SYSTEM AND
STORE IT IN THE APPROPRIATE FIELDS IN THE PROPOSED RMS
APPLICATION.
2-5.12 (1.4) ACCEPT THE TRANSFER OF WARRANT INFORMATION WHICH HAS
BEEN ENTERED INTO THE COURT SYSTEM AND STORE IT IN THE
APPROPRIATE FIELDS IN THE PROPOSED RMS APPLICATION.
2-5.13 VOICE
The Victim/Offender Information, Computer Enhancement (VOICE) system is a system
to keep victims of crime informed about their case. VOICE automatically notifies
victims by telephone and email about court dates, parole hearings, escapes, releases or
other important activity on their case. This system was implemented for the State of
Colorado by the County Sheriff’s of Colorado Inc.
This new interface is intended to support the VOICE system in whole and the Criminal
Records Information System of Colorado (CRISCO) specifically. The intent of this
interface is to automatically send the offender and victim information requested by the
CRISCO from the jail management system. The information concerning the export
requirements the CRISCO is on the web at http://asgnet2.psc.sc.edu/voice/.
In addition it is the intent of the participating agencies to define another new interface
to the VOICE system to automatically upload victim information from the victim’s
response module of the RMS. This will be a challenging interface as it has never been
accomplished before, and will require significant coordination with the VOICE
development team to create.
2-5.13 (1) THE PROPOSED RMS/JMS SYSTEM SHALL FULLY SUPPORT THE
REPORTING REQUIREMENTS OF THE VOICE SYSTEM AS THEY
RELATE TO THE COLLECTION AND DISSEMINATION OF DATA VIA
AN INTERFACE TO THE CRISCO.
2-5.13 (2) IT IS DESIRED THAT THE PROPOSED RMS/JMS FULLY SUPPORT A
NEW INTERFACE TO THE VOICE SYSTEM FOR THE REPORTING OF
VICTIM INFORMATION AS TRACKED BY THE VOICE SYSTEM. IT IS
ANTICIPATED THAT THIS INTERFACE WILL PROVIDE VICTIM
INFORMATION TO VOICE FROM THE VICTIM’S RESPONSE
INFORMATION MODULE OF THE RMS.
City of Fort Collins lii Proposal P-847
2-5.14 LIVESCAN
DBI Fingerprint System: This is the system that sends fingerprint and demographic
data to the state AFIS system. Larimer County has two DBI systems, one located in the
booking area, and one in the administration building, both of which currently receive
correctly formatted demographic data from the county mainframe via a FTP push to
each DBI system. This is a common interface in the industry and Larimer County
Sheriff’s Office requires the successful vendor to connect in a similar manner unitizing
the existing county WAN.
2-5.14 (1) THE PROPOSED SYSTEM SHALL INCLUDE AN INTERFACE TO THE
DBI FINGERPRINT SYSTEM.
2-5.14 (2) ANY DBI DEMOGRAPHIC FIELDS THAT ALSO EXIST IN RMS/JMS
MUST BE AVAILABLE FOR TRANSFER VIA THIS INTERFACE.
2-5.14 (3) IF MORE THAN THREE CHARGES EXIST FOR AN INDIVIDUAL THE
RMS/JMS MUST SEND THE THREE MOST SERIOUS CHARGES BASED
ON CHARGE TYPE AND CLASS OF CRIME.
2-5.15 CERTEX
2-5.15 (1) THE CERTEX SYSTEM IS A CHECK WRITING SYSTEM USED BY THE
DETENTION CENTER TO ISSUE ALL INMATE CHECKS. THE RMS/JMS
MUST BE ABLE TO SEND CHECK DATA (CHECK NUMBER, DATE,
NAME, AMOUNTS) TO THE CERTEX SOFTWARE.
2-5.16 COMMISSARY
2-5.16 (1) SWANSON COMMISSARY SYSTEM: THIS IS THE CURRENT PROVIDER
FOR JAIL COMMISSARY. THE JMS MUST PROVIDE A MECHANISM
FOR TRANSFERRING ORDERS ELECTRONICALLY TO THIS VENDOR.
2-5.16 (2) THE CURRENT SYSTEM ALLOWS FOR ENCUMBRANCE OF INMATE
MONIES AT THE TIME THE ORDER IS PLACED. THERE IS A 24 HOUR
DELAY FROM ORDER UNTIL DELIVERY. DUE TO ITEMS SOMETIMES
NOT BEING DELIVERED, INMATE CREDITS ARE CREATED. THERE
MUST BE A MECHANISM FOR ELECTRONICALLY PROCESSING
THESE CREDITS.
2-6 DATABASE CONVERSION SPECIFICATIONS
Prices must include costs for the following database conversions. Conversion prices
should detail any known expenses that you will expect the participating agencies to meet
including costs with other vendors. All costing must be broken out by requested
conversion with the specific understanding that the participating agencies may accept or
reject having the vendor complete each conversion on a case by case basis.
City of Fort Collins liii Proposal P-847
2-6.1 CAD DATA (PECC AND LCSO)
Import of basic CAD configuration (street alias, intersection alias, common place,
incident & disposition code, etc.) and premise history/hazard files.
2-6.2 RMS DATA (FORT COLLINS POLICE SERVICES)
This data currently resides in a PRC Tri-Fox version 5.5. relational database running on
Oracle version6.4. There is approximately 8 gigabytes of data stored across multiple
files. These are relational files with the indices linking the various files created and
maintained by the application. This data must be inserted into the new database. City
of Fort Collins IMS staff will unload the database files into flat, ASCII files, delimited
or not, to the vendor upon receipt of an entity relation diagram, table layout, and data
dictionary. City of Fort Collins IMS staff will format the ASCII files to correspond to
the vendor’s database table requirements. FCPS will predetermine the data to be
converted from the existing system. City of Fort Collins IMS will work with the vendor
to resolve data migration problems, to describe current data relationships, and to
mitigate any data conversion problems.
2-6.3 RMS/JMS DATA (LARIMER COUNTY SHERIFF’S OFFICE)
This data currently resides in a Unisys DMS 1100 hierarchical database running on a
Unisys 2200/500 mainframe. There is approximately 12 gigabytes of data stored across
numerous files. These are database files with the indices linking the various files
created and maintained by the application. This data must be inserted into the proposed
database. Larimer County IMS staff will unload the database files into flat, ASCII files,
delimited or not, to the vendor upon receipt of an entity relation diagram, table layout,
and data dictionary. Larimer County IMS staff will format the ASCII files to
correspond to the vendor’s database table requirements. LCSO will predetermine the
data to be converted from the existing system. Larimer County IMS will work with the
vendor to resolve data migration problems, to describe current data relationships, and to
mitigate any data conversion problems.
2-6.4 MUGSHOT DATA
This data currently resides in a Printrak mugshot system, although all data is replicated
real time to a Microsoft SQL Server database. A common index to the master name
record exists and would be availible for the conversion process. There is approximately
150,000 pictures in the database that is inclusive of all bookings by all participating
agencies.
2-7 DATA SEARCH SPECIFICATIONS
2-7.1 SEARCHES AND INQUIRIES
2-7.1 (1) THE FOLLOWING SEARCH FUNCTIONS MUST BE SUPPORTED BY
THE CAD/RMS/JMS APPLICATION:
City of Fort Collins liv Proposal P-847
2-7.1 (2) SEARCH FOR STRING, AND USE OF WILDCARDS,
2-7.1 (3) SEARCH CAPABILITY FOR ALL FORMATTED FIELDS,
2-7.1 (4) SEARCH CAPABILITY FOR ALL TEXT FIELDS (INCLUDING ALL
ORIGINAL AND SUPPLEMENTAL NARRATIVES),
2-7.1 (5) BOOLEAN VALUES SUPPORTED (SEPARATELY OR IN COMBINATION),
2-7.1 (6) AND MOBILE SEARCH CAPABILITIES (INCLUDING MUGSHOT TO
THE CAR).
2-7.1 (7) THE PROPOSED RMS/JMS APPLICATION SHALL INCLUDE A MASTER
INDEX INQUIRY (MNI, MLI, MVI, & MPI) FOR ALL APPLICATIONS
ALLOWING FOR IDENTIFICATION AND RETRIEVAL OF RELATED
RECORDS, SUCH AS INCIDENTS, CASE REPORTS, CITATIONS,
BOOKINGS, PROPERTY, ETC.
2-7.1 (8) THE PROPOSED RMS/JMS APPLICATION SHALL INCLUDE A
FUNCTION WHEREBY SEARCHES DEFAULT TO SYSTEM WIDE
SEARCH OR TO THE AGENCY LOGGED ON TO THE SYSTEM, AT
EACH PARTICIPATING AGENCIES DISCRETION.
2-7.1 (8.1) REGARDLESS OF SEARCH DEFAULT THE SYSTEM SHALL BE
CAPABLE OF BEING EASILY CHANGED TO SEARCH A SPECIFIC
AGENCY OR ALL AGENCIES.
2-7.1 (9) THE PROPOSED RMS/JMS APPLICATION SHALL INCLUDE A
FUNCTION FOR RETRIEVING ALL RECORDS ASSOCIATED WITH A
USER-DEFINED NAME REGARDLESS OF THE ASSOCIATION
BETWEEN THE NAME SEARCHED AND THE RECORD IN WHICH IT
APPEARS.
2-7.1 (10) THE PROPOSED RMS/JMS APPLICATION SHALL ALLOW
AUTHORIZED USERS TO PRINT A COMPLETE HISTORY OF ALL
OCCURRENCES OF A SPECIFIC INDIVIDUAL WITHIN THE PROPOSED
RMS/JMS APPLICATION. THIS REPORT WILL PRINT TO EITHER THE
SCREEN OR PAPER AND THE RECORDS SHALL BE SORTED BY DATE.
2-7.1 (11) THE PROPOSED RMS/JMS APPLICATION SHALL INCLUDE A
FUNCTION FOR RETRIEVING ALL RECORDS ASSOCIATED WITH A
USER-DEFINED LOCATION REGARDLESS OF THE ASSOCIATION
BETWEEN THE LOCATION SEARCHED AND THE RECORD IN WHICH
IT APPEARS.
2-7.1 (12) THE PROPOSED RMS/JMS APPLICATION SHALL INCLUDE A
FUNCTION FOR RETRIEVING ALL RECORDS ASSOCIATED WITH A
USER-DEFINED VEHICLE REGARDLESS OF THE ASSOCIATION
City of Fort Collins lv Proposal P-847
BETWEEN THE VEHICLE SEARCHED AND THE RECORD IN WHICH IT
APPEARS.
2-7.1 (13) THE PROPOSED RMS/JMS APPLICATION SHALL INCLUDE A
FUNCTION FOR RETRIEVING ALL RECORDS ASSOCIATED WITH A
USER-DEFINED PROPERTY ITEM REGARDLESS OF THE
ASSOCIATION BETWEEN THE PROPERTY ITEM SEARCHED AND THE
RECORD IN WHICH IT APPEARS.
2-7.1 (14) THE PROPOSED RMS/JMS APPLICATION SHALL ALLOW USERS TO
GO DIRECTLY TO ANY CASE REPORT, INCIDENT OR CONTACT (BY
DOUBLE CLICKING OR OTHER SIMPLE METHOD) FOUND WHEN
RUNNING A QUERY OF ANY PERSON OR VEHICLE.
2-7.1 (15) THE PROPOSED RMS/JMS APPLICATION SHALL ALLOW THE CRIME
ANALYST OR OTHER AUTHORIZED USER TO SEARCH BY ONE OR
MORE VEHICLE DESCRIPTORS.
2-7.1 (16) THE PROPOSED RMS/JMS APPLICATION SHALL ALLOW THE CRIME
ANALYST OR OTHER AUTHORIZED USER TO SEARCH BY ONE OR
MORE PROPERTY DESCRIPTORS.
2-7.1 (17) USERS SHALL HAVE THE ABILITY TO SAVE QUERY RESULTS.
2-7.1 (18) USERS SHALL HAVE THE ABILITY TO USE PREVIOUSLY SAVED
SEARCHES.
2-7.1 (19) THE PROPOSED RMS/JMS APPLICATION SHALL HAVE THE ABILITY
TO SEARCH THE DATABASE BY ANY INDIVIDUAL FIELD OR
COMBINATION OF FIELDS.
2-7.1 (20) THE PROPOSED RMS/JMS APPLICATION SHALL PROVIDE INQUIRY
FORMS THAT ARE CONSISTENT WITH THE DATA ENTRY FORMS.
HENCE, AN INCIDENT SEARCH FORM WOULD LOOK SIMILAR TO AN
INCIDENT ENTRY FORM.
2-7.1 (21) THE PROPOSED RMS/JMS APPLICATION SHALL INCLUDE AN
INQUIRY THAT CAN SHOW THE REPORTS WHICH HAVE BEEN
COMPLETED AS COMPARED TO THE REPORTS WHICH ARE
EXPECTED TO BE COMPLETED BASED ON INCIDENT DATA
RECEIVED FROM CAD (TO INCLUDE THE STATUS OF ALL THOSE
REPORTS).
2-7.1 (22) THE PROPOSED RMS/JMS APPLICATION SHALL INCLUDE AN
INQUIRY THAT ALLOWS THE EVIDENCE TECHNICIAN TO SEARCH
FOR CASES WHICH HAVE A COURT DISPOSITION AND WHICH HAVE
PROPERTY THAT CAN BE RETURNED OR DESTROYED.
City of Fort Collins lvi Proposal P-847
2-7.1 (23) THE PROPOSED RMS/JMS APPLICATION SHALL PROVIDE A
“SOUNDEX” OR OTHER PHONETIC SEARCH ALGORITHM FOR NAME
RETRIEVAL.
2-7.1 (24) THE PROPOSED APPLICATION SHALL HAVE A PARAMETER THAT A
USER CAN SELECT TO SEARCH FOR DERIVATIVE NAMES (I.E.
WILLIAM/BILL, CHARLES/CHUCK).
2-7.1 (25) THE PROPOSED RMS/JMS APPLICATION SHALL HAVE THE ABILITY
TO SEARCH FOR PERSONS OR BUSINESSES BY TELEPHONE NUMBER.
2-7.1 (26) PHONE NUMBERS SHALL BE SEARCHABLE WITHOUT BEING
ASSOCIATED TO NAME
2-7.1 (27) THE PROPOSED RMS/JMS APPLICATION SHALL HAVE THE ABILITY
TO SEARCH FOR TELEPHONE NUMBERS BY A PERSON’S NAME OR
ALIAS.
2-7.1 (28) THE PROPOSED RMS/JMS APPLICATION SHALL PROVIDE THE
ABILITY TO SEARCH FOR AND DISPLAY A LIST OF OFFENSES AND
OFFENSE DATES FOR, AT A MINIMUM:
2-7.1 (28.1) A GIVEN NAME,
2-7.1 (28.2) DATE OF BIRTH,
2-7.1 (28.3) GENDER, OR
2-7.1 (28.4) ETHNICITY.
2-7.1 (29) THE PROPOSED RMS/JMS APPLICATION SHALL ALLOW FOR QUERY
OF LOCATIONS BY EXACT ADDRESS, BY INTERSECTIONS, X-Y
COORDINATES, ADDRESS RANGES, OR BY USING WILDCARDS IF
EXACT ADDRESS IS UNKNOWN.
2-7.1 (30) THE PROPOSED RMS/JMS APPLICATION SHALL ALLOW FOR
QUERIES USING WILDCARDS (I.E. *, %, ETC.)
2-8 DATA ENTRY SPECIFICATIONS
The system is expected to have the capability to assist the user in performing many of the
tasks required for system operation.
2-8.1 (1) THE SYSTEM SHALL HAVE AN EXTENSIVE ON-LINE HELP SYSTEM
THAT ACCURATELY REFLECTS THE STATE OF THE SOFTWARE IN
ITS CURRENT VERSION.
City of Fort Collins lvii Proposal P-847
2-8.1 (2) THE SYSTEM SHALL HAVE AN EXTENSIVE CONTEXT SENSITIVE
HELP THAT BE ACCESS BY MOUSE OR A SINGLE KEY OR SINGLE
KEYSTROKE COMBINATION.
2-8.1 (3) THE SYSTEM SHALL HAVE THE ABILITY TO MODIFY OR ADD TO ON-
LINE HELP OR CONTEXT SENSITIVE HELP AS AN ADMINISTRATOR
FUNCTION.
2-8.1 (4) THE SYSTEM SHALL USE AND DISPLAY THE SAME DATE AND TIME
FORMATS ACROSS ALL APPLICATIONS.
2-8.1 (5) AUTHORIZED PERSONNEL, TYPICALLY RECORDS EMPLOYEES,
ENTER ALL CASE NARRATIVES. THEY SHALL BE ABLE TO
RETRIEVE A REPORT AND GO DIRECTLY TO THE NARRATIVE
SECTION.
2-8.1 (6) IT SHALL BE POSSIBLE FOR AN AUTHORIZED USER TO TRANSFER
THE CAD DETAILS OF AN EVENT TO RMS/JMS AT ANY TIME AFTER A
CASE (REPORT) NUMBER HAS BEEN ASSIGNED EVEN IF THE EVENT
HAS NOT BEEN CLOSED IN CAD.
2-8.1 (7) AUTHORIZED PERSONNEL, TYPICALLY RECORDS EMPLOYEES,
SOMETIMES HAVE TO UPDATE MANY CASES WITH THE SAME
INFORMATION WITHOUT RE-ENTERING THE INFORMATION. IT IS
PREFERRED THAT THE PROPOSED SYSTEM SUPPORT THIS
FUNCTION (VENDOR MUST ATTACH AN EXPLANATION AS TO HOW
THEY WOULD ACCOMPLISH THIS).
2-8.1 (8) WHEN A USER IS REQUIRED TO ENTER THEIR NAME AND ID FOR A
PROCESS, IT IS PREFERRED THAT THE SYSTEM HAVE THE ABILITY
(AT AGENCY DISCRETION) TO AUTOMATICALLY ENTER THE ID OF
THE USER THAT IS LOGGED ON.
2-8.1 (9) THE PROPOSED RMS/JMS APPLICATION SHALL AUTOMATICALLY
DISPLAY THE DAY OF THE WEEK WHEN THE DATE IS ENTERED.
2-8.1 (10) THE PROPOSED RMS/JMS APPLICATION SHALL ALLOW FOR
SHORTCUTS FOR DATE ENTRY (I.E. T=TODAY’S DATE,
Y=YESTERDAY’S DATE, ETC.)
2-8.1 (11) THE USER SHALL BE ABLE TO DECREASE AND INCREASE THE DATE
ONE DAY AT A TIME BY PRESSING THE MINUS OR PLUS KEY.
2-8.1 (12) THE PROPOSED APPLICATION SHALL SUPPORT WINDOWS STYLE
CUT AND PASTE FUNCTIONS.
City of Fort Collins lviii Proposal P-847
2-8.1 (13) THE SYSTEM SHALL USE DROP DOWN PICK LISTS FOR ALL EDITED
FIELDS, BUT SHALL NOT REQUIRE THE USER TO ACCESS THE LIST
IF THEY KNOW AND WISH TO ENTER A CORRECT VALUE DIRECTLY.
2-8.1 (14) THE SYSTEM SHALL UTILIZE “TYPE TO COMPLETE” (TYPING
MOVES THROUGH LIST FOR EASY SELECTION) ON ALL EDITED
FIELDS.
2-8.1 (15) THE SYSTEM SHALL UTILIZE “TYPING TO LIMIT CHOICE” (TYPING
NARROWS POSSIBLE CHOICES) ON ALL EDITED FIELDS.
2-8.1 (16) THE SYSTEM SHALL ALLOW FOR CONTROLLING ALL ENTRY
FUNCTIONS WITH THE EXCLUSIVE USE OF A MOUSE.
2-8.1 (17) THE SYSTEM SHALL ALLOW FOR CONTROLLING ALL ENTRY
FUNCTIONS WITH THE EXCLUSIVE USE OF A KEYBOARD.
2-8.1 (18) THE SYSTEM SHALL ALLOW FOR THE PARTICIPATING AGENCIES TO
DEFINE ADDITIONAL DATABASE FIELDS IN ALL MAJOR
APPLICATIONS.
2-8.1 (19) THE SYSTEM SHALL ALLOW FOR THE PARTICIPATING AGENCIES TO
DEFINE EDITS FOR AGENCY DEFINED FIELDS.
2-9 MASTER INDEXES
2-9.1 GENERAL PROVISIONS
The RMS/JMS shall maintain at least four master indexes (shared by all agencies), the
Master Name Record (MNI), the Master Location Record (MLI), the Master Vehicle
Record (MVI) and the Master Property Record (MPI), that are used to link all
occurrences of the indexed data throughout the RMS/JMS regardless of where the
information is entered or queried.
2-9.1 (1) THE SYSTEM SHALL GENERATE A UNIQUE GLOBAL
IDENTIFICATION NUMBER (NON AGENCY SPECIFIC) FOR EACH
MASTER INDEX RECORD ENTERED INTO THE SYSTEM THAT NEVER
CHANGES.
2-9.1 (2) IN THE EVENT THAT THE MASTER INDEX CONTAINS A SIMILAR
NAME OR ITEM, A SUMMARY LIST SHALL DISPLAY SHOWING THE
PARTICULARS OF THE NAMES OR ITEMS THAT ARE SIMILAR TO
THE ONE BEING ENTERED (DEFINED AS NEAR HITS).
2-9.1 (3) THE PROPOSED RMS/JMS APPLICATION SHALL ALLOW AN
AUTHORIZED USER TO MERGE TWO OR MORE MASTER INDEX
RECORDS INTO A SINGLE RECORD THAT MAINTAINS ALL LINKS TO
City of Fort Collins lix Proposal P-847
ALL AREAS THAT WERE PREVIOUSLY HELD BY ALL THE SEPARATE
RECORDS.
2-9.1 (3.1) UPON ANY MASTER INDEX RECORDS MERGE THE SYSTEM MUST
KEEP A USER VIEWABLE LOG OF THE MASTER INDEX NUMBERS
THAT WERE MERGED AND THE CURRENT MASTER INDEX
NUMBER IN USE.
2-9.1 (3.2) SYSTEM SHALL ALLOW FOR SEARCHING ON ALL MERGED
MASTER INDEX NUMBERS AND NOTIFY THE USER OF THE MERGE
AND THEN DISPLAY THE CURRENT RECORD.
2-9.1 (3.3) WHEN MERGING MASTER INDEX RECORDS, THE APPLICATION
SHALL PRESERVE THE MOST RECENTLY ENTERED INFORMATION
AND SHOW ALL OTHER POSSIBLE INFORMATION AS HISTORICAL
DATA.
2-9.1 (4) USERS SHALL HAVE THE ABILITY TO SET A GENERAL
NOTIFICATION FLAG TO INDICATE THEIR INTEREST IN A SUBJECT
OF A MASTER INDEX RECORD (PERSON, LOCATION, VEHICLE, OR
ITEM OF INTEREST).
2-9.1 (5) USERS SHALL HAVE THE ABILITY TO SET A BLIND NOTIFICATION
FLAG TO INDICATE THEIR INTEREST IN A SUBJECT OF A MASTER
INDEX RECORD (PERSON, LOCATION, VEHICLE, OR ITEM OF
INTEREST).
2-9.1 (6) WHEN A USER SELECTS A RECORD OF INTEREST (ROI) (OR ANY OF
ITS LINKED APPEARANCES) FOR VIEWING OR MODIFICATION, THE
PROPOSED RMS/JMS APPLICATION SHALL NOTIFY THE USER AND
THE PERSON WHO SET THE FLAG THAT THE RECORD IS THE
SUBJECT OF INTEREST TO ANOTHER USER (DEFINED AS THE
GENERAL NOTIFICATION FLAG).
2-9.1 (7) WHEN A USER SELECTS A RECORD OF INTEREST (ROI) (OR ANY OF
ITS LINKED APPEARANCES) FOR VIEWING OR MODIFICATION, THE
PROPOSED RMS/JMS APPLICATION SHALL NOTIFY ONLY THE
PERSON WHO SET THE FLAG THAT THE RECORD IS THE SUBJECT
OF INTEREST TO ANOTHER USER (DEFINED AS THE BLIND
NOTIFICATION FLAG).
2-9.1 (8) NO ONE, OTHER THAN THE PERSON ENTERING THE ROI, THE
SYSTEM ADMINISTRATOR OR OTHER AUTHORIZED USER, SHALL BE
ABLE TO SEE A LIST OF ROI ENTRIES.
2-9.1 (9) USERS SHALL BE ABLE TO VIEW ANY IMAGES ASSOCIATED WITH A
MASTER NAME INDEX RECORD ON ANY WORKSTATION THROUGH A
City of Fort Collins lx Proposal P-847
“POINT & CLICK” OR SOME OTHER SIMPLE COMMAND (IF NOT
ALWAYS DISPLAYED ALREADY).
2-9.1 (10) THE PROPOSED RMS/JMS APPLICATION SHALL MAKE THE MASTER
INDEXES ACCESSIBLE TO MOBILE USERS (IF CONNECTION EXISTS).
2-9.1 (11) THE PROPOSED RMS/JMS APPLICATION SHALL RETAIN ALL
MASTER INDEX RECORDS INDEFINITELY UNLESS A RECORD IS
MERGED OR DELETED BY A SYSTEM ADMINISTRATOR.
2-9.2 MASTER NAME INDEX
2-9.2 (1) THE PROPOSED RMS/JMS APPLICATION SHALL HAVE THE ABILITY
TO MAINTAIN A MASTER NAME INDEX (MNI) THAT IS CREATED OR
UPDATED BY THE ENTRY OF PERSONAL DEMOGRAPHICS IN
ORIGINAL AND SUPPLEMENTAL REPORTS AND FROM ANY FORM
WHERE PERSON QUERY AND ENTRY IS ALLOWED.
2-9.2 (2) THE MNI SHALL CONTAIN THE MINIMUM DATA AS FOLLOWS:
2-9.2 (2.1) LAST NAME (WITH PROVISIONS FOR HYPHENATED LAST NAMES
AND SUFFIXES),
2-9.2 (2.2) FIRST NAME,
2-9.2 (2.3) MIDDLE NAME,
2-9.2 (2.4) GENDER,
2-9.2 (2.5) ETHNICITY,
2-9.2 (2.6) HEIGHT,
2-9.2 (2.7) WEIGHT,
2-9.2 (2.8) HAIR COLOR,
2-9.2 (2.9) EYE COLOR,
2-9.2 (2.10) SCARS, MARKS, AND TATTOOS, AND THE LOCATION EACH
OCCURS ON THE BODY,
2-9.2 (2.11) DATE OF BIRTH,
2-9.2 (2.12) AGE (MANUAL ENTRY IF NO DOB EXISTS; CONTINUAL
AUTOMATIC CALCULATION IF DOB IS PRESENT),
2-9.2 (2.13) SOCIAL SECURITY NUMBER,
City of Fort Collins lxi Proposal P-847
2-9.2 (2.14) HOME STREET ADDRESS (TIED TO MNI & MLI),
2-9.2 (2.15) HOME CITY (TIED TO MNI & MLI),
2-9.2 (2.16) HOME STATE (TIED TO MNI & MLI),
2-9.2 (2.17) HOME ZIP CODE (TIED TO MNI & MLI),
2-9.2 (2.18) HOME PHONE (AT LEAST 20 CHARACTERS) (TIED TO MNI & MLI)
(UP TO 99),
2-9.2 (2.19) HOME PHONE TYPE CODE (PER RECORD ABOVE),
2-9.2 (2.20) HOME E-MAIL,
2-9.2 (2.21) OCCUPATION,
2-9.2 (2.22) BUSINESS NAME (TIED TO MNI & MLI),
2-9.2 (2.23) BUSINESS STREET ADDRESS (TIED TO MNI & MLI),
2-9.2 (2.24) BUSINESS CITY (TIED TO MNI & MLI),
2-9.2 (2.25) BUSINESS STATE (TIED TO MNI & MLI),
2-9.2 (2.26) BUSINESS ZIP CODE (TIED TO MNI & MLI),
2-9.2 (2.27) BUSINESS PHONE (AT LEAST 20 CHARACTERS) (TIED TO MNI &
MLI) (UP TO 99),
2-9.2 (2.28) BUSINESS PHONE TYPE CODE (PER RECORD ABOVE),
2-9.2 (2.29) BUSINESS E-MAIL
2-9.2 (2.30) OTHER PHONE NUMBER (TIED TO MNI) (UP TO 99),
2-9.2 (2.31) OTHER PHONE TYPE CODE (PER RECORD ABOVE),
2-9.2 (2.32) PARTICIPATING AGENCIES ID NUMBER(S),
2-9.2 (2.33) STATE CRIMINAL ID NUMBER(S),
2-9.2 (2.34) FBI NUMBER,
2-9.2 (2.35) DRIVER'S LICENSE NUMBER(S), STATE(S) OF ISSUE AND
EXPIRATION DATE(S),
2-9.2 (2.36) OTHER IDENTIFYING NUMBERS,
City of Fort Collins lxii Proposal P-847
2-9.2 (2.37) ALIAS LAST NAME (W/PROVISIONS FOR HYPHENATED LAST
NAMES AND SUFFIXES) (UP TO 99),
2-9.2 (2.38) ALIAS FIRST NAMES (UP TO 99),
2-9.2 (2.39) ALIAS MIDDLE NAMES (UP TO 99),
2-9.2 (2.40) ALIAS DATES OF BIRTH (UP TO 99),
2-9.2 (2.41) ALIAS SOCIAL SECURITY NUMBERS (UP TO 99),
2-9.2 (2.42) HISTORY OF HOME ADDRESSES (STREET, CITY, ZIP) (UP TO 99),
2-9.2 (2.43) HISTORY OF BUSINESS ADDRESSES (STREET, CITY, ZIP) (UP TO 99),
2-9.2 (2.44) MONIKER(S) (UP TO 99), AND
2-9.2 (2.45) MULTIPLE CAUTIONS (UP TO 99),
2-9.2 (2.46) MUGSHOT IMAGES OF THE INDIVIDUAL (UP TO 99),
2-9.2 (2.47) AND A LINK TO THE ADDITION DATA HELD IN THE MUGSHOT
MODULE.
2-9.2 (2.48) FOR PHONE NUMBER FIELDS THE SYSTEM SHALL HAVE THE
ABILITY TO SET A DEFAULT VALUE FOR AREA CODE AT THE
PARTICIPATING AGENCIES DISCRETION.
2-9.2 (3) THE MNI SHALL FUNCTION AS A CENTRAL CROSS REFERENCE TO
LINK ALL OCCURRENCES OF AN INDIVIDUAL’S PERSONAL
INFORMATION ACROSS ALL APPLICATIONS.
2-9.2 (4) UPON ENTRY OF A PERSON ANYWHERE IN THE RMS/JMS, THE
SYSTEM SHALL PROVIDE A MECHANISM TO SEARCH THE MNI FOR
ANY PERVIOUS CONTACTS WITH THAT PERSON (WITH THE SEARCH
BECOMING MORE SPECIFIC AS MORE PERSONAL INFORMATION IS
PROVIDED) AND,
2-9.2 (5) UPON ENTRY OF A PERSON ANYWHERE IN THE RMS/JMS, THE
SYSTEM SHALL PROVIDE A MECHANISM TO SEARCH THE MNI FOR
ANY PERVIOUS CONTACTS WITH THAT PERSON BY UTILIZING A
SOUNDEX ROUTINE ON THAT PERSON’S NAME (WITH THE SEARCH
BECOMING MORE SPECIFIC AS MORE NAME INFORMATION IS
PROVIDED).
2-9.2 (6) THE SYSTEM SHALL DISPLAY THE RESULTS OF THE MNI SEARCH IN
A FORMAT THAT PROVIDES SUFFICIENT INFORMATION PER
PERSON TO ELIMINATE NEAR HITS AND ALLOW FOR THE
City of Fort Collins lxiii Proposal P-847
SELECTION OF A MATCHING RECORD WITH THE USE OF A MOUSE
OR KEYBOARD.
2-9.2 (7) THE SYSTEM SHALL ALLOW THE CLEARING OF THIS SEARCH
RESULT AND ALLOW CHANGING THE DATA AND STARTING A NEW
SEARCH.
2-9.2 (8) UPON SELECTION OF A PERSON’S RECORD IN THE SEARCH RESULT
WINDOW THE SYSTEM SHALL AUTO-POPULATE ALL POSSIBLE
FIELDS ON THE ENTRY FORM AND CREATE A LINK TO THE MNI FOR
THIS RECORD.
2-9.2 (9) THE ENTRY PERSONNEL SHALL THEN BE ABLE TO MODIFY ANY OF
THE PERSONAL DEMOGRAPHIC INFORMATION, AND BY DOING SO,
AUTOMATICALLY UPDATE THE INFORMATION IN THE MNI.
2-9.2 (10) THE SYSTEM SHALL ALLOW THE CLEARING OF THIS SEARCH
RESULT AND THE MANUAL ENTRY OF ALL PERSONAL
DEMOGRAPHICS THAT WILL THEN CREATE A NEW MNI RECORD.
2-9.3 MASTER LOCATION INDEX
2-9.3 (1) THE PROPOSED RMS/JMS APPLICATION SHALL HAVE THE ABILITY
TO MAINTAIN A MASTER LOCATION INDEX (MLI) THAT IS CREATED
OR UPDATED BY THE ENTRY OF LOCATION INFORMATION IN
ORIGINAL AND SUPPLEMENTAL REPORTS AND FROM ANY FORM
WHERE LOCATION QUERY AND ENTRY IS ALLOWED.
2-9.3 (2) THE MLI SHALL CONTAIN THE MINIMUM DATA AS FOLLOWS:
2-9.3 (2.1) LOCATION NAME,
2-9.3 (2.2) LOCATION TYPE,
2-9.3 (2.3) LOCATION STREET NUMBER,
2-9.3 (2.4) LOCATION SUB UNIT TYPE (APARTMENT, BUILDING, ETC.),
2-9.3 (2.5) LOCATION SUB UNIT NUMBER (ALPHA NUMERIC),
2-9.3 (2.6) LOCATION STREET NAME,
2-9.3 (2.7) LOCATION CITY,
2-9.3 (2.8) LOCATION STATE,
2-9.3 (2.9) LOCATION ZIP CODE,
2-9.3 (2.10) LOCATION PHONE NUMBER (AT LEAST 20 CHARACTERS),
City of Fort Collins lxiv Proposal P-847
2-9.3 (2.11) LOCATION X COORDINATE (EASTING),
2-9.3 (2.12) LOCATION Y COORDINATE (NORTHING),
2-9.3 (2.13) LOCATION Z COORDINATE (ALTITUDE),
2-9.3 (2.14) DIGITAL IMAGES OF THE LOCATION (UP TO 9).
2-9.3 (2.15) AND, MULTIPLE CAUTIONS (UP TO 99).
2-9.3 (3) THE MLI SHALL FUNCTION AS A CENTRAL CROSS REFERENCE TO
LINK ALL OCCURRENCES OF A LOCATION ACROSS ALL
APPLICATIONS.
2-9.3 (4) UPON ENTRY OF A LOCATION ANYWHERE IN THE RMS/JMS, THE
SYSTEM SHALL PROVIDE A MECHANISM TO SEARCH THE MLI FOR
ANY PERVIOUS ENTRIES OF THAT LOCATION (WITH THE SEARCH
BECOMING MORE SPECIFIC AS MORE LOCATION INFORMATION IS
PROVIDED) AND,
2-9.3 (5) THE SYSTEM SHALL DISPLAY THE RESULTS OF THE MLI SEARCH IN
A FORMAT THAT PROVIDES SUFFICIENT INFORMATION PER
LOCATION TO ELIMINATE NEAR HITS AND ALLOW FOR THE
SELECTION OF A MATCHING RECORD WITH THE USE OF A MOUSE
OR KEYBOARD.
2-9.3 (6) THE SYSTEM SHALL ALLOW THE CLEARING OF THIS SEARCH
RESULT AND ALLOW CHANGING THE DATA AND STARTING A NEW
SEARCH.
2-9.3 (7) UPON SELECTION OF A LOCATION RECORD IN THE SEARCH RESULT
WINDOW THE SYSTEM SHALL AUTO-POPULATE ALL POSSIBLE
FIELDS ON THE ENTRY FORM AND CREATE A LINK TO THE MLI FOR
THIS RECORD.
2-9.3 (8) THE ENTRY PERSONNEL SHALL THEN BE ABLE TO MODIFY ANY OF
THE LOCATION INFORMATION, AND BY DOING SO,
AUTOMATICALLY UPDATE THE INFORMATION IN THE MLI.
2-9.3 (9) THE SYSTEM SHALL ALLOW THE CLEARING OF THIS SEARCH
RESULT AND THE MANUAL ENTRY OF ALL LOCATION
INFORMATION THAT WILL THEN CREATE A NEW MLI RECORD.
2-9.4 MASTER VEHICLE INDEX
2-9.4 (1) THE PROPOSED RMS/JMS APPLICATION SHALL HAVE THE ABILITY
TO MAINTAIN A MASTER VEHICLE INDEX (MVI) THAT IS CREATED
OR UPDATED BY THE ENTRY OF VEHICLES IN ORIGINAL AND
City of Fort Collins lxv Proposal P-847
SUPPLEMENTAL REPORTS AND FROM ANY FORM WHERE VEHICLE
QUERY AND ENTRY IS ALLOWED.
2-9.4 (2) THE MVI SHALL CONTAIN THE MINIMUM DATA AS FOLLOWS:
2-9.4 (2.1) VEHICLE TYPE,
2-9.4 (2.2) MAKE,
2-9.4 (2.3) MODEL,
2-9.4 (2.4) YEAR OF MANUFACTURE,
2-9.4 (2.5) VIN NUMBER,
2-9.4 (2.6) BODY STYLE,
2-9.4 (2.7) COLOR – TOP,
2-9.4 (2.8) COLOR – BOTTOM,
2-9.4 (2.9) COLOR – INTERIOR,
2-9.4 (2.10) LICENSE PLATE NUMBER,
2-9.4 (2.11) LICENSE PLATE STATE,
2-9.4 (2.12) LICENSE PLATE EXPIRATION YEAR,
2-9.4 (2.13) IDENTIFYING MARKS,
2-9.4 (2.14) COMMENTS,
2-9.4 (2.15) DIGITAL IMAGES OF THE VEHICLE (UP TO 9),
2-9.4 (2.16) HISTORY OF LICENSE PLATE NUMBER (UP TO 99),
2-9.4 (2.17) HISTORY OF LICENSE PLATE STATE (UP TO 99),
2-9.4 (2.18) AND HISTORY OF LICENSE PLATE EXPIRATION YEAR (UP TO 99).
2-9.4 (3) THE MVI SHALL FUNCTION AS A CENTRAL CROSS REFERENCE TO
LINK ALL OCCURRENCES OF A VEHICLE ACROSS ALL
APPLICATIONS.
2-9.4 (4) UPON ENTRY OF A VEHICLE ANYWHERE IN THE RMS/JMS, THE
SYSTEM SHALL PROVIDE A MECHANISM TO SEARCH THE MVI FOR
ANY PERVIOUS ENTRIES OF THAT VEHICLE (WITH THE SEARCH
City of Fort Collins lxvi Proposal P-847
BECOMING MORE SPECIFIC AS MORE VEHICLE INFORMATION IS
PROVIDED) AND,
2-9.4 (5) THE SYSTEM SHALL DISPLAY THE RESULTS OF THE MVI SEARCH IN
A FORMAT THAT PROVIDES SUFFICIENT INFORMATION PER
VEHICLE TO ELIMINATE NEAR HITS AND ALLOW FOR THE
SELECTION OF A MATCHING RECORD WITH THE USE OF A MOUSE
OR KEYBOARD.
2-9.4 (6) THE SYSTEM SHALL ALLOW THE CLEARING OF THIS SEARCH
RESULT AND ALLOW CHANGING THE DATA AND STARTING A NEW
SEARCH.
2-9.4 (7) UPON SELECTION OF A VEHICLE RECORD IN THE SEARCH RESULT
WINDOW THE SYSTEM SHALL AUTO-POPULATE ALL POSSIBLE
FIELDS ON THE ENTRY FORM AND CREATE A LINK TO THE MVI FOR
THIS RECORD.
2-9.4 (8) THE ENTRY PERSONNEL SHALL THEN BE ABLE TO MODIFY ANY OF
THE VEHICLE INFORMATION, AND BY DOING SO, AUTOMATICALLY
UPDATE THE INFORMATION IN THE MVI.
2-9.4 (9) THE SYSTEM SHALL ALLOW THE CLEARING OF THIS SEARCH
RESULT AND THE MANUAL ENTRY OF ALL VEHICLE INFORMATION
THAT WILL THEN CREATE A NEW MVI RECORD.
2-9.5 MASTER PROPERTY INDEX
2-9.5 (1) THE PROPOSED RMS/JMS APPLICATION SHALL HAVE THE ABILITY
TO MAINTAIN A MASTER PROPERTY INDEX (MPI) THAT IS CREATED
OR UPDATED BY THE ENTRY OF PROPERTY DESCRIPTIONS IN
ORIGINAL AND SUPPLEMENTAL REPORTS AND FROM ANY FORM
WHERE PROPERTY QUERY AND ENTRY IS ALLOWED.
2-9.5 (2) THE MPI SHALL CONTAIN THE MINIMUM DATA AS FOLLOWS:
2-9.5 (2.1) PROPERTY TYPE (E.G. JEWELRY, CURRENCY, FIREARM, ETC.),
2-9.5 (2.2) MAKE OR BRAND NAME,
2-9.5 (2.3) MODEL,
2-9.5 (2.4) SERIAL NUMBER
2-9.5 (2.5) OTHER IDENTIFYING NUMBER, (OWNER APPLIED ID,
ALPHA/NUMERIC) (UP TO 9),
2-9.5 (2.6) DIMENSIONS,
City of Fort Collins lxvii Proposal P-847
2-9.5 (2.7) SIZE,
2-9.5 (2.8) WEIGHT,
2-9.5 (2.9) COLOR,
2-9.5 (2.10) CALIBER/GAUGE,
2-9.5 (2.11) NARRATIVE DESCRIPTION,
2-9.5 (2.12) DIGITAL IMAGES OF THE PROPERTY (UP TO 9).
2-9.5 (3) THE MPI SHALL FUNCTION AS A CENTRAL CROSS REFERENCE TO
LINK ALL OCCURRENCES OF A PIECE OF PROPERTY ACROSS ALL
APPLICATIONS.
2-9.5 (4) UPON ENTRY OF A PROPERTY ANYWHERE IN THE RMS/JMS, THE
SYSTEM SHALL PROVIDE A MECHANISM TO SEARCH THE MPI FOR
ANY PERVIOUS ENTRIES OF THAT PROPERTY (WITH THE SEARCH
BECOMING MORE SPECIFIC AS MORE PROPERTY INFORMATION IS
PROVIDED) AND,
2-9.5 (5) THE SYSTEM SHALL DISPLAY THE RESULTS OF THE MPI SEARCH IN
A FORMAT THAT PROVIDES SUFFICIENT INFORMATION PER
PROPERTY TO ELIMINATE NEAR HITS AND ALLOW FOR THE
SELECTION OF A MATCHING RECORD WITH THE USE OF A MOUSE
OR KEYBOARD.
2-9.5 (6) THE SYSTEM SHALL ALLOW THE CLEARING OF THIS SEARCH
RESULT AND ALLOW CHANGING THE DATA AND STARTING A NEW
SEARCH.
2-9.5 (7) UPON SELECTION OF A PROPERTY RECORD IN THE SEARCH RESULT
WINDOW THE SYSTEM SHALL AUTO-POPULATE ALL POSSIBLE
FIELDS ON THE ENTRY FORM AND CREATE A LINK TO THE MPI FOR
THIS RECORD.
2-9.5 (8) THE ENTRY PERSONNEL SHALL THEN BE ABLE TO MODIFY ANY OF
THE PROPERTY INFORMATION, AND BY DOING SO,
AUTOMATICALLY UPDATE THE INFORMATION IN THE MPI.
2-9.5 (9) THE SYSTEM SHALL ALLOW THE CLEARING OF THIS SEARCH
RESULT AND THE MANUAL ENTRY OF ALL PROPERTY
INFORMATION THAT WILL THEN CREATE A NEW MPI RECORD.
City of Fort Collins lxviii Proposal P-847
2-10 MUGSHOT MODULE
The proposed RMS/JMS application shall provide for capturing additional data on any
person listed in the MNI to support mugshot applications.
2-10.1 (1) AT A MINIMUM, THE MUGSHOT APPLICATION SHALL INCLUDE:
2-10.1 (1.1) ALL DATA CAPTURED BY THE MNI AND;
2-10.1 (1.2) CALCULATED AGE AT TIME OF MUGSHOT,
2-10.1 (1.3) PLACE OF BIRTH,
2-10.1 (1.4) HAIR LENGTH,
2-10.1 (1.5) HAIR STYLE,
2-10.1 (1.6) FACIAL HAIR,
2-10.1 (1.7) COMPLEXION,
2-10.1 (1.8) GLASSES,
2-10.1 (1.9) EYE CHARACTERISTICS,
2-10.1 (1.10) SPEECH,
2-10.1 (1.11) TEETH,
2-10.1 (1.12) HAT,
2-10.1 (1.13) PHYSICAL BUILD,
2-10.1 (1.14) MISSING LIMBS,
2-10.1 (1.15) INJURY/ ILLNESS,
2-10.1 (1.16) TREATED BY,
2-10.1 (1.17) WHERE TREATED,
2-10.1 (1.18) DATE AND TIME TREATED
2-10.1 (1.19) CASE (REPORT) NUMBER HISTORY,
2-10.1 (1.20) REPORTING OFFICER HISTORY,
2-10.1 (1.21) ARREST HISTORY (ARREST (BOOKING) NUMBER, DATE AND TIME)
2-10.1 (1.22) ARREST LOCATION HISTORY,
City of Fort Collins lxix Proposal P-847
2-10.1 (1.23) AND A CLEAR INDICATION THAT A PICTURE IS ONE OF A
JUVENILE.
2-10.1 (2) THE PROPOSED RMS/JMS APPLICATION SHALL HAVE THE ABILITY
TO CREATE PHOTO LINEUPS, WITH USER DEFINED PARAMETERS,
USING PHOTOS IN THE MUGSHOT MODULE.
2-10.1 (3) THE PROPOSED RMS APPLICATION SHALL HAVE THE ABILITY TO
SAVE AND/OR PRINT PHOTO LINEUPS ONCE CREATED.
2-11 KNOWN OFFENDER MODULE
2-11.1 (1) THE PROPOSED RMS/JMS APPLICATION SHALL INCLUDE A MODULE
THAT WILL BE USED TO REGISTER KNOWN OFFENDERS SUCH AS
SEX OFFENDERS, GANG MEMBERS, ETC.
2-11.1 (2) THE KNOWN OFFENDER MODULE WILL INTERFACE TO THE
MASTER INDEXES SUCH THAT PERSONS ENTERED INTO THE
KNOWN OFFENDER MODULE WILL BE FOUND BY NAME, LOCATION
OR OTHER MASTER INDEX SEARCHES.
2-11.1 (3) THE KNOWN OFFENDER MODULE WILL ALLOW FOR MULTIPLE
ENTRIES OF OFFENDER CLASSIFICATION (I.E. SEX OFFENDER AND
GANG MEMBER AND PAROLEE)
2-11.1 (4) AT A MINIMUM, THE KNOWN OFFENDER MODULE SHALL INCLUDE
THE FOLLOWING FIELDS:
2-11.1 (4.1) ALL THE INFORMATION CONTAINED IN THE MNI, MLI, MVI, &
MUGSHOT MODULE FOR EACH OFFENDER ENTRY AND;
2-11.1 (4.2) DISPLAY OF THE MNI NUMBER,
2-11.1 (4.3) DISPLAY OF THE DATE OF LAST CONTACT (DERIVED FROM LAST
ENTRY FOR THIS PERSON ANYWHERE IN THE RMS/JMS),
2-11.1 (4.4) KNOWN OFFENDER CLASSIFICATION, (E.G. SEX OFFENDER, GANG
MEMBER, ETC.) (UP TO 99),
2-11.1 (4.5) MULTIPLE DATE FUNCTION (UP TO 99), DEFINED AS A ONE TO
MANY DATE CAPTURE CAPABILITY WITH A DATE TYPE PICK LIST
(ENTRY, FIRST REGISTRATION, NEXT REGISTRATION, END OF
REGISTRATION REQUIREMENT, REVIEW, ETC.) AND A DATE
FIELD. ALL DATE RECORDS TO BE HELD PER OFFENDER
CLASSIFICATION, AND ARE INTENDED TO DRIVE SYSTEM
ACTIONS AND NOTIFICATIONS,
City of Fort Collins lxx Proposal P-847
2-11.1 (4.6) REVIEW FLAG BY OFFENDER CLASSIFICATION (UP TO 99) (SETS A
FLAG BY DATE TYPE THAT CAUSES A REVIEW MESSAGE TO BE
SENT TO SPECIFIED PERSONNEL ON THAT DATE).
2-11.1 (4.7) DEFINE A ONE TO MANY CONDITIONS CAPTURE CAPABILITY
WITH A AGENCY DEFINED PICK LIST THAT ALLOWS TO APPEND
UP TO 99 CONDITIONS THAT ARE HELD UNIQUE TO AN OFFENDER
CLASSIFICATION, I.E. JUVENILE OR ADULT CONVICTION, SEXUAL
PREDATOR, COMMUNITY NOTIFICATION MADE, ETC.
2-11.1 (4.8) REGISTERING OFFICER NAME , ID AND ROLE,
2-11.1 (4.9) GANG AFFILIATION,
2-11.1 (4.10) GANG ‘SET’ AFFILIATION
2-11.1 (4.11) JURISDICTION OF CONVICTION,
2-11.1 (4.12) CONVICTION TYPE, (ALLOW FOR MULTIPLES)
2-11.1 (4.13) CONVICTION DESCRIPTION, (ALLOW FOR MULTIPLES)
2-11.1 (4.14) CONVICTION NCIC CODE, (ALLOW FOR MULTIPLES)
2-11.1 (4.15) AND NARRATIVE.
2-11.1 (5) THE KNOWN OFFENDER MODULE WILL ALLOW FOR
ENTRY/UPDATE TO THE CCIC/NCIC SYSTEM ON RECORD ENTRY
AND MODIFICATION.
2-11.1 (6) THE PROPOSED RMS/JMS APPLICATION SHALL HAVE THE ABILITY
CHECK CCIC/NCIC UPON ENTRY OF A REGISTERED SEX OFFENDER
TO DETERMINE IF THE INDIVIDUAL IS LISTED AS WANTED IN
ANOTHER JURISDICTION.
2-11.1 (7) THE PROPOSED RMS/JMS APPLICATION SHALL HAVE THE ABILITY
TO FORMAT AND SEND AN UPDATE MESSAGE TO CCIC EACH TIME
THAT A REGISTERED SEX OFFENDER IS ENTERED IN RMS.
2-11.1 (8) THE PROPOSED RMS/JMS APPLICATION SHOULD INCLUDE THE
ABILITY TO ATTACH THE CCIC/ NCIC RETURN TO THE REGISTERED
SEX OFFENDER.
2-12 WEB BASED FUNCTIONALITY
It is expected the system would utilize web technology to allow for many of the functions
of the CAD/RMS/JMS to be performed on any network attached workstation with use of a
City of Fort Collins lxxi Proposal P-847
web browser such as Microsoft Internet Explorer (version 5.5 or above) alone (no vendor
supplied software needed).
2-12.1 (1) WEB BASED FUNCTIONALITY IS PREFERRED FOR:
2-12.1 (1.1) MOBILE APPLICATION (MDC),
2-12.1 (1.2) OVER THE INTERNET (SECURE CLIENT),
2-12.1 (1.3) INTERNAL TO THE AGENCIES,
2-12.1 (1.4) AND PUBLIC INFORMATION DISSEMINATION OVER THE
INTERNET.
2-12.1 (2) WEB BASED USER CAPABILITIES ARE PREFERRED FOR:
2-12.1 (2.1) DATA SEARCH AND LOOKUP,
2-12.1 (2.2) CRIME ANALYSIS,
2-12.1 (2.3) DATA ENTRY,
2-12.1 (2.4) AND SYSTEM ADMINISTRATION.
2-13 WORKFLOW PROCESS SPECIFICATIONS
The proposed RMS/JMS application must support the ability for the participating agencies
to customize the workflow processes that are inherent in all system entry processes. This
customization should be a design feature of the system that allows the system
administrators of the system to configure many different work flow processes that will be
automatically driven by the task the user wishes to accomplish.
2-13.1 (1) THE PROPOSED RMS/JMS APPLICATION MUST SUPPORT THE
CAPABILITY FOR MULTIPLE, AGENCY CONFIGURABLE, WORKFLOW
PROCESSES.
2-13.1 (2) WORKFLOW PROCESSES MUST HAVE THE ABILITY TO
AUTOMATICALLY FORMAT AND SEND VARIOUS TYPES OF
INTERNAL MESSAGES THAT WILL PROMPT USERS TO COMPLETE
ACTIONS.
2-13.1 (3) WORKFLOW PROCESSES MUST HAVE THE ABILITY TO
AUTOMATICALLY FORMAT AND SEND VARIOUS TYPES OF
EXTERNAL (TO THE SYSTEM) E-MAIL MESSAGES THAT WILL
PROMPT USERS TO COMPLETE ACTIONS.
2-13.1 (4) WORKFLOW PROCESSES MUST BE ABLE TO BE SET BY SYSTEM
ADMINISTRATORS THAT WILL CHANGE BASED ON THE SELECTIONS
THAT THE USER MAKES DURING THE ENTRY PROCESSES
City of Fort Collins lxxii Proposal P-847
(DIFFERENT WORKFLOW DEPENDING ON SELECTIONS OR ENTRIES
MADE).
2-14 REPORT GENERATION SPECIFICATIONS
2-14.1 GENERAL REQUIREMENTS
2-14.1 (1) ALL REPORTING OF THE PROPOSED CAD/RMS/JMS THAT IS RUN
THROUGH THE USER CLIENT AT THE USER LEVEL SHALL HAVE THE
ABILITY TO BE MODIFIED, CREATED AND MADE AVAILABLE TO THE
USERS BY THE PARTICIPATING AGENCIES SYSTEM
ADMINISTRATORS.
2-14.1 (2) THE PROPOSING VENDOR SHALL TRAIN THE PARTICIPATING
AGENCIES SYSTEM ADMINISTRATORS TO MODIFY, CREATE, AND
MAKE AVAILABLE REPORTS TO THE USERS THROUGH THE
CAD/RMS/JMS CLIENT APPLICATIONS.
2-14.1 (3) ALL REPORTING OF THE PROPOSED CAD/RMS/JMS SHALL BE
DEFINABLE BY AGENCY (ONLY THE REPORTS FOR A USER’S
AGENCY ARE VIEWABLE AND USABLE BY THAT USER).
2-14.1 (4) THE PROPOSED CAD/RMS/JMS APPLICATION SHALL INCLUDE THE
ABILITY FOR AUTHORIZED USERS TO EDIT THE APPEARANCE OF
PRINTED REPORTS.
2-14.1 (5) THE PROPOSED CAD/RMS/JMS APPLICATION SHALL INCLUDE AN AD
HOC REPORT WRITER THAT CAN BE USED BY A NON-TECHNICAL
PROFESSIONAL TO CREATE, USE AND SAVE SEARCHES AND
REPORTS.
2-14.1 (6) THE PROPOSED AD HOC SEARCHING AND REPORTING CAPABILITY
SHALL INCLUDE LOGICAL OPERATORS AND OTHER ADVANCED
METHODS FOR SEARCHING AND RETRIEVING RECORDS THAT
MEET USER-DEFINED CRITERIA.
2-14.1 (7) THE PROPOSED CAD/RMS/JMS APPLICATION DATA FILES SHALL BE
COMPATIBLE WITH THIRD PARTY REPORTING TOOLS SUCH AS IQ
OBJECTS, AND CRYSTAL REPORTS.
2-14.1 (8) IT IS DESIRED THAT THE PROPOSED CAD/RMS/JMS APPLICATION
INCLUDE A GRAPHICAL OR OTHER AD HOC REPORT GENERATOR
THAT DOES NOT REQUIRE EXTENSIVE TRAINING IN SQL OR OTHER
QUERY LANGUAGES.
2-14.1 (9) THE PROPOSED CAD/RMS/JMS APPLICATION SHALL ALLOW
AUTHORIZED USERS TO SCHEDULE SEARCHES OR REPORTS TO RUN
AT SPECIFIC TIMES AND/OR SPECIFIC DATES.
City of Fort Collins lxxiii Proposal P-847
2-14.1 (10) SOME REPORTS CONTAIN EMPTY FIELDS. IN SOME CASES, THIS
RESULTS IN A LONG PRINTED REPORT WITH INFORMATION IN
ONLY A FEW FIELDS. IT IS PREFERRED THAT USERS HAVE THE
OPTION OF CHOOSING TO PRINT OR NOT TO PRINT EMPTY FIELDS.
2-14.1 (11) THE VENDOR SHALL DESCRIBE ANY REPORTS OFFERED AS PART OF
THEIR PROPOSED CAD/RMS/JMS APPLICATION THAT ARE NOT
REQUIRED HEREAFTER.
2-14.2 SYSTEM ADMINISTRATION REPORTS
2-14.2 (1) THE PROPOSED CAD/RMS/JMS APPLICATION SHALL INCLUDE A
LOGON REPORT THAT SHOWS THE TIME AND LOCATION OF EACH
USER LOGGING ON OR OFF THE SYSTEM FOR ANY GIVEN DATE.
2-14.2 (2) THE PROPOSED CAD/RMS/JMS APPLICATION SHALL INCLUDE A
WORKSTATION LOGON REPORT THAT SHOWS ALL USERS LOGGING
ON OR OFF THE SYSTEM ON A GIVEN WORKSTATION FOR ANY
GIVEN DATE.
2-14.2 (3) THE PROPOSED CAD/RMS/JMS APPLICATION SHALL INCLUDE A
REPORT THAT LISTS ALL PERSONS WHO HAVE PRINTED ANY OR
ALL FORMS ASSOCIATED WITH A GIVEN RECORD.
2-14.2 (4) THE PROPOSED CAD/RMS/JMS APPLICATION SHALL INCLUDE A
REPORT THAT SHOWS THE SYSTEM ADMINISTRATOR OR
AUTHORIZED USER ALL MASTER INDEX ENTRIES ADDED FOR A
USER SPECIFIED DATE AND TIME RANGE.
2-15 LOCATION SPECIFICATIONS
2-15.1 (1) ALL LOCATION DATA-SETS MUST CONTAIN X-Y COORDINATE
FIELDS
2-15.1 (2) THE PROPOSED CAD/RMS/JMS APPLICATION SHALL VERIFY EACH
ADDRESS ENTERED INTO ANY LOCATION FIELD SYSTEM WIDE
AGAINST THE SYSTEM GEOFILE.
2-15.1 (3) THE PROPOSED CAD/RMS/JMS APPLICATION SHALL ALLOW THE
USER TO RE-VERIFY ANY ADDRESS ENTERED INTO ANY LOCATION
FIELD SYSTEM WIDE AGAINST THE SYSTEM GEOFILE.
2-15.1 (4) THE PROPOSED APPLICATION SHALL ALLOW A USER TO BYPASS
THE ADDRESS VERIFICATION ROUTINE IF A CORRECT ADDRESS
CANNOT BE FOUND.
City of Fort Collins lxxiv Proposal P-847
2-15.1 (5) IN ORDER TO BYPASS ADDRESS VERIFICATION THE USER WILL BE
REQUIRED TO MANUALLY ENTER AN ADDRESS OR X-Y (NAD 83
STATE PLANE) COORDINATE.
2-15.1 (6) THE SYSTEM MUST BE ABLE TO DIRECTLY ENTER X-Y
COORDINATES (NAD 83 STATE PLANE) ON ANY LOCATION ENTRY.
2-15.1 (7) IT IS PREFERRED THAT THE USER BE ABLE TO SELECT X-Y
COORDINATES WITH THE USE OF A GRAPHICAL TOOL (POINT AND
CLICK ON A MAP).
2-15.1 (8) VALID LOCATION MUST DETERMINABLE BY X-Y COORDINATE
ALONE (ALL DISTRICTS AND AGENCIES ASSIGNED).
2-15.1 (9) THE PROPOSED APPLICATION SHALL NOTE EACH INSTANCE OF A
BYPASSED ADDRESS SO THAT THE SYSTEM ADMINISTRATOR OR
OTHER AUTHORIZED USER CAN MAKE THE APPROPRIATE
CORRECTIONS TO THE GEOFILE.
2-15.1 (10) THE PROPOSED APPLICATION SHALL ALLOW FOR THE TRANSFER
AND DISPLAY OF ADDRESS AND X-Y COORDINATES FROM CAD INTO
THE RMS/JMS.
2-16 MAPPING
2-16.1 GENERAL REQUIREMENTS
2-16.1 (1) MAPPING IMAGES SHALL BE STORED LOCALLY ON EACH
WORKSTATION AND MOBILE TO MINIMIZE BANDWIDTH USAGE.
2-16.1 (2) THE PROPOSED SYSTEM SHALL UTILIZE A SINGLE COORDINATE-
BASED MAPPING FILE (GEOFILE) FOR CAD, RMS AND ALL OTHER
APPLICATIONS (NAD 83 STATE PLANE).
2-16.1 (3) THE PROPOSED APPLICATION SHALL UTILIZE A SINGLE
APPLICATION FOR CREATING, UPDATING AND MAINTAINING THE
SHARED GEOFILE. GEOFILE MAINTENANCE WILL BE SHARED
BETWEEN MULTIPLE AGENCIES.
2-16.1 (4) THE MAPPING SYSTEM WILL SUPPORT THE ABILITY TO LOCATE A
POSITION ON ALL MAP PROJECTIONS ON THE FLY BY USING
LATITUDE/LONGITUDE COORDINATES.
2-16.1 (5) SYSTEM MUST HAVE THE ABILITY TO TRANSLATE AND DISPLAY
STORED NAD 83 STATE PLANE COORDINATES TO A DISPLAY ONLY
OF LATITUDE/LONGITUDE COORDINATES (VENDOR MUST ATTACH
AN EXPLANATION AS TO HOW THEY WOULD ACCOMPLISH THIS).
City of Fort Collins lxxv Proposal P-847
2-16.1 (6) THE PROPOSED MAPPING APPLICATION SHALL SUPPORT AT LEAST
256 SEPARATE LAYERS FOR SEPARATING LINE AND TEXT DATA.
2-16.1 (7) THE PROPOSED APPLICATION SHALL HAVE THE ABILITY TO
IMPORT BOTH DATABASE INFORMATION AND GRAPHIC ELEMENTS
FROM THE FOLLOWING MAPPING SYSTEMS:
2-16.1 (7.1) ESRI GIS FILE FORMATS,
2-16.1 (7.2) AUTOCAD,
2-16.1 (7.3) AND MAP INFO.
2-16.1 (8) THE VENDOR SHALL DESCRIBE HOW THE IMPORT OF DATA FROM
OTHER GIS SYSTEMS IS ACCOMPLISHED AND THE STEPS WHICH
ARE REQUIRED TO MERGE THAT INFORMATION WITH EXISTING
GEOFILE DATA (VENDOR MUST ATTACH AN EXPLANATION AS TO
HOW THEY WOULD ACCOMPLISH THIS).
2-16.1 (9) THE PROPOSED APPLICATIONS SHALL UTILIZE THE SHARED
GEOFILE EACH TIME A LOCATION MUST BE VALIDATED BY ANY
VENDOR-SUPPLIED APPLICATION.
2-16.1 (10) THE PROPOSED APPLICATION SHALL UTILIZE THE SHARED
GEOFILE TO DETERMINE:
2-16.1 (10.1) WHAT JURISDICTION THE ADDRESS IS IN.
2-16.1 (10.2) IF THE ADDRESS IS WITHIN THE CITY, TO DETERMINE THE
PATROL DISTRICT, AND
2-16.1 (10.3) THE X-Y COORDINATES.
2-16.1 (11) THE PROPOSED APPLICATIONS SHALL USE THE COORDINATES
PROVIDED BY THE GEOFILE WHENEVER A LOCATION MUST BE
PLOTTED ON A MAP FOR DISPLAY.
2-16.2 VENDOR SUPPLIED GEOFILE
In cooperation with Larimer County and surrounding municipalities, the City of Fort
Collins participated in the development of a number of countywide, GIS data sets.
These data sets include: street centerline with address ranges, city boundaries, police
jurisdictions, fire jurisdictions, ambulance jurisdictions, ZIP Code boundaries, and ESN
boundaries. These data sets are maintained by a vendor, which receives update
information from the participating agencies and produces a complete update of the data
sets on a monthly basis. These data sets are maintained in ESRI coverage and shapefile
formats in NAD83, State Plane.
City of Fort Collins lxxvi Proposal P-847
The city, Larimer County, and other agencies within Larimer County also maintain a
number of other data sets within their respective agencies. These data sets would
include common-places, parks, school, railroad lines, etc. These data sets are generally
maintained in an ESRI format, but may also be AutoCAD.
2-16.2 (1) VENDORS SHALL PROVIDE EXPLANATION OF HOW THEY WILL
SUPPLY A COORDINATE-BASED GEOFILE, WHICH WILL MEET THE
REQUIREMENTS LISTED BELOW.
2-16.2 (2) THE VENDOR SHALL SUPPLY A GEOFILE, WHICH IS BASED UPON
AND DERIVED FROM THE DATA SETS THAT ARE MAINTAINED BY
THE CITY, LARIMER COUNTY AND THE SURROUNDING AGENCIES.
2-16.2 (3) THE VENDOR SHALL SUPPLY A COMPLETE AND DETAILED
EXPLANATION OF ADDITIONS, CHANGES AND/OR CORRECTIONS
THAT MUST BE PERFORMED ON THE AVAILABLE DATA SETS IN
ORDER TO MAKE THEM COMPATIBLE WITH THE SUPPLIED SYSTEM
IN ORDER TO MEET ALL FUNCTIONALITY REQUIREMENTS. THIS
INCLUDES COMPLETE ADDRESS ERROR CHECKING TO ENSURE
THAT ALL ADDRESSES CONTAINED WITHIN THE STREET
CENTERLINE DATA SET ARE AVAILABLE FOR CALL VERIFICATION
WITHIN THE SYSTEM.
2-16.2 (4) THE VENDOR SHALL ENSURE A FINAL PRODUCT USED BY THE
SYSTEM AS A GEOFILE WHICH INCLUDES THE NAME, COORDINATE
LOCATION AND AN ASSOCIATED GRAPHIC ELEMENTS FOR EACH OF
THE FOLLOWING:
2-16.2 (4.1) STREETS,
2-16.2 (4.2) PARKS,
2-16.2 (4.3) SCHOOLS,
2-16.2 (4.4) FIRE, POLICE AND AMBULANCE STATIONS,
2-16.2 (4.5) COMMON PLACES,
2-16.2 (4.6) INTERSTATE AND STATE HIGHWAYS,
2-16.2 (4.7) BOUNDARY FOR EACH POLITICAL ENTITY/DISTRICT,
2-16.2 (4.8) BOUNDARY FOR EACH OF THE PATROL DISTRICTS, INCLUDING
SUB-JURISDICTIONS,
2-16.2 (4.9) WATER FEATURES INCLUDING LAKES, STREAMS AND
RESERVOIRS,
City of Fort Collins lxxvii Proposal P-847
2-16.2 (4.10) RAILROAD TRACKS,
2-16.2 (4.11) AND BOUNDARIES FOR EACH ESN.
2-16.2 (5) THE VENDOR SHALL ENSURE THAT THE GEOFILE HAS A
POSITIONAL ACCURACY OF NOT LESS THAN THREE METERS FOR
ALL DATABASE RECORDS AND GRAPHIC ELEMENTS. THUS
GRAPHIC ELEMENTS SHOWN ON THE SCREEN ARE WITHIN THREE
METERS OF THEIR ACTUAL POSITION IN THE WORLD.
2-16.3 GEOFILE MAINTENANCE TOOLS
2-16.3 (1) THE CITY OF FORT COLLINS AND LARIMER COUNTY DESIRES TO
CONTINUE TO USE THE EXISTING MAINTENANCE PROCEDURES
THAT CURRENTLY EXIST AS A COOPERATIVE EFFORT WITH THE
SURROUNDING AGENCIES. THE PROPOSED MAINTENANCE
APPLICATION SHALL PROVIDE FOR THE COMPLETE EXCHANGE OF
ALL INDIVIDUAL GEOFILE DATA ELEMENTS, SUCH AS STREET
CENTERLINE, CITY BOUNDARIES, ETC.
2-16.3 (2) THE VENDOR SHALL PROVIDE A DETAILED EXPLANATION OF HOW
THE MAINTENANCE PROCESS WILL BE ACCOMPLISHED GIVEN
THAT SOME, OR POSSIBLY ALL, OF THE DATA SETS WILL BE
MAINTAINED OUTSIDE OF THE SYSTEM AS A PART OF A SEPARATE
MAINTENANCE PROCESS.
2-16.3 (3) THE PROPOSED MAINTENANCE APPLICATION SHALL INCLUDE
TOOLS FOR:
2-16.3 (3.1) GRAPHICALLY CREATING, EDITING AND MAINTAINING A
COORDINATE-BASED GEOFILE,
2-16.3 (3.2) GRAPHICALLY CREATING, EDITING AND MAINTAINING
GEOGRAPHIC BOUNDARIES SUCH AS REPORTING DISTRICTS,
PATROL DISTRICTS, CITY BOUNDARIES, FIRE AND AMBULANCE
BOUNDARIES AND OTHER GEOGRAPHIC AREAS AND
ASSOCIATING THESE WITH A DATABASE RECORD,
2-16.3 (3.3) GRAPHICALLY CREATING, EDITING, AND MAINTAINING
GEOGRAPHIC FEATURES SUCH AS LAKES, PARKS, RAILROAD
TRACKS OR SCHOOLS AND ASSOCIATING THESE WITH A
DATABASE RECORD,
2-16.3 (3.4) GRAPHICALLY SELECTING THE DATABASE RECORDS
ASSOCIATED WITH A GRAPHIC ELEMENT BY USE OF A POINTING
DEVICE SO THAT THE UNDERLYING DATABASE RECORD CAN BE
MODIFIED,
City of Fort Collins lxxviii Proposal P-847
2-16.3 (3.5) ADDING NEW STREETS, AND OTHER GEOGRAPHICAL ELEMENTS
THROUGH ON-SCREEN DIGITIZING OR DRAWING,
2-16.3 (3.6) ADDING NEW STREETS AND OTHER GEOGRAPHIC ELEMENTS BY
IMPORT FROM OTHER ELECTRONIC SOURCES,
2-16.3 (3.7) ADDING NEW STREETS, AND OTHER GEOGRAPHICAL ELEMENTS
BY RECEIVING GEOGRAPHIC COORDINATE UPDATES FROM AN
AVL EQUIPPED VEHICLE AS IT IS MOVING,
2-16.3 (3.8) CREATING NEW GEOGRAPHIC AREAS BY SELECTING MANY
INDIVIDUAL GEOGRAPHIC ELEMENTS (E.G. STREETS AND
INTERSECTIONS) SIMULTANEOUSLY AND THEN MAKING A LIKE
UPDATE TO THEIR RESPECTIVE DATABASE RECORDS,
2-16.3 (3.9) AND MODIFYING MAPS TO INCLUDE ROAD AND BRIDGE
CLOSURES, BOTH PERMANENT AND TEMPORARY.
2-16.3 (4) THE PROPOSED APPLICATION SHALL PROVIDE A REPORTING TOOL
THAT WILL IDENTIFY CONFLICTS IN GEO-FILE ADDRESS
RESOLUTION ACROSS THE GEO-FILE. INCLUDING RANGE
OVERLAPS, RANGE GAPS ETC.
2-16.3 (5) THE MAINTENANCE APPLICATION SHALL DISPLAY THE MAP
COORDINATE POSITION OF THE POINTING DEVICE AT ALL TIMES
(STATE PLANE OR LATITUDE/LONGITUDE DISPLAY).
2-16.3 (6) FOR CLARITY, THE MAINTENANCE MODULE SHALL HAVE THE
ABILITY TO ASSIGN UNIQUE COLOR CODES TO GRAPHIC ELEMENTS
SUCH AS STREETS, PARKS, SCHOOLS, BRIDGES AND RIVERS.
2-16.3 (7) THE MAINTENANCE MODULE SHALL HAVE THE ABILITY TO ADD
LABELS TO GRAPHIC ATTRIBUTES SUCH AS STREETS AND PARKS
ON THE MAP AND DISPLAY THE LABELS ON THE MAP.
2-16.3 (8) THE MAINTENANCE MODULE SHALL HAVE THE ABILITY TO PRINT
SELECTED PORTIONS OF THE MAPS TO PRINTERS AND PLOTTERS.
2-16.4 MAP DISPLAY
2-16.4 (1) THE PROPOSED MAPPING APPLICATION SHALL ALLOW THE USER
TO DISPLAY ANY NUMBER OR COMBINATION OF THE MAP LAYERS
AT ONE TIME.
2-16.4 (2) THE PROPOSED MAPPING APPLICATION SHALL ALLOW THE USER
TO PAN AND ZOOM THE MAP DISPLAY EITHER WITH A MOUSE OR
WITH KEYBOARD CONTROLS.
City of Fort Collins lxxix Proposal P-847
2-16.4 (3) THE PROPOSED MAPPING APPLICATION SHALL ALLOW THE USER
TO RETRIEVE A DIFFERENT MAP VIEW BY ADDRESS OR COMMON
PLACE NAME.
2-16.4 (4) THE PROPOSED MAPPING APPLICATION SHALL PROVIDE A SINGLE
CONTINUOUS MAP AND SHALL NOT REQUIRE THE USER TO
RETRIEVE ANOTHER MAP “PAGE” WHEN THE EDGE OF ONE PAGE IS
REACHED.
2-16.4 (5) THE MAP DISPLAY SYSTEM SHALL DISPLAY PROGRESSIVELY MORE
DETAIL AS THE ZOOM LEVEL IS INCREASED.
2-16.4 (6) THE PROPOSED APPLICATION SHALL AUTOMATICALLY SIZE ICONS
AND OBJECTS AFTER A ZOOM-IN OR ZOOM-OUT SO THAT THEY
REMAIN THE SAME SIZE RELATIVE TO THE MAP VIEW.
2-16.4 (7) THE PROPOSED APPLICATION SHALL ALLOW THE SYSTEM
ADMINISTRATOR OR OTHER AUTHORIZED USER TO DETERMINE
WHICH LABELS DISPLAY AT EACH ZOOM LEVEL. FOR EXAMPLE, AS
THE USER VIEWS A LARGER MAP THEY MAY ONLY SEE LABELS FOR
THE MAJOR ARTERIAL AS OPPOSED TO LABELS FOR EVERY
STREET.
2-16.4 (8) THE PROPOSED APPLICATION SHALL ALLOW THE SYSTEM
ADMINISTRATOR OR OTHER AUTHORIZED USER TO DETERMINE
WHICH LAYERS OF THE MAP WILL DISPLAY AT EACH ZOOM LEVEL.
FOR EXAMPLE, WATER FEATURES MAY ONLY BE DISPLAYED ON
MAPS OF NEIGHBORHOODS AND NOT ON A WHOLE CITY MAP.
2-16.4 (9) IT IS PREFERRED THAT THE PROPOSED APPLICATION HAVE THE
ABILITY TO RECOMMEND DIFFERENT RESOURCES BASED ON A
STREET DIRECTION. FOR EXAMPLE, NORTHBOUND I-70 WILL
RECEIVE A DIFFERENT RECOMMENDATION THAN SOUTHBOUND I-
70 IN THE SAME LOCATION.
2-16.4 (10) IT IS PREFERRED THAT THE PROPOSED APPLICATION HAVE THE
ABILITY TO RECOMMEND DIFFERENT RESOURCES FOR EVENTS
OCCURRING ON THE STREET AS OPPOSED TO AT AN ADDRESS ON
THAT SAME STREET. FOR EXAMPLE, SOME STREETS IN THE CITY
ARE THE RESPONSIBILITY OF THE STATE, WHILE HOUSES LOCATED
ON THOSE STREETS ARE THE CITY’S JURISDICTION (VENDOR MUST
ATTACH AN EXPLANATION AS TO HOW THEY WOULD ACCOMPLISH
THIS).
2-16.4 (11) IT IS PREFERRED THAT THE PROPOSED MAPPING APPLICATION
ENABLE THE SYSTEM ADMINISTRATOR OR OTHER AUTHORIZED
USER TO ASSOCIATE NAMES WITH COMMON MAP VIEWS. FOR
EXAMPLE, A MAP VIEW SHOWING ALL STREETS WITHIN THE CITY
City of Fort Collins lxxx Proposal P-847
WITH MAJOR ARTERIALS LABELED MIGHT BE CALLED “CITY”.
ANOTHER VIEW MIGHT BE NAMED “NEIGHBORHOOD”. THIS VIEW
MIGHT SHOW A ½ MILE SQUARE AREA WITH ALL THE STREETS
LABELED, WITH PARKS, SCHOOLS AND RAILROAD TRACKS SHOWN.
THUS IF A USER IS VIEWING A MAP DISPLAY AND CHOOSES THE
“NEIGHBORHOOD” VIEW THE MAP WILL AUTOMATICALLY DISPLAY
THE PROPER ZOOM LEVEL AND FEATURES DEFINED FOR THAT
VIEW.
2-16.4 (12) THE PROPOSED APPLICATION SHALL ALLOW THE SYSTEM
ADMINISTRATOR OR OTHER AUTHORIZED USER TO CONFIGURE
THE NOTATION ACCOMPANYING EACH GRAPHIC SYMBOL. FOR
EXAMPLE, THE OPTION TO LIST THE EVENT NUMBER AND STATUS
ALONGSIDE AN EVENT SYMBOL.
2-16.4 (13) THE PROPOSED APPLICATION SHALL HAVE THE ABILITY TO
DISPLAY THE AVL REPORTED LOCATION OF FIELD UNITS ON THE
MAP.
2-16.4 (14) THE PROPOSED SYSTEM SHALL NOT BE DELAYED BY THE
REDRAWING OF A MAP OR BY THE CONSTANT CHANGES
ASSOCIATED WITH AVL LOCATION REPORTS.
2-17 PERSONNEL DATABASE
2-17.1 GENERAL REQUIREMENTS
2-17.1 (1) THE PROPOSED RMS/JMS APPLICATION SHALL INCLUDE A SHARED
PERSONNEL SYSTEM.
2-17.1 (2) EMPLOYEE PERSONAL INFORMATION IN REGARDS TO ALL
PERSONNEL SYSTEM FUNCTION MUST NOT BE A PART OF THE
MASTER NAME INDEX (INCLUDING DEMOGRAPHICS FOR
EMPLOYEES).
2-17.1 (3) PERSONNEL FILE VIEWING MUST BE RESTRICTED TO ONLY THOSE
PERSONS GRANTED PERMISSION BY THE SYSTEM ADMINISTRATOR.
2-17.1 (4) THE ABILITY TO MAKE CHANGES TO THE FILE MUST BE FURTHER
RESTRICTABLE AND THE DATES OF ANY CHANGES MUST BE
RECORDED AND WHO MADE THE CHANGES.
2-17.1 (5) AT A MINIMUM, THE PROPOSED PERSONNEL SYSTEM SHALL
CAPTURE THE FOLLOWING INFORMATION FOR EACH
APPLICANT/EMPLOYEE:
2-17.1 (5.1) STATUS (PRE-HIRE, CURRENT EMPLOYEE, RESERVE, VOLUNTEER,
EX EMPLOYEE, ETC.)
City of Fort Collins lxxxi Proposal P-847
2-17.1 (5.2) AGENCY
2-17.1 (5.3) EMPLOYEE ID AND/OR BADGE NUMBER (ALPHA/NUMERIC,
MINIMUM OF 8 CHARACTERS),
2-17.1 (5.4) FULL NAME (LAST, FIRST AND MIDDLE), WITH SUPPORT FOR
HYPHENATED LAST NAMES AND NAME SUFFIXES,
2-17.1 (5.5) DATE AND PLACE OF BIRTH,
2-17.1 (5.6) CURRENT AGE (CONTINUOUSLY CALCULATED FROM DOB),
2-17.1 (5.7) SOCIAL SECURITY NUMBER,
2-17.1 (5.8) DRIVERS LICENSE NUMBER AND EXPIRATION DATE,
2-17.1 (5.9) PHYSICAL DESCRIPTION THAT INCLUDES; GENDER,
RACE/ETHNICITY, HEIGHT, WEIGHT, EYE AND HAIR COLOR,
2-17.1 (5.10) DIGITAL PHOTO,
2-17.1 (5.11) BLOOD TYPE,
2-17.1 (5.12) HOME ADDRESS THAT INCLUDES; STREET NUMBER & NAME, PO
BOX, CITY, STATE, AND ZIP,
2-17.1 (5.13) APPLICANT WORK NAME AND ADDRESS THAT INCLUDES; STREET
NUMBER & NAME, PO BOX, CITY, STATE, AND ZIP,
2-17.1 (5.14) AT LEAST FOUR FIELDS FOR TELEPHONE, MOBILE PHONE, AND
PAGER NUMBERS,
2-17.1 (5.15) EMAIL ADDRESS,
2-17.1 (5.16) MARITAL STATUS,
2-17.1 (5.17) EMERGENCY CONTACT INFORMATION THAT INCLUDES; FULL
NAME, RELATION, HOME ADDRESS & PHONE, WORK ADDRESS
AND PHONE, AND MOBILE PHONE,
2-17.1 (5.18) INOCULATIONS,
2-17.1 (5.19) ALLERGIES (FREE TEXT TO ACCOMMODATE 3 ENTRIES)
2-17.1 (5.20) PRIMARY CARE PHYSICIAN,
2-17.1 (5.21) EMERGENCY MEDICAL INFORMATION,
2-17.1 (5.22) DATES OF PHYSICAL INJURIES WITH COMMENTS,
City of Fort Collins lxxxii Proposal P-847
2-17.1 (5.23) DATES OF PHYSICAL EXAMS WITH PASS/FAIL RATING AND
COMMENTS,
2-17.1 (5.24) SPECIAL SKILLS SUCH AS LANGUAGES,
2-17.1 (5.25) DATE OF SKILLS CERTIFICATION (IF APPLICABLE),
2-17.1 (5.26) LEVEL OF FORMAL EDUCATION,
2-17.1 (5.27) OUTSIDE DEGREES, CERTIFICATES AND EDUCATIONAL EFFORTS,
2-17.1 (5.28) DATE OF HIRE,
2-17.1 (5.29) DATE OF STATUS CHANGE (PROMOTION, REASSIGNMENT, ETC.)
2-17.1 (5.30) NOMINAL PROBATION PERIOD,
2-17.1 (5.31) DATE OF PROBATION COMPLETION,
2-17.1 (5.32) FLAG TO INDICATE RE-HIRE (FORCED CHOICE)
2-17.1 (5.33) DATE OF TERMINATION,
2-17.1 (5.34) REASON FOR TERMINATION,
2-17.1 (5.35) DATES OF PREVIOUS EMPLOYMENT (TO ACCOMMODATE 2
PREVIOUS EMPLOYMENT DATES),
2-17.1 (5.36) DATES OF PREVIOUS TERMINATION (TO ACCOMMODATE 2
PREVIOUS TERMINATION DATES),
2-17.1 (5.37) REASONS OF PREVIOUS TERMINATION (TO ACCOMMODATE 2
PREVIOUS TERMINATION DATES),
2-17.1 (5.38) CURRENT SHIFT,
2-17.1 (5.39) CURRENT ASSIGNMENT TO INCLUDE;
2-17.1 (5.39.1) DIVISION,
2-17.1 (5.39.2) SECTION,
2-17.1 (5.39.3) UNIT,
2-17.1 (5.39.4) AND JOB TITLE.
2-17.1 (5.40) CURRENT SUPERVISOR.
2-17.1 (5.41) ALL PREVIOUS ASSIGNMENTS BY DATE,
City of Fort Collins lxxxiii Proposal P-847
2-17.1 (5.42) TRANSFER INFORMATION (NO LIMIT ON NUMBER) THAT
INCLUDES;
2-17.1 (5.42.1) DATE OF TRANSFER,
2-17.1 (5.42.2) AND REASON FOR TRANSFER.
2-17.1 (5.43) SPECIAL ASSIGNMENTS (CONCURRENT TO REGULAR
ASSIGNMENT, NO LIMIT ON NUMBER) TO INCLUDE THE
FOLLOWING;
2-17.1 (5.43.1) NAME OF ASSIGNMENT,
2-17.1 (5.43.2) DATE OF ASSIGNMENT,
2-17.1 (5.43.3) AND DATE OF COMPLETION OF ASSIGNMENT.
2-17.1 (5.44) CURRENT RANK,
2-17.1 (5.45) A FLAG TO INDICATE STATUS AS A SWORN OFFICER,
2-17.1 (5.46) SENIORITY DATE BY CURRENT ASSIGNMENT.
2-17.1 (5.47) SENIORITY DATE DEPARTMENT WIDE.
2-17.1 (5.48) PREVIOUS RANKS WITH DATES OF PROMOTION,
2-17.1 (5.49) COMMENDATIONS AND DATES RECEIVED,
2-17.1 (5.50) DISCIPLINARY ACTIONS TAKEN, REASONS FOR EACH AND DATES,
2-17.1 (5.51) AND MANUALS ISSUED (FORCED CHOICE W/FREE TEXT).
2-17.2 EVALUATION PROCESS
2-17.2 (1) THE EVALUATIONS MODULE SHALL ONLY BE ACCESSIBLE BY THE
DESIGNATED SUPERVISORY PERSONNEL OR INDIVIDUALS
SPECIFIED BY SYSTEM ADMINISTRATOR.
2-17.2 (2) COMPLETED EVALUATIONS SHALL BE VIEWABLE BY THE
EMPLOYEE AND SUPERVISORS IN EMPLOYEE’S CHAIN OF
COMMAND OR INDIVIDUALS SPECIFIED BY SYSTEM
ADMINISTRATOR.
2-17.2 (3) THE EVALUATION SHALL FOLLOW A REVIEW PROCESS
CONFIGURABLE BY PARTICIPATING AGENCIES AND THE
EVALUATION WILL BE ABLE TO BE “LOCKED” WHEN DESIGNATED
REVIEWS HAVE BEEN COMPLETED.
City of Fort Collins lxxxiv Proposal P-847
2-17.2 (4) THE EVALUATION MODULE SHALL HAVE THE ABILITY TO STORE,
FOR IMMEDIATE RETRIEVAL BY THE EMPLOYEE OR AUTHORIZED
SUPERVISOR(S), THE CURRENT AND TWO PREVIOUS EVALUATIONS.
2-17.2 (4.1) IT IS PREFERRED THAT THE EVALUATION MODULE BE
CONFIGURABLE TO STORE AN AGENCY DEFINED NUMBER OF
EVALUATIONS.
2-17.2 (4.2) IT IS PREFERRED THAT THE EVALUATION MODULE WILL DELETE
THE OLDEST EVALUATION, AS CONFIGURED BY PARTICIPATING
AGENCIES, WHEN A NEW EVALUATION IS ENTERED INTO THE
SYSTEM WITHOUT SPECIFIC ACTION OF RATING OFFICIAL.
2-17.2 (5) THE EVALUATION MODULE SHALL HAVE THE ABILITY FOR THE
SYSTEM ADMINISTRATOR TO CONFIGURE THE EVALUATION
GROUPS BY AGENCY SELECTED FIELDS SUCH AS, BUT NOT LIMITED
TO:
2-17.2 (5.1) RANK,
2-17.2 (5.2) DIVISION (ASSIGNMENT),
2-17.2 (5.3) TYPE OF EVALUATION FROM A PICK LIST (MONTHLY, INTERIM,
YEARLY).
2-17.2 (6) EVALUATION MODULE SHALL BE ABLE TO DISPLAY, ON SCREEN OR
IN PRINT FORMAT, A LIST OF EVALUATIONS DUE WITHIN A
SPECIFIED DATE RANGE TO INCLUDE AT A MINIMUM:
2-17.2 (6.1) NAME,
2-17.2 (6.2) RANK,
2-17.2 (6.3) CURRENT PAY LEVEL
2-17.2 (6.4) DUE DATE,
2-17.2 (6.5) DATE OF LAST EVALUATION,
2-17.2 (6.6) SUPERVISOR,
2-17.2 (6.7) AND TRAINING/EDUCATION COMPLETED FOR SPECIFIED DATE
RANGE.
2-17.3 INTERNAL AFFAIRS
2-17.3 (1) IN ADDITION TO THE STANDARD INVESTIGATIVE RECORDS
MAINTAINED BY INTERNAL AFFAIRS THE PROPOSED SYSTEM
City of Fort Collins lxxxv Proposal P-847
SHALL RECORD THE FOLLOWING INFORMATION ABOUT
DISCIPLINARY ACTIONS:
2-17.3 (1.1) THE NAME, ADDRESS, AND PHONE NUMBER OF THE
COMPLAINANT,
2-17.3 (1.2) THE DATE OF THE ORIGINAL COMPLAINT,
2-17.3 (1.3) THE NATURE OF THE COMPLAINT,
2-17.3 (1.4) THE OFFICER IN CHARGE OF THE INVESTIGATION,
2-17.3 (1.5) THE DISCIPLINARY ACTION TAKEN, AND
2-17.3 (1.6) A NARRATIVE FIELD.
2-17.4 HIRING PROCESS
The Proposed RMS/JMS application shall contain a system specifically to track the
hiring process for all new employees.
2-17.4 (1) THE HIRING TRACKING SYSTEM SHALL BE LINKED TO, CAPTURE,
AND DISPLAY ALL PERSONAL INFORMATION CAPTURED BY THE
PERSONNEL SYSTEM.
2-17.4 (2) UPON EMPLOYMENT THE SYSTEM SHALL NOT REQUIRE THE RE-
ENTRY OF ANY DATA CAPTURED AND TRACKED BY THE
PERSONNEL DATABASE.
2-17.4 (3) THE HIRING TRACKING SYSTEM SHALL ALLOW FOR TRACKING
MULTIPLE APPLICANT PROCESSES FOR THE SAME PERSON, BOTH
CONCURRENTLY AND CONSECUTIVELY.
2-17.4 (3.1) THE SYSTEM MUST STORE THE RESULTS (PER APPLICATION) OF
ALL APPLICATIONS A PERSON HAS SUBMITTED.
2-17.4 (3.2) THE SYSTEM MUST CLEARLY INDICATE THE NUMBER OF
CONCURRENT PRE-HIRE PROCESSES A PERSON IS INVOLVED
WITH WHENEVER VIEWING THAT PERSON’S RECORD.
2-17.4 (3.3) THE SYSTEM MUST CLEARLY DISPLAY (PER APPLICATION) THE
MASTER STATUS AND WHAT STAGE OF TESTING APPLICANT IS AT
DURING THE PRE-HIRE PROCESSES WHENEVER VIEWING THAT
PERSON’S RECORD.
2-17.4 (4) SYSTEM MUST CAPTURE ALL INFORMATION RELATING TO EACH
APPLICATION PROCESS THAT INCLUDES THE FOLLOWING:
2-17.4 (4.1) DATE APPLICATION RECEIVED,
City of Fort Collins lxxxvi Proposal P-847
2-17.4 (4.2) WRITTEN EXAM INFORMATION;
2-17.4 (4.2.1) TEST DATE,
2-17.4 (4.2.2) TEST TIME,
2-17.4 (4.2.3) SCORE,
2-17.4 (4.2.4) MILITARY POINTS,
2-17.4 (4.2.5) TOTAL TEST SCORE,
2-17.4 (4.2.6) FAILED TO APPEAR (FTA)/WITHDREW (WD),
2-17.4 (4.2.7) AND COMMENTS (FREE TEXT).
2-17.4 (4.3) PHYSICAL AGILITY TESTING;
2-17.4 (4.3.1) TEST DATE,
2-17.4 (4.3.2) PASS/FAIL/FAILED TO APPEAR (FTA)/WITHDREW (WD),
2-17.4 (4.3.3) AND COMMENTS (FREE TEXT).
2-17.4 (4.4) BACKGROUND INVESTIGATION;
2-17.4 (4.4.1) INVESTIGATOR,
2-17.4 (4.4.2) PASS/FAIL,
2-17.4 (4.4.3) AND COMMENTS (FREE TEXT).
2-17.4 (4.5) POLYGRAPH;
2-17.4 (4.5.1) DATE,
2-17.4 (4.5.2) PASS/FAIL/FAILED TO APPEAR (FTA)/WITHDREW (WD),
2-17.4 (4.5.3) AND COMMENTS (FREE TEXT).
2-17.4 (4.6) ORAL BOARD;
2-17.4 (4.6.1) DATE,
2-17.4 (4.6.2) PASS/FAIL/FAILED TO APPEAR (FTA)/WITHDREW (WD),
2-17.4 (4.6.3) AND COMMENTS (FREE TEXT).
2-17.4 (4.7) PSYCHOLOGICAL;
City of Fort Collins lxxxvii Proposal P-847
2-17.4 (4.7.1) DATE OF EXAM,
2-17.4 (4.7.2) PSYCHOLOGIST,
2-17.4 (4.7.3) PASS/FAIL/FAILED TO APPEAR (FTA)/WITHDREW (WD),
2-17.4 (4.7.4) AND COMMENTS (FREE TEXT).
2-17.4 (4.8) PHYSICAL;
2-17.4 (4.8.1) DATE,
2-17.4 (4.8.2) PASS/FAIL/FAILED TO APPEAR (FTA)/WITHDREW (WD),
2-17.4 (4.8.3) AND COMMENTS (FREE TEXT).
2-17.4 (5) SYSTEM MUST BE ABLE TO EXPORT A TABLE OF PRE-HIRE
APPLICANTS AS SPECIFIED BY PERSONNEL STAFF TO DRIVE MAIL
MERGE PROCESSES.
2-17.5 SCHEDULING AND ATTENDANCE
2-17.5 (1) THE PROPOSED SCHEDULING SYSTEM SHALL INCLUDE A
COMPREHENSIVE WORK TRACKING SYSTEM THAT TRACKS CALLS
FOR SERVICE, COMMUNITY SERVICE, AND INVESTIGATIVE
ACTIVITIES CARRIED OUT BY INDIVIDUAL EMPLOYEES.
2-17.5 (2) THE PROPOSED SCHEDULING SYSTEM SHALL HAVE THE ABILITY
TO CREATE A DAILY ACTIVITY REPORT FOR A PATROL OFFICER OR
INVESTIGATOR THAT INCLUDES A CHRONOLOGICAL RECITATION
OF:
2-17.5 (2.1) CALLS FOR SERVICE,
2-17.5 (2.2) TRAFFIC STOPS,
2-17.5 (2.3) PEDESTRIAN STOPS,
2-17.5 (2.4) INVESTIGATIVE ACTIVITIES,
2-17.5 (2.5) COMMUNITY POLICING PROJECTS (BY PROJECT CODE),
2-17.5 (2.6) TRAINING, AND
2-17.5 (2.7) ADMINISTRATIVE ACTIVITIES.
2-17.5 (3) THE PROPOSED SCHEDULING SYSTEM SHALL INCLUDE THE
ABILITY TO ASSIGN EMPLOYEES TO A SHIFT.
City of Fort Collins lxxxviii Proposal P-847
2-17.5 (4) THE PROPOSED SCHEDULING SYSTEM SHALL ALLOW THE SYSTEM
ADMINISTRATOR OR OTHER AUTHORIZED USER TO DEFINE AN
UNLIMITED NUMBER OF ROTATIONAL SHIFTS.
2-17.5 (5) THE PROPOSED SCHEDULING SYSTEM SHALL INCLUDE THE
CAPABILITY TO DEFINE AT LEAST FIVE SQUADS WITHIN EACH
SHIFT.
2-17.5 (6) EACH SQUAD SHALL HAVE THE ABILITY TO SCHEDULE DIFFERENT
DAYS OFF.
2-17.5 (7) THE SYSTEM ADMINISTRATOR OR OTHER AUTHORIZED USER
SHALL HAVE THE ABILITY TO ASSIGN EMPLOYEES AND OTHER
PERSONNEL TO SQUADS OR SHIFTS.
2-17.5 (8) THE SYSTEM ADMINISTRATOR OR OTHER AUTHORIZED USER WILL
HAVE THE ABILITY TO ASSIGN DAYS OFF, VACATION DAYS,
HOLIDAYS, AND WORK HOURS BY INDIVIDUAL EMPLOYEE.
2-17.5 (9) THE SYSTEM ADMINISTRATOR OR OTHER AUTHORIZED USER
SHALL HAVE THE ABILITY TO ASSIGN DAYS OFF, HOLIDAYS, AND
WORK HOURS TO A SQUAD AND BY ASSOCIATION TO THE
EMPLOYEES ASSIGNED TO THAT SQUAD.
2-17.5 (10) THE PROPOSED PERSONNEL SYSTEM SHALL ALLOW THE SYSTEM
ADMINISTRATOR OR OTHER AUTHORIZED EMPLOYEE TO
DETERMINE MINIMUM STAFFING LEVELS FOR ANY SHIFT.
2-17.5 (10.1) IT IS PREFERRED THAT MINIMUM STAFFING LEVEL FUNCTION
ALLOW THE SYSTEM ADMINISTRATOR OR OTHER AUTHORIZED
EMPLOYEE TO DEFINE REQUIRED POSITIONS. FOR EXAMPLE, IT
MAY BE THAT A SHIFT REQUIRES A MINIMUM OF TWO
SERGEANTS. THE MINIMUM STAFFING FUNCTION SHOULD
MONITOR THIS AND NOT ALLOW A SERGEANT TO TAKE
VACATION IF THAT WILL LEAVE LESS THAN TWO SERGEANTS ON
DUTY FOR THAT SHIFT.
2-17.5 (10.2) IT IS PREFERRED THAT MINIMUM STAFFING LEVEL FUNCTION
ALLOW THE SYSTEM ADMINISTRATOR OR OTHER AUTHORIZED
EMPLOYEE TO DEFINE REQUIRED CAPABILITIES. FOR EXAMPLE,
IT MAY BE THAT A SHIFT REQUIRES A MINIMUM OF ONE CANINE
TEAM. THE MINIMUM STAFFING FUNCTION SHOULD MONITOR
THIS AND NOT ALLOW A CANINE OFFICER TO TAKE VACATION IF
THAT WILL LEAVE THE SHIFT WITH NO CANINE TEAMS.
2-17.5 (11) THE PROPOSED SCHEDULING SYSTEM SHALL ALLOW EMPLOYEES
TO REQUEST VACATION FOR ANY DATE UP TO ONE YEAR IN
City of Fort Collins lxxxix Proposal P-847
ADVANCE, SO LONG AS MINIMUM STAFFING LEVELS HAVE BEEN
MET.
2-17.5 (12) WHEN A VACATION REQUEST IS SUBMITTED, THE SYSTEM WILL
DEDUCT FROM THE AVAILABLE VACATION SLOTS.
2-17.5 (13) THE PROPOSED SCHEDULING SYSTEM SHALL RECORD VACATION
REQUESTS AND SHOW THEM TO THE SCHEDULING SUPERVISOR IN
A DISTINCTIVE MANNER.
2-17.5 (14) THE PROPOSED SCHEDULING SYSTEM SHALL ALLOW EMPLOYEES
TO SCHEDULE SICK LEAVE FOR ANY DATE UP TO ONE YEAR IN
ADVANCE.
2-17.5 (15) WHEN A SICK LEAVE REQUEST IS SUBMITTED, THE SYSTEM WILL
DEDUCT FROM THE AVAILABLE SICK LEAVE SLOTS.
2-17.5 (16) THE PROPOSED SCHEDULING SYSTEM SHALL RECORD SICK LEAVE
REQUESTS AND SHOW THEM TO THE SCHEDULING SUPERVISOR IN
A DISTINCTIVE MANNER.
2-17.5 (17) AT A MINIMUM, THE PROPOSED SCHEDULING SYSTEM SHALL HAVE
THE ABILITY TO HANDLE THE FOLLOWING KINDS OF SHIFTS:
2-17.5 (17.1) EIGHT HOURS, FIVE DAYS A WEEK,
2-17.5 (17.2) TEN HOURS, FOUR DAYS A WEEK,
2-17.5 (17.3) 12 HOURS, 2 ON, 2 OFF, 2 ON, 2 OFF, 2 ON, 2 OFF, 2 ON, 6 OFF,
2-17.5 (17.4) AND 10.75 HOURS, 6 ON (1 TRAINING DAY), 4 OFF, 5 ON, 5 OFF, 4 ON,
4 OFF.
2-17.5 (18) THE PROPOSED SCHEDULING SYSTEM SHALL ALLOW
ADMINISTRATORS AND SUPERVISORS TO MAKE UP A MONTHLY,
WEEKLY AND DAILY SCHEDULE FOR EACH MAJOR UNIT (E.G.
PATROL, TRAFFIC, SIU, INVESTIGATIONS, ETC.)
2-17.5 (19) THE PROPOSED SCHEDULING SYSTEM SHALL INCLUDE THE
ABILITY TO MAKE UP A SHIFT ROSTER THAT INCLUDES THE
FOLLOWING INFORMATION:
2-17.5 (19.1) FIRST AND LAST FULL NAME OF THE OFFICER,
2-17.5 (19.2) UNIT TO WHICH THE OFFICER IS ASSIGNED,
2-17.5 (19.3) PATROL DISTRICT OR LOCATION OF ASSIGNMENT,
2-17.5 (19.4) OFFICER’S RADIO CALL SIGN,
City of Fort Collins xc Proposal P-847
2-17.5 (19.5) OFFICER'S PHONE OR PAGER NUMBER, AND
2-17.5 (19.6) OFFICER’S VEHICLE NUMBER.
2-17.5 (20) IT SHALL BE POSSIBLE FOR A SUPERVISOR TO ASSIGN AN
EMPLOYEE FROM ANOTHER SQUAD, SHIFT OR WORK ASSIGNMENT
TO A ROSTER AT ANY TIME.
2-17.5 (21) THE PROPOSED SCHEDULING SYSTEM SHALL ALLOW DISPATCHERS
TO USE THE ELECTRONIC ROSTER TO PLACE UNITS ON AND OFF
DUTY.
2-17.5 (22) IT IS PREFERRED THAT THE PROPOSED SCHEDULING SYSTEM
ENABLE A SCHEDULING SUPERVISOR TO ASSIGN EMPLOYEES TO
SQUADS, DAYS OFF, HOLIDAYS, AND UNITS WITH A "POINT AND
CLICK" FUNCTION.
2-17.5 (23) IT SHALL BE POSSIBLE TO DISPLAY AND PRINT THE ROSTER BY
SHIFT AND DATE.
2-17.5 (24) IT SHALL BE POSSIBLE FOR COURT EMPLOYEES AND OTHER
AUTHORIZED PERSONS TO VIEW AN OFFICER OR EMPLOYEE'S
SCHEDULE SO THAT THEY WILL NOT SCHEDULE COURT DAYS ON
REGULARLY SCHEDULED DAYS OFF AND VACATION DAYS.
2-17.5 (25) THE PROPOSED RMS/JMS APPLICATION SHALL HAVE THE ABILITY
TO TRACK THE FOLLOWING INFORMATION ABOUT "OFF DUTY"
EMPLOYMENT:
2-17.5 (25.1) THE EMPLOYER'S NAME, ADDRESS AND PHONE NUMBER,
2-17.5 (25.2) THE PHYSICAL LOCATION AND PHONE NUMBER OF THE
ASSIGNMENT, AND
2-17.5 (25.3) THE SCHEDULED OFF-DUTY EMPLOYMENT TIME.
2-17.6 CAD INTERFACE TO PERSONNEL
2-17.6 (1) THE PROPOSED PERSONNEL SYSTEM SHALL BE
INTEGRATED/INTERFACED WITH THE PROPOSED CAD SUCH THAT
CAD WILL DRAW FROM THE PERSONNEL SYSTEM FOR
INFORMATION SUCH AS OFFICERS WITH SPECIAL SKILLS, SHIFT
ASSIGNMENT, ETC.
2-17.6 (2) THE PROPOSED SYSTEM MAY MAINTAIN A PERSONNEL FILE IN THE
CAD FOR PERFORMANCE OR OTHER REASONS. IN THIS CASE THE
SYSTEM SHALL ENSURE THAT THE SHARED PERSONNEL SYSTEM
SHALL HAVE PRIMACY OVER THE CAD PERSONNEL FILES AND
City of Fort Collins xci Proposal P-847
THAT CHANGES TO THE SHARED PERSONNEL SYSTEM ARE
SUCCESSFULLY WRITTEN TO THE CAD PERSONNEL FILE.
2-17.6 (3) AT A MINIMUM THE SYSTEM SHALL SHARE THE FOLLOWING
PERSONNEL FIELDS WITH THE CAD PERSONNEL FILE:
2-17.6 (3.1) EMPLOYEE NAME (FIRST, MIDDLE AND LAST),
2-17.6 (3.2) EMPLOYEE RANK,
2-17.6 (3.3) EMPLOYEE ID OR BADGE NUMBER,
2-17.6 (3.4) SOCIAL SECURITY NUMBER,
2-17.6 (3.5) EMPLOYEE SHIFT ASSIGNMENT,
2-17.6 (3.6) DISTRICT AND DUTY ASSIGNMENT, AND
2-17.6 (3.7) SPECIAL SKILLS.
2-17.6 (4) THE PROPOSED SYSTEM SHALL REFER TO THE PERSONNEL SKILLS,
ASSIGNMENT AND DISTRICT, ENTERED IN THE PERSONNEL
MODULE WHEN A CAD OPERATOR SEARCHES FOR SPECIAL
RESOURCES.
2-17.6 (5) THE PROPOSED SYSTEM SHALL TRANSFER THE SHIFT ROSTER
FROM THE PERSONNEL SYSTEM TO THE CAD AND SHALL PLACE
THE ONCOMING UNITS AND OFFICERS ON DUTY WHEN THE
DISPATCHER INVOKES THE FUNCTION.
2-17.6 (6) THE DISPATCHER SHALL PLACE EACH UNIT IN SERVICE MANUALLY.
2-17.7 PERSONNEL REPORTS
2-17.7 (1) THE PROPOSED RMS/JMS APPLICATION SHALL INCLUDE A DAILY
ACTIVITY REPORT FOR A GIVEN OFFICER AND DATE THAT DETAILS
THE ACTIVITY RECORDED FOR THAT OFFICER BY THE CAD
APPLICATION AND THE ACTIVITY REPORTING SYSTEM.
2-17.7 (2) THE PROPOSED RMS/JMS APPLICATION SHALL INCLUDE A
MONTHLY ACTIVITY REPORT FOR A GIVEN OFFICER AND DATE
THAT DETAILS THE ACTIVITY RECORDED FOR THAT OFFICER BY
THE CAD APPLICATION AND THE ACTIVITY REPORTING SYSTEM.
2-17.7 (3) THE PROPOSED RMS/JMS APPLICATION SHALL INCLUDE, BASED ON
LOG ON, TIME AND ATTENDANCE REPORTS THAT DETAILS:
2-17.7 (3.1) THE ATTENDANCE OF A GIVEN OFFICER FOR A GIVEN DATE OR
DATE RANGE PERIOD, AND
City of Fort Collins xcii Proposal P-847
2-17.7 (3.2) THE ATTENDANCE OF THE PERSONNEL ASSIGNED TO A GIVEN
SHIFT FOR A GIVEN DATE OR DATE RANGE.
2-17.7 (4) THE PROPOSED RMS/JMS APPLICATION SHALL INCLUDE AN
ASSIGNMENT REPORT THAT DETAILS THE ASSIGNMENTS OF ALL
PERSONNEL WORKING DURING A USER-DEFINED SHIFT AND DATE.
2-17.7 (5) THE PROPOSED RMS/JMS APPLICATION SHALL INCLUDE A DAILY
ATTENDANCE REPORT WHICH DETAILS THE TOTAL NUMBER OF
REGULAR, SICK, VACATION, OVERTIME AND LEAVE OF ABSENCE
HOURS RECORDED FOR A GIVEN DATE.
2-17.7 (6) THE PROPOSED RMS/JMS APPLICATION SHALL INCLUDE A WORK
SCHEDULE REPORT THAT SHOWS THE ASSIGNED SHIFT AND DAYS
OFF BY DAY FOR EACH SECTION, FOR A USER-DEFINED PERIOD OF
MONTHS.
2-17.7 (7) THE PROPOSED RMS/JMS APPLICATION SHALL INCLUDE A
SENIORITY REPORT WHICH LISTS STAFF BY RANK AND THEN BY
SENIORITY IN RANK.
2-17.7 (8) THE PROPOSED RMS/JMS APPLICATION SHALL INCLUDE A RECALL
REPORT THAT LISTS THE HOME ADDRESS AND CONTACT NUMBERS
FOR EACH OFFICER AND EMPLOYEE. AS WITH ALL REPORTS, THE
SYSTEM ADMINISTRATOR OR OTHER AUTHORIZED USER SHALL
HAVE THE ABILITY TO RESTRICT PRINTING OF THE REPORT BY
SECURITY PROFILE.
2-17.7 (9) THE PROPOSED RMS/JMS APPLICATION SHALL INCLUDE A PAGER
LIST REPORT THAT LISTS THE PAGER AND DEPARTMENT ASSIGNED
CELL TELEPHONE NUMBER FOR EACH OFFICER OR EMPLOYEE.
2-17.7 (10) MUST BE ABLE TO RUN A REPORT TO SHOW THE NUMBER OF
OFFICERS WITH POST CERTIFICATES. THIS REPORT MUST DISPLAY
AND BE ABLE TO RUN BY:
2-17.7 (10.1) DEPARTMENT,
2-17.7 (10.2) DIVISION,
2-17.7 (10.3) SECTION,
2-17.7 (10.4) UNIT,
2-17.7 (10.5) RANK,
2-17.7 (10.6) SHIFT,
City of Fort Collins xciii Proposal P-847
2-17.7 (10.7) AND CERTIFICATE.
2-17.7 (11) THE REPORT MUST INCLUDE BUT NOT BE LIMITED TO THE ABOVE
INFORMATION AND INCLUDE THE DATE THE CERTIFICATE WAS
RECEIVED.
2-17.7 (12) MUST BE ABLE TO RUN A REPORT TO SHOW THE NUMBER OF
SWORN OFFICERS BY:
2-17.7 (12.1) POSITION,
2-17.7 (12.2) RACE,
2-17.7 (12.3) AND GENDER.
2-17.7 (13) MUST BE ABLE TO RUN A REPORT TO SHOW THE NUMBER
CIVILIANS BY:
2-17.7 (13.1) POSITION,
2-17.7 (13.2) RACE,
2-17.7 (13.3) AND GENDER.
2-18 TRAINING DATABASE
2-18.1 (1) THE PROPOSED RMS/JMS APPLICATION SHALL INCLUDE A
FUNCTION FOR TRACKING AND MANAGING TRAINING FOR ALL
AGENCY PERSONNEL.
2-18.1 (2) THE PROPOSED SYSTEM SHALL MAINTAIN TRAINING RECORDS ON
EACH AGENCY EMPLOYEE THAT HAS A RECORD IN THE
PERSONNEL TRACKING SYSTEM THAT INCLUDES:
2-18.1 (2.1) A LINK TO THE EMPLOYEE’S NAME RECORD THAT DISPLAYS;
2-18.1 (2.1.1) AGENCY,
2-18.1 (2.1.2) EMPLOYEE ID OR BADGE NUMBER,
2-18.1 (2.1.3) LAST AND FIRST NAME,
2-18.1 (2.1.4) AND CURRENT JOB ASSIGNMENT.
2-18.1 (2.2) A RECORD OF EVERY COURSE THE EMPLOYEE HAS ATTENDED
THAT INCLUDES;
2-18.1 (2.2.1) COURSE TYPE,
City of Fort Collins xciv Proposal P-847
2-18.1 (2.2.2) COURSE TITLE,
2-18.1 (2.2.3) COURSE NUMBER,
2-18.1 (2.2.4) COURSE DATE,
2-18.1 (2.2.5) COURSE HOURS,
2-18.1 (2.2.6) COURSE DESCRIPTION,
2-18.1 (2.2.7) INSTRUCTOR'S NAME,
2-18.1 (2.2.8) DATE OF COMPLETION,
2-18.1 (2.2.9) LOCATION OF TRAINING,
2-18.1 (2.2.10) IN HOUSE OR OUTSIDE TRAINING,
2-18.1 (2.2.11) INSTITUTION PROVIDING TRAINING,
2-18.1 (2.2.12) GRADE RECEIVED,
2-18.1 (2.2.13) CERTIFICATE OR DEGREE PROVIDED,
2-18.1 (2.2.14) INDICATION IF TRAINING WAS MANDATORY OR OPTIONAL,
2-18.1 (2.2.15) CERTIFICATION EXPIRATION DATE, AND
2-18.1 (2.2.16) COST.
2-18.1 (3) IT SHALL BE POSSIBLE TO CONFIGURE THE PROPOSED TRAINING
SYSTEM WITH REQUIRED COURSES AND CERTIFICATIONS SO THAT
TRAINING AND CERTIFICATION AND RE-CERTIFICATION WILL NOT
BE ALLOWED TO LAPSE.
2-18.1 (4) THE PROPOSED TRAINING SYSTEM SHALL HAVE THE ABILITY TO
SCHEDULE PERIODIC TESTS.
2-18.1 (5) THE PROPOSED TRAINING SYSTEM SHALL HAVE THE ABILITY TO
SCHEDULE PERIODIC TRAINING.
2-18.1 (6) THE PROPOSED RMS/JMS APPLICATION SHALL INCLUDE A
NOTIFICATION OF REQUIRED RE-TESTS FOR OFFICERS AND
EMPLOYEES, INCLUDING CERTIFICATIONS AND INOCULATIONS.
2-18.1 (7) THE TRAINING SYSTEM SHALL ALLOW THE TRAINING
COORDINATOR TO ESTABLISH MINIMUM TRAINING
REQUIREMENTS FOR DIFFERENT CLASSES OF EMPLOYEES.
City of Fort Collins xcv Proposal P-847
2-18.1 (8) THE TRAINING SYSTEM SHALL ENABLE INSTRUCTORS TO ENTER
ATTENDANCE FOR EACH EMPLOYEE ENROLLED IN A TRAINING
COURSE WITH SOME TYPE OF MASS ASSIGNMENT TOOL.
2-18.1 (9) THE PROPOSED RMS/JMS APPLICATION SHALL INCLUDE A MEANS
FOR INSTRUCTORS TO ENTER NOTES ABOUT TRAINING CLASSES OR
INDIVIDUALS.
2-18.1 (10) THE TRAINING SYSTEM SHALL MAINTAIN A DATABASE OF
CERTIFIED TRAINERS/INSTRUCTORS.
2-18.1 (11) THE TRAINING SYSTEM SHALL ENABLE INSTRUCTORS TO ENTER
EXAMINATION AND FINAL GRADE SCORES FOR EACH EMPLOYEE
ENROLLED IN A TRAINING COURSE.
2-18.1 (12) THE TRAINING SYSTEM MODULE SHALL ALLOW THE TRAINING
COORDINATOR TO DEVELOP AN ANNUAL TRAINING SCHEDULE FOR
IN-SERVICE, RECRUIT AND OTHER TYPES OF TRAINING.
2-18.2 TRAINING REPORTS
2-18.2 (1) THE PROPOSED RMS APPLICATION SHALL INCLUDE A TRAINING
REPORT THAT DETAILS THE TRAINING COURSES COMPLETED AND
THE CHRONOLOGICAL HOURS EXPENDED IN TRAINING FOR A
GIVEN OFFICER/EMPLOYEE DURING A USER-DEFINED DATE RANGE.
2-18.2 (2) THE PROPOSED RMS APPLICATION SHALL INCLUDE A
DEPARTMENTAL TRAINING REPORT THAT DETAILS THE TOTAL
HOURS EXPENDED ON TRAINING FOR ALL MEMBERS OF THE
DEPARTMENT DURING A USER-DEFINED DATE RANGE. THIS
REPORT SHALL SUBTOTAL TRAINING EFFORTS BY THE CATEGORY,
E.G. POST, IN-SERVICE, PERSONAL, ETC.
2-18.2 (3) THE PROPOSED RMS APPLICATION SHALL INCLUDE A
CERTIFICATION EXPIRATION REPORT THAT SHOWS ALL REQUIRED
TRAINING COURSES AND CERTIFICATIONS, AND THEN LISTS ANY
PERSONNEL WHOSE CERTIFICATIONS WILL EXPIRE DURING THE
USER-DEFINED DATE RANGE.
2-18.2 (4) IN ADDITION TO THE OTHER TRAINING REPORTS, THE PROPOSED
APPLICATION SHALL INCLUDE A K-9 TRAINING REPORT WITH THE
FOLLOWING ELEMENTS:
2-18.2 (4.1) DATE AND TIME OF TRAINING,
2-18.2 (4.2) TEAM NAME,
2-18.2 (4.3) LOCATION OF TRAINING,
City of Fort Collins xcvi Proposal P-847
2-18.2 (4.4) WEATHER CONDITIONS,
2-18.2 (4.5) DECOY TYPE,
2-18.2 (4.6) TOTAL HOURS OF TRAINING,
2-18.2 (4.7) NARRATIVE,
2-18.2 (4.8) HANDLER NOTES, AND
2-18.2 (4.9) ACTIVITY.
2-18.2 (5) AFTER ALL INFORMATION IS ENTERED IN REFERENCE TO THE
TRAINING, A REPORT SHOULD BE GENERATED FOR ALL INSIDE
TRAINING WHICH MEETS COLORADO POLICE OFFICER
STANDARDIZED TRAINING (POST) REQUIREMENTS. THIS REPORT
SHOULD INCLUDE BUT NOT BE LIMITED TO:
2-18.2 (5.1) TITLE OF TRAINING,
2-18.2 (5.2) NUMBER IN ATTENDANCE,
2-18.2 (5.3) DATE OF TRAINING,
2-18.2 (5.4) SOCIAL SECURITY NUMBER,
2-18.2 (5.5) DATE OF BIRTH,
2-18.2 (5.6) NAME: LAST, FIRST, MIDDLE,
2-18.2 (5.7) SIGNATURE LINE,
2-18.2 (6) A REPORT WILL BE RUN EVERY 12 AND 24 MONTHS WHICH WILL
SEARCH THE TRAINING DATA BASE AND TOTAL THE NUMBER OF
HOURS FOR INSIDE AND OUTSIDE TRAINING WITHIN THE DATE
CRITERIA. THERE WILL BE A SEPARATE TOTAL FOR INSIDE AND A
SEPARATE TOTAL FOR OUTSIDE. ANY TRAINING OF LESS THAN ONE
HOUR WILL NOT BE INCLUDED IN THE REPORT.
2-18.2 (7) A REPORT WILL BE GENERATED TO LIST WHO HAS OR HAS NOT
ATTENDED CERTAIN TRAINING. THIS REPORT WILL BE GENERATED
BASED ON EITHER WORD SEARCH OR DATE(S). THE REPORT WILL
INCLUDE BUT NOT BE LIMITED TO:
2-18.2 (7.1) NAME: FIRST, LAST, MIDDLE,
2-18.2 (7.2) DATE(S) OF ATTENDANCE,
2-18.2 (7.3) NUMBER OF HOURS,
City of Fort Collins xcvii Proposal P-847
2-18.2 (7.4) LOCATION OF TRAINING,
2-18.2 (7.5) DIVISION AND SHIFT,
2-18.2 (7.6) AND SUPERVISOR.
2-18.2 (8) A REPORT WILL BE GENERATED USING NAME AND/OR DATE
SEARCH CRITERIA TO REPORT THE NUMBER OF TRAINING HOURS,
OVER ONE HOUR, FOR ALL EMPLOYEES FOR THE CRITERIA
ENTERED. THE REPORT WILL INCLUDE, BUT NOT BE LIMITED TO:
2-18.2 (8.1) NAME: FIRST, LAST, MIDDLE,
2-18.2 (8.2) TOTAL NUMBER OF HOURS,
2-18.2 (8.3) TRAINING ATTENDED,
2-18.2 (8.4) AND DATE(S) OF TRAINING.
2-18.2 (9) A REPORT WILL BE GENERATED TO REPORT THE AVERAGE
TRAINING HOURS BY:
2-18.2 (9.1) DEPARTMENT,
2-18.2 (9.2) DIVISION,
2-18.2 (9.3) SECTION,
2-18.2 (9.4) RANK,
2-18.2 (9.5) DIVISION,
2-18.2 (9.6) AND SHIFT.
2-18.3 ACADEMY PROCESS
Applicant Information (This database should be restricted to access by Training &
Personnel only except for searches which will display only information relevant to
criminal identification, e.g. race, sex, dob, name, address, social security number, and
drivers license number)
2-18.3 (1) THE SYSTEM MUST BE ABLE TO CAPTURE ALL INFORMATION IN
REFERENCE TO APPLICANTS FOR THE ACADEMY. THIS SHOULD
INCLUDE PERSONAL INFORMATION AS FOLLOWS:
2-18.3 (1.1) ACADEMY NUMBER,
2-18.3 (1.2) ACADEMY TYPE (POST, CITIZEN, RESERVE, ETC.)
City of Fort Collins xcviii Proposal P-847
2-18.3 (1.3) ACADEMY DATE(S)
2-18.3 (1.4) STUDENT AGENCY
2-18.3 (1.5) STUDENT ID AND/OR BADGE NUMBER (ALPHA/NUMERIC,
MINIMUM OF 8 CHARACTERS),
2-18.3 (1.6) STUDENT’S FULL NAME (LAST, FIRST AND MIDDLE), WITH
SUPPORT FOR HYPHENATED LAST NAMES AND NAME SUFFIXES,
2-18.3 (1.7) DATE AND PLACE OF BIRTH,
2-18.3 (1.8) CURRENT AGE (CONTINUOUSLY CALCULATED FROM DOB),
2-18.3 (1.9) SOCIAL SECURITY NUMBER,
2-18.3 (1.10) DRIVERS LICENSE NUMBER AND EXPIRATION DATE,
2-18.3 (1.11) PHYSICAL DESCRIPTION THAT INCLUDES; GENDER,
RACE/ETHNICITY, HEIGHT, WEIGHT, EYE AND HAIR COLOR,
2-18.3 (1.12) DIGITAL PHOTO,
2-18.3 (1.13) STUDENT HOME ADDRESS THAT INCLUDES; STREET NUMBER &
NAME, PO BOX, CITY, STATE, AND ZIP,
2-18.3 (1.14) STUDENT WORK NAME AND ADDRESS THAT INCLUDES; STREET
NUMBER & NAME, PO BOX, CITY, STATE, AND ZIP,
2-18.3 (1.15) AT LEAST FOUR FIELDS FOR TELEPHONE, MOBILE PHONE, AND
PAGER NUMBERS,
2-18.3 (1.16) AND EMAIL ADDRESS.
2-18.3 (2) SYSTEM MUST ALSO CAPTURE INFORMATION RELATING TO THE
ACADEMY APPLICATION PROCESS THAT INCLUDES THE
FOLLOWING:
2-18.3 (2.1) DATE APPLICATION RECEIVED,
2-18.3 (2.2) WRITTEN EXAM INFORMATION;
2-18.3 (2.2.1) TEST DATE,
2-18.3 (2.2.2) TEST TIME,
2-18.3 (2.2.3) SCORE,
2-18.3 (2.2.4) MILITARY POINTS,
City of Fort Collins xcix Proposal P-847
2-18.3 (2.2.5) TOTAL TEST SCORE,
2-18.3 (2.2.6) FAILED TO APPEAR (FTA)/WITHDREW (WD),
2-18.3 (2.2.7) AND COMMENTS (FREE TEXT).
2-18.3 (2.3) PHYSICAL AGILITY TESTING;
2-18.3 (2.3.1) TEST DATE,
2-18.3 (2.3.2) PASS/FAIL/FAILED TO APPEAR (FTA)/WITHDREW (WD),
2-18.3 (2.3.3) AND COMMENTS (FREE TEXT).
2-18.3 (2.4) BACKGROUND INVESTIGATION;
2-18.3 (2.4.1) INVESTIGATOR,
2-18.3 (2.4.2) PASS/FAIL,
2-18.3 (2.4.3) AND COMMENTS (FREE TEXT).
2-18.3 (2.5) POLYGRAPH;
2-18.3 (2.5.1) DATE,
2-18.3 (2.5.2) PASS/FAIL/FAILED TO APPEAR (FTA)/WITHDREW (WD),
2-18.3 (2.5.3) AND COMMENTS (FREE TEXT).
2-18.3 (2.6) ORAL BOARD;
2-18.3 (2.6.1) DATE,
2-18.3 (2.6.2) PASS/FAIL/FAILED TO APPEAR (FTA)/WITHDREW (WD),
2-18.3 (2.6.3) AND COMMENTS (FREE TEXT).
2-18.3 (2.7) PSYCHOLOGICAL;
2-18.3 (2.7.1) DATE OF EXAM,
2-18.3 (2.7.2) PSYCHOLOGIST,
2-18.3 (2.7.3) PASS/FAIL/FAILED TO APPEAR (FTA)/WITHDREW (WD),
2-18.3 (2.7.4) AND COMMENTS (FREE TEXT).
2-18.3 (2.8) PHYSICAL;
City of Fort Collins c Proposal P-847
2-18.3 (2.8.1) DATE,
2-18.3 (2.8.2) PASS/FAIL/FAILED TO APPEAR (FTA)/WITHDREW (WD),
2-18.3 (2.8.3) AND COMMENTS (FREE TEXT).
2-18.3 (2.9) ACADEMY OVERALL;
2-18.3 (2.9.1) DATE,
2-18.3 (2.9.2) PASS/FAIL/TERMINATED/FAILED TO APPEAR (FTA)/WITHDREW
(WD),
2-18.3 (2.9.3) AND COMMENTS (FREE TEXT).
2-18.4 ACADEMY REPORTS
2-18.4 (1) MUST BE ABLE TO RUN A REPORT TO SHOW TOTALS FOR EACH
STAGE IN THE ACADEMY SELECTION PROCESS. THE REPORT MUST
SHOW NUMBER AND PERCENTAGE CHANGE FROM TOTAL, AND
NUMBER AND PERCENTAGE CHANGE FROM ONE STAGE TO THE
NEXT. ALSO MUST INCLUDE RACE AND GENDER. THIS REPORT
MUST HAVE THE ABILITY TO RUN ON ANY OF THE INPUT FIELDS.
THIS REPORT WILL INCLUDE BUT NOT BE LIMITED TO:
2-18.4 (1.1) INITIAL APPLICATION,
2-18.4 (1.2) INITIAL INTERVIEW,
2-18.4 (1.3) WRITTEN TEST,
2-18.4 (1.4) PHYSICAL AGILITY TEST,
2-18.4 (1.5) BACKGROUND INVESTIGATION,
2-18.4 (1.6) POLYGRAPH EXAMINATION,
2-18.4 (1.7) ORAL INTERVIEW,
2-18.4 (1.8) PSYCHOLOGICAL EXAMINATION,
2-18.4 (1.9) PHYSICAL EXAMINATION,
2-18.4 (1.10) ACADEMY (ACADEMIC),
2-18.4 (2) MUST BE ABLE TO RUN A REPORT TO SHOW ALL FAILED TO APPEAR
AND WITHDRAW FOR EACH STEP OF THE ACADEMY PROCESS.
City of Fort Collins ci Proposal P-847
2-18.4 (3) MUST BE ABLE TO RUN A ROSTER OF ALL THE RECRUITS IN AN
ACADEMY TO INCLUDE BUT NOT BE LIMITED TO:
2-18.4 (3.1) NAME,
2-18.4 (3.2) STUDENT NUMBER,
2-18.4 (3.3) SOCIAL SECURITY NUMBER,
2-18.4 (3.4) DRIVERS LICENSE NUMBER,
2-18.4 (3.5) RACE,
2-18.4 (3.6) GENDER,
2-18.4 (3.7) DATE OF BIRTH,
2-18.4 (3.8) AGE,
2-18.4 (3.9) ADDRESS (TO INCLUDE CITY, STATE & ZIP),
2-18.4 (3.10) AND PHONE.
2-19 SUPPLIES, EQUIPMENT AND FACILITY MANAGEMENT SYSTEM
2-19.1 SUPPLY ORDER AND TRACKING
2-19.1 (1) THE PROPOSED RMS/JMS APPLICATION SHALL INCLUDE A MODULE
THAT MAINTAINS AN INNOVATORY OF CONSUMABLE SUPPLIES
THAT ARE ISSUES AND NO LONGER TRACKED. THIS MODULE
WOULD TRACK STOCK, SET ORDER POINTS, AND PROVIDE
ACCOUNTING FOR THE ACQUISITION, STORING, AND DISTRIBUTION
OF ALL CONSUMABLE SUPPLIES.
2-19.1 (2) THIS MODULE SHALL HAVE THE ABILITY TO MAINTAIN RECORDS
FOR NO LESS THAN 99,999 DIFFERENT SUPPLY ITEMS.
2-19.1 (3) AT A MINIMUM THE SUPPLY ORDER AND TRACKING MODULE
SHALL PERFORM THE FOLLOWING:
2-19.1 (3.1) ALLOW FOR SEPARATE SUPPLY TRACKING PROCESSES FOR
EACH PARTICIPATING AGENCY,
2-19.1 (3.2) ALLOW FOR SEPARATE SUPPLY TRACKING PROCESS FOR
SUBDIVISIONS OF EACH PARTICIPATING AGENCY (I.E.
JANITORIAL, MAINTENANCE, SUPPLY).
2-19.1 (3.3) TRACKING ON EVERY STOCKED ITEM THAT INCLUDES; PRODUCT
(ITEM) TYPE, MANUFACTURER ITEM NUMBER, OTHER (VENDOR)
City of Fort Collins cii Proposal P-847
ITEM NUMBERS, ITEM DESCRIPTION, ITEM QUANTITY, ITEM
COST, AND REORDER POINT,
2-19.1 (3.4) COST TRACKING FOR ALL ORDERED SUPPLIES (BOTH STOCKED
AND PASS THROUGH),
2-19.1 (3.5) ABILITY TO PROJECT COSTS FOR SUPPLIES,
2-19.1 (3.6) MAINTAIN AN ORDER HISTORY OF ALL SUPPLIES (INCLUDING
THE DATE OF LAST ORDER),
2-19.1 (3.7) BUILD ORDERS AND ALLOW THE USER TO ATTACH VENDORS
(FROM THE VENDOR DATABASE) BASED ON PRODUCT TYPE (A
LIST OF POSSIBLE VENDORS WOULD DISPLAY FOR SELECTION
BASED ON THE TYPE OF SUPPLIES TO ORDER),
2-19.1 (3.8) SHOW COSTING ON ORDERS THAT INCLUDES BOTH THE UNIT
COST ANT LOT COST,
2-19.1 (3.9) AND TRACK THE DISTRIBUTION OF SUPPLIES THAT INCLUDES;
NAME OF PERSON RECEIVING SUPPLIES, COST FOR SUPPLIES,
WORK UNIT OF RECIPIENT, AND FULL DETAILED LISTING OF
SUPPLIES.
2-19.1 (4) THE PROPOSED RMS/JMS APPLICATION SHALL HAVE A MEANS OF
TRACKING THE USE OF SUPPLIES AND MAINTAINING AN ACCURATE
ACCOUNTING OF QUANTITIES IN STOCK.
2-19.1 (5) THE PROPOSED RMS/JMS APPLICATION SHALL HAVE THE ABILITY
TO TRACK A REORDER QUANTITY FOR EACH SUPPLY AND NOTIFY
THE SUPPLY OFFICER WHEN THE REORDER QUANTITY HAS BEEN
REACHED.
2-19.1 (6) THE PROPOSED RMS/JMS APPLICATION SHALL HAVE A MEANS FOR
RECONCILING SUPPLY USE WITH INVENTORY ON HAND.
2-19.1 (7) THE PROPOSED RMS/JMS APPLICATION SHALL ALLOW FOR THE
ELECTRONIC ROUTING OF SUPPLY REQUESTS TO INCLUDE AN
APPROVAL PROCESS (ROUTING TO A DEFINED CHAIN OF COMMAND
FOR EACH REQUESTOR). SUPPLY REQUESTS WOULD REQUIRE
PERTINENT INFORMATION BASED ON ITEM REQUESTED.
2-19.1 (8) THE PROPOSED RMS/JMS APPLICATION SHALL INCLUDE A REPORT
WHICH SHOWS THE CURRENT SUPPLIES INVENTORY BY CATEGORY
OF SUPPLY, LOCATION, OR UNIT.
City of Fort Collins ciii Proposal P-847
2-19.2 EQUIPMENT INVENTORY AND MAINTENANCE
2-19.2 (1) THE PROPOSED RMS/JMS APPLICATION SHALL INCLUDE A MODULE
THAT MAINTAINS AN INVENTORY, TRACKS POSSESSION, AND KEEPS
A MAINTENANCE HISTORY OF ALL TYPES OF EQUIPMENT ASSETS
USED FOR VARYING PURPOSES BY ALL OF THE PARTICIPATING
AGENCIES. EQUIPMENT IS DEFINED AS ANY ASSET THAT IS NOT
CONSIDERED A CONSUMABLE ITEM.
2-19.2 (2) THE PROPOSED SYSTEM SHALL HAVE THE ABILITY TO TRACK
EQUIPMENT ISSUED TO EMPLOYEES, SUCH AS UNIFORMS, BADGES,
KEY CARDS, WEAPONS, COMPUTERS, CARS, ETC.
2-19.2 (3) THIS MODULE SHALL HAVE THE ABILITY TO MAINTAIN RECORDS
FOR NO LESS THAN 99,999 DIFFERENT EQUIPMENT ITEMS.
2-19.2 (4) AT A MINIMUM THE EQUIPMENT INVENTORY AND MAINTENANCE
MODULE SHALL PERFORM THE FOLLOWING:
2-19.2 (4.1) ALLOW FOR SEPARATE EQUIPMENT TRACKING PROCESSES FOR
EACH PARTICIPATING AGENCY,
2-19.2 (4.2) ALLOW FOR SEPARATE EQUIPMENT TRACKING PROCESS FOR
SUBDIVISIONS OF EACH PARTICIPATING AGENCY (I.E.
JANITORIAL, MAINTENANCE, SUPPLY).
2-19.2 (4.3) SUPPORT A BAR-CODING DEVICE TO CAPTURE INVENTORY
CONTROL TAGS,
2-19.2 (4.4) ALLOW FOR ASSIGNED INVENTORY CONTROL NUMBERS,
2-19.2 (4.5) RECORD SERIAL OR IDENTIFICATION NUMBER,
2-19.2 (4.6) DESCRIPTION OF THE EQUIPMENT,
2-19.2 (4.7) COST OF THE EQUIPMENT,
2-19.2 (4.8) ABILITY TO ASSIGN THE EQUIPMENT TO AN INDIVIDUAL,
MOBILE UNIT, OR LOCATION,
2-19.2 (4.9) AND ALLOW FOR EQUIPMENT TO BE TRACKED AS PEERS OR
SUBSERVIENT TO ANOTHER PIECE OF EQUIPMENT (EQUIPMENT
ASSIGNED TO A VEHICLE, VEHICLE ASSIGNED TO A PERSON).
2-19.2 (5) THE SYSTEM SHALL CAPTURE ALL THE NECESSARY INFORMATION
TO FULLY TRACK A VEHICLE ASSIGNMENT (LISTS UNIT NUMBER,
ALL EQUIPMENT INSTALLED IN THAT VEHICLE, AND OFFICER
VEHICLE IS ASSIGNED TO).
City of Fort Collins civ Proposal P-847
2-19.2 (6) THE SYSTEM SHALL CAPTURE ALL THE NECESSARY INFORMATION
TO FULLY TRACK OFFICER UNIFORM AND EQUIPMENT CHECK OUT
(LISTS ALL UNIFORMS AND EQUIPMENT CHECKED OUT TO EACH
OFFICER AND UPDATES INVENTORY RECORDS AS ADDITIONAL
ITEMS ARE CHECKED OUT OR RETURNED).
2-19.2 (6.1) IT IS DESIRED THAT THIS CHECK OUT FORM SHOULD BE DIVIDED
INTO SECTIONS, LISTING UNIFORMS AND RELATED EQUIPMENT
(BELTS, LEATHER GEAR) WITH SIZES IN ONE SECTION, AND
TRACKED EQUIPMENT IN ANOTHER SECTION (SUCH AS
CAMERAS, PBT’S ETC.) WITH CAPABILITY OF ENTERING SERIAL
NUMBER, BAR CODE NUMBER, MODEL, AND/OR BRAND.
FIREARMS WOULD BE IN ANOTHER SECTION WITH SERIAL
NUMBER, BAR CODE NUMBER, BRAND NAME, CALIBER, AND
RELATED EQUIPMENT (SCOPE, SLING, AMMO CARRIER, ETC.).
DATE OF CHECK OUT OR RETURN MUST ALSO BE NOTED.
2-19.2 (7) ABILITY TO SEARCH FOR ANY EQUIPMENT OR UNIFORM ITEM AND
RUN A REPORT OF EVERY EMPLOYEE WHO HAS THAT ITEM ISSUED
TO THEM, WITH RELATED INFORMATION (SERIAL NUMBERS,
QUANTITY, ETC.). FOR EXAMPLE, RUN A REPORT OF ALL
EMPLOYEES WHO HAVE A REMINGTON 870 SHOTGUN.
2-19.2 (8) ALLOW EMPLOYEES TO VIEW THE RECORD OF THE UNIFORMS AND
EQUIPMENT ISSUED TO THEM, BUT LIMIT EDITING TO
AUTHORIZED PERSONNEL ASSIGNED TO THE SUPPLY UNIT.
2-19.2 (9) ALLOW AUTHORIZED PERSONNEL IN THE SUPPLY UNIT TO
RETRIEVE A LIST OF ALL ITEMS ISSUED TO A PARTICULAR
OFFICER, AND TO SELECT FROM THIS LIST WHICH ITEMS ARE
BEING RETURNED TO INVENTORY.
2-19.2 (10) THE PROPOSED RMS/JMS APPLICATION SHALL INCLUDE A REPORT
WHICH LISTS ALL PROPERTY (UNIFORMS, DOOR CARDS, GUNS,
ETC.) ASSIGNED TO EACH OFFICER OR EMPLOYEE. THE REPORT
WILL INCLUDE A DESCRIPTION OF EACH ITEM AND ANY
IDENTIFYING NUMBER.
2-19.2 (11) SYSTEM SHOULD TRACK ITEMS RETURNED TO SUPPLY BY EITHER
PUTTING THEM BACK INTO INVENTORY, OR REMOVING THEM
FROM INVENTORY AND DOCUMENTING THE REASON FOR
REMOVAL. THE ITEM MAY HAVE BEEN DAMAGED OR NO LONGER
IN USABLE CONDITION, LOST, STOLEN, DONATED TO ANOTHER
AGENCY, ETC.
City of Fort Collins cv Proposal P-847
2-19.2 (12) ABILITY TO RUN A REPORT OF ALL ITEMS REMOVED FROM
INVENTORY, SPECIFYING THE REASON, AND THE DATE OF
REMOVAL.
2-19.2 (13) ALL ITEMS ISSUED OR RETURNED SHOULD BE MARKED IN THE
SYSTEM WITH THE DATE ISSUED OR RETURNED.
2-19.2 (14) THE PROPOSED RMS/JMS APPLICATION SHALL KEEP A
MAINTENANCE HISTORY OF ALL PIECES OF EQUIPMENT THAT
REQUIRES MAINTENANCE, THAT INCLUDES; USEFUL LIFE, COST
TRACKING, PREVENTIVE MAINTENANCE INTERVAL, REPAIR
HISTORY, AND A REPAIR THRESHOLD NOTIFICATION (USER
DEFINED THRESHOLD TO NOTIFY ABOUT PROBLEM EQUIPMENT).
2-19.2 (14.1) THE PROPOSED RMS/JMS APPLICATION SHALL AUTOMATICALLY
SEND NOTIFICATIONS THAT PREVENTIVE MAINTENANCE WORK
NEEDS TO BE PERFORMED AS MAINTENANCE INTERVALS EXPIRE.
2-19.2 (15) THE PROPOSED RMS/JMS APPLICATION SHALL HAVE THE ABILITY
TO KEEP A PARTS INVENTORY PER EACH PIECE OF TRACKED
EQUIPMENT, AND MAINTAIN A HISTORY OF PARTS USE ALONG
WITH A STOCK QUANTITY OF THE PARTS.
2-19.2 (16) THE PROPOSED RMS/JMS SYSTEM SHALL HAVE THE ABILITY TO
PRINT A LIST OF ALL EQUIPMENT ASSIGNED TO AN EMPLOYEE,
UNIT, STATION OR OTHER LOCATION.
2-19.3 FACILITY MANAGEMENT
2-19.3 (1) THE PROPOSED RMS/JMS SYSTEM SHALL HAVE A JOB TICKET
PROCESS THAT ALLOWS ANY SYSTEM USER TO MAKE AN
ELECTRONIC REQUEST TO THE FACILITY MAINTENANCE STAFF
FOR ANY OF THE FOLLOWING;
2-19.3 (1.1) FACILITY MAINTENANCE NEED,
2-19.3 (1.2) DAMAGE OR BREAKAGE REPAIR,
2-19.3 (1.3) WORK ORDER.
2-19.3 (2) THE RMS/JMS MUST ALLOW FOR SEPARATE JOB TICKET
PROCESSES FOR EACH PARTICIPATING AGENCY,
2-19.3 (3) THE RMS/JMS MUST ALLOW FOR SEPARATE JOB TICKET
PROCESSES FOR SUBDIVISIONS OF EACH PARTICIPATING AGENCY
(I.E. JANITORIAL, MAINTENANCE, ETC.).
City of Fort Collins cvi Proposal P-847
2-19.3 (4) THE RMS/JMS MUST ALLOW FOR GLOBAL JOB TICKET PROCESSES
ACROSS THE ENTIRE SYSTEM.
2-19.3 (5) THE JOB TICKET SYSTEM SHALL HAVE THE ABILITY TO SET
PRIORITY LEVELS, BOTH AT INITIAL REQUEST, AND UPON REVIEW
BY MAINTENANCE STAFF.
2-19.3 (6) THE JOB TICKET SYSTEM SHALL HAVE THE ABILITY TO MERGE
MULTIPLE REQUESTS ABOUT THE SAME THING INTO ONE REQUEST
THAT TRACKS ALL THE REQUESTORS.
2-19.3 (7) THE JOB TICKET SYSTEM SHALL HAVE THE ABILITY TO SCHEDULE
TO EXPECTED COMPLETION OF THE JOB TICKET.
2-19.3 (8) THE JOB TICKET SYSTEM SHALL HAVE THE ABILITY FOR ANY USER
OF THE SYSTEM TO LOOK AT ALL THE INFORMATION ON ALL JOB
TICKETS, REGARDLESS OF STATUS.
2-19.3 (9) THE JOB TICKET SYSTEM SHALL HAVE SPECIFIC FIELDS THAT
WILL BE SEARCHABLE BY A QUERY FORM THAT ALLOWS FOR
LIMITING THE AMOUNT OF RESPONSES. AT MINIMUM THE JOB
TICKET SHOULD CONTAIN THE FOLLOWING FIELDS;
2-19.3 (9.1) TYPE OF REQUEST (PICK LIST),
2-19.3 (9.2) LEVEL OF REQUEST (PICK LIST),
2-19.3 (9.3) STATUS OF REQUEST (PICK LIST)
2-19.3 (9.4) LOCATION OF REQUEST (PICK LIST),
2-19.3 (9.5) CLASSIFICATION OF REQUEST (PICK LIST),
2-19.3 (9.6) LAST NAME OF REQUESTOR,
2-19.3 (9.7) FIRST NAME OF REQUESTOR,
2-19.3 (9.8) REQUESTOR CONTACT INFO (PHONE NUMBER, E-MAIL, ETC.),
2-19.3 (9.9) LINK TO PREVIOUS REQUEST (JOB TICKET NUMBER),
2-19.3 (9.10) CHRONIC PROBLEM FLAG (CHECK BOX),
2-19.3 (9.11) DATE OF REQUEST,
2-19.3 (9.12) EXPECTED DATE OF COMPLETION,
2-19.3 (9.13) NARRATIVE OF REQUEST.
City of Fort Collins cvii Proposal P-847
2-19.3 (10) THE JOB TICKET SYSTEM SHALL NOTIFY DESIGNATED PERSONNEL
OF PENDING JOB TICKET REQUESTS.
2-19.3 (11) THE JOB TICKET SYSTEM SHALL NOTIFY DESIGNATED PERSONNEL
OF OVERDUE JOB TICKET REQUESTS.
2-19.3 (12) THE JOB TICKET SYSTEM SHALL NOTIFY DESIGNATED PERSONNEL
OF CHRONIC PROBLEMS BASED ON THE CHRONIC PROBLEM FLAG
OR ON A THRESHOLD SET BY THE AGENCY OF NUMBER OF
REQUESTS OF A SPECIFIC TYPE, IN A SPECIFIC AREA, OF A SPECIFIC
CLASSIFICATION, WITHIN A SPECIFIED TIME PERIOD.
2-19.3 (13) THE JOB TICKET SYSTEM SHALL NOTIFY THE REQUESTER(S) UPON
COMPLETION OF THE JOB TICKET.
2-19.3 (14) THE JOB TICKET SYSTEM SHALL HAVE THE ABILITY TO BUILD A
KNOWLEDGE BASE OF PROBLEM RESOLUTIONS THAT WILL BE
SEARCHABLE BY THE FIELDS ABOVE OR BY TEXT STRING.
2-19.4 VENDOR DATABASE
2-19.4 (1) THE PROPOSED RMS/JMS SHALL HAVE THE ABILITY TO MAINTAIN
LISTS OF VENDORS THAT SELL SUPPLIES AND EQUIPMENT AND
THAT PROVIDE SERVICES FOR FACILITY MANAGEMENT.
2-19.4 (2) THE SYSTEM SHALL ALLOW FOR SEPARATE VENDOR LISTS FOR
EACH PARTICIPATING AGENCY,
2-19.4 (3) THE SYSTEM SHALL ALLOW FOR VENDOR LISTS FOR SUBDIVISIONS
OF EACH PARTICIPATING AGENCY (I.E. JANITORIAL,
MAINTENANCE, SUPPLY).
2-19.4 (4) AT A MINIMUM THE VENDOR DATABASE MODULE SHALL RECORD
THE FOLLOWING:
2-19.4 (4.1) VENDOR NAME,
2-19.4 (4.2) VENDOR ADDRESS,
2-19.4 (4.3) CONTACT NAME, PHONE, FAX, E-MAIL,
2-19.4 (4.4) THE AGENCY CUSTOMER OR ACCOUNT NUMBER,
2-19.4 (4.5) COMMENT FIELD,
2-19.4 (4.6) LIST TYPES OF PRODUCT TYPES SOLD OR SERVICES PERFORMED
(MULTIPLE PER VENDOR),
2-19.4 (4.7) AND A LINK TO ORDER PROCESSING.
City of Fort Collins cviii Proposal P-847
2-20 MISCELLANEOUS FUNCTIONS
2-20.1 LOOKOUTS
2-20.1 (1) THE PROPOSED APPLICATION SHALL OFFER A MEANS FOR
ENTERING, STORING, RETRIEVING AND MANAGING BOLO’S AND
BROADCAST MESSAGES.
2-20.1 (2) THE PROPOSED APPLICATION SHALL PROVIDE A BOLO FORM
WHICH CONTAINS SPECIFIC FIELDS FOR THE FOLLOWING:
2-20.1 (2.1) SUSPECT,
2-20.1 (2.2) VEHICLE/PROPERTY DESCRIPTIONS,
2-20.1 (2.3) RELATED EVENT NUMBERS,
2-20.1 (2.4) EVENT LOCATION,
2-20.1 (2.5) DATE/TIME OF EVENT,
2-20.1 (2.6) BOLO NUMBER (AUTOMATICALLY POPULATED),
2-20.1 (2.7) PURGE DATE,
2-20.1 (2.8) UNLIMITED FREE-FORM TEXT FIELD.
2-20.1 (3) PREFERENCE WILL BE GIVEN TO SOLUTIONS WHICH ALLOW THE
USER TO SPECIFY WHEN CREATING A BOLO FOR HOW MANY DAYS
AND TIMES PER DAY THE BOLO WILL BE BROADCAST.
2-20.1 (4) THE BOLO DATABASE SHALL UTILIZE CUT/COPY/PASTE FUNCTIONS.
2-20.1 (5) THE DATABASE SHALL STORE NO LESS THAN 6 MONTHS WORTH OF
BOLO’S.
2-20.1 (6) AT A MINIMUM, THE PROPOSED APPLICATION SHALL ALLOW AN
AUTHORIZED USER TO SEARCH FOR A BOLO BY:
2-20.1 (6.1) BOLO NUMBER,
2-20.1 (6.2) LOCATION,
2-20.1 (6.3) COMPLAINANT,
2-20.1 (6.4) A PERSON NAMED IN THE LOOKOUT,
2-20.1 (6.5) A PERSON DESCRIBED IN THE LOOKOUT,
City of Fort Collins cix Proposal P-847
2-20.1 (6.6) A VEHICLE DESCRIBED IN THE LOOKOUT,
2-20.1 (6.7) DATE AND TIME OF ENTRY, AND
2-20.1 (6.8) THE NAME OF THE EMPLOYEE ENTERING THE LOOKOUT.
2-20.1 (7) THE PROPOSED APPLICATION SHALL ALLOW THE USER TO ROUTE
BOLO’S TO UNITS EQUIPPED WITH MOBILE COMPUTERS AND
OTHER WORKSTATIONS ON THE NETWORK.
2-20.1 (8) THE PROPOSED APPLICATION SHALL ALLOW A USER TO CROSS-
REFERENCE A BOLO TO A CAD EVENT AND/ OR A CASE (REPORT)
NUMBER.
2-20.1 (9) THE PROPOSED APPLICATION SHALL ALLOW ANY USER WHETHER
THEY ARE WORKING IN THE RMS, CAD, MDC OR JMS APPLICATION
BE ABLE TO INITIATE A BOLO.
City of Fort Collins cx Proposal P-847
3 - COMPUTER AIDED DISPATCH
3-1 SYSTEM DESIGN
3-1.1 GENERAL REQUIREMENTS
3-1.1 (1) THE PROPOSED APPLICATION SHALL UTILIZE AN
“INCIDENT/ENTRY MASK” FOR ALL CALL ENTRY. THIS MASK WILL
BE RETRIEVABLE WITH ONE KEYSTROKE COMBINATION AND WILL
CONTAIN THE FOLLOWING FIELDS. THE MINIMUM NUMBER OF
CHARACTERS PER FIELD ARE IDENTIFIED AS FOLLOWS:
3-1.1 (1.1) NUMERIC ADDRESS: 6 CHARACTERS
3-1.1 (1.2) ADDRESS DIRECTIONAL: 2 CHARACTERS
3-1.1 (1.3) STREET: 25 CHARACTERS
3-1.1 (1.4) STREET SUFFIX: 4 CHARACTERS
3-1.1 (1.5) INTERSECTIONS: 50 CHARACTERS
3-1.1 (1.6) APT/TRAILER NUMBERS: 5
3-1.1 (1.7) BUILDING NUMBER: 5
3-1.1 (1.8) INCIDENT TYPE: 6 CHARACTERS
3-1.1 (1.9) INCIDENT LOCATION: 60 CHARACTERS
3-1.1 (1.10) INFORMANT NAME: 35 CHARACTERS
3-1.1 (1.11) INFORMANT ADDRESS: 60 CHARACTERS
3-1.1 (1.12) INFORMANT PHONE NUMBER: 10 CHARACTERS
3-1.1 (1.13) PHONE EXTENSION: 5 CHARACTERS
3-1.1 (1.14) TEXT OF INCIDENT: 400 CHARACTERS
3-1.1 (1.15) PRIORITY FIELD: 2 CHARACTERS
3-1.1 (1.16) DISPOSITION FIELD: 6 CHARACTERS
3-1.1 (1.17) POLICE/FIRE AREA FIELD: 3 CHARACTERS
3-1.1 (2) IT IS PREFERRED THAT ALL TELEPHONE NUMBER FIELDS ALLOW
FOR THE ENTRY OF 12 DIGITS SO THAT THE COUNTRY CODE MAY
BE RECORDED WHEN NECESSARY.
City of Fort Collins cxi Proposal P-847
3-1.1 (3) THE PROPOSED APPLICATION SHALL ALLOW AUTHORIZED USER
TO CONFIGURE/MAP THE KEYBOARD AS NEEDED.
3-1.1 (4) THE PARTICIPATING AGENCIES WILL GIVE PREFERENCE TO
SOLUTIONS, WHICH PROVIDE CONTROLS FOR SCROLLING ALL
FREE FORM TEXT AND COMMENT FIELDS.
3-1.1 (5) IN ANY CASE WHERE THE PROPOSED APPLICATION PRESENTS
MULTIPLE “PAGES” OF INFORMATION OR THE INFORMATION
CANNOT BE DISPLAYED WITHIN THE AVAILABLE SPACE THERE
SHALL BE A CLEAR INDICATION TO THE USER THAT INFORMATION
REMAINS TO BE DISPLAYED.
3-1.1 (6) THE PROPOSED APPLICATION SHALL ALLOW THE USER TO EITHER
PAGE OR SCROLL FORWARD AND BACKWARD THROUGH THE
MATERIAL BY USING THE KEYBOARD OR A POINTING DEVICE.
3-1.1 (7) WHEN A SEARCH RESULTS IN THE RETRIEVAL OF MULTIPLE
RECORDS, THE CAD APPLICATION SHALL ALLOW THE SYSTEM
ADMINISTRATOR OR AUTHORIZED USER TO DETERMINE THE SORT
METHOD BY DISPLAY TYPE. FOR EXAMPLE, IF AN ADDRESS HAS
MULTIPLE RECORDS OF PREVIOUS CALLS FOR SERVICE THEY
MIGHT BE DISPLAYED BY DATE BEGINNING WITH THE MOST
RECENT EVENT.
3-2 CAD CLIENT
3-2.1 GENERAL REQUIREMENTS
3-2.1 (1) THERE SHALL BE NO LIMIT ON THE NUMBER OF WORKSTATIONS,
WHICH CAN SIMULTANEOUSLY ACCESS THE CAD SYSTEM (GIVEN
PROPER SECURITY CLEARANCE AND NETWORK CONNECTIONS).
3-2.1 (2) THE PROPOSED APPLICATION SHALL MAKE EFFICIENT USE OF
INPUT METHODS (COMMAND LINE SHORT CUT KEYS, FUNCTION
KEYS, GRAPHIC COMMAND BUTTONS, ETC.) RECOGNIZING THE
DIFFERENT WAYS THAT OPERATORS USE THE PROPOSED
APPLICATION.
3-2.1 (3) THE PROPOSED APPLICATION SHALL OFFER A MINIMUM OF 10
WORK SCREENS/WINDOWS FOR DISPATCHERS TO WORK ON. FOR
EXAMPLE, HANDLING MULTIPLE CALL ENTRIES OR HAVING
MULTIPLE VEHICLE OR DRIVERS LICENSE LISTINGS ON THE
COMPUTER AT ONE TIME AND BEING ABLE TO WORK ON EACH
WITHOUT AFFECTING THE OTHERS.
3-2.1 (3.1) THE SCREENS SHALL BE EASY TO “TOGGLE” BETWEEN AND
WILL NOT REQUIRE THE DISPATCHER TO “SAVE” ANY
City of Fort Collins cxii Proposal P-847
INFORMATION IN ANY SORT OF MEMORY OR BUFFER SYSTEM
WHICH WOULD REQUIRE MULTIPLE KEYSTROKES TO RETRIEVE
LATER.
3-2.1 (4) THE PROPOSED SYSTEM SHALL ALLOW USERS TO VIEW DIFFERENT
JURISDICTIONS/AGENCIES PENDING AND ACTIVE CALLS. THIS
WILL BE DONE FROM SCREEN LAYOUTS, WHICH WILL BE USER
CONFIGURABLE.
3-2.1 (5) THE PROPOSED SYSTEM SHALL ALLOW USERS TO VIEW DIFFERENT
JURISDICTIONS/AGENCIES UNIT STATUS INFORMATION. THIS WILL
BE DONE FROM SCREEN LAYOUTS, WHICH WILL BE USER
CONFIGURABLE.
3-2.1 (6) IN THE EVENT OF A SYSTEM FAILURE (NOT INCLUDING POWER
OUTAGES) USERS SIGNED ON TO CAD AT THE TIME OF THE FAILURE
SHALL BE ABLE TO VIEW:
3-2.1 (6.1) PENDING EVENTS
3-2.1 (6.2) STACKED OR WAITING EVENTS
3-2.1 (6.3) EVENTS IN PROGRESS
3-2.1 (6.4) UNITS ON DUTY AND LAST KNOWN LOCATION,
3-2.1 (6.5) UNITS ASSIGNED AND LAST KNOWN LOCATION, INCLUDING
UNITS ENGAGED IN TRAFFIC STOPS, ADMINISTRATIVE STATUSES,
OR OTHER NON-EVENT ACTIVITIES.
3-2.1 (7) THE PROPOSED CAD WORKSTATIONS SHALL HAVE THE CAPABILITY
TO SUPPORT AT LEAST THREE MONITORS.
3-2.2 LOCATION AND NUMBER OF CAD CLIENTS
3-2.2 (1) LOCATION/DEFINITION (ALL CLIENTS MUST BE CAPABLE OF FULL
FUNCTIONALITY)
Location/Definition FCPS LCSO LPD EPPD CSUPD BPD Total
Communications 10 9 8 5 4 1 37
Records / Civil 16 6 2 1 1 1 27
Administrative Use 10 18 5 1 1 1 36
Patrol / Investigations 180 110 75 20 10 6 401
Crime Analysis 2 0 1 0 0 0 3
City of Fort Collins cxiii Proposal P-847
TOTAL 218 143 91 27 16 9 504
3-2.3 USER INTERFACE
3-2.3 (1) ****CRITICAL FUNCTIONALITY**** THE PRIMARY CAD INTERFACE
FOR CALL TAKERS AND DISPATCHER SHALL BE A COMMAND LINE.
3-2.3 (2) IT IS PREFERRED THAT THE SYSTEM ADMINISTRATOR OR OTHER
AUTHORIZED USER TO ENTER ALIASES FOR SYSTEM SUPPORTED
COMMAND CODES. FOR EXAMPLE, IF THE PROPOSED APPLICATION
USES THE LETTERS I.E. AS SHORTHAND FOR INITIATE EVENT, THE
SYSTEM ADMINISTRATOR OR AUTHORIZED USER SHALL BE ABLE
TO ENTER THE LETTERS NE (NEW EVENT) AS AN ALIAS FOR THE
SYSTEM SUPPORTED I.E. COMMAND.
3-2.3 (3) IT IS PREFERRED THAT THE SYSTEM ADMINISTRATOR OR OTHER
AUTHORIZED USERS HAVE THE ABILITY CHANGE THE DEFAULT
ORDER OF COMMAND PARAMETERS TO ALLOW ENTRY OF THE
REQUIRED INFORMATION IN ANY ORDER. FOR EXAMPLE, IF THE
I.E. COMMAND IS FOLLOWED BY THE LOCATION OF THE CALL, THE
EVENT TYPE AND THE REPORTING PERSON’S NAME IN THE
VENDOR’S PRODUCT, THE SYSTEM ADMINISTRATOR OR
AUTHORIZED USER SHALL BE ABLE TO MODIFY THE APPLICATION
TO ACCEPT THE EVENT TYPE, THEN LOCATION, THEN REPORTING
PERSON.
3-2.3 (4) THE PROPOSED APPLICATION SHALL INCLUDE A SINGLE KEY OR
SINGLE KEYSTROKE COMBINATION COMMAND WHICH WILL
RETURN THE USER TO THE CAD COMMAND LINE FROM ANY OTHER
APPLICATION, MODULE OR WINDOW.
3-2.3 (5) AT A MINIMUM THE PROPOSED APPLICATION SHALL ALLOW THE
USER TO RECALL UP TO 50 PREVIOUSLY ENTERED COMMAND LINE
ENTRIES AND REUSE THEM AS THEY WERE TYPED IN OR TO
MODIFY AND RE-SUBMIT THEM.
3-2.3 (6) THE PROPOSED APPLICATION SHALL ALLOW THE NUMBER, SIZE,
LOCATION, ORIENTATION, CONTENT AND COLOR-CODING OF
STATUS WINDOWS TO BE CONFIGURED BY THE USER AGENCY.
3-2.3 (7) IT IS PREFERRED THAT THE CAD CLIENT ALLOW THE STATUS
WINDOW CONFIGURATION TO BE TIED TO THE USER’S LOG ON.
3-2.3 (8) THE PROPOSED APPLICATION SHALL ALLOW ALL USERS TO
CONFIGURE THE WINDOWS TO SUIT THEIR INDIVIDUAL NEEDS.
City of Fort Collins cxiv Proposal P-847
3-2.3 (9) MESSAGE AND DIALOG BOXES, WHICH ARE DISPLAYED
AUTOMATICALLY BY THE PROPOSED APPLICATION, RATHER THAN
IN RESPONSE TO A USER REQUEST, SHALL NOT COVER OTHER
WINDOWS SO AS TO IMPEDE THE EFFICIENT PROCESSING OF
CALLS FOR SERVICE OR OTHER WORK.
3-2.3 (10) ERROR MESSAGES SHALL BE DISPLAYED IN A LOCATION, WHICH
WILL NOT HINDER THE OPERATOR’S VIEW OF OTHER DATA.
3-2.3 (10.1) ERROR MESSAGES SHALL BE DISPLAYED IN A CONSISTENT
LOCATION.
3-2.3 (11) THE PROPOSED APPLICATION SHALL ALLOW AN AUTHORIZED
USER TO EDIT ANY FIELD IN THE INCIDENT MASK FROM THE
COMMAND LINE AND FROM A FORM. THESE CHANGES SHALL BE
ACCOMPLISHED IN CALLS THAT ARE:
3-2.3 (11.1) PENDING
3-2.3 (11.2) ACTIVE
3-2.3 (11.3) CLOSED (WITHOUT RE-OPENING)
3-2.3 (11.4) CANCELLED (WITHOUT RE-OPENING)
3-2.3 (12) THE PROPOSED APPLICATION SHALL ALLOW AN INCIDENT TO BE
RETRIEVED FOR EDITS BY UTILIZING THE FOLLOWING:
3-2.3 (12.1) INCIDENT NUMBER I.E. “CHG #1234…..”
3-2.3 (12.2) UNIT NUMBER I.E. “CHG 8K58…..”
3-2.3 (12.3) CASE (REPORT) NUMBER
3-2.3 (13) ANY TIME A FIELD VALUE IS CHANGED THE SYSTEM SHALL TRACK
THE PREVIOUS VALUE IN THE AUDIT TRAIL AND ATTACH A
TIME/DATE/USER STAMP.
3-2.3 (14) IT IS PREFERRED THAT THE SOFTWARE SOLUTION INCORPORATE
DATA VALIDATION AT THE FIELD LEVEL FOR CAD WORKSTATIONS.
THE OBJECT OF THIS REQUIREMENT IS TO ENHANCE SYSTEM USE
BY CATCHING INCORRECT ENTRIES AND INCOMPLETE FORMS
PRIOR TO THE USER SENDING THEM TO THE CAD APPLICATION
FOR PROCESSING.
3-2.3 (15) IN THE EVENT THAT THE DATA ENTERED INTO A RESTRICTED
FIELD IS INCORRECT OR INCOMPLETE THE PROPOSED
APPLICATION SHALL RETURN THE CURSOR TO THE FIRST
City of Fort Collins cxv Proposal P-847
INCORRECT OR INCOMPLETE FIELD AUTOMATICALLY AND
PROVIDE AN EXPLANATION OF THE ERROR OR THE REQUIRED
INFORMATION SOMEWHERE ON THE SCREEN.
3-2.3 (16) IT IS PREFERRED THAT THE PROPOSED SYSTEM ALLOW ON-LINE
HELP AT THE INCIDENT FIELD LEVEL.
3-2.3 (17) IN THE EVENT THAT THE USER HAS MADE MORE THAN ONE
MISTAKE THE PROPOSED APPLICATION SHALL STEP THROUGH
EACH INCORRECT FIELD SEQUENTIALLY UNTIL ALL CORRECTIONS
HAVE BEEN MADE.
3-2.3 (18) THE PROPOSED APPLICATION SHALL HAVE THE ABILITY TO
PERFORM LOGIC CHECKS ON ENTERED DATA AS WELL. FOR
EXAMPLE, IF THE USER HAS NOT ENTERED CORRECT INCIDENT
TYPE THE SYSTEM SHALL FLAG IT AS AN ERROR. THE FOLLOWING
FIELDS SHALL UTILIZE THIS LOGIC CHECK:
3-2.3 (18.1) INCIDENT TYPE
3-2.3 (18.2) PRIORITY FIELD
3-2.3 (18.3) DISPOSITION FIELD
3-2.3 (18.4) POLICE AREA FIELD
3-2.3 (19) IF A FIELD HAS RESTRICTED VALUES THE USER SHALL ONLY BE
ABLE TO CHOOSE ONE OF THE PREVIOUSLY DEFINED VALUES.
3-2.3 (20) THE PROPOSED APPLICATION SHALL ALERT THE USER BOTH
VISUALLY AND AUDIBLY THAT AN ANSWER TO A PREVIOUSLY
SUBMITTED QUERY HAS BEEN RECEIVED.
3-2.3 (21) THE ALERT OF AN ARRIVING RETURN SHALL NOT INTERRUPT THE
USER’S WORKFLOW.
3-2.3 (22) IT IS PREFERRED THAT THE SYSTEM INCORPORATE A COUNTER
INTO THEIR ALERT SO THAT USERS CAN SEE HOW MANY RETURNS
ARE WAITING TO BE VIEWED.
3-2.3 (23) IT IS PREFERRED THAT THE SYSTEM DIFFERENTIATE THE RETURN
BY THE SENDER (E.G. NCIC, DMV, RMS, ETC.).
3-2.3 (24) THE TIME, POSITION ID NUMBER, USER ID NUMBER, AND CAD MODE
(LIVE OR TRAINING) SHALL BE DISPLAYED DISCREETLY IN THE
WORK AREA AT ALL TIMES WHILE A WORKSTATION IS LOGGED ON.
City of Fort Collins cxvi Proposal P-847
3-2.3 (25) THE PROPOSED APPLICATION SHALL SUPPORT THE FOLLOWING
MEANS IN WHICH A DISPATCHER OR CALL-TAKER MAY ENTER,
QUERY, OR EDIT INCIDENT INFORMATION:
3-2.3 (25.1) BY COMMAND LINE FUNCTIONS,
3-2.3 (25.2) BY POINTING DEVICE (MOUSE FUNCTIONS WITH DROP DOWN
MENUS),
3-2.3 (25.3) BY FORMS,
3-2.3 (25.4) OR CHECK BOX.
3-2.3 (26) THE PROPOSED APPLICATION SHALL ALLOW UNIT STATUS
CHANGES TO BE COMPLETED IN THE FOLLOWING WAYS:
3-2.3 (26.1) BY COMMAND LINE FUNCTIONS,
3-2.3 (26.2) BY POINTING DEVICE (MOUSE FUNCTIONS WITH DROP DOWN
MENUS),
3-2.3 (26.3) OR CHECK BOX.
3-2.3 (27) THE PROPOSED APPLICATION SHALL ALLOW NEW EVENTS TO BE
ENTERED DIRECTLY FROM THE COMMAND LINE.
3-2.4 EVENT AND UNIT STATUS MONITORS AND FUNCTIONS
3-2.4 (1) THE PROPOSED APPLICATION SHALL ALLOW FOR NO LESS THAN
300 USER-DEFINED UNITS AND EVENT STATUSES PER
DISPATCHER/DISTRICT.
3-2.4 (2) EACH EVENT AND UNIT STATUS SHALL HAVE AN ASSOCIATED USER-
DEFINED TIMER.
3-2.4 (3) THE PROPOSED APPLICATION SHALL USE COLOR OR OTHER
VISUAL SIGNALS AS WELL AS TEXT TO HELP DIFFERENTIATE UNIT
AND EVENT STATUSES. FOR EXAMPLE, THE NOTATION FOR AN EN
ROUTE UNIT MIGHT BE A WHITE “EN” ON A BLACK BACKGROUND.
THE NOTATION FOR AN EN ROUTE UNIT, WHICH HAS TIMED OUT
MIGHT BE A RED “EN” ON A BLACK BACKGROUND.
3-2.4 (4) THE PROPOSED APPLICATION SHALL ALLOW THE SYSTEM
ADMINISTRATOR OR AUTHORIZED USER TO SELECT WHICH
COLORS AND COLOR COMBINATIONS INDICATE WHICH STATUSES.
City of Fort Collins cxvii Proposal P-847
3-2.4 (5) IF THE APPLICATION USES AUDIBLE ALERTS, THE APPLICATION
SHALL ALLOW THE SYSTEM ADMINISTRATOR OR AUTHORIZED
USER TO DISABLE THESE ALERTS ON A TASK BASIS.
3-2.4 (6) IT IS PREFERRED THAT THE PROPOSED APPLICATION HAVE THE
CAPABILITY TO ACTIVATE AN AUDIBLE SIGNAL WHEN AN EVENT
UPDATE INCLUDES A HIGHER PRIORITY.
3-2.4 (7) IT IS PREFERRED THAT EACH UNIT STATUS HAVE A MEANS OF
DEFINING WHETHER A UNIT IN THE STATUS SHALL BE:
3-2.4 (7.1) RECOMMENDED FOR AN ASSIGNMENT,
3-2.4 (7.2) AVAILABLE FOR AN ASSIGNMENT EVEN THOUGH NOT
RECOMMENDED.
3-2.4 (8) THE PROPOSED APPLICATION SHALL ALLOW THE USE OF “STATUS
CODES”. STATUS CODES SHALL BE CONFIGURED AS NEEDED BY
THE SYSTEM ADMINISTRATOR OR AUTHORIZED USER. (STATUS
CODES ARE DEFINED AS CODES USED BY UNITS TO LOG
ADMINISTRATIVE TIME, MEAL BREAKS, AND OTHER ACTIVITY
THAT DOES NOT REQUIRE AN INCIDENT TO BE INITIATED)
3-2.4 (9) THE PROPOSED APPLICATION SHALL ALLOW FOR AT LEAST TWO
CHARACTER STATUS CODES.
3-2.4 (10) THE PROPOSED APPLICATION SHALL ALLOW FOR STATUS CODES
TO BE COLOR CODED BY THE SYSTEM ADMINISTRATOR OR
AUTHORIZED USER
3-2.4 (11) THE PROPOSED APPLICATION SHALL ALLOW STATUS OF ALL UNITS
ON A SINGLE INCIDENT BE CHANGED AT ONCE BY UTILIZING THE
INCIDENT NUMBER FROM THE COMMAND LINE I.E. “#1234 C4”.
3-2.4 (12) THE PROPOSED APPLICATION SHALL ALLOW FOR AT LEAST 5
UNIT’S STATUS’ TO BE CHANGED AT ONE TIME FROM THE
COMMAND LINE.
3-2.4 (13) THE PROPOSED APPLICATION SHALL ALLOW USERS TO INITIATE
STATUS CHANGES WITH THE COMMAND LINE AND BY USING A
POINTING DEVICE (MOUSE) WITH AN ASSOCIATED “DROP DOWN”
MENU THAT LISTS ALL STATUS CODES.
3-2.4 (14) EACH STATUS CHANGE SHALL BE TIME\DATE\USER STAMPED AND
RECORDED IN THE AUDIT TRAIL.
City of Fort Collins cxviii Proposal P-847
3-2.4 (15) THE PROPOSED APPLICATION SHALL ALLOW THE SYSTEM
ADMINISTRATOR OR AUTHORIZED USER TO DEFINE STATUS
WINDOWS.
3-2.4 (16) AT A MINIMUM THE APPLICATION SHALL ALLOW FOR THE
FOLLOWING EVENT AND UNIT WINDOWS:
3-2.4 (16.1) EVENTS WHICH HAVE NOT BE REVIEWED BY A DISPATCHER
(WAITING/NEW)
3-2.4 (16.2) EVENTS WHICH HAVE BEEN REVIEWED AND ARE WAITING TO BE
DISPATCHED(PENDING)
3-2.4 (16.3) STACKED EVENTS
3-2.4 (16.4) ACTIVE EVENTS
3-2.4 (16.5) UNITS ON DUTY AND AVAILABLE
3-2.4 (16.6) UNITS ASSIGNED TO CALLS (UNIT STATUS)
3-2.4 (17) AT A MINIMUM THE WAITING AND PENDING EVENTS DISPLAYS
SHALL SHOW THE EVENT TYPE, ADDRESS, LOCATION, PRIORITY,
PATROL/FIRE DISTRICT, TIME IN STATUS, AND EVENT NUMBER.
3-2.4 (18) IT IS PREFERRED THAT THE SYSTEM ALLOW FOR THE DISPLAY OF
THE FIELDS IN ANY EVENT OR UNIT STATUS MONITOR TO BE
REORGANIZED AND SORTED BY ONE OR MORE CRITERIA BY THE
USER.
3-2.4 (19) ONCE AN EVENT HAS BEEN DISPATCHED OR REFERRED, IT SHALL
BE REMOVED FROM THE WAITING OR PENDING EVENTS DISPLAY.
3-2.4 (20) THE UNIT STATUS DISPLAY SHALL MINIMALLY DISPLAY THE UNIT
NUMBER, STATUS, TIME IN STATUS, CURRENT LOCATION, EVENT
ADDRESS AND ASSIGNMENT TYPE.
3-2.4 (21) IT IS PREFERRED THAT THE SYSTEM ALLOW FOR THE DISPLAY OF
THE FIELDS IN THE UNIT STATUS DISPLAY TO BE:
3-2.4 (21.1) REORGANIZED,
3-2.4 (21.2) SORTED BY ONE OR MORE CRITERIA,
3-2.4 (21.3) GROUPED ACCORDING TO UNITS ASSIGNED TO THE SAME EVENT,
AND
3-2.4 (21.4) OTHER RELEVANT CRITERIA BY THE USER.
City of Fort Collins cxix Proposal P-847
3-2.4 (22) THE PROPOSED APPLICATION SHALL ALWAYS DISPLAY THE LAST
RECORDED LOCATION OF EACH UNIT WITH PREVIOUS LOCATIONS
OR CHANGES IN LOCATION RETAINED IN THE AUDIT TRAIL WITH
AN ATTACHED DATE/TIME/USER STAMP.
3-2.4 (23) DISPATCHERS SHALL BE ALERTED TO ALL EVENT UPDATES MADE
BY ANOTHER USER UTILIZING A VISUAL ALERT AND AN AUDIBLE
ALERT. THE SYSTEM ADMINISTRATOR OR AUTHORIZED USER
SHALL HAVE THE ABILITY TO EASILY CHANGE THE SOUND OF THE
ALERT, AS WELL AS DISABLE THE ALERT AS NEEDED.
3-2.4 (24) THE PROPOSED APPLICATION SHALL SHOW THE USER ALL
UPDATES TO AN EVENT IN REAL-TIME IF THE USER HAS THE
INCIDENT DISPLAYED.
3-2.4 (24.1) IT IS PREFERRED THAT THE SYSTEM VISUALLY DIFFERENTIATE
THESE UPDATES TO MAKE THEM EASIER TO SEE WHEN THE
INCIDENT IS DISPLAYED.
3-2.4 (25) AT A MINIMUM THE PROPOSED APPLICATION SHALL HAVE THE
ABILITY TO RECORD THE DATE/TIME/USER FOR EACH OF THE
FOLLOWING STATUSES:
3-2.4 (25.1) CALL RECEIVED
3-2.4 (25.2) CALL REVIEWED
3-2.4 (25.3) CALL ASSIGNED TO UNIT’S STACK
3-2.4 (25.4) DISPATCHED
3-2.4 (25.5) EN ROUTE
3-2.4 (25.6) ON-SCENE
3-2.4 (25.7) PRE-EMPT
3-2.4 (25.8) ANY STATUS CHANGE /ADDITIONAL UNITS
3-2.4 (25.9) LOCATION CHANGE
3-2.4 (25.10) EMS/FIRE CALL GENERATED AND CROSS REFERENCED
3-2.4 (25.11) WRECKER CALLED
3-2.4 (25.12) CLEARED
3-2.4 (25.13) EVENT CLOSED
City of Fort Collins cxx Proposal P-847
3-2.4 (25.14) REOPEN
3-2.4 (25.15) CASE (REPORT) NUMBER ADDED
3-2.4 (25.16) CALL UPDATED
3-2.4 (26) THE PROPOSED APPLICATION SHALL ALWAYS DATE/TIME/USER
STAMP ANY UPDATES OR CHANGES.
3-2.4 (27) THE PROPOSED APPLICATION SHALL ALLOW OPERATORS TO
EASILY IDENTIFY MDT/MDC EQUIPPED VEHICLES BY USE OF
SYMBOLS ATTACHED TO UNIT ID’S.
3-2.5 LOG ON/OFF COMMANDS
3-2.5 (1) THE PROPOSED APPLICATION SHALL ALLOW USERS TO BE SIGNED
ONTO MULTIPLE WORKSTATIONS AND/OR MOBILE UNITS AT ONE
TIME WITHOUT FIRST HAVING TO LOG-OFF OF THEIR CURRENT
WORKSTATION OR MOBILE.
3-2.5 (2) THE PROPOSED APPLICATION SHALL NOT ALLOW A CAD USER TO
SIGN OFF UNDER THE FOLLOWING CONDITIONS:
3-2.5 (2.1) NO OTHER WORKSTATION IS SIGNED ON TO COVER THE AREA
WHICH THE WORKSTATION SIGNING OFF IS VACATING.
3-2.5 (2.2) UNITS UNDER THE CONTROL OF THE WORKSTATION SIGNING
OFF ARE NOT BEING CONTROLLED BY ANY OTHER
WORKSTATION.
3-2.5 (3) WHENEVER A LOG ON OR LOG OFF ATTEMPT IS REJECTED BY THE
APPLICATION THE APPLICATION SHALL DISPLAY AN ERROR
MESSAGE EXPLAINING WHY THE ACTION WAS REJECTED.
3-2.5 (4) THE PROPOSED APPLICATION SHALL PROVIDE A MEANS FOR AN
OPERATOR TO LOG ON TO AN ACTIVE WORKSTATION WITHOUT
TRANSFERRING THE CALL LOAD OR UNITS TO ANOTHER
WORKSTATION. THIS WILL FACILITATE THE RAPID TRANSFER OF
RESPONSIBILITY FROM ONE OPERATOR TO ANOTHER DURING
BREAKS AND SHIFT CHANGES.
3-2.5 (5) A COMMAND SHALL BE PROVIDED WHICH WILL ENABLE A
SUPERVISOR TO LOG OFF ANY USER FROM ANY WORKSTATION OR
MDC.
3-2.5 (6) THERE SHALL BE NO LIMIT TO THE NUMBER OF WORKSTATIONS
WHICH CAN SIGN ON TO A GIVEN GEOGRAPHIC ZONE
City of Fort Collins cxxi Proposal P-847
SIMULTANEOUSLY ASSUMING THAT ALL HAVE PROPER SECURITY
CLEARANCE.
3-2.5 (7) UPON LOG-ON, ALL USERS WITH AN OSN SHALL BE
AUTOMATICALLY LOGGED ONTO THE CCIC/NCIC SYSTEM
WITHOUT FURTHER ACTION BY THE USER.
3-2.5 (8) IT IS PREFERRED THAT THE SYSTEM ALLOW THE USE OF
ABBREVIATED, UNIQUE UNIT NUMBERS BY THE DISPATCHER OR
MOBILE USER. FOR EXAMPLE: A UNIT IS LOGGED ON AS UNIT
NUMBER “4B150”, BUT IF THE USER TYPES ONLY “B150”, THE
SYSTEM SHALL RECOGNIZE THIS AS “4B150” AND LOG ALL
ACTIVITY UNDER THE LOGGED ON UNIT NUMBER OF “4B150” FOR
STATISTICAL PURPOSES. THIS IS PROVIDED THERE ARE NO TWO
UNITS UTILIZING THE WHOLE OR PARTIAL UNIT NUMBER OF
“B150”.
3-3 CALL TAKING AND INITIATION
3-3.1 EVENT INITIATION PROCESSING
3-3.1 (1) ONLY THE EVENT TYPE AND ADDRESS SHALL BE REQUIRED TO
INITIATE A NEW CALL FROM THE COMMAND LINE OR FROM A
FORM.
3-3.1 (2) WHEN A CALL FOR SERVICE IS RECEIVED THE APPLICATION SHALL
ALLOW THE USER TO DISPLAY A BLANK FORM FOR ENTERING NEW
EVENTS WITH A SINGLE KEY OR SINGLE KEYSTROKE
COMBINATION OR MOUSE CLICK.
3-3.1 (3) IF THE NEW EVENT IS OCCURRING AT THE ALI REPORTED
LOCATION THE CALL TAKER SHALL NOT BE REQUIRED TO RE-
ENTER THE LOCATION DATA IN ANY OTHER FIELD.
3-3.1 (4) IF THE NEW EVENT IS NOT OCCURRING AT THE ALI REPORTED
LOCATION THE CALL TAKER SHALL ENTER THE EVENT ADDRESS IN
A SEPARATE LOCATION FIELD AND THE PROPOSED APPLICATION
SHALL USE THIS ADDRESS FOR ADDRESS VERIFICATION AND
DISPATCH ROUTING.
3-3.1 (5) THE PROPOSED APPLICATION SHALL ALLOW FOR AN INTERFACE
TO THE PLANTRONICS VESTA SYSTEM TDD CAPABILITIES AS
OUTLINED IN THE AMERICAN’S WITH DISABILITIES ACT.
3-3.1 (6) WHEN A TDD TONE IS DETECTED BY THE PHONE SYSTEM, IT WILL
COMMUNICATE IN SOME WAY WITH THE CAD SYSTEM, WHICH
WILL IN TURN, POP A SEPARATE WINDOW IN WHICH THE
DISPATCHER CAN COMMUNICATE WITH THE REPORTING PARTY.
City of Fort Collins cxxii Proposal P-847
3-3.1 (7) ALL TEXT OF THE TDD COMMUNICATION SHALL BE
AUTOMATICALLY ADDED TO THE AUDIT TRAIL FOR LATER REVIEW.
THIS FUNCTION SHALL BE TRANSPARENT TO THE DISPATCHER.
3-3.1 (8) IF THE NEW CALL IS BEING RECEIVED ON ANY PHONE LINE WHICH
OFFERS ANI OR ALI DATA THE PROPOSED APPLICATION SHALL
ALLOW THE TRANSFER OF THE ANI/ALI DATA FROM THE
TELEPHONE SYSTEM TO THE APPROPRIATE FIELDS ON THE EVENT
FORM WITH A SINGLE KEY OR SINGLE KEYSTROKE COMBINATION
OR OPERATOR ACTION. THE FIELDS TRANSFERRED WILL INCLUDE,
BUT ARE NOT LIMITED TO:
3-3.1 (8.1) CALLER ADDRESS INCLUDING CITY/COMMUNITY CODE
3-3.1 (8.2) LOCATION/BUSINESS NAME IF APPLICABLE
3-3.1 (8.3) CALLER’S PHONE NUMBER
3-3.1 (8.4) CALLER’S NAME
3-3.1 (9) ONCE THE CALL TAKER HAS ENTERED THE INFORMATION
NECESSARY TO CREATE A NEW EVENT A SINGLE KEY OR SINGLE
KEYSTROKE COMBINATION OR OPERATOR ACTION SHALL BE USED
TO SUBMIT THE NEW EVENT.
3-3.1 (10) THE CAD SYSTEM SHALL AUTOMATICALLY COMPLETE THE
FOLLOWING ACTIONS WITH A NEWLY SUBMITTED EVENT:
3-3.1 (10.1) ADDRESS VERIFICATION
3-3.1 (10.2) HAZARD RECORDS INQUIRY
3-3.1 (10.3) PREMISE RECORDS INQUIRY
3-3.1 (10.4) DETERMINE POLICE DISTRICT (BEAT)
3-3.1 (10.5) DETERMINE THE HIGH AND LOW CROSS STREETS FOR THE
VERIFIED ADDRESS
3-3.1 (10.6) DETERMINE MAP PAGE
3-3.1 (11) AFTER THE CAD APPLICATION HAS COMPLETED THESE STEPS THE
NEW EVENT SHALL BE SIMULTANEOUSLY ROUTED TO THE
CORRECT DISPATCH POSITION(S) AND RE-DISPLAYED AT THE CALL
TAKERS POSITION FOR IMMEDIATE UPDATE WITHOUT FURTHER
ACTIONS OR KEYSTROKES FROM BY THE CALL-TAKER.
City of Fort Collins cxxiii Proposal P-847
3-3.1 (12) IT IS PREFERRED THAT THE CALL TAKER HAVE THE ABILITY TO
DETERMINE WHICH FORM THE APPLICATION WILL DISPLAY AFTER
EACH CALL IS ROUTED.
3-3.1 (13) IT IS PREFERRED THAT THE SYSTEM ADMINISTRATOR OR
AUTHORIZED USER BE ABLE TO SET A DEFAULT FORM WHICH WILL
APPEAR AFTER A NEW CALL HAS BEEN COMPLETED.
3-3.1 (14) CALL TAKERS SHALL BE PERMITTED TO ADD ADDITIONAL
INFORMATION TO A CALL FOR SERVICE RECORD BEFORE AND
SUBSEQUENT TO DISPATCH.
3-3.1 (15) USERS SHALL BE PERMITTED TO ADD COMMENTS TO A CALL FOR
SERVICE RECORD AFTER THE CALL IS CLOSED WITHOUT
REOPENING THE EVENT.
3-3.1 (16) USERS SHALL BE PERMITTED TO ADD A CASE (REPORT) NUMBER TO
A CALL FOR SERVICE RECORD AFTER THE CALL IS CLOSED
WITHOUT REOPENING THE EVENT.
3-3.1 (17) USERS SHALL BE PERMITTED TO CHANGE INFORMATION IN ANY OF
THE INCIDENT FIELDS IN A CALL FOR SERVICE RECORD AFTER THE
CALL IS CLOSED WITHOUT REOPENING THE EVENT.
3-3.1 (18) THE PROPOSED APPLICATION SHALL ALLOW NEW EVENTS TO BE
SCHEDULED FOR SERVICE AT A FUTURE TIME AND DATE.
3-3.1 (19) IT IS PREFERRED THAT THE PROPOSED APPLICATION PROVIDE A
MEANS OF SCHEDULING REOCCURRING EVENTS SUCH AS
TRANSPORTING A PATIENT TO A FACILITY FOR REGULAR
TREATMENTS AT A CERTAIN DATE/TIME EACH DAY/WEEK OR
MONTH.
3-3.1 (20) THE PROPOSED APPLICATION SHALL PROCESS THE ADDRESS
VERIFICATION, PREMISE RECORDS AND OTHER EVENT ROUTINES
FOR A SCHEDULED EVENT IN THE SAME MANNER AS A
UNSCHEDULED EVENT. HOWEVER, THE EVENT SHALL NOT APPEAR
ON THE DISPATCHER’S PENDING EVENT MONITOR UNTIL A USER-
DEFINED TIME PERIOD BEFORE THE EVENT IS SCHEDULED FOR
DISPATCH.
3-3.1 (21) IT IS PREFERRED THAT THE APPLICATION SUPPORT THE ABILITY
TO IMMEDIATELY TRANSFER CALL DATA TO DISPATCH FOR A HOT-
CALL/EMERGENCY, WITHOUT WAITING FOR COMPLETION OF THE
CALL TAKER SCREEN.
3-3.1 (22) THE PROPOSED APPLICATION SHALL UTILIZE A SEPARATE
“VEHICLE/SUBJECT” MASK/FORM/TAB TO ASSIST THE DISPATCHER
City of Fort Collins cxxiv Proposal P-847
IN SPECIFICALLY IDENTIFYING VEHICLES AND SUBJECTS. ALL
INFORMATION ENTERED WILL BE ATTACHED TO THE AUDIT TRAIL
AUTOMATICALLY WITH A DATE/TIME/USER STAMP. THE FIELDS
FOR THIS FORM ARE DEFINED AS FOLLOWS:
3-3.1 (22.1) ALL VEHICLE DESCRIPTOR FIELDS DEFINED AS “CYMBALS”:
3-3.1 (22.2) COLOR
3-3.1 (22.3) YEAR
3-3.1 (22.4) MAKE
3-3.1 (22.5) BODY STYLE
3-3.1 (22.6) ADDITIONAL INFORMATION
3-3.1 (22.7) LICENSE
3-3.1 (22.8) STATE
3-3.1 (23) ALL PERSON DESCRIPTOR FIELDS SHALL BE AS FOLLOWS:
3-3.1 (23.1) RACE
3-3.1 (23.2) SEX
3-3.1 (23.3) AGE
3-3.1 (23.4) HEIGHT
3-3.1 (23.5) WEIGHT
3-3.1 (23.6) HAIR
3-3.1 (23.7) EYES
3-3.1 (23.8) CLOTHING/ADDITIONAL DESCRIPTIONS.
3-3.1 (24) THE PROPOSED APPLICATION SHALL AUTOMATICALLY QUERY THE
PLATE, VIN, OR PERSON (IF DOB INCLUDED) THROUGH THE
FOLLOWING DATABASES:
3-3.1 (24.1) RMS/JMS
3-3.1 (24.2) CCIC
3-3.1 (24.3) NCIC
City of Fort Collins cxxv Proposal P-847
3-3.1 (24.4) DMV (AS APPLICABLE)
3-3.1 (24.5) DOR (AS APPLICABLE)
3-3.1 (25) THE PROPOSED APPLICATION SHALL PROVIDE A MEANS OF
CREATING A COPY OF ACTIVE EVENT. WHEN THIS FUNCTION IS
SELECTED, THE SYSTEM SHALL CREATE A NEW EVENT, AT THE
SAME LOCATION, WITH THE SAME COMPLAINANT, AND A NEW
INCIDENT NUMBER, AND ROUTE THE EVENT ACCORDING TO CALL-
TYPE AND/OR JURISDICTION (CLONE INCIDENT).
3-3.1 (26) THE PROPOSED APPLICATION SHALL PROVIDE A MEANS OF
INITIATING AN EVENT AND CLOSING IT IMMEDIATELY WITHOUT
ROUTING IT TO A DISPATCHER. THIS FUNCTION COULD BE USED
FOR EXAMPLE TO CREATE AN EVENT AND ISSUE A CASE (REPORT)
NUMBER FOR AN EVENT WHICH OCCURRED EARLIER (ADVISED
EVENTS).
3-3.1 (27) THE PROPOSED CAD APPLICATION SHALL INCLUDE THE ABILITY
TO AUTOMATICALLY ASSIGN A UNIQUE CONTROL NUMBER TO
EACH CATALOGED ALARM.
3-3.1 (27.1) WHEN THIS CONTROL NUMBER IS ENTERED DURING A SEARCH
THE SYSTEM SHALL RETRIEVE THE PREVIOUSLY ENTERED
ADDRESS FOR THE CALL, THE NATURE CODE, AND ANY
COMMENTS ASSOCIATED WITH THE CALL.
3-3.1 (28) IT WOULD BE PREFERRED THAT THE PROPOSED APPLICATION
ALSO ALLOW FOR AN AUTHORIZED USER TO OVERRIDE THE
AUTOMATICALLY ASSIGNED CONTROL NUMBER AND ENTER A
CONTROL NUMBER (FROM ANOTHER SOURCE) MANUALLY SO
LONG AS THE MANUALLY ENTERED CONTROL NUMBER IS UNIQUE
TO THE SYSTEM.
3-3.2 ADDRESS VALIDATION
3-3.2 (1) WHEN AN EVENT IS INITIATED THE PROPOSED APPLICATION SHALL
VERIFY THE ADDRESS AGAINST THE GEO-FILE TO DETERMINE ITS
EXACT LOCATION, RESPONSIBLE AGENCY AND OTHER DATA
REQUIRED FOR COMPLETING THE EVENT INITIATION AND
RECOMMENDING RESOURCES.
3-3.2 (2) THE PROPOSED APPLICATION SHALL BE ABLE TO VERIFY THE
ADDRESS AS SOON AS IT IS ENTERED INTO THE ADDRESS FIELD
WITH ONE KEYSTROKE COMBINATION. IT WILL BE UP TO THE
DISPATCHER TO VERIFY AT THIS POINT, OR WAIT UNTIL ALL THE
INFORMATION IS ENTERED INTO THE CALL BEFORE
VERIFICATION/ENTRY.
City of Fort Collins cxxvi Proposal P-847
3-3.2 (3) WHEN AN ADDRESS OR LOCATION IS ENTERED WHICH MATCHES A
UNIQUE LOCATION RECORD IN THE GEO-FILE, THE SYSTEM SHALL
IMMEDIATELY ACCEPT THIS ADDRESS AS THE CORRECT ADDRESS
AND NOT REQUIRE THE USER TO CONFIRM THE ADDRESS.
3-3.2 (4) IF A USER ENTERS AN ADDRESS WHICH DOES NOT MATCH A
UNIQUE GEO-FILE LOCATION RECORD THE SYSTEM SHALL
PRESENT THE 10 CLOSEST POSSIBLE MATCHES TO THE LOCATION
ENTERED AND ALLOW THE USER TO SELECT THE CORRECT
LOCATION FOR THE CALL.
3-3.2 (5) THE PROPOSED APPLICATION SHALL BE ABLE TO RE-VERIFY ANY
ADDRESS THAT HAS PREVIOUSLY GONE THROUGH ADDRESS
VERIFICATION AT THE OPERATORS DISCRETION.
3-3.3 STREET ADDRESSES
3-3.3 (1) THE PROPOSED APPLICATION SHALL ACCEPT LOCATIONS
ENTERED AS STREET ADDRESSES (E.G. 123 MAIN ST.).
3-3.3 (2) IF THE STREET NAME DOES NOT MATCH A GEO-FILE LOCATION
RECORD THE PROPOSED APPLICATION SHALL UTILIZE A
“SOUNDEX” OR OTHER PHONETIC ALGORITHM TO DEVELOP AND
PRESENT A LIST OF STREETS WHICH MOST CLOSELY MATCH THE
ONE ENTERED BY THE USER.
3-3.3 (3) IF A CORRECT STREET NAME BUT INCORRECT ADDRESS NUMBER IS
ENTERED THE PROPOSED APPLICATION SHALL PRESENT A LIST OF
ALL VALID ADDRESS RANGES FOR THE GIVEN STREET.
3-3.3 (4) IF A USER ENTERS A STREET ADDRESS WITHOUT A SUFFIX (ST.,
BLVD., RD) AND THE GEO-FILE CONTAINS MORE THAN ONE
RECORD FOR THAT STREET WITH DIFFERENT SUFFIXES THE
PROPOSED APPLICATION SHALL DISPLAY ALL VARIATIONS OF THE
LOCATION NAME AND PROMPT THE USER TO SELECT THE
CORRECT ENTRY.
3-3.3 (5) IF A USER ENTERS A STREET ADDRESS WITHOUT A DIRECTIONAL
(N, S, E, W, ETC.) AND THE GEO-FILE CONTAINS MORE THAN ONE
RECORD FOR THAT STREET WITH DIFFERENT DIRECTIONAL
PREFIXES THE PROPOSED APPLICATION SHALL DISPLAY ALL
VARIATIONS OF THE LOCATION NAME AND PROMPT THE USER TO
SELECT THE CORRECT ENTRY.
3-3.3 (6) THE PROPOSED APPLICATION SHALL ACCEPT AS LITTLE AS TWO
CHARACTERS FOR A STREET OR COMMONPLACE NAME DURING
THE ADDRESS VERIFICATION ROUTINE (PARTIAL ADDRESS).
City of Fort Collins cxxvii Proposal P-847
3-3.3 (7) IT IS PREFERRED THAT THE PROPOSED APPLICATION HAVE THE
ABILITY TO ACCEPT HUNDRED BLOCK LOCATIONS. FOR EXAMPLE,
A CALLER MAY REPORT JUVENILES SPEEDING IN THE 2400 BLOCK
OF S COLLEGE AVE.
3-3.3 (7.1) THE PROPOSED APPLICATION SHALL ALLOW CALL TAKERS TO
DISTINGUISH BETWEEN CALLS OCCURRING AT THE FIRST EVEN
ADDRESS IN A BLOCK (E.G. 2400) AND THOSE WHICH ARE BEING
REPORTED FOR HUNDRED BLOCK LOCATIONS.
3-3.3 (8) THE PROPOSED APPLICATION SHALL UTILIZE MUNICIPALITY
DURING THE ADDRESS VERIFICATION PROCESS. IF THE GEO-FILE
CONTAINS THE SAME STREET AND ADDRESS FOR MULTIPLE
MUNICIPALITIES THE USER SHALL BE PROMPTED TO CHOOSE THE
CORRECT ADDRESS BASED ON THE MUNICIPALITY.
3-3.3 (9) IF A LOCATION MATCH IS NOT FOUND ON THE GEO-FILE, THE CALL
TAKER WILL BE PERMITTED TO BY-PASS VERIFICATION AND FORCE
THE LOCATION INTO THE PROPOSED APPLICATION BY DEFINING
THE FIRE/MEDICAL AND OR POLICE AREA TO WHICH IT BELONGS.
3-3.3 (10) THE PROPOSED APPLICATION SHALL LOG EACH OCCURRENCE OF
AN ADDRESS “OVERRIDE” AND PROVIDE A MEANS OF REPORTING
SUCH OCCURRENCES TO THE SYSTEM ADMINISTRATOR OR
AUTHORIZED USER.
3-3.4 INTERSECTIONS
3-3.4 (1) THE PROPOSED APPLICATION SHALL ACCEPT LOCATIONS
ENTERED AS INTERSECTIONS WITH THE STREET NAMES IN EITHER
ORDER AND THE STREET NAMES SEPARATED BY A SLASH (E.G.
MAIN/OAK).
3-3.4 (2) IF EITHER STREET NAME IS INVALID THE PROPOSED APPLICATION
SHALL UTILIZE A “SOUNDEX” ALGORITHM TO DEVELOP AND
PRESENT A LIST OF INTERSECTIONS WHICH INCLUDE THE VALID
STREET NAME AND WHICH MOST CLOSELY MATCH THE INVALID
STREET NAME.
3-3.4 (3) IF BOTH STREET NAMES ARE INVALID THE PROPOSED
APPLICATION SHALL UTILIZE A “SOUNDEX” ALGORITHM TO
DEVELOP AND PRESENT A LIST OF INTERSECTIONS WHICH MOST
CLOSELY MATCH THE TWO PARTIAL OR INVALID STREET NAMES.
3-3.4 (4) THE USER SHALL HAVE THE OPTION OF ENTERING A SPACE FOR
EITHER OF THE STREETS AT THE INTERSECTION IN ORDER TO
DISPLAY A LIST OF ALL STREETS INTERSECTING WITH THE VALID
STREET GIVEN BY THE USER.
City of Fort Collins cxxviii Proposal P-847
3-3.5 COMMONPLACE NAMES
3-3.5 (1) THE PROPOSED APPLICATION SHALL ACCEPT LOCATIONS
ENTERED AS COMMONPLACES (E.G. MCDONALD’S, CITY HALL,
POLICE HEADQUARTERS, ETC.)
3-3.5 (2) THE PROPOSED APPLICATION SHALL ALLOW COMMON PLACES TO
BE GROUPED INTO NO FEWER THAN 15 USER-DEFINED CATEGORIES
I.E. SCHOOLS, BUSINESSES, BANKS, BARS ETC.
3-3.5 (3) THE PROPOSED APPLICATION SHALL ALLOW FOR NO FEWER THAN
THREE COMMONPLACE ALIASES.
3-3.5 (4) THE PROPOSED APPLICATION SHALL ALLOW AT LEAST 60
CHARACTERS WHEN CONFIGURING COMMONPLACE NAMES.
3-3.5 (5) WHEN A COMMONPLACE IS ENTERED THE PROPOSED APPLICATION
SHALL RESPOND BY ENTERING THE OFFICIAL (OR PRE-
PROGRAMMED) ADDRESS INTO THE ADDRESS FIELD WITH THE
COMMONPLACE NAME IN THE LOCATION FIELD.
3-3.5 (6) WHEN A NON-UNIQUE (E.G. MCDONALD’S) COMMONPLACE NAME IS
ENTERED THE PROPOSED APPLICATION SHALL DISPLAY ALL
POTENTIAL MATCHES ALONG WITH THEIR ADDRESSES.
3-3.6 STREET ALIASES
3-3.6 (1) THE PROPOSED APPLICATION SHALL ALLOW AT LEAST THREE
ALIASES FOR EACH OFFICIAL STREET NAME AND INTERSECTION.
(E.G. MAIN STREET = STATE ROUTE 119, OR I-70= INTERSTATE ROUTE
70).
3-3.6 (2) THE PROPOSED APPLICATION SHALL ALLOW ALIASING DOWN TO
THE 100 BLOCK. FOR EXAMPLE, THE 100 BLOCK OF N LEMAY AVE IS
ALSO KNOWN AS NINTH ST, BUT ONLY IN THAT BLOCK.
3-3.6 (3) WHEN A STREET ALIAS IS USED TO ENTER AN EVENT THE
PROPOSED APPLICATION SHALL RECORD THE OFFICIAL ADDRESS
IN THE EVENT LOCATION FIELD AND THE ALIAS IN THE LOCATION
FIELD.
3-3.6 (4) IT IS PREFERRED THAT THE PROPOSED APPLICATION ALLOW THE
USER TO MANUALLY SEARCH THE AREA OF A GIVEN ADDRESS FOR
BUSINESS NAMES AND COMMONPLACE RECORDS.
City of Fort Collins cxxix Proposal P-847
3-3.7 EVENT UPDATES
3-3.7 (1) THE PROPOSED APPLICATION SHALL ALLOW ANY AUTHORIZED
USER TO ADD NEW OR ADDITIONAL INFORMATION TO AN EVENT
FROM A FORM AND FROM THE COMMAND LINE WHETHER THE
INCIDENT IS ACTIVE, PENDING, CLOSED OR CANCELLED.
3-3.7 (2) WHENEVER AN EVENT IS UPDATED ALL USERS, INCLUDING MOBILE
COMPUTERS, CONCERNED WITH THE EVENT SHALL BE NOTIFIED
BY A VISUAL AND AUDIBLE ALERT.
3-3.7 (2.1) VISUAL ALERTS GENERATED BY AN EVENT UPDATE SHALL NOT
COVER OTHER WINDOWS SO AS TO IMPEDE THE EFFICIENT
PROCESSING OF CALLS FOR SERVICE OR OTHER WORK.
3-3.7 (3) THE PROPOSED APPLICATION SHALL ALLOW A USER TO UPDATE
ANY FIELD EXCEPT, SYSTEM GENERATED TIMES AND DATES,
OPERATOR ID, AND CAD POSITION FROM A FORM AND FROM THE
COMMAND LINE.
3-3.7 (4) THE PROPOSED APPLICATION SHALL NOT EMPLOY RECORD
LOCKING WHEREBY USERS ARE PROHIBITED FROM MODIFYING AN
EVENT RECORD WHILE ANOTHER USER HAS THE EVENT RECORD
OPEN.
3-4 EVENT PROCESSING
3-4.1 GENERAL REQUIREMENTS
3-4.1 (1) THE PROPOSED APPLICATION SHALL HAVE A MEANS OF
AUTOMATICALLY IDENTIFYING POTENTIAL DUPLICATE CALLS FOR
SERVICE.
3-4.1 (2) THE PROPOSED APPLICATION SHALL IDENTIFY POTENTIAL
DUPLICATES BY SEARCHING WITHIN A USER-DEFINED DISTANCE
AROUND THE NEW CALL FOR SERVICE.
3-4.1 (3) THE PROPOSED APPLICATION SHALL INCLUDE RECENTLY CLOSED
EVENTS IN THE POTENTIAL DUPLICATE IDENTIFICATION PROCESS.
3-4.1 (3.1) THE DEFINITION OF “RECENTLY CLOSED” SHALL BE
DETERMINED THROUGH A CONFIGURATION PARAMETER
DEFINED BY THE SYSTEM ADMINISTRATOR OR AUTHORIZED
USER.
3-4.1 (4) THE PROPOSED APPLICATION SHALL NOTIFY THE CALL TAKER OF
POSSIBLE DUPLICATE EVENTS PRIOR TO THE NEW EVENT BEING
ROUTED TO THE DISPATCHER.
City of Fort Collins cxxx Proposal P-847
3-4.1 (5) EVENTS WHICH HAVE BEEN FLAGGED AS POTENTIAL DUPLICATE
CALLS:
3-4.1 (5.1) THE EXACT ADDRESS OF THE EVENT,
3-4.1 (5.2) THE TYPE OF EVENT,
3-4.1 (5.3) THE STATUS OF THE EVENT,
3-4.1 (5.4) THE TIME THE EVENT WAS INITIATED,
3-4.1 (5.5) AND THE UNIT ASSIGNED, IF ANY.
3-4.1 (6) IF A NEW CALL FOR SERVICE IS DETERMINED TO BE A DUPLICATE
CALL THE PROPOSED APPLICATION SHALL ALLOW THE CALL
TAKER TO:
3-4.1 (6.1) ADD A SECOND COMPLAINANT WITH COMPLETE COMPLAINANT
CONTACT INFORMATION, AND COMMENTS ABOUT THE EVENT TO
THE ORIGINAL EVENT RECORD,
3-4.1 (6.2) CLOSE THE EVENT WITH NO FURTHER ACTION,
3-4.1 (6.3) OR CREATE AN ENTIRELY NEW EVENT, USING EXISTING ADDRESS
DATA
3-4.1 (7) IF THE ORIGINAL EVENT IS UPDATED THE PROPOSED APPLICATION
SHALL THEN NOTIFY THE DISPATCHER THAT ADDITIONAL
INFORMATION HAS BEEN RECEIVED BY MARKING THE ORIGINAL
EVENT AS UPDATED.
3-4.1 (8) THE PROPOSED APPLICATION SHALL LOG ALL TRANSACTIONS
WITH A DATE/TIME/USER STAMP INTO AN AUDIT TRAIL. THE AUDIT
TRAIL SHALL BE EASILY ACCESSIBLE BY ALL USERS.
3-4.1 (9) THE AUDIT TRAIL SHALL BE VIEWABLE IN CHRONOLOGICAL
ORDER AND LAID OUT IN A FORMAT THAT IS EASY TO READ USING
DIFFERENT FONTS, FONT SIZES, COLORS, AND/OR STYLES TO
DIFFERENTIATE DATA FIELDS.
3-4.1 (10) THE PROPOSED APPLICATION SHALL PROVIDE AN EASY METHOD
TO ROUTE ANY SEARCHABLE INFORMATION FROM ANY DATABASE
ATTACHED TO THE CAD SYSTEM, TO A DEFAULT PRINTER(S).
3-4.1 (10.1) THE PRINTED FORMAT SHALL BE EASY TO READ USING
DIFFERENT FONTS, FONT SIZES, COLORS AND STYLES TO
DIFFERENTIATE DATA FIELDS.
City of Fort Collins cxxxi Proposal P-847
3-4.1 (11) THE PROPOSED APPLICATION SHALL PROVIDE A MEANS OF
RECALLING A UNIT’S LAST CALL (THAT HAS ALREADY BEEN
CLOSED) UTILIZING A SINGLE COMMAND WITH THE UNIT NUMBER.
I.E. “R 4B150”.
3-4.2 EVENT PRIORITIES
3-4.2 (1) THE PROPOSED APPLICATION SHALL AUTOMATICALLY ENTER A
USER-DEFINED PRIORITY FOR EACH NEW EVENT.
3-4.2 (2) THE APPLICATION SHALL ALLOW THE CALL TAKER OR
DISPATCHER TO UPGRADE OR DOWNGRADE THE SYSTEM ASSIGNED
PRIORITY FROM A FORM AND FROM THE COMMAND LINE.
3-4.3 EVENT ROUTING
3-4.3 (1) ONCE AN EVENT IS INITIATED, THE PROPOSED APPLICATION SHALL
AUTOMATICALLY ROUTE THE EVENT TO CORRECT DISPATCHER
BASED ON THE AGENCY, LOCATION AND EVENT TYPE.
3-4.3 (2) IT IS PREFERRED THAT THE SYSTEM HAVE THE ABILITY TO ROUTE
CALLS TO POLICE SERVICE TECHNICIANS FOR A TELEPHONE
REPORT BASED ON THE TIME OF DAY AND THE EVENT TYPE.
3-4.3 (3) WHEN A NEW CALL IS ROUTED TO A DISPATCHER AND NO OTHER
ACTIVITY IS DISPLAYED IN THE WINDOW USED FOR EVENT
CONTROL, THE NEW CALL SHALL BE DISPLAYED IMMEDIATELY.
3-4.3 (4) IF THE WINDOW USED FOR EVENT CONTROL IS BUSY THE
PROPOSED APPLICATION SHALL PRESENT A VISUAL AND AUDIBLE
ALERT TO NOTIFY THE DISPATCHER OF THE NEW CALL.
3-4.4 RESOURCE RECOMMENDATIONS
3-4.4 (1) THE PROPOSED APPLICATION SHALL RECOMMEND UNITS EACH
TIME A WAITING, PENDING OR ACTIVE EVENT RECORD IS
REVIEWED BY A DISPATCHER.
3-4.4 (2) IT IS PREFERRED THAT THE APPLICATION RECOMMEND UNITS
BASED ON A TABLE WHICH ALLOWS FOR THE RECOMMENDATION
OF AT LEAST TEN UNITS OF THE REQUIRED TYPE FOR EACH CALL
TYPE. FOR EXAMPLE, A COLD BURGLARY CALL WOULD RESULT IN
THE RECOMMENDATION OF ONE PATROL UNIT. A BURGLARY IN
PROGRESS WOULD RESULT IN THE RECOMMENDATION OF TWO
PATROL UNITS AND A K9.
3-4.4 (3) IT IS PREFERRED THAT THE PROPOSED APPLICATION OFFER A
MEANS OF RECOMMENDING UNITS BASED ON CAPABILITIES
City of Fort Collins cxxxii Proposal P-847
REQUIRED TO HANDLE A PARTICULAR CALL TYPE. FOR EXAMPLE,
A TRAFFIC ACCIDENT WITH INJURIES WOULD RESULT IN THE
RECOMMENDATION OF A TRAFFIC UNIT RATHER THAN A PATROL
UNIT.
3-4.4 (3.1) IF THIS CAPABILITY IS INCLUDED THE PROPOSED APPLICATION
SHALL ALLOW THE SYSTEM ADMINISTRATOR OR AUTHORIZED
USER TO DESIGNATE CAPABILITIES FOR EACH UNIT AND THE
CAPABILITIES REQUIRED FOR EACH EVENT TYPE.
3-4.4 (3.2) IF THIS CAPABILITY IS INCLUDED, THE PROPOSED SYSTEM
SHALL ALLOW THE SYSTEM ADMINISTRATOR OR AUTHORIZED
USER TO HAVE THE ABILITY TO ACTIVATE AND DEACTIVATE THE
CAPABILITIES-BASED RECOMMENDATION FEATURE AS NEEDED.
3-4.4 (4) REGARDLESS OF THE RECOMMENDATION ALGORITHM BEING
USED, THE PROPOSED APPLICATION SHALL SEARCH FOR THE
NEAREST RESPONSIBLE UNIT OF THE TYPE OR WITH THE
CAPABILITIES REQUIRED TO HANDLE THE NEW EVENT.
3-4.4 (5) AS AN OPTION, THE PROPOSED APPLICATION SHALL HAVE THE
ABILITY TO UTILIZE AVL REPORTED LOCATION TO RECOMMEND
THE NEAREST AVAILABLE RESOURCE WITH THE PROPER
CAPABILITIES.
3-4.4 (6) IT IS PREFERRED THAT THE PROPOSED APPLICATION HAVE THE
ABILITY TO RECOMMEND DIFFERENT RESOURCES BASED ON A
STREET DIRECTION. FOR EXAMPLE, NORTHBOUND I-70 WILL
RECEIVE A DIFFERENT RECOMMENDATION THAN SOUTHBOUND I-
70 IN THE SAME LOCATION.
3-4.4 (7) IT IS PREFERRED THAT THE PROPOSED APPLICATION HAVE THE
ABILITY TO RECOMMEND DIFFERENT RESOURCES FOR EVENTS
OCCURRING ON THE STREET AS OPPOSED TO AT AN ADDRESS ON
THAT SAME STREET. FOR EXAMPLE, SOME STREETS IN THE CITY
ARE THE RESPONSIBILITY OF THE STATE, WHILE HOUSES LOCATED
ON THOSE STREETS ARE THE CITY’S JURISDICTION (VENDOR MUST
ATTACH AN EXPLANATION AS TO HOW THEY WOULD ACCOMPLISH
THIS).
3-4.4 (8) THE PROPOSED APPLICATION SHALL PROVIDE A MEANS OF
RECOMMENDING SPECIAL RESOURCES. SPECIAL RESOURCES
SHALL INCLUDE EITHER SPECIAL EMPLOYEE SKILLS (LANGUAGES,
ETC.), OR RESOURCES WHICH ARE NOT NORMALLY CONTROLLED
BY CAD (MOBILE COMMAND POST, ETC.)
City of Fort Collins cxxxiii Proposal P-847
3-4.4 (9) THE PROPOSED APPLICATION SHALL ALLOW THE DISPATCHER TO
SELECT AND ASSIGN RECOMMENDED UNITS USING THE
FOLLOWING METHODS:
3-4.4 (9.1) COMMAND LINE ENTRY,
3-4.4 (9.2) FUNCTION KEY,
3-4.4 (9.3) CHECK BOX,
3-4.4 (9.4) POINTING DEVICE,
3-4.4 (9.5) OR FROM A FORM.
3-4.4 (10) THE PROPOSED APPLICATION SHALL ASSUME THAT THE FIRST
UNIT ASSIGNED TO A CALL IS THE PRIMARY UNIT.
3-4.4 (11) THE PROPOSED APPLICATION SHALL ALLOW ANY USER TO
CHANGE THE PRIMARY UNIT DESIGNATION FOR A GIVEN EVENT AT
ANY TIME.
3-4.5 HAZARD AND PREMISE FILES
3-4.5 (1) THE PROPOSED CAD APPLICATION SHALL ALLOW ALL USERS TO
CREATE HAZARD RECORDS FOR ANY PHYSICAL LOCATION.
3-4.5 (2) THE CAD SYSTEM SHALL ALLOW HAZARD RECORDS TO BE
ASSOCIATED WITH A SPECIFIC ADDRESS (INCLUDING APARTMENT
NUMBER OR TRAILER LOT NUMBER), BLOCK RANGE, RADIUS OR
COMMONPLACE.
3-4.5 (3) THE PROPOSED APPLICATION SHALL ALLOW THE USER TO
CATEGORIZE EACH HAZARD RECORD PRIOR TO ACCEPTING THE
RECORD. FOR EXAMPLE, HAZARD RECORDS COULD BE
CATEGORIZED AS GUN PERMITS, DANGEROUS PERSONS, ETC.
3-4.5 (4) THE PROPOSED APPLICATION SHALL ADD A DATE/TIME/USER
STAMP TO THE AUDIT TRAIL ONCE THE DISPATCHER HAS
ACCESSED THE HAZARD/PREMISE DETAILS.
3-4.5 (5) THE PROPOSED APPLICATION SHALL ALLOW AT LEAST 1000
CHARACTERS WORTH OF DATA TO BE ENTERED IN THE TEXT FIELD
OF THE HAZARD/PREMISE FORM.
3-4.5 (6) THE PROPOSED APPLICATION SHALL ALLOW THE SYSTEM
ADMINISTRATOR OR AUTHORIZED USER TO CREATE AND NAME
HAZARD RECORD CATEGORIES AS NEEDED. EXAMPLES INCLUDE:
City of Fort Collins cxxxiv Proposal P-847
3-4.5 (6.1) FIREARMS STORED ON SITE,
3-4.5 (6.2) PREMISE OWNER AND CONTACT INFORMATION,
3-4.5 (6.3) ACCESS TO FLOOR PLANS,
3-4.5 (6.4) SPECIAL PERMITS (GUN, HAZMAT, ALARM, ETC.),
3-4.5 (6.5) DANGEROUS SITUATIONS (COMBATIVE PERSONS, GUARD DOGS,
EXPLOSIVES, ETC.)
3-4.5 (6.6) PERSONS WITH MEDICAL CONDITIONS
3-4.5 (6.7) KNOX BOX, ALARM PANEL, AND STANDPIPE LOCATIONS
3-4.5 (7) THE CAD APPLICATION SHALL SORT HAZARD RECORDS
ACCORDING TO THEIR CATEGORIZATION WHEN THEY ARE
DISPLAYED AS A RESULT OF AN ADDRESS VERIFICATION.
3-4.5 (8) THE PROPOSED APPLICATION SHALL PUSH ALL HAZARD/PREMISE
INFORMATION OUT TO ALL MDC’S SO RESPONDING UNITS CAN
READ THE DETAILS OF THE ENTRY BEFORE ARRIVAL.
3-4.5 (9) THE PROPOSED APPLICATION SHALL DISPLAY BOTH VISUAL AND
AUDIBLE ALERTS AT BOTH THE DISPATCH TERMINAL AND MDC’S
NOTIFYING USER OF PREMISE/HAZARD AT THAT LOCATION.
3-4.5 (10) HAZARD/PREMISE DETAILS SHALL NOT BE DISPLAYED UNTIL USER
ELECTS TO SEE IT.
3-4.5 (11) DETAILS SHALL BE RETRIEVABLE UTILIZING ONLY ONE
KEYSTROKE COMBINATION.
3-4.5 (12) HAZARD AND PREMISE HITS SHALL BE DISPLAYED SEPARATELY
3-4.5 (13) ALL USERS SHALL HAVE THE ABILITY TO DISABLE THE AUDIBLE
ALERT.
3-4.5 (14) THE CAD APPLICATION SHALL INCLUDE AN EXPIRATION DATE
FIELD FOR EACH HAZARD RECORD.
3-4.5 (15) IT SHALL BE POSSIBLE TO ENTER A HAZARD RECORD WHICH DOES
NOT EXPIRE.
3-4.5 (16) THE PROPOSED CAD APPLICATION SHALL AUTOMATICALLY
CREATE PREMISE RECORDS EACH TIME A CALL FOR SERVICE IS
RECEIVED FROM A PHYSICAL LOCATION.
City of Fort Collins cxxxv Proposal P-847
3-4.5 (17) AT A MINIMUM A PREMISE RECORD SHALL CONTAIN THE INCIDENT
NUMBER, DATE, TIME, THE NATURE AND DISPOSITION OF EACH
CALL AND THE UNIT(S) THAT HANDLED THE CALL.
3-4.5 (18) THE CAD APPLICATION SHALL ALLOW THE OPERATOR TO EASILY
SELECT AND VIEW THE ORIGINAL CALL RECORD FROM THE
PREMISE RECORD SUMMARY.
3-4.5 (19) THE PROPOSED CAD APPLICATION SHALL VISUALLY ALERT THE
USER TO THE EXISTENCE OF HAZARD OR PREMISE RECORDS FOR A
GIVEN ADDRESS IMMEDIATELY UPON ADDRESS VERIFICATION.
3-4.5 (20) THE PROPOSED CAD APPLICATION SHALL ALLOW A USER TO
SEARCH FOR HAZARD OR PREMISE RECORDS FOR A GIVEN
ADDRESS.
3-4.5 (21) THE PREMISE FILE SHALL RETAIN NOT LESS THAN THE 20
PREVIOUS EVENTS FOR A GIVEN ADDRESS.
3-4.5 (22) BEYOND THE TWENTY REQUIRED RECORDS NO PREMISE HISTORY
RECORDS SHALL DISPLAY TO THE OPERATOR WHEN PROCESSING A
CALL FOR SERVICE.
3-4.5 (23) THE SYSTEM ADMINISTRATOR OR AUTHORIZED USER SHALL BE
ABLE TO DEFINE WHICH AGENCY PREMISE INFORMATION IS
VIEWABLE BY WHICH USERS. I.E. FIRE DEPARTMENT USERS ARE
ONLY ABLE TO VIEW FIRE DEPARTMENT PREMISE INFORMATION
ETC.
3-4.5 (24) AT A MINIMUM THE PROPOSED APPLICATION SHALL DISPLAY A
SUMMARY OF PREMISE RECORDS FOUND AND THEN ALLOW THE
USER TO DRILL-DOWN INTO THE DETAIL OF THE RECORD AS
NEEDED.
3-4.5 (25) THE PROPOSED APPLICATION SHALL ALSO CONDUCT A CHECK FOR
HAZARD RECORDS IN A USER DEFINED AREA AROUND THE NEW
EVENT AND FOR EXACT ADDRESSES.
3-4.5 (25.1) IF THIS FUNCTION IS PROVIDED THE RANGE OF THE AREA TO BE
CHECKED FOR PREMISE RECORDS SHALL BE USER DEFINABLE
FOR EACH CATEGORY OF HAZARD RECORDS (E.G. GUN PERMIT,
DANGEROUS PERSON, ETC.).
3-4.5 (26) THE PROPOSED APPLICATION SHALL NOT SEARCH FOR HAZARD
AND PREMISE RECORDS EACH TIME THE LOCATION OF A UNIT
ASSIGNED TO A CALL IS CHANGED.
City of Fort Collins cxxxvi Proposal P-847
3-4.5 (27) THE PROPOSED APPLICATION SHALL OFFER A SIMPLE METHOD
FOR THE SYSTEM ADMINISTRATOR OR AUTHORIZED USER TO
MODIFY OR DELETE HAZARD AND PREMISE RECORDS.
3-4.5 (28) IN THE EVENT THAT HAZARD RECORDS ARE LOCATED DURING A
SEARCH THE PROPOSED APPLICATION SHALL:
3-4.5 (28.1) INDICATE IN A NON-INTRUSIVE FASHION THE TYPE(S) OF
RECORD(S) (GUN, DANGEROUS PERSON, ETC.) THAT WERE
FOUND,
3-4.5 (28.2) AND DIFFERENTIATE BETWEEN RECORDS WHICH RELATE TO
THE EXACT ADDRESS OF THE NEW EVENT AND THOSE WHICH
FALL WITHIN THE USER-DEFINED SEARCH AREA.
3-4.6 EVENT AND CASE (REPORT) NUMBERING
3-4.6 (1) WHENEVER A CALL FOR SERVICE OR OFFICER-INITIATED EVENT IS
ENTERED INTO THE CAD SYSTEM A NEW INCIDENT NUMBER SHALL
BE ASSIGNED.
3-4.6 (2) THE PROPOSED APPLICATION SHALL ALLOW THE MANUAL
ADDITION OF CASE (REPORT) NUMBERS AS NEEDED. CASE
(REPORT) NUMBERS SHALL ONLY BE ISSUED WHEN AN INCIDENT
NUMBER IS PRESENT.
3-4.6 (2.1) CASE (REPORT) NUMBERS SHALL BE LINKED TO INCIDENT
NUMBERS AT ALL TIMES.
3-4.6 (3) THE PROPOSED APPLICATION SHALL ALLOW THE ADDITION OF
CASE (REPORT) NUMBERS TO INCIDENTS WHETHER THAT
INCIDENT IS PENDING, ACTIVE OR CLOSED WITHOUT HAVING TO
RE-OPEN THAT INCIDENT.
3-4.6 (4) IF THE PROPOSED APPLICATION ALLOWS THE ISSUANCE OF
MULTIPLE CASE (REPORT) NUMBERS PER INCIDENT, IT MUST ALSO
ALLOW THE AGENCY TO LOCK THIS FEATURE OUT SO MULTIPLE
CASE (REPORT) NUMBERS ARE NOT ALLOWED.
3-4.6 (5) THE PROPOSED APPLICATION SHALL ALLOW THE USER TO
CONFIGURE THE SYSTEM TO ASSIGN CASE (REPORT) NUMBERS
AUTOMATICALLY ON A PER-AGENCY/JURISDICTION BASIS.
3-4.6 (6) CAD INCIDENT NUMBERS SHALL CONFORM TO THE FOLLOWING
FORMAT (AA)(YY)(NNNNNN), WHERE (AA) IS A TWO LETTER CODE
FOR THE AGENCY OF JURISDICTION, WHERE (YY) IS THE LAST TWO
DIGITS OF THE CURRENT YEAR, AND (NNNNNN) IS A SIX DIGIT
City of Fort Collins cxxxvii Proposal P-847
SEQUENTIAL NUMBER UNIQUE TO EACH AGENCY THAT STARTS
OVER EACH YEAR.
3-4.6 (7) CASE (REPORT) NUMBERS SHALL CONFORM TO THE FOLLOWING
FORMAT (YY)(AA)(NNNNNN) WHERE (YY) IS THE LAST TWO DIGITS
OF THE CURRENT YEAR, (AA) IS A TWO LETTER CODE FOR THE
REPORTING AGENCY, AND (NNNNNN) IS A SIX DIGIT SEQUENTIAL
NUMBER UNIQUE TO EACH AGENCY THAT STARTS OVER EACH
YEAR.
3-4.6 (8) THE PROPOSED APPLICATION SHALL ALLOW THE USE OF
ABBREVIATED INCIDENT NUMBERS (NO MORE THAN 5 TOTAL
CHARACTERS) TO LESSEN THE NUMBER OF KEYSTROKES
NECESSARY TO RECALL, MODIFY, CANCEL OR CLOSE AN INCIDENT.
3-5 DISPATCH FUNCTIONS
3-5.1 GENERAL REQUIREMENTS
3-5.1 (1) DISPATCHERS SHALL HAVE ACCESS TO ALL CALL TAKER
FUNCTIONS PLUS THE FOLLOWING SPECIFIC FEATURES AND
FUNCTIONS.
3-5.1 (2) AT A MINIMUM THE PROPOSED APPLICATION SHALL ALLOW
DISPATCHERS TO CHOOSE WHICH PATROL OR FIRE DISTRICTS
THEY ARE CONTROLLING WHEN THEY SIGN ON.
3-5.1 (3) THE PROPOSED SYSTEM SHALL ALSO ALLOW THE USE OF A
DEFAULT SET OF PATROL OR FIRE DISTRICTS TO SIMPLIFY LOG-
ON’S AT SPECIFIC CONSOLES. THE DEFAULT SHALL BE
DETERMINED AND EASILY CHANGED BY THE SYSTEM
ADMINISTRATOR OR AUTHORIZED USER.
3-5.1 (4) IT IS PREFERRED THAT THE SYSTEM ALLOW DISPATCHERS TO
SPECIFY WHETHER THEY ARE CONTROLLING A DISTRICT FOR
WHICH THEY ARE SIGNED ON, OR MERELY MONITORING THE
DISTRICT.
3-5.1 (5) THE PROPOSED APPLICATION SHALL HAVE THE ABILITY TO
TRANSFER ALTERNATE DISTRICTS AND BEATS/RESPONSE AREAS
FROM THE TEST SYSTEM TO THE LIVE SYSTEM.
3-5.1 (6) IT IS PREFERRED THAT THE SYSTEM ALLOW THE USER TO SPECIFY
WHICH OTHER UNITS THEY WISH TO CONTROL OR MONITOR
WHEN THEY SIGN ON.
3-5.1 (7) THE PROPOSED APPLICATION SHALL ALLOW THE USER AGENCY
TO FACILITATE CHANGES IN RESOURCE DEPLOYMENT AND CAD
City of Fort Collins cxxxviii Proposal P-847
CONTROL THROUGH THE CREATION, RETRIEVAL AND
MANIPULATION OF RESOURCE DEPLOYMENT PLANS.
3-5.1 (8) THE PROPOSED APPLICATION SHALL INCLUDE A COMMAND FOR
RETRIEVING AND LOADING A NEW DEPLOYMENT PLAN.
3-5.1 (9) THE LOADING OF A NEW DEPLOYMENT PLAN SHALL NOT REQUIRE
THE PROPOSED APPLICATION TO BE STOPPED OR MADE QUIET.
3-5.1 (10) THE PROPOSED APPLICATION SHALL INCLUDE STATUS TIMERS FOR
EACH EVENT AND UNIT STATUS.
3-5.1 (11) THE PROPOSED APPLICATION SHALL OFFER USER-DEFINED STATUS
TIMERS FOR EVENTS AND UNIT STATUSES BASED UPON INCIDENT
TYPE.
3-5.1 (12) WHEN A STATUS TIMER EXPIRES THE OPERATOR SHALL BE
NOTIFIED BY MEANS OF A DISTINCTIVE CHANGE IN THE STATUS
DISPLAY
3-5.1 (13) WHEN A STATUS TIMER EXPIRES USERS SHALL HAVE TWO OPTIONS
FOR RESETTING THE TIMER.
3-5.1 (13.1) THE DISPATCHER MAY RESET THE STATUS TIMER TO THE
DEFAULT VALUE.
3-5.1 (13.2) THE DISPATCHER MAY RESET THE TIMER WITH A NEW TIME
VALUE. THE MANUAL TIMER VALUE FIELD SHALL SUPPORT AT
LEAST THREE DIGITS.
3-5.1 (14) THE PROPOSED APPLICATION SHALL PROVIDE A MEANS FOR ONE
WORKSTATION TO TRANSFER ITS ENTIRE WORKLOAD TO
ANOTHER SIGNED ON WORKSTATION.
3-5.1 (15) THE PROPOSED APPLICATION SHALL PROVIDE AN EASY MEANS
FOR THE TRANSFERRING WORKSTATION TO RECOVER ITS
WORKLOAD AT A LATER TIME WITHOUT SIGNING OFF.
3-5.1 (16) UPON DISPATCH, THE APPLICATION SHALL AUTOMATICALLY
ASSIGN THE RECOMMENDED OR REQUESTED UNITS, REMOVE THE
EVENT FROM THE PENDING QUEUE, UPDATE THE STATUS DISPLAY,
SEND THE EVENT TO THE ASSIGNED UNITS’ MDC’S, START THE
STATUS TIMERS, AND UPDATE THE AUDIT TRAIL.
3-5.1 (17) AFTER INITIAL DISPATCH, THE SYSTEM SHALL ALLOW THE
ADDITION OF UNITS TO AN INCIDENT FROM THE COMMAND LINE,
FROM A POINTING DEVICE (DRAG N DROP DISPATCHING) AND
FROM A FORM.
City of Fort Collins cxxxix Proposal P-847
3-5.1 (18) IT IS PREFERRED THAT THE PROPOSED APPLICATION HAVE THE
CAPABILITY TO PLACE ALL UNITS IN A PREVIOUSLY DEFINED
ROSTER ON OR OFF DUTY WITH A SINGLE COMMAND.
3-5.1 (18.1) IT IS PREFERRED THAT THE PROPOSED APPLICATION ALLOW
FOR SINGLE UNIT EXCEPTIONS WHEN PLACING A ROSTER ON OR
OFF DUTY.
3-5.1 (19) UNITS IN A ROSTER THAT IS PLACED “ON-DUTY” SHALL NOT BE
AVAILABLE OR RECOMMENDED FOR CALLS UNTIL THEY NOTIFY
THE DISPATCHER THAT THEY ARE IN SERVICE.
3-5.1 (20) THE PROPOSED SYSTEM SHALL MAINTAIN A LOG FOR TRACKING
IMPOUNDED AND TOWED VEHICLES. THIS FUNCTIONALITY MAY
EXIST AS A PART OF THE CAD APPLICATION OR AS A MODULE OF
THE RMS/JMS, SO LONG AS IT IS ACCESSIBLE TO ALL CAD/RMS/JMS
USERS.
3-5.1 (20.1) THE TOW/IMPOUND RECORD SHALL INCLUDE THE CCIC RTY
FIELD, VEHICLE LICENSE PLATE NUMBER, STATE OF
REGISTRATION, YEAR OF EXPIRATION, VEHICLE MAKE AND
BODY STYLE, COLOR, YEAR, VIN NUMBER, LOCATION WHICH
THE VEHICLE WAS TOWED FROM, TIME AND DATE, TOW
COMPANY NAME AND PHONE NUMBER.
3-5.1 (20.2) THE TOW/IMPOUND ENTRY FORM SHALL CONFORM TO
CCIC/NCIC STANDARDS AND UPON ENTRY, THE SYSTEM SHALL
AUTOMATICALLY RUN THE VEHICLE FOR WANTS/WARRANTS.
3-5.1 (20.3) UPON ENTRY OF A TOWED/IMPOUNDED VEHICLE INTO THE CAD
SYSTEM, THE APPLICATION SHALL GIVE THE USER THE OPTION
OF AUTOMATICALLY ENTERING THE VEHICLE AS
TOWED/IMPOUNDED/STOLEN ETC INTO CCIC/NCIC. ALL CIC AND
NIC NUMBERS SHALL BE AUTOMATICALLY ADDED TO THE AUDIT
TRAIL.
3-5.1 (20.4) THE PROPOSED APPLICATION SHALL ALLOW FOR SEARCHES
FROM ALL FIELDS IN THE TOW/IMPOUND ENTRY.
3-5.1 (20.5) ALL MODIFICATIONS OR CANCELS OF A TOW/IMPOUND ENTRY
SHALL AUTOMATICALLY UPDATE OR CANCEL THE CCIC/NCIC
ENTRY IF APPLICABLE.
3-5.1 (20.6) THE PROPOSED APPLICATION SHALL CHECK THE TOWED AND
REPOSSESSED VEHICLES FILE FOR POTENTIAL MATCHES WHEN
A STOLEN AUTO EVENT IS ENTERED.
City of Fort Collins cxl Proposal P-847
3-5.1 (20.7) THE PROPOSED APPLICATION SHALL OFFER A MEANS OF
ADDING COMMENTS TO AN EXISTING EVENT RECORD FROM THE
COMMAND LINE WITHOUT RETRIEVING THE EVENT.
3-5.1 (20.8) THE PROPOSED APPLICATION SHALL OFFER A MEANS OF
ADDING COMMENTS TO A UNIT’S HISTORY FROM THE COMMAND
LINE.
3-5.1 (20.9) THE PROPOSED APPLICATION SHALL ALLOW THE USER TO
ENTER COMMENTS CONTINUOUSLY TO ANY EVENT OR UNIT
RECORD, DATE/TIME/UNIT STAMPING EACH COMMENT AS IT IS
ENTERED AND NOT EXITING THE FUNCTION UNTIL ANOTHER
COMMAND IS INVOKED.
3-5.1 (20.10) THE APPLICATION SHALL ALLOW AT LEAST 1000 CHARACTERS
BE ENTERED PER COMMENT.
3-5.1 (21) IT IS PREFERRED THAT THE PROPOSED APPLICATION OFFER A CAR
CHASE FUNCTION WHEREBY:
3-5.1 (21.1) THE USER CAN QUICKLY ENTER THE UNIT NUMBER AND
LOCATION AND THE SYSTEM WILL PUT THAT UNIT IN PURSUIT
STATUS,
3-5.1 (21.2) FOLLOWING THE USE OF THIS COMMAND THE USER WILL BE
ABLE TO ADD COMMENTS CONTINUOUSLY TO THE RECORD
WITHOUT ENTERING ANOTHER COMMAND OR RETRIEVING THE
EVENT,
3-5.1 (21.3) AND A MEANS OF DATE/TIME/UNIT STAMPING EACH COMMENT
SHALL BE PROVIDED AND SHALL BE RECORDED INTO THE
INCIDENT AUDIT TRAIL.
3-5.2 EVENT CONTROL FUNCTIONS
3-5.2 (1) WHEN A DISPATCHER REVIEWS A PENDING EVENT AND RETURNS IT
TO THE PENDING QUEUE WITHOUT ACTION THE CALL STATUS
SHALL CHANGE. FOR EXAMPLE, ONCE A NEW CALL IS REVIEWED
IT WILL CHANGE FROM “WAITING/NEW” TO “PENDING”.
3-5.2 (2) THE PROPOSED APPLICATION SHALL PROVIDE A SINGLE KEY OR
SINGLE KEYSTROKE COMBINATION COMMAND FOR RETRIEVING
THE HIGHEST PRIORITY, OLDEST EVENT FROM THE PENDING
EVENTS QUEUE FOR REVIEW AND DISPATCH.
3-5.2 (3) THE PROPOSED APPLICATION SHALL ALSO PROVIDE A COMMAND
OR FUNCTION KEY FOR REVIEWING EACH PENDING EVENT
SEQUENTIALLY.
City of Fort Collins cxli Proposal P-847
3-5.2 (4) THE PROPOSED APPLICATION SHALL ALLOW THE DISPATCHER TO
INTERRUPT ONE TRANSACTION TO HANDLE ANOTHER OF HIGHER
PRIORITY WITHOUT LOSING INFORMATION ENTERED ON THE
FIRST.
3-5.2 (5) WHEN THE PROPOSED APPLICATION RECOMMENDS UNITS FOR
DISPATCH THE DISPATCHER SHALL HAVE THE FOLLOWING
OPTIONS FOR COMPLETING THE DISPATCH:
3-5.2 (5.1) PRESS A SINGLE KEY TO ACCEPT THE PROPOSED APPLICATION
RECOMMENDED UNITS,
3-5.2 (5.2) SELECT INDIVIDUAL UNITS FROM THE RECOMMENDED UNITS
FOR DISPATCH, THEN DISPATCH,
3-5.2 (5.3) OR SELECT UNITS NOT RECOMMENDED BY THE PROPOSED
APPLICATION FOR DISPATCH, THEN DISPATCH.
3-5.2 (6) DISPATCHERS AND MOBILE UNITS SHALL BE ABLE TO CREATE
SELF-INITIATED EVENTS. WHEN INVOKED THE DISPATCHER SHALL
PROVIDE THE UNIT NUMBER, LOCATION AND EVENT TYPE. THE
PROPOSED APPLICATION SHALL RESPOND BY CREATING A NEW
EVENT AT THAT LOCATION AND PLACING THE SPECIFIED UNIT IN
AN “ARRIVED” STATUS.
3-5.2 (7) THE PROPOSED APPLICATION SHALL HAVE THE ABILITY TO
DISTINGUISH BETWEEN SELF-INITIATED EVENTS, AND CALLS
TAKEN VIA PHONE OR WALK-IN SO AS TO BE ABLE TO REPORT ON
SELF-INITIATED ACTIVITY (“SOURCE OF ORIGIN”)
3-5.2 (8) THE PROPOSED APPLICATION SHALL ALLOW ALL CALL-TYPES TO
BE UTILIZED AS FIELD INITIATED CONTACTS.
3-5.2 (9) IF THE FIELD INITIATED CONTACT CONTAINS A LICENSE PLATE,
THE APPLICATION SHALL AUTOMATICALLY CHECK THE
FOLLOWING WITHOUT FURTHER INPUT FROM THE DISPATCHER OR
OFFICER IF INITIATED FROM AN MDC:
3-5.2 (9.1) CHECK LICENSE PLATE FOR WANTS/WARRANTS,
3-5.2 (9.2) LIST DMV INFORMATION ON PLATE,
3-5.2 (9.3) SEARCH FOR THE REGISTERED OWNER OF THE VEHICLE,
3-5.2 (9.4) CHECK THE RO FOR WANTS/WARRANTS,
3-5.2 (9.5) LIST THE REGISTERED OWNER’S DRIVER’S LICENSE
INFORMATION,
City of Fort Collins cxlii Proposal P-847
3-5.2 (9.6) AND QUERY RMS FOR ANY PAST CONTACTS WITH THAT PLATE.
3-5.2 (10) THE PROPOSED APPLICATION SHALL HAVE THE ABILITY TO BYPASS
ADDRESS VERIFICATION ON A PER INCIDENT BASIS ON ALL FIELD
INITIATED CONTACTS.
3-5.2 (11) THE SYSTEM ADMINISTRATOR OR AUTHORIZED USER SHALL HAVE
THE ABILITY TO CONFIGURE THE PROPOSED APPLICATION TO
REQUIRE ADDRESS VERIFICATION ON SELF-INITIATED EVENTS
BEFORE THAT EVENT IS CLOSED.
3-5.2 (12) IT IS PREFERRED THAT THE PROPOSED APPLICATION SHALL
ALLOW DISPATCHERS TO TRANSFER SELECTED EVENTS TO
ANOTHER DISPATCHER WHEN NECESSARY.
3-5.2 (13) IT IS PREFERRED THAT THE APPLICATION ALSO ALLOW THE
DISPATCHER TO SPECIFY WHICH EVENT THE DISPATCHER WILL
RETAIN, AND THE APPLICATION WILL TRANSFER ALL OTHER
EVENTS TO A DESIGNATED USER.
3-5.2 (14) DISPATCHERS SHALL HAVE THE ABILITY TO SEND A COPY OF AN
EVENT TO A WORKSTATION OTHER THAN THE PROPOSED
APPLICATION DETERMINED DESTINATION. FOR EXAMPLE, IF AN
EVENT OCCURS ON THE BOUNDARY BETWEEN TWO POLICE
ZONES/JURISDICTION THE DISPATCHER SHALL BE ABLE TO SEND A
“COPY” OF THE EVENT TO THE NEIGHBORING ZONE.
3-5.2 (15) THE PROPOSED APPLICATION SHALL HAVE A MEANS OF ASSIGNING
ONE CASE (REPORT) NUMBER TO MULTIPLE EVENT NUMBERS AND
LOGICALLY LINKING THOSE EVENTS TOGETHER.
3-5.2 (16) THE DISPATCHER SHALL BE ABLE TO ASSIGN MORE THAN ONE
EVENT TO A GIVEN UNIT OR RESOURCE (CALL STACKING) FROM
THE COMMAND LINE.
3-5.2 (17) THE DISPATCHER SHALL BE ABLE TO “UN-STACK” A CALL STACKED
AGAINST AN OFFICER FROM THE COMMAND LINE.
3-5.2 (18) THE SYSTEM ADMINISTRATOR OR AUTHORIZED USER SHALL HAVE
THE ABILITY TO SET QUEUE LIMITS FOR BOTH NUMBERS OF
EVENTS ALLOWED TO BE STACKED IN A GIVEN QUEUE AND THE
TIME AN EVENT REMAINS IN QUEUE FOR EACH PRIORITY LEVEL.
3-5.2 (19) IF THE TIMER FOR AN EVENT IN QUEUE EXPIRES THE PROPOSED
APPLICATION SHALL NOTIFY THE DISPATCHER.
3-5.2 (20) THE PROPOSED APPLICATION SHALL PROVIDE A COMMAND WHICH
ALLOWS A DISPATCHER TO CANCEL AN EVENT.
City of Fort Collins cxliii Proposal P-847
3-5.2 (20.1) THE COMMAND SHALL REQUIRE THE USER TO ENTER A REASON
FOR CANCELLATION PRIOR TO EXECUTING.
3-5.2 (20.2) UPON EXECUTION THE COMMAND WILL AUTOMATICALLY
REMOVE THE EVENT FROM THE PENDING OR ACTIVE EVENTS
QUEUE AND ADD A CANCELLATION DISPOSITION
AUTOMATICALLY TO THE EVENT COMMENTS.
3-5.2 (21) IF AN EVENT HAS BEEN DISPATCHED ALL UNITS MUST BE CLEARED
FROM THE INCIDENT PRIOR TO INVOKING THE CANCEL COMMAND.
3-5.2 (22) THE PROPOSED APPLICATION SHALL PROVIDE A COMMAND FOR
RE-OPENING OR RE-ACTIVATING AN EVENT WHICH HAS
PREVIOUSLY BEEN CLOSED USING A SIMPLE CODE AND INCIDENT
OR CASE (REPORT) NUMBER FROM THE COMMAND LINE.
3-5.2 (22.1) IF AN EVENT IS RE-OPENED THE PROPOSED APPLICATION SHALL
RECORD THE RE-OPENING COMMAND IN THE ORIGINAL EVENT
AUDIT TRAIL AND CONTINUE RECORDING ACTIONS TO THE
ORIGINAL AUDIT TRAIL.
3-5.2 (22.2) THE PROPOSED APPLICATION SHALL SUM ALL TIME SPENT ON
ANY GIVEN INCIDENT NO MATTER HOW MANY TIMES IT WAS RE-
OPENED TO ACCURATELY TRACK TIME SPENT ON INCIDENTS.
3-5.2 (23) THE PROPOSED APPLICATION SHALL ALLOW A WORKSTATION (NO
MDC’S) TO SELECT AN EVENT FOR CONTINUOUS MONITORING.
SUCH EVENTS WILL APPEAR IN A SEPARATE WINDOW, IN REAL
TIME AND ALL EVENT OR UNIT ACTIVITY, REGARDLESS OF THEIR
POINT OF ENTRY, WILL BE DISPLAYED IN THIS WINDOW AS THEY
ARE RECORDED TO THE CAD DATABASE.
3-5.2 (24) IF THE PROPOSED APPLICATION ALLOWS FOR OFFICERS TO
DISPATCH THEMSELVES ONTO INCIDENTS, THE SYSTEM
ADMINISTRATOR OR AUTHORIZED USER MUST BE ABLE TO
DISABLE THIS FUNCTION.
3-5.2 (25) THE PROPOSED APPLICATION SHALL INCLUDE AN OPTION TO
DISPLAY THE DISPATCH SCREEN WITH UNIT RECOMMENDATIONS
IMMEDIATELY AFTER A CALL HAS BEEN ENTERED. THIS WOULD
ALLOW FOR DISPATCHERS TO TAKE A CALL AND MOVE
IMMEDIATELY TO THE DISPATCH FUNCTION.
3-5.2 (26) THE PROPOSED APPLICATION SHALL INCLUDE A FUNCTION WHICH
ALLOWS TWO OR MORE EVENTS TO BE CROSS-REFERENCED. THE
RESULT OF A CROSS-REFERENCE COMMAND WILL BE TO INDICATE
THAT THE EVENT IS CROSS-REFERENCED TO ANOTHER EVENT
WHENEVER EITHER OF THE EVENTS ARE DISPLAYED.
City of Fort Collins cxliv Proposal P-847
3-5.2 (27) INCIDENTS FROM ANY JURISDICTION/COMMUNITY SHALL BE ABLE
TO BE CROSS-REFERENCED TO ONE ANOTHER.
3-5.3 UNIT CONTROL FUNCTIONS
3-5.3 (1) IT IS PREFERRED THAT THE PROPOSED APPLICATION SHALL
PROVIDE A MEANS FOR PLACING UNITS EITHER ON OR OFF-DUTY
EITHER INDIVIDUALLY OR AS A GROUP TO FACILITATE SHIFT
CHANGES.
3-5.3 (2) THE PROPOSED APPLICATION SHALL SHOW UNITS PLACED ON
DUTY AS AVAILABLE AND THEY SHALL BE AVAILABLE FOR CALLS.
3-5.3 (3) THE PROPOSED APPLICATION SHALL HAVE NO LIMITATIONS ON
THE NUMBER OF UNITS WHICH CAN BE ASSIGNED TO A GIVEN
EVENT, AND THE TIMES FOR EACH UNIT WILL BE TRACKED
SEPARATELY.
3-5.3 (4) IT IS PREFERRED THAT THE PROPOSED APPLICATION PROVIDE
SUPPORT FOR THE ASSIGNMENT OF A CALL FOR SERVICE TO ONE
OR MORE UNITS, OR THE ASSIGNMENT OF ONE OR MORE UNITS TO
AN EVENT BY “DRAGGING AND DROPPING” ONE ON TOP OF THE
OTHER.
3-5.3 (5) IF THE SYSTEM PROVIDES FOR DRAG AND DROP DISPATCHING, THE
SYSTEM SHALL HIGHLIGHT THE INCIDENT IN QUESTION WHEN
THE CURSOR/UNIT IS HOVERING ABOVE IT. THIS IS TO ENSURE THE
CORRECT UNIT IS DISPATCHED ONTO THE CORRECT CALL WHILE
THE SCREEN IS DYNAMICALLY REFRESHING.
3-5.3 (6) THE PROPOSED APPLICATION SHALL HAVE THE ABILITY TO
ASSOCIATE PERSONNEL WITH A PATROL OR OTHER MOBILE UNIT.
3-5.3 (7) THE PROPOSED APPLICATION SHALL PROVIDE A METHOD FOR
ADDING AN OFFICER TO OR REMOVING AN OFFICER FROM A UNIT
AT ANY TIME.
3-5.3 (8) THE PROPOSED APPLICATION SHALL HAVE THE ABILITY TO TRACK
THE ACTIVITY OF EACH OFFICER ASSOCIATED WITH A MOBILE
UNIT.
3-5.3 (9) THE PROPOSED APPLICATION SHALL ALLOW THE DISPATCHER TO
ASSIGN PRIMARY ZONE RESPONSIBILITY FOR PATROL/FIRE UNITS.
3-5.3 (10) THE PROPOSED APPLICATION SHALL ALLOW THE DISPATCHER OR
UNIT TO CHANGE PRIMARY ZONE OF RESPONSIBILITY EASILY
FROM THE COMMAND LINE.
City of Fort Collins cxlv Proposal P-847
3-5.3 (11) THE PROPOSED APPLICATION SHALL SUPPORT THE CAPABILITY TO
DISPATCH RESOURCES OTHER THEN PATROL UNITS, E.G. CRIME
SCENE TECHNICIANS, INVESTIGATORS, ETC WITHOUT FIRST
HAVING TO LOG THE UNIT ON-DUTY. “TEMPORARY UNITS”.
3-5.3 (12) THE RECORDED EVENT ADDRESS SHALL NOT BE AFFECTED BY A
CHANGE IN THE UNIT LOCATION.
3-5.3 (13) THE PROPOSED APPLICATION SHALL DISPLAY BOTH INCIDENT
ADDRESS AND OFFICER LOCATION ON THE STATUS MONITOR.
3-5.3 (14) THE PROPOSED APPLICATION SHALL PERMIT THE USER TO
QUICKLY DETERMINE THE LAST KNOWN LOCATION FOR A GIVEN
UNIT.
3-5.3 (15) THE PROPOSED APPLICATION SHALL PROVIDE A COMMAND WHICH
WILL ALLOW THE DISPATCHER TO PREEMPT ONE ASSIGNMENT
WITH ANOTHER ASSIGNMENT.
3-5.3 (15.1) THE PROPOSED APPLICATION SHALL ALSO PROVIDE FOR
AUTOMATIC PRE-EMPTING OF UNITS FROM AN INCIDENT IF A
NEW ASSIGNMENT, INCLUDING FIELD INITIATED CONTACTS, ARE
ASSIGNED WITHOUT USING THE ABOVE DEFINED COMMAND.
3-5.3 (15.2) THE ORIGINAL CALL THAT THE UNIT WAS ASSIGNED SHALL
AUTOMATICALLY BE “STACKED” FOR THAT UNIT AND SHALL BE
AUTOMATICALLY RE-ASSIGNED TO THE SAME UNIT ONCE THE
OFFICER CLEARS THE OTHER CALL FOR SERVICE.
3-5.3 (16) THE PROPOSED APPLICATION SHALL HAVE A COMMAND WHICH
WILL ALLOW A SINGLE UNIT TO BE CLEARED FROM AN EVENT
WITHOUT A DISPOSITION CODE IF OTHER UNITS ARE STILL
WORKING AN INCIDENT. AT A MINIMUM, THIS SHALL BE DONE
FROM THE COMMAND LINE.
3-5.3 (17) THE PROPOSED SYSTEM SHALL ALLOW FOR A DISPOSITION CODE
TO BE ENTERED FOR EACH OFFICER ON A CALL.
3-5.3 (18) THE PROPOSED SYSTEM SHALL ONLY REQUIRE ONE DISPOSITION
CODE FOR AN INCIDENT TO BE PLACED INTO “CLOSED” STATUS.
3-5.3 (19) IF A UNIT IS THE ONLY UNIT CURRENTLY ASSIGNED TO THE AN
EVENT THE PROPOSED APPLICATION SHALL REQUIRE A
DISPOSITION BEFORE CLEARING THE UNIT OR CLOSING THE
EVENT. ONCE THE DISPOSITION HAS BEEN ENTERED THE
PROPOSED APPLICATION SHALL CLOSE THE EVENT.
City of Fort Collins cxlvi Proposal P-847
3-5.3 (20) IF THE USER CLEARS LESS THAN ALL THE UNITS THE APPLICATION
SHALL NOT REQUIRE A DISPOSITION OR CLOSE THE EVENT.
3-5.3 (21) IF A DISPOSITION FOR THE EVENT HAS ALREADY BEEN ENTERED
THE SYSTEM SHALL NOT REQUIRE IT TO BE ENTERED AGAIN AS
ASSIGNED UNITS CLEAR.
3-5.3 (22) THE PROPOSED APPLICATION SHALL SUPPORT A SWAP FEATURE.
THIS FEATURE WILL ALLOW TWO UNITS TO EXCHANGE
CURRENTLY ASSIGNED ACTIVITIES. FOR EXAMPLE, IF ONE UNIT IS
ASSIGNED TO 123 MAIN ST. AND ANOTHER UNIT IS ASSIGNED TO 456
OAK STREET AND THEY WISH TO SWITCH ASSIGNMENTS THE
PROPOSED APPLICATION WILL ALLOW THE ASSIGNMENTS TO BE
SWAPPED WITH A SINGLE COMMAND.
3-5.3 (23) THE PROPOSED APPLICATION SHALL ALSO SUPPORT A UNIT
EXCHANGE COMMAND WHICH ALLOWS THE DISPATCHER TO
REMOVE AN ASSIGNED UNIT FROM A CALL AND ASSIGN A
ANOTHER UNASSIGNED UNIT TO THE FIRST UNIT’S CALL.
3-5.3 (23.1) THE PROPOSED APPLICATION SHALL PLACE THE FIRST UNIT
BACK IN SERVICE.
3-5.3 (24) THE PROPOSED APPLICATION SHALL ALLOW THE DISPATCHER TO
DISPATCH A CALL FOR SERVICE TO A UNIT WHICH IS NOT ON DUTY.
THE SYSTEM SHALL IMMEDIATELY LOG THE UNIT ON AS A
TEMPORARY UNIT AND SHALL BE DISTINGUISHED VISUALLY AS
NOT BEING “LOGGED” ONTO THEIR MDC.
3-5.3 (24.1) ONCE THE UNIT CLEARS THE ASSIGNMENT THE SYSTEM SHALL
PLACE THEM OFF-DUTY AGAIN.
3-5.3 (24.2) THE UTILIZATION OF A “TEMPORARY” UNIT SHALL NOT
REQUIRE THE USER TO FIRST LOG A UNIT ON DUTY.
3-5.3 (25) THE PROPOSED APPLICATION SHALL NOT REQUIRE AN
ADDITIONAL NUMBER KEYSTROKES WHEN ASSIGNING
TEMPORARY UNITS TO A CALL THAN WOULD BE REQUIRED TO
PLACE AN ON-DUTY UNIT ON A CALL.
3-5.3 (26) THE PROPOSED APPLICATION SHALL ALLOW THE DISPATCHER TO
DEFINE THE TEMPORARY UNIT NUMBER USING THAT PERSON’S
PRE-ASSIGNED UNIT NUMBER.
3-5.3 (27) THE PROPOSED APPLICATION SHALL HAVE THE ABILITY TO TRACK
OFF-DUTY DETAIL INFORMATION FOR OFFICERS.
City of Fort Collins cxlvii Proposal P-847
3-5.3 (28) THE PROPOSED APPLICATION SHALL PROVIDE A FUNCTION FOR
CHANGING THE LOCATION OF A UNIT AT ANY TIME WHILE STILL
ASSIGNED TO AN EVENT.
3-5.3 (29) WHEN A UNIT IS PLACED IN A TRAFFIC STOP STATUS, THE
PROPOSED APPLICATION SHALL ALLOW THE USER (MDC CLIENT)
TO RECORD THE LOCATION OF THE STOP, THE VEHICLE LICENSE
PLATE NUMBER, STATE OF REGISTRATION, AND COMMENTS FROM
THE COMMAND LINE.
3-5.3 (30) THE PROPOSED APPLICATION SHALL PROCESS A TRAFFIC STOP BY
INITIATING, AT A MINIMUM, AN INQUIRY TO THE FOLLOWING
RESOURCES:
3-5.3 (30.1) CCIC,
3-5.3 (30.2) CAD (PRIOR INVOLVEMENT BY LICENSE PLATE NUMBER),
3-5.3 (30.3) RMS/JMS,
3-5.3 (30.4) NCIC,
3-5.3 (30.5) DOR,
3-5.3 (30.6) AND DMV.
3-5.4 SYSTEM ACTIONS
3-5.4 (1) EACH TIME AN EVENT RECORD IS RETRIEVED FOR REVIEW OR
DISPATCH, IF RELATED PREMISE RECORDS ARE FOUND THE
PROPOSED APPLICATION SHALL DISPLAY A VISUAL WARNING
WHICH IS NOTICEABLE BUT WHICH DOES NOT INTERRUPT THE
PROCESSING OF THE EVENT.
3-5.4 (2) IT IS PREFERRED THAT THE PREMISE RECORDS WARNING NOTE
THE CATEGORIES OF THE RECORDS WHICH HAVE BEEN FOUND.
3-5.4 (3) THE PROPOSED APPLICATION SHALL ALLOW FOR “SPECIAL
INSTRUCTION MESSAGES” TO BE ENTERED FOR SPECIFIC
ADDRESSES, ADDRESS RANGES, AND GEOGRAPHICAL AREAS.
3-5.4 (3.1) THESE MESSAGES SHALL BE DEFINED BY AUTHORIZED USERS
AND BE ABLE TO CONTAIN FREE FORM TEXT INFORMATION TO
AID DISPATCHERS. EXAMPLE: NOTIFICATION INFORMATION
WHEN DISPATCHING INTO A MUTUAL AID RESPONSE AREA.
3-5.4 (3.2) THESE MESSAGES SHALL BE DISPLAYED WHEN A CALL IS
SELECTED FOR DISPATCH. THE MESSAGES WILL BE VISIBLE
City of Fort Collins cxlviii Proposal P-847
ENOUGH TO DRAW THE DISPATCHER’S ATTENTION TO THEM
WITHOUT COVERING OTHER PERTINENT INFORMATION.
3-5.4 (4) IT IS PREFERRED THAT THE PROPOSED APPLICATION SHALL HAVE
THE ABILITY TO DYNAMICALLY ALTER DISTRICTS AND
BEATS/RESPONSE AREAS BASED UPON TIME OF DAY OR NEED.
3-5.4 (5) WHEN REVIEWING A CALL RECORD FOR DISPATCH, AT A MINIMUM
THE CALL RECORD DISPLAYED SHALL INCLUDE THE FOLLOWING
INFORMATION:
3-5.4 (5.1) INCIDENT AND CASE (REPORT) NUMBER,
3-5.4 (5.2) EVENT TYPE,
3-5.4 (5.3) TIME OF EVENT INITIATION,
3-5.4 (5.4) CALL TAKER RECEIVING THE CALL AND POSITION ID,
3-5.4 (5.5) EVENT LOCATION,
3-5.4 (5.6) EVENT NUMBER,
3-5.4 (5.7) EVENT PRIORITY,
3-5.4 (5.8) COMPLAINANT NAME,
3-5.4 (5.9) COMPLAINANT ADDRESS,
3-5.4 (5.10) COMPLAINANT PHONE NUMBER,
3-5.4 (5.11) METHOD OF ALARM (911, 7 DIGIT, WALK-IN, ETC.),
3-5.4 (5.12) UNITS ASSIGNED (IF UNITS HAVE BEEN ASSIGNED),
3-5.4 (5.13) PATROL/FIRE DISTRICT,
3-5.4 (5.14) MAP GRID (X-Y),
3-5.4 (5.15) REPORTING AREA, DISTRICT OR ZONE,
3-5.4 (5.16) NEAREST HIGH AND LOW CROSS STREET,
3-5.4 (5.17) INDICATION OF PREMISE OR HAZARD RECORDS,
3-5.4 (5.18) COMMENTS OR NOTES,
3-5.4 (5.19) AND NOTIFICATIONS RELATED TO EVENTS OR LOCATIONS AS
DESCRIBED ABOVE.
City of Fort Collins cxlix Proposal P-847
3-5.4 (6) IN THE EVENT THAT THE CAD SYSTEM IS UNAVAILABLE FOR A
TIME, A FUNCTION SHALL BE PROVIDED WHICH WILL ALLOW
EVENTS TO BE ADDED RETROACTIVELY WITH THE ACTUAL DATE(S)
AND TIME(S) RATHER THAN THE CURRENT DATE(S) AND TIME(S).
3-5.4 (6.1) THE PROPOSED APPLICATION SHALL PROCESS RETROACTIVE
EVENTS AND ASSIGN CASE (REPORT) NUMBERS IN THE SAME
MANNER AS NEW EVENTS.
3-5.4 (6.2) THE PROPOSED APPLICATION SHALL CLEARLY NOTE IN THE
AUDIT TRAIL THAT AN EVENT WAS ENTERED “RETROACTIVELY”.
3-5.5 TOW REQUEST ROTATION
3-5.5 (1) THE PROPOSED APPLICATION SHALL OFFER A TOW REQUEST
ROTATION SERVICES MODULE.
3-5.5 (2) THE TOW REQUEST ROTATION SERVICE MODULE WILL ALLOW A
SYSTEM ADMINISTRATOR OR AUTHORIZED USER TO ENTER
MULTIPLE CONTRACTORS WITH DIFFERENT KINDS OF
CAPABILITIES, SIMILAR TO THE WAY PATROL UNITS ARE ENTERED
INTO THE SYSTEM AS DESCRIBED ABOVE.
3-5.5 (3) THE INFORMATION SUPPLIED TO THE DISPATCHER AFTER THIS
COMMAND HAS BEEN INITIATED SHALL INCLUDE THE NAME OF
THE TOW COMPANY, THEIR PHONE NUMBER, FREE FORM TEXT
(DESCRIBED BELOW), THE OFFICER THE TOW WAS REQUESTED
FOR, AND THE LOCATION OF THE INCIDENT FOR WHICH THE TOW
WAS CALLED.
3-5.5 (4) WHEN THE MODULE IS INVOKED IT SHALL PRESENT THE NEXT
CONTRACTOR WITH THE REQUIRED CAPABILITIES IN SEQUENTIAL
ORDER.
3-5.5 (5) IF A CONTRACTOR IS CONTACTED TO RESPOND, THEN IT’S
DETERMINED WHILE TOW IS EN ROUTE THAT THE TOW IS NO
LONGER NEEDED, THERE SHALL BE A SIMPLE CANCEL COMMAND
UTILIZED FROM THE COMMAND LINE TO PUT THAT CONTRACTOR
BACK AT THE TOP OF THE ROTATION.
3-5.5 (6) IF A CONTRACTOR CANNOT BE REACHED FOR A CALL, THE
PROPOSED APPLICATION SHALL PLACE THAT CONTRACTOR AT
THE BOTTOM OF THE ROTATION LIST.
3-5.5 (7) THE SYSTEM SHALL ALLOW TOW REQUESTS TO BE GENERATED
FOR ALL LOCATIONS INCLUDING UN-VERIFIED/FORCED
ADDRESSES.
City of Fort Collins cl Proposal P-847
3-5.5 (8) THE TOW ROTATION SHALL BE ACCESSIBLE VIA THE COMMAND
LINE BY ENTERING AN INCIDENT NUMBER OR UNIT NUMBER, A
COMMAND TO GENERATE THE NEXT TOW, AND FREE FORM TEXT
THAT IDENTIFIES THE VEHICLE BEING TOWED.
3-5.5 (8.1) THE FREE FORM TEXT FIELD SHALL BE AT LEAST 70
CHARACTERS IN LENGTH.
3-5.6 FIRE/AMBULANCE DISPATCHING
3-5.6 (1) THE PROPOSED APPLICATION SHALL ALLOW SYSTEM
ADMINISTRATOR OR AUTHORIZED USERS TO DEFINE ALARM
LEVELS.
3-5.6 (2) ALARM LEVELS SHALL ALLOW THE ADDITION OF EQUIPMENT
AND/OR APPARATUS TO ANY CALL-TYPE.
3-5.6 (3) ALARM LEVELS SHALL BE ABLE TO BE UPGRADED BY THE
DISPATCHER WITH NO MORE THAN ONE COMMAND.
3-5.6 (4) THE PROPOSED APPLICATION SHALL INCLUDE AN AMBULANCE
TRANSFER FEATURE. THIS FEATURE SHALL PERFORM THE
FOLLOWING FUNCTIONS:
3-5.6 (4.1) ALERT THE DISPATCHER OF ALL PRE-SCHEDULED EVENT
CONFLICTS AND RECOMMEND A SOLUTION,
3-5.6 (4.2) TAKE INTO ACCOUNT EMERGENT CALLS FOR SERVICE THAT ARE
BEING HANDLED BY THE AMBULANCE THAT IS SUPPOSED TO BE
TAKING A SCHEDULED TRANSFER AND RECOMMEND A
SOLUTION,
3-5.6 (4.3) AND AUTOMATICALLY SELECT AND DISPLAY A PRE-SCHEDULED
TRANSFER FOR DISPATCH AT THE PRE-DETERMINED TIME.
3-5.6 (5) AUTHORIZED USERS SHALL HAVE THE ABILITY TO DEFINE
VARIABLES (BUSINESS RULES) TO ADHERE TO CURRENT
PROTOCOLS.
3-5.6 (6) THE SYSTEM ADMINISTRATOR OR AUTHORIZED USER SHALL HAVE
THE ABILITY TO ADD “CANNED” ALPHA PAGING MESSAGES TO BE
AUTOMATICALLY SENT TO SPECIFIC GROUPS OF RESPONDERS AS
THE NEW ALARM LEVELS ARE TONED. I.E.…WHEN A 2ND ALARM IS
TONED AT THE FIRE STATIONS, CERTAIN GROUPS OF OFF-DUTY
FIREFIGHTERS ARE ALSO ALPHA PAGED AND NOTIFIED OF THE
SITUATION.
City of Fort Collins cli Proposal P-847
3-5.6 (7) THE SYSTEM SHALL NOT LIMIT THE NUMBER OF PAGERS
ATTACHED TO ANY ONE PAGER GROUP.
3-5.6 (8) THE PROPOSED APPLICATION SHALL ALLOW STATION TONING
FROM THE COMMAND LINE, WITHOUT GENERATING A CALL FOR
SERVICE. THIS IS TO PROVIDE A MEANS OF TESTING THE TONING
SYSTEM.
3-5.6 (9) THE PROPOSED APPLICATION SHALL INCORPORATE AN ALPHA
PAGING SYSTEM (ABILITY TO PAGE UTILIZING THE CAD
SOFTWARE). THE PAGING SYSTEM SHALL BE ACCESSIBLE FROM
BOTH WORKSTATIONS AND FROM MDC’S TO SEND PAGES VIA A
PAGING INTERFACE TO BOTH THE COUNTY PAGING SYSTEM AND
COMMERCIAL PAGING SYSTEMS.
3-5.6 (10) THE PROPOSED APPLICATION SHALL HAVE THE ABILITY TO WORK
WITH A ZETRON MODEL 25 AND 26 FIRE STATION TONERS VIA A
PAGING INTERFACE, UTILIZING ALL AVAILABLE FEATURES OF
THESE SYSTEMS PROVIDE.
3-5.6 (11) THE PROPOSED APPLICATION SHALL HAVE THE ABILITY TO WORK
WITH A ZETRON MODEL 2200 PAGING SYSTEM VIA A PAGING
INTERFACE, UTILIZING ALL AVAILABLE FEATURES OF THESE
SYSTEMS PROVIDE.
3-5.6 (12) THE APPLICATION SHALL BE ABLE TO BE CONFIGURED BY AN
AUTHORIZED USER, TO AUTOMATICALLY SEND CALL
INFORMATION TO RESPONDING UNITS’ ALPHA PAGERS AS THE
CALL IS DISPATCHED, WITH NO OTHER ACTION TAKEN BY THE
DISPATCHER. THE ALPHA PAGE SHALL BE ABLE TO BE
CONFIGURED WITH THE FOLLOWING INFORMATION:
3-5.6 (12.1) ADDRESS,
3-5.6 (12.2) LOCATION,
3-5.6 (12.3) HIGH AND LOW CROSS STREETS,
3-5.6 (12.4) MAP PAGE,
3-5.6 (12.5) AND CALL TEXT INFORMATION TO A TOTAL OF 220 CHARACTERS
IN LENGTH.
3-5.6 (13) IT IS PREFERRED THAT THE APPLICATION HAVE THE ABILITY FOR
AUTHORIZED USERS TO ENTER PRE-SCRIPTED MESSAGES TO
EXPEDITE PAGING GROUPS SUCH AS SWAT PARAMEDICS. PRE-
SCRIPTED MESSAGES MUST BE ABLE TO HAVE SPACES LEFT FOR
City of Fort Collins clii Proposal P-847
CALL SPECIFIC INFORMATION THE DISPATCHER WILL ENTER
BEFORE SENDING.
3-5.6 (14) THE PAGING APPLICATION SHALL HAVE THE ABILITY TO BE
“MINIMIZED” IN SOME FASHION AS TO NOT INTERRUPT OTHER
DISPATCHING FUNCTIONS AS MODEMS ARE BEING DIALED AND
PAGES SENT.
3-5.6 (15) THE APPLICATION SHALL PROVIDE A VISUAL ALERT TO THE
SENDING CONSOLE TO NOTIFY THE USER THAT THE PAGE HAS
BEEN SUCCESSFULLY SENT OR FAILED AND NEEDS TO BE RESENT.
3-5.6 (16) THE APPLICATION SHALL RECOMMEND UNITS FOR EACH CALL
TYPE AND AUTOMATICALLY POPULATE THOSE UNITS INTO A FORM
FOR DISPATCH.
3-5.6 (17) THE RECOMMENDED UNITS SHALL BE DETERMINED BY RUN
ORDERS ALREADY IN PLACE GEOGRAPHICALLY.
3-5.6 (18) THE APPLICATION SHALL ALLOW/FACILITATE THE IMPORTING OF
RUN CARDS INFORMATION FROM THE PARTICIPATING AGENCIES
CURRENTLY USING A CAD SYSTEM TO AVOID REBUILDING THAT
DATABASE FROM SCRATCH.
3-5.6 (19) IF AVL IS UTILIZED, THE SYSTEM SHALL RECOGNIZE AS UNITS
MOVE THROUGH THEIR JURISDICTION AND ADJUST
RECOMMENDATIONS OF UNITS ACCORDINGLY.
3-5.6 (20) THE PROPOSED APPLICATION SHALL ALLOW THE DISPATCHER TO
DISPATCH A CALL WITH A SINGLE KEY OR SINGLE KEYSTROKE
COMBINATION, PROVIDED THE SYSTEM IS ABLE TO RECOMMEND
UNITS FOR RESPONSE AND AUTOMATICALLY POPULATE A FORM OR
COMMAND LINE WITH THOSE UNITS.
3-5.6 (21) UPON STRIKING THE SINGLE KEY OR SINGLE KEYSTROKE
COMBINATION TO DISPATCH UNITS, THE APPLICATION SHALL
PERFORM THE FOLLOWING FUNCTIONS:
3-5.6 (21.1) TONE ALL APPLICABLE FIREHOUSES/AMBULANCE STATIONS,
3-5.6 (21.2) AND SEND THE INFORMATION TO ALL APPLICABLE PERSONNEL’S
ALPHA PAGERS AS DESCRIBED ABOVE.
3-5.6 (22) THE PROPOSED APPLICATION SHALL ALLOW THE SYSTEM
ADMINISTRATOR OR AUTHORIZED USER TO CONFIGURE THE
SYSTEM TO ALLOW FIRE/AMBULANCE CALLS TO BE CLOSED
WITHOUT THE USE OF DISPOSITION CODES.
City of Fort Collins cliii Proposal P-847
3-5.6 (23) THE PROPOSED APPLICATION SHALL ALLOW ADDITIONAL UNITS
BE ADDED TO A CALL THAT IS ACTIVE AND ASSIGNED FROM THE
COMMAND LINE, MOUSE, FORM AND/OR CHECK BOX.
3-5.6 (23.1) THE APPLICATION SHALL GIVE THE DISPATCHER THE CHOICE
OF SENDING TONES AND/OR ALPHA PAGES WHEN ASSISTING
OTHER UNITS IN THIS MANNER.
3-5.6 (24) THE PROPOSED APPLICATION SHALL ALLOW THE SYSTEM
ADMINISTRATOR OR AUTHORIZED USER TO DEFINE WHAT UNITS
ARE TO BE RECOMMENDED FOR EACH OF THE FOLLOWING:
3-5.6 (24.1) CALL TYPE,
3-5.6 (24.2) CALL TYPE AND GEOGRAPHY,
3-5.6 (24.3) CALL TYPE AND ADDRESS,
3-5.6 (24.4) OR CALL TYPE AND ADDRESS RANGE.
3-5.6 (25) THE PROPOSED APPLICATION SHALL ALLOW ALL LOGGED ON
UNITS TO SHOW AVAILABLE FOR CALLS ON THE DISPATCH SCREEN.
3-5.6 (26) THE PROPOSED APPLICATION SHALL ALLOW THE MOVEMENT OF
FIRE/AMBULANCE (MANUALLY) UNITS INTO DIFFERENT STATION
ASSIGNMENTS. THIS FUNCTION SHALL BE AVAILABLE FROM
WORKSTATIONS AND MDC’S.
3-5.6 (27) THE PROPOSED APPLICATION SHALL SUGGEST COVERAGE OF
FIREHOUSES THAT ARE VACANT DUE TO UNITS BEING ASSIGNED TO
LARGE-SCALE INCIDENTS (MOVE-UPS).
3-5.6 (27.1) THE SYSTEM SHALL ALERT THE DISPATCHER TO THE STATION
VACANCIES
3-5.6 (27.2) THE SYSTEM SHALL OFFER COVERAGE SOLUTIONS DUE TO
STATION VACANCIES.
3-5.6 (27.3) THE SYSTEM SHALL AUTOMATICALLY POPULATE A FORM WITH
UNITS TO BE TONED IF THE DISPATCHER ACCEPTS THE
RECOMMENDATIONS.
3-5.6 (27.4) ALL VARIABLES SHALL BE USER-DEFINABLE TO ASSURE
ADHERENCE TO CURRENT PROTOCOL.
City of Fort Collins cliv Proposal P-847
3-5.7 AUTOMATED ON-LINE SSM CONTROL FEATURES
Automated System Status Management (SSM) controls exist primarily to aid Dispatchers in
maintaining the best possible coverage at every point in time given the remaining ambulance
resources then available in the system, and to aid in assigning units to calls in the most prudent
manner possible. This specification category includes features enabling input of various SSM
protocols and controls by time-of-day and day-of-week, and the on-line application of those
protocols and controls.
3-5.7 (1) THE PROPOSED APPLICATION SHALL BE CAPABLE OF EASILY
CREATING AND STORING SUFFICIENT SYSTEM STATUS PLANS (SSPS)
FOR HOUR-OF-DAY, DAY-OF-WEEK AND FOR SPECIAL SITUATIONS
SUCH SEVERE WEATHER, MAJOR SPORTING EVENTS, AND
HOLIDAYS.
3-5.7 (1.1) PLANS SHALL BE EASILY MODIFIED, COPIED, OR DUPLICATED.
3-5.7 (1.2) SSP TABLE EXAMPLE: XX DESIGNATES EQUAL / ALTERNATE
POSTS:
PLAN #
HOUR_
_
DAY___
POST
”1”
POST
“2”
POST
“3”
POST
“4”
POST
“5”
LEVEL
1 **
LEVEL
2 ** XX XX
LEVEL
3 ** XX ** XX
LEVEL
4 ** ** ** **
LEVEL
5 ** ** ** ** **
3-5.7 (2) THE PROPOSED APPLICATION SHALL PROVIDE AN EASILY
UNDERSTOOD AND CONVENIENT FORMAT FOR ENTERING SSP
INFORMATION RE-POST PRIORITIES FOR EACH SSP, AT EACH
STATUS LEVEL.
3-5.7 (3) THE SYSTEM SHALL BE CAPABLE OF HANDLING (I.E. STORING,
DISPLAYING, AND CONTROLLING) NOT LESS THAN 10 SEPARATE
POST LOCATIONS, WITH STATUS LEVELS UP TO 20 UNITS.
City of Fort Collins clv Proposal P-847
3-5.7 (4) WITH THE SSP ENTERED, THE APPLICATION SHALL PROVIDE
VISUAL WARNING WHEN THE SYSTEM IS NOT IN COMPLIANCE
WITH SSP, AND CLEAR INDICATION OF WHAT MUST BE DONE TO
RESTORE COMPLIANCE.
3-5.7 (5) THE VISUAL WARNING SHALL BE DISPLAYED IN SUCH A MANNER AS
TO NOT HINDER ANY OTHER WORK BEING COMPLETED AT THE
TIME.
3-5.7 (6) SSM FEATURES SHALL INCLUDE THE “EQUAL/ALTERNATE POST
CONTROL FEATURE, DESIGNATED WITHIN THE SSP, BY ASSIGNING
THE SAME POST PRIORITY TO TWO OR MORE POSTS AT THE SAME
STATUS LEVEL.
3-5.7 (7) SO LONG AS AN AVAILABLE UNIT IS LOCATED AT ANY
EQUAL/ALTERNATE POST, THE SYSTEM SHALL BE DEEMED IN
COMPLIANCE WITH THE SSP. IF THE SYSTEM IS NON-COMPLIANT,
AND A UNIT MUST BE MOVED TO A POST FOR WHICH THERE IS AN
EQUAL/ALTERNATE, BOTH POSTS SHALL BE DISPLAYED AS
ALTERNATIVE OPTIONS FOR RESTORING COMPLIANCE.
3-5.7 (8) THE PROPOSED APPLICATION SHALL PROVIDE THE ABILITY FOR
ASSIGNMENT OF MULTIPLE UNITS TO A GIVEN POST, WITH A
METHOD TO ASSIGN A “DISPATCH PRIORITY” TO EACH UNIT.
3-5.7 (9) THE PROPOSED APPLICATION SHALL INCORPORATE A METHOD
FOR “SPECIAL UNIT ACTIVATION.” THE PURPOSE OF THIS FEATURE
IS TO PROVIDE FOR PLANNED ACTIVATION OF A “SUPERVISOR’S
UNIT” OR OTHER “SPECIAL UNIT” NOT OTHERWISE AVAILABLE IN
THE SYSTEM.
3-5.7 (9.1) THE ACTIVATION NOTIFICATION SHALL APPEAR ON THE
DISPATCH SCREEN, SUBJECT TO CONDITIONS SPECIFIED IN THE
SSP.
3-5.7 (9.2) USER-SPECIFIED OPTIONAL CONDITIONS SHALL INCLUDE:
STATUS LEVEL AND TYPE OF CALL.
3-5.7 (10) THE PROPOSED APPLICATION SHALL INCORPORATE A TABLE
DRIVEN “NON EMERGENCY CUTOFF” PROTOCOL LINKED TO EACH
SSP. THE PURPOSE OF THIS FEATURE IS TO NOTIFY THE
DISPATCHER WHEN A PRE-DETERMINED AMBULANCE LEVEL IS
REACHED.
3-5.7 (10.1) THE “CUTOFF” NOTIFICATION SHALL APPEAR ON THE DISPATCH
SCREEN, BUT SHALL NOT PREVENT THE DISPATCHER FROM
TAKING AN ACTION OR DISPATCHING A CALL.
City of Fort Collins clvi Proposal P-847
3-5.7 (11) THE PROPOSED APPLICATION SHALL INCLUDE AN “EMERGENCY
ONLY” UNIT RESTRICTION. THIS REFERS TO A UNIT WHICH IS NOT
AVAILABLE FOR POSTING OR FOR DISPATCH TO ROUTINE CALLS,
BUT IS AVAILABLE FOR DISPATCH TO EMERGENCY CALLS, AND CAN
TRANSPORT.
3-5.7 (12) THE PROPOSED APPLICATION SHALL INCLUDE A “NON-
TRANSPORT” STATUS UNIT RESTRICTION: (MANUAL/AUTOMATIC).
THIS UNIT IS AVAILABLE FOR DISPATCH TO EMERGENCY CALLS
BUT CANNOT TRANSPORT AND IS NOT DISPATCHED TO ROUTINE
CALLS.
3-5.7 (12.1) AN AUTOMATIC PROMPT SHALL REQUEST THE DISPATCH OF AN
ADDITIONAL UNIT TO THE SAME INCIDENT TO TRANSPORT.
3-5.7 (13) THE PROPOSED APPLICATION SHALL ALLOW FOR A “HOME POST”
FEATURE. THIS FEATURE ALLOWS A UNIT TO BE GIVEN A “HOME
POST” DESIGNATION AT THE TIME OF UNIT SETUP. WHEN ACTIVE,
THE HOME POST PROTOCOL WILL CALL FOR RELOCATION OF
“HOME POST” UNITS TO THEIR DESIGNATED HOME POSTS.
3-5.7 (14) THE APPLICATION SHALL PROVIDE AN EMERGENCY DISPATCH
UNIT RECOMMENDATION. THIS FEATURE SHALL PROVIDE FOR
AUTOMATIC RECOMMENDATION OF THE THREE NEAREST
AVAILABLE UNITS OR UNITS EN ROUTE TO LOWER-PRIORITY CALLS
(BY MPD PROTOCOL), LISTED NEAREST UNIT FIRST.
3-5.7 (14.1) “NEAREST” SHALL BE DETERMINED BY AVL (IF AVAILABLE)
USING STREET ATTRIBUTES OR LAST KNOWN LOCATION.
3-5.7 (15) THE PROPOSED APPLICATION SHALL PROVIDE AN AUTOMATIC
RECOMMENDATION FOR MULTIPLE AMBULANCE RESPONSE BASED
ON MPD PRIORITY CODE OR “CODE 5 STATUS” (IF SINGLE UNIT
LISTED IS A “STATUS 5” UNIT, DISPLAY WILL INDICATE “NON-
TRANSPORT UNIT”). (“ADDITIONAL UNIT” COMMAND CREATES
DUPLICATE “RUN CARD” FOR ASSIGNMENT OF OTHER UNITS TO
SAME INCIDENT.)
3-5.7 (16) THE PROPOSED APPLICATION SHALL PROVIDE A PRE-SCHEDULED
TRANSFER UNIT RECOMMENDATION. THIS FEATURE SHALL
PROVIDE FOR AUTOMATIC RECOMMENDATION OF UNITS FROM A
TABLE DRIVEN LIST OR THE NEAREST AVAILABLE UNIT IF NO
LISTED UNITS ARE AVAILABLE.
3-5.7 (17) THE PROPOSED APPLICATION SHALL NOTIFY THE DISPATCHER
WHEN AMBULANCE RESOURCES REACH CERTAIN LEVELS AND
SUGGEST A SOLUTION I.E. WHICH AGENCY TO CONTACT FOR
OTHER RESOURCES.
City of Fort Collins clvii Proposal P-847
3-5.7 (18) THE APPLICATION SHALL NOTIFY THE DISPATCHER WHEN AN
AMBULANCE IS DISPATCHED OUT OF A PRE-DETERMINED
GEOGRAPHICAL AREA AND OFF-DUTY CREWS OR OTHER AGENCY
AMBULANCES ARE NECESSARY FOR COVERAGE.
3-5.7 (19) IF THE DISPATCHER SELECTS THE SYSTEM RECOMMENDATION,
THE SYSTEM SHALL AUTOMATICALLY PAGE THE ON-CALL
AMBULANCE CREW WITH A “CANNED” ALPHA PAGE.
3-5.7 (20) THE PROPOSED APPLICATION SHALL ALLOW THE USER TO
CONFIGURE THE SYSTEM TO RECOGNIZE WHICH AMBULANCE
UNIT IS FIRST OR LAST CALL IN REFERENCE TO TIME OF DAY
AND/OR DAY OF THE WEEK.
3-5.7 (21) THE PROPOSED APPLICATION SHALL AUTOMATICALLY RECOGNIZE
A PRE-DETERMINED GEOGRAPHICAL AREA, CALL TYPE, AND TIME
OF DAY AND ALERT THE DISPATCHER TO CONTACT AN AIR
AMBULANCE FOR IMMEDIATE RESPONSE
3-5.7 (22) THE PROPOSED APPLICATION SHALL CONTAIN A SEPARATE
DATABASE WHERE BURN PERMITS WILL BE ENTERED AND
MAINTAINED.
3-5.7 (23) WHEN A CITIZEN CALLS TO REPORT THEY WILL BE CONDUCTING A
PRESCRIBED OR RECREATIONAL BURN THE SYSTEM SHALL DO THE
FOLLOWING:
3-5.7 (23.1) SHOW A VISUAL REFERENCE ON THE DISPATCHER’S SCREEN.
THE VISUAL REFERENCE SHALL BE AS UNOBTRUSIVE AS
POSSIBLE AND SHALL INCLUDE BURN PERMIT NUMBER, ADDRESS
OR LOCATION WHERE THE BURN IS, CALLBACK NUMBER.
3-5.7 (23.2) THE SYSTEM SHALL RECOGNIZE THESE CALLS AND ALERT THE
DISPATCHER TO THE POSSIBILITY OF A DUPLICATE CALL
SHOULD ANOTHER CALL BE ENTERED AT THE SAME LOCATION
OR GENERAL AREA.
3-5.7 (24) THE PROPOSED APPLICATION SHALL CREATE ONE INCIDENT ONLY
FOR CALLS REQUIRING BOTH FIRE APPARATUS AND AMBULANCE.
3-5.7 (24.1) IT IS PREFERRED THE PROPOSED APPLICATION SHALL CREATE,
HOWEVER, TWO SEPARATE INCIDENT NUMBERS—ONE FOR THE
FIRE JURISDICTION AND ONE FOR THE AMBULANCE
JURISDICTION UNDER THE ONE INCIDENT CREATED.
3-5.7 (24.2) THE PROPOSED APPLICATION SHALL ALSO AUTOMATICALLY
ASSIGN TWO AGENCY SPECIFIC (ONE FIRE, ONE EMS) CASE
City of Fort Collins clviii Proposal P-847
(REPORT) NUMBERS TO EACH INCIDENT NUMBER UPON
DISPATCH.
3-5.7 (25) THE PROPOSED APPLICATION SHALL HAVE THE ABILITY TO
CREATE “COMBINED” CALLS FOR POLICE AND FIRE/AMBULANCE
AT THE SAME TIME. THIS FUNCTION SHALL ALLOW RESOURCES
TO BE SENT TO THE SAME LOCATION ON THE SAME CALL, BUT
WITH THEIR RESPECTIVE CALL-TYPES.
3-5.7 (26) “COMBINED” CALLS SHALL BE AUTOMATICALLY “CROSS-
REFERENCED” WITH EACH OTHER BY INCIDENT NUMBER UPON
CREATION.
3-5.7 (27) THE PROPOSED APPLICATION SHALL ALLOW THE USER TO
CONFIGURE CERTAIN CALL-TYPES TO BE COMBINED, AND
AUTOMATICALLY GIVE THE DISPATCHER THE OPTION TO CREATE
BOTH, ONE, OR NEITHER.
3-5.7 (27.1) THE APPLICATION SHALL ALLOW THE DISPATCHER TO CHANGE
CALL TYPES FOR THE COMBINED CALLS IF NECESSARY BEFORE
THE CALL IS ENTERED.
3-5.7 (28) THE PROPOSED APPLICATION SHALL INCLUDE A “SPLIT CREW”
FUNCTION. THIS FUNCTION SHALL BE DRIVEN BY MINIMUM
NUMBERS OF PERSONNEL, DEFINED BY THE USER AGENCIES, THAT
ARE TO RESPOND ON PRIMARY AND SECONDARY PIECES OF
APPARATUS ASSIGNED TO A SINGLE FIRE STATION. I.E. WHEN THE
PRIMARY UNIT IS DISPATCHED ON A CALL OR MOVED OUT OF ITS
STATION AREA, THE SECONDARY UNIT SHALL AUTOMATICALLY
BECOME UNAVAILABLE IF THERE ARE NOT ENOUGH PERSONNEL
REMAINING TO RESPOND ON THAT PIECE OF APPARATUS.
3-5.7 (28.1) IF THE SECONDARY PIECE OF APPARATUS IS DISPATCHED TO A
CALL OR MOVED OUT OF IT’S AREA, THE PRIMARY UNIT SHALL
REMAIN AVAILABLE FOR CALLS (ASSUMING THERE ARE ENOUGH
PERSONNEL REMAINING).
3-5.7 (28.2) THE DISPATCHER SHALL HAVE THE ABILITY TO OVERRIDE
THESE FUNCTIONS AS NECESSARY.
3-5.7 (29) THE PROPOSED APPLICATION SHALL ALLOW THE SYSTEM
ADMINISTRATOR OR AUTHORIZED USER TO CREATE VOLUNTEER
STATION BOUNDARIES WITHIN THE PAID STATIONS BOUNDARIES.
3-5.7 (29.1) WHEN A CALL IS CREATED IN AN AREA THAT IS PART OF THE
VOLUNTEER BOUNDARY, THE VOLUNTEER UNITS SHALL BE
ADDED TO THE NORMAL FULL ASSIGNMENT OF PAID
EQUIPMENT.
City of Fort Collins clix Proposal P-847
3-5.7 (29.2) THE VOLUNTEER UNITS SHALL BE ABLE TO MOVE INTO A PAID
STATION AREA AND BECOME PART OF THE NORMAL RUN
ASSIGNMENT FOR THAT STATION.
3-5.7 (30) THE PROPOSED APPLICATION SHALL ALLOW OTHER FIRE
AGENCIES UNITS TO BE INCLUDED IN THE RUN CARDS AND BE
AUTOMATICALLY RECOMMENDED FOR DISPATCH IF A CALL FOR
SERVICE IS WITHIN A GIVEN BOUNDARY (AUTO-AID AREAS WHERE
MULTIPLE FIRE AGENCIES RESPOND TO THE SAME ADDRESS).
CLARIFICATION: THE OTHER AGENCY FIRE UNITS WILL NOT BE
DISPATCHED BY THIS AGENCY—THIS FEATURE IS TO MAKE THE
DISPATCHER AWARE THAT A CALL FOR SERVICE IS OCCURRING IN
AN AREA WHERE THEY NEED TO CONTACT ANOTHER AGENCY FOR
RESPONSE.
3-5.7 (30.1) IT IS PREFERRED THAT THE PROPOSED APPLICATION BE
CAPABLE OF NOTIFYING OTHER AGENCIES DISPATCH CENTERS
AUTOMATICALLY OF A CALL FOR SERVICE VIA DATA STREAMS,
OR PAGING SYSTEMS.
3-5.7 (31) THE PROPOSED APPLICATION SHALL ALLOW FOR BUREAU
(INVESTIGATIONS) UNITS TO BE ATTACHED TO THE LADDER
COMPANIES, BUT BE MAINTAINED AS A SEPARATE UNIT.
CLARIFICATION: THE BUREAU IS ACTUALLY A 4TH FIREFIGHTER
ASSIGNED TO A LADDER COMPANY, BUT RESPONDS IN THEIR OWN
VEHICLE AND HAS OTHER DUTIES SEPARATE OF THE LADDER
COMPANY AT TIMES.
3-5.7 (31.1) WHEN THE LADDER COMPANIES ARE DISPATCHED, THE BUREAU
UNIT SHALL BE AUTOMATICALLY RECOMMENDED AND
DISPATCHED WITH THE LADDER UNIT IT SUPPORTS. I.E.
BUREAU1 SHALL RESPOND WITH LADDER1 AND BUREAU5 SHALL
RESPOND WITH LADDER5 ETC.
3-5.7 (31.2) THE BUREAU UNIT SHALL NOT BE RECOMMENDED FOR
DISPATCH WITH A LADDER COMPANY IT IS NOT ATTACHED TO,
EVEN THOUGH THE RUN CARD WILL SHOW INCOMPLETE FOR
DISPATCH.
3-5.7 (31.3) BUREAU UNITS SHALL BE ABLE TO BE DISPATCHED TO CALLS
WITHOUT THE ACCOMPANYING LADDER UNIT. THIS IS TO
FACILITATE THE USE OF THE BUREAU UNITS FOR CODE
VIOLATIONS ETC.
3-5.7 (32) THE PROPOSED APPLICATION SHALL ALLOW THE USE OF LADDER-
TENDERS. LADDER-TENDERS SHALL BE ATTACHED TO A PRIMARY
City of Fort Collins clx Proposal P-847
LADDER UNIT JUST AS THE BUREAU UNIT IS ATTACHED TO THE
LADDER UNIT.
3-5.7 (32.1) LADDER-TENDERS SHALL BE DISPATCHED IN CONJUNCTION
WITH THE LADDER UNIT IN WHICH IT IS ATTACHED.
3-5.7 (32.2) LADDER-TENDERS SHALL BE ABLE TO BE DISPATCHED TO CALLS
WITHOUT THE ACCOMPANYING LADDER UNIT. THIS IS TO
FACILITATE THE USE OF THE LADDER-TENDERS FOR USE IN
WILD-LAND FIRE SITUATIONS IN RURAL AREAS.
3-5.7 (33) THE PROPOSED APPLICATION SHALL RECOGNIZE DRY AREAS IN
THE SYSTEM (AREAS WITHOUT FIRE HYDRANTS).
3-5.7 (33.1) THE PROPOSED SYSTEM SHALL AUTOMATICALLY ADD TENDERS
TO THE STRUCTURE FIRE RUN CARDS IN THESE AREAS.
3-5.7 (34) THE PROPOSED APPLICATION SHALL ALLOW AN “INSERT”
FUNCTION IN THE RUN CARD SYSTEM.
3-5.7 (34.1) THE INSERT FUNCTION SHALL ALLOW FOR FUTURE ADDITIONS
OF EQUIPMENT OR FIRE STATIONS WITHOUT THE NEED TO
RETYPE THE WHOLE RUN CARD.
3-6 MOBILE DATA COMPUTER
3-6.1 (1) IT IS PREFERRED THAT THE CAD MOBILE APPLICATION BE FULLY
DEVELOPED AND SUPPORTED BY THE SAME VENDOR FOR THE CAD
SYSTEM RATHER THAN A THIRD PARTY VENDOR.
3-6.1 (2) ALL DESCRIBED FUNCTIONS FOR THE MOBILE SYSTEM SHALL BE
COMPLETED BY EACH OF THE FOLLOWING:
3-6.1 (2.1) COMMAND LINE,
3-6.1 (2.2) MASKS/FORMS,
3-6.1 (2.3) AND HOT KEYS.
3-6.1 (2.4) ALL COMMANDS NOT POSSIBLE BY THE AFOREMENTIONED
FUNCTIONS SHALL BE DEFINED BY THE VENDOR.
3-6.1 (3) THE LOOK AND FEEL OF THE CAD CLIENT SHALL BE FULLY
CONFIGURABLE BY AGENCY SPECIFIC TO THE FUNCTIONS OF THAT
AGENCY (POLICE, FIRE AND EMS APPLICATIONS).
City of Fort Collins clxi Proposal P-847
3-6.1 (4) THE PROPOSED SYSTEM SHALL ALLOW THE SYSTEM
ADMINISTRATOR OR AUTHORIZED USER TO MAP THE MDC
KEYBOARD AS NECESSARY.
3-6.1 (5) THE PROPOSED MOBILE DATA APPLICATION SHALL RECEIVE AND
PROCESS LOGON REQUESTS FROM MDC EQUIPPED UNITS. WHEN A
LOGON REQUEST IS RECEIVED THE CAD SHALL:
3-6.1 (5.1) LOG THE UNIT ON WITH FULL CAD FUNCTIONALITY INCLUDING
ALL OTHER DATABASE FUNCTIONS, BUT NOT PLACE THEM IN AN
AVAILABLE-FOR-DUTY STATUS UNTIL THE MDC USER ISSUES
ANOTHER COMMAND,
3-6.1 (5.2) AND RECORD THE OFFICER(S) ASSIGNED TO THE UNIT.
3-6.1 (6) THE PROPOSED MOBILE DATA INTERFACE SHALL RECEIVE AND
PROCESS LOGOFF REQUESTS FROM MDC EQUIPPED UNITS.
3-6.1 (6.1) UNITS SHALL ALSO HAVE THE ABILITY TO REMOVE THEMSELVES
FROM ON-DUTY STATUS, TO OFF-DUTY STATUS WITHOUT FULLY
LOGGING OFF OF THE SYSTEM.
3-6.1 (6.2) AFTER BEING PLACED INTO THE OFF-DUTY STATUS, BUT
REMAINING LOGGED ON, THE USER SHALL HAVE FULL ACCESS
TO THE CAD SYSTEM AND ALL OTHER DATABASES ASSOCIATED.
3-6.1 (6.3) AFTER BEING PLACED INTO THE OFF-DUTY STATUS, BUT
REMAINING LOGGED ON, THE UNIT SHALL NO LONGER SHOW UP
ON THE DISPATCHER’S SCREEN.
3-6.1 (7) THE PROPOSED MOBILE DATA INTERFACE SHALL RECEIVE AND
PROCESS ALL CAD COMMANDS FROM AN MDC.
3-6.1 (7.1) ALL COMMANDS AVAILABLE ON THE CAD SYSTEM SHALL BE
AVAILABLE TO MOBILE USERS.
3-6.1 (7.1.1) CAD COMMANDS NOT AVAILABLE ON THE MDC, BUT
AVAILABLE ON THE CAD SYSTEM SHALL BE DETAILED BY THE
VENDOR.
3-6.1 (8) THE PROPOSED MOBILE DATA INTERFACE SHALL AUTOMATICALLY
SEND A COPY OF EACH CALL FOR SERVICE TO THE ASSIGNED
UNITS. THIS MESSAGE SHALL INCLUDE THE FOLLOWING
INFORMATION:
3-6.1 (8.1) THE EVENT NATURE CODE,
3-6.1 (8.2) THE EVENT PRIORITY,
City of Fort Collins clxii Proposal P-847
3-6.1 (8.3) EVENT NUMBER,
3-6.1 (8.4) THE CASE (REPORT) NUMBER (WHEN ASSIGNED),
3-6.1 (8.5) THE LOCATION OF THE INCIDENT,
3-6.1 (8.6) THE NAME, ADDRESS AND PHONE NUMBER OF THE
COMPLAINANT,
3-6.1 (8.7) PREMISE AND HAZARD ALERTS FOR THE ASSIGNED LOCATION,
3-6.1 (8.8) THE TIME THE CALL WAS RECEIVED,
3-6.1 (8.9) THE TIME THE CALL WAS DISPATCHED,
3-6.1 (8.10) THE UNITS ASSIGNED TO THE CALL,
3-6.1 (8.11) AND THE COMMENTS FIELD.
3-6.1 (9) WHEN A CALL OR MESSAGE IS SENT TO A MDC EQUIPPED UNIT THE
SYSTEM SHALL PROVIDE A POSITIVE ACKNOWLEDGEMENT TO THE
SENDER THAT THE CALL OR MESSAGE WAS RECEIVED BY THE MDC.
3-6.1 (10) ON DEMAND, MESSAGES TO OR FROM A MDC EQUIPPED UNIT
SHALL BE LOGGED TO THE INCIDENT OR UNIT AUDIT TRAIL.
3-6.1 (11) IF THE PROPOSED APPLICATION HAS A FEATURE THAT
AUTOMATICALLY LOGS EVERY MESSAGE TO OR FROM AN MDC
EQUIPPED UNIT INTO AN INCIDENT OR UNIT AUDIT TRAIL, THAT
FEATURE SHALL BE EASILY DISABLED BY THE SYSTEM
ADMINISTRATOR OR AUTHORIZED USER.
3-6.1 (12) THE PROPOSED APPLICATION SHALL ALLOW MDC USERS TO
IMPORT RESPONSE INFORMATION FROM OTHER APPLICATIONS
SUCH AS CCIC/NCIC OR LIMITED RMS INFORMATION (AS DEFINED
BY THE SYSTEM ADMINISTRATOR) INTO THE BODY OF A CALL.
3-6.1 (13) THE PROPOSED APPLICATION SHALL PROVIDE A VISUAL AND
AUDIBLE ALERT TO MDC USERS WHEN ANY INFORMATION
PERTAINING TO AN INCIDENT THAT USER IS ASSIGNED TO, HAS
BEEN UPDATED IN ANY WAY.
3-6.1 (13.1) THE SYSTEM SHALL NOT DISPLAY THE UPDATED INFORMATION
UNTIL REQUESTED BY A SINGLE KEY OR SINGLE KEYSTROKE
COMBINATION BY THE MDC USER.
3-6.1 (13.2) WHEN THE USER RECALLS THE INCIDENT TO REVIEW THE NEW
INFORMATION, THE ENTIRE INCIDENT SHALL BE DISPLAYED.
City of Fort Collins clxiii Proposal P-847
3-6.1 (14) THE USER SHALL BE ABLE TO EASILY SCROLL OR PAGE FORWARDS
AND BACKWARDS THROUGH AN INCIDENT WITHOUT USE OF A
POINTING DEVICE.
3-6.1 (15) THE PROPOSED MOBILE DATA INTERFACE SHALL ALLOW MDC
EQUIPPED UNITS TO INITIATE TRAFFIC STOPS FROM THEIR MDC’S
WITHOUT DISPATCHER INTERVENTION.
3-6.1 (15.1) WHEN MDC EQUIPPED UNITS INITIATE A TRAFFIC STOP THE CAD
SHALL PROCESS THE MESSAGE AS IF IT HAD BEEN ENTERED BY A
DISPATCHER.
3-6.1 (15.2) IN THE EVENT THAT A MDC INITIATED INQUIRY RECEIVES A HIT
FROM CCIC/NCIC OR ANOTHER SOURCE, THE VENDOR’S
PROPOSED INTERFACE TO THE MESSAGE SWITCH SHALL
ENSURE THAT AN ALERT MESSAGE IS ROUTED TO THE
DISPATCHER RESPONSIBLE FOR THAT UNIT AS WELL AS THE
MDC USER.
3-6.1 (15.3) THE DISPATCHER ALERT SHALL BE DISPLAYED IN AN OBVIOUS,
BUT NOT OBTRUSIVE MANNER.
3-6.1 (16) THE PROPOSED MOBILE DATA INTERFACE SHALL ALLOW MDC
EQUIPPED UNITS TO INITIATE AN INCIDENT.
3-6.1 (16.1) THE CAD APPLICATION SHALL CHANGE THE UNIT’S STATUS TO
ASSIGNED AT THE LOCATION GIVEN IN THE MDC MESSAGE.
3-6.1 (17) THE PROPOSED MOBILE DATA INTERFACE SHALL ALLOW AN
OFFICER TO ADD COMMENTS TO ANY ACTIVE OR CLOSED CAD
EVENT.
3-6.1 (17.1) THE CAD SYSTEM SHALL LOG THE COMMENTS TO THE AUDIT
TRAIL IDENTIFYING THE USER ENTERING THE COMMENTS, AND
THE TIME AND DATE THE COMMENTS WERE ADDED.
3-6.1 (18) THE PROPOSED MOBILE DATA INTERFACE SHALL ALLOW MDC
EQUIPPED UNITS TO CLEAR A CALL TO WHICH THEY ARE
ASSIGNED.
3-6.1 (18.1) WHEN THIS MESSAGE IS RECEIVED THE CAD SHALL CHANGE
THE CALL TYPE, IF INCLUDED IN THE MESSAGE.
3-6.1 (18.2) WHEN THIS MESSAGE IS RECEIVED THE CAD SHALL RECEIVE
AND RECORD THE EVENT DISPOSITION, IF INCLUDED IN THE
MESSAGE.
City of Fort Collins clxiv Proposal P-847
3-6.1 (18.3) WHEN THIS MESSAGE IS RECEIVED THE CAD SHALL PLACE THE
UNITS ASSIGNED TO THE CALL BACK IN SERVICE.
3-6.1 (19) THE PROPOSED APPLICATION SHALL PROVIDE MDC USERS THE
ABILITY TO CLOSE CALLS UTILIZING A MASK.
3-6.1 (19.1) THE MASK SHALL BE ACCESSIBLE BY ONE KEY OR KEYSTROKE
COMBINATION.
3-6.1 (19.2) THE MASK SHALL INCLUDE FIELDS TO CHANGE CALL TYPE,
ADDRESS OF THE CALL, ADD COMMENTS TO THE CALL, AND ADD
A DISPOSITION TO THE CALL.
3-6.1 (20) THE PROPOSED APPLICATION SHALL ALLOW USERS TO RETURN TO
AN “IN-SERVICE” STATUS WITH ONE KEY OR KEYSTROKE
COMBINATION IF THAT OFFICER IS NOT PRIMARY AND,
THEREFORE, IS NOT REQUIRED TO DISPOSITION THE CALL.
3-6.1 (21) THE PROPOSED MOBILE DATA INTERFACE SHALL ALLOW MDC
EQUIPPED UNITS TO ENTER A DISPOSITION FOR A CALL TO WHICH
THEY ARE ASSIGNED WITHOUT CLEARING THE EVENT.
3-6.1 (22) THE PROPOSED APPLICATION SHALL ALLOW OFFICERS TO ASSIST
THEMSELVES ONTO ANOTHER OFFICER’S CALL WITHOUT
ASSISTANCE FROM THE DISPATCHER.
3-6.1 (22.1) THIS FUNCTION SHALL BE DONE FROM THE COMMAND LINE.
3-6.1 (23) THE PROPOSED MOBILE DATA INTERFACE SHALL ALLOW MDC
EQUIPPED UNITS TO RETRIEVE THE DETAILS OF A SINGLE
INCIDENT.
3-6.1 (23.1) CAN BE RETRIEVED BY EITHER INCIDENT NUMBER, CASE
(REPORT) NUMBER OR OFFICER ASSIGNED (IF ANY).
3-6.1 (23.2) INCIDENT CAN BE EITHER OPEN OR CLOSED.
3-6.1 (23.3) IF THE INCIDENT IS RETRIEVED BY INCIDENT NUMBER OR CASE
(REPORT) NUMBER, A MAXIMUM OF SIX CHARACTERS SHALL BE
REQUIRED TO RECALL THE INCIDENT.
3-6.1 (23.4) THE SYSTEM ADMINISTRATOR OR AUTHORIZED USER SHALL BE
ABLE TO DEFINE A DEFAULT AGENCY I.D., THAT IS NO MORE
THAN TWO CHARACTERS IN LENGTH FOR ALL WORKSTATIONS
AND MDC’S. THIS SHALL FACILITATE USERS MINIMIZING
KEYSTROKES NECESSARY WHEN RECALLING AN INCIDENT.
City of Fort Collins clxv Proposal P-847
3-6.1 (24) THE PROPOSED MOBILE DATA INTERFACE SHALL ALLOW MDC
EQUIPPED UNITS TO VIEW ALL CAD INCIDENTS FOR A USER-
DEFINED DATE RANGE.
3-6.1 (25) THE PROPOSED SYSTEM SHALL ALLOW UNITS EQUIPPED WITH
MOBILE DATA COMPUTERS TO VIEW THE CURRENT STATUS OF ALL
UNITS UNDER THE CONTROL OF THE CAD SYSTEM.
3-6.1 (25.1) THIS FUNCTION SHALL BE ACCOMPLISHED WITH ONE KEY OR
KEYSTROKE COMBINATION.
3-6.1 (25.2) THE UNIT STATUS DISPLAY SHALL INCLUDE THE FOLLOWING:
3-6.1 (25.2.1) PATROL/FIRE AREA,
3-6.1 (25.2.2) UNIT(S) ASSIGNED TO THE CALL,
3-6.1 (25.2.3) CURRENT LOCATION OF UNITS,
3-6.1 (25.2.4) CALL TYPE,
3-6.1 (25.2.5) INCIDENT NUMBER,
3-6.1 (25.2.6) UNIT STATUS (ON SCENE, EN ROUTE ETC),
3-6.1 (25.2.7) TIME ELAPSED IN CURRENT STATUS,
3-6.1 (25.2.8) AND UNITS ASSIGNED TO THE SAME CALL SHALL BE GROUPED
TOGETHER FOR EASY VIEWING BY MOBILE USERS.
3-6.1 (26) THE PROPOSED APPLICATION SHALL ALLOW UNITS EQUIPPED
WITH MOBILE DATA COMPUTERS TO VIEW PENDING INCIDENTS
UNDER THE CONTROL OF THE CAD SYSTEM.
3-6.1 (26.1) THIS SHALL BE ACCOMPLISHED WITH ONE KEY OR KEYSTROKE
COMBINATION.
3-6.1 (26.2) THE PENDING INCIDENT STATUS SHALL INCLUDE THE
FOLLOWING INFORMATION:
3-6.1 (26.2.1) INCIDENT NUMBER,
3-6.1 (26.2.2) PATROL/FIRE DISTRICT,
3-6.1 (26.2.3) CALL TYPE,
3-6.1 (26.2.4) ADDRESS/LOCATION,
3-6.1 (26.2.5) TIME ELAPSED IN PENDING STATUS,
City of Fort Collins clxvi Proposal P-847
3-6.1 (26.2.6) UNIT THE CALL IS STACKED AGAINST (IF APPLICABLE),
3-6.1 (26.2.7) AND INCIDENTS SHALL BE GROUPED BY PATROL/FIRE AREA OF
ASSIGNMENT.
3-6.1 (27) MDC EQUIPPED UNITS SHALL HAVE THE ABILITY TO DRAW THE
NEXT LOGICAL CASE (REPORT) NUMBER FOR AN EXISTING EVENT
WITHOUT DISPATCHER INTERVENTION.
3-6.1 (28) MDC EQUIPPED UNITS SHALL HAVE THE ABILITY TO SEARCH FOR
AND DISPLAY PREMISE AND HAZARD RECORDS FOR A GIVEN
ADDRESS WITHOUT INITIATING A CALL.
3-6.1 (29) IF A PREMISE OR HAZARD ENTRY IS ASSOCIATED WITH AN
INCIDENT ADDRESS, THE PROPOSED APPLICATION SHALL ALERT
THE MDC USER BY A VISUAL AND AUDIBLE ALERT.
3-6.1 (29.1) THE ALERT SHALL BE OBVIOUS BUT NOT OBTRUSIVE AND SHALL
NOT IMPEDE ANY WORK ALREADY IN PROGRESS.
3-6.1 (29.2) THE ALERT SHALL DISTINGUISH BETWEEN A PREMISE OR
HAZARD ENTRY.
3-6.1 (29.3) THE ALERT SHALL DISTINGUISH BETWEEN AND EXACT MATCH
AND A PROXIMITY MATCH WITH THE INCIDENT ADDRESS.
3-6.1 (30) THE PROPOSED APPLICATION SHALL ALLOW THE MDC USER TO
PULL UP THE FULL TEXT OF THE HAZARD AND/OR PREMISE ENTRY
WITH ONE KEYSTROKE COMBINATION IF THERE IS JUST ONE
ENTRY ASSOCIATED WITH THE ADDRESS.
3-6.1 (30.1) IF THE ADDRESS IS ASSOCIATED WITH MORE THAN ONE PREMISE
AND/OR HAZARD ENTRY, THE PROPOSED APPLICATION SHALL
INSTEAD PRODUCE A LIST OF ENTRIES.
3-6.1 (30.2) THE PREMISE AND/OR HAZARD ENTRIES SHALL BE LISTED BY
PRIORITY DEFINED BY THE SYSTEM ADMINISTRATOR OR
AUTHORIZED USER.
3-6.1 (30.3) THE MDC USER SHALL BE ABLE TO PAGE OR SCROLL THROUGH
THE LIST OF PREMISE AND/OR HAZARD ENTRIES WITHOUT THE
USE OF A POINTING DEVICE.
3-6.1 (31) THE PROPOSED APPLICATION SHALL ALLOW PREMISE AND/OR
HAZARD ENTRIES FROM THE MDC.
3-6.1 (31.1) THE MDC USER SHALL HAVE THE SAME FUNCTIONALITY AS A
DISPATCHER.
City of Fort Collins clxvii Proposal P-847
3-6.1 (32) THE PROPOSED APPLICATION SHALL ALLOW THE SYSTEM
ADMINISTRATOR OR AUTHORIZED USER TO RESTRICT THE
NUMBER OF PREMISE HITS THAT POPULATE THE MDC SCREEN.
THIS IS TO MINIMIZE INFORMATION THE MDC USER HAS TO
REVIEW.
3-6.1 (33) PREMISE AND HAZARD DETAILS AVAILABLE TO THE MDC USER
SHALL MATCH THAT OF WHAT A DISPATCHER OR CALL-TAKER
SEES.
3-6.1 (34) THE PROPOSED MOBILE DATA INTERFACE SHALL ROUTE
MESSAGES FROM THE MDC EQUIPPED UNITS TO THE FOLLOWING:
3-6.1 (34.1) ANOTHER MDC (TERMINAL NAME),
3-6.1 (34.2) ANOTHER WORKSTATION (TERMINAL NAME),
3-6.1 (34.3) A SPECIFIC USER (VIA PERSONNEL NUMBER),
3-6.1 (34.4) A USER DEFINED GROUP OF INDIVIDUALS I.E. ALL DISPATCHERS,
3-6.1 (34.5) TO A PATROL/FIRE AREA,
3-6.1 (34.6) TO ALL OFFICERS ON AN INCIDENT (VIA INCIDENT NUMBER),
3-6.1 (34.7) OR TO A SYSTEM PRINTER.
3-6.1 (35) THE PROPOSED APPLICATION SHALL INCLUDE A METHOD OF
REPLYING TO A MESSAGE SENT BY ANY OF THE ABOVE LISTED
GROUPS/UNITS
3-6.1 (35.1) THE USER SHALL HAVE THE OPTION OF INCLUDING THE
ORIGINAL MESSAGE IN THE REPLY.
3-6.1 (36) THE PROPOSED APPLICATION SHALL INCLUDE A METHOD OF
FORWARDING MESSAGES TO THE ABOVE LISTED GROUPS/UNITS
3-6.1 (37) THE PROPOSED APPLICATION SHALL PROVIDE AN AUDIBLE AND
VISUAL ALERT TO NOTIFY THE USER OF AN INCOMING MESSAGE.
3-6.1 (37.1) THE VISUAL ALERT SHALL BE OBVIOUS, BUT NOT OBTRUSIVE TO
THE USER AND SHALL NOT IMPEDE ANY OTHER WORK BEING
DONE BY THE USER UPON RECEIPT.
3-6.1 (37.2) THE VISUAL AND AUDIBLE ALERTS SHALL BE CONFIGURABLE BY
THE USER.
3-6.1 (38) THE CAD APPLICATION SHALL PROVIDE A POSITIVE RESPONSE TO
THE MDC USER TO ALL MESSAGES AND COMMANDS RECEIVED
City of Fort Collins clxviii Proposal P-847
FROM AN MDC USER. I.E. CONFIRMATION THAT A COMMAND SUCH
AS “EN ROUTE” HAS BEEN ACCEPTED BY THE SYSTEM.
3-6.1 (39) THE PROPOSED APPLICATION SHALL ALLOW OFFICERS TO RESET
UNIT CONTACT TIMERS.
3-6.1 (39.1) THIS FUNCTION SHALL BE PREFORMED FROM THE COMMAND
LINE.
3-7 MAPPING AND GEOFILE FUNCTIONS
3-7.1 GENERAL REQUIREMENTS
3-7.1 (1) THE PROPOSED APPLICATION SHALL UTILIZE A GEOGRAPHIC
INFORMATION SYSTEM WHICH MEETS THE REQUIREMENTS LISTED
IN SECTION 2.
3-7.1 (2) THE PROPOSED APPLICATION SHALL ALSO USE THE COORDINATE-
BASED GEOFILE TO DETERMINE IF:
3-7.1 (2.1) THERE ARE DUPLICATE CALLS WITHIN A USER-DEFINED RADIUS
OF THE NEW CALL,
3-7.1 (2.2) AND THERE ARE PREMISE OR HAZARD RECORDS WITHIN A USER-
DEFINED RADIUS OF THE NEW CALL.
3-7.1 (3) THE PROPOSED APPLICATION SHALL HAVE THE ABILITY TO
RECEIVE AND ACCEPT GEOGRAPHIC COORDINATES FROM A
CELLULAR TELEPHONE CARRIER AND DISPLAY THE LOCATION OF
A CELLULAR CALLER ON A MAP (PHASE 2 WIRELESS).
3-7.2 MAP DISPLAY
3-7.2 (1) THE PROPOSED MAP APPLICATION SHALL ALLOW THE USER TO
TURN LAYERS OF THE MAP ON AND OFF AS NEEDED.
3-7.2 (2) THE MAP DISPLAY SHALL HAVE THE ABILITY TO RUN AS A WINDOW
ON THE SAME MONITOR AS THE STATUS DISPLAY OR ON A THIRD
MONITOR.
3-7.2 (3) THE PROPOSED MAP DISPLAY APPLICATION SHALL BE CAPABLE OF
REDRAWING QUICKLY ENOUGH SUCH THAT NEITHER THE USER OR
THE CAD APPLICATION HAS AN APPRECIABLE WAIT WHILE THE
MAP REDRAWS (APPRECIABLE WAIT IS DEFINED AS 5 SECONDS OR
MORE).
3-7.2 (4) THE PROPOSED APPLICATION SHALL INCLUDE A MAPPING DISPLAY
APPLICATION WHICH SHOWS THE LOCATION OF AN INCOMING 911
City of Fort Collins clxix Proposal P-847
CALL BASED ON THE ALI INFORMATION SUPPLIED BY THE
TELEPHONE COMPANY.
3-7.2 (5) THE MAPPING SYSTEM SHALL GENERALLY PROVIDE A GRAPHICAL
REPRESENTATION OF THE UNIT AND EVENT STATUS MONITORS
OVERLAID ON ANY MAPS DISPLAYED.
3-7.2 (6) THE PROPOSED APPLICATION SHALL BE CAPABLE OF DISPLAYING
A MAP WHICH SHOWS:
3-7.2 (6.1) THE LOCATION OF ACTIVE CALLS FOR SERVICE,
3-7.2 (6.2) THE LAST RECORDED LOCATION OF ALL UNITS,
3-7.2 (6.3) THE LOCATION OF AVL EQUIPPED UNITS,
3-7.2 (6.4) AND THE LOCATION OF PENDING CALLS FOR SERVICE.
3-7.2 (7) THE MAPPING SYSTEM SHALL DISPLAY SYMBOLS ON THE MAP FOR
EACH UNIT CONTROLLED BY THE CAD SYSTEM REGARDLESS OF
JURISDICTION.
3-7.2 (8) EACH USER SHALL BE ABLE TO IDENTIFY WHICH UNITS THE USER
VIEWS UP TO ALL UNITS CONTROLLED BY THE CAD SYSTEM.
3-7.2 (9) THE MAPPING SYSTEM SHALL DISPLAY SYMBOLS ON THE MAP FOR
EACH ACTIVE OR PENDING EVENT.
3-7.2 (10) EACH USER SHALL BE ABLE TO IDENTIFY WHICH INCIDENTS THE
USER VIEWS UP TO ALL INCIDENTS FOR ALL JURISDICTIONS
CONTROLLED BY THE CAD SYSTEM.
3-7.2 (11) THE MAP SYMBOLS SHALL UTILIZE COLORS WHICH ARE
CONSISTENT WITH THOSE UTILIZED BY THE STATUS DISPLAYS;
E.G., PENDING OR ACTIVE FOR EVENTS, ON-SCENE OR EN ROUTE
FOR UNITS, ETC.
3-7.2 (12) THE PARTICIPATING AGENCIES WILL GIVE PREFERENCE TO
SOLUTIONS WHICH DURING THE EVENT ENTRY PROCESS ZOOM
THE MAP TO A USER-DEFINED LEVEL AND DISPLAY A SYMBOL ON
THE MAP SHOWING THE LOCATION OF THE ADDRESS OF THE
CALLING PARTY AS REPORTED BY THE 9-1-1 OR CALLER ID SYSTEM.
3-7.2 (13) THE MAP DISPLAY SHALL ZOOM TO A USER-DEFINED LEVEL EACH
TIME AN EVENT RECORD IS SELECTED FOR REVIEW, CENTERING
ON THE EVENT LOCATION.
City of Fort Collins clxx Proposal P-847
3-7.2 (14) IT IS PREFERRED THAT THE MAP DISPLAY SHALL ALLOW FOR
DIFFERENT LEVELS OF ZOOMS BASED UPON INCIDENT TYPE; E.G.,
BROADER MAP AREA FOR CHASE.
3-7.2 (15) THE OPERATOR SHALL HAVE THE ABILITY TO ENTER AN ADDRESS
AND HAVE THE MAP ZOOM IN TO SHOW THAT ADDRESS. THIS WILL
BE ACCOMPLISHED EITHER FROM THE CAD COMMAND LINE OR
FROM THE MAPPING SYSTEM ITSELF.
3-7.2 (16) IT IS PREFERRED THAT THE PROPOSED APPLICATION ALLOW FOR
MAP MANIPULATION THROUGH AS MANY METHODS AS POSSIBLE;
I.E. FUNCTION KEY, POINTING DEVICE, COMMAND, OR GRAPHIC
COMMAND BUTTON.
3-7.2 (17) THE PROPOSED APPLICATION SHALL ALLOW THE USER TO
CONFIGURE THE DEFAULT MAP VIEWS FOR EACH WORKSTATION.
THESE VIEWS SHALL BE ATTACHED TO USER LOG-ON’S.
3-7.2 (18) THE MAP SHALL RETURN TO THE DEFAULT VIEW AFTER A USER-
DEFINED PERIOD OF TIME SUBSEQUENT TO A ZOOM INDUCED BY
AN EVENT RECORD REVIEW, LOCATION VERIFICATION OR USER
DIRECTED ZOOM.
3-7.2 (19) THE PROPOSED APPLICATION SHALL PROVIDE A FEATURE THAT
ALLOWS THE MAPPING DISPLAY SYSTEM TO HAVE THE ABILITY TO
CALCULATE THE FOLLOWING BETWEEN ANY TWO USER SELECTED
LOCATIONS OR SYSTEM SELECTED POINTS (AVL/CELL CALL DATA
ETC.) ON THE MAP BOTH UPON CALL ENTRY AND ON DEMAND:
3-7.2 (19.1) ROUTE WITH THE SHORTEST DISTANCE.
3-7.2 (19.2) ROUTE WITH THE SHORTEST TRAVEL TIME.
3-7.2 (20) THE GEOFILE SHALL HAVE THE ABILITY TO CAPTURE ALL
NECESSARY STREET ATTRIBUTES TO ACCOMPLISH THE
CALCULATION OF SHORTEST TRAVEL TIME.
3-8 SYSTEM ADMINISTRATION FUNCTIONS
3-8.1 DEFAULT AND RESTRICTED VALUES
3-8.1 (1) THE CAD SYSTEM SHALL ALLOW THE SYSTEM ADMINISTRATOR OR
AUTHORIZED USER TO ENTER “DEFAULT” VALUES IN EACH OF THE
FOLLOWING FIELDS:
3-8.1 (1.1) THE STATE FIELD ON ANY FORM,
3-8.1 (1.2) THE CITY FIELD ON ANY FORM,
City of Fort Collins clxxi Proposal P-847
3-8.1 (1.3) THE DATE FIELD ON ANY FORM (CURRENT DATE),
3-8.1 (1.4) THE TIME FIELD ON ANY FORM (CURRENT TIME),
3-8.1 (1.5) THE USER ID FIELD ON ANY FORM (LOGGED ON USER),
3-8.1 (1.6) OR THE WORKSTATION ID FIELD ON ANY FORM (WORKSTATION
INITIATING TRANSACTION).
3-8.1 (2) THE PROPOSED APPLICATION SHALL ALLOW THE SYSTEM
ADMINISTRATOR OR AUTHORIZED USER TO DEFINE THE
ACCEPTABLE VALUES FOR ANY FIELD.
3-8.1 (3) THE PROPOSED APPLICATION SHALL ALLOW THE SYSTEM
ADMINISTRATOR OR AUTHORIZED USER TO SET A DEFAULT TIME
PERIOD FOR SCHEDULED EVENTS SUCH THAT THE SCHEDULED
EVENT WILL APPEAR IN THE PENDING EVENT QUEUE FOR THE
APPROPRIATE DISPATCHER (XXX) MINUTES PRIOR TO THE
ORIGINAL TIME THAT THE EVENT WAS SCHEDULED.
3-8.1 (3.1) THE DEFAULT TIME FIELD SHALL BE AT LEAST THREE DIGITS
AND SHALL BE MEASURED IN MINUTES.
3-8.1 (4) THE SYSTEM ADMINISTRATOR OR AUTHORIZED USER SHALL HAVE
THE ABILITY TO RETRIEVE PREMISE RECORDS BASED ON THEIR
EXPIRATION DATE SO THAT THEY CAN BE RENEWED OR PURGED AS
APPROPRIATE. THIS SHALL BE AN AUTOMATIC REPORT
GENERATED BY THE SYSTEM BASED ON EXPIRATION DATES.
3-8.1 (5) THE PROPOSED APPLICATION SHALL SUPPORT AN AUTO-PURGE
FUNCTION FOR HAZARD RECORDS WHEN THEY REACH THEIR
EXPIRATION DATE.
3-8.1 (5.1) THE APPLICATION SHALL THEN SEND, VIA E-MAIL MESSAGE, A
FORM TO THE USER THAT ENTERED THE RECORD, THAT IT HAS
BEEN PURGED, GIVING THE USER THE CHANCE TO RE-ENTER IF
THE RECORD IS STILL VALID.
3-8.1 (6) THE PROPOSED APPLICATION SHALL SUPPORT USER-DEFINED
EVENT DISPOSITIONS OF, AT MINIMUM, 6 ALPHANUMERIC
CHARACTERS.
3-8.1 (7) THE SYSTEM ADMINISTRATOR OR AUTHORIZED USER SHALL BE
ABLE TO DETERMINE WHICH EVENTS REQUIRE A DISPOSITION
BEFORE THEY CAN BE CLOSED.
3-8.1 (8) THE SYSTEM ADMINISTRATOR OR AUTHORIZED USER SHOULD
HAVE THE ABILITY TO CONSTRUCT QUERY MASKS FOR OUTSIDE
City of Fort Collins clxxii Proposal P-847
INTERFACES INCLUDING BUT NOT LIMITED TO
CCIC/NCIC/DOR/DMV DATABASES.
3-8.2 GENERAL INQUIRY REQUIREMENTS
3-8.2 (1) THE PROPOSED APPLICATION SHALL OFFER A SINGLE FORM FOR
ENTERING THE FOLLOWING INQUIRIES TO CCIC AND OTHER
SYSTEMS FOR REGISTRATION, WANTED, STOLEN OR OTHER
INFORMATION. THE FORM SHALL INCLUDE ALL FIELDS FOR THE
FOLLOWING QUERIES:
3-8.2 (1.1) DRIVERS LICENSE QUERY,
3-8.2 (1.2) VEHICLE REGISTRATION QUERY BY LICENSE PLATE NUMBER OR
VIN,
3-8.2 (1.3) AND STOLEN ARTICLE QUERY.
3-8.2 (2) THE PROPOSED APPLICATION SHALL ALLOW THE USER TO ADD
THE ENTIRE TEXT OF ANY INQUIRY RETURN OR MESSAGE FROM
CCIC TO A CAD EVENT RECORD BY THE USE OF A SIMPLE
COMMAND OR ACTION.
3-8.2 (3) WHEN SUFFICIENT INFORMATION IS ENTERED ON A VEHICLE OR
PERSON STOP PROPOSED APPLICATION SHALL AUTOMATICALLY
QUERY TO THE FOLLOWING SYSTEMS FOR REGISTRATION, STOLEN
OR WANTED INFORMATION:
3-8.2 (3.1) CCIC/NLETS/NCIC,
3-8.2 (3.2) DOR/DMV,
3-8.2 (3.3) AND LOCAL (SYSTEM) RMS/JMS,
3-8.2 (4) WHEN A VEHICLE, BOAT, PERSON, ARTICLE OR GUN INQUIRY IS
INITIATED THE PROPOSED APPLICATION SHALL ALSO CHECK THE
CAD DATABASE FOR PREVIOUS INVOLVEMENT. FOR EXAMPLE,
NAMES SHALL BE CHECKED FOR PAST INVOLVEMENT AS A
COMPLAINANT OR SUSPECT; LICENSE PLATES SHALL BE CHECKED
FOR PREVIOUS INVOLVEMENT AS SUSPECT, STOLEN OR TOWED
VEHICLES.
3-8.2 (5) THE PROPOSED APPLICATION SHALL AUTOMATICALLY FORMAT
AND SEND INQUIRIES TO THE APPROPRIATE DATABASE(S) UNDER
THE FOLLOWING CIRCUMSTANCES:
3-8.2 (5.1) UPON THE ENTRY OF A VEHICLE CONTACT WHICH INCLUDES A
LICENSE PLATE NUMBER AND STATE OF ISSUE (DEFAULT VALUE),
City of Fort Collins clxxiii Proposal P-847
3-8.2 (5.2) UPON THE ENTRY OF A SUBJECT STOP WHICH INCLUDES NAME,
AND DOB INFORMATION,
3-8.2 (5.3) AND UPON THE ENTRY OF A TOWED/IMPOUNDED VEHICLE, BOAT,
TRAILER OR OTHER LICENSED OBJECT.
3-9 REPORTS AND SEARCH FUNCTIONS
The CAD system must provide a variety of management information reports. A
standardized set of management reports shall be provided, which will be used to analyze
the occurrence of events by unit ID, area of assignment, shift, type, geographic area, time
of day and day of week, call source and to examine the average response times. Although
most reports will be routine, the proposed application must also provide an ad-hoc report
writer that will enable non-technical authorized users to easily define, save, and share
custom reports created from any database included in the proposed application.
3-9.1 GENERAL REQUIREMENTS AND REPORTS
3-9.1 (1) THE PROPOSED APPLICATION SHALL ALLOW A USER TO SEARCH,
WITH THE USE OF WILDCARDS, ON ANY FIELD OR COMBINATION
OF FIELDS INCLUDING BUT NOT LIMITED TO:
3-9.1 (1.1) INCIDENT NUMBER,
3-9.1 (1.2) CASE (REPORT) NUMBER,
3-9.1 (1.3) DATE/TIME RANGES,
3-9.1 (1.4) JURISDICTION,
3-9.1 (1.5) CALL-TYPE,
3-9.1 (1.6) MAP PAGE,
3-9.1 (1.7) POLICE, FIRE AND/OR AMBULANCE BEAT/AREA/REPORTING
DISTRICT,
3-9.1 (1.8) PRIMARY UNIT,
3-9.1 (1.9) UNIT/DISPATCHER THAT ENTERED THE INCIDENT,
3-9.1 (1.10) DISPOSITION,
3-9.1 (1.11) ADDRESS (SHALL UTILIZE ADDRESS VERIFICATION),
3-9.1 (1.12) LOCATION,
3-9.1 (1.13) OR COMMONPLACE.
City of Fort Collins clxxiv Proposal P-847
3-9.1 (2) SEARCHES SHALL RETRIEVE INFORMATION PERTINENT TO THE
FIELD TYPE FROM ALL FORMS IN THE CAD APPLICATION. FOR
EXAMPLE IF THE USER QUERIES THE NAME ROBERT SMITH AND
MR. SMITH APPEARS AS A REPORTING PERSON ON ONE INCIDENT
AND A SUSPECT ON ANOTHER INCIDENT THE APPLICATION SHALL
RETURN BOTH INSTANCES.
3-9.1 (3) AT A MINIMUM ALL STANDARD REPORTS WILL CONTAIN THE
FOLLOWING FIELDS:
3-9.1 (3.1) REPORT HEADER WITH DEPARTMENT NAME,
3-9.1 (3.2) DATE REPORT WAS PRINTED,
3-9.1 (3.3) DATE AND TIME RANGE FOR THE CONTENTS OF THE REPORT,
3-9.1 (3.4) PAGE NUMBER,
3-9.1 (3.5) SPECIFIED SEARCH PARAMETERS (E.G. DISTRICT, UNIT ID, ETC.),
3-9.1 (3.6) AND REPORT REQUESTOR’S NAME.
3-9.1 (4) THE PROPOSED APPLICATION SHOULD HAVE THE ABILITY TO
SCHEDULE NAMED REPORTS FOR PRINTING:
3-9.1 (4.1) ON A SPECIFIC TIME AND DATE,
3-9.1 (4.2) OR ON A PERIODIC BASIS.
3-9.1 (5) THE PROPOSED APPLICATION SHALL INCLUDE A PREMISE
RECORDS REPORT WHICH ALLOWS THE USER TO VIEW PREMISE
RECORDS WHICH ARE DUE TO EXPIRE DURING USER-DEFINED
DATE RANGE.
3-9.1 (6) THE PROPOSED APPLICATION MUST BE ABLE TO PRINT A REPORT
ON COMMAND OF THE CURRENT UNIT AND EVENT STATUSES.
3-9.2 EVENT RELATED REPORTS
3-9.2 (1) THE PROPOSED CAD SYSTEM SHOULD INCLUDE THE FOLLOWING
EVENT REPORTS:
3-9.2 (1.1) EVENTS BY TYPE FOR A SPECIFIC DATE OR DATE RANGE,
3-9.2 (1.2) EVENTS BY TYPE AND DAY OF WEEK FOR A GIVEN DATE RANGE,
3-9.2 (1.3) EVENTS BY TYPE, AND DAY OF WEEK, SORTED BY DISTRICT,
LOCATION OR OTHER GEO-FILE SUPPORTED ZONE, FOR A GIVEN
DATE RANGE,
City of Fort Collins clxxv Proposal P-847
3-9.2 (1.4) EVENTS FOR A GIVEN DATE RANGE SUBTOTALED BY EVENT
TYPE,
3-9.2 (1.5) EVENTS FOR A GIVEN DATE RANGE SUBTOTALED BY CALL
SOURCE,
3-9.2 (1.6) ALL EVENTS BY ADDRESS, DISTRICT, LOCATION OR GEO-FILE
SUPPORTED GEOGRAPHIC AREA DURING A USER DEFINED DATE
AND TIME RANGE,
3-9.2 (1.7) ALL EVENTS BY POLICE, FIRE AND/OR AMBULANCE DISTRICT
DURING A USER DEFINED DATE AND TIME RANGE,
3-9.2 (1.8) TOTAL EVENT ACTIVITY OCCURRING IN A GIVEN POLICE, FIRE
AND/OR AMBULANCE DISTRICT ZONE DURING A USER DEFINED
TIME AND DATE RANGE,
3-9.2 (1.9) AVERAGE EVENT PROCESSING TIME SORTED AND TOTALED BY
EVENT PRIORITY,
3-9.2 (1.10) AVERAGE EVENT PROCESSING TIME SORTED AND TOTALED BY
EVENT TYPE,
3-9.2 (1.11) AVERAGE EVENT PROCESSING TIME FOR A SPECIFIC
COMMUNICATIONS EMPLOYEE BY EVENT PRIORITY,
3-9.2 (1.12) AVERAGE EVENT PROCESSING TIME FOR A GROUP OF
COMMUNICATIONS EMPLOYEES BY EVENT PRIORITY,
3-9.2 (1.13) EVENT AUDIT REPORT WHICH SHALL SHOW EVERY
TRANSACTION RECORDED TO A SPECIFIC EVENT IN
CHRONOLOGICAL ORDER,
3-9.2 (1.14) EVENT SUMMARY REPORT WHICH SHALL INCLUDE THE DATE,
TIME OF RECEIPT AND DISPATCH, LOCATION, EVENT TYPE AND
PRIORITY, CALL TAKER AND DISPATCHER ID, PRIMARY AND
BACKUP UNITS, DISPOSITION, AND EVENT CLOSE TIME FOR A
GIVEN EVENT NUMBER,
3-9.2 (1.15) DISPOSITION REPORTS WHICH DETAIL THE DISPOSITION FOR
ALL EVENTS IN A GIVEN PATROL, FIRE AND/OR AMBULANCE
DISTRICT FOR A GIVEN DATE RANGE,
3-9.2 (1.16) A REPORT SHOWING ALL EVENTS FOR WHICH THE EVENT TYPE
WAS CHANGED AT LEAST ONCE. THIS REPORT SHALL INCLUDE
THE ORIGINAL CLASSIFICATION AND ANY SUBSEQUENT
CLASSIFICATIONS. EVENTS SHALL BE IDENTIFIED BY EVENT
NUMBER AND LOCATION,
City of Fort Collins clxxvi Proposal P-847
3-9.2 (1.17) AND A “HOT SPOT” REPORT, WHICH DETAILS ALL EVENT
LOCATIONS WHICH EXCEED A USER-DEFINED NUMBER OF
EVENTS FOR A USER-DEFINED DATE AND TIME INTERVAL.
3-9.2 (2) RESPONSE TIME COMPLIANCE: USER-DEFINED “EMERGENCY” OR
“NON-EMERGENCY” AND “DISTRICT” OR “ZONE” DISPLAY WILL BE
AVAILABLE FOR CALL UP OR PRINTOUT AND WILL SHOW RESPONSE
TIME COMPLIANCE FOR A DATE RANGE. CUMULATIVE FRACTAL
DISTRIBUTION RESPONSE TIME (SEE EXAMPLE):
Emergency Calls / Zone / Date Range
N = 800 Time Fractal %
27 < 1 min 3.4%
100 <2 min 15.9%
200 < 3 min 40.9%
200 < 4 min 65.6%
200 < 5 min 90.1%
73 < 6 min 100.0%
3-9.2 (2.1) PROBLEM/SOLUTION MAPS: GRAPHICAL DISPLAY OF USER-
DEFINED CALL TYPES INPUT OF PRIORITY DISPATCH CODES
(EMERGENCY / NON-EMERGENCY), DATE RANGE, AND RESPONSE
TIME PARAMETERS): A GEOGRAPHIC DISPLAY SHOWING THE
LOCATIONS OF PROBLEM CALLS BY HOUR-OF-DAY, DAY-OF-
WEEK.
3-9.2 (2.2) DEMAND ANALYSIS: PEAK DEMAND BY DATE RANGE, HOUR-OF-
DAY, AND DAY-OF-WEEK-GRAPHIC, NUMERIC, AND CHART
3-9.2 (2.3) STATISTICS BY DATE RANGE: NUMBER OF CALLS, CALL TYPES BY
NUMBER AND % OF TOTAL.
3-9.2 (2.4) RECORDS FINDER: LIST OF AMBULANCE INCIDENTS AND RUN
NUMBERS BY DATE RANGE; LISTING CALL TYPE, DISPATCH TIME,
INCIDENT LOCATION, PATIENT NAME, DESTINATION, CREW
NAMES, UNIT ID NUMBERS.
3-9.3 UNIT AND EMPLOYEE RELATED REPORTS
3-9.3 (1) SINGLE UNIT ACTIVITY, INCLUDING CALLS FOR SERVICE AND
OTHER NON-EVENT RELATED ACTIVITIES, FOR A USER-DEFINED
TIME PERIOD, SHIFT, OR ASSIGNED AREA.
City of Fort Collins clxxvii Proposal P-847
3-9.3 (2) SINGLE EMPLOYEE ACTIVITY, INCLUDING CALLS FOR SERVICE
AND OTHER NON-EVENT RELATED ACTIVITIES, FOR A USER-
DEFINED TIME PERIOD OR SHIFT.
3-9.3 (3) SINGLE EMPLOYEE ACTIVITY OR EVENTS BY TYPE AND USER-
DEFINED DATE/TIME RANGE.
3-9.3 (4) SINGLE EMPLOYEE ACTIVITY BY LOCATION OR GRID DURING A
USER DEFINED DATE AND TIME RANGE.
3-9.3 (5) ADDRESS OVERRIDES BY USER-DEFINED EMPLOYEE DURING A
USER-DEFINED DATE AND TIME RANGE.
3-9.3 (6) ROSTER REPORT WHICH INCLUDES ALL PERSONNEL, UNITS AND
DISTRICTS TO WHICH THEY ARE ASSIGNED FOR A GIVEN DATE AND
SHIFT.
3-9.3 (7) IF THE ROSTER REPORT IS NOT FOR THE CURRENT SHIFT IT SHALL
INCLUDE THE ON-DUTY AND OFF-DUTY TIME FOR EACH EMPLOYEE
AND UNIT ASSIGNMENT CHANGES DURING THE SHIFT, IF ANY.
3-9.3 (8) A REPORT SHALL DETAIL THE ON-DUTY, OFF-DUTY TIMES, ELAPSED
TIME AND ASSIGNMENT FOR A GIVEN EMPLOYEE DURING A GIVEN
DATE AND TIME RANGE.
3-9.3 (9) A REPORT SHALL PROVIDE A STATISTICAL SUMMARY OF THE
HOURS WORKED BY ALL EMPLOYEES DURING A GIVEN TIME AND
DATE RANGE, SORTED AND SUB-TOTALED BY SHIFT OR
ORGANIZATIONAL ELEMENT.
3-9.3 (10) IT IS PREFERRED THAT THE SYSTEM BE CAPABLE OF CREATING A
REPORT WHICH SHOWS THE RECORDED LOCATION AND STATUS OF
ALL UNITS AND EVENTS AT PARTICULAR DATE AND TIME.
3-9.4 SEARCH FUNCTIONS
3-9.4 (1) THE PROPOSED APPLICATION SHALL ALLOW ACCESS TO A CAD
NAME INDEX AND OFFER A FORM OR OTHER DEVICE WHICH WILL
ALLOW A USER TO SEARCH THE CAD NAME INDEX FOR PRIOR CAD
INVOLVEMENT.
3-9.4 (2) THE PROPOSED APPLICATION SHALL PROVIDE SEARCH RESULTS
THAT INCLUDE AT A MINIMUM:
3-9.4 (2.1) RETURNS FROM CAD,
3-9.4 (2.2) AND RETURNS FROM THE RMS/JMS MNI.
City of Fort Collins clxxviii Proposal P-847
3-9.4 (3) THE PROPOSED APPLICATION SHALL PROVIDE A MEANS FOR
SEARCHING FOR BOLO’S.
3-9.4 (4) THE PROPOSED APPLICATION SHALL ALLOW THE FOLLOWING
FIELDS BE AVAILABLE AS SEARCH PARAMETERS FOR BOLO’S:
3-9.4 (4.1) DATE OR DATE RANGE/TIMES,
3-9.4 (4.2) SUMMARY OR TITLE,
3-9.4 (4.3) OFFENSE NATURE OR EVENT TYPE CODE,
3-9.4 (4.4) PERSONS NAMED ON BOLO,
3-9.4 (4.5) PHYSICAL DESCRIPTIONS,
3-9.4 (4.6) LICENSE PLATE NUMBERS INVOLVED,
3-9.4 (4.7) VEHICLE DESCRIPTIONS,
3-9.4 (4.8) POLICE DISTRICT,
3-9.4 (4.9) OTHER GEOGRAPHIC AREA SUPPORTED BY THE GEOFILE,
3-9.4 (4.10) FREE FORM TEXT SEARCH,
3-9.4 (4.11) OR REPORTING PARTY NAME.
3-9.4 (4.12) IT IS PREFERRED THAT THE FOLLOWING SEARCH CRITERIA BE
AVAILABLE:
3-9.4 (4.12.1) DATE OR DATE RANGE,
3-9.4 (4.12.2) SHIFT,
3-9.4 (4.12.3) DAY OF WEEK,
3-9.4 (4.12.4) VEHICLE OR UNIT NUMBER,
3-9.4 (4.12.5) AND POLICE, FIRE AND/OR AMBULANCE DISTRICT.
3-10 SECURITY FEATURES
3-10.1 AUDIT LOG
3-10.1 (1) THE PROPOSED APPLICATION MUST CREATE AND MAINTAIN AN
AUDIT TRAIL FOR EACH EVENT.
City of Fort Collins clxxix Proposal P-847
3-10.1 (1.1) THE SYSTEM WILL ARCHIVE THESE AUDIT LOGS FOR A
MINIMUM OF 12 MONTHS TIME.
3-10.1 (1.2) ALL AUDIT LOGS SHALL BE EASILY ACCESSIBLE FROM CAD
WORKSTATIONS AND MDC’S.
3-10.1 (2) THE PROPOSED APPLICATION SHALL CREATE AND MAINTAIN AN
AUDIT TRAIL FOR EACH UNIT.
3-10.1 (2.1) THE SYSTEM WILL MAINTAIN A HISTORY OF THESE AUDIT LOGS
FOR AT LEAST 12 MONTHS TIME.
3-10.1 (2.2) ALL AUDIT LOGS SHALL BE EASILY ACCESSIBLE FROM CAD
WORKSTATIONS AND MDC’S.
3-10.1 (2.3) THE AUDIT LOG SHALL RECORD EVERY TRANSACTION FOR AN
EVENT OR FIELD UNIT.
3-10.1 (3) THE PROPOSED APPLICATION SHALL PROVIDE A COMMAND FOR
DISPLAYING THE AUDIT TRAIL FOR ANY EVENT OR UNIT.
3-10.1 (4) IN EVERY CASE WHERE A CAD DATABASE RECORD, INCLUDING
NON-EVENT OR UNIT RECORDS, IS CREATED OR CHANGED THE
PROPOSED APPLICATION SHALL RECORD:
3-10.1 (4.1) THE TIME AND DATE OF THE CHANGE,
3-10.1 (4.2) THE USER MAKING THE CHANGE,
3-10.1 (4.3) THE WORKSTATION FROM WHICH THE CHANGE WAS MADE,
3-10.1 (4.4) THE ORIGINAL VALUE OF THE FIELD WHICH WAS CHANGED,
3-10.1 (4.5) AND THE NEW VALUE OF THE FIELD.
3-10.2 CAD MANAGEMENT INFORMATION SYSTEM
3-10.2 (1) THE PROPOSED APPLICATION SHALL OFFER A MANAGEMENT
INFORMATION SYSTEM MODULE FOR CAD.
3-10.2 (2) THE CAD MIS SHALL ALLOW THE SYSTEM ADMINISTRATOR OR
AUTHORIZED USER TO MANAGE:
3-10.2 (2.1) CAD CONFIGURATION FILES,
3-10.2 (2.2) PASSWORDS AND SECURITY TABLES,
3-10.2 (2.3) AND INTERFACES.
City of Fort Collins clxxx Proposal P-847
3-10.2 (3) THE CAD MIS SHALL MINIMALLY OFFER THE FOLLOWING
STANDARD REPORTS CONCERNING COMMUNICATIONS
OPERATIONS:
3-10.2 (3.1) A WORKLOAD STATISTICS SUMMARY REPORT WHICH
SUMMARIZES THE NUMBER OF CALLS FOR SERVICE HANDLED
DURING A GIVEN DATE RANGE, SUBTOTALED BY SHIFT WHICH
SHOWS THE AVERAGE PROCESSING TIME FOR ALL CALLS AND
BY CALL PRIORITY,
3-10.2 (3.2) A WORKLOAD STATISTICS DETAIL REPORT WHICH SHOWS THE
TOTAL CALLS FOR SERVICE HANDLED BY EACH EMPLOYEE
DURING A GIVEN TIME PERIOD, SUBTOTALED BY EVENT
PRIORITY AND SHOWING AVERAGE PROCESSING TIME BY
PRIORITY,
3-10.2 (3.3) AND AN INDIVIDUAL WORKLOAD REPORT WHICH SHOWS FOR A
GIVEN EMPLOYEE AND TIME PERIOD, THE TOTAL TIME SIGNED
ON TO CAD, THE TOTAL NUMBER OF CALLS FOR SERVICE
HANDLED BY CALLS ENTERED, CALLS DISPATCHED, AND CALLS
CHANGED OR SUPPLEMENTED.
3-10.3 PERSONNEL MODULE INTERFACE
3-10.3 (1) THE PROPOSED APPLICATION SHALL INCLUDE/INTERFACE WITH
THE SHARED PERSONNEL MODULE DESCRIBED IN SECTION 2 FOR
TRACKING INFORMATION RELATED TO EMPLOYEES WHO EITHER
INTERACT WITH THE CAD SYSTEM OR ARE RESOURCES TRACKED
BY IT.
3-10.3 (2) THE SHARED PERSONNEL MODULE SHALL HAVE PRIMACY OVER
THE CAD PERSONNEL DATABASE. THUS, CAD SHALL FIRST DRAW
PERSONNEL INFORMATION FROM THE SHARED SYSTEM AND
ALLOW THE USER TO ENTER ADDITIONAL INFORMATION AS
REQUIRED.
3-10.3 (3) THE PROPOSED CAD APPLICATION SHALL OBTAIN SPECIAL SKILLS
INFORMATION FROM THE SHARED PERSONNEL SYSTEM.
3-10.3 (4) THE PROPOSED CAD APPLICATION SHALL DRAW ON-DUTY
PERSONNEL INFORMATION FROM THE ROSTER FUNCTION OF THE
SHARED PERSONNEL SYSTEM.
3-10.3 (5) THE PROPOSED APPLICATION SHALL PROVIDE A SIMPLE MEANS
FOR A DISPATCHER OR OTHER AUTHORIZED EMPLOYEE TO
RECORD THE ON AND OFF DUTY TIME FOR A PARTICULAR
EMPLOYEE. NORMALLY THE SHIFT ROSTER WILL BE USED TO
RECORD SUCH TIMES. THIS FUNCTION WILL BE USED TO RECORD
City of Fort Collins clxxxi Proposal P-847
THE TIMES FOR EMPLOYEES WHO ARE NOT ASSIGNED TO A
PARTICULAR SHIFT, OR WHO ARRIVE LATER OR LEAVE EARLIER
THAN THE REST OF THEIR SHIFT.
3-11 OTHER CAD REQUIREMENTS
3-11.1 COMPUTER ASSISTED CAD TRAINING
3-11.1 (1) THE CAD SYSTEM SHALL INCLUDE A TRAINING SYSTEM WHICH
ALLOWS USERS TO ACCESS THE LIVE CAD DATABASES INCLUDING
THE GEO-FILE, UNIT TABLE, EVENT TABLE, HAZARD AND WARNING
FILES.
3-11.1 (2) USERS LOGGED ON TO THE TRAINING SYSTEM SHALL BE ABLE TO
SIMULATE THE ACTIONS OF ALL SYSTEM INTERFACES.
3-11.1 (3) USERS LOGGED ON TO THE TRAINING SYSTEM SHALL UTILIZE THE
SAME COMMANDS, FORMS AND SYSTEM FEATURES AS USERS
LOGGED ON TO THE LIVE CAD SYSTEM.
3-11.1 (4) NO DATA ENTERED OR COMMAND INVOKED WHILE LOGGED TO
THE TRAINING SYSTEM SHALL CORRUPT THE LIVE SYSTEM OR
NOTICEABLY IMPEDE THE PERFORMANCE OF THE LIVE SYSTEM.
3-11.1 (5) IT IS PREFERRED THAT THE PROPOSED APPLICATION PROVIDE AN
AUDIT TRAIL OF ALL ACTIONS TAKEN WHILE IN THE TRAINING
SYSTEM FOR POST-TRAINING REVIEW.
3-11.1 (6) ACCESSING THE TRAINING SYSTEM SHALL BE TIED TO USER LOG-
IN. IT SHALL REQUIRE NO OTHER INPUT FROM USER OR SYSTEM
ADMINISTRATOR TO BEGIN USING THE TRAINING MODE.
3-11.2 SCRATCH PAD
3-11.2 (1) IT WOULD BE PREFERRED THAT THE PROPOSED APPLICATION
OFFER A “SCRATCHPAD” OR OTHER MEANS OF STORING AND
RETRIEVING NOTES.
3-11.2 (2) IT IS PREFERRED THAT EACH USER BE ABLE TO STORE AND
RETRIEVE THEIR SCRATCHPAD NOTES INDIVIDUALLY.
3-11.3 ELECTRONIC MAIL AND MESSAGING FUNCTIONS
3-11.3 (1) THE PROPOSED APPLICATION SHALL ALLOW FOR SEPARATE CAD E-
MAIL AND MESSAGING FUNCTIONS.
3-11.3 (2) THE CAD SYSTEM SHALL INCORPORATE AN ELECTRONIC MAIL
SYSTEM WHICH ALLOWS USERS TO SEND AND RECEIVE MAIL
City of Fort Collins clxxxii Proposal P-847
MESSAGES TO ANOTHER CAD USER, NETWORKED CONNECTED
WORKSTATION, OR MOBILE COMPUTER.
3-11.3 (3) E-MAIL SHALL ALLOW FOR SYSTEM ADMINISTRATOR DEFINED E-
MAIL GROUPS. FOR EXAMPLE: 1 GROUP FOR DISPATCHERS ONLY, 1
GROUP FOR PATROL ONLY ETC.
3-11.3 (4) THE CAD SYSTEM SHALL ALLOW E-MAIL MESSAGES TO BE
ATTACHED TO THE CAD RECORD ON DEMAND.
3-11.3 (5) IF A USER IS NOT LOGGED ON TO THE SYSTEM WHEN THE MAIL
MESSAGE IS SENT THE APPLICATION WILL HOLD THE MESSAGE
UNTIL THE NEXT TIME THEY LOG ON.
3-11.3 (6) USERS SHALL BE ABLE TO SEND A MESSAGE TO:
3-11.3 (6.1) ONE OR MORE OFFICERS OR EMPLOYEES ID NUMBERS, IN
WHICH CASE THE APPLICATION WILL DETERMINE WHERE THE
ADDRESSEES ARE LOGGED ON AND ROUTE THE MESSAGE TO
THE APPROPRIATE WORKSTATIONS OR MDC’S,
3-11.3 (6.2) TO A PRE-DEFINED GROUP,
3-11.3 (6.3) TO A WORKSTATION,
3-11.3 (6.4) A CAD POSITION,
3-11.3 (6.5) A MOBILE DATA COMPUTER,
3-11.3 (6.6) TO AN INCIDENT NUMBER,
3-11.3 (6.7) OR TO A PRINTER.
3-11.3 (7) THE PROPOSED APPLICATION SHALL ALLOW EACH USER TO HAVE
A MAILBOX.
3-11.3 (8) THE SYSTEM ADMINISTRATOR OR AUTHORIZED USER WILL HAVE
THE ABILITY TO SET A MAXIMUM MAILBOX SIZE FOR EACH USER.
ONCE THE MAILBOX LIMIT HAS BEEN REACHED THE MAILBOX
WILL NO LONGER ACCEPT MESSAGES.
3-11.3 (9) THE MAILBOX WILL HOLD NEW MESSAGES, SENT MESSAGES AND
MESSAGES WHICH HAVE BEEN READ BUT WHICH HAVE NOT BEEN
DELETED.
3-11.3 (10) THE SYSTEM ADMINISTRATOR OR AUTHORIZED USER SHALL HAVE
THE CAPABILITY TO SET A TIME LIMIT FOR THE RETENTION OF
City of Fort Collins clxxxiii Proposal P-847
MESSAGES. WHEN A MESSAGE IS OLDER THAN THE TIME LIMIT IT
WILL BE AUTOMATICALLY PURGED.
3-11.3 (11) THE SYSTEM ADMINISTRATOR OR AUTHORIZED USER SHALL HAVE
THE ABILITY TO LOG ALL MESSAGES SENT IN THE CAD SYSTEM.
3-11.4 MEMOS/REMINDERS
3-11.4 (1) THE PROPOSED APPLICATION SHALL PROVIDE A MEMO FEATURE
TO ALLOW ALL USERS TO INPUT FREE-FORM REMINDER MESSAGES
TO POP UP AT A SELECTED DATE/TIME.
3-11.4 (2) THIS FEATURE SHALL ALLOW USERS TO ENTER A SINGLE MEMO TO
APPEAR ONE TIME, OR BE SCHEDULED TO APPEAR ON A REGULAR
BASIS—DAILY, WEEKLY, OR MONTHLY—FOR AN INDEFINITE
PERIOD OF TIME.
3-11.4 (3) THE FREE-TEXT FIELD SHOULD BE NO LESS THAN 200 CHARACTERS
IN LENGTH.
3-11.5 INFORMATION FILES
3-11.5 (1) THE PROPOSED APPLICATION SHALL INCORPORATE A SEPARATE
DATABASE THAT HOLDS MISCELLANEOUS INFORMATION
INCLUDING BUT NOT LIMITED TO PHONE NUMBERS, DOOR
COMBINATIONS, SPECIFIC PROCEDURES, ON-CALL LISTS, AND ANY
OTHER CONCEIVABLE BITS OF INFORMATION DEEMED NECESSARY.
3-11.5 (2) THIS DATABASE SHALL BE ACCESSIBLE BY ALL USERS FOR ENTRY
AND QUERY.
3-11.5 (3) THIS DATABASE SHALL BE SEARCHABLE BY KEY-WORDS AND
SHALL ALLOW SEARCHING BY “WILD-CARDS” ALL FROM THE
COMMAND LINE.
City of Fort Collins clxxxiv Proposal P-847
4 - RECORDS MANAGEMENT
4-1 SYSTEM DESIGN
4-1.1 GENERAL REQUIREMENTS AND DESIGN FEATURES
The Records Management Database shall be designed to operate as a component of a
comprehensive, fully integrated, multi-user, incident-based Public Safety System
Records Management System (RMS) and Jail Management System (JMS).
4-1.1 (1) THE PROPOSED RMS/JMS APPLICATION SHALL BE DESIGNED TO
SHARE INFORMATION LOGICALLY AND AUTOMATICALLY WITH
OTHER APPLICATIONS, SUCH AS CAD, FULL COURT JUSTICE
SYSTEMS, ETC.
4-1.1 (2) WHEN A USER SIGNS ON TO THE SYSTEM THE PROPOSED RECORDS
APPLICATION SHALL DISPLAY (AT PARTICIPATING AGENCIES
DISCRETION) A SUMMARY OR OTHERWISE INFORM THE USER OF:
4-1.1 (2.1) INCOMPLETE REPORTS FOR WHICH THE USER IS RESPONSIBLE,
4-1.1 (2.2) REPORTS WHICH HAVE BEEN RETURNED FOR CORRECTIONS OR
REVIEW FOR WHICH THE USER IS RESPONSIBLE,
4-1.1 (2.3) SCHEDULED REPORTS WHICH HAVE RUN SINCE THE USER’S LAST
LOGON,
4-1.1 (2.4) RETURNS FROM DELAYED INQUIRIES TO RMS/JMS, CBI, NCIC,
NLETS, AND OTHER RESOURCES,
4-1.1 (2.5) NEWLY ASSIGNED CASES FOR INVESTIGATIONS FOLLOW UP,
4-1.1 (2.6) RECORDS OF INTEREST (ROI) “HITS”,
4-1.1 (2.7) AND WAITING MESSAGES.
4-1.1 (3) THE PROPOSED RMS/JMS APPLICATION SHALL INCLUDE
EXTENSIVE “DRILL DOWN” SEARCH CAPABILITIES. FOR EXAMPLE,
IF A NAME SEARCH RETURNS FOUR POTENTIAL CANDIDATES THE
USER SHALL BE ABLE TO VIEW EACH RECORD BY SELECTING IT IN
SOME MANNER. IF THE RECORD DISPLAYED THEN HAD A CO-
DEFENDANT, THE USER WOULD BE ABLE TO SELECT THAT RECORD,
SEE THE CO-DEFENDANT RECORDS, IF THE CO-DEFENDANT HAD A
VEHICLE, THE USER WOULD BE ABLE TO SELECT THAT RECORD
AND SELL ALL PERSONS AND LOCATIONS ASSOCIATED WITH THAT
VEHICLE, AND SO ON.
City of Fort Collins clxxxv Proposal P-847
4-1.1 (4) THE PROPOSED APPLICATION SHALL HAVE THE ABILITY TO
RETRACE THE DRILL DOWN STEPS (STEP BY STEP) TO RETURN TO
ANY POINT OF THE DRILL DOWN AND THEN BRANCH IN A
DIFFERENT DIRECTION.
4-1.1 (5) ALL NARRATIVE FIELDS SHALL HAVE THE ABILITY TO ACCEPT NO
LESS THAN 32,000 CHARACTERS OF TEXT.
4-1.1 (6) THE PROPOSED RMS/JMS APPLICATION SHALL BE SIZED TO STORE
UP TO FIFTEEN YEARS OF DATA ON-LINE WITHOUT ADDING DISK
OR OTHER STORAGE DEVICES, MEMORY, OR ADDITIONAL
PROCESSORS.
4-1.1 (7) THE PROPOSED RMS/JMS APPLICATION SHALL SUPPORT SINGLE
POINT OF ENTRY OF DATA FOR ALL FORMS, REPORTS, AND OTHER
DATA ENTRY TASKS.
4-1.1 (8) THE PROPOSED APPLICATION SHALL ALLOW A USER TO RETRIEVE
A PREVIOUSLY SUBMITTED REPORT, CHANGE ONE OR MORE
FIELDS AND SAVE IT AS A NEW REPORT.
4-1.1 (8.1) THE PROPOSED APPLICATION SHALL PROVIDE A MEANS OF
MODIFYING THIS CLONED REPORT BY AUTOMATICALLY
INSERTING THE CAD DATA FOR THE NEW CASE (REPORT)
NUMBER.
4-1.1 (9) THE PROPOSED APPLICATION SHALL PROVIDE BASIC WORD
PROCESSING CAPABILITIES (WITHOUT SPAWNING A SEPARATE
WORD PROCESSOR) FOR ENTERING NARRATIVES AND
SUPPLEMENTAL REPORTS THAT SPECIFICALLY INCLUDES SPELL
CHECK AND THE CREATION OF TEMPLATES (ALL TEXT MUST BE
SEARCHABLE ON RMS/JMS USER QUERY).
4-1.1 (10) IT IS DESIRED THAT THE PROPOSED RECORDS APPLICATION TRACK
THE TIME REQUIRED TO COMPLETE EACH REPORT IN ORDER TO
FACILITATE MANAGEMENT REPORTING AND TO IDENTIFY PERSONS
WHO MAY REQUIRE ADDITIONAL TRAINING.
4-1.1 (11) THE PROPOSED APPLICATION SHALL ALLOW FOR THE USER TO
REQUEST TRANSLATION OF ANY CODE THAT HAS AN ASSOCIATED
ENTRY IN THE CODE TABLE BY ALLOWING THE USER TO SELECT
THE CODE IN SOME MANNER AND TO THEN HAVE A FULL TEXT
DESCRIPTION APPEAR IN SOME WAY.
4-1.1 (12) THE SYSTEM SHALL HAVE THE ABILITY TO ASSIGN SEQUENTIAL
CASE (REPORT) NUMBERS (NUMBERS UNIQUE TO EACH EVENT AND
EACH AGENCY) IN THE FORMAT DESCRIBED BELOW;
City of Fort Collins clxxxvi Proposal P-847
4-1.1 (12.1) ALPHA/NUMERIC,
4-1.1 (12.2) 10 CHARACTERS,
4-1.1 (12.3) IN THE FORMAT (YY)(AA)(NNNNNN) WHERE (YY) IS THE LAST
TWO DIGITS OF THE CURRENT YEAR, (AA) IS A TWO LETTER
CODE FOR THE REPORTING AGENCY, AND (NNNNNN) IS A SIX
DIGIT SEQUENTIAL NUMBER UNIQUE TO EACH AGENCY THAT
STARTS OVER EACH YEAR.
4-1.1 (13) THE NUMBERING SYSTEM SHALL BE DESIGNED TO ENSURE THAT
ALL CASES (REPORTS) RECEIVE A NUMBER, THAT NO NUMBERS
ARE OMITTED, AND THAT NO NUMBERS ARE DUPLICATED
(ANYWHERE IN THE SYSTEM).
4-1.1 (14) EACH RMS RECORD SHALL RECORD AND RETAIN THE INCIDENT
NUMBER ASSIGNED BY CAD.
4-1.1 (15) IT IS DESIRED THAT THE PROPOSED APPLICATION INCLUDE AS
MANY LABOR SAVING ROUTINES AS POSSIBLE. FOR EXAMPLE,
WHEN MULTIPLE PIECES OF PROPERTY ARE BEING ENTERED INTO
A REPORT BY ONE OFFICER THE OFFICER SHALL NOT HAVE TO
REENTER HIS/HER BADGE NUMBER FOR EACH ITEM, OR THE
LOCATION WHERE THE PROPERTY WAS FOUND OR SEIZED.
4-1.1 (16) THE PROPOSED APPLICATION SHALL HAVE A DEFINED FIELD TO
RECORD THE FACT THAT ONE OR MORE OF THE OFFICERS
INVOLVED IN THIS EVENT HAD TO USE PHYSICAL OR DEADLY
FORCE IN THE COURSE OF THE EVENT.
4-1.2 LOCATION AND NUMBER OF RMS/JMS CLIENTS
4-1.2 (1) LOCATION/DEFINITION (ALL CLIENTS MUST BE CAPABLE OF FULL
FUNCTIONALITY)
Location/Definition FCPS LCSO LPD EPPD CSUPD BPD Total
Communications 10 7 6 3 2 1 29
Records / Civil 16 27 12 2 3 1 61
Administrative Use 20 75 15 0 5 1 116
Patrol / Investigations 180 110 75 20 10 6 401
Crime Analysis 2 1 1 1 1 0 6
TOTAL 228 220 109 26 21 9 613
City of Fort Collins clxxxvii Proposal P-847
4-1.3 RMS PRINTING SERVICES
4-1.3 (1) THE PROPOSED RMS APPLICATION SHALL HAVE A "PUBLIC"
REPORT OPTION FOR EACH INCIDENT OR OTHER PUBLIC REPORT
SUCH THAT THE SYSTEM ADMINISTRATOR OR OTHER AUTHORIZED
USER CAN CHOOSE TO BLANK OUT (REDACT) CERTAIN FIELDS.
4-1.3 (1.1) THE PROPOSED RMS APPLICATION SHALL HAVE A "PUBLIC"
REPORT OPTION FOR EACH INCIDENT OR OTHER PUBLIC
REPORT SUCH THAT THE SYSTEM ADMINISTRATOR OR OTHER
AUTHORIZED USER CAN CHOOSE TO BLANK OUT (REDACT)
NARRATIVE WITH AN ON SCREEN TOOL
4-1.3 (1.2) THE PROPOSED RMS APPLICATION SHALL HAVE A "PUBLIC"
REPORT OPTION FOR EACH INCIDENT OR OTHER PUBLIC
REPORT SUCH THAT THE SYSTEM ADMINISTRATOR OR OTHER
AUTHORIZED USER CAN CHOOSE TO BLANK OUT (REDACT)
REPEATING NARRATIVE WITH AN (FIND AND REPLACE) ON
SCREEN TOOL.
4-1.3 (2) THE PROPOSED RMS APPLICATION SHALL OFFER ANY OFFICER,
INVESTIGATOR OR AUTHORIZED PERSON THE ABILITY TO PRINT:
4-1.3 (2.1) A SINGLE USER-SELECTED FORM, ACTIVITY, IMAGE, OR NOTE
FROM THE CASE (REPORT) FILE.
4-1.3 (2.2) THE ENTIRE CASE (REPORT) FILE, INCLUDING ALL FORMS,
NOTES, ACTIVITIES, IMAGES, ETC.
4-1.3 (2.3) A BROAD SCOPE PRINTOUT THAT COULD INCLUDE MULTIPLE
CASE REPORTS FOR WHICH THE SYSTEM ADMINISTRATOR OR
OTHER AUTHORIZED USER WILL BE ABLE TO DEFINE THE TYPES
OF FORMS, NOTES, IMAGES AND ACTIVITIES TO BE INCLUDED.
4-1.3 (2.4) A BROAD SCOPE PRINTOUT THAT COULD INCLUDE MULTIPLE
CASE REPORTS, WHICH INCLUDES FORMS, DEFINED BY THE
SYSTEM ADMINISTRATOR OR OTHER AUTHORIZED EMPLOYEE
AS BEING OF PUBLIC RECORD.
4-1.3 (3) THE PROPOSED RMS APPLICATION SHALL PROVIDE A MEANS OF
STORING THE ELECTRONIC SIGNATURE OF EACH EMPLOYEE SO
THAT WHEN A REPORT IS PRINTED HIS OR HER SIGNATURE WILL
APPEAR ON THE REPORT.
4-1.3 (4) THE PROPOSED RMS APPLICATION SHALL PROVIDE A MEANS OF
PRINTING AN ELECTRONIC INDICATOR SUCH AS “APPROVED BY
City of Fort Collins clxxxviii Proposal P-847
<OFFICER NAME>” TO INDICATE THAT THE REPORT HAS BEEN
PROCESSED AND APPROVED.
4-1.3 (5) THE PROPOSED RMS SYSTEM SHALL HAVE A CLEAR ON SCREEN
INDICATOR OF THE APPROVAL STATUS OF A REPORT.
4-1.3 (6) THE PROPOSED RMS APPLICATION SHALL PROVIDE A MEANS OF
CAPTURING AND STORING CITIZENS ELECTRONIC SIGNATURES
FOR RECEIPT OF DOCUMENTS AND/OR PROPERTY.
4-1.3 (7) THE PROPOSED RMS APPLICATION SHALL NOT ALLOW A PUBLIC
JACKET OR PUBLIC REPORT TO BE PRINTED BEFORE ALL REPORTS
ARE APPROVED.
4-1.3 (8) THE PROPOSED RMS APPLICATION SHALL HAVE THE ABILITY TO
PLACE OVERLAY “WATERMARKS” ON ANY OUTPUT WHEN AGENCY
DEFINED CONDITIONS EXIST (JUVENILES, SEX ASSAULT, NOT
APPROVED, RESTRICTED USE, ETC.)
4-1.3 (9) THE PROPOSED RMS APPLICATION SHALL ALLOW A
DISSEMINATION LOG OF ALL REPORTS PRINTED OR EMAILED. AT A
MINIMUM, THE LOG SHALL CAPTURE REQUIRE WHO PRINTED,
FAXED, OR EMAILED THE REPORT, WHO RECEIVED THE REPORT
(NAME, ADDRESS AND PHONE), AND THE REASON A REPORT WAS
PRINTED, FAXED, OR EMAILED.
4-1.3 (10) THE PROPOSED RMS APPLICATION SHALL PRINT THE
PARTICIPATING AGENCIES LOGO, ADDRESS, AND TELEPHONE
NUMBER ON ALL REPORTS PRINTED (AS DEFINED BY THE AGENCY).
4-1.3 (11) THE PROPOSED RMS APPLICATION SHALL PRINT MOTOR VEHICLE
ACCIDENT REPORTS TO LOOK LIKE THE STATE OF COLORADO
ACCIDENT REPORT FORMS.
4-1.3 (12) THE PROPOSED RMS APPLICATION SHALL HAVE THE ABILITY TO
DIRECT OUTPUT OF ANY INQUIRY OR REPORT TO:
4-1.3 (12.1) SCREEN (WORKSTATION),
4-1.3 (12.2) A NETWORK CONNECTED FAX MODEM,
4-1.3 (12.3) EMAIL AS AN ATTACHED .PDF FILE,
4-1.3 (12.4) ASCII TEXT FILE FORMAT, OR
4-1.3 (12.5) PRINTER.
City of Fort Collins clxxxix Proposal P-847
4-2 CASE REPORT ENTRY AND PROCESSING
4-2.1 GENERAL REQUIREMENTS
4-2.1 (1) THE PROPOSED RMS/JMS APPLICATION SHALL PROVIDE AN CLEAR
INDICATION OF CASES INVOLVING JUVENILE VICTIMS AND
SUSPECTS.
4-2.1 (2) THE PROPOSED RMS APPLICATION SHALL ALLOW THE SYSTEM
ADMINISTRATOR OR OTHER AUTHORIZED USER TO EXCLUDE
SPECIFIED SOME USERS FROM SEEING JUVENILE RECORDS ON MNI
INQUIRIES.
4-2.1 (3) THE PROPOSED RMS APPLICATION SHALL ALLOW A USER TO
BEGIN THE ENTRY OF A REPORT WITH ANY FORM. FOR EXAMPLE,
IT SHALL BE POSSIBLE FOR AN OFFICER TO COMPLETE A FIELD
INTERROGATION (FI) FORM FIRST, AND THEN UPON DETERMINING
THAT THE SUBJECT IS WANTED, USE THE INFORMATION ON THE FI
FORM TO COMPLETE THE ARREST AND OTHER NECESSARY
REPORTS.
4-2.1 (4) THE PROPOSED RMS APPLICATION SHALL INCLUDE THE ABILITY
FOR THE SYSTEM ADMINISTRATOR OR OTHER AUTHORIZED USER
TO DEFINE SPECIAL ENFORCEMENT ZONES SUCH AS SCHOOLS.
4-2.1 (5) IT IS PREFERRED THAT THE PROPOSED RMS/JMS APPLICATION
HAVE THE ABILITY FOR THE GEO FILE TO AUTO TRACK AND AUTO
POPULATE A SPECIAL ENFORCEMENT ZONE FIELD IN THE RMS/JMS.
4-2.1 (6) IF A CRIME IS REPORTED WITHIN A SPECIAL ENFORCEMENT ZONE
THE APPLICATION SHALL NOTIFY THE USER IN A DISTINCTIVE
FASHION.
4-2.1 (7) THE PROPOSED RMS APPLICATION SHALL ALLOW COPYING OR
MOVING OF DATA FROM ONE FIELD TO ANOTHER (WITH CUT &
PASTE FUNCTION) WITHOUT REENTRY.
4-2.2 CASE REPORT AND DATA ENTRY
The proposed RMS application shall allow an officer or other employee to complete the
remainder of a report initiated in CAD through the RMS module. To accomplish this,
the proposed RMS application shall have the ability to receive and display the
following initial incident data from the Computer Aided Dispatch (CAD) System:
4-2.2 (1.1) FINAL CALL TYPE
4-2.2 (1.2) DATE/TIME RECEIVED
City of Fort Collins cxc Proposal P-847
4-2.2 (1.3) LOCATION BY FULL STREET ADDRESS
4-2.2 (1.4) LOCATION BY X-Y COORDINATES
4-2.2 (1.5) LOCATION BY REPORTING DISTRICT
4-2.2 (1.6) LOCATION BY PATROL AREA
4-2.2 (1.7) LISTING OF ALL OFFICERS ASSIGNED
4-2.2 (1.8) LISTING OF ALL RELATED DISPOSITION CODES BY OFFICER
4-2.2 (2) IT IS PREFERRED THAT THE PROPOSED RMS APPLICATION PERMIT
AN EMPLOYEE TO BEGIN A NEW CASE REPORT DIRECTLY IN THE
RMS. UNDER THESE CIRCUMSTANCES RMS WOULD COMPLETE THE
FOLLOWING ACTIONS:
4-2.2 (2.1) CREATE A CAD INCIDENT CONTAINING THE BASIC CASE DETAILS
INCLUDING THE DATE, TIME, VERIFIED LOCATION, AND NATURE
OF THE INCIDENT, AND PRIMARY OFFICER'S IDENTIFICATION,
AND
4-2.2 (2.2) DRAW THE NEXT LOGICAL CASE (REPORT) NUMBER FROM THE
CAD SYSTEM.
4-2.2 (3) THE PROPOSED RMS APPLICATION SHALL ASSIGN A UNIQUE
SEQUENTIAL NUMBER SUBSERVIENT TO (UNDER) THE ORIGINAL
CASE (REPORT) NUMBER FOR EACH SUPPLEMENTAL
INVESTIGATIVE REPORT.
4-2.2 (4) THE PROPOSED RMS APPLICATION SHALL HAVE THE ABILITY TO
RECEIVE, STORE AND MANAGE DATA CONTAINED IN THE REPORT
FORMS INCLUDED IN THE APPENDIX.
4-2.2 (5) USERS SHALL BE ABLE TO INITIATE AND COMPLETE ALL REPORTS
AND FORMS FROM:
4-2.2 (5.1) A DESKTOP WORKSTATION CONNECTED TO THE RMS VIA A
LOCAL OR WIDE-AREA NETWORK,
4-2.2 (5.2) A MOBILE COMPUTER TERMINAL ATTACHED TO THE RMS VIA A
WIRELESS CONNECTION,
4-2.2 (5.3) A MOBILE COMPUTER TERMINAL RUNNING STAND ALONE (OFF-
LINE) WITH ONLY OCCASIONAL CONNECTIVITY TO THE RMS
4-2.2 (5.3.1) WHEN PROCESSING REPORTS ENTERED IN AN OFF-LINE MODE,
THE APPLICATION SHALL CHECK THE VALIDITY OF ALL
City of Fort Collins cxci Proposal P-847
FIELDS AND COMPLETE OTHER PROCESSING TASKS AS IF THE
REPORT WAS ENTERED FROM AN ON-LINE CLIENT.
4-2.2 (5.4) ANY COMPUTER WHICH SUPPORTS A BROWSER APPLICATION
AND WHICH HAS ACCESS TO THE DEPARTMENT'S LOCAL OR
WIDE AREA NETWORK.
4-2.2 (6) THE PROPOSED RMS APPLICATION SHALL LOG ALL NEW REPORTS,
INCLUDING SUPPLEMENTAL REPORTS, AS "UNAPPROVED" UNTIL
SUCH TIME AS THEY ARE APPROVED BY THE REPORTING
OFFICER'S SUPERVISOR.
4-2.2 (6.1) UNAPPROVED AND/OR INCOMPLETE REPORTS SHALL BE
PROMINENTLY MARKED AS SUCH WHETHER DISPLAYED ON-
SCREEN OR PRINTED (SUCH AS A WATERMARK).
4-2.2 (7) WHEN ALL REQUIRED FIELDS ON A REPORT HAVE BEEN
COMPLETED THE SYSTEM SHALL PROVIDE THE USER WITH A
DIALOG BOX OR OTHER MEANS TO ROUTE THE REPORT
ELECTRONICALLY TO THE NEXT PERSON IN AN AGENCY DEFINED
WORKFLOW PROCESS FOR REVIEW.
4-2.2 (8) THE PROPOSED RMS APPLICATION SHALL PROVIDE A MEANS OF
ROUTING A REPORT TO ANY OTHER PERSON IN THE RMS SUCH AS A
SUPERVISOR OR ANOTHER USER PRIOR TO COMPLETION OF THE
REPORT.
4-2.2 (9) THE PROPOSED RMS APPLICATION SHALL PROVIDE USERS WITH
THE ABILITY TO CAPTURE MUG SHOTS AND STORE THEM AS A
PART OF THE MNI.
4-2.2 (10) THE PROPOSED RMS APPLICATION SHALL PROVIDE USERS WITH
THE ABILITY TO CAPTURE OR UPLOAD PICTURES, SCANNED
IMAGES; SUCH AS PICTURES, DIAGRAMS AND WITNESS
STATEMENTS, OR ELECTRONIC FILES OF VARIOUS TYPES AND
STORE THEM WITH ANY RMS CASE RECORD.
4-2.2 (10.1) THE SYSTEM SHALL HAVE THE ABILITY TO LIMIT THE SIZE OF
ATTACHMENTS.
4-2.2 (11) THE PROPOSED RMS APPLICATION SHALL INCLUDE A REPORT
FORMAT FOR COLLECTING INFORMATION ON FIELD STOPS AND
INTERROGATIONS (CONTACT OR FIELD INTERVIEW CARDS).
4-2.2 (12) AT A MINIMUM, THE CONTACT CARD FORM SHALL CAPTURE THE
INFORMATION CONTAINED IN THE MNI, MLI, MVI, MUGSHOT
MODULE, & OFFENDER MODULE FOR EACH PERSON CONTACTED
AND;
City of Fort Collins cxcii Proposal P-847
4-2.2 (12.1) CLOTHING DESCRIPTION,
4-2.2 (12.2) NARRATIVE FOR COMMENTS AND PROBABLE CAUSE,
4-2.3 CASE REPORT PROCESSING
4-2.3 (1) THE PROPOSED RMS APPLICATION SHALL CHECK EACH
COMPLETED FIELD TO ENSURE:
4-2.3 (1.1) THAT THE USER HAS ENTERED A VALUE IN EACH MANDATORY
FIELD, AND
4-2.3 (1.2) THAT ENTRIES IN VALUE RESTRICTED FIELDS MATCH ONE OF
THE ACCEPTABLE VALUES FOR THAT FIELD.
4-2.3 (2) IF MANDATORY FIELDS HAVE NOT BEEN COMPLETED, THE
APPLICATION WILL DENOTE THE MISSING OR INCORRECT ENTRIES
IN A NOTICEABLE MANNER.
4-2.3 (3) THE PROPOSED RMS APPLICATION SHALL ALLOW A USER TO SAVE
A REPORT PRIOR TO COMPLETING ALL FIELDS OR WHEN ERRORS
ARE PRESENT, BUT THE APPLICATION WILL NOTIFY THE USER
THAT REQUIRED FIELDS HAVE NOT BEEN COMPLETED OR THE
REPORT CONTAINS ERRORS.
4-2.3 (4) THE PROPOSED RMS APPLICATION SHALL INCLUDE A TABLE THAT
SHALL ALLOW THE SYSTEM ADMINISTRATOR OR OTHER
AUTHORIZED USER TO DETERMINE WHICH REPORTS OR FORMS
MUST BE REVIEWED AND APPROVED BY A SUPERVISOR BEFORE
BEING COMMITTED TO THE DATABASE.
4-2.3 (5) THE PROPOSED RMS APPLICATION SHALL NOTIFY A SUPERVISOR
EACH TIME A REPORT REQUIRING REVIEW IS RECEIVED FROM A
USER UNDER THEIR COMMAND.
4-2.3 (6) THE PROPOSED RMS APPLICATION SHALL PROVIDE A COMMAND
FOR SUPERVISORS TO DISPLAY THE REPORTS WHICH ARE
AWAITING THEIR REVIEW.
4-2.3 (7) THE PROPOSED RMS APPLICATION SHALL:
4-2.3 (7.1) AUTOMATICALLY ROUTE COMPLETED REPORTS TO THE
SUPERVISOR DESIGNATED FOR THE OFFICER OR EMPLOYEE
WHO COMPLETES THE REPORT.
4-2.3 (7.2) AUTOMATICALLY ROUTE REVIEWED REPORTS REQUIRING
CORRECTIONS BACK TO THE INITIATING OFFICER OR STAFF
MEMBER.
City of Fort Collins cxciii Proposal P-847
4-2.3 (7.3) RETURN CORRECTED REPORTS TO THE SUPERVISOR FOR
REVIEW.
4-2.3 (7.4) MONITOR THE NUMBER OF TIMES A REPORT IS SUBMITTED AND
REVIEWED FOR EACH OFFICER IN ORDER TO IDENTIFY
OFFICERS OR STAFF MEMBERS WHO MAY REQUIRE ADDITIONAL
TRAINING.
4-2.3 (7.5) THE PROPOSED RMS APPLICATION SHALL INCLUDE A NOTES
FIELD WHERE SUPERVISORS CAN ENTER COMMENTS THAT
WOULD BE AUTOMATICALLY DELETED UPON FINAL APPROVAL.
4-2.3 (7.6) THE PROPOSED RMS APPLICATION SHALL ALLOW A SUPERVISOR
TO FLAG FIELDS OR TEXT THAT MUST BE CORRECTED BEFORE
THE REPORT WILL BE ACCEPTED.
4-2.3 (8) THE PROPOSED RMS APPLICATION SHALL PROVIDE A COMMAND
FOR SUPERVISORS TO SEE THE REPORTS WHICH THEY HAVE
RETURNED FOR CORRECTIONS AND WHICH HAVE NOT BEEN
RESUBMITTED.
4-2.3 (9) THE PROPOSED RMS APPLICATION SHALL NOTIFY THE
RESPONSIBLE SUPERVISOR AND THE COMMANDER OF THE UNIT TO
WHICH THE SUPERVISOR IS ASSIGNED WHEN REQUIRED REPORTS
HAVE NOT BEEN COMPLETED AFTER A DEPARTMENT DEFINABLE
TIME.
4-2.3 (10) THE PROPOSED RMS APPLICATION SHALL NOTIFY THE
RESPONSIBLE SUPERVISOR AND THE COMMANDER OF THE UNIT TO
WHICH THE SUPERVISOR IS ASSIGNED WHEN REQUIRED REPORTS
HAVE NOT BEEN SUBMITTED FOR REVIEW AFTER A DEPARTMENT
DEFINABLE TIME PERIOD.
4-2.3 (11) THE PROPOSED RMS APPLICATION SHALL ALLOW AUTHORIZED
USERS TO RESTRICT THE DISTRIBUTION OF A REPORT SO THAT IT
CANNOT BE VIEWED OR PRINTED BY OTHER USERS (REPORT
HOLD). (LOOK AT ALL OF THIS AREA)
4-2.3 (11.1) THE PROPOSED RMS APPLICATION SHALL HAVE THE ABILITY TO
CLASSIFY CERTAIN REPORTS AS CONFIDENTIAL AND RESTRICT
DISTRIBUTION TO A LIST DEFINED BY THE USER WHO IS
DEFINING THE REPORT AS RESTRICTED.
4-2.3 (11.2) THE PROPOSED RMS APPLICATION SHALL ALLOW THE SYSTEM
ADMINISTRATOR OR OTHER AUTHORIZED USER TO DETERMINE
WHICH USERS WILL HAVE THE AUTHORITY TO CLASSIFY A
REPORT AS RESTRICTED.
City of Fort Collins cxciv Proposal P-847
4-2.3 (11.3) THE PROPOSED RMS APPLICATION SHALL HAVE THE ABILITY TO
CLASSIFY CERTAIN REPORTS AS CONFIDENTIAL AND RESTRICT
DISTRIBUTION TO A LIST DEFINED BY THE USER WHO IS
DEFINING THE REPORT AS PASSWORD PROTECTED.
4-2.3 (11.4) THE PROPOSED RMS APPLICATION SHALL ALLOW THE SYSTEM
ADMINISTRATOR OR OTHER AUTHORIZED USER TO DETERMINE
WHICH USERS WILL HAVE THE AUTHORITY TO CLASSIFY A
REPORT AS PASSWORD PROTECTED.
4-2.3 (11.5) THE PROPOSED RMS APPLICATION SHALL HAVE LEVELS OF
SECURITY TO ENSURE CERTAIN CASES MAY BE PROTECTED
(FLAGGED) (I.E. CONFIDENTIAL, ADULT-AT-RISK, ETC.)
4-2.3 (11.6) THE PROPOSED RMS APPLICATION SHALL ALLOW HAVING MORE
THAN ONE (GLOBAL) PASSWORD (I.E. DIFFERENT PASSWORD FOR
DIFFERENT REASONS – DRUG TASK FORCE, ETC.)
4-2.3 (12) THE PROPOSED RMS APPLICATION SHALL ALLOW THE
GENERATION OF A HARD COPY LISTING OF ARCHIVED RECORDS.
4-2.3 (13) THE PROPOSED RMS APPLICATION SHALL ALLOW THE ARCHIVE
CAPABILITIES ACCORDING TO A PRE-DEFINED RECORDS
RETENTION SCHEDULE.
4-2.3 (14) THE PROPOSED RMS APPLICATION SHALL RETAIN MASTER INDEX
ENTRIES FOR ARCHIVED RECORDS IN THE ON-LINE MASTER INDEX
WITH A NOTATION THAT THE RECORD HAS BEEN ARCHIVED AND
THE LOCATION OF THE ARCHIVED INFORMATION.
4-2.3 (15) WHEN A SEARCH RETURN INCLUDES AN ARCHIVED RECORD, THE
OPERATOR SHALL BE ABLE TO EASILY DETERMINE THE LOCATION
OF THE ARCHIVED INFORMATION.
4-2.3 (16) THE PROPOSED RMS APPLICATION SHALL HAVE THE ABILITY TO
ACCESS AT LEAST 15 YEARS OF ON-LINE RMS DATA.
4-2.3 (17) IN ADDITION TO THE ELEMENTS SHOWN ON THE FORMS ATTACHED
IN THE APPENDIX, THE PROPOSED RMS APPLICATION SHALL HAVE
THE ABILITY TO TRACK THE FOLLOWING INFORMATION ABOUT
PERSONS:
4-2.3 (17.1) ALL INFORMATION CONTAINED IN THE MASTER NAME RECORD
AS IT WAS ORIGINALLY ENTERED IN THIS REPORT (DATA CAN
NOT CHANGE WHEN THE MNI IS UPDATED WITH NEW
INFORMATION).
City of Fort Collins cxcv Proposal P-847
4-2.3 (17.2) RELATIONSHIP TO REPORT (E.G. SUSPECT, WITNESS, PARENT,
COMPLAINANT, ETC.); MULTIPLE ROLES ALLOWED.
4-2.3 (17.3) MODUS OPERANDI (MO) FIELDS THAT ARE CONFIGURABLE BY
SYSTEM ADMINISTRATION
4-2.3 (17.4) CLOTHING DESCRIPTION,
4-2.3 (17.5) BLOOD ALCOHOL LEVEL,
4-2.3 (18) IN ADDITION TO THE ELEMENTS SHOWN ON THE FORMS ATTACHED
IN THE APPENDIX, THE PROPOSED RMS APPLICATION SHALL HAVE
THE ABILITY TO TRACK THE FOLLOWING INFORMATION ABOUT
VEHICLES:
4-2.3 (18.1) ALL INFORMATION CONTAINED IN THE MASTER VEHICLE
RECORD AS IT WAS ORIGINALLY ENTERED IN THIS REPORT
(DATA CAN NOT CHANGE WHEN THE MVI IS UPDATED WITH NEW
INFORMATION).
4-2.3 (18.2) STOLEN VEHICLE INFORMATION:
4-2.3 (18.2.1) VALUE OF THE VEHICLE,
4-2.3 (18.2.2) DATE/TIME RECOVERED,
4-2.3 (18.2.3) VALUE OF THE VEHICLE WHEN RECOVERED,
4-2.3 (18.2.4) LOCATION OF RECOVERY BY FULL STREET ADDRESS (TIED TO
MLI),
4-2.3 (18.2.5) LOCATION OF RECOVERY BY X-Y COORDINATES (TIED TO MLI),
4-2.3 (18.2.6) LOCATION OF RECOVERY BY REPORTING DISTRICT,
4-2.3 (18.2.7) LOCATION OF RECOVERY BY PATROL AREA,
4-2.3 (18.2.8) AND INSURANCE CARRIER AND POLICY NUMBER.
4-2.3 (19) THE PROPOSED RMS APPLICATION SHALL HAVE THE ABILITY TO
RECEIVE, STORE, AND MANAGE ALL DATA ELEMENTS REQUIRED
FOR COLORADO (IBRS) AND FBI (NIBRS) REPORTING.
4-2.3 (20) THE PROPOSED RMS APPLICATION SHALL ALLOW AUTHORIZED
USERS TO UPDATE CASE REPORTS WITH CLEARANCE
INFORMATION, AND AUTOMATICALLY GENERATE AN UPDATE TO
THE IBRS RECORD THAT WAS SENT TO THE STATE.
City of Fort Collins cxcvi Proposal P-847
4-2.3 (21) OUTSIDE OF (AND SUBSERVIENT TO) THE NIBRS/IBRS REPORTING
OF EXCEPTIONAL CLEARANCE OF INCIDENT REPORTS, THE
PROPOSED RMS APPLICATION SHALL ALLOW ADDITIONAL
CLEARANCES PER CASE RECORD TO SHOW THE INDIVIDUAL
STATUS OF EACH OFFENDER.
4-2.3 (22) THE PROPOSED RMS APPLICATION SHALL HAVE THE ABILITY TO
RECEIVE, STORE AND MANAGE COURT DISPOSITIONS FOR EACH
CHARGE IN THE CASE RECORD.
4-2.3 (23) THE PROPOSED RMS APPLICATION SHALL ALLOW STANDARD
IBRS/NIBRS REPORTS TO BE PRINTED LOCALLY, AND/OR SAVED TO
SOME TYPE OF MAGNETIC MEDIA; AND/OR FORWARDED
ELECTRONICALLY AS A BATCH DOWNLOAD, TO CBI MONTHLY.
4-2.3 (24) REPORTS SHALL INCLUDE, AT MINIMUM, ALL INFORMATION
CAPTURED BY IBRS/NIBRS ELEMENTS IN THE FORMAT(S)
PRESCRIBED BY CBI FOR THE FOLLOWING INFORMATION:
4-2.3 (24.1) MONTHLY RETURN OF OFFENSES,
4-2.3 (24.2) PROPERTY STOLEN BY CLASSIFICATION,
4-2.3 (24.3) PROPERTY RECOVERED TALLY,
4-2.3 (24.4) LARCENY - THEFT TALLY,
4-2.3 (24.5) MOTOR VEHICLE THEFT TALLY,
4-2.3 (24.6) SUPPLEMENT TO RETURN A - EVALUATION OF STOLEN
PROPERTY,
4-2.3 (24.7) MONTHLY RETURN OF ARSON OFFENSES,
4-2.3 (24.8) AGE, SEX AND RACE OF PERSON ARRESTED - 18 & OVER,
4-2.3 (24.9) AGE, SEX AND RACE OF PERSON ARRESTED - UNDER 18,
4-2.3 (24.10) LAW ENFORCEMENT OFFICERS KILLED OR ASSAULTED (LEOKA)
REPORT,
4-2.3 (24.11) HOMICIDE SUMMARY REPORT.
4-3 TRAFFIC ENFORCEMENT
4-3.1 (1) THE PROPOSED RMS APPLICATION SHALL INCLUDE AN
INTEGRATED MODULE FOR REPORTING AND TRACKING CITATIONS,
WARNINGS AND ACCIDENTS.
City of Fort Collins cxcvii Proposal P-847
4-3.1 (2) THE PROPOSED RMS APPLICATION SHALL ALLOW FOR CROSS-
REFERENCING TO OTHER INCIDENTS, ACCIDENTS, ARRESTS, ETC.
4-3.1 (3) THE PROPOSED RMS APPLICATION SHALL ALLOW FOR A
NARRATIVE REPORT TO BE ATTACHED TO THE ACCIDENT DETAILS.
4-3.1 (4) THE PROPOSED RMS APPLICATION SHALL HAVE THE ABILITY TO
CAPTURE AND STORE THE DATA ELEMENTS REQUIRED FOR THE
STATE OF COLORADO ACCIDENT, COMMERCIAL VEHICLE AND
FATALITY REPORT FORMS, INCLUDED IN THE APPENDIX.
4-3.1 (5) THE PROPOSED RMS APPLICATION SHALL HAVE THE ABILITY TO
PRINT OUT COMPLETED ACCIDENT REPORTS INCLUDING
ACCIDENT DIAGRAMS AS A REPLICA OF THE STATE OF COLORADO
ACCIDENT REPORT FORM.
4-3.1 (6) INFORMATION OBTAINED THROUGH THE TRAFFIC SYSTEM SHALL
BE INCLUDED IN THE MASTER NAME, AND VEHICLE INDEXES.
4-3.1 (7) IT IS PREFERRED THAT THE PROPOSED RMS APPLICATION HAS THE
ABILITY TO RECEIVE PARKING AND TRAFFIC COMPLAINTS FROM
CITIZENS. THESE COMPLAINTS WOULD THEN BE USED TO PLAN
TRAFFIC ENFORCEMENT ASSIGNMENTS.
4-3.1 (8) IT IS PREFERRED THAT THE PROPOSED RMS APPLICATION HAVE
THE ABILITY TO RECEIVE SIMPLE TRAFFIC ACCIDENT REPORT
FORMS VIA HTML SO THAT CITIZENS CAN REPORT MINOR
ACCIDENTS THROUGH THE AGENCY(IES) WEB SITE(S).
4-3.1 (9) THE PROPOSED RMS APPLICATION SHALL BE ABLE TO IMPORT AN
ASCII TEXT FILE FROM A TRAFFIC ACCIDENT FIELD REPORTING
APPLICATION. IMPORTED RECORDS SHALL BE PROCESSED FOR
FIELD LOGIC ONCE THEY ARE DISPLAYED ON THE PROPOSED RMS
CLIENT APPLICATION.
4-3.1 (10) THE PROPOSED RMS APPLICATION SHALL ALLOW FOR THE
TRANSFER OF ACCIDENT INFORMATION THAT HAS BEEN ENTERED
INTO THE RMS IN THE FORM OF A DELIMITED ASCII TEXT FILE.
4-3.1 (11) THE PROPOSED RMS APPLICATION SHALL HAVE THE ABILITY TO
TRACK THE ISSUANCE OF CITATION BOOKS WITH THE BEGINNING
AND ENDING CITATION NUMBER.
4-3.1 (12) AT A MINIMUM, THE PROPOSED RMS APPLICATION SHALL
CAPTURE AND REPORT THE FOLLOWING CITATION AND WARNING
INFORMATION:
City of Fort Collins cxcviii Proposal P-847
4-3.1 (12.1) CAPTURE THE INFORMATION CONTAINED IN THE MNI, MLI, &
MVI FOR EACH PERSON CONTACTED AND;
4-3.1 (12.2) CITATION OR WARNING NUMBER,
4-3.1 (12.3) LOCATION OF OFFENSE,
4-3.1 (12.4) COUNTY WHERE OFFENSE OCCURRED,
4-3.1 (12.5) OFFENSE DATE,
4-3.1 (12.6) OFFENSE TIME,
4-3.1 (12.7) ISSUING OFFICER,
4-3.1 (12.8) VIOLATION CODE
4-3.1 (12.9) VIOLATION DESCRIPTION,
4-3.1 (12.10) SPEED/POSTED SPEED,
4-3.1 (12.11) AND FINE ASSESSED.
4-3.1 (13) SYSTEM NEEDS TO BE ABLE TO FIGURE DUE DATE OF FINE
PAYMENT FROM DATE CITATION ISSUED (EARLY PAYMENT/POINT
REDUCTION)
4-3.1 (14) NEED TO BE ABLE TO GENERATE REPORTS OF FINES DUE, FINES
PAID, CITATIONS OVERDUE, AND CITATIONS SENT TO COURT.
4-3.1 (15) WHEN A CITATION IS ISSUED IN CONJUNCTION WITH AN ACCIDENT,
THE PROPOSED RMS APPLICATION SHALL COPY THE OFFENDER
NAME AND OTHER RELEVANT INFORMATION TO THE CITATION
RECORD SO THAT THE USER WILL NOT HAVE TO RE-ENTER THE
INFORMATION.
4-3.1 (16) IT IS PREFERRED THAT THE PROPOSED RMS APPLICATION ALLOW
OFFICERS TO ISSUE CITATIONS ON A MOBILE OR PORTABLE DATA
TERMINAL AND THEN UPLOAD THOSE CITATIONS TO THE SERVER
EITHER VIA WIRELESS OR SOME OTHER MEANS.
4-3.1 (17) THE VENDOR SHALL SUPPLY SPECIFICATIONS AND PRICING FOR
DRIVER’S LICENSE BARCODE OR MAGNETIC STRIPE READERS.
City of Fort Collins cxcix Proposal P-847
4-4 FIELD REPORTING
4-4.1 GENERAL REQUIREMENTS
4-4.1 (1) THE PROPOSED RMS APPLICATION SHALL PROVIDE A MOBILE
FIELD REPORTING APPLICATION.
4-4.1 (2) THE PROPOSED MOBILE FIELD REPORTING APPLICATION SHALL
HAVE THE SAME LOOK AND FEEL AS THE RMS CLIENT.
4-4.1 (3) IT IS PREFERRED THAT THE FIELD REPORTING APPLICATION BE
FULLY DEVELOPED AND SUPPORTED BY THE SAME VENDOR FOR
RMS/JMS RATHER THAN A THIRD PARTY VENDOR.
4-4.1 (4) THE USER AGENCY FORMS SHOULD BE RESIDENT ON THE MOBILE
DATA COMPUTER.
4-4.1 (5) THE PROPOSED MOBILE FIELD REPORTING APPLICATION SHALL
USE PULL-DOWN FIELDS WITH AUTO DEFAULTS AND AUTO FILL
CAPABILITIES.
4-4.1 (6) THE PROPOSED MOBILE FIELD REPORTING APPLICATION SHALL
USE LOOK UP TABLES FOR PICK AND VALIDATION PURPOSES.
4-4.1 (7) THE PROPOSED MOBILE FIELD REPORTING APPLICATION SHALL
REQUIRE DATA BE ENTERED ONLY ONCE AND USE THAT DATA IN
ALL OTHER NEEDED FORMS AND REPORTS.
4-4.1 (8) THE PROPOSED MOBILE FIELD REPORTING APPLICATION SHALL
ALLOW DATA ENTRY BY BAR CODE READER.
4-4.1 (9) THE PROPOSED MOBILE FIELD REPORTING APPLICATION SHALL
HAVE THE ABILITY TO PROMPT FOR NEEDED INFORMATION.
4-4.1 (10) THE PROPOSED MOBILE FIELD REPORTING APPLICATION SHALL
ALLOW SHORTCUT KEYS FOR ENTERING INFORMATION.
4-4.1 (11) AT A MINIMUM, THE PROPOSED MOBILE FIELD REPORTING
APPLICATION SHALL HAVE THE ABILITY TO ELECTRONICALLY
COMPLETE THE FOLLOWING FORMS AND REPORTS:
4-4.1 (11.1) CASE REPORTS,
4-4.1 (11.2) ARREST,
4-4.1 (11.3) BOOKING,
4-4.1 (11.4) TRAFFIC ACCIDENT,
City of Fort Collins cc Proposal P-847
4-4.1 (11.5) FIELD INTERVIEWS (CONTACT CARDS),
4-4.1 (11.6) WARNINGS,
4-4.1 (11.7) TRAFFIC CITATIONS,
4-4.1 (11.8) PROPERTY/EVIDENCE REPORTS,
4-4.1 (11.9) PROPERTY INVENTORY (FOR SEARCH WARRANTS),
4-4.1 (11.10) DOMESTIC VIOLENCE REPORTS,
4-4.1 (11.11) SUBPOENAS AND WARRANT SERVICE,
4-4.1 (11.12) CIVIL PROCESS
4-4.1 (11.13) AND AFFIDAVIT OF WARRANTLESS ARREST
4-4.1 (12) THE PROPOSED MOBILE FIELD REPORTING APPLICATION SHALL
HAVE THE ABILITY TO COMPLETE ALL OPERATIONS AS DESCRIBED
IN THIS MODULE WITHOUT FULL TIME WIRELESS CONNECTIVITY.
4-4.1 (13) THE PROPOSED MOBILE FIELD REPORTING APPLICATION SHALL
HAVE “STORE AND FORWARD” CAPABILITIES (ALL WORK IS
TRANSMITTED IN BOTH DIRECTIONS AND SYSTEM UPDATES ARE
DOWNLOADED AS A CONNECTION BECOMES AVAILABLE, EITHER
WIRELESS OR HARD WIRE).
4-4.1 (14) THE PROPOSED MOBILE FIELD REPORTING APPLICATION SHALL
HAVE THE ABILITY TO PRINT THE ABOVE-LISTED FORMS AND
REPORTS.
4-4.1 (15) THE PROPOSED MOBILE FIELD REPORTING APPLICATION SHALL
HAVE THE ABILITY TO SUBMIT REPORTS ELECTRONICALLY TO
RMS UPON COMMAND.
4-4.1 (16) THE PROPOSED MOBILE FIELD REPORTING APPLICATION SHALL
HAVE THE ABILITY TO ACCESS AND UPDATE SUBMITTED REPORTS
FROM THE FIELD BEFORE REPORT APPROVAL.
4-4.1 (17) THE PROPOSED MOBILE FIELD REPORTING APPLICATION SHALL
HAVE THE ABILITY TO ACCESS APPROVED REPORTS FROM THE
FIELD.
4-4.1 (18) THE PROPOSED MOBILE FIELD REPORTING APPLICATION SHALL
HAVE THE ABILITY TO WRITE REPORTS SIMULTANEOUSLY WITH
OTHER FUNCTIONS (E.G. ELECTRONIC DISPATCH, MESSAGING,
INQUIRIES, ETC.)
City of Fort Collins cci Proposal P-847
4-4.1 (19) THE PROPOSED MOBILE FIELD REPORTING APPLICATION SHALL
HAVE THE ABILITY TO AUTOMATICALLY POPULATE FIELD
REPORTING WITH INFORMATION GATHERED FROM AN INQUIRY.
4-5 ARREST PROCESSING
4-5.1 (1) THE PROPOSED RMS/JMS APPLICATION SHALL PROVIDE AN
ARREST-PROCESSING MODULE FOR ENTERING AND STORING
INFORMATION ABOUT PERSONS ARRESTED.
4-5.1 (2) THE PROPOSED RMS/JMS APPLICATION SHALL HAVE THE ABILITY
TO CAPTURE ALL OF THE FIELDS SHOWN ON THE ARREST REPORT
INCLUDED IN THE APPENDIX OF THIS RFP.
4-5.1 (3) THE PROPOSED RMS/JMS SHALL HAVE THE ABILITY TO AUTO-
POPULATE ALL ARREST MODULE INFORMATION FROM A BOOKING
AT THE JAIL.
4-5.1 (4) THE SYSTEM SHALL HAVE THE ABILITY TO ASSIGN SEQUENTIAL
ARREST (BOOKING) NUMBERS (NUMBERS UNIQUE TO THIS
INDIVIDUAL AND THIS ARREST OR BOOKING) IN THE FORMAT
DESCRIBED BELOW;
4-5.1 (4.1) ALPHA/NUMERIC,
4-5.1 (4.2) 12 CHARACTERS,
4-5.1 (4.3) IN THE FORMAT (YY)(AA)(F)(C)(NNNNNN) WHERE (YY) IS THE
LAST TWO DIGITS OF THE CURRENT YEAR, (AA) IS A TWO
LETTER CODE FOR THE ARRESTING AGENCY, (F) IS A ONE
LETTER CODE FOR FACILITY (DERIVED BY PHYSICAL LOCATION
OF THE ENTRY TERMINAL), (C) IS A ONE LETTER CODE
INDICATING TO HIGHEST LEVEL CHARGE FOR THIS ARREST, AND
(NNNNNN) IS A SIX DIGIT SEQUENTIAL NUMBER SHARED BY ALL
AGENCIES THAT STARTS OVER EACH YEAR.
4-5.1 (5) THE ARREST NUMBER SHALL BE GENERATED BY THE SAME
ROUTINE THAT PROVIDES BOOKING NUMBERS TO THE JAIL
(ARREST NUMBER IS THE SAME AS BOOKING NUMBER AND MUST
BE UNIQUE ACROSS THE ENTIRE SYSTEM).
4-5.1 (6) THE PROPOSED RMS APPLICATION SHALL ALLOW THE USER TO
RECORD THE FOLLOWING INFORMATION ABOUT ARRESTED
PERSONS:
4-5.1 (6.1) ALL INFORMATION CONTAINED IN THE MASTER NAME RECORD
AS IT WAS ORIGINALLY ENTERED IN THIS REPORT (DATA CAN
City of Fort Collins ccii Proposal P-847
NOT CHANGE WHEN THE MNI IS UPDATED WITH NEW
INFORMATION).
4-5.1 (6.2) ALL INFORMATION CONTAINED IN THE MUGSHOT MODULE AS IT
WAS ORIGINALLY ENTERED IN THIS REPORT.
4-5.1 (6.3) CASE (REPORT) NUMBER,
4-5.1 (6.4) BOOKING/ARREST NUMBER,
4-5.1 (6.5) ARRESTING OFFICER(S),
4-5.1 (6.6) REPORTING OFFICER,
4-5.1 (6.7) ARREST DATE,
4-5.1 (6.8) ARREST LOCATION,
4-5.1 (6.9) BLOOD ALCOHOL LEVEL,
4-5.1 (6.10) DUI TEST TYPE GIVEN,
4-5.1 (6.11) INJURIES OR ILLNESS,
4-5.1 (6.12) TREATED BY,
4-5.1 (6.13) WHERE TREATED,
4-5.1 (6.14) TREATED DATE AND TIME,
4-5.1 (6.15) OFFENSE LOCATION,
4-5.1 (6.16) OFFENSE DATE AND TIME.
4-5.1 (7) IF THE ARRESTEE IS A JUVENILE, THE RMS SHALL RECORD THE
FOLLOWING ADDITIONAL INFORMATION:
4-5.1 (7.1) PERSON NOTIFIED OF ARREST,
4-5.1 (7.2) HOW NOTIFIED,
4-5.1 (7.3) RELATIONSHIP,
4-5.1 (7.4) DATE AND TIME NOTIFIED
4-5.1 (7.5) ARRESTEE RELEASED TO,
4-5.1 (7.6) RELATIONSHIP,
City of Fort Collins cciii Proposal P-847
4-5.1 (7.7) DATE AND TIME RELEASED.
4-5.1 (8) DISPOSITIONS ASSOCIATED WITH JUVENILE ARRESTS (I.E. TURNED
OVER TO OTHER AGENCY, FELONY FILING, ETC.)
4-5.1 (9) THE PROPOSED RMS SYSTEM SHALL ALLOW A MINIMUM OF 99
CHARGES RECORDS PER PERSON WITH THE FOLLOWING
INFORMATION FOR EACH CHARGE:
4-5.1 (9.1) SEQUENTIAL NUMBER FOR EACH CHARGE,
4-5.1 (9.2) THE CHARGE (ABILITY TO SELECT FROM AN AGENCY
MAINTAINED PICK LIST, CHARGES, BY FULL OR PARTIAL
CHARGE CODE OR CHARGE DESCRIPTION) OR;
4-5.1 (9.3) ABILITY FOR FREE TEXT ENTRY OF A CHARGE CODE
(OVERRIDE).
4-5.1 (9.3.1) THE SYSTEM SHALL SEND AN NOTIFICATION TO A SYSTEM
ADMINISTRATOR THAT A MANUAL CHARGE CODE ENTRY WAS
MADE.
4-5.1 (9.4) ABILITY FOR FREE TEXT ENTRY OF A CHARGE DESCRIPTION,
4-5.1 (9.5) A PICK LIST FIELD (PER CHARGE) SPECIFICALLY FOR CLASS OF
CRIME (E.G. FELONY 1,2,3,4,5,6, MISDEMEANOR 1,2,3, PETTY
OFFENSE 1,2, ETC.),
4-5.1 (9.6) A PICK LIST FIELD (PER CHARGE/SENTENCE) SPECIFICALLY FOR
TYPE OF CHARGE/SENTENCE (E.G. STATE CHARGE, MUNICIPAL
CHARGE, WARRANT, ETC.)
4-5.1 (10) A FIELD (PER CHARGE) SPECIFICALLY FOR THE ENTRY OF THE
STATE OF COLORADO STANDARDIZED COURT DOCKET/WARRANT
NUMBER (FOR CICJIS LINKING),
4-5.1 (10.1) THE SYSTEM SHALL ENSURE CORRECT ENTRY OF STATE
STANDARDIZED COURT DOCKET/WARRANT NUMBER BY
CHECKING FOR ADHERENCE TO CORRECT FORMATTING AS
DEFINED BY THE STATE OF COLORADO.
4-5.1 (10.2) SUMMONS NUMBER,
4-5.1 (10.3) A PICK LIST FIELD (PER CHARGE/SENTENCE) SPECIFICALLY FOR
ARRESTING AGENCY.
4-5.1 (10.4) A FIELD (PER CHARGE/SENTENCE) SPECIFICALLY FOR
CHARGING OFFICER.
City of Fort Collins cciv Proposal P-847
4-5.1 (11) THE SYSTEM SHALL STORE (PER CHARGE/SENTENCE) ALL CHARGE
INFORMATION (CODE AND DESCRIPTION) AS DISPLAYED (AS
OPPOSED TO ONLY STORING A POINTER TO A TABLE).
4-5.1 (11.1) NUMBER OF COUNTS,
4-5.1 (11.2) THE IBRS CODE.
4-5.1 (12) THE PROPOSED RMS APPLICATION SHALL HAVE THE ABILITY TO
RECORD THE USE OF FORCE BY AN OFFICER CONCERNING ANY
ARRESTED PERSON.
4-5.1 (13) THE USER SHALL HAVE THE ABILITY TO RECORD THE TYPE OF
WEAPON USED DURING THE USE-OF-FORCE ENCOUNTER.
4-5.1 (14) THE PROPOSED RMS APPLICATION SHALL ALLOW FOR
NOTIFICATION TO USER-DEFINED INDIVIDUAL(S) WHEN USE OF
FORCE ENTRY IS MADE
4-5.1 (15) IF THE ARRESTED PERSON DOES NOT HAVE A MNI, THE PROPOSED
RMS APPLICATION SHALL GENERATE A NEW NUMBER.
4-5.1 (16) IF THE ARRESTEE HAS A PREVIOUS RECORD, THE SYSTEM SHALL
AUTO-POPULATE ALL EMPTY FIELDS ON THE NEW ARREST REPORT
UPON THE USER’S COMMAND.
4-6 CRIMINAL INVESTIGATION & ANALYSIS
4-6.1 INVESTIGATIONS
4-6.1 (1) THE PROPOSED RMS APPLICATION SHALL SUPPORT ALL DATA
FIELDS THAT CURRENTLY APPEAR ON THE AGENCY’S CRIMINAL
OFFENSE AND INVESTIGATIVE REPORT FORMS.
4-6.1 (2) THE PROPOSED RMS APPLICATION SHALL UTILIZE THE SHARED
MAPPING SYSTEM DESCRIBED IN SECTION 2 AND SECTION 3 SO AS
TO ENABLE AGENCY PERSONNEL TO PLOT AND DISPLAY INCIDENTS
AND OFFENSES BY VARIOUS PARAMETERS ON A COMPUTERIZED
MAP.
4-6.1 (2.1) THE PROPOSED APPLICATION SHALL HAVE THE ABILITY TO
PLOT INCIDENTS AND OFFENSES ON A MAP FOR ANY
JURISDICTION FOR WHICH THE SYSTEM HAS A COORDINATE
BASED GEOFILE.
4-6.1 (2.2) IT IS PREFERRED THAT THIS ANALYSIS MODULE INCLUDE A DATA
ANIMATION FEATURE. THIS FEATURE WOULD ALLOW THE USER
TO FIND PATTERNS OF ACTIVITY IN LARGE DATA SETS BY
City of Fort Collins ccv Proposal P-847
ANIMATING OR STEPPING THROUGH ACTIVITY ON SUCCESSIVE
DATES, WEEKS, MONTHS OR DAYS OF THE WEEK. FOR EXAMPLE,
THE ANALYST MIGHT RETRIEVE ALL ROBBERIES FOR A ONE
YEAR PERIOD AND THEN WITH A SIMPLE COMMAND ANIMATE
THE DATA SET SO THAT ROBBERIES WILL DISPLAY ONE MONTH
AT A TIME IN SUCCESSION. THIS WOULD ALLOW THE ANALYST
TO SEE HOW ROBBERIES ARE MOVING AROUND AND TO SEE IF
THERE ARE ANY DISCERNABLE PATTERNS.
4-6.1 (3) THE PROPOSED RMS APPLICATION SHALL ALLOW THE USER TO
SELECT A GEOGRAPHIC SEARCH AREA BY DRAWING A POLYGON
OR CIRCLE (ON A MAP) WITH A POINTING DEVICE.
4-6.1 (3.1) THE PROPOSED RMS APPLICATION SHALL ASSIST ANY
AUTHORIZED USER WITH THE IDENTIFICATION OF CRIME
PATTERNS BY:
4-6.1 (3.2) A REPORT WHICH SHOWS RATES OF OFFENSE
INCREASE/DECREASE BY PATROL DISTRICT OR OTHER AREA,
4-6.1 (3.3) A REPORT WHICH SHOWS RATES OF OFFENSE
INCREASE/DECREASE BY DAY OF WEEK AND TIME OF DAY,
4-6.1 (3.4) A MAPPING FUNCTION THAT WILL USE COLORED OR SHADED
MAPS TO SHOW RATES OF OFFENSE INCREASE/DECREASE BY
PATROL DISTRICT OR OTHER AREA GRAPHICALLY ON A MAP.
4-6.1 (4) THE PROPOSED RMS APPLICATION SHALL HAVE THE ABILITY TO
RETRIEVE CASES WITH SIMILAR MODUS OPERANDI TO ASSIST
DETECTIVES IN SOLVING CRIMES. FOR EXAMPLE, SIMILAR VICTIM
TYPES, CRIMES OCCURRING IN CLOSE PROXIMITY OR WITHIN A
GIVEN DATE OR TIME RANGE, OR IN WHICH SIMILAR KINDS OF
PROPERTY WERE TAKEN, TOOLS USED, METHOD OF ENTRY, POINT
OF ENTRY, CHARACTERISTIC ACTIONS, EVIDENCE FOUND, VICTIM
TYPE/LOCATION, OR WEAPON USED.
4-6.1 (4.1) IT IS PREFERRED THAT THIS FUNCTION NOT REQUIRE ADVANCED
TRAINING IN QUERY LANGUAGES OR TECHNIQUES.
4-6.1 (5) THE PROPOSED RMS APPLICATION SHALL AUTOMATICALLY
IDENTIFY CASES WITH SIMILAR SUSPECT DESCRIPTIONS, SUCH AS
GLASSES, TEETH, SPEECH, DEMEANOR, FACIAL HAIR,
COMPLEXION, SCARS, MARKS, TATTOOS, HAIR LENGTH, HAIR
STYLE, HAIR COLOR, ETHNICITY, HEIGHT, WEIGHT, OR GENDER BY
SEARCHING THE MUGSHOT MODULE.
City of Fort Collins ccvi Proposal P-847
4-6.1 (6) THE PROPOSED RMS APPLICATION SHALL INCLUDE THE ABILITY
TO SEARCH NARRATIVE FIELDS FOR A USER-DEFINED “STRING” OF
TEXT.
4-6.1 (7) THE PROPOSED RMS APPLICATION SHALL HAVE THE ABILITY TO
DISPLAY OR PRINT A LIST OF ALL INDIVIDUALS ASSOCIATED WITH
A GIVEN CASE SORTED BY THEIR ASSOCIATION WITH THE CASE
AND THEN ALPHABETICALLY.
4-6.1 (8) IT IS DESIRED THAT THE PROPOSED RMS APPLICATION INCLUDE A
GRAPHICAL REPRESENTATION OF THE ASSOCIATION BETWEEN
EACH LISTED INDIVIDUAL.
4-6.1 (8.1) IT IS PREFERRED THAT THE PROPOSED RMS APPLICATION
ALLOW A USER TO RETRIEVE ALL RECORDS FOR A GIVEN
ASSOCIATE BY DOUBLE-CLICKING ON THE NAME, OR BY SOME
OTHER SIMPLE METHOD.
4-6.2 CRIME ANALYSIS
4-6.2 (1) THE PROPOSED RMS/JMS APPLICATION SHALL INCLUDE A CRIME
ANALYSIS MODULE THAT PROVIDES GRAPHICAL AND STATISTICAL
TOOLS FOR ANALYZING THE OCCURRENCE OF CRIME AND OTHER
REPORTED INCIDENTS WITHIN LARIMER COUNTY.
4-6.2 (2) THE PROPOSED RMS/JMS APPLICATION SHALL PROVIDE FOR THE
ABILITY TO EXTENSIVELY QUERY THE RMS/JMS DATABASE
WITHOUT SIGNIFICANTLY SLOWING ANY OTHER FUNCTION OF
THE SYSTEM.
4-6.2 (3) THE PROPOSED RMS/JMS APPLICATION SHALL ALLOW THE CRIME
ANALYSTS TO EASILY ACCESS THE FOLLOWING KINDS OF
INFORMATION FROM CRIME AND OTHER REPORTS.
4-6.2 (3.1) DATE OF THE OFFENSE, BY DATE RANGE,
4-6.2 (3.2) TIME OF THE OFFENSE, BY TIME RANGE,
4-6.2 (3.3) LOCATION WHERE THE OFFENSE OCCURRED,
4-6.2 (3.4) TYPE OF PREMISES,
4-6.2 (3.5) DESCRIPTION OF WEAPONS OR TOOLS USED,
4-6.2 (3.6) METHOD AND POINT OF ENTRY/EXIT,
4-6.2 (3.7) VICTIM DATA,
City of Fort Collins ccvii Proposal P-847
4-6.2 (3.8) SUSPECT DATA,
4-6.2 (3.9) REPORTING PARTY DATA,
4-6.2 (3.10) TEXT CONTAINED IN NARRATIVE FIELDS,
4-6.2 (3.11) CLEARANCE TYPE,
4-6.2 (3.12) DESCRIPTION OF PROPERTY STOLEN,
4-6.2 (3.13) VEHICLE(S) INVOLVED/STOLEN DESCRIPTION(S),
4-6.2 (3.14) SUSPECT(S) DESCRIPTION(S),
4-6.2 (3.15) OR INCIDENT NAME.
4-6.2 (4) THE PROPOSED RMS/JMS APPLICATION SHALL ALLOW THE CRIME
ANALYST TO SET THRESHOLDS FOR CERTAIN KINDS OF ACTIVITIES
(INCIDENT TYPES). IF THE ACTIVITY THRESHOLD IS EXCEEDED
THE SYSTEM SHALL NOTIFY THE CRIME ANALYST. FOR EXAMPLE,
IF THE CRIME ANALYST SETS A THRESHOLD FOR BURGLARIES OF
FIVE PER MONTH THE SYSTEM WILL SEND A NOTICE TO THE
ANALYST IF MORE THAN FIVE BURGLARIES ARE COMMITTED IN
ONE MONTH.
4-6.2 (5) IT IS DESIRED THAT THE PROPOSED RMS/JMS APPLICATION
INCLUDE THE ABILITY TO PROVIDE A SUSPECT OR MO PROFILE
FOR A GIVEN OFFENSE BASED ON PAST OFFENSES OF THE SAME
TYPE. FOR EXAMPLE, IF THE ANALYST RUNS A PROFILE REPORT
ON ARMED ROBBERIES THE PROFILE MIGHT SHOW THAT PAST
ROBBERIES HAVE OCCURRED PRIMARILY AT CONVENIENCE
STORES BETWEEN THE HOURS OF 2100 AND 0200.
4-6.2 (6) THE PROPOSED RMS/JMS APPLICATION SHALL ALLOW THE CRIME
ANALYST OR OTHER AUTHORIZED USER TO SEARCH BY ONE OR
MORE PHYSICAL DESCRIPTORS, WITH THE RESULTS DISPLAYING
(EITHER ON SCREEN OR IN PRINTED FORM) IN ALPHABETICAL
ORDER (DEFINED ELSEWHERE - DESCRIPTORS TO BE RANGE
SEARCHABLE).
4-7 CASE MANAGEMENT
4-7.1 (1) THE PROPOSED RMS/JMS APPLICATION SHALL PROVIDE A VARIETY
OF MANAGEMENT AND ANALYSIS TOOLS TO:
4-7.1 (1.1) BETTER MANAGE INVESTIGATOR WORKLOADS,
4-7.1 (1.2) AND MONITOR PERFORMANCE.
City of Fort Collins ccviii Proposal P-847
4-7.1 (2) THE PROPOSED CASE MANAGEMENT MODULE SHALL BE TIGHTLY
INTEGRATED WITH THE OTHER PORTIONS OF THE RMS
APPLICATION. FOR EXAMPLE, IF AN INVESTIGATOR UPDATES A
CASE STATUS IN THE CASE MANAGEMENT MODULE OR CHANGES
AN OFFENSE CLASSIFICATION IT SHALL BE REFLECTED IN EVERY
OTHER PROPOSED MODULE.
4-7.1 (3) THE PROPOSED RMS APPLICATION SHALL INCLUDE FIELDS FOR
DETERMINING CASE SOLVABILITY.
4-7.1 (4) THE PROPOSED RMS APPLICATION SHALL AUTOMATICALLY
CALCULATE THE SOLVABILITY OF A CASE BY CALCULATING THE
SOLVABILITY FACTORS.
4-7.1 (5) THE PROPOSED RMS APPLICATION SHALL ALLOW AN AUTHORIZED
USER TO MANUALLY OVERRIDE THE AUTOMATICALLY
DETERMINED SOLVABILITY FACTOR, OR ASSIGN AN OVERRIDING
PRIORITY.
4-7.1 (6) THE PROPOSED RMS APPLICATION SHALL PROVIDE A MEANS OF
NOTIFYING OR DISPLAYING FOR AUTHORIZED USERS ALL CASES
WITH A TOTAL SOLVABILITY FACTOR GREATER THAN X, WHERE X
IS A CONFIGURATION PARAMETER OR IS CHOSEN BY THE USER AT
THE TIME THE DISPLAY COMMAND IS INVOKED.
4-7.1 (7) THE PROPOSED RMS APPLICATION SHALL ALLOW THE DETECTIVE
COMMANDER OR OTHER AUTHORIZED USER TO DISPLAY ALL NEW
CASES ENTERED FOR A GIVEN DATE RANGE SO THAT THE
COMMANDER CAN REVIEW THE CASES FOR ASSIGNMENT.
4-7.1 (8) THE PROPOSED RMS APPLICATION SHALL RESPOND WITH A
SUMMARY DISPLAY WHICH SHOWS THE CASE (REPORT) NUMBER,
THE LOCATION OF THE OFFENSE, THE OFFICER INITIATING THE
CASE, THE OFFENSE TYPE, THE VICTIM NAME, AND THE DATE ON
WHICH IT WAS INITIATED.
4-7.1 (9) THE PROPOSED RMS APPLICATION SHALL ALLOW THE DETECTIVE
COMMANDER OR OTHER AUTHORIZED USER TO DISPLAY ALL
ACTIVE CASES BY:
4-7.1 (9.1) ASSIGNED INVESTIGATOR,
4-7.1 (9.2) OFFENSE TYPE,
4-7.1 (9.3) DATE AND TIME OF OFFENSE,
4-7.1 (9.4) AGING (HOW LONG INVESTIGATION HAS BEEN ONGOING),
City of Fort Collins ccix Proposal P-847
4-7.1 (9.5) SHIFT,
4-7.1 (9.6) AND PATROL DISTRICT,
4-7.1 (9.7) DATE OF LAST MODIFICATION (ACTIVITY OR LACK THEREOF).
4-7.1 (10) THE PROPOSED RMS APPLICATION SHALL RESPOND WITH A
SUMMARY DISPLAY WHICH SHOWS THE CASE (REPORT) NUMBER,
THE VICTIM NAME, THE INVESTIGATOR ASSIGNED TO THE CASE,
THE OFFENSE TYPE, THE STATUS OF THE CASE (INCLUDING THE
DATE WHEN THE CASE WAS LAST MODIFIED).
4-7.1 (11) THE PROPOSED RMS APPLICATION SHALL HAVE THE ABILITY TO
TRACK AND REPORT CASE OUTCOMES AND CRIME STATISTICS ON
ALL RECORDS WHICH REMAIN IN THE ON-LINE DATABASE.
4-7.1 (12) IT SHALL BE POSSIBLE FOR THE SYSTEM ADMINISTRATOR OR
OTHER AUTHORIZED USER TO CONFIGURE THE PROPOSED RMS
APPLICATION SO THAT CASES ARE AUTOMATICALLY ASSIGNED TO
A SPECIFIC INVESTIGATOR BASED ON:
4-7.1 (12.1) OFFENSE LOCATION,
4-7.1 (12.2) OR OFFENSE TYPE.
4-7.1 (13) THE STANDARD CASE MANAGEMENT DISPLAY SHALL INCLUDE THE
OFFENSE TYPE, THE CASE (REPORT) NUMBER, DATE AND TIME THE
INCIDENT WAS REPORTED, LOCATION, TYPE OF REPORT, AND THE
SOLVABILITY RATING FOR EACH ACTIVE CASE.
4-7.1 (14) THE PROPOSED RMS APPLICATION SHALL ENABLE AN
AUTHORIZED SUPERVISOR OR OTHER AUTHORIZED EMPLOYEE TO
ASSIGN A CASE TO A SPECIFIC INVESTIGATOR OR OTHER MEMBER
OF THE DEPARTMENT.
4-7.1 (15) THE PROPOSED RMS APPLICATION SHALL ALLOW FOR THE
ASSIGNING OF A PRIMARY OFFICER ON ALL CASES.
4-7.1 (15.1) IF NO OFFICER IS ASSIGNED, THE CASE WILL AUTOMATICALLY
BE ASSIGNED TO THE PRIMARY OFFICER IDENTIFIED IN THE CAD
RECORD.
4-7.1 (16) THE PROPOSED RMS APPLICATION SHALL ALLOW A SUPERVISOR
OR OTHER AUTHORIZED EMPLOYEE TO REASSIGN CASES AT ANY
TIME, EVEN AFTER THE CASES HAVE BEEN CLOSED IN CAD.
4-7.1 (17) THE PROPOSED RMS APPLICATION SHALL ENABLE A SUPERVISOR
OR OTHER AUTHORIZED EMPLOYEE TO TRANSFER A CASE TO
City of Fort Collins ccx Proposal P-847
ANOTHER INVESTIGATIVE SUPERVISOR OR EMPLOYEE FOR
PROCESSING.
4-7.1 (18) THE PROPOSED RMS APPLICATION SHALL ENABLE A SUPERVISOR
OR OTHER AUTHORIZED EMPLOYEE TO ENTER A CASE
DISPOSITION WITHOUT FIRST ASSIGNING THE CASE TO AN
INVESTIGATOR.
4-7.1 (19) THE PROPOSED RMS APPLICATION SHALL AUTOMATICALLY
NOTIFY AN INVESTIGATOR OR OTHER MEMBER OF THE
DEPARTMENT AT LOGON WHEN A NEW CASE HAS BEEN ASSIGNED
TO THEM FOR FOLLOW-UP.
4-7.1 (20) THE PROPOSED RMS APPLICATION SHALL ALLOW AN
INVESTIGATOR TO FORWARD A CASE TO THE INVESTIGATIVE
SUPERVISOR FOR REVIEW ONCE THE INVESTIGATOR HAS
DETERMINED THAT THE CASE SHOULD BE CLOSED.
4-7.1 (21) THE PROPOSED RMS APPLICATION SHALL ALLOW A CASE TO BE
CLOSED FOR THE PURPOSES OF IBRS REPORTING, BUT REMAIN
ACTIVE FOR INVESTIGATION.
4-7.1 (22) THE PROPOSED RMS APPLICATION SHALL HAVE THE ABILITY TO
ALLOW MULTIPLE INVESTIGATORS TO BE ASSIGNED TO AND
UPDATE A SINGLE CASE.
4-7.1 (23) THE PROPOSED APPLICATION SHALL ALLOW AN INVESTIGATIVE
SUPERVISOR OR OTHER AUTHORIZED USER TO REASSIGN CASES
OR PRIMARY INVESTIGATOR DESIGNATION AT ANY TIME.
4-7.1 (24) THE PROPOSED RMS APPLICATION SHALL ALLOW ACCESS BY
POINT AND CLICK TO ALL FORMS, IMAGES, AND OTHER DATABASE
ITEMS ASSOCIATED WITH A GIVEN CASE.
4-7.1 (25) THE PROPOSED RMS APPLICATION SHALL ALLOW AN AUTHORIZED
USER TO ADD OR REMOVE INVESTIGATORS FROM A CASE AT ANY
TIME
4-7.1 (25.1) THE SYSTEM SHALL MAINTAIN AN EASILY DISPLAYED HISTORY
OF ALL ASSIGNED INVESTIGATORS.
4-7.1 (26) THE PROPOSED RMS APPLICATION SHALL ALLOW AUTHORIZED
USERS TO BLOCK ACCESS INTO SELECTED INVESTIGATIONS IN
PROCESS.
4-7.1 (27) THE PROPOSED RMS APPLICATION CLEARLY IDENTIFY JUVENILE
CRIMINAL HISTORY INFORMATION.
City of Fort Collins ccxi Proposal P-847
4-7.1 (28) THE PROPOSED RMS APPLICATION SHALL AUTOMATICALLY
CLASSIFY CASES AS JUVENILE CASES WHEN THE DEFENDANT, ON
THE DATE THAT THE CRIME OCCURRED, WAS A JUVENILE AND
PROCESS THE CASES ACCORDINGLY.
4-7.1 (29) THE PROPOSED RMS APPLICATION SHALL HAVE THE ABILITY TO
INCLUDE JUVENILE RECORDS IN ALL SEARCHES.
4-7.1 (30) THE PROPOSED RMS APPLICATION SHALL HAVE THE ABILITY TO
IDENTIFY CASES WITHOUT ACTIVITY FOR A USER DEFINED PERIOD
OF TIME.
4-7.1 (31) AT A MINIMUM, THE PROPOSED APPLICATION SHALL INCLUDE THE
FOLLOWING CASE STATUSES:
4-7.1 (31.1) ACTIVE CASE,
4-7.1 (31.2) ASSIGNED FOR INVESTIGATION,
4-7.1 (31.3) LACK OF INVESTIGATIVE LEADS (INACTIVE),
4-7.1 (31.4) SUSPENSE,
4-7.1 (31.5) USER CLOSURE - PENDING FOR ADDITIONAL
SUSPECT/INFORMATION,
4-7.1 (31.6) CASE BEING HANDLED BY ANOTHER AGENCY,
4-7.1 (31.7) UNFOUNDED,
4-7.1 (31.8) AND CIVIL MATTER.
4-7.1 (32) IT IS PREFERRED THAT THE SYSTEM ADMINISTRATOR OR OTHER
AUTHORIZED USER HAVE THE ABILITY TO DEFINE NEW CASE
STATUSES AND CLOSURES AS NEEDED.
4-7.1 (33) THE PROPOSED RMS APPLICATION SHALL INCLUDE THE
FOLLOWING CASE DISPOSITIONS:
4-7.1 (33.1) ADULT ARREST,
4-7.1 (33.2) JUVENILE ARREST,
4-7.1 (33.3) WARRANT ISSUED,
4-7.1 (33.4) UNFOUNDED,
4-7.1 (33.5) EXCEPTIONAL CLEARANCE,
City of Fort Collins ccxii Proposal P-847
4-7.1 (33.6) EXTRADITION DECLINED,
4-7.1 (33.7) DEATH OF OFFENDER,
4-7.1 (33.8) VICTIM/WITNESS REFUSED TO COOPERATE,
4-7.1 (33.9) AND PROSECUTION DECLINED.
4-7.1 (34) THE PROPOSED RMS APPLICATION SHALL ALLOW A USER TO
GENERATE A FORM LETTER TO THE COMPLAINANTS AND VICTIMS
OF AN OFFENSE AFTER THE CASE HAS BEEN CLOSED.
4-7.1 (35) THE PROPOSED RMS APPLICATION SHALL HAVE THE ABILITY TO
GENERATE A FORM LETTER TO A VICTIM OR WITNESS
REQUESTING THEM TO CALL THE INVESTIGATING DETECTIVE.
4-7.1 (36) THE PROPOSED RMS APPLICATION SHALL HAVE THE ABILITY TO
CROSS-REFERENCE TWO OR MORE CASES.
4-7.1 (37) THE PROPOSED RMS APPLICATION SHALL HELP INVESTIGATORS
TO TRACK ALL ACTIVITY ON A CASE INCLUDING PERSONAL
INTERVIEWS, PHONE CALLS, LETTERS WRITTEN AND SO ON BY
PROVIDING A MEANS OF RECORDING THE DATE, TIME,
DESCRIPTION AND DURATION OF THE ACTIVITY AND BY
PROVIDING A NOTES FIELD IN WHICH THE INVESTIGATOR CAN
RECORD INFORMATION.
4-7.1 (38) IT IS PREFERRED THAT THE PROPOSED RMS APPLICATION ALLOW
INVESTIGATORS, COMMUNITY AND SCHOOL RESOURCE OFFICERS,
AND OTHERS TO CAPTURE CASE ACTIVITIES ON A PALM OR OTHER
HAND-HELD COMPUTER AND TRANSFER THESE TO THE RMS
APPLICATION.
4-7.1 (39) IT IS PREFERRED THAT THE PALM ACTIVITY TRACKING
APPLICATION SHOULD INCLUDE:
4-7.1 (39.1) A FIELD FOR ENTERING THE CASE (REPORT) NUMBER THE
ACTIVITY IS RELATED TO,
4-7.1 (39.2) A FIELD FOR ENTERING THE INCIDENT NUMBER THE ACTIVITY
IS RELATED TO,
4-7.1 (39.3) A FIELD FOR THE OFFICER OR EMPLOYEE MAKING THE
ACTIVITY,
4-7.1 (39.4) A FIELD FOR THE ADDRESS WHERE THE ACTIVITY IS BEING
PERFORMED,
City of Fort Collins ccxiii Proposal P-847
4-7.1 (39.5) A FIELD TO RECORD THE NAME OF THE PERSON THE
INVESTIGATOR IS INTERVIEWING,
4-7.1 (39.6) A FIELD TO RECORD THE START TIME AND DATE,
4-7.1 (39.7) A FIELD TO RECORD THE END TIME AND DATE,
4-7.1 (39.8) AN ACTIVITY CLASSIFICATION LIST,
4-7.1 (39.9) A PROJECT CODE FIELD SO THAT DIFFERENT ACTIVITIES
RELATED TO THE SAME PROJECT CAN BE CAPTURED,
4-7.1 (39.10) A COMMENT FIELD.
4-7.1 (40) THE PROPOSED INVESTIGATIVE SYSTEM SHALL ALLOW THE
INVESTIGATOR TO RECORD CASE NOTES WITHOUT ADDING THESE
NOTES TO A CASE VIA AN OFFICIAL DEPARTMENTAL REPORT.
4-7.1 (41) THE PROPOSED RMS APPLICATION SHALL HAVE THE ABILITY TO
LIST THE ACTIVITIES ON A CASE AND PROVIDE A TOTAL OF THE
TIME EXPENDED.
4-7.1 (42) THE PROPOSED RMS APPLICATION SHALL ALLOW INVESTIGATORS
OR OTHER USERS TO ADD REMINDERS TO EACH CASE. THESE
REMINDERS WILL INCLUDE A TEXT FIELD AND A MEANS TO
SCHEDULE THE REMINDER DATE AND TIME.
4-7.1 (42.1) THE PROPOSED RMS APPLICATION SHALL ALLOW USERS TO
TRACK THE COMPLETION OF ACTIVITIES BY INCLUDING A
MEANS OF INDICATING THAT THE REMINDER WAS COMPLETED
OR RESCHEDULING IT FOR ANOTHER TIME.
4-7.1 (42.2) IT IS PREFERRED THAT THE REMINDER FUNCTION ALLOW THE
USER TO SCHEDULE REOCCURRING NOTICES AND INCLUDE A
USER-DEFINABLE LEAD TIME.
4-7.1 (43) THE PROPOSED RMS APPLICATION SHALL ALLOW ANY
AUTHORIZED USER TO VIEW OR PRINT OUT A COMPLETE HISTORY
OF INVESTIGATORS ASSIGNED TO A CASE AND ACTIVITIES
ASSOCIATED WITH THAT CASE.
4-8 WARRANTS TRACKING
4-8.1 (1) THE PROPOSED RMS APPLICATION SHALL INCLUDE THE ABILITY
TO ENTER AND TRACK WANTED INDIVIDUALS.
4-8.1 (2) AT A MINIMUM, THE RMS APPLICATION WILL CAPTURE THE
FOLLOWING DATA ELEMENTS FOR A WANTED PERSONS RECORD:
City of Fort Collins ccxiv Proposal P-847
4-8.1 (2.1) ALL THE INFORMATION CONTAINED IN THE MNI, MLI, & MVI FOR
EACH WANTED PERSON AND;
4-8.1 (2.2) CHARGE,
4-8.1 (2.3) MISDEMEANOR OR FELONY,
4-8.1 (2.4) BOND TYPE AND AMOUNT,
4-8.1 (2.5) FINGERPRINT CLASSIFICATION,
4-8.1 (2.6) VEHICLE INFORMATION,
4-8.1 (2.7) STATE OF COLORADO STANDARDIZED WARRANT NUMBER (FOR
CICJIS LINKING),
4-8.1 (2.7.1) THE SYSTEM SHALL ENSURE CORRECT ENTRY OF STATE
STANDARDIZED WARRANT NUMBER BY CHECKING FOR
ADHERENCE TO CORRECT FORMATTING AS DEFINED BY THE
STATE OF COLORADO.
4-8.1 (2.8) WARRANT STATUS,
4-8.1 (2.9) ISSUE DATE,
4-8.1 (2.10) COURT,
4-8.1 (2.11) AGENCY,
4-8.1 (2.12) CASE (REPORT) NUMBER,
4-8.1 (2.13) OTHER IDENTIFYING NUMBERS,
4-8.1 (2.14) CAUTIONS,
4-8.1 (2.15) MISCELLANEOUS FIELD,
4-8.1 (2.16) AND CANCELLATION DATE.
4-8.1 (3) THE PROPOSED RMS APPLICATION SHALL INCLUDE AN AUTOMATIC
ADD/UPDATE TO CCIC FOR EACH NEW WARRANT ADDED TO THE
WANTED PERSONS FILE.
4-8.1 (4) THE PROPOSED RMS APPLICATION SHALL INCLUDE AN AUTOMATIC
CANCEL TO CCIC FOR EACH WARRANT CANCELED IN THE WANTED
PERSONS FILE.
4-8.1 (5) IT IS PREFERRED THAT THE SYSTEM BE ABLE TO IMPORT CICJIS
WARRANT DATA DIRECTLY INTO THE SYSTEM. ALL CICJIS
City of Fort Collins ccxv Proposal P-847
MESSAGING WOULD BE HANDLED ELECTRONICALLY AS INTERNAL
MESSAGING (DATA WOULD BE PARSED AND DRIVE A SYSTEM
ENTRY/EXIT PROCESS).
4-8.1 (5.1) SYSTEM SHOULD HAVE A FIELD THAT INDICATES CICJIS
POSSESSION OF A WARRANT (COURT OR PACKING AGENCY).
4-8.1 (5.2) IT IS PREFERRED THAT THE PARTICIPATING AGENCIES WOULD
BE ABLE TO USE THE RMS TO TAKE POSSESSION OF A CICJIS
WARRANT.
4-8.1 (5.3) IT IS PREFERRED THAT THE RMS HAVE SOME METHOD TO
TRACK AND NOTIFY OF INCOMPLETE CICJIS WARRANTS.
4-8.1 (6) IT IS PREFERRED THAT THE SYSTEM TRACK ALL WARRANT
LOCATES AND THEN GENERATE AND FORMAT AN ARRESTING
AGENCY RESPONSE MESSAGE AS WELL INITIATE THE DISPOSITION
PROCESS.
4-8.1 (7) IT IS PREFERRED THAT THE SYSTEM HAVE THE ABILITY TO DO A
DEPARTMENT OF REVENUE REGISTERED OWNER VEHICLE QUERY
AND THEN TO AUTOMATICALLY PACK THE WARRANT WITH THE
RESPONSE.
4-9 CIVIL SERVICE PROCESS
The proposed system must have the capability to track the service, and attempts to service,
civil process papers and court orders processed by the Sheriff's Office. At minimum the
proposed system shall provide the following functionality:
4-9.1 (1) THE SYSTEM MUST RECORD THE AGENCY NAME, FULL ADDRESS,
PHONE AND CONTACT PERSON THAT ANY PAPERS ARE RECEIVED
FROM FOR SERVICE (TIED TO LOCATION AND NAME MASTER
INDEXES.
4-9.1 (2) THE SYSTEM MUST RECORD THE LAST POSSIBLE DATE AND TIME
THE PAPERS CAN BE SERVED BY THE SHERIFF’S OFFICE.
4-9.1 (3) THE SYSTEM MUST TRACK THE OFFICER ASSIGNED THE PAPERS OR
ORDER FOR SERVICE.
4-9.1 (4) THE SYSTEM MUST NOTIFY THE ASSIGNED OFFICER AND THE CIVIL
PROCESS PERSONNEL AS DEFINED BY THE AGENCY OF ANY PAPERS
OR PROCESSES THAT ARE NEARING THE LAST POSSIBLE DATE AND
TIME (LEAD TIME FOR THE NOTIFICATION TO BE SET BY THE
AGENCY).
City of Fort Collins ccxvi Proposal P-847
4-9.1 (5) THE SYSTEM MUST RECORD THE DATE AND TIME ANY PAPERS
WERE RECEIVED BY THE SHERIFF'S OFFICE.
4-9.1 (6) THE SYSTEM MUST RECORD THE CLASS OF SERVICE (PICK LIST).
4-9.1 (7) THE SYSTEM MUST RECORD THE TYPE OF DOCUMENT (PICK LIST).
4-9.1 (8) THE SYSTEM MUST RECORD THE COURT OF ISSUANCE.
4-9.1 (9) THE SYSTEM MUST RECORD THE DATE THE PAPERS WERE ISSUED
BY THE COURT.
4-9.1 (10) THE SYSTEM MUST RECORD THE COUNTY IN WHICH THE COURT
OF ISSUANCE RESIDES.
4-9.1 (11) THE SYSTEM MUST RECORD THE COURT OF ISSUANCE CASE
(REPORT) NUMBER.
4-9.1 (12) THE SYSTEM MUST RECORD THE PERSON(S) TO BE SERVED
PERSONAL DEMOGRAPHICS (TIED TO MASTER NAME INDEX AND
SPECIFIED AS TO ROLE).
4-9.1 (13) THE SYSTEM MUST RECORD THE PERSON(S) TO BE SERVED FULL
EMPLOYMENT INFORMATION INCLUDING COMPANY NAME, FULL
ADDRESS AND PHONE NUMBER (TIED TO MASTER NAME INDEX).
4-9.1 (14) THE SYSTEM MUST RECORD THE BEST POSSIBLE LOCATION(S) FOR
SERVICE INCLUDING PHONE NUMBERS.
4-9.1 (15) THE SYSTEM MUST RECORD DEFENDANT’S PERSONAL
DEMOGRAPHICS (TIED TO MASTER NAME INDEX AND SPECIFIED AS
TO ROLE).
4-9.1 (16) THE SYSTEM MUST RECORD DEFENDANT DOING BUSINESS AS
(SPECIFIC INFORMATION ON DEFENDANT’S COMPANY NAME).
4-9.1 (17) THE SYSTEM MUST RECORD PLAINTIFF’S PERSONAL
DEMOGRAPHICS (TIED TO MASTER NAME INDEX AND SPECIFIED AS
TO ROLE).
4-9.1 (18) THE SYSTEM MUST RECORD PLAINTIFF’S RELATIONSHIP TO
DEFENDANT.
4-9.1 (19) THE SYSTEM MUST ALLOW FOR MULTIPLE DEFENDANTS FOR A
SINGLE PLAINTIFF.
4-9.1 (20) THE SYSTEM MUST ALLOW FOR MULTIPLE PLAINTIFFS FOR A
SINGLE DEFENDANT.
City of Fort Collins ccxvii Proposal P-847
4-9.1 (21) THE SYSTEM MUST ALLOW FOR MULTIPLE PLAINTIFFS FOR
MULTIPLE DEFENDANTS.
4-9.1 (22) THE SYSTEM MUST TRACK ALL ATTEMPTS FOR SERVICE TO
INCLUDE;
4-9.1 (22.1) DATE AND TIME OF EACH ATTEMPT,
4-9.1 (22.2) FULL LOCATION INFORMATION OF EACH ATTEMPT (TIED TO
LOCATION MASTER INDEX),
4-9.1 (22.3) TIME ELAPSED FOR EACH ATTEMPT,
4-9.1 (22.4) MILEAGE DRIVEN FOR EACH ATTEMPT,
4-9.1 (22.5) OFFICER PERFORMING THE ATTEMPT (TIED TO MASTER NAME
INDEX),
4-9.1 (22.6) INDICATOR OF LAST ATTEMPT AND FAILURE TO COMPLETE
SERVICE,
4-9.1 (22.7) DATE AND TIME THE UN-SERVED PAPERS WERE RETURNED.
4-9.1 (22.8) PERSON THE PAPERS WERE RETURNED TO (TIED TO MASTER
NAME INDEX AND SPECIFIED AS TO ROLE).
4-9.1 (22.9) AND THE FREE TEXT COMMENTS FOR EACH ATTEMPT.
4-9.1 (23) THE SYSTEM MUST TRACK ALL SUCCESSFUL SERVICES TO
INCLUDE:
4-9.1 (23.1) INDICATION OF SERVICE TO THE DEFENDANT, OR,
4-9.1 (23.2) ACTUAL PERSON SERVED DEMOGRAPHICS (TIED TO MASTER
NAME INDEX AND SPECIFIED AS TO ROLE),
4-9.1 (23.3) ACTUAL PERSON SERVED RELATIONSHIP TO DEFENDANT,
4-9.1 (23.4) DATE AND TIME OF SERVICE,
4-9.1 (23.5) FULL SERVICE LOCATION INFORMATION (TIED TO MASTER
LOCATION INDEX),
4-9.1 (23.6) TIME ELAPSED FOR SERVICE,
4-9.1 (23.7) MILEAGE DRIVEN FOR SERVICE,
4-9.1 (23.8) OFFICER PERFORMING THE SERVICE (TIED TO MASTER NAME
INDEX AND SPECIFIED AS TO ROLE),
City of Fort Collins ccxviii Proposal P-847
4-9.1 (23.9) FREE TEXT COMMENTS FOR THE SERVICE,
4-9.1 (23.10) AND THE INDICATION OF A SUCCESSFUL SERVICE.
4-9.1 (24) THE SYSTEM MUST TRACK ALL FUNDS PROCESSING TO THE
AGENCY/PERSON REQUESTING CIVIL SERVICE PROCESS TO
INCLUDE:
4-9.1 (24.1) TYPE OF TRANSACTION (PAYMENT OR REFUND),
4-9.1 (24.2) DATE AND TIME OF ANY TRANSACTION,
4-9.1 (24.3) AMOUNT OF PAYMENT OR REFUND,
4-9.1 (24.4) FORM OF PAYMENT (CASH, CHECK),
4-9.1 (24.5) CHECK NUMBER (ISSUED OR RECEIVED),
4-9.1 (24.6) PERSON MAKING A PAYMENT OR RECEIVING A REFUND (TIED TO
MASTER NAME INDEX AND SPECIFIED AS TO ROLE),
4-9.1 (24.7) EMPLOYEE COMPLETING TRANSACTION (VIEWABLE AS PART OF
THE FORM),
4-9.1 (24.8) AUTOMATIC CALCULATION OF MILEAGE CHARGES,
4-9.1 (24.9) TRACKING OF VARIOUS FEES APPLICABLE TO CIVIL PROCESS
(EVICTION FEE, SERVICE FEE, NOTARY FEE, OTHER FEES AS
DEFINED BY THE AGENCY),
4-9.1 (24.10) PROVISION FOR A FREE TEXT FIELD PER FEE OR CHARGE
ASSESSED.
4-9.1 (24.11) TRACKING OF ALL UNPAID FEES AND INDICATION OF FINAL
PAYMENT,
4-9.1 (24.12) AUTOMATIC NOTIFICATION TO THE SYSTEM OPERATOR OF ANY
UNSATISFIED DEBT UPON ENTRY OF A NEW REQUEST FOR
SERVICE BY THE SAME AGENCY OR PERSON,
4-9.1 (24.13) AND THE GENERATION OF A DETAILED INVOICE AND/OR
RECEIPT.
City of Fort Collins ccxix Proposal P-847
4-10 PROPERTY AND EVIDENCE MANAGEMENT SYSTEM
4-10.1 GENERAL REQUIREMENTS
4-10.1 (1) THE PROPOSED RMS APPLICATION SHALL INCLUDE A
COMPREHENSIVE PROPERTY AND EVIDENCE MANAGEMENT
SYSTEM.
4-10.1 (2) AT A MINIMUM, THE PROPOSED SYSTEM SHALL HAVE THE ABILITY
TO TRACK THE FOLLOWING KINDS OF PROPERTY:
4-10.1 (2.1) EVIDENCE,
4-10.1 (2.2) STOLEN PROPERTY,
4-10.1 (2.3) RECOVERED STOLEN PROPERTY,
4-10.1 (2.4) SAFEKEEPING,
4-10.1 (2.5) FOUND PROPERTY,
4-10.1 (2.6) SEIZED PROPERTY, AND
4-10.1 (2.7) FOR DESTRUCTION.
4-10.1 (3) IN ADDITION TO THE OTHER FIELDS LISTED IN THE USER AGENCY
FORMS INCLUDED IN THE APPENDIX, THE PROPOSED SYSTEM
SHALL INCLUDE THE FOLLOWING INFORMATION FOR EACH
PROPERTY ITEM:
4-10.1 (3.1) MAKE OR BRAND NAME,
4-10.1 (3.2) MODEL,
4-10.1 (3.3) PROPERTY TYPE (E.G. JEWELRY, CURRENCY, FIREARM, ETC.),
4-10.1 (3.4) SIZE,
4-10.1 (3.5) WEIGHT,
4-10.1 (3.6) COLOR,
4-10.1 (3.7) SERIAL NUMBER,
4-10.1 (3.8) OTHER IDENTIFYING NUMBER, (OWNER APPLIED ID,
ALPHA/NUMERIC)
4-10.1 (3.9) LICENSE PLATE NUMBER,
City of Fort Collins ccxx Proposal P-847
4-10.1 (3.10) CALIBER,
4-10.1 (3.11) NARRATIVE DESCRIPTION,
4-10.1 (3.12) DIGITAL PHOTO OR SCANNED IMAGE OF PROPERTY ITEM,
4-10.1 (3.13) SPECIFIC LOCATION THE PROPERTY WAS FOUND, RECOVERED
OR SEIZED FROM,
4-10.1 (3.14) NAME, ADDRESS AND PHONE NUMBER OF THE PERSON FINDING
THE PROPERTY,
4-10.1 (3.15) DATE AND TIME RECOVERED,
4-10.1 (3.16) INDIVIDUAL THE EVIDENCE WAS CONFISCATED FROM,
INCLUDING NAME, ADDRESS, TELEPHONE NUMBER, AND
CRIMINAL CASE INFORMATION (DEFENDANTS, CHARGES),
4-10.1 (3.17) NAME AND ID NUMBER OF THE OFFICER(S) RECEIVING,
RECOVERING OR SEIZING THE PROPERTY,
4-10.1 (3.18) NAME, ADDRESS, AND PHONE NUMBER OF THE PROPERTY
OWNER,
4-10.1 (3.19) CASE (REPORT) NUMBER,
4-10.1 (3.20) EVIDENCE TAG NUMBER (NUMBER AND BARCODE),
4-10.1 (3.21) DATE AND TIME ENTERED,
4-10.1 (3.22) RETENTION REVIEW DATES,
4-10.1 (3.23) WHICH COURT (I.E. COUNTY, MUNICIPAL OR DISTRICT), AND
4-10.1 (3.24) TEMPORARY STORAGE LOCATION.
4-10.1 (4) IT IS PREFERRED THAT THE PROPOSED RMS APPLICATION INCLUDE
A VEHICLE DIAGRAM FOR AUTOMOBILE RECORDS OR THE ABILITY
TO ATTACH A DIGITAL PHOTO SO THAT EXISTING DAMAGE TO THE
PROPERTY CAN BE RECORDED.
4-10.1 (5) THE PROPOSED SYSTEM SHALL SUPPORT A CASH RECEIPTS
JOURNAL.
4-10.2 EVIDENCE ENTRY AND PROCESSING
4-10.2 (1) WHEN A NEW PROPERTY RECORD IS ENTERED, THE PROPOSED RMS
APPLICATION SHALL AUTOMATICALLY CHECK BY SERIAL NUMBER
AND/OR PROPERTY TYPE TO SEE IF THE ITEMS HAVE BEEN
City of Fort Collins ccxxi Proposal P-847
ENTERED INTO THE SYSTEM PREVIOUSLY (E.G. IT HAS BEEN
REPORTED STOLEN).
4-10.2 (2) THE PROPOSED RMS APPLICATION SHALL ASSIGN A UNIQUE CASE-
RELATED PROPERTY ID NUMBER TO EACH ITEM OF PROPERTY
ENTERED INTO THE SYSTEM.
4-10.2 (3) THE PROPOSED RMS APPLICATION SHALL ALLOW OFFICERS AND
EMPLOYEES TO ENTER PROPERTY RECORDS EITHER FROM A
DESKTOP WORKSTATION OR FROM THE FIELD.
4-10.2 (4) THE PROPOSED RMS APPLICATION SHALL ALLOW THE EVIDENCE
TECHNICIAN/CUSTODIAN TO REJECT IMPROPERLY PACKAGED
PROPERTY OR INAPPROPRIATE PROPERTY LOGGED IN BY
OFFICERS.
4-10.2 (4.1) IF THE PROPERTY IS REJECTED, THE SYSTEM SHALL ALLOW FOR
NOTIFICATION TO THE OFFICER THAT THE PROPERTY HAS BEEN
REJECTED.
4-10.2 (5) THE PROPOSED RMS APPLICATION SHALL OFFER A METHOD SO
THAT WHEN A USER IS REQUIRED TO ENTER MULTIPLE PROPERTY
ITEMS, THE USER SHALL NOT BE REQUIRED TO ENTER REPETITIVE
THE SAME INFORMATION MORE THAN ONE TIME.
4-10.2 (6) THE PROPOSED RMS APPLICATION SHALL UPON USER REQUEST
FORMAT AND SEND AN INQUIRY TO THE PAWN SYSTEM AND TO
CCIC FOR EACH NEW PROPERTY RECORD AND NAME THAT IS
ENTERED INTO THE SYSTEM.
4-10.2 (7) THE PROPOSED RMS APPLICATION SHALL INCLUDE THE ABILITY
TO PRINT A LABEL THAT INCLUDES AT A MINIMUM:
4-10.2 (7.1) CASE (REPORT) NUMBER,
4-10.2 (7.2) NAME AND NUMBER OF OFFICER RECOVERING THE PROPERTY,
4-10.2 (7.3) ITEM NUMBER,
4-10.2 (7.4) DATE AND TIME COLLECTED,
4-10.2 (7.5) OWNER’S NAME, AND
4-10.2 (7.6) BAR CODE FOR EVERY ITEM OF PROPERTY.
4-10.2 (8) WHEN PRINTING A LABEL FOR A PACKAGE CONTAINING DRUGS,
THE LABEL SHALL INCLUDE AT A MINIMUM:
City of Fort Collins ccxxii Proposal P-847
4-10.2 (8.1) THE PROPERTY DESCRIPTION,
4-10.2 (8.2) AND WEIGHT OF CONTENTS.
4-10.2 (9) THE PROPOSED RMS APPLICATION SHALL ALLOW EVIDENCE
TECHNICIANS OR OTHER AUTHORIZED USER TO PRINT SPECIFIED
PROPERTY LABELS IN A BATCH MODE ONCE THEY HAVE FINISHED
ENTERING PROPERTY EITHER IN THE FIELD OR AT THE STATION.
4-10.2 (10) THE PROPOSED RMS APPLICATION SHALL HAVE THE ABILITY TO
READ THE BAR CODE ON A PROPERTY LABEL AND RETRIEVE THE
PROPERTY RECORD WITHOUT ADDITIONAL INFORMATION.
4-10.2 (11) THE PROPOSED RMS APPLICATION SHALL INCLUDE THE ABILITY
TO RECORD A COURT DISPOSITION FOR EACH PROPERTY ITEM.
4-10.2 (12) ONCE A COURT DISPOSITION HAS BEEN RECORDED FOR A CASE,
THE SYSTEM SHALL GENERATE A FINAL DISPOSITION REQUEST
AND ELECTRONICALLY SEND THAT REQUEST TO THE
INVESTIGATING OFFICER AND EVIDENCE TECHNICIAN.
4-10.2 (13) THE PROPOSED RMS APPLICATION SHALL ALLOW AN AUTHORIZED
USER TO GENERATE/PRINT A FORM LETTER TO THE LISTED OWNER
OF THE PROPERTY FOR CASES THAT HAVE A FINAL DISPOSITION
STATUS.
4-10.2 (14) THE PROPOSED RMS APPLICATION SHALL INCLUDE THE ABILITY
TO RECORD THE FOLLOWING INFORMATION FOR NON-
DEPARTMENTAL PERSONNEL WHO ARE CLAIMING PROPERTY:
4-10.2 (14.1) ALL INFORMATION CONTAINED IN THE MASTER NAME RECORD,
4-10.2 (14.2) FORM OF IDENTIFICATION,
4-10.2 (14.3) DIGITAL SIGNATURE,
4-10.2 (14.4) AND DIGITAL PHOTOGRAPH.
4-10.2 (15) THE PROPOSED RMS APPLICATION SHALL ALLOW THE EVIDENCE
TECHNICIAN OR OTHER AUTHORIZED USERS TO RETRIEVE
PROPERTY ITEMS THAT ARE UNCLAIMED FOR AN AGENCY
DEFINED PERIOD AND GENERATE/PRINT A FORM LETTER TO THE
LISTED OWNER OF THE PROPERTY.
4-10.2 (16) THE PROPOSED RMS APPLICATION SHALL INCLUDE A REPORT
THAT LISTS CASE (REPORT) NUMBERS OF PROPERTY ITEMS WHICH
ARE RELEASABLE BUT WHICH HAVE NOT BEEN PICKED UP WITHIN
City of Fort Collins ccxxiii Proposal P-847
USER-DEFINED NUMBER OF DAYS OF THE LISTED OWNER’S
NOTIFICATION.
4-10.2 (17) THE PROPOSED RMS APPLICATION SHALL ALLOW THE SYSTEM
ADMINISTRATOR OR OTHER AUTHORIZED USER TO LIMIT
PROPERTY RECORD EDITING TO AUTHORIZED EMPLOYEES
ASSIGNED TO THE EVIDENCE VAULT.
4-10.3 PROPERTY ADMINISTRATION
4-10.3 (1) AT A MINIMUM, THE PROPOSED APPLICATION SHALL INCLUDE THE
FOLLOWING AGENCY DEFINED PROPERTY STATUS
CLASSIFICATIONS PER ITEM:
4-10.3 (1.1) DESTRUCTION,
4-10.3 (1.2) AUCTION,
4-10.3 (1.3) CONVERSION,
4-10.3 (1.4) EVIDENCE,
4-10.3 (1.5) EVIDENCE HOLD,
4-10.3 (1.6) EVIDENCE RELEASE,
4-10.3 (1.7) STOLEN PROPERTY,
4-10.3 (1.8) RECOVERED STOLEN PROPERTY,
4-10.3 (1.9) SAFEKEEPING,
4-10.3 (1.10) FOUND PROPERTY,
4-10.3 (1.11) DAMAGED,
4-10.3 (1.12) SEIZED PROPERTY, AND
4-10.3 (1.13) LAB HOLD.
4-10.3 (2) THE SYSTEM SHALL BE ABLE TO AUTOMATICALLY CALCULATE
THE RETENTION REVIEW DATES BY OFFENSE TYPE OR ALLOW FOR
MANUAL ADJUSTMENT/ENTRY AT THE USER’S DISCRETION ON A
PER ITEM BASIS.
4-10.3 (3) THE PROPOSED RMS APPLICATION SHALL ALLOW FOR THE
EVIDENCE TECHNICIAN OR OTHER AUTHORIZED USER TO PRINT
REPORTS BASED ON THE RETENTION REVIEW DATES.
City of Fort Collins ccxxiv Proposal P-847
4-10.3 (4) ONCE THE RETENTION DATE HAS BEEN REACHED, THE CASE
OFFICER AND EVIDENCE TECHNICIAN SHALL BE NOTIFIED VIA AN
INTERNAL SYSTEM MESSAGE OR AUTO-GENERATED
REPORT/EMAIL.
4-10.3 (4.1) CASE OFFICER NOTIFICATION SHALL BECOME A PART OF A
WORKFLOW PROCESS THAT MANDATES A RESPONSE FROM THE
OFFICER TO THE EVIDENCE TECHNICIAN.
4-10.3 (5) THE PROPOSED RMS APPLICATION SHALL MAINTAIN A “CHAIN OF
CUSTODY” RECORD FOR EVERY PIECE OF PROPERTY UNDER
DEPARTMENTAL CONTROL SUCH THAT THE DATE, TIME,
RELEASING AND RECEIVING MEMBERS’ IDENTIFICATION SHALL BE
RECORDED EVERY TIME THE CUSTODY OF A PROPERTY ITEM IS
CHANGED.
4-10.3 (6) THE PROPOSED RMS APPLICATION SHALL ALLOW THE USERS TO
TRACK WHEN PROPERTY IS CHECKED OUT BY A LAW
ENFORCEMENT OR AUTHORIZED REPRESENTATIVE OF ANOTHER
JURISDICTION.
4-10.3 (7) THE PROPOSED SYSTEM SHALL OFFER THE USER AN EASY WAY TO
RETRIEVE A PROPERTY RECORD AND TRANSFER CUSTODY OF THE
ARTICLE TO ANOTHER MEMBER OF THE DEPARTMENT OR A
CITIZEN.
4-10.3 (8) IN ORDER TO FACILITATE THE TRANSFER OF CUSTODY, THE
SYSTEM SHALL ALLOW THE EVIDENCE TECHNICIAN OR OTHER
AUTHORIZED USER TO RETRIEVE AND ASSEMBLE A LIST OF
PROPERTY ITEMS AND THEN TRANSFER CUSTODY OF ALL ITEMS
ON THE LIST AT ONE TIME.
4-10.3 (9) IN ORDER TO FACILITATE THE RETURN OF PROPERTY TO THE
EVIDENCE VAULT, THE SYSTEM SHALL ALLOW THE EVIDENCE
TECHNICIAN OR OTHER AUTHORIZED USER TO RETRIEVE ALL
ITEMS IN THE CUSTODY OF A PARTICULAR OFFICER AND SELECT
FROM THIS LIST WHICH ITEMS ARE BEING RETURNED TO THE
EVIDENCE VAULT.
4-10.3 (9.1) THE SYSTEM SHALL THEN MARK ALL THESE ITEMS AS
RETURNED AT THE SAME DATE AND TIME.
4-10.3 (10) THE PROPOSED SYSTEM SHALL ALLOW THE EVIDENCE
TECHNICIAN OR OTHER AUTHORIZED USER TO DESIGNATE
ANOTHER EMPLOYEE AS THE AUTHORITY FOR RELEASING
PROPERTY AS REQUIRED.
City of Fort Collins ccxxv Proposal P-847
4-10.3 (11) THE PROPOSED SYSTEM SHALL HAVE THE ABILITY TO TRACK THE
PHYSICAL LOCATION OF PROPERTY ITEMS WHILE THEY ARE
STORED IN THE EVIDENCE VAULT OR AT SATELLITE FACILITIES. AT
A MINIMUM, THE LOCATION RECORD SHALL INCLUDE:
4-10.3 (11.1) A FACILITY NAME OR NUMBER (I.E. FCPS, LCSO, CBI, FBI, ETC.)
(BOTH PRE-DEFINED PICK LIST AND FREE TEXT),
4-10.3 (11.2) A ROOM NAME OR NUMBER (I.E. EVIDENCE ROOM, LAB,
CLANDESTINE LAB STORAGE) (BOTH PRE-DEFINED PICK LIST
AND FREE TEXT),
4-10.3 (11.3) A SUB LOCATOR (I.E. RACK, DRUG BOX, REFRIGERATOR, SAFE,
ETC.) (PRE-DEFINED PICK LIST TO BE LIMITED BY ROOM
SELECTION),
4-10.3 (11.4) AND A SUB/SUB LOCATOR (I.E. BIN, SPACE, SHELF, DRAWER) (PRE-
DEFINED PICK LIST TO BE LIMITED BY SUB LOCATOR
SELECTION).
4-10.3 (12) THE PROPOSED RMS APPLICATION SHALL HAVE THE ABILITY TO
SUPPORT A FINAL DISPOSITION RECORD FOR ALL PROPERTY
ITEMS THAT INCLUDES THE DATE, TIME, AND DISPOSITION.
4-10.3 (12.1) IT IS PREFERRED THAT THE PROPOSED RMS APPLICATION HAVE
THE ABILITY TO PROCESS FINAL DISPOSITION WITH SOME TYPE
OF BATCH PROCESS.
4-10.3 (13) THE PROPOSED RMS APPLICATION SHALL ALLOW THE OFFICERS
RESPONSIBLE FOR THE EVIDENCE TO MARK IT FOR RELEASE TO
THE OWNER, DESTRUCTION, AUCTION, OR CONVERSION ON THE
COMPUTER ON A PER ITEM BASIS.
4-10.4 LABORATORY EXAMINATION
4-10.4 (1) THE SYSTEM SHALL HAVE THE ABILITY TO TRACK AND REPORT
LABORATORY EXAMINATION PROCESSES BY CAPTURING THE
MINIMUM OF THE FOLLOWING INFORMATION FOR EACH ITEM
PROCESSED BY THE LAB:
4-10.4 (1.1) CASE (REPORT) NUMBER,
4-10.4 (1.2) ITEM NUMBER,
4-10.4 (1.3) ITEM CONDITION BEFORE,
4-10.4 (1.4) ITEM CONDITION AFTER,
City of Fort Collins ccxxvi Proposal P-847
4-10.4 (1.5) PROCESS TYPE (UP TO 99 PER ITEM),
4-10.4 (1.6) PROCESS START DATE AND TIME (PER PROCESS TYPE),
4-10.4 (1.7) PROCESS END DATE AND TIME (PER PROCESS TYPE),
4-10.4 (1.8) TASK TYPE (UP TO 99 PER PROCESS TYPE),
4-10.4 (1.9) AND NARRATIVE PER TASK.
4-10.4 (2) LAB RESULTS AS TRACKED IN THIS MODULE SHALL HAVE THE
ABILITY TO BE ROUTED ELECTRONICALLY TO THE REPORTING
OFFICER, COLLECTING OFFICER, AND ANY OTHER DESIGNATED
PERSON.
4-10.4 (3) REPORTS SHALL INCLUDE:
4-10.4 (3.1) CASE (REPORT) NUMBER,
4-10.4 (3.2) ITEM NUMBER,
4-10.4 (3.3) ITEM CONDITION AFTER,
4-10.4 (3.4) PROCESSES PERFORMED (ALL FOR EACH ITEM),
4-10.4 (3.5) TASKS PERFORMED (ALL FOR EACH PROCESS),
4-10.4 (3.6) AND ALL NARRATIVES (FOR EACH TASK).
4-10.4 (3.7) LAB RESULTS AS TRACKED IN THIS MODULE SHALL HAVE THE
ABILITY TO BE GROUPED BY CASE (REPORT) NUMBER AND
ROUTED EN-MASS ELECTRONICALLY TO THE REPORTING
OFFICER, COLLECTING OFFICER, AND ANY OTHER DESIGNATED
PERSON.
4-11 VICTIM’S RESPONSE MODULE
4-11.1 (1) THE PROPOSED SYSTEM MUST HAVE A VICTIM’S RESPONSE
MODULE THAT FULLY SUPPORTS THE TRACKING OF ALL VICTIMS
OF CRIME THAT INCLUDES THE ABILITY TO INTERFACE TO THE
STATE VOICE SYSTEM AND AT MINIMUM COLLECTS ALL DATA
REQUIRED BY ALL FACETS OF THAT SYSTEM.
4-12 COMMUNITY POLICING SUPPORT SYSTEM
4-12.1 (1) THE PROPOSED RMS APPLICATION SHALL INCLUDE FUNCTIONS
DESIGNED TO SUPPORT COMMUNITY-POLICING EFFORTS.
City of Fort Collins ccxxvii Proposal P-847
4-12.1 (2) THE PROPOSED RMS APPLICATION SHALL ALLOW AN AUTHORIZED
USER TO ASSIGN A PROJECT CODE TO ANY COMMUNITY POLICING
OR OTHER SPECIAL PROJECT.
4-12.1 (3) THE PROPOSED RMS APPLICATION SHALL ALLOW THE USER
AGENCY TO TRACK ALL ACTIVITY AND EFFORTS ASSOCIATED
WITH A COMMUNITY POLICING PROJECT BY ALLOWING OFFICERS
TO ADD THE PROJECT CODE TO INCIDENT REPORTS, FOLLOW-UP
INVESTIGATIONS, ARRESTS, AND ALL OTHER ASSOCIATED
ACTIVITIES.
4-12.1 (4) THE PROPOSED RMS APPLICATION SHALL INCLUDE A LOG FOR
RECORDING COMMUNITY POLICING EFFORTS BY THE USER
AGENCY. THIS LOG SHALL BE SIMILAR TO THE INVESTIGATOR’S
ACTIVITY LOG IN THAT IT WILL RECORD ACTIVITIES THAT ARE
NOT CAPTURED BY THE CAD SYSTEM.
4-12.1 (5) AT A MINIMUM, THE ACTIVITY LOG WILL RECORD THE
FOLLOWING INFORMATION:
4-12.1 (5.1) THE ACTIVITY CODE,
4-12.1 (5.2) THE PROJECT CODE,
4-12.1 (5.3) THE DATE AND TIME OF THE ACTIVITY,
4-12.1 (5.4) THE DURATION OF THE ACTIVITY,
4-12.1 (5.5) THE LOCATION OF THE ACTIVITY,
4-12.1 (5.6) THE NAME OF THE USER CONDUCTING THE ACTIVITY,
4-12.1 (5.7) THE CLASSIFICATION OF THE ACTIVITY,
4-12.1 (5.8) A NOTES FIELD FOR RECORDING ADDITIONAL INFORMATION
ABOUT THE ACTIVITY.
4-12.1 (6) AT A MINIMUM, THE PROPOSED RMS APPLICATION SHALL HAVE
THE ABILITY TO MAINTAIN A LOG OF COMMUNITY POLICING
EFFORTS BY CATEGORY AND LOCATION.
4-12.1 (7) THE PROPOSED RMS APPLICATION SHALL HAVE THE ABILITY TO
MAINTAIN A LIST OF COMMUNITY MEMBERS INVOLVED IN
NEIGHBORHOOD WATCH OR OTHER COMMUNITY POLICING
INITIATIVES. AT A MINIMUM, THIS LIST SHALL INCLUDE THE
FOLLOWING DATA ELEMENTS:
4-12.1 (7.1) COMMUNITY MEMBER’S FULL NAME,
City of Fort Collins ccxxviii Proposal P-847
4-12.1 (7.2) UP TO FOUR TELEPHONE NUMBERS,
4-12.1 (7.3) UP TO TWO EMAIL ADDRESSES, AND
4-12.1 (7.4) UP TO FOUR USER-DEFINED FIELDS FOR DEFINING THE
COMMUNITY MEMBER’S SUBJECTS OF INTEREST.
4-12.1 (8) THE PROPOSED RMS APPLICATION SHALL HAVE THE ABILITY TO
SEND FORM LETTER OR EMAIL MAILINGS TO SOME OR ALL OF THE
PERSONS LISTED IN THE NEIGHBORHOOD WATCH LIST.
4-12.1 (9) IT IS PREFERRED THAT THE PROPOSED RMS APPLICATION INCLUDE
THE ABILITY TO RECEIVE TIPS ON CRIME, QUALITY OF LIFE
PROBLEMS AND DISORDER FROM AN HTML FORM.
4-12.1 (10) IT IS PREFERRED THAT THE PROPOSED RMS APPLICATION ALLOW
THE USER TO CAPTURE EMAILS AND MESSAGES FOR CRIME
PREVENTION AND SCHOOL RESOURCE OFFICERS SUBMITTED
THROUGH THE USER AGENCY WEB SITE.
4-12.1 (10.1) THE RECEIVER SHOULD BE ABLE TO ADD A PROJECT CODE TO
ANY MESSAGE RECEIVED IN THIS MANNER.
4-13 CRIME REPORTING REQUIREMENTS
4-13.1 (1) THE PROPOSED RMS APPLICATION SHALL HAVE THE ABILITY TO
SATISFY THE STATE OF COLORADO REQUIREMENTS FOR THE
COLORADO INCIDENT BASED REPORTING SYSTEM (IBRS) AND THE
NATIONAL INCIDENT BASED REPORTING SYSTEM (NIBRS).
4-13.1 (2) THE PROPOSED RMS APPLICATION SHALL EDIT RECORDS FOR
IBRS/NIBRS VALIDITY AND CONSISTENCY AS PRESCRIBED BY THE
COLORADO BUREAU OF INVESTIGATION (CBI).
4-13.1 (3) THE PROPOSED RMS APPLICATION SHALL HAVE THE ABILITY TO
TRANSMIT IBRS/NIBRS REPORTS TO CBI ELECTRONICALLY OR VIA
MAGNETIC MEDIA.
4-13.1 (4) THE PROPOSED RMS APPLICATION SHALL BE ABLE TO MAINTAIN,
AT A MINIMUM, FIFTEEN YEARS OF INCIDENT BASED REPORTING
(IBRS/NIBRS) DATA ON THE USER AGENCY SYSTEM FOR
ANALYTICAL AND STATISTICAL REPORTING PURPOSES.
4-13.1 (5) THE PROPOSED RMS APPLICATION SHALL ALLOW AUTHORIZED
USERS TO RECLASSIFY PRIOR INCIDENTS.
4-13.1 (6) THE PROPOSED RMS APPLICATION SHALL REPORT THE CORRECT
STATISTICAL COUNTS FOR CRIMES AND EVENTS EVEN WHEN A
City of Fort Collins ccxxix Proposal P-847
CASE IS CHANGED. FOR EXAMPLE, ASSUME THE USER AGENCY
HAD ONE HOMICIDE LAST QUARTER AND NONE THIS QUARTER.
THEN ASSUME THAT THE CLASSIFICATION FOR THE HOMICIDE
LAST QUARTER IS CHANGED TO ACCIDENTAL DEATH. THE
HOMICIDE COUNT FOR THIS QUARTER AND LAST QUARTER
SHOULD BOTH SHOW ZERO.
4-13.1 (7) THE PROPOSED RMS APPLICATION SHALL INCLUDE A STATISTICAL
REPORT OF IBRS/NIBRS OFFENSES BY OFFENSE TYPE FOR HARD
COPY.
4-13.1 (8) THE PROPOSED RMS APPLICATION SHALL INCLUDE THE
CAPABILITY TO DISPLAY OR PRINT INDIVIDUAL RECORDS.
4-13.1 (9) THE PROPOSED RMS APPLICATION SHALL HAVE THE ABILITY TO
PRINT IBRS/NIBRS REPORTS IN THE SAME FORMAT AS ALL OF THE
REPORTS DISTRIBUTED BY THE CBI FOR COMPARISON PURPOSES.
4-13.1 (10) THE PROPOSED RMS APPLICATION SHALL INCLUDE THE
FOLLOWING INTERNAL REPORTS:
4-13.1 (10.1) ARSON REPORT,
4-13.1 (10.2) HOMICIDE REPORT,
4-13.1 (10.3) USE OF FORCE,
4-13.1 (10.4) ARREST & CITATION LOG,
4-13.1 (10.5) ARRESTED PERSONS (ADULT AND JUVENILE) BY AGE, GENDER,
ETHNICITY AND CHARGE,
4-13.1 (10.6) HATE CRIMES,
4-13.1 (10.7) DOMESTIC VIOLENCE,
4-13.1 (10.8) PROPERTY STOLEN, BY CLASSIFICATION AND TYPE,
4-13.1 (10.9) LAW ENFORCEMENT OFFICERS KILLED AND ASSAULTED,
4-13.1 (10.10) AND PROPERTY RECOVERED TALLY – THEFT TALLY, MOTOR
VEHICLE THEFT TALLY.
4-13.1 (11) THE PROPOSED RMS APPLICATION SHALL INCLUDE THE
CAPABILITY TO DISPLAY OR PRINT ANY OF THE ABOVE-LISTED
REPORTS.
City of Fort Collins ccxxx Proposal P-847
4-14 MISCELLANEOUS APPLICATIONS
4-14.1 PAWN MODULE
4-14.1 (1) THE PROPOSED RMS APPLICATION SHALL INCLUDE THE ABILITY
TO CAPTURE ALL CBI-REQUIRED FIELDS AND FORMATS FOR PAWN
TICKETS.
4-14.1 (2) EACH TIME A NEW PAWN RECORD IS ENTERED, THE PAWN MODULE
SHALL AUTOMATICALLY COMPARE THE PAWNED ITEM AGAINST
THE RMS FILES TO DETERMINE IF THE ITEM HAS BEEN
PREVIOUSLY REPORTED STOLEN.
4-14.1 (3) THE PROPOSED RMS APPLICATION SHALL BE ABLE TO ENTER AND
TRACK A PAWN TICKET NUMBER ASSIGNED BY INDIVIDUAL
PAWNBROKERS.
4-14.1 (4) THE PROPOSED RMS APPLICATION SHALL BE ABLE TO ENTER AND
TRACK THE PAWN SHOP AND PAWNBROKER WHERE ITEM IS
PAWNED.
4-14.1 (5) THE PROPOSED RMS APPLICATION SHALL BE ABLE TO ENTER AND
TRACK POLICE HOLDS BY:
4-14.1 (5.1) CASE (REPORT) NUMBER
4-14.1 (5.2) DATE OF HOLD
4-14.1 (5.3) OFFICER PLACING HOLD
4-14.1 (5.4) PAWNBROKER NOTIFIED OF HOLD
4-14.1 (5.5) HOLD EXPIRATION DATE TO BE CONFIGURABLE BY SYSTEM
ADMIN
4-14.1 (6) IT IS DESIRED THAT THE PROPOSED RMS APPLICATION HAVE THE
ABILITY TO DISPLAY BOTH EXACT AND SIMILAR ITEMS. FOR
EXAMPLE, IF THE ITEM PAWNED IS THE SAME BRAND, MAKE AND
MODEL BUT A DIFFERENT COLOR OR SERIAL NUMBER IT SHOULD
RETURN A NOTIFICATION.
4-14.1 (7) THE PROPOSED RMS APPLICATION SHALL HAVE THE ABILITY TO
AUTOMATICALLY TRANSMIT PAWN RECORDS (PROPERTY AND
NAME INFORMATION) VIA THE INTERFACE TO CBI TO CHECK FOR
STOLEN.
City of Fort Collins ccxxxi Proposal P-847
4-14.1 (8) THE PROPOSED RMS APPLICATION SHALL HAVE THE ABILITY TO
AUTOMATICALLY RECORD AN ACKNOWLEDGEMENT FOR EACH
RECORD FROM CBI.
4-14.1 (9) IT IS DESIRED THAT THE PROPOSED RMS APPLICATION HAVE THE
ABILITY TO ENTER PAWN INFORMATION INTO THE ARTICLE FILE IN
CCIC WHEN ENTERED INTO THE RMS SYSTEM.
4-14.1 (10) IT IS DESIRED THAT THE PROPOSED RMS APPLICATION HAVE THE
ABILITY TO ACCEPT PAWN TICKETS FROM PAWNSHOPS
ELECTRONICALLY.
4-14.1 (11) THE PROPOSED RMS APPLICATION SHALL INCLUDE THE
CAPABILITY TO PRINT OR DISPLAY A LIST OF POTENTIAL MATCHES
OF STOLEN PROPERTY AGAINST PAWN MODULE RECORDS.
4-14.1 (12) THE PROPOSED RMS APPLICATION SHALL INCLUDE THE
FOLLOWING PAWNED PROPERTY REPORTS:
4-14.1 (12.1) A ONE-LINE LIST OF PAWNED PROPERTY FOR A GIVEN DATE
RANGE SORTED BY CATEGORY, THEN BY BRAND NAME, WITH
THE SERIAL NUMBER AND DESCRIPTION FOR EACH PIECE
LISTED.
4-14.1 (12.2) A LIST OF FREQUENT (THRESHOLD OF FREQUENCY USER
DEFINABLE) PAWNERS, SORTED IN DESCENDING ORDER BY THE
NUMBER OF ITEMS PAWNED.
4-14.1 (13) IT IS DESIRED THAT THE PROPOSED RMS APPLICATION REJECT OR
MAKE SOME TYPE OF NOTIFICATION THAT THE PERSON PAWNING
THE PROPERTY IS UNDER THE AGE OF 18 ON THE DATE OF PAWN.
4-14.1 (14) IT IS DESIRED THAT THE PROPOSED RMS APPLICATION IDENTIFY
INDIVIDUALS WHO USE A PAWNSHOP MORE THAN ONCE A DAY OR
ANY PAWNSHOP MORE THAN FOUR TIMES PER WEEK.
4-14.1 (14.1) TIME PARAMETERS (THRESHOLDS) FOR ALERTS SHALL BE USER
CONFIGURABLE
4-14.1 (14.2) ONCE THE IDENTIFICATION IS MADE, IT IS DESIRED THAT THE
PROPOSED RMS APPLICATION SHALL MAKE SOME TYPE OF
NOTIFICATION TO A USER-DEFINED INDIVIDUAL(S).
4-14.1 (15) THE PROPOSED RMS APPLICATION SHALL HAVE THE ABILITY TO
GENERATE REPORT LISTING ALL OUT OF AREA PAWNERS.
4-14.1 (16) THE PROPOSED RMS APPLICATION SHALL TRACK ALL PAWN
FORFEITURE REPORTS.
City of Fort Collins ccxxxii Proposal P-847
4-14.1 (17) THE PROPOSED RMS APPLICATION SHALL HAVE THE ABILITY TO
TRACK PAWNERS PROHIBITED BY COURT ORDER OR CITY
ORDINANCE.
4-14.2 TOWING AND IMPOUNDMENT RECORDS
4-14.2 (1) THE PROPOSED RMS APPLICATION SHALL MAINTAIN A FILE OF ALL
VEHICLES THAT HAVE BEEN TOWED OR IMPOUNDED BY THE USER
AGENCY OR LOCAL TOW COMPANIES.
4-14.2 (2) THE PROPOSED RMS APPLICATION SHALL ALLOW AN OFFICER TO
COMPLETE THE TOW REPORT DIRECTLY FROM A MOBILE
COMPUTER, WHEN CONNECTION AVAILABLE, AND SEND IT TO A
TOW COMPANY VIA A FAX MODEM ACCESSIBLE FROM THE RMS
SERVER.
4-14.2 (3) AT A MINIMUM THE TOW RECORD SHALL INCLUDE THE:
4-14.2 (3.1) ALL THE INFORMATION CONTAINED IN THE MNI, MLI, & MVI FOR
EACH TOWED VEHICLE AND;
4-14.2 (3.2) CASE (REPORT) NUMBER,
4-14.2 (3.3) NOTES, E.G. PREVIOUS DAMAGE TO THE VEHICLE,
4-14.2 (3.4) LOCATION WHERE VEHICLE WAS TOWED FROM,
4-14.2 (3.5) LIST OF PROPERTY IN VEHICLE,
4-14.2 (3.6) REASON FOR TOWING,
4-14.2 (3.7) CIVIL SEIZURE (YES OR NO),
4-14.2 (3.8) POLICE HOLD (YES OR NO),
4-14.2 (3.9) NAME OF EMPLOYEE AUTHORIZING RELEASE OF VEHICLE,
4-14.2 (3.10) RELEASE DATE AND TIME,
4-14.2 (3.11) PERSON TO WHICH VEHICLE WAS RELEASED,
4-14.2 (3.12) NAME OF TOWING COMPANY,
4-14.2 (3.13) STORAGE LOCATION,
4-14.2 (3.14) DATE AND TIME TOW OCCURRED,
4-14.2 (3.15) AND OFFICER ORDERING TOW OR RECEIVING NOTIFICATION OF
TOW.
City of Fort Collins ccxxxiii Proposal P-847
4-14.2 (4) IN THE EVENT THAT A VEHICLE IS TOWED IN CONJUNCTION WITH
A CASE, THE TOW RECORD SHALL BE LINKED TO THE CASE
RECORD AND SHALL BE RETRIEVABLE BY A CASE (REPORT)
NUMBER SEARCH.
4-14.2 (5) THE PROPOSED RMS APPLICATION SHALL ALLOW THE ENTRY
PERSON TO REQUEST A CHECK OF CCIC/NCIC TO DETERMINE IF
THE TOWED VEHICLE HAS BEEN REPORTED STOLEN IN ANOTHER
JURISDICTION.
4-14.2 (6) THE PROPOSED RMS APPLICATION SHALL HAVE THE ABILITY TO
FORMAT AND SEND AN UPDATE MESSAGE TO CCIC EACH TIME A
NEW VEHICLE IS ENTERED AS TOWED OR IMPOUNDED.
4-14.2 (7) THE PROPOSED RMS APPLICATION SHOULD INCLUDE THE ABILITY
TO ATTACH THE CCIC/NCIC RETURN TO THE TOW RECORD.
4-14.3 FIELD INTERVIEW
4-14.3 (1) THE PROPOSED RMS APPLICATION SHALL INCLUDE A MODULE
THAT WILL BE USED TO ENTER FIELD INTERVIEW INFORMATION.
4-14.3 (2) THE FIELD INTERVIEW MODULE WILL INTERFACE WITH THE
MASTER INDEXES SUCH THAT PERSONS ENTERED INTO THE FIELD
INTERVIEW MODULE WILL BE FOUND BY NAME, LOCATION OR
OTHER MASTER INDEX SEARCHES.
4-14.3 (3) AT A MINIMUM, THE FIELD INTERVIEW MODULE SHALL INCLUDE
THE FOLLOWING DATA FIELDS:
4-14.3 (3.1) UNIQUE SYSTEM-GENERATED NUMBER OR CASE (REPORT)
NUMBER,
4-14.3 (3.2) ALL THE INFORMATION CONTAINED IN THE MNI, MLI, MVI,
MUGSHOT MODULE, AND OFFENDER MODULE FOR EACH
PERSON CONTACTED AND;
4-14.3 (3.3) OFFICER NAME, ID AND ROLE
4-14.3 (3.4) REASON INDIVIDUAL WAS CONTACTED,
4-14.3 (3.5) LOCATION WHERE INDIVIDUAL WAS CONTACTED,
4-14.3 (3.6) DATE AND TIME INDIVIDUAL WAS CONTACTED,
4-14.3 (3.7) AND NARRATIVE.
City of Fort Collins ccxxxiv Proposal P-847
4-14.3 (4) FI FORM SHALL BE CONFIGURABLE TO RETAIN DATA ENTRY IN
FIELDS WHEN FORM IS SUBMITTED TO THE SYSTEM WHEN
SEVERAL INDIVIDUALS ARE CONTACTED (I.E., SAME DATE, TIME,
LOCATION, ETC.)
4-14.4 LICENSES
4-14.4 (1) THE PROPOSED RMS APPLICATION SHALL INCLUDE A LICENSE
MODULE THAT CAN BE USED TO TRACK BICYCLES, GUNS,
CONCEALED WEAPONS PERMITS, AND OTHER ITEMS.
4-14.4 (2) THE PROPOSED RMS APPLICATION SHALL ASSIGN A UNIQUE
LICENSE NUMBER BY LICENSE TYPE FOR EACH NEW RECORD THAT
IS ENTERED.
4-14.4 (3) AT A MINIMUM, THE LICENSE RECORD SHALL INCLUDE THE
FOLLOWING DATA FIELDS:
4-14.4 (3.1) ALL THE INFORMATION CONTAINED IN THE MNI, MLI, & MPI, FOR
EACH LICENSE ISSUED AND;
4-14.4 (3.2) LICENSE TYPE, (E.G. GUN, LIQUOR, CCW, ETC.)
4-14.4 (3.3) ASSOCIATED PROPERTY RECORDS,
4-14.4 (3.4) REGISTRATION DATE,
4-14.4 (3.5) AND EXPIRATION DATE.
4-14.4 (4) THE PROPOSED RMS APPLICATION SHALL HAVE THE ABILITY TO
CHECK CCIC/NCIC UPON ENTRY OF AN ITEM BEING LICENSED
(BIKE, GUN, ETC.) TO DETERMINE IF THE ITEM IS LISTED AS
STOLEN IN ANOTHER JURISDICTION.
4-14.5 BICYCLE REGISTRATION
Bicycle registrations and licensing are entered and maintained through this module.
4-14.5 (1) THE PROPOSED RMS APPLICATION SHALL INCLUDE THE ABILITY
TO CAPTURE ALL DESIGNATED FIELDS FOR BICYCLE
REGISTRATIONS TO INCLUDE THE FOLLOWING:
4-14.5 (1.1) ALL THE INFORMATION CONTAINED IN THE MNI, MLI, & MPI FOR
EACH BICYCLE REGISTERED AND;
4-14.5 (1.2) A PERSON ROLE AS OWNER,
4-14.5 (1.3) DATE OF REGISTRATION,
City of Fort Collins ccxxxv Proposal P-847
4-14.5 (1.4) REGISTRATION DURATION (TIME TO EXPIRE),
4-14.5 (1.5) REGISTRATION NUMBER,
4-14.5 (1.6) ASSOCIATED PROPERTY RECORD,
4-14.5 (1.7) BICYCLE FRAME STYLE,
4-14.5 (1.8) BICYCLE FRAME SIZE,
4-14.5 (1.9) AND A NARRATIVE FIELD FOR A MORE COMPLETE DESCRIPTION
AND TO LIST DISTINGUISHING FEATURES.
4-14.5 (2) IN ADDITION, IT IS DESIRED THE SYSTEM INCLUDE THE ABILITY TO
ATTACH IMAGES (I.E. DIGITAL PHOTOS) CORRESPONDING TO EACH
REGISTRATION.
4-14.5 (3) WHEN THE BICYCLE SERIAL NUMBER IS ENTERED, THE BICYCLE
REGISTRATION MODULE SHALL AUTOMATICALLY COMPARE THE
BICYCLE AGAINST THE MPI TO DETERMINE IF THE BICYCLE HAS
PREVIOUSLY BEEN ENTERED INTO THE SYSTEM AND THEN TO
NOTIFY THE ENTRY PERSON OF THE TYPES OF INVOLVEMENT.
4-14.5 (4) WHEN A BICYCLE SERIAL NUMBER IS ENTERED, IT IS DESIRED
THAT SYSTEM WOULD BE ABLE TO CHECK THE SERIAL NUMBER
THROUGH NCIC/CCIC FILES FOR STOLEN ENTRIES.
4-14.5 (5) THE SYSTEM MUST ALSO BE ABLE TO PERFORM SERIAL NUMBER
SEARCHES FOR REGISTRATION CHECKS OF SUSPECTED STOLEN
BICYCLES.
4-14.5 (6) THE BICYCLE INFORMATION SHALL BECOME PART OF THE MPI.
4-14.5 (7) PARTICIPATING AGENCIES USING THIS MODULE SHALL BE ABLE TO
DETERMINE THEIR OWN BEGINNING REGISTRATION NUMBER.
4-14.5 (8) THE PROPOSED RMS APPLICATION SHALL PROVIDE A SINGLE
QUERY THAT WILL RETURN A LIST OF ALL EXPIRED BICYCLE
REGISTRATIONS.
4-14.5 (9) IT IS DESIRED THAT WRITTEN WARNINGS FOR BICYCLE TRAFFIC
VIOLATIONS BE CAPABLE OF BEING ENTERED IN A SIMILAR
MANNER AS VEHICULAR TRAFFIC WARNINGS.
4-14.5 (10) IT IS DESIRED THAT THE SYSTEM HAVE THE ABILITY TO BE
CHANGED OVER TO A BAR CODING SYSTEM IF THE REGISTERING
AGENCY SO DESIRES. THIS SYSTEM SHOULD INCLUDE:
City of Fort Collins ccxxxvi Proposal P-847
4-14.5 (10.1) ABILITY TO PRINT INDIVIDUAL LABELS (LICENSES) INCLUDING
THE REGISTRATION NUMBER AND A BAR CODE MATCHING THE
REGISTRATION NUMBER.
4-14.5 (10.2) ABILITY TO READ A BARCODE FROM A DRIVER'S LICENSE OR
STUDENT REGISTRATION CARD FOR OWNER INFORMATION
WHICH WILL AUTOMATICALLY BE DOWNLOADED INTO THE
REGISTRATION RECORD.
4-14.5 (11) THE SYSTEM SHALL HAVE THE ABILITY TO PROVIDE A BICYCLE
REGISTRATION LIST BY NAME, SERIAL NUMBER, LICENSE NUMBER,
FRAME NUMBER, AND DATE RANGE (EITHER REGISTRATION DATE
OR EXPIRATION DATE).
4-14.6 ALARM TRACKING
4-14.6 (1) THE PROPOSED RMS APPLICATION SHALL INCLUDE AN ALARM
REGISTRATION AND FALSE ALARM TRACKING MODULE.
4-14.6 (2) AT A MINIMUM, THE ALARM REGISTRATION RECORD SHALL
INCLUDE THE FOLLOWING DATA FIELDS:
4-14.6 (2.1) THE LOCATION WHERE THE ALARM IS INSTALLED.
4-14.6 (2.2) THE NAME, ADDRESS AND PHONE NUMBER FOR THE OWNER(S)
OF THE PREMISES,
4-14.6 (2.3) THE NAME, ADDRESS AND TELEPHONE NUMBER FOR THE
PERSON(S) OR FIRM(S) RESPONSIBLE FOR RESPONDING WHEN AN
ALARM SOUNDS
4-14.6 (2.4) THE NAME, ADDRESS AND TELEPHONE NUMBER FOR THE
PERSON(S) OR FIRM(S) RESPONSIBLE FOR MAINTAINING THE
ALARM,
4-14.6 (2.5) THE REGISTRATION EXPIRATION DATE,
4-14.6 (2.6) THE TYPE OF ALARM (SILENT, AUDIBLE, ETC.),
4-14.6 (2.7) AND A UNIQUE ALARM REGISTRATION NUMBER FOR EACH
RECORD.
4-14.6 (3) THE PROPOSED RMS APPLICATION SHALL HAVE THE ABILITY TO
RECEIVE ALARM ACTIVATION REPORTS FROM THE CAD
APPLICATION.
4-14.6 (4) THE PROPOSED RMS APPLICATION SHALL HAVE THE ABILITY TO
RETRIEVE ALARM ACTIVATIONS BY:
City of Fort Collins ccxxxvii Proposal P-847
4-14.6 (4.1) ALARM LOCATION,
4-14.6 (4.2) BUSINESS NAME
4-14.6 (4.3) BUILDING OWNER NAME(S),
4-14.6 (4.4) NAME OF PERSON(S) RESPONSIBLE FOR MAINTAINING THE
ALARM, AND
4-14.6 (4.5) NUMBER OF ACTIVATIONS FOR A GIVEN DATE RANGE
4-14.6 (5) THE PROPOSED RMS APPLICATION SHALL INCLUDE THE ABILITY
TO RECORD THE COLLECTION OF ALARM REGISTRATION FEES.
4-14.6 (6) THE PROPOSED RMS APPLICATION SHALL INCLUDE THE ABILITY
TO PRINT AND SEND VIOLATION NOTICES TO THE OWNERS’ OF
BUILDINGS WHOSE PROPERTIES HAVE HAD MORE THAN A USER-
DEFINED NUMBER OF FALSE ALARMS IN A USER-DEFINED DATE
RANGE.
4-14.6 (7) THE PROPOSED RMS APPLICATION SHALL INCLUDE BASIC CASE
MANAGEMENT PROCEDURES FOR FALSE ALARM VIOLATIONS. (IT
IS ACCEPTABLE TO USE THE STANDARD CASE MANAGEMENT
MODULE. IF THIS IS PROPOSED, EXPLAIN HOW IT WILL WORK.)
4-14.6 (8) THE PROPOSED RMS APPLICATION SHALL ALLOW FOR INCIDENT
TRANSFER FROM CAD OF DISPATCHED INCIDENTS IDENTIFIED AS
FALSE ALARMS.
4-15 RMS REPORTS
4-15.1 CRIME AND EVENT REPORTS
4-15.1 (1.1) THE PROPOSED RMS APPLICATION SHALL ALLOW FOR PRINTING
OF ALL RECORDS ASSOCIATED WITH A USER-DEFINED NAME. AT
A MINIMUM, THE FOLLOWING INFORMATION SHOULD PRINT:
4-15.1 (1.2) NAME,
4-15.1 (1.3) DATE OF BIRTH,
4-15.1 (1.4) CURRENT ADDRESS,
4-15.1 (1.5) CURRENT TELEPHONE NUMBER,
4-15.1 (1.6) PHYSICAL DESCRIPTION,
4-15.1 (1.7) ALIAS OR AKA,
City of Fort Collins ccxxxviii Proposal P-847
4-15.1 (1.8) ALL CONTACTS ASSOCIATED WITH INDIVIDUAL,
4-15.1 (2) THE PROPOSED RMS APPLICATION SHALL ALLOW FOR THE
FOLLOWING TO PRINT ON ALL REPORTS PRINTED (I.E. CASE
REPORTS, MASTER NAME SEARCHES, MASTER VEHICLE SEARCHES,
ETC.):
4-15.1 (2.1) AGENCY NAME,
4-15.1 (2.2) AGENCY ADDRESS,
4-15.1 (2.3) AGENCY TELEPHONE NUMBER,
4-15.1 (2.4) DATE,
4-15.1 (2.5) TIME, AND
4-15.1 (2.6) NAME OF USER LOGGED ON TO SYSTEM AT TIME OF PRINT.
4-15.1 (3) THE PROPOSED RMS APPLICATION SHALL INCLUDE THE ABILITY
TO PRINT A COPY OF ANY CRIME OR EVENT (E.G. TRAFFIC
ACCIDENT) REPORT.
4-15.1 (4) CRIME AND EVENT REPORTS SHALL BE CONSPICUOUSLY MARKED
“UNAPPROVED” IN THE EVENT THAT THE RESPONSIBLE
SUPERVISOR HAS NOT APPROVED THE REPORT AT THE TIME IT IS
PRINTED.
4-15.1 (5) THE PROPOSED RMS APPLICATION SHALL INCLUDE A JUVENILE
OFFENSE SUMMARY REPORT WHICH PROVIDES A SUMMARY OF
OFFENSES INVOLVING JUVENILES BUT WHICH DOES NOT IDENTIFY
JUVENILE DEFENDANTS.
4-15.1 (6) THE PROPOSED RMS APPLICATION SHALL INCLUDE A REPORT
LISTING OFFENSES AND CALLS FOR SERVICE BY ADDRESS OR BY
USER-DEFINED MAP LOCATION.
4-15.1 (7) THE PROPOSED RMS APPLICATION SHALL INCLUDE AN INCIDENT
LOG THAT SHALL PRINT A LIST OF COMPLAINTS WITH THE TIME,
NATURE, AND CASE (REPORT) NUMBER, IF ANY, FOR A USER-
DEFINED DATE.
4-15.1 (8) THE PROPOSED RMS APPLICATION SHALL INCLUDE A SUMMARY OF
OFFENSES REPORT THAT PROVIDES A SUMMARY OF EACH OFFENSE
INCLUDING THE DATE, TIME, TYPE, LOCATION OF OCCURRENCE,
AND STATUS OF EACH OFFENSE FOR A USER- DEFINED DATE RANGE.
City of Fort Collins ccxxxix Proposal P-847
4-15.2 INVESTIGATIVE & CRIME ANALYSIS REPORTS
4-15.2 (1) THE PROPOSED RMS APPLICATION SHALL INCLUDE THE ABILITY
TO PROVIDE PERIODIC AND COMPARATIVE CRIME STATISTICS BY
OFFENSE TYPE.
4-15.2 (2) THE PROPOSED RMS APPLICATION SHALL INCLUDE STATISTICAL
REPORTS OF INCIDENTS AND CRIMES BY:
4-15.2 (2.1) USER-DEFINED ADDRESS,
4-15.2 (2.2) PATROL DISTRICT,
4-15.2 (2.3) ANY GEOGRAPHIC AREA DEFINED IN THE MAPPING SYSTEM,
4-15.2 (2.4) ANY USER-DEFINED GEOGRAPHIC AREA,
4-15.2 (2.5) DAY OF WEEK,
4-15.2 (2.6) TIME RANGE,
4-15.2 (2.7) DATE RANGE, OR
4-15.2 (2.8) ANY COMBINATION OF THE ABOVE.
4-15.2 (3) THE PROPOSED RMS APPLICATION SHALL INCLUDE A REPORT
THAT LISTS ALL CALLS FOR SERVICE OR CRIMES OCCURRING
DURING A USER-DEFINED DATE RANGE SORTED BY PATROL AREA.
4-15.2 (4) THE PROPOSED RMS APPLICATION SHALL INCLUDE AN OFFENSE
COMPARISON REPORT WHICH LISTS CRIMES BY STATE STATUTE OR
IBRS CODE, BY MONTH WITH COMPARISONS WITH PRIOR MONTH
AND SAME MONTH PRIOR YEAR, AND YEAR TO DATE TOTALS.
4-15.2 (5) THE PROPOSED RMS APPLICATION SHALL INCLUDE A REPORT
THAT SHOWS LOCATIONS THAT ARE EXPERIENCING THE CALLS
FOR SERVICE OR CRIMES THAT EXCEED A USER-DEFINED
THRESHOLD FOR A USER-DEFINED DATE RANGE (HOT
SPOT/EXCEPTION REPORT).
4-15.2 (6) THE USER SHALL BE ABLE TO DEFINE THE RADIUS OR PROXIMITY
INSIDE WHICH ALL ADDRESSES WILL BE CONSIDERED A SINGLE
ADDRESS WHEN SEARCHING FOR HOT SPOTS. FOR EXAMPLE, 123
MAIN STREET MIGHT BE WITHIN TWO BLOCKS OF 1ST AND MAIN
AND THEREFORE THEY SHOULD BE CONSIDERED THE SAME
ADDRESS FOR HOT SPOT REPORTING PURPOSES.
City of Fort Collins ccxl Proposal P-847
4-15.2 (7) THE PROPOSED RMS APPLICATION SHALL HAVE THE ABILITY TO
PLOT THE RESULTS OF ANY SEARCH ON A MAP SO LONG AS THE
RESULT OF THE SEARCH INCLUDES ADDRESSES THAT ARE IN THE
GEOFILE.
4-15.2 (8) THE PROPOSED RMS APPLICATION SHALL INCLUDE THE ABILITY
TO ADD A GRAPH OR CHART TO ANY REPORT THAT CONTAINS
STATISTICAL DATA.
4-15.3 CASE MANAGEMENT REPORTS
4-15.3 (1) THE PROPOSED RMS APPLICATION SHALL INCLUDE A REPORT
SHOWING ALL ACTIVE CASES SORTED BY ASSIGNED INVESTIGATOR
OR OFFICER WITH OFFENSE TYPE AND CASE (REPORT) NUMBER
INCLUDED (CASES BY INVESTIGATOR).
4-15.3 (2) THE PROPOSED RMS APPLICATION SHALL INCLUDE A REPORT
SHOWING ALL ACTIVE CASES SORTED BY OFFENSE TYPE WITH THE
ASSIGNED OFFICER, AND CASE (REPORT) NUMBER INCLUDED
(CASES BY TYPE).
4-15.3 (3) THE PROPOSED RMS APPLICATION SHALL INCLUDE A REPORT
THAT SHOWS THE CASES CLOSED FOR A GIVEN DATE RANGE
SORTED AND SUBTOTALED BY INVESTIGATOR (CASE CLOSURE
REPORT).
4-15.3 (4) THE PROPOSED RMS APPLICATION SHALL INCLUDE A REPORT
THAT SHOWS THE CASES CLOSED FOR A GIVEN DATE RANGE
SORTED AND SUBTOTALED BY ORGANIZATIONAL UNIT (CASE
CLOSURE REPORT - UNIT)
4-15.3 (5) THE PROPOSED RMS APPLICATION SHALL INCLUDE A REPORT
THAT SHOWS A STATISTICAL COMPARISON OF CLOSURES FOR ALL
INVESTIGATORS DURING A USER-DEFINED DATE RANGE
(CLEARANCE REPORT).
4-15.3 (6) THE PROPOSED RMS APPLICATION SHALL INCLUDE A REPORT
WHICH LISTS THE ASSIGNED INVESTIGATOR AND CASE (REPORT)
NUMBER FOR EACH ACTIVE CASE WHICH IS 30, 60, OR 90+ DAYS OLD
OR OTHER USER-DEFINED PARAMETER (CASE AGING REPORT).
4-15.3 (7) THE PROPOSED RMS APPLICATION SHALL INCLUDE A REPORT
THAT PROVIDES A SUMMARY OF ALL INVESTIGATIVE ACTIONS
TAKEN ON EACH ACTIVE CASE DURING A USER-DEFINED PERIOD.
THIS REPORT SHALL BE FOR ONE OR MORE OFFICERS AT THE
USERS DISCRETION (CASE STATUS REPORT).
City of Fort Collins ccxli Proposal P-847
4-15.3 (8) THE PROPOSED RMS APPLICATION SHALL INCLUDE A REPORT
WHICH DETAILS, BY INVESTIGATOR OR OTHER EMPLOYEE AND
DATE RANGE, A COUNT OF ASSIGNED AND CLOSED REPORTS AND
THE RATIO OF CLOSED TO ASSIGNED CASES (CASE MANAGEMENT
REPORT).
4-15.3 (9) THE PROPOSED RMS APPLICATION SHALL INCLUDE A REPORT
THAT LISTS THE PROPERTY ASSOCIATED WITH A CASE. THIS
REPORT SHALL INCLUDE A SUMMARY DESCRIPTION OF THE
PROPERTY AND A STATUS (STOLEN, RECOVERED, EVIDENCE, ETC.)
FOR EACH ITEM.
4-15.3 (10) THE PROPOSED RMS APPLICATION SHALL INCLUDE A REPORT
THAT LISTS ALL PENDING OR UNAPPROVED REPORTS FOR A GIVEN
OFFICER OR UNIT, AND DATE RANGE (PENDING REPORTS).
4-15.3 (11) THE PROPOSED RMS APPLICATION SHALL HAVE THE ABILITY TO
PRINT AN AUDIT TRAIL REPORT SHOWING ALL ACTIONS
CONCERNED WITH A CASE FROM BEGINNING TO END, INCLUDING
PRELIMINARY INVESTIGATIVE EFFORTS MADE BY PATROL.
4-15.3 (12) THE PROPOSED RMS APPLICATION SHALL PROVIDE AN EASY
MEANS TO CLOSE A CASE IN THE EVENT THAT A SUSPECT IS
ARRESTED BY ANOTHER JURISDICTION.
4-15.3 (13) THE PROPOSED RMS APPLICATION SHALL INCLUDE A REPORT
THAT DETAILS EACH INVESTIGATIVE ACTION COMPLETED FOR A
GIVEN CASE WITH THE TOTAL TIME EXPENDED ON THE REPORT.
4-15.3 (14) THE PROPOSED RMS APPLICATION SHALL INCLUDE A REPORT
THAT DETAILS THE INVESTIGATIVE TIME ALLOCATED TO A GIVEN
CASE SUBTOTALED BY OFFICER OR INVESTIGATOR.
4-15.3 (15) THE PROPOSED RMS APPLICATION SHALL INCLUDE A REPORT
THAT SHOWS THE TOTAL INVESTIGATIVE TIME EXPENDED FOR A
USER-DEFINED OFFICER AND DATE RANGE, SUBTOTALED BY CASE
(REPORT) NUMBER.
4-15.3 (16) THE PROPOSED APPLICATION SHALL INCLUDE THE ABILITY FOR
INVESTIGATORS TO PRINT ALL NOTES ASSOCIATED WITH A CASE
AT ONE TIME.
4-15.3 (17) THE PROPOSED APPLICATION SHALL INCLUDE A REPORT THAT
ALLOWS AN INDIVIDUAL USER TO PRINT ANY REMINDERS
ASSOCIATED WITH A CASE TO WHICH THEY ARE ASSIGNED. AT A
MINIMUM, THE REPORT SHALL INCLUDE:
4-15.3 (17.1.1) THE CASE (REPORT) NUMBER,
City of Fort Collins ccxlii Proposal P-847
4-15.3 (17.1.2) DEFENDANT OR COMPLAINANT’S NAME,
4-15.3 (17.1.3) THE REMINDER DATE,
4-15.3 (17.1.4) THE REMINDER TEXT, AND
4-15.3 (17.1.5) STATUS.
4-15.4 ARREST REPORTS
4-15.4 (1) THE PROPOSED RMS APPLICATION SHALL INCLUDE A REPORT
THAT PROVIDES A STATISTICAL BREAKDOWN OF ADULT ARRESTS
BY CRIME CATEGORY WITH MONTH-TO-DATE AND YEAR-TO-DATE
COMPARISONS.
4-15.4 (2) THE PROPOSED RMS APPLICATION SHALL INCLUDE A REPORT
THAT PROVIDES A STATISTICAL BREAKDOWN OF JUVENILE
ARRESTS BY CRIME CATEGORY WITH MONTH-TO-DATE AND YEAR-
TO-DATE COMPARISONS.
4-15.4 (3) THIS REPORT SHALL INCLUDE CASE DISPOSITION, CASE (REPORT)
NUMBER, AND COURT DISPOSITION.
4-15.5 PROPERTY AND EVIDENCE REPORTS
4-15.5 (1) THE PROPOSED RMS APPLICATION SHALL INCLUDE A LISTING OF
ALL PROPERTY IN THE DATABASE BY STORAGE LOCATION.
4-15.5 (2) THE PROPOSED RMS APPLICATION SHALL INCLUDE A LISTING OF
ALL PROPERTY BY SEIZING OR RECOVERING OFFICER.
4-15.5 (3) THIS REPORT SHALL INCLUDE THE CASE (REPORT) NUMBER AND
DISPOSITION IF AVAILABLE.
4-15.6 TRAFFIC REPORTS
4-15.6 (1) THE PROPOSED SYSTEM SHALL INCLUDE A SUMMARY REPORT OF
CITATIONS ISSUED BY:
4-15.6 (1.1) USER SPECIFIED OFFICER FOR A GIVEN DATE AND TIME RANGE,
4-15.6 (1.2) USER SPECIFIED SQUAD, FOR A GIVEN DATE AND TIME RANGE,
4-15.6 (1.3) USER SPECIFIED DISTRICT FOR A GIVEN DATE AND TIME RANGE,
4-15.6 (1.4) USER SPECIFIED SHIFT FOR A GIVEN DATE AND TIME RANGE,
4-15.6 (1.5) FOR ALL OFFICERS FOR A GIVEN DATE AND TIME RANGE,
City of Fort Collins ccxliii Proposal P-847
4-15.6 (1.6) OFFENSE LOCATION FOR A GIVEN DATE AND TIME RANGE, OR
4-15.6 (1.7) OFFENSE TYPE FOR A GIVEN DATE AND TIME RANGE.
4-15.6 (2) THE PROPOSED SYSTEM SHALL PROVIDE A STATISTICAL SUMMARY
OF CITATION ACTIVITY BY:
4-15.6 (2.1) USER SPECIFIED OFFICER FOR A GIVEN DATE AND TIME RANGE,
4-15.6 (2.2) USER SPECIFIED SQUAD, FOR A GIVEN DATE AND TIME RANGE,
4-15.6 (2.3) USER SPECIFIED DISTRICT FOR A GIVEN DATE AND TIME RANGE,
4-15.6 (2.4) USER SPECIFIED SHIFT FOR A GIVEN DATE AND TIME RANGE,
4-15.6 (2.5) FOR ALL OFFICERS FOR A GIVEN DATE AND TIME RANGE,
4-15.6 (2.6) OFFENSE LOCATION FOR A GIVEN DATE AND TIME RANGE, OR
4-15.6 (2.7) OFFENSE TYPES FOR A GIVEN DATE AND TIME RANGE.
4-15.6 (3) THE PROPOSED SYSTEM SHALL INCLUDE A SUMMARY REPORT OF
ACCIDENTS BY:
4-15.6 (3.1) LOCATION,
4-15.6 (3.2) DISTRICT, OR
4-15.6 (3.3) OTHER GEOFILE SUPPORTED POLYGON.
4-15.6 (3.4) OTHER GEOFILE USER-DEFINED PARAMETER
4-15.6 (4) THE PROPOSED SYSTEM SHALL INCLUDE, BUT NOT BE LIMITED TO,
REPORTS SHOWING THE:
4-15.6 (4.1) TOTAL NUMBER OF ACCIDENTS FOR A USER-DEFINED DATE AND
TIME RANGE,
4-15.6 (4.2) TOTAL NUMBER OF PERSONAL INJURIES AS A RESULT OF
ACCIDENTS, AND
4-15.6 (4.3) TOTAL NUMBER OF ACCIDENTS PER LOCATION WITHIN ANY
JURISDICTION BASED UPON A USER-DEFINED DATE AND TIME
RANGE.
4-15.6 (5) THE PROPOSED RMS APPLICATION SHALL INCLUDE A SUMMARY
AND A DETAIL REPORT OF ALL FATAL ACCIDENTS OCCURRING IN A
USER-DEFINED AREA OR LOCATION, DURING A USER-DEFINED DATE
RANGE.
City of Fort Collins ccxliv Proposal P-847
4-15.6 (6) THE PROPOSED RMS APPLICATION SHALL INCLUDE A REPORT
LISTING ACCIDENTS BY CAUSE IN A USER-DEFINED AREA AND
DURING A USER-DEFINED DATE AND TIME RANGE.
4-15.6 (7) THE PROPOSED RMS APPLICATION SHALL INCLUDE A REPORT
THAT SHOWS ALL LOCATIONS IN WHICH ACCIDENTS EXCEED A
USER-DEFINED NUMBER FOR A USER-DEFINED DATE AND TIME
RANGE.
4-15.7 POLICE MANAGEMENT REPORTS
4-15.7 (1) THE PROPOSED RMS APPLICATION SHALL SUPPORT CONTINUAL
IMPROVEMENT OF POLICE OPERATIONS AND ADMINISTRATION BY
PROVIDING PERIODIC REPORTS OF DIVISION AND DEPARTMENTAL
PERFORMANCE, PROVIDING BOTH CURRENT STATISTICAL AND
HISTORICAL DATA IN TABULAR AND GRAPHIC FORMATS.
4-15.7 (2) THE PROPOSED RMS APPLICATION SHOULD INCLUDE THE
FOLLOWING MONTHLY AND YEAR-TO-DATE FREQUENCY COUNTS
FOR PATROL:
4-15.7 (2.1) CITATIONS,
4-15.7 (2.2) WARNINGS,
4-15.7 (2.3) ARRESTS BY TYPE,
4-15.7 (2.4) JUVENILE ARRESTS,
4-15.7 (2.5) ADULT ARRESTS,
4-15.7 (2.6) FIELD INTERROGATIONS,
4-15.7 (2.7) REPORTED FELONIES,
4-15.7 (2.8) REPORTED MISDEMEANORS, AND
4-15.7 (2.9) SEIZED ITEMS AND VALUE.
4-15.7 (3) THE PROPOSED RMS APPLICATION SHALL INCLUDE THE
FOLLOWING PERFORMANCE REPORTS FOR PATROL:
4-15.7 (3.1) AVERAGE EN ROUTE TIME TO CALLS FOR SERVICE BY SHIFT,
4-15.7 (3.2) AVERAGE EN ROUTE TIME TO CALLS FOR SERVICE BY DISTRICT,
4-15.7 (3.3) AVERAGE EN ROUTE TIME TO CALLS FOR SERVICE BY PRIORITY,
4-15.7 (3.4) AVERAGE EN ROUTE TIME BY OFFICER,
City of Fort Collins ccxlv Proposal P-847
4-15.7 (3.5) AVERAGE ON SCENE TIME BY SHIFT,
4-15.7 (3.6) AVERAGE ON SCENE TIME BY DISTRICT,
4-15.7 (3.7) AVERAGE ON SCENE TIME BY OFFICER,
4-15.7 (4) REPORT PARAMETERS IN 13.9.3 SHALL BE REPORTABLE BY ANY OR
ALL PARAMETERS
4-15.7 (5) THE PROPOSED RMS APPLICATION SHALL INCLUDE THE
FOLLOWING REPORTS FOR INVESTIGATIONS:
4-15.7 (5.1) AVERAGE CRIME CLEARANCES BY SHIFT, AND
4-15.7 (5.2) AVERAGE CRIME CLEARANCES BY OFFICER OR INVESTIGATOR.
4-15.7 (5.3) AVERAGE CRIME CLEARANCES BY UNIT (INVESTIGATIONS, SIU,
ETC)
4-15.7 (6) THE PROPOSED RMS APPLICATION SHALL HAVE THE ABILITY TO
CREATE A DAILY ACTIVITY REPORT SHOWING THE CALLS FOR
SERVICE, INVESTIGATIVE ACTIVITIES AND OTHER SYSTEM
RECORDED ACTIONS TAKEN BY AN OFFICER FOR A GIVEN SHIFT.
4-15.7 (7) THE PROPOSED RMS APPLICATION SHALL INCLUDE A REPORT
SHOWING A SUMMARY OF THE REPORT SUBMISSION AND REVIEW
PROCESS FOR A SPECIFIC REPORT INCLUDING THE FOLLOWING
EVENTS:
4-15.7 (7.1) THE DATE AND TIME THE REPORT WAS FIRST ASSIGNED,
4-15.7 (7.2) THE DATE AND TIME IT WAS MODIFIED BY RECORDS,
4-15.7 (7.3) THE DATE AND TIME IT WAS SUBMITTED REVIEW,
4-15.7 (7.4) EACH DATE AND TIME IT WAS RETURNED FOR CORRECTIONS,
AND
4-15.7 (7.5) EACH TIME IT WAS RESUBMITTED.
4-15.7 (8) THE PROPOSED RMS APPLICATION SHALL INCLUDE THE
FOLLOWING CASE REPORT MANAGEMENT REPORTS:
4-15.7 (9) FOR AN INDIVIDUAL OFFICER THE PERCENT AND NUMBER OF
OFFENSE, ACCIDENT, PROPERTY AND OTHER REPORTS WHICH
WERE COMPLETED AND NOT RETURNED FOR CORRECTIONS (1ST
TIME COMPLETION REPORT).
4-15.7 (9.1) A 1ST TIME COMPLETION REPORT FOR A GROUP OF OFFICERS.
City of Fort Collins ccxlvi Proposal P-847
4-15.7 (9.2) A 1ST TIME COMPLETION REPORT WHICH DETAILS THE
PERCENT AND NUMBER OF REPORTS THAT WERE COMPLETED
AND NOT RETURNED FOR CORRECTIONS BY REPORT TYPE.
4-15.7 (10) THE PROPOSED RMS APPLICATION SHALL INCLUDE A CALLS FOR
SERVICE SUMMARY/ COMPARISON REPORT WHICH LISTS CALLS
FOR SERVICE BY CALL TYPE FOR A USER-DEFINED MONTH WITH
COMPARISONS TO THE PRIOR MONTH AND THE SAME MONTH IN
THE PRIOR YEAR.
City of Fort Collins ccxlvii Proposal P-847
5 - JAIL MANAGEMENT
5-1 GENERAL REQUIREMENTS
The Jail Management Database shall be designed to operate as a component of a
comprehensive, fully integrated, multi-user, incident-based Public Safety System Records
Management System (RMS) and Jail Management System (JMS).
5-1.1 WORKFLOW PROCESS
5-1.1 (1) THE SYSTEM SHALL HAVE THE ABILITY TO SET AN AGENCY
DEFINED WORKFLOW PROCESS THAT IS THEN FOLLOWED
AUTOMATICALLY FROM SCREEN TO SCREEN DURING BOOKING
AND RELEASE.
5-1.1 (2) THE SYSTEM SHALL HAVE THE ABILITY TO COMPLETE THE WORK
FLOW PROCESS OUT OF ORDER AT USER DISCRETION
5-1.1 (3) THE SYSTEM SHALL HAVE THE ABILITY TO HAVE MORE THAN ONE
WORKFLOW PROCESS DEFINED THAT WOULD THEN CHANGE
BASED ON TYPE OF BOOKING OR RELEASE.
5-1.1 (4) THE SYSTEM SHALL HAVE THE ABILITY TO MANAGE
SIMULTANEOUS WORKFLOW PROCESSES ON ONE STATION AT ONE
TIME.
5-1.2 SCHEDULING
System shall have a schedule keeping system that is used globally by all jail
management functions, allowing system wide visibility of all events scheduled per
inmate.
5-1.2 (1) SYSTEM SHALL SCHEDULE AT MINIMUM THE FOLLOWING EVENTS
FOR AN INDIVIDUAL (INDICATE THE TYPE OF SCHEDULING
CAPABILITIES BELOW);
5-1.2 (1.1) COURT APPEARANCES,
5-1.2 (1.2) PRISONER TRANSPORT,
5-1.2 (1.3) WRIT OF HABEAS CORPUS
5-1.2 (1.4) EXTRADITION,
5-1.2 (1.5) FURLOUGH,
5-1.2 (1.6) APPOINTMENTS,
City of Fort Collins ccxlviii Proposal P-847
5-1.2 (1.7) PROGRAMS,
5-1.2 (1.8) EDUCATION,
5-1.2 (1.9) VISITATION,
5-1.2 (1.10) OTHER EVENTS.
5-1.2 (2) THE SYSTEM SHALL ALLOW FOR SCHEDULING INMATES IN GROUPS
AS DEFINED BY THE OPERATOR.
5-1.2 (3) SYSTEM SHALL BE ABLE TO SCHEDULE ANY PERSON WHO HAS A
CORE RECORD IN THE RMS/JMS REGARDLESS OF BOOKING STATUS.
5-1.2 (4) SYSTEM SHALL BE ABLE TO SCHEDULE PHYSICAL LOCATIONS PRE-
DEFINED IN THE SYSTEM.
5-1.2 (5) SYSTEM SHALL WARN OF VIOLATIONS OF RESTRICTIONS (KEEP
SEPARATES, MEDICAL RESTRICTIONS, ETC.)
5-1.2 (6) SYSTEM SHALL ALLOW / DISALLOW SCHEDULE CONFLICTS BASED
ON ADMINISTRATIVE SETTINGS
5-1.2 (7) SYSTEM SHALL NOTIFY THE ORIGINATOR(S) OF THE OTHER
SCHEDULED EVENTS OF A NEW SCHEDULED EVENTS THAT
CONFLICTS WITH PREVIOUSLY SCHEDULED EVENTS (ALL THAT
CONFLICT).
5-1.2 (8) SYSTEM SHALL HAVE THE ABILITY TO SEND UNSOLICITED
NOTIFICATION OF PENDING PARTICIPATION IN AN EVENT TO ANY
NUMBER OF PRE DETERMINED RECIPIENTS BASED ON USER
DEFINED PARAMETERS.
5-1.2 (9) THE SYSTEM MUST BE CAPABLE OF CHOOSING THE SCHEDULED
EVENT FROM A PICK LIST: MEDICAL APPOINTMENTS AND THEIR
LOCATIONS, COURT DATES, VISITOR APPOINTMENTS (PERSONAL
AND PROFESSIONAL), TRANSPORTING INMATES TO OTHER
FACILITIES, AND SPECIAL PROGRAM APPOINTMENTS (GED
CLASSES, ETC.).
5-1.2 (10) THE SYSTEM MUST BE ABLE TO VIEW OR PRINT ALL SCHEDULED
APPOINTMENTS OR A PARTICULAR TYPE OF APPOINTMENT (E.G.
COURT APPOINTMENTS).
5-1.2 (11) THE SYSTEM SHOULD HAVE THE ABILITY TO CANCEL OR
RESCHEDULE EVENTS.
City of Fort Collins ccxlix Proposal P-847
5-1.2 (12) THE SYSTEM MUST PROVIDE THE ABILITY TO GENERATE A
SUMMARY SHEET OF ALL APPOINTMENTS SEQUENCED BY
HOUSING ASSIGNMENT AND BY INMATE IN CHRONOLOGICAL
ORDER.
5-1.2 (13) THE SYSTEM MUST PROVIDE THE ABILITY FOR THE USER TO
DISPLAY ALL SCHEDULED EVENTS FOR AN INMATE OR HOUSING
AREA FOR A PARTICULAR DATE AND EVENT TYPE.
5-1.2 (14) THE SYSTEM MUST ALLOW ENTRY OF SPECIAL INMATE EVENTS
(E.G. DELIVERY OF COURT CLOTHES, DELIVERY OF PERSONAL
ITEMS, SPECIAL VISITATION RIGHTS).
5-1.3 PROCESS NOTIFICATION
5-1.3 (1) THE SYSTEM SHALL INITIATE INTERNAL MESSAGES BASED ON
AGENCY DEFINED CRITERIA THAT WILL NOTIFY SYSTEM
OPERATORS OF PENDING PROCESSES (INDICATE THE TYPE OF
NOTIFICATIONS BELOW). NOTE - THIS IS NOT THE SAME AS A USER
REQUESTING A REPORT, THE SYSTEM DRIVES THIS PROCESS, NOT
THE USER;
5-1.3 (1.1) MITIMUS BOOKING DUE (FROM PRE-BOOKING),
5-1.3 (1.2) TEMP RELEASE FAIL TO RETURN,
5-1.3 (1.3) RELEASE DUE,
5-1.3 (1.4) SUICIDE WATCH DUE,
5-1.3 (1.5) MEAL WATCH DUE,
5-1.3 (1.6) SLEEP WATCH DUE,
5-1.3 (1.7) EMOTIONAL INSTABILITY WATCH DUE,
5-1.3 (1.8) RESTRAINT CHECK DUE,
5-1.3 (1.9) COURT DATE DUE,
5-1.3 (1.10) TRANSPORT PENDING,
5-1.3 (1.11) VISITATION DUE,
5-1.3 (1.12) PROGRAM ATTENDANCE,
5-1.3 (1.13) MEDICAL APPOINTMENTS DUE,
5-1.3 (1.14) COUNSELING APPOINTMENTS DUE,
City of Fort Collins ccl Proposal P-847
5-1.3 (1.15) STATUS AND/OR CLASSIFICATION REVIEW DUE,
5-1.3 (1.16) DISCIPLINARY HEARING BOARD ATTENDANCE,
5-1.3 (1.17) DISCIPLINARY PROCESS INCOMPLETE,
5-1.3 (1.18) WORK RELEASE FAIL TO RETURN,
5-1.3 (1.19) WEEKEND OR MIDWEEK PROGRAM FAIL TO REPORT,
5-1.3 (1.20) USEFUL PUBLIC SERVICE FAIL TO REPORT,
5-1.3 (1.21) INMATE WORK PROGRAM SCHEDULED,
5-1.3 (1.22) OTHER PROCESSES.
5-1.3 (2) THE SYSTEM SHALL SEND THESE SAME MESSAGES EXTERNAL TO
THE SYSTEM VIA AN INTERFACE TO AN E-MAIL SYSTEM.
5-1.4 OTHER GENERAL REQUIREMENTS
5-1.4 (1) THE SYSTEM SHALL DISPLAY A MASTER STATUS SCREEN THAT
WILL CONTAIN BRIEF INFORMATION (INCLUDING STATUS,
CHARGES, ASSIGNED HOUSING, AND CURRENT LOCATION) OF
EVERY ACTIVE INMATE IN THE SYSTEM.
5-1.4 (2) THE SYSTEM SHALL MAINTAIN A DYNAMIC ELECTRONIC COPY OF
THIS MASTER STATUS IN AN INDUSTRY STANDARD FORMATTED
FILE ON THE HARD DRIVE (IN A LOCATION SPECIFIED BY THE
AGENCY), OF ANY COMPUTER DEFINED BY THE AGENCY TO
RECEIVE THIS FILE, THAT HAS A CURRENTLY LOGGED ON CLIENT
OF THE RMS/JMS. THIS FILE MUST REMAIN AND BE AVAILABLE FOR
VIEWING IN THE EVENT OF A RMS/JMS FAILURE.
5-1.4 (3) THE SYSTEM SHALL HAVE THE ABILITY FOR PATROL OFFICERS TO
INITIATE THE BOOKING PROCESS BY PROVIDING BASIC NEEDED
INFORMATION ELECTRONICALLY VIA AN UPLOADED COMPUTER
FILE CREATED IN THE FIELD AND TRANSFERRED BY AIR, WIRE, OR
REMOVABLE MEDIA.
5-2 BOOKING AND RELEASE PROCESS
5-2.1 BOOKING - PERSON ENTRY
5-2.1 (1) THE SYSTEM SHALL HAVE THE ABILITY TO PRE-BOOK AN
INDIVIDUAL TO START SERVING A SENTENCE ON A SPECIFIC DAY IN
THE FUTURE.
City of Fort Collins ccli Proposal P-847
5-2.1 (2) THE SYSTEM SHALL HAVE A MECHANISM TO LOOKUP A PERSON
AFTER THE ENTRY OF A NAME (FULL OR PARTIAL), AND/OR RACE,
AND/OR SEX, AND/OR DOB, AND BY UTILIZING SOUNDEX
PROCEDURES, PROVIDE THE ENTRY PERSON WITH A LIST OF
POSSIBLE MATCHES OF INDIVIDUALS WITH ANY PRIOR
INVOLVEMENT IN ANY PART OF THE RMS/JMS AND, UPON
SELECTION, TO PRE-POPULATE ALL PERSONAL DEMOGRAPHIC
FIELDS (PERSON AND ADDRESS) FROM THE LATEST INFORMATION
HELD IN THAT INDIVIDUAL’S CORE RECORD.
5-2.1 (3) THE SYSTEM SHALL BE ABLE TO DISPLAY A PHOTOGRAPH AS A
PART OF THE LOOKUP PROCESS (NOT A SEPARATE PROCESS) PRIOR
TO SELECTING THE RECORD AND PRE-POPULATING ALL PERSONAL
DEMOGRAPHIC FIELDS.
5-2.1 (4) THE SYSTEM SHALL ALLOW THE USE OF A BAR CODE READER TO
GATHER ENTRY INFORMATION TO PRE-POPULATE ENTRY FIELDS
FROM A COLORADO DRIVER’S LICENSE.
5-2.1 (5) THE SYSTEM SHALL HAVE THE ABILITY TO ASSIGN SEQUENTIAL
BOOKING (ARREST) NUMBERS (NUMBERS UNIQUE TO THIS
INDIVIDUAL AND THIS BOOKING OR ARREST) IN THE FORMAT
DESCRIBED BELOW;
5-2.1 (5.1) ALPHA/NUMERIC,
5-2.1 (5.2) 12 CHARACTERS,
5-2.1 (5.3) IN THE FORMAT (YY)(AA)(F)(C)(NNNNNN) WHERE (YY) IS THE
LAST TWO DIGITS OF THE CURRENT YEAR, (AA) IS A TWO
LETTER CODE FOR THE ARRESTING AGENCY, (F) IS A ONE
LETTER CODE FOR FACILITY (DERIVED BY PHYSICAL LOCATION
OF THE ENTRY TERMINAL), (C) IS A ONE LETTER CODE
INDICATING TO HIGHEST LEVEL CHARGE FOR THIS ARREST, AND
(NNNNNN) IS A SIX DIGIT SEQUENTIAL NUMBER SHARED BY ALL
AGENCIES THAT STARTS OVER EACH YEAR.
5-2.1 (6) THE BOOKING NUMBER SHALL BE GENERATED BY THE SAME
ROUTINE THAT PROVIDES ARREST NUMBERS TO THE RMS
APPLICATION (BOOKING NUMBER IS THE SAME AS ARREST
NUMBER AND MUST BE UNIQUE ACROSS THE ENTIRE SYSTEM).
5-2.1 (7) THE SYSTEM SHALL AUTOMATICALLY CALCULATE AND DISPLAY
AN INMATE AGE FROM THE DATE OF BIRTH TO FLAG JUVENILE
INMATES.
City of Fort Collins cclii Proposal P-847
5-2.1 (8) THE SYSTEM SHALL MAINTAIN THE CALCULATED AGE AS
HISTORICAL INFORMATION (ALWAYS SHOW THE AGE THE PERSON
WAS AT THE TIME, NOT THE AGE THEY ARE NOW).
5-2.1 (9) THE SYSTEM SHALL HAVE AN AGENCY DEFINED PICK LIST FIELD
FOR COUNTRY OF BIRTH.
5-2.1 (10) THE SYSTEM SHALL TRACK THE LEVEL EDUCATION.
5-2.1 (11) THE SYSTEM SHALL AUTOMATICALLY NOTIFY STAFF AT THE TIME
OF BOOKING OF ANY SIGNIFICANT ALERTS ON FILE IN THE
RMS/JMS (INDICATE THE TYPE OF NOTIFICATIONS BELOW);
5-2.1 (11.1) PENDING WARRANTS,
5-2.1 (11.2) PENDING CIVIL PROCESS,
5-2.1 (11.3) REGISTERED SEX OFFENDER,
5-2.1 (11.4) OFFICER HAZARDS,
5-2.1 (11.5) GANG AFFILIATIONS,
5-2.1 (11.6) KEEP SEPARATES,
5-2.1 (11.7) VICTIM NOTIFICATIONS,
5-2.1 (11.8) PAST SUICIDAL BEHAVIOR,
5-2.1 (11.9) PAST COMBATIVE BEHAVIOR,
5-2.1 (11.10) ESCAPEE,
5-2.1 (11.11) ESCAPE RISK,
5-2.1 (11.12) MEDICAL CAUTIONS,
5-2.1 (11.13) DIETARY CAUTIONS,
5-2.1 (11.14) OTHER CAUTIONS.
5-2.1 (12) THE SYSTEM SHALL DISPLAY ANY AND ALL OF THESE ALERTS
ANYTIME THE INMATES RECORD IS VIEWED.
5-2.1 (13) THE SYSTEM SHALL HAVE THE ABILITY TO MAINTAIN A PERSON OF
INTEREST TAG SPECIFIC TO THE BOOKING PROCESS (ONLY NOTIFY
WHEN SOMEONE IS BROUGHT INTO THE FACILITY).
City of Fort Collins ccliii Proposal P-847
5-2.1 (14) THE SYSTEM SHALL AUTOMATICALLY QUERY STATE AND LOCAL
DATABASES FOR WANTS AND WARRANTS EVERY TIME SOMEONE IS
BOOKED.
5-2.1 (15) THE SYSTEM SHALL HAVE THE ABILITY TO FORMAT AND SEND
CCIC/NCIC MESSAGES AT THE USER INTERFACE.
5-2.1 (16) THE SYSTEM SHALL PROVIDE AUTHORIZED USERS ONLY WITH THE
ABILITY TO DE-ATTACH (SEPARATE) SPECIFIC BOOKING RECORDS
FROM A SPECIFIC INMATE AND ASSIGN IT TO ANOTHER PERSON.
5-2.1 (17) THE SYSTEM SHALL HAVE A PROVISION FOR AUTHORIZED USERS
ONLY TO COMBINE MULTIPLE INMATE RECORDS TO A SPECIFIC
INMATE.
5-2.1 (18) THE SYSTEM SHALL ALLOW ENTRY OF INFORMATION ASSOCIATED
WITH SCARS, MARKS AND TATTOOS INCLUDING THEIR LOCATION
AND DESCRIPTION.
5-2.1 (19) THE SYSTEM SHALL HAVE A PICK LIST FIELD SPECIFIC TO THE
BOOKING THAT WILL INDICATE THE AGENCY THAT BROUGHT THE
PERSON IN FOR BOOKING.
5-2.1 (20) THE SYSTEM SHALL HAVE FIELD SPECIFIC TO THE BOOKING THAT
WILL INDICATE THE PRIMARY OFFICER OF CUSTODY (OFFICER
WHO BROUGHT THE INMATE TO JAIL) OF THE AGENCY THAT
BROUGHT THE PERSON IN FOR BOOKING.
5-2.1 (21) THE SYSTEM SHALL HAVE A FIELD FOR BOOKING AGENCY CASE
(REPORT) NUMBER (USED FOR LINKING PURPOSES).
5-2.1 (22) THE SYSTEM SHALL HAVE A PICK LIST FIELD SPECIFIC TO THE
BOOKING THAT WILL INDICATE THE AGENCY THAT WILL BE THE
AGENCY OF RECORD FOR THE ARREST.
5-2.1 (23) THE SYSTEM SHALL HAVE FIELD SPECIFIC TO THE BOOKING THAT
WILL INDICATE THE PRIMARY ARRESTING OFFICER (OFFICER WHO
WILL BE FILING THE CHARGES) OF THE ARRESTING AGENCY.
5-2.1 (24) THE SYSTEM SHALL HAVE A FIELD FOR ARRESTING AGENCY CASE
(REPORT) NUMBER (USED FOR LINKING PURPOSES).
5-2.1 (25) THE SYSTEM SHALL HAVE A FIELD SPECIFIC TO THE BOOKING FOR
COMMENTS.
5-2.1 (26) THE SYSTEM SHALL HAVE A TOOL FOR ASSESSING POSSIBLE
SUICIDE RISK USING A QUESTION AND ANSWER FORM THAT IS
DEFINABLE BY THE AGENCY.
City of Fort Collins ccliv Proposal P-847
5-2.1 (27) THE SYSTEM SHALL MAINTAIN SUICIDE RISK INFORMATION
HISTORICALLY OF ANY INMATE CLASSIFIED AS A SUICIDE RISK.
5-2.1 (28) THE SYSTEM SHALL HAVE THE SYSTEM HAVE THE ABILITY TO
CAPTURE AND SAVE PARTIAL BOOKING INFORMATION UNTIL IT
CAN BE MODIFIED AND COMPLETED AT A LATER TIME.
5-2.1 (29) THE SYSTEM SHALL ALLOW FOR LOCATION CHANGES FOR
INMATES PRIOR TO COMPLETION OF THE BOOKING PROCESS.
5-2.1 (30) THE SYSTEM SHALL ALLOW FOR DIFFERENT TYPES OF BOOKINGS
(E.G. CITATION, WARRANT, DETAINER, COURTESY HOLD, COURT
PICKUP).
5-2.1 (31) THE SYSTEM SHALL GENERATE BOARD TAG INSERTS FOR A
MAGNETIC MASTER STATUS BOARD CURRENTLY IN PLACE AND
MAINTAINED BY BOOKING STAFF.
5-2.1 (32) THE SYSTEM SHALL GENERATE TAMPER RESISTANT BARCODE
BRACELETS WITH INMATE PICTURE AND IDENTIFYING TEXT AS
SPECIFIED BY LARIMER COUNTY.
5-2.1 (33) THE SYSTEM SHALL GENERATE PICTURE OUTPUT IN SIZES AND
QUANTITIES AS NEEDED BY BOOKING PERSONNEL.
5-2.1 (34) THE SYSTEM MUST BE ABLE TO TRACK FULL DEMOGRAPHICS,
NAME, ADDRESS, PHONE, ETC. (TIED TO THE MASTER NAME
RECORD) OF ALL VICTIMS OF THE PERSON BEING BOOKED.
5-2.1 (35) THE SYSTEM MUST BE ABLE TO TRACK UP TO 99 “VICTIM
CONDITION” CODES PER VICTIM THAT ARE PRE-DEFINED BY THE
AGENCY AND MADE AVAILABLE THROUGH THE USE OF DROP
DOWN SELECTION.
5-2.1 (36) THE SYSTEM SHALL HAVE THE ABILITY TO CAPTURE THE
AFFIDAVIT OF WARRANTLESS ARREST ON ANY BOOKING
(ESSENTIALLY AN ATTACHED NARRATIVE TO THE BOOKING).
5-2.1 (37) THE SYSTEM SHALL HAVE THE ABILITY TO LIMIT THE AFFIDAVIT
OF WARRANTLESS ARREST TO ONE PER BOOKING.
5-2.1 (38) THE SYSTEM SHALL HAVE THE ABILITY TO LIMIT THE NUMBER OF
CHARACTERS CONTAINED IN AN AFFIDAVIT OF WARRANTLESS
ARREST TO AN AGENCY DEFINED AND MAINTAINED NUMBER.
5-2.1 (39) THE SYSTEM MUST HAVE THE ABILITY TO FLAG THE BOOKING
RECORD TO INDICATE THAT THE PERSON BEING BOOKED NEEDS
TO GO TO A PRE-TRIAL INTERVIEW.
City of Fort Collins cclv Proposal P-847
5-2.1 (40) THE SYSTEM MUST HAVE THE ABILITY TO EXPORT BASIC BOOKING
INFORMATION (PERSON, CHARGES, AFFIDAVIT OF WARRANTLESS,
BOND INFORMATION, CCIC/NCIC RESPONSES, ETC.) TO AN ASCII
FILE TO BE SAVED AT A LOCATION CHOSEN BY THE USER (USED TO
IMPORT DATA TO PRE-TRIAL).
5-2.1 (40.1) THE INFORMATION CONTAINED IN THIS FILE AND HOW IT IS
DELIMITED SHALL BE CONTROLLED BY THE SYSTEM
ADMINISTRATOR.
5-2.2 BOOKING - CHARGE ENTRY AND TRACKING
5-2.2 (1) THE SYSTEM SHALL ALLOW FOR A MINIMUM OF 99 CHARGE
RECORDS FOR ANY INMATE.
5-2.2 (2) THE SYSTEM SHALL HAVE A SEQUENTIAL NUMBER FOR EACH
CHARGE.
5-2.2 (3) THE SYSTEM SHALL HAVE THE ABILITY TO SELECT FROM AN
AGENCY MAINTAINED PICK LIST, CHARGES, BY FULL OR PARTIAL
CHARGE CODE OR CHARGE DESCRIPTION.
5-2.2 (4) THE SYSTEM SHALL ALLOW FOR FREE TEXT ENTRY OF A CHARGE
CODE (OVERRIDE).
5-2.2 (5) THE SYSTEM SHALL SEND A NOTIFICATION TO A SYSTEM
ADMINISTRATOR THAT A MANUAL CHARGE CODE ENTRY WAS
MADE.
5-2.2 (6) THE SYSTEM SHALL ALLOW FOR FREE TEXT ENTRY OF A CHARGE
DESCRIPTION.
5-2.2 (7) THE SYSTEM SHALL STORE (PER CHARGE/SENTENCE) ALL CHARGE
INFORMATION (CODE AND DESCRIPTION) AS DISPLAYED (AS
OPPOSED TO ONLY STORING A POINTER TO A TABLE).
5-2.2 (8) THE SYSTEM SHALL HAVE A FIELD (PER CHARGE/SENTENCE)
SPECIFICALLY FOR THE ENTRY OF THE STATE OF COLORADO
STANDARDIZED COURT DOCKET/WARRANT NUMBER (FOR CICJIS
LINKING).
5-2.2 (9) THE SYSTEM SHALL ENSURE CORRECT ENTRY OF STATE
STANDARDIZED COURT DOCKET/WARRANT NUMBER BY CHECKING
FOR ADHERENCE TO CORRECT FORMATTING AS DEFINED BY THE
STATE OF COLORADO.
5-2.2 (10) THE SYSTEM SHALL HAVE A PICK LIST FIELD (PER
CHARGE/SENTENCE) SPECIFICALLY FOR TYPE OF
City of Fort Collins cclvi Proposal P-847
CHARGE/SENTENCE (E.G. STATE CHARGE, MUNICIPAL CHARGE,
WARRANT, SENTENCE (ST, WR, WE, HD, UPS, ETC.)).
5-2.2 (11) THE SYSTEM SHALL HAVE DESIGNATOR (PER CHARGE/SENTENCE)
SPECIFICALLY TO INDICATE THAT THIS CHARGE IS RESTRICTED
RELEASE OF INFORMATION (CAN BE USED TO SUPPRESS PRINTING
OF A CHARGE).
5-2.2 (12) THE SYSTEM SHALL HAVE A PICK LIST FIELD (PER
CHARGE/SENTENCE) SPECIFICALLY FOR CLASS OF CRIME (E.G.
FELONY 1,2,3,4,5,6, MISDEMEANOR 1,2,3, PETTY OFFENSE 1,2, ETC.).
5-2.2 (13) THE SYSTEM SHALL HAVE THE ABILITY TO RECORD A BOND TYPE
AND AMOUNT PER CHARGE.
5-2.2 (14) THE SYSTEM SHALL HAVE THE ABILITY TO RECORD A BOND
PROCESSING FEE PER CHARGE AND TO DEBIT THAT AMOUNT TO
THE INMATE’S ACCOUNT.
5-2.2 (15) THE SYSTEM SHALL HAVE A FIELD (PER CHARGE/SENTENCE)
SPECIFICALLY FOR NCIC CODE (4 DIGIT CODE) AS REQUIRED BY
THE COLORADO BUREAU OF INVESTIGATIONS.
5-2.2 (16) THE SYSTEM SHALL AUTOMATICALLY POPULATE NCIC CODE
WHEN CHARGE IS SELECTED FROM A PICK LIST.
5-2.2 (17) THE SYSTEM SHALL ALLOW A NCIC CODE TO BE MANUALLY
ENTERED IF THE CHARGE IS MANUALLY ENTERED.
5-2.2 (18) THE SYSTEM SHALL HAVE A PICK LIST FIELD (PER
CHARGE/SENTENCE) SPECIFICALLY FOR ARRESTING AGENCY.
5-2.2 (19) THE SYSTEM SHALL HAVE A FIELD (PER CHARGE/SENTENCE)
SPECIFICALLY FOR CHARGING OFFICER.
5-2.2 (20) THE SYSTEM SHALL HAVE A FIELD (PER CHARGE/SENTENCE) FOR
ARRESTING AGENCY CASE (REPORT) NUMBER (USED FOR LINKING
PURPOSES).
5-2.2 (21) THE SYSTEM SHALL HAVE A FIELD (PER CHARGE/SENTENCE)
SPECIFICALLY FOR BOND AMOUNT.
5-2.2 (22) THE SYSTEM SHALL HAVE A FIELD (PER CHARGE/SENTENCE)
SPECIFICALLY FOR COURT OF RECORD
5-2.2 (23) THE SYSTEM SHALL HAVE A FIELD (PER CHARGE/SENTENCE)
SPECIFICALLY FOR COMMENTS.
City of Fort Collins cclvii Proposal P-847
5-2.3 BOOKING - PROPERTY ENTRY AND TRACKING
5-2.3 (1) THE SYSTEM SHALL FULLY TRACK VEHICLES INVOLVED IN THE
ARREST (MAKE, MODEL, STYLE, PLATES, VIN, DESCRIPTION,
INVOLVEMENT, DISPOSITION, ETC.).
5-2.3 (2) THE SYSTEM SHALL ATTACH VEHICLE INVOLVEMENT IN THE
ARREST TO THAT VEHICLE’S MASTER RECORD (IF IT EXISTS) AND
THE INVOLVEMENT IN THE ARREST MUST BE DISPLAYED ON
FUTURE OPERATOR QUERIES ON THAT VEHICLE FROM ANYWHERE
IN THE SYSTEM.
5-2.3 (3) THE SYSTEM SHALL HAVE A PROPERTY SCREEN THAT USES BOTH
FREE TEXT ENTRY, AND AGENCY DEFINED PICK LISTS, TO RECORD
ALL PROPERTY REMOVED FROM, AND STORED FOR AN INMATE.
5-2.3 (4) THE SYSTEM SHALL HAVE THE ABILITY TO TRACK DISPOSITION OF
ANY ENTERED PROPERTY.
5-2.3 (5) THE SYSTEM SHALL HAVE THE ABILITY TO LOG AND TRACK
PROPERTY BEFORE THE ARRESTEE HAS GONE THROUGH THE
ENTIRE BOOKING PROCESS.
5-2.3 (6) THE SYSTEM SHALL ASSIGN PROPERTY BINS BASED ON THE NEXT
AVAILABLE OF A SERIES OF PRE-DEFINED BINS (REQUIRES THAT
THE SYSTEM TRACK BINS IN USE).
5-2.3 (7) THE SYSTEM SHALL HAVE AN ENTRY POINT ON THE PROPERTY
SCREEN FOR ALL CASH DEPOSITED TO THE INMATE’S INDIVIDUAL
ACCOUNT.
5-2.3 (8) THE SYSTEM SHALL PRINT A COMBINED PROPERTY AND MONEY
RECEIPT FOR INMATE AND OFFICER SIGNATURE AT TIME OF
BOOKING.
5-2.3 (9) THE SYSTEM SHALL HAVE SOME METHOD OF CAPTURING A
SIGNATURE FOR PROCESS VERIFICATION.
5-2.4 PROPERTY ISSUED
5-2.4 (1) THE SYSTEM SHALL HAVE FULL TRACKING OF PROPERTY ISSUED
TO AN A INMATE, INCLUDING THE ABILITY TO SHOW A COMPLETE
LIST OF ALLOWED PROPERTY BASED ON CLASSIFICATION AND OF
THAT PROPERTY WHAT WAS ISSUED.
5-2.4 (2) THE SYSTEM SHALL TRACK THE DATE/TIME OF ALL DRESS IN AND
DRESS OUT PROCESSES AND THE OFFICE THAT COMPLETES EACH.
City of Fort Collins cclviii Proposal P-847
5-2.5 SENTENCE CALCULATION
Sentence calculation is a process that is used to determine when a sentenced individual
is due to be released from jail. At the Larimer County jail it must not only handle
standard good time but also provide a mechanism for inmates to earn and lose
additional time from their sentence based on activities within the jail. The proposed
system must have a sentence calculation system.
5-2.5 (1) THE SYSTEM SHALL HAVE THE ABILITY TO CALCULATE (PER
CHARGE/SENTENCE) THE RELEASE DATE AS DEFINED BY APPLIED
FORMULAS.
5-2.5 (2) THE SYSTEM SHALL AUTOMATICALLY GIVE CREDIT FOR
STATUTORY GOOD TIME BASED ON AGENCY DEFINED
PARAMETERS.
5-2.5 (3) THE SYSTEM SHALL ALLOW FOR DEDUCTIONS IN ANY EARNED
TIME.
5-2.5 (4) THE SYSTEM SHALL HAVE A PROVISION FOR SENTENCE
CALCULATIONS BASED ON SERVED CONSECUTIVELY AND/OR
SERVED CONCURRENTLY PROVISIONS.
5-2.5 (5) THE SYSTEM SHALL ALLOW FOR A MINIMUM OF 99 SENTENCE
RECORDS FOR ANY INMATE.
5-2.5 (6) THE SYSTEM SHALL HAVE A PROVISION FOR A COMMENT FIELD
FOR ANY SENTENCE ENTRY.
5-2.5 (7) THE SYSTEM SHALL AUTOMATICALLY CALCULATE A RELEASE
DATE FOR INMATES IN ALTERNATIVE SENTENCING PROGRAMS
SUCH AS WORK RELEASE, WEEKEND OR MID-WEEK PROGRAMS,
HOME DETENTION, OR USEFUL PUBLIC SERVICE.
5-2.5 (8) THE SYSTEM SHALL PROVIDE A MECHANISM TO CONVERT A
SENTENCE FROM AN ALTERNATIVE SENTENCE PROGRAM TO
STRAIGHT TIME IN THE JAIL.
5-2.5 (9) THE SYSTEM SHALL PROVIDE A MECHANISM TO CONVERT A
SENTENCE FROM STRAIGHT TIME IN THE JAIL TO AN ALTERNATIVE
SENTENCE PROGRAM.
5-2.5 (10) THE SYSTEM SHALL PROVIDE A MECHANISM TO REPORT HOW
SYSTEM ARRIVED AT CALCULATED RELEASE DATE, HOW DATE WAS
DERIVED, AND WHO DID CALCULATION.
5-2.5 (11) SYSTEM MUST ALLOW FOR AN OVERRIDE ON CALCULATED
RELEASE DATE WITH MANDATORY COMMENT.
City of Fort Collins cclix Proposal P-847
5-2.5 (12) SYSTEM MUST PROVIDE FOR SENTENCE ADJUSTMENT WITH
MANDATORY COMMENT.
5-2.5 (13) THE SYSTEM SHALL HAVE A MECHANISM TO VOID CURRENT
SENTENCE CALCULATIONS.
5-2.5 (14) THE SYSTEM SHALL HAVE A MECHANISM FOR INMATES TO GAIN
ADDITIONAL CREDITS BASED ON STATUS IN ANY NUMBER OF JAIL
PROGRAMS WITH EVERY JAIL PROGRAM HAVING DIFFERENT
EARNING RATIOS.
5-2.5 (15) THE SYSTEM SHALL HAVE A PROVISION FOR INMATES TO LOSE
CREDITS EARNED BASED ON DISCIPLINARY ACTIONS.
5-2.5 (16) THE SYSTEM SHALL HAVE A PROVISION FOR LOGGING ACTIVITY
OF ALL ACTIONS THAT CONTRIBUTED TO FINAL CALCULATED
RELEASE DATE.
5-2.5 (17) THE SYSTEM SHALL SHOW RELATIONSHIPS BETWEEN EACH
SENTENCE RECORD (WHICH IS CONSECUTIVE TO WHICH, WHICH IS
CONCURRENT TO WHICH).
5-2.5 (18) THE SYSTEM SHALL BE ABLE TO DISPLAY A PERCENTAGE OF
CALCULATED SENTENCE SERVED.
5-2.5 (19) THE SYSTEM SHALL HAVE A MECHANISM TO ALLOCATE CREDIT
FOR TIME SERVED.
5-2.5 (20) THE SYSTEM SHALL HAVE A PROVISION THAT ALLOWS CREDIT FOR
TIME EARNED PRIOR TO ACTUAL SENTENCE DATE.
5-2.6 RELEASE PROCESS
5-2.6 (1) THE SYSTEM SHALL ALLOW FOR TEMPORARILY RELEASING AN
INMATE TO ANOTHER AGENCY WITHOUT THE NEED TO FULLY
SATISFY THE FORMAL RELEASE PROCESS (BOOKING REMAINS
ACTIVE).
5-2.6 (2) THE SYSTEM SHALL TRACK THE REASON FOR THE TEMPORARY
RELEASE.
5-2.6 (3) THE SYSTEM SHALL CLEARLY INDICATE THOSE INMATES WITH AN
ACTIVE BOOKING THAT ARE OUT OF THE FACILITY ON
TEMPORARY RELEASE.
5-2.6 (4) THE SYSTEM SHALL ALLOW THE OPERATOR TO SET A DATE FOR
THE ANTICIPATED RETURN OF A TEMPORARILY RELEASED
City of Fort Collins cclx Proposal P-847
INMATE, AND BY SO DOING CAUSE THE SYSTEM TO INITIATE
ACTION IF THE INMATE IS NOT RETURNED BY THAT DATE.
5-2.6 (5) THE SYSTEM SHALL HAVE THE ABILITY TO MAINTAIN HOLDS THAT
MUST BE SATISFIED BY AN OPERATOR SPECIFICALLY CLEARING
THE HOLD BEFORE THE SYSTEM WILL ALLOW THE RELEASE OF AN
INMATE FROM THE SYSTEM.
5-2.6 (6) THE SYSTEM SHALL HAVE A FREE TEXT HOLD DISPOSITION FIELD
(PER HOLD) THAT MUST BE COMPLETED BEFORE A HOLD CAN BE
RELEASED.
5-2.6 (7) THE SYSTEM SHALL AUTOMATICALLY QUERY STATE AND LOCAL
DATABASES FOR WANTS AND WARRANTS EVERY TIME SOMEONE IS
BEING RELEASED FROM THE SYSTEM.
5-2.6 (8) ON RELEASE OF PRE-DEFINED WARRANTS HOLDS, THE SYSTEM
SHALL AUTOMATICALLY GENERATE AN AGENCY RESPONSE
MESSAGE TO THE WARRANT AGENCY THAT CAN BE REVIEWED AND
CORRECTED BEFORE MESSAGE IS SENT BY THE RELEASING
OFFICER.
5-3 INMATE HOUSING AND MOVEMENT
5-3.1 CLASSIFICATION
5-3.1 (1) THE SYSTEM MUST HAVE AN AUTOMATIC CLASSIFICATION
PROCESS.
5-3.1 (2) THE SYSTEM MUST HAVE A CLASSIFICATION PROCESS THAT FULLY
ADHERES TO NIC GUIDELINES.
5-3.1 (3) THE SYSTEM MUST HAVE A CLASSIFICATION PROCESS THAT IS
ACCEPTABLE AND CERTIFIABLE BY ACA.
5-3.1 (4) THE SYSTEM MUST CLASSIFY INMATES BY UTILIZING A FLOW
CHART METHODOLOGY THAT BRANCHES IN DIFFERENT
DIRECTIONS BASED ON YES/NO ANSWERS (A POINT
CLASSIFICATION SYSTEM IS NOT ACCEPTABLE).
5-3.1 (5) THE CLASSIFICATION SYSTEM MUST BE INTEGRATED WITH THE
RMS/JMS AND AUTOMATICALLY UTILIZE INFORMATION ENTERED
AT OTHER POINTS IN THE SYSTEM TO ASSIST IN THE
CLASSIFICATION PROCESS.
5-3.1 (6) THE SYSTEM MUST ALLOW FOR AN AGENCY MAINTAINED
CATEGORIZATION OF INDIVIDUAL HOUSING AREAS AS TO TYPE OF
City of Fort Collins cclxi Proposal P-847
INMATE THAT WILL BE HOUSED (E.G. MINIMUM, MEDIUM,
MAXIMUM).
5-3.1 (7) THE SYSTEM MUST ALLOW THE AGENCY TO CHANGE A HOUSING
AREA'S DESIGNATION AS HOUSING NEEDS CHANGE.
5-3.1 (8) THE SYSTEM SHALL MAINTAIN HOUSING CATEGORIZATION
INFORMATION HISTORICALLY.
5-3.1 (9) THE SYSTEM MUST HAVE AN ALERT NOTING IF AN INMATE HAS
BEEN MIS-HOUSED.
5-3.1 (10) THE SYSTEM MUST ALLOW THE CLASSIFYING OFFICER TO
OVERRIDE THE HOUSING RECOMMENDATION AS NECESSARY, BUT
THE SYSTEM MUST LOG THE EVENT AND ALLOW FOR ENTRY OF
EXPLANATION.
5-3.1 (11) THE SYSTEM MUST HAVE AN AUTOMATIC MEANS OF SENDING A
MESSAGE TO PRE-DEFINED PERSON(S) THAT THE CLASSIFICATION
RECOMMENDATION WAS OVERRIDDEN.
5-3.1 (12) THE SYSTEM MUST HAVE AN AUTOMATIC MEANS OF SENDING A
CLASSIFICATION REVIEW NEEDED MESSAGE OR ALERT. EXAMPLES
OF EVENTS THAT SHOULD RE-SEND THE CLASSIFICATION NEEDED
MESSAGE OR ALERT ARE: NEW CHARGES/WARRANTS, A SECURITY
MOVE, A SPECIFIED NUMBER OF INCIDENTS, OR A TIME INTERVAL
BETWEEN REVIEWS.
5-3.2 HOUSING
5-3.2 (1) THE SYSTEM MUST HAVE AGENCY MAINTAINED SYSTEM TABLES
THAT CONTROL CODES FOR FACILITY, HOUSING AREA AND CELL.
5-3.2 (2) THE SYSTEM MUST PROVIDE INFORMATION ON AVAILABLE BEDS IN
EACH HOUSING AREA.
5-3.2 (3) THE SYSTEM MUST ALLOW ASSIGNMENT OF INMATES BY
CLASSIFICATION PERSONNEL TO A PARTICULAR HOUSING AREA.
5-3.2 (4) THE SYSTEM MUST PROVIDE MEANS FOR TRACKING PERSONS WHO
MUST BE KEPT SEPARATE FROM A SPECIFIC INMATE WITHIN THE
FACILITY. AN ALERT SHOULD BE GENERATED WHEN ASSIGNING
HOUSING LOCATIONS IF AN INMATE IS BEING ASSIGNED HOUSING
WITH A KEEP SEPARATE.
5-3.2 (5) THE SYSTEM MUST PROVIDE ENTRY OF ROUTINE INMATE COUNTS
AND THE ABILITY TO VIEW THEM IN BOTH ONLINE AND PRINTED
FORMATS.
City of Fort Collins cclxii Proposal P-847
5-3.2 (6) THE SYSTEM MUST PROVIDE INMATE ROSTERS IN BOTH ONLINE
AND PRINTED FORMATS. THE SYSTEM MUST ALLOW INDIVIDUAL
HOUSING AREAS TO BE VIEWED OR PRINTED AND MUST ALSO BE
ABLE TO VIEW AND PRINT ALL HOUSING AREA ROSTER
INFORMATION.
5-3.2 (7) THE SYSTEM MUST HAVE THE ABILITY TO FLAG AN INMATE BEING
HOUSED FOR ANOTHER AGENCY.
5-3.2 (8) THE SYSTEM MUST BE ABLE CREATE BOTH AN ONLINE AND
PRINTED ALPHABETIC LIST OF ALL ACTIVE INMATES, INCLUDING
EITHER THE HOUSING ASSIGNMENT OR THE ACTUAL LOCATION.
5-3.2 (9) THE SYSTEM MUST HISTORICALLY KEEP HOUSING AREA ROSTERS
FOR ANY GIVEN DATE AND TIME.
5-3.2 (10) THE SYSTEM MUST TRACK AND HISTORICALLY MAINTAIN ALL
HOUSING LOCATION CHANGES FOR AN INMATE.
5-3.3 HOUSING LOGS
5-3.3 (1) THE SYSTEM SHALL MAINTAIN PASS-ON FILES (TYPE OF ENTRY
CODE AND FREE TEXT COMMENT), KEYED TO LOCATIONS, THAT
CAN BE LATER RECALLED BY AN OFFICER BASED ON TYPE OF
ENTRY AND LOCATION, SUCH AS ALL INMATES SANCTIONED IN A
HOUSING AREA (PASS-ON FOR A HOUSING AREA FOR EXAMPLE).
5-3.3 (2) SYSTEM SHALL MAKE A NOTATION IN A PASS-ON FILE THAT A
PERSON HOUSED IN THAT AREA HAS HAD A BEHAVIORAL REPORT
FILED IN THE SYSTEM.
5-3.3 (3) SYSTEM SHALL DISPLAY PASS-ON FILES BY SELECTING
PREDEFINED TIME PERIODS (I.E. CLICKING ON A BUTTON).
5-3.3 (4) SYSTEM SHALL DISPLAY PASS-ON FILES BY ALLOWING THE USER
TO SPECIFY AREA AND TIME PERIOD.
5-3.4 MOVEMENT
5-3.4 (1) THE SYSTEM MUST CREATE ONLINE 'MOVE' LISTS FROM THE
ASSIGNMENT OF INMATES TO A PARTICULAR HOUSING AREA. THE
SYSTEM MUST BE ABLE TO DISPLAY THESE 'MOVE' LISTS ONLINE
AS NEEDED OR IN A PRINTED REPORT FORMAT.
5-3.4 (2) THE SYSTEM MUST BE ABLE TO TRACK ALL INMATE MOVEMENT
WITHIN THE FACILITY AND KEEP A HISTORY LOG OF THE
MOVEMENT.
City of Fort Collins cclxiii Proposal P-847
5-3.4 (3) THE SYSTEM MUST PROVIDE THE ABILITY TO ALERT TARGETED
JAIL STAFF BY INMATE'S NAME AND ID WITH DETAILS OF THE
SPECIAL ALERT(S) (E.G. SECURITY AND TRANSPORT STATUS,
MEDICAL ALERT, GANG AFFILIATIONS, SPECIAL DIETS, SECURITY
MOVES, UNSCHEDULED COURT APPEARANCE).
5-3.4 (4) THE SYSTEM SHOULD ALLOW ALERTS TO REQUIRE
ACKNOWLEDGEMENTS WITH OR WITHOUT COMMENT.
5-3.4 (5) THE SYSTEM SHALL NOTIFY SUPERVISORS OF UNACKNOWLEDGED
ALERTS AFTER A CERTAIN TIME.
5-3.4 (6) THE SYSTEM SHALL ALLOW FOR INMATE MOVEMENT TO BE
PROCESSED BY THE USE OF PORTABLE BAR CODE READERS.
5-3.4 (7) THE SYSTEM SHALL ALLOW FOR MOVING INMATES IN GROUPS BY
BARCODE AS DEFINED BY THE OPERATOR.
5-3.4 (8) THE SYSTEM MUST HAVE THE ABILITY TO GENERATE ONLINE AND
PRINTED INTERNAL AND EXTERNAL MOVEMENT LISTS.
5-3.4 (9) THE SYSTEM MUST ALLOW THE ADDITION OF NAMES TO
MOVEMENT LISTS.
5-3.4 (10) THE SYSTEM MUST BE ABLE TO RECORD INMATE MOVEMENT
SEPARATE FROM INMATE HOUSING ASSIGNMENTS.
5-3.5 TRANSPORTATION
5-3.5 (1) THE SYSTEM SHALL PROVIDE FOR FULL TRACKING AND
MANAGEMENT OF THE COURT TRANSPORTATION PROCESS.
5-3.5 (2) THE SYSTEM SHALL PROVIDE FOR FULL TRACKING AND
MANAGEMENT OF THE EXTRADITION PROCESS, INCLUDING
TRACKING ALL COSTS, PREPARING BILLING, OTHER AGENCY
HOLDS, CURRENT STATUS AND HISTORY MAINTENANCE.
5-3.5 (3) THE SYSTEM SHALL HAVE THE ABILITY TO MAINTAIN A
TRANSPORTATION NEEDED LISTING. THESE NAMES MAY BE
INMATES FROM BOOKED INTO THE FACILITY OR MAY BE INMATES
FROM OTHER AGENCIES.
5-3.5 (4) THE SYSTEM MUST BE ABLE TO GENERATE A PRINTED COURT
ACTION SHEET. THE SYSTEM WILL PRINT A COURT ACTION SHEET,
LISTING INMATES SCHEDULED FOR A COURT APPEARANCE FOR A
PARTICULAR DATE WITH SELECTS BY COURTROOM OR HOUSING
AREA.
City of Fort Collins cclxiv Proposal P-847
5-3.5 (5) THE SYSTEM MUST HAVE THE ABILITY TO ENTER THE DISPOSITION
OF EACH COURT APPOINTMENT AND THEN ALLOW SCHEDULING
OF THE NEXT COURT DATE.
5-3.5 (6) THE LIST OF INMATES SCHEDULED FOR TRANSPORT MUST
INCLUDE THE APPROPRIATE WARNINGS (E.G. ESCAPE RISK, PRONE
TO VIOLENCE, HIGH BOND, MEDICAL PRECAUTIONS).
5-4 PROGRAMS AND SERVICES
5-4.1 INMATE ACCOUNTING
5-4.1 (1) THE SYSTEM SHALL HAVE A FUNDS ACCOUNTING SYSTEM THAT
TRACKS FUNDS OF ALL INMATES INDIVIDUALLY (CREDITS AND
DEBITS).
5-4.1 (2) THE SYSTEM SHALL ALLOW FOR THE TRACKING OF AN
INDIVIDUAL’S ACCOUNT FROM BOOKING TO BOOKING TO INCLUDE
ALL NEGATIVE BALANCES.
5-4.1 (3) THE SYSTEM SHALL HAVE A PROCESS THAT TRACKS AN
INDIVIDUAL’S ACCOUNT BY TRANSACTION TYPE.
5-4.1 (4) THE SYSTEM MUST BE ABLE TO PROVIDE REAL-TIME INMATE
ACCOUNT BALANCE INFORMATION.
5-4.1 (5) THE SYSTEM MUST BE ABLE TO REPORT IN AN ONLINE AND IN
PRINTED FORMAT INMATES WHO HAVE BEEN RELEASED AND STILL
HAVE ACCOUNT BALANCES.
5-4.1 (6) THE SYSTEM MUST HAVE THE ABILITY TO HANDLE AND REPORT
UNCLAIMED FUNDS AND RETURN THE BALANCE TO ZERO BASED
ON LENGTH OF TIME LEFT UNCLAIMED.
5-4.1 (7) THE SYSTEM MUST HAVE THE ABILITY TO APPLY INMATE
ACCOUNT FUNDS TOWARDS BOND OR FINES AND COSTS. ALL
APPROPRIATE FINANCIAL RECORDS MUST BE UPDATED AS
NECESSARY.
5-4.1 (8) THE SYSTEM MUST HAVE THE ABILITY TO PRINT EACH INMATE'S
ACCOUNT ACTIVITY.
5-4.1 (9) THE SYSTEM SHALL HAVE THE ABILITY TO AUTOMATICALLY HAVE
REPETITIVE FEES DEBITED FOR EVERY PRE-DEFINED PERIOD THAT
PASSES WHILE AN INMATE IS (OR HAS) SERVED TIME IN THE
FACILITY.
City of Fort Collins cclxv Proposal P-847
5-4.1 (10) THE SYSTEM SHALL HAVE THE ABILITY TO SEND AUTOMATIC
NOTIFICATION TO A PREDEFINED PERSON(S) ANYTIME AN
INMATE’S ACCOUNT SHOWS A NEGATIVE BALANCE (EACH TIME IT
GOES FROM POSITIVE TO NEGATIVE).
5-4.1 (11) THE SYSTEM SHALL HAVE THE ABILITY TO HOLD ENCUMBRANCES
TO A NEGATIVE BALANCE THAT CAN BE SETTLED EITHER
AUTOMATICALLY OF MANUALLY (DEFINED BY TYPE OF
ENCUMBRANCE).
5-4.1 (12) THE SYSTEM SHALL HAVE THE ABILITY TO AUTOMATICALLY
NOTIFY THE ACCOUNTING TECHNICIAN OF ALL DEPOSITS TO A
NEGATIVE BALANCE.
5-4.1 (13) THE SYSTEM SHALL HOLD ALL MONIES DEPOSITED UP TO THE
TOTAL AMOUNT OF ENCUMBRANCES TO A NEGATIVE BALANCE
FROM THE RELEASE PROCESS (ONLY THAT MONEY ABOVE THE
NEGATIVE BALANCE IS RELEASABLE).
5-4.1 (14) THE SYSTEM SHALL HAVE THE ABILITY TO TRACK ALL INMATE
MONEY DEPOSITS AND RELEASES BY INDIVIDUAL BRINGING OR
RECEIVING MONEY.
5-4.1 (15) THE SYSTEM SHALL HAVE THE ABILITY TO ALLOW OR DENY
MONEY DEPOSIT OR RELEASE TO AN INDIVIDUAL BASED ON
PREVIOUS STATUS AS A RECENT INMATE OF LARIMER COUNTY.
5-4.1 (16) THE SYSTEM SHALL HAVE THE ABILITY TO ELECTRONICALLY
CAPTURE SIGNATURES FOR RECEIPT PROCESS.
5-4.1 (17) THE SYSTEM SHALL HAVE THE ABILITY TO PRINT RECEIPTS TO
INCLUDE CAPTURED SIGNATURE.
5-4.1 (18) THE SYSTEM SHALL HAVE THE ABILITY TO PRINT CHECKS AT
MULTIPLE LOCATIONS.
5-4.1 (19) THE SYSTEM SHALL HAVE THE ABILITY TO TRACK AND BILL COSTS
ASSOCIATED WITH BOOKING INMATES FOR OTHER AGENCIES AND
ENTITIES.
5-4.1 (20) THE SYSTEM SHALL HAVE THE ABILITY TO TRACK AND BILL COSTS
ASSOCIATED WITH HOLDING INMATES FOR OTHER AGENCIES AND
ENTITIES. THIS SHOULD INCLUDE A STANDARD RATE PER DAY AND
ALLOW ENTRY OF ANY SPECIAL FEES OR CHARGES.
5-4.1 (21) THE SYSTEM MUST BE ABLE TO HANDLE VARIOUS BILLING RATES
FOR INMATES FROM DIFFERENT AGENCIES.
City of Fort Collins cclxvi Proposal P-847
5-4.1 (22) THE SYSTEM MUST BE ABLE TO ACCOMMODATE DIFFERENT
BILLING CYCLES FOR DIFFERENT AGENCIES.
5-4.1 (23) THE SYSTEM MUST AUTOMATICALLY CALCULATE THE BILLING
AMOUNT FOR INMATES HOUSED FROM ANOTHER AGENCY.
5-4.1 (24) THE SYSTEM MUST BE ABLE TO REPORT ON INMATES HOUSED FOR
ANOTHER AGENCY (E.G. DAYS INCARCERATED, LAST DATE BILLED,
BILLABLE AMOUNT, SPECIAL FEES OR CHARGES, BILLING AGENCY
INFORMATION).
5-4.1 (25) THE SYSTEM MUST BE ABLE TO CREATE DETAILED BILLS FOR
EACH AGENCY THAT HAVE INMATES IN OUR FACILITY.
5-4.1 (26) THE SYSTEM SHALL HAVE THE ABILITY TO RECORD AND MAINTAIN
MULTIPLE MASTER INMATE FUND ACCOUNTS SET FOR VARYING
PURPOSES (INDIGENT, COMMISSARY, BOND FEE, MEDICAL FEE,
ETC.) TO INCLUDE TRANSACTIONAL TRACKING OF SUFFICIENT
DETAIL TO ALLOW COMPLETE RECONSTRUCTION OF ANY FUND
MOVEMENT PROCESS FOR AUDITING PURPOSES.
5-4.1 (27) THE SYSTEM SHALL HAVE THE ABILITY TO FULLY RECONCILE THE
MASTER ACCOUNTS AT THE BEGINNING OF EACH FISCAL PERIOD
(BALANCE OR ZERO AS DESIRED).
5-4.2 PROGRAMS
5-4.2 (1) THE SYSTEM SHALL MAINTAIN A LISTING OF QUALIFIED
INSTRUCTORS/VOLUNTEERS FOR VARIOUS PROGRAMS BY AGENCY
DEFINED AND MAINTAINED INSTRUCTION TYPE CODES.
5-4.2 (2) EACH INSTRUCTOR SHALL BE DEFINABLE BY UP TO 99
INSTRUCTION/FUNCTION TYPE CODES.
5-4.2 (3) THE SYSTEM SHALL SEARCH FOR AND DISPLAY QUALIFIED
INSTRUCTORS/VOLUNTEERS BY INSTRUCTION/FUNCTION TYPE
CODE.
5-4.2 (4) THE SYSTEM SHALL INDICATE CURRENT STATUS OF
INSTRUCTORS/VOLUNTEERS (I.E. ACTIVE OR INACTIVE)
5-4.2 (5) THE SYSTEM SHALL MAINTAIN A LISTING OF ACTIVITIES AND
COURSES THAT COULD BE OFFERED.
5-4.2 (6) THE SYSTEM SHALL TRACK ALL PROGRAMS ACTIVITIES (WHO
TAUGHT, WHO WENT, WHAT WAS TAUGHT, WHEN, PASS/FAIL/SCORE
BY PERSON IF APPLICABLE).
City of Fort Collins cclxvii Proposal P-847
5-4.2 (7) THE SYSTEM SHALL ALLOW FOR THE SCHEDULING OF PROGRAMS
RESOURCES (AVAILABILITY OF FACILITIES AND EQUIPMENT).
5-4.2 (8) THE SYSTEM SHALL HAVE THE ABILITY TO PROVIDE BASIC
LIBRARY TRACKING FUNCTIONALITY (INVENTORY AND
CHECKOUT).
5-4.3 VISITATION PROCESSING
5-4.3 (1) THE SYSTEM SHALL HAVE THE ABILITY TO PRE-SCHEDULE AND
TRACK ALL INMATE VISITATION, INCLUDING INDICATING
WHETHER OR NOT THE VISITOR WAS PREVIOUSLY INCARCERATED,
A RECORD OF ALL INMATES VISITED BY DAY AND DATE, AND ANY
PAST PROBLEMS WITH THE VISITOR.
5-4.3 (2) THE SYSTEM SHALL ALLOW FOR THE SCHEDULING OF VISITATION
RESOURCES (AVAILABILITY OF VISITATION SPACES).
5-4.3 (3) THE SYSTEM SHALL THE SYSTEM DISPLAY A LISTING OF ALL
SCHEDULED VISITS FOR AN OPERATOR REQUESTED DATE AND
TIME SPAN.
5-4.3 (4) THE SYSTEM SHALL ALERT VISITATION PERSONNEL OF PENDING
ISSUES AND CAUTIONS IN REGARDS TO POTENTIAL VISITORS
(INDICATE THE TYPE OF NOTIFICATION BELOW);
5-4.3 (4.1) PENDING WARRANTS,
5-4.3 (4.2) PENDING CIVIL PROCESS,
5-4.3 (4.3) OFFICER HAZARDS,
5-4.3 (4.4) GANG AFFILIATIONS,
5-4.3 (4.5) KEEP SEPARATES,
5-4.3 (4.6) VICTIM OF OFFENSE (VISITOR OR INMATE),
5-4.3 (4.7) RESTRAINING ORDER VIOLATIONS,
5-4.3 (4.8) PROPERTY (OR MONEY) TO BE RELEASED,
5-4.3 (4.9) SPECIAL OFFENDER (SEX OFFENDER, PAROLEE, PROBATION,
ETC,),
5-4.3 (4.10) OTHER NOTIFICATIONS
City of Fort Collins cclxviii Proposal P-847
5-4.4 COMMISSARY
In addition to providing an interface to a commissary vendor as specified in global
system specifications, the system must also provide the following commissary
functions;
5-4.4 (1) THE SYSTEM MUST HAVE THE ABILITY TO TRACK AND ISSUE
COMMISSARY THAT INCLUDES FULL BARCODE ENABLED
INVENTORY AND ORDER CONTROL, AUTOMATIC FUNDS DEBITING,
AND THE ABILITY TO DISALLOW PARTICIPATION BASED ON
CURRENT DISCIPLINARY OR CLASSIFICATION STATUS.
5-4.4 (2) THE SYSTEM MUST MAINTAIN A TABLE OF AVAILABLE
COMMISSARY PRODUCTS AND PRICES. THIS TABLE MUST ALLOW
FOR ADDING, MODIFYING AND DELETING PRODUCTS AND MAKING
PRICE ADJUSTMENTS. THIS TABLE MUST BE MAINTAINABLE BY
DIRECT IMPORT FROM A COMMISSARY VENDOR.
5-4.4 (3) THE SYSTEM MUST HAVE THE ABILITY TO LIMIT SELECTION OF
COMMISSARY PRODUCTS BY INMATE, SEX, HOUSING LOCATION,
AND SPECIAL DIET.
5-4.4 (4) THE SYSTEM MUST ALLOW A MAXIMUM DOLLAR AMOUNT FOR
EACH INMATE ORDER.
5-4.4 (5) THE SYSTEM MUST PROVIDE FOR IMMEDIATE CALCULATION OF
INMATE AVAILABLE FUNDS AS THE ORDER IS ENTERED.
5-4.4 (6) THE SYSTEM MUST PROVIDE IMMEDIATE NOTIFICATION IF THE
ORDER EXCEEDS AVAILABLE INMATE FUNDS.
5-4.4 (7) THE SYSTEM MUST BE ABLE TO TRACK THE ISSUANCE OF
INDIGENT PACKAGES TO INMATES.
5-4.4 (8) SELECTION OF THE INMATE FOR ORDER ENTRY MUST BE
AVAILABLE BY NAME SEARCH (ACTIVE INMATES ONLY) OR BY
ENTERING THE INMATE IDENTIFICATION NUMBER OR BOOKING
NUMBER.
5-4.4 (9) THE SYSTEM MUST ALLOW FOR AN INMATE FLAG THAT PREVENTS
COMMISSARY ACCESS FOR A SPECIFIC TIME PERIOD.
5-4.4 (10) THE SYSTEM MUST HAVE THE ABILITY TO PRODUCE ORDER
REPORTS AND PRODUCT USAGE REPORTS.
5-4.4 (11) THE SYSTEM MUST HAVE THE ABILITY TO PRODUCE COMMISSARY
PRODUCT LISTS.
City of Fort Collins cclxix Proposal P-847
5-4.4 (12) THE SYSTEM MUST HAVE THE ABILITY TO PRODUCE INMATE
COMMISSARY HISTORY REPORTS.
5-4.4 (13) THE SYSTEM MUST HAVE THE ABILITY TO PRODUCE ORDER
PAYMENT REPORTS.
5-4.4 (14) THE SYSTEM MUST HISTORICALLY KEEP ALL ORDERS FOR A
SPECIFIED PERIOD OF TIME. FINANCIAL RECORDS MUST BE
PERMANENTLY MAINTAINED.
5-4.4 (15) THE SYSTEM MUST CREATE, UPON REQUEST, AN ASCII FILE OF
COMMISSARY ORDERS FOR A GIVEN TIME PERIOD FOR SELECTED
HOUSING AREAS TO BE TRANSMITTED TO THE COMMISSARY
VENDOR.
5-4.4 (16) THE SYSTEM MUST CREATE, UPON REQUEST, AN ASCII FILE OF
AVAILABLE FUNDS PER INMATE FOR A GIVEN TIME PERIOD FOR
SELECTED HOUSING AREAS TO BE TRANSMITTED TO THE
COMMISSARY VENDOR.
5-4.5 FOOD SERVICES
5-4.5 (1) THE SYSTEM MUST TRACK AND NOTIFY SYSTEM OPERATORS OF
ANY SPECIAL DIETARY NEEDS OR CAUTIONS PER INMATE.
5-4.5 (2) THE SYSTEM MUST BE ABLE TO PRINT AN ALPHABETICAL LISTING
OF ALL INMATES WHO HAVE SPECIAL DIETARY NEEDS OR
CAUTIONS BY HOUSING AREA.
5-4.6 MEDICAL
5-4.6 (1) THE SYSTEM MUST HAVE THE ABILITY FOR MEDICAL PERSONNEL
TO SET A PERSON OF INTEREST FLAG THAT WOULD NOTIFY PRE-
DETERMINED PERSONNEL ANY TIME THAT PERSON IS BOOKED
INTO THE FACILITY.
5-4.6 (2) THE SYSTEM MUST HAVE AN INITIAL MEDICAL ASSESSMENT
PROCESS THAT ALLOWS FOR INITIAL MEDICAL SCREENING BY
BOOKING PERSONNEL WITHOUT GRANTING ANY ADDITIONAL
SECURITY TO VIEW ANY OTHER MEDICAL RECORDS.
5-4.6 (3) THE SYSTEM MUST LOG THE NEED FOR AND THE COMPLETION OF
THE INITIAL MEDICAL ASSESSMENT.
5-4.6 (4) THE SYSTEM SHALL PROVIDE FOR RECORDING THE FACT OF
INITIAL MEDICAL ASSESSMENT COMPLETION THAT IS GLOBALLY
VIEWABLE, BUT THE ACTUAL ASSESSMENT SHALL BECOME
City of Fort Collins cclxx Proposal P-847
PROTECTED AND VIEWABLE BY MEDICAL PERSONNEL ONLY UPON
COMPLETION.
5-4.6 (5) THE SYSTEM SHALL ALLOW FOR THE AGENCY SYSTEM
ADMINISTRATOR TO DEFINE (AND REDEFINE) ALL MEDICAL
SCREENING QUESTIONS AND ACTIONS FOR THOSE QUESTIONS.
5-4.6 (6) THE SYSTEM SHALL ALLOW FOR MULTIPLE MEDICAL
QUESTIONNAIRES.
5-4.6 (7) THE SYSTEM SHALL HAVE A PROVISION TO INDICATE A NEED FOR A
MEDICAL WATCH TO BE PERFORMED THAT CAN BE RESTRICTED
FOR VIEWING BY MEDICAL PERSONNEL ONLY.
5-4.6 (8) THE SYSTEM SHALL HAVE A PROVISION TO INDICATE A NEED FOR A
MEDICAL WATCH TO BE PERFORMED THAT CAN BE GLOBAL TO
THE SYSTEM.
5-4.6 (9) THE SYSTEM SHALL HAVE THE ABILITY TO SET AND TRACK MORE
THAN ONE WATCH PER INMATE.
5-4.6 (10) THE SYSTEM SHALL INDICATE THE TYPE OF WATCH TO BE
PERFORMED (I.E. ALCOHOL WITHDRAWAL, DRUG WITHDRAWAL,
HEAD INJURY, SLEEP WATCH, MEAL WATCH, ACTIVITY WATCH,
ETC.).
5-4.6 (11) THE SYSTEM SHALL INDICATE THE INTERVAL OF THE WATCH TO
BE PERFORMED (I.E. RANDOM, MEALTIMES, EVERY 15 MINUTES,
ETC.).
5-4.6 (12) THE SYSTEM SHALL RECORD THE COMPLETION OF THE WATCH BY
TIME, DATE, PERSON PERFORMING THE WATCH, AND COMMENTS.
5-4.6 (13) THE SYSTEM SHALL ALLOW FOR MEDICAL RESTRICTIONS TO BE
SET THAT WOULD THEN FLAG THE INMATE RECORD AND NOTIFY
ANY PERSON ATTEMPTING TO SCHEDULE OR LOCATE THE INMATE
FOR AN ACTIVITY OR IN AN AREA THAT IS RESTRICTED (I.E.
STRENUOUS PHYSICAL EXERTION, HANDICAP, LOWER BUNK
REQUIRED, COT REQUIRED, LOWER TIER ONLY, ETC.).
5-4.6 (14) THE SYSTEM SHALL HAVE THE ABILITY TO SET A FLAG ON THE
INMATE RECORD OF ANY MEDICAL CAUTIONS THAT MAY BE OF
CONCERN FOR OFFICER SAFETY.
5-4.6 (15) ALL MEDICAL, DENTAL, AND PSYCHOLOGICAL INFORMATION
GATHERED ON AN INMATE MUST BECOME A PART OF THE INMATE'S
MEDICAL RECORDS.
City of Fort Collins cclxxi Proposal P-847
5-4.6 (16) THE SYSTEM MUST BE ABLE TO MAINTAIN THE CONFIDENTIALITY
OF ALL MEDICAL, AND DENTAL, AND PSYCHOLOGICAL INMATE
INFORMATION.
5-4.6 (17) THE SYSTEM MUST HAVE THE ABILITY TO RECORD INMATE
MEDICAL HISTORIES.
5-4.6 (18) THE SYSTEM MUST HAVE THE ABILITY TO CHRONOLOGICALLY
RECORD DOCTOR AND NURSE NOTES FOR EACH INMATE.
5-4.6 (19) THE SYSTEM MUST HAVE THE ABILITY TO CHRONOLOGICALLY
RECORD DOCTOR ORDERS FOR EACH INMATE.
5-4.6 (20) THE SYSTEM MUST HAVE THE ABILITY TO RECORD INMATE
MEDICAL VISITS, BOTH INTERNAL AND EXTERNAL; NURSE,
PHYSICIAN'S ASSISTANT, AND DOCTOR.
5-4.6 (21) THE SYSTEM SHALL HAVE THE ABILITY IF VISITS ARE CANCELED
AND RE-SCHEDULED TO ALLOW FOR ENTRY OF A CODED REASON,
A NOTE AND WHO AUTHORIZED THE RESCHEDULING.
5-4.6 (22) THE SYSTEM MUST HAVE THE ABILITY TO TRACK INMATE SPECIAL
NEEDS (E.G. GLASSES, DIABETIC).
5-4.6 (23) THE SYSTEM MUST HAVE THE ABILITY TO TRACK MEDICATIONS
DISPENSED TO INMATES. EXAMPLES OF INFORMATION NEEDED
INCLUDE PRESCRIPTION AND NON-PRESCRIPTION MEDICATIONS,
DOSAGES, HOW DISPENSED, TIME TO BE DISPENSED, PERIOD OF
TIME TO BE TAKEN, INMATE REFUSAL OF MEDICATION, ETC.
5-4.6 (24) THE SYSTEM MUST HAVE THE ABILITY TO FLAG AN INMATE WHO
REQUIRES ISOLATION PRECAUTIONS.
5-4.6 (25) THE SYSTEM MUST HAVE THE ABILITY TO LIST IN DETAIL THE
TYPE OF ISOLATION PRECAUTIONS THAT MUST BE OBSERVED.
5-4.6 (26) THE SYSTEM MUST HAVE THE ABILITY TO TRACK AND DISPLAY
MORE THAN ONE ISOLATION PRECAUTION PER INMATE.
5-4.6 (27) THE SYSTEM MUST FLAG AN INMATE SCHEDULED FOR RELEASE
WHO IS UNDER CURRENT MEDICAL CARE (E.G. TAKING A
PRESCRIPTION DRUG) AND PRINT INSTRUCTIONS FOR THE INMATE.
5-4.6 (28) THE SYSTEM MUST HAVE THE ABILITY TO MAINTAIN AN
INVENTORY OF PRESCRIPTION AND NON-PRESCRIPTION
MEDICATIONS, AS WELL AS MEDICAL SUPPLIES.
City of Fort Collins cclxxii Proposal P-847
5-4.6 (29) THE SYSTEM MUST ALLOW MINIMUM INVENTORY LIMITS TO BE
SET.
5-4.6 (30) WHEN AN INVENTORY ITEM REACHES ITS MINIMUM LIMIT, THE
SYSTEM MUST FLAG THE ITEM AS NEEDING TO BE REORDERED.
5-4.6 (31) THE SYSTEM MUST CREATE AN ONLINE AND PRINTED REPORT OF
ITEMS NEEDING TO BE ORDERED.
5-4.6 (32) THE SYSTEM MUST BE ABLE TO REPORT ON INMATE MEDICATION
USAGE, ESPECIALLY CONTROLLED SUBSTANCES.
5-4.6 (33) THE SYSTEM MUST BE ABLE TO TRACK TREATMENTS ORDERED
FOR INMATES AND FLAG THOSE TREATMENTS NOT ADMINISTERED.
5-4.6 (34) THE SYSTEM SHALL HAVE THE ABILITY TO GLOBALLY INDICATE
ON AN INMATE RECORD APPROVAL OR DENIAL FOR THE INMATE
TO PARTICIPATE IN ANY NUMBER OF AGENCY DEFINABLE AND
MAINTAINABLE PROGRAMS OR ACTIVITIES.
5-4.6 (35) THE SYSTEM SHALL HAVE THE ABILITY TO TRACK MORE THAN
ONE TYPE OF MEDICAL APPROVAL PER INMATE.
5-4.6 (36) THE SYSTEM SHALL RECORD MEDICAL APPROVAL WITH THE USE
OF AN AGENCY MAINTAINED PICK LIST.
5-4.6 (37) THE SYSTEM SHALL HAVE THE ABILITY FOR MEDICAL PERSONNEL
TO PLACE AND RELEASE MEDICAL HOLDS THAT WOULD PREVENT
INMATE RELEASE UNTIL THE HOLD IS SATISFIED.
5-4.6 (38) THE SYSTEM MUST HAVE THE ABILITY TO BILL INMATE ACCOUNTS
FOR MEDICAL COSTS AND SERVICES.
5-4.7 MENTAL HEALTH
5-4.7 (1) THE SYSTEM MUST HAVE THE ABILITY TO CLASSIFY AN INMATE AS
A SUICIDE RISK AND MAINTAIN THIS INFORMATION HISTORICALLY.
5-4.7 (2) THE SYSTEM MUST HAVE THE ABILITY FOR MENTAL HEALTH
PERSONNEL TO SET A PERSON OF INTEREST FLAG THAT WOULD
NOTIFY PRE-DETERMINED PERSONNEL ANY TIME THAT PERSON IS
BOOKED INTO THE FACILITY.
5-4.7 (3) THE SYSTEM MUST BE ABLE TO TRACK AND CHRONOLOGICALLY
RECORD DETAILED INMATE PSYCHOLOGICAL INFORMATION.
5-4.7 (4) THE SYSTEM SHALL ALLOW FOR MENTAL HEALTH RESTRICTIONS
TO BE SET THAT WOULD THEN FLAG THE INMATE RECORD AND
City of Fort Collins cclxxiii Proposal P-847
NOTIFY ANY PERSON ATTEMPTING TO SCHEDULE OR LOCATE THE
INMATE FOR AN ACTIVITY OR IN AN AREA THAT IS RESTRICTED
(I.E. LIBRARY ONLY, STAFF RUN ONLY, ALL PROGRAMS, ETC.).
5-4.7 (5) THE SYSTEM SHALL HAVE A PROVISION TO INDICATE A NEED FOR A
PSYCHOLOGICAL WATCH TO BE PERFORMED THAT CAN BE
RESTRICTED FOR VIEWING BY MENTAL HEALTH PERSONNEL ONLY.
5-4.7 (6) THE SYSTEM SHALL HAVE A PROVISION TO INDICATE A NEED FOR A
MENTAL HEALTH WATCH TO BE PERFORMED THAT CAN BE GLOBAL
TO THE SYSTEM.
5-4.7 (7) THE SYSTEM SHALL HAVE THE ABILITY TO SET AND TRACK MORE
THAN ONE WATCH PER INMATE.
5-4.7 (8) THE SYSTEM SHALL INDICATE THE TYPE OF WATCH TO BE
PERFORMED (I.E. SUICIDE RISK, EMOTIONAL INSTABILITY,
MEDICATION REQUIRED, SLEEP WATCH, MEAL WATCH, ACTIVITY
WATCH, ETC.).
5-4.7 (9) THE SYSTEM SHALL INDICATE THE INTERVAL OF THE WATCH TO
BE PERFORMED (I.E. RANDOM, MEALTIMES, EVERY 15 MINUTES,
ETC.).
5-4.7 (10) THE SYSTEM SHALL RECORD THE COMPLETION OF THE WATCH BY
TIME, DATE, PERSON PERFORMING THE WATCH, AND COMMENTS.
5-4.7 (11) THE SYSTEM SHALL HAVE THE ABILITY TO SET A FLAG ON THE
INMATE RECORD OF ANY PSYCHOLOGICAL CAUTIONS THAT MAY
BE OF CONCERN FOR OFFICER SAFETY.
5-4.7 (12) ALL MEDICAL, DENTAL, AND PSYCHOLOGICAL INFORMATION
GATHERED ON AN INMATE MUST BECOME A PART OF THE INMATE'S
MEDICAL RECORDS.
5-4.7 (13) THE SYSTEM MUST BE ABLE TO MAINTAIN THE CONFIDENTIALITY
OF ALL MEDICAL, DENTAL, AND PSYCHOLOGICAL INMATE
INFORMATION.
5-4.7 (14) THE SYSTEM SHALL HAVE THE ABILITY FOR MENTAL HEALTH
PERSONNEL TO PLACE AND RELEASE MENTAL HEALTH HOLDS
THAT WOULD PREVENT INMATE RELEASE UNTIL THE HOLD IS
SATISFIED.
City of Fort Collins cclxxiv Proposal P-847
5-5 ADMINISTRATIVE FUNCTIONALITY
5-5.1 JMS INCIDENT AND DISCIPLINARY REPORTING (JMSIDR)
The jail management system, incident and disciplinary reporting (JMSIDR) module
manages inmate misconduct. This misconduct can include major and minor rules
violations that can lead to changes in inmate status. These changes may include, but are
not limited to, loss of time earned towards sentence length reduction, verbal or written
warning, lock down, reclassification, and loss of privileges. The proposed system must
include a jail incident and disciplinary reporting system that is separate from the RMS
incident reporting system.
5-5.1 (1) THE JMSIDR SHALL HAVE A MECHANISM TO ENTER UNLIMITED
NARRATIVE WITH SPELL CHECK CAPABILITIES.
5-5.1 (2) THE JMSIDR SHALL HAVE A MECHANISM TO ENTER INVOLVED
PEOPLE (IT MUST ALLOW THE ABILITY TO INCLUDE OR EXCLUDE
ANY PEOPLE ON QUERY AND HARD COPY REPORTS).
5-5.1 (3) THE JMSIDR SHALL HAVE A MECHANISM TO ROUTE REPORTS TO
APPROPRIATE MANAGEMENT PERSONNEL.
5-5.1 (4) THE JMSIDR SHALL HAVE A PROVISION FOR SUPERVISORY REVIEW
AND ACCEPTANCE.
5-5.1 (5) THE JMSIDR SHALL HAVE A PROVISION FOR ASSIGNING REPORTS
TO CERTAIN PERSONNEL AND SHOW WHO THE REPORT HAS BEEN
ASSIGNED TO.
5-5.1 (6) THE JMSIDR SHALL HAVE A MECHANISM TO PRODUCE HARD
COPIES OF INCIDENT REPORTS.
5-5.1 (7) THE JMSIDR SHALL BE ABLE TO REFERENCE ANY ASSOCIATED RMS
INCIDENT REPORTS AND/OR ARRESTS.
5-5.1 (8) THE JMSIDR SHALL HAVE A MECHANISM TO IMPORT THE REPORT
INTO THE RMS STANDARD INCIDENT REPORT SYSTEM.
5-5.1 (9) THE JMSIDR SHALL HAVE A MECHANISM TO TIME-STAMP REPORT.
5-5.1 (10) THE JMSIDR SHALL HAVE A MECHANISM FOR
DISPLAYING/PRINTING PENDING INCIDENT REPORTS.
5-5.1 (11) THE JMSIDR SHALL HAVE A MECHANISM FOR PROVIDING
DISPOSITION AND STATING WHO MADE THE INCIDENT
DETERMINATION.
City of Fort Collins cclxxv Proposal P-847
5-5.1 (12) THE JMSIDR SHALL HAVE A PROVISION FOR AN APPEAL PROCESS
INCLUDING MANAGEMENT BY TIME.
5-5.1 (13) THE JMSIDR SHALL HAVE A PROVISION FOR AN AGENCY
MAINTAINED TABLE OF TYPE CODES FOR THE TYPE OF INCIDENT
REPORT.
5-5.1 (14) THE JMSIDR SHALL HAVE A MECHANISM TO PROVIDE
INFORMATIONAL REPORTS.
5-5.1 (15) THE JMSIDR SHALL HAVE A MECHANISM TO PROVIDE MEDICAL
BASED INCIDENT REPORTS.
5-5.1 (16) THE JMSIDR SHALL HAVE A DISSEMINATION LEVEL FLAG.
5-5.1 (17) THE JMSIDR SHALL PROVIDE ALL PREVIOUS INCIDENT HISTORY
FOR ANY INMATE BASED ON SECURITY LEVEL OF USER.
5-5.1 (18) THE JMSIDR SHALL ALLOW FOR THE ABILITY TO CLASSIFY
INCIDENT (SIMILAR TO A JMS INCIDENT NAME).
5-5.1 (19) THE JMSIDR SHALL ALLOW FOR THE ENTRY OF UP TO 99 JMSIDR
INCIDENT NAMES PER REPORT.
5-5.1 (20) THE JMSIDR SHALL ALLOW FOR THE ABILITY TO SET A LEVEL OF
INCIDENT (SEVERITY OF INCIDENT) THAT COULD DRIVE THE POST
PROCESS OF THE INVESTIGATION.
5-5.1 (21) THE JMSIDR SHALL PROVIDE THE ABILITY TO MOVE TO DROPPED
SANCTIONS TO A SEPARATE AREA OF THE DATABASE AND TO
REMOVE LINKS TO THE SANCTIONED INMATE(S) CORE RECORD
WHILE STILL ALLOWING FOR A SEARCH (BASED ON SOMETHING
OTHER THAN INMATE NAME) TO DISPLAY THE INCIDENT ITSELF
(SEARCHING ON THE INMATE NAME MUST NOT DISPLAY THE
RECORD).
5-5.1 (22) THE JMSIDR SHALL HAVE THE ABILITY TO ATTACH SCANNED
DOCUMENTS TO THE INCIDENT REPORT.
5-5.1 (23) THE JMSIDR MUST PROVIDE THE ABILITY TO TRACK "USE OF
FORCE" INCIDENTS AND INVESTIGATION RESULTS.
5-5.1 (24) THE JMSIDR SHOULD HAVE THE ABILITY TO LINK ALL INMATES
INVOLVED IN A PARTICULAR INCIDENT OR ALL INCIDENTS
INVOLVING A PARTICULAR INMATE.
5-5.1 (25) THE JMSIDR MUST PROVIDE THE ABILITY TO VIEW AND OR PRINT
DATES AND TIMES OF VIOLATIONS, LOCATION(S) OF VIOLATIONS,
City of Fort Collins cclxxvi Proposal P-847
THE TYPE OF HOUSING AREAS AND THE TYPE OF VIOLATION AND
DISPOSITION SEQUENCED BY DATE, TIME, HOUSING AREA AND
FACILITY FOR USER SPECIFIED SELECTION CRITERIA, (E.G.
HOUSING AREA, VIOLATION, DISPOSITION, INMATE, OFFICER
INVOLVED, DATE, TIME, DAY OF THE WEEK).
5-5.1 (26) THE JMSIDR SHALL HAVE THE ABILITY TO MARK THE INCIDENT OR
DISCIPLINARY EVENT AS CONFIDENTIAL RESTRICTING ACCESS TO
CERTAIN USER GROUPS BY THE ORIGINATING SUPERVISOR.
5-5.2 ACA VALIDATION AND CERTIFICATION
5-5.2 (1) THE SYSTEM SHALL PROVIDE FUNCTIONALITY SPECIFIC TO THE
TRACKING AND MANAGEMENT OF ACA ACCREDITATION.
5-5.3 SOCIAL SECURITY ADMINISTRATION
5-5.3 (1) THE SYSTEM SHALL PROVIDE FOR TRACKING AND NOTIFICATION
TO THE SOCIAL SECURITY ADMINISTRATION OF INMATES THAT
ARE INCARCERATED FOR EXTENDED PERIODS OF TIME SO THAT
BENEFITS FOR THAT INDIVIDUAL CAN BE SUSPENDED.
5-6 ALTERNATIVE SENTENCING PROGRAMS
The Larimer County Sheriff’s Office has an extensive Alternative Sentencing Unit (ASU)
that administers a number of different programs to allow serving sentences for the
commission of crimes in ways that are more beneficial to the community than having an
inmate serve straight time in the jail. It is expected that the RMS/JMS that will be
purchased by the participating agencies will be capable of managing these inmates as well
as those in the jail. The ASU has four primary programs it administers;
Work Release (WR) - Inmates hold regular jobs, but spend all their off time for the
duration of their sentence at a facility operated by the Sheriff’s Office. The system will
have to track their status as an inmate, manage the assignment and reservation of available
beds (hotel function), and track the inmate’s location and the failure to be at a certain
location at a certain time.
Workender (WE) - Inmates report to the Sheriff's Office two days a week for the duration
of their sentence (could be any two days of the week) for assignment to a work crew. Time
served is counted for each day they are participating on a work crew. Inmates stay
overnight for one night of the two days. The system will have to track their status as an
inmate, manage the assignment and reservation of work slots, and track the inmate’s time
served over many months of two day check ins.
Useful Public Service (UPS) - Inmates are sentenced to perform a certain number of hours
performing some task that benefits the community. The time spent performing these tasks
is not directly supervised by the staff at ASU, but is instead tracked and reported by a
reliable third party such as an employer or program manager. Reports are generally
City of Fort Collins cclxxvii Proposal P-847
submitted on a weekly basis and are then entered into a computer program as a credit to
their sentence. Sentence is complete when all the hours of the sentence have been
accounted for. Some inmates are sentenced to perform a certain number of hours per year
for the rest of their lives and will never complete their sentence until their death. The
system will have to track their status as an inmate and the actual time they have worked
over many entries.
Home Detention (HD) - Inmates can hold regular jobs, but spend all their off time at their
residence for the duration of their sentence. Their location is tracked through the wearing
of an ankle transmitter that is monitored by a third party monitoring service. The system
will have to track their status as an inmate, and track the inmate’s location and the failure
to be at a certain location at a certain time.
It seems that calculation or completion of a sentence in ASU needs to be driven by some
type of applied formula system (calculated on time in for WR, HD, WE, or by number of
hours by date(s) for UPS) (i.e. 100hrs per year for 100 years). - See 5-2.5 “Sentence
Calculation”
5-6.1 (1) SYSTEM MUST ALLOW FOR CONCURRENT PARTICIPATION IN MORE
THAN ONE ASU PROGRAM (I.E. IN WORK RELEASE AND FULFILLING
COMMUNITY SERVICE HOURS AT THE SAME TIME).
5-6.1 (2) SYSTEM SHALL NOTIFY ASU PERSONNEL OF ANY CONTACT WITH
AN ASU INMATE RECORDED ANYWHERE ELSE IN THE SYSTEM.
5-6.1 (3) SYSTEM MUST BE ABLE TO TRACK BILLING AND PAYMENT FOR ASU
PROGRAMS, BY PROGRAM, AND BY COURT CASE WITHIN
PROGRAM.
5-6.1 (4) SYSTEM SHALL HAVE THE ABILITY TO RECORD AND TRACK THE
PAYMENT FOR ANY MANDATED TESTING (ALCOHOL, DRUG
TESTING ETC.) REQUIRED OF ALL INMATES OF THE ASU
PROGRAMS.
5-6.2 WORK RELEASE
5-6.2 (1) SYSTEM SHALL HAVE THE ABILITY TO RECORD AND TRACK THE
PAYMENT FOR A ONE TIME PROGRAM FEE FOR WORK RELEASE.
5-6.2 (2) SIGN IN FOR WORK RELEASE NEEDS TO BE RAPID AND
ELECTRONIC - SYSTEM SHALL HAVE THE ABILITY TO PRINT AN
EXPECTED ATTENDANCE ROSTER THAT LISTS FULL NAME, DOB,
EXPECTED TIME, BARCODE, AND A SIGNATURE CAPTURE BLANK.
5-6.2 (3) SYSTEM SHALL HAVE A MASS CHECK IN / CHECK OUT ROUTINE
THAT CAN CHECK IN AND CHECK OUT GROUPS OF PEOPLE USING
THAT BAR CODE ATTENDANCE SHEET.
City of Fort Collins cclxxviii Proposal P-847
5-6.2 (4) SYSTEM SHALL NOTIFY A PREDETERMINED GROUP OF PEOPLE
WHENEVER A WORK RELEASE INMATE IS OUT OF THE FACILITY
FOR MORE THAN A OPERATOR SELECTED TIME PERIOD IN A 24
HOUR PERIOD (24 HOUR PERIOD TO BE DEFINED BY PERSON)
(USUALLY MORE THAN 12 HOURS).
5-6.2 (5) SYSTEM MUST MAINTAIN SCHEDULES ON WORK RELEASE INMATES
THAT INCLUDES AUTOMATIC CALCULATION OF TOTAL TIME SPENT,
NOTIFICATION SENT TO A SPECIFIED INDIVIDUAL WHEN RETURN
TIMES ARE MISSED.
5-6.2 (6) SYSTEM MUST MAINTAIN A HISTORY OF WORK RELEASE
VIOLATIONS AND ADHERENCE TO THE SANCTIONS IMPOSED.
5-6.2 (7) SYSTEM MUST LOOK FOR, AND WARN OF, POTENTIAL INMATE
CONFLICTS (BASED ON PAST INCARCERATION RECORDS) WHEN
RESERVING SPACE.
5-6.3 WORKENDER
Workender programs are defined as any two days of the week.
5-6.3 (1) SYSTEM SHALL HAVE THE ABILITY TO RECORD AND TRACK THE
PAYMENT FOR A ONE TIME PROGRAM FEE FOR WORKENDER.
5-6.3 (2) SYSTEM MUST HAVE A SENTENCE CALCULATION ROUTINE THAT
CALCULATES AND RECORDS BOTH DAYS SERVED AND NIGHTS
SERVED (2-1 RATIO AT THIS TIME).
5-6.3 (3) SIGN IN FOR WORKENDER NEEDS TO BE RAPID AND ELECTRONIC -
SYSTEM SHALL HAVE THE ABILITY TO PRINT AN EXPECTED
ATTENDANCE ROSTER THAT LISTS FULL NAME, DOB, EXPECTED
TIME, BARCODE, AND A SIGNATURE CAPTURE BLANK.
5-6.3 (4) SYSTEM SHALL HAVE A MASS CHECK IN / CHECK OUT ROUTINE
THAT CAN CHECK IN AND CHECK OUT GROUPS OF PEOPLE USING
THAT BAR CODE ATTENDANCE SHEET.
5-6.3 (5) SYSTEM MUST ALLOW FOR EXCEPTION CHECK IN (ALL EXPECTED
INMATES ARE AUTOMATICALLY ASSUMED TO BE PRESENT UNLESS
OTHERWISE INDICATED).
5-6.3 (6) SYSTEM MUST RECORD A REASON FOR FAILURE TO APPEAR.
5-6.3 (7) SYSTEM MUST LOOK FOR, AND WARN OF, POTENTIAL INMATE
CONFLICTS WHEN RESERVING SPACE.
City of Fort Collins cclxxix Proposal P-847
5-6.4 USEFUL PUBLIC SERVICE
5-6.4 (1) SYSTEM SHALL HAVE THE ABILITY TO TRACK THE EXPECTED
PARTICIPATION IN THE UPS PROGRAM BASED ON ENTRY OF A
COURT ORDER AND RECORD AT MINIMUM;
5-6.4 (1.1) FULL NAME (TIED TO MASTER NAME INDEX),
5-6.4 (1.2) COURT CASE NUMBER (16 CHARACTER),
5-6.4 (1.3) CONVICTED CHARGE,
5-6.4 (1.4) NUMBER OF COMMUNITY SERVICE HOURS TO SERVE,
5-6.4 (1.5) NUMBER OF DAYS TO COMPLETE THE HOURS,
5-6.4 (1.6) JUDGE’S NAME,
5-6.4 (1.7) SENTENCING DATE,
5-6.4 (1.8) PROBATION OFFICER’S NAME,
5-6.4 (1.9) THE DEADLINE FOR THE COMMUNITY SERVICE,
5-6.4 (1.10) AND A COMMENT AREA.
5-6.4 (2) BASED ON THE SENTENCING DATE THE SYSTEM SHALL NOTIFY ASU
PERSONNEL IF THE PERSON EXPECTED TO PERFORM COMMUNITY
SERVICE DOES NOT REPORT TO ASU AFTER A PRE-DETERMINED
TIME HAS PAST.
5-6.4 (3) SYSTEM SHALL HAVE THE ABILITY TO RECORD AND TRACK THE
PAYMENT FOR A ONE TIME PROGRAM FEE FOR UPS.
5-6.4 (4) SYSTEM SHALL NOTIFY A DESIGNATED PERSON(S) IF THE
DEADLINE FOR THE COMMUNITY SERVICE PASSES AND THE
SENTENCE HAS NOT BEEN FULLY SATISFIED.
5-6.4 (5) SYSTEM MUST TRACK AND MAINTAIN SCHEDULES ON INMATES
SENTENCED TO USEFUL PUBLIC SERVICE THAT INCLUDES
AUTOMATIC CALCULATION OF TOTAL TIME SPENT, NOTIFICATION
SENT TO A SPECIFIED INDIVIDUAL WHEN CONDITIONS ARE NOT
MET AS SCHEDULED.
5-6.4 (6) SYSTEM MUST MAINTAIN A HISTORY OF USEFUL PUBLIC SERVICE
AND ADHERENCE TO THE SANCTIONS IMPOSED.
City of Fort Collins cclxxx Proposal P-847
5-6.5 HOME DETENTION
5-6.5 (1) SYSTEM SHALL HAVE THE ABILITY TO RECORD AND TRACK THE
PAYMENT FOR A ONE TIME PROGRAM FEE FOR HOME DETENTION.
5-6.5 (2) SYSTEM SHALL HAVE THE ABILITY TO AUTOMATICALLY ASSESS,
RECORD AND TRACK THE PAYMENT FOR A DAILY FEE FOR THE
HOME DETENTION ANKLE BRACELET.
5-6.5 (3) SYSTEM MUST TRACK AND MAINTAIN SCHEDULES ON INMATES
SENTENCED TO HOME DETENTION THAT INCLUDES AUTOMATIC
CALCULATION OF TOTAL TIME SPENT, NOTIFICATION SENT TO A
SPECIFIED INDIVIDUAL WHEN CONDITIONS ARE NOT MET AS
SCHEDULED.
5-6.5 (4) SYSTEM MUST MAINTAIN A HISTORY OF HOME DETENTION
VIOLATIONS AND ADHERENCE TO THE SANCTIONS IMPOSED.