Plan where to locate Downtime reporting points

The location of Downtime reporting points is important due to the way AVEVA™ Production Management aggregates information up the project hierarchy. Ideally, each reporting point is in an autonomous location. That is, there are no other Downtime reporting points in subfolders of its branch, or in the same folder, unless autonomous subfolders are being monitored. This stops duplication of recordings and double counting of downtime durations.

A Downtime reporting point can represent a large area of the plant. The details of downtime events are recorded by the following built-in analysis fields:

• Location - Identifies the equipment or subarea where the downtime event occurred.

• Cause - Identifies the cause of the downtime. This is automatically filtered to only show causes applicable to the event location.

• Classification - Identifies the type of downtime for this event. This field follows the user-defined Time usage model for the plant. For example: maintenance downtime versus breakdown downtime.

In this way, a Downtime reporting point can accommodate a large area of plant, and still provide the necessary details to analyze downtime events.

Related topics

• Add and configure a Downtime reporting point

• About Downtime reporting points

• Add and configure a Downtime custom field