Today\u2019s column will focus on one of my pet peeves: the misuse of illustrations in an attempt to explain and organize management products. A blatant example of this, and one that drives me up a wall is the use of \u201cLifecycle Management\u201d to explain the offerings of server and desktop management vendors, particularly software distribution vendors.I\u2019ll scream the next time I see another lifecycle management slide in a server or desktop management vendor\u2019s presentation. Nearly all of them are using this illustration to depict what they sell.First of all, the term \u201clifecycle\u201d usually implies a logical and predictable progression of stages with a defined beginning and an end. For example, a person is born and enters infancy, then becomes a toddler, and then on to adolescence and puberty, then fast forward to middle age, on to old age and then the end of life. All of these stages are very predictable, and they are logical progressions. You simply can\u2019t jump back to adolescence from being a middle-ager.There is a legitimate case for using \u201clifecycle management\u201d when describing asset management from a financial perspective. The asset is procured, tracked through its useful life in the company, and then disposed of when obsolete.However, there\u2019s nothing logical nor predictable about server or desktop management. The servers and desktops are procured and then deployed, and these systems are also retired from service. But it is at that point that the predictability stops. During their useful life, these systems can be repurposed to another user or for another use, which means redeploying the appropriate software for its new use. Software patching occurs on an ongoing basis, as well as periodic software upgrades. Throw into the mix the possibility of requiring software migration. Users may also add their own applications, or IT may add new applications. For servers, IT may decide to do server consolidations, which may drastically change the configuration and use of the server.Then there is another emerging approach that is not yet widely used but is being talked about by vendors: automated provisioning. If automated provisioning takes hold, then all bets are off for any kind of semblance to a lifecycle. Servers could be swapped into and out of server pools, temporarily repurposed for an application, then swapped out and re-provisioned for another application.None of these functions are performed at predictable stages; they\u2019re just done on as needed. The servers and desktops don\u2019t have \u201clives\u201d; they are boxes that are used for whatever the current need is.Why are the server and desktop vendors all using \u201clifecycle management\u201d to illustrate an environment that doesn\u2019t map to a lifecycle at all? As I see it, there are two possibilities. Either the vendors don\u2019t understand the dynamic nature of the server and desktop environments that ITers have to deal with, or it\u2019s a marketing ploy to convey broad and full management of the server and desktop environment, as well as trying to simplify the explanation of how their tools fit together. It is more simply illustrated but clearly not representative of the server and desktop management environment. In my view, neither of these reasons justifies the use of \u201clifecycle management\u201d in this context.So the next time you see a server or desktop management vendor touting \u201clifecycle management,\u201d please do me a favor and ask them to stop using it. If we stick together, we can eradicate this menace from our world - well, at least we\u2019ll have one less irritant to put up with.