Merge branch 'main' of https://github.com/ZaneMeyers/zmVault
This commit is contained in:
@@ -0,0 +1,34 @@
|
||||
---
|
||||
id: 2026-04-22T11:50:05-0400
|
||||
title: 2026-04-22 11:50:05
|
||||
tags: []
|
||||
daily: "[[2026-04-22]]"
|
||||
---
|
||||
# 2026-04-22 11:50:05
|
||||
|
||||
## Recursive Typicals
|
||||
|
||||
A competent quantity takeoff software must support **recursive typicals**.
|
||||
|
||||
> "Building Type A" has Levels
|
||||
> * Level 01,
|
||||
> * Level 02,
|
||||
> * Level 03,
|
||||
> * Level 04,
|
||||
> * Level 05
|
||||
>
|
||||
> "Building Type A Levels 02-04" is typical of
|
||||
> * "Building Type A/Level 02",
|
||||
> * "Building Type A/Level 03",
|
||||
> * "Building Type A/Level 04"
|
||||
>
|
||||
> "Building Type A" is typical of
|
||||
> * "Building 1",
|
||||
> * "Building 2",
|
||||
> * "Building 3"
|
||||
|
||||
In all cases, a typical must behave as the **Type** it is typical of,
|
||||
(i.e. the process to assign takeoff to "Levels 02-10"
|
||||
must be essentially the same as to do so to "Level 01")
|
||||
and the use of a typical must not exclude the use of the breakdowns it is typical of
|
||||
(i.e. the use of "Levels 02-10" must not exclude the use of "Level 02").
|
||||
@@ -0,0 +1,18 @@
|
||||
---
|
||||
id: 2026-04-22T13:41:20-0400
|
||||
title: 2026-04-22 13:41:20
|
||||
tags:
|
||||
- occupational
|
||||
daily: "[[2026-04-22]]"
|
||||
---
|
||||
# 2026-04-22 13:41:20
|
||||
|
||||
## Trust the Process
|
||||
|
||||
Separate UG, OH, and Flex Feeder assemblies
|
||||
add extra terminations, wire, and conduit fittings
|
||||
that will not be necessary for installation.
|
||||
|
||||
Mech Connection assemblies
|
||||
do not include disconnects
|
||||
nor labor to install them.
|
||||
@@ -0,0 +1,100 @@
|
||||
---
|
||||
id: 2026-04-23T10:01:40-0400
|
||||
title: 2026-04-23 10:01:40
|
||||
tags: []
|
||||
daily: "[[2026-04-23]]"
|
||||
---
|
||||
# 2026-04-23 10:01:40
|
||||
|
||||
## Virginia Live! Director Review
|
||||
|
||||
[[estimating-director-review]] for
|
||||
[[virginia-live-casino-and-hotel]]:
|
||||
|
||||
## Switchgear
|
||||
|
||||
Note extensive emergency power provisions
|
||||
verify control wiring for generator to ATS
|
||||
#### Lighting HR's
|
||||
|
||||
count of circuits, control zones in takeoff notes
|
||||
lot length
|
||||
|
||||
#### Temporary Power
|
||||
|
||||
Used two `TEMPORARY POWER - HR`
|
||||
|
||||
Narrative
|
||||
extended light layouts
|
||||
|
||||
#### Generator
|
||||
|
||||
3000 gallons * 6 dollars per gallon = $18000
|
||||
|
||||
#### Labor
|
||||
|
||||
ASL Column 2 with adjustments
|
||||
|
||||
Site Labor +50%
|
||||
#### Telecom Backbone
|
||||
|
||||
#### Medium Voltage
|
||||
|
||||
Medium voltage cabling downstream of
|
||||
|
||||
#### Underground Runs
|
||||
|
||||
need rigid 90's for PVC runs 200ft and above
|
||||
> horizontal? vertical? both?
|
||||
|
||||
#### Fixture Labor
|
||||
|
||||
Tape light: 1 hour per 6 feet
|
||||
|
||||
snap together linear: 1 hour per 5 feet
|
||||
|
||||
##### Center Bar Fixture
|
||||
|
||||
assuming each crystal is an individual fixture
|
||||
over 5000 crystals
|
||||
80 circuits
|
||||
|
||||
A-GAM-442
|
||||
##### Dragon Fixture
|
||||
|
||||
1000 hours
|
||||
|
||||
#### Lighting Control
|
||||
|
||||
"Networked" to mean either
|
||||
"Centralized"
|
||||
or "Standalone" with Network Bridges.
|
||||
|
||||
> Wattstopper Network Bridges are limited to 64 devices (zones)
|
||||
|
||||
#### DAS
|
||||
|
||||
Sold Design Build
|
||||
#### Historicals
|
||||
|
||||
Want to know
|
||||
casino cost per square foot
|
||||
|
||||
#### Composite Cleanup
|
||||
|
||||
#### Multi-Shift Impact
|
||||
|
||||
20% of hours
|
||||
add $5 per hour
|
||||
|
||||
#### Indirect Labor
|
||||
|
||||
16% burden
|
||||
|
||||
#### Facade
|
||||
|
||||
Extra cost for facade lighting install
|
||||
250,000
|
||||
|
||||
"Go to 150k"
|
||||
|
||||
@@ -0,0 +1,14 @@
|
||||
---
|
||||
id: 2026-04-23T14:36:51-0400
|
||||
title: 2026-04-23 14:36:51
|
||||
tags: []
|
||||
daily: "[[2026-04-23]]"
|
||||
---
|
||||
# 2026-04-23 14:36:51
|
||||
|
||||
Need to refresh myself on
|
||||
[[nfpa-70_311_mv-conductors]]
|
||||
|
||||
Note that 2023 moved MV content to
|
||||
Article 314 Part 3
|
||||
and Article 315
|
||||
@@ -0,0 +1,19 @@
|
||||
---
|
||||
id: 2026-04-23T16:24:49-0400
|
||||
title: 2026-04-23 16:24:49
|
||||
tags:
|
||||
- occupational
|
||||
daily: "[[2026-04-23]]"
|
||||
---
|
||||
# 2026-04-23 16:24:49
|
||||
|
||||
I asked a former [[pdi-operations#Project Manager|PM]]
|
||||
what purpose [[conest|ConEst]] serves
|
||||
if [[pdi-operations|Ops]] is doing the same takeoff.
|
||||
He said I was mistaken,
|
||||
that Ops modifies the ConEst estimate,
|
||||
they don't redo it.
|
||||
|
||||
When Ops receives the [[pdi-vdc|VDC]] Feeder Verification Sheet
|
||||
(which is based on our own [[pdi-project-start-notification#Feeder Verification]])
|
||||
they change our takeoff to match.
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
id: 2026-04-23T17:41:32-0400
|
||||
title: 2026-04-23 17:41:32
|
||||
tags: []
|
||||
daily: "[[2026-04-23]]"
|
||||
---
|
||||
# 2026-04-23 17:41:32
|
||||
|
||||
## Professional Certifications
|
||||
|
||||
* Project Management Professional (PMP)
|
||||
* Certified Quality Engineer (CQE)
|
||||
* Lean Six Sigma Black Belt (LSBB)
|
||||
Reference in New Issue
Block a user