Every capability your delivery workflow depends on — in one platform.
BOMSync is organised around five verbs of built asset delivery: BIM, BOM, BUY, BUILD, and MANAGE — each a deep capability domain, all sharing the same operational data layer.
Model intelligence that carries forward
BOMSync’s BIM layer is not a viewer and not a file repository. It is a selective release discipline: elements that matter for procurement, compliance, and fabrication graduate into the operational layer — deliberately, not by accident. What enters the platform is curated, classified, and ready to drive downstream decisions.
Released model elements map directly to BOM lines, assemblies, and calculation rules. No manual re-entry; no shadow spreadsheet that someone stops maintaining after week three.
PDF sheets and view-selected element sets drive structured quantities, so one sheet template serves multiple projects with consistent rules. Annotations and markups are stored as structured data — they survive the next revision cycle instead of living in someone's email.
IFC is treated as an on-demand geometric and classification source — not a bulk dump into core operations. Use geometry and classification when you need them; keep the operational layer clean and intentional.
Design deltas become operational flags, not forensic exercises. When a wall type changes, the affected BOM lines, procurement items, and fabrication batches know about it — without a coordinator chasing every downstream team manually.
Annotated PDFs, work items, and model-linked context stay anchored to the document version that created them. "Which PDF is law?" has a clear answer.
BOMSync connects directly with Revit for live model intelligence, parameter-driven BOM extraction, and bidirectional coordination — so design teams stay in their authoring environment while operational data flows into the platform.
From element to complete commercial scope
Models are never commercially complete. BOMSync’s BOM layer handles the modeled scope — and the real world that construction always adds: consumables, temporary works, overhead items, and non-modeled assemblies. The result is a bill of materials that procurement, estimating, and fabrication can actually work from.
Multi-dimensional calculation rules expand model quantities into procurement-ready line items. Recipes break down assemblies into their constituent parts — automatically, repeatably, and consistently across every project that uses the same template.
Complex assemblies — wall systems, MEP packages, structural frames — are defined once and reused. Every project that references the kit inherits the correct BOM breakdown without manual rebuilding.
Items that were never modeled — consumables, temporary works, site overhead, owner-supplied materials — can be added and managed as first-class BOM lines. Commercial completeness is not optional.
A library of BOM report formats for different outputs: RFQ packages, shop lists, cost breakdowns, and handover schedules. Reports are structured, not ad hoc, so the same format consistently produces the same result.
Select a view in the PDF viewer — a floor plan, a wall section, a specific level — and generate a structured BOM from the elements visible in that view. Quantities tied to what you see, not what you guess.
Multiple model variants or project configurations share a common item library. Scenario costing — "what if we use this wall type instead?" — is a configuration change, not a full re-estimation.
From demand to purchase order in one auditable graph
The gap between design intent and purchase reality is where commercial projects bleed. BOMSync’s procurement layer connects demand through pending to purchase orders — with vendor workflows, consolidation tools, and ERP synchronisation that keep every team reading from the same source.
BOM-derived demand flows into a structured pending stage where procurement teams assign vendors, quantities, and commercial terms before committing to purchase orders. Nothing goes to PO without a clear decision trail.
Send structured RFQ packages to vendors directly from BOMSync. Vendors respond through a dedicated portal — no email attachments, no version confusion. Compare responses, negotiate, and award within the same workflow.
Vendor-specific pricing tiers, material rate books, and contractor rate schedules sit in the platform — so cost estimates and purchase comparisons draw from agreed terms, not memory.
Multi-project programmes can consolidate procurement across projects to achieve volume efficiencies. Instead of each project buying independently, programme-level batching captures the commercial advantage of scale.
Purchase orders, receipts, and inventory movements synchronise with your ERP environment — so finance sees committed costs, procurement sees actual deliveries, and the BIM-originated demand context is not lost at the ERP boundary.
Track what was ordered against what was delivered and what was consumed. Variance is visible in the platform — not in a quarterly reconciliation spreadsheet someone builds manually from three exports.
From BOM to validated, machine-ready output
The gap between a BOM and a shop floor is where fabrication errors, scrap cycles, and rework happen. BOMSync’s BUILD layer connects the procurement-ready BOM to validated, machine-specific fabrication files — with audit gates, configurable rules, and traceable run history that make the shop floor as accountable as the design office.
Upload CNC files and validate them against configurable machine and tooling rules before anything is cut. Profile mismatches, unit errors, and rule violations surface before scrap, not after.
Each machine — each profile, each tool, each production line — has its own rule set. Validation is machine-specific, not generic. What passes on Machine A is not automatically permitted on Machine B.
Every production run — every batch of cut files, every fabrication job — is recorded with a timestamp, operator context, revision reference, and outcome. When "which run produced this?" comes up in a dispute or quality review, the answer is in the platform.
Tenant-defined quality checklists gate files from created to shop-ready and from checked to authorised for issue. The same engine governs document release and fabrication issuance — one quality posture across the platform.
BOMSync integrates with a deterministic nesting solver for material yield optimisation. Solver inputs come from the BOM; outputs feed back into demand and fabrication records. Nesting decisions are traceable — not a mystery folder on a USB stick.
Iterations stay linked across design churn. When a wall type changes, the platform connects yesterday's run to today's design change through stable element identity. Rework is traceable; re-keying is not required.
Govern the programme; run the building
BOMSync’s management layer spans the full lifecycle — from programmes of many projects through construction delivery to the operational phase where facility teams need to know what was installed, where, by whom, and to what specification. It is the governance layer that makes every other layer trustworthy.
Multiple projects under one programme with shared governance, item libraries, stable codes, and partner access controls. The programme level is where capital investment programmes, housing programmes, and infrastructure delivery schemes are coordinated at scale.
Controlled collaboration between organisations — each with their own data environment, each with explicit and auditable access grants. Share what needs to be shared; keep private what should remain private.
Authoritative document links connect the right file to the right element, specification, or procurement package. Files promote from draft to reviewed to authoritative through governed workflows — not arbitrary folder conventions.
Programme and project schedules with resource allocation, dependency management, and milestone tracking. Import from Microsoft Project where needed. Phase-linked to BOM and procurement workflows.
Purchase and consumption data at item and project level, with Uniclass and EN 15978-aligned attributes where your data supports them. Carbon and compliance stories trace to real procurement records — not generic industry coefficients.
Programme-level dashboards, project KPIs, financial summaries, and procurement status rolled up for leadership. Built on a structured reporting layer — not pivot tables rebuilt every Monday morning.
After construction, the operational layer stays live: item data, document links, maintenance references, and warranty records accessible from the element that contains them — without requiring every facilities user to operate a full authoring model.
Information container patterns, access controls, and activity logging are designed around the expectations of serious information management programmes — for owners, contractors, and regulators who require structured, auditable information delivery.
The trust layer
Per-organisation database isolation on Azure. Role-based access with least-privilege controls. Every access action logged. Encryption at rest and in transit. Azure Active Directory / B2C integration across all tiers.
Full audit trails across BIM, BOM, procurement, communications, and document actions. Designed for environments where regulatory, legal, or contractual disputes require a clear evidence trail. Alignment with ISO 19650 information management expectations.
AI assistance for enrichment, data quality flagging, and document intelligence — always with human-reviewable outputs. BOMSync's AI posture is deliberate: augment, don't replace, human judgment in audit-sensitive workflows.
See the capabilities that match your workflow
A 30-minute walk-through tailored to your industry and delivery model is the fastest way to understand BOMSync’s depth.