KPI Packs

KPI packs are curated bundles of ready-made KPI definitions for common asset types. Installing a pack creates its definitions in your catalog disabled — each one then goes through the normal preview and enable gate, so nothing computes until you have reviewed it.

To browse packs, go to Analytics → KPIs and click Add from pack. Each pack card shows the pack version, the number of definitions it contains, the input variable keys the definitions read, and any asset attributes they require.

Installing a pack

Open a pack to see the install page. The right side lists What this pack installs — every definition with its KPI key, cadence, unit, input variables, required asset attributes, and honest notes about the calculation's assumptions. Review these before installing.

1. Under 1 · Population, pick the asset categories (and optionally a site) the pack should apply to.

2. Click Check coverage. This is a dry run — nothing is created or written. The platform resolves the population and reports, per definition, whether it can be installed and enabled.

3. Review the Coverage report:

   Result	Meaning	Effect
   Check mark	The definition is ready to install.	—
   kpiKey taken	A definition with this KPI key already exists in your organization (typically from a previous install).	Blocks install of the whole pack — nothing is installed.
   N assets missing input variables	Some matched assets do not carry the telemetry variables the definition reads.	Blocks install — narrow the population or bind the variables, then check again.
   N assets missing parameters	Some matched assets lack a required asset attribute.	Does not block install. The definitions land disabled, and enabling is held until the attributes are set.

4. If parameters are missing, the report offers fill-in fields — one value per attribute key, applied to every asset missing that key. Fill-in values are written as asset attributes when the install commits. Assets you leave unfilled keep blocking the eventual enable, not the install.

5. Click Install N definitions (disabled). A confirmation reports how many definitions were created across how many assets, and you return to the catalog.

After installing

Pack-installed definitions appear in the catalog with a pack badge recording which pack and version created them. From here they behave exactly like hand-authored definitions: open each one, preview it over real history, then enable it. Installed definitions are ordinary definitions owned by your organization — not references back to the pack — so a later pack version never silently changes KPIs you already installed.

Available packs

BESS Core KPIs

Core battery storage KPIs for BESS modules. Inputs: active_power, soc, energy_imported, energy_exported (sign convention: positive power = discharge).

Notes worth knowing before you enable:

• Discharge cycles detects cycles from signed active power with hysteresis and a two-minute debounce. Each closed cycle records depth of discharge (state-of-charge swing), energy throughput, and duration. The detection thresholds are early-version constants sized for MW-class modules.
• Round-trip efficiency is the exact counter-based daily measure (energy discharged over energy charged). Values above 100% are possible on days that net-discharge previously stored energy; the metric converges to true efficiency over multi-day horizons. Days with no charging write no point.
• Capacity health is a trend indicator — apparent capacity from daily discharge and state-of-charge swing, as a percentage of nameplate — not a certified state-of-health measure. It is meaningful on days with substantial cycling and noisy on shallow-cycling days; idle days write no point.
• Per-cycle round-trip efficiency is deliberately omitted: a discharge-only cycle sees no charge energy, so the daily definition is the honest measure.

Packs are versioned and curated by Fleetera; the catalog grows over time.