What is the ni2-smarts integration? Actually, the principles are the following 1) 2) 3) 4) In the next slides, I will highlight these scenarios with a couple of screenshots and using a very basic demo database Next please
This first scenario shows that the Smarts real-time discovered topology and the ni2 cmdb are automatically reconciled. This concerns physical and logical resources. In this example, a set of devices, there composition and their network connectivity
This second scenario shows that business relationships such as consumers, services, cost but also details such as location are captured in the ni2 cmdb (which is still continuously updated – scenario 1) These business related items are being created trough a planned and documented change management process (as you saw in the previous presentation)
Still with this second scenario, it shows that the business topology have been updated within Smarts. Different alternatives here ; either by notification enrichment (populating user defined filed) or by updating the Smarts topology using the dynamic model (this is in our plan). In this example, downtime cost information shall be used to update the impact priority number It is important to mention that the business topology is continuously updated in Smarts so that Ni2 is acting as a source of notification for business topology.
In this scenario, we show that change tasks history can be leveraged from within Smarts trough in context launch of ni2 view
In this next scenario, we show that when incidents are being captured by Smarts, the business impact is being automatically highlighted thanks to an updated business topology.
From within Smarts, in context launch is then be used in order to pop-up a browser window with the incident history of a selected asset (device , service or connection) This information is also useful in order to take the appropriate action for problem resolution and to populate a trouble ticket with more detailed info.
In this last scenario, we show that detailed infrastructure (layer 1 – patch cabling) can also be presented from within the console.
My last slide summarizes the value proposition With this type of integration, we can provide more accurate … we can better set priorities to problem res Finally, it reduces the problem resolution time which one of the key objective when talking IT Service Management. The integration has been implemented using an iterative process Analyzing the valuable business cases Analyze implementation alternatives => Notification enrichment, in context launch, dynamic modeling Not GA -> still need to tune and validate the appropriate implementation strategies for each valuable scenario.
N(I)2 Smarts Jvp July 2005
The N(i) 2 Solution™/ SMARTS JVP
N(i)2 – Smarts Integration <ul><li>Smarts acts as a source of change trigger for N(i)2 CMDB and N(i)2 is acting as a full CMDB for Smarts </li></ul><ul><li>N(i)2 acts as a source of information for business topology for Smarts business impact </li></ul><ul><li>N(i)2 acts as a source of information for incident history for Smarts Business Impact </li></ul><ul><li>N(i)2 acts as a source of information for detailed infrastructure for Smarts </li></ul>
Scenario 1: Automated reconciliation btw Smarts and N(i)2 CMDB Physical and Logical topology 1 2
Scenario 2: Smarts leveraging business topology from N(i)2 Business topology created trough a change management process Consumers, Services, Location Costs 1 2
Scenario 2: Smarts leveraging business topology from N(i)2 Business topology automatically populated in Smarts 1 2
Scenario 3 : Smarts leveraging change management tasks from N(i)2 In context n(i)2 view on change task history 1 2
Scenario 4 : Smarts leveraging incident history from N(i)2 Incident Management 1
Scenario 4 : Smarts leveraging incident history from N(i)2 In context n(i)2 view on incident history 2 3
Scenario 4 : Smarts leveraging detailed infrastructure from N(i)2 In context n(i)2 view on detailed infrastructure for a connection
N(i)2 – Smarts Joint Value proposition <ul><li>Accurate and enhanced problem reporting to the service desk </li></ul><ul><li>Better prioritization of problem resolution </li></ul><ul><li>Reduces problem resolution time (MTTR) </li></ul>