Coverage and Lead Times

The worst procurement news arrives on its own schedule: a sixteen-week part you needed to order a month ago. The Coverage view exists so that news comes from your own screen, early, instead of from a vendor, late.

What Coverage shows

Open Procurement under Build in the project rail. Coverage derives demand straight from the Equipment Register: install quantity plus spares for every part, totaled across the whole job. A part shared across phases reads the same honest total on every row it appears on, never a per-panel guess.

Each item carries a status (Released for purchase, Not ordered, Partially received, On site), a coverage bar showing units received against units needed, and the submittal that covers it. Filter chips and search flatten the tree to exactly the rows you're chasing.

Need-by and order-by

Every item resolves a need-by date from a simple ladder: its own entered need-by if you set one, otherwise the Fabrication Start milestone scoped to the group that contains it, otherwise Materials on Site. Dates you maintain once on the schedule flow to every part they govern.

Order-by is that need-by minus the part's lead time. The lead time comes from an active quoted price if one carries it, otherwise from the median of your own actual receiving history for that part, otherwise from the distributor lead time for the part. The column names which one it used. When the distributor had enough stock to cover what is left to order, the row says the part is in stock and has no order-by date. When an order-by date is within two weeks, the row shows an ORDER BY warning; when a vendor's promised date slips past the need-by for a part still short of site coverage, it shows Late.

The dashboard's attention items run on exactly the same rules, so the dashboard and the Coverage view can never disagree about which part is in trouble.

The order list

Coverage answers per item; the Order list view answers per part. Each part the Register uses gets one row, summed across every panel: how many are needed (install plus spares), how many are on purchase orders, how many have been received, and how many are still to order. The PO numbers carrying the part are listed beside it, and clicking one opens that purchase order.

Parts with something left to order sort to the top, so the last few items, like airflow stations you order once the duct is measured, stay in front of you after everything else is bought. The chips narrow the list to To order, On order, or Received.

Download .xlsx saves the rows you are looking at. Pick To order first and the download is the list to hand to purchasing, with a blank PO number column to fill in.

Export the MOF

The material order form goes to whoever cuts the POs.

1. Click Export MOF in the Procurement header.
2. Choose the whole register or a single group.
3. The export builds in the background with live progress; you can keep working, or press Stop if you picked the wrong scope. Stopping isn't a failure, and you can export again anytime.
4. When it's ready, download the MOF ZIP. It holds the workbook and a copy of each linked quote. A quote file that could not be fetched is named in Quotes/Missing quotes.txt instead.

No need-by date on a row usually means the milestone it resolves to hasn't been given a target date yet. Date the milestone once and every part under it gets its order-by math.