Building a report on alarms as system failures

In Monitoring PSIM, you can build a report on alarms as system failures (see System failures) by specifying the beginning of the alarm, its ending, and duration. For this, the alarms must have starting and finishing events. To build such a report on failures, do the following:

1. On the Control Agent side, add the interception of starting and finishing events. The format of the message must strictly correspond to the following template: <Event name> [<id> ] - <name>, where instead of the <id>, you must specify the object number, and instead of the <name>, the object name.
   Example of the "starting" event.
   
   Example of the "finishing" event.
   
   As a result, there is a list of two events.
   
   

   On the Control Server side, these alarms are registered as short-term.

2. On the Control Server side, create the Monitoring reports interface object.
3. On the toolbar of the Monitoring reports object, click the System failures button.
   The corresponding configuration form appears, in which you must:
   1. Set the Alarms as failures checkbox.
      
   2. Click the button, to expand the Alarm list window.
   3. In the Alarm list window:
      1. Click the button, to add an entry.
      2. In the Failure name field, specify the failure name in the way it is to be displayed in the failure report.
         
      3. In the Starting event row, specify the name of the starting event fully in accordance with the template, as in step 1.
      4. In the Finishing event row, specify the name of the finishing event fully in accordance with the template, as in step 1.
      5. Set the Remove from Alarm report checkbox to prevent the display of starting and finishing events while building an "Alarm" report.
      6. Add an entry by clicking the button.
         

         The button to add an entry appears only if you fill in all the data, and the description of the starting and finishing events contains the [<id>] - <name> template. Further, you can edit or remove the created entry.

         As a result, the new entry is added to the Alarm list.
         
      7. Repeat steps i-vi for all alarms.
         

         When you add the following entry, don't duplicate the values of the edited fields. If you try to enter a duplicate, the error message appears.

      8. Build a report.
         Example of an alarm report
         
         Example of a report on failures with the Alarms as failures checkbox set.
         
         If you set the Remove from Alarm report checkbox in the Alarm list window, the corresponding events aren't included in the alarm report.
         
         

Building a report on alarms as system failures is complete.

Features of building a report on alarms as system failures

When you clear the Alarms as failures checkbox, then the Failure type list displays standard failures.

When you set the Alarms as failures checkbox, then the Failure type list displays failures described in the Alarm list window.

You can build a report either for all failures (Failure type=all failures) or for several ones (in the Failure type field, select specific failures).

Example of a script for a timer with number 1, which triggers once a day

If the starting event is lost, then the Alarms as failures incorrect report is built. To avoid this, we recommend using scripts on the Control Agent side to generate, for example, once a day, a starting or finishing event depending on the current state of the object. For more details on how to create scripts, see Guide for creating scripts (programming).
Example of a script for a timer with number 1, which triggers once a day.

if (Event.SourceType=="TIMER" && Event.SourceId=="1" && Event.Action=="TRIGGER")
{
  var msg = CreateMsg();
  msg.StringToMsg(GetObjectIds("CAM"));
  var count = msg.GetParam("id.count");
  var i;
  for(i = 0; i < count; i++)
  {
    if(GetObjectState("CAM", msg.GetParam("id." + i))=="DISARMED")
    {
      NotifyEventStr("CAM",msg.GetParam("id." + i),"DISARM","");
    }
    else
    {
      NotifyEventStr("CAM",msg.GetParam("id." + i),"ARM","");
    } 
  }
}