VP Manufacturing executive dashboard must show: (1) group OEE real-time + trend (12-month), (2) site ranking with inter-site comparison, (3) Six Big Losses Pareto (group-level + per-site drill-down), (4) capacity utilization vs plan, (5) improvement velocity tracker. Design: maximum 1 screen / 5 KPIs at VP level. Avoid vanity metrics — every KPI must trigger an action or escalation.
For VPs of Manufacturing managing 5-50+ production sites in 2027, the executive dashboard is the primary operational tool for: identifying underperforming sites, allocating improvement resources, tracking program effectiveness, and reporting to the COO/CEO/board. This guide details dashboard design principles, KPI selection, reporting cadence layers (real-time → shift → daily → weekly → monthly), inter-site comparison methodology, Six Big Losses Pareto analysis, BI integration patterns (Power BI, Tableau, Looker), and common dashboard anti-patterns to avoid. Designed as a complement to the COO 40-site scaling playbook — the VP dashboard is how you manage what the COO playbook deploys.
Dashboard design principles for manufacturing VPs
- One screen, five KPIs maximum: the VP dashboard is not a data exploration tool — it’s a decision-triggering tool. If you need to scroll or click tabs to find the important information, the dashboard has failed. Five KPIs maximum on the primary view.
- Every KPI triggers an action: if a KPI is green, no action needed. If amber/red, the VP knows exactly who to call and what to ask. “Interesting but not actionable” metrics don’t belong on the VP dashboard.
- Comparison is the unit of insight: a single number (e.g., “OEE 72%”) is meaningless without comparison: vs target, vs last period, vs peer sites, vs industry benchmark. Every KPI must have context.
- Trend over snapshot: a 12-month trend tells more than today’s number. Are we improving, stable, or declining? Trend direction matters more than absolute value for VP-level decisions.
- Drill-down available but not mandatory: the VP dashboard provides overview; clicking a site should reveal site-level detail. But the primary view must be self-sufficient for 80% of decisions.
The VP Manufacturing KPI suite: 5 primary metrics
KPI 1: Group OEE — real-time + 12-month trend
| Element | Specification |
|---|---|
| Metric | Weighted average OEE across all sites (weighted by production value or planned hours) |
| Display | Large number (current week) + sparkline (12-month trend) + delta vs same period last year |
| Target | Group target line (e.g., 78% group target 2027) |
| Color coding | Green ≥ target, Amber within 3 points below target, Red > 3 points below target |
| Refresh | Weekly consolidated (daily available on drill-down) |
| Action trigger | Red: escalation meeting with Regional Directors. Amber: investigation into contributing sites. |
KPI 2: Site ranking — inter-site comparison
| Element | Specification |
|---|---|
| Metric | OEE per site, ranked best-to-worst (or worst-to-best for action focus) |
| Display | Horizontal bar chart showing all sites, colored by region (EU blue, US green, Asia orange) |
| Context | Each bar shows: site name, current OEE, delta vs 3 months ago (improving/declining arrow), target gap |
| Comparison fairness | Normalize for product mix complexity where possible (OEE adjusted for changeover frequency) |
| Refresh | Weekly |
| Action trigger | Bottom 3 sites: mandatory improvement plan. Top 3 improvers: best practice sharing opportunity. |
KPI 3: Six Big Losses Pareto — group-level
| Element | Specification |
|---|---|
| Metric | Six Big Losses categorization aggregated across all sites, ranked by lost hours (or lost production value) |
| Display | Pareto chart — bar chart (losses by category) + cumulative line. Top 3 losses highlighted. |
| Categories | Equipment failure, Setup/adjustment, Idling/minor stops, Reduced speed, Process defects, Startup losses |
| Context | Each category shows: total lost hours this month, % of total losses, trend vs prior quarter |
| Refresh | Monthly (weekly available on drill-down) |
| Action trigger | Largest loss category: group-level improvement initiative assignment. If one loss >40% of total: systematic root cause investigation. |
KPI 4: Capacity utilization vs plan
| Element | Specification |
|---|---|
| Metric | Actual production output vs planned capacity (as % utilization), per site and group |
| Display | Heatmap: rows = sites, columns = weeks. Green (on-plan ±5%), Amber (5-15% gap), Red (>15% gap) |
| Context | Links OEE improvement to business outcome: are we producing what the customer/demand plan requires? |
| Refresh | Weekly |
| Action trigger | Red cells: production shortfall investigation (is it OEE? demand change? supply constraint?). Green cells with low OEE: hidden capacity opportunity (producing enough but inefficiently — OEE improvement = cost reduction not capacity gain). |
KPI 5: Improvement velocity tracker
| Element | Specification |
|---|---|
| Metric | OEE points gained per site per quarter (rolling 4-quarter view) |
| Display | Scatter plot: X = current OEE level, Y = improvement rate (points/quarter). Quadrants: high OEE + improving (maintain), high OEE + stagnant (push next level), low OEE + improving (support), low OEE + stagnant (intervene) |
| Context | Tracks the effectiveness of the OEE program itself — are sites sustaining improvement momentum? |
| Refresh | Monthly |
| Action trigger | Low OEE + stagnant quadrant: escalation + dedicated improvement team assignment. High OEE + improving: celebrate + share best practices. |
Reporting cadence layers
| Layer | Audience | Cadence | Content |
|---|---|---|---|
| Real-time andon | Operators + supervisors | Continuous | Machine state, current OEE, stop reason, cycle count vs target |
| Shift report | Supervisors + shift managers | End-of-shift (3× daily) | Shift OEE, top 3 losses, actions taken, handover notes |
| Daily plant report | Plant managers | Daily (morning meeting) | Yesterday OEE per line, top losses Pareto, comparison vs last week, improvement actions tracker |
| Weekly operations review | Regional Directors + VP Manufacturing | Weekly | 5 KPIs above, site ranking, escalations, improvement velocity |
| Monthly ExCom report | COO + CEO + CFO | Monthly | Group OEE trend, CapEx avoidance tracker, improvement program ROI, benchmark vs industry, strategic decisions |
| Quarterly board report | Board of Directors | Quarterly | Group operational excellence score (OEE as component), capacity vs demand trajectory, investment return on OEE program |
Download the case study
BI integration patterns
Power BI integration
- Data source: OEE platform REST API → Power BI DirectQuery or Import mode
- Architecture: OEE platform API → Power BI Gateway (on-premise) or Power BI service (cloud) → Power BI Dashboard
- Refresh: DirectQuery (real-time) for operational dashboards, Import (scheduled refresh hourly/daily) for executive dashboards
- Cross-domain analytics: Power BI combines OEE data + SAP/Oracle ERP data + CMMS maintenance data + quality SPC data → unified manufacturing intelligence
- Template: TeepTrak provides Power BI template (.pbit) with pre-built OEE dashboards matching the 5-KPI VP suite above
Tableau integration
- Data source: OEE platform REST API → Tableau Web Data Connector or Tableau Hyper extract
- Architecture: similar to Power BI — REST API → Tableau Server / Tableau Cloud → Dashboards
- Advantage: Tableau’s visual analytics superior for exploratory analysis; Power BI stronger for enterprise Microsoft stack integration
Looker / Google Looker Studio integration
- Data source: OEE platform REST API → BigQuery (GCP data lake) → Looker model
- Architecture: REST API → GCP Dataflow → BigQuery → Looker
- Best for: organizations on Google Cloud Platform stack
Inter-site comparison methodology: fairness framework
Inter-site OEE comparison must be fair — comparing a high-mix automotive Tier 1 stamping plant (200 changeovers/month) to a single-product food packaging line (2 changeovers/month) on raw OEE is misleading. Fairness adjustments:
- Product mix complexity index: number of changeovers per month normalized. High-mix sites get “complexity credit” in ranking.
- Equipment age weighting: older equipment with inherently lower performance vs new — sites with older fleet normalized vs newer.
- Industry sector grouping: compare automotive sites to automotive sites, food sites to food sites (for diversified groups like Hutchinson).
- Improvement trajectory over absolute level: rank sites by improvement velocity (points gained per quarter) not just absolute OEE. A site at 55% improving +4 points/quarter is performing better than a site at 80% declining -1 point/quarter.
- Operator experience composition: sites with 50% new hires vs stable workforce — experience composition affects OEE; normalize for training maturity.
Dashboard anti-patterns (what VPs should NOT do)
| Anti-pattern | Why it’s harmful | Better approach |
|---|---|---|
| 20+ KPIs on one screen | Decision paralysis, nobody reads it | 5 KPIs maximum, drill-down for detail |
| OEE without comparison context | “OEE 72%” means nothing in isolation | Always show: vs target, vs prior period, vs peer sites, vs industry |
| Daily VP dashboard review | VP micro-managing, plant managers feel surveilled | Weekly VP review; daily is plant manager’s responsibility |
| Naming and shaming lowest site | Creates blame culture, sites start gaming OEE definitions | Focus on improvement trajectory; celebrate improvers not punish laggards |
| Vanity metrics (cumulative OEE improving because you added good sites) | Misleading — group OEE increases by adding high-performing sites, not improving existing | Track same-site improvement (like-for-like) |
| Ignoring the “green zone” | Sites hitting target get no attention; they stagnate | Push high-performing sites to next level (80% → 85% → 90%) |
| Dashboard without action protocol | Pretty charts nobody acts on | Every color code triggers a defined action (green=maintain, amber=investigate, red=escalate) |
Template: VP weekly operations review agenda
- [5 min] Group OEE snapshot: KPI 1 review — current week vs target, trend direction, delta vs last year
- [10 min] Site ranking review: KPI 2 — bottom 3 sites: what’s happening, what actions planned? Top 3 improvers: what worked?
- [10 min] Losses analysis: KPI 3 — biggest loss category group-level, which sites contributing most, improvement actions in progress
- [5 min] Capacity vs plan: KPI 4 — any red cells (production shortfalls)? Root cause: OEE or demand or supply?
- [5 min] Improvement velocity: KPI 5 — any sites stagnating? Resources needed? Cross-site best practice sharing scheduled?
- [10 min] Actions & escalations: decisions made, actions assigned with owners + deadlines, items for COO escalation
Total: 45 minutes weekly. Disciplined. Data-driven. Action-oriented.
FAQ: VP Manufacturing dashboard
How many KPIs should the VP dashboard show?
Maximum 5 primary KPIs on the main view. Each must trigger an action (green=maintain, amber=investigate, red=escalate). More KPIs = decision paralysis. Recommended 5: Group OEE trend, Site ranking, Six Big Losses Pareto, Capacity vs plan, Improvement velocity. Drill-down available for detail but primary view must be self-sufficient for 80% of VP decisions.
Real-time or periodic dashboard for VP level?
Weekly consolidated for VP level. Real-time is for operators and supervisors. Daily is for plant managers. Weekly is for VP/Regional Directors. Monthly for COO/CEO/board. VP reviewing real-time OEE = micro-management signal that undermines plant manager authority. Exception: during crisis (major breakdown, quality event) VP may access real-time temporarily.
How to compare sites fairly?
Fairness adjustments: (1) product mix complexity index (changeover frequency normalized), (2) equipment age weighting, (3) industry sector grouping (compare automotive to automotive), (4) improvement trajectory over absolute level, (5) operator experience composition. Compare like-for-like. Rank by improvement velocity (points gained/quarter) not just absolute OEE. Celebrate improvers, don’t name-and-shame laggards.
Power BI or Tableau for manufacturing OEE?
Power BI: best for Microsoft stack organizations (Azure, Dynamics 365, Microsoft 365). DirectQuery for real-time, Import for scheduled refresh. Power BI Gateway for on-premise OPC UA data. Tableau: superior visual analytics for exploratory analysis. Best for organizations already on Tableau Server/Cloud. Looker: best for Google Cloud Platform. All integrate via OEE platform REST API. TeepTrak provides Power BI template (.pbit) pre-built.
What is Six Big Losses Pareto analysis?
Six Big Losses (from TPM methodology): Equipment failure, Setup/adjustment, Idling/minor stops, Reduced speed, Process defects, Startup losses. Pareto analysis ranks these by impact (lost hours or lost production value), showing which loss category deserves most attention. Group-level Pareto reveals systematic patterns across sites. If one loss >40% of total losses: systematic root cause investigation. Drill-down to per-site Pareto reveals site-specific issues.
How should the VP use the improvement velocity tracker?
Scatter plot: X = current OEE, Y = improvement rate (points/quarter). Four quadrants: (1) High OEE + improving: celebrate, share best practices, (2) High OEE + stagnant: push to next level (80→85→90), (3) Low OEE + improving: support with resources, patience, (4) Low OEE + stagnant: escalate, dedicated improvement team, root cause investigation. Sites should move right (higher OEE) and up (faster improvement) over time.
What does Hutchinson’s VP dashboard look like?
Hutchinson 40-site deployment: VP Operations dashboard shows group OEE trend (42% starting → 75% achieved), site ranking across 40 sites colored by geography, Six Big Losses Pareto group-level, capacity recovery tracker (how much new production capacity recovered from OEE improvement vs new line CapEx avoided), and improvement velocity per wave deployment cohort. Demonstrates the 5-KPI framework at enterprise scale.
What BI integration does TeepTrak support?
TeepTrak Pulse provides: REST API (HTTPS + JSON) for Power BI DirectQuery/Import, Tableau Web Data Connector, Looker via BigQuery, and any BI tool supporting REST API. Pre-built Power BI template (.pbit) with 5-KPI VP suite. OData feed option for SAP Analytics Cloud. CSV export for ad-hoc analysis. Webhook support for real-time event-driven integration.
How to avoid dashboard becoming shelfware?
Three rules: (1) every KPI has defined action protocol (green/amber/red → maintain/investigate/escalate), (2) weekly 45-minute operations review using the dashboard as meeting structure (not separate from meeting), (3) VP visibly uses dashboard in conversations with plant managers (creates pull demand for data quality). If VP doesn’t reference dashboard in weekly review, plant managers stop maintaining data quality within 2-3 months.
Should the dashboard show financial impact?
Yes for monthly/quarterly COO reports. Link OEE improvement to: capacity recovery value (€/quarter), CapEx avoidance (lines not built), quality cost savings, overtime reduction. VP weekly dashboard focuses on operational metrics; monthly report adds financial translation. CFO ROI calculator (companion article) provides methodology for financial impact quantification.
What about mobile dashboard for VP on-the-go?
Mobile dashboard: 3 KPIs maximum (Group OEE, worst-performing site, biggest loss category). Push notifications for red alerts only. VP should not be checking mobile OEE dashboard constantly — that’s micro-management. Mobile useful for: plant visits (pull up site dashboard while on shopfloor), travel days (quick group status check), crisis response (real-time access during major event).
Conclusion
VP Manufacturing executive dashboard design 2027 follows 5 principles (one screen, every KPI triggers action, comparison is insight, trend over snapshot, drill-down available) and 5 primary KPIs (Group OEE trend, Site ranking, Six Big Losses Pareto, Capacity vs plan, Improvement velocity). Weekly 45-minute operations review using dashboard as meeting structure ensures actionability. BI integration via Power BI (Microsoft stack), Tableau (visual analytics), or Looker (GCP) using OEE platform REST API. Inter-site comparison fairness requires product mix normalization, sector grouping, and emphasis on improvement trajectory over absolute level. Dashboard anti-patterns to avoid: too many KPIs, naming-and-shaming, daily VP review (micro-management), vanity metrics. TeepTrak Pulse provides Power BI template (.pbit) + REST API + multi-site standardized methodology supporting the full VP KPI suite at Hutchinson 40-site scale.
Next step: download the TeepTrak VP dashboard design guide or request a free executive dashboard prototype for your manufacturing group.
0 Comments