vault backup: 2025-07-24 16:44:33
This commit is contained in:
@@ -1,9 +1,10 @@
|
||||
---
|
||||
id: risk-oriented-estimating
|
||||
aliases: []
|
||||
tags: []
|
||||
tags:
|
||||
- estimating
|
||||
- risk
|
||||
---
|
||||
|
||||
# Risk Oriented Estimating
|
||||
|
||||
Risk-Oriented Estimating (ROE), is a methodology for [[construction-estimating]] which
|
||||
@@ -19,6 +20,7 @@ as these ultimately _increase_ risk by inflating the apparent project cost,
|
||||
increasing the probability of loss to a competitor.
|
||||
|
||||
%%
|
||||
|
||||
## Scratch
|
||||
|
||||
Bid risk may fit a [Taleb distribution](https://en.wikipedia.org/wiki/Taleb_distribution).
|
||||
@@ -42,6 +44,7 @@ given an organization's [[risk#Risk Tolerance]].
|
||||
## EVPI Takeoff
|
||||
|
||||
%%
|
||||
|
||||
## Scratch
|
||||
|
||||
Expected value of perfect information (EVPI)
|
||||
@@ -51,8 +54,8 @@ Count-based takeoff speed increases with count.
|
||||
|
||||
Optimizing the takeoff process means:
|
||||
|
||||
* *Minimizing* the need for information outside of drawings
|
||||
* *Maximizing* organizational consistency
|
||||
* _Minimizing_ the need for information outside of drawings
|
||||
* _Maximizing_ organizational consistency
|
||||
|
||||
> [!note]
|
||||
> Recent events have complicated my philosophy above.
|
||||
@@ -61,4 +64,4 @@ Optimizing the takeoff process means:
|
||||
|
||||
> [!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*.
|
||||
> but has the side effect that those accustomed to the names will inevitably _treat them as descriptive_.
|
||||
|
||||
Reference in New Issue
Block a user