PLM vertical PaaS strategies

July 25, 2014

PaaS-plm-large-manufacturing

SaaS, PaaS, IaaS, DMaaS, … I’m sure marketing folks are having lots fun of new xaaS acronyms. The amount of publication about various strategies of services is skyrocketing. EDACafe article – The Platform-as-a-Service Provides European Aerospace & Defence OEMs and Partners with Greater Collaboration Capabilities brings a story of “AirDesign” – the European aerospace and defense industry’s collaboration platform by BoostAeroSpace and Dassault System. The article taste a bit marketing. Nevertheless, I found the following passage capture the rationale behind what AirDesign supposed to provide:

AirDesign drastically reduces operational costs for all partners through a single infrastructure, common exchange methods, open standards and easy access, all without adversely impacting existing information systems. All the primary European OEMs jointly requested and defined this platform in order to facilitate exchanges, support their suppliers’ ecosystems and generate new opportunities with services.

MMT article provides more analyzes on what Dassault and BoostAerospace are doing:

To manage the exchange of PLM data between all partners whatever their systems may be, AirDesign delivers three key capabilities through its digital exchange hub: 1/ The first allows an OEM to organize exchanges in the context of programs and projects, including the delegation of administrative roles; 2/The second is an integrated, secured and automatic technical data package exchange. The traceability needed for complex programs is a native capability, ensuring proper management of large technical files between OEMs and suppliers; 3/The third capability consists of access to a wide variety of services, including converters based on standards or approval services that a partner can use during an exchange.

The set of functionality above aren’t new. Large PLM implementation did it in the past. The problem of standardization and platform cost in supply chain eco-systems is critical. So, it is not unusual for partners to share single enterprise software infrastructure for design supply chain and more.

However, the notion of PaaS (Platform as a Service) is interesting. I’ve been blogging about that earlier – Will Cloud PLM develop PaaS option? and Cloud PLM and PaaS dilemma. It looks like PLM vendors is moving towards more vertical platform architecture. Especially for large companies and business eco-systems, PaaS can provide an interesting solution – standardization and cost benefits. The information about private cloud deployment by AirDesign confirms earlier news about Dassault developing all cloud PLM options.

What is my conclusion? I think we are going to see lots of PLM PaaS variations in a near term future. Large manufacturing companies are looking how to optimize cost and standartize infrastructure. This is an opportunity for PLM vendors to re-establish and sometimes re-develop their legacy systems in a new way. I’m sure lots of ENOVIA applications will be used in announced AirDesign PaaS. Overall looks like PaaS is another way to sell PLM cloud system to large manufacturing eco-system. Just my thoughts…

Best, Oleg

picture credit to MMT article

 

 


Why Siemens PLM can develop PaaS option

July 16, 2014

cloud-paas

PaaS is a category of cloud computing service providing platform and solution stack. This service model is including not only computing infrastructure (IaaS), but also application design, development, testing, team collaboration, integration features, database integration, scalability, security and others. In addition to that, it might provide service management capabilities such as monitoring, workflow management, etc.

As cloud market becomes mature, IT, customers and application development are looking into complete solutions. All PLM vendors are in full swing into IaaS cloud PLM option. Cloud PLM experience brings the need to dig more into nuts and bolts of cloud business. It includes understanding of cost, scale, service maintenance, application development, partnership. So, fundamental question many vendors and customers have is what is the best way to make cloud PLM efficient? Understanding of PaaS option is an important step. I shared some of my thoughts about PaaS and PLM before- Cloud PLM and PaaS dilemma, Will cloud PLM develop PaaS options?

My blogging buddy and well known PLM analyst Chad Jackson tweetstormed what he learned at Siemens PLM about furure TeamCenter platform development. While I’m still waiting for full blog post on Chad’s Lifecycle Insight, the following filtered tweetstorm can give some idea about Siemens PLM platform strategy:

chad-jackson-siemens-plm-tweetstorm

It resonated with my previous thoughts about cloud PLM and PaaS and made me think why Siemens PLM as well as any other PLM vendor can consider PaaS as a right option for their cloud PLM strategy. Here are my 3 reasons to develop PLM PaaS:

1- Agile development.

Vendors should be able to go fast in the development of applications, ability to customize existing features and supporting new opportunities. Businesses are much more dynamic these days. Everyone wants to be agile. PLM vendors too. So, to get up to speed with business, PLM vendors need to have a stable platform to build on. PLM PaaS can be one.

2- Better upgrade strategies

Let’s take marketing gloves off. Regardless on deployment options (on premise; private cloud; public cloud), you need to deal with upgrades. Databases, services, data model changes- this is only a very short list. PaaS can hide upgrades from customer and application developers by providing a stable platform layer. This layer requires less frequent upgrades.

3- Scaling factor and cost.

Cost is important. Cloud is not cheap as many of us thoughts from the beginning. Customers are demanding new business models and optimized cost. The development and customization cost is another problem. Scaling and keeping cost low is also huge challenge. Utilization of enterprise servers is still relatively low. PaaS can answer on the question how to share resources and scale with low cost.

What is my conclusion? Most of PLM vendors took IaaS option as a starting point to develop cloud business. It is okay and will provide important experience from different perspective – technologies, business, user interface. However, IaaS won’t remove fundamental enterprise PLM issues – implementation complexity, upgrade challenges, high diversity of requirements and business changes. PaaS option can become the next logical step to optimize platform and application for agile delivery. It looks like Siemens is making steps towards this direction. Just my thoughts…

Best, Oleg


Why cloud won’t solve CAD/PDM/PLM integration problem tomorrow?

October 17, 2013

cloud-cad-pdm-plm-integration

All roads lead to Rome. Sometimes, I have a feeling whatever discussion happens in CAD, engineering and manufacturing world, it will lead to PDM and PLM. My earlier conversation about pros and cons of having special CAD file sharing tools started here, ended up on GrabCAD blog by Hardi Meybaum here with a conversation about what system should be used in organization to manage data, users and workflows and how to integrate these systems. Here is the passage:

In addition to the cons Oleg brought up I actually see a bigger issue – integration. A good thing about a generic/horizontal file sharing tool is that everyone is using the same system so it’s easy to manage data, users and workflows. Conversely, a manufacturing company might have someone who only needs to access very specific CAD data once or twice a quarter. Does this person really need access to your manufacturing-specific tool to get it? I think overcoming this problem is going to be an important obstacle to address in the next 3-5 years.

Another interesting point raised by Hardi, was the role of VAR is changing cloud/SaaS software role. In the past I discussed the future of PLM VARs last year here – What is the future of PLM VARs? My main point was that technical experience will become one of the main differentiation factors for future SaaS VARs. GrabCAD blog practically in the same way.

The benefit of VARs repositioning within the CAD space is that most of them have offered value implementing rather complicated engineering systems to customers already. They understand the customer well and have software knowledge within the company. I believe the new model for VARs in the next 5 years will be reinvention – some will become software companies providing specific integration like Zapier and others will focus on very specific workflow integrations between horizontal products.

However, let me get back to CAD, PDM, PLM and integration topic. While CAD File Sharing is highly demanded by almost all organizations these days, customer requirements are moving very fast from pure need to share information to questions and requirements how to control CAD data and manage change processes.

In the early beginning, PLM vendors and implementers were trying to get deep associations with CAD roots. This is not true anymore. One of the latest trend is to focus PLM on the business level of the company and how to improve company business processes. In one of my early articles CAD data and PLM, I described this position talking about CAD Rootless PLMs and importance of integration between CAD and PLM.

At the same time, the center of integration gravity is still positioned on integration of CAD and PDM. The complication of this type of integration is related to multi-CAD nature of CAD data. Companies are using different CAD systems. Some of CAD systems can dominant, but you always can find data from multiple CAD systems in every organization. GrabCAD post mentioned that as well. In the early days, PDM vendors were focusing on how to develop plug-ins for every CAD. This is still true for many vendors. However, next trend, in my view, would be future openness of CAD systems toward providing interfaces integrating to many PDM systems. You can read more about it in my post – Multi-CAD integration: Yesterday, Today and Tomorrow .

Last, but not least topic is related to Cloud/SaaS solutions. This is a place where Hardi Meybaum of GrabCAD believe the most. Here is an interesting passage from GrabCAD post:

It will only be solved once there is enough adoption in the general market for the next generation of SaaS CAD tools like GrabCAD Workbench, Autodesk PLM360, TeamPlatform. At that point the integration challenges will evolve.

I can see a clear point of movement to the cloud / SaaS trajectory. However, in my view, despite a significant growths in design domain, co-existence will be probably the right word to describe the reality of coming few years. I want to stress this point – CAD will be the latest application in the list of PDM, PLM and other business services to move to the cloud. What is interesting to me is how vendors are going to support this “cloud transition”. Companies clearly won’t be able to move all in a single shot. You can take a look on how I can see a transition in my blot post – PDM/PLM Evolution: Final Step and Cloud / On-Premises Integration.

What is my conclusion? Integration is a complicated and important topic. However, to think integration will disappear with movement to the cloud is too naive position. Cloud/SaaS can clearly simplify some technological aspects of integrations. However, the complexity of design, data management and processes in an organization will be very hard to overcome only by the change of technological foundation. The "transition phase" will be another reason why vendors and customers will have to deal with integration for coming decade, at least. Just my thoughts…

Best, Oleg


Midsize PLM: Forget old SaaS, new cloud is coming to disrupt you?

August 19, 2013

The technology trends are interesting these days. You think what can be more disruptive than cloud. Indeed, cloud, social and mobile are there major trends and forces to drive innovation in enterprise organizations now. However, here is the thing – I can see more and more confirmations about readiness of customers to go forward with cloud solutions. At the same time, the question that companies and individuals are raising are more towards understanding of "what" cloud means for them and "how" to implement cloud solutions. I raised this question in my recent post – Dassault IFWE and PLM Cloud Switch.

Yesterday, I’ve been reading venture bit article – How SaaS is triggering the rise of mid market companies. Navigate to the article, have a read and make your opinion. It speaks a lot about cloud "hows" in the context of cloud technology trends. It was the first time I’ve seen people mentioning "old cloud vs. new cloud". Here is the passage I found inspiring:

Startup software vendors can take advantage of new technology and infrastructure better than decade-old vendors in this new reality. They have an immense advantage over established players struggling to adapt legacy web 1.0 products to the new paradigm. As Salesforce approaches its 15th birthday, the SaaS market it pioneered so disruptively is itself feeling disrupted.

It sounds like "new cloud" positioned itself somewhat different from bigger cloud providers, by reaching better flexibility, data access, intuitiveness. One of the key elements is usage mobile devices and natural collaborativeness inherited from new mobile applications. Native mobility becomes one of the key advantages of "new cloud trend". It appears not only in the way application can be used, but also in the way application can be sold and implemented. Here is another interesting passage:

The SaaS paradigm also reduces the cost of selling to mid-size businesses. Since products are web-based, they can easily be demonstrated remotely. In addition, search engine and social technologies make it much easier for customers to find software vendors. These inbound tactics combine synergistically with outbound e-mail and telemarketing campaigns, eliminating the need to send a salesperson to each company.

What is my conclusion? The speed of business changes is dramatic these days. Only few years ago, we mentioned cloud pioneers like Salesforce.com as a company on the bleeding edge of technology and business model. It is interesting today, how new waves of disruption are going to open a new decade of cloud applications. Does it mean something for PLM companies and PLM implementations? I don’t think we have an answer. The question about speeding up transition of customers to the cloud solution is still not answered, in my view. Industry was changed by bringing new technologies to revolutionizing manufacturing business these days. What will be the next steps? It is a right time to ask about. Just my thoughts…

Best, Oleg


Cloud PLM and PaaS Dilemma

June 4, 2013

IaaS, PaaS, SaaS… Most probably you are familiar with this abbreviations. These are fundamental layers in cloud computing these days. IaaS stands for Infrastructure as a service. PaaS stands for Platform as a Service and, finally, SaaS stands for Software as a Service. These concepts were around for some time. SaaS is probably one of the earliest and it became a delivery model for many software providers these days. Salesforce.com, Google Apps, Workday – this is a very short list of notable SaaS providers. On the opposite side, IaaS offers virtual computing power – virtual machines, servers, storage, networks, etc. Amazon delivered the most reliable IaaS infrastructure today – AWS. Other competitors are scratching their heads these days trying to understand how to compete with that.

Let me get back to engineering, manufacturing, PDM and PLM. IaaS and specifically AWS became a mainstream for almost everybody. It is hard to find development organization that is not using AWS for some purposes. Massive amount of cloud applications today are dependent on IaaS cloud infrastructure. Some of PLM vendors decided to to leverage the power of IaaS to turn their existing solutions into cloud ones. I covered this topic couple of months ago here – Cloud PLM and IaaS Option.

The part of SaaS is clear as well. We can see a growing number of cloud (SaaS) applications. Notable vendors in PLM are Arena Solutions, Autodesk and some others. The topic I want to discuss today is PaaS. According to PaaS wikipedia definition

Platform as a service (PaaS) is a category of cloud computing services that provides a computing platform and a solution stack as a service.[1] Along with software as a service (SaaS) and infrastructure as a service (IaaS), it is a service model of cloud computing. In this model, the consumer creates the software using tools and/or libraries from the provider. The consumer also controls software deployment and configuration settings. The provider provides the networks, servers, storage and other services.[2] PaaS offerings facilitate the deployment of applications without the cost and complexity of buying and managing the underlying hardware and software and provisioning hosting capabilities.[3]

Here are few examples of notable PaaS providers – Heroku, Windows Azure, Google App Engine, and few others. If I think back to the idea of turning you PDM/PLM application to a platform in a conventional (pre- PaaS world), than I will think about usage of PLM as a platform to develop variety of applications and implementations. If you remember history of PDM /PLM platforms, you probably agree with me that it took a significant effort and time to leading PLM vendors to create platforms that can be easy used and evolve in the future is incredibly complicated tasks. Still existing platforms such as Enovia, TeamCenter and Windchill are complex and hard to use. It made me think more about PaaS and ability of PLM to leverage PaaS in the future.

The following article caught my attention last week – The problem with PaaS. Read this article and make your opinion. According to the article, the central paradigm of PaaS is to provide development and deployment environment to the user. I found the following passage interesting. It describes the problem very well. Take a read.

The central idea of PaaS is the CSP provides a development and deployment environment to the user. True, PaaS abstracts the underlying infrastructure, but that’s the role of the IaaS underneath the PaaS platform. The goal of PaaS is to abstract the development environment details themselves. Unfortunately, building an abstraction at this level is extraordinarily difficult, because developers typically require fine-grained, hands-on control of their development environments. Change a classpath or config file setting or environment variable or any number of other nuts and bolts that make up a coder’s day-to-day work environment, and everything the developer has built will crash and burn.

What is my conclusion? What is the future of PLM and PaaS? It is a complicate task to build a scalable, flexible and expandable PLM platform in the cloud. Some vendors are following this path now and some of PLM vendors are looking how to turn their existing systems into cloud PaaS. I can hardly see how cloud vendors will be able to leverage existing PaaS because of complexity of implementations, integrations and system conflicts. It would be very interesting to see if one of the existing cloud PLM products will turn into scalable PLM PaaS. Just my thoughts…

Best, Oleg


Cloud PLM debates about multitenant models

November 8, 2012

The discussion about cloud PLM is growing these days. Big players are entering the game. Latest announcement made by Siemens PLM about TeamCenter on the cloud just emphasized that PLM cannot avoid the "cloud" game. The list of cloud options for PLM today including a long list of companies – Autodesk PLM 360, Aras, Arena Solutions, Dassault Enovia V6, Dexma PLM from Ascon, PTC Windchil / IBM, TeamCenter and more. One of the questions that always raised by customers and analysts in this space is so-called "multi-tenat model". Usually confusing and raising many debates about what is "true cloud" solution, this topic is indeed very important and provide significant differentiations from both technological and business standpoint.

I’ve made few write ups earlier this year about cloud and multi-tenancy. One of them – Cloud PLM: what do you need to know about multitenancy provides a deep analyzes of all options multi-tenant implementation options. Two additional posts – What Oracle multi-tenancy means for PLM providers and Cloud PLM and IaaS options are discussing various aspects of multi-tenant implementations and cloud infrastructure usage.

Cloud PLM arguments

I can identify two major groups of people arguing about what means "cloud" for PLM and enterprise, in general. One group is saying that cloud PLM is just the ability to put PLM server located in "another place". I agree – this is one of the options. Second group of people is defining cloud PLM as "a service" available from some business applications located "somewhere" outside of customer infrastructure. ASP is not a new option and use d by many vendors in the cloud domain. SaaS option assumes you provide services (only) and make infrastructure (eg. IaaS) transparent.

I suggest to take a deeper look. The following article came to my attention couple of weeks ago – Ask the Experts: What’s the Difference between ASP and SaaS? In my view, it provides good arguments to both of these models: ASP and SaaS. The following two pictures show the diagram of the options. I liked the following passage:

The difference between ASP and SaaS providers lies mainly in the way they manage their respective computing resources… Most ASPs use a single environment for each customer, which means that they provide a specific application that is set up for the individual customer. Each customer uses the business software as a single tenant, and does not share it with anyone else. All application setup configuration, and sometimes even server and operation configuration, is unique for each client. On the other hand, with a SaaS provider, all customers share the same computing resources: servers, application, and database in a so-called multitenant model. So, while an ASP hosts the application environment in its own “building,” a SaaS provider uses the same application environment for all its customers, and they all share the same “building” (see figures 1 and 2)

Cloud ASP Model

Cloud SaaS Model

What is my conclusion? Most of the manufacturing companies are still not well educated about infrastructure and different "cloud options". To understand them is important for IT decision processes. I think to claim buzzwords like "true cloud" or "false cloud" is a fundamentally wrong approach. Both ASP and SaaS models are optimizing resources and cost of the infrastructure . ASP model is more "resources neutral" – you just pull resources by "moving servers outside of your company". At the same time, SaaS (or service model) hides servers resources from your company and provide "the resource consumption view". Such view is generally more focused on business functions and less on IT compared to ASP model. To understand the implication of each of these models on your company operation can help you to decide. Important. Just my thoughts.

Best, Oleg

Image courtesy of [nattavut] / FreeDigitalPhotos.net


PLM Cloud and Software Licensing Transformation

July 18, 2012

The topic of software licensing is one of the most debated in the context of industry transition to the cloud. PLM is not immunized to this discussion, and I can see it happen in many forms in blogs, twitter and other social media forms. I definitely cannot bring all quotes to this post. One discussion that caught my attention recently in Ralph Grabowski’s WorldCAD Access blog. Ralph is quoting Griffin Securities analyst Jay Vleeschhouwer report from the Autodesk annual analyst meeting in New York:

For Autodesk, switching to the cloud is bigger than the ’90s switch to Windows.

Navigate to this link and have read. Don’t miss comments – they are probably as important as the article itself. In addition to traditional discussion about “security” and “cloud” danger, I found few interesting notes on the topic related to the potential danger of usage metering and other “new forms” of licensing. Here is my favorite passage:

Autodesk showed a slide indicating a progression from today’s mix of perpetual and maintenance revenues (for blended desktop and cloud workflows) to a future of per-user subscriptions and usage metering.

Cloud and Software Licensing Shakeout

This statement above made me think about the real transformation which will happen with licensing model in the cloud era. Traditional software licensing and (especially) enterprise licensing models are not suitable into cloud environment. Until now, the vast majority of enterprise software vendors use to license Servers, CPUs and Databases. With the introduction of cloud environment, most of the metrics became obsolete. How you can license server when you, actually, not really interested to know how many physical servers and/or virtual machines are running to support your environment.

Will “usage” become an ultimate licensing model?

Pay as you go. This is one of the famous and well-known slogans of SaaS (Software as a Service world). The wide adoption of this model in consumer web, raised the question if such a model will work well for the enterprise. Here are few pros and cons I can see.

Pros:

- simple model focused on “resource consumption”

- create a feeling or “fear pricing”

Cons:

- in some situations can be unpredictable

- can create a feeling of “license hostage” for customers.

What is a potential alternative to “usage” in cloud licensing? In my view, I can see 3 additional alternatives: capacity (size of the data storage), timeshare and end user (named users) licenses. All these models are implying “usage” in different forms. To pick up the right one (or combination) will be an important step for vendors.

What is my conclusion? One of the most important questions every cloud vendor needs to ask these days is how to create “a predictable licensing model”. Customers are afraid about a potential license hostage. To prevent it, vendors need to focus on transparency of cost calculations and potential alternatives. Just my thoughts…

Best, Oleg


Follow

Get every new post delivered to your Inbox.

Join 252 other followers