PmAlarmEvent - Deatiled object description

See: Object PmAlarmEvent
Alarm/event groups enable to logically separate the creation and handling of the corresponding alarms/events in the application into smaller parts, on places where they logically belong. For example by the technological units, etc. The possibility to place the object that represents the alarm/event group into the corresponding branch in the objects tree, it allows better administration of the application and easier moving the parts of one application into other applications.
The PmAlarmEvent object creates its own group, or it is a subgroup of another group of another PmAlarmEvent object (see the configurator "Parent enabled"). If it is a subgroup in another group, then it saves its data into the main common group of the parent and each subgroups differ by the area setting (see the configurator "Area"). Each group then has its own different area, that can be used in the alarm viewer (status and history) for distinguishing and filtering them. When opening the viewer (status or history) over the PmAlarmEvent object of the subgroup type, the viewer automatically uses the filtration string, filtering the content of the group for specified area. Then only the alarms and events of the specific subgroup are displayed.
The PmAlarmEvent object can also automatically generate its current and historical entries into dynamic HTML pages and offer these pages to Web clients. Offering Web pages can be enabled on the page PmAlarmEvent > Web server. See: Overview of the Web technology in the PROMOTIC system. The client requiring data from this Web component is type of "PmWebClient" from the license point of view.
Alarm status and history viewer can also be opened, for example, using the PmPanel.OpenView method (see also Object viewer open) over the PmAlarmEvent object of the group or subgroup type. This method can be called, for example, by the panel button and it is functional for both local and Web applications (i.e. if the method is called in the Web panel button for example).
Data extension:

The variables of the PmData object can utilise Data extension ExtAlarmAnalog or ExtAlarmBinary and register itself directly into the PmAlarmEvent object. Then, on the page PmAlarmEvent > List the items for this type of alarming need not to be defined.

See also:
PROMOTIC 8.3.22 SCADA system documentation - MICROSYS, spol. s r.o.

Send page remarkContact responsible person
© MICROSYS, spol. s r. o.Tavičská 845/21 703 00 Ostrava-Vítkovice