1. Universal Data Model1.2 June 2011

2. Universal Data Model (UDM)
What?
Information model
Data + user interactions
Cross-portfolio
Extensible
Public not private
Why?
Transparency
Usability
Consistency
Interoperability
Where?
UCMDB 9.x
BSM 9.x
Executive Scorecard
Solutions (CLIP, CCRM)

3. UDM Conceptual Model 1.1.1 Business Enablement BusinessProcess
BusinessService
ServiceLevelAgreement
Incident
Asset
Application & Services
Service Support
Asset & Financial
InfrastructureService
BusinessApplication
BusinessTransaction
Project Management
Party
Software
Contract
RunningSoftware
InstalledSoftware
RequestForChange
Infrastructure
Project
NetworkEntity
Node
NodeElement
ApplicationSystem
Facilities
CostCenter
Kpi
Location

4. Current UDM Usage        CMS (UCMDB 9.0) RTSM
BSM internal model is UDM. The sync between BSM & UCMDB does not require transformation 
UDM Sync
The data exchange format used in CLIP– for exchange of incident records
UCMDB Model   
Business Service Management (BSM 9.0)
The internal class model defined in the UCMDB and leveraged by BSM
IT Service Management (ITSM) 
UDM over REST 
RTSM 

5. UDM Compliance Outbound Compliant Business View FPA XS
Studio
Dashboard Pages
Foundation
KPI Engine
FPA
Allocation Engine
BO Reports
KPI results
Config UI
Metamodel Compliant Dimensional Model in Data Warehouse
Customer DS
XS BO Universes
FPA BO Universes
XS DB Views
FPA DB Views
Input Model Compliant Input Connectors
UDM Aligned Target Schema
BODS
Source Staging
Consolidation
Target Staging
ETL
There are many places to consider regarding compliance. Possible places where compliance can be applied. We focused on the Business View case.
PPM
BSM SM AM
CMDB
External sources and POC

6. Modeling Analytics
Better Insight into Business Performance

7. Data Model in Application
UDM Classes and Attributes
The entities exposed in the universe are available as part of the data model available to build KPIs in the Formula Builder

8. Executive Scorecard UDM Content Areas
Enabling IT Executives to view and present their performance to the business
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 Used
Average Age of Hardware
Financials
Budget and expenses for projects/assets/CIs, Service TCO
% Capex vs. Opex
Actual vs. Planned Costs
Service Level Management
Planned downtime and outages for services
% Outage Time
Incident Response Time
UDM Content Areas
BTOT-WE-1145/3

9. Project Model Key Requirements Overdue Project Tasks Projects on Time
Projects with Objectives
Planned/Actual Hours
Project Initiation Time
Unhealthy Projects
Existing
New
This is a (rolling three-year) Statement of Direction and is subject to change without notice.

10. Asset Model Key Requirements Software Licenses Used Age of Hardware
Time to Procure
Licensing Exposure
Unused Software
Existing
New
This is a (rolling three-year) Statement of Direction and is subject to change without notice.

11. Financial Model Key Requirements Capex vs. Opex
Existing
New
Key Requirements
Capex vs. Opex
Discretionary vs. Non-discretionary
Actual vs. Planned Costs
Cost of IT Service Delivery
BTOT-WE-1145/3
This is a (rolling three-year) Statement of Direction and is subject to change without notice.

12. Service Level Management Model
Key Requirements
SLAs Breached
Outage Time
Incident Response Time
Achieved SLAs
Existing
New
BTOT-WE-1145/3
This is a (rolling three-year) Statement of Direction and is subject to change without notice.

13. UDM Compliance Vocabulary Compliant User Interface
BTOA Applications
FPA XS
Vocabulary Compliant User Interface
Reports and Dashboards
Semantic Business View (Universes)
Application Data Access
Outbound Compliant Business View
Target Systems
FPA
Workspace XS
Workspace ..
Workspace
Metamodel Compliant Dimensional Model in Data Warehouse
DB Views
DB Views
DB Views
DWH target Schema
Staging Systems
Loading
Input Model Compliant Input Connectors
Staging Schemas
Metadata DB
ABC DB
Extraction, Transformation and Consolidation
Data Source Systems
Source Interface
Source Interface
Source Interface
Source Interface
Source Interface
Source Interface SM AM
PPM
BAC QC
CMDB
Priority 1
Priority 2
BTOT-WE-1145/3

14. Virtualization & Cloud
UDM "Enhanced for Cloud"

15. 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.
Cloud Resource Manager
Allocation decisions
Monitor
Allocations
Adaptive Orchestration/ Provisioning via HP OO, BSA and ALU SAM
Jobs
Svc A
Svc B
Adapted Resource Allocation over Time
Distributed Resources
Svc A Workload
Svc B Workload
Upcoming Workload
1. Monitoring - - models mostly already in BDM, except installed software, and certain other cloud specific entities. 2. Provisioning - supporting models new area for BDM 3. Flexing - needs models for Virtualization, Cloud Storage extensions of existing BDM models 4. Tenant Management - Multi-Tenancy
This is a (rolling three-year) Statement of Direction and is subject to change without notice.
HP Confidential
3 June 2018

16. Modeling for Cloud Automation
Leveraged BDM Content
Class
Sub Classes
Communication Endpoint
IpServiceEndpoint
Application System
Cluster
NetworkEntity
IpAddress, IpSubnet, Layer2Connection, Vlan
Node
ClusterResourceGroup
NodeElement
DiskDevice, FileSystem, InstalledSoftware, Interface, LogicalVolume
RunningSoftware
ApplicationServer, WebServer
New Content
Requirement
Approach
Virtualization
Extension of existing UDM virtualization model
Cloud Storage
Extension of existing UDM storage model
Multi-Tenancy
Notion of tenants and their ownerships to be introduced
Configuration for Deployment
New Area of Model for UDM
This is a (rolling three-year) Statement of Direction and is subject to change without notice.

17. Example: Virtualization Model
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
This is a (rolling three-year) Statement of Direction and is subject to change without notice.

18. Wrap-Up

19. Summary Why should you care about the UDM?
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 adoption of UDM in key HP ITPS solutions
Broader support for asset & financials, project management, and service management
UDM being cloud ready thru virtualization and storage, multi-tenancy, and deployment models
For more information ,contact the UDM Team at
This is a (rolling three-year) Statement of Direction and is subject to change without notice.