vault backup: 2026-02-20 14:53:32
This commit is contained in:
@@ -0,0 +1,43 @@
|
||||
# 2026-01-22 14:56:??
|
||||
|
||||
#topic/estimating
|
||||
|
||||
### Accurate Budget Vs. Accurate BOM
|
||||
|
||||
#### Quote
|
||||
|
||||
> [!quote] Joel Jansen [[2026-01-15#2026-01-15 13:27]] (pp.)
|
||||
> I'd rather have an accurate budget than an accurate BOM.
|
||||
|
||||
#### Context
|
||||
|
||||
#### Analysis
|
||||
|
||||
It may be counterintuitive to BOM-oriented estimators
|
||||
(typical of those with an electrical background),
|
||||
but deviating from organization standard practice
|
||||
to make an assembly "more accurate"
|
||||
(read: to make the estimate BOM
|
||||
more closely resemble the construction BOM),
|
||||
may make the budget _less_ accurate.
|
||||
|
||||
The review and adjustment process
|
||||
is based on standard practice,
|
||||
so deviations may have unpredictable effects.
|
||||
|
||||
Our assemblies do not include screws.
|
||||
It would be more accurate to the BOM to add them,
|
||||
but we budget for that cost in the summary,
|
||||
so to do so would be double dipping.
|
||||
|
||||
Though not stated as such,
|
||||
we budget for takeoff-to-install deviations the same way.
|
||||
|
||||
\
|
||||
|
||||
An organization's takeoff database
|
||||
ought to include exactly what is necessary for takeoff
|
||||
at the acceptable level of detail, and nothing else.
|
||||
It ought to be assumed by estimators that the previous is true,
|
||||
and that acceptable takeoff of any scope
|
||||
must be possible with the contents of the database.
|
||||
Reference in New Issue
Block a user