IEEE C37.232-2007 pdf free download

IEEE C37.232-2007 pdf free download

IEEE C37.232-2007 pdf free download.IEEE Recommended Practice for Naming Time Sequence Data Files.
1. Overview Filenames are essential for both operating systems and users. The filename is the system’s key for unlocking the contents, and without friendly names (where key information about the file is in the 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. Reading 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. 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 specialized 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, 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.1 Scope This recommended practice defines a procedure for naming time sequence data (TSD) files that originate from digital protection and measurement devices, such as transient data records, event sequences, and periodic data logs.
1.2 1.3 2. 3. 3.1 Purpose The purpose of this recommended practice 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 time. Need for this recommended practice The recommended naming convention has been gaining popularity and has so far been used by a nontrivial number of utilities, independent system operators, manufactures, electric reliability commissions, and third- party developers. The North American Electric Reliability Council (NERC) and the Northeast Power Coordinating Council (NPCC) have recommended the use of a common file naming convention. Definitions For the purposes of this document, the following terms and definitions apply. The Authoritative Dictionary of IEEE Standards [B5] 1 should be referenced for terms not defined in this clause. 2.1 disallowed character set: The following characters are not allowed in filenames on most operating systems: 2.2 filename character set: The set is composed of all UTF-8 2 or 7 bit ASCII (American Standard Code for Information Interchange) characters that are allowed in filenames on a particular operating system.
3.2 3.3 Naming conventions for TSD files Several naming conventions are in use today. These formats can be organized in three classes. They are associated, coded, and sequenced. Associated means the filename extension defines the type of data storage format. For example, the extensions “.HDR,” “.CFG,” “.DAT,” and “.INF” are used to indicate that the file contents are compatible with IEEE Std C37.111 TM -1999 [B6]. The nonextension part of an associated filename is totally up to the user. Coded means the filename contains some information about the event. In this case, the storage format is usually manufacturer specific. For example, certain files that are generated from digital fault recorders have the event date and time (up to 12/31/2079-23:59:59.99) and the recorder number (up to 255) coded in the filename. The recorder number is coded in the first two characters of the name, and the date and time are coded in the last nine characters of the filename. The resulting filename is not friendly, and reading it requires special decoding software. For example, “G30BQ1EF.063” is the filename assigned by device number 163 on 09/18/1991 at 14:15:00.630. A detailed example of a similar scheme used to compress over 70 characters of key event information into the old 8.3 filename format is presented in Annex A.

The previous

IEEE C37.232-2011 pdf free download

The next

IEEE C37.122-2010 pdf free download

Related Standards