Vernon City Council
September 19, 2023

________________________
March 2013

AFFIDAVIT OF NON-COLLUSION BY CONTRACTOR

STATE OF CALIFORNIA )
) ss

COUNTY OF LOS ANGELES )
_______________________________________________________________, being first duly sworn deposes and says that he/she is ______________________________________________________________________ (Insert "Sole Owner", "Partner", "President, "Secretary", or other proper title) of______________________________________________________________________________________ (Insert name of bidder)
who submits herewith to the City of Vernon a bid/proposal; That all statements of fact in such bid/proposal are true; That such bid/proposal was not made in the interest of or on behalf of any undisclosed person, partnership, company, association, organization or corporation; That such bid/proposal is genuine and not collusive or sham; That said bidder has not, directly or indirectly by agreement, communication or conference with anyone attempted to induce action prejudicial to the interest of the City of Vernon, or of any other bidder or anyone else interested in the proposed contract; and further That prior to the public opening and reading of bids/proposals, said bidder:
a. Did not directly or indirectly, induce or solicit anyone else to submit a false or sham bid/proposal;
b. Did not directly or indirectly, collude, conspire, connive or agree with anyone else that said bidder or anyone else would submit a false or sham bid/proposal, or that anyone should refrain from bidding or withdraw his/her bid/proposal;
c. Did not, in any manner, directly or indirectly seek by agreement, communication or conference with anyone to raise or fix the bid/proposal price of said bidder or of anyone else, or to raise or fix any overhead, profit or cost element of his/her bid/proposal price, or of that of anyone else; d. Did not, directly or indirectly, submit his/her bid/proposal price or any breakdown thereof, or the contents thereof, or divulge information or data relative thereto, to any corporation, partnership, company, association, organization, bid depository, or to any member or agent thereof, or to any individual or group of individuals, except the City of Vernon, or to any person or persons who have a partnership or other financial interest with said bidder in his/her business.

I certify under penalty of perjury that the above information is correct By:______________________________________ Title:________________________________ Date:____________________________________
Ron A. Anderson
Chief Sales Officer
CentralSquare Technologies, LLC
Chief Sales Officer
DocuSign Envelope ID: C4504F08-DB59-468F-98F8-6A29D062E450 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
Computer Aided Dispatch (CAD)
General
ID Requirement Yes Future Modify No Comments
CA1 The system should allow authorized users to design
and enforce an agency-wide standard CAD window
layout to ensure consistency among workstations,
but also to allow users flexibility in configuring their own CAD displays as allowed by the agency.

X
CA2 The system should include a minimum of the
following for CAD window layout options: window
sizes and arrangements, column options, widths,
font types, font sizes, and default list-view filters.

X
CA3 The system should allow customized CAD windows
to retain a user or agency’s preference for all layout
options.

X
CA4 The system should support both command line and
point-and-click entry for all CAD commands. X
CA5 The system should support drag-and-drop issuance
of CAD commands. X
CA6 The system should allow authorized users to
maintain lists of beats and beat plans. X
CA7 The system should allow authorized users to
maintain a list of bulletin types in addition to BOLOs
and special instructions.

X
CA8 The system should allow authorized users to
maintain a list of CFS dispositions. X
CA9 The system should allow multiple dispositions to be specified for a single CFS. X
CA10 The system should allow calls for service to be set up to require dispositions before they can be closed. X CA11 The system should allow authorized users to
maintain a list of CFS link types (for example,
Duplicate of and Related to) to tie multiple calls into the same physical event.

X
Computer Aided Dispatch Page 1 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
CA12 The system should allow authorized users to
maintain a list of CFS list filters (to organize
information on the primary CFS windows).

X
CA13 The system should allow authorized users to
maintain CFS priority levels. X
CA14 The system should include inactivity alarm and unit status alarm values, along with the colors, for each
CFS priority level.

X
CA15 The system should allow authorized users to
maintain a list of CFS response codes. X
CA16 The system should allow users to maintain a list of recurring scheduled calls for service, such as pager
or siren tests.

X
CA17 The system should allow authorized users to
maintain a list of fire and/or EMS stations. X
CA18 The system should allow authorized users to
maintain a list of CAD terminals. X
CA19 The system should allow authorized users to
maintain a list of dispatch timers used to alert calltakers and dispatchers to calls waiting to be dispatched.

X
CA20 The system should allow authorized users to set up additional web sites to open within CAD windows,
without the standard browser controls or navigation
features.

X
CA21 The system should support Caller Location Query,
CLQ, functionality. X
CA22 System should allow for bulletin records to be linked to the master name index. X
CA23 System should allow for bulletin records to be linked to the master vehicle index. X
CA24 System should allow for bulletin records to be linked to the master address index. X
Calls for Service
ID Requirement Yes Future Modify No Comments
CB1 The system should track reporter/complainant data,
including name, address, and call-back number. X
Computer Aided Dispatch Page 2 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
CB2 The system should allow unlimited narrative details to be added to a CFS. X
CB3 The system should provide automatic date/time
stamping and user ID tracking for all call-taker and
dispatcher actions to track CFS activity, unit activity, radio log, etc.

X
CB4 The system should allow authorized users to
manage check-in times for units based on CFS type.

When a unit exceeds the allotted time, the system
should provide visible and audible warnings to the
call-taker or dispatcher.

X
CB5 The system should include an override/reset feature for the unit check-in time warnings. X
CB6 The system should allow for filtering subsets or
sorting the active or waiting calls within the CFS
control panel.

X
CB7 The system should display key information about
each CFS, such as incident number, call for service
type, priority, status, assigned units, and incident
address within the CFS control panel.

X
CB8 The system should allow the information displayed
for a CFS within the CFS control panel to be
configured per user or per agency.

X
CB9 The system should allow authorized users to
manage dispatch timers based on CFS type and
priority. The system should provide a visible and/or
audible warning, alerting the call-taker or dispatcher
that too much time has elapsed without assigning a
unit(s) to the CFS.

X
CB10 The system should make narrative details available to all stations in real time. X
CB11 The system should clearly display the SOP to the
call-taker and dispatcher when a CFS is created with
an incident code that has an SOP.

X
CB12 The system should be able to display the active and waiting calls for service through the CFS control
panel.

X
Computer Aided Dispatch Page 3 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
CB13 The system should allow the call-taker and
dispatcher to enter free-text log entries for a CFS. X
CB14 The system should auto-save narrative details after a specified period of inactivity on a CFS. X
CB15 The system should allow a CFS to be created with a single click or keystroke from either the CAD product
or from the mapping product.

X
CB16 The system should be able to immediately dispatch
a new CFS without any mandatory fields. X
CB17 The system should allow users to create traffic stop calls for service, with fields for entering key traffic stop data, including location and license plate
number, in the order specified by the agency.

X
CB18 The system should allow the dispatch display to
provide access to all CFS information, including
incident type, nature of call, address, reporter and
complainant names, and narrative.

X
CB19 The system should provide duplicate CFS
suggestions based on address location. X
CB20 The system should, after a dispatcher verifies a
duplicated call, link the duplicate to the original call to provide access to the additional data.

X
CB21 The system should allow calls for service to be
manually linked for any agency-defined reason. X
CB22 The system should allow a "use caution" flag to be placed on any CFS. X
CB23 The system should allow a CFS to be modified with
priority modifiers such as Routine, Just Occurred,
and In Progress throughout the life of the call. X
CB24 The system should allow calls for service to be
cleared at any time, including prior to dispatch. X
CB25 The system should allow a call-taker and/or
dispatcher to specify an unlimited number
dispositions or reasons for clearing a CFS.

X
Computer Aided Dispatch Page 4 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
CB26 The system should allow authorized users to view
cleared calls for service but prevent unauthorized
users from making any modifications to these
cleared calls.

X
CB27 The system should allow reactivation of recently
cleared calls for service and should also allow
additional activity and dispatching of units to the
original CFS.

X
CB28 The system should be able to generate a sequential reference number for a CFS for each
jurisdiction/responding agency.

X
CB29 The system should provide a list of all state/NCIC queries run and associated returns. This list should
be filtered by date, query type, user, and/or terminal.

X
CB30 The system should allow users to easily attach a
state/NCIC query to a call for service so that the
query and all returns are linked to the call.

X
CB31 The system should allow NCIC queries to run
automatically when a vehicle or name is added to a
CFS.

X
CB32 The system should allow all information captured
within a CFS to be transferred to and available via
the resulting Case report.

X
CB33 The system should allow authorized users to create unlimited custom form templates which are used to
associate agency-specified data with individual calls
for service.

X
CB34 The system should allow users with access to calls for service to use the custom forms to enter and
maintain the associated data.

X
Incident Codes
ID Requirement Yes Future Modify No Comments
CC1 The system should allow authorized users to
maintain a list of CFS types (incident codes),
including default priority levels and default modifiers. X Computer Aided Dispatch Page 5 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
CC2 The system should allow authorized users to
determine if incident reports are required for given
incident codes or if incident reports will be
automatically created in CAD.

X
CC3 The system should allow users to enter an unlimited number of incident codes for a CFS. X
CC4 The system should allow incident codes to be
associated with specific N-DEx codes for state and
federal reporting.

X
CC5 The system should allow map icons to be assigned
to each incident code for display of that incident/CFS
on the map.

X
CC6 The system should allow incident codes to be
changed at any time during the CFS. X
CC7 The system should allow incident codes to be
defined by the agency such that they will trigger the
appropriate response assistance from 911 EMD
systems, if so configured.

X
Unit Management
ID Requirement Yes Future Modify No Comments
CD1 The system should allow authorized users to
maintain lists of unit information such as unit alarm
times, unit details, unit list filters, unit locations, unit shifts, unit specialties, unit statuses, unit types, and the units themselves.

X
CD2 The system should allow authorized users to
determine the length of unit alarm times and the
frequency of the alarm tone.

X
CD3 The system should support filtering on the CAD
window to select the units which meet specified
criteria (has defibrillator, etc.).

X
CD4 The system should allow unit drill-down. That is, the user should be able to select a unit and use links to
locate information about the personnel, vehicle, and
equipment associated with that unit and jump to
those records (if authorized).

X
Computer Aided Dispatch Page 6 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
CD5 The system should have one or more CAD unit
control windows which allow filtering and sorting
units by key data.

X
CD6 The system should include key information about
each unit in the CAD unit control window, such as
unit type, call sign, details, status, incident
assignment, beat, and location, configurable per
user or per agency.

X
CD7 The system should allow a call-taker or dispatcher to view a list of active and waiting calls for service from the CAD control unit window and to dispatch the
units to calls for service.

X
CD8 The system should allow a call-taker or dispatcher to update unit information such as status, location, and
details from the CAD control unit window. X
CD9 The system should allow call-takers and dispatchers to dispatch units from a displayed list of available
units in the CFS control panel.

X
CD10 The system should allow call-takers and dispatchers to issue unit commands directly from the CFS
window.

X
CD11 The system should support pre-built shift rosters and allow call-takers or dispatchers to place multiple
units on shift with a single command.

X
CD12 The system should be able to re-assign a unit from one CFS to another with a single command and
stack the original CFS against the re-routed unit. X
CD13 The system should provide unlimited unit stacking
for calls for service. X
CD14 The system should allow a re-assigned unit to be
sent back to the original CFS when the unit is
cleared.

X
CD15 The system should allow one unit to be exchanged
with another, automatically recording in the log that
the first unit was initially dispatched and then
switched with the second unit.

X
Computer Aided Dispatch Page 7 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
CD16 The system should be able to group units so that
subsequent commands apply to all units in the
group.

X
CD17 The system should support the use of cross-staffed units. X
CD18 The system should allow the call-taker or dispatcher to enter free-text messages from an officer in the
CFS log.

X
CD19 The system should allow the CFS log to be queried
by unit to generate a record of an individual officer's activity for a given time period.

X
Addresses and GIS
ID Requirement Yes Future Modify No Comments
CE1 The system should display a list of potential matches as characters for addresses are typed into the CFS
address field. These potential matches should be
reduced as additional characters are typed until only
the matching address(es) is/are listed.

X
CE2 The system should allow users to suggest adding
new addresses when existing address information
does not exist.

X
CE3 The system should allow the call-taker to select a
suggested match at any time to auto-populate the
address field.

X
CE4 The system should, when possible, auto-populate
the city, state and zip code based on the street
address entered (if the address is already in the
master address database).

X
CE5 The system should allow intersections to be entered as CFS addresses. X
CE6 The system should allow mile markers to be entered
as CFS addresses. X
CE7 The system should allow the assignment of common
address names such as "Vernon Street" to actual
addresses, allowing call-takers and dispatchers to
enter either one in a CFS.

X
Computer Aided Dispatch Page 8 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
CE8 The system should allow the assignment of street
name aliases. For example, "LB" might be assigned
as a street alias for "Leonis Boulevard." Call-takers
and dispatchers may choose to enter either the
address or the alias.

X
CE9 The system should automatically alert the call-taker and/or dispatcher of a possible duplicate call based
on address data.

X
CE10 The system should be integrated with GIS. Please
describe the GIS integration. X
CE11 The system should support specifying and autopopulating the beat and/or zone for a CFS. X Command Line
ID Requirement Yes Future Modify No Comments
CF1 The system should allow authorized users to
maintain a list of CAD commands, including the
actions which the system performs within each
command.

X
CF2 The system should allow call-takers and dispatchers to enter commands via the command line using a
few keystrokes.

X
CF3 The system should allow authorized users to create
agency-specific commands for the command line. X
CF4 The system should allow the command line to use
natural language rather than cryptic key codes or a
specific information order.

X
CF5 The system should use business logic to dynamically display only the necessary fields for the selected
command in the command line.

X
CF6 The system should allow authorized users to arrange traffic stop fields in a CAD command to match the
order they are called out to dispatchers at the
agency.

X
CF7 The system should default the CFS number from the
current CFS to the command line embedded in the
CFS detail screen.

X
Computer Aided Dispatch Page 9 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
CF8 The system should support multiple instances of the command line on multiple displays from the same
workstation.

X
CF9 The system should allow users to run common
state/NCIC queries directly from the command line. X
Call-taker/Dispatcher
ID Requirement Yes Future Modify No Comments
CG1 The system should allow authorized users to take
over any call-taker or dispatcher position. X
CG2 The system should be able to be set up for a calltaker and/or dispatcher workflow, or for one user to fill both roles using the same windows.

X
CG3 The system should support either local or remote calltaker and/or dispatcher positions. X CG4 The system should support an unlimited number of
call-taker and/or dispatcher positions. X
CG5 The system should allow multiple call-takers or
dispatchers or mobile users to enter data on the
same CFS simultaneously.

X
CG6 The system should allow for units to be dispatched
simultaneously with call-taking activities. X
CG7 The system should make information immediately
available to all stations as soon as any dispatcher,
call-taker, or mobile unit updates a call. A CFS
update indicator (for example, flashing text) should
be visible to all stations.

X
CG8 The system should make all functions available from the call-taker and dispatcher positions for officerinitiated incidents (quick calls) and traffic stops. X Relationships
ID Requirement Yes Future Modify No Comments
CH1 The system should allow users to add unlimited
involved persons to a CFS. X
Computer Aided Dispatch Page 10 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
CH2 The system should allow authorized users to set up
an unlimited number of custom, configurable
relationship types.

X
CH3 The system should allow authorized users to extend
the list of CFS relationship types to include such
types as arrestee, cited, reporter, driver of vehicle,
and passenger.

X
CH4 The system should automatically check all involved
persons’ names against the master name index. X
CH5 The system should allow for the entry of anonymous
reporters such as concerned citizen or anonymous
female without creating a master name record for
these entries.

X
CH6 The system should automatically transfer all names, including any involved persons, from the CFS record
to any associated case reports.

X
Service Vehicles
ID Requirement Yes Future Modify No Comments
CI1 The system should include a list of service vehicle providers that need to maintain a rotation schedule,
such as wreckers or private ambulances.

X
CI2 The system should automatically position the second company in the first position after the first company
has been selected.

X
CI3 The system should allow the user to dispatch the
next company, when unable to reach the first
company in line, without manually moving the first
company to the bottom of the rotation sequence.

X
CI4 The system should allow the user to override the
rotation in the event a specific provider is requested. X CI5 The system should track attempts to contact service vehicle providers and the results of each attempt. X
Tow Calls
ID Requirement Yes Future Modify No Comments
Computer Aided Dispatch Page 11 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
CJ1 The system should allow authorized users to
maintain lists of tow call information such as tow call statuses, tow operators, and tow operator schedules. X
CJ2 The system should provide a means for recording
when a vehicle needs to be towed, including vehicle
identifying data, vehicle location, comments, and
attempts to contact service vehicles.

X
CJ3 The system should allow vehicle data from a call for service to automatically populate the tow call. X
CJ4 The system should ensure that tow calls are
recorded as links for the related master vehicle
records.

X
CJ5 The system should integrate the towing expenses
billing with the financial product provided by the
same vendor.

X
CJ6 The system should allow authorized users to create
unlimited custom form templates which are used to
associate agency-specified data with individual tow
calls.

X
CJ7 The system should allow users with access to tow
calls to use the custom forms to enter and maintain
the associated data.

X
Unit Recommendations
ID Requirement Yes Future Modify No Comments
CK1 The system should allow authorized users to
maintain a list of run cards. X
CK2 The system should allow agency-configurable run
cards to define the required responders for each
incident code.

X
CK3 The system should allow authorized users to define
run cards by particular map layer(s) or by individual
addresses.

X
CK4 The system should allow run cards to be applied to a single incident code or to multiple incident codes. X
Computer Aided Dispatch Page 12 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
CK5 The system should allow run cards to be based
on/include the following additional criteria: day, time of day, number and type of units.

X
CK6 The system should allow units which match up with
run card criteria to be differentiated with a tiebreaker (such as which one has been inactive for the longest
period).

X
CK7 The system should prioritize units for
recommendation based on factors including the
following:
- Department/jurisdiction
- Specialties, training skills, and equipment
- Closest path/shortest routing time to incident
location
- Time since last CFS assignment
- Unit status
X
CK8 The system should allow the dispatcher to assign a
recommended unit, assign all recommended units,
or expand the list of units to view more
recommendations.

X
CK9 The system should support the use of cascading unit recommendations. X
Vehicles
ID Requirement Yes Future Modify No Comments
CL1 The system should store all vehicle information
which is added to a CFS entry in the master vehicle
index.

X
CL2 The system should allow multiple vehicles to be
added to a CFS. X
CL3 The system should include the following vehicle
relationship types: traffic stops or traffic accidents, towed vehicles, abandoned vehicles, and unlimited
agency-defined relationships types.

X
CL4 The system should automatically transfer vehicle
information from a CFS to any associated case
reports.

X
Computer Aided Dispatch Page 13 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
Hazards and Alerts
ID Requirement Yes Future Modify No Comments
CM1 The system should visibly notify call-takers,
dispatchers and officers of any alert information for
names, addresses, and vehicles involved in a CFS.

X
CM2 The system should integrate hazards and alerts
between all products so that alerts entered in one
area are available in all others (for example, a
dispatcher is alerted in CAD that a complainant has
an outstanding warrant in RMS).

X
CM3 The system should allow unlimited narrative text for an alert. X
CM4 The system should include both urgent and nonurgent alerts. X CM5 The system should allow alerts to be deactivated, if no longer relevant, but still maintained in the alert
history.

X
CM6 The system should allow users to set an expiration
date for each alert. Expired alerts should be retained
but clearly marked as expired and non-urgent.

X
CM7 The system should display alerts triggered from any non-CAD area of the system to dispatchers in realtime based on the people involved, addresses, vehicles, etc. For example, any alerts for warrant hits or sex offender status should display when a
reporting party name is entered in CAD.

X
CM8 The system should allow authorized users to create
other name alert types, such as medical alerts,
protection orders, etc.

X
CM9 The system should directly link alerts (such as
warrant hits) to the triggering information. X
CM10 The system should alert the call-taker and dispatcher and/or officer if hazardous material is stored at a
site, including material name, amount, location on
site, and cutoff information (if the data is available on the master address record).

X
CM11 The system should link hazardous material alerts to the relevant text from the Hazmat Guide stored in
the system.

X
Computer Aided Dispatch Page 14 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
CM12 The system should alert the call-taker and dispatcher and/or officer to protection system details for an
address, such as fire alarm panel locations and
sprinkler system details (if the data is available on
the master address record).

X
CM13 The system should be able to alert the call-taker and dispatcher and/or officer to water supply details for
an address (if the data is available on the master
address record).

X
CM14 The system should alert the call-taker and dispatcher and/or officer to any officer safety warnings for an
address such as unlocked firearms, and vicious dogs
(if the data is available on the master address
record).

X
CM15 The system should allow authorized users to create other address alerts such as known crash pads, drug
sites, etc.

X
CM16 The system should allow authorized user to create
agency-defined vehicle warnings. X
CM17 The system should alert the call-taker and dispatcher and/or officer to any vehicle warnings. X
CM18 The system should allow name, address, and vehicle alerts to be created during the call-taking and/or
dispatch process.

X
CM19 The system should provide a means of granting or
denying users permission to view or create specific
name, address, and vehicle alert types so that these
alerts can be used to store data such as confidential
investigative information.

X
Call Scheduling
ID Requirement Yes Future Modify No Comments
CN1 The system should allow scheduling calls for future dispatch to help manage special events such as
parades, festivals, funeral escorts, and prisoner
transport.

X
CN2 The system should automatically create a CFS when
the scheduled activity occurs. X
Computer Aided Dispatch Page 15 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
CN3 The system should allow scheduled calls to be set
up to notify call-takers and dispatchers in advance of
the actual event.

X
CN4 The system should allow a user, when scheduling a
CFS, to specify which terminal will handle the CFS. X
CN5 The system should remind a user who schedules a
CFS to check the CFS date when calls are
scheduled for dates that are not in the near future.

X
CN6 The system should allow scheduled calls to include
unlimited narrative details. X
CN7 The system should support location overrides for
scheduled calls. X
CN8 The system should be able to display a list of
scheduled calls, either future or past. X
CN9 The system should allow a CFS to be scheduled to
recur according to a number of different times (for
example, daily, the first Friday of the month, every
other month, etc.)
X
External Messaging
ID Requirement Yes Future Modify No Comments
CO1 The system should include the ability to send
messages externally via smtp and sms. X
CO2 The system should support rip and run messaging
via email or fax for communication with external
agencies.

X
CO3 The system should allow authorized users to
maintain lists of paging groups and paging message
types.

X
CO4 The system should send automatic pages based on
incident types. X
CO5 The system should be able to notify users or groups via smtp or sms when specified calls for service are
received.

X
Internal Messaging
ID Requirement Yes Future Modify No Comments
Computer Aided Dispatch Page 16 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
CP1 The system should allow instant messages to be
sent to multiple recipients, such as via a public
message room accessible by all on-duty call-takers,
dispatchers and officers.

X
CP2 The system should allow instant messages to be
sent to specified user(s). X
CP3 The system should provide visible and/or audible
alerts or to bring the alert to the front of all other
open windows when the user receives an instant
message.

X
CP4 The system should allow for the inclusion of a
number of different tones to designate different types
of audible alerts.

X
CP5 The system should include an e-mail function that is internal to the system, allowing users to send e-mailstyle messages to other users on the system.

X
CP6 The system should allow e-mail-style messages to
include links to records within the system. X
CP7 The system should allow a single e-mail-style
message to be sent to one or more users. X
CP8 The system should allow users to store or delete
received e-mail-style messages. X
CP9 The system should log all sent e-mail-style
messages.

X
CP10 The system should provide a note pad function that allows call-takers and dispatchers to type in
unlimited text and store the text within the system.

X
CP11 The system should stamp note pad entries with the
date and time and user who created them. X
CP12 The system should allow note pad entries to be set to automatically expire. X
CP13 The system should be able to notify users or user
groups via internal system messaging, or e-mail
when specified calls for service are received.

X
CP14 The system should allow for call-takers and/or
dispatchers to notify users and/or user groups of a
CFS during any point of the call-taking or dispatching
process.

X
Computer Aided Dispatch Page 17 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
CP15 The system should allow bulletins such as BOLOs
and special instructions to be issued to groups of
officers based on type, jurisdiction, beat, etc.

X
CP16 The system should immediately make BOLOs
available to the system’s mobile units. X
CP17 The system should allow BOLOs to have files
attached to them via upload or scanner. X
Alarm Billing
ID Requirement Yes Future Modify No Comments
CQ1 The system should allow an alarm billing record to
be created from an incident code with a false alarm
disposition when the CFS is completed.

X
CQ2 The system should integrate the alarm billing with
the financial product provided by the same vendor. X
CQ3 The system should be able to automatically create
invoices to bill persons or businesses for false
alarms.

X
CQ4 The system should allow users to manually select
charges for alarm billing. X
CQ5 The system should allow users to save, print or
email an alarm billing record directly from the record
window.

X
CQ6 The system should allow users to sort and filter
alarm billing records within the list-view window. X
CQ7 The system should allow users to save, print or
email a summary list of alarm billing records from the
list-view window.

X
CQ8 The system should allow authorized users to create
unlimited custom form templates which are used to
associate agency-specified data with alarm billing
records.

X
CQ9 The system should allow users with access to alarm
billing records to use the custom forms to enter and
maintain the associated data.

X
CAD Reporting
ID Requirement Yes Future Modify No Comments
Computer Aided Dispatch Page 18 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
CR1 The system should provide a report generator for
building custom statistical and analytical reports from CAD data. The report generator should be provided
by the same vendor and should not be a third-party
application.

X
CR2 The system should restrict access to the report
generator and individual report templates by user or
user group.

X
CR3 The system should not allow a user who does not
have access to particular data via the application
user interface to gain access to that data via the
report generator.

X
CR4 The system should allow the creator of the report
template to build reports for any data entered into the CAD product.

X
CR5 The report generator should allow the creator of the report template to control layout and formatting
options for each CAD report template. This includes
such options as field arrangements, column widths,
label text, font sizes, and line spacing.

X
CR6 The report generator should allow the creator of
each CAD report template to choose which users
can access and/or run the report and/or modify the
report template.

X
CR7 The report generator should support the use of
aggregate (math) functions including Sum, Average,
Count, Count Blank, Minimum, and Maximum. X
CR8 The report generator should allow data to be
grouped or sorted by any data element. X
CR9 The report generator should allow multiple data
filters to be applied using "and/or" logic. X
CR10 The report generator should allow CAD reports to be saved (as PDF, .XLS, or .CSV), printed, or emailed
directly from the report.

X
CR11 The report generator should allow CAD report
templates to be saved and modified at a later time. X
Computer Aided Dispatch Page 19 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
CR12 The report generator should support adding the CAD reports to user's dashboards. X
CR13 The report generator should allow recurring CAD
reports to be scheduled and automatically uploaded
to a file-system or e-mailed to specified users on
certain days and times.

X
CR14 The report generator should support ad-hoc queries. X CR15 The report generator should support creation of CAD reports such as the following:
- Area/section activity
- CFS priority analysis
- Daily or shift-based CFS summary
- CFS by month, by day of week, by hour of day
- CFS by nature of call
- CFS by source, by disposition
- CFS by station, by call-taker or dispatcher
- Response time analysis by area, section, priority
- Summary of activity for an address or business
name
- Unit assignments
X
CR16 The system should be able to provide an officer
activity report that includes felony and misdemeanor
arrests, citations, vehicle checks, pedestrian checks,
and patrol checks.

X
ANI/ALI Interface
ID Requirement Yes Future Modify No Comments
CS1 The system should include an interface to the 911
service provider. X
CS2 The system should receive the raw spill data from
the 911 service and import it into the CFS via a serial or IP connection.

X
CS3 The system should intelligently handle ANI/ALI
rebids through the interface. X
Computer Aided Dispatch Page 20 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
CS4 The system should allow E911 calls, upon being
answered, to automatically generate and populate
the CFS entry window with all known data (for
example, address, registered name, and phone
number) from the call-in number.

X
Rip and Run Interface
ID Requirement Yes Future Modify No Comments
CT1 The system should include an interface to fax and
email services. X
CT2 The system should allow CFS information to be
transmitted via this interface to third-parties (such as fire departments).

X
CT3 The system should allow authorized users to
manage the settings for this interface (SMTP
configurations, etc.)
X
Computer Aided Dispatch Page 21 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
Mapping
General
ID Requirement Yes Future Modify No Comments
MA1 The system should use mapping functionality which
is based on ESRI-compatible mapping
components.

X
MA2 The system should allow for unlimited map layers,
including ESNs, counties, roads, railroads, postal
zones, and aerial imagery.

X
MA3 The system should allow users to click on any point on the map to view information such as an ESN,
county boundaries, postal zones, address,
coordinates, and nearest intersection.

X
MA4 The system should include map panning and
zooming functions. X
MA5 The system should allow the user to re-center the
map on a CFS, unit, or default location. X
MA6 The system should allow users to calculate the
distance between two points on the map. X
MA7 The system should allow users to toggle aerial
imagery for the map. X
MA8 The system should allow authorized users to
maintain a list of map marker types and assign
corresponding map icons.

X
MA9 The system should ignore city, state and zip code
data when searching for addresses if there are no
matches.

X
MA10 The system should allow authorized users to
configure any of the standard map actions as
system hot keys.

X
MA11 The system should allow for geo-verification of
addresses within CAD, RMS and JMS when the
client map application is not open.

X
MA12 The system should allow agency GIS personnel to
maintain map data. X
Mapping 22 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
CAD
ID Requirement Yes Future Modify No Comments
MB1 The system should integrate the mapping product
with the CAD product and make the map accessible
with a single click or keystroke from the CAD
product.

X
MB2 The system should allow all dispatch functions to be available from the map. X
MB3 The system should include map functions, such as
zooming and plotting, on other dispatch windows. X
MB4 The system should allow users to issue CAD
commands directly from the map. X
MB5 The system should automatically plot active and
waiting calls for service on the map as they are
entered, and automatically remove them from the
map as they are cleared.

X
MB6 The system should display key CFS data on the
map, including address, coordinates, nearest
intersection, cross streets, incident code, priority
level, and assigned units.

X
MB7 The system allows the map to filter units so that
only certain units are displayed on the map. X
MB8 The system should display dispatch alerts (if a CFS has been waiting past an agency-defined time to be
dispatched) on the map.

X
Markers
ID Requirement Yes Future Modify No Comments
MC1 The system should allow the user to filter the units which are viewable on the map, such as on-duty
units and/or off-duty units, or by unit type (law
enforcement, fire, and EMS).

X
MC2 The system should display key unit data on the
map, such as call sign unit type, and status. X
MC3 The system should display unit alerts for officer
safety checks (based on agency-defined times) on
the map.

X
Mapping 23 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
MC4 The system should allow map markers to expire
and should allow those expired markers to either be
removed from the map or grayed out upon
expiration.

X
MC5 The system should roll-up multiple markers for units so that they take up less space, if those units are all at the exact same location.

X
MC6 The system should allow users to place agencycustomizable map markers, without creating a CFS, for items such as controlled burns and road
construction.

X
MC7 The system should allow users to search on
customized map markers. X
MC8 The system should plot the ESN on the map for
Phase II calls. X
MC9 The system should display a shaded area which
represents the uncertainty distance around the
origination points for Phase I and Phase II calls.

X
Routing
ID Requirement Yes Future Modify No Comments
MD1 The system should include a routing function on the map which allows routes to be drawn between any
combination of unit locations, CFS addresses, and
other addresses, including intersections, mile
markers, and latitude/longitude coordinates.

X
MD2 The system should be able to mark road segments
as closed for routing purposes. Barriers or closed
segments should be displayed on the map. X
MD3 The system should allow users to create
bookmarks which capture both the location on the
map as well as the zoom level and any currently
enabled map layers.

X
MD4 The system should allow users to create a print
preview of mapping routes. X
Mapping 24 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
MD5 The system should allow users to create a PDF of
mapping routes and send them in an email. X
Search
ID Requirement Yes Future Modify No Comments
ME1 The system should include geospatial search which
supports the following:
- Searching and pinning specific addresses
including intersections, mile markers, and
latitude/longitude coordinates
- Searching for addresses within a radius
- Searching for addresses within an area (polygon)
drawn by the user
- Searching and pinning addresses by person or
business name
X
ME2 The system should allow all of the search results to be exported to a CSV file. X
AVL
ID Requirement Yes Future Modify No Comments
MF1 The system should allow the map to show unit
locations using AVL (if so equipped). X
MF2 The system should auto-populate the CFS with the
units AVL location for self-initiated calls (such as
traffic stops).

X
MF3 The system should update the unit location with the nearest address. X
MF4 The system should display the map coordinates for
any unit having AVL. X
MF5 The system should display units that do not have
AVL on the map at their user-specified locations. X
MF6 The system should allow units that do not have AVL
to be assigned default locations by unit status. X
AVL Playback
ID Requirement Yes Future Modify No Comments
Mapping 25 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
MG1 The system should record AVL data to permit
playback of data at a later time. X
MG2 The AVL playback data should be exportable from
the system using XML. X
MG3 The system should allow authorized users to restrict those who are able to view historical AVL data. X
Mapping 26 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
GIS Services
Data Migration and Scrubbing
ID Requirement Yes Future Modify No Comments
GA1 The vendor should provide GIS data migration and
scrubbing services as part of the implementation. X
GA2 The vendor should test the GIS data to ensure
proper functioning. X
GA3 The vendor should set up the data with the needed
configuration and load it into the ArcGIS format. X
GA4 The vendor should create address locator and
network dataset files to support geocoding and map
routing functionality.

X
GA5 The vendor should be capable of providing
additional GIS services without involving a third
party.

X
GIS Services 27 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
Mobile
General
ID Requirement Yes Future Modify No Comments
OA1 The system should allow mobile users to manage
their own passwords. X
OA2 The system should allow authorized users to
maintain a list of mobile user locations so that
mobile users do not have to manually type
commonly used locations.

X
OA3 The system should allow authorized users to
maintain a list of mobile user details such as "on
foot", or "has passenger", so that mobile users do
not have to enter commonly used details.

X
OA4 The system should allow authorized users to
configure default intervals for check-in reminders. X
OA5 The system should include options for visible and
audible alerts, as well as allowing the window
showing the alert to come to the front of other
programs which may be running.

X
OA6 The system should allow an authorized user to
identify which mobile users are logged in. X
OA7 The mobile system should be completely integrated
with the non-mobile CAD product. X
OA8 The mobile system should be completely integrated
with the non-mobile mapping product. X
OA9 The mobile system should be completely integrated
with the non-mobile RMS product. X
OA10 The mobile system should include a UI which was
specifically designed for entering data and
navigating within a mobile environment. For
example, users should be able to perform basic
functions via the touch-screen or mouse, with
minimal typing.

X
Mobile Page 28 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
OA11 The mobile system should allow the user to adjust
the font size for the display to ensure mobile
readability.

X
OA12 The mobile system should include large buttons to
support touch-screen access. X
OA13 The system should use highly visible color-coding
for UI elements such as windows and buttons. X
OA14 The system should be easily switched between day
and night mode display configurations. X
OA15 The system should provide a mobile usercustomizable dashboard that displays summary information from any modules which the user has
permission to access.

X
OA16 The system should display a mobile user’s
assigned tasks and overdue tasks on the user's
dashboard.

X
Network
ID Requirement Yes Future Modify No Comments
OB1 The system should synchronize data between
mobile workstations and system servers so that
CAD, RMS, or civil process data entered on mobile
units is immediately available on desktop
workstations at the agency and vice versa, as long
as the connection is maintained.

X
OB2 The system should use TCP/IP over HTTP with
web service type calls for communication between
the mobile workstation and the server.

X
OB3 The system should be compliant with FIPS-140 for
all network communication, wireless and wired. X
OB4 The system should support dual-factor
authentication with a username and password and
a USB dongle that meet FBI Security Addendum
Requirements.

X
Mobile Page 29 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
OB5 The system should support the mobile application
on any modern mobile data terminal with the
following specifications:
- Modern Intel processor or equivalent
- 512 MB RAM
- 4 GB storage
- 1024x768 touch-screen
- Windows 7 or 8.x (32-bit or 64-bit)
- Air card connection
X
OB6 The system should provide core mobile functionality on slower connections. X
OB7 The system should manage data transfers based
on network speed to optimize performance. X
OB8 The system should allow authorized users to set
upload and download limits and configure what
types of data can be uploaded and/or downloaded
based on connection speed.

X
OB9 The system should rely on intelligent connection
handling, including reusing connections and retrying
failed connections.

X
OB10 The system should require that the mobile
application automatically check for software
updates from the server when a user logs onto that
mobile workstation.

X
OB11 The system should ensure that the server
automatically pushes new updates to mobile
workstations.

X
CAD
ID Requirement Yes Future Modify No Comments
OC1 The system should provide silent dispatch for
mobile users. X
OC2 The system should allow the mobile user to
configure the mobile CAD screen to display the
data most useful or relevant at any given time.

X
OC3 The system should allow screen layouts to be
defined at the agency or user level. X
Mobile Page 30 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
OC4 The system should support fine-grained control of
UI elements, which would allow common layouts of
one area, but individual control of other areas.

X
OC5 The system should support individual user control
of assignment responses. X
OC6 The system should display data on the mobile CAD
screen about on-duty units such as call sign, status,
location, and key details (for example, has a ridealong). Information to be shown should be configurable per user or per agency.

X
OC7 The system should display data on the mobile CAD
screen about active calls for service such as CFS
number, priority, nature of call, address, and
assigned units. Information to be shown should be
configurable per user or per agency.

X
OC8 The system should allow mobile users to sort the
units display to show only a subset of units, such as
units in a specified beat, available units or assigned
units.

X
OC9 The system should allow mobile users to see which
units are using mobile CAD and are therefore
available to receive communications through the
mobile CAD system.

X
OC10 The system should allow mobile users to choose to
see all active calls for service or only their assigned calls for service.

X
OC11 The system should allow multiple call-takers,
dispatchers and/or mobile users to enter data on
the same CFS simultaneously.

X
Mobile Page 31 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
OC12 The system should allow mobile users to view all
incident information available to call-takers and
dispatchers. This includes:
- Incident location
- Nature of call
- Priority
- Beat
- Complainant/reporter data and contact
information
- Narrative details
- Any duplicate or linked incidents
- Attached state/NCIC queries and returns
X
OC13 The system should allow mobile users to update
data about their assigned CFS which was originally
entered by call-takers or dispatchers. For example,
they can update the street address if it was entered
incorrectly or change the nature of the CFS after
arriving on scene. All changes should be
immediately viewable to call-takers, dispatchers
and other mobile users.

X
OC14 The system should allow mobile users to add
unlimited narrative details to an assigned CFS.

These details should be viewable by call-takers,
dispatchers and other mobile users.

X
OC15 The system should allow mobile users to create
officer-initiated calls for service. This should
automatically assign the initiating officer to that
CFS.

X
OC16 The system should ensure that all information
entered into an officer-initiated CFS is immediately
viewable by call-takers, dispatchers and other
mobile users.

X
OC17 The system should allow a mobile user to add a use caution flag on any CFS. This flag should be visible
to all users viewing that CFS.

X
Mobile Page 32 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
OC18 The system should allow mobile users to create
officer-initiated traffic stop calls for service. This
should be done with a single press, click, or
keystroke and should automatically assign the
initiating officer to that CFS.

X
OC19 The system should allow mobile users to assign
themselves to calls for service with a single press,
click, or keystroke.

X
OC20 The system should allow mobile users to selfstatus, that is to change the status on their own unit as though they were a call-taker or dispatcher. Selfstatusing should be done with a single press, click, or keystroke. Status updates should be immediately
visible to call-takers, dispatchers and other mobile
users.

X
OC21 The system should include the self-statusing
actions such as the following for mobile users:
- Mark self as on duty and available for dispatch
- Assign self to an incident
- Mark self as enroute or on scene at an incident
- Mark self as leaving scene or completing incident
- Mark self as busy/unavailable for dispatch
- Mark self as off-duty or on-call
X
OC22 The system should allow mobile users to update
their own locations. Common locations (for
example, North Station, South Station, Jail, and
Hospital) should be accessible with a press or click.

Location updates should be immediately visible to
call-takers, dispatchers and other mobile users.

X
OC23 The system should allow mobile users to update
their own key details. Common key details (for
example, Has Ride-along, Has Prisoner, and On
Foot) should be accessible with a button or click.

Detail updates should be immediately visible to calltakers, dispatchers, and other mobile users.

X
Mobile Page 33 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
OC24 The system should allow call-takers and
dispatchers to continue to update statuses,
locations, details, etc. for mobile users should an
officer lose connection, step out of his/her vehicle,
etc.

X
OC25 The system should ensure that mobile users are
visibly alerted when the agency-defined check-in
time for officer safety has passed. The mobile user
should be able to check in with a single press, click,
or keystroke.

X
OC26 The system should ensure that mobile users are
visibly alerted when a call for service’s agencydefined dispatch timer (based on nature of incident and priority) has passed without any units having
been assigned.

X
OC27 The system should allow a mobile user assigned to
a call to stack himself/herself on a second call,
providing a visible indication to call-takers,
dispatchers and other mobile users that he/she will
respond to the stacked call after handling the
current call.

X
OC28 The system should allow a mobile user assigned to
a call to reassign himself/herself to a higher priority call and stack himself/herself to the initial call. X
OC29 The system should make all name, address and
vehicle alerts highly visible to mobile users. Alert
types may include outstanding warrants, officer
safety threats, medical alerts, hazardous materials
alerts, protection system or water supply
information, and other agency-defined alert types.

X
OC30 The system should allow authorized mobile users to access all previous data for persons, businesses,
addresses, and vehicles, such as prior calls for
service, traffic stops, case relationships, tickets, jail stays, warrants, parking tickets, etc.

X
Mobile Page 34 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
OC31 The system should allow mobile users to access
common state/NCIC queries with a single press,
click, or keystroke.

X
OC32 The system should automatically display the returns for state/NCIC queries to the initiating mobile user. X OC33 The system should allow instant messages to be
sent to multiple recipients from the mobile CAD
screen, such as via a public message room
accessible by all on-duty call-takers, dispatchers
and officers.

X
OC34 The system should allow mobile users to send and
receive private instant messages. X
OC35 The system should allow mobile users to send and
receive private email-style messages. X
OC36 The system should ensure that mobile users
receive bulletins issued by call-takers and/or
dispatchers such as BOLOS and special
instructions (for example, an extra patrol at a
specified address).

X
OC37 The system should allow authorized users to
configure alerts for mobile users for events such as
new CFS assignments for themselves and/or other
responders, new state/NCIC query returns, new
instant messages, new e-mail style messages, and
new bulletins. Options include visible and audible
alerts as well as forcing the mobile CAD display to
the front of all other open windows.

X
Administration
ID Requirement Yes Future Modify No Comments
OD1 The system should allow mobile users to use the
fleet management functionality as though they were
not remote.

X
OD2 The system should allow mobile users to use the
citizen feedback functionality as though they were
not remote.

X
Mobile Page 35 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
OD3 The system should allow mobile users to use the
policy manual as though they were not remote. X
OD4 The system should allow mobile users to use the
canine management functionality as though they
were not remote.

X
Civil Process
ID Requirement Yes Future Modify No Comments
OE1 The system should allow mobile users to interact
with and perform all functions which are accessible
from the desktop civil process product.

X
Mapping
ID Requirement Yes Future Modify No Comments
OF1 The system should allow mobile users to interact
with and perform all functions which are accessible
from the desktop mapping product.

X
OF2 The system should allow the map to automatically
zoom to a call or a location based on the mobile
unit's status.

X
OF3 The system should allow the mobile user to launch
the map as an embedded window. X
Records
ID Requirement Yes Future Modify No Comments
OG1 The system should allow mobile users to interact
with and perform all functions which are accessible
from the desktop RMS product.

X
OG2 The system should allow multiple users access for
entering supplemental narratives at the same time. X
Mobile Page 36 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
Mobility Client
Application Deployment
ID Requirement Yes Future Modify No Comments
MCA1 The application should be compatible with current
Android and iOS platforms. X
MCA2 The system should be available on both
smartphones and tablets. X
MCA3 The application should be available for download in public app stores. X
MCA4 The administrative portion of the application should be web-based and accessible from any webcapable device.

X
Application Security
ID Requirement Yes Future Modify No Comments
MCB1 The application should allow administrators to
approve or revoke usage for specific devices,
compliant with CJIS Policy Manual section 5.5.2.4. X
MCB2 The application should allow administrators to
approve or revoke usage for specific users,
compliant with CJIS Policy Manual section 5.5.2.4. X
MCB3 The application should use the same login
credentials as the CAD and/or RMS system. X
MCB4 The application should be deployed in such away
that multiple users can utilize the same device, if
needed.

X
MCB5 The web-based administration portion of the
application should require secure web login. X
MCB6 The application should have the option of MFA at
login via SMS message, compliant with CJIS Policy
Manual section 5.6.2.2.

X
MCB7 The application should present a system use
notification at login, compliant with CJIS Policy
Manual section 5.5.4.

X
Point Tracking Page 37 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
MCB8 The application should offer the abiility to lock a user out after 30 minutes of inactivity, compliant
with CJIS Policy Manual section 5.5.5.

X
MCB9 The application should grant the ability to unlock a phone after a session lock using a PIN, compliant
with CJIS Policy Manual section 5.6.2.1.2.

X
MCB10 The application should offer users the option to
unlock a phone via biometric authentication (e.g.,
fingerprint or face (iOS)) instead of a PIN code.

X
MCB11 The application should allow for the user to reset their PIN within the app. X
MCB12 The application should establish a secure
connection with the CAD/RMS server without usage
of a VPN.

X
MCB13 The application should transmit encrypted data that is FIPS 140-2 compliant. X
CAD Functionality
ID Requirement Yes Future Modify No Comments
MCC1 Access to the CAD portion of the application should be restricted based on user permissions defined
within the CAD system.

X
MCC2 The application should update CAD data in near
real-time, and the user should be able to receive
updates without manually refreshing the screen.

X
MCC3 The application should grant the ability to view
active, pending, and stacked CFS records. X
MCC4 The application should grant the ability to filter CFS on multiple criteria, including (but not limited to):
- Responding Agencies
- CFS Status
- Priority
- Jurisdiction (such as beat or zone)
X
Point Tracking Page 38 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
MCC5 The application should grant the ability to view CFS details, including:
- Incident Type
- Priority
- Call Taker
- Location
- CFS Jurisdiction
- Common Address (i.e. business name)
- CFS Creation Time
- Cross Streets
- Associated Alerts
- Name Alerts
- Vehicle Alerts
- Address Alerts
- Comments entered into the CFS by any users
- Assigned Units, including Status and Agency
- Ability to open each unit to see further
details
- Names and Vehicles associated with the CFS
- Case Reports associated with the CFS
X
MCC6 The application should notify the user of a newlyassigned CFS via push notification, even when the application is not open on the device.

X
MCC7 The application should allow for quick searches of the CFS list. X
MCC8 The application should show a list of CAD Units. X MCC9 The application should grant the ability to filter Units based on multiple criteria, including (but not limited
to):
- Responder Agency
- Unit Status
- Unit Jurisdiction
- Unit Type
X
Point Tracking Page 39 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
MCC10 The application should show unit details, including (but not limited to):
- Personnel associated with the unit
- Unit Agency
- Unit Type
- Unit Location
- Unit Status
- Assigned CFS
Other Details
X
MCC11 The application should feature an interfactive map that includes:
- Plotted CFS from the list of current CFS
- Plotted units, including those with AVL
- Ability to click a call or unit to see its details
- Ability to quickly launch a native routing
application for a plotted CFS
- Ability to see the user's current location
X
MCC12 The application should allow for quick searches of the Unit list. X
MCC13 The application should use the device's GPS
technology to report the device's position back to
CAD.

X
MCC14 The application should include settings that control the frequency of device location transmission to
extend battery life.

X
MCC15 The application should allow users to log in as CAD units or non-CAD units with limited CFS editing
abilities.

X
MCC16 The application should allow units that log in as a CAD unit to change their Unit Status. X
MCC17 The application should allow users to add
comments to the CFS. X
MCC18 The application should allow users to assign
themselves to a CFS. X
RMS Functionality
ID Requirement Yes Future Modify No Comments
Point Tracking Page 40 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
MCD1 Access to the RMS portion of the application should be restricted based on user permissions defined
within the RMS.

X
MCD2 The application should allow users to capture media for upload to a case report file, including:
- Photos
- Audio
- Notes
X
MCD3 The application should allow users to natively take photographs within the app. X
MCD4 Photos captured within the application should not
be accessible to other applications or galleries on
the device.

X
MCD5 The application should allow users to import photos from other photo galleries on the device. X
MCD6 The application should grant the ability to update photos with a description and comments before
uploading.

X
MCD7 The application should grant the ability to update audio with a description and comments before
uploading.

X
MCD8 The application should allow the user to upload
multiple pieces of media simultaneously. X
MCD9 The application should allow users to select the
case report to receive uploaded media via the
following methods:
- A link to a case report found on a currently
assigned CFS
- A list of case reports that the user recently
uploaded media to
- Searching for older cases that the user has
permission to access
X
MCD10 When uploads are complete, the media should
require no further validation or importing in the
RMS, and should be immediately accessible in the
RMS.

X
State/NCIC Functionality
Point Tracking Page 41 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
ID Requirement Yes Future Modify No Comments
MCE1 The application should allow users to run common
State/NCIC queries from the mobile device or
tablet.

X
MCE2 The application should display any pictures that are returned from a query. X
MCE3 The application should allow an agency
administrator to configure which queries are
available in the app.

X
MCE4 The application should allow scanning of driver's
license barcodes to prefill parameters necessary to
execute people- and driver-related queries.

X
MCE5 The application should allow scanning of VIN
barcodes to prefill parameters necessary to execute
vehicle-related queries.

X
MCE6 The application should automatically remove
State/NCIC query return results from the device
within a few hours of running the query.

X
MCE7 The application should allow users to manually
remove/clear a return from the device. X
MCE8 The ability to run State/NCIC queries in the app
should be based on user permissions within the
CAD/RMS.

X
MCE9 The application should respect permissions in the
app that indicate which queries a user has
permission to run.

X
Point Tracking Page 42 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
Personnel
Personnel
ID Requirement Yes Future Modify No Comments
PA1 The system should allow authorized users to create
and manage employee records. X
PA2 The system should provide a guided step-by-step
process (wizard) for entering a new person/user
into the system to ensure that all steps are
completed.

X
PA3 The system should allow unlimited photos to be
attached to each employee record. X
PA4 The system should allow bulk updating of employee
records. X
PA5 The system should retain records indefinitely for
employees who are no longer with the agency and
track the date(s) employees were in and out of
service.

X
PA6 The system should allow authorized users to set up
detailed permissions for each employee, both
individually and within groups.

X
PA7 The system should allow authorized users to
generate a permissions audit report for an
employee which shows all areas of the system to
which that person has access, what type of access
it is, and how it is granted.

X
PA8 The system should allow authorized users to
maintain lists of personnel job titles, personnel
addressed as, personnel specialties, personnel
groups, divisions, termination reasons and service
types.

X
PA9 The system should allow authorized users to view
and print a log of the changes to an employee's
personnel records.

X
CentralSquare Technologies LLC Agreement

________________________
PA10 The system should allow authorized users to create unlimited custom form templates which are used to
associate agency-specified data with individual
personnel records.

X
PA11 The system should allow users with access to
personnel records to use the custom forms to enter
and maintain the associated data.

X
PA12 Agency-defined custom fields should be available in Personnel. X
Employee Promotions
ID Requirement Yes Future Modify No Comments
PB1 The system should allow authorized users to create
and maintain employee promotion records. X
PB2 The system should allow employee promotion
records to have files attached to them via upload or
scanner.

X
PB3 Agency-defined custom fields should be available in Employee Promotions. X
Employee Commendations
ID Requirement Yes Future Modify No Comments
PC1 The system should allow authorized users to create
and maintain employee commendation records. X
PC2 The system should allow authorized users to
maintain a list of commendation types. X
PC3 The system should allow employee commendation
records to have files attached to them via upload or
scanner.

X
PC4 Agency-defined custom fields should be available in Employee Commendations. X
Employee Disciplinary Actions
ID Requirement Yes Future Modify No Comments
PD1 The system should allow authorized users to create
and maintain employee disciplinary action records. X
CentralSquare Technologies LLC Agreement

________________________
PD2 The system should allow authorized users to
maintain lists of offense types and disciplinary
action types.

X
PD3 The system should allow employee disciplinary
action records to have files attached to them via
upload or scanner.

X
PD4 Agency-defined custom fields should be available in Employee Disciplinary Actions. X
Employee Training
ID Requirement Yes Future Modify No Comments
PE1 The system should allow authorized users to create
and maintain training records for employees. X
PE2 The system should allow authorized users to
manage lists of training locations, training
certificates, and training categories.

X
PE3 The system should allow users to view a list of
courses which will soon expire. X
PE4 The system should allow training courses to be
entered for an individual employee or entered in
bulk with a single action for multiple employees (for
example, all officers or dispatchers).

X
PE5 The system should be able to calculate the total
training hours completed by each employee. X
PE6 The system should allow users to view the number
of training hours completed by an employee within a
specified time frame (for example, annual training
hours completed).

X
PE7 The system should display upcoming
training/certification expirations in a highly visible
manner.

X
PE8 The system should be able to list courses that were offered by the agency but declined by an employee. X
PE9 The system should be able to store default course
data for common training courses. X
CentralSquare Technologies LLC Agreement

________________________
PE10 The system should allow training records to have
files attached to them via upload or scanner. X
PE11 The system should allow authorized users to create unlimited custom form templates to associate
agency-specified data with individual training
records.

X
PE12 The system should allow users with access to
training records to use the custom forms to enter
and maintain the associated data.

X
PE13 Agency-defined custom fields should be available in Employee Training. X
Citizen Feedback
ID Requirement Yes Future Modify No Comments
PF1 The system should provide a means for tracking
citizen feedback. X
PF2 The system should allow authorized users to
maintain lists for feedback types, feedback actions,
and feedback dispositions.

X
PF3 The system should allow a CFS or case report to be
associated with the citizen feedback record. X
PF4 The system should allow one or more officers or
other users to be associated with the citizen
feedback record.

X
PF5 The system should automatically check the
reporting citizen's name against the master name
index.

X
PF6 The system should allow citizen feedback records
to have files attached to them via upload or
scanner.

X
PF7 Agency-defined custom fields should be available in Citizen Feedback. X
CentralSquare Technologies LLC Agreement

________________________
Records Management System (RMS)
Case Reports
ID Requirement Yes Future Modify No Comments
RA1 The system should allow authorized users to
maintain a list of case report types (for example,
patrol, investigations, narcotics, and juvenile).

X
RA2 The system should allow authorized users to build
unlimited case report output templates (such as an
internal report, a media report, and a state’s
attorney report) and to specify which data is printed
for each.

X
RA3 The system should allow authorized users to set up
case report approval workflows which notify users
to perform such tasks as completing cases,
reviewing and approving cases, and kicking back
cases for changes.

X
RA4 The system should support setting permissions for
each case report type by user and/or user group. X
RA5 The system should include the following default
involvement types for case reports: offender,
suspect, victim, and witness.

X
RA6 The system should allow authorized users to extend
the list of case report involvement types to include
such types as arrestee, cited, reporter, driver of
vehicle, and passenger.

X
RA7 The system should support agency or user-defined
notifications for case aging (for example, 30-days
since creation), case referrals, and follow-ups. X
RA8 The system should auto-populate case reports
generated from calls for service data such as
address, nature of the incident,
complainant/reporter data, beat/zone, and NCIC
queries and results.

X
Records Management System Page 47 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
RA9 The system should make incident data such as
responding units and unit response times readily
available to assist in completing the case report
when case reports are generated from calls for
service. This incident data should be viewable
alongside of the case report information.

X
RA10 The system should allow case reports to be
generated without a corresponding call for service. X
RA11 The system should allow call-takers and
dispatchers to perform an automatic transfer of
CFS data from CAD to the RMS when needed. This
transfer should not be a one-time transfer but
should be kept up to date as the CFS progresses.

X
RA12 The system should allow authorized users to
maintain a list of case dispositions, including
whether a disposition closes a case.

X
RA13 The system should allow a case report’s disposition (status) to be updated at any time. X
RA14 The system should allow dispositions to be agencydefined, and should allow the case list to be queried by disposition to show a list of cases under
investigation, cases sent to the state’s attorney, etc.

X
RA15 The system should allow multiple supplemental
case narratives to be added by the primary officer
or by other users.

X
RA16 The system should support multiple users adding
multiple narratives to a case at the same time. X
RA17 The system should allow the case narratives to
include unlimited text. X
RA18 The system should allow authorized users to create custom case narrative templates with section
headings (for example, Synopsis, Details, and
Actions Taken).

X
RA19 The system should allow a case report to specify
assisting officers. X
Records Management System Page 48 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
RA20 The system should allow a case report to specify
multiple offenses. X
RA21 The system should allow a case report to specify
multiple counts of a charge. X
RA22 The system should allow an unlimited number of
involvement types to be set up for and used on
case reports.

X
RA23 The system should automatically generate required
case report forms to gather additional necessary
information (for example, arrest forms and citations)
based on the selected involvement type(s).

X
RA24 The system should display the state, federal or local statute or offense descriptions for each offense
within the case report screen.

X
RA25 The system should allow case reports to include
multiple modi operandi for a single case report. X
RA26 The system should allow case reports to record
unlimited vehicles, such as vehicles involved in
traffic stops or traffic accidents, towed vehicles,
abandoned vehicles, and unlimited agency-defined
vehicle relationship types.

X
RA27 The system should allow users to record vehicle
information on citations, warnings, arrest forms, and
field identification forms without having to manually
re-enter data in each place.

X
RA28 The system should automatically transfer all vehicle information to a case report from an associated
CFS.

X
RA29 The system should allow case reports to include
unlimited case notes which are stamped with the
date, time and name of the user who created them. X
RA30 The system should allow for expunging individual
names from case reports. Expunging the name
involvement will automatically expunge the name
from system forms such as the arrest and victim
form.

X
Records Management System Page 49 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
RA31 The system should allow authorized users to
expunge individual offenses from a specified name
on a case report.

X
RA32 The system should allow authorized users to view
the original non-expunged case report. X
RA33 The system should have an option to allow
expunged records to be reverted back to include
the original names and offenses.

X
RA34 They system should have an option to allow
expunged records to be completely removed from
the database so report writing tools can not be used
to identify the original name or offense.

X
RA35 The system should allow historical reporting to
continue to include the expunged records so the
number of offenses does not change when items
are expunged. The expunged names will not
display within these reports.

X
RA36 The system should allow workflow activities to be
created around Sealing and Expungement actions
to help with verification processes.

X
RA37 The system should provide an agency and usercustomizable dashboard that displays summary information from any modules which the user has
permission to access (for example, that user’s open
case reports, reports needing approval, or a list of
recently added warrants).

X
RA38 Dashboards can be utilized with workflow options to display a list of all cases and tasks which require
the users attention.

X
RA39 The system allows for automatic workflow routing
based on the offense or state reporting code. X
RA40 The system should allow access to sealed cases to
be granted to users or user groups per case. X
RA41 The system should allow authorized users to
maintain the list of reasons for sealing cases. X
RA42 The system should allow authorized users to
update and correct previously entered data on a
case report.

X
Records Management System Page 50 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
RA43 The system should be able to support multiple case reports for the same event, with access to the
reports restricted by user permissions. For
example, a patrol report and an investigative report
may be created about a single event and linked to
each other.

X
RA44 The system should group case reports based on
agency-defined criteria (for example, a string of car
break-ins). Links should be provided between
grouped case reports.

X
RA45 The system should create a full audit trail showing all activity related to the case report such as case
report creation, adding and removing data, and
approval history. Each audit entry should include
the date, time, and user.

X
RA46 The system should support intelligent full-text
searching of case report narrative fields. X
RA47 The system should allow case reports to have files attached to them via upload or scanner. X
RA48 The system should allow authorized users to create unlimited custom form templates which are used to
associate agency-specified data with individual
case reports.

X
RA49 The system should allow users with access to case
reports to use the custom forms to enter and
maintain the associated data.

X
RA50 The system should include a configurable process
(workflow) for reviewing and approving case
reports.

X
RA51 The system should provide a means for users to
indicate that a case report is ready for review and
awaiting approval.

X
RA52 The system should restrict case report approvals to authorized users. X
Records Management System Page 51 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
RA53 The system should include configurable case
routing for review and approval (for example, to a
person’s supervisor, to any on-duty supervisor, or
according to routing criteria completed by the user).

X
RA54 The system should allow case reports to be routed
to multiple people for approval. X
RA55 The system should alert users when a case report
(or a component of a case report) has been
completed and sent to them for approval.

X
RA56 The system should allow case report approvers to
approve an entire case report or an individual
component (for example, a primary narrative but
not an attached citation).

X
RA57 The system should allow case report approvers to
"kick back" an entire case report or a case report
component.

X
RA58 The system should include a field for "kicked back" case reports and components which allows the
case report approver to request needed changes. X
RA59 The system should display a case report’s current
approval status and should allow the case report list
to be filtered by approval status.

X
RA60 The system should be able to lock approved case
reports against future editing. X
RA61 The system should allow authorized users to
reactivate locked case reports. X
RA62 The system should create a case report
management audit trail that includes the date and
time when the record was created, edited, saved,
completed, forwarded for approval, closed, etc.

X
RA63 The system should allow authorized users to
configure the case management tasks to match the
case review and approval system the agency has in
place.

X
Records Management System Page 52 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
RA64 The system should automatically generate tasks for the users who need to complete case reports,
approve case reports, perform investigative
reviews, etc.

X
RA65 The system should allow users to manually create
tasks for case reports. X
RA66 The system should include as a dashboard part a
list of the user's outstanding tasks or case reports
which require action.

X
RA67 The system should support adding case referral
forms to case reports and should also generate
notification and follow up tasks for predetermined
users or groups based on user input and scoring
thresholds.

X
RA68 The system should include case report scoring
functionality for investigators, with configurable
scoring requirements.

X
RA69 The system should send case report scoring
notifications via internal system messaging, e-mail,
paging and/or SMS.

X
RA70 The system should notify specified users, including primary officers and their supervisors, when case
reports have aged beyond an agency-specified time
threshold.

X
RA71 The system should allow e-mail-style messages
sent between users to contain links to case reports. X
RA72 The system should notify users or user groups via
internal system messaging, e-mail, paging and/or
SMS when a case report has been assigned to
them for completion and/or approval.

X
RA73 The system should allow for notifying individuals or groups when something new has been added to a
case report.

X
RA74 The system should allow for notifying individuals or groups when an item has been approved on a Case
Report.

X
Records Management System Page 53 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
RA75 The system should include a list of calls for service which require case reports that have not yet been
written.

X
RA76 The system should allow users to sort and filter
case reports within the list-view screen. X
RA77 The system should allow users to save, print or
email a case report (including all associated
records and attachments) directly from the record
window.

X
RA78 The system should allow users to save, print or
email a summary list of the case reports directly
from the list-view window.

X
Case Leads
ID Requirement Yes Future Modify No Comments
RB1 The system should have a feature within case
reports which allows for tracking all tips, leads, and
tasks associated with the case.

X
RB2 The system will allow a user to assign leads to
other users who are helping to gather information
on the case.

X
RB3 The system allows for assigning a lead to an
individual who doesn't have access to the full case
report. The assignor can determine how much
information about the case and lead should be
granted to the assignee. The assignee will be
allowed to add information to the leads assigned to
them.

X
RB4 The system allows users to create new leads for a
specific case even if they don't have access to the
case.

X
RB5 The system shall allow the primary investigator to
filter a list of all leads where the assignments have
been completed and are ready for review.

X
RB6 The system should allow leads to be organized by
agency-configurable values such as Interview a
witness or Canvas the neighborhood.

X
Records Management System Page 54 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
RB7 The system should allow the priority or urgency of
each lead to be assigned. X
RB8 The system should include names added to a lead
to the system's Master Name record and allow it to
be linked back to the lead.

X
RB9 The system should include Vehicles added to a
lead to the system's Master Vehicle record and
allow it to be linked back to the lead.

X
RB10 The system should allow Narratives to be added
specific to each lead. The primary investigator can
review the narrative and import the narrative into
the case report if they determine the information
should be included within the case report.

X
RB11 The system will allow for importing names, vehicles, and supplemental narratives from completed tasks
into the Case Report. Information that is deemed
unnecessary does not need to be imported into the
case report.

X
RB12 The system should allow workflow to be automated
to create tasks or notifications when a new lead is
entered.

X
RB13 The system should allow workflow to be automated
to create tasks or notifications when a new lead is
assigned.

X
RB14 The system should allow workflow to be automated
to create tasks or notifications when a new lead is
completed.

X
RB15 The system should allow leads assigned to
individuals to be displayed on their dashboards. X
RB16 The system should allow Property and Evidence to
be added to each lead. X
RB17 The system should allow attachments to be added
to each lead. X
RB18
The system should allow for tracking tips and leads
that are not associated with a specific case report.

X
Records Management System Page 55 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
RB19 The system should include a report generator that
allows user-defined reports to be created with the
information collected within each of the leads.

X
Intelligence Case Reports
ID Requirement Yes Future Modify No Comments
RC1 The system should allow the system to track
intelligence reports. X
RC2 The system should ensure that intelligence case
reports include all of the standard functionality and
workflow as regular case reports.

X
RC3 The system should lock down the intelligence case
reports so that only specified users have access to
any of the data stored in those case reports. X
RC4 The system should ensure that the intelligence case reports include links to warrants, protection orders,
field identifications, other intelligence case reports
and standard case reports.

X
RC5 The system should ensure that master name
records which are associated with an intelligence
report have an additional section of information
which records information such as informant ID and
the MO.

X
RC6 The system will allow authorized personnel to add
and track notes on Informants to document all
contacts with the individual.

X
RC7 The system should ensure that authorized users
may choose to not submit intelligence cases to
state reporting (IBR/UCR).

X
RC8 The system should allow Names, Offenses and
Vehicles to be copied from an Intelligence Case into
a normal case without the need to re-enter the
information.

X
IBR Preparation
ID Requirement Yes Future Modify No Comments
Records Management System Page 56 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
RD1 The system should perform IBR error checking and
validation on the case report, including detailed
error messages.

X
RD2 The system will provide a link to specific fields that need to be corrected for IBR validations. X
RD3 The system should package the case reports in
suitable format for IBR submittal. X
RD4 The system should be able to provide CA State
required reports - Anti-Reproductive Rights Crimes;
Hate Crimes; Domestic Violence Crimes and Law
Enforcement Officers Killed/Injured
X
Property/Evidence Management
ID Requirement Yes Future Modify No Comments
RE1 The system should allow users to create and
maintain property/evidence records for case
reports.

X
RE2 The system should allow users to manually assign
a number to property/evidence items for purposes
of displaying those items before the court. X
RE3 The system should allow authorized users to
maintain a list of property/evidence shelves,
lockers, bins, and other locations.

X
RE4 The system should allow access tags to be defined
for property/evidence items which would restrict
access to certain users or user groups.

X
RE5 The system should eliminate the need to duplicate
any property/evidence information after it has been
entered into the system.

X
RE6 The system should support stolen property reports. X RE7 The system should support lost property reports. X
RE8 The system should support found or recovered
property reports. X
RE9 The system should support contraband or seized
property items property reports. X
Records Management System Page 57 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
RE10 The system should support evidence items reports. X RE11 The system should include business logic that
allows the property/evidence forms to automatically
adjust to the type of property selected and to
display only the necessary fields for input of that
type of property.

X
RE12 The system should include the appropriate data
elements for each property and evidence type. X
RE13 The system should allow users to set a target
disposal date for each property/evidence item. X
RE14 The system should allow a user to access the
associated case report by a single click or
keystroke from the property/evidence record.

X
RE15 The system should allow digital photos of each
piece of property/evidence to be attached to the
property/evidence record.

X
RE16 The system should be able to print barcodes for
property/evidence items. X
RE17 The system should be able to open a
property/evidence record by scanning the item’s
barcode.

X
RE18 The system should allow users to capture
information regarding the intake, movement,
release, and disposal of property and evidence and
should produce appropriate chain-of-custody
reporting.

X
RE19 The system should include a full audit trail for the chain of custody, including the date, time, start and
end location, and personnel involved in each
transaction.

X
RE20 The system tracking should include transferring
property internally, transferring to/receiving from
personnel, and transferring to/receiving from
external entities (crime labs, etc.).

X
RE21 The system should allow only valid property
movement based on an item’s current status, to
enforce a valid chain of custody.

X
Records Management System Page 58 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
RE22 The system should generate receipt forms for
documenting movement of property and evidence. X
RE23 The system should support electronic capture of
signatures for the receipt forms. X
RE24 The system should allow users to move and
manage property/evidence in bulk. X
RE25 The system should store and manage digital
evidence such as audio, photos, documents, and
video links.

X
RE26 The system should store a read-only checksum for
digital files and provide a means of determining if
anyone has tampered with the file.

X
RE27 The system should allow users to export digital
evidence in bulk. X
RE28 The system should allow tagging specific points on the timeline within audio files to provide a means for
jumping directly to those points.

X
RE29 The system should display tagged time references
in a chronological list to allow users to jump to the
relevant information (for example, a confession) by
selecting the tag.

X
RE30 The system should allow users to sort and filter
property/evidence records within the list-view
screen.

X
RE31 The system should allow users to save, print or
email a summary list of the property/evidence
records directly from the list-view window.

X
RE32 The system should allow users to save, print or
email a property/evidence record directly from the
record window.

X
RE33 The system should support intelligent full-text
searching of property/evidence narrative fields. X
Records Management System Page 59 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
RE34 The system should be able to generate and print
reports based on the property/evidence list such as:
- Property nearing target disposal date
- Property in temporary locations
- Property out of agency custody
X
RE35 The system should offer the ability to audit a
property location to determine if all expected
physical items are within the specified location.

Missing and extra items will be identified for the
auditor.

X
RE36 The system should allow for creating custom forms
for Property and Evidence. X
RE37 The system should allow barcode labels to be
configured to display any of the information
available on the Property and Evidence screen.

X
RE38 The system should display thumbnail size pictures
on the screen to help navigate to the photos of
interest.

X
RE39 The system should allow multiple evidence photos
to be printed on a single page using thumbnailsized pictures.

X
RE40 Agency-defined custom fields should be available in Property and Evidence. X
Arrests
ID Requirement Yes Future Modify No Comments
RF1 The system should allow users to create and
maintain arrest forms. X
RF2 The system should support multiple charges for a
given person on a single arrest form. X
RF3 The system should allow users to add an arrest
form to a case report at the time of the original
incident or any time after that.

X
RF4 The system should allow users to add supplemental
arrest narratives to the original case report in the
event of an arrest at a later date.

X
Records Management System Page 60 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
RF5 The system should make the arrest information
from the RMS available to the JMS for autopopulating the booking record.

X
Citations
ID Requirement Yes Future Modify No Comments
RG1 The system should allow users to create and
maintain citation records. X
RG2 The system should allow the citation number to be
free-form text rather than a predefined number
sequence.

X
RG3 The system should support use of different types of citations, including traffic citations and non-traffic
citations.

X
RG4 The system should ensure that citations use the
state-defined charges/offenses. X
RG5 The citation should display on the master name
record and/or vehicle name record. X
RG6 The system should allow citations to be associated
with case reports or created without a case report. X
RG7 The system should allow users to save, print or
email a summary list of the citation records directly
from the list-view window.

X
RG8 The system should allow users to save, print or
email a citation record directly from the record
window.

X
RG9 The system should support intelligent full-text
searching of citation narrative fields. X
RG10 The system should allow citations to be manually
linked to existing case reports. X
RG11 Agency-defined custom fields should be available in Field Identifications. X
Field Identifications
ID Requirement Yes Future Modify No Comments
RH1 The system should allow users to create and
maintain field identification records. X
Records Management System Page 61 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
RH2 The system should allow users to create gang
affiliations as part of the field identification process. X RH3 The system should allow users to save, print or
email a summary list of the field identification
records directly from the list-view window.

X
RH4 The system should allow users to save, print or
email a field identification record directly from the
record window.

X
RH5 The system should support full-text searching of
field identification narrative fields. X
RH6 The system should allow field identification records to be associated with case reports or created
without a case report.

X
Warrants
ID Requirement Yes Future Modify No Comments
RI1 The system should allow users to create and
maintain warrant records. X
RI2 The system should allow authorized users to
update the warrant status at any time. X
RI3 The system should allow for addition of standard
fees upon creation of the warrant. X
RI4 The system should allow warrants to be organized
by agency-configurable values. X
RI5 The system should allow separate numbers, such
as NCIC, docket, state case, or OCA to be included
in the warrant record.

X
RI6 The system should allow data for the appropriate
prosecutor to be included with each warrant. X
RI7 The system should allow authorized users to
change the status of a warrant for the following
reasons: served on the person, recalled by the
court, person booked on warrant charge, and other
reasons defined by the agency.

X
RI8 The system should allow warrants to be sealed. X
Records Management System Page 62 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
RI9 The system should be able to generate a standard
felony warrant letter from the warrant. X
RI10 The system should restrict access to sealed
warrants to specified users or user groups. X
RI11 The system should keep track of cancelled
warrants. X
RI12 The system should automatically alert call-takers, dispatchers and/or officers when names with active
warrants are involved in a CFS.

X
RI13 The system should flag any names from the master
name index which have active warrants. X
RI14 The system should track service attempts for
warrants. X
RI15 The system should allow authorized users to
specify whether to charge for mileage on each
warrant service attempt trip.

X
RI16 The system should allow users to make notes on
warrants to record any data learned during service
attempts that may aid in successful service. Each
note should include the date, time, and username.

X
RI17 The system should allow warrants to have files
attached to them via upload or scanner. X
RI18 The system should allow authorized users to create unlimited custom form templates which are used to
associate agency-specified data with individual
warrants.

X
RI19 The system should allow users with access to
warrants to use the custom forms to enter and
maintain the associated data.

X
RI20 The system should allow for creating workflow
tasks for events such as adding a new warrant or
clearing an existing warrant.

X
RI21 Agency-defined custom fields should be available in Warrants. X
Protection Orders
ID Requirement Yes Future Modify No Comments
Records Management System Page 63 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
RJ1 The system should allow for tracking protection
orders. X
RJ2 The system should ensure that the master name
records for both the defendant and the complainant
show a link for the protection order.

X
RJ3 The system should flag any names from the master
name index which have active protection orders. X
RJ4 The system should track service attempts for
protection orders. X
RJ5 The system should allow users to make notes on
protection orders to record any data learned during
service attempts that may aid in successful service.

Each note should include the date, time, and
username.

X
RJ6 The system should create a Sheriff's Return for
successful service attempts. X
RJ7 The system should allow authorized users to create
unlimited custom form templates which are used to
associate agency-specified data with individual
protection orders.

X
RJ8 The system should allow users with access to
protection orders to use the custom forms to enter
and maintain the associated data.

X
RJ9 The system should allow for creating Protection
Order workflow tasks . X
RJ10 Agency-defined custom fields should be available in Protection Orders. X
Pawn Property
ID Requirement Yes Future Modify No Comments
RK1 The system should allow users to create and
maintain pawn property records. X
RK2 The system should allow users to attach digital
photos to a pawn property record, either via an
upload or directly from a camera.

X
Records Management System Page 64 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
RK3 The system should allow pawn property records to
have files attached to them via upload or scanner. X
RK4 The system should allow users to save, print or
email a summary list of the pawn property records
directly from the list-view window.

X
RK5 The system should allow users to save, print or
email a pawn property record directly from the
record window.

X
RK6 The system should support intelligent full-text
searching of pawn property narrative fields. X
RK7 Agency-defined custom fields should be available in Pawn Property. X
Sex Offenders
ID Requirement Yes Future Modify No Comments
RL1 The system should allow for tracking sex offenders. X RL2 The system should ensure that names and
addresses entered into sex offender records are
checked against the master indices and then added
to those indices if they do not already exist.

X
RL3 The system should provide a list of registered sex
offenders that is accessible by authorized users
from any product.

X
RL4 The system should alert users to sex offender
status whenever a sex offender’s name appears
anywhere in the system.

X
RL5 The system should track sex offender check-in
dates and alert users to an offender’s next required
check-in date.

X
RL6 The system should be able to generate a printable
list of sex offenders who are soon due to check in
or who are overdue.

X
RL7 Agency-defined custom fields should be available in Sex Offenders. X
Records Management System Page 65 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
Bicycle Registrations
ID Requirement Yes Future Modify No Comments
RM1 The system should allow bicycle registrations to be tracked. X
RM2 The system should ensure that names and
addresses entered into bicycle registration records
are checked against the master indices and then
added to those indices if they do not already exist.

X
RM3 The system should track invoices, fees, and
receipts associated with bicycle registrations. X
RM4 The system should allow photographs to be
attached to a bicycle registration record. X
RM5 The system should provide a list of bicycle
registrations that can be searched by any data
element including serial number.

X
RM6 Agency-defined custom fields should be available in Bicycle Registrations. X
Parking Tickets
ID Requirement Yes Future Modify No Comments
RN1 The system should allow parking tickets to be
tracked. X
RN2 The system should allow authorized users to
change the status of a parking ticket for any
number of reasons defined by the agency.

X
RN3 The system should ensure that the name, vehicle
and/or address entered into parking ticket records
use the master records. Parking ticket records
should also use the name and address validation
provided with the master name and master address
records.

X
RN4 The system should allow parking ticket statuses to
be changed in bulk. X
RN5 The system should allow users to attach documents
to parking ticket records. X
Records Management System Page 66 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
RN6 The system should track invoices, fees, and
receipts associated with parking tickets. X
RN7 The system should allow for an agency-defined
sliding fee scale based on parking ticket age. X
RN8 The system should provide a list of parking tickets that can be searched. X
RN9 The system should allow authorized users to create
unlimited custom form templates which are used to
associate agency-specified data with individual
parking tickets.

X
RN10 The system should allow users with access to
parking tickets to use the custom forms to enter
and maintain the associated data.

X
RN11 Agency-defined custom fields should be available in Parking Tickets. X
Pistol Permits
ID Requirement Yes Future Modify No Comments
RO1 The system should allow pistol permits to be
tracked. X
RO2 The system should ensure that names and
addresses entered into pistol permit records are
checked against the master indices and then added
to those indices if they do not already exist.

X
RO3 The system should allow invoices associated with
pistol permits to be printed or emailed directly from
the pistol permit.

X
RO4 The system should allow authorized users to
manage the fees which are charged for pistol
permits.

X
RO5 The system should allow authorized users to
manage permit subtypes. X
RO6 The system should track fees associated with pistol permits. X
Records Management System Page 67 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
RO7 The system should allow receipts to be printed or
emailed for paid invoiced directly from the pistol
permit.

X
RO8 The system should maintain an outstanding
balance when pistol permit fees are not paid in full. X RO9 The system should allow photographs or
documents to be attached to a pistol permit record. X
RO10 The system should provide a list of pistol permits that can be searched by any data element. X
RO11 The system should allow authorized users to create unlimited custom form templates which are used to
associate agency-specified data with individual
pistol permits.

X
RO12 The system should allow users with access to pistol permits to use the custom forms to enter and
maintain the associated data.

X
RO13 Agency-defined custom fields should be available in Pistol Permits. X
RO14 The system should automatically change the status
of a pistol permit once it expires. X
Digital Lineups
ID Requirement Yes Future Modify No Comments
RP1 The system should allow authorized users to create
digital lineups using mugshots stored in the system. X
RP2 The system should allow users to choose
demographic criteria to select mug shots for
inclusion in digital lineups, including eye color, hair color, height, and weight.

X
RP3 The system should support exporting digital lineups to a ZIP file. X
RP4 The system should allow users to randomly select
photos for a digital lineup. X
Accident Reports
Records Management System Page 68 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
ID Requirement Yes Future Modify No Comments
RQ1 The system should track accident reports, including attached accident diagrams. X
RQ2 The system should allow files to be attached to
accident reports via upload or scanner. X
RQ3 The system should allow accident reports to be
related to case reports. X
RQ4 Agency-defined custom fields should be available in Accident Reports. X
Records Reporting
ID Requirement Yes Future Modify No Comments
RR1 The system should provide a report generator for
building custom statistical and analytical reports
from RMS data. The report generator should be
provided by the same vendor and not be a thirdparty application.

X
RR2 The system should restrict access to the report
generator and individual report templates by user or
user group.

X
RR3 The system should not allow a user who does not
have access to particular data via the application
user interface to gain access to that data via the
report generator.

X
RR4 The system should allow the creator of the report
template to build reports for any data entered into
the RMS product.

X
RR5 The report generator should allow the creator of the report template to control layout and formatting
options for each administration report template.

This includes such options as field arrangements,
column widths, label text, font sizes, and line
spacing.

X
RR6 The report generator should allow the creator of
each RMS report template to choose which users
can access and/or run the report and/or modify the
report template.

X
Records Management System Page 69 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
RR7 The report generator should support the use of
aggregate (math) functions including Sum,
Average, Count, Count Blank, Minimum, and
Maximum.

X
RR8 The report generator should allow data to be
grouped or sorted by any data element. X
RR9 The report generator should allow multiple data
filters to be applied using "and/or" logic. X
RR10 The report generator should allow RMS reports to
be saved (as PDF, .XLS, or .CSV), printed, or
emailed directly from the report.

X
RR11 The report generator should allow administration
report templates to be saved and modified at a later
time.

X
RR12 The report generator should support adding the
RMS reports to user's dashboards. X
RR13 The report generator should allow recurring RMS
reports to be scheduled and automatically uploaded
to a file-system or e-mailed to specified users on
certain days and times.

X
RR14 The report generator should support ad-hoc
queries. X
RR15 The system should include performance reports
based on all information (date, time, etc.) captured
in the case management system. These reports
should show how long cases have been open, how
long they took to close, what the officer workload is,
and whether agency protocol was followed.

X
Records Management System Page 70 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
RR16 The report generator should support creation of
RMS reports such as the following:
- Daily or shift-based summary of case reports
- Summary of case reports for a specified time
range
- Summary of case reports by approval status or
by disposition
- Summary of case reports by offense or by nature
of incident
- Summary of case reports by geographical area
- Summary of juvenile cases
- Summary of arrests by officer
- Summary of citations by officer
- Officer case load report
- Crimes within an area
- Year-to-date crime totals
- Comparison of crime statistics year over year
- Outstanding warrants summary
- Warrants served by serving officer
- Unpaid parking ticket summary
- Parking tickets issued broken down by officer
X
NIBRS Interface
ID Requirement Yes Future Modify No Comments
The system should include an interface to the
state's NIBRS repository. X
The system should allow users to export cases as
text files via this interface. X
Interface A
ID Requirement Yes Future Modify No Comments
The system should be able to interface with the
Crossroads software for electronic traffic collision
reporting and electronic citations.

X
Scheduled for the 23.3 release of Pro
Suite
Records Management System Page 71 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
System (Global)
General
ID Requirement Yes Future Modify No Comments
SA1 The system should allow all software products
(CAD, RMS, JMS, etc.) to be configured and
managed from one system window.

X
SA2 The system should allow authorized users to
change commonly altered variables without
intervention from the vendor or IT.

X
SA3 The system should allow multiple (unlimited) users
to be logged into the system and using the same
applications simultaneously.

X
SA4 The system should allow multiple (unlimited) users
to view, add, and edit information in the same
records simultaneously.

X
SA5 The system should provide global search functions
for names, addresses, phone numbers, and
vehicles.

X
SA6 The system should ensure that these search
functions include SOUNDEX, partial, and wild-card
searches.

X
SA7 The system should be able to generate a summary
of each record displayed within these search
results, including digital images.

X
SA8 The system should be able to print, save or email
the search summary directly from the summary
window.

X
SA9 The system should be able to print, save or email a list directly from the list view window. X
SA10 The system should be able to print, save or email a record directly from the record detail window. X
SA11 The system should allow the creation of an agencyspecified header for use within printouts from the system. This header should include both an image
and text.

X
System (Global) Page 72 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
SA12 The system should allow authorized users to
maintain a list of phone number types. X
SA13 The system should allow authorized users to
maintain a list of relationships (for example, spouse,
neighbor, stranger, etc.)
X
SA14 The system should allow authorized users to
maintain a list of agencies. X
SA15 The system should allow authorized users to
electronically redact reports from within the built in
print preview option.

X
SA16 The system should allow authorized users to identify text or images within the report by drawing a box
overtop of the item, and then the system should
replace the underlying item with the box.

X
SA17 The system should convert redacted text to an
image so that the text itself is no longer searchable
or retrievable in any other fashion.

X
Security
ID Requirement Yes Future Modify No Comments
SB1 The system should provide multiple levels of data
security control, including access by user and user
group.

X
SB2 The system should be FIPS 140 compliant for all
network communication, including wired and
wireless communication.

X
SB3 The system should verify access by a username
and its corresponding password. X
SB4 The system should support integration with Active
Directory. X
SB5 The system should support integration with multiple Active Directory servers. X
SB6 The system should support dual-factor
authentication with a username and password and a
USB dongle that meets FBI Security Addendum
Requirements.

X
System (Global) Page 73 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
SB7 The system should never display passwords and
should store passwords as hashed values in the
database.

X
SB8 The system should provide each user with a single
username and password for the entire system. X
SB9 The system should include the following agencyconfigurable password parameters:
- Minimum length
- Case sensitive
- Required to use uppercase and lowercase
- Required to include a numeral
- Frequency of password changes
- Number of previous passwords which cannot be
reused
X
SB10 The system should be able to display agencydefined password parameters when users create or change a password.

X
SB11 The system should allow authorized users to
determine when any user’s password was last
changed and to change any user’s password.

X
SB12 The system should provide access levels, including view, edit, delete, and admin for each component of
the system for users and user groups. X
SB13 The system should track the user who last entered
or updated any record as well as the date and time
of the modification.

X
SB14 The system should store a read-only checksum for
digital files and provide a means of determining if
anyone has tampered with the file.

X
SB15 The system should be able to create an audit record each time a record is created, edited, or viewed. X
SB16 The system should create an audit record each time an audio or video attached to a case report is
exported from the system.

X
System (Global) Page 74 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
SB17 The system should include a screen that displays
users who are currently logged in. X
SB18 The system should include a screen that displays
successful and unsuccessful log-ins and password
changes.

X
Architecture
ID Requirement Yes Future Modify No Comments
SC1 The system should use an n-tier architecture. X
SC2 The system should use an SQL database. X
SC4 The system should include all server hardware.

Network equipment and workstations will be
furnished by the agency.

X
SC5 The system should include 30-minute rolling
backups of all data to an offsite location (not within
the city or county) during which the system
performance cannot be degraded.

X
SC6 The system should include a warm standby server
in the event that the primary server becomes
unavailable.

X
SC7 The system should ensure that the warm standby
server includes the physical servers, server
operating system software, server application and
database software, installation, testing and
configuration.

X
SC8 The system should replicate the production server
data to the warm standby server in near real time. X
SC9 The system should be configured to allow
workstations to connect to the warm standby server
in the event the primary server is unavailable. X
SC10 The system should include a testing/training server. X SC11 The system should ensure that the testing/training server includes the physical servers, server
operating system software, server application and
database software, installation, testing and
configuration.

X
System (Global) Page 75 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
SC12 The system should ensure that the testing/training server allows the users to work with a copy of the
production data without influencing the production
environment.

X
User Interface
ID Requirement Yes Future Modify No Comments
SD1 The system should be able to perform data
validation/error checking for fields in the system. X
SD2 The system should allow specific fields to be
designated as required to force users to enter
essential information before saving a record.

X
SD3 The system should visibly identify required fields (for example, by color-coding them). If a user attempts
to save a record without completing all required
fields, The system should visibly notify the user of
the remaining required fields (for example, by
causing the required fields to flash).

X
SD4 The system should provide auto-completion for
frequently entered information. Once the user
begins typing, the appropriate data should
automatically populate into the record.

X
SD5 The system should use the tab key to move
between fields. X
SD6 The system should include a spellchecker for
narrative fields throughout the system. Users should
be able to add words such as local place names to
the spellchecker’s dictionary.

X
SD7 The system should allow users to use a shortcut key to jump to any menu or submenu link on an open
screen, even if that screen is not currently in focus. X Integration
ID Requirement Yes Future Modify No Comments
System (Global) Page 76 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
SE1 The system should ensure that all of its modules
integrate with other modules (CAD, RMS, JMS,
etc.), are provided by the same vendor, and are not
third-party applications.

X
SE2 The system should use a single database, capable
of being hosted on a single server, for all modules. X
SE3 The system should allow all modules (CAD, RMS,
JMS, etc.) to be accessible to authorized users from
the same application window.

X
SE4 The system should allow all modules (CAD, RMS,
JMS, etc.) to be accessible based on assigned
permissions. All modules should be accessible with
a single click or keystroke, without launching a
separate program or application.

X
SE5 The system should provide a one-time, single point
of data entry to allow information to be accessible
from other modules in the system once it has been
entered.

X
SE6 The system should have consistent user interface
design throughout. X
SE7 The system should be integrated to provide
automatic transfer of critical information between
software modules, including:
- CFS data from CAD transfers to the case reports
in RMS
- Arrest or warrant data in RMS transfers to
booking in JMS
X
SE8 The system should ensure that all modules share
the same master records for names, addresses,
property and vehicles and that these master indices
are located within a single database.

X
SE9 The system should integrate alerts between all
modules so that alerts entered in one area are
available in all others (for example, a dispatcher is
alerted in CAD when a complainant has an
outstanding warrant in RMS).

X
System (Global) Page 77 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
SE10 The system should provide an agency and usercustomizable dashboard that displays summary information from any modules which the user has
permission to access (for example, that user’s open
case reports, the current jail roster, or a list of
recently added warrants).

X
SE11 The system should be able to display dashboard
reminders of overdue and soon-to-be-due tasks for
users or user groups.

X
SE12 The system should be able to display web links on
the dashboard to provide direct links to third-party
websites via the default browser.

X
Master Name Index
ID Requirement Yes Future Modify No Comments
SF1 The system should use a single database, accessed
from all modules, for storing the master name
records. The system should link all activity of a
person (or business) to a single master name
record. If the system does not do the above, please
explain the master name index architecture and
functionality.

X
SF2 The system should link the master name record to
and provide a list of all activity with which the person was involved, including calls for service, case
reports, jail bookings, citations, parking tickets,
warrants, registered vehicles, and anything built with
custom modules.

X
SF3 The system should include links from the activity list on the master name record to any other record in
which the person was involved, in the module the
activity originated. Access to these records should
be controlled by user permissions.

X
SF4 The system should include links to the master name
index from name fields found throughout the
system.

X
System (Global) Page 78 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
SF5 The system should support advanced name
searching based on any combination data elements
in a master name record.

X
SF6 The system should allow first, middle and last
names to be entered in any order in name fields. X
SF7 The system should not require separate search
fields for first, middle, and last names. X
SF8 The system should allow searching for persons and
businesses by full or partial names. X
SF9 The system should connect the alias and the master
name record so that searching for an alias finds that
master record.

X
SF10 The system should include the option of using
SOUNDEX when searching for names. X
SF11 The system should permit the use of age ranges, as well as specified ages on master name records. X
SF12 The system should eliminate the need to duplicate
any name information after it has been entered into
the system.

X
SF13 The system should allow users to update any basic
data fields and add or modify other information on
the master name record once it has been created. X
SF14 The system should display the last modified date on each master name record. X
SF15 The system should cross-reference each master
name record to all other records associated with a
person or business.

X
SF16 The system should automatically add names to the
master name index when entered elsewhere in the
system.

X
SF17 The system should allow users to manually enter
names directly into the master name index. X
SF18 The system should have built-in checking to reduce the possibility of creating duplicate master name
records for the same person or business.

X
System (Global) Page 79 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
SF19 The system should have the ability to merge
duplicate name entries, giving the user the choice of
which name data elements to keep for the merged
record.

X
SF20 The system should allow users to select, view and
merge multiple names at once to a single master
name record rather than having to merge them one
name at a time.

X
SF21 The system should store narrative comments linked
to a name and display it upon inquiry for its master
name record.

X
SF22 The system should display an address history for
persons including dates of address changes. X
SF23 The system should check all coded entries in the
master name index for validity at the time of data
entry.

X
SF24 The system should automatically check a name
against outstanding warrants, known sex offenders
and current jail inmates and notify or alert users
accordingly.

X
SF25 The system should automatically display any userentered name alerts (medical alerts, gang alerts, officer safety threats, and other agency-defined alert
types).

X
SF26 The system should allow users to create new name
alerts from or for a master name record. X
SF27 The system should allow users to specify expiration dates on name alerts. Expired name alerts should
remain attached to master name records for
historical purposes.

X
Master Address Index
ID Requirement Yes Future Modify No Comments
SG1 The system should link all activity occurring at an address to a single master address record. X
SG2 The system should eliminate the need to duplicate
any address information after it has been entered
into the system.

X
System (Global) Page 80 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
SG3 The system should allow users to update any basic
data fields and add or modify other information on
the master address record once it has been
created.

X
SG4 The system should use a single database, accessed
from all software modules, for storing the master
address index so that information entered about an
address in JMS, for example, is available in RMS. If
the system does not do the above, please explain
the master address index architecture and
functionality.

X
SG5 The system should ensure that the each master
address record includes a listing of all persons and
businesses known to reside at the address, which
are included in the master name index.

X
SG6 The system should display the following related
activities with master address records: calls for
service, case reports, and civil process service.

Activities should be listed in reverse chronological
order for each master address record.

X
SG7 The system should include links from the activity list to any record in which the address was involved, in
the module where the activity originated. Access to
these records should be controlled by user
permissions.

X
SG8 The system should provide a notification to the user that an address is either valid or invalid. For invalid addresses, the system should display a list of
potential valid addresses.

X
SG9 The system should link to the master address index
from address fields anywhere in the system. X
SG10 The system should cross-reference each master
address record to all other records associated with
that address.

X
SG11 The system should allow users to manually enter
addresses directly into the master address index. X
System (Global) Page 81 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
SG12 The system should provide a report that shows
manually added addresses. X
SG13 The system should have built-in checking to
automatically merge differently-typed addresses that
correspond to the same location (for example,
"5000 Pacific Boulevard" and "5000 pacific blvd"
should not create duplicate address records).

X
SG14 The system should be able to merge address
records (for example, "NORMS Restaurant" and
"2500 E. 2500 Slauson Ave." are the same address
and should be treated as such).

X
SG15 The system should automatically display any userentered address alerts (hazardous materials, alarm system, water supply information, officer safety
threats, and other agency-defined alert types).

X
SG16 The system should allow users to create new
address alerts from a master address record. X
SG17 The system should allow users to specify expiration dates on address alerts. Expired address alerts
should remain attached to the master address
record for historical purposes.

X
SG18 The system should allow searching for address by
house number, full or partial street name, state, or
zip code.

X
SG19 The system should ensure that searching for a
merged address record finds the appropriate master
address record (for example, searching on "NORMS
Restaurant" finds "2500 E. 2500 Slauson Ave.").

X
Master Vehicle Index
ID Requirement Yes Future Modify No Comments
SH1 The system should link all activity for a vehicle to a single master vehicle record. X
System (Global) Page 82 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
SH2 The system should eliminate the need to duplicate
any vehicle information after it has been entered
into the system.

X
SH3 The system should allow users to update any basic
data fields and add or modify other information on
the master vehicle record once the master vehicle
record has been created.

X
SH4 The system should use a single database, accessed
from all software modules, for storing the master
vehicle index so that information entered about a
vehicle in CAD, for example, is available in RMS. If
the system does not do the above, please explain
the master vehicle index architecture and
functionality.

X
SH5 The system should include a listing in the master
vehicle record, with history, of the vehicle's
registered owners.

X
SH6 The system should display the following related
activities with the master address index: calls for
service, traffic stops, tow calls, case reports,
citations, field identifications, and parking tickets.

Activities should be listed in reverse chronological
order for each master vehicle record.

X
SH7 The system should include links from the activity list to any record in which the vehicle was involved, in
the module where the activity originated. Access to
these records should be controlled by user
permissions.

X
SH8 The system should link to the master vehicle record from vehicle fields anywhere in the system. X
SH9 The system should cross-reference the master
vehicle record to all other records associated with
the vehicle.

X
SH10 The system should allow users to manually enter
vehicles directly into the master vehicle index. X
SH11 The system should have built-in checking to reduce the possibility of creating duplicate master vehicle
records for the same vehicle.

X
System (Global) Page 83 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
SH12 The system should check all coded entries in the
master vehicle record for validity at the time of data
entry.

X
SH13 The system should automatically display any userentered vehicle alerts (including agency-defined alert types).

X
SH14 The system should allow users to create new
vehicle alerts from a master vehicle record. X
SH15 The system should allow users to specify expiration dates on vehicle alerts. Expired vehicle alerts
should remain attached to the master vehicle record
for historical purposes.

X
SH16 The system should support searching for vehicles
by full or partial plate numbers. X
SH17 The system should allow vehicles to be searched by any data element or combination of data elements
(for example, vehicles registered to the name
"Smith" and/or red pickup trucks).

X
Notifications/Messages
ID Requirement Yes Future Modify No Comments
SI1 The system should support "if", "then" and "when"
business rules for notifications throughout the
system.

X
SI2 The system should include system-wide business
rules that allow authorized users to configure
unlimited notification scenarios for users and
workgroups.

X
SI3 The system should provide business logic which,
from information entered into certain required fields,
will automatically display other required and/or
corresponding fields which pertain to the data
already entered.

X
SI4 The system should include business rules that notify users and/or open up the next sequential required
field(s) and/or window(s) based on the information
added to the record.

X
System (Global) Page 84 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
SI5 The system should include system-wide business
rules that allow users and user groups to be notified
via multiple communication channels including
internal system messaging, e-mail, paging, and/or
SMS.

X
SI6 The system should include an internal e-mail-style
messaging system that supports the secure
transmission of messages with attachments within
the agency's network.

X
SI7 The system should warn users that they have
unfinished tasks when they attempt to log out. X
Statutes
ID Requirement Yes Future Modify No Comments
SJ1 The system should include federal, state, and local statutes. X
SJ2 The system should allow authorized users to create
and update local statutes and/or ordinances in the
system.

X
SJ3 The system should provide a hotkey that can be
used from anywhere in the system to search
statutes by statute numbers, title, and/or text within
a statute description.

X
Attachments
ID Requirement Yes Future Modify No Comments
SK1 The system should allow the attachment of files (for example, .DOC , .XLS, .JPG, .WAV) to specified
record types. Attached files should be able to be
opened or viewed on any workstation by authorized
users who have the necessary third-party
applications (such as MS Word or MS Excel).

X
SK2 The system should support scanning and attaching
documents directly to records in the system without
the need to first save them elsewhere. X
System (Global) Page 85 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
SK3 The system should store attached files on the
vendor’s server within the vendor’s software (not on
an open network folder) for security and ease of
access.

X
Custom Forms
ID Requirement Yes Future Modify No Comments
SL1 The system should allow authorized users to create
custom data collection forms to support agencyspecified functionality, without any intervention from the vendor or IT.

X
SL2 The system should ensure that each custom form is
associated with, and subordinate to, a non-custom
form (the parent form).

X
SL3 The system should allow authorized users to create
an unlimited number of custom forms. X
SL4 The system should ensure that the custom forms
are integral with the rest of the system and not
provided via a third-party application.

X
SL5 The system should support printing the data from
custom forms via an agency-defined output
template and process similar to a mail merge.

X
SL6 The system should allow authorized users to add
unlimited data items from the parent form when
creating a custom form.

X
SL7 The system should allow authorized users to include as many fields for data collection as are necessary
on custom forms, including entirely new fields (not
previously stored in the database) as well as the
following:
- Names from the Master Name Index
- Vehicles from the Master Vehicle Index
- Addresses from the Master Address Index
- Personnel, units, and other agency-defined lists
X
System (Global) Page 86 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
SL8 The system should support the following types of
agency-defined fields for custom forms:
- Address
- Automatic record sequence numbers
- Multiple item select boxes
- Vehicles/Dates/Times
- Dollar value
- Free form text
- Names
- Numbers
- Signatures (for electronic signatures)
- Checkboxes
- Yes/No drop-downs
- Drop-downs from agency-defined lists
X
SL9 The system should allow a custom form to create a
relationship on master name or master address
records when those fields are specified within the
custom form.

X
SL10 The system should allow authorized users to specify the label for each field and data item on a custom
form.

X
SL11 The system should allow authorized users to specify if each field on a custom form is required or not
required.

X
SL12 The system should allow for setting the default
value for each field. X
SL13 The system should allow the authorized users to
arrange the data items and fields in any order on
the form.

X
SL14 The system should make the data items and fields
on custom forms available to the built-in report
generator.

X
SL15 The system should allow records captured via
custom forms to be saved to an external file,
emailed and/or printed.

X
Custom Modules
ID Requirement Yes Future Modify No Comments
System (Global) Page 87 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
SM1 The system should permit authorized users to
create custom modules designed to meet specific
data collection, management, reporting, and output
needs without intervention from the vendor or any
additional costs.

X
SM2 The system should ensure that custom modules are
part of the main software solution and not a thirdparty application.

X
SM3 The system should allow authorized users to create
as many custom modules as desired. X
SM4 The system should allow information captured in
custom modules to be output from the system in
accordance with agency-defined output templates.

X
SM5 The system should allow authorized users to include as many fields for data collection as are necessary
within custom modules, including entirely new fields
(not previously stored in the database) as well as
the following:
- Names from the Master Name Index
- Vehicles from the Master Vehicle Index
- Addresses from the Master Address Index
- Personnel, units, and other agency-defined lists
X
SM6 The system should support the following types of
agency-defined fields for custom modules:
- Dates/times
- Dollar value
- Free form text
- Names
- Numbers
- Signatures (for electronic signatures)
- Checkboxes
- Yes/No drop-downs
- Drop-downs from agency-defined lists
X
SM7 The system should allow authorized users to specify all of the field labels for a custom module. X
System (Global) Page 88 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
SM8 The system should allow authorized users to
arrange and display custom module fields in any
order.

X
SM9 The system should allow all data included in a
custom module to be searched and included in
statistical reports.

X
SM10 The system should allow a custom module to create
an relationship on master name or master address
records when those fields are specified within the
custom module.

X
SM11 The system should allow authorized users to define and filter the list view of the data included within the custom module.

X
SM12 The system should allow records from custom
modules to be directly converted to PDF files within
the system.

X
SM13 The system should allow records from custom
modules to be attached to emails. X
Support and Maintenance
ID Requirement Yes Future Modify No Comments
SN1 The vendor should provide a minimum of 3-4 major
software updates (not bug fixes) per year as part of
the vendor’s software maintenance agreement.

Please include contact information for 5 existing
customers who can verify this.

X
SN2 The vendor should schedule and perform software
updates at no additional cost to the agency as part
of the standard maintenance agreement.

X
SN3 The vendor should load all software updates on the
vendor-provided testing/training server(s) before
loading them on vendor-provided production
servers.

X
SN4 The vendor should provide server operating system
software and database software as part of the
complete system.

X
System (Global) Page 89 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
SN5 The vendor should include all updates,
enhancements, new versions, and upgrades of the
server operating system software and database
software as part of its standard software
maintenance agreement.

X
SN6 The vendor should ensure that the agency will not
have to purchase any third-party server operating
system software updates and/or newer versions as
long as its software maintenance agreement is
maintained.

X
SN7 The vendor should be responsible for the vendorprovided physical server(s). As necessary to support proper system functions, the vendor should either
replace components and/or the entire server(s) as
part of the standard maintenance agreement. This
includes ensuring that system performance criteria
are met and that the server(s) continue to meet the
server operating system and database software
requirements.

X
SN8 The vendor should provide, as part of the standard
maintenance agreement, real-time 24x7x365
monitoring of the vendor-provided physical server(s)
and operating system software to detect and
manage any potential issues with the system.

X
SN9 The vendor should load all system software updates
to the server and then automatically load updates to
each client machine at next startup without any
intervention from the vendor or IT.

X
Data Conversion
ID Requirement Yes Future Modify No Comments
SO1 The vendor should perform data conversion as part
of the project. X
SO2 The vendor should convert the following data:
- Enterprise RMS
- Vision CAD
X
System (Global) Page 90 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
SO3 The vendor should ideally complete all data
conversion before the go live date for the new
system.

X
State/NCIC Queries
ID Requirement Yes Future Modify No Comments
SP1 The system should include an interface to the
state/NCIC system. X
SP2 The system should allow authorized users to run
state/NCIC queries directly from within the system. X
SP3 The system should restrict access to run state/NCIC queries to authorized users or user groups. X
SP4 The system should allow NCIC query returns to
populate Master Name and Master Vehicle records. X
SP5 The system should provide a list of all state/NCIC
queries which have been run and the associated
returns. This list should be filterable by date, query
type, user, and/or workstation.

X
System (Global) Page 91 of 91 7/26/2023
CentralSquare Technologies LLC Agreement

________________________
City of Vernon, CA
Page | 113
Legal Exceptions ____
Request for Proposals - Public Safety Software System

8. CONDITIONS FOR RESPONSES TO RFP
H. All submitted proposals and information included therein or attached thereto shall become public record upon delivery to the City.

CentralSquare Response: CentralSquare requests that in the event of a request for public release of relevant documents, the County shall provide CentralSquare with reasonable notice of the request so that CentralSquare may respond, as well as a copy of said request.

10. STANDARD TERMS AND CONDITIONS
Prior to the award of any work hereunder, City and proposer shall enter into the City’s standard form services agreement attached hereto as Exhibit B. Proposers responding to this RFP are strongly advised to review all the terms and conditions of the Agreement. The term of the Agreement shall not exceed three (3) years pursuant to the Vernon Municipal Code.

CentralSquare Response: CentralSquare will negotiate in good faith with the City to arrive at a contract with mutually acceptable terms and conditions using the City’s standard form services agreement as the basis for negotiations. CentralSquare has provided exceptions and/or comments to certain sections of the City’s sample contract as provided in the RFP, and proposes that the resulting contract shall contain revised provisions. Additionally, CentralSquare requests that additional terms and provisions be included in the resultant contract, including but not limited to software license, warranties, and system acceptance.

EXHIBIT B - STANDARD FORM AGREEMENT

4.0 TERM. The term of this Agreement shall commence on [state date], and it shall continue until [state date which may not be more than three years from the commencement date], unless terminated at an earlier date pursuant to the provisions thereof.

CentralSquare Response: CentralSquare proposes that the “Term” provision of the resultant contract shall also include renewal language. The contract which will govern the project and implemented system will need to include terms and conditions relative to ongoing support and maintenance, the terms of which will control such ongoing maintenance and support for the life of the system. Therefore, mutually acceptable renewal language beyond the initial term will need to be included.

CentralSquare Technologies LLC Agreement

________________________
City of Vernon, CA
Page | 114

9.0 INDEMNITY. Contractor agrees to indemnify City, its officers, elected officials, employees and agents against, and will hold and save each of them harmless from, any and all actions, suits, claims, damages to persons or property, losses, costs, penalties, obligations, errors, omissions or liabilities (herein “claims or liabilities”), including but not limited to professional negligence, that may be asserted or claimed by any person, firm or entity arising out of or in connection with the work, operations or activities of Contractor, its agents, employees, subcontractors, or invitees, provided for herein, or arising from the acts or omissions of Contractor hereunder, or arising from Contractor’s performance of or failure to perform any term, provision, covenant or condition of this Agreement, except to the extent such claims or liabilities arise from the gross negligence or willful misconduct of City, its officers, elected officials, agents or employees.

CentralSquare Response: CentralSquare will indemnify and hold harmless the City for direct damages arising from the negligent or wrongful acts or omissions of CentralSquare, its employees or agents, subject to a limitation of liability provision as further defined in section

5.0 (copied below for reference) of CentralSquare’s Software License and Service Agreement:
“5.0 Indemnification and Limitation of Liability
CentralSquare shall indemnify, defend and hold harmless Customer from any and all claims, lawsuits or liability, including attorneys' fees and costs, allegedly arising out of, in connection with, or incident to any loss, damage or injury to persons or property or arising from a wrongful or negligent act, error or omission of CentralSquare, its employees, agents, contractors, or any subcontractor as a result of CentralSquare’s or any subcontractor’s performance pursuant to this Agreement; however, CentralSquare shall not be required to indemnify Customer for any claims or actions caused to the extent of the negligence or wrongful act of Customer, its employees, agents, or contractors. Notwithstanding anything to the contrary in the foregoing, if a claim, lawsuit or liability results from or is contributed to by the actions or omissions of Customer, or its employees, agents or contractors, CentralSquare’s obligations under this provision shall be reduced to the extent of such actions or omissions based upon the principle of comparative fault.

Notwithstanding the foregoing, the aggregate liability of CentralSquare for any reason and upon any cause of action of claim, including, without limitation, CentralSquare’s obligation to indemnify and hold harmless under this agreement, shall be limited to direct damages which shall not exceed (i) the amount of the fees paid for the portion of the System giving rise to such claims in the aggregate, including, without limitation, breach of contract, breach of warranty, indemnity, negligence, strict liability, misrepresentations, and other torts; or (ii) for claims arising under annual maintenance, the amount of the maintenance fees paid for the term in which the claim arises.

CentralSquare Technologies LLC Agreement

________________________
City of Vernon, CA
Page | 115

IN NO EVENT SHALL CENTRALSQUARE, ITS SUBCONTRACTORS OR SUPPLIERS

BE LIABLE WHETHER IN CONTRACT OR IN TORT FOR LOST PROFITS, LOST

SAVINGS, LOST DATA, LOST OR DAMAGED SOFTWARE, OR ANY OTHER

CONSEQUENTIAL OR INCIDENTAL DAMAGES ARISING OUT OF, OR OTHERWISE

RELATED TO THIS AGREEMENT, REGARDLESS OF WHETHER

CENTRALSQUARE HAS NOTICE OF THE POSSIBILITY OF ANY SUCH LOSS OR DAMAGE.”

10.0 INSURANCE. Contractor shall, at its own expense, procure and maintain policies of insurance of the types and in the amounts set forth below, for the duration of the Agreement, including any extensions thereto. The policies shall state that they afford primary coverage… CentralSquare Response: CentralSquare carries and maintains insurance in policy types and coverage amounts that meet or exceed the requirements of the City’s RFP. Upon award, CentralSquare will provide the City with a fully prepared Certificate of Insurance including the City as additional insured on all applicable policies.

CentralSquare has reviewed the City’s insurance requirements and provides the following clarifications or exceptions:
• AUTO – CentralSquare does not own any autos; therefore, CentralSquare’s auto policy will not include any language for owned autos.
• CANCELLATION/NOTICE – CentralSquare’s insurance broker/carrier does not communicate directly with CentralSquare’s client base; all insurance related communications will be provided directly by CentralSquare. Therefore, the Certificate of Insurance will not contain any notice of cancellation or material change language. • FULL INSURANCE POLICIES – CentralSquare’s full insurance policies contain sensitive information relative to CentralSquare as a privately held company, and are never shared with its clients or the public.

11.0 GENERAL TERMS AND CONDITIONS

11.4 CORRECTION OF WORK. Contractor shall promptly correct any defective, inaccurate or incomplete tasks, deliverables, goods, services and other work, without additional cost to the City. The performance or acceptance of services furnished by Contractor shall not relieve the Contractor from the obligation to correct subsequently discovered defects, inaccuracy, or incompleteness.

CentralSquare Response: For clarification purposes, CentralSquare will provide the deliverables and services, including but not limited to support and maintenance of the system, in accordance with CentralSquare’s standard support provisions and the terms of the mutually agreed upon contract.

CentralSquare Technologies LLC Agreement

________________________
City of Vernon, CA
Page | 116

11.0 GENERAL TERMS AND CONDITIONS

11.8 NO ASSIGNMENT. Contractor shall not assign or transfer this Agreement or any rights hereunder without the prior written consent of the City and approval by the City Attorney, which may be withheld in the City's sole discretion. Any unauthorized assignment or transfer shall be null and void and shall constitute a material breach by the Contractor of its obligations under this Agreement. No assignment shall release the original parties from their obligations or otherwise constitute a novation.

CentralSquare Response: CentralSquare proposes that the Assignment clause in the resultant contract be mutual; that neither party may assign the contract without the prior written consent of the other party, the consent of which may not be unreasonably withheld.

11.0 GENERAL TERMS AND CONDITIONS

11.11.5 Order of Precedence. In case of conflict between the terms of this Agreement and the terms contained in any document attached as an Exhibit or otherwise incorporated by reference, the terms of this Agreement shall strictly prevail. The terms of the City’s Request for Proposals shall control over the Contractor’s Proposal.

CentralSquare Response: CentralSquare proposes that the final negotiated contract shall include all applicable terms and conditions and will reflect the mutually agreed upon project.

The RFP provides the City’s subjective criteria, to which Proposers have provided subjective responses based on the content of the RFP. The final negotiated contract and statement of work will provide the objective criteria for the project. CentralSquare proposes that the order of precedence be revised as follows:

1. Amendments to the Agreement

2. The Agreement

3. The Statement of Work

4. The RFP as modified by the Proposer’s response thereto.

CentralSquare Technologies LLC Agreement

________________________
City of Vernon, CA
Page | 117

11.0 GENERAL TERMS AND CONDITIONS

11.17 TERMINATION FOR CONVENIENCE (Without Cause). City may terminate this Agreement in whole or in part at any time, for any cause or without cause, upon fifteen (15) calendar days' written notice to Contractor. If the Agreement is thus terminated by City for reasons other than Contractor's failure to perform its obligations, City shall pay Contractor a prorated amount based on the services satisfactorily completed and accepted prior to the effective date of termination. Such payment shall be Contractor's exclusive remedy for termination without cause.

11.18 DEFAULT. In the event either party materially defaults in its obligations hereunder, the other party may declare a default and terminate this Agreement by written notice to the defaulting party. The notice shall specify the basis for the default.

The Agreement shall terminate unless such default is cured before the effective date of termination stated in such notice, which date shall be no sooner than ten (10) days after the date of the notice. In case of default by Contractor, the City reserves the right to procure the goods or services from other sources and to hold the Contractor responsible for any excess costs occasioned to the City thereby. Contractor shall not be held accountable for additional costs incurred due to delay or default as a result of Force Majeure. Contractor must notify the City immediately upon knowing that nonperformance or delay will apply to this Agreement as a result of Force Majeure. At that time Contractor is to submit in writing a Recovery Plan for this Agreement. If the Recovery Plan
is not acceptable to the City or not received within 10 days of the necessary notification of Force Majeure default, then the City may cancel this order in its entirety at no cost to the City, owing only for goods and services completed to that point.

11.19 TERMINATION FOR CAUSE. Termination for cause shall relieve the terminating party of further liability or responsibility under this Agreement, including the payment of money, except for payment for services satisfactorily and timely performed prior to the service of the notice of termination, and except for reimbursement of (1) any payments made by the City for service not subsequently performed in a timely and satisfactory manner, and (2) costs incurred by the City in obtaining substitute performance. If this Agreement is terminated as provided herein, City may require, at no additional cost to City, that Contractor provide all finished or unfinished documents, data, and other information of any kind prepared by Contractor in connection with the performance of Services under this Agreement. Contractor shall be required to provide such document and other information within fifteen (15) days of the request.

CentralSquare Technologies LLC Agreement

________________________
City of Vernon, CA
Page | 118
CentralSquare Response: CentralSquare proposes a mutual termination provision, which grants either party the right to terminate if (i) for breach, following thirty (30) days’ notice to the defaulting party, provided that such default has not been cured within such thirty (30) day period, such provision substantially similar to the terms set forth in Section 6.0 of CentralSquare’s Software License and Service Agreement, excerpted below for the City’s review:

Termination
“6.2 By CentralSquare for Cause
In addition to various other express rights of CentralSquare to terminate this Agreement set forth herein, CentralSquare shall also have the right to terminate this Agreement upon thirty (30) day’s prior written notice and cancel any unfulfilled portion of it by written notice to Customer due to Customer’s failure to comply with any material terms or conditions of this Agreement, or in other cases if: (i) Customer becomes bankrupt or insolvent or enters into any arrangement or composition with its creditors or if a receiver is appointed to direct the business of Customer, or (ii) Customer sells or assigns its rights, duties or obligations under this Agreement to any person or entity, in whole or in part, whether by assignment, merger, transfer or assets, sale of stock, operation of law or otherwise, without the express written permission of CentralSquare or (iii) upon Customer’s breach of the use or confidentiality and nondisclosure provisions contained herein, or (iv) upon a violation of CentralSquare’s proprietary rights hereunder. The termination of this Agreement shall automatically terminate and extinguish the right to use CentralSquare Software.

6.3 By Customer for Cause
Customer may terminate this Agreement for cause based upon the failure of CentralSquare to comply with any material terms and/or conditions of the Agreement, provided that Customer shall give CentralSquare thirty (30) days’ written notice specifying CentralSquare’s failure. If within thirty (30) days after receipt of such notice, CentralSquare shall not have either corrected such failure or, in the case of failure which cannot be corrected in thirty (30) days, begun in good faith to correct said failure and thereafter proceeded diligently to complete such correction, then Customer may, at its option, place CentralSquare in default and the Agreement shall terminate on the date specified in such notice.

6.4 Termination without Cause
After the fifth Renewal Term, this Agreement and the Software use granted herein may be terminated by either party by providing notice one-hundred eighty (180) days prior to the date the next Renewal Term payment is due.

CentralSquare Technologies LLC Agreement

________________________
City of Vernon, CA
Page | 119

6.5 Post-Termination Obligations
All provisions hereof relating to CentralSquare’s proprietary rights, confidentiality, nondisclosure and non-solicitation shall survive the termination or expiration of this Agreement. Any fees due as per Exhibit C: Payment Schedule for work completed prior to termination shall still be paid by Customer. In the event of termination of this Agreement prior to implementation of the CentralSquare Software, or termination due to Customer’s breach of CentralSquare’s intellectual property rights, the use of the CentralSquare Software granted under this Agreement shall also terminate and Customer shall remove all Server Hardware and at CentralSquare’s direction, either return or destroy the Server Hardware.”

11.0 GENERAL TERMS AND CONDITIONS

11.20 MAINTENANCE AND INSPECTION OF RECORDS. The City, or its authorized auditors or representatives, shall have access to and the right to audit and reproduce any of the Contractor's records to the extent the City deems necessary to insure it is receiving all money to which it is entitled under the Agreement and/or is paying only the amounts to which Contractor is properly entitled under the Agreement or for other purposes relating to the Agreement.

The Contractor shall maintain and preserve all such records for a period of at least three (3) years after termination of the Agreement.

The Contractor shall maintain all such records in the City of Vernon. If not, the Contractor shall, upon request, promptly deliver the records to the City of Vernon or reimburse the City for all reasonable and extra costs incurred in conducting the audit at a location other than the City of Vernon, including, but not limited to, such additional (out of the City) expenses for personnel, salaries, private auditors, travel, lodging, meals, and overhead.

CentralSquare Response: CentralSquare will maintain all applicable records and other material related to the contract for the required timeframe but does not agree to the City’s conditions for inspection or audit. Any audit or inspection of CentralSquare’s records shall occur upon reasonable notice and shall take place at CentralSquare’s principal place of business. Any costs associated with such audit or inspection shall be the responsibility of the City. Additionally, the City’s access to such records will require the execution of applicable non-disclosure agreements.

CentralSquare Technologies LLC Agreement

________________________

EXHIBIT B
SCHEDULE – PRICING AND PAYMENT DETAILS
CentralSquare Technologies LLC Agreement

________________________
CentralSquare Technologies LLC Agreement

________________________
CentralSquare Technologies LLC Agreement

________________________
CentralSquare Technologies LLC Agreement

________________________
CentralSquare Technologies LLC Agreement

________________________
CentralSquare Technologies LLC Agreement

________________________
Payment Schedule
The total amount of this contract is $272,288.94.

City of Vernon Migration Terms
The City of Vernon entered into a prior agreement for VISIONAir Software products with TriTech Software Systems (a CentralSquare Technologies company), and is a currently licensed end user of such VISIONAir Software. Whereas this Agreement is a migration from the legacy VISIONAir solution to CentralSquare Pro Suite, this Agreement will replace and supersede the City’s existing applicable VISIONAir Agreement and relevant system(s).

The City must pay all applicable support fees for its existing VisionAIR system up to the date of Go Live for the Contractor software in order to receive the upgrade discount.

The amounts due under this contract are as follows:

Upon contract execution 50% $84,506.50
Completion of BPR 30% $50,703.90
Go Live 20% $33,802.60
Annual Subscription Fee – due upon Go Live 100%
Year One $103,275.94
Year Two $103,275.94
Year Three $103,275.94
Year Four $103,275.94
Year Five $103,275.94
Travel Expenses and Other Reimbursements* Must be approved in advance by City
Contractor shall deliver to City an invoice: (a) within thirty (30) days of completion of the corresponding milestone as evidenced above; and (b) thirty (30) days prior to each Anniversary Date for each annual Subscription Fee. All payments are due within thirty (30) days of receipt of any invoice. In the event of a disputed invoice, City shall pay the entire non-disputed portion of any such invoice. *Travel Expenses and Other Reimbursements: City shall reimburse Contractor only for those costs or expenses specifically approved in this Agreement, or specifically approved in writing in advance by City.

Unless otherwise approved, such costs shall be limited and include nothing more than the following costs incurred by Contractor: Actual costs and/or other costs and/or payments specifically authorized in advance in writing and incurred by Contractor in the performance of this Agreement.

CentralSquare Technologies LLC Agreement

________________________
The remittance address for payments only is:

CentralSquare Technologies
12709 Collection Center Drive
Chicago, IL 60693

EXHIBIT C

EQUAL EMPLOYMENT OPPORTUNITY

PRACTICES PROVISIONS
A. Contractor certifies and represents that, during the performance of this Agreement, the contractor and each subcontractor shall adhere to equal opportunity employment practices to assure that applicants and employees are treated equally and are not discriminated against because of their race, religious creed, color, national origin, ancestry, handicap, sex, or age. Contractor further certifies that it will not maintain any segregated facilities.

B. Contractor agrees that it shall, in all solicitations or advertisements for applicants for employment placed by or on behalf of Contractor, state that it is an "Equal Opportunity Employer" or that all qualified applicants will receive consideration for employment without regard to their race, religious creed, color, national origin, ancestry, handicap, sex or age.

C. Contractor agrees that it shall, if requested to do so by the City, certify that it has not, in the performance of this Agreement, discriminated against applicants or employees because of their membership in a protected class.

D. Contractor agrees to provide the City with access to, and, if requested to do so by City, through its awarding authority, provide copies of all of its records pertaining or relating to its employment practices, except to the extent such records or portions of such records are confidential or privileged under state or federal law.

E. Nothing contained in this Agreement shall be construed in any manner as to require or permit any act which is prohibited by law.

CentralSquare Technologies LLC Agreement

________________________
EXHIBIT D – STATEMENT OF WORK
(ATTACHED)
CentralSquare Technologies LLC Agreement

________________________
1 Exhibit D: Statement of Work
CentralSquare will provide Software, Hardware, and Services substantially similar to those outlined below, in the quantities specified in the Quote.

1.0 Software
The software detailed in the following sections includes, but is not limited to, the listed functionality.

Pro Suite Base • Operating system software
• Database software
• Master name index
• Master address index
• Master vehicle index
• Secure intra-Customer
messaging
• Configurable dashboard
• Web address links
• No duplicate data entry
• Authentication
CAD (Core) • Command-line entry
• Bulletins
• Configurable CAD Windows
• Inactivity Alarms
• Rip and Run
• Full audit trail
• Command Log
• Triple I
• Custom CAD Commands
• Unit Alarms
• ANI/ALI
CAD (Advanced) • Alarm Billing
• Alarm Calls
• Nurse Calls
• Scheduled and Recurring
Scheduled Calls
• Tow Calls
• Custom Forms
• NCIC Automation
• Basic Paging
• Run Cards and Unit
Recommendation
• Unit Specialties
• Web windows
CAD – Agency Site License • Allows agencies named
herein to access and use
Customer’s CentralSquare
CAD system
Note: Many items are configurable by agency. All other configuration must be agreed upon between Customer and Primary Agency.

CentralSquare Technologies LLC Agreement

________________________
2 Mapping (Core) – Server
Based
• Command-line entry
• Drag and drop commands
• Visual status alerts
• User-configurable map layers
• GIS functions with map
window closed
• Quickest path unit
recommendation
• Active calls for service
• Call for service click-through
• Custom map markers
• Address verification
• Faster map functions
(compared with non-server
version)
• Required for 15 or more AVL
units
Mapping – Agency Site
License
• Allows agencies named
herein to access and use
Customer’s CentralSquare
Mapping system
Note: Many items are configurable by agency. All other configuration must be agreed upon between Customer and Primary Agency.

Mapping AVL • Vehicle locations on map • Call for service integration Mapping AVL – Agency Site
License
• Allows agencies named
herein to access and use
Customer’s CentralSquare
Mapping AVL system
Note: Many items are configurable by agency. All other configuration must be agreed upon between Customer and Primary Agency.

Mapping AVL Playback • Displays on the map
• View by time, by unit, by CFS
• Print or export playback data
Mobile Core • Grants access to the
CentralSquare Mobile
application
Mobile AVL • Vehicles shown on map • Call for service integration CentralSquare Technologies LLC Agreement

________________________
3 Mobile CAD • User-configurable layouts
• Day/Night mode
• Instant messaging
• Silent dispatch
• Bulletins/BOLOS
• NCIC queries
Mobile Mapping • Active calls for service
• Map Markers
• Visual status alerts
• User configurable map layers
• Route from current location to
CFS location
Mobile Records • Cases
• Warrants
• Master index access (including
mug shots and alerts)
Personnel (Core) • Personnel Log • Full audit trail
Personnel (Advanced) • Commendations
• Disciplinary Actions
• Positions
• Promotions
• Service History
• Training
• Citizen Feedback
Personnel – Agency Site
Licenses
• Allows agencies named
herein to access and use
Customer’s CentralSquare
Personnel system
Note: Many items are configurable by agency. All other configuration must be agreed upon between Customer and Primary Agency.

Public Safety Citizen
Reporting (P2C)
• Standalone application
• Online reporting platform for
citizens to report nonemergency incident reports
Records (Core) • Case Reports
• NIBRS/UCR Submission
• Master Record Notes
• Protection Orders
• Warrants
• Juvenile Referral List
• Pawn Property
• Pistol Permits
• Sex Offenders
• Full audit trail
CentralSquare Technologies LLC Agreement

________________________
4 Records (Advanced) • Field Identifications
• Expungement
• Intelligence Cases
• Investigative Leads
• Form Requirements
• Tow Calls
• Bicycle Registrations
• Parking Tickets
• Custom Forms
Records - Agency Site License • Allows agencies named
herein to access and use
Customer’s CentralSquare
Records system
Note: Workflow and personnel related items are configurable by agency. All other configuration must be agreed upon between Customer and Primary Agency.

Reporting (Core) • Pre-defined reports
• Custom reports
• Ad-hoc reports
• Drag and drop report
building
• Export to PDF, XLS, XML, TXT
• Custom data filters
• Statistical analysis
• Scheduled reports
• COMSTAT compatible
• Emailed reports
CentralSquare Field Ops • CJIS compliant mobile device
app
• Integrated photo and audio
capture tools
• Real-time CFS data access
• Uses existing CentralSquare
Suite user credentials
Community Data Platform
(CDP)
• Search engine for
CentralSquare Suite CAD and
RMS Data
• Up to 10 concurrent users
supported
• State-wide data sharing
CentralSquare Technologies LLC Agreement

________________________
5 1.1 Interfaces
All costs related to CentralSquare’s implementation of the following interfaces is represented in the Quote. Customer shall contact all interface third-party vendors notifying them about their integration to CentralSquare Suite. Any third-party costs or charges incurred related to the implementation of the following interfaces will be the responsibility of Customer.

Any interfaces that cannot be deployed as part of System go-live due to Customer or a third-party vendor not being ready for deployment shall not delay Software or Hardware Acceptance.

Customer shall not allow any party, other than CentralSquare, to add, update, or delete database records or file system objects directly to or on the server or database except as provided for in the CentralSquare Documentation.

CentralSquare backend server software is wholly managed by CentralSquare and the Customer shall not attempt to access it, except as provided in the CentralSquare Documentation. Customer shall not cause any software except the Software provided under this Agreement to be installed on or executed on the Server Hardware.

Refer to Statement of Work: 3.2 Implementation Process overview for interface implementation information.

Standard Interfaces
The following are sold as standard interfaces. There will be no software modifications or changes to these standard interfaces:

1.1.1 CAD – Basic Paging Interface (SMTP/Email) (Export) This is a one-way interface from CentralSquare CAD. Pages are sent via email from CentralSquare CAD.

CentralSquare enables the paging functionality in CAD.

Customer is responsible for configuring paging groups, templates, and trigger events for this interface.

1.1.2 CAD – E911 (ANI/ALI) Interface (Import) – Vesta
This is a one-way interface from the 911 service provider to CentralSquare CAD. It prepopulates calls for service by parsing raw spill data from the 911 service and importing it.

Customer is responsible for ensuring that:
(a) 911 service provider sets up the serial connection from the 911 controller to CentralSquare CAD. (b) 911 spill data can be pushed to CentralSquare CAD at a decided upon frequency. (c) ALI data meets NENA standards

1.1.3 CAD – Rip and Run Interface (Fax/Email)
This is a one-way interface from CAD to fax and email services. Completed Calls for Service (CFS) from CAD are output (printed) to the services. CentralSquare provides the connection from CentralSquare Suite to the SMTP server.

Customer will provide CentralSquare with SMTP information for setup and will manage all user CentralSquare Technologies LLC Agreement

________________________
6 configurations.

1.1.4 Records –CA Crime Reporting (NIBRS) Interface
This is a one-way interface from CentralSquare Records to CA NIBRS. Customer is able to select cases in CentralSquare Records and manually export those cases to a text file on the local file system. From there, Customer provides the file to the state system. CentralSquare creates functionality to support the text file export from CentralSquare Records.

1.1.5 Pro Suite –JDIC/NCIC Interface (Basic Queries)
This is a two-way interface between Pro Suite and the CentralSquare-provided NCIC server. The following basic queries will be generated by Pro Suite and passed to the NCIC server: The CentralSquare-provided NCIC server then sends the queries on to NCIC and collects the results. Those query results are then sent back to Pro Suite.

Customer is responsible for providing a network connection and the necessary authentication to the state message switch from the NCIC server. NCIC data mining results will only be returned for the state in which Customer is located.

1.1.6 Pro Suite – Time Synchronization Interface
This is a one-way interface that uses NTP to keep all CentralSquare server’s clocks in sync.

1.2 Data Conversion
CentralSquare will provide data conversion services from one (1) of Customer’s current software database sources to one (1) CentralSquare database module. For example, Customer’s current CAD database will be converted to CentralSquare CAD. The contents of the data conversion will be determined by the Data Conversion Specification documents.

The listed data conversion services and their associated costs are based on CentralSquare's understanding of Customer's needs and current system. Any modules not explicitly listed in this section are not a part of the current project scope and will not be included in implementation. If additional module conversions are required, each one will come at an additional cost based on the scope of the work required for each.

Customer shall work with its existing vendors to obtain unencrypted data for conversion in one of the following compatible formats:
(a) MS SQL .bak files with database version and credential information from MSSQL Server 2008R2 or newer
(b) MySQL .dump or .sql files with database version and credential information (c) PostgreSQL .sql files with database version and credential information (d) MS Access 2003 or newer .mdb files
(e) CSV files with column headers and relationship mapping documentation (f) Oracle 10g or newer backup files

1.2.1 VisionAIR CAD
Data will be converted into the CentralSquare CAD module from the VisionAIR database and data will be CentralSquare Technologies LLC Agreement

________________________
7 provided in one of the formats listed above. Data will be in a form substantially similar to that of the provided.

1.2.2 Enterprise RMS
Data will be converted into the CentralSquare Records module from the Enterprise RMS database and data will be provided in one of the formats listed above. Data will be in a form substantially similar to that of the provided.

1.2.3 VisionAIR CAD Admin
Data will be converted into the CentralSquare Jail module from the VisionAIR CAD Admin database and data will be provided in one of the formats listed above. Data will be in a form substantially similar to that of the provided.

1.2.4 VisionAIR CAD Personnel
Data will be converted into the CentralSquare Records module from the VisionAIR CAD Personnel database and data will be provided in one of the formats listed above. Data will be in a form substantially similar to that of the provided.

1.2.5 One-Time GIS Data Set Up
In CentralSquare’s efforts to make sure that Customer-supplied GIS data is working to the best of its abilities, CentralSquare will run a series of tests to ensure that the GIS data is ready for first installation.

In addition, the data will be set up with the proper configuration and loaded into an ArcGIS map document that is required for the software to operate. Address locator and network dataset files will be created and updated for proper geocoding and routing abilities.

A thorough GIS data review by Customer is imperative for an effective and organized CentralSquare software Go Live.

CentralSquare cannot make any guarantees for the spatial nor the tabular accuracy of Customer-supplied GIS data as it pertains to geocoding results, routing, and searching. Customer understands that there are several steps involved to make the GIS data sufficiently perform the abovementioned functions. If Customer is unable to make these corrections on its end, a GIS data contract can be set up with CentralSquare to ensure the data is built according to the desired specifications.

CentralSquare will apply one (1) GIS update per month to the Customer’s map as part of this contract.

2.0 Customer Hardware, Network and Power Requirements
CentralSquare is not responsible for physical installation of the computer hardware required for operating CentralSquare Software. CentralSquare is not responsible for networking any hardware.

Unless otherwise specified, Customer will be responsible for providing the following to meet the hardware, network and power requirements for the System.

2.1 Server Hardware

1. Three (3) rack-mount servers will be purchased by Customer as part of this agreement.

2. Three (3) CentralSquare Suite servers will be configured as follows:
(a) One (1) Production server with Lantronix remote access device CentralSquare Technologies LLC Agreement

________________________
8 (b) One (1) Warm Standby server with Lantronix remote access device (c) One (1) Testing/Training server

3. The servers will be installed at Vernon Police, CA and a standby location.

4. In addition to the standard CentralSquare Suite operating environment, the Production and Standby servers will have the capability of running the following on a virtual machine:
(a) One (1) virtual NCIC server (message switch)
(b) One (1) virtual GIS server

5. Ten (10) inches of rack space is required at the primary server location for one (1) CentralSquare Suite Production rack-mounted server (3.5”), one (1) CentralSquare Suite Testing/Training rackmounted server (3.5”), and one (1) Lantronix remote access device (3.0”).

6. Six and one-half (6.5) inches of rack space is required at the standby server location for one (1) CentralSquare Suite Standby rack-mounted server (3.5”) and one (1) Lantronix remote access device (3.0”).

2.2 Production and Testing/Training Server Network Requirements

1. Six (6) open Ethernet cables and ports to be used by one (1) CentralSquare Suite Production rackmounted server, one (1) CentralSquare Suite Testing/Training rack-mounted server, and one (1) Lantronix remote access device.

2. Static IP addresses that include four (4) for the CentralSquare Suite Production rack-mounted server, three (3) for the CentralSquare Suite Testing/Training rack-mounted server, and one (1) for the Lantronix remote access device.

3. Network access that maintains low-latency and high bandwidth that includes a Virtual Private Network (VPN) to support remote users per the requirements that are set forth in the Network Requirement Specifications and Server Requirement Specification documents provided by CentralSquare.

2.3 Production and Testing/Training Server Power Requirements

1. One (1) uninterrupted power supply (UPS) that support 1000 watts.

2. Power supply that will handle dual 720 watts for one (1) CentralSquare Suite Production rackmounted server, one (1) CentralSquare Suite Testing/Training rack-mounted server, and one (1) Lantronix remote access device.

3. Server cooling that will ensure the appropriate temperatures for one (1) CentralSquare Suite Production rack-mounted server, one (1) CentralSquare Suite Testing/Training rack-mounted server, and one (1) Lantronix remote access device.

2.4 Peripheral Hardware
Records – Property & Evidence Barcode Scanner and Printer Package (Wasp) This contract will provide for one (1) property and evidence barcode scanner and printer package that will CentralSquare Technologies LLC Agreement

________________________
9 include one (1) wireless Wasp WWS550i barcode scanner, one (1) Wasp WPL305 label printer, and four (4) rolls of labels.

3.0 Services

3.1 Project Management
Customer shall provide one primary Project Manager to be the main point of contact for CentralSquare.

A single, Project Manager will be assigned to manage the project for all Customers included in this installation.

Customer will identify a CentralSquare Build Team. With assistance from CentralSquare Implementation Analysts, Customer’s Build Team is responsible for the configuration of CentralSquare software. The Build Team should expect to devote 10-20% of each week of implementation to CentralSquare configuration work.

Customer’s Project Manager and Build Team will work within standard business hours (7:00 AM CST to 7:00 PM CST, Monday through Friday) to enable mutual availability to work with CentralSquare on configuration and project activities.

3.1.1.1 Customer’s Dedicated Project Manager Responsibilities

1. Have the authority to speak for Customer from a project perspective.

2. Designate people responsible for specific roles as needed, examples below:
(a) Module Subject Matter Experts (SMEs)
(b) Hardware Project Manager
(c) CentralSquare Build Team Members
(d) Data Conversion Review Team Members
(e) Interface points of contact at Customer (assigned per interface)

3. Involve Customer decision makers when needed

4. Escalate issues to the CentralSquare project manager

5. Eliminate roadblocks for completing project on schedule

6. Sign various project documents and ensuring signoff documents and deliverables are provided to CentralSquare project manager in a timely manner

7. Organize training schedules, training rooms, and training equipment

8. Provide real world scenarios for testing and review

3.1.2 CentralSquare Project Manager and Project Team
From the start of the project, a CentralSquare project manager will work with Customer as the single point of contact for implementation of the CentralSquare Suite system. The project manager will develop and manage the implementation schedule and will coordinate with Customer to keep the project on track and on schedule. The project manager will conduct weekly status meetings to provide Customer with project CentralSquare Technologies LLC Agreement

________________________
10 updates.

The CentralSquare project team, under the direction of the project manager, will visit pertinent areas of Customer and will meet with key Customer personnel to understand Customer’s operational needs and business rules. Team members will observe Customer’s daily operations first-hand and use that information to identify how the CentralSquare Suite system would best be configured to match and enhance Customer’s workflows. The project team will train Customer system administrators on configuration options and code table setup.

3.2 Implementation Process Overview
CentralSquare uses a multi-phase approach to ensure a successful implementation for each Customer.

Trained and experienced members of the CentralSquare implementation team move through the process with Customers to ensure successful outcomes. Timelines will be discussed with Customer’s project manager and will be mutually agreed upon to ensure a successful Go Live.

3.2.1 Kickoff Meeting
Upon contract signature, a kickoff meeting is scheduled to initiate the implementation process, setting up a statement of work, server installations and scheduling the Business Practice Review (BPR).

3.2.2 Business Practice Review
During this meeting, the CentralSquare project team works with Customer’s build team and will demo CentralSquare Suite modules and guide the agency on their configuration tasks.

3.2.2.1 Configuration
Customer plays a large part in the configuration and setup of the final system. Configuration of CentralSquare software is guided by Consultants, via remote online sessions, but is considered a Customer responsibility to complete.

3.2.2.2 Data Conversion and GIS Data Conversion
Data not contained in systems listed in Statement of Work: 1.2 Data Conversion will not be converted.

Code tables, data mapping, and other system configuration will be entered by Customer with the assistance of a CentralSquare Consultant. Code tables will not be part of the converted data.

A major part of data conversion is review of data that has been converted to CentralSquare software.

Customer plays a key role in this data review.

A thorough data conversion review by Customer is imperative for an effective and organized CentralSquare software Go Live. Customer should expect to devote 10-20% of each week of the data conversion process to CentralSquare configuration work. Each module converted will require participation of SMEs.

See Statement of Work: 1.2.5 GIS Data Conversion for information regarding the GIS data conversion process.

3.2.2.3 Interfaces
See Statement of Work: 1.1 Interfaces for a list of included interfaces.

Customer tasks related to interfaces will start immediately after the initial CentralSquare kickoff meeting.

Customer will set up conference calls with CentralSquare and each interface vendor within two weeks of contract signing or one week of kickoff call. Interfaces to and from CentralSquare software are created CentralSquare Technologies LLC Agreement

________________________
11 and tested internally before being available for Customer testing.

Customer is responsible for initiating and facilitating the relationship(s) between CentralSquare and the third-party interface vendor(s).

CentralSquare software interface specifications must be clearly defined in the Interface One Sheet or Interface Specifications Document. If applicable, each interface will be thoroughly tested by Customer before Go Live.

3.2.3 Final System Review
Throughout the project, implementation analysts from CentralSquare will schedule sessions with Customer’s Build Team and end users to review any questions or concerns.

3.2.4 Train-the-Trainer and/or End User Training
CentralSquare offers several options for end user training. All of the training options provide hands-on use of the software with real-world examples. Class sizes are limited to ensure that each individual has sufficient time to practice using the system. When the go live date arrives, users are well-prepared to begin using the new software.

3.2.5 Go Live
CentralSquare provides on-site the day that the new system goes live. Any questions that arise are addressed immediately by the team, ensuring that the first day(s) using the new system goes smoothly.

3.2.6 Software Acceptance
Customer acknowledges that the Software shall be deemed accepted on the date of delivery. In the event that a Customer notifies CentralSquare of a material non-conformity in the Software as compared with the Statement of Work, CentralSquare shall use commercially reasonable efforts to correct the reported non-conformity in accordance with the support provisions set forth in Exhibit E: Maintenance Agreement.

3.2.7 Hardware Acceptance
Customer acknowledges that the Hardware shall be deemed accepted on the date of delivery. In the event that a Customer notifies CentralSquare of a material non-conformity in the Hardware as compared with the Statement of Work, CentralSquare shall use commercially reasonable efforts to correct the reported non-conformity.

3.3 Training and Go Live Support

3.3.1 Training
CentralSquare staff will provide for remote training.

3.3.1.1 System Configuration and Training
The first portion of training will be performed by the CentralSquare project team. Team members will train and guide Customer’s Build Team in configuring the CentralSquare Suite system, setting up and maintaining code tables, managing users and user rights, among other options. Through CentralSquareguided configuration of the system, the Build Team becomes well versed in the CentralSquare software system administration.

3.3.1.2 Train-the-Trainer and/or End User Training
Instructors will conduct detailed courses for each of Customer’s user groups (such as dispatchers or CentralSquare Technologies LLC Agreement

________________________
12 officers). The content of each course will be tailored to the features and functionality in CentralSquare software that each group needs to know and use.

3.3.2 Training Resources
Training will be scheduled within standard business hours (7:00 AM CST to 7:00 PM CST, Monday through Friday).

The training facilities and equipment will be provided by Customer based on the following:

3.3.2.1 Instructor Resources

1. One (1) computer with a network connection

2. Most recent CentralSquare Suite version installed and tested (includes login)

3. Two (2) projectors and two (2) screens set up and tested

3.3.2.2 Trainee Resources

1. Five (5) to ten (10) computers with network connections two (2) monitors required (three (3) monitors are suggested)

2. One (1) supervisor will attend every class to address policy questions

3. No more than ten (10) trainees in each class

4. Most recent CentralSquare Suite version installed and tested (includes login)

5. All third-party devices (i.e., printers, scanners, barcode reader, mugshot camera) connected and tested

3.3.3 Go Live Support
CentralSquare staff will assist users with questions that arise during Go Live and will reinforce skills learned during the training sessions. CentralSquare staff will be on site for Go Live.

CentralSquare Technologies LLC Agreement

________________________
Exhibit E: Support Addendum

1.0 Term
Support will be provided in accordance with this Support Addendum for the Term of the Agreement so long as all Subscription Fees are current and paid in full.

2.0 Software Updates
While this Agreement remains in full force and effect, CentralSquare will maintain the Software by providing software updates and/or enhancements to Customer. All software updates provided to Customer by CentralSquare pursuant to the terms of this Agreement shall be subject to the terms and conditions of Section 2.0 License of this Agreement.

CentralSquare will install software updates remotely. Customer is responsible for guaranteeing that sufficient, capable personnel that possess the appropriate technology skills and public safety knowledge are available during the maintenance window. All updates will occur during normal business hours.

Normal business hours are defined as: 08:00-17:00 CT. Software updates are offered in the following time slots: 08:00-10:00 CST, 10:00-12:00 CST, 13:00-15:00 CST. CentralSquare Technologies will work with the Customer to schedule an agreeable time to occur during these time slots.

2.1 Included Updates
Updates will be provided on an as-available basis and include the items listed below:

1. Bug fixes;

2. Enhancements to products provided under this Agreement;

2.2 Not-Included Updates
Updates do not include:

1. Platform extensions including product extensions to different platforms (premise, hosted, cloud), different windowing system platforms, or different operating system platforms

2. New functions such as new modules, interfaces, components, products, or applications.

3.0 Hardware Updates
Server Hardware updates consist of different types of hardware changes ranging from hardware replacement (such as replacing a hard disk), to hardware additions and hardware updates. Server Hardware updates require physical access to the servers. Customer is responsible for guaranteeing that sufficient, capable personnel that possess the appropriate technology skills and public safety knowledge are available during the maintenance window. All updates will occur during normal business hours.

Normal business hours are defined as: 08:00-17:00 CT. Hardware updates are offered in the following time slots: 08:00-10:00 CST, 10:00-12:00 CST, 13:00-15:00 CST. CentralSquare Technologies will work with the Customer to schedule an agreeable time to occur during these time slots.

CentralSquare Technologies LLC Agreement

________________________

4.0 Support

4.1 General Support
CentralSquare shall provide phone and email support for the Software licensed under this Agreement and shall maintain a support center database to track any reported issues. Customer is required to accept and maintain updates to a supported version of the application(s) in order to maintain access to support services. No support will be provided for Software more than two versions back from the most recently released version.

Support does not include custom programming services or training.

Support is available 24 hours a day, seven days a week for CentralSquare Suite customers.

4.2 Remote Support
The BeyondTrust/Bomgar and/or SecureLink remote support solutions shall be the method of remote access to customer systems and/or data. These solutions meet all requirements as contained in Section

5.5.6 of the FBI CJIS Security Policy (Remote Access). Use of either of these solutions enable customer agencies to remain CJIS compliant for purposes of FBI and/or state regulatory agency audits.

VPN usage to connect to customer environments is prohibited. If previously contractually mandated, all costs associated with CentralSquare’s use of any technological device to mitigate against the risk of such connection shall be the responsibility of Customer. This includes but is not limited to jumpboxes, virtual machines, etc. Any access to Customer’s system and/or data shall be through the use of CentralSquare’s unique user SSO credentials, and all such access must be capable of being logged in accordance with FBI CJIS Security Policy.

4.3 GIS Data Maintenance
GIS data updates and maintenance are defined as changes to the GIS data based on actual additions or changes to points (e.g. addresses), lines (e.g. roads), or layers (e.g. Emergency Service Zones) that occur after the date of the software install.

CentralSquare will provide one (1) GIS update per month as part of this contract.

4.4 Server Hardware Maintenance
CentralSquare will maintain the Server Hardware necessary to host the Software. This does not include any hardware except the CentralSquare Technologies’ supplied Server Hardware. “Server Hardware Maintenance” is defined as ensuring the operating system and/or applications as installed are current and up to date.

A standby server is available for purchase by customer. This server replicates the production environment and is available to the customer for use in the event of a hardware and/or software failure of the production server. The training server is similar to the production server but it is not a mirror image of CentralSquare Technologies LLC Agreement

________________________
same. The training server cannot be utilized as a production server or other means to support the agency with respect to the Pro application and/or interfaces thereto in the event of a hardware failure of the production server.

In the event of a hardware and/or software failure, if the customer does not purchase a standby server, the customer acknowledges that the customer will be down for an extended period of time which could include, but not be limited to, an extended period of time while replacement hardware and/or software is attained and/or configured for use.

4.5 Customer Responsibilities

4.5.1 Access to Premises
Customer shall provide CentralSquare with reasonable and timely access to the sites and personnel necessary for CentralSquare to perform its obligations under this Agreement.

4.5.2 CentralSquare Server Access
Customer will ensure that all CentralSquare Server Hardware are directly network accessible to CentralSquare at all times via SSH. There shall be no additional authorization or equipment required except as requested by CentralSquare. The persistent SSH secured service connection is mandatory and necessary for the proper functionality of the managed server component and/or the Pro application by the CentralSquare Technologies DevOps team. This connection is only utilized by CentralSquare Technologies’ CJIS-compliant employees for purposes that include but are not limited to, contractually mandated backups, installation of major and minor software releases and/or execution of the managed service component of the Agreement.

4.5.3 Network Configuration Notification Requirements
Customer shall notify CentralSquare regarding all updates to Customer’s network configuration, firewall changes, and IP address updates with a minimum twenty-four (24) hour notice prior to implementation of such changes.

4.5.4 System Administrator
Customer is responsible for naming one or more System Administrators to serve as a primary point of contact between Customer and CentralSquare. At least one System Administrator must be available at all times. Customer will ensure that the System Administrators possesses the appropriate technology and public safety knowledge and skills to perform this role sufficiently.

4.5.5 Security
Customer is responsible for providing all physical security. The customer is responsible for securing their network.

4.5.6 System Updates
Customer shall work in good faith to allow CentralSquare to install System updates as requested by CentralSquare.

CentralSquare Technologies LLC Agreement

________________________
Community Data Platform Membership Page 1 of 9

COMMUNITY DATA PLATFORM MEMBERSHIP PROGRAM
Client: City of Vernon (for the benefit of and use by Vernon Police Department) Membership
A. CentralSquare Technologies, LLC (“CentralSquare”) offers qualifying Member Agencies access to IQ Search and CrimeMapping.com limited services (the Software and Services) as defined in this Agreement.

B. Clients who wish to qualify as a Member Agency must:
a. Be a CJIS compliant Law Enforcement Agency
b. Agree to contribute data to the Community Data Platform including:
i. CAD
ii. RMS Incidents
iii. RMS Arrests
iv. RMS Warrants
v. RMS Master Names
c. Agree to allow CentralSquare to share their data with other Member Agencies and third parties as provided in this Agreement
C. The Member Agency (also referred to herein as “Client”) will receive the following benefits:

Free subscription to IQ Search for up to 10
Concurrent Users, limited to the following:

Your
Contributed
Data
Your State’s
Participating
Agencies
National
Participating
Agencies
RMS Incidents
• QuickView (Date of Occurrence,
Location, Incident Type Description,
Case Status, RMS Case Number,
Agency)

YES YES
CAD Call for Service
• QuickView YES
Free subscription to CrimeMapping.com
Public access to:

Radius searches of crime data from a specified location Map-based summary of RMS Incident statistics based on crime type, description, location, agency, date
Register for alerts on RMS Incident activity within a certain radius of a location and/or crime type
Map-based citizen/public access to categorized RMS Incidents A free 90-day trial to the national IQ Search service which includes full detailed searches.

D. The Member Agency will receive up to 10 concurrent user licenses to the Community Data Platform.

E. In consideration of the free subscription to IQ Search and CrimeMapping.com as defined above, Client understands and agrees that CentralSquare will process and anonymize CentralSquare Technologies LLC Agreement

________________________
Community Data Platform Membership Page 2 of 9
data from the IQ Community Data Platform (the “Aggregate Data”) to provide further commercial services for its clients and third parties as described below.

F. Full search concurrent user licenses can be purchased to increase concurrent user access and search/query builder capabilities.

License
Membership includes a limited non-exclusive, non-transferable license to use the Software and Services, located on CentralSquare’s servers, through Client’s computer(s).

The Software and Services provide users an effective set of tools for conducting investigations, monitoring regional crime trends, and increasing transparency to the community.

Client is expressly prohibited from sublicensing, selling, renting, leasing, providing service bureau or timeshare services, distributing or otherwise making the Software and Services available to third parties.

Access and Passwords
A. Access to IQ Search by Client’s authorized end users (“Authorized Users”) will require the use of a password. Client is responsible for management and control of passwords for its end users.

B. Client acknowledges (i) that the protection of passwords issued to Authorized Users is an integral part of CentralSquare’s security and data protection process and procedures and, (ii) that CentralSquare will rely on Client utilizing and maintaining proper password control obligations and procedures. In the event that Client has reasonable cause to believe that a password is being improperly used by an Authorized User or used by an unauthorized person, Client shall promptly notify CentralSquare. CentralSquare reserves the right to deactivate a compromised password immediately upon notice from Client without further notice to Client or the affected Authorized User. CentralSquare shall have the right, at its sole cost and expense, to utilize an independent certified accounting firm, to verify the number of passwords that have been issued for use by Authorized Users of the Client and use of these passwords within Client’s organization in compliance with the terms of this Agreement.

Termination
A. This Agreement may be terminated by CentralSquare upon thirty (30) days’ written notice due to a material breach by Client.

B. Either Party may terminate this Agreement for convenience upon thirty (30) days’ written notice to the other Party.

Client Responsibilities
A. Client will assign a Client Administrator to manage end user access and passwords.

B. Client is responsible for providing hardware, operating system and browser software that meets CentralSquare’s technical specifications, as well as providing and maintaining a fast, stable, high-speed connection and remote connectivity for data contribution services as well as individual client user access.

C. Client is solely responsible for the integrity of all data and information that is provided to CentralSquare under this Agreement (i.e., the Client Information), including CentralSquare Technologies LLC Agreement

________________________
Community Data Platform Membership Page 3 of 9
completeness, accuracy, validity, authorization for use and integrity over time, regardless of form and format, and whether or not such data is used in conjunction with the Subscription Services.

D. Client shall not attempt to decode, disassemble, copy, transmit, transfer or otherwise reverse engineer the Services, including, without limitation, the Software.

E. Client is responsible for maintaining an active e-mail account for correspondence with CentralSquare.

F. Client is responsible for proper firewall maintenance allowing for data to move from their on-premise data contributing system to the applicable IQ application.

Confidentiality
A. In association with the execution of this Agreement and CentralSquare’s participation in the use and support of the Software and Services, Client has obtained, will have access to, or will obtain confidential information regarding intellectual property of CentralSquare, the Software and Services and its contents, sales and marketing plans and other similar information (hereinafter referred to as "Confidential Information"). Client acknowledges that the Software and Services itself represents and embodies certain trade secrets and confidential information of CentralSquare. Client hereby agrees that, for itself and its shareholders, officers, directors, employees, and agents, Client shall not disclose any of CentralSquare’s trade secrets or Confidential Information without CentralSquare’s prior written consent for any such disclosure.

B. In association with the execution of this Agreement and the participation of CentralSquare in the support of the Software and Services, CentralSquare has obtained or will obtain confidential information of Client regarding the business of Client or its customers (“Client Information”). CentralSquare shall not use any Client Information except as expressly set forth in this Agreement.

C. Confidential Information of either Party shall not include any information that is (i) already known to the receiving Party at the time of the disclosure; (ii) publicly known at the time of the disclosure or becomes publicly known through no wrongful act or failure of the receiving Party; (iii) subsequently disclosed to receiving Party on a non-confidential basis by a third party not having a confidential relationship with the other Party hereto that rightfully acquired such information; (iv) communicated to a third party by receiving Party with the express written consent of the other Party hereto; or (v) legally compelled to be disclosed pursuant to a subpoena, summons, order or other judicial or governmental process, provided the receiving Party provides prompt notice of any such subpoena, order, etc. to the other Party so that such Party will have the opportunity to obtain a protective order.

D. Each Party agrees to restrict access to the Confidential Information or Client Information of the other Party to those employees or agents who require access in order to use or support the Software and Services, acknowledging that certain Confidential Information or Client Information of each Party may be disclosed to Authorized Users as a necessary function of the Software and Services; and, except as otherwise provided, neither Party shall make Confidential Information or Client Information available to any other person or entity without the prior written consent of the other Party.

E. Notwithstanding the foregoing, Client understands and agrees that CentralSquare may transfer Client Information to a third party hosting entity for the purposes of providing the communications infrastructure, hosting services and/or related support and other operations necessary to deliver all or certain portions of the Services; provided that CentralSquare Technologies LLC Agreement

________________________
Community Data Platform Membership Page 4 of 9
CentralSquare, in turn, binds such third party to confidentiality and non-disclosure terms that are at least as protective of CentralSquare’s and Client’s interests as the terms stated herein. In addition, CentralSquare may also access and use Client Information and results or data, in a de-identified form, for data or analysis purposes (including for the purpose of preparing the Aggregate data and for crime data reporting), and may distribute the results of such analysis or data summaries to other Member Agencies or third parties provided no personally identifying information in the Client Information is disclosed. Client acknowledges that CentralSquare shall have no responsibility or liability for unauthorized access to or dissemination of Client Information by Authorized Users or other third parties, whether as a result of breach of data security, misappropriation or misuse of passwords or any other cause.

Ownership and Rights
A. CentralSquare owns all rights and title in and to the Software and Services. Further, Client agrees that the Software screens and any output of the Software, excepting the Client Information, are the property of CentralSquare and subject to United States and other patent, copyright, trademark, trade secret and other applicable laws and treaties and Client agrees that it shall not remove, alter or obstruct any ownership or use legends that CentralSquare places on any such screens or output of the Services. Nothing contained in this Agreement shall be construed as granting Client any rights in or to the Software and Services (including, without limitation, the Software and output of the Services), the deliverables from the implementation or additional services or related Confidential Information, other than the right to use the Software and Services and any applicable Confidential Information of CentralSquare during the Term, in accordance with this Agreement.

B. Clients who elect to participate in the Membership Program contribute to a database of information utilized by members to conduct investigations, monitor regional crime trends, and increase transparency to their communities. Notwithstanding anything to the contrary herein, excluding CJIS data, or personally identifying data, Client agrees that CentralSquare has and retains all rights to use any data and information relating to the Software and Services that is uploaded, inputted, or otherwise submitted by Client for any commercial purposes during or after the term of this Agreement; and any information that constitutes, or results in, an improvement or other modification to the Software and Services. CentralSquare shall retain all rights and ownership to the Aggregate Data.

C. As between the parties, CentralSquare agrees that all Client Information provided to CentralSquare under this Agreement for CentralSquare’s use in connection with the Software and Services is the property of Client; provided, however, CentralSquare shall have the right to retain Client Information in accordance with its obligations under the terms of this Agreement in the event that the return or the destruction of any Client Information is infeasible, and in any event may use and retain Client Information as provided in Section E of the “Confidentiality” section above.

D. The term “Developments” shall mean all programs, upgrades, updates or other enhancements or modifications to the Software, if any, and all Documentation or other materials developed and/or delivered by CentralSquare in the course of providing technical support or otherwise, under this Agreement.

E. Client will not have the ability to copy the Client Information entered onto the Software.

Rather, CentralSquare shall retain the physical copy of the Software, title, right and interest in and to the Software, including upgrades, updates, and/or other enhancements or modifications to the Software in any medium, including but not limited to all copyrights, patents, trade secrets, trademarks, and other proprietary rights.

CentralSquare Technologies LLC Agreement

________________________
Community Data Platform Membership Page 5 of 9
F. CentralSquare reserves the right to provide free cloud storage only for those data items viewable as part of the Limited Search Capabilities. Additional data attached to contributions such as video, images, and other document types may induce optional storage fees for cloud retention.

Liability
A. THE SERVICES, SOFTWARE AND ANY DOCUMENTATION ARE MADE AVAILABLE FOR CLIENT'S USE “AS IS” AND EXCEPT AS OTHERWISE SPECIFICALLY

STATED HEREIN, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR

IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

B. CENTRALSQUARE DOES NOT WARRANT THAT THE SOFTWARE WILL OPERATE UNINTERRUPTED OR ERROR-FREE. CLIENT AGREES TO INDEMNIFY

CENTRALSQUARE AGAINST ANY SUCH LIABILITY TO CLIENT, REGARDING THE CLIENT’S USE OF THE SERVICES, THE SOFTWARE AND ANY DOCUMENTATION OR OTHERWISE. IN NO EVENT SHALL CENTRALSQUARE BE LIABLE TO CLIENT

OR ANY THIRD PARTY, WHETHER IN CONTRACT, TORT, OR OTHERWISE FOR

INCIDENTAL, SPECIAL, INDIRECT, GENERAL, OR CONSEQUENTIAL DAMAGE OR

LOSS OF ANY NATURE, INCLUDING BUT NOT LIMITED TO LOSS OF BUSINESS

PROFITS, INCOME, LOSS OR USE OF DATA, WHICH MAY ARISE IN

CONNECTION WITH THIS AGREEMENT OR THE USE OF OR INABILITY TO USE

THE SERVICES, SOFTWARE AND ANY DOCUMENTATION EVEN IF

CENTRALSQUARE HAD BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THIS CLAUSE SHALL SURVIVE FAILURE OF AN EXCLUSIVE REMEDY.

C. CENTRALSQUARE DISCLAIMS ALL LIABILITY FOR THE ACCURACY AND/OR

COMPLETENESS OF DATA, INCLUDING BUT NOT LIMITED TO DATA SUPPLIED

WITH THE SOFTWARE OR AS ADDED OR MODIFIED BY CLIENT OR ANY THIRD PARTY, OR DATA AS PROCESSED ON CLIENT'S OR CENTRALSQUARE’S COMPUTER NETWORK. CLIENT BEARS THE ENTIRE RESPONSIBILITY FOR ITS

COMPUTER NETWORK, INCLUDING CLIENT'S USE OF THE SOFTWARE, THE

PERFORMANCE OF THE SERVICES AND THE SOFTWARE AND THE BEHAVIOR OF THE DATA ON EITHER CLIENT'S OR CENTRALSQUARE’S COMPUTER NETWORK.

D. CENTRALSQUARE REPRESENTS AND WARRANTS TO CLIENT THAT, TO CENTRALSQUARE’S CURRENT AND ACTUAL KNOWLEDGE, THE SOFTWARE,

WHEN USED IN ACCORDANCE WITH THIS AGREEMENT, DOES NOT VIOLATE ANY EXISTING U.S. COPYRIGHTS, PATENTS, TRADEMARKS, OR OTHER

INTELLECTUAL PROPERTY RIGHTS OF ANY THIRD PARTY AS OF THE DATE OF THIS AGREEMENT. CENTRALSQUARE SHALL INDEMNIFY AND HOLD CLIENT

HARMLESS FROM AND AGAINST ANY AND ALL ACTIONS, SUITS,

PROCEEDINGS, CLAIMS, DEMANDS, LOSSES, LIABILITIES, COSTS AND EXPENSES, INCLUDING REASONABLE ATTORNEYS’ FEES, INCURRED BY

CLIENT ARISING OUT OF ANY BREACH OF THIS WARRANTY ON THE PART OF CENTRALSQUARE.

E. IN NO EVENT SHALL CENTRALSQUARE’S TOTAL CUMULATIVE LIABILITY

HEREUNDER, FROM ALL CAUSES OF ACTION OF ANY KIND, WHETHER ARISING

UNDER CONTRACT, TORT (INCLUDING NEGLIGENCE), STRICT LIABILITY,

BREACH OF WARRANTY OR OTHERWISE, EXCEED THE VALUE OF ONE

ANNUAL TERM OF THE SUBSCRIPTION FEES FOR IQ SEARCH AND
CRIMEMAPPING.COM.

CentralSquare Technologies LLC Agreement

________________________
Community Data Platform Membership Page 6 of 9
Assignment
Client shall not transfer or assign any of its rights or obligations under this Agreement to any other person or entity without the express written permission of CentralSquare, which permission shall not be unreasonably withheld. Any assignment without such express written permission of CentralSquare shall result in the automatic termination of this Agreement.

Notices
Written notices required or permitted to be given under this Agreement shall be made to the parties at the following addresses and shall be presumed to have been received by the other party (i) (three) 3 days after mailing by the party when notices are sent by First Class Mail, postage prepaid; (ii) upon transmission (if sent via facsimile with a confirmed transmission report); or (iii) upon receipt (if sent by hand delivery or courier service).

To Client: To CentralSquare:

City of Vernon CentralSquare Technologies, LLC
Attn: Attn: Contracts
4305 South Santa Fe Avenue 1000 Business Center Drive
Vernon, CA 90058 Lake Mary, FL 32746
Governing Law
Except to the extent that this Agreement is governed by the laws of the United States, this Agreement shall be governed, interpreted and enforced in accordance with the laws of the State of California, without regard to its conflict of law provisions.

Support Services
Support will be provided in accordance with Attachment A.

This Agreement does not include any other CentralSquare subscription services. Additional subscription services purchased by Client will be subject to applicable fees.

Agreement
This Agreement may be executed in any number of identical counterparts, and each such counterpart shall be deemed a duplicate original thereof.

City of Vernon, a California charter City and
California municipal corporation
By: ____________________________
Carlos Fandino, City Administrator
CentralSquare Technologies, LLC, a Delaware
Limited Liability Company
By:

Name:

Title:

ATTEST:
_______________________________
Lisa Pope, City Clerk
By:

Name:

Title:

CentralSquare Technologies LLC Agreement

________________________
Community Data Platform Membership Page 7 of 9
APPROVED AS TO FORM:
_______________________________
Zaynah N. Moussa,
City Attorney
CentralSquare Technologies LLC Agreement

________________________
Community Data Platform Membership Page 8 of 9
Schedule A

TECHNICAL SUPPORT
This Schedule describes the terms and conditions relating to technical support that CentralSquare will provide to Client during the Term of the Agreement.

Technical Support Services:

Client may contact CentralSquare for issues with IQ Search via the following: by phone at (800) 987-0911 or via the Customer Portal: https://support.centralsquare.com. Assistance may include remote connectivity, modem, or electronic bulletin board.

Software Problem Reporting. Client may submit requests to CentralSquare identifying potential problems in the Software. Requests should be in writing and directed to CentralSquare by e-mail.

CentralSquare retains the right to determine in its sole discretion the final disposition of all requests, and will inform Client of the disposition of each request. If CentralSquare decides in its sole judgment to act upon a request, it will do so by providing a bug fix as described above.

Scheduled Maintenance. IQ applications may be unavailable periodically for system maintenance. Regular system maintenance includes installation of the IQ Updates, operating system updates/patches and updates to other third-party applications as needed. Clients are notified of maintenance periods via an email message.

Exclusions from Technical Support Services:

CentralSquare shall have no support obligations with respect to any third-party hardware or software product (“Nonqualified Product”). If CentralSquare provides support services for a problem caused by a Nonqualified Product, or if CentralSquare’s service efforts are increased as a result of a Nonqualified Product, CentralSquare will charge time and materials for extra service at its current published rates for custom software services. If, in CentralSquare’s opinion, performance of technical support is made more difficult or impaired because of a Nonqualified Product, CentralSquare shall so notify Client, and Client will immediately remove the Nonqualified Product at its own risk and expense during any efforts to render technical support under this Agreement. Client shall be solely responsible for the compatibility and functioning of Nonqualified Products with the Software.

Client Responsibilities:

In connection with CentralSquare’s provision of technical support as described herein, Client acknowledges that Client has the responsibility to do each of the following:
1) Provide hardware, operating system and browser software that meets CentralSquare’s technical specifications, as well as a fast, stable, high-speed connection and remote connectivity.
2) Maintain the designated computer system and associated peripheral equipment in good working order in accordance with the manufacturers’ specifications, and ensure that any problems reported to CentralSquare are not due to hardware malfunction; 3) Maintain the designated computer system at the latest code revision level deemed necessary by CentralSquare for proper operation of the Software; 4) Supply CentralSquare with access to and use of all information and facilities determined to be necessary by CentralSquare to render the technical support described herein; CentralSquare Technologies LLC Agreement

________________________
Community Data Platform Membership Page 9 of 9
5) Perform any test or procedures recommended by CentralSquare for the purpose of identifying and/or resolving any problems;
6) At all times follow routine operator procedures as specified in the Documentation set forth in the online portal(s) used to access the service;
7) Other than CentralSquare’s confidentiality obligations with respect to Client Information as set forth in this Agreement, Client shall remain solely responsible at all times for the safeguarding of Client’s proprietary, confidential, and classified information; and 8) Ensure that the designated computer system is isolated from any process links or anything else that could cause harm before requesting or receiving remote support assistance.

CentralSquare Technologies LLC Agreement

________________________