Unit cost is an input. Multi-year impact is the decision.
A product-cost model can be internally consistent while the resulting plan remains fragile. That happens when volumes, mix, ramp-up, sourcing and resource assumptions are not carried forward explicitly.
The planning question is larger than “What does one unit cost?” It is: What happens to margins, capacity, investment needs and cash as the business develops over several years?
- 01 / PRODUCT COSTING & EPCRetain the cost model.
Materials, routings, process quantities, rates and fixed / variable boundaries.
- 02 / OPERATIONAL DRIVERSApply volumes and resource logic.
Product and customer mix, ramps, machine and personnel hours, energy and capacity.
- 03 / MULTI-YEAR PLANNINGCalculate the financial path.
Cost changes, margins, investments, working capital, P&L and cash over time.
- 04 / CPM MANAGEMENT LAYERGovern the connected plan.
Consolidate assumptions and scenarios, approve versions and reconcile actuals.
Start with quantities before money
Carry the operational drivers alongside the monetary values. The relevant quantities depend on the manufacturing process; they should be owned and reviewed by the people who understand that process.
| Operational driver | Planning translation |
|---|---|
| Volumes & product mix | Revenue, material demand and manufacturing workload |
| Material quantities, yield & scrap | Purchased quantities and material cost by scenario |
| Machine hours | Capacity load, maintenance assumptions and investment triggers |
| Personnel hours | Staffing needs, labour cost and productivity assumptions |
| Electricity, steam & compressed air | Process-dependent resource demand and energy cost |
| Tooling & capacity thresholds | Capital expenditure timing, depreciation and cash outflows |
For example, required machine hours follow production volume and cycle time, adjusted for the relevant yield and efficiency assumptions. Converting those hours into cost requires a clearly defined rate and cost boundary.
Give changes a date and an owner
A multi-year model should distinguish the base case from the effects of changed assumptions.
- Volume ramps and mix: annual and, where needed, monthly changes by product or customer.
- Learning and cost-down: realistic timing, accountable owners and dependencies.
- Supplier prices: effective dates, commodity assumptions and contractual conditions.
- Engineering and sourcing changes: new specifications, sites, tooling and transition costs.
- Capacity: utilisation limits, additional equipment and staff requirements.
Separate a target from an evidenced assumption. A desired cost-down is not achieved merely because it appears in the plan.
Reconcile cost logic to P&L and cash
Distinguish variable consumption from fixed expenditure and allocated unit-cost rates. Otherwise, multiplying a fully absorbed unit cost by volume can misstate the total cost or double-count a fixed-cost block.
Fixed-cost dilution changes the cost per unit; it does not automatically change the underlying expenditure. Model the cost block and the capacity assumptions explicitly.
Investment creates a cash outflow on its payment schedule. Depreciation affects the P&L on a different timeline. Inventory, payment terms and receivables introduce further differences between profit and cash.
The practical limit of a spreadsheet plan
Gunnar’s industrial controlling background and experience with Excel-based planning shape this perspective. Spreadsheets offer flexibility, but maintaining a connected model becomes harder when calculation logic, versions and assumptions are distributed across many files.
Typical questions are practical: Which version was approved? Who changed the volume assumption? Does the investment plan reconcile to the capacity model? Has a cost-rate update reached every scenario?
A new planning system still needs a coherent model. Define the operational drivers, data ownership, aggregation and reconciliation rules before choosing the target-system configuration.
Where the CPM layer can take over
Product Costing provides detailed cost logic. Driver-based planning translates it across volumes, scenarios and time. Corporate Performance Management (CPM) systems can provide the management-planning layer in which the assumptions are consolidated and governed.
The boundary is a design question. Some costing platforms already cover multi-year calculations: Siemens documents lifetime-calculation versioning and period-level REST API access in Teamcenter Product Cost Management version 2512. A costing system need not stop at a static unit cost.
Corporate Planner is an example of a platform documented for operational planning. Lucanet documents integrated financial planning across P&L, balance sheet and liquidity. Their inclusion here is contextual and does not establish a standard connector to any costing tool.
A useful handover between the layers
- Define products, sites, currencies, units and time periods.
- Transfer quantities and rates with the cost result.
- Keep fixed and variable cost treatment explicit.
- Version volumes, mix, sourcing and technical assumptions together.
- Map tooling, capacity and investments to payment and depreciation schedules.
- Identify data owners and approved change rules.
- Reconcile a representative scenario back to the original cost model.
Three conversations worth having
With costing vendors: Which assumptions and resource quantities can leave the cost model, and at what granularity?
With consultancies: Where does a broader transformation or interim engagement need additional Product Costing, FACTON, Should Costing or cost-based planning depth?
With planning providers and practitioners: How should technical cost detail be aggregated, governed and reconciled in the management plan?
Sources & context
- SAP — calculation scenarios and lifecycle planning context Provider context; does not establish a cross-vendor connector.
- Corporate Planning — operational planning Supports the contextual Corporate Planner example.
- Lucanet — integrated financial planning Supports the contextual P&L, balance sheet and liquidity example.
- Siemens — multi-year calculations in version 2512 Release note dated 1 December 2025; provider-stated functionality.
- FACTON — Product Costing scope The cross-system handover model is this publication’s editorial synthesis.