1、 IEEE Standard for Common Format forEvent Data Exchange (COMFEDE) for Power Systems Sponsored by the IEEE Power System Relaying Committee IEEE 3 Park Avenue New York, NY 10016-5997 USA 11 November 2010IEEE Power +1 978 750 8400. Permission to photocopy portions of any individual standard for educati
2、onal classroom use can also be obtained through the Copyright Clearance Center. iv Copyright 2010 IEEE. All rights reserved. Introduction This introduction is not part of IEEE Std C37.239-2010, IEEE Standard for Common Format for Event Data Exchange (COMFEDE) for Power Systems. Power network fault e
3、vent data are indispensable to the analysis, testing, evaluation, and simulation of power systems and related protection schemes. The flexibility provided by digital devices in recording such event data has brought about a situation wherein the users of these records are confronted with the difficul
4、ty of dealing with the different formats used by each device to generate, store, and transmit the recorded data. Notice to users Laws and regulations Users of these documents should consult all applicable laws and regulations. Compliance with the provisions of this standard does not imply compliance
5、 to any applicable regulatory requirements. Implementers of the standard are responsible for observing or referring to the applicable regulatory requirements. IEEE does not, by the publication of its standards, intend to urge action that is not in compliance with applicable laws, and these documents
6、 may not be construed as doing so. Copyrights This document is copyrighted by the IEEE. It is made available for a wide variety of both public and private uses. These include both use, by reference, in laws and regulations, and use in private self-regulation, standardization, and the promotion of en
7、gineering practices and methods. By making this document available for use and adoption by public authorities and private users, the IEEE does not waive any rights in copyright to this document. Updating of IEEE documents Users of IEEE standards should be aware that these documents may be superseded
8、 at any time by the issuance of new editions or may be amended from time to time through the issuance of amendments, corrigenda, or errata. An official IEEE document at any point in time consists of the current edition of the document together with any amendments, corrigenda, or errata then in effec
9、t. In order to determine whether a given document is the current edition and whether it has been amended through the issuance of amendments, corrigenda, or errata, visit the IEEE Standards Association web site at http:/ieeexplore.ieee.org/xpl/standards.jsp, or contact the IEEE at the address listed
10、previously. For more information about the IEEE Standards Association or the IEEE standards development process, visit the IEEE-SA web site at http:/standards.ieee.org. v Copyright 2010 IEEE. All rights reserved. Errata Errata, if any, for this and all other standards can be accessed at the followin
11、g URL: http:/standards.ieee.org/reading/ieee/updates/errata/index.html. Users are encouraged to check this URL for errata periodically. Interpretations Current interpretations can be accessed at the following URL: http:/standards.ieee.org/reading/ieee/interp/ index.html. Patents Attention is called
12、to the possibility that implementation of standard may require use of subject matter covered by patent rights. By publication of this standard, no position is taken with respect to the existence or validity of any patent rights in connection therewith. The IEEE is not responsible for identifying Ess
13、ential Patent Claims for which a license may be required, for conducting inquiries into the legal validity or scope of Patents Claims or determining whether any licensing terms or conditions provided in connection with submission of a Letter of Assurance, if any, or in any licensing agreements are r
14、easonable or non-discriminatory. Users of this standard are expressly advised that determination of the validity of any patent rights, and the risk of infringement of such rights, is entirely their own responsibility. Further information may be obtained from the IEEE Standards Association. vi Copyri
15、ght 2010 IEEE. All rights reserved. Participants At the time this standard was submitted to the IEEE-SA Standards Board for approval, the Common Data Format for IED Event Data Working Group had the following membership: Mark Adamiak, Chair Pierre L. Martin, Vice Chair Eric Allen Scott Anderson Alex
16、Apostolov Christoph Brunner Jim Hacket Randy Hamilton Juergen Holbach Mladen Kezunovic Stanley Klein Larry Smith Stan Thompson Benton Vandiver The following members of the individual balloting committee voted on this standard. Balloters may have voted for approval, disapproval, or abstention. Willia
17、m J. Ackerman Mark Adamiak S. Aggarwal James Ariza Ali Al Awazi Hugh Barrass Martin Baur Kenneth Behrendt Oscar Bolado Steven Brockschink Gustavo Brunello Suresh Channarasappa Arvind K. Chaudhary Keith Chow Stephen Conrad R. W. Corlew James Cornelison Carlo Donati Gary Donner Michael Dood Neal Dowli
18、ng Gary Engmann Kenneth Fodero Jeffrey Gilbert Manjinder Gill Jalal Gohari Edwin Goodwin Randall Groves Roeer Hedding Gary Heuston Werner Hoelzl Stuart Holoman David Horvath C. Huntley Akio Iso R. Jackson Junghoon Jee Piotr Karocki Tanuj Khandelwal Yuri Khersonsky Yongburn Kim James Kinney Stanley K
19、lein J. Koepfinger Jim Kulchisky Chung-Yiu Lam Charles Lennon James Liming G. Luri Pierre L. Martin William McBride John McDonald Gary Michel Keith Moore Jerry Murphy R. Murphy Bruce Muschlitz Anthony Napikoski Michael S. Newman Robert Orndorff Chris Osterloh Lorraine Padden Bansi Patel Farnoosh Rah
20、matian R. Ray Robert Robinson Charles Rogers Sukhbir Sachdev Bob Saint Miriam Sanders Steven Sano Bartien Sayogo Thomas Schossig Lubomir Sevov Devki Sharma Gil Shultz Mark Simon Vesselin Skendzic James Smith Jerry Smith John Spare Gary Stoedter Michael Swearingen Richard Taylor John Tengdin John Tot
21、h Demetrios Tziouvaras Joe Uchiyama Eric Udren Sterling Vaden Srinivasa Vemuru John Vergis Jane Verner John Wang Hung-Yu Wei Kenneth White Philip Winston Paul Work Richard Young Oren Yuen vii Copyright 2010 IEEE. All rights reserved. When the IEEE-SA Standards Board approved this standard on 30 Sept
22、ember 2010, it had the following membership: Robert M. Grow, Chair Richard H. Hulett, Vice Chair Steve M. Mills, Past President Judith Gorman, Secretary Karen Bartleson Victor Berman Ted Burse Clint Chaplin Andy Drozd Alexander Gelman Jim Hughes Young Kyun Kim Joseph L. Koepfinger* John Kulick David
23、 J. Law Hung Ling Oleg Logvinov Ted Olsen Ronald C. Petersen Thomas Prevost Jon Walter Rosdahl Sam Sciacca Mike Seavey Curtis Siller Don Wright *Member Emeritus Also included are the following nonvoting IEEE-SA Standards Board liaisons: Satish Aggarwal, NRC Representative Richard DeBlasio, DOE Repre
24、sentative Michael Janezic, NIST Representative Don Messina IEEE Standards Program Manager, Document Development Matthew J. Ceglia IEEE Standards Program Manager, Technical Program Development viii Copyright 2010 IEEE. All rights reserved. Contents 1. Overview 1 1.1 Scope . 1 1.2 Purpose 1 2. Normati
25、ve references 2 3. Definitions, acronyms, and abbreviations 2 3.1 Definitions . 2 3.2 Acronyms and abbreviations . 3 4. Conformance 3 5. The COMFEDE format specification . 4 5.1 General 4 5.2 Name spaces 4 5.3 Specification method . 5 5.4 Extensibility . 7 5.5 COMFEDE versions and compatibility . 8
26、5.6 Main structure of the schema . 10 5.7 The COMFEDE and Log sections . 12 5.8 EntryData . 17 5.9 PayloadData . 23 Annex A (normative) The COMFEDE XML schema 41 Annex B (informative) COMFEDE instance file example . 60 Annex C (informative) Bibliography 63 1 Copyright 2010 IEEE. All rights reserved.
27、 IEEE Standard for Common Format for Event Data Exchange (COMFEDE) for Power Systems IMPORTANT NOTICE: This standard is not intended to ensure safety, security, health, or environmental protection. Implementers of the standard are responsible for determining appropriate safety, security, environment
28、al, and health practices or regulatory requirements. This IEEE document is made available for use subject to important notices and legal disclaimers. These notices and disclaimers appear in all publications containing this document and may be found under the heading “Important Notice” or “Important
29、Notices and Disclaimers Concerning IEEE Documents.” They can also be obtained on request from IEEE or viewed at http:/standards.ieee.org/IPR/disclaimers.html. 1. Overview 1.1 Scope This standard defines a format for files containing event data such as sequence of events or fault summary reports coll
30、ected from power systems or power system models. The format is intended to provide an easily interpretable form for use in exchanging data. 1.2 Purpose This standard defines a common format for the data files needed for the exchange of various types of power network events in order to facilitate eve
31、nt data integration and analysis from multiple data sources and from different vendor devices. The flexibility provided by digital devices in recording network fault event data in the electric utility industry has generated the need for a standard format for the exchange of data. These data are bein
32、g used with various devices to enhance and automate the analysis, testing, evaluation, and simulation of power systems and related protection schemes during fault and disturbance conditions. Since each source of data may use a different proprietary format, a common data format is necessary to facili
33、tate the exchange of such data between applications. This will facilitate the use of proprietary data in diverse applications and allow users of one proprietary system to use digital data from other systems. IEEE Std C37.239-2010 IEEE Standard for Common Format for Event Data Exchange (COMFEDE) for
34、Power Systems 2 Copyright 2010 IEEE. All rights reserved. 2. Normative references The following referenced documents and URLs are indispensable for the application of this document (i.e., they must be understood and used, so each referenced document is cited in text and its relationship to this docu
35、ment is explained). For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments or corrigenda) applies. World Wide Web Consortium, W3C Recommendation, XML Schema Part 1: Structures, 2d ed., 2004.1,2World Wide W
36、eb Consortium, W3C Recommendation, XML Schema Part 2: Datatypes, 2d ed., 2004.3World Wide Web Consortium, W3C Recommendation, Namespaces in XML 1.1, 2004.43. Definitions, acronyms, and abbreviations For the purposes of this document, the following terms and definitions apply. The IEEE Standards Dict
37、ionary: Glossary of Terms cannot be empty; and shall be limited to two to four characters. This is an optional attribute. If it is not present, the default value is assumed to be unknown. The IEDNameplate element is of type tIEDNameplate and has attributes as defined hereafter and in Table 5. IEEE S
38、td C37.239-2010 IEEE Standard for Common Format for Event Data Exchange (COMFEDE) for Power Systems 15 Copyright 2010 IEEE. All rights reserved. Table 5 Attributes of the element type tIEDNameplate Attribute name Description M/O name The name of the IED that produced the COMFEDE file. M vendor The n
39、ame of the manufacturer of the IED. M model The IED model. O serNum The IED serial number. O hwRev The IED hardware revision. O swRev The IED firmware revision. O 5.7.2 Entry The Entry element identifies each entry in the Log and is of type tEntry. Sequence number. Time when the Entry is added to th
40、e buffer Each element Entry shall contain at least one EntryData element. Table 6 shows the two optional attributes of the element Entry. Table 6 Attributes of the element type tEntry Attribute name Description M/O entryId Is a unique reference to all logged entries (elements EntryData) having the s
41、ame value of TimeOfEntry. O timeOfEntry Is the time when the logged entry (element EntryData) is added to a LOG. That time may be different to the time stamp of the data (element Timestamp), which is the time when the event occurred that caused the logged entry to be created. O 5.7.3 SettingFileName
42、 The SettingFileName element is of type tFileName. Each SettingFileName element identifies the name of a setting file in force in the device when the report was extracted. The type tFileName has one mandatory attribute extensionName corresponding to the name of the file extension. IEEE Std C37.239-2
43、010 IEEE Standard for Common Format for Event Data Exchange (COMFEDE) for Power Systems 16 Copyright 2010 IEEE. All rights reserved. Allowed file extension names are defined by the enumeration tFileExtensionEnum. The content of the type tFileExtensionEnum is the union of the enumerations tStandardiz
44、edFileExtensionEnum and tNonStandardizedFileExtensionEnum. tStandardizedFileExtensionEnum is the enumeration of the allowed standardized extension names.9Configured IED Description file as defined in IEC 61850-6 System Configuration Description file as defined in IEC 61850-6 Substation Specification
45、 Description file as defined in IEC 61850-6 COMTRADE Configuration file as defined in IEEE Std C37.111-1999 COMTRADE Data file as defined in IEEE Std C37.111-1999 COMTRADE Information file as defined in IEEE Std C37.111-1999 9Information on IEEE Std C37.111TM-1999 B5 can be found in Annex C. IEEE St
46、d C37.239-2010 IEEE Standard for Common Format for Event Data Exchange (COMFEDE) for Power Systems 17 Copyright 2010 IEEE. All rights reserved. COMTRADE Header file as defined in IEEE Std C37.111-1999 COMTRADE single file as defined in IEEE Std C37.111-1999 tNonStandardizedFileExtensionEnum is an en
47、umeration allowing any name with the following restrictions: It shall at least have three characters. The allowed characters are any mixture of letters and decimals. 5.8 EntryData The EntryData element is of type tEntryData and contains two mandatory elements (DataRef and either Val or DA) and two o
48、ptional elements (ReasonCode and PayloadData). The type tEntryData is as follows: IEEE Std C37.239-2010 IEEE Standard for Common Format for Event Data Exchange (COMFEDE) for Power Systems 18 Copyright 2010 IEEE. All rights reserved. tEntryData has two attribute groups: agTimeStamp and agQuality. An
49、attribute group is a named group of attribute declarations so that they may be incorporated as a group into complex type definitions. The attribute groups agTimeStamp and agQuality are described in 5.8.1 through 5.8.2. tEntryData has also two optional attributes, faultTrigger and eventType, as shown in Table 7. Table 7 Attributes of the element type tEntryData Attribute name Description M/O faultTrigger Boolean to indicate if the event was triggered by a fault trigger. O evenType Enumeration of types of events that may be used to filter events based on those
