The Standing Data section allows users to define reusable, configurable parameters that can be referenced in calculation logic across the system. This functionality is essential for maintaining business rules, regulatory parameters, and operational constraints that change over time but need to be applied consistently across contracts, portfolios, and market operations.
Typical Use Cases:
Tolerance thresholds: Define acceptable deviation limits for delivery obligations (e.g., ±5% volume tolerance for bilateral contracts, ±2% for imbalance positions). When market conditions or regulatory requirements change, update the tolerance value with a new Valid From date, and all relevant math editor formulas apply the new threshold.
Tariff structures: Maintain grid access tariffs, transmission fees, or capacity charges that vary by time period. For example, define a "Network Use of System Charge" parameter that changes quarterly based on regulatory decisions—all cost calculation formulas referencing this parameter automatically reflect the current tariff.
Values can be maintained with a Valid From date, enabling time-dependent configuration of these parameters. They can be referenced in Math Editor expressions and Math Editor Templates, and through them influence pricing logic, volume calculations, KPI definitions, or other derived results.
When a Standing Data value changes with a new validity date, any calculation that references it reflects the updated value according to the applicable time period. Standing Data therefore supports the centralized maintenance of reusable calculation parameters with full auditability and historical accuracy.
Structure
Standing Data is organized in two levels:
Standing Data Fields
Defined under Administration → Standing Data Fields.
The user selects Add to create a new parameter definition and specifies:
Name
Description (optional)
Unit of Measure
Field Type
This defines the structure and format of the parameter.

Standing Data Values
Maintained under Data Room → Standing Data.
For each defined field, the user selects Add Value and inserts:
Value
Valid From date
Multiple entries can exist for the same field, allowing the parameter to change over time without overwriting historical configurations.
Field Types
Available field types include:
Decimal
Int
Boolean
Timeseries
DateTime
String
The selected type determines how the parameter can be referenced within calculations.