vault backup: 2025-12-11 12:38:04
This commit is contained in:
@@ -14,12 +14,16 @@ tags:
|
||||
|
||||
#occupational/takeoff #topic/ambiguity #topic/transparency
|
||||
|
||||
Related: [[lighting-controls-takeoff]]
|
||||
|
||||
### Minutes
|
||||
|
||||
2025-12-10 08:30--10:00
|
||||
|
||||
Objective: Discuss lighting control systems
|
||||
|
||||
***
|
||||
|
||||
A primary reason for the discussion was presented:
|
||||
|
||||
> [!example] ^ex
|
||||
@@ -31,6 +35,8 @@ A primary reason for the discussion was presented:
|
||||
> When the project team received a quote for a "per code" system,
|
||||
> the total was ~$600,000.
|
||||
|
||||
***
|
||||
|
||||
Ultimately the responsibility is ConEst's
|
||||
to resolve discrepancies between:
|
||||
* applicable code
|
||||
@@ -38,6 +44,8 @@ to resolve discrepancies between:
|
||||
* Bid proposal intent
|
||||
* PDR quote intent
|
||||
|
||||
***
|
||||
|
||||
It was erroneously suggested that lighting control conductors
|
||||
may be run with their circuit conductors if both are 600V insulated.[^1]
|
||||
|
||||
|
||||
@@ -18,4 +18,7 @@ However, for construction projects,
|
||||
**return** is known but **cost** must be estimated.
|
||||
In this way, projects are better compared to _insurance accounts_.
|
||||
|
||||
- cost of individual service is uncertain
|
||||
- cost to customer must be minimized
|
||||
|
||||
[[actuarial-science]]
|
||||
|
||||
@@ -23,6 +23,8 @@ are currently disparate, disjointed, and redundant
|
||||
|
||||
### Naming Conventions (Use Case vs. Description)
|
||||
|
||||
Related: [[realism-vs-instrumentalism]]
|
||||
|
||||
Naming by use case is intuitive for those without estimating or field experience,
|
||||
but has the side effect that those accustomed to the names
|
||||
will inevitably _treat them as descriptive_.
|
||||
|
||||
@@ -47,11 +47,12 @@ that errors aren't set in stone
|
||||
until a contract is signed.
|
||||
|
||||
Destigmatizing proposal retraction is of critical concern for subcontractors.
|
||||
See [[estimating-culture]] for more on estimate error [[strategy#Game Theory]].
|
||||
See [[estimating-culture]] for more on estimate error [[game-theory]].
|
||||
|
||||
It's important to recognize that retracting a proposal
|
||||
may upset a few people employed by the GC,
|
||||
but consider how little your own opinion matters to your company's strategic decisions.
|
||||
but consider how little your own opinion
|
||||
matters to your company's strategic decisions.
|
||||
Much bigger people are involved after the proposal is accepted.
|
||||
|
||||
## Resources
|
||||
|
||||
@@ -12,8 +12,10 @@ title: Estimating Ethics
|
||||
---
|
||||
# Estimating Ethics
|
||||
|
||||
Clients engaging in unethical bidding practices can quickly gain a reputation for doing so,
|
||||
leading to reduced bid response that can be impossible to fully recover from.
|
||||
Contractors engaging in unethical bidding practices
|
||||
can quickly gain a reputation for doing so,
|
||||
leading to reduced bid response
|
||||
that can be impossible to fully recover from.
|
||||
|
||||
To ensure a transparent bidding process, one must
|
||||
|
||||
|
||||
+1
-19
@@ -12,29 +12,11 @@ title: Fixtures Takeoff
|
||||
# Fixtures Takeoff
|
||||
|
||||
This system is only for luminaires and their immediate branch wiring.
|
||||
See also [[lighting-controls]] and [[electrical]].
|
||||
|
||||
## Info
|
||||
See also [[lighting-controls-takeoff]] and [[electrical-takeoff]].
|
||||
|
||||
## Sequence
|
||||
|
||||
### 1. Preparation
|
||||
|
||||
1. Read about the project specifications and construction type
|
||||
2. In drawings, locate:
|
||||
* Fixture Schedule
|
||||
* Reflected Ceiling Plans
|
||||
|
||||
### 2. Takeoff
|
||||
|
||||
See [[fixture-designations]].
|
||||
|
||||
1. Takeoff floor plans in order
|
||||
2. Takeoff enlarged drawings
|
||||
|
||||
### 3. Review
|
||||
|
||||
1. Garage Homeruns
|
||||
2. Luminaire in Amenity Areas
|
||||
3. Ensure appropriate breakdowns
|
||||
* Site lighting in System "FML - Site Fixtures Material & Labor"
|
||||
|
||||
+17
-19
@@ -23,8 +23,8 @@ abbreviated Btu<sub>IT</sub>
|
||||
|
||||
$$
|
||||
\begin{align*}
|
||||
1 \text{Btu}_\text{IT} &= \left( 4.1868 \times 453.59237 \times{\frac{5}{9}} \right) \text{J} \\
|
||||
&\approx 1055.056 \text{J}
|
||||
1 \text{Btu}_\text{IT} &= \left( 4.1868 \times 453.59237 \times{\frac{5}{9}} \right)~\text{J} \\
|
||||
&\approx 1055.056~\text{J}
|
||||
\end{align*}
|
||||
$$
|
||||
|
||||
@@ -34,8 +34,8 @@ a unit of power.
|
||||
|
||||
$$
|
||||
\begin{align*}
|
||||
1 \text{MBH} &= 1000 \text{Btu/hr} \\
|
||||
&\approx 3.412 \text{W}
|
||||
1 \text{MBH} &= 1000~\text{Btu/hr} \\
|
||||
&\approx 3.412~\text{W}
|
||||
\end{align*}
|
||||
$$
|
||||
|
||||
@@ -49,8 +49,8 @@ Unit of power
|
||||
|
||||
$$
|
||||
\begin{align*}
|
||||
1 \text{TR} &= 12000 \text{Btu}_\text{IT}/\text{h} \\
|
||||
&\approx 3516.853 \text{W}
|
||||
1 \text{TR} &= 12000~\text{Btu}_\text{IT}/\text{h} \\
|
||||
&\approx 3516.853~\text{W}
|
||||
\end{align*}
|
||||
$$
|
||||
|
||||
@@ -62,8 +62,6 @@ Unit of volumetric flow
|
||||
|
||||
### Airflow
|
||||
|
||||
* CFM
|
||||
|
||||
External static pressure (ESP)
|
||||
measured in inches of water
|
||||
|
||||
@@ -72,23 +70,23 @@ measured in inches of water
|
||||
* Tons (refrigeration)
|
||||
* MBH
|
||||
|
||||
Entering air temperature (EAT)
|
||||
Leaving air temperature (LAT)
|
||||
Mixed air temperature (MAT)
|
||||
* Entering air temperature (EAT)
|
||||
* Leaving air temperature (LAT)
|
||||
* Mixed air temperature (MAT)
|
||||
|
||||
Latent heat
|
||||
Sensible heat
|
||||
* Latent heat
|
||||
* Sensible heat
|
||||
|
||||
Sensible -> dry bulb
|
||||
Latent -> wet bulb
|
||||
* Sensible -> dry bulb
|
||||
* Latent -> wet bulb
|
||||
|
||||
#### ???
|
||||
|
||||
OSA EAT (F)
|
||||
EXH EAT (F)
|
||||
* OSA EAT (F)
|
||||
* EXH EAT (F)
|
||||
|
||||
IN S.L.
|
||||
OUT ALT.
|
||||
* IN S.L.
|
||||
* OUT ALT.
|
||||
|
||||
### Efficiency
|
||||
|
||||
|
||||
@@ -17,7 +17,7 @@ title: Lighting Controls Takeoff
|
||||
> [!info] "Local Control" as a PDI proposal qualification
|
||||
> The term "local control only" is sometimes used to indicate
|
||||
> no consideration for _any_ lighting control beyond standard devices,
|
||||
> (with `$D`'s being the triac type)
|
||||
> (with `$D`'s being the [[lighting-controls#Triac Dimming|triac]] type)
|
||||
> however, this phrasing is ambiguous and non-universal.
|
||||
> Confirm with [[pdi-estimating#Bid Estimating|bid team]] on what must be included.
|
||||
|
||||
@@ -31,7 +31,7 @@ Determine which Systems and Codes are required:
|
||||
|
||||
### Stand Alone
|
||||
|
||||
0-10V dim -- "LV cable" is 2 conductor
|
||||
0-10V dim --- "LV cable" is 2 conductor
|
||||
|
||||
Takeoff rough-in for switches and occupancy sensors
|
||||
* **Branch Length** = length of room
|
||||
|
||||
@@ -100,6 +100,13 @@ Locate:
|
||||
|
||||
1. Locate Equipment Schedules
|
||||
|
||||
### Fixtures
|
||||
|
||||
1. Read about the project specifications and construction type
|
||||
2. In drawings, locate:
|
||||
* Fixture Schedule
|
||||
* Reflected Ceiling Plans
|
||||
|
||||
### Low Voltage
|
||||
|
||||
1. Locate Proposal/Scope of Work. Determine ownership and takeoff responsibility:
|
||||
|
||||
@@ -21,7 +21,7 @@ for [[construction-estimating]] which:
|
||||
* determines necessary [[estimating-detail]]
|
||||
|
||||
ROE leans heavily on [[uncertainty#Value of Information]],
|
||||
which challenges the natural tendency to shy from uncertainty
|
||||
which challenges the natural tendency to fear even the smallest risk
|
||||
with the reality of the **cost of certainty**.
|
||||
|
||||
ROE does not endorse common shortcuts that round up to "cover" uncertainty,
|
||||
@@ -32,19 +32,8 @@ increasing the probability of loss to a competitor.
|
||||
|
||||
## TALK
|
||||
|
||||
Despite how alien my approach may seem to most estimators,
|
||||
I believe its all merely extrapolation on the conventional practice.
|
||||
|
||||
ROE includes fields far more disparate
|
||||
than my peers would traditionally consider relevant.
|
||||
|
||||
Bid risk may fit a [Taleb distribution](https://en.wikipedia.org/wiki/Taleb_distribution).
|
||||
|
||||
[Actuarial Science](https://en.wikipedia.org/wiki/Actuarial_science)
|
||||
strongly parallels construction estimation:
|
||||
|
||||
- cost of individual service is uncertain
|
||||
- cost to customer must be minimized
|
||||
This note currently gets too far into the weeds
|
||||
of critiquing common practice.
|
||||
|
||||
%%
|
||||
|
||||
@@ -83,9 +72,7 @@ See [[optimal-estimating-patterns]] for more.
|
||||
Objections to the use of historical data in new estimates are not unfounded.
|
||||
A framework to do so competently and consistently
|
||||
does not currently exist.
|
||||
|
||||
> [!info]
|
||||
> Nor does the software necessary to utilize such a framework efficiently.
|
||||
Nor does the software necessary to utilize such a framework efficiently.
|
||||
|
||||
The goal in and of itself ought not be controversial, however.
|
||||
Businesses regularly make far riskier decisions based on projections
|
||||
@@ -117,7 +104,8 @@ Estimators know what the most likely and most expensive options are for a given
|
||||
and can fill in the detail required for item-oriented takeoff.
|
||||
This is called an **assumption** and is the basis of cost estimation.
|
||||
|
||||
Assumptions are fundamentally incompatible with item-oriented estimating as it is commonly implemented.
|
||||
Assumptions are fundamentally incompatible with item-oriented estimating
|
||||
as it is commonly implemented.
|
||||
It is not possible to compare price possibilities
|
||||
except by creating separate takeoffs and breakdowns for each one.
|
||||
|
||||
|
||||
+8
-1
@@ -1,13 +1,13 @@
|
||||
---
|
||||
id:
|
||||
aliases: []
|
||||
title: Takeoff Review
|
||||
tags:
|
||||
- authorship/original
|
||||
- destiny/permanent
|
||||
- occupational/takeoff
|
||||
- status/incomplete
|
||||
- type/encyclopedia
|
||||
title: Takeoff Review
|
||||
---
|
||||
# Takeoff Review
|
||||
|
||||
@@ -22,3 +22,10 @@ Count Car chargers and location
|
||||
Ensure takeoff is in the generator `Area` and `System` breakdowns
|
||||
|
||||
Put location, quantity, and type on OneNote
|
||||
|
||||
## Fixtures
|
||||
|
||||
1. Garage Homeruns
|
||||
2. Luminaire in Amenity Areas
|
||||
3. Ensure appropriate breakdowns
|
||||
* Site lighting in System "FML - Site Fixtures Material & Labor"
|
||||
|
||||
Reference in New Issue
Block a user