Point Properties

Overview

Point Properties define how Points behave in Bazefield — from how data is logged and typed, to where it is stored. These settings apply to all Point types, from Raw to Bazefield Calculated Points. They ensure telemetry is captured efficiently and in a format suitable for monitoring, analysis, and reporting.

Deadband

The Deadband setting controls how sensitive a point is to changes in value. If a new value falls within the deadband range, it is not logged, reducing unnecessary data storage.

Example:
If a point has a deadband of 0.1 and its current value is 10.61, a new value of 10.68 will not be logged because the change (0.07) is less than the deadband.

Key Notes:

Configured at the Point level to allow templatization across assets.
Helps reduce noise and optimize storage in the DataEngine Historian.

Value Type

Value Type determines how data is interpreted and stored. Bazefield supports a wide range of types including Default, Boolean, Int32, Double, String, DateTime, and more.

Device Point Value Type

Defines how data is read from external sources (e.g., OPC UA, Modbus).
Default is most commonly used, which allows the DataEngine to auto-select the best type.
For some Devices, the Value Type is a required configuration. For example, with Modbus, to read one 16-bit register as an Integer, then the Device Point Value Type should be set to UInt16 or Int16. If two registers should be read (to conflate a 32-bit Integer or Float), then the Value Type should be set to UIn32 or Single, respectively.

Editing device point settings including name, source, and value type options. — *A Device Point configured with Value Type* Default; *fine for reading most OPC tags.*

Domain Point Value Type

Defines how the value will be stored long-term in the Bazefield Historian or external databases.
Default is most commonly used, which allows the DataEngine to auto-select the best type.
Can be used to store a value as a specific type, e.g., to store a Boolean (True/False) as an integer (0/1).

Settings for Blade1 Pitch Angle including value type, unit, and data template options. — *A Domain Point configured with Value Type* Default. Most Domain Points can use Default.

Point Type

Point Type defines how Bazefield handles the point internally and which Point Properties are available for configuration. For example, the Calculation Expression property is not available in the UI until CALCULATED_POINT is selected as the Point Type.

Point Type	Usage
ALIAS	Used only for Alias tags, i.e., points that simply re-map data from another point on the same domain model.
CALCULATED_POINT	Used for Online and Interval Calculations. Selecting this Point Type allows the user to configure Expression, Condition, Interval, and Period Interval properties.
CUSTOM_POINT	Used for a wide variety of points that are usually not Device-Attached, such as Availability Statistics and PostgreSQL Column Calculations.
NON_CONTROL	Used for most Device-Attached points, e.g., Raw Points and Scale Equations.
TOTALIZER	Used for Totalizer points.

NON_CONTROL is a legacy misnomer. This Point Type is used for both Read and Write points, such as those for Asset Control writes to SCADA.

*Scale Equation tag that uses* NON_CONTROL as the Point Type. The Scale Equation is defined on the Device Point.

Data Storage Templates

Bazefield uses Data Templates to determine where and how point data is stored. The choice depends on the data’s frequency and origin.

Data Template	Usage
HISTORIAN	Used for all NON_CONTROL (Raw Points), Online Calculation, and some CUSTOM_POINTs. Anytime the tag data will be updating at irregular intervals, HISTORIAN is generally used. Data is stored in the DataEngine Archive files for efficient storage and data retrieval.
IMATIS	Used for TOTALIZERs, Interval Calculations, some Raw Points (like from a Wind OEM database), and some CUSTOM_POINTs. Anytime the tag data will be updating at regular intervals, IMATIS is generally used. (See note below.)
ALIAS	Used only for Alias tags, i.e., points that simply re-map data from another point on the same domain model.
ObjectTimeSeries	Used for Availability Statistics tags.
WideTimeSeries	Used to store data in PostgreSQL.
Report	Not used except for some custom deployments.
SQLData	Not used except for some custom deployments.
TimeSeries	Deprecated

IMATIS is not recommended for data with frequency < 5-minutes (e.g., data with a frequency of 60-seconds should be stored using HISTORIAN or WideTimeSeries).