Procurement Tracker (engine)
The Procurement Tracker engine is the extraction step that turns a schedule of values, bill of materials, bid leveling export or procurement log into structured procurement items. Each item gets a description, quantity, unit, committed amount, ETA and status, plus a vendor and PO number where known, and is imported into the Procurement Tracker workspace.
What does the Procurement Tracker engine do?
Procurement Tracker (engine) reads a procurement source document — SOV, BOM, bid leveling export, or existing procurement log — and extracts each item as a structured record: description, qty, unit, assigned vendor (if known), PO number (if issued), committed amount, actual ETA, and current status. Output imports to the Procurement Tracker workspace, where you manage items through delivery.
What do I upload to the Procurement Tracker engine?
Upload a schedule of values, a bill of materials or an existing procurement log, or chain in a Bid Leveling export, which carries its data forward.
- Schedule of values
- Bill of materials
- Bid Leveling export (chain from Bid Leveling — data carries forward)
- Existing procurement log
How do I run the Procurement Tracker engine?
To run the Procurement Tracker engine, open it, upload the source, run it, review the extracted items and assign vendors, then import them to the tracker.
Open the engine
Sidebar → Engines → Procurement Tracker.
Upload source
SOV, BOM, log, or chain from Bid Leveling.
Run
20–40 seconds.
Review + assign
Each row as editable. Link items to vendors if not already assigned.
Import to tracker
Merges by description + qty if items already exist.
How do I read the Procurement Tracker engine results?
The result is a procurement item table with a list of unassigned items and a budget summary.
Description, qty, unit, vendor, PO, committed amount, ETA, status.
Separate section for items without a vendor. Assign from the Vendor Database before importing to tracker.
Total committed, uncommitted, over/under budget.
Every control, explained
Run analysisOne run.
Assign vendorPick from vendor database or create new.
Link to submittalCross-reference a procurement item to its submittal tracker entry.
Import to Procurement TrackerPush to tracker.
Export PDFProcurement log report.
Export XLSXRaw table.
Chains
Chains into
Chained from
Exports
- PDF — procurement log.
- XLSX — raw table.
- CSV — flat list.
Troubleshooting
SOV line "Electrical package" is too coarse to track separately from "Switchgear" — provide a more granular source, or edit rows before import.