Wind Farm (WF)
A Wind Farm in Bazefield represents a collection of wind turbines and supporting balance of plant equipment grouped geographically or operationally under a single entity, with a single tie-in to the external grid. It acts as a parent-level object that aggregates operational, financial, and availability data from all associated turbines. Wind Farms are commonly used to model ownership structure, grid-level reporting, and SCADA-level oversight across a fleet.
Functional Description
A Wind Farm (also known as a Wind Power Plant) is a utility-scale facility designed to convert the kinetic energy in the wind into alternating current (AC) electrical power. This is achieved through a coordinated array of wind turbines, each equipped with a generator and control system. The combined electrical output of these turbines is typically collected at an on-site substation, where it's transformed and fed into the electrical transmission grid via a single point of interconnection (POI).
In Bazefield, the Wind Farm object type represents this entire power-producing entity — enabling monitoring, control, and reporting at the plant level. It serves as the top-level structure for aggregating turbine-level data, managing grid-level compliance, and analyzing overall site performance.
Logical Site
A wind farm asset type is specifically a Logical Site.
In Bazefield, the concept of a site is split into two layers — Physical Site and Logical Site — to provide accurate modeling of complex facilities that host multiple grid-connected systems. A Logical Site represents a distinct operational unit within a physical facility, usually aligned with a single point of interconnection (POI) to the electrical grid. It includes the set of assets (e.g., turbines, inverters, batteries) and control boundaries responsible for generating or storing power under a specific market registration, utility agreement, or revenue stream.
A Physical Site represents the shared physical facility or location where power-generating assets are installed. This includes common infrastructure such as access roads, fencing, communications equipment, and substations. A physical site typically maps to a real-world geographic footprint and can encompass multiple independent or dependent logical sites.
An example of how to use physical site asset types and logical site asset types together in modelling is shown below. Here a large, 4-phase wind powerplant is modelled as a Physical Site Wind Facility 1, with logical sites Wind Plants 1-4 as children.
.png?sv=2022-11-02&spr=https&st=2025-07-17T19%3A25%3A28Z&se=2025-07-17T19%3A41%3A28Z&sr=c&sp=r&sig=k3CuNQK8%2BK3PAs2NyEfgfHlap2sZ3NYJK1c%2BtULkVHk%3D)
A wind facility modelled using Physical and Logical Sites
Core Data Model
While the data model of individual turbines may vary by vendor, Bazefield offers a pre-installed CORE data model to account for the most common points, events, and attributes relevant to a wind farm. Model by model variations of wind farms of different underlying vendors are then handled typically through smart Model Inheritance. The image below shows an example model hierarchy of how inheritance can help organize the data for a large group of wind farms in a fleet.
.png?sv=2022-11-02&spr=https&st=2025-07-17T19%3A25%3A28Z&se=2025-07-17T19%3A41%3A28Z&sr=c&sp=r&sig=k3CuNQK8%2BK3PAs2NyEfgfHlap2sZ3NYJK1c%2BtULkVHk%3D)
Example of a common Modelling Strategy to encompass variations of data between turbine manufacturers and site specific SCADA configurations at the site level.
Core Attributes
Attributes are fixed key, value pairs used to represent non-time series data associated with each asset (read more about Attributes). While attribute values can differ from asset to asset, critical shared (e.g. CORE) attributes defining a wind turbine asset type, pre-installed in Bazefield are described below. These are often pre-requisite data required for the Bazefield applications to function fully.
Required for basic Bazefield Core functionality
Optional attributes for common additional modelling
Attributes marked with “** “ are only applicable to North American clients with wind farms requiring to submit GADS Performance and event reporting.
Depending on your version of Bazefield, there may be additional advanced attributes not listed here to support data integrations or migrations with other systems.
Attribute | Key | Description | |
---|---|---|---|
Capacity(MW) | capacity | The total installed capacity of the farm in Megawatts. | |
Latitude | latitude | GPS coordinate for the site location. For a definition of WGS 84, please refer to https://earth-info.nga.mil/?dir=wgs84&action=wgs84. | |
Longitude | longitude | The longitude of the power plant. | |
Time Zone | timeZone | Select this site local time zone. | |
Default Allocation Type | defaultAllocationType | Default Allocation Type for Asset Operations | |
Weather Forecast | weatherForecastType | System configuration. Integration Service/weather forecast data provider. | |
Number of Assets | enabledAssets | Number of Assets for site calculations | |
Notification Roles | notificationRoles | Default Notification Role | |
Planned Availability Interval | plannedAvailabilityInterval | Availability Planner configuration. Default/Fixed interval in minutes used for planned availability. | |
Max Power (MW) | maxPower | Enter turbine max power (rated). Used by max limits for dashboards | |
Asset Active Power Primary | assetActivePowerPrimary | This signal will be mapped to the standard point 'ActivePower.10m'. It is used by the system in the calculation of a number of KPIs. It should be a historical database signal. | |
Asset Active Power Secondary | assetActivePowerSecondary | This signal will be mapped to the standard point 'ActivePower'. It is used by the system in the calculation of a number of KPIs. It should be a raw/live signal. | |
Asset Wind Speed Primary | assetWindSpeedPrimary | This signal will be mapped to the standard point 'WindSpeed.10m'. It is used by the system in the calculation of a number of KPIs. It should be a historical database signal. | |
Asset Wind Speed Secondary | assetWindSpeedSecondary | This signal will be mapped to the standard point 'WindSpeed'. It is used by the system in the calculation of a number of KPIs. It should be a raw/live signal. | |
Performance Index Cut-In Threshold | performanceIndexCutInThreshold | Specify the threshold added to the Cut-In wind speed as the condition on when to calculate the Performance Index KPI. Default set to 2 m/s. Reference the expression for the Performance Index in the document “Wind Standard KPI and Calculations”. | |
Preferred Calculation Model | preferredCalculationModel | Preferred Calculation Model for Energy calculation. Choose between theoretical model or potential model. The former is based on Wind Speed and Power Curve of target or neighbouring turbines, the latter is based on actual power of neighbouring turbines or site average power. | |
Scheduled Delay | scheduledDelay | Interval Calculations Schedule Delay (in seconds). Delayed data require a scheduled delay to wait until data available. Recommended to set to 1800s as default. | |
Entity ID** | entityID | The NERC Compliance Registry ID number (NCR ID) or voluntary reporting ID assigned by NERC of the organization that owns or operates the plant. | |
Region** | region | The region code for the NERC Region where the Plant is located. | |
Plant ID** | plantID | For new plants, this field will be left blank to indicate that a plant ID is being requested. For updates to a plant configuration, enter the Plant ID assigned by the GADS Wind reporting application. | |
Plant Name** | plantName | The Plant name. Use the same plant name as reported to EIA. | |
EIA Plant Code** | eIACode | The Form 860 EIA Plant Code of the facility as reported to EIA. | |
ISO Resource ID** | plantISOID | If applicable, the unique plant identifier assigned by the ISO or RTO. | |
Forecast Energy Point used in ISO Export | plantISOExportForecastEnergyPointName | If using the forecast energy included ISO Planned Availability Export format. This is the site reference forecasted energy. | |
Forecast Energy Aggregate used in ISO Export Point Data | plantISOExportForecastEnergyAggregate | If using the forecast energy included ISO Planned Availability Export format. This is the aggregate type used to pull point data. | |
Country** | country | The country where the plant is located. | |
Nearest City** | nearCity | Name of the city closest in proximity to the plant. | |
Annual Average Wind Speed (m/s)** | AAWS | The average annual wind speed (AAWS) at 80m, measured in meters per second. Mandatory for the Theoretical Power calculation. | |
State/Province** | state | The State/Province abbreviation where the plant, subgroup, or energy storage is located. | |
Connected Energy Storage | onsiteStorage | Indicate whether the facility has any type of energy storage that is electrically connected to a renewable energy generating facility and installed on-site as part of the plant. | |
Plant Capacity at POI (MW)** | cPOI | Plant Capacity at Point of Interconnection (MW). This is the capacity of the Interconnection agreement or threshold. This capacity differs from installed capacity of equipment reported at the Subgroup level. | |
Plant Ownership Status** | plantOwnStatus | State of ownership (GADS) |
Certified Product Templates
This section will describe the common, shared point, event, and other data templates applicable to a wind turbine asset type pre-installed by the Bazefield product team.
Coming Soon