vault backup: 2025-10-28 17:01:24

.obsidian/community-plugins.json

@@ -11,5 +11,6 @@
   "quickadd",
   "image-converter",
   "recent-files-obsidian",
-  "obsidian-latex-suite"
+  "obsidian-latex-suite",
+  "obsidian-pretty-bibtex"
 ]

.obsidian/plugins/obsidian-pretty-bibtex/manifest.json

@@ -0,0 +1,10 @@
+{
+	"id": "obsidian-pretty-bibtex",
+	"name": "Pretty BibTeX",
+	"version": "2.0.1",
+	"minAppVersion": "0.15.0",
+	"description": "Shows raw BibTeX bibliography entries in a prettier way",
+	"author": "Sandro Figo",
+	"authorUrl": "https://sandrofigo.com",
+	"isDesktopOnly": false
+}

.obsidian/plugins/obsidian-pretty-bibtex/styles.css

@@ -0,0 +1,15 @@
+.bibtex.normal {
+    color: var(--text-faint);
+}
+
+.bibtex.value {
+    color: var(--text-muted);
+}
+
+.bibtex.key {
+    color: var(--text-faint);
+}
+
+.bibtex.header {
+    color: var(--text-accent);
+}

ai-in-estimating.md

@@ -2,11 +2,12 @@
 id:
 aliases: []
 tags:
-  - destiny/fleeting
   - topic/estimating
   - topic/software
   - type/philosophy
   - authorship/original
+  - status/incomplete
+  - destiny/permanent
 title: AI in Estimating
 ---
 # AI in Estimating

assembly-objects.md

@@ -2,12 +2,13 @@
 id:
 aliases: []
 tags:
+  - authorship/original
   - destiny/fleeting
+  - status/incomplete
   - topic/automation
   - topic/estimating
   - topic/software
   - type/idea
-  - authorship/original
 title: Assembly Objects
 ---
 # Assembly Objects

assembly-philosophy.md

@@ -2,10 +2,11 @@
 id:
 aliases: []
 tags:
+  - authorship/original
   - destiny/fleeting
+  - status/incomplete
   - topic/estimating
   - type/philosophy
-  - authorship/original
 title: Assembly Philosophy
 ---
 # Assembly Philosophy

automating-estimating-project-creation.md

@@ -2,11 +2,12 @@
 id:
 aliases: []
 tags:
+  - authorship/original
   - destiny/fleeting
+  - status/incomplete
   - topic/automation
   - topic/organization
   - topic/software
-  - authorship/original
 title: Automating Estimating Project Creation
 ---
 # Automating Estimating Project Creation

automating-pdf-annotation.md

@@ -2,11 +2,12 @@
 id:
 aliases: []
 tags:
+  - authorship/original
   - destiny/fleeting
+  - status/incomplete
   - topic/automation
   - topic/software
   - type/idea
-  - authorship/original
 title: Automating PDF Annotation
 ---
 # Automating PDF Annotation

bpm-award-analysis.md

@@ -7,6 +7,7 @@ tags:
   - topic/automation
   - type/idea
   - authorship/original
+  - status/incomplete
 title: BPM Award Analysis
 ---
 # BPM Award Analysis
@@ -17,11 +18,11 @@ The HUB > HUB Insights > WIGs, KPIs & milestones
 Inception to Date (ITD)
 
 $$
-"Overrun $" = "ITD Cost $" - "Baseline Cost $"
+\begin{gather*}
-
+\text{Overrun \$} = \text{ITD Cost \$} - \text{Baseline Cost \$} \\
-"Overrun %" = "Overrun $" / "Baseline Cost $"
+\text{Overrun \%} = \frac{\text{Overrun \$}}{\text{Baseline Cost \$}} \\
-
+\text{Overrun \%} = \frac{\text{ITD Cost \$}}{\text{Baseline Cost \$}} - 1
-"Overrun %" = "ITD Cost $" / "Baseline Cost $" - 1
+\end{gather*}
 $$
 
 > [!observation]

breakdown-objects.md

@@ -2,12 +2,13 @@
 id:
 aliases: []
 tags:
+  - authorship/original
   - destiny/fleeting
+  - status/incomplete
   - topic/automation
   - topic/estimating
   - topic/software
   - type/idea
-  - authorship/original
 title: Breakdown Objects
 ---
 # Breakdown Objects

construction-estimating.md

@@ -2,10 +2,11 @@
 id:
 aliases: []
 tags:
+  - authorship/original
   - destiny/permanent
+  - status/incomplete
   - topic/estimating
   - type/encyclopedia
-  - authorship/original
 title: Construction Estimating
 ---
 # Construction Estimating

distributed-antenna-systems-takeoff.md

@@ -38,36 +38,32 @@ Match Fire Alarm takeoff Length and Count
 
 ### Stairwell Riser Every 2 Floors
 
-`COMMON ASSEMBLIES`/`FIRE ALARM & DAS SYSTEMS`/`DAS ASSEMBLIES`/`STAIRWELL RISER EVERY 2 FLRS = 1 1/2" EMT (20') W/ 16X16X6 BOX`
+`Area` = "Typical - Building Even Levels"
 
-Create a Stairwell typical on every other floor
+`COMMON ASSEMBLIES`/`FIRE ALARM & DAS SYSTEMS`/`DAS ASSEMBLIES`/`STAIRWELL RISER EVERY 2 FLRS = ...`
 
 ### FACR to Electric Room
 
-`COMMON ASSEMBLIES`/`FIRE ALARM & DAS SYSTEMS`/`DAS ASSEMBLIES`/`FACR TO 2HR-RATED RM = 2" PVC40`
+`COMMON ASSEMBLIES`/`FIRE ALARM & DAS SYSTEMS`/`DAS ASSEMBLIES`/`FACR TO 2HR-RATED RM = ...`
 
 Match Fire Alarm takeoff Length
 
 ### Electric Room Riser to Every Floor
 
-`COMMON ASSEMBLIES`/`FIRE ALARM & DAS SYSTEMS`/`DAS ASSEMBLIES`/`2HR-RATED RM RISER TO EVERY FLR = 2" EMT (15') W/ 16X16X6 BOX`
+`COMMON ASSEMBLIES`/`FIRE ALARM & DAS SYSTEMS`/`DAS ASSEMBLIES`/`2HR-RATED RM RISER TO EVERY FLR = ...`
 
 Takeoff in every Electric Room
 
 ### Top 2H Rated Room To Roof
 
-`COMMON ASSEMBLIES`/`FIRE ALARM & DAS SYSTEMS`/`DAS ASSEMBLIES`/`TOP 2HR RATED RM TO ROOF = 2" EMT W/ RMC WEATHERHEAD & IMC STUB`
+`COMMON ASSEMBLIES`/`FIRE ALARM & DAS SYSTEMS`/`DAS ASSEMBLIES`/`TOP 2HR RATED RM TO ROOF = ...`
 
 Use 15' or Height of ceiling on last building level
 
 ## Horizontal
 
-CORRIDORS EMT OH = 1 1/2" EMT W/ 16X16X6 BOX EVERY 80'
-CA.28.31.23
-
-CORRIDORS DECK = 1 1/2" PVC40, STUBBY, FLEX W/ 16X16X6 BOX EVERY 80'
-CA.28.31.21
-
 1-1/2 through corridors w/ 16x16x6 J-Box
 
+`COMMON ASSEMBLIES`/`FIRE ALARM & DAS SYSTEMS`/`DAS ASSEMBLIES`/`CORRIDORS ...`
+
 Length for every corridor/garage

electrical-estimators-manual.md

@@ -2,10 +2,11 @@
 id: electrical-estimators-manual
 aliases: []
 tags:
-  - destiny/uncertain
-  - type/media-commentary
   - authorship/original
+  - destiny/permanent
+  - status/draft
   - topic/estimating
+  - type/media-commentary
 title: _Electrical Estimators Manual_
 ---
 # _Electrical Estimators Manual_

estimating-thoughts.base

@@ -20,6 +20,8 @@ views:
       - formula.type
       - formula.linkText
     sort:
+      - property: formula.status
+        direction: ASC
       - property: formula.type
         direction: DESC
       - property: file.size

favorite-quotes.md

@@ -4,6 +4,7 @@ aliases: []
 tags:
   - authorship/original
   - destiny/fleeting
+  - status/draft
 title: Favorite Quotes
 ---
 # Favorite Quotes

feeder-verification.md

@@ -7,6 +7,7 @@ tags:
   - topic/automation
   - type/guide
   - authorship/original
+  - status/incomplete
 title: Feeder Verification
 ---
 # Feeder Verification

fire-alarm-takeoff.md

@@ -35,20 +35,30 @@ Include [[sleeving-takeoff]] as necessary.
 
 ### Generator Room
 
+`Area` = Same as FACR
+
 `COMMON ASSEMBLIES`/`FIRE ALARM & DAS SYSTEMS`/`GEN, ELEV, FIRE PUMP & FA ROOM ASSEMBLIES`/`GENERATOR ROOM ...`
 
 ### Fire Pump Room
 
+`Area` = Same as FACR
+
 `COMMON ASSEMBLIES`/`FIRE ALARM & DAS SYSTEMS`/`GEN, ELEV, FIRE PUMP & FA ROOM ASSEMBLIES`/`FIRE PUMP ROOM ...`
 
 ### FACR to Elevator Shafts
 
+`Area` = Same as FACR
+
+For each elevator shaft:
+
 `COMMON ASSEMBLIES`/`FIRE ALARM & DAS SYSTEMS`/`GEN, ELEV, FIRE PUMP & FA ROOM ASSEMBLIES`/`ELEV SHAFT ...`
 
+Count = 1
+
 `COMMON ASSEMBLIES`/`FIRE ALARM & DAS SYSTEMS`/`GEN, ELEV, FIRE PUMP & FA ROOM ASSEMBLIES`/`FACR TO ELEV SHAFT ...`
 
-Measure Length from the most distant points of the FACR and each shaft.
+Length = Length measured from the most distant points of the FACR and elevator shaft.
-Input adder length to reach the bottom of the pit (Minimum 15ft).
+* Input adder length to reach the level of the shaft (Minimum 15ft).
 
 > [!important] Counting Elevator Shafts
 > Adjacent elevators may be in the same or parallel shafts.
@@ -65,34 +75,47 @@ Input adder length to reach the bottom of the pit (Minimum 15ft).
 
 ### FACR to Elevator Control Rooms
 
+For each Elevator Control Room (ECR):
+
 `COMMON ASSEMBLIES`/`FIRE ALARM & DAS SYSTEMS`/`GEN, ELEV, FIRE PUMP & FA ROOM ASSEMBLIES`/`ELEV CONTROL ROOM ...`
 
+Count = 1
+
 `COMMON ASSEMBLIES`/`FIRE ALARM & DAS SYSTEMS`/`GEN, ELEV, FIRE PUMP & FA ROOM ASSEMBLIES`/`FACR TO ELEV CONTROL RM ...`
 
-* Measure the Horizontal and Vertical Distance from the FACR to the ECR.
+Length = Length measured from the most distant points of the FACR and ECR.
-* Use Typicals for the vertical riser. (10ft per floor)
+* Input adder length to reach the level of the ECR (Minimum 15ft).
 
 ### FACR to Stairwells
 
 > [!info]
 > This is for the Flow/Tamper modules in the stairwells
 
-`COMMON ASSEMBLIES`/`FIRE ALARM & DAS SYSTEMS`/`GEN, ELEV, FIRE PUMP & FA ROOM ASSEMBLIES`/`FACR TO STAIRWELLS ...`
+For each stairwell:
 
-* Measure from the furthest end of FACR to the furthest end of the stairwell to find length
+`COMMON ASSEMBLIES`/`FIRE ALARM & DAS SYSTEMS`/`GEN, ELEV, FIRE PUMP & FA ROOM ASSEMBLIES`/`FACR TO STAIRWELLS 1" CONDUIT ...`
+
+Length = Length measured from the most distant points of the FACR and stairwell.
+* Input adder length to reach the level of the stairwell (Minimum 15ft).
 
 ### Terminal Cabinets
 
-`COMMON ASSEMBLIES`/`FIRE ALARM & DAS SYSTEMS`/`TERMINAL CABINET`/`ACE D ACCESSORY CABINET ENCLOSURE (2) 2" ...`
+`COMMON ASSEMBLIES`/`FIRE ALARM & DAS SYSTEMS`/`TERMINAL CABINET`/`ACE D ACCESSORY CABINET ENCLOSURE ...`
 
 * _Garden Style, High Density:_ (2) 1"C
 * _High Rise:_ (2) 2"C
 
 Horizontal:
-* Measure from the Fire Command room to all electrical rooms
+
+`Area` = Same as FACR
+
+**Length** = Length measured from FACR to all electrical rooms
 
 Vertical:
-* Use 10ft Riser in Typical
+
+`Area` = "Typical - Building All Levels"
+
+**Length** = 10ft
 
 ### Annunciator Panels
 
@@ -102,7 +125,7 @@ Vertical:
 
 `COMMON ASSEMBLIES`/`FIRE ALARM & DAS SYSTEMS`/`ANNUNCIATORS`/`REMOTE SERIAL ANNUNCIATOR ...`
 
-* Measure from the Fire Command Room to FAA or Lobby
+**Length** = Length measured from the FACR to FAA or Lobby
 
 ## Devices
 

functional-labor-factoring.md

@@ -26,14 +26,14 @@ laboring is the most interesting and rewarding part of the job.
 Discussions of human factors are far more engaging
 than those of statistical analysis.
 
-%%
+<!--
 TODO: discuss the necessity of comprehensive labor consumption insights
 and visualizations which are not currently feasible
 as an expectation of owners and contractors.
 
 Estimators know that doubling crew won't double production,
 but we must be able to offer evidence as such.
-%%
+-->
 
 Tables of labor factors given certain conditions
 can be converted to functions using regressions.
@@ -64,7 +64,7 @@ the prediction of labor of unstudied items.
 	month = {7},
 	number = {4},
 	pages = {331--337},
-	title = {{Benchmarking productivity Indicators for Electrical/Mechanical Projects}},
+	title = {Benchmarking productivity Indicators for Electrical/Mechanical Projects},
 	volume = {128},
 	year = {2002},
 	doi = {10.1061/(asce)0733-9364(2002)128:4(331},

gold-plating.md

@@ -2,12 +2,13 @@
 id:
 aliases: []
 tags:
+  - authorship/original
   - destiny/fleeting
   - status/complete
-  - topic/estimating
+  - topic/construction
+  - topic/construction/electrical
   - topic/risk
   - type/encyclopedia
-  - authorship/original
 title: Gold Plating
 ---
 # Gold Plating

lightning-protection.md

@@ -1,7 +1,12 @@
 ---
 id:
 aliases: []
-tags: []
+tags:
+  - authorship/original
+  - destiny/permanent
+  - topic/construction/electrical
+  - status/incomplete
+  - type/encyclopedia
 title: Lightning Protection
 ---
 # Lightning Protection

low-voltage-systems.md

@@ -1,7 +1,12 @@
 ---
 id:
 aliases: []
-tags: []
+tags:
+  - authorship/original
+  - destiny/permanent
+  - status/incomplete
+  - topic/construction/electrical
+  - type/encyclopedia
 title: Low Voltage Systems
 ---
 # Low Voltage Systems

multi-family-dwellings.md

@@ -1,7 +1,12 @@
 ---
 id:
 aliases: []
-tags: []
+tags:
+  - authorship/original
+  - destiny/permanent
+  - status/incomplete
+  - topic/construction
+  - type/encyclopedia
 title: Multifamily Dwellings
 ---
 # Multifamily Dwellings

optimal-estimating-patterns.md

@@ -15,34 +15,6 @@ title: Optimal Estimating Patterns
 [[construction-estimating-software]] consistently fails to innovate
 on the stale patterns developed for marginally similar applications decades ago.
 
-## Flaws of Traditional Patterns
-
-### Required Hyper-Specificity
-
-The reason that it's such a big deal to change between 1-hole straps and and unistrut straps
-is because it takes so long to do.
-If it was as simple as it is to visualize,
-which it could be if you were drawing these things and it was being interpreted,
-rather than having to explicitly specify every aspect of what you wanted.
-Then that would make a huge difference.
-
-In the (granted, limited) market segment that we've worked in,
-I use ~10 assemblies on a regular basis.
-That makes up 99% of the work.
-Why are there hundreds in in our database?
-They just need to be better.
-You could probably get away with hard coding some of this,
-even if that irks me,
-if they were good.
-It's just that it doesn't seem to be a goal
-that Trimble or anybody else has.
-
-### Assumed Finality
-
-While they may support a multitude of creative methods to create takeoffs,
-traditional methods are rarely as convenient when it comes to modify those takeoffs,
-as is frequently necessary as in the case of mistakes and revisions.
-
 ## More Optimal Patterns
 
 > [!note]
@@ -74,18 +46,43 @@ in terms of what existing estimators may be willing to accept
 #### Compared to Existing Frameworks
 
 Traditional methods interact with an existing database.
-EaC builds a static database at runtime.
+EaC builds a static database at runtime,
+allowing flexibility of input.
+
+* define variables
+* search and replace
+* undo
 
 #### Project Structure
 
 Organizational info (items, assemblies) as submodules.
 Solves database conflicts by pinning estimates to a commit.
 
-[[breakdown-objects]]
+#### Related Notes
-[[assembly-objects]]
+
+* [[breakdown-objects]]
+* [[assembly-objects]]
+* [[functional-labor-factoring]]
+
+### Bayesian Takeoff
+
+#### User Story
+
+Frank is estimating a 20-story high rise
+and notices that their are roughly, but not exactly,
+the same number of receptacles in the corridors of levels 2 to 19.
+Frank starts a new takeoff for duplex receptacles,
+typical of levels 2 to 19.
+He counts and inputs quantities for 3 levels,
+each adjusts the prior to calculate the expected quantity for all 18 levels.
 
 ### Sketch-Based Lookup
 
+<!-- TODO:
+This section is a transcription of a dictation.
+To be condensed.
+-->
+
 A better use for computer vision in estimating
 is sketch based assembly lookup.
 Probably the the biggest hang-up in the workflow

pathfinding.md

@@ -6,6 +6,7 @@ tags:
   - topic/software
   - type/idea
   - authorship/original
+  - status/incomplete
 title: Pathfinding
 ---
 # Pathfinding

pdi-estimating.md

@@ -6,6 +6,7 @@ tags:
   - occupational
   - type/encyclopedia
   - authorship/original
+  - status/incomplete
 title: PDI Estimating
 ---
 # PDI Estimating

project-info.md

@@ -2,11 +2,12 @@
 id:
 aliases: []
 tags:
+  - authorship/original
   - destiny/fleeting
+  - status/incomplete
   - topic/automation
   - topic/estimating
   - type/idea
-  - authorship/original
 title: Project Info
 ---
 # Project Info

pumpkin-coins-estimate.md

@@ -1,7 +1,12 @@
 ---
 id:
 aliases: []
-tags: []
+tags:
+  - authorship/original
+  - destiny/permanent
+  - topic/estimating
+  - type/idea
+  - status/incomplete
 title: Pumpkin Coins Estimate
 ---
 # Pumpkin Coins Estimate
@@ -14,7 +19,9 @@ title: Pumpkin Coins Estimate
 > Think you've got what it takes to guess the total value inside?
 >
 > 💰 Guess the Dollar Value in the Pumpkin
+> 
 > ...
+> 
 > 🕒 All votes due by 3:00 PM on Wednesday, 10/29
 >
 > Bring your best guess--the closest estimate wins big!

realism-vs-instrumentalism.md

@@ -2,8 +2,9 @@
 id:
 aliases: []
 tags:
-  - destiny/fleeting
   - authorship/original
+  - destiny/fleeting
+  - status/draft
 title: Realism vs. Instrumentalism
 ---
 # Realism vs. Instrumentalism

separating-estimating-concerns.md

@@ -2,12 +2,13 @@
 id:
 aliases: []
 tags:
+  - authorship/original
   - destiny/fleeting
+  - status/incomplete
   - topic/automation
   - topic/estimating
   - topic/software
   - type/philosophy
-  - authorship/original
 title: Separating Estimating Concerns
 ---
 # Separating Estimating Concerns
@@ -19,11 +20,11 @@ title: Separating Estimating Concerns
 > It is traditionally understood as a principle strictly of _software_ design,
 > however its applications are universal.
 
-%%
+<!--
 Minimize takeoff flow disruption
 
 Decouple takeoff (description of work) from assembly selection:
-%%
+-->
 
 ## 1. Annotation
 

sigmoid-functions.md

@@ -0,0 +1,27 @@
+---
+id:
+aliases: []
+tags:
+  - authorship/original
+  - destiny/permanent
+  - status/incomplete
+  - topic/math
+  - type/encyclopedia
+title: Sigmoid Functions
+---
+# Sigmoid Functions
+
+![[sigmoid-function-example.excalidraw]]
+
+$f'(x)$ is a **sigmoid** function.
+
+A sigmoid function compresses a function with infinite range to (0,1)
+
+This is preferable to a floor-ceiling piece-wise function
+since it remains differentiable.
+
+## Formula
+
+$$
+\sigma(x) = \frac{1}{1 + e^{-x}}
+$$

stochastic-branch-takeoff.md

@@ -2,11 +2,12 @@
 id:
 aliases: []
 tags:
+  - authorship/original
   - destiny/fleeting
+  - status/incomplete
   - topic/construction/electrical
   - topic/estimating
   - type/idea
-  - authorship/original
 title: Stochastic Branch Takeoff
 ---
 # Stochastic Branch Takeoff
@@ -44,24 +45,4 @@ varies greatly with the aspect ratio of the space.
 Weighted by a probability distribution
 an average length and confidence could be given for any known area.
 
-I remember seeing a video on machine learning(?)
+[[sigmoid-functions]]
-that described a class of functions(?)
-used to change(?) a function with infinite range.
-Something like this:
-
-![[function-example.excalidraw.md]]
-
-$f'(x)$ is a **sigmoid** function.
-
-This is preferable to a floor-ceiling piece-wise function
-since it remains differentiable.
-
-Maybe suckerpinch's latest video on the Rupert property
-or 3blue1brown's on Euler's Formula.
-
-Actually I think its neither of those,
-but a more general ML video by another creator
-that used mango cultivar classification by dimensions
-as an example.
-
-

strategy.md

@@ -56,4 +56,6 @@ Opposite of a conventional "open" auction,
 in a sealed-bid auction,
 bid prices are hidden from the bidders.
 
+[[uncertainty#Information]]
+
 <!-- TODO: -->

supertopics.md

@@ -6,6 +6,7 @@ tags:
   - topic/organization
   - type/encyclopedia
   - authorship/original
+  - status/incomplete
 title: Supertopics
 ---
 # Supertopics

traditional-estimating-methods.md

@@ -61,3 +61,34 @@ and to adjust for all labor conditions and market factors _exactly_.
 
 Most estimators wouldn't rate their margin of error at less than 10%,
 though most would refuse to answer anyway (see [[estimating-culture]]).
+
+#### Required Hyper-Specificity
+
+<!-- TODO:
+This section is a transcription of a dictation.
+To be condensed.
+-->
+
+The reason that it's such a big deal to change between 1-hole straps and and unistrut straps
+is because it takes so long to do.
+If it was as simple as it is to visualize,
+which it could be if you were drawing these things and it was being interpreted,
+rather than having to explicitly specify every aspect of what you wanted.
+Then that would make a huge difference.
+
+In the (granted, limited) market segment that we've worked in,
+I use ~10 assemblies on a regular basis.
+That makes up 99% of the work.
+Why are there hundreds in in our database?
+They just need to be better.
+You could probably get away with hard coding some of this,
+even if that irks me,
+if they were good.
+It's just that it doesn't seem to be a goal
+that Trimble or anybody else has.
+
+#### Assumed Finality
+
+While they may support a multitude of creative methods to create takeoffs,
+traditional methods are rarely as convenient when it comes to modify those takeoffs,
+as is frequently necessary as in the case of mistakes and revisions.

two-way-takeoff.md

@@ -10,9 +10,9 @@ tags:
   - occupational/takeoff/standalone-systems
   - status/draft
   - type/guide
-title: Area of Refuge (AoR) Takeoff
+title: Two-Way Takeoff
 ---
-# Area of Refuge (AoR) Takeoff
+# Two-Way Takeoff
 
 > [!important]
 > Complete [[emergency-systems-research]] before beginning takeoff.
@@ -21,25 +21,28 @@ title: Area of Refuge (AoR) Takeoff
 > See [[emergency-communications-systems]] for information
 > about Two-Way and AoR communication systems.
 
+> `System` = "FA - Two Way Communication"
+
 ## Horizontal
 
-> Area: Same as Fire Command Room
+> `Area` = Same as Fire Command Room
 
-`FIRE ALARM & DAS SYSTEMS`/`TWO WAY COMMUNICATION ASSEMBLIES`/`...`
+`FIRE ALARM & DAS SYSTEMS`/`TWO WAY COMMUNICATION ASSEMBLIES`/`2-WAY COMMUNICATION = 1" CONDUIT ...`
 
-* Length: Per drawings if shown, otherwise use longer of
+**Length** = Per drawings if shown, otherwise use longer of
-    * FCR to elevator lobbies
+* FCR to elevator lobbies
-    * FCR to stairwells
+* FCR to stairwells
 
-* Count: Number of boxes run to. Per drawings if shown, otherwise use the greater of:
+**Count** = Number of boxes run to. Per drawings if shown, otherwise use the greater of:
-    * Count of elevators
+* Count of elevators
-    * Count of stairwells
+* Count of stairwells
 
 ## Vertical
 
-> Area: "Typical - Building All Levels"
+> `Area` = "Typical - Building All Levels"
 
-`FIRE ALARM & DAS SYSTEMS`/`TWO WAY COMMUNICATION ASSEMBLIES`/`...`
+`FIRE ALARM & DAS SYSTEMS`/`TWO WAY COMMUNICATION ASSEMBLIES`/`2-WAY COMMUNICATION = 1" CONDUIT ...`
 
-* Length: 15ft x count
+**Length** = 15ft x Count
-* Count: match Horizontal
+
+**Count** = match Horizontal

uncertainty.md

@@ -25,14 +25,32 @@ In statistical inference and [[strategy]],
 > is the amount a decision maker would be willing to pay
 > for information prior to making a decision.
 
-It is the value of the reduction in uncertainty
+Suppose information $I$ is available to a decision maker
-that the information provides.
+Consider these two scenarios:
 
-In a monetary context, it is the reduction of
+1. the decision maker does not purchase the information
-expected opportunity loss.
+  and makes \$9,000. $P(D)=9000$
+
+2. the decision maker purchases the information
+  and makes \$10,000 $P(D)|I=10000$
+
+The monetary value of $I$ is the difference between the payout
+without ($P(D)$) and with ($P(D)|I$) the information $I$.
 
 $$
-\text{EVI} = \text{EOL} - \text{EOL}|I
+\begin{align*}
+V(I) &= P(D)|I - P(D) \\
+&= (10000) - (9000) \\
+&= 1000
+\end{align*}
+$$
+
+> [!info] Expectation Notation
+> When forecasting, the payout of decisions is unknown,
+> thus
+
+$$
+\mathbb{E}\left[V(I)\right] = \mathbb{E}\left[P(D)\right] - \mathbb{E}\left[P(D)|I\right]
 $$
 
 ### Expected Value of Perfect Information