http://toutvirtual.com/blogs/2007/11/28/charge-back-models-a-lack-of-financial-brain-power/ Best Practices Guide to Virtualization - From Getting Started with Virtualization to Advanced Strategic Virtualization Concepts Tue, 14 Feb 2012 19:37:56 +0000 http://wordpress.org/?v=2.8.4 hourly 1 http://toutvirtual.com/blogs/2007/11/28/charge-back-models-a-lack-of-financial-brain-power/comment-page-1/#comment-40455 Constipation Remedies · Tue, 09 Nov 2010 20:57:36 +0000 http://toutvirtual.com/blogs/2007/11/28/charge-back-models-a-lack-of-financial-brain-power/#comment-40455 my doctor recommends relaxation exercises do help my panic attack " my doctor recommends relaxation exercises do help my panic attack “

]]> http://toutvirtual.com/blogs/2007/11/28/charge-back-models-a-lack-of-financial-brain-power/comment-page-1/#comment-39603 Valeria Kelly Tue, 05 Oct 2010 09:59:56 +0000 http://toutvirtual.com/blogs/2007/11/28/charge-back-models-a-lack-of-financial-brain-power/#comment-39603 i have panic attacks and my doctor reccomends relaxation exercise,', i have panic attacks and my doctor reccomends relaxation exercise,’,

]]> http://toutvirtual.com/blogs/2007/11/28/charge-back-models-a-lack-of-financial-brain-power/comment-page-1/#comment-4477 LifeCycle Wars? Gotta Be kidding… More Important Issues Remain To Be Resolved! : ToutVirtual Enterprise Virtualization - A Proper Virtual World Thu, 29 May 2008 02:29:46 +0000 http://toutvirtual.com/blogs/2007/11/28/charge-back-models-a-lack-of-financial-brain-power/#comment-4477 [...] Provisioning and retirement are obvious no? The automated creation and destruction of instances makes sense. Once an instance exists it must be maintained, so functional configuration, security remediation, and patch management (fixing bugs, not just closing holes), all fall into place. Now, lets see, that is left? Oh, yes, asset management, which beyond inventory and capacity planning, tracking, and trending, that wonders of wonders, the charge forward and back model! Well, blah, blah, duhe, once more. There are quite of few CPAs I know that really do hate charge models, not because of the validity of the concept is not sound, but because establishing and maintaining such models is a pain, can you see blood? I even know one individual that equated capitalization and deprecated costing hang ups with virtual instances as… and I quote… spreading the peanut-butter. Of course I asked, smooth or chunky… the reply was… and I quote again… I don’t know, super chunky? Quite a few big scale clients of virtualization have even developed their own in-house LifeCycle solutions, why? Because enterprise class solutions took more than two (2) years to get to market in 2004 and/or 2005, and some products were/are incomplete, nothing but band-aiding VMware ESX as a Linux distribution into the same old gadgets, very un-cool. The one exception would physical-to-virtual (P2V) solutions, which have remained tight and focused on modest improvement objectives rather than chasing feature set expansion as the only valued goal. [...] [...] Provisioning and retirement are obvious no? The automated creation and destruction of instances makes sense. Once an instance exists it must be maintained, so functional configuration, security remediation, and patch management (fixing bugs, not just closing holes), all fall into place. Now, lets see, that is left? Oh, yes, asset management, which beyond inventory and capacity planning, tracking, and trending, that wonders of wonders, the charge forward and back model! Well, blah, blah, duhe, once more. There are quite of few CPAs I know that really do hate charge models, not because of the validity of the concept is not sound, but because establishing and maintaining such models is a pain, can you see blood? I even know one individual that equated capitalization and deprecated costing hang ups with virtual instances as… and I quote… spreading the peanut-butter. Of course I asked, smooth or chunky… the reply was… and I quote again… I don’t know, super chunky? Quite a few big scale clients of virtualization have even developed their own in-house LifeCycle solutions, why? Because enterprise class solutions took more than two (2) years to get to market in 2004 and/or 2005, and some products were/are incomplete, nothing but band-aiding VMware ESX as a Linux distribution into the same old gadgets, very un-cool. The one exception would physical-to-virtual (P2V) solutions, which have remained tight and focused on modest improvement objectives rather than chasing feature set expansion as the only valued goal. [...]

]]>