HomeMy WebLinkAbout2022.04.12_Worksession AgendaThis meeting is a work session for Council/Trustee discussion only.
There is no opportunity for public comments at work session.
PUBLIC NOTICE OF THE JOINT MEETING OF THE
OWASSO CITY COUNCIL
OWASSO PUBLIC WORKS AUTHORITY (OPWA)
OWASSO PUBLIC GOLF AUTHORITY (OPGA)
Council Chambers Old Central Building 109 North Birch, Owasso, OK
Tuesday, April 12, 2022 - 6:00 PM
AGENDA APR 08 2022
1. Call to Order
Mayor /Chair Bill Bush
City Clerk's Office
2. Discussion relating to bids received for the purchase of integrated software for Computer
Aided Dispatch, Law Enforcement Records, Mobile Operations, and Court Management
David Hurst
3. Discussion relating to Finance Department items
Linda Holt
A. Annual review of the Owasso Utility Rate Study, Five -Year Utility Rate Plan
B. Fiscal Year 2022 -2023 Budget Calendar
4. Discussion relating to Public Works Department items
Roger Stevens /Dwayne Henderson
A. Request from Oklahoma Department of Transportation to decommission State
Highway 135, located along East 76th Street North from Main Street, extending east to
the Northbound off -ramp of US Highway 169
B. Surface Transportation Project (STP) Grant Applications for the following projects:
• East 116th Street North, from North Memorial Drive to North Mingo Road
• North Garnett Road, from East 116th Street North to East 126th Street North
• US Highway 169 East Service Road, from East 76th Street North to East 86th Street North
C. Project Update - East 1061h Street North and North 129th East Avenue Intersection
5. Discussion relating to City /Authority Manager items
Warren Lehr
A. Monthly sales tax report and revenue outlook
B. City Manager report
6. City Councilor /Trustee comments and inquiries
7. Adjournment
Notice of Public Meeting filed in the office of the City Clerk on Friday, December 10, 2021, and
the Agenda posted at City Hall, 200 South Main Street, at 12:00 pm on Friday, April 8, 2022.
M. Stevens, City
The City of Owasso encourages citizen participation. To request an°accommodotion due to a disability, contact the City
Clerk at least 48 hours prior to the scheduled meeting by phone 918 - 376 -1502 or by email to istevens@citvofowasso.com
TO: The Honorable Mayor and City Council
FROM: David Hurst
Fire Chief
SUBJECT: Computer Aided Dispatch System Purchase
DATE: April 8, 2022
BACKGROUND:
Staff from Emergency Communications, court, records, police, fire and information technologies
(IT) have evaluated the operational stability and condition of the City's computer aided dispatch
(CAD), Report Management System (RMS) and Court Software.
After a thorough evaluation, staff determined the current CAD /RMS, Sheriff's Office Management
System (SOMS®) from M &M Micro System Inc., no longer meets the needs of the City. SOMSO is
built on an older operating system that is no longer supported by M &M Micro System Inc. The
evaluation team concluded that the City is in critical need to replace the current CAD /RMS
system with an updated system capable of reliably delivering emergency service
communications and an RMS, generating a functional dispatching system, report management,
records management, court management and providing analytics.
SOMSO is primarily a law enforcement records management system with CAD capabilities. SOMSO
was an affordable system that met the basic needs of the police department when it was placed
into service in 2011. The SOMS® system worked well for its intended use for a period of time, but
since being placed in service, the system has become cumbersome for dispatchers and patrol
officers, relying heavily on user input with very little automation and, in several areas, requires
duplication of input. SOMS® is limited on its configuration and provides very little support to the
fire department for fire and Emergency Medical Services (EMS) dispatch applications. The City of
Owasso has outgrown the capabilities of SOMSO and requires a modern system capable of
supporting the needs of dispatch, records, court, police and fire.
The evaluation team began meeting in March of 2018. The team reviewed the current capabilities
and limitations of SOMSO. After compiling the information, staff developed a minimum needs list
from the respective departments. With the minimum needs list, staff began researching other
CAD /RMS vendors. Through extensive research and review, staff determined that Central Square,
Tyler Technologies and Motorola were the top three industry leaders with the most capabilities.
Staff made contact with each of the three vendors and set up demonstration meetings to allow
each vendor to demo their product. After assessing the three systems, staff requested a list of
local, regional, and national municipalities that have purchased their systems. Staff then
contacted municipalities from the list, along with other known municipalities, and made several
on -site visits, viewing these systems in real world application. Staff then developed bid
specifications, that would meet the needs of each department.
PROJECT BID
On March 14, 2022, the project bid specifications were sent to Central Square, Tyler Technologies,
Motorola, and posted on the City's website, with a bid opening date of March 25, 2022. Tyler
CAD Software
Page 2 of 3
Technologies was the only bid received. Both Central Square and Motorola submitted a decline
to bid letter.
Staff has reviewed the Tyler Technologies bid proposal for compliance and has determined that
Tyler Technologies' proposal has met adherence of the bid specifications. After thorough review
and consideration of performance, reliability and capabilities, staff concludes that Tyler
Technologies will meet the current and future needs for each department.
Tyler Technologies provides integrated information management solutions and services, with a
focus on local governments. They are based in Plano, Texas, and have offices in 17 states. Their
system offers CAD - dispatching for police, fire and EMS, mobile operations, law enforcement
records and court management.
Dispatch - Tyler Technologies has developed an intuitive CAD program that will allow for
streamlined data collection, information processing and distribute information to the
department users. Tyler eliminates the duplication of work by reducing the number of
computers and programs to enter and process information. When information is entered,
in reference to vehicles or individuals into a call, it is searchable and interfaces directly
with Oklahoma Law Enforcement Telecommunications System (OLETS), vehicle
registration, Department of Motor Vehicles and local systems. This improves efficiency in
the processing of calls into dispatch as well as responder safety. It also interfaces with what
responders are doing in the field in real time allowing dispatch and units in the field to work
together. The Tyler CAD system also integrates with the use of electronic emergency
medical dispatching (EMD) guide cards that assist call- takers in the processing of medical
calls, providing pre - arrival instructions, enhancing care and reducing the liability for the
City. Tyler's system includes call routing, call assignment and resource allocation for
enhanced performance and reduced response times. The CAD system is customizable to
the level of individual user. The information entered into system can cross refence history
within the entire system including alerts for responder safety, rather than one or two fields.
Police - Consolidates records management functions within a single source system, that
includes training documentation, case management, property /evidence management,
employee records, performance tracking, equipment management and scheduling.
Eliminates duplicate reporting. Contains impound reports, driver information exchange
reports, State crash reports and driver license scanning. Mobile operations include
electronic ticketing and warning tracking. Citations and warnings are directly sent
electronically to the Court Clerk. Tyler is Oklahoma State Bureau of Investigation (OSBI)
certified and interfaces directly with Oklahoma Low Enforcement Telecommunications
System (OLETS), checking for criminal history, vehicle registration, insurance, and stolen
property, that can be accessed on scene. Includes police records, that produce standard
the required reports, with the ability to create custom detailed reports. The custom reports
can track crime statistics, criminal activity hot spots with mapping and other informational
reports for actionable intelligence for responsive and proactive decision making.
Improving efficiency and time savings for increased performance and productivity.
Fire /EMS - Offers advanced dispatching for Fire /EMS, with a cross staffing function,
dispatching the closest unit available for a faster response time, along with emergency
medical call questioning and pre arrival instructions. Contains mobile operations that
include mapping, turn by turn directions with recommended response routes, hydrant
locations and preplans.
CAD Software
Page 3 of 3
Court - The Court system interfaces directly with the police record management system,
allowing the Court Clerk and Municipal Judge access to past issued warnings and
contacts by officers. It will automatically transmit electronic citations directly to DPS, which
will minimize duplication of work. When court is cancelled or dates changed, participants
will be notified via text and email, eliminating the need to contact each person individually
via telephone. The system has the ability to administer court virtually when needed. It
manages the check -in system and allows for court proceedings to be conducted in a
protected virtual environment. There would be for less duplication of effort with reporting
and error correction, increasing performance and productivity and allowing for more
intuitive management of the court docket.
• Tyler also offers an evergreen licensing that includes no cost updates and /or system
upgrade.
Tyler Technologies Bid Proposal:
There will also be IT infrastructure upgrades needed to support this project, which include NETAPP
storage and two (2) host servers. These upgrades would be used for this project as well as other IT-
related projects city -wide. Additionally, the City will need to purchase software that gives
dispatchers the ability to provide pre - arrival emergency care instructions to 911 callers during
medical incidents. All of the additional upgrades will come before City Council as separate
agenda items at a later date, with an estimated cost of $155,000.00.
FUNDING:
The General Fund includes the necessary funding for the purchase of a CAD /RMS system.
ATTACHMENTS:
Additional Evaluation Factors
Tyler Technologies Bid Proposal
Tyler Technologies
Police Dispatching
Included
Police Records
Included
E- Citation
Included
Property/Evidence
Included
Added Hardware /Services
Included
Fire /EMS Dispatching
Included
Fire /EMS Mobile
Included
Court
Included
Updates/Upgrade Fees
Included
Total
$999,829.00
Annual Maintenance Fee
$172,990.00
There will also be IT infrastructure upgrades needed to support this project, which include NETAPP
storage and two (2) host servers. These upgrades would be used for this project as well as other IT-
related projects city -wide. Additionally, the City will need to purchase software that gives
dispatchers the ability to provide pre - arrival emergency care instructions to 911 callers during
medical incidents. All of the additional upgrades will come before City Council as separate
agenda items at a later date, with an estimated cost of $155,000.00.
FUNDING:
The General Fund includes the necessary funding for the purchase of a CAD /RMS system.
ATTACHMENTS:
Additional Evaluation Factors
Tyler Technologies Bid Proposal
Additional Evaluation Factors I Tyler Technologies
• Oklahoma OSBI SIBRS Certified Vendor
Yes
• Vendor's Flagship (Tier 1) Offering
Yes
• Integrated proposal with Municipal Court System
Yes
• Integrated proposal with Electronic Citations
Yes
• Advanced Analytics and Reporting Suite
Yes
• Fire Department Advanced Dispatching
Yes
• Publicly Traded & Transparent Finances (NYSE: TYL) Yes
• Financials: Growing, profitable, solid balance sheet Yes
• Largest provider of Public Sector Software in USA Yes
• Has discontinued (end of life) software products No
• Evergreen licensing Yes
• Online Education & Ongoing Training System Yes
• Dedicated Client Executive and Technical Rep Yes
• Oklahoma Regional User Groups Yes
• Award Winning and Industry Leading Support Yes
Friday, March 25, 2022
Ms. Juliann Stevens, City Clerk
City of Owasso
200 S. Main Street
Owasso, Oklahoma 74055
Dear Ms. Stevens:
technologies
840 West Long Lake Road
Troy, Michigan 48098
P: 800.333.9673
www,tylertech.com
Tyler Technologies , Inc. (Tyler) is pleased to provide our proposal to the City of Owasso (City) for an an
integrated public safety and courts system that include Enterprise Public Safety powered by New World
software. With decades of experience in designing, developing and delivering public sector and courts
software nationally, we look forward to the opportunity to partner with the City to implement the
requested software and provide professional services including project management, data conversion,
testing and training.
Should the City have any questions regarding this RFP response, please contact:
Eric Burrell, Account Executive
840 West Long Lake Road
Troy, Michigan 48098
(806) 789 -6117
Eric.Burrell@tylertech.com
Tyler can provide a successfully proven and low -risk approach that will allow the City to quickly achieve
the goals set forth for this project. We look forward to working with you as you consider the options for
this upcoming project and firmly believe that the Tyler solution combines the product, the experience and
the approach to fully meet the project's goals.
Sincerely,
Bryan Proctor
President, Public Safety Division
NON - COLLUSION BID AFFIDAVIT
A. For the purpose of competitive bids, I certify:
1. 1 am the duly authorized agent of Tyler Technologies, Inc. , the bidder submitting
the competitive bid which is attached to this statement, for the purpose of certifying the facts
pertaining to the existence of collusion among bidders and between bidders and state officials or
employees, as well as facts pertaining to the giving or offering of things of value to government
personnel in return for special consideration in the letting of any contract pursuant to the bid to
which this statement is attached;
2. 1 am fully aware of the facts and circumstances surrounding the making of the bid to which
this statement is attached and have been personally and directly involved in the proceedings
leading to the submission of such bid; and
3. Neither the bidder nor anyone subject to the bidder's direction or control has been a party;
a. to any collusion among bidders in restraint of freedom of competition by agreement to bid at
a fixed price or to refrain from bidding,
b. to any collusion with any state /municipal official or employee as to quantity, quality or price in
the prospective contract, or as to any other terms of such prospective contract,
c. in any discussion between bidders and any state official concerning exchange of money or
other thing of value for special consideration in the lettering of a contract, nor
d. to any collusion with any state agency or political subdivision official or employee as to create
a sole- source acquisition in contradiction to Section 85.45j.1 of Title 74
B. I certify, if awarded the contract, whether competitively bid or not, neither the contractor nor
anyone subject to the contractor's direction or control has paid, given or donated or agreed to
pay, give or donate to any officer or employee of the State of Oklahoma or the City of Owasso
any money or other thing of value, either directly or indirectly, in procuring the contract to which
this statement is attached.
STATE OF Michigan 1
COUNTY OF Oakland 1
Bryan Proctor ,being first duly sworn, on oath says that I a the agent authorized by the bidder to submit
the Non - Collusion Affidavit and attached bid.
22nd March 2022
St,lbscribed and sworn before me this _day of
Noto Public MELISSA ANN GIBBS G
Commission# Notary Public- State of Michigan
CountyofOakiand ss
Expiration: - ,as 63
My Commission Expires 24,2023
Acting in the County of
NOTE: COMPLETE THIS AFFIDAVIT AND RETURN WITH BID PROPOSAL
BID PROPOSAL
TOTAL BID: $ 999, 829 (One -time cost plus SaaS fees)
ESTIMATED DELIVERY DATE: Pursuant to the City and Tyler creating a mutually developed project schedule.
Annual Reoccurring Fees / System Maintenance Fees: $ 172,990
*Tyler will not increase annual maintenance fees on Tyler software by more than 3 percent per year in years two through 5.
I hereby acknowledge that I have read the requirements and specifications and that I
am legally bound by the statements in those specifications and on this Bid Proposal -
Submittal page.
Name of Manufacturer:
Name of Vendor /Bidder:
Tyler Technologies software; multiple third -party hardware providers.
Tyler Technologies, Inc.
Printed Name of Person Authorized to Sign:
Signature:
Title: President, Public Safety Division
Vendor /Bidder's Address:
Bryan Proctor
840 West Long Lake Road
Troy, Michigan 48098
Vendor /Bidder's Phone Number: (248) 269 -1000
Comprehensive Public Safety Software Solution
Single /Multi - Jurisdictional Dispatch Software
CAD Mapping
Dispatch questionnaire
Rip -N -Run Printing
Service Vehicle Rotation
E -911
ePCR
Call Entry
Fire Equipment Search
Run Cards /Response Plans
Unit Management
NG911
Fire Records
Call Control Panel
GIS /Geo -File Verification
Rapid SOS
Web CAD Monitor
CAD NCIC
Out -of -Band AVL
Unit Recommendations
Hazard and Location Alerts
Corrections Management Software
Unit Status /Control Panel
Hazmat Search
Additional Modules
Available Interfaces
Pictometry
ASAP
Telestaff
Call Stacking
g
[Inventory
BOLOS
Alarm
VINE
Taalkit
CAD Messaging
Note P
Note Pads
CAD Auto Routing
Enterprise Custom Reports
Pre -Arrival Questionnaire
Twitter
Call Scheduling
Scheduling
proximity Dispatch
CAD AVL
CAD to CAD
Encoder
PEMA Knowledge Center
CAD Paging
CAD CFS Export
Radio location
Records Management
Software for Single /Multi - Jurisdictional Law Enforcement
Arrests
Impounded Vehicles
Training
Equipment and inventory
Ave Interfaces
MiDEx
Buildin s
Incidents
Wants and Warrant
Gang s
Livescam
lACP15
Businesses
Investigations
Hazardous Materials
Ticket Writer
NCIC
Case Management
Order of Protection
Additional Modules
Narcotics
Citizen Reporting
Case Processing
Personnel
Alarms
Pawn Shops
COPLINK
Citations
Property and Evidence
Bookings
Permits Guns i
Accurin[Crime Analysis
Dynamic Reporting
Records Request
q
Briefing Notes
i
Scheduling
LINK
Field Interviews
Registered Offenders
Crash
Content Manager
Evidence
ISR /Clery Reporting
Standard Reporting
Stop Data
Use of Force
SECTOR
Records Management for Fire Departments
Activity Reporting and Hazardous Materials
Personnel /Education
NFIRS /NEMSIS SA Reporting
Fire Permits
Scheduling Hydrant Inventory and
Pre -Plans
Additional Modules
Inventory
Investigations Inspections
Business Registry
Station Activity Log
Data Analysis /Management
LOSAP Tracking and Reporting
Incident Tracking
BLS /AB
Equipment Tracking
Vehicle Tracking and Maintenance
Corrections Management Software
Tyler Corrections NorthPoint Classification
Biometric identification
Available Interfaces
TDEx
eSi natures
g Mobility Tracking
Biometric Hyperpliance
Livescan
Jail
Jail Manager rintegration
Mugshots Jail Data Export
Export
VINE
Taalkit
Enterprise Custom Reports
Mobile Computing
Dispatch /Messaging/
State /NCIC
Fire Dispatch /Messaging
Mobility Software
Law Enforcement Field
Mobile
DLSwipe Mugshot
Download
In -Car Mapping/AVL
Fire Field Mobile
In -Car Routing
Stop Data
Use of Force
Data Collect Mobile
Analytics
Data Marts Public Safety Analytics Agency Intelligence
LE Field Reporting
LE Accident Field Reporting
Field Investigations
Ticket Writer
SPECIFICATIONS FOR BID AND DELIVERY
The below equipment is preferred, but equivalent equipment will be considered as long as
documentation is provided outlining the equivalency:
r
CAD must be part of a modular public safety suite of software to
x
1
include Mobile, LE Records, and Field Reporting.
All modules must be integrated to increase information sharing
x
2
and reduce duplication of effort.
The software must utilize an industry standard relational database
x
3
structure.
CAD must utilize Microsoft SQL Server 2012 or higher as the
x
4
backend database management system.
The server application must operate on MS Windows 2012 Server
x
5
or higher.
The system must provide for mandatory use of agency- specified
x
"codes" in most fields such as Call for Service (CFS) type, call
6
disposition, etc.
The system must provide a list of valid codes for certain "coded"
X
7
fields.
The operator is able to select a code from the list, at which time
x
8
the system enters the code into the field.
All code tables must be able to be updated by the agency's
x
personnel - no requirement for programmer or vendor
9
intervention to maintain any configuration or settings.
CFS and Unit information must be accessible through ad hoc
x
10
query searches with an internal query tool and report writer.
11
Standard CAD Reports can open directly in MS Excel.
x
The application administration functions can be performed by
x
any agency designated person and does not require technical
12
skills.
The application provides module level security using agency and
x
13
roles.
System must be able to accommodate up to 99 CAD
x
14
Dispatcher /Call Taker workstations.
15
System must be able to accommodate up to 750 Mobile units.
x
System must be able to accommodate at least 500,000 annual
X
16
calls for service.
17
Oklahoma OSBI SIBRS Certified
X
17
Ad Hoc Reporting via MS Excel
x
18
Be -On- the - Lookout (BOLO) processing
x
19
Businesses and Places processing
x
20
Call for Service (CFS) Processing
x
21
Configurable CAD Workspace and Templates
x
22
Modern Windows UI with ribbon toolbar
x
23
Integrated Esri Mapping
x
24
Premise /Alert and Hazard Notifications
x
25
System -wide Global Files (Master Indexes)
x
26
Service Vehicle Rotation System
x
27
Unit Recommendations
x
28
Text Paging
x
29
Automatic Vehicle Locator (AVL) Display
x
30
CAD Unit Status Monitor
x
31
CAD -to -CAD Event Transfer
x
32
Multi- Jurisdictional CAD (all disciplines)
x
33
Rip - and -Run Printing /Email
x
34
Integrated Shift Management
x
35
Importing roster from Kronos Telestaff
x
36
State /NCIC Transactions
x
Any name entered by a CallTaker /Dispatcher must provide the
x
capability to be associated or added to the LE Records master
37
name database.
The Call Taker /Dispatcher position must be capable of being
x
38
either local or remote.
The system must flag all incidents /calls that require a report
x
39
submitted by the officer.
The software must separate the CAD CFS number from the LE
x
40
Records Incident and Records Case.
The user must be able to access a command line within the call
x
41
entry window; CAD must support multiple command lines.
The system must provide the ability to attach special response
x
information to any CFS type desired by the agency. This must be
42
automatically displayed when the specified call type is selected.
43
The system must provide the ability to view cleared calls,
x
Cleared call processing must have the appropriate security,
x
defined by the agency, to prevent unauthorized modification
44
and viewing.
The system must have the ability to reactivate cleared calls and
x
allow additional activity /dispatching of units to the original CFS
45
number.
46
The CAD call entry window must show the closest cross - streets.
x
The CAD call entry Window must allow jacket and global vehicle
x
47
processing.
The CAD call entry Window must allow for a non -E911 person to
x
48
be added or deleted.
The CAD call entry window must have a visual indicator on the
x
tabs if the tab contains information.
49
50
The CAD call list must allow users to customize the grid layout.
x
The CAD call list must allow for filters to be set, displaying just one
x
51
type or any combination of call types (police, fire, EMS).
The CAD Quick Entry Cali must support multiple license plates and
x
52
driver's license numbers.
The software must allow multiple Unit Status lists to be opened with
x
53
different configurations.
The software must have a list of values that can be used to
x
facilitate the data entry process, such as abbreviations,
54
directions, status codes and quick prompting
The CAD system must support shortcut or "hot" keys for quick
x
55
navigation.
The software must have the ability to set up permissions for all
x
56
components.
Software must restrict users from operating in any agency unless
x
57
authorized.
Components must have the ability to restrict individual users or
x
58
groups.
59
Components cannot be changed or deleted by users.
x
The software must support role -based security templates, which
x
60
are defined by name.
61
System must support both user and password maintenance.
x
62
Passwords must never be displayed.
x
The system administrator must have the ability to easily create
x
63
users.
The application must allow for Microsoft Active Directory
x
integration across domains; the application user ID and password
64
would be managed by Active Directory.
The system administrator must have the ability to easily change
x
65
passwords.
A user's password can be changed but must not be displayed to
x
66
the system administrator.
A user's password must be encrypted when stored in the
x
67
database.
68
Application permissions can be associated with a user or a role.
x
The software must automatically date and time stamp all CFS and
x
69
unit activity in CAD.
The software must allow supervisors /power users to reset
x
passwords without access to system administrator features or
70
other user authentication functions.
71
The software must provide a purge for the system log.
x
72
The software must support both client and server logging.
x
MOP f r r
s
s.
E91 1 calls must automatically generate and populate the call
x
entry window with all known data (e.g., address, venue,
registered name, phone number, etc.) based on the ANI /ALI
73
information.
The Call Taker screen must capture a minimum of information,
x
including: call type, agency, status, phone number, address, cross
street, nature of call, unlimited narrative and caller /complainant
74
names.
The system must provide agency- defined security features to
x
75
restrict commands and usage for each user.
Once a Call Taker enters the minimal information about an
x
incident it must be immediately available for dispatch or other
76
CAD users
The Call Taker must provide the option to put an unlimited
x
number of partially completed call(s) on hold to retrieve at a later
77
time.
When the Call Taker enters additional information to a current
x
incident, the system must forward the updated communication to
the Dispatcher. Dispatcher must be alerted to call updates by a
78
visual indicator in the call control window.
The Call Taker must have the ability to override geo -based
x
79
addresses and have the system document overridden addresses.
The Call Taker must provide easy access to the Law Enforcement
x
(L.E.) Records name database for additional information on the
Caller /Complainant, such as missing person, outstanding warrant,
80
prior incidents, hazards, etc.
The system must alert all the appropriate Dispatchers when the
x
81
call is ready for dispatch.
Multiple Call Takers and Dispatchers must be able to work on the
x
82
same call simultaneously.
83
The Call Taker must be able to enter individual unit activity.
X
84
The software must allow an unlimited number of Call Takers.
x
The system must allow for the Supervisor to view any Call Taker
x
85
position on demand.
The system must be able to schedule calls for future dispatch (i.e.,
x
parades, funerals, fairs, etc.) and assign to a specific unit as
86
needed
87
The system must be able to display a list of all scheduled calls.
x
88
The system must allow for agency- defined call types.
x
Call Types can be configured with a primary discipline
x
89
Police /Fire /EMS or none.
..},
-��et
90
Priority Indicator
91
Default Status
X
92
Alert Duration
X
93
Report Required
X
94
Call Type Timer
X
95
Primary Agency (P /F /E)
x
The icon displaying the CFS type on the map must be agency
x
96
defined.
Unit recommendations must be agency- defined based on
x
97
configurable response plans.
The software must provide the ability to exchange one unitwith
X
another, automatically recording in history that the first unit was
initially dispatched and then switched with the second unit.
98
The system must be able to reroute a unit from one call to another
x
in a single command and stack the original call against the
99
rerouted unit.
When a rerouted unit is cleared, it must automatically be sent
x
100
back to the original call.
101
Command line entry must be agency defined.
x
102
Commands used in the command line must be agency defined.
x
103
The command line must support all unit and call functionality.
x
104
State /NCIC transactions can be run from the CAD application.
x
105
State /NCIC transactions use agency - configurable forms /masks.
x
106
State /NCIC transactions can run automatically from the call
subject or vehicle information.
x
107
State /NCIC responses can be parsed for critical text and notify
the dispatcher.
x
108
VIN
X
109
State
X
110
Plate
X
111
Color
X
112
Model
X
113
Condition
X
114
Year
X
115
Description
x
116
Style
X
117
The software must allow users to match a vehicle already entered
into the system.
x
118
Vehicle information can be sent to State /NCIC automatically.
x
119
As the call is being entered, any potential associated active call
must be made known to the Call Taker /Dispatcher.
x
120
The system must automatically track all activity by updating a CFS
if dispatch updates any resource working that call.
x
121
Information about intersections, areas, sections, hydrants, etc.,
must be easily displayed based upon the entered address.
x
122
The Call Taker /Dispatcher /Officer working the call must be
notified of any known hazards or alerts based on the location,
subjects or vehicles.
X
123
CAD must create an agency- specific incident number for all
responding agencies that is easily displayed.
x
124
The system must provide capability to create additional incident
numbers for the CFS.
x
125
All narrative entered into an incident must be immediately
available to everyone working the CFS.
126
NCIC Transactions
x
127
All persons or businesses associated with the call
x
128
Special Response Information
x
129
Unit Recommendation
X
130
All Associated Vehicles
x
131
Call and Unit Log
X
132
GIS information to include response areas
x
133
Associated and Linked Calls
x
134
Alerts, Hazards, and Call History
x
135
Narrative
x
136
Call Questionnaire (agency configured based on call type)
x
137
Dispositions
x
138
Service Vehicle Rotation
x
139
The system must allow a CFS to be canceled prior to dispatching
it, and record that activity showing a cancelled CFS.
x
140
The system must provide the Call Taker /Dispatcher with a visual
indicator if a CFS type has an associated questionnaire.
x
141
The software must support CAD commands and descriptions that
can be maintained by a system administrator.
142
Activate Mode of Operation
X
143
Add Call Disposition
X
144
Add Call Stack
X
145
Add Unit Disposition
X
146
Add Unit to Cross Staffing Group
x
147
Alert Search
x
148
Call Type Timer Check In
x
149
Cancel Call
x
150
Change Call Location
x
151
Change Dispatch Position
x
152
Change Status of All Units on Call
x
153
Change Unit Personnel
x
154
Change Unit Status
X
155
Clear Call
X
156
Clear Call Change Trackers
x
157
Clear Units Assignment
x
158
Close Command Line
x
159
Copy Call
x
160
Create Call from Alarm Permit
x
161
Create Case Number
X
162
Cycle Command Line
x
163
Disassociate Call
X
164
Dispatch Unit to Location
x
165
End Unit Pursuit
X
166
Exchange Units
x
167
Execute User Interface Command
x
168
Global Subject Search
x
169
Launch Emergency Medical Dispatch
x
170
Load Template
x
171
Make Primary Unit on Call
X
172
Move Up Unit
x
173
New Call
x
174
New Narrative
X
175
New Quick Call
x
176
New Unit Log Entry
x
177
Notepad Search
x
178
Purge E911 Queue
x
179
Remove Call Links
x
180
Remove Unit Dispositions
X
181
Remove Units from Cross Staffing group
x
182
Report Fire Controlled
X
183
Request Incident for Call
X
184
Reroute Unit
x
185
Return Unit to Cross Staffing group
X
186
Run NCIC Form
X
187
Run NCIC Query
X
188
Search Cleared Calls
x
189
Search Location Alerts
X
190
Send Call Page
x
191
Send Chat Message
x
192
Send Custom Page
X
193
Set Ready for Dispatch
x
194
Set Standby Unit
x
195
Show Call
X
196
Show Call in Default Window
x
197
Show Call Stack
x
198
Show EMD Summary
x
199
Show Recommendations
x
200
Show Unit Detail
X
201
Show Unit Log
X
202
Show Unit Personnel
x
203
Start Track Unit
x
204
Stop Track Unit
x
205
Test Tone (tone encoders)
x
206
Transfer Call
x
207
Update Call
X
208
Update Unit Check In
x
209
Update Unit Dispatch Location
x
210
Update Unit Information
x
211
Update Unit Location
x
212
Update Unit Secondary Location
x
213
Update Unit Station
x
214
Update Unit Timer
x
215
Update Unit Vehicle Number
x
216
Zoom to Call
X
217
Zoom to Point
X
218
Zoom to Unit
x
219
E911 calls must automatically generate and populate the call
entry window or E911 queue with all known data (e.g., address,
venue, registered name, phone number) based on the call -in
number.
x
220
The dispatch screen must provide quick and easy access to all
CFS information, specifically type, agency, status, phone number,
address, cross street, nature of call, unlimited narrative and
caller /complainant nome(s).
x
The system must provide the option to set up a dispatch position
x
as Law Enforcement only, Fire only, EMS only, combined Fire and
EMS, or combined Law Enforcement, Fire and EMS.
221
Multiple call takers and dispatchers must be able to work on the
x
222
some call simultaneously.
The call list must display all calls that are assigned to a dispatch
x
223
1 position.
The system must provide agency- defined security features to
x
224
restrict commands and usage for each user.
The software must provide dispatchers with access to all unit
x
recommendations and unit commands based on Law
225
Enforcement, Fire and EMS access security.
The software must provide the ability to access any CAD function
x
226
based on authorized security.
The system must provide the ability to filter (e.g., include or
x
exclude) types of calls from the call list.
227
228
All dispatch positions can have access to all call types.
x
The software must automatically dispatch stacked calls in order
x
229
when a CFS is cleared.
The system must automatically alert the dispatcher of a possible
x
duplicate call when two calls provide addresses that are in close
230
proximity to each other; radius defined by the agency.
The software must provide agency - defined check -in times for
x
officers to increase safety. When an officer exceeds the allotted
time, the software must visually and audibly display a warning
alerting the Dispatcher. The reminder must provide an
231
override /reset feature.
The software must provide agency- defined dispatch timers based
X
on CFS type and priority. The software must visually display a
warning alerting the Dispatcher that too much time elapsed
232
without assigning a unit(s) to the call.
The software must provide the Dispatcher with easy access to the
x
LE Records name database for additional information on the
Caller /Complainant, such as missing person, outstanding warrant,
233
prior incidents, hazards, etc.
Officer initiated quick call and traffic stop call entry functions must
x
234
be accessible from the dispatch position.
The software must allow for officer initiated quick calls and traffic
x
235
stops to be created as a regular incident /call.
Provide address /location verification against a common Esri
X
236
geodatabase.
Supports common names (building, business, landmark, places,
x
237
etc..
238
Common Names are maintainable within the application.
x
Provides street name suggestions to Call Taker with a drop -down
x
239
list as the user types.
Provides intersection suggestions to Call Taker with a drop -down
x
240
list as the user types.
241
Intersecting streets can be entered in any order.
x
The software must allow Dispatchers to override address geo-
x
242
validation, run priority and unit recommendations.
The software must support an unlimited number of dispatch
x
243
positions.
The system must provide the ability to exchange one unit with
X
another, automatically recording in history that the first unit was
244
initially dispatched and then switched with the second unit.
The system must be able to reroute a unit from one call to another
x
in a single command and stack the original call against the
245
rerouted unit.
A call list must display active CFS information
X
246
247
Dispatched Calls vs. Non - dispatched Calls
X
248
Discipline (Police, Fire or EMS - any combination)
x
249
Agency
x
250
Specific Coverage or Response Areas
x
251
Priority
x
252
Unit Number
x
253
Call Type
x
254
Location and /or Common Name
x
255
CFS Number
x
256
CAD Position
X
Dispatchers must be able to quickly dispatch units from a
X
257
displayed list of available units in the call list.
The system must be able to dispatch units and perform call taking
X
258
activities simultaneously at any position.
All Dispatcher /Call Taker positions must be able to filter calls by
X
agency including or excluding specific agencies.
259
The system must provide an integrated Brit mapping solution with
x
the ability to plot incidents /calls and the units on a street map.
The plotting of the incident /unit information must be a by- product
of normal dispatch. The Dispatcher must be able to control the
map from within the CAD display as to zoom, pan and layer
260
control.
CAD GIS data must be maintainable using Esri desktop
X
261
applications.
System supports layers on the map, which can be turned on or off
x
262
based on the level of detail required.
263
All primary dispatch functions must be accessible from the map.
x
264
Map must include a command line.
x
The system must be able to change a unit's status from the
x
265
Command Line or Unit Status monitor window
To dispatch a unit, the software must allow the user to drag and
x
266
drop a unit to the call list.
From the unit control panel, a dispatcher must have access to a
X
list of available calls and dispatch the units to calls.
267
The software must provide Supervisors with the ability to easily
x
support Call Takers and Dispatchers from their own display station,
268
as needed.
The software must provide Supervisors with complete access to
x
269
unit assignments and replacements features.
When a supervisor fills in for a Dispatcher or Call Taker, they will
x
have the ability to perform all call- taking and dispatching
270
operations.
The software must provide Supervisors with the ability to track CFS
x
by Dispatcher using assigned calls or by area.
271
The software must provide Supervisors with the ability to maintain
X
command and functional access for Call Takers and Dispatchers,
272
allowing CFS assignment transfers.
The software must provide Supervisors with the ability to maintain
x
single and combined CFS types (each discipline gets their own
273
call type).
The software must allow Supervisors to easily maintain police unit
x
274
assignments and unit replacements.
The software must allow Supervisors to easily maintain police
x
275
patrol assignments and patrol backups.
The software must allow Supervisors to easily maintain unit timers
x
used for officer safety.
276
The software must allow the entry of alerts or hazards on an as-
x
277
needed basis.
278
Alert types are agency defined and can be proximity based,
x
Alerts can be based on locations, persons, businesses and
x
279
vehicles.
The software must require first name, last name and ID number to
x
280
enter an agency personnel record.
The software must support maintaining personnel records by
x
Originating Agency Identification /Fire Department Identifiers and
281
Identity number.
282
Personnel records require additional permissions to access.
x
Personnel maintenance can display a picture of the employee on
x
283
the initial screen of the personnel record.
Each personnel record must support multiple education /training
x
284
records with agency- defined course codes.
Personnel records must support the attachment of other
x
285
documents.
The personnel record must support multiple assignments and
x
286
require assignment date and type.
The personnel record must support multiple issued equipment
x
287
records and require issued date, item type and quantity.
The software must allow for a universal way to search for and
x
288
select officer ID numbers throughout the applications.
The software must provide chat messaging across CAD, Mobile,
x
x
289
and LE Records.
Available in
Available in
CAD and
LE Records.
Mobile.
The software must provide a separate message screen that shows
x
all Coll Taker, Dispatcher and Mobile Computing messages sent
290
to the Caller Taker /Dispatcher.
The software must allow a CAD user to send and store messages
x
291
to other users, groups or mobile units.
The software must allow a message to be sent to multiple
x
292
recipients.
The software must allow a user to see all unread messages or all
x
293
messages in the last 24 hours.
294
System can archive messages without deleting them.
x
System Administrators must have the ability to search for any
x
295
message regardless of message state.
296
The software must be able to log all messages.
x
The software must automatically schedule CFS for future dispatch
X
to help manage special events, such as parades, funeral details,
297
prisoner transport, etc.
298
The software must be able to display a list of all scheduled calls.
X
The software must allow a user to manually activate a scheduled
X
299
call.
Authorized users must have the ability to activate a scheduled
X
300
call at any time.
301
The software must support location override for scheduled calls.
x
The software must allow units to be assigned to multiple calls at
X
302
the same time.
The software must allow a user to view a unit's call stack to see
X
what call the unit is on, and what calls the unit will be handling
303
next.
304
The software must have only one call that is active per unit.
x
The software must support configuration by agency of mobile
X
alert types, export call types, call type disposition, and associated
305
call types.
The agency must be able to define and associate a
x
306
questionnaire to each CFS type, as needed by the agency.
If a CFS type has an associated questionnaire, the system must
X
307
provide the Call Taker /Dispatcher with a visual indicator.
The software must have an unlimited number of questions, and an
X
308
unlimited number of pre -set answers for each question.
Once the current question of the questionnaire is answered, the
X
309
next button is activated.
310
Once a question is answered, the "Previous" button is enabled,
x
The questionnaires) must have the ability to have the responses
X
selected from a pre -set list of valid answers from a pull -down
311
window or entered as a free -form text.
The questionnaires must allow for an answer to a question to
X
change the priority and the status, as well as add sub - questions to
312
further detail the response.
The questionnaire must provide the ability to prompt the user to
x
change the CFS type based on a question's response. This is not
313
an automatic or mandatory change, but a prompt.
The questionnaire must have the ability to create a default
X
synopsis of the questionnaire, which is updated as questions are
314
answered.
When the questionnaire is closed or saved, the default synopsis is
X
315
stored in the narrative of the call.
The software must allow users to continue to view /use the call
x
316
while the questionnaire is being answered.
The software must only allow one questionnaire narrative entry at
x
a time, because if the user changes answers to questions, the
current synopsis narrative will be updated with the current
317
synopsis.
CAD client can operate as stand -alone client and continue basic
x
dispatch operations without network connectivity or CAD server
318
access while in Catch -Up mode.
Provides mechanism to back enter CFS with correct date and
x
319
times.
Must provide security to limit access to CAD catchup
x
320
functionality.
Allows for blocking out of incident numbers by agency as
x
321
needed.
User only needs to enter the number of incidents to catchup; they
x
322
do not need to know starting or ending incident numbers.
Narratives can be entered in catchup and reflect the actual
x
323
event.
Alert settings include show icon, flash icon, show desktop alert,
x
324
and show map alert.
The software must alert the Call Taker, Dispatcher and /or Officer
x
325
of previous CFS at a location.
The software must alert the Call Taker, Dispatcher and /or Officer if
x
an active warrant exists for any person at the location or for the
326
caller /complainant.
The software must alert the Call Taker, Dispatcher and /or Officer if
x
any gun permits are at the location or guns are registered to the
327
caller /complainant.
The software must alert the Call Taker, Dispatcher and /or Officerif
x
the caller /complainant is a known offender, a suspect in an open
case, or a career criminal.
328
The software must alert the Call Taker, Dispatcher and /or Officer if
x
329
hazardous material is stored at a location.
The software must alert the Call Taker, Dispatcher and /or Officer if
x
there is any serious medical information concerning a person at
330
the location.
The software must alert the Call Taker, Dispatcher and /or Officer if
x
331
the location has an associated vacation check or house watch.
The software must alert the Call Taker, Dispatcher and /or Officer if
x
332
the location is a known narcotics location.
The software must alert the Call Taker, Dispatcher and /or Officer if
x
333
a building pre -plan or geo -file information exists for the location.
The software must alert the Call Taker, Dispatcher and /or Officer if
x
orders of protection are associated with the location and /or
334
caller /complainant.
The system must provide the ability to reactivate an alert in the
x
335
event an expired alert needs to be reactivated.
The software must alert the Call Taker, Dispatcher and /or Officer if
x
a unit has gone over its allocated time, as setup for the CFS type
336
to increase officer safety.
The software must have the ability to set a timer for CFS types
x
based on priority. This timer alerts the dispatcher that an agency -
specified time has elapsed and no units have been assigned to
337
the called.
The software must provide automatic alerts to the Call Taker,
x
Dispatcher and /or Officer on an as- needed basis.
338
The software must allow the user to create an alert with a
x
category, description, and duration of time and an assigned
339
priority for the alert.
The software must allow a note pad function that allows CAD
x
340
users to type in any unlimited text and store the text within CAD.
341
The software must support a subset of note information by type.
x
The software must allow a document to be attached to a note
x
342
via standard document controls.
343
Note pad entries must be date /time stamped.
x
344
Note pad entries can be deleted.
x
The software must allow note pads to be edited and deleted only
x
345
by authorized users.
The software must allow rip and run reports to be sent to a printer
x
346
or via email.
The software must have the ability to determine when rip and run
x
347
reports are sent and the format of the report.
Rip and Run information can be sent multiple times based on
x
multiple triggers (when dispatched, at scene, return to station,
348
etc.).
F
Y S
i
r,
The software must allow the creation of response plans to define
x
Law Enforcement, Fire and EMS unit recommendations that are
used to dispatch units based on the CFS type and location.
349
350
Supports cross - staffing for Fire /EMS units, based on personnel
x
Law Enforcement unit recommendations must be incident type
X
351
specific and allow for multiple levels of backup.
Law Enforcement unit recommendations must support different
x
unit types (i.e., one -man, two -man or K -9) to respond to a CFS
352
based on the incident type, priority and in- progress flag.
The software must support changing the unit's assigned primary
x
353
police beat during the shift.
t
:ISi� j4 i�-x 4al e` Mfr Gtr"ln
354
Agency -based Unit Type
x
355
Response Areas ( Beat /Quadrant /District /Station)
x
356
Radio Number
x
357
Number of crew required
x
358
Vehicle Number
x
359
Capabilities
x
360
Cross - Staffing
x
361
Personnel
x
All Law Enforcement, Fire or EMS unit activity must be captured as
x
362
part of the unit log.
The Law Enforcement, Fire or EMS unit recommendation
x
maintenance must maintain operating procedures on each
363
incident type.
All Law Enforcement, Fire or EMS unit personnel activity must be
x
364
captured in a unit personnel log.
The software must allow agency - defined icons to represent unit
x
365 1
types.
Unit Recommendations can be proximity based and can display
x
366
unit ETA.
Proximity -based recommendations use the street attributes, road
x
367
closures and other GIS information.
Fire /EMS recommendations must incorporate backup units, move
X
368
up and stand by units, and backup stations.
Proximity response plans, routing and ETA calculations leverage
X
Esri network analyst and available GIS data so information is
369
based on "real- world" factors.
CAD must support dynamic unit recommendations where if a
x
better unit fit becomes available after initial dispatch, the system
370
will provide a notification to the dispatcher.
The system must allow the agency to define an icon for each
x
371
type of unit as defined by the agency.
372
All unit statuses can be defined by agency.
X
373
The software must allow the setup of unit timers and call timers.
x
The software must generate a unit log, showing all actions that
X
374
unit had taken.
The unit log must show date /time of entry, status, action, CFS #,
X
375
CFS type, CFS location and unit location.
Response plans can be configured as proximity based, to prefer
X
376
proximity, or area based.
The software must allow the user to assign a priority to the CFS
x
377
and enter the date /time range that the response plan is active.
The software must allow the user to define units or unit
X
type /stations to a CFS based on Fire district (quadrant) and CFS
378
type.
The software must allow a user to define alarm levels for response
X
379
plans.
The software must allow for multiple backups so that if the first
x
backup is unavailable, the system will check for the next available
380
backup.
The software must have the ability to add special response
x
381
narrative for response plans.
The Supervisor must be able to maintain unit response plans as
x
382
needed.
The software must allow units on a response plan to be placed in
x
383
the dispatched or other defined status.
CAD must display unit recommendations with the unit /apparatus
x
384
ETA,
The software must allow the creation of exception and location-
x
385
based response plans.
The software must be able to handle multiple levels of alarm
x
386
responses.
Response plans must be able to use unit type, unit, capability,
X
equipment or skills in determining unit recommendations.
387
The system must allow for recommending units by proximity -based
X
dispatching utilizing the agency's GIS data to determine unit ETAS.
388
The system must provide the ability to recommend units based on
x
agency - defined capabilities such as Haz -Mat, Foam, Lift
389
capabilities, etc.
The system must provide the ability to recommend units based on
x
agency- defined personnel skills (Spanish speaking, rope rescue,
390
hostage negotiation, etc.).
The system must provide for creating alternate response plans
x
(disaster mode) based on agency- defined modes of operation
391
such as storms, wildland fires, or earthquakes.
The system must provide for easy entry of agency- defined
x
response plans that can be associated to multiple areas and call
392
hypes (eliminate duplicate data entry).
The software must allow multiple units lists to be opened with
x
393
different configurations based on CAD workspace template.
The software must provide the ability to filter or subset the list in
x
394
the unit list.
The software must allow to subset by agency type, allowing the
x
395
selection of multiple agency types within any unit list.
The software must allow the user to drag and drop a unit from the
x
396
unit list to a call on the call list.
The software must allow a user to change a unit's status, open the
x
unit's call stack and reroute a unit within the unit list via a mouse
397
click.
From the unit list, a user must be able to get a list of all available
x
398
calls and dispatch the unit to the call.
An option must be available to determine if the unit will display on
X
399
the unit list if the unit is not on a call.
The software must allow the agency to modify the statuses that a
x
400
particular unit can be assigned.
The software must automatically refresh the unit list when
x
401
information is updated.
Unit recommendations can be specific to the CFS type and allow
x
402
multiple levels of backup.
Police unit recommendations must provide for different types of
x
units, such as one -man, two -man or K -9, to respond based on the
403
CFS type, priority and in-progress flag.
A primary police beat can be assigned to a unit at the beginning
x
of a shift or automatically assigned as part of shift management
404
and changed at any time as needed.
The software must be able to swap or exchange one unit with
x
another, and record that the first unit was initially dispatched, and
405
then exchanged with the second unit.
All Law Enforcement, Fire or EMS unit activity must be captured in
x
406
a unit history database.
The system must provide access to the unit recommendation
x
407
process as part of the incoming call.
The software must maintain operating procedures (special
x
response information) on each CFS type.
408
The software must to maintain all agencies, including dispatched
x
409
agencies and non - dispatched agencies.
The software must create agency- specific incidents for a
x
410
particular ORI /FDID.
The software must have the ability to generate an incident
x
411
number for mutual aid agencies.
1
r�1
x
F
412
Alert Listing
X
413
BOLO Listing
x
414
CAD Log Listing
x
415
Daily CFS Detail
x
416
Daily CFS Summary
X
417
Dispatch Threshold
x
418
Dispatcher Log
x
419
False Burglary Alarm
x
420
Officer Dispatch
x
421
Officer Location
x
422
Officer /Unit Status Inquiry List
x
423
Service Vehicle Log
x
424
User Access
x
Z
m9€~ �
Z
425
Briefing Listing
x
426
Building Watch Listing
x
427
Calls by Hour
x
428
Calls by Month
x
429
Call by Priority
x
430
Officer Log
x
431
Unit Status Time Report
X
432
Overridden Address Report
x
433
Personnel History
x
434
Unit Auto Vehicle Locator Report
x
435
Unit Status Response Analysis
x
1
The software must have mapping capability to plot CAD calls
and the units on a map.
x
2
The plotting of the call and unit information must be a by- product
of normal dispatch.
x
3
The CAD map uses a standard windows toolbar.
x
4
The CAD mapping toolbar ((bbon) must be customizable
x
5
CAD Mapping uses standard Windows Help functionality,
x
6
The dispatcher must be able to control the map from within the
CAD display as to zoom, pan and layer control.
x
7
All primary dispatch functions must be accessible from the map.
x
8
The map must have agency defined and maintainable layers
that help identify real -time critical information, such as unit status
and call type.
x
9
The software must allow for the layers on the map to display
automatically based on the zoom level.
x
to
Map layers must be able to be turned on or off manually.
X
The software must provide the ability to dispatch by placing the
x
11
cursor on the unit or the map.
The software must provide the ability to easily change unit status
X
12
and dispatch units right from the map window.
For each call for service type, the icon that displays on the map
x
13
for that call type must be agency definable.
The map must display only the units within the dispatcher's
x
14
assigned Originating Agency Identification or beat.
Standard right -click options must be available to map control.
X
Examples include center map on the unit; override unit time;
check -in unit; change status; and go -to command (to send a unit
15
to a different location).
The map must provide a tool tip on the unit displaying the unit ID
x
16
and unit location when mouse -over the unit.
The map must provide a tool tip on the CFS, which must display
x
the CFS number, the CFS location, and the CFS type when rolling
17
the mouse over the call.
°liar t" r 11 4 '
—
c
18
Previous View
x
19
Find Location
x
20
New Call Here
X
21
Directions from Here
X
22
Directions to Here
x
23
Zoom to Call
X
24
Create simple or complex roadblocks
x
25
Create Map Event
X
26
Create Map Hyperlink
X
27
Enable Clustering
X
28
Show Map Scale
x
29
Show Coordinates
x
30
Show Unit Latency (for AVL Units)
X
31
Show Unit Direction of Travel (for AVL units)
x
32
Show in Picometre
x
The CAD Mapping must meet the guidelines set forth by the FCC
x
regarding wireless carriers to provide information about a caller
33
as part of the 911 call.
The software must have the capability to receive latitude and
x
34
longitude information via the E911 interface.
The software must have the capability to enter latitude and
x
35
longitude of the caller's location in the CAD call entry Window.
The software must retain the latitude and longitude as original call
x
location if the call taker changes the location to an actual
36
address.
The software must plot the Lat /long location on the map control
x
37
panel using a special icon to designate a cell phone call.
The software must provide the ability to draw a shape or a buffer
x
38
around a call or location with a user entered description.
1 Software solution must be built on the Esri platform X
2 Support the Enterprise Level of ArcGIS Server (ArcSDE). x
3 Provide support for Picometre Imagery. x
4 Supports Esri aeodatabose replication. x
GIS data can be stored locally on CAD and Mobile clients (GIS X
functionality available without server connectivity) using Esri map
5 package functionality.
The GIS data can be updated without impacting production ( x
6 operations.
The software must have the ability to plot, with agency- defined
X
icon, known activity (e.g., street closures, parades, construction,
39
etc.).
40
The software must have the ability to open the CPS from the map.
x
Map data updates must not require CAD being in a restricted or
X
41
"down" state
Map must support both a street centerline and an address point
X
42
layer for location verification
The CAD ma p must support su the configuration of a map
X
43
document which controls the default mop view.
The GIS map must be Esri based using an SDE instance within MS
X
44
SQL Server
The CAD map must also provide a view for address verification in
x
45
a separate window
The CAD map must work as a window within the CAD workspace
X
or as a "floating" window to maximize the available screen
46
display.
CAD mapping must support map templates for easy
x
47
configuration and restoration of map settings
Must allow both a default zoom level and a custom zoom level
x
48
for users
CAD mapping must provide a "find location" function that
x
supports both physical locations as well as common names and
49
intersections.
Users must be able to add a call for service into CAD from the
x
50
mop
Users must be able to go to any call for service from the map
X
51
using a right click or context menu.
Mop should support a command line that a user can turn on or
X
52
off.
Users can display "breadcrumbs" to identify tracks of AVL
X
53
equipped units.
CAD map has functionality for user to measure distance or area
x
54
on the map.
Mapping should allow a user to identify any GIS attribute from
X
55
any map layer.
CAD mapping must support finding the nearest address to a
X
location. If a E911 phase II call is entered, the CAD map must be
able to resolve the closest physical location to the coordinates to
56 1
aid first responders.
1 Software solution must be built on the Esri platform X
2 Support the Enterprise Level of ArcGIS Server (ArcSDE). x
3 Provide support for Picometre Imagery. x
4 Supports Esri aeodatabose replication. x
GIS data can be stored locally on CAD and Mobile clients (GIS X
functionality available without server connectivity) using Esri map
5 package functionality.
The GIS data can be updated without impacting production ( x
6 operations.
The system shall provide a mechanism to "activate" any GIS
x
7
updates for both CAD and Mobile.
8
The system shall utilize ArcView ArcSDE for map generation.
x
The system must be able to upgrade to the most current versions
x
of ArcMap, ArcSDE and SQL Server as those versions become
9
available and are deployed.
10
The system shall support definable map symbology.
x
Support the customization of how maps are displayed within the
x
11
Vendor's solution by use of Esri's .MXD files.
Provide the some advanced routing capabilities as available
x
through Esri's Network Analyst. Must be fully integrated into CAD
12
solution.
Support the use of Esri's Dynamic Display technology for high
x
13
performance display of Units, CFS, etc., on the CAD Map.
14
Support a Services Oriented Architecture.
X
15
Support the use of a common Enterprise Geodatabose.
x
16
Support Multiple Locator Services for geocoding.
x
Support multiple map documents for CAD, LE Records, and
x
17
Mobile.
Support the use of scale tolerances for map layers to allow
x
18
certain layers to appear at appropriate zoom levels.
Support the ability to use agency- defined icons for units, CFS,
x
19
etc., in the software.
20
Support the use of Hyperlinks within the CAD Map.
X
Supports proximity dispatch, routing and ETA using Esri
x
21
technology.
Can leverage the centerline attributes as part of the network
x
22
dataset for routing, ETA, and driving directions.
Ability to enter an address on a map and find directions between
x
23
two locations
Ability to display shortest route from point -A to point -B (i.e., street
x
network routing), and highlight quickest route, including directions
based upon roadway /access availability (e.g., construction,
24
detours).
Ability to highlight on the map the recommended route from
X
25
current location to a dispatched incident site.
The mapping application must include the ability to provide
x
mobile units with routing information to a dispatched incident
26
from their current GPS /AVL location.
Routing to an event uses street impedances to factor fastest
X
27
route.
28
Must provide both turn -by -turn and route indicator on map.
X
CAD must provide a driving directions toolbar which launches a
X
directions window for easy navigation, allowing the directions to
29
"float" over the map.
30
Auto Routing must support both units to calls and from call to call.
x
The auto routing feature must use a "find route" function that
x
allows both text -based driving directions and a visual route line on
31
the map.
Routing accounts for unit /apparatus details (height, weight, turn
x
32
radius) in conjunction with street impedances.
I
CAD AVL must be integrated with vendor's Mobile solution.
x
2
Must support various GPS devices based on NMEA standards.
x
3
Must provide configurable icon to track unit on map.
x
4
Must capture unit and incident location as part of playback
feature.
x
5
AVL Playback must use the integrated CAD map and not require
a separate map.
x
6
AVL Playback must allow selection of specific unit(s).
x
7
AVL Playback must allow selection of date /time ranges.
x
8
AVL Playback must show the unit location, coordinates and
seed for each stored AVL transmission.
x
9
AVL Playback must show active incidents within the selected
date /time range.
x
IN
Sr't �y ��%.�j`jr..jj �Tm�pi�aYs54'py� -0 R,- _,yS 'b.5k���`g�j yy`+.��- .G NOMINEE; i _ 5
MINE
The software must quickly and equitably send wreckers, tow
x
1
trucks or other service vehicles to a specific location.
The software must setup wrecker response based on geographic
x
coverage, hours of operation, type of equipment or service
2
required, as well as company's place in the dispatch sequence.
The software must maintain a database of service vehicle
x
3
providers that want to maintain a rotation schedule.
The software must show where in the rotation a provider is placed
x
4
if a special event occurs when attempting contact.
The software must automatically position the second company in
x
5
the first position when the first company is selected.
The software must allow the user to dispatch the next company,
x
when unable to reach the first company in line, without moving
6
the first company to the bottom of the rotation sequence.
The software must generate a service vehicle log and service
x
7
rotation listing.
The software must be able to display service vehicle areas on the
x
8
CAD map as a separate layer.
The system must provide Wrecker /Ambulance Rotation software
x
to help Dispatchers dispatch a wrecker or private ambulance to
9
a call.
10
Service vehicle types must be configurable by agency.
x
Service vehicle rotation must be fully integrated with the CAD
x
map using map polygons to represent areas for easy
11
maintenance.
aeyta�"'E" S
Sr't �y ��%.�j`jr..jj �Tm�pi�aYs54'py� -0 R,- _,yS 'b.5k���`g�j yy`+.��- .G NOMINEE; i _ 5
The software must send text pages, using freeform text, to field
X
2
personnel with alphanumeric pagers.
3
The software must send text pages to groups of pagers.
x
The software must allow for the entry and maintenance of pagers
x
or groups of pagers that have been added to the pager
4
software.
CAD Paging must support numerous paging protocols to include:
x
Standard Telelocator Alphanumeric Protocol (TAP), Simple Mail
Transfer Protocol, (SMTP), Simple Network Paging Protocol (SNPP)
5
and Wireless Communications Transfer Protocol WCTP .
Paging must provide the CAD CFS details in the body of the text
x
page including location, coordinates, closest intersections and
6
narrative.
Paging should allow configuration of the paging message
x
including "literals" that would allow agencies to define their own
7
label for fields in the page.
Configuration for paging must be available from unit
x
8
maintenance to allow easy setup of group pages
9
Paging must be supported from the Command Line in CAD.
x
Paging must be supported from the unit response
x
10
recommendations window.
CFS types must support automatic paging so that certain
x
1 1
dispatch events will be paged without user intervention.
Access to paging functions must be controlled by the application
X
12
security.
Paging maintenance must support drag and drop functionality to
x
13
quickly and easily configure paging groups.
The CAD application will provide a separate "Send Page' window
x
14
for users to send text pages outside of a CFS.
The "Send Page" window should provide a drop -down list of
x
individuals and groups that can be paged allowing the user to
15
quickly select from the list.
Users will be able to view unit attributes from anywhere in CAD
x
16 1
and see which paging rou the unit is assigned to
n t 0
The E911 interface must provide an interface between the
x
17
ANI /ALI controller and the CAD system.
E911 should support most ANI /ALI controllers and industry
X
18
standard E911 formats such as 30W and ALI GTE.
The E -911 interface must transfer ANI/AU information into the CAD
x
software, either by means of a call queue and /or automatically
populating a call for service data entry window.
19
20
Fields transferred into CAD must include the following:
21
Call received date and time
x
22
Telephone number
x
23
E -911 Address
X
24
Special Instructions
x
Phone subscriber information (Residence, Business, Cellular, PBXB,
x
25
etc..
26
The E -911 interface must be Cellular Phase I and Phase II
compliant.
x
27
In the event of Cellular Phase II calls, the CAD System shall
provide users the ability to locate the nearest address directly
from the CFS data entry window, without having to utilize the
map.
x
28
With a Cellular Phase II call, the CAD system will allow users to
locate the nearest address to the call coordinates using the map.
x
29
The interface must automatically link E91 1 data into the computer
system via a communications port to a multi -user, multi- tasking
workstation.
x
30
The CAD software must be able to load data directly from an
E911 system.
X
31
The system must be able to accept data from a caller ID system.
x
32
The interface must provide the ability to transfer and maintain the
following data elements from the phone company's database to
the CAD system:
33
The interface must accommodate changes in the ANI /ALI layout
without requiring programming or vendor modifications
X
34
Time of Call
X
35
Date of Call
x
36
Customer Name
X
37
House Number
x
38
House Number Suffix
x
39
Street Name
X
40
Zone (ESN)
x
41
City /Community
X
42
Class of Service
X
43
Operator Position
x
44
The interface must accommodate changes in the ANI /ALI layout
without requiring programming or vendor modifications
x
45
The interface must provide the ability to discriminate between.
class of service on the telephone ALI record and appropriately
handle the class of service field on the CAD screen.
X
46
The interface must allow for validation checks against:
47
Address verification file
x
48
Active CFS
x
49
Previously entered hazards
X
50
Activate various checks in an E91 1 control file
x
51
Cell phone capability to plot caller location
x
52
EMS Questionnaire
X
53
AVL
X
54
Building Watch
X
55
Ability to Lookup Personnel History
X
56
Accept or Override Priority
x
57
Unlimited Filter Capability
x
58
Maintain user configured Window preferences
x
59
Check Subject, Vehicle and Location master files
x
60
Ability to Add Narrative to Call
x
The E91 1 interface must provide support for emerging NG 911
x
61
standards and provide a framework for IP -based communication.
The software must seamlessly interface with ProQA EMS Dispatch
x
62
or APCO MEDS, a third party - application.
The ProQA /APCO MEDS interface must automatically launch
x
63
upon agency- defined call types.
64
ProQA must be able to be called from the CAD Command Line.
x
CFS information must be transferred from CAD to the
x
ProQA /APCO MEDS interface via a text file that meets technical
65
specifications.
66
Response information is written to CAD narrative for the CFS.
x
The CAD software must provide the ability to automatically
x
launch ProQA or APCO MEDS as a call type is entered, via the
67
interface.
The CAD software must allow the user to manually launch ProQA
X
66
or APCO MEDS as desired, via an interface.
69
The ProQA /APCO MEDS interface must be bi- directional.
x
The CAD Narrative must be populated with pertinent EMD
X
70
questions /answers as well as any determinant codes.
The ProQA /APCO MEDS interface must allow for the automatic
x
change of the call type, depending on the final answers to
71
questions,
a
The tone encoder interface must support Zetron 25, 26, and IPFSA
X
72
tone encodin
The tone encoder interface must support Westnet First In and
x
73
ComTech station alertin s stems
Tones must be automatically sent from the unit recommendation
x
74
window
CAD must provide an option to send tone information from unit
x
75
recommendations
Toning must be provided using a web service framework for easy
x
76
troubleshooting
Toning interface must support sendin g hexadecimal codes
x
77
and /or text as required by the encoder
The system must provide the capability of sending tones to
x
encoder devices that can control Fire station doors, alarms and
78
pages.
The software must support BOLOS for vehicles, including
make /model and narrative.
The software must support BOLOS for people, including attributes x
2 for sex, race, height and narrative.
The CAD -to -CAD interface must support call transfer between X
1 disparate CAD systems using the APCO /NENA standard.
Dispatchers can easily send a CFS to another CAD system from X
2 within the CAD application.
CAD -to -CAD supports mutual aid and dispatching of agency x
3 configurable "shared" units.
CAD -to -CAD supports real -time narrative updates between X
4 systems_
Interface must support requests for assistance from otherCAD I x
systems but also allow a dispatcher to approve or decline the
5 request based on agency configuration.
The application must be configurable to select specific incident
x
3
types for inclusion.
9
P O
O
4
The application must provide log in functionality.
X
Users must log into an inquiry screen that defaults values but
x
5
allows user to expand search for more information.
1
Law Enforcement Records must fully integrate with the CAD
x
Briefing notes must allow user to include incident narratives if
x
software and be provided by the some vendor. Full integration must
6
desired.
include automatic, seamless transfer of critical information between
The CAD -to -CAD interface must support call transfer between X
1 disparate CAD systems using the APCO /NENA standard.
Dispatchers can easily send a CFS to another CAD system from X
2 within the CAD application.
CAD -to -CAD supports mutual aid and dispatching of agency x
3 configurable "shared" units.
CAD -to -CAD supports real -time narrative updates between X
4 systems_
Interface must support requests for assistance from otherCAD I x
systems but also allow a dispatcher to approve or decline the
5 request based on agency configuration.
! O
9
P O
O
1
Law Enforcement Records must fully integrate with the CAD
x
software and be provided by the some vendor. Full integration must
include automatic, seamless transfer of critical information between
CAD, Mobile Computing, and LE Records. Examples include transfer
of CAD incident information to LE Records, and transfer of hazard
information associated with persons and locations to alert
dispatchers of potentially threatening situations for officers.
2
The software must have multi - jurisdictional environment capabilities.
x
3
The software must have a tabular design, allowing access to
x
multiple layers of the system from the some screen.
4
Ability for multiple users to be logged onto the system and use the
x
same applications simultaneously.
5
The software must be compliant with current Web Browser
x
standards, while adhering to UI /UX design best practices
6
All software modules must have the ability to access the some
x
master name records.
7
Authorized agency staff must be able to modify or adjust
x
commonly altered variables such as codes, tables, report
parameters, etc., without the services of a professional
programmer.
8
Standard toolbar functionality must include buttons that allow users
to do the following:
Create new records
x
Open existing records
x
Save records
x
Delete records
x
Copy records
x
Print records
X
Access online Help
x
9
The software must allow for users to open and use multiple Web
browsers or tabs.
x
10
The software must be able to associate codes to more than one
location or panel when the some validation table entries are used
in multiple locations.
x
11
The system must use consistent validation table processing.
x
12
The system must allow for agencies to define values within each
validation table.
x
13
Ability to assign alternate values to validation set values in order to
tie specific data elements to various software functions, including,
but not limited to, report generation and data matching with other
ORIs and third-party software.
x
F
All applications must integrate tightly with each other to permit the
greatest operator ands stem efficiency.
x
15
The software must provide a one -time, single -point system of data
entry that allows information to be accessed from other r
applications.
x
16
The software must provide a basis, such as a report wizard, for
preparing various statistical and analytical reports.
x
17
The software must allow users to create and store ad -hoc reports.
x
18
The software must directly output from a data search to a printer
upon user request.
x
19
The software must provide the capability to add unlimited narrative
to records, to ensure all critical information is captured.
x
20
The system administrator must be able to identify the individual who
last entered or updated any transaction as well as the date and
time of the modification.
x
21
The software must track user activity (i,e., the addition, modification,
viewing, and deletion of records) and record the following for each
incidence of such activity: user name, access type, date, time,
record key and device.
x
22
The LE records software must have the ability to run in a virtual
server environment, including both VMware and Microsoft Hyper -V.
x
23
The software must provide inquiry capability for all employees
based on profile and password security.
x
24
The software must have Incident Based Reporting (IBR) compliance
capability.
x
25
The software must be National Incident Based Reporting System
NIBRS compliant.
x
26
The base LE Records software must support:
Accidents
x
Arrests
x
Business Registry
x
Case Processing
x
Incidents
x
Computer Aided Investigation
x
Federal Reports (IBR)
x
Geo- Address Verification
x
Impounded Vehicles
x
Incident Tracking
x
Known Associates
x
Master Name Processing
x
Personnel /Training
x
Property and Evidence Tracking
x
Traffic Tickets & Citations
x
Wants and Warrants
x
27
The following optional modules must also be available:
Alarms
x
Bookings
x
Briefing Notes
x
Registered Offenders
x
Case Management
x
Demographic Profiling
x
Equipment /Inventory
x
Field Interviews
x
Gangs
x
Permits
x
Hazardous Materials
x
Narcotics
x
Orders of Protection
x
Pawn Shops
x
NCIC Interface
x
1
The software must provide component (e.g., modules, entry
screens) and report (e.g., case reports, ticket reports) security to
permit and restrict user /user group rights.
X
2
The system administrator must have the ability to set up, grant or
deny, user /user group permissions for all components, including
add, than e, delete, view /use, and execute permissions.
x
3
The system administrator must have the ability to restrict security
components by individual user or user group.
x
4
Security components cannot be changed or deleted by
unauthorized users.
x
5
The system administrator must have the ability to create and
maintain authorization templates (which are defined by name).
x
6
Authorizations must be tied to user login and corresponding
confidential password.
x
7
Passwords must never be displayed.
X
8
The system administrator must have the ability to easily create
system users.
x
9
The system administrator must have the ability to easily change
passwords.
x
10
Although the administrator can change user passwords, the actual
passwords must not be revealed to the system administrator.
X
11
User passwords must be encrypted when stored in the database.
x
12
Ability to require at least one number, symbol, and /or letter in user
passwords.
x
13
Ability to require password expiration after an administrator- defined
number of days.
x
14
Ability to define a minimum and maximum password length.
x
15
Ability to lock users out of the system after an administrator - defined
number of invalid login attempts.
x
16
Authorized users can set individual document permissions. These
permissions are governed by user roles. Permissions can only be
removed from a user role, not added. Example, if a user role did not
have access to delete documents, they cannot be added when
applying individual document permissions.
x
17
The software must provide the ability to restrict access to specific
information /features.
x
18
The software must restrict access to specific records by review level. I
X
19
The software must provide inquiry capabilities for all employees
based on profile and password security.
x
x l
1
Record numbering can be configured for system counter and/or
manual entry.
X
2
Ability to configure departmental structures as a representation of
the operational hierarchy specific to an agency.
x
3
Ability to configure the availability and display order of non - system
required sections on a module record's view.
x
4
Ability to configure the requirement, availability, and layout of non-
system required fields in a module record's view.
X
5
Ability to create user - defined fields specific to a module section
that is shared amongst all agencies and of type:
Checkbox
x
Date
x
Date /Time
X
Decimal
x
Hyperlink
x
Enumeration
X
Numeric
X
Text Area
X
Text box
x
Time
X
Validation Sets
x
6
Allow admins to optimize data entry workflow in the software
through specialized configuration of sections and fields.
X
7
Ability to configure the email server, system admin email, default
system email address, and SMTP port number for a specific agency.
x
8
Able to configure the email settings to use SSL for a specific
agency.
x
91
Allow agencies to create activity types for global records.
X
1
Ability to configure the system to enable remote system integration
X
2
Ability to configure the Date and Time format of the system.
X
3
Ability to configure the time -out duration for all record locks in the
system.
x
4
Ability to define base alert types in the system that can be inherited
and configured by each agency for their specific alert definitions.
x
5
Ability to set up and configure email groups.
x
6
Ability to configure the email server, system admin email, default
system email address, and SMTP port number for the application
system.
x
7
Able to configure the email settings to use SSL for the application
system.
x
8
Ability to create Incident groups by type that can be leveraged in
the system for reporting and search features.
x
9
Ability to configure the maximum NCIC request number.
X
10
Ability to configure the Property Room Evidence Barcode and
Inventory Number auto -start values.
x
1 1
Define reciprocal relationships between members of the Known
Associates validation set in the system.
x
12
Enter and maintain the name, description, and type (scor, mark,
tattoo) of identifying features utilized throughout the system.
X
yt V « amt- c Ai
1
The software must use the master name concept and contain all
information collected on a person or business, as well as all
associated activities, in a single master name record.
x
2
The software must provide a listing of all activities in which a person
has been involved, including those related to arrests, jail releases,
tickets, warrants, cases, incidents, accidents, gangs, vehicles and
guns.
X
3
Ability to display an image of the subject within the master name
record, whether by capturing an image with a digital camera or by
uploading an image from a camera, computer disk or any
TWAIN32- compliant imaging device.
x
4
The master name record must be accessible from the following
modules:
Accidents
x
Alarms
x
Alerts
x
Arrests
x
Bookings
x
Buildings
x
Registered Offenders
x
Case Management
x
Cases
x
Computer Aided Investigation
x
Equipment /Inventory
x
Field Interviews
x
Gangs
x
Global Vehicles
x
Permits
x
Impounded Vehicles
x
Incidents
x
Narcotics
x
Orders of Protection
x
Pawn Shops
X
Property Room
x
Tickets and Citations
x
Wants and Warrants
x
5
Ability to enter and maintain the following master name record
data elements:
Name (First, Middle, Last, Suffix)
x
Address (City, State, Zip Code)
x
Age /Race /Sex
x
Associated Names
x
Affiliation
x
Physical Description
X
Scars, Marks or Tattoos
x
Date of Birth
x
Driver's License Number
x
Driver's License Expiration Date
x
Driver's License Characteristics
x
Social Security Number
x
Personal Information
x
Handicaps
x
Inmate Number
X
Department Arrest Number
x
Mug Shot Number
x
FBI Number
x
Local Identification Number
x
State Identifier Number (SID)
x
Military Service Number
x
Identikit Number
x
Alias (Multiple Types)
x
Nickname (Street Name)
x
Place of Birth
x
Occupation
x
Home Phone
x
Work Phone
x
Cell Phone
x
Employer Name and Address
x
Fingerprint Classification Number
X
Marital Status
x
City, County, Country and Place of Birth
x
Illegal Alien
x
School
x
Religion
x
Citizenship
x
Associated ID Numbers
x
Modus Operandi /Crime Specialties
x
Known Associates
x
Contact Information
x
6
The software must eliminate the need to duplicate any information
already entered.
x
7
Once a master name record is created, authorized users must be
able to update any basic data fields and add or modify other
information as needed.
x
8
Ability to cross - reference the master name record to all other
records associated with an individual.
x
9
Ability to restrict name activity access by jurisdiction.
x
10
Ability to edit and merge duplicate master names.
x
1 1
The software must restrict access to Master Name Index to
authorized users only.
x
12
The software must store narrative associated with a name and
display it upon inquiry for that name.
x
13
The software must link multiple addresses to a master name record
and date all changes to an address.
x
14
The software must associate previous address records with a date
of address change, along with the person that changed the
address.
x
15
The software must have the ability to check all coded entries in the
master name record for validity at the time of data entry.
x
16
The software must automatically check a name against the list of
outstanding warrants and notify the user.
x
17
Users must have the ability to search for and obtain details on any
type of record associated with the individual master name record,
such as:
Arrests
x
Known Offenders
x
Known Associates
x
18
Users must have the ability to search for master name files based on
any of the following criteria:
Name
x
Social Security Number
x
Date of Birth
x
Height or Height Range
x
Weight or Weight Range
x
Hair Color
x
Eye Color
x
Physical Characteristics
X
Combination of Parameters
x
Race
x
Sex
x
Identifying Clothing
x
19
The software must treat common business names as a master name
record.
x
20
Ability to easily copy master name records, e.g., to use in other
jurisdictions.
x
21
Ability to locate subject records via Soundex (first, middle, last
name).
x
22
Ability to perform field level auditing within a master name record.
X
23
The software must capture and store data from an officer's field
report, including the associated report narrative.
x
24
The software must allow authorized users to update and maintain
incident records with new information as needed.
x
25
Ability to apply user security to incident entry, search and all
incident related reports.
x
26
Ability to enter supplemental reports.
X
27
Ability to index incident records by incident number.
X
28
Ability to enter and maintain information on any type of
incident /criminal activity.
x
29
Ability to correct previously entered incident data in the case data
entry screen.
x
30
Ability to enter and maintain the following general incident record
data elements:
Incident Type
x
Call Date /Time
X
Call Source
x
Status
x
Priority
x
Associated Case Number
X
Nature of the Call
x
Caller Name
x
Incident Location
x
Reporting District
x
31
Ability to enter and maintain multiple officer narratives,
x
32
Ability to view related special response information, as entered and
maintained in CAD.
x
33
Ability to enter and maintain associated calls, as entered and
maintained in CAD.
x
34
Ability to enter and maintain information about associated units
and personnel.
x
35
Ability to view a call and unit logs, i.e., lists of the calls and units
associated with the incident.
x
36
Ability to enter and maintain information about the vehicles
associated with the incident.
x
37
Ability to view a list of other incident numbers associated with the
incident, as entered via CAD.
x
38
Ability to enter and maintain information about all persons
associated with the incident.
X
39
Ability to enter and maintain associated dispositions.
x
40
Ability to display and view a list of other records associated with the
incident.
x
41
Ability to generate multiple incident related reports for statistical
crime analysis.
X
42
Ability to associate property with an incident.
x
43
Ability to apply user security to case entry, search and all incident
related reports.
X
44
Ability to pull data from an existing incident record.
X
45
Ability to update and maintain case records with new information
as needed.
x
46
Ability to enter supplemental reports.
x
47
Ability to index case records by case number, which may be the
same as the originating incident number.
x
48
Ability to enter and maintain case records on any type of incident
or criminal activity.
X
49
Ability to track multiple crimes within a single master case record.
x
50
Ability to cross - reference and link multiple related offenses to a
specific case record via its case number.
X
51
Ability to automatically create a case record upon entry of the
crime report data.
x
52
Option to automatically generate year -based case numbers.
x
53
Ability to correct previously entered incident data in the case data
entry screen.
X
54
Ability to enter and maintain the following case record data
elements:
Incident Type
x
Occurred Location
X
Hate Bias Information
X
Criminal Activity
X
Entry and Exit Methods /Points
x
Date /Time of Occurrence
x
Date of Reported
Occurrence
X
Multiple Crime
/Offense Codes
x
Type of Arson Reported
X
Type of Theft Reported
X
Status of the Complaint
X
Disposition /Date of the Complaint
x
Multiple MOs of the Crime
X
Attempted Crime
x
Type of Weapon
x
Type of Tool
X
Codes for the Type of Scene of the Crime
x
Officer's Assignment
x
Type of Stolen /Recovered Vehicle
X
Estimated Dollar Amount of Property Involved
x
Property Involved
x
Solvability Factors Associated with Complaint
x
55
Ability to enter and maintain detailed information about all offenses
associated with a case.
x
56
Ability to enter and maintain detailed information about all subjects
x
associated with a case, such as arrested adults, juveniles, witnesses,
complainants, missing persons, reporting party, victims, etc.
57
Ability to enter and maintain information about all arrests
x
associated with a case.
58
Ability to enter and maintain information about all property
X
associated with a case.
59
Ability to enter and maintain information about all field
x
investigations associated with a case.
60
Ability to automatically link all information from a field investigation
x
record to the original complaint report.
61
Ability to enter and maintain information about all vehicles
X
associated with a case.
62
Ability to support unlimited narrative entries, with a maximum limit of
x
100K characters, and formatting capabilities for the original
complaint and supplemental reports.
63
Ability to support unlimited narrative entries, with a maximum limit of
x
100K characters, and editing capabilities for any manually entered
supplemental report.
64
Ability to capture crime analysis related information during case
x
processing.
65
Ability to expunge a subject from a case record.
X
66
Information from an incident record is automatically pulled into an
x
associated case record to eliminate the need to enter the same
data twice.
67
Ability to print hard copies of case records and supplemental
x
reports, depending on security.
68
Ability to print a sanitized version of a case record for public use.
X
69
All entry information can be built into a report, which will plot on a
x
map or generate a printable report.
70
Ability to generate multiple case related reports for statistical crime
x
analysis.
71
Ability to attach multiple supporting documents of various types
x
(e.g., Word, Excel, JPG, MPG, WAV, etc.) to a case record.
1
Ability to enter, maintain and track all information about an
x
accident.
2
Ability to enter, maintain and track detailed information about all
x
subjects associated with an accident (e.g., drivers, passengers,
pedestrians, witnesses, etc.
3
Ability to enter, maintain and track detailed information about all
X
vehicles associated with an accident.
4
Ability to attach multiple supporting documents of various types to
x
an accident record.
5
Ability to link accident, incident and case numbers for investigative
X
and search purposes .
6
Ability to print accident report on demand.
x
�_i
¢`
3
..Y �a£�,y`,4`iimY -' °- �%;W�.Se'.� 3i�rw^+\Y.t rf.�. ,y_�� .Af4
•1h
i }.:'v
Y� r. J
1
Ability to enter and maintain the following general arrest
information:
Arrest Number
X
Date /Time of Arrest
x
Arrest Type
x
Arrest Status and Status Date /Time
x
Associated Case Number
x
Location of Arrest
X
Name of Arrested Person
x
Arresting Officer (multiple possible)
x
Arresting Officer's Assigned Bureau
X
Assisting Arrest Officer
X
Disposition of the Arrest
X
Disposition Date
x
Resulting Charge at Disposition
X
Sentencing Information
x
Bond Information
x
2
Ability to enter and maintain information about all charges
associated with the arrest.
x
3
Ability to enter and maintain data on arrest and court dispositions.
x
4
Ability to enter and maintain information about any injuries the
arrestee may have sustained while being apprehended.
x
5
Ability to enter and maintain information about any weapons
involved in the arrest.
x
6
Ability to enter and maintain information about the various
identification numbers associated with the arrest, such as a booking
number, case number, warrant number and offender -based
tracking system number.
x
7
Ability to properly report information per NIBRS requirements.
X
8
Compliance with IBR reporting.
X
9
The software must link newly arrested individuals to previous arrests,
if applicable,
x
10
If one does not already exist, the software must automatically
create a master name record at the time of the arrest processing.
X
1 1
The software must have easy access to an arrest register within a
selected date range.
X
12
An arrest record can be added at the time of the original
complaint report or at a later date.
X
13
In the event of an arrest at a later date, the software must have the
ability to add additional supplemental narrative to the original
complaint report.
x
14
The software must require additional security to access juvenile
records.
x
15
Ability to search for arrest records based on the following criteria:
Arrestee's Name
x
Arrest Date /Range
x
Complaint /Case Number
X
Arresting Officer ID
X
Arrest Tracking Number
x
16
Ability to print a variety of arrest related reports to facilitate the
statistical analysis or arrest data, including the following:
Arrest by Court Disposition Date Report
x
Arrest by Location Report
X
Arrest by Officer Report
x
Arrest Detail Report
X
Arrest Register Report
X
Arrest Status Summary Report
x
17
The software must provide equivalent reports for both juvenile and
adult arrest records.
x
1 1
Authorized users must have the ability to enter and maintain the
details of an impounded vehicle, including the following general
information:
Impound Date /Time
x
Impound Lot
x
Reason for Impounding
x
Place of Storage
x
Location Impounded From
X
Towing Service
x
Impounding Officers
x
Vehicle Information (make, model, color, etc,)
x
2
Ability to enter owner Information based on master name file
selection.
x
3
Ability to enter and maintain disposition information.
x
4
Ability to enter and maintain vehicle release information.
x
5
Ability to enter and maintain associated incident, case, arrest,
warrant, and booking information.
x
6
Ability to enter and maintain information about associated fees.
x
7
Ability to attach multiple supporting documents of Various types to
an impounded vehicle record.
X
1
Ability to create an electronic lineup based on user defined
physical characteristics and /or other pertinent information.
X
2
Ability to easily modify, reorganize and print lineups.
x
3
Ability to use any single photo of possibly multiple available photos
for a single lineup subject.
x
4
Ability to locate subjects using a single criterion or multiple criteria,
including (but not limited to) physical characteristics, charges,
scars, marks, tattoos, MO and handicaps.
x
5
Ability to use "Wild Card" Combinations, i.e., random lineups of
subjects drawn from search results.
x
6
Ability to limit searches to a single jurisdiction.
X
7
Ability to generate a crime analysis report based on user - defined
report criteria, such as, but not limited to, specific criminal activity,
offenses, M.O., entry/exit methods, evidence collected,
location /scene, hate /bias and weapon used.
x
8
Ability to search master names and businesses.
x
w
t c f if f GP. irb 'cODII3,�.g'"„
I
The software must capture crime analysis data in the complaint
report and produce specific crime analysis reports:
Date of Offense
x
Time of Offense
x
Location of Offense
x
Description of the Premises
X
Type of Offense
x
Method and Point of Entry
x
Description of Weapons Used
x
Description of Tools Used
x
Victim Data (Age /Relationship)
X
Type of Property Stolen
X
Suspect Vehicle Description
x
Suspect Description
X
Modus Operandi (M.O.) Parameters
x
Hard Copy and Map Plotting
x
2
Ability to generate all reports using a report wizard to ensure that
reports meet all requirements and are easy to build.
x
3
Ability to generate a report that shows statistical data on crimes
concerning the frequency and the distribution of crime throughout
user - selected jurisdiction reporting districts.
x
4
Ability to retrieve cases with similar crime modus operandi to assist
investigators in solving crimes.
x
5
Ability to identify the overall activity per crime type within a
selected date range and reporting district.
x
6
Ability to create reports that target specific types of crimes based
on the following:
Location (specific address) of Occurrence
x
User Selected Crime Type
x
Hate Bias Information
x
Geographical Groupings of Crimes
x
Similar Types of Victims
x
Common M.O. of Crime
x
Suspect Vehicle Description
x
Suspect Physical Description
x
Tools Used
x
Weapons Used
x
Property Targeted for Theft
x
Point and Method of Entry
x
Scene Category of Crime
x
Theft Category of Crime (i.e., shoplifting from buildings,
vehicles
x
Crime Attempts
x
7
Ability to retrieve suspect names based on:
Available photo in our system
x
Known Offender Address
x
Past Criminal Contacts
X
Past Vehicle Relations
x
Pawn Transactions
x
Weapon Registration
x
Known Associates
x
8
Ability to retrieve suspect vehicle information based upon:
Model Year of Vehicle
x
Make of Vehicle
x
Model of Vehicle
x
Style of Vehicle
x
Top and Bottom Color of Vehicle
x
License Plate of Vehicle
x
9
Ability to retain information on vehicles obtained through:
Field Interview Reports
x
Prior Contacts with the Department
x
Ability to associate impounded vehicle records with an arrest. The
impoundment is an activity tracked on the global vehicle record.
x
Complaint Reports
x
Citations /Moving Violations
x
Accident Reports
x
Want and Warrant Records
x
Suspect Vehicles Record
x
Impounded Vehicles
x
10
Ability to retain M.O. characteristics in coded fields and search for
some by selected ammeters.
x
11
Ability to generate report with M.O. parameters and crime
specialties.
X
12
Ability to retain information on known offenders, such as:
Past Criminal Contact
X
Sex Offenders
x
Narcotics Offenders
X
Parolees
x
Court Probationers
x
13
Ability to capture and retrieve juvenile information, including:
Juvenile Demographic Information
x
Juvenile Personal Characteristics
x
Juvenile Guardian Information
X
14
Ability to capture and retrieve crime analysis information from
complaint records when information is included on a juvenile arrest.
x
15
Ability to link related complaints together through capture of
associated case numbers.
x
-+. wi£.�u�}J4J...:311
...
1
The software must satisfy the physical requirements for automated
submission (tape, bulletin board or Internet) to:
Incident Based Reporting (IBR)
X
Interface to the State Police via Internet, if applicable
x
2
The software must transmit changed and updated records as well
as original records within the reported month.
x
3
The software must provide the required Incident Based Reporting
data elements in the appropriate formats.
x
4
The software must edit the monthly IBR information and identify
errors before submission (for IBR, create as you go).
x
E
1
Ability to enter and maintain detailed information about want and
warrant records, including (but not limited to) the following data
elements:
Court Warrant Number
x
Court Case Number
x
Warrant Number
x
Wanted Driver's License Number
X
Wanted Social Security Number
X
Reason for Change on Warrant
X
Issuing Judge
x
Wanted Alias(s)
X
Date of Birth
x
Charges
x
Bond Amount
x
Vehicle Make /Model /Color
x
Vehicle License Plate /State /Year
x
Disposition
x
Status History
x
Activity
x
2
Ability to display an image of the subject within the master name
record, whether captured by directly connected digital camera or
by if uploaded from local workstation or any connected media.
x
3
Ability to display an alert whenever the name of a subject with an
outstanding warrant is entered anywhere in the system.
x
4
Authorized users must be able to update the status of a warrant
record whenever necessary.
x
5
Ability to assign warrant transaction numbers manually or
automatically via an optional auto - incrementing feature.
x
6
Ability to generate a printed report displaying a log of all warrants
within a specified date range.
x
7
Authorized users have the ability to cancel outstanding warrant
records. Authorization is based on user security profiles (ID,
password, security permissions).
x
8
Ability to cancel outstanding warrants for the following reasons:
Recalled by Court
x
Served on the Person
x
Cleared of the Charge
x
Beyond Statutory Limits
x
9
Ability to maintain records on canceled warrants for an unlimited
amount of time.
x
10
In CAD, warrants are automatically searched based on the entry of
matching name and /or matching address. A match on either of
these search criteria will display a warning message for the user.
x
1 1
Ability to generate a printed report that lists all canceled warrants
within a specified date range.
x
12
Ability to generate a printed warrant summary report that lists all
warrant types and totals within a specified date range.
x
1
Ability to enter and maintain all information pertaining to traffic
tickets and citations:
Ticket Book Distribution
x
Statistical Information by Department
x
Statistical Information by Officer
x
Ticket Deletions
x
Status Changes
x
2
Ability to maintain a history on each traffic ticket and citation
produced, including (but not limited to) the following information:
Name
x
Violation
x
Personal Information
x
License Plate Number
x
Vehicle Make and Model
x
Vehicle Color
x
Location
x
Date /Time Stamped
x
Statute /Ticket Type
x
Court and Disposition Data
x
Weather and Traffic Conditions
x
3
Authorized personnel must have the ability to void /delete tickets.
x
4
Ability to support multiple violations under a single ticket number.
x
5
Ability to quickly search and access ticket /citation information using
name, location, geographic area, officer and ticket type as search
criteria.
x
6
Ability to track multiple subjects involved /associated with the ticket
(example Witness, Juvenile Guardian, Passengers).
x
7
Provide integration with form -based Brazos eTicketing solution.
x
8
Ability to track and synchronize the following data with the Brazos
eficketing software:
Statutes
x
Personnel Info
x
Cities (Venue) I
x
Counties
X
Court rooms
x
Ethnicity
x
Eye color
X
Hair color
X
Phone Type
x
Race
x
Sex
x
State
x
Ticket Types
X
Traffic Conditions
x
Vehicle Colors
x
Vehicle Makes
x
Vehicle Styles
x
Vehicle Types
x
Court Docket Number
X
-fx
1
Ability to enter and maintain detailed information on all businesses
located within a given jurisdiction.
x
2
Ability to track the following information on businesses:
Business Name, Address, Phone
X
License Type
x
Hours of Operation
x
Owner's Information
x
Hazards
x
Basic Floor Plans
X
Prior Addresses
x
Contact Information
x
3
Ability to search for business records based on business name,
building name, building number, district, zone, class and sub - class.
x
4
Ability to easily access the fire pre -plan associated with a given
business, should one exist.
X
5
Ability to generate a Pre -plan report for the Business
x
61
Ability to customize the pre -plan report for each ORI
x
s
+ 1c
1
Ability to enter and maintain detailed information on all
buildings/structures located within a jurisdiction.
x
2
Ability to track the following information for Buildings
Building Name, address, phone
x
Contacts including address and phone numbers
x
Structure Details including structure floor size, stories,
elevators
x
Fire Flow calculations based off of NFPA guidelines
x
Key Response Details such as knox box codes, gate
codes or utility shutoff locations
x
Hazardous Materials on site
x
Tanks including both above and below ground
x
Protection Systems including Fire Alarms
x
Sprinkler systems and locations
x
Auto Extinguishment Systems and locations
x
Fire Pumps and Hose Cabinets
x
3
Ability to search for building records based on building name,
building number, address
x
4
Ability to easily access the fire preplan associated with a given
building
X
5
Ability to generate a Pre-plan report for the building
6
Ability to customize the pre-plan report for each ORI
I
Ability to display an image of the subject within the record, whether
captured by directly connected digital camera or by if uploaded
from local workstation or any connected media.
x
2
Ability to enter and maintain the following general personnel
information on every employee:
x
Employee Full Name
x
Employee Address
x
Employee Badge and/or ID Number
x
Social Security Number
x
Home Phone Number
x
Department Number and Extension
x
Date of Birth
x
Place of Birth
x
Citizenship
x
Current Rank
x
Rank History
x
Hire Date
x
Termination Date
x
Education (Job-specific skills and certifications)
x
Special Skills
x
Emergency Notification Information
x
Employee Status or Promotions
x
Reprimands and Commendations (associating the
Personnel record to the relevant documentation in file
storage)
x
Spouse's Name
x
Driver's License Number
x
Employee Demographic Information
x
Contact Information
x
3
Ability to enter and maintain information about an employee's
current assignment, as well as maintain a history of assignments.
x
4
Ability to track information about the equipment issued to each
employee, including the following:
x
Item Type
x
Quantity
x
Inventory Number
x
Date Issued
x
Condition of Item
x
Returned Date
x
Condition Returned
x
5
Ability to enter and maintain information about an employee's
education and training, including, but not limited to, the following:
x
Courses (e.g., Firearms Training, Hazmat Technician Training, etc.)
x
Programs
x
Certifications
x
Basic Academy Training
x
Military Training
x
College Classes
X
6
Ability to maintain the following training-related data elements:
x
Employee ID Number
x
Training Course Title
x
Training Location
x
Re- certification Date
x
Length of the Course
x
Course Completion Date
x
Course Comments
x
Credit Hours
x
7
Ability to enter and maintain information about any special skills an
employee may have, including, but not limited to:
x
Foreign Language
x
Public Relations Training
x
Bomb Disposal Training
x
First Aid Training
x
SWAT Training
x
Breathalyzer Training
x
8
Ability to view summary information for all employees and all
training conducted within a date range.
x
9
Ability to view summary information of all training received by an
employee during employment.
x
10 Ability to display an image of the subject within the record, whether x
captured by directly connected digital camera or by if uploaded
from local workstation or any connected media.
MM
1
Ability to enter and maintain the following property data:
x
Item Number
x
Piece Number
x
Serial Number
x
Property Code (e.g., stolen, pawned, evidence)
x
Property Tag Number
x
Owner Applied Number
x
Storage Location
x
Quantity
x
Value — Nearest Dollar
x
Property Owner (one or more)
x
Date Property Received
x
Item Category (e.g., currency, gun, drugs, tools, etc.)
x
Lab Report Information
x
Date of Disposal /Release
x
Target Disposal Date
x
Item Class
x
Free -form Descriptions
x
Color
x
2
Ability to enter and maintain the following additional elements for
firearms:
x
Gun Type
x
Action (automatic, bolt action, carbine, pump)
x
Caliber
x
Shot Capacity
x
Barrel Length
x
Finish
x
Make /Model
x
Type of Firearm
x
Condition j
x
Year Made I
x
3
Ability to enter and maintain the following additional elements for
boats:
x
Boat Name
x
Hull Shape
x
Hull Material
x
Propulsion
x
Boat Length
x
4
Ability to enter and maintain the following additional elements for
vehicles:
x
Vehicle Type
x
Color (primary, secondary, interior)
x
Make /Model
X
License Plate /VIN
x
Plate Year
x
5
Ability to tie a property item to a case.
x
6
Ability to maintain complete evidence tracking audit trail until final
disposition of the property item.
x
7
Ability to maintain details of all evidence retained in the property
room for an indefinite amount of time
x
8
Ability to maintain a status value for all evidence items after each
item has been released.
x
9
Ability to track items from receipt to disposal.
X
10
Ability to maintain lab reports on fingerprint tests,
x
1 1
Ability to enter and maintain information about the individual or
organization to which the property was released.
x
12
Ability to print an evidence inventory report by case number.
x
13
Ability to print a disposal /release report for all items when disposed.
x
14
Ability to generate a list of property /evidence by Target Disposal
Date with user - defined date range).
x
15
Ability to generate a list of all items of property /evidence by case or
incident.
x
16
Ability to restrict inquiry access to property /evidence records by
individual user and permission.
x
17
The module must allow users to search for property based on the
following search criteria:
x
Serial Number
x
Owner's Name
x
Tag Number
x
Case Number
x
Make /Model
x
Property Type
x
Property Class
x
Storage Location
x
18
Ability to print barcodes for the following:
x
Originating Agency Identification (ORI)
x
Officer
x
Status
x
Chain of Custody (Intake /Release) value
x
Locations
x
19
Ability to print location labels by specific location or all for a specific
facility.
x
20
Ability to set agency- defined label height and width.
x
21
Ability to print labels individually.
x
22
Ability to automatically generate tag numbers for
property/evidence items.
x
23
Ability to perform property room inventory using barcode scanning.
x
24
Supports bar code scanning.
x
25
Ability to locate and access property items based on information
x
obtained from scanned property bar codes.
26
Ability to generate a randomized list of items for use with periodic
X
audit requirements
27
Ability to update multiple records at the some time based on
x
barcode scan
28
Ability to check in multiple records to property room at the some
x
time
29
Ability to reject items back to officer to correct /update before
X
checking in
30
Ability to dispose of multiple items at once (e.g., by case /incident,
X
Target Disposal Date, etc.)
1�
Document management available in all record modules
x
2
Upload attachments through file selection or drag and drop
X
3
Attach multiple files simultaneously via file selection or drag and
X
drop
4
Document permissions are role based and govern who has access
x
to document functions
5
Ability to set permissions on individual documents
x
6
Supported file types: bmp, jpg, jpeg, gif, html, png, tit, tiff, doc,
x
docx, pdf, txt, wav, xls, xlsx, xml, zip
7
Redaction is available on documents saved in an image format
x
PDF,' e , tiff, pn )
8
Ability to manually redact selected information in a document.
x
.9
Ability to manually redact information from files prior to printing a
x
public copy.
10
Ability to include agency- defined language in a redacted
X
document
11
Ability to save a copy of the redacted report.
x
12
Ability for redaction to include the metadata that is associated with
x
the redacted fields.
13
Ability to manually redact information prior to generating a public
x
copy.
14
Ability to manually redact designated fields prior to generating a
x
public copy.
15
Ability to generate a full version of the document without
X
redactions for output.
16
Ability to maintain multiple redacted versions of the some original
x
document (e.g., insurance version, DHS version, public version).
17
Ability to identify whether an electronic file has been altered by a
x
System User.
18
Permissions govern who has access to perform and see - through
x
redactions
19
Online view of documents / images available
x
20
Ability to download documents
X
21
Ability to view documents in read only mode
X
22
Ability to seal documents
X
23
Ability to create and edit PDF, Word, Text and PowerPoint Files
x
through the document module
1
For the available modules, the software shall include set of pre-
x
defined standard reports
2
Ability to search for reports from a central location
X
3
Ability to assign specific permissions for every report
x
0
4
Ability to mark reports as favorite for easy access
x
5
Ability to use pre- defined filters to easily find reports (keyword
x
2
search, module name, report name, etc.)
x
6
Ability to preview the report and print a paper copy of the report
x
7
Ability to add custom watermarks to the report
x
8
Ability to add Agency specific logo to the report
x
9
Ability to customize Report Title and subtitle
x
10
Ability to set a daily, weekly, monthly, or yearly recurrence to
x
schedule report
11
Ability to electronically transfer reports to specific personnel or a
x
group of personnel
12
Ability to download any report in PDF or Excel format
x
13
Ability to attach documents to a detail report and print the report
x
7
with the selected documents
x
14
Ability to customize a detail report for difference audiences, such as
x
9
public view, prosecutor requests, court proceedings, FOIA requests,
x
etc.
15
Ability to inactive a report not used by the Agency
x
0
1
The module must be fully integrated with some vendor CAD and LE
x
Records to eliminate redundant data entry.
2
Ability to track and maintain a complete history of and up -to -date
x
log about each inmate.
3
Ability to enter, maintain and track all details about a
x
booking /incarceration.
4
Ability to display an image of the subject within the record, whether
x
captured by directly connected digital camera or by if uploaded
from local workstation or any connected media.
5
From the Bookings module, authorized users must have access to
x
information, such as arrest details, prior records, and warrants.
6
Ability to enter and maintain the names of the individuals who
x
brought the subject in, as well as their associated agency.
7
Ability to record and maintain unlimited booking related events.
x
8
Ability to enter and maintain unlimited number of charges.
x
9
Ability to house an inmate in location based on a pre- defined list of
x
jail locations.
10
When housing an inmate, user is alerted if co- defendants or known
x
associates are housed together.
11
Ability to maintain and track the name of the individual who
X
received the offender's personal possessions on booking and the
location of their storage.
12
Ability to print receipts for possessions.
x
13
Ability to attach associated documents to the booking record.
x
14
When creating a new record, the module must automatically
x
check the database for an existing record to eliminate duplicates.
15
Ability to track an inmate's booking history.
x
16
Ability to create agency defined forms with any of the booking
x
1
Ability to search records and global items x
= 3
1
information included.
x
17
Ability to create a booking from on arrest record that is in the
x
x
3
system.
x
x
18
Ability to create a booking from an arrest report that has been
x
x
5
started by an officer in the field.
x
x
ME
6
,., . n,e ,�. .-qua ,- .., V .,.., z.. � .v . - ✓-. ....:r. .. ..S J i� 'CV
f
1
Ability to search records and global items x
= 3
1
Ability to maintain a database of current cases and statuses.
x
2
Ability to use the module as a supervisory tool.
X
x
3
Ability to assign or reassign officers to cases,
x
x
4
Ability to assign case activities to officers,
x
x
5
Ability to enter and maintain solvability factors.
x
x
6
Ability to view status history.
x
x
7
Ability to view disposition history.
x
x
8
Ability to generate numerous breakdown statistical reports.
x
x
9
Ability to track assigned and unassigned cases.
x
x
10
Ability to track cases by case status.
x
x
1 1
Ability to track cases by officer, activity type and activity owner.
x
x
12
Ability to track cases by agency defined departmental
structures /hierarchies.
x
13
Ability to enable automatic email notifications to appropriate
personnel whenever a case is updated, or a report is added to a
case, through subscriptions.
x
14
When information is entered into the module, it must be
automatically updated in the master name file in LE Records.
x
15
Create Arrest from Case
x
16
Ability for an officer to maintain email and in -app notifications for
assignments and activities.
x
17
Ability for multiple officers assigned to the some case to collaborate
and share notes within the system.
x
ME
6
,., . n,e ,�. .-qua ,- .., V .,.., z.. � .v . - ✓-. ....:r. .. ..S J i� 'CV
f
1
Ability to search records and global items x
= 3
l
2
Ability to createWork Queues based on (Event Types):
Arrest Recently Merged
x
Arrest Reports to Review
x
Career Criminal Upcoming Registrations
x
Career Criminal Home Visits Due
x
Career Criminal Homeless Check -ins
x
Career Criminal Overdue Registrations
x
Case Recently Merged
x
Case Reports to Review
x
Crash Reports to Review
x
Field Interview Reports to Review
x
The module must automate the reporting process using a report x
W that guides users through the steps of generating reports.
2 Authorized users must be able to run a query on nearly every field in X
the LE Records software to generate reports.
3 The Management Reports must track statistical, operational, x
investigative, management and administrative data.
4 1 The module must be fully integrated with LE Records and all optional ) x
5 Once data is extracted from a query, the user must be able to: x
Save and edit the query of a later date x
Export to one of the supported formats (Excel, PDF) x
Plot data on a map x
Generate and print the final report x
6 Users can only query data they are authorized to view within the x
module must allow users to customize the following report I x
Titles and Subtitles I x --r�
Incident Reports to Review
x
Unmatched Alarm Transactions
X
Warrant Expiration
x
3
Ability to access specific tasks for each Event Type
x
4
Ability to create a Web Viewer Tile
x
5
Ability to create a Chart Tile
x
6
Ability to create a Map Tile
x
7
Ability to create a Saved Search Notifications Tile
x
8
Ability to create a Saved Search Tile
x
9
Ability to create Work Queue Task Cards
x
10
Ability to create KPIs based on a defined goal /limit
x
11
Ability to create KPIs based on a floor /ceiling
x
12
Ability to set KPI goals based on a value
x
13
Ability to set KPI goals based on a comparison
x
14
Ability to set multiple KPI target values
x
15
Ability to configure target color /icon
x
16
Ability to modify the display value of the KPI result
x
17
Ability to create multiple dashboards per user
x
18
Ability to create multiple dashboard objects per dashboard
x
19
Ability to reorganize dashboard layout
x
20
Ability to represent the same data in multiple formats
X
>, .;Sr
-� 13 ra4 LiEi yox y
21 Ability to create Saved Search Notifications
x
22 Export Map as Image
X
23 Export Chart as Image
X
The module must automate the reporting process using a report x
W that guides users through the steps of generating reports.
2 Authorized users must be able to run a query on nearly every field in X
the LE Records software to generate reports.
3 The Management Reports must track statistical, operational, x
investigative, management and administrative data.
4 1 The module must be fully integrated with LE Records and all optional ) x
5 Once data is extracted from a query, the user must be able to: x
Save and edit the query of a later date x
Export to one of the supported formats (Excel, PDF) x
Plot data on a map x
Generate and print the final report x
6 Users can only query data they are authorized to view within the x
module must allow users to customize the following report I x
Titles and Subtitles I x --r�
Graphics (e.g., agency logo)
x
8
The module must support electronic transfer of reports to
management officials.
x
9
The software must support pin- mapping and plot incidents on a map
to show:
x
Incidents near specific businesses, such as liquor stores
x
Incidents near specific schools
x
Incidents by type
x
Incidents by date /time
x
10
The software must provide an agency- defined list of topics located
in the drop -down menus, including:
x
Incidents
x
Cases
x
Offenses
x
Arrests
x
Warrants
x
Tickets /Citations
x
Jackets
x
Property
x
Case Subjects
x
Field Investigations
x
Use of Force
x
Training
x
Buildings
x
Hydrants
x
Training (Program, Course, Class)
x
Intelligence
x
Personnel
x
Evidence
x
Pawn Transaction
x
Alarm Invoice
x
Equipment
x
Gun Permit
x
Order of Protection
x
Registered Offender
x
11
The wizard must allow users to specify information such as, but not
limited to, the following:
x
Date and Date Ranges
x
Time and Time Ranges
x
ORIs
x
Address and Address Ranges
x
Types
x
Maps
x
Specific Beats
x
12
Ability to name and save a query, and quickly access a saved query
at a later date.
x
13
Users can only query data they are authorized to view within the
system.
x
14
Ability to display detailed information about an incident, accident,
etc., on mouse -over of each map icon.
x
15 1
Ability to zoom and pan.
x
16
Ability to apply multiple and various layers for more details.
x
17
The module must have a hot spot map to show high crime areas.
X
18
Ability to export data into spreadsheets for users to create high
quality meaningful reports
x
2
Ability to create and maintain agency- defined equipment
categories.
19
The module must be able to map crime trends by M.O., location,
subject or weapon.
x
3
Ability to create and maintain agency- defined equipment types.
20
Ability to add agency logo
X
4
Ability to define equipment type by equipment category.
21
Ability to set a daily, weekly, monthly, or yearly recurrence to
schedule report
x
5
Ability to track and assign equipment by:
22
Ability to electronically transfer reports to specific personnel or a
Qroup of personnel
x
Personnel
23
Ability to download any report in PDF or Excel format
X
Storage Location
24
Ability to assign specific permissions on who can create, configure
and execute the ad hoc queries
X
Unit
1
Ability to enter and maintain detailed records on all department
equipment.
MM
x
2
Ability to create and maintain agency- defined equipment
categories.
x
3
Ability to create and maintain agency- defined equipment types.
x
4
Ability to define equipment type by equipment category.
x
5
Ability to track and assign equipment by:
x
Personnel
x
Storage Location
x
Unit
x
6
Ability to capture equipment issued and return dates.
x
7
Ability to capture equipment condition when assigned to
personnel.
x
8
Ability to capture equipment condition when returned.
X
9
Ability to capture the name of the officer who issued the
equipment.
x
10
Ability to capture equipment purchase information, such as
purchase date, the name of the individual from whom an
equipment item was purchased, P.O. number, and retail and
original cost.
x
1 1
Ability to schedule replacement date.
X
12
Ability to update personnel record with issued equipment.
x
13
Ability to search all department equipment from CAD.
x
14
Ability to schedule equipment for department- specific
maintenance.
x
15
Ability to associate with department- specific inventory number.
x
16
Ability to capture and report by equipment serial number.
x
17
Ability to create and maintain department- specific equipment
activities maintenance).
x
18
Ability to enter and schedule department- specific equipment-
related activities.
x
19
Ability to track complete equipment history.
x
20
Ability to attach multiple and various supporting documents to
equipment records.
X
21
Ability to receive in app notifications of assigned activities or
maintenance forequipment
x
22
Ability to receive in app notifications when activities or
maintenance for equipment is overdue
x
M
I
. - '' -
The module must provide immediate access to all information
about field interviews.
MM
x
2
Ability to associate an interview to one or more cases.
x
Ability to associate an interview to multiple record types, including
Incidents, Arrests, and Intelligence records.
x
3
Ability to enter and maintain the following basic contact
information:
x
Contact date /time
x
Contact type
X
Contact reason
x
Location
x
4
Ability to enter and maintain information sources (e.g., rumors,
anonymous tips, confidential informants and first -hand accounts
from a law enforcement officer).
x
5
Ability to grade the credibility of each source (e.g., reliable,
unreliable, unknown, etc.).
x
6
Ability to associate an interview with a specific agency
department.
x
7
Ability to identify a contact by master name or by associated case
subject.
x
8
Ability to enter and maintain contact vehicle information.
x
9
Ability to enter and maintain all officers associated with the
interview.
x
10
Ability to attach multiple documents of various types to an interview
record.
x
11
Ability to enter formatted Comments on the interview.
x
12
Ability to enter one or multiple log entries tracking information
about the interview
x
13
Ability to enter officer written formatted narratives describing the
interview
x
14
Ability to track interviews entered in the field by officers
x
15
Full field level auditing of views, additions, deletions, and changes
within the interview.
x
16
Ability to track field interviews by:
X
Contact type
X
Contact reason
x
Date /time range
x
Field interview number
x
Investigating officer
x
Contact name
x
Partial text contained in narratives
x
Location
x
1 Ability to build a digital lineup based on a wide variety of subject x
criteria.
2 Ability to view all photos associated with a single subject and x
choose one for inclusion in a lineup.
3 Ability to automatically display a minimum of six photos x
simultaneously that meet the criteria specified.
4
Ability to quickly and easily add a photo to a lineup.
X
5
Ability to quickly and easily remove a photo from a lineup.
X
Ability to automatically generate system -wide alerts when a
defendant is defined, and the order record saved.
x
6
Ability to quickly and easily organize photos in a lineup.
x
Ability to track the following basic order of protection details:
7
Ability to generate a lineup of subjects randomly selected from the
search results of matching subjects.
x
Issued date
X
8
Ability to print a lineup.
X
Expiration date
X
9
Ability to quickly and easily view statistics on a subject within the
lineup.
x
Number of subjects served
x
1
Ability to create, maintain and track orders of protection records.
x
2
Ability to automatically generate system -wide alerts when a
defendant is defined, and the order record saved.
x
3
Ability to track the following basic order of protection details:
Issued date
X
Expiration date
X
Number of subjects served
x
Number of subjects not served
x
Court date
X
Status
x
Type
x
4
Ability to create and maintain information on all subjects
associated with an order, including each subject's role and
relationship to the complainant or petitioner.
x
5
Ability to access the department history of all involved parties from
the master name index.
X
6
Ability to enter and maintain information about all the locations
from which defendants are restricted.
x
7
Ability to enter and maintain the terms of orders of protection.
x
8
Ability to enter and maintain information about the cancellation of
orders of protection.
X
9
Ability to enter and maintain information about all activities
associated with an order,
x
10
Ability to enter and maintain information about court ordered
remedies.
X
11
Ability to generate NCIC queries and display query responses.
x
12
Ability to generate department- specific reports on any captured
table /data field.
x
1 I Supports communication between the booking module and third-
2 Supports communication between the arrest module and third- x
party Livescan software.
3 Supports communication between the person module and third- x
party Livescan software.
4 Supports Identix, CrossMatch, Printrok, Sagem Morpho and Cogent. x
5 Ability to utilize interoperability to facilitate the sharing of data x
between Bookings and third -party applications.
6
Ability to determine which booking and master file name data
x
elements are exported from the booking, arrest or person record to
1
The interface must support two -way communication between the
x
the Livescan software.
application suite and the National Crime Information Center
7 1
Ability to start and stop the interface.
x
(NCIC), as well as local and state systems.
0
OW
1
The interface must support two -way communication between the
x
application suite and the National Crime Information Center
(NCIC), as well as local and state systems.
2
Ability to authorize individual clients or workstations to access the
x
State /NCIC application based on IP address or device name.
3
Ability to direct a single query to the state /NCIC.
x
4
Ability to create user - designed format screens.
x
5
Ability to specify the maximum number of requests your agency
x
can send to the NCIC.
6
Ability to log all transactions in a history file for viewing and reporting
X
purposes.
7
Ability to search for state /NCIC responses by date /date range.
X
8
Ability to print messages received via a state /NCIC
x
re Lest /response.
9
Ability to edit the string of data that is sent to the local, state, or
x
NCIC system.
10
The interface must provide or support an online interface from the
X
CAD application to the State /NCIC database.
11
Ability to link form the CAD software to the State /NCIC network to
X
run license plate and warrant checks.
12
Ability to link from the CAD to the State /NCIC network to
X
automatically attach a CAD inquiry to the incident /call database.
13
Ability to access NCIC forms within CAD.
X
14
Ability to access NCIC history within CAD,
x
15
Ability to set up the automatic transmission of license plate or driver
x
license information based on CFS type.
16
All automatic transmissions that are attached to a CFS must be
X
logged on the call and easily accessed.
17
All responses that can be matched to the original transmission and
x
are attached to a CFS will be logged on the call in the same area
as the transmissions.
18
Application must support encryption up to AES 256 for state /NCIC
x
traffic on the LAN and FIPS 140 -2 for wireless state /NCIC traffic.
Ability to create and maintain records on all the training courses for X
which fire personnel can register.
Ability to enter and maintain the following basic information for each
course:
Course Title I x
Instruction Method
Recertification Period
Recertification Units
x
3
Ability to enter and maintain course information regarding hours and
default provider, including the following:
Duration
x
Units
x
Number of Days
x
Credit Hours
x
Additional Hours
x
Length of Service Award Programs ( LOSAP) Category Type
x
LOSAP Category
x
LOSAP Points
x
Default Provider Name, Address and Phone
x
4
Ability to view course history and the scheduling of a given course,
including the following information:
Course Title
x
Category
x
Start Date /Time
x
End Date /Time
x
Provider
x
Address
x
Location
x
Phone Number
x
5
Ability to create and maintain course objectives.
x
6
Ability to attach multiple supporting documents of various types to
each course record.
x
7
Ability to search for existing course records based on the following
user - defined search criteria:
Course Code
x
Title
x
Category
x
Active /Inactive /All
x
Program
x
8
Ability to create, maintain and track class records, i.e., schedules for
individual courses.
x
9
Ability to enter and maintain the following basic information for each
class record:
Start Date /Time
x
End Date /Time
x
Provider
x
Course
x
Class Location
x
Address
x
Phone Number
x
Days of the Week
x
Class Format (Instruction Method)
x
Training Type
x
Level of Training
x
Remarks (free -form narrative)
x
10
Ability to indicate all subjects associated with the scheduled course,
including instructor and attendees. (classes)
x
11
Ability to select class attendees by entering individual personnel
x
3
subjects, linking to master name files, entering names in free -form
x
4
narrative. Personnel can be added in a type ahead multi - select
x
5
field.
x
12
Ability to enter and maintain information about the registered
x
attendees' course results (grade /score), see at- a- glance all of the
x
objectives associated with a current scheduled course, and track
x
which objectives have been completed by which attendees.
x
13
Ability to attach multiple supporting documents of various types to
x
each scheduled course record.
x
14
Ability to search for existing class records based on the following user -
x
defined search criteria:
x
Class Code
x
Class Title
x
Provider
x
Location
X
Program
x
Class Start Date /Time Range
X
15
Ability to create, maintain and track training program records.
x
16
Ability to associate multiple required courses with a training program.
X
17
Ability to associate personnel with a training program by selecting
x
individual personnel subjects. Personnel can be added in a type
ahead multi - select field.
Ability to apply user security to Use of Force entry, search and all Use I X
of Force related reports.
2
The software must allow authorized users to search, update and
maintain information within a Use of Force record as needed
x
3
Ability to associate a Use of Force record to an Incident record
x
4
Ability to associate a Use of Force record to a Case record
x
5
Ability to view the following Case data on the Use of Force record:
x
Case Number
x
Case Offenses
x
Case Subjects
x
6 1 Ability to correct previously entered incident data in the case data I x
7
Ability to enter and maintain the following general incident record
data elements:
Use of Force Type
x
Contact Date /Time
x
Result
x
Status and Status Date
x
Reason for Initial Contact
x
Location
X
Officer approached subject
x
Ambush Incident
x
Supervisor Consulted
x
Location Type
x
Light Condition
x
Number of Officer Involved
x
8
Ability to enter and maintain all subjects associated with the Use of
Force
x
9
Ability to enter and maintain Injury information for each subject
associated with the Use of Force
x
10
Ability to enter and maintain officer information (including Name
and Demographic information) associated with the Use of Force
x
Able to support multi - jurisdictional and multi - discipline (law
x
11
Ability to enter and maintain related subjects to each officer
x
enforcement, fire, EMS) environments.
12
Ability to enter and maintain officer LEOKA information
x
Must support configuration of the main toolbar and workspace by
x
13
Ability to view history of status changes on the Use of Force record
x
discipline.
14
Ability to enter and maintain Assisting Agencies on the Use of Force
event
x
Must support State /NLETS /NCIC inquiry transactions.
x
15
Ability to display and view a list of other records associated with the
Use of Force
x
Mobile should support a dynamic (real -time) unit status monitor
x
16
Ability to enter additional comments and events related to the Use of
Force
x
that can be configured by the user.
17
Ability to add multiple documents related to a Use of Force
x
The mobile client should have utilities for changing unit
x
18
Ability to search for specific Use of Force record using any of the
following fields:
x
information, audible alerts, and GPS status.
Use of Force Number
x
The mobile system must have an emergency button. Once
x
Use of Force Type
x
pressed, the message should go out to all Mobile users and CAD.
Status
x
The message should include the unit number, last known location
Contact Date /Time
x
(if no AVL), or current location (with AVL).
Subject Name
x
The software should support remote administration via a browser-
x
Officer Name
x
based portal.
Location
x
Location Type
x
Reason for Initial Contact
x
19
Ability to view and print a detail Use of Force report
x
20
Ability to customize the standard report by OR]
x
21
Ability to Lock a Use of Force and allow specific personnel to access
the locked Use of Force
x
22
Ability for the software to build and submit Use of Force data to the
state
x
23
Ability for the officer to capture Use of Force information in the field
x
Able to support multi - jurisdictional and multi - discipline (law
x
1
enforcement, fire, EMS) environments.
Must support configuration of the main toolbar and workspace by
x
2
discipline.
3
Must support State /NLETS /NCIC inquiry transactions.
x
Mobile should support a dynamic (real -time) unit status monitor
x
4
that can be configured by the user.
The mobile client should have utilities for changing unit
x
5
information, audible alerts, and GPS status.
The mobile system must have an emergency button. Once
x
pressed, the message should go out to all Mobile users and CAD.
The message should include the unit number, last known location
6
(if no AVL), or current location (with AVL).
The software should support remote administration via a browser-
x
7
based portal.
Should provide the capability to direct output to a local or
X
8
network printer.
9
Should limit the Call Types officer can initiate from the field.
X
Should have ability to save user settings on the mobile server
X
10
(roaming profiles).
11
Windows 8.1
X
12
Windows 10
x
13
Must support touch screen, hot keys and mouse input.
x
14
Mobile client must have night mode for all features.
X
Must have the ability to update Mobile clients remotely. The
x
updates should include but not limited to mobile software, map
15
data, pre-plans, building diagrams and any field reporting data.
Administrator should be able to see which units have received
X
16
and installed the updates successfully.
Mobile must have the capability to run either Low Enforcement or
x
Fire mobile on the same client (public safety agencies) without
any configuration required on the user's part. The user needs only
17
to close one application to start the other.
18
Allow more than one user to be assigned to one Mobile unit.
x
The Mobile software should have a visual indicator showing the
x
19
client's connection status.
Should provide emergency transmission support to all MDTs/MCTs
x
20
and CAD dispatchers for the jurisdiction.
Administrator should be able to configure the layout of the
X
assigned call for service form that an officer uses to view CFS
21
information
Assigned call for service form layouts can be configured
x
22
separately for each agency.
Assigned call for service form should display unit's assigned
X
23
location when it differs from the call for service location.
24
Should allow an MDT/MCT to add narrative to a CFS.
X
Should provide for the entry of text information that goes directly
x
to the narrative of a call whether or not the call is active or
25
cleared.
26
Should allow the user to mark a narrative entry as critical.
X
Should display critical narrative in a way the alerts the user about
x
27
the importance of the text.
Should support the use of hyperlinks in narrative entries to allow
x
28
the user to drill down into additional information.
Should provide message routing between Mobile Data Terminal
X
(MDTs) and CAD for the purposes of assisting dispatching,
updating unit status, and database inquiry provided appropriate
29
CAD interfaces are licensed.
Should provide emergency button that transmits to CAD and
X
30
other mobile units.
Should provide the ability to initiate "quick calls" from the mobile
x
devices which alert the dispatch center of an event, officer
location, license plate number, unusual circumstances and/or
31
other added narrative.
Should support voiceless dispatch for law enforcement, fire and
X
32
EMS personnel.
33
Should provide information on open incidents by ORI status.
x
34
Should provide information on unit status by OR[ display.
X
Should provide information on all units associated with an
x
35
incident.
Should provide sign -on /sign -off dispatch, en- route, at scene,
x
36
clear, to hospital, at hospital functions from MDT /MCT to CAD.
Users should be able to view Active or Pending calls and be able
x
37
to dispatch self to selected call (based on permissions).
Should have a unit monitor to view all statuses, location and any
x
38
changes in real time.
Should have standard filters and the ability to create custom filters
x
39
for the unit monitor.
40
Notify user with audible new message alert.
x
41
Mobile shall be completely integrated with CAD and LE Records.
x
CAD must have the capability to automatically send and receive
x
incident information to and from mobile clients. Must support
42
silent dispatching.
43
Mobile must support Unit Log inquiries.
x
Mobile must have the ability to automatically prompt the officer
x
44
for demographic profiling information after clearing a traffic stop.
Must have available the ability to change the unit status to one of
x
45
the next available statuses.
The Mobile Unit Status Monitor and mobile map should update
x
46
dynamically in real -time.
The Mobile client must be able to receive supplemental dispatch
x
information in real -time. This includes updates from CAD or other
mobile units (i.e., updates to incident, additional information on
47
persons, vehicle information, narratives, etc.).
Mobile client must have the capability of displaying pre - plans,
x
building diagrams, photos or any other media file associated with
48
a location.
Mobile users should be able to query both CAD calls and agency
x
49
incidents.
50
Should provide search functionality over unit log information.
x
System should allow agency- defined questionnaires that can be
x
used for various activities, including start of shift or with specific
51
field situations.
a
Should provide security that prevents unauthorized access
x
52
application functionality.
Should provide sign on /sign off capability from the mobile
x
computer to include a configurable time period to force
53
reauthentication.
Should prevent users from signing on without authorization from
x
54
the system administrator.
Should provide password security to limit access to specific
x
55
transactions from any MDT.
56
Should support multiple security templates for different roles.
x
57
Security and encryption must be FIPS 140 -2 compliant.
x
58
Should allow Administrator to set password rules.
x
The administrator should be able to set password length, special
x
characters, numbers, uppercase, duration, disallow previous used
passwords (i.e., cannot change password to the current
password and time period to be able to use that password
59
again).
The administrator should be able to set password rules to conform
x
with the Criminal Justice Information Services (CJIS) Security
60
Policy.
The administrator should be able to configure a system use
x
notification that is displayed to all users as part of the login
61
process.
62
The mobile system must use a least privilege authorization model.
x
63
The Mobile client must support the use of an AVL device.
x
The Mobile AVL system must support locally stored Esri -based GIS
x
64
map data for operation in a disconnected mode.
qT
Local Person /Vehicle /Property inquiries should allow wildcard
x
65
searches.
Person /Vehicle /Property inquiries should include
X
66
State /NLETS /NCIC and Local (RMS) at the some time.
The message switch or mobile server must interface to local,
x
county, state, national or any other databases for the purpose of
67
-inquiry.
Should provide records database inquiry on wants /warrants,
x
hazards, locket activity, house watches, geo -file verifications, and
68
vehicles.
69
Should provide the ability to do global name searches.
x
User should be able to run inquires for persons, vehicles or prior
x
70
calls from dispatch message without reentering information.
Should provide a location history search that can display all
x
71
1 activity, alerts, cleared calls, and resident information.
The Mobile user should be able to turn on or off different layers of
x
72
the map.
The Mobile client should be able to display all active and
x
73
pending call locations on the map.
Mobile mapping should display the position of all mobile units that
x
74
are providing AVL updates.
Mobile mapping should provide the option to display the position
x
of all mobile devices linked to a unit that are providing AVL
75
updates including tablets, cell phones, and watches.
The Mobile user should be able to filter map to display only those
x
76
units on the call they are dispatched to.
77
The Mobile user should be able to filter units to their own ORI /FDID.
x
78
The Mobile user should be able to select units to display on map.
x
The Mobile client must support routing and high lighting the
x
79
suggested route on the map.
Must plot call location on map from dispatch without reentering
x
80
address of incident.
Should be able to display the route from unit to call location on
x
81
map and with driving directions.
Calculated route should take into account roadblocks and
x
82
impediments defined in real -time in CAD.
Mobile client should support configurable geo- fencing and geo-
x
83
fence rules.
84
Mobile mapping should display geofences defined in CAD.
x
Geofences should be capable of automatically changing a unit's
x
85
status based on proximity to a location.
Geofences should be capable of notifying user based on
x
86
proximity to other units.
Mobile mapping should support integrated hyperlinks to allow
x
87
user to access files related to a map location or feature.
Mobile mapping has the ability to route unit to a call or any other
x
88
location.
User can search the mobile map for a location or any map
x
89
feature.
Should support officer- initiated calls and traffic stops and
x
90
automatically run any State /NCIC queries.
Should ability to save inquiries (State and Local) and retrieve
X
91
saved inquiries from any mobile computer.
Should provide message routing between mobile and State /NCIC
x
92
networks for inquiry purposes.
Should provide the capability for a single query to be directed to
x
93
the State /NCIC, the local database or both.
94
All State /NCIC messages must be logged and available for audit.
x
95
Should provide the capability for user - defined formats.
x
96
Should provide the capability for multi- screen formats.
X
Should support parsing of response information that can populate
x
97
other inquiries and field reports.
V.
p „jp vi 'tny;.x pl
l`
i3C Yri
SK�
J
98
Font Size
X
99
Font Color
x
100
Audio File
X
Mobile must include functionality to scan a driver license
X
barcode to send State /NCIC transactions and /or populate field
101
1 reports or other queries.
Mobile must include functionality to scan a vehicle registration
X
barcode to send State /NCIC transactions and /or populate field
102
reports or other queries.
Should provide broadcast message capability based on
x
103
configurable groups.
104
Messaging allows configuration of static and dynamic groups.
x
Messaging is available across CAD, Mobile, and LE Records
x
105
applications.
Supervisors have the capability to review any messages to or from
X
106
mobile units.
Allow users (with permissions) to set up chat groups from
X
107
MDT /MCT.
108
Allow users to inquire on chat history from MDT /MCT.
X
Mobile users must be able to access current BOLO information
x
109
directly via a hotkey or toolbar button.
The mobile system must support viewing BOLO information to x
1 10 include any photo or image.
Mobile users must be able to add new BOLOS to the system as x
111 needed; to include uoloadina photos and imaaes.
mobile client must support configuration for an
112
Mobile client should support functionality to send freeform x
113 alphanumeric text messages via CAD Paaina.
The software must support entry of incidents, cases, arrests,
X
1
supplements, and user - defined forms.
The software must also offer an option for field
x
investigations /contact cards so they can be done in the field but
3
still support a review process
Forms and report merge (into LE Records) process must be
X
4
agency- defined.
5
The software must support entry of accident reports.
x
The software must have the ability to add business logic to form
x
6
entry.
7
The software must support an IBR- compliant data schema
x
The printed output from any particular field report type must be
X
g
agency configurable to support mandated report outputs.
The software must have the ability to use a scanned image as a
X
9
background for the report.
Field Reporting must support the downloading of tables to all
X
mobile devices, eliminating the need to update tables on
10
individual devices.
11
Software should use drop -down lists and validation sets.
x
All field reporting drop -down lists should come from LE Records,
X
avoiding duplicate configuration and setup and ensuring that
12
both LE Records and FR are in synch
Should support hidden data for report entry allowing the
x
administrator to configure default values and text that becomes
13
visible based on any report field.
Should allow agency- defined data entry screens for all field
x
14
reports.
Must support multiple report types for each incident and /or case
x
so an agency can have separate screens for specific report types
15
like domestic violence
16
Should support touch screen functionality.
x
17
Should allow agencies to define business rules on any form.
x
Should allow agency - defined actions in the field report based on
x
a certain text string or predefined setup. For example, if a report
has a certain value in a field than other field (s) can be made
mandatory. This type of action should be allowed on any form or
18
any field on any form.
The software should allow for agency defined colors and modes
x
19
on all forms and screens.
The software should allow all toolbars and toolbar buttons to be
x
agency defined. In a multi - jurisdictional environment, each
20
agency can layout the system the way they desire.
The software should allow for patches and updates to be applied
x
from a central site without having to go to each individual mobile
21
unit to load.
The software should support encryption during all processes both
x
22
on the local client and over the wireless network.
The software should fully utilize XML to store, transmit, and edit
X
23
data.
Any form that is built or scanned into the field reporting software
x
should also have ability to print with the appropriate data as the
24
original form.
25
Software should support the display of a night mode theme.
X
26
The software should support user password protection
x
The software should support granting and denying permissions to
x
27
write field reports by agency.
The software should support granting and denying permissions to
x
28
view field reports by agency.
The software should support granting and denying permissions to
X
29
review field reports by agency.
Software should restrict the display of a field report that is linked to
x
30
a case that is locked in the LE Records system.
Software should prevent the display of a field report that is linked
x
31
to a case that has been sealed in the LE Records system.
Field Reporting (FR) must be able to have configurable form /field
x
32
rules that will catch most IBR errors at data entry time
The software must allow an officer to review the report for errors
x
33
and warnings before submitting to a supervisor.
34
Software must support narrative text entry with spell checker.
x
35
Software must have automatic spell check.
x
Should support copying of data from different report sections and
x
36
between different reports to cut down on data entry.
Should allow a user to base a new report on a previously entered
x
report. This would copy the applicable data out of one report
37
and into another.
Should allow users to prompt data from the report into the
x
38
narrative.
39
Should provide the ability to print in the car.
x
The software should support the start of a new field report by
x
40
defaulting information from the officer's assigned call for service.
The software should support the start of a new field report by
x
defaulting information from a booking record that the officer
41
specifies.
', c u a l
?'
L�.
w —
y
42
The software must support Supervisor Review.
x
The software must allow for upload of officer reports to the
x
43
Supervisor via the following means:
The software must support printing of a Field Report prior to being
x
44
merged into the LE Records database.
Must support handheld devices that include tablets and x
1 smartphones with functionality other than radio transmissions.
Must support GPS tracking which should be automatically x
2 updated.
3 Handheld device should include a live video camera capability. x
4 Handheld device should include a sound recording capability. X
The software must allow a user to merge officer reports into an
x
existing Records Management Database, eliminating duplicate
45
entry and any re- keying of data.
The software must be able to attach an exact copy of the field
x
46
report into LE Records as a PDF.
The software must be able to attach an exact copy of all
X
47
supplements into LE Records as a PDF
Field Reporting must support an exact copy of an officer's report,
X
as it existed when approved, for agencies that treat the officers
48
report as evidence in court proceedings
Software should allow an officer to save an incomplete report for
x
49
completion at another time.
Incomplete reports can be completed in station or on any other
x
50
device that has Field Reporting installed
The merge process should support merging one record at a time,
x
51
allowing the merge administrator to make changes if necessary.
The field reports should be capable of automatically populating
x
52
the Fields in the LE Records database during the merge process.
53
Should provide the ability to complete accident diagrams.
X
Any completed accident diagram must be part of LE Records
X
54
and accessible from both Field Reporting and LE Records.
Should allow notes on every form and field as needed by the
X
55
officer or supervisor
The software should allow for a report to be transmitted to a
x
supervisor and back to individual for review and editing all over
56
the wireless network.
Software should provide the option to track the workflow status
x
history for field reports retaining a copy of the field report data for
57
each workflow status change.
Authorized user should be able to view the workflow history for a
X
field report and display and /or print the report data at the time of
58
the workflow status change.
Software should be able to display a watermark indicating that a
x
field report is in progress if it is printed before the data has been
59
finalized in the LE Records system.
An officer should be able to recall a report that has been
x
submitted for supervisor review as long as the review process has
60
not started.
The software should allow the configuration of report fields that
x
can be used to help organize and manage field reports through
61
the workflow process.
Must support handheld devices that include tablets and x
1 smartphones with functionality other than radio transmissions.
Must support GPS tracking which should be automatically x
2 updated.
3 Handheld device should include a live video camera capability. x
4 Handheld device should include a sound recording capability. X
Should support multiple GIS map systems including Esri and
x
5
Goo le.
Applications must handle switching between networks without
x
6
interruption (e.g., WIFI network to 4G network).
Mobility solution must be deployable in both a secure cloud-
x
based service to route data between device and agency and
an on- premise server solution, depending on agency
7
requirements.
Ability to secure the application with a login including a
x
8
username and password.
Any data stored on the device must be encrypted to HIPAA and
X
9
CJIS levels.
Ability to disconnect a device with confirmation that the device
x
10
has been disconnected.
Ability to receive a dispatched call and display associated call
x
11
information.
Handheld app must adhere to CAD system permissions in regard
x
12
to access to information or status changes.
13
Ability to change status for authorized users.
x
Ability to provide GPS -based location information to CAD so that
x
14
the location can be plotted on the CAD map.
Ability to allow multiple handheld devices to be associated with
X
15
the same unit or vehicle.
Ability to show an overview map which also displays calls and
x
16
units.
17
Ability to show a list of active Calls for Service (CFS).
x
Ability to calculate and display on the map the best route
X
18
between current location and destination.
Ability to show turn -by -turn directions for route between current
x
19
location and destination.
20
Ability to view Call narrative on a CFS.
x
21
Ability to view Alarm narrative on a CFS.
X
22
Ability to view EMD narrative on a CFS.
x
23
Ability to add narrative on a CFS.
X
Ability to view pre -plan information for a building or business
X
including contacts, hydrants, onsite chemicals, and attached
24
documents such as floor Ions.
Ability to view a Personnel Accountability (PARS) countdown
X
timer and to track check -ins for all personnel associated with a
25
call.
26
Ability to show a summary of the CFS including:
27
Date and Time of Incident
X
28
Call Type
x
29
Address of Incident
x
30
Dispatched Time
x
31
Arrived Time
x
32
Cleared Time
x
33
Number of minutes while en -route
X
Total duration in minutes of the call from Dispatched Time to
x
34
Cleared Time
35
Name of all Officers associated with CFS
x
36
History of all Narrative during CFS
X
37
Ability to email the summary of the CFS.
x
Ability to print the summary of the CFS directly from the handheld
x
38
device to a network connected printer.
Ability to send /receive chat messages with CAD, Mobile, and
x
x
39
Records system users.
Available in
Available in
CAD and
LE Records.
Mobile.
Ability to support voice commands for adding CFS narrative
x
40
entries.
41
Ability to easily switch between a day /night mode display.
x
Ability to automatically capture and display the user name and
x
42
date /time of when narrative is entered.
When displaying apparatus /units on the map, the icon must
X
43
distinguish between Fire, EMS and Law Enforcement.
When displaying apparatus /units on the map, the unit number,
x
44
speed, and estimated time of arrival must be shown.
Ability to use common pinch action to zoom into and out of the
x
45
map.
46
Ability to use a swipe action to pan the map in any direction.
X
Ability to use the same data from map layers which are used in
x
47
CAD.
Ability to. automatically update the route on map if vehicle drives
X
48
off of the route
Ability to automatically zoom the map display as vehicle
X
49
approaches route destination.
Ability to show the following information in the route driving
X
50
directions:
51
Next Turn direction
X
52
Distance until next turn
x
53
Street name of next turn
X
54
Estimated arrival time
x
55
distance until destination
x
pRemaining
For call list, ability to show associated call information including
x
Call Date /Time, Call Type, Call Priority, Call Location, Radio
56
Channel, ETA, Last Narrative.
57
Ability to filter call list by FDID or ORI.
X
Ability to zoom and center the map to corresponding call when
x
58
the call is selected in the call list.
59
Ability to easily view next PARS time.
x
60
Ability to reset the PARS timer.
x
Ability to initiate immediate PARS timer reset for specific situations
x
61
such as all clear or sudden hazard.
Ability to view personnel associated with call and display an
x
62
indicator that shows if they have checked in.
K tot[ -1'!4
Ability to show users who are online and who can receive a chat
x
63
message.
•au
a
1
Solution must be a complete, turnkey solution integrated with the
x
d
public safety system.
2
Solution must be configurable to meet the Agency's requirements.
x
3
Shall run on any device with a Windows, Android, or IOS operating
x
system.
4
Solution should not be hard -coded for a specific function but
X
running on a configuration interpreter for flexibility.
5
Solution must support multi- agency /multi- department
X
implementation.
6
Must support custom workflows.
x
7
Solution must be entirely web -based and require no dedicated
x
workstations for administration or updates.
8
Assign unique citation numbers and include complete audit reports
X
to account for all citation numbers
9
Provide data integrity controls to prevent a loss of data integrity
x
such as a disassociation of citation number to citation data, mixing
of citation data, association of citation number to multiple records,
association of citation data to the wrong citation number, data
corruption and other forms of integrity loss.
10
Reinitialize a handheld device and reestablish the configuration
x
after the battery dies.
1 1
Data must be encrypted.
x
12
Must be able to capture signature electronically,
x
13
Solution must allow officers to create, save, and print citations with
X
or without network connectivity.
14
The solution must ensure that no ticket records are lost, or in
X
jeopardy of being lost, due to software, hardware or wireless
network problems, or due to low battery power.
15
Software installation must be an automated process that requires
X
minimal IT involvement.
16
Must provide the ability to add additional customized "forms" such
X
as parking, racial profiling, field investigation, crash, etc., that also
meet the exact process flow desired by the Agency.
17
Must have the function of drawing collision diagrams and
X
automatically attach to citation.
18
Must be able to interface with all of the Agency's existing systems.
X
19
Must offer an import /export wizard for creating new interfaces.
x
20
Must allow authorized users to view and print the citation from
x
website.
21
Solution must provide a system that provides real -time access and
x
query to State /NCIC.
22
Vendor must offer customer support, 365 days a year, 24 hours a
X
day, 7 days o week, including holidays
23
Vendor maintenance plan must be all inclusive'flat fee' that will not
x
require the agency to pay any additional fees for changes,
modifications, and updates requested by courts and State
throughout the year
24
Training shall consist of two (2) days of on -site officer /employee
X
training, including classroom and On the Job training; online
reference materials; one 1 day remote administrator training.
25
Vendor must have been in business for a minimum of five (5) years.
X
The Court Case Management System must utilize a true 32 -bit
X
1
Graphical User Interface,
2
Master files are used to reduce the need to re -enter often used
X
information, codes, persons, and vehicles.
A "List Window" for all fields marked with a dropdown must allow
x
the user to select code from the screen during input without
3
having to look up information in separate manuals, and provide
the ability to add new codes from a lookup window without exiting
to a file maintenance program.
4
All dates in the system use a four (4) digit year.
X
Docket numbers can be manually entered, automatically entered
x
5
by the system, or the citation number can automatically be used
as the docket number.
6
The system collects street name and block number in the location
x
of a violation fields.
7
The system has defaulted fields for new citation entry.
x
8
The user can define unlimited warrant types.
X
9
The system must keep a history of previous addresses for persons in
X
the Master Name file.
10
System must track changes to master name file by user and date.
x
The system must provide an option to add a fee to citations
x
1 1
involving an accident.
12
A fee can be added to warrants when issued. This is done for each
X
of the warrant types.
The system allows partial payments to be taken for a fine and
x
13
distributed to the fees /costs /fines, fines /fees /costs, or a
percentage to fees /costs /fines.
14
The systems must not allow the same citation number to be used
X
more than once.
15
The system must allow the user to attach multiple violations to the
X
basic citation information.
The system must provide for each fine and multiple fees and /or
x
16
court costs to be attached to the offense, based on State & Local
fees /costs requirements.
17
The system must allow fees /costs /fines to be increased or
x
decreased without affecting other citations.
18
The system must allow an administrator or designated user to
x
adjust fees or fines in a table, based on effective date.
19
The system must display all violations for a defendant in a single
x
Inquiry Screen.
If a violator is a juvenile at the time of the violation, an indicator
x
20
must be shown on the Name, Inquiry, and Case information
Screens.
21
The system must be able to create an export file for the Collection
x
Agency,
22
The system must note in the case state specific collection
x
information.
{s uf. .�t 1 , - .; -.
23
Citation number.
x
24
Date violation occurred.
x
25
Time violation occurred.
x
26
Date citation filed in Court.
x
27
If an accident involved.
x
28
If hazardous material involved.
x
29
Display Commercial Driver's License flag,
x
30
State Specific identification numbers.
x
31
Name of the violator (see Master Name File for detail).
x
32
Information on vehicle involved (see Master Vehicle File for detail).
x
33
Officer issuing citation (see Officer File for detail).
x
34
County where violation occurred.
X
35
The system must allow for cases that are not initiated with a
citation.
x
36
System must be able to capture user defined code for selected
citations for tracking purposes.
x
^.s�Jw ]r
34
Docket number (assigned by system, manually entered or same as
citation number).
x
_
35
Offense.
x
36
Location of the violation (block, street).
x
37
Intersection.
x
38
Location of intersection (block, street).
x
39
Location grid (user defined).
x
40
Attorney of record (from Attorney file).
X
41
Judge scheduled to hear case (from Judge file).
x
42
Plea entered.
x
43
Date plea entered.
x
44
Date of conviction.
x
45
Date conviction reported to State.
X
46
Current case event status, due date /pending date and time.
x
47 The system must allow for multiple statuses, due dates /pending
dates / and times.
x
x
48
Warrant status of case.
49
Fees due for case.
X
50
Court costs due for case.
x
51
Fines due for case.
x
52
Total amount due for case.
X
53
Bond set by Judge.
x
54
Bond posted by violator.
x
55
Type of bond posted.
x
56
Indicator for "No Bond."
x
57
Bond agent or attorney.
X
58
Review Attorney.
x
59
Prosecutor.
x
60
Date case sent to collection agency.
x
61
Date case cleared from collection agency.
x
62
State specific case information for state reporting.
x
63
Continuance Tracking.
X
64
Driver's License suspension.
X
65
Suspension date,
x
66
End suspension date.
x
67
Date suspension report to State.
x
68
Special sentencing.
X
69
Other complainant.
x
70
Posted speed limit.
x
71
Actual alleged speed.
x
72
Construction zone.
x
73
Must be able to double fines for violations within a construction
zone.
x
74
The system must allow for a complaint form to be printed for each
violation on each citation entered.
X
75
The system must have the ability to print a complaint.
X
76
The system must allow for a complaint form for each violation to
be user defined.
X
77
A user defined letter can be produced automatically to send to
the parent /guardian of juvenile offenders.
x
"K,
78
Last Name
x
79
First Name
x
80
Middle Name
X
81
Suffix Name
x
82
Soundex code last name
x
83
Soundex code first name
x
84
Date of birth
x
85
Sex
x
86
Race
x
87
Ethnic Designator
X
88
Height
x
89
Weight
x
90
Hair Color
x
91
Eye Color
x
92
Driver's license number
x
93
Driver's license State
X
94
Driver's license expiration year
x
95
Driver's license type
X
96
Driver's license CDL
x
97
Social Security Number
x
98
Address /Block /Street /Apartment /City /State /Zip
x
99
Home phone
X
100
Cell Phone
x
101
Occupation
x
102
Employer
x
103
Employer address /city /state /zip
X
104
Work phone
x
105
The system must have a Master Name file that holds information on
all persons in the court system.
X
106
Once a person is added to the Master Name file, the system must
have the ability to attach the name to multiple citations without
re- entering their personal information.
x
107
The system must provide for user - defined flags to be placed on a
defendant that will be view from other programs in the software
(e.g., CASH ONLY, VIOLENT, CDL).
x
108
The system must provide for alternate mailing addresses for
defendant.
x
109
The system must provide for Alias Information.
x
110
The system must display all violations for a defendant, including
citations for Aliases on the Inquiry Screen,
x
III
Ability to capture photograph of violator and attach to file.
x
112
Must be able to print photo directly onto documents (e.g.,
Warrants).
x
113
Make of vehicle
114
Model of vehicle
115
Body style of vehicle
116
Year of vehicle
117
Vehicle color - must allow for multiple colors
118
Commercial vehicle
119
VIN
120
License plate State
121
License plate number
122
License plate expiration year
x
123
Comments or Notes on the vehicle
x
124
Registered Owner information
x
125
Date last sold
x
126
Boot or Tow Information
x
127
The system must maintain a history of any changes made to the
vehicle information by user and date.
x
128
Once a vehicle is entered in the system it must be able to attach a
vehicle to multiple citations without re-entering the information.
129
Officer agency
130
Officer badge/id number
131
Officer last name
132
Officer first name
133
Officer middle initial
134
Officer rank
x
135
Officer email address
x
136
Officer Alternate contact information
x
137
Sub - station information
x
138
The system must maintain an Officer Master File that allows officers
to be associated with their citations Without typing names for each
citation.
x
139
The system must allow for Citation Book Tracking for citation books
assigned to officers.
x
140
The officer's badge /ID number must allow for a change without
affecting citations already entered, or future citations entered in
the court system.
x
141
I
The Attorney/Bond Co. & Collection Agency Master file must
eliminate the need to type in attorney information for cases.
x
142
I
Attorney/Bond Company or Collection Agency name must be
searchable.
x
143
Contact Person.
x
144
Firm/Company name.
x
145
Firm/Company address /block /street /city /state /zip,
x
146
Phone number/Alternate Phone number/ Fax number,
x
147
The system must be able to set a Bond Limit for Bondsperson.
x
148
The system must collect Attorney State Bar number and expiration.
x
149
The system must collect Bondsperson License number and
expiration.
x
150
The system must collect Bondsperson insurer.
x
151
The system must be able to receive a bond payment separately
from a court payment.
x
152
The system must have a field to enter the Bond number,
x
153
The system must have the ability to display Bond Company
information related to each case.
x
154
The system must allow a single bond to be applied to number
violations on the defendant, and /or transferred to othercases
within one bond management screen.
x
155
Must be able to accept and track:
x
156
Cash Bonds
x
157
Surety Bonds
x
158
Property Bonds
x
159
PR Bonds
x
160
The system must allow a bond to be returned, forfeited, or
changed by designated user.
x
161
Warrants can be automatically flagged by the system or selected
by the user and printed by the system.
x
162
The system must retain information on served warrants for historic
purposes.
x
163
The system must be able to automatically add a warrant fee to
fees /costs when a warrant is issued.
x
164
The user can define an unlimited number of warrant types and set
up the wording for each.
x
165
Warrant number.
x
166
Type of warrant (user defined),
x
167
Date warrant was issued.
x
168
Amount of bond set for warrant.
x
169
Amount due for warrant.
x
170
Name of person for which warrant issued.
x
171
Vehicle information.
x
172
Date warrant closed.
x
173
How closed (served, recalled, canceled - from user - defined fields).
x
174
Person closing warrant,
x
175
Officer warrant assigned to for service.
x
176
State /Regional Data Bank Information.
x
177
ID number.
x
178
Date entered.
x
179
Date removed.
x
180
Current status of warrant.
x
181
Notes or Comments section specifically for warrants.
x
182
The system must be able to track and log service attempts for
warrants.
x
183
The system must provide for a user - defined warrant form with
site /state specific information for each type of warrant.
x
184
The system must provide for a secure signature to be placed on a
warrant if desired.
x
X
185
Warrant program must be able to maximize fine automatically.
186
The system will allow fees, costs, or fines to be changed when
x
payments are entered.
187
The system will allow payment in full or partial payments.
X
188
The system must allow credit to be applied to a case for various
x
types of community service or jail time.
189
The system must have Internet payment capability
X
190
The system must have receipts that are printed and numbered for
x
each transaction
The system must allow for cases to be set for any type of court
x
191
session and a case docket printed for each pending court session
or prior court sessions
192
The system must allow for subpoena printing for officers and /or
x
witnesses automatically within the court setting process
193
The system must allow for subpoenas to be printed for one entire
x
court session at one time
194
Automated processes must be available to perform batch
X
processing without human intervention
195
Cases must be able to be processes individually or in a group,
x
using user defined process steps
196
The system must allow for purging cases
x
197
The system must allow for expunging cases
X
198
The system must allow for sealing of cases
X
199
The system must allow for cases to be placed on any user defined
x
program including:
200
Probation
x
201
Deferred adjudication /diversion
x
202
Traffic school
X
-203
Any type of program /sentence ordered by the judge and tracked
x
through completion
204
The system must have a live courtroom docket for disposition of
x
cases in real -time in the courtroom.
205
The system must have a live courtroom docket that has a
x
customizable view for each user.
The system must have a courtroom check -in program which allows
x
206
for unscheduled cases to be placed on the courtroom docket at
the time of check -in.
The system must have a live courtroom docket which has a one-
x
207
click to detailed case information, prior violation information,
imaging system and processing information.
208
The system must provide user - defined workflow utilizing queues
x
and automated processing.
209
The system must be able to assign cases to multiple users through
x
queue -based workflow.
1
210
The system must allow for a full Court Calendar template and
X
creation.
The court sessions must allow for user defined sessions to include
x
211
maximum number of cases allowed in a court session, and the
weight given to each type of case for accurate caseload.
212
The court calendar must be displayed in a daily, weekly and
x
monthly view.
213
The court calendar must filter for view by Judge, Session and
x
Prosecutor.
214
The court calendar must allow for editing by designated user.
x
215
Calendar must validate court date availability prior to setting the x
case for court.
The system must have a document generation capability that
X
216
merges case management system data with word processing
templates.
217
The system must allow for the court to add, modify and otherwise
x
maintain the templates without programmer assistance.
218
Any documents produced by the court must be able to be sent
x
directly to the case within document imaging.
219
The system must provide for either manual or automatic
x
production of complaints if needed.
220
The system must provide the capability of emailing any generated
x
document.
221
The system must prevent documents from being printed when the
x
address is undeliverable.
222
The system must provide for more than one address to be placed
x
on a generated document.
223
The system must be able to create the following non - compliance
reports:
224
Number of payment plans /cases are late with payments
x
225
Number of extensions /cases have not paid by extension due date
x
226
Number of cases have not completed Traffic School by due date
x
227
Number of cases have not completed Diversion /Probation terms or
x
payment by due date
228
Number of cases have not completed court ordered classes by
x
due date
229
Number of cases are in collections for non - payment
x
230
Number of cases have a DL Suspension status for non - payment
x
231
The system must be able to create the following reports for
x
outstanding cases by:
232
Officers
x
233
Offense
x
234
Judges
x
235
The system must comply with all State Reporting.
x
236
The system must be able to export select reports to Excel.
x
237
The system must provide reporting based on case status, file date
x
and citation date.
238
List Citations by Violation Date
x
239
List Citations by Filed Date
x
240
List Citations by Citation Number
x
241
List Citations by Docket Number
x
242
List Citations by Violator Name
x
243
1 List Citations by Officer
x
244
List Citations by Violation Type
x
245
List Citations by Court Date
x
246
List Citations by Due Date and Event
x
251
List of Vehicles by make, model, year
247
List Citations by Payment Plan
x
252
List of Vehicles by license plate information
248
List of Defendants by Name
x
249
List of Defendants by sex, race, date of birth, ethnicity
x
250
List of Defendants with associated vehicles
X
264
List of Warrants Outstanding by date or person
x
251
List of Vehicles by make, model, year
x
List of Warrants entered and removed from State /Region data
bank
x
252
List of Vehicles by license plate information
X
Option to include name /address information in warrant reports
x
253
List of Vehicles with associated persons
x
Must be able to update a warrant status notes with "attempt to
x
254
List of Officers by Name
x
255
List of Officers by Agency /Badge /ID Number
X
256
List of Citation Books assigned to an officer I
x
257 The system must produce a list of cases by attorney or surety bonds x
by attorney /bond company /collection agency.
258 The system must list attorneys by name. x
259 The system must list court cases on docket by attorney. X
260 The system must list bond companies by name. x
261
The system must provide warrant report of defendants with
warrants in the system.
x
262
List of Warrants Issued
x
263
List of Warrants Cleared
x
264
List of Warrants Outstanding by date or person
x
265
List of Warrants entered and removed from State /Region data
bank
x
266
Option to include name /address information in warrant reports
x
267
Must be able to update a warrant status notes with "attempt to
x
268 1
Payments by date
x
269
Payments by Receipt number
x
270
Payments by Fees /Costs /Fines
X
271
Payments by GL account number
x
272
Fees /Cost distribution for quarterly report to State
x
273 1 Conviction report to State to include all State required reports x
274 Various court docket schedules by judge /date /type of trial x
275 Monthly judicial report to State x
276 List of persons requesting Drivers Safety Course x
277 List of cases pending by various status x
278 Outstanding bond list I x
279 Bonds Posted x
280 Bonds Forfeited /Refunded x
281
Central cash collections
x
282
Imaging capability
x
283
Public safety RMS
x
1
The Central Cash Collection System must utilize a true 32 -bit
284
Financial software
x
Graphical User Interface.
285
Hand -held citation issuing device
x
2
System must be able to accept cash receipts for all types of court
286
Third -party collection agency
x
payments.
MOM-
1
The Central Cash Collection System must utilize a true 32 -bit
Graphical User Interface.
2
System must be able to accept cash receipts for all types of court
X
payments.
Cashiers are to have a workstation with a dedicated
x
3
receipt /validation printer, Credit card swipe, automated cash
drawer, signature pad, and eyeball camera.
4
The system must provide the option to have more than one
x
operator logged into a work station at the same time.
5
System must require that each operator is given a unique code that
x
must be used by the operator receiving payments on a workstation.
The system must allow that if only one operator is logged on a work
x
6
station, the unique operator code should not have to be re- entered
before each payment posted.
The system must provide department level security for the
x
7
centralized cash collections system which allows departmental
access granted or prevented based on security settings.
8
Operator profiles should define authorized security parameters for
x
each operator in the cash collection system.
Each operator profile must contain operator name, the terminal to
x
which the login permits access, the operator's cash drawer and
printer setup, the operator's login and transaction passwords, the
9
department codes the operator is authorized to access, the
transaction codes for which the operator is authorized to accept
payments, and the payment methods the operator is authorized to
receive.
The system must provide an inactive status flag on the operator
x
10
profile to suspend an operator who has been terminated - An
inactive operator ID cannot be used to access cash collections,
but can still be selected to include on reports.
11
An operator listing must be available for printing from the operator
x
maintenance.
Each operator must be able to have multiple batches active in the
x
12
system, and the ability to update each separately - the batches
must be available with approval and update functions from the
same operator process window.
13
Cash receipts integrated into Court must remove warrant status
x
when full payment is made.
Receipts are reflected in the vendor's integrated sub - system as
x
14
"pending activity" until such time the daily posting procedure is
completed.
15
Each type of receipt must carry a unique code that indicates the
x
type of payment being posted.
A drop -down list look -up feature must be provided that allows the
x
16
operator to view the available codes authorized for that operator
and make a selection.
The transaction codes must be user defined providing parameters
x
17
such as description, an option for a default charge, and a receipt
description.
18
Must provide an option to deactivate transaction codes.
x
19
Must provide the ability to require a description for General Ledger
x
type transaction codes.
System must support a minimum of 99 predefined General Ledger
x
20
accounts that may be debited /credited for each transaction
code.
21
Must have an option to apply a receipt across multiple General
x
Ledger accounts on a predefined percentage basis.
22
The system should be capable of endorsing checks and printing
x
receipts.
The time, date, operator code, amount paid, how paid, amount
x
23
posted, change given, and customer balance should be printed
on the receipt or bill.
24
The system must provide online account number validation
x
integrated court system.
25
The system must default to the balance currently owed by the
x
violator when posting a payment to the court account.
26
Any overpayments must be stored in an unapplied credit account
x
until applied against the proper revenue code.
When posting a payment the system must provide the ability to
x
27
look -up tickets by ticket number, the violator name, or a portion of
the name - once the account is selected, the operator can choose
from all tickets available for that account to apply payment.
28
The system must allow financial transactions be consolidated for a
x
person across multiple cases.
29
The system must be able to compute and display all fees and costs
x
associated with a case
30
Balance financial obligation must display inclusive of all fees and
x
costs for cases with payment applied.
31
The system must allow for a non -cash transaction, e.g., jail time
x
served, community service, etc.
The system must have the ability to process cases in the payment
x
32
screen e.g., add fees, change status, print documents, according
to court processes.
The system must be able to place defendants into a payment plan
x
33
or agreement and have the payment ordered display on the
payment screen.
34
The system must allow emailing receipt to defendant and /or
x
multiple parties.
35
The system must allow for a payee that is different from the party on
x
the case.
36
The system must allow for multiple payment methods on one
x
payment.
37
The system must allow for multiple cases to be paid with one check
x
or payment method.
38
The system must allow a supervisor to view batch total for operators
x
throughout the business day.
39
The collection sequence of fees and fines must follow state
x
requirements.
40
The system must allow for a credit card payment to be processed in
x
the system without having to use an outside terminal.
41
The system must allow for credit card payments to be made over
x
the phone.
The system must be able to block payments where there is a
x
42
mandatory court appearance, but allow payment after
adjudication.
43
The system must allow for miscellaneous payments, (e.g., copies,
x
reports) that are separate from the defendant case.
The system must allow the court to designate whether the
x
44
supervisor or cashier will perform individual cashier close out and
reconciliation.
45
The system must be able to combine multiple batches into a single
x
deposit or posting.
The system must allow for returning a batch to the operator for
X
46
correction before final posting, even if moved to the pre -post
system.
The system must be able to receive the Online Payments in a batch
x
47
for posting with all payments at the posting time designated by the
court /finance
48
The system must allow the payment screen to have alerts which
x
would alert to clerk to CASH ONLY, BAD CHECK, WARRANT, etc.
49
The system must have a customizable grid on the payment screen
x
to display defendant case information
50
Operators should be warned by the system if they attempt to post a
x
ticket payment to a case that has a payment pending
51
A record of each transaction must be able to be printed on a
x
separate journal tape.
They system must provide for verification of online credit card
x
52
payments based on address or credit card security code - setup
requirements may apply for the merchant code when using this
feature.
The system must provide the feature to mask credit card
x
53
information on receipts and reports - options should include the
ability to mask full credit card numbers and /or expiration dates.
They system must provide the ability for a cashier to collect and
x
54
receipt payments for miscellaneous transactions not related to
offenses entered in the system.
From the operator process window, the operator must be able to
x
55
create, open, and close batches, as well as enter payments, void
receipts, and reprint receipts.
The system must allow, at the end of a cashier's scheduled day, a
x
56
close -out report to be printed and balanced with the cash, checks,
money orders, etc. in the operator's drawer.
The system allows the ability to record cashier over and under to a
x
57
finance system account, as well as, the ability to print a receipt for
the over and under transaction.
58
The system must provide the ability to void a receipt.
X
The system must provide online context sensitive documentation
x
59
with table of contents, index, and keyword search capabilities, and
the ability to email or generate fox sheets for support requests
directly from the application.
The system must provide direct access to the vendor's help website
x
to log support requests, query knowledge base for FAQs,
60
participate in user -group discussions, and download updates via a
secure connection.
If a customer pays less than the current balance in the court case,
x
61
the payment should be automatically distributed to revenue
categories based on a user - defined formula.
X
The system must allow a user - defined message to be printed on the
62
bottom of the receipt - the message will print on all receipts
regardless of the system a payment is collected for.
When processing a customers ticket payment, the system must
X
provide the ability to go to court case management window and
63
inquire information such as transaction history, detailed data of
current ticket, violator history, etc. - once the inquiry is complete,
the system must return the user to the original point of processing.
The system must provide the ability, at any time of the day, to
x
display a summary of all receipts processed at a cash collection
64
workstation - information displayed should include the operator's
code and name and payment type (cash, check, credit card,
etc.) the grand total of all receipts at the workstation should be
displayed as well as the total number of receipts voided.
The system must allow for user defined payment methods to be
X
65
setup with an associated bank reconciliation group to be assigned
to each payment method.
66
Cash Collections must be integrated to provide the ability to
x
automatically post to the court system.
67
s.
The system must provide all stat=Windows
x
All reports must be able to be ph a Windows-
x
68
format viewer with user - defined ers, layouts,
formats, and rinters available.
The required viewer should prov, and status bar
X
69
functionality.
The required viewer should provide a report warehousing function
x
70
through folder structure on server, with the ability to retrieve and
reprint any or all previously warehoused reports.
The system must produce a journal report for each operator,
x
71
department, terminal and batch.
Users must be able to save filtering and formatting settings specified
x
72
for a particular report with a profile name for retrieval when printing
the report on a subsequent occasion.
73
Users should be able to flag a profile as the default for loading
x
report settings.
74
The system must produce a History Transaction Report by
X
transaction date, posting date, receipt range and packet.
75
The system must produce a payment history report by payment
x
method.
76
The system must produce a report of all cash long or short entries
x
and amounts.
77
The system must produce a report that would list all outstanding
x
Must be able to match the City's website decor and format.
1
Ability to expose cases via browser for internal and external
viewing.
fees /fines /costs.
2
Website must be PCI compliant.
2
78
The system must produce a report that would list all paid
x
Must be able to accept Credit, Debit and e- checks for
payments of court fees /fines.
3
Ability to view general citation data i.e., Name, DOB, violations,
dates and amounts, Citation #, Docket # and Current Status on
one screen view.
fees /fines /costs within a date range in detail and summary.
4
Must be able to accept partial payments.
4
79
The system must produce a report showing restitution paid.
x
Must integrate to the court system in real time.
5
y y o e
1
Must be able to match the City's website decor and format.
1
Ability to expose cases via browser for internal and external
viewing.
X
2
Website must be PCI compliant.
2
Secured or open accessibility.
X
3
Must be able to accept Credit, Debit and e- checks for
payments of court fees /fines.
3
Ability to view general citation data i.e., Name, DOB, violations,
dates and amounts, Citation #, Docket # and Current Status on
one screen view.
x
4
Must be able to accept partial payments.
4
Ability to view case status including warrants, court location and
pleas, bonds, configurable by the site.
x
5
Must integrate to the court system in real time.
5
Ability to view Judgment data included but not limited to:
x
6
Must be accessible from the City's website.
6
Judge
x
7
Must clear warrants in real -time when a full payment is made.
7
Verdict
x
8
Must be formatted to operate on a smartphone or tablet
device.
8
Original offense and amended offense
X
9
Must allow defendant to view past or paid citations.
9
Prosecutor and /or Review Attorney
x
10
Program must be highly configurable by the site.
10
Defense Attorney
x
1 1
Restitution amount sentenced
X
12
Must be integrated in the on -line payment system for payment
options.
X
13
Must be highly configurable by the city to prevent or allow
various data elements to be exposed or hidden.
x
14
Must be able to view court dockets for upcoming court sessions
to include:
x
15
Session, location, date and time
X
16
Hyperlinks to List of defendants
X
17
Hyperlinks to case details
x
y y o e
1
Must be able to match the City's website decor and format.
X
2
Website must be PCI compliant.
X
3
Must be able to accept Credit, Debit and e- checks for
payments of court fees /fines.
x
4
Must be able to accept partial payments.
x
5
Must integrate to the court system in real time.
x
6
Must be accessible from the City's website.
x
7
Must clear warrants in real -time when a full payment is made.
x
8
Must be formatted to operate on a smartphone or tablet
device.
x
9
Must allow defendant to view past or paid citations.
x
10
Program must be highly configurable by the site.
x
a�.
HIRE, MINIM f� Ag
Must retain defendant email address entered for payment
x
11
confirmation, as information placed in the court system
Ability to auto dial defendants based on a preset message and X
X
defendant email address field.
Ability to call in English or Spanish. X
X
12
Must have ability to provide defendants with options such as
x
x
Extensions, Driving Safety or Traffic Schools, etc.
Date and time of call must be configurable by the court staff x
x
13
Must have the ability to customize requirements for defendants
X
to upload or download required documents.
Answered call x
x
14
Must have the ability for uploaded documents to be
X
x
automatically stored in the document imaging software.
Voicemail x
x
a�.
HIRE, MINIM f� Ag
-
o�
1 A
Ability to auto dial defendants based on a preset message and X
X
2 A
Ability to call in English or Spanish. X
X
3 T
Text must be configurable by the our staff without programmer x
x
4 D
Date and time of call must be configurable by the court staff x
x
5 a
Must integrate with the court case management system to
6 A
Answered call x
x
7 W
Wrong number x
x
8 V
Voicemail x
x
9 H
Hang -up x
x
10 N
No answer x
x
1 1 B
Busy line x
x
12 I
Information tone x
x
13 S
System must provide notification results reports to include the
following:
14 A
Answered call x
x
15 W
Wrong number x
x
16 V
Voicemail x
x
17 H
Hang -up x
x
18 N
No answer x
x
19 B
Busy line x
x
20 T
Total Notifications x
x
21 S
System must provide notification results reports to include the
followin :
22 P
Payments received within 48 hours of the call X
X
23 P
Payments received within a specific date range x
x
24 W
Warrants cleared as a result of the call x
x
HIRE, MINIM f� Ag
5
Email capability to defendant from court case management
X
system.
6
Ability to redact and /or highlight in imaged document.
x
Ability to automatically rubber stamp documents as a
x
7
workflow step (e.g., stamp "Received by (date)" as a
document enters the database).
8
Imaged documents must be categorized by date entered
x
into imaging,
9
Photos and /or videos must be able to be placed in imaging,
x
in a particular case.
Documents in imaging must be easily retrieved from
x
10
numerous programs within the court case management
system.
1 1
The system must have a client friendly user interface to create
X
new document types from existing templates.
12
The system must have the ability to capture documents from
x
forms with preprinted barcodes.
13
The system must allow for batch scanning of documents.
x
14
The system must have the ability to perform a keyword search
x
for documents within imaging.
The system must allow for security within the system (e.g.,
x
15
documents may be hidden from users without permission to
view).
16
The system must allow for purging of images when a case is
x
purged in the system.
The system must allow documents from the court case
x
17
management system to be sent automatically to imaging in
the specific case.
City of Owasso, Oklahoma
The CAD Project
2. Technical Information
Our response centers around a virtualized Windows Server 2019 environment configured to work within
the City's network. Windows Server 2019 is the most integrated, comprehensive and easy -to -use server
operating system available today. Its flexibility and expanded communications services meet the most
demanding requirements of today's computing environments, while providing the best network
foundation for the future.
The system configuration will provide high performance. A Windows workstation environment exists to
provide the ability to switch /interface applications easily, including any workstation -based applications
the user may require. The Windows look and feel combined with Tyler's standard menu - driven
capabilities results in a familiar and practical presentation format.
Some of the major benefits of the Windows Server 2019 are its processing speed, reliability and storage
capabilities. All communication procedures, system security, network monitoring and server diagnostics
are made simple with graphical user interfaces. The operating system was designed to allow the system
to grow as a client's needs change. The ability to add hardware components without the need to modify
the Windows Server 2019 software protects your original investment for many years to come. Tyler will
team with the City to develop a successful project plan and together we will proceed through a smooth
implementation process that culminates when the system goes live.
Hardware Requirements
System Hardware
Host Servers
(2) Dell PowerEdge R650 (1U) Rack Server (Or Similar)
- (2) Intel Silver 4310 2.1Ghz, 2666MHz, 12C Processors
- 512GB 3200MHz RDIMM (Memory)
- Internal Dual SO Module with 16GB SD Card
- Diskless configuration, iDRAC9 Enterprise
- (1) Intel X710 -T4L Quad Port 10Gb Base -T OCP NIC 3.0
- (1) Intel X710 -T2L Dual Port 10Gb Base -T PCIe
Dual, Hot -Plug 110OW Power Supply
- 3 Year ProSupport and Mission Critical 24X7X4 Hour Onsite
Storage Array (SAN)
(1) Dell EMC PowerVault ME4024 (2U) 10GB iSCSI Hybrid SAN (Or Similar)
- (6) 960GB SSD 2.5" SAS Hot Plug Disk Drives (5.8TB RAW)
- (14) 1.2TB 10k -RPM 2.5" SAS Hot Plug Disk Drives (16.8TB RAW)
- (4) Blank Future Expansion Slots
-10Gb iSCSI Base -T Ethernet Dual Controller (Up to 8 Total)
- Dual Controllers with 8GB Memory (16GB total)
- Supports RAID 0, 1, 5, 6, 10, 50 or Adapt
- Redundant Hot Swappable Controllers and Cooling Fans
- Dual, Hot -Plug 58OW Power Supply, 100 -240v
- 3 Year ProSupport and Mission Critical 24X7X4 Hour Onsite
c
`CO. tyler Page 12
City of Owasso, Oklahoma
The CAD Project
System Software
Host Servers
(24) Microsoft Windows Server 2019 Datacenter- License, 2 Cores, MOLP Gov
(100) Microsoft Windows Server 2019 - Device CALs (Estimated)
(6) SQL Server 2019 - Standard Core Edition (12 vCPUs Total)
(1) VMware Essentials Plus 7 - Includes vSphere & vCenter for 3 Hosts, 1 Yr. SnS
(2) Microsoft Office Standard 2019 - License, MOLP Gov (Prod/Test)
Workstation Specifications
Call Taker /Dispatcher Workstation
- Intel Core i7 /Xeon (4C) Processor
- Windows 10 Professional 64 -bit
-16GB System Memory
- Keyboard, Mouse, DVD -ROM
- SSD System Disk (50GB Available)
- Integrated GB Ethernet, Integrated Audio w /External Speakers (Audible Alerts)
- (3) 24" Flat Panel Color Monitors (1024 X 768 or Better)
- Quad Port Graphics with 4GB Dedicated Memory
RMS /Court Workstation
- Intel Core i5 /i7 Processor
- Windows 10 Professional 64 -bit
- 8GB System Memory
- SSD /SATA System Disk (50GB Available), Keyboard, Mouse, DVD -ROM
- Integrated GB Ethernet, Standard /Integrated Graphics Adapter
- (1) 24" Flat Panel Color Monitor (1024 X 768 or Better)
Mobile Data Computer
- Intel Core i5 /i7 Processor
- Windows 10 Professional 64 -bit
- 8GB System Memory
- SSD /SATA System Disk (50GB Available - Not Including Aerial Imagery)
-12" or Larger Display (1024 X 768 or Better), Backlit Keyboard
- Optional Integrated 4G /LTE Mobile Broadband w /GPS
Windows Tablet
- Intel Core i5 Processor
Windows 10 Professional 64 -bit
8GB System Memory
SSD /Flash System Disk (50GB Available - Not Including Aerial Imagery)
tyler Page 13
City of Owasso, Oklahoma
The CAD Project
10" or Larger Display (1024 X 768 or Better), Wil'i 802.11 g /n /ac
Optional Integrated 4G /LTE Mobile Broadband w /GPS
Mobility Device
- 10S Version 13.0 (or newer), 32GB Capacity (or larger)
- Android Version 8.0 (or newer), 32GB Capacity (or larger)
Hardware System Diagram
Please see attached.
Page 14
City of Owasso, Oklahoma
The CAD Project
2D Barcode Imager
2D Barcode Imager
(1) L -TRON 4910LR- 152 -LTRK 2D Imaging Scanner
- High Performance 2 Dimensional (PDF 417) Barcode Imager
- High Visibility Green LED Aimer and Red LED Backlight
- Supports COM Port Emulation, Keyboard Emulation, HID Mode
Microphone Style Megapixel Imager w /Mount
9.5' Coiled USB Interface Cable
Native USB COM Port Emulation Drivers
- 3 Year Warranty
Bar Coding Scanner Kit with Signature Pad
Zebra TC72 TC720L- OME24BO -FT Handheld Tablet
-Android 10 Operating System
Qualcomm Snapdragon 660 octa -core 2.2 Ghz
4.7" HD Multi Touch LCD, 1280 X 720 Resolution, Gorilla Glass
32GB Flash Memory
-4GB RAM
- 802.11 a /b /g /n /ac WiFi, Bluetooth, NFC, GMS
- 1D /2D Barcode Laser (SE4750)
-13MP Rear Camera, 5MP Front Camera
- 4620mAh, 3.7V Hot Swap Li -Ion Battery Pack
- 6.3" (L) X 3.3" (W) X 1.1" (H), 13.3 oz.
- FIPS & TAA Compliant
Five -Year oneCare Essential Support Services Z1AE- TC72XX -5C00
Zebra LI4278- PRBU2100AWR Cordless Handheld Scanner Kit
- Zebra LI4278- SR20007WR Linear Scanner
- Zebra CR0078- SC10007WR Desktop Cradle
-Zebra PWR- BGA12V50WOWW Power Supply
- 7' USB Cable
- Bluetooth
3 Year Limited Warranty, Parts & Labor (Excludes Battery)
Zebra ZD421 ZD4A042- 301EOOEZ Thermal Barcode Printer
-4" Print Width
- Thermal Transfer /Direct Thermal
- 203 dpi Print Resolution
- 256MB Standard Memory
- 10/100 Ethernet or USB
Page 15
City of Owasso, Oklahoma
The CAD Project
Topaz SignatureGem T- LBK755SE- BTBl -R Bluetooth Signature Pad
- Tempered Glass 4X3 LCD Display
- 2 Year Manufacturer Warranty
*A USB Signature Pad is available upon request (T- LBK755- BHSB -R)
ACCESSORIES
Zebra CRD- TC7X- SE2EPP -01 Single Desktop ShareCradle
- Includes Spare Battery Charging Slot
- Charge /USB /Ethernet Connection
Zebra PW R- BGA12VSOWOW W Power Supply Adapter
Zebra CBL- DC -38BA1 DC Line Cord
Zebra 23844- 00 -OOR AC Line Cord
Zebra SG- TC7X- HSTR2 -03 Hand Strap, 3 pack
Zebra SG -TC7X- STYLUS -03 Stylus with Tether, 3 pack
Zebra BTRY - TC7X- 46MAH -01 Spare Battery Pack
Theramark TTL4010P5 4" X 1" Therm. Trans. Label (2,260 /Roll)
Zebra 03200GS11007 4.3" X 244' Wax Resin Ribbon
TRENDNETTBW -106UB Micro Bluetooth USB Adapter
Device Server
(1) Lantronix UDS -1100 External Device Server (UD1100001 -01)
- Ethernet, Fast Ethernet, RS -232, RS -422, RS -485 Data Link Protocols
- TCP /IP, UDP /IP, ICMP /IP Network/Transport Protocols
- SNMP, Telnet, HTTP Remote Management Protocols
-1 X Serial RS- 232/422/485 - 25 Pin D -Sub (DB -25) Interface
- 1 X Ethernet 10Base- T /100Base -TX - RJ -45 Interface
(1) Null Modem Adapter
- (1) DB -9 (9 -Pin, D -Sub) Male I (1) DB -9 (9 -Pin, D -Sub) Female
- Converts Straight Through Cable into Null Modem Cable
Tyler Page 6
TO: The Honorable Mayor and City Council
FROM: Linda Holt, Finance Director
SUBJECT: Owasso Utility Rate Study
DATE: April 8, 2022
BACKGROUND:
The City provides water, sewer, refuse, recycling, and stormwater management services to
residents. In 2016, the Owasso Public Works Authority (OPWA) implemented a five -year rate plan
to address the following:
• Depletion of the OPWA and Stormwater fund balances
• Rising operational costs
• Funding for necessary capital infrastructure including an upgrade of the
wastewater treatment plant
• Oklahoma Water Resources Board (OWRB) debt requirements
While the fund balance was successfully restored with the implementation of the 2016, five -year
rate plan, pending capital needs and inflationary pressures necessitated the implementation of
an additional five -year plan in 2021 to enable revenues to sustain expected increased costs.
In conjunction with approval of the 2016, five -year rate plan, the City Council requested City
staff perform an annual review of utility rates /revenues to evaluate progress in achieving a
balanced budget to comply with City Ordinance and OWRB debt requirements.
The results of the comprehensive review of utility operations will be presented at the April
Worksession meeting.
TO: The Honorable Mayor and City Council
FROM: Linda Holt
Finance Director
SUBJECT: FY 2022 -2023 Annual Operating Budget
DATE: April 6, 2022
BACKGROUND:
Pursuant to statutory and Charter provisions, an annual operating budget for the General Fund,
Owasso Public Works Authority (OPWA) Fund, Owasso Public Golf Authority (OPGA) Fund and
other funds is being developed, and will be transmitted for City Council review on May 10, 2022.
The proposed budget is scheduled for discussion during the May, and June, Worksession
meetings.
PUBLIC INPUT:
Printed copies of the proposed budget will be made available for public viewing on the City's
website on May 13, 2022.
On May 11, 2022, legal notice of a public hearing will be published in the Owasso Reporter, and
such hearing is planned for May 17, 2022. The public hearing provides opportunity for citizen
comment and questions relating to the proposed budget.
The proposed adoption of the annual operating budget is scheduled for June 21, 2022.
ATTACHMENT:
FY 2022 -2023 Budget Calendar
CITY OF OWASSO
BUDGET CALENDAR
FY 2022 -2023
Due Date
Dec. 31 Directors submit requests for additional personnel to Finance.
Jan. 31 Requests are prioritized and submitted by the Directors for each Department.
February Directors meet with City Manager/Asst. City Manager for justification and
clarification of requested increases.
April 12 Budget calendar is presented at the Council Worksession meeting.
April 20 Revenue estimates are finalized to determine which budget priorities will be
recommended for funding.
May 10 The proposed budget is presented to the City Council at Work Session.
May 11 Publication of notice of public hearing (at least five days prior to hearing *)
May 12 The proposed budget is posted to the City website.
May 17 Public Hearing (no later than June 15 *)
June 21 Budget adoption (at least seven days prior to July 1 *).
July 27 Publication of notice to vendors (no later than July 31 *).
July 31 Budget is filed with the State Auditor (no later than July 31').
Sept. 30 Deadline for submission of vendor invoices for previous fiscal year. Open
purchase orders are closed, and budgetary fiscal year -end fund balances are
determined.
*Deadline set by state statute
TO: The Honorable Mayor and City Council
FROM: H. Dwayne Henderson. P.E.
City Engineer
SUBJECT: State Highway 135 Decommissioning (East 76th Street North) Request from
Oklahoma Department of Transportation (ODOT) and Acceptance of right -of-
way (ROW)
DATE: April 8, 2022
BACKGROUND.
US Highways 169 and 75 have directed drivers through northern Tulsa County for years. US
Highway 75 was designated a highway in the 1920's. The highway paralleled US 66 east of Tulsa
along Admiral, but diverted northward on Mingo Road toward Owasso, where it ended at East
76th Street North. US Highway 75 then moved northward along Owasso's Main Street. As Main
Street ended, the highway moved to Garnett Road and continued north toward Collinsville.
In the late 1930's, US Highway 169 was constructed in northern Tulsa County. The roadway
branched from State Highway I I (Peoria), and headed northeast through the Mohawk Park
Area and eventually turned into East 56th Street North and converged with US Highway 75 at
North Mingo Road. US Highways 169 and 75 shared the same alignment for many years to
Collinsville.
According to the 1965 Oklahoma State Highway Map, US Highway 169 was constructed on the
current alignment in the mid- 1960's and ended at the current 76th Street North interchange. US
Highway 75 (Business Route) assumed the US Highway 169 designation from State Highway 11
to North Mingo Road and extended to the new US Highway 169 alignment.
With US Highway 169 ending at the interchange, ODOT needed to connect to the existing
highway on Main Street. State Highway 135 was conceived to make the connection until US
Highway 169 could be extended northward. Eventually US Highway 75 moved west of Owasso
and US Highway 169 extended north of East 86th Street North, not needing State Highway 135 for
the required contiguous connection.
The current pavement and utilities along East 76th Street North from the east side of Main Street
to the interchange has been maintained by the City of Owasso for many years. The pavement
and utilities east of the interchange were recently updated with new concrete paving, water
and storm sewer lines with local funds and matching funds from the Federal Highway
Administration.
DECOMMISSIONING REQUEST:
ODOT has requested that the City of Owasso allow the decommission of State Highway 135 and
transfer all infrastructure maintenance and right -of -way properties over to the City of Owasso.
These areas include East 76th Street North between the east edge of Main Street to
approximately where the traffic signals are located east of the new Kum N Go. Also included is
the right -of -way east of the east service road in front of Arvest Bank and Quik -Trip.
State Highway 135 Decommissioning (East 76th Street North(
Request from ODOT and Acceptance of ROW
Page 2
The City of Owasso currently, by agreement when the interchange was built, is responsible for
operation and maintenance of East 761h Street North and the drainage structures between the
service roads, however the right -of -way for the interchange will remain ODOT's.
AGREEMENT:
ODOT has prepared an agreement for the decommissioning of State Highway 135. The City
Attorney has reviewed the agreement and has no issues with the request. If approved by both
parties, the agreement would remove State Highway 135 from the State Highway System and
convert segments beginning on East 76th Street North at the intersection of Main Street and
extending east to the intersection of the Northbound off -ramp of US Highway 169 to the
responsibility of the City of Owasso.
PROPOSED ITEM:
An item has been included on the April 12, 2022, Worksession agenda for discussion.
ATTACHMENTS:
Right -of -Way Map
ODOT Agreement
SH -135 (76th Street North) Decommissioning
V = 400 ft
Right -of Way Map
03/27/2022
This map may represents a visual display of related geographic information- Data provided hereon is not guarantee of acutual field conditions -To be sure of complete accuracy, please contact the
responsible staff for most up -to -date information-
AGREEMENT BETWEEN THE
OKLAHOMA DEPARTMENT OF TRANSPORTATION
AND
THE CITY OF OWASSO
This Agreement is made and entered on the day of 2022 by
and between the Oklahoma Department of Transportation (hereinafter referred to as "ODOT "), and
the City of Owasso (hereinafter referred to as "CITY ").
WITNESSETH:
WHEREAS, ODOT is charged under the laws of the State of Oklahoma with the
construction and maintenance of highways which are designated as a part of the State Highway
System; and,
WHEREAS, ODOT and the CITY are authorized to enter into agreements with one another
for joint or cooperative action pursuant to the State Highway Administration Act at Title 69 O.S. §
304.
NOW, THEREFORE, for and in consideration of the mutual needs of the parties, ODOT
and the CITY hereby mutually agree as follows:
SECTION 1: Purpose of the Agreement
This Agreement is to remove State Highway 135 within the corporate limits of the
municipality from the State Highway System and convert segments to municipal streets owned by
the CITY, pursuant to 69 O.S. § 501 (C). The removal of State Highway 135 begins on 70h Street
North at the intersection of Main Street and extends east to the intersection of the Northbound off -
ramp of US -169.
-1-
SECTION 2: Right -of -Way to be Conveyed
ODOT shall determine the specific right -of -way to be conveyed to the CITY and execute a
conveyance of title document for all right -of -way within the corporate limits of the CITY for State
Highway 135 described in Section 1.
SECTION 3: Necessary Improvements by ODOT
ODOT shall make all necessary improvements to the road to meet the minimum design
guidelines as required by 69 0. S. § 501(D) prior to transferring the state highway to the CITY, all as
contemplated in ODOT Project NHPP- 272N(291)PM. The CITY shall be responsible for any
upgrades needed for ADA compliance west of the intersection of SH -135 and W. Frontage Road.
ODOT shall be responsible for any upgrades needed for ADA compliance east of the intersection of
SH -135 and W. Frontage Road.
SECTION 4: Acceptance of Right- of -Wav by CITY
Upon ODOT's completion of all necessary improvements to the subject right -of -way
pursuant to Section 3, the CITY hereby agrees to accept the conveyance of title of all of the described
right -of -way from ODOT to be dedicated and accepted by the CITY in trust for the public use and
enjoyment as a municipal street thereafter maintained by the CITY.
2
SECTION 5: Mutual Agreements
Both parties mutually agree to do all things necessary or legally required to accomplish the
purposes of this Agreement and close the transaction contemplated herein.
IN WITNESS THEREOF, Mayor Bill Bush of the City of Owasso has set his hand and seal
this day of , 2022, and Brian Taylor, Chief Engineer, Oklahoma
Department of Transportation has set his hand and seal this day of
_, 2022,.
CITY OF OWASSO:
Bill Bush, Mayor
ATTEST:
Juliann M. Stevens, City Clerk
(SEAL)
OKLAHOMA DEPARTMENT OF
TRANSPORTATION
Recommended Approval:
Shawn Davis,
Director of Operations
/11» 11phIll03
Brian Taylor,
Chief Engineer
3
Approved as to Form and Legality:
Julie Lombardi, City Attorney
Approved as to Form and Legality:
David Allen Miley
Assistant General Counsel
TO: The Honorable Mayor and Council
FROM: H. Dwayne Henderson, P.E.
City Engineer
SUBJECT: Surface Transportation Project Application for Three (3) Asphalt Overlay
Projects
East l 16th Street North, North Memorial Drive to North Mingo Road
North Garnett Road, East 116th Street North to East 126th Street North
US Highway 169 East Service Road, East 76th Street North to East 86th Street
North
DATE: April 8, 2022
BACKGROUND:
In January 2022, Indian Nations Council of Governments ( INCOG) opened applications for the
FY 2024 Surface Transportation Program (STP) funds. These funds are made available on an
annual basis by the Federal Highway Administration (FHWA), through the Oklahoma Department
of Transportation (ODOT), for the implementation of eligible transportation improvements in the
Tulsa Urbanized Area. Road rehabilitation and reconstruction projects are scored together, with
the higher scoring projects being successfully funded.
This year, INCOG opened the projects up to where multiple projects could be submitted as long
as projects were prioritized based on funding preference. After internal review, staff is proposing
three (3) projects be submitted. Each project has:
Increasing average daily traffic;
Are located adjacent to a project either under construction or soon will be under
construction and will affect the surface of the road due to road construction;
Roads that should be able to withstand waiting 3 -4 years for funding to be approved
and ready to make improvements.
The projects recommended are as follows:
• East 116th Street North, North Memorial Drive to North Mingo Road
• North Garnett Road, East 1 16th Street North to East 126th Street North
• US Highway 169 East Service Road, East 76th Street North to East 86th Street North
East 116th Street North, North Memorial Drive to North Mingo Road is a heavily traveled road.
Recent traffic counts taken showed that 9,830 vehicles per day (VPD) traveled the two -lane
road. The road funnels traffic from US Highway 169 to US Highway 75. The City of Owasso
annexed the road in the mid -70s and has been in our maintenance system since then. The road
has not been resurfaced in many years and is due for a new surface. The project is located at
the west end of the East 116th Street North Vision Project corridor and will need a new surface
even more with the increased traffic this corridor will experience.
North Garnett Road, East 116th Street North to East 1261h Street North is another heavily traveled
two -lane road, registering 7,240 VPD. The project is currently maintained by Tulsa County, but
STP Funding
Page 2
half the road belongs to the City of Owasso byway of annexation. The roadway is the original US
Highway 169 that traversed along North Garnett Road from East 86th Street North to Collinsville,
Oklahoma. Tulsa County has been using the double chip and seal method to resurface the
road; however, the heavy traffic requires the road to be resurfaced every 4 -5 years. The
expansion of the intersection at East 1161h Street North and Garnett Road and the subsequent
mile south of the intersection will allow more traffic to flow in the area. A mill and overlay of the
road section is being proposed to restore the life of the road. Tulsa County has agreed that if the
project is funded they will contribute 50% of the local match for the project.
The US Highway 169 service road between East 76th Street North to East 86th Street North is a busy
roadway that serves many businesses, restaurants, single - family, multi - family and light industrial
users. The road section was constructed by ODOT with the new elevated US Highway 169 in the
1980s. The road has medium duty asphalt, but has had very little maintenance since originally
constructed. Staff registered traffic loads for a week and the traffic averaged 6,280 VPD. The
floodplain on the southern end is not conducive to curb and gutter due to potential flooding,
which is evident with the use of large borrow ditches. For this project, staff proposes to
concentrate on the road surface through this program and continue to maintain the drainage
with local crews. As the interchange at East 761h Street North and US Highway 169 is modified,
there will be an increase of traffic on this section of road as people avoid the construction.
Staff has targeted these sections of roadway for resurfacing in the next few years as part of the
annual street rehabilitation program, but the cost to mill and overlay the roads with 100% City of
Owasso funds would take almost 2 years of funding. Utilizing STP for arterial maintenance has
been staff's focus for the last few years and these three projects are prime candidates for the
funds.
STP FUNDS:
INCOG administers the grant funding and has established a selection process for the distribution
of STP funds. Priority funding is given to projects that meet federal regulations, help advance the
Regional Transportation Plan through safety improvements, and reduce traffic congestion.
Proposed projects are evaluated for eligibility and prioritized based on a 100 -point rating system.
While the two project categories (rehabilitation and capacity improvements) have different
scoring criteria and reconstruction projects score higher, maintenance projects typically cost less
and asking for less funds score higher at the end.
The total funding for projects in the urbanized area is $22,000,000 for the FY 2024 funding year.
$6,000,000 is designated to the Gilcrease Expressway implementation, which leaves $16,000,000
for remaining projects. INCOG solicited for STP funding applications with a submittal deadline of
March 18, 2022. Resolutions are allowed to be submitted following the deadline.
PROPOSED RESOLUTION FOR CONSTRUCTION PHASE:
Similar to the process utilized in obtaining federal funding assistance for previous STP projects,
such as East 86th Street North Pavement Improvements from North 119th East Avenue to North
129th East Avenue that were recently bid by ODOT, a resolution is necessary in order to complete
the application process. The application will request federal funding assistance for the
construction of the roadway improvements. If this project is selected in spring 2024, the funding
for construction will be targeted in FY 2027 or sooner, depending on funding availability.
STP Funding
Page 3
CONCEPTUAL COST SUMMARIES:
The proposed work for these roadway sections is to remove the surface course of pavement
and replace it with a new surface course. The pavement will be restriped. Repairs will be made
as needed and driveway aprons replaced if necessary.
Based on the conceptual cost estimate, the anticipated costs for construction of the proposed
roadway improvements are listed below. Construction administration (testing, inspection and
administration of pay applications) is equal to 10% of the construction fee. Budgeting another
10% for engineering, surveying and geotechnical exploration, the estimated total project cost
for each submitted roadway segment is listed below.
If authorized by the City Council, the City of Owasso will pay for engineering design locally and
request ODOT funding to contribute towards construction. ODOT funding for this project would
be through the Surface Transportation Program, which would fund 80% of eligible construction
costs, while the local government funds 20 %. Based upon this information, the following tables
indicate the project estimates:
East 1 I 61 Street North, North Memorial Drive to North Mingo Road
Project Segment
Estimate
ODOT Portion
City of Owasso
Construction
$621,182
$496,946
$124,236
Administration
$62,118
$49,694
$12,424
Engineering
$62,118
N/A
$62,118
Total Project Cost
$745,418
$546,640
$198,778
North Garnett Road, East 116th Street North to East 126th Street North
Project Segment
Estimate
ODOT Portion
City of Owasso /Tulsa
County
Construction
$668,500
$534,800
$133,700
Administration
$66,850
$53,480
$13,370
Engineering
$66,850
N/A
$66,850
Total Project Cost
$802,200
$588,280
$213,920
US Highway 169 East Service Road, East 76th Street North to East 86th Street North
Project Segment
Estimate
ODOT Portion
City of Owasso
Construction
$825,176
$660,141
$165,035
Administration
$82,518
$66,014
$16,504
Engineering
$82,518
N/A
$82,518
Total Project Cost
$990,212
$956,800
$395,200
Therefore, 100% of the engineering costs will be paid by the City of Owasso. Construction and
construction administrative services will be shared with ODOT paying for 80% of these costs and
the City of Owasso paying 20% of these costs. The total project cost to ODOT will be 73 %, which
STP Funding
Page 4
will be paid with STP funds. Local project costs for the overall project will be 27 %. Reducing the
STP request to 73% will allow an extra point in the scoring criteria.
PROPOSED ACTION:
Staff intends to seek City Council consideration and action during the April 19, 2022, City Council
meeting for resolution(s) requesting ODOT to consider the construction phase of (in priority of
order) the (1) East 116th Street North, North Memorial Drive to North Mingo Road; (2) North
Garnett Road, East 116th Street North to East 126th Street North; and (3) US Highway 169 East
Service Road, East 76th Street North to East 86th Street North rehabilitation projects as candidates
for federal funding assistance through the Surface Transportation Program.
ATTACHMENTS:
Resolutions — Draft
Location Maps
CITY OF OWASSO, OKLAHOMA
RESOLUTION NO.2022 -XX
A RESOLUTION OF THE CITY COUNCIL OF THE CITY OF OWASSO, OKLAHOMA, AUTHORIZING
AN APPLICATION FOR FUNDING BETWEEN THE CITY OF OWASSO AND THE OKLAHOMA
DEPARTMENT OF TRANSPORTATION FOR THE 116th STREET NORTH, MEMORIAL DRIVE TO MINGO
ROAD RESURFACING PROJECT
WHEREAS, Surface Transportation Program Urbanized Area funds have been made available for
transportation improvements within the Tulsa Transportation Management Area; and
WHEREAS, The City of Owasso has selected a project described as follows: The 116th STREET
NORTH, MEMORIAL DRIVE TO MINGO, Resurfacing Project, Owasso, Oklahoma; and
WHEREAS, the selected project is consistent with the local comprehensive plan; including
applicable Major Street and Highway Plan Element, and the Regional Transportation Plan; and
WHEREAS, the engineer's preliminary estimate of cost is $745,418, and Federal participation under
the terms of the Surface Transportation Block Grant Program Urbanized Area funds are hereby requested
for funding of 73 percent of the project cost ($546,640); and
WHEREAS, the City of Owasso proposes to utilize the 1/2 Penny Sales Tax Fund and the Capital
Improvements Fund for the balance of the project costs; and
WHEREAS, the City of Owasso agrees to provide for satisfactory maintenance after completion,
and to furnish the necessary right -of -way clear and unobstructed; and
WHEREAS, the City of Owasso has required matching funds available and further agrees to
deposit with the Oklahoma Department of Transportation said matching funds within the time frame as
required by the ODOT.
NOW, THEREFORE, BE IT RESOLVED BY THE CITY COUNCIL OF THE CITY OF OWASSO, that, to -wit
The Indian Nations Council of Governments is hereby requested to program this project into the
Transportation Improvement Program for the Tulsa Transportation Management Area, should the project
be selected for funding; and
That upon inclusion in the Transportation Improvement Program, the Oklahoma Transportation
Commission is hereby requested to concur in the programming and selection of this project and to
submit the same to the Federal Highway Administration for its approval.
The Mayor is authorized and directed to execute the above described agreement on behalf of the City
of OWASSO.
PASSED AND APPROVED this 19th day of April, 2022.
Bill Bush, Mayor
ATTEST:
Juliann M. Stevens, City Clerk
APPROVED AS TO FORM:
Julie Lombardi, City Attorney
East 116th Street North STP Project
Project Location Map
03/27/2022
CITY OF OWASSO, OKLAHOMA
RESOLUTION NO. 2022 -XX
A RESOLUTION OF THE CITY COUNCIL OF THE CITY OF OWASSO, OKLAHOMA, AUTHORIZING
AN APPLICATION FOR FUNDING BETWEEN THE CITY OF OWASSO AND THE OKLAHOMA
DEPARTMENT OF TRANSPORTATION FOR THE NORTH GARNETT, EAST 116th STREET NORTH to EAST
126th STREET NORTH ROAD RESURFACING PROJECT
WHEREAS, Surface Transportation Program Urbanized Area funds have been made available for
transportation improvements within the Tulsa Transportation Management Area; and
WHEREAS, The City of Owasso has selected a project described as follows: NORTH GARNETT,
EAST 116th STREET NORTH to EAST 126th STREET NORTH ROAD RESURFACING PROJECT; and
WHEREAS, the selected project is consistent with the local comprehensive plan, including
applicable Major Street and Highway Plan Element, and the Regional Transportation Plan; and
WHEREAS, the engineer's preliminary estimate of cost is $802,200, and Federal participation under
the terms of the Surface Transportation Block Grant Program Urbanized Area funds are hereby requested
for funding of 73 percent of the project cost ($588,280); and
WHEREAS, the City of Owasso proposes to utilize the 1/2 Penny Sales Tax Fund and the Capital
Improvements Fund for the balance of the project costs; and
WHEREAS, the City of Owasso agrees to provide for satisfactory maintenance after completion,
and to furnish the necessary right -of -way clear and unobstructed; and
WHEREAS, the City of Owasso has required matching funds available and further agrees to
deposit with the Oklahoma Department of Transportation said matching funds within the time frame as
required by the ODOT.
NOW, THEREFORE, BE IT RESOLVED BY THE CITY COUNCIL OF THE CITY OF OWASSO, that, to -wit
The Indian Nations Council of Governments is hereby requested to program this project into the
Transportation Improvement Program for the Tulsa Transportation Management Area, should the project
be selected for funding; and
That upon inclusion in the Transportation Improvement Program, the Oklahoma Transportation
Commission is hereby requested to concur in the programming and selection of this project and to
submit the some to the Federal Highway Administration for its approval.
The Mayor is authorized and directed to execute the above described agreement on behalf of the City
of OWASSO.
PASSED AND APPROVED this 19{h day of April, 2022.
Bill Bush, Mayor
ATTEST:
Juliann M. Stevens, City Clerk
APPROVED AS TO FORM:
Julie Lombardi, City Attorney
North Garnett Road STP Project
1" = 1200 ft
Project Location Map
03/27/2022
This map may represents a visual display of related geographic information. Data provided here on is not guarantee of acutual field conditions. To be sure of complete accuracy, please contact the
responsible staff for most up-to -date information.
CITY OF OWASSO, OKLAHOMA
RESOLUTION NO. 2022 -XX
A RESOLUTION OF THE CITY COUNCIL OF THE CITY OF OWASSO, OKLAHOMA, AUTHORIZING
AN APPLICATION FOR FUNDING BETWEEN THE CITY OF OWASSO AND THE OKLAHOMA
DEPARTMENT OF TRANSPORTATION FOR THE US HWY 169 EAST SERVICE ROAD, EAST 76TH STREET
NORTH TO EAST 86TH STREET NORTH ROAD RESURFACING PROJECT
WHEREAS, Surface Transportation Program Urbanized Area funds have been made available for
transportation improvements within the Tulsa Transportation Management Area; and
WHEREAS, The City of Owasso has selected a project described as follows: US HWY 169 EAST
SERVICE ROAD, EAST 76TH STREET NORTH TO EAST 86TH STREET NORTH ROAD RESURFACING PROJECT;
and
WHEREAS, the selected project is consistent with the local comprehensive plan, including
applicable Major Street and Highway Plan Element, and the Regional Transportation Plan; and
WHEREAS, the engineer's preliminary estimate of cost is $990,211, and Federal participation under
the terms of the Surface Transportation Block Grant Program Urbanized Area funds are hereby requested
for funding of 73 percent of the project cost ($726,155); and
WHEREAS, the City of Owasso proposes to utilize the 1/2 Penny Sales Tax Fund and the Capital
Improvements Fund for the balance of the project costs; and
WHEREAS, the City of Owasso agrees to provide for satisfactory maintenance after completion,
and to furnish the necessary right -of -way clear and unobstructed; and
WHEREAS, the City of Owasso has required matching funds available and further agrees to
deposit with the Oklahoma Department of Transportation said matching funds within the time frame as
required by the ODOT.
NOW, THEREFORE, BE IT RESOLVED BY THE CITY COUNCIL OF THE CITY OF OWASSO, that, to -wit
The Indian Nations Council of Governments is hereby requested to program this project into the
Transportation Improvement Program for the Tulsa Transportation Management Area, should the project
be selected for funding; and
That upon inclusion in the Transportation Improvement Program, the Oklahoma Transportation
Commission is hereby requested to concur in the programming and selection of this project and to
submit the same to the Federal Highway Administration for its approval.
The Mayor is authorized and directed to execute the above described agreement on behalf of the City
of OWASSO.
PASSED AND APPROVED this 19th day of April, 2022.
Bill Bush, Mayor
ATTEST:
Juliann M. Stevens, City Clerk
APPROVED AS TO FORM:
Julie Lombardi, City Attorney
US HWY 169 - East Service Road STP Project
1" = 1200 ft
Project Location Map
03/27/2022
This map may represents a visual display of related geographic information. Data provided hereon is not guarantee of acutual field conditions: To be sure of complete accuracy, please contact the
responsible staff for most up-to -date information.