Merge remote-tracking branch 'origin/main'
This commit is contained in:
+1
-1
@@ -50,6 +50,6 @@ I've decided I've considered learning [[shorthand]]
|
||||
enough times independently
|
||||
that I would likely benefit from it.
|
||||
|
||||
I added [[Leslie_1968_Gregg-Notehand|a book]]
|
||||
I added [[leslie-et-al_1968_gregg-notehand|a book]]
|
||||
on [[shorthand#Gregg Notehand]]
|
||||
to my calibre library.
|
||||
|
||||
+1
-1
@@ -15,7 +15,7 @@ title: 2025-11-16
|
||||
#topic/hobbies/shorthand #topic/hobbies/writing
|
||||
|
||||
Yesterday evening,
|
||||
while I was reading [[Leslie_1968_Gregg-Notehand]],
|
||||
while I was reading [[leslie-et-al_1968_gregg-notehand]],
|
||||
for the first time practicing its lessons,
|
||||
trying to [[learn-shorthand]],
|
||||
I was growing frustrated with the terminology the text uses
|
||||
|
||||
@@ -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]
|
||||
|
||||
|
||||
@@ -0,0 +1,32 @@
|
||||
---
|
||||
id:
|
||||
aliases: []
|
||||
title: 2025-12-12
|
||||
tags:
|
||||
- authorship/original
|
||||
- destiny/permanent
|
||||
- status/draft
|
||||
- type/daily
|
||||
---
|
||||
# 2025-12-12
|
||||
|
||||
## 2025-12-12 09:38
|
||||
|
||||
A humorous exchange between a peer in estimating and myself:
|
||||
|
||||
> **Peer:** "Your research will one day cure estimator's brain,
|
||||
> a disease sweeping across \[our\] floor"
|
||||
>
|
||||
> **Me:** "if you ask me-I mean my friend-it's quite rare actually"
|
||||
>
|
||||
> **Peer:** "more data will be needed before a strong conclusion can be made"
|
||||
>
|
||||
> **Me:** "damn it's got you too"
|
||||
|
||||
My response was meant to imply that,
|
||||
among those employed as estimators,
|
||||
knowledge of and application of scientific methods are rare.
|
||||
I wonder though if it would have been more apt
|
||||
to reply "you're in the clear" or something to that effect,
|
||||
implying that one with estimator brain
|
||||
would make decisions based on limited data.
|
||||
@@ -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]]
|
||||
|
||||
+4
-1
@@ -2,7 +2,10 @@
|
||||
id:
|
||||
aliases: []
|
||||
title: Auction Theory
|
||||
tags: []
|
||||
tags:
|
||||
- authorship/original
|
||||
- destiny/permanent
|
||||
- topic/strategy
|
||||
---
|
||||
# Auction Theory
|
||||
|
||||
|
||||
@@ -15,12 +15,12 @@ tags:
|
||||
## Scope
|
||||
|
||||
This note is intended to describe bid process strategy
|
||||
especially in terms of [[auction-theory]],
|
||||
which specifically addresses the competitive bid format
|
||||
typical of construction project award,
|
||||
and [[actuarial-science]], ...
|
||||
especially in terms of
|
||||
|
||||
See [[bad-bid-practice]]
|
||||
* [[auction-theory]],
|
||||
which specifically addresses the competitive bid format
|
||||
typical of construction project award, and
|
||||
* [[actuarial-science]], ...
|
||||
|
||||
### Outside Factors Influencing Bid Price
|
||||
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
---
|
||||
id:
|
||||
aliases: []
|
||||
title: Breakdown Objects
|
||||
tags:
|
||||
- authorship/original
|
||||
- destiny/fleeting
|
||||
@@ -9,7 +10,6 @@ tags:
|
||||
- topic/estimating
|
||||
- topic/software
|
||||
- type/idea
|
||||
title: Breakdown Objects
|
||||
---
|
||||
# Breakdown Objects
|
||||
|
||||
@@ -64,10 +64,13 @@ equipment of the same type is assumed to be evenly spaced.
|
||||
|
||||
![[location-vs-scope.excalidraw]]
|
||||
|
||||
MDPB is physically _located_ in "Bldg A",
|
||||
but serves only loads in "Bldg B".
|
||||
MDPB is physically _located_ in Building A,
|
||||
but serves only loads in Building B.
|
||||
|
||||
```
|
||||
location = "Bldg A"
|
||||
scope = "Bldg B"
|
||||
location = Buildings["Building A"]
|
||||
scope = Buildings["Building B"]
|
||||
```
|
||||
|
||||
Were Building B removed from the contract scope,
|
||||
it can be expected that MDPB would be as well.
|
||||
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 182 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 91 KiB |
@@ -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
|
||||
|
||||
@@ -13,12 +13,12 @@ title: Distribution Equipment
|
||||
|
||||
## Pigtail Adaptors
|
||||
|
||||
![[burndy-AYP300_pigtail-adaptor.png|201x201]]
|
||||
|
||||
Pigtail adaptors are used where feeder wires exceed the range of terminal lugs.
|
||||
Pigtail adaptors are used where wire size exceeds the range of terminal lugs.
|
||||
They are crimped onto the stripped end of the conductor.
|
||||
|
||||
> [!info]
|
||||
> "Pigtail adaptor" is the most common name and spelling for the device,
|
||||
> "Pigtail adaptor" is (unfortunately)
|
||||
> the most common name and spelling for the device,
|
||||
> however it's something of a misnomer,
|
||||
> having nothing to do with pigtails (a short length of wire),
|
||||
> the name likely stemming from the device being used _in lieu_ of a pigtail.
|
||||
@@ -29,8 +29,6 @@ Pigtail adaptors are used where feeder wires exceed the range of terminal lugs.
|
||||
> * Theatrical Switchboard
|
||||
> * Stage Switchboard
|
||||
|
||||
![[company-switch.png|500x625]]
|
||||
|
||||
Company switches are lighting control equipment
|
||||
unique to performance venues
|
||||
like those subject to [[nfpa-70_520_theaters]]
|
||||
|
||||
@@ -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"
|
||||
|
||||
@@ -7,6 +7,7 @@ tags:
|
||||
- destiny/permanent
|
||||
- status/incomplete
|
||||
- topic/math
|
||||
- topic/strategy
|
||||
- type/encyclopedia
|
||||
---
|
||||
# Game Theory
|
||||
|
||||
+3
-3
@@ -12,7 +12,7 @@ tags:
|
||||
# _Gregg Notehand_
|
||||
|
||||
Gregg Notehand is a simplified form of Gregg Shorthand.
|
||||
It is described in the namesake [[Leslie_1968_Gregg-Notehand]]
|
||||
It is described in the namesake [[leslie-et-al_1968_gregg-notehand]]
|
||||
|
||||
This note is a description and critique
|
||||
of both the book and the shorthand,
|
||||
@@ -25,7 +25,7 @@ and generally suffer from a facile understanding of phonology.
|
||||
Totally unacceptable for a proposed alternative alphabet,
|
||||
but then the text does not understand that's what it's proposing.
|
||||
|
||||
> [[Leslie_1968_Gregg-Notehand#2-8. Notehand principles]]
|
||||
> [[leslie-et-al_1968_gregg-notehand#2-8. Notehand principles]]
|
||||
> **Silent letters omitted.**
|
||||
> In the English language many words contain letters that are not pronounced.
|
||||
> In Notehand these silent letters are omitted,
|
||||
@@ -49,7 +49,7 @@ but then the text does not understand that's what it's proposing.
|
||||
|
||||
***
|
||||
|
||||
> [[Leslie_1968_Gregg-Notehand#2-8. Notehand principles]]
|
||||
> [[leslie-et-al_1968_gregg-notehand#2-8. Notehand principles]]
|
||||
> Gregg Notehand is easy to learn---easier, actually, than longhand. Why?
|
||||
> In longhand, there are many different ways of writing a given letter;
|
||||
> in Gregg Notehand, there is only one way.
|
||||
|
||||
+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
|
||||
|
||||
|
||||
@@ -134,7 +134,7 @@ year: 1968
|
||||
## Gregg Notehand
|
||||
|
||||
Gregg Notehand is a simplified form of Gregg Shorthand.
|
||||
It is described in the namesake [[Leslie_1968_Gregg-Notehand]]
|
||||
It is described in the namesake [[leslie-et-al_1968_gregg-notehand]]
|
||||
|
||||
### Critiques
|
||||
|
||||
@@ -143,7 +143,7 @@ and generally suffer from a facile understanding of phonology.
|
||||
Totally unacceptable for a proposed alternative alphabet,
|
||||
but then the text does not understand that's what it's proposing.
|
||||
|
||||
> [[Leslie_1968_Gregg-Notehand#2-8. Notehand principles]]
|
||||
> [[leslie-et-al_1968_gregg-notehand#2-8. Notehand principles]]
|
||||
> **Silent letters omitted.**
|
||||
> In the English language many words contain letters that are not pronounced.
|
||||
> In Notehand these silent letters are omitted,
|
||||
@@ -167,7 +167,7 @@ but then the text does not understand that's what it's proposing.
|
||||
|
||||
***
|
||||
|
||||
> [[Leslie_1968_Gregg-Notehand#2-8. Notehand principles]]
|
||||
> [[leslie-et-al_1968_gregg-notehand#2-8. Notehand principles]]
|
||||
> Gregg Notehand is easy to learn---easier, actually, than longhand. Why?
|
||||
> In longhand, there are many different ways of writing a given letter;
|
||||
> in Gregg Notehand, there is only one way.
|
||||
@@ -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"
|
||||
|
||||
@@ -92,6 +92,9 @@ Use standard MC assemblies for remaining devices.
|
||||
|
||||
### "High-Lows"
|
||||
|
||||
Empty in-wall pass through
|
||||
from credenza location to behind television location.
|
||||
|
||||
`COMMON ASSEMBLIES`/`TELECOM SYSTEMS`/`UNIT DATA - TELECOM`/`HIGH-LOW - TV SCOOP 1 1/2" ENT - NO CABLE`
|
||||
|
||||
Eaton 35M2W
|
||||
|
||||
+4
-3
@@ -43,12 +43,12 @@ when i die
|
||||
|
||||
### Commentary
|
||||
|
||||
I wrote this at about 4:00 this morning (2025-10-21)
|
||||
I wrote this at about 2025-10-21 04:00
|
||||
when I couldn't sleep.
|
||||
|
||||
#### Theme
|
||||
|
||||
At the time I thought the poem was very funny,
|
||||
At the time I thought the poem was very funny:
|
||||
it starts out morbid and death-negative,
|
||||
then becomes touching,
|
||||
then a sharp pivot to grotesque and absurd.
|
||||
@@ -74,7 +74,8 @@ they're letting the reader off easy:
|
||||
"don't bother with burial or cremation,
|
||||
just toss me in the woods",
|
||||
but the convenience is negated by their second request,
|
||||
a task that would be so ethically and technically difficult
|
||||
a task that would be so ethically difficult
|
||||
(not to mention technically difficult)
|
||||
as to be impossible for almost all people.
|
||||
|
||||
To make the speaker's request
|
||||
|
||||
@@ -144,8 +144,8 @@ may only be used where they will be concealed from view.
|
||||
|
||||
### EMT Overhead
|
||||
|
||||
Set-screw fittings are [[best-practice]]
|
||||
Set-screw fittings may not be acceptable.
|
||||
Set-screw fittings are cheaper than compression,
|
||||
but may not be acceptable.
|
||||
|
||||
> [!info]
|
||||
> EMT has a third coupling type "indenter",
|
||||
@@ -210,6 +210,8 @@ flowchart LR
|
||||
|
||||
#### Fire Rated Feeders
|
||||
|
||||
[[fire-resistive-wiring-methods-takeoff]]
|
||||
|
||||
PDI estimating practice is to run all "emergency" feeds
|
||||
(life-safety or just standby)
|
||||
in a 2-hour rated assembly.
|
||||
|
||||
Reference in New Issue
Block a user