Knowledge Base
How can we help? 👋
All Categories
Data Collection & Input
Meters & Consumption in Scaler: Overview

Meters & Consumption in Scaler: Overview

A conceptual overview of how meters and consumption data work in Scaler, including meter types, related data, and how to prepare for detailed meter setup.

Last updated on January 23, 2026

Purpose of this article

This article explains how meters and consumption data function in Scaler, why meter setup matters, and how to think about real-world data before configuring meters.

It is designed to prepare you for the detailed meter setup guides, not to replace them.

What meters represent in Scaler

In Scaler, meters define how performance data is measured.

They provide the structural link between:

  • Real-world data sources (meters, invoices, estimates)
  • Time-based consumption values
  • Analytics, emissions calculations, and reporting outputs

Meters do not store usage themselves. They define how and where consumption is recorded.

How meters fit into Scaler’s data model

Meters sit within Scaler's core hierarchy:

  • Portfolio
  • Asset
  • Meter
  • Consumption record

Every meter belongs to a specific asset.

If building units exist within an asset, meters can optionally be linked to one or more building units to enable tenant-level analysis.

Consumption records

Consumption records store measured usage over a defined reporting period, typically monthly.

Each consumption record may include:

  • A usage value
  • A unit
  • A reporting period (start/end date; reading date)
  • Optional cost data
  • Optional evidence or documentation

Consumption records are time-based and roll up into annual performance.

Meter types: physical vs calculated

Scaler supports two distinct meter types. Choosing the correct type is essential before setup.

Physical meters

A physical meter represents a direct measurement source, such as:

  • A utility meter
  • A sub-meter
  • An invoice-based data source

Physical meters:

  • Represent real-world measurement or documented usage
  • Can be populated via manual entry, spreadsheet upload, or automations
  • Are the only meter type that accepts direct consumption entry

When a physical meter is connected to an automation or API:

  • The Automated field is set to true
  • Manual editing of consumption values is locked
  • Consumption is updated automatically from the source system

Physical meters are typically the starting point for most assets.

Calculated meters

A calculated meter derives consumption from one or more physical meters.

Calculated meters are used to:

  • Aggregate multiple meters
  • Disaggregate or allocate consumption
  • Support framework-specific reporting logic

Calculated meters:

  • Must be manually configured in Scaler
  • Do not represent a real-world device
  • Do not accept direct consumption entry

Consumption values for calculated meters:

  • Appear in Scaler Spreadsheet exports for transparency
  • Cannot be manually edited
  • Are recalculated automatically when source data changes

For calculated meters to work correctly:

  • The Subcategory must match across all source meters
  • The Consumption format must be consistent across all meters used
Example: common area consumption

A common use case for calculated meters is separating Common Area consumption.

For example:

  • A whole-building physical meter exists
  • Tenant meters capture leased space usage
  • A calculated meter subtracts tenant usage from the whole-building total

This approach is commonly required for frameworks such as GRESB.

Data that lives alongside consumption

Meter and consumption data is often accompanied by additional inputs, including:

  • Cost data, used for spend and intensity metrics
  • Evidence and documentation, used for auditability
  • Special operational inputs, such as fluorinated gases (F-gases)

These inputs are closely related to meters but are explained in dedicated articles.

Ways to add meters and consumption

Meters and consumption data can be added to Scaler through different workflows depending on your data source and setup needs.

Understanding meter setup vs. consumption data entry

All meters must first be created in Scaler — whether you plan to enter data manually or automate it later. Meter creation establishes the structure that consumption data flows into.

Once meters exist, consumption data can be added either:

  • Manually — through direct platform entry, spreadsheet uploads, or data requests
  • Automatically — through API integrations, utility bill scraping, or other automation tools

Important: Even for automated data sources, you must first create and configure the meter shell in Scaler using one of the manual methods below.

Manual meter setup: Three workflows

These three workflows allow you to create meters and add consumption data manually:

1. Direct entry in the platform

Create meters and add consumption directly through the Data Collection Portal interface.

Best for:

  • Initial meter setup
  • One-off updates
  • Validation and corrections

2. Spreadsheet bulk upload

Use the Scaler Spreadsheet to create multiple meters and upload historical or ongoing consumption data efficiently.

Best for:

  • Creating many meters at once
  • Uploading large volumes of historical data
  • Bulk updates across multiple assets

3. Data requests

Send structured data collection requests to internal teams, external property managers, or other stakeholders who can fill in meter details and consumption data.

Best for:

  • Collecting data from external parties
  • Standardizing data collection across multiple contributors
  • Limiting what information each contributor can see

Automated consumption data

Once meters are created in Scaler, consumption data can be automatically pulled in through:

  • API integrations with utility providers or energy management systems
  • Utility bill scraping services
  • Building management system (BMS) connections
  • Third-party data providers

Critical requirement: Before automation can begin, meters must be:

  1. Created manually in Scaler (using one of the three workflows above)
  1. Mapped to the corresponding external data source
  1. Configured with matching data structures (subcategory, consumption format, etc.)

Once mapping is complete, the Automated field is set to true and:

  • Manual editing of consumption values is locked
  • Consumption updates automatically from the source system
  • The meter continues to function normally for reporting and analytics

Additional resources

For creating meters from direct data sources:

For aggregating or allocating consumption:

For complex or non-standard metering scenarios:

Did this answer your question?
😞
😐
🤩