Is public cloud reshaping PLM landscape? Time to re-check…

March 6, 2015

plm-cloud-landscape

The question how to implement PLM cloud is one of the most confusing when it comes to the decision about choosing one of available PLM solutions on the market today. The time when PLM vendors used "cloud" as a differentiation is over. Most of PLM vendors are comfortable with "cloud" word and the number of companies considering cloud as part of their PLM strategy is growing. How to decide what is the right cloud strategy for you? The dilemma of public vs private cloud is one of the most challenging for many companies.

My attention was caught by ReadWrite web article – You Think Private Clouds Are More Stable And Agile Than Public? Think Again. The article provides a set of good arguments for public cloud option. Here is my favorite passage:

Of course, your CIO’s job is only truly threatened by the public cloud if she chooses to fight it, or mindlessly continues to believe she can build a better cloud than Amazon, Google, and Microsoft. For 99.999% of enterprises, building your own cloud or data center may be a comforting way to stick with old habits, but it’s generally going to be the wrong decision. While there are certainly workloads that will perform better or need to be secured within the four walls of your firewall, the reality is that most infrastructure belongs in the cloud.

No, You Can’t. It’s a convenient fiction that public cloud is unreliable compared to private IT. But let’s be clear: it’s fiction, not fact. Here’s the reality on public cloud up-time: last year Amazon Web Services managed 99.9974% uptime despite hefty growth and unparalleled pressure on its infrastructure. Google was even better at 99.999% uptime. (Microsoft Azure performed a bit worse, though still quite well, according to the Cloud Harmony data.)

In lights of this article, I decided to make a check and see what cloud options are supported by different PLM vendors. Here is a short summary of my discovery (alphabetical order of vendors).

1- Aras PLM is supporting Azure public cloud and, in addition to that saying that Aras is capable to run on any cloud infrastructure (public and private). Here is the link to Aras website.

2- Arena Solutions is cloud solutions. There is no specific information on the website about public vs. private options. My assumption, Arena is public cloud.

3- Autodesk PLM360 is cloud only solution. There is no specific public vs. private information on PLM360 website. My assumption PLM360 is public cloud.

4- Dassault Systems announced to support all cloud options by 2015. See my blog about it. I cannot find a link to a specific cloud configuration available for the moment. The following link presents a list of ENOVIA on the cloud products.

5- Oracle Agile PLM is available via hosted environment. The link with more information is here via Oracle partners. I wasn’t able to find specific information about public vs. private cloud options. More information is here.

6- PTC PLM cloud is supporting both private and public cloud options as you can see it from PTC website. Here is the link, which presents PTC cloud portfolio stating private instance for both premium and enterprise cloud options.

7- SAP cloud applications website is not providing any link to PLM solutions. At the same time, SAP PLM website has zero references to cloud solutions.

8- Siemens PLM is supporting IaaS based cloud deployment. According to the information on the following link, TeamCenter is compatible with Amazon Web services and future support is planned for IBM and Microsoft clouds.

What is my conclusion? Most of PLM vendors are supporting public cloud. It is a real change and it just happened over the past 2-3 years. However, devil is in details. A specific architecture of cloud solution can make a difference. In the past, I put several articles discussing details of cloud technologies. The following link can be a good starting point to discuss definition of true cloud PLM solution. In a nutshell it comes to 4 things – available on demand, hosted, elastic, global access. Just my thoughts…

Best, Oleg

Image courtesy of ddpavumba at FreeDigitalPhotos.net


When BOM is not BOM

December 17, 2014

walks-like-BOM-quacks-like-BOM

Bill of Materials (BOM) is a central part of everything in product development. Sometimes, people call it product structure. Manufacturers are using BOM to define list of raw materials, parts and sub-assemblies with corresponded quantities need to manufacture a product. This is over simplistic definition. As usual, devil is details and BOM story is getting quite complex. Depends to whom are you talking, people see a different aspects of bill of materials – sales options, design hierarchy, product configurations, manufacturing process, service parts. Many systems are defining BOM differently. It depends on their roles and functions in overall product lifecycle.

In one of my recent articles – Thoughts about BOM ownership, I discussed some ideas about how BOM can be shared among organizations and enterprise software tools. That was my attempt to think about how to resolve a conflict between two major BOM stakeholder – Product Lifecycle Management and ERP systems. The BOM management landscape in the organization is complex. In my view, companies are not ready for a single BOM management tools – it was my observation 2 years ago.

At the time a major BOM master ownership dispute is between PLM and ERP vendors, I can see an interesting trend which can put some lights on how PLM companies are articulating their BOM strategies.

Dassault Systems ENOVIA is coming with their "zero BOM error" strategy. I posted about it earlier – PLM and Zero BOM errors: the devil is in details. In a nutshell, ENOVIA is trying to improve process of Bill of Material generation by direct connection between CATIA design and product structure. In my view, it might lead to potential formal elimination of EBOM, which will be replaced by a bundle of design and engineering information. Practically, product structure in CATIA/ENOVIA will represent everything that happens on engineering level. According to ENOVIA strategy, it will eliminate errors between design and engineering.

In parallel, I’m observing the way BOM is positioned by Siemens PLM. Teamcenter blog – Introducing BOM management speaks about BOM information as a vital part of many processes supported by PLM. I found interesting how "BOM management" term was replaced by "Product definition". Here is the passage:

I just noticed that as I am writing this I am using the words “bill of materials” less and “product definition” more. I would go back and correct – I wanted to keep it a surprise! But I think it’s ok – it helps me get to this next part. To us, it has become abundantly clear that one of the problems that come up when you talk about bill of materials (BOM) management is that the scope of what people might mean is so broad. To call all those things listed above “BOM Management” is not sufficient. We’ve collected these capabilities into an umbrella we call the Integrated Product Definition. This is an area where we have been leaders, and it continues as a high priority for us – we have the breadth and depth to address these issues like nobody else can.

In both situations, I can see a strategy by PLM vendors to redefine BOM and bring up the extended value PLM environment for customers. This is a very important transformation in my view, since it helps to streamline processes. The problem of synchronization between design and engineering environment is well-known and not solved in many companies. Teamcenter is connecting BOM management into varietly of topics such as part management, master data management, configuration management, coordinate change and variability and others. It helps to create a solid platform to manage product data.

However, the biggest fight over the BOM is between PLM and ERP environments. Engineering.com outlined it in their article – The next big boom in PLM is a battle over MBOM ownership. Muris Capital Advisors outlined the sam conflict in the blog post – The Battle for BOM Control. According to Bruce Boes of Muris Capital, service integrators will play a leading role in making alignment between PLM and ERP and forming BOM master model. Here is an interesting passage:

We predict that System Integrators have a unique opportunity and from our recent experience, the desire to bridge the gap and add value during integration with the BOM as a key point of integration. In doing so they open the market for process consulting and integration services surrounding the master model concept.

The last one make sense. In many PLM implementation projects, SI teams are actually leading development of PLM-ERP integration on site or using different middleware or integration toolkits. Unfortunately, the cost of these implementation is high and overall process is very complex.

What is my conclusion? PLM vendors redefining BOM by tight integrating of product information into development processes. From what I can see, both Teamcenter and ENOVIA are trying to redefine Bill of Material (BOM) as a wider topic. This is an interesting strategy to fight over MBOM ownership. Integrated "product definition" can help to streamline processes between engineering and manufacturing. However, the end game should be total BOM experience including all manufacturing aspects – manufacturing process planning, cost and orders. The last one brings PLM-ERP integration topic back on the table. Just my thoughts…

Best, Oleg


How to migrate into “future PLM platform”?

December 6, 2014

plm-platform-migration

One of the topics I touched in my yesterday post about future PLM platforms is platform migration. The ability of customer to make a move is significantly dependent on how existing environment can be migrated. You can catch up on some of my earlier thoughts about PLM migrations by reading the following posts – PLM upgrades, release cycle and legacy software; PLM migration and product data rock-n-roll; PLM cloud and future of upgrades.

Most of large manufacturing companies (and even smaller companies) already made some sort of investment in PLM products. What is ROI of move to a new platform? How to calculate it? How not to get troubled by supporting multiple versions of applications and environment? These are good questions. Customers and PLM vendors are equally interested how to manage it in a right way.

My attention caught Dassault Systemes’ 3Dperspective blog post – Top Three Considerations for Planning Your Move to the 3DEXPERIENCE Platform. It speaks about how customer can migrate into new 3DEXPERIENCE platform. Here is an interesting passage:

The same data model and business process rules that power the 3DEXPERIENCE platform also powered the ENOVIA platform. In fact, the same basic approach also powered the MatrixOne platform. This is why so many of ENOVIA’s current customers have been able to successfully upgrade since their first implementation in the mid to late 1990’s.

The following picture shows the history of 3DEXPERIENCE platform evolution. It basically means that the say foundation platform used by all MatrixOne and ENOVIA customers and migration is effortless. I’m not sure if I’m happy to know that the same data technology used by all generation of systems from mid 1990s. However, it is clear benefit for customers looking how to migrate data between different versions of MatrixOne and ENOVIA V6.

3D-experience-platform-evolution

Dassault System’s rival – Siemens PLM and its TeamCenter platform also has long history of transformations. I didn’t find specific public references on compatibility between data models and application among TeamCenter versions. However, the following article from Tech-Clarity blog by Jim Brown presents an interesting diagram of TeamCenter evolution – Siemens PLM vision 2014+.

TeamCenter platform evolution

More information about evolution of TeamCenter can be found in the following CIMdata document – TeamCenter “unified”. The following passage speaks about “migration” issues:

Siemens PLM will continue to support Teamcenter Engineering and Enterprise for those customers that have them in production. Importantly, with each release of these older products, they have updated the underlying architecture and technology so that when a customer decides to change, the transition to the unified Teamcenter solutions will be easier. They have also developed a robust suite of migration tools that can be used when moving from earlier versions of Teamcenter products to the unified platform.

What is my conclusion? The migration is a complex topic. It is probably one of the most important topics that will define ability of large vendors to move into bright future of next generation PLM platforms. Regardless on what platform customer is going to move, migration will have cost that must be calculated and validated. The idea of “federated platforms” brings some promise of minimizing of migration cost. However, the mechanics of this process is not very clear. At the end of the day, data must be brutally dumped out and transferred. Application migration is even more complex. Users must be re-trained. All together, it is not a simple task. Just my thoughts…

Best, Oleg


PLM Vendors and Tunnel Vision

November 11, 2014

plm-tunnel-vision

I’ve been following Dassault Systems 3DXforum this morning. Thanks for technology improvements these days you can be almost present at the events by combination of live streaming and social media communication. The first presentation by Bill Taylor, Fast Company editor struck me by mentioning of the idea of Tunnel Vision. I took a trip to Fast Company website. Navigate to the following link to read Six Ways to Prevent Corporate Tunnel Vision. In a nutshell, I can see tunnel vision as a sort of decease that keeps company in the eco-system of existing business boundaries. At the same time, business is getting so disruptive these days that focusing on a known boundaries, suppliers, partners and business models will crash you eventually. Here is my favorite passage:

Such upheaval is evident everywhere in the business world today. Did you know that big-box retailer Walmart now competes with Comcast, and Netflix for movie streaming on TVs? Or that a business-to-business network equipment giant Cisco now competes with Kodak and Sony for consumer camcorders? Most market incumbents stick with their current products, business models and industry for their entire existance, such that they don’t see opportunities to move—or the risk of new entrants. Such tunnel vision presents a tremendous opportunity for savvy executives looking outside their current base to grow revenue or maintain leadership.

It made me think about PLM vendors attempts to think out of the box by pushing boundaries and challenging current paradigms. If you had a chance to read my yesterday blog, you can see how Siemens PLM is pushing PLM-ERP boundary with the strategic objective to develop fully digital manufacturing and take over mBOM. The comparison of engineering and manufacturing performance with Google self-driving cars was pretty bold. At the same time, you see how Dassault System is innovating into multiple domains by pushing CAD file paradigms introducing “Zero file” strategy and, as I just learned this morning, very much focusing on experience. PTC is looking how to expand their horizons with IoT strategy and services. The last, but not least – Autodesk is focusing on cloud as a strategic differentiation in PLM.

PLM vendors are clearly coming to push existing PLM boundaries. I’ve been trying to map PLM vendors’ strategy to six ways to prevent tunnel vision – business models, encroachment, simplification, total customer, next wave, distribution. I think there are bits of these ways in everything PLM vendors are doing. However, I want to come back to the one of the slides I captured – Apple Lazarus Strategy.

apple-lazarus-strategy

Apple repeatedly outsmarted competitors by introducing revolutionary products in the domains of other companies by providing new experience, combining services and new design. PLM companies all have their strengths these days. However, in many situations, PLM implementations are all look very similar if go down to nuts and bolts of business.

What is my conclusion? PLM companies are innovating to change traditional boundaries of what we know about PLM. My hunch, we are still in a very beginning of PLM disruption. I want to bring Marc Andreessen’s talk about competition and market -“The common theory is that you want to be first to market, but actually you want to be last to market and close the door [on that industry] so no one can come after you“. So, from that standpoint, it is interesting to see who will become last to PLM market. Just my thoughts…

Best, Oleg

picture credit


PLM vendors’ fight over BOM will require to solve data synchronization problems

November 10, 2014

data-links

Engineering.com article by Verdi Ogewell earlier today is introducing a next step of PLM vs. ERP battle for ownership of manufacturing BOM. Navigate to the following link to read a very provoking interview with Siemens PLM CEO Chuck Grinstaff who says – “PLM should take over ownership of the manufacturing BOM too“.

I’ve been writing about the complexity of manufacturing BOM before. You can refresh your memories with the following two articles I wrote earlier this year: Manufacturing future will dependent on solving old PLM-ERP integration problems and Manufacturing BOM is the next cool thing in PLM.

BOM topic is fascinating and incredibly important for PLM companies. It boils down to the ability of PLM to control the complexity of variety of product definitions. The complexity of modern manufacturing environment is skyrocketing. Think about a combination of multiple disciplines involved into the process of design, engineering, manufacturing and support. Mechanical, electronic and software components are tightly integrated to produce modern airplanes, cars and other highly sophisticated products. However, to solve design complexity is just a beginning of the road. The next huge problem is to solve manufacturing problems. It all comes to manufacturing planning, procurement and shopfloor control. After, eventually, you end up with the result, which is represented by “as built” product data, support and maintenance systems.

To demonstrate complexity of BOM transformation I created a diagram below. What you can see below is different views of product data. It usually represented as a different views of Bill of Materials.

plm-bom-data-synchronization

The following quote from Engineering.com article is one of my favorite to describe the importance of product data modeling. According to Chuck Grinstaff of Siemens PLM:

How important is the BOM issue among businesses? ”Incredibly important”, claims Chuck Grindstaff, and it’s not just a matter of semantics, ”The real issue around the Bill of Materials, whether for engineering, for manufacturing, for test or for procurement, is that each of these views of the product are important to the consumer of the BOM. Every view of the ‘bill’ needs to reconcile to other views and must remain accurate within the context of the total product during each stage of development. We believe that each of these viewpoints needs to be configurable from a common definition; from a single source of truth into the context for each of the engineers. For that reason it’s important to get it right. You can call it ”a battle”, yes, but the point still is that a PLM system is the best environment to manage this complexity.”

PLM vendors arguing towards full control of all aspects of BOM by PLM platforms and tools. The main battle is with ERP systems. Historically and traditionally, ERP companies are controlling part of product data starting from manufacturing planning and going future towards procurement and as built representations. It created well-known status of engineering vs. manufacturing balance. However, future demands of deep manufacturing integration brings PLM vendors to think that to take over MBOM (or more specific, manufacturing planning BOM) will deliver better solution for product complexity management.

The desired status for PLM vendors is to push ERP down towards procurement only and manage manufacturing BOM as part of PLM database. Here is another passage from Engineering.com article quoting Peter Billelo of CIMdata explaining why it can be reasonable from PLM vendors’ standpoint:

”ERP solutions generally do not actually optimize or have development tools for defining what the manufacturing BOM is. They just focus on executing a defined Bill of Material. So if I look at what Siemens is doing they are based on developing what that mBOM should be and optimizing that BOM. Quite frankly I don’t see any of the ERP vendors spending much time, if any time, at all at actually doing that. That said it makes sense for Chuck to claim the ownership since they have the tools to make changes, analyze and optimize the BOM.”

Engineering.com article made me think again about complexity of data management and integration in product development. It is certainly complex thing to manage multiple aspects of product data – design, engineering and manufacturing. To ensure data accuracy, both PLM and ERP systems must be well synchronized, which requires multiple very complex data transformation. The “sync” is king of the road on the PLM-ERP highway connecting engineering and manufacturing organizations.

Current enterprise data management paradigm is based on the RDBMS architecture that fundamentally provides a storage for all aspects of product data. TeamCenter is probably one of the best systems to support the complexity of product data representation. By moving manufacturing planning BOM to TeamCenter (or other PLM system), PLM vendors can decrease complexity of data synchronization between two complex views – engineering and manufacturing planning. ERP system role in this situation will be limited to procurement function and management of master production schedule.

However, Siemens PLM is not alone in their desire to take control of complete product structure management and all aspects of BOM. My earlier article – PLM and Zero BOM errors speaks about how Dassault Systems ENOVIA strategy to simplify the complexity of BOM synchronizations between design and engineering environment. This is a bit different aspect, but still represents the desire of PLM companies to solve BOM synchronization problem.

What is my conclusion? The problem of data synchronization between different BOM representations is a real one. The level of complexity is huge. PLM companies are trying to leverage their sophisticated data platform to control the overall product data complexity. The fight is two fold – technical and political. The heart of every CIO is usually with ERP system. PLM companies need to think how to deliver technologies to solve the level of integration complexity. In my view, this is a key to win MBOM battle. Just my thoughts…

Best, Oleg

photo credit: elcovs via photopin cc


How PLM vendors will develop next security technologies

September 22, 2014

future-security-tech

The world is a scare place today. Every day we hear about different security problems – very large retail network informed me that their payment system was breached; large organization informes that customer databases with account information leaked, proprietary photos of celebrities available for general public, credit card numbers compromised. You can continue this list…

If you are responsible for IT organization, you should be scary to death. Think about engineering and manufacturing organization. How can you insure the protection of sensitive information assets? The time when a potential solution was just to cut a network cable into engineering working room is probably in the past. Even if you do that, mobile devices, global environment and need for supply chain access will simply put your effort in a trash can. EBNonline published a very interesting infographic called – The iPhone 6 Saga. It presents Apple’s global supply chain. I have no specific information about how Apple support security in their engineering, manufacturing and supply chains systems. What is clear – security is not optional there.

Security is well known topic in PLM community. Manufacturing companies are afraid of IP leaks for their most important intellectual assets. The question about how to protect data is on the top of the list when you evaluate PLM system. Introducing of cloud technologies and cloud PLM systems just raised the sense of urgency towards protecting highly sensible engineering and manufacturing assets.

Security of information in PLM system is multi-dimensional problem.. These days vendors are very vocal about their commitment to insure information is secured. It is easy to find this information available from vendors’ website and published white papers. A very simple Google search for “PLM security” returned a bunch of documents from Aras, Autodesk PLM360, Dassault Systems,  Siemens PLM, Oracle Agile PLM and few others. Take a look on links and draw your opinion.

It made me think, security management is not a topic that can be covered by one vendor. In modern manufacturing world, you hardly can find a company that using engineering, data management and manufacturing software from a single software vendor. The situation won’t be different in a future. It means manufacturing companies will have to insure security of sensitive IP. My hunch, software vendors will have to talk to develop future security technologies and systems together.

My attention caught THEINQUIRER article Google, Dropbox and others launch Simply Secure to ensure open security. Simply Secure is an organization that aims to work on how to solve the problem of security in an open source community.

A collection of firms and internet thinkers have gathered under a Simply Secure banner and promised to make security and privacy tools that protect and serve. Google and Dropbox are players in the Simply Secure support group and are joined by the Open Technology Fund. Together they all hope to address web users’ concerns about their content and connections. “Internet software links us to our friends, allows us to transact across oceans, and forms a digital space for culture and society. Because these technologies provide forums for sensitive discourse and expression, we are all concerned about their security and privacy.

The world of product lifecycle management is very competitive. Vendors are in a constant search how to differentiate their solution. However, security technology is a thing that can benefit a community of customers to adopt technologies and to work together. Modern enterprise software is quickly adopting best technological practices and tools coming from open source and web world. Security best practice can be next place where adopting of some industry and open source standards can be beneficial.

What is my conclusion? Security is a big deal. By developing future security technologies and adopting some well known best practices, PLM vendors can raise the bar for how they can protect customers from security breaches. The world around us is highly connected these days. To solve security problems is not an optional thing. It impacts every company in modern global manufacturing world.

Best, Oleg


CAD, PLM and Top 500 cloud app vendors list

September 5, 2014

top-cloud-apps-cad-plm-500

The cloud is growing. Few years ago, some of us had a concern if cloud is fad and it will over fast. Since that time, we can see many new companies in cloud space as well as many companies turned their development efforts completely towards the cloud eco-system.

If you like research, ranks and comparison of vendors, you may find the following list of vendors interesting. Apps Run The Cloud web site published the list of Cloud Top 500 Applications Vendors. You can see list of companies and detailed information about top 50 vendors for free. More detailed information requires subscription.

I’ve been trying to see what companies from CAD/PLM space made it to the list. Here is the list of companies with rank (assigned by Apps Run The Cloud) and domain (CAD or PLM):

120 – Autodesk (CAD)

158 – Altair Engineering, Inc. (CAD)

291 – Dassault Systems (PLM)

377 – Arena Solutions (PLM)

407 – Siemens PLM software (PLM)

What is my conclusion? Cloud is here to stay. The question is not "why the cloud?", but "how and what cloud vendor to choose?". I’ve been blogged about it before – PDM/PLM: Why the cloud? Wrong question… The growth of cloud software is fascinating. The fact 3 top CAD providers are in the list confirms the commitment of companies to cloud strategies and development. I didn’t find few names from CAD/PLM domain that I expected to see. I hope we will see more analysis and comparison of cloud strategies and cloud platforms in CAD/PLM space.

Best, Oleg


Follow

Get every new post delivered to your Inbox.

Join 272 other followers