Common Grid Model Exchange Specification (CGMES) Version 2.5 Draft IEC Part 1, Edition 2

Transcription

1 Commo Grid Model Exchage Specificatio (CGMES) Versio.5 Draft IEC Part 1, Editio Documet versio: 1 Date: 15 July 016

2 Cotets Page 1 Scope... 5 Normative refereces Terms ad defiitios Exchage process Specificatios ad fuctioalities Geeral costraits Model authority sets (MAS) File header File body Profiles ad istace file types CGMES profiles properties CGMES extesios Equipmet profile ad istace file Topology profile ad istace file Steady state hypothesis profile ad istace file State variables profile ad istace file Boudary equipmet profile ad istace file Boudary topology profile ad istace file Diagram layout profile ad istace file Geographical locatio profile ad istace file Dyamics profile ad istace file Maifest profile ad istace file Cotigecy profile ad istace file Availability Pla profile ad istace file Area Iterchage Cotrol profile ad istace file File exchage Boudary poit properties ad locatio Model assemblig process RDF/XML model validity Namig Covetio Modellig specificatios CGMES goverace Versios of the CGMES ad the profiles Coformity assessmet Implemetatio process Aex A (ormative) Template for further restrictios o amig Aex B (ormative) Summary of specific rules for amig covetio B.1 IdetifiedObject.ame B. IdetifiedObject.descriptio B.3 IdetifiedObject.eergyIdetCodeEic B.4 IdetifiedObject.shortName B.5 CoectivityNode ad TopologicalNode.fromEdIsoCode B.6 CoectivityNode ad TopologicalNode.toEdIsoCode B.7 CoectivityNode ad TopologicalNode.fromEdName B.8 CoectivityNode ad TopologicalNode.toEdName B.9 CoectivityNode ad TopologicalNode.fromEdNameTso B.10 CoectivityNode ad TopologicalNode.toEdNameTso... 48

3 B.11 Future developmets o CIM for dyamics Aex C (ormative) File header guidelies C.1 Itroductio C. Exchage scearios C.3 Examples C.3.1 Example 1: File header of full model C.3. Example : File header of full model that is depedig o aother model C.3.3 Example 3: File header of full model that is depedig o a model ad supersedes aother model... 5 C.3.4 Example 4: File header of differece model that is depedig o a full model ad supersedes aother full model C.3.5 Example 5: File header of differece model that is depedig o a differece model ad supersedes aother differece model Aex D (ormative) PST trasformer modellig D.1 Itroductio D. Mappig to CIM classes ad attributes D.3 Reactace formulas summary table D.4 Symmetrical Phase shifters D.4.1 Oe phase diagram ad equatios D.4. Expressio of the agle ad ratio per tap D.4.3 Expressio of the equivalet series reactace give the agle D.4.4 Three-phase diagrams D.5 Quadrature booster D.5.1 Oe phase diagram ad equatios D.5. Expressio of the agle ad ratio per tap... 6 D.5.3 Expressio of the equivalet series reactace give the agle... 6 D.5.4 Three-phase diagrams... 6 D.6 Asymmetrical Phase Shifter D.6.1 Oe phase diagram ad equatios D.6. Expressio of the agle ad ratio per tap D.6.3 Expressio of the equivalet series reactace give the agle D.6.4 Three-phase diagram D.7 I-phase trasformer ad symmetrical phase shifter D.7.1 Oe phase diagram ad equatios D.7. Expressio of the agle ad ratio per tap D.7.3 Expressio of the equivalet series reactace give the agle ad the i-phase trasformer ratio D.7.4 Techology priciples D.8 I-phase trasformer ad asymmetrical phase shifter D.8.1 Oe phase diagram ad equatios D.8. Expressio of the agle ad ratio per tap D.8.3 Expressio of the equivalet series reactace give the agle ad the i-phase trasformer ratio D.8.4 Techology priciples D.9 Detailed calculatios ad examples D.9.1 Symmetrical Phase Shifters with two cores D.9. Quadrature boosters D.9.3 Asymmetrical phase shifter Aex E (ormative) CGMES profiles versios Aex F (ormative) Use of Modelica i the Dyamics profile F.1 Itroductio F. Supported types user defied models by CGMES F.3 Modellig of user defied model i the CGMES F.4 Modelica way to lik with the code of the model F.5 CGMES proprietary model exchage applied to lik with Modelica code

4

5 Foreword The purpose of the Commo Grid Model Exchage Specificatio (CGMES) is to defie the iterface betwee Trasmissio System Operators (TSO) software i order to exchage power system modellig iformatio as required by the Europea Network of Trasmissio System Operators for Electricity (ENTSO-E) ad TSO busiess processes. The CGMES is used as a baselie exchage stadard for the implemetatio of the Commo Grid Model (CGM) methodologies i accordace with the requiremets for the implemetatio of various Europea etwork codes ad guidelies. The CGMES applies to applicatios dealig with power system data maagemet, as well as applicatios supportig the followig aalyses: load flow ad cotigecy aalyses, short circuit calculatios, market iformatio ad trasparecy, capacity calculatio for capacity allocatio ad cogestio maagemet, ad dyamic security assessmet. The coformity of the applicatios used for operatioal ad system developmet exchages with the CGMES is crucial for the eeded iteroperability of these applicatios. ENTSO-E therefore developed ad approved the CGMES Coformity Assessmet Framework as the guidig priciples for assessig applicatios CGMES coformity. Based o those priciples. This publicly available specificatio relies o the CGMES Coformity Assessmet Process operated by ENTSO-E i order to esure that the CGMES is properly implemeted by suppliers of the applicatios used by TSOs. Itroductio 1 Scope This publicly available specificatio o the CGMES defies the mai rules ad requiremets related to the CGMES ad which are madatory for achievig iteroperability with the CGMES ad for satisfyig the busiess processes. I the documet requiremets are idicated as such i a tabular format. Some descriptios are merely used for clarificatio ad are marked Iformatioal. The profiles which belog to CGMES are defied i a separate documet. The related techical iformatio ad documetatio (i.e. RDFS, OCL, XMI ad HTML) eeded for the implemetatio of the CGMES, which is ot copyrighted by either IEC or CENELEC, is available at the ENTSO-E web site. The CGMES is defied usig iformatio o the Commo Iformatio Model (CIM) available i the public domai. The followig refereced documets are idispesable for the applicatio of this documet. For dated refereces, oly the editio cited applies. For udated refereces, the latest editio of the refereced documet (icludig ay amedmets) applies. The CGMES is a superset of the former ENTSO-E CIM based data exchage stadard (Profile 1) which was based o CIM14 (UML14v0) ad has bee used for certai etwork models exchages sice 009. The CGMES reflects TSO requiremets (as kow by 014) for accurate modellig of the ENTSO-E area for 5

6 power flow, short circuit, ad dyamics applicatios whilst also allowig for the exchage of ay diagram layouts icludig GIS data of a grid model. Next editios of the publicly available specificatio will be released to describe followig CGMES versios which will be reflectig the additioal requiremets due to Europea etwork codes or guidelies. Normative refereces The CGMES is based o the CIM 16 (UML16v9). Oce the followig IEC CIM stadards are approved the CGMES would rely o them: IEC : CIM XML Model Exchage Format IEC : Commo Iformatio Model (CIM) Base IEC : Commo Iformatio Model (CIM) for Dyamics Specificatio IEC : CIM Static Trasmissio Network Model Profiles IEC : Diagram Layout Profile IEC : Solved Power System State Profiles IEC : Commo Iformatio Model (CIM) for Dyamics Profile IEC : Commo Iformatio Model Resource Descriptio Framework (CIM RDF) schema IEC : Applicatio itegratio at electric utilities System iterfaces for distributio maagemet - Part 4: Iterfaces for records ad asset maagemet. 3 Terms ad defiitios For the purposes of this documet, the followig terms ad defiitios apply. For defiitios which are ot specified i the CGMES the defiitios i the IEC CIM related stadards shall be applied. 3.1 Commo Grid Model Exchage Stadard (CGMES) This is a ENTSO-E stadard used for the exchage of power system models betwee TSOs for the purpose of performig bilateral, regioal or pa-europea studies i the frame of TYNDP or TSOs projects. It is based o IEC CIM Stadards ad further exteded to meet Network Codes ad projects requiremets. The stadard defies a set of data model exchage profiles. 3. Profile This refers to the uiquely amed subset of classes, associatios ad attributes eeded to accomplish a specific type of iterface ad based upo a caoical model. The term profile may be used to defie either the sematic model for a istace data payload or the sytactic schema for a istace data payload. A profile may be expressed i XSD, RDF, ad/or OWL files. A istace data coformig to a profile ca be tested i exchages betwee applicatios. A profile is ecessary i order to use the caoical model. 3.3 CIM Extesio A collectio of classes, attributes ad associatios, which exted the stadard IEC CIM model i order to cover use cases ot curretly supported by IEC stadards, ad which are ot cosidered to be iteratioal use cases or are covered by a later versio of the stadard which is ot yet supported. 3.4 ENTSO-E Extesio CIM Extesio, specifically maaged by ENTSO-E.

7 3.5 Boudary set A boudary set cotais all boudary poits ecessary for a give grid model exchage. A boudary set ca have differet coverage depedig o the requiremets of the commo grid model exchage. A complete boudary set is ecessary to assemble a pa-europea power system model. 3.6 Boudary poit (BP) Boudary poit is a coectio poit betwee two Model Authority Sets (MAS). A Boudary poit could be a CoectivityNode or a TopologicalNode placed o a tie-lie or i a substatio. A Boudary poit must be cotaied i a Boudary Set ad must ot be cotaied i the MAS of a TSO. A Boudary poit is refereced by Termials i the MAS of a TSO. CoectivityNode ad TopologicalNode are terms specified i IEC CIM stadards. If a Boudary poit is placed o a tie-lie, the term X-Node is ofte used istead of Boudary poit. X-Node is therefore a specific type of Boudary poit. 3.7 Abbreviatios IEC The Iteratioal Electrotechical Commissio, headquartered i Geeva TSO ENTSO-E MRID CIM CGMES MAS IOP RDF EQ_BD TP_BD EQ TP SSH SV DL GL DY BP Trasmissio System Operator Europea Network of Trasmissio System Operators for Electricity. ENTSO-E has 41 TSO members. CIM Master Resource Idetifier Commo Iformatio Model (electricity) Commo Grid Model Exchage Stadard Model Authority Set Iteroperability Test Resource Descriptio Framework Boudary equipmet profile or istace file Boudary topology profile or istace file Equipmet profile or istace file Topology profile or istace file Steady State Hypothesis profile or istace file State Variables profile or istace file Diagram Layout profile or istace file Geographical Locatio profile or istace file Dyamics profile or istace file Boudary poit 7

8 4 Exchage process There are various levels i which the exchage of power system data/models is ecessary. A pa-europea model exchage level covers the territory of all TSOs. Regioal model exchages ca be realised betwee differet TSOs i oe or more sychroous areas. A model exchage o the atioal level icludes iterfaces betwee TSOs ad DSOs, as well as betwee differet DSOs. The purpose of model exchages is ot oly to exchage the data from oe authority to aother but also to satisfy the ultimate goal, amely to perform commo studies usig shared data. All parties ivolved i the process should be able to perform the same types of studies ad be able to share project tasks betwee differet parties which are usig differet power system aalysis applicatios. Ideed, the iteroperability betwee differet applicatios used i the exchage process is therefore crucial i both reachig seamless data exchage ad obtaiig comparable study results whe usig this data. The CGMES covers these ENTSO-E ad TSO busiess processes by defiig the followig mai types of exchages valid for a particular study or process: Exchage of Boudary set: A exchage of a Boudary Set is ecessary to prepare a exchage of a iteral TSO model ad to assemble a commo grid model. The latest iformatio o Boudary Sets coverig pa-europea area is available to TSOs ad maitaied i the ENTSO-E Network Modellig Database (NMD) where all TSOs egotiate ad agree o the boudary iformatio. Exchage of a Iteral TSO model: A umber of busiess processes require each TSO to provide models of its iteral territory. To describe its iteral territory i a sigle stad-aloe exchage, a TSO is treated as a sigle model authority set ad shall be able to exchage all profiles defied i the CGMES. The TSO prepared its iteral model i such a way that it is easily ad uambiguously combied with other TSO iteral models to make up complete models for aalytical purposes. This type of exchage ca also be applied for the iterface betwee a TSO ad a DSO, where models coverig trasmissio or distributio parts of the power system ca be exchaged based o a mutual agreemet betwee the TSOs ad the DSOs. I this case, ad if a TSO requests a DSO model, the DSO would provide its model i accordace with CGMES defiitios which might be exteded by the TSO requestig this type of exchage. Exchage of a Commo grid model: A commo grid model refers to the cocept of havig oe model which ca be used for multiple purposes. The stadard describes what is eeded to create a assembly of multiple TSOs Idividual Commo Grid Model (ICGM) of their resposible territory ito a regioal or pa-europea model. Differet busiess processes will require specific implemetatio of the profiles part of the CGMES ad the exchage of respective istace files to meet iteroperability iside the busiess process. The Commo Grid Model meta-model descriptio will esure iteroperability across the busiess process. ENTSO-E ad TSO busiess processes (e.g. system developmet plaig, protectio plaig, operatioal plaig, operatio, fault study/simulatio, market operatio, etc.) are, of course, more complex tha these operatios, but what is importat to ote is that all processes are supported usig oly these basic kids of iteroperatio. Note that each power system model i CIM ormally cosists of multiple datasets (istace files) as defied i IEC CIM Stadards ad further specified by CGMES. The CGMES supports a ode-breaker ad a bus-brach model exchages. Movig forward the procedures of the model exchages usig the CGMES, it is expected that equipmet ad steady state hypothesis data (EQ ad SSH istace files) will be the iput source data for all processes. This type of model should be the

9 fully detailed model with all discoectors/breakers, etc. Ay cofiguratio chages are made by chagig switch statuses. ID Specificatio Type EXCH1. EXCH. EXCH3. EXCH4. The CGMES defies equipmet ad steady state hypothesis profiles as a iput, meaig that all results, whether topology or state variables profiles data, must refer to the equipmet ad steady state hypothesis objects. Therefore, i the case that both equipmet ad steady state hypothesis istace files are available, there is o eed to exchage topology or state variables istace files i order to obtai a load flow. For ode-breaker model exchages the TopologicalNodes represet the output from a topology processig o the detailed iput source operatioal data. These ca be optioally exchaged to be used by tools which have a iterest i the computed buses. For ode-breaker model exchages mrid (rdfids i serialisatio) of the TopologicalNodes are ot persistet. For ode-breaker model exchages a topology istace file is ot exchaged usig a differece file. Iformatio Iformatio EXCH5. For bus-brach model exchages the TopologicalNodes must be persistet. EXCH6. EXCH7. EXCH8. If a cotigecy list is exchaged belogig to the model exchaged i busbrach detail, it shall refer to CoductigEquipmet (TopologicalNode, braches, etc.). This results i a costrait o iteroperability betwee plaig ad operatio processes. If a cotigecy list is exchaged belogig to the model exchaged i odebreaker detail, it shall refer to CoductigEquipmet (CoectivityNode, which is ot artificial, Busbar, etc.). If a model has mixed represetatio (ode-breaker ad bus-brach) the the profile URI i the header related to the Equipmet Operatio is ot icluded as oly part of the etwork will iclude classes stereotyped with Operatio. 5 Specificatios ad fuctioalities 5.1 Geeral costraits The followig rules are geeral i ature or ivolve multiple classes. Additioal rules are defied i the otes to the idividual classes i the profiles part of the CGMES. ID Specificatio Type GENC1. All objects must have a persistet ad globally uique idetifier (it is the mrid - see Sectio 5.). I the ENTSO-E data exchage process this uique idetifier will be exchaged as rdf:id. Madatory GENC. Software solutios shall ot use ame related attributes (ame, short ame, descriptio, etc. iherited by may classes from the abstract class Madatory 9

10 ID Specificatio Type IdetifiedObject) to lik the power system model. Oly mrid (exchaged as rdf:id) is used for this purpose. GENC3. GENC4. GENC5. GENC6. GENC7. GENC8. The rdf:id defied withi a data exchage process is the oly globally uique ad persistet idetifier IEC defies the rdf:id as UUID ad its sytax (i.e. lower case ad umber of characters for the differet groups part of the UUID). UUID algorithm esures global uiqueess of the idetifier. Example UUID: f81d4fae-7dec- 11d0-a765-00a0c91e6bf6. The CGMES defies the idetifier as a case sesitive strig which coforms to W3C (ISO 8859/1 8-bit sigle-byte coded graphic character set kow as Lati Alphabet No. 1; with a imum character limit of 60 characters. A prefix could be added, if ecessary, to esure global uiqueess. The rdf:id is the mrid plus a uderscore _ added i the begiig of the strig. Applicatios which coform to the CGMES shall support IEC ad rdf:id expressed as a strig. Each TSO is resposible for esurig that the rdf:id is globally uique. ENTSO- E role i esurig global uiqueess of the rdf:id is limited to coordiatio ad harmoisatio of the approaches used i differet data exchages ad which shall coform to GENC4 ad GENC5. rdf:ids must be kept persistet for all profiles except for State Variable ad Diagram layout profiles: Madatory Madatory Madatory Madatory Madatory Madatory For the State Variable profile the rdf:ids for state variable classes (SvPowerFlow, SvVoltage, etc.) are ot kept persistet. For the Diagram layout profile the rdf:ids of DiagramObjectPoit ad DiagramObject classes may ot be kept persistet GENC9. rdf:about expressio is used for objects which are exchaged i a istace file for a give profile but defied i a differet profile (i.e. exchaged i a differet istace file). A stereotype Descriptio is itroduced to facilitate the implemetatio of this rule. All classes which shall be expressed by rdf:about are stereotyped with Descriptio. Madatory GENC10. UTF-8 is the stadard for file ecodig. UTF-16 is ot supported. Madatory GENC11. GENC1. GENC13. Istace data to be exchaged must make use of the most detailed class possible withi a profile, i.e. usig sub-typed classes rather tha geeral classes e.g. NuclearGeeratigUit istead of GeeratigUit. Optioal ad required attributes ad associatios must be imported ad exported if they are i the model file prior to import. If a optioal attribute does ot exist i the imported file, it does ot have to be exported i case exactly the same data set is exported, i.e. the tool is ot obliged Madatory Madatory Madatory

11 ID Specificatio Type to automatically provide this attribute. This is ot valid if the user is able to process the data, update the model ad perform aother export. GENC14. GENC15. GENC16. I most of the profiles the selectio of optioal ad required attributes is made o this basis so as to esure a miimum set of required attributes without which the exchage does ot fulfil its basic purpose. Busiess processes goverig differet exchages ca require madatory exchage of certai optioal attributes or associatios. Optioal ad required attributes ad associatios must therefore be supported by applicatios which claim coformace with certai fuctioalities of the CGMES. This provides flexibility for the busiess processes to adapt to differet busiess requiremets ad base the exchages o CGMES compliat applicatios. Breakers represet busbar couplers i a bus-brach model exchage. I this case, breakers are oly icluded if they are to be retaied. I case of a odebreaker model exchage the rules defied i the IEC ad i the CGMES profiles shall be applied. Roles ad multiplicity: The directio of the associatios i the profiles part of the CGMES is defied i the profiles. All associatios are bidirectioal, although a associatio istace is specified oly at oe ed i the istace files. The documetatio of the profiles, which is part of the CGMES, describes the associatio with the ed user. It is allowed to iclude both eds of a associatio i the XML, although oly the ed desigated by the profile is required. The followig two examples preset two optios which ca be see i the CGMES profiles: Madatory Madatory Madatory Example 1: The ames CoductigEquipmet.Termials ad Termial.CoductigEquipmet specify opposite eds of the associatio betwee the CoductigEquipmet class ad the Termial class. I a oeto-may associatio, the associatio referece is icluded with the data of the may side class. Therefore, a CoductigEquipmet ca be associated with up to two Termials, although a Termial must be associated with oe ad oly oe CoductigEquipmet. Cosequetly, the XML elemet correspodig to the CoductigEquipmet class is ot expected to cotai ay CoductigEquipmet.Termials elemets. However, the XML elemet correspodig to the Termial class is required to cotai appropriate Termial.CoductigEquipmet elemets. Example : The ames TopologicalIslad.TopologicalNodes ad TopologicalNode.TopologicalIslad specify opposite eds of the associatio betwee the TopologicalIslad class ad the TopologicalNode class. The XML elemet correspodig to the TopologicalNode class is ot required to cotai ay TopologicalNode.TopologicalIslad elemets. However, the XML elemet correspodig to the TopologicalIslad class is expected to cotai appropriate TopologicalIslad.TopologicalNodes elemets. 11

12 5. Model authority sets (MAS) The CIM cocept of Model Authority Sets is applied to eable the assembly or extractio of TSO models. Model Authority Sets allow a itercoectio model to be divided ito disjoited sets of objects, which i tur allows differet parties to take resposibility for differet parts of a commo grid model. ID Specificatio Type MAS_1. MAS_. MAS_3. MAS_4. MAS_5. MAS_6. MAS_7. MAS_8. MAS_9. I ay model exchage govered by the CGMES, each model object has a mrid. Across all models, the model object istace which represets a give real world asset (lie, trasformer, etc.) shall always have the same mrid. A CIM fuctioal represetatio is give by CIM classes defied i CGMES UML. Withi ay oe model, object mrids are uique, sice the same elemet shall ot be represeted twice. The mrid shall be persistet for the same give fuctioal represetatio iside a give versio of CIM. I the case of upgradig from oe versio of CIM to aother the mrid shall be kept persistet for the same fuctioal represetatio i the ew CIM give by a ew CIM class. For istace, the chage from CIM 15 to CIM 16 allows for a fuctioal represetatio idetified by the mrid for a ShutCompesator which is chaged to the ewly itroduced class NoLiearShutCompesator with the same mrid. mrids are oly geerated for cocrete classes i a give profile. I most cases there is o overlap of fuctioality betwee differet cocrete classes. A ew mrid is geerated i case there is a eed to chage the class (e.g. GeeratigUit is chaged to ThermalGeeratigUit). If a physical uit give by mrid i the asset part of the CIM eeds to be represeted simultaeously as GeeratigUit ad ThermalGeeratigUit (a give specialisatio) it must have differet mrids for GeeratigUit ad ThermalGeeratigUit. If differet busiess processes are required to support both types (GeeratigUit ad ThermalGeeratigUit) the applicatios should maitai two mrids ad i both cases support differece file exchage. Oly oe represetatio (the mai class or its specialisatio) should be preset i a give istace file. Each object istace is assiged to oe ad oly oe Model Authority Set. There are two types of Model Authority Sets: Madatory Madatory Madatory Madatory Madatory Madatory Madatory Madatory Madatory Boudary Sets TSO sets MAS_10. MAS_11. Boudary Sets which cotai Boudary poits markig the boudary betwee idividual models. Boudary Sets are maaged by oe authority (ENTSO-E) but have bee defied by TSOs as a result of mutual agreemet. TSO sets cotai idividual TSO istace files. Objects i the TSO sets have iteral associatios ad have associatios to Boudary sets. A TSO set shall Madatory Madatory

13 MAS_1. MAS_13. ever have associatios with objects i other TSO sets. This allows TSO modellig to be carried out idepedetly of other TSOs Each TSO i ENTSO-E is a Model Authority ad maages a Model Authority Set i its area of resposibility. The TSO as Model Authority is also resposible for assigig ad maitaiig object mrids i its area set. The territory that a TSO model represets may ot be exactly the same as the territory maaged by a TSO. I the CGMES, TSO territory always refers to the model resposibility territory. Madatory Madatory 5.3 File header The followig rules apply to all headers ID Specificatio Type HGEN1. The defiitio of file header is specified i IEC The CGMES applies the same defiitio i ay model exchage govered by the CGMES, each model object has a mrid. Madatory HGEN. Each type of istace file (full ad differece) shall have a file header. Madatory HGEN3. The file header is declared at the top of the istace file i.e. at the begiig of the file. Madatory The followig rules are applied to the model ID (rdf:about) i the file header: ID Specificatio Type HREF1. HREF. HREF3. HREF4. HREF5. New ID is geerated for ew istace files oly whe the cotext of istace data chages. A export doe o the imported istace data without ay chages should have the same model ID referece i the header. Depedet IDs refer to IDs of the depedet istace files at the time of the export. If all depedecies are resolved the there shall ot be ay uresolved refereces withi the data. The depedecy referece i the header shall be used as guidace ad shall ot restrict the possibility of importig profiles which are exported based o a previous versio of a depedig profile istace file. The stadard does ot prevet the tools from exchagig files where the file referece does ot match. Uresolved or missig refereces shall be reported to the user. I geeral, users are free to combie files o a ad-hoc basis ad toolig shall idetify ad optioally resolve all uresolved refereces. Model ID shall be the same if a re-export of a model cotais the same objects ad attributes. 13

14 ID Specificatio Type If the iformatio exchaged with the istace file is the same the the reexport is cosidered idetical. Rearragemets of classes ad attributes i the istace file are allowed. 5.4 File body ID Specificatio Type FBOD1. FBOD. FBOD3. FBOD4. FBOD5. The IEC specificatio is used to format a file, although the istace file shall cotai oly the objects from oe Model Authority Set. A istace file could cotai istace data of more tha oe profile from the CGMES oly if all profile URIs are defied i the file header ad as log as the istace data belogs to oe MAS. All profile URIs are defied i the file header eve if oe profile is a superset of aother, i.e. both URIs should be icluded. Istace files may cotai objects with associatios to objects which will be packaged i a differet istace file. This situatio meas that the istace file by itself is icomplete it may have daglig refereces ad caot be used except whe combied with oe or more other istace file as specified i the file header depedecies. Whe this occurs, validatio for completeess ca oly be performed whe all the parts are preset. The CGMES requires that at the receivig ed of the exchage all refereces i the istace files poitig to istace files from other profiles which are part of the exchage should be satisfied. Therefore, the complete set of istace files ecessary for the grid model must have fulfilled refereces (o daglig refereces are allowed). Whe a differece model is created differece elemets may be created due to very small umeric differeces. This is uecessary ad the applicatios are desiged i a way which prevets such meaigless differece files. 5.5 Profiles ad istace file types There are ie differet profiles i the CGMES. This sectio defies some specific rules for the profiles ad their istace files so that the model exchage ca be performed correctly CGMES profiles properties The profiles which are part of the CGMES are based o IEC CIM UML ad maitaied i a UML eviromet. ID Specificatio Type PROF1. The UML amespace, amespaces of the profiles, ENTSO-E extesios, profiles versios as well as the idetificatio of the versios of the UML ad profiles are

15 ID Specificatio Type defied i a Versio class for each profile of the CGMES. These properties shall be used as a primary source for file header iformatio. PROF. PROF3. PROF4. Profile specific otes have bee added to various classes ad attributes i the UML i order to further clarify differet profiles ad defie specific rules. These otes are cosidered madatory ad shall be satisfied by the applicatios Oly istaces of cocrete classes are used i actual exchages (istace files). Those cocrete classes may iherit attributes or associatios from abstract classes. The CGMES uses UML stereotypes to categorise classes, attributes ad associatios used for differet exchages. This is maily valid for the EQ (equipmet) profile where the followig categorisatio is applied ad defies the three differet types of equipmet istace files supported by CGMES: EQ core: icludes all classes/attributes/associatios which are ot stereotyped. These elemets are part of both ode-breaker ad bus-brach types of model exchage. EQ operatio: icludes all classes/attributes/associatios stereotyped with "Operatio". These elemets are oly ecessary if a ode-breaker model represetatio is exchaged. EQ short circuit: icludes all classes/attributes/associatios stereotyped with "ShortCircuit". These elemets are oly ecessary if a ode-breaker or a bus-brach model represetatio is exchaged for the purpose of performig short circuit calculatios PROF5. PROF6. PROF7. PROF8. The cardiality of give classes/attributes/associatios stereotyped with "Operatio" or "ShortCircuit" shall be respected if the exchage requires the iclusio of "Operatio" or "ShortCircuit". The respective profile URI shall be declared i the file header. If the profile URI is ot icluded i the header all classes/attributes/associatios part of the udeclared profile are cosidered optioal. Classes/attributes/associatios which were itroduced by ENTSO-E ad therefore cosidered as CIM extesios are marked with a stereotype "Etsoe". Ay classes/attributes/associatios which are defied by the CGMES profiles ca be used i grid model exchages. The authority goverig a give busiess process ad related data exchage process shall specify all required attributes/classes/associatios to be exchaged. A optioal attribute ca be required, while a required attribute as defied i the CGMES caot be chaged to optioal without modificatio of the versio of the profile. Applicatios ad tools should be able to deal with this complexity ad support all classes ad attributes depedig o the tools' fuctioalities, i.e. they should at least able to host the data ad trasfer with o chage i case the tool is ot able to use the data. All profiles which are part of the CGMES are documeted as follows: Iformatio UML (XMI), which cotais packages CommoGridModelExchageStadard ad Extesio. These packages 15

16 ID Specificatio Type cotai all defiitios related to the profiles i the CGMES ad are a source of other ways i which to documet the CGMES. RDFS, which cotais RDF schema files for each profile of the CGMES. The files are geerated by the applicatio CimCoteXtor. HTML, which cotais HTML documetatio for each profile of the CGMES. The files are geerated by the applicatio CimCoteXtor. HTML_EA, which cotais the HTML ative Eterprise Architect export of the CommoGridModelExchageStadard package. Pdf, which cotais detail descriptio of the CGMES profiles. PROF9. Aex E provides refereces to the CGMES documetatio related to a specific versio of the profiles. Iformatio PROF10. The depedecies betwee the profiles belogig to CGMES are defied i the followig figure. Madatory IEC Dyamic (Trasiet model) DY opt.ref IEC Diagram Layout DL opt. ref IEC Maifest MF Cotigecy CO Availability Pla AP ref ref ref IEC ref Short-Circuit EQ-SC ref Network Equipmet ad Coectivity EQ-CO Operatio (Node-Breaker) EQ-OP ref ref ref Topology TP ref State Variable SV Steady State Hypothesis SSH ref ref ref Boudary equipmet EQ-BD opt. ref Geographical Locatio GL Area Iterchage Cotrol AIC ref Boudary topology TP-BD opt. ref The diagram defies the ref relatios that show a depedecy betwee two profiles. Profile schemas (RDFS) shall ot be merged to create ew joit merged profile defiitios. Profile istace files shall list i the file header all profiles that describe the istace data so that a applicatio ca load all the profile schemas eeded to validate the istace data. The ref relatio may be added to the profile schemas such that a applicatio workig with istace data ca use this iformatio to load all eeded profile schemas.

17 ID Specificatio Type The ref ad opt.ref (optioal referece) are used to idicate possible depedecies at istace data level. These depedecies are provided i the file header. PROF11. The profile refereces i the file header specifies for which profiles validatio the istace file data is valid for. Madatory The istace data file ca cotai data from multiple profiles (such as ShortCircuit or Operatio) without beig declared i the header profile refereces. However, the data belogig to o-declared profiles does ot eed to be imported ad re-exported as the profiles are ot defied i the file header. The user shall be iformed if the data is ot imported CGMES extesios Due the complexity ad specificity of the ENTSO-E s ad TSOs s busiess processes, the CIM versio used to create the profiles of the CGMES has bee exteded. ID Specificatio Type EEXT1. EEXT. EEXT3. ENTSO-E extesios defied i the frame of the CGMES ad part of its profiles shall be equally supported i the same way as the IEC CIM. All extesio shall be a additio to a existig stadard (CGMES of IEC CIM stadards). ENTSO-E extesios which are part of the CGMES are extesios of the IEC CIM. Whe extedig the CGMES it is permitted to create a restrictio which does ot prevet the validity of the CGMES. While a optioal attribute or associatio ca be made required as a part of the profilig work, a required attribute or associatio caot be made optioal as part of a extesio. Declarig the ENTSO-E Extesio URI ad the Correspodig Alias: The ENTSO-E extesio URI ad the correspodig alias shall be declared at the topmost elemet of your CIM/XML file alog with CIM ad other URI. EXAMPLE (URI of the ENTSO-E CIM extesio ad the alias): EEXT4. <?xml versio="1.0" ecodig="utf-8"?> <rdf:rdf xmls:rdf=" xmls:cim=" xmls:etsoe=" </rdf:rdf> Usig Extesio URI Alias to Declare the Exteded Data is illustrated i the followig examples. I the first example the attribute IdetifiedObject.shortName is declared as a exteded attribute ad prefixed with the extesio alias etsoe. EXAMPLE (declarig a exteded attribute): <cim:acliesegmet rdf:id="_ f73688e-bace-4ece-bcb-5d "> <cim:idetifiedobject.ame>dfg-thy 1</cim:IdetifiedObject.ame> 17

18 ID Specificatio Type <etsoe:idetifiedobject.shortname>brussels</etsoe:idetifiedobject.s hortname> <cim:acliesegmet.bch> e-05</cim:acliesegmet.bch> <cim:acliesegmet.r> </cim:acliesegmet.r> <cim:acliesegmet.x> </cim:acliesegmet.x> <cim:coductor.legth>45</cim:coductor.legth> <cim:equipmet.aggregate>false</cim:equipmet.aggregate> <cim:coductigequipmet.basevoltage rdf:resource= "#_ a-e07-441b-bc3c-dc7b00de7e5e" /> </cim:acliesegmet> I the secod example, if a istace of the exteded class is declared as extesio, the the exteded class, i.e. ExtededClass, ad the exteded attribute ExtededClass.extededAttribute must be prefixed with the extesio alias etsoe. EXAMPLE (declarig a exteded istace or object): <etsoe:extededclass rdf:id="_ 1d3bbfb-0aec-4e44-8db0-aee064be"> <cim:idetifiedobject.ame>ex11</cim:idetifiedobject.ame> <etsoe:extededclass.extededattribute>0</etsoe:extededclass.exted edattribute >. </etsoe:extededclass > The third example illustrates the additio of a associatio, amely ENTSO-E extesio. EXAMPLE (declarig a exteded associatio): <cim:acliesegmet rdf:id="_9cdc68b c88a-4de a59"> <cim:acliesegmet.bch> </cim:acliesegmet.bch> <cim:acliesegmet.gch>0</cim:acliesegmet.gch> <cim:acliesegmet.r> </cim:acliesegmet.r> <cim:acliesegmet.x>1</cim:acliesegmet.x> <etsoe:coductigequipmet.extededclass rdf:resource="#_9cf549dc- 453-d a-cea " /> <cim:coductor.legth>30</cim:coductor.legth> <cim:idetifiedobject.ame>b1x3</cim:idetifiedobject.ame> </cim:acliesegmet> EEXT5. EEXT6. EEXT7. The same priciple related to extesios applies to ay other extesios. Therefore, if a istace file produced by a give applicatio/software cotais some extesios specific to vedors' iteral applicatios, the same method to declare such exteded data shall be used. A istat file which cotais classes, associatios ad attributes ot defied i the CGMES shall be processed by the receivig applicatio which would igore the extesios left udefied by the CGMES ad make use of the rest of the data. Extedig a eumerator has to be doe by addig a ew eumerator which icludes the additioal values. Both the exteded ad the stadard eumerator

19 ID Specificatio Type have to comply with the profile, i.e. if the stadard eumerator is madatory, it shall be icluded i additio to the ew (exteded) eumerator Equipmet profile ad istace file ID Specificatio Type EQ 1. The equipmet profile is separated by three fuctioal parts: EQ core, EQ operatio ad EQ short circuit. The followig types of equipmet istace files ad their relatio with the EQ profiles ca be exchaged: Full EQ: cotais all classes/attributes/associatios defied i EQ core, EQ operatio ad EQ short circuit profiles. EQ operatio: cotais all classes/attributes/associatios defied i EQ core ad EQ operatio profiles. EQ short circuit: cotais all classes/attributes/associatios defied i EQ core ad EQ short circuit profiles. It covers a bus-brach model exchage which cotais short circuit data. EQ. EQ 3. EQ 4. EQ 5. A equipmet istace file describes the equipmet i the power system model covered by a MAS. A equipmet istace file would ot ormally chage i case of frequet data exchage process. It ca be updated with differece file exchage. The SIPS allows for sharig of Protective Actios amog differet triggerig coditios. SIPS should, whe possible, have multiple trigger coditio ad/or protective actio that would make it work i all differet eviromets. Measuremet classes ad refereces to them are excluded from the profile. If a geerator is take out by discoectig switch it should be also be a protective actio that take geerator out of service, i.e. Equipmet.iService = false. Iformatio Madatory Topology profile ad istace file ID Specificatio Type TP 1. TP. A topology istace file cotais all topology objects for a MAS. These topology objects referece the correspodig equipmet describig how equipmet is electrically coected. A topology istace file is the result of a etwork topology processig aalysis. Because of this the topology istace file is cosidered as a output if the exchage is based o a ode-breaker model exchage. Iformatio 19

20 ID Specificatio Type TP 3. Depedig o the data exchage process a topology istace file may or may ot chage frequetly. E.g. a topology istace file ca be updated usig differece file exchage i case of bus-brach model exchage. Iformatio Steady state hypothesis profile ad istace file ID Specificatio Type SSH_1. SSH_. A steady state hypothesis istace file cotais all objects required to exchage iput parameters to be able to perform load flow simulatios. A steady state hypothesis istace file is always exchaged i full. Due to the ature of the SSH profile, all objects i a steady state hypothesis istace file shall have persistet mrids ad rdf:ids State variables profile ad istace file ID Specificatio Type SV 1. A state variable istace file cotais all objects required to complete the specificatio of a steady-state solutio. SV. A state variables istace file is always exchaged i full. SV 3. A state variables istace file of a assembled model cotais state variables related objects for all model authority sets beig part of the assembled model Boudary equipmet profile ad istace file ID Specificatio Type EQBD1. EQBD. A boudary equipmet istace file cotais all objects defied i the boudary equipmet profile ad icludes data for boudary iformatio relatig to a give exchage. The boudary equipmet profile defies which istace data represets types or voltages which are agreed for the CGMES based exchages. Therefore, idividual grid models shall refer to the boudary equipmet istace file to use declared EergyScheduligType-s ad BaseVoltage-s. This does ot limit differet model authorities whe it comes to defiig additioal types or voltages i their istace files, although there shall ot be a overlap of data values betwee boudary equipmet files ad idividual grid model istace files. For istace, ENTSO-E boudary equipmet file defies base voltages for both 380 kv ad 400 kv to which TSOs istace files should refer ad ot redefie these base voltages i their istace files.

21 ID Specificatio Type EQBD3. Boudary equipmet istace files ca be updated usig differece file exchage Boudary topology profile ad istace file ID Specificatio Type TPBD1. A boudary topology istace file cotais all objects defied i the boudary topology profile ad icludes data for boudary iformatio relatig to a give exchage. TPBD. A boudary topology istace file ca be updated usig differece file exchage Diagram layout profile ad istace file A diagram istace file is based o the IEC Diagram layout profile stadard ad cotais data ecessary for the model diagram. ID Specificatio Type DL 1. DL. DL 3. A full Diagram (o-differece istace file) represets a ew drawig of the diagram. Data may chage from oe system drawig to aother, e.g. two diagrams with the same mrid of the classes i the istace files do ot eed to be idetical. The purpose of Diagram layout profile is to support the uderstadig of the equipmet data. If a diagram geerated by oe system is updated by aother the file does ot eed to be idetical, with the exceptio of the edited chages. However, the updated ad exported diagram istace file must iclude all the same relevat iformatio ad must have the same layout rederig i the ew destiatio system (old source) as the origial, with the exceptio of the chages. The expected behaviour is that a diagram may have a ew layout with the same Diagram mrid as well as DiagramObject mrid. Persistece of Diagram ad DiagramObject mrids is required if differece updates are supported. The objects i the equipmet of the Diagram Layout istace are idetified by the DiagramObject.IdetifiedObject. The diagram layout profile supports exchage of more tha oe diagram, e.g. detailed substatio diagram, sigle lie diagram, etc i oe istace file of DL profile. DL 4. A diagram layout istace file is always exchaged i full. 1

22 Geographical locatio profile ad istace file ID Specificatio Type GL 1. GL. A geographical data istace file cotais GIS data ad is costructed based o IEC , although it is limited to the classes which cover ENTSO-E eeds. A geographical data istace file is exchaged i full, although it could be updated usig differece file exchage. Iformatio Dyamics profile ad istace file ID Specificatio Type DY 1. DY. A dyamics istace file represets the parameters ecessary to model dyamic behaviour of the power system, e.g. trasiet ad subtrasiet reactaces of sychroous machies, parameters of the cotrol block diagrams of excitatio systems, turbie, goverors, power system stabilisers, etc. A dyamics istace file would ot ormally chage i case of frequet data exchage processes. It ca be updated usig differece file exchage. Iformatio Maifest profile ad istace file ID Specificatio Type MF 1. A maifest istace file cotais all objects required to complete the specificatio of a meta data of the models exchaged i a give busiess process. Therefore it describes the cotet the icluded i the exchage models. MF. A maifest istace file is exchaged i full Cotigecy profile ad istace file ID Specificatio Type CO 1. A cotigecy istace file cotais all objects required to complete the specificatio of the cotigecy that has bee studied ad validated. CO. A cotigecy istace file is exchaged i full.

23 Availability Pla profile ad istace file ID Specificatio Type AP 1. AP. A availability pla istace file cotais all objects required to complete the specificatio of equipmets o availability for the study period. A availability pla istace file is exchaged i full ad with a complete set for the period Area Iterchage Cotrol profile ad istace file ID Specificatio Type AIC 1. A area iterchage cotrol istace file cotais all objects required to complete the specificatio of cogestio zoes with their respective capacity. AIC. A area iterchage cotrol istace file is exchaged i full. 5.6 File exchage ID Specificatio Type FILX1. FILX. FILX3. A give exchage cosists of multiple files. The CGMES defies that all files i a give logical exchage must be zipped together 1. The tools use zip files directly whe importig ad exportig i order to miimise users. The CGMES defies is o amig covetio applied to the.xml or.zip file ames. Although differet busiess processes may defie such a file amig covetio, the applicatios shall rely solely o the iformatio provided i the file headers i order to process the istace files. Oe zip file ca oly cotai the followig types of files: Iformatio. Iformatio Iformatio A sigle istace file of the followig types: equipmet (EQ), boudary equipmet (EQ_BD), topology (TP), boudary topology (TP_BD), steady state hypothesis (SSH), state variables (SV), dyamics (DY), diagram layout (DL), geographical locatio (GL). 1 Note that a give busiess process may require the istaces to be exchaged i idividual zip files 3

24 ID Specificatio Type Combiatios of equipmet, topology, steady state hypothesis, state variables, dyamics, diagram ad geographical istace files which are allowed by the CGMES ad are related to oe MAS oly. Differece files of oe MAS oly whe exchagig a TSO model. Equipmet, topology, steady state hypothesis, state variables, dyamics, diagram ad geographical files per MAS for a assembled model. Differece files per MAS for a assembled model. Boudary MAS istace files (full or differece or the assembled model is expressed with differece files) shall always be icluded i the zip file cotaiig a assembled model FILX4. The zip file shall ot cotai folders. It is oly a cotaier of *.xml files. FILX5. The hierarchy ad model depedecy shall be respected whe exchagig models. The umber of files ad the type of the files (full or differece) depeds o the requiremets set by the busiess process. The followig examples show some possible situatios: If the equipmet file is chaged, all files (depedig o the requiremets of the exchage: equipmet, topology, steady state hypothesis, state variables, dyamics, diagram ad geographical files) must be set as part of ay exchage. If oly the steady state hypothesis file is chaged, oly the steady state hypothesis file must be set as part of ay exchage if there is o requiremet to exchage the solved power system model. If oly the state variables file is chaged, oly the state variables file must be set as part of ay exchage. If oly the dyamics file is chaged, oly the dyamics file must be set as part of ay exchage. If oly the diagram file is chaged, oly the diagram file must be set as a part of ay exchage. If oly the geographical file is chaged, oly the geographical file must be set as a part of ay exchage. FILX6. FILX7. FILX8. It is ot allowed to exchage a topology file, a steady state hypothesis file, a state variables file, a dyamics file, a diagram file or a geographical file from oe model ad a equipmet file from aother model (or from a etity which has chaged the equipmet file) ad attempt to assemble all files ito oe assembled model. I case differece files are exchaged, the same depedeces as for full model exchage are followed. The differece file (e.g. equipmet, topology or dyamics) should refer to the base model which is subject to a update. Depedecies are listed i the file header of each file which is exchaged CGMES supports Efficiet XML Iterchage (EXI), defied by W3C, as a alterative way of achievig smaller, faster, more efficiet serialisatio of XML data. Iformatio about EXI is available here:

25 ID Specificatio Type This format is ot a replacemet for the CIM RDF XML that previous versios of the CGMES used. Istead it is a complimetary stadard providig a alterative serialisatio of the same data that is focussed o efficiecy ad speed ad offers drop-i replacemets that is already compatible with existig code. Busiess processes usig CGMES will defie the required schedule for implemetatio cosiderig loger trasitio period form xml/zip to EXI exchage. FILX9. Applicatios shall support cimx file extesio, which is a zip file. Madatory 5.7 Boudary poit properties ad locatio ID Specificatio Type BPPL1. BPPL. BPPL3. EquivaletIjectio classes are used to represet the power flow exchages through Boudary poits. These classes are icluded i the idividual model MAS (TSO MAS) ad refer to the Boudary poits i the Boudary set. A SvIjectio class is ot used for this purpose. I case the use cases require the exchage of multiple SSH, TP, SV, etc. istace files which are depedet o a EQ istace file, this EQ shall always iclude a istace of EquivaletIjectio per Boudary poit. Therefore, i a multi TSO exchage a Boudary poit will always have two EquivaletIjectios per Boudary poit cotaied i differet TSO MAS. Rdf:IDs of those EquivaletIjectios are kept persistet. There are two optios related to the locatio of the Boudary poit (BP) i a etwork model represetig the AC grid oly: Boudary poit placed o a tie-lie: The CGMES does ot fix the positio of the Boudary poit o a tie-lie. The Boudary poit ca be placed o a coutry border, at the electrical middle of the tie-lie, or elsewhere based o mutual agreemet betwee the two eighbourig MAS. Tie-lie Substatio 1 Substatio BP Boudary Poit (BP) placed o coutry border, electrical middle or elsewhere 5

26 ID Specificatio Type Boudary poit placed i a substatio: The CGMES allows a Boudary poit to be placed i a substatio. The two eighbourig MAS shall agree betwee which two elemets i a substatio the Boudary poit is placed. Substatio Elemet 1 (e.g. trasformer) BP Elemet (e.g. bus bar) BPPL4. The CGMES supports HVDC modellig for a detailed represetatio of HVDC itercoectios, TSO iteral HVDC liks ad HVDC grid. The figures below illustrate differet cases. Iformatio TSO 3 (MAS 3) CC4 AC ad DC part of the HVDC itercoectio (HVDC A) CC TSO (MAS ) CC9 AC ad DC part of the HVDC iteral lie (HVDC D) CC10 CC3 TSO 1 (MAS 1) AC ad DC part of the HVDC itercoectio (HVDC B) Commo couplig ode (CC 1) CoectivityNode or TopologicalNode Coutry border Figure 1 - HVDC as itercoectio or iteral lie

27 ID Specificatio Type TSO 5 (MAS 5) CC7 TSO 4 (MAS 4) CC5 AC ad DC part of the HVDC grid (HVDC C) CC6 TSO 6 (MAS 6) CC8 TSO 7 (MAS 7) Figure - HVDC grid BPPL5. There are two mai represetatios/exchages of a HVDC lik which are supported by the CGMES: Iformatio Simplified exchage (o exchage of the AC/DC part of the HVDC itercoectios. A HVDC lik is represeted with two radial AC lies) Detail exchage (AC/DC part of HVDC liks is exchaged) BPPL6. BPPL7. BPPL8. I the simplified exchage of a HVDC lik the et iterchage betwee the MAS is represeted by EquivaletIjectio classes referrig to each commo couplig ode (CC). The simplified exchage of a HVDC lik could be applied to iteral HVDC liks (systems) as well as to HVDC itercoectios. I the detail exchage of a HVDC lik the HVDC grid shall be exchaged as a MAS: Iformatio Separate istace files (EQ, TP, SSH, SV) are icluded i this MAS. I case oe TSO is resposible for the HVDC, the HVDC model is icluded i the TSO MAS (EQ, TP, SSH, SV). BPPL9. BPPL10. I case of a detail exchage of a HVDC lik, the HVDC MAS shall refer to the commo couplig poits (CoectivityNode or to TopologicalNode) icluded i the Boudary set. I case of more tha oe HVDC itercoectio (icludig itercoectios with differet TSOs) the TSO ca iclude them i a sigle HVDC MAS or i its ow MAS. Iformatio 7

28 ID Specificatio Type BPPL11. I particular cases a Boudary poit ca be placed o a DCLieSegmet ad could possibly represet a differet authority. The CGMES does ot allow for the separatio of the HVDC model at this specific Boudary poit. It oly makes sese to add a Boudary poit with a locatio to idetify certai resposibilities Iformatio 5.8 Model assemblig process ID Specificatio Type MAPR1. MAPR. MAPR3. A complete (assembled) commo grid model (solved or usolved power system model) cotais iformatio from more tha oe model authority set. Part of the reaso for the divisio ito files per MAS is to create better flexibility whe it comes to how complete assembled models for differet purposes are formed from base parts. Model maagemet systems ca be desiged based o this capability. Amog istace files which are to be combied to form a assembled model, there is o overlap each object, associatio or attribute appears i oe ad oly oe of the istace files beig combied. The model assemblig procedure i the CGMES is based o the Model Authority Sets cocept. The procedure icludes the followig steps: Iformatio Model maagemet system (calculatio tool/software) imports all MAS (full set of files for MAS for each TSO ad Boudary MAS). Depedig o the implemetatio of the import process, the Boudary MAS must be imported first i case other MAS are subsequetly imported. The followig files/mas should be available for import. o At least two models from TSOs are available ad represeted i two differet MAS. These models have ecessary refereces to the Boudary set. o TSO models which iclude classes (EquivaletIjectio for SSH profile; SvPowerFlow ad SvVoltage for SV) represet the flow betwee the MAS ad the voltage of the Boudary poits. o Boudary MAS: Boudary istace files (equipmet ad topology) cover, but are ot limited to, the area represeted i the commo grid model. SvVoltage classes poitig to the Boudary set are set to the omial voltage of the Boudary Node with zero agles i case the values for EquivaletIjectio poitig to a Boudary Node are differet. EquivaletIjectio.p ad EquivaletIjectio.q are set to zero, if a tie-lie or a CoectivityNode is coected. It is ot ecessary that these parameters be set to zero at the time of the import. Additioal fuctios should be made available for users to cover all ecessary use cases whe dealig with TSO MAS ad Boudary MAS. A power flow ca be performed to obtai a solutio for the assembled power system model.

29 ID Specificatio Type MAPR4. MAPR5. MAPR6. MAPR7. MAPR8. MAPR9. A update of the assembled power system model is performed via a update of the cocered MAS (i.e. replacig of MAS files). A power flow solutio is ecessary to update the commo state variables file valid for the updated assembled model. State variable istace file for the commo grid model iclude SvPowerFlow for ijectios of Boudary poits. I order to solve a assembled model these ijectios are set to zero i case a Boudary poit successfully coects the two MAS. Some ijectios (SvPowerFlow) may differ from zero to represet the exchage with other areas ot icluded i the assembled model. The exported assembled model shall have oly oe istace of SvVoltage per Boudary poit. The CGMES does ot fix the cotet of a assembled grid model. Differet busiess processes shall defie the type (EQ, SSH, TP, SV, etc.) of data eeded i the assembled model depedig o the objectives. The CGMES supports export of usolved assembled model. The model ca be a ode-breaker or bus-brach model represetatio type, ad shall always iclude SSH istace files if the purpose of the exchage is to perform (without data additios) a load flow calculatio i a differet applicatio. The exported assembled model cotais multiple MAS. These exported multiple MAS iclude all chages which are itroduced o the assembled model (chages made i the software which is used to assemble the model) per MAS. The followig chart illustrates the assembly process: Iformatio Iformatio 9

30 ID Specificatio Type TSO A: oe MAS; set of files - zipped TSO B: oe MAS; set of files - zipped TSO N: oe MAS; set of files - zipped Import Boudary MAS (equipmet ad topology files) - zipped Software for power flow/simulatios 1. Import all MAS (first Boudary the TSOs). Set EquivaletIjectio to zero (user s iput eeded) 3. Ru power flow/simulatios 4. User modifies assembled model icludig data i the idividual MAS, if ecessary ad ru power flow/simulatios 5. Export of assembled model per MAS icludig all modificatios itroduced usig the tool Export Assembled power system model oe zip file; multiple MAS represetig TSOs models ad boudary MAS Boudary MAS: equipmet ad topology files TSO A: oe MAS; EQ, TP, SSH, DY,GL TSO N: oe MAS; EQ, TP, SSH, DY,GL A Diagram file exported by the assemblig MAS A State variables file exported by the assemblig MAS

31 ID Specificatio Type MAPR10. MAPR11. The model authority set of the state variable istace file of the assembled model is ot defied i the file header. The model authority set of the diagram layout istace file of the assembled model is ot defied i the file header. 5.9 RDF/XML model validity I order to be cosidered a valid model, a give combied set of RDF/XML must adhere to the followig criteria: ID Specificatio Type MVAL1. MVAL. MVAL3. The file must be well-formed as defied by the Extesible Markup Laguage (XML) 1.0 (Secod Editio) ( The file must adhere to the rules set forth i the Simplified RDF Sytax for Power System Model Exchage as defied i IEC The file must cotai CIM etities which are valid accordig to the CIM RDF Schema file. MVAL4. Use of IEC Ed for all profiles that are created i CGMES.5 rdf:id is replaced with rdf:about "ur:uuid:"+mrid; rdf:about that refers to rdf:id shall also be replaced with rdf:about "ur:uuid:"+mrid referece. The existig profiles from CGMES.4 could be serialised usig IEC Ed1 for processes that eeds backwards compatibility. However, for coformity it is allowed that a system oly ca serialise usig IEC Ed. A CGMES.4 importer ca also support IEC Ed. If a file is imported as IEC Ed1 with rdf:id, ad the exported accordig to IEC Ed, the applicatio eeds to use rdf:about "ur:uuid:"+mrid if it is a UUID. If it ot a UUID it should be left as is. The preferred serializatio for CGMES.5 is IEC Ed Namig Covetio The amig covetio of ay profile is importat i order to esure that the iformatio which is part of the data exchage ca be uderstood ad used. A power system model without appropriate amig iformatio caot be readily used for ay huma aalyses ad thus loses its meaig. Namig is complex issue as differet applicatios ca have icosistet ad sometimes coflictig amig covetios. 31

32 The CGMES, which uses multiple profiles, serves various busiess processes. These busiess processes have differet eeds i terms of amig iformatio. There is o sigle set of rules which could be applied to deal with the specificities of differet busiess processes axes such as: Bilateral, regioal, ENTSO-E pa-europea data exchages; Operatioal (day ahead ad related processes), log term plaig data exchages; Node-breaker, bus-brach based data exchages; Volutary, project orieted, obligatory by a ENTSO-E process, obligatory by law data exchages. A restrictio related to amig could serve oe busiess process well but may represet a sigificat costrait for aother busiess process. I additio, actors ivolved i the exchage are ot ecessarily the same. CGMES applies the followig amig priciples: Names are maily for humas. They shall ot be used for ay purposes object idetificatio. Namig rules shall be drive by the use cases (maily iformatio presetatio), ot restricted by limitatios of vedors systems ad UML/profilig tools. Names are importat i may cases. But restrictive requiremets o amig may result i the iteroperability issues. For example, the dyamically-created ames may ot be storable i the uderlyig data source, resultig i iformatio loss. Physical modellig etities, such as Substatio, Equipmet, etc., require a ame to be specified, while amig is optioal for the compoets that make up a physical modellig etity, such as Termial, RatioTapChager, etc. Coceptual modellig etities may or may ot require a ame to be specified depedig o whether these modellig etities shall be preseted to ed-users. DiagramObjects, for example, are meaigless for huma audieces. TopologicalIslad, o the other had, may require a ame to be provided, sice they could be show i the power flow reports. Name of coceptual modellig etities shall be optioal wheever possible. For example, if the coceptual modellig ca be characterized by oe or a combiatio of its attributes, the amig shall be optioal. As a example, ame for BaseVoltage may ot be required, sice it is characterized by attribute BaseVoltage.omialVoltage, which could optioally serve as ame. By the same toke, if a coceptual modellig etity is uiquely associated with a physical modellig etity, the its ame ca be derived from the associated physical modellig etity if eeded. Therefore, the objective of the CGMES amig covetio is to defie a commo framework related to amig rules which could be further restricted by differet busiess processes. The followig rules related to the amig covetio are defied: ID Specificatio Type NAMC1. A template for further defiig costraits related to the amig covetio is provided i Aex A. The template shall be used by experts defiig amig covetio rules withi a busiess process. The template shall be completed by a profile (EQ, TP, SV, etc.). As soo as a busiess process is defied ad data exchage requiremets agreed, the tables related to differet profiles should be made available to all parties participatig i the data exchage ad vedors should be iformed. This will allow: Iformatio TSO experts to be aware ad respect requiremets related to amig i the models.

33 ID Specificatio Type Vedors developig tools for power system aalyses to esure that: o TSO experts are able to supply the ames as required by the busiess process; o A agreemet for amig traslatio betwee requiremets i the busiess process ad the proprietary formats or TSO databases is i place; o Export ad import fuctioalities are compliat with the data exchage rules. Vedors developig validatio tools to adjust validatio rules valid for the busiess process NAMC. NAMC3. The restrictios related to the amig covetio are cosidered obligatory for ay tool importig or exportig amig data if the tool claims compliace with the CGMES. Further restrictios ca be applied by differet busiess processes. Busiess processes restrictios o amig must defie required ad optioal attributes related to amig. These restrictios or rules should ot cotradict this amig covetio ad are cosidered madatory for all parties participatig i a give busiess process. Tools used to validate istace data shall be able to validate agaist differet sets of amig covetios which are applied to exchages based o the CGMES. Tools used for various power system aalyses shall provide users with the opportuity to cope with differet amig rules. These tools shall be developed to support the full scope of this amig covetio. NAMC4. NAMC5. Due to the curret iheritace structure of the CIM used for the profile, the amig covetio primarily addresses the attributes of the class IdetifiedObject. However, there are certai exceptios, icludig Boudary profiles whereby some ENTSO-E extesios are applied to CoectivityNode ad TopologicalNode. The ame related attributes have a iformatioal character iteded for huma readig for explaatios outside the classes. Software solutios must ot cout o this iformatio to complete physical liks of the power system model. All ecessary liks betwee differet parts of the CIM XML are expressed by the referece schema which uses rdf:id Iformatio NAMC6. Names shall coform to UTF-8 NAMC7. NAMC8. I cases where tools usig istace data (compliat with the CGMES exchages) eed uiqueess rules, this shall be hadled i the importig fuctio based o requiremets defied by the users. It is obligatory that iformatio exchaged i ame related attributes is ot modified by the tools withi a exchage, i.e. step 1: Tool A imports data from Tool B ad modifies iitial iformatio to fit user requiremet of tool limitatio; 33

34 ID Specificatio Type step : Tool A is obliged to export the imported data i the same form ad cotet as the data exported from Tool B. NAMC9. NAMC10. NAMC11. Oe of the mai reasos behid this rule is the fact that exchages i the ENTSO-E are meat to be bi-directioal, i.e. there is a sedig party ad a receivig party which exchage models withi studies ad do ot ecessarily cosume oly the data. It is madatory that tools shall provide users with the ability to add ad maitai amig related iformatio for classes which represet physical equipmet as well as classes which represet elemets importat for busiess processes (e.g. TopologicalNode). This iformatio is the mapped oto relevat attributes ad ca be exported for the purpose of the exchage. There is o eed for a specific amig covetio whe it comes to the ames of the istace files due to file header iformatio which is defied by IEC CIM stadards ad the CGMES. The followig tables summarise the use of ame related attributes i the differet profiles. It provides the legth of the strigs which tools must support for all classes that iherit from IdetifiedObject or o CoectivityNode ad TopologicalNode. Table 1 IdetifiedObject attributes Iformatio IdetifiedObject Strig legth, characters Equipmet profile Topology profile Study State Hypothesis profile State variables profile Diagram layout profile Geographical locatio profile Dyamics profile.ame 3 r o o r r o.descriptio 56 o o o.eergyidetcodeeic 16 exactly o o.shortname 1 o o Table IdetifiedObject attributes for CoectivityNode i EQ_BD profile ad for TopologicalNode i TP_BD profile IdetifiedObject Strig legth, characters Boudary equipmet profile Boudary topology profile.ame 3 r r.descriptio 56 r r.eergyidetcodeeic 16 exactly o o.shortname 1 r r.fromedisocode exactly r r

35 ID Specificatio Type.toEdIsoCode exactly r r.fromedname 3 r r.toedname 3 r r.fromednametso 3 r r.toednametso 3 r r Leged: r the attribute is preset i the profile ad required (required meas that it is madatory that this attribute be preset i the istace data); o - the attribute is preset i the profile ad optioal; - the attribute is ot preset i the profile. NAMC1. NAMC13. NAMC14. Additioal specific rules related to the amig attributes are icluded as otes i the profile specificatios. These otes are cosidered as madatory rules. The same rules are summarised i Aex B. OCL validatio rule i the TP profile defies i which cases the attribute IdetifiedObject.ame is required. Name related attributes of the IdetifiedObject that are required ca be exchaged as empty strig i.e. <IdetifiedObject.ame>< IdetifiedObject.ame>. Requireme t 5.11 Modellig specificatios The followig modellig specificatios are defied to support the implemetatio of the CGMES. ID Specificatio Type MSPEC1. RegulatigCotrol descriptio specifies that i case multiple equipmet, possibly of differet types, cotrol same termial there must be oly oe RegulatigCotrol at that termial. The most specific subtype of RegulatigCotrol shall be used i case such equipmet participate i the cotrol, e.g. TapChagerCotrol for tap chagers. This setup is illustrated i the followig figure. The applicatios shall esure that the cotrolled termial is the oe of the cotrolled ode. Madatory 35

36 ID Specificatio Type MSPEC. CGMES requires the followig implemetatio related to the tap chage ad phase shift trasformers: TapChager.eutralU is the voltage at the termial of the PowerTrasformerEd associated with the tap chager whe all tap chagers o the trasformer are at their eutralstep positio. Normally eutralu of the tap chager is the same as ratedu of the PowerTrasformerEd, but it ca differ i special cases such as whe the tappig mechaism is separate from the widig more commo o lower voltage trasformers. For CGMES eutralu equals ratedu. RatioTapChager.stepVoltageIcremet shall be i per cet of eutral voltage, per step positio, ot omial. The right descriptio of this attribute is: Tap step icremet, i per cet of eutral voltage, per step positio. Nomial quatities are ot related to the equipmet but to the system omial voltage i the grid. Rated quatities such as ratedu are related to the ameplate data. TapChager.eutralStep is the step positio where the voltage is eutralu whe the other termials of the trasformer are at the ratedu. If there are other tap chagers o the trasformer those taps are kept costat at their eutralstep. For PhaseTapChagerAsymmetrical, PhaseTapChagerSymmetrical ad PhaseTapChagerLiear the eutralu is ot relevat. Madatory

37 ID Specificatio Type PhaseTapChagerNoLiear.voltageStepIcremet relates to the ratedu. The voltagestepicremet is used for PhaseTapChagerAsymmetrical, PhaseTapChagerSymmetrical. SvTapStep.positio shall be required eve if the TapChager.cotrolEabled is set to false. As CGMES requires eutralu to be equal to ratedu, the followig implemetatios are valid: ratedu + ratedu* stepvoltageicremet*(svtapstep.positio-eutralstep) eutralu + eutralu*stepvoltageicremet*(svtapstep.positioeutralstep) eutralu + ratedu*stepvoltageicremet*(svtapstep.positio-eutralstep) ratedu + eutralu*stepvoltageicremet*(svtapstep.positio-eutralstep) MSPEC3. Cotrol of tap chagers i a power flow type of applicatio is made usig the TapChagerCotrol class ad the TapChager.ltcFlag. If a TapChager has a TapChagerCotrol (refereced TapChager.TapChagerCotrol) meas that the power flow applicatio may cotrol the tap chager. The TapChager.ltcFlag provides iformatio that the TapChager has physical capability to move the tap uder load. Also used i the IEC calculatios to idicate if the tap ca move o load. The meaig of the combiatios for TapChager.TapChagerCotrol ad TapChager.ltcFlag are described i the followig tableerror! Referece source ot foud.. Madatory TapChager. ltcflag False True True TapChager. TapChagerCotrol Not preset Not preset Preset Descriptio A real ad fixed tap that is ot cotrolled ad caot be moved o load (maual tap chage). Power flow caot be set to chage the tap for voltage cotrol durig the calculatio. A real ad fixed tap that is ot cotrolled but ca be moved uder load, e.g. maually. Power flow caot be set to chage the tap for voltage cotrol durig the calculatio. Optimal power flow might have access to these taps ad chage i order to optimize. Also State Estimator may estimate the tap positio to fid a better solutio for the system state. A real tap with a possibility to chage taps automatically for voltage cotrol/active power (load flow) eabled. Depedig o the RegulatigCotrol.eabled ad TapChager.cotrolEabled i SSH, the power flow shall or shall ot participate i the regulatio. I cases where the RegulatigCotrol is associated with more tha oe tap chager or other devices the attribute TapChager.cotrolEabled ca 37

38 ID Specificatio Type be set to false i order to set which of the taps are ot eabled. False Preset A artificial tap chager ca be used to simulate cotrol behavior i power flow. MSPEC4. Please ote that SvTapStep is required for all TapChagers. CGMES supports ACLieSegmet-s betwee differet termial voltages. The followig implemetatio is required: Madatory All implemetatios shall use associatio to a BaseVoltage for the purpose of ay per uit calculatios ad shall ot rely o the voltages (either omial or actual values obtaied by previous or curret solutio) at the odes, which the ACLieSegmet coects to. I case there are itercoected ACLieSegmets with differet BaseVoltage for differet parts of the etworks (whe assemblig differet model authority sets) the applicatio eeds to hadle this to esure accurate physical uits. MSPEC5. The followig best practice implemetatio is recommeded related to GeographicalRegio as SubGeographicalRegio: Madatory Oe GeographicalRegio should be exchaged per MAS. I case TSOs have a eed to have the same GeographicalRegio (i.e. multiple TSOs i a coutry) the class GeographicalRegio shall be preset i all TSO models ad shall have differet rdf:id, but ca have same ame/descriptio. SubGeographicalRegio is ormally a TSO or sub-area of a TSO. There is o specific amig covetio defied. MSPEC6. It is allowed to have values for GeeratigUit.ormalPF which sum is differet tha 1. The applicatio that imports such model shall have a load flow calculatio logic setup (for differet MAS that use very differet ormalpf values, the values must be ormalized) to use the iformatio for the purpose of the distributed slack ad preserve the origial values of GeeratigUit.ormalPF i case of export. Example of GeeratigUit.ormalPF values (before ormalizatio) for differet MAS Madatory MAS 1 MAS MAS 3 GeeratigUit.ormalPF for Ge GeeratigUit.ormalPF for Ge GeeratigUit.ormalPF for Ge MSPEC7. The applicatios shall follow strictly the descriptio of the PowerTrasformerEd which states for a two Termial PowerTrasformer the high voltage PowerTrasformerEd has o zero Madatory

39 ID Specificatio Type values o r, r0, x, ad x0 while the low voltage PowerTrasformerEd has zero values for r, r0, x, ad x0.. The high voltage side is give by the TrasformerEd.edNumber: Number for this trasformer ed, correspodig to the ed's order i the power trasformer vector group or phase agle clock umber. Highest voltage widig should be 1. Each ed withi a power trasformer should have a uique subsequet ed umber. Note the trasformer ed umber eed ot match the termial sequece umber. I case of a two widig trasformer with same rated voltage (PowerTrasformerEd.ratedU) o both sides the applicatio makes sure that oly oe side has TrasformerEd.edNumber equals to 1. Therefore the parameters are always provided for PowerTrasformerEd which has TrasformerEd.edNumber equal to 1. MSPEC8. MSPEC9. PhaseTapChagerTablePoit.agle i CGMES shall be implemeted cosiderig that A positive value idicates a positive phase shift from the widig where the tap is located to the other widig (for a two-widig trasformer). The followig rules are applied regardig the slack geerator: Madatory Madatory SychroousMachie.referecePriority is used to defie the slack geerator - referece agle. SychroousMachie.referecePriority is a required attribute i the SSH. I SSH - SychroousMachie.referecePriority - Priority of uit for use as powerflow voltage phase agle referece bus selectio. 0 = do t care (default) 1 = highest priority. is less tha 1 ad so o. Please ote that GeeratigUit.ormalPF is used for represetig distributed slack participatio factor. I SV - TopologicalIslad. AgleRefTopologicalNode - The agle referece ode is the TopologicalNode to which a sychroous machie is coected ad refereced from TopologicalIslad.AgleRefTopologicalNode. Therefore, this is the TopologicalNode to which a SychroousMachie is coected ad has SychroousMachie.referecePriority equals 1 i SSH. MSPEC10. The attribute SychroousMachie.qPercet shall be used as a participatio factor ot ecessarily summig up to 100% for the participatig devices i the cotrol. The reaso for this statemet is that the attribute is exchaged i the EQ profile. The participatio of the devices regulatig particular ode ca be set i other profiles such as SSH. Therefore, the implemetatios shall cosider this i the load flow calculatio ad ormalize the participatio based o what devices are participatig i the regulatio of a particular ode. MSPEC11. The TopologicalIslad-s for a merged model which are defied i the state variables istace file for the merged model are created with the Madatory Madatory 39

40 ID Specificatio Type solvig o the power flow of the merged model, i.e. there are o TopologicalIslad-s defied per MAS i a merged model. I case a solved model is exchaged for a sigle MAS the state variables profile must iclude at least oe istace of TopologicalIslad. MSPEC1. Iterpretatio of parameters of PowerTrasformerEd Madatory r+jx u g+jb A two widig PowerTrasformer has two PowerTrasformerEds. This gives the optio to specify the impedace values for the equivalet pi-model completely at oe ed or split them betwee the two eds. The impedaces shall be specified at the primary voltage side. The left side is the primary (high voltage) voltage side. MSPEC13. There are two differet use cases related to the associatio Termial.TopologicalNode: reductio away of the Switchig details to create bus-brach style model iteded for traditioal plaig oly. keep the detailed model icludig the Switches ad provide topology results also about the Switches. I cases of creatio of a bus-brach model from a ode-breaker model oretaied Switches are of o iterest ad their Termial.TopologicalNode refereces shall ot be icluded. If istead the model is iteded to stay ode-breaker it is of iterest to kow if a Switch has bee reduced away idicated by the two Switch Termial.TopologicalNodes referrig the same TopologicalNode. if a ope Switch coect two differet TopologicalNodes that is useful whe studyig the cosequeces of closig the switch. I this case Termial.TopologicalNode shall be icluded for all Switches. If the two sides of a Switch are coected to the same CoectivityNode this should be cosidered a error. A Switch with the two sides coected to the same TopologicalNode is valid ad ormal situatio, if ot retaied. A Switch coectig BusbarSectios at differet VoltageLevels is a error. MSPEC14. UitMultiplier is ot exchaged. It is defied that the multiplier is: M for W, VA, VAh, Wh, VArh ad Var k for volt 1 for all the rest of UitSymbol values. Madatory Madatory

41 ID Specificatio Type MSPEC15. Load sig covetio for SSH ad SV is used for attributes where the sig covetio is ot specified. For reactive power (e.g. o RotatigMachie, StaticVarCompesator, etc.) positive meas iductive. For EQ ratigs the equipmet is used as a referece rather tha the ode. MSPEC16. There shall ot be ay groud voltage level. The CoectivityNode coected to the Groud istace belogs to the same cotaimet istace as the groudig device. This meas that the Groud istaces are cotaied i the same voltage level where other switchig devices are cotaied with a o-zero BaseVoltage. Madatory Madatory 6 CGMES goverace The overall goverig process of the CGMES is a complex process ad icludes the followig sub-processes: Stadardisatio process a process to develop the CGMES, ad which relies o the latest IEC CIM related stadards. Iteroperability process the process to coduct IOPs targetig verificatio of the CGMES ad IEC CIM stadards. Feedback to stadardisatio bodies ad orgaisatios ivolved i the developmet of differet profiles which form part of the CGMES. Busiess process all busiess processes which use the CGMES, They defie requiremets ad request additioal improvemets due to busiess eeds. CGMES coformace process this process esures that tools used by parties ivolved i a exchage utilisig the CGMES are implemetig the CGMES correctly. Implemetatio process the implemetatio process is triggered by a busiess process/eed. It aims to apply a certai versio of the CGMES to a busiess process. The followig chart illustrates the mai stages related to the CGMES. 41

42 CGMES process Operatioal versio of the CGMES Implemetatio Coformace Extesio Extesio Approval Approval Developmet Busiess process requiremets Defie rules ad procedures for coformace with the CGMES ENTSO-E CGM discussios IEC WG13 discussios Defie Coformity Assessmet Scheme Agreemet Tools developmet (Vedors & TSOs) IOP to verify CGMES profiles ENTSO-E aalysis of IOP results; recommedatio to decisio bodies Trigger & deadlie Coformity Tests Discussio with IEC WG13 ad propose IEC Std extesios ENTSO-E decisio Tools available for TSOs busiess TSO busiess process uses ew release Deadlie Developmet process Busiess eed to modify the CGMES ad release of a major versio Apply chages Need release of a mior versio 6.1 Versios of the CGMES ad the profiles Each versio of the CGMES ad the profiles part of the CGMES has its uique versio idetifier. The followig rules related to versioig are defied: ID Specificatio Type VERS1. The format of a versio of the CGMES is xx.yy.zzz where xx, yy ad zzz are o-egative itegers, ad must ot cotai leadig zeroes, ad: xx - ames the major versio of the CGMES yy ames the mior versio of the CGMES zzz ames the revisio versio of the CGMES VERS. VERS3. VERS4. VERS5. VERS6. Each profile part of the CGMES is assiged with a versio defied by the profile URI which shall be declared i the file header of the istace files. The profile URI is specified i the UML of the CGMES. A profile URI chages every time a mior or a major versio of a profile is released. The amespace URI of the ENTSO-E extesios chages every time a mior or a major versio of the extesio package is released. The amespace UML chages every time the CGMES chages the base versio of the CIM, e.g. the base UML chages from CIM 16 to CIM 17. Each of the CGMES profiles is related to a profile defied by the IEC. The ENTSO-E UML lists the base URI of the IEC profiles for iformatio oly ad to

43 ID Specificatio Type lik a specific profile of the CGMES to the closest IEC CIM profile. This iformatio is provided i the base URI attribute of the versio class to each profile of the CGMES VERS7. VERS8. VERS9. VERS10. VERS11. VERS1. VERS13. A mior versio is a compatible chage to a profile. The mior versio must be icremeted if ew, backwards compatible fuctioality is itroduced to the CGMES. It must be icremeted if ay fuctioality is marked as deprecated. It may be icremeted if substatial ew fuctioality or improvemets are itroduced to the CGMES by addig additioal profiles ad/or ENTSO-E extesio. It may iclude revisio level chages. Revisio versio must be reset to 0 whe mior versio is icremeted. The umber of a major must be icremeted if ay backwards icompatible chages are itroduced to the CGMES, e.g. somethig is deleted. It may iclude mior ad revisio level chages if the amout of chages is sigificat. The major versio will also be icremeted if oe or more profile is o loger backwards compatible. Mior ad revisio versio umbers must be reset to 0 whe major versio is icremeted. Updates belogig to a mior versio update should ot break the iteroperability for a major profile exchage. This meas that a tool which supports a profile versio, e.g..4 ( major versio, ad 4 mior versio) shall be able to import a file which is geerated based o profile versio.5 where all the additioal classes, attributes ad associatios are igored. The revisio versio must be icremeted if oly backwards compatible error fixes are itroduced. A fix is defied as a iteral chage that fixes icorrect behaviour. Updatig documetatio or a class, a attribute or a profile to reflect the iteded behaviour are cosidered error fixes. A pre-release versio may be deoted by appedig a hyphe ad a series of dot separated idetifiers immediately followig the revisio versio. Idetifiers must comprise oly ASCII alphaumeric ad hyphe [0-9a-Za-z-]. Idetifiers must ot be empty. Numeric idetifiers must ot iclude leadig zeroes. A prerelease versio idicates that the versio is ustable ad might ot satisfy the iteded compatibility requiremets as deoted by its associated ormal versio. Example:.5.0-alpha. Oce a versioed package has bee released, the cotets of that versio must ot be modified. Ay modificatios must be released as a ew versio. The key words "must", "must ot", "required", "shall", "shall ot", "should", "should ot", "recommeded", "may", ad "optioal" i this sectio of the CGMES are to be iterpreted as described i RFC Coformity assessmet Coformity assessmet of tools is ecessary to cofirm that tools comply with a give profile part of the CGMES ad ca be used for model exchage i a give busiess process. Coformity assessmet is busiess drive ad esures reliability of the model exchages by cofirmig iteroperability betwee applicatios. The coformity assessmet processes that shall be followed is defied i the ENTSO-E CGMES Coformity Assessmet Framework. 43

44 Each ew versio of a tool shall be tested for coformity with a particular versio of the CGMES used i ENTSO-E busiess processes prior to its usage i the busiess processes. ENTSO-E members are resposible for esurig that tools which they use i the frame ENTSO-E busiess processes coform to the CGMES. Test cofiguratios (models) represetig the mai fuctioalities of the profiles of the CGMES shall be publicly available to all iterested parties o later tha 3 moths after the approval of a major or mior release of the CGMES or its profiles. Depedig o the complexity of the chages i the profiles the decisio body approvig the CGMES shall either cofirm this deadlie or specify aother deadlie. Each ew versio of the CGMES shall iclude iformatio o which coformity assessmet procedures ad test cofiguratios should be updated. Coformity assessmet shall rely o a machie readable way of defiig the validatio rules ad describig the costraits valid for a certai profile. Object Costrait Laguage (OCL) is used for this purpose. 6.3 Implemetatio process The implemetatio of a versio of the CGMES for use i a busiess process is lauched as soo as the coformity assessmet process has bee fialised. The followig rules are defied for the implemetatio process: The implemetatio process is triggered by the body resposible for the model exchage. The body defies the deadlie whe the implemetatio process shall ed ad the busiess process switches to the ew versio of the CGMES. The implemetatio process icludes a period durig which TSOs shall upgrade their tools ad a period durig which a trial tests ruig the busiess process with the ew versio of the CGMES. This is especially valid for operatioal exchages where the exchage shall be reliable ad completed more frequetly tha a plaig model exchage process. The CGMES cotais various profiles. The implemetatio of each of them ca have a differet schedule depedig o the busiess eeds. Due to the differet requiremets of the busiess processes, differet versios of the CGMES profiles ca be simultaeously operatioal. The ENTSO-E Secretariat shall maitai a publicly available list of versio of the CGMES used i busiess processes. Vedors ad TSOs shall adapt the implemetatio process ad the support to the model exchage processes ad be able to cope with a variety of the CGMES versios used i the exchages. Busiess processes shall be adapted i order to allow smooth iterfaces betwee mai types of exchage such as plaig to plaig, operatio to operatio, operatio to plaig, iterface with distributio, etc. Busiess processes shall aim to use a limited umber of differet versios of the CGMES i order to decrease maiteace effort by TSOs ad facilitate iteroperability of data exchages betwee busiess processes.

45 Aex A (ormative) Template for further restrictios o amig IdetifiedObject.ame.descriptio.eergyIdetCodeEic.shortName Class ame Status [r, o, ] Required cotet/rules Status [r, o, ] Required cotet/rules Status [r, o, ] Required cotet/rules Status [r, o, ] Required cotet/rules Leged: r the attribute is required; o - the attribute is optioal; - users do ot eed to have the ability to add ame to the attribute. 45

46 Aex B (ormative) Summary of specific rules for amig covetio B.1 IdetifiedObject.ame Huma readable ame with a imum strig legth of 3 characters. The legth restrictio is defied i the IEC IdetifiedObject.ame is a required attribute for the Boudary Equipmet ad Boudary Topology profiles. The IdetifiedObject.ame shall be cosistet with the ame of the object used i compaies, i daily operatio (e. g. i SCADA systems), i plaig processes or i asset related systems. The IdetifiedObject.ame should allow for iter-commuicatig of TSO, usig geeral ames. B. IdetifiedObject.descriptio Huma readable descriptio with imum strig legth of 56 characters. The legth restrictio is defied i the IEC IdetifiedObject.descriptio is a required attribute for the Boudary Equipmet ad Boudary Topology profiles. B.3 IdetifiedObject.eergyIdetCodeEic It is a ENTSO-E extesio of the IEC CIM. The followig descriptio was give i the UML for this attribute: The attribute is used for a exchage of the EIC code (Eergy idetificatio Code). The legth of the strig is 16 characters as defied by the EIC code. Refereces: Local issuig offices for EIC: EIC descriptio: B.4 IdetifiedObject.shortName It is a ENTSO-E extesio of the IEC CIM. The followig descriptio was give i the UML for this attribute: The attribute is used for a exchage of a huma readable short ame with legth of the strig 1 characters imum. B.5 CoectivityNode ad TopologicalNode.fromEdIsoCode It is a ENTSO-E extesio of the IEC CIM. The followig descriptio was give i the UML for this attribute: The attribute is used for a exchage of the ISO code of the regio to which the from side of the Boudary poit belogs to or is coected to. The ISO code is a two character coutry code as defied by ISO 3166 ( The legth of the strig is characters imum.

47 The attribute is required for the Boudary Model Authority Set where this attribute is used oly for the TopologicalNode i the Boudary Topology profile ad CoectivityNode i the Boudary Equipmet profile. B.6 CoectivityNode ad TopologicalNode.toEdIsoCode It is a ENTSO-E extesio of the IEC CIM. The followig descriptio was give i the UML for this attribute: The attribute is used for a exchage of the ISO code of the regio to which the to side of the Boudary poit belogs to or is coected to. The ISO code is a two character coutry code as defied by ISO 3166 ( The legth of the strig is characters imum. The attribute is a required for the Boudary Model Authority Set where this attribute is used oly for the TopologicalNode i the Boudary Topology profile ad CoectivityNode i the Boudary Equipmet profile. B.7 CoectivityNode ad TopologicalNode.fromEdName It is a ENTSO-E extesio of the IEC CIM. The followig descriptio was give i the UML for this attribute: The attribute is used for a exchage of a huma readable ame with legth of the strig 3 characters imum. The attribute covers two cases: if the Boudary poit is placed o a tie-lie the attribute is used for exchage of the geographical ame of the substatio to which the from side of the tie-lie is coected. if the Boudary poit is placed i a substatio the attribute is used for exchage of the ame of the elemet (e.g. PowerTrasformer, ACLieSegmet, Switch, etc) to which the from side of the Boudary poit is coected. The attribute is required for the Boudary Model Authority Set where it is used oly for the TopologicalNode i the Boudary Topology profile ad CoectivityNode i the Boudary Equipmet profile. B.8 CoectivityNode ad TopologicalNode.toEdName It is a ENTSO-E extesio of the CIM. The followig descriptio was give i the UML for this attribute: The attribute is used for a exchage of a huma readable ame with legth of the strig 3 characters imum. The attribute covers two cases: if the Boudary poit is placed o a tie-lie the attribute is used for exchage of the geographical ame of the substatio to which the to side of the tie-lie is coected. if the Boudary poit is placed i a substatio the attribute is used for exchage of the ame of the elemet (e.g. PowerTrasformer, ACLieSegmet, Switch, etc) to which the to side of the Boudary poit is coected. The attribute is required for the Boudary Model Authority Set where it is used oly for the TopologicalNode i the Boudary Topology profile ad CoectivityNode i the Boudary Equipmet profile. B.9 CoectivityNode ad TopologicalNode.fromEdNameTso It is a ENTSO-E extesio of the IEC CIM. The followig descriptio was give i the UML for this attribute: The attribute is used for a exchage of the ame of the TSO to which the from side of the Boudary poit belogs or is coected to. The legth of the strig is 3 characters imum. The attribute is required for the Boudary Model Authority Set where it is used oly for the TopologicalNode i the Boudary Topology profile ad CoectivityNode i the Boudary Equipmet profile. 47

48 B.10 CoectivityNode ad TopologicalNode.toEdNameTso It is a ENTSO-E extesio of the IEC CIM. The followig descriptio was give i the UML for this attribute: The attribute is used for a exchage of the ame of the TSO to which the to side of the Boudary poit belogs or it is coected. The legth of the strig is 3 characters imum. The attribute is required for the Boudary Model Authority Set where it is used oly for the TopologicalNode i the Boudary Topology profile ad CoectivityNode i the Boudary Equipmet profile. B.11 Future developmets o CIM for dyamics The followig gaps ad eeds for future developmet are curretly idetified. Discussio regardig these topics is expected to: Exted user-defied models approach of the dyamics profile. The class StaticVarcompesator is preset i the equipmet model, but is ot represeted i the dyamic model. The class could probably be used to represet differet FACTS compoets, although it should be possible to defie type of SVC (TCR,TCR/TSC, STATCOM) as this is of importace whe it comes to how dyamic respose is modelled. There are o models represetig brach quatities (like lie relays ad models which measure lie flow). It is critical that this type of model should be tested at the IOP, sice the iput ad behaviour is very differet from uit models (topology depedecy). Clarificatio regardig wid farms modellig is ecessary. There is a eed to verify that the models are compliat with the last IEC stadard o wid modellig. There is also the eed for adequate modellig of the wid power plats/parks. There are o relay models at all, whether for lies or for loads/uits. Frequecy depedet load relays are importat. Models to represet dyamics behaviour of HVDC are ecessary.

49 Aex C (ormative) File header guidelies C.1 Itroductio The aex is providig guidace o how to apply IEC which is defiig file headers for complete istace files ad differece istace files. C. Exchage scearios The IEC gives as a example the followig figure which is used i order to explai what iformatio should be provided i differet file headers. Equipmet Topology State Variables E1 T1 S1 S T S3 Time E T3 S4 E3 E3 S5 E4 T4 S6 Profile Full model DifferetialModel DepedetO Supersedes 49

50 C.3 Examples C.3.1 Example 1: File header of full model This example is for full model E1 from the figure i sectio C.. <?xml versio="1.0"?> Sytax <rdf:rdf xmls:rdf=" xmls:cim=" xmls:md=" xmls:etsoe= 3/1#> <md:fullmodel rdf:about="ur:uuid:bcb6877a-e948-11e3-89cf-8687f4fc15c"> <md:model.sceariotime> T17:00:00.000Z</md:Model.scearioTime> <md:model.created> T17:48:31.474Z</md:Model.created> <md:model.descriptio>cgmes Coformity Assessmet: This is guidelies o the file header.</md:model.descriptio> <md:model.versio>1</md:model.versio> <md:model.profile> e/3/1</md:model.profile> <md:model.profile> eratio/3/1</md:model.profile> <md:model.profile> rtcircuit/3/1</md:model.profile> <md:model.modeligauthorityset> g/cgmes/.4.14</md:model.modeligauthorityset> </md:fullmodel> Commet/Explaatio This is the ID of the model icluded i the istace file. Please refer to Chapter 4.3 i the CGMES. The ID to which other models (full or differece) refer i case of deped o or supersede. Please ote that the ur:uuid: is used oly for rdf:about or rdf:resource i the file header, i.e. it is ot applied for other elemets i the istace file. This is the date & time that this model represets, i.e. for which the model is valid. The format is a exteded format accordig to the ISO The ENTSO-E exchages should refer to UTC. The date & time whe the model was created. It is the time of the serializatio. The format is a exteded format accordig to the ISO The ENTSO-E exchages should refer to UTC. A descriptio of the model ad explaatio of the purpose. Versio of the model. If the istace file is imported ad exported with o chage the versio umber is the kept same. The versio chages oly if the cotet of the file chages. It is the same logic as for the header id (see CGMES [R ]). The versio is the huma readable id. The versio is iteger umber. Oe to may URN/URI describig the profiles that govers this model. It uiquely idetifies the profiles ad its versio. I this case EQ istace file cotais oe profile. Additioal profile URN/URI are icluded if classes ad attributes that belog to Operatio ad Short Circuit are used ad the istace file is iteded for such use. A URN/URI referrig to the orgaisatio role / model authority set referece. The orgaizatio role is the source of the model. It is the same for all profiles part of a model exchage. This cocept might be modified i the future whe applyig the cocept of frames which is uder discussio.

51 C.3. Example : File header of full model that is depedig o aother model This example is for full model T1 from the figure i sectio C.. Sytax <?xml versio="1.0"?> <rdf:rdf xmls:rdf=" xmls:cim=" xmls:md=" xmls:etsoe= tesio/3/1#> <md:fullmodel rdf:about="ur:uuid:d63e4784- e94b-11e3-89cf-8687f4fc15c"> <md:model.sceariotime> T17:00:00.000Z</md:Model.scearioTime> <md:model.created> T17:48:31.474Z</md:Model.created> <md:model.descriptio>cgmes Coformity Assessmet: This is guidelies o the file header.</md:model.descriptio> <md:model.versio>1</md:model.versio> <md:model.profile> ogy/4/1</md:model.profile> <md:model.depedeto rdf:resource="ur:uuid:bcb6877a-e948-11e3-89cf-8687f4fc15c" /> <md:model.modeligauthorityset> /Plaig/CGMES/.4.14</md:Model.modelig AuthoritySet> </md:fullmodel> Commet/Explaatio This is the ID of the model icluded i the istace file. Please refer to Chapter 4.3 i the CGMES. The ID to which other models (full or differece) refer i case of deped o or supersede. Please ote that the ur:uuid: is used oly for rdf:about or rdf:resource i the file header, i.e. it is ot applied for other elemets i the istace file. This is the date & time that this model represets, i.e. for which the model is valid. The format is a exteded format accordig to the ISO The ENTSO-E exchages should refer to UTC. The date & time whe the model was created. It is the time of the serializatio. The format is a exteded format accordig to the ISO The ENTSO-E exchages should refer to UTC. A descriptio of the model ad explaatio of the purpose. Versio of the model. If the istace file is imported ad exported with o chage the versio umber is the kept same. The versio chages oly if the cotet of the file chages. It is the same logic as for the header id (see CGMES [R ]). The versio is the huma readable id. The versio is iteger umber. Oe to may URN/URI describig the profiles that govers this model. It uiquely idetifies the profiles ad its versio. I this case it is the profile URI of the TP profile. A referece to the model documets that the model described by this documet depeds o, e.g. i this case the T1 model depeds o E1 model. I geeral there ca be 0 or may Model.DepedetO depedig o the profile ad the cotet of the istace file. A URN/URI referrig to the orgaisatio role / model authority set referece. The orgaizatio role is the source of the model. It is the same for all profiles part of a model exchage. This cocept might be modified i the future whe applyig the cocept of frames which is uder discussio. 51

52 C.3.3 Example 3: File header of full model that is depedig o a model ad supersedes aother model This example is for full model S from the figure i sectio C.. Sytax <?xml versio="1.0"?> <rdf:rdf xmls:rdf=" xmls:cim=" xmls:md=" xmls:etsoe= sio/3/1#> <md:fullmodel rdf:about="ur:uuid:aad4c9cce94d-11e3-89cf-8687f4fc15c"> <md:model.sceariotime> T17:00:00.000Z</md:Model.scearioTime> <md:model.created> T17:48:31.474Z</md:Model.created> <md:model.descriptio>cgmes Coformity Assessmet: This is guidelies o the file header.</md:model.descriptio> <md:model.versio></md:model.versio> <md:model.profile> ables/4/1</md:model.profile> <md:model.depedeto rdf:resource="ur:uuid:d63e4784-e94b-11e3-89cf-8687f4fc15c" /> <md:model.supersedes rdf:resource="ur:uuid:b1f4d506-e94f-11e3-89cf- 8687f4fc15c"/> Commet/Explaatio This is the ID of the model icluded i the istace file. Please refer to Chapter 4.3 i the CGMES. The ID to which other models (full or differece) refer i case of deped o or supersede. Please ote that the ur:uuid: is used oly for rdf:about or rdf:resource i the file header, i.e. it is ot applied for other elemets i the istace file. This is the date & time that this model represets, i.e. for which the model is valid. The format is a exteded format accordig to the ISO The ENTSO-E exchages should refer to UTC. The date & time whe the model was created. It is the time of the serializatio. The format is a exteded format accordig to the ISO The ENTSO-E exchages should refer to UTC. A descriptio of the model ad explaatio of the purpose. Versio of the model. If the istace file is imported ad exported with o chage the versio umber is the kept same. The versio chages oly if the cotet of the file chages. It is the same logic as for the header id (see CGMES [R ]). The versio is the huma readable id. The versio is iteger umber. Oe to may URN/URI describig the profiles that govers this model. It uiquely idetifies the profiles ad its versio. I this case it is the profile URI of the SV profile. A referece to the model documets that the model described by this documet depeds o, e.g. i this case the S model depeds o T1 model. I geeral there ca be 0 or may Model.DepedetO depedig o the profile ad the cotet of the istace file. Whe a model is updated the resultig model supersedes the models that were used as basis for the update. Hece this is a referece to the CIMXML documets which are superseded by this model. A model (or istace file) ca supersede 1 or more models, e.g. a differece model or a full model supersede multiple models (differece or full). I this case more tha oe Model.Supersedes are icluded i

53 <md:model.modeligauthorityset> aig/cgmes/.4.14</md:model.modeligautho rityset> </md:fullmodel> the header. The refereced documet(s) is (are) idetified by the URN/MRID/UUID i the FullModel rdf:about attribute whe full model(s) is (are) refereced ad by the URN/MRID/UUID i the DiffereceModel rdf:about attribute whe differece model(s) is (are) refereced. I this case the model S supersedes model S1 which has <md:fullmodel rdf:about="ur:uuid:b1f4d506-e94f- 11e3-89cf-8687f4fc15c"> A URN/URI referrig to the orgaisatio role / model authority set referece. The orgaizatio role is the source of the model. It is the same for all profiles part of a model exchage. This cocept might be modified i the future whe applyig the cocept of frames which is uder discussio. C.3.4 Example 4: File header of differece model that is depedig o a full model ad supersedes aother full model This example is for differece model T from the figure i sectio C.. Sytax <?xml versio="1.0"?> <rdf:rdf xmls:rdf=" xmls:cim=" xmls:dm=" xmls:md=" xmls:etsoe= tesio/3/1#> <dm:differecemodel rdf:about="ur:uuid:7ca7efa-e95-11e3-89cf- 8687f4fc15c"> <md:model.sceariotime> T17:00:00.000Z</md:Model.scearioTime> <md:model.created> T17:48:31.474Z</md:Model.created> <md:model.descriptio>cgmes Coformity Assessmet: This is guidelies o the file header.</md:model.descriptio> <md:model.versio></md:model.versio> Commet/Explaatio Please pay attetio that for differece models xmls:dm= is icluded as well This is the ID of the model icluded i the istace file. Please refer to Chapter 4.3 i the CGMES. The ID to which other models (full or differece) refer i case of deped o or supersede. Please ote that the ur:uuid: is used oly for rdf:about or rdf:resource i the file header, i.e. it is ot applied for other elemets i the istace file. This is the date & time that this model represets, i.e. for which the model is valid. The format is a exteded format accordig to the ISO The ENTSO-E exchages should refer to UTC. The date & time whe the model was created. It is the time of the serializatio. The format is a exteded format accordig to the ISO The ENTSO-E exchages should refer to UTC. A descriptio of the model ad explaatio of the purpose. Versio of the model. If the istace file is imported ad exported with o chage the versio umber is the kept same. The versio chages oly if the cotet of the file chages. It is the same logic as for the header id (see 53

54 <md:model.profile> ogy/4/1</md:model.profile> <md:model.depedeto rdf:resource="ur:uuid:bcb6877a-e948-11e3-89cf-8687f4fc15c" /> <md:model.supersedes rdf:resource="ur:uuid:d63e4784-e94b-11e3-89cf-8687f4fc15c"/> <md:model.modeligauthorityset> /Plaig/CGMES/.4.14</md:Model.modelig AuthoritySet> Here the place for the cotet of the differece file </dm:differecemodel> CGMES [R ]). The versio is the huma readable id. The versio is iteger umber. Oe to may URN/URI describig the profiles that govers this model. It uiquely idetifies the profiles ad its versio. I this case it is the profile URI of the TP profile. A referece to the model documets that the model described by this documet depeds o, e.g. i this case the T model depeds o E1 model. I geeral there ca be 0 or may Model.DepedetO depedig o the profile ad the cotet of the istace file. Whe a model is updated the resultig model supersedes the models that were used as basis for the update. Hece this is a referece to the CIMXML documets which are superseded by this model. A model (or istace file) ca supersede 1 or more models, e.g. a differece model or a full model supersede multiple models (differece or full). I this case more tha oe Model.Supersedes are icluded i the header. The refereced documet(s) is (are) idetified by the URN/MRID/UUID i the FullModel rdf:about attribute whe full model(s) is (are) refereced ad by the URN/MRID/UUID i the DiffereceModel rdf:about attribute whe differece model(s) is (are) refereced. I this case the model T supersedes model T1, i.e. this differece model is applied o the model which has the id metioed i this Model.Supersedes. A URN/URI referrig to the orgaisatio role / model authority set referece. The orgaizatio role is the source of the model. It is the same for all profiles part of a model exchage. This cocept might be modified i the future whe applyig the cocept of frames which is uder discussio. This follows the sytax as defied i the C.3.5 Example 5: File header of differece model that is depedig o a differece model ad supersedes aother differece model This example is for differece model T3 from the figure i sectio C.. Sytax Commet/Explaatio <?xml versio="1.0"?> <rdf:rdf xmls:rdf=" xmls:cim=" xmls:dm=" xmls:md=" xmls:etsoe= tesio/3/1#> <dm:differecemodel rdf:about="ur:uuid:8033db8-ea73-11e3-9df6-8687f4fc15c"> Please pay attetio that for differece models xmls:dm= is icluded as well This is the ID of the model icluded i the istace file. Please refer to Chapter 4.3 i the CGMES. The ID to which other models (full or differece) refer i case of deped o or supersede.

55 <md:model.sceariotime> T17:00:00.000Z</md:Model.scearioTime> <md:model.created> T17:48:31.474Z</md:Model.created> <md:model.descriptio>cgmes Coformity Assessmet: This is guidelies o the file header.</md:model.descriptio> <md:model.versio>3</md:model.versio> <md:model.profile> ogy/4/1</md:model.profile> <md:model.depedeto rdf:resource="ur:uuid:1a419b4-ea74-11e3-9df6-8687f4fc15c" /> <md:model.supersedes rdf:resource="ur:uuid:7ca7efa-e95-11e3-89cf-8687f4fc15c"/> <md:model.modeligauthorityset> MES/.4.14</md:Model.modeligAuthoritySet> Please ote that the ur:uuid: is used oly for rdf:about or rdf:resource i the file header, i.e. it is ot applied for other elemets i the istace file. This is the date & time that this model represets, i.e. for which the model is valid. The format is a exteded format accordig to the ISO The ENTSO-E exchages should refer to UTC. The date & time whe the model was created. It is the time of the serializatio. The format is a exteded format accordig to the ISO The ENTSO-E exchages should refer to UTC. A descriptio of the model ad explaatio of the purpose. Versio of the model. If the istace file is imported ad exported with o chage the versio umber is the kept same. The versio chages oly if the cotet of the file chages. It is the same logic as for the header id (see CGMES [R ]). The versio is the huma readable id. The versio is iteger umber. Oe to may URN/URI describig the profiles that govers this model. It uiquely idetifies the profiles ad its versio. I this case it is the profile URI of the TP profile. A referece to the model documets that the model described by this documet depeds o, e.g. i this case the T3 model depeds o differece model E which has <dm:differecemodel rdf:about="ur:uuid:1a419b4- ea74-11e3-9df6-8687f4fc15c">. I geeral there ca be 0 or may Model.DepedetO depedig o the profile ad the cotet of the istace file. Whe a model is updated the resultig model supersedes the models that were used as basis for the update. Hece this is a referece to the CIMXML documets which are superseded by this model. A model (or istace file) ca supersede 1 or more models, e.g. a differece model or a full model supersede multiple models (differece or full). I this case more tha oe Model.Supersedes are icluded i the header. The refereced documet(s) is (are) idetified by the URN/MRID/UUID i the FullModel rdf:about attribute whe full model(s) is (are) refereced ad by the URN/MRID/UUID i the DiffereceModel rdf:about attribute whe differece model(s) is (are) refereced. I this case the model T3 supersedes the differece model T, i.e. this differece model is applied o the model which has the id metioed i this Model.Supersedes. A URN/URI referrig to the orgaisatio role / model authority set referece. The orgaizatio role is the source of the model. It is the same for all profiles part of a model exchage. This cocept might be modified i the future whe applyig the cocept of frames which is uder discussio. Here the place for the cotet of the differece file This follows the sytax as defied i the </dm:differecemodel> 55

56 Aex D (ormative) PST trasformer modellig D.1 Itroductio This aex describes Phase-Shiftig Trasformer (PST) modellig accordig to the type ad techology of the equipmet; ad more specifically, equivalet series reactace of phase shifters i the positive sequece as a fuctio of the phase shift agle. I these specific models, the resistaces ad the magetizig currets are always eglected. This documet also provides the mappig betwee the equatios for each type ad techology of PST to the CIM classes ad attributes which are icluded i the CGMES. D. Mappig to CIM classes ad attributes To illustrate how to use the PST modellig described i this documet, the mappig to CGMES classes is preseted i the followig table: PST type CIM class Geeral Case Symmetrical phase shifters Asymmetrical phase shifter I-phase trasformer ad symmetrical phase shifter I-phase trasformer ad asymmetrical phase shifter cim:phasetapchagertabular cim:phasetapchagersymmetrical or cim:phasetapchagerliear cim:phasetapchagerasymmetrical cim:phasetapchagersymmetrical ad cim:ratiotapchager cim:phasetapchagerasymmetrical ad cim:ratiotapchager Recommedatio: It is highly recommeded to use tabular data to exchage PST parameters (cim:phasetapchagertabular) istead of havig to recalculate the parameters per tap accordig to each model type Notes: - Agle sig covetio: Positive value idicates a positive phase shift from the widig where the tap is located to the other widig (for a two-widig trasformer). - RatioTapChager.stepVoltageIcremet: Both positive ad egative values are allowed. - PhaseTapChagerNoLiear.voltageStepIcremet: Both positive ad egative values are allowed. - PhaseTapChagerAsymmetrical.widigCoectioAgle: Both positive ad egative values are allowed. PST attribute CIM attribute cim:phasetapchagertablepoit.step

57 0 u cim:tapchager.eutralstep cim:phasetapchagernoliear.voltagestepicremet r cim:tapchagertablepoit.ratio cim:phasetapchagertablepoit.agle cim:phasetapchagerliear.stepphaseshifticremet X () cim:tapchagertablepoit.x X (0) cim:phasetapchagerliear.xmi or cim:phasetapchagernoliear.xmi X ( ) cim:phasetapchagerliear.xmax or cim:phasetapchagernoliear.xmax cim:phasetapchagerasymmetrical.widigcoectioagle D.3 Reactace formulas summary table Equipmet type Symmetrical Equivalet series reactace as a fuctio of the phase shift agle Phase shifters X ) X (0) X ( ) X (0) Asymmetrical si / ( si / Phase Shifter X ( ) X (0) X ( ) X (0) I-phase trasformer ad symmetrical phase shifter I-phase trasformer ad asymmetrical phase shifter X ( r, ) X X ( r, ) X X ( 0 r r ta ta si ta cos si ta cos r si / r X (0) X ( ) X (0) r om om ) X r om r r om X (0) ta si ta ( r) cos (0) ta ( ) si ta cos r si / with ( r ) A ta r om r 0 ta si 0 si ta cos cos ad 0 ( r ) om Variable Meaig 57

58 r om Maximal phase shift: the imum agle value of the phase shifter agles table Nomial ratio of the i-phase trasformer 0 Maximal phase shift whe the i-phase trasformer ratio is omial

59 D.4 Symmetrical Phase shifters D.4.1 Oe phase diagram ad equatios e j X() I V 1 V 1 V 1 1 V 1 1 V j V V1e j jx ( ) I V 1' j V11 jsi e e V1 D.4. Expressio of the agle ad ratio per tap Based o the figure above: ( ) or ta 0 u A ) r 1 ( 0 D.4.3 Expressio of the equivalet series reactace give the agle Assumig the reactace of the regulatig widig varies as the square of the umber of turs, the equivalet reactace ca be writte as follows for o delta-hexagoal techologies (see proof i sectio D.9.1): 3 parameters: X : imal phase shift si / ( ) X (0) X ( ) X (0) si / X(0): equivalet series reactace at zero phase shift X(): equivalet series reactace at imal phase shift 1 variable: : curret phase shift 59

60 The formula above is valid for sigle or double core symmetrical phase shifters except for the hexagoal techology. For sigle core symmetrical phase shifters: X(0)= Impedace 5kV symmetrical double core phase shifter (i Ohm) Ohm measurmets from field test theoretical law phase shift agle (degree) D.4.4 Three-phase diagrams Dual core: Sigle core: Va Vb Vc Va Vb Vc I3a Ia Ib Ic V3a V3b V3c Va I1a I1b I1c I a I b I c Va I1a I1b I1c V a V b V c V a V b V c I4a I4b I4c Ia Ib Ic V4a Va Vc Ia Ib Ic Va Vc Shut trasformer Series trasformer

61 Sigle core, delta hexagoal: Va Vb Vc Ia Ib Ic Va I a I b I c V a V b V c Ia Ib Ic Va Vc D.5 Quadrature booster D.5.1 Oe phase diagram ad equatios V 1 V 1 e j X() I V 1 1 V 1 1 V j j ta e 1 j V 1' V11 V V V1e jx ( ) I ad vary with.cos = costat. 61

62 D.5. Expressio of the agle ad ratio per tap Based o the figure above: Ata ( 0 ) u r 1 ( ) u 1 0 D.5.3 Expressio of the equivalet series reactace give the agle Assumig the reactace of the regulatig widig varies as the square of the umber of turs, the equivalet reactace of the quadrature booster ca be writte as follows (see proof i sectio D.9.): X ( ) X (0) X ( ta ) X (0) ta 3 parameters: : imal phase shift X(0): equivalet series reactace at zero phase shift X(): equivalet series reactace at imal phase shift 1 variable: : curret phase shift For quadrature boosters with a sigle core: X(0)=0 D.5.4 Three-phase diagrams Dual core: Sigle core:

63 Va Vb Vc Va Vb Vc I3a Ia Ib Ic V3a V3b V3c Va I1a I1b I1c I a I b I c Va I1a I1b I1c V a V b V c V a V b V c I4a I4b I4c Ia Ib Ic V4a Va Vc Ia Ib Ic Va Vc Shut trasformer Series trasformer 63

64 D.6 Asymmetrical Phase Shifter D.6.1 Oe phase diagram ad equatios V 1 e j X() I V 1 V 1 1 V 1 1 V j ta j V 1' V11 e. e V1 j V V1. e jx ( ) I si ta cos is fixed, oly ad vary. D.6. Expressio of the agle ad ratio per tap Based o the figure above: ( 0) u si A ta 1 ( 0 ) u cos r 1 ( ) u si 1 ( ) u 0 0 si D.6.3 Expressio of the equivalet series reactace give the agle Assumig the reactace of the regulatig widig varies as the square of the umber of turs, the equivalet reactace ca be writte as follows (see proof i sectio D.9.3): X ( ) X (0) X ( ta ) X (0) ta si ta cos si ta cos

65 4 parameters: : imal phase shift X(0): equivalet series reactace at zero phase shift X(): equivalet series reactace at imal phase shift : boost voltage agle 1 variable: : curret phase shift D.6.4 Three-phase diagram Dual core: Va Vb Vc V3a I3a V3b V3c Va I1a I1b I1c V a V b V c I4a I4b I4c WINDINGS CONNECTIONS Ia Ib Ic V4a Va Vc Shut trasformer Series trasformer 65

66 D.7 I-phase trasformer ad symmetrical phase shifter D.7.1 Oe phase diagram ad equatios V 1 rv 1 e j X(r,) I V 1 V 1 1 V 1 1 V j j V V1e jx ( ) I. V 1' j r. V11 j si e e V1 r ad vary, ad =r D.7. Expressio of the agle ad ratio per tap Same as D.4. with the additio of the i-phase trasformer ratio r. D.7.3 Expressio of the equivalet series reactace give the agle ad the i-phase trasformer ratio Assumig: the reactace of the regulatig widig varies as the square of the umber of turs, the equivalet reactace is the sum of the reactace of the i-phase trasformer Xr ad the reactace of the phase shifter part X, the phase shiftig agle does ot deped o the i-phase ratio r The equivalet reactace ca be writte as follows (ot proved): X ( r, ) X r r si / r X (0) X ( ) X (0) om r om si / 6 Parameters:

67 rom: omial ratio of the i-phase trasformer Xr(rom): equivalet series reactace of the i-phase trasformer at omial i-phase ratio : imal phase shift X(0): equivalet series reactace of the phase shifter part at zero phase shift X(): equivalet series reactace of the phase shifter part at imal phase shift at omial iphase ratio (rom) Variables: r: curret ratio of the i-phase trasformer : curret phase shift D.7.4 Techology priciples No example foud. D.8 I-phase trasformer ad asymmetrical phase shifter D.8.1 Oe phase diagram ad equatios e j X(r,) I V 1 r V 1 rv 1 V 1 V 1 1 V 1 1 V (r) j ta j V 1' rv11 e. e V1 si ta cos j is fixed, oly r ad are variables, varies as a cosequece. V V1 jx ( ) I. e 67

68 D.8. Expressio of the agle ad ratio per tap Not proved. D.8.3 Expressio of the equivalet series reactace give the agle ad the i-phase trasformer ratio Assumig: the reactace of the regulatig widig varies as the square of the umber of turs, the equivalet reactace is the sum of the reactace of the i-phase trasformer Xr ad the reactace of the phase shifter part X, The equivalet series reactace ca be writte as follows (ot proved): X r 0 r X (0) X ( ) X (0) ta si ta ( r)cos ( r, ) X ta ( ) si ta cos r om r r om with si ( r ) A ta si ta cos cos with 0 ( rom) r 0 0 r om ta 6 Parameters: rom: omial ratio of the i-phase trasformer Xr(rom): equivalet series reactace of the i-phase trasformer at omial i-phase ratio rom : fix boost voltage agle 0 ( r ) : imal phase shift for omial i-phase ratio (rom) om X(0): equivalet series reactace of the phase shifter part at zero phase shift X( ): equivalet series reactace of the phase shifter part at imal phase shift at omial iphase ratio (rom) Variables: r: curret ratio of the i-phase trasformer : curret phase shift

69 For = / (quadrature booster): rom 0 ( r) Ata ta r D.8.4 Techology priciples I-phase regulatig auto-trasformer Series trasformer Switchig etwork Shut autotrasformer The phase shift regulatio may be o the shut or o the series trasformer D.9 Detailed calculatios ad examples D.9.1 Symmetrical Phase Shifters with two cores V V R V 1 Detailed three phase diagram 69

70 Z1/, 1/ turs VAX Z1/, 1/ turs VAX Ai IAi A1 IAo Ao Bi IBi B1 IBo Bo Ci ICi C1 ICo Co Z, turs IA /1.VAX IB IC IAi-IAo IBi-IBo ICi-ICo IC-IB IA-IC IB-IA A B C Series Trasformer VAY 4/3. VAY Z3, 3 turs Z4, 4 turs Shut Trasformer Oly 4 varies. Example of umerical values: 1=10 =318 3=680 4=18 X1=1,3 X=8,64 X3=101 Expressio of the output curret Io ad the shut curret I3=Ii-Io:

71 Whe cosiderig a ideal phase shifter, the coservatio of the electric power is writte: * * Si 3ViIi 3VoIo As the voltage agle is shifted by alpha: Vo e j Vi The curret agle must also be shifted by alpha as well: Io e j Ii The, the shut curret I3 Ii Io (1 e j ) Ii Expressio of the shut equivalet reactace The shut reactace Xshut() is defied as the equivalet reactace which crossed by the series iput curret (Ii) would produce the reactive losses of the shut trasformer: Qshut 3. Xshut ( ). Ii with: Qshut 3. X3. I3 3. X 4. I4 j / ) I3 Ii 1 e (1 cos ) Ii 4 si( 3 I 4 I3 4 Xshut ( ) 4 si( / ) 3 X 3 X 4 4 Hypothesis: X 4 X The Xshut ( ) 4 si / X 3 X Expressio of the equivalet series reactace 71

72 The series reactace Xseries() is defied as the equivalet reactace which crossed by the series iput curret (Ii) would produce the reactive losses of the series trasformer: Qseries 3. Xseries ( ). Ii with: X1 X1 Qseries 3.. Ii 3.. Io 3. X. I as see previously: Io e j Ii 1 1 series trasformer curret relatioship:. Ii. Io. I 1 j the I 1 e Ii ad 1 j 1 1 I Ii 1 e (1 cos ) Ii the 1 1 Xseries ( ) X1 1 (1 cos ) X X1 1 1 Xseries ( ) X1 X X si( / ) (1 si( / )) X Expressio of the total equivalet reactace X X ( ) X1 X 4 si / X 3 X 4 X 4 or with: X si / ( ) X (0) X ( ) X (0) si /

73 1 X (0) X1 X X ( 3 1 ) X (0) 4 si / X 3 X 4 X 4 Remark: oly varies. D.9. Quadrature boosters D.9..1 Quadrature booster with two cores DETAILED THREE PHASE DIAGRAM Va Vb Vc V3a I3a V3b V3c Va I1a I1b I1c V a V b V c I4a I4b I4c Ia Ib Ic V4a Va Vc Shut trasformer Series trasformer For each physical value X (X=V or I) X X ax a X with a b c j 3 a e shut trasformer with variable ratio 4/3 with X3 reactace o the primary widig ad X4 o the secodary widig: 73

74 V 3 V 4 X4 I4 X3 I3 3 4 Y Y I jx V I jx V I I I X X j V V Hypothesis: the X4 reactace varies like the square of the umber of turs 4: X X Series trasformer of fixed ratio 1/ with X1 reactace o the primary widig ad X o the secodary widig: I X X j V V 1 1 I I Lik betwee series ad shut trasformers: Primary widigs: V V 3 Secodary widigs: 3 ) ( 4 4 I j I a a I I I I a c b a ) ( 4 4 V j V a a V V V V c b a

75 Calculatio: V 4. 1 j 3. 3V 1 j X1 1 X 3 X X 3 I I3 j 3I1 3. At o load coditios (I=0): 4. 1 V j 3V 3. Ad geometrically: V V V V jv ta hece 4 4 ta ta X X 3 ta Ad V j 3V j X1 X 34 I ta comes: 4. 1 V j 3V 3. jxi with X ( ) X (0) X ( ) X (0) ta ta 75

76 D.9.. Quadrature booster with a sigle core Detailed three phase diagram Va Vb Vc Ia Ib Ic I a I b I c Va I1a I1b I1c V a V b V c Ia Ib Ic Va Vc 1 varies. I' j 3I V j 3V V 1 V 1 j X1 X I1 V j 1 3 V 1 j X1 X I1

77 77 Assumig X X I X X j V j V At o-load: V j V 1 3 Ad geometrically: V V V V jv ta hece ta ta 1 1 ta ta 1 1 ) ( X X X ta ta ) ( ) ( X X

78 D.9.3 Asymmetrical phase shifter D Asymmetrical phase shifter with two cores Detailed three phase diagram:

79 Va Vb Vc V3a I3a V3b V3c Va I1a I1b I1c V a V b V c I4=z.I I4a I4b I4c Ia Ib Ic V4a Va Vc Shut trasformer Series trasformer For each physical value X (X=V or I) X X ax a X with a b c j 3 a e shut trasformer equatios: 4 V 4 V3 3 j X 4 X 3 I I3 I 4 3 Hypothesis: the X reactace varies like the square of the k 1 ratio: X 4 X

80 Series trasformer of fixed ratio k with Xseries reactace o the primary widig: V 1 V 1 j X1 X I1 1 I I1 Lik betwee series ad shut trasformers: Primary widigs: V3 V z, a complex umber, determies the couplig betwee the series ad shut trasformer secodary widigs: I4 I4 z. I a V z. V 4 for a quadrature booster z j 3 Calculatio: V zv j X1 X z 1 X X 3 I I3. z. I1 3. At o load coditios (I=0): 4. 1 V. zv. 3. Ad geometrically: V e j ta. V si ta cos

81 81 V V V hece cos ta si cos ta si ta ta 4 4 Ad 1 cos ta si cos ta si ta ta I X X z X X j V j V comes: jxi V z V with cos ta si cos ta si ta ta (0) ) ( (0) ) ( X X X X

82 D.9.3. Asymmetrical phase shifter with a sigle core Va Vb Vc Ia Ib Ic I a I b I c Va I1a I1b I1c V a V b V c V=z.V Ia Ib Ic Va Vc Oly 1 varies. I' z. I V zv. V 1 V 1 j X1 X I1 V 1 z. V 1 j X1 X I1 Assumig X 1 X1 1 1 V 1 z. V X1 j 1 X 1 I1

83 83 At o-load: V z V 1. Ad geometrically: cos ta si ta. V e V j V V V hece cos ta si cos ta si ta ta 1 1 cos ta si cos ta si ta ta 1 1 ) ( X X X cos ta si cos ta si ta ta ) ( ) ( X X

84 D I-phase trasformer ad asymmetrical phase shifter Examples of detailed three-phase diagrams: voltage regulatig auto-trasformer ad Quadrature booster:

85 Voltage regulatig auto-trasformer ad Quadrature booster: 1 EHV widig HV widig 3 EV voltage regulatig widig 4 Phase shift regulatig widig 5 Tertiary widig 6 Primary widig of the series trasformer 7 Secodary widig of the series trasformer 85

86

87 Aex E (ormative) CGMES profiles versios The CGMES versio.5 uses the followig profiles ad extesios: XMI: ENTSOE_CGMES_v.4.15_7Aug014_XMI.zip HTML: ENTSOE_CGMES_v.4.15_7Aug014_HTML.zip RDFS: ENTSOE_CGMES_v.4.15_7Aug014_RDFS.zip HTML_EA: ENTSOE_CGMES_v.4.15_7Aug014_HTML_EA.zip PDF: ENTSOE_CGMES_v.4.15_7Aug014_PDF.pdf OCL: ENTSOE_CGMES_v.4.15_7Aug014_OCL.zip EQ_BD profile versio: 3.1 TP_BD profile versio: 3.1 EQ profile versio: 3.1 TP profile versio: 4.1 SSH profile versio: 1.1 SV profile versio: 4.1 DL profile versio: 3.1 GL profile versio:.1 87

88 Aex F (ormative) Use of Modelica i the Dyamics profile F.1 Itroductio The purpose of the aex is to illustrate the use of Modelica to describe models (cotrol diagrams) for dyamics simulatios. Dyamics models exchage supplies data for oe of the most complex aalyses of a power system. The requiremets of the data exchages are directly related to the level of detail of the power system modellig applied i a give area. The DY (dyamics) profile supports the exchage of dyamic behaviour models used by software applicatios which perform aalysis of the steady state stability (small-sigal stability) or trasiet stability of a power system as defied by IEEE / CIGRE Stadard Terms ad Defiitios for Power System Stability Aalysis. There are three ways i which the curret versio of the dyamics profile is desiged to support as follows: Stadard models exchage a simplified approach to exchage, where models are cotaied i packages i predefied libraries of classes which represet dyamic behaviours of elemets of the power system itercoected i a stadard maer. Block diagrams ad other iformatio are also defied. The curret profile supports a set of stadard models. User-defied models exchage - a more flexible approach which permits users to exchage the defiitios of a model by defiig elemetary cotrol blocks ad itercoectios betwee these blocks i a explicit maer i the istace data. It is a way i which to exchage full iformatio o user defied models. The profile does ot fully support this type of exchage, amely does ot support the mechaism to model the idividual elemets from the cotrol blocks ad describe how these are liked each other. Proprietary models exchage - a exchage which provides users with the ability to exchage the parameters of a model represetig a vedor-proprietary device where a explicit public descriptio of the model is ot desired. It is a way i which to exchage proprietary models, ad the models black box (dll, etc.). All parties participatig i the exchage should have the model (dll, etc.). Oly parameters of models are exchaged. The profile supports this approach. It allows for the exchage of model ame ad descriptio as well as a ulimited umber of parameters per model. Dyamics models are typically described usig both graphics ad text. Therefore there is a high level of complexity ad room for iterpretatio. Besides may other fuctioalities, Modelica facilitates the process of describig the behaviour of the elemets i the power system i a form of atural mathematical equatios. This approach limits the iterpretatio of the cotrol logic ad dyamic behaviour which is a challege i case the classically used methods to describe this are ot well documeted, because the geerated model ca be directly ru o stadard, ope tools to give referece results ad eable to better uderstad expected behaviours. Besides, Modelica leads to well-defied iterfaces, which are very useful for models reusability ad stadardisatio. As required by the CGMES, vedors shall support proprietary model exchage which shall be used for a exchage of user defied models if all parties ivolved i the exchage have modelled the user defied models i their tools.

89 Therefore the CGMES mechaism to exchage iformatio o the proprietary models is to demostrate how the proprietary models ca i fact be modelled based o Modelica code for differet elemets of the power system. F. Supported types user defied models by CGMES I its curret versio the DY profile of the CGMES supports the followig user defied models which are used to lik with the Modelica code. I case additioal dyamics models (e.g. to be able to represet the dyamics behaviour of HVDC, etc.) eed to be liked with the static (load flow) part of the model respective CIM classes ca be created ad associated with the equipmet. WidPlatUserDefied WidType1orTypeUserDefied WidType3or4UserDefied SychroousMachieUserDefied AsychroousMachieUserDefied TurbieGoverorUserDefied TurbieLoadCotrollerUserDefied MechaicalLoadUserDefied ExcitatioSystemUserDefied OverexcitatioLimiterUserDefied UderexcitatioLimiterUserDefied PowerSystemStabilizerUserDefied DiscotiiousExcitatioCotrolUserDefied PFVArCotrollerType1UserDefied VoltageAdjusterUserDefied PFVArCotrollerType1UserDefied VoltageCompesatorUserDefied LoadUserDefied All classes listed above are likig models coected as show i the itercoectio diagram below. It is importat to ote that this is also valid for cross compoud systems. I additio, ad just as a example, the class SychroousMachieUserDefied ca be used to lik a Modelica code that represets the behaviour of a give sychroous machie icludig the associated cotrols such as excitatio system, turbie, goveror, etc. 89

90 V Q,P,I Efd, Ifd PF,Q V I Uderexcitatio Limiter Overexcitatio Limiter Voel PF / VAr Cotroller Type Vpf/Vvar P,Q Vc Voltage Compesator V I PF / VAr Cotroller Type 1 Vcr Vcl Voltage Adjuster Vuel Vref V S Excitatio System Efd Ifd w,pe,f Sychroous Machie Vs Discotiuous Excitatio Cotrol Vst Vsi Power System Stabilizer Vsi Turbie Load Cotroller Pref Turbie- Goveror or Mechaical Load Vsi Pm (or Tm) NOTE: Vsi iput sigals may be of multiple types, which are eumerated by the IputSigalKid class Power system (etwork algebraic equatios) or sychroous machie bus Sychroous Machie Itercoectio F.3 Modellig of user defied model i the CGMES I order to illustrate the mechaism how Modelica code is coected to the CGMES a example of modellig of a simple excitatio system is preseted. I the CGMES the user defied model (i the example of excitatio system this is ExcitatioSystemUserDefied) class which is to be used to lik with the Modelica code is already properly liked to the respective sychroous machie i the load flow part of the model. This is illustrated i the UML diagram below.

91 The specific sychroous machie i the load flow part of the model. The specific excitatio system liked with a give sychroous machie. The user defied (Modelica code) model which is represetig a excitatio system for a specific sychroous machie. The figure below illustrates the approach applied to a turbie-goveror model. The same cocept is used to explai the modellig of the CGMES ExcSEXS excitatio system - the lik with Modelica code. 91

92 The ExcSEXS model i CGMES has the followig structure.