1. Service modelling on the top of a dependency graph of a service available in a CMDB

2. PROBLEM STATEMENTS Service Modelling
Statement : Performing service modelling on the top of a dependency graph of a service available in a CMDB.
Synopsis : A configuration management database (CMDB) is a data repository that stores data related to IT assets or configuration items (CI) as well as the relationships between CIs.
A service model needs to be created dynamically out of the dependent Cis and their relationships in CMDB. The model should be graphical and should take care of the various types of relationships between Cis. The model should also allow dynamic creation of relationships by the use of a drawing tool. The model should depict change in service states because of change in states of other Cis in the model. The impact analysis can also be done through an impact simulator through which impact of a state change on one dependent CI on a service availability can be analysed by the user.

3. RESOURCES
Service Modelling
Description : Service Model

4. RESOURCES Service Modelling Description : Relationship List
Name
Type
Service A – Appl A1
Rel_1
Depends On
Service A – Appl A2
Service A – Appl A3
Service B – Appl B1
Service B – Appl B2
Service B – Appl B3
Service B – Appl B4
Service C – Appl C1
Relationship
Name
Type
Appl A1 – Web Server A1
Rel_2
Hosted On
Appl A2 – App Server A2
Appl A3 – App Server A2
Appl B1 – Load Balancer 1
Appl B1 – App Server B3
Appl B2 – App Server B4
Appl B3 – App Server B4
Appl B4 – App Server B5
Appl C1 – App Server C1
Appl C2 – App Server C1
Relationship
Name
Type
Appl A1 – DB1
Rel_3
Uses
Appl A2 – DB2
Appl A3 – DB2
Appl B1 – DB3
Appl B2 – DB3
Appl B3 – DB3
Appl B4 – DB4
Appl C1 – DB5
Appl C2 – DB5
Relationship
Name
Type
DB1 – Cluster 1
Rel_2
Hosted On
DB2 – Cluster 1
DB3 – DB Server C1
DB4 – Cluster 2
DB5 – DB Server C2
Relationship
Name
Type
Load Balancer 1 – Web Server B1
Rel_4
Balances
Load Balancer 1 – Web Server B2
Relationship
Name
Type
Server1a – Cluster 1
Rel_5
Member Of
Server1b – Cluster 1
Server1c – Cluster 1
Server2a – Cluster 2
Server2b – Cluster 2

5. RESOURCES Description : Impact Simulation for Service A
Impact Relationship
Impact Weight
Impact
Service A – Appl A1 1
If Appl A1 is unavailable, Service A will be unavailable
Service A – Appl A2
0.5
If Appl A2 is unavailable, Service A will be partially unavailable
Service A – Appl A3
If Appl A3 is unavailable, Service A will be partially unavailable
Appl A2 and Appl A3 are unavailable
Appl A2 is unavailable
Server 1a is unavailable
Web Server A1 is unavailable
Service A is unavailable
Service A is available
Service A is unavailable
Service A is available

6. RESOURCES
Description : Impact Simulation for Service B

7. RESOURCES
Description : Impact Simulation for Service B

8. RESOURCES
Description : Impact Simulation for Service C

9. THANK YOU