This recommended practice is limited to maintenance, test schedules, and testing procedures that can be used to optimize the life and performance of valve-regulated lead-acid (VRLA) batteries for stationary applications. It also provides guidance to determine when batteries should be replaced. The maintenance and testing programs described in this recommended practice represent "the best program" based on the information reviewed at the time this document was developed. The user should evaluate… read more these practices against their operating experience, operating conditions, manufacturer's recommendations, resources, and needs in developing a maintenance program for a given application. These maintenance and testing recommendations were developed without consideration of economics, availability of testing equipment and personnel, or relative importance of the application. Development of a maintenance and testing program for a specific application requires consideration of all issues, not just the technical issues considered in this document. Stationary cycling applications, such as those found in alternative energy applications, are also beyond the scope of this recommended practice. This recommended practice does not include any other component of the dc system nor surveillance and testing of the dc system, even though the battery is part of that system. Sizing, installation, qualification, selection criteria, and other battery types and applications are also beyond the scope of this recommended practice. read less
The methods given here relate to measurements, as made with either analog or digital indicating or integrating instruments, of power, energy, voltage, and current, in dc or ac rotating machines, transformers, induction apparatus, arc and resistance heating equipment, mercury arc, thermionic, or solid-state rectifiers and inverters. Measurements made with supplementary instruments and devices are also included. This guide does not deal with measurements of resistance or temperature that are… read more often included in determining the performance characteristics of electric machinery. Instruments for these latter measurements will be found in the specific publications dealing with the particular measurement, such as IEEE Std 118-1978, IEEE Standard Test Code for Resistance Measurements [4]1, and IEEE Std 119-1974, IEEE Recommended Practice for General Principles of Temperature Measurement as Applied to Electrical Apparatus [5]. read less
This standard provides a protocol for exposing cable samples to a theoretical 20 kW (70 000 BTU/h) flaming ignition source for a 20-min test duration. The test determines the flame propagation tendency of single-conductor and multi-conductor cables intended for use in cable trays.
Part I of the guide discusses the effects of various aspects of the ac/dc interactions on the design and performance of dc schemes where the ac system appears as a high impedance at the ac/dc interface bus; i.e., low and very low short-circuit (short-circuit ratio [SCR]) conditions. AC systems having zero or inadequate mechanical rotational inertia, such as island schemes with no or with limited local generation, are also considered. Environmental, siting, and construction issues are not addressed. General issues, such as steady-state reactive compensation and ac and dc filter requirements, are not in the scope of this guide, but would be included in a complete study for a particular dc scheme design. In order to assist those not familiar with dc transmission and convertors, a brief description of basic rectifier and inverter operation is given in Annex A of Part I. Part II of this guide, which is bound together with Part I, considers how the ac/dc interaction phenomena described in Part I should be taken into account in the planning and the preliminary design of ac/dc systems having low or very low SCR values.
This standard covers handsets and headsets whose receive performance can be measured using standardized artificial ears, as defined in ITUT Recommendation P.57: 1993 and ANSI S3.36-1985. The standard also covers handsets and headsets whose transmit performance can be measured with the center of the transmitter sound port in front of the artificial mouth lip plane. Othere types of handsets or headsets, having transmitters whose sound ports fall behind the lip plane in normal use, are not covered… read more by this standard. However, the general methods described in this standard may be used as guidelines for testing such handsets or headsets. This standard covers measurements on four-wire handsets and headsets having separate transmit and receive speech paths. This standard also applies to three-wire handsets and headsets in which a common lead is shared between the transmit and receive circuitry. When handsets and headsets are connected to hybrid speech networks performing four-wire to two-wire conversion, their transmission performance may be measured using the methods of IEEE Std 269-1992, with due consideration given to the relevant transmitter positioning and receiver coupling issues discussed in this standard. read less
This recommended practice addresses the evaluation and selection of CASE tools supporting software engineering processes including project management processes, predevelopment processes, development processes, post development processes, and integral processes (see IEEE Std 1074-1991). It is not intended to address systems engineering, integrated software engineering environments, or general purpose tools such as spreadsheets or word processors. This recommended practice assumes that evaluation/… read more selection activities are initiated by a person or group with the authority to commit the resources necessary to perform the activities. It assumes that recommendations resulting from these activities are provided to the initiator and/or to some other decision maker external to the process. It does not address activities leading up to the evaluation/selection process initiation, nor activities following a decision recommendation, such as acquisition-related activities, or qualification activities such as use in pilot projects. This recommended practice assumes that its user understands the job the CASE tool is to perform and the environmental constraints that would affect the use of the CASE tool. It does not address process maturity, technological readiness, or implementation of CASE tools. The evaluation and selection processes recommended in this recommended practice are based upon the perspective of a CASE tool user. Thus, the evaluation and selection criteria address only program characteristics visible to the user, such as program inputs and outputs, program function, user interfaces, and documented external program interfaces. Not addressed are the aspects of the CASE tool's programs or the process by which they were developed. This recommended practice neither dictates nor advocates particular or specific development standards, design methods, methodologies, techniques, programming languages, or life cycle paradigms. The existence of this recommended practice should not be construed to prohibit additional efforts in the evaluation and selection processes. read less
This standard applies to cable-pulling lubricants (compounds) and the testing and analysis of their interaction with wire and cable. Cable-pulling lubricants are used to lower the friction on cables when they are installed (pulled) into conduits, ducts, or directionally bored holes. These lubricants and/or their residues are in direct contact with the cable exterior covering and may remain so for the life of the cable. Cablepulling lubricants should be compatible with the cable. They should not… read more interfere with the function of any component of the cable system that they contact. Compatibility of cable-pulling lubricants with cable coverings is the only subject of this standard. Other important performance criteria for cable-pulling lubricants, such as friction reduction, toxicity, combustibility, and so on, are not discussed. This standard uses accepted cable performance standards whenever possible. Relevant standards are cited in the text and listed in Clause 2 and Annex A. read less
This is a full-use standard, a revision of ISO/IEC 13213:1994; its scope reflects accumulated experience with the CSR architecture since it was first promulgated as a standard in 1991. In the intervening years, two bus standards, Scalable Coherent Interface (SCI), IEEE Std 1596-199x, and Serial Bus, IEEE Std 1394-1995, have been the source of most practical implementation experience. The revised scope of the CSR architecture is given below: a) The overall architectural framework partitions the… read more total available address space into equal spaces available to individual nodes. A node's address space is in turn partitioned into regions which have different usage models, e.g., memory space, private space for vendor uses, configuration ROM and an I/O space (units space) where transactions may have side effects; b) A minimal transaction set (read, write and lock requests and their associated completion responses) required for compliant bus standards. Bus bridges compliant with this architecture, whether in a homogeneous or heterogeneous environment, are also expected to transport this transaction set; c) Fundamental control and status registers (CSRs) are defined to provide a common infrastructure for all compliant buses. In some cases the details of the registers are entirely bus-dependent but the function is common to all compliant buses; d) Message request and response CSRs are specified to enable directed delivery or broadcast of messages to multiple nodes. The message format permits organizations or vendors to define the meaning of the data payload without the need for a centralized registry of all possible formats; and e) Configuration ROM provides self-descriptive data structures that permit nodes to uniformly characterize the device services available. This is critical for buses that permit live insertion and removal of nodes; each newly inserted node contains sufficient information for it to be uniquely identified and for the requisite device drivers to be loaded. Although the original CSR architecture anticipated widespread development of bridges between heterogeneous bus standards and a diversity of addressing modes, both fixed and variable, no such implementations have been made. As a consequence, the most significant changes in scope between the earlier CSR architecture and this standard are the adoption of a single, fixed addressing model and the removal of tutorial material pertaining to the design of bridges. read less
This is a full-use standard, a revision of ISO/IEC 13213:1994; its scope reflects accumulated experience with the CSR architecture since it was first promulgated as a standard in 1991. In the intervening years, two bus standards, Scalable Coherent Interface (SCI), IEEE Std 1596-199x, and Serial Bus, IEEE Std 1394-1995, have been the source of most practical implementation experience. The revised scope of the CSR architecture is given below: a) The overall architectural framework partitions the… read more total available address space into equal spaces available to individual nodes. A node's address space is in turn partitioned into regions which have different usage models, e.g., memory space, private space for vendor uses, configuration ROM and an I/O space (units space) where transactions may have side effects; b) A minimal transaction set (read, write and lock requests and their associated completion responses) required for compliant bus standards. Bus bridges compliant with this architecture, whether in a homogeneous or heterogeneous environment, are also expected to transport this transaction set; c) Fundamental control and status registers (CSRs) are defined to provide a common infrastructure for all compliant buses. In some cases the details of the registers are entirely bus-dependent but the function is common to all compliant buses; d) Message request and response CSRs are specified to enable directed delivery or broadcast of messages to multiple nodes. The message format permits organizations or vendors to define the meaning of the data payload without the need for a centralized registry of all possible formats; and e) Configuration ROM provides self-descriptive data structures that permit nodes to uniformly characterize the device services available. This is critical for buses that permit live insertion and removal of nodes; each newly inserted node contains sufficient information for it to be uniquely identified and for the requisite device drivers to be loaded. Although the original CSR architecture anticipated widespread development of bridges between heterogeneous bus standards and a diversity of addressing modes, both fixed and variable, no such implementations have been made. As a consequence, the most significant changes in scope between the earlier CSR architecture and this standard are the adoption of a single, fixed addressing model and the removal of tutorial material pertaining to the design of bridges. read less