50 lines
1.1 KiB
Markdown
50 lines
1.1 KiB
Markdown
---
|
|
id:
|
|
aliases: []
|
|
tags:
|
|
- automation
|
|
- estimating
|
|
- software
|
|
- type/idea
|
|
---
|
|
# Separating Estimating Concerns
|
|
|
|
## 1. Annotation
|
|
|
|
Annotation is documenting project scope as intended by its design.
|
|
This involves reconciling missing and conflicting requirements,
|
|
as well as erroneous and misplaced symbols.
|
|
|
|
This process is intended to be *unbiased*, without respect for
|
|
* industry knowledge
|
|
* contractor standard practices
|
|
|
|
The annotator is to describe the design scope
|
|
without adding any outside information.
|
|
|
|
### Output
|
|
|
|
The processes and tools for completing this step
|
|
would differ between design-build and plans-and-specs projects,
|
|
but the output would be identical in function.
|
|
|
|
This step encodes "measures" with "tags"
|
|
and describes the behavior of special tags
|
|
(e.g. structure height of each `Level`)
|
|
|
|
## ~~next step(s)~~
|
|
|
|
Define takeoff given counts from step 1.
|
|
|
|
```
|
|
LET wiring-devices 'default/wiring-devices/decora'
|
|
|
|
FOREACH MEASURE
|
|
WHERE 'type' IS 'device/receptacle/duplex' AND 'mounting' IS 'flush'
|
|
TAKEOFF 'DUPLEX REC - FLUSH IN METAL STUDS' FROM wiring-devices
|
|
```
|
|
|
|
## -1. Reporting
|
|
|
|
Build deliverables (proposals, BOM's)
|