Experience and lessons learned to build a cloud solution framework that requires full consideration of business requirements

Because of the dynamic factors of the enterprise and the distrust of it by many enterprises, after weighing the costs and benefits, some may choose to bypass the cloud solution. In this case, Mr. Bobdeutsche discusses the factors that need to be considered when building a workable cloud solution framework, far more than simply it and data centers. In other words, you need to take full account of your business needs, not just technical aspects.

Lessons learned from racing cars

Here's a simple analogy: it's like the 24-hour endurance race in France's Le Mans in June, which has a long history and is called the "Toughest in the world" game. Need to test hardware reliability, drive endurance and good team strategy. It can be said that the world's car drivers and carmakers are looking forward to the peak in Le Mans career. In the 1960s, the Ford Motor Company decided to play and win, which meant replacing Ferrari, the era in the Le Mans GT car's strongest fleet.

As you can imagine, Ford Motor Company assembled a sophisticated fleet (similar to the components of the solution framework in the data center): It includes engineers, automotive design teams, management teams and racing drivers, with such a strong team marching into the 1964 Le Mans Championship. It also spawned a later legend: Ford GT40. Three GT40 attended the Le Mans tournament. Although they did well at the beginning of the tournament, none of them finished the game. Ferrari occupies the top six of the five seats. Well ... so let's think about how the solution framework seems so perfect on paper, why does it backfire in the end?

In view of the final outcome of the tournament, I have to say that Ford is really embarrassing. So the company took a slightly different approach forward. This time, they continue to keep their original GT40 strong team while Ford adds a set of California hot Rodder. These hot rodder not only appreciate the original Ford framework, but also more familiar with the external situation. Know what other elements Ford needs to win the Le Mans tournament. In 1966, Ford's GT40 team won the top three and continued to dominate the next four games.

Cloud computing solutions and Ford's desire to win

You might wonder: How does this relate to the framework based on cloud computing solutions? It is easy to understand that you have such a question. Do you remember the VP of Sales I introduced in a few previous blogs that just contracted to implement a new cloud-based customer Relationship Management (CRM) system? (We assume he is henryfordii, Ford's CEO from 1960 to 1979).

At the end of the discussion, our VP of sales paid little attention to the solution framework, focusing on deadlines, budgets, resources, and selling more parts of the product with less overhead. Similarly, Henry Ford only wanted his GT40 team to win the 24-hour endurance race in Le Mans. Are you starting to see similarities?

What we learned from Ford's 1964 experience is that just putting together a good technology and a component team (the solution framework) doesn't mean your plan is foolproof. Factors beyond the framework can still ruin your plan. So, if the core of a cloud computing solution framework is hardware or software, how would you convince your VP of sales that he needs to be more concerned than just selling more parts to the outside?

Henry Ford's example is really simple. The broader framework of reality clearly influenced his winning the Le Mans Championship in 1964. He needs to find people who are more aware of the reality and who can connect core solutions to viable delivery systems.

Discussions with our VP of sales may also be relatively easy, as he is more familiar with the broader enterprise system than you are. Make him more aware that "oopsies" may hinder the success of his new CRM system. At this point, you simply need to remind him to help him potentially influence a cloud-based CRM system through a series of jobs. Helped him, you are actually helping yourself and your business.

The following are some of the factors you might want to consider:

Considerations for cloud Computing Solution framework

Regional requirements:
Where is your data stored? How do you access this data? Does the data correspond to the laws and regulations of the location of your data center according to industry and data types?
Security/Privacy: Does your business have relevant security policies, and is there a confidentiality policy for relevant important information? Are these policies linked in some way to security issues? If so, how do I handle it?
The development direction of the industry: is your vertical industry tending to share data or keep data confidential and isolated? Will it be clearly defined? Or can it affect the use and sharing of information in the event of a major change? When are these major changes expected to occur?
Enterprise strategy: Is the company's cloud strategy Top-down? Or is it not surprising that your business's cloud plans were initially created solely by the needs of one or more business units?
Team cohesion: Does your business unit work together harmoniously? Do corporate culture and incentives work at the functional level? Have you ever had a successful business cooperation experience across departments? (Cloud computing needs to be the largest level of enterprise consolidation ever) how does an enterprise evaluate the value of an internal IT department?
The cognitive level and standardization of enterprise systems: Has your business ever discussed how an enterprise architecture can be combined with a technology business? Have the relevant standards been established? In the spirit, at least, are you in a business environment that advocates and supports this standard?
Acceptance of reform: any degree of cloud computing deployment is destructive. It will cause some of the original business and business level changes. Has your business ever experienced similar changes? Does your company have the ability to evade risk?
Management: Cloud is destructive and requires your business to be fully considered
Establish a balanced approach to achieving an effective service level agreement (SLA) based on cost factors for business needs
The need to recognize highly virtualized and diversified business models will make monitoring of applications very difficult
Assessment of skills requires environmental management and advice to the outside world (maybe you don't have the talent you need in your current business)
Based on the historical and cultural management of the enterprise, this paper forecasts and makes suggestions on how to deal with these challenges.
In Ford's 1964-year case, no one in the original team thought it would take a slightly different perspective to win the Le Mans Championship.

I think it's the same for those IT companies or data centers. They need to consider the familiar cloud framework, not necessarily directly related to technology. In my opinion, now, you have no choice at all.

(Responsible editor: admin)