Best Practices Guidelines
- Proven through actual implementation – more than “just a good idea”
- Address classes of problems (rather than one time issues)
- A single concept should be captured in each practice (one thought, one practice)
- Should not endorse specific commercial documents, products or services
- Developed through rigorous deliberation and expert consensus
- Confirmed by a broad set of stakeholders
- Should not be assumed to be applicable in all situations or to all industry types
- Should not imply mandatory implementation
Recommendation
Communications organizations should evaluate and implement those Best Practices which they deem appropriate. These organizations should institutionalize the review of Best Practices as part of their planning processes and assess on a periodic basis how implementing selected Best Practices might improve the proficiency and reliability of their operations.
Best Practice Format
The format of the Best Practices should all be in the form of: "__________________ should ___________________".
1st blank “Who” : consists of the implementer (i.e., Service Provider, Network Operator, Equipment Supplier, Property Manager, Government)
2nd blank “What” : consists of the Best Practice. The Best Practice may include the use of a modifier (e.g., consider, in order to, etc.).
Best Practices Numbering Format
For existing CSRIC Best Practices: Each Best Practice has a unique number that follows the numbering format: X - Y - Z # # # X = the current, or most recent CSRIC Council (e.g., 7 in 2004-2005) Y = the Council in which the Best Practice was last edited Z = 0-4 for Network Reliability and Interoperability = 1 for Disaster Recovery and Mutual Aid = 3 for Public Safety = 5 for Physical Security = 8 for Cyber Security # # # = any digits, where every Best Practice has a unique Z # # #
Critical Best Practices include those which met any of the following standards:
- Significantly reduce the potential for a catastrophic failure of critical communications network infrastructure and/or services (e.g., telecommunication, public safety, energy sector, financial, etc.).
- Significantly reduce the duration or severity of critical communications outages.
- Materially limit and/or contain the geographic area affected by a communications failure from cascading to other or adjacent geographic areas.
- Affect critical communications networks (e.g., SS7) for all network configurations, independent of size.
- Preserve priority communications for key personnel involved in disaster response and recovery.
Communications experts joined together under the ATIS Network Reliability Steering Committee (NRSC) to prepare industry checklists to help ensure business continuity during significant events that could critically impact service:
Disaster Roaming Guide and ResourceThis document provides a guide that Wireless Service Providers can use as a checklist of procedures and available resources to facilitate roaming during disasters.
NRSC Pandemic ChecklistIn August 2009, the ATIS NRSC released a Pandemic Planning Checklist. This document includes 56 voluntary Best Practices that continue the U.S. communications industry’s nearly 20-year history of collaboration among experts to promote the health of the nation’s public networks.
NRSC Hurricane ChecklistIn the wake of Hurricane Katrina in 2005, the NRSC developed a list of proactive steps that could be taken by a telecommunications service provider to prepare for a hurricane. The checklist was also submitted as part of the FCC proceeding requesting comments on the Hurricane Katrina Panel.