infoarch

Currently I'm in a big project to improve the way we organize product development and manage product and project information. In short, this can be called 'Product Lifecyle Management' (PLM). I haven't been following too many experts in this area. So, I've been looking around and started following some of them. The interesting thing is though: not many people in this area are twittering and blogging... I've run into this before: although blogging and twittering can be used by all disciplines, in some areas it just seems to fit better. But anyway, I did run into a person who I find has very interesting thoughts about PLM. It's Oleg Shilovitsky. His blog is 'Daily PLM Think Tank Blog' and he tweets as @olegshilovitsky . Although I can hardly keep up with his posts ;-) I like the way he approaches this area. He's not your regular 'put-everything-in-SAP' guy. He also thinks about relating traditional PLM systems with social media, which...

Some time ago I started thinking about how long product data should be archived? I'm not finding clear answers. I've heard people say: "Store it forever". That's the easy way to 'solve' this issue. Other say: "Store it for (about) 20 years." This sounds more realistic. But then I wonder when to start counting. Is this after the data have been created? Or is this after the product has been released to the customer? Someone else said: "Well, you should keep the product data as long as you have to service the customer's product." Good approach, but how long does the law require me to service a product? Finally, I found there are differences between types of product data. Product data from medical machines is different from software code of a text editor, for instance. This made me wonder: Are there different archiving rules for different types of product data? Is there anyone who can help me answer this question? The standards t...