vault backup: 2026-02-17 17:04:56
This commit is contained in:
Vendored
-1
@@ -24,6 +24,5 @@
|
||||
"obsidian-tasks-plugin",
|
||||
"digitalgarden",
|
||||
"pdf-plus",
|
||||
"obsidian-tracker",
|
||||
"copy-document-as-html"
|
||||
]
|
||||
+1
-1
@@ -53,7 +53,7 @@
|
||||
},
|
||||
"yaml-key-sort": {
|
||||
"enabled": true,
|
||||
"yaml-key-priority-sort-order": "id\naliases\ntitle\ntags",
|
||||
"yaml-key-priority-sort-order": "id\naliases\ntitle\ntags\ndg-publish\ndaily\nweekly\nmonthly\nquarterly\nyearly",
|
||||
"priority-keys-at-start-of-yaml": true,
|
||||
"yaml-sort-order-for-other-keys": "Ascending Alphabetical"
|
||||
},
|
||||
|
||||
+1
Submodule .obsidian/plugins/obsidian-pandoc-plus added at 89d0fdbcf0
-4
File diff suppressed because one or more lines are too long
@@ -1,10 +0,0 @@
|
||||
{
|
||||
"id": "obsidian-tracker",
|
||||
"name": "Tracker",
|
||||
"version": "1.17.0",
|
||||
"minAppVersion": "0.9.12",
|
||||
"description": "A plugin tracks occurrences and numbers in your notes",
|
||||
"author": "pyrochlore",
|
||||
"authorUrl": "",
|
||||
"isDesktopOnly": false
|
||||
}
|
||||
-182
@@ -1,182 +0,0 @@
|
||||
.theme-light {
|
||||
--color-title: #000000;
|
||||
--color-axis: #000000;
|
||||
--color-axis-label: #000000;
|
||||
--color-tick-label: #000000;
|
||||
--color-line: #000000;
|
||||
|
||||
--color-legend-border: #000000;
|
||||
|
||||
--color-dot-fill: #69b3a2;
|
||||
--color-dot-stroke: none;
|
||||
|
||||
--color-bar-fill: #69b3a2;
|
||||
--color-bar-border: none;
|
||||
|
||||
--color-tooltip-bg: #ffffff;
|
||||
--color-tooltip-border: #000000;
|
||||
--color-tooltip-label: #000000;
|
||||
}
|
||||
|
||||
.theme-dark {
|
||||
--color-title: #ffffff;
|
||||
--color-axis: #ffffff;
|
||||
--color-axis-label: #ffffff;
|
||||
--color-tick-label: #ffffff;
|
||||
--color-line: #ffffff;
|
||||
|
||||
--color-legend-border: #ffffff;
|
||||
|
||||
--color-dot-fill: #69b3a2;
|
||||
--color-dot-stroke: none;
|
||||
|
||||
--color-bar-fill: #69b3a2;
|
||||
--color-bar-border: none;
|
||||
|
||||
--color-tooltip-bg: #ffffff;
|
||||
--color-tooltip-border: #000000;
|
||||
--color-tooltip-label: #000000;
|
||||
}
|
||||
|
||||
.tracker-title {
|
||||
fill: var(--color-title);
|
||||
text-anchor: middle;
|
||||
font-size: 18px;
|
||||
}
|
||||
|
||||
.tracker-title-small {
|
||||
fill: var(--color-title);
|
||||
text-anchor: middle;
|
||||
font-size: 16px;
|
||||
}
|
||||
|
||||
.tracker-axis {
|
||||
fill: none;
|
||||
stroke: var(--color-axis);
|
||||
stroke-width: 1px;
|
||||
}
|
||||
|
||||
.tracker-axis-label {
|
||||
fill: var(--color-axis-label);
|
||||
text-anchor: middle;
|
||||
font-size: 14px;
|
||||
stroke: none;
|
||||
}
|
||||
|
||||
.tracker-tick-label {
|
||||
fill: var(--color-tick-label);
|
||||
stroke: none;
|
||||
font-size: 12px;
|
||||
}
|
||||
|
||||
.tracker-line {
|
||||
fill: none;
|
||||
stroke: var(--color-line);
|
||||
stroke-width: 1.5px;
|
||||
stroke-linecap: round;
|
||||
stroke-linejoin: round;
|
||||
}
|
||||
|
||||
.tracker-dot {
|
||||
fill: var(--color-dot-fill);
|
||||
}
|
||||
|
||||
.tracker-tooltip {
|
||||
fill: var(--color-tooltip-bg);
|
||||
stroke: var(--color-tooltip-border);
|
||||
stroke-width: 1px;
|
||||
}
|
||||
|
||||
.tracker-tooltip-label {
|
||||
fill: var(--color-tooltip-label);
|
||||
stroke: none;
|
||||
font-size: 12px;
|
||||
}
|
||||
|
||||
.tracker-legend {
|
||||
fill: none;
|
||||
stroke: var(--color-legend-border);
|
||||
stroke-width: 0.5px;
|
||||
}
|
||||
|
||||
.tracker-legend-label {
|
||||
font-size: 14px;
|
||||
text-anchor: left;
|
||||
}
|
||||
|
||||
.tracker-bar {
|
||||
fill: var(--color-bar-fill);
|
||||
}
|
||||
|
||||
.tracker-month-header-year {
|
||||
fill: var(--color-title);
|
||||
text-anchor: start;
|
||||
font-size: 22px;
|
||||
|
||||
}
|
||||
|
||||
.tracker-month-header-month {
|
||||
fill: var(--color-title);
|
||||
text-anchor: start;
|
||||
font-size: 18px;
|
||||
}
|
||||
|
||||
.tracker-month-dividing-line {
|
||||
fill: var(--color-bar-fill);
|
||||
}
|
||||
|
||||
.tracker-month-title-arrow {
|
||||
fill: var(--color-title);
|
||||
text-anchor: middle;
|
||||
font-size: 22px;
|
||||
}
|
||||
|
||||
.tracker-month-title-rotator {
|
||||
fill: var(--color-title);
|
||||
text-anchor: middle;
|
||||
font-size: 20px;
|
||||
}
|
||||
|
||||
.tracker-month-title-monitor {
|
||||
fill: var(--color-title);
|
||||
text-anchor: middle;
|
||||
font-size: 18px;
|
||||
}
|
||||
|
||||
.tracker-month-weekday {
|
||||
fill: var(--color-tick-label);
|
||||
stroke: none;
|
||||
font-size: 12px;
|
||||
}
|
||||
|
||||
.tracker-month-today-circle {
|
||||
fill: none;
|
||||
stroke: "white";
|
||||
stroke-width: 4px;
|
||||
}
|
||||
|
||||
.tracker-month-selected-circle {
|
||||
fill: none;
|
||||
stroke: "red";
|
||||
stroke-width: 2px;
|
||||
}
|
||||
|
||||
.tracker-month-label {
|
||||
fill: var(--color-axis-label);
|
||||
text-anchor: middle;
|
||||
font-size: 14px;
|
||||
stroke: none;
|
||||
}
|
||||
|
||||
.tracker-month-annotation {
|
||||
fill: var(--color-axis-label);
|
||||
text-anchor: middle;
|
||||
font-size: 10px;
|
||||
stroke: none;
|
||||
}
|
||||
|
||||
.tracker-pie-label {
|
||||
fill: var(--color-tick-label);
|
||||
stroke: none;
|
||||
font-size: 12px;
|
||||
}
|
||||
Vendored
+2
-1
@@ -24,6 +24,7 @@
|
||||
"TQ_show_task_count": "checkbox",
|
||||
"TQ_show_tree": "checkbox",
|
||||
"TQ_show_urgency": "checkbox",
|
||||
"dg-publish": "checkbox"
|
||||
"dg-publish": "checkbox",
|
||||
"id": "datetime"
|
||||
}
|
||||
}
|
||||
@@ -14,6 +14,8 @@ dg-publish: true
|
||||
|
||||
## 2025-11-05 ??:??
|
||||
|
||||
#topic/morality
|
||||
|
||||
Conservatives claim to care about
|
||||
family values, but a purely merit-based system
|
||||
incentivizes degenerate lifestyles.
|
||||
|
||||
+3
-1
@@ -43,7 +43,7 @@ like music and style and... birdwatching...
|
||||
|
||||
## 2025-11-10 10:40
|
||||
|
||||
#topic/estimating
|
||||
#topic/estimating #occupational
|
||||
|
||||
A significant change from Ace to PDI in my mentality during takeoff
|
||||
is that I now tend to expect that (within reason)
|
||||
@@ -117,6 +117,8 @@ those are [[nfpa-70_100_definitions#Branch Circuit.|branch circuit]] conductors.
|
||||
|
||||
## 2025-11-10 20:00 --- Monday Evening, Before Bed
|
||||
|
||||
#topic/estimating #occupational
|
||||
|
||||
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
|
||||
|
||||
+3
-1
@@ -26,7 +26,7 @@ that I'm not capable of under the pressure of conversation.
|
||||
|
||||
## 2025-11-13 08:19
|
||||
|
||||
#topic/estimating
|
||||
#topic/estimating #occupational
|
||||
|
||||
I'm still working on articulating
|
||||
my main difficulty in the transition
|
||||
@@ -45,6 +45,8 @@ as judged from a realist perspective, wrong.
|
||||
|
||||
## 2025-11-13 ??:??
|
||||
|
||||
#occupational
|
||||
|
||||
### Questions for Bid Estimators
|
||||
|
||||
Questions for [[pdi-estimating#Bid Estimating|PDI Bid Estimators]].
|
||||
|
||||
+2
-2
@@ -35,8 +35,8 @@ Note: It is not usually necessary to count emergency fixtures separately.
|
||||
Use minimum 1 hour for tape lights, except in units (minimum 0.5hr).
|
||||
|
||||
Final Pricing adjustments:
|
||||
Warranty,
|
||||
CIP (see proposal)
|
||||
* Warranty,
|
||||
* CIP (see proposal)
|
||||
|
||||
Added putty pads.
|
||||
|
||||
|
||||
+1
-27
@@ -11,30 +11,4 @@ dg-publish: true
|
||||
---
|
||||
# 2025-11-21
|
||||
|
||||
## 2025-11-21 10:11
|
||||
|
||||
#topic/estimating
|
||||
|
||||
> [!quote] [ELECTRI's Industry Benchmarking Tool - ELECTRI International](https://www.electri.org/research-overview/electris-industry-benchmarking-tool/)
|
||||
> ### Hours Burned vs. Hours Earned
|
||||
>
|
||||
> Definition:
|
||||
> Comparison between portion of project estimated hours complete
|
||||
> compared with the actual hours spent on the task.
|
||||
> This is the labor performance factor
|
||||
> (needs to reference the labor factor used at bid time for a full comparison).
|
||||
|
||||
This is a terribly problematic metric.
|
||||
|
||||
If a project went over its material budget
|
||||
despite standard rigorous oversight
|
||||
where would you first look,
|
||||
construction or estimating?
|
||||
In almost all cases the safer bet is estimating.
|
||||
Why should labor be different?
|
||||
|
||||
Wherever there is budget variance
|
||||
there is a persistent tendency to blame construction
|
||||
before estimating.
|
||||
|
||||
[[purpose-of-construction-estimating#The Myth of Estimate Accuracy]]
|
||||
[[2025-11-21_10-11-00]]
|
||||
@@ -0,0 +1,36 @@
|
||||
---
|
||||
id: 2025-11-21T10:11:00-05:00
|
||||
aliases: []
|
||||
title: 2025-11-21 10:11:??
|
||||
tags:
|
||||
- authorship/original
|
||||
- destiny/permanent
|
||||
- status/complete
|
||||
- topic/estimating
|
||||
- type/periodic/timestamped
|
||||
---
|
||||
# 2025-11-21 10:11:??
|
||||
|
||||
> [!quote] [ELECTRI's Industry Benchmarking Tool - ELECTRI International](https://www.electri.org/research-overview/electris-industry-benchmarking-tool/)
|
||||
> ### Hours Burned vs. Hours Earned
|
||||
>
|
||||
> Definition:
|
||||
> Comparison between portion of project estimated hours complete
|
||||
> compared with the actual hours spent on the task.
|
||||
> This is the labor performance factor
|
||||
> (needs to reference the labor factor used at bid time for a full comparison).
|
||||
|
||||
This is a terribly problematic metric.
|
||||
|
||||
If a project went over its material budget
|
||||
despite standard rigorous oversight
|
||||
where would you first look,
|
||||
construction or estimating?
|
||||
In almost all cases the safer bet is estimating.
|
||||
Why should labor be different?
|
||||
|
||||
Wherever there is budget variance
|
||||
there is a persistent tendency to blame construction
|
||||
before estimating.
|
||||
|
||||
[[purpose-of-construction-estimating#The Myth of Estimate Accuracy]]
|
||||
+7
-5
@@ -32,9 +32,9 @@ is the relevant section.
|
||||
Effective date: [[2026-01-21]]
|
||||
|
||||
* [x] Escrow deposit due by [[2026-01-26]]
|
||||
* [ ] Loan application submitted by [[2026-01-26]]
|
||||
* [ ] Inspection period ends [[2026-01-28]]
|
||||
* [ ] Loan approval due by [[2026-02-11]]
|
||||
* [x] Loan application submitted by [[2026-01-26]]
|
||||
* [x] Inspection period ends [[2026-01-28]]
|
||||
* [x] Loan approval due by [[2026-02-11]]
|
||||
* [ ] Title commitment due by [[2026-02-27]]
|
||||
|
||||
Closing: [[2026-03-04]]
|
||||
@@ -54,13 +54,15 @@ Closing: [[2026-03-04]]
|
||||
|
||||
It may be counterintuitive to BOM-oriented estimators
|
||||
(typical of those with an electrical background),
|
||||
but deviating from ~~common practice~~
|
||||
but deviating from organization standard practice
|
||||
to make an assembly "more accurate"
|
||||
(read: to make the estimate BOM
|
||||
more closely resemble the construction BOM),
|
||||
may make the budget _less_ accurate.
|
||||
|
||||
The review and adjustment process is based on ~~common practice~~,
|
||||
The review and adjustment process
|
||||
is based on standard practice,
|
||||
so deviations may have unpredictable effects.
|
||||
|
||||
Our assemblies do not include screws
|
||||
It would be more accurate to the BOM to add them,
|
||||
|
||||
@@ -13,6 +13,8 @@ dg-publish: true
|
||||
|
||||
## 2026-01-25 18:46
|
||||
|
||||
#topic/finance
|
||||
|
||||
### Calculating Monthly Principal & Interest Payment
|
||||
|
||||
For a **fixed-rate, fully-amortizing mortgage**,
|
||||
|
||||
@@ -13,6 +13,8 @@ dg-publish: true
|
||||
|
||||
## 2026-01-27 17:31
|
||||
|
||||
#topic/hobbies/reading
|
||||
|
||||
### BLAME! Coelacanth
|
||||
|
||||
Follow-up to [[2026-01-26#BLAME! Coelacanth]]
|
||||
|
||||
+10
-4
@@ -11,7 +11,9 @@ dg-publish: true
|
||||
---
|
||||
# 2026-01-28
|
||||
|
||||
## 2026-01-28 09:51
|
||||
## 2026-01-28 09:51:??
|
||||
|
||||
#occupational
|
||||
|
||||
### ConEst OneNote Template
|
||||
|
||||
@@ -25,8 +27,10 @@ some I would not have thought could work so well.
|
||||
At Ace my takeoff notes were entirely freeform,
|
||||
and I would have balked at the idea of using a standard checklist.
|
||||
Our projects were so varied
|
||||
no list could be generic enough to approach universal applicability
|
||||
without being so shallow as to be useless to an experienced estimator.
|
||||
that no list could be generic enough
|
||||
to approach universal applicability
|
||||
without being so shallow
|
||||
as to be useless to an experienced estimator.
|
||||
|
||||
#### Estimator Initials
|
||||
|
||||
@@ -34,7 +38,9 @@ Voluntary commitment to responsibility.
|
||||
An estimator adding their initials
|
||||
knows they are expected to be familiar with the scope.
|
||||
|
||||
## 2026-01-28 10:02
|
||||
## 2026-01-28 10:02:??
|
||||
|
||||
#topic/meta
|
||||
|
||||
I'm tempted to replace [[daily-notes]] with timestamped notes
|
||||
from core plugins Unique Note Creator,
|
||||
|
||||
+1
-1
@@ -82,7 +82,7 @@ even when slightly lower.
|
||||
|
||||
Short-term investments may be favored
|
||||
when liquidity is needed during the term,
|
||||
Tax deferred investments (IRA)
|
||||
and tax deferred investments (IRA)
|
||||
are strongly favored over elective payment
|
||||
since interest is deductible
|
||||
(effective interest < nominal).
|
||||
|
||||
+3
-1
@@ -45,7 +45,9 @@ and touch a virtual light switch
|
||||
because the routines they programmed were too conservative.
|
||||
|
||||
Human or software,
|
||||
an assistant without agency and the will to contradict you is worthless.
|
||||
an assistant without agency
|
||||
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.
|
||||
|
||||
@@ -10,42 +10,3 @@ tags:
|
||||
dg-publish: true
|
||||
---
|
||||
# 2026-01-31
|
||||
|
||||
## 2026-01-31 12:48:00
|
||||
|
||||
Follow-up to [[2026-01-19#2026-01-19 11:57]]
|
||||
|
||||
a **natural-language parser**
|
||||
could easily determine where hyphens should be replaced with em dashes.
|
||||
|
||||
"deep-set" `{ADJECTIVE}-{VERB_PAST_TENSE}` -> `{COMPOUND_ADJECTIVE}`
|
||||
"leather-covered" `{NOUN}-{VERB_PAST_TENSE}` -> `{COMPOUND_ADJECTIVE}`
|
||||
"magic-worker" `{NOUN}-{AGENT_NOUN}` -> `{COMPOUND_NOUN}`
|
||||
"eon-old" `{NOUN}-{ADJECTIVE}` -> `{COMPOUND_ADJECTIVE}`
|
||||
"one-armed" `{NUMBER_ADJECTIVE}-{ADJECTIVE}` -> `{COMPOUND_ADJECTIVE}`
|
||||
"twenty-two" `{NUMBER_ADJECTIVE}-{NUMBER_ADJECTIVE}` -> `{NUMBER_ADJECTIVE}`
|
||||
|
||||
[Agent noun](https://en.wikipedia.org/wiki/Agent_noun)
|
||||
|
||||
- **-er / -or**: _worker, runner, actor_
|
||||
- **-ist**: _pianist, socialist_
|
||||
- **-ant / -ent**: _assistant, respondent_
|
||||
|
||||
[Theta role](https://en.wikipedia.org/wiki/Theta_role)
|
||||
|
||||
- **-ee** (often recipient rather than doer, but related): _employee, trainee_
|
||||
|
||||
## 2026-01-31 17:49:00
|
||||
|
||||
> [!quote] [Linux Bash Shell Script Error: cannot execute: required file not found - Unix Stack Exchange](https://unix.stackexchange.com/questions/721844/linux-bash-shell-script-error-cannot-execute-required-file-not-found)
|
||||
> > [!quote] [ctrl-alt-delor](https://unix.stackexchange.com/users/4778/) 2022-10-21 08:16
|
||||
> > Note: use of back ticks e.g. `... ``command`` ...` is deprecated. Use the newer easier to use `"$(command)"` (but yes this simple use with echo is hoop jumping). Use of `.sh` at the end of file names is not Unix. And it violates the principle of abstraction, as it leaks implementation detail. Just name them by what they do, not how they do it.
|
||||
>
|
||||
> > [!quote] [Kusalananda](https://unix.stackexchange.com/users/116858/) 2022-10-21 08:22
|
||||
> > @ctrl-alt-delor They are most definitely not deprecated, only awkward to use and should be avoided. In this particular case, any type of command substitution would be inappropriate. As for naming files, that's really up to the user. If you are concerned with abstraction, you could suggest the user uses the `hostname` command directly rather than via a nonsensical script with a function.
|
||||
>
|
||||
> > [!quote] ctrl-alt-delor 2022-10-21 08:29
|
||||
> > `deprecate` : express disapproval of. I disapprove. You say should be avoided. Thus deprecated. As for up to the user. I agree, it is the same for drug use. And the best abstraction is no abstraction (it depends). However I assume the examples were minimum non-working examples.
|
||||
>
|
||||
> > [!quote] [Ed Swangren](https://unix.stackexchange.com/users/597584/) 2024-09-28 07:46
|
||||
> > @ctrl-alt-delor `deprecate(3):` to withdraw official support for or discourage the use of (something, such as a software product) in favor of a newer or better alternative" you're right, but only accidentally, so no credit given and mockery warranted. Citing a dictionary definition in a technical context is always wrong, citing the wrong one is lazy and stupid, and citing your opinion as evidence is in line with what I'd expect after #1 and #2. No one cares.
|
||||
|
||||
@@ -0,0 +1,35 @@
|
||||
---
|
||||
id:
|
||||
aliases: []
|
||||
title: 2026-01-31 12:48:00
|
||||
tags:
|
||||
- authorship/original
|
||||
- destiny/permanent
|
||||
- status/draft
|
||||
- type/timestamped
|
||||
daily: "[[2026-01-31]]"
|
||||
dg-publish: true
|
||||
---
|
||||
# 2026-01-31 12:48:00
|
||||
|
||||
Follow-up to [[2026-01-19#2026-01-19 11:57]]
|
||||
|
||||
a **natural-language parser**
|
||||
could easily determine where hyphens should be replaced with em dashes.
|
||||
|
||||
"deep-set" `{ADJECTIVE}-{VERB_PAST_TENSE}` -> `{COMPOUND_ADJECTIVE}`
|
||||
"leather-covered" `{NOUN}-{VERB_PAST_TENSE}` -> `{COMPOUND_ADJECTIVE}`
|
||||
"magic-worker" `{NOUN}-{AGENT_NOUN}` -> `{COMPOUND_NOUN}`
|
||||
"eon-old" `{NOUN}-{ADJECTIVE}` -> `{COMPOUND_ADJECTIVE}`
|
||||
"one-armed" `{NUMBER_ADJECTIVE}-{ADJECTIVE}` -> `{COMPOUND_ADJECTIVE}`
|
||||
"twenty-two" `{NUMBER_ADJECTIVE}-{NUMBER_ADJECTIVE}` -> `{NUMBER_ADJECTIVE}`
|
||||
|
||||
[Agent noun](https://en.wikipedia.org/wiki/Agent_noun)
|
||||
|
||||
* **-er / -or**: _worker, runner, actor_
|
||||
* **-ist**: _pianist, socialist_
|
||||
* **-ant / -ent**: _assistant, respondent_
|
||||
|
||||
[Theta role](https://en.wikipedia.org/wiki/Theta_role)
|
||||
|
||||
* **-ee** (often recipient rather than doer, but related): _employee, trainee_
|
||||
@@ -0,0 +1,27 @@
|
||||
---
|
||||
id: 2026-01-31T17:49:00-05:00
|
||||
aliases: []
|
||||
title: 2026-01-31 17:49:00
|
||||
tags:
|
||||
- authorship/other
|
||||
- destiny/permanent
|
||||
- status/draft
|
||||
- type/timestamped
|
||||
daily: "[[2026-01-31]]"
|
||||
dg-publish: true
|
||||
---
|
||||
# 2026-01-31 17:49:00
|
||||
|
||||
> [!quote] [Linux Bash Shell Script Error: cannot execute: required file not found - Unix Stack Exchange](https://unix.stackexchange.com/questions/721844/linux-bash-shell-script-error-cannot-execute-required-file-not-found)
|
||||
>
|
||||
> > [!quote] [ctrl-alt-delor](https://unix.stackexchange.com/users/4778/) 2022-10-21 08:16
|
||||
> > Note: use of back ticks e.g. `... ``command`` ...` is deprecated. Use the newer easier to use `"$(command)"` (but yes this simple use with echo is hoop jumping). Use of `.sh` at the end of file names is not Unix. And it violates the principle of abstraction, as it leaks implementation detail. Just name them by what they do, not how they do it.
|
||||
>
|
||||
> > [!quote] [Kusalananda](https://unix.stackexchange.com/users/116858/) 2022-10-21 08:22
|
||||
> > @ctrl-alt-delor They are most definitely not deprecated, only awkward to use and should be avoided. In this particular case, any type of command substitution would be inappropriate. As for naming files, that's really up to the user. If you are concerned with abstraction, you could suggest the user uses the `hostname` command directly rather than via a nonsensical script with a function.
|
||||
>
|
||||
> > [!quote] ctrl-alt-delor 2022-10-21 08:29
|
||||
> > `deprecate` : express disapproval of. I disapprove. You say should be avoided. Thus deprecated. As for up to the user. I agree, it is the same for drug use. And the best abstraction is no abstraction (it depends). However I assume the examples were minimum non-working examples.
|
||||
>
|
||||
> > [!quote] [Ed Swangren](https://unix.stackexchange.com/users/597584/) 2024-09-28 07:46
|
||||
> > @ctrl-alt-delor `deprecate(3):` to withdraw official support for or discourage the use of (something, such as a software product) in favor of a newer or better alternative" you're right, but only accidentally, so no credit given and mockery warranted. Citing a dictionary definition in a technical context is always wrong, citing the wrong one is lazy and stupid, and citing your opinion as evidence is in line with what I'd expect after #1 and #2. No one cares.
|
||||
@@ -7,6 +7,7 @@ tags:
|
||||
- destiny/permanent
|
||||
- status/draft
|
||||
- type/timestamped
|
||||
- topic/meta
|
||||
dg-publish: true
|
||||
daily: "[[2026-02-02]]"
|
||||
---
|
||||
|
||||
@@ -7,6 +7,7 @@ tags:
|
||||
- destiny/permanent
|
||||
- status/draft
|
||||
- type/timestamped
|
||||
- occupational/takeoff
|
||||
dg-publish: true
|
||||
daily: "[[2026-02-02]]"
|
||||
---
|
||||
|
||||
@@ -7,6 +7,7 @@ tags:
|
||||
- destiny/permanent
|
||||
- status/draft
|
||||
- type/timestamped
|
||||
- occupational
|
||||
dg-publish: true
|
||||
daily: "[[2026-02-03]]"
|
||||
---
|
||||
|
||||
@@ -7,6 +7,7 @@ tags:
|
||||
- destiny/permanent
|
||||
- status/draft
|
||||
- type/timestamped
|
||||
- topic/estimating
|
||||
dg-publish: true
|
||||
daily: "[[2026-02-03]]"
|
||||
---
|
||||
|
||||
@@ -7,6 +7,7 @@ tags:
|
||||
- destiny/permanent
|
||||
- status/draft
|
||||
- type/timestamped
|
||||
- occupational
|
||||
dg-publish: true
|
||||
daily: "[[2026-02-03]]"
|
||||
---
|
||||
|
||||
@@ -7,6 +7,7 @@ tags:
|
||||
- destiny/permanent
|
||||
- status/draft
|
||||
- type/timestamped
|
||||
- occupational
|
||||
dg-publish: true
|
||||
daily: "[[2026-02-04]]"
|
||||
---
|
||||
|
||||
@@ -7,6 +7,7 @@ tags:
|
||||
- destiny/permanent
|
||||
- status/draft
|
||||
- type/timestamped
|
||||
- topic/organization
|
||||
dg-publish: true
|
||||
daily: "[[2026-02-04]]"
|
||||
---
|
||||
@@ -24,28 +25,26 @@ is a method of project estimation
|
||||
characterized by the use of T-shirt sizes
|
||||
representing project scale buckets.
|
||||
|
||||
> [!example]
|
||||
> [!example] [T-Shirt Sizing in Agile --- Project Management Pathways](https://www.projectmanagementpathways.com/project-management-articles/tshirt-sizing-in-agile-projects)
|
||||
> * **XS (1-2 days):** Simple UI changes or minor bug fixes
|
||||
>
|
||||
> Example: "Update button color on checkout page"
|
||||
> Example: "Update button color on checkout page"
|
||||
>
|
||||
> * **S (2-3 days):** Feature enhancements with minimal complexity
|
||||
>
|
||||
> Example: "Add product sorting by price"
|
||||
> Example: "Add product sorting by price"
|
||||
>
|
||||
> * **M (5-7 days):** Features requiring moderate integration
|
||||
>
|
||||
> Example: "Implement basic search filters"
|
||||
> Example: "Implement basic search filters"
|
||||
>
|
||||
> * **L (8-10 days):** Complex features affecting multiple components
|
||||
>
|
||||
> Example: "Create shopping cart functionality"
|
||||
> Example: "Create shopping cart functionality"
|
||||
>
|
||||
> * **XL (2+ weeks):** Major features requiring breaking down
|
||||
>
|
||||
> Example: "Implement payment gateway integration"
|
||||
>
|
||||
> --- [T-Shirt Sizing in Agile --- Project Management Pathways](https://www.projectmanagementpathways.com/project-management-articles/tshirt-sizing-in-agile-projects)
|
||||
> Example: "Implement payment gateway integration"
|
||||
|
||||
The buckets chosen should be wide enough
|
||||
that scale can be confidently estimated
|
||||
|
||||
@@ -7,6 +7,7 @@ tags:
|
||||
- destiny/permanent
|
||||
- status/draft
|
||||
- type/timestamped
|
||||
- occupational/takeoff
|
||||
dg-publish: true
|
||||
daily: "[[2026-02-04]]"
|
||||
---
|
||||
|
||||
@@ -7,6 +7,7 @@ tags:
|
||||
- destiny/permanent
|
||||
- status/draft
|
||||
- type/timestamped
|
||||
- occupational/takeoff
|
||||
dg-publish: true
|
||||
daily: "[[2026-02-04]]"
|
||||
---
|
||||
@@ -23,9 +24,9 @@ so that we would not risk having too little overall.
|
||||
|
||||
Their expectation surprised me,
|
||||
since it is intuitive to me
|
||||
that there must be some limit to the logic of "covering it"
|
||||
that there must be some limit to the logic of "covering it",
|
||||
since it is always within our power to add contingency,
|
||||
and especially because, if anything,
|
||||
and especially because---if anything---
|
||||
I feel that our procedures tend towards
|
||||
the upper end of reasonable ECI.
|
||||
(see [[value-of-information.jpg]])
|
||||
|
||||
@@ -7,6 +7,7 @@ tags:
|
||||
- destiny/permanent
|
||||
- status/draft
|
||||
- type/timestamped
|
||||
- topic/estimating
|
||||
dg-publish: true
|
||||
daily: "[[2026-02-04]]"
|
||||
---
|
||||
|
||||
@@ -1,12 +1,13 @@
|
||||
---
|
||||
id:
|
||||
aliases: []
|
||||
title: "2026-02-05 10:14:01"
|
||||
title: 2026-02-05 10:14:01
|
||||
tags:
|
||||
- authorship/original
|
||||
- destiny/permanent
|
||||
- status/draft
|
||||
- type/periodic/timestamped
|
||||
- occupational/takeoff
|
||||
dg-publish: true
|
||||
daily: "[[2026-02-05]]"
|
||||
weekly: "[[2026-W06]]"
|
||||
|
||||
@@ -1,12 +1,13 @@
|
||||
---
|
||||
id:
|
||||
aliases: []
|
||||
title: "2026-02-05 12:14:47"
|
||||
title: 2026-02-05 12:14:47
|
||||
tags:
|
||||
- authorship/original
|
||||
- destiny/permanent
|
||||
- status/draft
|
||||
- type/periodic/timestamped
|
||||
- topic/construction/electrical
|
||||
dg-publish: true
|
||||
daily: "[[2026-02-05]]"
|
||||
weekly: "[[2026-W06]]"
|
||||
|
||||
@@ -1,12 +1,13 @@
|
||||
---
|
||||
id:
|
||||
aliases: []
|
||||
title: "2026-02-07 09:16:31"
|
||||
title: 2026-02-07 09:16:31
|
||||
tags:
|
||||
- authorship/original
|
||||
- destiny/permanent
|
||||
- status/draft
|
||||
- type/periodic/timestamped
|
||||
- topic/hobbies/reading
|
||||
dg-publish: true
|
||||
daily: "[[2026-02-07]]"
|
||||
weekly: "[[2026-W06]]"
|
||||
|
||||
@@ -1,12 +1,13 @@
|
||||
---
|
||||
id:
|
||||
aliases: []
|
||||
title: "2026-02-08 08:00:49"
|
||||
title: 2026-02-08 08:00:49
|
||||
tags:
|
||||
- authorship/original
|
||||
- destiny/permanent
|
||||
- status/draft
|
||||
- type/periodic/timestamped
|
||||
- topic/hobbies/reading
|
||||
dg-publish: true
|
||||
daily: "[[2026-02-08]]"
|
||||
weekly: "[[2026-W06]]"
|
||||
|
||||
@@ -1,23 +0,0 @@
|
||||
---
|
||||
id:
|
||||
aliases: []
|
||||
title: "2026-02-10 07:46:30"
|
||||
tags:
|
||||
- authorship/original
|
||||
- destiny/permanent
|
||||
- status/draft
|
||||
- type/periodic/timestamped
|
||||
dg-publish: true
|
||||
daily: "[[2026-02-10]]"
|
||||
weekly: "[[2026-W07]]"
|
||||
monthly: "[[2026-02]]"
|
||||
quarterly: "[[2026-Q1]]"
|
||||
yearly: "[[2026]]"
|
||||
---
|
||||
# 2026-02-10 07:46:30
|
||||
|
||||
## Foobar2000 Autofill Metadata Values
|
||||
|
||||
```foobar
|
||||
%tracknumber%. %artist% - %title%
|
||||
```
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
id:
|
||||
id: 2026-02-11T12:12:16-05:00
|
||||
aliases: []
|
||||
title: 2026-02-11 12:12:16
|
||||
tags:
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
id:
|
||||
id: 2026-02-12T09:49:56-05:00
|
||||
aliases: []
|
||||
title: 2026-02-12 09:49:56
|
||||
tags:
|
||||
@@ -7,6 +7,7 @@ tags:
|
||||
- destiny/permanent
|
||||
- status/draft
|
||||
- type/periodic/timestamped
|
||||
- topic/construction/electrical
|
||||
daily: "[[2026-02-12]]"
|
||||
dg-publish: true
|
||||
monthly: "[[2026-02]]"
|
||||
@@ -22,7 +23,7 @@ yearly: "[[2026]]"
|
||||
|
||||
Applies to "Equipment intended to interrupt current".
|
||||
|
||||
[[nfpa-70_110_requirements#110.9 Interrupting Rating.|110.9 Interrupting Rating.]]
|
||||
[[nfpa-70_110_requirements#110.9 Interrupting Rating.|NEC 110.9 Interrupting Rating.]]
|
||||
|
||||
Maximum current that the equipment can interrupt without damage.
|
||||
Measured in amperes, usually shown as kAIC.
|
||||
@@ -31,7 +32,7 @@ Measured in amperes, usually shown as kAIC.
|
||||
|
||||
* "withstand rating"
|
||||
|
||||
[[nfpa-70_110_requirements#110.10 Circuit Impedance, Short-Circuit Current Ratings, and Other Characteristics.]]
|
||||
[[nfpa-70_110_requirements#110.10 Circuit Impedance, Short-Circuit Current Ratings, and Other Characteristics.|NEC 110.10 Circuit Impedance, Short-Circuit Current Ratings, and Other Characteristics.]]
|
||||
|
||||
Applies to **assemblies**: distribution equipment like switchboards, panelboards, switches, etc.
|
||||
|
||||
|
||||
@@ -0,0 +1,24 @@
|
||||
---
|
||||
id: 2026-02-17T13-13-06-05:00
|
||||
aliases: []
|
||||
title: "2026-02-17 13:13:06"
|
||||
tags:
|
||||
- authorship/original
|
||||
- destiny/permanent
|
||||
- status/draft
|
||||
- type/periodic/timestamped
|
||||
dg-publish: true
|
||||
daily: "[[2026-02-17]]"
|
||||
weekly: "[[2026-W08]]"
|
||||
monthly: "[[2026-02]]"
|
||||
quarterly: "[[2026-Q1]]"
|
||||
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:??]]
|
||||
|
||||
Today I spoke to a peer about
|
||||
[[earned-value-management#Earned Value Management|earned value management]]:
|
||||
how it relates to our [[pdi-estimating#ConEst Processes|WBS]]
|
||||
and my negative opinion of it.
|
||||
@@ -0,0 +1,44 @@
|
||||
---
|
||||
id: 2026-02-17T16-47-46-05:00
|
||||
aliases: []
|
||||
title: "2026-02-17 16:47:46"
|
||||
tags:
|
||||
- authorship/original
|
||||
- destiny/permanent
|
||||
- status/draft
|
||||
- type/periodic/timestamped
|
||||
dg-publish: true
|
||||
daily: "[[2026-02-17]]"
|
||||
weekly: "[[2026-W08]]"
|
||||
monthly: "[[2026-02]]"
|
||||
quarterly: "[[2026-Q1]]"
|
||||
yearly: "[[2026]]"
|
||||
---
|
||||
# 2026-02-17 16:47:46
|
||||
|
||||
## The Lindy Effect
|
||||
|
||||
> [!quote] [Lindy effect - Wikipedia](https://en.wikipedia.org/wiki/Lindy_effect)
|
||||
> The Lindy effect (also known as Lindy's law)
|
||||
> is a theorized phenomenon by which the future life expectancy
|
||||
> of some non-perishable thing,
|
||||
> like a technology or an idea,
|
||||
> is proportional to its current age.
|
||||
> Thus, the Lindy effect proposes
|
||||
> the longer a period something has survived
|
||||
> to exist or be used in the present,
|
||||
> the longer its remaining life expectancy.
|
||||
> Longevity implies a resistance to change,
|
||||
> obsolescence, or competition,
|
||||
> and greater odds of continued existence into the future.
|
||||
> Where the Lindy effect applies,
|
||||
> mortality rate decreases with time.
|
||||
>
|
||||
> ...
|
||||
>
|
||||
> The concept is named after Lindy's delicatessen in New York City,
|
||||
> where the concept was informally theorized by comedians:
|
||||
> a show running only 2 weeks
|
||||
> would be expected to last another 2 weeks,
|
||||
> while a show that has lasted 2 years
|
||||
> could expect a further 2-year run.
|
||||
@@ -21,7 +21,8 @@ For contents, prose conventions, etc. see [[this-notebook]].
|
||||
|
||||
I primarily use [[obsidian|Obsidian]] for both reading and writing,
|
||||
so notes are written in [Obsidian-flavored markdown](https://help.obsidian.md/),
|
||||
which is partially reimplemented by [Foam](https://foamnotes.com/) for Visual Studio Code
|
||||
which is partially reimplemented by
|
||||
[Foam](https://foamnotes.com/) for Visual Studio Code
|
||||
and [Markdown Oxide](https://oxide.md/) for vim, neovim, and others.
|
||||
|
||||
For compatibility,
|
||||
|
||||
@@ -58,7 +58,10 @@ dg-publish: true
|
||||
|
||||
### Top 2H Rated Room To Roof
|
||||
|
||||
Weatherhead for antenna. One per building.
|
||||
|
||||
1. .../`TOP 2HR RATED RM TO ROOF = ...`
|
||||
* **Count** = 1
|
||||
* **Length** = Top level ceiling height to structure (minimum 15ft)
|
||||
|
||||
## Horizontal
|
||||
|
||||
@@ -0,0 +1,24 @@
|
||||
---
|
||||
id:
|
||||
aliases: []
|
||||
title: Earned Value Management
|
||||
tags:
|
||||
- authorship/original
|
||||
- destiny/permanent
|
||||
- status/incomplete
|
||||
- topic/organization
|
||||
- type/encyclopedia-entry
|
||||
---
|
||||
# Earned Value Management
|
||||
|
||||
Earned value management (EVM)
|
||||
is a [[project-management]] technique
|
||||
...
|
||||
|
||||
EVM is frequently stated to be capable of
|
||||
"measuring project performance and progress
|
||||
in an _objective_ manner",[^1]
|
||||
an analysis that is either optimistic
|
||||
or totally misleading, depending on the context.
|
||||
|
||||
[^1]: [Wikipedia](https://en.wikipedia.org/wiki/Earned_value_management) (emphasis added)
|
||||
+13
-1
@@ -101,4 +101,16 @@ and easily interpreted as an [optimization problem](https://en.wikipedia.org/wik
|
||||
> Brother, let me pull out the mote that is in thine eye,
|
||||
> when thou thyself beholdest not the beam that is in thine own eye?
|
||||
> Thou hypocrite, cast out first the beam out of thine own eye,
|
||||
> and then shalt thou see clearly to pull out the mote that is in thy brother's eye.
|
||||
> and then shalt thou see clearly to pull out the mote that is in thy brother's eye.
|
||||
|
||||
## About Estimating
|
||||
|
||||
> [!quote] Tom Cargill, Bell Labs
|
||||
> The first 90 percent of the code
|
||||
> accounts for the first 90 percent of the development time.
|
||||
> The remaining 10 percent of the code
|
||||
> accounts for the other 90 percent of the development time.
|
||||
|
||||
> [!quote] Hofstadter's law
|
||||
> It always takes longer than you expect,
|
||||
> even when you take into account Hofstadter's law.
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
id: {{date:YYYY-MM-DD-HH-mm-ss}}
|
||||
id: {{date:YYYY-MM-DDTHH-mm-ssZ}}
|
||||
aliases: []
|
||||
title: "{{date:YYYY-MM-DD}} {{time:HH:mm:ss}}"
|
||||
title: "{{date:YYYY-MM-DD HH:mm:ss}}"
|
||||
tags:
|
||||
- authorship/original
|
||||
- destiny/permanent
|
||||
@@ -14,4 +14,4 @@ monthly: "[[{{date:YYYY-MM}}]]"
|
||||
quarterly: "[[{{date:YYYY-[Q]Q}}]]"
|
||||
yearly: "[[{{date:YYYY}}]]"
|
||||
---
|
||||
# {{date:YYYY-MM-DD}} {{time:HH:mm:ss}}
|
||||
# {{date:YYYY-MM-DD HH:mm:ss}}
|
||||
|
||||
+38
-31
@@ -12,29 +12,33 @@ dg-publish: true
|
||||
---
|
||||
# Unit Takeoff
|
||||
|
||||
[[pdi-conest-project-setup#Create Unit Matrix|Create Unit Matrix]]
|
||||
[[accubid-setup#Create Unit Typicals|Create Unit Typicals]]
|
||||
> [!info]
|
||||
> See [[multi-family-dwellings]].
|
||||
|
||||
[[pdi-building-types]]
|
||||
|
||||
## Prerequisites
|
||||
|
||||
> [!important]
|
||||
> Complete [[pre-takeoff-research]],
|
||||
> including [[wiring-method-selection]] and [[wiring-device-research]],
|
||||
> before beginning takeoff.
|
||||
|
||||
> [!info]
|
||||
> See [[multi-family-dwellings]].
|
||||
1. [[pdi-conest-project-setup#Create Unit Matrix|Create Unit Matrix]]
|
||||
2. [[accubid-setup#Create Unit Typicals|Create Unit Typicals]]
|
||||
|
||||
[[pdi-building-types]]
|
||||
## Takeoff
|
||||
|
||||
> [!tip] Preparing for Unit Takeoff
|
||||
> Units generally have very little variation.
|
||||
> It is usually best to copy-paste takeoffs
|
||||
> rather than re-build them for each unit.
|
||||
|
||||
1. Kitchen and Bath
|
||||
2. General assemblies
|
||||
3. Low Voltage
|
||||
4. Lighting Fixtures
|
||||
5. Lighting Control
|
||||
3. Kitchen and Bath
|
||||
4. General assemblies
|
||||
5. Low Voltage
|
||||
6. Lighting Fixtures
|
||||
7. Lighting Control
|
||||
|
||||
> [!tip]
|
||||
> It may be more efficient and neat to not copy switches,
|
||||
@@ -42,7 +46,9 @@ dg-publish: true
|
||||
> and creating them new for each unit,
|
||||
> since the types required can vary greatly between units.
|
||||
|
||||
## Load Centers
|
||||
### Load Centers
|
||||
|
||||
* `System` = "EL - Electrical"
|
||||
|
||||
| Rating | Assembly |
|
||||
| ------- | ---------------------------------------------------------------------------------- |
|
||||
@@ -51,17 +57,17 @@ dg-publish: true
|
||||
|
||||
Include terminations per [[switchgear]].
|
||||
|
||||
## Fixtures
|
||||
### Fixtures
|
||||
|
||||
[[fixtures-takeoff]]
|
||||
|
||||
## Shade Control
|
||||
### Shade Control
|
||||
|
||||
## VTAC Units
|
||||
### VTAC Units
|
||||
|
||||
Used in lieu of individual split systems.
|
||||
|
||||
## Dedicated Circuit Receptacles
|
||||
### Dedicated Circuit Receptacles
|
||||
|
||||
> [!quote] Joel Jansen 2025-11-11, pp.
|
||||
>
|
||||
@@ -76,7 +82,7 @@ Used in lieu of individual split systems.
|
||||
> match the receptacle configuration shown on the plans
|
||||
> (i.e. simplex to simplex, duplex to duplex).
|
||||
|
||||
## Air Sealing
|
||||
### Air Sealing
|
||||
|
||||
* LEED Silver
|
||||
* Mid-Atlantic jobs
|
||||
@@ -86,28 +92,28 @@ Used in lieu of individual split systems.
|
||||
|
||||
`COMMON ASSEMBLIES`/`UNITS - MC CABLE ASSEMBLIES`/`GENERAL ASSEMBLIES - METAL STUD`/`UNIT MISC ITEMS - MC - ADJUST ACCORDINGLY`
|
||||
|
||||
## Dishwasher/Disposal Receptacles
|
||||
### Dishwasher/Disposal Receptacles
|
||||
|
||||
> [!quote] Joel Jansen 2026-01-12 in Reference to Woodbrook (pp.)[^1]
|
||||
> Even when drawings show 2 separate duplex receptacles,
|
||||
> use `DW & DISPOSAL DUAL CIR - ...`,
|
||||
> which includes only one receptacle.
|
||||
|
||||
[^1]: [[2026-01-12#Unit Diskwasher/Disposal]]
|
||||
[^1]: [[2026-01-12#Unit Dishwasher/Disposal]]
|
||||
|
||||
## Islands
|
||||
### Islands
|
||||
|
||||
Use 1 `SLAB / DECK` receptacle for every 2 circuits in the island.
|
||||
Use (1) `SLAB / DECK` receptacle for every 2 circuits in the island.
|
||||
|
||||
`COMMON ASSEMBLIES`/`UNITS - MC CABLE ASSEMBLIES`/`... RECEPTACLE TAMPER RESISTANT ...`/`... (METAL STUD) - 20' 3/4" PVC, ENT, 3#12 THHN`
|
||||
|
||||
Use standard MC assemblies for remaining devices.
|
||||
|
||||
## Bidet Toilets, Whirlpool Baths, etc.
|
||||
### Bidet Toilets, Whirlpool Baths, etc.
|
||||
|
||||
`COMMON ASSEMBLIES`/`MECHANICAL CONNECTIONS (UP TO 100A)`/`PVC - LT NM FLEX (CARFLEX)`/`20A 1PH MECH CONN (100') 3/4" PVC 3#12 - CARFLEX`
|
||||
|
||||
## "High-Lows"
|
||||
### "High-Lows"
|
||||
|
||||
Empty in-wall pass through
|
||||
from credenza location to behind television location.
|
||||
@@ -115,27 +121,28 @@ from credenza location to behind television location.
|
||||
`COMMON ASSEMBLIES`/`TELECOM SYSTEMS`/`UNIT DATA - TELECOM`/`HIGH-LOW - TV SCOOP 1 1/2" ENT - NO CABLE`
|
||||
|
||||
> 
|
||||
> Eaton 35M2W
|
||||
>
|
||||
> _Eaton 35M2W_
|
||||
|
||||
## Telecom Homeruns
|
||||
### Telecom Homeruns
|
||||
|
||||
### Residential
|
||||
#### Residential
|
||||
|
||||
Included in MSDE.
|
||||
|
||||
### Key
|
||||
#### Key
|
||||
|
||||
`COMMON ASSEMBLIES`/`TELECOM SYSTEMS`/`BOH AMENITY ASSEMBLIES`/...
|
||||
|
||||
Adjust cable length as needed.
|
||||
|
||||
## Fire Alarm Devices
|
||||
### Fire Alarm Devices
|
||||
|
||||
### Residential
|
||||
#### Residential
|
||||
|
||||
* `System` = "EL - Electrical"
|
||||
|
||||
#### Smoke Detectors & CO Detectors
|
||||
##### Smoke Detectors & CO Detectors
|
||||
|
||||
For smoke detectors and CO detectors where 120V (most common):
|
||||
|
||||
@@ -145,11 +152,11 @@ For ADA units:
|
||||
|
||||
`COMMON ASSEMBLIES`/`UNITS - MC CABLE ASSEMBLIES`/`GENERAL ASSEMBLIES - METAL STUD`/`UNIT SMOKE DETECTOR / VISUAL SIGNAL ...`
|
||||
|
||||
#### Additional Signaling Devices
|
||||
##### Additional Signaling Devices
|
||||
|
||||
`COMMON ASSEMBLIES`/`FIRE ALARM & DAS SYSTEMS`/`INDICATING DEVICES WITH WIRE - ...`/`UNIT HORN/STROBE - ...`
|
||||
|
||||
### Key
|
||||
#### Key
|
||||
|
||||
* `System` = "FA - Fire Alarm"
|
||||
|
||||
|
||||
Reference in New Issue
Block a user