How Darwin Works

Abstract

Construction estimation often breaks down due to redundant data entry, outdated price references, and fragmented document handling. Darwin introduces a modular framework combining reusable cost blocks, dynamic price lists, and collaborative workflows. The result is rapid, precise, and auditable estimations that scale across teams and projects.

1. The Core Idea: Eliminating Redundancy

Traditional workflows force estimators to repeatedly define elements, retype supplier prices, and attach documents in separate systems. Darwin resolves this by:

• Defining construction knowledge once (modules).
• Anchoring estimates to time-stamped price lists.
• Managing documents directly inside each project context.

2. Modules as Knowledge Blocks

Modules capture the complete cost structure of an element:

• Materials (quantity x price)
• Labor (hours x rate)
• Expenses (transport, insurance, overheads)

Modules are reusable across projects. Once validated, they become the company’s Cost DNA and can be applied instantly with only price updates.

3. Price Lists as Temporal Anchors

Darwin separates logic (modules) from market conditions (prices).

• Price Lists store material, labor, and logistics values at a given moment.
• Projects can be recalculated with new lists without redefining modules.

This ensures historical estimates remain reproducible while future ones reflect current conditions.

4. Design Integration as Input

Darwin can parse IFC BIM files to extract elements and map them into modules. This acts as a fast input channel into the cost engine, reducing manual entry while preserving estimator control.

5. Estimation Formula

6. Collaboration as a First-Class Citizen

Darwin is not a single-user tool. Teams can:

• Draft estimates and request price review.
• Assign roles such as approvers, reviewers, and contributors.
• Track modifications with time-stamped histories.

Collaboration ensures estimates are technically correct and organizationally accountable.

7. Projects as Organized Repositories

Every estimate lives inside a Project container. Projects can store:

• Estimates and revisions
• IFC design files
• Supplier and client documents
• Contracts, drawings, and correspondence

This keeps knowledge preserved and accessible in context, rather than scattered across emails or drives.