vault backup: 2026-02-27 16:50:56

2026-02-27 16:50:56 -05:00
parent b49b653833
commit 944192ae4c
3 changed files with 264 additions and 0 deletions
@@ -0,0 +1,121 @@
 ---
 id:
 aliases: []
 title: ConEst Pre-Takeoff Email Template
 tags:
  - authorship/other
  - destiny/permanent
  - occupational
  - type/media
 ---
 # ConEst Pre-Takeoff Email Template
 %%
 This template effectively replicates the official template,
 originally written in Microsoft Word.
 It's my belief that this template can not be implemented
 without significant modifications specific to the intended project.
 See implementations elsewhere in this notebook for reference.
 %%
 Hello Team,
 Below is a comprehensive list of means & methods for {Project Name}.
 Please confirm you have received this email and respond with any questions or comments.
 * **Delivery Method:** %% Plans & Specs, Design Build, Design Assist, P&S with Approved VE %%
 * **Document Stage:** %% DD, CD, Permit, GMP, Bid, Awarded %%
 * **Drawings Date:** %% Date %%
 * **Project Manual Date:** %% Date %%
 * **Proposal Date:** %% Date %%
 * **Takeoff Request Stage:** %% Stage 1, Full takeoff, etc. %%
 ### Project Specification Callouts
 %% Put page of Drawing or PM after answer %%
 * Conduit Execution Plans:
    %% GRC, coupling specs, etc. %%
 * Wire:
    %% Copper or Aluminum, Acceptable Manufacturers %%
 * Cable Uses:
    %% Branch Homeruns %%
 * Steel Box Depth:
    %% 1-1/2", 2-1/8" %%
 * Floor Boxes:
    * Box Material:
        %% Box: PVC, Sheet metal, Cast iron %%
    * Cover Material:
        %% Covers: Brass, Aluminum %%
 * Wiring Devices:
  * Units:
      %% 15A Decora %%
  * BOH/Common Areas:
      %% 20A Toggle %%
 * Switchboards/Panelboards:
    %% Acceptable Manufacturers, AL or CU Bussing, Breaker Types (Snap-on, bolt on), ACI Ratings %%
 * Transformers:
    %% Windings AL or CU, K-rating %%
 * Generator:
    %% Acceptable manufacturers, Enclosure Specs, Sound Rating, Remote Tank, Tank Size, Load Banks %%
 ### Project Drawing/Detail Callouts
 * Describe conflicts between drawings / proposal: %% Plans show CU feeders, proposal calls for aluminum, Specification grade devices, etc. %%
 * Cost drivers in details not shown elsewhere on plans:
 ### PDI System Execution Plan
 * Primaries:
    %% Installation only, (9) 6" PVC %%
 * Secondaries:
    %% PVC UG, GRC Stub-ups, AL %%
 * Feeders:
    %% PVC UG, EMT OH, AL over 100A, 2% VD %%
 * Unit Subfeeds:
    %% MC OH AL, VD per Chart on E5.01 %%
 * Units:
    %% 15A Decora, Insinkerators, T-stat, Floor Boxes, Shade Control, Doorbells, Dimmer Switches, etc. %%
 * Telecom:
    %% 42" MSDE, No Cable Homeruns, (1) 1" Back to IDF, CAT6 with Stub-ups %%
 * EV Chargers:
    %% 42) Conduit only, (56) Conduit & Wire, (20) Conduit, Wire & Equipment %%
 * Fire Alarm:
    %% Free-air where allowed by code. EMT Risers. %%
 * DAS:
    %% Conduit only, Per PDI DAS Design %%
 * Low Voltage:
    %% Free-air where allowed by code. Stub-ups to accessible ceilings. %%
 ### Lighting Control
 * Scope:
    %% Code Minimum per Energy Code Assigned, P&S, PDI Design %%
 * Area: %% Assign Method to Areas: Line Voltage, Low-Voltage Stand Alone or Centralized System %%
  * BOH:
  * Corridor:
  * Amenity:
  * Site/Landscape:
  * Garage Entry Point
  * Office:
 ### Tasks/Quotes Needed for WBS
 %% Delete any completed %%
 * Electrical Constructability Review
 * Electrical VDC
 * Coordination Study
 * DAS Public Safety Raceway Design
 <!--
 DAS Public Safety Raceway Design is necessary
 if we own DAS pathways but not the system,
 since if we own the system,
 the raceway design will be included in the Systems quote.
 -->
 Thank you,
@@ -16,6 +16,8 @@ yearly: "[[2026]]"
 ---
 # 2026-02-11 12:12:16
 %% Implementation of [[conest-pre-takeoff-email-template]] %%
 Hello Team,
 Below is a comprehensive list of means & methods for **1990 K Street**.
@@ -0,0 +1,141 @@
 ---
 id: 2026-02-27T13:58:30-05:00
 aliases: []
 title: "2026-02-27 13:58:30"
 tags:
  - authorship/original
  - destiny/permanent
  - status/draft
  - type/timestamped
 dg-publish: true
 date-created: 2026-02-27T13:58:30-05:00
 daily: "[[2026-02-27]]"
 weekly: "[[2026-W09]]"
 monthly: "[[2026-02]]"
 quarterly: "[[2026-Q1]]"
 yearly: "[[2026]]"
 ---
 # 2026-02-27 13:58:30
 ## Conversation Regarding ConEst Pre-Takeoff Email Template
 A conversation with a peer via Microsoft teams
 regarding [[pdi-estimating#Construction Estimating (ConEst)|ConEst]]'s
 recent implementation of a "pre-takeoff email template".
 [[conest-pre-takeoff-email-template]]
 ### Peer @ 13:42
 _A screenshot of the new Pre-Takeoff email template._
 _The fields "Breaker Types" and "AIC Ratings" are highlighted._
 At what point is it no longer spoon feeding
 and instead should be considered fully chewing and digesting?
 What is the purpose of such information?
 What does procurement do?
 What does operations do?
 I have no involvement whatsoever in the decision making
 of these very specific lines
 or how they are applied to the job;
 my takeoff is in no way affected or altered by this.
 Why, pray tell, the fuck,
 do I need to tell someone else this information?
 If I am expected to supply this information,
 should I not also check and cross reference quotes?
 I want to hear from the electrical contractor
 who has built a multi-family residence
 where bolt-on breakers were specified for unit panels,
 submitted, approved, ordered and installed,
 never being mentioned in a VE.
 ### Me @ 15:15
 I thought you'd have a fun time with some of those.
 At least you and I had seen the words before,
 imagine the rest of us.
 I've heard other estimators say it shouldn't be our job
 because it doesn't affect our takeoff,
 but I think that's misguided.
 It could be said that it's always been ConEst's purpose
 to check Bid's work _generally_, even outside of takeoff,
 only until now, the things we considered important enough to check
 have happened to line up with takeoff.
 They (whoever _They_ is) want Bid to handle more volume,
 which requires that Bid spend less time on a single estimate,
 which requires ConEst to pick up slack to maintain the same rigor.
 Regardless, it is totally reasonable to be upset
 that their was no training (or even warning) prior.
 ***
 >  If I am expected to supply this information,
 >  should I not also check and cross reference quotes?
 This is my gripe too.
 Let us check required manufacturers for wire and cable, sure,
 no one else could reasonably be expected to if not us or Bid,
 but Procurement has to check gear specs already,
 and ConEst doesn't have the experience necessary
 to make the redundancy cost-effective.
 My 100% baseless speculation is that ConEst has recently been blamed
 for losses (very easy to do:
 "ConEst was looking at these specs for two weeks
 and they didn't say anything")
 and rather than argue the point,
 our plan is to ensure that we have written record
 that we made Bid aware of significant issues.
 Poor plan in my opinion,
 since it's foolish to expect nothing will be missed,
 and we are _taking responsibility_ where we thought we had none before.
 ### Peer @ 15:36
 Poor plan indeed. 
 From the perspective of someone under a Senior
 who, after the initial meetings regarding this template,
 stated it was "about some email shit"
 I see this as poorly implemented.
 I believe some basic and general education
 about each line should be put into place,
 to help those of us that are unfamiliar with these things.
 For example, the original template states
 'Generator: Acceptable manuf., enclosure specs,
 sound rating, remote tank & size, load banks.'
 My issue is with the vagueness of 'load banks.'
 Not the only instance, but quite annoying
 as some may not have any idea what a load bank is,
 how it is incorporated into a system, or, most importantly,
 what information the template is asking of you.
 > They (whoever _They_ is) want Bid to handle more volume,
 > which requires that Bid spend less time on a single estimate,
 > which requires ConEst to pick up slack to maintain the same rigor.
 Where does this come from?
 ### Me @ 15:53
 More baseless speculation.
 I'm assuming that there's a legitimate reason
 to pass this responsibility to ConEst,
 rather than just the natural preference for least effort.
 My experience was the same as yours,
 what I sent was quite different from the template.
 It had to be for the job I used it for,
 but I don't expect most will be easier.
 I'll forward you it, but the source
 (the cooler version) is at
 "zmVault/timestamped/2026-02-11_12-12-16.md"
 Bid reacted exactly how I said they would,
 that it was way too much information.