Skip to content
Datablare
Claude Code Manufacturing Executive overview

Plant comparison: output and attainment

Pune leads output with 1,575,170 good units; Chennai trails at 82.5% of plan, held back by breakdowns.

Data
Synthetic manufacturing plant demo data (PostgreSQL)
Asked in
Claude Code
Updated
Try this on your data

1 · The brief

What Claude Code was asked

I run three plants. Give me an executive comparison for 2026: good units, plan attainment, availability and yield per plant, monthly output by plant, and what causes downtime at each plant.

Given exactly like this. Claude Code asked Datablare which tables it could read, wrote the SQL itself, ran each query through Datablare and built the dashboard from what came back.

2 · The dashboard

The dashboard Claude Code built

Plant comparison: output and attainment dashboard: Good units per month by plant, Plan attainment by plant, Downtime by plant and reason, Plants

Built from 3 read-only queries. Every figure on the dashboard was read from the database through Datablare; nothing was estimated or typed in.

Headline numbers (January–October 2026):

  • Pune: 1.58M (86.3% of plan · 97.3% yield)
  • Sanand: 1.56M (85.9% of plan · 97.3% yield)
  • Chennai: 1.51M (82.5% of plan · 96.0% yield)
  • Lowest availability: 91.8% (Chennai)

What stands out:

  • Good units per month by plant: Monthly output for each plant
  • Plan attainment by plant: Chennai is lowest at 82.5%
  • Downtime by plant and reason: Breakdowns dominate at Chennai
  • Plants: Output, plan, availability and yield, 2026

The data is a synthetic manufacturing plant dataset made for this example, so the numbers describe no real company. The queries, the dashboard and the audit entries are real: Claude reached the database only through Datablare, read-only, and every query is on record with the question it served.

3 · What Datablare ran

3 read-only queries, nothing changed

Each query below is copied from the audit log of this run. Datablare checked that it only reads, ran it read-only, and gave only the rows to Claude Code; it never stores them.

  1. Query 1

    Good units, plan attainment, availability and yield by plant, 2026

    3 rows · 68 ms

    SELECT l.plant, sum(r.good_units) AS good_units,
           round(sum(r.good_units)::numeric / sum(r.planned_units), 4) AS plan_attainment,
           round(sum(r.runtime_min)::numeric / sum(r.runtime_min + r.downtime_min), 4) AS availability,
           round(sum(r.good_units)::numeric / sum(r.good_units + r.scrap_units), 4) AS yield
    FROM manufacturing.production_runs r
    JOIN manufacturing.lines l ON l.id = r.line_id
    WHERE r.run_date >= DATE '2026-01-01'
    GROUP BY 1
    ORDER BY 2 DESC
  2. Query 2

    Good units by plant and month, 2026

    30 rows · 68 ms

    SELECT to_char(date_trunc('month', r.run_date), 'YYYY-MM') AS month, l.plant, sum(r.good_units) AS good_units
    FROM manufacturing.production_runs r
    JOIN manufacturing.lines l ON l.id = r.line_id
    WHERE r.run_date >= DATE '2026-01-01'
    GROUP BY 1, 2
    ORDER BY 1, 2
  3. Query 3

    Downtime hours by plant and reason, 2026

    15 rows · 63 ms

    SELECT l.plant, r.downtime_reason, round(sum(r.downtime_min) / 60.0, 0) AS downtime_hours
    FROM manufacturing.production_runs r
    JOIN manufacturing.lines l ON l.id = r.line_id
    WHERE r.run_date >= DATE '2026-01-01' AND r.downtime_reason IS NOT NULL
    GROUP BY 1, 2
    ORDER BY 1, 2
Tables read manufacturing.linesmanufacturing.production_runs

4 · The audit entry

Who asked what, on record

Every query is recorded with the person who asked, the question in their words and why the agent ran it. Admins see this in the audit log; nothing reaches the database without it.

How the audit log works

query_data_source

via Claude Code

Allowed
Who
The person signed in (hidden on this public page)
Question
I run three plants. Give me an executive comparison for 2026: good units, plan attainment, availability and yield per plant, monthly output by plant, and what causes downtime at each plant.
Intent
Good units, plan attainment, availability and yield by plant, 2026
Result
3 queries, 48 rows, read-only

More use cases

All examples
  • Production output, yield and downtime dashboard: Good units per week, Downtime by line, Downtime by reason, Scrap rate by line, Lines
    Claude Code Manufacturing Operations

    Production output, yield and downtime

    4.64M good units at 96.9% yield and 84.9% plan attainment, with downtime by line and reason pointing at Line B2.

    Updated Open

  • Shift performance across the plant dashboard: Plan attainment by shift, per month, Downtime hours by shift, Downtime by line and shift, Scrap rate by shift
    Claude Code Manufacturing Operations

    Shift performance across the plant

    The night shift reaches 80.9% of plan against 86.9% in the morning, scraps 4.2% and loses 1,357 hours.

    Updated Open

  • E-commerce sales and retention dashboard dashboard: Monthly revenue, Revenue by category, 2026, Lifetime revenue per customer, by channel, Orders per month
    Claude Code E-commerce Executive overview

    E-commerce sales and retention dashboard

    ₹5.21M revenue from 11,897 orders this year, a 57.9% repeat-customer rate, and which channels bring the customers who spend most.

    Updated Open

Build this on your own data.

Connect your database, choose the tables Claude may read, and give it the same brief. Claude is connected in about two minutes.

30 minutes with the founder. Or WhatsApp / [email protected]