Name Context Mapping

Name Context mapping provides a way in which rule sets and naming rules can be used to generate, validate and write a name within a scope. It is used to group the naming rules for an attribute and provides unique name allocation. Scopes can have multiple name context.

Database for Name Context Mappings

On the Rules tab, in the Tag Naming group, select Name Context Mappings. This displays the Name context mappings window with a dropdown list of databases. Select a database and OK. All Name Context mappings will then be stored in the database.

Note:
Allocating a database can only be performed once.

Map Name Context to write Attribute

Click Name context mappings to map a name context to a Write attribute. For example, StellO Name context is mapped to the Default Name Write attribute.

Select OK.

Note:
A name context must be mapped against a Write attribute.

Name context mapping provides a Prevent Duplicate Names option. When the option is enabled, irrespective of the class, Fully qualified names must be unique in the Name context. When the option is disabled, the Name context permits elements of different classes to have the same Fully qualified name (allocated name combined with invisible name part values). For example: a Plant P-101 and also a Pump P-101.

The Prevent duplicate names is checked only during the creation of the name context and cannot be modified once tagging is done. Refer to Scopes.