vault backup: 2025-10-01 17:05:32

This commit is contained in:
2025-10-01 17:05:32 -04:00
parent e0a10cfe49
commit 84f69ea865
62 changed files with 365 additions and 325 deletions
+3 -3
View File
@@ -17,7 +17,7 @@
"editor-status": true,
"bookmarks": true,
"markdown-importer": true,
"zk-prefixer": false,
"zk-prefixer": true,
"random-note": false,
"outline": true,
"word-count": true,
@@ -26,8 +26,8 @@
"workspaces": false,
"file-recovery": true,
"publish": false,
"sync": true,
"sync": false,
"webviewer": false,
"footnotes": false,
"footnotes": true,
"bases": true
}
+2 -2
View File
@@ -1,7 +1,7 @@
{
"settings": {
"flashcardTags": [
"#fleeting"
"#destiny/fleeting"
],
"convertFoldersToDecks": false,
"burySiblingCards": false,
@@ -22,7 +22,7 @@
"editLaterTag": "#edit-later",
"enableNoteReviewPaneOnStartup": true,
"tagsToReview": [
"#review"
"#destiny/fleeting"
],
"noteFoldersToIgnore": [
"**/*.excalidraw.md"
+52 -52
View File
@@ -1,5 +1,57 @@
{
"recentFiles": [
{
"basename": "fixture-designations",
"path": "fixture-designations.md"
},
{
"basename": "fixtures",
"path": "fixtures.md"
},
{
"basename": "full-takeoff",
"path": "full-takeoff.md"
},
{
"basename": "portable-tools",
"path": "portable-tools.md"
},
{
"basename": "README",
"path": "README.md"
},
{
"basename": "tags",
"path": "tags.md"
},
{
"basename": "estimating-ergonomics",
"path": "estimating-ergonomics.md"
},
{
"basename": "separating-estimating-concerns",
"path": "separating-estimating-concerns.md"
},
{
"basename": "separation-of-concerns",
"path": "separation-of-concerns.md"
},
{
"basename": "this-notebook",
"path": "this-notebook.md"
},
{
"basename": "Untitled",
"path": "Untitled.md"
},
{
"basename": "electrical",
"path": "electrical.md"
},
{
"basename": "3-phase-power",
"path": "3-phase-power.md"
},
{
"basename": "accubid-setup",
"path": "accubid-setup.md"
@@ -12,18 +64,10 @@
"basename": "material-pricing",
"path": "material-pricing.md"
},
{
"basename": "full-takeoff",
"path": "full-takeoff.md"
},
{
"basename": "supertopics",
"path": "supertopics.md"
},
{
"basename": "README",
"path": "README.md"
},
{
"basename": "risk",
"path": "risk.md"
@@ -56,10 +100,6 @@
"basename": "realism-vs-instrumentalism",
"path": "realism-vs-instrumentalism.md"
},
{
"basename": "this-notebook",
"path": "this-notebook.md"
},
{
"basename": "telecom",
"path": "telecom.md"
@@ -72,10 +112,6 @@
"basename": "90-day-performance-review",
"path": "90-day-performance-review.md"
},
{
"basename": "3-phase-power",
"path": "3-phase-power.md"
},
{
"basename": "construction-estimating",
"path": "construction-estimating.md"
@@ -144,10 +180,6 @@
"basename": "estimating-dimensionality",
"path": "estimating-dimensionality.md"
},
{
"basename": "estimating-ergonomics",
"path": "estimating-ergonomics.md"
},
{
"basename": "estimating-detail",
"path": "estimating-detail.md"
@@ -167,38 +199,6 @@
{
"basename": "calibration-questions",
"path": "calibration-questions.md"
},
{
"basename": "automating-pdf-annotation",
"path": "automating-pdf-annotation.md"
},
{
"basename": "assembly-philosophy",
"path": "assembly-philosophy.md"
},
{
"basename": "ai-in-estimating",
"path": "ai-in-estimating.md"
},
{
"basename": "feeder-verification",
"path": "feeder-verification.md"
},
{
"basename": "feeder-sizing",
"path": "feeder-sizing.md"
},
{
"basename": "list",
"path": "list.md"
},
{
"basename": "birds",
"path": "birds.md"
},
{
"basename": "breakdowns",
"path": "breakdowns.md"
}
],
"omittedPaths": [],
+3 -3
View File
@@ -2,10 +2,10 @@
id: 2025-07-18_estimating-isnt-engineering
aliases: []
tags:
- type/anecdote
- topic/estimating
- status/incomplete
- destiny/permanent
- status/incomplete
- topic/estimating
- type/anecdote
---
# Estimating Isn't Engineering
+3 -3
View File
@@ -2,8 +2,8 @@
id:
aliases: []
tags:
- occupational
- destiny/permanent
- occupational
---
# 90-Day Performance Review
@@ -117,7 +117,7 @@ and seeks help for more complex situations.
Regularly achieves performance targets and actions.
## Decision Quality
## Decision Quality
Makes decisions with confidence,
balancing short- and long-term goals.
@@ -185,7 +185,7 @@ and helps identify resources for learning.
Regularly achieves performance targets and actions.
## Technical
## Technical
Handles routine technical tasks
with growing confidence and minimal support.
+10 -5
View File
@@ -1,15 +1,17 @@
---
id:
aliases: []
excalidraw-plugin: parsed
tags: [excalidraw]
tags:
- excalidraw
---
==⚠ Switch to EXCALIDRAW VIEW in the MORE OPTIONS menu of this document. ⚠== You can decompress Drawing data with the command palette: 'Decompress current Excalidraw file'. For more info check in plugin settings under 'Saving'
==⚠ Switch to EXCALIDRAW VIEW in the MORE OPTIONS menu of this document. ⚠== You can decompress Drawing data with the command palette: 'Decompress current Excalidraw file'. For more info check in plugin settings under 'Saving'
# Excalidraw Data
## Text Elements
Bldg A ^bLRdNvMD
Bldg B ^9Fro5dQn
@@ -19,7 +21,9 @@ MDPB ^6VX5FXYi
MDPA ^LnSPklkP
%%
## Drawing
```compressed-json
N4KAkARALgngDgUwgLgAQQQDwMYEMA2AlgCYBOuA7hADTgQBuCpAzoQPYB2KqATLZMzYBXUtiRoIACyhQ4zZAHoFAc0JRJQgEYA6bGwC2CgF7N6hbEcK4OCtptbErHALRY8RMpWdx8Q1TdIEfARcZgRmBShcZQUebQBGABYEmjoghH0EDihmbgBtcDBQMBKIEm4ICgBpAE4ARR5sGAA1AGYABWxsAE0EZwANAClB/AB9KFSSyFhECsDsKI5lYMnS
@@ -71,4 +75,5 @@ DUtO/MZs4vM8wNgDCJyP0NwN8m5kpFs8iPgN0IzblL5bdBAEYGwAYKo+WAQITE8L6gswk5k84mOms/5P
/SmjceCeycmMNNaruJkqwemgFRssOQXI/ScAULML/S8LntajhI30jAS0Nz+Adzd0qzYQwQCwCUdGQgUIBgKzoq6F0jmFjkBgXI6Q7ry90ZjdUIc07rdrDrbqj44ATcS+wQEY8YIA8YQAA===
```
%%
%%
+1 -1
View File
@@ -2,8 +2,8 @@
id:
aliases: []
tags:
- topic/electrical
- authorship/other
- topic/electrical
---
# 314.28 Pull and Junction Boxes and Conduit Bodies.
+6 -180
View File
@@ -4,8 +4,11 @@ aliases:
- home
- zmVault
tags:
- authorship/original
- destiny/permanent
- status/incomplete
- topic/meta
- type/encyclopedia
---
# zmVault
@@ -21,184 +24,7 @@ for use in editors other than Obsidian.
Novel syntax implemented by Obsidian plugins should be avoided.
## Tags
## Organization
These tags are presented in an associative order.
### #destiny
`#destiny` describes the permanency of an item.
It does not necessarily reflect its current [[README#status]].
#### #destiny/fleeting
The content of an item tagged `#destiny/fleeting`
will ultimately be absorbed into another note
and the file deleted.
These notes may deviate from standard formatting.
#### #destiny/permanent
Notes tagged `#destiny/permanent` are intended for long-term use.
They are expected to reflect standard formatting
and should be heavily tagged and linked.
### #status
`#status` reflects the remaining work necessary
to bring an item to the standard of its [[README#destiny]].
#### #status/incomplete
Beyond intent, the note offers little to go on.
#### #status/draft
The main content of the note is present, but:
* text may need to be reflowed
* links may need to be added
* citations may be necessary
#### #status/complete
The text flows well,
the note is sufficiently tagged and linked,
and citations are included as appropriate
### #topic
Notes can and usually will have multiple topic tags.
#### #topic/meta
Relating to the structure or intent of this notebook.
#### #topic/software
Relating to specific software written by others,
or hypothetical software functionality I've conceived.
The latter I generally relegate to [[README#destiny/fleeting]],
to be absorbed into the specifications of the relevant project
when the idea is sufficiently developed.
#### #topic/automation
On the subject of lightweight scripts
that could reduce redundancy in processes,
without requiring fundamental change.
#### #topic/electrical
Relating to electrical installation,
including:
* code
* material
#### #topic/estimating
Relating to the field of cost estimation,
as understood in [[construction-estimating]]
as well as other industries.
This topic also includes concepts that may be useful to estimation,
but that aren't widely understood to be.
#### #topic/math
#### #topic/risk
Relating to mathematical and abstract concepts of [[risk]].
#### #topic/organization
On the subject of [[optimal-patterns]] for processes
of varying importance.
#### #topic/other
Notes relating to subjects not relevant to this notebook's [[supertopics]],
but that I include for the convenience of editing them in Obsidian.
Some standouts include:
* [[birds|Birdwatching]]
* [[list|Warhammer 40,000]]
### #occupational
Items tagged `#occupational` include information and instructions
relevant to my current occupation
that may not reflect [[construction-estimating]] practice
in the wider industry.
> [!info]
> This tag is largely separate from the wider vault.
> I would probably move them to their own repository
> were it not for the complexity of preserving the version history of both.
#### #occupational/systems
> [!important]
> Notes tagged `#occupational/systems/*` include information as understood by PDI,
> which is not necessarily consistent with (and often sharply deviates from)
> wider industry understanding.
### #type
#### #type/idea
Items of `#type/idea` are recommendation
that I do something in the future,
possibly including some details of how to go about it.
They have the minimum amount of information
necessary to allow me to return to them.
They are always? of [[README#destiny/fleeting]].
#### #type/guide
<!--TODO-->
#### #type/encyclopedia
Items of `#type/encyclopedia` are thorough,
use exact language, and include citations.
They describe concepts as they are, not as they should be.
#### #type/philosophy
Items of `#type/philosophy` are highly opinionated.
They describe concepts as I believe them to be.
They are always? of [[README#authorship/original]].
#### #type/anecdote
<!--TODO-->
#### #type/media-commentary
<!--TODO-->
### #authorship
`#authorship` reflects my claim to the content of an item
_in its current state_.
#### #authorship/original
Items of `#authorship/original` are primarily my own work.
Content from other sources is properly cited.
#### #authorship/other
> [!info]
> I'm unsatisfied with the name of this tag.
> It is subject to change.
Items of `#authorship/other` are not my own work.
They may be of one source a collection of several
without significant commentary.
All notes are located in the main directory.
[[tags]] are used for filtering.
View File
+1 -1
View File
@@ -2,8 +2,8 @@
id:
aliases: []
tags:
- type/guide
- occupational
- type/guide
---
# Accubid Setup
+4 -2
View File
@@ -1,8 +1,10 @@
---
id:
aliases: []
tags:
- destiny/fleeting
- topic/estimating
- topic/software
- destiny/fleeting
- type/philosophy
---
# AI in Estimating
@@ -24,4 +26,4 @@ Estimating specific AI features, being unpredictable literally by design,
will inevitably be inconsistent in reliability between implementations;
a glaring issue since they will be provided by apps with no external compatibility.
Most of these features are far better implemented with traditional computing.
Most of these features are far better implemented with traditional computing.
+2 -2
View File
@@ -1,9 +1,9 @@
---
id:
aliases:
- 2-way-communication
- area-of-rescue
- two-way-communication
- 2-way-communication
tags:
- occupational/systems/standalone-systems
- type/guide
@@ -60,5 +60,5 @@ Complete [[fire-alarm]] preparation and takeoff.
* Length: 15ft x per count
* Count: match Horizontal
### 3. Extension (Review and Checking)
+1 -1
View File
@@ -2,8 +2,8 @@
id:
aliases: []
tags:
- topic/estimating
- destiny/fleeting
- topic/estimating
- type/philosophy
---
# Assembly Philosophy
+1 -1
View File
@@ -2,10 +2,10 @@
id:
aliases: []
tags:
- destiny/fleeting
- topic/automation
- topic/organization
- topic/software
- destiny/fleeting
- type/encyclopedia
---
# Automating Email
+1 -1
View File
@@ -2,10 +2,10 @@
id:
aliases: []
tags:
- destiny/fleeting
- topic/automation
- topic/organization
- topic/software
- destiny/fleeting
---
# Automating Estimating Project Creation
+2 -2
View File
@@ -2,9 +2,9 @@
id:
aliases: []
tags:
- destiny/fleeting
- topic/automation
- topic/software
- destiny/fleeting
- type/idea
---
# Automating PDF Annotation
@@ -107,4 +107,4 @@ q
4230 3891 l
4230 3947 l
...
```
```
+1 -1
View File
@@ -2,8 +2,8 @@
id:
aliases: []
tags:
- topic/other
- destiny/fleeting
- topic/other
- type/encyclopedia
---
# Birds I've Seen Around Here
+2 -2
View File
@@ -2,9 +2,9 @@
id:
aliases: []
tags:
- topic/automation
- occupational
- destiny/fleeting
- occupational
- topic/automation
- type/idea
---
# BPM Award Analysis
+1 -1
View File
@@ -2,10 +2,10 @@
id:
aliases: []
tags:
- destiny/fleeting
- topic/automation
- topic/estimating
- topic/software
- destiny/fleeting
- type/idea
---
# Breakdown Objects
+1 -1
View File
@@ -2,8 +2,8 @@
id:
aliases: []
tags:
- occupational
- authorship/other
- occupational
---
# Breakdowns
+3 -3
View File
@@ -1,10 +1,10 @@
---
id:
aliases: []
tags:
- topic/risk
- topic/estimating
tags:
- destiny/fleeting
- topic/estimating
- topic/risk
- type/encyclopedia
---
# Calibration Questions
+1 -1
View File
@@ -2,9 +2,9 @@
id:
aliases: []
tags:
- destiny/permanent
- topic/estimating
- type/philosophy
- destiny/permanent
---
# Construction Estimating
+1 -1
View File
@@ -2,8 +2,8 @@
id:
aliases: []
tags:
- type/guide
- occupational
- type/guide
---
# Design Build Budget
+1 -2
View File
@@ -4,7 +4,7 @@ aliases: []
tags:
- type/media-commentary
---
# *Electrical Estimating Methods*
# _Electrical Estimating Methods_
Electrical Estimating Methods, Fourth Edition
(Wayne J. Del Pico)
@@ -32,4 +32,3 @@ Electrical Estimating Methods, Fourth Edition
## Overall
* Incredible book, I would love to have a copy
+2 -2
View File
@@ -4,7 +4,7 @@ aliases: []
tags:
- type/media-commentary
---
# *Electrical Estimators Manual*
# _Electrical Estimators Manual_
Electrical Estimators Manual:
How to Estimate Electrical Construction Projects Including Everyday Labor Installation Rates
@@ -20,7 +20,7 @@ How to Estimate Electrical Construction Projects Including Everyday Labor Instal
* Notable Inclusions
* Labor hours
* Unit conversions
* Unit conversions
* too many, including rare units
* Checklist
* VERY brief
+1 -1
View File
@@ -2,10 +2,10 @@
id:
aliases: []
tags:
- destiny/fleeting
- topic/automation
- topic/estimating
- topic/software
- destiny/fleeting
- type/idea
---
# Estimating as Code
+3 -1
View File
@@ -1,7 +1,9 @@
---
id:
aliases: []
tags:
- topic/estimating
- topic/project-management
- topic/organization
- type/philosophy
---
# Estimating Culture
+3 -1
View File
@@ -1,8 +1,10 @@
---
id:
aliases: []
tags:
- topic/estimating
- topic/software
- topic/organization
- topic/software
- type/idea
---
# Estimating Dimensionality
+1 -1
View File
@@ -2,9 +2,9 @@
id:
aliases: []
tags:
- destiny/fleeting
- topic/estimating
- topic/software
- destiny/fleeting
- type/idea
---
# Estimating Ergonomics
+2
View File
@@ -1,4 +1,6 @@
---
id:
aliases: []
tags:
- topic/estimating
- type/philosophy
+1 -1
View File
@@ -2,8 +2,8 @@
id:
aliases: []
tags:
- occupational
- authorship/other
- occupational
---
## Create a WBS
+2 -2
View File
@@ -32,7 +32,7 @@ Given a minimum ampacity, find all valid configurations.
> for each phase, polarity, neutral, or grounded circuit
> shall be permitted to be connected in parallel
> (electrically joined at both ends)
> *only in sizes 1/0 AWG and larger*
> _only in sizes 1/0 AWG and larger_
> where installed in accordance with 310.10(H)(2) through (H)(6).
Rank by total cost of install.
@@ -48,4 +48,4 @@ can be assumed out of scope.
Wire and EGC conductors are usually assumed to match,
but it is sometimes preferable to use a copper EGC
with high-amp aluminum parallel feeds.
with high-amp aluminum parallel feeds.
+2 -2
View File
@@ -2,9 +2,9 @@
id:
aliases: []
tags:
- topic/automation
- occupational
- destiny/fleeting
- occupational
- topic/automation
- type/guide
---
# Feeder Verification
+2 -2
View File
@@ -79,8 +79,8 @@ This is for the Flow/Tamper modules in the stairwells
`COMMON ASSEMBLIES`/`FIRE ALARM & DAS SYSTEMS`/`TERMINAL CABINET`/`ACE D ACCESSORY CABINET ENCLOSURE (2) 2" ...`
* *Garden Style, High Density:* (2) 1"C
* *High Rise:* (2) 2"C
* _Garden Style, High Density:_ (2) 1"C
* _High Rise:_ (2) 2"C
Horizontal:
* Measure from the Fire Command room to all electrical rooms
+3 -3
View File
@@ -41,7 +41,7 @@ Use empty designations to separate phases.
| Fixture Type | Labor |
| ------------ | ------------ |
| Paddle Fan | 1.5 hrs/ea |
| Pendant | 1-4 hrs/ea |
| Pendant | 1-4 hrs/ea |
| Strip/Cove | 0.083 hrs/ft |
| Site Poles | 1.5 hrs/ea |
| Festoon | 2 hrs/ea |
@@ -51,7 +51,7 @@ Use empty designations to separate phases.
| Case | Standard Length |
| --------------------- | --------------- |
| Site/Courtyard | 50ft |
| Site/Courtyard | 50ft |
| Garage | 50ft |
| BOH | 40ft |
| Corridors | 40ft |
@@ -221,7 +221,7 @@ Create its own breakout in WBS, and phase in Accubid
| Bollard | `COURTYARDS & LANDSCAPE`/`BOLLARD, 3/4" CONDUIT - PVC40 - ...`[^1] |
| Up-light | `COURTYARDS & LANDSCAPE`/`PERMA POST, 3/4" CONDUIT - PVC40 - ...` |
| In-grade up-light | `COURTYARDS & LANDSCAPE`/`3/4" CONDUIT - PVC40, IMC Elbow, ...` |
| Fixtures built into cabanas/pergolas | `COURTYARDS & LANDSCAPE`/`ALUM BOX W/ FLEX FIX, 3/4" CONDUIT - PVC40 - ...` |
| Fixtures built into cabanas/pergolas | `COURTYARDS & LANDSCAPE`/`ALUM BOX W/ FLEX FIX, 3/4" CONDUIT - PVC40 - ...` |
| Handrail light | `COURTYARDS & LANDSCAPE`/`ALUM BOX W/ FLEX FIX, 3/4" CONDUIT - PVC40, IMC ELBOW - ...` |
[^1]: If we don't own concrete, delete Pre-cast bollard base from assembly
+1 -1
View File
@@ -2,8 +2,8 @@
id:
aliases: []
tags:
- type/guide
- occupational
- type/guide
---
# Full Takeoff
+1 -1
View File
@@ -2,10 +2,10 @@
id:
aliases: []
tags:
- destiny/fleeting
- topic/automation
- topic/estimating
- topic/software
- destiny/fleeting
---
# Functional Labor Factoring
+2 -2
View File
@@ -1,9 +1,9 @@
---
id:
aliases: []
tags:
- topic/risk
tags:
- destiny/fleeting
- topic/risk
---
# Gut Feel
+1 -1
View File
@@ -24,7 +24,7 @@ Not to be confused with [[telecom]].
EMT to accessible space?
PVC to MDF?
#### Devices
#### Devices
#### Daisy Chaining
+1 -1
View File
@@ -2,9 +2,9 @@
id:
aliases: []
tags:
- destiny/fleeting
- topic/automation
- topic/software
- destiny/fleeting
- type/idea
---
# Markdown Formatter CLI
@@ -2,11 +2,11 @@
id: mike-holts-illustrated-guide-to-electrical-estimating
aliases: []
tags:
- type/media-commentary
- topic/electrical
- topic/estimating
- type/media-commentary
---
# *Mike Holt's Illustrated Guide to Electrical Estimating*
# _Mike Holt's Illustrated Guide to Electrical Estimating_
Holt, C. M. (2023). Mike Holt's Illustrated Guide to Electrical Estimating. Mike Holt Enterprises, Inc
+1 -1
View File
@@ -2,8 +2,8 @@
id:
aliases: []
tags:
- occupational
- authorship/other
- occupational
---
# NEW HIRE - ESTIMATOR
+1 -1
View File
@@ -1,7 +1,7 @@
---
id:
aliases: []
tags:
tags:
- topic/estimating
---
# Open Problems in Estimating
+1 -1
View File
@@ -24,4 +24,4 @@ p1.y = 6.0d;
// ??? = Pathfinder.Taxicab(p1, p2)
```
```
+1 -1
View File
@@ -2,8 +2,8 @@
id:
aliases: []
tags:
- occupational
- destiny/fleeting
- occupational
- type/philosophy
---
# PDI Estimating
+3 -1
View File
@@ -1,4 +1,6 @@
---
id:
aliases: []
tags:
- topic/software
---
@@ -21,4 +23,4 @@ which may make these possible as well:
* Asciidoctor
* Antora
* taskjuggler
* taskjuggler
+2 -2
View File
@@ -3,8 +3,8 @@ id:
aliases: []
tags:
- destiny/fleeting
- topic/automation
- occupational
- topic/automation
- type/idea
---
# Project Info
@@ -53,4 +53,4 @@ Even proposals are truly better suited to this format as,
neglecting the former benefits,
markdown can be rendered with standard stylesheets for improved consistency.
Sublime is a friendly option for non-technical users.
Sublime is a friendly option for non-technical users.
+3 -1
View File
@@ -1,6 +1,8 @@
---
id:
aliases: []
tags:
- topic/project-management
- topic/organization
---
# Project Management™
+1 -1
View File
@@ -2,8 +2,8 @@
id:
aliases: []
tags:
- type/guide
- occupational
- type/guide
next: setup-accubid
---
# Project Setup
+1 -1
View File
@@ -1,7 +1,7 @@
---
id:
aliases: []
tags:
tags:
- occupational
- type/guide
---
+2
View File
@@ -1,4 +1,6 @@
---
id:
aliases: []
tags:
- destiny/fleeting
---
+1 -1
View File
@@ -2,8 +2,8 @@
id:
aliases: []
tags:
- occupational
- destiny/fleeting
- occupational
- type/guide
---
# Requirement Precedence
+3 -3
View File
@@ -69,7 +69,7 @@ Optimizing the takeoff process means:
> Recent events have complicated my philosophy above.
> It appears that similar efforts have already been made here,
> their success being a matter of perspective.
> Is it acceptable that optimal
> Is it acceptable that optimal
#### Naming Conventions (Use Case vs. Description)
@@ -145,11 +145,11 @@ Uncertainty being a necessity of estimating,
the language and tools that we use
must facilitate discussions of risk management.
In estimation in fields other than construction
it is common to give an estimate as a *confidence interval*,
it is common to give an estimate as a _confidence interval_,
a range in which a result has a certain percentage chance to fall.
This interval can be determined from a population of possible prices.
The *accuracy* of a risk-oriented estimate remains roughly the same
The _accuracy_ of a risk-oriented estimate remains roughly the same
(approaching 100% with continuous input)
through the takeoff process and, assuming no incorrect input,
is entirely out of the hands of the estimator doing the "takeoff".
+2 -2
View File
@@ -2,10 +2,10 @@
id:
aliases: []
tags:
- destiny/fleeting
- topic/automation
- topic/estimating
- topic/software
- destiny/fleeting
---
# Separating Estimating Concerns
@@ -15,7 +15,7 @@ Annotation is documenting project scope as intended by its design.
This involves reconciling missing and conflicting requirements,
as well as erroneous and misplaced symbols.
This process is intended to be *unbiased*, without respect for
This process is intended to be _unbiased_, without respect for
* industry knowledge
* contractor standard practices
+2
View File
@@ -1,4 +1,6 @@
---
id:
aliases: []
tags:
- topic/estimating
- topic/software
+1 -1
View File
@@ -1,7 +1,7 @@
---
id:
aliases: []
tags:
tags:
- topic/risk
---
# Strategy
+6 -6
View File
@@ -28,8 +28,8 @@ tags:
| Construction Type | Wiring Method | Subfeed Options |
| ----------------- | ------------- | --------------- |
| 1,2 | MC Cable | MC, PVC, EMT |
| 3,4,5 | NM Cable | SER, EMT |
| 1,2 | MC Cable | MC, PVC, EMT |
| 3,4,5 | NM Cable | SER, EMT |
%%
TODO: Create flow chart for wiring methods.
@@ -58,7 +58,7 @@ Pigtail adaptors are used where feeder wires exceed the range of panel lugs.
| ---------------- | --------------- |
| 100A | 2/0 AWG |
| 125A | 3/0 AWG |
| 150A | 4/0 AWG |
| 150A | 4/0 AWG |
| 225A | 300 kcmil |
| 400A | 500 kcmil |
@@ -74,9 +74,9 @@ Pigtail adaptors are used where feeder wires exceed the range of panel lugs.
Only for PVC subfeeds where we own voltage drop.
- `Area` = "Typical - Building Levels With Meter Centers"
- `System` = "Electrical"
- `Phase` = "Sub Feeders"
* `Area` = "Typical - Building Levels With Meter Centers"
* `System` = "Electrical"
* `Phase` = "Sub Feeders"
`ITEM DATABASE`/`DISTRIBUTION`/`BUDGET ITEMS $ & LBR`/`METER CENTER WIRE TROUGH ($400/E)`
+2 -2
View File
@@ -1,9 +1,9 @@
---
id:
aliases: []
tags:
- topic/organization
tags:
- destiny/fleeting
- topic/organization
- type/encyclopedia
---
# Supertopics
+191
View File
@@ -0,0 +1,191 @@
---
id: tags
aliases: []
tags:
- authorship/original
- destiny/permanent
- status/incomplete
- topic/meta
- type/encyclopedia
---
# Tags
These tags are presented in an associative order.
## #destiny
`#destiny` describes the permanency of an item.
It does not necessarily reflect its current [[README#status]].
### #destiny/fleeting
The content of an item tagged `#destiny/fleeting`
will ultimately be absorbed into another note
and the file deleted.
These notes may deviate from standard formatting.
### #destiny/permanent
Notes tagged `#destiny/permanent` are intended for long-term use.
They are expected to reflect standard formatting
and should be heavily tagged and linked.
## #status
`#status` reflects the remaining work necessary
to bring an item to the standard of its [[README#destiny]].
### #status/incomplete
Beyond intent, the note offers little to go on.
### #status/draft
The main content of the note is present, but:
* text may need to be reflowed
* links may need to be added
* citations may be necessary
### #status/complete
The text flows well,
the note is sufficiently tagged and linked,
and citations are included as appropriate
## #topic
Notes can and usually will have multiple topic tags.
### #topic/meta
Relating to the structure or intent of this notebook.
### #topic/software
Relating to specific software written by others,
or hypothetical software functionality I've conceived.
The latter I generally relegate to [[README#destiny/fleeting]],
to be absorbed into the specifications of the relevant project
when the idea is sufficiently developed.
### #topic/automation
On the subject of lightweight scripts
that could reduce redundancy in processes,
without requiring fundamental change.
### #topic/electrical
Relating to electrical installation,
including:
* code
* material
### #topic/estimating
Relating to the field of cost estimation,
as understood in [[construction-estimating]]
as well as other industries.
This topic also includes concepts that may be useful to estimation,
but that aren't widely understood to be.
### #topic/math
### #topic/risk
Relating to mathematical and abstract concepts of [[risk]].
### #topic/organization
On the subject of [[optimal-patterns]] for processes
of varying importance.
### #topic/other
Notes relating to subjects not relevant to this notebook's [[supertopics]],
but that I include for the convenience of editing them in Obsidian.
Some standouts include:
* [[birds|Birdwatching]]
* [[list|Warhammer 40,000]]
## #occupational
Items tagged `#occupational` include information and instructions
relevant to my current occupation
that may not reflect [[construction-estimating]] practice
in the wider industry.
> [!info]
> This tag is largely separate from the wider vault.
> I would probably move them to their own repository
> were it not for the complexity of preserving the version history of both.
### #occupational/systems
> [!important]
> Notes tagged `#occupational/systems/*` include information as understood by PDI,
> which is not necessarily consistent with (and often sharply deviates from)
> wider industry understanding.
## #type
### #type/idea
Items of `#type/idea` are recommendation
that I do something in the future,
possibly including some details of how to go about it.
They have the minimum amount of information
necessary to allow me to return to them.
They are always? of [[README#destiny/fleeting]].
### #type/guide
<!--TODO-->
### #type/encyclopedia
Items of `#type/encyclopedia` are thorough,
use exact language, and include citations.
They describe concepts as they are, not as they should be.
### #type/philosophy
Items of `#type/philosophy` are highly opinionated.
They describe concepts as I believe them to be.
They are always? of [[README#authorship/original]].
### #type/anecdote
<!--TODO-->
### #type/media-commentary
<!--TODO-->
## #authorship
`#authorship` reflects my claim to the content of an item
_in its current state_.
### #authorship/original
Items of `#authorship/original` are primarily my own work.
Content from other sources is properly cited.
### #authorship/other
> [!info]
> I'm unsatisfied with the name of this tag.
> It is subject to change.
Items of `#authorship/other` are not my own work.
They may be of one source a collection of several
without significant commentary.
+1 -1
View File
@@ -4,7 +4,7 @@ aliases: []
tags:
- type/media-commentary
---
# *The Failure of Risk Management*
# _The Failure of Risk Management_
The Failure of Risk Management
(Why It's Broken and How to Fix It)
+4 -1
View File
@@ -2,8 +2,11 @@
id:
aliases: []
tags:
- topic/meta
- authorship/original
- destiny/permanent
- status/incomplete
- topic/meta
- type/encyclopedia
---
# This Notebook
+3 -3
View File
@@ -1,7 +1,7 @@
---
id:
aliases: []
tags:
tags:
- topic/estimating
---
# Traditional Estimating Methods
@@ -22,7 +22,7 @@ Such methods lack the ability to intelligently express [[uncertainty]].
Traditional estimating methods, sometimes referred to as "Detailed Takeoff",
seek to detail all constituent subcosts,
including 100% itemized pricing by way of a *material extension*,
including 100% itemized pricing by way of a _material extension_,
a complete list of all material included in the price.
For clarity and contrast to [[risk-oriented-estimating]],
@@ -37,7 +37,7 @@ for little reward in overall **precision**.
> [!info] Pareto Principle
> The Pareto principle states that for many outcomes,
> roughly 80% of consequences come from 20% of causes.
>
>
> In the case of estimating efficiency, this means that optimal strategy
> is to focus on the 20% of estimating effort
> representing 80% of the overall efforts contribution to the total.