Revit Add-ons

Product Roundup: Penguin Tools (PTP)

2026-10-18T14:06:23.904-07:00

From the Autodesk Design and Make Marketplace:

About

Hi there! We are a two-person team dedicated to building practical, time-saving plugins for Revit. After developing a range of internal automations to optimize our own projects, we decided to release them publicly to support fellow BIM managers, architects, and engineers.

Our goal is to keep over 90% of our add-ins completely free. The few exceptions involve tools with ongoing maintenance costs—such as cloud services and database hosting—which help support our infrastructure and keep the rest of our library free for everyone.

Community feedback drives our roadmap. If you have an idea for a plugin that would make your life easier, or feedback on our existing tools, don't hesitate to reach out!

Editor's Note: Ratings are static and accurate at press time. For up-to-date ratings, visit the Autodesk Design and Make Marketplace.

Auto Sync Pro

Automate your Autodesk® Revit® workflow with timed background synchronization, scheduled saves, idle exit, and smart model maintenance to keep your team efficient. | Free

No ratings yet

Bulk Rename Pro

Batch rename Autodesk® Revit® Views, Sheets, Levels, Grids & Elements with powerful regex, casing, and rule presets. | Free

No ratings yet

Color Tabs Pro

Visual organization for Autodesk® Revit® made simple. Automatically color-code your document tabs by Project, Family, or View Type to never get lost in a cluttered interface again. | Free

No ratings yet

Model Upgrader Pro

Batch upgrade Autodesk® Revit® models cleanly without opening views. | Free

No ratings yet

Opening Handing

Automatically calculate, map, and audit door and window swing handing directions (LH, RH, LHR, RHR). | $3/month or $30/year

No ratings yet

Revision Manager Pro

Master your revision workflows with ease. Create, manage, and bulk-apply revisions across hundreds of sheets in seconds. Features smart filtering, regex search, Excel export, and a custom date format. | Free

No ratings yet

Section Box Pro

Instantly create precise 3D views around selected elements in Autodesk® Revit®, with smart auto-naming, batch view creation, and quick buffer presets for faster detailing. | Free

★★★★★ (1 review)

Version QR Codes

Connect Your Drawings to the Digital World.

Penguin Tools brings the power of the digital twin directly to your printed sheets. The QR Code Exporter is a professional-grade module designed. | $15/month or $150/year

No ratings yet

View Duplicator Pro

Batch duplicate Autodesk® Revit® Views & Sheets with naming rules, Scope Box, Phase, and auto Sheet placement. | Free

No ratings yet

Free View Duplicator Pro: Create Organized, Predictably Named Deliverables

2026-10-17T15:24:00.000-07:00

Overview

View Duplicator Pro is a free Revit add-in from Penguin Tools for batch-producing views and sheets. It is aimed at BIM managers and architectural, structural, and MEP teams that repeatedly create similar floor plans, reflected ceiling plans, elevations, 3D views, dependent views, or complete sheet sets. The add-in consolidates source selection, duplication method, naming, view-property overrides, sheet creation, and viewport placement into a visual workflow. Its core value is not merely copying views; it is creating organized, predictably named deliverables while reducing repetitive Revit commands and avoidable naming errors.

Core Workflow

Select source content. Choose one or more existing views or sheets that will act as the basis for the new deliverables.
Choose a duplication mode. Create standard copies, copies with annotations, dependent views, or duplicated sheet sets.
Build target names. Apply prefixes, suffixes, or find-and-replace rules, then inspect the live preview before making changes to the model.
Resolve conflicts. Review collision warnings where a proposed name already exists and manually override individual names when exceptions are required.
Apply view settings. Assign or replace View Templates, Scope Boxes, and Phases for the copies.
Create sheets and place views. Where required, create new sheets with a selected title block and place the duplicated views automatically. When entire sheets are duplicated, preserve the relative viewport layout.
Review the result. Validate generated names, crop regions, templates, phases, sheet numbers, viewport placement, and annotation behavior before issue.

Duplication Modes

Duplicate: Creates a standard independent copy without view-specific detailing. This is useful when the new view should inherit model visibility but develop its own annotations.
Duplicate with Detailing: Copies the view with view-specific content such as text, tags, dimensions, detail lines, and keynotes. This best fits deliverables that need a close starting copy of an annotated view, but copied annotations still require QA.
As Dependent: Creates a dependent child view linked to its parent. This supports split plans and other coordinated views that share annotation and model context while using separate crop regions.
Sheet Set Duplication: Recreates entire sheets with their placed views and maintains relative viewport positions and title-block alignment. This can accelerate parallel documentation packages, phases, zones, or disciplines.

Naming and Collision Management

The live naming engine is a central control feature. Users can preview proposed view or sheet names, append standardized prefixes and suffixes, and replace strings across a batch. Examples include adding a project code, discipline identifier, phase label, or zone designation. The add-in flags proposed names that conflict with existing model content, helping prevent failed transactions or unwanted Revit-generated copy names. Individual preview rows can be manually edited for legitimate exceptions. Together, preview, collision detection, and row-level overrides provide a balance between standardization and project-specific control.

View and Sheet Automation

View Template assignment: Apply or switch templates on duplicated views in one operation, supporting consistent graphics and discipline standards.
Scope Box overrides: Assign copies to areas such as towers, wings, podiums, cores, or phases, reducing the effort required to prepare area plans.
Phase assignment: Set new views to project phases such as Existing, Demolition, or New Construction during creation.
New-sheet creation: Generate sheets using a selected title block and place duplicated views without manually opening each sheet.
Layout preservation: Retain relative viewport positions when reproducing existing sheets, which is especially useful for standardized packages.

Benefits for BIM Production

Faster repetitive setup: Combines several manual operations into a single batch process, with the greatest potential benefit on projects containing repeated areas, phases, disciplines, or drawing packages.
Improved naming quality: Preview and collision checks expose problems before creation, making it easier to enforce a view-naming standard.
More consistent graphics: Template, scope-box, and phase assignments can be applied at generation time rather than corrected afterward.
Reduced sheet-layout work: Automated sheet creation and retained viewport relationships can remove substantial placement and alignment effort.
Better scalability: The workflow can support setup of multiple deliverables while still allowing manual exceptions where strict batch rules do not fit.

Limitations and QA Considerations

Automation does not validate design intent: A correctly duplicated view can still show the wrong content for its purpose. Teams must review visibility, crop, scale, discipline, phase filters, and annotations.
Detail copying can propagate defects: Duplicate with Detailing may reproduce outdated notes, dimensions, tags, keynotes, or drafting items. Copied content should be checked against the target context.
Dependent views behave differently: Because dependent views remain linked to a parent, teams should confirm crop, matchline, annotation, and sheet-composition expectations.
Sheet duplication may encounter constraints: Certain views, schedules, legends, or other placed content can have Revit-specific placement or duplication restrictions. The public product description does not document every exception.
Naming must address both views and sheets: A project standard should define view names, titles on sheet, sheet numbers, and allowable exceptions before a large batch is run.
Transaction size matters: Large jobs should be tested on a representative subset and saved before execution. The public listing does not state a maximum supported batch size.

Recommended Implementation Approach

Document the team’s approved view, title-on-sheet, and sheet-number naming rules.
Prepare stable View Templates, Scope Boxes, Phases, and title-block families before running the tool.
Pilot each duplication mode with typical architectural, structural, and MEP content.
Test conditions that are likely to cause conflicts, including existing target names and sheets containing varied viewport types.
Review the live preview and resolve every flagged collision rather than relying on automatic fallback names.
Run the batch, then perform a structured QA check of view properties, annotations, crops, sheets, and viewport locations.
Record repeatable settings and examples in the BIM execution plan or internal production guide.

Assessment

View Duplicator Pro addresses a common production bottleneck with a focused combination of batch duplication, naming control, property assignment, and sheet automation. Its most valuable features are the preflight naming preview, collision detection, simultaneous View Template/Scope Box/Phase assignments, and preservation of viewport arrangements during sheet duplication. These capabilities can materially improve setup speed and consistency on repeated documentation packages. The add-in should nevertheless be treated as a production accelerator, not an automatic QA system. Its effectiveness depends on prepared standards, correctly configured source views, and disciplined post-generation review. Because it is currently listed as free, it is a low-cost candidate for a controlled pilot, subject to compatibility, installer, and internal IT review.

Sources

Autodesk Design and Make Marketplace — View Duplicator Pro. Used for the official marketplace description, feature set, free pricing status, installer note, support details, and public rating status.
Penguin Tools — View Duplicator Pro product page. Used to confirm the vendor’s positioning, intended users, duplication modes, naming controls, and view-parameter overrides.

View Duplicator Pro is brought to you by Penguin Tools (PTP). It's free.

This add-in is compatible with Revit 2025-2027.

There's more information available on the Autodesk Design and Make Marketplace »

Questions? Contact the developer »

Version QR Codes: Drawing Version Control

2026-10-16T17:36:00.000-07:00

Overview

Version QR Codes is a Revit add-in from Penguin Tools that connects issued or printed sheets to live digital information through unique QR codes. Its principal use is drawing version control: a person in the office or on site scans the code with a standard phone or tablet camera to reach the latest PDF, a common data environment (CDE) location, a project URL, or a 3D model, and can determine whether the physical drawing is current or superseded. The product is intended to close the information gap between paper deliverables and the project’s digital source of truth. Penguin Tools reports more than 19,000 active codes in use; this is a vendor claim rather than independently verified usage data.

How It Works

Define the identifier. By default, the add-in uses the Revit Sheet Number. Users can combine built-in parameters and custom shared parameters assigned to the Sheets category to form a drawing name or data payload.
Configure a profile. A profile controls appearance, data links, and title-block placement. Profiles can be created for purposes such as client issue or internal review, saved for reuse, and loaded from a central network location to support company standards.
Generate and place codes. The add-in can create one code or batch-generate many unique codes and place them on title blocks. The vendor advertises generation of up to 1,000 codes in one operation.
Publish the deliverable. Codes can be carried into PDF, DWG, or DXF output, or exported as standalone PNG/JPG images for reports, labels, or stickers.
Scan and verify. The recipient scans the code without a proprietary viewer. The linked destination provides access to current information so the recipient can check the drawing’s status before using it.

Key Capabilities

Revit-aware data linking: Uses sheet parameters and project URLs rather than requiring codes to be prepared manually in a generic web generator.
Batch automation: Produces unique codes at scale and positions them consistently on title blocks, reducing repetitive sheet-by-sheet work.
Visual customization: Supports standard, dots, rounded, and modern pixel styles; preset or advanced colors; left-to-right, top-to-bottom, radial, and other gradients; and a centrally embedded PNG company logo. The listing states that logo placement uses error correction to preserve scan reliability.
Reusable standards: Named profiles capture configurations for different issue purposes. External profiles can provide centrally managed settings for multi-user deployment.
Multiple outputs: Codes can appear in PDF and CAD exports or be delivered as raster images, extending their use beyond native Revit sheets.
Mobile accessibility: Standard smartphone and tablet cameras can read the codes, avoiding a dedicated field application or specialized hardware.

Value for BIM and Construction Workflows

The add-in’s strongest use case is reducing the risk of building from an obsolete paper set. A scan gives field staff a quick verification path to the controlled digital source, potentially exposing a newer revision before work proceeds. This can reduce rework, delays, and time spent locating documents. It also gives BIM and document-control teams a consistent method for linking physical sheets to a CDE, latest PDF set, or model while retaining company branding. These benefits depend on sound publishing governance: the QR target, sheet identifiers, revision data, and permissions must remain accurate and available.

Implementation Considerations

Define governance first: Decide which destination is authoritative, who updates it, and how long links must remain valid.
Standardize identifiers: Establish parameter combinations that stay unique across projects, packages, disciplines, and revisions.
Test print and scan quality: Validate minimum size, contrast, logo treatment, gradients, printer output, photocopies, and weathered field copies before deployment.
Confirm access: A code is only useful if intended recipients can open the target on their devices. Review CDE authentication, external-user permissions, connectivity, and offline contingencies.
Control profiles: Store approved profiles centrally where appropriate, restrict uncontrolled variants, and document the title-block insertion standard.
Pilot before scaling: Test a limited sheet set through authoring, export, upload, print, scan, revision, and archive cycles. Confirm how replaced or superseded content is presented.
Review IT requirements: Because the application uses a custom installer and creates externally resolved links, deployment, security, privacy, firewall, and data-retention requirements should be reviewed.

Assessment

Version QR Codes is a focused bridge between Revit sheet production and field document verification. Its principal differentiators are native access to sheet parameters, automated title-block placement, large-batch generation, branded styling, reusable profiles, and support for several publishing formats. It is most valuable where printed drawings continue to circulate alongside controlled digital information. It does not replace a CDE, revision procedure, or document-control policy; it provides a fast access and verification layer over those systems. A well-governed deployment could improve QA/QC and reduce superseded-document risk, while a poorly maintained link strategy could create false confidence. The add-in is therefore best evaluated through a controlled pilot using representative projects and field conditions.

Sources

Autodesk App Store — Version QR Codes (current English listing). Used for current features, supported Revit versions, release information, pricing, trial period, installation method, and support details.
Penguin Tools — Version QR Codes product page. Used for the product overview, workflow, drawing-version-control purpose, and vendor-reported usage.

Exporter_QR_DataLink

Exporter_QR_Dashboard

Exporter_QR_Sheet

Exporter_QR_ExternalPaths

Exporter_PM_Dashboard

Exporter_PM_Help

Current

Not Current

Version QR Codes is brought to you by Penguin Tools (PTP). It's priced at $15/month or $150/year. A 30-day free trial is available.

This add-in is compatible with Revit 2025-2027.

There's more information available on the Autodesk Design and Make Marketplace »

Questions? Contact the developer »

Orkestra Review: Distributing Tools—Dynamo or Grasshopper Graphs or OkPy Add-ins

2026-10-15T18:26:58.552-07:00

Editor's Note: This is a sister article to OkPy Review: Create Fully Functional Revit Add-ins with Zero Coding, with Examples!

Orkestra can be used for a couple different things. One is developing Revit add-ins with OkPy, which we've already covered. The second is distributing customizations in a managed way, whether they are OkPy-authored add-ins or Dynamo or Grasshopper graphs.

The first step is publishing. If it's an OkPy add-in, you'll need both OkPy Pro and Orkestra subscriptions. For Dynamo and Grasshopper, an Orkestra subscription will suffice. For our example, we're going to work with the Color Warnings add-in from our OkPy review.

From the OkPy for Revit window, with the OkPy file loaded, click the Publish button:

The Publish to Orkestra window opens. There's some work to be done in this dialog: there's the Description, which is also the tooltip in Revit, the Body, which is the text for a wiki entry (this is what the user will see if they click on More Info in the tooltip), and Keywords:

Fortunately, if you're working with OkPy, the AI agent will do the work for you. Simply click on Draft with agent and the AI will create pitch perfect documentation for you:

Beautiful!

A note about the two icons the AI generates in the above step: consider them placeholders. You'll get a much more polished result in a later step.

Clicking Publish again will open the Publish your tool window. Here you'll select a destination for your tool. You can select an existing folder or create a new one. The only really important thing in this step is that you can find your tool in a later step.

Click Publish a third time and you're done with the publishing process.

For the next step, you'll need the Orkestra desktop app. To access it, in the Orkestra palette in Revit, click the gears icon:

This opens the Orkestra Revit Addin window. In the lefthand pane, click on QuickAccess. In the top bar, pick Ribbon Builder. Set your Revit version (for our purposes we'll use 2026):

(Astute readers may notice that we've created two new add-ins since our OkPy review: View Sheets By Element and Visibility/Graphics Off By Element.)

If you already have a tab and panel defined as I do (sorry, but we don't want to delete them), you can use them, or, to create a new tab, click the + symbol along the top of the preview:

In the Create a new Tab window, name the tab. We'll use "Revit Add-ons:"

Click Create. The tab is added to the preview. To create a panel, click on the + symbol below the tab:

In the Create a new Panel window, give the panel a name. We'll use "Warnings:"

Click Create. The panel is added to the preview. To create a button, click on the + symbol above the panel name:

Select either Add QA button or Add dropdown group. We'll click Add QA button.

In the Create Quick Access ribbon button window, browse to your tool definition:

Click Continue. If working with OkPy add-ins, remove ".okpy" from the UI Name.

Click on the icon and in the Replace icon window, click AI Icon Generator. Type a simple but meaningful prompt. We'll use "Warning icon with gradient color, red to yellow to green." Orkestra will return two icons. Click Apply under the one you like. Finally, click Create. The button is added to the preview.

Click Update Ribbon:

The UI is written to Revit:

Test your button!

It's a bit of a process, but easy once you're used to it. It wasn't especially easy to discover though.

One nice feature is that the interfaces are portable between the Revit versions. We were afraid that we'd have to recreate our buttons in Revit 2025, but we didn't have to. We simply selected 2025 and clicked Update Ribbon!

Grade: A

Revision Manager Pro: Make Revision Administration Faster and More Consistent

2026-10-14T17:27:00.000-07:00

Executive Summary

Revision Manager Pro is a free Revit productivity and QA/QC add-in from Penguin Tools designed to simplify revision creation, editing, sheet assignment, removal, and reporting. It organizes the work into two main stages: first managing the project’s revision records, and then applying selected revisions to filtered groups of sheets. Its strongest value is scale: operations that normally require repeated dialog navigation and sheet-by-sheet checking can be carried out across hundreds of sheets through a reviewable interface.

Core Capabilities

Two-step interface: Separates revision definition and maintenance from revision-to-sheet assignment, making the workflow easier to understand and audit.
Revision creation: Creates new project revisions and supports quick templates for recurring descriptions such as Tender, Construction, or other office-standard issue stages.
Description history: Reuses standard or previously entered descriptions to reduce retyping and improve consistency.
Bulk editing: Updates descriptions or dates for multiple revision records at the same time.
Bulk sheet assignment: Applies a selected revision to large numbers of sheets with a single action.
Smart sheet filtering: Narrows the sheet list by sheet sets, disciplines, issued status, the presence of revision clouds, or particular revisions.
Regular-expression search: Supports advanced pattern searches for both revisions and sheets, enabling precise matching of sheet numbers, names, prefixes, or other naming conventions.
Date-format builder: Provides a visual drag-and-drop method for constructing revision date formats that align with office or client standards.
Undo Last Set: Reverses the most recent revision-assignment operation, providing a safeguard against accidental bulk changes.
Revision-log management: Removes revisions from selected sheets or deletes them more broadly from the project when appropriate.
Excel matrix export: Produces a project revision matrix for external reporting, transmittal preparation, audit records, or coordination.

Typical Workflow

Review the project’s revision standard, numbering sequence, issue terminology, and required date format.
Open the revision-management stage and create a new revision from a template or select existing revisions for editing.
Enter or update the revision description and date, using description history and the date builder where helpful.
Move to the sheet-assignment stage and select the revision to be issued or recorded.
Filter the sheet list by sheet set, discipline, issued status, revision-cloud presence, existing revision, or regex criteria.
Review the filtered list carefully, then apply the revision to the selected sheets.
If the wrong set was updated, use Undo Last Set immediately before performing another assignment.
Export the revision matrix to Excel and compare it with the intended issue register or transmittal.
Use the removal tools cautiously for corrections, then verify title blocks, revision schedules, clouds, sequences, and issued-sheet status in Revit.

Practical BIM Use Cases

Major issue packages: Apply a tender, permit, construction, or record revision to hundreds of sheets selected by discipline or sheet set.
Partial reissues: Identify only sheets that contain revision clouds and apply the corresponding revision without modifying unaffected sheets.
Revision cleanup: Correct an incorrect date or description across several revisions in one operation.
Standards enforcement: Use templates and date formatting to keep descriptions and dates consistent across projects.
Sheet-set auditing: Filter for sheets that are unissued, already contain a revision, or may have missed a required assignment.
Complex numbering schemes: Use regex to isolate discipline prefixes, packages, building zones, phases, or numeric ranges.
External reporting: Export an Excel revision matrix for coordination with document-control systems, issue registers, and transmittals.
Pre-issue QA/QC: Compare revision assignments with clouds and issued-sheet status before publishing.

Benefits and Productivity Value

The add-in concentrates revision administration into a purpose-built interface rather than requiring users to move repeatedly between Revit’s revision settings, sheet properties, and schedules. Bulk editing reduces repetitive data entry, while smart filters and regex search make large sheet inventories manageable. The Excel matrix creates a useful external checkpoint, and Undo Last Set lowers the risk of a mistaken mass assignment. For BIM and document-control teams, these features can shorten issue preparation, improve consistency, and make sheet-level revision coverage easier to audit.

Limitations and Implementation Considerations

Revit revision rules still apply: The add-in manages native revision data; sequence behavior, numbering, clouds, schedules, and per-sheet display remain governed by Revit and the project setup.
Sheet assignment is not the same as cloud verification: A revision can appear on a sheet through assignment even when no revision cloud is present. Teams should define when explicit sheet assignment is permitted.
Bulk operations amplify mistakes: Incorrect filters or regex patterns can affect many sheets. Always inspect the final selection before applying a change.
Undo has a narrow role: “Undo Last Set” should not be treated as a complete rollback system. Backups, synchronization discipline, and issue records remain necessary.
Deletion requires governance: Removing revisions can alter title-block history, schedules, and issued-document records. Previously issued information should be changed only under an approved document-control process.
Excel is a snapshot: An exported matrix is not automatically synchronized with later Revit changes.
Regex requires expertise: Advanced search is powerful but can produce unexpected matches when patterns are written or tested poorly.
Limited independent evidence: The Marketplace listing had no ratings or reviews when indexed, and public sources do not provide performance benchmarks or a comprehensive manual.

Recommended Deployment Approach

Document the office’s revision numbering, date, description, and sheet-assignment rules.
Pilot the add-in in a nonproduction copy containing multiple disciplines, issued and unissued sheets, revision clouds, and assigned revisions.
Build and test reusable filters, regex patterns, description templates, and date formats against known sheet sets.
Confirm who is authorized to create, edit, assign, remove, or delete revision records.
Require a pre-issue comparison between the Revit sheet set, revision matrix export, and document-control register.
Retain backups and approved issue records before using broad removal or wipe operations.

Overall Assessment

Revision Manager Pro appears best suited to projects with large sheet counts, frequent issue packages, formal document-control requirements, or repeated revision cleanup. Its strongest differentiators are the clear two-stage workflow, bulk editing and assignment, revision-aware sheet filters, regex search, configurable date formatting, Excel matrix export, and a targeted undo safeguard. The add-in can make revision administration faster and more consistent, but it should be implemented within a controlled issue process that verifies clouds, assignments, title-block output, and external registers before publication.

Internet Sources

Revision Manager Pro — Autodesk Design and Make Marketplace: https://marketplace.autodesk.com/apps/d32bd01e-666c-48a4-a0fc-beca41055304
Revision Manager — Penguin Tools: https://www.penguintools.co.uk/product/add-revision/
Penguin Tools Revit Plugins Catalog: https://www.penguintools.co.uk/shop/
Penguin Tools — Autodesk Publisher Profile: https://marketplace.autodesk.com/publisher-profile/0174e89d-07d3-44eb-b33f-2e9b8b80eb1e

revision_manager_smart_filters.png

revision_manager_main.png

revision_manager_create_modal.png

Revision Manager Pro is brought to you by Penguin Tools (PTP). It's free.

This add-in is compatible with Revit 2025-2027.

There's more information available on the Autodesk Design and Make Marketplace »

Questions? Contact the developer »

Opening Handing: Calculate, Review, and Record Door and Window Handing at Scale

2026-10-13T17:18:00.000-07:00

Executive Summary

Opening Handing is a Revit automation and QA/QC add-in from Penguin Tools for calculating, reviewing, and recording door and window handing. It analyzes opening geometry, swing direction, wall insertion orientation, and adjacent room context to determine standard architectural handing values such as Left Hand (LH), Right Hand (RH), Left Hand Reverse (LHR), and Right Hand Reverse (RHR). The calculated result can then be mapped to a chosen Revit parameter for schedules, door and window data, hardware coordination, and model checking. Its primary value is replacing repetitive visual interpretation and manual parameter entry with a consistent, reviewable process.

Core Capabilities

Automated handing calculation: Determines LH, RH, LHR, and RHR classifications from the modeled orientation and swing behavior of an opening.
Inward/outward interpretation: Can identify whether an opening swings inward or outward, adding useful directional context beyond a simple left/right result.
Geometry-based analysis: Evaluates swing geometry, insertion vectors, wall orientation, mirrored state, and room-bounding relationships rather than relying only on family names.
Flexible parameter mapping: Writes calculated codes to existing shared parameters, project parameters, or custom instance/type parameters instead of forcing a single proprietary field.
From Room/To Room context: Uses spatial relationships to interpret the transition direction between rooms or between interior and exterior space.
Batch audit dashboard: Presents calculated results in a table for review before model parameters are updated.
Flipped-opening detection: Identifies mirrored or flipped doors and windows that may create hardware, scheduling, or documentation discrepancies.
Multi-category support: The Marketplace description identifies Doors, Windows, Curtain Wall Doors, and custom nested opening families as supported targets.
Custom handing attributes: Penguin Tools describes an interface that lets users assign or configure handing attributes for door and window types.

Typical Workflow

Confirm the project’s handing convention and the viewpoint from which handing is defined.
Prepare the destination Revit parameter, including its name, data type, category binding, and instance/type behavior.
Select the door, window, curtain-wall door, or nested-opening scope to analyze.
Run the geometry and spatial analysis to calculate handing and inward/outward orientation.
Review the proposed values in the batch-audit table, paying particular attention to mirrored, flipped, exterior, double-acting, or nonstandard families.
Map the calculated values to the selected shared, project, or custom parameter.
Update the model and verify representative results in plan, schedules, elevations, and hardware documentation.
Resolve exceptions manually or correct family geometry and room settings where the modeled condition does not support a reliable result.

Practical BIM Use Cases

Door schedules: Populate a consistent handing field across hundreds of openings without manually reading each plan symbol.
Hardware coordination: Supply handing data that can be reviewed alongside hardware sets, lock functions, closers, and frame requirements.
Model audits: Find mirrored, flipped, or inconsistently modeled openings before issue or export.
Room-transition checking: Compare handing with From Room and To Room assignments to verify circulation and schedule intent.
Consultant-model cleanup: Normalize handing information in received models that use different parameters or incomplete values.
Family-library QA: Test whether custom and nested opening families expose usable geometry and respond predictably when flipped.
Documentation updates: Recalculate values after layout changes instead of relying on stale manually entered data.

Benefits and Productivity Value

The add-in’s principal benefit is consistency at scale. Handing is easy to misread when plans are rotated, openings are mirrored, room assignments are incomplete, or family graphics differ. Automated analysis can reduce manual schedule entry, expose exceptions earlier, and make the basis for each value more repeatable. Parameter mapping also allows the tool to fit an established BIM standard rather than requiring teams to rebuild schedules around a new field. The preview dashboard provides an important control point between calculation and model modification.

Limitations and Implementation Considerations

Convention must be defined: LH/RH terminology can vary by region, trade, hardware practice, and observation side. The team must agree on the convention before trusting or publishing results.
Family quality matters: Nonstandard swing graphics, nested geometry, unusual insertion origins, double doors, sliding openings, double-acting leaves, or custom families may require testing or manual review.
Room data can be ambiguous: Unenclosed rooms, phase differences, design options, room separation lines, and exterior conditions may weaken From Room/To Room interpretation.
Output still requires QA: Automated calculations should be sampled against plans, schedules, and hardware requirements, especially after major layout changes.
Parameter governance: Writing to type parameters may unintentionally apply one value to multiple instances with different conditions. Instance parameters are often safer for spatially dependent results.
Scope boundaries: The public description does not explain every special condition, failure state, or exception rule.
Limited independent evidence: Publicly indexed sources do not provide benchmark testing, a detailed manual, or extensive user reviews.

Pricing and Product Information

The Autodesk Marketplace listing indexed in September 2026 prices Opening Handing Pro at US$3.00 per month and offers a free trial. The listing describes the product as an automated spatial-analysis and parameter-management tool.

Recommended Deployment Approach

Document the office handing convention with diagrams and examples.
Create or confirm an instance-based shared parameter for Doors, Windows, and applicable custom categories.
Pilot the tool on a project containing standard, mirrored, curtain-wall, exterior, double, and custom-family conditions.
Compare calculated values with a manually verified sample and record exception types.
Define which conditions require manual review before parameters are committed.
Add the handing audit to model-health checks before hardware coordination and major documentation issues.

Overall Assessment

Opening Handing appears most valuable on projects with large opening counts, formal door schedules, or hardware-coordination requirements. Its strongest differentiators are geometry-based handing calculation, room-transition context, flexible parameter mapping, flipped-opening detection, and a review-first batch interface. The tool can improve speed and consistency, but its output is only as reliable as the agreed handing convention, family construction, parameter design, and spatial data. A controlled pilot and exception-based QA process are therefore essential.

Internet Sources

Opening Handing — Autodesk Design and Make Marketplace: https://marketplace.autodesk.com/apps/7360a749-7c3a-4dcb-adea-eb23bcdbbb4e
Opening Handing — Penguin Tools: https://www.penguintools.co.uk/product/opening-handing/
Penguin Tools Revit Plugins Catalog: https://www.penguintools.co.uk/shop/
Penguin Tools — Autodesk Publisher Profile: https://marketplace.autodesk.com/publisher-profile/0174e89d-07d3-44eb-b33f-2e9b8b80eb1e

Handing Type 2

Handing Type 5

Handing Type 1

Handing Type 4

Opening Handing is brought to you by Penguin Tools (PTP). It's priced at $3/month or $30/year. A 30-day free trial is available.

This add-in is compatible with Revit 2025-2027.

There's more information available on the Autodesk Design and Make Marketplace »

Questions? Contact the developer »

Revit Add-ons Advertising Sale: Save 35% and Get 3 Months Free!

2026-10-13T12:26:18.416-07:00

Free Model Upgrader Pro: Process Interdependent Model Sets Systematically

2026-10-12T17:32:00.000-07:00

Executive Summary

Model Upgrader Pro is a free, high-performance Revit add-in from Penguin Tools that automates the migration of project models and family libraries to a newer Revit release. It is aimed primarily at BIM managers, project leads, and architecture/engineering teams responsible for annual software-version transitions. The tool scans folders recursively, identifies file versions and linked-model relationships, opens and upgrades files in memory, and can apply worksharing and cleanup options without filling the active Revit session with view tabs. Its central value is the ability to process interdependent model sets systematically rather than requiring users to open, dismiss prompts, save, and close every file manually.

Core Capabilities

Batch upgrading: Processes multiple Revit project files and family-library files in one run, reducing repetitive open-and-save work.
Recursive folder scanning: Searches selected directories and their subfolders, reports file counts, and detects source Revit versions before processing.
Linked-model inspection: Reads Revit Transmission Data to identify nested links inside parent models and add linked files to the upgrade queue.
Dependency-aware processing: Helps preserve coordinated model sets by discovering linked content rather than treating each parent model in isolation.
Duplicate sublink protection: Deduplicates repeated linked-model references so the same file is not unnecessarily processed more than once.
In-memory operation: Opens and upgrades files without drawing their view canvases or populating the normal document-tab interface.
Audit on open: Can invoke Revit’s internal audit process while opening files to identify and attempt correction of database inconsistencies.
Worksharing handling: Provides options to detach worksets and re-establish upgraded workshared files as central models.
Backup cleanup: Can remove redundant _backup directories created during processing to reduce storage clutter.

Typical Migration Workflow

Make verified backups and freeze production changes for the migration window.
Launch the target Revit release and open Model Upgrader Pro.
Select the source directory containing project models, linked models, or family libraries.
Allow the tool to scan subfolders, count files, detect source versions, and inspect Transmission Data for nested links.
Review the queue and confirm that every intended file—and no unintended archive or deliverable—is included.
Choose processing options such as Audit on Open, detach behavior, central-model re-establishment, and backup-folder cleanup.
Run the upgrade and monitor completion or error messages for each file.
Validate upgraded models in the target Revit version, including links, worksets, warnings, schemas, coordinates, families, sheets, and critical outputs.
Retain the original files until the upgraded set passes QA/QC and the team formally approves the transition.

Practical BIM Use Cases

Annual project migration: Upgrade an active project directory and its linked discipline models for firmwide adoption of a new Revit release.
Content-library maintenance: Move large collections of reusable family files forward to the current production version.
Archived-project recovery: Prepare selected legacy models for reopening, renovation work, or data extraction in a supported Revit environment.
Consultant handoff preparation: Upgrade coordinated local files before packaging them for a team that is already using the newer release.
Workshared-model transition: Detach legacy central files and recreate upgraded central models as part of a controlled migration.
Model-health review: Combine upgrading with Audit on Open to expose files that require closer inspection before production use.
Storage housekeeping: Remove generated backup directories after successful validation when organizational retention policies permit it.

Benefits and Productivity Value

Model Upgrader Pro addresses three major costs of Revit migration: manual handling, dependency discovery, and interruption of the user interface. Recursive scanning reduces the chance that files buried in subfolders are missed; Transmission Data inspection helps identify linked models that belong in the same migration set; and background-style, in-memory processing avoids the clutter and regeneration overhead associated with visibly opening each document. For BIM management teams, these capabilities can make migrations more repeatable, reduce operator touch time, and produce a clearer processing sequence for complex directories.

Risks, Limitations, and Safeguards

Irreversible file conversion: Revit files cannot be saved back to an earlier release. Always preserve untouched source copies.
Not a substitute for validation: A successful batch process does not prove that links, geometry, warnings, schedules, add-in data, or deliverables behave identically in the new version.
Audit side effects: Audit may remove or repair problematic data. Use it deliberately and review the resulting models and logs.
Worksharing risk: Detaching and recreating central models can affect central paths and local-file workflows. Coordinate downtime and require users to create new locals afterward.
External dependencies: Linked CAD, point clouds, images, keynotes, shared parameters, add-ins, custom schemas, and cloud-hosted content may require separate checks.
Backup deletion: Automatic removal of backup directories saves space but should be enabled only after confirming retention and recovery requirements.
Local-directory focus: The public descriptions emphasize directory and file processing; they do not document a direct workflow for upgrading Autodesk Construction Cloud or BIM 360 cloud models.
Installer governance: Autodesk’s listing states that the app uses a custom installer, which may require testing, packaging, and approval in managed environments.
Limited independent evidence: The indexed Marketplace listing showed no ratings or reviews, and the public sources did not provide benchmark data or a detailed troubleshooting guide.

Recommended Deployment Approach

Pilot the add-in on a representative copy of one project containing worksharing, nested links, custom families, and external references.
Record source versions, file counts, migration options, errors, durations, and output locations.
Compare pre- and post-upgrade model health, warnings, coordinates, links, sheets, schedules, and published deliverables.
Define whether auditing, detaching, re-centralizing, and backup cleanup are standard or exception-based actions.
Document rollback procedures and approval criteria before scaling to production directories.
Run the final migration during controlled downtime and communicate new-local-file requirements to the project team.

Overall Assessment

Model Upgrader Pro appears particularly valuable for BIM teams managing large, linked, locally stored Revit datasets. Its strongest differentiators are recursive scanning, Transmission Data link discovery, deduplication of repeated sublinks, in-memory processing, and options for audit and workshared central-model re-establishment. Those features address complexities that basic folder-based upgraders may overlook. However, migration remains a high-impact operation: adoption should be paired with immutable backups, a documented test plan, controlled worksharing procedures, targeted model validation, and confirmation of current Revit compatibility.

Internet Sources

Model Upgrader Pro — Autodesk Design and Make Marketplace: https://marketplace.autodesk.com/apps/eb237ef8-a01d-4a08-8c58-0243cacabe64
Model Upgrader Pro — Penguin Tools: https://www.penguintools.co.uk/product/model-upgrader-pro/
Penguin Tools Revit Plugins Catalog: https://www.penguintools.co.uk/shop/
Officially supported product versions of Revit — Autodesk Support: https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/Which-are-the-officially-supported-product-versions-of-Revit.html

Model Upgrader Pro is brought to you by Penguin Tools (PTP). It's free.

This add-in is compatible with Revit 2025-2027.

There's more information available on the Autodesk Design and Make Marketplace »

Questions? Contact the developer »

Free Color Tabs Pro: Includes User-Defined Rules-Based Processing

2026-10-11T13:26:27.809-07:00

Executive Summary

Color Tabs Pro is a free Revit productivity add-in that visually organizes open document and view tabs. It automatically applies color and styling according to the source document, view type, file category, or user-defined rules. Its purpose is to reduce navigation errors in busy Revit sessions, particularly when users have many views open across multiple projects and family files. Instead of relying only on truncated tab names, users gain an immediate visual cue indicating which document or view category each tab belongs to.

Core Capabilities

Unique color per document: Automatically assigns a distinct color from a curated palette to each open project, allowing all views from the same model to be recognized instantly.
Color by view type: Uses different colors for functional view categories such as Sheets, Floor Plans, 3D Views, and Schedules.
Single-color mode: Applies a consistent color to a selected document category—for example, displaying all Revit family documents in green.
Separate project and family behavior: Allows .rvt and .rfa documents to use different coloring modes and styles.
Multiple visual styles: Offers Solid Fill, Striped, Top Bar, and Border treatments, enabling users to balance visibility against interface intensity.
Custom rules engine: Supports “If/Then” overrides based on Project Number, File Name, or Project Name. A high-priority project can therefore receive a specific color and style regardless of the general settings.
Rule precedence: Custom rules override the broader project or family configuration, making exceptions predictable.
Native-theme integration: Overrides Revit’s normal tab appearance while preserving the active-tab selection theme, helping the current tab remain identifiable.
Background operation: Runs silently after configuration; users return to the settings dashboard from the Penguin Tools ribbon when changes are needed.

Configuration and Typical Workflow

Open the settings dashboard from the Penguin Tools ribbon.
Configure Project Documents and Family Documents independently.
Select a coloring mode: Unique Per Doc, By View Type, or Single Color.
Choose a presentation style: Solid, Striped, Top Bar, or Border.
Create exception rules for important projects using Project Number, File Name, or Project Name criteria.
Return to normal Revit work. The add-in continues operating in the background and updates the visual treatment of tabs according to the configured logic.
Review the interface under typical workloads and adjust colors or styles if the treatment is too subtle, visually dominant, or difficult to distinguish.

Practical BIM Use Cases

Multi-model coordination: Assign one color to each open project so users can distinguish host, consultant, option, and archive models before selecting a tab.
Family editing: Give all family-document tabs a consistent treatment, such as a green Top Bar, separating content-authoring work from project-model work.
View-type recognition: Visually separate sheets, plans, 3D views, and schedules, making large tab sets easier to scan.
High-priority project alerts: Add a custom rule that gives a critical project number a prominent red Solid style.
Training and support: Use predictable visual categories to help less-experienced users understand which document and view type they are operating in.
Screen sharing and demonstrations: Improve orientation during reviews, troubleshooting, and training sessions where many views are open.
Error reduction: Reduce the likelihood of editing a family, test model, or similarly named view in the wrong document.

Benefits and Productivity Value

The add-in addresses a common usability problem rather than changing model content. Color becomes a secondary navigation system layered over Revit’s document tabs. This can shorten the time required to locate the correct view, reduce context-switching effort, and make mistakes less likely when tab names are similar or partly hidden. The combination of automatic modes and exception rules is especially useful: general settings require little maintenance, while selected projects can still receive distinctive treatment. Because the tool operates in the interface rather than modifying model standards, deployment should have a low impact on project data and deliverables.

Limitations and Implementation Considerations

Personal interface aid: Tab colors improve local navigation but do not replace model naming standards, browser organization, QA/QC procedures, or document controls.
Color dependence: Teams should select palettes and styles that remain distinguishable for users with color-vision differences. Border or pattern-based treatments may be preferable to color alone.
Visual overload: Solid fills across many tabs may become distracting. Top Bar, Border, or Striped styles can provide a lighter visual signal.
Rule maintenance: Rules based on names or project numbers may require updates when project metadata or file naming changes.
Shared conventions: If consistent visual behavior is important across a team, organizations should document recommended settings because individual configurations may otherwise differ.
Limited independent evidence: The Marketplace listing had no ratings or reviews when indexed, and public sources did not provide benchmark data quantifying time savings or error reduction.

Overall Assessment

Color Tabs Pro is best suited to Revit users who routinely work with numerous open views, multiple projects, or a mix of project and family documents. Its strongest features are automatic per-document coloring, view-type categorization, separate project/family settings, flexible display styles, and metadata-driven exception rules. The add-in is narrowly focused, but that focus is useful: it improves session awareness without changing model geometry or production data. Organizations considering deployment should test color accessibility, define a restrained visual convention, and confirm installer approval and Revit-version compatibility through the official listing.

Internet Sources

Color Tabs Pro — Autodesk Design and Make Marketplace: https://marketplace.autodesk.com/apps/b3601993-1800-4220-b1e8-ad9c5cee825b
Colour Tabs — Penguin Tools: https://www.penguintools.co.uk/product/colour-tabs/
Penguin Tools Revit Plugins Catalog: https://www.penguintools.co.uk/shop/

ColourTabs_Family_Striped

ColourTabs_Dash_Rules

ColourTabs_Dash_ViewType

ColourTabs_Family_TopBar

ColourTabs_Dash_Default

ColourTabs_Project_Border

Color Tabs Pro is brought to you by Penguin Tools (PTP). It's free.

This add-in is compatible with Revit 2025-2027.

There's more information available on the Autodesk Design and Make Marketplace »

Questions? Contact the developer »

Free Bulk Rename Pro: Clean Up Model Naming Conventions at Scale

2026-10-11T13:01:45.946-07:00

Executive Summary

Bulk Rename Pro is a Revit productivity add-in from Penguin Tools designed to standardize and clean up model naming conventions at scale. Rather than editing names one item at a time, users can assemble rename rules, preview the proposed results, and apply consistent changes across multiple categories. The Autodesk Marketplace listing positions it for BIM managers, architects, and engineers who need faster naming cleanup, repeatable standards, and fewer manual errors.

Core Capabilities

Live before-and-after preview: Displays existing and proposed names in a sortable, filterable table so users can inspect results before committing changes.
Case conversion: Converts names to uppercase, lowercase, Title Case, Sentence case, camelCase, or PascalCase.
Find and replace: Replaces literal text and supports regular expressions for advanced pattern matching, extraction, and restructuring.
Prefix and suffix rules: Adds project, discipline, package, status, or revision identifiers to many names in one operation.
Trimming and insertion: Removes leading or trailing characters and whitespace, or inserts text at a specified character position.
Symbol and spacing cleanup: Resolves double spaces, substitutes spaces with underscores or hyphens, and removes unwanted non-alphanumeric characters.
Multi-category processing: The Marketplace listing identifies Views, Sheets, View Templates, Schedules, Levels, Grids, and Worksets as supported rename targets.
Usage analytics: Tracks model updates and estimated time savings over time.

Typical Workflow

Select the Revit category or categories to be renamed.
Filter or sort the item list to isolate the intended scope.
Build one or more naming operations, such as case conversion, find-and-replace, prefixing, suffixing, trimming, character insertion, or regex-based transformation.
Review the live old-name/new-name preview and check for unintended results or potential naming conflicts.
Apply the changes to the model, then validate affected views, sheets, levels, grids, templates, schedules, and worksets against the project naming standard.

Practical BIM Use Cases

Project startup: Apply office-standard discipline, level, zone, package, or phase prefixes to views and sheets.
Model audits: Correct inconsistent capitalization, duplicate spaces, punctuation, and legacy abbreviations discovered during QA/QC.
Template migration: Convert names from a consultant or acquired model to an internal naming convention.
Sheet-set reorganization: Update sheet names and related identifiers for issue packages, milestones, or revised numbering structures.
Level and grid normalization: Replace inconsistent designations with predictable formats that improve navigation and downstream coordination.
Deliverable preparation: Remove temporary labels and enforce naming rules before publishing, model exchange, or archival.
Advanced pattern cleanup: Use regular expressions to identify digits, swap level designations, extract codes, or restructure repeated naming patterns.

Strengths and Value

The add-in’s main value is the combination of broad batch processing, flexible rule construction, and preview-driven control. It can reduce repetitive editing, improve adherence to BIM standards, and make cleanup operations reproducible. Regex support gives technically advanced users significantly more control than a basic prefix/suffix tool, while the preview table reduces risk by exposing the proposed outcome before model changes are written. For BIM management teams, these capabilities can support faster audits, more consistent deliverables, and less time spent correcting naming drift.

Limitations and Implementation Considerations

Regex knowledge: Advanced transformations require careful pattern design; an incorrect expression can affect many items at once.
Revit naming constraints: Some categories require unique names or enforce limits on characters and numbering, so preview and validation remain essential.
Dependencies: Renaming can affect human workflows, exports, scripts, schedules, standards checks, and external references that rely on predictable names, even when Revit maintains internal element relationships.
Governance: Teams should test rules on a copy or controlled model, limit the rename scope, document the convention, and coordinate major naming changes before applying them to a shared project.
Evidence gap: Public sources reviewed did not provide a full user manual, release history, detailed licensing terms, or independently verified performance benchmarks.

Compatibility and Product Positioning

The current Autodesk Marketplace entry identifies Bulk Rename Pro as free, but the captured listing does not expose version, release-date, or supported-Revit-version details. Penguin Tools also maintains a separate free product page titled “Bulk Rename” that describes bulk renaming for Views, Sheets, and sheet numbers and lists Revit 2023, 2024, and 2025 support. Because that page uses a different product name and describes a narrower feature set, it should not be treated as definitive compatibility documentation for Bulk Rename Pro without confirmation from the publisher.

Overall Assessment

Bulk Rename Pro appears best suited to teams that routinely clean up large models, enforce formal naming standards, or inherit inconsistent consultant content. Its live preview and rule-based transformations address the two central risks of bulk renaming: scale and unintended change. The strongest differentiators are multi-category coverage, regular-expression support, comprehensive string cleanup, and built-in usage analytics. Adoption should be paired with a documented naming standard, controlled testing, and a post-rename QA check.

Internet sources

Autodesk Design and Make Marketplace — “Bulk Rename Pro”: marketplace overview, price, major features, custom-installer note, and support information.
Penguin Tools — “Bulk Rename”

Bulk Rename Pro is brought to you by Penguin Tools (PTP). It's free.

This add-in is compatible with Revit 2025-2027.

There's more information available on the Autodesk Design and Make Marketplace »

Questions? Contact the developer »

Free Auto Sync Pro: Automatic Sync, Relinquish, Link Reloading, Idle Exit, Compact & Backup Cleanup

2026-10-09T17:26:00.000-07:00

Executive summary

Auto Sync Pro is a free Penguin Tools add-in designed to automate routine Revit file-management tasks in the background. Its central function is timed or idle-triggered saving and Synchronize with Central, but the documented toolset also includes automatic relinquishment, Revit-link reloading, scheduled or inactivity-based exit, compact-on-sync, backup cleanup, a live status dashboard, and a persistent activity log. The product is aimed at workshared teams that want to reduce forgotten synchronizations, stale links, retained ownership, oversized files, and Revit sessions left running after hours.

Core automation tasks

Synchronize or save: Automatically performs Synchronize with Central for workshared projects or saves non-workshared/local files at configured intervals. The vendor describes smart logic that skips models with no changes.
Relinquish ownership: Releases borrowed elements and worksets so other team members are less likely to encounter editing bottlenecks.
Reload linked documents: Refreshes Revit links automatically to bring current discipline data into the host model.
Auto-exit: Closes Revit safely after a specified idle period or at a scheduled time, helping release workstation and license resources.
Compact on sync: Uses Revit’s compact option during synchronization to reduce file bloat and support model maintenance.
Backup cleanup: Removes older numbered backup files to manage storage consumed by local or server-side backup folders.
Activity logging: Keeps a persistent record of background events and task completion for review and troubleshooting.

Scheduling and operating modes

Continuous mode: Runs enabled tasks at clock-based intervals. Public product descriptions identify common synchronization intervals of 15, 30, and 60 minutes.
Idle mode: Waits until Revit has been inactive for a user-defined duration, reducing the chance that automation interrupts active modeling.
Time boundaries: Restricts background operations to configured start and end times, such as normal office hours.
Scheduled exit: Supports a set closing time in addition to inactivity-based exit.
Global activation: A master toggle enables or suspends the entire automation system; disabled tasks do not run.

Interface and monitoring

The Status tab acts as a dashboard for the principal automated operations. It displays task state and countdown information so users can see when synchronization, relinquishment, link reload, or exit is expected to occur. The Activity Log provides a persistent history of background actions and completions. Together, these controls improve visibility into automation that would otherwise be silent, although teams should still establish how failures and warnings will be reviewed.

Typical workflow

Open and enable: Launch the Auto Sync Pro interface and turn on the global activation control.
Choose tasks: Enable synchronization/save, relinquishment, link reload, auto-exit, and any maintenance options appropriate to the project.
Select a trigger: Configure fixed intervals or idle-based execution and, if needed, restrict operations to defined working hours.
Set maintenance behavior: Decide whether synchronization should compact the model and how aggressively old backup files should be removed.
Monitor: Use the dashboard to check countdowns and status, then review the Activity Log for successful actions, skipped operations, or problems.
Govern: Adjust settings when project size, network conditions, collaboration patterns, or office policy change.

Benefits for Revit teams

Reduced data-loss exposure: Regular saves and synchronizations limit the amount of unsaved work between recovery points.
More current collaboration data: Automated synchronization and link reloading help users work with fresher model information.
Fewer ownership conflicts: Automatic relinquishment can return borrowed elements and worksets that users might otherwise retain.
Lower administrative effort: Routine housekeeping runs without relying on each user to remember every step.
Improved model hygiene: Compact-on-sync and backup cleanup target file growth and storage overhead.
Resource management: Auto-exit can close unattended sessions and free computer and license capacity after hours.
Better accountability: Status feedback and activity history provide evidence that an operation ran—or reveal that it did not.

Risks and operational considerations

Automation does not eliminate sync conflicts: A timed trigger can coincide with central-model activity, network instability, warnings, editable-element conflicts, or dialogs requiring attention. Teams should verify how the add-in reports and recovers from these conditions.
Interval selection matters: Very frequent synchronization may disrupt concentration or increase network and central-model load; very long intervals reduce the protective value.
Idle does not always mean safe: Revit may be processing, waiting on another application, displaying a modal dialog, or running another add-in even when the user is inactive.
Relinquishment requires policy alignment: Automatically releasing ownership can be beneficial, but teams should test how it interacts with long-running tasks, borrowed worksets, and intentional ownership.
Link reloads can be expensive: Large or remote linked models may make automatic reloading slow and can change visible coordination context without active user review.
Compaction adds processing time: Compact-on-sync can reduce file size but may lengthen synchronization, especially on large projects.
Backup deletion is destructive: Cleanup rules must match retention requirements and should be tested so useful recovery points are not removed prematurely.
Auto-exit needs safeguards: Confirm behavior for unsaved documents, open dialogs, cloud models, multiple documents, background processes, and failed synchronization before using scheduled shutdown broadly.
Logs require ownership: An activity history is valuable only if someone reviews repeated failures and understands where the log is stored and how long it is retained.

Deployment and governance recommendations

Pilot the add-in on a copy of a representative project with realistic central-model, cloud, network, and linked-model conditions.
Define office-standard intervals and idle thresholds by model size and collaboration pattern rather than leaving every user to choose independently.
Test synchronization with warnings, borrowed elements, offline links, unavailable central files, open dialogs, and interrupted network access.
Create a documented backup-retention policy before enabling cleanup.
Decide whether compact-on-sync should run every time, on a longer cadence, or only under controlled maintenance conditions.
Establish user notifications, log-review responsibility, and an escalation path for repeated failures.
Confirm settings after Revit, Windows, model-hosting, VPN, or add-in updates.
Train users that background automation supplements—not replaces—manual synchronization before major changes, breaks, handoffs, and closing.

Availability and support

The Autodesk Design and Make Marketplace lists Auto Sync Pro as free and notes that it uses a custom installer rather than the standard marketplace installer. Penguin Tools also lists AutoSync in its Revit plug-in catalog. Public search results reviewed for this summary did not provide a definitive supported-Revit-version matrix or detailed infrastructure requirements. Administrators should confirm version compatibility, installer privileges, update behavior, log location, cloud-model support, and data-retention behavior with the current product page or vendor before deployment.

Overall assessment

Auto Sync Pro addresses a genuine worksharing-management gap: critical housekeeping depends too often on individual memory and discipline. Its combination of scheduled or idle-triggered synchronization, relinquishment, link refresh, maintenance, auto-exit, and logging can improve consistency across a team. The highest value will come from governed deployment with tested defaults and visible failure handling. Because synchronization, compaction, cleanup, and shutdown affect shared data and user sessions, organizations should treat the add-in as managed project infrastructure rather than a set-and-forget personal convenience.

Internet sources

Autodesk Design and Make Marketplace — “Auto Sync Pro”: marketplace overview, price, major features, custom-installer note, and support information.
Penguin Tools — “AutoSync”: developer description of automated tasks, scheduling modes, maintenance options, dashboard, and activity log.

AutoSync_Help

AutoSync_Status

AutoSync_ActivityLog

AutoSync_Configuration

Auto Sync Pro is brought to you by Penguin Tools (PTP). It's free.

This add-in is compatible with Revit 2025-2027.

There's more information available on the Autodesk Design and Make Marketplace »

Questions? Contact the developer »

Free Section Box Pro: Expands the Native Section-Box Workflow

2026-10-08T17:35:00.000-07:00

Executive summary

Section Box Pro is a free Revit add-in from Penguin Tools that expands the native section-box workflow for rapid 3D isolation, detailing, coordination, and documentation. Instead of manually creating a 3D view, enabling its section box, dragging six faces, orienting the camera, and renaming the result, users can select model elements and generate a tightly cropped, predictably named 3D view. Its principal differentiators are independent directional buffers, alignment to selected geometry, linked-model support, preset camera orientations, batch creation of one view per element, and automated view naming.

Core capabilities

Instant cropped 3D views: Creates and activates a new 3D view whose section box is calculated from the selected element or elements.
Six-direction buffer control: Allows separate offsets for top, bottom, left, right, front, and back, supporting asymmetric working space rather than a single uniform margin.
Quick presets: Vendor documentation identifies Tight (150 mm), Context (500 mm), and Clash (0 mm) presets for common inspection and detailing conditions.
Automatic alignment: Can align the section box to the primary rotation of selected walls, columns, or structural framing rather than leaving it aligned only to project north.
Linked-model selection: Supports elements in linked Revit models and transforms their coordinates into the host model for correct box placement.
Camera orientation: Offers standard isometric, top, bottom, front, back, left, and right orthographic viewpoints.
Scope-box synchronization: Can match the active section-box extents to a project scope box.
Batch view creation: Generates separate cropped 3D views for multiple selected objects, such as doors, columns, or equipment.
Smart naming: Builds descriptive names from category, type, and mark while handling duplicate names to reduce generic “3D View” and “Copy 1” clutter.
Element isolation: Can isolate the selected object in the generated view.
Section-box visibility: Provides a quick show/hide control for the section-box cage, useful for screenshots and presentation exports.

Typical workflow

Select: In a plan, section, elevation, or 3D view, select one element, several elements, or an item in a linked model.
Configure: Open Section Box Pro and choose a buffer preset or enter directional offsets. Set the desired orientation, alignment, isolation, and naming options.
Choose creation mode: Use a single encompassing section box for a group, or enable batch mode to produce an individual view for each selected object.
Apply: The add-in calculates the bounding geometry, creates and crops the 3D view, assigns its name, sets its orientation, and activates it.
Refine and document: Hide the box cage if needed, annotate or inspect the view, and place it on a sheet or use it for coordination.

Primary use cases

Clash investigation: A zero buffer can frame the immediate interference zone, while directional offsets can expose access or clearance conditions.
Detail development: A context buffer creates a localized 3D working view around assemblies, junctions, connections, and penetrations.
Linked-model coordination: Teams can isolate structural, architectural, or MEP components in links without opening the source model merely to establish a useful host-model view.
QA/QC: Focused views support review of placement, orientation, clearances, joins, interfaces, and constructability.
Element documentation: Batch mode can prepare consistently cropped views for repeated assets, unique conditions, schedules, diagrams, or sheets.
Communication: Clean, box-free 3D views can be captured for issue reports, markups, meetings, and presentations.

Productivity and BIM value

Fewer manual steps: Automates view creation, section-box sizing, orientation, naming, activation, and optional isolation.
More repeatable output: Presets and naming rules make views more consistent across users and models.
Better spatial control: Independent offsets avoid the excessive context or repeated face dragging associated with uniform manual adjustments.
Faster linked-model review: Link-aware coordinate transformation reduces setup friction in federated coordination models.
Scalable documentation: Batch mode converts a repetitive one-view-at-a-time process into a multi-element operation.
Cleaner project browser: Descriptive, duplicate-aware names improve view identification and reduce generic naming clutter.

Requirements and availability

Penguin Tools and the Autodesk marketplace list Section Box Pro as free. It is distributed as a Revit plug-in through the Autodesk Design and Make Marketplace and is also presented in the developer’s catalog of free tools.

Considerations and limitations

Potential view proliferation: Batch generation can quickly add dozens of views. Teams should establish naming, browser organization, template, and cleanup rules before broad use.
Bounding-box behavior: A calculated box may still need adjustment for irregular, rotated, nested, hosted, or unusually extended geometry.
Linked-content dependencies: Accuracy depends on link placement, transforms, loaded status, and the add-in’s handling of nested or atypical link conditions.
Not a clash engine: The tool helps inspect a known location or selected element; it does not replace model-comparison, interference-detection, or issue-management systems.
Visibility standards still apply: Isolation and box visibility can simplify a view, but users must still manage categories, worksets, phases, design options, detail level, and view templates.
Batch QA remains necessary: Automatically named and cropped views should be reviewed for extents, orientation, naming, duplicate conditions, and suitability before sheet placement.

Implementation guidance

Pilot the tool on a copy of a representative multidisciplinary project, including linked and rotated elements.
Define approved view-name patterns and browser organization rules for automatically generated views.
Agree when to use tight, context, clash, or custom directional buffers.
Test batch mode on a small selection before generating large view sets.
Document cleanup ownership so temporary coordination views do not remain indefinitely.
Include checks for box extents, orientation, hidden/isolate states, link visibility, and view-template compatibility in the team’s QA procedure.

Overall assessment

Section Box Pro addresses a narrow but frequent Revit task with a strong combination of speed and control. Its highest-value features are the six-direction offsets, rotation-aware alignment, linked-model support, repeatable camera orientations, and one-view-per-element batch processing. The add-in is particularly useful for production teams that routinely create localized 3D views for detailing and coordination. The main management concern is not the section-box operation itself, but controlling the number, naming, organization, and lifecycle of the views it can generate so quickly.

Internet sources

Autodesk Design and Make Marketplace — “Section Box Pro”: primary listing for product positioning, features, price, and marketplace availability.
Penguin Tools — “Section Box Pro”: developer description, workflow instructions, presets, linked-model support, batch mode, and use cases.
RVT Plugins — “Revit Plugin Review: Section Box Pro”: independent overview of the major features and intended productivity benefits.

Section Box Pro is brought to you by Penguin Tools (PTP). It's free.

This add-in is compatible with Revit 2025-2027.

There's more information available on the Autodesk Design and Make Marketplace »

Questions? Contact the developer »

OkPy Review: Create Fully Functional Revit Add-ins with Zero Coding, with Examples!

2026-10-07T18:47:00.000-07:00

Recently we posted about OkPy and its parent, the Orkestra add-in. I've been using OkPy for several days and have created a few add-ins with it, with zero coding. (I haven't even so much as looked at code.) Here I'll detail my add-ins and the prompts I used to create them. It's a good cross section, from a simple scripting task to a model scanner to interactive element selection, with some snazzy dialog box design and Excel interoperability thrown in for good measure.

A little about my programming background: I have about 30 years of development experience, though it has been almost exclusively with Bentley products, especially MicroStation (I know, boo, hiss!), and primarily with Visual Basic. A few months ago, I tried to create a Revit add-in the traditional way, with C#, but you need to configure Visual Studio to work with Revit and I couldn't find a modern reference for how to do that, so I didn't even get out of the starting block.

First, let's cover an add-in I named Hammer Sync. I wanted a tool that would sync, reload selected links, and sync again. Something I could kickoff and walk away from. This process is handy before exporting CAD files to make sure everything's up to date.

I used the following prompt to create the add-in:

Create a new project named Hammer Sync. In a dialog box, list "Synchronize Now", then all the Revit links in the active file in alphabetical order, and "Synchronize Now" again. To the left of each list item, place an icon appropriate for the task, synchronize for each Synchronize Now and reload for each link. To the far left of each list item, place a checkbox. At the bottom left of the dialog, place "Check None" and "Check All" buttons. If all checkboxes are ticked, lock the Check All button. If some checkboxes are unticked, unlock the Check All button. If no checkboxes are ticked, lock the Check None button. If some checkboxes are ticked, unlock the Check None button. If the user clicks Check None, untick all the checkboxes. If the user clicks Check All, tick all the checkboxes. To the right of the list, place an image of a steaming cup of coffee. At the bottom right of the dialog, place "Apply" and "Cancel" buttons. When the user clicks Apply, if the first Synchronize Now list item is checked, synchronize the model. Then, reload each link that is checked in list order. Finally, if the second Synchronize Now is checked, synchronize the model again. To the right of the list, when a list item is being processed, show a clock icon. When a list item is done processing, display a checkmark.

Now, to be fair, it took me four prompts to get this all included, which was fortuitous because that's the number of free prompts OkPy gives you per day. But my first prompt did the lion's share of the work. The others were just interface tweaks.

Let's see how OkPy works...

You open the OkPy agent through the Orkestra tab:

This opens the OkPy Agent dialog box, where you input prompts:

Once you enter a prompt, the OkPy agent starts thinking. It asked me one question after the above prompt, what kind of dialog box I wanted. I answered Classic:

The OkPy agent took about 5 minutes to complete this task. Total development time was about 20 minutes, and this is what I ended up with:

There are a lot of nice little touches that I didn't ask for, like whether or not a link is loaded, the messages at the top and bottom of the list, the message below the cup of coffee, and the steam coming off the cup of coffee is even animated! This means that it was created programmatically, rather than just being a static image. Also, when running the add-in, there's a nice little warning dialog that I didn't ask for:

Lastly, when running the add-in, there's a progress bar at the bottom of the dialog box, which, again, I didn't ask for, and which is more than what Revit gives you:

Most importantly, the add-in works as designed!

Because AI is ever evolving, you may get slightly different results than I did with the same prompt(s). For instance, the cup of coffee may look different. And the added touches may be different, or you may have to add them yourself.

Although the dialog box has some nice bells and whistles—for instance, populating the list with the links in the active file would be somewhat challenging programmatically—ultimately, this is an example of a script because it just sequences a list of Revit commands.

For my next add-in, I wanted to create a 3D view showing the elements with warnings colored red, and all other elements with 90% transparency. Here's my prompt:

Create a new project named "Color Warnings". Display a dialog box with the message, "This add-in creates or updates a view named: 3D - Warnings". Add "OK" and "Cancel" buttons. When the user clicks OK, create or update a view named "3D - Warnings". In this view, make all elements with warnings color red. Make all elements without warnings white and 90% transparent. Set the 3D view to an isometric orientation, turn off all links, turn off grids, turn off levels, turn off scope boxes, turn off shadows, set the Detail Level to fine, and set the Visual Style to Shaded. While processing, display a dialog box with a progress bar.

Again, the add-in worked as designed out of the chute, and it's fast! Here's an original view, and the view created with the add-in:

And, again, the OkPy agent threw in some nice touches: the dialog box lists the number of warnings in the file and the number of types of warnings, and the number of affected elements (I've since tweaked the add-in so I'll show this dialog a little later on in this article).

And the progress dialog is nice:

At this point, I thought, "Wouldn't it be good if the elements were color-coded based on warning severity?" Revit doesn't rank warnings like this, but it occurred to me that I could do this easily in a spreadsheet if my add-in spit one out. So I used a second prompt to add this functionality:

Before processing, if the file exists in my Documents folder, open the spreadsheet "Color Warnings.xlsx". If it doesn't exist, create it, with two columns, "Warning Message" and "Warning Color". For each element with warnings, match the warning message with the color column in the spreadsheet, and assign the element that color. If the warning doesn't exist in the spreadsheet, write it to the spreadsheet and assign it and the element color "Blue". When done, close the spreadsheet.

Simple, right? Not so simple programmatically I'm sure, but it worked! Here's the resulting dialog box:

That's pretty clear!

In the resulting spreadsheet, I then simply assigned the color I wanted each warning to have:

Then I reran the add-in, and here are the results:

Over time, with each model you run the add-in on, you'd effectively be building your own database of Revit warnings with ratings. I use it a little bit differently; I recreate the spreadsheet for each file and send it with a screengrab of the "3D - Warnings" view to the project's design team and ask them to correct the red warnings. For yellow, I indicate that they can use their judgement, and I tell them that they can probably safely ignore the green warnings.

Let's do a couple more things. We want it to be easy for the user to open the spreadsheet and, while we're at it, to open the native Revit Warnings dialog. For that, we'll need another prompt:

In the last dialog box, add a checkbox labeled, "Open Color Warnings.xlsx". If any warnings are color blue, tick this checkbox on, or else, untick it. If the checkbox is ticked when the user clicks OK, open the spreadsheet. Add a second checkbox labeled, "Open Warnings dialog box". If this is ticked on when the user clicks OK, open the Warnings dialog. Remember the user's last selection and apply it on the next run.

We end up with something like this:

This is an example of a scanner; it sequences every element in the file and does something to it.

Lastly, I wanted to be able to pick elements and see what their warnings are. With our colored view, that'd be useful, right? Here's my prompt:

Create a new project named "Pick Warning". Prompt the user to select an element to see its warning(s). Allow the user to select an element and, in a dialog box with an "OK" button, display the element's warning(s). When the user clicks the OK button, loop. Exit the application when the user selects a different command or presses the Esc key.

Again, the add-in worked flawlessly, and here's a sample resulting message box:

Handy to know that a single element has multiple warnings, isn't it? And, again, the OkPy agent added some really nice touches: the element type and ID of the element, related elements, and instructions on how to exit the add-in. The formatting's very professional too.

This is an example of an interactive add-in.

That's the limit of my explorations with OkPy so far.

One thing to note is that these add-ins are saved as .OKPY files, meaning, once you're satisfied with them, they're baked and don't change with the whimsies of the ever-evolving AI. And they're not black boxes either; you can view and modify the code.

In my nearly 40 years in the AEC industry, OkPy is the singular greatest innovation that I've seen. It's the cat's meow, the cream in my coffee. Bravo to the folks at Orkestra!

Speaking of, how do we distribute these add-ins? You need to use Orkestra, and—while there's no barrier to using OkPy or Orkestra (both have free tiers)—you'll need a paid license for both to be able to publish add-ins. OkPy Pro costs $24/month or $200/year (for unlimited prompts). Orkestra costs $100/year. Bundled together though, the price is $224/year. Downstream users only need the Orkestra license. (And you can also use Orkestra to distribute Dynamo and Grasshopper scripts in a managed way, extending its value.) Is it worth it? Well, that's a value judgement. But, for me, the answer's a resounding yes.

Someone smarter than me could, perhaps, figure out how to port these add-ins to PyRevit, but I'm not going down that path.

Imagine this tool in the hands of creatives, say architects who've never coded. A colleague of mine very recently participated in such a team that won a hackathon by using OkPy to read redlines from PDFs and make the corresponding changes in Revit. Now that's brilliant!

OkPy earns an A+ from me.

Challenge: use OkPy to create an add-in that allows you to select an element, see what sheets it's on, open a selected sheet, and zoom into the highlighted element automatically.

Update 10/15/2026: A sister article has been published: Orkestra Review: Distributing Tools—Dynamo or Grasshopper Graphs or OkPy Add-ins.

Free CA Bulk Exporter: PDF and DWG Batch Export

2026-10-06T18:05:00.000-07:00

Executive summary

CA Bulk Exporter is a free Revit productivity add-in developed by CA Tools to consolidate repetitive drawing-issue work into one batch process. It can export multiple sheets to PDF, DWG, or both; apply model-based DWG export setups; automate deliverable naming; and report progress and exceptions. The Autodesk App Store listing positions it as a one-screen issue-production utility for Revit.

Core capabilities

Batch output: Exports any number of selected sheets to PDF, DWG, or both in one run, replacing repeated use of Revit’s Print and Export dialogs.
PDF packaging: Creates one PDF per sheet or a single combined PDF for the selected package.
Standards-based DWG output: Reads named DWG Export Setups stored in the active model, preserving established layer mappings, units, and other office export standards.
Flexible naming: Builds filenames from sheet number, sheet name, revision, project fields, and configurable text or separators.
Sheet-set support: Loads existing Revit sheet sets for rapid reuse of predefined issue packages.
Selection tools: Displays sheet number, name, current revision, and sheet set; supports filtering, sorting, individual selection, and bulk selection.
Run visibility: Provides a live progress log and a completion summary identifying successful exports and skipped items.
Remembered settings: Retains the previous selection and output configuration to speed recurring issues.

Typical workflow

Select content: Open the exporter, review the model’s sheet list, search or filter the list, load a saved sheet set if appropriate, and select the required deliverables.
Choose formats: Enable PDF, DWG, or both. For DWG, select a named export setup already stored in the model.
Configure output: Choose the destination folder, optional format-specific subfolders, PDF options, DWG scope, and the filename rule.
Control conflicts: Decide whether existing files should be skipped, overwritten, or given an automatic suffix.
Run and review: Start the unattended batch, monitor the live log, and use the final summary to check exported and skipped items.

Output controls

PDF

Paper size and orientation follow each sheet’s title block. Output can be color, grayscale, or monochrome, with vector or raster processing choices for graphics-heavy sheets. Users can create separate PDFs or one combined package.

DWG

The exporter exposes the named DWG Export Setups available in the project, allowing teams to reuse their approved configuration rather than reconstruct settings for every issue. It also provides a choice between exporting sheets alone and including views placed on sheets.

Extended functionality in the public repository

CA Tools also publishes a public Bulk Exporter repository described as an all-in-one pyRevit tool. Its documented workflow extends beyond basic export to include sheets or views, view-type filtering, saved-set creation and deletion, CSV list export, custom filename construction, print-order controls, and index numbering. The repository specifies pyRevit 5.3.1/IronPython 2.7 and notes that native PDF export requires Revit 2022 or later. Because the repository and Autodesk marketplace describe different packaging and interface details, teams should verify which build they plan to deploy before standardizing instructions around these extended features.

Benefits for BIM production

Reduced repetitive labor: One configuration replaces repeated per-sheet print and export steps.
Improved naming consistency: Parameter-driven rules reduce manual renaming and package inconsistencies.
Standards compliance: Reuse of model-based DWG setups helps preserve approved CAD layers, units, and export behavior.
Faster recurring issues: Saved sets, remembered settings, and export profiles reduce setup time for weekly or milestone deliverables.
Better QA/QC: Logs, completion summaries, and explicit file-conflict handling make omissions and skipped outputs easier to identify.
Single-point workflow: Combined PDF and DWG production reduces context switching and supports consistent issue packaging.

Requirements and deployment

Supported platform: Autodesk Revit 2022–2027 on 64-bit Windows.
Price: Free in the Autodesk App Store listing.
Dependencies: The marketplace listing states that no additional frameworks or subscriptions are required.
Suite availability: The CA Tools website presents Bulk Exporter as part of its broader MSI-installed Revit productivity suite, which also targets Revit 2022–2027.

Considerations and limitations

The marketplace feature set is centered on sheets; some expanded functions for views, sheet-set management, indexing, and CSV export are documented in the separate public repository. Confirm feature availability in the installed build.
DWG quality still depends on the named export setup and project standards maintained in the Revit model.
Title-block metadata, sheet parameters, revisions, and printability must be maintained correctly for dependable naming and output.
Automated logs improve checking but do not replace a final review of file count, filenames, sheet order, graphical output, and revision status before transmittal.

Assessment

CA Bulk Exporter is best suited to teams that issue multi-sheet packages repeatedly and need predictable PDF/DWG deliverables without investing in a more complex publishing platform. Its strongest production value is not merely faster exporting, but the combination of reusable selections, controlled naming, established DWG standards, conflict handling, and an auditable run summary. For BIM managers, the practical deployment priority is to pair the add-in with governed export setups, parameter standards, and a documented preflight checklist.

Internet sources

Autodesk App Store — “CA Bulk Exporter”: primary source for features, output controls, price, and compatibility.
CA Tools website — “CA Tools | Revit Automation & BIM Productivity”: developer overview and suite deployment context.
GitHub — CATools2026/Bulk-Exporter: technical notes and extended pyRevit workflow.
RVT Plugins — “Review: CA Bulk Exporter — Streamlining Your Revit Export Process”: third-party overview of the workflow and benefits.

CA Bulk Exporter is brought to you by CA Tools. It's free.

This add-in is compatible with Revit 2022-2027.

There's more information available on the Autodesk Design and Make Marketplace »

Questions? Contact the developer »

OkPy: An AI-Assisted Python Development Environment for Revit

2026-10-05T18:13:00.000-07:00

Executive Overview

OkPy is an automation-development environment and AI-assisted tool builder that runs inside Autodesk Revit through the Orkestra add-in. It is designed to let AEC professionals create working Revit utilities—including their user interfaces and back-end logic—without building and packaging a conventional compiled add-in from scratch. Users can write tools directly, ask the OkPy Agent to generate them from plain-language requirements, test them against a Revit model, save them as portable OkPy files, and deploy approved tools locally or through Orkestra.

OkPy is broader than a fixed collection of commands. It combines three related offerings: a development environment for custom automation; an AI Agent that generates and revises tools; and a public library of ready-made Revit utilities. Orkestra supplies the host integration, ribbon access, tool distribution, analytics, permissions, and enterprise deployment layer. This makes OkPy most comparable to a low-code development platform, scripting environment, and AI coding assistant combined—not to a single-purpose Revit plug-in.

The product's key promise is to shorten the path from an automation idea to a repeatable, deployable Revit command. Its key risk is equally important: generated or user-written code can modify live project data at scale. Successful adoption therefore depends on testing, code review, release control, model backups, and clear separation between experimental and production tools.

Product Architecture

OkPy Editor

The full editor is aimed at tool creators. It combines a code editor, automatically generated input controls, a debugging console, result handling, and tool metadata in one environment. Current Revit documentation begins new tools in C#, while OkPy's broader documentation and history also describe Python and CPython-based development. Existing scripts may therefore require interpreter-specific review when moving between Revit generations.

OkPy Agent

The Agent provides a simplified conversational workflow. A user describes the Revit task, desired controls, and output; the Agent asks clarifying questions when needed, drafts the code and interface, and presents the result for testing. Published examples include a modeless Door Summary dashboard and a grid-renumbering utility. The generated result is a deterministic tool that can be saved and rerun, rather than a one-time chat response.

Orkestra Integration

OkPy ships with Orkestra and opens from the Orkestra ribbon tab in Revit. Orkestra can organize OkPy, Dynamo, and Grasshopper automations, place approved commands on Revit ribbons through Quick Access, distribute content across a firm, manage environments, and provide analytics. Local OkPy creation can be used independently, while organization-wide cloud deployment and management depend on Orkestra services and plan entitlements.

Public Tool Library

OkPy Tools is a browsable library of completed automations with documentation and demonstrations. It provides immediate value to non-developers and also serves as a reference for the kinds of interfaces and Revit API workflows that can be built.

Typical Tool-Creation Workflow

Open OkPy in Revit. Open a model, select the Orkestra ribbon tab, and launch OkPy.
Choose a starting mode. Create a blank tool in the editor, use the simplified Agent, or begin from a library example.
Describe the requirement precisely. Define the target categories, selection scope, parameters, transactions, units, interface controls, expected results, and failure conditions.
Generate or write the tool. Build the logic and user interface with C#, Python-compatible workflows, or Agent assistance, depending on the current environment.
Test in sandbox mode. Documentation shows a Test mode in which model changes are undone when the test window closes. This allows interface and result verification before saving.
Debug and refine. Use the console, results, screenshots, markups, and follow-up prompts to correct errors or improve the interface.
Save the tool. Store it locally as an OkPy file. Saving is explicit; the Agent does not automatically preserve the generated tool.
Publish when approved. Upload to an Orkestra workspace for controlled sharing, or deploy locally when cloud distribution is unnecessary.
Add to the production ribbon. Use Orkestra's Quick Access and workspace controls to expose vetted tools to end users without giving them the development environment.
Monitor and maintain. Track usage, revise tools when Revit APIs or standards change, and retain tested versions for rollback.

Interface and Development Capabilities

Automatically generated interfaces: OkPy can turn declared inputs into a user-facing form, avoiding the need to hand-code every dialog.
Advanced interfaces: Current product material describes WPF applications and web views for tools requiring data grids, color pickers, spreadsheets, complex layouts, or modeless interaction.
Model-aware prompts: Users can describe Revit categories, parameters, filters, and interactions in ordinary language. PDFs, spreadsheets, screenshots, and images can be attached as contextual references in supported Agent workflows.
Clarification and iteration: The Agent can ask questions when a requirement is ambiguous and maintain code state through a longer development conversation.
Markup workflow: Recent releases allow users to draw notes, arrows, boxes, and labels over a generated interface or host-screen capture, then send the marked image back to the Agent.
Reusable inputs and components: Developers can create, organize, and share input controls rather than rebuilding common interface elements.
Debug console: The editor exposes diagnostic output during development, which is essential for identifying Revit API, transaction, data-type, and selection errors.
Recovery snapshots: OkPy takes a local recovery snapshot before each run, retains up to five snapshots per tool, and opens restored snapshots as copies. This protects development work but is not a substitute for model backup or source control.

Current Ready-Made Revit Automations

The public OkPy Revit library currently advertises approximately fourteen tools. The catalog changes over time, but the published set demonstrates the platform's range across documentation, data, maintenance, modeling, and analysis.

PDF and DWG Exporter: Batch-exports sheets and printable views to PDF and DWG. It pools host-model and loaded-link content into one selection list, builds filenames from view or sheet parameters, and uses native Revit export settings.
Add Parameter to Project Families: Adds shared or non-shared parameters to selected editable component families and reloads them into the project. It supports parameters from an existing shared-parameter file or newly created definitions and reports skipped or failed families.
Parameter Mapper: Copies, combines, splits, or transforms values from source parameters into target parameters. Mapping presets can be saved and shared.
Material Find & Replace: Finds uses of a selected material and replaces them with another material across the model.
Linked & Imported DWG Detector: Lists linked and imported DWGs, identifies their owner views, and supports highlighting or navigating to a placement.
Place Family Instances from DWG Layer: Reads block insertion points on a selected linked-DWG layer and places a chosen Revit family type at those locations on the selected level.
Wall Types Filters Creator: Creates view filters for wall types, assigns customizable graphic overrides, applies them to view templates, and generates a color-coded legend.
Sheets Alignment: Aligns selected sheets to a reference sheet to standardize viewport or title-block-related arrangements.
Rotate View: Rotates plan views beyond routine cardinal orientation workflows.
3D View by Workset Creator: Creates a separate 3D view for each selected workset.
View Template Cleaner: Identifies and removes unused view templates.
Unreferenced View Cleaner: Removes selected views that are not placed on sheets.
Hatch Pattern Creator: Generates a hatch pattern from 2D line geometry.
Shadow Study: Builds a viewer from active-view geometry, including links, visualizes the sun path and projected shadows, and can record the result as a video.

Illustrative Agent-Built Workflow

OkPy's documentation uses a Door Summary dashboard to demonstrate the complete Agent workflow. The request specifies a level filter, family/type search, fire-rating filter, live counts, a sortable table, details for the selected type, and a Refresh command. The Agent produces a floating modeless dashboard, which can remain open while the user works in Revit. The developer tests it against the current model, verifies counts and filters, closes Test mode to roll back changes, and then saves or publishes the tool.

This example is significant because it goes beyond generating a short script. It demonstrates specification by natural language, a custom user interface, live model queries, interaction while Revit remains available, safe testing, local packaging, and enterprise publishing. Comparable tools could be created for warnings, family auditing, parameter QA, sheet review, standards checks, data extraction, or firm-specific model-maintenance tasks.

Local, Cloud, and Enterprise Deployment

Local files: Tools can be saved as portable OkPy files and run without publishing them to an organization.
Local Orkestra features: Orkestra's documented free tier includes the local Revit player, local Quick Access commands, and playlists.
Cloud workspaces: Approved tools can be published to online workspaces for organized distribution and controlled updates.
Ribbon delivery: Administrators can expose tools as familiar Revit ribbon buttons, allowing end users to run an approved command without editing its code.
Cross-platform automation library: Orkestra can manage OkPy alongside Dynamo and Grasshopper automation and distribute content to Revit, Civil 3D, AutoCAD, and Rhino.
Enterprise controls: Current product material references analytics, environments, GitHub synchronization, schedules, SSO, Azure AD, console management, and playlists. Availability depends on the Orkestra plan.
Autodesk Construction Cloud: Recent releases add tooling for Issues, RFIs, Submittals, Forms, Photos, Assets, Clash results, properties, reviews, sheets, Docs metadata, links, Takeoff, and project administration using the host's signed-in Autodesk session.

Pricing, Availability, and Compatibility

OkPy Agent Plans

Community: Free, with a 5 daily prompt limit, a standard AI model, basic code generation, and community support.
Pro Monthly: Currently listed at US$24 per month, with unlimited daily prompts, 50 super conversations per month, access to more advanced AI models, and priority support.
Pro Annual: Currently listed at US$200 per year, equivalent to about US$16.67 per month, with the same published Pro allowances.

OkPy and Orkestra

Foundational OkPy documentation describes the programming environment as free and included with Orkestra. Orkestra itself has a free local tier; cloud deployment, enterprise administration, and related services use subscription plans. Firms should distinguish the cost of the AI Agent from the cost of organization-wide Orkestra management.

Revit Compatibility

Current public pages do not present a single definitive OkPy version matrix. Community evidence shows Orkestra 2.0 operating across Revit 2020–2026 after an installer correction, and current documentation addresses Revit 2025 CPython behavior. The latest release information identifies Orkestra 2.5.1.2. Compatibility should therefore be confirmed against the exact Revit, Orkestra, Python/.NET, add-in, and package versions used by the firm rather than inferred from isolated forum reports.

Practical BIM and Automation Assessment

Where OkPy Adds Value

Rapid prototyping: BIM staff can move from a workflow problem to a tested interface and command much faster than with a conventional add-in project.
Bridges the skills gap: The Agent makes Revit API automation more accessible to users who understand the BIM problem but are not professional software developers.
Firm-specific utilities: OkPy is well suited to narrow standards, QA, naming, data, selection, documentation, and cleanup requirements that commercial add-ins may not address.
Reusable deterministic tools: Once generated and approved, the output can be saved, versioned, deployed, and rerun consistently instead of relying on a fresh AI response each time.
Interface development: Automated forms, dashboards, and advanced interface options reduce one of the biggest barriers to turning scripts into user-friendly firm tools.
Integrated distribution: Orkestra can move a successful prototype into controlled ribbon deployment without a separate software-distribution stack.
Shared automation ecosystem: The same management platform can accommodate OkPy, Dynamo, and Grasshopper, reducing fragmentation for multidisciplinary design-technology teams.

Best-Fit Users

OkPy is most useful for BIM coordinators, design technologists, computational designers, Revit power users, digital-practice teams, and developers who need to build and maintain a portfolio of internal automations. It can also serve noncoders when the Agent produces a well-bounded tool and a qualified reviewer validates the result. Firms seeking only one fixed command may prefer a conventional add-in with a narrower support surface.

Limitations and Governance Considerations

Generated code can be wrong: A plausible interface or successful test does not prove that the tool handles every project state, category, unit, phase, design option, workset, link, or failure condition.
Live-model risk: Revit API tools can modify or delete large numbers of elements. Test mode protects the development run described in the documentation, but production use still requires backups, worksharing controls, and rollback procedures.
Version sensitivity: Revit API changes and the shift from IronPython to CPython can break previously working tools. Community examples document .NET collection and Python interoperability differences in Revit 2025.
Code review remains necessary: AI output should be reviewed for transaction boundaries, exception handling, unit conversion, element filtering, null values, performance, and unintended changes.
Security exposure: Tools can access project data and, depending on their code, local files, network resources, spreadsheets, web services, or Autodesk Construction Cloud. Limit who can develop, publish, and update production tools.
Dependency management: Python packages, .NET libraries, Dynamo packages, and Revit builds must be controlled to keep deployed automations reproducible.
User-interface quality varies: Agent-generated forms may require refinement for accessibility, validation, cancel behavior, progress feedback, localization, and large projects.
Library tools still require testing: Public tools should not be assumed to match firm parameters, naming, templates, coordinates, links, export standards, or approved content.
AI plan limits: The free Agent tier has prompt limits and basic generation; Pro allowances include a finite number of premium conversations.
Limited independent benchmarking: Available evidence is dominated by Orkestra documentation, release notes, demonstrations, and community posts. Public long-term comparisons of generated-tool reliability are limited.

Recommended Evaluation Before Production Deployment

Confirm official support for every deployed Revit version, the current Orkestra release, required runtimes, and the intended Python or C# engine.
Install OkPy in a controlled test environment and review code signing, antivirus behavior, permissions, update channels, and network endpoints.
Select a small, measurable workflow with a clear manual baseline and low consequence if it fails.
Write acceptance criteria covering scope, element categories, parameter bindings, units, worksets, links, phases, design options, undo behavior, and error reporting.
Generate the tool with the Agent or editor, then inspect the code before running it against a model.
Test in OkPy Test mode and confirm that temporary model changes are rolled back as documented.
Repeat testing on detached copies of small, large, central, linked, and intentionally imperfect projects.
Validate performance, warnings, model size, transactions, element ownership, synchronization, and results after reopening the file.
Publish only reviewed versions to a restricted workspace; separate development, pilot, and production libraries.
Assign an owner, version number, supported-Revit range, change log, test model, and rollback package to every production tool.
Restrict Agent and publishing rights according to role, and audit tools that read files, call web services, or access Autodesk Construction Cloud.
Measure time saved, failure rate, maintenance effort, support demand, and adoption before scaling the workflow across the firm.

Sources Consulted

OkPy documentation — Introduction
OkPy documentation — Getting started in Revit
OkPy documentation — Build with the Agent
OkPy documentation — Recovery and tool backups
OkPy Tools — Revit automation library
Orkestra — AEC automation at scale
OkPy Agent — current plans
Orkestra GitHub — current release notes
Orkestra community — multi-version Revit compatibility discussion
Orkestra community — Revit 2025 CPython compatibility example

Source-quality note: OkPy and Orkestra documentation, product pages, release notes, and the public tool catalog are the principal sources for capabilities and pricing. Community posts were used to identify real version-migration issues, but they are not an official support matrix. Compatibility and production reliability should be confirmed with the current installer and a firm-controlled test.

OkPy is brought to you by Orkestra. A free "Community" version is available with a "standard" AI model and a 4 prompt daily limit. The "Pro" version, with an "advanced" AI model and unlimited prompts, costs $24/month or $200/year.

Revit version compatibility was not known at press time.

There's more information available on the Orkestra website »

Questions? Explore the Orkestra forum »

Editor's Note: For a while now, I've wanted a tool that would sync, reload selected links, and sync again. Something I could kick off and walk away from. With OkPy, I created Hammer Sync in just 20 minutes with the daily allotment of 4 free prompts. Zero coding required.

Hammer Sync, because, sometimes, you just want a hammer.

If there was a SUPER DUPER Editor's Choice award, OkPy would be the first winner.

The next time I develop something with OkPy, I'll document it in a review.

SWAPP.AI: An Operational Intelligence Layer for Architecture

2026-10-04T12:09:00.000-07:00

Executive Overview

SWAPP.AI is an enterprise architecture-production platform that applies firm-specific artificial intelligence directly inside Autodesk Revit and Graphisoft Archicad. Its Revit experience is centered on an agentic assistant called Frank, which can read and write the live BIM model rather than merely answer questions or generate instructions. SWAPP positions the system as an operational intelligence layer: it executes documentation, modeling, annotation, coordination, and quality-control work using the firm's established standards and prior production decisions.

The platform's principal value is large-scale construction-document automation. Published capabilities include creating and organizing views and sheets, placing dimensions, tags, and callouts, generating schedules, modeling walls, doors, fixtures, finishes, and worksets, detecting collisions and annotation conflicts, checking accessibility conditions, and validating a model or drawing set against firm rules. SWAPP states that its automation can address up to 80% of repetitive documentation tasks, although actual scope and savings vary by project, onboarding, and encoded standards.

SWAPP is not a conventional self-service Autodesk Marketplace utility with a fixed command list. Deployment begins with a vendor-led onboarding engagement, the workflows are configured to the architecture firm's methods, and commercial access is sold through custom, credit-based pricing. The most accurate description is therefore a managed AI production system integrated with Revit, with human approval and auditability built into its execution model.

Frank: The AI Architect Inside Revit

Live-Model Execution

Frank operates in the active Revit environment and is described as reading and modifying the live model without creating a disconnected export or copy. Users can trigger work conversationally or launch configured skills and scripts. Frank proposes an operation, the user reviews or previews it, and execution occurs only after approval. This human-in-the-loop pattern is important because the system is acting on liability-bearing project data rather than producing advisory text.

Published Revit Capabilities

Agentic modeling: Creates or adjusts walls, doors, fixtures, finishes, and worksets, including building-scale 2D-to-3D workflows.
Dimensions and annotations: Places exterior and interior dimension strings, tags, room tags, callouts, and other annotations according to firm rules.
Views and sheets: Generates views, establishes sheets, and organizes documentation sets.
Model and set QA: Checks content against encoded standards, flags discrepancies, and can propose corrections.
Collision and graphic cleanup: Detects model conflicts and overlapping annotations, then resolves approved issues in Revit.
Accessibility review: Identifies certain ADA-related conditions and proposes model changes.
Reusable automation: Prompts and successful procedures can be saved as repeatable skills or scripts, turning one-off instructions into standardized firm tools.
Traceability: SWAPP states that actions are reversible and recorded in an audit trail.

Firm-Specific Standards and Workflow Memory

SWAPP differentiates itself from generic automation by learning how a particular firm documents and checks projects. The source material emphasizes completed project work, production history, annotation decisions, QA logic, graphic conventions, and user corrections—not merely a standards manual. The goal is to encode tacit knowledge normally held by experienced technical staff and apply it consistently across offices and projects.

Onboarding

SWAPP states that a typical engagement begins with a roughly two-week onboarding process. The vendor and firm map recurring workflows, identify high-value tasks, encode standards, and configure initial skills. Because implementation is tailored, two customers may receive materially different automation even though both use Revit.

Compounding Knowledge

When users correct or reject an output, the system can incorporate that feedback into workflow memory. This is intended to make later projects more consistent and reduce repeated explanation. It also creates a governance obligation: corrections should be reviewed by authorized staff before they become reusable institutional rules.

Knowledge Retention

The platform is marketed as a way to preserve senior staff judgment when key employees move roles or retire. It can capture recurring choices about dimensions, tagging, sheet organization, model cleanup, and QA review so that production knowledge remains available to the firm.

Core Documentation and Modeling Workflows

Construction-Document Production

SWAPP targets complete drawing-set production rather than isolated shortcuts. Published examples include plan and detail dimensions, annotation placement, view generation, sheet creation, schedules, callouts, and set-wide consistency checks. The system can apply the same configured logic across many views or sheets, which is where it can exceed the value of a typical single-command add-in.

2D-to-3D Modeling

Case-study and product material describes converting 2D design information into Revit content, including walls, furniture or fixtures, and organized groups or worksets. This can accelerate model initiation or development when the incoming design source is reliable and the target Revit standards are clearly defined.

Design-Change Propagation

Because Frank works against the live model, approved changes can be reflected through associated views and documentation using native Revit relationships. This does not eliminate drawing review; it reduces the repetitive work needed to restore consistency after a model change.

QA/QC and Coordination

SWAPP can compare the model and documentation set with firm rules, identify missing or inconsistent annotations, detect selected collision conditions, and present proposed fixes. A 2026 Revit demonstration showed a preview before dimension placement, a color-coded quality-control legend, grid adjustment to crop regions, and room-tag correction against a customer's guidelines.

Typical Implementation and Project Workflow

Select target workflows. Identify repetitive, rules-based work with meaningful volume, such as dimensions, tags, view setup, sheet creation, schedules, model setup, or recurring QA checks.
Provide approved references. Supply completed projects, templates, families, guidelines, and examples that accurately represent current firm standards.
Configure and test skills. SWAPP's implementation team encodes the rules and validates initial outputs with designated firm experts.
Run on a live or controlled project. Users trigger Frank in Revit, review previews or proposed actions, and approve execution.
Perform targeted QA. Check generated model elements and documentation against known benchmarks rather than assuming automated output is correct.
Capture corrections. Approved user feedback informs reusable workflow memory and future skills.
Scale across projects. Mature skills can be applied across teams and offices, subject to project-specific codes, clients, templates, and exceptions.
Measure value. Track credit consumption, production hours saved, rework, documentation consistency, warnings, RFIs, and correction effort.

Reported Production Use and Case-Study Evidence

Place Studio: A SWAPP case study for a five-tower, 550-unit mixed-use development in Sydney describes AI agents creating views, sheets, tags, and schedules across parallel Revit models. Reported outcomes include a 27% reduction in coordination issues and a 40% decrease in documentation inconsistencies. These are vendor-reported project results, not an independent benchmark.
SNHA, a Woolpert company: A published case-study summary reports that a repetitive mission-critical documentation process dropped from approximately two weeks to under 48 hours. A later live demonstration discussed reorienting a fully annotated prototype building in a few days rather than several weeks.
MYS Architects: A third-party case-study page describes 2D-to-3D conversion, automated modeling, standards adaptation, and marking modeling errors on sheets for targeted correction.
Current adopters: SWAPP and an independent AEC publication identify firms including Stantec, Woolpert, MOREgroup, AHA, MYS Architects, Page, and HGA as customers or users.
Aggregate vendor metrics: SWAPP currently reports more than 35 million square feet of production-grade construction documents and more than 104,000 production hours saved over two years. These figures should be treated as vendor claims and evaluated against the firm's own pilot metrics.

Integrations, Deployment, and Security

Revit and Archicad

SWAPP supports both Autodesk Revit and Graphisoft Archicad, carrying the same firm-tuned logic across mixed-platform practices. For Revit, the system is described as a native intelligence layer that executes real BIM actions in the live model.

Cloud Architecture

The platform is cloud-based and does not require a SWAPP server installation inside the customer's network. This reduces local infrastructure but introduces dependence on network connectivity, service availability, compatible authoring-tool versions, and enterprise identity and access controls.

Connected Platforms

Current integration material also references Autodesk Forma. Procore and Trimble connections are described as coming in 2026, intended to bring RFI history, field execution, estimating, quantities, and constructability signals back into design. These roadmap connections should be verified before including them in implementation scope.

Security Claims

SWAPP and independent product sources state that the platform is ISO/IEC 27001:2022 certified.
The vendor states that customer intelligence remains associated with the firm and that customer data is siloed.
Human approval, reversible actions, and audit trails are positioned as core controls.
Architecture firms should still review data-processing terms, model access, subprocessors, geographic hosting, retention, deletion, incident response, intellectual-property ownership, and whether customer data is used for generalized model training.

Pricing and Commercial Model

SWAPP does not publish a simple per-seat or perpetual add-in price. Current pricing uses a custom, credit-based system aligned with the work executed. Documentation, modeling, annotation, optimization, and other tasks consume different amounts of credit based on complexity and compute effort.

Custom quotation: Firms provide information about organization size, project types, Revit use, and anticipated work to receive pricing.
Flexible allocation: Credits can be consumed across projects and workflows rather than being tied to a single fixed scope.
Usage visibility: The vendor states that customers can review credit consumption and compare it with hours or production effort saved.
No public fixed tiers: Contemporary independent listings also describe pricing as custom or enterprise-oriented.
Budgeting requirement: A useful commercial evaluation should compare credits consumed with fully burdened labor savings, implementation effort, QA time, subscription commitments, support, and minimum purchase requirements.

Practical BIM Assessment

Where SWAPP Adds Value

High-volume documentation: The strongest fit is repetitive production across many views, sheets, units, buildings, or parallel models.
Firm-wide consistency: Centralized skills can apply annotation, graphic, and QA standards more consistently than isolated user macros.
Knowledge retention: Workflow memory can preserve specialist methods and reduce dependence on a few experienced staff members.
Live-model automation: Native Revit execution avoids the handoff and reconstruction associated with external drawing generators.
Capacity without proportional hiring: Firms may increase documentation throughput while redirecting skilled staff toward design, coordination, and review.
Continuous improvement: Reviewed corrections can strengthen future automation rather than requiring each project to restart with generic rules.

Best-Fit Firms and Projects

SWAPP is best suited to architecture practices with established Revit standards, recurring project types, significant construction-document volume, and leadership willing to formalize review and automation governance. Strong candidates include multifamily, mixed-use, healthcare, institutional, workplace, hospitality, and mission-critical or data-center work. Very small firms, one-off projects, weakly standardized models, or teams seeking an inexpensive self-install add-in may find the operating model less suitable.

Limitations and Governance Considerations

Not an instant generic tool: Value depends on onboarding, suitable reference projects, workflow mapping, and continued expert review.
Automation scope varies: The claim of automating up to 80% of documentation does not mean every project or task will achieve that percentage.
Source-data quality matters: Inconsistent templates, families, parameters, annotations, and legacy projects can encode the wrong lessons.
Human responsibility remains: Architects and engineers must approve outputs and retain responsibility for code compliance, accessibility, life safety, constructability, coordination, and professional services.
ADA checking is not comprehensive code analysis: Automated accessibility findings depend on modeled conditions and configured rules; they do not replace jurisdictional review.
Live-model changes carry risk: Automated actions can affect large numbers of elements, views, dimensions, tags, and sheets. Worksharing, ownership, backups, audit trails, and rollback procedures are essential.
Workflow memory requires curation: A correction from one project may not be appropriate as a firm-wide rule. Only approved decisions should be promoted.
Cloud and service dependency: Availability, latency, outages, authoring-tool compatibility, and contract termination can affect production access.
Commercial predictability: Credit-based pricing may be harder to forecast than per-seat licensing until real project consumption is measured.
Limited independent technical detail: Many performance figures and capability claims originate from SWAPP or vendor-hosted case studies. Independent demonstrations provide useful corroboration but do not replace controlled testing.

Recommended Evaluation Before Production Deployment

Request a live demonstration using a representative firm project rather than a generic sample.
Confirm supported Revit versions, installation method, user roles, network requirements, identity controls, update process, and support coverage.
Select one high-volume, rules-based workflow with a known manual baseline, such as dimensioning, room tagging, sheet setup, or a recurring building-prototype update.
Provide only current, approved templates and completed project examples; exclude legacy work that does not represent desired standards.
Define measurable acceptance criteria for placement accuracy, adherence to standards, correction rate, execution time, credit use, and rollback.
Test previews, approvals, audit trails, undo or reversal, failure handling, element ownership, and synchronization in a workshared Revit environment.
Review outputs across plans, sections, elevations, details, schedules, sheets, exports, warnings, and model-performance metrics.
Validate accessibility and QA findings against independent manual review and documented firm procedures.
Test how user corrections become reusable workflow memory and establish who can approve changes to shared skills.
Complete legal, privacy, cybersecurity, insurance, intellectual-property, and client-contract reviews before uploading confidential project data.
Compare credits and implementation costs with fully burdened labor saved, avoided rework, schedule improvement, and ongoing QA effort.
Approve expansion only after the pilot demonstrates repeatable value without weakening professional oversight or model quality.

Sources Consulted

SWAPP.AI — operational intelligence for architecture
SWAPP.AI — Frank, the AI architect for Revit and Archicad
SWAPP.AI — integrations
SWAPP.AI — pricing
SWAPP.AI — Place Studio multi-tower case study
aec+tech — Frank inside Revit
aec+tech — live Revit demonstration with Woolpert
aec+tech — MYS Architects case study
CaseStudies.com — SNHA/Woolpert case-study summary
Autodesk Platform Services — SWAPP customer story

Source-quality note: SWAPP's current product, integration, pricing, and case-study pages are the main sources for capabilities and commercial positioning. Third-party demonstrations and case-study summaries were used to cross-check live Revit behavior and customer-reported outcomes. Aggregate savings and project metrics remain vendor or customer claims and should be validated through a firm-specific pilot.

SWAPP.AI is brought to you by SWAPP.

Revit version compatibility was not known at press time.

There's more information available on the SWAPP website »

Questions? Contact the publisher »

Skema: A Web-Based Generative-Design and BIM-Automation Platform

2026-10-03T11:07:00.000-07:00

Executive Overview

Skema is a web-based generative-design and BIM-automation platform for architecture and AEC teams. Its Revit add-in is the interoperability layer that connects a firm’s existing BIM knowledge to Skema and returns developed designs to Revit. The workflow is unusual among generative tools because it begins with proven Revit content—such as repeatable units, assemblies, families, parameters, and office standards—rather than producing disconnected conceptual geometry that must later be rebuilt.

Through the add-in, teams organize Revit model groups as reusable catalog units, validate and upload them to a cloud Design Catalog, update or remove catalog content, and synchronize Skema-generated layouts back into Revit as native BIM. The broader Skema application then lets designers compose and morph those units within new footprints, compare alternatives using live project metrics, and progress from early feasibility toward a detailed model.

The key distinction is that Skema is not simply a ribbon utility running entirely inside Revit. The add-in handles catalog creation and BIM exchange; option generation, catalog configuration, and metric-driven design occur primarily in Skema’s cloud workspace.

Primary Roles of the Revit Add-in

1. Create and Maintain Design Catalogs

The catalog side of the add-in converts selected Revit model groups into reusable design units. A unit may represent an apartment, hotel room, patient room, classroom module, office neighborhood, building core, façade bay, or another repeatable assembly. The upload preserves the BIM information associated with the group so the component can be stretched, morphed, arranged, and later reconstructed as Revit content.

2. Validate Revit Content Before Upload

The plug-in identifies units, compares them with the cloud catalog, and reports validation or synchronization status. Teams can add new units, remove obsolete ones, or re-upload only units that have changed. Unchanged catalog content remains intact, reducing unnecessary replacement.

3. Synchronize Skema Designs into Revit

After a design is developed in the web application, the add-in translates the layout into a Revit project. Published material describes native walls, floors, roofs, families, rooms, parameters, materials, and other BIM components rather than a flattened or reference-only import. The objective is to continue development and documentation without remodeling the concept from scratch.

End-to-End Workflow

Prepare the Revit source model. Identify proven units or assemblies, clean their content, organize them as model groups, and confirm that families, parameters, levels, rooms, and standards are suitable for reuse.
Install and open the Skema add-in. Open a Revit project, launch Skema from its ribbon tab, and sign in to the associated Skema account.
Define catalog units. Select model groups and establish which content will become reusable units. Units initially enter the catalog with a classification that can be refined later.
Review validation status. Resolve conditions that prevent clean upload and compare local units with their catalog versions.
Upload the catalog. Send the approved Revit-derived units and their BIM data to the Skema workspace.
Configure the catalog in Skema. Assign unit types, space-use classifications, default wall, slab, roof, and other assemblies, analytical meshes, interactive elements, and solver constraints.
Compose a new building. Arrange catalog units within a footprint, morph them where permitted, and generate alternative layouts.
Evaluate live metrics. Compare options using project measures such as unit mix, area, floor-area ratio, and other configured performance indicators.
Synchronize to Revit. Use the add-in to generate or update the native Revit model from the selected Skema option.
Continue detailed development. Audit the delivered model, then proceed with coordination, documentation, specifications, code review, engineering, and construction-detail work in Revit.

Design Catalogs and Generative Composition

Reusable Firm Knowledge

Skema positions Design Catalogs as a way to retain lessons already embedded in completed Revit projects. Instead of treating a prior model as a static archive, selected assemblies become configurable building blocks for future work. This is especially valuable for firms with repeatable typologies, standardized room modules, branded design systems, or substantial investment in vetted Revit content.

Morphing and Constraints

Catalog units can be made stretchable or morphable within boundaries established during setup. Constraints may protect fixed dimensions, circulation requirements, service zones, structural logic, or other relationships. Interactive elements can be designated so users retain control over important parts of a layout while automated processes adjust the remainder.

Default Assemblies

The catalog can assign default exterior walls, interior walls, slabs, roofs, and other systems. These mappings help Skema reconstruct the chosen design with native Revit assemblies rather than generic conceptual surfaces.

Metrics-Driven Options

As units are added, removed, or rearranged, the platform updates project measures in real time. Public product material highlights unit mix and floor-area ratio, with additional metrics depending on project type and configuration. This supports option comparison and feasibility decisions before the design moves deeper into documentation.

Revit Content Preparation and Synchronization

Model-group foundation: Current help material emphasizes uploading Revit model groups substantially as they already exist, with less reformatting than earlier workflows required.
Incremental updates: When one unit changes, the add-in can update that unit while leaving unchanged catalog units in place.
Catalog comparison: Users can review differences and validation status before synchronizing revised content.
Downloaded source: If the original local Revit source file is unavailable, the catalog-management workflow can provide a downloadable copy for continued editing.
Constraint review: Updating a unit may require its solver constraints to be checked or re-established after upload.
Native BIM objective: Vendor material describes the returned model as clean, editable, and suitable for continued detailed design, with Revit intelligence retained rather than reduced to simple solids.
Bidirectional relationship: Independent summaries characterize the Revit connection as bidirectional. In practice, teams should confirm the exact synchronization scope, conflict handling, and overwrite behavior for their subscription and current plug-in release.

Interoperability and Platform Scope

Skema’s public product and pricing material lists connections to Revit, Rhino, SketchUp, Miro, and related design workflows. Revit is the principal BIM endpoint for catalog capture and native-model delivery, while other connections support conceptual form-making, collaboration, or visualization. Independent product directories also report IFC export.

The platform is therefore most effective when treated as part of a connected early-design ecosystem rather than as a standalone Revit command. Its value depends on how well catalog content, design constraints, metrics, and downstream BIM standards are coordinated across the firm.

Compatibility, Installation, and Access

Supported Revit releases: Current Skema help documentation lists Revit 2022, 2023, 2024, 2025, and 2026.
Installation access: The installer can be downloaded from the platform’s plug-in and connections area, the Unit Catalog workflow, or the export workflow after signing in.
Project requirement: A Revit file must be open before the plug-in can be initiated.
Ribbon location: Successful installation adds a Skema tab and a Skema Start command to Revit.
Account and cloud dependency: Users sign in to Skema through the add-in, and catalog upload, cloud design, and synchronization require network access.
Code-signing caution: The current help article states that the plug-in installer is unsigned and may trigger Windows and Revit warnings. The documented workflow instructs users to proceed and choose Always Load. Enterprise teams should independently validate the installer, publisher provenance, hashes, permissions, and security approval rather than relying solely on that instruction.
Installation location: The installer is expected to place the add-in in the appropriate Revit Addins folder; this should be confirmed during deployment.

Pricing and Plans

Trial and entry access: Skema advertises a free trial for individual architects. Independent summaries describe a community or free tier, but the precise continuing limits should be verified in the current signup flow.
Professional plan: Public pricing currently lists a full-featured individual plan at US$199 per month, with a lower effective rate when billed yearly.
Team and enterprise use: The vendor offers team and enterprise options for wider deployment, advanced workflows, firm catalogs, custom solutions, and implementation support. Current enterprise pricing requires direct engagement.
Commercial scope: Plans include the cloud design environment, catalog functions, BIM automation, metrics, and integrations; the Revit add-in is part of that service rather than a simple perpetual desktop license.
Pricing caution: Plan names, seat minimums, storage, catalog limits, export rights, trial duration, and integration entitlements can change. Confirm the current pricing page and contract before budgeting.

Practical BIM Assessment

Where It Adds Value

Reduces concept-to-BIM rework: The central benefit is carrying approved schematic logic into native Revit instead of recreating the design after early approval.
Reuses proven solutions: Firms can convert established units and assemblies into a repeatable design system rather than beginning every project from a blank model.
Supports rapid option studies: Catalog-driven composition and live metrics enable more alternatives to be tested while preserving known BIM logic.
Improves continuity of standards: Revit families, parameters, materials, and assemblies can inform early design instead of being introduced only after handoff.
Creates organizational memory: A maintained catalog can capture design intelligence that might otherwise remain buried in past project files or individual staff experience.
Potential schedule compression: Vendor testimonials describe work that once required days or weeks being completed much faster. Actual savings depend heavily on catalog maturity, typology, and QA effort.

Best-Fit Users and Project Types

Skema is best suited to architecture firms, owners, developers, design technologists, BIM managers, and computational-design teams working with repeatable building types or modules. Strong candidates include multifamily residential, hospitality, healthcare, education, workplace, mixed-use, and data-center projects. One-off forms with little repetition may receive less value unless the firm develops an appropriate catalog strategy.

Limitations and Governance Considerations

Catalog preparation is a real investment: Revit groups must be clean, consistent, and intentionally structured. Poor source content will be reproduced and amplified.
Group behavior requires discipline: Nested groups, attached details, hosted elements, constraints, levels, room boundaries, design options, and unusual family behavior should be tested carefully.
Generative output is not automatic approval: Unit fit and live metrics do not replace code review, accessibility analysis, egress, fire and life safety, zoning, structure, MEP coordination, constructability, specifications, or professional judgment.
Native does not mean office-ready: Returned Revit content still requires audit for naming, worksets, phases, parameters, room bounding, joins, warnings, materials, detail levels, view standards, and model performance.
Synchronization risks: Teams need clear rules for ownership, versioning, overwrite behavior, rejected changes, deleted objects, and the system of record.
Cloud-data governance: Uploading firm-developed BIM content may involve intellectual property, client restrictions, confidentiality, retention, support access, geographic hosting, and contractual requirements.
Security review: The unsigned installer noted in current help documentation is a material enterprise-deployment concern and should pass formal IT review.
Subscription dependency: Access to catalogs, generation, and synchronization depends on an active service and compatible plug-in versions.
Metrics depend on configuration: Area, counts, unit mix, and FAR are only as reliable as space classifications, boundaries, catalog data, and project assumptions.
Public claims exceed independently verified detail: Most technical claims originate from Skema. Independent directories broadly confirm pricing and interoperability but do not replace a controlled Revit pilot.

Recommended Evaluation Before Production Deployment

Confirm the current plan, trial scope, Revit-version support, export rights, catalog limits, data terms, and implementation services with Skema.
Submit the installer to IT for publisher verification, malware scanning, code-signing review, and controlled packaging before allowing Always Load.
Select a completed, nonconfidential project with a repeatable unit type and known Revit-quality baseline.
Audit candidate model groups for nested content, hosted families, levels, rooms, parameters, constraints, materials, warnings, and group-exclusion behavior.
Create a small pilot catalog and document every validation message, upload requirement, classification, assembly mapping, and constraint.
Modify one catalog unit in Revit, re-upload it, and verify change comparison, unchanged-unit preservation, and any constraints that must be restored.
Generate several new layouts within different footprints and test the permitted morphing range, fixed dimensions, circulation, adjacencies, and live metrics.
Synchronize a selected option to a new Revit file and compare native elements, families, type definitions, rooms, parameters, materials, locations, and dimensions with the source intent.
Round-trip a controlled design change to determine what updates, what is replaced, and what remains independent.
Measure catalog-preparation labor, option-generation time, Revit cleanup, file size, warnings, model performance, and documentation readiness against the existing workflow.
Review data security, intellectual-property ownership, retention, service availability, exports, termination rights, and recovery of catalog source files.
Define catalog ownership, approval, versioning, naming, QA, training, and change-management standards before broad deployment.

Sources Consulted

Skema — “Generative Design for AEC”
Skema — plans and pricing
Skema Help Center — “Create a Catalog | Upload a Catalog”
Skema Help Center — “Managing Your Catalog”
Skema — Revit interoperability demonstration
Skema — synchronizing a project to Revit demonstration
buildingtech.pro — independent Skema product assessment
BIM Tools Hub — Skema pricing and feature review

Source-quality note: Skema’s website and help center are the primary sources for workflow, compatibility, installation, and product claims. Independent sources were used to cross-check public pricing, interoperability, and adoption considerations. Because the platform evolves rapidly, confirm the current add-in build and plan entitlements during a trial.

Skema is brought to you by Skema. It's priced at $199/month or $750/month for a 5-seat team license. A free "Starter" version is available.

Skema is compatible with Revit 2022-2026.

There's more information available on the Skema website »

Questions? Contact the publisher »

ELLAH-M: A Structural-Production Toolkit

2026-10-02T18:42:00.000-07:00

Executive Overview

ELLAH-M is a Revit productivity add-in developed specifically for structural engineers and BIM teams. Its currently published core automates structural-column numbering, foundation and pile numbering, and two-way Excel exchange. Broader tools presented on the developer’s website extend the concept toward project setup, view and sheet creation, opening and recess modeling, and future automated pile layout.

The add-in’s central design idea is continuity across the structural workflow: marks assigned to columns can drive the identification of supporting pile caps and individual piles; selected model data can move to Excel for coordination and return to the correct Revit elements; and office standards can be reused to establish views and sheets in new projects. This makes ELLAH-M less of a general-purpose utility collection and more of a structural-production toolkit centered on numbering, information consistency, and drawing setup.

Product-status distinction: Autodesk Marketplace currently presents column numbering, foundation and pile numbering, and Excel export/import as the principal released capabilities. The developer’s version 1.3.1 website also advertises Project Setup and FastVoid as available in the trial, while some page sections still label FastVoid and automated pile layout as in development. Teams should therefore confirm the exact feature set in the installed Marketplace build before relying on website previews.

Structural Column Numbering

ELLAH-M scans structural columns, sorts them according to the chosen project logic, and writes sequential identifiers directly to Revit’s native Mark parameter. The tool is intended to replace manual renumbering across multiple levels while preserving a predictable relationship between vertically aligned structural members.

Published Capabilities

Multi-level numbering: Columns can be numbered across the full project rather than one level at a time.
Existing-mark continuity: The Marketplace states that the tool can continue from existing manual numbering without overwriting intentional marks.
Preview before commit: Proposed changes can be reviewed before values are written to the model.
Native undo: Changes support Revit’s standard Ctrl+Z undo workflow.
Structural-category targeting: The tool is described as operating on structural columns, limiting accidental edits to unrelated architectural columns or other categories.
Flexible scope: Developer material describes full-project, single-floor, selected-range, and manual numbering modes.
Snake Path: A newer interactive method lets the user move the cursor over columns in the desired sequence without clicking every element. Published controls indicate Space can skip a number and Ctrl can finish the path.
Output choice: Developer demonstration material states that Snake Path can write the sequence to Mark or Comments while maintaining vertical numbering continuity across floors.

Foundation and Pile Numbering

ELLAH-M links substructure identification to the structural column above. If a column is marked 140, the supporting pile cap can receive 140 and the piles beneath it can be labeled 140A, 140B, 140C, and so forth. This preserves a recognizable vertical relationship from superstructure to foundation plan and reduces disconnected manual naming.

Published Capabilities

Column-driven marks: Foundation and pile identifiers derive from the supported column’s mark.
Multiple foundation arrangements: The Marketplace lists support for single piles, grouped piles, and pile caps serving multiple columns.
Office-family support: The developer states that the workflow works with standard Autodesk families and custom office families.
Bilingual family recognition: Published material specifically identifies English and Hebrew family names.
Direct Revit storage: Values are written to the native Mark parameter, allowing them to flow into ordinary tags and schedules.

The method is most valuable when the structural team’s naming standard intentionally ties pile and cap identifiers to column marks. Firms using independent foundation numbering, grid-based codes, or contractor fabrication marks will need to verify whether the built-in logic can match their conventions.

Excel Export and Import

The Excel workflow exports selected Revit information to a structured XLSX workbook, allows users or external collaborators to edit values, and imports updates back into the correct model elements. This supports coordination with office schedules, reviewers, and external structural applications that work more efficiently with tabular data.

Published Workflow

Select an element category and level.
Choose the parameters to include.
Export a styled Excel workbook containing model data.
Edit approved values outside Revit.
Import the workbook and write the changes back to the corresponding elements.

Supported Data

Categories: Columns, walls, beams, doors, and windows are explicitly listed.
Standard fields: Level, Mark, and Type can be included.
Custom parameters: Users can add selected project or shared parameters to the export.
Round-trip coordination: The tool is intended to maintain element correspondence so imported values return to the proper Revit objects.

This is a data-exchange feature, not unrestricted spreadsheet synchronization. Before use, teams should test how the add-in identifies elements, handles deleted or duplicated rows, validates data types, treats read-only, type, and instance parameters, and reports failed imports.

Project Setup and Office Standards

The developer site describes a Project Setup feature that reads a completed office reference project and recreates its production structure in a new job. The stated workflow learns the office’s view series, view templates, browser folders, and sheet organization, then builds structural views and sheets for each floor.

Advertised Functions

View generation: Create recurring structural view sets such as slab plans, top-reinforcement plans, bottom-reinforcement plans, and sections.
Sheet creation and placement: Establish sheets and organize generated views according to the reference project.
Template reuse: Transfer or apply established view templates.
Browser organization: Reproduce office project-browser folder logic.
Existing-view option: Developer posts state that, if views already exist, the tool can focus on arranging sheets to match the reference.
Tag-family transfer: Developer material also describes transferring loaded tag families rather than loading them individually.
Saved settings: Project-setup preferences can reportedly be reused and restored after a new architectural link is loaded.

Project Setup has potentially broad model impact because it can create and organize many views and sheets. Confirm that it is included in the installed version and test naming collisions, duplicate views, template dependencies, browser parameters, title blocks, sheet numbers, crop settings, and linked-model behavior before production use.

FastVoid and Planned Pile Layout

FastVoid

The developer describes FastVoid as a tool for quickly creating recesses or openings inside a structural member on a user-selected face, including recesses in structural columns. Its role is to reduce manual void-family placement and improve opening coordination. However, the developer site contains mixed status language: FastVoid is listed among trial features while another section labels it in development. Its installed availability, supported hosts, family behavior, and limitations should be verified directly.

Automated Pile Layout

An automated pile-layout tool is presented as a future capability that would use soil-report information and basement-slab geometry to develop a pile plan. The website explicitly describes this feature as in development. It should not be included in current purchasing or deployment decisions until it appears in released documentation and can be tested in Revit.

Compatibility, Pricing, and Access

Supported Revit releases: Revit 2024, 2025, 2026, and 2027.
Operating system: 64-bit Windows 10 and Windows 11.
Current version: The developer website identifies version 1.3.1 as live on Autodesk Marketplace.
Trial: A 30-day trial is available through Autodesk Marketplace, with all included features unlocked during the trial.
Subscription: Published pricing is US$8 per month or US$79 per year. Taxes, regional pricing, renewal terms, and future changes should be confirmed at purchase.
Entitlement: Access is managed through the user’s Autodesk account and the Autodesk Entitlement API.
Distribution: The add-in is obtained through Autodesk Marketplace.
Publisher focus: The publisher describes its work as Revit API development and structural workflow automation.

Practical BIM and Structural-Engineering Assessment

Where It Adds Value

Large vertical structures: Multi-level towers and repetitive framed buildings benefit from consistent column numbering across floors.
Foundation coordination: Column-derived pile and cap marks make it easier to trace load-path relationships between plans and schedules.
Reduced transcription: Automatic marks and round-trip Excel exchange reduce repeated manual entry and the associated risk of skipped or duplicated values.
Office-standard deployment: Project Setup could shorten the effort required to recreate view, template, browser, and sheet conventions in each new project.
External coordination: XLSX exchange provides a familiar format for reviewers or analysis workflows that do not operate directly in Revit.
Incremental adoption: Numbering and Excel tools can be piloted independently before broader model-setup or opening-generation functions are introduced.

Best-Fit Users and Projects

ELLAH-M is best suited to structural engineers, Revit modelers, BIM coordinators, and drawing-production teams working on multistory buildings, piled foundations, or office-standardized structural documentation. Its value will be highest where marks drive plans, schedules, details, or downstream coordination. Projects with small element counts or unconventional identification systems may see less benefit.

Limitations and Governance Considerations

Feature descriptions are evolving: The Marketplace listing and developer website do not present an identical scope. Confirm released versus preview functionality in the specific installed build.
Numbering logic must match the standard: Sorting and vertical-continuity rules should be tested against grids, offsets, slanted columns, split columns, transfers, design options, and phased elements.
Marks have downstream consequences: Changes can affect tags, schedules, drawing references, exports, fabrication identifiers, and coordination records.
Existing values require protection: Although the Marketplace states that intentional marks can be preserved, teams should test duplicates, blanks, locked conventions, manual exceptions, and restart behavior.
Foundation relationships can be ambiguous: Multi-column caps, eccentric supports, battered piles, linked geometry, shared foundations, and nonstandard families may challenge automatic association.
Excel round trips require controls: Unvalidated worksheets can introduce incorrect units, invalid values, duplicate marks, type/instance conflicts, or edits to parameters that should be governed in Revit.
Project Setup can create broad changes: View, template, sheet, and browser automation should be tested on a copy and reviewed for duplicate names, dependencies, and office-specific parameters.
FastVoid is not code coordination: Creating a recess does not confirm structural adequacy, reinforcement clearance, fire protection, clash resolution, or approval by the responsible engineer.
Cloud entitlement dependency: Autodesk-account validation means activation and continued access may depend on sign-in, Marketplace entitlement, and network availability.
Limited independent evidence: The product is new, with little independent technical review. Most detailed claims originate from the publisher.

Recommended Evaluation Before Production Deployment

Confirm the installed version, exact included features, supported Revit build, pricing, renewal terms, and Autodesk-account requirements.
Use a detached or copied model containing representative structural columns, levels, grids, piles, pile caps, walls, beams, doors, windows, phases, groups, and design options.
Test full-project, floor, range, manual, and Snake Path numbering; compare the resulting sequence with the firm’s written convention.
Verify behavior for existing marks, skipped numbers, duplicates, stacked columns, transferred columns, and vertically misaligned members.
Test pile and cap numbering on single piles, grouped piles, multi-column caps, custom families, and bilingual family names.
Export each supported category to Excel with standard and custom parameters; edit a controlled sample and verify exact round-trip element matching.
Test malformed, reordered, filtered, duplicated, and partially deleted spreadsheet rows to understand import validation and error reporting.
If Project Setup is present, run it in a blank test project and audit created views, view templates, browser folders, sheets, numbers, title blocks, and tag families.
If FastVoid is present, test supported hosts, faces, rotations, depths, family behavior, structural warnings, and changes to the host element.
Measure time saved, correction effort, model warnings, audit findings, and user training needs against the current manual process.
Define permissions, backups, review ownership, and approval rules before writing bulk marks or importing spreadsheet changes into a central model.
Document which features are approved for production and which remain pilot-only or unavailable.

Sources Consulted

Autodesk Marketplace — “ELLAH-M”
ELLAH-M — “Structural Tools for Revit”
Developer announcement — Snake Path and upcoming tools
ELLAH-M — Excel import/export demonstration
ELLAH-M — floor-range numbering demonstration

Source-quality note: Autodesk Marketplace is the primary source for the released core feature set, compatibility, trial, and subscription model. The developer website and demonstrations provide additional workflow details and roadmap information. Where those sources differ on release status, this summary identifies the uncertainty rather than treating previewed functionality as definitively available.

SPECIFIC FLOOR 3

SPECIFIC FLOOR 2

SPECIFIC FLOOR 1

PILE NUMBERING

EXCEL EXPORT 2

EXCEL EXPORT

HOME PAGE

FEATURES

ELLAH-M is brought to you by ELLAH-M. It's priced at $8/month or $79/year. A 30-day free trial is available.

This add-in is compatible with Revit 2024-2027.

There's more information available on the Autodesk Design and Make Marketplace »

Questions? Contact the developer »

Product Roundup: DesignLab

2026-10-01T17:26:00.000-07:00

From the Autodesk Design and Make Marketplace:

About

Professional Revit plugins for architects, BIM engineers, and designers.

Products by DesignLab

Editor's Note: Ratings are static and accurate at press time. For up-to-date ratings, please visit the Autodesk Design and Make Marketplace.

AutoJoin Manager

Join and unjoin Autodesk® Revit® elements across multiple categories in a user-defined priority order. | $15

No ratings yet

Beam Finish Generator

Automatically generate finish walls and ceilings around structural beams in Autodesk® Revit® — select beams, choose a type, and create all finish elements in one click. | $15

No ratings yet

Beam Finish Generator: Automatically Create Finish Walls and Ceilings Around Structural Beams

2026-09-29T17:56:00.000-07:00

Executive Overview

Beam Finish Generator is a focused Revit productivity add-in developed by DesignLab for automatically creating finish walls and ceilings around structural beams. Its purpose is to eliminate the repetitive process of modeling beam encasement or finish surfaces one beam at a time. The user selects one or more structural beams, chooses an existing Revit wall or ceiling type, and runs one of two commands: Side Walls or Lower Ceiling.

The add-in creates native Revit wall and ceiling elements rather than symbolic graphics. Because the results use project types already available in the model, they can participate in normal documentation, scheduling, material definition, visibility control, and downstream editing. The tool is best understood as a geometry-generation utility: it accelerates finish creation around modeled beams, but it does not design assemblies, determine required fire protection, or verify constructability.

Core Commands and Workflow

Side Walls

The Side Walls command generates four finish walls for each selected structural beam: two walls along the beam’s long sides and two walls closing the ends. The generated walls are offset by half the selected wall type’s thickness so their finish faces align around the beam rather than placing their centerlines directly on its edges. Vertically, the walls are aligned to the beam’s bottom face.

A typical workflow is to select any number of beams, launch Side Walls from the dedicated Beam Finish ribbon tab, choose a wall type available in the active project, and confirm the operation. The add-in then creates the finish walls for every selected beam in one batch. This can replace four manual wall placements—and their associated offsets and height adjustments—for each beam.

Lower Ceiling

The Lower Ceiling command creates one ceiling beneath each selected beam. The ceiling footprint is generated to match the beam’s plan footprint, and its elevation is aligned with the beam’s bottom face. The user selects the beams, chooses an existing project ceiling type, and runs the command for the complete selection.

The command is intended for soffit-like or encasement conditions where the underside finish follows the beam footprint. It can be used independently from Side Walls, allowing a team to generate only vertical finish faces, only the lower horizontal finish, or both.

Generated Model Content and Expected Behavior

Native Revit elements: Output consists of standard walls and ceilings created from types already loaded in the project.
Batch creation: Both commands accept multiple selected beams, making the workflow suitable for an entire bay, floor, or larger model area instead of beam-by-beam execution.
Beam-driven geometry: Wall placement and ceiling footprint are derived from each structural beam’s geometry and bottom elevation.
Type flexibility: The Marketplace listing states that the commands work with any wall type or ceiling type available in the project. The selected type therefore controls thickness, material layers, and other type-based properties.
Independent commands: Side walls and lower ceilings are created separately, giving the user control over which faces of the beam receive finish geometry.
Downstream editability: Once generated, the walls and ceilings can be edited using ordinary Revit tools, subject to the constraints and behavior of those native categories.

Typical Production Workflow

Prepare the structural model. Confirm that the beams to be finished are correctly placed, sized, oriented, and associated with the intended level.
Load or verify finish types. Ensure the required wall and ceiling types already exist and represent the approved assembly, material, thickness, naming, and graphic standards.
Select the beams. Choose one beam or a larger set. Selection quality determines the processing scope.
Create vertical finishes. Run Side Walls and choose the appropriate wall type.
Create underside finishes. Run Lower Ceiling and choose the appropriate ceiling type when a bottom finish is required.
Review the generated geometry. Inspect ends, intersections, offsets, levels, slopes, joins, duplicate conditions, and relationships with nearby walls, ceilings, columns, ducts, pipes, and architectural finishes.
Integrate with documentation. Apply project-standard parameters, room-bounding decisions, filters, material tags, schedules, details, and view controls as needed.

Practical BIM Assessment

Where It Adds Value

Repetitive finish modeling: The largest benefit appears where many exposed or partially enclosed beams require the same finish treatment.
Soffit and encasement creation: The commands establish a fast starting point for gypsum board, plaster, cladding, or other modeled finish assemblies around beams.
Consistency: Automated offsets and alignment reduce variability introduced when different users model the same condition manually.
Design changes: The tool can quickly regenerate finishes after beams are added or after a selected finish type changes, although previously generated elements must still be managed carefully.
Documentation readiness: Native walls and ceilings can appear in plans, sections, elevations, details, schedules, and material takeoffs using standard Revit behavior.
Low-cost specialization: The published permanent license is inexpensive compared with the accumulated labor of manually finishing a large beam population.

Best-Fit Users and Projects

The add-in is most relevant to architects, interior designers, BIM modelers, coordinators, and design-technology teams responsible for architectural finishes around structural framing. It is likely to provide the greatest value on projects with many consistent dropped beams or beam enclosures, including multifamily, hospitality, healthcare, institutional, commercial, and interior-fit-out work. Projects with only a few beams, highly irregular finish profiles, or predominantly exposed structure may gain less.

Limitations and Quality-Control Considerations

Finish design is not automated: The user remains responsible for selecting an appropriate wall or ceiling type and confirming its material, thickness, fire rating, acoustic performance, and specification.
Rectangular enclosure assumption: The stated four-wall and footprint-based workflows are best suited to beam geometries that can be represented by straight side and end walls with a ceiling beneath. Public documentation does not describe special handling for curved, tapered, haunched, castellated, or complex custom framing.
Sloped and rotated beams require testing: The Marketplace description does not explicitly document behavior for sloped beams, beams rotated about their axis, or members with nonhorizontal bottom faces.
Intersections require review: Closely spaced beams, beam-to-column conditions, beam crossings, walls meeting the enclosure, and adjacent ceilings may create overlaps, gaps, or duplicate finish elements that require cleanup.
End conditions may vary: The command creates two end walls per beam. Continuous beams, beams framing into other construction, or finishes intended to stop at a wall may require trimming, deletion, joining, or modified profiles.
Native-category consequences: Generated walls and ceilings can affect room bounding, quantities, material takeoffs, interference checks, view graphics, joins, and model performance.
Duplicate-run risk: Re-running a generation command after finishes already exist may create duplicate geometry unless the user removes or accounts for earlier output. Public documentation does not state that existing finishes are automatically detected.
Host and constraint behavior: Teams should verify levels, offsets, constraints, worksets, phases, design options, and behavior when the source beam moves or changes size; public descriptions do not claim an ongoing associative link.
Linked structural models: The advertised workflow refers to selected structural beams, but current public material does not confirm whether beams in linked Revit models can be processed.
Limited independent evidence: Available technical information is primarily the publisher’s Marketplace listing and demonstration video. The listing currently states that there are no known issues, but that is not a substitute for project-specific testing.

Compatibility, Licensing, and Deployment

Publisher: DesignLab, which describes its portfolio as professional Revit plugins for architects, BIM engineers, designers, structural engineers, and MEP professionals.
Supported Revit releases: Autodesk Marketplace currently lists Revit 2021, 2022, 2023, 2024, 2025, 2026, and 2027.
Trial: A seven-day, fully functional trial is offered without a credit card.
License: The published price is US$15 for a permanent per-machine license, with no subscription or recurring fee. License keys are generated for the machine and delivered by email, reportedly within 24 hours of purchase.
Connectivity: The add-in is described as fully offline, including installation, operation, and license activation.
Installer: Autodesk Marketplace notes that the app uses a custom installer rather than the standard Marketplace installer.
Support: The Marketplace directs users to contact the publisher by email for technical support and license activation.
Commercial caution: Pricing, supported versions, fulfillment times, transfer rights, refund terms, and update eligibility can change and should be confirmed before purchasing or standardizing deployment.

Recommended Evaluation Before Production Deployment

Confirm the current installer, supported Revit build, machine-license terms, license-transfer process, trial period, and update policy with DesignLab.
Install the trial in a controlled environment and verify code signing, antivirus behavior, administrator requirements, and enterprise deployment compatibility.
Create a test model containing beams of different widths, depths, lengths, rotations, elevations, slopes, materials, families, and framing orientations.
Test Side Walls with thin and thick finish types, compound structures, wrapping settings, room-bounding behavior, and expected wall location lines.
Test Lower Ceiling with several ceiling types and verify footprint, elevation, thickness direction, material display, and schedule values.
Check continuous beams, beam ends at columns and walls, intersecting beams, beams near slabs or ceilings, and adjacent enclosures for overlaps and gaps.
Run both commands on a large multiselection and measure creation time, warning count, model-size change, and editing responsiveness.
Move, resize, rotate, or delete source beams after generation to determine whether finishes update, remain independent, or require regeneration.
Run the commands twice on the same beams to test duplicate prevention and establish a safe rerun procedure.
Verify behavior in workshared models, groups, design options, phases, linked-model conditions, and projects using shared coordinates.
Review generated walls and ceilings in plans, sections, elevations, reflected ceiling plans, schedules, material takeoffs, interference checks, and exports.
Document approved finish types, selection rules, cleanup steps, QA responsibility, and rollback procedures before firmwide use.

Sources Consulted

Autodesk Marketplace — “Beam Finish Generator” by DesignLab
DesignLab — “Beam Finish Generator — Automate Finish Walls & Ceilings Around Beams in Revit” demonstration
Autodesk Marketplace — DesignLab publisher profile

Source-quality note: The product is new and the available evidence is concentrated in DesignLab’s Marketplace listing and tutorial. No substantial independent technical review or long-term user-rating base was found, so workflow claims should be validated through the free trial before production adoption.

Beam Finish Generator is brought to you by DesignLab. It's priced at $15 for a permanent, per-machine license. A 7-day free trial is available.

This add-in is compatible with Revit 2021-2027.

There's more information available on the Autodesk Design and Make Marketplace »

Questions? Contact the developer »

AutoJoin Manager: Automates Revit’s Join Geometry and Unjoin Geometry Workflows

2026-09-28T17:42:00.000-07:00

Executive Overview

AutoJoin Manager is a professional productivity add-in developed by DesignLab for Autodesk Revit. It automates Revit’s Join Geometry and Unjoin Geometry workflows across multiple element categories and gives users explicit control over cutting priority. Instead of joining intersecting elements one pair at a time—and then correcting join order where the wrong element cuts—the user creates an ordered list of categories, optionally narrows each category to chosen element types, and runs the operation across the model in one batch.

The add-in is primarily a model-cleanup and standards-enforcement utility. It is intended for architectural and structural teams that repeatedly coordinate walls, floors, columns, framing, ceilings, foundations, and other joinable categories. Its main advantage is not merely speed; it makes join precedence repeatable. A saved rule set can express a firm or project convention for which categories should cut others, reducing inconsistent results created by manual selection order.

How the Workflow Operates

Build the category list. Add the Revit categories that should participate in the operation. Published examples include structural columns, structural framing, walls, floors, ceilings, foundations, and other categories that Revit permits to be joined.
Set the cutting hierarchy. Arrange the categories in priority order. The category in the first row has the highest priority and is intended to act as the cutting element when it is joined to categories listed below it.
Refine by type when necessary. Any category row can be restricted to selected element types rather than applying to every type in that category. This allows different treatment for items such as particular wall, floor, framing, or column types.
Run Join or Unjoin. One command processes the configured categories in batch rather than requiring individual element-pair selections.
Monitor progress. A progress window reports processing status and percentage completion while Revit evaluates the model.
Review the outcome. A results report separates successful operations, skipped pairs, and failures, including reasons where available.
Reuse the setup. The priority list is automatically retained between sessions, avoiding repeated configuration when Revit or a project is reopened.

Core Capabilities

Priority-Controlled Join Geometry

Revit’s native join result can depend on the category combination and join order. AutoJoin Manager formalizes that behavior through an ordered hierarchy. If a project standard requires structural framing to cut walls, or columns to take precedence over floors, the hierarchy provides a repeatable rule rather than relying on each modeler to select the correct element first.

Batch Unjoin

The same category-and-type framework can be used to remove existing joins in bulk. This is useful before rebuilding relationships under a revised hierarchy, correcting legacy models with inconsistent joins, or preparing a controlled model-cleanup sequence.

Optional Type Filtering

Type filtering limits a category rule to specified Revit types. This is important where a broad category contains elements that should behave differently—for example, where only selected wall constructions, floor assemblies, or framing types should participate.

Large-Scale Processing

The Marketplace description positions the add-in for hundreds or thousands of element pairs. Revit processes the relationships in batches while the plugin reports progress. Actual duration will depend on model size, geometric complexity, category count, type filters, and the number of intersecting or nearby candidates.

Persistent Configuration

Settings are remembered between sessions. This supports repeatable execution but also creates a governance requirement: teams should confirm that the stored hierarchy is appropriate for the current project before running it.

Progress Tracking and Results Reporting

Real-time status: The processing window displays an accurate percentage indicator so users can follow long-running operations.
Successful joins or unjoins: Completed relationships are counted and summarized.
Skipped element pairs: Pairs that are too far apart or otherwise do not qualify are reported rather than silently presented as successful.
Failed operations: Errors are identified with the available reason, helping users isolate problematic geometry or unsupported relationships.
Operational transparency: The report provides a review point after bulk modification, which is essential because a large join operation may change many view graphics, material intersections, quantities, and model relationships at once.

The report should be treated as the beginning of QA rather than proof that every resulting join is correct. A technically successful join may still conflict with design intent, detailing standards, quantity requirements, or downstream model uses.

Deployment

Operating model: The add-in is described as fully offline; no Internet connection is required during use or activation.
Configuration persistence: Priority settings remain available across sessions on the machine, supporting repeatability but requiring local standards control.
Network and privacy implications: Offline operation reduces reliance on cloud availability and limits routine transmission of project geometry.

Practical BIM Assessment

Where It Adds Value

Model cleanup: Quickly standardizes large numbers of geometric joins that would otherwise require repetitive pair-by-pair work.
Consistent cutting precedence: Converts an informal modeling convention into an explicit category hierarchy.
Architectural–structural coordination: Helps regularize interfaces among walls, floors, columns, beams, foundations, and ceilings after coordination changes.
View and material cleanup: Correct joins can improve displayed intersections, remove unwanted lines, and produce cleaner sections, elevations, and details.
Quantity and layer behavior: Join order can affect how overlapping geometry is resolved. A controlled process can reduce arbitrary results, provided quantities are checked afterward.
Legacy-model remediation: Batch unjoin followed by a controlled rejoin can be useful when inherited models contain inconsistent or incorrectly ordered relationships.
Standards-driven workflows: Type-level filters provide more precision than category-only automation and can support project-specific exceptions.

Best-Fit Users and Projects

The add-in is most relevant to BIM coordinators, architects, structural modelers, VDC teams, and model-health specialists working with join-intensive Revit projects. Large concrete, steel, institutional, healthcare, commercial, and multidiscipline models are likely to see the greatest time savings. Small models with few intersections may not justify a model-wide operation.

Limitations and Governance Considerations

Joinability remains governed by Revit: The add-in automates native join and unjoin operations; it cannot create a valid relationship where Revit does not support the category pair or geometry condition.
Geometric proximity is not design intent: Intersecting elements are candidates for joining, but not every intersection should be joined. Movement joints, finish layers, embeds, openings, stacked assemblies, phasing conditions, and discipline ownership may require exceptions.
Cutting priority requires careful definition: A hierarchy that works for one project, material system, or level of development may be inappropriate elsewhere. The top-listed category should not automatically be assumed to cut every lower category.
Model-wide operations can affect performance: Evaluating large numbers of element pairs and creating many join relationships may increase processing, regeneration, opening, synchronization, or editing time.
Downstream effects require review: Joins can change visible edges, wall and floor cleanup, hosted-element behavior, material takeoffs, calculated quantities, analytical interpretation, and exported geometry.
Worksharing risk: Bulk changes may require ownership of many elements. Run the tool in a controlled worksharing state and coordinate with other users before synchronization.
Groups, design options, phases, links, and special elements: Public descriptions do not fully document behavior for every Revit context. These conditions should be tested rather than assumed.
Limited independent evidence: Public information is dominated by the publisher’s Marketplace description and demonstration.
No substitute for clash detection: Automating joins does not identify all spatial conflicts, coordinate linked disciplines, or replace formal interference-checking and issue-management workflows.

Recommended Evaluation Before Production Deployment

Confirm the current installer, supported Revit build, license scope, machine-transfer policy, refund terms, and update process with DesignLab.
Install the trial in a controlled test environment and verify compatibility with enterprise security, antivirus, and software-deployment standards.
Use a detached or copied model containing representative walls, floors, columns, beams, ceilings, foundations, groups, phases, design options, and worksets.
Document the intended hierarchy in plain language before configuring it—for example, which structural and architectural categories should cut others and where exceptions apply.
Test category-only rules first, then apply type filters to isolate assemblies that require different behavior.
Run Join on a limited scope and inspect plans, sections, elevations, details, material boundaries, hosted elements, and quantities.
Compare successful, skipped, and failed report entries with a manual sample to confirm that the result categories are understood.
Test Unjoin and rejoin sequences to determine whether the tool restores the intended priority without creating new graphical or data issues.
Measure processing time, model-size change, regeneration time, synchronization time, and editing responsiveness before and after a large run.
Test worksharing ownership and synchronization behavior with more than one user in a nonproduction environment.
Establish exclusions for elements, types, phases, design options, or worksets that should never be processed automatically.
Require model review and backup or version control before committing bulk geometry changes to a production central model.

Sources Consulted

Autodesk Marketplace — “AutoJoin Manager” by DesignLab
DesignLab — “AutoJoin Manager — Automate Join & Unjoin in Revit with Priority Control” tutorial

AutoJoin Manager is brought to you by DesignLab. It's priced at $15 for a permanent, per-machine license. A 7-day free trial is available.

This add-in is compatible with Revit 2022-2027.

There's more information available on the Autodesk Design and Make Marketplace »

Questions? Contact the developer »

BIM-IT Pipe: Practical Automation for Piping Workflows

2026-09-27T13:32:00.000-07:00

Executive Overview

BIM-IT Pipe is a specialized Autodesk Revit add-in developed by BIM-IT for plumbing and piping modelers, MEP engineers, BIM technicians, and coordinators. Rather than attempting full system design or automated routing, it concentrates on recurring production tasks that routinely consume time in detailed modeling and shop-drawing workflows: tagging pipe banks, matching elevations, maintaining spacing and clearance, splitting branches, aligning sections, isolating systems, and applying or displaying insulation. The tools operate on native Revit pipes, annotations, views, and insulation, so their results remain part of the model and documentation set.

The product’s core value proposition is practical automation. Each command addresses a narrow operation that can otherwise require repeated selection, measurement, movement, alignment, visibility adjustment, or annotation cleanup. This makes the add-in most relevant after basic systems and routes have been established, when a team is refining geometry, coordinating congested pipe runs, and preparing readable plans and sections.

Annotation and Documentation Tools

Pipe Size Tag

Adds a pipe-size tag above a selected spot elevation in the current view. The user chooses the pipe-tag type and can adjust offsets. Placement is calculated from the spot-elevation text position, reducing manual alignment. Developer guidance states that the spot-elevation text should be horizontal and its text location set in line with the leader. If the selected tag family wraps its label onto two lines, the computed label height can create excessive spacing; enlarging the label in the tag family and reloading it is the recommended correction.

Tag Pipe Bank

Adds size tags for multiple pipes associated with a selected spot elevation. Tags are stacked vertically in the order the pipes are selected, with configurable offsets and a reverse-order option. This is especially useful for congested parallel services where conventional individual tagging takes time and produces inconsistent arrangement.

Align Section

Aligns a section view to a selected pipe or model line and centers the section on that reference. The command helps a modeler orient working sections to sloped, angled, or otherwise inconvenient pipe runs before making detailed adjustments or preparing shop drawings.

Pipe Layout and Modification Tools

Align Pipe Elevation

Matches the elevation of multiple selected pipes to the first pipe in the selection. Alignment can use centerline, top, or bottom elevation, allowing differently sized pipes to be coordinated against the appropriate datum. The developer notes that affected pipes inherit the reference level of the base pipe and that the command does not operate on sloped pipes.

Align Branch

Aligns a branch pipe with a main pipe while preserving the branch slope. Its purpose is to produce a clean Revit connection without the fitting errors that can occur when a sloped branch is adjusted manually.

Evenly Distribute

Repositions selected pipes at a user-defined, equal centerline spacing while holding the first selected pipe fixed. It is appropriate when the requirement is a regular pipe-bank layout rather than a specific clear dimension between outside surfaces.

Pipe Clearance

Moves selected pipes to maintain a required clear distance between their outside surfaces, including insulation when present. The user can specify a default spacing or apply rules based on pipe diameter and insulation thickness. This differs materially from Evenly Distribute: it focuses on physical clearance rather than uniform centerline spacing, making it more useful for coordination, access, and fabrication planning.

Split Pipe Branch

Splits multiple pipes in one operation using either a picked point or a reference line. Published options include perpendicular, vertical, horizontal, and custom split directions. This can accelerate branch preparation, connection work, and coordinated breaks across a bank of pipes.

System Visibility and Insulation Tools

Isolate by System Type

Temporarily isolates pipe runs according to the system types represented by selected reference pipes. This gives a focused view of the systems under review and can simplify coordination in dense models.

Reset Pipe Isolation

Restores the pipe visibility affected by the system-type isolation command, providing a direct way to return to the full view after focused inspection.

Insulation by Size & Type

Applies pipe insulation using user-defined rules based on pipe size and system type. The command includes a detailed status report showing how each rule was applied. This can improve consistency compared with selecting runs and assigning insulation manually, particularly where a project has several systems and thickness requirements.

Toggle Insulation Visibility

Turns pipe-insulation visibility on or off in relation to the active view settings. It is useful when switching between model review, coordination, and documentation views where insulation graphics may either clarify actual clearance or obscure underlying pipe geometry.

Installation and Licensing

Distribution: BIM-IT Pipe is available through Autodesk Marketplace and through the developer’s website.
Installation: Developer instructions direct users to download and run the BIM_IT_Pipe.msi package. On first launch after installation, Revit may display a security prompt; the documented workflow is to choose Always Load.
Activation: The installed application accepts a serial number or can continue in trial mode.
License model: BIM-IT’s terms describe time-limited trials and monthly or annual subscription products. The license is nonexclusive, nontransferable, and restricted to the purchased subscription or trial conditions.
Online validation: The EULA states that activation and periodic license validation may use third-party licensing services.

Practical BIM and MEP Assessment

Where It Adds Value

Detailed plumbing production: Strongest fit for teams developing coordinated plumbing models and installation or shop-drawing documentation.
Repeated geometry edits: Alignment, spacing, clearance, and splitting tools reduce the error risk and selection burden associated with repetitive manual operations.
Annotation consistency: Pipe-bank tagging formalizes tag placement and order around spot elevations, improving drawing readability.
Coordination accuracy: Surface-to-surface clearance that accounts for insulation is more meaningful than centerline spacing when testing realistic installation envelopes.
View preparation: Section alignment and system isolation shorten the path from model navigation to focused editing and review.
Standards enforcement: Rule-based insulation can help standardize how systems are treated, provided project criteria are configured and reviewed correctly.
Incremental adoption: Because the commands are discrete utilities rather than a replacement design platform, teams can introduce them individually within existing Revit standards.

Best-Fit Users and Projects

The add-in is best suited to plumbing designers, MEP modelers, BIM coordinators, and piping-detailing teams handling repetitive parallel runs, branch connections, insulated services, and dense documentation. Its benefit is likely greatest on healthcare, laboratory, residential, hospitality, institutional, or contractor-led coordination projects with substantial piping content. Simpler projects may use only a subset of the tools.

Limitations and Implementation Considerations

Not an engineering-design engine: Published features focus on modeling and documentation productivity; the add-in does not claim to perform hydraulic sizing, code analysis, automated routing, clash detection, or fabrication spooling.
Selection order matters: Several commands rely on the first selected pipe as the fixed or reference element, and pipe-bank tag order follows selection order unless reversed. Users need a consistent selection procedure.
Sloped-pipe exception: Align Pipe Elevation is documented as unavailable for sloped pipes. Align Branch is the purpose-built alternative for preserving branch slope.
Tag-family dependency: Automatic tag placement depends on the geometry and text behavior of office tag families. Wrapped labels may require family adjustment.
Model constraints remain active: Moving or splitting pipes can affect fittings, connections, slopes, reference levels, dimensions, constraints, and hosted annotations. Results should be inspected immediately.
Clearance is not code approval: A geometric clearance rule does not confirm accessibility, insulation specification, seismic restraint, firestopping, manufacturer requirements, or applicable plumbing and mechanical codes.
Insulation rules require governance: Criteria should be reconciled with the project specification, service temperatures, regional requirements, and approved pipe and insulation types.
Limited independent evidence: Most detailed information is supplied by BIM-IT or repeated from its Marketplace listing. The third-party review is favorable but not a substitute for project testing, and public long-term user feedback remains limited.
Custom installer and license validation: Enterprise teams should evaluate software signing, administrator rights, deployment packaging, update control, firewall requirements, privacy terms, and license-server behavior.

Recommended Evaluation Before Production Deployment

Confirm the current installer, supported Revit builds, subscription price, trial limitations, activation count, and update policy with BIM-IT.
Install the add-in in a controlled test environment and verify compatibility with the firm’s security and deployment standards.
Use a copied project containing horizontal, vertical, sloped, insulated, connected, pinned, grouped, and workshared pipe examples.
Test Pipe Size Tag and Tag Pipe Bank with every approved tag family, text orientation, leader configuration, scale, and expected label length.
Verify Align Pipe Elevation against centerline, top, and bottom criteria for mixed pipe sizes; confirm reference-level changes and connected-fitting behavior.
Test Align Branch on representative slopes and fitting configurations, checking that slope, connectivity, and intended flow geometry are preserved.
Compare Evenly Distribute with Pipe Clearance on mixed diameters and insulation thicknesses; measure final centerline and surface-to-surface spacing.
Test Split Pipe Branch in each published direction and inspect unions, fittings, open connectors, system continuity, and downstream fabrication requirements.
Validate isolation and reset behavior in views with templates, filters, linked models, phases, design options, and existing temporary hide/isolate settings.
Configure insulation rules from approved specifications, then audit the application report and spot-check resulting types and thicknesses.
Measure time saved and correction effort against the standard manual process before approving wider deployment.
Document command-specific usage rules, rollback expectations, and QA ownership in the firm’s Revit add-in standard.

Sources Consulted

Autodesk Marketplace — “BIM-IT Pipe”
BIM-IT — “BIM-IT Pipe – Revit Add-in for Faster Plumbing Modeling”
BIM-IT — installation and tool help documentation
BIM-IT Pipe Tools — developer demonstration playlist
BIM-IT — End User License Agreement
BIM-IT — Terms of Service
RVT Plugins — “BIM-IT Pipe: Streamlining MEP Workflows in Revit”

BIM-IT Pipe Toolbar

Pipe Size Tag tool adds a pipe size tag
above each spot elevation in the current view.

Tag Pipe Bank tool adds size tags for all pipes
in a pipe bank above the selected spot elevation.

Align Pipe Elevation

Align Branch tool quickly aligns a branch pipe
with the main pipe while preserving its slope.

Evenly Distribute

Pipe Clearance

Split multiple pipes at once in Revit, quickly and precisely.

Align Section tool aligns the section view to
a selected pipe or line, centering it on the object.

Isolate By System Type tool isolates pipe
runs based on selected system types.

Reset Pipe Isolation tool - This tool reverses
the effect of Isolate By System Type.

Apply different insulation based on pipe size
and system type in Revit — automatically.

Toggle Insulation Visibility tool switches pipe insulation
visibility on/off based on your current view settings.

BIM-IT Pipe is brought to you by BIM-IT. It's priced at $10/month or $100/year. A free trial is available.

This add-in is compatible with Revit 2027, 2026, 2025, 2024, and 2023.

There's more information available on the Autodesk Design and Make Marketplace »

Questions? Contact the developer »

Electrical Panels Manager

2026-09-26T11:59:00.000-07:00

Executive Overview

Electrical Panels Manager (EPM), published by BIM_OS, is an add-in for Autodesk Revit aimed at electrical engineers, BIM engineers, coordinators, and model authors. It centralizes electrical-panel data editing, automates recurring panel naming and rating tasks, sizes feeder cables using IEC-based methods, performs voltage-drop and short-circuit studies, and exports engineering reports without requiring the user to leave Revit. The add-in is designed to replace repetitive schedule reading and parameter entry with a single interface that reads model data, calculates results, and writes approved values back to Revit.

Panel Discovery and Data Management

Automatic panel discovery: Current product descriptions state that EPM can detect panels in the active 2D or 3D view and can switch to whole-project scanning, reducing the need for manual selection.
Centralized property editing: The interface exposes critical properties such as panel name, location, mains or bus rating, circuit-breaker rating, short-circuit rating, enclosure type, number of slots or maximum breakers, and comments.
Direct model updates: EPM reads Revit’s electrical parameters and writes edits back to the panel elements in a single transaction.
Batch processing: Multi-panel selection supports consistent edits and calculations over several panels rather than one element at a time.
Panel visualization: A Show Panel function highlights or isolates the selected panel in an appropriate view, helping users locate equipment while reviewing tabular information.
Standardized naming: Auto-naming uses user-defined prefixes, reference codes, separators, start indices, and increments. Panels can be grouped by level, zone, or location reference to align identifiers with project conventions.

Automated Ratings and Connected-Load Workflow

The Auto Calculate or Auto Assign workflow reads connected loads from Revit and uses them to propose mains and circuit-breaker ratings. Marketplace material describes an 80% design-current rule associated with IEC 60364-4-43. This can accelerate initial sizing and improve consistency across a large panel population, but the quality of the result depends on accurate Revit circuiting, load classifications, demand assumptions, supply-system data, and parameter mapping. Calculated ratings should therefore be treated as engineering outputs requiring review rather than unquestioned metadata updates.

IEC Cable Sizing

Standard basis: The integrated cable sizer is described as selecting a minimum adequate copper XLPE conductor section under IEC 60364-5-52.
Design current: Selection considers the panel’s circuit-breaker rating and the published 80% loading rule.
Installation derating: Listed installation methods include enclosed or conduit method B1, clipped-direct method C, and underground method D.
Voltage-drop calculation: For three-phase circuits, the published formula is ΔV = √3 × I × L × (R·cosφ + X·sinφ), incorporating current, route length, conductor resistance and reactance, and power factor.
Operating resistance: Marketplace documentation states that conductor resistance is evaluated at a 90°C operating temperature using IEC 60228 data.
User constraint: The user can set the maximum acceptable voltage-drop percentage.
Parallel conductors: If one cable cannot satisfy the requirement, the tool can recommend parallel conductor sets.
Results stored in Revit: Cable size and route length are written to panel shared parameters identified by the publisher as Cable_Size_IEC and Cable_Length_m.

Voltage-Drop and Fault Study

The VD & Fault Study area performs an upstream impedance analysis described as following IEC 60909-0. Published outputs include the symmetrical initial short-circuit current Ik″, peak short-circuit current ip using the κ factor, equivalent thermal short-circuit current Ith for one second, and a breakdown of source, transformer, and cable impedance. The calculation applies the IEC voltage factor, with Marketplace material citing cmax = 1.05 for low-voltage breaker sizing. It also proposes a protection type and required breaking capacity with reference to IEC 60947-2 and IEC 60898.

Reporting and Deliverables

Excel panel schedule: EPM exports an XLSX workbook containing panel loads, calculated currents, circuit-breaker and mains ratings, cable sizes, voltage-drop results, and overload flags.
Project summary: A second worksheet provides project-level totals and statistics for broader review.
PDF panel report: A formatted panel-schedule report can be generated for coordination, submittal, or client review.
PDF engineering study: Voltage-drop and short-circuit results can be issued as a separate calculation report.
Earlier descriptions: Some third-party and historical materials mention CSV export. The current Marketplace listing emphasizes XLSX and PDF, so teams should verify the exact export set in the installed release.

Practical BIM and MEP Assessment

Where It Adds Value

Model-data consistency: Batch editing and rule-based naming reduce variation in panel identifiers and ratings across schedules and views.
Reduced repetitive work: Automatic discovery, connected-load reading, sizing, and export can replace substantial manual transcription.
Model-to-calculation continuity: Engineering inputs and outputs remain associated with Revit panel elements instead of being maintained only in detached spreadsheets.
Faster QA review: Whole-project scanning, overload flags, and direct panel highlighting provide useful checkpoints for electrical and BIM reviews.
Best-fit projects: IEC-based low-voltage projects with well-developed Revit electrical systems, reliable panel connectivity, and consistent data standards.
Best-fit users: Electrical designers and engineers, BIM coordinators, and model managers responsible for panel schedules, feeder sizing, naming standards, or calculation deliverables.

Limitations and Validation Requirements

IEC-centered methodology: The cited calculations reference IEC 60364, IEC 60228, IEC 60909, IEC 60947-2, and IEC 60898. Firms working under NEC, CEC, BS 7671 amendments, local utility rules, or authority-specific practices must verify suitability and may need a different workflow.
Not a substitute for professional judgment: Suggested ratings, conductor sizes, and fault duties require review by a qualified electrical engineer and coordination with protective-device data.
Input quality governs output quality: Incomplete circuits, incorrect system voltage, missing lengths, unreliable connected loads, inappropriate demand factors, or inconsistent family parameters can invalidate results.
Shared-parameter governance: Confirm parameter GUIDs, binding categories, naming conventions, schedules, templates, and downstream data exchanges before allowing the add-in to write values to production models.
Fault-study completeness: Validate source impedance, transformer impedance and vector assumptions, conductor material and temperature, X/R ratio, fault duration, earthing arrangement, and protective-device coordination against the project basis of design.
Transaction scope: Because edits can be performed in batches and written directly to model elements, teams should test on a copy, use worksharing controls, and review changed values before synchronization.
Evidence base: Independent test data and customer reviews are limited. Publisher claims should be confirmed through a controlled pilot using known hand calculations or an approved analysis package.

Recommended Evaluation Before Production Use

Confirm the supported Revit release, current EPM version, trial terms, and subscription entitlements.
Use a copied model containing representative distribution panels, panelboards, levels, locations, connected loads, schedules, and feeder lengths.
Map EPM fields to the firm’s built-in and shared parameters; document which fields the add-in reads and writes.
Compare auto-calculated mains and breaker ratings with independently checked engineering calculations.
Test cable sizing for each intended installation method, power factor, allowable voltage drop, conductor length, and parallel-set condition.
Benchmark IEC 60909 results against a validated calculation example or the firm’s approved electrical-analysis software.
Review auto-naming for uniqueness, level and zone behavior, leading zeros, reserved identifiers, and schedule sorting.
Test batch edits and exports in a workshared model, verifying permissions, transaction behavior, schedule updates, and retained parameter values.
Review XLSX and PDF outputs for units, rounding, assumptions, revision information, warnings, and suitability for formal submissions.
Define approval responsibilities so generated values are checked and signed off by the appropriate electrical professional before issue.

Sources Consulted

Autodesk Marketplace — “Electrical Panels Manager” by BIM_OS
Osman Mohamed / BIM Guru — “Electrical Panels Manager V1.1.0” developer demonstration
Osman Mohamed — version 1.1.0 release announcement
RVT Plugins — “Review: Electrical Panels Manager Plugin for Revit”

Choose the panel to edit its parameters.

You can use a dropdown menu or write the value.

Check the edited values in panel
schedules or from the properties panel.

Electrical Panels Manager is brought to you by BIM OS. It's priced at $5/month or $50/year. A free trial is available.

This add-in is compatible with Revit 2027, 2026, 2025, 2024, 2023, and 2022.

There's more information available on the Autodesk Design and Make Marketplace »

Questions? Contact the developer »

Free Bimroom: Thousands of High-Quality BIM Objects w/Seamless Drag-and-Drop Integration

2026-09-25T17:47:00.000-07:00

Overview

bimroom is a free Windows add-in from Bimform AG that embeds the bimroom cloud library inside Autodesk Revit. Its primary purpose is to reduce the time designers spend leaving Revit, searching manufacturer websites, downloading family files, organizing local folders, loading content, and later replacing temporary objects. Users can search, filter, preview, place, find, and replace BIM objects from within the Revit workflow. The library combines generic objects for early design with quality-controlled manufacturer objects for later specification, making the add-in both a content-delivery platform and an object-management utility.

Typical Revit Workflow

Open bimroom inside Revit. The integrated interface provides access to the online catalog without requiring a separate download-and-load sequence.
Search and refine. Locate content by keyword, then narrow results with filters and facets. Preview information before committing an object to the project.
Place content. Drag an object into the model; the add-in handles content delivery into Revit, avoiding manual file browsing and family loading.
Develop from generic to specified. Use uniform generic objects during concept and design development, then replace them with manufacturer-specific products when selections are made.
Manage existing instances. Use Find Similar to identify related content and Replace One or Replace Many to update selected or repeated objects across the project.

Library and Content Strategy

Broad catalog: bimroom promotes access to thousands of generic and manufacturer BIM objects spanning multiple building-product categories.
Uniform structure: The platform emphasizes consistent parameter naming and data formatting so objects are easier to search, compare, filter, schedule, and exchange.
Parametric behavior: Premium objects are described as fully parametric and dimensionally accurate, supporting adjustment within the limits built into each family.
Model efficiency: bimroom states that its content is modeled cleanly, without redundant geometry, to reduce unnecessary model weight and performance problems.
Product information: Objects are intended to include the data required for specification and project use, helping reduce later enrichment or placeholder replacement.
Continuously expanding content: New generic and manufacturer objects are added over time, so search results and product availability can change.

Key Revit Features

In-product search: Browse the bimroom catalog while remaining in Revit, with keyword search, filters, facets, and previews.
Drag-and-drop placement: Insert selected content directly into the active project rather than downloading an RFA file and navigating through Load Family manually.
Find Similar: Start from an existing object and locate comparable alternatives, useful when the design intent is known but the final product is not.
Replace One: Exchange a particular object for another catalog item with a streamlined replacement workflow.
Replace Many: Update repeated content across a project to improve consistency and accelerate transitions from generic to manufacturer-specific families.
Favorites and organization: Published product information describes saved preferred objects and project-oriented content organization as productivity features associated with higher service tiers.
Integrated properties: Object information can be reviewed as part of selection and specification, reducing dependence on disconnected websites and folder structures.

Practical BIM Assessment

Where It Adds Value

Reduced content-search friction: The largest efficiency gain is eliminating repeated transitions between Revit, browsers, download folders, and family-load dialogs.
Faster design progression: A generic-to-manufacturer replacement path supports early flexibility without requiring teams to remodel components when products are selected.
Improved repeatability: Uniformly structured content can reduce the parameter inconsistency commonly found in uncontrolled manufacturer-family downloads.
Project-wide substitutions: Replace-many functionality can save substantial time when standards, products, or selections change across numerous instances.
Best-fit users: Architects, interior designers, engineers, specifiers, BIM coordinators, and content managers who regularly source and maintain Revit families.
Best-fit projects: Projects that rely heavily on repeatable components and manufacturer selections, or teams without a mature internally curated family library.

Limitations and Governance Considerations

Cloud and account dependency: Integrated catalog access depends on the bimroom service, authentication, and internet availability.
Tier-dependent functionality: Download limits, premium families, team organization, and advanced tools may vary by plan; confirm entitlements before deployment.
Manufacturer content is not automatically office-standard content: Even quality-controlled families should be checked for category, hosting, origin, connectors, type catalogs, formulas, shared parameters, materials, subcategories, visibility settings, naming, file size, and level of detail.
Specification risk: A placed product family does not independently confirm regional availability, substitutions, code compliance, procurement status, warranty, or current technical data.
Model performance: Although bimroom emphasizes efficient geometry, teams should still test representative objects in large models and verify behavior at each required detail level.

Recommended Evaluation Before Firmwide Deployment

Install the current signed release in a test Revit environment.
Select a representative sample of generic and manufacturer objects from the categories the firm uses most.
Audit each family against office standards for naming, parameters, geometry, connectors, classification, scheduling, and file size.
Test search-to-placement time against the current content-library process.
Test Find Similar, Replace One, and Replace Many in a copied project, checking instance placement, hosted relationships, parameter retention, type mapping, and schedule results.
Confirm plan limits, user licensing, privacy terms, update behavior, support response, and deployment method with the publisher.
Approve vetted content through the firm’s normal library-governance process rather than treating all online content as preapproved.

Sources Consulted

Autodesk Marketplace — “bimroom” by Bimform AG
bimroom — “bimroom in Revit” integration overview
bimroom — BIM object library and product overview
bimroom — Premium plans and feature descriptions
RVT Plugins — bimroom add-in overview

Replace objects - Replace a BIM object
in your project with just a few clicks.

Find the right BIM object instantly - search by keyword
and refine results with powerful filters and facets.

Find similar - Pick an object in your project
to find similar BIM objects in the library.

Place objects - Place any BIM object
from the library directly into your project.

Bimroom is brought to you by Bimform AG. For users, it's free. For manufacturers, there are three tiers: Starter (free)—host up to 10 products, Build (€200/month)—host up to 50 products, and Pro (€600/month)—host unlimited products.

This add-in is compatible with Revit 2027, 2026, 2025, 2024, 2023, and 2022.

There's more information available on the Autodesk Design and Make Marketplace »

Questions? Contact the developer »

Got a Free Add-in? Get a Free Ad!

2026-09-25T12:41:54.995-07:00

Do you have a free add-in? Wouldn't you like to advertise it for free? On Revit Add-ons, publishers of free add-ins can get a free Saver Sidebar ad. Simply save your artwork in a 16:9 aspect ratio and email it to us, along with the web address you’d like it linked to. For image format, PNG is great for still images, GIF for animated.

Have multiple free add-ins? Send us artwork for each and we’ll set your ad space to rotate on page load. Or you could do something similar with an animated GIF.

Need professional artwork? We’ve got a great, inexpensive referral for you! Just ask...

It’s all a part of the service here at Revit Add-ons!