http://itknowledgeexchange.techtarget.com/data-center-automation/data-center-automation-blueprint-made-a-round-of-updates/ Mon, 09 Nov 2009 09:41:22 +0000 http://wordpress.org/?v=2.6.2 http://itknowledgeexchange.techtarget.com/data-center-automation/data-center-automation-blueprint-made-a-round-of-updates/#comment-135 Shenning Mon, 14 Apr 2008 16:28:59 +0000 http://itknowledgeexchange.techtarget.com/data-center-automation/data-center-automation-blueprint-made-a-round-of-updates/#comment-135 After considering your comments and looking at the Blueprint again, I still feel that Analytics should stay as a separate category. Even though many Analytics products are specific to other categories as you point out, I think Analytics as a whole is important enough to warrant its own category. The main reason for even having the Blueprint is to educate on what is needed to achieve complete data center automation. With the size and complexity of today's data centers, Analytics is a must have capability and subjugating it to a part of each of the other categories minimizes the impact these solutions can have. Additionally, while many IT leaders are aware of some Analytics solutions that are available (e.g., Capacity Planning), it is clear that they are not very familiar with the breadth and depth of solutions that are available today. By calling out Analytics as its own category, the complete set of capabilities can be defined and brought to the forefront. In a time when virtualization and SOA-based architectures are increasing complexity in a way that simply throwing more bodies at it won't solve, the Blueprint can serve a valuable role in educating on the increased levels of automation that can be achieved across the board with Analytics. After considering your comments and looking at the Blueprint again, I still feel that Analytics should stay as a separate category. Even though many Analytics products are specific to other categories as you point out, I think Analytics as a whole is important enough to warrant its own category. The main reason for even having the Blueprint is to educate on what is needed to achieve complete data center automation. With the size and complexity of today’s data centers, Analytics is a must have capability and subjugating it to a part of each of the other categories minimizes the impact these solutions can have. Additionally, while many IT leaders are aware of some Analytics solutions that are available (e.g., Capacity Planning), it is clear that they are not very familiar with the breadth and depth of solutions that are available today. By calling out Analytics as its own category, the complete set of capabilities can be defined and brought to the forefront. In a time when virtualization and SOA-based architectures are increasing complexity in a way that simply throwing more bodies at it won’t solve, the Blueprint can serve a valuable role in educating on the increased levels of automation that can be achieved across the board with Analytics.

]]>