Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Production Management

Configure the Downtime Event Table

  • Last UpdatedFeb 25, 2025
  • 4 minute read

There are several steps to complete in the configuration of the Event Table matrix. This is an advanced procedure to perform.

  1. Configure SCADA

  2. Configure the connection

  3. Set Event Table properties

  4. Populate the Event Table fields

  5. Define Event Masks

  6. Turn on EnableEventTableLookup property

  7. Define Event Areas

  8. Configure Effect Mappings

1. Configure SCADA

These screens show examples only of SCADA configuration. They are provided for illustrative purposes only and occur outside of AVEVA™ Production Management. There are many ways to configure SCADA or your external source database and an experienced engineer configures this part of the procedure.

Example:

  • Configure SCADA to log alarms to an SQL Table named EventTable.

    Devices dialog box for configuring SCADA to log alarms in SQL table.

  • Configure a SCADA Alarm Category. Be certain that you set the Log Device to the device you created in step 1.

    Alarm Categories dialog box with record details.

2. Configure the connection

In Studio, configure the database connection details for the OLE-DB connection item.

Studio project hierarchy view with highlighted Connection item in Downtime module.

For more information on the database connection properties, see Downtime database connection properties.

3. Set Event Table properties

In Studio, configure the connection details for the EventTable item.

Studio project hierarchy view with highlighted Event table item in Downtime module.

For more information on the database connection properties, see Downtime Event Table properties.

4. Populate the Event Table fields

  1. Navigate to System Configuration > Downtime > Events > Event Table, right-click the Fields folder, and select Populate Fields.

    Studio project explorer view showing context menu for field in Downtime module.

  2. For each populated field, configure the Field Type and Field ID Type properties.

    Studio project hierarchy view showing list of fields under Event table in Downtime module.Studio Properties pane showing selected FieldIDType property with its context menu options.

    Set the FieldIDType for these fields as specified in this table.

    Field

    FieldIDType

    Tag

    EventName

    Area

    EventArea

    OnDateTime

    EventTime

5. Define Event Masks

  • Specify the EventMask properties for Applications folders on the plant hierarchy.

    Embedded Image (65% Scaling) (LIVE)

    The EventMask property is a regular expression used to determine the cause location from the list of possible events. This property supports a regular expression.

    Example

    For example, an EventMask of 2020CV.+ matches any EventName that contains 2020CV followed by at least one other character, such as ABC2020CV1, 2020CVTOL.

    From the filtered list of events captured in the time window, the regular expressions are used to match an event mask with an event. A match occurs when the EventName field matches the EventMask regular expression on a folder in the plant hierarchy. The match process starts from the top of the hierarchy and works down. When a match is established, the cause location is identified.

    It is important to be certain that only a single cause location results from the matching process.

6. Turn on EnableEventTableLookup property

  • Set the value on the EnableEventTableLookup property of the relevant Downtime reporting point to True.

    Studio Properties pane showing selected EnableEventTableLookup property set to true.

7. Define Event Areas

If the plant contains parallel processes, it may be helpful to limit possible events/alarms to the areas in which you are interested.

Example

StationA and StationB. The stations are two separate processes and an alarm in StationA is not relevent to Downtimes in StationB. To restrict the list of possible Downtime-causing alarms, each Downtime Reporting Point has an EventsAreas property.

  • Specify the EventAreas properties for Downtime reporting points on the plant hierarchy.

    Embedded Image (65% Scaling) (LIVE)

    The values entered into the EventAreas property should align with the area values associated with the alarms from the SCADA system.

8. Configure Effect Mappings

Add effect mapping items to the effect mapping parent and configure each item.

Studio project hierarchy view showing newly created Effect mapping item under the lookup list folder.

A matching process, like determining the cause location, also takes place to determine the effect.

This time, the EventName is matched against the regular expressions configured for each of the Effect items. When a match is established, the string value of the Effect property is selected for inclusion into the Downtime record.

After a match is established the Downtime record is populated with the event, effect, and cause location as defined by the CaptureDataWhen property for the field; for example, DowntimeStateOff.

Example

An event mask of .+TOL$ matches any event name that contains at least one other character and ends with TOL.

Example of returned results:

2020CVTOL - AVEVA™ Production Management chooses the event ending in TOL.

2020CVBLK

TitleResults for “How to create a CRG?”Also Available in