Welcome to the charges domain of the Green Energy Hub project
The charges domain is responsible for keeping track of price lists of Grid Access Providers and Transmission System Operators (TSO). A charge may be a fee, a subscription or a tariff, where the latter has the option of being a tax.
In addition, the charges domain also keeps track of which of these prices are assigned to a specific metering point at any given moment in time.
These are the business processes maintained by this domain.
For more information on the system flows supporting the above-mentioned business processes, please see the process-flows folder.
Learn how to get started with Green Energy Hub here.
Learn how to get a development environment up and running for development, debugging, testing or evaluation purposes here.
The architecture diagrams below illustrate both current state of the Charges domain as well as future work, last-mentioned being illustrated by grey arrows and components with lowered opacity.
The diagrams depict the architecture of Charge Information, Charge Prices and Charge Links, respectively.
Please note, all the azure functions displayed in the architecture diagrams are hosted in the same function host. Also, some components have singular names while others have plural names. This is intended. The components using plural may need to process a bundle of e.g. charge links to determine whether an operation, e.g. validation, was successful.
Below depicts architectural components which supports the Charges domain in fulfilling its business purpose. One such example is consuming market participant integration events published by the Market Participant domain. Market participant data is required to authenticate and authorize the sender of incoming requests.
This sections documents the data flows to and from the Charges domain.
If you are interested in the public contracts of the Charges domain, please visit this page.
Planned work for Charges:
- Add a variety of front end capabilities:
- Show and access messages received for a given charge.
- Show a charge's active timeline as per a user-defined date and time. Implicitly this entails defining and implement a charge historical data model.
- Enable traceability between the operation id causing the state change on the timeline and the message in which it was received.
Read about community for Green Energy Hub here and learn about how to get involved and get help.
Please note that we have provided a Dictionary to help understand many of the terms used throughout the repository.