When you buy a new PBX, you want it to be as resilient as possible, especially given that VoIP technology has a reputation for not quite being as bullet proof as older products.
Disaster prevention, overall reliability, disaster mitigation, and recovery capabilities and performance are therefore extremely important in any RFP you issue and the responding vendor should be required to provide information dealing with these issues and concerns as part of the bid proposal.
I have seen too many RFP templates that do an inadequate job of defining the enterprise's requirements. This tip should go a long way toward making vendors respond adequately by addressing their system reliability, disaster mitigation and recovery capabilities.
Some vendors have participated in laboratory testing of their products. If there has been independent testing of the vendor's product reliability, disaster and recovery capabilities, this information should be part of the bid proposal. If the vendor does not have the data or will not provide it, then the following points should be evaluated during a pilot operation of the system.
Selecting the vendor with the highest reliability is a key component of the consideration of the final proposing vendor. The fewer the hardware and software failures, the less frequently the enterprise has to exercise the recovery capabilities of the product. The following should be part of the RFP:
- What is the hardware MTBF and MTTR for the proposed system (not a boilerplate example)? Is the answer field experience or predicted by calculation and, if so, by what calculation method?
- What is the hardware MTBF and MTTR for the proposed IP phones and gateways? Is the answer field experience or predicted by calculation and, if so, by what calculation method?
- What has been the field experience reliability over the past two years of the software for the:
- IP phones?
- What is the anticipated availability (99.xxx%) of the proposed system combining both hardware and software?
The primary goal of the enterprise is to avoid any disasters. The vendor may have optional capabilities that can be acquired which will reduce or possibly prevent a disaster for the system operation. Consider the following as potential questions for the RFP:
- What features and capabilities does the proposed system have for preventing disasters (such as redundant components and fault-tolerant operation)?
- What happens to the calls in progress when the server is not reachable? Do they drop? Stay up? Can they hang up and initiate new calls? If so, with what features?
- Are the aforementioned features and capabilities integral parts of the system or are they optional?
- What are the vendor's recommendations for disaster prevention with the proposed systems?
- What additional solutions can the enterprise implement to reduce disasters?
Disaster mitigation and recovery features
Once a disaster occurs, the system has to return to normal operation. Getting it up and running acceptably is expected. The vendor may have mechanisms that will reduce/mitigate the disaster so that some operation can continue. The following questions should be part of the RFP:
About the author: