Leveraging information from federated sources through IBM Jazz for Service Management

icarotech.comÍcaro Technologies ® Copyright 2013

1

IBM PULSE 2013 > Session 1351:Leveraging information from federated sources through IBM Jazz for Service Management

Fernando Moraes, R&D Manager, Ícaro TechnologiesChris Lazzaro, IBM


2

Agenda

On decision-making and information federation

OSLC and IBM Jazz for Service Mgmt

Quick ROI Exercise

Summary

Q&A


3

Decision-making...

“… is the selection of a course of action among several alternative scenarios.”

(Wikipedia)


4

IT Operations daily decisions...

...Must be quick and tactical!


5

Having the right info is keyfor decision-making

Most of the information your team needs for effective decision-making is within your IT environment

But have you ever struggled to pull that information from multiple systems and applications?


6

Common approaches for information sharing

Our customers usually consider:

1) Data replication/concentration

2) Pont-to-point integration

3) Data federation


7

1) Data replication/concentration

Problem: not usually a solution for IT Operations’ real-time information needs

Why?

- Data replication may bring inconsistency• “A man with two watches...”

- You may have plenty of data• May not be practical to replicate

- Data may change very frequently• You will never be up-to-date


8

2) Point-to-point integration

Problem: High initial cost, high TCO

Why?

- Different systems use different integration architectures• API, database, web services – you have to maintain them

all

- When new systems are incorporated, changes are needed

• Applications not aware of new information providers


9

3) Data Federation better for real-time information

No costly, risky data replication or point-to-point integration

Instead: on-demand access to up-to-date information


10

What are data federation principles?

Define common identifiers for the managed resources

Provide a resource “index”

Allow consumers to search the index for resources

Allow consumers to directly access resource data from providers


11

Federation in practice


12


Providers


13


Consumers


14


Index


15



16

Federation in practice Consumer

BMC Atrium informationrelated to a resource


17

Federation in practice Consumer

IBM ITM information related to the same resource


18

Data federation means that...

Each application will perform specialized management of aspects of the same resources

- Inventory- Configuration Management (CMDB)- System health monitoring- Capacity planning- Incident Management- Change Management


19

OSLC allows for a step further in Federation

OSLC: Open Services for Lifecycle Collaboration

- Community of software developers, operations experts, and organizations

Activities

- Gather industry experts- Openly discuss common problems and

solutions- Publish open specifications

Open Services for Lifecycle

Collaboration


20

OSLC principles

Built on the WWW architecture- Minimalist & loosely coupled - Standard data representation - Can be supported by existing applications

Use HTTP Uniform Resource Identifiers (URI) as a naming convention- So that people can look up those names- Include links to other URIs, so that anyone can discover

more things.

Linked Data


21

IBM Jazz for Service Management

IBM implementation of OSLC-compliant components:

Registry - to find data, resources & relationships

Visualization – to display multi-tool data in context

Administration – to lower cost of maintaining tools

Reporting – to better predict and plan

Security – for compliant & quick login & data integrity


22

IBM Jazz for SM: Real-Time Federation of Data

Gather info from all sources

License

Mgm

t

Work Orders

Chg History

Health

Versus launching multiple apps


23

IBM Jazz for SM: Plug-and-play integrationBuild once...

...and integrate everywhere


24

OSLC query examples

Retrieve all records that depend on a particular resource: - http://oslc-registry/oslc/rr/collection?

oslc.where=crtv:dependsOn=<http://oslc-registry/oslc/

resources/1>

Retrieve URLs for all model 4061-BKA ComputerSystem Resource Records: - http://oslc-registry/oslc/rr/collection?

oslc.where=crtv:model="4061-BKA" and rdf:type=<http://open-services.net/ns/crtv

%23ComputerSystem>

server

clause

qualif.

server

clause

qualif.


25

QUICK ROI EXERCISES


26

Scenario: Change Mgmt labor cost savings

As much as 70% of critical incidents – those that cause service downtime - are related to poorly planned or implemented changes.

Business value statement: - By using OSLC, an average customer can save ~USD

144 k a year in downtime related to poorly planned or implemented changes to the infrastructure.

Why?- Experience shows that reason #1 for change planning

failure is lack of accurate, real-time information


27

Scenario: Change Mgmt labor cost savings (cont.)

Current situation- 30 critical incidents per week- 30% of incidents related to poorly planned changes

(conservative)- Average service downtime per incident: 4 h- Avg cost per hour of service downtime: USD 10 k- Downtime costs per year: USD 360 k

Improvement with OSLC- 40% reduction in the change failure rate - Downtime costs per year (after): USD 216 k

Savings: USD 144 k, or 40%


28

Other possible OSLC ROI exercises

Reduction of average time to deploy an integration by 75%- Develop once, reuse many times

Customers can reduce the integration costs of an average project with 4 integrations by 33%

An average customer can save ~USD 60k a year in rework related to Change Management- Less changes not approved because of poor planning


29

SUMMARY


30

Summary

OSLC and IBM Jazz for Service Management alow for:- Easier, quicker, reusable integrations- Data federation

Up to 75% potential ROI - System integration deployment time savings- Labor cost and service downtime savings

Don’t miss the demo scenario at Expo!- IBM, BMC, Icaro and other BP’s tools integrated


31

Q&A


32

EXAMPLE SCENARIO


33

Scenario: Quicker, assertive response to incidents

Service Providers such as our customers must be quick in identifying the root cause of faults.

The more information available regarding a faulty equipment, the quicker the root cause and the fix procedure are found


34

Scenario description

An operator investigating a faulty element on IBM Tivoli Business Service Mgmt (TBSM) needs more information

She hovers over the element object in the TBSM service tree

Detailed information is fetched from a BMC Atrium CMDB OSLC provider and displayed to the operator

Information includes Incidents and Changes related to that element


35

Tools involved

Tools:- BMC Atrium CMDB

• Data provider. Contains CI details to be consulted by other applications

- Ícaro OSLC Provider• Standalone application that will enable BMC Atrium CMDB to

integrate to OSLC-enabled tools

- IBM Jazz for SM- IBM TBSM

BMC AtriumCMDB

ÍcaroOSLC

ProviderIBM

TBSMIBM Jazz for SM


36

A) Setup Phase

Steps:1) OSLC Provider connects to CMDB

2) OSLC Provider registers itself as an OSLC provider on Jazz for SM

3) OSLC Provider fetches CI ID’s from CMDB and stores them locally

4) OSLC Provider registers CI ID’s on Jazz for SM

BMC AtriumCMDB

ÍcaroOSLC

Provider

1. Connect to CMDB

3. Fetch CI IDs

2. Registerprovider

4. RegisterCI IDs

IBMTBSM

IBM Jazz for SM


37

B) Request providers

Steps:5) TBSM request CI details providers to Jazz for SM

6) Jazz for SM informs provider

BMC AtriumCMDB

ÍcaroOSLC

Provider

5. Requestprovider

6. Inform provider

IBMTBSM

IBM Jazz for SM


38

C) Request CI ID

Steps:7) TBSM request CI ID to Jazz for SM

8) Jazz for SM informs CI ID

BMC AtriumCMDB

ÍcaroOSLC

Provider

7. RequestCI ID

8. Inform CI ID

IBMTBSM

IBM Jazz for SM


39

D) Request data

Steps:9) TBSM requests CI details to OSLC Provider

BMC AtriumCMDB

ÍcaroOSLC

Provider

9. RequestCI details

IBMTBSM

IBM Jazz for SM


40

E) Provide data

Steps:10) OSLC Provider request CI details to CMDB

11) CMDB provides CI details to OSLC Provider

12) OSLC Provider forwards CI details to TBSM

BMC AtriumCMDB

ÍcaroOSLC

Provider

10. RequestCI details

11. ProvideCI details

12. Forwarddetails

IBMTBSM

IBM Jazz for SM


41

REFERENCES


42

REFERENCES


43

References

Open Services for Lifecycle Collaboration home- http://open-services.net/

Case Study: Open Services Lifecycle Collaboration framework based on Linked Data- http://www.w3.org/2001/sw/sweo/public/UseCases/IBM/

Search IBM developerWorks community for “Jazz for Service Management”- https://www.ibm.com/developerworks/

http://open-services.net/

http://www.w3.org/2001/sw/sweo/public/UseCases/IBM/

https://www.ibm.com/developerworks/


44

Acknowledgements and Disclaimers:

© Copyright IBM Corporation 2013. All rights reserved.

U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Please update paragraph below for the particular product or family brand trademarks you mention such as WebSphere, DB2, Maximo, Clearcase, Lotus, etc

IBM, the IBM logo, ibm.com, [IBM Brand, if trademarked], and [IBM Product, if trademarked] are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at “Copyright and trademark information” at www.ibm.com/legal/copytrade.shtml

If you have mentioned trademarks that are not from IBM, please update and add the following lines:

[Insert any special 3rd party trademark names/attributions here]

Other company, product, or service names may be trademarks or service marks of others.

Availability. References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates.

The workshops, sessions and materials have been prepared by IBM or the session speakers and reflect their own views. They are

provided for informational purposes only, and are neither intended to, nor shall have the effect of being, legal or other guidance or advice to any participant. While efforts were made to verify the completeness and accuracy of the information contained in this presentation, it is provided AS-IS without warranty of any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this presentation or any other materials. Nothing contained in this presentation is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software.

All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics may vary by customer. Nothing contained in these materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific sales, revenue growth or other results.

http://www.ibm.com/legal/copytrade.shtml


45

Demo Video

Watch Advanced Dashboards 2.0 demo: federated, dynamic integration with information providers, using OSLC.

http://youtu.be/BO-_0X58Nyo

More info: http://smconnect.net/jazzsm



http://www.youtube.com/redirect?q=http%3A%2F%2Fsmconnect.net%2Fjazzsm&session_token=KlHsi-bDT4sxct17_0JiA8Xn8ut8MTM2MzkwODM4OEAxMzYzODkzOTg4

Leveraging information from federated sources through IBM Jazz for Service Management

Technology

resource data

data federation principles

information federation

risky data replication

multitool data

leveraging information

oslc principles

ibm pulse