It’s the question you ask yourself every morning. The shift report lands on your desk, and the numbers are crisp and exact: 47,200 bottles filled yesterday. OEE at 84%. Three line stops, each under fifteen minutes. You know the throughput down to the digit. But then someone asks what it cost to make those bottles, and you’re back to square one.
You know your answer will involve a spreadsheet. Probably several spreadsheets. And it definitely won’t be ready by coffee time.
This is the central question that haunts manufacturing operations everywhere. Not because the answer doesn’t matter—it matters enormously. But because the answer is hidden inside a fragmented landscape of systems, each speaking a different language and operating on different timescales. Your historian knows production volumes. Your SCADA tracks efficiency metrics across every production area. Your ERP owns financial records. Your CMMS holds maintenance costs. Your sustainability team keeps their data in—you guessed it—spreadsheets.
Nobody owns the bridge between them.
The Data Divorce That Costs You Time
The cruelty of modern manufacturing is that you’ve invested heavily in the right infrastructure. You have historians capturing production data in real time. You have SCADA systems monitoring every aspect of your lines. You have financial systems that know your costs. And yet, the simple question—what did production cost yesterday?—requires you to manually stitch together information that lives in completely separate worlds.
Your historian records throughput in bottles per minute. Your ERP records syrup cost per litre on a monthly cycle. Your maintenance logs show unplanned downtime in hours. Your plan targets sit in a spreadsheet updated weekly. They’re all measuring real aspects of yesterday’s production, but none of them are in the same place, on the same timescale, or in a format that lets you do the accounting math you need.
So what actually happens? Someone—usually you—opens a spreadsheet. That person manually pulls the daily production volumes from the historian. They grab last month’s standard costs from the ERP (hoping they haven’t changed since Thursday). They cross-reference the OEE figure with maintenance records to allocate some portion of fixed costs. They multiply, divide, adjust, and pray they didn’t miss anything. Two hours later, they have an answer. By then, the shift is long over, the window for corrective action has closed, and the data is already a day old.
The Spreadsheet Treadmill
This is where most manufacturing operations live today. It’s not that companies are allergic to data. It’s that answering the cost question with the tools at hand means accepting a deeply unsatisfying reality: your production cost analysis is monthly at best, manual by necessity, and late by design.
The numbers get compiled during the cost period close. They’re reviewed and blessed by accounting. And by the time you have final actuals, the production decisions that drove those costs are weeks in the past. You’re learning from yesterday’s mistakes on a 30-day delay.
For decision-making, this cadence is almost useless. If you could see that yesterday’s production had a 12% higher cost per unit than the previous week, you might investigate why. Was it a material issue? Equipment drift? An unplanned change in the recipe? But by the time that 12% has made it through the cost accounting process, cycled through approval workflows, and landed on your desk, you’ve already run ten more production days that may be carrying the same underlying issue.
Real-Time Is For Alarms. Daily Is For Decisions.
Here’s what actually matters: you don’t need real-time production cost data. You need daily production cost data.
There’s an important difference. Real-time systems are expensive, fragile, and often answer the wrong question. They’re built for alarm conditions—shut down the line when something breaks, trigger a notification when a metric exceeds a threshold. Real-time is for “stop the pain right now.”
Daily cost accounting is different. It’s built on a simple cadence: yesterday’s production happened. Today, you want to know what it cost. A daily batch job is far more manageable than a continuous stream. Daily data can be reconciled against known good sources. Daily reporting aligns with how people actually run operations—they review yesterday’s numbers over coffee and decide what happens today.
When you can answer the cost question daily, the math changes. Yesterday’s production cost 3% more per unit than last week? You can investigate that today, while the information is fresh and the operators remember what they changed.
The Model: Inputs, Assumptions, Financial View
The trick to answering this question daily without a massive infrastructure project is understanding that production cost is built from three layers of data, each operating on a different timescale.
The first layer is daily production data. This is where your historians and SCADA systems excel. You have precise, second-by-second records of throughput, yield, downtime, and material consumption. This layer is highly variable and highly detailed, and it’s updated continuously.
The second layer is monthly cost assumptions. These come from your ERP. What does a litre of syrup cost this month? What’s your packaging cost per unit? What’s your labour rate? These numbers change less frequently—sometimes they’re fixed for the entire month—but they’re financial ground truth.
The third layer is weekly or longer-term plans and allocations. These might be your target throughput for a line, your planned maintenance windows, your expected overhead allocation method.
The magic is that you can layer these together. You take yesterday’s daily production (47,200 bottles), multiply it by last month’s standard costs (syrup, packaging, labour), and allocate fixed costs based on your plan assumptions. The formula is human-readable: [Cola Filler Throughput] × [Cola Syrup Cost/Litre] × ([Syrup Mix %] / 100). Any operator can understand it. No obscure macros. No hidden worksheets.
What Changes When You Know
When you shift from monthly spreadsheet exercises to daily cost visibility, the character of your operations changes in subtle but important ways.
Suddenly, you can see trends. Was productivity cheaper on Monday than Friday? Is there a pattern to when your cost per unit drifts up? Are you running material more efficiently on one line than another? These questions become answerable in time for them to matter.
You start to see the financial impact of operational decisions immediately. That unplanned shutdown yesterday? You can see exactly what it cost, in dollars, by 9 AM. The decision to run a faster production pace because you had a rush order? You can see whether it was worth it, cost-wise, the next day.
Most importantly, you shift from a reactive stance on cost—understanding your costs after they’ve happened—to a proactive one. Cost becomes something you can manage, not something you discover. And in manufacturing, that difference is enormous.
Making It Happen Without the Twelve-Month Project
There’s another approach: layer a cost accounting system on top of the infrastructure you already have. You don’t replace your historian, your SCADA system, or your ERP. You leave them exactly as they are. But you add an intelligent platform that sits above them, pulls data from each, applies the financial logic you need, and delivers daily cost answers.
A system built this way deploys in days, not months. It costs a fraction of the full platform replacement. It scales as your needs grow. And it stays out of the way—it doesn’t disrupt your existing workflows or force you to re-engineer your data pipelines.
The question isn’t whether you should know what yesterday’s production cost. The question is how long you’re willing to wait for the answer, and what you’re willing to build to get it.
NxGN Solutions builds intelligent, cloud-based platforms to help organisations see clearly, act faster, and scale with confidence. NxGN Capstone is our data management platform for integrated reporting. Learn more →