This article covers how to set under-performance detection rules through the Bazefield Power Curve application, and visualize the alarms created in the Alarm Log and the heat map widget.
Often, machine power curves may under perform their contractual guaranteed performance curves for various reasons, including ambient temperature, internal de-rates, icing, or other environmental conditions. While some under-performance can not be controlled nor fixed, some occurrences are addressable through smarter operations or parameter changes in the machine software. This article walks through how to set and test the validity of under-performance thresholds that can be used in Bazefield to monitor under-performance of the machines in real time.
This article assumes the user has basic knowledge and experience with turbine power curves, and has used the existing Bazefield power curve tool for basic analysis.
After following theses setup steps you can view these alarms and alert
Step 1: Open Power Curve App / Find Asset/Models
The power curve application doesn't load with an asset selected. Once the application is selected, use the filter on the right side of the site page. For performance alarms, you can apply the same calculation or alarm criteria across all models, so selecting one typical turbine in that model can be useful.
Note: The Performance alarms point to the Performance Index tag which is the Active Power vs Theoretical Power when expected run mode. This may be different from install to install. (reference article for generic tag list description for wind assets https://bazefield.freshdesk.com/a/solutions/articles/36000188552 ). Selecting "Performance" from Contractual vs Fitted won't impact the curve used.
Note: If you looking to compare across turbines with the same model utilize the compare page
Within the graph section of the power curve that is shown in the picture above, it will automatically load 3 series, Actual, Fitted and Contractual. Actual contains the binned raw data from the tags setup in the Settings section of the portal. When you hover over the Actual scatter points the points will be displayed as a reference.
Note: Depending on customer requirements and data availability, these may be linked to 10 minute SQL data, or real time OPC tags
Step 2: Pick the Curve / Determine the Under performing Criteria
When selecting the performance link, shown as #8 above, the pop-up below with show up. These define the equation for performance detection.
Note: When searching for under performance, it is best practice to tune the detection thresholds on a single asset using re-calculation and re-alarm to test findings. If a small percentage is shown over a short period of time you will be getting numerous alarms that create a lot of noise making it difficult to track actual under performance.
The default settings are 6 hours, 5% and a minimum calculation threshold of 10 kW. To create the alarm, follow the pop-up options and check save.
Step 3: (Advanced) Validate Tag Alarm Creation
The UI under the Power Curve application creates the calculated tag called <AssetName>-PerformanceAlarm600. This tag can be viewed, edited and re-calculated in the Tag Manager application.
Example general section here shown for reference, this one in particular is on a multi-host environment, thus showing the 2nd IO Server, Library and Tag Engine.
The Attributes section of the 'Edit Tag' page shows the equation generated from the prompt from the power curve application, the table below describes the link.
|Time Detection Period||3 & 4|
|Change In Performance||2|
|Minimum detection Power||1|
Note: From this attributes section you can view the tags associated with this alarm. These are defined in configuration file for the particular customer installation. Contact support or your product delivery team for reference.
Step 4: (Advanced) Re-configure tag
When making edits to the performance alarm parameters or tag itself, you will need to re-configure the tag. Also if you wish you have this performance alarm applied to the past, you will need to re-calculate the tag after re-configuring to generate data for that particular interval.
Note: If you want to re-alarm in the past please contact support to trigger those jobs.
Step 5: View Performance Alarms
Viewing performance alarms by default can be done using the Alarm Log. The Alarms themselves, as well as the statistics page under the alarm log to help rank, count and provide some statistics around the occurrences. In addition these can also be pulled into Allocations in the availability application.
Bazefield Portal 126.96.36.199