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

vault backup: 2025-09-08 16:28:40

Browse Source
This commit is contained in:
Zane Meyers
2025-09-08 16:28:40 -04:00
parent c69536555b
commit 7f42178876
9 changed files with 244 additions and 199 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.obsidian/graph.json
Vendored
+1 -1
View File
@@ -8,7 +8,7 @@
"collapse-color-groups": false,
"colorGroups": [
{
"query": "tag:#meta",
"query": "tag:#topic/meta",
"color": {
"a": 1,
"rgb": 14725458
.obsidian/plugins/recent-files-obsidian/data.json
Vendored
+132 -120
View File
@@ -1,5 +1,25 @@
{
"recentFiles": [
{
"basename": "feeders",
"path": "feeders.md"
},
{
"basename": "full-takeoff",
"path": "full-takeoff.md"
},
{
"basename": "misc-budgets",
"path": "misc-budgets.md"
},
{
"basename": "standalone-systems",
"path": "standalone-systems.md"
},
{
"basename": "lightning-protection",
"path": "lightning-protection.md"
},
{
"basename": "fixture-designations",
"path": "fixture-designations.md"
@@ -9,17 +29,125 @@
"path": "fixtures.md"
},
{
"basename": "full-takeoff",
"path": "full-takeoff.md"
"basename": "construction-estimating",
"path": "construction-estimating.md"
},
{
"basename": "90-day-performance-review",
"path": "90-day-performance-review.md"
"basename": "construction-estimating-using-excel",
"path": "construction-estimating-using-excel.md"
},
{
"basename": "design-build-budget",
"path": "design-build-budget.md"
},
{
"basename": "distributed-antenna-systems",
"path": "distributed-antenna-systems.md"
},
{
"basename": "electrical",
"path": "electrical.md"
},
{
"basename": "electrical-estimating-methods",
"path": "electrical-estimating-methods.md"
},
{
"basename": "electrical-estimators-manual",
"path": "electrical-estimators-manual.md"
},
{
"basename": "estimating-as-code",
"path": "estimating-as-code.md"
},
{
"basename": "excel-macros",
"path": "excel-macros.md"
},
{
"basename": "estimator-skills",
"path": "estimator-skills.md"
},
{
"basename": "estimating-philosophy",
"path": "estimating-philosophy.md"
},
{
"basename": "grounding",
"path": "grounding.md"
},
{
"basename": "material-pricing",
"path": "material-pricing.md"
},
{
"basename": "me",
"path": "me.md"
},
{
"basename": "project-info",
"path": "project-info.md"
},
{
"basename": "project-management-tm",
"path": "project-management-tm.md"
},
{
"basename": "project-setup",
"path": "project-setup.md"
},
{
"basename": "psn-distribution-list",
"path": "psn-distribution-list.md"
},
{
"basename": "raceway-terms",
"path": "raceway-terms.md"
},
{
"basename": "README",
"path": "README.md"
},
{
"basename": "requirement-precedence",
"path": "requirement-precedence.md"
},
{
"basename": "gold-plating",
"path": "gold-plating.md"
},
{
"basename": "systems",
"path": "systems.md"
},
{
"basename": "supertopics",
"path": "supertopics.md"
},
{
"basename": "switchgear",
"path": "switchgear.md"
},
{
"basename": "telecom",
"path": "telecom.md"
},
{
"basename": "the-failure-of-risk-management",
"path": "the-failure-of-risk-management.md"
},
{
"basename": "this-notebook",
"path": "this-notebook.md"
},
{
"basename": "monte-carlo-methods",
"path": "monte-carlo-methods.md"
},
{
"basename": "90-day-performance-review",
"path": "90-day-performance-review.md"
},
{
"basename": "lighting-controls",
"path": "lighting-controls.md"
@@ -36,10 +164,6 @@
"basename": "burndy_AYP300",
"path": "Assets/subfeeds/burndy_AYP300.png"
},
{
"basename": "README",
"path": "README.md"
},
{
"basename": "list",
"path": "list.md"
@@ -60,10 +184,6 @@
"basename": "getting-historical-pricing",
"path": "getting-historical-pricing.md"
},
{
"basename": "telecom",
"path": "telecom.md"
},
{
"basename": "pathfinding",
"path": "pathfinding.md"
@@ -76,117 +196,9 @@
"basename": "ai-in-estimating",
"path": "ai-in-estimating.md"
},
{
"basename": "psn-distribution-list",
"path": "psn-distribution-list.md"
},
{
"basename": "feeders",
"path": "feeders.md"
},
{
"basename": "units",
"path": "units.md"
},
{
"basename": "feeder-sizing",
"path": "feeder-sizing.md"
},
{
"basename": "subfeeds",
"path": "subfeeds.md"
},
{
"basename": "systems",
"path": "systems.md"
},
{
"basename": "breakdowns",
"path": "breakdowns.md"
},
{
"basename": "bpm-award-analysis",
"path": "bpm-award-analysis.md"
},
{
"basename": "automating-email",
"path": "automating-email.md"
},
{
"basename": "accubid-setup",
"path": "accubid-setup.md"
},
{
"basename": "area-of-refuge",
"path": "area-of-refuge.md"
},
{
"basename": "material-pricing",
"path": "material-pricing.md"
},
{
"basename": "switchgear",
"path": "switchgear.md"
},
{
"basename": "open-problems-in-estimating",
"path": "open-problems-in-estimating.md"
},
{
"basename": "portable-tools",
"path": "portable-tools.md"
},
{
"basename": "low-voltage",
"path": "low-voltage.md"
},
{
"basename": "misc-budgets",
"path": "misc-budgets.md"
},
{
"basename": "estimator-skills",
"path": "estimator-skills.md"
},
{
"basename": "project-setup",
"path": "project-setup.md"
},
{
"basename": "assembly-philosophy",
"path": "assembly-philosophy.md"
},
{
"basename": "2025-07-18_estimating-isnt-engineering",
"path": "2025-07-18_estimating-isnt-engineering.md"
},
{
"basename": "mike-holts-illustrated-guide-to-electrical-estimating",
"path": "mike-holts-illustrated-guide-to-electrical-estimating.md"
},
{
"basename": "monte-carlo-methods",
"path": "monte-carlo-methods.md"
},
{
"basename": "new-hire",
"path": "new-hire.md"
},
{
"basename": "requirement-precedence",
"path": "requirement-precedence.md"
},
{
"basename": "raceway-terms",
"path": "raceway-terms.md"
},
{
"basename": "nfpa70_314.028_pull-and-junction-boxes",
"path": "nfpa70_314.028_pull-and-junction-boxes.md"
},
{
"basename": "separating-estimating-concerns",
"path": "separating-estimating-concerns.md"
}
],
"omittedPaths": [],
estimator-skills.md
+6 -2
View File
@@ -2,6 +2,7 @@
id:
aliases: []
tags:
- occupational
- type/media
---
## Create a WBS
@@ -66,7 +67,8 @@ Once received, validation no longer required
* Create Accubid file in proper location and format
* Create LiveCount folder in proper location and format
* Enter WBS area breakout and Unit Matrix into Accubid
* Upload contracted plans per scope of work to LiveCount and tie to Accubid using standard bookmark instructions
* Upload contracted plans per scope of work to LiveCount
and tie to Accubid using standard bookmark instructions
### Grading Scale
@@ -122,7 +124,9 @@ Once received, validation no longer required
### Requirements
* Review reflected ceiling plans and compare/cross reference architectural, electrical, interior design, and landscape plans to identify all fixtures and their proper mounting requirements and length per fixture.
* Review reflected ceiling plans and compare/cross reference
architectural, electrical, interior design, and landscape plans
to identify all fixtures and their proper mounting requirements and length per fixture.
Fixture schedule may be required to consult for mounting requirements.
* Build fixture assembly and assign to proper Accubid task
fixture-designations.md
+32 -34
View File
@@ -37,27 +37,28 @@ Use empty designations to separate phases.
## Fixture Labor
| Fixture Type | Labor |
| ------------ | -------------- |
| Paddle Fan | 1.5 hrs/ea |
| Pendant | 1-4 hrs/ea[^1] |
| Strip/Cove | 0.083 hrs/ft |
| Site Poles | 1.5 hrs/ea |
| Festoon | 2 hrs/ea |
| All Others | 1 hrs/ea |
| Fixture Type | Labor |
| ------------ | ------------ |
| Paddle Fan | 1.5 hrs/ea |
| Pendant | 1-4 hrs/ea |
| Strip/Cove | 0.083 hrs/ft |
| Site Poles | 1.5 hrs/ea |
| Festoon | 2 hrs/ea |
| All Others | 1 hrs/ea |
## Fixture Branch Length
| Case | Standard Length |
| ------------- | --------------- |
| Site/Courtyard | 50ft[^1] |
| Garage | 50ft |
| BOH | 40ft |
| Corridors | 40ft |
| Interior Amenity | 40ft[^2] |
| Office/Retail | 50ft |
| Exterior Amenity | 50ft |
| Units | 20ft |
| Case | Standard Length |
| --------------------- | --------------- |
| Site/Courtyard | 50ft |
| Garage | 50ft |
| BOH | 40ft |
| Corridors | 40ft |
| Interior Amenity | 40ft |
| Office/Retail | 50ft |
| Exterior Amenity | 50ft |
| Units | 20ft |
| Undercabinet Fixtures | 10ft |
## Fixture Branch Wire size
@@ -172,8 +173,6 @@ round up to the nearest 5ft
> [!note]
> Takeoff 2 fixtures if jumping over oven
Use 10ft \#12/2 for MC & NM
## Paddle Fans
| Wiring Method | Assembly Path |
@@ -207,11 +206,6 @@ Create its own breakout in WBS, and phase in Accubid
> [!quote]
> This is not technically exposed or drop ceiling, but still use PVC
## FAA Lighting
> 1. `FIXTURE LABOR`/`FIXTURE LABOR 1HR`
> 2. `FESTOON & ROOF ASSEMBLIES`/`Aircraft Warning, 3/4" Conduit GRC/PVC 2#10, 1#10G`
## Site & Courtyard
### Breakdowns
@@ -220,17 +214,16 @@ Create its own breakout in WBS, and phase in Accubid
### Fixture Assemblies
| Fixture Type | Assembly Path |
| ------------------------------------ | -------------------------------------------------------------------------------- |
| Step Light | `COURTYARDS & LANDSCAPE`/`STEP FIX, 3/4" CONDUIT - PVC40 - ...` |
| 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 - ...` |
| Handrail light | `COURTYARDS & LANDSCAPE`/`ALUM BOX W/ FLEX FIX, 3/4" CONDUIT - PVC40 - ...`[^2] |
| Fixture Type | Assembly Path |
| ------------------------------------ | --------------------------------------------------------------------------------------- |
| Step Light | `COURTYARDS & LANDSCAPE`/`STEP FIX, 3/4" CONDUIT - PVC40 - ...` |
| 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 - ...` |
| 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
[^2]: Per Corwin: Hand rail lights should have a rigid 90 stub up and some flex
### Festoon Lighting
@@ -241,3 +234,8 @@ Create its own breakout in WBS, and phase in Accubid
> * `Length per Unit` = Light string length
> 3. `COURTYARDS & LANDSCAPE`/`ALUM BOX W/ FLEX FIX, 3/4" CONDUIT - PVC40 - ...`
> * `Length per Unit` = Distance to panel + 15ft
## FAA Lighting
> 1. `FIXTURE LABOR`/`FIXTURE LABOR 1HR`
> 2. `FESTOON & ROOF ASSEMBLIES`/`Aircraft Warning, 3/4" Conduit GRC/PVC 2#10, 1#10G`
gold-plating.md
+11 -11
View File
@@ -12,14 +12,14 @@ of arbitrarily requiring components or methods far more stringent than typical.
In [[construction-estimating]],
such cases quickly reveal every error of assumption made by the estimator.
## Example: Aluminum Feeders ILO Copper
The typical value engineering option for electrical installations
is to use aluminum wiring in lieu of copper above a certain size.
Assuming competent installation, such an option is strictly functionally equal to the design.
There is _no_ difference to capacity, future expansion, or long-term maintenance.
Moreover, the substitution is invisible to the client,
such that they would have to employ an electrician
to determine whether it had been taken.
Despite this, copper wiring is still a common specification default
because clients care about that sort of thing for some reason.
> [!example] Aluminum Feeders ILO Copper
> The typical value engineering option for electrical installations
> is to use aluminum wiring in lieu of copper above a certain size.
> Assuming competent installation,
> such an option is strictly functionally equal to the design.
> There is _no_ difference to capacity, future expansion, or long-term maintenance.
> Moreover, the substitution is invisible to the client,
> such that they would have to employ an electrician
> to determine whether it had been taken.
> Despite this, copper wiring is still a common specification default
> because clients care about that sort of thing for some reason.
lightning-protection.md
+1 -4
View File
@@ -8,10 +8,7 @@ tags:
## Info
Two Types:
* Protection \$\$\$
* Prevention \$
* ESE (EARLY STREAMER EMISSIONS)
### Early Streamer Emission (ESE)
## Estimate Scope
misc-budgets.md
+22 -8
View File
@@ -8,7 +8,11 @@ tags:
## Slab Deck
* `System` = "Electrical"
```
Drawing = "N/A"
Area = "Typical - ..."
System = "EL - Electrical"
```
Create `area` Typicals for every concrete slab floor:
@@ -16,9 +20,17 @@ Create `area` Typicals for every concrete slab floor:
* 1 each level except roof
* **HD:** 1 per Section
```
Phase = "Building - BOH, Storage & Common"
```
* 'All Garage'
* 1 each level
```
Phase = "Garage"
```
In each Typical:
* Takeoff: `ITEM DATABASE`/`MISC PDI PRODUCT`/`MISC MATERIAL - SLAB/DECK & FEEDER`/`MISC MATERIAL - SLAB/DECK (NAILS, PAINT, TAPE, ETC = $250)`
@@ -47,20 +59,21 @@ System = "TPD - Temp Power Distribution (Gag. & Bldg.)"
BidItem = "3 - Building"
```
* Takeoff: `ITEM DATABASE`/`TEMPORARY POWER`/`* - TEMPORARY LIGHTING / PWR PNL (PER BLDG AREA SFT)`
* _Count_ = Building GSF = Total GSF - Garage GSF
Garden Styles:
* Takeoff: `ITEM DATABASE`/`TEMPORARY POWER`/`TEMPORARY POWER - T POLE (EACH)`
* _Count_ = 1 per 150ft per building
All others:
* Takeoff: `ITEM DATABASE`/`TEMPORARY POWER`/`* - TEMPORARY LIGHTING / PWR PNL (PER BLDG AREA SFT)`
* _Count_ = Building GSF = Total GSF - Garage GSF
### Temp Lighting (Garage)
```
Area = "01 - Temp Power Distribution Building"
Area = "01 - Temp Power Distribution Garage"
Phase = "Temp Power"
System = "TPD - Temp Power Distribution (Gag. & Bldg.)"
BidItem = "3 - Building"
BidItem = "2 - Garage"
```
* Takeoff: `ITEM DATABASE`/`TEMPORARY POWER`/`* - TEMPORARY LIGHTING / PWR PNL (PER BLDG AREA SFT)`
@@ -75,5 +88,6 @@ System = "MISC - Site Miscellaneous"
BidItem = "1 - Site"
```
* (3) 3Phase 30A 200' Mech. Con. EMT Carflex
* Append to name: "Irrigation Pump - "
Takeoff: `COMMON ASSEMBLIES`/`MECHANICAL CONNECTIONS (UP TO 100A)`/`PVC - LT NM FLEX (CARFLEX)`/`30A 3PH MECH CONN (200') 3/4" PVC 4#10 - CARFLEX`
* _Count_ = 3
* Append to name: "Irrigation Pump - "
psn-distribution-list.md
+1 -1
View File
@@ -8,7 +8,7 @@ tags:
| Region | Subregion | Title | Name |
| ------------ | --------- | ----------------- | --------------------------------------------- |
| All | | ITR Team | Liz De Erbiti , ITR Operations |
| All | | ITR Team | Liz De Erbiti, ITR Operations |
| All | | PCO Team | Joel Liz Pereira, Sarah Brown, Lani Schneider |
| Carolinas | | Commodities Buyer | Canyon Murphy |
| Carolinas | | Procurement PX | Conner Kuehn |
raceway-terms.md
+38 -18
View File
@@ -24,7 +24,7 @@ tags:
> [!info] Duct Bank
> "Duct bank" is not given explicit definition in the NEC,
> however it is used frequently to refer to any group of ducts,
> however it is used frequently to refer to any group of **ducts**,
> _even as few as one_, as shown in Figure 310.60(C)(3).
> It is always spelled as two words.
@@ -33,9 +33,11 @@ tags:
"Wiring method" is not given explicit definition in the NEC.
> [!quote] NEC 110.8 Wiring Methods
> Only wiring methods recognized as suitable are included in this Code.
> Only wiring methods recognized as suitable
> are included in this Code.
> The recognized methods of wiring
> shall be permitted to be installed in any type of building or occupancy,
> shall be permitted to be installed
> in any type of building or occupancy,
> except as otherwise provided in this Code.
> [!quote] NEC 300.1(A) All Wiring Installations
@@ -44,8 +46,10 @@ tags:
> for all _wiring installations_ (emphasis added)
> unless modified by other articles in Chapter 3.
Nor is wiring installation, however by closest definition
it can be assumed premises wiring includes all wiring installations.
Nor is wiring installation,
however by closest definition
it can be assumed **premises wiring**
includes all wiring installations.
> [!quote] NEC Article 100
> **Premises Wiring (System).**
@@ -55,34 +59,50 @@ it can be assumed premises wiring includes all wiring installations.
> both permanently and temporarily installed.
> This includes
> (a) wiring from the service point or power source to the outlets or
> (b) wiring from and including the power source to the outlets where there is no service point.
> (b) wiring from and including the power source
> to the outlets where there is no service point.
Notably, Chapter 3 does not prescribe requirements for _raceway_, but for _wiring installations_.
As such, conduit used for other purposes (e.g. routing beverage tubing) is out of scope.
### Inappropriate Use
Raceways used for supporting communications cables _would be_ out of scope,
except for Article 800.110:
Notably, Chapter 3 does not prescribe requirements for _raceway_,
but for _wiring installations_.
As such, conduit used for other purposes
(e.g. routing beverage tubing) is out of scope.
Raceways used for supporting communications cables
_would be_ out of scope, except for Article 800.110:
> [!quote] NEC 800.110(A)(1) Raceways Recognized in Chapter 3
> Communications wires and cables shall be permitted
> to be installed in any raceway included in Chapter 3.
> The raceways shall be installed in accordance
> with the requirements of Chapter 3.
> _The raceways shall be installed in accordance_
> _with the requirements of Chapter 3._
Raceway is not a wiring method unless it is used to support premises wiring,
Raceway is not a _wiring method_
unless it is used to support _premises wiring_,
which communications cabling is not.
It is not appropriate to say "EMT conduit is a wiring method"
(granted the NEC does use this syntax occasionally),
because a recognized wiring method must include
the wiring, splices, pull boxes, outlet boxes, and supports
It is not appropriate to say "EMT conduit is _a_ wiring method"
(granted the NEC does use similar phrasing occasionally),
because any recognized wiring method must include the
* wiring,
* splices,
* pull boxes,
* outlet boxes,
* and supports
necessary of a complete wiring installation,
each of which has countless options.
It may be appropriate to refer to "MC cable" as a wiring method
### Appropriate Use
It may be appropriate to refer to "MC cable" as _a_ wiring method
if you and your audience understand the name as shorthand
for a more specific, standard framework.
In a robustly implemented specification-based takeoff software,
an assembly's specifications would describe it's wiring methods.
A 20A and 30A branch circuit may utilize identical "wiring methods".
## Takeaways
No part of a manufactured cable assembly (e.g. MC cable)