IEC 61970-600-1:2021 covers the definition of Common Grid Model Exchange Standard (CGMES), defines the main rules and application\u2019s requirements to meet business requirements for assembled and merged model to fit relevant business services. This document does not define the business requirements, business processes nor how applications are implemented. This document defines how relevant Common Information Model (CIM) standards work together so that specific business requirements can be resolved. It also includes extensions to the Common Information Model (CIM). The current extensions are defined in IEC 61970-301:2020 and will be covered in its future Amendment 1, but additional extensions can be defined in other standards in the IEC 61970-600-series. The extensions can be used to define additional profiles or to expand IEC 61970-450-series or IEC 61968-13 profiles. However, primary CGMES includes additional constraints on existing profiles and validation of assembled and merged models that is based on existing profiles. This can be done by making optional attributes and associations mandatory (required). In addition, this document includes the specification of the serialisation that must be supported by referring to an existing standard defined in IEC 61970-550-series, e.g. IEC 61970-552, and making relevant constraints related to it. The goal is to achieve interoperability between applications using CGMES in a high-performance environment with combined minimum effort so that relevant business processes are satisfied. This first edition cancels and replaces IEC TS 61970-600-1 published in 2017. This edition constitutes a technical revision.<\/p>\n
| PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
|---|---|---|---|---|---|---|---|
| 2<\/td>\n | undefined <\/td>\n<\/tr>\n | ||||||
| 4<\/td>\n | European foreword Endorsement notice <\/td>\n<\/tr>\n | ||||||
| 5<\/td>\n | Annex ZA (normative) Normative references to international publications with their corresponding European publications <\/td>\n<\/tr>\n | ||||||
| 7<\/td>\n | CONTENTS <\/td>\n<\/tr>\n | ||||||
| 9<\/td>\n | FOREWORD <\/td>\n<\/tr>\n | ||||||
| 12<\/td>\n | INTRODUCTION <\/td>\n<\/tr>\n | ||||||
| 13<\/td>\n | 1 Scope <\/td>\n<\/tr>\n | ||||||
| 14<\/td>\n | 2 Normative references <\/td>\n<\/tr>\n | ||||||
| 15<\/td>\n | 3 Terms, definitions and abbreviated terms 3.1 Terms and definitions <\/td>\n<\/tr>\n | ||||||
| 16<\/td>\n | 3.2 Abbreviated terms <\/td>\n<\/tr>\n | ||||||
| 17<\/td>\n | 4 Data exchange context <\/td>\n<\/tr>\n | ||||||
| 20<\/td>\n | 5 Specifications and functionalities 5.1 General constraints <\/td>\n<\/tr>\n | ||||||
| 22<\/td>\n | 5.2 Model authority sets (MAS) <\/td>\n<\/tr>\n | ||||||
| 23<\/td>\n | 5.3 File header <\/td>\n<\/tr>\n | ||||||
| 24<\/td>\n | 5.4 File body 5.5 Profiles and instance file types 5.5.1 General 5.5.2 CGMES profiles\u2019 properties <\/td>\n<\/tr>\n | ||||||
| 25<\/td>\n | Figures Figure 1 \u2013 CGMES instance file dependency <\/td>\n<\/tr>\n | ||||||
| 26<\/td>\n | 5.5.3 CGMES extensions <\/td>\n<\/tr>\n | ||||||
| 27<\/td>\n | 5.5.4 Equipment profile and instance file <\/td>\n<\/tr>\n | ||||||
| 28<\/td>\n | 5.5.5 Topology profile and instance file 5.5.6 Steady state hypothesis profile and instance file <\/td>\n<\/tr>\n | ||||||
| 29<\/td>\n | 5.5.7 State variables profile and instance file 5.5.8 Equipment boundary profile and instance file 5.5.9 Topology boundary profile and instance file 5.5.10 Diagram layout profile and instance file <\/td>\n<\/tr>\n | ||||||
| 30<\/td>\n | 5.5.11 Geographical location profile and instance file 5.5.12 Dynamics profile and instance file <\/td>\n<\/tr>\n | ||||||
| 31<\/td>\n | 5.6 File exchange <\/td>\n<\/tr>\n | ||||||
| 32<\/td>\n | 5.7 Boundary point \u2013 properties and location Figure 2 \u2013 Boundary point placed on a tie-line Figure 3 \u2013 Boundary point placed in a substation <\/td>\n<\/tr>\n | ||||||
| 33<\/td>\n | Figure 4 \u2013 HVDC as interconnection or internal line Figure 5 \u2013 HVDC grid <\/td>\n<\/tr>\n | ||||||
| 34<\/td>\n | 5.8 Model merging process <\/td>\n<\/tr>\n | ||||||
| 36<\/td>\n | Figure 6 \u2013 Merge process <\/td>\n<\/tr>\n | ||||||
| 37<\/td>\n | 5.9 CIM XML document\/distribution validity <\/td>\n<\/tr>\n | ||||||
| 38<\/td>\n | 5.10 Naming Convention <\/td>\n<\/tr>\n | ||||||
| 41<\/td>\n | 6 CGMES governance 6.1 General Table 1 \u2013 IdentifiedObject attributes Table 2 \u2013 IdentifiedObject attributes in EQBD profile <\/td>\n<\/tr>\n | ||||||
| 42<\/td>\n | 6.2 Versions of the CGMES and the profiles <\/td>\n<\/tr>\n | ||||||
| 43<\/td>\n | 6.3 Conformity assessment 6.4 Implementation process <\/td>\n<\/tr>\n | ||||||
| 44<\/td>\n | Annex A (xxxx) <\/td>\n<\/tr>\n | ||||||
| 45<\/td>\n | Annex B (normative)File header guidelines B.1 General B.2 Exchange scenarios Figure B.1 \u2013 Example workflow events <\/td>\n<\/tr>\n | ||||||
| 46<\/td>\n | B.3 Examples B.3.1 Example 1: File header of full model <\/td>\n<\/tr>\n | ||||||
| 47<\/td>\n | B.3.2 Example 2: File header of full model that is depending on another model <\/td>\n<\/tr>\n | ||||||
| 48<\/td>\n | B.3.3 Example 3: File header of full model that is depending on a model and supersedes another model <\/td>\n<\/tr>\n | ||||||
| 49<\/td>\n | B.3.4 Example 4: File header of difference model that is depending on a full model and supersedes another full model <\/td>\n<\/tr>\n | ||||||
| 50<\/td>\n | B.3.5 Example 5: File header of difference model that is depending on a difference model and supersedes another difference model <\/td>\n<\/tr>\n | ||||||
| 52<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Energy management system application program interface (EMS-API) – Common Grid Model Exchange Standard (CGMES). Structure and rules<\/b><\/p>\n |