vault backup: 2026-06-01 17:13:50
This commit is contained in:
@@ -10,7 +10,7 @@ daily: "[[2025-12-03]]"
|
||||
## Excluding Vs. Ignoring Project Requirements
|
||||
|
||||
%%
|
||||
A criticism of an observed lack of [[transparency]] in [[construction-estimating]].
|
||||
A criticism of an observed lack of [[transparency-in-construction-estimating]].
|
||||
%%
|
||||
|
||||
There is a distinct difference between _excluding_ and _ignoring_ requirements.
|
||||
|
||||
@@ -30,7 +30,7 @@ The probability that any construction will be performed
|
||||
according the drawings that we take off
|
||||
(or even their immediate successors)
|
||||
I suspect is slim to zero.
|
||||
That Ops would have the patience to add the revisions,
|
||||
That [[pdi-operations|Ops]] would have the patience to add the revisions,
|
||||
fighting with Trimble Connect as they would be,
|
||||
I suspect is even less.
|
||||
|
||||
|
||||
@@ -63,5 +63,5 @@ to ask for a revision to a WBS
|
||||
|
||||
Bid receives bonuses based on _awarded GP_ ([[markup-vs-margin|margin]]),
|
||||
thus they are incentivized to underestimate cost.
|
||||
Ops receives bonuses based on _positive GP variance_,
|
||||
[[pdi-operations|Ops]] receives bonuses based on _positive GP variance_,
|
||||
thus they are incentivized to overestimate cost.
|
||||
|
||||
@@ -44,7 +44,7 @@ Carried labor for lost time due to badging
|
||||
|
||||
### Free Notes
|
||||
|
||||
Ops creates, approves the labor plan.
|
||||
[[pdi-operations|Ops]] creates, approves the labor plan.
|
||||
This limits our ability to make interesting decisions:
|
||||
MC cable ILO PVC in-slab pushes the schedule out.
|
||||
|
||||
|
||||
@@ -10,6 +10,11 @@ date-created: 2026-03-11T11:58:49-04:00
|
||||
---
|
||||
# 2026-03-11 11:58:49
|
||||
|
||||
%%
|
||||
Note concerning [[ambiguity-in-construction-estimating]]
|
||||
and [[transparency-in-construction-estimating]].
|
||||
%%
|
||||
|
||||
## Selling Scope
|
||||
|
||||
When an estimator provides a proposal,
|
||||
|
||||
@@ -31,7 +31,7 @@ potentially to be qualified in future bids.
|
||||
>
|
||||
> 2. Awarded contract does not include respect for the direction
|
||||
>
|
||||
> 3. Ops, not aware of direction, believes ConEst takeoff was in error.
|
||||
> 3. [[pdi-operations|Ops]], not aware of direction, believes ConEst takeoff was in error.
|
||||
|
||||
Intent is to improve transparency,
|
||||
an area the OneNote is poor in.
|
||||
|
||||
@@ -15,8 +15,8 @@ and replaced with [[heating-designations]],
|
||||
I suggested leaving the existing work alone,
|
||||
citing that the limited information
|
||||
makes likely our superiors will have a different interpretation than us.
|
||||
**If we changed the takeoff then**
|
||||
**we would have to change it again.**
|
||||
**If we changed the takeoff now**
|
||||
**then we would have to change it again.**
|
||||
|
||||
> Ultimately we did change the takeoff
|
||||
> because there were less than a dozen outlets in the project.
|
||||
@@ -27,7 +27,8 @@ This is a good example of a scope question
|
||||
which I believe should be saved for review,
|
||||
not raised with the senior.
|
||||
|
||||
1. The maximum project cost impact of the decision is low,
|
||||
1. The maximum project cost impact of the decision is low
|
||||
(final cost is not especially [[sensitivity|sensitive]] to it),
|
||||
being only the difference between RG6 and Cat5e.
|
||||
|
||||
2. The result of the decision will not affect our future takeoff.
|
||||
|
||||
@@ -48,7 +48,7 @@ with no coordination with other disciplines.
|
||||
|
||||
Water Feature plans are a similar case.
|
||||
|
||||
> [!quote] [[josh-komis]] 2026-05-28 around 10:30 (pp.)
|
||||
> [!quote] [[joshua-komis]] 2026-05-28 around 10:30 (pp.)
|
||||
> Assume a single-point connection
|
||||
> to a pool equipment panel.
|
||||
> 100A for the spa.
|
||||
|
||||
@@ -12,7 +12,7 @@ daily: "[[2026-05-30]]"
|
||||
|
||||
Hubbard doesn't explain the concept
|
||||
of "record-breaking probability" to my tastes.
|
||||
more to the point,
|
||||
More to the point,
|
||||
he gives special attention to minimum and maximum
|
||||
when the probability that the next sample will have _any_ rank
|
||||
is given by 1/(n+1).
|
||||
|
||||
@@ -0,0 +1,21 @@
|
||||
---
|
||||
id: 2026-06-01T08:31:48-0400
|
||||
title: 2026-06-01 08:31:48
|
||||
tags: []
|
||||
daily: "[[2026-06-01]]"
|
||||
---
|
||||
# 2026-06-01 08:31:48
|
||||
|
||||
## ConEst Schedule Meeting 2026w23
|
||||
|
||||
[[conest-schedule-meeting]] for [[2026w23]].
|
||||
|
||||
Recently received several WBS approvals,
|
||||
expect bells rung for them soon.
|
||||
|
||||
[[milan-hrvacevic|Milan]]'s team
|
||||
just returned from Albuquerque,
|
||||
visiting a data center there.
|
||||
|
||||
Committed to finishing [[303-mariposa-residence]]
|
||||
and [[cincinnati-convention-center-hotel]] this week.
|
||||
Reference in New Issue
Block a user