Do you know what is legacy software? Earlier today, Marc Lind of Aras Corp. challenged me by his twitter status about companies complaining about legacy PLM systems and upgrading. Here is the original passage from twitter here and here.
“a lot of people complains about legacy PLM and a lot of companies that have legacy PLM are throwing in the towel and switching these days”.
The part of statement about “legacy software” is really interesting. Last week, I wasn’t able to update a game on my son’s iPad. After few minutes, I discovered that Apple is not supporting the original iPad hardware manufactured 4 years ago. Does it mean iOS software run on that iPad is a legacy? Good question. At the same time, what about properly functioning ERP software that company runs already for the last 10 years without any plans to upgrade? Is that a legacy software?
Wikipedia gives me the following definition of legacy system:
In computing a legacy system is an old method, technology, computer system, or application program,”of, relating to, or being a previous or outdated computer system.”[1] A more recent definition says that “a legacy system is any corporate computer system that isn’t Internet-dependent.”[2]… The first use of the term legacy to describe computer systems probably occurred in the 1970s. By the 1980s it was commonly used to refer to existing computer systems to distinguish them from the design and implementation of new systems. Legacy was often heard during a conversion process, for example, when moving data from the legacy system to a new database.
Software upgrades is an important topic in engineering and manufacturing. Very often, systems can be in use very long time because of product lifecycle and the need to maintain existing data. It happens a lot in defense, aero and some other “regulated” industries. Also, because of significant investment, the ROI from upgrade can be questionable, which leads companies to keep existing outdated systems in operation. I’ve been posted about problems of PLM customization and upgrades before – How to eliminate PLM customization problems and Cloud PLM and future of upgrades.
PLM vendors are aware about the issue of upgrades and difficulties of software migrations . For long time, industry recognized it as something unavoidable. However, in today’s dynamic business environment, the issue of software upgrades cannot be ignored. Customers demanding flexible and agile software that can be deployed and updated fast. At the same time, changes of business models towards services and subscriptions pushed the problem of upgrades back to vendors.
Earlier this year, my attention was caught by CIMdata publication – Aras Innovator: Redefining Customization & Upgrades. Aras enterprise open source model is predominantly subscription oriented. Which provides lots of incentives for Aras engineers to solve the issue of upgrades and new versions deployment. Here is the passage from the article confirming that:
For several years, the Aras Corporation (Aras) has included no-cost version-to-version upgrades in their enterprise subscriptions, independent of how the solution has been customized and implemented. This is a rather bold guarantee given the historic challenges the industry has experienced with upgrading highly customized PLM deployments. With more than 300 upgrades behind it, CIMdata felt it appropriate to find out how Aras’ guarantee was playing out, and discovered that there was much more to the story than just a contractual guarantee. Fundamentally, Aras Innovator is engineered to be highly configurable—even customizable—without resulting in expensive and complex version-to-version upgrades and re-implementations.
One of PLM software leaders, Siemens PLM is also thinking about What is the best release cycle. The article speaks about SolidEdge release cycle.
A few years ago we moved from an irregular release cycle for Solid Edge, maybe 9 months in one cycle to 15 months in the next, to a regular cycle of annual releases (of course there are also maintenance packs delivered in the interim). I believe our customers much prefer this, they can plan ahead knowing that there will be a significant Solid Edge release available to them in August each year.
At the same time, the article confirms that CAD/PLM vendors are looking how to solve the problem of upgrades. As I mentioned earlier, cloud software model is one of the most promising technical ways to solve the issue of upgrades. It is true, but can be tricky in case both desktop and cloud software are involved. Here is the passage from the same Siemens PLM blog:
Working in the PLM area we try really hard to provide our customers with a good upgrade experience. PLM software is itself dependent on both the operating system and database software, and it has to work with specific releases of CAD software (sometimes with more than one CAD solution for our multi-CAD customers) and with office software as well! Moving PLM software to the cloud could potentially take some of the upgrade issues away from the end user, but PLM software does not work in isolation from your data files, or your other software and systems so I believe there is much work still to be done before the cloud really impacts the upgrade situation for real-world customers.
What is my conclusion? From customer perspective, the best option is to make release cycle completely transparent. In my view, this is really high bar for PLM vendors. Customer data migration, customization and sometimes absence of backward compatibility make release transparency questionable. However, since industry moves towards cloud software and service business model the demand for agile release management and absence of upgrades will be growing. So, my hunch, in the future we will not see “legacy software” anymore. New type of enterprise software will manage upgrades and migrations without customers paying attention. Sound like a dream? I don’t think so. For most of web and consumer software it is a reality already today. Just my thoughts…
Best, Oleg
Pingback: How to migrate into “future PLM platform”?()