Arizona's $24-Million Prison Management Software Is Keeping People Locked Up Past The End Of Their Sentences

from the taking-life,-wasting-tax-dollars dept

The Arizona Department of Corrections is depriving inmates of freedom they've earned. Its $24 million tracking software isn't doing what it's supposed to when it comes to calculating time served credits. That's according to whistleblowers who've been ignored by the DOC and have taken their complaints to the press. Here's Jimmy Jenkins of KJZZ, who was given access to documents showing the bug has been well-documented and remains unfixed, more than a year after it was discovered.

According to Arizona Department of Corrections whistleblowers, hundreds of incarcerated people who should be eligible for release are being held in prison because the inmate management software cannot interpret current sentencing laws.

KJZZ is not naming the whistleblowers because they fear retaliation. The employees said they have been raising the issue internally for more than a year, but prison administrators have not acted to fix the software bug. The sources said Chief Information Officer Holly Greene and Deputy Director Joe Profiri have been aware of the problem since 2019.

The management software (ACIS) rolled out during the 2019 Thanksgiving holiday weekend, which is always the best time to debut new systems that might need a lot of immediate tech support. Since its rollout, the software has generated 19,000 bug reports. The one at the center of this ongoing deprivation of liberty arose as the result of a law passed in June of that year. The law gave additional credit days to inmates charged with low-level drug offenses, increasing the credit from one day for every six served to three days for every seven.

Qualified inmates are only supposed to serve 70% of their sentences, provided they also complete some other prerequisites, like earning a GED or entering a substance abuse program. That law hasn't been implemented in the Arizona prison system because the $24 million software can't seem to figure out how to do it.

To be sure, legislation that changes time served credits for only a certain percentage of inmates creates problems for prison management systems. But that's why you spend $24 million buying one, rather than just asking employees if they're any good at Excel.

But that's what has actually happened. With the expensive software unable to correctly calculate time served credits, prison employees are doing it by hand.

Department sources said this means “someone is sitting there crunching numbers with a calculator and interpreting how each of the new laws that have been passed would impact an inmate.”

“It makes me sick,” one source said, noting that even the most diligent employees are capable of making math errors that could result in additional months or years in prison for an inmate. “What the hell are we doing here? People’s lives are at stake.”

Hundreds of inmates are affected. A spokesperson for the prison system says the DOC has identified 733 inmates who qualify for the increased time served credits. But that number is still likely on the low end since the software is incapable of accurately identifying qualifying inmates, much less accurately calculating the length of time they have left to serve.

Meanwhile, the bug that's killing freedom remains unpatched. And it appears the software's many other bugs are making time spent in prison even more dangerous and miserable than it already is. Medical information goes missing or fails to transfer correctly when inmates are moved. Rival gang members have been placed in the same cells. Head counts are inaccurate. Inmate property and commissary funds are routinely recorded incorrectly.

Prison is already a miserable experience. Those trying to turn their lives around and engage in the rehabilitative process most prisons consider to be ancillary at best are being punished for trying by a system that is failing everyone who uses it or is affected by it.

Hide this

Thank you for reading this Techdirt post. With so many things competing for everyone’s attention these days, we really appreciate you giving us your time. We work hard every day to put quality content out there for our community.

Techdirt is one of the few remaining truly independent media outlets. We do not have a giant corporation behind us, and we rely heavily on our community to support us, in an age when advertisers are increasingly uninterested in sponsoring small, independent sites — especially a site like ours that is unwilling to pull punches in its reporting and analysis.

While other websites have resorted to paywalls, registration requirements, and increasingly annoying/intrusive advertising, we have always kept Techdirt open and available to anyone. But in order to continue doing so, we need your support. We offer a variety of ways for our readers to support us, from direct donations to special subscriptions and cool merchandise — and every little bit helps. Thank you.

–The Techdirt Team

Filed Under: acis, arizona, arizona department of corrections, early release, holly greene, joe profiri, prison management, software


Reader Comments

Subscribe: RSS

View by: Time | Thread


  • identicon
    Baron von Robber, 23 Feb 2021 @ 12:19pm

    If tone = not white, then n=n+1 more years, else goto freedom.

    reply to this | link to this | view in chronology ]

    • icon
      Samuel Abram (profile), 23 Feb 2021 @ 12:28pm

      Re:

      Here's how I would write it:

      if (skin.tone(!white))
      {
      years++;
      }
      else
      {
      prison.exit();
      }

      I tried code-blocking the whole thing, but the "<br />" html tags kept showing up instead of proper line breaks.

      reply to this | link to this | view in chronology ]

    • identicon
      Anonymous Coward, 23 Feb 2021 @ 12:29pm

      Re:

      They could probably get that code in to the program easily as it is adding time to a sentence.

      I find it hard to believe that they cannot easily add the code for this to the program. A better guess is someone put this sentence reduction program together but never got any funding the modify the code.

      reply to this | link to this | view in chronology ]

      • identicon
        Anonymous Coward, 23 Feb 2021 @ 11:17pm

        Re: Re:

        >A better guess is someone put this sentence reduction program together but never got any funding the modify the code.

        No guess. The law changed after the program was written. The Developer says it's not a bug because the new law wasn't in the original contracted specifications--so, pay up or it's Not Our Problem.

        reply to this | link to this | view in chronology ]

        • identicon
          Brian, 24 Feb 2021 @ 10:26am

          Re: Re: Re:

          As a software engineer, I would argue this is a bug; even if the specification changed at a later date. The software company should have made the rules configurable because it is well established that laws continually change.

          reply to this | link to this | view in chronology ]

    • icon
      Thad (profile), 23 Feb 2021 @ 2:21pm

      Re:

      If tone = not white, then n=n+1 more years

      Objection. You're using the equals sign for both assignment and comparison.

      reply to this | link to this | view in chronology ]

    • icon
      TaboToka (profile), 23 Feb 2021 @ 5:55pm

      Re:

      Code golf time!

      const WHITE; (tone === WHITE) ? freedom() : years++;

      reply to this | link to this | view in chronology ]

  • icon
    That One Guy (profile), 23 Feb 2021 @ 12:27pm

    Easy and quick fix, IF the desire was there

    You could get the software patched in less than a week if it was mandated that the execs of any company selling such software, and those running the prisons who have been informed of the problem but ignored it would be sentenced to spend an equal amount of time in prison as those that the software keeps incarcerated, calculated on a monthly basis.

    Much like the silk-glove treatment police get from politicians and courts so long as it's someone else suffering the consequences there's no real incentive to change anything. Someone spends a few months/years longer in prison then they should have? Eh, no big deal, they shouldn't have been convicted in the first place if they didn't want to suffer, and besides it's not like convicts are people or anything.

    reply to this | link to this | view in chronology ]

    • icon
      Thad (profile), 23 Feb 2021 @ 2:25pm

      Re: Easy and quick fix, IF the desire was there

      You could get the software patched in less than a week if it was mandated that the execs of any company selling such software, and those running the prisons who have been informed of the problem but ignored it would be sentenced to spend an equal amount of time in prison as those that the software keeps incarcerated, calculated on a monthly basis.

      ...you think that would incentivize them to make that number easier to calculate?

      reply to this | link to this | view in chronology ]

      • icon
        That One Guy (profile), 23 Feb 2021 @ 4:02pm

        Re: Re: Easy and quick fix, IF the desire was there

        If they knew that mistakes would result in them seeing the inside of a cell I imagine they'd go above and beyond to ensure that the system was as mistake-free and easy to understand as possible.

        reply to this | link to this | view in chronology ]

    • icon
      Uriel-238 (profile), 23 Feb 2021 @ 2:56pm

      Less easy and quick fix

      Maybe take seriously the notion of abolishing the entire fucking justice system.

      There's no valid reason we have more inmates than China, and more per capita than any nation in the world.

      Oh wait, maybe because we're addicted to the slave labor and the government contracts for private prisons?

      reply to this | link to this | view in chronology ]

  • identicon
    Anonymous Coward, 23 Feb 2021 @ 1:08pm

    I see that Terry Gilliam's Brazil continues to be an inspiration for the policies and procedures of state governments...

    reply to this | link to this | view in chronology ]

  • identicon
    Anonymous Coward, 23 Feb 2021 @ 1:34pm

    was $24million.....

    With lawsuits, $124 million or so? higher?

    reply to this | link to this | view in chronology ]

  • icon
    That Anonymous Coward (profile), 23 Feb 2021 @ 3:47pm

    Official misconduct.
    Holding citizens past the date of their leaving the system.

    I mean its not like we had to pass laws to give money to people railroaded to prison by bad cops/judges/prosecutors... (and of course immediately attempted to put more road blocks into compensating them for being screwed for decades).

    No one cares because they are bad people, if they weren't bad people they wouldn't be in prison. $24 million to what I am sure is a powerful donor, for a system unable to do the job. Perhaps some of them need to be imprisoned with this system running their release dates.

    reply to this | link to this | view in chronology ]

  • identicon
    Châu, 23 Feb 2021 @ 4:18pm

    Open Source for < 24 million $

    State can hire one group of 5 or less good computer science students in University Of Arizona during summer build open source prison software can update and fix any time.

    reply to this | link to this | view in chronology ]

  • icon
    crazy_diamond (profile), 23 Feb 2021 @ 9:04pm

    This is obviously a bug which became a feature for Arizona "law enforcement". How many times do we have to be reminded that the purpose of policing in this country is to inflict maximum brutality and terror on the marginalized for no other reason than to have favored population feel "safe", and to keep the money flowing for cops. The affluent and otherwise powerful don't see this as a problem, because their fate will never depend on this system because they'll never see the inside of a cell.

    reply to this | link to this | view in chronology ]

    • identicon
      Anonymous Coward, 23 Feb 2021 @ 11:42pm

      Re:

      There's no hint in the actual news that race was involved. Why do so many people assume that there are no other evils in the world.

      In my experience (actually developing and using large systems) the greatest evil is even attempting a multi-decamillion-dollar one-size-fits-all program. It wouldn't fit all if it worked, and very few organizations can organize to create such a program that works. Not to mention the fact that nobody but an expert programmer who also knows everything about the user's systems, can specify what 'working' even means at that scale. (And there is almost never such a persion. I new one....once.) It's not a summer project for comp sci students who've never worked on anything larger than an 800-line semester project which took, in their ignorant stumblings, 2000 lines of code.

      So you have top-level bureaucrats (or their henchlings in one department) trying to write down what everyone in another very-large department knows about how their job is done. The specification writers don't know what questions to ask, or whom to ask them of. Of course the specifications are rubbish--thousands of actual errors, and thousands more incoherent blatherings that fail to be errors only by failing to communicate any idea, true or false. The programmers don't have a chance.

      Not that they'd be able to take it if they had. Middle managers seeing big-dollar bonuses if their work-units deliver ahead of schedule, push to ignore problems that are found (or better yet, fail to look for problems and don't find them). The actual work is done by comp-sci graduates who mostly don't have the skills and experience to handle 10,000-line programs, let alone the actual size. They will be lucky to only deliver thousands of bugs. And the system they deliver will be fragile--one bug fix or spec-update will likely introduce 2 or more bugs. It will be opaque--nobody will be able to tell why it does things without consulting the code, which the user doesn't have access to. And it will be hated, passionately hated, by all its users for the extra work it imposes on them.

      For x tens of millions of dollars, that's what you will always get. Unless the user-organization is managed and staffed by professional engineers, in which case it will know how to create a spec and hold the contractor to it.

      So what's really going on here? Nothing in the race wars. Nothing even hinky in the software developer. Just the usual human bumbling, resulting in millions of dollars spent, after which much of the real work has to be done manually, just like it had been done before.

      reply to this | link to this | view in chronology ]

      • icon
        Scary Devil Monastery (profile), 24 Feb 2021 @ 1:29am

        Re: Re:

        "There's no hint in the actual news that race was involved. Why do so many people assume that there are no other evils in the world."

        No one mentioned race - only the marginalized; Of course when it comes to US prisons, that means poor people and, yes, brown people.

        The human bumbling you describe certainly doesn't have it in for any human concerns beyond saving money and cutting corners, with not a single nod towards which demographic gets to suffer the most of those actions. This is what would be called systemic racism - because it hits a given demographic harder than others without specific intent to do so, or the primary mechanisms of the discrimination not necessarily within the action chain discussed.

        reply to this | link to this | view in chronology ]

    • identicon
      Anonymous Coward, 24 Feb 2021 @ 12:14pm

      Re:

      There's no hint in the actual news that race was involved. Why do so many people assume that there are no other evils in the world.

      In my experience (actually developing and using large systems) the greatest evil is even attempting a multi-decamillion-dollar one-size-fits-all program. It wouldn't fit all if it worked, and very few organizations can organize to create such a program that works. Not to mention the fact that nobody but an expert programmer who also knows everything about the user's systems, can specify what 'working' even means at that scale. (And there is almost never such a persion. I new one....once.) It's not a summer project for comp sci students who've never worked on anything larger than an 800-line semester project which took, in their ignorant stumblings, 2000 lines of code.

      So you have top-level bureaucrats (or their henchlings in one department) trying to write down what everyone in another very-large department knows about how their job is done. The specification writers don't know what questions to ask, or whom to ask them of. Of course the specifications are rubbish--thousands of actual errors, and thousands more incoherent blatherings that fail to be errors only by failing to communicate any idea, true or false. The programmers don't have a chance.

      Not that they'd be able to take it if they had. Middle managers seeing big-dollar bonuses if their work-units deliver ahead of schedule, push to ignore problems that are found (or better yet, fail to look for problems and don't find them). The actual work is done by comp-sci graduates who mostly don't have the skills and experience to handle 10,000-line programs, let alone the actual size. They will be lucky to only deliver thousands of bugs. And the system they deliver will be fragile--one bug fix or spec-update will likely introduce 2 or more bugs. It will be opaque--nobody will be able to tell why it does things without consulting the code, which the user doesn't have access to. And it will be hated, passionately hated, by all its users for the extra work it imposes on them.

      For x tens of millions of dollars, that's what you will always get. Unless the user-organization is managed and staffed by professional engineers, in which case it will know how to create a spec and hold the contractor to it.

      So what's really going on here? Nothing in the race wars. Nothing even hinky in the software developer. Just the usual human bumbling, resulting in millions of dollars spent, after which much of the real work has to be done manually, just like it had been done before.

      reply to this | link to this | view in chronology ]

  • identicon
    Anonymous Coward, 24 Feb 2021 @ 11:15pm

    $24 million BRICK

    i've seen that before and it's likely due to the very strict provisions of the initial contract with no provision for follow-up payment for development of new functions.

    they probably bought a $24 million immutable, non-evolving BRICK as if it were a sack of potatoes - contract and funtional specs nailed shut at signing time, binary code only, no ownership of source code.

    They wanted a fixed quantifiable brick, they got one.

    Now they want to shape and squeeze that brick to fit into a shape that's somewhere between "brick" and has round corners like an "egg"... but that is not covered by the terms in the initial very-specific-contract.

    They basically want a new car with more bells and whistles by just trading in the old car.

    reply to this | link to this | view in chronology ]


Add Your Comment

Have a Techdirt Account? Sign in now. Want one? Register here



Subscribe to the Techdirt Daily newsletter




Comment Options:

  • Use markdown. Use plain text.
  • Remember name/email/url (set a cookie)

Close

Add A Reply

Have a Techdirt Account? Sign in now. Want one? Register here



Subscribe to the Techdirt Daily newsletter




Comment Options:

  • Use markdown. Use plain text.
  • Remember name/email/url (set a cookie)

Follow Techdirt
Insider Shop - Show Your Support!

Advertisement
Report this ad  |  Hide Techdirt ads
Essential Reading
Techdirt Deals
Report this ad  |  Hide Techdirt ads
Techdirt Insider Chat
Advertisement
Report this ad  |  Hide Techdirt ads
Recent Stories
Advertisement
Report this ad  |  Hide Techdirt ads

This site, like most other sites on the web, uses cookies. For more information, see our privacy policy. Got it
Close

Email This

This feature is only available to registered users. Register or sign in to use it.