 So thank you for joining me. My name's Bill Giard, working Intel. So I've been at Intel for 20 years, currently lead our architecture and enterprise strategy within the data center group. Prior to joining DCG, my focus was on leading our enterprise strategy in IT, our app and software development efforts for most of my career at Intel. So today I want to share with you some research that we've done, our own experiences, what we've talked about with our customers around setting cloud strategies and how organizations can look at their application portfolio environment and understand what works best on-premises and a private cloud, potentially a public cloud, and navigating that journey. So before we get started, we'll set some context around really what are the focus areas that an enterprise organization is dealing with, not only cloud itself as an opportunity, but certainly responding to ever-increasing cyber threats and security concerns that are driving application code changes, causing new infrastructure controls, driving new opportunities for speeding development with DevOps initiatives. It's been around for quite some time. It's getting more formalized with driving more continuous deployment, continuous integration, taking advantage of open standards and software platforms, driving new shifts that used to be in IT that if you standardize on a common operating system and platform that you could speed your deployment. That's kind of taking a converse effect where rapid deployments of new operating systems and browsers on a quarterly basis is really causing organizations to make pretty significant code changes to their software environment. Certainly the scale of computing is growing used to be in IT that if you had a software solution that was higher functionality at lower cost, that would win the RFP. We've seen quite dramatically, certainly in our own environment, that our users will actually pay for more for software solutions if the experience is good and it's doing the right things right. And so that's causing whole disruption in the way that we're purchasing a procurement of solutions. Analytics is growing, certainly IoT and social. The net net of really that whole macro environment really is a cloud strategy should be in support of the broader business objectives. We've seen a lot of organizations pursue cloud for the sake of cloud and those end up struggling a bit, but cloud as an enabler for digital transformation enable for responding some of these really is the solution that works best. So the key message on this one is don't pursue cloud for the sake of cloud. It certainly is a key enabler where show some data points on our own experiences but really approach your cloud strategies as a key component for enabling these other business objectives. So organizations are pursuing cloud, it's no surprise. And then do it again in three areas, really to address challenges and what we've seen before. Certainly business agility, how do we improve time to market? How do we respond to the rapid changing environment, develop and deploy new capabilities, faster return on the investment, respond more quickly to user needs. Lower cost, cost was the driver historically for pursuing a cloud journey. It's really fallen over the last few years and last few surveys, it used to be number one three years ago, hey, I'm pursuing cloud technologies for cost. Cost is still super important. It really is starting to take a second seat to the agility and growth area. But cost really is an important consideration in almost every entry conversation. Not only cost for the infrastructure but also for the team that's managing the environment. And security and trust, how do we really drive new solutions and respond to the changing needs? So organizations are pursuing cloud, they're pursuing it in response to the industry trends that are driving their solutions and then really setting a plan for improving agility, lowering cost and then really comprehending their security needs. So really where that's evolved, oops, what happened to our presentation here? So why they bring that back up. So really the strategy was one where that's better, okay. So it used to be a private public cloud and so hybrid cloud really is kind of where things are migrating. You start to see not only solutions and traditional capabilities with things like VMware and OpenStack integrating with things like Amazon and Google. Microsoft is embracing Azure plus Azure Stack. And so really it's a decision of not public or private but what's finding the right mix. So we've done a number of research efforts over the last year, year and a half where we went out and talked to a bunch of users, took our own experience, worked with our analyst, over 125 different focus sessions and a lot of research efforts around what are the key characteristics. So we wanna share with you at least some of those key findings, some of the key tenets, some key learnings around that to help navigate that environment. Certainly people are pursuing private cloud, they're pursuing it for different reasons. And most have a multi-cloud strategy. So when we talk hybrid cloud, really talk private plus public and then even a multi-cloud strategy that says, hey, we're running both, perhaps multiple public solutions certainly in a SaaS world, that's true. Where we have, whether it's your CRM solution, your email solution or dot collaboration, really running those in multiple environments becomes critical. And they're doing that for the challenge that we talked about for, reducing time to market, lowering cost, improved scalability, higher developer satisfaction, we'll have a deeper discussion in a few slides around, hey, what's the role of the application online of business in those cloud strategies? It's disrupted quite a bit from what's the traditional environment. And then improved infrastructure management. But it gets you to, fundamentally, there's the business context for cloud and how do you set an environment and strategy. Is it public, is it private, is it a mix of both? So what we wanna do now is kind of share with you at least our observations, what we've set from a cloud strategy, what we've seen from our research. There is more details on this on intel.com. You'll be able to see some of the research itself that's published out there. But there's really three areas that become key considerations. Certainly the business environment, what's the environment with respect to a local organization. Some key technical considerations that came up pretty consistently around performance, integration, the size of the data, level of security and control. And then other elements around ecosystem. So in the next few slides, we'll share at least the summary of that research. We'll also show you some workload assessments and application workloads by vertical that says, hey, what are the weighting based off that from an industry perspective to help at least guide you as a starting point. It's certainly a beginning for your own organization to be able to pursue. So the intent really for us to help you on your cloud journey, at least from an Intel perspective, we run most of the clouds from an architecture perspective, both public and private. And so our goal really is to help our customers and our partners drive solutions that help them grow their business. That's where we think, we win, that's where we think the organizations win. And so we really are in the mode of trying to help really pursue the optimal strategy such that you can avoid the costly rework from moving to one environment or struggling and then moving it back. And we've seen that. So really that's really our own purpose on why we do that. And we think it's a good effort. It is our number one question we often get from our customers and our partners, where do I run my solution? How do we do that? And so the intent of this discussion really is to help you understand what we've learned, what our partners have told us, the experiences that we've had. So business, certainly the first part, we often like to get into kind of the technical consideration, certainly within our own IT organization. The starting point really centers on, hey, what's the business objective that your organization is pursuing? Are you trying to improve agility? You've got to imperative to respond to some digital disruption in your own environment. And it may vary around, hey, I've got existing infrastructure that I've got to go manage. I've got some legal cost controls that I've got to go pursue. I've got a new business opportunity, remote geography that I don't have a data center involved in, right? And so really spinning up and responding to those. Or even just managing high levels of service all agreement. And those kinds of considerations vary between public and private. So certainly an agility perspective if you're looking to rapidly deploy some new capabilities that your organization may not have the technical expertise to support or heavyweight from a capital investment. The public cloud becomes a pretty good offering. This is, hey, how do I jumpstart that? I may get some key learnings, make sure it works and then move it back. But the converse is also true, right? So you've got some agility and I've got a new imperative to release some of the solutions, respond to security control. And I've got a pretty significant level of investment already. And lifting that and moving it, working through the integrations between the firewall becomes quite expensive. And so it all depends on what you're trying to do from a new investment perspective from an agility. What do you have to integrate? What do you have to go deploy? Are you lifting and shifting and those types of things? And so looking at really what the business objective from a cost agility perspective and where you're at and where you need to go to becomes important. The number one kind of consideration that we hear oftentimes is really around compliance, legal and control compliance. And being able to manage that, get the transparency and control from a infrastructure perspective, highly regulated data sovereignty and driving some of the legal compliance that varies. And so if it's a solution that may not have a whole lot of regulatory oversight, then public cloud becomes kind of an area that most organizations pursue. Not to say you can't put those controls in, they're actually working quite hard to drive security controls and do security compliance. And so it certainly is one that is also quite feasible but your solutions have to be aware around what are your legal compliance controls that you can move. Oftentimes organizations are pursuing a private cloud for that very reason because it's not just that the ability of an infrastructure to manage the legal compliance but the ability to do attestation and prove to your auditors that the controls and components that you're running are supporting the business. And so really looking at it not just from a security perspective but what's your ability to prove that your process controls are in place. Global reach, I mentioned before that, it may be a consideration that you're branching out, you don't have a data center in Europe. Certainly making sure that you're spending your dollars on growing in the business solutions versus building facilities may make sense. If you have a design team or you have an audience globally or you're getting cost and capacity, we certainly see many organizations pursuing some of that from a volume perspective. So that also becomes a key business consideration is what's the strategy for deploying solutions where your end users growing and where does that kind of run. And then service of agreements. It's an interesting phenomenon. It used to be, hey, we can't move something to the public cloud because we need certain levels of operating SLAs and operating level agreements OLA's. We've seen that shift change quite dramatically as the kind of robust fault tolerance things happen at the public cloud but we certainly have quality levels of service guaranteed and service delivery depending on the criticality of the business that still needs some of those strong SLAs. That's really where we may see deployments really in the private cloud more specifically than a public environment. Now it's situational but it really starts at the business context. So you're trying to grow your business or you're trying to achieve cost and really what are the first key sets of business considerations. The next one really, we found four key technical attributes and at Intel we kind of hone on these quite heavily because we want to make sure our products and platforms are optimized to be able to support the performance needs, the security needs, what we have from integration and size. And so we look at this and there's really four key attributes that came up pretty consistently. I mentioned the first one, as organizations are mapping out their strategy, what are the four technical characteristics of an application or workload environment that drives that. So security became number one quite strong around, hey, how do we drive really the security and legal and transparency controls that you need to do from an IP protection or even a geo regulatory control perspective. Performance and it's not only performance with respect to the application or solution itself running on a series of servers but also performance in relation to the end user. So if you have a manufacturing or partner systems, manufacturing environment that just got a process, data from your factory line, be able to do some insights and then load new components, that latency that you have in that area becomes important but also if you've got a set of users working on large sets of CAD design files and that becomes important as well. And so really not only the performance of the system itself on how fast it can respond and get a fairly tuned environment but performance with respect to other systems or the integration systems or the end users using the solution. Integration, almost no enterprise application actually is standalone, right? So the level of integration from something like an ERP environment becomes an important consideration to your lift it, move it through the firewall, what's the level of rework? There's almost no enterprise app that is truly standalone. I mean, you have some of those but the level of rework and the level of integration to other systems becomes important. And then certainly the size of the data we've seen a bunch of work around as data grows, being able to just move it from your local system to the external solution becomes expensive from a time perspective but then also managing that externally is also an important consideration. And so on this one there's some examples around, hey, there's some application workloads that really have less stringent performance, low latency, and end user responsive needs. They're designed from the get go to kind of work over a wide area network or over the internet. You know, they have burst capacity from a performance perspective where they may need a lot of compute capacity that you may not have the flow. And so really that becomes a good opportunity for a public burst capacity if you don't have the scale where you may see some lower latency ones kind of running on a private cloud. Security, it varies like I said, it's kind of the number one area that we see in a number of cases. And really it all becomes around, what's the attack surface you want to have? What's the level of rework and controls that you have? So a private cloud has a smaller attack surface than a public cloud but you may not have the operational controls in your own organization. So how do you go put those in place? And so looking at those different considerations. And then optimized integration and then things for data size. And so really those are the four key technical characteristics. And until we're looking at how do we provide high-speed fabric for performance? How do we implement cloud security controls for app isolation and VM isolation? And what are we doing for encryption capabilities for security optimizing communication APIs from an integration perspective? And then certainly storage is a big focus certainly with our platform capabilities with 3D cross-point and our NAND storage and what we're doing in Optane technology. And so we get different things that we look at how do we optimize both public and private cloud in each one of those areas? And so you'll see those. I'm not in this session but kind of a deeper discussion around, hey, how do we take this in our own perspective and help our customers and you just drive that? So then we look at kind of a standard set of workloads. We said, hey, what do we have from things that may run more effectively on-premise or public? And it's no kind of surprise that some of the more mature software, commercially available software solutions which you have for web servers and email or even some of the customer relationship management systems really exhibit lower sets of capabilities from a size of the data that it's running, level of security and backend integration. At the other end of the spectrum, if you have some financial systems or research and R&D capabilities, they end up seeing large sets of data size, right? Large security requirements. And then conversely, there's fewer commercially available software apps for that. And so the middle ground is kind of situational. You certainly see ERP mix from traditional, big deployments on-premise. Some of the newer, small and media business have less integration so they've been able to kind of start in a public cloud environment and it kind of mixes. And this ends up being a fairly common set of assessment that says, how do you pursue based off app and workloads, things that may run off-premise, things that may run on-premise in a public or private cloud environment? And so you can look at that as kind of a framework for running. And then there's the ecosystem consideration. We kind of mentioned really, IT organizations are really pursuing SaaS, public cloud as the new buy, right? The new buy for software, buy versus build. And so the maturity of offerings becomes largely the starting point for conversation. Can I move my email environment or purchase my new software solution? And that's really the new way of delivering. We are seeing a hybrid set of cloud solutions kind of deploying both managed services on-premises but really looking at the SaaS maturity, what's the capability from a developer services offering within a public cloud solution and what's the ability to kind of respond to different ecosystem needs? What's the skill set of my organization, et cetera? And so those kind of all manage into different flows of where do you map out the ecosystem? And there's more detail kind of in the research paper around some of those, but I wanna give you some examples of how we've applied some of that knowledge, how we've navigated, what are some of the best practices that we've had at least in our own experiences. And so I'll get into a couple of examples around defining our own cloud strategy. So we'll look at really a public cloud SaaS solution and then we'll look at our more in detail given the focus of this summit around, hey, how have we deployed our private cloud capabilities? What have we put onto it? What are the some of the business results that we've put in? So certainly the first one that will be open about is we've been like any IT organizations looking at our software portfolio. We have about 3,000 or so applications within Intel that we manage from our IT organization, 6,000 employees, data centers spread globally. But like any organization, we're approaching a strategy from both a public cloud and a private perspective. And our first one really is, hey, we've got aging software, we've got to respond to different changing needs. And so we've got a portfolio set of tools that help manage our expense and travel, right? And what do we do from an employee perspective? And so we've moved that into a public cloud SaaS offering. And so really manage that infrastructure. We do have other portfolios that we also kind of look at some of the capabilities from our email and collaboration tools. But really the drivers for us was pretty significant cost savings, right? I mean, we've got, it's been running a number of years in production. We're able to kind of embrace the mobile worker, right? Be able to move our traditional browser-based, laptop-based solution and be able to deliver capabilities via mobile and desktop and across Mac, Windows, Linux, right? Enable our design and our Salesforce. And get pretty significant returns in time to market and speed from pursuing a SaaS strategy. And certainly cost is a key factor, but also the ability for meeting our end-users' expectations as employees. What do we run from that? You know, important in that consideration is not only what do we have from a deployment, but also what's the role of the application or line of business in the developer? And so we did another set of research study that I'll share that kind of shapes the capabilities that we deploy, which really is, you know, what's the role of the developer in kind of cloud adoption? How do we shape that in infrastructure decisions? The short answer is the traditional IT infrastructure decision-making, the person that would set up your open-stack environment isn't necessarily the decision-maker that's driving adoption, right? I mean, we saw that in some of our SaaS solution deployments where the application teams in the business really is driving those decisions in. When the technology is relatively in its early phases, you know, from an app perspective, you know, that the app developer is most influential, right? They're also, that's what life cycle says, also in the later phases when you're moving it and you're kind of migrating it and supporting it becomes most influential as well. And important to note is, you know, a lot of the technologies from a cloud-native perspective, whether it's containers and security, are really in early phases of technology maturity. And so what that means is the app developer is highly influential in driving your cloud decisions, which kind of gets us into, you know, approaching a cloud strategy from both an app and an infrastructure perspective. And so we'll talk about at least, you know, what we've done from our approach, you know, integrating both a cloud infrastructure, infrastructure service with, you know, platform services, which is kind of evolving, right? We have both platform traditional, platform developer services and database services to really achieve three things. Agility time to market, all right? We want to be able to enable the developers to release code at a pretty rapid pace, be able to support their app and database line of business, you know, drive new efficiencies from a, not only an efficiencies from an IT infrastructure cost perspective, but from a deployment as well and then respond to security concerns. And security is an important one because, you know, we've been making, you know, at least at Intel with our own app software strategy, you know, tremendous amount of code changes to our traditional apps, things that we're running on, you know, .NET or HTML or Java, right? And what are we changing the front end and doing, you know, static code scanning? And so what we found in our security environment is the ability to more quickly patch and standardize some of those on environment. I'm pretty significantly improved our security posture for responding to that, you know, those kind of those environments. And so we really have three different cloud offerings internally. We have an app platform, which is based off of a, you know, platform as a service, a pass capability. We have a database set of database services that support kind of all of the mainstream databases for SQL Server and Oracle as well as MySQL and MariaDB. And then a compute environment, which is really largely just VMs, right? So how do we support our VM infrastructure? Important to that consideration really is enabling self-service for the development teams, not forcing them to go through an IT ticketing process to get, you know, new virtual machines, making sure that we're kind of holding true to the, you know, cloud feature sets around, you know, metering and monitoring and policy enforcement, but also giving them the, you know, self-service ability to provision an app like they would be able to do in a public cloud environment. And, you know, openly that's a big culture shift debate for our organization, but holding true to the self-service really, you know, rapidly increased our adoption. We have over 2,800 apps or so, you know, which is increased from what you'll see on the next slide or so that are deployed to our internal, you know, pass environment, you know, another, you know, 2,200 or so apps and databases as well. So we really get rapid adoption from our global teams without the mandates that we see in the environment. And really the focus that becomes important is adding things on top of the VM infrastructure, becomes pretty critical. You know, most organizations will deploy, you know, like an open stack environment and say, hey, you've got, you know, free access, self-service access to, you know, compute VMs, get self-service access to storage. You can configure the network. And from an app team, you know, it really looks and feels like traditional IT still. And really what they're looking from a cloud perspective is how do I ease the ability to set up my database environment, not deploy new sets of app configurations, right? I mean, even if I get a VM with unlimited computer immediately, right? And we've got pretty good success stories for moving, you know, the physical server landing down to, you know, weeks to, you know, hours, right? And then be able to get VMs down to minutes. But even if I get a VM, you know, on instant access, I'm setting up the database environment, setting up the application environment, setting up the app code, still takes weeks in a project, right? And so, you know, how can we also deliver capabilities for our app and dev teams such that they don't have to manage the databases anymore. They don't have to set up high availability. They just deployed their database code. How do we deploy their app code such that the web server support it? And really, you know, driving solutions that allow them to focus on, you know, writing code, deploying code, making sure it's tested and integration with different DevOps practices or even traditional deployment models such that they're getting out the environment set up, right, set up new environments from dev to test and making sure they're in place. Containers certainly help with that. And so, we're evolving our capabilities to move from the traditional pass to kind of a container-based deployment. That's its own set of evolution. It's got its own set of controls in place. But, you know, really the key message here is for those new line of decision makers that are driving infrastructure deployment, making sure we're deploying some of those. And so, this is, you know, kind of a logical architecture that we've deployed internally, you know, sets of app services. We happen to deploy, you know, open-source, you know, cloud, you know, platform as a service. This is what it would look like on top of OpenStack. We also integrate both sets of automations capabilities around, you know, deploying, you know, things on top of our environment. And the key notion here is abstracting a lot of those things in, you know, traditional pass, whether it's, you know, cloud boundary initiative, whether it's open shift, what you're doing in Docker swarm, you know, really, you know, strongly consider, you know, approaching your digital transformation and cloud strategy approach by adding some of those things. And this is our own, you know, set, right? We've got another diagram that talks about, you know, ramping, you know, what would it mean from a developer ramp? You know, the numbers that I quoted are much bigger than what you're seeing here just because, you know, this seems like every time we go and pull the snapshot, you know, the adoption gets bigger and bigger. And one of the big debates that we have really is, hey, is it really more cost-effective to run, you know, on-premise versus public? And we run both. We've got things in, you know, kind of the, you know, mainstream, you know, top cloud service providers. We've got big, you know, SAS capabilities. And we've been benchmarking our own set of cost efficiencies and agility time to market on, what does it take to, you know, lift and replace? Internally, it's about six weeks savings to just, you know, reuse things because we don't have to rework solutions, right? So we can deploy things almost immediately in a, you know, DevOps kind of fashion or even traditional deployments, deploying apps and microservices on that solution. But then also just getting the raw cost numbers, right? So we're often asked, hey, you know, how are we, you know, taking advantage of some of these private cloud technologies? And so we've been, you know, continuously looking at, you know, where's the public cloud going? You know, what's our cost for deploying into kind of the top cloud service providers? And what's our cost for deploying infrastructure and supporting these applications on-premise? And, you know, what we've seen interestingly enough is we've continued to kind of drop and optimize. We've kind of a normalizing point last year, but we've seen some more savings this year. But, you know, the short answer is, you know, within IT we're wired for getting to the lowest cost, right? Not cost competitive. And so we see some of those kind of level out and we think the market still changes and we're getting new efficiencies now with things like serverless computing. But this is even just on pure infrastructure as a service savings. So pretty significant savings, consistently on driving, you know, our own private cloud versus public. And then additional one from a time perspective. So, you know, what are the stages, right? So, you know, we've given some of our own kind of characteristics of driving a workload on what's the approach. And it's really four major areas you can bring into different things. So as soon as you get the traditional data center environment, and an organization may be on different areas of this, we even internally, depending on what we have from our manufacturing on different stages, you know, doing compute virtualization, you know, moving from a heavyweight server landing to a virtualized infrastructure, you know, gets greater efficiencies, be able to take advantage of more shared resources, that's not a new story. You know, the move to software defined infrastructure, automated orchestration using, not only, you know, virtualized compute, but also software defined storage, you know, software configurable network, you really gave us greater agility, and that's what you saw, you know, from that cost savings that we had before in agility deployment, it was really, you know, largely in this third phase. Now what we have seen interestingly enough is the ability to go quickly respond to that and store data more specifically, you know, really gives us more ability to drive new analytics and insights. We have an example where we've seen quite heavily, you know, the ability to store data, manage that data online, all right, in a server-based software defined storage environment, we're able to then go and drive analytics. One example that I'll just refer to is we have our security network logs, and having, you know, larger storage frame around our network, you know, software defined network, and then storing those logs online in our server environment, we then drove new security analytics solutions around network traffic, around, you know, different capabilities, and just new, you know, sets of analytics from a, you know, security operations perspective. Similar kind of case studies around sales and analytics, right, what are we doing for kind of predictive sales management, and really driving that new set of focus that a lot of organizations are pursuing around, you know, building on your optimized data center infrastructure and then doing new insights, either manufacturing, sales, security, you know, number of case studies around analytics. And so these are kind of the four major phases, traditional, compute, software defined infrastructure, right, you know, spreading that out and then, you know, driving that out. But we're to start, you know, it's easy to say, hey, we've got an infrastructure approach with data center consolidation, you know, really what's the hybrid cloud model, you know, from that perspective. Certainly kind of two areas come up most frequently, you know, start with really a cloud native approach and, you know, taking your traditional infrastructure, you know, optimizing some of the application components, connecting it back to your traditional environment. So, you know, you may have a, you know, an SAP environment or a heavyweight SQL server, you know, traditional application and then taking some of those new front end components, those web and app components and connecting them back to your traditional infrastructures that may be virtualized on the environment and pursuing kind of a cloud native perspective. That really makes, you know, a lot of sense for most people are pursuing that. Now, the reality there is when you migrate that journey, not lifting and replacing that into an environment, you know, be able to modify the things in place becomes an important kind of agility and execution strategy. In fact, you know, most of the solutions that are running in most clouds are still running VMs, but they're running, they're pursuing a cloud journey such that they can get the agility and the benefits from this cloud native deployment experience model. So start with cloud native. Don't, you know, pursue it as I have to rewrite the entire app, right? It's really what are the components that you're extending and integrating and then also software defined storage, the cost benefits of scaling out storage, taking advantage of capabilities, certainly just even moving your traditional volume stores over and then moving that from a block storage, you know, model to an object storage model and take advantage of some new cloud capabilities for doing that makes a ton of sense and then integrate, you know, with the existing sets of capabilities. And so, you know, approach it from a, some people have called it kind of a hybrid hybrid, right? Because an application doesn't have to move holistically, but just, you know, think about it as a stage deployment from an infrastructure and then how does this support your application environments as they progress up the flow. And then certainly integrating some of those with external, you know, SaaS solutions, where it makes sense, like in our HR example, you know, certainly most of our employee data is internally integrating that externally with, you know, single sign-on experience and then taking advantage of some of the cloud infrastructures for our own employee management talent systems and our external ones becomes an important kind of consideration. You know, I am happy to say, you know, at least, you know, we've made the shift to supporting, you know, cloud technologies, whether it's on-premise or public. And so we do look at it, you know, quite holistically, you know, how do we run and optimize, you know, technology solutions from compute, whether it's our, you know, standard Xeon platforms running, you know, increased capabilities for app and VM isolation, what we're running with respect to, you know, security technologies and really putting, you know, security at the hardware level, right? As we respond to enabling flows, what are we doing from an ecosystem enablement, you know, in software perspective? Certainly one of the biggest areas that is being disrupted quite heavily is kind of the bottlenecks moving from a compute optimization perspective into storage and IO and network. And so, you know, a lot of the things that we're seeing for, you know, in-memory analytics and being able to optimize, you know, storage platforms and be able to make sure we can, you know, really respond to this growing set of data, you know, certainly what we've done from a, you know, you know, 10 plus year research investment around 3D cross-porn and storage architectures and what we're doing for our obtained solutions becomes, you know, important new things to integrate with our, you know, cloud solution providers, both in an open stack capability as well as a public cloud. And certainly, I think we're just getting into the, you know, early phases of some of the network optimizations around, you know, policy-based informants, how do we do, you know, from a traditional, you know, firewall, you know, provisioning segment perspective and put, you know, really those firewall, deep packet inspection things into, you know, this micro-segmentation world of, you know, multiple apps that have to be kind of contained and wrapped around and, you know, many sets of DMZs within a computer environment becomes important. So you look at, you know, kind of the network, you know, virtualization and what's happening from a, you know, software optimization and a silicon optimization, you know, so, you know, lots of platform architecture capabilities that we're looking at to try to enable some of those things. So what are the key messages? Certainly, cloud technologies when approached holistically can accelerate some of these key business objectives around multi-platform, what's happening from a security, you know, look at the characteristics and try to map that out. You know, we've got some additional insights that you'll see around mapping those out. We're certainly happy to, you know, help you in that journey either, you know, through, you know, some, our partner ecosystem or what we have in our other, you know, field engagements. But do focus both on the infrastructure and the apps, right? It's really a holistic digital transformation discussion. There are absolutely certain applications that will run best on-premise. Some that are optimized for public and the future really is a mix between both. And so, you know, engage, you know, with some of the resources we have out on our IT center, you know, we have some best practices with respect to what we've done internally and we try to drink our own champagne as they say, you know, we're pursuing our own journey on that perspective. And then we've got, you know, solution briefs and capabilities in our cloud builders where, you know, our partners have brought together capabilities to enable those solutions and case studies and briefs that help you with that. And then there's more resources. There's a link to kind of the white paper if you just did a search on Optimal workload on intel.com it'll come up and it'll show you some of our more detailed research and details that says, hey, you know, in a step function, you know, what are some of the things that you can map out? There's some deep dive sessions around other errors and flow and certainly, you know, feel free to send me a note if you have some follow-on questions. And with that, I think we're at time. I'd be available for questions off to the side, I think, as we're run out of time, but what are we at from a time perspective? Good, okay, thank you, appreciate it.