Production Dashboard Real-Time Manufacturing: Excel vs MES vs Custom

Your operators log downtime in a spreadsheet. Your shift leads enter it into SAP the next morning. Your production manager pulls an OEE report on the 5th of the following month. By then, the machine that caused 340 minutes of unplanned stops three weeks ago has already caused another 280.

This is the reality at most mid-market manufacturers running 3-15 production lines. The question isn't whether you need a production dashboard with real-time manufacturing data. The question is which approach fits your plant, your team, and your budget.

Who Faces This Decision

This comparison is for manufacturers between 200 and 2000 employees running discrete or batch production. You're likely ISO 9001 certified, possibly ISO 13485 or IATF 16949. You have SAP ERP (or similar) for planning and finance. Your actual production floor runs on a mix of legacy MES, Excel trackers, WhatsApp groups, and paper.

You've probably been burned by at least one software implementation. Maybe a MES project that took 18 months and still doesn't do what the demo showed. Maybe a BI tool nobody uses because the data is always stale.

Your real requirement: see what's happening on the floor right now, not what happened last shift.

The Current State: How Information Actually Flows

Before comparing solutions, here's how data typically moves in a plant without real-time visibility:

flowchart LR
    subgraph Floor["Production Floor"]
        OP[Operator] -->|"paper form, ~5min"| LOG[Shift Log Excel]
        MC[Machine] -->|"no connection"| OP
    end
    
    subgraph Office["Planning Office"]
        LOG -->|"manual entry, next day"| SAP[SAP ERP]
        SAP -->|"month-end report"| MGR[Plant Manager]
    end
    
    subgraph Reality["Actual Decisions"]
        WA[WhatsApp Group] -->|"real-time but unstructured"| MGR
        OP -->|"direct message"| WA
    end
    
    style WA fill:#ffcccc
    style LOG fill:#ffffcc

The WhatsApp group is your actual real-time system. It's also unstructured, unsearchable, and invisible to anyone running reports.

Option 1: Excel with Manual Refresh

What it is: Shared Excel files (often on SharePoint) where operators or shift leads enter production data. Someone runs a pivot table weekly or monthly.

What it costs:

• License: €0-20/user/month (M365)
• Setup: 0-40 hours of internal time
• Maintenance: 2-5 hours/week for someone to clean data and run reports

Where it works:

• Single production line
• Fewer than 20 data entry points per shift
• No compliance requirement for electronic records (so, not FDA, not ISO 13485)
• Team already lives in Excel

Where it breaks:

• More than 2 shifts. Data entry delays stack. By the time you see Tuesday's numbers, it's Thursday.
• Cross-shift root cause analysis. Connecting a quality deviation to a specific parameter change three shifts ago takes hours of manual correlation.
• OEE accuracy. Manual downtime logging underreports by 15-30% in most plants we've audited. Operators round, forget, or log "planned" downtime that wasn't planned.
• Audit trail. Excel doesn't give you 21 CFR Part 11 compliance. It doesn't even give you reliable version history.

Who it's for: Plants under 150 people, single shift, or as a stopgap while evaluating other options.

For deeper analysis on why Excel breaks for OEE specifically, see our comparison on OEE tracking automation.

Option 2: Enterprise MES (MPDV, FORCAM, SAP ME)

What it is: Full Manufacturing Execution Systems designed for large-scale production environments. Typically includes OEE tracking, scheduling, quality management, and integration with ERP and PLCs.

What it costs:

• License: €50,000-500,000+ depending on modules and scale
• Implementation: 6-24 months
• Annual maintenance: 15-20% of license cost
• Internal resources: 0.5-2 FTE for ongoing administration

Where it works:

• Plants with 500+ employees or 20+ production lines
• Automotive Tier 1 suppliers under IATF 16949 pressure from OEMs
• Environments with deep PLC/SCADA integration requirements
• Organizations with dedicated IT/OT teams

Where it breaks:

• Mid-market plants (200-500 employees). The system is overbuilt for your scale. You pay for features you'll never configure.
• Implementation timeline. 12-18 months before you see value is common. Your problem is now.
• Flexibility. Changing a workflow often requires vendor involvement at €1,200+/day.
• ROI at mid-market scale. A €200,000 MES for a plant with €15M annual output needs to save significant labor or waste to pay back in 3 years.

Who it's for: Large manufacturers (1000+ employees), automotive OEMs and Tier 1s with compliance mandates from customers, or plants where full vertical integration (ERP-MES-PLC) is required.

Option 3: Standalone Dashboard Tools (Power BI, Grafana, Tableau)

What it is: Business intelligence tools connected to your existing data sources. Build dashboards that visualize production data.

What it costs:

• License: €10-70/user/month
• Setup: 40-200 hours depending on data source complexity
• Maintenance: 4-10 hours/month for report updates

Where it works:

• You already have structured data somewhere (MES, historian, database)
• You need visualization, not data capture
• Internal BI team with SQL skills
• Read-only dashboards for management

Where it breaks:

• Data capture. Power BI doesn't collect data. If your operators log to paper or Excel, Power BI just shows you stale Excel data faster.
• Real-time. Most BI tools refresh on a schedule (hourly, daily). True real-time requires additional infrastructure.
• Workflow automation. Dashboards show problems. They don't route them to the right person or track resolution.
• Mobile/floor use. These tools are built for desktop analysts, not operators on the floor.

Who it's for: Plants that already have a MES or historian generating clean data and need better visualization for management reporting.

Option 4: Custom Production Dashboard (TIMPIA or Similar)

What it is: A purpose-built system designed for your specific production environment. Connects to your existing systems (SAP, legacy MES, PLCs where available), fills data gaps with structured operator input, and delivers real-time dashboards accessible on floor terminals, tablets, or phones.

What it costs:

• Build: €30,000-80,000 depending on integration complexity
• Timeline: 6-12 weeks to first production use
• Annual operation: €12,000-24,000 including hosting and support
• Internal resources: 0.1-0.2 FTE for administration

Where it works:

• Mid-market plants (200-2000 employees) with 3-15 production lines
• Mixed environments with SAP, legacy equipment, and manual processes
• Teams that need both data capture and visualization
• Plants where shift handover is a known pain point
• ISO 9001/13485/IATF environments needing audit trails without enterprise MES cost

Where it breaks:

• Plants needing deep PLC integration across 50+ machines. Custom work can do this, but enterprise MES may be more cost-effective at that scale.
• Organizations requiring SAP-certified integrations for regulatory reasons
• Teams with no appetite for any change (even a 6-week implementation requires floor involvement)

Who it's for: Mid-market manufacturers who've outgrown Excel but can't justify enterprise MES cost or timeline.

The shift handover problem is a common entry point. For context on how different approaches handle this, see our analysis of manufacturing shift handover practices.

Comparison: What Real-Time Actually Means

"Real-time" means different things depending on your approach:

flowchart TB
    subgraph Excel["Excel Approach"]
        E1[Event occurs] -->|"operator logs later"| E2[Data in Excel]
        E2 -->|"someone runs report"| E3[Visible to Manager]
        E3 -.- ED["Delay: 4-48 hours"]
    end
    
    subgraph BI["BI Tool Approach"]
        B1[Data in source system] -->|"scheduled refresh"| B2[Dashboard updates]
        B2 -->|"manager checks"| B3[Visible]
        B3 -.- BD["Delay: 1-24 hours"]
    end
    
    subgraph Custom["Custom Dashboard"]
        C1[Operator logs via tablet] -->|"instant"| C2[Dashboard updates]
        C2 -->|"alert if threshold"| C3[Floor lead notified]
        C3 -.- CD["Delay: 0-5 minutes"]
    end
    
    subgraph MES["Enterprise MES"]
        M1[PLC sends signal] -->|"direct integration"| M2[MES processes]
        M2 -->|"rule triggers"| M3[Alert & escalation]
        M3 -.- MD["Delay: seconds"]
    end

The right "real-time" depends on what you're tracking:

• Machine micro-stops (under 5 minutes): Needs PLC integration. Enterprise MES or custom with OPC-UA.
• Downtime events (5+ minutes): Operator logging via tablet works. Delay of 1-5 minutes is acceptable.
• Quality deviations: Operator logging at inspection point. Custom or MES.
• OEE per shift: Calculated from above data. Any system can aggregate; the question is source data quality.

Decision Framework: Which Approach Fits You

Use these criteria based on your actual situation:

Stay with Excel if:

• You run 1-2 production lines
• Single shift operation
• No compliance requirements for electronic records
• You can live with weekly OEE updates
• Budget: under €10,000

Add a BI tool (Power BI, Grafana) if:

• You already have a MES or historian generating structured data
• Your problem is visualization, not data capture
• You have internal BI skills
• Budget: €5,000-30,000 for setup

Go custom if:

• You have 3-15 production lines
• Multiple shifts with handover problems
• Mixed data sources (SAP + Excel + manual)
• You need both data capture and real-time visibility
• ISO/IATF compliance but can't justify enterprise MES
• Budget: €30,000-80,000 build + €12,000-24,000/year
• Timeline need: 6-12 weeks, not 12-18 months

Go enterprise MES if:

• You have 20+ production lines
• Automotive Tier 1 with OEM pressure
• Deep PLC/SCADA integration is non-negotiable
• You have dedicated OT staff for ongoing administration
• Budget: €200,000+ and 12-18 month runway

The Math: What Real-Time Visibility Actually Saves

Here's a sample calculation for a plant running 3 lines, 2 shifts, with current OEE of 72%:

Current state (Excel-based tracking):

• Unplanned downtime discovered at month-end: ~40 hours/line/month
• Root cause analysis time per incident: 3-4 hours (cross-referencing shift logs, Excel files, WhatsApp)
• Quality deviations traced to parameter drift: average 11 days to identify

With production dashboard real-time manufacturing visibility:

• Downtime visible within 5 minutes of operator log
• Root cause pattern flagged same-shift (connects deviation to parameter change automatically)
• Estimated downtime reduction from faster response: 15-20% of unplanned downtime

Calculation:

• 40 hours unplanned downtime × 3 lines × 12 months = 1,440 hours/year
• 15% reduction = 216 hours recovered
• Value per production hour (contribution margin): €400-800 at most mid-market plants
• Annual value: €86,400-172,800

Against a custom build of €50,000 + €18,000/year operation, payback is 4-8 months.

This calculation excludes labor savings from reduced manual data entry and faster compliance reporting.

For IATF-certified plants, the traceability requirement alone often justifies the investment. See our breakdown on IATF 16949 traceability and Excel tracking.

What Happens After You Decide

Whichever path you choose, the implementation pattern matters:

Week 1-2: Map current data flow. Where does production data actually live today? Who enters it? What's trusted vs. known-bad?

Week 3-4: Define minimum viable dashboard. What 5 metrics must be visible in real-time to your shift leads? OEE? Downtime by category? First-pass yield? Quality hold status?

Week 5-8: Build or configure. Connect to SAP for order data. Set up operator entry points for floor data. Build the dashboard view.

Week 9-12: Floor pilot. One line, one shift. Get operator feedback. Fix what's broken before rollout.

This timeline applies to custom builds. Enterprise MES takes 3-4x longer. Excel "implementation" takes a weekend but delivers proportionally less.

Not Sure Which Path Fits?

The comparison above covers general patterns. Your plant has specific constraints: legacy equipment that can't be touched, an SAP landscape that took 3 years to stabilize, compliance requirements your auditor interprets differently than the next plant's auditor.

Book a 20-minute walkthrough and we'll map your current state to the option that fits. If that's not us, we'll tell you.