02.03.2013 Budget, congress, criminal justice, Data, data sharing, Information sharing, justice, law enforcement, Law enforcement information sharing, leadership, LEIS, N-DEx, NIEM Comments Off on Letter to Congressman Reichert: If you want LE information sharing, please aim your pen at a different target

Letter to Congressman Reichert: If you want LE information sharing, please aim your pen at a different target

If you want law enforcement agencies to share information, go to the source and help the Chiefs and Sheriffs to push their data in the FBI’s National Data Exchange N-DEx. Trying to impose information sharing with unfunded standards mandates will not work.

As someone who has been in the standards business since 1995, history has proven to me that:

  • The business need must drive standards, standards can NEVER drive the business; and
  • Trying to SELL the business on standards is a losing strategy.

Hi Congressman Reichert,

You won’t remember me, but a long time ago we were in meetings together in Seattle with the likes of John McKay, Dave Brandt, Scott Jacobs, Dale Watson, and others working on building the Law Enforcement Information Exchange (LInX); I was the technical guy on the project, working with Chief Pat Lee and our very dear lost friend Julie Fisher (may she rest-in-peace, I sure miss her).

A hell of a lot of water has gone under the bridge since then–it’s been nearly TWELVE YEARS. If we look back over this time, we have had so many bills, laws, strategies, policies, papers, speeches, conferences, proclamations, and other assorted attempts to prod law enforcement data loose from the nearly 18,000 agencies across our country. While we are far better off than we were back then, I think we can agree that we still have a long way to go.

Where we differ, I’m afraid, is in the approach to get there – a few days ago, you proposed legislation, the Department of Justice Global Advisory Committee Authorization Act of 2013, as a means to improve information sharing among law enforcement agencies – do we really believe another “stick” will work to get agencies to share information? Do we really believe it’s a technology or data standards problem that’s preventing law enforcement data from being shared? As a technologist for 34 years, and someone who has been involved in law enforcement information sharing since the Gateway Project in St. Louis, MO in 1999, I can tell you it is neither.

While I applaud the work of the GAC, and I have many colleagues who participate in its work, I’m afraid having more meetings about information sharing, developing more standards, approving more legislation, and printing more paper will NOT help to reach the level of information sharing we all want.

Instead, I want to propose to you a solution aimed at capturing the commitment of the men and women who can actually make law enforcement information sharing happen, and virtually overnight (metaphorically speaking) – namely, the great men and women who lead our police and sheriffs departments across America.

Now to be fair, many of these agencies are already contributing their records to a system I am sure you are familiar with called the National Data Exchange (N-DEx). Built by the FBI CJIS Division, this system has matured into a pretty respectable platform for not only sharing law enforcement information, but also for helping cops and analysts to do their respective investigative and analytic work.

Now, in case you are wondering, I do not own stock in any of the companies that built N-DEx, nor has the FBI signed me up as a paid informant to market N-DEx. I write to you on my own volition as a result of my nearly six years of volunteer work as a member of the International Association of Chiefs of Police (IACP) Criminal Justice Information Systems (CJIS) Committee.

About two years ago I volunteered to lead a small sub-group of the committee who have either built, led, or managed municipal, state, federal, or regional information sharing systems. Our charge was (and still is) to help CJIS take a look under the hood of N-DEx to see what’s in there (data wise) and to help figure out what needs to be done to make it a more effective tool to help cops across America catch more criminals, and maybe, just maybe, even prevent criminals from acting in the first place.

While our work is far from done, I can tell you that one thing we need is more data – as you well know, be it N-DEx, LInX, RAIN, or any other information sharing system, it is only as good as the data that’s put into it.

Believe it or not we already have the data standards in-place to get the data into N-DEx. CJIS has developed two Information Exchange Packet Descriptions (IEPDs) that tells agencies exactly what to do and how to format and package up their data so it can get to N-DEx. Additionally, CJIS has an extensive team ready to assist and my colleagues over at the IJIS Institute hold training sessions sponsored by BJA, to help agencies along the process (NIEM training).

These two IEPDs can help law enforcement agencies today to share the following law enforcement records:

  • Service Call
  • Incident
  • Arrest
  • Missing Person
  • Warrant Investigation
  • Booking
  • Holding
  • Incarceration
  • Pre-Trial Investigation
  • Pre-Sent Investigation
  • Supervised Release

So what’s the hold up? Speaking only for myself, and I will be very straight with you, I believe the root cause for not getting more law enforcement data into N-DEx is the current piecemeal, politically charged, hit and miss grant funding process that the Act you propose, if passed, will burden even further – see page 3, lines 17-25 and page 4, lines 1-6.

Instead, I ask that you please answer the following question…

If law enforcement information sharing is important enough to push though a Public Act, where is the nationwide project, with funding, to get all shareable law enforcement data loaded into the one system that would give ALL law enforcement officers and analysts access to collective knowledge of the nearly 18,000 law enforcement agencies?

The immediate answer might be “we already have one; N-DEx;” however, N-DEx is only a piece of the answer…it’s as they say, “one hand clapping.” And in all fairness to my friends and colleagues at the FBI CJIS Division, that program was only charged and funded to build the  N-DEx bucket, they were never funded to actually go get the data to fill the bucket.

The strategy, for whatever reason back then, was relegated to a “build it and they will come” approach, that IMHO has not worked very well so far and may take another 5-10 years to work. I should also note that the bucket isn’t totally empty…there are quite a number of agencies and regional projects, like LInX, that have stepped up and are helping to fill the bucket – however, if we want to expedite filling up the bucket, focusing on mandating more standards is not the answer

What I submit  is the “other hand clapping” is the need for a shift focus, away from policy, standards, and technology, and establish a funded nationwide project that will offer a menu of choices and support packages to the Chiefs and Sheriffs that will enable them to start sending as many of their shareable records as possible to N-DEx.

Some of the options/support packages could include:

  1. Provide direct funding to agencies and regional information sharing systems to develop N-DEx conformant data feeds to N-DEx;
  2. Grant direct funding to RMS and CAD system providers to develop N-DEx conformant data feeds from their software, with the stipulation they must offer the capability at no additional cost to agencies that use their products;
  3. Establish a law enforcement data mapping assistance center, either bolted on to IJIS NIEM Help Desk, as an extension of NLETS menu of services, or through funding support at an existing information sharing project like the Law Enforcement Technology, Training, & Research Center who works in partnership with the University of Central Florida.

At the end of the day, we all know that the safety and effectiveness of law enforcement is greatly affected by the information he or she has at their fingertips when responding to that call.

Do you really want to leave it to chance that that officer’s life is taken, or a criminal  or terrorist is let go because his or her agency wasn’t “lucky enough” to win the grant lottery that year?

So, let’s empower the single most powerful force that can make sure the information is available – the Sheriff or Chief leading that agency. Let’s stop with the unfunded mandates, laws, standards, studies, point papers, etc., and let’s finally put a project in-place with the funding necessary to make it happen.

v/r

Chuck Georgo,

Executive Director
NOWHERETOHIDE.ORG
chuck@nowheretohide.org

30.09.2008 data sharing, Information sharing, Strategy, Uncategorized Comments Off on WARNING: Successful Law Enforcement Information Sharing Can be Hazardous to Your Career

WARNING: Successful Law Enforcement Information Sharing Can be Hazardous to Your Career

Well, the news is out-John McKay was put on the list of U.S. Attorneys to be fired because “McNulty’s office was unhappy that McKay had tried to force McNulty to act on the LInX matter” [quoted from the 392 page DOJ report that can be read at this link–http://seattletimes.nwsource.com/ABPub/2008/09/29/2008212881.pdf

LInX is the Naval Criminal Investigative Service’s Law Enforcement Information Sharing Project. Those of you that know me know that I was an architect of the LInX approach and a project manager for many of the LInX locations over a five year period.  What many don’t realize is that LInX was started by the Navy with a mere $50,000 purchase order.  Through what was a largely grass-roots efforts by state and local law enforcement executives, fueled by the leadership of John McKay (one of the fired U.S.Attorneys) and Dave Brant (former NCIS Director), LInX has grown to a nearly $100 million dollar project in nine major regions around the U.S. 

What’s particularly interesting about this whole saga is that when John took this information sharing success story to his leadership and offered it up as a “proven approach to nationwide information sharing,” they put the politics of internal DOJ projects ahead of the needs of state and local law enforcement and in the process took a good man down.  

Unfortunately, they saw LInX as a competing “IT system” and not as what I and others believed–that LInX really was “a proven and standardized process for organizing, implementing, and evaluating regional law enforcement information sharing.”  I and others believed the LInX approach could have been implemented with many of the other IT systems currently in use around the country at that time (or being developed) for information sharing.  We also recognized that LInX was not a threat to any of the national-level systems being developed by DOJ (or DHS) and, in-fact, (as DOJ would attest to today) are now convinced that those national efforts CANNOT succeed unless LInX-like information sharing projects are quickly replicated in other parts of the country.

While I am sure the final chapter in the U.S. Attorney firings has yet to be written, my hope is that the recently released report will help us to move past federal politics and realize that the true victims here are the state and local law enforcement agencies who were cheated out of a proven approach to enabling the electronic sharing of each other’s law enforcement records–let’s give the LInX approach (and what John and Dave started) its due and develop a formal project to make the process available to other’s who are still struggling with getting it done.  I’ve summarized the LInX approach below. 

STEPS IN THE LINX APPROACHIt is NOT about the technology.

  1. Strategy – Develop a regional law enforcement plan detailing areas of concern and how to leverage information sharing for the desired impact.
  2. Governance – Establish an information sharing governance infrastructure that gives each participating Chief Executive Officer an equal vote on all matters pertaining to the regional LInX system.
  3. Data – Identify and agree to integrate ALL relevant data. The key to success is sharing more not less information.  
  4. Capabilities – Provide easy to use query and analysis tools, with multi-levels of security. LInX is a system developed by law enforcement personnel for law enforcement personnel. Feedback from user groups and the flexibility to make enhancements to the system keeps the LInX system robust and valuable to the community.
  5. Technology – The LInX system is built with open standards and leverages existing technology to integrate diverse systems. An open standards architecture that is flexible, scalable, sharable, and possess the ability to enhance current systems interfaced with.
  6. Full Support – There are some requirements for the participating agencies. The goal is to have minimal impact on a participating agency’s resources, however, there is a need to support user training, system administration, and maintenance.
  7. Evaluation – Conduct formal evaluations to assess achievement of desired impact. The LInX system is being developed to enhance law enforcement utilizing technology to assist the investigator and patrol officer.