Previous 6.9 Customization Next

6.9.4 User defined relationships

These relationships enable quick navigation between equipments and virtual equipments when using any Measurements or Alarms menu, or even the Site and equipment configuration menu. A relationship might be symmetric or asymmetric: in the later case it has separate attributes for the two direction, for example two names. After installation the system contains several predefined relationships, but these can be freely modified and extended by the users using the Customization => User defined relationships menu.

The page shows all the relationship types in a filterable table. Each relationship has the following parameters:

·       Direction: it is either symmetric or asymmetric

·       Names: the name of the relationship. For asymmetric relationships the user must provide two different names.

·       Element type: optional element types for which the relationship is enabled. Multiple types can be choosen. If no types are choosen then the relationship can be used for every equipment types. For asymmetric relationships the element types for the different sides can be specified separately

·       Show remote alarm status: if it is set then PVSR will show the current alarm status of the remote equipment and not just its name. For asymmetric relationships this option can be specified separately

·       Uniqueness: if it set to “Not allowed” then once a relationship exists with this type and direction for an object then the user is not allowed to create a similar relationship. If the option is set to “Overwrite” then the new relationship can be created but PVSR will automatically delete the old one. For asymmetric relationships this option can be specified separately. For example if there is an asymmetric relationship with names for the two direction R1 and R2 and the equipment A has a R1 relationship to equipment B and the uniqueness is set to “Not allowed” then A cannot point to equipment C with R1, but equipment C could point to A as R1 and so A could point to C as R2. If the uniqueness would be set to “Overwrite” then A could point to C as R1 but that would automatically delete the relationship between A and B

·       Show relationship for children as well: if it is set then the relationship is also shown when viewing a chart below the equipment / virtual equipment

·       Delete relationship if connected equipment is deleted: if the option is set and an equipment on either side of the relationship is deleted then PVSR will automatically delete the relationship as well. This option is meaningless if a virtual equipment is in a relationship and it is deleted, because unlike the equipments the virtual equipments are not preserved in an archive table in the system after deletion, so the relationship would be deleted in such a case anyway

 

This table shows the default relationships after the system is installed. For the symmetric relationships only the Name A column is filled in.

Name A

Name B

Hosts

Hosted by

Same device

Connected to

Load balance

Backup system

Live system

Behind

In front of

Service depending on

Affecting service

VM runs

Running on VM

Contains chart from

Has charts in