Skip to main content
PlanRelevé Wiki

Assemblies and bill of materials

The bill of materials (BOM) links a symbol class to a parts recipe. PlanRelevé includes 101 built-in symbols, 101 library assemblies and a shared catalog of 10,655 bilingual parts; the runtime also retains 30 embedded fallback recipes. Your recipes and prices can override them without changing the common library.

Access, path and counted data

Path: project → Dashboard, the Bill of materials (BOM) section to read it; project → Estimate → Edit recipes to change it. There is no longer a "Legend and BOM" page: classes are created in the Legend symbols (B) tool on Plan review, and their recipes are edited on the estimate page. A viewer may inspect; an editor or project administrator creates classes and changes recipes. See Symbols and manual placement to create a class from a legend scan, plan box or icon.

The BOM uses only confirmed and manual detections on active sheets. Candidates and ignored items never enter materials or the estimate; the estimate always shows how many detections are still waiting for review. A disabled sheet is excluded. Review statuses before pricing in Review and quality.

The "BOM recipe" editor opened from the estimate: a class's parts, quantities, costs and hours.
The "BOM recipe" editor opened from the estimate: a class's parts, quantities, costs and hours.

Create or correct a recipe

  1. Confirm the class name, description and unit. Renaming a class also moves its detections and its project recipes, variants included; if a different recipe already exists under the new name, the rename is refused rather than silently changing a price.
  2. On the Estimate page, select Edit recipes, or click the class chip on a BOM line. A class with no recipe is valid, but contributes no lines.
  3. Add each part with a strictly positive quantity and a unit. In Part #, type a number or a name and pick a catalog part: its number, names and unit are copied in. A number that is in no catalog can be created in the project ("+ Create part … in the catalog") or simply kept as typed, all the way to price requests.
  4. Leave Unit cost or Labor (h) blank to follow the catalog — and supplier quotes for the price; the catalog value shows greyed in the field. A typed value is fixed in the recipe for that line. An older line whose price was copied in stays fixed and says so on hover; clear the field to make it follow the catalog again.
  5. Save keeps the recipe at the project tier, as a local exception. Publish to organization makes it the recipe for that class in every authorized project.
  6. Open the dashboard or estimate and verify the aggregated quantity, material cost and labour hours.

Three-tier precedence

Resolution always follows project → organization → shared library. This applies to recipes and referenced parts. A project recipe, even an empty one, blocks lower tiers. The imported library covers 101 classes; the runtime also keeps 30 embedded recipes that can seed the editor when the shared library is not yet imported or a matching recipe is absent.

Each class count multiplies every recipe quantity. Lines for the same part — same number, or same name when there is no number — in the same unit consolidate; their source classes remain visible and the part number shows next to the name. A part priced in one recipe and unpriced in another stays on two lines instead of producing a misleading average price. Hiding a shared part removes it from lists and pickers, but a recipe that still names its number continues to resolve and price it.

Attribute variants and surfaces

Three assembly names carry a special meaning:

  • class::wattage_w=1000 prices an attribute value with its own parts and hours. Without a variant, each confirmed value inherits the class recipe but still forms its own bill-of-materials line. See Attributes.
  • class::area prices a surface per square foot. The net area of a zone, voids deducted, then feeds the bill of materials with its provenance. When a symbol class has the same name as the zone, only this form prices the zone: the symbol's per-device recipe is never applied per square foot.
  • class::linear_ft prices a linear class (baseboards, wall convectors) per foot of measured bar. Without it, the lines in feet (ft, pi) of the class recipe are priced once on that footage — marked per ft of bar, never per fixture nor again on a variant — and the other lines stay per device. Check per fixture for a length per fixture; a line above 2 ft per foot of bar is flagged in the editor, the BOM, the PDF and the workbook.

A valid supplier quote price applies on top of the catalog without changing the recipe, on any line that follows the catalog: the line then carries the matching badge. A quote refused because its unit differs from the part's unit is flagged on its line.

Missing prices, limits and recovery

A line without cost remains visible with a missing cost; PlanRelevé does not invent a price. Blank hours likewise mean no labour value for that line. Correct the part at the appropriate catalog tier, or enter a recipe-specific value.

If the BOM is empty, check in this order: active sheets, confirmed/manual statuses, exact class-name match, non-empty recipe and positive quantities. Counted classes with no recipe are named on the estimate page, and each name opens its recipe. If an incorrect override persists, Reset to default deletes the project recipe to reveal the organization or shared value; Remove organization recipe or Revert to default recipe does the same at the organization tier. Then generate a new deliverable from Exports; an earlier export remains a snapshot.

See also