The BIMIO Suite | User guide

Overview

BIMIO is a suite of add-ins for Autodesk Revit created by Francis Martinez. Every tool lives under a single BIMIO tab on the Revit ribbon, sharing the same Apple-inspired window design, a common light and dark theme, and a shared infrastructure that coordinates work with the Revit API. The name sums up the idea: BIM I/O. Most of the tools put data into the model (Excel, standards, coordinates), reshape it, or get results out (schedules, reports, shareable HTML). The ribbon panels read from left to right following that flow.

Unlike a collection of loose plugins, BIMIO installs and loads as a single package: one manifest (FJV.Tools.addin) starts a host that creates the tab, builds the panels and composes each tool when Revit starts. Each tool starts up individually protected, so if one were to fail to load, the rest of the suite keeps working normally and the failure is recorded in a local log.

This general manual explains what BIMIO is, how it is installed and deployed, how the tab and its panels are organised, which interface conventions all the tools share, and how to diagnose loading problems. Each tool (Relay, Assay, Palette, Lens, Canon, Pinup, etc.) also has its own detailed manual.

Who it's for

Architects, modellers and BIM managers who work with Revit 2022 to 2026 and want a coherent set of productivity, quality-control and standards tools. The installation and deployment workflows are aimed at the practice's BIM manager or IT lead; the rest of the manual serves any Revit user.

Requirements

Windows with Autodesk Revit 2022, 2023, 2024, 2025 or 2026 installed (BIMIO builds a specific version for each Revit year).
To build from source: Visual Studio 2022 (Community or higher) and the repository's FJV.sln solution; the R22 to R26 configurations correspond to each Revit version.
To install without building: an already-generated build folder (FJV.Tools with all its DLLs) and the FJV.Tools.addin manifest, copied into the Revit add-ins folder for the corresponding year.
Write permissions in %AppData%\Autodesk\Revit\Addins\<year> for the per-user routes (deployment script or folder copy, no administrator rights), or administrator rights once if you install with the MSI (per-machine).
The Excel round-trip tools (Relay, Inlay, Christen) read and write .xlsx files directly, with no need to have Excel installed; any spreadsheet application will do for editing the workbooks. See each tool's manual.

Where to find it

BIMIO tab on the Revit ribbon→seven panels: Setup, Family Editor, Data, QA / QC, View, Misc and About

The BIMIO tab appears automatically when Revit starts if the suite is deployed for that version.

Each button shows a short description on hover, and a longer explanation if you keep the cursor there a moment longer (Revit's extended tooltip).

Some buttons appear greyed out intentionally: Mold is only enabled inside the Family Editor, and Reset View and Bloat are disabled because their tools have not been released yet.

Key concepts 8 terms

Host: The component that Revit actually loads. It creates the BIMIO tab, builds the panels and buttons, and starts each tool in the suite when Revit launches. It is the only add-in registered with Revit: there are no individual per-tool manifests.

Manifest (.addin): The FJV.Tools.addin file that is copied into %AppData%\Autodesk\Revit\Addins\<year> and tells Revit which DLL to load. The whole suite shares a single manifest; if you see old per-tool manifests, they should be removed (the deployment script does this for you). With the MSI installer the same manifest lands in C:\ProgramData\Autodesk\Revit\Addins\<year> instead (per-machine).

Ribbon panel: Each headed group within the BIMIO tab. They are ordered by BIM workflow stage: Setup (prepare the project), Family Editor (families), Data (data in/out), QA / QC (quality control), View (views and sheets), Misc (utility toolbox) and About.

Apple-style window: All BIMIO windows share the same visual frame: rounded corners, traffic-light window buttons (close, minimise, maximise), Segoe UI typography and controls with the same theme. Warnings and errors use the suite's own dialogs in the same style, never the standard Windows message boxes.

Light / dark theme: The entire suite shares one theme preference (light or dark), saved in %AppData%\FJV\Common\theme.txt. When you change it from any tool that exposes the toggle (for example, Relay's sun/moon button), every BIMIO window adopts the same appearance.

Suite backbone (shared store): A common infrastructure that starts with the suite: an event bus and a local per-project store (an SQLite database on your machine) where the tools publish facts such as synchronisations or model changes. It is what feeds the Health dashboard. Everything is local: nothing leaves your machine.

Toast (notification): A floating, unobtrusive notice in the suite's style that some tools show without interrupting you. The prime example is Canon, which watches project standards in real time and alerts you with green, amber or red toasts depending on severity.

Contextual availability: The mechanism by which a ribbon button is shown greyed out when it is not appropriate to use it. Mold only lights up with a family document open; Reset View and Bloat stay greyed out until they are released.

The interface

BIMIO's overall interface is the Revit ribbon tab itself. It contains seven headed panels, ordered left to right following the typical BIM workflow: first you prepare the project (Setup), then work on families (Family Editor), move data (Data), control quality (QA / QC), prepare views and sheets (View), handle one-off tasks (Misc) and consult the suite's information (About).

Each button opens its tool in its own window with the suite's common style. The Misc panel is special: alongside the Misc button, which opens a searchable launcher, it groups the utilities into drop-down buttons and compact stacks (Along Path, Sheet Graphics, Select & Find, Annotate, Renumber, Titles, Viewport, Datum Tools, Views and direct shortcuts such as Set Integrity, Cleanup, Type Swap and Param Copy).

The Revit ribbon with the BIMIO tab active, showing the seven panels (Setup, Family Editor, Data, QA / QC, View, Misc, About) with their icons; the cursor over the Relay button with its extended tooltip visible.

Setup panelProject start-up and standards tools: Graft (transfer standards from another model with per-element control), Datum (audit the coordinates and geo-referencing of the model and its links) and Canon (the live standards engine; its button opens the per-project configuration).

Family Editor panelMold, the spreadsheet-style editor for the open family (type-by-parameter matrix, formula auditing and file hygiene). The button is only enabled when the active document is a family; in a project it appears greyed out.

Data panelData in and out with Excel: Relay (round-tripping Revit schedules with Excel, with a preview of every change before applying), Inlay (insert an Excel range as a formatted table in a drafting view or legend, with a Refresh button that detects external edits) and Christen (bulk renaming of families and types via Excel).

QA / QC panelQuality control: Assay (model audit and inventory with an HTML report), Lens (dockable panel with change history and extended properties for the selected element), Clash (interference detection by category pairs with marker spheres), Bloat (heavy-family analysis; still disabled, coming soon) and Health (opens an HTML dashboard in the browser with the project's health read from the suite's shared store).

View panelViews and sheets: Palette (view filter and template editor), Select (rule-based selection by category and parameters, with colouring), Trace (diagnose why an element is not visible in a view), Reset View (undo graphic tricks in the active view; still disabled, coming soon), Room Sheets (generate one sheet per room with its views placed automatically) and Pinup (digital mark-up sessions over the sheet set, with HTML export and re-import of annotations).

Misc panelThe toolbox: the Misc button opens the searchable hub with all the utilities; beside it, drop-down groups by theme: Along Path (dimensions, tags, spot elevations and families along a path, plus Section Strip), Sheet Graphics (Key Plan, QR Stamp, Scale Bars, Grid Rulers, Section Locator, Cover Mosaic, Match Lines), Select & Find (Multi-ID, Ripple, View Locator, Sketch Owner), Annotate (Tag Master, Anno Tidy), Renumber (by click and for details), Titles (Title Align, Title Audit, Title Block Manager), Viewport (Viewport Sync, View Swapper), Datum Tools (Datum Bubbles, Datum Doctor), Views (Category Switch, Schedule Style, Template Diff) and direct buttons Set Integrity, Cleanup, Type Swap and Param Copy.

About panelAn About button that opens the suite's presentation window (the BIMIO brand, the installed version, the author and the copyright, plus a button to rate the suite and send feedback to the author) and a Manuals button that opens a search-first browser of the PDF user manuals shipped with the suite.

Tool windowsEach tool opens its own window with the common visual frame: a title bar with the traffic-light buttons on the left, a title in the format BIMIO · ToolName, controls in the active theme (light or dark) and error and confirmation dialogs in the same style. On the right of the title bar, a small book button opens that tool's own PDF manual directly (the Misc utilities open the Misc manual, Select opens its own); the button only appears when the manuals are staged next to the binaries.

Step-by-step workflows 11 workflows

1

Install BIMIO with the installer (MSI)

4 steps

Goal. Install the suite on any machine in a couple of clicks, choosing which Revit versions to install.

Double-click the BIMIO installer (BIMIO-<version>.msi) and accept the licence agreement.This is the route used by the Autodesk App Store; you can also receive the .msi file directly.
In the feature tree, choose which Revit versions to install BIMIO for.Every Revit version included in the installer (2022 to 2026) is ticked by default; untick the years you do not want. Versions not built into that installer release are not offered.
assets/shots/bimio-suite/fig-03.pngBIMIO installer feature tree with one entry per Revit version, all ticked.
Click Install, confirm the administrator prompt and finish the wizard.The MSI installs per-machine (for all users of the computer), so Windows asks for administrator rights once.
Start Revit and check that the BIMIO tab appears.

Result. BIMIO is installed for every user of the machine under C:\ProgramData\Autodesk\Revit\Addins\<year>: the manifest, the self-contained binaries and the PDF manuals, so the Manuals button works straight away.

To update, simply run the newer installer: it replaces the previous version automatically, with no need to uninstall first.
To remove BIMIO, uninstall it from Windows Settings, Apps, like any other application.
Do not combine the installer with the developer deployment on the same machine: Revit would see the add-in twice (same identifier) and refuse one of them. Uninstall the MSI, or delete the per-user copy, when switching between the two.

2

Build and deploy BIMIO on your machine

6 steps

Goal. Build the suite from source and leave it installed for your Revit versions using the deployment script.

Open FJV.sln in Visual Studio 2022.The solution contains every project in the suite; there is no need to open anything else.
Select the configuration for your Revit version (R22, R23, R24, R25 or R26) and build the solution.R22 to R24 build for .NET Framework 4.8 (Revit 2022 to 2024); R25 and R26 for .NET 8 (Revit 2025 and 2026). You can build several configurations, one per year.
Close Revit if you have it open, or let the script do it for you.The script detects running Revit processes and asks for confirmation before closing them; with the -Force parameter it closes them without asking.
From the repository root, run in PowerShell: .\tools\deploy-lens.ps1With no parameters it deploys every year it finds built. With -Years 2024,2025 you limit the years; with -DryRun you see what it would do without copying anything; with -Force it skips confirmations.
assets/shots/bimio-suite/fig-04.pngPowerShell console showing the script's output: builds discovered per year, copy steps and the final summary with every year at OK.
Check the script's final summary: every year should finish at OK.The script verifies that the critical files (FJV.Tools.dll, FJV.Common.UI.dll, the Lens and SQLite DLLs, and in 2025/2026 the .NET 8 files) exist before and after copying. SKIPPED means an incomplete build; FAIL, files missing after the copy.
Start Revit and check that the BIMIO tab appears.The first time, Revit may show its add-in security warning; click Always Load or Load Once.

Result. The suite is installed in %AppData%\Autodesk\Revit\Addins\<year>\ for each deployed version: the FJV.Tools.addin manifest at the root of the year and the FJV.Tools folder with all the binaries. The script also cleans up zombie manifests and folders from old versions.

Always run the script from the repository root; otherwise, pass it -RepoRoot with the correct path.
Use -DryRun the first time to see exactly what would be copied and where.
Repeat build and deploy after every code update: deploying is idempotent and deletes the previous folder before copying.

3

Install BIMIO on another machine without building

4 steps

Goal. Take the suite to a colleague's machine by copying a folder, with no Visual Studio or repository.

On a machine where BIMIO already works, open the %AppData%\Autodesk\Revit\Addins\<year> folder for the Revit year you use.There you will find the FJV.Tools.addin file and the FJV.Tools folder with all the DLLs.
Copy the FJV.Tools.addin file and the complete FJV.Tools folder to a USB stick or network drive.The build is self-contained: every dependency, including native ones such as e_sqlite3.dll, is inside the folder. This portable route needs no installer and writes no registry entries.
On the target machine, paste both into %AppData%\Autodesk\Revit\Addins\<year> for the same Revit year.The year must match: a Revit 2024 build will not work in Revit 2025 (even the .NET framework changes).
Start Revit on the target machine and accept the add-in security warning if it appears.

Result. BIMIO works on the new machine exactly the same: deploying is literally copying a folder plus its manifest.

If your colleague uses a different Revit version, copy the folder for the year that matches (each year has its own build).
Check that no old per-tool manifests remain (for example FJV.ChangeTracker.addin) in the year's folder: the suite uses a single manifest.

4

First launch: getting to know the BIMIO tab

4 steps

Goal. Familiarise yourself with the ribbon layout and know what to expect from each panel.

Start Revit and click the BIMIO tab on the ribbon.The tab is created when Revit starts, before opening any project. Most tools, however, will ask for an open project when you launch them.
assets/shots/bimio-suite/fig-05.pngRevit ribbon with the BIMIO tab selected and the seven panels visible from left to right.
Walk through the panels from left to right: Setup, Family Editor, Data, QA / QC, View, Misc and About.The order follows the BIM workflow: prepare the project, edit families, move data, control quality, assemble views and sheets, and loose utilities.
Hover over any button and wait a moment to read its longer description.Each button has a short tooltip and an extended explanation summarising what the tool does before you open it.
Notice the greyed-out buttons: Mold (only enabled in the Family Editor), Reset View and Bloat (coming soon).This is intentional behaviour, not a loading failure.

Result. You know where each tool lives and understand the logic of the panels, which makes the rest of the manuals much easier to follow.

If you mostly work with sheets, your area will be View and Misc; if you are a BIM manager, Setup and QA / QC concentrate the model-governance tools.

5

Open a tool from the suite

4 steps

Goal. Launch any tool from the ribbon and recognise the common conventions of its windows.

Open a Revit project (or a family, if you are going to use Mold).Almost every tool needs an active document; if there is none, it will ask for one with a notice in the suite's style.
Click the tool's button on its panel of the BIMIO tab.For example: BIMIO → Data → Relay, or BIMIO → QA / QC → Assay.
Look at the window that opens: a title bar with the traffic-light buttons on the left and a BIMIO · ToolName title.All windows share theme, typography and controls; errors and confirmations appear in the suite's own dialogs, never in Windows message boxes.
assets/shots/bimio-suite/fig-06.pngA BIMIO window (for example Relay) showing the Apple-style window frame: traffic-light window buttons, title with the middle-dot separator and light-theme controls.
Work with the tool and close it from its own close button when you finish.The windows do not block Revit except for modal dialogs; tools with dockable panels (such as Lens) integrate into the Revit frame itself.

Result. Any tool in the suite open and running, with an identical experience from one to the next.

The changes a tool makes to the model are grouped into a single named transaction (in the format FJV Tool — action), so you can undo them with a single Ctrl+Z from Revit.

6

Launch utilities from the Misc hub

5 steps

Goal. Quickly find and run any of the utilities in the Misc toolbox using the searchable launcher.

With a project open, click BIMIO → Misc → Misc.If there is no project open, you will see the Open a project first notice.
Type in the search box to filter the list of utilities.The hub is a Spotlight-style launcher: the list is organised into cards by section and filters live as you type. Your most-used utilities appear highlighted as frequent shortcuts.
assets/shots/bimio-suite/fig-07.pngMisc hub window with the search box at the top, the utility cards in two columns and the footer with the tool count and the colour legend.
Notice the coloured dot on each row: amber means the utility modifies the model; green means it is read-only.The legend also appears in the window's footer.
Navigate with the up and down arrows, and press Enter to launch the highlighted utility (or click on it directly). Esc closes the hub without launching anything.The hub closes first and the utility runs afterwards, so it can ask you for on-screen selections or open transactions without conflicts.
Alternatively, launch the utility directly from its drop-down button on the Misc panel, without going through the hub.The drop-downs group by theme: Along Path, Sheet Graphics, Select & Find, Annotate, Renumber, Titles, Viewport, Datum Tools, Views, plus the direct buttons Set Integrity, Cleanup, Type Swap and Param Copy.

Result. The chosen utility runs; the hub records the usage to highlight your frequent tools next time.

Before launching an amber utility in a workshared model, remember it will modify elements: check what it does in its description in the hub's right-hand panel.
The hub shows the total number of available utilities in the footer: the toolbox grows with every version.

7

Assign keyboard shortcuts to the tools

4 steps

Goal. Launch your favourite BIMIO tools from the keyboard using Revit's standard shortcut system.

In Revit, open File → Options → User Interface → Keyboard Shortcuts (or type KS).
Search for the name of the BIMIO tool you want (for example Relay, Trace or any Misc utility).Every ribbon button, including the items inside the Misc drop-downs, has its own individual command, so all of them are assignable.
Assign the key combination and click OK.
Test the shortcut with a project open.

Result. Your most-used tools launch without touching the ribbon, with standard Revit shortcuts that persist between sessions.

The most frequent Misc utilities (Multi-ID, Key Plan, QR Stamp...) benefit greatly from a shortcut: you save yourself opening the drop-down or the hub.

8

Check the project's health (Health)

3 steps

Goal. See the project's activity and health across all the suite's tools in a single dashboard.

With the project open, click BIMIO → QA / QC → Health.Health needs an open project: if there is none, the button simply does nothing.
Wait for your browser to open with the HTML dashboard.The report is generated as a self-contained local file in your temporary folder (FJV-Suite-Dashboard-<code>.html, a unique name per project) and opens in the default browser.
assets/shots/bimio-suite/fig-08.pngHealth dashboard open in the browser: health score, synchronisation cadence, per-tool activity and a filterable timeline.
Review the health score, the synchronisation cadence, who has gone a while without synchronising, the rate of change and the 30-day trends.The data comes from the local per-project store where the suite's tools publish their activity. Nothing leaves your machine.

Result. A local HTML report with a health snapshot of the project across the whole suite, ready to review or archive.

The dashboard gets richer the more you use the suite on that project: it feeds on the recorded activity (synchronisations, changes, audits).
If the browser does not open automatically, the report has already been generated: look for FJV-Suite-Dashboard-*.html in your temporary folder (%TEMP%) and open it manually.

9

See the installed version and send feedback (About)

5 steps

Goal. Check which version of BIMIO you have and send the author a rating or a comment.

Click BIMIO → About → About.It does not need any document open.
assets/shots/bimio-suite/fig-09.pngAbout BIMIO window: the cube brand with input and output nodes, the BIMIO name, the BIM tools for Revit tagline, the version and the Rate / send feedback and Close buttons.
Read the installed version (Version x.y.z) and the credits.The version is read from the installed binary itself, so it always reflects the build you have deployed.
If you want to give your opinion, click Rate / send feedback.
Choose a rating from 1 to 5 stars, write a note (optional if you have rated) and click Send feedback.You must rate or write a note, at least one of the two; if not, the window will remind you. The submission includes your rating, the note, the BIMIO version and your Revit version. It is sent directly to the author; if the direct send fails, a pre-filled email draft opens and, as a last resort, the note is copied to the clipboard. Cancel discards the submission.
Click Close to close the About window.

Result. You know exactly which version of the suite you are running (useful when reporting a problem) and your feedback reaches the author.

Note down the version shown in About before reporting any issue: it is the first piece of information needed to reproduce it.

10

Switch between light and dark theme

3 steps

Goal. Put the whole suite into dark mode (or back to light) with a single shared preference.

Open a tool that exposes the theme toggle, for example BIMIO → Data → Relay.The toggle is the button with the sun/moon icon in its main window.
Click the sun/moon button to switch between light and dark.The change applies immediately to the suite's windows and is saved as a global preference in %AppData%\FJV\Common\theme.txt.
assets/shots/bimio-suite/fig-10.pngThe same Relay window before and after clicking the toggle: light palette versus dark palette.
Open any other BIMIO tool and check that it respects the chosen theme.The preference is a single one for the entire suite: there is no need to configure each tool separately.

Result. The whole suite stays in the chosen theme, which is remembered between Revit sessions.

Only Light and Dark modes exist; there is no automatic mode following the system. If an old preference said System, it is interpreted as Light.

11

Diagnose loading problems

6 steps

Goal. Find out why the BIMIO tab does not appear, why a button is missing or why a tool does not open.

If the BIMIO tab does not appear, check that %AppData%\Autodesk\Revit\Addins\<year> contains FJV.Tools.addin and the FJV.Tools folder with FJV.Tools.dll inside.If they are missing, deploy again with the script or copy the folder again. Remember that the folder's year must match your Revit version.
If Revit showed a security warning at start-up and you chose Do Not Load, restart Revit and accept loading the BIMIO add-in.
Open the suite's start-up log: %AppData%\FJV\Tools\logs\suite-startup-YYYYMMDD.log.There you will see a Registered / OnStartup OK line for each tool, and OnStartup FAIL or Register FAIL with the full error detail if any of them failed. A failure in one tool never brings down the rest: the suite keeps loading.
$Windows Explorer in the %AppData%\FJV\Tools\logs folder with the daily log files, and a log open in Notepad showing OnStartup OK lines.$
assets/shots/bimio-suite/fig-11.pngWindows Explorer in the %AppData%\FJV\Tools\logs folder with the daily log files, and a log open in Notepad showing OnStartup OK lines.
If a window does not open or appears unstyled, also check theme-bootstrap-YYYYMMDD.log in the same folder.It records the theme initialisation step by step with the full exception chain if something fails.
Delete old per-tool manifests if you find them in the year's folder (for example FJV.ChangeTracker.addin).The suite uses a single manifest; parallel manifests cause double loading and resource failures. The deployment script cleans up these zombies automatically.
As a last step, deploy again from a clean build: the script deletes the target folder and verifies the critical files after the copy.

Result. You identify the cause of the faulty load (incomplete deployment, zombie manifest, failure of a specific tool) with evidence from the log, and resolve it by redeploying.

The Reset View and Bloat buttons being greyed out, and Mold being greyed out outside the Family Editor, are normal behaviour, not a failure.
If the project's health store was written by a newer version of the suite, the log records it once and the suite keeps working without that store.

Options reference 7 options

Option	What it does
Light / Dark theme	A single visual preference for the whole suite, saved in %AppData%\FJV\Common\theme.txt. It is changed from the sun/moon toggle available in the Relay window and applies to every BIMIO window.
Deployment script parameters	deploy-lens.ps1 accepts -Years (list of years to deploy), -DryRun (simulation without copying), -Force (no confirmations, closes Revit automatically) and -RepoRoot (repository path if you are not running it from its root).
Per-tool keyboard shortcuts	Each button and each item in the Misc drop-downs is an individual Revit command, assignable from the standard Keyboard Shortcuts dialog (KS).
Misc hub frequents	The hub records locally which utilities you launch and highlights the most used as frequent shortcuts at the top. It is not manually configurable: it adapts to your usage.
Contextual button availability	Mold is only enabled with an active family document; Reset View and Bloat remain disabled until they are released. There is no user setting: it is automatic.
Feedback submission	From About → Rate / send feedback: a 1-to-5-star rating and a text note. It is sent directly to the author; if it fails, an email draft opens and, as a last resort, the note is copied to the clipboard.
Installer Revit-version features (MSI)	The installer's feature tree offers one feature per Revit year, all selected by default; untick a year to skip it. Each feature installs that year's self-contained build, the manifest and the PDF manuals.

What you get out

The BIMIO tab on the Revit ribbon with the suite's tools organised into seven panels.
Local diagnostic logs in %AppData%\FJV\Tools\logs: suite-startup-YYYYMMDD.log (each tool's start-up) and theme-bootstrap-YYYYMMDD.log (theme initialisation).
The Health dashboard: a self-contained HTML file per project, generated in the user's temporary folder and opened in the browser.
A local per-project store (one SQLite database per project in %AppData%\FJV\Suite\projects) where the tools record activity; it is what feeds Health. Everything stays on your machine.
Each tool also produces its own outputs (Excel, HTML reports, CSV, PDF...); see its specific manual.

Pro tips 5 tips

There are two ways to install BIMIO: the MSI installer (per-machine, pick your Revit versions, administrator rights once) or copying a folder (per-user, no installer, no administrator rights). Use one or the other on a given machine, not both.

Read the panels from left to right as a workflow: Setup to start the project, Data to move information, QA / QC before delivery, View for sheet production.

The ribbon's long tooltips are a mini manual: hold the cursor over a button before opening it for the first time.

Undo always works: each action a tool performs on the model is a single named transaction, visible in Revit's undo history.

For any issue, note down the version (About) and attach the day's start-up log: those are the two pieces of information that speed up diagnosis.

Good to know

Only Revit 2022 to 2026 on Windows; each Revit year needs its own build (they are not interchangeable between versions).

The Reset View (View panel) and Bloat (QA / QC panel) buttons are visible but disabled: their tools have not been released yet.

Mold only works inside the Family Editor; in a project its button stays greyed out.

The Misc utilities and most tools require an open project; the hub warns with Open a project first if there is none.

The theme only offers Light and Dark modes; it does not automatically follow the operating system's theme.

The deployment script closes Revit (with confirmation, or without it using -Force): you cannot deploy with Revit open.

If a project's health store was created by a newer version of the suite, that session does not use it (it is recorded in the log once); the rest of the suite works normally.

The suite installs and loads as a complete package: installing individual tools separately is not supported.

FAQ 8 questions

The BIMIO tab does not appear in Revit. What should I check first?

Check that %AppData%\Autodesk\Revit\Addins\<your Revit year> contains the FJV.Tools.addin file and the FJV.Tools folder with FJV.Tools.dll inside. If the security warning appeared when Revit started and you chose not to load, restart and accept the load. If all of that is fine, open %AppData%\FJV\Tools\logs\suite-startup-YYYYMMDD.log and look for FAIL lines.

Why is the Mold button always greyed out?

Mold is a Family Editor-only tool. Its button lights up automatically when the active document is a family (.rfa) and goes back to grey in a project. This is the designed behaviour, not an error.

Can I install just one of the tools, for example only Relay?

No: BIMIO deploys and loads as a single package with one manifest. In return, each tool starts individually protected, so if one were to fail to load it does not affect the rest, and the ones you do not use simply take up nothing more than their button.

Does BIMIO send data outside my machine?

No. The logs, the per-project activity store and the Health dashboard are local files in your user profile. The only external communication is the voluntary feedback submission from the About window, which you initiate expressly.

How do I update the suite to a new version?

The same way you installed it: build the configuration for your Revit year and run tools\deploy-lens.ps1 (or copy the new FJV.Tools folder and the manifest over the existing one). The script closes Revit, replaces the whole folder and verifies the critical files. Then check the version in About. If you installed BIMIO with the MSI, just run the newer installer: it upgrades the previous version in place.

I have Revit 2024 and 2025 on the same machine. Can I use BIMIO in both?

Yes. Each Revit version has its own per-year add-ins folder, and BIMIO produces a specific build for each one (R24 for 2024, R25 for 2025). Deploy both with -Years 2024,2025 and each Revit will load its own.

Can I launch the tools from the keyboard?

Yes. Every BIMIO button, including the items inside the Misc panel drop-downs, is an individual Revit command, so you can assign shortcuts from the standard Keyboard Shortcuts dialog (type KS in Revit).

In some files and logs I see the name FJV instead of BIMIO. Is that normal?

Yes. BIMIO is the product name you see on screen (tab, windows, reports). Internally, the code, the DLLs and some data folders keep the technical FJV prefix; that is why the logs live in %AppData%\FJV\Tools\logs and the DLLs are named FJV.*. It is just internal nomenclature.