vault backup: 2026-03-30 22:54:00
This commit is contained in:
@@ -51,7 +51,7 @@ See [[UNLICENSE]] for legalese to that effect.
|
||||
> it is not my intent to violate any laws enforcing it.
|
||||
>
|
||||
> [[UNLICENSE]] applies only to files and portions of files that are my own original work.
|
||||
> It does not grant rights to reproduce, modify, or redistribute third-party content included herein.
|
||||
> It does not grant rights to reproduce, modify, or redistribute third-party content included herein.
|
||||
> Users are responsible for complying with the licenses of any third-party material.
|
||||
|
||||
## Attribution
|
||||
|
||||
+10
-10
@@ -48,21 +48,21 @@ global = {
|
||||
mel = { %\global
|
||||
c8\2 <g\3 c\2 dis'\1>16 g'16\5
|
||||
\deadNote c16\2 g16\3 <g\3 c\2 dis'\1>16 g'16\5 |
|
||||
|
||||
|
||||
ais16\3( g16\3 ) g16\3 g'16\5
|
||||
f16\4( c16\4 ) g16\3 g'16\5 |
|
||||
|
||||
|
||||
ais8\3 <g\3 c\2 dis'\1>16 g'16\5
|
||||
\deadNote c16\2 ais16\3 <ais\3 c\2 dis'\1>16 g'16\5 |
|
||||
|
||||
|
||||
c8\2 <g\3 c\2 dis'\1>16 g'16\5
|
||||
\deadNote dis'16\1 c16\2 d16\2( dis16\2 ) | \break
|
||||
|
||||
|
||||
|
||||
|
||||
}
|
||||
|
||||
voc = {
|
||||
|
||||
|
||||
}
|
||||
|
||||
lyr = \lyricmode { "
|
||||
@@ -70,17 +70,17 @@ lyr = \lyricmode { "
|
||||
\"You better treat me right
|
||||
I'll eat up all o' your cotton
|
||||
Sleep in your grain rail tonight\"
|
||||
|
||||
|
||||
Boll weevil told the farmer
|
||||
\"You don't need no Ford machine
|
||||
I'll eat up all of your cotton
|
||||
Can't buy no gasoline\"
|
||||
|
||||
|
||||
Yonder comes the spider
|
||||
Crawled up and down the wall
|
||||
He must've been going
|
||||
To get his hash's haul
|
||||
|
||||
|
||||
I don't see no water
|
||||
But I'm about to drown
|
||||
I don't see no fire
|
||||
@@ -105,7 +105,7 @@ lyr = \lyricmode { "
|
||||
\global
|
||||
\mel
|
||||
}
|
||||
|
||||
|
||||
\new Staff = "voice" <<
|
||||
\new Voice = "vocal" \with {midiInstrument = "choir oohs"} {
|
||||
\global
|
||||
|
||||
@@ -24,7 +24,7 @@ Buildings["Building A"].GetTaggedLevel("Roof")
|
||||
|
||||
```
|
||||
Buildings["Building A"].GetHeight()
|
||||
```
|
||||
```
|
||||
|
||||
```
|
||||
Buildings["Building A"].GetLevels()[0]
|
||||
|
||||
@@ -38,7 +38,7 @@ is insufficient for [[full-takeoff]].
|
||||
Budget per Unit Count.
|
||||
Compare to Bid Sheet.
|
||||
|
||||
> [!info] Alternate method as described by Joel
|
||||
> [!info] Alternate method as described by [[joel-jansen]]
|
||||
> Takeoff unit risers normally
|
||||
> with Length * 1.5 to cover house panel feeders.
|
||||
|
||||
@@ -54,5 +54,5 @@ See [[switchgear-takeoff#Generator]].
|
||||
|
||||
Budget per Unit Count. Compare to Bid Sheet.
|
||||
|
||||
> [!info] Alternate method as described by Joel
|
||||
> [!info] Alternate method as described by [[joel-jansen]]
|
||||
> Takeoff per [[subfeeds-takeoff]], use average for length.
|
||||
|
||||
+1
-1
@@ -33,7 +33,7 @@ dg-publish: true
|
||||
Worker to Self
|
||||
|
||||
This one is not a big deal to me,
|
||||
beyond
|
||||
beyond
|
||||
%%
|
||||
|
||||
## Cognitive Ergonomics
|
||||
|
||||
+1
-1
@@ -23,7 +23,7 @@ dg-publish: true
|
||||
|
||||
All feeder takeoff descriptions should be prefixed with `<parent> TO <child>`
|
||||
|
||||
> [!cite] Joel Jansen, in reference to Omni Hotels Raleigh (pp.)
|
||||
> [!cite] [[joel-jansen]], in reference to Omni Hotels Raleigh (pp.)
|
||||
> It is acceptable to use typicals for identical feeders
|
||||
> (i.e. meter centers fed from bus plugs)
|
||||
> so long as the typical is in `Area` = "01 - Feeders/Risers ...".
|
||||
|
||||
@@ -50,8 +50,8 @@ not especially consistent with the actual install.
|
||||
> This scope is included here for its similarity in content.
|
||||
> It may be more appropriate in [[electrical-takeoff]]
|
||||
|
||||
> [!quote] Joel Jansen 2026-01-20T16:30 (pp.)
|
||||
> Josh Ford prefers it in electrical, but I'm not concerned.
|
||||
> [!quote] [[joel-jansen]] 2026-01-20T16:30 (pp.)
|
||||
> [[josh-ford]] prefers it in electrical, but I'm not concerned.
|
||||
> So long as it's named "Pool Bonding" it's fine.
|
||||
|
||||
1. * `Area` = _Contentious_
|
||||
|
||||
+1
-1
@@ -39,7 +39,7 @@ and a micrometer would be silly.
|
||||
> [!quote] George E. P. Box, British statistician
|
||||
> All models are wrong, but some are useful.[^1]
|
||||
|
||||
[^1]: > [!quote] [[box-et-al_1987_empirical-model-building#The Use of Approximating Functions]]
|
||||
[^1]: > [!quote] [[box-et-al_1987_empirical-model-building#The Use of Approximating Functions]]
|
||||
> The fact that the polynomial is an approximation
|
||||
> does not necessarily detract from its usefulness
|
||||
> because all models are approximations.
|
||||
|
||||
@@ -16,11 +16,11 @@ dg-publish: true
|
||||
lists 5 major construction types based on fire ratings/materials.
|
||||
|
||||
> [!info] 5-Over-1 Construction ^5-over-1
|
||||
>
|
||||
>
|
||||
> "5-over-1" construction denotes a building
|
||||
> with levels of combustible construction
|
||||
> above levels of non-combustible construction.
|
||||
>
|
||||
>
|
||||
> buildings with two non-combustible levels (5-over-2)
|
||||
> and Type III upper floors (3-over-1)
|
||||
> are also common,
|
||||
|
||||
@@ -301,36 +301,36 @@ and the probability that their answer would be within 10% of the true value.
|
||||
> * Population in the U.S.
|
||||
> * Proportion of population that immigrated to U.S.
|
||||
> * Percentage of U.S immigrants from Argentina
|
||||
>
|
||||
>
|
||||
> ##### Circulation of TV Guide
|
||||
>
|
||||
> * Households in the U.S.
|
||||
> * Proportion of households with a TV
|
||||
> * Proportion of households with a TV receiving TV Guide
|
||||
>
|
||||
>
|
||||
> ##### Circumference of 50¢ coin
|
||||
>
|
||||
> * Diameter in inches of a 50¢ coin
|
||||
> * Number of pieces of string the length of the diameter needed to wrap around circumference
|
||||
>
|
||||
>
|
||||
> ##### Bushels of wheat
|
||||
>
|
||||
> * Population of the world
|
||||
> * Number of bushels of wheat consumed per person per year
|
||||
> * Proportion of wheat wasted per year
|
||||
>
|
||||
>
|
||||
> ##### Bank failures in 1933
|
||||
>
|
||||
> * Current population of the U.S.
|
||||
> * Population of U.S. in 1933 as a proportion of current population
|
||||
> * Number of customers for a typical bank
|
||||
> * Proportion of banks failed in 1933
|
||||
>
|
||||
>
|
||||
> ##### U.S. presidents
|
||||
>
|
||||
> * Number of years U.S. has had presidents
|
||||
> * Number of years the average president holds office
|
||||
>
|
||||
>
|
||||
> ##### Men's pants
|
||||
>
|
||||
> * Number of men in the U.S.
|
||||
@@ -338,20 +338,20 @@ and the probability that their answer would be within 10% of the true value.
|
||||
> * Number of women in the U.S.
|
||||
> * Number of pairs of men's pants the average woman buys each year
|
||||
> * Proportion of men's pants manufactured in the U.S. that are sold to U.S. customers
|
||||
>
|
||||
>
|
||||
> ##### Athletic shoes
|
||||
>
|
||||
> * Population of the U.S.
|
||||
> * Proportion of the population that wears athletic shoes
|
||||
> * Pairs of athletic shoes each wearer buys per year
|
||||
> * Proportion of athletic shoes manufactured in U.S. that are sold to U.S. customers
|
||||
>
|
||||
>
|
||||
> ##### Auto accidents
|
||||
>
|
||||
> * Number of people in the U.S. of driving age
|
||||
> * Proportion of people of driving age who drive
|
||||
> * Number of accidents the average driver has per year
|
||||
>
|
||||
>
|
||||
> ##### Area of U.S.
|
||||
>
|
||||
> * Distance in miles from San Francisco, CA to Washington, D.C.
|
||||
@@ -557,7 +557,7 @@ In practical problems, of course, one could simply use the actual value.
|
||||
In their study of decomposition, Henrion et al. (1993) gave the U.S. population value to the subjects.
|
||||
|
||||
> ##### Fig. 1. Calibration of probability assessments that estimated answer is within 10% of true answer.
|
||||
>
|
||||
>
|
||||
> %% ![[figure_1.jpeg]] %%
|
||||
|
||||
The issue of 'how extreme is extreme' has not been resolved.
|
||||
|
||||
+4
-2
@@ -13,8 +13,10 @@ dg-publish: true
|
||||
# Me-isms
|
||||
|
||||
* (when misunderstood) "No, no, no."
|
||||
* certainly
|
||||
* "certainly"
|
||||
* "ought", "ought not"
|
||||
|
||||
## Others-isms
|
||||
|
||||
* "... and stuff."
|
||||
* "Also too ..."
|
||||
*
|
||||
@@ -214,16 +214,16 @@ shall be based on Table 310.16 as appropriately modified by 310.12.
|
||||
* (a) Termination provisions of equipment for circuits rated 100 amperes or less,
|
||||
or marked for 14 AWG through 1 AWG conductors,
|
||||
shall be used only for one of the following:
|
||||
|
||||
|
||||
* (1) Conductors rated 60°C (140°F).
|
||||
|
||||
* (2) Conductors with higher temperature ratings,
|
||||
provided the ampacity of such conductors
|
||||
is determined based on the 60°C (140°F) ampacity of the conductor size used.
|
||||
|
||||
|
||||
* (3) Conductors with higher temperature ratings
|
||||
if the equipment is listed and identified for use with such conductors.
|
||||
|
||||
|
||||
* (4) For motors marked with design letters B, C, or D,
|
||||
conductors having an insulation rating of 75°C (167°F) or higher
|
||||
shall be permitted to be used,
|
||||
|
||||
@@ -100,14 +100,14 @@ in excess of the temperature specified for the type of insulation involved.
|
||||
shall comply with the installation requirements
|
||||
of [[nfpa-70_334_nm-cable#Part II. Installation|Part II of Article 334]],
|
||||
excluding [[nfpa-70_334_nm-cable#334.80 Ampacity.|334.80]].
|
||||
|
||||
|
||||
* (2) Where more than two Type SE cables
|
||||
containing two or more current-carrying conductors in each cable
|
||||
are installed in contact with thermal insulation, caulk, or sealing foam
|
||||
without maintaining spacing between cables,
|
||||
the ampacity of each conductor shall be adjusted
|
||||
in accordance with [[nfpa-70_310_conductors_for_general_wiring#Table 310.15(C)(1) Adjustment Factors for More Than Three Current-Carrying Conductors|Table 310.15(C)(1)]].
|
||||
|
||||
|
||||
* (3) For Type SE cable with ungrounded conductor sizes 10 AWG and smaller,
|
||||
where installed in contact with thermal insulation,
|
||||
the ampacity shall be in accordance with 60°C (140°F) conductor temperature rating.
|
||||
@@ -122,7 +122,7 @@ in excess of the temperature specified for the type of insulation involved.
|
||||
where installed as exterior wiring,
|
||||
shall be installed in accordance with Part I of Article 225.
|
||||
The cable shall be supported in accordance with 334.30.
|
||||
|
||||
|
||||
* (2) Type USE cable installed as underground feeder and branch circuit cable
|
||||
shall comply with Part II of Article 340.
|
||||
|
||||
|
||||
@@ -414,21 +414,20 @@ All 15- and 20-ampere, 125- and 250-volt nonlocking-type receptacles in the area
|
||||
* (8) Assisted living facilities
|
||||
|
||||
> [!info] Informational Note No. 1:
|
||||
> This requirement would include receptacles identified as 5-15, 5-20, 6-15, and 6-20 in ANSI/NEMA WD 6-
|
||||
2016, Wiring Devices — Dimensional Specifications.
|
||||
> This requirement would include receptacles identified as 5-15, 5-20, 6-15, and 6-20 in ANSI/NEMA WD 6-2016, Wiring Devices — Dimensional Specifications.
|
||||
|
||||
> [!info] Informational Note No. 2:
|
||||
> Assisted living facilities are Institutional Use Group I-1 per IBC 2015.
|
||||
|
||||
> [!important] Exception to (1), (2), (3), (4), (5), (6), (7) and (8):
|
||||
> Receptacles in the following locations shall not be required to be tamper resistant:
|
||||
>
|
||||
>
|
||||
> * (1) Receptacles located more than 1.7 m (5 1⁄2 ft) above the floor
|
||||
>
|
||||
>
|
||||
> * (2) Receptacles that are part of a luminaire or appliance
|
||||
>
|
||||
>
|
||||
> * (3) A single receptacle, or a duplex receptacle for two appliances, located within the dedicated space for each appliance that, in normal use, is not easily moved from one place to another and that is cord-and-plug-connected in accordance with 400.10(A)(6), (A)(7), or (A)(8)
|
||||
>
|
||||
>
|
||||
> * (4) Nongrounding receptacles used for replacements as permitted in 406.4(D)(2)(a)
|
||||
|
||||
### 406.13 Single-Pole Separable-Connector Type.
|
||||
@@ -458,17 +457,17 @@ The use of single-pole separable connectors shall be performed by a qualified pe
|
||||
* (2) Line connectors are of the listed sequential-interlocking type so that load connectors are connected in the following sequence and that disconnection is in the reverse sequence:
|
||||
|
||||
* (a) Equipment grounding conductor connection
|
||||
|
||||
|
||||
* (b) Grounded circuit conductor connection, if provided
|
||||
|
||||
|
||||
* (c) Ungrounded conductor connection
|
||||
|
||||
* (3) A caution notice that complies with 110.21(B) is provided on the equipment employing single-pole separable connectors, adjacent to the line connectors, indicating that connections are to be performed in the following sequence and that disconnection is in the reverse sequence:
|
||||
|
||||
* (a) Equipment grounding conductor connectors
|
||||
|
||||
|
||||
* (b) Grounded circuit-conductor connectors, if provided
|
||||
|
||||
|
||||
* (c) Ungrounded conductor connectors
|
||||
|
||||
> [!info] Informational Note:
|
||||
|
||||
@@ -75,7 +75,7 @@ Where ground-fault circuit interrupter protection for personnel is supplied by p
|
||||
|
||||
> [!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.
|
||||
@@ -90,7 +90,7 @@ The fixed wiring methods shall be metal raceways, flexible metal raceways, nonme
|
||||
|
||||
> [!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
|
||||
|
||||
@@ -103,16 +103,16 @@ A box, conduit body, or other enclosure, with a cover installed, shall be requir
|
||||
> 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.
|
||||
@@ -181,13 +181,13 @@ Ground-fault circuit-interrupter protection for personnel.
|
||||
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
|
||||
|
||||
@@ -293,7 +293,7 @@ Fire pump supply conductors on the load side of the final disconnecting means an
|
||||
|
||||
> [!info] Informational Note No. 1:
|
||||
> Fire-resistive cables are tested to ANSI/UL 2196-2017, Standard for Fire Test for Circuit Integrity of Fire-Resistive Power, Instrumentation, Control and Data Cables.
|
||||
|
||||
|
||||
> [!info] Informational Note No. 2:
|
||||
> The listing organization provides information for fire-resistive cable systems on proper installation requirements to maintain the fire rating.
|
||||
|
||||
|
||||
+4
-1
@@ -15,4 +15,7 @@ A package manager is a service that curates software
|
||||
## For Linux
|
||||
|
||||
On Linux machines,
|
||||
package managers are the
|
||||
package managers are the defacto means
|
||||
for installing any software.
|
||||
|
||||
## For Windows
|
||||
|
||||
@@ -229,7 +229,7 @@ delivers high-quality results and takes initiative.
|
||||
|
||||
### Comment
|
||||
|
||||
> [quote] Joel Jansen
|
||||
> [quote] [[joel-jansen]]
|
||||
> Zane has been a great addition to our team in these short few months.
|
||||
> He's shown genuine enthusiasm while learning,
|
||||
> asks the right questions, and has picked up our PDI standards quickly.
|
||||
|
||||
@@ -42,7 +42,7 @@ Clear **Field** for other than the project's [[pdi-building-types|building type]
|
||||
* **Cost/Unit** <- 8.5
|
||||
* **Duration** <- 0.01
|
||||
|
||||
%% Approved by Joel Jansen 2026-02-20 %%
|
||||
%% Approved by [[joel-jansen]] 2026-02-20 %%
|
||||
|
||||
### Garden Style, High Rise
|
||||
|
||||
|
||||
+1
-1
@@ -126,7 +126,7 @@ Does not include finished restaurants
|
||||
* `Area` = "XX - Level XX Retail Building"
|
||||
* `Phase` = "Office Space"
|
||||
|
||||
> [!quote] Joel Jansen to William Bonn 2025-12-05 (pp.)
|
||||
> [!quote] [[joel-jansen]] to William Bonn 2025-12-05 (pp.)
|
||||
> PDI Accubid `Phase` "Office Space"
|
||||
> is normally used for core & shell retail office space
|
||||
|
||||
|
||||
+1
-1
@@ -40,7 +40,7 @@ dg-publish: true
|
||||
| Code | Description |
|
||||
| ---- | -------------------- |
|
||||
| 200 | rough |
|
||||
| 300 | trim |
|
||||
| 300 | trim |
|
||||
| 400 | rough wire and cable |
|
||||
|
||||
9. Some items will autofill when you fill out the "Accubid Extension Totals" table on the right
|
||||
|
||||
@@ -37,9 +37,9 @@ Paste the completed template content to the body of a new email.
|
||||
* Bid Estimator or Associate Estimator (if applicable)
|
||||
|
||||
**CC:**
|
||||
* Senior Construction Estimator %% Joel %%
|
||||
* ConEst Manager (Josh Ford)
|
||||
* Director of Estimating (Corwin Fluit)
|
||||
* Senior Construction Estimator %% [[joel-jansen]] %%
|
||||
* ConEst Manager ([[josh-ford]])
|
||||
* Director of Estimating ([[corwin-fluit]])
|
||||
* Jessalyn Williams
|
||||
* Other ConEst Estimators (if applicable)
|
||||
|
||||
|
||||
@@ -23,6 +23,14 @@ believed to be implied by the context.
|
||||
One must write with clarity sufficient for an outsider to understand,
|
||||
because the writer will eventually be the outsider.
|
||||
|
||||
In this note and elsewhere
|
||||
I strongly associate the concept of PKM
|
||||
and effective note-taking in general
|
||||
with the use of [hypertext](https://en.wikipedia.org/wiki/Hypertext).
|
||||
Notes you don't reference are useless and,
|
||||
short of reading your entire collection every few weeks,
|
||||
liberal use of links is the best way to increase availability.
|
||||
|
||||
## Getting Started
|
||||
|
||||
Getting started with PKM will feel so intimidating that you'll want to give up,
|
||||
@@ -35,6 +43,35 @@ so you may leave some of those videos feeling like you need to pick up boulderin
|
||||
It speaks to the highly personal nature of PKM that, of these hundreds,
|
||||
there is no consensus larger than two on best practice.
|
||||
|
||||
### My Advice
|
||||
|
||||
#### Write Literally Everything
|
||||
|
||||
Plain text is too cheap to have high standards.
|
||||
Write dumb ideas, write about trivial conversations,
|
||||
write anything you can make two sentences out of.
|
||||
|
||||
When you don't yet know your goals for your vault
|
||||
this is how you figure out how it can help you,
|
||||
but you should never stop doing this.
|
||||
|
||||
I recommend setting up timestamped notes
|
||||
to make this workflow as easy as possible.
|
||||
Naming topics is one of the hardest parts of PKM
|
||||
and the more it can be avoided the better
|
||||
as far as I'm concerned.
|
||||
|
||||
#### Use Version Control
|
||||
|
||||
In service to my preferred method of moving fast and breaking stuff,
|
||||
[[git]] allows me to make massive changes to my vault,
|
||||
including deleting entire files that have gone stale,
|
||||
without fear of regret,
|
||||
because what's lost can always be recovered.
|
||||
|
||||
To get the most benefit out of git,
|
||||
commit your changes at least once a day.
|
||||
|
||||
## See Also
|
||||
|
||||
* [[digital-gardens]]
|
||||
|
||||
+2
-2
@@ -61,7 +61,7 @@ tags:
|
||||
## Chef's Notes
|
||||
|
||||
This recipe has very low [[utility]].
|
||||
It is easily the most complex of all my
|
||||
|
||||
It is easily the most complex of all I've curated,
|
||||
but it has very little to offer in reward.
|
||||
|
||||
%%
|
||||
+1
-1
@@ -32,7 +32,7 @@ Seek additional clarification.
|
||||
|
||||
## Breakdowns
|
||||
|
||||
> [!quote] Joel Jansen 2026-02-02 12:10, while reviewing Howard University East Towers (pp.)
|
||||
> [!quote] [[joel-jansen]] 2026-02-02 12:10, while reviewing Howard University East Towers (pp.)
|
||||
> Match breakdowns of the relevant system,
|
||||
> i.e. don't change breakdowns after taking off
|
||||
> the assembly to be sleeved.
|
||||
|
||||
@@ -55,7 +55,7 @@ dg-publish: true
|
||||
|
||||
2. ==1" to 1-1/2" EMT riser==
|
||||
|
||||
* [ ] TODO: Establish Power Monitoring riser takeoff procedure with Joel and document
|
||||
* [ ] TODO: Establish Power Monitoring riser takeoff procedure with [[joel-jansen]] and document
|
||||
|
||||
## Generator
|
||||
|
||||
|
||||
@@ -116,7 +116,7 @@ of varying importance.
|
||||
|
||||
### #topic/transparency
|
||||
|
||||
### #topic/hobbies
|
||||
### #topic/hobbies
|
||||
|
||||
### #topic/other
|
||||
|
||||
@@ -238,7 +238,7 @@ Items of `#authorship/other` are not my own work.
|
||||
They may be of one source or a collection of several
|
||||
without significant commentary.
|
||||
|
||||
### #authorship/other-for-now
|
||||
### #authorship/other-for-now
|
||||
|
||||
Items of `#authorship/other-for-now`
|
||||
will eventually be [[#authorship/original]],
|
||||
|
||||
+1
-1
@@ -9,4 +9,4 @@ tags:
|
||||
- topic/hobbies/cooking
|
||||
- type/recipe
|
||||
---
|
||||
#
|
||||
#
|
||||
|
||||
@@ -27,5 +27,5 @@ timestamp based on my teams message to Joel.
|
||||
> * Coupling Method: Compression coupling or Setscrew coupling.
|
||||
> Setscrew couplings with only single screw per conduit are unacceptable.
|
||||
|
||||
> [!quote] Joel Jansen via Microsoft Teams @ 2025-10-15 09:33 AM
|
||||
> [!quote] [[joel-jansen]] via Microsoft Teams @ 2025-10-15 09:33 AM
|
||||
> use set screw 🙂
|
||||
|
||||
@@ -15,7 +15,9 @@ dg-publish: true
|
||||
|
||||
### Belle Meade Director Review
|
||||
|
||||
[[belle-meade-plaza]]
|
||||
Estimating Director Review for [[belle-meade-plaza]]
|
||||
lead by [[corwin-fluit]],
|
||||
attended by [[joel-jansen]] and myself.
|
||||
|
||||
#### Takeoff Review
|
||||
|
||||
@@ -59,7 +61,7 @@ Joel to add these.
|
||||
|
||||
> [!info] Circuits per Raceway
|
||||
> Corwin stated that---assuming no overriding specification---
|
||||
> up to 6 circuits in a raceway are permissible.
|
||||
> up to 6 circuits per raceway are permissible.
|
||||
|
||||
##### Lighting Control
|
||||
|
||||
|
||||
@@ -11,7 +11,7 @@ dg-publish: true
|
||||
# 2025-11-10 11:14:??
|
||||
|
||||
I was updating my notes,
|
||||
filling in gaps in scripts based on Joel's,
|
||||
filling in gaps in scripts based on [[joel-jansen]]'s,
|
||||
when I noticed a strange paragraph:
|
||||
|
||||
> [!quote] `OneNote`/`Joel Take-off`/`Misc. Notes`
|
||||
@@ -29,7 +29,7 @@ when I noticed a strange paragraph:
|
||||
> >
|
||||
> > 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
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@ tags:
|
||||
- authorship/original
|
||||
- destiny/permanent
|
||||
- status/draft
|
||||
- topic/hobbies/shorthand
|
||||
- topic/hobbies/shorthand
|
||||
- topic/hobbies/writing
|
||||
- type/periodic/timestamped
|
||||
dg-publish: true
|
||||
|
||||
@@ -18,7 +18,7 @@ dg-publish: true
|
||||
|
||||
%%
|
||||
Transcription of notes
|
||||
taken while reviewing Elliot St. with Joel Jansen.
|
||||
taken while reviewing Elliot St. with [[joel-jansen]].
|
||||
%%
|
||||
|
||||
Adorne USB Heating Designation was built with standard device.
|
||||
|
||||
@@ -12,7 +12,7 @@ dg-publish: true
|
||||
[[2025w51|This week]]
|
||||
William Bonn, as part of [[units-takeoff]] for Howard University East Towers,
|
||||
used an `Area` "Typical - Unit Balconies" for `Phase` "UNIT - RESIDENTIAL" takeoff.
|
||||
Our senior Joel Jansen approved of the method.
|
||||
Our senior [[joel-jansen]] approved of the method.
|
||||
|
||||
I'd like to use the method tentatively for takeoff strictly typical of all units
|
||||
(e.g. master switches, MSDE's, etc.),
|
||||
|
||||
@@ -66,7 +66,7 @@ I would, but I usually extract the schedules anyway
|
||||
so I just use the actual average.
|
||||
|
||||
> Thank you for that.
|
||||
> Joel wagged his finger at me about missing terms this morning---
|
||||
> [[joel-jansen|Joel]] wagged his finger at me about missing terms this morning---
|
||||
> I wanted to see how it's preferred.
|
||||
> I was told terms are captured by feeders/mech connections
|
||||
> and have never added them to panelboards.
|
||||
|
||||
@@ -13,7 +13,8 @@ dg-publish: true
|
||||
|
||||
## 2100 Crystal Drive Takeoff Review
|
||||
|
||||
[[2100-crystal-drive]]
|
||||
Notes on my takeoff for [[2100-crystal-drive]]
|
||||
as reviewed with [[joel-jansen]]:
|
||||
|
||||
### Generators
|
||||
|
||||
|
||||
@@ -10,7 +10,8 @@ dg-publish: true
|
||||
|
||||
## 2100 Crystal Drive Closeout
|
||||
|
||||
[[2100-crystal-drive]]
|
||||
Notes on [[2100-crystal-drive]]
|
||||
as reviewed with [[joel-jansen]]:
|
||||
|
||||
### Extension
|
||||
|
||||
@@ -50,6 +51,8 @@ Joel is having me change them to \#12/2.
|
||||
|
||||
### Labor Plan
|
||||
|
||||
Relevant to [[pdi-labor-plan]]:
|
||||
|
||||
$$
|
||||
\mathbb{E}\left[\frac{\text{Hours Per Unit}}{\text{Openings Per Unit}}\right] \approx .75~\text{Hours Per Opening}
|
||||
$$
|
||||
|
||||
@@ -17,4 +17,4 @@ Drawings show 2 separate duplex receptacles for dishwasher and disposal
|
||||
Takeoff used `DW & DISPOSAL DUAL CIR - ...`,
|
||||
which includes only one receptacle.
|
||||
|
||||
According to Joel this takeoff is correct for the scenario.
|
||||
According to [[joel-jansen]] this takeoff is correct for the scenario.
|
||||
|
||||
@@ -9,7 +9,7 @@ dg-publish: true
|
||||
---
|
||||
# 2026-01-12 12:23:??
|
||||
|
||||
Travelling with Brian Smarslok and Joel Jansen on [[2026-01-15]]
|
||||
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.
|
||||
We'll be meeting with the developer, [Greystar](https://www.greystar.com/).
|
||||
|
||||
@@ -11,7 +11,7 @@ dg-publish: true
|
||||
---
|
||||
# 2026-01-12 13:02:??
|
||||
|
||||
Joel attributes the [[#GP Variance|apparent variance]]
|
||||
[[joel-jansen]] attributes the [[#GP Variance|apparent variance]]
|
||||
of [[woodbury-heights]] to
|
||||
1. missed Polaris lugs for feeders for one building,
|
||||
2. insufficient budget for equipment rental, and
|
||||
|
||||
@@ -15,6 +15,10 @@ dg-publish: true
|
||||
|
||||
### 2100 Crystal Drive ConEst Manager Review
|
||||
|
||||
ConEst Manager Review for [[2100-crystal-drive]]
|
||||
lead by [[josh-ford]],
|
||||
attended by [[joel-jansen]] and myself.
|
||||
|
||||
#### Josh's Review Order
|
||||
|
||||
1. Backwards from Final Pricing through rest of closeout,
|
||||
|
||||
@@ -14,7 +14,7 @@ dg-publish: true
|
||||
|
||||
Follow-up to [[2026-01-13_11-28-14#Lighting Control]]
|
||||
|
||||
> [!quote] Conversation between Joel Jansen and Christian Pereiro regarding lighting control for [[2100-crystal-drive]]:
|
||||
> [!quote] Conversation between [[joel-jansen]] and Christian Pereiro regarding lighting control for [[2100-crystal-drive]]:
|
||||
>
|
||||
> **Joel:** "It was sold as local."
|
||||
>
|
||||
|
||||
@@ -16,7 +16,7 @@ dg-publish: true
|
||||
|
||||
#### Quote
|
||||
|
||||
> [!quote] Joel Jansen 2026-01-15 13:27 (pp.)
|
||||
> [!quote] [[joel-jansen]] 2026-01-15 13:27 (pp.)
|
||||
> I'd rather have an accurate budget than an accurate BOM.
|
||||
|
||||
#### Context
|
||||
|
||||
@@ -33,7 +33,7 @@ function Import-Markdown {
|
||||
catch {
|
||||
throw "no YAML conversion module installed. Try ``Install-Module powershell-yaml``."
|
||||
}
|
||||
|
||||
|
||||
$content = Get-Content -Path $Path -Raw
|
||||
$pattern = [Regex]'(?ms)^---\s*(.*?)\s*---\s*(.*)$'
|
||||
$match = $pattern.Match($content)
|
||||
@@ -45,7 +45,7 @@ function Import-Markdown {
|
||||
$frontmatter = ''
|
||||
$body = $content
|
||||
}
|
||||
|
||||
|
||||
return [pscustomobject]@{
|
||||
frontmatter = $frontmatter | ConvertFrom-Yaml
|
||||
body = $body
|
||||
|
||||
@@ -16,13 +16,13 @@ dg-publish: true
|
||||
## Sleeving Takeoff Breakdown Direction
|
||||
|
||||
Updated [[sleeving-takeoff#Breakdowns]]
|
||||
per clarification with Joel.
|
||||
per clarification with [[joel-jansen]].
|
||||
Previous direction below.
|
||||
|
||||
> * `Area` = "01 - Feeders/Risers ..."
|
||||
> * `Phase` = "Feeders"
|
||||
> * `System` = "FRR - Feeders and Risers"
|
||||
>
|
||||
>
|
||||
> For all sleeving, regardless of application.
|
||||
|
||||
I feel certain I received this from someone I trust
|
||||
|
||||
@@ -26,7 +26,7 @@ Anything else?
|
||||
How do they rank in importance?
|
||||
|
||||
Why are other departments so confused about ConEst's purpose?
|
||||
(Ops stakeholder auditing CBOM to Joel: "missing screws")
|
||||
(Ops stakeholder auditing CBOM to [[joel-jansen]]: "missing screws")
|
||||
If we don't know, and Ops doesn't know, who does?
|
||||
That is, who defines our purpose?
|
||||
|
||||
|
||||
@@ -27,23 +27,23 @@ representing project scale buckets.
|
||||
|
||||
> [!example] [T-Shirt Sizing in Agile --- Project Management Pathways](https://www.projectmanagementpathways.com/project-management-articles/tshirt-sizing-in-agile-projects)
|
||||
> * **XS (1-2 days):** Simple UI changes or minor bug fixes
|
||||
>
|
||||
>
|
||||
> Example: "Update button color on checkout page"
|
||||
>
|
||||
> * **S (2-3 days):** Feature enhancements with minimal complexity
|
||||
>
|
||||
>
|
||||
> Example: "Add product sorting by price"
|
||||
>
|
||||
> * **M (5-7 days):** Features requiring moderate integration
|
||||
>
|
||||
>
|
||||
> Example: "Implement basic search filters"
|
||||
>
|
||||
> * **L (8-10 days):** Complex features affecting multiple components
|
||||
>
|
||||
>
|
||||
> Example: "Create shopping cart functionality"
|
||||
>
|
||||
> * **XL (2+ weeks):** Major features requiring breaking down
|
||||
>
|
||||
>
|
||||
> Example: "Implement payment gateway integration"
|
||||
|
||||
The buckets chosen should be wide enough
|
||||
|
||||
@@ -20,7 +20,7 @@ yearly: "[[2026]]"
|
||||
## Mechanical Connection Selection
|
||||
|
||||
Relevant to [[electrical-takeoff]],
|
||||
sourced from Joel Jansen's OneNote Takeoff Notes "Mechanical Connections".
|
||||
sourced from [[joel-jansen]]'s OneNote Takeoff Notes "Mechanical Connections".
|
||||
|
||||
Ben says he has never used any PVC assembly except .../`PVC - ...`.
|
||||
|
||||
|
||||
@@ -20,15 +20,17 @@ yearly: "[[2026]]"
|
||||
|
||||
## Hampton Roads Navy - Norfolk: Director Review
|
||||
|
||||
[[hampton-roads-navy_norfolk]]
|
||||
Director Review of [[hampton-roads-navy_norfolk]].
|
||||
|
||||
### Dramatis Personae
|
||||
|
||||
Director of ConEst: Corwin Fluit
|
||||
Director of ConEst: [[corwin-fluit|Corwin Fluit]]
|
||||
|
||||
Bid Estimator: Christian Pereiro
|
||||
Bid Estimator: [[christian-pereiro|Christian Pereiro]]
|
||||
|
||||
Senior ConEst Estimator: Joel Jansen
|
||||
Senior ConEst Estimator: [[joel-jansen|Joel Jansen]]
|
||||
|
||||
ConEst Estimator: [[zane-meyers|Zane Meyers]]
|
||||
|
||||
### Lighting Control
|
||||
|
||||
|
||||
@@ -17,7 +17,7 @@ yearly: "[[2026]]"
|
||||
---
|
||||
# 2026-02-20 09:39:20
|
||||
|
||||
A few minutes ago I asked Joel about [[units-takeoff|unit takeoff]],
|
||||
A few minutes ago I asked [[joel-jansen]] about [[units-takeoff|unit takeoff]],
|
||||
specifically if I should provide a GFI for each bathroom
|
||||
even if the receptacles are on the same circuit,
|
||||
which he confirmed.
|
||||
|
||||
@@ -20,13 +20,14 @@ yearly: "[[2026]]"
|
||||
|
||||
## Fire Alarm Wiring Methods
|
||||
|
||||
[[fire-alarm-takeoff]]
|
||||
direction for [[fire-alarm-takeoff]]
|
||||
as confirmed by [[joel-jansen]]:
|
||||
|
||||
> [!quote] Zane Meyers @ 09:35 to Joel Jansen via Teams regarding [[1990-k-street]]
|
||||
> From our Pre-Takeoff email:
|
||||
>
|
||||
>
|
||||
> > **Fire Alarm:** Devices PVC in-slab, Risers EMT.
|
||||
>
|
||||
>
|
||||
> Still PVC for Retail shell and Amenity, Building areas with dropped ceilings?
|
||||
|
||||
### Regarding Retail
|
||||
|
||||
@@ -52,7 +52,7 @@ except for the total absence of [skeuomorphism](https://en.wikipedia.org/wiki/Sk
|
||||
interfaces designed to resemble their physical counterparts.
|
||||
|
||||
> ![[level-selector.jpg|400]]
|
||||
>
|
||||
>
|
||||
> Mock-up of a level selection interface,
|
||||
> perhaps for quickly creating typicals.
|
||||
|
||||
|
||||
@@ -22,7 +22,7 @@ yearly: "[[2026]]"
|
||||
|
||||
## Trainee Development Scorecard
|
||||
|
||||
[[2026-02-20]]
|
||||
reviewed with [[joel-jansen]] [[2026-02-20]]:
|
||||
|
||||
### Skill: WBS
|
||||
|
||||
|
||||
@@ -64,7 +64,7 @@ Calculate Factor and apply to column **Slab-Deck**
|
||||
| --------------- | -------------------------------- |
|
||||
| BLDG - CORRIDOR | Slab-Deck, All Others |
|
||||
| BLDG - BOH | Slab-Deck, All Others |
|
||||
| GARAGE | Slab-Deck, All Others |
|
||||
| GARAGE | Slab-Deck, All Others |
|
||||
| UNITS | Slab-Deck, Rough, Trim, Fixtures |
|
||||
| SUBFEEDS | Slab-Deck, All Others |
|
||||
| GEAR | Not adjusted |
|
||||
|
||||
@@ -19,7 +19,7 @@ yearly: "[[2026]]"
|
||||
|
||||
## Values & Competencies
|
||||
|
||||
Reviewed in-person with Joel Jansen [[2026-03-03]].
|
||||
Reviewed in-person with [[joel-jansen]] [[2026-03-03]].
|
||||
|
||||
Regarding the scoring,
|
||||
Joel stated that in past years,
|
||||
@@ -33,7 +33,7 @@ the ratings were much more confusing
|
||||
|
||||
I take no issue with the ratings Joel gave,
|
||||
all the topics I feel strongly enough about to argue
|
||||
were scored accurately as far as
|
||||
were scored accurately as far as
|
||||
|
||||
### Integrity
|
||||
|
||||
@@ -232,7 +232,7 @@ which would make rating much easier to give,
|
||||
however it would be somewhat redundant with other values.
|
||||
%%
|
||||
|
||||
### Decision Quality
|
||||
### Decision Quality
|
||||
|
||||
Makes decisions with confidence, balancing short- and long-term goals.
|
||||
Demonstrates a growing ability to make decisions independently
|
||||
@@ -333,7 +333,7 @@ going through the documents and filling out the OneNote,
|
||||
...
|
||||
%%
|
||||
|
||||
### Technical
|
||||
### Technical
|
||||
|
||||
Handles routine technical tasks
|
||||
with growing confidence and minimal support.
|
||||
|
||||
@@ -112,7 +112,7 @@ and respond with any questions or comments.
|
||||
"Transformer windings shall be manufacturer's standard design,
|
||||
copper or aluminum conductor. Bussing shall be copper."
|
||||
_---Spec 262002.5(L) (p. 2296)_
|
||||
|
||||
|
||||
* K-Rating: Only as shown (None shown)
|
||||
_---Spec 262002.5(K) (p. 2295)_
|
||||
|
||||
|
||||
@@ -20,6 +20,7 @@ yearly: "[[2026]]"
|
||||
## Charlotte South End Hotel Spec Interpretation
|
||||
|
||||
Spec interpretation notes for [[charlotte-south-end-hotel]]
|
||||
with clarification by [[joel-jansen]]:
|
||||
|
||||
### EMT Fittings
|
||||
|
||||
@@ -54,7 +55,7 @@ No definition is provided for a liquid-tight flexible non-metallic raceway
|
||||
> in mechanical rooms or where subject to moisture or weather.
|
||||
|
||||
> [!quote] Joel Jansen 2026-03-10 (pp.)
|
||||
>
|
||||
> Assume LFMC.
|
||||
|
||||
[^1]: I feel fairly confident this is erroneous.
|
||||
|
||||
@@ -130,7 +131,7 @@ These are captured as a budget
|
||||
Assuming that this line includes master switches
|
||||
based on sum of quote and switch allowance
|
||||
|
||||
> [!quote] PDR Lutron Lighting Control Quote 2025-12-10, Pricing Summary –Turnkey
|
||||
> [!quote] PDR Lutron Lighting Control Quote 2025-12-10, Pricing Summary –Turnkey
|
||||
> Lighting Control: Lutron $ 738,400.00
|
||||
|
||||
### EV Chargers
|
||||
|
||||
@@ -18,7 +18,8 @@ yearly: "[[2026]]"
|
||||
---
|
||||
# 2026-03-18 11:31:07
|
||||
|
||||
Takeoff directive for [[charlotte-south-end-hotel]]:
|
||||
Takeoff directive for [[charlotte-south-end-hotel]]
|
||||
from [[joel-jansen]]:
|
||||
|
||||
## Feeder Length Rounding
|
||||
|
||||
|
||||
@@ -21,7 +21,7 @@ yearly: "[[2026]]"
|
||||
|
||||
## Pre-Takeoff Email Template Meeting
|
||||
|
||||
Meeting lead by Josh Ford
|
||||
Meeting lead by [[josh-ford]]
|
||||
to discuss acceptable use of [[conest-pre-takeoff-email-template]].
|
||||
|
||||
### Topics
|
||||
@@ -30,7 +30,7 @@ to discuss acceptable use of [[conest-pre-takeoff-email-template]].
|
||||
|
||||
Reiterated intent to replace OneNote,
|
||||
however stated that OneNote might (even should)
|
||||
be used to track
|
||||
be used to track
|
||||
|
||||
Intent is too provide information to the bid team
|
||||
potentially to be qualified in future bids.
|
||||
@@ -44,7 +44,7 @@ an area the OneNote is poor in.
|
||||
|
||||
***
|
||||
|
||||
Direction from Aaron to improve turnaround
|
||||
Direction from [[aaron-permuy]] to improve turnaround
|
||||
while maintaining standards
|
||||
including presentability of information;
|
||||
raise issues with missing BPM tasks ASAP
|
||||
@@ -56,9 +56,9 @@ hounding Bid at the very end.
|
||||
> > > They (whoever _They_ is) want Bid to handle more volume,
|
||||
> > > which requires that Bid spend less time on a single estimate,
|
||||
> > > which requires ConEst to pick up slack to maintain the same rigor.
|
||||
> >
|
||||
> >
|
||||
> > Where does this come from?
|
||||
>
|
||||
>
|
||||
> > [!quote] Me @ 15:53
|
||||
> > More baseless speculation.
|
||||
|
||||
@@ -73,7 +73,7 @@ Intent is to have conversations before contract
|
||||
There will be bad estimates, bad proposals,
|
||||
but ConEst's role is to prevent PDI _from making bad deals_
|
||||
|
||||
> [!quote] Joel Jansen, pp.
|
||||
> [!quote] [[joel-jansen]], pp.
|
||||
> Similar could be said by Ops about ConEst.
|
||||
> ~~They have more time than us~~
|
||||
|
||||
|
||||
@@ -22,7 +22,7 @@ yearly: "[[2026]]"
|
||||
|
||||
Follow-up to [[2026-03-19_09-00-43]]
|
||||
|
||||
> [!quote] Josh Ford @ 2026-03-20 09:10 via Outlook
|
||||
> [!quote] [[josh-ford]] @ 2026-03-20 09:10 via Outlook
|
||||
> Good Morning, Team,
|
||||
>
|
||||
> Following up from our meeting yesterday.
|
||||
@@ -43,7 +43,7 @@ Follow-up to [[2026-03-19_09-00-43]]
|
||||
>
|
||||
> * We will not use this exact template for Design Builds (remove spec portion of email),
|
||||
> Data Centers, Stadiums or Large commercial projects (We will customize based on SOW)
|
||||
>
|
||||
>
|
||||
> For the tasks, I will set up a separate meeting to go over that portion,
|
||||
> feel free to leave that portion off the email until after that training.
|
||||
>
|
||||
|
||||
@@ -34,7 +34,7 @@ between the quantities listed in:
|
||||
> s \overset {\leftarrow}{=} b(s)
|
||||
> \end{gather}
|
||||
> $$
|
||||
>
|
||||
>
|
||||
> $b(s)$ causes $s$ which in turn causes $a(s)$: $b(s) \overset {\rightarrow}{=} a(s)$
|
||||
|
||||
[Bayesian networks](https://en.wikipedia.org/wiki/Bayesian_network)
|
||||
|
||||
@@ -22,7 +22,7 @@ yearly: "[[2026]]"
|
||||
|
||||
Relevant to [[fire-alarm-takeoff]],
|
||||
while reviewing my takeoff for [[1990-k-street]]
|
||||
Joel had to fix the assemblies I used for unit smoke detectors.
|
||||
[[joel-jansen]] had to fix the assemblies I used for unit smoke detectors.
|
||||
|
||||
Unit plans show combo smoke/CO detectors in all cases,
|
||||
but bedroom smokes are to be smoke only
|
||||
|
||||
@@ -18,7 +18,7 @@ yearly: "[[2026]]"
|
||||
---
|
||||
# 2026-03-23 12:48:49
|
||||
|
||||
Joel asked me to give feedback on the project engineer
|
||||
[[joel-jansen]] asked me to give feedback on the project engineer
|
||||
I've had shadowing and helping me on [[charlotte-south-end-hotel]].
|
||||
|
||||
They've been exceptionally engaged,
|
||||
|
||||
@@ -29,7 +29,7 @@ which appears to be older (1800's)
|
||||
and may be the origin of its use in drafting.
|
||||
|
||||
> **match-line**
|
||||
>
|
||||
>
|
||||
> a line drawn on a pattern
|
||||
> denoting where the textile pattern must be aligned
|
||||
> to ensure it is visually continuous across seam lines.
|
||||
|
||||
@@ -33,7 +33,7 @@ Strictly speaking, requirements for communications wiring
|
||||
(governed by [[nfpa-70_national-electric-code#^ch8|NEC Chapter 8]])
|
||||
are minimal.
|
||||
|
||||
> [!quote] Joel Jansen 2026-03-24 (pp.)
|
||||
> [!quote] [[joel-jansen]] 2026-03-24 (pp.)
|
||||
> If rough-in for Telecom or a Low Voltage system is included,
|
||||
> even if qualified as "free-air per code" or similar,
|
||||
> always provide backboxes and conduit stub-ups for outlets
|
||||
|
||||
@@ -21,7 +21,8 @@ yearly: "[[2026]]"
|
||||
|
||||
## BPM Tasks Meeting
|
||||
|
||||
Regarding [[conest-pre-takeoff-email-template#Tasks/Quotes Needed for WBS]]
|
||||
Meeting lead by [[josh-ford]]
|
||||
regarding [[conest-pre-takeoff-email-template#Tasks/Quotes Needed for WBS]]
|
||||
for [[pdi-pre-takeoff-confirmation]]:
|
||||
|
||||
Intent is to reduce WBS turnaround,
|
||||
@@ -45,7 +46,7 @@ and it is not already open (or completed) in BPM.
|
||||
If all necessary tasks are open or completed:
|
||||
"No tasks missing."
|
||||
|
||||
Prompted by Joel,
|
||||
Prompted by [[joel-jansen]],
|
||||
Josh clarified that "... Raceway Design" tasks
|
||||
are not necessary for Low Voltage, Telecom systems,
|
||||
only Public Safety DAS.
|
||||
|
||||
@@ -21,8 +21,8 @@ yearly: "[[2026]]"
|
||||
|
||||
Follow-up to [[2026-03-20_13-44-59#2026-03-20 13:44:59]].
|
||||
|
||||
Comments by Joel Jansen
|
||||
Relevant to my takeoff for [[1990-k-street]]:
|
||||
Comments by [[joel-jansen]]
|
||||
relevant to my takeoff for [[1990-k-street]]:
|
||||
|
||||
### Lighting Control Assemblies
|
||||
|
||||
@@ -34,10 +34,10 @@ but the drawings painted as exact a picture as one could ask for prior to constr
|
||||
|
||||
> Design shows digital control, dimming controlled by occ sensors in stairwells, corridors. \
|
||||
> ---E021 AUTOMATED LIGHTING CONTROL - SEQUENCES OF OPERATIONS
|
||||
>
|
||||
>
|
||||
> Proposal excludes digital lighting control due to lack of information. \
|
||||
> ---Proposal 2026-01-22, Pricing Alternates
|
||||
>
|
||||
>
|
||||
> Spec 260923 - LIGHTING CONTROL DEVICES \
|
||||
> Spec 260936 - MODULAR DIMMING CONTROLS
|
||||
|
||||
|
||||
@@ -21,14 +21,14 @@ yearly: "[[2026]]"
|
||||
## 1990 K Street ConEst Manager Review
|
||||
|
||||
ConEst Manager Review for [[1990-k-street]]
|
||||
lead by Josh Ford and Joel Jansen
|
||||
lead by Josh Ford and [[joel-jansen]]
|
||||
|
||||
### Purpose of ConEst Manager Review
|
||||
|
||||
Josh explains purpose of this review to PE
|
||||
|
||||
Jobs below 12% margin
|
||||
are reviewed further with Corwin Fluitt
|
||||
are reviewed further with [[corwin-fluit]]
|
||||
who is able and authorized
|
||||
to "make judgement calls" on pricing concerns
|
||||
in order to get GP to an acceptable number.
|
||||
|
||||
+1
-1
@@ -60,7 +60,7 @@ require communication systems per
|
||||
> redundant with the standard takeoff described above.
|
||||
> These assemblies can be ignored
|
||||
> unless given specific direction otherwise.
|
||||
> Confirmed by Joel Jansen 2025-12-08 in reference to [[2100-crystal-drive|2100 Crystal Drive]].
|
||||
> Confirmed by [[joel-jansen]] 2025-12-08 in reference to [[2100-crystal-drive|2100 Crystal Drive]].
|
||||
|
||||
`COMMON ASSEMBLIES`/`FIRE ALARM & DAS SYSTEMS`/`COMMUNICATION DEVICES ...`/`...`
|
||||
|
||||
|
||||
+3
-3
@@ -75,7 +75,7 @@ Used in lieu of individual split systems.
|
||||
|
||||
### Dedicated Circuit Receptacles
|
||||
|
||||
> [!quote] Joel Jansen 2025-11-11, pp.
|
||||
> [!quote] [[joel-jansen]] 2025-11-11, pp.
|
||||
>
|
||||
> For N5-15R/N5-20R receptacles serving fixed equipment such as:
|
||||
>
|
||||
@@ -100,7 +100,7 @@ Used in lieu of individual split systems.
|
||||
|
||||
### Dishwasher/Disposal Receptacles
|
||||
|
||||
> [!quote] Joel Jansen 2026-01-12 in Reference to [[woodbrook]] (pp.)[^1]
|
||||
> [!quote] [[joel-jansen]] 2026-01-12 in Reference to [[woodbrook]] (pp.)[^1]
|
||||
> Even when drawings show 2 separate duplex receptacles,
|
||||
> use `DW & DISPOSAL DUAL CIR - ...`,
|
||||
> which includes only one receptacle.
|
||||
@@ -127,7 +127,7 @@ 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_
|
||||
|
||||
### Doorbells
|
||||
|
||||
@@ -124,10 +124,10 @@ may be routed through with special permission.
|
||||
|
||||
[[construction-methods#Post-Tensioned Slab|Post-Tensioned Slab]]
|
||||
|
||||
> [!cite] Joel Jansen 2025-08-15, in reference to [[belle-meade-plaza|Belle Meade Plaza]] (pp.)
|
||||
> [!cite] [[joel-jansen]] 2025-08-15, in reference to [[belle-meade-plaza|Belle Meade Plaza]] (pp.)
|
||||
> No affect on takeoff. Routing in slab still possible.
|
||||
|
||||
> [!cite] Joel Jansen 2025-08-21, in reference to [[belle-meade-plaza|Belle Meade Plaza]] (pp.)
|
||||
> [!cite] [[joel-jansen]] 2025-08-21, in reference to [[belle-meade-plaza|Belle Meade Plaza]] (pp.)
|
||||
> PT slabs do have some affect on takeoff.
|
||||
> 3in conduit can not be run in an 11in PT slab.
|
||||
|
||||
@@ -135,7 +135,7 @@ may be routed through with special permission.
|
||||
|
||||
[[construction-methods#Pan Deck Slab|Pan Deck Slab]]
|
||||
|
||||
> [!cite] Joel Jansen 2025-08-15, in reference to [[belle-meade-plaza|Belle Meade Plaza]] (pp.)
|
||||
> [!cite] [[joel-jansen]] 2025-08-15, in reference to [[belle-meade-plaza|Belle Meade Plaza]] (pp.)
|
||||
> Do not route in slab.
|
||||
|
||||
### MC Cable Overhead
|
||||
|
||||
+7
-7
@@ -18,35 +18,35 @@ tags:
|
||||
|
||||
> [!quote] [_How To Ask Questions The Smart Way_ --- Eric Steven Raymond](http://www.catb.org/~esr/faqs/smart-questions.html)
|
||||
> > [!quote] ["Questions Not To Ask"](http://www.catb.org/~esr/faqs/smart-questions.html#classic)
|
||||
> > **Q:** How can I use X to do Y?
|
||||
> >
|
||||
> > **Q:** How can I use X to do Y?
|
||||
> >
|
||||
> > **A:** If what you want is to do Y,
|
||||
> > you should ask that question without pre-supposing the use of a method
|
||||
> > that may not be appropriate.
|
||||
> > Questions of this form often indicate a person who is not merely ignorant about X,
|
||||
> > but confused about what problem Y they are solving
|
||||
> > and too fixated on the details of their particular situation.
|
||||
>
|
||||
>
|
||||
> > [!quote] ["Describe the goal, not the step"](http://www.catb.org/~esr/faqs/smart-questions.html#goal)
|
||||
> > If you are trying to find out how to do something
|
||||
> > (as opposed to reporting a bug),
|
||||
> > begin by describing the goal.
|
||||
> > Only then describe the particular step towards it
|
||||
> > that you are blocked on.
|
||||
> >
|
||||
> >
|
||||
> > Often, people who need technical help
|
||||
> > have a high-level goal in mind
|
||||
> > and get stuck on what they think is one particular path towards the goal.
|
||||
> > They come for help with the step,
|
||||
> > but don't realize that the path is wrong.
|
||||
> > It can take substantial effort to get past this.
|
||||
> >
|
||||
> >
|
||||
> > **Stupid:** How do I get the color-picker on the FooDraw program
|
||||
> > to take a hexadecimal RGB value?
|
||||
> >
|
||||
> >
|
||||
> > **Smart:** I'm trying to replace the color table on an image with values of my choosing.
|
||||
> > Right now the only way I can see to do this is by editing each table slot,
|
||||
> > but I can't get FooDraw's color picker to take a hexadecimal RGB value.
|
||||
> >
|
||||
> >
|
||||
> > The second version of the question is smart.
|
||||
> > It allows an answer that suggests a tool better suited to the task.
|
||||
Reference in New Issue
Block a user