# Overview **BIM Climate Action Tool (bimCAT)** is a free and open-access Revit plug-in that supports the export of material quantities from Autodesk Revit to Web App and allows synchronization between them. It is powered by the bimCAT database and enables users to select materials based on project needs, assess embodied carbon reduction opportunities, and produce charts and reports from within Revit. Download BIM Climate Action Tool (bimCAT) from Autodesk App Store Download BIM Climate Action Tool (bimCAT) Community Edition **BIM Climate Action Tool (bimCAT)** gives you a fully functional CQD inside your Revit project. * Export material quantities from Revit into Web App * Identify each material (concrete, steel, gypsum…) * **BIM Climate Action Tool (bimCAT)** starts you with a reasonable guess * User should refine each material search * Evaluate climate impact based on product specific 3rd party verified EPDs. * Visualize hot spots and biggest carbon reduction opportunities * Generate graphs and reports * Synchronize between Revit and the bimCAT model in the web * Annotate your Revit model & components so you can reuse your work * Save libraries of materials and assemblies for future use **BIM Climate Action Tool (bimCAT)** currently supports **Revit 2021-2025**. To install, download the MSI and double-click the file to install it. We expect **BIM Climate Action Tool (bimCAT)** will also be available shortly from the Autodesk app store. *bimCAT is a free sustainability plugin from bimCAT Carbon Action Technology Society, a British Columbia environmental nonprofit.* · *Software development by C-Change Labs, Inc. found at c-change-labs.com* · *Developed in partnership with* [*Perkins+Will*](https://perkinswill.com/)*,* [*Autodesk*](https://autodesk.com)*, and* [*Building Transparency*](https://www.buildingtransparency.org) · *Library Browser original design courtesy of the Design Technology Team at ZGF Architects* · *tally® original design courtesy of KT Innovations* We gratefully acknowledge the financial support of the [Province of British Columbia through the Ministry of Energy, Mines and Low Carbon Innovation](https://www2.gov.bc.ca/gov/content/governments/organizational-structure/ministries-organizations/ministries/energy-mines-and-petroleum-resources), which made creation of this tool possible.

## Feedback You may be familiar with Web App’s purple Report Bugs & Feedback button, but there is a second bug reporting path inside Revit, which helps us troubleshoot issues in the Revit environment. See [Report a Bug](/user-manual/usage/help/report-a-bug) section for details. # User Manual

This document describes version [1.7](/release-notes) of the **Building Information Model Climate Action Tool (bimCAT)**, built by [C-Change Labs](https://www.c-change-labs.com/en/) for [Autodesk](https://www.autodesk.com/). * [Installing the BIM Climate Action Tool (bimCAT)](/user-manual/installation) * [Using the BIM Climate Action Tool (bimCAT)](/user-manual/usage) * Technical Details. # Installation ### **Download the Plugin** Building Information Model Climate Action Tool (bimCAT) is delivered as an **msi** installer for Windows. It comes in two versions: * [BIM Climate Action Tool (bimCAT)](/user-manual/installation/tally-climate-action-tool-tallycat) * [BIM Climate Action Tool (bimCAT) Community Edition](/user-manual/installation/tally-climate-action-tool-tallycat-community-edition) Only one of them could be installed on your PC at a time. In terms of functionality, the only difference between them is the **About** window and the source of update. Also, **BIM Climate Action Tool (bimCAT)** always installs on the per-machine basis while **BIM Climate Action Tool (bimCAT) Community Edition** allows you to choose the installation scope. If you right-click the MSI installer of either plugin version and view its properties, you may find the version number in the **Details > Subject** field.

**Close Revit before installing** Please make sure that the Autodesk Revit application is not running while you are installing the plugin! **Install the plugin** Open the .msi file to start installation. ![](/files/pxwAqyLYiN0SDWlzOcsx) ![](/files/bnL1WbuXUHn1lxdOuqME) The installation currently offers Revit 2025, Revit 2024, Revit 2023, Revit 2022, Revit 2021 versions of the plugin; choose the version of Revit you are using.

The installer is **signed**, and the plugin is compatible with **Autodesk Store Bundle** format, so Windows shouldn’t display any warnings during the installation process or when Revit starts. **Uninstalling the Plugin:** BIM Climate Action Tool (bimCAT) will appear in the Windows Apps & features (Installed apps) screen, where you can uninstall it like any other application.

For documentation on exactly what the installer does see [Appendix 1: Installer](/user-manual/appendix-1-installer). # BIM Climate Action Tool (bimCAT) **Building Information Model** **Climate Action Tool (bimCAT)** can be [downloaded from the Autodesk App Store](https://apps.autodesk.com/ADSTPR/en/Detail/Index?id=8691868899675781155\&appLang=en\&os=Win64\&mode=preview). It is distributed in a form of an MSI installer **bimCAT\_installer.msi** It is always installed on per-machine basis and thus requires administrator's permissions for running.

If you attempt to install **BIM Climate Action Tool (bimCAT)** when [BIM Climate Action Tool (bimCAT) Community Edition](/user-manual/installation/tally-climate-action-tool-tallycat-community-edition) is already present on your PC, you'll get an error message and the installer will close.

When [checking for updates](/user-manual/usage/help/check-for-updates), this version of the plugin will look at the[ Autodesk App Store page](https://apps.autodesk.com/ADSTPR/en/Detail/Index?id=8691868899675781155\&appLang=en\&os=Win64\&mode=preview). You can check which version of the plugin is installed in the About window. The Autodesk App Store version will have the corresponding disclaimer.

# BIM Climate Action Tool (bimCAT) Community Edition **Building Information Model Climate Action Tool (bimCAT) Community Edition** can be [downloaded from the C-Change Labs website](https://www.c-change-labs.com/bimcat/about). It is distributed in a form of an MSI installer **bimCAT\_community\_installer.msi** It could be installed either on per-user or on per-machine basis. You can choose the scope during the installation.

If you're installing this version of the plugin using **scripts or the command line**, please note that by default it will install for the current user. To install it on the per-machine basis, please see the section [Administrative Installation](/tips-and-tricks/administrative-installation). If you attempt to install **BIM Climate Action Tool (bimCAT) Community Edition** when [BIM Climate Action Tool (bimCAT)](/user-manual/installation/tally-climate-action-tool-tallycat) is already present on your PC, you'll get an error message and the installer will close.

When [checking for updates](/user-manual/usage/help/check-for-updates), this version of the plugin will look at the [C-Change Labs website](https://www.c-change-labs.com/bimcat/about). You can check which version of the plugin is installed in the About window. The Community Edition will have the corresponding disclaimer.

# Usage This section describes how to use Building Information Model Climate Action Tool (bimCAT) in details and shows off some typical use cases. # Ribbon Panel Overview After the plugin is installed, start Autodesk Revit. Open a file in Revit that you would like to upload to Web App. Go to the **Add-Ins** tab. You should see the **BIM Climate Action Tool (bimCAT) ribbon**.

Currently, the ribbon consists of 5 buttons: **bimCATLibrary**, **Web Analysis**, **Sign In**, **Server Settings** and **Help**.

# Sign In The **Sign In** button allows a user to sign in to the EC3 Building Transparency service, which is essential for using most of the BIM Climate Action Tool functions.

This button has the same functionality as the [corresponding item](/user-manual/usage/tallycat-beta/sign-in) under the **Web Analysis** drop-down menu. # Server Settings You can choose the Web server by clicking the active server name on the ribbon.

Currently the following default options are available: * [buildingtransparency.org](https://buildingtransparency.org/) * [amazon.buildingtransparency.org](https://amazon.buildingtransparency.org/) * [disney.buildingtransparency.org](https://disney.buildingtransparency.org/)

If you like, you may add a custom server to the list by clicking the **Add Server...** button.

Upon clicking it, the corresponding dialog will appear where you may enter the server address. The **https\://** prefix could be omitted.

Currently only custom servers from the following domains are allowed: * **c-change-labs.com** * **buildingtransparency.org** * **enterprisetransparency.com** After clicking the **Add Server** button, **bimCAT** will try to connect to the server. If it fails, the corresponding error message will be displayed.

Upon success, the dialog will be closed and the new server will appear in the list.

You may delete a custom server by clicking the ![](/files/tj42dlTX6dXo3srhCEcR) button next to its name in the list. Deleting the default servers is not allowed. The chosen server is displayed on the ribbon next to its icon.

If you change the server while being logged in, BIM Climate Action Tool (bimCAT) will automatically log you out. # Help The Help section currently has the following items:

#### **bimCAT beta Manual** Opens this manual in the default system browser.

#### **Revit Naming Guidance for Web App** Opens the Revit material naming guidance which helps to improve automatic material detection on Web App for a particular project.

#### **Report a Bug** Brings up the bug reporting dialog. More on it in the [Report a Bug section](/user-manual/usage/help/report-a-bug).

#### **Check for Updates** Allows checking for the plugin’s updates. More on it in the [Check for Updates section](/user-manual/usage/help/check-for-updates).

#### **Release Notes** Shows what’s new in the latest version of bimCAT.

#### **About bimCAT beta** Shows an about window with basic plugin information. * [BIM Climate Action Tool (bimCAT)](/user-manual/installation/tally-climate-action-tool-tallycat)

* [BIM Climate Action Tool (bimCAT) Community Edition](/user-manual/installation/tally-climate-action-tool-tallycat-community-edition)

# Report a Bug Upon encountering a bug, error or crash you could file a bug report to the C-Change Labs Support Team. To do this, go to **Help > Report a Bug** command in the bimCAT ribbon.

In the Bug Report window, click the **Generate logs** button and choose the resulting zip-file location.

After the logs are generated, Windows Explorer will open automatically highlighting the created zip-file.

Now you could click the URL in the **Report a Bug** dialog which will create an email in your default email client. Then you could describe your issue in the email, manually attach the logs zip-file you just created and send it to the C-Change Labs Support Team ().

![](/files/NJwug8UfcgrQw89hTLOa)

The following kinds of data are included in the logs: * **BIM Climate Action Tool (bimCAT) logs**: the plugin and Revit information, errors, etc.; * **BIM Climate Action Tool (bimCAT) export data**: the raw data acquired from a Revit project during an export - mainly, names and quantities or Revit elements and materials; * **BIM Climate Action Tool (bimCAT) Library Indexer logs**: the Library Indexer information, errors, etc. * **Revit journal files**. Apart from the **Report a bug** tool, you could find the BIM Climate Action Tool (bimCAT) logs in the following locations: * For **Revit 2025** version:\ **C:\Users\\\[UserName]\AppData\Local\C-Change Labs Inc\bimCAT\2025\Logs** * For **Revit 2024** version:\ **C:\Users\\\[UserName]\AppData\Local\C-Change Labs Inc\bimCAT\2024\Logs** * For **Revit 2023** version:\ **C:\Users\\\[UserName]\AppData\Local\C-Change Labs Inc\bimCAT\2023\Logs** * For **Revit 2022** version:\ **C:\Users\\\[UserName]\AppData\Local\C-Change Labs Inc\bimCAT\2022\Logs** * For **Revit 2021** version:\ **C:\Users\\\[UserName]\AppData\Local\C-Change Labs Inc\bimCAT\2021\Logs** # Check for Updates Building Information Model Climate Action Tool (bimCAT) automatically checks for updates on Revit startup. If an update is found, the plugin displays the following window.

To install: * Follow the URL to the download location and download the plugin installer. * Close Revit. * Double-click on the installer to update the plugin. The same check could be performed manually through the **Help > Check for Updates** command in the Building Information Model Climate Action Tool (bimCAT) ribbon.

If an update was found, you'll see the same prompt as above.

If not, you'll be informed that bimCAT is up to date.

# Web Analysis **Web Analysis** is the main drop-down menu which contains all the bimCAT-related plugin commands.

When the user is not signed in, it has just a single item, **Sign In**, as the other commands require successful login to the EC3 Building Transparency web service.

# Sign In First, you’ll need to log in to your web account. Either click the **Sign in…** button in the BIM Climate Action Tool (bimCAT) ribbon, or go to **Web Analysis > Sign in…**

Please note that the plugin requires [WebView 2 from Microsoft installed](https://go.microsoft.com/fwlink/p/?LinkId=2124703). If it’s not present on your PC, the following dialog will pop up.

Click Download & Install to automatically install missing components to your system. After the installation finishes, restart Revit. If you already have WebView 2, the plugin will start the login process. Starting from the BIM Climate Action Tool (bimCAT) v0.10, the plugin uses the **OAuth2 authentication**. This means that the plugin will use your default system browser for performing the login and then store your login credentials between Revit sessions, so you’ll no longer need to sign in on every Revit start. Upon clicking the **Sign in** button, the plugin will open your default system browser with the login form. Also, a progress dialog will be shown through the whole process of signing in, so you may cancel the login at any moment by either closing it or clicking the **Cancel** button.

You may either sign in by entering your login and password or use Google, Microsoft or LinkedIn login options. After signing in through the form, you’ll need to give the BIM Climate Action Tool (bimCAT) the required permissions by clicking the **Allow** button.

If everything went fine, the browser will display the following page and the progress dialog will close automatically.

Now, you can close the page in the browser and switch back to the Revit window where the bimCAT ribbon should change.

* The ribbon **Sign in…** button changed its icon and now shows the user's login.\ If you click it, you will be signed out after a prompt.\ ![](/files/ISzYtZEfmihpZST5GEDX) * Under the **Web Analysis** drop-down menu, the **Sign in…** command became **Sign out** and also changed the icon. If you click it, you will be signed out after a prompt.

* If the current Revit project doesn’t have a 3D view called **bimCAT**, the drop-down menu will show a command that creates one. This view will be used later for all the operations performed by BIM Climate Action Tool (bimCAT).

* If the **bimCAT** view is already created, the ribbon will show additional commands: **Export to Web App**, **Open in Web App**, **Manage Scope**, **Detach from Web App**, **Properties & charts** and **Export to JSON**. ![](/files/sUAbosuJin7zSKsymHKa)
Depending on whether the project was exported to Web App or not, certain options will be enabled or disabled. * You could click **Export to Web App** to start the export process instantly with the default settings, or you could go to **Manage Scope** to configure what’s exported first. * If you exit Revit and start it again, you’ll remain signed in. # Create bimCAT View The first thing you need to do to use Building Information Model Climate Action Tool (bimCAT) with the new Revit project after signing in is to create a **special bimCAT view**. Later it will be used for all the operations performed by BIM Climate Action Tool (bimCAT). After successfully signing in, go to **Web Analysis > Create bimCAT view**

After the view is created, BIM Climate Action Tool (bimCAT) will automatically make it active and open the **Manage Scope** window where you could configure what’s exported. More on it is in the [Manage Scope](/user-manual/usage/tallycat-beta/manage-scope) section.

You won’t see this command in the **Web Analysis** drop-down menu if a view with the name **bimCAT** already exists in the project. Please note, that **you cannot rename the bimCAT view**. If you attempt to do so, Revit won’t allow it and an error will be displayed. After clicking **Cancel** the view will revert to its original name.

Deleting the **bimCAT view** is permitted, but you’ll need to confirm this action first.

After the **bimCAT view** is created, the **Web Analysis** drop-down menu will change displaying additional commands.

If you click **Export to Web**, **Manage Scope** or **Export to JSON**, but the BIM Climate Action Tool (bimCAT) won’t be able to find the dedicated **bimCAT view** for some reason, the following warning will pop up.

If you choose Yes, BIM Climate Action Tool (bimCAT) will automatically create the **bimCAT view** and open the **Manage Scope** window. Otherwise, the warning will close and the bimCAT drop-down menu will revert to the initial state.

# Export to Web App / Synchronize with Web App If this is the first export of the current Revit to Web App, this command will be called **Export to App**.

Otherwise, it will be called **Synchronize with Web App**.

In any case, clicking it will start the export/synchronization process with the settings previously configured in the [Manage Scope](/user-manual/usage/tallycat-beta/manage-scope) dialog. Clicking the **Export/Synchronize** button in the [Manage Scope](/user-manual/usage/tallycat-beta/manage-scope) dialog will basically do the same thing. # Export / Synchronization Process If you’re exporting a new Revit project, its data will be collected from the revit model, analyzed, converted to the Web App Building Project format and uploaded to the server according to the selected scope. The newly created Web App building project will receive a version number **1**.

If you’re updating the existing building project, the plugin will collect all required data from the current Revit project, compare it to the selected building project and create a patch containing only the data that was changed on the Revit side (additional instances and materials, changed quantities, etc.) Then this patch will be applied to the existing building project. * Material refinements made on Web App will be preserved and the corresponding element masses recalculated using the new densities. New building elements and materials which were added on Web App will be retained as well as automatically added reinforcements. If the existing building element quantities or names were changed both in the Web App and Revit projects, the Revit changes will be prioritized. * During an update, the **Export Detail**, **Project Location** and **Web App's Project Name** settings will be taken from the existing bimCAT building project, so the user won’t be able to change them from the plugin. **Floors** and **Height** values will be also taken from Web App, as they were automatically calculated during the initial export and it’s highly likely the user would want to refine them. * During an update, the new supported Revit model categories selected in the **Manage Scope > Manage Categories** dialog will be added to the building project. * During an update, the supported Revit model categories unselected in the **Manage Scope > Manage Categories** dialog will be removed from the bimCAT building project together with all their building elements. * During every synchronization the plugin will check if the Revit project was changed since the last export. If yes, the version number will be automatically incremented by 1. If not, it will stay the same.

* After an update, the building project ID and URL will remain the same. See more details in the **Project update example** section below. The export progress and what exactly is currently happening will be shown in the special progress window.

You may cancel the process at any moment by either clicking the Cancel button or closing this window. If error 503 (service not available) occurs during the export process, the plugin will attempt to automatically reconnect three times in 10, 20 and 60 seconds. If all the reconnection attempts fail or other critical error occurs, the export process will stop and the error dialog will be displayed.

More detailed information could be retrieved from the **error log** created by the plugin. # Web App Export Results Overview After the export finishes successfully, the following report window will be shown.

You could view a more detailed CSV report by clicking the **Open report as CSV** button. ![](/files/H03K9NcJCPwpctEbQ1JQ) All CSV reports are automatically saved to the following location: * For **Revit 2025** version:\ **C:\Users\\\[UserName]\AppData\Local\C-Change Labs Inc\bimCAT\2025\Reports** * For **Revit 2024** version:\ **C:\Users\\\[UserName]\AppData\Local\C-Change Labs Inc\bimCAT\2024\Reports** * For **Revit 2023** version:\ **C:\Users\\\[UserName]\AppData\Local\C-Change Labs Inc\bimCAT\2023\Reports** * For **Revit 2022** version:\ **C:\Users\\\[UserName]\AppData\Local\C-Change Labs Inc\bimCAT\2022\Reports** * For **Revit 2021** version:\ **C:\Users\\\[UserName]\AppData\Local\C-Change Labs Inc\bimCAT\2021\Reports** Clicking the **Open in Web App**button will open the exported EC3 building project in the **Open in Web App** window which **could take a couple of seconds to fully load**.

* The **Project Name** field is filled with the name specified during the export. The project name specified by the user during the export. * The **Project address** is taken from the Location and Site settings in the Revit file and recognized by the Google Maps service. * The **preview** displays a screenshot of the bimCAT view at the time of the export. * Under the title there is also **the version number** incrementing during each update followed by the initial upload date. * In the **Building Classification** section the **Material Quantity Source** is set to **Revit Import**.

* In the **Floor Area** and **EC** sections below, the following fields are calculated: **Floor Area Below Grade, Floor Area Above Grade, Gross Floor Area, Floors, Height**, **Weight**, **EC Building Intensity (Achievable, Realized, Conservative), EC Building Total (Achievable, Realized, Conservative)**. * The **Floor Area Above Grade** is the total area of all Revit floor instances assigned to the levels above ground. * The **Floor Area Below Grade** is the total area of all Revit floor instances assigned to the levels below ground. * The number of **Floors** is the total number of unique levels above ground which have at least one floor instance assigned to them. * The **Height** is taken from the highest occupiable level in the building. ![](/files/r20q53R1tHDJUvjNHM6B) Below, the project data is structured hierarchically in two main views: [Revit View](/user-manual/usage/tallycat-beta/export-to-ec3-synchronize-with-ec3/ec3-export-results-overview/revit-view) and [Custom View](/user-manual/usage/tallycat-beta/export-to-ec3-synchronize-with-ec3/ec3-export-results-overview/custom-view). # Revit View In the Revit view, you can see various project’s families and elements sorted in alphabetical order and compressed according to the **Export Detail** setting.

Please note, that in Revit view the editing is restricted. You can refine the existing elements, change their quantities and add new elements, **but reorganizing the view is disabled**, so you cannot move the exported building elements between the labels. This is done to minimize potential issues during the bimCAT synchronization. If you need to reorganize the elements, please switch to the [Custom View](/user-manual/usage/tallycat-beta/export-to-ec3-synchronize-with-ec3/ec3-export-results-overview/custom-view), it allows to do it freely without any restrictions. All refinements done to the building elements are preserved across the [Revit View](/user-manual/usage/tallycat-beta/export-to-ec3-synchronize-with-ec3/ec3-export-results-overview/revit-view) and [Custom View](/user-manual/usage/tallycat-beta/export-to-ec3-synchronize-with-ec3/ec3-export-results-overview/custom-view). Revit elements are exported as multi-material bimCAT building elements, each sub-element representing a material or a layer. Besides the material sub-elements, their total quantities are shown. ![](/files/gvlTefNDW0Wsx8LuWjrk) By default, formulas are used to specify the quantities of both parent building elements and their sub-elements.

If the **Detect material type during input** option was selected in the [Manage Scope](/user-manual/usage/tallycat-beta/manage-scope) dialog, the materials are mapped to corresponding bimCAT categories. Items that failed to map display warnings in the Note field. ![](/files/ZhBBRe3Fqp84Z1Xlu6tz) Revit elements do not typically contain reliable mass information, so if an web collection requires mass, bimCAT has to calculate it by multiplying volume by density, where the latter is provided by the Web App. If a particular material’s mass was automatically calculated this way, the corresponding note will be added to the material. ![](/files/8OQwPvaTq1xCcVxQ5NMj) If Web App requires to provide the mass of a particular material but mapping doesn’t provide density, the plugin puts a formula with density placeholder into the quantity field and leaves a warning note, e.g., \_“*Web App\_is missing data for quantity, so it has inserted an incomplete equation like '1.23\*kg\_per\_m3'. In this example,* Web App *needs a mass, currently only has volume.* Web App *needs you fill in the placeholder (kg\_per\_m3) with a number (e.g. density in kg/m3) or simply fill in the correct total, so the equation looks like '1.23\*10' or '12.3'.”* ![](/files/WO2Ha3P73Aok4vuU8O5n) A building element corresponding to a Revit family type will typically have a name in the following format: ***Revit Family Name***: ***Revit FamilyType Name \[Type Mark]*** If a Revit project contains Type Mark data for a particular family type, it will be put into square brackets and added at the end of the name of the corresponding building element on Web App.

If the combined name exceeds the Web App limit of 250 characters, it will be shortened to fit. Revit curtain elements (Curtain Panels and Curtain Wall Mullions) will be exported together with the information about the elements they’re included in. You can read it in the Note field.

If a particular Revit family type has a layered structure (wall, floor, ceiling, etc.), the layer order will be preserved in the building project. The name of a material element representing a layer is prefixed by the Revit layer **Function** put in square brackets if available. Also, if multiple layers consist of the same material, they will be shown in Web App as separate elements. Their quantity will be calculated using each layer width and the parent element area. ![](/files/ec6M9LTxytLQG1RmKWDb) Please note, that the **units** of elements and materials in the resulting the building project are based on **display units** set in the Revit project from **Manage > Settings > Project Units**. ![](/files/349TW1DNMkfxHbZQrBhf) Whichever units for **volume**, **area, length** and **mass are** selected in Revit under **Manage > Settings > Project Units** will be used for calculating and displaying the amounts in Web App BuildingProject. |

| | ------------------------------------------------------------------- | ------------------------------------------------------------------- | During the **export/synchronization**, BIM Climate Action Tool (bimCAT) adds data to the Revit model (in extensible storage) linking it to the building project, storing information about material categories & specs, and basic climate change data. Thus, after the export finishes, it will prompt you either to save the Revit project (if it doesn’t have a central model) or to synchronize it with the central model. # Custom View The **Custom View** is automatically created along with the [Revit View](/user-manual/usage/tallycat-beta/export-to-ec3-synchronize-with-ec3/ec3-export-results-overview/revit-view) during the [Web App Export](/user-manual/usage/tallycat-beta/export-to-ec3-synchronize-with-ec3) In a nutshell, it's a carbon copy of the **Revit View** with additional benefits. The **Custom View** initially has the same hierarchical structure as the **Revit View**.

All building element refinements which could be done in the **Revit View** are available here as well. These changes are preserved across the **Custom View** and the **Revit View**. Although the **Revit View** is very restricted in terms of reorganizing the data, in the **Custom View** you're free to move the building elements between the labels however you like.

These view organization changes will not affect the **Revit View** in any way. It will always preserve the strict bimCAT-compatible structure. Feel free to use the **Custom View** to organize the data for your convenience. # Web Builder Support After exporting a Revit project, Web App will attempt to detect which building elements could be refined by the **Web Builders**. These builders are a set of helper tools which allow you to automatically recognize and refine typical assemblies. For example, a single **Concrete** layer could be turned into **Reinforced Concrete**, a **Metal Stud** layer mass could be calculated according to its volume and other properties, etc. To use this feature, after opening an exported web project in a browser or using the [Open in Web App](/user-manual/usage/tallycat-beta/open-in-ec3) window, click the **Next Decision** button in the [Revit](/user-manual/usage/tallycat-beta/export-to-ec3-synchronize-with-ec3/ec3-export-results-overview/revit-view) or [Custom](/user-manual/usage/tallycat-beta/export-to-ec3-synchronize-with-ec3/ec3-export-results-overview/custom-view) view.

It will highlight the next element is proposing to apply a builder to.

For example, in this case it's a **Concrete** layer which could transformed into **Reinforced Concrete** by automatically adding a rebar. To do this, click the layer's quantity.

You will see two options: **Concrete By Area** and **Concrete By Volume**, so you can choose which dimensionality to use for this layer. After clicking either of them (for example, **Concrete By Volume**) the builder dialog will open allowing you to choose how to calculate the required amount of rebar for this element.

By clicking **Add Rebar By Concrete Volume, Add Rebar By Reinforcing Ration** or **Add rebar By Length**, you'll make the builder to automatically add a Rebar layer for the Concrete layer using the selected principle to calculate the quantity.

By clicking the **Accept** button you'll confirm the calculated quantities and get the reinforced concrete assembly.

The EC3 Builders could help with **Metal Stud** layers too. After the export, Web App often is unable to reliably calculate the quantity of such layer, because it lacks material density. In this case, instead of quantity, the **#VALUE!** error is displayed in the quantity filed.

After clicking the quantity field of such layer, you can apply the **Metal Stud** builder to it.

It will help to calculate the realistic quantity.

After clicking the **Accept** button, you will get the properly calculated **Metal Stud** layer.

Apart from proposing to apply a builder, the **Next Decision** button also highlights other problems in the project, like missing quantities or EPDs, lacking an accurate material category, etc. # Web App Project Sync Example Let’s see an example of the project update sequence to see how it works. First, let’s export one of the sample Revit projects **GSA Courthouse.rvt** The project units in the **Manage > Project Units** dialog are set as follows. ![](/files/6A55UsL1TKWBe3cskfTA) ![](/files/fUU4DRFTlTvDbh6xo2IQ) Let’s click [**bimCAT > Manage scope**](/user-manual/usage/tallycat-beta/manage-scope) and perform a new export with **Export by Family Type** detail.

After the export finishes, the **Roofs** category of the corresponding web building project will look as follows. ![](/files/g4EE2pQbjEEiT2YZog7b) Let’s focus on it and slightly adjust the **Basic Roof: Insulation on Metal Deck - EPDM** element. Let’s refine the material of **Metal - Deck** element: * Change the name to **Metal - Structural Deck** * Click the Refine button and change the material to **Steel > Structural Steel** * Change the quantity formula to **0.125\*10 (\~1.3)** and the unit to **lb** * Change the note to ‘**Updated by John**’ ![](/files/8ed5ddo8fPiW1L8WKXy5) Now, let’s add a new material **Aluminium Sheet** to the **Basic Roof: Insulation on Metal Deck - EPDM** element: * Name: **Aluminium Sheet** * Quantity: **10.5 lbs** * Collection: **AluminiumSiding** And, finally, let’s add another building element Panel Roof under the Roofs category: * Name: **Panel Roof** * Quantity: **2900 m2** * Collection: **RoofPanels** ![](/files/iaA360nl8OsE0VEqU9YE) Please note, that these two items didn’t previously exist in the Revit project. Now let’s save the web building project and switch back to the corresponding Revit project to make some adjustments as well. In the Revit project, let’s double the quantity of **Basic Roof: Insulation on Metal Deck - EPDM** we just edited on the Web side. Go to **Project Browser > Families > Roofs > Basic Roof**, right click the **Insulation on Metal Deck - EPDM** element and choose **Select All Instances > Visible in View.** ![](/files/7eLg0jus1XhNzLUBMVhi) Then just **copy and paste the selection** anywhere in the project to double the quantity of this roof. Then go to **Project Browser > Families > Roofs > Basic Roof**, right click the **Insulation on Metal Deck - EPDM** element, and choose **Type Properties.** ![](/files/EvX3dIoTok9x5WAc3CJK) Go to **Structure > Edit…** and make the following changes: Also, go to **Project Browser > Families > Roofs > Basic Roof**, right-click the **Generic - 18’’** element, choose **Create Instance** from the menu and draw a roof.

![](/files/LDR7tbXhiN2mWK5W0D60) Select the roof you just created, click **Edit Type > Structure > Edit…** and change its material to **Plastic** with the width **5’ 7’’**.

Now, let’s click [**tallCAT > Synchronize with Web App**](/user-manual/usage/tallycat-beta/export-to-ec3-synchronize-with-ec3).

After the export finishes, click [**Open in Web App**](/user-manual/usage/tallycat-beta/open-in-ec3) in the result dialog.

**The updated web building project has the same ID and is accessible using the same URL.** Let’s compare the old and the updated web building projects. **The old web building project:** ![](/files/hCSkv3rE3UlqXVxa7KL1) **The updated web building project:** ![](/files/P6NT1dUXnRQ3qARSGcGv) Here are the results of updating the project which was changed **both on Web and Revit** **sides**: * The quantity of the **Basic Roof: Insulation on Metal Deck - EPDM** has increased considerably. * The **GWP Realized** value has increased too as the result of copy/pasting the existing roof in Revit. * **Metal - Structural Deck** retained the new Web App name, the updated StructuralSteel category and the note. The quantity formula was also taken from the Web App project and retained, regardless of the changes in the Revit project. * The **Aluminium Sheet** material and **Panel Roof** building element previously added on the Web App were retained during the update. * The **Vinyl** material and **Basic Roof: Generic - 18”** element added in Revit were created on the Web App during the update. * The rest of the materials which existed in the previous export were left as they are with their quantities, collections and units preserved. We hope that this little example helped you to understand how the update feature currently works. # Open in Web App After a Revit project is successfully exported to Web App, you can open it in the Web Building Planner directly from the plugin and perform a number of interactions between the building project and the Revit 3D model. To do it, click the **Open in Web App** item in the **bimCAT** drop-down menu.

The following window will open side by side with the main Revit window, showing the exported project in the embedded browser, where you can perform any actions available from a regular web browser.

Additionally, in the Web Building Planner shown in the Open in Web App window you may see **small checkboxes** near building elements.

Checking them will allow you to perform a couple of interactions between the Building Planner and the Revit 3D model using the tools from the Open in Web App window’s toolbar.

The ![](/files/harXkznanTu59ShYIIhf) button opens the Revit 3D view associated with the current building project. Typically, it’s the **bimCAT** view. If it was removed from the Revit file, an error message will appear.

The ![](/files/1HBlPkl7Td9k5N2G92yD) button will immediately start the synchronization process. If the web building project has any unsaved changes, it will be automatically saved after clicking this button. The ![](/files/jMxZrWSbVh5r4u2UFS3n) button produces a small tip on how to use the **Open in Web App** tools.

Finally, clicking the ![](/files/ZGC9sPfoNERyJ2s4BbhV) button will put the **Open in Web App** window always on top. Afterwards the button will change into ![](/files/g37KmIFNCfuWn8rK65Wq) Clicking the button one more time will restore the default behavior. By using the tools from the **Select** tab you can select elements from the Revit 3D model which correspond to the building elements checked in the web Building Planner. * Click ![](/files/WIhQ8M9TBf3XLbsGlyNx) to select the Revit elements checked in the Building Planner.

* Click ![](/files/vnfu2EueDUhzVynB0Hwt) to temporary hide/isolate the Revit elements checked in the Building Planner.

* Click ![](/files/LxR02gvITrTi4YJfMfB4) to clear the selection or exit the temporary hide/isolate mode.

By using the tools from the **Visualize** group you can apply various color filters to elements from the Revit 3D model which correspond to the building elements checked in the Web App's Building Planner. * From the dropdown list in the **Visualize** tab, select the **Highlight Selected Items** option. It will instantly switch to the temporary Revit view and color Revit elements selected in the web Building Planner yellow while making all the rest transparent. If you continue checking and unchecking the checkboxes in the Building Planner, the elements in the Revit view will be colored/cleared instantly.\ Upon closing the Open in Web App window or switching to the Select tab, all coloring will be discarded and the temporary view turned off.

* From the dropdown list in the **Heatmap** tab, select the **GWP Savings Potential** option. It will instantly switch to the temporary Revit view and color Revit elements selected in the Web App's Building Planner according to their GWP savings potential while making all the rest transparent. The legend is displayed in the same Heatmap tab. The GWP savings potential is calculated using the formula:\ **(realized - achievable) / conservative**\ If you continue checking and unchecking the checkboxes in the Building Planner, the elements in the Revit view will be colored/cleared instantly. Also, you can refine materials in the Building Planner shown inside the Open in Web App window and the colors in the Revit model will be updated instantly.\ Upon closing the Open in Web App window or switching to the Select tab, all coloring will be discarded and the temporary view turned off.

If you open a new Revit document while the Open in Web App window is displayed, it will either automatically load the corresponding web building project if the one exists, or close if it doesn’t. Also, if the existing web building project contains any unsaved changes, it will be automatically saved before reloading/closing. The ![](/files/0mYEsxymPtSCLSxy6XYz) tools at the bottom of the **Open in Web App** window allow zooming the Building Planner in and out. Click to zoom out and to zoom in. The default zoom factor is **75%.**

The minimum is **33%**

The maximum is **100%**

Please note the horizontal scrollbars which will help you to access building element data not fitting into the window. Clicking the zoom factor indicator resets the zoom factor to default **75%** ![](/files/kUgKvnVwMD5OMRmQ4vLZ) Also, if you open the web Builder dialog either by clicking the bimCat Mapping button or the small calculator button near the building element, the corresponding Revit items will be highlighted in the Revit view.

If a project was exported but then deleted on Web App, clicking the **Open in Web App** item will pop up the following dialog instead: ![](/files/bOAZ7p4FoV7XZpV2WsQu) Clicking **Yes** will open the Manage Scope dialog. If you click the ![](/files/wLsVHFDyUUDfGpxWBEQN) button of the **Open in Web App** window when the currently opened web building project has any unsaved changes, the **Open in Web App** will prompt you to save the document before exit.

# Manage Scope After the bimCAT view is created, the **Manage Scope** window will automatically pop up.

Also, it could be opened from the bimCAT drop-down menu.

This window allows you to configure various export options and then perform an export or synchronization with an existing web building project. The **Manage Scope** window will look different depending on whether the current Revit project was exported to Web App or not. # New Web App Export If a Revit project is exported for the first time, the **Manage Scope** window will look as follows.

* **Web App Project Name** - allows to set the name of the web building project associated with the current Revit project. By default, the name is the title of the current Revit project. * **Web Folder** - allows you to select or create an Web folder to export your project to.\ By default, the project is exported to My Buildings. However, by clicking the open folder button, you could bring up the Select Web Folder dialog and change the export location. * ```

``` The dialog allows you to either choose an existing folder, or to create your own folder or super folder by clicking the corresponding buttons.

Super folders have a special double folder icon and their names are written in bold.\ Please note that you can export your project either to My buildings, or to folder, but not super folder. However, you can create a folder inside any super folder. * **Export Detail** - allows to specify the level of detail in the resulting web building project. Currently three levels are supported. * **Export by Family Type** (selected by default) * ```

``` ``` * Web App will create an entry (a BuildingElement) for each **Revit Family Type**. * The quantity totals take any cutouts and overlaps into account, so the amount of material per unit of the family type may be slightly lower than nominal. * The Web Revit tab will be organized by Revit Category. * Each Building Element contains a Material for each layer described in Revit. ``` Below’s an example of **Export by Family Type** result: ![](/files/wqQ3aBuYKrlqveXHJATf) * **Summarize Repeated Families**

* Web App will create an entry (a Building Element) for each Revit Family Type, but will **combine family types with almost identical quantities**, identical materials, and identical type marks and assembly codes. * This setting is useful for modular designs where the Revit Family gets duplicated in each repeat of a module. * The quantity totals take cutouts and overlaps into account. * The Web Revit tab will be organized by Revit Category. * Each Building Element contains a Material for each layer described in Revit. Below’s an example of **Summarize Repeated Families** result. ![](/files/QPzW1c9xIX2DP3Z2WPld) * **Summarize Families with Same Materials**

* Web App will create an entry (a BuildingElement) for each group of Revit Families/Types in the same Revit Category with the same **list** of materials inside. * Multiple Revit Families are summarized together. * The amounts of each material are totaled across all the instances. * The Web Revit tab is organized by Category. * Each BuildingElement contains a Material for each layer described in Revit. Below’s an example of a **Summarize Families with Same Materials** result. ![](/files/WjLgR94cobzdWVi7rUVk) * **Detect material type during input** - this checkbox specifies whether the Web App should try to detect Revit materials and map them to the web collections automatically. * If the checkbox is set, the Web App will try to create collections for all Revit materials upon the export. Material quantities will be set according to the collection requirements. ![](/files/MZcsLtC1h8CeEO0LFDn4) * If the checkbox is not set, the Web App will leave the collections empty for the user to choose them manually. The material quantities will be set according to the following rule: * If two dimensions of the corresponding Revit element’s bounding box are < 10 cm, the **length** is used. * If the material layer thickness is < 10 cm, or one dimension of the corresponding Revit element’s bounding box is < 10 cm, the **area** is used. * In all other cases, the **volume** is used. ![](/files/68yb8jp9vzFL3KExneuL) Please note that exported Revit elements having the bimCAT back-annotations will be automatically mapped to the web collections corresponding to their back-annotations regardless of whether the checkbox was set or not. * **Categories Exported** - displays the list of exported categories and allows you to change it by clicking the **Manage Categories** button. It will bring up the Revit **Visibility/Graphic Overrides** window. The categories not currently supported by Tally Climate Action Tool (tallyCAT) will be unselected by default, and selecting them will have no effect. Currently the following categories are supported: **Ceilings, Columns, Curtain Panels, Doors, Floors, Roofs, Stairs, Structural Columns, Structural Foundations, Structural Framing, Walls, Windows**.

* **Cannot Be Exported -** if any selected categories are not currently supported by bimCAT for export to Web App, then they are listed here. These categories will not be sent to Web App, but will remain visible in the bimCAT view. * **Project Location -** allows to specify web building project location. During the new export, this field is always filled with the **latitude and longitude** taken from **Manage > Project Location > Location and Site** Revit dialog. You can bring this dialog up by clicking the **Modify Location** button and adjust the location. After an export, Web App will use the latitude and longitude to obtain the human-readable address using the Google services.

* Clicking the **Export** button will start the [export process](/user-manual/usage/tallycat-beta/export-to-ec3-synchronize-with-ec3/export-synchronization-process) with chosen settings. # Updating an Existing Web Building Project If the selected Revit project was already exported to Web App, the **Manage scope** dialog will look a bit different.

* **Web Project Name** - displays the name of the web building project linked to the current Revit project and the date of the last update. In this case, the name couldn’t be changed from the plugin. To edit it you’ll need to open the project in Web App. * **Web Folder** - show the web folder the project was previously exported into. * **Export Detail** - displays the level of detail which was used to export the current Revit project for the first time. On update this setting cannot be changed. * **Detect material type during input** - this checkbox specifies whether the Web App should try to detect Revit materials and map them to the web collections automatically. For additional details, see the [New Web App Export](/user-manual/usage/tallycat-beta/manage-scope/new-ec3-export) section. * **Categories Exported** - displays the list of exported categories and allows you to change it by clicking the **Manage Categories** button. For additional details, see the New Web App Export section. If new supported categories were selected during an update, their elements will be added to the existing web building project. If during an update you uncheck some of the categories added to the web building project during the initial export, they will be removed from the web building project together with all building elements. * **Cannot Be Exported -** if any selected categories are not currently supported by bimCAT for export to Web App, then they are listed here. These categories will not be sent to Web App, but will remain visible in the bimCAT view. * **Project Location** - displays the location of the web building project linked to the current Revit project. After the initial export Web App used the latitude and longitude to obtain a human-readable address through the Google services. During the update this value cannot be changed from the **Manage Scope** dialog. To edit it you’ll need to open the project in Web App. * **Reset to Default** - this button allows you to reset the bimCAT view settings to default. This mainly includes the list of exported categories.

* Clicking the **Synchronize** button will start the [synchronization process](/user-manual/usage/tallycat-beta/export-to-ec3-synchronize-with-ec3/export-synchronization-process) with chosen settings. # Detach from Web App After successfully exporting a Revit project to Web App, all the following uses of Synchronize with Web App or Manage scope commands will result in updating the existing web building project. If you need to create a new web building project from the current Revit project with no information about previous update history, you’ll need to use the **Detach from Web App** command.

This will break the connection between the current Revit project and related web building project without deleting the latter, and you’ll be able to export the Revit project to a brand new web building project. After clicking the **Detach from Web App** command, you’ll see the following prompt.

After choosing **Yes** the link will be broken and the **bimCAT** menu will revert to the default state. The next export will create a new web building project with the version number 1.

When detaching a Revit project from Web App, BIM Climate Action Tool (bimCAT) removes data from the Revit model (in extensible storage) linking it to its former web building project, information about material categories & specs, and basic climate change data. Thus, after the detaching finishes, it will prompt you either to save the Revit project (if it doesn’t have a central model) or to synchronize it with the central model. # Properties & Charts Once a project is exported to Web App, the corresponding JSON is retrieved from the service and saved in the Revit project file using Revit Extensible Storage. Later it could be viewed in user-friendly format using the **Properties & charts** command. To open it, click the corresponding item in the **bimCAT** drop-down menu.

The project browser window will appear.

The building project structure is displayed in the left pane. By expanding various items the user can browse Categories, Families, Elements and Materials.

The selection of a particular material in the tree will bring its statistics to the right pane.

There the user could see basic material information and embodied carbon data along with a simple GWP chart. All quantities are calculated according to the display units the user selected in the Revit project settings. # Export to JSON After you logged in, you could export a project to a JSON file. To do it, click the **Export to JSON** item in the **bimCAT** drop-down menu.

You’ll see practically the same wizard as with the [**Manage Scope**](/user-manual/usage/tallycat-beta/manage-scope) command.

After clicking the **Save as** button you’ll see the file selection dialog. ![](/files/tAcp9AZuAEHyKiGjWpT3) After choosing the save location and clicking **Save**, the export process will start.

The only difference is, this time the project won’t be sent to Web App. Instead, it will be saved to the selected file in JSON format. You may cancel the process at any moment by either clicking the Cancel button or closing this window. Once the export finishes, the Export Summary dialog will be shown.

You could view a more detailed CSV report by clicking the **Open report as CSV** button. Clicking **View the project JSON** in the same window opens the resulting JSON in the default text editor. ![](/files/8TzpSvmUjdqXTiVH1vSo) This is precisely the same JSON that would’ve been uploaded to Web App if you had chosen the [**Export to Web App / Synchronize with Web App**](/user-manual/usage/tallycat-beta/export-to-ec3-synchronize-with-ec3) command. It could be used to check if the raw data is correct. # bimCAT Library The **bimCAT Library** command allows access to a library of various Revit family types. These types could be annotated with the bimCAT data allowing to maintain user-refined collections and bimCAT builder data between different projects. These bimCAT back-annotations are automatically created during the Export and updated during each Synchronization for every exported family type. Basically, the back-annotations contain information about bimCAT collections assigned to every exported Revit material, building elements created only on the Web App, builders, etc. This data is later used by bimCAT to restore collection refinements and builders when Revit elements of the corresponding family types are exported from other projects or during the new export of the same project. The Library Browser allows users to create new libraries, export both system and loadable family types to RFA and RVT files, put them to existing libraries and import family types from a library to another Revit project.

After clicking the corresponding item in the ribbon, the following window will appear.

The window has two tabs: **Current Project** and **Library**. # Current Project The **Current Project** tab lists all family types existing in the current Revit project.

**Category, Family** and **Type** columns display the corresponding Revit information. The **Document** column is only displayed when the current Revit document has linked models and displays the name of the main or linked document where the selected family type belongs to. The **Revit Version** column shows off the Revit document version. **Loadable** shows whether a family is loadable or not (system). If elements of a family type were already exported to the Web App, the corresponding back annotations will be added to the family type. The **Web App** column shows whether these annotations are present. If that’s the case, the **Unit** column will display the quantity unit assigned to the family type on the Web App, and GWP Achievable and GWP Conservative columns will show off the approximate GWP values for 1 unit of this family type (calculated using the Revit material data and the bimCAT material statistics). Upon clicking a particular row in the data grid, you’ll be able to see more detailed information about the corresponding family type in the right pane. It includes a **preview image**, **Category**, **Family**, **Type** and **GWP data**. Also, the **Annotation** text box displays the list of materials or material layers of the family types together with bimCAT material search information. Clicking the **View All** link opens the **bimCAT Properties Viewer** which shows the complete bimCAT back annotation in JSON format.

Clicking the small magnifying glass icon in a column header brings up the filter, where you can configure elements visibility in the data grid. More than one filter could be applied.

The toolbar above the data grid hosts a number of buttons which allow you to perform various actions on project family types. Most of them become enabled when data grid items are checked using the checkboxes in the first column. # Place The **Place** button works with the item currently highlighted in the data grid ignoring the checkboxes. Allows to place an instance of the chosen family type to the current Revit view.

# Add to Library The **Add to Library** button becomes available when one or more items are checked using the checkboxes.

Upon clicking, opens the **Add to Library** dialog allowing to add the checked items to one the existing user’s libraries.

After selecting a library from the list and clicking the **Add Family Types to Library** button, the confirmation dialog will be displayed, where you could skip certain items or rename them if you like.

After clicking the **Confirm** button the items will be added to the chosen library.

You could see them in the [Library tab](/user-manual/usage/library-browser/library).

Both the **loadable** family types (Doors, Windows, Columns, etc.) and the **system** family types (Walls, Ceilings, Floors, etc.) are added to the library as separate entities, without exporting their whole family. # Remove bimCAT Data The **Remove bimCAT Data** button becomes available when one or more items are checked using the checkboxes. Allows to remove the bimCAT back annotations from the checked items. Before:

After:

If the selected family types are located in linked models, upon clicking the **Remove bimCAT Data** button a save prompt will be displayed.

# Save As... The **Save As…** button becomes available when one or more items are checked using the checkboxes. Allows to save checked family types to files. * The **loadable** family types (Doors, Windows, Columns, etc.) are saved to the **RFA** format, **one family type per file**. * The **system** family types (Walls, Ceilings, Floors, etc.) are saved to the **RVT** format, **one family type per file**. Here’s an example of using this function. Let’s assume that the following family types are checked.

Clicking the **Save As** button will produce the destination folder selection dialog.

After picking a folder and clicking the **Select Folder** button, the export process will start.

Upon its completion, the summary dialog will appear.

The destination folder with the exported items will be automatically shown in the Windows Explorer.

For each Wall family type a separate RVT file was created even though they all belong to the same Basic Wall family. In a similar way, each loadable family type was exported into an individual RFA file, even if originally a few of them belonged to the same family. As in the case of RFA files the file name corresponds to the family name, bimCAT has put all RFA files into dedicated folders to not create naming conflicts. # Scan for Updates The **Scan for Updates** function allows to check all family types in a Revit project and its linked documents for their updated versions in all connected libraries. It doesn't depend on the selection in the Library Browser, all existing family types are checked.

When looking for an update for a particular Revit project family type, bimCAT will check if an element with the same Revit category, family name and type name exists within the library and its last updated date is later than the one of the project family type. If such element is found, it is considered to be an update. If no update is found, the corresponding message will be shown.

If updates were found, the comparison window will appear.

In the upper part of the window, under the **Project Family Types** title you will see the list of family types both from the current Revit project and its linked models for which the updates were found. By checking the checkboxes, you may select them for update. The orange question mark in a family type row means that this family type has more than one matching update in the library, so the user has to pick one in the lower portion of the window, under the **Library Family Types** section. Once the family type update is selected, the question mark will go away.

You can compare the family type properties by reviewing both tables and the details pane on the right. To compare the bimCAT back annotation JSONs, you may click the **Compare** button.

This will bring up the bimCAT back annotation comparison window.

No orange question mark in a project family type row means that either there's only one matching update in the library, or the update was already selected by the user.

If you select the row with the orange question mark for update without explicitly selecting an update from the available updates list, bimCAT will automatically choose the first option. After clicking the **Update X Family Types** button, the confirmation screen will appear where you could verify your selections.

After clicking the **Confirm** button the updates will be applied to the project. If some of the family types being updated are located in linked models, additional prompt will be displayed. ![](/files/AU9IWzJsQHqPjy5Glosd) Updating family types could take some time, especially if they're located in linked models. Once the process is completed, you can view the updated family types in the [Current Project](/user-manual/usage/library-browser/current-project) tab.

# Library The **Library** tab lists all family types in the user's libraries. If no user library exists upon opening the Library Browser, bimCAT will automatically create the **Default** library and populate it with a few test items. By default, this library will be created in the following location:\ C:\Users\\\[UserName]\AppData\Local\C-Change Labs Inc\bimCAT \Libraries\Default In the filesystem a library is a folder containing various RFA and RVT files hosting Revit family types. It is indexed by a special **bimCAT Library Indexer** background application which stores the collected data in a database from where the bimCAT Library Browser could read it. If for some reason no library currently exists, the **Library** tab will look as follows having only the **Add Library** button.

The **Add Library** button will bring up the Library Settings window where you could add a library. More information on it is provided below.

Otherwise, the fully functional **Library** tab will be displayed.

Here in the data grid, **the Category, Family** and **Type** columns display the corresponding Revit information. The **Version** column shows off the family type version. The **Library** column specifies the name of the library where each of the family types resides. If elements of a family type were previously exported to the Web App, the corresponding back annotations were added to the family type. The **Web App** column shows whether these annotations are present. If that’s the case, the **Unit** column will display the quantity unit assigned to the family type on the web App, and GWP Achievable and GWP Conservative columns will show off the approximate GWP values for 1 unit of this family type (calculated using the Revit material data and the bimCAT material statistics). The right pane displays the same family type information as the one in the Current Project tab. The data grid filters also work in the same way. The toolbar above the data grid hosts a number of buttons which allow you to perform various actions on project family types. Most of them become enabled when data grid items are checked using the checkboxes in the first column. # Manage Libraries The **Manage Libraries** button opens the **Library Settings** window.

Here you can view the existing libraries, their locations, the access level and the time of the last update of each library. By clicking the hamburger button next to a library, you can forget the corresponding library. Please note that in this case the library folder and its contents will remain on disk.

Also, here you can add a new library by clicking the **Add Library** button. Upon clicking, it will bring up the **Connect new library** dialog.

Here you can add a library from one of the sources. ### Local Local libraries are stored on your computer or company network drives. These can be used for personal, group or office libraries. After selecting the **Local** library source, the **Library Location** dialog will pop up.

Clicking the small ![](/files/unHu8BKIASvKaYDV9UQr) button will bring up the folder browser dialog. By default, it will look in the **C:\Users\\\[UserName]\AppData\Local\C-Change Labs Inc\bimCAT\Libraries** folder, but you may pick any other location.

You can either pick a local folder or specify a network location here. If the selected directory contains any RFA or RVT files, bimCATwill try to add them to the new library right away. If not, an empty library will be created which you could populate with content later. All the new library items will be copied to this location. After selecting a directory, you could also specify the new **Library Name**. It will be displayed in the **Library Settings** dialog and the **Library** column of the data grid.

After clicking the **Add Library** button, the bimCATLibrary Indexer application will analyze the library and automatically add all the family types it was able to locate inside. Please note, that every RFA file will be processed, but concerning the RVTs, the Indexer will only process the files which were previously prepared by the bimCAT. After the library is added, it will show up in the Library Settings window.

The **Location** here is set to **Local**, while the **Access** is set to **Manage**. The latter means, that the user could perform any operations with the library content: view, import, edit, add or remove items. All the family types found in the library folder will show up in the data grid together with the corresponding library name.

If the remote library is unavailable due to connection issues, the following message will be displayed in the **Access** column.

Also, the name of such library will be colored red in the **Library** table.

### bimCAT Library Open libraries hosted by bimCAT.org, containing pre-annotated families created by manufacturers and other professionals. This allows to add one of pre-configured remote libraries from the bimCAT servers.

After clicking **Connect**, the remote library will be added to the list.

Please note that the **Location** for the remote library is set to **Web** and the **Access** - to **Read**. The latter means, that the user can only view and import the items from such library but is unable to edit, add or delete the library contents. Also, in the case of remote libraries their files are not stored on the user's machine. All the family types found in the remote library will show up in the data grid together with the corresponding library name.

### Custom Remote Library Connect to a bimCAT-compatible library available over the web. These are usually in-house libraries or commercial libraries. You will need to know the URL in order to connect. If you have your own remote library configured or have access to a configured third-party library server, you can use this option to establish the connection.

After entering the URL, click the **Find libraries** button to automatically connect to the server and get the list of the available libraries. Then you could select the one to add and specify its name in the Library Browser. This is not unlike the [bimCAT Library](#building-transparency-library), but the **Access** level here may differ depending on the server configuration. # Add to Project The **Add to Project** button becomes available when one or more items are checked using the checkboxes.

Allows to add the checked family types to the current Revit project. They will be added together with their corresponding bimCAT back annotations, that will be used to restore the bimCAT collections, builders and bimCAT-specific material layers during the next bimCAT export. * The **loadable** family types (Doors, Windows, Columns, etc.) are added to the Revit project together with their whole family. Even if you check only a single family type from a family containing multiple types, the complete family will be imported to the project anyway. * The **system** family types (Walls, Ceilings, Floors, etc.) are added to the Revit project as separate entities, without importing their whole library. After the family types are added to the project, they instantly become visible in the Current Project tab.

# Add Files to Library **Add Files to Library** The **Add Files to Library** button allows you to import family types from RFA or RVT files to the library. ![](/files/t8ZRGtqICQwBwartpPjj) Concerning the RVT format, please note that only RVT files prepared by the bimCAT Library Browser are supported. Any RFA file could be imported to the library, it simply won’t contain the bimCAT back annotations if it wasn’t prepared by the bimCAT. After clicking the target library selector window will open.

After selecting the target library and clicking the **Add Family Types to Library** button, the open file dialog will appear allowing you to select RFA/RVT files.

After clicking the **Open** button the chosen family types will appear in the library.

In the background, the bimCAT Library Indexer application will copy chosen files to the corresponding library folder and index them. From there on, the library will work with the copies of added files, so the originals will be left intact as long as they’re not located in the library folder. # Delete The **Delete** button becomes available when one or more items are checked using the checkboxes.

It allows you to delete the checked family types from the library. Please note that the corresponding files will be removed from the file system as well. After checking the items you want to delete and clicking this button you will be prompted to remove the family types. If some of the family types cannot be deleted, they will be listed here as well.

After clicking the **Delete** button, the selected entries will be removed from the library database, and the corresponding RFA and RVT files will be removed from the library folder. # Transfer Material Information In order to be able to transfer material information across projects, you need to have a source project with already defined materials. ## 1. Add Families to Library Open the source project with defined material assignments and then open the [bimCAT Library](/user-manual/usage/library-browser).

Select the families that you want to transfer to another project.

Click 'Add to Library', then select the library you want to add the families to, and click the 'Add Family Types to Library' button.

This places all of the selected families in a library that can be used to populate other projects. ## 2. Open target project Now open the project where you want to apply the saved material definitions and open the [bimCAT Library](/user-manual/usage/library-browser) again.

## 3. Scan for updates This time, click the 'Scan for Updates' button to check if there are any families in any of our bimCAT libraries that have a matching name with families in the opened model.

## 4. Select and map families In the 'Project Family Types' window, select the families that you want to transfer information to. If you see ![](/files/gC4Fm8IHeaImJ7tHPQyC) next to any families, then you will also need to select a specific source of definitions in the 'Library Family Types' window for each of the marked families. Click the 'Update # Family Types' button in the bottom right corner to proceed to the next step.

Check and confirm the transfer of information in the next window. The information is now transferred from the library into the active project.

The next time you open and sync the project with Web Ap, you will be able to see all of the transfered definitions in Web App as well. # Assembly Properties The bimCAT Library Browser supports setting a number of assembly properties to the family types, both for the [Current Project](/user-manual/usage/library-browser/current-project) and [Library ](/user-manual/usage/library-browser/library)items. The assembly properties are supported for the following Revit categories: * [Ceilings](#ceilings) * [Columns](#columns) * [Floors](#floors) * [Roofs](#roofs) * [Structural Columns](#structural-columns) * [Structural Framing](#structural-framing) * [Walls](#walls) To set these properties, the user needs to enter the **Compare Assemblies Mode**. This is done by selecting a family type belonging to one of the supported Revit categories and clicking the **Compare \[Category]** button in the right pane.

The **Library Browser** will then enter the **Compare Assemblies Mode** in which only the elements of the chosen Revit category will be visible along with additional set of property columns depending on the Revit category.

Unlike the rest of the columns, the assembly properties could be directly edited in the table.

If you want to change a property for multiple rows at once, select the rows you want to edit using the checkboxes on the right and then edit a property in one of the selected rows. This will result in changing this property for all the selected rows. This feature works both for drop-down lists and edit boxes.

To exit the **Compare Assemblies Mode**, you can either click the **End Compare** button in the right pane, or close the category tag displayed in the toolbar.

Next to the new assembly properties column, the library grid will have one more column responsible for saving or reverting changes done to the assembly properties.

The Save All button allows to save the changes for all modified items

The Save button saves the changes for a specific family type

The Revert button allows to undo changes for a specific family type

When the buttons are in a disabled state, nothing could be saved or reverted here

If the user attempts to exit the **Compare Assemblies Mode** while having unsaved changes, the will be prompted to save.

Apart from the dedicated columns, the assembly properties are also displayed in the right pane.

Also, they could be seen in the **bimCAT Properties Viewer**.

Also, in the **Compare Assemblies Mode** the GWP columns will display a **mini-bar chart** which will makes easier to compare the corresponding values.

The assembly properties are saved to the library and could be transferred from one project to another together with their family types. The set of assembly properties available for each supported Revit category is different. Here's a brief description. ### Ceilings The following assembly properties are available for this category: * **Fire Rating** - a number from the fixed list: **0.5, 1, 1.5, 2, 3, 4**. Unit: **h**. Default value: **none**. * **Thickness** - a number. Unit: **mm**. Default value: **the thickness property of the corresponding Revit assembly, if available**. * **Thermal Resistance** - a number. Unit: **RSI**. Default value: **none**. * **STC** - an integer. Unit: **dimensionless**. Default value: **none**. * **Impact Insulation** - an integer. Unit: **dimensionless**. Default value: **none**. Here's an example on how this set of assembly properties looks in the **Compare Assemblies Mode**.

### Columns The following assembly properties are available for this category: * **Column Type** - a type from the fixed list: **Architectural, Structural**. Default value: **none**. * **Fire Rating** - a number from the fixed list: **0.5, 1, 1.5, 2, 3, 4**. Unit: **h**. Default value: **none**. Here's an example on how this set of assembly properties looks in the **Compare Assemblies Mode**.

### Floors The following assembly properties are available for this category: * **Floor Type** - a type from the fixed list: **Slab on Grade, Suspended**. Default value: **none**. * **Fire Rating** - a number from the fixed list: **0.5, 1, 1.5, 2, 3, 4**. Unit: **h**. Default value: **none**. * **Thickness** - a number. Unit: **mm**. Default value: **the thickness property of the corresponding Revit assembly, if available**. * **Thermal Resistance** - a number. Unit: **RSI**. Default value: **none**. * **STC** - an integer. Unit: **dimensionless**. Default value: **none**. * **Impact Insulation** - an integer. Unit: **dimensionless**. Default value: **none**. Here's an example on how this set of assembly properties looks in the **Compare Assemblies Mode**.

### Roofs The following assembly properties are available for this category: * **Roof Type** - a type from the fixed list: **Steep Slope, Flat, Vegetated**. Default value: **none**. * **Fire Rating** - a number from the fixed list: **0.5, 1, 1.5, 2, 3, 4**. Unit: **h**. Default value: **none**. * **Thickness** - a number. Unit: **mm**. Default value: **the thickness property of the corresponding Revit assembly, if available**. * **Thermal Resistance** - a number. Unit: **RSI**. Default value: **none**. * **STC** - an integer. Unit: **dimensionless**. Default value: **none**. * **Impact Insulation** - an integer. Unit: **dimensionless**. Default value: **none**. Here's an example on how this set of assembly properties looks in the **Compare Assemblies Mode**.

### Structural Columns The following assembly properties are available for this category: * **Column Type** - a type from the fixed list: **Architectural, Structural**. Default value: **none**. * **Fire Rating** - a number from the fixed list: **0.5, 1, 1.5, 2, 3, 4**. Unit: **h**. Default value: **none**. Here's an example on how this set of assembly properties looks in the **Compare Assemblies Mode**.

### Structural Framing The following assembly properties are available for this category: * **Fire Rating** - a number from the fixed list: **0.5, 1, 1.5, 2, 3, 4**. Unit: **h**. Default value: **none**. Here's an example on how this set of assembly properties looks in the **Compare Assemblies Mode**.

### Walls The following assembly properties are available for this category: * **Wall Type** - a type from the fixed list: **Exterior, Partition, Retaining**. Default value: **none**. * **Fire Rating** - a number from the fixed list: **0.5, 1, 1.5, 2, 3, 4**. Unit: **h**. Default value: **none**. * **Thickness** - a number. Unit: **mm**. Default value: **the thickness property of the corresponding Revit assembly, if available**. * **Thermal Resistance** - a number. Unit: **RSI**. Default value: **none**. * **STC** - an integer. Unit: **dimensionless**. Default value: **none**. * **Load Bearing** - a boolean: **True, False**. Default value: **none**. Here's an example on how this set of assembly properties looks in the **Compare Assemblies Mode**.

# Plans for Future **That’s it for now. We are working on:** * **More heatmaps in the Revit 3D viewer** * **Further improvements of annotating back from Web App into Revit and versioning** * **Further improvements of the Library** * **Helpers for concrete/rebar, concrete on metal deck, and columns** * **Improvements on handling the curtain walls** * **Various UI improvements** We would love to get your feedback # Appendix 1: Installer The installer performs two main operations: installing the binaries and the Revit addin. ### Installing the binaries During this step the installer puts all the required plugin binaries into the locations which depend on the chosen installation scope. #### Per-user installation The full paths for the **per-user** installation ([bimCAT Community Edition](/user-manual/installation/tally-climate-action-tool-tallycat-community-edition)) are as follows. * For **Revit 2025** version:\ **C:\Users\\\[UserName]\AppData\Local\Programs\C-Change Labs Inc\bimCAT\2025**

* For **Revit 2024** version:\ **C:\Users\\\[UserName]\AppData\Local\Programs\C-Change Labs Inc\bimCAT\2024** * For **Revit 2023** version:\ **C:\Users\\\[UserName]\AppData\Local\Programs\C-Change Labs Inc\bimCAT\2023** * For **Revit 2022** version:\ **C:\Users\\\[UserName]\AppData\Local\Programs\C-Change Labs Inc\bimCAT\2022** * For **Revit 2021** version:\ **C:\Users\\\[UserName]\AppData\Local\Programs\C-Change Labs Inc\bimCAT\2021** #### Per-machine installation The full paths for the **per-machine** installation ([bimCAT from the Autodesk App Store](/user-manual/installation/tally-climate-action-tool-tallycat) and [bimCAT Community Edition](/user-manual/installation/tally-climate-action-tool-tallycat-community-edition) in the per-machine mode) are as follows. * For **Revit 2025** version:\ **C:\Program Files\C-Change Labs Inc\bimCAT\2025**

* For **Revit 2024** version:\ **C:\Program Files\C-Change Labs Inc\bimCAT\2024** * For **Revit 2023** version:\ **C:\Program Files\C-Change Labs Inc\bimCAT\2023** * For **Revit 2022** version:\ **C:\Program Files\C-Change Labs Inc\bimCAT\2022** * For **Revit 2021** version:\ **C:\Program Files\C-Change Labs Inc\bimCAT\2021** ### Installing the Revit addin During this step the installer puts the plugin's bundle **ApplicationPlugins** location compatible with **Autodesk Store**. #### Per-user installation The full paths for the **per-user** installation ([bimCAT Community Edition](/user-manual/installation/tally-climate-action-tool-tallycat-community-edition)) are as follows. * The bimCAT bundle:\ **C:\Users\\\[UserName]\AppData\Roaming\Autodesk\ApplicationPlugins\bimCAT.bundle**

The paths to **.addin** files corresponding to each Revit version: * For **Revit 2025** version:\ **C:\Users\\\[UserName]\AppData\Roaming\Autodesk\ApplicationPlugins\bimCAT.bundle\Contents\2025\bimCAT.addin** * For **Revit 2024** version:\ **C:\Users\\\[UserName]\AppData\Roaming\Autodesk\ApplicationPlugins\bimCAT.bundle\Contents\2024\bimCAT.addin** * For **Revit 2023** version:\ **C:\Users\\\[UserName]\AppData\Roaming\Autodesk\ApplicationPlugins\bimCAT.bundle\Contents\2023\bimCAT.addin** * For **Revit 2022** version:\ **C:\Users\\\[UserName]\AppData\Roaming\Autodesk\ApplicationPlugins\bimCAT.bundle\Contents\2022\bimCAT.addin** * For **Revit 2021** version:\ **C:\Users\\\[UserName]\AppData\Roaming\Autodesk\ApplicationPlugins\bimCAT.bundle\Contents\2021\bimCAT.addin** #### Per-machine installation The full paths for the **per-machine** installation ([bimCAT from the Autodesk App Store](/user-manual/installation/tally-climate-action-tool-tallycat) and [bimCAT Community Edition](/user-manual/installation/tally-climate-action-tool-tallycat-community-edition) in the per-machine mode) are as follows. * The bimCAT bundle:\ **C:\ProgramData\Autodesk\ApplicationPlugins\bimCAT.bundle**

The paths to **.addin** files corresponding to each Revit version: * For **Revit 2025** version:\ **C:\ProgramData\Autodesk\ApplicationPlugins\bimCAT.bundle\Contents\2025\bimCAT.addin** * For **Revit 2024** version:\ **C:\ProgramData\Autodesk\ApplicationPlugins\bimCAT.bundle\Contents\2024\bimCAT.addin** * For **Revit 2023** version:\ **C:\ProgramData\Autodesk\ApplicationPlugins\bimCAT.bundle\Contents\2023\bimCAT.addin** * For **Revit 2022** version:\ **C:\ProgramData\Autodesk\ApplicationPlugins\bimCAT.bundle\Contents\2022\bimCAT.addin** * For **Revit 2021** version:\ **C:\ProgramData\Autodesk\ApplicationPlugins\bimCAT.bundle\Contents\2021\bimCAT.addin** # Tips & Tricks # Revit Naming Guidance bimCAT tries automatically identify the materials used in your Revit project, but it can only do so effectively if the Revit family and material names are descriptive enough. You can view our list of typical materials used on projects and assessed using bimCAT and see what we suggest for naming schemes that help bimCAT understand what your families and materials actually mean. See this [Google sheet](https://docs.google.com/spreadsheets/d/1jK72adc3zSZYXpNs3tjoZ57d00Iq29DctzEDn2EdGYM/edit#gid=0).

### Linked models # Linked Models **Exporting linked models** Large projects often consist of multiple linked Revit files. You may want to export all linked files with a single click of a button, but unfortunately, that is not possible at this time. The reason is that bimCAT appends additional information to the Revit file you are working in and therefore needs edit access to the elements, which is not possible without opening the file in which all of the elements are actually placed. You will need to open each linked file to be able to export and work on it using bimCAT. Follow the same process for each linked file as in the single-file approach. 1. Open the linked file 2. Create a bimCAT view 1. You should now see all of the elements that you would be able to see in the other file that simply linked this one in. 3. Export the linked file to Web App 1. This will create a new bimCAT project specifically for this linked file. You can now refine and edit the linked file. Note that you will always need to work directly inside the linked file if there are any changes that need to be re-sync. # Calculating Floor Area Above/Below Grade In bimCAT, here's our approach to differentiating between '**above grade**' and '**below grade**' areas: We set a threshold, for instance, **-2 ft**. We then analyze all the elements within the Revit project that fall under the "**Floors**" category. For each of these elements, we assess whether it has an assigned level and if the elevation of that level is above or below our established threshold. * If the elevation is greater than the threshold, we include the area of that floor element in the total **"above grade"** floor area. * Otherwise, we incorporate the area of that floor element into the total **"below grade"** floor area. # Administrative Installation [BIM Climate Action Tool (bimCAT) from the Autodesk App Store](/user-manual/installation/tally-climate-action-tool-tallycat) always installs under the administrator account on per-machine basis, so no special actions are required. To install [BIM Climate Action Tool (bimCAT) Community Edition](/user-manual/installation/tally-climate-action-tool-tallycat-community-edition) from the command line under the administrator account while also making it accessible to other users on the same machine, please adjust your installation scripts as follows: ```batch msiexec /i "bimCAT_community_installer.msi" ALLUSERS=1 ``` **Note**: `ALLUSERS=1` is the critical element in this command. **Installation Paths**: * The `.addin` files will be placed in `C:\ProgramData\Autodesk\ApplicationPlugins\bimCAT.bundle`. * The plugin binaries will reside in `C:\Program Files\C-Change Labs Inc\bimCAT`. **User-Specific Data**: For each user who launches Revit, plugin data (such as configuration files, logs, libraries, etc.) will be stored in `C:\Users\[USERNAME]\AppData\Local\C-Change Labs Inc\bimCAT`. This feature is available starting from version **0.52.1**. **Caution**: If you had previously installed the plugin in a different manner, kindly uninstall it first via Windows Apps & Features (or 'Installed Apps' on Windows 11). # Troubleshooting # "Open in Web App" Display Frozen The **bimCAT plugin** uses [Microsoft Edge WebView2 Runtime](https://developer.microsoft.com/en-us/microsoft-edge/webview2/) to display content within the [Open in Web App](/user-manual/usage/tallycat-beta/open-in-ec3) window. Occasionally, the window may not properly render the bimCAT Building Planner, leading to issues like prolonged loading, blank displays, or freezes. #### **Try Simple Solutions**: * Close and reopen the [Open in Web App](/user-manual/usage/tallycat-beta/open-in-ec3) window. * Restart Revit. #### **Repair WebView2**: If the above steps don't resolve the issue, it may be related to the [Microsoft Edge WebView2 Runtime](https://developer.microsoft.com/en-us/microsoft-edge/webview2/) installation. Consider repairing it: * Exit Revit. * Navigate to **Windows Start Menu > Add or Remove Programs**.

* Locate **WebView2** in the Installed Apps list. It should appear as "**Microsoft Edge WebView2 Runtime**".

* Click on the three-dot menu next to the application and select **Modify**.

* In the installer window that appears, select the **Repair** button.

* Once the repair process concludes, restart Revit and attempt to launch the [Open in Web App](/user-manual/usage/tallycat-beta/open-in-ec3) window again. #### **Reporting the Issue**: If, after following these steps, the problem remains unresolved, kindly use the [Report a Bug](/user-manual/usage/help/report-a-bug) feature to provide us with the specifics of the issue. # Release Notes ## Feature Summary: v0.51 to v1.7 * Support for Revit 2021-2025. * Support for custom EC3 servers. * Improved handling of large buildings. * Greatly improved material recognition. * Support for Linked Models * Support for Design Options * Improved handling of the Curtain Walls. * Partial support for the Generic Models. * When a Revit project is exported to EC3, two EC3 views are created: the Revit view with restricted view organization capabilities and the Custom view which allows to freely re-organize elements. * Improved support for back-annotating sub-components of a family Type * Whenever a builder dialog is opened, the corresponding elements are highlighted in the Revit view. * A new screen to iterate through each family type and sort out its layers. * tallyCAT Library with the ability to save, restore and update Revit Family Types * Scan for Updates in the tallyCAT Library. * Connection of external libraries in the tallyCAT Library * The support of assembly properties in the tallyCAT Library * The support of the new formulas and mini-builders during the EC3 export and in the tallyCAT Library. * An opportunity to select or create custom EC3 folder during the export. * The option to disable auto-detection of Revit materials. This is useful if the recognition is performing poorly (e.g., for non-English designs). * Improved handling of long project and element names during the export to EC3. * Error reports during the export to EC3 and tallyCAT Library operations. * The Help menu item to show these Release Notes. ## What's New {% content-ref url="/pages/HS08k3FdTjkZRV9pmWOk" %} [v1.7](/release-notes/v1.7) {% endcontent-ref %} {% content-ref url="/pages/z57xrJ1kvuKYMrE0QyJK" %} [v1.6](/release-notes/v1.6) {% endcontent-ref %} {% content-ref url="/pages/z57xrJ1kvuKYMrE0QyJK" %} [v1.6](/release-notes/v1.6) {% endcontent-ref %} {% content-ref url="/pages/z57xrJ1kvuKYMrE0QyJK" %} [v1.6](/release-notes/v1.6) {% endcontent-ref %} {% content-ref url="/pages/RCuOib0HTu1nQwQst4Gu" %} [v1.5](/release-notes/v1.5) {% endcontent-ref %} {% content-ref url="/pages/6fp1PKwfLVWHMjkQkXsW" %} [v1.4](/release-notes/v1.4) {% endcontent-ref %} {% content-ref url="/pages/DqWqc3E72mpYCpzf9Cht" %} [v1.3](/release-notes/v1.3) {% endcontent-ref %} {% content-ref url="/pages/yQExYIvLRSl1b4zPcvhE" %} [v1.2](/release-notes/v1.2) {% endcontent-ref %} {% content-ref url="/pages/0FpqPLgCCQdHIChubLhc" %} [v1.0.11](/release-notes/v1.0.11) {% endcontent-ref %} {% content-ref url="/pages/bpuE26tg1VY1F1YLtjZE" %} [v0.65](/release-notes/v0.65) {% endcontent-ref %} {% content-ref url="/pages/wl6PUSvrEWNlULC5n3wz" %} [v0.64](/release-notes/v0.64) {% endcontent-ref %} {% content-ref url="/pages/azaYdtSfRGgzCEwHVvIf" %} [v0.63](/release-notes/v0.63) {% endcontent-ref %} {% content-ref url="/pages/rgQ0AbzJzbScdgMnERrB" %} [v0.62](/release-notes/v0.62) {% endcontent-ref %} {% content-ref url="/pages/I5BkOlchYArBxDTSHTSP" %} [v0.60](/release-notes/v0.60) {% endcontent-ref %} {% content-ref url="/pages/pBXDt8AM95h1qCGhWYx7" %} [v0.57](/release-notes/v0.57) {% endcontent-ref %} {% content-ref url="/pages/m6XT9akRdZX9Zq4N5UnJ" %} [v0.56](/release-notes/v0.56) {% endcontent-ref %} {% content-ref url="/pages/zbCCx1Lz72lrGC1UIETb" %} [v0.55](/release-notes/v0.55) {% endcontent-ref %} {% content-ref url="/pages/PwF8ISXiOlOYUL3X29AV" %} [v0.54](/release-notes/v0.54) {% endcontent-ref %} # v1.7 * tallyCAT has been renamed to bimCAT, introducing several new features and enhancements. While the product name has changed, existing functionality remains intact alongside these improvements.

* Added a new bimCAT category: Curtain Wall Door. This separate category is displayed in the Library Browser, but in Revit, it is still called Doors.

# v1.6 * Added selection corresponding Revit elements on EC3 side

Select elements in Revit, press the 'Check' button ('Select EC3 Elements'), and they will be selected in EC3. * Bugfixes & small improvements. # v1.5 * Added the support for the Revit Design Options. * On the new export using the Manage Scope dialog the user has an opportunity to either export all existing design options or just the elements currently visible in the tallyCAT view.

Export only the elements currently visible in the tallyCAT view

* The user could also set which of the exported design options is Baseline or Plan of Record. This choice will be reflected in tags on EC3. Also, the Plan of Record design option will be used as a source of EC3 material data to be back-annotated to the Revit family types in the project. * Upon exporting the design options, a separate EC3 project will be created for each design option. They will be automatically put into a folder with the name of the Revit project.

* The export report window now lists all the created projects.

* By going to the "Open in EC3" window, the user will be able to switch between the created EC3 project. Upon selecting a project, tallyCAT view will automatically switch to the corresponding design option.

* Fix login issues for non-activated accounts:

If the account isn’t activated, it can be activated during the current session, allowing the login to continue. * Numerous bugfixes & small improvements. # v1.4 * Added **Revit 2025** support. * Dropped **Revit 2020** support. * Added the ability to reset tallyCAT view settings to default.

* Added gathering and sending to the EC3 assemblies perimeter information. * Nunerous bugfixes & small improvements. # v1.3 * Added [disney.buildingtransparency.org](https://disney.buildingtransparency.org) to the list of supported servers.

* Added the opportunity to add custom server to the list. Currently the following domains are supported: [c-change-labs.com](https://c-change-labs.com), [buildingtransparency.org](https://buildingtransparency.org), [enterprisetransparency.com](https://enterprisetransparency.com)

* Fixed the synchronization of the back-annotated linked model items. * Numerous other fixes and improvements. # v1.2 * Added the support for **Linked Models**. Now they're exported to EC3 and annotated together with the items of the main project. Also, the elements from **Linked Models** are fully supported by the **tallyCAT Library**: adding to library, saving to a file, the EC3 back-annotations, [the assembly properties](/user-manual/usage/library-browser/assembly-properties), scanning for updates, etc. In the case when a Revit project has linked documents, the corresponding column is shown in the Library Browser allowing to see which family type belongs to which document.

* Export to EC3: now, upon the export two views are created instead of one: * [Revit View](/user-manual/usage/tallycat-beta/export-to-ec3-synchronize-with-ec3/ec3-export-results-overview/revit-view) - allows to refine material collections but doesn't allow to re-organize the view. This restriction was made to avoid tallyCAT synchronization problems. * [Custom View](/user-manual/usage/tallycat-beta/export-to-ec3-synchronize-with-ec3/ec3-export-results-overview/custom-view) - allows to refine material collections and re-organize the view in any way. This view is not directly used during the tallyCAT synchronization process, so the users could freely change it for their convenience. * tallyCAT Library: added the opportunity to [connect external libraries](/user-manual/usage/library-browser/library/manage-libraries).

* tallyCAT Library: added the support for [Assembly Properties](/user-manual/usage/library-browser/assembly-properties).

* tallyCAT Library: improved handling of the batch library operations. Now errors should not prevent the processing of other elements. Also, at the end of a group operation the report is shown to the user.

* tallyCAT Library: important fixes and performance improvements. The plugin should no longer crash on the startup due to database connection issues. * Open in EC3: important fixes and performance improvements. No more login issues and blank window problems. * Numerous other fixes & improvements. # v1.0.11 * Added the [Community](https://www.buildingtransparency.org/tally/tallycat/) and [Autodesk App Store](https://apps.autodesk.com/ADSTPR/en/Detail/Index?id=8691868899675781155\&appLang=en\&os=Win64\&mode=preview) versions of the plugin. * Added the ability to install per-user or per machine in the [tallyCAT Community](https://www.buildingtransparency.org/tally/tallycat/) version.

* Added the F1 Help feature.

* Fixed Revit 2022 and 2023 startup crashes in some environments. * Fixed errors related to the incompatible version of Polly library used for network resilience. * Fixed the Library startup crashes in some environment due to conflicting database settings. * Various other fixes and improvements. # v0.65 * Fixed quantity conversions when Windows locale is not English. * Improved network resilience during the export to EC3. * Fixed handling of GWP values of piece (item) quantities in "Properties & Charts". * Library: added support for updating Family Types which have grouped elements in the project. * Library: fixed database configuration conflicts with other Revit plugins. * Fixed positioning of various tallyCAT windows. * Added more graceful error handling in the "Open in EC3" window.

* Other fixes & improvements. # v0.64 * Added the refresh button to the Select EC3 Folder dialog.\\

* Add syntax highlighting to the EC3 Properties Viewer in the Library.

* Fixed deleting loadable family types from the Library; added the list of the items that are about to be deleted to the removal prompt.

* Improved the GWP values display in the Library.

* Fixed calculation of the GWP quantities in the library. Now the Library Browser properly shows approximate GWP per unit of the target assembly. * Added more details to Library error messages.

* Fixed recalculation of the quantities of materials added only on the EC3 side when adding a family type from the Library to a new project and exporting it to the EC3. * Fixed Scan for Updates for loadable families. * Numerous other fixes & improvements. # v0.63 1. Moved the **tallyCAT Library** to a separate button in the ribbon.

2. Add the new **Scan for Updates** functionality to the **tallyCAT Library.**

* The **Scan for Updates** button allows to check if family types in the currently opened project have updated versions in the Library. * If this is the case, the **Scan for Updates** window will pop up allowing the user to choose which family types to update.

* Clicking the **Compare** button will bring up the **Compare Annotations** screen where the user could see the difference between the EC3 annotations in selected project family type and the corresponding Library family type.

* After selecting the family types to update and clicking the **Update X Family Types** button, the user will be prompted to confirm the operation.

* Afte clicking **Confirm**, the selected project family types will be overwritten by the Library ones. 3. Now tallyCAT uses formulas instead of explicit quantities both for multi-material Building Elements and their Materials. These formulas are also stored in the Library to be re-used in other projects. Mini-builder data persists through the Library as well.

4. Added partial Generic Models support (no material detection for now).

4. Fixed the incorrectly calculated Floor Area Above/Below grade. 5. Added the correct handling of too long Revit element names. 6. Moved the plugin documentation to GitBook. 7. Various small tweaks in the installer. 8. Lots of other bugfixes & improvements. # v0.62 1. Added the export folder selection feature in Manage Scope dialog.\\

2. The new way of handling Curtain Walls: * Now curtain Curtain Panels and Curtain Wall Mullions are grouped under two corresponding labels on the EC3. * The Revit elements (Curtain Walls, etc.) which include each of these curtain element types are listed in the corresponding building element’s notes. * This new grouping simplifies EC3 project structure and allows to avoid duplications.

3. Added the support for material quantities measured in pieces.\\

4. Open in EC3: fixed the issue when Open in EC3 window was reloading the project page spontaneously, losing unsaved user’s changes due to authentication refresh. 5. Fixed the issue when material quantity units were not properly displayed in the EC3. 6. Library Browser: fixed the Remove EC3 Data functionality. 7. Fixed handling of the overlong family names, type names, material names and type marks during the export. 8. Various other fixes & improvements.\\ # v0.60 1. During the export, added the option to not detect the Revit materials on the EC3.\\

1. If the checkbox is set, the EC3 will try to create collections for all Revit materials upon the export. Material quantities will be set according to the collection requirements.\\

2. If the checkbox is not set, the EC3 will leave the collections empty for the user to choose them manually.\ \ The material quantities will be set according to the following rule:

* If two dimensions of the corresponding Revit element’s bounding box are < 10 cm, the length is used. * If the material layer thickness is < 10 cm, or one dimension of the corresponding Revit element’s bounding box is < 10 cm, the area is used. * In all other cases, the volume is used 2. Added the completion time to the Export Report.\ ![](https://lh3.googleusercontent.com/LbwD4XR4QvruG4xT8dmfmo_qTJcNqCpWBodFnvmQf2UTX_HsGpV7Q9KKJ2oCE_nETb2hWN0SG1YyRIXpHQro-WJ3pSaDmsTVQArVZ1d7kKJcD6V0U0qJ6leRDMt_u4HSFvhWsIc2pFHZByTOP6zMsEY) 3. Added the Help menu item to show these Release Notes.\ ![](https://lh4.googleusercontent.com/TgZSZm0bFnvx6EWxrDBVCLfn3fKrGlbwnCElbGYv_9dsupQUqu6bN5E4VaGTQZP2i0CX6f__P8vMfcUix82EOo9NAhaEXC3irANzA0CWKZshROs0oCCt3J6pIVDvu58ycQKqEsU0M2us-613DEDiR20) 4. Fixed the Open in EC3 window spontaneously refreshing itself and losing the user’s unsaved data. 5. Other fixes & performance improvements. # v0.57 1. Improved the identification of detached projects on EC3. Project names will now be appropriately truncated if they exceed the EC3 limit of 100 characters.\ \ E.g.,\ **Original name:** \[tallyCAT] This is some very-very long Revit project name just to demonstrate our splendid idea2024\ \ **Detached name:** \[tallyCAT] This is some very-very long Revit project name just to demonstrate our spl... \[Detached] 2. A Revit version column has been added to the Library tab of the Library Browser. Moreover, library items with a version higher than the current Revit document will now be disabled in the Library Browser.\\

3. After exporting a project that includes Curtain Walls, tallyCAT will now verify if any Curtain Panel or Mullion family types are utilized in more than one Curtain Wall type. If so, a warning will be displayed, as tallyCAT currently cannot assign two or more different EC3 collections to the same family type. This behavior will be improved in the future.\ ![](https://lh5.googleusercontent.com/tNuj98yODKm4HvR4m330dswcp39tRu1Isvx7dVNl4m1YtGhTVo_mbcWPrKuB9dezKwkv_98TAFCrsxkREYOCD0t93DqRe7MYeRUybLwTX7wBogxQB6kU_1TTUT84rgFfpl0WR6zes_kUwvuhxqRghmE) 4. Additional EC3 collection information is now displayed in the EC3 Revit view.\ ![](https://lh3.googleusercontent.com/ohnXKjK4rqzmyPotIJtGLCWvsN3PpRtgrP103UDvX1xesE08N5tZHcWeQOxkH1plVIhsi124GzWbQ8zyhzt6kNIh1qhw5CU76Ci3rqbkJgd5wogUWKpmenqB3eT-GmBtTTOYbMaKE9PNpGlwB3GRbDE)\\

5. Various bug fixes and performance enhancements have been implemented. # v0.56 1. Added support for Revit 2024. 2. The EC3 builder data is now saved to the library and automatically restored during the export of a new project having annotated elements. 3. Whenever a builder dialog is opened, the corresponding elements are highlighted in the Revit view.\\

**Bug Fixes** 1. Fixed Revit freezes after a large project export to EC3; made various performance improvements. 2. Fixed the ‘Changes to groups are allowed only in group edit mode’ error which often happened during the export of large projects having groups.\\

3. Better resolution of Library database conflicts.\\

4. Added automatic exit from the Temporary Hide/Isolate mode during the export. 5. During the sync, fixed restoring collections and builders for Revit elements which were hidden and then unhidden in the project. 6. Numerous other fixes & improvements. # v0.55 1. Implemented the Library Browser.\\

2. Added the EC3 builder integration.\ ![](https://lh6.googleusercontent.com/qSU-Yjy9kgn6A9n7QqUNx1CFvdWNTB_IsAcGq1kJ8dLYbAuxuFJvDQhtK-RH835He193cp8uXHGr0-caW4woWUCvG1QZND-MYdfuswbzcGqxMtOi89AwNunYMdGzsUBGsFfsArU_npfL2nkhmOJI2S8)\\

3. Various fixes and improvements. # v0.54 1. The Curtain Walls hierarchy on the EC3 now has one more level to group together Curtain Wall Panels and Mullions.\\

2. During the initial export, all quantities for EC3 building elements & their sub-elements (materials) are coming from Revit. After that, during each subsequent synchronization: 1. Sub-elements (materials) are governed by EC3, if manually altered. Even if a sub-element’s quantity gets changed in Revit, during the next sync the existing EC3 quantity/formula will be left intact. 2. The building elements and up are always governed by Revit. If a parent elements quantity gets changed in Revit, the EC3 quantity will be overwritten on the next sync. 3. If a material collection requires mass but the EC3 is unable to provide reliable density to calculate it, an erred equation will be used instead of quantity, e.g., "123.4\*kg\_per\_{{volume\_unit}}", so the user could set the density themselves.\ Also the corresponding comment note will be added.\\

4. We had a bug when words ‘concrete’, ‘brick’, ‘steel’, etc. in the parent element’s name affected the mapping of the sub-elements too much. This is fixed now.\\

5. A lot of bugfixes and improvements. **Testing recommendations** 1. Please check if the projects which produced errors before are now exported fine. 2. Also please check the performance and the WebView behavior. 3. Please pay attention to various sync-related scenarios, e.g.: 1. A project is exported to the EC3. 2. Sub-element (material) quantities are changed on the EC3 and saved. 3. Parent element quantities are changed in Revit, new material layers are added to family types, etc. 4. The project is synced with the EC3.\ In this case, the parent element quantities should be updated by Revit, the sub-element quantities should retain their EC3 values, new layers should be added from Revit. 4. Also please check Curtain Walls export/sync. 5. Please check whether the words ‘steel’, ‘brick’, ‘concrete’, ‘wood’, etc. in a parent element’s name affect the sub-elements’ mapping in a wrong way.