CGMES Profiling User Guide V1.0

CGMES Profiling User Guide V1.0

European Network of Transmission System Operators for Electricity CGMES Profiling User Guide v1.0 2021-04-21 SOC APPROVED VERSION 1.0 ENTSO-E AISBL • Rue de Spa, 8 • 1000 Brussels • Belgium • Tel +32 2 741 09 50 • Fax +32 2 741 09 51 • [email protected] • www.entsoe.eu CGMES Profiling User Guide v1.0 European Network of Transmission System Operators for Electricity Copyright notice: Copyright © ENTSO-E. All Rights Reserved. This document and its whole translations may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and d erivative works. However, this document itself may not be modified in any way, except for literal and whole translation into languages other than English and under all circumstances, the copyright notice or references to ENTSO-E may not be removed. This document and the information contained herein is provided on an "as is" basis. ENTSO-E DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Maintenance notice: This document is maintained by the ENTSO-E CIM EG. Comments or remarks are to be provided at [email protected] NOTE CONCERNING WORDING USED IN THIS DOCUMENT The force of the following words is modified by the requirement level of the document in which they are used. • SHALL: This word, or the terms “REQUIRED” or “MUST”, means that the definition is an absolute requirement of the specification. • SHALL NOT: This phrase, or the phrase “MUST NOT”, means that the definition is an absolute prohibition of the specification. • SHOULD: This word, or the adjective “RECOMMENDED”, means that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course. • SHOULD NOT: This phrase, or the phrase “NOT RECOMMENDED”, means that there may exist valid reasons in particular circumstances when the particular behaviour is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behaviour described with this label. • MAY: This word, or the adjective “OPTIONAL”, means that an item is truly optional. – Page 2 of 74 – ENTSO-E AISBL • Rue de Spa, 8 • 1000 Brussels • Belgium • Tel +32 2 741 09 50 • Fax +32 2 741 09 51 • [email protected] • www.entsoe.eu CGMES Profiling User Guide v1.0 European Network of Transmission System Operators for Electricity Revision History Version: Date Author Comment 1.0: 21-April-2021 Chavdar Ivanov Version for first drafted by CGMES SG, agreed in CIM EG, for SOC approval. Approved by SOC. – Page 3 of 74 – ENTSO-E AISBL • Rue de Spa, 8 • 1000 Brussels • Belgium • Tel +32 2 741 09 50 • Fax +32 2 741 09 51 • [email protected] • www.entsoe.eu CGMES Profiling User Guide v1.0 European Network of Transmission System Operators for Electricity CONTENTS Copyright notice: ..................................................................................................................... 2 Maintenance notice: ................................................................................................................ 2 Revision History ...................................................................................................................... 3 CONTENTS ............................................................................................................................ 4 INTRODUCTION ..................................................................................................................... 8 1 Scope .............................................................................................................................. 8 2 Normative references ...................................................................................................... 9 3 Terms and definitions ...................................................................................................... 9 4 Basic concepts .............................................................................................................. 10 4.1 Overview of the modelling methodology ........................................................... 10 4.2 Canonical CIM UML ......................................................................................... 10 4.3 UML package structure .................................................................................... 11 4.4 Maintenance of UML ........................................................................................ 13 4.5 Parameters for Enterprise Architect ................................................................. 13 4.5.1 MDG Technologies ......................................................................... 13 4.5.2 Reference data ............................................................................... 14 4.5.3 Order of attributes in classes .......................................................... 17 4.6 CimConteXtor and CimSyntaxGen plugins ....................................................... 18 4.7 jCleanCim ........................................................................................................ 19 5 Rules to extend Canonical CIM ...................................................................................... 19 5.1 Overview.......................................................................................................... 19 5.2 General rules ................................................................................................... 25 5.3 Class rules ....................................................................................................... 26 5.4 Attribute rules .................................................................................................. 27 5.5 Enumeration rules ............................................................................................ 27 5.6 Association rules ............................................................................................. 28 5.7 Diagram rules .................................................................................................. 29 5.8 Multiplicity rules ............................................................................................... 29 5.9 Inheritance rules .............................................................................................. 30 5.10 Documentation rules ........................................................................................ 30 5.11 “deprecated” stereotype rules .......................................................................... 30 5.12 “Inf” prefix rules ............................................................................................... 31 5.13 “Doc” prefix rules ............................................................................................. 31 5.14 DetailedDiagrams rules .................................................................................... 31 5.15 Naming rules ................................................................................................... 31 5.15.1 General .......................................................................................... 31 5.15.2 Package ......................................................................................... 32 5.15.3 Class .............................................................................................. 32 5.15.4 Enumeration class .......................................................................... 32 5.15.5 Attribute .......................................................................................... 32 5.15.6 Enumeration literal ......................................................................... 32 5.15.7 Association ..................................................................................... 32 5.15.8 Association end .............................................................................. 32 5.15.9 Diagram .......................................................................................... 34 6 Rules related to profiling ................................................................................................ 34 – Page 4 of 74 – ENTSO-E AISBL • Rue de Spa, 8 • 1000 Brussels • Belgium • Tel +32 2 741 09 50 • Fax +32 2 741 09 51 • [email protected] • www.entsoe.eu CGMES Profiling User Guide v1.0 European Network of Transmission System Operators for Electricity 6.1 General rules. .................................................................................................. 34 6.2 Rules about the organization of the profile packages. ...................................... 35 6.3 Rules on UML description ................................................................................ 36 7 Step by step profiling using CimConteXtor ..................................................................... 36 7.1 General overview ............................................................................................. 36 7.2 Profile creation ................................................................................................ 36 7.2.1 Manual profile creation ..................................................................

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    74 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us