metriqone real federation, measured end to end
Upload a Navisworks NWD, choose what belongs in the bid, and download a line-based MTO in your client’s own schema.
Sign-in required for the platform. No account needed to read this page.
Why take-offs go wrong
A federation stacks source models on top of each other — superseded revisions, duplicated geometry, the same run delivered by two disciplines. Walked by hand, every copy reads as new material.
Measuring a large model manually takes days, and those days run inside the tender window, not after it.
Procurement cannot buy from one number. They need the quantity split by code, nominal size and material — which is also how your client’s schema is laid out.
Three steps
Drag the NWD in — up to 300 MB, straight from your browser to processing.
~20 min for a 210 MB federation · you can close the tab
Every source model in the federation is listed with its own quantities. Tick what belongs in the bid; the screen, the Excel and the PDF all follow.
under 2 minutes
Excel workbook and evidence report, in your client’s schema.
immediate
End to end, that is about 40 minutes on the largest federation we have run.
Deliverables
Summary, Heading Breakdown, MTO, Fitting Breakdown, Steel, Valves, Material Summary, Material Detail, Unknown Items, Method. Sheets appear when the model carries the data for them. Editable, in your client’s column order.
A printable pack behind the totals: diameter breakdown, fitting breakdown by code and size, what was excluded and why, and the method used. Hand it to your client with the bid.
Include or exclude any source model in the federation with one tick. One decision, applied to the screen, the workbook and the report at the same time.
Quantities split by material where the model publishes it — carbon, stainless, and the rest — so procurement can price directly from the sheet.
Click any row in the take-off and see the exact objects behind it, isolated in the model. Every quantity is traceable to geometry. Available on cloud-processed models.
Ask in plain English — “how much 4-inch pipe on the CIP lines?” The answer is executed against the take-off rows, not generated.
One real federation · anonymised
Five things happened between the upload and the number. Here is all of them.
A single federation lands on the desk. One file, every discipline, 210 MB. Somewhere inside it is every metre of pipe you are about to price.
1,300,000objects in one federation
The same runs are in there twice — a superseded revision here, geometry delivered by two disciplines there. The copies sit exactly on top of each other, so the model looks perfectly normal.
The eye cannot see it. The bid pays for it.
Every object is fingerprinted before it is measured. Byte-identical copies across source models collapse to one. Nothing is estimated, nothing is thrown away — the same pipe is simply bought once.
82,200duplicate objects counted once
7,104mof phantom pipe that never reached your bid
The full model is not the tender. Tick the source models that belong in the bid and the total moves with them — on screen, in the workbook and in the report at the same moment.
20,37610,692mfull model, then tendered scope
Open any line and the objects behind it light up in the model. Row, source model, geometry — the chain never breaks, so your client can check the same line you did.
Every row → its source model → the objects behind it.
Numbers come from a deterministic engine. AI never writes a quantity.
Client, project and file identifiers are never published. Anonymised figures only.
Pricing
£300 a month — £200 for the platform, £100 for the support and the engineering time that comes with it. No card on this page; every plan starts with a conversation.
Metriq
★ EVERYTHING INCLUDED£300/ month
£200 platform+£100 support & engineering
Unlimited users, 15 models a month, and the take-off comes out in your client’s schema — not ours.
What the £100 buys
16engineering hours a year
About half a day a quarter, spent on what you ask for — a new export, an extra column, a rule your client insists on. One pool: it also covers re-calibration and anything support cannot answer in a reply. Whatever we build stays in the platform and we keep maintaining it.
Six-month minimum term, then 30 days’ notice — the first month includes mirroring your template, which is two to four days of work on our side.
Engineering hours are scoped with you each quarter and reported monthly; unused hours do not carry over.
Need more volume? 25 models and 5 large federations a month — just ask.
Prices exclude VAT. Any VAT due is shown on the invoice.
Invoiced monthly, 30-day terms.
Before you ask
Four things worth knowing before the first model.
We read what the model publishes. A federation of plain meshes or dumb solids carries no sizes or classes, so it produces no take-off rows — we tell you that instead of estimating.
That is the current ceiling for a single NWD. Larger federations are split by discipline and measured as separate runs.
Your client’s conventions are not ours — whether 45° bends fold into 90s, whether collars count 1:1, whether companion flanges are in scope. We mirror your template, then it applies to every model after it.
Calibrating and scoring on the same file is not a measurement. Instead you get the evidence: every row, its source model, and the geometry behind it. Check any line you like.
Send one federation. You get the Excel, the evidence report, and a walkthrough of every difference against your own numbers.
We reply within one working day.
