After covering NFV definitions and the benefits, let's also talk about how does it get deployed, what are the different options for that, and what are the capabilities required after choosing one or the other options? So, here, we have a point of view from Orange couple of years ago, nicely visualizing different, what is being called steps, but those are different deployment models. On one side, on the left it starts with vertically integrated, where the model is being consumed the same way where purchasing and operations is handling the same vertical integrated system, which now has a hypervisor, it does bring benefits of software upgrades. It allows to move in direction of automated, but does not decouple between multiple vendors and having all the different layers fully distributed network as some of the other steps. So, step number one here is where the NFV infrastructure is different from the VNFs on top of it; this acquires VNF onboarding effort. Step two here in the middle is, at that time with additional orchestration on top is what Orange deployed couple of years ago for business services. This has normal volume servers and switches with hypervisor, and then the third party VNFs on top of it orchestrated video orchestration layer, in this case, it was not represented here, but this is how it got deployed. Then, the further desegregation as it goes, is of course more desirable for the comm service provider to take advantage of the virtualization, transformation, also to introduce new vendors in the ecosystem and to decouple those previously vertical systems. This includes adding the NFV orchestration layer, also in the right layered ways, where it can also have generic VNF manager, and then it goes into fully distributed network, where the orchestration can depending on the requirements from the VNF, typically, it's somewhere in the VNF descriptors simplified, can decide where exactly to instantiate this type of functionality in the whole Telco Cloud distributed. So, going further to the right, requires way more studying and skills and help from the right partners that are willing to have this type of model implemented. It requires also very big changes in the procedures. So, this means what is here represented operational model needs to change. So, for managing silos to managing layers, is typically how it's set, and also the purchasing needs to change, because it's not the old model buying all from the same vendor. Now, it's being using IT equipment inside the carrier network with some of the IT virtualization vendors, and also it can have third party VNFs. For the customer facing services, also the sales procedures are changing, and required capabilities for all that here, we simplified those five models into the three ones. On one side, is vertical integrated by telecommunication equipment manufacturer. In the middle, is integrated platform with on-boarded VNFs, and on the right, is everything layered in multi vendor. So, required capabilities for that, there are some that fit into the baseline category of capabilities. This is to be convinced on the overall value of this type of transformations, be able to sort the hardware configurations and connectivity options for data plane, transcoding, eventually some of the hardware acceleration. Third, is to have software applications that are at some stage of readiness. Here, we call it cloud ready. So, this means that they're virtualized, they can scale up and down to a certain extent, but they don't have to be perfectly decoupled from the Cloud platform, decomposed, and so on. There needs to be skill of building additional data center capacity, or there needs to be such capacity in the already provided data centers. So, this is the baseline regardless of which deployment model is being used, and then the capabilities required for this vertical integrated model will typically come from the Telco equipment manufacturer who is providing this vertical integrated stack. They will help with financial and planning tools, sizing, characterization, data provided, and integrated into the current environments of IT and OSS/BSS. So, this is the easiest way to deploy a number of communication service providers after realizing what are all the capabilities at a given point in time decided to go with this type of model. So, the model where their platform is integrated, and we need to on-board the VNFs, is from the communication service providers or the appropriate partners who are willing to complement this type of model, requires additionally on top of those baselines, and basic financial tools, requires getting to the right balance between the separation and integration costs. These type of financial planning tools for revenue cost sizing is for multiple use cases on the shared infrastructure. Now, because of the VNF on-boarding effort on this platform, people start to become aware of the VNF on-boarding methodologies requirement for other common data model that is going to help in this type of effort start to experience more of the artifacts of the VNFs. So, starts asking for those to be resilience of what are the impairments in the Cloud Platform. Also, to be decomposed into the functionalities in software modules, start looking at multi-vendor orchestration with integration into the current IT versus BSS systems, need to figure out how to operationalize this multi-vendor ecosystem. At this point in time, this is already enough capabilities and the change requirement, it is really worth addressing organizational culture changes that are going to further this whole transformation, and make it successful in this case. So, for those that still want to go further and inside the platform itself, make it multi-vendor and layered, there is additionally required to make this balance between separation and integration costs in the platform, and also the TCO models will have to be built for the multi-vendor NFV infrastructure and now this multi-vendor NFV infrastructure needs to be integrated into existing systems and operarationalizing it also on the level of the multi-vendor. So, this is a slide that was created to help reflect on the required capabilities to get to the right planning and resourcing, especially to fit it in time on how the up-skilling or the partnering is going to go during this transformation. It's also for this planning on where to invest in concepts beyond skills, or where to partner with the right ecosystem vendors that are capable of bringing this type of pure play system integration, is typically what we're talking about bringing complementary business models to make this whole thing successful. This is also helping those that might not have this type of capabilities to realize faster, and still do what is vertical integrated model that can be done now, and is in terms of required capabilities much easier proposition to offer.
