BIM product configurator
Configure the building product. Deliver the information the project needs.
Configurix connects governed building-product rules, interactive 3D, project context, technical properties and commercial workflow. Architects, specifiers, contractors, dealers and manufacturers can continue from one accepted configuration into a controlled specification, BIM or CAD package, technical review and quote.
Building product project
South elevation · Entrance system
Product
Entrance system D-42
Configuration
CFG-B17 · rev 04
Classification
Mapped
Properties
18 required · 18 present
Files
RFA · IFC · PDF
Product rules
Accepted
Information
Validated
Project handoff
Connected
Valid product state
Dimensions, options and dependencies follow the approved catalogue model.
Structured information
Properties retain identifiers, definitions, units, sources and revisions.
Purpose-specific files
Each BIM, CAD or document output is scoped for a named recipient and use.
Connected project
Specification, technical review, quote and order share configuration identity.
Category definition
BIM configuration is an information workflow, not a file-format promise.
The terms are often mixed together. A useful procurement and implementation plan separates product configuration, BIM content, CAD automation, commercial workflow and project approval before deciding how they connect.
BIM product configurator
A guided application that lets a user select or configure a valid building product and creates a traceable information package for a defined project purpose. It can connect product rules, browser 3D, technical properties, classifications, documents and approved BIM or CAD derivatives.
It is not automatically a BIM authoring tool, engineering calculator or model-checking platform.
BIM object library
A governed collection of downloadable objects or families prepared for design applications. A library can be part of the journey, but a file catalogue alone does not evaluate product compatibility, capture continuous dimensions or preserve a commercial configuration revision.
The library governs released content; the configurator governs the accepted selection or state.
CAD product configurator
A broader category for rule-driven geometry, drawings, neutral exchange files or native CAD automation. BIM adds built-environment information requirements, object classification, project context, property semantics and exchange expectations beyond geometric output alone.
CAD geometry and BIM information can share a source model while remaining different deliverables.
Visual CPQ
A connected commercial experience combining valid product choices, interactive visualization, pricing, quotation and downstream handoff. It can receive or produce technical data, but commercial acceptance and BIM model acceptance are separate decisions with separate owners.
A priced configuration is not automatically a coordination-approved design object.
Interactive scope planner
Start with the product, the user and the required decision.
Choose a representative scenario. The planner exposes the minimum architecture and evidence needed before anyone promises a BIM download, specification package or connected commercial handoff.
Recommended acceptance boundary
One configuration identity. Purpose-specific outputs.
Keep continuous dimensions, option rules, engineering-review thresholds and configuration revision explicit. Generate or select technical content only inside the accepted solution space.
Prioritize selection guidance, project context, technical-property provenance, a concise specification record and a clear path to approved BIM or CAD content.
Define a structured property contract: identifiers, definitions, units, applicability, sources, classification, documents, intended use and revision.
Minimum proof
Validate a representative product from browser selection through saved state, property package, receiving tool and downstream project or commercial record. Record the source, configuration revision, generator version, file version and acceptance result.
Four connected journeys
The same building product has different users and evidence needs.
A strong configurator gives every participant the right next action without distributing disconnected copies of the product definition.
Role
Architect or specifier
Decision
Find a suitable product and obtain information that can be evaluated in a project.
Journey
Filter the product family → configure allowed choices → review properties and documents → request or download the approved information package → retain product and revision identity.
Acceptance evidence
The output states product, type or configuration, intended use, property sources, units, revision, status and file version.
Role
BIM manager or consultant
Decision
Confirm that exchanged geometry and information meet a documented requirement.
Journey
Review the required class, properties, units and geometry scope → receive a mapped file → validate it in the target workflow → report exceptions against the named requirement.
Acceptance evidence
The acceptance record identifies target format, schema or application version, information requirement, test model and validation result.
Role
Contractor or installer
Decision
Continue from a specified product into site validation, procurement and installation planning.
Journey
Open the shared configuration → confirm site dimensions and interfaces → request technical review → receive approved drawings or schedules → continue to quote, order and delivery.
Acceptance evidence
Site assumptions, outstanding checks, approved dimensions, product revision and downstream project identifiers remain visible.
Role
Manufacturer technical sales
Decision
Turn project interest into a valid commercial and technical opportunity without re-entering product data.
Journey
Receive project and configuration context → validate market and product rules → calculate the applicable price → issue a branded quote → request engineering review where the solution leaves the standard boundary.
Acceptance evidence
The quote and technical package reference the same configuration and revision, while their approval statuses stay separate.
Canonical information contract
Ten connected records make a BIM handoff traceable.
File generation is downstream of identity, rules and governed information. The contract makes each value explainable across the website, project, BIM workflow and commercial systems.
Product identity
Manufacturer, product family, model or system, stable ID and market availability.
Typical authority · PIM or governed product master
Configuration identity
Saved configuration ID, revision, rule version, status and timestamps.
Typical authority · Configurix
Project context
Project, location or market, building or zone, role, intended use and recipient.
Typical authority · Project system or Configurix journey
Geometry parameters
Approved units, overall and interface dimensions, orientation, host or placement assumptions.
Typical authority · Product rules plus approved geometry source
Selected product state
Options, modules, materials, finishes, accessories, dependencies and exclusions.
Typical authority · Configurix product model
Technical properties
Named properties, values, units, test or calculation basis, applicability and source revision.
Typical authority · Approved technical product data
Classification and semantics
Object class, classification references, property identifiers and dictionary versions where used.
Typical authority · BIM or information governance owner
Files and representations
File ID, format, schema or application version, detail scope, coordinates, status and checksum.
Typical authority · BIM, CAD or document repository
Commercial context
Price list, currency, tax, quote ID, validity and approval state where included.
Typical authority · Pricing service, CPQ or ERP
Review and release
Intended use, limitations, reviewer, decision, date, supersession and next action.
Typical authority · Named technical or project approver
Output architecture
One configured product can create several controlled deliverables.
Each output has a different purpose, recipient and acceptance test. Reusing authoritative identity and source parameters does not make the representations interchangeable.
Product selection summary
A human-readable record of the chosen product, dimensions, materials, options, project context and outstanding checks.
Use
Early specification, technical enquiry and sales continuation
Proof
Summary values reconcile with the saved structured configuration
Structured property package
Machine-readable product and configuration properties with stable identifiers, units, sources, applicability and revision context.
Use
Specification systems, data templates, schedules and integration
Proof
Required fields, semantics, units and allowed values validate against the agreed contract
Revit family or type
A governed RFA or type package designed for an agreed Revit version, category, parameters, visibility, geometry behavior and project use.
Use
Native Revit placement, schedules and documentation
Proof
Flex, placement, type or instance behavior, shared parameters and sample-project tests pass
IFC exchange
An IFC representation mapped to an agreed schema, object class, geometry, property and quantity scope for a defined exchange purpose.
Use
OpenBIM exchange, coordination or downstream model-based workflows
Proof
Export, import, class, property, unit, placement and target-tool validation pass
CAD and drawing package
DWG, DXF, STEP, PDF drawing or another approved derivative with the exact views, layers, dimensions and revision required by its recipient.
Use
Detailing, review, coordination, fabrication preparation or installation
Proof
Representative largest and boundary configurations reproduce the accepted dimensions and state
Commercial project package
Saved configuration, visual snapshot, price result, quote, project record and references to technical files without conflating commercial and technical approval.
Use
Lead, quote, dealer, CRM, ERP and order workflows
Proof
Every downstream record resolves the same product and configuration revision
System ownership
Do not make the configurator the accidental source of every fact.
Connected BIM and commercial workflows work when each system owns a deliberate record and exchanges stable identifiers, revisions and acknowledgements. The exact allocation is project-specific; ambiguity is not.
PIM
Product identity, descriptions, documents, market publishing and approved channel attributes
Parametric geometry behavior or every project-specific configuration
PLM and CAD
Released engineering definition, technical revisions, native models and approved derivatives
Customer journey, public content or commercial opportunity state
BIM content repository
Released Revit, IFC or related content, file versions, status and intended-use metadata
Live sales pricing or CRM ownership
Configurix
Allowed product choices, configuration identity, browser 3D state and structured journey handoff
Unapproved engineering truth, project coordination approval or every downstream record
CPQ or pricing service
Commercial price, discount, quote and approval policy for the applicable context
BIM class, geometry fidelity or technical-property approval
CRM, ERP or project system
Opportunity, customer, order, delivery or project process according to the agreed architecture
Interactive product rules unless explicitly assigned and synchronized
Capability boundaries
Six distinctions protect architects, manufacturers and project teams.
These boundaries turn vague BIM claims into requirements that can be demonstrated against a representative building product and receiving workflow.
3D preview is not automatically a BIM object
A browser model may be optimized for interaction, rendering and device performance. A BIM deliverable can require different geometry, object class, parameters, representation, coordinates, detail and validation. Share identity and source inputs; test each representation for its own use.
A file extension is not an acceptance result
Producing an IFC or RFA file proves only that a file exists. Acceptance requires a named target version or schema, receiving workflow, required information, representative test cases and evidence that the file imports and behaves correctly.
Product data needs semantics and provenance
A label such as acoustic value or thermal performance is insufficient without the exact property definition, unit, product applicability, source, test or calculation basis, revision and approved owner. Do not infer engineering values from visual options.
Configuration validity is not project approval
The rules engine can prove that selected catalogue choices are allowed. It cannot by itself prove site conditions, structural suitability, regulatory compliance, coordination clearance or installation approval unless those checks are explicitly modeled, sourced and accepted.
Detail must match the information need
More polygons and parameters are not automatically better. Define the geometry and information needed for selection, coordination, documentation, analysis, procurement or operation, then avoid unnecessary weight and unsupported data.
Commercial and technical revisions must remain linked
A quote can remain commercially valid while a technical file is superseded, or a model can be technically approved before the final price. Keep separate statuses and approvals connected to one configuration identity and explicit revisions.
Implementation blueprint
Build the product truth before automating the file delivery.
An eight-stage implementation aligns catalogue, engineering, BIM, sales and integration owners around one representative-product proof before scaling to the wider building-product range.
Define the use case and recipients
Choose the building products, user roles, project stages, markets, authoring or coordination tools and downstream commercial actions. Name what decision each output supports.
Proof: Use-case map with in-scope products, recipients, decisions and exclusions
Inventory the authoritative product data
Trace product identity, options, dimensions, interfaces, properties, classifications, documents, CAD or BIM content, price inputs and release status to their owners.
Proof: Source-of-truth matrix and data-quality report
Model the valid configuration space
Define stable IDs, product families, types, continuous parameters, option groups, compatibility, calculated values, review triggers and market rules independently of interface labels.
Proof: Representative normal, boundary, invalid and exception configurations
Specify the information contract
Map required classes, properties, identifiers, units, sources, applicability, file metadata and project context. Record which fields are required for each use, market and recipient.
Proof: Versioned schema, property map and example payloads
Design each representation deliberately
Separate browser visualization, thumbnails, drawings, native families, open exchange and production derivatives. Define geometry scope, placement, coordinates, materials, detail, parameters and file versions for each.
Proof: Representation matrix and approved sample files
Connect the project and commercial journey
Preserve project, product and configuration identity through enquiry, specification, technical review, quote, dealer routing, order and revision without copying uncontrolled snapshots between systems.
Proof: End-to-end trace across Configurix and named downstream records
Validate in receiving tools
Test representative and worst-case outputs in supported Revit, IFC viewers, authoring, coordination or project systems. Check geometry, class, properties, units, files, status and failure behavior.
Proof: Signed acceptance evidence per target version and use case
Govern change after launch
Version product rules, properties, mappings, files and integrations; assess saved projects; deprecate safely; publish approved updates; and rerun regression evidence whenever a source or target changes.
Proof: Release workflow, change-impact record and regression pack
Working acceptance tests
Twelve tests replace “BIM-ready” with evidence.
Run these tests against the real catalogue, largest supported geometry, target file versions, receiving applications and connected systems. A presentation is not the acceptance environment.
- 1
A user can identify the exact manufacturer product, model or system and supported market before configuring it.
- 2
Every allowed selection, continuous dimension and calculated value resolves to stable structured identifiers rather than interface text alone.
- 3
Invalid combinations are prevented or explained, and configurations outside the standard solution space follow an explicit technical-review path.
- 4
The browser 3D scene, saved configuration, property summary and generated outputs reconcile to the same configuration revision.
- 5
Required technical properties retain definition, value, unit, applicability, source and revision; missing values are not invented or silently defaulted.
- 6
Classification, IFC class, Revit category, shared parameter or dictionary mappings match the agreed target and version.
- 7
Each native or open file imports into every supported receiving-tool version and passes geometry, placement, parameter, unit and behavior checks.
- 8
Largest, smallest, boundary, optional-accessory, multilingual and historical configurations are included in regression evidence.
- 9
A superseded product, property or file cannot appear as current without a visible migration, substitution or review decision.
- 10
Quote, technical review and BIM acceptance retain separate statuses while pointing to one product and configuration identity.
- 11
Project, customer and commercial information follows the agreed authorization, retention and sharing policy in every downloaded or linked output.
- 12
The complete architect, contractor, dealer and manufacturer journey works on supported devices and through delayed, failed and retried integrations.
Failure patterns
Most BIM configurator failures begin before the export button.
The recurring problems are unclear purpose, uncontrolled information, detached files and missing receiving-tool evidence—not simply the choice of 3D technology.
Calling every 3D model BIM
A renderable asset may have no governed object class, properties, project placement, information requirement or receiving-tool acceptance. Define each representation by purpose.
One generic download for every user
Architects, BIM managers, contractors and sales teams need different decisions and evidence. A giant file bundle creates confusion and stale copies instead of a controlled handoff.
Unmapped property names
Similar labels can carry different definitions, units and applicability. Use governed identifiers, definitions and sources; do not map by display text alone.
Over-modelled manufacturer content
Excess geometry and irrelevant details slow authoring and coordination tools without improving the decision. Match geometry and information to the intended project use.
Static files detached from product revisions
A download folder cannot explain whether a file matches the current product, market, properties or configuration. Version and status belong in the delivery contract.
Engineering claims inferred from choices
A finish, size or component can affect performance, but the system must use an approved relationship and source. Visual similarity does not establish technical performance.
No receiving-tool regression
A generator may succeed while Revit, an IFC workflow or a project system loses parameters, units, placement or geometry. Acceptance happens in the supported target workflow.
One approval status for everything
Configured, priced, quoted, technically reviewed, BIM-validated and released are different states. Combining them hides risk and makes later changes impossible to explain.
Primary technical references
Use current standards and receiving-tool documentation.
These sources support the category definitions and implementation boundaries. The project still needs its own information requirements, product sources, mappings and acceptance evidence.
buildingSMART: IFC 4.3.2.0 documentation
The official IFC 4.3 documentation covering the schema, property and quantity sets, exchange mechanisms and domain definitions.
buildingSMART: Information Delivery Specification
Primary guidance on machine-interpretable exchange requirements for objects, classifications, properties, values and units.
buildingSMART Data Dictionary
Primary description of bSDD as a free service for interconnected definitions and consistent built-environment terms.
ISO 19650-1:2018
Current published concepts and principles for managing, exchanging, recording, versioning and organizing information across an asset life cycle.
ISO 23386:2020
Current methodology for describing, authoring and maintaining construction properties in interconnected data dictionaries.
ISO 23387:2025
The current second edition covering machine-interpretable data templates for objects used across the life cycle of assets.
Autodesk: Loadable Families
Primary Revit guidance on external RFA families, types, parameters, geometry behavior, detail levels and sample-project testing.
Autodesk: Shared Parameters
Primary guidance on reusable parameter definitions across Revit families and projects, schedules and annotation.
Autodesk: Revit and IFC
Primary guidance on Revit IFC import, export, containers, parameters and mapping to buildingSMART exchange standards.
Related architecture guides
Connect BIM delivery to the rest of the product system.
Frequently asked questions
BIM product configurator questions, answered precisely.
The answers separate configurable product logic, governed BIM information, native and open file delivery, commercial workflow and project approval.
From product catalogue to project handoff
Prove the workflow with one representative building product.
Bring the real product rules, source models, property requirements, target BIM or CAD tools and commercial journey. Configurix can define the configuration and handoff boundary around evidence the project team can inspect.