One platform. Five domains. One operational truth.
BOMSync is a data refinery — not a data lake. Five interconnected domains share one curated, auditable operational layer so every team, every project, and every decision draws from the same trusted source.
A refinery, not a lake
Every domain in BOMSync writes to and reads from the same operational layer: stable element identities, curated item intelligence, auditable history, and governed document links. An element released from BIM into the BOM layer carries its identity into procurement, fabrication records, and eventually the facility management register — without re-keying, without reconciliation spreadsheets, and without a team of integrators manually bridging each transition.
This is what “refinery, not lake” means in practice: data enters the platform once, deliberately, and enriches every downstream decision it touches. Point tools store data. BOMSync makes it operational.
One model. Unlimited projects, finishes, and procurement decisions.
BOMSync separates model geometry from procurement reality. A single canonical BIM model can be deployed to any number of project instances — each carrying its own finish selections, fixture assignments, and material procurement decisions. Changing the paint colour on one unit never touches the model. Assigning a different kitchen package to Apartment 407 versus Apartment 812 is a procurement decision, not a design revision. The model stays canonical; the procurement stays as individual as each brief requires.
One house type model. Fifty-unit subdivision. Every unit carries its own finish package — colour schemes, fixture grades, optional upgrades. BOMSync generates a procurement-ready BOM for each unit independently. The model is canonical; the procurement is as individual as the buyer.
Five room type models for a 30-story hotel. Two hundred rooms. Every room has a unique floor, view configuration, and FF&E assignment. BOMSync generates location-aware BOMs by room, by floor, by category — without rebuilding the model for each room.
A single PDF that dynamically reports the BOM for any location you query — Room 507, Floor 12, Wing B, or the entire project. The report draws from the procurement layer attached to each model instance, not from a static export that was accurate on the day it was run.
A single BIM model with configurable parameters — number of bedrooms, bathroom configuration, optional garage, selected fitout tier. Query the model with different variant inputs; receive a structurally correct BOM for each configuration. Procurement decisions attach to the variant, not to a separate model file.
Platform depth, domain by domain
BOMSync's BIM Design domain is the entry point for operational intelligence. Rather than treating every element as equally relevant, BOMSync uses a selective release discipline: only elements with procurement, compliance, or fabrication significance graduate into the operational layer. Geometry and classification inform the platform when depth is needed — without turning the CDE into an unmanaged file pile.
Sheet intelligence, IFC-aware workflows, and revision tracking ensure that design changes are operational events, not communication problems. When a design changes, the downstream operational record knows — without a coordinator chasing every team to update a spreadsheet.
-
Selective BIM release — Only procurement-relevant elements enter the operational layer; noise stays in the authoring environment.
-
BIM-to-BOM lineage — Model elements map directly to BOM lines, calculation rules, and procurement items — without re-entry.
-
Sheet and PDF intelligence — Quantities tied to view-selected elements; annotations stored as data, surviving every revision cycle.
-
IFC-aware distribution — IFC used as an on-demand geometric and classification source — not a bulk operational dump.
-
Revision and change tracking — Design deltas surface as operational events — traceable from the moment they are released.
-
Revit integration — Live parameter-driven BOM extraction and bidirectional coordination for design teams staying in their authoring tool.
The AEC Delivery domain is where projects become programmes. BOMSync's programme architecture groups many projects under one governed environment — with shared item libraries, stable codes, and partner access controls that make cross-organisation collaboration auditable rather than ad hoc.
Multi-disciplinary coordination, threaded communication, work item conversion, and ISO 19650-aligned information management are native behaviours of the domain — not integrations bolted on later. Audit posture is continuous, not periodic. The programme director has a current, governed view at all times.
-
Programme and portfolio management — Many projects under one programme with shared governance, codes, and commercial controls.
-
Multi-agency collaboration — Controlled access across organisations; explicit grants, auditable sharing, no accidental commingling.
-
Threaded communications and work items — Comments convert to tracked work items anchored to model and document context.
-
ISO 19650-aligned information management — Container patterns, access controls, and activity logging for serious programme environments.
-
Audit-grade history — Every action across BIM, BOM, procurement, and communications recorded and searchable.
-
Programme KPIs and dashboards — Executive-ready rollups of cost, procurement status, schedule, and quality posture.
The Manufacturing domain closes the gap between a procurement-ready BOM and a shop-floor-ready, machine-validated fabrication file. CNC file validation with configurable machine and tooling rules catches profile mismatches, unit errors, and rule violations before material is consumed.
Run ledgers record every production batch, revision reference, and operator action. QA gates enforce the same governed quality posture as document release. Nesting optimisation connects the solver to real demand data — making yield decisions traceable, not tribal.
-
CNC file validation — Machine-specific rules checked before cutting; errors caught before scrap cycles — not after.
-
Configurable machine and tooling rules — Per-machine, per-profile rule sets; what passes on one machine is validated separately for another.
-
Auditable run ledgers — Every production batch timestamped, revision-referenced, and outcome-recorded.
-
QA checklist engine — Tenant-defined quality gates from file creation through to shop-issue authorisation.
-
Nesting optimisation — Solver-integrated yield optimisation with traceable inputs and outputs linked to BOM demand.
-
Design-revision linkage — Stable element identity connects production runs to design versions — rework is traceable, not re-keyed.
The Procurement domain connects the BOM-derived demand picture to supplier reality — through a structured, auditable graph of demand, pending decisions, purchase orders, receipts, and inventory positions. Vendor portals, RFQ workflows, tiered pricing, and consolidated batch ordering are native.
ERP synchronisation keeps finance and procurement reading from the same committed-cost picture. The domain closes a loop that generic procurement suites leave permanently open: the loop between what the design said the project needs and what the supply chain actually delivered.
-
Demand-to-PO graph — BOM-derived demand flows through pending decisions to purchase orders in one auditable thread.
-
RFQ and vendor portals — Structured competitive tender with vendor responses, comparison, and award within the platform.
-
Tiered pricing and rate books — Vendor-specific pricing terms and contractor rate schedules used directly in cost estimation.
-
Consolidated batch procurement — Multi-project volume batching to capture commercial advantages of programme-scale purchasing.
-
Bi-directional ERP synchronisation — Purchase orders, receipts, and inventory synchronised with ERP — no boundary data loss.
-
Buy-vs.-actual visibility — Demand, orders, and deliveries compared in real time — not in a quarterly reconciliation spreadsheet.
The Data Intelligence domain is the refinery itself. It governs how data enters the platform (selective ingestion, not passive accumulation), how it is enriched over time (item intelligence: supplier context, lead times, carbon attributes, compliance fields), and how it stays traceable under design and organisational change.
Stable element identity survives model renames, revision cycles, and contract transitions. Bounded AI assists with enrichment and data quality — always with human-reviewable outputs. Reporting, KPIs, and sustainability traceability connect the operational record to the external narratives that owners, regulators, and ESG stakeholders require.
-
Selective ingestion discipline — Only relevant elements enter the operational layer; data quality is a design choice, not a filter after the fact.
-
Item intelligence that compounds — Supplier attributes, lead times, carbon data, and compliance fields accumulate per item across every project.
-
Stable identity across change — Elements, items, and documents stay connected through model revisions, renames, and contract transitions.
-
Sustainability and ESG traceability — Purchase and consumption records trace embodied carbon to real procurement data — not generic coefficients.
-
Bounded AI enrichment — AI assists with data quality and enrichment — with human-reviewable outputs and audit-compatible posture.
-
Operational reporting — Programme and project KPIs, procurement status, and sustainability metrics from a structured reporting layer.
One operational truth beneath every domain
Every domain in BOMSync feeds and draws from the same governed operational layer. The element released in BIM Design becomes the BOM line, which becomes the demand record, which becomes the purchase order, which becomes the fabrication run, which becomes the FM asset register. No re-keying. No reconciliation. No meaning lost at the boundary between disciplines.
This is what separates BOMSync from a collection of connected point tools: the platform’s value compounds with every project, every item, and every procurement cycle — because the knowledge stays.
Ready to see the platform in action?
A 30-minute tailored walk-through is the fastest way to see how BOMSync’s domains map to your specific workflow and delivery model.