Which Deployment Model is Right for You? Rip and Replace, OTT, or Network Edge Orchestration?
Author: Lars Nohling, Edgewater Networks
When legacy VoIP systems start wreaking havoc on your business, it’s time to take action and evaluate options for deployment methods. There’s no reason to become complacent with reduced call quality, dropped calls, and expensive truck rolls to fix the influx of issues. In the end, these every day headaches will lead to customer dissatisfaction and churn, plus degraded revenue streams.
We’re going to help you avoid that situation, by reviewing some deployment models that will get your systems in order:
Rip and Replace
For older enterprise systems, the rip and replace method may feel like the only option. If legacy technologies aren’t keeping up, the idea of tearing it all out and starting fresh seems like and easy choice. Of course when budgets are considered, doubts may begin.
This deployment model is by far the most costly way to modernize your systems. While it is a fool-proof method to control quality, you will have to sacrifice time for planning and implementing the systems. To pay for that and the system itself, you will most likely need to bury it into your customers’ monthly bill.
Rip and replace shouldn’t be done just because newer technology is “better.” There needs to be a business reason that acts as a springboard for the decision. If the systems are inhibiting business growth because they do not have the necessary integration capabilities, then there is a real reason to replace everything. On the other hand, if business can still be done, but new technology would help things flow more seamlessly, then this expensive method probably isn’t the best option.
Pros: Efficient – always works, come away with new technology, can be done without much downtime
Cons: Very expensive, not feasible to do every few years
Over the Top
Over the Top (OTT) is more of a patch then a true fix for operators’ and end-users’ issues. While this deployment method is certainly more affordable than rip and replace, there is no actual improvement to the system already in place.
As the name implies, OTT sits on top of the network and its components to improve system functionality. Unfortunately, because it is a topper, it can often cause more harm than good. Consider if dropped calls become an issue. Troubleshooting on multiple system layers can be a nightmare and create lengthy troubleshooting times especially since there won’t be any onsite diagnostic tools. Your team will be left wondering: is it the network, the phones, or the OTT switch?
While this is a more affordable option, you might be trading one issue for another.
Cons: Difficult to troubleshoot, lack of on site diagnostic tools, needs a well trained staff to manage issues
Network Edge Orchestration
Network Edge Orchestration is a cost efficient and fast solution if you need your technology to simply work better. If rip and replace isn’t an option, Network Edge might be your best bet for optimization.
Network Edge Orchestration uses Intelligent Edge Solutions to actively monitor, secure, and optimize service quality. From the data collected at the edge of the network, reports are sent to a cloud-based Service Control Center, where IT teams have a single point to provision, configure, and manage edge solutions.
This deployment can be preconfigured so that you have a plug and go capability, resulting in nearly no downtime. Plus, it’s affordable. With the option for a fully cloud-based solution, costly hardware is unnecessary. You can use your existing system, but use Network Edge Orchestration to make it better.
If there are lingering issues with legacy equipment, troubleshooting is a breeze. With constant monitoring, the Service Control Center provides insight to detect and resolve issues without a truck roll.
A Network Edge Orchestration deployment gives you the best of both worlds between rip and replace and OTT. It provides the flexibility of new equipment, with the cost savings of just improving your old systems.
Pros: Affordable, quick and easy, great for troubleshooting, can keep old equipment, doesn’t require a team to manage
Cons: Doesn’t replace legacy systems
There isn’t a one-deployment-model-fits-all for providers, so be sure to take the time and weigh the pros and cons for the needs of you and your customers.
One final thought to consider is the technology lifecycle. You should ask yourself which model would provide you with the most cost efficient, long-term benefits.
Looking for more information to help make your decision easier? Click here to read more on our blog about Network Edge Orchestration.