Overview

This guide walks through the full Dusty workflow for teams who are brand new to the system. It explains how the hardware, software, and Dusty team support work together before your first jobsite deployment and after you are up and running.

Throughout this process, the Dusty Academy is your primary self-serve learning resource. It includes short videos, step-by-step guides, and best practices for operators, VDC teams, and project leaders. Many customers rely on the Academy as their first stop for questions between projects or while ramping up new team members.

Dusty Academy: https://academy.dustyrobotics.com

This guide walks through the full Dusty workflow for teams who are brand new to the system. It explains how the hardware, software, and Dusty team support work together before your first jobsite deployment and after you are up and running.

Before your first on-site use, you can expect:

• Hardware delivery and initial coordination with Dusty
• File preparation and control alignment discussions
• Operator onboarding and training

Once you are live on a project, you will see:

• A repeatable workflow from model to printed layout
• Ongoing support from Dusty for questions, optimization, or issues
• Increasing independence as your team gains confidence

Why This Workflow Matters

Dusty is most successful when the field, VDC, and project teams are aligned early. Clear expectations around control, file prep, and site readiness help avoid delays, rework, or last-minute scrambling.

This workflow is designed to:

• Reduce risk before mobilizing to the field
• Make first-time printing predictable and successful
• Ensure you always know who to contact and when

How the Dusty System Works

Roles and Responsibilities at a Glance

Below is a high-level view of what is typically owned by your team versus supported by Dusty. Exact responsibilities may vary by account or service package, but this reflects the standard engagement.

Customer-Owned Responsibilities

• Project schedule and readiness for layout
• Providing or coordinating surveyed control
• Preparing or approving layout files
• Site access, safety, and power
• Operating the system day to day once trained

Dusty-Owned Responsibilities

• Hardware delivery and readiness
• Software access and system reliability
• Initial onboarding and training
• Ongoing technical support and guidance
• Workflow recommendations and best practices

If any responsibility is unclear, align with Dusty before mobilizing to the field.

1. Hardware: What Shows Up Onsite

Dusty is a system, not a single tool. The core components are:

• FieldPrinter robot that prints the layout directly on the slab
• A Laser tracker on a tripod that locates the robot in space
• iPad running the Dusty App to control printing
• Batteries, ink cartridges, and accessories for daily operation

Dusty coordinates shipment so the system arrives ahead of your planned deployment. Hardware is ready to use out of the box; no calibration or assembly is needed by your team beyond standard setup.

2. Software: From Model to Print

The Dusty software workflow connects the office and field. The main purpose of File preparation is to translate source Revit/AutoCAD files into automated layout files ( .dusty files) and to communicate only what's needed for the layout to be printed on site, which helps with clarity and collaborations across trades and field crews.

• Layout files are prepared by editing the supported geometry and filtering scopeand in AutoCAD or Revit using Dusty-supported workflows.
• Files are uploaded and managed in the Dusty Portal.
• The Dusty App syncs files to the iPad for field use.

Your team decides what information gets printed, such as walls, embeds, sleeves, text, dimensions, and more. Dusty does not change your design intent; it prints it at full scale, and each customer has an assigned VDC Solutions Specialist who guides and trains the team on Best practices for file prep.

3. Control: Aligning Digital to Reality

Accuracy on the field is affected by how accurately control points are laid out on site:

• Control is typically established by a surveyor or GC
• Control points tie the digital file to the physical slab
• Dusty uses multiple control points to verify accuracy before printing

If control is missing, unclear, or inconsistent, Dusty will flag it before layout begins. This is intentional and protects the project from downstream errors.

Pre-Onsite: What Happens Before First Deployment

Ownership and Expectations (Pre-Onsite)

Customer Responsibilities

• Identify a first project and Scope
• Confirm who owns file preparation and robot operation
• Coordinate with the survey or GC to establish control
• Share project constraints, schedule, and risks early

Dusty Responsibilities

• Confirm hardware shipment and readiness
• Provide onboarding and training resources
• Review files on the Dusty Portal before implementation

Step 1: Kickoff and Expectations

Early on, Dusty works with your team to understand:

• Project type and schedule
• Who owns file prep, and who operates the robot
• How will it be provided

This is the right time to raise any concerns about survey workflows, site conditions, or internal ownership.

Step 2: File Preparation Alignment

Before going on-site:

• A print-ready dusty file and csv file for Control/tarde points must be prepared and published on the portal by the customer's VDC team
• Share onsite pictures of control and site conditions.

Step 3: Training and Onboarding

Dusty provides onboarding tailored to your roles:

• Operators learn how to set up, station, and print
• VDC teams learn how to prepare and publish files
• Project teams learn how to plan for Dusty in the schedule

In parallel, customers are expected to use the Dusty Academy to reinforce training and support long-term adoption:

Dusty Academy: https://academy.dustyrobotics.com
Dusty provides onboarding tailored to your roles:

• Operators learn how to set up, station, and print
• VDC teams learn how to prepare and publish files
• Project teams learn how to plan for Dusty in the schedule

Onsite: What a Typical Day Looks Like

Ownership and Expectations (Onsite)

Customer Responsibilities

• Ensure the slab is safe, accessible, and ready for printing
• Control points are laid out on site
• Set up and operate the system following training
• Communicate conflicts with other trades or activities

Dusty Responsibilities

• Provide real-time or near-real-time support when issues arise
• Help diagnose, control, file, or set up problems
• Advise when issues are site-related versus system-related

Once deployed, a standard Dusty workflow looks like this:

1. Prepare the site – slab is accessible, safe, and reasonably clean
2. Set up the tracker and robot – one operator, typically under 30 minutes
3. Record control points – verify alignment and accuracy
4. Print layout – select content and print directly from the model
5. Verify and wrap up – confirm results and move to the next area

Once deployed, a standard Dusty workflow looks like this:

1. Prepare the site – slab is accessible, safe, and reasonably clean
2. Set up the tracker and robot – one operator, typically under 30 minutes
3. Record control points – verify alignment and accuracy
4. Print layout – select content and print directly from the model
5. Verify and wrap up – confirm results and move to the next area

After Go-Live: Ongoing Support and Growth

Ownership and Expectations (After Go-Live)

Customer Responsibilities

• Apply lessons learned to future projects
• Maintain trained operators and file prep coverage
• Flag recurring issues or workflow gaps
• Plan Dusty use earlier in project schedules
• Use the Dusty Academy to onboard new team members

Dusty Responsibilities

• Continue providing technical and workflow support
• Share best practices from similar customers
• Assist with scaling to new teams or projects
• Support continuous improvement and optimization

Dusty Support 

Dusty does not disappear after the first use. Support includes:

• Remote troubleshooting for hardware or software issues
• File prep assistance when workflows change
• Guidance on improving speed, accuracy, or collaboration

How Teams Typically Mature

Most customers follow a similar path:

• First project: heavy coordination and questions
• Next few projects: growing confidence and speed
• Long term: internal champions and standardized workflows

Dusty’s goal is to make your team self-sufficient while staying available when needed.