Official Grid Model Data Management (GMDM) profile repository used by EPRI's Vendor Forum and related tooling.
This repository contains the RDFS profile artifacts, example instance data, and supporting files used for validating and demonstrating GMDM exchange profiles.
Enterprise Architect model file used as a reference: CIM_Grid18v15_Enterprise14v04_Market04v18_GMDM_v1.3.eap
RDFS profile artifacts and JSON schema files that define exchange profiles:
Asset.rdfs-2020.rdfs- Asset profileDiagramLayout.rdfs-2020.rdfs- Diagram layout profileGeographicalLocation.rdfs-2020.rdfs- Geographical location profileMarketDER.draft-2020-12.schema.json- Market DER JSON schemaMarketNode.rdfs-2020.rdfs- Market node profileUnbalancedConnectivity.rdfs-2020.rdfs- Unbalanced connectivity profileUnbalancedElectrical.rdfs-2020.rdfs- Unbalanced electrical profile
Example CIM instance XML files organized by source system:
Facilities SubTransmission exports from Bentley systems:
Facilities SubTransmission/- Contains three substations with connectivity and naming convention files
Facilities Distribution exports from GEV systems:
Facilities Distribution/- Contains geographical location and unbalanced connectivity data for three circuits:- Central Neighborhood
- Industrial District
- Old Town
Master grid model data organized by voltage level and profile:
Master Complete/- Complete consolidated model files (asset, connectivity, electrical, location, marketnode)Master D-to-SubT-Boundary/- Distribution to SubTransmission boundary interfacesMaster Distribution/- Distribution level assets, connectivity, electrical, and geographical locationMaster SubTransmission/- SubTransmission level assets, connectivity, electrical, and geographical locationmerge.xml- Merge configuration file
The instance data follows GMDM naming conventions with profile identifiers:
CN- Connectivity profile (Naming Convention)GL- Geographical Location profileEL- Electrical profileAsset- Asset profile
Each file is versioned and dated to track the evolution of the model data.
See LICENSE at the repository root for license details.