1、IEEE Std 1159.3-2003IEEE Standards1159.3TMIEEE Recommended Practice for theTransfer of Power Quality DataPublished by The Institute of Electrical and Electronics Engineers, Inc.3 Park Avenue, New York, NY 10016-5997, USA12 January 2004IEEE Standards Coordinating Committee 22Sponsored by theIEEE Stan
2、dards Coordinating Committee 22on Power QualityIEEE StandardsPrint: SH95085PDF: SS95085Authorized licensed use limited to: IEEE Standards Staff. Downloaded on October 26, 2009 at 10:21 from IEEE Xplore. Restrictions apply. Recognized as anAmerican National Standard (ANSI)The Institute of Electrical
3、and Electronics Engineers, Inc.3 Park Avenue, New York, NY 10016-5997, USACopyright 2004 by the Institute of Electrical and Electronics Engineers, Inc.All rights reserved. Published 12 January 2004. Printed in the United States of America.Print: ISBN 0-7381-3578-X SH95085PDF: ISBN 0-7381-3579-9 SS95
4、085No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the priorwritten permission of the publisher.IEEE Std 1159.3-2003 (R2009)IEEE Recommended Practice for the Transfer of Power Quality DataSponsorIEEE Standards Coordinating Committee
5、22on Power Quality Approved 7 August 2003American National Standards InstituteReaffirmed 20 January 2009Approved 20 March 2003IEEE-SA Standards BoardAbstract: This recommended practice defines a file format suitable for exchanging power qualityrelated measurement and simulation data in a vendor inde
6、pendent manner. The format is designedto represent all power quality phenomena identified in IEEE Std 1159TM-1995, IEEE RecommendedPractice on Monitoring Electric Power Quality, other power related measurement data, and isextensible to other data types as well. The recommended file format utilizes a
7、 highly compressedstorage scheme to minimize disk space and transmission times. The utilization of globally uniqueidentifiers (GUID) to represent each element in the file permits the format to be extensible withoutthe need for a central registration authority.Keywords: data interchange, file format,
8、 measurement, monitoring, power quality, power qualitydata interchange format (PQDIF)IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating Committees of theIEEE Standards Association (IEEE-SA) Standards Board. The IEEE develops its standards through a consen
9、susdevelopment process, approved by the American National Standards Institute, which brings together volunteersrepresenting varied viewpoints and interests to achieve the final product. Volunteers are not necessarily members of theInstitute and serve without compensation. While the IEEE administers
10、the process and establishes rules to promote fairnessin the consensus development process, the IEEE does not independently evaluate, test, or verify the accuracy of any of theinformation contained in its standards.Use of an IEEE Standard is wholly voluntary. The IEEE disclaims liability for any pers
11、onal injury, property or otherdamage, of any nature whatsoever, whether special, indirect, consequential, or compensatory, directly or indirectly resultingfrom the publication, use of, or reliance upon this, or any other IEEE Standard document.The IEEE does not warrant or represent the accuracy or c
12、ontent of the material contained herein, and expressly disclaimsany express or implied warranty, including any implied warranty of merchantability or fitness for a specific purpose, or thatthe use of the material contained herein is free from patent infringement. IEEE Standards documents are supplie
13、d “AS IS.”The existence of an IEEE Standard does not imply that there are no other ways to produce, test, measure, purchase, market,or provide other goods and services related to the scope of the IEEE Standard. Furthermore, the viewpoint expressed at thetime a standard is approved and issued is subj
14、ect to change brought about through developments in the state of the art andcomments received from users of the standard. Every IEEE Standard is subjected to review at least every five years forrevision or reaffirmation. When a document is more than five years old and has not been reaffirmed, it is
15、reasonable toconclude that its contents, although still of some value, do not wholly reflect the present state of the art. Users are cautionedto check to determine that they have the latest edition of any IEEE Standard.In publishing and making this document available, the IEEE is not suggesting or r
16、endering professional or other servicesfor, or on behalf of, any person or entity. Nor is the IEEE undertaking to perform any duty owed by any other person orentity to another. Any person utilizing this, and any other IEEE Standards document, should rely upon the advice of acompetent professional in
17、 determining the exercise of reasonable care in any given circumstances.Interpretations: Occasionally questions may arise regarding the meaning of portions of standards as they relate to specificapplications. When the need for interpretations is brought to the attention of IEEE, the Institute will i
18、nitiate action to prepareappropriate responses. Since IEEE Standards represent a consensus of concerned interests, it is important to ensure that anyinterpretation has also received the concurrence of a balance of interests. For this reason, IEEE and the members of itssocieties and Standards Coordin
19、ating Committees are not able to provide an instant response to interpretation requestsexcept in those cases where the matter has previously received formal consideration. Comments for revision of IEEE Standards are welcome from any interested party, regardless of membership affiliation withIEEE. Su
20、ggestions for changes in documents should be in the form of a proposed change of text, together with appropriatesupporting comments. Comments on standards and requests for interpretations should be addressed to:Secretary, IEEE-SA Standards Board445 Hoes LaneP.O. Box 1331Piscataway, NJ 08855-1331USAA
21、uthorization to photocopy portions of any individual standard for internal or personal use is granted by the Institute ofElectrical and Electronics Engineers, Inc., provided that the appropriate fee is paid to Copyright Clearance Center. Toarrange for payment of licensing fee, please contact Copyrig
22、ht Clearance Center, Customer Service, 222 Rosewood Drive,Danvers, MA 01923 USA; +1 978 750 8400. Permission to photocopy portions of any individual standard for educationalclassroom use can also be obtained through the Copyright Clearance Center.Note: Attention is called to the possibility that imp
23、lementation of this standard may require use of subjectmatter covered by patent rights. By publication of this standard, no position is taken with respect to theexistence or validity of any patent rights in connection therewith. The IEEE shall not be responsible foridentifying patents for which a li
24、cense may be required by an IEEE standard or for conducting inquiries into thelegal validity or scope of those patents that are brought to its attention.Copyright 2004 IEEE. All rights reserved. iiiIntroduction(This introduction is not part of IEEE Std 1159.3-2003, IEEE Recommended Practice for the
25、Transfer of Power QualityData.)This recommended practice evolved over 10 years and includes the work of private companies and researchinstitutions who kindly contributed their earlier work, source code, and staff to the 1159.3 task force when itwas formed. This earlier work made its way into commerc
26、ial applications whose vendors have continued toupgrade throughout the standards development process. The feedback from those vendors and theircustomers have provided invaluable experience and feedback that have made this recommended practice amuch better document in its initial release.The primary
27、user of this standard will be engineers and software developers who are called upon to createsoftware to encode and decode files utilized for power quality data interchange using the guidelines in thisrecommended practice. Although the document is thorough and complete, detailed examples and sourcec
28、ode can be quite helpful when implementing the format described herein. Therefore, reference andsupporting documentation (header files, sample code, etc.) related to this standard can be found at the 1159.3task force web site which at the time of this writing could be found at the following URL: htt
29、p:/grouper.ieee.org/groups/1159/3/docs.htmlPatentsAttention is called to the possibility that implementation of this standard may require use of subject mattercovered by patent rights. By publication of this standard, no position is taken with respect to the existence orvalidity of any patent rights
30、 in connection therewith. The IEEE shall not be responsible for identifyingpatents for which a license may be required by an IEEE standard or for conducting inquiries into the legalvalidity or scope of those patents that are brought to its attention.Interpretations and errataInterpretations and erra
31、ta associated with this recommended practice may be found at one of the followingInternet locations: http:/standards.ieee.org/reading/ieee/interp http:/standards.ieee.org/reading/ieee/updates/errata/iv Copyright 2004 IEEE. All rights reserved.AcknowledgmentsThe following individuals provided substan
32、tial contributions to the development of this recommendedpractice:Core Design and DocumentationBill DabbsErich W. GuntherJack KingRobert F. ScottIndependent ReviewDr. Mesut E. BaranDaniel BrooksExample Software and MaintenanceErich W. GuntherJack KingRobert F. ScottParticipantsAt the time this recom
33、mended practice was completed, the working group on Power Quality DataInterchange Format had the following membership. Scott Peele, ChairDavid Kreiss, Secretary EmeritusRichard Bingham, SecretaryErich W. Gunther, Technical EditorRajaie Abu-HashimVladimir BaschRoger BergeronMike BridgewoodDaniel Broo
34、ksRichard BrownRandy CollinsLarry ConradJames CraneJohn CsomayBehnam DanaiAndy DetloffJoe EnkStan FabinwskiGil HensleyMark KempkerAjay KoliwadJeff LamoreeAlex McEachernMark McGranaghanLarry MorganAllen MorinecDavid MuellerRam MukerjiDan NordelGreg OlsenPragasen PillayV. RajagopalanGreg RauchDan Sabi
35、nAndrew SaglSurya SantosaPeter ShahGeorge SimardLinh TuDavid VannoyMarek WaclawiakCheri WarrenSteve WhisenantJames WikstonCopyright 2004 IEEE. All rights reserved. vThe following members of the balloting committee voted on this standard. Balloters may have voted forapproval, disapproval, or abstenti
36、on. When the IEEE-SA Standards Board approved this standard on 20 March 2003, it had the followingmembership:Don Wright, ChairHoward M. Frazier, Vice ChairJudith Gorman, Secretary*Member EmeritusAlso included are the following nonvoting IEEE-SA Standards Board liaisons:Alan Cookson, NIST Representat
37、iveSatish K. Aggarwal, NRC RepresentativeMichelle TurnerIEEE Standards Project EditorGregory ArdreyRichard BinghamMath BollenRichard BrownTommy CooperAndrew DettloffDavid GilmerThomas GrebeRandall GrovesErich W. GuntherGilbert HensleyJohn KennedyDavid KreissMaurice LinkerAlex McEachernMark McGranagh
38、anChristopher MelhornRobert L MorganCharles PerryPaulo RibeiroJames RuggieriDaniel SabinJordan ShikoskiRobert SmithDehn StevensCassio VinhalH. Stephen BergerJoe BruderBob DavisRichard DeBlasioJulian Forster*Toshio FukudaArnold M. GreenspanRaymond HapemanDonald M. HeirmanLaura HitchcockRichard H. Hul
39、ettAnant JainLowell G. JohnsonJoseph L. Koepfinger*Tom McGeanSteve MillsDaleep C. MohlaWilliam J. MoylanPaul NikolichGary RobinsonMalcolm V. ThadenGeoffrey O. ThompsonDoug ToppingHoward L. Wolfmanvi Copyright 2004 IEEE. All rights reserved.Contents1. Overview 11.1 Scope 11.2 Purpose. 12. References
40、23. Definitions . 24. Physical structure. 24.1 Overall file structure 24.2 Internal record structure. 45. Logical structure 55.1 Logical record structure . 55.2 Logical element structure. 75.3 Logical structure of container record. 75.4 Logical structures of data sources and observations 95.5 How to
41、 put together a series 106. Compression 126.1 Compression algorithmzlib 126.2 Record-level compression 127. Logical device modeling 137.1 General procedures 147.2 Representing a waveform recording 167.3 Representing an RMS variation recording. 207.4 Representing periodically recorded steady state va
42、lues 25Annex A (normative) Physical format definitions 31Annex B (normative) Logical structure documentation39Annex C (informative) File directory structure 117Copyright 2004 IEEE. All rights reserved. 1IEEE Recommended Practice for the Transfer of Power Quality Data1. Overview1.1 ScopeDevelop a rec
43、ommended practice for a file format suitable for exchanging power quality-relatedmeasurement and simulation data in a vendor-independent manner. Appropriate definitions and eventcategories to be developed by other task forces under the IEEE Standards Coordinating Committee 22(SCC-22) on Power Qualit
44、y and the IEEE 1159 Working Group on Power Quality Monitoring.1.2 PurposeA variety of simulation, measurement, and analysis tools for power quality engineers are now available frommany vendors. Generally, the data created, measured, and analyzed by these tools are incompatible betweenvendors. The pr
45、oposed file format will provide a common ground that all vendors could export to and importfrom to allow the end user maximum flexibility in choice of tool and vendor.There are two “layers” to this Power Quality Data Interchange Format (PQDIF): the physical layer and thelogical layer. The physical l
46、ayer describes the physical structure of the file without regard to what willactually be stored in it. It uses tags to identify particular elements of the file. This is similar in concept totagged image file format (TIFF), used for storing images.The logical layer uses the structure defined by the p
47、hysical layer; it specifies specific tags to use whenbuilding up elements in the file.The physical layer is based on Specific “physical” data types (e.g., INT1, INT2, INT4, REAL4, REAL8, etc.) for portability and aspecific list of IDs for physical representation (e.g., ID_SERIES_PHYS_TYPE_INTEGER1,
48、etc.) 4 byte alignment for efficient processing Little endian byte ordering (least significant byte stored first, ordering used in PCs) Tags, using globally unique identifiers (GUIDs), for unique identification of elements (hereaftercalled “tags”)The logical layer is based on Specific lists of tags
49、to identify elements of a file A hierarchy of tags and expected physical types Extensibility using user-defined tags for private data Extensibility of the standard format using tags defined in the futureIEEEStd 1159.3-2003 IEEE RECOMMENDED PRACTICE FOR THE TRANSFER2 Copyright 2004 IEEE. All rights reserved.To keep things simple, many elements in the logical layer are based on an explicit list of enumerated IDs,such as Phase (ID_PHASE_AN, ID_PHASE_BN, etc.) IEEE 1159 disturbance category (ID_1159_TRANSIENT, ID_1159_SHORTDUR, etc.) High-level quantity type (ID_Q
