Failures
from the setting-money-on-fire dept
Thu, Jun 27th 2024 12:30pm - Tim Cushing
Well, we’ll see how long ShotSpotter/SoundThinking will keep making that New York money. The outlook is not good. A lot of this will depend on how well the NYPD can defend the useless product it’s spending millions on, but at the end of the day, the city still holds the purse strings and it has the power to terminate contracts that simply aren’t worth paying for.
The NYC comptroller performed an audit of the NYPD and ShotSpotter not with the intent of burying them, but simply to determine whether or not the NYPD was paying its bills on time and whether or not ShotSpotter was fulfilling the obligations of its contract.
The answer to both questions is “No.”
First, the comptroller takes on ShotSpotter and its guarantees of certain amount of law enforcement success:
When measured against the contractual performance standards set by NYPD, ShotSpotter met its 90% target for avoiding missed incidents in almost all boroughs except Manhattan, but when measured against the number of confirmed shootings, performance is far lower. During the sampled months of review in 2022 and 2023, ShotSpotter alerts only resulted in confirmed shootings between 8% and 20% of the time.
That’s pretty terrible, especially by the standards ShotSpotter claims to hold itself. When you’re wrong that often, you start costing cities real money while providing very little value in exchange.
During the month of June 2023, for example, out of the 940 ShotSpotter alerts that NYPD responded to 771 could not be confirmed as shootings upon arrival at the scene (82%), 47 were determined to be unfounded (5%), and 122 were confirmed as shootings (13%). NYPD officers spent 426.9 hours investigating alerts that were not confirmed as shootings. If only one officer responded, this equates to almost 36 twelve-hour shifts; if two officers responded, this number doubles.
More than 427 hours of wasted payroll in a single month. That’s pretty f*cking terrible. But it could actually be much worse. There’s no way to know how much payroll is being blown by officers responding to ShotSpotter alerts because (surprise surprise!) the NYPD does not “track the amount of time — or associated staff costs — spent responding to such instances.”
I’ll try not to read too much into the NYPD’s disagreements with the comptroller’s conclusions, but they sound eerily like the new wave of PR emanating from SoundThinking HQ: the real value of ShotSpotter isn’t measured in arrests and prosecutions but rather lives saved. According to its new set of talking points, ShotSpotter brings EMS units to shooting victims faster, resulting in fewer lives lost to gun violence.
Maybe it would have a point if anyone was tracking this particular factor. But no one is, not even the NYPD which uses the same exact argument to excuse ShotSpotter’s underperformance:
NYPD does not agree that confirmed shootings should be used to measure ShotSpotter’s performance. It asserts that ShotSpotter improves the response time to possible shots fired which in turn increases the ability to provide assistance to victims, increases officers’ safety, and provides a more accurate location of the possible shooting than a 911 call alone.
However, NYPD does not measure ShotSpotter alert response times in comparison to 911 call response times to shots fired outside, the metric most closely aligned to ShotSpotter alerts.
Since the NYPD can’t or won’t do it, the comptroller’s office did what it could with available data. And that data contradicts the claims made by the NYPD (and, indeed, claims made by ShotSpotter itself).
The audit analyzed the two data sets, NYPD’s internal OCD ShotSpotter Tracking report and the Open DataNYPD Call for Servicereport, and found that during the month of June 2023 average response times to ShotSpotter alerts were 1 minute and 38 seconds faster than response times to reports to 911 of outdoor shots fired (3 minutes 50 seconds for ShotSpotter versus 5 minutes 28 seconds for 911), far less than the difference of 5 minutes claimed in publicly-available data.
So far, the NYPD has spent $45 million on ShotSpotter since 2014. Another $9 million will have to be spent before the contract expires in December of this year. That’s not much compared to the PD’s multi-billion dollar budget, but it’s still money that could be spent elsewhere on more useful things or, if legislators are trying to do a bit of budget balancing — not spent at all.
The comptroller has suggestions, most of which the NYPD disagrees with. The NYPD should track and publish data on ShotSpotter alerts, including the percentage of false or unconfirmed alerts. It already has the capacity to compile this data, but the comptroller wants the PD to pass that info on to the general public.
It also says the NYPD needs to start tracking how many officer hours are wasted responding to ShotSpotter alerts. And, if it really wants to use the argument that ShotSpotter is there to save shooting victims, rather than contribute to shooting investigations, the NYPD should start tracking this information too.
It also recommends the contract with ShotSpotter be allowed to expire at the end of the year. And, until that point, the NYPD should start paying its invoices within 30 days of receiving them as is mandated by the city’s procurement policy. (lol)
The NYPD has responded by saying pretty much everything asked of it is impossible or difficult or something it just doesn’t feel like doing, starting with the recommendation it allow its ShotSpotter contract expire:
NYPD disagreed with this recommendation, stating that “…non-renewal of ShotSpotter services may endanger the public and not renewing the ShotSpotter contract until the Department conducts further analysis would be a premature measure…”
First off, the data the comptroller compiled shows that, in most city boroughs, ShotSpotter is far better at wasting officers’ time than finding shooters or shooting victims. Second, the department should have been conducting “further analysis” ever since the inception of this contract a decade ago. It has no right to be asking for more time to conduct analysis, especially when it’s clear it’s just a stalling tactic meant to help the NYPD slide by the contract termination date and into another (potentially) long-term contract with the company.
Law enforcement agencies and ShotSpotter itself (although more often the latter) continue to defend this questionable tech with vague statements about safety and even more vague representations about its usefulness. But pretty much any city that’s actually dug into the data has come to the same conclusions: ShotSpotter may be an innovative use of acoustic detection tech, but it’s really not worth paying for.
Filed Under: gunshot detection, new york city, nypd, surveillance
Companies: shotspotter, soundthinking
