CMDB数据采集EMC公司解决方案.ppt

* * Money slide. This dependency mapping screen shot shows an n-tier diagram for a Siebel business application. The call outs highlight the key components: Application server DB server Reports server Mail server File server Gateways Clusters So as an example, if a change manager or CCB (change control board) receives an RFC (request for change, like an upgrade or maintenance) related to a specific gateway or mail server that indirectly supports the Siebel application, this allows the CM/CCB to do rapid impact analysis to know that a change to this gateway will impact the corporate Siebel service. Better not do it at the end of the quarter, buddy! Whew! What we do without that nLayers solution…saving our jobs again. * * Key messages to conclude with: Dependency mapping is the missing link in IT management today – unlocks the ability to truly fix change management through impact analysis – by knowing how things relate, you can avoid 90% of problems in advance. Automate, automate, automate – dependency mapping is a manual process today. Dependency mapping is a poster child for process automation. Impending event of the decade: find the data center move or consolidation project in the customer’s enterprise and latch onto it. Good things will happen I promise. Real-time management is EMC’s ticket to differentiation – nLayers and Smarts excel and win if we find those accounts where this is critical, or we make it critical. CMDB applications now: use Flash CMDBs and Foundational CMDBs now and achieve immediate value. Don’t wait for a committee to form and reports to be written. You can achieve instant ROI by getting started now. Why wait? * * * * The best way to approach this slide is to break it into 5 major pieces: The lower section describes how we collect data (passive active) and what kinds of data we collect. The middle section shows what we do with the collected data: discovery, DM, change tracking, impact analysis, CMDB analytics and then h