Manufacturing dashboard: output, late orders, and cost

Your daily review shows output up, yet late orders are still climbing. A manufacturing dashboard needs to connect what the plant released to the customer orders that needed it, using the same dates and product identities. Add production cost on an agreed basis so you can see whether the extra output served the required orders and what it cost.

Start with ERP sales orders, posted production and inventory records, and finance cost records. The dashboard supports daily or hourly management review. Each figure needs a declared calculation and source cutoff; a production count alone cannot establish that due orders were completed or that the resulting stock was available to ship.

Keep order lines, production postings, and costs at their own grain

A sales order line records a customer commitment, while a production posting records completed output. One batch may serve several orders, and one order may require several batches. Preserve those identities before grouping records by company, site, product, and reporting date. Joining every order line to every batch for the same SKU would repeat both quantities.

Aggregate each input separately before combining the dashboard totals. Keep the company-scoped order and line IDs, production posting IDs, and cost references available for inspection. Product aliases need an approved mapping, and cases need a dated conversion before they can be added to units. Expose unmapped rows beside the reported scope so missing records cannot disappear into a plausible total.

For delivery performance, freeze the commitment date used for the review. If the planner moves yesterday's due date to next week, preserve both the original and revised dates with the approval record. Decide whether performance is measured against the requested date or an accepted customer commitment; switching between them changes the denominator without changing execution.

Compare output with the orders due on the same day

This synthetic example covers September 28 and 29, 2026, for SKU FG-100 at North and South sites. All quantities use individual units, labeled EA. Each daily cutoff is 23:59:59 America/Chicago, and all source exports complete at 06:00 the following day. These are teaching values, not customer results.

Planned released units come from the dated, approved production plan. Posted released units include completed units whose release status was effective by the cutoff. Due lines are eligible customer order lines with a frozen commitment date on that day; on-time complete lines are those whose full ordered quantity shipped by that deadline. Late open lines are still incomplete after their commitment date, counted once per site at the snapshot.

September 28 released output is 180 + 90 = 270 units against a plan of 200 + 100 = 300, so plan attainment is 270 / 300 = 90%. On-time line completion is (8 + 4) / (10 + 5) = 80%. Late open lines total 3 + 2 = 5 at that day's cutoff.

September 29 released output reaches 240 + 120 = 360 units against a plan of 220 + 120 = 340, giving 105.88% attainment. On-time line completion falls to (7 + 3) / (10 + 5) = 66.67%, and late open lines rise to 5 + 4 = 9. Output increased by 90 units, but the delivery measures worsened. Inspect the order-to-stock allocation and shipment evidence before deciding whether the extra production addressed the overdue work.

Download the synthetic manufacturing dashboard data for the same inputs and source references. Keep the dates, units, and cost basis attached when replacing the rows with your own data. A sample calculation is reproducible only when its denominator and reporting scope survive the replacement.

Calculate cost and cross-site rates from their inputs

Assigned manufacturing cost in the example contains posted material and labor costs allocated to the completed, released batches under an illustrative finance-approved policy. It excludes costs assigned to unfinished work, and it is not an inventory valuation or financial statement measure. Preserve the allocation basis and batch links so a cost transfer can be distinguished from a change in production performance.

September 28 cost per released unit is ($3,600 + $2,250) / (180 + 90) = $21.67 after rounding. September 29 is ($4,800 + $3,000) / (240 + 120) = $21.67. North costs $20 per unit and South $25 on both days; their unweighted average of $22.50 would misstate the combined result because the sites produce different volumes.

Use the same method for on-time performance: add the completed lines and due lines, then divide. On September 29, averaging North's 70% and South's 60% gives 65%, while the combined rate is 10 / 15 = 66.67%. Label this a line-based measure, since a small order line and a large one each count once. If you also need unit-weighted delivery performance, publish its separate numerator and denominator.

Late open lines are a snapshot (the same overdue line can remain open on both dates). Adding 5 and 9 would count backlog exposure across days, not identify 14 distinct late lines. Across products, aggregate unit quantities only where the unit represents comparable output; otherwise, show product-level rates or use an approved common basis with its conversion visible.

Turn a changed metric into a bounded investigation

Start the September 29 review with the nine late open lines. Identify which are short of released stock, which have stock reserved elsewhere, and which lack a completed shipment despite sufficient eligible supply. Hold status and reservation rules decide what can cover an order. The separate inventory reconciliation workflow addresses disagreements between inventory records before those balances enter the dashboard.

Record the responsible owner and source reference for each exception rather than assigning a cause from the KPI tile. A production posting can explain that units were completed; a shipment record can explain when the order left. A missing shipment record needs investigation and a coverage warning before it becomes evidence of nonperformance.

Carry sustained delivery or supply constraints into the SIOP manufacturing review. That review compares future demand, materials, and capacity assumptions. Keep the dashboard's observed execution separate from the planning scenario, so an imported forecast cannot overwrite the record of what happened.

How Permute builds recurring manufacturing dashboards

Permute sells connected data and custom reporting software for businesses with fragmented operating and financial records. We combine supplied production exports with ERP and finance sources, retain their references, and apply approved product and site mappings. An unresolved identity or conflicting status remains visible for review instead of becoming an unexplained adjustment.

We encode the agreed due-date basis, release rules, and cost calculation in reusable reporting logic. An operations lead can inspect the orders behind a late-line count, while a finance lead can inspect the postings and allocations behind unit cost. Refreshing the view reapplies those definitions to the available records, with access controlled by the underlying permissions.

Our manufacturing work starts with a bounded reporting problem across disconnected inputs. The scope should name the source coverage, reporting cadence, and owners who approve the definitions. Source availability and customer configuration determine which records the dashboard can use.

Keep planning, accounting, and plant controls with their owners

This workflow reads manufacturing inputs for management reporting. It does not release stock, reschedule production, approve cost allocations, or write changes back to an ERP. We are not a forecasting engine or a scheduling optimizer; planners supply approved plans, finance owns the costing policy, and authorized operational owners make changes in the systems that control the work.

Daily or hourly source refresh supports planning and cost review. It does not supply machine telemetry, second-by-second monitoring, or real-time overall equipment effectiveness (OEE). Display both the latest source timestamp and the business cutoff, and flag incomplete feeds before comparing sites. A newly refreshed page can still contain yesterday's records.

A manufacturing dashboard explains the daily review when output, customer commitments, and cost share a reproducible reporting basis. The worked example shows higher output alongside worse delivery performance, with the order evidence needed to investigate the gap. Cross-site totals use summed inputs, while overdue snapshots retain their dates. You can then review the late orders without treating an improved production total as proof that customer commitments were met.

Questions about manufacturing dashboards