vault backup: 2026-01-07 17:01:31

This commit is contained in:
2026-01-07 17:01:31 -05:00
parent 97dd06e296
commit c276d4adf3
21 changed files with 10539 additions and 125 deletions
+32
View File
@@ -0,0 +1,32 @@
---
id:
aliases: []
title: Location vs. Scope
tags: []
---
# Location vs. Scope
A detailed breakdown being a necessity of a quality estimate,
it is important to consider what one means
when they say that some portion of the installation is _in_ some place.
![[location-vs-scope.excalidraw]]
MDPB is physically _located_ in Building A,
but serves only loads in Building B.
If a customer requests a cost breakdown by building,
under which building would you put MDPB?
Were Building B removed from the contract scope,
it can be expected that MDPB would be as well.
Were Building A removed from the contract scope,
it can be expected that MDPB would be relocated.
Therefore if the customer requests a cost breakdown by _building_,
it would be confusing to do so along location.
That is, to include MDPB and its feeders in the price for Building A.
```
Panel_MDPB.Location = Buildings["Building A"]
Panel_MDPB.Scope = Buildings["Building B"]
```