Overview

Asset attributes are fixed, descriptive properties that define what an asset is, not what it does. Unlike time-series data (points), which track performance or behavior over time, attributes are static values that help characterize, group, and interpret assets consistently across your power plant or fleet.

In Bazefield, every asset comes with a set of core attributes defined by its Asset Type — and in many cases, users can add their own custom attributes to meet project- or fleet-specific needs.

Definition

An attribute is a named key, value pair assigned to an asset. It could be something structural (e.g. "Rated Capacity"), contextual (e.g. "OEM"), or organizational (e.g. "Region"). It could even be a calculation parameter (e.g. “System Efficiency”) to be used for later analytics or points.

These attributes:

Help categorize and group assets
Drive filtering and navigation in dashboards
Are used to parameterize logic in reports, rules, and calculatoin engines
Enable uniform behavior across similar assets, even when their telemetry or SCADA tags vary

Examples of Common Attributes

Attribute	Description
`Name`	The display name of the asset
`Asset ID`	A unique, system-wide identifier
`Type`	The general classification (e.g., “Wind Turbine”, “PV Inverter”)
`Model`	The specific asset model variant
`Commissioning Date`	Date the asset became operational
`Rated Power (kW)`	The nameplate power rating
`Region`	A user-defined tag to group assets geographically or organizationally
`Collection Feeder`	For AC power assets, the feeder they are tied into
`Substation`	Parent or downstream interconnection context

Where Do Attributes Come From?

Asset attributes are defined by the Asset Type the asset is based on. The Asset Type governs which attributes are required, or optional. By default, attributes are not assigned a value on a specific asset, unless the user sets a “default value” associated with them based on its Asset Type.

The image below shows an example of a core set of weather station attributes. When users or administrators create a new asset on a solar farm of type Weather Station, they will then be prompted to populate required attribute fields before saving the asset.

If the desired behavior is to pre-populate an attribute with a default value for every asset of a given asset type, the Default Value field can be used.

Default values can be set on attributes to serve as the default suggested value for all assets

Populating Asset Attributes in Bazefield when managing or building a power plant hierarchy

Why Attributes Matter

✔️ Clarity & Consistency
Standardized attributes make reporting and analysis cleaner and more comparable across assets, sites, or fleets.

✔️ Automation & Customization
Attributes are often referenced in custom data models, calculations or BI dashboards & reports— making them a key part of automation.

✔️ Model-Driven Uniformity
Attributes defined in Asset Models ensure each asset type is represented with the same key characteristics, no matter the OEM or SCADA structure.

✔️ Asset to Asset Relationships
While assets can be placed in 1-1 parent/child relationships, it sometimes is required to model reference assets or siblings. For example, every PV inverter has a reference weather station attribute that picks the weather station on the same power plant that is used to define its irradiance source for expected energy calculations