Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Contractual KPIs

Contractual KPIs track performance requirements defined in contracts for a specific project. Proximal configures these KPIs for each project. They are not portfolio or industry benchmarks.

KPI page

The Contractual KPI page shows the KPI name and description. Select the performance-data year to view the annual performance chart and the contracts associated with that KPI.

Each associated contract has its own panel. The panel identifies the counterparty and contract execution date. When a contract document is available, it is displayed in the panel and can be opened for a larger view. If no document is available, the panel shows that it is unavailable.

Each panel has the following tabs:

  • Threshold shows the contract-defined performance targets.
  • Remedies shows contract-configured liquidated-damages information.
  • Claim shows the configured submission method, timeframe, and required information.

Remedies and Claim details may not be specified for every contract. Proximal does not calculate damages or submit claims from this page.

Thresholds

Thresholds can be configured in one of two ways:

  • Discrete annual targets show the target for each year.
  • Surface-by-device targets define a guarantee surface of warranty year (x), cycles per year (y), and guaranteed value (z). Each device has a warranty start (x_origin) and optional pre-telemetry cycle offset (y_origin).

Surface-by-device evaluation

For surface-by-device targets, the current period is the device's current warranty year: the largest tabulated x that is less than or equal to the years since that device's x_origin.

Historical cycles per year are:

(y_origin + measured string cycle count through the as-of date) / years since x_origin

Measured cycles come from the BESS_STRING_CYCLE_COUNT KPI. Missing y_origin is treated as 0.

The guaranteed value at that warranty year is linearly interpolated between neighboring tabulated cycle-count (y) points. Cycle counts outside the tabulated range are clamped to the nearest edge.

The performance and annual charts draw one applied threshold line: the simple mean of per-string guaranteed values. Strings that cannot be evaluated are omitted from the mean. If cycle data is not available, the charts fall back to showing every tabulated cycles-per-year slice.

The Threshold tab keeps the contract surface as a reference: device warranty dates, cycles at connection, and a cycles-per-year selector to explore tabulated z values.

The Applied Device Thresholds table shows the current, time-specific evaluation for each string: warranty year, historical cycles per year, guaranteed SoH, latest actual SoH, and margin. Rows below the guaranteed floor are highlighted.

If threshold data is unsupported or missing, it is shown as unavailable.

Availability of contract details

Contract documents, thresholds, liquidated-damages information, and claim instructions depend on the contract configuration for the project. When any of these details are absent, the Contractual KPI page shows them as unavailable or not specified.