PLM Prompt: What Means to Create “Good Enough” PLM?

Those are good. I would also add data integrity because without that what’s the point? You almost always start with dirty data and it is impossible to instantly make it right.

For wide adoption users must see the value otherwise they will fall back to finding ways around the system. I find that some users understand the value right away, and some don’t ever get it. Most are in between.

PS Oleg – great site, very thought provoking.

Cam

So thought provoking that I decided to start my blog 🙂
I probably won’t update as much as you do, but I’ll try to post regularly.

Yep Oleg… Your update rate is awkward for any blogger, me included 🙂

Back in topic: I second Cam’s opinion about data integrity. I have nightmares sometimes about it, though I know IT guys are doing a great work… I wanna add “cross-media”. Your last post about iPhone is the perfect explaination. And Catia/Enovia on Apple computers is my wettest dream…

A good simple list. I guess it all depends on what the sub headings are going to be under each of those. I would push usability right ot the top of the list. If users can’t use it then then won’t, it’s that simple. I would give up flexibility over usability any day. If there was only one simple easy to teach way of doing something or three flexible but comlicated ways of doing something then I would rather go for the simple way every time. As we expand our PLM system we teach one consistent method of doing something. Once users are comforatble we can tech them some alternatives, but to get adoption rates up its go to be simple. As Cam said some people never seem to get it.

Since the question is for “good enough” PLM, I think that Usability and Integration are more important than Flexibility. The phrasing of “good enough” elicits thoughts of a usable system that seeks to accomplish the minimum tasks of a PLM, not necessarily something very flexible.

For a great PLM, I do agree with your listed order. Usability and integration are significantly important attributes and sometimes even a minor usability issue gives a bad overall impression. These minor (sometimes major) issues can very often be overcome if there is flexibility in the system. This puts flexibility at the top. Integration is often a subset of usability, so I put it below usability.

SCALABILITY!.
Just as data and business workflow complexity grows with time, the system should support scalability easily by using J2EE or such robust technology and can be easily upgraded.