Throughout this Private Cloud Infrastructure as a Service content series we have presented key areas for the architect to consider in designing a private cloud in their organization. Many of these areas are likely to be familiar either in terms of the process or the technology used to deliver IT services. Within an organization there may be silos throughout the organization where these processes and technology are faithfully practiced individually or in some combined form. However a private cloud represents the holistic collection of these existing and new processes and technology that when stitched together in a fully automated manner allow IT to compose and deliver infrastructure solutions that meet the continually evolving needs of the business.

In this article we review the business drivers for transition to a private cloud and a maturity model gauge the existing state of the organization and identify growth areas that develop the organization to a level required for successful implementation of a private cloud delivering Infrastructure as a Service capability.

1 Understanding Key Business Drivers

In the Private Cloud Reference Architecture we’ve developed to help our customers make the transition to a private cloud we describe business drivers for cloud computing in terms of the competing vertices of agility, cost, and quality:

Agility	Cost	Quality
Reduce time to market: Implement new business solutions quickly to accelerate revenue growth.	Reduce operational costs: Optimize daily operational costs like people, power, and space.	Consistently deliver to better defined service levels: Better service leads to increased customer satisfaction.
Better enable the solution development life cycle: Speed up business solutions through better development and test, and a fast path to production.	Reduce capital costs or move to annuity-based operational costs: Benefit from reduced IT physical assets and more pay-per-use services.	Ensure continuity of service: Minimize service interruption.
Be more responsive to business change: Deliver quickly on new requirements for existing business solutions.	Make IT costs transparent: Service consumers better understand what they are paying for.	Ensure regulatory compliance: Manage the compliance requirements that may increase in complexity with online services.

Where organizations locate their business need among these primary drivers and define their objectives as they consider their cloud computing options is a basic starting point in the process. For many in the IT shops of large organizations, whether private enterprises or public entities, the private cloud is proving especially attractive, mainly for what it offers in terms of control over matters of security, data access, and regulatory compliance. Their primary interest in a private cloud architecture typically revolves around the very real pressures to cut costs without sacrificing too much control over essential data, core applications, or business-critical processes.

But according to a recent Gartner survey of CIOs worldwide, what’s top of mind for a lot of them has less to do with the usual need to drive greater efficiencies and cut costs in IT than with the desire to increase enterprise growth and attract new business. This shows that IT leaders are beginning to think seriously about cloud computing as a way to turn IT into a key contributor to the positive side of the balance sheet, rather than a cost center that has to be constantly squeezed, prodded, and bled of every last inefficiency.

1.1 Asking the Right Questions

Cutting costs, increasing efficiency, and driving growth: these are all worthy objectives for implementing a cloud solution. Indeed, a cloud could conceivably deliver all of these benefits. But if we focus too much on all the things we could do with a cloud, we may fail to see what we should do—and actually have the capability to do—with a cloud. This is where a clear-eyed strategy for success comes in, which depends in large part on your ability to ask the right questions especially at the outset of your journey.

2 Introducing the Core IO Maturity Model – Private Cloud View

Once you’ve identified business needs and objectives, you need to understand fully the capabilities, limitations, and complexities of your current IT environment, which starts by performing an analysis of your technical and organizational maturity against the backdrop of the different capabilities of cloud computing. The next step is then to determine where you want to take your organization, assessing the prerequisites for the desired objective.
This process of change we describe in the Core IO Maturity Model – Private Cloud View. It is organized by infrastructure optimization stage (basic, standardized, rationalized, and dynamic), with the details f each stage described using an industry-standard definitional schema for cloud attributes (self-service, usage-based, service, elastic, pooled resources, and broad network access). As you progress in infrastructural and organizational maturity, your business will benefit from increasingly advanced private cloud-based scenarios.

Figure 1. The Core IO Maturity Model - Private Cloud View

2.1 An Incremental Approach

Many organizations are starting at a relatively basic stage along the optimization continuum, where they’ve already managed to consolidate infrastructural resources for better cost-efficiencies through virtualization. If your organization fits this profile, a perfectly acceptable outcome might be to advance your business to the next stage by implementing more sophisticated infrastructure-level resource pooling which would achieve still greater cost savings as well as a measure of improved time to market.

Similarly, your current organizational capabilities may land you somewhere in the middle of the maturity model, with a relatively high degree of sophistication in those business areas you consider your top priorities, such as being able to respond to seasonal shifts in demand if you happen to be a major retailer. While your ultimate goal might be to bring into play platform as a service (PaaS) and software as a service (SaaS) architectures so you can leverage a larger set of hybrid cloud capabilities—such as anytime, anywhere access for your customers built on a highly unified set of compute, network, and storage resources—your near-term focus in the context of an infrastructure as a service (IaaS) model may be just in moving the dial specifically on automated provisioning and de-provisioning of resources.

It’s in this approach—by making deliberate, incremental progress in the service of a longer-term strategy—that real IT transformation occurs on a private cloud model. The way forward is rooted in recognizing that change is an evolutionary process, where the investments you make in technology solutions must be evenly matched at each step by the maturity of your organization in managing them. Further, your strategy must be carefully applied in those areas where your business is likely to benefit most. Indeed, not all capabilities of a private cloud need to be—or should be—exploited. Greater elasticity, for example, may not be what your business fundamentally needs nor has the technical or organizational maturity to support. The task isn’t to do it all, much less to do it all at once. The real task lies in balancing the potential goods of a private cloud solution against actual business needs, understanding your capabilities and limitations at each stage of the process, and charting a realistic, achievable course of action for getting it done.

2.2 Understanding the Implications

To be sure, considering capabilities and limitations in going from one stage to the next is just one vector of analysis. Any one of the capabilities or features of a private cloud solution with which you choose to align introduces additional considerations that may not be obvious at first. The objectives you choose for your private cloud will raise a number of questions about the various technical and organizational implications of implementing your solution.

Below are some examples of the kinds of questions you need to be able to ask in order to frame a comprehensive and realistic strategy for achieving your objectives. With reference to the maturity model diagram above, these are presented in the order of the fundamental private cloud attributes:

• Self-service: Allowing your users to provision the resources they need on-demand without human intervention may seem like an eminently desirable option, such as when it comes to partitioning new storage volumes or building out a new virtual machine cluster to support test scenarios, but very quickly you can run into questions of governance. How much control should you relinquish, and what are the potential consequences of offering a self-service model for common tasks? Consider the way collaboration sites can proliferate in a large organization when left unchecked and the concomitant and increasingly costly burden on storage, network, and compute capacity.
• Usage-based: Pay-per-service, or “chargeback,” is one of the hallmarks of cloud computing, and if your private cloud strategy includes driving greater transparency of costs for the sake of better resource planning (among other potential objectives), you need to know the incentives you’re trying to drive. Are you trying to reward good behavior and punish bad? In that case, a consumption-based tax might make sense, based on input/output operations per second (IOPS), for example. Or, you may wish to push more round-the-clock workloads to nighttime operations for the sake of power savings that support your company’s “green” initiatives.
• Elastic: Being able to respond efficiently to fluctuations in resource usage—whether seasonal (as in the case of retail businesses), diurnal (as in the case of typical corporate email systems) or some other periodicity—can represent a major selling point for cloud computing, in no small part because of the perceived benefit of reducing a company’s carbon footprint. But it is important to consider first whether you really need a sophisticated system of automated provisioning and de-provisioning of servers to deal with fluctuations in demand. If significant and relatively unpredictable, then this capability may be appropriate. If the need is regular and predictable, straightforward automation may be sufficient for your purposes. Among other questions you need to ask: Which applications are priorities, and which can be pushed farther back in the queue?
• Pooled Resources: Consolidating resources to save on infrastructure, platform, and/or software costs is a common goal for large-scale IT operations. If you’re in a large organization with several independent departments potentially with their own IT operations (a common model for governmental institutions), you are likely to encounter critical questions of process: How, for example, will wholly independent groups deal with the inherent limitations of shared infrastructure and services? Will standardized configurations come at the cost of the optimized systems to which they’ve grown accustomed? As you move forward in the process of pooling your resources to get the attendant benefits, you need to be cognizant of the likely tradeoffs in putting everyone on a standard set of services. It may very well be worth the cost to the organization as a whole, but it may not seem that way to those who lose capabilities or levels of service to which they’ve been accustomed.
• Broad Network Access: As you move out from behind the corporate firewall and away from tightly controlled client configurations and network access scenarios, there are several important considerations that will need to inform your strategy, beyond the obvious concerns over security, such as the nature and extent of supportability: What kinds of personal devices will you support and to what degree? How will mobile clients—smartphones, tablets, or other kinds of devices with third-party operating systems, applications, etc.—access network resources, and will you have the requisite bandwidth to service them? What forms of authentication will you support?

Whichever objectives you are aiming to achieve, the important point to bear in mind is that building a private cloud is a process for which there are numerous tactical and strategic considerations, for which the Core IO Maturity Model can provide a useful framework. A successful implementation hinges on your ability to think through all facets of the undertaking, clearly understanding the dependencies, tradeoffs, limitations, and opportunities of any particular strategy.

3 Managing Expectations

The Core IO Maturity Model – Private Cloud View is in some sense a response to an underlying issue that we’ve encountered in our experiences working with large organizations on their cloud deployments. Often, we have found that the ambitions and expectations that organizations have for a cloud solution are out of line with the realities of the process and its potential outcomes. To help these organizations set more appropriate expectations and frame strategies with realistic and achievable goals, the maturity model can be very useful. But its lessons must also find their way to the organization as a whole in order to ensure the alignment of business and IT on the goals of the project.

3.1 Service Providers and Service Consumers

A persistent perception of cloud computing is that it can very rapidly deliver significant return to a business with the potential for a minimum of effort and investment. It’s a common expectation among consumers that the cloud should offer easy-to-implement, extremely scalable, well performing, and secure solutions. Internet-based email services have benefited consumers for years, and it’s become commonplace for individuals to be able to collaborate, store personal data, or host applications large or small in the cloud. If consumers can benefit from all these on-demand services, why should it be any different for businesses? Why does it take a week or more to instantiate a new email account within a corporate firewall, when Hotmail or similar services in the cloud—which cost the consumer little or nothing—can be had almost instantly?

The answer may or may not be self-evident, depending on your point of view:

• The provider’s perspective: If you happen to work in IT, and are steeped in the technical and organizational challenges of delivering services to consumers within your organization, and understand in some measure the complexities of the systems involved in terms of both the technical and non-technical requirements imposed on them (such as data integrity, regulatory compliance, corporate information security, etc.), it will seem obvious that a public cloud-type solution would be highly problematic.
• The consumer’s perspective: If, however, you happen to be a consumer of IT services, your perspective instead may be one of an inscrutably complex array of infrastructure components and software services that are often unreliable, unresponsive to change, and difficult to customize and control. And if you control budget, you may even question why you’re spending so much money for such a disappointing return on investment. This point of view has the effect of putting IT, fairly or unfairly, in the challenging position of having to compete directly with large public cloud providers and offer services of comparable scale, reach, and efficiency.

This misalignment of perceptions and expectations between service providers and service consumers is telling, as it underscores the challenge of cloud adoption for large organizations in particular. Consumers’ personal experience of a public cloud has unfortunately contributed to the expectation that businesses can leap ahead, potentially in one step, from a traditional IT environment to one that is dynamic, responsive to changing business needs, highly available, and extremely cost-effective.

3.2 Aligning Business and IT

But the reality for most large organizations is that an incremental strategy is the only realistic path, given the technical and organizational complexity of current IT operations fed by years of layered investments that businesses are justifiably reluctant to abandon wholesale. And this is one of the key reasons why a private cloud model is proving especially compelling for those who are evaluating their cloud options in the context of enterprise IT: it takes into account existing investments and organizational aptitudes, permitting incremental approaches to adoption.

Be that as it may, the tension between unrealistic expectations and realities of cloud computing in an enterprise IT context can prove a challenge to resolve. Many IT leaders understand why an incremental approach is needed, but those outside IT—business leaders in particular—are less clear about the real implications of implementing a cloud solution. A sound strategy for achieving your objectives must also include an appropriate communications strategy for the sake of consistently setting and managing expectations for the organization as a whole. With the whole organization informed, from the board room to the front office, the hard work of defining and executing on your private cloud strategy is far more likely to achieve its objectives and set your business on the path to long-term success in the cloud.

For many corporations and government bodies seeking to improve business agility, reduce IT costs, and/or enhance service quality, a private cloud architecture—regardless of the service model—is the best choice. If your organization is evaluating a private cloud deployment, or even if it has already begun the process, there are many resources and programs available from Microsoft that will help you get and stay on track.