Configure alternative ENS definitions for a configuration - HxGN SDx - Update 64 - Administration & Configuration

An ENS definition can be related to ClassDefs, classifications, and also configuration items.

In the case of classification and configuration, the software navigates the respective trees looking for the most specialized ENS definition. In the case of configuration, the software starts at the current create configuration, and if it does not find an ENS definition at this level, it navigates up the tree to the configuration top until it finds one.

The following order of preference is used to determine which ENS definition to use. In all the following cases, the system first retrieves ENS definitions related to the ClassDef of the object.

1. First, search for an ENS definition with a matching classification and configuration or one higher up the tree; that is, if the object is classified and in a configuration, look for an ENS definition with both a relevant classification and configuration related.

2. If the object is classified, the classification takes preference over the configuration; that is, an ENS definition with a matching classification and no configuration (applicable for any configuration) takes preference over one with a matching configuration and no classification.

3. If the object is not classified, search for an ENS definition with a matching configuration.

4. Finally, search for an ENS definition with no configuration and no classification.

There is a drag-and-drop condition (IsObj1SPFPlantOrConfigTop) on the configuration item to ENS definition relationship definition (SPFConfigurationItemENSDef) that only allows an ENS definition to be related to a plant. The reason this restriction is in place is because if an ENS definition was allowed to be related at both the project and plant level, then there could potentially be a problem when merging: If different ENS definitions are used at the project level and the plant level, then the object would need to be renamed on merge, which isn’t allowed. However, it is valid for a customer to add a configuration level above the plant, for example, at the site; in this case, the condition (IsObj1SPFPlantOrConfigTop) would need to be updated to support this.