Quoting assemblies and kits from the STEP tree and the parts list
VenturusEQ reads a STEP assembly into a tree with quantities per parent, creates a quote line for each component, and rolls the costs up recursively. Purchased parts come from your price list or from a vendor quote captured on the line, and any component that could not be costed is named with the cause rather than rolled up as zero.
How an assembly gets quoted today
An assembly RFQ is a STEP of the whole thing, a stack of part drawings, a parts list in Excel that disagrees with the model, and a request for one price per kit at three quantities. The estimator builds a spreadsheet with a row per part, types the quantities by hand, and prices the machined parts one at a time.
The hardware and the purchased parts get a guess or an email to a distributor. Sub-assemblies are hidden inside sub-assemblies. When the customer changes one bracket, the whole sheet is checked line by line for what the change touched, and something is always missed.
The judgment about make-or-buy, fixturing and assembly hours stays the estimator's. Counting components, carrying quantities through three levels and keeping the sum honest is arithmetic VenturusEQ does in the open.
What VenturusEQ does with the tree, the parts list and the roll-up
The STEP tree read with quantities per parent
A STEP assembly is read into components with quantities per parent, up to 25 levels and 2,000 nodes, with a note when a tree is truncated. The reader runs inside the product; nothing leaves the container.
Quote lines created from the tree
Assembly children, package files and parts-list rows become quote lines, pre-ticked and editable, quantities carried, part numbers reconciled against the title block. Running line creation twice does not duplicate lines.
A recursive roll-up
Costs roll up through the tree with every bucket kept separate. Un-costed nodes are disclosed with the cause. The roll-up is recomputed each time you open it, so it is never stale.
Purchased parts priced with their source recorded
A purchased-part template prices hardware from your material price list. A sourcing request captures any vendor price with currency, exchange rate and lead days, and the one you select lands in the bill with its source.
The parts list read into rows
An Excel parts list becomes component rows with blank quantities left blank rather than guessed. A block pasted from a spreadsheet becomes up to 500 lines, header-aware and all-or-nothing.
Each body in the viewer linked to its bill row
The 3D viewer bridges each body to its bill-of-materials row. Isolate, explode, snap views and native colors show what a quantity of twelve looks like before you price it.
How a STEP assembly becomes a kit price
The package lands
The STEP, the drawings and the Excel parts list are hashed, given roles and paired. The package brief says what is covered, what is missing and proposes the bill.
The tree is read
Components and quantities per parent come out of the STEP. Drawings are paired with their components by evidence: bound files, read title blocks, dash variants, names and folders.
Lines are created
One line per component with quantity carried. Each line opens its own eight-tab part workspace: overview, method, materials and bill, pricing, geometry, compliance, sourcing and manual roll-up.
Each component is costed
Made parts go through the read, the measurement and the two cost lines like any other line. Purchased parts take a price list row or a vendor quote. Every value is confirmed before it prices.
The roll-up is checked
The tree is rolled up recursively. Un-costed nodes are listed with the cause, and a whole-set charge such as final inspection or a fixture is costed once across the kit.
Levels and margin are set, and the quote is sent
Lines can be grouped into quote levels with their own status. Margin or markup is applied with per-line override, then the digital quote goes out from your own mailbox where that is switched on.
Common questions
What if a component cannot be costed?
It is disclosed. The roll-up lists every un-costed node with the cause, such as a missing template or an unconfirmed input, instead of rolling it up as zero, so you see the gap before your customer does.
How do purchased parts and hardware get priced?
A purchased-part template prices them from your material price list, or you fire a sourcing request from the line and capture a vendor price with its currency, exchange rate and lead days. The selected price lands in the subcontract or material bucket with its source.
The customer's parts list does not match the STEP tree. Which one wins?
Neither, until a person picks. Rows from the Excel parts list, the package files and the STEP children are all offered as candidate lines, pre-ticked and editable, with quantities carried and part numbers reconciled against the title block. A block pasted from any spreadsheet can also become up to 500 lines in one go.
See one of your own assemblies rolled up in VenturusEQ
Bring a STEP assembly and its parts list. We create the lines, price the purchased parts and roll the kit up in your rates, live. If you would rather look first, the interactive demo is open, with no form in front of it.