VDC Reference Guide

VDC File Prep
Best Practices

A trade-by-trade guide for getting from coordinated model to accurate layout on the slab — cleanly, efficiently, and with every trade aligned before the robot touches the floor.

Trades Covered Framing · Electrical · Mechanical · Plumbing
Stay Current
Check release notes for the latest Dusty updates, new features, and product changes.
▶ Release Notes: New Dusty Features Support & FAQs vdcsupport@dustyrobotics.com

📋 How to use this guide

This is an interactive guide — open it in any web browser (Chrome, Edge, Safari) and use the tabs at the top to navigate between sections. Start with Getting Started and Workflow to understand the end-to-end process, then use Universal Standards and By Trade for trade-specific file prep best practices. Checkboxes are interactive — check them off as you go. You can also save or print a copy from your browser using Ctrl+P (or Cmd+P on Mac).

Section 01

Getting Started

A reference for your team to work from as you prep files for Dusty.

💻
What Software Do I Need?
Make sure your team has the right tools set up before starting file prep
SoftwareRequirementNotes
Revit Recommended Version 2020 or above. Dusty's workflow is designed to leverage the model you've already built, using view templates, Dynamo scripts, and family tags to prepare and export your files.
AutoCAD / AutoCAD Architecture Required Version 2019 or above. The Dusty AutoCAD Plugin exports your drawing as a .dusty file directly to the Dusty Portal.
CSV (spreadsheet) Required for points Control points and MEP hanger/support locations are uploaded as CSV files to the Portal. Compatible tools include Excel, Google Sheets, Autodesk Point Layout, Trimble, and others. Always keep a reference showing where your points align relative to your Dusty files.
💡
Even if your team primarily works in Revit, AutoCAD is still required to run the Plugin export step.
🎯
Before You Begin
Set expectations across the team on scope and priorities
Print what matters most — not everything. Ensure clash detection is complete and all trades are in sync before file prep begins. Prioritize what scope is most critical to have on the floor. Think in two buckets: must-haves (what the field cannot start without) and nice-to-haves (useful context if time and ink allow). The goal is to communicate more with less — simplify your layout to what actually drives installs, and print it efficiently. Multi-trade success comes from communication and trade alignment first.
Scope Planning Checklist
Team Roles
RoleResponsibility
VDC Coordinator Coordinates across all trades, runs QA on combined files, manages the Portal, owns final sign-off before publishing
Trade VDC Lead Preps their trade's Dusty files, coordinates with the VDC Coordinator, reviews and signs off on their trade's layer content before printing
Dusty Operator Sets up and operates the FieldPrinter on site, communicates field conditions back to VDC
Prerequisites Checklist

Section 02

BIM-to-Field Workflow

End-to-end — from coordinated model to printed layout on the slab. Revit → AutoCAD → Dusty AutoCAD Plugin → Portal → Publish → Print.

1
Zone Locked — Coordination Complete
Clash detection is resolved and all trades signed off for the print zone. Design changes can be made on the Portal but should be discussed internally before making any edits.
📌Define a "freeze date" per zone. Post-freeze changes get a new revision number — no ad-hoc file swaps.
2
Duplicate View in Revit → Set Scale → Apply Templates
Duplicate the view (don't modify the working view). Set scale to 12" = 1'. Apply Dusty View Templates. Make necessary text height edits to tags. Run Dynamo cleanup script if applicable.
3
Export to AutoCAD → Clean Up
Export view to AutoCAD (.dwg). Delete hatches. Explode arrays/attributes and double-check dynamic blocks. Confirm text heights to ½", 1", or 2". Freeze layers not needed in print. Freeze any point layers that should be uploaded as separate CSV files to the Portal.
4
Dusty Plugin: Pre-Process → Export
Pre-Process gives you a preview of what the file will look like before you export to the Dusty Portal. Use Ctrl+Z if you need to make edits. Always save a backup before running the Plugin. Once all edits are confirmed, use "Export File to Dusty" to export from .dwg to the .dusty file in the Dusty Portal.
5
Upload to Portal → Review → Sign Off → Publish
VDC Coordinator and Trade VDC Lead review the visual preview on the Dusty Portal. Zoom into complex areas — corners, mechanical rooms, restrooms, etc.
6
FieldPrinter Prints — Multi-Trade in One Pass
Operator sets up Laser Tracker, localizes to control points, and initiates printing. Feedback from field teams to the VDC team makes the process more efficient over time.
7
Revisions → Re-export → Re-sign Off
Any design change generates a new revision Dusty file. Review the Dusty Portal tutorial for how to manage revisions and updated files. Re-export, re-upload, re-sign off, and always notify the field crew before they start work on a revised layout.
📋A print change the field doesn't know about is worse than no change at all.

Section 03

Universal Standards

These apply to every trade and every file before any trade-specific prep begins.

📍
Coordinate System
The single most important thing to get right across all trades
⚠️
All trade files need to reference the same starting point. Before exporting, confirm with every trade that their files overlay correctly when placed on top of each other. Dusty does not detect or correct misaligned files. If files don't overlay in your model, they won't align on the slab. This must be resolved before uploading to the Dusty Portal.
✅ Files overlay correctly — trades are aligned
FRAMING MEP Framing MEP
Both files use the same reference point. When overlaid, the geometry lines up — Dusty prints each trade's content exactly where it belongs on the slab.
❌ Files are offset — content won't land in the right place
FRAMING should be here MEP OFFSET
The MEP file references a different starting point. When overlaid, geometry doesn't match — Dusty can't detect or correct this, and that trade's content will print in the wrong location.
Coordinate Checklist
⚙️
AutoCAD Settings & Layer Management
Get these right before running the Dusty Plugin
📐
Units and scale first. Before using the Dusty AutoCAD Plugin, confirm units are set to Inches (Length Type = Architectural, Insertion Scale = Inches) and your drawing is to scale. If using metric, contact vdcsupport@dustyrobotics.com before proceeding.
Layer Cleanup
Text & Geometry
🚧
Obstruction File
Tells the robot where it cannot travel — required for every project
🖥️
Using the Dusty Portal
Upload, review, and publish your print files — all trade sign-offs happen here before anything reaches the FieldPrinter
📌
The Portal is your central hub for file management and publishing. After exporting your Dusty file, all uploads, previews, and publishing are managed here. Each trade's VDC Lead should review the visual output before the file is published on the Portal.
Portal Workflow Checklist
▶ How It Works and Dusty Portal ▶ Points and Specialty File Prep ▶ Multi-Trade with Dusty Portal

Section 04

By Trade

Select a trade. Each tab covers what to include and the exact export steps to follow.

🏗️ Framing / Drywall

Full wall information on the floor — stud placement, wall types, fire ratings, and rough openings. Your crew starts framing immediately, no measuring required.

💡
Minimum linework, maximum clarity. Every line should have a reason to be there. Excess geometry slows print time and clutters the slab.
File Prep Checklist Best practices
💡

Use layers and line types to distinguish framing tracks from finish layers so crews can tell what's what on the printed layout. For fire-rated and shear walls, use Revit filters and modify your DWG export settings to map them into separate layers when exporting to AutoCAD.

Keep door and window rough openings simple. Use the Dusty Door Tag with minimum lines and avoid complex tag families that add unnecessary linework.

Include gridlines at full extents (don't trim them for crop regions or pour zones). They help provide context for control points when an operator sets up a station. Show the concrete edge of slab near the perimeter for reference.

Export Steps Revit → AutoCAD → Portal
1
Duplicate your view in Revit — name it descriptively (e.g., DR_L2_Framing_Dusty). Never modify your working view.▶ Review tutorial: Dusty Revit Process
2
Set Revit view scale to 12" = 1' — ensures text at 1" or ½" height is correctly scaled for print.▶ Review tutorial: Dusty Revit Process
3
Apply Dusty View Templates and run the Dusty Dynamo Script to clean up multi-layer gypboard (combines plywood + gypboard layers).▶ Review tutorial: Dusty Revit Process · ⬇ Download: Dusty Revit Export Resources (View Templates & Dynamo Scripts)
4
Export to AutoCAD (.dwg). Delete hatches, explode arrays, confirm text heights and review geometry (lines and arcs). Make any edits needed within AutoCAD before exporting to the Portal.▶ Review tutorial: Dusty AutoCAD Plugin
5
Dusty AutoCAD Plugin → run "Pre-Process" to review, then Export Dusty File to the Portal.▶ Review tutorial: Dusty AutoCAD Plugin
6
Upload to Portal → review preview → Trade VDC Lead sign-off → Publish.▶ Review tutorial: How It Works and Dusty Portal · ▶ Review tutorial: Multi-Trade with Dusty Portal

⚡ Electrical

Device rough-in, conduit pathways, panel footprints, and under-slab runs printed directly on deck — install to the coordinated model, not tape measures.

💡
Avoid small circles. Receptacle symbols with small circles take significantly longer to print. Use a simplified symbol or text label with leader instead.
File Prep Checklist Best practices
💡

Simplify device symbols and rough-in geometry. Avoid small circles for receptacles, data, comm, and low-voltage devices as they take significantly longer to print. Use simple outlines or text labels with leaders instead, and use Revit family tags to add detail like type, mounting height, and circuit info. For discrete device locations, consider using CSV point files instead of linework.

Use layers to separate under-slab conduit from above-slab, and coordinate print timing with the concrete pour schedule. Keep conduit pathways from the coordinated model and simplify sleeves to outlines.

Simplify equipment footprints (panels, transformers, switchgear, lighting fixtures) to outlines. Use Revit family tags for additional detail rather than complex geometry.

Export Steps Revit → AutoCAD → Portal
1
Duplicate your view in Revit — name it (e.g., DR_L2_Electrical_Dusty).▶ Review tutorial: Dusty Revit Process
2
Set Revit view scale to 12" = 1'.▶ Review tutorial: Dusty Revit Process
3
Export to AutoCAD (.dwg). Delete hatches, explode arrays, confirm text heights and review geometry (lines and arcs). Make any edits needed within AutoCAD before exporting to the Portal.
4
Dusty AutoCAD Plugin → run "Pre-Process" to review, then Export Dusty File to the Portal.▶ Review tutorial: Dusty AutoCAD Plugin

🌀 Mechanical

Ductwork centerlines, equipment pads, hanger locations, and penetrations on deck — crews hang duct, not tape measures.

💡
Centerlines, not full outlines. Printing full duct outlines takes significantly longer. Centerlines convey the same install intent in a fraction of the print time. Use CSV points for hangers.
File Prep Checklist Best practices
💡
Use centerlines for ductwork instead of full duct outlines and individual fittings — full outlines result in a much slower print. Use the Dynamo script to extract centerlines for MEP Fabrication categories, Revit family tags for duct size labels at transitions, and CSV files for hanger locations and diffuser points instead of linework (see the CSV / Points tab for formatting). Simplify equipment pad footprints (AHU, RTU, FCU) and slab penetrations to outlines — use Revit family tags for more detailed information, and place duct penetrations through fire or smoke barriers on a separate layer.
Export Steps Revit → AutoCAD → Portal
1
Duplicate your view in Revit — name it (e.g., DR_L2_Mech_Dusty).▶ Review tutorial: Dusty Revit Process
2
Set Revit view scale to 12" = 1'.▶ Review tutorial: Dusty Revit Process
3
Export to AutoCAD (.dwg). Delete hatches, explode arrays, confirm text heights and review geometry (lines and arcs). Make any edits needed within AutoCAD before exporting to the Portal.▶ Review tutorial: Dusty Revit Process
4
Dusty AutoCAD Plugin → run "Pre-Process" to review, then Export Dusty File to the Portal. Upload hanger CSV separately.▶ Review tutorial: Dusty AutoCAD Plugin · ⬇ User Guide: Points Import/Export on AutoCAD

💧 Plumbing

Under-slab rough-in, floor drains, cleanouts, and fixture rough-in printed on the concrete — set sleeves and rough-in right the first time.

File Prep Checklist Best practices
💡
Simplify rough-in geometry into centerlines, outlines, or CSV files — piping, drains, cleanouts, stub-ups, fixture locations, sleeves, and equipment pads should all be easy to read at print scale. Use the Dynamo script to extract centerlines for MEP Fabrication categories, Revit family tags to add detail instead of complex symbols, and CSV files for hanger and support rod locations instead of linework (see the CSV / Points tab for formatting). Use dedicated layers to keep content organized.
Export Steps Revit → AutoCAD → Portal
1
Duplicate your view in Revit — name it (e.g., DR_L2_Plumbing_Dusty).▶ Review tutorial: Dusty Revit Process
2
Set Revit view scale to 12" = 1'.▶ Review tutorial: Dusty Revit Process
3
Export to AutoCAD (.dwg). Delete hatches, explode arrays, confirm text heights and review geometry (lines and arcs). Make any edits needed within AutoCAD before exporting to the Portal.▶ Review tutorial: Dusty Revit Process
4
Dusty AutoCAD Plugin → run "Pre-Process" to review, then Export Dusty File to the Portal. Upload support CSV separately.▶ Review tutorial: Dusty AutoCAD Plugin · ⬇ User Guide: Points Import/Export on AutoCAD

📊 CSV / Point Files

The most efficient way to represent discrete locations — hangers, drains, anchor bolts, devices — without adding linework.

When to use CSV instead of geometry: mechanical hangers, plumbing supports, diffuser centers, receptacle locations, control points — any discrete point that doesn't need a line.
Format Requirements Strict 5-column format
🚨
5 columns only — no more, no fewer. Additional columns cause import errors. Do not leave X, Y, or Z coordinate columns blank — blank coordinate values will cause upload errors in the Portal. Be mindful of which unit format your coordinates are in — when uploading to the Portal, make sure to update the unit setting accordingly so Dusty interprets the values correctly.
ColumnFieldNotes
1stPoint Name2–3 words or a short ID — e.g., 1483, AB-01, HG:10E
2ndX CoordinateUse decimal format — e.g., 125.75 not 125' 9"
3rdY CoordinateUse decimal format
4thZ CoordinateUse decimal format
5thDescription2–3 words; use abbreviations where possible to avoid overlaps when printed — e.g., Hanging Rod, H:CRL, SS
⚠️
If the Point Name and Description columns are left blank, Dusty will still print the crosshair marker at each location — but with no identifying text alongside it.
What the Field Team Sees on the Slab
Dusty prints a crosshair marker at every point location. If the Point Name and Description columns in your CSV have values, that text prints alongside each marker.
Name + Description filled
1483: Hanging Rod
1059: Threaded Rod
1857: SS
1684: Hanging Rod
1751: Hanging Rod
NameXYZDesc
1483125.7548.200Hanging Rod
1059132.1051.850Threaded Rod
1857128.9046.300SS
Name + Description blank
NameXYZDesc
(blank)125.7548.200(blank)
(blank)132.1051.850(blank)
(blank)128.9046.300(blank)
Dusty offers multiple point styles to choose from, which can be edited on the Portal and iPad for each CSV file.
CSV Checklist
QR Codes
Give field crews instant access to reference documents directly from the slab
💡
Print QR codes alongside your layout to give field crews instant access to shop drawings, submittals, or reference documents.

Section 05

Dusty Academy Resources

Complete these before your first print. academy.dustyrobotics.com →

Dusty Robotics
Questions? vdcsupport@dustyrobotics.com
dustyrobotics.com · academy.dustyrobotics.com
VDC File Prep Best Practices · 2026