vault backup: 2025-07-28 17:12:58

risk-oriented-estimating.md

@@ -11,7 +11,7 @@ Risk-Oriented Estimating (ROE), is a methodology for [[construction-estimating]]
 * prioritizes estimating tasks,
 * determines necessary [[estimating-detail]]
 
-ROE leans heavily on [[perfect-information]],
+ROE leans heavily on [[uncertainty#Value of Information]],
 which challenges the natural tendency to shy from uncertainty
 with the reality of the cost of certainty.
 
@@ -41,16 +41,17 @@ ROE prioritizes estimating tasks by their contribution to _cost certainty_.
 ROE determines the appropriate level of [[estimating-detail]]
 given an organization's [[risk#Risk Tolerance]].
 
-## EVPI Takeoff
+### EVI Takeoff
 
-%%
+Expected value of information (EVI)
 
-## Scratch
+### Takeoff Optimization
 
-Expected value of perfect information (EVPI)
+For systems where EVI analysis determines manual takeoff is still necessary,
+optimizations can be made to decrease the required effort of takeoff,
+and thus the opportunity cost of takeoff.
 
 Count-based takeoff speed increases with count.
-%%
 
 Optimizing the takeoff process means:
 
@@ -62,6 +63,13 @@ Optimizing the takeoff process means:
 > It appears that similar efforts have already been made here,
 > their success being a matter of perspective.
 
-> [!note] Naming Conventions (Use Case vs. Description)
-> Naming by use case is intuitive for those without estimating or field experience,
-> but has the side effect that those accustomed to the names will inevitably _treat them as descriptive_.
+#### Naming Conventions (Use Case vs. Description)
+
+Naming by use case is intuitive for those without estimating or field experience,
+but has the side effect that those accustomed to the names
+will inevitably _treat them as descriptive_.
+
+| Use Case            | Description   |
+| ------------------- | ------------- |
+| Hi-Hat              | Daisy-Chain   |
+| Furnished By Others | Rough-In Only |