Will enterprise PLM embrace hybrid cloud?

February 15, 2013

Cloud is trending and we can see more examples of how cloud technologies applies in business. PLM vendors are not standing aside from the cloud. You may see different ways PLM companies are developing their cloud PLM strategies. It starts from public cloud offering coming from Autodesk PLM 360 and Arena and ends up with Siemens PLM Teamcenter leveraging IaaS, Windchill hosted by IBM and Dassault Enovia presenting their solutions as "online system".

What is important is to look on customer realities these days. Let’s face the facts. Almost every manufacturing company these days have a significant amount of enterprise software deployed in house. The larger company you go, you discover more enterprise system managed by company IT. While cloud can be promising opportunity, co-existence of public cloud systems and existing IT can become a problem and impact the speed of cloud deployments and developments. In such context, development of "hybrid clouds" can become an interesting option, in my view.

Earlier today, my attention was caught by Rackspace article – Rackspace Study: The Case for Hybrid cloud. Rackspace is a growing outfit specialized in hosting and cloud infrastructure. Read the article and make your opinion. The following passage explains in a nutshell the idea:

One big trend that has gained considerable momentum with these large organizations is the use of hybrid clouds, which is basically the usage of cloud from an IaaS provider alongside other platforms in order to deliver an application or workload to several users. Hybrid clouds bring a number of different advantages to enterprises, such as the ease of spinning resources up and down , and the cost efficiency of being able to pay for the capacity on an hourly or monthly basis instead of being tied down to a specific billing plan. What’s even better is that it allows for the greatest flexibility when the virtualization technology vendors started offering built in support for moving live virtual machines across a network, as it allows a straightforward means of transitioning applications and workloads between sites.

Take a look on a picture below. Rackspace is building a case for the multi-site hybrid cloud. Here is the explanation provided by Rackspace:

rackspace-hybrid-cloud1.png

Rackspace defines a multi-site hybrid cloud is one that involves attaching existing IT infrastructure to a public cloud provider via a private leased line or a public internet connection. The main advantage to a hybrid cloud is that it allows existing infrastructure, including legacy hardware and code that are otherwise expensive and disruptive to replace. However, this doesn’t come without a catch, as it greatly limits control over geography and may result in increased latency as distance between sites increase, not to mention includes additional time and expense meant for provisioning network connections and reliability of inter-site communication, when compared to pure cloud implementations.

I found this idea interesting. Every IT in a large organization is looking how to optimize cloud deployment without disrupting the existing IT servers rooms. Hybrid cloud can be a good solution for that. Another aspect is security. In my view, hybrid cloud can provide some advantages to IT and large companies to keep some their servers more protected.

What is my conclusion? IT is a blocker to cloud technologies in many companies these days. Even if IT understands the value of the cloud technologies, it provides too much disruption to existing IT infrastructure and future strategies. So, Rackspace is spot on. Hybrid cloud can be a potential way to mitigate a potential concerns of IT about public cloud. Note to companies looking for PLM solutions. While public cloud can provide a clear strategic advantage in terms of resource optimiaztion, Hybrid cloud can be an interesting option and intermediate steps towards exploration of cloud technologies for larger manufacaturing firms. Just my thoughts…

Best, Oleg


PLM Cloud: Dedicated, Private, Public

February 1, 2011

The conversation about cloud is trending these days. Earlier last week, duringSolidWorks World 2011, I had a chance to share my opinion about cloud application development with many people there. SolidWorks was “talking about cloud” a lot during the past year. Last year, I read a nice review of platform shifts and online security from SolidWorks’s co-founder Jon Hirschtick published on SolidWorks blog. Actually, new SolidWorks CEO, Bertrand Sicot, put some clarification behind SolidWorks cloud program during the last event. Despite the fact everybody talks “cloud”, I found a lot of confusion around the cloud topic especially with the notion of different “types of cloud” environment.

Cloud: Server + Network + Virtualization

The best short definition of the “cloud” I’ve heard over the past few weeks was the following one: cloud means “not here”. I found it may be a bit over simplification. I found very meaningful to talk about cloud in terms of servers, network and virtualization. I can see servers is something that remains the same regardless on the notion of company IT as well as the cloud. However, in the case of IT option, servers are located in the company IT data center. Cloud can move these servers out of your company IT data center room. Network is another element that actually bridge between our traditional understanding of IT and cloud. In the past, we operated with terms LAN and WAN. Today the Internet is included into the network scope. However, network remains the same. Another topic is Virtualization. This is not an absolutely new topic, but getting a new notion these days. The ability to make a virtual environment isn’t new and this is not invented by cloud. However, this ability is getting new meaning when multiple virtual environments are able to run on physical servers over the network. Depending on the server location we differentiate between dedicated, private and public clouds.

Dedicated Cloud

This is simple and, in my view, very similar to traditional corporate IT environments. You still have a physical instance of the server. However, the server will be located “not here”. This practically means the outsourcing of physical servers from corporate data centers.

Private Cloud

The next step in “not here” option. In addition to outsourcing servers, you can run multiple virtual environment on top of physical server boxes. You can also have a firewall option. So, this “private cloud” environment will be a bunch of virtual machines running on top of physical server boxes.

Public Cloud

This option is probably the most interesting. Cloud providers (i.e. AWS, Rackspace) can provide virtual servers running on top of “some servers” located “not here”. However, in this case, you won’t be able to control physical boxes. This option can provide a maximum of elastic cloud capabilities. However, it brings a compromise with regards to security options.

No Agreement About The Cloud?

I still cannot see an agreement between different players on the market of cloud computing. On the following video, you can see how Cloud is explained by salesforce.com – the most clean and straightforward definition, in my view.

However, life is not as easy as it presented on salesforce’s video. To prove that, you can join this fascinating video of Larry Allison talking about his perspective on cloud computing.

What is my conclusion? I think we are in the middle of cloud transformation. Still the definition, terminology and lots of other stuff can be modified in the next few years. I’m expecting some marketing buzzes to go away and some practical definitions to get in to clarify what means cloud for the enterprise, in general, and specifically for engineering and manufacturing software. Just my thoughts…

Best, Oleg


Follow

Get every new post delivered to your Inbox.

Join 115 other followers