Spillman Dashboard Users guide

Transcription

1 Command Solutions; Spillman Dashboard Spillman Dashboard Users guide CAMS 2011

2 Contents Introduction... 3 Dashboard Concept... 3 Rapid Deployment... 3 Effective Tactics... 3 Accurate and Timely Intelligence... 3 Dashboard Login:... 4 Dashboard Incidents Page... 6 Department Information:... 6 Comparison Range:... 7 Search Button:... 7 Location:... 7 Sidebar Information... 9 Details Tab Setup Tab: Modify Categories: Offense Page Citations: Locations: Mapping Help Tab: Technical Information Determine the operating system bit count Tables Page 2

3 Introduction Dashboard Concept The Dashboard software is a result of a combined 6 decades of law enforcement management and executive experience. The Dashboard combines the principles of the "Dashboard Theory of Management" with the basic principles of Comp Stat management. These similar management theories both require the consistent or regular review of immediate and accurate data. The review of this data will then provide a public safety manager or executive with a comprehensive picture of the health of their agency and community. The dashboard was also created to increase the value of your agency's record management system. Technology, software and your record management system are all very valuable assets within your department. The dashboard was designed for managers who make strategic decisions and create plans for reducing crime and increasing the quality of life in your community. The statistical data displayed on the dashboard will prompt the managers and the executives of your agency to go back into your records management system and retrieve additional information for this decision making process. The basic purpose of the dashboard is to provide managers and executives with the software necessary to create an atmosphere of accountability and achievement. The opportunity of confusing activity with accomplishment can be diminished with regular use of the dashboard software. Rapid Deployment For decades, police departments have been driven by calls for service and responded with their limited resources in a reactive manner. With COMPSTAT, the police department is now armed with vital intelligence regarding emerging crime trends or patterns which allows for a strategic police response. The strategic response can be in many forms; traditional uniformed or plainclothes officer as well as nontraditional decoys and sting operations. Effective Tactics Traditional policing tactics have always dictated that most problems may be solved at a superficial level. In other words, take care of the suspect and don't worry about the social or environmental situation that may be adding to or creating the problem. COMPSTAT tactics encourage "thinking outside the box" and mandate that every resource, both internal and external, is considered in responding to a problem. COMPSTAT tactics also provide for a sense of urgency in responding to problems. The old attitudes of public entities responding at slow speed are no longer acceptable. Every case or call for service is handled as the traditional "Big Case" and is thoroughly and rapidly investigated in a systematic manner. Accurate and Timely Intelligence Accurate and timely intelligence or information is absolutely essential in effectively responding to any problem or crisis. Since today's policing techniques nearly always consist of vast amounts of information, it is necessary to provide a vehicle where essential information can easily and effectively be shared with all levels of the organization. Often times, detectives have information on suspects or crime trends and patterns but the actual field patrol officers who may be in contact with potential suspects have no idea of what information detective personnel possess or need to clear a case. Just as important, this principle also provides for an early warning system to identify emerging crime trends and patterns. In today's Page 3

4 environment of ever shrinking resources, being able to apply the necessary resources to an identified problem area is crucial in successfully reducing crime. Dashboard Login: Release 2.8 Dashboard Version 2.8 introduced the Dashboard Login Window which comes up when the Dashboard is started. Spillman Dashboard requires users to login to access the system. There are two levels of authentications, "User" and "Manager". A User has read access to all the pages in Spillman Dashboard and can change dates and locations, but not modify any settings. Managers can change category settings as well as modify users. There is also a One-Click Login which doesn t require any passwords, if this access is used anyone can access the system and change any of the settings, including the categories and locations. All users are managed through the User Setup tab located by going to setup>application settings>user setup tab. Page 4

5 Selecting the User Setup tab will allow the Dashboard Administrator to add users give them privileges to either change the settings or to just view the settings. The user setup window is also used to enable One-Click Login Users are added by selecting the Add User button above the user list. The add window appears with areas to fill in the name, password and user privileges. There are two access levels available, USER and MANAGER. Access as a USER will only allow the user to view the categories, locations and other settings, MANAGER will allow the user to set up new users, and change all settings. cams One-Click Login One-Click Login is created from the user listing page. Selecting One-Click Login towards the bottom of the page and the user will allow that user to login without putting using a login or password. You must be logged in as a manager to give One-Click Login privileges. The autologin user can also be given access to either as a user or manager. General Authentication Information: A person with USER access will be able to see all the settings in categories, locations, but they will not be able to save any changes to those categories. Any agency using a single server with more than one agency using the Dashboard will not have the one One-Click Login available. Page 5

6 Dashboard Incidents Page Figure 1 Dashboard Front Page Incidents. After the users login page the Dashboard Incident page (Figure 1) is built showing the graphs and crime data as a result of the tboffenses that were setup for each category under the setup tab. This information is either taken from the as observed field #42 of the Law Incident page or Sequence #1 of the lwoffense page. Sequence #1 should be highest priority offense by default of the fields #35 through #39 of the Law Incident page. Department Information: The department information on the Left side is setup under the setup tab setup>application settings> this is free text page to enter in the department name, population, and any other information the agency may desire. The population is used to figure the crime index rate for the time period of the search. See figure 2. The application settings page also shows the location to place the department logo; Note that the site logo is a 24 bit transparent.png files stored in /cams/resources/images/sitelogo.png and is 100 x 100. Page 6

7 Figure 2 Setup>application settings Figure 3 Main Dashboard Screen, both Incident and Offense page. Comparison Range: Number of days chosen to compare, the Dashboard compares two sets of days one against the other. The total days compared in this example are 60 the first 30 compared to the 30 before. Search Button: Selecting this button will start the search. Location: Selecting the location button creates quick set drop down page allowing the user to select a location created under the setup>application settings>locations tab. Page 7

8 The lower half of the Incident page and the offense page has three graphs showing the offense for that page in period differences, incidents or offenses per day and incidents or offenses per hour. Figure 5 Period Differences first page of Dashboard; Bottom half of Incident page and offense page. Figure 6 Incidents Per Day, first page of Dashboard; Bottom half of Incident page and Offense page. Figure 7 Incidents per Hour, first page of Dashboard; Bottom half of Incident page and Offense Page. Page 8

9 Sidebar Information The side bar shows what locations are being viewed which have been setup under setup>modify categories>locations as well which screen is being viewed, either Incidents or Offenses. The Sidebar also gives a quick look at the crime categories the user has setup such as Part I, Part II, Quality of Life, Accidents, Citations, or Group A and Group B Offenses on the offenses page. Clicking on any of the headings will change the main page to the details for that crime category. The total number of Incidents or Offenses is shown as well as a green arrow if the crime has decreased and a red arrow if the crime has increased. Figure 8 Side Bar, Main Page Page 9

10 10 Details Tab When Detail tab is selected it will take the user to the details page that will show a detailed list of the offenses that were setup under the setup tab. Details of a crime category can also be selected by double clicking on the one of the graphs. Figure 9 Details Page, Incidents The details page shows two comparisons of time Period 1 and Period 2, the graphs also shows the offenses that make up the graph and their percentages. Below the graphs is a list of all the offenses that make up the category, checking the check box on the right side will allow the user just use those offenses that they want to zero in on. Once the check box is checked or unchecked then click the Update View button on the right side. Below the offense list will be details of each of the incidents that make up the offenses shown. Figure 10 Details Page bottom half.

11 11 Note this will not show if Display raw data button is unchecked under the setup>application settings. Shown in figure 2. Each of the columns are sort able moving the mouse over the heading of the column will allow the user to sort the data. Also if using Internet Explorer, right clicking on the data will allow the user to export the data to excel. Setup Tab: The setup tab contains the following menus on the right side: Application Settings discussed above Figure 2 Modify Categories: Figure 5 The Incident Page of the Dashboard uses one crime per incident, whereas the Offense Page of the Dashboard counts all offenses associated with the incident. LAW (LWMAIN) COUNTING OFFENSES BY OFFCODE AND OFFEOBS: LWMAIN.LWOFFS OFFCODE FROM THE TBOFF TABLE 35,36, LWMAIN.OFFEOBS OFFCODE FROM THE TBOFF TABLE 42 Starting with version 2.5 offense codes can be used more than once in any category.. The Dashboard counts the number of incidents that have occurred in two ways, by the number of LWOFFS and the number of OFFEOBS. There are two Dashboard pages, the Incident page which uses the TBOFF codes from the tables on the law page numbers 42 one incident one crime. There is also the OFFENSE page that counts all offenses attached to the incident in fields 35,36,37,38. Offenses Codes are created in the TBOFF table. The dashboard reads the TBOFF table at the same time it pulls all the incident information. If a new TBOFF is created then it would be available to use in the setup menu the next day after the load warehouse has executed, or if the data was manually loaded it would be available. To create a TBOFF the user has to complete three fields, a four digit code, description of code, and UCR priority. The dashboard reads the description next associated with the TBOFF code so that it is easier to understand than a four digit code.. The Dashboard does not use lwmain Nature Codes for any statistics for the regular dashboard. There are several sites that provide the crime index for your area; the crime index is the number of crimes divided by the population. Each year the FBI publishes a list of the crime rate for cities and counties this can be found at : Additional information can be located at General information on crime statistics can be located at

12 12 Part 1 crimes are also referred to as the "index crimes" and are made of eight different categories of the most serious crimes. The Part I crimes are usually the ones that the news media uses when the crime index is being discussed as up or down. The eight categories are Homicide, Rape, Robbery, Aggravated Assault, Burglary, Larceny/Theft, Motor Vehicle Theft, and Arson. The Part I crimes are defined by the Uniform Crime Reporting (UCR) procedure developed by the FBI. In order to figure the correct Crime Index for a department only use the Incident page and be sure to add the population to the program through the Sidebar settings page. The incident page proscribes to the following rule: In the Summary reporting system, the Hierarchy Rule governs multiple offense reporting If more than one crime was committed by the same person or group of persons and the time and space intervals separating the crimes were insignificant, then the crime highest in the hierarchy is the only offense reported. Therefore the INCIDENT page counts one crime per incident. The first page of the Dashboard is titled Part I and Part II which follows the Uniform Crime Reporting (UCR) developed by the FBI. Definitions for Part I and II crimes can be found at:

13 13 The Dashboard can be setup with whatever categories that the department may want to track. It is suggested that the Part I crimes be setup with only those crimes identified by the FBI as Part I crimes. In that way the crime index calculation at the bottom of the Part I crime category will be more accurate. Part II crimes are not used to figure the crime index. Modify Categories: Figure 11 setup>modify categories Under the Setup>modify categories there will be four tabs to setup the offenses in Incidents and Offenses, as well as the setup for the Traffic and Locations category.

14 14 Setting Up Incidents: Each category must first be setup before it can be populated with offenses. To create a category first select the add category button at the top of the categories See Figure 5. The Create a Category window will popup. Figure 12 Category Setup Incidents The Category Name is free text and can be named anything you wish, the category must be assigned to a group, either Part I, PartII, Quality of Life, or Accident information. Once the category is setup then and you save it, you will be returned back to the Enabled Incident Categories screen Figure 5. Once the category has be cr4ated it can now be populated. The Incident Categories are populated by moving the tboffense description from the left column to the right column and saving it. Placing the curser in the available offense list and begin typing the category you are looking for will take you to that area. Example if you are setting up the category Burglary, then entering B will take you to all the offenses that have a B in the first letter. The available offense come from the tboff table, instead of using the actual tboff code the description is used, for example if TAPD is used for Traffic Accident Property Damage then you will see Traffic Accident Property Damage on the right side as an available offense code. Once a code is found or a group of codes are found they can be moved to the right column by clicking on each code or by CTRL clicking on each code, or by CTRL clicking and Shift Clicking on the last code you want to use. Once the codes are moved over to the right save your changes, that category is not populated and will show data if any of those offense have been used in the time frame that was searched on.

15 15 Figure 13 As many Categories of crimes can be setup as the department may desire, Part I crimes should remain the same however the user may setup and number of Part II crime, Quality of Life categories, and Accident categories. In order to use offense codes for Accident information a department must first create tboff codes for whatever category they may want to track, then under application settings( Figure 2) they must check the box use lwmain for accident data the dashboard will now use the lwmain offense codes to track the accident information. Offense Page The next tab under setup>modify categories is the offense tab. The offense page is setup the same as the Incident page with first creating a category and then populating that category. The offense page counts all offense associated with the incident, there can several offenses associated with one offense The second page of the Dashboard is titled Group A and Group B offenses, and follows the NIBRS rules. In NIBRS, if more than one crime was committed by the same person or group of persons and the time and space intervals were insignificant, all of the crimes are reported as offenses within the same incident. Therefore the OFFENSE page counts all offense associated with each law incident. The offense page can also be setup by using any of the categories listed below. The following offense categories, known as Group A offenses, are those for which Extensive crime data can be collected by the Dashboard..

16 1. Arson 2. Assault Offenses - Aggravated Assault, Simple Assault, Intimidation 3. Bribery 4. Burglary/Breaking and Entering 5. Counterfeiting/Forgery 6. Destruction/Damage/Vandalism of Property 7. Drug/Narcotic Offenses - Drug/Narcotic Violations, Drug Equipment Violations 8. Embezzlement 9. Extortion/Blackmail 10.Fraud Offenses - False Pretenses/Swindle/Confidence Game, Credit Card/Automatic Teller Machine Fraud, Impersonation, Welfare Fraud, Wire Fraud 11. Gambling Offenses - Betting/Wagering, Operating/Promoting/Assisting Gambling, Gambling Equipment Violations, Sports Tampering 12. Homicide Offenses - Murder and Nonnegligent Manslaughter, Negligent Manslaughter, Justifiable Homicide 13. Kidnapping/Abduction 14. Larceny/Theft Offenses - Pocket-picking, Purse-snatching, Shoplifting, Theft from Building, Theft from Coin-Operated Machine or Device, Theft from Motor Vehicle, Theft of Motor Vehicle Parts or Accessories, All Other Larceny 15. Motor Vehicle Theft 16. Pornography/Obscene Material Page 16

17 17 Citations: The next tab on the setup>modify applications tab is the traffic button, this button is used to setup up information on Citations issued. In order to use this information the department must be using the Spillman Citation Module. To setup the Citation page click on the citation tab, all the types of citations that a department uses are listed. Clicking the check box next to the citation type an agency wants to use and given it a description will allow it to be counted by the dashboard and show up under the citation information. Locations: The location setup tab is located under the setup>modify categories and is a tab at the top of the page. Locations are used create an individual dashboard for a defined location. The location is entered in tbzones and must be used at least once in order to be used by the dashboard. The dashboard searches on the area or location field of the lwmain table to determine which locations have been used. Like all setups for the dashboard you must first create the location and populate it.

18 18 Figure 14 Location setup An agency can create as many locations as they wish the locations can be temporary and deleted at a later date. To access the locations, and use different locations from the incidents page look for the next to the comparisons range (days) on the incident page, offense page or details page. Once the slide out button is selected the locations added will drop down for selection. Mapping The next setup tab under setup>mapping settings is used to set parameters on how many incidents are mapped and if the user wishes to use heat mapping, place marker or both. Figure 15 Setup Application settings

19 The Dashboard uses Google Earth to map the locations of all incidents listed on the details page, by first creating a KML file and then sending it to Google. Every computer that wants to have mapping must have installed Google Earth. Figure 10 has the heat map and place markers turned on. Figure 16 Page 19

20 20 Help Tab: The help tab shows a number of help topics pertaining to the dashboard. However, the >help>application testing can be an important tool to trouble shoot any problems or issues with the dashboard. The testing page show the last load, number of rows loaded, ODBC connection status and a number of other settings that can help trouble shoot any problems you might be having. Figure 17 Application Testing screen.

21 21 Technical Information The ODBC Driver that should work for the set up you have; Windows to Windows bit drivers can be downloaded and installed from the link below. If you are setting up a Windows 64 bit machine you will need to download the following drivers, you can not use the 64 bit drivers on Spillman versions 4.x The driver installs very quickly and once you have installed it then you have to configure the ODBC in the setup window located at start>settings>control panel>administrative tools>data sources(odbc) this will open up the "ODBC data source Administrator" window. Click on the "System DNS" tab and then the add button on the right,look for the c-tree ACE drive click on it and then the configure button. Fill out the fields like as below: Just a note the password may be upper or lower case. Data Source Name: c-treeace ODBC Driver (this name must be the same in the testconnection file) Description: c-treeace ODBC Driver (What every you would like) Host: IP address (of the Spillman machine)

22 22 Database: live (This is the default data base some places change the name) User ID: odbcuser (Default is odbcuser Sometimes Upper case) Password odbcuser (Default is "odbcuser" (lower sometimes upper) Service 6597 (Has always been 6597) Preserve Cursor OFF Options: (blank) Once you have completed the ODBC setup download the testconnection located at It's probably best to open the testconnection file in notepad and make sure that the name of the connection in the fifth line down is the same as the name in the c-tree setup window under Data Source Name (look at figure 1 above) Now just double click the testconnection and hopefully you will get "done" if not make a note of the error and let me know. If you wish you can give me a call when you are getting ready to install the driver and I can walk through it with you. The whole process takes less than five minutes. Possible errors: Changing the Description name does nothing no error is produced. Host: Wrong host name will create the error Erron in network daemon

23 23 Database: Wrong database name will create the error CTDB-database does not exist or not found User ID: Wrong User I.D. Will create the error CT-Invalid user id Password: Wrong password will create the error =17451 CT- Invalid password Service: Blank Preserve Cursor: Leave it blank. Options: Blank Determine the operating system bit count Locate the operating system that is running on your computer in this section, and then follow the steps to determine the bit count of your operating system. Windows Vista If you have Windows Vista, there are two methods to determine whether you are running a 32-bit or a 64- bit version. If one does not work, try the other. Method 1: View System window in Control Panel 1. Click Start, type system in the Start Search box, and then click system in the Programs list. 2. The operating system is displayed as follows: o For a 64-bit version operating system: 64-bit Operating System appears for the System type under System. o For a 32-bit version operating system: 32-bit Operating System appears for the System type under System. Method 2: View System Information window 1. Click Start, type system in the Start Search box, and then click System Information in the Programs list. 2. When System Summary is selected in the navigation pane, the operating system is displayed as follows: o For a 64-bit version operating system: x64-based PC appears for the System type under Item. o For a 32-bit version operating system: x86-based PC appears for the System type under Item. If you cannot determine the operating system bit count with these methods, go to the "Next Steps" section.

24 24 Windows XP If you have Windows XP, there are two methods to determine whether you are running a 32-bit or a 64-bit version. If one does not work, try the other. Method 1: View System Properties in Control Panel 1. Click Start, and then click Run. 2. Type sysdm.cpl, and then click OK. 3. Click the General tab. The operating system is displayed as follows: o For a 64-bit version operating system: Windows XP Professional x64 Edition Version < Year> appears under System. o For a 32-bit version operating system: Windows XP Professional Version <Year> appears under System. Note <Year> is a placeholder for a year. Method 2: View System Information window 1. Click Start, and then click Run. 2. Type winmsd.exe, and then click OK. o When System Summary is selected in the navigation pane, locate Processor under Item in the details pane. Note the value. o If the value that corresponds to Processor starts with x86, the computer is running a 32- bit version of Windows. o If the value that corresponds to Processor starts with ia64 or AMD64, the computer is running a 64-bit version of Windows. If you cannot determine the operating system bit count with these methods, go to the "Next Steps" section. Windows Server 2003 If you have Windows Server 2003, there are two methods to determine whether you are running a 32-bit or a 64-bit version. If one does not work, try the other. Method 1: View System Properties in Control Panel 1. Click Start, and then click Run. 2. Type sysdm.cpl, and then click OK. 3. Click the General tab. The operating system is displayed as follows: o For a 64-bit version operating system: Windows Server 2003 Enterprise x64 Edition appears under System. o For a 32-bit version operating system: Windows Server 2003 Enterprise Edition appears under System. Method 2: View System Information window 1. Click Start, and then click Run 2. Type winmsd.exe, and then click OK. 3. When System Summary is selected in the navigation pane, locate Processor under Item in the details pane. Note the value. o If the value that corresponds to Processor starts with x86, the computer is running a 32- bit version of Windows. o If the value that corresponds to Processor starts with EM64T or ia64, the computer is running a 64-bit version of Windows. If you cannot determine the operating system bit count by using these methods, go to the "Next Steps" section. Notes To find the computer s bit count, see the documentation that was included with the computer, or contact the hardware manufacturer.

25 Intel Itanium-based computers can run only 64-bit versions of Windows. Intel Itanium-based computers cannot run 32-bit versions of Windows. Currently, 64-bit versions of Windows run only on Itanium-based computers and on AMD64 Page 25

26 26 ables modwhen geoid acmain.modwhen acmain.geoid CTBSEV able ccident ACMAIN TMAIN GBADDR LWMAIN Used/Not Severity descriptions Screen for acmain Fields abbr Used Number Known Name Field actbsev.abbr Name desc actbsev.desc number 1 Accident Number acmain.number adate 2 Date acmain.adate street number 41 Address Citation Number acmain.street ctmain.number city dtissue 26 7 City Date of Citation acmain.city ctmain.dtissue zip vildate 25 9 Zip Violation Date acmain.zip ctmain.vildate locat issuoff Location Issuing Officer Code acmain.locat ctmain.issuoff sev locatn Severity Area Location Code acmain.sev ctamin.locatn officer street Officer Street Address Assigned acmain.officer ctmain.street agency city Agency City acmain.agency ctmain.city relinc citype not used 2 Citation Type ctmain.citype nearl agency not used 28 Agency Code ctmain.agency localt addwhen not used When Added ctmain.addwhen killed modwhen not used 46 People When Last Killed Modified acmain.killed ctmain.modwhen totdam geoid not used 28 Total Geobase Damage Address ID acmain.totdam ctmain.geoid injured 47 People Injured acmain.injured wcond not used roads number not used 1 Address ID: gbaddr.number roadc street not used 7 Street address gbaddr.stname lcond citycd not used 15 City Code apcity.abbr traffc stnumb not used 8 Street Number gbaddr.street collt x not used 19 Coordinates: X gbaddr.x speed y not used 21 Coordinates: Y gbaddr.y advsp xshift not used x>>n wcond2 not used firshar city not used 12 City lwmain.city firsloc ocurdt1 not used Occurred After lwmain.ocurdt1 sourcin ocurdt2 not used Occurred Before lwmain.ocurdt2 reljct dtrepor not used 63 When Reported lwmain.dtrepor inttype dispdat not used 72 Date Disposition Declared lwmain.dispdat busrela modwhen not used When Last Modified lwmain.modwhen wrkzon modby not used Who Last Modified lwmain.modby wrkloc number not used 1 Incident Number lwmain.number wrktype nature not used 2 Incident Nature lwmain.nature wrkpres address not used 9 Incident Address lwmain.address addwhen zip 14 Zip Code acmain.addwhen lwmain.zip

27 27 contact Contact or Caller lwmain.contact nameid not used Complaint Name Number lwmain.nameid locatn 15 Area Location Code lwmain.locatn rcvby not used Received By lwmain.rcvby howrc not used How Received lwmain.howrc agency 59 Agency Code lwmain.agency respoff 58 Responsible Officer lwmain.respoff offeobs 42 Offense as Observed lwmain.offeobs offcode 35,36,37,38,39 Offense codes lwmain.offcode dispos not used Disposition lwmain.dispos misc not used WOFFS number seq 1 Seq (Sequence Number) lwoffs.seq desc 3 Offense Codes (Offense Description) tboff.desc modwhen none modby not used offcode 2 Code lwoffs.offcode amount not used BOFF abbr 1 Offense Code (Code for Offense) desc 2 Offense Description tboff.desc priority not used UCR Action Code tboff.action riskval not used action not used