First, creating a proper plan is an entire group effort; the planning should ultimately fall on each core function, i.e. engineering (technical facilities), IT (data), programming and operations (traffic, billing, sales).
Each group should document its respective functions, infrastructure requirements (i.e. networking, applications, data files) personnel and other needs, in as much detail as possible; this will form the basis for establishing a plan.
Lessons learned from past events, whether good or bad, can be extremely valuable. Many companies will routinely perform root cause analysis (RCA) when something goes wrong, which can be a powerful tool when it comes to predicting possible future problems.
Here are some items to consider:
Data storage — When/how often is data backed-up? Where do the back-ups reside? How is the back-up verified? Who are the personnel responsible for managing back-ups? Is data backed-up at sufficient intervals as to not disrupt the business operation should a failure occur? How will data get restored and who is responsible? Are network servers available offsite? How is the data accessed from the remote location? Since stored data plays such a large role in any business, you should always treat the location where the servers are located as a data center.
Back-up power systems — Have you determined the maximum run time that the studio(s), transmitter(s) will operate on back-up power? Are the back-up systems tested under load routinely? Are they under a current maintenance contract? Are the generator(s) sized adequately for the application? Is the fuel supply adequate and filled-up? If generators are diesel, has the fuel been tested and polished if needed? Are network servers and other critical equipment powered from back-up battery systems? Are the batteries routinely tested and/or changed? Is the battery back-up properly sized for the application? Have you run a scheduled disaster scenario to see how the system operates?
HVAC systems — Is there an alternate method of cooling/heating critical equipment? Is there a list of and a plan to shut down non-essential equipment?
Microwave radio systems — Is there a back-up method to transport data? If the station operates multiple hop sites, have you evaluated the impact of losing a donor site? Are these systems tied to back-up power? In the case of multiple T1 systems, what other services are affected by a loss of equipment? How do you control equipment at the remote site(s)?
Transmitter sites — Is there an alternate method to deliver programming to the site? Is there an alternate method to control the site? Is there a sufficient level of monitoring to detect smoke, fire, water, etc.? Are back-up transmitter systems in place and operational? Are all antenna switching systems routinely tested? Is there a sufficient level of monitoring of transmission line (VSWR) and other antenna parameters? Are proper fail safes in place and tested?
Studios — Is there a reciprocal plan in place with other stations to support back-up operations in the event of a total studio loss? Can the back-up studio be connected to the transmitter site remotely? If audio servers are out of commission, how will programming occur?
Personnel — Have you identified essential personnel? Does each employee understand his role and responsibility in the event of an emergency? Does the company have a plan to house personnel if travel is restricted?
Other considerations — Be aware of potential hazards such as flood zones, earthquake areas, proximity to chemical/nuclear plants, high lightning areas, fire prone zones, high wind areas, etc. Much of the information you will need to identify hazards specific to a particular location can be found at www.fema.org and other websites. While it is nearly impossible to predict those unforeseen situations with 100 percent accuracy, the implementation and follow-through of a written plan before a disaster strikes is essential.
McNamara is president of Applied Wireless, Cape Coral, FL.