The HP NGOSS Blueprint and Solutions

Basic information for the TMF product assessments

based on HP’s OSS Assurance Suite V1.4

Technical white paper

Issued: December 8th 2011

Table of contents
Executive Summary ........................................................................................................................ 2
HP NGOSS Functional Blueprint ...................................................................................................... 3
Simplified Blueprint with Scope on Assurance ................................................................................ 4
HP NGOSS Assurance Solution Blueprints ........................................................................................ 6
Advanced Network Operations Center ......................................................................................... 6
Integrated Operations Support & Readiness .................................................................................. 6
Integrated Customer Experience and Service Management Center ................................................... 7
Full Assurance Solution for VoIP on IMS ........................................................................................ 8
HP Products used in Solutions ...................................................................................................... 8
Specific Aspects of typical OSS requirements .................................................................................. 10
Combining eTOM and ITIL ........................................................................................................ 10
Automation of Problem Management .......................................................................................... 12
Event and Service Impact Management ...................................................................................... 12
Factory integration ................................................................................................................... 13
Data Model ............................................................................................................................. 13
For more information .................................................................................................................... 16
 Executive Summary
HP offers products and solutions for enterprise IT operations and for communication service
providers (CSP) operations support systems (OSS). Due to this broad portfolio HP is positioned
exceptionally to address the convergence of IT and Telco: Services become an Internet- and All-IP
based technology, Service Production platforms become IT infrastructures, OSS joins IT
Operations and eTOM applies ITIL processes.
HP’s offering comprises “carrier grade” specific tools (e.g. HP TeMIP for Fault Management of big
CSP Networks) or IT tools with Telco Extensions (e.g. HP Service Manager for ITIL Incident
Management in a CSP’s environment). Tools are pre-integrated in well defined solutions. The
overall suite addresses the typical requirements that are typical for today’s OSS market:
a) ITIL processes in an eTOM environment for Assurance
b) Telco specific (e.g. Access networks) as well as IT-similar technologies to be managed
(e.g. an IMS platform)
c) largely automation of trouble diagnostics and resolution
d) supporting a collaboration of outsourced “factories” (e.g. the access network), producing
atomic services, and an overarching end-to-end service management, producing service
bundles (i.e. ready for products)
A specific customer case was consciously selected for the TMF Frameworx assessment, to
demonstrate the mapping of products in HP’s OSS Assurance Suite addressing the requirements
as shown above to the TMF Frameworx Process Framework (eTOM) and Information Framework
(SID). This paper provides some explanations of certain aspects of HP’s OSS solutions, as listed
above.
HP applies its “NGOSS Blueprints” to describe the functional offerings and description of generic
and pre-integrated solutions, as well as specific customer case solutions. The NGOSS Blueprints
are defined in a version 1.4 as “HP OSS Assurance Suite V1.4”. It comprises an agreed set of
solutions with pre-integrated products and 3rd party integrations. Depending on the customer case,
products can be combined to address the specific requirements and context with the best business
benefit; the same processes may require alternative products, e.g. eTOM processes Resource
Trouble Management and Service Problem Management can be realized with IT Tools (HP OMi)
or Carrier Grade Tools (HP TeMIP). Therefore the TMF Frameworx conformance assessment did
double assessments for some processes.
Note: while the HP NGOSS Blueprint in general addresses fulfillment and assurance, this paper
has a focus to assurance.

2
HP NGOSS Functional Blueprint
HP’s NGOSS Functional Blueprint (Figure 1) outlines HP’s functional offering for OSS overall. Its
structure is a pragmatic approach to allow mapping of products on the OSS market to functional
building blocks. It takes into account HP’s experience from customer engagements worldwide, as
well as TMF Frameworx process framework (eTOM), application framework (TAM) and ITIL based
operations workflows. It serves as a pattern to enable various solutions, to serve different customer
scope and environment.

Fulfillment Domain Assurance Domain

Common Data Domain
Subscription
Product Catalog Customer Mgmt
Inventory
Config Mgmt
Service Catalog Resource Catalog Service Inventory Resource Inventory Data Integrity Mgmt
System (CMS)

Order Mgmt Domain Change Mgmt Domain Problem Mgmt Domain Service Mgmt Domain

Order Portal Workforce Mgmt Help Desk SLA Management

Order Order Customer Experience

Change Mgmt Incident & Problem Mgmt
Entry Mgmt Assurance

OS&R Domain
Diagnostics & Resolution
Order Distribution Release Mgmt Service Quality Mgmt
Automation

Service Activation Domain Configuration Mgmt Fault Mgmt Domain Performance Mgmt
Domain Domain
Resource Planning & Correlation Service
Service Order Mgmt Impact Usage Traffic Analysis
Optimization Mgmt Analysis

Service Design & Assign Configuration Mgmt E2E Fault Manager Performance Mgmt

Service Activation Reconcilliation Domain Fault Mgr Network Traffic Analysis

Element Abstraction / Interaction Domain

Service Resource
Assurance Probing &
Activation Configuration Discovery ITS Adapter
Mediation Tracing
Mediation Mediation

Figure 1 HP NGOSS Functional Blueprint Model

HP’s NGOSS functional blueprint (in its current version) model differentiates three layers:
A. The common data layer primarily contains the inventories, and all data, which may be
relevant for both, fulfillment and assurance, on customer, service and resource level. Here
fulfillment is primarily the master of data, while assurance acts more as a user. Functional
blocks like the Configuration Management System (CMS) are means, originating in ITIL
context, to federate the various data sources. In case of complex scattered inventory data and
the need of model transformations, a specific data integrity management is provided.
B. The applications layer follows the eTOM domains for Assurance and Fulfillment. But further
differentiation is more pragmatic, matching typical applications functionality on the market.

Fulfillment differentiates two main functional domains:

a. the more automated part of Service (CFS) Activation (eTOM “Service Configuration &
Activation”), preceded by an Order Management and

b. the more manual part of Change & Configuration Management for Resources and
Services (RFS) (eTOM “Resource Management & Operations”), enabling any Service
(CFS) can be activated at all (therefore some operators call this part also OS&R). It
comprises also the discovery &reconciliation of inventory data from the network.

Assurance differentiates these functional domains:

3
 c. Fault management with the classical event management applications (eTOM
“Resource Trouble Mangement”), receiving events for resources or services and
evaluating their service impact and availability.

d. Performance Management (eTOM “Resource Performance Management”) may have

sub-functionality for network traffic or usage traffic. All may feed SQM with KPIs, or
fault mangers, when reaching thresholds. The usage traffic is also essential input for
customer experience management.

e. Service Management differentiates three major application blocks:

i. operational Service Quality Management, which is proactive, not customer

specific and receiving network data from fault, performance and active
probing into account,

ii. Customer Experience Assurance, taking customer specific data such as xDR or
other performance data into account,

iii. SLA Management, receiving data from various sources to monitor contracted
KPIs. In context of customer relationship management, SLA management may
become part of OSS, when operations have to monitor e.g. important business
customers more real-time.

f. The Problem management comprises the ITIL Incident and problem management,
connected to resource management thru change management, which applications
are part of the Fulfillment stack (see above).

C. An element abstraction layer may be used to hide vendor specific (protocols, data models etc)
from the generic applications. Any case, the interaction with the network is addressed in this
layer. This may also comprise an IT-Service (e.g. WebServices) Adapter to interact, e.g. with
a partner or supplier systems, providing e.g. an outsourced network management.

Simplified Blueprint with Scope on Assurance

Since any solutions integrates into a full/existing environment, the functional blueprint helps to
identify the complete integrations. However, for gaining an overview on possible assurance
solutions, Figure 2 simplifies the functional blueprint and reduces the scope. The domain of
common data, change and configuration management and problem management are converged
into a domain just called Operations Support.

4
 Operations Support Assurance

Incident & Problem

SLA Management
Mgmt
Service
Inventory

CMS & Data Integrity Mgmt.

Change Mgmt Service Quality Mgmt

Customer
Workforce Mgmt Experience
Assurance
Re- Fault &
Performance
source Service Impact
Mgmt
Inventory Mgmt
Configuration Mgmt

Figure 2 Simplified HP NGOSS Functional Blueprint Model, Scope on Assurance

This simplified functional blueprint is used in subsequent sections to depict variants of typical
assurance solutions, integrated by HP OSS Transformation team, and adapted to the specific
case.

5
 HP NGOSS Assurance Solution Blueprints
Depending on the specific case, products are combined and tailored, to provide the specific
solution, matching the customer needs for processes, managed infrastructure, existing environment
etc. Four examples of Solutions are given, from which the last one is used by the TMF Frameworx
Conformance assessment.

Advanced Network Operations Center

A solution of a typical network operations center (NOC), with fault and performance management
including service impact analysis is shown in Figure 3. The TeMIP based umbrella fault
management may comprise domain managers such as NNM (for IP networks) or integrate EMS.
MyCom is used as comprehensive performance management solution, generating events on
threshold crossing. The trouble management is realized using ITIL incident, problem and change
management with HP ServiceManager, and the data integrity management (with UTM) allows
integration of single inventories from HP partners or of scattered inventories for the use by
assurance. The colors indicate the scope of coverage:
 orange blocks indicate the HP or OEM products, provided complete solution
 green blocks indicate other functional blocks in scope of Assurance, but not from HP

Operations Support Assurance

Incident & Problem

SLA Management
HP Mgmt
Service
Manager Service
Incident & Problem & Inventory
HP uCMDB & UTM

Change Mgmt.
Change Mgmt Service Quality Mgmt

Customer
Workforce Mgmt HP TeMIP Experience
& UCA Assurance
Re-
Partner
Resource
Fault & HP PI
Perfor-mance
Resource
source & OM
Service Impact Performance
Inventory Mgmt
Inventory &Mgmt
NNM Mgmt.
Configuration Mgmt Fault & Service
Impact Mgmt.

Figure 3 HP Solution Example for an Advanced NOC

Integrated Operations Support & Readiness

Another example in Figure 4 shows an integrated ITIL incident, problem, change and workforce
management with HP Service Manager, automated using Operations Orchestrations for access to
the network as well as updates to an Inventory of HP partners for configuration changes. In that
example uCMDB may be used for assurance relevant service topology, integrating resources of
the network inventory.

6
 Operations Support Assurance

Incident & Problem

SLA Management
Mgmt
Partner
Service
HP Service Inventory
Manager
Change Mgmt Service Quality Mgmt

HP uCMDB
HP Operations
Orchestrations
Incident & Problem &
Customer
Change & Workforce
Workforce Mgmt Experience
& Config Mgmt & Assurance
Automation Re-
Partner Fault &
Perfor-mance
Resource
source Service Impact
Mgmt
Inventory Mgmt
Configuration Mgmt

Figure 4 HP Solution Example for an Integrated OS&R

Integrated Customer Experience and Service Management Center

A full SOC solution, integrating Customer Experience with Contractual SLA Management and
operational SQM is depicted in Figure 4. The uCMDB based SQM may be fed from existing fault
and performance management, processs KPIs (e.g. MTTR, MTTD) and aggregated KQIs (e.g.
MOS per region) from the CEM. The CEM will take probe data or xDRs into account, and allows
feeding of contracted SLA Management. The uCMDB may read service instance data from a
service inventory.

Operations Support Assurance

Incident & Problem HPManagement

SLA USLAM
Mgmt SLA Management
Partner
Service
Service
Inventory
Integrity Mgmt.

Inventory
Change Mgmt HPQuality
Service SQMMgmt
DatauCMDB

Service Quality Mgmt

Partner
CEA
CMS &HP

Workforce Mgmt Customer

Experience
Re- Fault & Assurance
Performance
source Service Impact
Mgmt
Inventory Mgmt
Configuration Mgmt

Figure 5 HP Solution Example for an Integrated SOC

7
 Full Assurance Solution for VoIP on IMS
An existing solution was used e.g. to define the scope and perform the assessment against the
TMF process and information framework assessment. It addressed the management of an IMS
platform with its VoIP services. The specific products in scope of the assessment are mapped to the
functional blueprint as shown in Figure 6 below:

Operations Support Assurance

HP Service
Incident & Problem
SLA Management
Manager
Mgmt

HP Operations Service
Inventory

Integrity Mgmt.
Orchestrations
Incident
Change& Problem
Mgmt & HPQuality
Service SQMMgmt

DatauCMDB
Change Mgmt. Service Quality Mgmt

CMS &HP
Customer
Workforce Mgmt Experience
Assurance
Re- HP OMi
Fault & HP PI
Perfor-mance
source Service
Fault Impact
& Service Performance
Mgmt
Inventory Mgmt
Impact Mgmt. Mgmt.
Configuration Mgmt

S/P Interaction
HP Adapter Framework
SOA Adapter

Figure 6 HP Solution Blueprint Option for Assurance

In addition to the simplified assurance blueprints, the integration with other OSS systems, e.g
realized by suppliers or partners is indicated with the “S/P Interaction” domain.

HP Products used in Solutions

Brief description of products:
 HP Service Manager is used for Incident, Problem and Change Management, which are
classic ITIL processes. They complement various eTOM process elements (see section
“Combining eTOM and ITIL”).
 HP Operations Orchestrations is used to automate parts of the Incident, Problem and
Change Management (see also section “Automation of Problem Management” below)
 HP Operations Manager with HP Network Node Manager is used for Fault
Management, while OM i brings in the topology based event correlation and the service health
management (see also section “Event and Service Impact Management” below)
 HP TeMIP provides an umbrella Fault Management. It may use other HP event management
applications (e.g. NNMi or OM) or 3rd party EMS as underlying domain management systems.
 HP Performance Insight provides the Resource Performance Management
 HP SQM based on Business Availability Center (BAC) implements the Service Quality
Management. HP SQM comprises also extensions for uCMDB CI-types to support the TM Forum
Business Information Framework.

8
 HP Universal SLA Manager (USLAM) provides contractual SLA management for
dedicated customers.
 HP uCMDB uses federation with the 3rd party inventories. It provides the assurance relevant
part of the data model while avoiding data duplication. HP uCMDB serves as a basis to various
HP assurance applications.
 HP Adapter Framework enables the integration of Supplier/Partner organizations,
providing resources or services (see section “Factory integration”)

9
 Specific Aspects of typical OSS requirements
For specific solutions, specific configurations and integrations are available. The subsequent
sections provide information mentioned in the mapping tables of the TMF assessments, and
highlight typical aspects of today’s OSS market.

Combining eTOM and ITIL

As already mentioned the typical assurance customer use cases require ITIL as reference for (often
called:) Trouble Ticket management, and eTOM for all other areas. “Trouble Tickets” here are a
synonym for Service Problem-, Service Performance Degradation-, Resource Trouble-, Resource
Performance Degradation- and S/P Problem - Report s. ITIL is a very typical industry requirement
and the combination has been discussed in documents of TMF such as TR143 or GB921V as well
as by various OSS vendors. However, a Mapping to TMF Frameworx standards stays not straight
forward and is seldom defined precisely, per process step in eTOM.
ITIL is more descriptive in (dynamic) process flow definitions than eTOM, but not specific to the
subject of the trouble. eTOM defines the necessary processes (as static decomposition) specific to
the subject of the trouble, but without fixing a sequence of execution (definition of dynamic flows).
ITIL differentiates a trouble ticket first by its specific workflow: incident, problem, change-
management etc., while eTOM differentiates first of the subject of the trouble ticket: service and
resource, each for fault or performance trouble, what is just a parameter of a trouble ticket in ITIL.
HP applies a schema using
1. specific tools to detect the problems, either in the managed network or services, or from
interaction with customers,
2. ITIL best practice workflows (here with HP Service Manager) once a problem is detected and
has to be managed, and
3. Specific tools and ITIL best practice processes in combination for deeper diagnostics or overall
reporting.
The schema may be expressed more concrete in an assignment of ITIL and Monitoring
applications to level 3 processes as indicated in Table 1.
All ITIL processes are implemented using HP Service Manager. Further automation (not mentioned
here) is achieved as described in section “Automation of Problem Management” below.
The detailed mappings of this and the specific applications, their detailed functionality are shown
in the detailed reports, available at the TMF web pages of product assessment results.
Note, although ITIL differentiates the trouble categories into Incident, Problems, Workaround etc.
for simplification, the assessment mappings refer only to Incident Management workflows. Of
course, the full implementation always comprises the related processes.

10
 eTOM level 2 1.1.1.6 1.1.1.7 1.1.2.3 1.1.2.4 1.1.3.3 1.1.3.4 1.1.4.3 Service Manager’s
process Problem Handling Customer QoS/SLA Service Problem Service Quality Resource Trouble Resource S/P Problem ITIL Best Practice workflows
elements Management Management Management Management Performance Reporting & (cf. [HP SM ITIL Procs])
Management Management

Specific HP Service HP Universal SLA HP TeMIP HP SQM HP TeMIP HP Performance HP Service

Application Manager Service Manager and/or and/or Insight Manager
Desk HP OMi HP OMi Service Desk
Abstraction of
level 3 process

(1) Monitoring 1.1.1.6.1 1.1.1.7.1 1.1.2.3.7 1.1.2.4.1 1.1.3.3.1 1.1.3.4.1 1.1.4.3.2 Specific application
& trouble Isolate Customer Assess Customer Survey & Analyze Monitor Service Survey & Monitor Resource Receive S/P
detection Problem QoS/SLA Service Problem Quality Analyze Performance Problem
Performance Resource Trouble Report

(2) Trouble 1.1.1.6.5 1.1.1.7.4 1.1.2.3.1 1.1.2.4.5 1.1.3.3.7 1.1.3.4.5 1.1.4.3.1 Specific application &
Report Creation Create Customer Create Customer Create Service Create Service Create Resource Create Resource Initiate S/P SM Incident Logging
Problem Report QoS Performance Trouble Report Performance Trouble Report Performance Problem
Degradation Report Degradation Report Degradation Report Report

(3) Trouble n/a n/a 1.1.2.3.2 1.1.2.4.2 1.1.3.3.2 1.1.3.4.2 n/a Specific application &
Report Diagnose Service Analyze Service Localize Analyze Resource SM Incident Assignment,
Diagnostics Problem Quality Resource Trouble Performance SM Incident Invest. & Diag.,
SM Incident Escalation

(4) Trouble 1.1.1.6.6 1.1.1.7.2 1.1.2.3.3 1.1.2.4.3 1.1.3.3.3 1.1.3.4.3 n/a SM Change & Config.
Report Correct & Manage QoS/SLA Correct & Resolve Improve Service Correct & Control Resource Mgmt
Resolution Recover Customer Violation Service Problem Quality Resolve Resource Performance
Problem Trouble

(5) Trouble 1.1.1.6.3 1.1.1.7.5 1.1.2.3.4 1.1.2.4.6 1.1.3.3.4 1.1.3.4.6 1.1.4.3.3 SM Incident Escalation,
Report Tracking Track & Manage Track & Manage Track & Manage Track & Manage Track & Manage Track & Manage Track & SM Incident SLA
Customer Problem Customer QoS Service Problem Service Quality Resource Trouble Resource Manage S/P Management
Performance Performance Performance Problem
Resolution Resolution Resolution Resolution

(6) Trouble 1.1.1.6.4 1.1.1.7.6 1.1.2.3.6 1.1.2.4.7 1.1.3.3.6 1.1.3.4.7 1.1.4.3.5 SM Incident Closure,
Report Close Close Customer Close Customer Close Service Close Service Close Resource Close Resource Close S/P SM Incident Escalation
Problem Report QoS Performance Trouble Report Performance Trouble Report Performance Problem
Degradation Report Degradation Report Degradation Report Report

(7) Report 1.1.1.6.2 1.1.1.7.3 1.1.2.3.5 1.1.2.4.4 1.1.3.3.5 1.1.3.4.4 1.1.4.3.4 See specific application &
Monitoring & Report Customer Report Customer Report Service Report Service Report Resource Report Resource Report S/P SM Implicit Reporting of
Trouble Problem QoS Performance Problem Quality Trouble Performance Problem Incident Mgmt
Processing Performance Resolution

Table 1 Mapping of ITIL to eTOM level 3 processes

11
 Automation of Problem Management
The ITIL conformant Incident, Problem and Change Management processes are provided with HP
Service Manager. These are described detailed in [HP SM ITIL Procs]. However, ITIL processes
can be automated in parts.
Specific Automation in particular for diagnostics and resolutions, requires a specific workflow
engine, which is provided thru HP Operations Orchestrations. However, any fault diagnostics or
resolution cannot be off-the-shelf, as every trouble has individual signature and resolution, which
need to be configured within the applications, based on operators experience and expertise.
Therefore HP Operations Orchestrations provides the means for automating the trouble and
problem management processes.
The TMF assessment was done based on a specific customer example, providing specific
approach to automate Incidents Diagnostics and Resolutions, to provide evidence of the
automation capability: the “Fault Tree” concept: expected problems (sort of known problems) are
managed as nodes of a problem hierarchy (a folder hierarchy within HP OO), for which each has
its own problem detection workflow. If the detection is positive, more detailed nodes will be
executed, to narrow down the problem, or finally to call a resolution workflow.

Event and Service Impact Management

The solution for an Advanced Network Operations Center as shown in Figure 3 shows TeMIP with
UCA providing Event and Service Impact Management:
 HP TeMIP, the classic umbrella fault management for big networks with subordinated EMS
collects events for resources or services from managed network elements or EMS. TeMIP is
highly scalable and integrates with various technologies to be managed.
 HP UCA, Universal Correlation Analyzer, correlates events and applies network and/or service
topology for correlation. Thus it enables also the Service Impact Analysis, by propagating
events and their impact to the impacted services. UCA may be used standalone or with other
fault management systems.
 TeMIP Service Console allows combining TeMIP fault management with other service
management applications in one GUI, such as OMi or SQM.
The conformance of TeMIP is done in the second phase of the conformance assessment.
The first phase of the conformance assessment used a more simple solution for event and service
impact management, as shown with the Full Assurance Solution for VoIP on IMS and Figure 6 for
the assessed IMS customer case. The products used are
 HP Network Node Manager i (NNMi), collects events thru SNMP of IP network nodes and
interfaces. HP NNM can be seen as domain manager for IP networks
 HP Operations Manager (OM), collects events from IT systems and application thru off-the-shelf
plug-ins. OM can be seen as domain manager for IT systems.
 HP Operations Manager i (OMi) “understands” the service hierarchies/topology as from the
uCMDB (and its access to inventories). OMi collects events from subordinated OM and NNMi
and provides a single GUI to the operator, with its event console and the service health view.
Hence OMi enables
– topology based correlation, identifying root cause and symptomatic events
– service impact analysis, with mapping of events to service health indicators
Note: the notion “service health” may also be explained as “service status (expressed thru
heath indicators), based on resource fault information”.
See [HP OMi Concepts] for Event- and Health-Perspective.

12
Factory integration
The “Factory Concept” was defined by Deutsche Telekom. The idea is the production of semi-
products (e.g. atomic services), delivered by “factories” and being assembled in final products
(e.g. composite services) by higher level factories.
This is comparable to typical situations with outsourced networks where the NOC is operated by
the network provider, while the service provider operates only an overarching end-to-end service
management SOC. Networks are black boxes to the service operator (the solution example
“Integrated Customer Experience and Service Management Center” may address such a service
management factory).
Comparing the TMF process framework, the factory concept shapes organizational units
(“factories”) into three layers:
1. Customer level (i.e. customer relationship management or BSS layer)
2. Service level, which consumes “atomic” services (e.g. Copper Access, VoIP, IP TV, Internet)
delivered by internal or external suppliers into “composite” services (e.g. “Triple-Play-at-
Home” to the Customer level
3. Resource level, which delivers the “atomic” services to the service level and managing of a
production infrastructure (e.g. networks or single resources); a resource management factory
can also be seen on a supplier/partner level.
The figure outlines a theoretic example, how a factory model can be structured:

Customer facing unit Customer facing unit

“Home Products” “Business Products”

Service Service
Service
factory factory
factory “Home “Business
“FMC VoIP” Bundle” Bundle”

Resource Resource Resource Resource Resource Resource Resource

mgmt. mgmt. mgmt. mgmt. mgmt. mgmt. mgmt.
“Mobile “Fixed “Call “Internet” “Transport “CPE” “Office
Access” Access” Control” ” Apps”

Figure 7 Example of a Factory Model

The arrows indicate the flow to call IT-Services (e.g. WebServices) between the factories, using a
communication bus. These IT-Services are provided by Adapters.
In general, all factories can be internal or external suppliers or partners. Hence the factory
concept is also used to assess the ability to integrate with a Supplier/Partner Relationship
Management.

Data Model
The data models used by HP assurance applications use SID, to allow predefined Service or
Resource Models to CSP operators. HP’s uCMDB provides an extension to its CI-Type definitions
called “Telco Universe”.
Note, the uCMDB does not substitute the role of a full Service- and Resource Inventory (even it
could be extended for this purpose). Its primary purpose is the support of Assurance applications
for Operations. Entities and detailed attributes relevant for other domains (e.g. such as Fulfillment,
Meditation or Customer Relationship Management) are not supported off the shelf. Typically SID
ABE’s core entities and their required attributes are supported; some attributes (e.g. status) may be

13
 supported by specific and more sophisticated means (e.g. health indicators) instead of SID data
definitions.
Important ABEs such as Service- or Resource-Specifications are relevant, when Service or
Resource-Instances are created in Fulfillment processes. For operational assurance, the service or
resource models may be also slightly different from Specifications for Fulfillment; the uCMDB Telco
extensions brings a lot of predefined models, inherited from SID entities (SID conformant CI-Type
definitions). See Figure 8 shows the complete telco-extension off-the-shelf. SID entities are marked
with red or yellow frames. The trees indicate inheritance structures.

Figure 8 SID Telco Extension of HP uCMDB

The previous figure shows a screenshot of the uCMDB CI-Type modeler. Any CIT can be extended
as needed.

An UML formatted diagram of Telco Universe is shown next the figure:

Connection

Network

Logical
Resource Physical
Resource

14
 Figure 9 SID Telco extension of HP uCMDB (UML)

The Telco Universe was initiated thru the SQM Application, as it requires to support specific Telco
Services. Its model ad relationship to SID is explained in [HP SQM UG], chapter 2, Service
Modeling, page 13f. Further information and specific deviations to SID are explained in [HP Telco
Uni WP], section “CMDB Telecom Universe”, page 7f.

15
 For more information
To read more about HP CMS solutions for CMS and OSS, go to www.hp.com/cms and checkout
for OSS Transformation with OSS Fulfillment and OSS Assurance and its specific Products or the
downloads for white papers and other information.
General Information about HP SW for IT Operations is available under www.hp.com/software
and look for IT Performance Suite.
Some specific documentation is refered to within this document. They are available, on the HP
support web pages under http://support.openview.hp.com/selfsolve/manuals . You may need to
register first.
[HP SM ITIL Procs] HP Service Manager, Processes and Best Practices Guide,
Software Version: 7.1x
“SM7.1x_ProcessesBestPractice.pdf”

[HP OMi Concepts] HP Operations Manager I for the Windows, Software Version: 8.10,
Concepts Guide
“OMi8.10_Concepts_Guide.pdf”

[HP SQM UG] HP Service Quality Management Solution, User Guide, Version 1.0
“hp_sqm_solution_user_guide_v1.0.pdf”

© Copyright 2011 Hewlett-Packard Development Company, L.P. The information contained herein is
subject to change without notice. The only warranties for HP products and services are set forth in the
express warranty statements accompanying such products and services. Nothing herein should be
construed as constituting an additional warranty. HP shall not be liable for technical or editorial
errors or omissions contained herein.

Trademark acknowledgments, if needed.

Created November 2011