Digital Twins Definition Language ontology for Energy Grid
A global standard for energy grid assets management, power system operations modeling and physical energy commodity market.
https://github.com/Azure/opendigitaltwins-energygrid
Category: Sustainable Development
Sub Category: Taxonomy and Ontology
Keywords from Contributors
3d-map sustainable measurement web-map orchestration
Last synced: about 21 hours ago
JSON representation
Repository metadata
DTDL based ontology for Energy Grid
- Host: GitHub
- URL: https://github.com/Azure/opendigitaltwins-energygrid
- Owner: Azure
- License: mit
- Created: 2020-09-01T23:19:08.000Z (over 4 years ago)
- Default Branch: main
- Last Pushed: 2021-06-11T21:38:00.000Z (almost 4 years ago)
- Last Synced: 2025-04-20T09:04:15.960Z (8 days ago)
- Size: 820 KB
- Stars: 58
- Watchers: 12
- Forks: 22
- Open Issues: 2
- Releases: 0
https://github.com/Azure/opendigitaltwins-energygrid/blob/main/
# Digital Twins Definition Language (DTDL) ontology for Energy Grid Domain ontologies are the foundational components to develop global solutions with industry standards. The Azure IoT engineering team has been collaborating with customers, domain experts, and industry-standard organizations to develop DTDL ontologies by leveraging the existing industry ontologies and best practices. Earlier, we published the DTDL ontologies for [smart buildings](https://github.com/Azure/opendigitaltwins-building) based on RealEstateCore, and for [smart cities](https://github.com/Azure/opendigitaltwins-smartcities) based on ETSI NGSI-LD. Today, we are releasing the energy grid ontology adapted from [Common Information Model (CIM)](https://cimug.ucaiug.org/Pages/About.aspx), a global standard for energy grid assets management, power system operations modeling and physical energy commodity market. The CIM-based DTDL ontology provides contextual understanding of data by identifying the properties of various grid entities and the relationships among them. Power & Utilities customers and partners can leverage as well as extend this open-source repository for their solutions and contribute their learnings to the repository for others to benefit from. The CIM organizes entities into distinct packages. In this first iteration, we have included core, wire, and generation packages, and prosumer-related entities from metering, customer, and Distributed Energy Resource (DER) packages. We have selected them based on the implemented and in-progress solutions, and on the collaborative decision of the extended team members of Agder Energi, Statnett, Sirus, FiWare, and Azure IoT. - **Core Package** contains the PowerSystemResource, ConductingEquipmen, and common collections of those entities shared by all applications. Most of the other packages have associations and generalizations that depend on the core package. - **Wire Package** is an extension to the Core that provides model information on the electrical characteristics of transmission and distribution networks. This package is used by network applications, such as state estimation, load flow, and optimal power flow. - **Generation Package** has information for unit commitment and economic dispatch of hydro and thermal generating units, load forecasting, automatic generation control, and unit modeling for training simulation. Last but not least – **prosumer** – we included various entities related to consumer and DER in the prosumer folder. For examples, EquivalentLoad, UsagePoints, and MeterReading. If you need additional entities before the next iteration, please contact us. If you already have DTDL grid entities feel free to contribute them to the repo.  # How To Use Using these models you can now build Azure Digital Twins based solution and bring it to life in a live execution environment. You can use Azure Digital Twins Explorer to create a sample easily: upload models, instantiate entities in a twins graph, visualize the graph and run queries against the graph. # Contributing This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com. When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA. This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [[email protected]](mailto:[email protected]) with any additional questions or comments. # Modeling guidelines Before creating new entities, [check if they exist already in the repo](https://github.com/Azure/opendigitaltwins-energygrid). You can look under each folder. To learn how to adopt the ontology for your project, refer to [How to use the ontology](https://github.com/Azure/opendigitaltwins-smartcities#how-to-use). # Syntax - Use English terms, preferably American English. - Use camel case syntax for attribute names (camelcase). - Entity Type names must start with a Capital letter, for example: Substation. - Use names and not verbs for Attributes of type Property, for example: nominalVoltage, EquipmentContainer. - Use verbs for Relationship and optional an object, for example: locatedAt, partOf. # Data Types DTDL provides a full set of [primitive data types, along with support for a variety of complex schemas](https://github.com/Azure/opendigitaltwins-dtdl/blob/master/DTDL/v2/dtdlv2.md#schemas). # Validation Use the [DTDL Validator tool](https://docs.microsoft.com/en-us/samples/azure-samples/dtdl-validator/dtdl-validator/) to validate the model document to make sure the DTDL is valid. # Resources - [Azure Digital Twins product page](https://azure.microsoft.com/services/digital-twins/) - [Azure Digital Twins documentation](https://docs.microsoft.com/en-us/azure/digital-twins/) - [Azure Digital Twins Tech Deep Dive](https://www.youtube.com/watch?v=5Ku55g1GQG8&feature=youtu.be) - [Digital Twins Definition Language specification](https://github.com/Azure/opendigitaltwins-dtdl) - [DTDL Ontologies](https://docs.microsoft.com/en-us/azure/digital-twins/concepts-ontologies) - [ADT Explorer](https://github.com/Azure-Samples/digital-twins-explorer) - [Azure Digital Twins Model Uploader](https://github.com/Azure/opendigitaltwins-tools/tree/master/ADTTools#uploadmodels) This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [email protected] with any additional questions or comments.
Owner metadata
- Name: Microsoft Azure
- Login: Azure
- Email:
- Kind: organization
- Description: APIs, SDKs and open source projects from Microsoft Azure
- Website: https://docs.microsoft.com/en-us/azure/
- Location: United States of America
- Twitter: Azure
- Company:
- Icon url: https://avatars.githubusercontent.com/u/6844498?v=4
- Repositories: 2270
- Last ynced at: 2025-04-25T21:02:11.366Z
- Profile URL: https://github.com/Azure
GitHub Events
Total
- Watch event: 4
- Fork event: 1
Last Year
- Watch event: 4
- Fork event: 1
Committers metadata
Last synced: 7 days ago
Total Commits: 89
Total Committers: 6
Avg Commits per committer: 14.833
Development Distribution Score (DDS): 0.135
Commits in past year: 0
Committers in past year: 0
Avg Commits per committer in past year: 0.0
Development Distribution Score (DDS) in past year: 0.0
Name | Commits | |
---|---|---|
op-ravi | o****i@m****m | 77 |
miriambrus | m****b@m****m | 5 |
Microsoft Open Source | m****e | 4 |
Akshay Johar | a****r@g****m | 1 |
Brian Crawford | b****r@m****m | 1 |
microsoft-github-operations[bot] | 5****] | 1 |
Committer domains:
Issue and Pull Request metadata
Last synced: 2 days ago
Total issues: 5
Total pull requests: 55
Average time to close issues: 1 day
Average time to close pull requests: about 2 hours
Total issue authors: 4
Total pull request authors: 5
Average comments per issue: 2.0
Average comments per pull request: 0.05
Merged pull request: 53
Bot issues: 1
Bot pull requests: 0
Past year issues: 0
Past year pull requests: 0
Past year average time to close issues: N/A
Past year average time to close pull requests: N/A
Past year issue authors: 0
Past year pull request authors: 0
Past year average comments per issue: 0
Past year average comments per pull request: 0
Past year merged pull request: 0
Past year bot issues: 0
Past year bot pull requests: 0
Top Issue Authors
- JMayrbaeurl (2)
- Haigutus (1)
- microsoft-github-operations[bot] (1)
- Sveino (1)
Top Pull Request Authors
- op-ravi (49)
- miriambrus (3)
- arvdrpoo (1)
- briancr-ms (1)
- LukasSchwendemann (1)
Top Issue Labels
Top Pull Request Labels
Score: 5.886104031450156