Configure an ERP Production Efficiency Dashboard in Six Steps

Why real-time efficiency tracking matters

A plant that waits for end-of-shift reports loses hours of output every day. When supervisors rely on whiteboards or spreadsheets, small delays compound into missed deliveries and higher costs. An ERP production efficiency dashboard pulls live data from machines, operators and orders, so managers see problems as they happen and can act before the shift ends.

Map the data points first

Before configuring any dashboard, list the signals the plant already collects. Most factories log:

• Machine start and stop times from PLCs or manual entries.
• Good pieces and rejects per batch from in-process QC stations.
• Operator log-ons and shift handovers from time-clocks or tablets.
• Order quantities and due dates from the production module.
• Material movements from inventory transactions.

In Facteno, these signals feed a single ledger; no duplicate entry is needed. If the plant uses separate MES or weighbridge software, check that it exports CSV or JSON files that the ERP can ingest hourly or on demand.

Set up the three core metrics

An ERP production efficiency dashboard typically tracks Overall Equipment Effectiveness (OEE), cycle time and bottlenecks. Configure each metric in turn.

Overall Equipment Effectiveness (OEE)

OEE combines availability, performance and quality into one percentage. The formula is:

OEE = Availability × Performance × Quality

Availability = Run time ÷ Planned production time
Performance = (Ideal cycle time × Total pieces) ÷ Run time
Quality = Good pieces ÷ Total pieces

Illustration: A dyeing machine planned to run 8 hours (480 minutes) has 30 minutes of breakdowns and 20 minutes of setup. Run time is 430 minutes. It produces 120 pieces; ideal cycle time is 3 minutes per piece. Total pieces = 120, good pieces = 114.

Availability = 430 ÷ 480 = 0.896 (89.6%)
Performance = (3 × 120) ÷ 430 = 0.837 (83.7%)
Quality = 114 ÷ 120 = 0.95 (95%)
OEE = 0.896 × 0.837 × 0.95 = 0.713 (71.3%)

Cycle time

Cycle time is the average time from start to finish for one unit. In Facteno, the dashboard tile shows the rolling 60-minute average, updated every 5 minutes. If the tile turns red, the current cycle is 10% above the standard; the supervisor can drill down to see which machine or operator is causing the delay.

Bottlenecks

Bottlenecks appear when a work centre’s queue exceeds a set threshold. The dashboard uses a simple table:

Thresholds are set per work centre and shift; night shifts often tolerate longer queues because fewer supervisors are on duty.

Choose the right dashboard layout

A single screen should show the three core metrics plus supporting tiles. Facteno offers three layouts:

• The shift supervisor layout shows OEE, cycle time and bottlenecks in large tiles, with a live feed of machine status below.
• The plant manager layout adds a 24-hour trend line and a comparison against the weekly target.
• The finance layout replaces the live feed with cost-per-piece and material yield tiles, linked to the product costing module.

Pick one layout per role; avoid mixing roles on the same screen. If the plant has multiple lines, create a separate dashboard for each line and a summary dashboard that rolls them up.

Set thresholds and alerts

Thresholds turn raw numbers into action. For OEE, most textile plants set:

• Green: 85% and above.
• Amber: 70–84%.
• Red: below 70%.

For cycle time, the threshold is usually 10% above standard. Bottleneck thresholds are set per work centre; dyeing might tolerate 90 minutes, while stitching tolerates only 30 minutes because space is limited.

Alerts can be sent as:

• On-screen pop-ups for the supervisor.
• SMS or email to the production manager.
• Automatic work orders for maintenance if a machine’s OEE drops three times in one shift.

In Facteno, alerts are configured in the Business Control Centre, where the plant decides which roles receive which alerts and at what thresholds.

Test with one shift before rolling out

Run the dashboard for one shift on one line. Compare the numbers against manual logs:

• If OEE differs by more than 2%, check the machine logs for missing start or stop events.
• If cycle time is consistently higher, verify the standard time in the routing.
• If bottlenecks appear in the wrong place, adjust the queue threshold or the work-centre definition.

Once the numbers match, train the shift supervisors. Facteno provides a 15-minute video walkthrough and a one-page quick-reference card. After training, run the dashboard for a full week; the numbers should stabilise within 3% of the manual logs.

Interpret trends, not just snapshots

A single red tile is a symptom; a trend is a problem. The dashboard should show:

• A 24-hour OEE line chart, so managers see if the drop is sudden or gradual.
• A shift-by-shift comparison, to spot patterns (e.g., night shifts always dip).
• A defect Pareto, linked to the quality module, so managers know if the problem is machine, material or operator.

If OEE drops steadily over a week, the cause is usually maintenance or material quality. If it drops suddenly, the cause is usually operator error or a machine fault. The dashboard does not diagnose the cause; it shows where to look.

What to do next week

Start small:

1. Pick one line and one shift. Map the data points and configure the three core metrics in the ERP.
2. Run the dashboard for one shift; compare the numbers against manual logs.
3. Adjust thresholds and alerts based on what the shift supervisor needs.
4. Train the supervisor and run the dashboard for a full week.
5. If the numbers are stable, roll out to the next line or shift.

Do not try to cover the whole plant at once. A dashboard that works for one line can be copied to others; the thresholds and alerts will need tuning for each new line.

If the plant does not yet log machine start and stop times, start with manual entries on tablets. Once the habit is established, add PLC integration. The dashboard is only as good as the data it receives.