Power Systems Data Working Group (WG2)
An open specification for raw electric power system data to facilitate a systematic and more accurate approach to report grid emissions.
This working group focuses on creating a unified specification for data retrieved from power system operators.
Power system data might include, but is not limited to:
- Generation mix
- Power imports and exports
- Power market data
- Delivery capacities and/or constraints
- Power generation emissions
This common standard shall enable grid decarbonisation pathways and decision-making. By aligning the definition of the data shared by power system operators, this specification will make it easier for third parties to consistently compute (using their own carbon models) and report grid emissions worldwide.
These are the official specifications written by this working group.
CDSC-WG2-01- Grid Topologies [Overview] [Specification]
CDSC-WG2-02- Data Types [Overview] [Specification]
CDSC-WG2-03- API Interface [Overview] [Specification]
CDSC-WG2-*- Additional specifications will be added in the future
CDSC-WG2-01 - Grid Topologies is used to develop a shared terminology for various levels of granularity of grid entities and a convention for describing how those entities relate to each other.
CDSC-WG2-02 - Data Types describes consensus around data fields that are either required or recommended in order to adequately describe the state of various grid entities. These two specifications are used in the development of
CDSC-WG2-03 - API Interface, which describes an interface for power systems operators when sharing power system data.
If you would like to contribute to these specifications, please see our docs on Contributing.
Want to participate? Great! We’re an open organization, so we welcome any company or individual who wants to provide input.
Things anyone can do (no membership required): 🔗
- Read anything on our repository, website, or mailing list.
- Join and participate in general discussion on the mailing list or Slack channel (
- Ask or answer questions on the mailing list or Slack channel (
- Attend and participate in meetings on our calendar.
- File or comment on an issue in our repository.
- Comment on pull requests.
- Fork our repository and play around with our code and documentation on your own (we’re open source!).
Things you can do if you become an LFESS member (it’s free!): 🔗
- Contribute comments, suggestions, or other content that will be included in our specifications.
- Open pull requests with proposed changes to our repository or specifications.
NOTE: It’s okay if you’re not yet an LFESS member and comment on something (spec, issue, pull request, mailing list, slack discussion, etc.), and we want your input to be incorporated into our specifications. We’ll just ask you to join LFESS before we can merge your suggestions into the specifications.
See our LICENSE.md.
Our specifications operate under the Joint Development Foundation (JDF) project model.
Our code and documentation is released under the Apache 2.0 license.
Code of Conduct
Contact for Code of Conduct issues or inquires: email@example.com