---
id:
aliases: []
tags:
  - destiny/fleeting
  - topic/estimating
  - type/philosophy
title: Assembly Philosophy
dg-publish: true
---
# Assembly Philosophy

also "Modularization"

## Assemblies

In [[construction-estimating-software]],
assemblies are groups of material items
representing a specific scope of work.

Assemblies reduce the effort required for takeoff
by grouping related items,
for example 3/4" EMT connectors and couplings
in addition to conduit.

Assemblies allow... (in order of necessity):

1. complex items (devices, conduit runs, etc.) with known proportions to be counted as one.
2. changes to be made to measures and counts without recounting an entire area.
3. takeoffs to be skimmed for obvious deficiencies that would otherwise be obscured
4. changes to be made to project requirements (specifications) without recounting an entire area.

If we agree on the definition of `Branch Wiring: 2#12 #12G; 3/4"C, EMT; On Structure`
and its contents as ratios of its length,
then their quantities can be calculated with only one measurement.

This is how "estimating software" assembly takeoff works,
however its a simple generic process,
possible with several tools an estimator should be familiar with:

* `XLOOKUP()` - Excel
* `Table.Join` - MS Power Query
* `JOIN` - SQL

## Abstract Assemblies

Assembly _philosophy_ is essentially minimizing the number of necessary counts and measurements.
More generally, it is minimizing the effort required for measurement.

> [!info] Abstractions
> An abstraction is a model that intentionally ignores details
> that are irrelevant to problem it is used to solve

As useful a concept as assemblies are,
the same concept can be applied as a test of potential efficiency gains
in areas other than material takeoff.

Assembly philosophy as applied to coordination
is minimizing redundant memorization among participants.
In an ideal work breakdown,
every estimator would be totally ignorant of the requirements of others' scopes,
thus allowing them to understand their own as well as possible.
In practice there is some overlap where scopes meet

* Eliminate redundant measurements
* Minimize redundant responsibility