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

vault backup: 2026-06-04 16:59:32

Browse Source
This commit is contained in:
Zane Meyers
2026-06-04 16:59:32 -04:00
parent d127008fb1
commit 32e24aab08
32 changed files with 714 additions and 133 deletions
Download Patch File Download Diff File Expand all files Collapse all files
feeders-takeoff.md
+52 -20
View File
@@ -1,5 +1,5 @@
---
id: feeders
id:
aliases:
- feeders takeoff
title: Feeders Takeoff
@@ -16,12 +16,12 @@ up: "[[takeoff-scripts]]"
> including [[conest-wiring-method-selection]],
> before beginning takeoff.
## Execution
## Scope
1. Primaries
2. Secondaries
3. Feeders
4. Grounding
* Primaries
* Secondaries
* Feeders
* Grounding
### Formatting
@@ -46,38 +46,50 @@ For adjacent panels, use a minimum 10ft length.
#### Adders
Use the difference in elevation between equipment
Use the difference in elevation between equipment[^2]
or 10ft, whichever is greater.
Add an additional 5ft (total 15ft) for site runs
(primaries, secondaries, etc.).
[^2]: Not actually difference in elevation.
A site run from the bottom to the top of a hill may still only need 10ft.
This needs more precise wording.
It is not necessary to change this logic for site runs.[^3][^4]
[^3]: [[2026-06-03_14-05-39#Site Run Adders]]
[^4]: I will remove this line when I break the habit.
## Primaries
* `Area` = "2 - Site"
* `Phase` = "Site"
* `System` = "PRI - Primaries"
> [!info] Breakdowns
> * `Area` = "2 - Site"
> * `Phase` = "Site"
> * `System` = "PRI - Primaries"
Usually only empty conduit if included.
## Secondaries
* `Area` = "2 - Site"
* `Phase` = "Site"
* `System` = "SEC - Secondaries"
> [!info] Breakdowns
> * `Area` = "2 - Site"
> * `Phase` = "Site"
> * `System` = "SEC - Secondaries"
### Wiring on Vault Racks
Where secondary conductors run on racks in utility vaults
manually set the length of conduit,
measure the wire length,
add 20ft in addition to previously mentioned adders.
add 20ft in addition to previously mentioned adders.[^5]
[^5]: [[art-baldwin]] at some point, I think.
## Feeders
* `Area` = "01 - Feeders/Risers Building"
* `Phase` = "Feeders"
* `System` = "FRR - Feeders and Risers"
> [!info] Breakdowns
> * `Area` = "01 - Feeders/Risers Building"
> * `Phase` = "Feeders"
> * `System` = "FRR - Feeders and Risers"
> [!info] Garage Feeders
> `Area` "01 - Feeders/Risers Garage" is seldom used.
@@ -88,9 +100,25 @@ add 20ft in addition to previously mentioned adders.
`COMMON ASSEMBLIES`/`DISTRIBUTION`/`BUS DUCT`/...
Delete unnecessary items and change `Fct 1`
to get the correct quantities for the use case.
## Conductor Support
![[nfpa-70_300_general-requirements#300.19(A) Spacing Intervals --- Maximum.]]
In lieu of more stringent requirements
that may be imposed by project requirements,
minimum support for vertical conductors
is determined by [[nfpa-70_300_general-requirements#300.19(A) Spacing Intervals --- Maximum.|NEC 300.19(A)]]
Various [[heuristics]] exist among ConEst teams.
Assuming minimum 40ft spacing
(the absolute minimum for feeders we're likely to encounter)
for _all_ conductors is popular even among more detail-favoring seniors.
I generally prefer not to use a heuristic
because `takeoff-calcs.xlsm` trivializes accurate selection
and results in far fewer necessary supports.
Like [[#Sleeving]], it is acceptable to takeoff total counts
`ITEM DATABASE`/`CONDUIT & FITTINGS`/`CABLE SUPPORT / WEDGES`/`... COMPLETE FITTING`/...
@@ -101,3 +129,7 @@ See [[grounding-takeoff]].
## Sleeving
See [[sleeving-takeoff]].
Because feeders are not broken down by level
(they use `Area` = "01 - Feeders/Risers ...")
it is acceptable to use total counts.