This Friday and Saturday, 14th and 15th September 2012, respectively, will be challenging days for me, and will count among two of the most physically demanding days of my life. On Thursday evening I will join my Cisco colleagues taking part in the Deloitte Ride Across Britain (or RAB as we call it), to raise funds for the Paralympics GB team. I’ll forsake my desk and comfortable chair, and over Friday and Saturday, I will cycle 238 miles (close to 400km!), including over 11,000 feet (over 3,300m) of climbing, from just outside Glasgow, in the west of Scotland, to Fort William, and then on to Kyle of Sutherland, which is around 40 miles north of Inverness.
On Thursday and Friday evening, I will join the camps -- yes, tents in a field, no luxury hotels here!! -- as you can see from my short video from last year’s RAB camp at one of the stages.
In my previous blogs confine and clover, I spoke about determining the scope of your business problems as well as defining your measures of success when planning a Cloud solution. Now, I would like to help you understand both the cost you will incur for the work necessary to achieve your defined cloud goals and how to avoid unexpected fees.
Because of all the hype around Cloud, we hear (sometimes disproportionately) about how Cloud can transform your business. However, the cost of that transformation is often not fully understood. Careful planning and awareness can save you money along the Cloud journey. Be aware of and consider the following hidden costs:
Last week, I introduced my concept of the 3 C’s of Cloud: Confine, Clover, and Cost and began outlining a simple strategy for maximizing your benefits during the process of adopting a cloud solution by confining the scope of your business problems. What comes next?
Let’s now talk about the second of my “C” concepts—Clover.
Before you can ‘roll in the clover’ of a successful cloud implementation you need to address one of the most common pitfalls to success: failing to build an appropriate business justification for migrating to cloud. If you enter the process with the attitude that “I’ll just experiment with this new Cloud thing and see what happens; maybe it will give me what I need,” you may not end up ‘in clover’ but in the weeds. So, what do you need to do?
Feeling frustrated among all this chatter about Cloud? Want to implement a cloud solution quickly for your business, but don’t know where to start? I can help you understand how to maximize your benefits during the process of adopting a cloud solution. It’s as simple as 3 C’s: confine, clover, and cost.
Today, I will focus on the first “C”—Confine.
Before you can determine what cloud strategy you want to implement, you need to narrow down or “confine” the business problem you want to solve with Cloud. Once you have confined the problem, you can begin your roadmap for success with clear goals and expectations.
But how do you confine the problem? I suggest you take a good look at the market forces that are pushing you to consider cloud. Internally, it may be cost efficiency: reducing IT investment or managing staffing costs. Externally, the forces could be government regulations or competitive differentiations that are leading you to consider a cloud solution.
What do a telecommunications company and a University have in common? Well, at first glance, not a heck of a lot — unless you consider their network requirements. After talking to a telecommunications company and a University I found out they both wanted:
To know the exact status of all networking devices…within minutes.
A simplified service contract structure for said devices
To better predict, and budget for, support and upgrades of devices
Reduced network risk, simplified operations, and increased employee productivity.