You need to organize your database so that the tree-structure within the Database Bar is logical and user-friendly, and allows you and other users to locate items quickly. Typically, you should organize the database so that it reflects the physical structure of your system—for example, regions, control centers, outstations, and points.
To produce a multi-level tree structure that reflects the physical layout of your system, you need to organize your database into Groups. If your database structure is ‘modular’ and like-aspects of configuration are repeated throughout parts of your system, you should consider using one or more Group Templates to produce ‘model’ Group configuration. You then configure as many Group Instances as you require, to contain the groups of ‘live’ data. As each Instance inherits much of its configuration from a Group Template, this can considerably reduce configuration time. Within each Instance, ‘Instance-specific’ configuration is used to uniquely identify the ‘live’ data that is specific to that particular instance.
You can also use Abstract items within Group Templates to produce the base configuration for points or outstations, and then convert those Abstract items into specific point or outstation types within the Group Instances.
Example:
A ClearSCADA system might contain 50 outstations. Each outstation might monitor two analog values, have a digital input that monitors the open or closed state of a switch, and have a digital output that is used to control the state of that switch.
As much of the configuration for each outstation and its associated points is common to each outstation on the system, a Group Template can be configured to include the common configuration. Group Instances, which reference the Group Template, can then be configured to include both the common configuration (inherited from the Group Template) and the outstation- or point-specific configuration (such as an address or ID), that is unique to each Instance.
You can configure up to 12 levels of Groups, Group Templates, and Group Instances, and individual database items (such as points, outstations, and timers) within your database.
For further information, see, as appropriate:
- Groups
- Group Templates and Group Instances.
We suggest that you place any User, User Group, and User Roster configuration in a separate ‘Users’ Group, off your system’s root directory. This will allow the user settings and permissions to be adjusted and updated when required, from the one location.