Quick Answer
A mature ERP does two jobs at once: it tells you what's happening right now (through KPIs, SOPs, dashboards, and reports) and what things should cost or will need next (through estimated, standard, and actual costing, plus prediction across human, physical, financial, and property resources). These aren't separate systems bolted together, they're one connected chain where operational data feeds costing, and costing feeds resource forecasting.
KPIs, SOPs, Dashboards, and Reports: The Operating Layer
This is the part of ERP most people think of first, the day-to-day visibility layer.
- KPIs turn raw activity into a small number of numbers people actually watch, defect rate, on-time delivery, cash conversion cycle, utilization rate. The discipline is picking a handful that matter and giving each one a formula, a target, and an owner, rather than tracking everything and acting on nothing.
- SOPs, when digitized inside the ERP rather than kept as separate documents, generate the data that feeds those KPIs directly. A digital SOP step that captures a real measurement (a weight, a pass/fail check, a completion time) is also a data point for a KPI, with no manual re-entry.
- Dashboards translate that data by role: a supervisor needs real-time alerts and shift comparisons, a department head needs trend and variance against plan, an executive needs plant- or company-level aggregation tied to financial impact.
- Reports are the recurring, structured output of all of this, daily operational summaries, weekly or monthly compliance and quality reports, and monthly financial rollups, ideally drawing from the same underlying data so the numbers never contradict each other across departments.
We've covered this operating layer in more depth in our guide to connecting ISO compliance, KPIs, SOPs, and dashboards, and the report structure itself in Manufacturing Reports That Matter.
Estimated, Standard, and Actual Costing: Three Different Questions
These three costing approaches aren't competing methods, they answer three different questions, and a well-configured ERP uses all three at different points in the business cycle.
Estimated cost answers: what will this probably cost, before we've committed to anything? It's used at the quotation stage, before a purchase order or manufacturing order exists, built up from expected raw material prices, expected labor time, and an assumed overhead allocation. We covered how this works (and where Openbravo and Odoo differ) in Estimated Quotation: Raw Materials, Overhead, Safety Margin and Currency.
Standard cost answers: what should this cost, under normal conditions? It's a predetermined, fixed cost assigned to each material, labor operation, and overhead element, set periodically (often annually) and used to value inventory and production consistently. The ERP values everything at this standard rather than at the real, fluctuating cost of each transaction.
Actual cost answers: what did this actually cost, this time? It's the real price paid for materials and the real labor and overhead incurred on a specific job or production run, which naturally fluctuates run to run.
The value comes from comparing them: variance analysis is the structured process of comparing standard costs against actual costs and breaking the difference down into causes, material price variance, usage variance, labor rate variance, overhead spending variance. A favorable variance means actual cost came in below standard; an unfavorable one means it ran over. Most manufacturers run standard costing for day-to-day control and pricing stability, then reconcile to actual cost periodically, monthly or per production run, to see where reality diverged from plan and why. In ERP terms: a purchase price variance shows up when procurement pays more or less than the standard material cost, and a production order generates usage and efficiency variances as actual consumption deviates from the standard routing.
Odoo, for example, lets each product category be configured for standard, average (AVCO), or FIFO costing, so a business can run standard costing for manufactured goods that need variance control while using average or FIFO costing for simpler purchased/resale items, in the same system.
Predicting Resource Needs: Four Categories, One Discipline
Costing tells you what things cost. Resource prediction tells you what you'll need, and when, before you're short. The discipline is the same across all four resource types: use historical and current data inside the ERP to forecast forward, rather than reacting after a shortage or surplus already happened.
Human resources: headcount and skills forecasting based on production plans or sales pipeline, so hiring or training starts before a shortage hits the shop floor. Attendance and leave patterns feed shift-coverage prediction, and overtime trend data flags departments heading toward burnout or budget overrun before it's a crisis.
Physical resources: equipment capacity planning based on order backlog and machine utilization data, so a bottleneck is visible weeks out, not discovered when a delivery date slips. Preventive maintenance scheduling, tied to actual usage hours rather than a fixed calendar, predicts when a machine needs service before it fails mid-run.
Financial resources: cash flow forecasting built from confirmed sales orders, purchase commitments, and payment terms already in the system, not a separate spreadsheet model disconnected from actual transactions. Working capital and inventory investment forecasts follow the same logic, projecting forward from real demand and lead-time data.
Property resources: space and facility utilization tracked against growth plans, warehouse or floor capacity against inventory and production growth trends, and lease or facility cost forecasting tied to the same headcount and production plans driving the other three categories.
The reason to treat these four together, rather than as separate planning exercises, is that they're not independent. A sales forecast drives a materials plan (physical), which drives a labor plan (human), which drives a cash flow plan (financial), which eventually drives a facility decision (property). An ERP that holds all of this in one connected data model can actually chain that logic together; four disconnected spreadsheets can't.
How It All Connects
- Estimated costing sets the price at quotation, before commitment
- Standard costing sets the benchmark for control once production is planned
- Actual costing and variance analysis show what really happened and why
- KPIs, SOPs, and dashboards surface that reality to the right person in real time
- Resource prediction, across people, equipment, cash, and space, uses that same operational history to forecast what's needed next, closing the loop back to planning
Frequently Asked Questions
What's the difference between estimated cost and standard cost?
Estimated cost is a one-off forecast built for a specific quotation before any commitment exists. Standard cost is a fixed, predetermined benchmark set periodically and applied consistently across all production, used for ongoing control and variance analysis rather than a single quote.
Why would a business use standard costing instead of just tracking actual costs?
Standard costing gives stable, comparable unit costs for pricing and budgeting, and it surfaces problems as variances rather than burying them in fluctuating actuals. Actual costing is more precise but lags and varies with every price and usage change, so most manufacturers use standard costing for control and reconcile to actual periodically.
Can one ERP handle different costing methods for different products?
Yes. Platforms like Odoo let costing method (standard, average/AVCO, or FIFO) be set per product category, so a manufacturer can apply standard costing where variance control matters and simpler valuation methods elsewhere in the same system.
Why treat human, physical, financial, and property resource planning together instead of separately?
Because they're causally linked, a sales or production forecast drives material needs, which drives labor needs, which drives cash requirements, which eventually drives facility decisions. Planning them in one connected ERP data model lets that chain of cause and effect actually be modeled, rather than reconciled by hand across separate spreadsheets.
Want your KPIs, SOPs, dashboards, and costing method connected to real resource forecasting instead of four disconnected spreadsheets? Contact RAWN Technologies to scope an implementation.
Part of the Complete Guide to ERP Comparisons, Manufacturing Performance Systems & Data Roles.