With the explosion of social media and smartphones, there has been a growing expectation that police departments and 911 Centers ought to send tailored alerts of potential risks directly to citizens and organizations, such as schools, businesses, assisted living centers, and just ordinary citizens. Last night, a local TV station ran a story about this, interviewing the proprietor of a day care center who was unhappy that she wasn't notified of a shooting that happened at 3:50 AM on Sunday morning a short distance from her business.
There are many software systems out there for delivering mass notifications. The problem is not the lack of technology, rather it is the lack of the infrastructure necessary to exploit the technology. Specifically, it would require personnel. Essentially, someone would need to be dedicated to the task of listening to the radio and watching the flow in the computer-aided dispatch center. This person would need to make a determination about which incidents need to trigger a public alert, to whom it should be sent, and what the content should be. He or she would not only need to compose the alert, but would also need to determine when an "all clear" rescinding the alert is appropriate.
This is no small task. It would require someone with exceptionally good knowledge about the dynamics of police events in the field. Not very many robberies, for example, represent an immediate risk to people in the surrounding area. Many reports are belated, and in many cases the assailant is known to the victim and was long gone before the police were even called. Conversely, a simple hit-and-run crash could turn into an emergency event, if the wanted felon involved in the collision flees the scene on foot armed with a pistol and disappears into the surrounding neighborhood. Although technology can help, this is something that cannot be entirely automated. Human judgement is needed to distinguish the incidents that require notifications from the background noise.
Moreover, a mass notification system like this would need to operate 24 hours a day, seven days a week, 365 days a year. That requires about 5.5 full-time equivalent employees. In a low-volume environment, you might be able to use employees who multi-task, performing other duties but able to drop what they are doing to attend to alerts as needed, a sergeant, for instance, or a dispatcher. That's not going to happen reliably in a busy 911 Center where employees are frequently working mandatory overtime, and where its a struggle just to fill the seats. Consider that during a big event that might suggest an alert, the dispatchers and police officers are especially busy.
If it's so difficult, you might ask, why are universities able to manage such systems, notifying their students and staffs of risky business? Aside from the fact that universities are generally mighty well funded, the simple fact is that your typical university police department is not very busy. As an example, the University of Nebraska Police Department handled 13 incidents yesterday. The Lincoln Police Department handled 334.
I'm not saying "never," but the impediments to such notification systems are substantial. Recently, we have been looking at various notification systems, and trying to brainstorm about how we might possibly incorporate these into our operations. If we had the personnel to do so, we might even use something as simple as the police department's Twitter feed, but it isn't staffed or monitored constantly, and we don't have the people to do so. We've also been considering the feasibility of launching a real time crime center for Lincoln, which might be an ideal location for a public notification system.
In the days before Twitter and Facebook, people turned to the news media in order to stay abreast of things going on in the community. Folks actually used to listen to AM radio, and could follow the news reports of the Martian invasion and take appropriate precautions. If we had some big deal going on and needed to get the word out quickly, a couple of phone calls to the radio stations were obligatory. In every news room in Lincoln, whether print, radio, or television, assignment editors and reporters are listening to police scanners right now. These days, they are often tweeting about interesting or emergent transmissions they hear in near real-time.
For the moment, your workaround might be to simply follow the Twitter feeds of a few of the local news outlets if you really need to know what's breaking bad at any given moment. Rest assured that if we thought a day care, senior center, business, or residence was in imminent risk of harm, we'd be making concerted efforts to notify you the old-fashioned way: door to door, and also through the news media.
Wednesday, June 29, 2016
Monday, June 27, 2016
Out of the ashes
The fire last month that destroyed Ideal Grocery in Lincoln was devastating on several levels. The neighborhood lost a convenient full-service grocery store within walking distance. The City lost a landmark. Lincoln's foodies lost a favorite destination where you could pick up a tin of escargot, a bottle of Veri Veri Teriyaki, and a tube of anchovy paste.
Tonja and I visited Ideal frequently, usually on Saturdays. In addition to the quaint charm of its 1930s vibe, what we really loved about Ideal was the memories it stirred up of Pete's IGA, the tiny 3-aisle store Tonja's dad owned at 31st and U Street--before he went big time with Wagner's IGA at 33rd and A Street. Both buildings are still there. Wagner's is now the A Street Market, not much changed from the time Pete acquired it in 1976.
I worked for Pete for six years at the little store from the age of 15 until I joined the police department. Tonja worked for her dad for 10 years at the "big" store. Every time we went into Ideal, the memories flooded back.
After the fire, I tweeted about one of the things I'd really miss from Ideal: the small wheeled shopping baskets, a precursor to the modern grocery cart. Many others commiserated on Twitter. But here's a surprise.
I stopped into Leon's at Winthrop Road and South Street yesterday to pick up a steak for the grill, and what did I find but the famous Ideal carts, looking pretty much the same as they did during the Hoover administration.
Our checker told us that she helped wire brush the baskets, which were salvaged from the debris. That's a nice save out of the ashes that many Lincoln citizens will continue to enjoy, and explain to their grand children!
Tonja and I visited Ideal frequently, usually on Saturdays. In addition to the quaint charm of its 1930s vibe, what we really loved about Ideal was the memories it stirred up of Pete's IGA, the tiny 3-aisle store Tonja's dad owned at 31st and U Street--before he went big time with Wagner's IGA at 33rd and A Street. Both buildings are still there. Wagner's is now the A Street Market, not much changed from the time Pete acquired it in 1976.
I worked for Pete for six years at the little store from the age of 15 until I joined the police department. Tonja worked for her dad for 10 years at the "big" store. Every time we went into Ideal, the memories flooded back.
After the fire, I tweeted about one of the things I'd really miss from Ideal: the small wheeled shopping baskets, a precursor to the modern grocery cart. Many others commiserated on Twitter. But here's a surprise.
I stopped into Leon's at Winthrop Road and South Street yesterday to pick up a steak for the grill, and what did I find but the famous Ideal carts, looking pretty much the same as they did during the Hoover administration.
Our checker told us that she helped wire brush the baskets, which were salvaged from the debris. That's a nice save out of the ashes that many Lincoln citizens will continue to enjoy, and explain to their grand children!
Monday, June 13, 2016
What we can do
One of the largest mass shootings in the history of the United States yesterday in Orlando has many public safety professionals thinking about what can be done in their local context. While some of the issues are national or even international in scope, there are some very good things we can do at the local level. Here are some thoughts that came to mind over the lunch hour. Although I think we have given all of these some attention, there is always room for improvement.
- We can improve our ability to collect, analyze, and when appropriate disseminate intelligence information. The may mean providing good training to police officers on what to be alert for, how to document suspicious activity, and so forth. We should not forget the community, either. We did a lot of work in the 1990s with landlords and retailers to make them aware of the kinds of activities that might be related to methamphetamine labs. The result was lots of tips that really helped. We need to do the same thing surrounding terrorism and radicalization. We also need to maintain or improve our analytical abilities. This means investing in software, system, and (most importantly) analysts needed to turn information into intelligence,
- We can participate in information sharing and joint agency operations. Participation in joint terrorism task forces, shared information platforms, and even just good informal relationships with our area law enforcement agencies will maximize our opportunities to connect the dots. We must avoid information silos and cultivate an environment of inter-agency collaboration.
- We can cultivate and maintain a good relationship with the LGBTQ community, developing personal relationships with opinion leaders, community members, business owners, and so forth. These citizens feel incredibly vulnerable in the wake of Orlando, and need to be assured that we take our duty to protect them seriously, and are committed to doing our best to vigorously investigate hate crimes and hold perpetrators responsible.
- We can cultivate and maintain good relationships with the Muslim community in our jurisdiction. They need to know that we are concerned for their safety and well-being, that we will protect them and the free exercise of their religion. We need to develop personal relationships of trust, so that Muslim citizens will feel comfortable contacting the police about when they have information we need to know about.
- We can train and exercise for active shooter events and mass casualty events. We can make sure that this training includes everyone that is likely to be working together in such incidents: law enforcement agencies, 911 centers, fire and rescue agencies, hospitals, etc.. We should train for a team effort, because if we ever have such incidents, they will undoubtedly involve all of us.
- We can train police officers in critical emergency care for traumatic wounds. We can make sure that officers have the basic equipment and training that might allow them to save a critically-injured victim before medical personnel can take over patient care.
- We can improve our ability to get life-saving emergency care to patients in danger zones. This will require improving communication between law enforcement personnel and EMS responders. We need to train together with enough regularity that we all understand how we will safely get patients out, and paramedics in, when the threat is still imminent, and the situation only partially stabilized. We need to practice communication, unified command, and collaborative operations in the mundane daily events, such as traffic crashes, so it is second nature when it is most needed.
- We can organize a multi-disciplinary threat management team, with expertise in assessing information and identifying the truly dangerous.
Friday, June 3, 2016
Appears to be working
A few months ago, the Lincoln Police Department implemented a new policy that encourages officers to take advantage more often of a state law that allows vehicles driven by suspended drivers to be impounded for 30 days. The policy change went into effect in late February, and provides an opportunity for a bit of evaluation research.
Since the policy is intended to deter suspended drivers, if it's working we would expect a decrease after implementation. Here's the problem: you can't simply count up the number of suspended driving tickets, because the overall level of traffic enforcement would influence that independent of the policy change. When officers are writing a lot of tickets, they are more likely to encounter suspended drivers then when they are writing fewer tickets.
Traffic enforcement activity by police officers varies considerably over time for several reasons, such as weather, service demands, and staffing levels. As an example, the peak month for tickets in 2015 was March, with 8,046 tickets (both warnings and officials), while the low month, December, produced 5,718. In order to account for these fluctuations, a good measure would be to calculate a percentage of tickets that yielded a suspended driver: suspended driving tickets divided by total tickets.
As the chart shows, that percentage takes a significant drop in the three months since the policy change. In fact, March, April, and May are the lowest months during the entire comparison period, which begins in January, 2013. If the percentage during the past three months had been the same as the average over the preceding 38 months, there would have been 159 additional suspended driving arrests from March through May.
I think this is pretty strong evidence that the policy is having the intended effect, although I'd like to watch it over a longer time period. Sometimes the impact of a crackdown initiative decays quickly over time. Officer Luke Bonkiewicz, whose research credentials are better than mine, is doing some more sophisticated work with these data. In particular, he is also looking at repeat suspended drivers. His work may shed even more light on the efficacy of impounding vehicles. Police practitioners ought to do this stuff more often: simple evaluations that, despite some methodological warts, provide evidence about what might be working (or not.)
Since the policy is intended to deter suspended drivers, if it's working we would expect a decrease after implementation. Here's the problem: you can't simply count up the number of suspended driving tickets, because the overall level of traffic enforcement would influence that independent of the policy change. When officers are writing a lot of tickets, they are more likely to encounter suspended drivers then when they are writing fewer tickets.
Traffic enforcement activity by police officers varies considerably over time for several reasons, such as weather, service demands, and staffing levels. As an example, the peak month for tickets in 2015 was March, with 8,046 tickets (both warnings and officials), while the low month, December, produced 5,718. In order to account for these fluctuations, a good measure would be to calculate a percentage of tickets that yielded a suspended driver: suspended driving tickets divided by total tickets.
As the chart shows, that percentage takes a significant drop in the three months since the policy change. In fact, March, April, and May are the lowest months during the entire comparison period, which begins in January, 2013. If the percentage during the past three months had been the same as the average over the preceding 38 months, there would have been 159 additional suspended driving arrests from March through May.
I think this is pretty strong evidence that the policy is having the intended effect, although I'd like to watch it over a longer time period. Sometimes the impact of a crackdown initiative decays quickly over time. Officer Luke Bonkiewicz, whose research credentials are better than mine, is doing some more sophisticated work with these data. In particular, he is also looking at repeat suspended drivers. His work may shed even more light on the efficacy of impounding vehicles. Police practitioners ought to do this stuff more often: simple evaluations that, despite some methodological warts, provide evidence about what might be working (or not.)
Subscribe to:
Posts (Atom)