ANSI IEEE C37 232-2011 Common Format for Naming Time Sequence Data Files (COMNAME)《命名时序数据文件的通用格式标准(COMNAME)》.pdf

《ANSI IEEE C37 232-2011 Common Format for Naming Time Sequence Data Files (COMNAME)《命名时序数据文件的通用格式标准(COMNAME)》.pdf》由会员分享，可在线阅读，更多相关《ANSI IEEE C37 232-2011 Common Format for Naming Time Sequence Data Files (COMNAME)《命名时序数据文件的通用格式标准(COMNAME)》.pdf（25页珍藏版）》请在麦多课文档分享上搜索。

1、g3IEEE Std 90003-2008 IEEE Std 90003-2008 IEEE Standard for Common Format for Naming Time Sequence Data Files (COMNAME) g3Sponsored by the Power System Relaying Committee g3IEEE 3 Park Avenue New York, NY 10016-5997 USA 9 November 2011 g3IEEE Power +1 978 750 8400. Permission to photocopy portions o

2、f any individual standard for educational classroom use can also be obtained through the Copyright Clearance Center. Introduction This introduction is not part of IEEE Std C37.232-2011, IEEE Standard for Common Format for Naming Time Sequence Data Files (COMNAME). Microprocessor-based measurement an

3、d protection devices (digital devices) used in electric power substations produce large quantities of time sequence data (TSD) files that contain vast volumes of data about the power system. Additional TSD files are also produced while processing the original data and while performing maintenance an

4、d testing operations on the original devices. Many problems are associated with handling such large quantities of TSD files. The term handling means reporting, saving, archiving, exchanging, and so on. The problems are mainly due to the fact that currently there are too many different types of propr

5、ietary naming conventions in circulation. Work on this project began with the IEEE-PES-PSRC Communications Subcommittee task force HTF8 in 1999. Working group H8 then followed, and their report was posted in 2001. Their reported naming convention solved many problems that are associated with handlin

6、g the large quantities of TSD files. Their main objective was to define a common naming convention. In 2002 a new task force was formed to study the potential of developing the common naming convention into an IEEE standard. In 2003 this working group, also designated H8, was formed with the objecti

7、ve of writing this recommended practice. The recommended TSD filename is human readable and includes, among other features, key portions of the information contained in the file, including, but not limited to, the name of the circuit, substation, and recording device, and the date and time of initia

8、l occurrence. This was not easy to do under older operating systems, which limited file names to 11 characters, but now filenames of up to 253 characters are generally permitted. Notice to users Laws and regulations Users of these documents should consult all applicable laws and regulations. Complia

9、nce with the provisions of this standard does not imply compliance 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 t

10、hat is not in compliance with applicable laws, and these documents 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

11、 private self-regulation, standardization, and the promotion of engineering 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. iv Copyright 2011 IEEE. All rights rese

12、rved. Updating of IEEE documents Users of IEEE standards should be aware that these documents may be superseded 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 co

13、nsists of the current edition of the document together with any amendments, corrigenda, or errata then in effect. 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

14、Association web site at http:/ieeexplore.ieee.org/xpl/standards.jsp, or contact the IEEE at the address listed 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. Errata Errata, if an

15、y, for this and all other standards can be accessed at the following URL: http:/standards.ieee.org/findstds/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/findst

16、ds/interps/index.html. Patents Attention is called to the possibility that implementation of this 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 th

17、erewith. The IEEE is not responsible for identifying Essential 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

18、 Assurance, if any, or in any licensing agreements are reasonable 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

19、 obtained from the IEEE Standards Association. v Copyright 2011 IEEE. All rights reserved. vi Copyright 2011 IEEE. All rights reserved. Participants At the time this standard was submitted to the IEEE-SA Standards Board for approval, the File Name Convention Working Group had the following membershi

20、p: Eric Allen, Chair J. Rick Cornelison, Vice Chair Amir Z. Makki, Secretary David Bertagnolli Jim Hackett Ken Martin The following members of the individual balloting committee voted on this standard. Balloters may have voted for approval, disapproval, or abstention. William J. Ackerman Satish K. A

21、ggarwal Eric Allen Ali Al Awazi G. Bartok Kenneth Behrendt Kenneth Birt William Bloethe Gustavo Brunello Stephen Conrad J. Rick Cornelison Gary Donner Michael Dood Gearold O. H. Eidhin Gary Engmann Jeffrey Gilbert Jalal Gohari Randall C. Groves Ajit Gwal Roger Hedding Gerald Johnson Piotr Karocki St

22、anley Klein Joseph L. Koepfinger Jim Kulchisky Chung-Yiu Lam Greg Luri Amir Z. Makki Wayne W. Manges Pierre Martin John McDonald Gary Michel R. Murphy Bruce Muschlitz Michael S. Newman Robert Orndorff Lorraine Padden Bruce Pickett Michael Roberts Charles Rogers Bob Saint Bartien Sayogo Gil Shultz Je

23、rry Smith Gary Stoedter Charles Sufana Michael Swearingen Richard Taylor William Taylor Joe Uchiyama John Vergis Phil Winston Richard Young Jian Yu Sergio Zimath When the IEEE-SA Standards Board approved this standard on 31 October 2011, it had the following membership: Richard H. Hulett, Chair John

24、 Kulick, Vice Chair Robert M. Grow, Past Chair Judith Gorman, Secretary Masayuki Ariyoshi William Bartley Ted Burse Clint Chaplin Wael Diab Jean-Philippe Faure Alexander Gelman Paul Houz Jim Hughes Joseph L. Koepfinger* David J. Law Thomas Lee Hung Ling Oleg Logvinov Ted Olsen Gary Robinson Jon Walt

25、er Rosdahl Sam Sciacca Mike Seavey Curtis Siller Phil Winston Howard L. Wolfman Don Wright *Member Emeritus Also included are the following nonvoting IEEE-SA Standards Board liaisons: Satish K. Aggarwal, NRC Representative Richard DeBlasio, DOE Representative Michael Janezic, NIST Representative Don

26、 Messina IEEE Standards Program Manager, Document Development Soo H. Kim IEEE Standards Project Manager vii Copyright 2011 IEEE. All rights reserved. Contents 1. Overview 1 1.1 Scope . 1 1.2 Purpose 1 1.3 General 1 1.4 Need for this standard 2 2. Definitions 2 3. Filenames 3 3.1 General 3 3.2 Naming

27、 conventions for TSD files 3 3.3 Coding schemes. 3 4. Standard file naming convention 4 4.1 General 4 4.2 Limitations. 5 4.3 Required fields. 5 4.4 User fields 6 4.5 Extension field. 7 4.6 Examples of the file naming convention . 7 4.7 Geographic position (latitude and longitude) 8 4.8 Additional ex

28、amples 8 4.9 Short filenames 8 5. Uniqueness . 9 6. Universality 9 7. Applications 10 Annex A (informative) Example coding algorithm 11 Annex B (informative) Example source code. 12 Annex C (informative) Bibliography 15 viii Copyright 2011 IEEE. All rights reserved. IEEE Standard for Common Format f

29、or Naming Time Sequence Data Files (COMNAME) 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, environmental, and health practices or regulatory r

30、equirements. 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 Notices and Disclaimers Concerning IEEE

31、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 procedure for naming time sequence data (TSD) files that originate from digital protection and measurement devices, such as transient d

32、ata records, event sequences, and periodic data logs. The filename includes, among other features, key portions of the information contained in the file, including, but not limited to, the names of the circuit, substation, and recording device, and the date and time of event occurrence. 1.2 Purpose

33、The purpose of this standard is to define a procedure for naming TSD files, a procedure that is needed to resolve many problems that are associated with reporting, saving, exchanging, archiving, and retrieving large numbers of files. There is no other defined standard for naming such files at this t

34、ime. 1.3 General Filenames are essential for both operating systems and users. The filename is the systems key for unlocking the contents, and without friendly names (where key information about the file is in the 1 Copyright 2011 IEEE. All rights reserved. IEEE Std C37.232-2011 IEEE Standard for Co

35、mmon Format for Naming Time Sequence Data Files (COMNAME) 2 Copyright 2011 IEEE. All rights reserved. filename), the user will have trouble handling large numbers of files. Also, programs for analysis and trending applications have to automatically sift through and process large numbers of files. Re

36、ading file contents requires considerable disk access time especially for large files. But reading filenames is much faster because the filenames are stored separately from their contents in system files called allocation tables, and these tables can be quickly loaded with minimal disk access time.

37、Meaningful filenames provide software developers with the ability to write programs that can quickly manage and process large numbers of files. The hardware benefits as well from the reduced number of disk access operations. The alternative to meaningful filenames is to build and maintain a speciali

38、zed database. However, specialized databases are very costly to create and maintain, and they use extremely large memory structures. Accordingly, the recommended filename information is specified in comma-delimited format where commas are used to separate the information into multiple fields. Thus,

39、spreadsheet-like tables can be made from directory listings of filenames. Such tables provide users with an easy way to perform sort and query operations based on any one of the fields in the filename, in effect providing the same look and feel as any other specialized database application. 1.4 Need

40、 for this standard The standard naming convention has been gaining popularity and has so far been used by a nontrivial number of utilities, independent system operators, manufacturers, electric reliability commissions, and third-party developers. The North American Electric Reliability Council (NERC

41、) and the Northeast Power Coordinating Council (NPCC) have recommended the use of a common file naming convention. 2. Definitions For the purposes of this document, the following terms and definitions apply. The IEEE Standards Dictionary: Glossary of Terms $ % (i.e., question mark, quotation mark, f

42、orward slash, backward slash, less than, greater than, asterisk, pipe, colon, semi-colon, brackets, dollar sign, percent, and braces). Additionally, spaces in filenames may cause problems on most operating systems. filename character set: The set is composed of all UTF-8 or 7-bit ASCII (American Sta

43、ndard Code for Information Interchange) characters that are allowed in filenames on a particular operating system. NOTEFor UTF-8, see The Unicode Standard, Version 5.0 B11.3time sequence data (TSD) file: A TSD file is any type of electronic data file where each data item in the file corresponds to a

44、n instant of time that is identified by an explicit or implicit time tag, such as transient data records, event sequences, and periodic data logs. 1The IEEE Standards Dictionary: Glossary of Terms current CDs do not work with filenames that are more than 64 characters long; users who deal with thous

45、ands of long filenames per folder have also reported problems with their compression applications. However, given the rate of advancement in technology, it is highly possible that these limitations will soon vanish or become obsolete. The naming convention has been successfully tested under a variet

46、y of operating systems. 4.3 Required fields Start Date: The field is defined in a fixed numeric format that allows for sorting (yymmdd). The field width is six digits. The first two digits are for the year (0099), the second two digits are for the month (0112), and the last two digits are for the da

47、y (0131). For example, the code 010203 means the date is February 3, 2001 (leading zeros are required for values that are less than two digits wide). The Start Date is the date at which the first sample was recorded (the first sample in the file, physically). However, depending on the last character

48、 in the Time Code field, the Start Date could be the date at which the first trigger occurred (date at which the originating instrument initially triggered). This distinction is made because digital relays and digital fault recorders provide a pre-fault record before the fault record. It is up to th

49、e user to decide whether the Start Date is the date at which the first sample was recorded or is the date at which the first trigger occurred. By default, the Start Date is the date at which the first sample was recorded. If the last character of the Time Code is set to “t,” then the Start Date is the date at which the first trigger occurred. The Working Group has chosen to limit the year expression to two digits to limit the number of characters in the filename. The Working Group has carefully considered a four-digit year expression and has decided against