You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 8, 2023. It is now read-only.
This feature is a continuation of Wholesale settlement V1, where we calculate settlement for flex consumption metering points for all charge types.
This feature will take into account hourly consumption metering points, production metering points, and all child metering points.
The purpose of this feature is to finish the calculation engine, used for wholesale settlement.
Acceptance criterias
Perform wholesale settlement (tariffs, fees & Subscriptions) for all metering point types
Aggregate quantities (Energy and quantity) per charge per energy supplier per type of metering point
Get prices per charge
Calculate amounts
It must be possible to trigger a Wholesale fixing (D05) and Correction settlement (D32) process, with different process variants
a) Wholsale fixing: Process variant = 1st (D01)
b) Correction settlement: Process variant = 1st (D01), 2nd (D02), 3rd (D03)
Store results from the calculations
Store basis data from the calculations
Register grid loss and system correction metering points
Test data is updated with new metering points
Estimate
0,75 PI
The text was updated successfully, but these errors were encountered:
Description
This feature is a continuation of Wholesale settlement V1, where we calculate settlement for flex consumption metering points for all charge types.
This feature will take into account hourly consumption metering points, production metering points, and all child metering points.
The purpose of this feature is to finish the calculation engine, used for wholesale settlement.
Acceptance criterias
a) Wholsale fixing: Process variant = 1st (D01)
b) Correction settlement: Process variant = 1st (D01), 2nd (D02), 3rd (D03)
Estimate
0,75 PI
The text was updated successfully, but these errors were encountered: