Tender overview
Nine steps from the consultant's drawing to a priced alternative. The tool tabulates and flags; the engineer decides and signs off.
Drawing
Upload the plotted tender drawing. Cap outlines are colour-coded in the PDF's vector layer, so detection is deterministic — no OCR guessing about which pile is which.
The drawing carries its own PILE AND PILECAP SCHEDULE as real text. Every run is checked against it. A mismatch never passes silently — it goes to the review queue.
Verify caps
Click a row to fly the drawing to that cap. Geometry and pile type come from the vector layer and are exact; the column marking is the one field that needed reading, so that is the field to check.
Column loads
Key in DL and LL per row, or import the consultant's loading schedule and join it on gridline plus column marking. Efficiency updates as you type.
Boreholes
The SPT profile drives the pile length solve. Edit an N value and every pile assigned to that borehole re-solves.
The workbook writes this as fs×As + fb×Ab / F.O.S, which is ambiguous. The form above applies each factor of safety separately, which is what two quoted FOS values imply — confirm before production, it moves every pile length.
Pile library
The catalogue the alternative design draws from. Edit a working load and every row re-checks.
Alternative design
Pick a pile type and key in platform level and cut-off. Pile length solves from the borehole; boring length, rock socket and efficiency follow. Anything typed by hand is kept and marked as an override.
Reinforcement
Cage is built in three segments of up to 12 m. Bars are adopted from the required area then checked against the minimum cage count. Links run one spec for the first 12 m and another below.
Quantities
What the alternative costs against what the consultant specified. This is the number the tender turns on.
Export & audit
The workbook goes out in the house format with live formulas, not baked values, so the engineer can still interrogate every cell.
Export is gated on engineer sign-off. The tool tabulates and flags; it never approves.
Every export is logged — who, which screen, format, scope, row count, time. In production this is written server-side, not in the browser.
The client's manual summary was built on R0. R1 added six 600 mm piles under the fuel, sprinkler and CW tank slabs — all inside revision clouds, all missing from the hand-tabulated sheet.
Client BQ → Excel
The consultant issues the BQ as a locked PDF. This reads it page by page — every bill, every line, in the same column positions the QS printed them — and writes the priceable workbook in the house format, with the cost / margin / selling columns already wired.