1、 AMERICAN NATIONAL STANDARD FOR TELECOMMUNICATIONS ATIS-0600317.1993(R2013) Uniform Language for Accessing Power Plants Human-Machine Language As a leading technology and solutions development organization, ATIS brings together the top global ICT companies to advance the industrys most-pressing busi
2、ness priorities. Through ATIS committees and forums, nearly 200 companies address cloud services, device solutions, emergency services, M2M communications, cyber security, ehealth, network evolution, quality of service, billing support, operations, and more. These priorities follow a fast-track deve
3、lopment lifecycle from design and innovation through solutions that include standards, specifications, requirements, business use cases, software toolkits, and interoperability testing. ATIS is accredited by the American National Standards Institute (ANSI). ATIS is the North American Organizational
4、Partner for the 3rd Generation Partnership Project (3GPP), a founding Partner of oneM2M, a member and major U.S. contributor to the International Telecommunication Union (ITU) Radio and Telecommunications sectors, and a member of the Inter-American Telecommunication Commission (CITEL). For more info
5、rmation, visit. AMERICAN NATIONAL STANDARD Approval of an American National Standard requires review by ANSI that the requirements for due process, consensus, and other criteria for approval have been met by the standards developer. Consensus is established when, in the judgment of the ANSI Board of
6、 Standards Review, substantial agreement has been reached by directly and materially affected interests. Substantial agreement means much more than a simple majority, but not necessarily unanimity. Consensus requires that all views and objections be considered, and that a concerted effort be made to
7、wards their resolution. The use of American National Standards is completely voluntary; their existence does not in any respect preclude anyone, whether he has approved the standards or not, from manufacturing, marketing, purchasing, or using products, processes, or procedures not conforming to the
8、standards. The American National Standards Institute does not develop standards and will in no circumstances give an interpretation of any American National Standard. Moreover, no person shall have the right or authority to issue an interpretation of an American National Standard in the name of the
9、American National Standards Institute. Requests for interpretations should be addressed to the secretariat or sponsor whose name appears on the title page of this standard. CAUTION NOTICE: This American National Standard may be revised or withdrawn at any time. The procedures of the American Nationa
10、l Standards Institute require that action be taken periodically to reaffirm, revise, or withdraw this standard. Purchasers of American National Standards may receive current information on all standards by calling or writing the American National Standards Institute. Notice of Disclaimer their exist
11、ence does not in any respect preclude anyone, whether he has approvedthe standards or not, from manufacturing, marketing, purchasing, or usingproducts, processes, or procedures not conforming to the standards.The American National Standards Institute does not develop standards andwill in no circumst
12、ances give an interpretation of any American NationalStandard. Moreover, no person shall have the right or authority to issue aninterpretation of an American National Standard in the name of the AmericanNational Standards Institute. Requests for interpretations should be ad-dressed to the secretaria
13、t or sponsor whose name appears on the title pageof this standard.CAUTION NOTICE: This American National Standard may be revised orwithdrawn at any time. The procedures of the American National StandardsInstitute require that action be taken periodically to reaffirm, revise, or withdraw this standar
14、d. Purchasers of American National Standards mayreceive current information on all standards by calling or writing the AmericanNational Standards Institute.Published byAmerican National Standards Institute11 West 42nd Street, New York, New York 10036Copyright 1994 by Alliance for Telecommunications
15、Industry SolutionsAll rights reserved.No part of this publication may be reproduced in anyform, in an electronic retrieval system or otherwise,without prior written permission of the publisher.Printed in the United States of AmericaAPS2.5C494/68iContentsPageForewordii1 Scope, purpose, and applicatio
16、n12 Normative references23 Definitions 24 Functional description for power system monitoring and control .45 Language elements.76 Command language definition .257 Implementation .338 Menus.39Tables1 Access commands 72 Site attributes and mnemonics83 AC inverter plant attributes and mnemonics .84 AC
17、plant attributes and mnemonics 95 Battery string attributes and mnemonics.106 Cell attributes and mnemonics117 Converter plant attributes and mnemonics .128 DC converter attributes and mnemonics.139 DC plant attributes and mnemonics 1410 Fault detection attributes and mnemonics 1611 Feeder attribute
18、s and mnemonics.1712 Generator attributes and mnemonics1813 Inverter attributes and mnemonics2014 Rectifier attributes and mnemonics.2115 Ring plant attributes and mnemonics2216 UPS attributes and mnemonics.2317 Special objects, descriptions, and mnemonics .2518 Character set.34AnnexesA Sample meter
19、 reading report .44B BIbliography45iiForeword (This foreword is not part of American National Standard T1.317-1993.)The project to develop a standard for a command language for telecommu-nications power systems monitors and controllers was established underCommittee T1 Telecommunications, T1E1 Techn
20、ical Subcommittee,T1E1.6 Working Group.Changes in the telecommunications industry have created a need for moredetailed monitoring and controlling power systems. Fewer trained person-nel are expected to be available to oversee an increasing number oftelecommunications power systems. However, at the t
21、ime this standardsproject was initiated, the general perception was that users were confront-ed with too many specific languages and procedures for communicatingwith power systems monitors and controllers. This resulted in excessiveeffort for software development, higher training costs, and increase
22、d possi-bility of errors in mechanized data acquisition, control, and monitoring ofpower systems. This proposed standard addressed the need for a uniformcommand language structure that may be employed throughout the indus-try by both users and manufacturers of equipment.No single standard exists tha
23、t specifically addresses communications betweenmachines, humans, and telecommunications power plants. This standard willbuild on the variety of language and protocol structures in existence.Many years of experience and a large body of technical knowledge existsconcerning the manual operation and lim
24、ited alarm capabilities of present-generation telecommunications power systems. However, subject matterexperts appropriate to this standards project needed a knowledge basecovering not only power systems but also data acquisition systems, controlsystems, operation support systems, and the data commu
25、nications tech-nology to tie it all together. Therefore, in addition to establishing a WorkingGroup under T1E1, a formal liaison was established with the T1M1Technical Subcommittee.There are two annexes in this standard. Both annexes are informative andare not considered a part of this standard.Sugg
26、estions for the improvement of this standard are welcome. They maybe addressed to the Alliance for Telecommunications Industry Solutions,1200 G Street, NW, Suite 500, Washington, DC 20005.This standard was processed and approved for submittal to ANSI byAccredited Standards Committee T1 on Telecommun
27、ications. Committeeapproval of the standard does not imply that all members voted for itsapproval. At the time it approved this standard, the T1 committee had thefollowing members:A. K. Reilly, ChairmanG. H. Peterson, Vice-ChairmanO. J. Gusella, Jr., SecretaryF. J. Fiederlein, Senior EditorOrganizat
28、ion Represented Name of RepresentativeEXCHANGE CARRIERSAmeritech Services, Inc. Laurence A. YoungJames Orme (Alt.)Bell Atlantic Corporation John W. SeazholtzRoger Nucho (Alt.)iiiBellcore.D. S. JordanJames C. Staats (Alt.)BellSouth Telecommunications, Inc. Leonard Strickland, Jr.William J. McNamara,
29、III (Alt.)Centel Corporation Bruce BeckerCincinnati Bell Telephone Kevin R. SullivanScott M. Kalinoski (Alt.)Exchange Carriers Standards AssociationGregory L. TheusJames L. Eitel (Alt.)GTE Telephone Operations .Gregory L. TheusRichard L. Cochran (Alt.)National Telephone Cooperative Association .Jose
30、ph M. FlaniganNYNEX .James F. BaskinJim Papadopoulos (Alt.)Pacific Bell Sal R. TesoroPuerto Rico Telephone Company.Alberto E. MoralesSegundo Ruiz (Alt.)Southwestern Bell Corporation Joseph MendozaC. C. Bailey (Alt.)Sprint Local Telecommunications Division.Robert P. McCabeHarold L. Fuller (Alt.)US Te
31、lephone Association (USTA) Dennis ByrnePaul K. Hart (Alt.)US WESTJames L. EitelJames Dahl (Alt.)INTEREXCHANGE CARRIERSAmerican Mobile Satellite Corporation .Michael K. WardWilliam Garner (Alt.)AT human-interpretable responses from thePSMC resulting from recognizable human-initiated commands; and hum
32、an-interpretable responses from thePSMC resulting from nonrecognizedhuman-initiated inputs, e.g., improperlyformed commands or typing errors.Future standards will address: interfaces between PSMCs andOperations System (OS)-like systems thatperform systems management functions butare not located with
33、in a Telecommuni-cations Management Network (TMN) envi-ronment; interfaces between power systems-ori-ented network elements and OSs that arelocated within a TMN environment.1.2 Limitation of scopeThis standard does not define either the algo-rithms or means of calculations. Such itemsas resolution,
34、number of decimal places, andmeans of deriving averages are not within thescope of this standard.It is not the intent of this standard that allaspects of this type of system be specifiedand standardized.This standard is intended to meet the needsof those who engineer, install, operate, main-tain, an
35、d provision power systems. At thistime it may not fully comply with TMN stan-dards in their present state of development.Future revisions are expected to further inte-grate standardization of TMN requirementswith power systems access.This standard does not inhibit innovation andthe provision of func
36、tions, commands, andresponse structures which are in addition tothose defined by this standard. This standard1American National Standardfor Telecommunications Uniform Language for Accessing Power Plants Human-Machine LanguageAMERICAN NATIONAL STANDARD ANSI T1.317-1993or mouse movement, or both, and
37、clicking. Norestrictions are placed on means to makemenu item selection under category B.2 Normative referencesThe following standards contain provisionswhich, through reference in this text, consti-tute provisions of this American NationalStandard. At the time of publication, the edi-tions indicate
38、d were valid. All standards aresubject to revision, and parties to agreementsbased on this American National Standard areencouraged to investigate the possibility ofapplying the most recent editions of the stan-dards indicated below.ANSI T1.210-1993, Telecommunications Operations, administration, ma
39、intenance, andprovisioning (OAM reduced training costs; increased interoperability among abroad range of power systems monitoringand control equipment.1.4 ApplicationThis standard defines language elements thatsupport management functions concerning themonitoring and controlling of telecommunica-tio
40、ns power systems. Specifically, this stan-dard defines the command/response interac-tions between human users and PSMCs.1.5 ComplianceTo address the disparate capabilities of termi-nals and workstations, there are two cate-gories of compliance with this standard.Compliance with this standard may be
41、accom-plished under either or both categories.Category A compliance allows all require-ments of this standard to be met using anASCII text terminal which implements thecharacter set found in table 18 of this stan-dard. To comply within this category, the usermust be able to select menu items by ente
42、ringthe standard alphanumeric characters foundin table 18 of this standard.Category B compliance allows all require-ments of this standard to be met using intelli-gent workstations employing diverse means ofmenu item selection; including cursor controlANSI T1.317-199321)Available from the American N
43、ational Standards Institute, 11 West 42nd Street, New York, NY 10036.ANSI T1.317-19933.6 entry: A record, transaction, orattribute of a managed object entered into thePSMC.3.7 event: An occurrence that changes thestatus/state of an object. This status changemay be persistent or temporary, thus allow
44、ingfor surveillance, monitoring, and performancemeasurement functionality, etc.3.8 fault management: A set of functionsthat enables the detection, isolation and cor-rection of abnormal operation of power sys-tems and their environment.3.9 group: An assignment of one or moremanaged objects or attribu
45、tes to a commonrelationship for purposes of gathering orreporting data. Also, it may contain one ormore managed objects or attributes, one ormore groups, or both.3.10 managed object: The telecommuni-cations management, including power sys-tems management, view of a resource withinthe telecommunicati
46、ons environment that maybe managed through the use of OAM An abstract object such as a circuit; A support object such as an “AlarmReport”.3.11 managed object class: An identifiedfamily of managed objects that share certaincharacteristics.3.12 managed object instance: A particu-lar managed object of
47、a managed object class.3.13 meter reading: The present valueread or derived by the PSMC as it measuresthe values of attributes of managed objectsthat are being monitored.3.14 object: An “object” for the purposesof this standard, is defined by a set ofattributes, a set of sub-objects, or both. Anobje
48、ct is defined only when it is useful inorder to support one or more power systemsmanagement functions. An object may includean equipment unit or units, e.g., a rectifier ora dc power plant. An object may include a setof data, e.g., an alarm record or event record.An object may be the superset of oth
49、erobjects, e.g., the alarm record for a dc powersystem may be the superset of the alarmrecords of each of the power plants and otherentities within the dc power system.3.15 peak values: The highest/lowestvalue acquired by the PSMC on a given ana-log channel. These are defined as the HighPeak and Low Peak.3.16 performance management: A set offunctions to evaluate and report upon thebehavior of power systems performance. Thisincludes present and statistical readings ofvarious voltages, currents, and other perfor-mance measurements.3.17 point: A Physical connection to the
