As we get close to wrapping up the report, we will consolidate the observations and analysis so far and combine them with further requirements that we are hearing from our conversations with leading CSPs. Based on our combined analysis, SDxCentral believes that key MANO requirements for success in 2017 include:
- Lifecycle service management—Simplistic VNFM implementations are insufficient, as are barebones NFVOs. CSPs are clear that their livelihood depends on the roll-out, sale and management of network services (e.g. vCPE, VPN etc). If the MANO systems are not able to model and manage the concept of services, they are of little use to the CSPs. MANO solutions that succeed will need to ensure a robust implementation of service management, from design and provisioning to ongoing management, to deprovisioning of services.
- OSS/BSS awareness and ease-of-integration—CSPs are not expecting MANO to displace OSS/BSS solutions they’ve spent years and millions of dollars building and maintaining. However, they do need the MANO systems to integrate smoothly into their OSS/BSS systems and to be able to take commands from OSS systems and provide information back into these systems. Without the ability to order and bill, an NFV roll-out is unlikely to be a success.
- Hybrid/brownfield deployment support and management—Physical network functions (PNF) and VNF hybrid management is an issue today, along with license management across different versions of network functions. MANO solutions will have to resolve how to seamlessly integrate across deployments that may mix both PNF and VNFs. CSPs also need to explore how workflows accomodating a wide variety of EMS systems, some legacy, some modern can be managed. This, in addition to managing the complexity of different licensing schemes across vendors, with legacy pricing models different from NFV models: per instances, per unit of capacity or bandwidth, per subscriber etc creates yet more headaches.