CIM Diagram Layout. Model Driven Architectures and Eclipse. OGO Open Grid Systems. Alan McMorran B.Eng Ph.D

Transcription

1 CIM Diagram Layout Model Driven Architectures and Eclipse Technologies for the Power Industry Alan McMorran B.Eng Ph.D G pen Grid Systems

2 Introduction The CIM is used widely for exchanging electrical network data for transmission, planning and distribution To aid the understanding of complex electrical models, engineers will use single-line diagrams and geographical overviews A great deal of effort (and cost) has often been required to build and then maintain these diagrams The CIM Diagram Layout profile will enable users to define these diagrams in a CIM format with direct links into the underlying CIM network data 2 pen Grid Systems

3 Exchanging Diagrams 3 G pen Grid Systems

4 Synchronising Exchanges A number of systems exchange electrical network (Domain) data GIS System Many of these systems also have graphical interface Control Centre System Control Centre System Planning System Users want to see the same single line diagram layout from one system to the next Substation Automation System Graphical Data Exchange Domain Data Exchange 4 pen Grid Systems

5 Graphics vs Layout The key question is whether it is better to exchange the diagram as a graphic or layout data The former would be graphical rendering data with links into the domain data, along with all information about icons, styles, colours etc. The latter provides the coordinates for each component and an optional style reference The receiving system then uses the domain data in combination with this layout data to generate the diagram 5 pen Grid Systems

6 Diagram Layout The CIM Diagram Layout profile builds on the existing IEC CIM model and adds classes for describing diagram layout By building on the existing CIM UML model, the related serialisation technologies for Resource Document Framework (RDF) XML and XML Schema can also be utilised Diagrams (including updates) can be exchanged along with network data using the same serialisation format 6 pen Grid Systems

7 Diagram Layout Profile The Diagram Layout Profile becomes another profile linked into the network profiles Profiles Profiles Analog Measurement Profile Discrete Measurement Profile State Variables Profile Topology Profile For instance data each profile is a separate dataset (e.g. file) with dependencies Profile Profile Diagram Layout Profile Equipment Model Profile 7 pen Grid Systems

8 Multiple Uses The Diagram Layout profile can be used in a number of existing exchanges Any existing network data exchange for planning or operations can include single-line diagram layout data This includes internal substation schematics and network overviews Pseudo-geographical views can be generated from geographical data but maintained separately from the pure Geographical positions CIM for Dynamics can represent dynamic block models graphically using CIM Diagram Layout 8 pen Grid Systems

9 Modular Profiles Planning perational (EMS) Distribution Equipment Equipment Equipment Equipment Topology Topology Measuremen Measurement State State Geographical Measuremen Diagram Geographica 9 pen Grid Systems

10 Modular Profiles Planning perational (EMS) Distribution Equipment Equipment Equipment Equipment Topology Topology Measuremen Measurement State State Diagram Geographical Measuremen Diagram Diagram Geographica 9 pen Grid Systems

11 Diagram Layout UML 10 G pen Grid Systems

12 Diagram Layout UML Core::Identifiedbject + mrid: String + name: String DiagrambjectStyle DiagrambjectStyle VisibilityLayer + drawingrder: Integer + VisibilityLayers 0..* Identifiedbject Diagram + orientation: rientationkind + x1initialview: Float + x2initialview: Float + y1initialview: Float + y2initialview: Float DiagrambjectPoint + sequencenumber: Integer + xposition: Float + yposition: Float + zposition: Float + DiagrambjectPoints 2..* + DiagrambjectGluePoint Diagrambjects 0..* + Visibilebjects + DiagramElements 0..* 0..* + Styledbjects 0..* Diagrambject + DiagrambjectPoints 0..* + Diagrambject 1 + drawingrder: Integer + ispolygon: Boolean + offsetx: Float + offsety: Float + rotation: AngleDegrees Diagram <<enumeration>> rientationkind positive negative DiagrambjectGluePoint TextDiagrambject + text: String 11 pen Grid Systems

13 Diagram bjects The basic construct is a Diagrambject that has 1 or more DiagrambjectPoints DiagrambjectPoint + sequencenumber: Integer + xposition: Float + yposition: Float + zposition: Float + DiagrambjectPoints 0..* + Diagrambject 1 Diagrambject + drawingrder: Integer + ispolygon: Boolean + offsetx: Float + offsety: Float + rotation: AngleDegrees 12 pen Grid Systems

14 Link to the Domain Domain data is anything that inherits from Identifiedbject This can be: Electrical components (breakers, line segments) Containment objects (substations, bays) Measurements from SCADA points Dynamic modelling blocks Core::Identifiedbject + mrid: String + name: String Identifiedbject + Diagrambjects 0..* DiagrambjectPoint + sequencenumber: Integer + xposition: Float + yposition: Float + zposition: Float 13 + DiagrambjectPoints 0..* + Diagrambject 1 Diagrambject + drawingrder: Integer + ispolygon: Boolean + offsetx: Float + offsety: Float + rotation: AngleDegrees pen Grid Systems

15 Diagrams Core::Identifiedbject + mrid: String + name: String A Diagram contains multiple Diagrambjects An Identifiedbject can have multiple Diagrambjects in multiple Diagrams Identifiedbject + Diagrambjects 0..* + DiagramElements 0..* + orientation: rientationkind + x1initialview: Float + x2initialview: Float + y1initialview: Float + y2initialview: Float Diagram Diagram <<enumeration>> rientationkind DiagrambjectPoint + sequencenumber: Integer + xposition: Float + yposition: Float + zposition: Float + DiagrambjectPoints 0..* + Diagrambject 1 Diagrambject + drawingrder: Integer + ispolygon: Boolean + offsetx: Float + offsety: Float + rotation: AngleDegrees 14 positive negative pen Grid Systems

16 Core::Identifiedbject + mrid: String + name: String DiagrambjectStyle DiagrambjectStyle VisibilityLayer + drawingrder: Integer + VisibilityLayers 0..* Identifiedbject Diagram + orientation: rientationkind + x1initialview: Float + x2initialview: Float + y1initialview: Float + y2initialview: Float DiagrambjectPoint + sequencenumber: Integer + xposition: Float + yposition: Float + zposition: Float + Diagrambjects 0..* + Visibilebjects + DiagramElements 0..* 0..* + Styledbjects 0..* Diagrambject + DiagrambjectPoints 0..* + Diagrambject 1 + drawingrder: Integer + ispolygon: Boolean + offsetx: Float + offsety: Float + rotation: AngleDegrees Diagram <<enumeration>> rientationkind positive negative + DiagrambjectPoints 2..* + DiagrambjectGluePoint 0..1 DiagrambjectGluePoint TextDiagrambject + text: String 15 pen Grid Systems

17 Diagram Layout Example Integrating diagram layout and electrical model data 16 G pen Grid Systems

18 17 CIM Diagram Layout Example BusbarSection SynchronousMachine Breaker Power Transformer ACLineSegment Breaker pen Grid Systems

19 BusbarSection x Breaker Diagrambject Power Transformer DiagrambjectPoint SynchronousMachine Breaker ACLineSegment y 19 pen Grid Systems

20 BusbarSection x Breaker Diagrambject Power Transformer DiagrambjectPoint SynchronousMachine Breaker ACLineSegment y 19 pen Grid Systems

21 BusbarSection x Breaker Diagrambject Power Transformer DiagrambjectPoint SynchronousMachine Breaker ACLineSegment y 19 pen Grid Systems

22 BusbarSection x Breaker Diagrambject y SynchronousMachine Power Transformer Breaker DiagrambjectPoint <cim:breaker rdf:id="_b001"> <cim:identifiedbject.name>breaker</cim:identifiedbject.name> </cim:breaker>! <cim:diagrambject rdf:id="_d001"> <cim:diagrambject.identifiedbject rdf:resource="#_b001"/> </cim:diagrambject>! ACLineSegment <cim:diagrambjectpoint rdf:id="_p001"> <cim:diagrambjectpoint.xposition>583</cim:diagrambjectpoint.xposition> <cim:diagrambjectpoint.yposition>493</cim:diagrambject.yposition> <cim:diagrambjectpoint.diagrambject rdf:resource="#_d001"/> </cim:diagrambjectpoint> 19 pen Grid Systems

23 y BusbarSection <cim:busbarsection rdf:id="_bb001"> <cim:identifiedbject.name>busbarsection</cim:identifiedbject.name> </cim:busbarsection>! <cim:diagrambject rdf:id="_d002"> <cim:diagrambject.identifiedbject rdf:resource="#_bb001"/> Breaker </cim:diagrambject>! <cim:diagrambjectpoint rdf:id="_p002"> <cim:diagrambjectpoint.xposition>164</cim:diagrambjectpoint.xposition> <cim:diagrambjectpoint.yposition>79</cim:diagrambject.yposition> <cim:diagrambjectpoint.sequencenumber>1</cim:diagrambject.sequencenumber> Power Transformer <cim:diagrambjectpoint.diagrambject rdf:resource="#_d002"/> </cim:diagrambjectpoint>! <cim:diagrambjectpoint rdf:id="_p003"> <cim:diagrambjectpoint.xposition>485</cim:diagrambjectpoint.xposition> <cim:diagrambjectpoint.yposition>79</cim:diagrambject.yposition> <cim:diagrambjectpoint.sequencenumber>2</cim:diagrambject.sequencenumber> <cim:diagrambjectpoint.diagrambject rdf:resource="#_d002"/> </cim:diagrambjectpoint> SynchronousMachine 20 Breaker DiagrambjectPoint Diagrambject! <cim:diagrambjectpoint rdf:id="_p004"> <cim:diagrambjectpoint.xposition>775</cim:diagrambjectpoint.xposition> <cim:diagrambjectpoint.yposition>79</cim:diagrambject.yposition> <cim:diagrambjectpoint.sequencenumber>3</cim:diagrambject.sequencenumber> <cim:diagrambjectpoint.diagrambject rdf:resource="#_d002"/> </cim:diagrambjectpoint> ACLineSegment pen Grid Systems x

24 BusbarSection x Terminal Breaker Power Transformer SynchronousMachine Terminal Breaker ACLineSegment y 21 pen Grid Systems

25 y BusbarSection <cim:breaker rdf:id="_b001"> <cim:identifiedbject.name>breaker</cim:identifiedbject.name> </cim:breaker>! <cim:terminal rdf:id="_t001"> <cim:identifiedbject.name>terminal</cim:identifiedbject.name> SynchronousMachine Terminal 21 Breaker <cim:terminal.conductingequipment rdf:resource="#_b001"/> </cim:busbarsection>! <cim:diagrambject rdf:id="_d003"> <cim:diagrambject.identifiedbject rdf:resource="#_t001"/> Power Transformer </cim:diagrambject>! <cim:diagrambjectpoint rdf:id="_p005"> <cim:diagrambjectpoint.xposition>494</cim:diagrambjectpoint.xposition> Breaker Terminal <cim:diagrambjectpoint.yposition>507</cim:diagrambject.yposition> <cim:diagrambjectpoint.sequencenumber>1</cim:diagrambject.sequencenumber> <cim:diagrambjectpoint.diagrambject rdf:resource="#_d003"/> </cim:diagrambjectpoint>! <cim:diagrambjectpoint rdf:id="_p006"> ACLineSegment <cim:diagrambjectpoint.xposition>590</cim:diagrambjectpoint.xposition> <cim:diagrambjectpoint.yposition>507</cim:diagrambject.yposition> <cim:diagrambjectpoint.sequencenumber>2</cim:diagrambject.sequencenumber> <cim:diagrambjectpoint.diagrambject rdf:resource="#_d003"/> </cim:diagrambjectpoint> pen Grid Systems x

26 Defining Graphical Styles 23 G pen Grid Systems

27 Styling bjects The Diagram Layout Profile does not seek to define how graphics are rendered, just the layout The DiagrambjectStyle class is to allow exchanging parties to agree a set of style references that they can use to interpret the incoming data But since the Diagrambjects are tied to a domain object, the receiver can base their rendering on the known state of the domain object 24 pen Grid Systems

28 Multiple Diagrambjects Styles are useful if you have multiple Diagrambjects for one Domain bject LANG PriTrA Here we have a single PowerTransformer which may have 4 Diagram bjects Appropriate Style IDs against each let senders/receivers coordinate what is to be shown for each Style IDs PrimaryWindingColoured 25 pen Grid Systems

29 Multiple Diagrambjects Styles are useful if you have multiple Diagrambjects for one Domain bject LANG PriTrA Here we have a single PowerTransformer which may have 4 Diagram bjects Appropriate Style IDs against each let senders/receivers coordinate what is to be shown for each Style IDs PrimaryWindingColoured SecondaryWindingColoured 25 pen Grid Systems

30 Multiple Diagrambjects Styles are useful if you have multiple Diagrambjects for one Domain bject LANG PriTrA Here we have a single PowerTransformer which may have 4 Diagram bjects Appropriate Style IDs against each let senders/receivers coordinate what is to be shown for each Style IDs PrimaryWindingColoured SecondaryWindingColoured TransformerLocalName 25 pen Grid Systems

31 Multiple Diagrambjects Styles are useful if you have multiple Diagrambjects for one Domain bject LANG PriTrA Here we have a single PowerTransformer which may have 4 Diagram bjects Appropriate Style IDs against each let senders/receivers coordinate what is to be shown for each 25 Style IDs PrimaryWindingColoured SecondaryWindingColoured TransformerLocalName TransformerTapChangerType pen Grid Systems

32 Multiple Diagrambjects Styles are useful if you have multiple Diagrambjects for one Domain bject LANG PriTrA Here we have a single PowerTransformer which may have 4 Diagram bjects Appropriate Style IDs against each let senders/receivers coordinate what is to be shown for each 25 Style IDs PrimaryWindingColoured SecondaryWindingColoured TransformerLocalName TransformerTapChangerType pen Grid Systems

33 Summary 26 G pen Grid Systems

34 Summary The CIM Diagram Layout is not about exchanging diagrams as graphics, it is about layout Systems can use their own icons, styles, colours etc. but the layout and placement of the components is the same Using the CIM to describe this data allows it to be easily integrated with the network data and utilise existing interfaces and serialisation formats The standard is flexible and can be used for different types of diagrams: e.g. single-line, geovisual and dynamic block models 27 pen Grid Systems

35 Questions?