PLM ART & Science

Have you seen the article "All changes should be free!"?

noreply@blogger.com (Peter Storti) — Fri, 06 Mar 2009 00:00:00 +0000

Are there times when you see something that makes you say "HUH?". Well I was looking at some discussions on a link-in group and came across a note about this article "All changes should be free!" -By Ana Kacarska, Product Manager at Seavus.

http://www.linkedin.com/news?viewArticle=&articleID=26536024&gid=89884&srchCat=CMPY&articleURL=http%3A%2F%2Fpmtips%2Enet%2Fchange-management-free%2F&urlhash=dx0N&trk=news_discuss

I have been accused of exaggerating to make a point and I would expect that has been done here. So I don't want to be the pot calling the kettle black but following this approach sounds very irresponsible. Project management and change management are not the villians. If you have all the time & resources in the world (exaggertion) then you by all means try this. You need control of enterprise projects so that multiple groups can work in parallel toward agreed upon objectives. I do agree that changes are good and continuing with a plan where changes are needed is bad but giving users carte blanche to make changes is not wise. Increased costs and schedule delays do not make happy customers (or bosses). "All changes should be free!" is alot like giving your 16 year old son the keys to a Corvette and saying go have a good time. It will probably not end well.

What makes PLM so powerful?

noreply@blogger.com (Peter Storti) — Wed, 25 Feb 2009 20:01:00 +0000

The power of PLM is its inherent ability to model the business environment. This makes PLM straightforward and rewards simplicity. The items you include in a PLM system should be present in the business processes: drawings, models, parts, product structure, requirements,... The "art" to PLM design comes from making sure that you don't create conflicts in your data model. A classic example is creating 2 PLM data items for equivalent business items: if for instance one business unit calls their parts "part" and another calls theirs "component". Any attempt to use common parts, reuse assemblies, or report on structures is going to be much more difficult (possibly impossible in the short term). Now this is an obvious example and most people will understand the problem here but there are many more subtle occurences and managing the PLM data model is a crucial task.

Welcome Aboard

noreply@blogger.com (Peter Storti) — Fri, 20 Feb 2009 02:42:00 +0000

Welcome my name is Pete. I have been working in the PLM field for the last 20 years. It has been very interesting watching PLM develop. In the beginning there was Kalthoff, if you attended a Kalthoff conference you qualify as an old timer. At the early conferences we had conference sessions to debate what acronym to use - the result was PDM. The technology PDM was built on has tremendous potential which is one reason it grew into PLM. The technology is maturing and the business vision is expanding. I am going to use this blog to reflect on this growth, where it may be going, and what additional potential there is. Please feel free to comment on my thoughts or suggest additional topics to discuss.

I look forward to making your acquaintance, Pete