---
title: "Calculated Points"
slug: "calculated-points"
status: "update"
updated: 2025-07-16T14:06:39Z
published: 2025-07-16T14:06:39Z
canonical: "docs.bazefield.com/calculated-points"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bazefield.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Calculated Points

## Overview

**Calculated Points** are virtual telemetry streams generated within Bazefield via the Calculation Service. Unlike Raw Points, which come directly from devices, Calculated Points are derived from existing data to provide **deeper insights**, **standardization**, and **advanced analytics**.

There are two main types: **Interval** and **Online Calculations**.

- **Interval Calculations** run on a set schedule and store values at **regular intervals** (e.g., evaluation every 5 minutes, stored at the bottom of the hour).
- **Online Calculations** run based on their input(s) and store values at **irregular intervals** (i.e., the Online Calculation evaluates when its input(s) change value).

---

## Key Characteristics

- **Distributed**: Calculations are evaluated on Bazefield Storage Nodes so that processing load is distributed across multiple resources.
- **Configurable Logic**: Built using one-line expressions or for more complex logic, custom Calculation Models. Both are configured in the Bazefield Portal.
- **Flexible & Scalable**: Ideal for normalizing data across vendors or implementing custom KPIs.

---

## Data Structure

Calculated Point data includes:

- **Name**: Logical identifier (e.g., `ExpectedPower`)
- **Timestamp**: Time of calculation
- **Value**: Computed result (e.g., `102.3 kW`)

---

## Example

A Calculated Point like `ExpectedPower` might use:

- **Inputs**: Irradiance, wind speed, and asset specs like rated power
- **Logic**: A model that forecasts power output (e.g., park available capacity factor or a custom power curve lookup)
- **Output**: A real-time estimate of what the asset *should* be producing

![](https://cdn.document360.io/a0786c0f-b171-4b24-8860-c32eb7ef2738/Images/Documentation/image(217).png?sv=2026-02-06&spr=https&st=2026-11-06T20%3A39%3A50Z&se=2026-11-06T21%3A39%3A50Z&sr=c&sp=r&sig=oQx1nITbPahM9HWlsLA%2FT5dyrkbZcMa1%2Bx%2BQ4%2BH296I%3D)

*Example Interval Calculation for ExpectedPower (from Asset Model > Point Template > Point)*

---

## Why Calculated Points Matter

✔️ **Performance Benchmarking**: Enables comparisons between actual and expected output.

✔️ **Standardization**: Normalizes telemetry across different OEMs and SCADA systems.

✔️ **Advanced KPIs**: Powers metrics like availability, curtailment, and performance ratios.

✔️ **Automation**: Supports alarms, rules, and operational logic.