vault backup: 2025-09-30 18:41:22

This commit is contained in:
2025-09-30 18:41:22 -04:00
parent e33ee183ac
commit 09e2493efa
9 changed files with 163 additions and 135 deletions
+80 -80
View File
@@ -1,5 +1,85 @@
{
"recentFiles": [
{
"basename": "sketch-over-photo-style-example",
"path": "sketch-over-photo-style-example.png"
},
{
"basename": "switchgear",
"path": "switchgear.md"
},
{
"basename": "company-switch",
"path": "company-switch.png"
},
{
"basename": "burndy-AYP300_pigtail-adaptor",
"path": "burndy-AYP300_pigtail-adaptor.png"
},
{
"basename": "birds",
"path": "birds.md"
},
{
"basename": "lighting-controls",
"path": "lighting-controls.md"
},
{
"basename": "2025-07-18_estimating-isnt-engineering",
"path": "2025-07-18_estimating-isnt-engineering.md"
},
{
"basename": "automating-pdf-annotation",
"path": "automating-pdf-annotation.md"
},
{
"basename": "full-takeoff",
"path": "full-takeoff.md"
},
{
"basename": "README",
"path": "README.md"
},
{
"basename": "automating-estimating-project-creation",
"path": "automating-estimating-project-creation.md"
},
{
"basename": "breakdown-objects",
"path": "breakdown-objects.md"
},
{
"basename": "project-info",
"path": "project-info.md"
},
{
"basename": "automating-email",
"path": "automating-email.md"
},
{
"basename": "assembly-objects",
"path": "assembly-objects.md"
},
{
"basename": "strategy",
"path": "strategy.md"
},
{
"basename": "requirement-precedence",
"path": "requirement-precedence.md"
},
{
"basename": "realism-vs-instrumentalism",
"path": "realism-vs-instrumentalism.md"
},
{
"basename": "uncertainty",
"path": "uncertainty.md"
},
{
"basename": "this-notebook",
"path": "this-notebook.md"
},
{
"basename": "estimating-methodologies",
"path": "estimating-methodologies.md"
@@ -52,18 +132,10 @@
"basename": "construction-estimating-using-excel",
"path": "construction-estimating-using-excel.md"
},
{
"basename": "automating-email",
"path": "automating-email.md"
},
{
"basename": "assembly-philosophy",
"path": "assembly-philosophy.md"
},
{
"basename": "assembly-objects",
"path": "assembly-objects.md"
},
{
"basename": "area-of-refuge",
"path": "area-of-refuge.md"
@@ -76,10 +148,6 @@
"basename": "accubid-setup",
"path": "accubid-setup.md"
},
{
"basename": "2025-07-18_estimating-isnt-engineering",
"path": "2025-07-18_estimating-isnt-engineering.md"
},
{
"basename": "90-day-performance-review",
"path": "90-day-performance-review.md"
@@ -96,10 +164,6 @@
"basename": "estimating-as-code",
"path": "estimating-as-code.md"
},
{
"basename": "birds",
"path": "birds.md"
},
{
"basename": "favorite-quotes",
"path": "favorite-quotes.md"
@@ -108,10 +172,6 @@
"basename": "pre-takeoff-confirmation",
"path": "pre-takeoff-confirmation.md"
},
{
"basename": "burndy_AYP300",
"path": "Assets/subfeeds/burndy_AYP300.png"
},
{
"basename": "location-vs-scope",
"path": "Excalidraw/location-vs-scope.md"
@@ -120,18 +180,10 @@
"basename": "standalone-systems",
"path": "standalone-systems.md"
},
{
"basename": "full-takeoff",
"path": "full-takeoff.md"
},
{
"basename": "feeders",
"path": "feeders.md"
},
{
"basename": "README",
"path": "README.md"
},
{
"basename": "grounding",
"path": "grounding.md"
@@ -140,10 +192,6 @@
"basename": "functional-estimating",
"path": "functional-estimating.md"
},
{
"basename": "uncertainty",
"path": "uncertainty.md"
},
{
"basename": "raceway-terms",
"path": "raceway-terms.md"
@@ -151,54 +199,6 @@
{
"basename": "risk",
"path": "risk.md"
},
{
"basename": "risk-oriented-estimating",
"path": "risk-oriented-estimating.md"
},
{
"basename": "functional-labor-factoring",
"path": "functional-labor-factoring.md"
},
{
"basename": "traditional-estimating-methods",
"path": "traditional-estimating-methods.md"
},
{
"basename": "sleeving",
"path": "sleeving.md"
},
{
"basename": "realism-vs-instrumentalism",
"path": "realism-vs-instrumentalism.md"
},
{
"basename": "automating-pdf-annotation",
"path": "automating-pdf-annotation.md"
},
{
"basename": "automating-estimating-project-creation",
"path": "automating-estimating-project-creation.md"
},
{
"basename": "breakdown-objects",
"path": "breakdown-objects.md"
},
{
"basename": "subfeeds",
"path": "subfeeds.md"
},
{
"basename": "project-setup",
"path": "project-setup.md"
},
{
"basename": "markdown-formatter-cli",
"path": "markdown-formatter-cli.md"
},
{
"basename": "separating-estimating-concerns",
"path": "separating-estimating-concerns.md"
}
],
"omittedPaths": [],
+1 -33
View File
@@ -9,13 +9,7 @@ tags:
---
# Automating Estimating Project Creation
Use-case specific wrapper for a document database like MongoDB.
## Features
Features below are in addition to those of Vanilla Atlas.
### Extract from Bid Boards
## Extract from Bid Boards
```sh
> jobHandler --new project --from-web https://app.buildingconnected.com/opportunities/66fab32654ef4e1affd178e0/info
@@ -27,29 +21,3 @@ Features below are in addition to those of Vanilla Atlas.
jobHandler\FreezPak Cold Storage> --add-details --from-web https://app.buildingconnected.com/opportunities/66fab32654ef4e1affd178e0/info
...
```
## Standard Structured Text for Projects
Markdown with YAML frontmatter is an excellent choice for project documentation
which offers a compromise between interoperability and flexibility.
* [x] Create an `Import-Markdown` returning `frontmatter` and `body` objects.
* [ ] Create vscode workflows for formatting frontmatters and calculating properties.
* [ ] Integrate my "Estimating Work" and "Notebook" folders
* Before my plaintext renaissance, I used to need many more .xlsx and .pdf files
for a single project. It makes better sense for `Sources.xlsx` to be .yaml
Ultimately most project information could be formatted in markdown and yaml files,
greatly aiding in:
* quick research
* data aggregation and analysis
* version control and backups
* software independence
without compromising on professional output.
Even proposals are truly better suited to this format as,
neglecting the former benefits,
markdown can be rendered with standard stylesheets for improved consistency.
Sublime is a friendly option for non-technical users.
+5 -1
View File
@@ -75,9 +75,13 @@ Recursively parse and consume pdf vector content.
> creating a `duplex_gfci_receptacle` token
> which inherits the `duplex_receptacle`'s position.
```
```sh
$ mutool show file.pdf pages/1/Contents
```
>>>
```pdf
629 0 obj
<<
/Filter /FlateDecode

Before

Width:  |  Height:  |  Size: 182 KiB

After

Width:  |  Height:  |  Size: 182 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 91 KiB

+24
View File
@@ -29,3 +29,27 @@ To calculate regular quantities
* conductor support
* by area
* temp power
Markdown with YAML frontmatter is an excellent choice for project documentation
which offers a compromise between interoperability and flexibility.
* [x] Create an `Import-Markdown` returning `frontmatter` and `body` objects.
* [ ] Create vscode workflows for formatting frontmatters and calculating properties.
* [ ] Integrate my "Estimating Work" and "Notebook" folders
* Before my plaintext renaissance, I used to need many more .xlsx and .pdf files
for a single project. It makes better sense for `Sources.xlsx` to be .yaml
Ultimately most project information could be formatted in markdown and yaml files,
greatly aiding in:
* quick research
* data aggregation and analysis
* version control and backups
* software independence
without compromising on professional output.
Even proposals are truly better suited to this format as,
neglecting the former benefits,
markdown can be rendered with standard stylesheets for improved consistency.
Sublime is a friendly option for non-technical users.
Binary file not shown.

After

Width:  |  Height:  |  Size: 502 KiB

+1 -1
View File
@@ -49,7 +49,7 @@ tags:
#### Pigtail Adaptors
![[burndy_AYP300.png]]
![[burndy-AYP300_pigtail-adaptor.png]]
Pigtail adaptors are used where feeder wires exceed the range of panel lugs.
+52 -20
View File
@@ -6,38 +6,61 @@ tags:
---
# Switchgear
## Info
### Special Equipment
#### Company Switches
> [!info] Also Known As
> * Theatrical Switchboards
> * Stage Switchboards
Company switches are lighting control devices
unique to performance venues
like those subject to **NEC Article 520:
Theaters, Audience Areas of Motion Picture and Television Studios,
Performance Areas, and Similar Locations**
![[company-switch.png|500x625]]
> [!cite] NEC Article 520.2
> **Stage Switchboard.**
> A permanently installed switchboard, panelboard, or rack
> containing dimmers or relays with associated overcurrent protective devices,
> or overcurrent protective devices alone, used primarily to feed stage equipment.
## Sequence
### 1. Estimate preparation
1. Initial the OneNote
2. In the drawings, locate:
* Riser Diagrams
* House Panels
3. Copy over default Temporary Assemblies from sandbox job
* Riser Diagrams
* House Panels
### 2. Takeoff
1. Build Items in Distribution:
* Panelboards
* Switchboards
* Meter centers
* Generators
* Transfer switches
* Generator connection cabinets
* Panelboards
* Switchboards
* Meter centers
* Generators
* Transfer switches
* Generator connection cabinets
* CT cabinet
* Power monitor
2. Takeoff Common Assemblies:
* XFMRs
* Disconnect switches
* XFMRs
* Disconnect switches
3. Takeoff Items in Item Database:
* Wireway (Trough/Gutter)
* Wireway (Trough/Gutter)
4. Takeoff Temp Assemblies:
* CT Cabinet
* Meter
* Fire Pump
* Fire Pump Controller
* Fire Pump
* Fire Pump Controller
When building panelboards/switchboards,
add terminations according to an example from the schedules.
@@ -53,7 +76,16 @@ Items to Avoid:
#### SPD's/TVSS's
Labor only: ~1.5hrs
Labor only.
Specific item is not important, but I use
`SPLITTERS / SOCKETS / CABINETS`/`METER SOCKETS & CABINETS`/`METERING CURRENT TRANSFORMER`
(Labor = 1.5hrs)
for consistency.
#### Submeters/Power Monitors
See [[switchgear#SPD's/TVSS's]]
#### Panelboards
@@ -65,7 +97,7 @@ Treat as disconnect switch.
#### Generators
Add `GENERATOR SET UP`
Add `DISTRIBUTION FITTINGS`/`GENERATOR SET UP`.
#### Generator Connection Cabinets
@@ -92,5 +124,5 @@ Adjust Factor 1 for meter stacks, delete zeroed items.
### 3. Extension (Review and Checking)
1. Generator
* Ensure takeoff is in the generator Area and System breakdowns
* Put location, quantity, and type on OneNote
* Ensure takeoff is in the generator Area and System breakdowns
* Put location, quantity, and type on OneNote