1. The workflow gap from Revit MEP to factory floor
Almost every duct shop running serious volume in 2026 lives with a structural gap. On one side of the gap, the design team builds a coordinated 3D Revit MEP model at LOD 350, runs Navisworks Manage clash detection, and signs off a beautiful purple-blue duct route through a hospital plant room. On the other side of the gap, a takeoff estimator opens that model in CAMduct, manually re-creates the run as a fabrication model, redraws every transition and offset, generates a cut list by hand, and emails a PDF spool drawing to a fabricator who keys the dimensions into the auto duct line HMI one piece at a time. Two engineering teams. Two separate models. One project worth of avoidable rework.
The cost of that gap is well known in the industry. A mid-size mechanical contractor running high duct volumes can see a meaningful share of installed length reworked because the as-built deviates from the model. Fittings carry the worst variance — in hospital plant rooms with dense duct routing a noticeable share of transitions and offsets can end up fabricated to dimensions that do not match the field condition. Most of that variance is not a fabrication defect. It is a translation defect: the design model is interpreted twice and lost in translation each time.
Building Information Modelling integration with HVAC duct fabrication machinery is the bridge that closes the gap. Done well, it transports a single source of geometric truth from the BIM coordinator through CAMduct through the auto duct line PLC and back to the model as as-built data — no manual re-drawing, no PDF spool drawings keyed by hand, no two-engineer interpretation of the same fitting. In practice the pattern is 4 to 8 weeks of setup for a shop already running Autodesk Fabrication, or 12 to 16 weeks for a shop new to it, including a small pilot batch before scaling to full project volume.
This article explains how to set the workflow up. It is written for two readers: the BIM coordinator who needs to understand what the shop floor expects from their model, and the duct shop owner who needs to understand what the BIM team is actually shipping to them. We assume you are familiar with Revit MEP basics and have at least seen a CAMduct interface — if you are starting from zero, read the vendor documentation for the tools in section 3 first. Everything below is concrete: software versions, command names, file extensions, schema fragments and the specific failure modes you will hit on the way.
2. Revit MEP duct elements — the data model behind every duct piece
Before you touch any export workflow, understand what a Revit duct element actually contains. A modern Revit MEP duct (in 2024, 2025 and 2026 versions) is not a 3D shape — it is a parametric instance with a defined data model. When you place a duct in Revit MEP, you are creating an object with the following properties on the Properties palette:
- Size — width and height for rectangular, diameter for round. Stored internally in decimal feet regardless of project units, and converted to project units for display.
- System Type — Supply Air, Return Air, Exhaust Air, Outside Air, or any custom system. Drives system colouring and Navisworks filtering.
- System Classification — broader category (Supply, Return, Exhaust). Distinct from System Type and used by analysis tools.
- Insulation Type and Thickness — separate object linked to the duct. Carries a thermal conductivity for energy analysis but no shop-floor seam information by default.
- Lining Type and Thickness — internal acoustic lining, again with no fabrication detail by default.
- Reference Level and Offset — the elevation and level binding that drives clash detection.
- Flow — air flow rate (l/s or m³/h), used by the system analysis but not directly by fabrication.
- Connector Geometry — endpoint connectors that determine fitting selection.
A Revit duct fitting (transition, elbow, tee, offset, takeoff) is a separate Family instance — typically a Family loaded from the standard MEP content library. Each fitting Family carries its own size, angle, throat radius and connector definitions. Critically, the default Revit fittings are design parts — they have geometric dimensions but no fabrication detail (no seam allowance, no connector flange, no gauge specification, no material type beyond a generic system colour).
This data model is sufficient for design coordination, basic energy analysis and clash detection. It is not sufficient to drive a CNC machine. The reason is simple: a duct shop floor cares about properties that the design data model does not store — seam type, connector type, gauge, gasket groove, fabrication tolerance, run-out length, hanger position. To get those properties into the model you need to convert design parts to fabrication parts, which is the topic of section 5.
2.1 Duct Family types and where they live
The standard Revit MEP install ships with three categories of duct content: Ducts (the linear segments), Duct Fittings (elbows, tees, transitions, offsets) and Duct Accessories (dampers, silencers, smoke detectors). The default content lives at C:\ProgramData\Autodesk\RVT 2026\Libraries\English\Mechanical\MEP on Windows and is loaded as .rfa Family files. Most projects load a small subset and rely on their MEP template to standardise what is available. A quick audit of the loaded duct content is the first thing you do when you take over a project from another BIM coordinator — open the Project Browser, expand Families > Duct Fittings, and confirm you have the elbows, tees and transitions you actually need before you start modelling.
3. Revit add-ins and exporters — the tooling landscape
The Revit ecosystem in 2026 supports four primary paths from a coordinated MEP model to fabrication-ready data. Each has a different sweet spot and different licensing footprint. Choose deliberately.
3.1 Autodesk Fabrication CAMduct and CADmep
The native Autodesk path. CAMduct is the shop-floor application — coil nesting, cut list generation, machine output, plasma table NC posting, spool drawing automation. CADmep is the AutoCAD-based companion that BIM coordinators use to layout fabrication-converted runs in 2D. The Revit Fabrication Parts toolset (built into Revit since Revit 2016 R2) loads the CAMduct ITM database directly and gives you a Fabrication Browser palette inside Revit that shows every fabrication part available in your configuration.
This is the path most shops choose because the round-trip between Revit, CADmep and CAMduct uses a shared content database — a change to a connector dimension in CAMduct propagates to Revit on the next reload. Licensing is via the Autodesk AEC Collection or the standalone Fabrication suite. Plan for one CAMduct seat per shop-floor scheduler and one CADmep seat per BIM coordinator who will be doing fabrication editing.
3.2 MagiCAD for Revit
The dominant European MEP add-in for Revit, with strong content libraries from European duct manufacturers and certified product data on a per-region basis. MagiCAD for Revit ships its own duct sizing engine, balancing engine and a Bills of Quantities (BoQ) export that produces fabrication-grade output. It is particularly strong in markets where the duct content is tied to a national standard catalogue (DIN, EN, BS).
3.3 eVolve Mechanical for Revit
A Revit add-in focused on the fabrication-detailing workflow itself. eVolve Mechanical extends the native Revit fabrication parts with hanger automation, layout point export to Trimble or Topcon total stations, weld-mark numbering, and a more shop-floor-centric spool drawing engine. Many North American mechanical contractors run eVolve alongside CAMduct rather than instead of it — eVolve handles the field-coordination side and CAMduct handles the cut list and machine output.
3.4 Native Revit plus Dynamo
For shops that do not have any of the above, the lowest-cost path is native Revit MEP design parts plus a Dynamo script (Dynamo is free, ships with Revit) that walks every duct element, reads dimensions and writes a CSV cut list. This produces a usable basic cut list but loses the spool drawing automation, the connector library mapping and the direct CNC posting. It is a workable entry point for shops in markets where Autodesk Fabrication content is hard to source. Confirm with the machine supplier which job-file formats the line's controller accepts.
4. Common file formats for fabrication transfer
Once you have decided which add-in is producing the fabrication data, the next decision is the transfer format. Each format carries a different set of properties and a different level of fidelity. Get this decision wrong and you spend the project re-creating data that was already in the model.
4.1 PCF — Piping Component File
Originally a piping format, PCF (.pcf, plain text) is widely supported across mechanical fabrication tooling. It carries component types, dimensions, materials and connection data in a flat human-readable schema. For ductwork PCF is rarely used directly — it has been adapted in a few workflows but its native vocabulary is pipe-shaped. Mention it for completeness; in a duct shop the more relevant formats are MAJ and the CAMduct XML.
4.2 MAJ — Autodesk Fabrication job file
The Autodesk Fabrication job file (.MAJ), the native job format of CAMduct and the CAM export format from CADmep. Contains every fabrication part in the project, the coil nesting state, the cut list, the spool definitions, the gauge mapping and the connector assignments. MAJ files are not directly readable by an auto duct line PLC — they are the staging file from which you export the cut list, spool drawings and machine NC files. Treat the MAJ as the project master and the XML/DXF/JSON exports as the dispatched outputs.
4.3 Autodesk Fabrication content and database files (.ITM, .MAP)
An Autodesk Fabrication configuration is a folder of shared content: item files (.ITM) and database files (.MAP), located through a MAP.INI file. The .ITM file is the item itself, the parametric definition of a fitting. The database files hold the shared tables such as materials, gauges, seams and connectors. Job files (.MAJ, see 4.2) are separate: each one holds a single project, not the shared content. When you change a connector or material definition in CAMduct, you are editing the shared database, so the change reaches every job that uses the configuration. Version-control these files in your shop's Git repository or an equivalent version control system; otherwise an undocumented edit to a connector or item will silently break every project that uses it.
4.4 IFC — Industry Foundation Classes
IFC (.ifc, plain text under ISO 16739) is the open BIM exchange format. IFC4 and IFC4.3 carry duct geometry under IfcDuctSegment, IfcDuctFitting and IfcFlowController entities. For ductwork the IFC export from Revit (using the IFC4 Reference View MVD) is sufficient for clash coordination and high-level QTO but loses fabrication detail — seam type and connector type are not standard IFC attributes and require a property set extension. Some shops use IFC as the input to a custom IFC parser that produces a cut list for the line, typically exported as CSV or DXF (confirm the controller import formats at quotation); this is a sensible path for projects where the design team will not move to Revit fabrication parts.
4.5 gbXML — Green Building XML
gbXML (.xml) is the energy analysis exchange format used by IES VE, EnergyPlus and other simulation tools. Mention it because it appears in BIM workflows, but it is not used for duct fabrication — it carries airflow and thermal data, not seam and connector information.
4.6 IDS — Information Delivery Specification
IDS (.ids, an XML schema under buildingSMART) is a relatively new format that lets a project specify which IFC properties must be present on which entities. For BIM-to-fab work an IDS file lets the duct shop demand that any IFC handed over must have, for example, IfcDuctSegment.Material, IfcDuctSegment.WallThickness and a Pset_DuctFabrication property set with seam type and connector type. Where the design team produces an IDS-compliant IFC, the shop floor saves weeks of data cleaning.
4.7 CAMduct XML cut list
The format that matters most for direct CNC integration. CAMduct exports a project cut list as XML with a stable schema documented in the Autodesk Fabrication SDK. The XML contains, per part, an item ID, system tag, gauge, blank length and width, fitting type, seam type, connector references and any per-part metadata. Whether a given machine controller can read this XML directly, or needs a transform step, depends on the machine, so confirm the accepted job-file formats with the supplier. The CAMduct XML is the most common production-grade transfer format for shops running a full Autodesk Fabrication workflow.
4.8 DXF flat patterns
For any fitting that requires plasma cutting outside the auto duct line — non-standard transitions, oval-to-round transitions, custom plenum panels — CAMduct exports a DXF flat pattern (.dxf, AutoCAD ASCII format) ready for nesting on a CNC plasma table. DXF is the most widely supported input for plasma table nesting and CNC software. See Taokron auto duct line specifications.
4.9 JSON job package
For shops running a more modern API-driven scheduling workflow, a JSON job package is one option, containing job ID, priority, due date, part list (with reference to the XML cut list rows) and a per-part scheduling attribute. Check with the machine supplier whether the line's controller can import it. JSON is a sensible format for shops integrating BIM with a Manufacturing Execution System (MES).
5. Fab parts vs design parts — the critical distinction for duct shops
The single most common failure in BIM-to-fab projects is sending a Revit model full of design parts down the fabrication path. Design parts are the default Revit MEP duct elements — they look like ducts, they clash like ducts, but they have no fabrication detail. Fabrication parts are real shop-floor components with seam type, gauge, connector geometry, gasket groove and supplier-specific dimensions, loaded from a CAMduct or CADmep ITM database.
5.1 What design parts contain
A Revit MEP design duct stores nominal width, height and length, system tag, insulation reference, level reference and a generic connector at each end. It does not store seam type, gauge, exact connector flange dimension, gasket groove, fabrication tolerance or shop-floor part number. The fitting Families ship with default geometric dimensions but those dimensions are not pegged to a specific manufacturer's hardware.
5.2 What fabrication parts contain
A Revit fabrication part is loaded from a CAMduct ITM and stores every property a shop floor cares about — seam type (Pittsburgh, snaplock, button-punch), gauge (mapped to a coil thickness in the gauge table), exact connector flange profile (TDF, slip-on, S-and-drive), gasket groove, gasket type, hanger anchor location, accessory mounting bosses. Every dimension is keyed to your actual hardware library. When the BIM coordinator places a fabrication transition in Revit, the model knows exactly what blanks the auto duct line must cut to make that transition.
5.3 The Design to Fabrication conversion
Revit MEP includes a Design to Fabrication command (Systems tab → Fabrication panel → Design to Fabrication). It reads design ducts and fittings from the active view, looks up the closest match in the loaded CAMduct ITM database, and replaces them with fabrication parts. The conversion is not perfect — orphaned fittings, mismatched connectors and out-of-range sizes all get flagged in the Fabrication Browser palette as unconverted segments. A typical conversion of a hospital plant room takes 10–30 minutes of automated work plus 4–10 hours of manual cleanup of orphans.
The cleanup is non-negotiable. If you export a cut list from a partially converted model, the orphaned segments either get skipped (the shop runs short of duct on site) or get exported as design parts (the shop fabricates from invalid dimensions and has to rework pieces). Either way the project pays the cost. Build the cleanup into your BIM-to-fab playbook as a mandatory checkpoint.
6. Spool drawings and shop drawing automation
Once you have a clean fabrication-converted model, the next question is how the shop floor knows what to fabricate, in what order, in what bundle. The answer is spool drawings — isometric shop drawings of grouped duct segments labelled with piece marks, dimensions, gauge call-outs, connector schedule and a per-spool BOM.
6.1 What a spool actually is
A spool is a transport-and-rigging unit — typically up to 6 m or 12 m of duct (depending on transport) that ships from the shop to site as a single bundle. A spool may contain a straight run plus its connecting elbows and a transition, or it may be one large transition with connectors on both ends. Spools are defined by:
- System and level — every spool belongs to one system tag (SA, RA, EA) on one floor level.
- Transport length — capped at 6 m or 12 m depending on what fits in your truck and through the building's loading dock.
- Rigging mass — capped at the lift capacity of the site crane, typically 200–800 kg per spool.
- Sequence — installed in a defined order that drives the fabrication priority queue.
6.2 Generating spool drawings in CAMduct
In CAMduct the Spool Drawing tool (under Output > Spool Drawings) generates an isometric drawing per spool, optionally with a key plan and a BOM. The output is typically a multi-page PDF or a per-spool DWG file. A typical mid-rise commercial project produces 200–600 spool drawings; large hospital and industrial projects can generate 2,500+ spool drawings from a single CAMduct project file. Auto-generating that volume without scripting would not be feasible.
6.3 Piece marks and bar codes
Every fabrication part in a spool gets a unique piece mark — a short alphanumeric tag printed on the duct in the shop and used by the field crew to install the right piece in the right place. Modern spool drawings include a Code-128 or QR code per piece mark so the field crew can scan the duct against the model on a tablet. Some auto duct lines can print the tag and bar code directly on the duct with an inline printer, which removes the manual labelling step. Ask the supplier whether this is available on the line you are specifying.
7. CAMduct and CADmep coil nesting and cut list generation
The cut list is where BIM-to-fab earns its money. A busy duct shop cuts a large number of individual blanks every month, each one consuming coil according to a calculated nesting pattern. Manual nesting on a typical project takes an estimator hours and tends to leave more scrap on the coil. CAMduct coil nesting generally improves material utilisation and cuts the nesting time substantially.
7.1 Coil nesting basics
Coil nesting is the optimisation problem of arranging duct blanks across a coil width such that material yield is maximised and the cut sequence is feasible. CAMduct's coil nesting module supports rectangular, transition and offset blanks with configurable seam allowance, scrap allowance and kerf compensation. Set the kerf to match your plasma table or shear cut width — typically 0.8–1.5 mm for plasma — otherwise downstream cut lengths drift.
7.2 Cut list generation
Once nesting is complete the cut list is exported as XML, CSV or directly to the auto duct line PLC. The XML is the production-grade format because it carries all per-part properties and binds back to the CAMduct project (and therefore the Revit model) via the part ID. The cut list is the file that drives the auto duct line — every job on the auto duct line traces back to a row in the cut list, which traces back to a fabrication part in CAMduct, which traces back to a fabrication part in Revit, which was converted from the LOD 350 coordinated design and brought to LOD 400 before export.
7.3 Sample CAMduct XML cut list fragment
For reference, a typical CAMduct XML cut list fragment for a single straight duct piece looks like (schema-illustrative, not a literal field-by-field copy of the SDK):
<CutList project="HospitalPlantRoomL3">
<Item id="SA-L3-0142">
<System>Supply Air</System>
<Gauge>1.0</Gauge>
<BlankLength>1985</BlankLength>
<BlankWidth>1230</BlankWidth>
<Seam>Pittsburgh</Seam>
<ConnectorA>TDF-25</ConnectorA>
<ConnectorB>TDF-25</ConnectorB>
<Spool>SP-L3-014</Spool>
</Item>
</CutList>
Each item carries the data needed to define a finished duct piece. The controller may still need the list transformed into its own job format, and for Taokron lines cut lists are exported as CSV or DXF, so confirm the controller import formats at quotation.
8. Direct CNC integration — posting from BIM to plasma table and auto duct line PLCs
Direct CNC integration is the moment the BIM data physically meets the steel. The data has travelled from Revit MEP through CAMduct to a cut list; now the cut list has to drive a machine.
8.1 The two CNC paths
A modern duct shop runs two CNC paths in parallel. The auto duct line (SBAL-V or SBAL-III) handles straight runs and standard fittings — it accepts a coil and produces finished duct sections with seams, beads and connectors automatically. A CNC plasma table handles non-standard transitions, oval-to-round transitions, custom plenum panels and any flat-pattern blank that does not fit the auto duct line geometry envelope. Both paths read from the same CAMduct cut list — the auto duct line takes its job data from the cut list, and the plasma table reads DXF flat patterns.
8.2 Posting to an auto duct line
Ask the machine supplier which controller the line uses and how it takes job files: a network file drop, a USB import or an industrial protocol such as OPC UA. See our PLC integration guide for general background.
8.3 Posting to a CNC plasma table
Most CNC plasma tables accept a DXF flat pattern, either in the controller or through the table's nesting software. The flat pattern is nested on the plasma table (either by the CAMduct nesting or by the plasma controller's nesting module), and the controller drives the torch through the cut path. Most shops route any non-standard transition or oval blank to the plasma table.
8.4 OPC UA — the bridge protocol
OPC UA (IEC 62541) is the protocol that ties the auto duct line PLC to the higher-level BIM and MES systems. Many current industrial PLCs support OPC UA natively, and others can be connected through a gateway. It gives the BIM team a clean, vendor-neutral interface: they read job status, throughput and as-built data through the same protocol regardless of which PLC brand is on the line.
9. File formats and what to ask the machine supplier
Auto duct lines differ in which job-file formats their controllers accept. These are the four input formats most often used, and two output formats worth asking about. Confirm with Taokron which of them apply to the line you are specifying.
9.1 Common input formats
- XML cut list — CAMduct XML, directly or through a transform step.
- DXF flat patterns — for non-standard blanks routed to a plasma table.
- JSON job package — for shops running an MES and scheduling priority through an API.
- CSV — an entry-level cut list for shops without CAMduct (typically generated from a Revit Dynamo script), and the usual format for the procurement bill of materials.
9.2 Possible output and feedback formats
- OPC UA tags — real-time job status, throughput, scrap rate, line state.
- Completion JSON — per-job completion package with actual cut length, gauge, scrap, time taken, exported back to the BIM model for as-built reconciliation.
9.3 Tooling envelope and what fits the auto duct line
Check the duct sizes in your model against the published specification of the line. The SBAL-V takes 0.5–1.5 mm material at 1250 or 1550 mm maximum width, and the SBAL-III takes 0.5–2.0 mm at the same widths. Anything outside the envelope (round, oval, very large rectangular) routes to a plasma table or another machine. Taokron auto duct lines specification page has the full envelope. For sizing rectangular runs against the SBAL-V envelope, the Taokron rectangular duct sizing chart is the quick reference.
10. Coordination with structural BIM — clash detection in Navisworks
BIM-to-fab does not exist in isolation. The duct model only matters because it has been coordinated against the architectural and structural models in the same BIM environment. Most projects do this in Autodesk Navisworks Manage, the BIM clash-detection and 4D coordination tool.
10.1 Standard Navisworks clash workflow
The MEP coordinator exports a Revit model to NWC (Navisworks Cache) format, the architect and structural engineer export their models to NWC, and the clash detection coordinator appends all NWCs in a single NWF (Navisworks File) container. The Clash Detective tool runs hard, soft and clearance clashes per system pairing — duct vs structural beam, duct vs cable tray, duct vs hydronic pipe.
10.2 Why clash detection matters for fabrication
A clash discovered on site costs far more to fix than the same clash discovered in BIM. A duct that hits a structural beam in the model costs 30 minutes of re-routing in Revit. The same duct fabricated, shipped, hung and then discovered to clash on site costs the rework labour, the new piece, the shipping, and the site delay. Run the clash detection before exporting any fabrication data — every project skipping this step pays the cost on the floor.
10.3 Federated model handover to fabrication
Once clashes are resolved, the federated Navisworks model becomes the basis of the fabrication handover. The MEP fabrication-converted Revit model is the source of cut lists and spool drawings, but the federated NWF is the basis for hanger location coordination, ceiling void verification and access route planning. Some shops route hanger anchor points directly from Navisworks to a Trimble or Topcon total station for site setting-out.
11. LOD progression — from design intent to fabrication-ready
Level of Development (LOD) is the BIM standard for describing how complete a model is. The terminology comes from the AIA LOD framework and the BIMForum LOD Specification. ISO 19650 itself does not use LOD; it uses the concept of level of information need, which many projects map to LOD stages in the BEP. For HVAC duct fabrication, four LOD levels matter.
11.1 LOD 200 — design intent
Generic system geometry approximating size, location and orientation. A duct at LOD 200 may be a single line with a nominal width tag — usable for system layout and concept clash but not for procurement or fabrication. Any contractor exporting fabrication data from a LOD 200 model is gambling.
11.2 LOD 350 — coordinated design
Specific system geometry coordinated against architecture and structure, with size, location, orientation and interface to other systems. The model is at LOD 350 by the end of the design coordination phase. Critically, LOD 350 still uses design parts, not fabrication parts. The model is good for clash and tender takeoff but not for direct fabrication.
11.3 LOD 400 — fabrication-ready
Fabrication-ready geometry with seams, connectors, hangers, accessory mountings and supplier-specific dimensions. LOD 400 is the threshold for direct CNC posting. Any shop running BIM-to-fab is producing or receiving a LOD 400 model. The transition from LOD 350 to LOD 400 typically happens 6–10 weeks before the first duct piece is required on site, often via a contractor-led fabrication conversion of the design team's LOD 350 model.
11.4 LOD 500 — as-built
As-installed geometry verified against the field condition. LOD 500 is the asset handover model used by facilities management for the building's operational life. The digital twin feedback loop described in section 16 is what produces LOD 500.
12. Quantity takeoff and procurement integration
The same fabrication-converted Revit model that drives the cut list also drives procurement. Quantity Takeoff (QTO) reads the model and produces a coil-per-gauge-per-width purchase list, a connector hardware count, a gasket length, a hanger count, an accessory schedule and a labour estimate.
12.1 Running QTO from CAMduct
CAMduct's Quantity Takeoff to CSV produces a procurement BOM in 2–5 minutes for a typical mid-size project. The CSV columns are coil specification (material, gauge, width), total length required, total area, scrap allowance, connector count per type, gasket length, hanger count by type. Hand off to procurement early enough to cover the longest coil lead time on the job. Standard galvanised coil in common widths usually arrives sooner than heavier gauges or stainless, which can take considerably longer, so confirm lead times with your coil supplier and hand off at least that far ahead of fabrication.
12.2 Linking to ERP
Larger shops link the QTO output directly to their ERP (SAP Business One, Microsoft Dynamics 365, NetSuite). The CSV becomes a purchase requisition, the ERP creates the PO, and the goods-received entry on the coil delivery closes the loop back to the BIM model. The practical pattern is to schedule a weekly QTO export from the active CAMduct project into a shared folder watched by an ERP ingest script. Setup is usually a short job; ongoing maintenance is light, but the script needs checking whenever the QTO export or ERP fields change.
13. ISO 19650, NBS and Australia/NZ BIM guidance reference
BIM-to-fab in 2026 happens inside a regulated framework. The relevant standards depend on the market.
13.1 ISO 19650
The ISO 19650 series is the international standard for information management using BIM. Most public-sector and large private-sector BIM projects globally are now contracted under ISO 19650 — the standard defines the Common Data Environment (CDE), the Master and Task Information Delivery Plans (MIDP and TIDP), the BIM Execution Plan (BEP) and the Asset Information Model (AIM). For BIM-to-fab work, ISO 19650 mostly affects how fabrication data is exchanged between the BIM coordinator and the duct shop — it defines information container states (work in progress, shared, published, archived); the status codes S0 to S5 come from the UK National Annex, not the core standard, and a Common Data Environment for hosting the exchange.
13.2 NBS BIM Toolkit
The NBS BIM Toolkit is a UK BIM specification framework, used mainly on UK projects. It maps Uniclass classification codes to model elements and links to NBS Source for product data. Some UK projects require NBS and Uniclass-compliant deliverables.
13.3 Australia and New Zealand BIM guidance
In Australia, project BIM requirements are commonly framed with the NATSPEC National BIM Guide, a free national guide published by NATSPEC (Construction Information Systems Ltd), a not-for-profit organisation. It is a guide, not an AS/NZS standard, and it is used alongside ISO 19650 and a project BIM brief. Australian projects typically reference NATSPEC documents in their BEP, and New Zealand projects commonly reference the New Zealand BIM Handbook. Ask your project's BEP which NATSPEC requirements apply to drawing title blocks and model element naming.
13.4 SMACNA HVAC BIM Guidelines
SMACNA — the Sheet Metal and Air Conditioning Contractors' National Association — publishes specific guidance on HVAC BIM workflows including a Fabrication LOD specification for ducts, fittings and accessories. Projects in North America typically reference SMACNA HVAC BIM as the LOD baseline. For gauge selection inside the BIM model, the SMACNA gauge chart remains the reference for rectangular duct construction.
14. Common failure modes — and how to prevent them
BIM-to-fab fails in predictable ways. The eight failures below cover most of what we see in the field.
14.1 Rounding errors at fittings
Revit stores lengths internally in decimal feet and converts to project units for display. Fittings authored in imperial then placed in a metric project can pick up conversion residue, so a size that displays as 600 mm may store as 599.998 mm. The residue is tiny per fitting, but it breaks exact-match rules in schedules, connector matching and exports that compare values without rounding. Fix: lock the project unit precision to 1 mm and use the Family Editor to round any internal dimension to the nearest millimetre.
14.2 Missing transitions
The Design to Fabrication conversion sometimes orphans transitions where the size step is not standard in the loaded ITM (e.g. 750→625 mm where the ITM has 750→600 and 750→650 but no 625). Fix: extend the ITM transition library to cover every size step in your design palette before running the conversion.
14.3 Wrong gauge mapping
The CAMduct gauge table has a default gauge schedule — typically conservative SMACNA defaults. If your project specification calls for a different gauge (for example AS/NZS 4254 medium-pressure), the default table produces over-gauge duct that wastes coil and over-loads the line. Fix: edit the CAMduct gauge table to match the project specification before exporting any cut list.
14.4 Connector dimensional mismatch
The CAMduct connector ITM stores cleat dimensions, gasket groove, fastener pattern. If those dimensions do not match the actual hardware on your shelf, every connector seats incorrectly. Fix: physically measure your connector hardware and update the ITM to match — yes, including a calliper measurement of the actual cleat profile.
14.5 Insulation interference
Revit's insulation is a separate object that wraps the duct. If the insulation thickness in the model does not match the actual insulation pre-applied at the line, fittings interfere on assembly. Fix: align the modelled insulation thickness with the line's pre-applied insulation capability, as confirmed with the machine supplier.
14.6 Hanger location drift
Hangers placed in Revit at design-intent levels sometimes drift to non-standard structural positions during coordination. The fabrication-converted model needs hangers at fabrication-grade locations, not design-intent locations. Fix: re-host every hanger on the structural elements in the federated Navisworks model before exporting.
14.7 Spool length exceeds transport
CAMduct spool generation sometimes produces spools longer than 6 m or 12 m if the spool boundary rule is not configured. Fix: set explicit transport-length and rigging-mass caps in the CAMduct spool configuration and re-run the spool generator.
14.8 Cut list units mismatch
The CAMduct XML carries units in millimetres by default, but some legacy plasma controllers expect inches. Fix: set the controller unit explicitly in the export or transform step and run a 5-piece pilot before scaling.
15. Setting up a BIM-to-fab workflow — week-by-week plan
For a duct shop with an existing Revit MEP licence and a trained CAMduct or CADmep operator, the practical setup runs over 4–8 weeks. For shops without prior Autodesk Fabrication experience, plan 12–16 weeks. Below is a suggested timeline for the full 8-week case; faster shops compress the configuration, tuning and scale-up stages.
15.1 Week 1 — audit and scope
Document the current takeoff process, time per 100 m² and rework rate. Confirm Revit MEP and Autodesk Fabrication versions match. Identify the first pilot project — ideally a mid-rise commercial floor, not a hospital plant room, because the scope is constrained.
15.2 Weeks 2–3 — configuration build
Map your shop's tooling to a CAMduct ITM database. Build the connector library matching your hardware. Map gauge tables to your coil inventory. Set up the cut list export for the machine controller.
15.3 Week 4 — Revit conversion
Convert the pilot project's design parts to fabrication parts. Run Navisworks clash detection on the federated model. Validate LOD 400 readiness on the converted model.
15.4 Week 5 — pilot fabrication
Generate the pilot cut list, spool drawings and procurement BOM. Run a 50-piece pilot batch through the line, with transitions and offsets on the plasma table. Measure cut length variance, fitting accuracy and connector seating.
15.5 Week 6 — tuning
If pilot variance exceeds 2%, tune the CAMduct configuration — typically connector allowance, seam allowance or gauge mapping. Re-run a 25-piece confirmation batch.
15.6 Weeks 7–8 — scale and standardise
Scale to the full pilot project volume. Lock the CAMduct ITM database. Version-control the connector library. Publish an internal BIM-to-fab playbook for new operators.
Ask a Taokron engineer about your BIM workflow →
16. Digital twin and feedback loop
The forward direction — Revit to auto duct line — gets most of the attention in BIM literature. The reverse direction — auto duct line back to Revit — is what turns the workflow into a true digital twin.
16.1 What a digital twin actually is
A digital twin in HVAC fabrication is a model that reflects the as-fabricated and as-installed state of every duct piece, not just the as-designed state. It carries actual cut lengths (which are not always identical to designed lengths), actual gauge (which sometimes substitutes due to coil availability), actual connector type (which sometimes substitutes due to procurement) and actual install location (which sometimes drifts in coordination).
16.2 The feedback loop
A feedback loop can draw on three data sources: the machine's actual-cut-length reading, the operator's piece mark scan at line exit, and the field crew's install-confirmation scan. Each piece of data flows back to the BIM model via OPC UA tags and a small Dynamo script that stamps the as-built attributes onto the original fabrication part. The model self-updates from LOD 400 to LOD 500 as the project progresses.
16.3 Variance tracking
The most useful single metric from the feedback loop is length variance per piece — actual cut length minus designed length. Aggregate this metric per gauge, per fitting type and per shift on the line, and use the trend to spot tooling drift before it becomes a quality problem. A stable line holds its variance within the machine's rated tolerance; when variance creeps up, the line is due for tooling regrind or roller alignment.
17. The future — AI-powered BIM optimisation for duct routing
The frontier of BIM in 2026 is AI-powered routing optimisation. Several Revit add-ins now ship with an AI-routing capability that, given a start point, an end point and a set of structural and architectural constraints, proposes a duct route optimised for length, fitting count, pressure drop and cost. The output is a Revit-native fabrication-converted run that integrates directly with the CAMduct cut list workflow.
The reality in 2026 is that AI routing is a useful first-pass tool, not a replacement for a senior MEP coordinator. It can produce a clean route in simpler plant rooms but tends to produce sub-optimal routes in dense ceiling voids where access, hanger constraints and trade sequencing dominate. The realistic role of AI today is as a productivity multiplier — the AI proposes a route, the MEP coordinator audits and adjusts, the fabrication conversion runs as normal.
The more interesting AI development for duct shops is anomaly detection on the as-built feedback data. Feeding the line's actual-cut-length data into a simple regression model spots tooling drift, gauge mis-mapping and connector fatigue weeks before they would surface as quality complaints.
18. Choosing the right Taokron machine for your BIM-to-fab workflow
If you are reading this article because you are about to specify a new auto duct line and you want it to integrate cleanly with your BIM environment, here is the short version of how Taokron machines map to BIM workflows.
- SBAL-V auto duct line — U-shape automatic rectangular duct line for 0.5–1.5 mm material, 1250 or 1550 mm maximum width, 18 m/min, PLC touchscreen. Ask which job-file formats the controller accepts.
- SBAL-III auto duct line — automatic duct line with hydraulic notching and shearing for 0.5–2.0 mm material, 1250 or 1550 mm maximum width, 18 m/min. Ask which job-file formats the controller accepts.
- Plasma table integration — Used for non-standard transitions and oval blanks. Most plasma controllers accept DXF.
- Spiral tubeformer — for round duct, separately specified. The spiral duct sizing chart is the quick reference for sizing round runs against the Taokron tubeformer envelope.
For decision support on which configuration fits your throughput and BIM environment, see how to choose an auto duct production line. For end-to-end fittings fabrication including the connectors and accessories that travel with the auto duct line output, see the HVAC duct fittings fabrication guide.
FAQ
What is BIM-to-fabrication for HVAC ductwork?
The workflow that converts a coordinated Revit MEP duct model into machine-ready cut lists, spool drawings and CNC files driving plasma tables, coil lines and auto duct production lines on the shop floor. It replaces manual takeoff and re-drawing in CAMduct with a continuous data path from designer to machine, reducing rework and length variance.
What is the difference between Revit design parts and fabrication parts?
Design parts are the default Revit MEP duct elements — simplified placeholders sized for design intent and clash detection. Fabrication parts are real shop-floor components loaded from a CAMduct or CADmep ITM with seams, gauges, connector types, gasket grooves and supplier-specific dimensions that can be posted directly to a CNC machine. A duct shop must convert design parts to fabrication parts before any cut list, spool drawing or PLC file can be produced.
Which file formats can Taokron auto duct lines accept from BIM?
It depends on the line and its controller, so ask Taokron which job-file formats the controller on your line accepts. From a BIM workflow the usual candidates are an XML cut list (the CAMduct cut list export), DXF flat patterns for nested plasma cutting, a JSON job package and CSV (a basic cut list or the procurement bill of materials).
How long does it take to set up a Revit-to-Auto-Duct-Line workflow?
For a duct shop with an existing Revit MEP licence and a trained CAMduct or CADmep operator, plan 4–8 weeks: 1 week of audit and mapping the fabrication configuration to your machine tooling, 1–2 weeks building a connector library and gauge mapping, 1–2 weeks converting the pilot model and running a 50-piece pilot batch end-to-end, and 1–3 weeks of process tuning and scale-up. Shops without prior Autodesk Fabrication experience should plan 12–16 weeks including operator training.
What is the ROI on BIM-to-fabrication integration?
Payback depends on your duct volume, current takeoff effort and rework rate, so measure your own baseline before you start and again after a pilot. The main drivers are reduced length variance, fewer manual takeoff hours, less rework on fittings and faster procurement turnaround.
Can I run BIM-to-fab without Autodesk Fabrication CAMduct?
Yes. CAMduct is the most common path because it ships with Revit-compatible content, but third-party Revit add-ins such as MagiCAD for Revit and eVolve Mechanical for Revit can also export fabrication-ready data. Some shops use the IFC4 export from Revit combined with a custom IFC parser to produce a cut list for the line, typically as CSV or DXF. Native Revit design parts plus a Dynamo script can also produce a basic cut list, but this loses spool drawing automation and direct CNC posting.
What LOD does fabrication require?
Fabrication requires LOD 400 — geometry that includes actual fabrication seams, connector dimensions, gauge mapping, hanger locations, and accessory positions accurate to within manufacturing tolerance. LOD 200 (design intent) and LOD 350 (coordinated for clash) are not fabrication-ready. Most projects upgrade from LOD 350 to LOD 400 at the start of the shop drawing phase, typically 6–10 weeks before the first duct piece is required on site.
Does Taokron provide BIM consultation as part of an auto duct line purchase?
A Taokron engineer can talk through your BIM workflow and the job-file formats a given line accepts when you ask for a quotation. Operator training is part of the commissioning visit, as stated on each product page.
