Successive Exception Report

IMPORTANT: When you upgrade to AVEVA Mobile Operator 6.0.0, the number of records displayed in Successive Exception Report will be less as compared to the reports in the earlier version. This is because the severity "Normal" is no longer considered as an exception and therefore, you will only see the records that has actual exceptions

The Successive Exception Report retrieves data points that are consecutively in a multiple exception condition. You can use this report to determine how long a data point (which typically represents an asset) remains in an alarm state (ie. the data point was in exception). For example, with the exception count at =5, only those assets that have triggered a criticality (Data Filter) at least five times in a row within the specified period of time will be returned.

You can change the filter to report how many times a data point is in exception. For example, reporting only items where a data point was in exception 4 times consecutively. You can also specify which exceptions to take into account. For example, reporting all data points that triggered criticalities (Data Filters) 2, 3 or 4 for more than 4 consecutive readings.

The Successive Exception Report includes two key search configurations: Exception Count; and Earliest Start Date.

Exception Count

Use the Exception Count to filter the report to show only those exception items which have met or exceeded the criteria for a specified frequency. The minimum exception count is 0.

Earliest Start Date

The Earliest Start Date value specifies a starting date prior to the Begin Date which is used to limit how far back the query searches to find the first exception.

This setting is necessary in order to find successive exceptions that span reporting periods.

Example: Assume that this report is run, with the Exception Count value set to 5, on the first day of every month against data gathered the previous month. Further assume that Asset XYZ, which is polled once daily, has triggered an exception only on the last three days of March, and the first two days of April. Without the Earliest Start Date value, a report run on May 1st would not return data on this asset, because during the specified period (April 1st – April 30th) the asset only triggered two exceptions. With Earliest Start Date set to March 28th, however, five consecutive exceptions are found and displayed by the report.

The Successive Exception Report returns the following data point items for the selected Plant.

• Base – Name of the base to which the procedure belongs.

• Procedure – Name of the procedure.

• Task Group – The task group name that the task is assigned to. Task assignment is made within Procedure Builder – Tasks (see the Procedure Builder section of the "Management Center User’s Guide").

• Task – The title of the task presented to the field user.

• Asset – The asset number associated with the completed task.

• Successive Exception - The data points that are consecutively in a multiple exception condition.

• Begin Date – The first date that the data point met the exception criteria; if blank, the data point was in exception before the Back Date of the report.

• End Date – The last date the data point met the exception criteria; if blank, the data point did not move out of exception by the Max Date of the report.

• Data - The data of the data filter.

• Severity Level - The Severity level assigned to this Data Filter in Procedure Builder’s List Manager along with the severity color assigned to the data filter.

• Signature - Signature of the operator who executed the Procedure.