Confluent Public Sector New Zealand

Palmerston North City Council

Customer Service Automation · IT Operations Automation · Real-time Analytics

Palmerston North City Council needed to break data out of spreadsheets and siloed on-premises systems so citizen services, regulatory workflows, and AI initiatives could run on trusted real-time information instead of slow manual handoffs.

around 25 manual steps
minutes instead of hours
once a quarter to just a couple of sprints
over 200 cameras and sensors

Reported impact

Business outcome

PNCC cut service response times from hours to minutes, sped up delivery of new digital services, reduced manual work in finance and regulatory processes, and created a more auditable foundation for smart-city and AI-assisted operations.

  • Compliance
  • Customer Experience
  • Productivity Improvement
  • Speed to Market

Solution

Palmerston North City Council deployed Confluent Cloud as the backbone of a shift-left, event-sourced data architecture for civic operations. Every piece of data - whether it arrives from IoT devices, APIs, supplier files, finance systems, or regulatory applications - now flows through the managed streaming platform first, where governance and reuse are applied at the source. Kafka topics hold the history of data products, which the council then syncs into relational, NoSQL, time-series, and lake environments as needed. On top of that base, PNCC created reusable Property 360 datasets, real-time AI-assisted invoice processing, human-in-the-loop AI agents for resource-consent workflows, and smart-city monitoring that streams insights from hundreds of cameras and sensors. The architecture lets departments share one governed source of truth, shortens response times for citizen issues, and provides auditable orchestration for automation without handing final decisions to AI.

Data flow

IoT devices, APIs, supplier files, financial systems, and regulatory applications publish events into Confluent Cloud, where PNCC governs and reuses them as data products for search, citizen-service workflows, AI-assisted invoice processing, and smart-city monitoring across downstream stores and services.

Solution architecture

2 components · 2 layers
  1. Governance
    • Schema Registry Supports governed, reusable data products that can be trusted across departments and AI-assisted workflows.
  2. Uncategorized
    • Confluent Cloud Acts as PNCC's central streaming backbone for operational, regulatory, and smart-city data.

Architecture clues

  • AI agents orchestrate resource-consent steps via Kafka topics while keeping humans in the loop for final decisions.
  • PNCC uses an event-sourced model with Kafka topics kept as the source of truth for data products.
  • The architecture fans governed data into relational, NoSQL, time-series, and lake storage systems.

Evidence from the source

Every piece of data - whether from IoT devices, APIs, or file uploads - flows through Confluent Cloud for processing and distribution in real time.
PNCC can process citizen service requests in minutes instead of hours.
PNCC is piloting the automation of up to 15 of these steps with AI agents that run continuously, while keeping humans in the loop for all decisions.
Resource consent applications involve around 25 manual steps.
Transparency Evidence & methodology 75/100 reference value · 77% 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 value75/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 impact0/25
    0 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence77%
  • 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
    4 direct source quotes retained.
  • Date provenance0/10
    The publication date has no documented provenance.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity8/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. Confluent

    Palmerston North City Council customer story

    First-party
    https://www.confluent.io/customers/pncc/
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes

Date evidence

  • First archived Aug 21, 2025 · Internet Archive · Independent First Wayback Machine capture; confirms the page existed by this date, not when it was published.
    Open date source
  • Sitemap last modified Oct 11, 2026 · Confluent · Publisher metadata Publisher-reported modification timestamp; not a publication date.
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.