Use Case

In certain occasions users will want to setup custom alarm functionality for non-scada related event tracking. For example, FAA lighting can be a required monitoring item for a wind farm, however OEM SCADA systems won't track the failure of the lights themselves in alarm or event form.


Background

This follows an asset model setup instead of the tag alarm setup which can be done for performance alarms. The asset model setup allows for custom tag creation, link to an asset model which can determine source, re-calculation and re-alarming for historical statistics and tracking. Additionally this allows for flexibility in filter-ability and relationships to fleet, sites, substations and/or turbines assets. 


Prerequisites

  • Administrative Access to the Portal


Steps

For a quick start example, this will walk through a site level setup for all FAA light alarms. This can be used as a reference to create other custom alarms linked to existing (if licensed) source options such as Performance or Condition Monitoring.


Step 1: Create/Verify Asset Model Setup

There are a number of asset model setup descriptions for different types of assets, for example a custom feeder setup shown here (https://bazefield.freshdesk.com/a/solutions/articles/36000128363?lang=en). 


Step 1a: Download Example of Asset Model from Portal.

If you are starting from scratch, using the Performance asset model is a good starting point. Download current configuration from the asset models edit page in the portal

Step 1b: Setup "Turbine Model" tab general settings

Example turbine model tab shown below, explanations further below. 

Note: For here we are going to go with a tag name pattern of %SITE%-%ALARM% since this asset is going to grab all site turbines so we'll need the alarms to contain the full name, i.e. SITE-WTG001-FAA-Failure - %ALARM% = WTG001-FAA-Failue.


Important RowDescriptionExample Value
Model NameHere we will have the general name, i.e. "Feeder" or "FAA Alarms". This model can have a number of assets assigned to it, so it needs to be general at some level.FAA Alarms
HasOneAlarmTagIf this asset model has only one tag that will be referenced you can set this to true. For custom alarm setups, usually you will be planning for multi tag alarms, which will lead you to put false here.False
AlarmTagNamePatternThis defines the tag name pattern. The %ALARM% relates to the "Name" column on the alarm tab in the excel configuration file. %SITE%-%ALARM%
SourceThis relates to the alarm SourceId which provides additional flexibility for the alarm log filtering.Substation


Setup 1c: Setup "Turbine Model" tab object and domain settings


These settings need to match existing setup. This may differ slightly from customer to customer for additional object types or customized attributes or references. A typical list of options in shown in the screenshot below.



The attributes shown are critical to understand the impact in different sections of the portal. For example whether these types of assets will be shown in the filter, whether they will show up in Asset Operations and which KPI's will be shown in Asset Operations. For this example will leave it under the custom asset type. Contact support or your project team to confirm these ids or names.


Note: Depending on use case, it may be better to utilize feeder, power plant controller or new item/object type instead of grouping it into Turbine. Contact support or project team if a new type is needed.


The turbine asset reference:

TypeIdCategoryIdItemTypeIdNameAttribute
2002144Turbine [{"key":"showInFilter","name":"ShowInFilter","valueType":10,"value":"true"},{"key":"operationStateDomainPoint","name":"OperationState","valueType":103,"value":"IEC-OperationState"},  {"key":"communicationStateDomainPoint","name":"CommuncationState","valueType":103,"value":"CommunicationState"},  {"key":"performanceAlarmDomainPoint","name":"PerformanceAlarm","valueType":103,"value":"PerformanceAlarm600"},  {"key":"operationKpi1","name":"OperationKPI1","valueType":102,"value":"{\"name\": \"Power\",\"point\": \"ActivePower\"}"},  {"key":"operationKpi2","name":"OperationKPI2","valueType":102,"value":"{\"name\": \"Wind\",\"point\": \"WindSpeed\"}"},  {"key":"icon","name":"Icon","valueType":101,"value":"turbine"}]


Important RowDescriptionExample Value
ItemTypeThis is the name of the Item Type referenced in the shown configuration as ItemTypeId. Wind Farm Turbine
DomainNameThe name of the domain model that will be linked to this asset model. Same as Model Name.FAA Alarms
DomainTypeIdThe type id relating the domain object type shown in above configuration200
DomainCategoryIdThe category of that object type shown in configuration above.21


Step 2: Setup Alarm Definition

In this case we are setting up a tag for each alarm on the asset model. For asset model based alarms the result has to follow 0 = Good / 1 = Alarm. For additional information please reference tag manager and calculation creation help and reference documentation.

Step 2a: Create a tag (One at a time example)

Using Tag Manager in the administration section of the portal. Select New Tag. Below is an example of an Online Expression tag for this quick start. For additional tag manager and expression syntax reference calculation help documentation.

Step 2b: Reconfigure & Recalculate to confirm tag values.

Re-configuring tags can take a few moments as well as re-calculating them. The website will post a green popup on the bottom right updating progress. Select the tag and jump to trend to validate values over your re-calculation period.

Step 3: Finalize Alarm Setup & Import Asset Model

Step 3a: Define Alarm

On the alarms tab of the asset model configuration excel sheet. Fill in the Name column to match the pattern defined on the general turbine model page.

There are additional options to explore here, as in adding lots of alarms, linking to a allocation category for availability definitions. For this quick start we'll keep it simple and proceed with what we have. Further additions and edits can be made later.

Step 3b: Upload Asset Model

Follow the TurbineModel.xlsx naming convention shown below. Save our excel file and use the portal to upload a new asset model following screenshots below.

Step 4: Create Asset this model

Navigate to the Asset Management section of the portal and click new asset under the relevant site. Follow similar definitions as below. Device connection/IO Prefix are not particularly relevant to this.


Step 5: Re-alarm to confirm

Ensure that the tag itself has values for this period where it has been active or value has been 1. Then navigate to the Data Management section of the portal and add a new job, checking the Re-import Alarms box for this FAA asset.

If you catch a re-alarm failed, contact support. The Alarm service may need to load the new configuration from the new asset model and asset created into its live configuration.


View in the alarm log to verify results are as desired.


Product Environment and Version

Bazefield Portal 8.0.27