Discovery Rules
The Discovery Rules feature allows you to customize and create discovery rules for a family library, modify family settings, edit hierarchy settings, and modify object mapping rules. It also allows you to create additional discovery rules for a library so that you can select which rules will be used when importing objects. For procedures or workflows, see the step-by-step section.
Your software contains pre-installed family libraries for the global and local levels, but they are not editable until you customize them. Customizing means that the library structure is copied from the Headquarter level to the Project level, where the family library can then be modified and saved.
The Discovery Rules folder allows you to create additional libraries with discovery rules so that you can select which rules will be used when importing objects. Libraries you create will be available in the Device Discovery expander in the Discovery tab.
The Family Settings section allows you to make a few minor modifications, such as selecting a family library name (which must be unique in the system) and sub-family library name. You can also select a custom SiB-X DLL file, and create a folder to contain all the objects in the device. Additionally, you can choose to support database changes for a device family, which means that the family will support automatic detection of added and removed objects. Finally, you can disable consistency alarms and full discovery for devices.
The Hierarchy Settings section allows you to create an object name hierarchy (a Logical View) based on a delimiter or text.
Using Delimiters
You can create a Logical View based on a delimiter, and on various character lengths for each level in the hierarchy. The following object name uses a period as a delimiter, while using various character lengths for each level in the hierarchy.
Level 1: BG
Level 2: WCAMPUS
Level 3: BLDG1
Level 4: FLR1
Result: BG.WCAMPUS.BLDG1.FLR1.RMTEMP1
Using Text
You can also create a Logical View based on text entries for each level in the hierarchy.
Level 1: Zug
Level 2: Hq
Level 3: Trng
Level 4: Flr3
Level 5: Blind1
Result: ZugHqTrngFlr3Blind1
The Object Mapping Rules section allows you to insert new rows for objects, files, and devices—and then define their rules for discovery. You can also remove rows or move them up or down in the table. Entries are evaluated in a top-down order.
The rules are comprised of Vendor, Object Type, Property, Match Strings, EO Type, Object Model Name, and Function Key. The inputs are Vendor, Object Type, Property, and Match Strings. If a device matches the parameters of the inputs, the device uses the specified object model and function.
A function can be either a name or a key. If a string maps to a function name (a real function) in a library, the function is used. If no function is found, a function key is used. The function key may map to a function key in the Import Rules.
