As we’ve discussed previously, software-as-a-service, engineered stacks and personal cloud could be the biggest IT winners within the next five to 10 years. Private clouds hold the foremost potential — in reality, early adopters together with JP Morgan Chase and Fidelity are seeing larger savings and bigger benefits than initially anticipated.

While savings is a key reason to head to a non-public cloud, shorter development cycles and faster time to market are more significant. Organizations can test risky ideas more easily as small, low-cost projects, quickly dispensing with those projects that fail and accelerating people that show more promise.

Meantime, early implementations at scale are producing savings well in far more than 50%. It truly is well past my earlier estimate of 30% savings, occurring largely due to the vastly reduced labor requirements to construct and administer a personal cloud versus traditional IT infrastructure.

[ What does the proliferation of cloud services mean in your IT organization? Read IT As Cloud Merchant: New Skills Required. ]

Given those potential benefits, how should an IT department go about building a personal cloud? The building blocks are virtualized servers running on commodity hardware. There’s also a powerful early trend toward leveraging open source software for personal clouds, from the Linux operating system to OpenNebula and Eucalyptus for infrastructure management. And naturally, you will have server engineering and administration expertise to support the platform. But having only a virtualized server platform doesn’t a personal cloud make.

First, establish a hard and fast of standardized images that constitute the various stack. Preferably, that stack will go from the hardware layer to the operating system to the applying server layer, and it’ll include systems management, security, middleware and database. Ideally, choose a dozen or fewer server images and positively not more than 20. Consider everything else to be custom and treated separately and differently from the cloud.

Second, build a catalog and ordering process that’s easy to take advantage of and whose costs are clear.

Third, couple the catalog with highly automated provisioning and de-provisioning. Your objective ought to be to deliver servers quickly — certainly within hours, preferably within minutes (once your customer authorizes the prices). De-provisioning will be just as rapid and regular. The truth is, you need to offer automated “sunset” servers in test and development environments (e.g., after 90 days the servers automatically get returned to the pool).

Fourth, do clear cost and allocation reporting to drive the correct user behaviors. Such reporting will encourage rapid adoption, more efficient usage and rapid decommissioning.

With these four prerequisites in place, you are ready to begin your private cloud.
Global CIOs: a domain Only for You

Visit InformationWeek’s Global CIO — our online community and knowledge resource for CIOs operating within the global economy.

Build your private cloud in parallel along with your traditional data center platforms. Build both a development and test private cloud and a production private cloud. Seed the cloud with an initial investment of servers of every standard type. Transition demand into the personal cloud as new projects initiate, after which proceed project by project.

Speeding up provisioning should shorten development times. Begin by routing small and medium-size projects to the personal cloud environment, and as you amass scale and exercise session the provisioning kinks, migrate an increasing number of server requests until the vast majority of them are routed through your private cloud.

As you achieve scale and prove out your ordering and provisioning (and de-provisioning) processes, tighten the factors for projects to proceed with traditional custom servers. Within six months, custom servers must be the rare exception and also you should charge fully for the surplus costs they generate.

Once you’ve established the non-public cloud, verify the price savings and advantages. Armed with that data, circle back to existing environments and legacy servers. a great time to transition to a personal cloud is during another event (e.g., a first-rate application release or end-of-life server migration). a number of early adopters are seeing outsized benefits and a powerful developer push into these private cloud environments. So in case you build yours well, you want to reap a similar advantages.

How is your private cloud journey proceeding? Are there other steps necessary for achievement? i glance forward to hearing your perspectives within the Comments section below.

Cloud Connect, happening Oct 21-23, 2013, offers three days of in-depth boot camps, panel discussions and access to a number of industry experts, all designed that can assist you weigh your cloud options and transform your small business. Register for Cloud Connect now.