COPLINK 1.0, 2.0, and 2.5 Reviews

1
COPLINK 1.0, 2.0, and 2.5 Reviews
Presenters W. Wyzga, V.P Eng., KCC Robert Fund
, Project Manager, KCC

• Thursday, January 17th, 2002

2
Agenda

• COPLINK 1.0
• Functionality Overview
• Architecture Overview
• COPLINK 2.0
• Functionality Overview
• Architecture Overview
• COPLINK 2.5 (In development)
• Functionality Overview
• Architecture Overview

3
COPLINK 1.0 Functionality

• Ability to search for Person, Location, Vehicle,
  and Incident/Warrant
  
• Ability to sort the results by columns
• Detail Screens provided for Person and
  Incident/Warrant
  
• Detect Relationships created for Person,
  Location, Vehicle, and Incident
  
• Simple Detect Search capability

4
COPLINK 1.0 Person Search
5
COPLINK 1.0 Location Search
6
COPLINK 1.0 Architecture

• Front End developed as JAVA based application
• Difficult to add new functionality providing
  more query fields or more columns to display
  results
  
• Hard to distribute client upgrades to officers
• Tied directly to ORACLE Application Server (OAS)
• Highly database dependent through use of stored
  procedures, OAS, proprietary cartridge, and ProC

7
COPLINK 1.0 Architecture

• Big Detect DB 10GB in size
• Staging Tables increase Connect DB size
• Use of Triggers to populate COPLINK tables
• Stored Procedures and Views to retrieve data

8
COPLINK 1.0 Deficiencies

• Inability to conduct a search for a Person using
  generic descriptors (height, weight, age, etc.)
  
• Vehicle make, model, and style in a cryptic code
• Crime types identified by UCR codes difficult
  to remember and no tip help available
  
• No provision to share information between
  different agencies

9
COPLINK 1.0 Deficiencies

• Hard-coded searches
• Modifications to searches done through code
  changes
  
• No exact match and sound-alike searches on
  names
  
• No ability to search locations by crime types
• Graphical User Interface difficult to change

10
COPLINK 2.0 Added Functionality

• Possible to search on a generic person by
  height, weight, age, etc
  
• Vehicle make, model, and style described in plain
  text, no cross referencing required
  
• Crime types are listed by their descriptions, not
  codes
  
• Ability to filter searches by incident date
• Detail Screens added for all objects
• Improved navigation within the application
• Has the ability to connect different agencies
  (COPLINK nodes)

11
COPLINK 2.0 Added Functionality

• Three different types of searches are available
  and controlled by an individual user
  
• Auto Wildcard
• Exact Match
• Sound-Alike (soundex)
• Locations can be searched using crime types as a
  filter
  
• Interface is simple to change and can be
  controlled for an individual user or group of
  users

12
COPLINK 2.0 Added Functionality

• Improved Detect capabilities
• More relationships added home locations
• Ability to show all related objects or limit the
  results
  
• Filtering of results added through Advanced
  Search capability
  
• Detect Database size decreased 10 fold
• Increased speed of Detect searches 5 times
  faster on average

13
COPLINK 2.0 Screen
14
COPLINK 2.0 Architecture

• Browser based Graphical User Interface
• Old Java application based Client thrown away and
  replaced by browser based client
  
• Utilizes Java Applet and relies heavily on
  JavaScript and Dynamic HTML (DHTML)
  
• Screen definition stored in the new
  Administration database
  
• Added ability for quick modifications to existing
  system
  
• Users can define default values for each screen
  and store their preferences and get the same
  presentation from any machine in the department

15
COPLINK 2.0 Architecture

• New Java Servlet based operating system
  independent middle-ware
  
• Utilizes JDBC database connectivity with the
  database (ORACLE, SQL Server, DB2)
  
• User validation
• Session tracking
• Communication with different agencies through a
  socket connection
  
• No Search Stored Procedures in the Database
• Searches utilize database Views

16
COPLINK 2.0 Architecture

• New smaller Detect DB
• JDBC and Java provide Interoperability
• Architecture is not specific to law enforcement
• Accessible from the browser
• Familiar HTML based user interface

17
COPLINK 2.0 Deficiencies

• No ability to search for a Person using
  distinguishing marks (scars, tattoos, etc.)
  
• Filtering of Person and Vehicle searches by crime
  type is not possible
  
• Dependent on 1.0 Database design
• Client is very slow due to the use of JavaScript
• No history tracking in Detect module
• Detect database not incrementally built
• 1.0 data load migration still in use, dependent
  on ORACLE

18
COPLINK 2.5 Added Functionality(under
development)

• Ability to search for a Person using
  distinguishing marks
  
• Added ability to filter any search by crime type
• New search screens and details added for
  Organization, Property, and Weapon
  
• Added history tracking in Detect module
• Added ability for users to control their
  preferences

19
COPLINK 2.5 Added Functionality(under
development)

• Client software redesigned to be less dependent
  on JavaScript provides for faster display
  
• Middle-ware redesigned to run distributed
  (inter-agency) searches concurrently utilizing
  XML
  
• Database redesigned to support richer queries
• Detect Database incorporated into Connect
  Database incrementally built

20
COPLINK 2.5 Architecture(under development)

• Front End changed to generate DHTML from an
  Applet instead of JavaScript
  
• Java based data migration module, provides for
  better system independent migration
  
• XML used to program migration module
• Capability to receive XML data on the socket and
  populate COPLINK database
  
• Staging table in the database no longer
  necessary
  
• One Database, smaller size

21
COPLINK 2.5 Architecture(under development)

• No Detect DB
• JDBC and Java migration for legacy systems
• Ability to receive XML
• Thinner JavaScript
• Migration Server programmable through XML file
• Runs on ORACLE, SQL Server, DB2

22
COPLINK User Support

• Knowledge Computing Corporation (KCC) provides an
  on-line help feature for end users
  
• KCC has developed a self-paced learning program
  for COPLINK that allows a new user to learn the
  systems capabilities in less than one hour
  
• Customer support is available from KCC during
  regular business hours

23
COPLINK Administration

• KCC has developed a separate Administration
  program that is distributed starting with COPLINK
  2.0
  
• Most routine maintenance can be addressed by a
  system administrator without requiring any
  vendor/developer intervention
  
• Administration enhances COPLINK system security
  and permits different levels of user access

24
COPLINK Demo
25
Questions?