A blog by Oleg Shilovitsky
Information & Comments about Engineering and Manufacturing Software

How many Lifecycles do we need?

How many Lifecycles do we need?
olegshilovitsky
olegshilovitsky
25 August, 2009 | 2 min for reading

how-many-lifecyclesYesterday, two separate article got my attention and brought me to think about Lifecycle. Alternatively, even more, about number of systems claims different lifecycle support. Jim’s Brown thought about QLM Quality Lifecycle Management and TEC article What keeps EAM/CMMS away from PLM“. Why I choose these two is because they are presenting a complimentary story, in my view.

Jim claims Quality is a complimentary process to Product Lifecycle. Manufacturers these days cannot take risks and afford quality issues rising up, so QLM processes need to be adjusted and/or work together with Product Lifecycle. At the same time, Jim mentioned that many of today’s PLM systems doesn’t have QLM capabilities and some hybrid PLM/QLM would be probably interesting combination, we can offer to customers. I’d agree with Jim with PLM system capable of manage overall product lifecycle, we’d better had Quality related processes connected and working together.

If I read correctly TEC, Kurt Chen presents in his article need to tie PLM and EAM systems together and analyze possible ways to do so. These processes represent both sides of product-related activities. First- from a product development side, second- from side of purchasing. What I liked is presenting of “two-sides of the story” of the same lifecycle.

I thought, these two stories is excellent examples to stop considering product-related processes as a something separate. Today’s organizational goals can be achieved only if we will be able to establish single lifecycle to manage all product-related activities in organization across department, divisions and cross-organizational boundaries. The siloed approach won’t work anymore. And I think demand on customers today is to establish such approach.

So, that’s what I thought about “lifecycles”. What do you think? What is your opinion? Do you have similar discussions and/or thoughts coming from your organizational experience?

Best, Oleg

Recent Posts

Also on BeyondPLM

4 6
21 July, 2010

I read MCADCafe article – PLMIG announces a 10-Year PLM Industry Vision. It navigates you to PLM IG (Interest Group) where...

14 January, 2016

I think, most of PLM people are considering the fight about pros and cons of intelligent numbers is only related to...

26 October, 2024

Last week, I attended Autodesk University 2024 in San Diego. I came to share OpenBOM experience of building digital workflows and integrating Fusion data...

16 February, 2011

I want to talk about PLM and Standards today. In my view view, the story of standards is over complicated...

2 May, 2013

Engineers hate PDM. It is an axiom known to all people touching engineering and manufacturing software. Nobody gets up in...

1 April, 2016

PLM software is hard to interact with. I think the hardest part is PLM workflows. Usually very sophisticated it creates...

3 August, 2010

Collaboration is a widely used term, and I found it sometime even overused. Collaborative development, Collaborative PDM, Collaborative PLM, Collaborative...

21 August, 2009

In my view, there is a very strong interest from PLM community to something called “Social PLM”. You probably had...

30 August, 2010

I’m continuing discussions about PDM vs. PLM differences. I’d encourage you to take a look on my previous two posts...

Blogroll

To the top