Energy reporting point properties

StartDelay

Defines how long to wait after the capture conditions are met before the Energy event is recognized or event recording is activated.

This feature can be used to filter out short events that don't significantly impact production, allowing analysis to focus on major events. In spite of this delay, Energy records treat the start time of the event as when the capture condition was first met to enable accurate time accrual.

A valid time span in the form hh:mm:ss

StopDelay

Defines how long to wait after the capture conditions have reset before closing the Energy event or event recording is stopped.

This can be used to stop multiple Energy events being triggered during startup phases where conditions are fluctuating. In spite of this delay, Energy records treat the stop time of the event as when the capture condition was first reset to enable accurate time accrual.

A valid time span in the form hh:mm:ss

CauseLocations

Defines valid locations related to this Downtime reporting point that can be the cause of a Downtime event.

When operators are selecting a cause location, they cannot select any location other than those listed here.

Use the Cause Location picker to select a cause location. For more info, see Cause Location picker.

List of locations from the project hierarchy that are valid for this reporting point

LocationIdentifier

The unique identifier for the reporting point so that AVEVA™ Production Management recognizes the reporting point from an external system.

For example, a reporting point in SAP has an identifier. You enter the SAP identifier into the LocationIdentifier property so that AVEVA Production Management recognizes the SAP reporting point. The LocationIdentifier cannot be the same as any other LocationIdentifier or EquipmentIdentifier.

String