ZaneMeyers/zmVault
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge remote-tracking branch 'origin/main'

Browse Source
This commit is contained in:
Zane Meyers
2026-02-25 22:14:35 -05:00
parent 4b68ae302a 802377a012
commit 760663ac84
124 changed files with 1632 additions and 935 deletions
Download Patch File Download Diff File Expand all files Collapse all files
2025-11-10.md
-150
View File
@@ -1,150 +0,0 @@
---
id:
aliases: []
title: 2025-11-10
tags:
- authorship/original
- destiny/permanent
- status/complete
- type/periodic/daily
dg-publish: true
---
# 2025-11-10
# 2025-11-10 06:53:??
_Monday Morning Before Work_
#original-format/typewritten-print #topic/mindfulness
I've been trying to be alone with my thoughts more
recently. It's almost bizarre how working in silence
for an hour makes the thought of music or an audio­book
seem overstimulating, It feels right, though.
To want to converse with myself rather than let my
superego be drowned out by appealing sounds or a
fantasy story I've already heard, or obscure facts
about a game I've never played and never will.
I still relapse, of course, a lifetime (albeit
a short one) of unhealthy interaction with computers
will do that, but I'm making quick progress.
I watched a video yesterday that suggested that
it might be my growing understanding of computers
rather than my self discipline that's lead to this
change in the dynamic between me and them. That,
in understanding _how_ they function, I've turned
them from _devices_ into _things_, which lack
the mystical allure of the former. Whatever
the reason, it's good progress as far
as I'm concerned. It feels good to be introspective
and to have time to build skills people care about,
like music and style and... birdwatching...
# 2025-11-10 10:40:??
#topic/estimating #occupational #original-format/digital-text
A significant change from Ace to PDI in my mentality during takeoff
is that I now tend to expect that (within reason)
"holes" in takeoff scripts are _intentional omissions_,
not holes in cost coverage.
# 2025-11-10 11:14:??
#occupational/takeoff #original-format/digital-text
I was updating my notes,
filling in gaps in scripts based on Joel's,
when I noticed a strange paragraph:
> [!quote] `OneNote`/`Joel Take-off`/`Misc. Notes`
> Drop Down Ceilings vs. GWB (Gypsum Wall Boards)
>
> Drop down ceiling is technically "Exposed" (the real term should be accessable),
> so Romex and SER is not permited. Will need to use MC.
>
> > [!image]
> > ### 334.12 Uses Not Permitted.
> >
> > #### 334.12(A) Types NM and NMC.
> >
> > Types NM and NMC cables shall not be permitted as follows:
> >
> > 1. In any dwelling or structure not specifically
> > permitted in 334.10(1), (2), (3)
> >
> > 2. ==Exposed in dropped or suspended ceilings==
> > in other than one- and two-family and multifamily dwellings
This analysis of 334.12(A)(2) is flawed.
Based on the [[nfpa-70_100_definitions|Article 100]] definitions
of [[nfpa-70_100_definitions#Exposed (as applied to wiring methods).|exposed]]
and [[nfpa-70_100_definitions#Dwelling, Multifamily.|dwelling]],
[[nfpa-70_334_nm-cable#334.12(A) Types NM and NMC.|334.12(A)(2)]]
can be paraphrased as follows:
> [!cite] NEC 334.12(A)(2), pp.
> Types NM and NMC cable are not permitted to be installed
> in accessible spaces above suspended ceilings,
> _except in buildings containing one or more dwelling units._
The prohibition of 334.12(A)(2) _never_ applies to apartments or condos,
And only applies to hotels and dormitories on a basis of AHJ interpretation
(See [[multi-family-dwellings#Are Hotels Multifamily Dwellings?]]).
It's unclear to me if this a genuine misunderstanding
or just a [[heuristics|rule of thumb]] to cover the case
that guestrooms are not interpreted to be dwelling units.
If it's the latter, I believe it's far too conservative
to be used whole-cloth on all estimates.
# 2025-11-10 15:15:??
### "Feeder"
#topic/construction/electrical #original-format/digital-text
The NEC definition of feeder is quite strict.
I'm certain I misuse it frequently.
![[nfpa-70_100_definitions#Feeder.]]
It _does not_ include power conductors to
[[nfpa-70_100_definitions#Utilization Equipment.|utilization equipment]],
those are [[nfpa-70_100_definitions#Branch Circuit.|branch circuit]] conductors.
# 2025-11-10 20:00:??
_Monday Evening, Before Bed_
#topic/estimating #occupational #original-format/typewritten-print
Today while (a peer) and I were walking, he asked
me what I thought of his qualities as an estimator.
I told him I think he has the right of it, that having beliefs
about what's correct that don't change just because
a senior says they should, is a good sign.
I can't remember now if I knew it before today,
but my relationship with Dale, my former manager,
while never "good", was much improved when I started
pushing back on his direction and feedback. I became
an estimator, where before I was just someone who
could estimate for him. He hated it, and let me know,
but I never felt more sure of my position.
Estimating is not a field where you get ahead
by being more technically skilled or efficient.
You distinguish yourself by convincing your superiors
that you understand the objective and how to achieve
it. The best estimators---as measured by compensation
package---are not doing takeoff, they're
telling other estimators what to take off and how.
Conquer your self-doubt. Tell your boss they're
wrong and stupid and they should feel bad. Profit.
2025-11-11.md
-65
View File
@@ -1,65 +0,0 @@
---
id:
aliases: []
title: 2025-11-11
tags:
- authorship/original
- destiny/permanent
- status/complete
- type/periodic/daily
dg-publish: true
---
# 2025-11-11
# 2025-11-11 06:06:??
_Tuesday Morning, Before Work_
#topic/estimating #original-format/typewritten-print
One of the most appealing aspects of estimating
to me is the dynamic we have with our employers.
my experience was at Ace that estimators act like,
and are treated like good artists, like loveable
little scamps who always get into trouble, but
you keep them around because they do good work.
There was no other position with a similar reputation.
I attribute this strange relationship to two
facts of our role:
1. Estimating provides executives with a service,
one that they could almost do without, but that they
understand the value of paying for.
2. Estimating is just math-heavy enough that it
seems like magic to the uninitiated.
In these ways we're actually more like court
wizards than artists, which is an understandably
desirable position.
# 2025-11-11 14:41:??
#topic/estimating #topic/transparency #original-format/digital-text
I just saw a post on a construction estimators forum
from a user lamenting that their coworkers and customers
largely do not understand the difference between markup and margin.
It made me remember the micro-debates about that I would have with Dale
every time we were closing out an estimate.
This is the example I would always give
while trying to explain it to him.
![[markup-vs-margin#Markup vs. Margin]]
***
The user also stated that they would prefer to list overhead and profit
separately from scope line item costs,
but that their customers push back when they try.
I'm not sure where they got this preference.
Sure that would be more "transparent",
but it's at odds with the purpose of a breakdown.
2025-11-13.md
-75
View File
@@ -1,75 +0,0 @@
---
id:
aliases: []
title: 2025-11-13
tags:
- authorship/original
- destiny/permanent
- status/complete
- type/periodic/daily
dg-publish: true
---
# 2025-11-13
# 2025-11-13 08:03:??
#topic/hobbies/writing
I was thinking about recent critiques of my writing style
and how they don't really apply to my speech,
even though I don't imagine myself approaching them differently.
I imagine I _would_ speak like I write,
but that to use the same constructions
would require a level of forethought
that I'm not capable of under the pressure of conversation.
# 2025-11-13 08:19:??
#topic/estimating #occupational
I'm still working on articulating
my main difficulty in the transition
from Ace to PDI estimating.
At a high level,
it's that our process is built on _instrumental_ methods,
but that it is frequently judged from a _realist_ perspective.
See [[realism-vs-instrumentalism]].
There may be a more accurate way to state this.
[[2025-11-10#2025-11-10 11 14]] may be an example of a similar issue,
where instrumental methods are presented as if they were realist,
causing confusion when the methods are,
as judged from a realist perspective, wrong.
## 2025-11-13 ??:??:??
#occupational
### Questions for Bid Estimators
Questions for [[pdi-estimating#Bid Estimating|PDI Bid Estimators]].
#### Exclusions
When we send proposals with significant exclusions
(no lighting control, no demo, no submetering,
even when designed and shown on drawings):
Is there a conversation happening with our customers
before they receive our proposal?
Is it clear they understand what we're excluding?
# 2025-11-13 20:41:??
#topic/hobbies/shorthand
I've decided I've considered learning [[shorthand]]
enough times independently
that I would likely benefit from it.
I added [[leslie-et-al_1968_gregg-notehand|a book]]
on [[shorthand#Gregg Notehand|Gregg Notehand]]
to my calibre library.
2025-12-02.md
-90
View File
@@ -1,90 +0,0 @@
---
id:
aliases: []
title: 2025-12-02
tags:
- authorship/original
- destiny/permanent
- status/draft
- type/periodic/daily
dg-publish: true
---
# 2025-12-02
# 2025-12-02 10:40:??
#topic/construction/electrical
> [!cite] [Hysteresis - Wikipedia](https://en.wikipedia.org/wiki/Hysteresis)
> **Hysteresis** is the dependence of the state of a system on its history.
> For example, a [magnet](https://en.wikipedia.org/wiki/Magnet "Magnet")
> may have more than one possible
> [magnetic moment](https://en.wikipedia.org/wiki/Magnetic_moment "Magnetic moment")
> in a given [magnetic field](https://en.wikipedia.org/wiki/Magnetic_field "Magnetic field"),
> depending on how the field changed in the past.
> Such a system is called **hysteretic**.
![[alternating-current#Ferroelectric Hysteresis]]
# 2025-12-02 10:57:??
### Set Notation Example
Let $A$ and $B$ be sets
sharing some but not all elements.
* $A \cap B \neq \varnothing$:
"The intersection of $A$ and $B$ is nonempty"
(They share at least one element).
* $A \not\subseteq B$:
"$A$ is not a subset of $B$"
($A$ has at least one element not in $B$).
Equivalent to $A \setminus B \neq \varnothing$.
* $B \not\subseteq A$:
"$B$ is not a subset of $A$"
($B$ has at least one element not in $A$).
Equivalent to $B \setminus A \neq \varnothing$.
# 2025-12-02 13:20:??
### Panel Schedule Relationship Diagram
#### Sections
A panelboard with multiple sections
may or may not have multiple schedules.
`PANEL A1 SEC 1`
#### Typical Schedules
Schedules may be typical of multiple panelboards
`PANEL H(2-6)`
# 2025-12-02 15:35:??
### Bluebeam Model Context Protocol Tools
* add_view_port
* color_process_analyze
* color_process_modify
* count
* create_bookmarks
* create_markup_thumbnail
* get_markup_state
* get_page_count
* get_page_information
* list_markups_in_pdf
* list_state_models_in_pdf
* list_studio_projects
* list_studio_sessions
* open_file
* redact
* save_as_text
* search_and_markup
* set_markup_property
* set_markup_state
* set_page_labels
* stamp
* studio_project_search
2025-12-16.md
-24
View File
@@ -1,24 +0,0 @@
---
id:
aliases: []
title: 2025-12-16
tags:
- authorship/original
- destiny/permanent
- status/draft
- type/periodic/daily
dg-publish: true
---
# 2025-12-16
# 2025-12-16 09:20:52
[Probability Management](https://www.probabilitymanagement.org/)
[Handbook of Decision Analysis | Wiley Online Books](https://onlinelibrary.wiley.com/doi/book/10.1002/9781118515853)
# 2025-12-16 20:04:??
### Metalog Distributions
[Metalog Distributions]http://www.metalogdistributions.com/home.html)
2026-01-07.md
-134
View File
@@ -1,134 +0,0 @@
---
id:
aliases: []
title: 2026-01-07
tags:
- authorship/original
- destiny/permanent
- status/draft
- type/periodic/daily
dg-publish: true
---
# 2026-01-07
# 2026-01-07 06:41:??
> [!quote] _The Shadow of the Torturer_, Chapter 17: "The Challenge"
> No intellect is needed to see those figures who wait beyond the void of death---
> every child is aware of them, blazing with glories dark or bright,
> wrapped in authority older than the universe.
> They are the stuff of our earliest dreams, as of our dying visions.
> Rightly we feel our lives guided by them,
> and rightly too we feel how little we matter to them,
> the builders of the unimaginable,
> the fighters of wars beyond the totality of existence.
>
> The difficulty lies in learning that we ourselves encompass forces equally great.
> We say, "I will," and "I will not," and imagine ourselves
> (though we obey the orders of some prosaic person every day) our own masters,
> when the truth is that our masters are sleeping.
> One wakes within us and we are ridden like beasts,
> though the rider is but some hitherto unguessed part of ourselves.
# 2026-01-07 10:03:??
At Ace, "residential" always meant single-family/duplex construction,
but I think now we were the outliers.
# 2026-01-07 10:05:??
See [[pdi-breakdowns#Location]].
I have---for some time now---
been trying to figure out the purpose of the non-system breakdowns.
[[location-vs-scope]]
Perhaps there is another dichotomy
in that an estimator may use the area classifications of the design
or according to their own understanding of each term.
For lack of a better example,
whether a "101 - KITCHEN", without provisions for cooking,
would be broken down under "Kitchen".
# 2026-01-07 10:42:??
When I got to work today Art admonished a fellow estimator
for not uploading _all_ of a project's drawings,
even those they did not intend to take off, to Trimble Connect.
Art suggested that the estimator should upload all the drawings,
but only add them to LiveCount as needed.
I take issue with the suggestion on principle
since doing so would not benefit the estimator or their senior
(if they aren't added, the estimator can do nothing with them),
but would require not-insignificant effort.
Effort that would ultimately benefit no one:---
Trimble Connect's ham-fisted approach to version control
means that the fewer times it must be used, the better.
> I'm currently dealing with the headache of an estimate
> where such caution was not applied.
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,
fighting with Trimble Connect as they would be,
I suspect is even less.
> On my current project, after trying in vain to play by Trimble's rules,
> I started by deleting all the drawings I could
> (those without takeoff associated with them)
> then reuploaded the revised set.
> I'm confident that this would be the dominant strategy.
***
It's curious to me that the possibility of scope revisions
doesn't seem to be at the front of every estimator's mind
when doing takeoff or considering process changes,
like it was for my mentors and peers at Ace.
# 2026-01-07 12:13:??
#occupational #topic/estimating #topic/organization
Just now Jorge admonished another peer
for using insulated wire for pool bonding,
his rational was flawed beyond saving
(something about the difference between bonding and grounding),
but stemmed from a frustratingly common misunderstanding
that our Accubid assemblies are intended to be an accurate list
of the material to be installed.
They are not.
If they were intended to be accurate,
there would need to be several times as many.
They are a compromise between accuracy and estimator effort.
It should be assumed that for common scope,
at least one assembly should be acceptable as-is.
Pool bonding is required for at least a quarter of our jobs.
We have no bonding assemblies with bare wire.
Therefore it must be assumed that it was determined
that it would be acceptable to represent bare wire bonding with insulated wire items,
because otherwise it would be necessary to have double the assemblies,
or to expect estimators to substitute each size of wire
everywhere bare was necessary.
See [[realism-vs-instrumentalism]].
# 2026-01-07 16:03:??
#occupational #topic/estimating #topic/organization
There is a palpable animosity for [[pdi-estimating#Bid Estimating|Bid]]
in [[pdi-estimating#Construction Estimating (ConEst)|ConEst]],
stemming---I believe---from an lack of buy-in on Bid's part.
Their lack is easily explained by their [[estimating-culture#Incentives|incentive structure]]:
Since throughput is systematically prioritized over accuracy,
ConEst has a strictly antagonistic role
because it slows down the bid process.
2026-01-09.md
-114
View File
@@ -1,114 +0,0 @@
---
id:
aliases: []
title: 2026-01-09
tags:
- authorship/original
- destiny/permanent
- status/draft
- type/periodic/daily
dg-publish: true
---
# 2026-01-09
# 2026-01-09 10:00:03
### 2100 Crystal Drive
`#600 ? WHITE ?` had incorrect sort codes.
#### Lighting Control
I took off lighting per plans (E510)
in spite of proposal stating "local control".
Will have to be changed.
#### Labor Factor
Fire Alarm
Switchgear
Feeders
Subfeeds
Corridors
Amenity
Retail
Units
#### Fixtures
> [!failure]
> Several fixtures were erroneously based on NM cable.
I built some fixtures with \#12/3 in areas with emergency lighting
to be an unswitched hot.
Joel is having me change them to \#12/2.
#### Units
> [!failure]
> One unit type typical was missing `Area` quantities.
> Another had no takeoff.
#### Labor Plan
$$
\mathbb{E}\left[\frac{\text{Hours Per Unit}}{\text{Openings Per Unit}}\right] \approx .75~\text{Hours Per Opening}
$$
High Rise .110--.120 hr/sqft
# 2026-01-09 12:00:??
$$
\begin{gather*}
\frac{146097}{400} = 365.2425~\text{Days Per Year} \
\frac{20871}{400} = 52.1775~\text{Weeks Per Year} \
\frac{6957}{1600} = 4.348125~\text{Weeks Per Month}
\end{gather*}
$$
$$
\frac{365.2425~\text{Days Per Year}}{7~\text{Days Per Week}}
= 52.1775~\text{Weeks Per Year}
$$
$$
\frac{52.1775~\text{Weeks Per Year}}{12~\text{Months Per Year}}
= 4.348125~\text{Weeks Per Month}
$$
# 2026-01-09 14:45:??
[[bid-price-modeling]]
Suppose a true cost model,
accounting for all relevant information available at time $t$.
$C(t)$ returns a distribution whose [scale](https://en.wikipedia.org/wiki/Scale_parameter)
decreases with $t$, and $C(0)$ maps to a single value.
$t>0$ is time until the final payment.
> ![250](https://upload.wikimedia.org/wikipedia/commons/thumb/8/89/Log-normal-pdfs.png/960px-Log-normal-pdfs.png)
>
> Figure: lognormal distributions with the same [location](https://en.wikipedia.org/wiki/Location_parameter)
> varied by [scale](https://en.wikipedia.org/wiki/Scale_parameter).
# 2026-01-09 16:28:??
### Occam's razor
> [!info] Also Known As
> * the principle of parsimony
> * the law of parsimony
recommends searching for explanations constructed with the smallest possible set of elements.
Attributed to William of Ockham, 14th-century English philosopher and theologian.
> _Entia non sunt multiplicanda praeter necessitatem_
> ("Entities must not be multiplied beyond necessity")
> "Of two competing theories, the simpler explanation is to be preferred."
> [!quote] [[klugman-et-al_2019_loss-models#4.2 The Role of Parameters]]
> The principle of parsimony states that the simplest model
> that adequately reflects reality should be used.
2026-01-15.md
-23
View File
@@ -1,23 +0,0 @@
---
id:
aliases: []
title: 2026-01-15
tags:
- authorship/original
- destiny/permanent
- status/draft
- type/periodic/daily
dg-publish: true
---
# 2026-01-15
# 2026-01-15 08:11:10
Follow-up to [[2026-01-12#2026-01-12 12:23|2026-01-12 12:23]]
Left Apartment at 05:30, at terminal around 06:10.
# 2026-01-15 08:15:??
[[2025-11-13#2025-11-13 08:19]]
I spoke to a peer about this yesterday.
2025-11-01.md → daily/2025-11-01.md
View File
daily/2025-11-10.md
+12
View File
@@ -0,0 +1,12 @@
---
id:
aliases: []
title: 2025-11-10
tags:
- authorship/original
- destiny/permanent
- status/complete
- type/periodic/daily
dg-publish: true
---
# 2025-11-10
daily/2025-11-11.md
+12
View File
@@ -0,0 +1,12 @@
---
id:
aliases: []
title: 2025-11-11
tags:
- authorship/original
- destiny/permanent
- status/complete
- type/periodic/daily
dg-publish: true
---
# 2025-11-11
daily/2025-11-13.md
+12
View File
@@ -0,0 +1,12 @@
---
id:
aliases: []
title: 2025-11-13
tags:
- authorship/original
- destiny/permanent
- status/complete
- type/periodic/daily
dg-publish: true
---
# 2025-11-13
daily/2025-12-02.md
+12
View File
@@ -0,0 +1,12 @@
---
id:
aliases: []
title: 2025-12-02
tags:
- authorship/original
- destiny/permanent
- status/draft
- type/periodic/daily
dg-publish: true
---
# 2025-12-02
daily/2025-12-16.md
+12
View File
@@ -0,0 +1,12 @@
---
id:
aliases: []
title: 2025-12-16
tags:
- authorship/original
- destiny/permanent
- status/draft
- type/periodic/daily
dg-publish: true
---
# 2025-12-16
daily/2025-12-17.md
+12
View File
@@ -0,0 +1,12 @@
---
id:
aliases: []
title: 2025-12-17
tags:
- authorship/original
- destiny/permanent
- status/draft
- type/periodic/daily
dg-publish: true
---
# 2025-12-17
daily/2025-12-18.md
+12
View File
@@ -0,0 +1,12 @@
---
id:
aliases: []
title: 2025-12-18
tags:
- authorship/original
- destiny/permanent
- status/draft
- type/periodic/daily
dg-publish: true
---
# 2025-12-18
daily/2025-12-19.md
+12
View File
@@ -0,0 +1,12 @@
---
id:
aliases: []
title: 2025-12-19
tags:
- authorship/original
- destiny/permanent
- status/draft
- type/periodic/daily
dg-publish: true
---
# 2025-12-19
2026-01-01.md → daily/2026-01-01.md
View File
daily/2026-01-02.md
+12
View File
@@ -0,0 +1,12 @@
---
id:
aliases: []
title: 2026-01-02
tags:
- authorship/original
- destiny/permanent
- status/draft
- type/periodic/daily
dg-publish: true
---
# 2026-01-02
daily/2026-01-06.md
+12
View File
@@ -0,0 +1,12 @@
---
id:
aliases: []
title: 2026-01-06
tags:
- authorship/original
- destiny/permanent
- status/draft
- type/periodic/daily
dg-publish: true
---
# 2026-01-06
daily/2026-01-07.md
+12
View File
@@ -0,0 +1,12 @@
---
id:
aliases: []
title: 2026-01-07
tags:
- authorship/original
- destiny/permanent
- status/draft
- type/periodic/daily
dg-publish: true
---
# 2026-01-07
daily/2026-01-08.md
+12
View File
@@ -0,0 +1,12 @@
---
id:
aliases: []
title: 2026-01-08
tags:
- authorship/original
- destiny/permanent
- status/draft
- type/periodic/daily
dg-publish: true
---
# 2026-01-08
daily/2026-01-09.md
+12
View File
@@ -0,0 +1,12 @@
---
id:
aliases: []
title: 2026-01-09
tags:
- authorship/original
- destiny/permanent
- status/draft
- type/periodic/daily
dg-publish: true
---
# 2026-01-09
daily/2026-01-11.md
+12
View File
@@ -0,0 +1,12 @@
---
id:
aliases: []
title: 2026-01-11
tags:
- authorship/original
- destiny/permanent
- status/draft
- type/periodic/daily
dg-publish: true
---
# 2026-01-11
2026-01-12.md → daily/2026-01-12.md
View File
daily/2026-01-15.md
+12
View File
@@ -0,0 +1,12 @@
---
id:
aliases: []
title: 2026-01-15
tags:
- authorship/original
- destiny/permanent
- status/draft
- type/periodic/daily
dg-publish: true
---
# 2026-01-15
2026-01-19.md → daily/2026-01-19.md
View File
2026-01-20.md → daily/2026-01-20.md
View File
2026-01-22.md → daily/2026-01-22.md
View File
2026-01-23.md → daily/2026-01-23.md
View File
2026-01-25.md → daily/2026-01-25.md
View File
2026-01-28.md → daily/2026-01-28.md
View File
2026-01-29.md → daily/2026-01-29.md
View File
2026-01-30.md → daily/2026-01-30.md
View File
fixture-designations.md
+4 -1
View File
@@ -158,10 +158,13 @@ Separate these fixtures by labor, not length
B - Surface (Tape) = 1.0hr (0-17ft) - MC #12 40ft
_
*** Interior Amenity ***
IA - Surface (Tape) = 1.0hr (0-17ft) - MC+LV #12 40ft
IA - Surface (Tape) = 1.0hr (00-17ft) - MC+LV #12 40ft
IA - Surface (Tape) = 2.0hr (18-29ft) - MC+LV #12 40ft
IA - Surface (Tape) = 3.0hr (30-41ft) - MC+LV #12 40ft
IA - Surface (Tape) = 4.0hr (42-53ft) - MC+LV #12 40ft
IA - Surface (Tape) = 5.0hr (54-65ft) - MC+LV #12 40ft
IA - Surface (Tape) = 6.0hr (66-77ft) - MC+LV #12 40ft
IA - Surface (Tape) = 7.0hr (78-89ft) - MC+LV #12 40ft
```
## Recessed
nfpa-70_518_assembly-occupancies.md
+130
View File
@@ -0,0 +1,130 @@
---
id:
aliases:
- nec-518
title: Article 518 Assembly Occupancies
tags:
- authorship/other
- destiny/uncertain
- exclude-from-word-count
- status/draft
- topic/construction/electrical
- type/media/reference
---
# Article 518 Assembly Occupancies
### 518.1 Scope.
Except for the assembly occupancies
explicitly covered by [[nfpa-70_520_theaters#520.1 Scope.|520.1]],
this article covers all buildings or portions of buildings or structures
designed or intended for the gathering together of 100 or more persons
for such purposes as deliberation, worship, entertainment,
eating, drinking, amusement, awaiting transportation,
or similar purposes.
### 518.2 General Classification.
#### 518.2(A) Examples.
Assembly occupancies shall include, but not be limited to, the following:
* Armories
* Assembly halls
* Auditoriums
* Bowling lanes
* Club rooms
* Conference rooms
* Courtrooms
* Dance halls
* Dining and drinking facilities
* Exhibition halls
* Gymnasiums
* Mortuary chapels
* Multipurpose rooms
* Museums
* Places of awaiting transportation
* Places of religious worship
* Pool rooms
* Restaurants
* Skating rinks
#### 518.2(B) Multiple Occupancies.
Where an assembly occupancy forms a portion of a building containing other occupancies, Article 518 applies only to that portion of the building considered an assembly occupancy. Occupancy of any room or space for assembly purposes by less than 100 persons in a building of other occupancy, and incidental to such other occupancy, shall be classified as part of the other occupancy.
#### 518.2(C) Theatrical Areas.
Where any such building structure, or portion thereof, contains a projection booth or stage platform or area for the presentation of theatrical or musical productions, either fixed or portable, the wiring for that area, including associated audience seating areas, and all equipment that is used in the referenced area, and portable equipment and wiring for use in the production that will not be connected to permanently installed wiring, shall comply with Article 520.
> [!info] Informational Note:
> For methods of determining population capacity, see local building code or, in its absence, NFPA 101-2018, Life Safety Code.
### 518.3 Other Articles.
#### 518.3(A) Hazardous (Classified) Areas.
Electrical installations in hazardous (classified) areas located in assembly occupancies shall comply with Article 500.
#### 518.3(B) Temporary Wiring.
In exhibition halls used for display booths, as in trade shows, the temporary wiring shall be permitted to be installed in accordance with Article 590. Flexible cables and cords approved for hard or extra-hard usage shall be permitted to be laid on floors where protected from contact by the general public. The ground-fault circuit-interrupter requirements of 590.6 shall not apply. All other ground-fault circuit-interrupter requirements of this Code shall apply.
Where ground-fault circuit interrupter protection for personnel is supplied by plug-and-cord-connection to the branch circuit or to the feeder, the ground fault circuit interrupter protection shall be listed as portable ground fault circuit interrupter protection or provide a level of protection equivalent to a portable ground fault circuit interrupter, whether assembled in the field or at the factory.
> [!important] Exception:
> Where conditions of supervision and maintenance ensure that only qualified persons will service the installation, flexible cords or cables identified in Table 400.4 for hard usage or extra-hard usage shall be permitted in cable trays used only for temporary wiring. All cords or cables shall be installed in a single layer. A permanent sign shall be attached to the cable tray at intervals not to exceed 7.5 m (25 ft). The sign shall read
>
> CABLE TRAY FOR TEMPORARY WIRING ONLY
#### 518.3(C) Emergency Systems.
Control of emergency systems shall comply with Article 700.
### 518.4 Wiring Methods.
#### 518.4(A) General.
The fixed wiring methods shall be metal raceways, flexible metal raceways, nonmetallic raceways encased in not less than 50 mm (2 in.) of concrete, Type MI, MC, or AC cable. The wiring method shall itself qualify as an equipment grounding conductor according to 250.118 or shall contain an equipment grounding conductor sized in accordance with Table 250.122.
> [!important] Exception:
> Fixed wiring methods shall be as provided in the following:
>
> * (1) Audio signal processing, amplification, and reproduction equipment --- Article 640
> * (2) Communications systems --- Chapter 8
> * (3) Class 2 and Class 3 remote-control and signaling circuits --- Article 725
> * (4) Fire alarm circuits --- Article 760
#### 518.4(B) Nonrated Construction.
In addition to the wiring methods of 518.4(A), nonmetallic-sheathed cable, electrical nonmetallic tubing, and rigid nonmetallic conduit shall be permitted to be installed in those buildings or portions thereof that are not required to be of fire-rated construction by the applicable building code.
> [!info] Informational Note:
> Fire-rated construction is the fire-resistive classification used in building codes.
#### 518.4(C) Spaces with Finish Rating.
Electrical nonmetallic tubing and rigid nonmetallic conduit shall be permitted to be installed in club rooms, conference and meeting rooms in hotels or motels, courtrooms, dining facilities, restaurants, mortuary chapels, museums, libraries, and places of religious worship where the following apply:
* (1) The electrical nonmetallic tubing or rigid nonmetallic conduit is installed concealed within walls, floors, and ceilings where the walls, floors, and ceilings provide a thermal barrier of material that has at least a 15-minute finish rating as identified in listings of fire-rated assemblies.
* (2) The electrical nonmetallic tubing or rigid nonmetallic conduit is installed above suspended ceilings where the suspended ceilings provide a thermal barrier of material that has at least a 15-minute finish rating as identified in listings of fire-rated assemblies.
Electrical nonmetallic tubing and rigid nonmetallic conduit are not recognized for use in other space used for environmental air in accordance with 300.22(C).
> [!info] Informational Note:
> A finish rating is established for assemblies containing combustible (wood) supports. The finish rating is defined as the time at which the wood stud or wood joist reaches an average temperature rise of 121°C (250°F) or an individual temperature rise of 163°C (325°F) as measured on the plane of the wood nearest the fire. A finish rating is not intended to represent a rating for a membrane ceiling.
### 518.5 Supply.
Portable switchboards and portable power distribution equipment shall be supplied only from listed power outlets of sufficient voltage and ampere rating. Such power outlets shall be protected by overcurrent devices. Such overcurrent devices and power outlets shall not be accessible to the general public. Provisions for connection of an equipment grounding conductor shall be provided. The neutral conductor of feeders supplying solid-state phase control, 3-phase, 4-wire dimmer systems shall be considered a current-carrying conductor for purposes of ampacity adjustment. The neutral conductor of feeders supplying solid-state sine wave, 3-phase, 4-wire dimming systems shall not be considered a current-carrying conductor for purposes of ampacity adjustment.
> [!important] Exception:
> The neutral conductor of feeders supplying systems that use or are capable of using both phase-control and sine-wave dimmers shall be considered as current-carrying for purposes of ampacity adjustment.
> [!info] Informational Note:
> For definitions of solid-state dimmer types, see 520.2.
### 518.6 Illumination.
Illumination shall be provided for all working spaces about fixed service equipment, switchboards, switchgear, panelboards, or motor control centers installed outdoors that serve assembly occupancies. Control by automatic means only shall not be permitted. Additional lighting outlets shall not be required where the workspace is illuminated by an adjacent light source.
nfpa-70_590_temporary-installations.md
+223
View File
@@ -0,0 +1,223 @@
---
id:
aliases:
- nec-590
title: Article 590 Temporary Installations
tags:
- authorship/other
- destiny/uncertain
- exclude-from-word-count
- status/draft
- topic/construction/electrical
- type/media/reference
---
# Article 590 Temporary Installations
### 590.1 Scope.
The provisions of this article apply to temporary electric power and lighting installations.
### 590.2 All Wiring Installations.
#### 590.2(A) Other Articles.
Except as specifically modified in this article, all other requirements of this Code for permanent wiring shall apply to temporary wiring installations.
#### 590.2(B) Approval.
Temporary wiring methods shall be acceptable only if approved based on the conditions of use and any special requirements of the temporary installation.
### 590.3 Time Constraints.
#### 590.3(A) During the Period of Construction.
Temporary electric power and lighting installations shall be permitted during the period of construction, remodeling, maintenance, repair, or demolition of buildings, structures, equipment, or similar activities.
#### 590.3(B) 90 Days.
Temporary electric power and lighting installations shall be permitted for a period not to exceed 90 days for holiday decorative lighting and similar purposes.
#### 590.3(C) Emergencies and Tests.
Temporary electric power and lighting installations shall be permitted during emergencies and for tests, experiments, and developmental work.
#### 590.3(D) Removal.
Temporary wiring shall be removed immediately upon completion of construction or purpose for which the wiring was installed.
### 590.4 General.
#### 590.4(A) Services.
Services shall be installed in conformance with Parts I through VIII of Article 230, as applicable.
#### 590.4(B) Feeders.
Overcurrent protection shall be provided in accordance with 240.4, 240.5, 240.100, and 240.101. Conductors shall be permitted within cable assemblies or within multiconductor cords or cables of a type identified in Table 400.4 for hard usage or extra-hard usage. For the purpose of this section, the following wiring methods shall be permitted:
* (1) Type NM, Type NMC, and Type SE cables shall be permitted to be used in any dwelling, building, or structure without any height
limitation or limitation by building construction type and without concealment within walls, floors, or ceilings.
* (2) Type SE cable shall be permitted to be installed in a raceway in an underground installation.
> [!important] Exception:
> Single insulated conductors shall be permitted where installed for the purpose(s) specified in 590.3(C), where accessible only to qualified persons.
#### 590.4(C) Branch Circuits.
All branch circuits shall originate in an approved power outlet, switchgear, switchboard or panelboard, motor control center, or fused switch enclosure. Conductors shall be permitted within cable assemblies or within multiconductor cord or cable of a type identified in Table 400.4 for hard usage or extra-hard usage. Conductors shall be protected from overcurrent as provided in 240.4, 240.5, and 240.100. For the purposes of this section, the following wiring methods shall be permitted:
* (1) Type NM, Type NMC, and Type SE cables shall be permitted to be used in any dwelling, building, or structure without any height limitation or limitation by building construction type and without concealment within walls, floors, or ceilings.
* (2) Type SE cable shall be permitted to be installed in a raceway in an underground installation.
> [!important] Exception:
> Branch circuits installed for the purposes specified in 590.3(B) or 590.3(C) shall be permitted to be run as single insulated conductors. Where the wiring is installed in accordance with 590.3(B), the voltage to ground shall not exceed 150 volts, the wiring shall not be subject to physical damage, and the conductors shall be supported on insulators at intervals of not more than 3.0 m (10 ft); or, for festoon lighting, the conductors shall be so arranged that excessive strain is not transmitted to the lampholders.
#### 590.4(D) Receptacles.
##### 590.4(D)(1) All Receptacles.
All receptacles shall be of the grounding type. Unless installed in a continuous metal raceway that qualifies as an equipment grounding conductor in accordance with 250.118 or a continuous metal-covered cable that qualifies as an equipment grounding conductor in accordance with 250.118, all branch circuits shall include a separate equipment grounding conductor, and all receptacles shall be electrically connected to the equipment grounding conductor(s). Receptacles on construction sites shall not be installed on any branch circuit that supplies temporary lighting.
##### 590.4(D)(2) Receptacles in Wet Locations.
All 15- and 20-ampere, 125- and 250-volt receptacles installed in a wet location shall comply with 406.9(B)(1).
#### 590.4(E) Disconnecting Means.
Suitable disconnecting switches or plug connectors shall be installed to permit the disconnection of all ungrounded conductors of each temporary circuit. Multiwire branch circuits shall be provided with a means to disconnect simultaneously all ungrounded conductors at the power outlet or panelboard where the branch circuit originated. Identified handle ties shall be permitted.
#### 590.4(F) Lamp Protection.
All lamps for general illumination shall be protected from accidental contact or breakage by a suitable luminaire or lampholder with a guard.
Brass shell, paper-lined sockets, or other metal-cased sockets shall not be used unless the shell is connected to the circuit equipment grounding conductor.
#### 590.4(G) Splices.
A box, conduit body, or other enclosure, with a cover installed, shall be required for all splices.
> [!important] Exception No. 1:
> On construction sites, a box, conduit body, or other enclosure shall not be required for either of the following conditions:
>
> * (1) The circuit conductors being spliced are all from nonmetallic multiconductor cord or cable assemblies, provided that the equipment grounding continuity is maintained with or without the box.
>
> * (2) The circuit conductors being spliced are all from metal-sheathed cable assemblies terminated in listed fittings that mechanically secure the cable sheath to maintain effective electrical continuity.
> [!important] Exception No. 2:
> On construction sites, branch-circuits that are permanently installed in framed walls and ceilings and are used to supply temporary power or lighting, and that are GFCI protected, the following shall be permitted:
>
> * (1) A box cover shall not be required for splices installed completely inside of junction boxes with plaster rings.
>
> * (2) Listed pigtail-type lampholders shall be permitted to be installed in ceiling-mounted junction boxes with plaster rings.
>
> * (3) Finger safe devices shall be permitted for supplying and connection of devices.
#### 590.4(H) Protection from Accidental Damage.
Flexible cords and cables shall be protected from accidental damage. Sharp corners and projections shall be avoided. Where passing through doorways or other pinch points, protection shall be provided to avoid damage.
#### 590.4(I) Termination(s) at Devices.
Flexible cords and cables entering enclosures containing devices requiring termination shall be secured to the box with fittings listed for connecting flexible cords and cables to boxes designed for the purpose.
#### 590.4(J) Support.
Cable assemblies and flexible cords and cables shall be supported in place at intervals that ensure that they will be protected from physical damage. Support shall be in the form of staples, cable ties, straps, or similar type fittings installed so as not to cause damage.
Cable assemblies and flexible cords and cables installed as branch circuits or feeders
shall not be installed on the floor or on the ground.
Extension cords shall not be required to comply with 590.4(J).
Vegetation shall not be used for support of overhead spans of branch circuits or feeders.
> [!important] Exception:
> For holiday lighting in accordance with 590.3(B), where the conductors or cables are arranged with strain relief devices, tension take-up devices, or other approved means to avoid damage from the movement of the live vegetation, trees shall be permitted to be used for support of overhead spans of branch-circuit conductors or cables.
### 590.5 Listing of Decorative Lighting.
Decorative lighting used for holiday lighting and similar purposes,
in accordance with 590.3(B),
shall be listed and shall be labeled on the product.
### 590.6 Ground-Fault Protection for Personnel.
Ground-fault protection for personnel for all temporary wiring installations shall be provided to comply with 590.6(A) and (B). This section shall apply only to temporary wiring installations used to supply temporary power to equipment used by personnel during construction, remodeling, maintenance, repair, or demolition of buildings, structures, equipment, or similar activities. This section shall apply to power derived from an electric utility company or from an on-site-generated power source.
#### 590.6(A) Receptacle Outlets.
Temporary receptacle installations used to supply temporary power to equipment used by personnel during construction, remodeling, maintenance, repair, or demolition of buildings, structures, equipment, or similar activities shall comply with the requirements of 590.6(A)(1) through (A)(3), as applicable.
> [!important] Exception:
> In industrial establishments only, where conditions of maintenance and supervision ensure that only qualified personnel are involved, an assured equipment grounding conductor program as specified in 590.6(B)(2) shall be permitted for only those receptacle outlets used to supply equipment that would create a greater hazard if power were interrupted or having a design that is not compatible with GFCI protection.
##### 590.6(A)(1) Receptacle Outlets Not Part of Permanent Wiring.
All 125-volt, single-phase, 15-, 20-, and 30-ampere receptacle outlets that are not a part of the permanent wiring of the building or structure and that are in use by personnel shall have ground-fault circuit-interrupter protection for personnel. In addition to this required ground-fault circuit-interrupter protection for personnel, listed cord sets or devices incorporating listed ground-fault circuit-interrupter protection for personnel identified for portable use shall be permitted.
##### 590.6(A)(2) Receptacle Outlets Existing or Installed as Permanent Wiring.
Ground-fault circuit-interrupter protection for personnel shall be provided for all 125-volt, single-phase, 15-, 20-, and 30-ampere receptacle outlets installed or existing as part of the permanent wiring of the building or structure and used for temporary electric power.
Listed cord sets or devices incorporating listed ground-fault circuit-interrupter protection for personnel identified for portable use shall be permitted.
##### 590.6(A)(3) Receptacles on 15-kW or less Portable Generators.
All 125-volt and 125/250-volt, single-phase, 15-, 20-, and 30-ampere receptacle outlets that are a part of a 15-kW or smaller portable generator shall have listed ground-fault circuit-interrupter protection for personnel. All 15- and 20-ampere, 125- and 250-volt receptacles, including those that are part of a portable generator, used in a damp or wet location shall comply with 406.9(A) and (B).
Listed cord sets or devices incorporating listed ground-fault circuit-interrupter protection for personnel identified for portable use shall be permitted for use with 15-kW or less portable generators manufactured or remanufactured prior to January 1, 2011.
#### 590.6(B) Other Receptacle Outlets.
For temporary wiring installations, receptacles, other than those covered by 590.6(A)(1) through (A)(3) used to supply temporary power to equipment used by personnel during construction, remodeling, maintenance, repair, or demolition of buildings, structures, or equipment, or similar activities, shall have protection in accordance with 590.6(B)(1) or the assured equipment grounding conductor program in accordance with 590.6(B)(2).
##### 590.6(B)(1) GFCI Protection.
Ground-fault circuit-interrupter protection for personnel.
##### 590.6(B)(2) Assured Equipment Grounding Conductor Program.
A written assured equipment grounding conductor program continuously enforced at the site by one or more designated persons to ensure that equipment grounding conductors for all cord sets, receptacles that are not a part of the permanent wiring of the building or structure, and equipment connected by cord and plug are installed and maintained in accordance with the applicable requirements of 250.114, 250.138, 406.4(C), and 590.4(D).
* (a) The following tests shall be performed on all cord sets, receptacles that are not part of the permanent wiring of the building or structure, and cord-and-plug-connected equipment required to be connected to an equipment grounding conductor:
* (1) All equipment grounding conductors shall be tested for continuity and shall be electrically continuous.
* (2) Each receptacle and attachment plug shall be tested for correct attachment of the equipment grounding conductor. The equipment grounding conductor shall be connected to its proper terminal.
* (3) All required tests shall be performed as follows:
* a. Before first use on site
* b. When there is evidence of damage
* c. Before equipment is returned to service following any repairs
* d. At intervals not exceeding 3 months
* (b) The tests required in 590.6(B)(2)(a) shall be recorded and made available to the authority having jurisdiction.
The assured equipment grounding conductor program shall be documented and made available to the authority having jurisdiction.
> [!info] Informational Note:
> The Occupational Safety and Health Administration 29 CFR 1910 and 1926 contain requirements for assured equipment grounding conductor programs. Additional information is provided in NFPA 70E-2018, Standard for Electrical Safety in the Workplace.
### 590.7 Guarding.
For wiring over 600 volts, nominal, suitable fencing, barriers, or other effective means shall be provided to limit access only to authorized and qualified personnel.
### 590.8 Overcurrent Protective Devices.
#### 590.8(A) Where Reused.
Where overcurrent protective devices that have been previously used are installed in a temporary installation, these overcurrent protective devices shall be examined to ensure these devices have been properly installed, properly maintained, and there is no evidence of impending failure.
#### 590.8(B) Service Overcurrent Protective Devices.
Overcurrent protective devices for solidly grounded wye electrical services of more than 150 volts to ground but not exceeding 1000 volts phase-to-phase shall be current limiting.
> [!info] Informational Note:
> The phrase "evidence of impending failure" means that there is evidence such as arcing, overheating, loose or bound equipment parts, visible damage, or deterioration. The phrase "properly maintained" means that the equipment has been maintained in accordance with the manufacturers' recommendations and applicable industry codes and standards.
> References for manufacturers' recommendations
> and applicable industry codes and standards include but are not limited to
> NEMA AB 4-2017, Guidelines for Inspection and Preventative Maintenance of Molded-Case Circuit Breakers Used in Commercial and Industrial Applications;
> NFPA 70B-2019, Recommended Practice for Electrical Equipment Maintenance;
> NEMA GD 1-2016, Evaluating Water- Damaged Electrical Equipment;
> and IEEE 1458-2017, IEEE Recommended Practice for the Selection, Field Testing, and Life Expectancy of Molded-Case Circuit Breakers for Industrial Applications.
nfpa-70_national-electric-code.md
+2 -2
View File
@@ -124,7 +124,7 @@ title: "NFPA 70: National Electric Code"
* [[nfpa-70_515|515 Bulk Storage Plants]]
* [[nfpa-70_516|516 Spray Application, Dipping, Coating, and Printing Processes Using Flammable or Combustible Materials]]
* [[nfpa-70_517|517 Health Care Facilities]]
* [[nfpa-70_518|518 Assembly Occupancies]]
* [[nfpa-70_518_assembly-occupancies|518 Assembly Occupancies]]
* [[nfpa-70_520_theaters|520 Theaters, Audience Areas of Motion Picture and Television Studios, Performance Areas, and Similar Locations]]
* [[nfpa-70_522|522 Control Systems for Permanent Amusement Attractions]]
* [[nfpa-70_525|525 Carnivals, Circuses, Fairs, and Similar Events]]
@@ -136,7 +136,7 @@ title: "NFPA 70: National Electric Code"
* [[nfpa-70_551|551 Recreational Vehicles and Recreational Vehicle Parks]]
* [[nfpa-70_552|552 Park Trailers]]
* [[nfpa-70_555|555 Marinas, Boatyards, Floating Buildings, and Commercial and Noncommercial Docking Facilities]]
* [[nfpa-70_590|590 Temporary Installations]]
* [[nfpa-70_590_temporary-installations|590 Temporary Installations]]
## Chapter 6 Special Equipment
timestamped/2025-07-18_00-00-00.md
+1 -1
View File
@@ -1,7 +1,7 @@
---
id: 2025-07-18T00:00:00-04:00
aliases: []
title: 2025-07-18
title: 2025-07-18 ??:??:??
tags:
- authorship/original
- destiny/permanent
timestamped/2025-11-10_06-53-00.md
+39
View File
@@ -0,0 +1,39 @@
---
id:
aliases: []
title: 2025-11-10 06:53:??
tags:
- original-format/typewritten-print
- topic/mindfulness
- type/timestamped
dg-publish: true
---
# 2025-11-10 06:53:??
_Monday Morning Before Work_
I've been trying to be alone with my thoughts more
recently. It's almost bizarre how working in silence
for an hour makes the thought of music or an audio­book
seem overstimulating, It feels right, though.
To want to converse with myself rather than let my
superego be drowned out by appealing sounds or a
fantasy story I've already heard, or obscure facts
about a game I've never played and never will.
I still relapse, of course, a lifetime (albeit
a short one) of unhealthy interaction with computers
will do that, but I'm making quick progress.
I watched a video yesterday that suggested that
it might be my growing understanding of computers
rather than my self discipline that's lead to this
change in the dynamic between me and them. That,
in understanding _how_ they function, I've turned
them from _devices_ into _things_, which lack
the mystical allure of the former. Whatever
the reason, it's good progress as far
as I'm concerned. It feels good to be introspective
and to have time to build skills people care about,
like music and style and... birdwatching...
timestamped/2025-11-10_10-40-00.md
+17
View File
@@ -0,0 +1,17 @@
---
id:
aliases: []
title:
tags:
- type/timestamped
- topic/estimating
- occupational
- original-format/digital-text
dg-publish: true
---
# 2025-11-10 10:40:??
A significant change from Ace to PDI in my mentality during takeoff
is that I now tend to expect that (within reason)
"holes" in takeoff scripts are _intentional omissions_,
not holes in cost coverage.
timestamped/2025-11-10_11-14-00.md
+57
View File
@@ -0,0 +1,57 @@
---
id:
aliases: []
title:
tags:
- type/timestamped
- occupational/takeoff
- original-format/digital-text
dg-publish: true
---
# 2025-11-10 11:14:??
I was updating my notes,
filling in gaps in scripts based on Joel's,
when I noticed a strange paragraph:
> [!quote] `OneNote`/`Joel Take-off`/`Misc. Notes`
> Drop Down Ceilings vs. GWB (Gypsum Wall Boards)
>
> Drop down ceiling is technically "Exposed" (the real term should be accessable),
> so Romex and SER is not permited. Will need to use MC.
>
> > [!image]
> > ### 334.12 Uses Not Permitted.
> >
> > #### 334.12(A) Types NM and NMC.
> >
> > Types NM and NMC cables shall not be permitted as follows:
> >
> > 1. In any dwelling or structure not specifically
> > permitted in 334.10(1), (2), (3)
> >
> > 2. ==Exposed in dropped or suspended ceilings==
> > in other than one- and two-family and multifamily dwellings
This analysis of 334.12(A)(2) is flawed.
Based on the [[nfpa-70_100_definitions|Article 100]] definitions
of [[nfpa-70_100_definitions#Exposed (as applied to wiring methods).|exposed]]
and [[nfpa-70_100_definitions#Dwelling, Multifamily.|dwelling]],
[[nfpa-70_334_nm-cable#334.12(A) Types NM and NMC.|334.12(A)(2)]]
can be paraphrased as follows:
> [!cite] NEC 334.12(A)(2), pp.
> Types NM and NMC cable are not permitted to be installed
> in accessible spaces above suspended ceilings,
> _except in buildings containing one or more dwelling units._
The prohibition of 334.12(A)(2) _never_ applies to apartments or condos,
And only applies to hotels and dormitories on a basis of AHJ interpretation
(See [[multi-family-dwellings#Are Hotels Multifamily Dwellings?]]).
It's unclear to me if this a genuine misunderstanding
or just a [[heuristics|rule of thumb]] to cover the case
that guestrooms are not interpreted to be dwelling units.
If it's the latter, I believe it's far too conservative
to be used whole-cloth on all estimates.
timestamped/2025-11-10_15-15-00.md
+22
View File
@@ -0,0 +1,22 @@
---
id:
aliases: []
title:
tags:
- type/timestamped
- topic/construction/electrical
- original-format/digital-text
dg-publish: true
---
# 2025-11-10 15:15:??
### "Feeder"
The NEC definition of feeder is quite strict.
I'm certain I misuse it frequently.
![[nfpa-70_100_definitions#Feeder.]]
It _does not_ include power conductors to
[[nfpa-70_100_definitions#Utilization Equipment.|utilization equipment]],
those are [[nfpa-70_100_definitions#Branch Circuit.|branch circuit]] conductors.
timestamped/2025-11-10_20-00-00.md
+40
View File
@@ -0,0 +1,40 @@
---
id:
aliases: []
title:
tags:
- type/timestamped
- topic/estimating
- occupational
- original-format/typewritten-print
dg-publish: true
---
# 2025-11-10 20:00:??
_Monday Evening, Before Bed_
Today while (a peer) and I were walking, he asked
me what I thought of his qualities as an estimator.
I told him I think he has the right of it, that having beliefs
about what's correct that don't change just because
a senior says they should, is a good sign.
I can't remember now if I knew it before today,
but my relationship with Dale, my former manager,
while never "good", was much improved when I started
pushing back on his direction and feedback. I became
an estimator, where before I was just someone who
could estimate for him. He hated it, and let me know,
but I never felt more sure of my position.
Estimating is not a field where you get ahead
by being more technically skilled or efficient.
You distinguish yourself by convincing your superiors
that you understand the objective and how to achieve
it. The best estimators---as measured by compensation
package---are not doing takeoff, they're
telling other estimators what to take off and how.
Conquer your self-doubt. Tell your boss they're
wrong and stupid and they should feel bad. Profit.
timestamped/2025-11-11_06-06-00.md
+35
View File
@@ -0,0 +1,35 @@
---
id:
aliases: []
title:
tags:
- type/timestamped
- topic/estimating
- original-format/typewritten-print
dg-publish: true
---
# 2025-11-11 06:06:??
_Tuesday Morning, Before Work_
One of the most appealing aspects of estimating
to me is the dynamic we have with our employers.
my experience was at Ace that estimators act like,
and are treated like good artists, like loveable
little scamps who always get into trouble, but
you keep them around because they do good work.
There was no other position with a similar reputation.
I attribute this strange relationship to two
facts of our role:
1. Estimating provides executives with a service,
one that they could almost do without, but that they
understand the value of paying for.
2. Estimating is just math-heavy enough that it
seems like magic to the uninitiated.
In these ways we're actually more like court
wizards than artists, which is an understandably
desirable position.
timestamped/2025-11-11_14-41-00.md
+33
View File
@@ -0,0 +1,33 @@
---
id:
aliases: []
title:
tags:
- type/timestamped
- topic/estimating
- topic/transparency
- original-format/digital-text
dg-publish: true
---
# 2025-11-11 14:41:??
I just saw a post on a construction estimators forum
from a user lamenting that their coworkers and customers
largely do not understand the difference between markup and margin.
It made me remember the micro-debates about that I would have with Dale
every time we were closing out an estimate.
This is the example I would always give
while trying to explain it to him.
![[markup-vs-margin#Markup vs. Margin]]
***
The user also stated that they would prefer to list overhead and profit
separately from scope line item costs,
but that their customers push back when they try.
I'm not sure where they got this preference.
Sure that would be more "transparent",
but it's at odds with the purpose of a breakdown.
timestamped/2025-11-13_00-00-00.md
View File
timestamped/2025-11-13_08-03-00.md
+19
View File
@@ -0,0 +1,19 @@
---
id:
aliases: []
title:
tags:
- type/timestamped
- topic/hobbies/writing
dg-publish: true
---
# 2025-11-13 08:03:??
I was thinking about recent critiques of my writing style
and how they don't really apply to my speech,
even though I don't imagine myself approaching them differently.
I imagine I _would_ speak like I write,
but that to use the same constructions
would require a level of forethought
that I'm not capable of under the pressure of conversation.
timestamped/2025-11-13_08-19-00.md
+28
View File
@@ -0,0 +1,28 @@
---
id:
aliases: []
title:
tags:
- type/timestamped
- topic/estimating
- occupational
dg-publish: true
---
# 2025-11-13 08:19:??
I'm still working on articulating
my main difficulty in the transition
from Ace to PDI estimating.
At a high level,
it's that our process is built on _instrumental_ methods,
but that it is frequently judged from a _realist_ perspective.
See [[realism-vs-instrumentalism]].
There may be a more accurate way to state this.
[[2025-11-10#2025-11-10 11 14]] may be an example of a similar issue,
where instrumental methods are presented as if they were realist,
causing confusion when the methods are,
as judged from a realist perspective, wrong.
[[2025-11-13_08-19-01]]
timestamped/2025-11-13_08-19-01.md
+18
View File
@@ -0,0 +1,18 @@
## 2025-11-13 ??:??:??
#occupational
### Questions for Bid Estimators
Questions for [[pdi-estimating#Bid Estimating|PDI Bid Estimators]].
#### Exclusions
When we send proposals with significant exclusions
(no lighting control, no demo, no submetering,
even when designed and shown on drawings):
Is there a conversation happening with our customers
before they receive our proposal?
Is it clear they understand what we're excluding?
timestamped/2025-11-13_20-41-00.md
+18
View File
@@ -0,0 +1,18 @@
---
id:
aliases: []
title:
tags:
- type/timestamped
- topic/hobbies/shorthand
dg-publish: true
---
# 2025-11-13 20:41:??
I've decided I've considered learning [[shorthand]]
enough times independently
that I would likely benefit from it.
I added [[leslie-et-al_1968_gregg-notehand|a book]]
on [[shorthand#Gregg Notehand|Gregg Notehand]]
to my calibre library.
timestamped/2025-11-20_08-46-00.md
+2 -3
View File
@@ -6,14 +6,13 @@ tags:
- destiny/permanent
- status/draft
- type/periodic/daily
- occupational
title: 2025-11-20 08:46:??
dg-publish: true
---
# 2025-11-20 08:46:??
### Elliot St. WBS Prep
#occupational
## Elliot St. WBS Prep
MC multi-circuit homeruns have makeup included
($\text{Length} \times 1.1$)
timestamped/2025-11-21_10-11-00.md
+1 -2
View File
@@ -8,11 +8,10 @@ tags:
- status/complete
- topic/estimating
- type/timestamped
- topic/organization
---
# 2025-11-21 10:11:??
#topic/organization
> [!quote] [ELECTRI's Industry Benchmarking Tool - ELECTRI International](https://www.electri.org/research-overview/electris-industry-benchmarking-tool/)
> ### Hours Burned vs. Hours Earned
>
timestamped/2025-12-02_10-40-00.md
+21
View File
@@ -0,0 +1,21 @@
---
id:
aliases: []
title:
tags:
- type/timestamped
- topic/construction/electrical
dg-publish: true
---
# 2025-12-02 10:40:??
> [!cite] [Hysteresis - Wikipedia](https://en.wikipedia.org/wiki/Hysteresis)
> **Hysteresis** is the dependence of the state of a system on its history.
> For example, a [magnet](https://en.wikipedia.org/wiki/Magnet "Magnet")
> may have more than one possible
> [magnetic moment](https://en.wikipedia.org/wiki/Magnetic_moment "Magnetic moment")
> in a given [magnetic field](https://en.wikipedia.org/wiki/Magnetic_field "Magnetic field"),
> depending on how the field changed in the past.
> Such a system is called **hysteretic**.
![[alternating-current#Ferroelectric Hysteresis]]
timestamped/2025-12-02_10-57-00.md
+28
View File
@@ -0,0 +1,28 @@
---
id:
aliases: []
title:
tags:
- type/timestamped
dg-publish: true
---
# 2025-12-02 10:57:??
### Set Notation Example
Let $A$ and $B$ be sets
sharing some but not all elements.
* $A \cap B \neq \varnothing$:
"The intersection of $A$ and $B$ is nonempty"
(They share at least one element).
* $A \not\subseteq B$:
"$A$ is not a subset of $B$"
($A$ has at least one element not in $B$).
Equivalent to $A \setminus B \neq \varnothing$.
* $B \not\subseteq A$:
"$B$ is not a subset of $A$"
($B$ has at least one element not in $A$).
Equivalent to $B \setminus A \neq \varnothing$.
timestamped/2025-12-02_13-20-00.md
+22
View File
@@ -0,0 +1,22 @@
---
id:
aliases: []
title:
tags:
- type/timestamped
dg-publish: true
---
# 2025-12-02 13:20:??
### Panel Schedule Relationship Diagram
#### Sections
A panelboard with multiple sections
may or may not have multiple schedules.
`PANEL A1 SEC 1`
#### Typical Schedules
Schedules may be typical of multiple panelboards
`PANEL H(2-6)`
timestamped/2025-12-03_15-54-22.md
+2 -2
View File
@@ -7,14 +7,14 @@ tags:
- destiny/permanent
- status/draft
- type/timestamped
- topic/estimating
- topic/transparency
dg-publish: true
---
# 2025-12-03 15:54:22
## Excluding Vs. Ignoring Project Requirements
#topic/estimating #topic/transparency
There is a distinct difference between _excluding_ and _ignoring_ requirements.
If, before award, you communicate to the customer
timestamped/2025-12-10_10-45-19.md
+3 -2
View File
@@ -7,14 +7,15 @@ tags:
- destiny/permanent
- status/draft
- type/timestamped
- occupational/takeoff
- topic/ambiguity
- topic/transparency
dg-publish: true
---
# 2025-12-10 10:45:19
## ConEst Lighting Controls Meeting Notes
#occupational/takeoff #topic/ambiguity #topic/transparency
Related: [[lighting-controls-takeoff]]
### Minutes
timestamped/2025-12-16_09-20-52.md
+13
View File
@@ -0,0 +1,13 @@
---
id:
aliases: []
title:
tags:
- type/timestamped
dg-publish: true
---
# 2025-12-16 09:20:52
[Probability Management](https://www.probabilitymanagement.org/)
[Handbook of Decision Analysis | Wiley Online Books](https://onlinelibrary.wiley.com/doi/book/10.1002/9781118515853)
timestamped/2025-12-16_20-04-00.md
+13
View File
@@ -0,0 +1,13 @@
---
id:
aliases: []
title:
tags:
- type/timestamped
dg-publish: true
---
# 2025-12-16 20:04:??
### Metalog Distributions
[Metalog Distributions]http://www.metalogdistributions.com/home.html)
timestamped/2025-12-17_05-39-00.md
+45
View File
@@ -0,0 +1,45 @@
---
id:
aliases: []
title:
tags:
- type/timestamped
dg-publish: true
---
# 2025-12-17 05:39:??
One aspect of estimating that I find most interesting,
but that is criminally understudied,
is the effect of building dimensions
(footprint shape, floor area, stories, height)
on total cost.
Unfortunately, lack of interest in the subject extends beyond estimating.
Discourse on spatial data seems to fall into one of two bins:
* civil engineering
* n-dimensional mathematics[^1]
neither are readily applicable to building construction.
[^1]: worse still, the "space" studied in such disciplines is
[vector space](https://en.wikipedia.org/wiki/Vector_space)
where "distance" is a measure of similarity
and physical geometry is rarely considered.
Of the two, pure math would be be preferred---
being generally more rigorous---
but the first bin far outweighs the second.
See the difference in content from
[geostatistics](https://en.wikipedia.org/wiki/Geostatistics)
to the conceivably far more broad
[spatial statistics](https://en.wikipedia.org/wiki/Spatial_statistics).
> [!quote] [Geographic data and information](https://en.wikipedia.org/wiki/Geographic_data_and_information)
> **Spatial data** or **spatial information** is broader class of data
> whose geometry is relevant
> but it is not necessarily [georeferenced](https://en.wikipedia.org/wiki/Georeferenced "Georeferenced"),
> such as in computer-aided design (CAD),
> see [geometric modeling](https://en.wikipedia.org/wiki/Geometric_modeling "Geometric modeling").
### Ambiguity
New Note: [[ambiguity]]
2025-12-17.md → timestamped/2025-12-17_12-32-00.md
+3 -47
View File
@@ -1,58 +1,14 @@
---
id:
aliases: []
title: 2025-12-17
title:
tags:
- authorship/original
- destiny/permanent
- status/draft
- type/periodic/daily
- type/timestamped
- topic/ambiguity
dg-publish: true
---
# 2025-12-17
# 2025-12-17 05:39:??
One aspect of estimating that I find most interesting,
but that is criminally understudied,
is the effect of building dimensions
(footprint shape, floor area, stories, height)
on total cost.
Unfortunately, lack of interest in the subject extends beyond estimating.
Discourse on spatial data seems to fall into one of two bins:
* civil engineering
* n-dimensional mathematics[^1]
neither are readily applicable to building construction.
[^1]: worse still, the "space" studied in such disciplines is
[vector space](https://en.wikipedia.org/wiki/Vector_space)
where "distance" is a measure of similarity
and physical geometry is rarely considered.
Of the two, pure math would be be preferred---
being generally more rigorous---
but the first bin far outweighs the second.
See the difference in content from
[geostatistics](https://en.wikipedia.org/wiki/Geostatistics)
to the conceivably far more broad
[spatial statistics](https://en.wikipedia.org/wiki/Spatial_statistics).
> [!quote] [Geographic data and information](https://en.wikipedia.org/wiki/Geographic_data_and_information)
> **Spatial data** or **spatial information** is broader class of data
> whose geometry is relevant
> but it is not necessarily [georeferenced](https://en.wikipedia.org/wiki/Georeferenced "Georeferenced"),
> such as in computer-aided design (CAD),
> see [geometric modeling](https://en.wikipedia.org/wiki/Geometric_modeling "Geometric modeling").
### Ambiguity
New Note: [[ambiguity]]
# 2025-12-17 12:32:??
#topic/ambiguity
A while ago I heard a minor coding influencer lament
that frameworks, packages, and tools
often have ridiculous sounding names[^2]
timestamped/2025-12-18_08-32-18.md
+11
View File
@@ -0,0 +1,11 @@
---
id:
aliases: []
title:
tags:
- type/timestamped
dg-publish: true
---
# 2025-12-18 08:32:18
[[uncertainty-in-construction-estimating]]
timestamped/2025-12-18_10-38-00.md
+18
View File
@@ -0,0 +1,18 @@
---
id:
aliases: []
title:
tags:
- type/timestamped
- topic/meta
dg-publish: true
---
# 2025-12-18 10:38:??
I definitively think my new approach
of putting nascent ideas in [[periodic-notes|daily notes]]
rather than separate fleeting notes
is superior.
The unfortunate reality is I'll never look at most of them again,
so better that they don't crowd out my main notes.
2025-12-18.md → timestamped/2025-12-18_14-18-00.md
+3 -36
View File
@@ -1,32 +1,11 @@
---
id:
aliases: []
title: 2025-12-18
title:
tags:
- authorship/original
- destiny/permanent
- status/draft
- type/periodic/daily
- type/timestamped
dg-publish: true
---
# 2025-12-18
# 2025-12-18 08:32:18
[[uncertainty-in-construction-estimating]]
# 2025-12-18 10:38:??
#topic/meta
I definitively think my new approach
of putting nascent ideas in [[periodic-notes|daily notes]]
rather than separate fleeting notes
is superior.
The unfortunate reality is I'll never look at most of them again,
so better that they don't crowd out my main notes.
# 2025-12-18 14:18:??
### Estimating Golf
@@ -52,16 +31,4 @@ whether organization historicals are freely available
or must be questioned like project details.
The most interesting part of this problem is choosing when to stop,
since it requires one to estimate their certainty of their estimate.
# 2025-12-18 15:22:??
PDI has moved up the schedule to transition to Accubid Anywhere
and will be signing a contract with Trimble in late January.
[Drawer AI | Automated Electrical Takeoff & Estimating](https://drawer.ai/)
# 2025-12-18 15:30:??
[Kip (unit) - Wikipedia](https://en.wikipedia.org/wiki/Kip_\(unit\))
[Construction Cost Estimating](https://www.quantity-takeoff.com/index.htm)
since it requires one to estimate their certainty of their estimate.
timestamped/2025-12-18_15-22-00.md
+14
View File
@@ -0,0 +1,14 @@
---
id:
aliases: []
title:
tags:
- type/timestamped
dg-publish: true
---
# 2025-12-18 15:22:??
PDI has moved up the schedule to transition to Accubid Anywhere
and will be signing a contract with Trimble in late January.
[Drawer AI | Automated Electrical Takeoff & Estimating](https://drawer.ai/)
timestamped/2025-12-18_15-30-00.md
+12
View File
@@ -0,0 +1,12 @@
---
id:
aliases: []
title:
tags:
- type/timestamped
dg-publish: true
---
# 2025-12-18 15:30:??
[Kip (unit) - Wikipedia](https://en.wikipedia.org/wiki/Kip_\(unit\))
[Construction Cost Estimating](https://www.quantity-takeoff.com/index.htm)
timestamped/2025-12-19_10-44-00.md
+15
View File
@@ -0,0 +1,15 @@
---
id:
aliases: []
title:
tags:
- type/timestamped
- occupational/takeoff
dg-publish: true
---
# 2025-12-19 10:44:??
> [!quote] Art Baldwin 2025-12-19, in reference to Howard University East Towers (pp.)
> When using PVC slab box assemblies where substantial insulation
> (e.g mineral wool, spray foam) is to be applied,
> add extension rings to compensate for the thickness
2025-12-19.md → timestamped/2025-12-19_10-44-01.md
+3 -22
View File
@@ -1,33 +1,14 @@
---
id:
aliases: []
title: 2025-12-19
title:
tags:
- authorship/original
- destiny/permanent
- status/draft
- type/periodic/daily
- type/timestamped
- occupational/takeoff
dg-publish: true
---
# 2025-12-19
# 2025-12-19 06:22:??
[[music-theory-as-code]]
# 2025-12-19 10:44:??
#occupational/takeoff
> [!quote] Art Baldwin 2025-12-19, in reference to Howard University East Towers (pp.)
> When using PVC slab box assemblies where substantial insulation
> (e.g mineral wool, spray foam) is to be applied,
> add extension rings to compensate for the thickness
# 2025-12-19 10:44:??
#occupational/takeoff
This week (2025w51)
William Bonn, as part of [[units-takeoff]] for Howard University East Towers,
used an `Area` "Typical - Unit Balconies" for `Phase` "UNIT - RESIDENTIAL" takeoff.
timestamped/2026-01-02_10-10-18.md
+17
View File
@@ -0,0 +1,17 @@
---
id:
aliases: []
title:
tags:
- type/timestamped
dg-publish: true
---
# 2026-01-02 10:10:18
### Harborside Plaza 4
#### TODO
* [ ] [[electrical-takeoff|Electrical]]
* [x] [[telecom-takeoff#Backbone Riser|Telecom Backbone]]
* [x] [[distributed-antenna-systems-takeoff|DAS]]
2026-01-02.md → timestamped/2026-01-02_19-21-00.md
+2 -17
View File
@@ -1,26 +1,11 @@
---
id:
aliases: []
title: 2026-01-02
title:
tags:
- authorship/original
- destiny/permanent
- status/draft
- type/periodic/daily
- type/timestamped
dg-publish: true
---
# 2026-01-02
# 2026-01-02 10:10:18
### Harborside Plaza 4
#### TODO
* [ ] [[electrical-takeoff|Electrical]]
* [x] [[telecom-takeoff#Backbone Riser|Telecom Backbone]]
* [x] [[distributed-antenna-systems-takeoff|DAS]]
# 2026-01-02 19:21:??
Without apparent prompt I was reminded of a practical joke
timestamped/2026-01-06_07-47-00.md
+20
View File
@@ -0,0 +1,20 @@
---
id:
aliases: []
title:
tags:
- type/timestamped
dg-publish: true
---
# 2026-01-06 07:47:??
### _Let Them Theory_ Theory
1. Person habitually engages in toxic behavior
which they consciously believe to be benevolent
2. Person recognizes that when they stop engaging in said toxic behavior,
others appreciate it
3. Person feels that they are doing a service
by not engaging in said toxic behavior
2026-01-06.md → timestamped/2026-01-06_10-00-00.md
+3 -37
View File
@@ -1,29 +1,11 @@
---
id:
aliases: []
title: 2026-01-06
title:
tags:
- authorship/original
- destiny/permanent
- status/draft
- type/periodic/daily
- type/timestamped
dg-publish: true
---
# 2026-01-06
# 2026-01-06 07:47:??
### _Let Them Theory_ Theory
1. Person habitually engages in toxic behavior
which they consciously believe to be benevolent
2. Person recognizes that when they stop engaging in said toxic behavior,
others appreciate it
3. Person feels that they are doing a service
by not engaging in said toxic behavior
# 2026-01-06 10:00:??
Paraphrased Teams conversation with a peer
@@ -107,20 +89,4 @@ If I had a job where some were significantly more full than others
I _might_ do something similar,
but I'd probably name them
"... 1-Section, ~25% Fill"/"... 1-Section, ~75% Fill" instead.
But that's a lot of mental overhead.
# 2026-01-06 10:57:??
Tracking contractor growth by project square footage
rather than contract value dollars.
Account for market shifts and regional differences.
Problematic for other than new residential construction.
Do you count site area?
Out of contract building area for renovations?
Maybe the sum of in-contract building area and other areas prorated somehow.
Seems imminently gameable.
See [[incentives#Perverse Incentive]]
and [[estimating-culture#Incentives]].
But that's a lot of mental overhead.
timestamped/2026-01-06_10-57-00.md
+23
View File
@@ -0,0 +1,23 @@
---
id:
aliases: []
title:
tags:
- type/timestamped
dg-publish: true
---
# 2026-01-06 10:57:??
Tracking contractor growth by project square footage
rather than contract value dollars.
Account for market shifts and regional differences.
Problematic for other than new residential construction.
Do you count site area?
Out of contract building area for renovations?
Maybe the sum of in-contract building area and other areas prorated somehow.
Seems imminently gameable.
See [[incentives#Perverse Incentive]]
and [[estimating-culture#Incentives]].
timestamped/2026-01-07_06-41-00.md
+26
View File
@@ -0,0 +1,26 @@
---
id:
aliases: []
title:
tags:
- type/timestamped
dg-publish: true
---
# 2026-01-07 06:41:??
> [!quote] _The Shadow of the Torturer_, Chapter 17: "The Challenge"
> No intellect is needed to see those figures who wait beyond the void of death---
> every child is aware of them, blazing with glories dark or bright,
> wrapped in authority older than the universe.
> They are the stuff of our earliest dreams, as of our dying visions.
> Rightly we feel our lives guided by them,
> and rightly too we feel how little we matter to them,
> the builders of the unimaginable,
> the fighters of wars beyond the totality of existence.
>
> The difficulty lies in learning that we ourselves encompass forces equally great.
> We say, "I will," and "I will not," and imagine ourselves
> (though we obey the orders of some prosaic person every day) our own masters,
> when the truth is that our masters are sleeping.
> One wakes within us and we are ridden like beasts,
> though the rider is but some hitherto unguessed part of ourselves.
timestamped/2026-01-07_10-03-00.md
+12
View File
@@ -0,0 +1,12 @@
---
id:
aliases: []
title:
tags:
- type/timestamped
dg-publish: true
---
# 2026-01-07 10:03:??
At Ace, "residential" always meant single-family/duplex construction,
but I think now we were the outliers.
timestamped/2026-01-07_10-05-00.md
+23
View File
@@ -0,0 +1,23 @@
---
id:
aliases: []
title:
tags:
- type/timestamped
dg-publish: true
---
# 2026-01-07 10:05:??
See [[pdi-breakdowns#Location]].
I have---for some time now---
been trying to figure out the purpose of the non-system breakdowns.
[[location-vs-scope]]
Perhaps there is another dichotomy
in that an estimator may use the area classifications of the design
or according to their own understanding of each term.
For lack of a better example,
whether a "101 - KITCHEN", without provisions for cooking,
would be broken down under "Kitchen".
timestamped/2026-01-07_10-42-00.md
+48
View File
@@ -0,0 +1,48 @@
---
id:
aliases: []
title:
tags:
- type/timestamped
dg-publish: true
---
# 2026-01-07 10:42:??
When I got to work today Art admonished a fellow estimator
for not uploading _all_ of a project's drawings,
even those they did not intend to take off, to Trimble Connect.
Art suggested that the estimator should upload all the drawings,
but only add them to LiveCount as needed.
I take issue with the suggestion on principle
since doing so would not benefit the estimator or their senior
(if they aren't added, the estimator can do nothing with them),
but would require not-insignificant effort.
Effort that would ultimately benefit no one:---
Trimble Connect's ham-fisted approach to version control
means that the fewer times it must be used, the better.
> I'm currently dealing with the headache of an estimate
> where such caution was not applied.
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,
fighting with Trimble Connect as they would be,
I suspect is even less.
> On my current project, after trying in vain to play by Trimble's rules,
> I started by deleting all the drawings I could
> (those without takeoff associated with them)
> then reuploaded the revised set.
> I'm confident that this would be the dominant strategy.
***
It's curious to me that the possibility of scope revisions
doesn't seem to be at the front of every estimator's mind
when doing takeoff or considering process changes,
like it was for my mentors and peers at Ace.
timestamped/2026-01-07_12-13-00.md
+37
View File
@@ -0,0 +1,37 @@
---
id:
aliases: []
title:
tags:
- type/timestamped
- occupational
- topic/estimating
- topic/organization
dg-publish: true
---
# 2026-01-07 12:13:??
Just now Jorge admonished another peer
for using insulated wire for pool bonding,
his rational was flawed beyond saving
(something about the difference between bonding and grounding),
but stemmed from a frustratingly common misunderstanding
that our Accubid assemblies are intended to be an accurate list
of the material to be installed.
They are not.
If they were intended to be accurate,
there would need to be several times as many.
They are a compromise between accuracy and estimator effort.
It should be assumed that for common scope,
at least one assembly should be acceptable as-is.
Pool bonding is required for at least a quarter of our jobs.
We have no bonding assemblies with bare wire.
Therefore it must be assumed that it was determined
that it would be acceptable to represent bare wire bonding with insulated wire items,
because otherwise it would be necessary to have double the assemblies,
or to expect estimators to substitute each size of wire
everywhere bare was necessary.
See [[realism-vs-instrumentalism]].
timestamped/2026-01-07_16-03-00.md
+20
View File
@@ -0,0 +1,20 @@
---
id:
aliases: []
title:
tags:
- type/timestamped
- occupational
- topic/estimating
- topic/organization
dg-publish: true
---
# 2026-01-07 16:03:??
There is a palpable animosity for [[pdi-estimating#Bid Estimating|Bid]]
in [[pdi-estimating#Construction Estimating (ConEst)|ConEst]],
stemming---I believe---from an lack of buy-in on Bid's part.
Their lack is easily explained by their [[estimating-culture#Incentives|incentive structure]]:
Since throughput is systematically prioritized over accuracy,
ConEst has a strictly antagonistic role
because it slows down the bid process.
2026-01-08.md → timestamped/2026-01-08_13-33-34.md
+2 -7
View File
@@ -1,16 +1,11 @@
---
id:
aliases: []
title: 2026-01-08
title:
tags:
- authorship/original
- destiny/permanent
- status/draft
- type/periodic/daily
- type/timestamped
dg-publish: true
---
# 2026-01-08
# 2026-01-08 13:33:34
### 2100 Crystal Drive Takeoff Review
timestamped/2026-01-09_10-00-03.md
+53
View File
@@ -0,0 +1,53 @@
---
id:
aliases: []
title:
tags:
- type/timestamped
dg-publish: true
---
# 2026-01-09 10:00:03
### 2100 Crystal Drive
`#600 ? WHITE ?` had incorrect sort codes.
#### Lighting Control
I took off lighting per plans (E510)
in spite of proposal stating "local control".
Will have to be changed.
#### Labor Factor
Fire Alarm
Switchgear
Feeders
Subfeeds
Corridors
Amenity
Retail
Units
#### Fixtures
> [!failure]
> Several fixtures were erroneously based on NM cable.
I built some fixtures with \#12/3 in areas with emergency lighting
to be an unswitched hot.
Joel is having me change them to \#12/2.
#### Units
> [!failure]
> One unit type typical was missing `Area` quantities.
> Another had no takeoff.
#### Labor Plan
$$
\mathbb{E}\left[\frac{\text{Hours Per Unit}}{\text{Openings Per Unit}}\right] \approx .75~\text{Hours Per Opening}
$$
High Rise .110--.120 hr/sqft
timestamped/2026-01-09_12-00-00.md
+27
View File
@@ -0,0 +1,27 @@
---
id:
aliases: []
title:
tags:
- type/timestamped
dg-publish: true
---
# 2026-01-09 12:00:??
$$
\begin{gather*}
\frac{146097}{400} = 365.2425~\text{Days Per Year} \
\frac{20871}{400} = 52.1775~\text{Weeks Per Year} \
\frac{6957}{1600} = 4.348125~\text{Weeks Per Month}
\end{gather*}
$$
$$
\frac{365.2425~\text{Days Per Year}}{7~\text{Days Per Week}}
= 52.1775~\text{Weeks Per Year}
$$
$$
\frac{52.1775~\text{Weeks Per Year}}{12~\text{Months Per Year}}
= 4.348125~\text{Weeks Per Month}
$$
timestamped/2026-01-09_14-45-00.md
+23
View File
@@ -0,0 +1,23 @@
---
id:
aliases: []
title:
tags:
- type/timestamped
dg-publish: true
---
# 2026-01-09 14:45:??
[[bid-price-modeling]]
Suppose a true cost model,
accounting for all relevant information available at time $t$.
$C(t)$ returns a distribution whose [scale](https://en.wikipedia.org/wiki/Scale_parameter)
decreases with $t$, and $C(0)$ maps to a single value.
$t>0$ is time until the final payment.
> ![250](https://upload.wikimedia.org/wikipedia/commons/thumb/8/89/Log-normal-pdfs.png/960px-Log-normal-pdfs.png)
>
> Figure: lognormal distributions with the same [location](https://en.wikipedia.org/wiki/Location_parameter)
> varied by [scale](https://en.wikipedia.org/wiki/Scale_parameter).
timestamped/2026-01-09_16-28-00.md
+27
View File
@@ -0,0 +1,27 @@
---
id:
aliases: []
title:
tags:
- type/timestamped
dg-publish: true
---
# 2026-01-09 16:28:??
### Occam's razor
> [!info] Also Known As
> * the principle of parsimony
> * the law of parsimony
recommends searching for explanations constructed with the smallest possible set of elements.
Attributed to William of Ockham, 14th-century English philosopher and theologian.
> _Entia non sunt multiplicanda praeter necessitatem_
> ("Entities must not be multiplied beyond necessity")
> "Of two competing theories, the simpler explanation is to be preferred."
> [!quote] [[klugman-et-al_2019_loss-models#4.2 The Role of Parameters]]
> The principle of parsimony states that the simplest model
> that adequately reflects reality should be used.
timestamped/2026-01-11_09-00-00.md
+15
View File
@@ -0,0 +1,15 @@
---
id:
aliases: []
title:
tags:
- type/timestamped
dg-publish: true
---
# 2026-01-11 09:00:??
[[2026-01-09#2026-01-09 14:45]]
[[bid-price-modeling]]
[[decrease-in-sigma]]
2026-01-11.md → timestamped/2026-01-11_11-00-00.md
+2 -15
View File
@@ -1,24 +1,11 @@
---
id:
aliases: []
title: 2026-01-11
title:
tags:
- authorship/original
- destiny/permanent
- status/draft
- type/periodic/daily
- type/timestamped
dg-publish: true
---
# 2026-01-11
# 2026-01-11 09:00:??
[[2026-01-09#2026-01-09 14:45]]
[[bid-price-modeling]]
[[decrease-in-sigma]]
# 2026-01-11 11:00:??
![[favorite-quotes#"It Takes an Engineer to Build a Bridge that Barely Stands"]]
timestamped/2026-01-12_10-00-00.md
+4 -2
View File
@@ -1,11 +1,13 @@
---
id: 2026-01-12T10:00:00-05:00
title: 2026-01-12 10:00:??
tags:
- type/timestamped
- occupational
dg-publish: true
---
# 2026-01-12 10:00:??
#occupational
### ECH3 Executed Contract Revision WBS
For Executed Contract Revisions, Bid GP% must be maintained.
timestamped/2026-01-12_10-42-30.md
+4 -2
View File
@@ -1,11 +1,13 @@
---
id: 2026-01-12T10:42:30-05:00
title: 2026-01-12 10:42:30
tags:
- type/timestamped
- occupational
dg-publish: true
---
# 2026-01-12 10:42:30
#occupational
### Woodbrook Executed Contract Revision Takeoff Check
#### Unit Dishwasher/Disposal
timestamped/2026-01-12_12-23-00.md
+4 -2
View File
@@ -1,11 +1,13 @@
---
id: 2026-01-12T12:23:00-05:00
title: 2026-01-12 12:23:??
tags:
- type/timestamped
- occupational
dg-publish: true
---
# 2026-01-12 12:23:??
#occupational
Travelling with Brian Smarslok and Joel Jansen on [[2026-01-15]]
to visit [[#Woodbury Heights|an awarded project]] in New Jersey.
Flying from TPA to PHL, departure @ 7:00AM.
timestamped/2026-01-12_13-02-00.md
+4 -23
View File
@@ -1,31 +1,12 @@
---
id: 2026-01-12T13:02:00-05:00
title: 2026-01-12 13:02:??
tags:
- type/timestamped
- topic/construction
dg-publish: true
---
# 2026-01-12 13:02:??
#topic/construction
**Dry utilities:** utilities other than "wet" utilities (water, sewer, stormwater),
namely power, data, and natural gas.
# 2026-01-12 13:02:??
#occupational
Joel attributes the [[#GP Variance|apparent variance]] to
1. missed Polaris lugs for feeders for one building,
2. insufficient budget for equipment rental, and
3. upfront costs already paid (construction is 50% complete).
He also said that operations accused ConEst
of providing insufficient length for subfeeds,
which he said was true,
but not to the extent accused
(only ~600ft missed total).
The award WBS shows $32,382 for equipment rental
I'm dubious of all these explanations,
but I don't have another one.
I can't find the ConEst folder or Accubid file.
timestamped/2026-01-12_13-02-01.md
+20
View File
@@ -0,0 +1,20 @@
# 2026-01-12 13:02:??
#occupational
Joel attributes the [[#GP Variance|apparent variance]] to
1. missed Polaris lugs for feeders for one building,
2. insufficient budget for equipment rental, and
3. upfront costs already paid (construction is 50% complete).
He also said that operations accused ConEst
of providing insufficient length for subfeeds,
which he said was true,
but not to the extent accused
(only ~600ft missed total).
The award WBS shows $32,382 for equipment rental
I'm dubious of all these explanations,
but I don't have another one.
I can't find the ConEst folder or Accubid file.
timestamped/2026-01-13_11-28-14.md
+1 -2
View File
@@ -7,12 +7,11 @@ tags:
- destiny/permanent
- status/draft
- type/timestamped
- occupational
dg-publish: true
---
# 2026-01-13 11:28:14
#occupational
### 2100 Crystal Drive ConEst Manager Review
#### Josh's Review Order
timestamped/2026-01-14_13-27-20.md
+1 -2
View File
@@ -7,12 +7,11 @@ tags:
- destiny/permanent
- status/draft
- type/timestamped
- occupational
dg-publish: true
---
# 2026-01-14 13:27:20
#occupational
Follow-up to [[2026-01-13#Lighting Control]]
Conversation between Joel Jansen and Christian Pereiro
timestamped/2026-01-15_08-11-10.md
+13
View File
@@ -0,0 +1,13 @@
---
id:
aliases: []
title:
tags:
- type/timestamped
dg-publish: true
---
# 2026-01-15 08:11:10
Follow-up to [[2026-01-12#2026-01-12 12:23|2026-01-12 12:23]]
Left Apartment at 05:30, at terminal around 06:10.
timestamped/2026-01-15_08-15-00.md
+12
View File
@@ -0,0 +1,12 @@
---
id:
aliases: []
title:
tags:
- type/timestamped
dg-publish: true
---
# 2026-01-15 08:15:??
[[2025-11-13#2025-11-13 08:19]]
I spoke to a peer about this yesterday.
timestamped/2026-01-19_11-57-39.md
+3
View File
@@ -1,6 +1,9 @@
---
id: 2026-01-19T11:57:39-05:00
title: 2026-01-19 11:57:39
tags:
- type/timestamped
dg-publish: true
---
# 2026-01-19 11:57:39
timestamped/2026-01-19_12-32-00.md
+5 -2
View File
@@ -1,11 +1,14 @@
---
id: 2026-01-19T12:32:00-05:00
title: 2026-01-19 12:32:??
tags:
- type/timestamped
- topic/construction
- topic/estimating
dg-publish: true
---
# 2026-01-19 12:32:??
#topic/construction #topic/estimating
Real example of [[location-vs-scope]]:
450-460 James Robertson Parkway Phase II (fka James Roberston Pkwy Mixed Use Development)
timestamped/2026-01-19_18-13-00.md
+3
View File
@@ -1,6 +1,9 @@
---
id: 2026-01-19T18:13:00-05:00
title: 2026-01-19 18:13:??
tags:
- type/timestamped
dg-publish: true
---
# 2026-01-19 18:13:??
timestamped/2026-01-20_09-09-12.md
+3
View File
@@ -1,6 +1,9 @@
---
id: 2026-01-20T09:09:12-05:00
title: 2026-01-20 09:09:12
tags:
- type/timestamped
dg-publish: true
---
# 2026-01-20 09:09:12

Some files were not shown because too many files have changed in this diff Show More