Storage rules

A project administrator can put access control on databases for project teams. This is to ensure the strict separation of data when multiple teams are working on a project. Storage rules enables the storage of Engi and Funite tags in multiple engineering databases based on class model. Rules are based on class and conditions are based on class attributes.

In engineering configuration, the administrator creates a list of storage rules in a selected database based on class model. A class without conditions can be used in creating administrative elements like Plant or System.

Storage rule creation

A project administrator uses the the storage rule editor in Configuration to maintain a list of storage rules.

Note:
Class rule can exist without condition but must have a database number

Storage configuration rules

To create storage configuration rules;

1. Select ‘+’ in Configurations

2. Complete the Name field in New/edit configuration.

3. Select the browse button on the right of Class to display the Select class window.

4. Select a class.

   

5. Select '+' next to Attribute rule to display Rule and Database number field.

6. Insert the database number if the field is empty.

7. In Configurations, select the tick button next to each name.

8. Select Save.

9. To delete a selected configuration, select ‘x’ in Configurations.

   

   Note:
   1. Storage configuration rules defaults to Class rule.
   2. Storage rules will execute only on creation of tag. It will not execute if attribute values are modified after it has been created.
   3. A parent storage rule is applied to havepart associated part class even if another DB is individually specified for part class.

Attribute storage rule

Attribute storage rules can have multiple conditions defined for the same class.

For Attribute rule;

10. Select '+'and complete the Name field.

11. Complete the Name field in New/edit configuration, for example, MCC50.

12. Select the browse button on the right of Class to display the Select class window.

13. Select a class. For example, Motor Control Centre (MCC).

    

14. Select + next to Attribute rule to display Rule with, And/Or, Attribute, Comparison and Value fields.

    

Note:
To ensure that the storage rule is triggered correctly during tag creation, the attributes used in the rule should be mapped to a naming rule part.

It is a best practice to make naming rule parts mandatory so that a value is always provided, allowing the system to accurately determine the appropriate database for storage.

Inheritance in Storage rules

In Engineering database, storage rule supports inheritance on tag creation. If a rule is set in a parent class, then the children classes inherit the rules.

Some conditions could have conflicting result. If so, the priority of the rule is determined by sequence. The lower the sequence number the higher the priority.