The ELV take-off workstation.
One place to read the drawings, check what the system found, build the quantities and release them to pricing — with the evidence attached at every step.
Click a quantity. The places it came from appear.
A priced line is not the end of the trail — it is the top of it. Open any line and the drawing locations behind it are listed, one by one, each with the device tag, the sheet and the grid reference an engineer would use to go and check it.
This is the difference between a number you accept and a number you can defend. Try it — the bill below is live.
- Source
- BOQ line 04.10.021
- Decision
- Open the evidence behind the quantity
- Result
- Four locations on E-L02-ELV-001
- CCTV-001: External WP camera — Verified — grid A/1
- CCTV-002: External WP camera — Verified — grid B/1
- CCTV-003: External WP camera — Verified — grid C/1
- CCTV-004: External WP camera — Verified — grid D/1
- CCTV-041: Lift car camera — grid C/3
- CCTV-042: Lift car camera — grid C/3
- ACS-CR-01: Proximity reader, door 02-04 — grid A/1
- ACS-CR-02: Proximity reader, door 02-06 — grid B/1
- ACS-CR-03: Proximity reader, door 02-08 — grid C/1
- ACS-CR-04: Proximity reader, door 02-10 — grid D/1
- ACS-CR-05: Proximity reader, door 02-11 — grid B/2
- BGM-SP-01: Ceiling loudspeaker, 6W — grid A/2
- BGM-SP-02: Ceiling loudspeaker, 6W — grid C/2
- BGM-SP-03: Ceiling loudspeaker, 6W — grid D/2
Evidence 01 / 04CCTV-001External WP camera
A tender is a package, not a page.
- Source
- A 187-sheet package
- Decision
- Navigate by system, level and revision
- Result
- The sheet you need, at the zoom you need
Move through the set the way you would at a desk with the drawings spread out — by system, by level, by revision. Layers separate so services read against architecture instead of on top of it. Sheets cross-reference, so following a riser from level 02 to the head-end does not mean losing your place.
Four actions, and the machine is never the last word.
- Source
- A machine observation
- Decision
- Confirm · reject · reclassify · add
- Result
- An observation an engineer owns
Confirm an observation, reject it, reclassify it as the device it actually is, or add the one that was missed. Every action is attributed and timed. Corrections are not discarded once applied — they are how the system learns what a symbol means on this project, and they remain part of the record for anyone auditing the takeoff later.
Deterministic rules, not a second opinion.
- Source
- Verified observations
- Decision
- Engineering rules, versioned and inspectable
- Result
- A quantity with its derivation attached
Quantities are produced by engineering rules that are versioned, inspectable and repeatable: a controlled door yields its five devices, outlets aggregate into ports and patch panels, coverage sets speaker counts, a lane width selects a boom. Run the same rules on the same verified observations and you get the same numbers — which is what makes the output auditable rather than merely plausible.
Only approved quantities reach pricing.
- Source
- Verified quantities
- Decision
- Approved for pricing, by a named engineer
- Result
- A BOQ line that opens backwards
Approval is a deliberate act by someone with the right to make it, not a side effect of finishing. Unverified observations and open QA queries cannot cross into the priced bill. What reaches the estimator is a set of quantities that a named engineer released, on a stated revision — and every one of them still opens backwards.
Every number should have a reason.
Five steps, and the same three parts underneath all of them: a source you can point at, a decision someone made, and a result that carries both with it. Nothing in this workstation produces a quantity that cannot answer where it came from.
That is not a feature list. It is the reason an engineer can put their name on the output — which is the only thing that makes a take-off worth anything at tender review.