Purpose of this article
This article explains the minimum asset setup required in Scaler before data collection begins. It covers what must be completed to save an asset, what is required to run calculations, and which details can be added later.
What is an asset in Scaler?
An asset in Scaler represents a single physical building.
Each asset:
- Belongs to one portfolio
- Contains asset-level characteristics and reporting details
- Is the container for meters, consumption data, and building units
Assets are the foundation of operational data collection in Scaler.
Adding an asset
Assets can be added to Scaler in several ways:
- Manually through the Data Collection Portal
- Via spreadsheet upload
- Via API or automations
During onboarding, many teams add assets manually or via spreadsheet, then refine details later.
Related article:
Required fields to save an asset
To save a new asset in Scaler, all required fields must be completed.
When adding assets in the platform
When adding or editing an asset manually, required fields are indicated with a star (*) in the interface.
At a minimum, the following fields must be completed to save an asset:
Asset name
Client ID
Country
Asset unit system(metric or imperial)
Main property type
Main property subtype
Owned since
Active in analytics
Active in reporting outputs
Once all required fields are completed, the asset can be saved and will appear in the portfolio.
Required fields are always indicated directly in the platform with an asterisk (*).
When adding assets via spreadsheet
When adding assets via the Scaler Spreadsheet, required fields are identified differently.
In the Asset details sheet:
- Row 9 (Requirement) labels required fields in dark grey
All required fields must be completed for each asset in order for the upload to succeed and for assets to be created in Scaler.
If any required spreadsheet fields are missing, the upload will fail and the asset will not be added.
Related article:
Floor areas required to run calculations
Saving an asset allows it to exist in Scaler. To run calculations and populate analytics, floor area data is also required.
Scaler requires the following three floor area fields:
Gross floor area (GFA)
GFA – common area
GFA – tenant area
The common area and tenant area values must add up to the gross floor area.
These values are used to:
- Calculate intensity metrics
- Support benchmarking and targets
- Enable analytics and reporting outputs
Floor area fields use the asset unit system and cannot be adjusted per entry.
Asset unit system
Each asset has its own Asset unit system (metric or imperial).
The asset unit system determines:
- Units for asset-level fields where units cannot be adjusted per entry
- How values such as floor areas are recorded
Assets within the same portfolio may use different unit systems, even though reports are generated using the portfolio's default unit system.
Related article:
Required fields vary by reporting framework
In addition to the minimum setup required to save an asset and run calculations, different reporting frameworks require additional fields.
For example:
- For GRESB, asset
Status(e.g.standing investment,new construction,major renovation) must be specified
- The selected status determines which additional reporting fields become required
As reporting frameworks are enabled, Scaler dynamically evaluates required fields based on:
- Portfolio configuration
- Asset characteristics
- Reporting framework logic
You do not need to complete all report-specific fields during onboarding. Focus first on saving assets and enabling calculations.
Asset groups (optional during onboarding)
Asset groups allow multiple assets to be treated as a single reporting unit.
Asset groups are useful when:
- Multiple buildings function as one operational site
- A single investment spans several buildings
- Reporting frameworks require aggregated views
Asset groups can be created or adjusted later without affecting underlying asset data.
Building units (optional)
Building units represent leased or occupiable spaces within an asset.
They are typically used when:
- Tenant-level or space-level performance is required
- Sub-metering exists within a building
Building units are optional and can be added after baseline asset setup.
What to review before moving on
Before proceeding to meters and consumption, confirm:
☐ All required (*asterisk) asset fields are complete
☐ Asset unit system is correct
☐ Floor areas are entered and internally consistent
☐ Asset is active in analytics and reporting
This ensures calculations can run successfully and analytics will populate as expected.
Additional resources
Once asset setup is complete, continue with:
- Data onboarding: Process overview — End-to-end onboarding workflow
- Meters & Consumption in Scaler: Overview — Understanding meters, consumption records, and data entry