So there are small factors, which we need to consider when we go to cloud. So there will be some slides you'll see which you have seen, but I want to give a different perspective of each slide. So going to the next. So everything, every, every time we move to cloud, we have seen that what we expect from the moving to cloud. So moving to cloud is one reason is everybody's moving. Why not me? So we decide to move that way. We also look at cost saving alternatives because some conference provided that yes, you move to our cloud and you will save 50%, 60% of your cost. Then also you can reduce internal it stuff and hand over everything to cloud provider or transferring security risks. You don't have to maintain any internal security person. Just give it to somebody else who can manage this well to achieve scalability, a big factor and pay for use model.
So scalability and pay per use. They go hand in hand. Although we have seen all of this, what we have not considered is how we can reuse our existing resources, internal staff in a different way. So if you see this chart, there is left side, which is the traditional way of operations of it department. So we support business services, applications, not out majority of time is done in maintaining of service, maintenance of infrastructures, data center, server rooms, networks, et cetera. What if we decide to inverse this pyramid and more help on business services to buy helping them in application supporting, of course the platform management will be reduced because you'll be outsourcing to the cloud environment and reduce the infrastructure to bare minimum, because that is not your business day to day business of your company. So look at the enterprise strategy, look at what the enterprise business is.
Is it your business fine? Then the left side is for you. If it is not your business, then you should try to go to the right side of the pyramid or the right side of the cha slide, because that will give more time for your it resources to develop the business, to reach the business goals and not having to spend your time in maintaining servers, which is not the business for you. This lights is dejavu. We have 10, we have seen 10 times. This is not my invention, but I just wanted to see what is your cloud adoption here from this, as you go from left to right, you'll see that the role of cloud provider increases role of internal stuff decreases. Does that mean we can get rid of all it resources or it and power we have, and we rely on cloud. It may happen in some cases, but as we go from left to right, we also lose granular control of each layer we are discussing here.
And that means we cannot easily separate the security. We cannot easily manage what the cost controls are. So let's see further how this is impacting in our daily life. So you are, you are transferring to cloud provider. The provider is more responsible. So gradual access we saw it's not there. Each application needs integration. And if we transfer everything into one cloud or we transfer it to different clouds, security will have to be enhanced than what we have today. Because today we, if we are not in cloud, on-premise you just integrate across the words and much security is not required. So that is with limited security cost allocation becomes complex because we sign up to the cloud, which is used by 10 to 10, 15 different business units. And then the cost allocation across business units could also become complex to calculate now, oh, so how a cloud can be made as advantage.
So we have to reduce resource investment in routine support activities. We have to focus on what business deliverables are. Business strategies invest in resources for enterprise development, rather than it development or the infrastructure development alone. And in transfer day to day operations to the provider who are experts in doing that and who have business to do that, let's visit a common business stakeholder relation diagram. This is a chart which, which can high level explain how the bus different business entities work together. There are partners, there are core corporate services. There are customers in the whole business of any product setting company, for example. So it starts from innovation production. Then it goes to the market presence. So in that there is supply chain. There are distributors, there are selling reselling agents. There are customers who are involved then from marketplaces. Somebody does the market survey to give feedback to the management and in the innovation team.
So that is another area where support and survey support service comes into picture and market survey providers do the survey to analyze how far the success was. And then the feedback is given back to the innovation production you need so that they can make improvements. They can adopt the requirements from the market and then deliver something else. So this is a cycle in this. You see, there are multiple colors and each color represents different business unit or business entity, which operate in different way. There is a business owner. There are stakeholders in each of them, which are independent. The only common criteria could be the, the core management who wants to see the whole picture from all locations. Now, is this a complex thing though? It's, it's a standard thing, but when we stay in our traditional environment, the traditional way is to have three tier application.
Architecture servers are hosted in web front contain side DMC, which we call. Then there is another layer of data of the application services, another DMC. And then the second one, the last one, not least import the, the most important is data storage. Everything is managed by the operations center with security and management area, but everything is in one location, one place, or maybe even if they're distributed, they're in private network, they're not segregated. I'm sure there are some companies who have done this in past to segregate them so that each business functions are different. Of course, there are more efforts. There are, there is a more cost attached to them leaving that aside. We assume this is an average scenario. When we go to cloud, what is required to optimize? So what is required is to go serverless, to get real advantage of cloud. If you just lift and shift to the cloud as infrastructure, you are not really moving to cloud, you are just handing over server, harder maintenance to somebody else, but you are still maintaining the all other layers.
So to get the real advantage of cloud, go to serverless technology, make a choice of technologies or services, which are optimized for use of your requirements and to your scale, to your capacity, your capability, and to the capacity you need. So there could be some services which are based on size, based on use, based on per heat location or per user make a wise choice based on your use case, automated scaling up, scaling down. I don't need to explain this is by default given by cloud, but you have to make sure this is available for the services you choose. And the segment. This is first time we're talking segmentation here. So segmentation is, should be done based on the stakeholder involvement, the SLX expectations and functionalities. Let's go ahead and see how this look like. So we start with adding where we start with a bottom segment, which is common for all the areas which we want to implement.
This involves security access control. This involves the integration components, which you need for integrating various business applications, externals, and also the user management management, et cetera, monitoring auditing services. They need to be in the shared services, no need to say that share service is common for all the segments. So they have to be very well made high. Then you can go with each segment having different business unit or business element working independently. So now you can segregate the services, the databases, the access control, specifically the privileged access control, like administrators, developers of that application. They can have access to all the, that area. Now, if you see they're independent to each other, so they need not be sitting in one cloud provider, they can be sitting in with different cloud providers with different geographies and they are still connected over secure channel. And that gives you real advantage of using different platforms, different flavors of services from different providers and obtain all the, all the benefits of cloud, including not having to invest your own human resources into the area.
So how to approach this. So this is to get out of the challenges we have from standard environment is to group applications based on stakeholders and say, requirements, simplify, access control at a segment level, of course, within segment, there, there may be still access control required, but that will stay at application level. And then implementability for the basic, the shared services component because that, without that you cannot operate all of those segments, our rollout distributed and delegated management to each segment, which we are talking about that will be give you the advantage of cloud security and segregation as well as local ability. So whenever there is a data which cannot be kept internationally can be kept locally, but still access control could be done centrally, oh, we come to the end, the solution benefit. So how we get benefited from this all solutions. So distributed delegated administration, we saw the shared common services we obtain because we need to have control across the segments, but still connected through one base, scaling up and down for each segment, you can manage separately.
So you don't have to do the scaling up, scaling down for the entire environment. You have, the cost allocation can be done at a segment level again, to allocate it to businesses and independent maintenance windows will not affect failure of one application to the other, or in case there is an attack on one segment, it won't affect the others similar way. So if we go through this summarize, this is a really small thing to understand a technical level to how we can separate this. We try to apply this in the I area because we work with 192 national societies from 192 countries. We have our own offices in 62 countries, and we have about 120 internal applications, and we are hosting different applications for national societies. Now, when we do this with national societies, we work with IFRC staff. We work with national society staff about two to 300,000 in numbers.
And we work with volunteers who work with national societies in millions. Just imagine how we, if we had not done this segregation, how different applications will survive or will survive in these large scales. So I hope this gave you some inputs about insight lines, about the different way of implementing the cloud environment, to get some benefits for your business goals, to be achieved with little, relatively little investment, still getting the advantages. Thank you very much for being patient in hearing this. And I hand over to the organizers. Thank you, JE call team to let me come and present here today and hope you enjoy the limiting time. Thank you very much.
