The manufacturing value tree
Value in manufacturing is decided twice: once when the price is agreed, and again on the line, where yield, downtime and changeovers quietly decide what that price was worth.
01 The same tree, this industry
Where the money is made and lost here
The structure does not change: value is profit plus how well that profit becomes cash, profit is revenue minus cost, and revenue is price times quantity. What changes is which drivers sit underneath each branch, and which system holds them. If you have not read the general version, start with the Enterprise Value Tree and come back.
The tree is symmetrical here in a way it is in almost no other sector: every branch has a commercial owner and an operational owner, and they use different systems to describe the same event. A tonne of product sold is a sales order in ERP and a batch in MES, and until those two records are the same object, the tree is two trees.
Every driver below names the metric it lands on. Follow one and you get its formula, the system the number lives in, and the ways it is commonly misread.
02 Price
What decides the price you actually get
Contract and index pricing
Long-term agreements with material indices attached, so realised price moves with a formula rather than a negotiation — and drifts from list without anyone deciding.
Price realisation net_revenue ÷ list_revenuePriceSpecification
What the customer actually needs versus what the drawing says. Over-specification is margin given away at the design stage and never revisited.
Average net price net_revenue ÷ unitsPriceFreight terms
Ex-works or delivered changes the realised price by several points and rarely appears in a pricing review at all.
Freight cost per unit total_freight_cost ÷ units_shippedPriceRebates and volume tiers
Annual tiers that pay out on volume you would have won anyway, accrued centrally and earned at customer level.
Contribution margin (net_revenue − variable_cost) ÷ net_revenuePriceSurcharges and pass-through
Energy, alloy and logistics surcharges: the mechanism that decides whether input inflation reaches the invoice or your margin.
Gross margin % (net_revenue − cogs) ÷ net_revenuePricePayment terms as price
Settlement discounts and extended terms are a price concession booked as a finance line, which is why nobody in commercial sees them.
Days sales outstanding (accounts_receivable ÷ net_revenue) × days_in_period03 Quantity
What decides how much you sell
Capacity available to sell
What you can actually offer before capex. The gap between nameplate and demonstrated rate is the cheapest capacity you will ever find.
Capacity utilisation actual_output ÷ practical_capacityVolumeLead time against competitors
In an outage, the supplier who can ship this week wins the order at almost any price.
Order cycle time delivery_date − order_date, in calendar daysVolumeApproved supplier status
Qualification cycles gate volume for years in automotive, aerospace and medical — a commercial asset held in a quality system.
Win rate opportunities_won ÷ opportunities_closedVolumeService level
OTIF is a growth driver, not a logistics metric. Customers allocate next year on last year's reliability.
On time in full orders_delivered_on_time_and_complete ÷ total_ordersVolumeAftermarket and spares
Higher margin, steadier volume, usually under-served because it sits outside the main order book.
Attach rate orders_containing_the_attached_item ÷ eligible_ordersVolumeMix and allocation of the constraint
Which product gets the constrained hour. This is a margin decision made hourly by people who see a schedule, not a P&L.
Contribution margin (net_revenue − variable_cost) ÷ net_revenue04 Cost
What it takes to operate
Material and yield
The largest line, moved by input prices and by material that never reached a customer.
Scrap and yield scrapped_quantity ÷ total_produced (yield is the inverse)CostConversion cost
Labour, energy and overhead per unit produced — where utilisation and losses show up in money rather than in percentages.
Overall equipment effectiveness availability × performance × qualityCostChangeover and start-up waste
The real cost of short runs, usually buried inside general scrap and invisible in the mix decision that caused it.
Schedule adherence units_produced_as_scheduled ÷ units_scheduledCostQuality failures
Rework, warranty and returns: paid twice, and rarely traced back to the line, shift or batch that produced them.
Returns rate units_returned ÷ units_soldCostMaintenance and downtime
Unplanned stops cost the contribution of everything not made, which is a much larger number than the repair.
Mean time to repair total_downtime_hours ÷ number_of_failuresCostEnergy per unit
A cost line and an emissions line from the same meter reading, if anyone joins it to output.
Energy per unit energy_consumed_kWh ÷ units_produced05 Cash
Where the cash actually sits
Inventory across three stages
Raw, work-in-progress and finished goods, each with a different owner and a different cause.
Days inventory outstanding (inventory_value ÷ cogs) × days_in_periodCashWork in progress specifically
The stage nobody owns. It grows with batch size and changeover avoidance, both of which look like efficiency.
Inventory turns cogs ÷ average_inventory_valueCashCustomer payment terms
Large OEM customers set the terms and the cash consequence lands on you, months after the commercial negotiation.
Days sales outstanding (accounts_receivable ÷ net_revenue) × days_in_periodCashSupplier terms
Balanced against security of supply for critical materials — the one lever that can be pulled too hard.
Days payables outstanding (accounts_payable ÷ cogs) × days_in_periodCashTooling and capex phasing
Cash out long before the first part is sold, and rarely modelled against the programme that justified it.
Capex intensity capital_expenditure ÷ net_revenueCashThe cycle as one number
Three owners, three metrics, and no one accountable for the total they add up to.
Cash conversion cycle dso + dio − dpo06 Where the numbers live
The systems behind the branches
A value tree is only usable once each box maps to a system and a record. These are the six that matter most in manufacturing: what each one is actually for, the records inside it the tree depends on, and which branch it feeds.
| System | What it holds | Key records | Feeds |
|---|---|---|---|
| ERP (SAP, Oracle, Dynamics) | The commercial and financial truth: orders, invoices, standard costs and stock valuation. | Material, BOM, Routing, Sales order, Invoice line, Cost centre | Price, cost, cash |
| MES / SCADA | What actually happened on the line, minute by minute — the only place downtime, speed loss and batch genealogy exist. | Work order, Asset, Downtime event, Batch, Quality result | Quantity, cost |
| PLM | The specification and its revisions: what the product is meant to be, and what it costs by design rather than by execution. | Part, Revision, Specification, Change order | Price, cost |
| QMS | Non-conformance, complaints and warranty claims — the cost of quality, held where finance never looks. | Non-conformance, CAPA, Complaint, Claim | Cost, price |
| WMS / TMS | Stock locations and outbound movement, which decide fill rate and the freight actually paid per unit against the freight quoted. | Stock item, Delivery, Shipment, Lane | Quantity, cost, cash |
| CMMS | Maintenance history and asset condition: the leading indicator behind availability, and the spares policy behind repair time. | Asset, Work request, Failure code, Spare part | Cost, quantity |
Almost every hard question in manufacturing needs two of these joined. That join — not the calculation — is the work.
07 Where it leaks
Value lost between two systems
These are the losses that no single system can see, because the evidence is split across two of them. Each one is a real number that stays invisible until the join exists — which is why the tree is an integration exercise before it is an analysis one.
| Where value leaks | Why it happens | The join that finds it |
|---|---|---|
| Scrap counted in units, lost in euros | MES counts rejected pieces; ERP holds the standard cost. Neither system multiplies them, so scrap is discussed as a percentage and never as a margin line. | Join MES batch to ERP material cost at the point of rejection |
| The constraint moved and no report noticed | Capacity is planned in the scheduling system and actually consumed on the line. When the bottleneck shifts, the plan keeps optimising yesterday's constraint. | Join demonstrated rate by work centre to the schedule that assumed it |
| Freight recovered by contract, spent by lane | Delivered pricing is agreed per customer; freight is incurred per lane. The two are reconciled annually, if at all, and always in aggregate. | Join TMS lane cost to the ERP invoice line it delivered |
| Warranty cost never reaches the line that caused it | Claims land in the quality system months after the batch was made, by which time the shift, the material lot and the setting that produced it are three joins away. | Join QMS claim to MES batch genealogy and material lot |
| Rebates accrued centrally, earned locally | The accrual is a finance estimate; the entitlement is a customer-level fact. Sales teams price without seeing the tier the volume will trigger. | Join the rebate agreement to customer-level invoiced volume, live |
08 Worked example
Where the margin actually went
Revenue rose 9.6% and gross margin fell a point. The tree splits it into parts that have different owners: price gave €1.9m, the volume push added €2.4m of revenue but only €0.86m of profit because it was won on discount, and a 2.9% scrap rate cost €960k. The volume consumed capacity that scrap then wasted — two numbers, from two systems, that never appear on the same report.
| Component | Effect | What sits behind it |
|---|---|---|
| Price | +€1.9m | Index pass-through, net of rebate accrual |
| Volume | +€0.86m | €2.4m revenue at a discounted contribution rate |
| Mix | −€0.4m | Constrained hours went to the lower-margin family |
| Scrap and yield | −€0.96m | 2.9% of material, valued at standard cost |
| Downtime | −€0.61m | Contribution of what the stopped hours would have made |
| Net | +€0.79m | A margin point lost while revenue grew |
Illustrative figures, shown to demonstrate the split. The point is the shape of the walk, not the numbers — on your own data the same bridge is built from your ledger.
09 Diagnostics
Six questions to ask in manufacturing
Ask them of your own team before anyone asks them of you. In most organisations at least two of these cannot be answered without a manual exercise, and those two are the plan.
- Can you value one hour of downtime on the constraint in contribution, not in units?
- When MES and ERP disagree on what was produced, which one does the P&L use — and is that a written rule or a monthly argument?
- Do you know the realised price by customer after rebate, surcharge and freight, or only the invoiced price?
- Which product consumed the constrained hours last month, and was that the mix you would have chosen with a margin view?
- Can you trace a warranty claim back to the batch, the shift and the material lot?
- Who owns work in progress? If the answer is "planning and operations", the answer is nobody.
10 The metrics behind it
Definitions for every box
11 Questions
Frequently asked
Which number should a plant manager and a CFO share?
Contribution margin per constrained hour. It converts factory decisions — run length, mix, maintenance windows — into the currency the CFO plans in, without either side having to learn the other's vocabulary.
Why do factory and finance numbers rarely agree?
Because MES counts what was produced and ERP counts what was confirmed, at different times and often at different levels. Neither is wrong; they answer different questions, and the reconciliation has to be a defined rule rather than a monthly argument.
Where should a manufacturer start if the estate is fragmented?
With one product family on one line, and the join between MES and ERP for that family only. It produces a defensible contribution-per-hour number in weeks, which funds the next domain far more reliably than an estate-wide programme.
Does this work for high-mix, low-volume production?
It matters more there. High mix means changeover and start-up waste dominate, and those are exactly the costs that hide inside a general scrap percentage until the tree separates them.
See this tree on your own data
Connect the systems above, define each box once, and the tree stops being a slide.