July 19, 2013 Via Email Jeffery Goldthorp Chief, Communications
Contents
1. Naik maid ga but a NA oa bot eet ee A ANG A NAN ANAN identified ete o Other E Ade vlr dida dimos of citar Do dotussdicsecotenmadorihe caropinta failures alls duplexeccsstent Diversity_Indicater Lack of Diversity Contributed to or Caused the Outage Determine whether lack of diversity contributed to or caused the outage Fhatis determine Ater aga feeders ta eserad af T Best Practices related to diversity are discussed in any of the Best Practice fields or if the lack of diversity is listed as a root cause or contributing factor to the outage then the diversity checkbox must alsethis field should be eheeked marked Yes In general determine whether engineering standards for diversity are being followed Malicious Activity Indicate whether you believe malicious activity might be involved in outage Malicious aetivity could be product ofterrorists TfF there is malieieus activity the The form asks for some explanation of why the nputter beHevesyou believe the activity is malicious or what is suspicious about the activity Malicious activity could be the product of terrorists A1se the Spins ren teed Name and Type of Equipment that Failed Provide the vendor name and the specific equipment inclu2. Reportable Provide threshold that was crossed that determined that this outage was reportable If more than one threshold was crossed please choose the primary reason Pick from the scroll down menu one of the following Wireline 900 000 User Minutes Wireless 900 000 User Minutes Cable Telephony 900 000 User Minutes MSC E911 Blocked Calls 1350 DS3s minutes DS3 Simplex Greater than 5 Days 557 MTP Messages Airport Other Special Facilities Military nuclear etc Paging Satellite Other VoIP E911 VoIP 900 000 User Minutes Outage Duration Provide the total elapsed time hours and minutes from the commencement of the outage as provided in the preceding data fields until restoration of fullservice Full service restoration means includes the restoration of servieeall services to all customers impacted by the outage net only restoration_of the service s which may have madeeven if the restoral is over temporary facilities If the customers locations are destroyed such as by a hurricane flood tornado wildfire the duration continues until the reporting carrier is capable of again providing service to those locations If an outage repertable to the FCC is ongoing at the time the Final Report is filed report the outage duration as the total time between the commencement of the outage and the time the Final Report is filed
3. TET lid id ence Le tice Kaka A ven restesuse a preferredtotheuse of unknown WhenclassHications provided do notmatehroot NG ee ANA ee ee ANIMOS canbe ae aria oreo cad HIPS MNT Le oe Hes eo eect ot peres Lecce heel cem om service provider taining available but not attended training attended but L from service provider trainine avadlable but not attended trainine attended but 1 L4 entified ete i dote teeter te e soe tan es Wes Other Simplex Conditi Jalanan taa Team anehe aa steht SONET ri 22 still TP ones ee tee one Pa a aapa ana eee e o Service affecting Failure of one side of a duplexed system such SONEF Contributing Factors Scroll down the menu and piel choose the contributing factors that fit best fit if applicable Contributing factors are problems or causes that are closely linked to the outage Often if a contributing factor were was addressed beforehand the outage could be have b
4. Date Outage Determined Reportable Date on which a company determines that an outage has occurred and meets one or more of the reportable thresholds This field is voluntary Local Time Outage Determined Reportable 24 HR Clock Time at which a company determines that an outage has occurred and meets one or more of the reportable This field is voluntary Explanation of Outage Duration for incidents with partial restoration times Describe the stages of restoration if different blocks of users were restored at different times Often times significant blocks of users may be restored to service prior to full restoration of service If this is the case provide information on the number of users in theeach block restored to service and the elapsed time to partial restoration should be provided so that an accurate assessment of the outage impact may be made In addition it is important to report when some services e g E911 are restored if different than other services In addition for outages that last unusually long time an explanation should be provided in this field Inside Building Indicator Indicate whether the outage occurred inside a building owned leased or otherwise controlled by the reporting entity Gutaces hatccenton fictiies otis Sher bus are consigerse building A building is a structure that is temperature controlled E911 Outage Location Effects For
5. 2 1200 Street NW 202 628 6380 Suite 500 F 202 393 5453 Washington 20005 W www atis org ATIS Board Officers Chair Kristin Rinne AT amp T First Vice Chair Stephen Bye Sprint Second Vice Chair Thomas Sawanobori Verizon Treasurer Joseph Hanley Telephone and Data Systems President amp Chief Executive Officer Susan M Miller ATIS Vice President of Finance amp Operations William J Klein ATIS July 19 2013 Via Email Jeffery Goldthorp Chief Communications Systems Analysis Division Public Safety and Homeland Security Bureau Federal Communications Commission 445 12th Street SW Washington DC 20554 Re ATIS NRSC Recommendations for NORS Help File Dear Jeff Attached are recommendations from the ATIS Network Reliability Steering Committee NRSC for changes to the Network Outage Reporting System NORS Help File a clean and marked up version are attached These changes align the text with what is currently contained in the NORS and associated NORS User Manual Version 7 In addition to the recommended changes there are three observations noted as comments in the attached e The first comment pertains to whether there should be a VoIP service provider bullet added to the list of company types under of Entity Reporting Disruption section If the answer to this question is yes the NRSC recommends that this be addressed in the NORS production system and NORS
6. Seesddecthe aumber o peesieasb opecettea O SZ eiceuib Eabvereadteeted bs Eve eutage Provide the number of previously operating 0535 that were affected by the outage and were out of service for 30 or more minutes regardless of the services carried on the DS3s or the utilization of DS3s DS3s restored to service in fewer than 30 minutes should not be recorded in the box for the number of DS3s For example if an outage initially took 576 DS3s out of service but 384 were restored to service in less than 30 minutes and only 192 were out of service for 30 minutes or longer the number of affected DS3s should be recorded as 192 If some failed DS3s were initially knocked out of service but restored in fewer than 30 minutes the rapid restoration of those DS3s can be noted in the Description of Incident field but they should not counted in the field for number of DS3s affected Count any failed STS3c as 3 0535 a failed STS12c as 12 DS3s etc Lost SS7 MTP Messages In cases of an SS7 outage and where an SS7 provider cannot directly estimate the number of blocked calls provide the number of real time lost SS7 MTP messages or the number SS7 MTP messages carried on a historical basis Historic carried 557 MTP messages shallshould be for the same day s of the week and the same time s of day as the outage and for a time interval The information should not be older than 90 days preceding the onset of the o
7. User Manual The second comment notes that the Mobile Switching Center MSC Failed appears only in the online reporting system but is not documented in the Help File or NORS User Manual The NRSC recommendis that this section heading be added to the Help File and the User Manual The third comment recommends updating the NORS User Manual to reflect the changes proposed by the NRSC to the State section of the Help File which has been renamed as Geographic Area Affected State Territory Commonwealth or the District of Columbia to reflect what is currently displayed on the online reporting system Letter to J Goldthorp July 19 2013 Page 2 Thank you for your consideration of these items Please contact me if additional information is necessary or if you have any questions Sincerely e Z 2 nd Thomas Goode General Counsel cc John Healy Associate Division Chief Cybersecurity and Communications Reliability Division Report Choose type of report Initial Draft or Final An Initial Report on an outage is due no later than 72 hours after the reporting entity discovered that the outage was reportable and the Final Report on an outage is due no later than 30 days after the reporting entity discovered that the outage was reportable A Final Report is due in 30 days even in the event that the outage has not yet been cleared by that time The Initial Report shall contain all available pertinent infor
8. direct cause is the event action or procedure that triggered the outage In Section 7 of the NORS User Manual there is a complete description of each of the direct causes For example a cable cut could be the triggering event or direct cause of an outage whose root cause is lack of diversity Root Cause The root cause is the underlying reason why the outage occurred or why the outage was reportable Scroll down the menu and choose the root cause that best fits Root Cause is the key problem which once identified and corrected will prevent the same or a similar problem from recurring With today s technology two or more problems may be closely linked and require detailed investigation However in any single incident there should be only one primary cause the Root Cause In Section 7 of the NORS User Manual there is a complete description of each root cause For example a cable cut improper marking could be the triggering event or direct cause but the real cause root cause may be lack of diversity Contributing Factors Scroll down the menu and choose the contributing factors that best fit if applicable Contributing factors are problems or causes that are closely linked to the outage Often if a contributing factor was addressed beforehand the outage could have been prevented or the effect of the outage would have been reduced or eliminated The form allows two contributing factors for which there are complete descriptions in Section 7
9. non E911 outages leave this field blank For E911 outages select from the scroll down menu one of the following ALI Location Only Affected for wireline carriers when location of the caller could not be provided but the call could be routed to a PSAP Phase 2 Only Affected for wireless outages when Phase 2 location information could not be provided but the call could be routed to a PSAP Phase 1 and Phase 2 Only Affected for wireless outages when neither Phase 1 nor Phase 2 could be provided but the call could be routed to a PSAP More than Location Affected for wireline and wireless carriers when the call could not be routed to the appropriate PSAP Failure Occurred in Another Company s Network Check box if failure occurred in another company s network Effects of the Outage Services Affected Cable Telephony Check the box if cable telephony users were affected Wireless other than paging Check the box if wireless users were affected VoIP Check the box if VoIP users were affected E911 Check the box if E911 service or some aspect of E911 service was affected Paging Check the box if paging users were affected by the outage Satellite Check the box if satellite facilities were affected by the outage Signaling SS7 Check the box if SS7 service was affected by the outage Wireline Check the box if wireline users were affected by the outage This includes wh
10. person E mail Address Provide the e mail address of the secondary contact person iieaseockepectedble
11. the outage inputter used when he she applied for a UserID This field is automatically filled in Outage reports must be filed with the FCC by any cable communications provider wireless service provider Voice over Internet Protocol VoIP service provider satellite operator SS7 provider wireline communications provider paging provider E911 service provider or facility owner and on any facilities which it owns operates or leases that experiences an outage meetinsthat meets the reporting thresholds as defined in Part 4 of the Commission s Rules and Regulations en any faeilitieswhich it owns eperaetes ecdensos Type of Entity Reporting Disruption Lists the type entity your company is type This entry is automatically filled with the information taken from the Notification Companies are not able to change the entry on the Initial Report regardless of what appears on the Notification The possible entries were e Wireline carrier e Wireless carrier e Cable telephony provider e Paging provider e Satellite provider 557 network provider 911 service provider e Facility owner or operator Comment RG1 NRSC Comment Should SS there be a VoIP service provider bullet added to this list If so this needs to be addressed in the NORS production system and NORS User Manual Date of Incident Provide the month day and year at the commencement of the outage The expected format is mm d
12. F Root Cause The root cause is the underlying reason why the outage occurred or why the outage was reportable Scroll down the menu and the root cause that best fits best Root Cause is the key problem which once identified and correctedweuld will prevent the same a similar problem from recurring fx With today s technology two or more problems may be closely linked and require detailed investigation However in any single incident there should be only one primary eauses cause the Root Cause In the AppendixSection 7 of NORS User Manual there is complete description of each efthe root eauses cause For example a cable cut is eftenimproper marking could be the triggering event or direct cause but the real cause er root cause may be lack of diversity te A BA KAKAK dco plas cessat Ineffecti 3 Hed eene ulting ota i an ha ease ee esos External Failure id serge sist Sale cee bette ose tee Power Failire hai eat ERRAR ARMAR p ete Fire arene SU ie Da
13. For outages affecting more than one community it is important to describe actual communities affected Include CLLIs if applicable Description of Incident Provide a narrative that describes the sequence of events leading up to the incident the steps taken to try and resolve the incident once it had occurred and the action s that finally resolved the incident This is for the reader to better understand what happened Include any factors that may have contributed to the duration of the incident quick fix actions that may have resolved or at least mitigated the immediate problem but were not the final long term solution and any other contributing factors The description should be sufficiently detailed to allow the reader to reach the same conclusions as the writer as to the Direct Cause and Root Cause of the incident The maximum number of characters that will be saved in this field is 5 000 and that may be reduced due to the way words break at the end of a line in the field Additional text may be referenced here and placed in the remarks field Description of the Cause s of the Outage Provide a text description of all causes of the outage This text should be in the inputter s own words and should not use the words in the pull down menus for Direct Cause or Root Cause Direct Cause The direct cause is the immediate event that results in an outage Scroll down the menu and choose the direct cause that is the most accurate The
14. NXX XXXX That is 201 444 5656 would mean that the area code or NPA is 201 the NNX is 444 and the line number is 5656 Extension Provide the extension number in format XXXX U S Postal Service Address Provide the address of the secondary contact person E mail Address Provide the e mail address of the secondary contact person Choose type of report Initial Draft or Final An Initial Reports are due within 2 days of the on an outage Final Reports are duewithin 30 days of is due no later than 72 hours after the reporting entity discovered that the outage frem whenwas reportable and the Final Report on an outage started is due no later than 30 days after the reporting entity discovered that the outage was reportable A Final Report is due in 30 days even in the event that the outage has not yet been cleared by that time The Initial Report shall contain all available pertinent information then available the outage and shall be submitted in good faith The Final Report shall contain all pertinent information on the outage including any information that was not contained in or that has changed from that provided in the Initial Report An Initial Report is not required if VoIP is the only service affected Name of Reporting Entity Lists the name of the company filing the outage report which This Beld is automatically filled in is the name of the company thatsame used by
15. P messages carried on a historical basis Historic carried SS7 MTP messages should be for the same day s of the week and the same time s of day as the outage The information should not be older than 90 days preceding onset of the outage If the outage does not affect an 557 network please leave this field blank Mobile Switching Center MSC Failed Comment RG2 NRSC Comment The MSC Mod section appears only in NORS but not the NORS User Manual or the Help File Recommended adding this section heading Geographic Area Affected State Territory Commonwealth or the District of Columbia Comment RG3 NRSC Comment The heading of this section needs to be updated NORS User Manual as well Choose the primary state from the scroll down menu affected by the outage All 50 states along with the District of Columbia and Puerto Rico are listed Outages affecting major parts of more than one state should be listed as Multi State Finally if an outage occurred outside the fifty states the District of Columbia or Puerto Rico please choose Outside the 50 States City Provide the primary city affected Please do NOT enter the state in this box Enter the state in the state box More Complete Description of Geographical Area of Outage Provide a more complete description of the geographical area of the outage In particular for Multi State outages it is important to list the states affected
16. Reason Reportable Provide threshold that was crossed that determined that this outage was reportable If more than one threshold was crossed please choose the primary reason Pick from the scroll down menu one of the following Wireline 900 000 User Minutes Wireless 900 000 User Minutes Cable Telephony 900 000 User Minutes MSC E911 Blocked Calls 1350 DS3s minutes DS3 Simplex Greater than 5 Days SS7 MTP Messages Airport Other Special Facilities Military nuclear etc Paging Satellite Other VoIP E911 VoIP 900 000 User Minutes Outage Duration Provide the total elapsed time hours and minutes from the commencement of the outage as provided in the preceding data fields until restoration of fullservice Full service restoration includes the restoration of all services to all customers impacted by the outage even if the restoral is over temporary facilities If the customers locations are destroyed such as by a hurricane flood tornado or wildfire the duration continues until the reporting carrier is capable of again providing service to those locations If an outage is ongoing at the time the Final Report is filed report the outage duration as the total time between the commencement of the outage and the time the Final Report is filed Date Outage Determined Reportable Date on which a company determines that an outage has occurred and meets one or more of the reportable thresholds This
17. actices that might have prevented the Outage reduced its effects Provide a deseriptionthe number s of the Best Practices that could have prevented the outage reduced its effects The Network Reliability and Interoperability Council NRIC and Communications Security Reliability and Interoperability Council CSRIC has have developed a list of Best Practices They can be accessed via swvwnrie org or https www fcc gov nors outage bestpractice BestPractice cfm You can find relevant Best Practices by using keywords Alternatively Best Practices can also be sourced from the ATIS Best Practices website http www atis org bestpractices Best Practices used to mitigate diminish effects of the Outage Provide a deseriptien of the number s and also possibly descriptions of most important Best Practices that were actually used to mitigatelessen the effects of the outage These chosen Best praetieesPractices helped shorten the outage reduced the restoration times prevented the outage from affecting more customers and or reduced the effects on customers e g ensured that E911 was not affected If none were used please leave blank Best Practices can be sourced from https www fcc gov nors outage bestpractice BestPractice cfm or the ATIS Best Practices website http www atis org bestpractices and frem or Analysis of Best Practices Provide an evaluation of the relevance applicability and usef
18. alls reported should be 3 times carried load The number of blocked calls if known must be filled out even if it is not the trigger for an outage being reportable Real Time Historic Check Box Check whether the number of Blocked Calls came from real time data or was based on historic loads carried the same day s of the week and the same time s of day as the outage DS3s Provide the number of previously operating DS3s that were affected by the outage and were out of service for 30 or more minutes regardless of the services carried on the 0535 or the utilization of the DS3s DS3s restored to service in fewer than 30 minutes should not be recorded in the box for the number of DS3s For example if an outage initially took 576 DS3s out of service but 384 were restored to service in less than 30 minutes and only 192 were out of service for 30 minutes or longer the number of affected DS3s should be recorded as 192 If some failed DS3s were initially knocked out of service but restored in fewer than 30 minutes the rapid restoration of those DS3s can be noted in the Description of Incident field but they should not counted in the field for number of 0535 affected Count any failed STS3c as 3 DS3s a failed STS12c as 12 DS3s etc Lost SS7 MTP Messages In cases of an SS7 outage and where an SS7 provider cannot directly estimate the number of blocked calls provide the number of real time lost SS7 MTP messages or the number SS7 MT
19. cable Description of Incident Provide a narrative whiehthat describes the sequence of events leading up to the incident the steps taken to try and resolve the incident once it had occurred and the action s whiehthat finally breughtresolution teresolved the incident This is for the reader to better understand what happened Include any factors whiehthat may have contributed to the duration of the incident quick fix actions whiehthat may have resolved or at least mitigated the immediate problem but were not the final long term solution and any other contributing factors whieh may aid the readerin better understandine the incident The description should be sufficiently detailed to allow readerin conjunction with other information provided inthe report to reach the same conclusions as the writer as to the Direct Cause and Root Cause of the incident The maximum number of characters that will be saved in this field is 5 000 and that may be reduced due to the way words break at the end of a line in the field Additional text may be referenced here and in remarks teld _ Description of Cause s of the Outage Provide a text description of all the causes of the outage This text should be in the inputter s own words e eutage inputter and should not neeessarily use the words eentained in pull down menus for Direct Cause or Root Cause Direct Cause The direct cause is the immediate event
20. d by the outage and the number of administrative numbers potentially affected If this outage did not affect wireline users please leave this blank Assigned numbers are defined as telephone numbers working in Public Switched Telephone Network under an agreement such as a contract or tariff at the request of specific end users or customers for their use and include DID numbers This excludes numbers that are not yet working but have a service order pending Administrative numbers are defined as the telephone numbers used by communications providers to perform internal administrative or operational functions necessary to maintain reasonable quality of service standards Wireless Users Provide the number of potentially affected wireless users In determining the number of users potentially affected by a failure of a switch a concentration ratio of 8 shall be applied If this outage did not affect wireless users please leave this blank VoIP Users Provide the number of potentially affected VoIP users If this outage did not affect VoiP users please leave this blank Paging Users Provide the number of assigned telephone numbers for those paging networks in which each individual user is assigned a telephone number If this outage did not affect paging users please leave this blank Cable Telephony Users Provide the number of assigned telephone numbers If this outage did not affect cable telephony users please l
21. d yyyy NORS automatically inserts today s date but you can change that by first deleting the entire date then re entering the correct date Local Time Incident Began 24 hr clock Provide the local time at the location of the outage not the reporting location of commencement of the outage 24 hour clock That is for 1 00 PM you should use 1300 The format should be nnnn thatis do not use a colon Aeeeptable nputs weuld be 800 0800 2300 ete Fhis this number should be between 90000 and 2359492359 In most cases both the physical location of the outage and the majority of the effects e the eutage are in the same time zone However some outages have wide ranging impacts and at times the greatest customer impaetthat may not be at the physical location of the outage Fer undersea cables such as a cut undersea cable In that case please provide the time at the elesest end of the undersea cable closest to the US Detailed explanations willbe provided in the Initial or Fina Report the local time of the physical outage You should include more detailed explanations in the Initial or Final Report Time Zone Pick from the scroll down menu one of the following e Alaskan Atlantic e Central e Eastern Greenwich Mean Time GMT Guam e Hawaii Aleutian e Mountain Other e Pacific Puerto Rico is in the Atlantic Time zone Other should be used for some place like American Samoa
22. ding software release if applicable involved in the outage For example if a relay in a power plant fails that subsequently causes switch to go out of service due to lack of power then report the make and model of the relay not the power plant or switch Specific Part of the Network Involved Provide the part of the network involved with the incident Examples are local switch tandem switch signaling network central office power plant digital cross connect system outside plant cable ALI database etc Method s Used to Restore Service Provide a complete chronological narrative of the methods used to restore service both quick fix and final Seret Gros see to eestor aioe R Telecommunications Service Priority Indicator Indicate whether TSP was used involved during service restoration Steps Taken to Prevent Reoccurrence Provide the pal Rd taken and to be taken to reoccurrence Fhese steps could beat and throtehon pety tate Typically the corrective actions are identified through a Root Cause of the incident _and steps for prevention be at both this location and throughout the network s if appropriate If a time frame for implementation exists it should be provided If no further action is required or planned the service d should 50 indicate EE Applicable Best Pr
23. eave this blank Satellite Users Provide the number of satellite users affected if known Number Affected Blocked Calls Provide the number of blocked calls If no calls were blocked please leave the field blank or put 0 down If blocked call information is available in only one direction for interoffice facilities which handle traffic in both directions total number of blocked calls shall be estimated as twice the number of blocked calls determined for the available direction If real time information is not available providers may provide data for the same day s of the week and the same time s of day as the outage covering a time interval not older than 90 days preceding the onset of the outage in an effort to estimate blocked calls In this case the number of blocked calls reported should be 3 times the historic carried load If for whatever reason real time and historic carried call load data are unavailable to the provider even after a detailed investigation the provider must estimate the carried call load based on data obtained in the time interval between the repair of the outage and the due date for the Final Report this data must cover the same day of the week the same time of day and the same duration as the outage Justification that such data accurately estimates the traffic that would have been carried at the time of the outage must be available on request In this case the estimate of the number of blocked c
24. een prevented or the effect of the outage would have been reduced or eliminated The form allows two contributing factors for which there are complete descriptions in Section 7 of the NORS User Manual NI iiic nite Fire d d a aan sab bapan eo Insufficient Data Fail ieation if lid id a eet TAA ON es Nn itis usually still possible to determine probable cause bebes Tue nes o Bee teh soot ibe Seb E o tnadequate site specifie power contingenes plans UR oor o from service provider training available but not attended training attended but inadeeuate or out et datecteazaiaccadequatebutinsefhielentapplieauenellased jode bone Mac bcc icio EE SO Denescssne cocco doccia tbls bot ed eee ben adeaua Or out er d
25. ether intraLATA or interLATA service was affected Special Facilities Airport Government etc Check the box if some special facility lost telecommunication service Other please specify Fill in any other services affected Number of Potentially Affected Wireline Users Provide the sum of the number of assigned telephone numbers potentially affected by the outage and the number of administrative numbers potentially affected If this outage did not affect wireline users please leave this blank Assigned numbers are defined as the telephone numbers working in the Public Switched Telephone Network under an agreement such as a contract or tariff at the request of specific end users or customers for their use and include DID numbers This excludes numbers that are not yet working but have a service order pending Administrative numbers are defined as telephone numbers used communications providers to perform internal administrative or operational functions necessary to maintain reasonable quality of service standards Wireless Users Provide the number of potentially affected wireless users did atak area users please leave this blank In determining the number of users potentially affected by a failure of a switch a concentration ratio of 8 shall be applied If this outage did not affect wireless users please leave this blank VoIP U
26. field is voluntary Local Time Outage Determined Reportable 24 HR Clock Time at which a company determines that an outage has occurred and meets one or more of the reportable This field is voluntary Explanation of Outage Duration for incidents with partial restoration times Describe the stages of restoration if different blocks of users were restored at different times Often times significant blocks of users may be restored to service prior to full restoration of service If this is the case provide information on the number of users in each block restored to service and the elapsed time to partial so that an accurate assessment of the outage impact may be made In addition it is important to report when some services e g E911 are restored if different than other services In addition for outages that last an unusually long time an explanation should be provided in this field Inside Building Indicator Indicate whether the outage occurred inside a building owned leased or otherwise controlled by the reporting entity A building is a structure that is temperature controlled E911 Outage Location Effects For non E911 outages leave this field blank For E911 outages select from the scroll down menu one of the following ALI Location Only Affected for wireline carriers when location of the caller could not be provided but the call could be routed to a PSAP Phase 2 Only Affected for wireless outages when Phase 2
27. location information could not be provided but the call could be routed to a PSAP Phase 1 and Phase 2 Only Affected for wireless outages when neither Phase 1 nor Phase 2 could be provided but the call could be routed to a PSAP More than Location Affected for wireline and wireless carriers when the call could not be routed to the appropriate PSAP Failure Occurred in Another Company s Network Check the box if the failure occurred in another company s network Effects of the Outage Services Affected Cable Telephony Check the box if cable telephony users were affected Wireless other than paging Check the box if wireless users were affected VoIP Check the box if VoIP users were affected E911 Check the box if E911 service or some aspect of E911 service was affected Paging Check the box if paging users were affected by the outage Satellite Check the box if satellite facilities were affected by the outage Signaling SS7 Check the box if SS7 service was affected by the outage Wireline Check the box if wireline users were affected by the outage This includes whether intraLATA or interLATA service was affected Special Facilities Airport Government etc Check the box if some special facility lost telecommunication service Other please specify Fill in any other services affected Number of Potentially Affected Wireline Users Provide the sum of the number of assigned telephone numbers potentially affecte
28. mation on the outage and shall be submitted in good faith The Final Report shall contain all pertinent information on the outage including any information that was not contained in or that has changed from that provided in the Initial Report An Initial Report is not required if VoIP is the only service affected Name of Reporting Entity Lists the name of the company filing the outage report which is the same used by the outage inputter when he she applied for a UserID This field is automatically filled in Outage reports must be filed with the FCC by any cable communications provider wireless service provider Voice over Internet Protocol VoIP service provider satellite operator SS7 provider wireline communications provider paging provider E911 service provider or facility owner and on any facilities which it owns operates or leases that experiences an outage that meets the reporting thresholds as defined in Part 4 of the Commission s Rules and Regulations Type of Entity Reporting Disruption Lists company type This entry is automatically filled with the information taken from the Notification Companies are not able to change the entry on the Initial Report regardless of what appears on the Notification The possible entries were e Wireline carrier e Wireless carrier e Cable telephony provider e Paging provider e Satellite provider 557 network provider e E911 service provider e Facility owner or operator Commen
29. nsuf clenteriiedae emwhecedeoteause ccesiL asdeeinvestieatton A reot enue bepress te cesses shoe es Tee ane eel seaside de eet tel soot eause approximate matehas preferred te the use of other dnt ae aga a banana aa E epe phase e plate A KRESEK ge eaaa an ababe aaa heel cem hardware procedures load shedding plans ete _ cud uis sor id Medea pote ee D om service provider taining available but not attended taining attended but icient training Training not available from yendor trainine net available from service provideriraining available but not attended training attended but inad er out of date training adequate butinsuffieient applieatien fellewed 1 entified ete o TR PERR abl nedele Gther TOME Ben esdeeauteedaes F adture eccone side eiandaplexedosetenmoseehaveat ras ones ecce ei Pa e eee e o Service affecting Failure of one side of a duplexed system such SONE
30. of the NORS User Manual Diversity_Indicater Lack of Diversity Contributed to or Caused the Outage Determine whether lack of diversity contributed to or caused the outage If Best Practices related to diversity are discussed in any of the Best Practice fields or if the lack of diversity is listed as a root cause or contributing factor to the outage then this field should be marked Yes In general determine whether engineering standards for diversity are being followed Malicious Activity Indicate whether you believe that malicious activity might be involved in outage The form asks for some explanation of why you believe the activity is malicious or what is suspicious about the activity Malicious activity could be the product of terrorists Name and Type of Equipment that Failed Provide the vendor name and the specific equipment including software release if applicable involved in the outage For example if a relay in a power plant fails that subsequently causes switch to go out of service due to lack of power then report the make and model of the relay not the power plant or switch Specific Part of the Network Involved Provide the part of the network involved with the incident Examples are local switch tandem switch signaling network central office power plant digital cross connect system outside plant cable ALI database etc Method s Used to Restore Service Provide a complete chronological narrative of
31. s of the outage These chosen Best Practices helped shorten the outage reduced the restoration times prevented the outage from affecting more customers and or reduced the effects on customers e g ensured that E911 was not affected If none were used please leave blank Best Practices can be sourced from https www fcc gov nors outage bestpractice BestPractice cfm or http www atis org bestpractices Analysis of Best Practices Provide an evaluation of the relevance applicability and usefulness of the current Best Practices for the outage If a new Best Practice is needed or an existing Best Practice needs to be modified please indicate Remarks Provide any additional information that you believe is relevant but did not fit anyplace else on the form Primary Contact Person Provide the full name of the primary contact person Phone Number Provide the phone number of the primary contact person in the format NPA NXX XXXX That is 201 444 5656 would mean that the area code or NPA is 201 the NNX is 444 and the line number is 5656 Extension Provide the extension number if used in format XXXX U S Postal Service Address Provide the address of the primary contact person E mail Address Provide the e mail address of the primary contact person Secondary Contact Person Provide full name of the secondary contact person Phone Number Provide the phone number of the secondary contact person in the format NPA
32. same day s of the week and the same time s of day as the outage and fercovering a time interval not older than 90 days preceding the onset of the outage in an effort to estimate blocked calls wheneverdtis not possible to obtain realtime bloeked eall eounts In this case the number of blocked calls reported should be 3 times the historic carried load In situationswhere If for whatever reason real time and historic carried call load data are unavailable to the provider even after a detailed investigation the provider must determineestimate the carried call load based on data obtained in the time interval between the ensetrepair of the outage and the due date for the amp naLrepestFinal Report this data must cover the same day of the week the same time of day and the same duration as the outage Justification that such data accurately estimates the traffic that would have been carried at the time of the outage had the eutage not eeeurred must be available on request In this case the estimate of the number of blocked calls reported should be 3 times carried load The number of blocked calls sheuld if known must be filled out even if it is not the trigger for an outage being reportable Real Time Historic Check Box Check eff whether number of blecked callsBlocked Calls came from real time data was based on historic loads carried leads the same day s of the week and the same time s of day as the outage DS3s
33. sers Provide the number of potentially affected VoIP users If this outage did not affect VoiP users please leave this blank Paging Users Provide the number of assigned telephone numbers for those paging networks in which each individual user is assigned a telephone number If this outage did not affect paging users please leave this blank pls aaa V ina quia aed Public Lea aaa endi yan Cable Telephony Users Provide number of assigned telephone numbers If ttiis outage did not affect cable telephony users please leave this blank e dediae eee e Publiecwiehed 3 E i e e epeo een eos teins for thence en M seecoane batbueseacserdec ordecpencdine Satellite Users Provide the number of satellite users affected if known Number Affected Blocked Calls Provide the number of blocked calls If no calls were blocked please leave the field blank or put 0 down Fer If blocked call information is available in only one direction for interoffice facilities which handle traffic in both directions and ferwhich blecked call information is _available in one direction only the total number of blocked calls shall be estimated as twice the number of blocked calls determined for the available direction Providers If real time information is not available providers may use histerie earried ealldeadprovide data for the
34. t RG1 NRSC Comment Should C CC MC there be a VoIP service provider bullet added to this list If so this needs to be addressed in the NORS production system and NORS User Manual Date of Incident Provide the month day and year at the commencement of the outage The expected format is mm dd yyyy NORS automatically inserts today s date but you can change that by first deleting the entire date then re entering the correct date Local Time Incident Began 24 hr clock Provide the local time at the location of the outage not the reporting location of commencement of the outage 24 hour clock That is for 1 00 PM you should use 1300 The format should be nnnn do not use a colon this number should be between 0000 and 2359 In most cases both the physical location of the outage and the majority of the effects are in the same time zone However some outages have wide ranging impacts that may not be at the physical location of the outage such as a cut undersea cable In that case please provide the time at the end of the undersea cable closest to the US or the local time of the physical outage You should include more detailed explanations in the Initial or Final Report Time Zone Pick from the scroll down menu one of the following e Alaskan e Atlantic e Central e Eastern Greenwich Mean Time GMT Guam Hawaii Aleutian Mountain e Other e Pacific Puerto Rico is in the Atlantic Time zone
35. that results in an outage Scroll down the menu and piekchoose the direct cause that fits bestis the most accurate The direct cause is the event action or procedure that triggered the outage In the AppendixSection 7 of NORS User Manual there is a complete description of each of the direct causes For Formatted Font color Red example a cable cut is often could be triggering event or direct cause butthe realcause orof an outage whose root cause may be is lack of diversity 1 gt one si less le poincfai z e A i ae d sudieaectandbslisace aate corpeneated External Failure id soso Power AA ANA nda p gear lagan esed acento baH oeenn adan Hre eeheehe a Eu ee A eec cue oe oe eese etate ceto eee directly related entra ice equipment fire nen flame moldering 2 Fail TOES lid id cuneate ilies anapa eed cose deer ee aces elas Seaton bee oes net cata tes i
36. the methods used to restore service both quick fix and final Telecommunications Service Priority TSP Indicator Indicate whether TSP was involved during service restoration Steps Taken to Prevent Reoccurrence Provide the steps already taken and to be taken to prevent reoccurrence Typically the corrective actions are identified through a Root Cause Analysis of the incident and the steps for prevention can be at both this location and throughout the network s if appropriate If a time frame for implementation exists it should be provided If no further action is required or planned the service provider should so indicate Applicable Best Practices that might have prevented the Outage or reduced its effects Provide the number s of the Best Practices that could have prevented the outage or reduced its effects The Network Reliability and Interoperability Council NRIC and Communications Security Reliability and Interoperability Council CSRIC have developed a list of Best Practices They can be accessed via https www fcc gov nors outage bestpractice BestPractice cfm You can find relevant Best Practices by using keywords Alternatively Best Practices can also be sourced from the ATIS Best Practices website http www atis org bestpractices Best Practices used to diminish effects of the Outage Provide the number s and also possibly descriptions of the most important Best Practices that were actually used to lessen the effect
37. ulness of the current Best Practices for the outage If a new Best Practice is needed or an existing Best Practice needs to be modified please indicate this Also the following speeial eharaeters Tblank may notbeusedin gt z a preven hao ce om hang a kah anan EME DA NENGA hh Remarks Provide any additional information that you believe is relevant but that did not fit anyplace else on the form Primary Contact Person Provide the full name of the primary contact person Phone Number Provide the phone number of the primary contact person in the format That is 201 444 5656 would mean that the area code or NPA is 201 the NNX is 444 and the line number is 5656 Extension Provide extension number if used in format nannX XXX U S Postal Service Address Provide the address of the primary contact person E mail Address Provide the e mail address of the primary contact person Secondary Contact Person Provide the full name of the secondary contact person Phone Number Provide the phone number of the secondary contact person in the format xagNPA nnnNXX nnnnXXXX That is 201 444 5656 would mean that the area code or NPA is 201 the NNX is 444 and the line number is 5656 Extension Provide the extension number in format U S Postal Service Address Provide the address of the secondary contact
38. utage If the outage does not affect an SS7 network please leave this field blank Mobile Switching Center MSC Failed Comment RG2 NRSC Comment The MSC E section appears only in NORS but not the NORS User Manual or the Help File Recommended adding this section heading Formatted Font color Red Geographic Area Affected State Territory Commonwealth or the District of Columbia Comment RG3 NRSC Comment The posu heading of this section needs to be updated in the NORS User Manual as well Choose the primary state from the scroll down menu affected by the outage 50 states along with the District of Columbia and Puerto Rico are listed In addition eutages Outages affecting major parts of more than one state should be listed as mult state Multi State Finally if an outage occurred outside the fifty states the District of Columbia or Puerto Rico please choose Outside the 50 States Provide primary city affected Please do NOT enter state in this box Enter state in the state box More Complete Description of Geographical Area of Outage Provide a more complete description of the geographical area of the outage In particular for widespreadMulti State outages affeetine several states it is important to list the states affected For outages affecting more than one community it is important to describe actual communities affected Include CLLIs if appli
Download Pdf Manuals
Related Search