ZaneMeyers/zmVault
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

vault backup: 2025-09-29 13:43:57

Browse Source
This commit is contained in:
Zane Meyers
2025-09-29 13:43:57 -04:00
parent 84d043c925
commit e33ee183ac
11 changed files with 183 additions and 146 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.obsidian/core-plugins.json
Vendored
+1 -1
View File
@@ -16,7 +16,7 @@
"slash-command": false,
"editor-status": true,
"bookmarks": true,
"markdown-importer": false,
"markdown-importer": true,
"zk-prefixer": false,
"random-note": false,
"outline": true,
.obsidian/hotkeys.json
Vendored
+9 -1
View File
@@ -33,5 +33,13 @@
"key": "ArrowDown"
}
],
"editor:toggle-checklist-status": []
"editor:toggle-checklist-status": [],
"obsidian-linter:lint-file": [
{
"modifiers": [
"Mod"
],
"key": "S"
}
]
}
.obsidian/plugins/recent-files-obsidian/data.json
Vendored
+116 -116
View File
@@ -1,20 +1,132 @@
{
"recentFiles": [
{
"basename": "full-takeoff",
"path": "full-takeoff.md"
"basename": "estimating-methodologies",
"path": "estimating-methodologies.md"
},
{
"basename": "estimating-ergonomics",
"path": "estimating-ergonomics.md"
},
{
"basename": "estimating-detail",
"path": "estimating-detail.md"
},
{
"basename": "estimating-culture",
"path": "estimating-culture.md"
},
{
"basename": "electrical-estimators-manual",
"path": "electrical-estimators-manual.md"
},
{
"basename": "electrical-estimating-methods",
"path": "electrical-estimating-methods.md"
},
{
"basename": "electrical",
"path": "electrical.md"
},
{
"basename": "distributed-antenna-systems",
"path": "distributed-antenna-systems.md"
},
{
"basename": "design-build-budget",
"path": "design-build-budget.md"
},
{
"basename": "breakdowns",
"path": "breakdowns.md"
},
{
"basename": "calibration-questions",
"path": "calibration-questions.md"
},
{
"basename": "construction-estimating",
"path": "construction-estimating.md"
},
{
"basename": "construction-estimating-using-excel",
"path": "construction-estimating-using-excel.md"
},
{
"basename": "automating-email",
"path": "automating-email.md"
},
{
"basename": "assembly-philosophy",
"path": "assembly-philosophy.md"
},
{
"basename": "assembly-objects",
"path": "assembly-objects.md"
},
{
"basename": "area-of-refuge",
"path": "area-of-refuge.md"
},
{
"basename": "ai-in-estimating",
"path": "ai-in-estimating.md"
},
{
"basename": "accubid-setup",
"path": "accubid-setup.md"
},
{
"basename": "2025-07-18_estimating-isnt-engineering",
"path": "2025-07-18_estimating-isnt-engineering.md"
},
{
"basename": "90-day-performance-review",
"path": "90-day-performance-review.md"
},
{
"basename": "3-phase-power",
"path": "3-phase-power.md"
},
{
"basename": "construction-estimating-software",
"path": "construction-estimating-software.md"
},
{
"basename": "estimating-as-code",
"path": "estimating-as-code.md"
},
{
"basename": "birds",
"path": "birds.md"
},
{
"basename": "favorite-quotes",
"path": "favorite-quotes.md"
},
{
"basename": "pre-takeoff-confirmation",
"path": "pre-takeoff-confirmation.md"
},
{
"basename": "burndy_AYP300",
"path": "Assets/subfeeds/burndy_AYP300.png"
},
{
"basename": "birds",
"path": "birds.md"
"basename": "location-vs-scope",
"path": "Excalidraw/location-vs-scope.md"
},
{
"basename": "standalone-systems",
"path": "standalone-systems.md"
},
{
"basename": "full-takeoff",
"path": "full-takeoff.md"
},
{
"basename": "feeders",
"path": "feeders.md"
},
{
"basename": "README",
@@ -24,30 +136,6 @@
"basename": "grounding",
"path": "grounding.md"
},
{
"basename": "feeders",
"path": "feeders.md"
},
{
"basename": "estimating-as-code",
"path": "estimating-as-code.md"
},
{
"basename": "construction-estimating-software",
"path": "construction-estimating-software.md"
},
{
"basename": "3-phase-power",
"path": "3-phase-power.md"
},
{
"basename": "90-day-performance-review",
"path": "90-day-performance-review.md"
},
{
"basename": "breakdowns",
"path": "breakdowns.md"
},
{
"basename": "functional-estimating",
"path": "functional-estimating.md"
@@ -76,18 +164,10 @@
"basename": "traditional-estimating-methods",
"path": "traditional-estimating-methods.md"
},
{
"basename": "standalone-systems",
"path": "standalone-systems.md"
},
{
"basename": "sleeving",
"path": "sleeving.md"
},
{
"basename": "estimating-methodologies",
"path": "estimating-methodologies.md"
},
{
"basename": "realism-vs-instrumentalism",
"path": "realism-vs-instrumentalism.md"
@@ -100,26 +180,10 @@
"basename": "automating-estimating-project-creation",
"path": "automating-estimating-project-creation.md"
},
{
"basename": "automating-email",
"path": "automating-email.md"
},
{
"basename": "assembly-philosophy",
"path": "assembly-philosophy.md"
},
{
"basename": "assembly-objects",
"path": "assembly-objects.md"
},
{
"basename": "breakdown-objects",
"path": "breakdown-objects.md"
},
{
"basename": "pre-takeoff-confirmation",
"path": "pre-takeoff-confirmation.md"
},
{
"basename": "subfeeds",
"path": "subfeeds.md"
@@ -128,10 +192,6 @@
"basename": "project-setup",
"path": "project-setup.md"
},
{
"basename": "2025-07-18_estimating-isnt-engineering",
"path": "2025-07-18_estimating-isnt-engineering.md"
},
{
"basename": "markdown-formatter-cli",
"path": "markdown-formatter-cli.md"
@@ -139,66 +199,6 @@
{
"basename": "separating-estimating-concerns",
"path": "separating-estimating-concerns.md"
},
{
"basename": "project-info",
"path": "project-info.md"
},
{
"basename": "pathfinding",
"path": "pathfinding.md"
},
{
"basename": "feeder-sizing",
"path": "feeder-sizing.md"
},
{
"basename": "estimating-ergonomics",
"path": "estimating-ergonomics.md"
},
{
"basename": "calibration-questions",
"path": "calibration-questions.md"
},
{
"basename": "bpm-award-analysis",
"path": "bpm-award-analysis.md"
},
{
"basename": "ai-in-estimating",
"path": "ai-in-estimating.md"
},
{
"basename": "misc-budgets",
"path": "misc-budgets.md"
},
{
"basename": "fire-alarm",
"path": "fire-alarm.md"
},
{
"basename": "distributed-antenna-systems",
"path": "distributed-antenna-systems.md"
},
{
"basename": "area-of-refuge",
"path": "area-of-refuge.md"
},
{
"basename": "lightning-protection",
"path": "lightning-protection.md"
},
{
"basename": "fixture-designations",
"path": "fixture-designations.md"
},
{
"basename": "fixtures",
"path": "fixtures.md"
},
{
"basename": "construction-estimating",
"path": "construction-estimating.md"
}
],
"omittedPaths": [],
birds.md
+7
View File
@@ -1,3 +1,10 @@
---
id:
aliases: []
tags:
- topic/other
- status/fleeting
---
# Birds I've Seen Around Here
## [Order _Pelecaniformes_](https://en.wikipedia.org/wiki/Pelecaniformes)
construction-estimating-software.md
+2
View File
@@ -1,4 +1,6 @@
---
id:
aliases: []
tags:
- topic/estimating
- topic/software
estimating-culture.md
+3 -2
View File
@@ -35,8 +35,9 @@ With intelligent work breakdown, jobs can be cleanly segmented for work in paral
Estimators working in the same room can be an invaluable resource
for brainstorming ideas and beneficial conversation.
It is the failure of [[estimating-culture]] and of [[construction-estimating-software]]
that so many estimators are wary of collaboration
It is the failure of [[estimating-culture]]
and of [[construction-estimating-software]]
that so many estimators are wary of collaboration.
The value of a second set of eyes can not be overstated.
estimating-detail.md
+5 -9
View File
@@ -6,28 +6,24 @@ tags:
---
# Estimating Detail
In [[construction-estimating]], the acceptable level of detail of an estimate is a contentious subject.
The acceptable level of detail of an [[construction-estimating|estimate]] is a contentious subject.
What's worse, estimators often disagree on what makes an estimate more detailed than another.
With our [[risk-oriented-estimating]] approach,
detail is essentially the inverse of epistemic [[uncertainty]].
That said, the correct answer is this.
The commonly repeated answer is this:
> As detailed as possible, given required turnaround and available estimating resources.
%%
TODO: This analysis is not much better than the common belief.
A commonality of both is the implication that more time ought to be preferred,
This analysis is flawed
because it implies more time ought to be preferred,
when the reality is that when considering larger organizational factors (strategy),
ideal estimate certainty is likely far lower than most expect.
The _correct_ correct answer involves optimizing for these factors:
* value of increased bid certainty
* value of increased estimate volume
%%
An estimate's detail is irrelevant to its quality.
A less detailed estimate is a more [[risk]]y bid,
A less detailed estimate is a more [[risk|risky]] bid,
but **it is not the role of the estimator to determine acceptable risk**.
## Experiment
favorite-quotes.md
+6
View File
@@ -1,3 +1,9 @@
---
id:
aliases: []
tags:
- status/fleeting
---
# Favorite Quotes
## About Tools
feeders.md
+21 -12
View File
@@ -21,10 +21,10 @@ may be routed through with special permission.
> STRUCTURAL SLAB IS AN 8-INCH THICK
> UNBONDED POST-TENSIONED TWO-WAY SLAB UNLESS NOTED OTHERWISE.
> [!cite] Joel Jansen 2025-08-15, in reference to Belle Meade Plaza, pp.
> [!cite] Joel Jansen 2025-08-15, in reference to Belle Meade Plaza (pp.)
> No affect on takeoff. Routing in slab still possible.
> [!cite] Joel Jansen 2025-08-21, in reference to Belle Meade Plaza, pp.
> [!cite] Joel Jansen 2025-08-21, in reference to Belle Meade Plaza (pp.)
> PT slabs do have some affect on takeoff.
> 3in conduit can not be run in an 11in PT slab.
@@ -34,15 +34,27 @@ may be routed through with special permission.
> STRUCTURAL SLAB IS 3 1/2 INCHES OF NORMALWEIGHT CONCRETE
> ON 3-INCH COMPOSITE STEEL DECK UNLESS NOTED OTHERWISE.
> [!cite] Joel Jansen 2025-08-15, in reference to Belle Meade Plaza, pp.
> [!cite] Joel Jansen 2025-08-15, in reference to Belle Meade Plaza (pp.)
> Do not route in slab.
#### Fire Rated Feeders
PDI estimating practice is to run all "emergency" feeds
(life-safety or just standby)
in a 2-hour rated assembly.
This usually requires no change to takeoff for high-rises
since electrical riser rooms are themselves fire-rated.
* RHW-2 insulated conductors in conduit -- "Lifeline Cable"
* 2-hour rated metal clad cable -- "Vitalink"
### Formatting
All feeder takeoff descriptions should be prefixed with `<parent> TO <child>`
> [!cite] Joel Jansen, in reference to Omni Hotels Raleigh, pp.
> It is acceptable to use typicals for identical feeders
> (i.e. meter centers fed from bus plugs)
> so long as the typical is in the Feeders `Area`.
## Sequence
@@ -50,23 +62,20 @@ All feeder takeoff descriptions should be prefixed with `<parent> TO <child>`
### 1. Estimate preparation
Read about the project specifications and construction type:
* Delivery Method (Plans & Specs, Design Build, Design Assist, Preliminary Budget)
* Deck thickness
* Wiring method
* Conductor material (Aluminum/Copper)
* Wiring methods
* Conductor material
* Wire terminations (set-screw acceptable or compression required?)
Locate:
* Riser Diagram
* Feeder Schedule (if present)
* Main Electrical rooms and panel locations
* Routing (if present)
### 2. Takeoff
* Choose a starting point on the riser
* Determine wire & Conduit makeup (3Ph/1Ph, AL/CU, Conduit)
* Measure off the length of the feed _ADDERS_
* Square corners, use corridors if possible
Run parallel to building lines
and route through corridors where possible.
> [!important]
> All takeoffs in Systems with names including "site"
@@ -84,7 +93,7 @@ Add an additional 5ft (total 15ft) for site runs
#### Primaries
Empty conduit.
Usually only empty conduit if included.
#### Secondaries
grounding.md
+5 -2
View File
@@ -11,14 +11,17 @@ tags:
This script is intended to cover both electrical and telecom grounding
in lieu of detail sufficient for standard takeoff (e.g. a grounding riser).
Note that the material provided in this system
is intended to be budgetary,
Note that the material provided in this system is intended to be budgetary,
not especially consistent with the actual install.
## Sequence
### 1. Estimate preparation
Locate:
* Main electric room (service entrance)
* Remote electric rooms
### 2. Takeoff
`COMMON ASSEMBLIES`/`GROUNDING`
pre-takeoff-confirmation.md
+5
View File
@@ -1,3 +1,8 @@
---
id:
aliases: []
tags: []
---
# Pre-Takeoff Confirmation
The purpose of the pre-takeoff confirmation