-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Modification of energy billing and invoicing enumeration values #419
Comments
Time Of Use enumeration within “usage” transactions This field should be made optional as some C&I usage charges do not have a time band associated with the charges. For example, charges could be based on total consumption, a percentage of total consumption or another calculation method. There needs to be flexibility to be able to support these charges. If this field cannot be made optional then include “FLAT” as an enumeration value Enumeration list for usage units & billing units Enumeration for quantity unit
Enumeration for rate unit
|
Thank you for your feedback @priyaH-OriginEnergy
At the moment we are proposing no change to the "Time Of Use" enumeration because we believe single use charges can accommodate within "onceOff" transaction.
We will add the above ENUMs within optional fields with kVa as default for quantity unit and $/kVA as default for rate unit. We can discuss the above changes further in implementation calls and amend the recommendation if required. |
This change was incorporated into release v1.15.0. Refer to Decision 212 for further details. |
Description
In the recently published candidate standards for energy there were a number of enumeration fields included in the payloads. Initial values and descriptions for these enumerations were defined but these may not be comprehensive
Area Affected
Energy APIs and payloads
Change Proposed
Review the enumeration fields across the energy APIs, specifically the billing and invoicing payloads to ensure the enumeration lists are well described and comprehensive
The text was updated successfully, but these errors were encountered: