|
|
| Sheriffs Share "Tips" and Information |
| By TechBeat |
| Published: 06/27/2005 |
|
This article was reprinted from the Winter 2005 edition of TechBeat, the award-winning quarterly newsmagazine of the National Law Enforcement and Corrections Technology Center system, a program of the National Institute of Justice under Cooperative Agreement #96-MU-MU-K011, awarded by the U.S. Department of Justice. On a September afternoon in 2004, two preadolescent girls in North Charleston, South Carolina, reported being followed by a man who had a tattoo on his neck. When a similar report surfaced in Charleston County, the tattoo was identified as that of a lizard. A database search for suspects associated with lizard tattoos in these two locations and surrounding jurisdictions yielded three matches, one of whom was a registered sex offender. The offender, however, provided an ironclad alibi. Police returned to question the girls, who recanted their accusations. In South Carolina's Low Country the sheriff's departments of Charleston, Berkeley, and Dorchester Counties and the police departments for the municipalities of Charleston, Mount Pleasant, and North Charleston have developed a secure regional information system called the Information Technology Improvement Project (ITIP) "Because of ITIP, our agencies are sharing information, working more cases together, and arresting offenders who are committing crimes in all our jurisdictions," says Chief Roddy Perry of the Mount Pleasant Police Department. ITIP enables line officers to access information about a suspect's involvement in other crimes, not only as a suspect but also as a witness or victim, according to Chris Helms, Technology Specialist Officer for the Mount Pleasant Police Department. "ITIP brings back all the cases where the suspect has been involved and provides not only suspect information, but situations where the person of interest might have been a witness or bystander or have been reporting a crime. Information on other contacts is particularly valuable for our narcotics officers." Karen Cordray, Sergeant in Charge of Crime Analysis for the North Charleston Police Department, which serves a population of 82,000 with 177 sworn officers, agrees that ITIP's access to information on known associates is a valuable investigative tool. "We're able to do a link analysis, find the associates' names, then run the associates down. You're looking for a frequent running mate or [someone] who the person may have had disagreements with in the past." In one investigation, Mount Pleasant officers used ITIP to round up individuals known as Batman, Poopsie, and The Joker who were involved in a car-to-car shootout. Batman was identified and his address determined through ITIP. Batman identified a female bystander, whose name was in ITIP, and who subsequently ITIP catches suspects who would not be detained without access to data in other jurisdictions. "Our dispatchers use it for the deputies on traffic stops and for other calls ... they end up arresting people who would slip through the cracks because no warrants are entered in NCIC [the National Crime Information Center]," says Linda Driggers, Dorchester County's Training and Certification Assistant. "When our detention center does a records check, they run the name through ITIP looking for active warrants, and we often end up holding prisoners for other agencies." Early in their collaboration, ITIP member agencies sought technical assistance from NIJ's NLECTC-Southeast, located in North Charleston, to help develop a regional information system. NLECTC-Southeast helped develop architectural concepts and operational requirements for the network. The Southeast Center works in "Integrating justice information is not simply a matter of choosing technology and integrating various computer software or records management systems," notes Coleman Knight, project manager at NLECTC-Southeast. "Agencies that want to integrate and share information need to consider policy decisions such as who is responsible for data, access, and security; legal and liability issues; how the resulting information-sharing system will be governed; and how it will be funded." Technological and operational issues also must be considered. Agencies must determine what information should be shared, develop operational standards and protocols, choose software and hardware, design security precautions, populate the database, perform acceptance testing, and train users. Security, Knight says, is critical in designing a shared information system. Law enforcement data is usually highly sensitive. Officers with different duties have access requirements at differing levels of confidentiality, and legal requirements for data at city, county, State, and Federal levels vary. According to Knight, the strength of ITIP has been the joint ownership of the executive committee. This ownership is critical, he says, because the executive committee needs the authority as a group to make decisions, manage the system for the benefit of all, and avoid power struggles and potential turf issues. Each agency in an information-sharing system should be an equal voting partner. For ITIP, this means that the chief executive officer of each member agency is on the executive committee. This committee oversees management of the ITIP system, adopts policies and procedures, and exercises final authority over all aspects of the system. The committee exercises its authority by majority vote, with each agency having one vote. A working group regularly reviews ITIP services, Knight says, to inform the executive committee about technical and operational issues and guide the system's day-to-day operation. "The working group has discussed everything from what we want it to do for us to how we want the screens that return information to look," says "Nearly all of the working group members have been on the street in uniform wishing we had access to this data," Helms says, "so we know what the line-level officer wants." According to Knight, the ITIP system connects each member agency's records management system (RMS) via redundant, high-speed, dedicated lines that end at SCRA, the site of a central data warehouse to which all agencies have access. Routers are installed at each agency and at SCRA to coordinate information transmission. Firewalls, user codes, and passwords ensure data and user security. "Of primary concern to the participating agencies was the avoidance of an additional burden on their legacy record management systems, most of which were stretched nearly to the breaking point under normal, everyday operation," Knight says. "So when you run a query, it goes to the central data warehouse instead of going to each agency's database. The ITIP system thus is set up to handle thousands of users simultaneously." ITIP agencies also wanted to segregate their legacy RMS from the shared system to allow each agency to determine which data elements to share. Finally, they wanted to create an environment that would be conducive to exploring Each jurisdiction still maintains and controls its own RMS, which cannot be modified through the ITIP network. A software system replicates data and allows information sharing across jurisdictions regardless of the structure of the underlying data sources. Searches can be done using either a preformatted name query application In automating information sharing, Knight says, "First, do no harm." An automated information-sharing system should lessen the workload and should not negatively affect an RMS or its data. Automating an already bad process will only result in an automated bad process. Protecting law enforcement agency data is critical When developing a request for proposal (RFP) to build an ITIP-like system, the more detail, the better, Knight says. If the RFP uses language that is too broad, it is subject to vendor interpretation, which may not be what the agency really wants. Be clear, he says, about what the information-sharing system should do. Provide As the system gets up and running, test and retest, Knight says. Quality assurance testing with actual system data will ensure that vendor hardware and software perform to specifications. Failing to conduct quality assurance testing could allow defective hardware or software to be installed, leaving little or no recourse. And finally, says Charleston's Pham, "Contract, contract, contract. Make sure you have a good contract with your vendor. If recurring costs to maintain the system are too high, your agency can't afford it." For more information about the Low Country Information Technology Improvement Project, contact Coleman Knight, 800-292-4385 or nlectc-se@nlectcse.org. Note: Analyses of test results do not represent product approval or endorsement by the National Institute of Justice, U.S. Department of Justice; the National Institute of Standards and Technology, U.S. Department of Commerce; or Aspen Systems Corporation. Points of view or opinions contained within this document are those of the authors and do not necessarily represent the official position or policies of the U.S. Department of Justice. |
|

Comments:
No comments have been posted for this article.
Login to let us know what you think