vault backup: 2026-01-22 16:52:55
This commit is contained in:
+1
-1
@@ -123,7 +123,7 @@
|
|||||||
"mdBorderColor": "Black",
|
"mdBorderColor": "Black",
|
||||||
"mdCSS": "",
|
"mdCSS": "",
|
||||||
"scriptEngineSettings": {},
|
"scriptEngineSettings": {},
|
||||||
"previousRelease": "2.19.1",
|
"previousRelease": "2.19.2",
|
||||||
"showReleaseNotes": true,
|
"showReleaseNotes": true,
|
||||||
"compareManifestToPluginVersion": true,
|
"compareManifestToPluginVersion": true,
|
||||||
"showNewVersionNotification": false,
|
"showNewVersionNotification": false,
|
||||||
|
|||||||
+2
-2
File diff suppressed because one or more lines are too long
@@ -1,7 +1,7 @@
|
|||||||
{
|
{
|
||||||
"id": "obsidian-excalidraw-plugin",
|
"id": "obsidian-excalidraw-plugin",
|
||||||
"name": "Excalidraw",
|
"name": "Excalidraw",
|
||||||
"version": "2.19.1",
|
"version": "2.19.2",
|
||||||
"minAppVersion": "1.5.7",
|
"minAppVersion": "1.5.7",
|
||||||
"description": "Sketch Your Mind. An Obsidian plugin to edit and view Excalidraw drawings. Enter the world of 4D Visual PKM.",
|
"description": "Sketch Your Mind. An Obsidian plugin to edit and view Excalidraw drawings. Enter the world of 4D Visual PKM.",
|
||||||
"author": "Zsolt Viczian",
|
"author": "Zsolt Viczian",
|
||||||
|
|||||||
@@ -0,0 +1,79 @@
|
|||||||
|
---
|
||||||
|
id:
|
||||||
|
aliases: []
|
||||||
|
title: 2026-01-22
|
||||||
|
tags:
|
||||||
|
- authorship/original
|
||||||
|
- destiny/permanent
|
||||||
|
- status/draft
|
||||||
|
- type/daily
|
||||||
|
---
|
||||||
|
# 2026-01-22
|
||||||
|
|
||||||
|
## 2026-01-22 09:55
|
||||||
|
|
||||||
|
The lighting drawings for
|
||||||
|
450-460 James Robertson Parkway Phase II
|
||||||
|
(fka James Roberston Pkwy Mixed Use Development)
|
||||||
|
show occupancy sensors serving electrical rooms.
|
||||||
|
I knew this was understood to be prohibited,
|
||||||
|
but could not have provided a code reference.
|
||||||
|
|
||||||
|
[[nfpa-70_110_requirements#110.26(D) Illumination.|110.26(D)]]
|
||||||
|
is the relevant section.
|
||||||
|
|
||||||
|
## 2026-01-22 11:58
|
||||||
|
|
||||||
|
### 463 Davison Contract Dates
|
||||||
|
|
||||||
|
[[463-davison-ave-ne]]
|
||||||
|
|
||||||
|
Effective date: [[2026-01-21]]
|
||||||
|
|
||||||
|
* [ ] Escrow deposit due by [[2026-01-26]]
|
||||||
|
* [ ] Loan application submitted by [[2026-01-26]]
|
||||||
|
* [ ] Inspection period ends [[2026-01-28]]
|
||||||
|
* [ ] Loan approval due by [[2026-02-11]]
|
||||||
|
* [ ] Title commitment due by [[2026-02-27]]
|
||||||
|
|
||||||
|
Closing: [[2026-03-04]]
|
||||||
|
|
||||||
|
## 2026-01-22 14:56
|
||||||
|
|
||||||
|
### Accurate Budget Vs. Accurate BOM
|
||||||
|
|
||||||
|
#### Quote
|
||||||
|
|
||||||
|
> [!quote] Joel Jansen [[2026-01-15#2026-01-15 13:27]] (pp.)
|
||||||
|
> I'd rather have an accurate budget than an accurate BOM.
|
||||||
|
|
||||||
|
#### Context
|
||||||
|
|
||||||
|
#### Analysis
|
||||||
|
|
||||||
|
It may be counterintuitive to BOM-oriented estimators
|
||||||
|
(typical of those with an electrical background),
|
||||||
|
but deviating from ~~common practice~~
|
||||||
|
to make an assembly "more accurate"
|
||||||
|
(read: to make the estimate BOM
|
||||||
|
more closely resemble the construction BOM),
|
||||||
|
may make the budget _less_ accurate.
|
||||||
|
|
||||||
|
The review and adjustment process is based on ~~common practice~~,
|
||||||
|
|
||||||
|
Our assemblies do not include screws
|
||||||
|
It would be more accurate to the BOM to add them,
|
||||||
|
but we budget for that cost in the summary,
|
||||||
|
so to do so would be double dipping.
|
||||||
|
|
||||||
|
Though not stated as such,
|
||||||
|
we budget for takeoff-to-install deviations the same way.
|
||||||
|
|
||||||
|
\
|
||||||
|
|
||||||
|
An organization's takeoff database
|
||||||
|
ought to include exactly what is necessary for takeoff
|
||||||
|
at the acceptable level of detail, and nothing else.
|
||||||
|
It ought to be assumed by estimators that the previous is true,
|
||||||
|
and that acceptable takeoff of any scope
|
||||||
|
must be possible with the contents of the database.
|
||||||
@@ -0,0 +1,46 @@
|
|||||||
|
---
|
||||||
|
id:
|
||||||
|
aliases: []
|
||||||
|
title: 463 Davison Ave NE
|
||||||
|
tags:
|
||||||
|
- authorship/original
|
||||||
|
- destiny/permanent
|
||||||
|
- status/incomplete
|
||||||
|
---
|
||||||
|
# 463 Davison Ave NE
|
||||||
|
|
||||||
|
463 Davison Ave NE
|
||||||
|
St. Petersburg, FL 33703
|
||||||
|
|
||||||
|
## Spaces
|
||||||
|
|
||||||
|
### Living/Dining
|
||||||
|
|
||||||
|
### Main Bedroom
|
||||||
|
|
||||||
|
### Guest Bedroom A
|
||||||
|
|
||||||
|
### Guest Bedroom B
|
||||||
|
|
||||||
|
## Needs
|
||||||
|
|
||||||
|
### Appliances
|
||||||
|
|
||||||
|
#### Clothes Washing
|
||||||
|
|
||||||
|
Stacked washer dryer combo
|
||||||
|
|
||||||
|
#### Television
|
||||||
|
|
||||||
|
%% boo. %%
|
||||||
|
|
||||||
|
Maybe take back from Val.
|
||||||
|
|
||||||
|
### Furnishings
|
||||||
|
|
||||||
|
#### Rugs
|
||||||
|
|
||||||
|
1 each bedroom (3)
|
||||||
|
2--3 living/dining area
|
||||||
|
|
||||||
|
####
|
||||||
+34
-2
@@ -1,13 +1,13 @@
|
|||||||
---
|
---
|
||||||
id:
|
id:
|
||||||
aliases: []
|
aliases: []
|
||||||
|
title: Diagrams
|
||||||
tags:
|
tags:
|
||||||
- authorship/original
|
- authorship/original
|
||||||
- destiny/uncertain
|
- destiny/uncertain
|
||||||
- status/incomplete
|
- status/incomplete
|
||||||
- topic/meta
|
- topic/meta
|
||||||
- type/encyclopedia-entry
|
- type/encyclopedia-entry
|
||||||
title: Diagrams
|
|
||||||
---
|
---
|
||||||
# Diagrams
|
# Diagrams
|
||||||
|
|
||||||
@@ -62,4 +62,36 @@ classDiagram
|
|||||||
| `--` | Link (Solid) |
|
| `--` | Link (Solid) |
|
||||||
| `..>` | Dependency |
|
| `..>` | Dependency |
|
||||||
| `..\|>` | Realization |
|
| `..\|>` | Realization |
|
||||||
| `..` | Link (Dashed) |
|
| `..` | Link (Dashed) |
|
||||||
|
|
||||||
|
### Pie Chart
|
||||||
|
|
||||||
|
```mermaid
|
||||||
|
pie title Estimating Process
|
||||||
|
"Estimate Preparation" : 15
|
||||||
|
"Takeoff" : 65
|
||||||
|
"Estension & Review" : 10
|
||||||
|
"Bid Summary" : 10
|
||||||
|
```
|
||||||
|
|
||||||
|
### Mind Map
|
||||||
|
|
||||||
|
```mermaid
|
||||||
|
mindmap
|
||||||
|
root((mindmap))
|
||||||
|
Origins
|
||||||
|
Long history
|
||||||
|
::icon(fa fa-book)
|
||||||
|
Popularisation
|
||||||
|
British popular psychology author Tony Buzan
|
||||||
|
Research
|
||||||
|
On effectiveness<br/>and features
|
||||||
|
On Automatic creation
|
||||||
|
Uses
|
||||||
|
Creative techniques
|
||||||
|
Strategic planning
|
||||||
|
Argument mapping
|
||||||
|
Tools
|
||||||
|
Pen and paper
|
||||||
|
Mermaid
|
||||||
|
```
|
||||||
|
|||||||
@@ -445,11 +445,11 @@ and likely to require examination, adjustment, servicing, or maintenance while e
|
|||||||
shall comply with the dimensions of 110.26(A)(1), (A)(2), (A)(3), and (A)(4)
|
shall comply with the dimensions of 110.26(A)(1), (A)(2), (A)(3), and (A)(4)
|
||||||
or as required or permitted elsewhere in this Code.
|
or as required or permitted elsewhere in this Code.
|
||||||
|
|
||||||
Informational Note:
|
> [!info] Informational Note:
|
||||||
NFPA 70E-2018, Standard for Electrical Safety in the Workplace,
|
> NFPA 70E-2018, Standard for Electrical Safety in the Workplace,
|
||||||
provides guidance, such as determining severity of potential exposure,
|
> provides guidance, such as determining severity of potential exposure,
|
||||||
planning safe work practices including establishing an electrically safe work condition,
|
> planning safe work practices including establishing an electrically safe work condition,
|
||||||
arc flash labeling, and selecting personal protective equipment.
|
> arc flash labeling, and selecting personal protective equipment.
|
||||||
|
|
||||||
### 110.26(A)(1) Depth of Working Space.
|
### 110.26(A)(1) Depth of Working Space.
|
||||||
|
|
||||||
|
|||||||
@@ -0,0 +1,25 @@
|
|||||||
|
---
|
||||||
|
id:
|
||||||
|
aliases: []
|
||||||
|
title: Project Management for Construction Estimating
|
||||||
|
tags:
|
||||||
|
- authorship/original
|
||||||
|
- destiny/permanent
|
||||||
|
- status/incomplete
|
||||||
|
- topic/construction
|
||||||
|
- topic/estimating
|
||||||
|
- topic/organization
|
||||||
|
- type/cross-topic
|
||||||
|
---
|
||||||
|
# Project Management for Construction Estimating
|
||||||
|
|
||||||
|
Cross-topic of [[project-management]] and [[construction-estimating]].
|
||||||
|
|
||||||
|
%%
|
||||||
|
|
||||||
|
## TALK
|
||||||
|
|
||||||
|
This note concerns optimal organization
|
||||||
|
for construction estimating
|
||||||
|
|
||||||
|
%%
|
||||||
+26
-12
@@ -1,35 +1,49 @@
|
|||||||
---
|
---
|
||||||
id:
|
id:
|
||||||
aliases: []
|
aliases: []
|
||||||
|
title: Project Management™
|
||||||
tags:
|
tags:
|
||||||
- authorship/original
|
- authorship/original
|
||||||
- destiny/permanent
|
- destiny/permanent
|
||||||
- status/draft
|
- status/draft
|
||||||
- topic/organization
|
- topic/organization
|
||||||
- type/philosophy
|
- type/philosophy
|
||||||
title: Project Management™
|
|
||||||
---
|
---
|
||||||
# Project Management™
|
# Project Management™
|
||||||
|
|
||||||
[[this-notebook]] assumes the reader is more familiar with the construction industry
|
%%
|
||||||
than with any of the other disciplines introduced.
|
|
||||||
As such, "project management" usually refers to _construction_ project management,
|
|
||||||
or more generally to a layman understanding of the term:
|
|
||||||
roughly, "the organizational processes necessary to complete a long-term goal".
|
|
||||||
|
|
||||||
Where I am referring specifically to the discipline,
|
## TALK
|
||||||
as documented by the [Project Management Institute](htpps://pmi.org),
|
|
||||||
I've opted to humorously style the term as Project Management™ for clarity.
|
|
||||||
|
|
||||||
## The Problem with Project Management™
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
%%
|
||||||
|
|
||||||
|
This note is distinguished from [[project-management]]
|
||||||
|
by referring specifically to doctrine/curriculum,
|
||||||
|
especially as documented by [The Project Management Institute](htpps://pmi.org).
|
||||||
|
I've opted to humorously style this concept as Project Management™ for clarity.
|
||||||
|
That is, "Project management" could never be wrong or even misguided,
|
||||||
|
but Project Management™ can (and often is).
|
||||||
|
|
||||||
|
This note may include generic criticism,
|
||||||
|
but discussion of the applicability (or lack thereof)
|
||||||
|
of Project Management™ to construction specifically
|
||||||
|
|
||||||
|
## Criticism
|
||||||
|
|
||||||
The term "Project Management" is deliberately vague,
|
The term "Project Management" is deliberately vague,
|
||||||
in the hope that generalizing the terminology
|
in the hope that generalizing the terminology
|
||||||
maximizes its applicability across industries.
|
maximizes its applicability across industries.
|
||||||
|
|
||||||
There are many core Project Management™ ideas that have no parallel in construction,
|
There are many core Project Management™ ideas
|
||||||
and there are as many or more critical construction project management problems
|
that have no parallel in other industries,
|
||||||
|
and industries often have problems of project management
|
||||||
that Project Management™ doctrine has no good solutions for.
|
that Project Management™ doctrine has no good solutions for.
|
||||||
|
See [[project-management-tm-for-construction]] for examples.
|
||||||
|
|
||||||
I would posit that, despite its cross-discipline language,
|
I would posit that, despite its cross-discipline language,
|
||||||
Project Management™ practice is only _universally_ applicable
|
Project Management™ practice is only _universally_ applicable
|
||||||
|
|||||||
@@ -0,0 +1,26 @@
|
|||||||
|
---
|
||||||
|
id:
|
||||||
|
aliases: []
|
||||||
|
title: Project Management
|
||||||
|
tags:
|
||||||
|
- authorship/original
|
||||||
|
- destiny/permanent
|
||||||
|
- status/incomplete
|
||||||
|
- topic/organization
|
||||||
|
---
|
||||||
|
# Project Management
|
||||||
|
|
||||||
|
[[this-notebook]] assumes the reader is more familiar with the construction industry
|
||||||
|
than with any of the other disciplines introduced.
|
||||||
|
As such, "project management" usually refers to _construction_ project management.
|
||||||
|
|
||||||
|
This note refers more generally to a layman understanding of the term:
|
||||||
|
roughly, "the organizational processes necessary to complete a long-term goal".
|
||||||
|
This note is not concerned with any particular implementation
|
||||||
|
of project management processes (See [[project-management-tm]]),
|
||||||
|
only the end goals of optimal organization.
|
||||||
|
That is, "project management" could never be wrong or even misguided.
|
||||||
|
|
||||||
|
See cross-topics for industry specific project management concerns and practices.
|
||||||
|
Notably [[project-management-for-construction]]
|
||||||
|
and [[project-management-for-construction-estimating]].
|
||||||
Reference in New Issue
Block a user