Introduction to Grid SVG

Directory
1. Range 1
2. Normative Reference Document 1
3. Abbreviations 1
4. Features of the graphics exchange involved in this standard 1
5. Interactive formats and processes 2
6. Metadata Model 2
7. svg File Description 4
7.1 Basic File Structure 4
7.2 File Header 4
7.3 form of Expression 5
7.3.1 Entity 5
7.3.2 Style 7
7.4 References to Entities and styles 8
7.4.1 References to Primitives 8
7.4.2 Coordinate Transformation 8
7.4.3-style References 8
7.5 Graphics ID Description 9
7.6 association with domain data 9
7.7 Power System Components 9
7.7.1 Circuit Breaker (CBR) 9
7.7.2 Gate and Grounding Gate (DIS) 10
7.7.3 Generator (GEN) 10
7.7.4 Transformer (PTR) 10
7.7.5 Busbar (BAR) 11
7.7.6 Load (IFL) 11
7.7.7 AC Line (LIN) 11
7.7.8 shunt reactance (REA) 12
7.7.9 shunt Capacitor (CAP) 12
7.7.10 Converter (CON) 12
7.7.11 DC Line (GIL) 12
7.7.12 Voltage Transformer (VTR) 13
7.7.13 current transformer (CTR) 13
7.7.14 transformer Winding (PTW) 13
7.7.15 Tap (LTC) 13
7.7.16 Motor (MOT) 14
7.7.17 Arc Suppression Coil (EFN) 14
7.7.18 Power Shunt (PSH) 14
7.7.19 Auxiliary Network (AXN) 14
7.7.20 Battery (BAT) 15
7.7.21 Casing (BSH) 15
7.7.22 Power Cable (CAB) 15
7.7.23 Rotating Reactive components (RRC) 15
7.7.24 surge arrester (SAR) 15
7.7.25 Frequency Converter (TCF) 16
7.7.26 controlled reactive element (TCR) 16
7.8 Connecting Cable 16
7.9 Real-time data 17
7.10 Note Text 17
7.11 Bottom Diagram 17
7.12 Layer 17
7.12.1 graphic static background layer (Head_layer) 17
7.12.2 Power Equipment Component Layer 17
7.12.3 static text layer (Text_layer) 18
7.12.4 measurement Layer (Data _layer) 18
7.12.5 Connection Relationship layer (Connectivitynode _layer) 18
7.12.6 other layers (Other_layer) 18
7.12.7 hotspot Layer (ref_layer) 18
8. Characterization of topologies 18
8.1 Pre-condition 18
8.2 Connection Description 18
8.3 Connection Relationship Example 19
9. Organization of Graphic Objects 21
9.1 Types of organization 21
Appendix A entity naming 24
Appendix B color and font naming (common) 26

1. Scope
This standard specifies the graph interaction rules between the system diagram and the primary wiring diagram of the SAS system based on SVG, and the graphical interactive rules of the SAS system and other application systems such as the EMS system. The aim is to realize the graphic exchange between different systems, different manufacturers and different power enterprises. This standard mainly consider the plant station single-line diagram, collectively referred to as SVG single-line diagram. This standard does not specify the specific implementation measures or products, nor does it stipulate the method and interface of the whole realization in the computer system.
Graphical interaction must be closely linked to the existing 61850 standard and SCL data interaction format, because graphical interactions are closely related to these data structures and interaction standards. The set of symbols used will be limited to the range of device classes that have been defined in the SCL.
2. Normative reference Documents
The articles in the following documents are the terms of this section by reference to this section of GB/T1. All subsequent revisions (excluding errata) or revisions of the quoted documents, which are dated, do not apply to this section, however, it is encouraged to study the availability of the latest versions of these documents in all aspects of the agreement reached under this section. The latest version of the quoted document, which does not note the date, applies to this section.
GB/T 4728 Power Engineering drafting standard
ISO10646 Universal multiple-octet Coded Character Set Information technology general purpose multi eight-bit coded character set
DLT 860.6-2008 substation Communication networks and Systems part 6th: Communication Configuration Description Language in substations related to intelligent electronic devices
DLT 860.7-1 substation Communication networks and Systems Section 7-1_: Basic communication structure of substation and feeder equipment _ principle and model
DLT 860.7-2 substation Communication networks and Systems Section 7-2_: Basic communication structure of substation and feeder equipment _ Abstract Communication Service Interface (ACSI)
DLT 860.7-3 substation Communication networks and Systems Section 7-3_: Basic communication structure for substation and feeder equipment _ Common data classes
DLT 860.7-4-2006 substation communication networks and Systems 第7-4部: Basic communication structure of substation and feeder equipment compatible with logical node classes and data classes
SVG 1.1 specification, http://www.w3.org/TR/2003/REC-SVG11-20030114/
3. Abbreviations
The following abbreviations apply to this standard.
SCL Substation Configuration Description Language substation configuration Description Language
GIS Geographic Information System
XML Extensible Markup Language
SVG Scalable Vector Graphics
EMS Energy Management System
SAS Substation Automation System
CSS Cascading Style Sheets
CCAPI Control Center Application programming Interface
4. Graphic Exchange features covered by this standard
This standard specifies that the graphic object Interchange format needs to have the following characteristics:
The basic methods for connecting graphical objects and domain data are described in detail. Domain data and graphical objects are described separately.
The method of mapping graphical object representation rules in different systems is described in detail.
Supports the exchange of graphical objects that have no relation to domain data, such as purely static background objects.
The exchange of complex objects only supports hotspot connections, commands and menus are not supported, and curves and bar graphs are not supported.
Support for drawing objects to be distributed by layer or by other means, to show or hide some information based on the zoom level and/or the user's attention angle.
This standard takes into account the existing old system export convenience, so when the system is exported, you can select one of the scenarios to achieve, but for the importer, you need to support all the scenarios in this standard.
5. Interactive formats and processes
Depending on the starting point of the application, CCAPI presents two methods for graphical interaction:
Graphics Center: The use of SVG to establish a separate common graphics model, in the graphics Exchange, the SVG file with graphics information and the CIM file with the model information can be exported separately, and then the graphics system involved in the object set up with its CIM association relationship.
Domain Center: Adding graphical properties to an existing CIM object is an extension of the CIM method, and when the information is exchanged, the imported exported CIM object is expanded and its graphic properties are also included.
In a graph-centric interaction, visualization is a loosely coupled relationship with data storage, and it is easy to support the diversity of each object representation, easy to support background data in charts, easy to integrate graphics into diagrams, and easy to use SVG browsers. This approach is primarily for SAS systems.
In a domain-centric interaction, the SCL contains both dynamic and static parameter attributes, along with graphical properties, which facilitates the integration of GIS (geographic information systems). However, the domain center method needs to extend the SCL, which causes the changes in the graphical interaction to affect the corresponding SCL definition changes, and extensibility is poor.
According to the recommendation of Ccapi, the interactive mode of graphic center should be used in dispatching automation system. The flow of graphics interop is as shown in the following:



6. Metadata Model
Metadata is a kind of data describing data, mainly used to describe some properties of data, to indicate the location of data storage, query methods and other information. The SVG specification provides attributes that the <metadata> element uses to describe other SVG elements.
<g id= "566" >
<use width= "stroke-dasharray=" "x=" -10.5 "xlink:href=" #Breaker: [email protected] "y=" 0 "class=" v110kv "height=" 37.5 "transform=" translate ( -287.5,-9.25) "stroke-width=" 1 "/>
<metadata>
<cgeev_ref objectid= "_4cd1261e00c702c6" objectname= "161 switch"/>
<cgeatas_ref objectid= "_4CD1261E00D702C9" objectname= "status"/>
</metadata>
</g>
The code above gives an example of associating an SVG graphical object with the CIM model with the <metadata> element. which
The <use> element describes a specific graphical object that renders a break in the diagram by referencing the "breaker" primitive reference.
The,<metadata> element is a sub-element of the <use> element that describes the Id of the CIM object corresponding to the graphic object,
This Id can be used to associate a drawing object with a CIM object. Because the <metadata> element supports any XML-compatible metadata
Syntax, you can describe an SVG graphic object in the format you want by specifying a namespace, rather than using only graphic objects
The method associated with the Id is more flexible.
Figure 6-1 shows the metadata data model and references to the substation, Voltage level, Bay, tranformer, equipment, and data classes in the IEC 61850 SCL model. Figure 6-2 shows the properties of the Cge:metadata. Table 6-1 Describes how these properties are used in different use cases.

Figure 6-1: Metadata model and references to the class in the IEC 61850 SCL model

Figure 6-2: Properties of the Cge:metadata
Property Description for Table 6-1:metadata
Interchange type or reference case metadata element metadata property
ObjectID ObjectName ClassName
Power Equipment Dev_ref
Datas_ref required (compliant with-6 standard) must be optional
Only show measurement data datas_ref required (compliant with-6) optional N/A
Layer Layer_ref optional Layer number optional layer name N/A
Connection cable with connection point Cn_ref Optional N/A
Device with connection point Cn_ref Optional N/A
7. svg file description
7.1 Basic File structure

7.2 File Header
<?xml version= "1.0" standalone= "no" encoding= "UTF-8"?>
<! DOCTYPE svg public "-//W3C//DTD svg 1.1//en"
Http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd >
< svg width= "1024x768" height= "768" graname= "xx substation" viewbox= "0 0 2000 1000"
Xmlns= "Http://www.w3.org/2000/svg"
xmlns:xlink= "Http://www.w3.org/1999/xlink" xmlns:cge= "http://iec.ch/TC57/2005/SVG-schema#" >

There are several main parameters to note in the header file:
? XML version: Refers to the XML versions that are used, because SVG graphics are XML-based applications, so an SVG document must also contain XML declarations and root elements. The version currently in use is 1.0.
? Character encoding using UTF-8
? DOCTYPE to indicate the SVG and SVG versions.

The root element of SVG mainly describes the width and height of the entire graph and its namespace information, width and height describe the width and height of the canvas, Graname Plant Station description information, Viewbox can translate and convert the local coordinate system. The main name space has the:<svg> element in the Http://www.w3.org/2000/svg namespace, which is the default namespace. There are two other spaces, xmlns:xlink= "Http://www.w3.org/1999/xlink", xmlns:cge= "http://iec.ch/TC57/2005/SVG-schema#"
7.3 Presentation Forms
The transmitting party needs to express the form of expression, and the importer need not and how to dispose of these forms can be considered separately. The expression forms are mainly in the defs
<defs>
(all symbols is defined here)
</defs>
7.3.1 Elements
An entity is a description of how different power system objects are displayed in a diagram.
In an SVG document, you can copy shapes, paths, or groupings to multiple different locations in a document by referencing an element that is defined elsewhere in the document by using the <use> element. Typically, the referenced element is placed inside a <defs> element until a <use> element refers to the element to draw the graphic. The <defs> element is used only to define the referenced elements, not to actually draw and render the elements.
The graphical entities are converted to <symbol> elements in SVG to define the template for the image. The defined template can only be referenced by an instance of the <use> element for actual rendering.
Entity definition:
The unique identity ID of an entity is represented by the "primitive Type: Entity Name" method. The entity type is the class name in the 61850 model that corresponds to the device. The entity names in the same primitive type are not duplicated.
In each symbol definition, the drawing area is the fourth quadrant of the right-handed coordinate system. The upper-left point coordinates are (0,0), the right side is the X-increment direction, and the lower y-direction.
To give the actual size Viewbox (x,y,width, height) that represents the element after reduction.
A reference terminal is used to represent the position of the element terminal, according to the value of the Terminal_seq label, numbered 0,1,2.
For multi-State entities, there are two ways to represent
Method 1: Identity ID takes "primitive type: Entity name @ Entity State, divided into multiple entity description, the entity name should be named suitable for sub-type, such as trolley knife, round knife and so on. For open and close two states of the entity, with @o expression Open, @c expression, for the car switch and other complex elements, can be used @[email protected] (switch on, the gate Open), @[email protected] (switch on, knife brake), @[email Protected] (switch, gate Open), @[email protected] (switching reactive power measurement FMEASQ

Introduction to Grid SVG