From 84c8c76ccbdfdbe81c87f457da6b4c58f5970d14 Mon Sep 17 00:00:00 2001 From: Zane Meyers Date: Wed, 25 Feb 2026 08:15:32 -0500 Subject: [PATCH 1/6] vault backup: 2026-02-25 08:15:32 --- 2025-11-10.md | 138 ----------------------------- 2025-11-11.md | 53 ----------- 2025-11-13.md | 63 ------------- 2025-12-02.md | 78 ---------------- 2025-12-16.md | 12 --- 2025-12-17.md | 82 ----------------- 2025-12-18.md | 55 ------------ 2025-12-19.md | 28 ------ 2026-01-02.md | 29 ------ 2026-01-06.md | 114 ------------------------ 2026-01-07.md | 122 ------------------------- 2026-01-08.md | 43 --------- 2026-01-09.md | 102 --------------------- 2026-01-11.md | 58 ------------ 2026-01-15.md | 11 --- fixture-designations.md | 5 +- timestamped/2025-11-10_06-53-00.md | 31 +++++++ timestamped/2025-11-10_10-40-00.md | 8 ++ timestamped/2025-11-10_11-14-00.md | 49 ++++++++++ timestamped/2025-11-10_15-15-00.md | 14 +++ timestamped/2025-11-10_20-00-00.md | 31 +++++++ timestamped/2025-11-11_06-06-00.md | 27 ++++++ timestamped/2025-11-11_14-41-00.md | 24 +++++ timestamped/2025-11-13_00-00-00.md | 0 timestamped/2025-11-13_08-03-00.md | 12 +++ timestamped/2025-11-13_08-19-00.md | 37 ++++++++ timestamped/2025-11-13_20-41-00.md | 11 +++ timestamped/2025-12-02_10-40-00.md | 14 +++ timestamped/2025-12-02_10-57-00.md | 20 +++++ timestamped/2025-12-02_13-20-00.md | 14 +++ timestamped/2025-12-16_09-20-52.md | 5 ++ timestamped/2025-12-16_20-04-00.md | 5 ++ timestamped/2025-12-17_05-39-00.md | 37 ++++++++ timestamped/2025-12-17_12-32-00.md | 43 +++++++++ timestamped/2025-12-18_08-32-18.md | 3 + timestamped/2025-12-18_10-38-00.md | 11 +++ timestamped/2025-12-18_14-18-00.md | 26 ++++++ timestamped/2025-12-18_15-22-00.md | 6 ++ timestamped/2025-12-18_15-30-00.md | 4 + timestamped/2025-12-19_10-44-00.md | 17 ++++ timestamped/2025-12-19_10-44-01.md | 14 +++ timestamped/2026-01-02_10-10-18.md | 9 ++ timestamped/2026-01-02_19-21-00.md | 18 ++++ timestamped/2026-01-06_07-47-00.md | 12 +++ timestamped/2026-01-06_10-00-00.md | 84 ++++++++++++++++++ timestamped/2026-01-06_10-57-00.md | 15 ++++ timestamped/2026-01-07_06-41-00.md | 18 ++++ timestamped/2026-01-07_10-03-00.md | 4 + timestamped/2026-01-07_10-05-00.md | 15 ++++ timestamped/2026-01-07_10-42-00.md | 40 +++++++++ timestamped/2026-01-07_12-13-00.md | 28 ++++++ timestamped/2026-01-07_16-03-00.md | 11 +++ timestamped/2026-01-08_13-33-34.md | 42 +++++++++ timestamped/2026-01-09_10-00-03.md | 45 ++++++++++ timestamped/2026-01-09_12-00-00.md | 19 ++++ timestamped/2026-01-09_14-45-00.md | 15 ++++ timestamped/2026-01-09_16-28-00.md | 19 ++++ timestamped/2026-01-11_09-00-00.md | 7 ++ timestamped/2026-01-11_11-00-00.md | 49 ++++++++++ timestamped/2026-01-15_08-11-10.md | 5 ++ timestamped/2026-01-15_08-15-00.md | 4 + 61 files changed, 926 insertions(+), 989 deletions(-) create mode 100644 timestamped/2025-11-10_06-53-00.md create mode 100644 timestamped/2025-11-10_10-40-00.md create mode 100644 timestamped/2025-11-10_11-14-00.md create mode 100644 timestamped/2025-11-10_15-15-00.md create mode 100644 timestamped/2025-11-10_20-00-00.md create mode 100644 timestamped/2025-11-11_06-06-00.md create mode 100644 timestamped/2025-11-11_14-41-00.md create mode 100644 timestamped/2025-11-13_00-00-00.md create mode 100644 timestamped/2025-11-13_08-03-00.md create mode 100644 timestamped/2025-11-13_08-19-00.md create mode 100644 timestamped/2025-11-13_20-41-00.md create mode 100644 timestamped/2025-12-02_10-40-00.md create mode 100644 timestamped/2025-12-02_10-57-00.md create mode 100644 timestamped/2025-12-02_13-20-00.md create mode 100644 timestamped/2025-12-16_09-20-52.md create mode 100644 timestamped/2025-12-16_20-04-00.md create mode 100644 timestamped/2025-12-17_05-39-00.md create mode 100644 timestamped/2025-12-17_12-32-00.md create mode 100644 timestamped/2025-12-18_08-32-18.md create mode 100644 timestamped/2025-12-18_10-38-00.md create mode 100644 timestamped/2025-12-18_14-18-00.md create mode 100644 timestamped/2025-12-18_15-22-00.md create mode 100644 timestamped/2025-12-18_15-30-00.md create mode 100644 timestamped/2025-12-19_10-44-00.md create mode 100644 timestamped/2025-12-19_10-44-01.md create mode 100644 timestamped/2026-01-02_10-10-18.md create mode 100644 timestamped/2026-01-02_19-21-00.md create mode 100644 timestamped/2026-01-06_07-47-00.md create mode 100644 timestamped/2026-01-06_10-00-00.md create mode 100644 timestamped/2026-01-06_10-57-00.md create mode 100644 timestamped/2026-01-07_06-41-00.md create mode 100644 timestamped/2026-01-07_10-03-00.md create mode 100644 timestamped/2026-01-07_10-05-00.md create mode 100644 timestamped/2026-01-07_10-42-00.md create mode 100644 timestamped/2026-01-07_12-13-00.md create mode 100644 timestamped/2026-01-07_16-03-00.md create mode 100644 timestamped/2026-01-08_13-33-34.md create mode 100644 timestamped/2026-01-09_10-00-03.md create mode 100644 timestamped/2026-01-09_12-00-00.md create mode 100644 timestamped/2026-01-09_14-45-00.md create mode 100644 timestamped/2026-01-09_16-28-00.md create mode 100644 timestamped/2026-01-11_09-00-00.md create mode 100644 timestamped/2026-01-11_11-00-00.md create mode 100644 timestamped/2026-01-15_08-11-10.md create mode 100644 timestamped/2026-01-15_08-15-00.md diff --git a/2025-11-10.md b/2025-11-10.md index 4bc9b85..ad6a93e 100644 --- a/2025-11-10.md +++ b/2025-11-10.md @@ -10,141 +10,3 @@ tags: 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. diff --git a/2025-11-11.md b/2025-11-11.md index 94dc8af..163ce6b 100644 --- a/2025-11-11.md +++ b/2025-11-11.md @@ -10,56 +10,3 @@ tags: 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. diff --git a/2025-11-13.md b/2025-11-13.md index 37b8fde..6028b09 100644 --- a/2025-11-13.md +++ b/2025-11-13.md @@ -10,66 +10,3 @@ tags: 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. diff --git a/2025-12-02.md b/2025-12-02.md index dafac0f..9c50dd3 100644 --- a/2025-12-02.md +++ b/2025-12-02.md @@ -10,81 +10,3 @@ tags: 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 diff --git a/2025-12-16.md b/2025-12-16.md index 7279f64..4063ca0 100644 --- a/2025-12-16.md +++ b/2025-12-16.md @@ -10,15 +10,3 @@ tags: 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) diff --git a/2025-12-17.md b/2025-12-17.md index 0750523..1051981 100644 --- a/2025-12-17.md +++ b/2025-12-17.md @@ -10,85 +10,3 @@ tags: 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] -when, he suggests, they ought to just be called what they do. - -[^2]: `bubble-tea` and `ratatui` - (libraries for creating CLI's) come to my mind - -Unfortunately some people and organizations agree with him, -giving us terms which mean both something very general -and something very specific.[^3] - -[^3]: [[project-management-tm|"Project Management"]] - was my go to example, but weak - because it's difficult for me to articulate - the difference from construction project management - especially to someone unfamiliar with the specifics of either. - -For lack of a better term I've been thinking of this as an SEO problem, -but the bigger problem is that it invites [[ambiguity#Category Mistake|Category Mistake]], -whereby the ignorant listener associates traits unique to the example -to all things that the name could describe. - -I thought to finally write about this problem -while researching [[lighting-controls#Protocols|lighting control protocols]]. -The two most dominant examples: - -* [[lighting-controls#^dali|"Digital Addressable Lighting Interface (DALI)"]] -* [[lighting-controls#^dmx|"Digital Multiplex (DMX)"]] - -while notably different in topology, -could both be described accurately with the other's name. - -> It is possible to avoid this problem -> without the effort necessary to come up with a clever name. -> Just stick an arbitrary, but reasonably unique word -> in front of the generic description. -> A person's name ("John's Digital Addressable Lighting Interface (JDALI)") -> or your favorite animal ("Heron Digital Multiplex (HDMX)") are good options. diff --git a/2025-12-18.md b/2025-12-18.md index 0251f70..8e762c7 100644 --- a/2025-12-18.md +++ b/2025-12-18.md @@ -10,58 +10,3 @@ tags: 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 - -What interests me most in [[construction-estimating]] -is an idea you might call "estimating golf": -the goal is to produce a satisfactory[^1] estimate, -but the estimator can not view the project documents -and must instead ask questions about the job -(answerable in a sentence or less) -of a neutral party ("the reader"). -The estimator fails if the estimate is unsatisfactory[^1], -but otherwise is scored by number of questions asked. - -[^1]: satisfactory in terms of accuracy and precision, - according to the standards of the organization. - a control estimate must be prepared accordingly - by a neutral party ("the control"). - -You could further imagine different brackets -for required accuracy and precision, -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) diff --git a/2025-12-19.md b/2025-12-19.md index 830f054..6ba4e07 100644 --- a/2025-12-19.md +++ b/2025-12-19.md @@ -10,31 +10,3 @@ tags: 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. -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.), -but there is potential for significant efficiency gains -in treating units like panelboards in [[switchgear-takeoff]]: -picking one unit type to be typical of many nearly identical types. diff --git a/2026-01-02.md b/2026-01-02.md index c9557c3..b29b07a 100644 --- a/2026-01-02.md +++ b/2026-01-02.md @@ -10,32 +10,3 @@ tags: 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 -that my fellow apprentice Joe used to play often -that never failed to get a laugh out of me: - -Mid-conversation Joe would stop suddenly, -search in his pockets or tool belt, -pull out a random object (usually his lineman's pliers), -and act as if he had received a phone call on it. -Often the other party had apparently dialed in error, -and Joe would say, "Hello?... Hello?" -before deciding they'd hung up. -Other times he'd step away (only one step) -and have whole conversations. - -Try as I might have, -I could never pull it off like he could. diff --git a/2026-01-06.md b/2026-01-06.md index 4d620d3..3bcf9b3 100644 --- a/2026-01-06.md +++ b/2026-01-06.md @@ -10,117 +10,3 @@ tags: 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 -about [[distribution-designations#Terminations]]. -Peer's messages are in block quotes. - -*** - -> Good morning! -> Do you add branch terminations to panelboards? -> If so, how does your 'distribution' section looks? - -Morning! Yes to the first question, ? to the second - -> As all panelboards on a job don't have the same size/# of terminations, -> I assume you would have a plethora of same size boards in the job, with different terms. -> How do you list them? - -| | Designation | Status | Quantity | -| --- | ----------------------------- | ------ | -------- | -| 1 | Generator - 350kW, Diesel | | 1 | -| 2 | Generator - 2000kW, Diesel | | 1 | -| 3 | ATS - 200A | | 2 | -| 4 | ATS - 250A | | 1 | -| 5 | ATS - 400A | | 2 | -| 6 | ATS - 600A | | 2 | -| 7 | ATS - 800A | | 1 | -| 8 | ATS - 1000A | | 1 | -| 9 | Panelboard - 50A, 1-Section | | 1 | -| 10 | Panelboard - 100A, 1-Section | | 18 | -| 11 | Panelboard - 125A, 1-Section | | 26 | -| 12 | Panelboard - 150A, 1-Section | | 2 | -| 13 | Panelboard - 225A, 1-Section | | 11 | -| 14 | Panelboard - 225A, 2-Section | | 5 | -| 15 | Panelboard - 400A, 1-Section | | 2 | -| 16 | Panelboard - 400A, 2-Section | | 3 | -| 17 | Panelboard - 400A, 3-Section | | 5 | -| 18 | Panelboard - 600A, 2-Section | | 1 | -| 19 | Panelboard - 800A, 1-Section | | 1 | -| 20 | Panelboard - 1200A, 1-Section | | 2 | -| 21 | Panelboard - 1200A, 2-Section | | 1 | -| 22 | Panelboard - 3000A, 1-Section | | 1 | -| 23 | CT Cabinet | | | -| 24 | Power Monitor | | 82 | -| 25 | SPD/TVSS | | 2 | - -> Ah, so you just chuck in a lot # of terms per board and call it good? - -Essentially. -Ben's direction was to pick a schedule -on the upper end of terms for each size panel -to be representative of the rest. -At my old place I would have made a designation for each panel, -I'm not upset to leave that behind. -I see no reason you couldn't just make each size once -and keep it in a temp job. -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--- -> 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. -> -> That would be the best way, finding the actual average. - -The mech connection assemblies have the load side term, -the feeder assemblies have both sides, -the branch assemblies don't have either, -that's why he got you, I think. - -I don't think my way is best -unless you already have all the circuits in a big table for other reasons. -Lot of effort for a marginal increase in certainty above a heuristic like Ben's. - -I'm working on a job Noah started now, -he made certain panels separate from what I assume is the average -and labeled them with the name of the panel. -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]]. diff --git a/2026-01-07.md b/2026-01-07.md index cd4f06b..7d745a5 100644 --- a/2026-01-07.md +++ b/2026-01-07.md @@ -10,125 +10,3 @@ tags: 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. diff --git a/2026-01-08.md b/2026-01-08.md index 0fed691..6413c28 100644 --- a/2026-01-08.md +++ b/2026-01-08.md @@ -10,46 +10,3 @@ tags: dg-publish: true --- # 2026-01-08 - -# 2026-01-08 13:33:34 - -### 2100 Crystal Drive Takeoff Review - -#### Generators - -> [!failure] -> Generators were erroneously broken down in switchgear. - -[[switchgear-takeoff#Generator|Generator]] - -#### Switchgear - -Switchgear cost comp -"\\EgnyteDrive\Shared\Estimating\11 Bid Estimating Spreadsheets\Switchgear Pricing Tool Version 2 (2.02.2024) (Template) - Copy.xls" - -Includes -* submetering -* coordination study - -#### Composite Cleanup - -1 day per week - -$$ -\text{Average Weeks Per Month} = -$$ - -> It occurs to me I don't know all the rules of our calendar -> [Gregorian calendar - Wikipedia](https://en.wikipedia.org/wiki/Gregorian_calendar) - -#### Temp Power - -$10,000 per [[heavy-equipment#Swing Stage Scaffolding|swing stage]] - -[[temp-power-takeoff]] - -#### Unit Typicals - -I asked Joel about using unit typicals as described in -[[2025-12-19#2025-12-19 10:44]]. -He stated that would be acceptable. diff --git a/2026-01-09.md b/2026-01-09.md index e9bb7e0..76bd818 100644 --- a/2026-01-09.md +++ b/2026-01-09.md @@ -10,105 +10,3 @@ tags: 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. diff --git a/2026-01-11.md b/2026-01-11.md index ea071e8..40b3228 100644 --- a/2026-01-11.md +++ b/2026-01-11.md @@ -10,61 +10,3 @@ tags: 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"]] - -The value that estimators provide for a contractor -is in modeling project cost. -If the goal were simply to present a number the cost will not exceed, -than anyone could be an estimator. -If the goal were only to present a reasonably accurate figure, -with no other constraints, -then there are few who in the world who couldn't, -given infinite time for a single bid. -The _true_ value of an estimator, then, -is in their ability to model project cost _efficiently_, that is, -to achieve _acceptable_ accuracy and precision as quickly as possible,--- -much as the engineer's is in building a bridge that _meets_ the requirements -as cheaply as possible. - -Estimating "as accurately as possible" -is akin to building a bridge "as strong as possible"; -it sounds nice, but ignores the actual objective of _optimal cost-efficiency_. - -I think that most estimators believe this to be the case, -but, whatever they believe in mind, they believe in practice -that the goal is to model cost as accurately and precisely as possible, -_given the time allowed for bid_. -Estimates tend always to take exactly as many weeks as until the bid due date, -even those of significantly different turnaround but equal scope and complexity. -This behavior is objectionable, -since if an acceptable estimate _could_ be provided in two weeks, -it is not cost-effective[^1] to allow it to take four.[^2] - -[^1]: "Cost" referring both to estimator salaries and the opportunity cost of declined bids. - -[^2]: Supposing a contractor maintained a modern portfolio theory styled record of estimates - including pending bids, and projects ongoing and completed - (each with confidence estimates), - uncorrupted by [[estimating-culture#Incentives|perverse incentives]], - they may have reasonable basis to set sliding standards for estimate precision - to be specifically determined at consideration of the opportunity for bid - according to current climate (i.e. their transient risk appetite). - I believe my use of the absolute is still fair: - No contractor is doing that, so they lack a competent measure of risk tolerance - besides continuing to tolerate what they have historically. - -> [!important] -> Objectionable as it is, -> it is to be expected that estimators will use all time allowed them -> when the standards for _acceptability_ are inadequately defined. diff --git a/2026-01-15.md b/2026-01-15.md index 49ce2b8..d9495a4 100644 --- a/2026-01-15.md +++ b/2026-01-15.md @@ -10,14 +10,3 @@ tags: 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. diff --git a/fixture-designations.md b/fixture-designations.md index dbb75cf..32dbfd0 100644 --- a/fixture-designations.md +++ b/fixture-designations.md @@ -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 diff --git a/timestamped/2025-11-10_06-53-00.md b/timestamped/2025-11-10_06-53-00.md new file mode 100644 index 0000000..b6011bf --- /dev/null +++ b/timestamped/2025-11-10_06-53-00.md @@ -0,0 +1,31 @@ +# 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... \ No newline at end of file diff --git a/timestamped/2025-11-10_10-40-00.md b/timestamped/2025-11-10_10-40-00.md new file mode 100644 index 0000000..ba5ab98 --- /dev/null +++ b/timestamped/2025-11-10_10-40-00.md @@ -0,0 +1,8 @@ +# 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. \ No newline at end of file diff --git a/timestamped/2025-11-10_11-14-00.md b/timestamped/2025-11-10_11-14-00.md new file mode 100644 index 0000000..f23ce1b --- /dev/null +++ b/timestamped/2025-11-10_11-14-00.md @@ -0,0 +1,49 @@ +# 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. \ No newline at end of file diff --git a/timestamped/2025-11-10_15-15-00.md b/timestamped/2025-11-10_15-15-00.md new file mode 100644 index 0000000..3c4e1bb --- /dev/null +++ b/timestamped/2025-11-10_15-15-00.md @@ -0,0 +1,14 @@ +# 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. \ No newline at end of file diff --git a/timestamped/2025-11-10_20-00-00.md b/timestamped/2025-11-10_20-00-00.md new file mode 100644 index 0000000..d16edc9 --- /dev/null +++ b/timestamped/2025-11-10_20-00-00.md @@ -0,0 +1,31 @@ +# 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. diff --git a/timestamped/2025-11-11_06-06-00.md b/timestamped/2025-11-11_06-06-00.md new file mode 100644 index 0000000..3a7ca14 --- /dev/null +++ b/timestamped/2025-11-11_06-06-00.md @@ -0,0 +1,27 @@ +# 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. \ No newline at end of file diff --git a/timestamped/2025-11-11_14-41-00.md b/timestamped/2025-11-11_14-41-00.md new file mode 100644 index 0000000..33c107b --- /dev/null +++ b/timestamped/2025-11-11_14-41-00.md @@ -0,0 +1,24 @@ +# 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. diff --git a/timestamped/2025-11-13_00-00-00.md b/timestamped/2025-11-13_00-00-00.md new file mode 100644 index 0000000..e69de29 diff --git a/timestamped/2025-11-13_08-03-00.md b/timestamped/2025-11-13_08-03-00.md new file mode 100644 index 0000000..a3af7e5 --- /dev/null +++ b/timestamped/2025-11-13_08-03-00.md @@ -0,0 +1,12 @@ +# 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. \ No newline at end of file diff --git a/timestamped/2025-11-13_08-19-00.md b/timestamped/2025-11-13_08-19-00.md new file mode 100644 index 0000000..8e43287 --- /dev/null +++ b/timestamped/2025-11-13_08-19-00.md @@ -0,0 +1,37 @@ +# 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? \ No newline at end of file diff --git a/timestamped/2025-11-13_20-41-00.md b/timestamped/2025-11-13_20-41-00.md new file mode 100644 index 0000000..f1357c8 --- /dev/null +++ b/timestamped/2025-11-13_20-41-00.md @@ -0,0 +1,11 @@ +# 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. diff --git a/timestamped/2025-12-02_10-40-00.md b/timestamped/2025-12-02_10-40-00.md new file mode 100644 index 0000000..420998d --- /dev/null +++ b/timestamped/2025-12-02_10-40-00.md @@ -0,0 +1,14 @@ +# 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]] \ No newline at end of file diff --git a/timestamped/2025-12-02_10-57-00.md b/timestamped/2025-12-02_10-57-00.md new file mode 100644 index 0000000..b5e529f --- /dev/null +++ b/timestamped/2025-12-02_10-57-00.md @@ -0,0 +1,20 @@ +# 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$. \ No newline at end of file diff --git a/timestamped/2025-12-02_13-20-00.md b/timestamped/2025-12-02_13-20-00.md new file mode 100644 index 0000000..4efb9f6 --- /dev/null +++ b/timestamped/2025-12-02_13-20-00.md @@ -0,0 +1,14 @@ +# 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)` diff --git a/timestamped/2025-12-16_09-20-52.md b/timestamped/2025-12-16_09-20-52.md new file mode 100644 index 0000000..4f41ec4 --- /dev/null +++ b/timestamped/2025-12-16_09-20-52.md @@ -0,0 +1,5 @@ +# 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) \ No newline at end of file diff --git a/timestamped/2025-12-16_20-04-00.md b/timestamped/2025-12-16_20-04-00.md new file mode 100644 index 0000000..d2e4c26 --- /dev/null +++ b/timestamped/2025-12-16_20-04-00.md @@ -0,0 +1,5 @@ +# 2025-12-16 20:04:?? + +### Metalog Distributions + +[Metalog Distributions]http://www.metalogdistributions.com/home.html) diff --git a/timestamped/2025-12-17_05-39-00.md b/timestamped/2025-12-17_05-39-00.md new file mode 100644 index 0000000..89e1886 --- /dev/null +++ b/timestamped/2025-12-17_05-39-00.md @@ -0,0 +1,37 @@ +# 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]] \ No newline at end of file diff --git a/timestamped/2025-12-17_12-32-00.md b/timestamped/2025-12-17_12-32-00.md new file mode 100644 index 0000000..58f5f76 --- /dev/null +++ b/timestamped/2025-12-17_12-32-00.md @@ -0,0 +1,43 @@ +# 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] +when, he suggests, they ought to just be called what they do. + +[^2]: `bubble-tea` and `ratatui` + (libraries for creating CLI's) come to my mind + +Unfortunately some people and organizations agree with him, +giving us terms which mean both something very general +and something very specific.[^3] + +[^3]: [[project-management-tm|"Project Management"]] + was my go to example, but weak + because it's difficult for me to articulate + the difference from construction project management + especially to someone unfamiliar with the specifics of either. + +For lack of a better term I've been thinking of this as an SEO problem, +but the bigger problem is that it invites [[ambiguity#Category Mistake|Category Mistake]], +whereby the ignorant listener associates traits unique to the example +to all things that the name could describe. + +I thought to finally write about this problem +while researching [[lighting-controls#Protocols|lighting control protocols]]. +The two most dominant examples: + +* [[lighting-controls#^dali|"Digital Addressable Lighting Interface (DALI)"]] +* [[lighting-controls#^dmx|"Digital Multiplex (DMX)"]] + +while notably different in topology, +could both be described accurately with the other's name. + +> It is possible to avoid this problem +> without the effort necessary to come up with a clever name. +> Just stick an arbitrary, but reasonably unique word +> in front of the generic description. +> A person's name ("John's Digital Addressable Lighting Interface (JDALI)") +> or your favorite animal ("Heron Digital Multiplex (HDMX)") are good options. diff --git a/timestamped/2025-12-18_08-32-18.md b/timestamped/2025-12-18_08-32-18.md new file mode 100644 index 0000000..fed9aff --- /dev/null +++ b/timestamped/2025-12-18_08-32-18.md @@ -0,0 +1,3 @@ +# 2025-12-18 08:32:18 + +[[uncertainty-in-construction-estimating]] \ No newline at end of file diff --git a/timestamped/2025-12-18_10-38-00.md b/timestamped/2025-12-18_10-38-00.md new file mode 100644 index 0000000..0c74a4c --- /dev/null +++ b/timestamped/2025-12-18_10-38-00.md @@ -0,0 +1,11 @@ +# 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. \ No newline at end of file diff --git a/timestamped/2025-12-18_14-18-00.md b/timestamped/2025-12-18_14-18-00.md new file mode 100644 index 0000000..11a1c8f --- /dev/null +++ b/timestamped/2025-12-18_14-18-00.md @@ -0,0 +1,26 @@ +# 2025-12-18 14:18:?? + +### Estimating Golf + +What interests me most in [[construction-estimating]] +is an idea you might call "estimating golf": +the goal is to produce a satisfactory[^1] estimate, +but the estimator can not view the project documents +and must instead ask questions about the job +(answerable in a sentence or less) +of a neutral party ("the reader"). +The estimator fails if the estimate is unsatisfactory[^1], +but otherwise is scored by number of questions asked. + +[^1]: satisfactory in terms of accuracy and precision, + according to the standards of the organization. + a control estimate must be prepared accordingly + by a neutral party ("the control"). + +You could further imagine different brackets +for required accuracy and precision, +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. \ No newline at end of file diff --git a/timestamped/2025-12-18_15-22-00.md b/timestamped/2025-12-18_15-22-00.md new file mode 100644 index 0000000..910afc3 --- /dev/null +++ b/timestamped/2025-12-18_15-22-00.md @@ -0,0 +1,6 @@ +# 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/) \ No newline at end of file diff --git a/timestamped/2025-12-18_15-30-00.md b/timestamped/2025-12-18_15-30-00.md new file mode 100644 index 0000000..b946ad9 --- /dev/null +++ b/timestamped/2025-12-18_15-30-00.md @@ -0,0 +1,4 @@ +# 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) diff --git a/timestamped/2025-12-19_10-44-00.md b/timestamped/2025-12-19_10-44-00.md new file mode 100644 index 0000000..4f1efcc --- /dev/null +++ b/timestamped/2025-12-19_10-44-00.md @@ -0,0 +1,17 @@ +# 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 + +> [!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 \ No newline at end of file diff --git a/timestamped/2025-12-19_10-44-01.md b/timestamped/2025-12-19_10-44-01.md new file mode 100644 index 0000000..b0fc24a --- /dev/null +++ b/timestamped/2025-12-19_10-44-01.md @@ -0,0 +1,14 @@ +# 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. +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.), +but there is potential for significant efficiency gains +in treating units like panelboards in [[switchgear-takeoff]]: +picking one unit type to be typical of many nearly identical types. diff --git a/timestamped/2026-01-02_10-10-18.md b/timestamped/2026-01-02_10-10-18.md new file mode 100644 index 0000000..17f5c3c --- /dev/null +++ b/timestamped/2026-01-02_10-10-18.md @@ -0,0 +1,9 @@ +# 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]] \ No newline at end of file diff --git a/timestamped/2026-01-02_19-21-00.md b/timestamped/2026-01-02_19-21-00.md new file mode 100644 index 0000000..b5dad43 --- /dev/null +++ b/timestamped/2026-01-02_19-21-00.md @@ -0,0 +1,18 @@ +# 2026-01-02 19:21:?? + +Without apparent prompt I was reminded of a practical joke +that my fellow apprentice Joe used to play often +that never failed to get a laugh out of me: + +Mid-conversation Joe would stop suddenly, +search in his pockets or tool belt, +pull out a random object (usually his lineman's pliers), +and act as if he had received a phone call on it. +Often the other party had apparently dialed in error, +and Joe would say, "Hello?... Hello?" +before deciding they'd hung up. +Other times he'd step away (only one step) +and have whole conversations. + +Try as I might have, +I could never pull it off like he could. diff --git a/timestamped/2026-01-06_07-47-00.md b/timestamped/2026-01-06_07-47-00.md new file mode 100644 index 0000000..d3fd654 --- /dev/null +++ b/timestamped/2026-01-06_07-47-00.md @@ -0,0 +1,12 @@ +# 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 \ No newline at end of file diff --git a/timestamped/2026-01-06_10-00-00.md b/timestamped/2026-01-06_10-00-00.md new file mode 100644 index 0000000..9b1f55c --- /dev/null +++ b/timestamped/2026-01-06_10-00-00.md @@ -0,0 +1,84 @@ +# 2026-01-06 10:00:?? + +Paraphrased Teams conversation with a peer +about [[distribution-designations#Terminations]]. +Peer's messages are in block quotes. + +*** + +> Good morning! +> Do you add branch terminations to panelboards? +> If so, how does your 'distribution' section looks? + +Morning! Yes to the first question, ? to the second + +> As all panelboards on a job don't have the same size/# of terminations, +> I assume you would have a plethora of same size boards in the job, with different terms. +> How do you list them? + +| | Designation | Status | Quantity | +| --- | ----------------------------- | ------ | -------- | +| 1 | Generator - 350kW, Diesel | | 1 | +| 2 | Generator - 2000kW, Diesel | | 1 | +| 3 | ATS - 200A | | 2 | +| 4 | ATS - 250A | | 1 | +| 5 | ATS - 400A | | 2 | +| 6 | ATS - 600A | | 2 | +| 7 | ATS - 800A | | 1 | +| 8 | ATS - 1000A | | 1 | +| 9 | Panelboard - 50A, 1-Section | | 1 | +| 10 | Panelboard - 100A, 1-Section | | 18 | +| 11 | Panelboard - 125A, 1-Section | | 26 | +| 12 | Panelboard - 150A, 1-Section | | 2 | +| 13 | Panelboard - 225A, 1-Section | | 11 | +| 14 | Panelboard - 225A, 2-Section | | 5 | +| 15 | Panelboard - 400A, 1-Section | | 2 | +| 16 | Panelboard - 400A, 2-Section | | 3 | +| 17 | Panelboard - 400A, 3-Section | | 5 | +| 18 | Panelboard - 600A, 2-Section | | 1 | +| 19 | Panelboard - 800A, 1-Section | | 1 | +| 20 | Panelboard - 1200A, 1-Section | | 2 | +| 21 | Panelboard - 1200A, 2-Section | | 1 | +| 22 | Panelboard - 3000A, 1-Section | | 1 | +| 23 | CT Cabinet | | | +| 24 | Power Monitor | | 82 | +| 25 | SPD/TVSS | | 2 | + +> Ah, so you just chuck in a lot # of terms per board and call it good? + +Essentially. +Ben's direction was to pick a schedule +on the upper end of terms for each size panel +to be representative of the rest. +At my old place I would have made a designation for each panel, +I'm not upset to leave that behind. +I see no reason you couldn't just make each size once +and keep it in a temp job. +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--- +> 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. +> +> That would be the best way, finding the actual average. + +The mech connection assemblies have the load side term, +the feeder assemblies have both sides, +the branch assemblies don't have either, +that's why he got you, I think. + +I don't think my way is best +unless you already have all the circuits in a big table for other reasons. +Lot of effort for a marginal increase in certainty above a heuristic like Ben's. + +I'm working on a job Noah started now, +he made certain panels separate from what I assume is the average +and labeled them with the name of the panel. +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. \ No newline at end of file diff --git a/timestamped/2026-01-06_10-57-00.md b/timestamped/2026-01-06_10-57-00.md new file mode 100644 index 0000000..8d09168 --- /dev/null +++ b/timestamped/2026-01-06_10-57-00.md @@ -0,0 +1,15 @@ +# 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]]. diff --git a/timestamped/2026-01-07_06-41-00.md b/timestamped/2026-01-07_06-41-00.md new file mode 100644 index 0000000..71e1c6c --- /dev/null +++ b/timestamped/2026-01-07_06-41-00.md @@ -0,0 +1,18 @@ +# 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. \ No newline at end of file diff --git a/timestamped/2026-01-07_10-03-00.md b/timestamped/2026-01-07_10-03-00.md new file mode 100644 index 0000000..50f5478 --- /dev/null +++ b/timestamped/2026-01-07_10-03-00.md @@ -0,0 +1,4 @@ +# 2026-01-07 10:03:?? + +At Ace, "residential" always meant single-family/duplex construction, +but I think now we were the outliers. \ No newline at end of file diff --git a/timestamped/2026-01-07_10-05-00.md b/timestamped/2026-01-07_10-05-00.md new file mode 100644 index 0000000..1e66ae0 --- /dev/null +++ b/timestamped/2026-01-07_10-05-00.md @@ -0,0 +1,15 @@ +# 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". \ No newline at end of file diff --git a/timestamped/2026-01-07_10-42-00.md b/timestamped/2026-01-07_10-42-00.md new file mode 100644 index 0000000..c0852e8 --- /dev/null +++ b/timestamped/2026-01-07_10-42-00.md @@ -0,0 +1,40 @@ +# 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. \ No newline at end of file diff --git a/timestamped/2026-01-07_12-13-00.md b/timestamped/2026-01-07_12-13-00.md new file mode 100644 index 0000000..bc9f947 --- /dev/null +++ b/timestamped/2026-01-07_12-13-00.md @@ -0,0 +1,28 @@ +# 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]]. \ No newline at end of file diff --git a/timestamped/2026-01-07_16-03-00.md b/timestamped/2026-01-07_16-03-00.md new file mode 100644 index 0000000..cad28df --- /dev/null +++ b/timestamped/2026-01-07_16-03-00.md @@ -0,0 +1,11 @@ +# 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. diff --git a/timestamped/2026-01-08_13-33-34.md b/timestamped/2026-01-08_13-33-34.md new file mode 100644 index 0000000..ead382a --- /dev/null +++ b/timestamped/2026-01-08_13-33-34.md @@ -0,0 +1,42 @@ +# 2026-01-08 13:33:34 + +### 2100 Crystal Drive Takeoff Review + +#### Generators + +> [!failure] +> Generators were erroneously broken down in switchgear. + +[[switchgear-takeoff#Generator|Generator]] + +#### Switchgear + +Switchgear cost comp +"\\EgnyteDrive\Shared\Estimating\11 Bid Estimating Spreadsheets\Switchgear Pricing Tool Version 2 (2.02.2024) (Template) - Copy.xls" + +Includes +* submetering +* coordination study + +#### Composite Cleanup + +1 day per week + +$$ +\text{Average Weeks Per Month} = +$$ + +> It occurs to me I don't know all the rules of our calendar +> [Gregorian calendar - Wikipedia](https://en.wikipedia.org/wiki/Gregorian_calendar) + +#### Temp Power + +$10,000 per [[heavy-equipment#Swing Stage Scaffolding|swing stage]] + +[[temp-power-takeoff]] + +#### Unit Typicals + +I asked Joel about using unit typicals as described in +[[2025-12-19#2025-12-19 10:44]]. +He stated that would be acceptable. diff --git a/timestamped/2026-01-09_10-00-03.md b/timestamped/2026-01-09_10-00-03.md new file mode 100644 index 0000000..396b7cf --- /dev/null +++ b/timestamped/2026-01-09_10-00-03.md @@ -0,0 +1,45 @@ +# 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 \ No newline at end of file diff --git a/timestamped/2026-01-09_12-00-00.md b/timestamped/2026-01-09_12-00-00.md new file mode 100644 index 0000000..1af14ed --- /dev/null +++ b/timestamped/2026-01-09_12-00-00.md @@ -0,0 +1,19 @@ +# 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} +$$ \ No newline at end of file diff --git a/timestamped/2026-01-09_14-45-00.md b/timestamped/2026-01-09_14-45-00.md new file mode 100644 index 0000000..8bee251 --- /dev/null +++ b/timestamped/2026-01-09_14-45-00.md @@ -0,0 +1,15 @@ +# 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). \ No newline at end of file diff --git a/timestamped/2026-01-09_16-28-00.md b/timestamped/2026-01-09_16-28-00.md new file mode 100644 index 0000000..85b6789 --- /dev/null +++ b/timestamped/2026-01-09_16-28-00.md @@ -0,0 +1,19 @@ +# 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. diff --git a/timestamped/2026-01-11_09-00-00.md b/timestamped/2026-01-11_09-00-00.md new file mode 100644 index 0000000..ed7f171 --- /dev/null +++ b/timestamped/2026-01-11_09-00-00.md @@ -0,0 +1,7 @@ +# 2026-01-11 09:00:?? + +[[2026-01-09#2026-01-09 14:45]] + +[[bid-price-modeling]] + +[[decrease-in-sigma]] \ No newline at end of file diff --git a/timestamped/2026-01-11_11-00-00.md b/timestamped/2026-01-11_11-00-00.md new file mode 100644 index 0000000..e9d9af8 --- /dev/null +++ b/timestamped/2026-01-11_11-00-00.md @@ -0,0 +1,49 @@ +# 2026-01-11 11:00:?? + +![[favorite-quotes#"It Takes an Engineer to Build a Bridge that Barely Stands"]] + +The value that estimators provide for a contractor +is in modeling project cost. +If the goal were simply to present a number the cost will not exceed, +than anyone could be an estimator. +If the goal were only to present a reasonably accurate figure, +with no other constraints, +then there are few who in the world who couldn't, +given infinite time for a single bid. +The _true_ value of an estimator, then, +is in their ability to model project cost _efficiently_, that is, +to achieve _acceptable_ accuracy and precision as quickly as possible,--- +much as the engineer's is in building a bridge that _meets_ the requirements +as cheaply as possible. + +Estimating "as accurately as possible" +is akin to building a bridge "as strong as possible"; +it sounds nice, but ignores the actual objective of _optimal cost-efficiency_. + +I think that most estimators believe this to be the case, +but, whatever they believe in mind, they believe in practice +that the goal is to model cost as accurately and precisely as possible, +_given the time allowed for bid_. +Estimates tend always to take exactly as many weeks as until the bid due date, +even those of significantly different turnaround but equal scope and complexity. +This behavior is objectionable, +since if an acceptable estimate _could_ be provided in two weeks, +it is not cost-effective[^1] to allow it to take four.[^2] + +[^1]: "Cost" referring both to estimator salaries and the opportunity cost of declined bids. + +[^2]: Supposing a contractor maintained a modern portfolio theory styled record of estimates + including pending bids, and projects ongoing and completed + (each with confidence estimates), + uncorrupted by [[estimating-culture#Incentives|perverse incentives]], + they may have reasonable basis to set sliding standards for estimate precision + to be specifically determined at consideration of the opportunity for bid + according to current climate (i.e. their transient risk appetite). + I believe my use of the absolute is still fair: + No contractor is doing that, so they lack a competent measure of risk tolerance + besides continuing to tolerate what they have historically. + +> [!important] +> Objectionable as it is, +> it is to be expected that estimators will use all time allowed them +> when the standards for _acceptability_ are inadequately defined. diff --git a/timestamped/2026-01-15_08-11-10.md b/timestamped/2026-01-15_08-11-10.md new file mode 100644 index 0000000..996f4e4 --- /dev/null +++ b/timestamped/2026-01-15_08-11-10.md @@ -0,0 +1,5 @@ +# 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. \ No newline at end of file diff --git a/timestamped/2026-01-15_08-15-00.md b/timestamped/2026-01-15_08-15-00.md new file mode 100644 index 0000000..b56bda2 --- /dev/null +++ b/timestamped/2026-01-15_08-15-00.md @@ -0,0 +1,4 @@ +# 2026-01-15 08:15:?? + +[[2025-11-13#2025-11-13 08:19]] +I spoke to a peer about this yesterday. From 74cbd5ed142eceb2bf82967e42952d884fcffbf9 Mon Sep 17 00:00:00 2001 From: Zane Meyers Date: Wed, 25 Feb 2026 12:13:29 -0500 Subject: [PATCH 2/6] vault backup: 2026-02-25 12:13:29 --- 2025-11-01.md => daily/2025-11-01.md | 0 2025-11-10.md => daily/2025-11-10.md | 0 2025-11-11.md => daily/2025-11-11.md | 0 2025-11-13.md => daily/2025-11-13.md | 0 2025-12-02.md => daily/2025-12-02.md | 0 2025-12-16.md => daily/2025-12-16.md | 0 2025-12-17.md => daily/2025-12-17.md | 0 2025-12-18.md => daily/2025-12-18.md | 0 2025-12-19.md => daily/2025-12-19.md | 0 2026-01-01.md => daily/2026-01-01.md | 0 2026-01-02.md => daily/2026-01-02.md | 0 2026-01-06.md => daily/2026-01-06.md | 0 2026-01-07.md => daily/2026-01-07.md | 0 2026-01-08.md => daily/2026-01-08.md | 0 2026-01-09.md => daily/2026-01-09.md | 0 2026-01-11.md => daily/2026-01-11.md | 0 2026-01-12.md => daily/2026-01-12.md | 0 2026-01-15.md => daily/2026-01-15.md | 0 2026-01-19.md => daily/2026-01-19.md | 0 2026-01-20.md => daily/2026-01-20.md | 0 2026-01-22.md => daily/2026-01-22.md | 0 2026-01-23.md => daily/2026-01-23.md | 0 2026-01-25.md => daily/2026-01-25.md | 0 2026-01-28.md => daily/2026-01-28.md | 0 2026-01-29.md => daily/2026-01-29.md | 0 2026-01-30.md => daily/2026-01-30.md | 0 nfpa-70_518.md | 124 +++++++++++++++++++++++++++ timestamped/2025-07-18_00-00-00.md | 2 +- timestamped/2025-11-10_06-53-00.md | 14 ++- timestamped/2025-11-10_10-40-00.md | 8 ++ timestamped/2025-11-10_11-14-00.md | 8 ++ timestamped/2025-11-10_15-15-00.md | 8 ++ timestamped/2025-11-10_20-00-00.md | 8 ++ timestamped/2025-11-11_06-06-00.md | 8 ++ timestamped/2025-11-11_14-41-00.md | 8 ++ timestamped/2025-11-13_08-03-00.md | 8 ++ timestamped/2025-11-13_08-19-00.md | 8 ++ timestamped/2025-11-13_20-41-00.md | 8 ++ timestamped/2025-12-02_10-40-00.md | 8 ++ timestamped/2025-12-02_10-57-00.md | 8 ++ timestamped/2025-12-02_13-20-00.md | 8 ++ timestamped/2025-12-16_09-20-52.md | 8 ++ timestamped/2025-12-16_20-04-00.md | 8 ++ timestamped/2025-12-17_05-39-00.md | 8 ++ timestamped/2025-12-17_12-32-00.md | 8 ++ timestamped/2025-12-18_08-32-18.md | 8 ++ timestamped/2025-12-18_10-38-00.md | 8 ++ timestamped/2025-12-18_14-18-00.md | 8 ++ timestamped/2025-12-18_15-22-00.md | 8 ++ timestamped/2025-12-18_15-30-00.md | 8 ++ timestamped/2025-12-19_10-44-00.md | 8 ++ timestamped/2025-12-19_10-44-01.md | 8 ++ timestamped/2026-01-02_10-10-18.md | 8 ++ timestamped/2026-01-02_19-21-00.md | 8 ++ timestamped/2026-01-06_07-47-00.md | 8 ++ timestamped/2026-01-06_10-00-00.md | 8 ++ timestamped/2026-01-06_10-57-00.md | 8 ++ timestamped/2026-01-07_06-41-00.md | 8 ++ timestamped/2026-01-07_10-03-00.md | 8 ++ timestamped/2026-01-07_10-05-00.md | 8 ++ timestamped/2026-01-07_10-42-00.md | 8 ++ timestamped/2026-01-07_12-13-00.md | 8 ++ timestamped/2026-01-07_16-03-00.md | 8 ++ timestamped/2026-01-08_13-33-34.md | 8 ++ timestamped/2026-01-09_10-00-03.md | 8 ++ timestamped/2026-01-09_12-00-00.md | 8 ++ timestamped/2026-01-09_14-45-00.md | 8 ++ timestamped/2026-01-09_16-28-00.md | 8 ++ timestamped/2026-01-11_09-00-00.md | 8 ++ timestamped/2026-01-11_11-00-00.md | 8 ++ timestamped/2026-01-12_10-00-00.md | 3 + timestamped/2026-01-12_10-42-30.md | 3 + timestamped/2026-01-12_12-23-00.md | 3 + timestamped/2026-01-12_13-02-00.md | 3 + timestamped/2026-01-15_08-11-10.md | 8 ++ timestamped/2026-01-15_08-15-00.md | 8 ++ timestamped/2026-01-19_11-57-39.md | 3 + timestamped/2026-01-19_12-32-00.md | 3 + timestamped/2026-01-19_18-13-00.md | 3 + timestamped/2026-01-20_09-09-12.md | 3 + timestamped/2026-01-20_10-10-00.md | 3 + timestamped/2026-01-20_14-25-00.md | 3 + timestamped/2026-01-22_09-55-42.md | 3 + timestamped/2026-01-22_11-58-00.md | 3 + timestamped/2026-01-22_14-56-00.md | 3 + timestamped/2026-01-23_08-18-53.md | 3 + timestamped/2026-01-23_12-34-00.md | 3 + timestamped/2026-01-25_18-46-00.md | 3 + timestamped/2026-01-25_21-02-00.md | 3 + timestamped/2026-01-25_22-59-00.md | 3 + timestamped/2026-01-28_09-51-08.md | 3 + timestamped/2026-01-28_10-02-00.md | 3 + timestamped/2026-01-29_10-07-37.md | 3 + timestamped/2026-01-29_17-57-00.md | 3 + timestamped/2026-01-30_08-44-29.md | 3 + timestamped/2026-01-30_09-06-00.md | 3 + timestamped/2026-01-30_13-42-00.md | 7 +- timestamped/2026-01-30_16-29-00.md | 8 +- timestamped/2026-01-30_18-33-00.md | 7 +- timestamped/2026-01-31_12-48-00.md | 2 +- timestamped/2026-02-04_08-07-00.md | 2 + timestamped/2026-02-04_19-35-00.md | 2 +- timestamped/2026-02-17_13-13-06.md | 2 +- 103 files changed, 573 insertions(+), 13 deletions(-) rename 2025-11-01.md => daily/2025-11-01.md (100%) rename 2025-11-10.md => daily/2025-11-10.md (100%) rename 2025-11-11.md => daily/2025-11-11.md (100%) rename 2025-11-13.md => daily/2025-11-13.md (100%) rename 2025-12-02.md => daily/2025-12-02.md (100%) rename 2025-12-16.md => daily/2025-12-16.md (100%) rename 2025-12-17.md => daily/2025-12-17.md (100%) rename 2025-12-18.md => daily/2025-12-18.md (100%) rename 2025-12-19.md => daily/2025-12-19.md (100%) rename 2026-01-01.md => daily/2026-01-01.md (100%) rename 2026-01-02.md => daily/2026-01-02.md (100%) rename 2026-01-06.md => daily/2026-01-06.md (100%) rename 2026-01-07.md => daily/2026-01-07.md (100%) rename 2026-01-08.md => daily/2026-01-08.md (100%) rename 2026-01-09.md => daily/2026-01-09.md (100%) rename 2026-01-11.md => daily/2026-01-11.md (100%) rename 2026-01-12.md => daily/2026-01-12.md (100%) rename 2026-01-15.md => daily/2026-01-15.md (100%) rename 2026-01-19.md => daily/2026-01-19.md (100%) rename 2026-01-20.md => daily/2026-01-20.md (100%) rename 2026-01-22.md => daily/2026-01-22.md (100%) rename 2026-01-23.md => daily/2026-01-23.md (100%) rename 2026-01-25.md => daily/2026-01-25.md (100%) rename 2026-01-28.md => daily/2026-01-28.md (100%) rename 2026-01-29.md => daily/2026-01-29.md (100%) rename 2026-01-30.md => daily/2026-01-30.md (100%) create mode 100644 nfpa-70_518.md diff --git a/2025-11-01.md b/daily/2025-11-01.md similarity index 100% rename from 2025-11-01.md rename to daily/2025-11-01.md diff --git a/2025-11-10.md b/daily/2025-11-10.md similarity index 100% rename from 2025-11-10.md rename to daily/2025-11-10.md diff --git a/2025-11-11.md b/daily/2025-11-11.md similarity index 100% rename from 2025-11-11.md rename to daily/2025-11-11.md diff --git a/2025-11-13.md b/daily/2025-11-13.md similarity index 100% rename from 2025-11-13.md rename to daily/2025-11-13.md diff --git a/2025-12-02.md b/daily/2025-12-02.md similarity index 100% rename from 2025-12-02.md rename to daily/2025-12-02.md diff --git a/2025-12-16.md b/daily/2025-12-16.md similarity index 100% rename from 2025-12-16.md rename to daily/2025-12-16.md diff --git a/2025-12-17.md b/daily/2025-12-17.md similarity index 100% rename from 2025-12-17.md rename to daily/2025-12-17.md diff --git a/2025-12-18.md b/daily/2025-12-18.md similarity index 100% rename from 2025-12-18.md rename to daily/2025-12-18.md diff --git a/2025-12-19.md b/daily/2025-12-19.md similarity index 100% rename from 2025-12-19.md rename to daily/2025-12-19.md diff --git a/2026-01-01.md b/daily/2026-01-01.md similarity index 100% rename from 2026-01-01.md rename to daily/2026-01-01.md diff --git a/2026-01-02.md b/daily/2026-01-02.md similarity index 100% rename from 2026-01-02.md rename to daily/2026-01-02.md diff --git a/2026-01-06.md b/daily/2026-01-06.md similarity index 100% rename from 2026-01-06.md rename to daily/2026-01-06.md diff --git a/2026-01-07.md b/daily/2026-01-07.md similarity index 100% rename from 2026-01-07.md rename to daily/2026-01-07.md diff --git a/2026-01-08.md b/daily/2026-01-08.md similarity index 100% rename from 2026-01-08.md rename to daily/2026-01-08.md diff --git a/2026-01-09.md b/daily/2026-01-09.md similarity index 100% rename from 2026-01-09.md rename to daily/2026-01-09.md diff --git a/2026-01-11.md b/daily/2026-01-11.md similarity index 100% rename from 2026-01-11.md rename to daily/2026-01-11.md diff --git a/2026-01-12.md b/daily/2026-01-12.md similarity index 100% rename from 2026-01-12.md rename to daily/2026-01-12.md diff --git a/2026-01-15.md b/daily/2026-01-15.md similarity index 100% rename from 2026-01-15.md rename to daily/2026-01-15.md diff --git a/2026-01-19.md b/daily/2026-01-19.md similarity index 100% rename from 2026-01-19.md rename to daily/2026-01-19.md diff --git a/2026-01-20.md b/daily/2026-01-20.md similarity index 100% rename from 2026-01-20.md rename to daily/2026-01-20.md diff --git a/2026-01-22.md b/daily/2026-01-22.md similarity index 100% rename from 2026-01-22.md rename to daily/2026-01-22.md diff --git a/2026-01-23.md b/daily/2026-01-23.md similarity index 100% rename from 2026-01-23.md rename to daily/2026-01-23.md diff --git a/2026-01-25.md b/daily/2026-01-25.md similarity index 100% rename from 2026-01-25.md rename to daily/2026-01-25.md diff --git a/2026-01-28.md b/daily/2026-01-28.md similarity index 100% rename from 2026-01-28.md rename to daily/2026-01-28.md diff --git a/2026-01-29.md b/daily/2026-01-29.md similarity index 100% rename from 2026-01-29.md rename to daily/2026-01-29.md diff --git a/2026-01-30.md b/daily/2026-01-30.md similarity index 100% rename from 2026-01-30.md rename to daily/2026-01-30.md diff --git a/nfpa-70_518.md b/nfpa-70_518.md new file mode 100644 index 0000000..7813336 --- /dev/null +++ b/nfpa-70_518.md @@ -0,0 +1,124 @@ +--- +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 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 Restaurants +* Exhibition halls +* Gymnasiums +* Mortuary chapels +* Multipurpose rooms +* Museums +* Places of awaiting transportation +* Places of religious worship +* Pool rooms +* 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. diff --git a/timestamped/2025-07-18_00-00-00.md b/timestamped/2025-07-18_00-00-00.md index 49dfb39..199d22b 100644 --- a/timestamped/2025-07-18_00-00-00.md +++ b/timestamped/2025-07-18_00-00-00.md @@ -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 diff --git a/timestamped/2025-11-10_06-53-00.md b/timestamped/2025-11-10_06-53-00.md index b6011bf..e2719fe 100644 --- a/timestamped/2025-11-10_06-53-00.md +++ b/timestamped/2025-11-10_06-53-00.md @@ -1,9 +1,17 @@ +--- +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_ -#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 @@ -28,4 +36,4 @@ 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... \ No newline at end of file +like music and style and... birdwatching... diff --git a/timestamped/2025-11-10_10-40-00.md b/timestamped/2025-11-10_10-40-00.md index ba5ab98..b3345cc 100644 --- a/timestamped/2025-11-10_10-40-00.md +++ b/timestamped/2025-11-10_10-40-00.md @@ -1,3 +1,11 @@ +--- +id: +aliases: [] +title: +tags: + - type/timestamped +dg-publish: true +--- # 2025-11-10 10:40:?? #topic/estimating #occupational #original-format/digital-text diff --git a/timestamped/2025-11-10_11-14-00.md b/timestamped/2025-11-10_11-14-00.md index f23ce1b..2f0c578 100644 --- a/timestamped/2025-11-10_11-14-00.md +++ b/timestamped/2025-11-10_11-14-00.md @@ -1,3 +1,11 @@ +--- +id: +aliases: [] +title: +tags: + - type/timestamped +dg-publish: true +--- # 2025-11-10 11:14:?? #occupational/takeoff #original-format/digital-text diff --git a/timestamped/2025-11-10_15-15-00.md b/timestamped/2025-11-10_15-15-00.md index 3c4e1bb..a14a6fa 100644 --- a/timestamped/2025-11-10_15-15-00.md +++ b/timestamped/2025-11-10_15-15-00.md @@ -1,3 +1,11 @@ +--- +id: +aliases: [] +title: +tags: + - type/timestamped +dg-publish: true +--- # 2025-11-10 15:15:?? ### "Feeder" diff --git a/timestamped/2025-11-10_20-00-00.md b/timestamped/2025-11-10_20-00-00.md index d16edc9..7bf2095 100644 --- a/timestamped/2025-11-10_20-00-00.md +++ b/timestamped/2025-11-10_20-00-00.md @@ -1,3 +1,11 @@ +--- +id: +aliases: [] +title: +tags: + - type/timestamped +dg-publish: true +--- # 2025-11-10 20:00:?? _Monday Evening, Before Bed_ diff --git a/timestamped/2025-11-11_06-06-00.md b/timestamped/2025-11-11_06-06-00.md index 3a7ca14..111327b 100644 --- a/timestamped/2025-11-11_06-06-00.md +++ b/timestamped/2025-11-11_06-06-00.md @@ -1,3 +1,11 @@ +--- +id: +aliases: [] +title: +tags: + - type/timestamped +dg-publish: true +--- # 2025-11-11 06:06:?? _Tuesday Morning, Before Work_ diff --git a/timestamped/2025-11-11_14-41-00.md b/timestamped/2025-11-11_14-41-00.md index 33c107b..25a519e 100644 --- a/timestamped/2025-11-11_14-41-00.md +++ b/timestamped/2025-11-11_14-41-00.md @@ -1,3 +1,11 @@ +--- +id: +aliases: [] +title: +tags: + - type/timestamped +dg-publish: true +--- # 2025-11-11 14:41:?? #topic/estimating #topic/transparency #original-format/digital-text diff --git a/timestamped/2025-11-13_08-03-00.md b/timestamped/2025-11-13_08-03-00.md index a3af7e5..cd10f58 100644 --- a/timestamped/2025-11-13_08-03-00.md +++ b/timestamped/2025-11-13_08-03-00.md @@ -1,3 +1,11 @@ +--- +id: +aliases: [] +title: +tags: + - type/timestamped +dg-publish: true +--- # 2025-11-13 08:03:?? #topic/hobbies/writing diff --git a/timestamped/2025-11-13_08-19-00.md b/timestamped/2025-11-13_08-19-00.md index 8e43287..92fa658 100644 --- a/timestamped/2025-11-13_08-19-00.md +++ b/timestamped/2025-11-13_08-19-00.md @@ -1,3 +1,11 @@ +--- +id: +aliases: [] +title: +tags: + - type/timestamped +dg-publish: true +--- # 2025-11-13 08:19:?? #topic/estimating #occupational diff --git a/timestamped/2025-11-13_20-41-00.md b/timestamped/2025-11-13_20-41-00.md index f1357c8..fd26ad7 100644 --- a/timestamped/2025-11-13_20-41-00.md +++ b/timestamped/2025-11-13_20-41-00.md @@ -1,3 +1,11 @@ +--- +id: +aliases: [] +title: +tags: + - type/timestamped +dg-publish: true +--- # 2025-11-13 20:41:?? #topic/hobbies/shorthand diff --git a/timestamped/2025-12-02_10-40-00.md b/timestamped/2025-12-02_10-40-00.md index 420998d..a281143 100644 --- a/timestamped/2025-12-02_10-40-00.md +++ b/timestamped/2025-12-02_10-40-00.md @@ -1,3 +1,11 @@ +--- +id: +aliases: [] +title: +tags: + - type/timestamped +dg-publish: true +--- # 2025-12-02 10:40:?? #topic/construction/electrical diff --git a/timestamped/2025-12-02_10-57-00.md b/timestamped/2025-12-02_10-57-00.md index b5e529f..218a996 100644 --- a/timestamped/2025-12-02_10-57-00.md +++ b/timestamped/2025-12-02_10-57-00.md @@ -1,3 +1,11 @@ +--- +id: +aliases: [] +title: +tags: + - type/timestamped +dg-publish: true +--- # 2025-12-02 10:57:?? ### Set Notation Example diff --git a/timestamped/2025-12-02_13-20-00.md b/timestamped/2025-12-02_13-20-00.md index 4efb9f6..4806e52 100644 --- a/timestamped/2025-12-02_13-20-00.md +++ b/timestamped/2025-12-02_13-20-00.md @@ -1,3 +1,11 @@ +--- +id: +aliases: [] +title: +tags: + - type/timestamped +dg-publish: true +--- # 2025-12-02 13:20:?? ### Panel Schedule Relationship Diagram diff --git a/timestamped/2025-12-16_09-20-52.md b/timestamped/2025-12-16_09-20-52.md index 4f41ec4..aba18d6 100644 --- a/timestamped/2025-12-16_09-20-52.md +++ b/timestamped/2025-12-16_09-20-52.md @@ -1,3 +1,11 @@ +--- +id: +aliases: [] +title: +tags: + - type/timestamped +dg-publish: true +--- # 2025-12-16 09:20:52 [Probability Management](https://www.probabilitymanagement.org/) diff --git a/timestamped/2025-12-16_20-04-00.md b/timestamped/2025-12-16_20-04-00.md index d2e4c26..d7dec25 100644 --- a/timestamped/2025-12-16_20-04-00.md +++ b/timestamped/2025-12-16_20-04-00.md @@ -1,3 +1,11 @@ +--- +id: +aliases: [] +title: +tags: + - type/timestamped +dg-publish: true +--- # 2025-12-16 20:04:?? ### Metalog Distributions diff --git a/timestamped/2025-12-17_05-39-00.md b/timestamped/2025-12-17_05-39-00.md index 89e1886..73c6692 100644 --- a/timestamped/2025-12-17_05-39-00.md +++ b/timestamped/2025-12-17_05-39-00.md @@ -1,3 +1,11 @@ +--- +id: +aliases: [] +title: +tags: + - type/timestamped +dg-publish: true +--- # 2025-12-17 05:39:?? One aspect of estimating that I find most interesting, diff --git a/timestamped/2025-12-17_12-32-00.md b/timestamped/2025-12-17_12-32-00.md index 58f5f76..ba19a47 100644 --- a/timestamped/2025-12-17_12-32-00.md +++ b/timestamped/2025-12-17_12-32-00.md @@ -1,3 +1,11 @@ +--- +id: +aliases: [] +title: +tags: + - type/timestamped +dg-publish: true +--- # 2025-12-17 12:32:?? #topic/ambiguity diff --git a/timestamped/2025-12-18_08-32-18.md b/timestamped/2025-12-18_08-32-18.md index fed9aff..c2b5377 100644 --- a/timestamped/2025-12-18_08-32-18.md +++ b/timestamped/2025-12-18_08-32-18.md @@ -1,3 +1,11 @@ +--- +id: +aliases: [] +title: +tags: + - type/timestamped +dg-publish: true +--- # 2025-12-18 08:32:18 [[uncertainty-in-construction-estimating]] \ No newline at end of file diff --git a/timestamped/2025-12-18_10-38-00.md b/timestamped/2025-12-18_10-38-00.md index 0c74a4c..c98adad 100644 --- a/timestamped/2025-12-18_10-38-00.md +++ b/timestamped/2025-12-18_10-38-00.md @@ -1,3 +1,11 @@ +--- +id: +aliases: [] +title: +tags: + - type/timestamped +dg-publish: true +--- # 2025-12-18 10:38:?? #topic/meta diff --git a/timestamped/2025-12-18_14-18-00.md b/timestamped/2025-12-18_14-18-00.md index 11a1c8f..47156c4 100644 --- a/timestamped/2025-12-18_14-18-00.md +++ b/timestamped/2025-12-18_14-18-00.md @@ -1,3 +1,11 @@ +--- +id: +aliases: [] +title: +tags: + - type/timestamped +dg-publish: true +--- # 2025-12-18 14:18:?? ### Estimating Golf diff --git a/timestamped/2025-12-18_15-22-00.md b/timestamped/2025-12-18_15-22-00.md index 910afc3..0533dd4 100644 --- a/timestamped/2025-12-18_15-22-00.md +++ b/timestamped/2025-12-18_15-22-00.md @@ -1,3 +1,11 @@ +--- +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 diff --git a/timestamped/2025-12-18_15-30-00.md b/timestamped/2025-12-18_15-30-00.md index b946ad9..4c7c521 100644 --- a/timestamped/2025-12-18_15-30-00.md +++ b/timestamped/2025-12-18_15-30-00.md @@ -1,3 +1,11 @@ +--- +id: +aliases: [] +title: +tags: + - type/timestamped +dg-publish: true +--- # 2025-12-18 15:30:?? [Kip (unit) - Wikipedia](https://en.wikipedia.org/wiki/Kip_\(unit\)) diff --git a/timestamped/2025-12-19_10-44-00.md b/timestamped/2025-12-19_10-44-00.md index 4f1efcc..13553e5 100644 --- a/timestamped/2025-12-19_10-44-00.md +++ b/timestamped/2025-12-19_10-44-00.md @@ -1,3 +1,11 @@ +--- +id: +aliases: [] +title: +tags: + - type/timestamped +dg-publish: true +--- # 2025-12-19 10:44:?? #occupational/takeoff diff --git a/timestamped/2025-12-19_10-44-01.md b/timestamped/2025-12-19_10-44-01.md index b0fc24a..570a10e 100644 --- a/timestamped/2025-12-19_10-44-01.md +++ b/timestamped/2025-12-19_10-44-01.md @@ -1,3 +1,11 @@ +--- +id: +aliases: [] +title: +tags: + - type/timestamped +dg-publish: true +--- # 2025-12-19 10:44:?? #occupational/takeoff diff --git a/timestamped/2026-01-02_10-10-18.md b/timestamped/2026-01-02_10-10-18.md index 17f5c3c..18da16e 100644 --- a/timestamped/2026-01-02_10-10-18.md +++ b/timestamped/2026-01-02_10-10-18.md @@ -1,3 +1,11 @@ +--- +id: +aliases: [] +title: +tags: + - type/timestamped +dg-publish: true +--- # 2026-01-02 10:10:18 ### Harborside Plaza 4 diff --git a/timestamped/2026-01-02_19-21-00.md b/timestamped/2026-01-02_19-21-00.md index b5dad43..efc1d62 100644 --- a/timestamped/2026-01-02_19-21-00.md +++ b/timestamped/2026-01-02_19-21-00.md @@ -1,3 +1,11 @@ +--- +id: +aliases: [] +title: +tags: + - type/timestamped +dg-publish: true +--- # 2026-01-02 19:21:?? Without apparent prompt I was reminded of a practical joke diff --git a/timestamped/2026-01-06_07-47-00.md b/timestamped/2026-01-06_07-47-00.md index d3fd654..e658923 100644 --- a/timestamped/2026-01-06_07-47-00.md +++ b/timestamped/2026-01-06_07-47-00.md @@ -1,3 +1,11 @@ +--- +id: +aliases: [] +title: +tags: + - type/timestamped +dg-publish: true +--- # 2026-01-06 07:47:?? ### _Let Them Theory_ Theory diff --git a/timestamped/2026-01-06_10-00-00.md b/timestamped/2026-01-06_10-00-00.md index 9b1f55c..d0a71b4 100644 --- a/timestamped/2026-01-06_10-00-00.md +++ b/timestamped/2026-01-06_10-00-00.md @@ -1,3 +1,11 @@ +--- +id: +aliases: [] +title: +tags: + - type/timestamped +dg-publish: true +--- # 2026-01-06 10:00:?? Paraphrased Teams conversation with a peer diff --git a/timestamped/2026-01-06_10-57-00.md b/timestamped/2026-01-06_10-57-00.md index 8d09168..16ba9c0 100644 --- a/timestamped/2026-01-06_10-57-00.md +++ b/timestamped/2026-01-06_10-57-00.md @@ -1,3 +1,11 @@ +--- +id: +aliases: [] +title: +tags: + - type/timestamped +dg-publish: true +--- # 2026-01-06 10:57:?? Tracking contractor growth by project square footage diff --git a/timestamped/2026-01-07_06-41-00.md b/timestamped/2026-01-07_06-41-00.md index 71e1c6c..5ca3d9f 100644 --- a/timestamped/2026-01-07_06-41-00.md +++ b/timestamped/2026-01-07_06-41-00.md @@ -1,3 +1,11 @@ +--- +id: +aliases: [] +title: +tags: + - type/timestamped +dg-publish: true +--- # 2026-01-07 06:41:?? > [!quote] _The Shadow of the Torturer_, Chapter 17: "The Challenge" diff --git a/timestamped/2026-01-07_10-03-00.md b/timestamped/2026-01-07_10-03-00.md index 50f5478..298375d 100644 --- a/timestamped/2026-01-07_10-03-00.md +++ b/timestamped/2026-01-07_10-03-00.md @@ -1,3 +1,11 @@ +--- +id: +aliases: [] +title: +tags: + - type/timestamped +dg-publish: true +--- # 2026-01-07 10:03:?? At Ace, "residential" always meant single-family/duplex construction, diff --git a/timestamped/2026-01-07_10-05-00.md b/timestamped/2026-01-07_10-05-00.md index 1e66ae0..a3fb080 100644 --- a/timestamped/2026-01-07_10-05-00.md +++ b/timestamped/2026-01-07_10-05-00.md @@ -1,3 +1,11 @@ +--- +id: +aliases: [] +title: +tags: + - type/timestamped +dg-publish: true +--- # 2026-01-07 10:05:?? See [[pdi-breakdowns#Location]]. diff --git a/timestamped/2026-01-07_10-42-00.md b/timestamped/2026-01-07_10-42-00.md index c0852e8..a07c91d 100644 --- a/timestamped/2026-01-07_10-42-00.md +++ b/timestamped/2026-01-07_10-42-00.md @@ -1,3 +1,11 @@ +--- +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 diff --git a/timestamped/2026-01-07_12-13-00.md b/timestamped/2026-01-07_12-13-00.md index bc9f947..adab515 100644 --- a/timestamped/2026-01-07_12-13-00.md +++ b/timestamped/2026-01-07_12-13-00.md @@ -1,3 +1,11 @@ +--- +id: +aliases: [] +title: +tags: + - type/timestamped +dg-publish: true +--- # 2026-01-07 12:13:?? #occupational #topic/estimating #topic/organization diff --git a/timestamped/2026-01-07_16-03-00.md b/timestamped/2026-01-07_16-03-00.md index cad28df..332c815 100644 --- a/timestamped/2026-01-07_16-03-00.md +++ b/timestamped/2026-01-07_16-03-00.md @@ -1,3 +1,11 @@ +--- +id: +aliases: [] +title: +tags: + - type/timestamped +dg-publish: true +--- # 2026-01-07 16:03:?? #occupational #topic/estimating #topic/organization diff --git a/timestamped/2026-01-08_13-33-34.md b/timestamped/2026-01-08_13-33-34.md index ead382a..666e1f5 100644 --- a/timestamped/2026-01-08_13-33-34.md +++ b/timestamped/2026-01-08_13-33-34.md @@ -1,3 +1,11 @@ +--- +id: +aliases: [] +title: +tags: + - type/timestamped +dg-publish: true +--- # 2026-01-08 13:33:34 ### 2100 Crystal Drive Takeoff Review diff --git a/timestamped/2026-01-09_10-00-03.md b/timestamped/2026-01-09_10-00-03.md index 396b7cf..b0a340b 100644 --- a/timestamped/2026-01-09_10-00-03.md +++ b/timestamped/2026-01-09_10-00-03.md @@ -1,3 +1,11 @@ +--- +id: +aliases: [] +title: +tags: + - type/timestamped +dg-publish: true +--- # 2026-01-09 10:00:03 ### 2100 Crystal Drive diff --git a/timestamped/2026-01-09_12-00-00.md b/timestamped/2026-01-09_12-00-00.md index 1af14ed..fc67132 100644 --- a/timestamped/2026-01-09_12-00-00.md +++ b/timestamped/2026-01-09_12-00-00.md @@ -1,3 +1,11 @@ +--- +id: +aliases: [] +title: +tags: + - type/timestamped +dg-publish: true +--- # 2026-01-09 12:00:?? $$ diff --git a/timestamped/2026-01-09_14-45-00.md b/timestamped/2026-01-09_14-45-00.md index 8bee251..05b45f3 100644 --- a/timestamped/2026-01-09_14-45-00.md +++ b/timestamped/2026-01-09_14-45-00.md @@ -1,3 +1,11 @@ +--- +id: +aliases: [] +title: +tags: + - type/timestamped +dg-publish: true +--- # 2026-01-09 14:45:?? [[bid-price-modeling]] diff --git a/timestamped/2026-01-09_16-28-00.md b/timestamped/2026-01-09_16-28-00.md index 85b6789..c2189ad 100644 --- a/timestamped/2026-01-09_16-28-00.md +++ b/timestamped/2026-01-09_16-28-00.md @@ -1,3 +1,11 @@ +--- +id: +aliases: [] +title: +tags: + - type/timestamped +dg-publish: true +--- # 2026-01-09 16:28:?? ### Occam's razor diff --git a/timestamped/2026-01-11_09-00-00.md b/timestamped/2026-01-11_09-00-00.md index ed7f171..ba82426 100644 --- a/timestamped/2026-01-11_09-00-00.md +++ b/timestamped/2026-01-11_09-00-00.md @@ -1,3 +1,11 @@ +--- +id: +aliases: [] +title: +tags: + - type/timestamped +dg-publish: true +--- # 2026-01-11 09:00:?? [[2026-01-09#2026-01-09 14:45]] diff --git a/timestamped/2026-01-11_11-00-00.md b/timestamped/2026-01-11_11-00-00.md index e9d9af8..f4cd08f 100644 --- a/timestamped/2026-01-11_11-00-00.md +++ b/timestamped/2026-01-11_11-00-00.md @@ -1,3 +1,11 @@ +--- +id: +aliases: [] +title: +tags: + - type/timestamped +dg-publish: true +--- # 2026-01-11 11:00:?? ![[favorite-quotes#"It Takes an Engineer to Build a Bridge that Barely Stands"]] diff --git a/timestamped/2026-01-12_10-00-00.md b/timestamped/2026-01-12_10-00-00.md index 3f3ad4f..0507945 100644 --- a/timestamped/2026-01-12_10-00-00.md +++ b/timestamped/2026-01-12_10-00-00.md @@ -1,6 +1,9 @@ --- id: 2026-01-12T10:00:00-05:00 title: 2026-01-12 10:00:?? +tags: + - type/timestamped +dg-publish: true --- # 2026-01-12 10:00:?? diff --git a/timestamped/2026-01-12_10-42-30.md b/timestamped/2026-01-12_10-42-30.md index 04363f7..2305610 100644 --- a/timestamped/2026-01-12_10-42-30.md +++ b/timestamped/2026-01-12_10-42-30.md @@ -1,6 +1,9 @@ --- id: 2026-01-12T10:42:30-05:00 title: 2026-01-12 10:42:30 +tags: + - type/timestamped +dg-publish: true --- # 2026-01-12 10:42:30 diff --git a/timestamped/2026-01-12_12-23-00.md b/timestamped/2026-01-12_12-23-00.md index 9288037..44989e7 100644 --- a/timestamped/2026-01-12_12-23-00.md +++ b/timestamped/2026-01-12_12-23-00.md @@ -1,6 +1,9 @@ --- id: 2026-01-12T12:23:00-05:00 title: 2026-01-12 12:23:?? +tags: + - type/timestamped +dg-publish: true --- # 2026-01-12 12:23:?? diff --git a/timestamped/2026-01-12_13-02-00.md b/timestamped/2026-01-12_13-02-00.md index 14d7445..db8b944 100644 --- a/timestamped/2026-01-12_13-02-00.md +++ b/timestamped/2026-01-12_13-02-00.md @@ -1,6 +1,9 @@ --- id: 2026-01-12T13:02:00-05:00 title: 2026-01-12 13:02:?? +tags: + - type/timestamped +dg-publish: true --- # 2026-01-12 13:02:?? diff --git a/timestamped/2026-01-15_08-11-10.md b/timestamped/2026-01-15_08-11-10.md index 996f4e4..aa156a7 100644 --- a/timestamped/2026-01-15_08-11-10.md +++ b/timestamped/2026-01-15_08-11-10.md @@ -1,3 +1,11 @@ +--- +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]] diff --git a/timestamped/2026-01-15_08-15-00.md b/timestamped/2026-01-15_08-15-00.md index b56bda2..f04d4bc 100644 --- a/timestamped/2026-01-15_08-15-00.md +++ b/timestamped/2026-01-15_08-15-00.md @@ -1,3 +1,11 @@ +--- +id: +aliases: [] +title: +tags: + - type/timestamped +dg-publish: true +--- # 2026-01-15 08:15:?? [[2025-11-13#2025-11-13 08:19]] diff --git a/timestamped/2026-01-19_11-57-39.md b/timestamped/2026-01-19_11-57-39.md index 41b242c..217768b 100644 --- a/timestamped/2026-01-19_11-57-39.md +++ b/timestamped/2026-01-19_11-57-39.md @@ -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 diff --git a/timestamped/2026-01-19_12-32-00.md b/timestamped/2026-01-19_12-32-00.md index a9aeb7b..14db51c 100644 --- a/timestamped/2026-01-19_12-32-00.md +++ b/timestamped/2026-01-19_12-32-00.md @@ -1,6 +1,9 @@ --- id: 2026-01-19T12:32:00-05:00 title: 2026-01-19 12:32:?? +tags: + - type/timestamped +dg-publish: true --- # 2026-01-19 12:32:?? diff --git a/timestamped/2026-01-19_18-13-00.md b/timestamped/2026-01-19_18-13-00.md index 4c11412..2c5b395 100644 --- a/timestamped/2026-01-19_18-13-00.md +++ b/timestamped/2026-01-19_18-13-00.md @@ -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:?? diff --git a/timestamped/2026-01-20_09-09-12.md b/timestamped/2026-01-20_09-09-12.md index 8cb35ca..9ddea9a 100644 --- a/timestamped/2026-01-20_09-09-12.md +++ b/timestamped/2026-01-20_09-09-12.md @@ -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 diff --git a/timestamped/2026-01-20_10-10-00.md b/timestamped/2026-01-20_10-10-00.md index 71e2f31..650d334 100644 --- a/timestamped/2026-01-20_10-10-00.md +++ b/timestamped/2026-01-20_10-10-00.md @@ -1,6 +1,9 @@ --- id: 2026-01-20T10:10:00-05:00 title: 2026-01-20 10:10:?? +tags: + - type/timestamped +dg-publish: true --- # 2026-01-20 10:10:?? diff --git a/timestamped/2026-01-20_14-25-00.md b/timestamped/2026-01-20_14-25-00.md index 7b8c428..1f1a7d0 100644 --- a/timestamped/2026-01-20_14-25-00.md +++ b/timestamped/2026-01-20_14-25-00.md @@ -1,6 +1,9 @@ --- id: 2026-01-20T14:25:00-05:00 title: 2026-01-20 14:25:?? +tags: + - type/timestamped +dg-publish: true --- # 2026-01-20 14:25:?? diff --git a/timestamped/2026-01-22_09-55-42.md b/timestamped/2026-01-22_09-55-42.md index 3c4b020..bbe6a2d 100644 --- a/timestamped/2026-01-22_09-55-42.md +++ b/timestamped/2026-01-22_09-55-42.md @@ -1,6 +1,9 @@ --- id: 2026-01-22T09:55:42-05:00 title: 2026-01-22 09:55:42 +tags: + - type/timestamped +dg-publish: true --- # 2026-01-22 09:55:42 diff --git a/timestamped/2026-01-22_11-58-00.md b/timestamped/2026-01-22_11-58-00.md index c665ee3..fc157b5 100644 --- a/timestamped/2026-01-22_11-58-00.md +++ b/timestamped/2026-01-22_11-58-00.md @@ -1,6 +1,9 @@ --- id: 2026-01-22T11:58:00-05:00 title: 2026-01-22 11:58:?? +tags: + - type/timestamped +dg-publish: true --- # 2026-01-22 11:58:?? diff --git a/timestamped/2026-01-22_14-56-00.md b/timestamped/2026-01-22_14-56-00.md index 00edee4..e61cbd2 100644 --- a/timestamped/2026-01-22_14-56-00.md +++ b/timestamped/2026-01-22_14-56-00.md @@ -1,6 +1,9 @@ --- id: 2026-01-22T14:56:00-05:00 title: 2026-01-22 14:56:?? +tags: + - type/timestamped +dg-publish: true --- # 2026-01-22 14:56:?? diff --git a/timestamped/2026-01-23_08-18-53.md b/timestamped/2026-01-23_08-18-53.md index 120305b..47c9e81 100644 --- a/timestamped/2026-01-23_08-18-53.md +++ b/timestamped/2026-01-23_08-18-53.md @@ -1,6 +1,9 @@ --- id: 2026-01-23T08:18:53-05:00 title: 2026-01-23 08:18:53 +tags: + - type/timestamped +dg-publish: true --- # 2026-01-23 08:18:53 diff --git a/timestamped/2026-01-23_12-34-00.md b/timestamped/2026-01-23_12-34-00.md index 8477c31..a55fd41 100644 --- a/timestamped/2026-01-23_12-34-00.md +++ b/timestamped/2026-01-23_12-34-00.md @@ -1,6 +1,9 @@ --- id: 2026-01-23T12:34:00-05:00 title: 2026-01-23 12:34:?? +tags: + - type/timestamped +dg-publish: true --- # 2026-01-23 12:34:?? diff --git a/timestamped/2026-01-25_18-46-00.md b/timestamped/2026-01-25_18-46-00.md index d658757..5cc6377 100644 --- a/timestamped/2026-01-25_18-46-00.md +++ b/timestamped/2026-01-25_18-46-00.md @@ -1,6 +1,9 @@ --- id: 2026-01-25T18:46:00-05:00 title: 2026-01-25 18:46:?? +tags: + - type/timestamped +dg-publish: true --- # 2026-01-25 18:46:?? diff --git a/timestamped/2026-01-25_21-02-00.md b/timestamped/2026-01-25_21-02-00.md index 6a4b411..41d3361 100644 --- a/timestamped/2026-01-25_21-02-00.md +++ b/timestamped/2026-01-25_21-02-00.md @@ -1,6 +1,9 @@ --- id: 2026-01-25T21:02:00-05:00 title: 2026-01-25 21:02:?? +tags: + - type/timestamped +dg-publish: true --- # 2026-01-25 21:02:?? diff --git a/timestamped/2026-01-25_22-59-00.md b/timestamped/2026-01-25_22-59-00.md index 5107291..e652017 100644 --- a/timestamped/2026-01-25_22-59-00.md +++ b/timestamped/2026-01-25_22-59-00.md @@ -1,6 +1,9 @@ --- id: 2026-01-25T22:59:00-05:00 title: 2026-01-25 22:59:?? +tags: + - type/timestamped +dg-publish: true --- # 2026-01-25 22:59:?? diff --git a/timestamped/2026-01-28_09-51-08.md b/timestamped/2026-01-28_09-51-08.md index 74c8f6a..7f48cf3 100644 --- a/timestamped/2026-01-28_09-51-08.md +++ b/timestamped/2026-01-28_09-51-08.md @@ -1,6 +1,9 @@ --- id: 2026-01-28T09:51:08-05:00 title: 2026-01-28 09:51:08 +tags: + - type/timestamped +dg-publish: true --- # 2026-01-28 09:51:08 diff --git a/timestamped/2026-01-28_10-02-00.md b/timestamped/2026-01-28_10-02-00.md index 9e7396e..f563197 100644 --- a/timestamped/2026-01-28_10-02-00.md +++ b/timestamped/2026-01-28_10-02-00.md @@ -1,6 +1,9 @@ --- id: 2026-01-28T10:02:00-05:00 title: 2026-01-28 10:02:?? +tags: + - type/timestamped +dg-publish: true --- # 2026-01-28 10:02:?? diff --git a/timestamped/2026-01-29_10-07-37.md b/timestamped/2026-01-29_10-07-37.md index 9831447..9fec1f1 100644 --- a/timestamped/2026-01-29_10-07-37.md +++ b/timestamped/2026-01-29_10-07-37.md @@ -1,6 +1,9 @@ --- id: 2026-01-29T10:07:37-05:00 title: 2026-01-29 10:07:37 +tags: + - type/timestamped +dg-publish: true --- # 2026-01-29 10:07:37 diff --git a/timestamped/2026-01-29_17-57-00.md b/timestamped/2026-01-29_17-57-00.md index 84367bd..e43b577 100644 --- a/timestamped/2026-01-29_17-57-00.md +++ b/timestamped/2026-01-29_17-57-00.md @@ -1,6 +1,9 @@ --- id: 2026-01-29T17:57:00-05:00 title: 2026-01-29 17:57:?? +tags: + - type/timestamped +dg-publish: true --- # 2026-01-29 17:57:?? diff --git a/timestamped/2026-01-30_08-44-29.md b/timestamped/2026-01-30_08-44-29.md index 9fc672b..ebbc961 100644 --- a/timestamped/2026-01-30_08-44-29.md +++ b/timestamped/2026-01-30_08-44-29.md @@ -1,6 +1,9 @@ --- id: 2026-01-30T08:44:29-05:00 title: 2026-01-30 08:44:29 +tags: + - type/timestamped +dg-publish: true --- # 2026-01-30 08:44:29 diff --git a/timestamped/2026-01-30_09-06-00.md b/timestamped/2026-01-30_09-06-00.md index b2d5178..2a988c7 100644 --- a/timestamped/2026-01-30_09-06-00.md +++ b/timestamped/2026-01-30_09-06-00.md @@ -1,6 +1,9 @@ --- id: 2026-01-30T09:06:00-05:00 title: 2026-01-30 09:06:?? +tags: + - type/timestamped +dg-publish: true --- # 2026-01-30 09:06:?? diff --git a/timestamped/2026-01-30_13-42-00.md b/timestamped/2026-01-30_13-42-00.md index 46ef291..ff60260 100644 --- a/timestamped/2026-01-30_13-42-00.md +++ b/timestamped/2026-01-30_13-42-00.md @@ -1,6 +1,11 @@ --- id: 2026-01-30T13:42:00-05:00 +aliases: [] title: 2026-01-30 13:42:?? +tags: + - authorship/original + - topic/personal-productivity + - type/timestamped --- # 2026-01-30 13:42:?? @@ -25,4 +30,4 @@ _and the will to contradict you_ is worthless. If the effort to _communicate_ your instructions exceeds the effort to perform them, -you will always do the task yourself. \ No newline at end of file +you will always do the task yourself. diff --git a/timestamped/2026-01-30_16-29-00.md b/timestamped/2026-01-30_16-29-00.md index d65ae90..79c331b 100644 --- a/timestamped/2026-01-30_16-29-00.md +++ b/timestamped/2026-01-30_16-29-00.md @@ -1,11 +1,13 @@ --- id: 2026-01-30T16:29:00-05:00 +aliases: [] title: 2026-01-30 16:29:?? +tags: + - authorship/original + - topic/math/statistics --- # 2026-01-30 16:29:?? -#topic/math/statistics - ### Laplace's Rule of Succession (LRS) > [!info] @@ -29,4 +31,4 @@ $n$ times in a row. There is a 93.75% chance that the median of a population is between the smallest and largest values -in any random sample of five from that population. \ No newline at end of file +in any random sample of five from that population. diff --git a/timestamped/2026-01-30_18-33-00.md b/timestamped/2026-01-30_18-33-00.md index 2a647da..4650a90 100644 --- a/timestamped/2026-01-30_18-33-00.md +++ b/timestamped/2026-01-30_18-33-00.md @@ -1,11 +1,14 @@ --- id: 2026-01-30T18:33:00-05:00 +aliases: [] title: 2026-01-30 18:33:?? +tags: + - authorship/original + - destiny/permanent + - topic/personal-productivity --- # 2026-01-30 18:33:?? -#topic/personal-productivity - Why is it that I find it so easy, even compulsory, to clean my house while working from home, even after returning from work on-site? diff --git a/timestamped/2026-01-31_12-48-00.md b/timestamped/2026-01-31_12-48-00.md index c8cbbaf..25ceaab 100644 --- a/timestamped/2026-01-31_12-48-00.md +++ b/timestamped/2026-01-31_12-48-00.md @@ -12,7 +12,7 @@ dg-publish: true --- # 2026-01-31 12:48:00 -Follow-up to [[2026-01-19#2026-01-19 11:57]] +Follow-up to [[2026-01-19_11-57-39]] a **natural-language parser** could easily determine where hyphens should be replaced with em dashes. diff --git a/timestamped/2026-02-04_08-07-00.md b/timestamped/2026-02-04_08-07-00.md index b2080d7..2a6c0fd 100644 --- a/timestamped/2026-02-04_08-07-00.md +++ b/timestamped/2026-02-04_08-07-00.md @@ -15,6 +15,8 @@ daily: "[[2026-02-04]]" ## Questions for ConEst +[[pdi-estimating#Construction Estimating (ConEst)]] + ### Purpose of ConEst What is the purpose of ConEst? diff --git a/timestamped/2026-02-04_19-35-00.md b/timestamped/2026-02-04_19-35-00.md index 52b90e9..5832bf8 100644 --- a/timestamped/2026-02-04_19-35-00.md +++ b/timestamped/2026-02-04_19-35-00.md @@ -14,7 +14,7 @@ daily: "[[2026-02-04]]" ## Time Interval Conversion -In [[2026-01-09#2026-01-09 12:00]] +In [[2026-01-09_12-00-00]] I defined time intervals according to averages which are true of the Gregorian calendar for $\lim\limits_{t\to\infty}$, but which are not so appropriate for a human lifetime scale. diff --git a/timestamped/2026-02-17_13-13-06.md b/timestamped/2026-02-17_13-13-06.md index c4a77c1..218b713 100644 --- a/timestamped/2026-02-17_13-13-06.md +++ b/timestamped/2026-02-17_13-13-06.md @@ -16,7 +16,7 @@ yearly: "[[2026]]" --- # 2026-02-17 13:13:06 -Relevant to [[2025-11-21_10-11-00#2025-11-21 10:11:??|2025-11-21 10:11:??]] +Relevant to [[2025-11-21_10-11-00]] Today I spoke to a peer about [[earned-value-management#Earned Value Management|earned value management]]: From e831c38cf87704e870cc294a1e0368c6a74d7346 Mon Sep 17 00:00:00 2001 From: Zane Meyers Date: Wed, 25 Feb 2026 12:41:36 -0500 Subject: [PATCH 3/6] vault backup: 2026-02-25 12:41:35 --- ....md => nfpa-70_518_assembly-occupancies.md | 28 ++- nfpa-70_590_temporary-installations.md | 223 ++++++++++++++++++ nfpa-70_national-electric-code.md | 4 +- 3 files changed, 242 insertions(+), 13 deletions(-) rename nfpa-70_518.md => nfpa-70_518_assembly-occupancies.md (90%) create mode 100644 nfpa-70_590_temporary-installations.md diff --git a/nfpa-70_518.md b/nfpa-70_518_assembly-occupancies.md similarity index 90% rename from nfpa-70_518.md rename to nfpa-70_518_assembly-occupancies.md index 7813336..d35d72a 100644 --- a/nfpa-70_518.md +++ b/nfpa-70_518_assembly-occupancies.md @@ -15,7 +15,13 @@ tags: ### 518.1 Scope. -Except for the assembly occupancies explicitly covered by 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. +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. @@ -31,7 +37,7 @@ Assembly occupancies shall include, but not be limited to, the following: * Conference rooms * Courtrooms * Dance halls -* Dining and drinking facilities Restaurants +* Dining and drinking facilities * Exhibition halls * Gymnasiums * Mortuary chapels @@ -40,6 +46,7 @@ Assembly occupancies shall include, but not be limited to, the following: * Places of awaiting transportation * Places of religious worship * Pool rooms +* Restaurants * Skating rinks #### 518.2(B) Multiple Occupancies. @@ -66,7 +73,9 @@ In exhibition halls used for display booths, as in trade shows, the temporary wi 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 +> 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. @@ -80,14 +89,11 @@ 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 - -* (4) Fire alarm circuits --- Article 760 +> +> * (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. diff --git a/nfpa-70_590_temporary-installations.md b/nfpa-70_590_temporary-installations.md new file mode 100644 index 0000000..86ad973 --- /dev/null +++ b/nfpa-70_590_temporary-installations.md @@ -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. diff --git a/nfpa-70_national-electric-code.md b/nfpa-70_national-electric-code.md index 8a193ce..45fec8f 100644 --- a/nfpa-70_national-electric-code.md +++ b/nfpa-70_national-electric-code.md @@ -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 From 422c6a1d3492538c1eedac14d9f98ba1e567d744 Mon Sep 17 00:00:00 2001 From: Zane Meyers Date: Wed, 25 Feb 2026 12:52:50 -0500 Subject: [PATCH 4/6] vault backup: 2026-02-25 12:52:50 --- timestamped/2025-11-10_10-40-00.md | 5 +++-- timestamped/2025-11-10_11-14-00.md | 4 ++-- timestamped/2025-11-10_15-15-00.md | 4 ++-- timestamped/2025-11-10_20-00-00.md | 5 +++-- timestamped/2025-11-11_06-06-00.md | 4 ++-- timestamped/2025-11-11_14-41-00.md | 5 +++-- timestamped/2025-11-13_08-03-00.md | 3 +-- timestamped/2025-11-13_08-19-00.md | 4 ++-- timestamped/2025-11-13_20-41-00.md | 3 +-- timestamped/2025-11-20_08-46-00.md | 5 ++--- timestamped/2025-11-21_10-11-00.md | 3 +-- timestamped/2025-12-02_10-40-00.md | 3 +-- timestamped/2025-12-03_15-54-22.md | 4 ++-- timestamped/2025-12-10_10-45-19.md | 5 +++-- timestamped/2025-12-17_12-32-00.md | 3 +-- timestamped/2025-12-18_10-38-00.md | 3 +-- timestamped/2025-12-19_10-44-00.md | 12 +----------- timestamped/2025-12-19_10-44-01.md | 3 +-- timestamped/2026-01-07_12-13-00.md | 5 +++-- timestamped/2026-01-07_16-03-00.md | 5 +++-- timestamped/2026-01-12_10-00-00.md | 3 +-- timestamped/2026-01-12_10-42-30.md | 3 +-- timestamped/2026-01-12_12-23-00.md | 3 +-- timestamped/2026-01-12_13-02-00.md | 3 +-- timestamped/2026-01-13_11-28-14.md | 3 +-- timestamped/2026-01-14_13-27-20.md | 3 +-- timestamped/2026-01-19_12-32-00.md | 4 ++-- timestamped/2026-01-22_09-55-42.md | 3 +-- timestamped/2026-01-22_11-58-00.md | 3 +-- timestamped/2026-01-22_14-56-00.md | 3 +-- timestamped/2026-01-25_18-46-00.md | 3 +-- timestamped/2026-01-27_17-31-00.md | 3 +-- timestamped/2026-01-28_09-51-08.md | 3 +-- timestamped/2026-01-28_10-02-00.md | 3 +-- timestamped/2026-01-29_10-07-37.md | 3 +-- timestamped/2026-01-29_17-57-00.md | 3 +-- timestamped/2026-01-30_08-44-29.md | 3 +-- timestamped/2026-01-30_09-06-00.md | 3 +-- 38 files changed, 57 insertions(+), 86 deletions(-) diff --git a/timestamped/2025-11-10_10-40-00.md b/timestamped/2025-11-10_10-40-00.md index b3345cc..c72566d 100644 --- a/timestamped/2025-11-10_10-40-00.md +++ b/timestamped/2025-11-10_10-40-00.md @@ -4,12 +4,13 @@ aliases: [] title: tags: - type/timestamped + - topic/estimating + - occupational + - original-format/digital-text dg-publish: true --- # 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_, diff --git a/timestamped/2025-11-10_11-14-00.md b/timestamped/2025-11-10_11-14-00.md index 2f0c578..809db21 100644 --- a/timestamped/2025-11-10_11-14-00.md +++ b/timestamped/2025-11-10_11-14-00.md @@ -4,12 +4,12 @@ aliases: [] title: tags: - type/timestamped + - occupational/takeoff + - original-format/digital-text dg-publish: true --- # 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: diff --git a/timestamped/2025-11-10_15-15-00.md b/timestamped/2025-11-10_15-15-00.md index a14a6fa..697ccd0 100644 --- a/timestamped/2025-11-10_15-15-00.md +++ b/timestamped/2025-11-10_15-15-00.md @@ -4,14 +4,14 @@ aliases: [] title: tags: - type/timestamped + - topic/construction/electrical + - original-format/digital-text dg-publish: true --- # 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. diff --git a/timestamped/2025-11-10_20-00-00.md b/timestamped/2025-11-10_20-00-00.md index 7bf2095..b3332c2 100644 --- a/timestamped/2025-11-10_20-00-00.md +++ b/timestamped/2025-11-10_20-00-00.md @@ -4,14 +4,15 @@ aliases: [] title: tags: - type/timestamped + - topic/estimating + - occupational + - original-format/typewritten-print dg-publish: true --- # 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 diff --git a/timestamped/2025-11-11_06-06-00.md b/timestamped/2025-11-11_06-06-00.md index 111327b..87063d5 100644 --- a/timestamped/2025-11-11_06-06-00.md +++ b/timestamped/2025-11-11_06-06-00.md @@ -4,14 +4,14 @@ aliases: [] title: tags: - type/timestamped + - topic/estimating + - original-format/typewritten-print dg-publish: true --- # 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, diff --git a/timestamped/2025-11-11_14-41-00.md b/timestamped/2025-11-11_14-41-00.md index 25a519e..383bcaa 100644 --- a/timestamped/2025-11-11_14-41-00.md +++ b/timestamped/2025-11-11_14-41-00.md @@ -4,12 +4,13 @@ aliases: [] title: tags: - type/timestamped + - topic/estimating + - topic/transparency + - original-format/digital-text dg-publish: true --- # 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. diff --git a/timestamped/2025-11-13_08-03-00.md b/timestamped/2025-11-13_08-03-00.md index cd10f58..e9e1e27 100644 --- a/timestamped/2025-11-13_08-03-00.md +++ b/timestamped/2025-11-13_08-03-00.md @@ -4,12 +4,11 @@ aliases: [] title: tags: - type/timestamped + - topic/hobbies/writing dg-publish: true --- # 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. diff --git a/timestamped/2025-11-13_08-19-00.md b/timestamped/2025-11-13_08-19-00.md index 92fa658..d92a9f9 100644 --- a/timestamped/2025-11-13_08-19-00.md +++ b/timestamped/2025-11-13_08-19-00.md @@ -4,12 +4,12 @@ aliases: [] title: tags: - type/timestamped + - topic/estimating + - occupational dg-publish: true --- # 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. diff --git a/timestamped/2025-11-13_20-41-00.md b/timestamped/2025-11-13_20-41-00.md index fd26ad7..ff57545 100644 --- a/timestamped/2025-11-13_20-41-00.md +++ b/timestamped/2025-11-13_20-41-00.md @@ -4,12 +4,11 @@ aliases: [] title: tags: - type/timestamped + - topic/hobbies/shorthand dg-publish: true --- # 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. diff --git a/timestamped/2025-11-20_08-46-00.md b/timestamped/2025-11-20_08-46-00.md index 0bbdb03..022b8a3 100644 --- a/timestamped/2025-11-20_08-46-00.md +++ b/timestamped/2025-11-20_08-46-00.md @@ -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$) diff --git a/timestamped/2025-11-21_10-11-00.md b/timestamped/2025-11-21_10-11-00.md index 1669835..4dfd9f3 100644 --- a/timestamped/2025-11-21_10-11-00.md +++ b/timestamped/2025-11-21_10-11-00.md @@ -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 > diff --git a/timestamped/2025-12-02_10-40-00.md b/timestamped/2025-12-02_10-40-00.md index a281143..d8a12cd 100644 --- a/timestamped/2025-12-02_10-40-00.md +++ b/timestamped/2025-12-02_10-40-00.md @@ -4,12 +4,11 @@ aliases: [] title: tags: - type/timestamped + - topic/construction/electrical dg-publish: true --- # 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") diff --git a/timestamped/2025-12-03_15-54-22.md b/timestamped/2025-12-03_15-54-22.md index da49a38..8c6202d 100644 --- a/timestamped/2025-12-03_15-54-22.md +++ b/timestamped/2025-12-03_15-54-22.md @@ -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 diff --git a/timestamped/2025-12-10_10-45-19.md b/timestamped/2025-12-10_10-45-19.md index bb5e742..709e16e 100644 --- a/timestamped/2025-12-10_10-45-19.md +++ b/timestamped/2025-12-10_10-45-19.md @@ -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 diff --git a/timestamped/2025-12-17_12-32-00.md b/timestamped/2025-12-17_12-32-00.md index ba19a47..641c7a1 100644 --- a/timestamped/2025-12-17_12-32-00.md +++ b/timestamped/2025-12-17_12-32-00.md @@ -4,12 +4,11 @@ aliases: [] title: tags: - type/timestamped + - topic/ambiguity dg-publish: true --- # 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] diff --git a/timestamped/2025-12-18_10-38-00.md b/timestamped/2025-12-18_10-38-00.md index c98adad..2357410 100644 --- a/timestamped/2025-12-18_10-38-00.md +++ b/timestamped/2025-12-18_10-38-00.md @@ -4,12 +4,11 @@ aliases: [] title: tags: - type/timestamped + - topic/meta dg-publish: true --- # 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 diff --git a/timestamped/2025-12-19_10-44-00.md b/timestamped/2025-12-19_10-44-00.md index 13553e5..d632c4e 100644 --- a/timestamped/2025-12-19_10-44-00.md +++ b/timestamped/2025-12-19_10-44-00.md @@ -4,22 +4,12 @@ aliases: [] title: tags: - type/timestamped + - occupational/takeoff dg-publish: true --- # 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 - -> [!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 \ No newline at end of file diff --git a/timestamped/2025-12-19_10-44-01.md b/timestamped/2025-12-19_10-44-01.md index 570a10e..4ec6b59 100644 --- a/timestamped/2025-12-19_10-44-01.md +++ b/timestamped/2025-12-19_10-44-01.md @@ -4,12 +4,11 @@ aliases: [] title: tags: - type/timestamped + - occupational/takeoff dg-publish: true --- # 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. diff --git a/timestamped/2026-01-07_12-13-00.md b/timestamped/2026-01-07_12-13-00.md index adab515..24ae634 100644 --- a/timestamped/2026-01-07_12-13-00.md +++ b/timestamped/2026-01-07_12-13-00.md @@ -4,12 +4,13 @@ aliases: [] title: tags: - type/timestamped + - occupational + - topic/estimating + - topic/organization dg-publish: true --- # 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 diff --git a/timestamped/2026-01-07_16-03-00.md b/timestamped/2026-01-07_16-03-00.md index 332c815..5f291f3 100644 --- a/timestamped/2026-01-07_16-03-00.md +++ b/timestamped/2026-01-07_16-03-00.md @@ -4,12 +4,13 @@ aliases: [] title: tags: - type/timestamped + - occupational + - topic/estimating + - topic/organization dg-publish: true --- # 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. diff --git a/timestamped/2026-01-12_10-00-00.md b/timestamped/2026-01-12_10-00-00.md index 0507945..b890cd1 100644 --- a/timestamped/2026-01-12_10-00-00.md +++ b/timestamped/2026-01-12_10-00-00.md @@ -3,12 +3,11 @@ 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. diff --git a/timestamped/2026-01-12_10-42-30.md b/timestamped/2026-01-12_10-42-30.md index 2305610..feffa68 100644 --- a/timestamped/2026-01-12_10-42-30.md +++ b/timestamped/2026-01-12_10-42-30.md @@ -3,12 +3,11 @@ 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 diff --git a/timestamped/2026-01-12_12-23-00.md b/timestamped/2026-01-12_12-23-00.md index 44989e7..8ab583c 100644 --- a/timestamped/2026-01-12_12-23-00.md +++ b/timestamped/2026-01-12_12-23-00.md @@ -3,12 +3,11 @@ 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. diff --git a/timestamped/2026-01-12_13-02-00.md b/timestamped/2026-01-12_13-02-00.md index db8b944..28379b1 100644 --- a/timestamped/2026-01-12_13-02-00.md +++ b/timestamped/2026-01-12_13-02-00.md @@ -3,12 +3,11 @@ 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. diff --git a/timestamped/2026-01-13_11-28-14.md b/timestamped/2026-01-13_11-28-14.md index ed0832e..ba9a688 100644 --- a/timestamped/2026-01-13_11-28-14.md +++ b/timestamped/2026-01-13_11-28-14.md @@ -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 diff --git a/timestamped/2026-01-14_13-27-20.md b/timestamped/2026-01-14_13-27-20.md index e1f9703..ae7b4bb 100644 --- a/timestamped/2026-01-14_13-27-20.md +++ b/timestamped/2026-01-14_13-27-20.md @@ -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 diff --git a/timestamped/2026-01-19_12-32-00.md b/timestamped/2026-01-19_12-32-00.md index 14db51c..ac59236 100644 --- a/timestamped/2026-01-19_12-32-00.md +++ b/timestamped/2026-01-19_12-32-00.md @@ -3,12 +3,12 @@ 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) diff --git a/timestamped/2026-01-22_09-55-42.md b/timestamped/2026-01-22_09-55-42.md index bbe6a2d..fff9beb 100644 --- a/timestamped/2026-01-22_09-55-42.md +++ b/timestamped/2026-01-22_09-55-42.md @@ -3,12 +3,11 @@ id: 2026-01-22T09:55:42-05:00 title: 2026-01-22 09:55:42 tags: - type/timestamped + - occupational dg-publish: true --- # 2026-01-22 09:55:42 -#occupational - The lighting drawings for 450-460 James Robertson Parkway Phase II (fka James Roberston Pkwy Mixed Use Development) diff --git a/timestamped/2026-01-22_11-58-00.md b/timestamped/2026-01-22_11-58-00.md index fc157b5..ea46813 100644 --- a/timestamped/2026-01-22_11-58-00.md +++ b/timestamped/2026-01-22_11-58-00.md @@ -3,12 +3,11 @@ id: 2026-01-22T11:58:00-05:00 title: 2026-01-22 11:58:?? tags: - type/timestamped + - occupational dg-publish: true --- # 2026-01-22 11:58:?? -#occupational - ### 463 Davison Contract Dates [[463-davison-ave-ne]] diff --git a/timestamped/2026-01-22_14-56-00.md b/timestamped/2026-01-22_14-56-00.md index e61cbd2..a5dd829 100644 --- a/timestamped/2026-01-22_14-56-00.md +++ b/timestamped/2026-01-22_14-56-00.md @@ -3,12 +3,11 @@ id: 2026-01-22T14:56:00-05:00 title: 2026-01-22 14:56:?? tags: - type/timestamped + - topic/estimating dg-publish: true --- # 2026-01-22 14:56:?? -#topic/estimating - ### Accurate Budget Vs. Accurate BOM #### Quote diff --git a/timestamped/2026-01-25_18-46-00.md b/timestamped/2026-01-25_18-46-00.md index 5cc6377..8ae6b6c 100644 --- a/timestamped/2026-01-25_18-46-00.md +++ b/timestamped/2026-01-25_18-46-00.md @@ -3,12 +3,11 @@ id: 2026-01-25T18:46:00-05:00 title: 2026-01-25 18:46:?? tags: - type/timestamped + - topic/finance dg-publish: true --- # 2026-01-25 18:46:?? -#topic/finance - ### Calculating Monthly Principal & Interest Payment For a **fixed-rate, fully-amortizing mortgage**, diff --git a/timestamped/2026-01-27_17-31-00.md b/timestamped/2026-01-27_17-31-00.md index f40dd86..4367b79 100644 --- a/timestamped/2026-01-27_17-31-00.md +++ b/timestamped/2026-01-27_17-31-00.md @@ -7,12 +7,11 @@ tags: - destiny/permanent - status/draft - type/timestamped + - topic/hobbies/reading dg-publish: true --- # 2026-01-27 17:31:?? -#topic/hobbies/reading - ### BLAME! Coelacanth Follow-up to [[2026-01-26#BLAME! Coelacanth]] diff --git a/timestamped/2026-01-28_09-51-08.md b/timestamped/2026-01-28_09-51-08.md index 7f48cf3..6d1fafe 100644 --- a/timestamped/2026-01-28_09-51-08.md +++ b/timestamped/2026-01-28_09-51-08.md @@ -3,12 +3,11 @@ id: 2026-01-28T09:51:08-05:00 title: 2026-01-28 09:51:08 tags: - type/timestamped + - occupational dg-publish: true --- # 2026-01-28 09:51:08 -#occupational - ### ConEst OneNote Template The ConEst OneNote template concept diff --git a/timestamped/2026-01-28_10-02-00.md b/timestamped/2026-01-28_10-02-00.md index f563197..b4a5246 100644 --- a/timestamped/2026-01-28_10-02-00.md +++ b/timestamped/2026-01-28_10-02-00.md @@ -3,12 +3,11 @@ id: 2026-01-28T10:02:00-05:00 title: 2026-01-28 10:02:?? tags: - type/timestamped + - topic/meta dg-publish: true --- # 2026-01-28 10:02:?? -#topic/meta - I'm tempted to replace \[\[daily-notes\]\] with timestamped notes from core plugins Unique Note Creator, however the utility of the calendar widget is hard to concede. diff --git a/timestamped/2026-01-29_10-07-37.md b/timestamped/2026-01-29_10-07-37.md index 9fec1f1..0a33474 100644 --- a/timestamped/2026-01-29_10-07-37.md +++ b/timestamped/2026-01-29_10-07-37.md @@ -3,12 +3,11 @@ id: 2026-01-29T10:07:37-05:00 title: 2026-01-29 10:07:37 tags: - type/timestamped + - topic/estimating dg-publish: true --- # 2026-01-29 10:07:37 -#topic/estimating - A peer's senior, expressing frustration, told them that it if they disagree with an instruction, they must have a reason, diff --git a/timestamped/2026-01-29_17-57-00.md b/timestamped/2026-01-29_17-57-00.md index e43b577..08e86e2 100644 --- a/timestamped/2026-01-29_17-57-00.md +++ b/timestamped/2026-01-29_17-57-00.md @@ -3,12 +3,11 @@ id: 2026-01-29T17:57:00-05:00 title: 2026-01-29 17:57:?? tags: - type/timestamped + - topic/finance dg-publish: true --- # 2026-01-29 17:57:?? -#topic/finance - ### Calculating Utility of Above-Minimum Mortgage Payment See [[2026-01-25#Calculating Monthly Principal & Interest Payment]]. diff --git a/timestamped/2026-01-30_08-44-29.md b/timestamped/2026-01-30_08-44-29.md index ebbc961..0a63ce2 100644 --- a/timestamped/2026-01-30_08-44-29.md +++ b/timestamped/2026-01-30_08-44-29.md @@ -3,12 +3,11 @@ id: 2026-01-30T08:44:29-05:00 title: 2026-01-30 08:44:29 tags: - type/timestamped + - topic/meta dg-publish: true --- # 2026-01-30 08:44:29 -#topic/meta - Follow-up to [[2026-01-28_10-02-00]]. I really would like to implement timestamped notes, diff --git a/timestamped/2026-01-30_09-06-00.md b/timestamped/2026-01-30_09-06-00.md index 2a988c7..8aa6c94 100644 --- a/timestamped/2026-01-30_09-06-00.md +++ b/timestamped/2026-01-30_09-06-00.md @@ -3,12 +3,11 @@ id: 2026-01-30T09:06:00-05:00 title: 2026-01-30 09:06:?? tags: - type/timestamped + - topic/meta dg-publish: true --- # 2026-01-30 09:06:?? -#topic/meta - I tried the Smart Connections community plugin. I can't imagine who it could be useful for. It seems to just identify large blocks of similar content, From 75b84fda8010cb2f7e1900a8e42d398c541c847f Mon Sep 17 00:00:00 2001 From: Zane Meyers Date: Wed, 25 Feb 2026 12:58:18 -0500 Subject: [PATCH 5/6] vault backup: 2026-02-25 12:58:18 --- 2025-11-13_08-19-01.md | 18 ++++++++++++++++++ 2026-01-12_13-02-01.md | 20 ++++++++++++++++++++ timestamped/2025-11-13_08-19-00.md | 19 +------------------ timestamped/2026-01-12_13-02-00.md | 21 --------------------- 4 files changed, 39 insertions(+), 39 deletions(-) create mode 100644 2025-11-13_08-19-01.md create mode 100644 2026-01-12_13-02-01.md diff --git a/2025-11-13_08-19-01.md b/2025-11-13_08-19-01.md new file mode 100644 index 0000000..2a58cdb --- /dev/null +++ b/2025-11-13_08-19-01.md @@ -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? \ No newline at end of file diff --git a/2026-01-12_13-02-01.md b/2026-01-12_13-02-01.md new file mode 100644 index 0000000..afe2e68 --- /dev/null +++ b/2026-01-12_13-02-01.md @@ -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. diff --git a/timestamped/2025-11-13_08-19-00.md b/timestamped/2025-11-13_08-19-00.md index d92a9f9..4623cc9 100644 --- a/timestamped/2025-11-13_08-19-00.md +++ b/timestamped/2025-11-13_08-19-00.md @@ -25,21 +25,4 @@ 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? \ No newline at end of file +[[2025-11-13_08-19-01]] \ No newline at end of file diff --git a/timestamped/2026-01-12_13-02-00.md b/timestamped/2026-01-12_13-02-00.md index 28379b1..3c02530 100644 --- a/timestamped/2026-01-12_13-02-00.md +++ b/timestamped/2026-01-12_13-02-00.md @@ -10,24 +10,3 @@ dg-publish: true **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. From 802377a012039924c79caf0dc25c865cd59a53cf Mon Sep 17 00:00:00 2001 From: Zane Meyers Date: Wed, 25 Feb 2026 13:08:42 -0500 Subject: [PATCH 6/6] vault backup: 2026-02-25 13:08:42 --- 2025-11-13_08-19-01.md => timestamped/2025-11-13_08-19-01.md | 0 2026-01-12_13-02-01.md => timestamped/2026-01-12_13-02-01.md | 0 2 files changed, 0 insertions(+), 0 deletions(-) rename 2025-11-13_08-19-01.md => timestamped/2025-11-13_08-19-01.md (100%) rename 2026-01-12_13-02-01.md => timestamped/2026-01-12_13-02-01.md (100%) diff --git a/2025-11-13_08-19-01.md b/timestamped/2025-11-13_08-19-01.md similarity index 100% rename from 2025-11-13_08-19-01.md rename to timestamped/2025-11-13_08-19-01.md diff --git a/2026-01-12_13-02-01.md b/timestamped/2026-01-12_13-02-01.md similarity index 100% rename from 2026-01-12_13-02-01.md rename to timestamped/2026-01-12_13-02-01.md