Documente Academic
Documente Profesional
Documente Cultură
Notice
Copyright © 2017, Spillman Technologies, Inc. All rights reserved. The information contained herein is proprietary to
Spillman Technologies, Inc.
Spillman Technologies, Inc., reserves the right to make improvements and changes in the product described in this
publication at any time and without notice, and may revise this publication from time to time without notice.
Spillman Technologies, Inc., provides this publication “as is” without warranty of any kind, either expressed or implied,
including but not limited to the implied warranties or conditions of merchantability or fitness for a particular purpose.
While every precaution has been taken in the preparation of this manual and its representation of the product, the
publisher and author assume no responsibility for errors, omissions, or any damages or loss of data as a result of said
errors or omissions.
Spillman, Spillman Flex, Summit, Sentryx, Involvements, Spillman Touch, Visual Involvements, and CrimeMonitor are
federally registered trademarks of Spillman Technologies, Inc. Spillman InSight and Integrated Hub are trademarks of
Spillman Technologies, Inc. All other registered or unregistered trademarks and names are the property of their
respective owners.
Table of Contents
Preface 7
Other manuals 7
Windows basics 7
Manual conventions 8
1 User Information 11
Introduction 12
Using CrimeMonitor 13
Using Analytics 14
Opening Analytics 15
Closing Analytics 16
Creating dashboards 64
Creating a dashboard 64
Selecting a dashboard 65
Creating reports 67
2 Administrator Information 77
Introduction 78
A Appendix A 139
Understanding geographic profiling 139
Assumptions of geographic profiling 140
Other manuals
The Application Setup and Maintenance Manual provides information for the
Spillman Applications Administrator (SAA) at your agency, including
procedures for installing and maintaining the software. The Code Table Setup
and Maintenance Manual provides information on adding and maintaining
your agency’s code tables. The Security Setup and Maintenance Manual
provides information on protecting your agency’s system and setting up
system privileges.
Windows basics
Before using the software, be familiar with the standard features of
Microsoft® Windows®. At a minimum, know how to do the following:
Use a mouse or keyboard to perform basic tasks, such as choosing
menu options and buttons
Work with windows, such as selecting, minimizing, restoring,
maximizing, sizing, scrolling, closing, and so forth
Work with dialog boxes
If these tasks are unfamiliar, then refer to your Windows online
documentation or complete an online Windows tour.
Manual conventions
When using this manual, note the following conventions.
angle bracket (>) Shows the menu option(s) that must be From the Start menu, select All Programs >
between items selected, in sequence, to get to a specific Spillman > Spillman Mobile.
option.
plus sign (+) between Used for keys that are pressed at the same Press Ctrl+E.
keys time. Hold down the first key, and then Click Close, or press Ctrl+F4.
press the other key(s). When a keystroke
is available for a mouse action, both the
mouse action and the keystroke are
presented.
comma (,) between Used for keys that are pressed in Press Alt, F, O to open the File Options dialog box.
keys sequence. Press and release each key, in
the order shown.
Courier font Used for displayed text. The software prompts: Are you sure you
Used for table names. want to delete this record?
Open the Names table (nmmain).
bold Courier Used for information you enter. Enter the street address, such as 401 W
font Sycamore St.
italics Used for emphasis. Enter the date, using the mm/dd/yyyy format.
Used for variable information you supply.
NOTE
Notes call attention to information that is of particular importance or that varies
depending on a particular condition, such as the way your Spillman Application
Administrator (SAA) has configured the software.
TIP
Tips present recommendations, optional actions, and additional ways to perform
specific tasks.
CAUTION
Cautions point out actions that might endanger your data or its integrity
(usefulness) or cause other problems later.
User Information
Jump to topic:
Introduction 12
Using CrimeMonitor 13
Opening Analytics 15
Using the Menu Pane 19
Using the Analytics Tabs 36
Using the Menu Bar and Toolbar 61
User Information
1 Introduction
Introduction
CrimeMonitor and Analytics are modules that interface with BAIR (Behavior
Analysis and Intelligence Resources) Analytics. The modules each contain
two parts: an application and an interface. The interface exports incident and
call for service data from the software to BAIR, while the application allows
the data to be mapped, analyzed, and reported on.
Because the CrimeMonitor module is not integrated with the software, this
chapter focuses on how to open and use the Analytics module.
For more information about each module, see the following:
“Using CrimeMonitor” on page 13
“Using Analytics” on page 14
Using CrimeMonitor
CrimeMonitor is a public crime map that interfaces with BAIR’s RAIDS
(Regional Analysis and Information Data Sharing) Online product.
CrimeMonitor allows law enforcement to connect to and engage with the
community to reduce crime and improve public safety, including mapping
crime activity and collecting anonymous tips. With CrimeMonitor, seven data
elements are exported from the software and mapped to RAIDS Online to
show incidents within your agency’s jurisdiction. CrimeMonitor data is public
data that can be accessed by any member of the public through the web
application from any web browser. CrimeMonitor is not integrated with the
software.
Once the CrimeMonitor interface is installed and set up, the information that
is exported to BAIR RAIDS is displayed on the map found at
https://raidsonline.com/?rms+spillman_crime.
Anyone can view the information displayed on the map, including basic
analysis of the data, such as what types of crime occurred most often in a
location or time period.
For more information about using RAIDS Online, see the help documentation
on the RAIDS Online website.
Using Analytics
Analytics is an agency-based crime map and analytics tool that interfaces with
BAIR’s ATACRAIDS (Automated Tactical Analysis of Crime) product.
Analytics offers national crime data sharing, pattern analysis, advanced crime
mapping, and enhanced data analytics, as well as CrimeMonitor. Analytics
also exports up to 140 data elements from incident records to the online map.
Analytics is for law enforcement personnel only, and is accessed through a
secure connection within the software.
The following sections describe how to use the Analytics application:
“Opening Analytics” on page 15
“Understanding the Analytics Screen” on page 17
“Using the Menu Pane” on page 19
“Using the Analytics Tabs” on page 36
“Using the Menu Bar and Toolbar” on page 61
Opening Analytics
Once the Analytics interface is installed and set up, the exported information
can be viewed using a web application that is accessed through one of the
following ways:
Through the software. See “Accessing Analytics through the
software” on page 15.
Through a secure web address. See “Accessing Analytics without the
software” on page 15.
When Analytics is accessed, the Analytics screen opens in a web browser. For
more information, see “Understanding the Analytics Screen” on page 17.
Accessing To open the Analytics application from the software, do one of the following:
Analytics through
At the command line, enter analytics.
the software
From the command center, on the menu bar, click the Analytics button.
Analytics button
2. Enter the email address connected to your user name and password,
and then click Sign In.
NOTE
Your SAA must have the Single Sign On Connector (SSOC) application deployed
and running to enable the Analytics button in Flex and Mobile, and to allow the
Analytics application to be opened remotely. For more information, contact your
SAA.
Closing Analytics
When finished with your Analytics session, do not exit the web browser.
Make sure to click the Logout button from the menu bar to log out. Logging
out ensures that the Analytics data is secure, and that your dashboards and
polygons are saved correctly.
NOTE
The Analytics website has a 30-minute timer. If no changes are made to the page
for 30 minutes, then, to protect your agency’s data, the session automatically
ends. Any changes that were not saved are lost.
Menu pane
Menu pane. Used to select the data that is displayed, including the
type, location, and date range of the incidents. Also used to select the
analytic and agency layers to display on the map. For more
information, see “Using the Menu Pane” on page 19.
NOTE
Analytics is only as powerful as the data exported to it. If the data is inaccurate or
missing, then Analytics cannot provide a complete analysis of crime in your
agency’s jurisdiction. Make sure your agency has data entry procedures in place
to encourage accurate and complete data entry.
Due to the limits of web applications, the maximum number of records that can be
displayed in Analytics at one time is 500. However, when a report is created, up
to 10,000 records can be included.
5. To display only incidents that occurred within the buffer, select the
Only display crimes within buffer check box.
IR Number link
Incident icon
NOTE
If the Analytics application is opened from outside of the software, then the IR
Number link is displayed, but it does not work because it is not connected to the
database. However, the Show Full Record link still works.
NOTE
To create an analytic layer, at least two incidents must be displayed on the map.
Some analytic layers require more incidents to be displayed.
Depending on the number of incidents displayed on the map, it can take several
seconds for the calculations to be completed.
2. Select the check box for the layer to display on the map. For more
information about the analytic layer options, see the following
sections:
– “Using the Density Map analytic layer” on page 27
– “Using the Time Comparison analytic layer” on page 28
– “Using the Geo Profiler analytic layer” on page 30
– “Using the Prediction Zone analytic layer” on page 31
– “Using the Animated Density analytic layer” on page 33
The layer is calculated and displayed on the map, and the Calculate
link appears for that layer.
3. To change the resolution of the analytic layer, move the slider on the
corresponding Resolution slider bar. The higher the resolution, the
sharper the lines on the analytic layer. Higher resolution layers might
take longer to load. To recalculate the analytic layer with the new
resolution, click the Calculate link.
NOTE
The resolution can be changed before a layer is selected.
TIP
To view the analytic layer without any incidents, after the layer has been
calculated, click Deselect All in the Events and CAD/CFS menu groups. The
icons are removed, but the analytic layer is not recalculated. The analytic layer is
only recalculated when the Calculate link is clicked.
The colors of the layer indicate how dense the selected types are on a color
scale, with dark blue indicating the lowest concentrations and dark red
indicating the highest concentrations.
When the Time Comparison check box is selected, the Calculate Change
Density dialog box opens.
The colors of the analytic layer indicate the areas where searches for a suspect
are most likely to be effective, with dark red indicating search areas of high
probability, and dark green indicating search areas of low probability. The
number and size of the contours are not important. They provide a visual cue
to aid in sectioning off geographic areas to search.
When the Prediction Zone check box is selected, the Select Prediction in
Time dialog box opens.
Control bar
NOTE
Your SAA must submit your agency’s GIS files to BAIR for processing. If no
agency layers are available in the Agency Layers menu group, then contact your
SAA.
Analytics tabs
Use the menu groups in the Menu pane to determine what data is displayed
on the map, including incidents and analytic layers. For more information, see
“Using the Menu Pane” on page 19.
Sub-tabs
Record total
View buttons
Navigation buttons
The data grid lists all the incidents currently displayed on the map, and is
divided into sub-tabs that match the menu groups on the Menu pane, such as
Events.
NOTE
Each sub-tab in the Data Grid tab displays only those incidents that match the
menu groups on the Menu pane. Therefore, if no incidents are selected in a
menu group on the Menu pane, then the corresponding sub-tab on the Data Grid
tab will not display any information. For example, if only crime event type
incidents are selected, then information is displayed only in the Events sub-tab,
and the CFS/CAD sub-tab would be empty.
The data grid displays the first 20 incidents that match the current data
restrictions. To view more incidents, use the navigation buttons in the
lower-left corner of the grid. The total number of incidents that match the
current data restrictions is displayed in the lower-right corner of the data grid.
NOTE
Due to the limits of web applications, the maximum number of records that can be
displayed in Analytics at one time is 500. However, when a report is created, up
to 10,000 records can be included. For more information, see “Creating reports”
on page 67.
Each sub-tab contains columns that display specific details about the incident,
such as the time the incident was reported and the address where the incident
occurred. To manage the data displayed on the data grid, see the following:
“Reordering columns in the grid” on page 38
“Removing or adding columns to the grid” on page 39
“Sorting the information in a column” on page 39
“Filtering the information in a column” on page 40
To configure the data grid itself, see the following:
“Searching the data grid” on page 42
“Changing the view of the data grid” on page 43
NOTE
Any restrictions made in any part of Analytics affect all other parts of Analytics. If
data is restricted in the data grid, then the restricted data is not displayed on the
map. If the map is filtered with a drawing tool, then the data in the data grid is
filtered as well. For more information about drawing tools, see “Creating
polygons” on page 62.
The name of the column is displayed next to the mouse pointer, and
blue arrows appear to indicate where the new location of the column
would be.
Blue arrows
Click the column. The information is sorted in ascending order. To sort
the information in descending order, click the column again.
NOTE
Filters remain in place until they are cleared. If the map or the data grid is not
displaying the expected incidents, then make sure there are no filters restricting
the data being displayed. For more information, see “Clearing a filter” on page 40
and “Using the Clear Filters button” on page 74.
The filter is removed, and any data that was hidden by the filter is
displayed in the data grid.
3. To clear all filters for the data grid, click the Clear Filters button on
the toolbar. For more information, see “Using the Clear Filters
button” on page 74.
NOTE
When entering the alphabetic versions of the symbols, such as NOT, all
uppercase letters must be used. For example, if “Not knife” is entered, then the
software will look for records containing the phrase “Not knife,” instead of
excluding records that contain the word “knife.”
Boolean function/
Symbol Description
wildcard character
Boolean function/
Symbol Description
wildcard character
Single-character wildcard Underscore (_) Filters the column to include all results
that contain the matching text with a
character in place of the wildcard
character. For example, entering
Anders_n in the Last Name column
would restrict the data to only those
incidents with criteria, such as
Anderson or Andersen.
Multiple character wildcard Asterisk (*) Filters the column to include all results
that contain the matching text with
multiple characters in place of the
wildcard character. For example,
entering Ric* in the First Name
column would restrict the data to only
those incidents with criteria, such as
Rich, Rick, Richard, and Ricky.
Search field
Search button
Search options
Events
Primary. Displays only the highest-priority offense record linked to
the incident, based on the offense UCR grouping. For example, if an
ToolTip
Add/Remove
Analytics button
On the left side, additional graphics that can be added are listed,
based on the menu groups for crime types, such as Events and
CFS/CAD. On the right side, the graphics currently displayed in the
tab are listed.
2. To collapse or expand a menu group, click the Arrow icon.
3. To add a graphic to be displayed, from the desired menu group, click
the Add link for the desired graphic.
Make sure the graphic type matches the data displayed on the map.
For example, if only CFS/CAD incidents are displayed on the map,
then a graphic selected from the Events group would be empty.
4. To remove a currently displayed graphic, click the Remove link for
that graphic.
5. When finished, click Done.
The selected graphics are displayed in the Analytics tab.
Downloading graphics
If desired, an analytic graphic can be downloaded individually.
To download an analytic graphic:
1. In the upper-right corner of the desired graphic, click the Download
icon ( ).
The Analytic Download dialog box opens.
2. Select the image size for the download. In the Size area, the width
and height of the selected image size is displayed.
3. If the Custom option is selected, then enter the desired width and
height of the image in the Width and Height fields.
4. Click Get Analytic to download the analytic image.
When the Link Analysis tab is opened, the nodes are displayed using their
geographic placement, the same way as on the map.
Menus
Controls pane
The Controls pane can be used to control the layout of the nodes. It is
recommended to establish links between the nodes before changing the
layouts. For more information about creating links between nodes, see
“Managing links between nodes” on page 49. For more information about
changing layouts, see “Using the Controls pane” on page 53.
Use the View and Analysis menus to change the view of the nodes and to
perform analysis on the links. For more information, see “Using the View
menu” on page 56 and “Using the Analysis menu” on page 58.
To view details about a node, right-click the desired node, and then select
View.
The Attributes message box opens and displays information about the
incident, such as the class and address of the incident.
Plus sign
Selected node
2. In the Link Label field, enter a name for the link. The label is
displayed on the connection line.
3. In the Start Date and End Date fields, do the following:
– Click either the Start Date or End Date field.
– To specify a start date and time, select the Start Date Time check
box. Select a date from the drop-down calendar and enter a time in
the appropriate fields.
– To specify an end date and time, select the End Date Time check
box. Select a date from the drop-down calendar and enter a time in
the appropriate fields.
– Click Apply to close the date/time selection window.
4. In the Strength field, enter a numeric value of your choice to
indicate the strength of the connection between the nodes, such as a
percentile representing the confidence of the analyst in the
connection accuracy.
5. In the Distance field, enter a numeric value of your choice to
indicate the closeness of the connection between the nodes, such as a
time distance between the occurrence of the events.
NOTE
The values entered in the Strength and Distance fields can represent anything
desired, but the representation should be consistent throughout your session to
ensure accurate analysis. For example, if the Strength field represents how
much confidence there is in the connection accuracy for the first link created, then
all subsequent links should use the Strength field to represent the confidence in
the connection accuracy.
6. In the Color field, click the color box to open the color selector and
select a color for the connection line.
7. In the Direction field, select a direction for the connection line from
the following options:
– Normal: The connection line arrow points from the first node to
the second node.
– None: The connection line arrow is not displayed.
– Both: The connection line arrow points at both nodes.
– Swapped: The connection line arrow points from the second node
to the first node.
8. Click Apply.
The Attributes dialog box closes, and the link is displayed on the
Link Analysis tab between the nodes.
9. Repeat steps 1–8 to create additional links between nodes.
NOTE
Nodes can be connected to as many other nodes as needed.
TIP
Use the Select Rectangle tool in the View menu to create a link between multiple
nodes and one node, such as three calls that are connected with one event. For
more information, see “Using the Select Rectangle tool” on page 57.
Deleting a link If needed, a link between nodes can be deleted, such as if new information
reveals that the incidents are not connected, or if the connection was created
in error.
To delete a link:
1. Right-click the desired connection line between the nodes, and then
select Delete Link.
The Delete Edge dialog box opens, prompting confirmation of the
deletion.
2. Click Yes to delete the link. Otherwise, click No to keep the link.
NOTE
With the exception of the Geo X/Y Placement and Display X/Y Placement
layouts, if a node is not linked to any other node, then it is not displayed. For more
information about layouts, see “Using the Layout menu group” on page 53.
Using the Layout Use the Layout menu group to select the layout of the nodes.
menu group
Concentric Radial. Displays the network in expanding rings that
correspond to their distance from the root node.
Hyperbolic. Displays the network as a bubble. The top of the bubble is
the root node, and the child nodes gradually become smaller the farther
the distance between the child nodes and the root node.
ISOM. Displays the network as groups that move together. ISOM
stands for isometric.
NOTE
With the exception of the Geo X/Y Placement and Display X/Y Placement
layouts, if a node is not linked to any other node, then it is not displayed. For more
information about links, see “Managing links between nodes” on page 49.
Additional options Depending on the layout selected, additional options are displayed in the
in the Layout Layout menu group, including the following:
menu group
Link Length. Use the bar on the slider to indicate how long the
connection lines between the nodes should be. Use this option when the
Autofit option is not selected.
Disable Animations. Select this check box to not show any animations
when the layout is changed.
NOTE
The Hyperbolic and ISOM layouts are not affected by disabling animations
because animations are used as part of the calculations.
Autofit. Select this check box to have the nodes and connection lines
automatically sized to all fit on the screen.
Using the Link Use the Link Styles menu group to select the style of the connection lines.
Styles menu group
NOTE
Use the Attributes dialog box to create link labels. For more information, see
“Managing links between nodes” on page 49.
Using the View Use the View Controls menu group to configure the view of the node links.
Controls menu
group
Using the Timeline Use the Timeline feature to visually analyze the network of nodes based on
feature their assigned Start and End times.
To use the Timeline feature:
1. From the upper-left corner of the Link Analysis tab, select View >
Timeline.
The Timeline slider bar appears at the bottom of the Link Analysis
tab.
View menu
Play/Pause button
5. If desired, the layout of the nodes can be changed, which affects how
the nodes are animated with the Timeline feature. For more
information, see “Using the Layout menu group” on page 53.
NOTE
Regardless of the layout selected, the Timeline feature displays all nodes, even if
a node does not have any links.
If multiple incidents occurred on the same date, then, depending on the layout
selected, the nodes might be displayed in the same spot. If multiple nodes are in
the same spot, then the border around the visible node is thicker and darker. To
see the other nodes, move the visible node away from the spot.
6. To close the Timeline feature, click the Close button on the timeline
slider bar.
Using the Select Use the Select Rectangle tool to select multiple nodes, and then create a link
Rectangle tool to an additional node.
To use the Select Rectangle tool:
1. Enable the Select Rectangle tool by doing one of the following:
– Right-click in the area where the nodes are displayed, and select
Rectangle Select On/Off.
– Select View > Rectangle Select.
The Select Rectangle tool is enabled, and a check mark is displayed
next to the Rectangle Select menu item.
2. Draw a rectangle around the nodes to group them, such as three calls
that are related to a robbery.
The nodes are selected.
3. Drag the grouped nodes to the desired node, such as the robbery, and
then release the group.
The links are created between the nodes, and the Attributes dialog
box opens.
4. Complete the fields described in “Creating a link” on page 49.
5. To disable the Select Rectangle tool, do one of the following:
– Right-click in the area where the nodes are displayed, and select
Rectangle Select On/Off.
– Select View > Rectangle Select.
The Select Rectangle tool is disabled, and the check mark is removed
from the Rectangle Select menu item.
NOTE
The Analysis menu is available only when the Hierarchical, Circular Layout,
Concentric Radial, Hyperbolic, or ISOM layouts are selected.
Slider bar
Highlighted node
4. If desired, use the slider bar to change the percentage of the top
nodes to include. The higher the percentage, the more nodes are
included. For example, the top 3% of the nodes might be only two
nodes, but your agency may have the resources to focus on the top
five nodes. Therefore, the slider bar should be moved until five
nodes are displayed, so your agency can know the incidents upon
which to focus.
Agency hyperlink
NOTE
Your SAA can load your agency’s badge or image to display next to your
agency’s information. If the badge or image is missing, then contact your SAA.
Menu bar
Toolbar
NOTE
The Intel menu is for an add-on module that in not currently available with
Analytics.
Creating polygons
Use the Drawing Toolbar menu to create polygons or bounding boxes on the
map. Polygons can be any shape, while bounding boxes are rectangles.
Adding a polygon or bounding box to the map restricts the data displayed
throughout Analytics to the incidents inside the polygon.
NOTE
Any restrictions made in any part of Analytics affect all other parts of Analytics. If
the map is filtered with a drawing tool, then the data in the data grid is filtered as
well. If data is filtered in the data grid, then the filtered data is not displayed on the
map. For more information about the data grid, see “Using the Data Grid tab” on
page 37.
To remove a polygon or a bounding box from the map, select the Clear Polygon
menu item from the Drawing Toolbar menu.
The polygon is created, and all incidents outside the polygon are
removed.
Creating dashboards
Use the Dashboards menu and the Switch Dashboard button to manage your
dashboards. Dashboards are saved configurations of the data and tabs that can
be opened again to quickly display the type of data and analytics desired. For
example, a dashboard can be created for property crimes and a different
dashboard can be created for crimes against people.
Creating a dashboard
To create a dashboard:
1. Set up Analytics to display the information desired in the
configuration. Some information to include might be the following:
– The type of incidents
– The date range of the incidents
– The graphics for the incidents
– The link analysis of the incidents
For more information, see “Using the Menu Pane” on page 19 and
“Using the Analytics Tabs” on page 36.
2. Once Analytics is configured as desired, rest the mouse pointer on
the Dashboards menu, and then select Manage Dashboards.
The Dashboard Manager opens.
Selecting a dashboard
When at least one dashboard is saved, a dashboard can be selected to display.
To select a dashboard:
1. Do one of the following:
– From the toolbar, click Switch Dashboard.
– From the menu bar, rest the mouse pointer on the Dashboards
menu, and then select Switch Dashboards.
The Switch Dashboard dialog box opens.
NOTE
If desired, before selecting a dashboard, save the current configuration as a
dashboard so it can be returned to later. For more information, see “Creating a
dashboard” on page 64.
To close the Switch Dashboard dialog box without selecting a dashboard, click
Close.
Last Selected
Dashboard message
Creating reports
Use the Create a Report button to create reports. Reports are created from
the map, filters, and analytics currently displayed in Analytics. Reports can
either be created once, or set up to be sent as an email on a regular basis.
NOTE
It is recommended to first generate a one-time download to review how the data
is formatted in the report. Once the report is formatted as desired, then create the
report again as an email or scheduled report.
To create a report:
1. Set up Analytics to display the information desired in the report.
Some information to include might be the following:
– The type of incidents
– The date range of the incidents
– The graphics for the incidents
For more information, see “Using the Menu Pane” on page 19 and
“Using the Analytics Tabs” on page 36.
2. From the toolbar, click Create a Report.
The Reporting Wizard dialog box opens and displays the Welcome
and Basic Information areas.
NOTE
Due to the limits of web applications, the maximum number of records that can be
displayed in Analytics at one time is 500. However, when a report is created, up
10,000 records can be included, and up to 100,000 records can be queried for
inclusion.
6. Click Next.
– Rolling date range for report: Determine whether the report will
be run using a rolling date or specific dates.
Do one of the following:
– To have the report use a rolling date range (so that the dates
change with each report), make sure the Override the default
initial date range check box is cleared. By default, the check
box is cleared.
– To have the report use specific start and end dates for each
report, select the Override the default initial date range check
box, and then enter dates in the Start Date and End Date fields.
12. When finished, click Next.
The Reporting Wizard dialog box displays the Summary area.
The Summary area displays the name of the report and the action
associated with the creation of the report, such as downloading the
report.
The Report Contents area lists the additional files that were selected
for inclusion in the report.
If the report is being sent in an email, then the Report Recipients
area is displayed and lists the names of the people to which the report
is being sent.
14. If the report is a one-time download, then click the here link to
download the report.
15. Click OK to close the dialog box.
NOTE
Using the Download Data button provides unformatted data. To download a
graphic of the data, either create a report with the data, or download the graphic
from the Analytics tab. For more information, see “Creating reports” on page 67
and “Using the Analytics tab” on page 45.
NOTE
Due to the limits of web applications, the maximum number of records that can be
displayed in Analytics at one time is 500. However, when a file is created for
download, up to 10,000 records can be included, and up to 100,000 records can
be queried for inclusion.
4. Click Download.
The file is downloaded to your designated downloads folder.
When a filter is added through the Data Grid tab, the Clear Filters button
keeps track of the number of filters, and displays the total in red.
To clear all filters, click Clear Filters. All filters are cleared, and the button
displays a zero (0) in green.
To clear a specific filter, instead of all filters, select the Data Grid tab and
clear the filter in the specific column. For more information, see “Filtering the
information in a column” on page 40.
NOTE
The Clear Filters button does not remove any polygons placed on the map. Use
the Clear Polygon menu item to remove polygons. For more information, see
“Creating polygons” on page 62
Administrator Information
Jump to topic:
Introduction 78
Adding Email Addresses to Apnames Records 80
Using the SSOC Web Application 82
Configuring Interface Settings 86
Configuring Settings for Agencies on the Server 90
Setting Up Agency Configuration Screens 101
2 Administrator Information
Introduction
Introduction
When the CrimeMonitor or Analytics module is purchased, an Installation
technician sets up the interface. This chapter is provided as a reference in
cases where modification of the set up is necessary.
If your agency uses the CrimeMonitor module, then the following task must
be completed:
Deploy the Analytics web application, and then configure settings
accordingly.
Complete the following:
– “Configuring Interface Settings” on page 86
– “Configuring Settings for Agencies on the Server” on page 90
– “Setting Up Agency Configuration Screens” on page 101
If your agency uses the Analytics module, then the following tasks must be
completed:
Add user email addresses in the Names Code table (apnames) in the
software. See “Adding Email Addresses to Apnames Records” on
page 80.
Deploy the Single Sign On Connector (SSOC) web application, making
sure the necessary outbound ports are open, and then configure
application settings if necessary.
The SSOC is a separate web application in the Application Server that
allows users to open Analytics without a secondary login. See “Using
the SSOC Web Application” on page 82.
Deploy the Analytics web application, and then configure settings
accordingly.
Complete the following:
– “Configuring Interface Settings” on page 86
– “Configuring Settings for Agencies on the Server” on page 90
– “Setting Up Agency Configuration Screens” on page 101
NOTE
When setting up the agency configuration screens, the Agency Information
screen must be set up first and your agency’s information successfully submitted
to activate the interface and enable the other configuration screens. For more
information, see “Setting up the Agency Information screen” on page 102.
NOTE
If the email value does not display as an option, then the value must be
added to the Miscellaneous Info Type code table (tbmitype). For more
information, see “Adding the email code to the tbmitype code table” on
page 80.
SSOC icon
Analytics
icon
Application Server
Home link
Properties link
Navigation pane
NOTE
The functionality of the Log Level field in the Properties screen is different than
the Logging section in the Agency Administration screen. The Log Level field is
used to specify how much interface-specific data is stored on the server, while
the Logging section is used to manage the history of data that has been
uploaded to BAIR.
– Maximum Log Size (kB): Enter the maximum size a log file can
be before creating a new log. The default value is 10000000.
– Maximum Backups: Enter the maximum number of backup log
files to keep. The default value is 5.
– Rotate Logs: Select this check box to create a new log file when
reaching the maximum log size. By default, this check box is
selected.
6. In the Application Settings area, complete the following field:
– Export Directory: Enter the location path to the directory where
application settings will be saved. The following is the default
path:
C:/Tomcat/Properties/Analytics/incidents/
– Maximum Simultaneous Exports: Enter the amount of records
that can be updated at one time. The default number is 75.
7. Click Update.
Agency
section
Historical
Submission
section
Logging section
Gray ( ): The agency has a license, but is not set up with BAIR, and is
not exporting data.
Red ( ): The agency has a license, and is set up with BAIR, but is not
actively exporting data.
When each agency is expanded, a list of configuration screens for that agency
displays, including the following:
Agency Information
Configuration
Location
Modus Operandi
Incident
Offense
Calls For Service
Nature
Configuration Screens
Select the configuration screen link to open the screen. For more information,
see “Setting Up Agency Configuration Screens” on page 101.
NOTE
If the agency has been set up on the BAIR server, then the configuration screen
links are enabled based on the license type of the agency. If the agency has not
been set up on the BAIR server, then all links are disabled and the status
indicator displays the gray box. The Modus Operandi, Calls For Service, and
Nature configuration screens are not available to CrimeMonitor licenses, while all
configuration screens are available to Analytics licenses.
NOTE
To ensure the analytics work properly, it is recommended to upload historical
data before uploading current data so that there is a set of historical information
on which predications are based.
NOTE
If a Location Type has never been entered for an incident, then it will not be
included in the Historical Submission. Therefore, it is recommended that
agencies enter Location Type information on incidents when they begin to use
the interface to ensure it is included when historical data is submitted to BAIR for
analysis. For more information on Location Type, see “Setting up the Location
screen” on page 117.
NOTE
The Mail server must be set up for the notification feature to work properly. For
information, see “Configuring SMTP settings” on page 95.
NOTE
The specified recipient is notified for each data set completed. For example, if
historical submissions are configured for four agencies, then the recipient is
notified as each of the four uploads is completed.
NOTE
If the same data is uploaded to BAIR more than once, either by Historical
Submissions or regular exports, then the existing data is overwritten by the new
data.
/Spillman link
SMTP Setting
link
NOTE
The functionality of the Logging section in the Agency Administration screen is
different than the Log Level field in the Properties screen. The Log Level field is
used to specify how much interface-specific data is stored on the server, while
the Logging section is used to manage the history of data that has been
uploaded to BAIR.
Searching for In the Log Pane area, a log of all incidents and events sent to BAIR is
logging displayed, including the following information about each incident:
information
Date/Time
Agency
Record Type
Crime
Event Number
Action
A total of all logs listed displays at the bottom of the Log Pane area.
Use the scroll bar to view a specific log file, or enter search criteria in the
Agency, Event Number, and/or date range fields above the columns to
narrow the log list.
NOTE
Although the log displays all records sent to BAIR, this does not necessarily
mean that the items are added to or removed from the map immediately. Instead,
they are queued for the action.
Purging log In the Purging of Log Records area, the application can be set up to purge
information logs automatically after a certain time period or file size is reached. The logs
can also be purged manually.
To set up the application to purge records automatically:
1. Select the Purge Logs Automatically check box.
2. Select one of the following options:
– To purge by log size, select When logs reach this size, and then
specify the maximum size, in megabytes, that a file can be before
it is deleted.
– To purge by date, select When logs are older than, and then
select the maximum age a file can be before it is deleted.
3. Click Save to save the purge settings.
To purge all records manually:
1. Click Purge All Records.
A dialog box opens with the following warning: You are about
to delete all records from the log, do you wish to
continue?
2. Click Yes to delete the records. Otherwise, click No.
NOTE
Until the Agency Information screen is completed and successfully submitted to
BAIR, all other configuration screens remain disabled. For more information, see
“Setting up the Agency Information screen” on page 102.
NOTE
The apagncy table is used only to populate fields in the Agency
Information screen, and only when the interface is set up for the first time.
When information is added through the web application, but later removed
from the corresponding table, the data is automatically removed from the web
application. No alert is given when data is changed, nor does the web
application prompt to save. This is also the case if data is added back into a
table. The web application automatically updates with the changes, but gives
no notification and requires no save.
For example, if a Location Type is assigned in the web application (from the
lwtbcirc table), and then removed in the table, that setting is automatically
removed from the application without notice or a required save. This can
cause unexpected data to export or not export. However, this problem does
not occur often.
The exception to this rule is the apagncy table, which is used to populate
fields only for the Agency Information screen, and only when the interface is
set up for the first time. If records in the apagncy table are changed after the
interface is configured, then modified data from the table does not
automatically transfer from the software to the Agency Information screen.
Changes must be entered manually in the web application and resubmitted
through the interface to BAIR. When the apagncy table is modified, the web
application still does not give notice or prompt for a save.
NOTE
If changes are made to any table that populates fields in the web
application, then the web application must be reloaded to ensure that the
most current information can be reviewed.
NOTE
Some data provided in the Agency Information screen is viewable to the public
and other law enforcement, such as the URL link to an agency’s website (if
provided) and the badge image. Viewable data is located in the Metadata tabs of
the CrimeMonitor and Analytics applications. Keep this in mind when reviewing or
entering data into the Agency Information screen.
Certain fields on the screen are populated with information from the apagncy
table. If data is missing or incorrect, it can be added or updated on the screen
as necessary.
NOTE
If records in the apagncy table are changed after the interface is
configured, then modified data from the table does not transfer
automatically from the software to the Agency Information screen.
Changes must be entered manually in the web application and
resubmitted through the interface to BAIR. The web application does not
notify when changes are made or prompt for a save.
CAUTION
If an agency’s ORI is modified in the apagncy table, then any previous settings
configured in the interface for that agency are deleted. However, do not change
the agency ORI without first consulting Technical Services to understand the
impact to the Analytics or CrimeMonitor application.
CAUTION
Changing the selection in the Offense Mapping area does not change
data that was previously exported. To change previously exported data, a
new historical submission must be completed. For more information, see
“Using the Historical Submission section” on page 92.
In addition, changing the selection does not delete the mapping from the
Offense screen. However, mapping for the new selection will need to be
completed. If the selection is switched back to the previous selection, then
the old mapping is still available. However, some codes might need to be
remapped.
NOTE
For Kansas agencies, an additional Use trlaw codes check box is
displayed below the Statue Codes option. Select this check box to export
the statute codes from the trlaw table in the database. If this check box
is not selected, then the statute codes are exported from the tblaw table
as normal.
CAUTION
Values in the Geographic Boundaries area are used by BAIR to determine if an
address falls outside of your jurisdiction or cannot be geocoded. Such addresses
are then prevented from being placed on the map incorrectly. Although values
can be adjusted, unless the exact desired boundaries to use are known, leave the
default values in the Geographic Boundaries area. Otherwise, if incorrect data
is entered, then incidents can be quarantined because they were placed outside
of the boundary box.
7. In the Incident Offset area, in the X Min / Max and Y Min / Max
fields, enter the minimum and maximum x-coordinate and
y-coordinate values (distance in miles) to offset crime incidents from
their origination on the map. The default value for each field is half a
mile (.5).
Offset values are used to randomly vary the location of the incident
icon on the crime map. This provides a level of privacy for sensitive
crimes, such as sexual assault, by not placing the icon directly above
the incident.
8. For CrimeMonitor, in the Tip411 area, do the following to activate
the Tip411 feature of RAIDS Online:
– Select the Enable check box.
NOTE
To enable the Tip411 feature, your agency must have a Citizen Observer ID
number.
Submit an
anonymous tip
link
If the Enable check box is cleared, then a link does not appear on the
CrimeMonitor map application.
9. In the Image Upload area, select an image of your agency’s badge to
upload. This field is optional.
To upload an image:
– Click Select Image.
A browsing window opens.
– Locate and select the image file to use.
The most recent file name and path for the image displays below
the Image Upload area.
10. Click Submit.
NOTE
Before starting the interface for the first time, ensure that all Offense and
Nature codes are mapped and all set up tasks are completed.
Customize interface settings.
Copy the settings of another agency for quick interface setup.
Configure security settings.
Allow the Tip411 feature to be used for all exported incidents.
To have the software resume the export at the time and date
specified, click Yes. Otherwise, click No to have the export begin
with the current time and date.
3. In the Basic Configuration area, select one of the following options:
– Custom Setup: Allows for a customized setup of the agency’s
configuration settings. This method is recommended if the settings
for each agency on the server will be configured differently.
NOTE
When using the Custom Setup option, changing the settings in one
agency’s configuration does not affect the settings in another. However, if
an agency changes the setting from Custom Setup to Configure like,
then the following warning message is displayed: Changing from
Custom Setup to Configure like will replace all the
custom settings for this agency. Do you wish to
continue? Click Yes to replace the current settings with those like the
chosen agency.
NOTE
Depending on the export trigger and subsequent status codes specified in
the Incident screen, only certain data is copied. For more information, see
“Setting up the Incident screen” on page 128.
NOTE
Whenever settings in the Basic Configuration area are changed, a dialog box
opens with the following warning message: You are about to change your
settings. Are you sure you wish to continue. Click Yes to proceed.
NOTE
If one agency is set up to be configured like a second agency, then the second
agency cannot be set up to be configured like the first because the settings are
the same and the action would be redundant.
NOTE
If one agency is configured under Custom Setup and a second agency is
configured like the first under Configure like, then any setting changes made in
the first agency will be made in the second. This setup is typical when an
administrator wants a single configuration for every agency. If changes are later
made to the second agency, then its setup option changes from Configure like
to Custom Setup, and the following message is displayed: Changing these
settings will create a Custom configuration for this agency
and it will no longer be configured like Agency [xxx]. Do
you wish to continue? Click Yes to proceed.
NOTE
The defined export frequency does not control how often the database is queried
for incidents, but only how often data is exported to BAIR.
Static Data
section
Variable Data
section
Contact section
File section
The default Location Types match those used by the FBI for Uniform Crime
Reporting (UCR). Location Types are used by CrimeMonitor and Analytics
as one of the primary data elements displayed for an incident on the map, as
shown in the following example.
Location Type
Custom Location Types can also be created from the Location screen. This is
due to the variety of reporting within the database. The Configure like option
in the Configuration screen includes all Location settings for copying location
data.
NOTE
It is recommended that agencies enter Location Type information on incidents
when they begin to use the interface to ensure it is included when historical data
is submitted to BAIR for analysis. Otherwise, if the Location Type has never been
entered, then it will not be included in the Historical Submission.
Spillman
Circumstance
Code column
Location Type
column
Bar or Nightclub
Construction Site
Convenience Store
Fields or Woods
Grocery or Supermarket
Highway/Road/Alley/Street/Sidewalk
Hotel or Motel
Liquor Store
Residence or Home
Restaurant
Specialty Store
Other/Unknown
Amusement Park
Auto Dealership
Camp or Campground
Daycare Facility
Farm Facility
Industrial Site
Military Installation
Park or Playground
Rest Area
School–College or University
School–Elementary or Secondary
Shopping Mall
Tribal Lands
Community Center
NOTE
Multiple Circumstance codes can be added to any one incident.
Therefore, the following export rules apply:
3. For the Analytics module, extra Location Types can be added in the
Add additional Location Types area. This feature is unavailable for
CrimeMonitor modules.
– In the Location Type field, enter the name of the new Location
Type. See “Standard Location Types” on page 119.
– In the Spillman Circumstance Code field, click the drop-down
button and select a Circumstance code.
To delete an added Location Type, click the Delete button ( ) next
to the Spillman Circumstance Code field.
4. To print the configuration settings, click Print Configuration.
A dialog box opens with the following message: Would you like
to print just the settings on this page or all
agency settings?
5. Click either This page or All agency settings. To return to the
screen without printing, close the prompt box.
6. Click Save.
TIP
Modus Operandi are extremely valuable when trying to find patterns and trends
for certain types of crime. Therefore, it is highly recommended to enter Modus
Operandi whenever possible.
Spillman Analytics
Modus Operandi
column
– Point of Entry
– Method of Entry
– Suspect Action Against Person
– Suspect Action Against Property
– Weapon Type
– Method of Departure
– Number of Companions
– Persons MO (lower): Displays MO categories related to the
persons of the incident. Categories are agency and module type
specific, and may include the following:
– Hand Use
– Physical Condition
– Hat
– Mask
– Appearance
– Pants
– Shoes
– Jacket
2. For each MO category listed in each portion, in the Spillman MO
Factor field, click the corresponding drop-down button and select
the appropriate Spillman Modus Operandi Code factor.
For information on recommended Spillman MO factors and
methods, see “Recommended Spillman MO Factors and Methods”
on page 125.
3. To print the configuration settings, click Print Configuration.
A dialog box opens with the following message: Would you like
to print just the settings on this page or all
agency settings?
4. Click either This page or All agency settings. To return to the
screen without printing, close the prompt box.
5. Click Save.
Recommended Spillman MO
Spillman Analytics MO category
Factor or Method
Roommate/Neighbor
Resident
Friend/Former Friend
Commercial Structure
Residential Structure
Coin-Op Machine
Cash Register/Safe
Customer
Owner/Employee/Staff
Officer/LEO
Construction Site
Self (Suicide/Attempted)
Vehicle
Yard Ornaments/Statues/Decorations
Recommended Spillman MO
Spillman Analytics MO category
Factor or Method
Door–Side
Door–Back
Roof/Skylight
Ventilation System
Window–Main/Upper Levels
Window–Basement
Gate
Fence/Wall
Garage/Overhead Garage
Trunk
Remove (Lock/Window)
Cut/Chop/Saw/Drill
Bolt Cutters
No Sign Force
Pry Tool/Crowbar
Rock/Brick/Thrown Object
Unlocked
Drove Thru/Vehicle
Key/Key Available
Recommended Spillman MO
Spillman Analytics MO category
Factor or Method
Deceptive Practices
Bit/Slap/Hit/Strike/Gag Victim
Fondle/Rub/Grope/Masturbate
Stalking
Harassment/Made Threats
Oral/Vaginal Sex
Civil Matter
Counterfeit/Embezzlement
Gang Graffiti/Marks/Tagging
Theft by Deceit
Purse Snatch/Pickpocket
Ransacked/Searched
Shoplift
Yard Farming
Recommended Spillman MO
Spillman Analytics MO category
Factor or Method
Brick/Rock
Car
Chemical Agent
Club/Bat
Handgun
Hands/Feet
Knife
Screwdriver
Shotgun/Rifle
Simulated Weapon
Thrown Object
Tire Iron
Car
Motorcycle
Foot
Mass Transit
Unknown
From the list, select the applicable Status code(s) for the trigger type.
For CrimeMonitor modules, only one code may be selected.
NOTE
The selected trigger type determines which Status codes are copied when the
Configure like field is used on the Configuration screen. For the Disposition
and Clearance options, selected Status codes are automatically copied because
these values are from shared code tables and are the same for all agencies.
However, for the Workflow option, values are agency specific and are not
automatically copied. Therefore, values must be manually selected in the
wfstatcf table to display as a list in the interface Configuration screen. For
more information on workflow management, search for the article How to setup
workflow in the Knowledgebase online.
4. Click Save.
5. In the Incident Field Mapping area, the following two columns are
displayed:
– Spillman Analytics Fields: Lists the mapping field names of
Analytics.
– Spillman Schema: Lists the schema to be mapped to the
Analytics fields. Fields displayed in the Field Mapping area are
dependent on your module type.
Certain schema fields can be customized for your agency’s needs,
while others are hard coded and cannot be changed. Scroll through
the schema fields listed to see which can be modified.
To customize a schema field, click the drop-down button and
select a schema to map to the corresponding Analytics field.
NOTE
A dashed line around the first data elements listed on the screen indicates that
the information is viewable to the public. For CrimeMonitor modules, only this
data is exported. To make incidents visible to the public, see “Setting up the
Offense screen” on page 131.
The schema choices in the Crime field change based on whether Offense
Codes or Statute Codes was selected in the Offense Mapping area on the
Agency Information screen.
NOTE
The information and name of this column changes based on whether Offense
Codes or Statute Codes was selected in the Offense Mapping area on the
Agency Information screen.
NOTE
When the Do Not Export option is selected, the Viewable by column
becomes disabled and data is not exported for the specified data element.
– Clearance
– Disposition
3. Based on the trigger type selected, a list of Status codes is displayed
to the right of the trigger options. From the list, select the applicable
Status codes for the trigger type. Multiple Status codes may be
selected within the trigger type.
4. Click the Save button.
5. In the Calls For Service Field Mapping area, the following two
columns display:
– Spillman Analytics Fields: Lists the names of Analytics’
mapping fields.
– Spillman Schema: Lists the schema to be mapped to the
Analytics fields. Fields displayed in the Field Mapping area are
agency dependent.
Certain schema fields can be customized for your agency’s needs,
while others are hard coded and cannot be changed. Scroll through
the schema fields listed to see which can be modified.
To customize a schema field, click the drop-down button and
select a schema to map to the corresponding Analytics field.
For the Analytics module, up to 140 data elements can be exported
for each incident, including basic incident and offense
information, modus operandi, persons involved, vehicles
involved, and property.
6. To print the configuration settings, click Print Configuration.
A dialog box opens with the following message: Would you like
to print just the settings on this page or all
agency settings?
7. Click either This page or All agency settings. To return to the
screen without printing, close the prompt box.
8. Click Save.
NOTE
When the Do Not Export option is selected, the Viewable by column
becomes disabled and data is not exported for the specified data element.
When offenders find targets within their activity and awareness spaces, they
unknowingly reveal pieces of their mental maps. As an offender’s mental map
is revealed, the anchor points of the offender are also revealed. Although there
are exceptions, most offenders are less likely to commit crimes in unfamiliar
areas.
Therefore, the further away a location is from an offender’s anchor points, the
less likely it is that the offender will commit a crime in that location. This
pattern is called the distance decay model because the probability of
committing a crime decays, or decreases, with distance.
Researchers have developed several distance decay functions to
mathematically model the observed rate at which the probability decreases.
The observed decay rate is non-linear. For this and other reasons, traditional
density maps do not model the observed behavior of serial offenders.
However, geographic profiling creates a probability map of the offender’s
possible anchor points, which can make it easier to find and arrest the
offender.
NOTE
Geographic profiling works well on marauding serial offenders. Marauders
commit crimes outward from their anchor points as described. However,
other serial offenders are commuters. Commuters travel outside of their
normal activity spaces to commit crimes. Commuters might do this in an
attempt to leave no connection between their crime locations and their
residence.
Even distribution Geographic profiling must assume that the targets are spread out
of targets approximately evenly in an area. Therefore, geographic profiling works well
for cities and suburban areas where people and buildings are evenly located
across an area.
Geographic profiling does not work well for rural areas because people and
buildings are unevenly clumped together between empty spaces, such as
fields, mountains, or water.
Linked incidents Geographic profiling must assume that all the incidents in the set are linked to
the same offender. If incidents that are linked to different offenders are
incorrectly used together, then the cognitive maps of the offenders are
blended, which creates a mental map that does not match the real cognitive
map of any of the offenders. However, with enough correctly linked incidents
in a set, the occasional incorrectly linked incident will have little effect.
To determine if an incident that is possibly linked to the wrong offender will
distort the geographic profile, run the profile with different sets of incidents
based on the certainty that the incident is correct.
For example, if there are 10 incidents linked to an offender, but two of the
incidents could be incorrectly linked, then the profile should be run multiple
times in the following ways:
Once with all 10 incidents
Once with one of the questioned incidents removed
Once with the other questioned incident removed
Once with both of the questioned incidents removed
The maps should be compared to see if the geographic profiling changes
when the questioned incidents are removed.