1、 AMERICAN NATIONAL STANDARD FOR TELECOMMUNICATIONS ATIS-0100012.2013 STANDARD OUTAGE CLASSIFICATION As a leading technology and solutions development organization, ATIS brings together the top global ICT companies to advance the industrys most-pressing business priorities. Through ATIS committees an
2、d 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 development lifecycle from design and innovatio
3、n 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 Partner for the 3rd Generation Partnership
4、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 information, visit . AMERICAN NATIONAL STANDARD
5、 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 Standards Review, substantial agreement h
6、as 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 towards their resolution. The use of America
7、n 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 standards. The American National Standards
8、 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 American National Standards Institute. Req
9、uests 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 National Standards Institute require that action
10、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 that is, the value in one category does not preclude
11、or exclude the use of a value in another category. Outage databases constructed using this concept can be perceived as having one field for Category 1 (What), two fields for Category 2 (Why-Primary and Why-Secondary), and one field for Category 3 (Who). The concept of decomposing the outage cause in
12、to categories facilitates the statistical analysis of outage data. The category values presented in this standard address the highest level of outage cause description with the broadest applicability across the industry. It is likely that individual companies or organizations may wish to provide mor
13、e in-depth outage cause descriptions to focus on their own individual needs. The standard presented here provides a basis and structure for doing so. The decomposition concept allows additional fields to be added if needed where more precision is desired in the description. For example, Category 1 (
14、What) could have an added field describing specific types of hardware and software elements that were the source of the outage. Such a level of description is beyond the scope of this standard, but the system described here provides a structure for such expansion of detail if desired. 4.3 Examples o
15、f Application The examples provided in Table 1 provide guidance on the application of the classification system to various outage scenarios. In particular, note should be made of scenarios involving acts of nature such as lightning or storms. It is often simplest to ascribe service outages arising f
16、rom such events exclusively to Acts of Nature. However, in many cases, a thorough outage cause analysis will often find that true responsibility for these outages lies elsewhere (e.g., with the service provider if proper precautions were not made, or with the vendor if the event was within the desig
17、n tolerance of the failed equipment); several scenarios in Table 1 address the differences in classification for such outages. ATIS-0100012.2013 5 Table 5: Examples of Application to Various Outage Scenarios Description Category 1 - What Category 2 - Why Category 3 - Who Primary Secondary DS3s faile
18、d due to a fiber cut caused by a private land owner who was digging and cut the fiber. Cable Damage Accident Public individual/organization Cable was accidentally cut by a construction contractor (working for the reporting service provider), although locates were done and were accurate. Cable Damage
19、 Accident Contractor of Reporter Loss of service was incurred by the reporting service provider when a leased cable was accidentally cut by the leasing service provider. Cable Damage Accident Other Service Provider Cable was cut when lightning struck a utility pole. Cable Damage External Environment
20、 Act of Nature Cable was cut by a contractor for a private firm. Service provider failed to process the cable locate request from the contractor. Cable Damage Procedure Violation Reporting Service Provider Cable was cut by a contractor installing a drainage pipe for a restaurant. No cable locate req
21、uest was made. Cable Damage Procedure Violation Public individual/organization Cable cut was caused by the county highway department which did not request a cable locate. Cable Damage Procedure Violation Government High call volume in anticipation of an approaching hurricane resulted in network cong
22、estion. Capacity Traffic/System Overload External Environment Customer Lightning strike exceeding the design tolerance of a receiver caused the failure of the receiver, which had to be replaced to restore service. Hardware Damage External Environment Act of Nature ATIS-0100012.2013 6 Description Cat
23、egory 1 - What Category 2 - Why Category 3 - Who Primary Secondary Lightning strike caused the failure of the receiver, which had to be replaced to restore service. The receiver was improperly grounded. Hardware Damage Procedure Violation Reporting Service Provider Lightning strike within the design
24、 tolerance of a receiver caused the failure of the receiver, which had to be replaced to restore service. Hardware Damage External Environment Vendor High winds caused loss of service by satellite dish. Wind strength was within the design tolerance of dish. Hardware Failure External Environment Vend
25、or High winds caused loss of service by satellite dish. Satellite dish was not properly maintained to secure it in high winds. Hardware Failure Procedure Violation Reporting Service Provider High winds caused loss of service by satellite dish. Wind strength was outside design tolerance of dish. Hard
26、ware Failure External Environment Act of Nature A loss of protect resulted from a faulty amp. The spare amp was replaced, but alarms did not clear and service was not restored. An investigation found that the spare on site was an out of box failure from the vendor. Hardware Failure Spare Vendor A lo
27、ss of protect resulted from a faulty amp. Service was restored when the amp was replaced. Hardware Failure Wear Reporting Service Provider Switch experienced a loss of commercial power. After transferring to standby generators, the cooling system failed to restart due to low voltage. Hardware Infras
28、tructure Support Power Failure Reporting Service Provider ATIS-0100012.2013 7 Description Category 1 - What Category 2 - Why Category 3 - Who Primary Secondary Translation error caused loss of calls. Translator did not consult documentation on how to do the work. Software Damage Procedure Violation
29、Reporting Service Provider An invalid pointer was added to an office retrofit tape, which caused trunk groups to experience failure. Software Design Accident Vendor Software error in card produced false overload condition. Software Design Accident Vendor An order request was submitted to disconnect
30、a single toll free number. The order was inadvertently processed incorrectly by order processing personnel, consequently disconnecting all toll free numbers associated with the customers account. Personnel were confused by a new layout screen for this procedure, which was not clearly documented. Sof
31、tware Design Documentation Vendor Traffic was lost as a result of corruption of a card that occurred while a vendor performed a database update. Software Failure Accident Vendor Newly constructed billboard interferes with microwave signal. Wireless Transmission Failure Accident Public individual/org
32、anization ATIS-0100012.2013 8 Annex A (informative) A Additional Levels of Classification and Comparison to FCC Outage Categories This section is strictly an example of how this guide compares to a set of cause codes that are currently in use by the United States FCC (US FCC). It is not intended to
33、be considered a part of the Standard Outage Classification guidelines. A.1 Additional Levels of Detail for What & Why In order to make a mapping between the standard set of what-why-who and the existing NORS outage categories, an additional classification level is provided for both the “what” and th
34、e “why”. The following two tables show the additional levels of detail. Table A.1: What - Secondary What - Secondary Description Underground Used with Cable to differentiate location. Aerial/Non-Buried Used with Cable to differentiate location. Backplane Used with Hardware to provide more detail. Ca
35、rd/Frame Mechanisms Used with Hardware to provide more detail. Memory Unit Used with Hardware to provide more detail. Peripheral Unit Used with Hardware to provide more detail. Processor Community Used with Hardware to provide more detail. Circuit Pack/Card Failure-Other Used with Hardware to provid
36、e more detail. Circuit Pack/Card Failure-Processor Used with Hardware to provide more detail. Passive Devices Used with Hardware to provide more detail. Self-Contained Device Used with Hardware to provide more detail. Shelf/Slot Failure Used with Hardware to provide more detail. Software Storage Med
37、ia Failure Used with Hardware to provide more detail. Battery Used with Hardware to provide more detail. Generator Used with Hardware to provide more detail. Power Alarms Used with Hardware to provide more detail. Power Equipment Used with Hardware or Capacity to provide more detail. Rectifier Used
38、with Hardware to provide more detail. Signaling Network Used with Capacity to provide location in network experiencing problem. ATIS-0100012.2013 9 Table A.2: Why - Tertiary Why Tertiary Description Un-located The “what” was not properly located which caused the outage. Digging Digging caused the ou
39、tage. Notification Lack of notification caused the outage. Accuracy Accuracy of location marking of cable caused the outage. Cable Shallow Depth at which cable is buried caused the outage. Fault Recovery Problems with fault recovery caused the outage (generally associated with software). Diagnostics
40、 Problems with diagnostics caused the outage (generally associated with firmware or software). Grounding Problems with grounding of the equipment caused the outage (generally associated with hardware design). Backplane / Pin Arrangement Problems with the backplane/pin arrangement caused the outage (
41、generally associated with hardware design). Card/Frame Mechanisms Problems with the card/frame mechanisms caused the outage (generally associated with hardware design). Office Data Problems with the office data caused the outage (generally associated with software design). Program Data Problems with
42、 the program data caused the outage (generally associated with software design). Defensive Checks Problems with the defensive checks caused the outage (generally associated with software design). Diversity Problems with diversity caused the outage. Animal Problems with animals caused the outage (gen
43、erally associated with external environment). Earthquake Problems with an earthquake caused the outage (generally associated with external environment). Fire Problems with fire caused the outage (generally associated with internal or external environment). Flood Problems with a flood caused the outa
44、ge (generally associated with external environment). Lightning/Transient Voltage Problems with lightning/transient voltage caused the outage (generally associated with external environment). Storm - Water/Ice Problems with a storm including water/ice caused the outage (generally associated with exte
45、rnal environment). Storm - Wind/Trees Problems with a storm including wind and/or trees caused the outage (generally associated with external environment). Vandalism/Theft Problems with vandalism or theft caused the outage (generally associated with external environment). Vehicular Accident Problems
46、 with a vehicular accident caused the outage (generally associated with external environment). Pressurization Problems with pressurization caused the outage (generally associated with internal environment). Dust Problems with pressurization caused the outage (generally associated with internal envir
47、onment). HVAC Problems with pressurization caused the outage (generally associated with internal environment). Fire Suppression Damage Problems with fire suppression damage caused the outage (generally associated with internal environment). Leak Problems with a leak caused the outage (generally asso
48、ciated with internal environment). ATIS-0100012.2013 10 Why Tertiary Description Breaker Tripped/Blown Fuses Problems with a tripped breaker or blown fuses caused the outage (generally associated with a power failure). Extended Commercial Power Failure Problems with an extended commercial power fail
49、ure caused the outage (generally associated with a power failure). Generator Failure Problems with a generator failure caused the outage (generally associated with a power failure). Maintenance/Testing Lack of routine maintenance or testing caused the outage (generally associated with a power failure). Power Surge Problems with a power surge caused the outage (generally associated with a power failure). Out-of-Date, Unusable, Impractical Used with Procedural Documentation problems to provide more detail. Unavailable/unclear/incomplete Used with Procedural Documentation problems to pr
