An XML Based Data Exchange Model for Power System Studies

ARI The Bulletin of the Istanbul Technical University VOLUME 54, NUMBER 2 Communicated by Sondan Durukanoğlu Feyiz An XML Based Data Exchange Model for Power System Studies Hasan Dağ Department of Electrical Engineering, Istanbul Technical University, 34469 Maslak, Istanbul, Turkey Umut Utkan Department of Computational Science and Engineering, Institute of Informatics, Istanbul Technical University, 34469 Maslak, Istanbul, Turkey (Received 09 April 2004) Data exchange is very important in electrical and electronics engineering applications. The exchange needs to be reliable, error-free and adaptable to different types of software used in the related industries. In power community, IEEE common format, WSCC format, and PTI s PCI format have been used extensibly to date with almost no problem for data exchange purposes. As the industry goes under big changes, such as deregulation and use of power electronics more and more, aforementioned formats are not adequate. In this paper we present a model for exchanging power system data using extensibly Markup Language (XML) as the exchange base. The developed software can accept IEEE common format data as input and convert it to any other forms of data formats desired such as WSCC, PTI, HTML, or even to another form of XML. Keywords: XML, data exchange, power systems. 1. Introduction Data exchange is a major necessity in engineering world because any data can be output of a process while being input for another. For the reliability the data exchange must have a protocol that makes the transferred data meaningful for the other processes. Defining a protocol for data exchange for a specific area is a difficult and time consuming task due to the expectation of being a standard for every relevant study and software developments. Data exchange is also a major problem and a new value in power industry with the open access. New participants join the market as generation companies, transmission companies, and distributors. Because of the physical connectivity property of power systems, all levels of industry like generation, transmission, distribution and market need proper operational and equipmental data. As expected, the data to be shared is huge and this requires an efficient and reliable data exchange method. The data exchange model should be expandable and should not exclude any other technologies used or will be used in the future. It must also be software and hardware independent for fully integration with all environments and industries. This paper suggests a data exchange method and conversion from or to the related protocols, especially the IEEE Common Format [1]. The suggested method is currently at introductory level and is open for development. Its format is based on XML (Extensible Markup Language) [2]. In the following sections we present a brief history on data exchange in power systems, then we provide some general information on XML and its related technologies. Then we present the suggested data exchange model. We conclude with some examples and related future research directions on the topic. 1.1. A Brief History of Power System Data Exchange For a variety of reasons, such as simulation needs for proper operation of power systems, realtime monitoring, maintenance planning, transmission planning and operation standardization of power systems, data exchange is important for power systems. Real-time monitoring needs big amount of data to be transferred for processing, like equipment types, grid connections, layout information etc. While the data exchange is a big problem, non-reliable data and/or data loss are not acceptable for power system operation at all. To this end several formats were offered in the past for exchanging power system data either proprietary or not, all having some advantages and disadvantages. The first and the most widely used format is the IEEE Common Format implemented in 1968 by an IEEE working group [1]. IEEE Common Format is used for transferring solved load flow data and is a textual, column-wise representation of grid data. During 1980s firstly PTI format was appeared; a proprietary format developed by Power Technologies, Inc., for using data with the software developed by the same company. PTI is similar to IEEE Common For-

An XML Based Data Exchange Model for Power System Studies 1 1 1 1 0 1.0284 5.9500 90.00 49.00 0.000 0.000 115.00 0.000 0.0000 0.0000 0.0000 0.0000 0 2 1 1 1 0 1.0354 7.7400 56.00 15.00 0.000 0.000 115.00 0.000 0.0000 0.0000 0.0000 0.0000 0 3 1 1 1 0 0.9971 6.6400 20.00 0.000 0.000 0.000 230.00 0.000 0.0000 0.0000 0.0000 0.0000 0 ------------------------------------------------------------------------------------------ <?xml version="1.0" encoding="utf-8"?> <!--XML file generated by CF2XML converter (http://dexchange.fbe.itu.edu.tr)--> <NETWORK xmlns:xsi="http://www.w3.org/2001/xmlschema-instance" xsi:nonamespaceschemalocation="cf.xsd"> <TITLE> <MVA_BASE>100.0</MVA_BASE> <CASE_IDENTIFICATION>16 BUS AC SYSTEM</CASE_IDENTIFICATION> </TITLE> <BUS id="1" type="3" area_number="0" loss_zone_number="1" remote_bus_number="0"> <NAME>BUS_1 18.0</NAME> <FINAL> <VOLTAGE>1.0</VOLTAGE> <ANGLE>0.0</ANGLE> </FINAL> <LOAD> <MW>0.0</MW> <MVAR>0.0</MVAR> </LOAD> <GENERATION> <MW>0.0</MW> <MVAR>0.0</MVAR> </GENERATION> <BASE_kV>18.0</BASE_kV> <DESIRED_VOLTS>1.0</DESIRED_VOLTS> <LIMITS unit= MVAR > <MAX>-99999.0</MAX> <MIN>999999.0</MIN> </LIMITS> <CONDUCTANCE>0.0</CONDUCTANCE> <SUSCEPTANCE>0.0</SUSCEPTANCE> </BUS> Figure 1. A portion of a Common Format Data (upper part) and the corresponding XML representation (lower part) mat except it includes the DC links. After PTI, The Western System Coordinating Council (WSCC) also developed its own format. These three formats are the most frequently used power system data exchange formats. Whenever a more general necessity occurred another extended version of power system data exchange method is developed. When these methods were proposed, mostly the interzonal exchange of data was needed. With the deregulation of the power industry there is now a greater need for data exchange. The exchanges are now between companies and between the interconnected networks, extending to countries. As a result, a more standardized and extensible format of data exchange is needed due to the international-wide differences in power industry standards and data manipulating techniques used. The only unchanged fact is the data and it s usage. A method that answers all deficiencies of the aforementioned methods is the best solution for the problem. 1.2. IEEE Common Format Data as a Base for the Suggested Method IEEE Common Format was implemented by IEEE in 1968 and is the basic framework for power system data exchange. We offer a data exchange model using the strength of XML while chosing the IEEE Common Format due to its simplicity of implementation. Certainly IEEE Common Format is not competent for power system data exchange. IEEE Common Format is a column-wise representation of solved power flow data. Lines are separated by section headers such as bus data, branch data etc. Columns represent load flow data, loss zones, bus and branch types, and transformer settings. All elements have to be presented between exact column numbers with exact lengths. It is not easy to read at the first glance because values are not labeled and it requires a knowledge about the format. Furthermore, reading it programmatically requires several string manipulations such as splitting and concatenation, etc. 27

Hasan Dağ and Umut Utkan <xs:element name="load"> <xs:complextype> <xs:sequence> <xs:element name="mw" type="xs:float"/> <xs:element name="mvar" type="xs:float"/> </xs:sequence> </xs:complextype> </xs:element> <xs:element name="generation"> <xs:complextype> <xs:sequence> <xs:element name="mw" type="xs:float"/> <xs:element name="mvar" type="xs:float"/> </xs:sequence> </xs:complextype> </xs:element> <xs:element name="base_kv" type="xs:float" minoccurs="0"/> <xs:element name="desired_volts" type="xs:float" minoccurs="0"/> <xs:element name="limits" minoccurs="0"> Figure 2. A portion of an XSD document used for validation Using IEEE common format as a data exchange format thus has some disadvantages that make the exchange out of standard. Replacement of this standard with a newer, extensible and programmingenvironment-independent will make the process more efficient. 2. XML extensible Markup Language (XML) [2] is a markup language defined by World Wide Web Consortium (W3C) (http://www.w3c.org) and standardized by a W3C recommendation. It is a very popular format for structured, semi-structured and unstructured data exchange over Internet and private networks. XML is a simple and flexible text format derived from Standard Generalized Markup Language (SGML) and generic type of its antecedent Hyper Text Markup Language (HTML). Unlike a few predefined HTML tags, a user can create and use his/her own tags in XML according to his/her own like. An XML document is similar to HTML document in terms of appearance. However, the former has strict rules whereas the later does not in terms of syntax. Fig. 1 shows both a portion of a common format data and the corresponding XML representation of the same data. As apparent from the figure, an XML document provides more information than a common format document. The first line in the XML document begins with a processing instruction - the XML declaration defining the XML version and the character encoding used in the document. NETWORK is the root element and the others defined under the NETWORK element are the child elements of NET- WORK. id, type, area number, loss zone number, and remote bus number are the attributes of the element BUS. As can be seen from the figure, the form of XML is very simple, it consists of elements and element attributes. Every element has an opening tag <foo> and ending tag </foo>. An element that does not require an ending tag is called empty tag. 2.1. Syntax XML syntax rules require that all tags be properly nested. Thus, the first usage below <bus><name> BUS 1 180 </bus></name> is invalid. The correct form of this representation is <bus><name> BUS 1 180 </name></bus> All XML documents must have a root element. For example, the the root element in Fig. 1 is the NETWORK. Unlike HTML, all opening tags must be closed in XML. If these rules are followed XML document is said to be well-formed. Unlike HTML, XML is case sensitive, hence the tag <Bus> is different from the tag <bus> and the closing tags must therefore be written in the same case. The attribute values must be quoted in XML. Another difference between the HTML syntax and that of XML is that whitespaces are generally preserved not collapsed into a single whitespace. The syntax for writing a comment is similar to that of HTML. <! This is a comment > Usually a dictionary, a text file that describes the allowable content of the elements, attribute type, occurrence frequency of an element, etc. accompanies an XML file. This dictionary is called document type definition or Schema depending on the usage explained below. 28

An XML Based Data Exchange Model for Power System Studies <?xml version="1.0" encoding="utf-8"?> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/xsl/transform" xmlns:xs="http://www.w3.org/2001/xmlschema"> <xsl:template match="/"> <html> <body> <table border="1"> <thead> <tr> <td>id</td> <td>type</td> <td>name</td> <td>base_kv</td> <td>d_voltage</td> </tr> </thead> <tbody> <xsl:for-each select="network/bus[5>=position()]"> <tr> <td><xsl:value-of select="@id"/></td> <td><xsl:value-of select="@type"/></td> <td><xsl:value-of select="name"/></td> <td><xsl:value-of select="base_kv"/></td> <td><xsl:value-of select="desired_volts"/></td> </tr> </xsl:for-each> </tbody> </table> </body> </html> </xsl:template> </xsl:stylesheet> Figure 3. Sample XSL document 2.2. Validation In most applications it is essential to create an exact definition of the syntax; elements, their attributes, and the occurrence frequencies of the elements within a document. This can be done in XML using Document Type Definitions (DTD) [3] or XML Schema Document (XSD) [4]. XSD is an XML based alternative to DTD, which has a different way of defining elements. Both them specify the syntax of the XML document. If an XML document conforms to the accompanying DTD or XSD file it is said to be valid. Fig. 2 shows a portion of an XSD document used to validate the XML document given in Fig. 1 (below part). Fig. 2 establishes mandatory, the hierarchy of the document, order of elements, and occurrence frequencies of elements etc. Using a DTD or XSD before processing the associated XML document maintains the exact data reliability for applications. Programmer does not need to spend time for data reliability controls. XML processor does all the work for the programmer. 2.3. Viewing XML document also have some extra capabilities because of being a standard for the future s web. All browsers have XML libraries for manipulation. XML Table 1 Output produced by the XSL document. id type Name Base kv Voltage 1 3 BUS 1 18.0 18 1.0 2 0 BUS 2 230.0 230 1.0 3 2 BUS 3 138.0 138 1.0 4 0 BUS 4 230.0 230 1.0 5 0 BUS 5 125.0 125 1.0 documents do not have to be seen in the form they are created. With the help of the XML Stylesheet Language (XSL) [5] one can convert his/her own XML document to any other form such as html, pdf, postscript, even to XML. XSL is a standard recommended by the World Wide Web Consortium. XSL can output the XML document as HTML and is supported by all current web browsers. The process is quite easy, one uses defined tags of XSL to reach the nodes (elements) in XML documents and print them into the classic HTML documents as tables, images, links, etc. The XML data can be embedded wherever desired in HTML. The result of applying Fig. 3 to the XML document in Fig. 1 is shown in Table 1. 29

Hasan Dağ and Umut Utkan Figure 4. A pictorial overview of the suggested model 3. Suggested Data Exchange Model Fig. 4 gives a pictorial overview of the proposed data exchange model. To realize this model a Java API is developed. API has capability of transforming IEEE Common Format Data to XML and XML document to Common Format Data. It is only a programming effort to support other formats such as WSCC format or PTI format. Inclusion of FACTS data is also easy since each element can easily be defined and added to the model. Currently, only Common Format Data is supported because the proposed model is an introduction to XML based data exchange model for power systems. Whenever a standardized power system data model developed as XML (especially the type definitions either XSD or DTD), other formats can be added easily. Here we want to show that XML has big advantages over other exchange formats. XML data produced by the developed converter program is validated using the accompanying XSD document (or DTD document) and is viewed as HTML. The developed programs and their usage can be viewed at http://dexchange.fbe.itu.edu.tr/pwmodel. The XML document created can be edited online by the use of DOM class developed. As can be seen from Fig. 4 viewing and editing of XML documents is easier than viewing and editing other forms of data such as Common Format, WSCC and PTI formats. Produced output can be directly processed by other applications or can be transformed to the other structural representations again as XML by the use of extensible Stylesheet Transformation (XSLT) [5] language. XML transformations are the most important parts of XML data exchange. Transformation makes XML data exchange more valuable. The same data can be used in other areas with little programming effort, all work is done with XSLT. For example the suggested model gets the XML document produced from the related Common Format Data and transforms into a form that YFiles can process to produce graph of the power grid in GraphML [6] format. The developed Java API consists of six base classes to transform Common Format to XML or vica versa. readcf: reads whole Common Format Data document and checks the validity of Common Format document. titledata: stores all title values of the given Common Format document and has methods for writing the title data as XML or as Common Format. busdata: stores all bus values and has methods for writing the bus data as XML or as Common Format. branchdata: stores all branch values and has methods for writing the branch data as XML or as Common Format. networkdata: stores all network data as title data and arrays of bus and branch objects and 30

An XML Based Data Exchange Model for Power System Studies Figure 5. Orthogonal layout of a sample power grid generated using evaluation version of YFiles developed by YWorks (http://www.yworks.de) has methods for writing the whole document as XML or as Common Format. readcf invokes the methods of networkdata to store the data as read from the Common Format Document. xmlparser: controls the validity of the XML document against the accompanying XSD (or DTD) document and reads the whole document into networkdata object. All code will be opened to public access and will be available for download when the development is matured. The developed program is only an introductory model to the proposed framework for the power system data exchange. The most important advantage of XML is that it is self-described in a way that the data (element of XML) mean both the data and the label. Simply, when you transfer data you also get the description of it. The only need then is an XML processor and a DTD or XSD. The processors checks whether the document is well-formed or not. The proposed model have all the requirements expressed in [7]. It is self-defined, expandable, restrictable and secure. It also gets the power of XML behind such as the full web integration and strong support provided by various programming languages. XML based power system data can be easily integrated with the existing technology standards for the same purpose like CIM, which is an acronym for common information model used for power system control. CIM and XML integration is discussed in [8]. 3.1. Tools Used For this paper a sample XML Schema is formed for power system data based on the elements and relationships used in IEEE Common Format. A Java API (application programming interface) is developed for transformation of IEEE Common Format Data to XML. Conversion from XML to IEEE Common Format is also available. The developed software can be checked online at url; http://dexchange.fbe.itu.edu.tr/pwmodel. Representing power system data as XML is advantageous because it can be transformed error-free between various types of platforms, programming languages, and database systems. All database server vendors provide XML support and this is a very big advantage for different corporations that use different database servers. Power system corporations can easily integrate the use of XML as a standard. The transformation of IEEE Common Format to XML is made by Document Object Model (DOM) [9], which is also a W3C Recommendation. DOM is a document object model that models the XML data in a tree form. It reads the whole XML data and generates its tree model in the memory and has a lot of functions to manipulate XML elements. Each node and attribute is easily accessible by DOM. One disadvantage of DOM is that it requires large memory space because it reads whole XML document into memory to form a tree model. However, since Java also provides additional libraries for applications that parse large XML documents and requires less memory one may prefer Java APIs instead of DOM. The SAX (Simple API for XML) API is formed in this way. It follows an event based procedure when processing XML files. That is, when it sees an element opening it triggers startelement() function, and when it sees an element closing it triggers closeelement() function, etc. It does not load the whole XML document to memory at once. The disadvantage of SAX is that it does not allow up- 31

Hasan Dağ and Umut Utkan <?xml version="1.0" encoding="utf-8"?> <!--XML file generated by CF2XML converter (http://dexchange.fbe.itu.edu.tr)--> <p:network xmlns:p="http://dexchange.fbe.itu.edu.tr/pwmodel"> <p:title> <p:mva_base>100.0<p:/mva_base> <p:case_idendification>16 BUS AC SYSTEM <p:case_identification> <LOCATION> <COMPANY>ITU</COMPANY> <CITY>ISTANBUL</CITY> </LOCATION> <p:/title> <p:/network> Figure 6. An example of Namespace usage date on XML data. It can be used for query purposes. Additionally using orthogonal layouter component from YFiles on our transformed XML file generates power system grid layout shown in Fig. 5. This generated layout can be stored as GraphML; another markup language developed to store graphs and bigraphs as XML data. XML is also extensible, additional elements can be added afterwards to the power system data to get extra functionalities. This lets the exchange to be specialized within company transformations. Companies can do any additions to the XML documents except the changes that do not ruin the validity of the document. Also XML documents can contain other data than power system data. For example documents can contain both directed graph data as GraphML representing topology of the grid and solved power flow data corresponding to grid in the same document. This can be done with the help of the XML Namespaces. 3.2. XML Namespaces Since element names in XML are not fixed, very often a name conflict may occur when two different documents use the same name describing two different types of elements. It is impossible to provide uniqueness over all markup languages developed by classical ways. To overcome this difficulty XML Namespaces are used. XML elements are used with prefixes, which are mapped to a URL (uniform resource locator), that usually corresponds to an Internet resource usually the IP addresses to the creator company or association of the document. Fig. 6 shows the usage of XML Namespaces. In the fifth line of the figure a namespace is declared with prifix p and url http://dexchange.fbe.itu.edu.tr/pwmodel. The elements associated to the namespace declared are used with the prefix p in the sample document. The other elements without prefix do not belong to the document declarations. They are included for other purposes such as additional information. Additional capabilities come with the usage of XML Namespaces that make power system data more powerful. Power system data can be transferred with directed graph data as well, which provides layout representation. When the clients get the network layout data, real time monitoring and power system simulations become aware of the predefined network layout information. If program gets the layout information with the related power system data, simulation environments can visualize every power system data on its original grid layout. This capability can be transferred to web using Java applets that makes the application place-independent. One can view and monitor the power system everywhere in Intranet and also on the web if desired. 4. Discussions And Conclusions XML is mostly used for data exchange solution for enterprise applications such as web publishing, e- commerce, etc., due to the features it contains. The huge support provided by various programming languages is an indication for this. Easy integration with the web and Intranet/Internet applications makes XML one of the best solutions for data exchange scenarios. This paper suggests the use of XML as the data exchange base for power system data. Towards this end a program is developed and published on the web for the use of power system community. With the help of this program IEEE common format data can be converted to XML, from which conversion to any other form is then depends on user s like. References [1] Common Format for Exchange of Solved Load Flow Data, Technical Report 6 (1973). 32

An XML Based Data Exchange Model for Power System Studies [2] Extensible Markup Language (XML) 1.0, Technical report, http://www.w3.org/tr/rec-xml (2001). [3] Guide to the W3C XML Specification (XMLspec) DTD, Technical report, W3C Recommendation, http://www.w3.org/xml/1998/06/xmlspec-report (1998). [4] XML Schema Primer, Structures, Datatypes. Technical report, W3C Recommendation, http://www.w3.org/tr/xmlschema-0 (2001). [5] XSL Transformations (XSLT) Version 1.0, Technical report, W3C Recommendation (1999). [6] GraphML Progress Report: Structural Layer Proposal, LNCS 2265, 501 (2001). [7] S. S. Miller, J. V. Staron, M. L. Oatts, and M. K. Enns, Power Systems, 17, 337 (2002). [8] J. Zhu A. devos and S.E. Widergren, Power Industry Computer Applications Conference, 31 (2001). [9] Document Object Model (DOM) Specification, Technical report, W3C Recommendation, http://www.w3.org/tr/rec-dom-level-1 (1998). 33