Alarms and events

Configure an ALM_STATISTICS module for gathering and computing alarm statistics

The ALM_STATISTICS module requires some additional configuration in order to set it up; it is intended that this module will be configured by an experienced DeltaV control engineer familiar with Visual Basic and DeltaV Operate (Configure) schedules.

When creating a new module instance from the ALM_STATISTICS module template, the scheduler needs to be modified in order to tie the corresponding module to it. Sometimes you may want to have a separate module instance for each Operator station while having the scheduler running on only the Professional Plus. Or you may want to have a separate module instance for each Operator station while having a scheduler running on each Operator station.

The following procedure outlines how to configure a single ALM_STATISTICS module instance for gathering and computing alarm statistics. This procedure presumes the scheduled iFix task to collect alarm statistics (ALM_STATS_CALC.evs) is deployed on the workstation for which alarm statistics are being collected. For other deployment scenarios, a well-qualified DeltaV configuration engineer will need to examine the script and edit as required.
Note

For more detailed information on how to modify the ALM_ STATS_CALC.evs in the Scheduler, see the commented instructions in the ALM_ STATS_CALC.evs script.

  1. Create an instance of the Operator Statistics Module (ALM_STATISTICS) in DeltaV Explorer.
  2. Assign it to a node and download the module.
  3. Open DeltaV Operate in Configure mode.
  4. Under Schedules, double-click on ALM_ STATS_CALC to open it in the Scheduler.
    Note

    You may need to click on the Event Based Entries tab in the Scheduler to see ALM_STATS.

  5. Double click the expression to open the Data Source dialog.
    1. Replace ALM_STATIST_1 with the name of the module instance created in step 1.
  6. Expand ALM_STATS_CALC in the system tree.
  7. Right-click ALM_STATS in the system tree and select Edit Script… from the context menu.
  8. On the lines marked with @@@, change all instances of ALM_STATIST_1 to match the name of the module instance created in step 1.
    If the default module name was not modified when instantiated, leave ALM_STATIST_1 as is.
  9. Save the edited ALM_STATS_CALC schedule template as a new schedule (for example, OP1_OSM.evs).
  10. Close the Visual Basic editor.
  11. In DeltaV Operate Configure, add the schedule to the background task startup list using the User Preferences dialog box > Background Startup tab.
  12. In the UserSettings script, locate the ADD YOUR INITIALIZATION HERE comment.
  13. Add the line Shell "fixbackgroundserver.exe /SERVICE" just after "ADD YOUR INITIALIZATION HERE".
    This enables the fixbackgroundserver to be launched when starting iFix.
  14. In the Opening Scheduler section (just below the 'ADD YOUR INITIALIZATION section), locate the line frsOpenUserSchedule "<Your Scheduler>.evs".
    1. Uncomment this line.
    2. Replace <YourScheduler> with the name you gave your schedule in Step 8.
      Example: frsOpenUserSchedule "OP1_OSM.evs"
  15. Save and close the Visual Basic Editor.
    Note

    If you are editing the User_ref picture, be sure to save this as UserSettings.

  16. Close DeltaV Operate and re-open the Scheduler in Configure mode.
  17. Switch to Run mode to initialize the FixBackgroundServer.
  18. Verify that the FixBackgroundServer has been initialized by doing the following:
    1. Switch to Configure mode and verify that the status of the ALM_STATS entry is Active.
    2. Open Windows Task Manager and verify that FixBackgroundServer.evs is now running in Processes.
  19. Switch to Run mode and open the module faceplate.
    The values displayed on the faceplate should coincide with the module's values when it is opened in Control Studio on-line.