VitruAI + Bluebeam
The VitruAI + Bluebeam integration writes structured markups, hyperlinks, and takeoff summaries into Bluebeam Revu through XFDF round-trip and the Bluebeam scripting API, tied to Bluebeam Revu 21+ on Windows with an eXtreme licence for scripting. It powers the Document AI Agent PDF-takeoff workflows for Bluebeam-led plan rooms and is available as a bespoke Labs engagement under MSA + Appendix.
- Reads and writes Bluebeam markups, hyperlinks, and tool sets through the XFDF round-trip plus the scripting API, without breaking existing standards.
- Drives window/door takeoff, mechanical-drawing PDF parsing, and plan-archive workflows for Bluebeam-led plan rooms.
- Ships as a Labs engagement under MSA + Appendix, co-designed around one pilot project before joining the roadmap product cohort.
Install, requirements, and what runs through the integration.
-
Bluebeam Revu 21+ on Windows
The integration targets Bluebeam Revu 21+ on Windows workstations, with the eXtreme licence required wherever the scripting API drives automated markups or hyperlink creation. Standard and CAD licences still participate fully in the XFDF import/export path, so estimators can review and edit AI-authored markups without scripting. Firms can mix licence types across teams as long as at least one eXtreme seat runs the scripted workflows.
-
PDF + XFDF round-trip into existing plan rooms
VitruAI reads PDFs exported from Revit, AutoCAD, ArchiCAD, or IFC tools and writes markups back as XFDF, so the plan room stays Bluebeam-led. XFDF payloads carry comments, statuses, layers, and hyperlink targets, which land in the same profiles estimators already use. For teams running Studio sessions, the same XFDF packets can be pushed into the active session so remote reviewers see new callouts and takeoff marks in ~single-digit minutes.
-
Tool-set aware markup generation
The integration reads the firm’s existing Bluebeam tool sets for architectural, structural, and MEP takeoff, then maps each Document AI rule to those symbols and colors. Agents extend the tool sets with new items where needed, but never overwrite or rename existing entries, preserving long-standing office standards. Window and door counts from window and door takeoff from PDF workflows appear as the same rectangles and legends estimators already trust, and mechanical elements follow the MEP tool set conventions.
-
Document AI rule packs tuned to your PDFs
VitruAI scopes a Document AI rule pack against the firm’s typical drawing styles, title blocks, and layer conventions, then binds those rules to Bluebeam markups. Window schedules, door tags, and MEP symbols are parsed by the Document AI Agent, and results feed directly into Bluebeam as comments plus CSV summaries. Those summaries can hand off to downstream quantity workflows such as the BOQ Takeoff Agent for line-item pricing and reconciliation.
-
Available now as a Labs engagement under MSA + Appendix
This integration runs today as a bespoke Labs engagement, scoped around one pilot project and a small set of drawing types. VitruAI works with your estimators and plan-room admins to script Bluebeam profiles, map tool sets, and validate rule-pack accuracy against a known project. Once the pilot hits agreed accuracy thresholds, the configuration rolls into the roadmap cohort for broader rollout across more projects and additional takeoff categories.
Bluebeam integration — common questions
-
Do we need Bluebeam Revu eXtreme?
You need at least one Bluebeam Revu eXtreme 21+ seat wherever the scripting API drives automated markups, hyperlinks, or batch processing. Teams running only Standard or CAD licences can still review, edit, and publish AI-authored markups through the XFDF round-trip path. Many firms run eXtreme on a plan-room admin machine while estimators and project managers work in Standard during Studio sessions.
-
Will it overwrite our existing tool sets?
No, the integration reads your existing tool sets and adds new items where needed rather than overwriting them. Architectural, structural, and MEP tools remain intact, so long-standing colors, line weights, and symbols still match firm standards. When new symbols are introduced for workflows like window and door takeoff from PDF, they are added as clearly named entries instead of replacing what your teams already use.
-
Can it land markups into a live Studio session?
Yes, for firms using Bluebeam Studio, XFDF markups can be posted into an active Studio session so reviewers see new callouts and takeoff marks without reloading drawings. Typical runs push window, door, and MEP markups into the same session where RFIs and coordination comments already live. Estimators can then adjust counts manually, export updated summaries, and pass quantities to tools like the BOQ Takeoff Agent for pricing.
-
How is this different from the AutoCAD or Revit integrations?
The Bluebeam integration works at the PDF and markup layer, not inside the design model itself. Upstream geometry still comes from Revit, AutoCAD, or other authoring tools, but the Document AI Agent reads the printed sheets and writes structured markups back to Bluebeam. Model-native checks, such as element-parameter review or clash-focused workflows, run through other agents and integrations rather than through Bluebeam Revu.