Network Reliability and Interoperability Council
2
Network Reliability and Interoperability Council
Gordon BarberMarch 14, 2003
Focus Group Committee Chairs
Cable: John Thrower (Cox Communications)
CLECs: Robert Smith (McLeod USA)
Equipment Manufacturers: Greg Garrett (Lucent)
IECs: Dante Hawkins (Sprint LD)
ILECs: Jim Sampson (Qwest)
Industry Services and Consulting:Maria Estefania (ATIS)Choa-Ming Liu (Telcordia)
Satellite: Bill McHargue (Hughes Network System)
Wireless: Rich Moczygemba (ATT Wireless)
3
Network Reliability and Interoperability Council
Gordon BarberMarch 14, 2003
DR/MA Committee Representation
62 Industry Representatives >1000 Years experience
13 Business Segments Service Providers, Network Operators, Equipment Providers,
Government, etc.
34 Companies/Government Entities 5K to 100K Employees Single State to Global Footprints New Entrants to Companies With Decades of Experience
4
Network Reliability and Interoperability Council
Gordon BarberMarch 14, 2003
Mission
Prepare and institute mechanisms for distributing Contact Information for telecommunications industry personnel essential to telecommunications services restoration
Report on the viability of past or present Mutual Aid Agreements and develop and report on any additional perspectives that may be appropriate to facilitate effective telecommunications restorations
Create Best Practices which focus on Business Continuity and Disaster Recovery
5
Network Reliability and Interoperability Council
Gordon BarberMarch 14, 2003
Deliverables
Mechanism for Contact Information for industry personnel to ensure effective communication during restoration (August 2002)
Usefulness of Mutual Aid Agreements and additional efforts necessary to facilitate service restoration (August 2002)
Best Practices for Business Continuity and Disaster Recovery (March 2003)
6
Network Reliability and Interoperability Council
Gordon BarberMarch 14, 2003
Summary of Statistics
>5000 Participant Hours in Working Meetings Developing Best Practices
36 Best Practice Recommendations carried over from NRIC V
68 New Best Practice Recommendations
7
Network Reliability and Interoperability Council
Gordon BarberMarch 14, 2003
Principles and Guidance in Disaster Recovery BPs
Practices already implemented Developed by industry consensus Best Practices are verified by a broader set of industry
members Sufficient rigor and deliberation Not all Best Practices are appropriate for all service providers Best Practices are dynamic and must be frequently reviewed,
updated, and refined Best Practices are totally ineffective unless implemented and
can never be implemented quickly enough
8
Network Reliability and Interoperability Council
Gordon BarberMarch 14, 2003
Format of Best Practice Recommendations
Business Continuity Emergency Preparedness
• Mitigation /Prevention• Preparedness
Disaster Recovery• Response• Recovery• Resumption• Restoration/Return
9
Network Reliability and Interoperability Council
Gordon BarberMarch 14, 2003
Best Practice or Recommendation
ILEC
CLEC
Wire
less
IEC
Equi
p. S
uppl
ier
Sate
llite
Cabl
e
ILEC
CLEC
Wire
less
IEC
Equi
p. S
uppl
ier
Sate
llite
Cabl
e
ILEC
CLEC
Wire
less
IEC
Equi
p. S
uppl
ier
Sate
llite
Cabl
e
ILEC
CLEC
Wire
less
IEC
Equi
p. S
uppl
ier
Sate
llite
Cabl
e
ILEC
CLEC
Wire
less
IEC
Equi
p. S
uppl
ier
Sate
llite
Cabl
e
ILEC
CLEC
Wire
less
IEC
Equi
p. S
uppl
ier
Sate
llite
Cabl
e
Service Providers, Network Operators and Equipment Suppliers should formally document their business continuity process. Key areas for consideration include: Plan Scope, Responsibility, Risk Assessment, Business Impact Analysis, Plan Testing, Training and Plan Maintenance. A template is provided on the NRIC website for assistance in this regard.
A successful Business Continuity Plan requires executive support and oversight. Service Providers, Network Operators and Equipment Suppliers should consider establishing an executive steering committee (composed of executive managers and business process owners) to provide guidance and direction to the planning team.
The Business Continuity Plan for Service Providers and Network Operators should address critical business processes (e.g., Call Completion, 911/Emergency Services, Provisioning,, Maintenance, etc.), support functions (IT, Sourcing, Logistics, Real Estate, etc.) and key business partners.
Emergency Preparedness Disaster Recovery
Mitigation/ Prevention Preparedness Response Recovery Resumption Restoration/Return
Business Continuity Template
10
Network Reliability and Interoperability Council
Gordon BarberMarch 14, 2003
Example of Best PracticesFG 1D: 6-6-1001
Service Providers, Network Operators and Equipment Suppliers should formally document their business continuity process
Key areas for consideration include: Plan Scope
Responsibility
Risk Assessment
Business Impact Analysis
Plan Testing
Training and Plan Maintenance
Network Reliability and Interoperability Council
11 Gordon BarberMarch 14, 2003
Example of Best PracticesFG 1D: 6-6-1030
Service Providers and Network Operators should consider entering into Mutual Aid agreements with partners best able to assist them in a disaster situation using the templates provided on the NRIC and NCS websites
URLs
NRIC: http://www.nric.org/meetings/meeting20020913.html
NCC: http://www.ncs.gov/ncc/main.html
12
Network Reliability and Interoperability Council
Gordon BarberMarch 14, 2003
Example Best PracticeFG 1D: 6-6-1045
Service Providers and Network Operators should consider when/where feasible maintaining sufficient hardware spares for critical elements to continue service after an incident without need to obtain spares from Equipment Suppliers
13
Network Reliability and Interoperability Council
Gordon BarberMarch 14, 2003
Example Best PracticeFG 1D: 6-6-1034
Disaster Recovery Exercises should include deployment of emergency mobile assets and should be conducted to train as many technicians and support personnel as possible in as realistic a manner as possible
14
Network Reliability and Interoperability Council
Gordon BarberMarch 14, 2003
Example Best PracticeFG 1D: 6-6-1020
Service Providers, Network Operators, and Equipment Suppliers should identify the need for Chemical, Biological, Radiological, Nuclear (CBRN) response via internal hazardous material response team or contracting with external HazMat response and remediation vendor to safely respond to aftermath of Weapons of Mass Destruction attack.
15
Network Reliability and Interoperability Council
Gordon BarberMarch 14, 2003
Example Best PracticeFG 1D: 6-6-1029
Service Providers and Network Operators should ensure that an adequate number of portable power generators are available consistent with the deployment of additional remote terminals.
16
Network Reliability and Interoperability Council
Gordon BarberMarch 14, 2003
Example of Best PracticeFG 1D: 6-5-0546
No single point of failure should exist in paths linking network elements deemed critical to the operation of a network (with this design, two or more simultaneous failures or errors must occur to cause a service interruption).
17
Network Reliability and Interoperability Council
Gordon BarberMarch 14, 2003
Example of Best PracticeFG 1D: 6-6-1057
Service Providers, Network Operators, and Equipment Suppliers should ensure deployment of Government Emergency Telecommunications Service (GETS) cards to appropriate Disaster Recovery personnel. Appropriate training and testing should be provided as necessary.
18
Network Reliability and Interoperability Council
Gordon BarberMarch 14, 2003
Example Best PracticeFG 1D: 6-6-1061
Service Providers, Network Operators, and Equipment Suppliers should ensure that Telecommunications Service Priority (TSP) records and data bases are reconciled annually.
19
Network Reliability and Interoperability Council
Gordon BarberMarch 14, 2003
RecommendationNRIC VI-1D-02
The federal government should support an outreach program to expand awareness and use of NCS priority services including Telecommunication Service Priority (TSP), Government Emergency Telecommunications Service (GETS), Wireless Priority Service (WPS) and Shared Resources HF Radio Network (SHARES) by State and Local Organizations, including Public Safety entities, as well as applicable private sector organizations.
20
Network Reliability and Interoperability Council
Gordon BarberMarch 14, 2003
Questions?
Top Related