Glossary (EDGEBIC)

What Is Actual Cost in Earned Value Reporting? EDGEBIC Definition

User Solutions TeamUser Solutions Team
|
6 min read

Actual cost is the effort a job has genuinely consumed up to the reporting cut-off date, and in EDGEBIC by User Solutions it is measured in hours before it is measured in money. It is the sum of the actual hours logged against every day of every operation on the job, with anything dated after the cut-off excluded. Where planned value states an intention and earned value states an accomplishment, actual cost states a bill.

This entry belongs to the EDGEBIC glossary series introduced on the platform overview; the broader index of planning vocabulary sits in the manufacturing glossary. Actual cost is the denominator of the cost performance index and the starting point of the estimate at completion.

How Actual Cost Works

The kitchen renovation analogy that explains budget at completion carries straight through here. Budget at completion is the fifty thousand you agreed before anyone lifted a hammer. Actual cost is the drawer of receipts. It grows on its own schedule, it does not care what stage the work has reached, and it is the only one of the three earned value numbers that comes from outside the plan.

That last point is what makes actual cost worth defining carefully. Budget and planned value are both read from the schedule, so they are as good as the routing. Actual cost is read from logged actuals, so it is as good as the discipline on the floor. When the two disagree, you are usually learning something about one of those two sources rather than about the job.

The arithmetic is simple. Every scheduled operation carries a per-day breakdown of planned hours and actual hours. Actual cost adds up the actual hours on every day dated on or before the cut-off, across every operation on the job. Days after the cut-off are ignored, which keeps the figure aligned with the planned value it will be compared against. Sub-assembly roll-up rows are excluded from the sum so a parent step's hours are not counted twice through a child routing.

Currency arrives second, and only if it can. EDGEBIC multiplies the hours by each work center's hourly rate to produce the actual cost in currency. If no work center on the job carries a rate above zero, the report hides the currency columns entirely instead of presenting a column of zeros. That behavior is deliberate honesty: a shop that has not configured rates should see hours, not a fabricated dollar figure. It also means the currency valuation is a labor valuation built from work center rates, not a fully burdened cost including overhead.

A Concrete Example

Job J-100 again, five steps, budgeted at 50 hours in total. Here is what was actually logged by the cut-off, which lands halfway through step S4.

StepWork centerPlanned hoursActual hours
S1 CutSaw-1810
S2 DrillMill-11211
S3 CNCCNC-12430
S4 DeburrFinish-144
S5 InspectQC-12not started

Actual cost = 10 + 11 + 30 + 4 = 55 hours. Step S5 has no logged hours, so it contributes nothing.

Percent complete is 55 divided by 50, which would be 110 percent, so the cap holds it at 100. Earned value is therefore the full 50 hours. Cost performance index is earned value divided by actual cost: 50 divided by 55 = 0.91. For every planned hour of work delivered, roughly 1.10 hours are being spent.

Estimate at completion then reads 55 hours against a 50 hour budget, forecasting a 5 hour overrun. The job is physically fine, every started step finished, and it is still 10 percent over on effort. That is a distinction only actual cost can draw.

How EDGEBIC Uses Actual Cost

Actual cost appears as the AC h column on the Earned Value report, with an optional AC $ column beside it when rates are configured. Three product behaviors are worth knowing:

  • It is fed by logged actuals, not by completion flags. A step marked complete with no hours behind it adds nothing to actual cost, which is one of the quickest ways a job's indices go strange. The habit that keeps the number honest is logging actual hours and pieces as work happens, whether from the planner grid or the kiosk.
  • It respects the cut-off. Hours dated after the report's To date are excluded, so actual cost and planned value are always measured over the same window.
  • It survives a reschedule. Rescheduling redraws the plan, which moves budget and planned value; the hours already logged are historical fact and are not recomputed.

For the underlying comparison of what a job was supposed to take against what it did take, at day and work center grain rather than job grain, the companion figure is planned versus actual hours. The report walkthrough in how to run the Earned Value report shows the whole column set in one place.

Actual cost is the effort genuinely consumed by a job up to the reporting cut-off date. EDGEBIC measures it in hours first, summing the actual hours logged on each day of each scheduled operation, and only converts to currency afterwards by multiplying those hours by each work center's rate. It answers 'what has this taken so far?', which is a different question from 'what have we finished?' and 'what should we have finished?'.

Because hours are the figure the shop floor actually records. Operators and planners log hours and pieces, not dollars, so hours are a captured fact while currency is a derived valuation. EDGEBIC keeps the hours column as the primary measure and shows currency columns beside it only when at least one work center on the job has an hourly rate greater than zero. With no rates configured the currency columns are hidden rather than shown as zeros.

Actual cost is what the job has consumed; earned value is what the job has produced, priced in the plan's own hours. Dividing earned value by actual cost gives the cost performance index, so a job with 50 hours of earned value and 55 hours of actual cost scores 0.91 and is spending about 10 percent more effort than the work it has completed is worth. The two are equal only on a job running exactly to its estimate.

Expert Q&A: Deep Dive

Q: My job shows 55 actual hours against a 50 hour budget but says 100 percent complete. Is the report broken?

A: No, that combination is by design. Percent complete is actual hours divided by budget, capped at 100, so a job that overruns cannot report more than fully done. Earned value is then budget multiplied by that capped percent, which pins it at 50 hours. Actual cost keeps climbing past the cap to 55, which is what makes the cost performance index fall to 0.91 and the estimate at completion land at 55 hours. The cap protects earned value from inflating on overrun, and actual cost is where the overrun stays visible.

Q: Actual cost looks too high on a job with parallel operations. What causes that?

A: Parallel work centers running the same operation each log their own hours, so a naive job-level total counts the same wall-clock work more than once. EDGEBIC has a site-wide primary hours only setting that excludes parallel sibling hours from job-grain figures, including the Earned Value report, so the job total reflects the primary chain. Per-work-center rows and the currency valuation stay at full effort on purpose, because every machine hour was genuinely consumed even when the job only earned one chain's worth.

Frequently Asked Questions

Ready to Transform Your Production Scheduling?

User Solutions has been helping manufacturers optimize their production schedules for over 35 years. One-time license, 5-day implementation.

User Solutions Team

User Solutions Team

Manufacturing Software Experts

User Solutions has been developing production planning and scheduling software for manufacturers since 1991. Our team combines 35+ years of manufacturing software expertise with deep industry knowledge to help factories optimize their operations.

Let's Solve Your Challenges Together