Because businesses today depend so much on communications capabilities, maintaining quality communications is a must for successful telecom environment management.
This means, there needs to be a network contingency plan in place that offers the telecom environment quick, alternate connectivity whenever it is needed—ensuring business continuity if ever disaster or other connectivity-impairing events should occur.
To assist businesses with ensuring their telecom environment is in line with this need, an AOTMP whitepaper, "Disaster Recovery Planning: Key consideration for developing a network contingency plan," offers several considerations for getting around challenges when developing a disaster recovery plan.
The whitepaper notes that when it comes to building a disaster recovery plan, it is important for businesses to understand the value in each of their services and what the impact would be if that service were missing.
Next, the whitepaper advises businesses to determine what the "weakest links" in their services are--which components of service delivery are most likely to fail and if they do, will they cripple connectivity?
Also, it's important for businesses to recognize what system components are critical and focus on the possible inability to access connectivity from the subscriber premises.
If this should occur, the whitepaper notes, "Back up data centers and redundant call center providers can be commissioned to provide data connectivity and accept inbound voice traffic if the organization does not maintain multiple corporate offices."
For more, check out www.aotmp.com to see how AOTMP helps businesses achieve excellence in enterprise telecom environment management.
Telecom Environment Management Best Practices for Inventory and Cost Control
AOTMP Releases Study Detailing CFO Vs. CIO Approach to IT and Telecom Management
TEM 2008: Learn Best Practices and Get Telecom Certification
Stefania Viscusi is an established writer and avid reader. To see more of her articles, please visit Stefania Viscusi’s columnist page.