It is best practice to manage dgnlib files outside the day to day working environment, primarily to avoid any unwanted changes to operational files that people may be using for their project work.
In AECOsim Building Designer there is also the added concern that DGNLIBs may become cross-contaminated with the contents of other DGNLIBs duplicating of levels and other library content. This can happen due to the dataset scan discussed in Unwanted Levels in AECOsim Building Designer DGN Files.
One method to avoid this is using an administrator User Configuration file containing appropriate variables.
If you are the CAD/BIM administrator, copy your existing <name>.ucf file to Admin_<name>.ucf, then using Notepad++ or a similar editor add the appropriate variable from the table below:
This will disable the copying of dataset library levels into the dgnlib when you are working on it.
(Note that in CONNECT Edition when BB_DVDATASETELEMENTDISABLE = 1 is defined there is no need to define BB_DVLEVELSDISABLE, it should be left in its default undefined state.)
Another approach if it is available is to work on DGNLIB files in MicroStation.
Note: these variables must not be used in production, the levels and other resources copied from the dataset into active DGN files are needed for successful creation of Dynamic Views, if these resources are not present views are likely to be incomplete.
AECOsim Building Designer copies levels and linestyles needed for Dynamic View creation into each file on open. These are required for DV operations but are neither needed or wanted in dgnlibs other than the source dgnlibs in the dataset.
Unwanted content can be compressed out of dgnlib files by careful use of the Compress Options or the key-in "delete unused" with options as appropriate, eg "delete unused linestyles".
Obviously you should not use this example command in a dgnlib that actually contains your library linestyles!
Search help using the string "delete unused" for all options for the 'delete unused' key-in.
A series of key-ins can be applied to a whole set of dgnlibs using the Batch Processor. An example of using the Batch Processor is described in Batch Update of Cached Visible Edges (CVE) in AECOsim Building Designer.