©2010 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice

Session ID: BTOT-WE-1145/3 Twitter hashtag #HPSWU

©2010 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice

Speaker Name: Chris Peltz, Technology Strategist – CTO OfficeDate: December 1, 2010Session ID: BTOT-WE-1145/3

What's Next with the HP BTO Data Model

Forward Looking Statements

This document contains forward looking statements regarding future operations, product development, product capabilities and availability dates. This information is subject to substantial uncertainties and is subject to change at any time without prior notification. Statements contained in this document concerning these matters only reflect Hewlett Packard's predictions and / or expectations as of the date of this document and actual results and future plans of Hewlett-Packard may differ significantly as a result of, among other things, changes in product strategy resulting from technological, internal corporate, market and other changes. This is not a commitment to deliver any material, code or functionality and should not be relied upon in making purchasing decisions.

4 BTOT-WE-1145/3

What?

Why?

Where?

– Information model

– Data + user interactions

– Cross-portfolio

– Extensible

– Public not private

– Transparency

– Usability

– Consistency

– Interoperability – UCMDB 9.0

– BSM 9.0

– CLIP

BTO Data Model (BDM)

5 BTOT-WE-1145/3

BDM Conceptual Model 1.1.1Business Enablement

Application & Services

Software

Infrastructure

Facilities

Serv

ice

Support

Asse

t &

Financia

l

Pro

ject

Managem

ent

BusinessProcess

BusinessService

ServiceLevelAgreement

InfrastructureService

BusinessApplication

RunningSoftware InstalledSoftware

Node NodeElement ApplicationSyste

m

Location

Incid

en

tR

equestFo

rChang

eK

pi

Asse

tC

ontra

ctC

ostC

ent

er

Party

Pro

ject

BusinessTransaction

NetworkEntity

Current BDM Usage

CMS (UCMDB 9.0)

RTSM

Business Service Management

(BSM 9.0)

IT ServiceManagement

(ITSM)BDM over REST

BD

M o

ver

TQ

L

UCMDBModel

The data exchange format used in CLIP– for exchange of incident records

The internal class model defined in the UCMDB and leveraged by BSM

The interface exposed by UCMDB, via the Topology Query Language (TQL)

7 BTOT-WE-1145/3

What's Coming Next

ExecutiveScorecard

Financial Planning& Analysis

Cloud Service Automation

UCMDBConfiguration Mgr

UCMDBContent Packs

Software License

Compliance

Configuration Policies

Budgets and

costs

Vendor Manageme

nt

Virtualization

Project

Health

Downtime

Deployment

Models

Business

Strategy

This is a (rolling three-year) Statement of Direction and is subject to change without notice.

Modeling AnalyticsBetter Insight into Business Performance

BDM Compliance Objectives

– BDM-compliant models for ease of integration with other products

– BDM-compliant data sources to simplify data warehouse integration

– BDM as common language for user interactions

Analytical Applications and BDM

Project &Portfolio

Business Service Automation

3rd Party Data

LDAP

BSMServiceDesk

ApplicationQuality

Asset

Performance DataManagement data Processed data

Your Environment

UCMDB BTO Data Model

myBTO Dashboards

BTO DW

Financial Planning & Analysis (FPA)

Executive Scorecard (XS)

A solution supporting analytical reports and applications for decision support and analytics across the BTO portfolio

This is a (rolling three-year) Statement of Direction and is subject to change without notice.

10 BTOT-WE-1145/3

Executive Scorecard

Area Scope Example KPI(s)

Project Portfolio

Project tasks, issues, and risks; timesheet tracking

% Projects On Time% Healthy Projects

Asset Mgmt Software license compliance, asset lifecycle

% Software Licenses UsedAverage Age of Hardware

Financials Budget and expenses for projects/assets/CIs, Service TCO

% Capex vs. OpexActual vs. Planned Costs

Service Level Management

Planned downtime and outages for services

% Outage TimeIncident Response TimeBDM Content Areas

Enabling IT Executives to view and present their performance to the

business

This is a (rolling three-year) Statement of Direction and is subject to change without notice.

Mock up: Product view is an illustrations and might not represent final version.

11 BTOT-WE-1145/3

Key Requirements

– Overdue Project Tasks

– Projects on Time

– Projects with Objectives

– Planned/Actual Hours

– Project Initiation Time

– Unhealthy Projects

Project ModelKpi ProjectObjective

Project<<Party>>

Person

ProjectIssue

Party

ProjectTask

Service

supports

owns

has

manages

owns

has

supports

measures assigned

contains

Existing New

This is a (rolling three-year) Statement of Direction and is subject to change without notice.

12 BTOT-WE-1145/3

Key Requirements

– Software Licenses Used

– Age of Hardware

– Time to Procure

– Licensing Exposure

– Unused Software

Asset ModelAsset ProductModel

realizes

License

Is-a

LicenseContractexpresses

InventoryModel

manages

InstalledSoftwarerealizes

SoftwareCountDefinition

defines

defines

Existing New

This is a (rolling three-year) Statement of Direction and is subject to change without notice.

13 BTOT-WE-1145/3

– Capex vs. Opex

– Discretionary vs. Non-discretionary

Financial Model

Budget CostCenterCostPeriod CostCategory

recorded recorded

Project

hashas

Servicehas has

Contract

Asset

has

has

hashas

has

has

– Actual vs. Planned Costs

– Cost of IT Service Delivery

Key Requirements

Existing New

This is a (rolling three-year) Statement of Direction and is subject to change without notice.

14 BTOT-WE-1145/3

Key Requirements

– SLAs Breached

– Outage Time

– Incident Response Time

– Achieved SLAs

Service Level Management Model<<ItProcessRecord>>

RFC

PlannedDowntime

causes

ConfigurationItem

hasRegistered

ServiceContract

affects

Outage

has

<<ItProcessRecord>>

Incident

causes causes

ItProcessRecord

hasRegistered

Kpimeasures

measures

Existing New

This is a (rolling three-year) Statement of Direction and is subject to change without notice.

BDM Compliance

SM AM PPM QCBAC

Staging Schemas

Semantic Business View (Universes)

FPA XS

CMDB

Source Interface

Staging Systems

Data Source Systems

Metadata DB ABC DB

Target Systems

FPA Workspace

DB Views

..Workspace

DB Views

XSWorkspace

DB Views

Application Data Access

Analytical Applications

Extraction, Transformation and Consolidation

Loading

Reports and Dashboards

DWH target Schema

Source Interface

Source Interface

Source Interface

Source Interface

Source Interface

Vocabulary Compliant

User Interface

Outbound Compliant Business

View

Input Model Compliant

Input Connectors

Metamodel Compliant

Dimensional Model in

Data Warehouse

Priority 1

Priority 2This is a (rolling three-year) Statement of Direction and is subject to change without notice.

Virtualization & CloudBDM "Enhanced for Cloud"

Cloud Services Automation (CSA)– Dynamically monitor & provision the server, storage and network elements

as well as applications to meet the needs of current and upcoming workloads.

– Automatically grow and shrink the allocated resources in order to meet QoS targets.

Distributed ResourcesSvc A

Workload

Upcoming Workload

Svc B Workload

Jobs

Cloud Resource Manager

Adaptive Orchestration/ Provisioning via HP OO, BSA and ALU SAM

Allocationdecisions

MonitorAllocations

Svc A

Svc B

Adapted Resource Allocation over Time

This is a (rolling three-year) Statement of Direction and is subject to change without notice.

Modeling for Cloud Automation

New Content

Requirement

Approach

Virtualization

Extension of existing BDM virtualization model

Cloud Storage

Extension of existing BDM storage model

Multi-Tenancy

Notion of tenants and their ownerships to be introduced

Configuration for Deployment

New Area of Model for BDM

Leveraged BDM Content

Class Sub Classes

CommunicationEndpoint

IpServiceEndpoint

ApplicationSystem

Cluster

NetworkEntity IpAddress, IpSubnet, Layer2Connection, Vlan

Node ClusterResourceGroup

NodeElement DiskDevice, FileSystem, InstalledSoftware, Interface, LogicalVolume

RunningSoftware

ApplicationServer, WebServer

This is a (rolling three-year) Statement of Direction and is subject to change without notice.

19 BTOT-WE-1145/3

– HypervisorManagementSoftware• Manages Hypervisors deployed on Nodes

– Hypervisors• Deployed on (Physical) Nodes

• Define ResourcePools (CPU, Memory, etc.)

• Execute (Virtual) Nodes

– (Virtual) Nodes • Use resources from ResourcePool

• Have NodeConfiguration defining structure/contents

• Run BusinessApplications

Example: Virtualization Model

ResourcePool(Virtual)

Node

runs-on

executes

Hypervisor

BusinessApplication

uses

Cpu Memory

contains

(Physical)Node

runsOn

HypervisorManagement

Software runsOn

NodeConfiguration

defines

has

This is a (rolling three-year) Statement of Direction and is subject to change without notice.

Summary– Why should you care about the BDM?

• Increases product usability through consistency of terminology

• Reduces potential for data errors caused by semantic differences

• Accelerates time to develop integrations and solutions

– What can you expect in the future?• Broader support for asset & financials, project management, and service management

• BDM being cloud ready thru virtualization and storage, multi-tenancy, and deployment models

• Broader adoption of BDM in key BTO solutions

For more information ,contact the BDM Program Manager (jishnu@hp.com)

This is a (rolling three-year) Statement of Direction and is subject to change without notice.

Continue the conversation with your peers at the HP Software Community hp.com/go/swcommunity