Every project must have the project Floor Manager data stored in it's own dgnlib.
The default name of the Floor Manager dgnlib is BB_FloorMaster.dgnlib, located by default in the WorkSet. For instance in the delivered NM Dataset the location is "C:\ProgramData\Bentley\OpenBuildings CONNECT Edition\Configuration\WorkSpaces\Building_Examples\worksets\BuildingTemplate_NM\Standards\DgnLib\BB_FloorMaster.dgnlib".
The location and name of the dgnlib is defined by BB_FLOORMASTER_DGN in each WorkSet Configuration File.
The data contained in BB_FloorMaster.dgnlib is obviously very important, you may wish to be able to name each project's floor master with a unique name to avoid any mixup in operation and when archiving or restoring from backup.
Provided that the filename specified by BB_FLOORMASTER_DGN matches the actual dgnlib name it will be found correctly.
If you have a small number of projects simply making matching edits to the file name and the BB_FLOORMASTER_DGN statement in each WorkSet Configuration File will be a valid approach.
For larger numbers of projects (or if you like me you just don't like repetitive tasks!) try the following methods to specify individual names for the Floor manager dgnlib:
_USTN_WORKSETNAME is a standard variable that gathers the name of the active WorkSet from the WorkSet CFG name, this can be used to uniquely identify the DGNLIB:
You might utilize to use a standard organization identifier such as a project number via a custom variable:
Don't get carried away with custom variables, only add them when absolutely necessary otherwise things can get over-complicated when troubleshooting!
A custom variable such as PROJECTNUMBER can also be used to prefix the file names of other project specific resources. Once PROJECTNUMBER is defined, $(PROJECTNUMBER) can be used in any subsequent statements that define file names.