Detecting User-Defined Events

Model 802 can be configured to detect user-defined events. A user-defined event is a generic manually recorded event used to document important occurrences related to process operations. User-defined events could be major maintenance items, routine maintenance items, process checks, shift notes, or any other event important to later analysis. For information about creating models, refer to Creating Models for User-Defined Events.

To configure Model 802

  1. In the Plant Model, right-click the production unit where you want to detect events and click Configure Events on <production unit>. The Event Detection wizard appears.

  2. On the Configured Models tab, select User-Defined Event from the Model Type list. The Subtype list appears.

  3. Select a sub-type and click Add New Model. To create a new sub-type, click Manage Subtypes. For more information, see Configuring User-defined Events

  4. Click the General tab and do the following:

  1. optional: In the Maximum Run Time (Seconds) box, type the number of seconds you want the model to run. The default is 0 (zero), which means the model will not time out. Typically, you will want to limit the run time of the model only if troubleshooting the model (for example, one of the stored procedures is in an infinite loop).

  2. optional: Type the group number in the Model Processing Group box. The Model Processing Group number can be up to six digits.

  3. optional: In the Extended Information box, type additional information that may be useful. This is not used on any reports or displays.

  4. optional: In the Exclusions box, type the values this model is to ignore and not use to trigger the model. Use a comma to separate values.

  5. optional: Select Chain User Defined Event Times to produce a user-defined event where the start time of the current event is the end time of the previous event.

  1. Click the Identify Input(s) tab to identify and select the historian tags used for input.

  1. If the tag is to be set as a trigger, select the Trigger check box. A minimum of one trigger tag is required.

  2. Click the Browse button beside the Tag box. The Tag Search dialog box appears. Click Search (you can enter search criteria prior to clicking the button if necessary). Select the tag and click OK.

  3. From the Attribute list, select either Value or Timestamp, depending on whether you want the value or time of the tag to be passed.

  4. From the Sampling Type list, select the type of sampling that is applied to the tag. For more information on sampling types, see Sampling Types.

  5. In the Time Offset box, enter the number of seconds backward from the trigger time that the next value will be retrieved.

    For example:
    If you have trigger tag A in the list and you also have another tag B that is used as an input in the VB Script, you can specify what the time offset will be for tag B. This would be the amount of time backward from the trigger time that the EventMgr would attempt to get the ’Last Good Value’ for tag B. So if tag A changed at 9/28/07 7:00, and you specified a 10 second offset for tag B, then the EventMgr would attempt to retrieve the Last Good Value for tag B starting at 9/28/07 6:59:50.

  6. Click the Scripts tab to edit sample scripts or write script logic.

    The following functionality is available on each tab.

  7. Click . The Script Builder dialog box appears where you can edit the existing script or to write script logic.

  8. In the Script Builder dialog box:

  9. Click . The Select Alias dialog box appears. Select the Alias and click OK. The Alias letter appears in the Script box.

  10. Click Check Syntax to ensure you have entered the VB Script correctly.

  1. Click the Define UDE Name Logic tab to edit the VB Script. "UDEName" is the required keyword. This script will be used to generate the user-defined event name when the event is triggered. It will support the expression: ”UDE Name = Null” which will signify that there is no event to process and will prevent the model from firing.

  2. Click the Define State Logic tab to edit the VB Script. "State" is the required keyword. This script determines when to open or close a user-defined event. Possible values for the result are:

  3. OPEN

  4. CLOSE

  5. OPENCLOSE

  1. Click to activate the model.

See Also