Solar Farm
The Solar Farm is a core asset type in the Bazefield platform representing a physical solar plant. It serves as the foundational asset for collecting, organizing, analyzing, and visualizing operational and performance data. One solar site is uniquely identified in the Bazefield platform. It is linked to sub devices including inverters, weather stations, meters that form the solar farm asset hierarchy.
Functional Description
A Solar Farm (also known as a Solar Power Plant) is a utility-scale facility designed to collect solar energy and convert it into alternating current (AC) electrical power. This is achieved through a coordinated array of solar panels, which collect and produce direct current (DC) power, as well as connected inverters to convert the power to alternating current. The panels may be mounted on the ground or rooftop, and may be arranged for string or central inverter types. The combined electrical output of these inverters 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 Solar 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 solar 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, solar site with attached storage is modelled as Solar & Storage Facility, with logical solar site PV Site and Attached ESS as children.
.png?sv=2022-11-02&spr=https&st=2025-07-17T14%3A53%3A32Z&se=2025-07-17T15%3A09%3A32Z&sr=c&sp=r&sig=IZBF3OZFq7cnw6UqRyt%2F7vFz4NvcztrRtFNMhsv5lH0%3D)
A solar facility with attached storage modelled using Physical and Logical sites.
Core Data Model
While the data model of solar farms will vary according to the design, Bazefield offers a pre-installed CORE data model to account for the most common points, events, and attributes relevant to all solar farm set ups. Model by model variations are then handled typically through smart Model Inheritance.
.png?sv=2022-11-02&spr=https&st=2025-07-17T14%3A53%3A32Z&se=2025-07-17T15%3A09%3A32Z&sr=c&sp=r&sig=IZBF3OZFq7cnw6UqRyt%2F7vFz4NvcztrRtFNMhsv5lH0%3D)
Example of a common modeling strategy to encompass variations of data between inverter manufacturers and site specific SCADA configurations at the plant 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 | |
---|---|---|---|
PV Installed Capacity (MW DC) | pvInstalledCapacity | The total capacity of all components on the DC side. It is theoretically equal to the sum of the capacity of all components on the DC side of all inverters. |
|
Latitude | latitude | The latitude of the power plant. |
|
Longitude | longitude | The longitude of the power plant. |
|
Node ID | nodeId | System configuration. Used by the system for location of data source (Buffer/Edge DataEngine Node ID) |
|
Site Rated Power (kW AC) | siteRatedPower | Enter the maximum plant production at the point of interconnection - for the Map table |
|
Number of Assets | numberOfAssets | Number of Inverters for this site. They are used in calculations and applications to represent the number of assets. |
|
Time Zone | timeZone | Select this site local time zone. |
|
Notification Roles | notificationRoles | Default Notification Role |
|
Default Allocation Type | defaultAllocationType | Default Allocation Type for Asset Operations |
|
Weather Forecast | weatherForecast | System configuration. Integration Service/weather forecast data provider. |
|
Planned Availability Interval | plannedAvailabilityInterval | Availability Planner configuration. Default/Fixed interval in minutes used for planned availability. |
|
External Device ID | externalDeviceId |
| |
Inverter Rated Power (MWac) | inverterRatedPower | The rated output power from the AC side is equal to the sum of all inverters rated capacity from the AC side. |
|
Commissioning Date | commissioningDate | When the power plant is connected to the grid. |
|
Installation Type | installationType | The terrain of the site. |
|
City ID | cityId | City ID for Solar AI |
|
Currency (Current Code) | currency | Preferred currency to display. Country Currency Codes ISO 4217 (i.e. USD, EUR, NOK..) |
|
Central Inverter Amount | centralInverterAmount | The number of the central inverters onboarded to this site. |
|
String Inverter Amount | stringInverterAmount | The number of the string inverters onboarded to this site. |
|
Weather Station Amount | weatherStationAmount | The number of physical weather stations that are onboarded to this site. |
|
DC Combiner Box Amount | dcCombinerBoxAmount | The number of the DC combiner boxes onboarded to this site. |
|
Energy Meter Amount | energyMeterAmount | The number of energy meters that are onboarded to this site. |
|
Grid Meter Amount | gridMeterAmount | The number of grid meters that are onboarded to this site. |
|
Other Meter Amount | otherMeterAmount | The number of other meters onboarded to this site. |
|
Wash Cost [Currency/kWdc] | washCost | Wash Cost [Currency/kWdc] |
|
Nominal Plant Capacity (MW AC) | nominalPlantCapacity | Enter the maximum authorized plant production at the point of interconnection if limited by a plant controller. If not limited, leave empty. |
|
Delta Temp Mod from Sunlight (a) | deltaTempModSunlight | Factor for Bifacial sites. |
|
Delta Temp Mod Wind Speed (b) | deltaTempModWindSpeed | Factor for Bifacial sites. |
|
PVsyst PR | pvsystPr | Theoretical PR, 0.78 by default if left empty. |
|
Manufacturer Weighted Efficiency | manufacturerWeightedEfficiency | Input Manufacturer Weighted Efficiency in decimals, example 0.985. |
|
Albedo Factors | albedoFactors | Monthly albedo values for bifacial sites. Make sure to add exact 12 values separated by a comma. Example: 0.4,0.4,0.25,0.25,0.25,0.25,0.25,0.25,0.25,0.25,0.25,0.4 |
|
Calculate Timezone | calculateTimezone | Indicate a different timezone for calculations within EnOS timezone batches. |
|
Onboarding Date | onboardingDate | The date the site is connected and uploads data to our system, with daily KPI also starting to generate. It should be later than the commissioning date. From the commissioning date to the day before onboarding, KPI needs to be initialized using the offline record. |
|
PPA Rate (Unit/MWh) | ppaRate | Used to calculate the revenue. Revenue = production x unit price of electricity. The default value is 0.88 if this field is left blank. |
|
Altitude [m] | altitude | Altitude of this site. |
|
Observation Time | observationTime | Used for to set the calculation method for calculating the 5 min average value. Standard should be START. |
|
Expected Frequency (s) | expectedFrequency | Unit is seconds; default value of 300 (i.e., 5min). |
|
Meter ID | meterId | Meter ID |
|
Energy Model Reference | energyModelReference | Used for display of loss decomposition-theoretical loss, typically given in PVsyst reports or similar. Example: {"expected_prwc": "80.45", "energy_production_assumption": "1380", "lost_shading": "2", "lost_soiling": "1.5", "lost_module_thermal": "5", "lost_reactive_power": "0.1", "lost_efficiency": "1", "lost_down_time": "2", "lost_clipping": "1.7", "loss_night_time": ""} |
|
Ensight Arguments | ensightArguments | This attribute will contain multiple parameters that can be set to adjust algorithms or the way that Solar is executed. |
|
DC System Voltage (V DC) | dcSystemVoltage | 1000V or 1500V: Enter the value closest to the maximum DC input voltage of the inverter. |
|
Corrective Action Arguments | correctiveActionArguments | Corrective Action Arguments |
|