---
type: project
tags: [project, hod-quality, toyota, kpi, performance]
status: active
---

# 📊 QC Mgr KPI Dashboard

**Folder:** `HOD_Quality_ASSB/qc_mgr_kpi/`
**Plant:** Bukit Raja Klang
**Owner:** Nizmax (HOD Quality)
**Reporting:** GM Richi Lim (immediate superior)

---

## 🎯 Purpose

Track KPIs for each QC Manager reporting to Nizmax-san. Surfaces daily/weekly/monthly performance, supports PMDS reviews, identifies coaching opportunities.

## 👥 Managers in scope

| Name | Role | Stage (PMDS) |
|---|---|---|
| Hisyam | Mgr QC | Checked |
| Razmair | Asst Mgr QC | Prepared |
| *(add others as joined)* | | |

## 📂 Folder layout

- `raw_data/` — Source CSVs/JSONs (Toyota QMS extracts, training records, complaint logs)
- `dashboards/` — One HTML dashboard per manager + combined views
- `pmds/` — PMDS scoring sheets per cycle
- `coaching/` — Coaching notes, action items, follow-ups
- `reports/` — Generated weekly/monthly summaries

## 📊 KPI framework (TBD — first session)

Candidate KPIs per manager (4-6 metrics each):

1. **PPM (Parts Per Million defects)** — incoming + outgoing
2. **Audit score** — internal ISO 9001 / process audit results
3. **Training compliance** — % required courses completed
4. **Defect closure rate** — time from open to close
5. **Customer complaint cycle time** — receipt to containment
6. **On-time delivery (PPH/PPD)** — schedule adherence

## 🔄 Review cadence

- **Weekly sync** — Mon 9:00 AM (Hisyam + Razmair + Nizmax)
- **Monthly PMDS prep** — first week of each month
- **Quarterly deep review** — with GM Richi Lim

## 📡 Data feeds (to integrate)

- Toyota QMS — PPM, defect logs
- Customer complaint system (TCCS)
- Training records — i-Learn / corporate LMS
- Inspection logs — manual extract from TQI sheets

## 🔗 Cross-references

- **Parent folder:** `HOD_Quality_ASSB/` (HOD role)
- **Discord:** #QC Mgr KPI Dashboard category, #qc-mgr-kpi-dashboard forum
- **Sibling project:** `performance_ranking/` (PMDS 2026 dashboard — model for format)
- **Sibling project:** `ai_database/` (AI insights, supplier quality)
- **Hub:** https://botbot-main-hub.pages.dev/

## 📅 History

- **13 Jul 2026** — Folder spun up by BotBot. Discord category + forum + root thread created. Local folder structure initialised. Initial task list posted to root thread.

---

# 💰 CapEx FY2027 Utilisation Tracker (sub-project)

**Live dashboard:** https://botbot-main-hub.pages.dev/capex_dashboard
**Live state:** https://botbot-main-hub.pages.dev/capex_state.json
**Live audit log:** https://botbot-main-hub.pages.dev/capex_audit.log

## 🎯 Purpose

Track utilisation of QCD CapEx budget FY2027 (26 lines, RM 2.6M total) across SAP / BRP / CF plants. Surfaces commitment, utilisation, overdue items by target date and stalled-by-age.

## 🔒 Read-only access model (Option A)

The dashboard is **always read-only** for everyone. Edits happen via BotBot on Telegram, owner-only (sir / Nizmax).

## ⌨️ Commands

Send to BotBot on Telegram:

| Command | What it does |
|---|---|
| `capex status` | Show breakdown by stage (Planning → GRA/Closed) |
| `capex move #N <stage>` | Move item #N to stage (e.g. `#4 PO Issued`) |
| `capex set #N YYYY-MM-DD` | Set target date for item #N |
| `capex audit [N]` | Show last N audit entries (default 10) |
| `capex help` | Full command list |

### Stage names accepted
`Planning`, `Plan`, `0`, `PR Issued`, `PR`, `Issued`, `1`, `PO Issued`, `PO`, `Ordered`, `2`, `Item Received`, `Received`, `Recv`, `3`, `GRA`, `Closed`, `Done`, `4`

## 🛠️ Files in this folder

- `capex_dashboard.html` — the deployed HTML (34KB, self-contained, no deps)
- `capex_state.json` — current stage + target per item (live state)
- `capex_audit.log` — append-only change history
- `items.json` — flat item list (description, PIC, amount) for the bot
- `capex_bot.py` — Telegram command handler (CLI form)
- `deploy_capex.py` — copy state files to hub repo
- `_headers` (in hub_registry) — CDN no-cache rules for state.json

## 🔄 How updates flow

1. You send `capex move #N stage` to BotBot
2. Bot runs `capex_bot.py move N "stage"` — updates local state.json + audit.log
3. Bot calls `deploy_capex.py` → `build_index.py` → `copy_assets.py` → `wrangler pages deploy`
4. Cloudflare Pages rolls out new state.json (~10s)
5. Dashboard auto-polls every 30s and re-renders with new state

## 📊 Current state (auto-updated)

See live `capex_status` command or open the dashboard.

## 👥 Who can see what

- **Owner (sir / Nizmax)** — full edit via Telegram commands
- **All members** — read-only via dashboard URL; can filter, search, click details, export CSV
- **Public audit log** — anyone with the URL can see who moved what when (transparency)

— BotBot 🤖