We support grid operators in introducing and developing CIM and CGMES – from analysing existing data models through mapping and individual extensions to integration into applications and business processes.
CIM defines a shared semantics. The real challenge is to map existing company data onto the standard, add individual requirements sensibly and integrate CIM permanently into processes and systems.
Analyse source systems, data models and domain requirements, define mapping rules and transfer data into CIM structures.
Mappings, profiles and extensions matched to company-specific requirements.
Reusable structures and standardised interfaces make connecting existing systems easier.
Harmonised CIM structures create a shared foundation across systems and use cases.
Don't just exchange CIM – use it reliably in applications, processes and across company boundaries.
enervance is our strategic partner for all questions relating to the exchange of grid asset data based on the Common Information Model. Their deep expertise and customized solutions have impressed and supported us. We thank enervance for many years of successful collaboration.
With enervance solutions GmbH, we have a strong partner at our side who supports us with deep expertise in the field of data governance, helping us avoid data silos and develop a future-oriented data strategy.
CIM is a standardised information model for the energy industry. It describes grid objects, their properties and relationships in a shared semantics and thereby creates a basis for interoperable data exchange between different systems and organisations.
Our work is guided in particular by the CIM standards of the IEC 61970 and IEC 61968 families as well as CGMES profiles based on them. Which standards and profiles are relevant depends on the specific use case and system landscape.
First we analyse the existing source systems and data structures. Domain assignments between the existing model and CIM are then defined. This yields traceable mapping and transformation rules with which existing data can be transferred to CIM in a structured way.
No. CIM can be used as a shared integration and exchange layer without every specialist system having to switch internally to CIM. What matters is at which system boundaries and for which processes standardised semantics create value.
Yes. Existing CIM models can be adapted to concrete requirements via profiles and defined extensions. The standard should be retained as far as possible and extensions used specifically where company-specific information is genuinely needed.
Integration can take place via interfaces, transformations and defined data processes. The goal is not to introduce CIM as an isolated data format but to position it sensibly between source systems, analysis and planning solutions and external exchange processes.
Besides technical and domain checks, validation rules can be formalised with SHACL, for example. The CIM Suite applications can then be used for operational validation, analysis and correction.
CIM consulting addresses the domain and technical design of the CIM landscape: analysing data models, developing mappings, defining profiles and extensions and integrating CIM into the organisation. The CIM Suite then provides software for operational work with CIM data – validation with e.validate, analysis with CIM-Navigate and editing with e.ditor.
The concrete course depends on the use case. A project typically starts with analysing data sources, target processes and requirements. Mapping and modelling follow, possibly the definition of profiles or extensions, and then technical integration. Data quality and real usability are checked continuously.
Whether CIM introduction, mapping, CGMES, individual extensions or integration: we look at your starting position together and develop an approach that fits your data and system landscape.
