Free Ze’Diag: Revit Journal Analyzer

Overview

Ze’Diag is a free diagnostic tool from ZestineTech that explains why Revit crashed or misbehaved. Revit records every action, add-in call, and error in a session in a plain-text journal file. These files run to thousands of lines and are hard to read by hand. With Ze’Diag, you upload a journal and get back a structured, readable report. The report covers whether Revit crashed, the likely root cause, the errors and warnings raised, links that failed to load, where time was lost, and which add-ins may have been involved. It also links to known Autodesk solutions where they apply. The report can be downloaded as a PDF to share with the team. ZestineTech's pitch is to diagnose crashes "in minutes, not hours."

Note on sources and scope: Ze’Diag isn’t installed inside Revit. It’s a web application you open in a browser, and it’s listed on the Autodesk App Store as a "web-based Autodesk Revit journal analyzer." Some directories group it under Revit add-ins and scripts because it’s part of the Revit tool ecosystem. This summary is based on ZestineTech’s product page, the Ze’Diag web app’s own pages, the Autodesk App Store listing, ZestineTech’s LinkedIn posts, a third-party directory entry, and Autodesk’s documentation on journal files. I found no independent reviews or hands-on tests. Performance claims, such as the speed of the analysis and the crash statistics on the product page, come from ZestineTech.

The Problem It Addresses: Reading Revit Journals

Autodesk's documentation explains what journals are and why they matter, and it shows why a tool like Ze’Diag has a place:

• Revit writes a journal every session: A new journal file (for example Journal.0001.txt) is created each time Revit starts, and the highest number is the most recent. Journals record activity from startup to shutdown. They're normally stored under the user's local AppData folder, in Autodesk\Revit\Autodesk Revit [version]\Journals, which is hidden by default in Windows.
• They hold the answers but are hard to read: Autodesk describes journals as useful for troubleshooting both on the affected machine and remotely. Reading them takes practice, because you have to know what to search for, such as exceptions, fatal errors, add-in entries, and the last successful command before a failure. ZestineTech notes that most BIM users aren't trained to do this.
• Other files travel with them: The journals folder can also hold dump files (.dmp) created when the program crashes, plus worker logs and abbreviated journals. Autodesk tells users to send a dump file to Product Support along with the journal.
• Crash investigations are manual: Common practice is to open the journal in a text editor, search for keywords, find the last successful command and the first error, and isolate suspect add-ins. Autodesk also offers a Notepad++-based search method for documented issues.

Ze’Diag automates that first-pass reading and presents the result in a consistent report format.

BIMIT by Integrated Projects (IPX): Scan-to-BIM as a Service

Overview

BIMIT is Integrated Projects' (IPX) scan-to-BIM product. You upload a registered point cloud of a building, and BIMIT turns it into a Revit model, floor plans, CAD drawings, and a quality report. It's sold as a standardized product with published prices, not as a custom modeling engagement. IPX launched BIMIT 4.0, a new engine, on October 15, 2026. It offers three settings. BIMIT 100 and 200 are fully automated, and BIMIT 300 adds an architect's review. IPX says its starting price is 4¢ per square foot for fully automated models, delivered in hours.

Note on sources and scope: BIMIT is an online ordering and delivery service, and what you get back is a Revit model (.rvt) that you open in Revit as normal. This summary is based on IPX's own BIMIT pages, its help center, developer documentation, and launch posts. I found no independent reviews or hands-on tests, so the speed, cost, and accuracy figures below are IPX's own claims.

What BIMIT Is, and Isn't

IPX's help center describes BIMIT as a fixed-price product that turns a point cloud into a usable building model, built to confirm square footage and equipment counts quickly. IPX is explicit about what it is and isn't:

• It is: A product with standardized, predictable pricing. It's built for fast, on-time delivery and can combine architecture, furniture, and MEP in one model file. It's intended for verifying floor areas, room dimensions, and element counts.
• It isn't: A custom service with a unique quote for every job, work priced by the hour or as a lump sum, or a set of separate files from different consultants.
• Not construction-grade: IPX says BIMIT should not be used as a definitive guide for construction. Point cloud registration from devices such as the Matterport Pro2 or Leica BLK360 has accuracy limits. Licensed professionals should always field-verify.
• No materials or specifications: The model has geometry but no material information or construction details. Non-graphical data is kept generic, so you can customize it yourself.

Product Roundup: underbim (ub.Suite Edition 1)

Overview

underbim was created around one idea: BIM technology should make real work easier. It is a focused, independent company built on about 25 years of hands-on BIM and Revit experience, starting in October 2001. It took shape as underbim around a decade ago, when practice, consultancy, and development came together under one identity. Its current product line, ub.Suite, turns real workflows into focused Revit software.

Key Takeaways

• Practice first: underbim did not start as a software company looking for problems to solve. It grew out of years of work with BIM models, project teams, training, and real production constraints.
• Workflow before software: The approach is to observe the real problem, structure the workflow, and then build a focused tool around it. Anything Revit already does well natively is kept, and unnecessary steps are removed.
• One person across the whole chain: The founder identifies workflow problems, analyzes them, designs the solution, writes the software, and understands how it behaves in a real BIM environment.
• Focused, ownable products: ub.Suite is a collection of focused tools that extend Revit where everyday workflows can be made clearer, faster, and more effective. It is licensed perpetually, with no subscription required to keep using the Edition purchased.

From BIM Practice to Software

Over the years, underbim has worked across BIM consultancy, implementation, training, automation, and custom development. Its process has three steps:

1. Observe: Find the real problem by looking at the work itself, including recurring friction, repetitive operations, information gaps, and model-control needs.
2. Structure: Reduce the problem to a clear sequence of steps, preserve what already works natively in Revit, and remove unnecessary steps.
3. Build: Develop focused software around the workflow instead of forcing the workflow around the software.

BackupMover: Keeping Revit Backups Out of the Working Folder

Overview

ub.BackupMover is an Autodesk Revit add-in from underbim, a Portugal-based BIM consultancy that has worked in BIM, Revit training, consulting, and software development since 2001. It is one of eight independent add-ins in ub.Suite Edition 1, which launched in late October 2026, and is positioned as a file safety utility. Its tagline, "Move the backups. Keep the folder clear," sums up the approach. It finds genuine Revit project and family backup files beside the current document and moves them into a controlled subfolder, keeping the working folder readable. It can run manually or automatically after each Save.

Note on sources: This summary is based mainly on underbim's full BackupMover product page, which covers the workflow, feature explorer, detection rules, manual and automatic modes, destination handling, and licensing. Background on how Revit creates backups comes from Autodesk documentation, Autodesk forums, and Revit community blogs. An independent review or hands-on test was not found, and gaps are listed under Open Questions.

The Problem Area: Revit Backup Files

Revit creates backup files automatically whenever a model is saved or synchronized. Where they go and how they behave depends on the type of model, and the sources below describe several recurring problems:

• Backups are saved beside the model, with no setting to change it: For standalone (non-workshared) models, Revit places backups in the same folder as the project, named like "project name.0001.rvt," "project name.0002.rvt," and so on. Forum answers confirm there's no built-in way to choose a different location. Once the maximum backup count is reached, Revit overwrites the oldest backup.
• Folders fill up with clutter: The numbered backup files pile up next to the files people actually work with, and they're easy to mistake for real project files. Revit family files create the same kind of backups.
• Cloud sync and server replication get overloaded: Users report that OneDrive uploads every backup, which wastes bandwidth and data. An IT manager described tens of gigabytes of extra data slowing synchronization between four offices.
• Workshared models use a separate backup folder: Revit stores central and local model backup information in a folder named [model name]_backup next to the model. Autodesk says not to delete or rename files in it, and to keep the folder with the model if it's moved or copied, renaming it to match if the model is renamed. Backups in this folder are incremental, so they aren't ordinary .rvt files.
• Manual and scripted workarounds: Common approaches include deleting backup files by hand, batch files with wildcards, Dynamo or Python scripts that move or delete files matching the numbered pattern, and older add-ins such as MoveBackup (later Wormhole for Revit), which moved backups into a subfolder or a chosen directory.

BackupMover addresses the clutter problem for standalone project and family files. Like the older add-ins, it moves numbered backups out of the working folder. Unlike broad scripts, it works only from the active document and applies strict matching rules, so it only ever moves files that are clearly that document's own backups.

Elevations: Top and Bottom Elevation Data for Revit Elements

Overview

ub.Elevations is an Autodesk Revit add-in from underbim, a Portugal-based BIM consultancy that has worked in BIM, Revit training, consulting, and software development since 2001. It is one of eight independent add-ins in ub.Suite Edition 1, which launched in late October 2026. Despite its name, it doesn't create elevation views. It's a vertical data tool. Its tagline, "Know where every element starts and ends," sums up the approach. It calculates each element's upper and lower elevations from its extents in the Revit model and writes them to usable instance parameters, using either Project or Survey coordinates as the reference.

Note on sources: This summary is based mainly on underbim's full Elevations product page, which covers the workflow, feature explorer, coordinate references, parameter output, and licensing. Background on Revit's elevation parameters and coordinate system comes from Autodesk documentation and community forums. An independent review or hands-on test wasn't found.

The Problem Area: Vertical Data in Revit

Knowing the absolute top and bottom elevation of elements matters for coordination, clearance checks, scheduling, tagging, and handing data to contractors or other software. Revit shows this information graphically, but it isn't consistently available as data that can be scheduled. Autodesk documentation and user forums describe several gaps:

• Built-in elevation parameters only exist for some categories: Ducts, pipes, cable trays, and conduit have detailed top, bottom, and centerline elevation parameters, and structural framing has Elevation at Top and Elevation at Bottom. Many other categories have no equivalent absolute elevation values.
• Level-relative values, not absolute ones: Parameters such as Elevation from Level give an offset from a level, not an absolute height. They're also unavailable in multi-category schedules.
• No level elevation in schedules: For elements such as columns, a schedule can show the base and top level names and offsets, but not the level's elevation as a number. That means you can't calculate the actual top or bottom elevation in a schedule or tag. This is a long-standing request on the Revit Ideas board.
• Annotation isn't data: Spot elevations can show heights relative to the Project Base Point or the Survey Point, but they're annotations in a view, not parameter values you can filter, schedule, or export.
• Dynamo workarounds go stale: A common fix is to add shared parameters and fill them with a Dynamo script. Forum users point out that values become outdated as heights and offsets change, unless someone remembers to rerun the script.
• Coordinate references cause confusion: Revit has an Internal Origin, a Project Base Point (the project's local zero), and a Survey Point (the real-world reference, often sea level). The same element can have very different elevation values depending on which reference is used.

Elevations addresses this gap. It works the same way across whichever categories you choose: it calculates top and bottom values and writes them to parameters you control, with the coordinate reference stated explicitly.

ScopeViews: Scope Box–Driven View Creation for Revit

Overview

ScopeViews is an Autodesk Revit add-in from underbim, a Portugal-based BIM consultancy that has worked in BIM, Revit training, consulting, and software development since 2001. It is one of eight independent add-ins in ub.Suite Edition 1, which launched in late October 2026, and is positioned as a view creation tool. Its tagline, "Define the scope. Generate the views," sums up the approach. It turns selected Revit Scope Boxes into repeatable sets of plan, section, and 3D views. View templates, scale, and naming are all set before the views are created.

Note on sources: This summary is based mainly on underbim's full ScopeViews product page, which covers the workflow, feature explorer, generated view set, templates and scale, naming, and licensing. The background on scope boxes comes from Autodesk documentation and community forums. An independent review or hands-on test was not found, and the gaps are listed under Open Questions.

The Problem Area: Views and Scope in Revit

In Revit, view "scope" is mainly controlled by scope boxes and crop regions. A scope box is a 3D region drawn around part of the model. Assign it to views and their crop extents follow the box, so changing the box once updates every view that uses it. Assign it to grids, levels, and reference planes and they appear only in views whose cut plane intersects the box. The difference is often summed up as "a crop region belongs to one view, a scope box belongs to the project." Documentation and user forums point to several recurring pain points:

• Repetitive view setup: Large or multi-zone projects need many plans, ceiling plans, and dependent views cropped consistently. Cropping views by hand often leaves them slightly misaligned on sheets.
• Assignment limits: Scope boxes can only be created in plan views. Since Revit 2023, users report they can no longer assign or change scope boxes on dependent section views and some other dependent views, though dependent floor plans still work.
• Finding and tracking scope boxes: Scope boxes appear only in views they intersect. Forum users report "losing" a scope box after deleting the views where it was visible, and they have no easy way to see which views use which box.
• Greyed-out or conflicting settings: The Scope Box parameter can be unavailable, for example when a view template controls it, which makes troubleshooting harder.
• Bulk work needs add-ins: Creating dependent views from scope boxes, reassigning scope boxes across many views, or copying scope boxes from linked models is commonly done with third-party add-ins or Dynamo, not native tools.

ScopeViews tackles the repetitive-setup part of this problem. It uses the Scope Boxes you've already defined as the spatial basis for generating complete, consistently set-up view sets, so you don't have to create and crop each view by hand.

ConstraintScanner: Inspecting Constraints in Revit Projects

Overview

ub.ConstraintScanner is an Autodesk Revit add-in from underbim, a Portugal-based BIM consultancy that has worked in BIM, Revit training, consulting, and software development since 2001. It is one of eight independent add-ins in ub.Suite Edition 1, which launched in late October 2026, and is positioned as a model diagnosis tool. Its tagline, "See the relationships. Inspect what they mean," sums up the approach. It scans Revit constraints, dependencies, and model conditions, narrows the results to the relationships that matter, and lets users go straight from the evidence to the elements involved, without changing the model.

Note on sources: This summary is based mainly on underbim's full ConstraintScanner product page, which covers the workflow, feature explorer, coverage, and licensing. The background on Revit constraints comes from Autodesk documentation and community forums. An independent review or hands-on test wasn't found, and gaps are listed under Open Questions.

The Problem It Addresses: Constraints in Revit

Constraints build intelligence into a Revit model by setting relationships between elements. They're powerful, but they're also a common source of confusion and unexpected model behavior. Autodesk's documentation and user forums describe several traits that make constraints hard to manage at project scale:

• Several kinds of constraints: Explicit constraints (locked alignments, locked dimensions, and EQ equality constraints) always hold, and conflicts with them cause errors. Looser relationships, such as unlocked dimensions and alignments, may be dropped without notice when a conflict occurs. Implied constraints, such as walls attached to roofs or joined at corners, are managed by Revit itself.
• Constraints exist apart from dimensions: Constraints don't belong to a specific view and can exist without the dimension that created them. Deleting a dimension doesn't always remove the constraint, so "hidden" constraints can remain in the model. Several locked dimensions between the same two references can also map to a single constraint.
• Hard to trace: Revit's native Reveal Constraints mode shows constraints only temporarily, in the current view. Users on Autodesk forums report they can't find which locked dimension or view controls an element, or "take me to" the source of a constraint.
• No native bulk review: Revit has no built-in way to list, filter, or unlock constraints across a whole project. Users have turned to Dynamo scripts or the Revit API, where constraints sit in a separate category from dimensions.
• Over-constraining and unpredictable behavior: Leftover or unnecessary locks can make elements resist edits or move unexpectedly. In workshared models, a constraint can't be edited if any constrained element is in a workset the user can't edit.

ConstraintScanner is aimed at this gap. It helps BIM managers, coordinators, and modelers inspect and understand the constraints and dependencies already in a model, instead of discovering them one at a time when an element won't move.

ProjectManager: Project Cleanup with Context Attached

Overview

ProjectManager is an Autodesk Revit add-in from underbim, a Portugal-based BIM consultancy with experience in BIM, Revit training, consulting, and software development since 2001. It is one of eight add-ins in ub.Suite Edition 1, released in late October 2026, and can be purchased individually or as part of the suite. underbim summarizes its purpose as “Know what is in the project. Decide what stays.” The add-in audits recurring Revit project resources—V/G filters, scope boxes, view templates, and views—classifies them as used, unused, or unreferenced, shows their dependencies, and supports batch view management and controlled cleanup. Its defining principle is “audit first, change second”: discovery and filtering are kept separate from destructive operations, every change can be previewed before it is applied, and an applied operation retains a single Revit Undo path.

This summary is based primarily on the text of the official ProjectManager product page, supplemented by underbim’s website, suite overview, and announcement. The product page is marketing material: the Views workflow and delete behavior are described in detail, while some feature areas are summarized briefly. No user guide, independent review, or hands-on testing was available, so the remaining gaps are listed as open questions rather than filled with assumptions.

Core Concept: Audit First, Change Second

ProjectManager brings recurring project-management operations into one place, so the target set can be understood before anything is renamed, detached, or deleted. The product page frames this in four stages:

• Find: search, filters, and project content.
• Classify: used, unused, and unreferenced.
• Review: dependencies, protection, and preview.
• Act: batch changes, delete, and Undo.

Six-Step Workflow

underbim describes the workflow as “Find the target set. Understand it before acting.” Discovery and filtering are separated from destructive operations so that project cleanup remains an explicit user decision:

1. Audit: read the current project content across the supported resource areas and views.
2. Filter: reduce the list by usage, search criteria, or native Revit view properties.
3. Understand: review usage counts, dependencies, sheet placement, references, and protected conditions.
4. Select: build the working set manually or from the current filtered result.
5. Preview: see what will be deleted, skipped, or detached before the Revit document is modified.
6. Apply: commit the selected operation, review the result, and retain a single Revit Undo path.

InterferenceInvestigator: Interference Management in Revit

Overview

InterferenceInvestigator is an Autodesk Revit add-in from underbim, a Portugal-based BIM consultancy with experience in BIM, Revit training, consulting, and software development since 2001. It is one of eight add-ins in ub.Suite Edition 1, released in late October 2026, and can be purchased individually or as part of the suite. underbim summarizes its purpose as “See the clash. Understand the pair.” The add-in focuses on the work after interference detection: moving from an interference result to the exact host and linked elements involved, locating them in the Revit model, recovering enough surrounding context to understand the problem, tracking a review state for each occurrence, and turning the investigation into an actionable result. Reviewed results can become a native Revit schedule, a .ubr result package, or input to ModelData.

This summary is based primarily on the text of the official InterferenceInvestigator product page, supplemented by the ModelData and FilterToSchedule product pages, underbim’s website and suite announcement, and Autodesk documentation on the native Interference Check. The product page is marketing material: several feature areas are described in detail, while others are only named. No user guide, independent review, or hands-on testing was available, so the remaining gaps are listed as open questions rather than filled with assumptions.

Core Concept: A Clash Becomes Useful When You Can Investigate It

underbim states that InterferenceInvestigator is “built for the work after detection”: identifying the pair, reaching the actual elements, understanding their model context, and deciding what needs to happen next. The product page frames this as four stages:

• Result: a structured interference set.
• Pair: host and linked participants with their identities.
• Context: select, isolate, and Focus 5%.
• Continue: schedule, .ubr, or ModelData.

The page’s coordination-workflow graphic illustrates a pair consisting of a host structural beam and a linked service element, labeled “Status · Open,” following a path of pair → model → context.

ModelData: A Schedule-Centered Data Workbench

Overview

ModelData is an Autodesk Revit add-in from underbim, a Portugal-based BIM consultancy with experience in BIM, Revit training, consulting, and software development since 2001. It is one of eight add-ins in ub.Suite Edition 1, released in late October 2026. underbim positions it as a “data workbench” to “build, inspect, calculate and refine Revit schedule and model data with more control over the logic behind the result.” Rather than replacing Revit schedules with a separate data viewer, ModelData extends the schedule workflow with richer field sources, logical filters, grouping, calculated and combined values, investigation in the model, and reusable definitions and results. It is sold individually or as part of the complete ub.Suite.

This summary is based primarily on the text of the official ModelData product page, supplemented by underbim’s website and suite announcement. The product page is marketing material: it describes capabilities at a high level, and some feature areas are named without detailed explanation. No user guide content, independent review, or hands-on testing was available, so those gaps are identified in the open-questions section rather than filled with assumptions.

Core Concept: Work with the Logic Behind the Schedule

The product idea is to extend Revit’s schedule workflow “with filters, grouping, derived values and model context — while keeping the native Revit schedule at the centre.” underbim frames this as four connected layers:

• Input: native and semantic fields.
• Logic: filters and structure.
• Data: calculated and combined values.
• Context: investigation in the model.

The product page includes an illustrative data-workbench preview listing walls with Element, Level, Calculated, and Status columns, in which one row is flagged “CHECK” while the others show “OK.” This suggests that calculated values and status-style results can be used to flag items for review. Because it is a marketing preview, the specific rules behind such a status column are not explained.

Six-Step Workflow

underbim describes a connected workflow in which each step, “from source data to final output,” remains part of the same process:

1. Fields: choose native, semantic, and derived data sources.
2. Filter: build conditions and logical groups around the result.
3. Structure: sort, group, and organize the schedule output.
4. Calculate: create concatenations and calculated data where needed.
5. Investigate: move from rows and values back into model context.
6. Output: keep the Revit schedule or continue into reusable results.

FilterToSchedule: Revit Schedule Snapshots With OR Statements

Overview

FilterToSchedule (F2S) is an Autodesk Revit add-in from underbim, a BIM consultancy with experience in BIM, Revit training, consulting, and software development since 2001. It is one of eight add-ins in ub.Suite Edition 1, released in late October 2026, and can be purchased individually or as part of the suite. underbim summarizes its purpose as “Filter once. Keep the result.” The add-in turns defined Revit filter results into persistent native Revit schedule snapshots that can be reviewed, refreshed, duplicated, and carried into the next workflow, either as a stored .ubr result or directly in ModelData.

This summary is based primarily on the text of the official FilterToSchedule product page, supplemented by the ModelData product page, underbim’s website and suite announcement, and Autodesk documentation on native schedule filters. The product page is marketing material: some feature areas are described in detail, while others are only named. No user guide, independent review, or hands-on testing was available, so the remaining gaps are listed as open questions rather than filled with assumptions.

Core Concept: Make the Result Persist

underbim observes that a filter is useful while it is being evaluated, but its result is not otherwise retained. FilterToSchedule turns that result into a native Revit schedule snapshot with its own identity, provenance, and controlled lifecycle. The product page frames this in four stages:

• Scope: model, category, and context.
• Logic: Filter A and Filter B with AND/OR.
• Result: a native Revit schedule snapshot.
• Continue: refresh, create a .ubr, or open in ModelData.

The page’s workflow graphic shows source elements passing through Filter A (parameter, operator, value), an AND/OR connector, an optional Filter B, and a stored, persistent schedule snapshot. This indicates that a result is built from one or two parameter conditions; the page does not state whether more conditions or nested groups are possible.

BPM — BIM Production Manager: A Dashboard for Managing Drawing-Sheet Production Inside Revit

Overview and Purpose

BPM, short for BIM Production Manager, is a Revit add-in from BREVIT LLC focused on managing drawing-sheet production inside the authoring environment. It brings sheet status, tasks, assignments, production phases, reference links, notes, sketches, PDF export, and print-set preparation into a single dashboard. Its scope is drawing-production coordination rather than geometric modeling, engineering analysis, or clash detection.

Dashboard and Sheet Management

• Modeless interface: the dashboard can remain open while users work in Revit, reducing the need to repeatedly close a dialog to return to the model.
• Sheet-set visibility: sheet cards provide an overview of the drawing set and its production status, with a detail panel for selected-sheet information.
• Grouping: sheets can be organized into groups and moved between them to support the team’s production structure.
• Sheet metadata: the documented detail workflow includes editing sheet number, sheet name, and a Reference / Link field.
• Bulk selection: selecting several sheet-row checkboxes switches the panel into bulk-edit mode. Sheet numbers and names are locked in this mode to prevent accidental collective renaming.
• Sheet duplication: a Duplicate Sheet action is documented.

Tasks, Progress, and Production Phases

• Sheet-based tasks: tasks can be added to an individual sheet or applied across multiple sheets, supporting repeated production checklists without entering the same item separately on every drawing.
• Task completion: users can check and uncheck tasks. Completion stamps record the user and time, providing context for checklist updates.
• Progress tracking: the dashboard exposes sheet-production progress. The reviewed source excerpts do not specify the calculation formula, task weighting, or whether progress can also be entered manually.
• Phase assignment: sheets can be associated with production phases and filtered to focus on the phase being prepared.
• Live phase filtering: removing a sheet from the active phase removes it from the filtered list immediately; adding a sheet to that phase brings it into the list without a manual refresh.

Revit Add-ons Eclipses 4,000 Post Mark!

We recently made our 4,000th post about a week ago with Product Roundup: Karo Modum. We knew we were close, but still ticked past the landmark. At an average of one post per day, that would be about 11 years of posts. We now sit at 4,009 published posts and slightly over 4.8 million pageviews. That makes us happy. Thank you readers!

Advertisement

LengthMEP: Measure and Tabulate the Lengths of MEP Elements

Overview

LengthMEP is a focused Autodesk Revit add-in from DQ Projects for measuring and tabulating the lengths of mechanical, electrical, and plumbing elements. Its documented capabilities combine length checks on preselected elements with the creation of category-specific and multicategory quantity schedules. The publisher also describes measurement in views and updating total values by diameter or size. Its primary purpose is quantity reporting rather than system design or engineering calculations.

Supported Revit Categories

• Electrical: conduits, wires, and cable trays.
• Mechanical: ducts and flex ducts.
• Plumbing and piping: pipes and flex pipes.

These are the seven categories explicitly identified in the Autodesk Marketplace description. Fittings, accessories, equipment, fabrication parts, and linked-model elements are not expressly identified as supported measurement categories. Their treatment should therefore be confirmed rather than assumed.

Principal Commands and Outputs

• LengthMEP command: creates quantity schedules for the supported categories, creates a multicategory schedule, and updates total values by diameter or size. This provides a reporting-oriented workflow for reviewing accumulated lengths rather than inspecting elements individually.
• Selection command: displays total length for supported elements that the user has already selected. Preselection is an explicit prerequisite in the publisher’s description, making this command suitable for focused checks of a chosen group of elements.

The two-command interface separates quick measurement from schedule-based reporting. However, the available description does not explain the schedule field layouts, sorting and filtering rules, treatment of mixed categories, or whether the reported results refresh automatically after model changes. Because an update function is explicitly mentioned, users should verify when it must be rerun.

BNotes: Advanced Keynote Manager

Overview

Bnotes—Advanced Keynote Manager is a Revit add-in from BREVIT LLC that provides a visual interface for searching, editing, organizing, and maintaining keynote text files. It retains Revit’s external .txt keynote-file workflow while reducing the need to maintain that file manually in a separate editor. Its main capabilities combine hierarchical browsing, usage indicators, inline editing, reference updates, file recovery, and coordination tools for cloud-hosted keynote files. 

Keynote Browsing and Editing

• Hierarchical tree view: Keynotes appear in a collapsible parent/child structure. The Marketplace listing identifies blue entries as used, red entries as unused, and black entries as parent or category headings. This makes project usage visible without reviewing a flat text file.
• Live search: Entering part of a keynote key or description filters the tree. The listing describes debounced searching intended to remain responsive with thousands of entries.
• Inline editing: Users select an entry and change its key or description in the detail panel. Changes can be written back to the keynote file and applied to Revit. The guide distinguishes Update Selected, Reload From File, Refresh, and Save & Apply to Revit controls.
• Adding and reorganizing notes: Users can add child or sibling entries, edit a parent key to move an entry within the hierarchy, and delete entries with confirmation. New keys are automatically numbered to follow the existing scheme, according to the listing.
• File-wide text-case tools: Descriptions can be converted to Title Case, UPPERCASE, or lowercase. These are broad standardization operations across the file, rather than selective editorial corrections.

Usage Checking and Reference Coordination

• Usage navigation: Users can click usage indicators to reach the sheets and views where a keynote is used. This provides a connection between library maintenance and placed documentation.
• Bulk reference updates: Renaming a keynote key updates placed references across sheets in one Revit transaction. The precise coverage of element assignments, annotations, and project-specific conditions should be verified in a trial.
• Orphan detection: Identification of missing-key references and entries no longer referenced. These conditions should be treated differently: an unused library note may be intentional, whereas a placed reference with a missing key requires investigation.
• Keynote types: The product page explicitly identifies element and user keynotes. The reviewed material does not clearly establish equivalent material-keynote support; firms requiring that workflow should confirm it directly.