Talk:Product life cycle management
From Wikipedia, the free encyclopedia
A Wikipedia article on "Product Lifecycle Management (PLM)" has a very similar title but very different contents and scope.
This "Product Life Cycle Management" article has contents and scope much more in line with what I was expecting for this title. The other "PLM" article seems too narrow in focus and too IT-oriented.
Could someone provide a justification for the two similar titles and a short description as to how they differ?
--Gary Walker, gwlucca@yahoo.com
Contents |
[edit] 'wikipedia subject bias'
I find this phenomena prevalent of wikipedia and extremely frustrating.
When you find two terms that appear to be alike the solution is not to merge the terms or relace one with another, the solution is to discover why two terms exist by conducting research! What is being demonstrated is what I would called 'wikipedia subject bias' where the definition of terms on wikipedia is biased toward the subject discipline of wikipedia users with a complete disregard for the academic community as a whole from whom these 'rejected terms' originate. These terms exist for a reason! If one investigates why, one might discover a plerothra of encyplopedic information....
Firstly academics use these terms differently for a reason and they don't write their definitions for the terms they use in textbooks of other disciplines.
The act of wikiepedia users merging articles of similar terms that are used in different disciplines is analogous to the geographer consulting a physics textbook to look up a definition. We need to be inclusionist and stop merging terms so that we allow specific content to develop. There is nothing wrong with wikipedia being specialised, the last thing we need is to be generalised. Quite simply, subjects often have different definitions of similar concepts, it is like that for good reason and wikipedia shouldn't be trying to change what the academic community has chosen to be. Supposed 11:35, 15 May 2006 (UTC)
[edit] I agree
I agree, I don't think that this should be merged with Software Life Cycle. I am an IT professional, and even I understand that our definition is too narrow for this topic. These topics should not be merged...simply referenced.
-
- The differentiation has been noted and is being worked. Talk:Product_Lifecycle_Management and more recently Product_lifecycle.
-
- 'wiki' is a computational phenomenon despite being fed by humans (after all, those beings meet only in virtual space as far as I can surmise (there are some sys admins somewhere on the planet touching actual hardware)). Things like PLM actually deal with processes that touch matter thereby humans.
-
- 'software' is only one type of product, though in many cases it has a very wide touch (let's list the ways!!!). jmswtlk 22:06, 4 June 2006 (UTC)
[edit] Advertising should be what?
the section breaks off halfway through a sentence. I'd fix it but I am not sure what advertising should be. Came here as a user to read some stuff on hte subject. I did flag it for cleanup!
Elinruby 13:48, 20 November 2006 (UTC)elinruby
[edit] Lessons of the PLC
In my opinion, this section adds to the content of the current page and lends some contextual connection to Product_Lifecycle_Management (a relative newcomer (even if it's a rework of former efforts) that is enabled by general advances, such as computer science, applied science, materials, manufacturing, ...
It seems to be oriented to the consumer goods. One can argue from an entirely different framework, namely technology (computers, cars, military jets, commercial airplane programs) where there is noted obsolescence (yet even old aircraft sit on the desert awaiting some future fate, I'm still using an antiquated I386 now and then)). Perhaps, it's these types that motivate the PLM thrust.
Could we title the Section "Analysis" and talk lessons, futures, and related?jmswtlk 21:45, 4 June 2006 (UTC)
[edit] Unit cost line not correct
In the graph provided, there is a subtle but important detail overlooked. As product enter the "decline stage", volume drops and costs INCREASE. The model here shows decreasing costs but that is more often not the case. During the Growth and Maturity stages, there is usually significant work done to reduce costs. When a product starts its decline, most of the easy changes to lower cost are done and the excitement of workiing on a growign product is also gone. Additionally, as the volume drops, overhead rises as a percent of cost. The reason this is important is that managing a declining product is just as important as managing a growing one. In all cases, action must continue to be taken.