vault backup: 2026-04-28 16:30:30

2026-04-28 16:30:30 -04:00
parent ce087f8880
commit 16cf1e3393
85 changed files with 196 additions and 117 deletions
@@ -39,7 +39,7 @@ Started ~13:45

 6. Create TrimbleConnect project

-7. Create Accubid Job
+7. Create [[accubid|Accubid]] Job
    * Paste Areas

 8. Unit Matrix
@@ -1,7 +1,6 @@
 ---
 title: "13723 Feather Sound Circle East #210"
-tags:
-  - occupational
+tags: []
 ---
 # 13723 Feather Sound Circle East #210

@@ -17,10 +17,10 @@ tags:

 ## Syntax

-I primarily use [[obsidian|Obsidian]] for both reading and writing,
+[[me|I]] primarily use [[obsidian|Obsidian]] for both reading and writing,
 so notes are written in [Obsidian-flavored markdown](https://help.obsidian.md/),
-which is partially reimplemented by
-[Foam](https://foamnotes.com/) for Visual Studio Code
+which is partially reimplemented
+by [Foam](https://foamnotes.com/) for Visual Studio Code
 and [Markdown Oxide](https://oxide.md/) for vim, neovim, and others.

 For compatibility,
@@ -4,6 +4,7 @@ tags:
  - occupational
  - type/guide
 title: Accubid Setup
+up: "[[pdi-estimating]]"
 ---
 # Accubid Setup

@@ -11,7 +12,7 @@ title: Accubid Setup

 ### Automation

-It is likely infeasible to automate LiveCount and Accubid project creation.
+It is likely infeasible to automate LiveCount and [[accubid|Accubid]] project creation.
 However, a script could launch the apps with a procedure,
 setting the clipboard.

@@ -8,7 +8,7 @@ tags:
 ---
 # AI in Estimating

-Most estimators are already pigeon-holed into poor SaaS like Accubid and the rest already,
+Most estimators are already pigeon-holed into poor SaaS like [[accubid|Accubid]] and the rest already,
 but the need to increase efficiency with AI will be the nail in the coffin.
 The myth that "full package" estimating software is most efficient
 will only be exacerbated by the inclusion of AI features
@@ -5,6 +5,7 @@ tags:
  - topic/automation
  - type/idea
 title: BPM Award Analysis
+up: "[[pdi-estimating]]"
 ---
 # BPM Award Analysis

@@ -0,0 +1,10 @@
+---
+title: Christian Pereiro
+tags:
+  - occupational
+  - type/person
+up: "[[pdi-bid-estimating]]"
+---
+# Christian Pereiro
+
+preconstruction manager (chief estimator) for [[pdi-bid-estimating]]
@@ -4,6 +4,7 @@ tags:
  - authorship/other
  - occupational
  - type/media
+up: "[[pdi-pre-takeoff-confirmation]]"
 ---
 # ConEst Pre-Takeoff Email Template

@@ -5,4 +5,4 @@ tags:
 ---
 # ConEst Projects

-Link target for [[conest]] projects.
+Link target for [[conest|ConEst]] projects.
@@ -1,9 +1,12 @@
 ---
+aliases:
+  - ConEst
 title: PDI Construction Estimating (ConEst)
 tags:
  - occupational
  - topic/estimating
  - type/encyclopedia-entry
+up: "[[power-design-inc]]"
 ---
 # PDI Construction Estimating (ConEst)

@@ -4,5 +4,6 @@ tags:
  - occupational
  - status/not-started
  - type/person
+up: "[[pdi-estimating]]"
 ---
 # Corwin Fluit
@@ -65,7 +65,7 @@ Weatherhead for antenna. One per building.

 > [!important]
 > Usually only for cellular DAS.
-> Confirm takeoff requirement with [[pdi-estimating#Bid Estimating|Bid]].
+> Confirm takeoff requirement with [[pdi-bid-estimating|Bid]].

 1. .../`CORRIDORS ...`
    * **Length** = Length measured for every corridor/garage
@@ -45,7 +45,7 @@ Once received, validation no longer required
 * Compare/cross reference architectural and electrical plans
  to determine correct unit naming, count, location, and layout
 * Create unit matrix excel document
-* Enter information into Accubid and cBOM accurately
+* Enter information into [[accubid|Accubid]] and cBOM accurately

 ### Grading Scale

@@ -228,7 +228,7 @@ Length and Labor will be more than a normal fixture in BOH/Amenity

 ## Porte Cochere (Drive up Area)

-Create its own breakout in WBS, and phase in Accubid
+Create its own breakout in WBS, and phase in [[accubid|Accubid]]

 > [!quote]
 > This is not technically exposed or drop ceiling, but still use PVC
@@ -46,8 +46,8 @@ tags:

 ### See Also

-3. [[carbon-monoxide-detection-takeoff]]
-4. [[lightning-protection-takeoff]]
+* [[lightning-protection-takeoff]]
+* [[carbon-monoxide-detection-takeoff]]

 [[general-takeoff]]

@@ -13,6 +13,8 @@ up: "[[conest-projects]]"

 ## ConEst Questions

+Questions for [[conest|ConEst]]:
+
 ### Area Breakdowns

 Since residential building types have corridors
@@ -20,6 +22,8 @@ it will be necessary to create Areas for each level.

 ## Bid Questions

+Questions for [[pdi-bid-estimating|Bid]]:
+
 ### Voltage Drop

 VOLTAGE DROP CALCULATIONS ON ALL FEEDERS AND BRANCH CIRCUITS
@@ -3,5 +3,6 @@ title: Joel Jansen
 tags:
  - occupational
  - type/person
+up: "[[conest]]"
 ---
 # Joel Jansen
@@ -4,5 +4,6 @@ tags:
  - occupational
  - status/not-started
  - type/person
+up: "[[conest]]"
 ---
 # Josh Ford
@@ -9,8 +9,8 @@ tags:
 Assembly selection for lighting controls is _never_ straightforward,
 even where it ought to be.
 There _must_ be conversation and consensus
-between the [[conest]]
-and [[pdi-estimating#Bid Estimating|Bid]] senior estimators
+between the [[conest|ConEst]]
+and [[pdi-bid-estimating|Bid]] senior estimators
 before takeoff can begin.
 This note is intended to assist in collecting all information
 likely to be relevant to said discussion,
@@ -17,7 +17,7 @@ up: "[[takeoff-scripts]]"
 > no consideration for _any_ lighting control beyond standard devices,
 > (with `$D`'s being the [[lighting-controls#Triac Dimming|triac]] type)
 > however, this phrasing is ambiguous and non-universal.
-> Confirm with [[pdi-estimating#Bid Estimating|bid team]] on what must be included.
+> Confirm with [[pdi-bid-estimating|bid team]] on what must be included.

 Determine which Systems and Codes are required:
 * _IBC/IECC 2021 or later:_ all fixtures 0-10V dimmable.
@@ -26,7 +26,7 @@ search for direction on downlead counts, total length, and conduit size

 > [!tip]
 > While you have the quotes open,
-> put the costs in the Subcontractors tab in Accubid.
+> put the costs in the Subcontractors tab in [[accubid|Accubid]].

 If no quote is available:

@@ -4,6 +4,7 @@ tags:
  - occupational
  - status/not-started
  - type/person
+up: "[[pdi-estimating]]"
 ---
 # Megan Blizard

@@ -15,7 +15,7 @@ of [[this-notebook]].

 %%

-[[conest]]
+[[conest|ConEst]]

 ## Goals

@@ -229,5 +229,5 @@ delivers high-quality results and takes initiative.
 > Zane has been a great addition to our team in these short few months.
 > He's shown genuine enthusiasm while learning,
 > asks the right questions, and has picked up our PDI standards quickly.
-> His experience with Accubid has proven extremely valuable,
+> His experience with [[accubid|Accubid]] has proven extremely valuable,
 > and he's shared some helpful Excel shortcuts with the team.
@@ -7,6 +7,8 @@ tags:
 ---
 # PDI Accubid Closeout

+[[accubid|Accubid]]
+
 Also called "tabs".

 1. [[pdi-labor-plan]]
@@ -66,4 +68,4 @@ TODO
 > * "MATERIAL HANDLER - PER MO"

 Only if included in Base Bid.
-Confirm with [[pdi-estimating#Bid Estimating|Bid]] estimator.
+Confirm with [[pdi-bid-estimating|Bid]] estimator.
@@ -3,6 +3,7 @@ title: PDI Accubid Equipment
 tags:
  - occupational/closeout
  - type/guide
+up: "[[pdi-accubid-closeout]]"
 ---
 # PDI Accubid Closeout: Equipment

@@ -3,6 +3,7 @@ title: "PDI Accubid Closeout: Final Price"
 tags:
  - occupational/closeout
  - type/guide
+up: "[[pdi-accubid-closeout]]"
 ---
 # PDI Accubid Closeout: Final Price

@@ -3,6 +3,7 @@ title: "PDI Accubid Closeout: General Expenses"
 tags:
  - occupational/closeout
  - type/guide
+up: "[[pdi-accubid-closeout]]"
 ---
 # PDI Accubid Closeout: General Expenses

@@ -3,6 +3,7 @@ title: "PDI Accubid Closeout: Indirect Labor"
 tags:
  - occupational/closeout
  - type/guide
+up: "[[pdi-accubid-closeout]]"
 ---
 # PDI Accubid Closeout: Indirect Labor

@@ -3,6 +3,7 @@ title: "PDI Accubid Closeout: Quoted Material"
 tags:
  - occupational/closeout
  - type/guide
+up: "[[pdi-accubid-closeout]]"
 ---
 # PDI Accubid Closeout: Quoted Material

@@ -3,6 +3,7 @@ title: "PDI Accubid Closeout: Subcontractors"
 tags:
  - occupational/closeout
  - type/guide
+up: "[[pdi-accubid-closeout]]"
 ---
 # PDI Accubid Closeout: Subcontractors

@@ -0,0 +1,10 @@
+---
+aliases:
+  - Bid
+title: PDI Bid Estimating
+tags:
+  - occupational
+  - type/department
+up: "[[power-design-inc]]"
+---
+# PDI Bid Estimating
@@ -6,6 +6,8 @@ title: PDI Breakdowns
 ---
 # PDI Breakdowns

+[[accubid|Accubid]]
+
 ## Location

 ### Bid Item: Site
@@ -1,8 +1,9 @@
 ---
+title: PDI Estimating Systems
 tags:
  - occupational/takeoff
  - type/encyclopedia
-title: PDI Estimating Systems
+up: "[[pdi-estimating]]"
 ---
 # PDI Estimating Systems

@@ -3,6 +3,7 @@ tags:
  - occupational
  - type/encyclopedia
 title: PDI Estimating
+up: "[[power-design-inc]]"
 ---
 # PDI Estimating

@@ -14,6 +15,8 @@ title: PDI Estimating

 ### Bid Estimating

+Main article: [[pdi-bid-estimating]]
+
 ### Construction Estimating (ConEst)

-Main article: [[conest]]
+Main article: [[conest|ConEst]]
@@ -37,7 +37,7 @@ for multifamily, commercial, and federal projects.

 * Excellent communicator who is organized, detail-oriented, and efficient.

-* Proficiency in Microsoft Office and estimating software (Accubid preferred).
+* Proficiency in Microsoft Office and estimating software ([[accubid|Accubid]] preferred).

 * Demonstrate and uphold all of Power Design's core values,
    which include integrity, accountability, teamwork, innovation, and growth.
@@ -24,7 +24,7 @@ title: PDI Labor Plan
    * Change breakdown of everything in each phase to the proper `Labor Factor`
    * Do not move Temp Power (budgets) or site

-5. Use the Accubid Extension tab to fill out the "Unit Lbr Calc" tab in the labor plan
+5. Use the [[accubid|Accubid]] Extension tab to fill out the "Unit Lbr Calc" tab in the labor plan

 6. Select extension view "Phase, Sort Code"

@@ -1,9 +1,10 @@
 ---
 aliases:
-  - ops
+  - Ops
 title: PDI Operations
 tags:
  - occupational
+up: "[[power-design-inc]]"
 ---
 # PDI Operations

@@ -1,16 +1,18 @@
 ---
+aliases:
+  - Pre-Takeoff Confirmation
+title: Pre-Takeoff Confirmation
 tags:
+  - occupational/takeoff
  - status/draft
  - type/guide
-  - occupational/takeoff
-title: Pre-Takeoff Confirmation
 ---
 # Pre-Takeoff Confirmation

 The purpose of the pre-takeoff confirmation
 is to address potential discrepancies
 between the requirements of the project documents
-and the scope included in the bid team's proposed price.
+and the scope included in the [[pdi-bid-estimating|Bid]] team's proposed price.

 ## Procedure

@@ -28,14 +30,14 @@ Paste the completed template content to the body of a new email.

 **To:**
 * Preconstruction Manager %% Brian %%
-* Senior Bid Estimator %% Christian %%
+* Senior Bid Estimator %% [[christian-pereiro]] %%
 * Bid Estimator or Associate Estimator (if applicable)

 **CC:**
 * Senior Construction Estimator %% [[joel-jansen]] %%
-* ConEst Manager ([[josh-ford]])
-* Director of Estimating ([[corwin-fluit]])
+* ConEst Manager ([[josh-ford|Josh Ford]])
+* Director of Estimating ([[corwin-fluit|Corwin Fluit]])
 * Jessalyn Williams
-* Other ConEst Estimators (if applicable)
+* Other ConEst Estimators involved (if applicable)

 [^1]: [[2026-03-20_09-11-09#Pre-Takeoff Email Process]]
@@ -1,4 +1,6 @@
 ---
+aliases:
+  - PSN
 title: Project Start Notification
 tags:
  - authorship/other-for-now
@@ -29,7 +31,7 @@ Export Awarded WBS to PDF, or just copy if available.

 ## Procurement Accubid Export

-In master Accubid file,
+In master [[accubid|Accubid]] file,
 group by `System`, `PDI SORT CODES`.

 Export ==**Extension** only== as ==**Excel**==
@@ -1,5 +1,7 @@
 ---
-title: Project Start Notification
+aliases:
+  - WBS
+title: PDI WBS
 tags:
  - authorship/other-for-now
  - occupational
@@ -9,7 +11,8 @@ tags:

 ## CBOM Accubid Export

-In master Accubid file, group by `Bid Item`, `System`, `PDI SORT CODES`, `Area`, `Phase`.
+In master [[accubid|Accubid]] file,
+group by `Bid Item`, `System`, `PDI SORT CODES`, `Area`, `Phase`.

 Export ==**all tabs**== as ==**csv**== to ".\6. Notes & Emails\Accubid CBOM - {Job}"

@@ -0,0 +1,10 @@
+---
+id: 2026-04-28
+title: 2026-04-28
+tags: []
+weekly: "[[2026w18]]"
+monthly: "[[2026-04]]"
+quarterly: "[[2026q2]]"
+previous: "[[2026-04-27]]"
+---
+# 2026-04-28
@@ -0,0 +1,8 @@
+---
+aliases:
+  - PDI
+title: Power Design, Inc.
+tags:
+  - occupational
+---
+# Power Design, Inc.
@@ -17,7 +17,7 @@ This note should be arranged chronologically:
 * Project Manual (Specifications)
 * GC Narrative
 * GC verbal direction
-* Bid proposal
+* [[pdi-bid-estimating|Bid]] proposal
 * Bid verbal direction

 %%
@@ -20,7 +20,8 @@ when in practice there's no meaningful difference in practice from manual.

 * Manual estimation is best done in terms of [[assembly-philosophy#Assemblies|assemblies]] anyway.
 * On-screen takeoff only eliminates a single manual process.
-* Any estimator trained on Accubid could do the same by hand, the methodology is quite transparent.
+* Any estimator trained on [[accubid|Accubid]] could do the same by hand,
+    the methodology is quite transparent.
 * At what point in Excel automation does manual estimation become software based?

 There is no place for truly manual estimation (pencil and paper)
@@ -96,12 +96,6 @@ as well as other industries.
 This topic also includes concepts that may be useful to estimation,
 but that aren't widely understood to be.

-### #topic/math
-
-### #topic/risk
-
-Relating to mathematical and abstract concepts of [[risk]].
-
 ### #topic/ergonomics/organizational

 On the subject of [[optimal-patterns]] for processes
@@ -9,4 +9,4 @@ daily: "[[2025-08-22]]"

 ## Getting Historical Material Pricing

-Aggregate SupplierLink.xml files from Accubid job folders.
+Aggregate SupplierLink.xml files from [[accubid|Accubid]] job folders.
@@ -9,7 +9,7 @@ daily: "[[2025-11-13]]"

 ## Questions for Bid Estimators

-Questions for [[pdi-estimating#Bid Estimating|PDI Bid Estimators]].
+Questions for [[pdi-bid-estimating|PDI Bid Estimators]].

 ### Exclusions

@@ -26,7 +26,8 @@ A primary reason for the discussion was presented:

 > [!example] ^ex
 > While putting together a large garden style project
-> Bid received a quote for lighting control at over one million dollars.
+> [[pdi-bid-estimating|Bid]] received a quote for lighting control
+> at over one million dollars.
 > Believing it [[gold-plating|overengineered]],
 > Bid proposed ~$150,000 for lighting control "per code".
 > The contract was awarded on those terms.
@@ -6,7 +6,7 @@ daily: "[[2025-12-18]]"
 ---
 # 2025-12-18 15:22:??

-PDI has moved up the schedule to transition to Accubid Anywhere
+PDI has moved up the schedule to transition to [[accubid|Accubid]] Anywhere
 and will be signing a contract with Trimble in late January.

 [Drawer AI | Automated Electrical Takeoff & Estimating](https://drawer.ai/)
@@ -9,12 +9,12 @@ daily: "[[2026-01-07]]"
 ---
 # 2026-01-07 12:13:??

-Just now Jorge admonished another peer
+Just now [[jorge-padron|Jorge]] admonished another peer
 for using insulated wire for pool bonding,
 his rationale was flawed beyond saving
 (something about the difference between bonding and grounding),
 but stemmed from a frustratingly common misunderstanding
-that our Accubid assemblies are intended to be an accurate list
+that our [[accubid|Accubid]] assemblies are intended to be an accurate list
 of the material to be installed.

 They are not.
@@ -9,8 +9,8 @@ daily: "[[2026-01-07]]"
 ---
 # 2026-01-07 16:03:??

-There is a palpable animosity for [[pdi-estimating#Bid Estimating|Bid]]
-in [[conest]],
+There is a palpable animosity for [[pdi-bid-estimating|Bid]]
+in [[conest|ConEst]],
 stemming (I believe) from an lack of buy-in on Bid's part.

 The lack is easily explained by their [[estimating-culture#Incentives|incentive structure]]:
@@ -23,4 +23,4 @@ The award WBS shows $32,382 for equipment rental

 I'm dubious of all these explanations,
 but I don't have another one.
-I can't find the ConEst folder or Accubid file.
+I can't find the ConEst folder or [[accubid|Accubid]] file.
@@ -34,7 +34,7 @@ Follow up to [[2026-01-09_10-00-03#Lighting Control]]

 Josh stated my takeoff was correct per drawings,
 but that concessions would need to be made for the scope
-as sold by [[pdi-estimating#Bid Estimating|Bid]].
+as sold by [[pdi-bid-estimating|Bid]].
 At his direction I've removed dimming from BOH and corridor spaces.
 The remaining takeoff will remain,
 a $4/sf budget for a lighting control system for those areas was added.
@@ -10,7 +10,7 @@ daily: "[[2026-01-14]]"

 Follow-up to [[2026-01-13_11-28-14#Lighting Control]]

-> [!quote] Conversation between [[joel-jansen]] and Christian Pereiro regarding lighting control for [[2100-crystal-drive]]:
+> [!quote] Conversation between [[joel-jansen]] and [[christian-pereiro]] regarding lighting control for [[2100-crystal-drive]]:
 >
 > **Joel:** "It was sold as local."
 >
@@ -1,14 +1,15 @@
 ---
 id: 2026-01-25T18:46:00-0500
 title: 2026-01-25 18:46:??
-tags:
-  - topic/finance
+tags: []
 daily: "[[2026-01-25]]"
 ---
 # 2026-01-25 18:46:??

 ### Calculating Monthly Principal & Interest Payment

+Relevant to [[finance]]:
+
 For a **fixed-rate, fully-amortizing mortgage**,
 the monthly payment is computed using the **standard amortization formula**:

@@ -1,15 +1,14 @@
 ---
 id: 2026-01-29T17:57:00-0500
 title: 2026-01-29 17:57:??
-tags:
-  - topic/finance
+tags: []
 daily: "[[2026-01-29]]"
 ---
 # 2026-01-29 17:57:??

 ### Calculating Utility of Above-Minimum Mortgage Payment

-See [[2026-01-25#Calculating Monthly Principal & Interest Payment]].
+Follow-up to [[2026-01-25#Calculating Monthly Principal & Interest Payment]]:

 Homeowners are often advised to make elective mortgage payments
 to reduce the total interest paid on the loan,
@@ -21,8 +20,8 @@ and are deciding whether to make an elective payment on your mortgage
 or to invest in a promising opportunity.

 The return on electing to pay $E$ to the mortgage
-is the
-(i.e., interest that will no longer accrue)
+is the ...
+(i.e. interest that will no longer accrue)
 at the end of the loan is:

 $$
@@ -8,6 +8,6 @@ daily: "[[2026-02-03]]"
 ---
 # 2026-02-03 16:17:00

-Valued in [[conest]] estimators:
+Valued in [[conest|ConEst]] estimators:
 * **consistency**
 * **humility** --- willingness to say "I don't know that, please teach me"
@@ -10,13 +10,13 @@ daily: "[[2026-02-04]]"

 ## Questions for ConEst

-[[conest]]
+[[conest|ConEst]]

 ### Purpose of ConEst

 What is the purpose of ConEst?
-To comb for requirements Bid missed?
-To create the CBOM for Ops?
+To comb for requirements [[pdi-bid-estimating|Bid]] missed?
+To create the CBOM for [[pdi-operations|Ops]]?
 Anything else?
 How do they rank in importance?

@@ -29,7 +29,7 @@ attended by [[christian-pereiro]], [[joel-jansen]], and myself.
 Systems refused to quote lighting control due to lack of detail,
 but sufficient detail was provided.

-Bid expected takeoff to include DLM devices and cabling.
+[[pdi-bid-estimating|Bid]] expected takeoff to include DLM devices and cabling.

 ### Closeout

@@ -25,6 +25,6 @@ and continuing takeoff as if the scope were not typical

 The ability to reorder and permanently delete takeoff
 would invalidate most concerns here,
-however Accubid's solution to typical scope
+however [[accubid|Accubid]]'s solution to typical scope
 (named-typicals-as-breakdowns)
 is still clunky and unsuitable for large projects.
@@ -12,7 +12,7 @@ date-created: 2026-02-27T13:58:30-05:00
 ## Conversation Regarding ConEst Pre-Takeoff Email Template

 A conversation with a peer via Microsoft teams
-regarding [[conest]]'s
+regarding [[conest|ConEst]]'s
 recent implementation of [[conest-pre-takeoff-email-template]].

 ### Peer @ 13:42
@@ -50,7 +50,7 @@ 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,
+to check [[pdi-bid-estimating|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.

@@ -10,7 +10,7 @@ date-created: 2026-02-28T12:02:03-05:00
 ---
 # 2026-02-28 12:02:03

-It is difficult to express how _little_ Accubid does for the user.
+It is difficult to express how _little_ [[accubid|Accubid]] does for the user.
 Except for LiveCount and SupplierLink
 (which are separate programs anyhow)
 100% of its functionality could be replicated with database queries.
@@ -37,7 +37,7 @@ Has not had a chance to complete a Garden style project at this time.

 * Create a unit matrix Excel document.

-* Enter information into Accubid.
+* Enter information into [[accubid|Accubid]].

 #### Score: Highly Proficient

@@ -131,7 +131,7 @@ Identify wiring type, receptacle and switch specs based on Unit panel, proposal

 Minimal to no issues on unit take-offs.
 Captures all systems included in our scope.
-Gets clarification from myself or Bid
+Gets clarification from myself or [[pdi-bid-estimating|Bid]]
 on discrepencies between drawings/PDI proposal (typically telecom).

 ### Skill: Units Sub feeds
@@ -202,7 +202,7 @@ and seeks help for more complex situations.
 Regularly achieves performance targets and actions.

 %%
-Joel framed [[pdi-estimating#Bid Estimating|Bid Estimating]]
+Joel framed [[pdi-bid-estimating|Bid Estimating]]
 as the customer in question,
 and implied that if I had a more involved relationship
 with the relevant bid estimators (namely Christian)
@@ -342,7 +342,7 @@ Delivers exceptional performance and actions,
 far beyond role targets.

 %%
-We discussed my fluency in Accubid,
+We discussed my fluency in [[accubid|Accubid]],
 which is a skill I'm annoyed to have.
 It's like being really good at digging trenches with a garden trowel.
 Skill using a poor tool
@@ -21,7 +21,7 @@ with a search algorithm like [A*](https://en.wikipedia.org/wiki/A*_search_algori
 Such a program could also calculate voltage drop.

 I think, though, I may have been unfair to my employers (current and previous).
-Innovative methods will always be bottlenecked by Accubid's strict input pattern,
+Innovative methods will always be bottlenecked by [[accubid|Accubid]]'s strict input pattern,
 but there are still opportunities for improvement
 that can comply with existing expectations of evidence.

@@ -26,7 +26,7 @@ be used to track
 Intent is too provide information to the bid team
 potentially to be qualified in future bids.

-> 1. ConEst deviates from specs based on direction from Bid.
+> 1. ConEst deviates from specs based on direction from [[pdi-bid-estimating|Bid]].
 > 2. Awarded contract does not include respect for the direction
 > 3. Ops, not aware of direction, believes ConEst takeoff was in error.

@@ -13,7 +13,7 @@ daily: "[[2026-03-25]]"

 Direction for [[telecom-takeoff]] and [[low-voltage-takeoff]]
 concerning the proper interpretation of "free-air per code"
-as used by [[pdi-estimating#Bid Estimating|Bid]] to qualify our scope.
+as used by [[pdi-bid-estimating|Bid]] to qualify our scope.
 Relevant to [[charlotte-south-end-hotel]].

 > [!quote] Charlotte South End Proposal 2025-12-12 Ex. B Notes
@@ -21,4 +21,4 @@ Project start date according to the Approved PDI Labor Plan is 2025-05-04.

 ***

-Bid used 8.25% as they ought to have.
+[[pdi-bid-estimating|Bid]] used 8.25% as they ought to have.
@@ -27,6 +27,8 @@ estimator and senior tasks.

 #### 2. Accubid Extension Pricing

+Relevant to [[pdi-accubid-extension]]:
+
 PDI used as vendor as required.

 Quotes requested, received for any specialty items.
@@ -58,9 +58,9 @@ Joel intends to substitute.
 ***

 **\[2026-03-26 09:36\]**
-After conversation with Christian,
+After conversation with [[christian-pereiro]],
 Joel substituted all EMT feeders for MC cable.
-Christian stated that [[pdi-estimating#Bid Estimating|they]]
+Christian stated that [[pdi-bid-estimating|they]]
 would qualify the substitution in their next proposal
 and raised that 5 inch EMT does not exist in our database anyway[^1].

@@ -49,7 +49,7 @@ Confirmed for 1990.

 Fire pump feeds are not tagged as 2hr rated
 takeoff assumed 2hr rated MC cable ("Vitalink")
-to be confirmed with Christian.
+to be confirmed with [[christian-pereiro]].

 ### EV Chargers

@@ -99,7 +99,7 @@ expected ~0.120.
 ***

 Josh found the answer to a question of scope
-in the qualifications of Bid's proposal.
+in the qualifications of [[pdi-bid-estimating|Bid]]'s proposal.
 he said he did not immediately think to look for them
 because they are rare of current proposals.
 Apparently they are penalized by the Proposal Audit Scorecard.
@@ -41,7 +41,7 @@ with the expectation that they may need to substitute them
 following [[conest-senior-review]].
 This is a [[heuristics|heuristic]]
 in that it achieves an outcome acceptable to the estimator
-despite being objectionable according to established[^1] [[conest]] practice.
+despite being objectionable according to established[^1] [[conest|ConEst]] practice.

 [^1]: As far as it can be said to be established...

@@ -20,7 +20,7 @@ he told me to use my best judgement.
 I told him that _my_ intuition,
 trained from my time estimating for Ace,
 is to break down by **scope**,
-but that [[conest]] usually breaks down by **location**.
+but that [[conest|ConEst]] usually breaks down by **location**.
 He agreed that is the preference,
 and since the previous estimator's breakdowns
 did not include Building Areas for the FB zones anyway
@@ -10,11 +10,12 @@ daily: "[[2026-04-10]]"
 ---
 # 2026-04-10 08:28:18

-I tend to think I have more to contribute to [[conest]] than to Bid.
+I tend to think I have more to contribute to [[conest|ConEst]]
+than I do to [[pdi-bid-estimating|Bid]].
 I'd need to know more about the executive philosophy of both
 before I could decide to switch or stay.

-> Moreover, what about estimating coordinators and "estimating solutions"?
+> Moreover, what about estimating coordinators and "[[pdi-estimating-solutions|Estimating Solutions]]"?

 I know very little now,
 but it doesn't seem many are more certain.
@@ -38,4 +39,5 @@ jobs of every size tend to take about two weeks
 (80 estimator hours plus change for review).
 In order for ConEst to estimate as budgeted,
 we would need standards for acceptable takeoff
-at multiple levels of estimating detail.
+at multiple levels of estimating detail,
+which we do not.
@@ -22,4 +22,4 @@ The use of 450kcmil for the EGC is strange:
 * it is a non-standard size anyway,
    not appearing in [[nfpa-70_ch09|Chapter 9]] tables,
    the [[neca-mlu]],
-    or our Accubid database.
+    or our [[accubid|Accubid]] database.
@@ -51,7 +51,7 @@ are not actionable plans.
 "Mistake" may be a misnomer,
 because acceptability is not objective.
 For example:
-two [[conest]] senior estimators
+two [[conest|ConEst]] senior estimators
 may disagree on the acceptability of a certain [[heuristics|heuristic]].
 It may still be useful to record criticism from the more stringent senior
 as a mistake, even if their position is less popular.
@@ -26,7 +26,7 @@ High-Level

 Process changes

-Accubid Anywhere
+[[accubid|Accubid Anywhere]]

 #### Also Planned

@@ -11,7 +11,11 @@ Follow-up to [[2026-04-23_16-24-49]]:

 Knowing now that [[pdi-operations|Ops]]'s baseline estimate
 isn't entirely redundant with [[conest|ConEst]]'s,
+I'm less convinced that "detailed takeoff"
+(for lack of a better term[^1])
+could easily be removed from the [[pdi-estimating]] process.

+[^1]: See [[traditional-estimating-methods]].

 Suppose that an ongoing project
 with 1000 feet of #2 CU in its CBOM
@@ -16,6 +16,6 @@ and "fly\[ing\] by the seat of \[one's\] pants".

 [Strategic Foresight](https://en.wikipedia.org/wiki/Strategic_foresight)
 has a Wikipedia page,
-but I'll be so bold as to suggest it shouldn't.
+but I'll be so bold as to suggest that it shouldn't.
 It has the same problem as [[project-management-tm|"project management"]]
 as the name of a discipline.
@@ -1,7 +0,0 @@
---
-id: 2026-04-26T09:30:18-0400
-title: 2026-04-26 09:30:18
-tags: []
-daily: "[[2026-04-26]]"
---
-# 2026-04-26 09:30:18
@@ -17,7 +17,7 @@ with all runs less than 100ft.

 I asked [[joel-jansen]] if it would be necessary
 to use minimum 10 AWG
-as is [[conest]] standard
+as is [[conest|ConEst]] standard
 for [[pdi-breakdowns#Bid Item Garage|Garage]].
 He said it would not be,
 and confirmed 12 AWG is acceptable in this case.
@@ -11,13 +11,13 @@ daily: "[[2026-04-27]]"
 Continuing a recent conversation
 I've been having with [[joel-jansen]]
 on [[voltage-drop]],
-both ideally and for application in [[conest]],
-Joel brought Bill Swan with Estimating Solutions
+both ideally and for application in [[conest|ConEst]],
+Joel brought Bill Swan with [[pdi-estimating-solutions|Estimating Solutions]]
 over to my desk.
 Bill said that when he is calculating voltage drop
 he doesn't the ubiquitous "Voltage Drop Calc 2011.xlsx"
 which uses a simple DC calculation,
-he uses [[pdi-vdc]]'s calculator,
+he uses [[pdi-vdc|VDC]]'s calculator,
 which is based on AC resistance and reactance.

 I showed them my own calculator,
@@ -8,27 +8,36 @@ daily: "[[2026-04-27]]"

 ## Virginia Live! Internal Review

-[[virginia-live-casino-and-hotel]]
+review of [[virginia-live-casino-and-hotel]] [[accubid|Accubid]] job
+with [[pdi-operations|Ops]]

 Underfloor power is Reloc.
 Customer is curious if it would be more cost effective to use MC.

-Objective is to discuss closeout mainly:
+### Meeting Objective
+
+discuss closeout mainly:
 quotes and subs.

-FF&E
+### Topics Discussed
+
+#### Fixture Labor
+
+> **Furniture, Fixtures, and Equipment (FF&E)**
+
 Concern that all fixtures are captured

 "add a line for aiming and testing"
 1 week (80 hours)

-Shift rate
+#### Shift Rate
+
 "in the past we've paid a little more for night work,
 but nothing crazy"

-$2,500 per day scaffold
+#### Site Services

-### Site Services
+$2,500 per day scaffold

 Ditch witches for most excavation

@@ -40,7 +49,7 @@ hydraulic bender
 Do we own dewatering?
 pretty sure yes

-### MV Terminations
+#### MV Terminations

 No one at PDI can perform MV terms
 so they must be subbed out
@@ -51,7 +60,7 @@ worst case $300k

 to be quoted by Ops

-### Testing
+#### Testing

 primary injection testing

@@ -59,25 +68,25 @@ NETA testing

 to be quoted by Ops

-### Rigging
+#### Rigging

 Ops quoted $85k to take one generator off the truck.

 to be quoted by Ops

-### Burden
+#### Burden

 PTO not included in burden
 because it is not charged to the job

 ### Admin Housing

-Ops paying $4,500 for 6-bed
+Ops paying $4,500 per month for 6-bed

-### Composite Cleanup
+#### Composite Cleanup

-terms in contract
+exact terms in contract

-### Permits
+#### Permits

 to be quoted by Ops