BOM costing: what a part really costs to make

What BOM costing is

BOM costing is the calculation of what a manufactured item costs to make by rolling cost up through its Bill of Materials and its Bill of Resources. It has two halves that mirror the two definitions of a manufacturable part: material cost comes from the BOM lines — what the part is made of — and process cost comes from the Bill of Resources and the route — what it takes to make it. Add them, apply overhead, and you have an estimated unit cost: the number that underpins every quotation, make-or-buy call and margin decision a plant makes.

For an Indian job shop or make-to-order plant, this is not a back-office nicety — it is the daily commercial decision. You cannot quote a make-to-order part honestly without knowing what it costs to make, and you cannot know that without costing the bill and the route. In Fast Production Software this is the BOM costing and cost-estimation report, drawing material from the BOM lines and process cost from the operation times.

Material cost: rolling up the bill

Material cost is built from the BOM, line by line and level by level. For each child line the calculation is quantity-per × child cost, adjusted for the scrap or yield allowance so the cost reflects what you actually have to buy, not the theoretical minimum. In a multi-level BOM the roll-up runs bottom-up: raw material costs roll into the sub-assembly that consumes them, and the sub-assembly cost rolls into the finished good. Each level therefore carries its own material cost, which is what lets a plant cost a semi-finished sub-assembly in its own right, not just the final product.

This is exactly why the scrap allowance and the make-or-buy flag matter so much: leave the scrap allowance out and material cost is understated on every quote; mis-flag a purchased part as manufactured and its cost is computed the wrong way. The roll-up is only as good as the bill feeding it.

Process cost: the Bill of Resources

The second half of the cost comes from the Bill of Resources (BOR) and the route. Each operation on the route has a standard time and runs on a work center with a cost rate, so the process cost of an operation is standard time × work-center rate. Sum that across every operation in the route and you have the process cost of the part. This is where the operation-time data earns its keep — in the reference deployment the operation-time table is the single largest transaction table, precisely because process cost and scheduling both draw on it.

Building the estimated unit cost

Put the two halves together and add overhead and you have the estimated unit cost — the standard, calculated before the job runs. This is the number a quotation is built on and the benchmark every job is later measured against. Because it is assembled from the released bill and route, it is reproducible: cost the same part today and next month and, unless the bill or route changed under control, you get the same figure. That reproducibility is what makes it a standard rather than a guess, and it is why costing sits on the released definition, not on a working draft.

Estimate vs actual: the variance

The estimate is only half the story. The other half is what the job actually cost, and the comparison between them is where a plant learns:

• Estimated cost — the standard from the released BOM and route, calculated before the job.
• Actual cost — the material actually issued to the work order net of returns, plus the process time actually taken.
• Variance — the gap, revealed by comparing actual consumption against the standard BOM quantity.

That consumption-versus-BOM variance is the single most useful number in production costing. A positive variance points to excess issue, unbooked scrap, or a standard that is simply wrong. Run it job after job and a plant either fixes the process — reducing the excess — or fixes the estimate, so future quotes reflect reality. Either way the loop closes between what was quoted and what was earned.

Why costing needs a released, accurate BOM

The cost roll-up is only as good as the bill it rolls up. If quantity-per is wrong, if the scrap allowance is missing, or if a component is flagged make when it is buy, the estimated cost is wrong — and every quotation built on it is wrong in the same direction. That is why costing sits on the released BOM and why changes to it go through an engineering change: a controlled, accurate bill is the precondition for a cost estimate you can quote against. A plant that lets BOMs drift as silent edits also lets its costs drift, and usually discovers it only when a run of jobs comes in under margin.

Feeding quotation and margin

The whole point of BOM costing is commercial. A job shop quoting a part needs its cost before it commits to a price; BOM costing supplies the material-plus-process estimate the quotation is built on. Then the later consumption-versus-BOM variance shows whether the job actually delivered the expected margin. Run repeatedly, this closes the loop between estimate and outcome — which is exactly the discipline that lets a plant price work profitably rather than staying busy at a loss. Layered on top, Dhruv AI can surface process-cost and reject patterns from the same data, so cost drift is spotted as a trend rather than a year-end surprise.

How Fast Production costs a BOM

Fast Production Software implements costing as real, exercised modules on the shared Fast Suite platform:

Because it runs on the shared platform, costing draws on the same BOM, route and material-issue data the floor already produces — the manufacturing core behind deployments such as Nikhtish Engineering and Solidus Hi-Tech. INR figures are indicative; confirm costing policy and any tax treatment with your CA.

Frequently asked questions