Both types of libraries are created by enabling & linking BIM 360 projects, but from different views within the Account Admin page. Once enabled, the two types of libraries behave nearly the same, with a few exceptions. Here are the key differences between the two.
- Created/Enabled from the Account Admin > Projects view
- Can transfer content into any number of Enterprise libraries
- Can have content transferred into it from a Single enterprise library
- Can be used with Sync BOM
Created/Enabled from the Account Admin > Enterprise Libraries view
Can transfer content into any number of Project libraries
Can have content transferred into it from any number of Project Libraries
Cannot be used with Sync BOM
In short, if you plan on publishing content that will be re-used for multiple projects, an enterprise library is highly recommended. At the end of a project, if you decide that the content will be useful in other projects, you may want to transfer it into an enterprise library, by using the Content Manager.
Creating Enterprise Libraries
To create an enterprise library, you must first pick a BIM 360 project to enable. Typically, this is a BIM 360 project that has been created specifically for this reason. After creating the project, find the Enterprise Libraries view in Account Admin.
Find the project you wish to use, and click Enable.
Once the project has been enabled, you can click Manage User Access
to add additional users
. Be sure to give yourself the Kit Manager
role on this project if you wish to transfer content into it.
Using an Enterprise Library
Connect a Revit document to the library to publish and maintain your families and modules just like any other library.
However, the enterprise library will now appear in the Content Manager for transferring. To do this, open the KitConnect Content Manager application from the start menu.
As long as you have the Kit Manager role on the "TO:" library, you should see it in the combobox at the top of the application.
Alternately, if you wish to transfer from the enterprise library, select a project library in the "TO:" project, then find the enterprise library in the lower "From:" combobox.
Once content has been transferred from an enterprise library to a project, it becomes bound to that project, so you will be unable to change it. This is to prevent dependencies from being overwritten unexpectedly by content from another enterprise library.