IBM Public Sector North America

Arizona Department of Child Safety

Customer Service Automation · Document Processing · IT Operations Automation

Arizona DCS needed to reduce manual casework, document handling, policy navigation, and development overhead so staff could make child-safety decisions faster and spend less time on administrative work.

40% productivity gain
5x decrease in document upload time
Data retrieval has become 40% more efficient
approximately 200 different types of documents

Reported impact

Business outcome

Arizona DCS improved classification accuracy, sped policy retrieval, accelerated development workflows, and reduced document-processing effort so caseworkers and analysts could focus more on child and family outcomes.

  • Customer Experience
  • Productivity Improvement
  • Risk Reduction

Solution

Arizona DCS and IBM Consulting used a phased Microsoft Azure and Azure OpenAI transformation to modernize several operational workflows. In the central-registry workflow, Azure OpenAI classifies and subcategorizes allegation narratives to improve retention-period decisions and reduce manual review. A separate virtual assistant built on Azure generative AI helps caseworkers navigate policy documents, retrieve reliable answers with source links, and understand updates faster. The program also integrated TachyonGPT with Azure DevOps to generate user stories, acceptance criteria, and test cases, while Power Platform AI Builder automates document uploads and form prefilling. IBM Consulting Advantage supported internal workflows and program materials throughout the effort. Together these components created a governed operating model where classification, policy search, delivery work, and document processing move faster without removing human oversight from child-safety decisions.

Data flow

Case narratives, policy documents, DevOps work items, and uploaded forms flow through Azure-based generative-AI services, where classification models organize allegations, the virtual assistant retrieves policy answers, TachyonGPT prepares delivery artifacts, and AI Builder reads documents and prefills forms before humans review and act.

Solution architecture

5 components · 2 layers
  1. Compute
    • Microsoft Azure OpenAI Powers allegation classification, policy assistance, and other generative-AI workflows.
    • TachyonGPT Generates and refines DevOps work items such as user stories, acceptance criteria, and test cases.
    • Microsoft Power Platform AI Builder Automates document processing by reading files and prefilling forms for casework workflows.
  2. Orchestration
    • Microsoft Azure Provides the cloud foundation for Arizona DCS's generative-AI modernization program.
    • IBM Consulting Advantage for Cloud Transformation Supports program materials and internal workflows that helped the transformation move faster and more consistently.

Architecture clues

  • Productivity improvements came from integrating Azure OpenAI, Azure DevOps, and Power Platform automation.
  • The transformation was delivered in phases across classification, policy support, DevOps, and document processing.
  • The virtual assistant returns confidence-ranked summaries with links to source material.

Evidence from the source

Data retrieval has become 40% more efficient
The team worked on improving categorization using Microsoft Azure OpenAI tools to generate subcategories for classified allegations
With the power of AI Builder, the team has significantly improved the efficiency of document processing
an AI-powered virtual assistant was created to simplify the process of accessing and understanding policy documents.
the team worked to integrate TachyonGPT ... with an Azure DevOps Board to generate and refine features, user stories, acceptance criteria and test cases.
Transparency Evidence & methodology 95/100 reference value · 89% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value95/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    4 metrics describe measurable impact.
  • Deployment scale5/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence89%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. IBM

    Arizona Department of Child Safety customer story

    First-party
    https://www.ibm.com/case-studies/arizona-dcs-consulting
    Source type
    Vendor-published customer story
    Published
    Nov 14, 2024
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.