How to eliminate PLM customization problems?

How to eliminate PLM customization problems?


I’m following strategic visions of the major PLM vendors 2014+ publication by Jim Brown – well known analyst and my blogging buddy for last few years. It started as a publication covering Autodesk, Dassault, PTC, Siemens (vendors listed alphabetically). Last week, Jim expanded his PLM vision publications by adding Aras Innovator to the list. Navigate here to read about Aras 2014+ vision. Aras is well known by their Enterprise Open Source strategy. One of the interesting differentiation I captured in Jim’s article is related to Aras’ strategy to break rules of PLM customization. Here is the passage:

Aras has decided to break the rules [of PLM customization]. They aim to become the PLM company that defies the conundrum, allowing manufacturers to customize their software and still upgrade to future releases without major disruption. They can do this because customers can update the data schema, business rules, workflows, and forms without jeopardizing the integrity of the system. How does this work? Aras’ XML-based, model-oriented approach coupled with their willingness to provide customers with the business flexibility and tools to make it feasible.  Aras has effectively morphed themselves into a PLM Platform with solid core functionality with a built in ability to be extended by customers and partners. To put this strategy into action, they have told me they are “putting their money where their mouth is.” They now include upgrade services as a part of their subscription service. I haven’t seen that from anyone else anywhere, particularly while encouraging people to enhance and modify the package. This is a clear differentiator and makes Aras unique in the PLM market.

PLM customization is a tricky deal. Honestly, nobody is dreaming to make PLM implementation with zero customization effort. It all starts from flexible data modeling, which imply certain level of data customization. Time ago, I posted – Is PLM customization a data management Titanic?  Earlier this year, I’ve been discussing options and reasons on How to de-customize PLM? The story of PLM customization is tightly related to PLM system flexibility data modeling. Typically, every PLM implementation contains some portion of customization that usually done by service organization and/or internal IT department. Lifecycle rules, data import, workflows, integration with other enterprise systems – this is only a very short list of customizations done during PLM deployment. Another huge aspect of customization is related to system upgrades. That one is actually mentioned by Jim Brown in his Aras’ review.

So, is there a way to solve customization problem? In my view, the answer is – it depends. In my view, you cannot eliminate specific implementation activities. Adding of new features and infrastructure technologies (eg. RDBMS) will require certain upgrade activity to happen. However, if you are selling services, the interest will be to optimize this work. Cloud vendors have similar incentive to optimize infrastructure upgrades and maintenance, otherwise operational cost will go up. So, smart technology can optimize cost and customization efforts.

What is my conclusion? Business and technology are going together. To have good business incentive to optimize technologies is always helpful and can put pressure on development organization to optimize cost of infrastructure upgrades. Service based offering (open source and cloud) are two great examples where business interests of vendors and customers are going at the same direction. Just my thoughts…

Best, Oleg


Share This Post

  • Customization has long been a PLM dilemma, Aras’s approach is certainly on the right path only time will tell how effective it will be in practice (there are reasonable limits to any intended model-oriented modularity). I think further openness on all parts (provider and client) could potentially revolutionize how PLM works. So instead of being able to customize on a platform, a particular company would help contribute in return for sharing in the contributions of others. In essence creating a true community, rather than simply a market. Will all companies be willing to work in such a model?

  • beyondplm

    Ed, thanks for sharing your thoughts! I think, return back to community is a good model. Aras is trying to do so. You can think “app store” like innovation is kind of similar to that. Will it work for PLM market? It is a good question. Some high-end customers predominantly not interested to share, since they see PLM experience and best practices as something developed by them uniquely. However, there is a potential customers will be interested to share.

  • Pingback: On PLM (In)Compatibility | Joe Barkai()

  • Pingback: PLM Customization and Cloud Code Editors()

  • Pingback: PLM upgrades, release cycles and legacy software()

  • Pingback: PLM: configuration v customization. Let’s sort it out.. | Daily PLM Think Tank Blog()