So you have decided it’s time to build your private cloud. All you need to do now is sign the check, right? Not so fast. You start doing your cloud due-diligence and find that deploying a cloud solution is going to take more than just installing software to realize the value your organization demands. It is imperative to look at people, process and the supporting technologies based on your cloud model. It’s now time to start thinking about integrating your cloud into your current IT organization. You decide on starting small and adding services over time.
In building your strategy you come across an interesting twist. You have defined both the reference architecture and cloud strategy, but in building your strategy have uncovered some concerns. You’ve identified that you have three ways to install & integrate your cloud. In looking at your options you can:
A) Install your private cloud as a standalone point solution
B) Implement cloud and integrate with your current systems
C)Transform how you do business and install a brand new platform
You now have some architecture decisions to make. What are the right choices for your organization? Associated with each decision are costs and benefits. Solution A is a point solution. Installing a point solution means just that, it is limited to where you installed the cloud. The downside is that you don’t have any connective tissue to the existing systems. With a point solution it could increase your administration costs if the cloud platform doesn't integrate into your existing service management infrastructure.
The second choice is a cloud integrated with your current systems. Integrating your cloud with your current systems gives you the connective tissue with the existing environment. A request for resources will be handled with the current process and procedure you have defined. When you integrate with your existing process and procedures you will have the ability to tie into the current state. If your current state is not optimized then you could be limiting your longer term benefit, but might get a short term gain by being able to realize the benefits while having the ability to upgrade your systems to the future architecture state.
The third option is transformative in nature, but will likely prove to be disruptive in the short term. This solution will have a longer payoff period, but can ultimately provide greater benefit than the point solution or the solution integrated with your current architecture, assuming the current state is sub -optimal.
Many organizations are faced with similar questions and decisions when building their cloud strategy. During the discovery phase, the implementation and integration process has a potentially large impact throughout your organization. The reality is that there isn’t just a one size fits all solution for designing your cloud architecture. Coming up with the right strategy requires a sound understanding of the IT and business drivers for cloud. It is critical to understand your architecture options, and what the implications are when it comes time to integrating, upgrading and supporting your systems. We recommend having a cloud assessment to give you the information you need to make an informed decision.
Choosing the right architectural solution for integrating your cloud platform can provide a lot of benefits such as easier upgrade paths, better long term business value, quicker mean time to repair, and lower TCO. The biggest value is the peace of mind in knowing that you got the facts before making complex decisions that will impact the business for years to come.
You don’t have to make the decision on your own. BMC Consulting Services can help provide the information you need to make an informed decision.
Learn more at bmc.com/consulting
John M. Hawkins is the Chief Services Architect for Cloud Strategy & Planning at BMC. He helps clients create the future state Vision/Strategies and Roadmaps to help them realize that vision